Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for any additional information.
2
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table of Contents This document has 551 pages
Summary of changes................................................................... 28
Radio resource management features.........................................40 RAN2578: AMR Codec Set for 2G-3G TrFO................................40 Description of RAN2578: AMR Codec Set for 2G-3G TrFO.........40 Benefits........................................................................................ 40 Requirements...............................................................................40 Functional description.................................................................. 41 System impact..............................................................................41 RAN2578: AMR Codec Set for 2G-3G TrFO management data...... 41 Sales information......................................................................... 43 Activating RAN2578: AMR Codec Set for 2G-3G TrFO............... 43 Verifying RAN2578: AMR Codec Set for 2G-3G TrFO.................44 Deactivating RAN2578: AMR Codec Set for 2G-3G TrFO...........46 Testing RAN2578: AMR Codec Set for 2G-3G TrFO................... 46 RAN3018: BTS Load Based AACR............................................. 51 Description of RAN3018: BTS Load Based AACR...................... 51 Benefits........................................................................................ 51 Requirements...............................................................................51 Functional description.................................................................. 52 System impact..............................................................................53 RAN3018: BTS Load Based AACR management data............... 53 Sales information......................................................................... 55 Activating RAN3018: BTS Load Based AACR.............................55 Verifying RAN3018: BTS Load Based AACR...............................56 Deactivating RAN3018: BTS Load Based AACR.........................57 RAN2963: Data Session Profiling................................................ 58 Description of RAN2963: Data Session Profiling......................... 58 Benefits........................................................................................ 58 Requirements...............................................................................58
Transmission and transport features..........................................212 RAN2913: Local and Remote IP Traffic Capturing.....................212 Description of RAN2913: Local and Remote IP Traffic Capturing.... 212 Benefits...................................................................................... 212 Requirements.............................................................................212 Functional description................................................................ 213 System impact............................................................................216 RAN2913: Local and Remote IP Traffic Capturing management data............................................................................................ 216 Sales information....................................................................... 217 Activating RAN2913: Local and Remote IP Traffic Capturing.... 217 Verifying RAN2913: Local and Remote IP Traffic Capturing......220 Deactivating RAN2913: Local and Remote IP Traffic Capturing...... 221 Stopping an IP Traffic Capturing session................................... 221 Testing RAN2913: Local and Remote IP Traffic Capturing........ 222 Test case 1: Capture traffic in Streaming mode......................... 222 Test case 2: Capture traffic in File mode.................................... 223 Test case 3: Capture traffic in different monitoring point............ 225 RAN2243: Performance Monitoring Based on ETH Service OAM... 227 Description of RAN2243: Performance Monitoring Based on ETH Service OAM.............................................................................. 227
Benefits...................................................................................... 227 Requirements.............................................................................227 Functional description................................................................ 228 System impact............................................................................230 RAN2243: Performance Monitoring Based on ETH Service OAM management data...................................................................... 231 Sales information....................................................................... 233 Activating RAN2243: Performance Monitoring Based on ETH Service OAM.............................................................................. 233 Activating Ethernet Service OAM PM........................................ 234 Activating Frame Loss Measurement session........................... 236 Activating Frame Delay Measurement session..........................237 Verifying RAN2243: Performance Monitoring Based on ETH Service OAM.............................................................................. 240 Deactivating RAN2243: Performance Monitoring Based on ETH Service OAM.............................................................................. 244 Deactivating Ethernet Service OAM PM.................................... 244 Deactivating Frame Loss Measurement session....................... 246 Deactivating Frame Delay Measurement session......................247 Testing RAN2243: Performance Monitoring Based on ETH Service OAM.............................................................................. 248 Testing Frame Loss Measurement session using dual-ended mode.......................................................................................... 250 Testing Frame Loss Measurement session using single-ended mode.......................................................................................... 254 Testing Frame Delay Measurement session.............................. 258
5 5.1 5.1.1
Operability features.................................................................... 264 RAN2199: BTS Event Triggered Symptom Data Collection.......264 Description of RAN2199: BTS Event Triggered Symptom Data Collection................................................................................... 264 Benefits...................................................................................... 264 Requirements.............................................................................264 Functional description................................................................ 265 System impact............................................................................267 RAN2199: BTS Event Triggered Symptom Data Collection management data...................................................................... 267 Sales information....................................................................... 269 Activating RAN2199: BTS Event Triggered Symptom Data Collection................................................................................... 269 Deactivating RAN2199: BTS Event Triggered Symptom Data Collection................................................................................... 270 Testing RAN2199: BTS Event Triggered Symptom Data Collection ................................................................................................... 271 RAN2919: OMS Certificate Update and Revocation Support.... 274 Description of RAN2919: OMS Certificate Update and Revocation Support.......................................................................................274 Benefits...................................................................................... 274 Requirements.............................................................................274
Functional description................................................................ 275 System impact............................................................................276 RAN2919: OMS Certificate Update and Revocation Support management data...................................................................... 277 Sales information....................................................................... 278 Testing RAN2919: OMS Certificate Update and Revocation Support.......................................................................................278 RAN2699: OMS System Status View.........................................279 Description of RAN2699: OMS System Status View..................279 Benefits...................................................................................... 279 Requirements.............................................................................279 Functional description................................................................ 280 System impact............................................................................283 RAN2699: OMS System Status View management data.......... 283 Sales information....................................................................... 284 Activating RAN2699: OMS System Status View........................ 284 Verifying RAN2699: OMS System Status View..........................285 Deactivating RAN2699: OMS System Status View....................286 RAN2393: Optical Fiber: RX/TX Level Monitoring..................... 287 Description of RAN2393: Optical Fiber: RX/TX Level Monitoring.... 287 Benefits...................................................................................... 287 Requirements.............................................................................287 Functional description................................................................ 288 System impact............................................................................288 RAN2393 Optical fiber: RX/TX level monitoring management data. 288 Sales information....................................................................... 289 Testing RAN2393: Optical Fiber: RX/TX Level Monitoring.........289 RAN3004: Parameter Categorization.........................................291 Description of RAN3004: Parameter Categorization..................291 Benefits...................................................................................... 291 Requirements.............................................................................291 Functional description................................................................ 292 System impact............................................................................293 RAN3004: Parameter Categorization management data...........293 Sales information....................................................................... 294 RAN2507: RNW Plan Progress Indicator and Abort.................. 294 Description of RAN2507: RNW Plan Progress Indicator and Abort. 294 Benefits...................................................................................... 294 Requirements.............................................................................294 Functional description................................................................ 295 System impact............................................................................299 RAN2507: RNW Plan Progress Indicator and Abort management data............................................................................................ 300 Sales information....................................................................... 301
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
5.7 5.7.1 5.7.1.1 5.7.1.2 5.7.1.3 5.7.1.4 5.7.1.5
5.8.1.6
RAN2554: Transport Configuration Fall-back............................ 301 Description of RAN2554: Transport Configuration Fall-back..... 301 Benefits...................................................................................... 301 Requirements.............................................................................301 Functional description................................................................ 302 System impact............................................................................303 RAN2554: Transport Configuration Fallback management data...... 304 Sales information....................................................................... 304 Activating RAN2554: Transport Configuration Fallback............. 304 Activating RAN2554: Transport Configuration Fallback using BTS Site Manager..............................................................................305 Activating RAN2554: Transport Configuration Fallback from NetAct CM Editor....................................................................... 305 Verifying RAN2554: Transport Configuration Fallback............... 305 Deactivating RAN2554: Transport Configuration Fallback......... 305 Deactivating RAN2554: Transport Configuration Fallback using BTS Site Manager......................................................................306 Deactivating RAN2554: Transport Configuration Fallback from NetAct CM Editor....................................................................... 306 Testing RAN2554: Transport Configuration Fallback................. 306 Test Case 1: Transport configuration fallback ........................... 306 Test Case 2: Transport configuration roll forward.......................308 RAN2229: Troubleshooting Data Management by NetAct.........309 Description of RAN2229: Troubleshooting Data Management by NetAct........................................................................................ 309 Benefits...................................................................................... 310 Requirements.............................................................................310 Functional description................................................................ 310 System impact............................................................................310 RAN2229: Troubleshooting Data Management by NetAct management data.......................................................................311 Sales information....................................................................... 312
Enabling MDT measurement collection for a particular subscriber.. 320 Configuring feature optional parameters....................................323 Verifying RAN2496: Minimization of Drive Tests........................ 324 Verifying MDT measurements collection for all UEs within the cell.. 325 Verifying MDT measurements collection for a particular subscriber ................................................................................................... 325 Deactivating RAN2496: Minimization of Drive Tests.................. 326 Disabling MDT measurements collection for all UEs within the cell. 326 Disabling MDT measurement collection for a particular subscriber. 327 RAN2443: BTS Resource Utilization Monitoring........................329 Description of RAN2443: BTS Resource Utilization Monitoring.329 Benefits...................................................................................... 329 Requirements.............................................................................329 Functional description................................................................ 330 System impact............................................................................331 RAN2443: BTS Resource Utilization Monitoring management data ................................................................................................... 332 Sales information....................................................................... 337 Testing RAN2443: BTS Resource Utilization Monitoring........... 338 Test case 1. Checking M5008C48 - M5008C50 counters..........338 Test case 2. Checking M5006C63 and M5006C57 counters..... 339 Test case 3. Checking M5011C8 and M5011C11 counters........341 Test case 4. Checking M5012C4 counter.................................. 343 RAN2555: Configurable Ranges for User Throughput Counters..... 344 Description of RAN2555: Configurable Ranges for User Throughput Counters................................................................. 344 Benefits...................................................................................... 345 Requirements.............................................................................345 Functional description................................................................ 345 System impact............................................................................347 RAN2555: Configurable Ranges for User Throughput Counters management data...................................................................... 347 Sales information....................................................................... 350 Activating RAN2555: Configurable Ranges for User Throughput Counters.....................................................................................350 Verifying RAN2555: Configurable Ranges for User Throughput Counters.....................................................................................352 Deactivating RAN2555: Configurable Ranges for User Throughput Counters.....................................................................................353 Testing RAN2555: Configurable Ranges for User Throughput Counters.....................................................................................354 Testing environment................................................................... 354 Test execution - case 1.............................................................. 355
RNC solution features................................................................ 391 RAN2251: Automatic mcRNC Resource Optimization...............391 Description of RAN2251: Automatic mcRNC Resource Optimization............................................................................... 391 Benefits...................................................................................... 391 Requirements.............................................................................391 Functional description................................................................ 392 System impact............................................................................393 Management data...................................................................... 394 Sales information....................................................................... 394 Activating RAN2251: Automatic mcRNC Resource Optimization.... 394 Verifying RAN2251: Automatic mcRNC Resource Optimization...... 395 Deactivating RAN2251: Automatic mcRNC Resource Optimization ................................................................................................... 399 RAN2928: DSP Pool Information in Measurements.................. 400 Description of RAN2928: DSP Pool Information in Measurements. 400 Benefits...................................................................................... 401 Requirements.............................................................................401 Functional description................................................................ 401 System impact............................................................................403 RAN2928: DSP Pool Information in Measurements management data............................................................................................ 403 Sales information....................................................................... 404 Activating RAN2928: DSP Pool Information in Measurements..404 Verifying RAN2928: DSP Pool Information in Measurements....406 Deactivating RAN2928: DSP Pool Information in Measurements.... 406 Testing RAN2928: DSP Pool Information in Measurements...... 406 RAN2959: mcRNC Step 7 Support............................................ 408
Description of RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio............................................................... 382 Benefits...................................................................................... 382 Requirements.............................................................................382 Functional description................................................................ 383 System impact............................................................................384 RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio management data.............................................................385 Sales information....................................................................... 386 Activating RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio...................................................................... 386 Verifying RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio...................................................................... 388 Deactivating RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio............................................................... 389
Two HSDPA carriers located in two different frequency bands.......... 83
Figure 6
The Enhanced Interference Cancellation procedure.......................... 96
Figure 7
The residual signal stream relationship.............................................. 97
Figure 8
Weighted Fair Queuing in PDCP layer of RNC................................ 129
Figure 9
End-user benefits of the RAN2510: In-bearer Application Optimization feature.............................................................................................. 129
Configurable Ranges for User Throughput Counters....................... 346
Figure 33
Overview of RAN2930: IMSI-based Call Monitoring.........................360
Figure 34
Site solution deployment for IPA-RNC..............................................363
Figure 35
IP interfaces between units in the IPA-RNC..................................... 363
Figure 36
Assigning IP address to external monitoring tool workstation.......... 367
DN09146788
19
RU50 Feature Descriptions and Instructions
20
Figure 37
Connection status in IPA-RNC......................................................... 369
Figure 38
Connection status in mcRNC........................................................... 370
Figure 39
IPA-RNC: Control Plane default profiles........................................... 370
Figure 40
mcRNC: Control Plane default profiles.............................................370
Figure 41
IPA-RNC: User Plane monitoring..................................................... 370
Figure 42
IMSI in TP profile for IPA-RNC......................................................... 371
Figure 43
IPA-RNC connected with CP profile, US UP profile, TP profile, and IMSI profile....................................................................................... 371
Figure 44
mcRNC connected with CP profile and IMSI profile......................... 371
Figure 45
Site solution deployment for mcRNC................................................374
Figure 46
PSK for mcRNC................................................................................375
Figure 47
Connection status in IPA-RNC......................................................... 378
Figure 48
Connection status in mcRNC........................................................... 379
Figure 49
IPA-RNC: Control Plane default profiles........................................... 379
Figure 50
mcRNC: Control Plane default profiles.............................................379
Figure 51
IPA-RNC: User Plane monitoring..................................................... 379
Figure 52
IMSI in TP profile for IPA-RNC......................................................... 380
Figure 53
IPA-RNC connected with CP profile, US UP profile, TP profile, and IMSI profile....................................................................................... 380
Figure 54
mcRNC connected with CP profile and IMSI profile......................... 380
Figure 55
Measuring RTT and PLR with TWAMP............................................ 384
Figure 56
Example of M2002 CPU Usage Core Level measurement from USPU0 unit.................................................................................................399
Figure 57
DSP load measurement before the feature activation......................402
Figure 58
DSP load measurement after the feature activation ........................403
Figure 59
M617C20 counter visible in GOMS.................................................. 408
Figure 60
mcRNC S7-B2 capacity step with full mesh cabling.........................410
Figure 61
Network resiliency transport network concept.................................. 416
BTS configuration after connecting the extension System Module FSME................................................................................................542
Figure 94
BTS configuration with connected extension System Module FSME without proper configuration............................................................. 543
Figure 95
WCDMA Carrier Candidates and Local Cell Group Settings............544
Figure 96
BTS configuration according to RAN2732........................................544
Figure 97
Sync Hub Direct forward chaining.................................................... 547
Figure 98
Sync Hub Direct Forward RF sharing...............................................548
DN09146788
21
RU50 Feature Descriptions and Instructions
List of Tables
22
Table 1
RU50 radio resource management features...................................... 31
Table 2
RU50 EP1 radio resource management features...............................32
Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.
g
The RU50 Feature Descriptions and Instructions document includes additional procedures that can be found under feature-specific “Testing” chapters. These procedures are intended for testing the feature functionality in the laboratory environment. The generic procedures that can be used in live network can be found under feature-specific “Verifying” chapters.
Changes between issues 01E (2015-02-20, RU50 and RU50 EP1) and 01F (2015-03-20, RU50 and RU50 EP1) Description of RAN147: RRC Connection Setup Redirection •
Management data has been updated.
Description of RAN3168: Flexi 3-sector RF Module 900 (FXJB) •
Functional description has been updated.
Changes between issues 01D (2014-11-28, RU50 and RU50 EP1) and 01E (2015-02-20, RU50 and RU50 EP1) New feature descriptions: •
BTS solution features –
Description of RAN2733: Flexi Multiradio System Module Extension, FSMF + FSMF
New test cases: •
BTS solution features –
Testing RAN2733: Flexi Multiradio System Module Extension, FSMF + FSMF
Other changes Testing RAN2578: AMR Codec Set for 2G-3G TrFO •
The instructions have been updated.
Description of RAN2443: BTS Resource Utilization Monitoring •
Management data has been updated.
Activating RAN2512: Network Resiliency for RNC2600 •
The instructions have been updated.
Operating and Maintaining RAN2512: Network Resiliency for RNC2600 •
The instructions have been updated.
Changes between issues 01C (2014-10-31, RU50 and RU50 EP1) and 01D (2014-11-28, RU50 and RU50 EP1) New feature descriptions:
28
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
•
Radio resource management features –
•
Summary of changes
RAN2221: HSPA+ Over Iur
BTS solution features – – – –
RG302084/RAN2556/LTE1556: 3-RAT RF Sharing 2G-3G and 2G-4G RAN2860/LTE1266: BTS and BTS Site Reset Support RAN3168: Flexi 3-sector RF Module 900 (FXJB) RG602339/RAN3001/LTE1710: Sync Hub Direct Forward
New feature activation instructions: •
Radio resource management features –
RAN2221: HSPA+ Over Iur
New test cases: •
Radio resource management features – – –
•
Transmission and transport features –
•
–
–
RAN2443: BTS Resource Utilization Monitoring RAN2555: Configurable Ranges for User Throughput Counters
RNC solution features – –
•
RAN2919: OMS Certificate Update and Revocation Support RAN2393: Optical Fiber: RX/TX Level Monitoring
Performance monitoring features –
•
RAN2913: Local and Remote IP Traffic Capturing
Operability features –
•
RAN2578: AMR Codec Set for 2G-3G TrFO RAN1905: DC-HSUPA RAN2221: HSPA+ Over Iur
RAN2928: DSP Pool Information in Measurements RAN2512: Network Resiliency for RNC2600
BTS solution features – – –
RAN3010: 24 Cell Support with Flexi FSMF + FSMD/E System Modules RAN2784: Flexi Lite BTS 1900 MHz RAN2732: Flexi System Module Extension, FSMF + FSMD/E
Removed features: •
RAN2826: Flexi Compact as RF Module
Other changes Description of RAN2963: Data Session Profiling
Issue: 01F
DN09146788
29
Summary of changes
RU50 Feature Descriptions and Instructions
• •
Functional description has been updated. Management data has been updated.
Description of RAN2211: Multi-Cell HSDPA (trial) •
Management data has been updated.
Description of RAN2443: BTS Resource Utilization Monitoring •
Management data has been updated.
Description of RAN2251: Automatic mcRNC Resource Optimization •
Description of RAN2512: Network Resiliency for RNC2600 •
All sections have been updated.
Activating RAN2512: Network Resiliency for RNC2600 •
30
All instructions have been updated.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Introduction to RU50 features
1 Introduction to RU50 features 1.1 RU50 radio resource management features See the following table for more detailed information on WCDMA RAN functions and feature activation: RU50 features Table 1
RU50 radio resource management features
Feature
Other related descriptions
Related instructions
RAN2963: Data Session Profiling
WCDMA RAN RRM Packet Scheduler
Activating RAN2963: Data Session Profiling
WCDMA RAN Packet Data Transfer States
RAN2179: Dual Band HSDPA 42 Mbps
WCDMA RAN HSDPA in BTS WCDMA RAN RRM Handover Control WCDMA RAN RRM HSDPA
Testing RAN2963: Data Session Profiling Activating RAN2179: Dual Band HSDPA 42 Mbps Testing RAN2179: Dual Band HSDPA 42 Mbps
WCDMA RAN RRM HSUPA RAN2482: Enhanced Virtual Antenna Mapping
This feature does not have any related descriptions.
Activating RAN2546: VHS Receiver for High Speed Train
Testing RAN1905: DC-HSUPA
Testing RAN2221: HSPA+ Over Iur
1.2 RU50 telecom features There are no RU50 features in the Telecom area.
32
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Introduction to RU50 features
RU50 EP1 features Table 3
RU50 EP1 Telecom features
Feature
Other related descriptions
Related instructions
RAN2211: Multi-Cell HSDPA (trial)
This feature does not have any related descriptions.
This feature does not have any related instructions.
1.3 RU50 transmission and transport features See the following table for more detailed information on WCDMA RAN functions and feature activation: RU50 features Table 4
RU50 transmission and transport features
Feature RAN2243: Performance Monitoring Based on ETH Service OAM
Other related descriptions WCDMA RAN IP Transport
Related instructions Activating RAN2243: Performance Monitoring Based on ETH Service OAM Testing RAN2243: Performance Monitoring Based on ETH Service OAM
RU50 EP1 features Table 5
RU50 EP1 transmission and transport features
Feature
Other related descriptions
Related instructions
RAN2913: Local and Remote IP Traffic Capturing
This feature does not have any related descriptions.
Activating RAN2913: Local and Remote IP Traffic Capturing Testing RAN2913: Local and Remote IP Traffic Capturing
1.4 RU50 operability features See the following tables for more detailed information on WCDMA RAN functions and feature activation: RU50 features
Issue: 01F
DN09146788
33
Introduction to RU50 features
Table 6
RU50 Feature Descriptions and Instructions
RU50 operability features
Feature
Other related descriptions
Related instructions
RAN2199: BTS Event Triggered Symptom Data Collection
This feature does not have any related descriptions.
Activating RAN2199: BTS Event Triggered Symptom Data Collection Testing RAN2199: BTS Event Triggered Symptom Data Collection
RAN2554: Transport Configuration Fall- This feature does not have any related back descriptions.
Activating RAN2554: Transport Configuration Fall-back Testing RAN2554: Transport Configuration Fall-back
RU50 EP1 features Table 7
RU50 EP1 operability features
Feature
Other related descriptions
Related instructions
RAN2919: OMS Certificate Update and This feature does not have any related Revocation Support descriptions.
Testing RAN2919: OMS Certificate Update and Revocation Support
RAN2699: OMS System Status View
This feature does not have any related descriptions.
Activating RAN2699: OMS System Status View
RAN2393: Optical Fiber: RX/TX Level Monitoring
This feature does not have any related descriptions.
This feature does not have any related descriptions.
This feature does not have related instructions.
RAN2507: RNW Plan Progress Indicator and Abort
This feature does not have any related descriptions.
This feature does not have related instructions.
RAN2229: Troubleshooting Data Management by NetAct
This feature does not have any related descriptions.
This feature does not have related instructions.
1.5 RU50 performance monitoring features There are no RU50 features in the performance monitoring area. See the following table for more detailed information on WCDMA RAN functions and feature activation: RU50 EP1 features
34
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 8
Introduction to RU50 features
RU50 EP1 performance monitoring features
Feature
Other related descriptions
Related instructions
RAN2496: 3GPP Minimization of Drive Tests
This feature does not have any related descriptions.
Activating RAN2496: Minimization of Drive Tests
RAN2443: BTS Resource Utilization Monitoring
This feature does not have any related descriptions.
Activating RAN2928: DSP Pool Information in Measurements Testing RAN2928: DSP Pool Information in Measurements
Issue: 01F
DN09146788
35
Introduction to RU50 features
Table 10
RU50 Feature Descriptions and Instructions
RU50 EP1 RNC solution features (Cont.)
Feature
Other related descriptions
Related instructions
RAN2959: mcRNC Step 7 Support
RAN2874: mcRNC HW Capacity Expansion Support
Activating RAN2591: Selective BTS Resource Re-Balancing in mcRNC
RAN2512: Network Resiliency for RNC2600
This feature does not have related descriptions.
Activating RAN2512: Network Resiliency for RNC2600. Testing RAN2512: Network Resiliency for RNC2600
RAN2671: Upgrading of mcBSC to mcRNC
RAN2874: mcRNC HW Capacity Expansion Support
Clean installation
RAN2959: mcRNC Step 7 Support
1.7 RU50 BTS solution features See the following tables for more detailed information on WCDMA RAN functions and feature activation: RU50 features Table 11
Other related descriptions This feature does not have any related descriptions.
Related instructions Activating RAN3017: Additional 6 WCDMA Cell Activation
RU50 EP1 features Table 12
RU50 EP1 BTS solution features
Feature
Other related descriptions
Related instructions
RG302084/RAN2556/LTE1556: 3-RAT RF Sharing 2G-3G and 2G-4G
RF Sharing Operability
This information will be provided in further deliveries.
RAN3010: 24 Cell Support with Flexi FSMF + FSMD/E System Modules
This feature does not have related descriptions.
Activating RAN3010: 24 cell support with Flexi FSMF + FSMD/E System Modules Testing RAN3010: 24 cell support with Flexi FSMF + FSMD/E System Modules
RAN2860: BTS and BTS Site Reset Support
36
This feature does not have related descriptions.
DN09146788
This information will be provided in further deliveries.
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 12
Introduction to RU50 features
RU50 EP1 BTS solution features (Cont.)
Feature
Other related descriptions
Related instructions
RAN3168: Flexi 3-sector RF Module 900 (FXJB)
Flexi Multiradio BTS Radio Module and Remote Radio Head Description
This feature does not have related instructions.
RAN2784: Flexi Lite BTS 1900 MHz
Flexi Lite BTS Product Description
Testing RAN2733: Flexi Multiradio System Module extension, FSMF + FSMF
RAN2733: Flexi Multiradio System Module extension, FSMF + FSMF
Multiradio 10 Base Station System Module Description
Testing RAN2733: Flexi Multiradio System Module extension, FSMF + FSMF Cabling Flexi Multiradio 10 Base Station
RAN2998: Flexi RRH 2TX 2100 (FRGY)
Flexi Multiradio BTS Radio Module and Remote Radio Head Description
Installing Flexi Multiradio BTS WCDMA Modules for Stack, Wall, and Pole Configurations
RAN2732: Flexi System Module Extension, FSMF + FSMD/E
Flexi Multiradio 10 Base Station System Module Description
Testing RAN2733: Flexi Multiradio System Module extension, FSMF + FSMF
Flexi Multiradio BTS WCDMA System Module Description RAN3001: Sync Hub Direct Forward
This feature does not have related descriptions.
This information will be provided in further deliveries.
1.8 Licensing The application software features (ASW) are under license key management. A license is a file that includes the feature information. Before a licensed feature can be activated, the license file needs to be transferred to and installed in the RNC. For information on transferring the license, see License management operations in RNC in WCDMA RAN License Operation. For information on installing the license, see Installing licenses in the network element in Managing License-based Features in IPA-RNC and Managing License-based Features in Multicontroller RNC.
g g
Some RNC-controlled features are activated using an RNC general parameter file (PRFILE) or a feature information control file (FIFILE). For details, see Parameter-based option management in WCDMA RAN License Operation. There are no licenses in the Flexi Direct RNC. A license can be installed using NetAct or a local MML (IPA-RNC) or SCLI (mcRNC) interface. If it is installed using NetAct, the licensed feature state is automatically set to ON state. If the MML/SCLI interface is used, the default value is OFF, and you need to set the feature to ON state manually. For information on feature states, see Feature States in WCDMA RAN License Operation. The license-related MML commands are described in W7 - License and Feature Handling.
Issue: 01F
DN09146788
37
Introduction to RU50 features
RU50 Feature Descriptions and Instructions
License management in mcRNC For details on the mcRNC-specific license management, see License management in RNC in WCDMA RAN License Operation and Managing License-based Features in Multicontroller RNC.
License management in WBTS License management in WBTS is based on a pool concept. Each license contains a specific amount of capacity that can be distributed among the selected WBTSs. Distributing licenses from the pool license decreases the amount of free capacity in the pool. Managing pool licenses and distributing to WBTSs is done via NetAct Licence Manager. Some basic license operations (for example, license installation or deletion) are also possible with BTS Site Manager. For details on the WBTS-specific license management, see License management in WBTS in WCDMA RAN License Operation.
1.9 Reference documentation For information on the parameters, counters and alarms related to each feature, see the Management data section of the feature descriptions. For parameter descriptions, see: • • • • • • • • • • •
WCDMA Radio Network Configuration Parameters IP Configuration Plan Interface Parameters for Multicontroller RNC OMS LDAP Parameters Flexi Transport Module Parameters Flexi Multiradio BTS WCDMA Parameters Multicontroller Radio Network Configuration Parameters ATM Configuration Plan Interface Parameters Frequently Used Parameters for SS7 Signalling over IP IP Configuration Plan Interface Parameters for Flexi Direct RNC Radio Network Parameters in Flexi Direct Reference Information Service in NOLS for RNC parameters
For counter descriptions, see: • • • • •
RNC Counters - RNW Part RNC Counters – Transport and HW Part WBTS Counters Flexi Lite BTS Counters Reference Information Service in NOLS
Multicontroller RNC, IPA-RNC and Flexi Direct RNC Base Station Alarms (70009000) Flexi WCDMA Base Station Faults Flexi Lite BTS Faults mcRNC Alarms OMS Alarms
For key performance indicator descriptions, see: •
Issue: 01F
WCDMA RAN Key Performance Indicators
DN09146788
39
Radio resource management features
RU50 Feature Descriptions and Instructions
2 Radio resource management features 2.1 RAN2578: AMR Codec Set for 2G-3G TrFO 2.1.1 Description of RAN2578: AMR Codec Set for 2G-3G TrFO Introduction to the feature In addition to existing AMR codec mode sets (12.2), (12.2, 7.95, 5.9, 4.75) and (5.9, 4.75), AMR codec mode set (12.2, 7.4, 5.9, 4.75) shall be supported for enhancing TrFO call quality between 2G and 3G. AMR codec mode set (12.2, 7.4, 5.9, 4.75) is also supported between 3G calls.
2.1.1.1
Benefits End-user benefits Transcoder free operation and GSM half rate can be used simultaneously in 2G-3G calls.
Operator benefits In case of GSM the preferred AMR half rate codec mode is 7.4 kbps. Adding it to the existing codec rates in 3G enables 2G-3G TrFO calls, where the preferred AMR half rate codec mode can be used. This enhances the voice quality if half-rate needs to be used on GSM side. Otherwise only the lower modes 5.9 kbps or 4.75 kbps would need to be used in TrFO calls.
2.1.1.2
Requirements Software requirements Table 13: Software requirements lists the software required for this feature. Table 13
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
OMS
BTS Flexi
Flexi Lite
RU50 EP1
Not planned RN8.1
mcRNC4.1
OMS3.1
WN9.1
WL9.1
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
WN9.1
NetAct 8 EP2 (NetAct 15)
M13.6
Support not required
U3C
Support not required
Hardware requirements This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF or Flexi Lite BTS WCDMA.
40
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
2.1.1.3
Radio resource management features
Functional description Functional overview Narrowband AMR codec mode set (12.2, 7.4, 5.9, 4.75) is added among the other supported Narrowband AMR codec mode sets, which can be selected by the operator to be in use. This is controlled by a cell based radio network configuration parameter controlling also the usage of the other AMR codec mode sets. AMR codec mode set (12.2, 7.4, 5.9, 4.75) is added as a new supported set. It does not replace any existing AMR codec mode set. The new codec mode set is used when Core Network asks it to be used, mainly in case of 2G-3G TrFO calls. The new codec mode set can be used also between 3G – 3G calls, based on Core Network request. The AMR codec mode set (12.2, 7.4, 5.9, 4.75) can be determined to be applied in CS AMR call setup, in SRNC relocation UE involved (Hard Handover), in SRNC relocation UE not involved and in Inter-RAT handover (from 2G to 3G). The AMR codec mode set (12.2, 7.4, 5.9, 4.75) is supported over Iur in mobility cases i.e. branch addition to DRNC and in anchoring cases. The AMR codec mode set (12.2, 7.4, 5.9, 4.75) is applied in Load Based AMR codec mode selection for low loaded cells. The deployment to network requires Core Network support, RNC support and also BTS support to 7.4 kbps codec mode (preferably in all BTSs under one RNC).
2.1.1.4
System impact Interdependencies between features The RAN830: AMR Codec Sets (12.2, 7.95, 5.90, 4.75) and (5.90, 4.75) feature is required.
Impact on interfaces There are no impact on interfaces.
Impact on commands There are no commands related to this feature.
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.
2.1.1.5
RAN2578: AMR Codec Set for 2G-3G TrFO management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Issue: 01F
DN09146788
41
Radio resource management features
RU50 Feature Descriptions and Instructions
Alarms There are no alarms related to this feature.
Measurements and counters Table 14: New counters lists counters introduced with this feature. Table 14
New counters
Counter ID
Counter name
Measurement
M1002C694
AMR CODEC SET (12.2, 7.4, 5.9, 4.75) ALLOCATION
M1002 Traffic
M1004C175
AMR CODEC SET (12.2, 7.4, 5.9, 4.75) IUR FAIL
M1004 L3 signalling at IuR
M1006C316
AMR CODEC SET (12.2, 7.4, 5.9, 4.75) UE M1006 RRC signalling FAIL
Related existing counters There are no existing counters related to this feature.
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table 15: New parameters lists parameters introduced with this feature. Table 15
New parameters
Full name
Abbreviated name
Managed object
AMR codec mode set 7.4 enabled
AMRCodecSet74Enabled
RNFC
AMR codec mode set enabled
AMRCodecSetEnabled
RNFC
WB AMR codec mode set enabled
WBAMRCodecSetEnabled
RNFC
Table 16: Modified parameters lists parameters modified by this feature. Table 16
42
Modified parameters
Full name
Abbreviated name
Managed object
RNC Options
RncOptions
RNC
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 16
2.1.1.6
Radio resource management features
Modified parameters (Cont.)
Full name
Abbreviated name
Managed object
Configured CS AMR mode sets
CSAMRModeSET
VCEL
Configured CS AMR mode sets
CSAMRModeSET
WCEL
Configured CS WBAMR mode sets
CSAMRModeSETWB
VCEL
Configured CS WBAMR mode sets
CSAMRModeSETWB
WCEL
Sales information Table 17
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
RNC LK
2.1.2 Activating RAN2578: AMR Codec Set for 2G-3G TrFO Purpose Follow this procedure to activate the RAN2578: AMR Codec Set for 2G-3G TrFO feature. Before you start The RAN830: AMR Codec Sets (12.2, 7.95, 5.90, 4.75) and (5.90, 4.75) feature need to be activated. For more information, see RAN830: Activating AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and (5.9, 4.75)
g
If the RAN830: AMR Codec Sets (12.2, 7.95, 5.90, 4.75) and (5.90, 4.75) feature is not activated then the CSAMRModeSET parameter cannot be set as True for (12.2, 7.4, 5.9, 4.75) and the (12.2, 7.4, 5.9, 4.75) cannot be used for CS AMR call. Restart of RNC is not required after the activation of this feature. This procedure does not cause downtime and can be activated at any time of the day. Make sure you have an access to the following applications: • • •
OMS Element Manager Application Launcher Man-machine interface (MMI)
Make sure that BTS supports the RAN2578: AMR Codec Set for 2G-3G TrFO feature, preferably in all BTSs under one RNC. BTS products supporting AMR codec mode 7.4 are Flexi System Module release 2 outdoor and release 3 (FSMr2, FSMr3).
g
Issue: 01F
The FSMr2 indoors BTS does not support the AMR Codec Set for 2G-3G TrFO/7.4 codec mode functionality.
DN09146788
43
Radio resource management features
RU50 Feature Descriptions and Instructions
Configure MSS to enable the Active Codec Set (ACS) so that AMR becomes '(12.2, 7.4, 5.9, 4.75)' for the resource allocation from the Radio Network Subsystem (RNS) with RAB Assignment or Relocation Request. This feature is controlled by the long-term ON/OFF license key. For more information on licensing, see Licensing.
g
The feature code for this feature is 5248. To set the feature state to ON, use the following command:
•
for IPA-RNC: ZW7M:FEA=5248:ON; for mcRNC: set license feature-mgmt code 0000005248 feature-admin-state on
1
Open OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object and then the WBTS object.
4
Configure the WCEL object.
•
a) Right-click on the WCEL object and select Edit parameters. b) On Admission Control tab, find CSAMRModeSET parameter. c) Under CSAMRModeSET parameter, set the value of CS AMR codec mode set (12.2, 7.4, 5.9, 4.75) to True
g
Preferably configure the AMR codec mode set (12.2, 7.4, 5.9, 4.75) to all cells under the RNC. 5
Expand the RNC object and configure the RNFC object. a) Right-click on the RNFC object and select Edit parameters. b) On Admission control tab set the value of AMRCodecSet74Enabled to Enabled.
2.1.3 Verifying RAN2578: AMR Codec Set for 2G-3G TrFO Purpose Follow this procedure to verify if this RAN2578: AMR Codec Set for 2G-3G TrFO feature works properly in the network. Before you start Make sure you have an access to the following applications:
Configure MSS to enable the Active Codec Set (ACS) so that AMR becomes '(12.2, 7.4, 5.9, 4.75)' for the resource allocation from the Radio Network Subsystem (RNS) with RAB Assignment or Relocation Request.
g
When the AMRCodecSetEnabled and AMRCodecSet74Enabled parameters are both set to the value Enabled, then RNC is able to establish the call at least with the codec sets (12.2), (12.2, 7.95, 5.9, 4.75), and (12.2, 7.4, 5.9, 4.75) regardless of the value of the CSAMRCodecSet management parameter, if the three codec sets are exactly the ones which MSS is allowed to use in the AMR call assignments. Especially, MSS shall not use other multi mode codec set in the AMR call assignments if the PeriodULRCAMR parameter's value is other than 255, indicating that the support of the TFO/TrFO calls is enabled in RNC.
1
Open the RNW Measurement Management application.
2
Activate the 1002 Traffic measurement in the RNW and BTS measurements window. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management application in Managing and viewing RNC measurements.
3
Make a CS AMR call.
4
Open the RNW Measurement Presentation application.
5
Check if the value of the M1002C694: AMR CODEC SET (12.2, 7.4, 5.9, 4.75) ALLOCATION counter increased over time. The value of the M1002C694: AMR CODEC SET (12.2, 7.4, 5.9, 4.75) ALLOCATION counter represents the number of successful allocations of AMR codec mode set (12.2, 7.4, 5.9, 4.75). For details on using the RNW Measurement Presentation application, see Radio Network Measurement Presentation in Managing and viewing RNC measurements.
Expected outcome Value of the M1002C694: AMR CODEC SET (12.2, 7.4, 5.9, 4.75) ALLOCATION counter is increased. Unexpected outcome Value of the M1002C694: AMR CODEC SET (12.2, 7.4, 5.9, 4.75) ALLOCATION counter isn't increased.
Issue: 01F
DN09146788
45
Radio resource management features
g
• • • •
RU50 Feature Descriptions and Instructions
Check the configuration of the CSAMRModeSET (WCEL) parameter, licenses, Alarms and Notifications. Ensure that BTS products support AMR codec mode 7.4 (FSMr2, FSMr3). Check the CN configuration. For example, 7.4 is included to RAB Assignment Request from CN to RNC. Check the M1006C316: AMR CODEC SET (12.2, 7.4, 5.9, 4.75) UE FAIL counter for number of setup or reconfiguration failures due to UE.
Further information It is possible to verify the RAN2578: AMR Codec Set for 2G-3G TrFO feature using Core Network. For example check the allocated AMR codec mode set for CS AMR call.
2.1.4 Deactivating RAN2578: AMR Codec Set for 2G-3G TrFO Purpose Follow this procedure to deactivate this feature.
1
Configure the MSS so that it does not use the codec set (12.2, 7.4, 5.9, 4.75) in the RAB assignment or Relocation Request.
2
Open OMS Element Manager.
3
Go to Topology and expand the ROOT directory.
4
Expand the RNC object.
5
Configure the RNFC object. a) Right-click on the RNFC object and select Edit parameters. b) On Admission control tab, set the value of AMRCodecSet74Enabled to Disabled
Expected outcome Value of the M1002C694: AMR CODEC SET (12.2, 7.4, 5.9, 4.75) ALLOCATION counter is not updated when making CS AMR call. Unexpected outcome The AMR codec mode set (12.2, 7.4, 5.9, 4.75) is used when setting up CS AMR call.
2.1.5 Testing RAN2578: AMR Codec Set for 2G-3G TrFO Purpose
g
46
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.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
The purpose of this test case is to verify that the feature was activated successfully and that basic calls are working correctly. This test case verifies voice quality and signaling in the following scenarios: • •
mobility between 3G and 2G, AMR codec set (12.2, 7.4, 5.9, 4.75) in BSC and RNC 2G to 3G ISHO with HR AMR, HR supported only in 2G
Test environment For the test case, the following network elements must be at least on the following software level: • • • • • • • • •
one RNC two N-BTS one MGW one MSC/MSS one SGSN one GGSN one Netact one GOMS 6 3G UE 2 R99/1 R5/1 R6/2 R7
Figure 1
ISHO between 3G and 2G.
BS SA
NB AMRcodecset 12.27.45.94.75
P
Iu
Mc
SA BS
NB AMRcodecset 12.27.45.94.75
P
MSS
CP
IuUP
UE
mcRNC
AoIP
MGW Iu
NB AMR UDP IP
NB AMR UDP IP
BSC
UE
RNC
UE
UP
NB AMRcodecset 12.27.45.94.75
TrFO
Issue: 01F
DN09146788
47
Radio resource management features
Figure 2
RU50 Feature Descriptions and Instructions
2G to 3G ISHO with HR AMR, HR supported only in 2G.
Before you start The following features need to be enabled: • • •
RAN2578 : AMR Codec Set for 2G-3G TrFO RAN830 : AMR Codec Sets (12.2, 7.95, 5.90, 4.75) and (5.90, 4.75) O&M connection between RNC and OMS is working
Configure the listed parameters in the following way: •
set the values of the following RNFC parameters: – –
•
set the values of the following RNAC: Admission control parameters: – – – –
•
PeriodULRCAMR to 10 s (IuUP =2) LoadBasedAMRCodecMode to Enabled DLPuncturingLimit to 0.60 DLmaxBitRateSF256 to 35 kbps
set the values of the following WBTS: WCEL: Load Control parameters: –
•
AMRCodecSet74Enabled to Enabled AMRCodecSetEnabled to Enabled
PtxTarget to 40db
set the values of the following WBTS: WCEL: Admission Control parameter: –
CSAMRmodeSET (12.2, 7.4, 5.9, 4.75) to True
Other network element parameter configuration:
48
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
•
• •
1
Radio resource management features
Configure the MSS so that the Active Codec Set (ACS) of the AMR becomes '(12.2, 7.4, 5.9, 4.75)' for the resource allocation from the Radio Network Subsystem (RNS) with RAB Assignment or Relocation Request. Note that if the TFO/TrFO is activated in the MSS and in the MGW, the TFO/TrFO support needs to be enabled in the WCDMA RAN as well. If the MSS is configured to initiate TFO/TrFO calls, check the value of the PeriodULRCAMR parameter to see if the TFO/TrFO is in use or not in the RNC. If the MSS is not configured to initiate TFO/TrFO calls, the value of the PeriodULRCAMR parameter does not need to be checked.
Set up an UE (using 3G) to UE (using 2G) NB AMR call. a) Verify that CN sends RAB Assignment to RNC with AMR codec set (12.2, 7.4, 5.90, 4.75) and the IUUP support mode version 2 is indicated. b) Verify that in the RANAP:RAB-AssignmentRequest message, 7.4 AMR codec mode’s sub-flow combination is list as 61, 87, 0. c) Verify that AMR call is setup on DCH, and both the IU UP codec set and the RL AMR codec set are (12.2, 7.4, 5.90, 4.75).
2
Move one UE from 2G to 3G to keep the peer end UE stationary. a) Check that the AMR codec set 12.2, 7.4, 5.9, 4.75 allocation in ISHO from 2G to 3G is verified. After successful ISHO the transport channel expect to be reconfigured for AMR codec mode set (12.2, 7.4, 5.9, 4.75) b) In case of HR in 2G, the AMR codec set 12.2, 7.4, 5.9, 4.75 is allocated and configured, but 7.4 codec is selected and configured to UE and BTS directly. c) When AMR codec mode set (12.2, 7.4, 5.9, 4.75) is selected to be used, in configuring the TFS the following parameters shall be used: Table 18
Issue: 01F
Parameters
AMR mode
Sub-flow SDU size / TB size (bits)
Sub-flow SDU size / TB size (bits)
Sub-flow SDU size / TB size (bits)
4.75
42
53
0
5.9
55
63
0
7.4
61
87
0
12.2
81
103
60
AMR SID
39
0
0
DN09146788
49
Radio resource management features
RU50 Feature Descriptions and Instructions
d) Verify that the TrFO is active and Iu interface codec NB AMR 12.2 ingress/egress rate is used in both MGW termination printouts (ZJKE, ZJKF, ZJKH). e) In case of HR verify that the TrFO is active and Iu interface codec NB AMR 7.4 ingress/egress rate is used in both MGW termination printouts (ZJKE, ZJKF, ZJKH). f)
3
Check the audio path and voice quality during ISHO.
Release call of UE1.
Expected outcome • • • • • •
TrFO is used end to end. Voice quality is as expected during call. No alarms have been issued by RNC or BTS as a result of test case execution(s). All resources set up during the test case execution(s) has/have been released. It is possible to set up new calls after the test case executions(s). Check Counters.
Table 19
50
Counters
Counter ID
Counter name
Description
M1002C694
AMR CODEC SET (12.2, 7.4, 5.9, 4.75) ALLOCATION
It shows the number of successful allocations of AMR codec mode set {12.2, 7.4, 5.9, 4.75}. The counter is updated by the Controlling-RNC of the cell. The same counter is used both in SRNC and DRNC role.
M1004C175
AMR CODEC SET (12.2, 7.4, 5.9, 4.75) IUR FAIL
The number of failures to setup or reconfigure Iur SHO branch to use AMR codec mode set {12.2, 7.4, 5.9, 4.75} The counter is updated when the SRNC receives RNSAP: Radio Link Setup Failure or RNSAP: Radio Link Reconfiguration Failure from DRNC when attempting to setup or reconfigure Iur branch to use AMR codec mode set {12.2, 7.4, 5.9, 4.75}.
M1006C316
AMR CODEC SET (12.2, 7.4, 5.9, 4.75) UE FAIL
It shows the number of AMR codec mode set {12.2, 7.4, 5.9, 4.75} setups or reconfigurations failed due to UE. The counter is updated when the RNC receives negative RRC protocol response from the UE, or the UE does not respond at all, when trying to setup or reconfigure AMR codec mode set {12.2, 7.4, 5.9, 4.75} into use.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Use the counter M1002C694: Number of successful allocations of AMR codec mode set (12.2, 7.4, 5.9, 4.75) to check that the CS AMR call using AMR codec mode set (12.2, 7.4, 5.9, 4.75) is setup. It is expected that the value of the M1002C694: Number of successful allocations of AMR codec mode set (12.2, 7.4, 5.9, 4.75) counter are increased. In case of UE failure to set codec mode set (12.2, 7.4, 5.9, 4.75) this counter is increased: M1006C316. Unexpected outcome •
In case of UE failure to set codec mode set (12.2, 7.4, 5.9, 4.75) this counter is increased: M1006C316.
2.2 RAN3018: BTS Load Based AACR 2.2.1 Description of RAN3018: BTS Load Based AACR Introduction to the feature In the current system implementation, BTS overload does not trigger access class restriction provided by the RAN2480: Automatic Access Class Restriction (AACR) feature. AACR is used to temporarily prevent network access for UEs with defined access class that is SIM-specific random number (0,1,…9). The RNC controls the limitation level dynamically based on the network load. The RAN3018: BTS Load Based AACR feature triggers the AACR when the BTS is in the processing overload due to congestion of RL procedures.
2.2.1.1
Benefits End-user benefits This feature provides smooth recovery to the normal system state when there is a BTS overload. Under overload conditions, this feature allows more subscribers to be served, even if some users are temporarily restricted.
Operator benefits This feature provides smooth recovery from high BTS control plane processing overload.
2.2.1.2
Requirements Software requirements Table 20: Software requirements lists the software required for this feature. Table 20
Issue: 01F
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
Flexi BTS
RU50 EP1
Not planned RN8.1
mcRNC4.1
Not planned OMS3.1
WN9.1
DN09146788
51
Radio resource management features
Flexi Lite BTS
Flexi 10 BTS
Not planned WN9.1
RU50 Feature Descriptions and Instructions
NetAct
MSC
SGSN
MGW
NetAct 8 Support not Support not Support not EP2 required required required (NetAct 15)
UE
Support not required
Hardware requirements This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF.
2.2.1.3
Functional description This feature helps the BTS to recover from the network overload conditions by triggering the Automatic Access Class Restriction (AACR), provided by the RAN2480: Automatic Access Class Restriction feature, when the BTS processing load is high. The RAN3018: BTS Load Based AACR feature provides: • • •
overload protection for the BTSs based on the new and improved BTS notification about BTS processing load the ability to set NBAP signaling/BTS processing load as a trigger for AACR a possiblity to restrict Cell_PCH to Cell_FACH/Cell_DCH state transitions in a cell due to high AACR level in the cell (AACR triggered by the RAN2480: Automatic Access Class Restriction feature or the RAN3018: BTS Load Based AACR feature)
The BTS's capacity for handling NBAP signaling is limited. The NBAP entity in the RNCcontinuously follows the number of simultaneously ongoing NBAP signaling procedures towards the BTS. In current system implementation, when the number of parallel NBAP procedures iets too high, the system limits the amount of incoming RRC Connection Requests and Radio Link Setup procedures towards the loaded BTS. When the RAN3018: BTS Load Based AACR feature is activated, the RNC starts the automatic access class restriction procedure in the cells of the loaded BTS based on the information from the BTS overload protection procedure. With the access class restriction procedure the BTS and the RNC can be protected, as the UEs are temporarily banned from entering the network. This is done by sending the access class barred list in system information block 3 (SIB3). The restriction actions introduced with the RAN3018: BTS Load Based AACR feature start once the RNC detects that the BTS cannot handle all the requests. If the NBAP signaling overload continues long enough, AACR-based restriction is started. Level of AACR restriction is then updated dynamically according to detected NBAP signaling load. When the AACR level in the cell exceeds the threshold AACR level defined by the AutoACResFromCellPCH parameter, the RNC limits the number of Cell_PCH to Cell_DCH state transitions in the cell in the following way: • •
52
a number of UEs is moved to IDLE state instead of Cell_PCH to Cell_DCH state transition a number of UEs is kept in Cell_PCH state
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
The selection of the UEs is based on the restricted access classes in the cell at that moment and the regulation action depends on how long the access class of the UE is assumed to be restricted.
2.2.1.4
System impact Interdependencies between features This feature requires the RAN2480: Automatic Access Class Restriction feature.
Impact on interfaces This feature has no impact on interfaces.
Impact on commands There are no commands related to this feature.
Impact on network and network element management tools This feature has no impact on network management or network element management tools.
Impact on system performance and capacity This feature provides smooth recovery from BTS overload.
2.2.1.5
RAN3018: BTS Load Based AACR management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms There are no alarms related to this feature.
Measurements and counters Table 21: New counters lists counters introduced with this feature. Table 21
Issue: 01F
New counters
Counter ID
Counter name
Measurement
M1000C408
ACCESS CLASS RESTRICTION ACTIVE BTS SAMPLES
Cell Resource
M1005C255
RL SETUP REJECT DUE TO OVERLOAD
L3 signalling at Iub
M1005C256
RL ADDITION REJECT DUE TO OVERLOAD
L3 signalling at Iub
M1005C257
RL RECONFIGURATION REJECT DUE TO OVERLOAD
L3 signalling at Iub
M1005C258
RL SETUP FAIL DUE TO BTS OVERLOAD
L3 signalling at Iub
DN09146788
53
Radio resource management features
RU50 Feature Descriptions and Instructions
Table 22: Related counters lists counters related to this feature. Table 22
Related counters
Counter ID
Counter name
Measurement
M1000C404
ACCESS CLASS RESTRICTION ACTIVE SAMPLES
Cell Resource
M1000C405
ACCESS CLASSES BLOCKED AMOUNT
Cell Resource
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table 23: New parameters lists parameters introduced with this feature. Table 23
New parameters
Full name
Abbreviated name
Managed object
Automatic Access Class Restriction based on BTS load Enabled
AutoACResBTSEnabled
RNFC
BTS load indication selection
BTSLoadIndSel
RNFC
Access Class Restriction for UEs transferring from Cell_PCH state to Cell_FACH/Cell_DCH
AutoACResFromCellPCH
RNAC
Table 24: Modified parameters lists parameters modified by this feature. Table 24
54
Modified parameters
Full name
Abbreviated name
Managed object
RNC Options
RncOptions
RNC
Automatic Access Class Restriction Enabled
AutoACResEnabled
RNFC
Automatic Access Class Restriction Trigger of RNC Load
AutoACRTrigRNCLoad
RNAC
Access Restriction for Cell_PCH state UE
AutoACRestForCellPCH
RNAC
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 24
2.2.1.6
Radio resource management features
Modified parameters (Cont.)
Full name
Abbreviated name
Managed object
Access class restriction guard time
RNARDSACGuardTime
RNAC
Sales information Table 25
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
RNC LK
2.2.2 Activating RAN3018: BTS Load Based AACR Purpose Follow this procedure to activate the RAN3018: BTS Load Based AACR 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. Install the license key for the RAN2480: Automatic Access Class Restriction feature in the RNC and set the feature state to ON. For instructions, see Activating RAN2480: Automatic Access Class Restriction Activate the license of the RAN3018: BTS Load Based AACR feature using BTS load Access Class Restriction license key. To set the feature state to ON, use the following command: • •
for IPA-RNC: ZW7M:FEA=5170:ON; for mcRNC: set license feature-mgmt code 0000005170 feature-admin-state on
For information on managing licenses, see Licensing.
Issue: 01F
DN09146788
55
Radio resource management features
RU50 Feature Descriptions and Instructions
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: a) Right-click on the RNFC object and select Edit parameters. b) On the Load Control tab, set the value of the BTSLoadIndSel parameter to Private cause code is used. c) On the General tab, set the value of the AutoACResBTSEnabled parameter to Enabled.
Further information With the AutoACResFromCellPCH RNAC parameter state change from Cell_PCH to Cell_FACH/Cell_DCH can be prevented. With the AutoACMaxRestLevel RNAC parameter the maximum number of Access Classes that are allowed in a cell at the same time can be defined.
2.2.3 Verifying RAN3018: BTS Load Based AACR Purpose Follow this procedure to verify that the RAN3018: BTS Load Based AACR feature works properly in the network. Before you start Make sure you have access to the following applications: • •
Generate NBAP overload or wait for a situation in which the Iub transport or BTS cannot process all needed NBAP signaling. NBAP overload can be detected from the following counters that indicate NBAP radio link rejections in RNC resulting from active BTS overload protection in the RNC: • • •
M1005C255 RL SETUP REJECT DUE TO OVERLOAD M1005C256 RL ADDITION REJECT DUE TO OVERLOAD M1005C257 RL RECONFIGURATION REJECT DUE TO OVERLOAD
NBAP overload can also be detected by checking the "NBAP overload" information element in NBAP RADIO LINK SETUP FAILURE message using the M1005C258 RL SETUP FAIL DUE TO BTS OVERLOAD counter. However, this counter is only updated if the BTS is capable of sending this indication.
56
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Radio resource management features
To trigger the RAN3018: BTS Load Based AACR feature, the overload situation has to last for more than one minute. 2
Open the RNW Measurement Management application.
3
Start the measurements for the M1000C408 ACCESS CLASS RESTRICTION ACTIVE BTS SAMPLES counter. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Application in Managing and viewing RNC measurements.
4
Open the RNW Measurement Presentation application.
5
Check if the value of the M1000C408 ACCESS CLASS RESTRICTION ACTIVE BTS SAMPLES counter increased over time. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentation in Managing and viewing RNC measurements.
g g
Automatic Access Class Restriction can also be triggered by reasons other than BTS overload. In that case the highest AACR level of all active triggers is used. Therefore the M1000C408 counter does not indicate that the final access class restriction decision was done based only on BTS overload. Emergency calls are not restricted during the BTS overload.
2.2.4 Deactivating RAN3018: BTS Load Based AACR Purpose Follow this procedure to deactivate the RAN3018: BTS Load Based AACR feature.
Issue: 01F
DN09146788
57
Radio resource management features
RU50 Feature Descriptions and Instructions
1
Open the OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object and then expand the RNFC object.
4
Configure the RNFC object: a) Right-click on the RNFC object and select Edit parameters. b) On the Load Control tab, set the value of the BTSLoadIndSel parameter to 0 (3GPP cause code is used). c) On the General tab, set the value of the AutoACResBTSEnabled parameter to 0 (Disabled).
2.3 RAN2963: Data Session Profiling 2.3.1 Description of RAN2963: Data Session Profiling Introduction to the feature The RAN2963: Data Session Profiling feature provides faster web-browsing sessions for the end-user.
2.3.1.1
Benefits End-user benefits The RAN2963: Data Session Profiling feature improves end-user experience for data traffic, reducing the webpage loading time by up to 10%.
Operator benefits The RAN2963: Data Session Profiling feature provides: • • •
2.3.1.2
more resources for data traffic by moving the small keep-alive messages to common channels improved HSPA efficency by using shorter Cell_DCH inactivity timers resulting in faster direct Cell_PCH to Cell_DCH allocation reduced state transition from Cell_PCH to Cell_DCH by up to one second by skipping Cell_FACH state when UE is sending/receiving large amounts of data in a short time period
Requirements Software requirements Table 26: Software requirements lists the software required for this feature.
58
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 26
Radio resource management features
Software requirements
RAS
Flexi Direct
IPA-RNC
mcRNC
Flexi Direct RNC
OMS
BTS Flexi
RU50
Flexi Direct RU50
RN8.0
mcRNC4.1
ADA6.0
OMS3.0 1)
Support not required
OMS3.1 2) IHO 6.0 3)
Flexi Lite BTS
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
Support not required
Support not required
NetAct 8 EP1 1)
Support not required
Support not required
Support not required
Support not required
NetAct 8 EP2 (NetAct 15) 2) 3)
1) for RU50 2) for RU50 EP1 3) for Flexi Direct RU50
Hardware requirements This feature requires no new or additional hardware.
2.3.1.3
Functional description Functional overview The RAN2963: Data Session Profiling feature enables profiling of web-browising users and moving them directly from Cell_PCH to Cell_DCH state, saving up to one second. The fast state change is performed both for sending and receiving data. The user is identified as a Large Data Session user when the data amount in the session exceeds the threshold defined with the LargeDataThr parameter. A Large Data Session user is moved directly to Cell_DCH state, regardless of the amount of data in the buffer (even if buffered data is lower than the value defined with the TrafVolThresholdULLow WAC parameter), but only when the Large Data Time timer (defined with the LargeDataTime parameter) is not expired. The Large Data Time timer is started when the user is identified as Large Data Session user. The Figure 3: Logic of Cell_PCH to Cell_DCH/Cell_FACH state change illustrates how the RAN2963: Data Session Profiling feature impacts the user session.
Issue: 01F
DN09146788
59
Radio resource management features
Figure 3
RU50 Feature Descriptions and Instructions
Logic of Cell_PCH to Cell_DCH/Cell_FACH state change
When UE in Cell_PCH or URA_PCH state starts the next data session by sending the RRC: CELL UPDATE message with uplink data transmission cell update cause and the Large Data Time timer is not exceeded, UE is moved directly to Cell_DCH state with the RRC: CELL UPDATE CONFIRM message. When the RRC: RADIO BEARER RECONFIGURATION COMPLETE message is received from UE, RNC updates the M1006C309: SUCCESSFUL PCH TO DCH TRANS DUE TO DATA SESSION PROFILING counter, provided that the Traffic Volume Indicator is not set as True in RRC: CELL UPDATE message sent by UE. The threshold amount of data for defining Large Data Session users (LargeDataThr) and the Large Data Time timer (LargeDataTime) are both controlled by operatortunable parameters.
60
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
If UE is capable of using HS-RACH, either a direct transfer to Cell_DCH state or using HS-RACH/FACH channels in Cell_FACH state can be preffered. The preferences are defined with the HSChaPrefInDataSesProf RNPS parameter.
2.3.1.4
System impact Interdependencies between features •
•
RAN1913: High Speed Cell_FACH This feature enables special handling of HS-RACH-capable UEs, depending on the value of the HSChaPrefInDataSesProf parameter. RAN2494: Fast Cell_PCH Switching This feature is recommended to be used with the RAN2963: Data Session Profiling feature in order to achieve faster transitions to aCell_DCH state.
Impact on interfaces This feature has no impact on interfaces.
Impact on commands There are no commands related to this feature.
Impact on network and network element management tools This feature has no impact on network management or network element management tools.
Impact on system performance and capacity The state change from Cell_PCH to Cell_DCH is approximately one second faster.
2.3.1.5
RAN2963: Data Session Profiling management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms There are no alarms related to this feature.
Measurements and counters Table 27: New counters lists counters introduced with this feature. Table 27
New counters
Counter ID
Counter name
Measurement
M1006C309
SUCCESSFUL PCH TO DCH TRANS DUE TO DATA SESSION PROFILING
RRC signalling (RNC)
Table 28: Related existing counters lists existing counters related to this feature.
Issue: 01F
DN09146788
61
Radio resource management features
Table 28
RU50 Feature Descriptions and Instructions
Related existing counters
Counter ID
Counter name
Measurement
M1006C174
STATE TRANSITION TIME PCH TO DCH
RRC signalling (RNC)
M1006C175
DENOMINATOR FOR STATE TRANSITION RRC signalling (RNC) TIME PCH TO DCH
M1006C196
ATTEMPTED PCH TO DCH TRANSITIONS RRC signalling (RNC) USING UM-RLC
M1006C197
SUCCESSFUL PCH TO DCH TRANSITIONS USING UM-RLC
RRC signalling (RNC)
M1006C198
CELL RESELECTIONS DURING PCH TO DCH TRANSITIONS USING UM-RLC
RRC signalling (RNC)
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table 29: New parameters lists parameters introduced with this feature. Table 29
New parameters
Full name
Abbreviated name
Managed object
Data Session Profiling Enabled
DataSessionProfEnabled
RNFC
Large DataThreshold
LargeDataThr
RNPS
Large Data Time
LargeDataTime
RNPS
HS-RACH/FACH Preferred in Data Session Profiling
HSChaPrefInDataSesProf
RNPS
Table 30: Modified parameters lists parameters modified by this feature. Table 30
62
Modified parameters
Full name
Abbreviated name
Managed object
RNCOptions
RncOptions
RNC
Uplink traffic volume measurement low threshold
TrafVolThresholdULLow
WAC
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 30
2.3.1.6
Radio resource management features
Modified parameters (Cont.)
Full name
Abbreviated name
Managed object
UL traffic volume threshold for Smartphone
SmartTrafVolThrUL
WCEL
Downlink traffic volume measurement low threshold
TrafVolThresholdDLLow
WCEL
DL traffic volume threshold for Smartphone
SmartTrafVolThrDL
WCEL
Downlink NAS signalling volume threshold
NASsignVolThrDL
WCEL
Sales information Table 31
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
RNC LK
2.3.2 Activating RAN2963: Data Session Profiling Purpose Follow this procedure to activate the RAN2963: Data Session Profiling 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. Activate the license of the RAN2963: Data Session Profiling feature using Data session Profiling license key. To set the feature state to ON, use the following command: • •
g
for IPA-RNC: ZW7M: FEA=4654:ON; for mcRNC: set license feature-mgmt code 0000004654 feature-admin-state on No license is required for Flexi Direct RNC.
For information on managing licenses, see Licensing. The RAN2494: Fast Cell_PCH Switching feature is recommended to be activated and configured before activation of the RAN2963: Data Session Profiling feature.
Issue: 01F
DN09146788
63
Radio resource management features
RU50 Feature Descriptions and Instructions
To enable proper working of the RAN2963: Data Session Profiling feature, the following parameters need to be set as follows: • •
MSActivitySupervision WAC parameter must be set to a non-zero value CUCforPCHtoDCHallowed RNFC parameter must be set to True
Additionally, the DCHtoPCHEnabled RNFC parameter is suggested to be set to the value Enabled.
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: a) Right-click on the RNFC object and select Edit parameters. b) On the General tab, set the value of the DataSessionProfEnabled parameter to Enabled.
2.3.3 Verifying RAN2963: Data Session Profiling Purpose Follow this procedure to verify if the RAN2963: Data Session Profiling feature works properly in the network. Before you start Make sure you have access to the following applications: •
Start the measurements for the M1006C309: SUCCESSFUL PCH TO DCH TRANS DUE TO DATA SESSION PROFILING counter.
•
Set the measurement interval to 15 minutes. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Application in Managing and viewing RNC measurements.
64
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
3
Radio resource management features
With the smartphone, start the PS session to be qualified as a Large Data Session user. The session can be internet-browsing or mailbox checking. The transmitted data amount must be higher than the value specified with the LargeDataThr parameter.
4
Make pauses in the session. During the data session make pauses, but keep the RRC connection. The pauses must not be longer than the time value defined in the LargeDataTime parameter.
5
Resume the user-data transmission. After the pause during which the UE was moved from the Cell_DCH to Cell_PCH, renew the user-data transmission. Even a small data amount is sufficient for the purposes of the veneration process. User-data transmission must be resumed before the Large Data Time timer (defined with LargeDataTime parameter) is expired.
6
Open the RNW Measurement Presentation application.
7
Check if the value of the M1006C309: SUCCESSFUL PCH TO DCH TRANS DUE TO DATA SESSION PROFILING counter increased over time. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentation in Managing and viewing RNC measurements.
2.3.4 Deactivating RAN2963: Data Session Profiling Purpose Follow this procedure to deactivate the RAN2963: Data Session Profiling feature.
Issue: 01F
DN09146788
65
Radio resource management features
RU50 Feature Descriptions and Instructions
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: a) Right-click on the RNFC object and select Edit parameters. b) On the General tab, set the value of the DataSessionProfEnabled parameter to Disabled.
2.3.5 Testing RAN2963: Data Session Profiling Purpose
g
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. Test environment For the test case, the following network elements must be at least on the following software level: • • •
RNC: RN8.0 BTS: WN9.0 UE: 3GPP Rel-6
Before you start Before executing the test procedure make sure the RAN2963: Data Session Profiling feature is activated.
1
In OMS Element Manager, configure the following parameters: • • • •
set the value of LargeDataThr RNPS parameter to 1000 bytes set the value of LargeDataTime RNPS parameter to 30 seconds set the value of HSChaPrefInDataSesProf RNPS parameter to Disable set the value of TrafVolThresholdULLow WAC parameter to 512 bytes
2
Start the HSPA call in the cell.
3
Make 20 pings of 32 bytes. Make 20 continuous pings in the packet data transfer (HSPA) towards RNC. Check if during the pinging time UE is in Cell_FACH state. After the pinging, let the UE move to Cell_PCH state.
66
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
4
Radio resource management features
Make at least 20 pings of 60 bytes. Make at least 20 continuous pings towards RNC. Make sure that the UE is moving first to Cell_FACH and then to Cell_DCH state. After the pinging, let UE move back to Cell_PCH state.
5
Make a 10-second pause. The pause between pinging periods cannot exceed the value defined by the LargeDataTime parameter.
6
Make at least 30 pings of 32 bytes. Make at least 30 continuous pings in HSPA towards RNC. Make sure that UE is moving directly from the Cell_PCH to Cell_DCH state.
7
Make a 40-second pause. The pause between pinging periods has to exceed the value defined by the LargeDataTime parameter.
8
Make at least 20 pings of 60 bytes. Make at least 20 continuous pings towards RNC. Make sure that UE is moving first to Cell_FACH state and then to Cell_DCH state. After the pinging, let UE move to Cell_PCH state.
9
Make a 10-second pause. The pause between pinging periods cannot exceed the value defined with the LargeDataTime parameter.
10 Make 20 pings of 60 bytes. Make no more than 20 continuous pings towards RNC. Make sure that UE is moving directly from Cell_PCH to Cell _DCH state. After the pinging, let UE move to the Cell_PCH state. 11 Make a 40-second pause. The pause between pinging periods has to exceed the value defined by the LargeDataTime parameter. 12 Make a ping of 32 bytes. Make a 32-bytes ping towards RNC. Make sure that UE is in Cell_FACH state. 13 End the HSPA call. Expected outcome The UE is successfully moved between states, as described in the steps.
Issue: 01F
DN09146788
67
Radio resource management features
RU50 Feature Descriptions and Instructions
2.4 RAN1905: DC-HSUPA 2.4.1 Description of RAN1905: DC-HSUPA Introduction to the feature The feature allows the usage of two adjacent WCDMA carriers simultaneously in UL for a single UE.
2.4.1.1
Benefits End-user benefits This feature improves the usage of the NRT services such as e-mail sending and receiving, web browsing, chatting, video file uploading, and photo uploading.
Operator benefits This feature benefits the operator as follows: • • •
2.4.1.2
Increases the UL peak bit rate to 11,5 Mbps. Increases the average UE UL data rate by up to 100% in bursty traffic. Provides perfect load balancing across UL carriers, utilizing the unused air interface resources.
Requirements Software requirements Table 32: Software requirements lists the software required for this feature. Table 32
Software requirements
RAS
Flexi Direct
IPA-RNC
mcRNC
Flexi Direct RNC
OMS
Flexi BTS
Flexi Lite BTS
RU50 EP1
Not planned
RN8.1
mcRNC4.1
Not planned
OMS3.1
WN9.1
WL9.1
Flexi 10 BTS
NetAct
MSC
SGSN
MGW
UE
WN9.1
NetAct 8 EP2 (NetAct 15)
Support not required
SG7.0
Support not required
3GPP Rel9
Hardware requirements This feature requires Flexi Multimode System Module FSMC/D/E, or Flexi Multiradio System Module FSMF or Flexi Lite BTS WCDMA.
68
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
2.4.1.3
Radio resource management features
Functional description Functional overview The RAN1905 feature allows the user equipment to transmit simultaneously on two adjacent UL carriers. During the dual carrier operation mode, the UE sends data over two parallel E-DCHs, one per each carrier. Each of the dual E-DCH is transmitted over its own Active Set, consisting of serving and non-serving Radio Link sets. Combining of the data streams from the two carriers is done on MAC-is layer in the SRNC. The DC HSUPA is defined only with E-DCH 2ms TTI and F-DPCH. Scheduling grants for UEs are given independently on both carriers, based on the available power and serving grant value for each carrier. The SRBs are on the primary carrier. The distribution of channels between the two carriers (primary carrier and secondary carrier) is presented in the following picture. Figure 4
DC-HSUPA physical channel structure. Physical channels distribution Primary carrier
E-DPDCHs E-DPCCH HS-DPCCH
UL
Of1DCHSUPA UE
DPCCH HS-SCCH HS-PDSCH
E-AGCH E-RGCH E-HICH
DL
E-DPCH
E-DPDCHs E-DPCCH UL
DPCCH HS-SCCH HS-PDSCH
E-AGCH E-RGCH
DL
E-HICH E-DPCH
Secondary carrier
It is possible to allow the DC-HSUPA operation for the UE only in the Cell_DCH state. The SRNC allocates DC-HSUPA always when it is possible. The following conditions must be met before it is possible to allocate DC-HSUPA: •
Issue: 01F
The UE has informed that it supports DC-HSUPA.
DN09146788
69
Radio resource management features
•
• •
• • • • •
RU50 Feature Descriptions and Instructions
The DC-HSUPA is allowed for used service combination, that is, up to three Interactive or Background PS NRT RABs. The DC-HSUPA is not supported when Conversational or Streaming service is configured There is no radio link over Iur in the active set The DC-HSUPA is enabled in all the cells of the current DCH active set and in their possible DC-HSDPA/DC-HSUPA cell pairs in the same sector. Furthermore, the primary/possibly secondary E-DCH active set on the primary/ secondary UL frequency is equal to the DCH active set on the primary/ possible secondary UL frequency It is possible to allocate the DC-HSDPA for the UE in the primary and secondary serving HS-DSCH cell It is possible to allocate the F-DPCH for the UE in all primary and secondary E-DCH active set cells It is possible to allocate the HSUPA 2 ms TTI in all primary and secondary E-DCH active set cells It is possible to allocate the Flexible RLC for the UE in uplink It is possible to allocate the DC-HSUPA in all primary and secondary E-DCH active set cells
The setup of the first RT (Conversational or Streaming) RAB causes a channel type switch to HSPA. The release of the last RT (Conversational or Streaming) RAB makes DC-HSUPA allocation possible.
2.4.1.4
System impact Interdependencies between features The following features must be activated in order to activate the RAN1905: DC-HSUPA feature: • • • • •
RAN1016: Flexi BTS Multimode System Module, RAN1848: Flexi BTS Multimode System Module - FSME, or RAN2262: Flexi Multiradio System Modules RAN1201: Fractional DPCH RAN1470: HSUPA 2 ms TTI RAN1906: DC-HSDPA: Dual-Cell HSDPA 42Mbps RAN1910: Flexible RLC in UL
The following features are affected by the RAN1905: DC-HSUPA feature: • •
RAN971: HSUPA Downlink Physical Channel Power Control RAN2124: HSPA 128 Users per Cell
The RAN1905: DC-HSUPA feature is related to the following features: • • • •
•
70
RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover RAN2211: Multi-Cell HSDPA RAN2509: Application Aware RAN RAN2886: Faster OLPC By shortening the OLPC SIR target modulation interval, this feature reduces the number of retransmissions and improves the HSUPA cell capacity. RAN2302: Dynamic HSUPA BLER This feature increases the Cell Peak throughput, optimizes bursty traffic, improves the cell edge data-rate, and improves cell coverage.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Impact on interfaces This feature impacts interfaces (and protocols) as follows: •
interfaces between BTS and RNC (Iub, NBAP) –
–
–
–
–
–
–
–
–
•
NBAP: AUDIT RESPONSE and NBAP: RESOURCE STATUS INDICATION Cell Capability Container IE is enhanced to indicate BTS‘s DC-HSUPA capability to RNC. NBAP: RADIO LINK SETUP REQUEST An additional E-DCH Cell Information RL Setup Req IE is introduced for RL configuration on an uplink secondary cell. The procedure of establishing the radio link is as follows: RADIO LINK SETUP REQUEST > Additional E-DCH Cell Information RL Setup Req > Additional E-DCH Cell Information Setup > Additional E-DCH FDD Setup Information > Additional E-DCH FDD Information > E-DCH Maximum Bitrate IE The E-DCH Maximum Bitrate IE specifies the maximum bitrate supported per carrier. NBAP: RADIO LINK SETUP RESPONSE and NBAP: RADIO LINK SETUP FAILURE An additional E-DCH Cell Information Response IE is introduced for a secondary cell RL configuration response. NBAP: RADIO LINK ADDITION REQUEST An additional E-DCHCell Information RL Add Req IE is introduced for RL addition during softer handover on secondary E-DCH. NBAP: RADIO LINK ADDITION RESPONSE and NBAP: RADIO LINK ADDITION FAILURE An additional E-DCH Cell Change Information Response IE is introduced for RL addition response during softer handover on secondary E-DCH. NBAP: RADIO LINK RECONFIGURATION PREPARE An additional E-DCH Cell Information RL Reconf Prep IE is introduced for RL reconfiguration of secondary E-DCH. NBAP: RADIO LINK RECONFIGURATION READY An additional E-DCHCell Information Response RLReconf IE is introduced for RL reconfiguration response of secondary E-DCH. NBAP: SECONDARY UL FREQUENCY UPDATE INDICATION and NBAP: SECONDARY UL FREQUENCY REPORT These messages are newly introduced for DC-HSUPA. NBAP: RADIO LINK PARAMETER UPDATE INDICATION An additional E-DCH Cell Information RL Param Upd IE is introduced for RL parameter update indication of secondary E-DCH. But, in Nokia the implementation of this message is not used. So, no changes are needed.
Frame Protocol Impacts –
–
The UL Max Info IE is introduced in Outer Loop PC Control frame and E-DCH TYPE 2 UL Data frame to differentiate primary and secondary carrier frames in the single Iub transport bearer. The TNL Congestion Indication control frame is used to indicate congestion in the transport bearer.
The following L3 (RRC) messages are affected by the features: •
Issue: 01F
ACTIVE SET UPDATE
DN09146788
71
Radio resource management features
• • • • • • • •
RU50 Feature Descriptions and Instructions
CELL UPDATE CONFIRM PHYSICAL CHANNEL RECONFIGURATION RADIO BEARER RECONFIGURATION RADIO BEARER RELEASE RADIO BEARER SETUP RRC CONNECTION SETUP COMPLETE TRANSPORT CHANNEL RECONFIGURATION MEASUREMENT REPORT
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 as follows: • • •
Increases the data rates offered to UEs - 11,5 Mbps, on L1 (with QPSK). Enlarges the available bandwidth, which allows for the trunking gain and higher cell throughput. According to simulations available in feasibility study: – –
2.4.1.5
For full buffer traffic, only 1 UE per sector per cell can get double throughput when compared to SC-HSUPA. For bursty traffic, up to 10 UEs per sector per cell can get double throughput when compared to SC-HSUPA.
RAN1905: DC-HSUPA management data For information on alarm, counter, key performance indicators, and parameter documents, see Reference documentation.
Alarms Table 33: New Alarms presents alarms introduced with the feature. Table 33
New Alarms
Alarm ID
Alarm name
7795
INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG
3325
INCONSISTENCY IN CONFIGURATION PARAMETERS
Measurements and counters Table 34: New counters lists counters introduced with this feature.
72
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 34
Radio resource management features
New counters
Counter ID
Counter name
Measurement
M1001C711
UE SUPPORT FOR E-DCH CATEGORY 8
Service Level (RNC)
M1001C712
UE SUPPORT FOR E-DCH CATEGORY 9
Service Level (RNC)
M1002C691
SC-HSUPA SELECTED DUE TO UL LOAD
Traffic (RNC)
M1006C303
RADIO BEARER CONFIGURATION FOR DC-HSUPA SUCCESSFUL
RRC signalling (RNC)
M1006C304
RADIO BEARER CONFIGURATION FOR DC-HSUPA FAILED
RRC signalling (RNC)
M1022C248
CHANNEL SWITCH FROM SC-HSUPA TO DC-HSUPA SUCCESSFUL
SUCC_SWI_SCHSUPA_TO_ DCHSUPA
M1022C249
CHANNEL SWITCH FROM DC-HSUPA TO Packet Call (RNC) SC-HSUPA SUCCESSFUL
M5005C36
SUM OF DC HSUPA USERS
HSPA in WBTS Extension (WBTS)
M5005C37
MAX NUMBER OF DC HSUPA USERS
HSPA in WBTS Extension (WBTS)
M5005C38
SUM OF ACTIVE DC HSUPA USERS USING 2C
HSPA in WBTS Extension (WBTS)
M5005C39
SUM OF ACTIVE DC HSUPA USERS USING 1C
HSPA in WBTS Extension (WBTS)
M5005C48
DC HSUPA USERS DENOMINATOR
HSPA in WBTS Extension (WBTS)
M5005C49
SUM DC-HSUPA MACI PDU DATA USING 2 CARRIERS
HSPA in WBTS Extension (WBTS)
M5005C50
SUM DC-HSUPA MACI PDU DATA FOR PRIMARY CARRIER
HSPA in WBTS Extension (WBTS)
M5005C51
SUM DC-HSUPA MACI PDU DATA FOR SECONDARY CARRIER
HSPA in WBTS Extension (WBTS)
M5005C52
SUM OF MACI PDU FOR DC-HSUPA USERS USING 2 CARRIERS
HSPA in WBTS Extension (WBTS)
M5005C53
SUM OF MACI PDU FOR DC-HSUPA USERS USING PRIMARY CARRIER
HSPA in WBTS Extension (WBTS)
M5005C54
SUM OF MACI PDU FOR DC-HSUPA USERS USING SECONDARY CARRIER
HSPA in WBTS Extension (WBTS)
Key performance indicators Table 35: New key performance indicators lists key performance indicators introduced with this feature.
Issue: 01F
DN09146788
73
Radio resource management features
Table 35
RU50 Feature Descriptions and Instructions
New key performance indicators
KPI ID
KPI name
Abbreviated name
RNC_5535a
DC-HSUPA Average End User throughput
DC-HSUPA Avg end u thr
Parameters Table 36: New parameters lists parameters introduced with this feature. Table 36
New parameters
Full name
Abbreviated name
Managed object
DC HSUPA Enabled
DCellHSUPAEnabled
WCEL
DPCCH Power offset for secondary UL frequency
DPCCHPwrOffsetSecULFreq
RNHSPA
Maximum number of E-DCH users per MAC-i/is scheduler
MaxNumberEDCHS
WCEL
Table 37: Modified parameters lists parameters modified by this feature. Table 37
Modified parameters
Full name
Abbreviated name
Managed object
RNC Options
RncOptions
RNC
Maximum number of E-DCHs in the cell
MaxNumberEDCHCell
WCEL
Maximum number of E-DCHs in the local cell group
MaxNumberEDCHLCG
WBTS
Number of E-DCHs reserved for SHO branch additions
There are no PRFILE parameters related to this feature.
74
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
2.4.1.6
Radio resource management features
Sales information Table 38
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
RNC LK
2.4.2 Activating RAN1905: DC-HSUPA Purpose Follow this procedure to activate this feature. For more information on the feature, see the RAN1905: DC-HSUPA Feature Description. Before you start Restart of the RNC and WBTS is not required after the activation of this feature. This procedure requires cell locking. Make sure that one of the following hardware requirements is met: • •
RAN1016: Flexi BTS Multimode System Module RAN1848: Flexi BTS Multimode System Module - FSME
Make sure you have access to the following applications: • •
OMS Element Manager Application Launcher
This feature is controlled by a license. For information on managing licenses, see Licensing. To set the feature state to ON, use the following command: • •
for IPA-RNC: ZW7M: FEA=1794:ON; for mcRNC: set license feature-mgmt code 0000001794 feature-admin-state on
The following features need to be activated/configured before the activation of the RAN1905: DC-HSUPA feature:
•
RAN1906: DC-HSDPA RAN1910: Flexible RLC in UL RAN1470: HSUPA 2ms TTI RAN1201: Fractional DPCH
Lock the cell. If the cell is not locked, it will be locked and unlocked automatically during modification. a) Expand the WCELs object. b) Select the WCEL object. c) Right click on the cell and select Administrative State Change ► Lock Cell/Unlock Cell.
5
Configure the WCEL object. a) From the drop-down menu, select Edit Parameters. b) To find the DCELLHSUPAEnabled parameter, navigate to the Packet Scheduler tab or use the filter function. c) Set the DCellHSUPAEnabled parameter value to Enabled.
6
Save the changes. a) Click the Apply button.
7
g
Unlock the cell. If the cell is not locked, it will be locked and unlocked automatically during modification. a) Expand the WCELs object b) Select the WCEL object c) Right click on the cell and select Administrative State Change ► Lock Cell/Unlock Cell.
2.4.3 Verifying RAN1905: DC-HSUPA Purpose Follow this procedure to verify that this feature works properly in the network. Before you start Make sure you have access to one of the following applications: • •
76
RNW Measurement Management NetAct Administration of Measurements
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
1
Radio resource management features
Open the RNW Measurement Management application in the Application Launcher. Alternatively, the NetAct Administration of Measurements application can be used.
2
Start the M1006 RRC signalling (RNC) measurement with the 15 minutes interval. For details on using the RNW Measurement Management application, see the Using the RNW Measurement Management application in Managing and viewing RNC measurements. Alternatively the measurement can be started using NetAct Administration of Measurements Application.
3
Wait for the next full 15 minutes till the measurement interval starts.
4
Perform the RRC connection setup with a Rel-9 UE that supports DC-HSUPA.
5
Open the RNW Measurement Presentation application in the Application Launcher.
6
Select counters from Measurement Selector tab (select Measurement Type 1006 RRC ► select M1006C303 and M1006C304 ► click Add).
7
Go to Object Selector tab, select proper RNC-BTS-WCEL and then click Add.
8
Go to Time and Settings tab, select the time period you want to observe and the way of displaying results in Chart Type (for example Textual). Then click Create Presentation.
9
Check if the M1006 RRC signalling (RNC) measurement data is available and the following counters have been updated and are grater than 0 • •
M1006C303 – NUMBER OF RADIO BEARERS SUCCESSFULLY CONFIGURED TO USE DC-HSUPA SUCCESSFULLY M1006C304 – NUMBER OF RADIO BEARERS FAILED TO CONFIGURE TO USE DC-HSUPA FAILED
Expected outcome The value of the counters has been changed, which means that the attempt to establish a connection using the DC-HSUPA feature was performed. The feature is activated successfully.
Issue: 01F
DN09146788
77
Radio resource management features
RU50 Feature Descriptions and Instructions
2.4.4 Deactivating RAN1905: DC-HSUPA Purpose Follow this procedure to deactivate this feature.
1
Open the OMS Element Manager.
2
Go to the Topology Tree View. Select Network Management ► Topology Tree View.
Lock the cell. If the cell is not locked, it will be locked and unlocked automatically during modification. a) Expand the WCELs object. b) Select the WCEL object. c) Right click on the cell and select Administrative State Change ► Lock Cell/Unlock Cell.
5
Configure the WCEL object. a) From the drop-down menu, select Edit Parameters. b) To find the DCELLHSUPAEnabled parameter, navigate to the Packet Scheduler tab or use the filter function. c) Set the DCellHSUPAEnabled parameter value to Disabled.
6
Save the changes. a) Click the Apply button.
7
Unlock the cell. a) Expand the WCELs object b) Select the WCEL object c) Right click on the cell and select Administrative State Change ► Lock Cell/Unlock Cell.
78
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
2.4.5 Testing RAN 1905: DC-HSUPA Purpose
g
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. Purpose The purpose of this test case is to verify functionality of DC HSUPA. Test environment For the test case, the following network elements must be at least on the following software level: • • • • • • •
one RNC FLEXI rel.2 HW or newer with RU50 EP1/WN9.1 SW or newer one MGW one MSC/MSS one SGSN one GGSN Rel. 9 UE that supports DC HSUPA
Before you start The following feature related license keys need to be activated: •
License of RAN1905 DC-HSUPA with feature code 1794.
The following parameters need to be activated for this test case: BTS Commissioning settings The following requirements must be met: • •
Cells in cell pair must be correctly spaced – 25 UARFCNs apart Cells in cell pair are in the same LCG
RNFC Configuration settings The following RNFC object-specific parameters must be configured before the test: •
FlexULRLCEnabled set to value Enabled
The following RNFC object-specific parameter is recommended: •
FRLCEnabled set to value Enabled
WBTS Configuration settings The following parameters are recommended: •
HSDPA14MbpsPerUser set to value Enabled
WCEL Configuration settings The following parameters must be configured before the test:
Issue: 01F
DN09146788
79
Radio resource management features
• • • • • • • •
RU50 Feature Descriptions and Instructions
the HSDPAenabled set to value Enabled the HSUPAEnabled set to value Enabled the HSUPA2MSTTIEnabled set to value Enabled the HSUPA2MSTTIEnabled set to value Enabled the FDPCHEnabled set to value Enabled the HSPAQoSEnabled set to value Enabled the DCellHSDPAEnabled set to value Enabled the DCellHSUPAEnabled set to value Enabled
The following parameters are recommended: •
HSDPA64QAMallowed set to value Enabled HSPDSCHCodeSet set to value At least 15 HS-PDSCH codes are checked.
1
Open the OMS Element Manager.
2
Go to the Topology.
3
Expand the ROOT.
4
Expand the WCEL object.
•
Select RNC ► WBTSs ► WBTS ► WCELs ► WCEL. 5
g
Lock the cell. If the cell is not locked, it will be locked and unlocked automatically during modification. a) Expand the WCELs object. b) Select the WCEL object. c) Right click on the cell and select Administrative State Change ► Lock Cell/Unlock Cell.
80
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
6
Set up a PS call
7
Start full speed traffic upload.
8
Monitor what is the achieved uplink throughput. Check if it reaches such high levels like DC-HSUPA feature promises.
2.5 RAN2179: Dual Band HSDPA 42 Mbps 2.5.1 Description of RAN2179: Dual Band HSDPA 42 Mbps
g
Terminal IOT ready, not E2E tested.
Introduction to the feature With RAN2179: Dual Band HSDPA 42 Mbps, it is possible to use Dual Cell HSDPA with two carriers located in different frequency bands (example: Carrier 1 in band 2110-2170 MHz and Carrier 2 in band 925-960 MHz). Dual Band HSDPA is therefore very similar to Dual Cell HSDPA, the only difference is at Layer 1: the carriers are in different frequency bands. For more information on Dual Cell HSDPA, see RAN1906: Dual Cell HSDPA in WCDMA RAN, Rel. RU20, Feature Descriptions.
2.5.1.1
Benefits End-user benefits With this feature, end-user benefits from increased coverage and throughput.
Operator benefits With this feature, Dual Cell HSDPA benefits can be obtained even when no contiguous 10 MHz frequency allocation is available. Gains are obtained from additional frequency band. Lower band provides coverage, while higher band provides increased capacity and peak rate. BTS based scheduling enables dynamic resource sharing, so that faraway-UEs mainly use low frequency band, while close-by-UEs mainly use the high frequency. This approach maximizes the sector coverage and capacity.
2.5.1.2
Requirements Software requirements Table 39: Software requirements lists the software required for this feature.
Issue: 01F
DN09146788
81
Radio resource management features
Table 39
RU50 Feature Descriptions and Instructions
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi OMS Direct RNC
Flexi BTS
RU50
Flexi Direct RU50
mcRNC4.1
ADA6.0
WN9.0
RN8.0
OMS3.0 1) OMS3.1 2) IHO 6.0 3)
Flexi Lite BTS
Flexi 10 BTS
NetAct
MSC
SGSN
Not planned
WN9.1
NetAct8 EP1 1)
Support not SG8.0 required
MGW
UE
Support not 3GPP Relrequired 9
NetAct 8 EP2 (NetAct 15) 2)
1) for RU50 2) for RU50 EP1 3) for Flexi Direct RU50
Hardware requirements This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF.
2.5.1.3
Functional description With the RAN2179: Dual Band HSDPA 42 Mbps feature data for capable UE is scheduled on two distinct frequency bands in the downlink. With this feature, the maximum peak rate is 42 Mbps when 64QAM is enabled and 15 codes are available on both frequencies. The BTS uses proportional fair scheduling and optimizes the sector coverage and capacity by favoring the low-frequency band for cell-edge-UEs and the high-frequency band for UEs, that are closer to the BTS. This allows Dual Band HSDPA to combine the gain of normal Dual Cell HSDPA scheduling and the benefits of low frequency band for faraway users. The carrier selection is based both on the UE distance and current load on both uplink carriers. The RNC uses the RAN2172: Multi-Band Load Balancing feature for carrier selection.
82
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 5
Radio resource management features
Two HSDPA carriers located in two different frequency bands.
Table 40: Supported band combinations shows three band combinations supported by the RAN2179: Dual Band HSDPA 42 Mbps feature. Table 40
Supported band combinations
Dual Band HSDPA Configuration
g 2.5.1.4
UL Band
DL Band
1
I or VIII
I and VIII
2
II or IV
II and IV
3
I or V
I and V
Mixed RF module configurations, Rel 1+Rel2 or Rel1+Rel3, cannot be used with this feature.
System impact Interdependencies between features • •
Issue: 01F
The RAN1906: Dual Cell HSDPA feature and all its preconditions are prerequisites for this feature. Use of 64QAM modulation requires the RAN1643: HSDPA 64QAM feature.
DN09146788
83
Radio resource management features
•
RU50 Feature Descriptions and Instructions
Licenses for two separate frequency bands in the same NodeB and RNC are required.
Impact on interfaces RNC and BTS NBAP interface including new IE's in messages: (BTS -> RNC) Audit Response: BTS informs RNC on DualBand-HSDPA capability (BTS -> RNC) Resource Status Indication: BTS informs RNC which cell will support DualBand-HSDPA. Following NBAP procedures are unchanged between DC-HSDPA and DB-HSDPA: • •
Radio Link Setup Radio Link Reconfiguration
Changed NBAP procedures between DC-HSDPA and DB-HSDPA: Audit Response and Resource Status Indication. These procedures are enhanced with new IE indicating that NodeB has new DB-capability
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 The RAN2179: Dual Band HSDPA 42 Mbps feature can double maximum achievable peak user throughput. It also increases cell capacity (by up to 40%) and cell edge throughput.
2.5.1.5
RAN2179: Dual-Band HSDPA 42Mbps management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms Table 41: Existing alarms lists alarms related to this feature. Table 41
Existing alarms
Alarm ID
Alarm name
3325
INCONSISTENCY IN CONFIGURATION PARAMETERS
7795
INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG
Measurements and counters Table 42: New counters lists counters introduced with this feature.
84
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 42
Radio resource management features
New counters
Counter ID
Counter name
Measurement
M1001C728
UE SUPPORT FOR DB-HSDPA BAND REL9-1
Service Level
M1001C729
UE SUPPORT FOR DB-HSDPA BAND REL9-2
Service Level
M1001C730
UE SUPPORT FOR DB-HSDPA BAND REL9-3
Service Level
M1006C293
RB SETUP ATTEMPT FOR DB-HSDPA
RRC signalling
M1006C294
SUCCESSFUL RB SETUP FOR DBHSDPA
RRC signalling
M1006C295
RB SETUP FAIL FOR DB-HSDPA DUE TO NO REPLY
RRC signalling
M1006C296
RB SETUP FAIL FOR DB-HSDPA DUE TO UE NACK
RRC signalling
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table 43: New parameters lists parameters introduced with this feature. Table 43
Issue: 01F
New parameters
Full name
Abbreviated name
Managed object
Dual Band HSDPA Enabled
DBandHSDPAEnabled
WCEL
Preferred Frequency Layer for DB-DCHSDPA NRT
PFLDBHSDNRT
PFL
Preferred Layer for DB-DC-HSDPA NRT PrefLayerDBHSDNRT
PFL
Preferred Frequency Layer for DB-DCHSDPA Streaming
PFLDBHSDStr
PFL
Preferred Layer for DB-DC-HSDPA Streaming
PrefLayerDBHSDStr
PFL
Preferred Frequency Layer for DB-DCHSDPA AMR
PFLDBHSDAMR
PFL
DN09146788
85
Radio resource management features
Table 43
RU50 Feature Descriptions and Instructions
New parameters (Cont.)
Full name
Abbreviated name
Managed object
Preferred Layer for DB-DC-HSDPA AMR PrefLayerDBHSDAMR
PFL
Preferred Frequency Layer for DB-DCHSDPA AMR and NRT
PFL
PFLDBHSDAMRNRT
Preferred Layer for DB-DC-HSDPA AMR PrefLayerDBHSDAMRNRT and NRT
PFL
Table 44: Modified parameters lists parameters modified by this feature. Table 44
2.5.1.6
Modified parameters
Full name
Abbreviated name
Managed object
DC HSDPA Enabled
DCellHSDPAenabled
WCEL
Dual Cell versus MIMO preference
DCellVsMIMOPreference
RNC
Frame timing offset of a cell
Tcell
WCEL
Sales information Table 45
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
RNC LK
2.5.2 Activating RAN2179: Dual Band HSDPA 42 Mbps Purpose Follow this procedure to activate this feature. Before you start A restart of the RNC and the BTS is not required after the activation of this feature. This procedure requires cell locking. Make sure you have access to the following applications: • • •
86
OMS Element Manager Application Launcher Man-machine interface (MMI)
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Make sure that: • • • •
RAN1906: Dual-Cell HSDPA 42 Mbps feature is activated in the RNC. Dual Cell HSDPA must be activated to those cells that are going to be used for Dual Band HSDPA. Used cells must be configured to those bands that are supported for Dual Band HSDPA. Used frequencies (in two bands) must be handed with the same HSDPA scheduler (similar to Dual Cell HSDPA uses frequencies in one band that must be handled with the same scheduler).
For the allowed band combinations for Dual Band HSDPA, see Table 46: Allowed band combinations for Dual Cell and Dual Band HSDPA. Table 46
Allowed band combinations for Dual Cell and Dual Band HSDPA
Dual Band - Dual Cell HSDPA Configuration
Uplink band
Downlink band
1
I or VIII
I and VIII
2
II or IV
II and IV
3
I or V
I and V
The RAN2179: Dual Band HSDPA 42 Mbps feature is controlled by the capacity license key. For more information on licensing, see Licensing.
g
The feature code for this feature is 2118. To set the the feature state to ON, use the following command: • •
g
Issue: 01F
for IPA-RNC: ZW7M:FEA=2118:ON; for mcRNC: set license feature-mgmt code 0000002118 feature-admin-state on No license is required for Flexi Direct RNC.
DN09146788
87
Radio resource management features
RU50 Feature Descriptions and Instructions
1
Open the OMS Element Manager.
2
Go to the Topology.
3
Expand the ROOT.
4
Expand the RNC object.
5
Expand the WBTS object.
6
Lock the WCEL where the RAN2179: Dual Band HSDPA 42 Mbps feature needs to be activated: a) Select the WCEL object. b) Select the cell in the WCell(s) table. c) From the drop-down menu select "State ► Change State: Lock".
7
Configure the WCEL object: a) Select Edit parameters from the WCEL object. b) Set the DBandHSDPAEnabled parameter to Enabled.
8
Unlock the WCEL.
9
Repeat the steps 6-8 for all the required cells.
2.5.3 Verifying RAN2179: Dual Band HSDPA 42 Mbps Purpose Follow the procedure below to verify that the activation of the RAN2179: Dual Band HSDPA 42Mbps feature has been successful.
88
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
1
Perform the RRC connection setup with UE that supports Dual Band HSDPA and send some data.
2
Open the RNW measurement management application from Application Launcher.
3
Use the RNW measurement management application to start measurements M1006 Traffic with 15 minute interval. Alternatively the measurement can be started using NetAct Administration of Measurements Application. Wait until the measurement interval starts.
4
After the measurement data has been collected, use the RNW Measurement presentation GUI to check if any of the following counters has value greater than 0. • • • • • • •
M1006C293 - RB SETUP ATTEMPT FOR DB-HSDPA M1006C294 - SUCCESSFUL RB SETUP FOR DB-HSDPA M1006C295 - RB SETUP FAIL FOR DB-HSDPA DUE TO NO REPLY M1006C296 - RB SETUP FAIL FOR DB-HSDPA DUE TO UE NACK M1001C728 - UE SUPPORT FOR DB-HSDPA BAND REL9-1 M1001C729 - UE SUPPORT FOR DB-HSDPA BAND REL9-2 M1001C730 - UE SUPPORT FOR DB-HSDPA BAND REL9-3
Expected outcome Values of counters M1006C293 and M1006C294 are updated by a normal DB call setup, and value of counter M1006C295 or M1006C296 is updated by related failure RB setup scenarios.The approximate throughput is 42 Mbit/s. The RAN2179: Dual Band HSDPA 42Mbps feature has been activated successfully.
2.5.4 Deactivating RAN2179: Dual Band HSDPA 42 Mbps Purpose Follow this procedure to activate this feature.
Issue: 01F
DN09146788
89
Radio resource management features
RU50 Feature Descriptions and Instructions
1
Open the OMS Element Manager.
2
Go to the Topology.
3
Expand the ROOT.
4
Expand the RNC object.
5
Expand the WBTS object.
6
Lock the WCEL where the RAN2179: Dual Band HSDPA 42 Mbps feature needs to be activated: a) Select the WCEL object b) Select the cell in the WCell(s) table. c) From the drop-down menu select "Start ► Change state: Lock".
7
Configure the WCEL object: a) Select Edit parameters from the WCEL object. b) Set the DBandHSDPAEnabled parameter to Disabled
8
Unlock the WCEL.
9
Repeat the steps 6-8 for all the required cells.
Further information
g
A restart of the RNC and the BTS is not required after the deactivation of this feature.
2.5.5 Testing RAN2179: Dual Band HSDPA 42 Mbps Purpose
g
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. Purpose of this test case is to verify: • • •
90
successful cell setup when RNC and BTS are configured for DB DC HSDPA and successful DB DC HSDPA call with SRBs on HSPA and HSUPA 2 ms TTI state transition between Cell_DCH, Cell_FACH, and Cell_PCH by NRT traffic change inter-BTS serving cell change (SCC) between DB DC HSDPA cell and R6 HSPA cell
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
2.5.5.1
Radio resource management features
Testing environment • •
1 RNC 1 NodeB, Flexi WCDMA BTS – –
• • • • • •
Multimode System Module FSMC/FSMD/FSME BTS RF modules for 2100 and 900 must be Release 2 or newer
Check the BTS configuration whether there is enough baseband capacity licenses. Proportional fair resource packet scheduler (PF-R) must be activated in BTS. For more information, see WCDMA RAN HSDPA in BTS and Commissioning Flexi Multiradio BTS WCDMA. RNC parameters setting The following RNFC object-specific parameters must be configured before the test: • • •
HSDPAMobility, set to ON FRLCEnabled, set to ON HSDPADynamicResourceAllocation, set to ON
The following RNHSPA object-specific parameter must be configured before the test: •
MaxBitRateNRTMacdflow, set to 0
The following WBTS object-specific parameter must be configured before the test: •
HSDPA14MbpsPerUser, set to ON
The following WCEL object-specific parameters must be configured before the test: •
Issue: 01F
DBandHSDPAEnabled, set to 'Enabled' for dual cells
DN09146788
91
Radio resource management features
RU50 Feature Descriptions and Instructions
DCellHSDPAEnabled, set to ON HSDPA64QAMallowed, set to ON HSDPAenabled, set to ON HSUPAEnabled, set to ON HSPDSCHMarginSF128, set to 0 HSPDSCHCodeSet set according to the recommended code set
• • • • • •
–
contains 5,8,10,12,14,15 codes
UARFCN, dual cells have different frequencies in different frequency band HSUPA2MSTTIEnabled, set to ON SectorID, dual cells have the same value Tcell, dual cells have the same value DCellHSDPAFmcsId, set to the FMCS object ID to be used for DC HSDPA
• • • • •
UE categories Category
Max. number of codes
Modulation
21
Max number of bits / HSDSCH TB
Single Band L1 maximal Throughput
Dual Band L1 maximal Throughput
23266
11,6
23,3
27856
13,9
27,9
35168
17,6
35,2
42040
21,0
42,0
16-QAM 22 15 23 64-QAM 24
The maximum bit rate is defined in HRL QoS profile as DL:42M for PS NRT.
2.5.5.2 2.5.5.2.1
Test execution Successful cell setup when DB DC HSDPA is configured at BTS and RNC (DB DC HSDPA RAB setup with SRB on HSPA, HSUPA 2ms TTI, throughput >35M and stable) Before you start Needed BTSs and their WCDMA cells are described in the following table: WBTS
WCEL
Cell configuration
Band
UARFCN
Sector id
Tcell
WBTS1
WCEL1
Pair 1: DB DC HSDPA
I
f1
1
0
WBTS1
WCEL2
Pair 1: DB DC HSDPA
VIII
f2
1
0
1
Restart the BTS and check the telecom setup. Verify that the BTS signals DB DC HSDPA-related dual band capability information in NBAP AUDIT RESPONSE / RESOURCE STATUS INDICATION message (Dual Band Capability Info). Dual Band Capability IE = Dual Band Capable for CELL1 and CELL 2. Verify that the BTS sends CELL2 in Possible Secondary Serving Cell List IE to indicate the candidate cells for secondary cells for CELL1 and vice versa. Note that the first audit response may have dummy data.
92
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Verify that cells are on air. 2
Make a PS NRT interactive call in CELL1, then start FTP download. Verify that in the RRC: RRC CONNECTION SETUP COMPLETE message the UE indicates its dual band capability in Radio Access Capability Band Combination List -> Band Combination. Ensure that it supports band I+VIII combination. Verify that the throughput peak rate is > 35 Mbps and it is stable.
3
2.5.5.2.2
Release the PS NRT call.
State transition between Cell_DCH, Cell_FACH, and Cell_PCH by NRT traffic change
1
Set the value of the RNC CUCforPCHtoDCHallowed parameter to 'Not allowed'.
2
Set up a DB DC HSDPA call in Cell1 and Cell2. Keep full speed FTP download. Verify that value of the M1001C728 counter (number of RRC connection establishments by UEs supporting DB DC HSDPA band combination Rel9-1 (band I and band VIII)) is increased. Verify that the call is established correctly and data throughput can reach >35 Mbps and is stable. The throughput is acceptable. Verify that the value of the M1006C293 counter (the number of attempted radio bearer setups/reconfigurations for DB HSDPA) is increased. The M1006C209 counter is also updated along with this counter because the radio bearer was not using DC HSDPA previously. Verify that the value of the M1006C294 counter (the number of successful radio bearer setups/reconfigurations for DB HSDPA) is increased. M1006C210 is also updated along with this counter because the radio bearer was not using DC HSDPA previously.
3
Stop the FTP download. Verify that the radio link is correctly deleted and the RNC sets the UE first to CELL_FACH state, and then to CELL_PCH state.
4
Ping big packet to server, then start FTP download at full speed. Verify that the UE can go back first to Cell_FACH state, and then to Cell_DCH state. Verify that DB DC HSDPA is allocated.
5
Keep the full speed FTP download for 5 minutes. Verify that DL throughput can go back to >35 Mbps and it is stable.
Issue: 01F
DN09146788
93
Radio resource management features
RU50 Feature Descriptions and Instructions
Verify that the value of the M1006C293 counter (the number of attempted radio bearer setups/reconfigurations for DB HSDPA) is increased. M1006C209 is also updated along with this counter because the radio bearer was not using DC HSDPA previously. Verify that the value of the M1006C294 counter (the number of successful radio bearer setups/reconfigurations for DB HSDPA) is increased. M1006C210 is also updated along with this counter because the radio bearer was not using DC HSDPA previously. 6
Release the call. Verify that the call is released correctly .
2.5.5.2.3
Inter-BTS serving cell change (SCC) between DB DC HSDPA cell and SC HSPA cell Before you start Needed BTSs, their WCDMA cells, and the relationship between them are described in the following table: WBTS
WCEL
Cell configuration
Band
UARFCN Sector id
Tcell
ADJ
WBTS1
WCEL1
Pair 1: DB DC HSDPA
I
f1
1
0
Cell6
WBTS1
WCEL2
Pair 1: DB DC HSDPA
VIII
f2
1
0
-
WBTS2
WCEL6
R6 HSPA
I
f1
0
0
Cell1
1
Set up a DB DC HSDPA call in cell pair1 (cell1/cell2) and start FTP download. Verify that the value of the M1006C293 counter (the number of attempted radio bearer setups/reconfigurations for DB HSDPA) is increased. M1006C209 is also updated along with this counter because the radio bearer was not using DC HSDPA previously. Verify that the value of the M1006C294 counter (the number of successful radio bearer setups/reconfigurations for DB HSDPA) is increased. M1006C210 is also updated along with this counter because the radio bearer was not using DC HSDPA previously.
2
Decrease the attenuation of cell6 gradually to strengthen its signal, so that cell6 is added to active set.
3
Decrease the attenuation of cell6 gradually to strengthen its signal; SCC from DC pair 1 to SC-HSPA cell is performed. Verify that the throughput (FTP) is acceptable during and after the SCC.
4
Repeat the SCC from SC-HSPA cell6 to DC pair 1. Verify that SCC back is successful and the throughput (FTP) is stable during the SCC.
94
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Verify that the value of the M1006C293 counter (the number of attempted radio bearer setups/reconfigurations for DB HSDPA) is increased. M1006C209 is also updated along with this counter because the radio bearer was not using DC HSDPA previously. Verify that the value of the M1006C294 counter (the number of successful radio bearer setups/reconfigurations for DB HSDPA) is increased. M1006C210 is also updated along with this counter because the radio bearer was not using DC HSDPA previously. 5
Release the call. Verify that the call was released successfully.
6
Restore all parameters.
2.6 RAN2250: Enhanced HSUPA IC 2.6.1 Description of RAN2250: Enhanced HSUPA IC Introduction to the feature The RAN2250: Enhanced HSUPA IC provides an improved algorithm, which cancels an interference from 2ms TTI users from other 2ms TTI users. The feature is an extension of the RAN1308: HSUPA Interference Cancellation Receiver feature, which cancels interference from 2 ms TTI users from 10 ms TTI and DCH users.
2.6.1.1
Benefits End-user benefits This feature provides the user with the following benefits: • •
removing the interferences appearing during a direct data transfer providing the service with higher quality than without the feature
Operator benefits This feature benefits the operator by increasing the UL data rates when several 2 ms TTI users are present in the same cell.
2.6.1.2
Requirements Software requirements Table 47: Software Requirements lists the software required for this feature. Table 47 RAS
Software Requirements Flexi Direct IPA-RNC mcRNC
RU50 EP1 Not planned RN8.1
Issue: 01F
mcRNC4.1
DN09146788
Flexi Direct RNC OMS Not planned
Flexi BTS
OMS3.1 WN9.1
95
Radio resource management features
Table 47
RU50 Feature Descriptions and Instructions
Software Requirements (Cont.)
Flexi Lite BTS
Flexi 10 BTS
NetAct
MSC
SGSN
MGW
UE
Not planned
WN9.1
NetAct 8 EP2 (NetAct 15)
Support not required
Support not required
Support not required
Support not required
Hardware requirements This feature requires Flexi Multimode System Module FSMC/D/E, or Flexi Multiradio System Module FSMF.
2.6.1.3
Functional description The algorithm which is introduced with this feature is presented on the picture below, and described in the following paragraph. Figure 6
The Enhanced Interference Cancellation procedure Originalstreampower(cell-specific) Prx_total,orig = Prx_total non-PIC
DEM - the demodulation stage REM - the remodulation stage RSR - the Residual Signal Reconstruction stage
The cell-specific signal is marked with the r(k) and the power of this stream is marked with the Prx_total,original. In the first phase part of the process the algorithm generates the common residual signal, by subtracting the demodulated and re-modulated signals of all 2 ms TTI E-DCH users) from the original stream. On the picture, the created signal is named as Prx_total,res,common. In the second phase, for each 2 ms TTI E-DCH user, the individual signal for user k Prx_total,res,k (where the k is the indicated user) is created. This is achieved by adding the own detected signal to the common residual signal Prx_total,res,common. This process is called RSR.
96
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Figure 7: The residual signal stream relationship presents the basic AC consideration with and without the RAN2250: Enhanced HSUPA IC feature. The power levels on the common residual signal stream and the UE-specific residual stream significantly differ what shows the benefits of using the RAN2250: Enhanced HSUPA IC feature. Figure 7
System impact Interdependencies between features This feature requires the following feature up and running: •
RAN1308: HSUPA interference cancellation receiver
Impact on interfaces This feature impacts NBAP interface as follows: •
NBAP CAPABILITY INFORMATION –
the PIC level parameter is enhanced. The new value: enhanced-2ms-PIC is added to the PIC level for the RAN2250: Enhanced HSUPA IC feature.
Impact on network and network element management tools This feature has no impact on network management or network element management tools.
Issue: 01F
DN09146788
97
Radio resource management features
RU50 Feature Descriptions and Instructions
Impact on system performance and capacity The RAN2250: Enhanced HSUPA IC feature increases cell HSUPA throughput by up to 45%. It allows high signal-to-noise ratio for a high data rate 2ms HSUPA user while keeping the noise rise within the planned limits. The feature allows also to increase a number of admitted RT E-DCH users mapped on E-DCH transport channel with 2 ms TTI, keeping the coverage and performance of admitted users mapped on DCH or E-DCH with 10 ms TTI at the same level as without interference cancellation.
2.6.1.5
RAN2250: Enhanced HSUPA IC management data 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 48: Modified Parameters lists parameters modified by this feature. Table 48
Modified Parameters
Full name
Abbreviated name
Management object
PIC state
PICState
WCEL
Admin PIC state
AdminPICState
WCEL
Filtering Coefficient of PrxTotal measurement
PrxMeasFilterCoeff
WCEL
Cell assigned to PIC pool
AssignedPICPool
WCEL
Max target received wide band PrxMaxOrigTargetBTS original power for BTS
2.6.1.6
WCEL
Sales information Table 49
Sales Information BSW/ASW
ASW
License control in network element RAN
License control in network element BTS LK
2.6.2 Activating RAN2250: Enhanced HSUPA IC Purpose Follow this procedure to activate this feature.
98
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
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 an access to the following applications: •
BTS Site Manager
The RAN2250: Enhanced HSUPA IC feature is controlled by the On/Off HSUPA Interference Cancellation Receiver BTS license and requires a valid license file. The feature code for this feature is 5175. For more information on managing licenses, see Licensing. Before activating the RAN2250: Enhanced HSUPA IC feature, the RAN1308: HSUPA Interference Cancellation Receiver feature must be activated (see Activating RAN1308: HSUPA Interference Cancellation Receiver).
1
Open BTS Site Manager.
2
Go to the Commissioning panel.
3
Go through the Wizard steps up to the WCDMA Carrier Candidates and Local Cell Group Settings page by clicking the Next button at the bottom of the page.
4
To enable the RAN2250: Enhanced HSUPA PIC feature mark the 'Enhanced parallel interference cancellation in use' checkbox.
Expected outcome The RAN2250: Enhanced HSUPA PIC is activated.
2.6.3 Verifying RAN2250: Enhanced HSUPA IC Purpose Follow this procedure to verify that this feature has been activated successfully. Before you start Make sure that the RAN1308: HSUPA Interference Cancellation Receiver is activated in the cell.
Issue: 01F
DN09146788
99
Radio resource management features
RU50 Feature Descriptions and Instructions
1
Start the measurement (schedule: 7 days, 00:00-24:00, 60 minutes interval) using the RNW Measurement Management application in the Application Launcher.
2
Wait for the next full 60 minutes till the measurement interval starts.
3
Make at least two simultaneous HSUPA 2 ms TTI PS data calls and transfer some data.
4
Wait for the next full 60 minutes for the measurement collection and additional 10 minutes for the transfer of the measurement data to OMS.
5
Activate the RAN2250: Enhanced HSUPA IC feature (see Activating RAN2250: Enhanced HSUPA IC). Perform steps 1-4 again and compare cell throughput before and after the feature activation using the following counters and KPIs: Counters: • • • • • •
M5002C2 E-DCH DATA VOLUME FOR SERVING CELL UL M5002C3 E-DCH DATA VOLUME FOR NON-SERVING CELL IN SERVING EDCH RLS UL M5002C4 E-DCH DATA VOLUME FOR NON-SERVING CELL IN NONSERVING E-DCH RLS UL M5000C322 HSUPA MACE PDU DATA WITH 2MS TTI M5000C324 SUM OF HSUPA USERS WITH 2MS TTI M5000C153 HSUPA AVERAGE MAC-D THROUGHPUT
KPIs: • •
RNC_2050b Active HSUPA 2ms TTI throughput RNC_1884c Average HSUPA Throughput per Session
Expected outcome Cell throughput is higher after activation of the RAN2250: Enhanced HSUPA IC feature.
2.6.4 Deactivating RAN2250: Enhanced HSUPA IC Purpose Follow this procedure to deactivate this feature.
g
100
Restart of the RNC or the BTS is not required after activation of this feature.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Radio resource management features
1
Open BTS Site Manager.
2
Go to the Commissioning panel.
3
Go through the Wizard steps up to the WCDMA Carrier Candidates and Local Cell Group Settings page by clicking the Next button at the bottom of the page.
4
To disable the RAN2250: Enhanced HSUPA PIC feature unmark the 'Enhanced parallel interference cancellation in use' checkbox.
Another way to disable the RAN2250: Enhanced HSUPA PIC feature is disabling the RAN1308: HSUPA Interference Cancellation Receiver feature (see Deactivating RAN1308: HSUPA Interference Cancellation Receiver).
2.7 RAN2482: Enhanced Virtual Antenna Mapping 2.7.1 Description of RAN2482: Enhanced Virtual Antenna Mapping Introduction to the feature With the Virtual Antenna Mapping the WCDMA or HSDPA downlink signals, either nonMIMO or MIMO, are all sent from two physical antennas using a virtual antenna mapping matrix between the virtual antennas and physical antennas. The RAN2482: Enhanced Virtual Antenna Mapping feature tunes the phase difference between the two physical antennas to obtain the best signal quality for HSDPA.
2.7.1.1
Benefits End-user benefits The end user benefits from an enhanced application experience because of higher HSDPA DL throughput.
Operator benefits The operator benefits from higher average DL throughput for HSDPA users, and thus higher average cell throughput.
2.7.1.2
Requirements Software requirements Table 50: Software requirements lists software required for this feature.
Issue: 01F
DN09146788
101
Radio resource management features
Table 50
RU50 Feature Descriptions and Instructions
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
Flexi BTS
RU50
Not planned RN8.0
mcRNC4.1
Not planned OMS3.0 1)
WN9.0
OMS3.1 2)
Flexi Lite BTS
Flexi 10 BTS
NetAct
MSC
WL9.1
WN9.1
NetAct 8 EP1 1)
Support not Support not required required
NetAct 8 EP2 (NetAct 15)
SGSN
MGW
UE
Support not required
Support not required
2)
1) for RU50 2) for RU50 EP1
Hardware requirements This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF or Flexi Lite BTS WCDMA. This feature also requires double Tx and double antenna lines per sector. For supported BTS configurations, see Flexi Multiradio BTS WCDMA Supported and Planned Configurations Excel in NOLS.
2.7.1.3
Functional description Virtual Antenna Mapping (VAM) was introduced with the feature RAN1642: MIMO and it can be used in cells with two Tx like in physical MIMO configuration. With the VAM the cell area is covered with two physical antennas using virtual antenna mapping between physical and virtual antennas. The mapping can be used for MIMO and non-MIMO configurations. However, VAM solution provides more efficient MIMO performance by transmitting to non-MIMO UEs without transmit diversity but by Virtual Antenna Mapping for power balancing. VAM is beneficial for adding power of two power amplifiers instead of one and introducing polarization diversity when the cross-polarized base station antennas are used. The RAN2482: Enhanced Virtual Antenna Mapping (E-VAM) feature improves the performance of VAM by controlling the phase difference between the physical antennas. The RAN2482: Enhanced Virtual Antenna Mapping feature tunes the phase difference between the two physical antennas to obtain the best signal quality for HSDPA. The channel quality indicators of active non-MIMO UEs in the cell are used to obtain the best phase difference between the two physical antennas. Tuning of the phase offset is dynamic and automatic. The best benefits are obtained for UEs with one Rx.
102
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
The E-VAM can be activated only in cells with two Tx. Cell restart is required whenever the RAN2482: Enhanced Virtual Antenna Mapping feature is activated or deactivated.
2.7.1.4
System impact Interdependencies between features There is no interdependencies with other features. Virtual Antenna Mapping (VAM) has to be configured in the cells prior to E-VAM activation.
Impact on interfaces This feature has no impact on interfaces.
Impact on MML commands There are no MML commands related to this feature.
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 The feature increases the DL cell throughput.
Impact on dimensioning The RAN2482: Enhanced Virtual Antenna Mapping feature can provide significantly higher average HSDPA throughput for non-MIMO users (field test results showed up to 50% higher). The feature provides higher average HSDPA cell throughput comparing to the situation when Virtual Antenna Mapping is enabled in the cell. The gain depends on actual radio conditions measured from CQI reports sent by UE. The highest gains are observed for stationary UEs.
2.7.1.5
RAN2482: Enhanced Virtual Antenna Mapping management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms There are no alarms related to this feature.
Measurements and counters There are no measurements and counters related to this feature.
Key performance indicators There are no key performance indicators related to this feature.
Issue: 01F
DN09146788
103
Radio resource management features
RU50 Feature Descriptions and Instructions
Parameters Table 51: New parameters lists parameters introduced with this feature. Table 51
2.7.1.6
New parameters
Full name
Abbreviated name
Managed object
EVAM in use
EVAMInUse
WCEL
Sweep time
EvamTSweep
WCEL
Keep time
EvamTKeep
WCEL
Phase offset amount
EvamNumPhaseOffset
WCEL
Initial Phase Offset
EvamDInit
WCEL
EVAM Capability
EVAMCapability
WCEL
Sales information Table 52
Sales information
BSW/ASW
RAS SW component
License control in network element
ASW
RAN
RNC LK
2.7.2 Activating RAN2482: Enhanced Virtual Antenna Mapping Purpose Follow this procedure to activate RAN2482: Enhanced Virtual Antenna Mapping feature.
Configuring Virtual Antenna Mapping Before you start Before activating the RAN2482: Enhanced Virtual Antenna Mapping feature, Virtual Antenna Mapping (VAM) needs to be configured first. The VAM is configured via BTS Site Manager only in MIMO-capable BTSs. After VAM configuration, BTS restart is required. Although VAM was introduced with the RAN1642: MIMO feature, it does not require a license to be configured. Make sure you have access to the BTS Site Manager.
104
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
1
Radio resource management features
Start the WCDMA BTS Site Manager application and establish the connection to the BTS. Flexi Multiradio BTS WCDMA is able to autonomously request for missing license file(s) from the NetAct License Manager during the RAN2131: Automatic Licence Distribution to Flexi BTS feature activation. Make sure that you have selected Automatic licensing in use checkbox in the Automatic License Distribution Settings page.
g
If the RAN2131: Automatic Licence Distribution to Flexi BTS feature is not activated, the relevant license must be uploaded manually.
2
Upload the configuration plan file from the BTS. When BTSSM is connected to the BTS, it automatically uploads the current configuration plan file from the BTS. •
3
Select View ► Commissioning or click Commissioning on the View bar.
Configure Virtual Antenna Mapping in a cell. a) In Commissioning, go to Local Cell Resources page and assign two Tx outputs for a single cell to make MIMO settings section appear. b) In MIMO settings section, select the Virtual antenna mapping in use checkbox and choose MIMO type from the drop-down list.
g
Please note, that following this step allows to configure VAM only in one specific cell. To configure VAM in multiple cells, run this step on each cell separately.
4
Send the commissioning plan file to the BTS. Click Send Parameters button. You may save the parameters at this point.
5
The new commissioning plan file is automatically activated in the BTS. BTSSM automatically sends an activation command after finishing the file download.
6
Select Next to complete the commissioning. You can save the commissioning report, if required.
7
Backup commissioning files (if applicable). Select File Backup commissioning files Save the complete backup commissioning file for further use.
Expected outcome VAM is configured in chosen cells. Restart the BTS to make changes valid.
Issue: 01F
DN09146788
105
Radio resource management features
RU50 Feature Descriptions and Instructions
Activating Enhanced Virtual Antenna Mapping Before you start The RAN2482: Enhanced Virtual Antenna Mapping feature activating procedure does not cause downtime and the feature can be activated at any time of the day. Make sure you have access to the following applications: OMS Element Manager Application Launcher Man-machine interface (MMI)
• • •
The RAN2482: Enhanced Virtual Antenna Mapping feature is controlled by the long-term capacity Enhanced Virtual Antenna mapping license key. Capacity license refers to the number of cells. For more information on licensing, see Licensing.
g
Number of activated cells must not exceed the capacity of the Enhanced Virtual Antenna mapping license.
g
The feature code for this feature is 3732. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M:FEA=3732:ON; for mcRNC: fsclish -c "set license feature-mgmt code 0000003732 featureadmin-state on”
• •
g
No license is required for Flexi Direct RNC.
1
Open the OMS Element Manager.
2
Go to the Topology.
3
Expand the ROOT.
4
Go to the WCEL object by following the path: RNC object ► WBTSs folder ► WBTS object ► WCELs folder ► WCEL object
106
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
5
Radio resource management features
Configure the WCEL object: a) Lock the WCEL object. b) Right-click on the WCEL object and select Edit parameters. c) Set the EVAM in use (EVAMInUse) parameter to Enabled. The change of the parameter to Enabled consumes the license in terms of number of cells. d) Unlock the WCEL object.
Expected outcome The RAN2482: Enhanced Virtual Antenna Mapping feature has been activated in the RNC. After activating the feature, there is no need to reset the RNC or the BTS.
2.7.3 Verifying RAN2482: Enhanced Virtual Antenna Mapping Purpose In a cell which has MIMO hardware capability, E-VAM provides higher average DL throughput for non-MIMO users and thus higher average cell throughput. When compared to VAM, the enhanced VAM is expected to increase stationary one-Rx UE’s average throughput by at least 10%.
2.7.4 Deactivating RAN2482: Enhanced Virtual Antenna Mapping Purpose Follow this procedure to deactivate this feature.
1
Open the OMS Element Manager.
2
Go to the Topology.
3
Expand the ROOT.
4
Go to the WCEL object following the path: RNC object ► WBTSs folder ► WBTS object ► WCELs folder ► WCEL object
5
Configure the WCEL object: a) Lock the WCEL object. b) Right-click on the WCEL object and select Edit parameters. c) Set the EVAM in use (EVAMInUse) parameter to Disabled. The change of the parameter to Disabled frees the license in terms of number of cells.
Issue: 01F
DN09146788
107
Radio resource management features
RU50 Feature Descriptions and Instructions
d) Unlock the WCEL object. Further information
g
A restart of the RNC and the BTS is not required after the deactivation of the feature.
2.8 RAN2221: HSPA+ Over Iur 2.8.1 Description of RAN2221: HSPA+ Over Iur Introduction to the feature This feature provides support for additional HSDPA+ functionalities over the Iur interface: • • •
The RAN2221: HSPA+ Over Iur feature supports calls performed in the serving RNC with the established radio links, and calls peformed in anchoring cell without radio links in serving RNC.
g 2.8.1.1
IOT completed only between Nokia devices.
Benefits End-user benefits This feature benefits the end-user with enhanced service quality in the RNC border area.
Operator benefits Operator can enable HSDPA+ functionalities over the Iur interface and therefore offer improved capacity and HSDPA throughput in the RNC border area.
2.8.1.2
Requirements Software requirements lists the software required for this feature. Table 53
108
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
Flexi BTS
RU50 EP1
Not planned RN8.1
mcRNC4.1
Not planned OMS3.1
WN9.1
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 53
Flexi Lite BTS
Radio resource management features
Software requirements (Cont.)
Flexi 10 BTS
Not planned WN9.1
NetAct
MSC
SGSN
MGW
NetAct 8 EP2
Support not Support not Support not required required required
UE
Support not required
Hardware requirements This feature does not require any new or additional hardware.
2.8.1.3
Functional description Functional overview This feature introduces the following functionalities to the Iur interface: • • •
This feature is supported only with signaling radio bearers (SRBs) on a dedicated channel and only with one NRT PS radio access bearer. The following HSDPA configurations are supported over Iur: • • • •
Dual cell HSDPA with Flexible RLC DL Single cell HSDPA with Flexible RLC DL Dual cell HSDPA (64QAM) with Flexible RLC DL Single cell HSDPA (64QAM) with Flexible RLC DL
When DRNC is the Nokia RNC, the target cell capabilities are received via the Cell Capability Container. If DRNC is provided by another vendor, the Cell Capability Container of the target cell might not be sent by DRNC. When the Cell Capability Container of the target cell is not received from DRNC, the intra-frequency serving cell change over Iur is tried with the Flexible RLC in DL and HSDPA 64QAM, provided the UE was using those before the serving cell change, and those usages are allowed over Iur by the FRLCOverIurEnabled and HSDPA64QAMOverIurEnabled parameters. When the DRNC does not support the Flexible RLC in the target cell or over Iur (failure cause: Requested Configuration not Supported, or HS-DSCH MAC-d PDU Size Format not supported), the SRNC retries allocation of the SC-HSDPA with fixed RLC configuration. Anchoring The RAN2221: HSPA+ Over Iur feature supports anchoring. Provided the RAN2270: Extension of HSPA Over Iur feature is activated, the SRNC is allowed to:
Issue: 01F
DN09146788
109
Radio resource management features
• •
RU50 Feature Descriptions and Instructions
setup HS-DSCH with Flexible RLC in DL, DC-HSDPA, and/or HSDPA64QAM over Iur perform Serving Cell Change from DRNC cell to DRNC cell with Flexible RLC in DL, DC-HSDPA, and/or HSDPA64QAM without radio links in serving RNC.
The RAN2221: HSPA+ over Iur feature supports only one NRT PS RAB over Iur. When the RAN2270: Extension of HSPA Over Iur feature is in use and there is an attempt to establish AMR call with the existing HSPA+ over Iur RAB, the DC-HSDPA is reconfigured to SC-HSDPA for enabling AMR+HSPA over Iur. With an existing AMR call, a single NRT PS RAB on the SC-HSPA with fixed size RLC PDU might be established. When there is an attempt to establish another PS RAB with the existing HSPA+ over Iur RAB, the DRNC rejects the request by the failure code Requested Configuration not Supported. When the RAN2270: Extension of HSPA Over Iur feature is not used: • •
2.8.1.4
the SRNC does not set up HS-DSCH and/or E-DCH RL over Iur the SRNC does not perform SCC from DRNC cell to DRNC cell without radio links in serving RNC.
System impact Interdependencies between features This feature requires the following features to be up and running: • •
RAN1231: HSPA over Iur RAN1638: Flexible RLC in DL
This feature requires the license of RAN1258: HSDPA 14 Mbps per User feature to work. The following features have impact on the RAN2221: HSPA+ Over Iur feature: • • •
RAN1906: Dual-Cell HSDPA 42Mbps RAN1643: HSDPA 64QAM RAN2270: Extension of HSPA Over Iur
Impact on interfaces This feature provides support for HSDPA+ features listed in Functional description over the Iur 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 provides support for higher HSDPA data rates over Iur.
110
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
2.8.1.5
Radio resource management features
RAN2221: HSPA+ Over Iur management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms There are no existing alarms related to this feature.
Measurements and counters Table 54: New counters lists counters introduced with this feature. Table 54
New counters
Counter ID
Counter name
M1004C179
FAILED DC-HSDPA ALLOCATION OVER IUR
M1004C181
FAILED HSDPA 64QAM ALLOCATION OVER IUR
M1004C177
FAILED HS-DSCH FLEXIBLE RLC ALLOCATION OVER IUR
M1004C178
SUCCESSFUL DC-HSDPA ALLOCATION OVER IUR
M1004C180
SUCCESSFUL HSDPA 64QAM ALLOCATION OVER IUR
M1004C176
SUCCESSFUL HS-DSCH FLEXIBLE RLC ALLOCATION OVER IUR
Key performance indicators There are no new KPIs related to the feature.
Parameters Table 55: New parameters lists parameters introduced with this feature. Table 55
New parameters
Full name
Abbreviated name
Managed object
Flexible RLC Over Iur Enabled
FRLCOverIurEnabled
RNC/IUR
DC-HSDPA Over Iur Enabled
DCHSDPAOverIurEnabled
RNC/IUR
HSDPA 64QAM Over Iur Enabled
HSDPA64QAMOverIurEnabled
RNC/IUR
Enable HSUPA Congestion Control on Iur HSUPACCIurEnabled
RNC/IUR
Table 56: Modified parameters lists parameters modified by this feature. Table 56
Issue: 01F
Modified parameters
Full name
Abbreviated name
Managed object
RNC Options
RncOptions
RNC
Flexible RLC Enabled
FRLCEnabled
RNC/RNFC
HSPA Over Iur
HSPAOverIur
RNC/IUR
Maximum NRT HS-DSCH MACd flow bit rate over Iur
MaxIurNRTHSDSCHBitRate
RNC/IUR
DN09146788
111
Radio resource management features
2.8.1.6
RU50 Feature Descriptions and Instructions
Sales information Table 57
Sales information
BSW/ASW SW component License control in network element ASW
RAN
RNC LK
2.8.2 Activating RAN2221: HSPA+ Over Iur Purpose Follow this procedure to activate the RAN2221: HSPA+ Over Iur feature. 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. Before activating the RAN2221: HSPA+ Over Iur feature, activate the following features: • • • • •
RAN1231: HSPA Over Iur RAN1638: Flexible RLC in DL RAN1258: HSDPA 14 Mbps per User RAN1906: Dual-Cell HSDPA 42Mbps RAN1643: HSDPA 64QAM
The RAN1638: Flexible RLC in DL feature is enabled by the FRLCEnabled RNP parameter on the RNC level. For anchoring support, the RAN2270: Extension of HSPA Over Iur needs to be be activated. Activate the license for the RAN2221: HSPA+ Over Iur feature using HSPA+ over Iur license key. To set the feature state to ON, use the following command: • •
for IPA-RNC: ZW7M:FEA=5233:ON; for mcRNC: set license feature-mgmt code 0000005233 feature-admin-state on
For information on managing licenses, see Licensing.
112
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
1
Open OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object then expand the IUR object.
4
Configure the IUR object: a) Right-click on the IUR object and select Edit parameters. b) On the Admission Control tab, set the value of the FRLCOverIurEnabled parameter to Enabled. c) On the Admission Control tab, set the value of the DCHSDPAOverIurEnabled parameter to Enabled. d) On the Admission Control tab, set the value of the HSDPA64QAMOverIurEnabled parameter to Enabled.
g
In order to work, activate the RAN2221: HSPA+ Over Iur feature in both the serving and drift RNC for feature functionalities. To activate HSUPA Congestion Control over Iur, set the value of the HSUPACCIurEnabled parameter to Enabled. If increase of the maximum data rate over Iur is needed, change the value of the MaxIurNRTHSDSCHBitRate IUR parameter accordingly. In order to work correctly, set the NRncVersion IUR parameter (release version of drift RNC) to Rel 9 or higher. For inter vendor test cases, set the InterfaceMode IUR parameter to value other than 0 depending on the drift RNC vendor.
2.8.3 Verifying RAN2221: HSPA+ Over Iur Purpose Follow this procedure to verify if the RAN2221: HSPA+ over Iur feature works properly in the network. Before you start Make sure you have access to the following applications: • •
Start the measurements for the M1004C176, M1004C178, and M1004C180 counters. If the RAN2221: HSPA+ over Iur feature is in use, SRNC updates the following counters: • • •
M1004C176: SUCCESSFUL HS-DSCH FLEXIBLE RLC ALLOCATION OVER IUR M1004C178: SUCCESSFUL DC-HSDPA ALLOCATION OVER IUR M1004C180: SUCCESSFUL HSDPA 64QAM ALLOCATION OVER IUR
For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. 3
Open the RNW Measurement Presentation application.
4
Check if the values of the M1004C176, M1004C178, and M1004C180 counters increased over time. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentation in Managing and viewing RNC measurements.
Unexpected outcome The RAN2221: HSPA+ over Iur feature does not work correctly in the network. In that case, values of the following counters are updated: • • •
M1004C177: FAILED HS-DSCH FLEXIBLE RLC ALLOCATION OVER IUR M1004C179: FAILED DC-HSDPA ALLOCATION OVER IUR M1004C181: FAILED HSDPA 64QAM ALLOCATION OVER IUR
2.8.4 Deactivating RAN2221: HSPA+ Over Iur Purpose Follow this procedure to deactivate the RAN2221: HSPA+ Over Iur feature.
114
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
1
Open OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object then expand the IUR object.
4
Configure the IUR object: a) Right-click on the IUR object and select Edit parameters. b) On the Admission Control tab, set the value of the DCHSDPAOverIurEnabled parameter to Disabled. c) On the Admission Control tab, set the value of the HSDPA64QAMOverIurEnabled parameter to Disabled. d) On the Admission Control tab, set the value of the FRLCOverIurEnabled parameter to Disabled.
2.8.5 Testing RAN2221: HSPA+ Over Iur Purpose
g
This is an example of the verification; do not use it for the feature as such in the 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 show that with the RAN2221: HSPA+ Over Iur feature activated, it is possible to achieve higher HSDPA throughput over the Iur interface. Test environment • • • •
two RNCs two Flexi BTS with Multimode System Module (for Dual-Cell HSDPA support) one UE Rel-8 (with Dual-Cell HSDPA support) UE throughput monitoring tool (DU meter)
Before executing this testing procedure, ensure that the following features are activated: • • • • • • •
g
Issue: 01F
RAN979: HSUPA 2.0 Mbps RAN1231: HSPA Over Iur RAN1638: Flexible RLC in DL RAN1258: HSDPA 14 Mbps per User RAN1906: Dual-Cell HSDPA 42Mbps RAN1643: HSDPA 64QAM RAN2221: HSPA+ Over Iur Before executing this testing procedure, cells taking part in the test have to be configured as intra-frequency neighbor cells and cell pairs of DC-HSDPA have to be configured as inter-frequency neighbours.
DN09146788
115
Radio resource management features
1
RU50 Feature Descriptions and Instructions
Make an HSPA call (background, FTP service) and monitor the call throughput. Ensure that during the HSPA call, UE has good radio conditions and that there is only one UE in the test BTS in SRNC. Ideally, the call throughput will be close to 42 Mbps. In practise the throughput depends on the UE and test environment settings.
2
Adjust the attenuation to make the UE undergo the serving cell change (SCC) to DRNC and monitor the call throughput. When an ongoing call goes under serving cell change, the signal-to-noise ratio decreases causing the subsequent call throughput decrease. In laboratory conditions, the throughput can reach about 15 Mbps. If the relocation is disabled, during the anchoring similar throughput as under SRNC can be reached.
3
Deactivate the RAN2221: HSPA+ over Iur feature. For the detailed instructions, see Deactivating RAN2221: HSPA+ Over Iur.
4
Once again make the UE undergo the serving cell change to DRNC and monitor the call throughput. After deactivating the RAN2221: HSPA+ over Iur feature, a significant call throughput decrease is expected for calls undergoing the serving cell change over Iur. The throughput of a call undergoing SCC over Iur is expected to be about 8 Mbps.
Result
g
Note that in this testing procedure, the results depend on the radio conditions.
2.9 RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover 2.9.1 Description of RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover Introduction to the feature The RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature introduces compressed mode measurements with HSPA active without UL channel type switching to DCH. The feature also introduces basic compressed mode support for performing measurements related to inter-system handover to LTE. Without this feature, during inter-frequency handover in HSPA, before compressed mode is started, switching the UL transport channel from HSUPA to DCH is needed. A switch back to HSPA is performed, after inter-frequency handover using UL DCH.
2.9.1.1
Benefits End-user benefits The end-user benefits from fast HSPA inter-frequency handover and higher data throughput during compressed mode.
116
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Operator benefits This feature benefits the operator as follows: • • •
2.9.1.2
HSPA inter-frequency handover (HO) is done faster when channel type switching to DCH is not needed first The inter-system handover (ISHO) and redirection from HSPA to LTE becomes more reliable when LTE cells are measured before ISHO or redirection. This feature reduces signaling for RNC, Iub, BTS, and the UE as channel type switching to DCH is not needed.
Requirements Software requirements Table 58: Software requirements lists the software required for this feature. Table 58
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi OMS Direct RNC
Flexi BTS
RU50
Flexi Direct RU50
RN8.0
mcRNC4.1
ADA6.0
Support not WN9.0 required
Flexi Lite BTS
Flexi 10 BTS
NetAct
MSC
SGSN
MGW
WL9.1
WN9.1
NetAct8 EP1 1)
Support not Support not Support not 3GPP Relrequired required required 6
UE
NetAct 8 EP2 (NetAct 15) 2)
1) for RU50 2) for RU50 EP1 and Flexi Direct RU50
Hardware requirements This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF or Flexi Lite BTS WCDMA.
2.9.1.3
Functional description The RAN1668: HSUPA Compressed Mode for LTE and Inter- frequency Handover feature introduces HSUPA compressed mode (CM) for LTE and inter-frequency measurements, without UL channel type switching to DCH.
Issue: 01F
DN09146788
117
Radio resource management features
RU50 Feature Descriptions and Instructions
HSUPA CM configuration for inter-frequency measurements is achieved using a singleframe method with 7 (or less)-slot transmission gap pattern (TGP). HSUPA CM configuration for LTE measurements is achieved using a double-frame method with 7 (or more)-slot TGP. In Nokia implementation the TGP for single frame method is always fixed to 7 slots and for double frame method, the TGP is fixed to 10 slots. Compressed mode is supported while the radio bearers are mapped to E-DCH in uplink and SRBs are mapped on DCH or E-DCH. This also includes the case where DL SRB is mapped to DCH or HSDPA. Compressed mode can also be activated when the UE’s RAB combination is reduced to SRBs + PS NRT mapped to 0/0. In such case, SRBs are mapped to DCH transport only. Avoiding the channel-type switch to UL DCH reduces the total handover execution time up to 1.5 s. Also, the high HSUPA throughput can be experienced during compressed mode. For inter-system handover to LTE, only the basic HSUPA compressed mode support is covered in this feature. HSUPA compressed mode for LTE is used by the RAN2980: Measurement based LTE Layering feature and the RAN2264: Smart LTE Handover feature. All the control, signaling, and RRM decision making of measurement-based redirection and PS HO to LTE are included in those features.
g
In Nokia implementation HSUPA CM is never enabled independently. It is always done in tandem with HSDPA CM, that is CM is always enabled in both directions together
g
Note that HSUPA compressed mode is not supported over Iur.
2.9.1.4
System impact Interdependencies between features The RAN1276: HSDPA Inter-frequency Handover feature is a prerequisite for using this feature. The RAN1276: Inter-frequency Handover feature covers the following direct handover cases: • • • • •
DCH/HSDPA to DCH/HSDPA DCH/HSDPA to HSUPA/HSDPA DCH/HSDPA to DCH/DCH DCH/DCH to DCH/HSDPA DCH/DCH to HSUPA/HSDPA
With the RAN1668: HSUPA Compressed Mode For LTE and Inter-frequency Handover feature the following direct handover cases are supported in addition: • • •
HSUPA/HSDPA to DCH/HSDPA HSUPA/HSDPA to HSUPA/HSDPA HSUPA/HSDPA to DCH/DCH
The feature also introduces compressed mode support for the following RAB combination (the transport configuration post handover can be any of the above listed): •
118
DCH/DCH (0/0) + SRBs on DCH
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Impact on interfaces HSUPA CM is configured and activated using the following messages: •
over Iub: – –
•
NBAP: Radio Link Setup Request procedure NBAP: Radio Link Re-configuration Procedure (Synchronized)
over Uu: – – –
RRC: Transport Channel Re-configuration RRC: Physical Channel Re-configuration RRC: Measurement Control (Setup)
HSUPA CM is deactivated using the following messages: •
over Iub: – –
•
over Uu: – – –
g
NBAP: Compressed Mode Command NBAP: Radio Link Re-configuration Procedure (Synchronized only)
RRC: Transport Channel Re-configuration RRC: Physical Channel Re-configuration RRC: Measurement Control (Release)
Note that only messages supported by Nokia are listed.
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 as follows: • • •
HSPA IFHO is done faster, as channel type switching to DCH is not needed first. ISHO and redirection from HSPA to LTE becomes more reliable, as the LTE cells can be measured before ISHO or redirection. During UL compressed mode, the UL throughput is degraded, since the UE cannot transmit in every slot. The reduction depends on the configured transmission time interval and on whether the UE is performing intra- or inter-system measurement. With this feature, the impact on UL throughput is smaller, since the time taken to perform UL CTS to R99 DCH is totally avoided.
This feature impacts system capacity as follows: • •
Issue: 01F
Signaling for RNC, Iub, BTS, and UE is reduced, as channel type switching to DCH is not needed for enabling CM. In FSM3, a maximum 50% of the users with CM active can be supported, that is, a maximum 50% of the users can have CM active at the same time.
DN09146788
119
Radio resource management features
2.9.1.5
RU50 Feature Descriptions and Instructions
RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms There are no alarms related to this feature.
Measurements and counters Table 59: New counters lists counters introduced with this feature. Table 59
New counters
Counter ID
Counter name
Measurement
M1002C676
ALLOCATION FOR HSUPA IFHO COMPRESSED MODE
Traffic (RNC)
M1002C677
ALLOCATION DURATION FOR HSUPA IFHO COMPRESSED MODE
Traffic (RNC)
M1002C678
REJECTED HSUPA IFHO COMPRESSED MODE
Traffic (RNC)
M1002C692
ALLO FOR COM MODE LTE
Traffic (RNC)
M1002C693
ALLO DURA FOR COM MODE LTE
Traffic (RNC)
M1006C312
HSUPA IFHO COMPRESSED MODE FAIL DUE TO UE
RRC signalling
M1006C313
LTE COMPRESSED MODE FAIL DUE TO UE
RRC signalling
M1008C294
HSUPA IFHO ATTEMPTS
Intra System Hard Handover (RNC)
M1008C295
SUCCESSFUL HSUPA IFHO
Intra System Hard Handover (RNC)
Table 60: Related existing counters lists existing counters related to this feature. Table 60
120
Related existing counters
Counter ID
Counter name
Measurement
M1002C623
ALLOCATION FOR HSDPA IFHO COMPRESSED MODE
Traffic (RNC)
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 60
Radio resource management features
Related existing counters (Cont.)
Counter ID
Counter name
Measurement
M1002C624
ALLOCATION DURATION FOR HSDPA IFHO COMPRESSED MODE
Traffic (RNC)
M1002C625
REJECTED HSDPA IFHO COMPRESSED MODE
Traffic (RNC)
Key performance indicators Table 61: New key performance indicators lists key performance indicators introduced with this feature. Table 61
New key performance indicators
KPI ID
KPI name
RNC_5301a
HSUPA Compressed Mode allocation success rate
There are no modified and existing key performance indicators related to this feature.
Parameters Table 62: New parameters lists parameters introduced with this feature. Table 62
New parameters
Full name
Abbreviated name
Managed object
TGPL for HSPA Inter Frequency Measurement
TGPLHSPAInterFreq
RNHSPA
Table 63: Modified parameters lists parameters modified by this feature. Table 63
Issue: 01F
Modified parameters
Full name
Abbreviated name
Managed object
BTS Support For HSPA CM
BTSSupportForHSPACM
WBTS
Max number of UEs in HSDPA CM due to critical HO
MaxNumberUEHSPACmHO
WCEL
Max number of UEs in HSDPA CM due to NCHO
MaxNumberUEHSPACmNCHO
WCEL
DN09146788
121
Radio resource management features
RU50 Feature Descriptions and Instructions
Table 64: Related existing parameters lists existing parameters related to this feature. Table 64
Related existing parameters
Full name
122
Abbreviated name
Managed object
Serving HS-DSCH cell change and SHO HSDPAMobility on/off switch
RNFC
Gap position single frame
GAPPositionSingleFrame
RNC
Gap position single frame
GAPPositionSingleFrame
RNMOBI
Recovery Period Power in UL Compressed Mode
UplinkRecoveryPeriodPowerMode
RNAC
Initial transmit power in uplink compressed mode
UplinkInitialTransmitPowerMode
RNC
UL Delta SIR1 in compressed mode
DeltaSIRUplink
RNC
UL Delta SIR1 in compressed mode
DeltaSIRUplink
WRAB
DL Delta SIR1 in compressed mode
DeltaSIRDownlink
RNC
DL Delta SIR1 in compressed mode
DeltaSIRDownlink
WRAB
UL Delta SIR after1 in compressed mode
DeltaSIRAfterUplink
RNC
UL Delta SIR after1 in compressed mode
DeltaSIRAfterUplink
WRAB
DL Delta SIR after1 in compressed mode
DeltaSIRAfterDownlink
RNC
DL Delta SIR after1 in compressed mode
DeltaSIRAfterDownlink
WRAB
Compressed Mode: Alternative scrambling code
AltScramblingCodeCM
WCEL
Compressed mode master switch
CmMasterSwitch
RNFC
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
2.9.1.6
Radio resource management features
Sales information Table 65
Sales information
BSW/ASW
SW component
License control in network element
ASW
HSPA
RNC LK
2.9.2 Activating RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover Purpose Follow this procedure to activate this feature. For more information on the feature, see the Description of RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover in WCDMA RAN, rel. RU50, feature descriptions. Before you start Restart of the RNC is not required after the activation of this feature. This procedure does not cause downtime, and can be activated at any time of the day. Make sure you have access to the following applications: • • •
OMS Element Manager Application Launcher Man-machine interface (MMI)
Before activating this feature, activate the RAN1276: HSDPA Inter-frequency Handover feature (see Activating RAN1276: HSDPA Inter-frequency Handover). Before activating this feature make sure that basic HSUPA and HSDPA mobility are enabled. This feature is controlled by the long-term ON/OFF license key. For more information on licensing, see Licensing.
g
The feature code for this feature is 4783. To set the feature state to ON, use the following command: • •
g
Issue: 01F
for IPA-RNC: ZW7M:FEA=4783:ON; for mcRNC: set license feature-mgmt code 0000004783 feature-admin-state on No license is required for Flexi Direct RNC.
DN09146788
123
Radio resource management features
RU50 Feature Descriptions and Instructions
1
Open the OMS Element Manager.
2
Go to the Topology.
3
Expand the ROOT.
4
Expand the RNC object.
5
Expand the RNHSPAs folder.
6
Configure the RNHSPA object: a) Select Edit Parameters from the RNHSPA object. b) In Packet Scheduler tab set the TGPLHSPAInterFreq parameter to 5 if this feature is used for inter-frequency handovers or/and set the value of the TGPLForLTEMeas parameter to 6 if this feature is used for LTE handover or layering. Set the TGPLAMRHSDPAInterFreq parameter and the TGPLHSDPAInterFreq parameter to default value 4. c) Navigate back to the RNC object.
7
Expand the WBTSs folder.
8
Configure the WBTS object: a) Select Edit Parameters from the WBTS object. b) In Packet Scheduler tab set the value of the BTSSupportForHSPACM parameter to "HSPA CM supported". c) Navigate back to the RNC object.
9
Expand the RNFCs folder.
10 Enable compressed mode by configuring the RNFC object: a) Select Edit Parameters from the RNFC object. b) In Packet Scheduler tab set the CmMasterSwitch parameter to "Used". c) Navigate back to the RNC object.
11 Go to the WCEL object by the following path: RNC object ► WBTSs folder ► WBTS object ► WCELs folder ► WCEL object
124
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
12 Configure the WCEL object. a) Select Edit Parameters from the WCEL object. b) In Packet Scheduler tab, set value greater than 0 for the parameter MaxNumberUEHSPACmHO . c) In Packet Scheduler tab, set value greater than 0 for the parameter MaxNumberUEHSPACmNCHO.
2.9.3 Verifying RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover Purpose Follow this procedure to verify that this feature works properly in the network. Before you start 1. Make sure that the RAN1668: HSUPA Compressed Mode for LTE and Interfrequency Handover feature is activated in the RNC (see Activating RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover). 2. Set BTS 1 CELL 2 as inter-frequency adjacent cell of BTS 1 CELL 1. 3. Set the values of FMCI - IFHOcauseCPICHEcNo and FMCI-IFHOcauseCPICHrscp parameters to 1 ('Enabled') in FMCI_ID assigned to BTS 1 CELL 1 (HsdpaFmciIdentifier or NrtFmciIdentifier parameter).
1
Make an NRT interactive call with the UE (Rel-6/Rel-7/Rel-8/Rel-9), RAB on HSPA in BTS 1 CELL 1 and send data.
2
Adjust the signal of BTS 1 CELL 1, so that it is lower than the threshold value of the HHoEcNoThreshold parameter or the HHoRscpThreshold parameter.
3
Adjust the signal of BTS 1 CELL 2, so that it is stronger than the signal of BTS 1 CELL 1.
4
Release the call.
5
Collect the log for "step 1", "step 2", "step 3", and "step 4" and analyze the log.
6
Verify that: • •
Issue: 01F
The UE sends out RRC: MEASUREMENT REPORT with Measured Results for intra-frequency event 1f. In NBAP message RADIO LINK RECONFIGURATION PREPARE the values of IEs in Transmission Gap Pattern Sequence Information are as follows:
DN09146788
125
Radio resource management features
RU50 Feature Descriptions and Instructions
TGPS Identifier xx tGSN xx tGL1 7 tGD xx tGPL1 5 uL/DL mode UL/DL Downlink Compressed Mode Method sf/2 Uplink Compressed Mode Method sf/2 Downlink Frame Type xx DeltaSIR1 xx DeltaSIRafter1 xx
g
“xx” means that the value of the IE is not relevant for verifying this feature. •
In RRC message PHYSICAL CHANNEL RECONFIGURATION the values of IEs are as follows: tgp-SequenceList {{ tgpsi xx, tgps-Status activate : { tgcfn xx }, tgps-ConfigurationParams { tgmp fdd-Measurement, tgprc xx, tgsn xx, tgl1 7, tgd xx, tgpl1 5, rpp xx, itp xx, ul-DL-Mode ul-and-dl : { ul sf-2, dl sf-2 }, dl-FrameType dl-FrameTypeA, deltaSIR1 xx, deltaSIRAfter1 xx }}}
g
“xx” means that the value of the IE is not relevant for verifying this feature. •
Counters M1002C676 ALLO_CM_HSUPA_IFHO and M1002C623 ALLO_CM_HSDPA_IFHO are updated: 1 is added to their value.
Expected outcome HSUPA compressed mode starts successfully and call release is normal. Log’s data are as specified above and counters are updated.
2.9.4 Deactivating RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover Purpose Follow this procedure to deactivate this feature.
126
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
1
Open the OMS Element Manager.
2
Go to the Topology.
3
Expand the ROOT.
4
Expand the RNC object.
5
Expand the WBTSs folder.
6
Configure the WBTS object: a) Select Edit Parameters from the WBTS object. b) In Packet Scheduler tab set the value of the BTSSupportForHSPACM parameter to "Only DCH CM supported" or "HSDPA CM supported".
Further information After deactivating the feature, set the feature state to OFF using the following command: •
for IPA-RNC ZW7M:FEA=4783:OFF;
2.10 RAN2510: In-bearer Application Optimization 2.10.1 Description of RAN2510: In-bearer Application Optimization Introduction to the feature Without QoS-based air interface scheduling all radio bearers, interactive and background, are treated equally. The RAN1262: QoS Aware HSPA Scheduling feature allows service and subscriber differentiation according to radio access bearer parameters (interactive or background). The RAN2509: Application Aware RAN feature introduces prioritization between different radio bearers based on the packets' content. The content is verified using Deep Packet Inspection (DPI). With the RAN2509: Application Aware RAN feature, scheduling priority for a radio bearer can be upgraded or downgraded according to application priority. The RAN2510: In-bearer Application Optimization feature introduces service prioritization within one bearer. Latency-sensitive user traffic has different queueing and is prioritized ahead of non-latency-sensitive traffic.
Issue: 01F
DN09146788
127
Radio resource management features
2.10.1.1
RU50 Feature Descriptions and Instructions
Benefits End-user benefits Service-specific flow prioritization within a single bearer allows improved QoE for multitasking users. For example, user's web-browsing session can be prioritized over a large file download by the same user.
Operator benefits The RAN2510: In-bearer Application Optimization feature enables operators to offer a better application user experience with the same system capacity. With this solution the capacity is used in more optimal manner. The additional traffic control provided by this feature allows the operator to defer investment in congested cells or backhaul links.
2.10.1.2
Requirements Software requirements Table 66: Software requirements lists the software required for this feature. Table 66
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
Flexi BTS
RU50 EP1
Not planned RN8.1
mcRNC4.1
Not planned OMS3.1
Support not required
Flexi Lite BTS
Flexi 10 BTS
MSC
SGSN
UE
Not relevant Support not required
NetAct
MGW
Support not Support not Support not Support not required required required required
Support not required
Hardware requirements This feature requires CDSP-DH card in the IPA-RNC.
2.10.1.3
Functional description Functional overview In the RNC PDCP layer, the user flow is prioritized according to deep packet inspection (DPI) marking received from the core network (CN). The DPI engine in the CN marks the headers of the inner IP packets with the differentiated service code point (DSCP) values. The DSCP-marked data is sent to the PDCP layer in the RNC and mapped to the PDCP queues according to the assigned DSCP values. There are two queues in the RNC PDCP layer:
128
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
• •
Radio resource management features
for packets marked as latency-sensitive, called high-priority queue for the non-latency-sensitive packets, called low-priority queue
The PDCP layer performs Weighted Fair Queuing, which means that it serves high priority queue with a bigger weight. As a result, high-priority packets get relatively higher bandwidth and lower delay than low-priority packets.
g
If the 100% weight is assigned to high-priority queue, the low-priority queue is then scheduled only when high-priority queue becomes empty. This may lead to starvation of traffic in low-priority queue and is not a recommended configuration. Figure 8
Weighted Fair Queuing in PDCP layer of RNC
The DSCP code values in the inner IP packet headers are used only inside the PDCP of RNC when the RAN2510: In-bearer Application Optimization feature is enabled. Figure 9
End-user benefits of the RAN2510: In-bearer Application Optimization feature
When the RAN2510: In-bearer Application Optimization feature along with the Iur are enabled, then the data is prioritized inside SRNC before sending it over the Iur. Activating this feature affects both Iub and Iur interfaces.
Issue: 01F
DN09146788
129
Radio resource management features
2.10.1.4
RU50 Feature Descriptions and Instructions
System impact Interdependencies between features
g
The RAN2510: In-Bearer Application Optimization feature requires that Deep Packet Inspection (DPI) is activated in the Core Network (CN). In case of Nokia Core, DPI is implemented in Flexi Network Gateway. The configuration of this feature has to be in line with CN DPI configuration. Other vendor of DPI is also allowed. In case of Nokia Core, the RAN2510: In-Bearer Application Optimization feature requires the FC085_001011: DSCP Marking for Services feature in the CN. For better network optimization, the following features may be used along with the RAN2510: In-bearer Application Optimization feature: • • •
RAN1110: HSDPA Congestion Control for maintaining the maximum load over Iub without causing congestion RAN2509: Application Aware RAN for dynamic prioritization between bearers RAN1262: QoS Aware HSPA Scheduling for subscriber differentiation
Impact on interfaces This feature affects both Iub and Iur interfaces.
Impact on commands There are no commands related to this feature.
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.
2.10.1.5
RAN2510: In-bearer Application Optimization management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms There are no alarms related to this feature.
Measurements and counters The RAN2510: In-bearer Application Optimization feature performance can be measured with M1035-type counters added to DSCP level. The M1035C3 counter provides information per DSCP code marking of Iu-PS user plane package received by RNC. The M1035C4-C7 counters provide RNC-level packet statistics per priority queue (that is summation of packets of all DSCPs) and are updated for DSCP-999 special object. Table 67: New counters lists counters introduced with this feature.
130
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 67
Radio resource management features
New counters
Counter ID
Counter name
Measurement
M1035C3
PACKETS FROM CN MAPPED TO HS-DSCH OR R99
DSCP Statistics
M1035C4
PACKETS FROM CN MAPPED TO LOW PRIORITY QUEUE
DSCP Statistics
M1035C5
PACKETS FROM CN MAPPED TO HIGH PRIORITY QUEUE
DSCP Statistics
M1035C6
LOW PRIORITY PACKETS DROPPED
DSCP Statistics
M1035C7
HIGH PRIORITY PACKETS DROPPED
DSCP Statistics
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table 68: New parameters lists parameters introduced with this feature. Table 68
New parameters
Full name
Abbreviated name
Managed object
In Bearer Application Optimization High Queue DSCP Codes Part1
IBAODSCPHighPrioQPart1
RNHSPA
In Bearer Application Optimization High Queue DSCP Codes Part2
IBAODSCPHighPrioQPart2
RNHSPA
In Bearer Application Optimization High Queue Weight
IBAOHighQueueWeight
RNHSPA
In Bearer Application Priority Enabled
InBearerAppPrioEnabled
RNHSPA
Table 69: Modified parameters lists parameters modified with this feature. Table 69
Issue: 01F
Modified parameters
Full name
Abbreviated name
Managed object
RNC Options
RncOptions
RNC
DN09146788
131
Radio resource management features
2.10.1.6
RU50 Feature Descriptions and Instructions
Sales information Table 70
Sales information
BSW/ASW
SW component
License control in network element
ASW
HSPA
RNC LK
2.10.2 Activating RAN2510: In-Bearer Application Optimization Purpose Follow this procedure to activate the RAN2510: In-Bearer Application Optimization feature in SRNC. 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.
g
The RAN2510: In-Bearer Application Optimization feature requires that Deep Packet Inspection (DPI) is activated in the Core Network (CN). In case of Nokia Core, DPI is implemented in Flexi Network Gateway. The configuration of this feature has to be in line with CN DPI configuration. Other vendor of DPI is also allowed. In case of Nokia Core, the RAN2510: In-Bearer Application Optimization feature requires the FC085_001011: DSCP Marking for Services feature in the CN. Activate the license of the RAN2510: In-Bearer Application Optimization feature using Inbearer Service Optimization license key. To set the feature state to ON, use the following command: • •
for IPA-RNC: ZW7M:FEA=3421:ON; for mcRNC: set license feature-mgmt code 0000003421 feature-admin-state on
For information on managing licenses, see Licensing. Before activating the RAN2510: In-Bearer Application Optimization feature configure the following RNHSPA parameters: • • •
Expand the RNC object and then expand the RNFC object.
4
Configure the RNFC object: a) Right-click on the RNFC object and select Edit parameters. b) On the Packet Scheduler tab, set the value of the InBearerAppPrioEnabled parameter to Enabled.
Further information
g
For improving the TCP session establishment time, it is recommended to mark the packets involved in the session establishment with DSCP code 0 and then assign the DSCP code 0 to high-priority queue.
2.10.3 Verifying RAN2510: In-Bearer Application Optimization Purpose Follow this procedure to verify if the RAN2510: In-Bearer Application Optimization feature works properly in the network.
g
This verification procedure is vaild for HSDPA. Before you start Make sure you have access to the following applications: • • •
OMS Element Manager RNW Measurement Management RNW Measurement Presentation
Make sure the Deep Packet Inspection is activated in the CN and DSCP is being assigned to application packets. To verify this feature, maintain the application data transfer with 11 UEs under a single cell: • •
one UE maintaining both HTTP and FTP transfer 10 UEs maintaining only the FTP transfer
The verification needs to be performed in congested scenario: monitoring the peformance of one UE with active HTTP+FTP transfer while 10 additional UEs have only FTP transfer ongoing in the same cell. This produces the load in the cell so that the HSDPA scheduling is affected.
Issue: 01F
DN09146788
133
Radio resource management features
g
RU50 Feature Descriptions and Instructions
It is also possible to verify the feature with only one UE. For this purpose, the BTS's air interface capacity must be limited, so that RNC cannot schedule all the required data at once. Then the configured prioritization is performed.
1
Set the DPI marking of HTTP packets with DSCP15. In case of Nokia Core, DPI is implemented in Flexi Network Gateway (Flexi NG) For more information on configuring Flexi NG, see the Service Awareness document available in NOLS at this location: Product Information Center ► Core Network ► Mobile Packet Core ► Flexi NG ► NG3.0 ► Flexi Network Gateway, Rel. 3.1, Operating Documentation, v. 3 You can access NOLS at https://online.portal.nsn.com. Accessing NOLS requires authentication.
2
Open the OMS Element Manager.
3
Go to Topology and expand the ROOT directory.
4
Expand the RNC object and then expand the RNHSPA object.
5
Configure the RNHSPA object: a) Right-click on the RNHSPA object and select Edit parameters. b) On the Packet Scheduler tab, set the value of DSCP code 15 of the IBAODSCPHighPrioQPart1 parameter to True. In this configuration, it equals assigning HTTP packets to high-priority queue. Other packets, with DSCPs set to False, are assigned to low-priority queue. c) On the Packet Scheduler tab, set the value of the IBAOHighQueueWeight parameter to 90%.
6
With one of the UEs initiate the data transfer with HTTP and FTP applications. With other 10 UEs initiate only the FTP transfer. The 10 UEs with FTP transfer active are producing the traffic load to have the cell congested.
7
Open the RNW Measurement Management application.
8
With counters M1035C3-M1035C7, check if the HTTP application share of the overall UE data is the same as configured with the IBAOHighQueueWeight parameter. Check the values of the following counters and verify if they match the configured weight: • •
134
M1035C3 PACKETS FROM CN MAPPED TO HS-DSCH OR R99 M1035C4 PACKETS FROM CN MAPPED TO LOW PRIORITY QUEUE
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
• • •
Radio resource management features
M1035C5 PACKETS FROM CN MAPPED TO HIGH PRIORITY QUEUE M1035C6 LOW PRIORITY PACKETS DROPPED M1035C7 HIGH PRIORITY PACKETS DROPPED
For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. After the measurements, the values of the counters can be viewed in RNW Measurement Presentation application. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentation in Managing and viewing RNC measurements. Further information Whether the RAN2510: In-Bearer Application Optimization feature works properly is visible in the HTTP throughput. In this configuration when the capacity of the air interface is limited, the HTTP share should be higher when the RAN2510: In-Bearer Application Optimization feature is enabled. Also the throughput difference between HTTP and FTP applications should be visible. The FTP data should be lower when the RAN2510: InBearer Application Optimization feature is enabled. Expected outcome If there is only one radio bearer, the amount of packets is equal to the number of packets in low and high priority queues plus possible dropped packets. Check if the dropped counter indicates dropped packets and if packet amount of high, low, and dropped packets match the overall packet amount measured for the RAB. Troubleshooting actions Ensure that there is enough application data traffic for verification purposes and the time of maintaining the application data traffic was long enough. Check if there is data dropping due to overload actions inside RNC that prevents the prioritization. Check if the CN DPI engine is configured properly.
2.10.4 Verifying RAN2510: In-Bearer Application Optimization and RAN2509: Application Aware RAN in the RNC when HTTP traffic is prioritized over FTP traffic Purpose Follow this procedure to verify if the RAN2510: In-Bearer Application Optimization feature and the RAN2509: Application Aware RAN feature work properly in the network when in configuration of both features HTTP data is prioritized over FTP data.
g
This verification procedure is vaild for HSDPA. Before you start Make sure you have access to the following applications: • •
Issue: 01F
OMS Element Manager RNW Measurement Management
DN09146788
135
Radio resource management features
RU50 Feature Descriptions and Instructions
RNW Measurement Presentation
•
Make sure the Deep Packet Inspection is activated in the CN and DSCP is being assigned to application packets. Make sure the following features are activated: RAN2510: In-Bearer Application Optimization RAN2509: Application Aware RAN
• •
g
When using both theRAN2509: Application Aware RAN feature and the RAN2509: Application Aware RAN feature, make sure their configuration is aligned. This means that for the packets marked with a certain DSCP code they are both performing promotion or demotion. Make sure that BTS supports dynamic SPI change functionality of the RAN2509: Application Aware RAN feature by checking the AppAwareRANCapability WCEL parameter, which is reported by BTS to GOMS. The value AAR Capable means that BTS supports the feature in the cell and the value AAR Not Capable means that BTS does not support the feature in the cell. To verify this feature, maintain the application data transfer with 11 UEs under a single cell: one UE maintaining both HTTP and FTP transfer 10 UEs maintaining only the FTP transfer
• •
The verification needs to be performed in congested scenario: monitoring the performance of one UE with active HTTP+FTP transfer while 10 additional UEs have only FTP transfer ongoing in the same cell. This produces the load in the cell so that the HSDPA scheduling is affected.
g
It is also possible to verify the feature with only one UE. For this purpose, the BTS's air interface capacity must be limited, so that RNC cannot schedule all the required data at once. Then the configured prioritization is performed.
1
Set the DPI marking of HTTP packets with DSCP50 and FTP packets with DSCP30. In case of Nokia Core, DPI is implemented in Flexi Network Gateway (Flexi NG) For more information on configuring Flexi NG, see the Service Awareness document available in NOLS at this location: Product Information Center ► Core Network ► Mobile Packet Core ► Flexi NG ► NG3.0 ► Flexi Network Gateway, Rel. 3.1, Operating Documentation, v. 3 You can access NOLS at https://online.portal.nsn.com. Accessing NOLS requires authentication.
136
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
2
Open the OMS Element Manager.
3
Go to Topology and expand the ROOT directory.
4
Expand the RNC object and then expand the RNHSPA object.
5
Configure the RNHSPA object: a) Right-click on the RNHSPA object and select Edit parameters. b) On the Packet Scheduler tab, set the value of DSCP code 50 of the IBAODSCPHighPrioQPart2 parameter to True. In this configuration, it equals assigning HTTP packets to high-priority queue. Other packets, with DSCPs set to False, are assigned to low-priority queue. c) On the Packet Scheduler tab, set the value of the IBAOHighQueueWeight parameter to 90%. d) On the Packet Scheduler tab, set the value of the InitialSPINRT parameter to 5.
6
Establish two application groups and configure the prioritization. a) In the RNHSPA object on the Packet Scheduler tab, right-click on the Application Aware RAN Configuration Table (AARConfigTable) folder and select Add Item. An Item folder appears. Each Item stands for one application group. b) Using the AppGrpId parameter, establish the first application group with id 1 and configure it in the following way: • • •
set the value of the DSCPCode1 parameter to 50 set the value of the Precedence parameter to 0 set the value of the TargetSPIforSPI5 parameter to 9
c) Using the AppGrpId parameter, establish the second application group with id 2 and configure it in the following way: • • •
Issue: 01F
set the value of the DSCPCode1 parameter to 30 set the value of the Precedence parameter to 1 set the value of the TargetSPIforSPI5 parameter to 1
DN09146788
137
Radio resource management features
RU50 Feature Descriptions and Instructions
7
With one of the UEs, initiate the data transfer with HTTP and FTP applications. With the other 10 UEs, initiate only the FTP transfer.
8
Open the RNW Measurement Management application.
9
With counters M1035C3-M1035C7, check if the HTTP application share of the overall UE data is the same as configured with the IBAOHighQueueWeight parameter. Check the values of the following counters and verify if they match the configured weight: • • • • •
M1035C3 PACKETS FROM CN MAPPED TO HS-DSCH OR R99 M1035C4 PACKETS FROM CN MAPPED TO LOW PRIORITY QUEUE M1035C5 PACKETS FROM CN MAPPED TO HIGH PRIORITY QUEUE M1035C6 LOW PRIORITY PACKETS DROPPED M1035C7 HIGH PRIORITY PACKETS DROPPED
For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. After the measurements, the values of the counters can be viewed in RNW Measurement Presentation application. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentation in Managing and viewing RNC measurements.
g
To make a counter-based comparison between the average packet amount per queue and the configured weight the data transfer initiated with UEs has to be maintained for an hour. However, if there is continuous FTP data transfer and both the RAN2510: In-Bearer Application Optimization and the RAN2509: Application Aware RAN feature work properly, any download of HTTP data should be done significantly shorter. This can be easily recognized by the UE user. Expected outcome When there is continuous HTTP and FTP data transferat the same time, the expectation is to have 90% of HTTP data and 10% FTP data. When HTTP+FTP data is present, the priority of the data is 9 and with only FTP data present, the priority of the data is 1. Note that in this configuration when HTTP data is not present, the RAN2510: In-Bearer Application Optimization feature queue does not perform any weighted fair queuing. Unexpected outcome No differentiation in HTTP and FTP application data. Wrong priority in air interface. Wrong share of data (not following the PDCP priority queue weight). Troubleshooting actions Check that there is data available in both priority queues inside the RNC. Check if there is data dropping due to overload actions inside RNC that prevents the prioritization. Check if the CN DPI engine is configured properly.
138
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
2.10.5 Deactivating RAN2510: In-Bearer Application Optimization Purpose Follow this procedure to deactivate the RAN2510: In-Bearer Application Optimization feature.
1
Open the OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object and then expand the RNFC object.
4
Configure the RNFC object: a) Right-click on the RNFC object and select Edit parameters. b) On the Packet Scheduler tab, set the value of the InBearerAppPrioEnabled parameter to Disabled.
Further information When the RAN2510: In-Bearer Application Optimization feature is to be disabled temprarily, it is enough to change the InBearerAppPrioEnabled paremeter value to Disabled. If this feature is not going to be used in RNC anymore, it is recommended to remove the In-bearer Service Optimization license from the RNC.
2.11 RAN2980: Measurement Based LTE Layering 2.11.1 Description of RAN2980: Measurement Based LTE Layering Introduction to the feature The RAN2717: Smart LTE Layering feature supports blind redirection from WCDMA to LTE, that is without prior measurements of LTE layer. It is a good alternative when, for example, WCDMA and LTE cells are co-located and have largely overlapping coverage areas. However, UEs could face problem in cell reselection which can cause unsatisfying end-user experience. The RAN2980: Measurement Based LTE Layering feature supports the redirection of UE to LTE layer only if measurement results indicate that LTE-capable UE could camp on LTE cell successfully. This ensures seamless LTE camping even if the WCDMA cell has only partial LTE coverage. Both FDD-LTE and TDD-LTE are supported.
Operator benefits Operator benefits from having two types of WCDMA to LTE redirections available: with and without a measurement. Operator can choose if the trigger activates with- or withoutmeasurement-based redirection.
2.11.1.2
Requirements Software requirements Table 71: Software requirements lists the software required for this feature. Table 71
Software requirements
RAS
Flexi Direct
IPA-RNC
mcRNC
Flexi Direct RNC
OMS
Flexi BTS
RU50
Flexi Direct RU50
RN8.0
mcRNC4.1
ADA6.0
OMS3.0 1)
WN9.0
OMS3.1 2) IHO 6.0 3)
Flexi Lite BTS
Flexi 10 BTS
NetAct
MSC
SGSN
MGW
WL9.1
WN9.1
NetAct 8 EP1 1)
Support not Support not Support not required required required
UE
3GPP Rel-8
NetAct 8 EP2 (NetAct 15) 2) 3)
1) for RU50 2) for RU50 EP1 3) for Flexi Direct RU50
Hardware requirements This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF or Flexi Lite BTS WCDMA.
140
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
2.11.1.3
Radio resource management features
Functional description Functional overview RRC connection release with the redirection command to LTE can be used for moving LTE-capable UE to LTE, if compressed mode measurements indicate that LTE coverage is available. Each of the following events triggers the compressed mode measurements for LTE: • • • •
RRC state change from Cell_DCH to Cell_FACH, Cell_PCH, or URA_PCH channel type change from HSDPA/HSPA to DCH/DCH CTS CS call release when UE has CS and PS connection active periodic trigger with operator-definable timer: When LTE-capable UE enters the Cell_DCH state having only PS RAB(s), its timer (controlled with LTEPeriodicTriggerTimer parameter) is set. At the expiry of timer, measurements for redirection to LTE are started. If measurement results lead to decision to redirect UE to LTE system, UE is then redirected. If the measurement results do not trigger UE’s redirection to LTE and UE still continues data activity, then the timer is reset. At the expiry of the timer, measurements are started again.
First three of the above mentioned triggers are also used in the RAN2717: Smart LTE Layering feature. The RAN2980: Measurement Based LTE Layering feature introduces the fourth trigger for UEs keeping long Cell_DCH reservations for PS services. Note that when the RAN2980: Measurement Based LTE Layering feature is active, all four triggers are valid and there is no need to have the RAN2717: Smart LTE Layering feature installed separately. In uplink, DCH is used during compressed mode. HSPA compressed mode, also including HSUPA compressed mode, is supported by the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature. If the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature is not implemented in the network, the RAN2980: Measurement Based LTE Layering feature supports HSDPA/DCH, and DCH/DCH. If there is HSUPA (E-DCH) in uplink, then it is reconfigured to DCH, before initiating the compressed mode measurements. LTE-capable UEs are checked for their measurement capabilities. UEs with dual receiver do not require compressed mode for creating gaps to listen to other frequencies. For such UEs, compressed-mode-related information is not required and thus not sent to them. The RAN2980: Measurement Based LTE Layering feature also offers a possibility to limit the UE's redirection to LTE. When the limitation is activated, redirection to LTE is allowed only to UEs that are indicated to be redirected from LTE to WCDMA and/or are indicated to be in WCDMA because of a CS fallback (CSFB). Each limitation guarantees that the UE has the LTE subscription and that the LTE coverage was available when the UE came to WCDMA. The first limitation is activated with the 002:1916 RN60_MAINT_41 PRFILE parameter and the latter with the CSFBDetection RNMOBI parameter. If WCDMA cell load is not high and users can be provided good enough experience within WCDMA layer, measurements and redirection to LTE can be bypassed. RNC load level parameter can be used to define if the load is low enough for keeping UEs in WCDMA. With the RAN2980: Measurement Based LTE Layering feature operator can:
Issue: 01F
DN09146788
141
Radio resource management features
•
• • • • • •
RU50 Feature Descriptions and Instructions
enable LTE redirection without measurements for the first three redirection triggers (also provided with the RAN2717: Smart LTE Layering feature) and measurementbased redirection to LTE for the periodic trigger establish measurement-based redirection to LTE for all four redirection triggers enable measurement-based and/or blind redirection only for the UEs that have been indicated to be moved to WCDMA because of CS fallback enable measurement-based redirection only for the UEs that have been indicated to be redirected to from LTE to WCDMA select the frequencies to which UEs in Cell_DCH state are redirected in LTE system as well as define camping priorities for those frequencies exclude some LTE carrier frequencies from LTE target camping layers disable the WCDMA cell load check which will result in automatic LTE redirection every time the LTE coverage is available
In cases where measurement is configured to be used before redirection, but the measurements are not supported, redirection is done blindly. This happens for example when UE does not support LTE measurements. When blind redirection takes place, LTE frequency ordering is performed as specified in functional description of RAN2717: Smart LTE Layering.
2.11.1.4
System impact Interdependencies between features The RAN2067: LTE Interworking feature provides support for LTE cell reselection in idle mode Cell_PCH and URA_PCH states.
Impact on interfaces This feature affects Uu and Iub interfaces and uses standard signaling procedures.
Impact on commands There are no commands related to this feature.
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.
2.11.1.5
RAN2980: Measurement Based LTE Layering management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms There are no alarms related to this feature.
142
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Measurements and counters Table 72: New counters lists counters introduced with this feature. Table 72
New counters
Counter ID
Counter name
Measurement
M1001C747
RRC SETUP ATT CSFB
Service Level
M1001C748
RC SETUP ACCESS FAIL CSFB
Service Level
M1001C749
RRC ACCESS RELEASE CSFB
Service Level
M1001C750
RRC SETUP ATT REPEAT CSFB
Service Level
M1006C310
RRC CONN RELEASE LTE REDIR IN DCH
RRC signaling
M1010C237
LTE CARRIER NOT FOUND FOR REDIRECTION
Inter System Hard Handover
M1010C238
LTE REDIRECTION STARTED AFTER MEASUREMENT
Inter System Hard Handover
M1010C239
DURATION OF LTE CARRIER MEASUREMENT
Inter System Hard Handover
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table 73: New parameters lists parameters introduced with this feature. Table 73
New parameters
Full name
Abbreviated name
Managed object
FMCL Identifier
FMCLId
RNC FMCL
Issue: 01F
Change origin for FMCL object
FMCLChangeOrigin
FMCL
LTE Measurement Averaging Window
LTEMeasAveWindow
FMCL
LTE Maximum Measurement Period
LTEMaxMeasPeriod
FMCL
LTE Minimum Measurement Interval
LTEMinMeasInterval
FMCL
DN09146788
143
Radio resource management features
Table 73
RU50 Feature Descriptions and Instructions
New parameters (Cont.)
Full name
Abbreviated name
Managed object
LTE Neighbor Carrier Frequency Search LTENcarrFreqSearchPeriod Period
FMCL
Measurement Based LTE Layering and Handover Activation
LTELayeringMeasAndHOActivatio n
WCEL
LTE Periodic trigger timer
LTEPeriodicTriggerTimer
RNC
Adjacent LTE Selected Frequency ( EARFCN)
AdjLSelectFreq
ADJL
WCDMA Cell Load Threshold
WCDMACellLoadThreshold
WCEL
FMCL Identifier
FMCLIdentifier
WCEL
Adjacent LTE Frequency Priority
AdjLFreqPriority
HOPL
LTE Carrier frequency selection Minimum Rx Power level
AdjLMinRSRPLevel
HOPL
LTE Carrier frequency selection Minimum Rx qual level
AdjLMinRSRQLevel
HOPL
Transmission Gap Length for LTE Carrier frequency measurements
TGPLForLTEMeas
RNHSPA
CSFB detection for LTE layering
CSFBDetection
RNMOBI
Table 74: Modified parameters lists parameters modified by this feature. Table 74
144
Modified parameters
Full name
Abbreviated name
Managed object
RNC Options
RncOptions
RNC
Smart LTE Layering Enabled
SmartLTELayeringEnabled
WCEL
Smart LTE Layering RSCP threshold
SmartLTELayeringRSCP
WCEL
Smart LTE Layering NRT user amount threshold
SmartLTELayeringUA
WCEL
Smart LTE Layering Target System Selection
SmartLTELayeringTSysSel
WCEL
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 74
Radio resource management features
Modified parameters (Cont.)
Full name
Abbreviated name
Managed object
Smart LTE Layering service control
SmartLTELayeringServ
RNMOBI
Timer for Smart LTE Layering Preventio
SmartLTELayeringPrevT
RNMOBI
Table 75: Related PRFILE parameters lists the existing parameters related to this feature. Table 75
2.11.1.6
Related PRFILE parameters
Parameter ID
Parameter name
002:1916
RN60_MAINT_41
Sales information Table 76
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
RNC LK
2.11.2 Activating RAN2980: Measurement Based LTE Layering Purpose Follow this procedure to activate the RAN2980: Measurement Based LTE Layering feature. Before you start After activating this feature there is no need to restart neither the RNC, nor the BTS. Activating procedure does not cause downtime and the feature can be activated at any time of the day. Activate the license of the RAN2067: LTE Interworking feature using LTE Interworking license key. For more information, see Activating RAN2067: LTE Interworking. Activate the license of the RAN2980: Measurement Based LTE Layering feature using Measurement Based LTE Layering license key. To set the feature state to ON, use the following command: • •
Issue: 01F
for IPA-RNC: ZW7M:FEA=4839:ON; for mcRNC: set license feature-mgmt code 0000004839 feature-admin-state on
DN09146788
145
Radio resource management features
g
RU50 Feature Descriptions and Instructions
No license is required for Flexi Direct RNC. For more information on managing licenses, see Licensing. Before activating the RAN2980: Measurement Based LTE Layering feature, the LTE neighbors must be configured according to the RAN2067: LTE Interworking feature. HSDPA compressed mode measurements for LTE requires setting the BTSSupportForHSPACM WBTS parameter value to 1. If HSDPA CM is not activated, then the HS-DSCH to DCH channel switching is needed before starting the LTE measurements. Note that if the RAN1276: HSDPA Inter-frequency Handover feature license is ON, HSDPA Compressed Mode measurements for IFHO to the BTS in question is activated, provided the BTSSupportForHSPACM parameter value is set to 1. The HSUPA compressed mode measurement support for LTE is provided with the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature. If that feature is not activated, then the E-DCH to uplink DCH channel switching is needed before starting the LTE measurements. The HSPA (HSUPA/HSDPA) compressed mode measurements for LTE requires that the license of RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature is ON and the value of the BTSSupportForHSPACM parameter is set to 2. Configure the following database objects and relevant parameters for the RAN2980: Measurement Based LTE Layering feature and attach them to the WCDMA cell: •
Note that the listed parameters are optional and have a default value. Only the AdjLEARFCN ADJL parameter, for defining the E-UTRA Absolute Radio Frequency Channel Number of the neighboring E-UTRA frequency, is mandatory.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Radio resource management features
Redirection to LTE happens only when the cell has at least one Cell_DCH adjacency defined with the AdjLSelectFreq RNC/WBTS/WCEL/ADJL parameter. Operator can exclude chosen frequency from redirection target using the AdjLSelectFreq parameter. In order to use redirection to LTE, value 0 for the AdjLSelectFreq parameter must be used for at least one LTE frequency configured in the cell.
g
Ensure that RSRP and RSRQ thresholds in both LTE and WCDMA networks are aligned. Corresponding parameters related to this feature are AdjLMinRSRPLevel and AdjLMinRSRQLevel. Additionally, the following parameters can be used for tuning the RAN2980: Measurement Based LTE Layering feature: LTEPeriodicTriggerTimer RNC parameter SmartLTELayeringServ RNMOBI parameter LTETargetFreqCriterion RNMOBI parameter CSFBDetection RNMOBI parameter LTELayerCellHSLoad WCEL parameter SmartLTELayeringUA WCEL parameter SmartLTELayeringTSysSel WCEL parameter SmartLTELayeringRSCP WCEL parameter 002:1916 RN60_MAINT_41 PRFILE parameter
• • • • • • • • •
g
It is crucial to ensure the correctness of AdjLEARFCN and AdjLMeasBw neighboring LTE parameters while configuring, because RNC O&M is not able to verify the values of these parameters. For more information on parameters, see Reference documentation.
1
Open the OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object and then the WBTS object.
4
Configure the WCEL object: a) Right-click on the WCEL object and select Edit parameters. b) In Handover Control tab, set the value of the SmartLTELayeringEnabled parameter to Enabled.
5
In Handover Control tab, set the value LTELayeringMeasActivation parameter to: • •
0 for setting T1, T2, T3 as triggers for redirection without measurements and T4 as a trigger for redirection with measurements 1 for setting T1, T2, T3, T4 as triggers for redirection with measurements
Further information
Issue: 01F
DN09146788
147
Radio resource management features
RU50 Feature Descriptions and Instructions
SmartLTELayeringEnabled WCEL parameter enables triggers (T) for the RAN2980: Measurement Based LTE Layering feature as follows: • • • • • • • • •
value (0) = T1, T2, T3, and T4 disabled value (1) = T1 enabled value (2) = T1 and T2 enabled value (3) = T1 and T3 enabled value (4) = T1, T2, and T3 enabled value (5) = T1 and T4 enabled value (6) = T1, T2, and T4 enabled value (7) = T1, T3, and T4 enabled value (8) = T1, T2, T3, and T4 enabled
where the triggers are: • • • •
T1: RRC state change Cell_DCH to CCH T2: HSDPA/HSPA to DCH/DCH CTS T3: CS RAB release T4: periodic trigger
For more information on triggers, see Description of RAN2980: Measurement Based LTE Layering. The RAN2980: Measurement Based LTE Layering feature is supported for the following PS QoS classes: • • •
interactive (NRT) background (NRT) streaming (RT)
2.11.3 Verifying RAN2980: Measurement Based LTE Layering Purpose Follow this procedure to verify if the RAN2980: Measurement Based LTE Layering feature works properly in the network. Before you start Make sure you have an access to the following applications: •
For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Application in Managing and viewing RNC measurements.
148
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
3
Radio resource management features
Wait for the next 60-minute interval to begin. The measurement interval then starts. For example, if you press the Start button at 11:22, the data collection starts at 12:00.
4
Make a PS call. Ensure you are under both WCDMA and LTE coverage area while making the PS call.
5
Wait until the current 60-minute interval ends for the measurement collection and an additional 10 minutes for the measurement data to be transferred to the OMS.
6
Open the RNW Measurement Presentation application.
7
Check if the values of the M1006C310 and M1010C238 counters increased over time. The M1006C310 RRC CONN RELEASE LTE REDIR IN DCH counter is updated when RNC sends RRC connection release message to the UE, because of the LTE redirection started by the periodic trigger. The M1010C238 LTE REDIRECTION STARTED AFTER MEASUREMENT counter is updated when the LTE carrier measurement performed by the UE finds a carrier frequency with the quality acceptable to perform redirection and RNC initiates the redirection procedure. For details on using the RNW Measurement Presentation application, see Using RNW Measurement Presentation in Managing and viewing RNC measurements.
Expected outcome Redirection to LTE is successful and visible in the listed counters. Unexpected outcome Redirection to LTE is not successful. Unsuccessful redirection to LTE can be verified with the M1010C237 LTE CARRIER NOT FOUND FOR REDIRECTION counter, which is updated when the LTE carrier frequency measurement performed by UE does not result in a carrier frequency with the quality acceptable to perform redirection. Further information
g
The M1010C239 DURATION OF LTE CARRIER MEASUREMENT counter can be used for more detailed monitoring the RAN2980: Measurement Based LTE Layering feature.
2.11.4 Deactivating RAN2980: Measurement Based LTE Layering Follow this procedure to deactivate the RAN2980: Measurement Based LTE Layering feature.
Issue: 01F
DN09146788
149
Radio resource management features
RU50 Feature Descriptions and Instructions
1
Open the OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object and then the WBTS object.
4
Configure the WCEL object: a) Right-click on the WCEL object and select Edit parameters. b) In Handover Control tab, set the value of the SmartLTELayeringEnabled parameter to Disabled.
2.11.5 Testing RAN2980: Measurement Based LTE Layering 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. Purpose This test case verifies if the following events trigger the compressed mode measurements of the LTE layer and the UE's redirection to LTE: • • • •
RRC state change from Cell_DCH to Cell_FACH/Cell_PCH channel type switch from HSDPA to DCH CS call release when the UE has CS and PS connection active periodic trigger
Test environment • • •
RNC with RN8.0 software or newer BTS with WN9.0 software or newer LTE- and WCDMA-capable UE (3GPP Rel-8 or higher)
Before you start The following features need to be activated: • •
RAN2067: LTE Interworking RAN2980: Measurement Based LTE Layerig
Configure the listed parameters in the following way: •
set the values of the following HOPL parameters: – – –
•
150
AdjLMinRSRPLevel to -112 dBm AdjLMinRSRQLevel to -12 dB AdjLFreqPriority to assign the priority of operator's LTE frequency
set the values of the following RNMOBI parameters:
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
– –
SmartLTELayeringServ to Background (True) and Interactive (True) LTETargetFreqCriterion to 0 (Qualified Frequencies only)
set the value of the following WCEL parameters:
•
– – – – –
SmartLTELayeringEnabled to Enabled for all triggers LTELayeringMeasActivation to T1-T4 redirection with measurements SmartLTELayeringUA to 0 LTE Layer Cell HSDPA Load to 0 FMCLIdentifier to 1
set the value of the AdjLEARFCN ADJL parameter to target LTE frequency and check the value of AdjLMeasBw ADJL parameter for neighboring E-UTRA measurement bandwidth
•
g
Radio resource management features
FMCL object with ID=1 has to be created before setting the value of the FMCLIdentifier WCEL parameter to 1.
1
Under the 3G cell, make PS call and then stop data download/upload. Wait for the UE to camp on LTE and stop the call. Pausing data download/upload in PS call leads to UE's state change from Cell_DCH to Cell_FACH/Cell_PCH, which triggers redirection to LTE. Result During state change from Cell_DCH to Cell_FACH/Cell_PCH, the RNC starts compressed mode and sends MEASUREMENT CONTROL message to the UE for measuring the LTE cell. After the UE has sent measurement report about the LTE cell, the RNC sends RRC CONNECTION RELEASE with EUTRA’s AFRCN to the UE for LTE redirection.
2
Under the 3G cell, make a PS call and adjust cell’s signaling power to lower value. Wait for the UE to camp on LTE and stop the call. Result Reducing cell's signaling power during an ongoing PS call intitates UE's channel type switch from HSDPA to DCH, due to UL SIR requirements. After the channel switch, the RNC starts compressed mode and sends MEASUREMENT CONTROL message to the UE for measuring the LTE cell. After the UE has sent the measurement report about the LTE cell, the RNC sends RRC CONNECTION RELEASE with EUTRA’s AFRCN to the UE for LTE redirection.
3
Under the 3G cell, make a multi-RAB call: CS and PS calls at the same time. Release the CS call and make sure PS call is still downloading data. Wait for the UE to camp on LTE and stop the call. Result During CS call release, the RNC starts compressed mode and sends MEASUREMENT CONTROL message to the UE for measuring the LTE cell. After the UE has sent the measurement report about the LTE cell, the RNC sends RRC CONNECTION RELEASE with EUTRA’s AFRCN to the UE for LTE redirection.
Issue: 01F
DN09146788
151
Radio resource management features
4
RU50 Feature Descriptions and Instructions
Under the 3G cell, make a PS call and let the data be downloaded continuously. Wait for the UE to camp on LTE and stop the call. Result After 20 seconds of continuously active PS call, the RNC starts compressed mode and sends MEASUREMENT CONTROL message to the UE for measuring the LTE cell. After the UE has sent measurement report about the LTE cell, the RNC sends RRC CONNECTION RELEASE with EUTRA’s AFRCN to the UE for LTE redirection.
Working of the RAN2980: Measurement Based LTE Layering feature can be verified with the following counters: • • •
M1006C310 RRC CONN RELEASE LTE REDIR IN DCH M1010C238 LTE REDIRECTION STARTED AFTER MEASUREMENT M1010C239 DURATION OF LTE CARRIER MEASUREMENT
For more information, see Verifying RAN2980: Measurement Based LTE Layering. For veryfing LTE redirection triggerd by AMR call release, HSDPA to DCH channel type switch, or CS RAB release with PS RAB still active, please see Testing RAN2717: Smart LTE Layering.
2.12 RAN147: RRC Connection Setup Redirection 2.12.1 Description of RAN147: RRC Connection Setup Redirection Introduction to the feature In case the RRC connection is rejected due to admission control reasons, the RNC sends the UE to 2G or 3G to a new frequency for the next try. If the RRC connection is rejected due to the signaling unit overload reason, the RNC sends UE to 2G.
2.12.1.1
Benefits End-user benefits Better subscriber experience because of call setup delay.
Operator benefits This feature helps to reduce call setup delay in case of congestion.
2.12.1.2
Requirements Software requirements Table 77: Software requirements lists the software required for this feature.
152
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 77
Radio resource management features
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
OMS
BTS Flexi
Flexi Lite
RU50
Not planned RN8.0
mcRNC4.1
OMS3.0 1)
Support not required
Support not required
OMS3.1 2)
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
Support not required
NetAct 8 EP1
Support not required
Support not required
Support not required
Support not required
1)
NetAct 8 EP2 (NetAct 15) 2)
1) for RU50 2) for RU50 EP1
Hardware requirements This feature does not require any new or additional hardware.
2.12.1.3
Functional description Functional overview The RAN 147: RRC Connection Setup Redirection feature enables the redirection of an RRC connection to another 3G frequency or GSM. The redirection happens if the admission control rejects the RRC connection request. The Figure 10: RRC connection setup redirection illustrates the described situation.
RRCCONNECTIONREJECT message containsredirectioninformation The redirection info sent in the RRC message RRC CONNECTION REJECT depends on the target system. If the target system is GSM, then the redirection info is a list of target cells for the UE with release rel-6 or newer. If the UE release is older than rel-6, then the redirection info is just the target system, for example, GSM. If the target system is 3G, then the redirection info is a target frequency (UTRA Absolute Radio Frequency Channel Number). The inter-frequency neighbor cell AdjiUARFCN parameter defines it for downlink. The RNC calculates it for uplink in legacy way from value of the AdjiARFCN parameter and duplex distance used in the RF band. RRC connection sets up on Cell_DCH state when the redirection is triggered. The RRC connection can be set up also on common channels. For more information, see RAN1797 Common channel setup. There is no Admission control in common channels therefore it cannot fail when RRC connection is set up on common channels. RRM decides about the target system on the basis of the establishment cause of the RRC Connection Request and the new management RRCReDirTargetSys parameter. The RRCReDirTargetSys parameter defines the target system for each establishment cause. Also, if the RNC tries to redirect the RRC connection into GSM but UE is not able to camp to the new target cell in GSM, then the RNC is allowed to redirect the RRC connection into 3G. The value for each parameter needs to be planned based on the functionality of the actual establishment cause and the available radio access technologies. It must also be taken into consideration whether or not this functionality can be performed on GSM. The RRCReDirBlockedCellAllowed parameter defines whether cells, which are marked as blocked in SLHO or MBLB procedure, should not be used as a target cell of an RRC connection redirection. If MBLB load information is not available, then only SLHO information (loaded or not loaded) is used. If both MBLB and SLHO load information is not available, then SLHO and MBLB blocked cells are not reduced from
154
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
the target cell list, although the RRCReDirBlockedCellAllowed parameter indicates that the blocked cells should not be used as a target cell of an RRC connection redirection. The AdjiPriorityReDir parameter defines priority for each inter-frequency cell in the neighbor cell list if the congestion of the lub transmission or BTS causes the rejection. The AdjiPriorityQuality parameter defines priority for cells in the neighbor cell list if the RRC connection is rejected because of downlink power, uplink interference, or downlink spreading code congestion. The frequency of feasible target cells with the highest priority are selected as the target frequency for redirection. For more information, see the Figure 11: Selection process of redirection information. Figure 11
If the RNC signaling unit overload is the reason to reject the RRC Connection Request, UE can be redirected to GSM network without target cell list.
2.12.1.4
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 commands There are no commands related to this feature.
Impact on network and network element management tools This feature has no impact on network management or network element management tools.
Issue: 01F
DN09146788
155
Radio resource management features
RU50 Feature Descriptions and Instructions
Impact on system performance and capacity This feature has no impact on system performance or capacity.
2.12.1.5
RAN147: RRC Connection Setup Redirection management data For information on alarms, counters, key performance indicators, and parameter documents, see Reference documentation.
Alarms There are no alarms related to this feature.
Measurements and counters Table 78: New counters lists counters introduced with this feature. Table 78
New counters
Counter ID
Counter name
Measurement
M1006C305
RRC_CONN_REDIR_GSM_FAIL
1006 - RRC signalling (RNC)
Table 79: Related existing counters lists existing counters related to this feature. Table 79
Related existing counters
Counter ID
Counter name
Measurement
M1006C70
RRC_CONN_REJ_DIR_SETUP
1006 - RRC signalling (RNC)
M1001C618
RRC CONN SETUP FAIL DUE TO ICSU OVERLOAD
1001 - RRC signaling (RNC)
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table 80: New parameters lists parameters introduced with this feature. Table 80
156
New parameters
Full name
Abbreviated name
Managed object
Enabling RRC connection Redirection
RRCReDirEnabled
RNFC
RRC Connection Redirection Target System
RRCReDirTargetSys
WCEL
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 80
Issue: 01F
Radio resource management features
New parameters (Cont.)
Full name
Abbreviated name
Managed object
RRC Connection Redirection Target System for conversational causes
TargetsystemConversationalC all
WCEL
RRC Connection Redirection Target System for streaming causes
TargetsystemStreamingCall
WCEL
RRC Connection Redirection Target System for interactive causes
TargetsystemInteractiveCall
WCEL
RRC Connection Redirection Target System for background causes
TargetsystemBackgroundCall
WCEL
RRC Connection Redirection Target System for subscribed traffic causes
TargetsystemSubscribedTraffi c
WCEL
RRC Connection Redirection Target System for emergency call causes
TargetsystemEmergencyCall
WCEL
RRC Connection Redirection Target System for inter-RAT re-selection causes
TargetsysteminterRATreselecti WCEL on
RRC Connection Redirection Target System for inter-RAT cell change order causes
TargetsysteminterRATchangeo WCEL rder
RRC Connection Redirection Target System for registration causes
Targetsystemregistration
WCEL
RRC Connection Redirection Target System for detach causes
TargetsystemDetach
WCEL
RRC Connection Redirection Target System for high priority signalling causes
TargetsystemHighPrioritySign alling
WCEL
RRC Connection Redirection Target System for low priority signalling causes
TargetsystemLowPrioritySigna WCEL lling
RRC Connection Redirection Target System for low priority signalling causes
Targetsystemreestablishment
WCEL
RRC Connection Redirection Target System for unknown causes
Targetsystemunknown
WCEL
RRC Connection Redirection Target System for MBMS reception causes
TargetsystemMBMSreception
WCEL
DN09146788
157
Radio resource management features
Table 80
RU50 Feature Descriptions and Instructions
New parameters (Cont.)
Full name
Abbreviated name
Managed object
RRC Connection Redirection Target System for MBMS ptp RB request causes
TargetsystemMBMSrbrequest
WCEL
RRC Connection Redirection allows blocked cells
RRCReDirBlockedCellAllowed RNMOBI
Neighbour cell priority for RRC Connection Redirection
AdjiPriorityReDir
HOPI
Table 81: Modified parameters lists parameters modified by this feature. Table 81
Activating RAN147: RRC Connection Setup Redirection due to admission control reasons Purpose Follow this procedure to activate this feature. For more information on the feature, see the RAN147: RRC Connection Setup Redirection Feature Description. Before you start Restart of the RNC is not required after activation of this feature.
158
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
This procedure does not require cell locking. 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: • •
OMS Element Manager Application Launcher
This feature is controlled by a license. For information on managing licenses, see Licensing. To set the feature state to ON, use the following command:
•
for IPA-RNC: ZW7M: FEA=4780:ON; for mcRNC: set license feature-mgmt code 0000004780 feature-admin-state on
1
Open the OMS Element Manager.
2
Go to the Topology Tree View.
•
Select: Network Management ► Topology Tree View 3
Expand the RNFC object.
4
Configure the RNFC object. a) From the drop-down menu select Edit ► Edit Parameters. b) Set the RRCReDirEnabled parameter value to Enabled(AC 1 or 3). c) The value of the target system for redirection (both primary and secondary) should be defined, and its value depends on the value of the Establishment Cause received in the message RRC: RRC CONNECTION REQUEST. The RRCReDirTargetSys (under WCEL objects) parameter value primary target system secondary target system: • • • • •
Save the changes. a) Click the Apply button. b) If the UE should be redirected to UMTS, then ADJI's should to be created. If the redirection should be done to GSM, then ADJG's should be created for WCEL.
Issue: 01F
DN09146788
159
Radio resource management features
2.12.2.2
RU50 Feature Descriptions and Instructions
Activating RAN147: RRC Connection Setup Redirection due to signaling unit overload Purpose Follow this procedure to activate this feature. For more information on the feature, see the RAN147: RRC Connection Setup Redirection Feature Description. Before you start Restart of the RNC is not required after activation of this feature. This procedure does not require cell locking. 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: • •
OMS Element Manager Application Launcher
This feature is controlled by a license. For information on managing licenses, see Licensing. To set the feature state to ON, use the following command:
•
for IPA-RNC: ZW7M: FEA=4780:ON; for mcRNC: set license feature-mgmt code 0000004780 feature-admin-state on
1
Open the OMS Element Manager.
2
Go to the Topology Tree View.
•
Select: Network Management ► Topology Tree View 3
Expand the RNFC object.
4
Configure the RNFC object. a) From the drop-down menu select Edit ► Edit Parameters. b) Set the RRCReDirEnabled parameter value to Enabled(AC 2 or 3). c) The value of the target system for redirection (both primary and secondary) should be defined, and its value depends on the value of the Establishment Cause received in the message RRC: RRC CONNECTION REQUEST. The RRCReDirTargetSys (under WCEL objects) parameter value primary target system secondary target system: •
160
0 none,
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
• • • •
5
Radio resource management features
1 GSM 3G, 2 3G GSM, 3 GSM none, 4 3G none.
Save the changes. a) Click the Apply button. b) If the UE should be redirected to UMTS, then ADJI's should to be created. If the redirection should be done to GSM, then ADJG's should be created for WCEL.
Verifying RAN147: RRC Connection Setup Redirection due to admission control reasons Purpose Follow this procedure to activate this feature. Before you start Make sure you have access to the following application: •
RNW Measurement Management
1
UE1 sends RRC Connection Request with cause "originatingInteractiveCall" to WBTS1 CELL-1. RRC Connection of UE1 is rejected due to DL Power. Verify, if RNC sends RRC: RRC Connection Reject to UE with redirection info specifying frequencyInfo. Since Primary Target System (selected on the base of HOPI - AdjiPriorityQuality), defined for RRCReDirTargetSysTargetsystemInteractiveCall is 3G. The specified target frequency of WBTS1 CELL-3 has the highest priority defined by HOPI2- AdjiPriorityQuality.
2
RRC connection setup successfully on WBTS1 CELL-3 with cause "originatingInteractiveCall" for UE1.
3
Counters verification. The counters are updated as follows:
Issue: 01F
DN09146788
161
Radio resource management features
Table 83
2.12.3.2
RU50 Feature Descriptions and Instructions
Counters verification
ID
Name
Value
Updated objects
M1006C70
RRC CONN REJECT DUE TO RRC CONNECTION SETUP REDIRECTION
1
WBTS1 CELL-1
Verifying RAN147: RRC Connection Setup Redirection due to signaling unit overload reasons Purpose Follow this procedure to activate this feature. Before you start Make sure you have access to the following application: •
RNW Measurement Management
1
Make sure that there is very heavy CPU load in signaling unit (ICSU or USCP).
2
UE1 sends RRC Connection Request. Verify, if the RNC sends RRC: RRC Connection Reject to UE with redirection info / Inter-RAT info = GSM.
3
Counters verification. The counters are updated as follows: Table 84
162
Counters verification
ID
Name
Value
Updated objects
M1001C618
RRC CONN SETUP FAIL DUE TO ICSU OVERLOAD
1
WBTS1 CELL-1
M1006C70
RRC CONN REJECT DUE TO RRC CONNECTION SETUP REDIRECTION
Deactivating RAN147: RRC Connection Setup Redirection due to admission control reasons Purpose Follow this procedure to deactivate this feature. Before you start Make sure you have access to the following applications: •
Application Launcher
1
Open the OMS Element Manager.
2
Go to the Topology Tree View. Select: Network Management ► Topology Tree View
3
Expand the RNFC object.
4
Configure the RNFC object. a) From the drop-down menu select Edit ► Edit Parameters. b) Set the RRCReDirEnabled parameter value to Disabled (0 or 2).
5
Save the changes. a) Click the Apply button.
6
Open the MMI session. Open the Secure MMI Window application from the Application Launcher. Alternatively, any other configured MMI client can be used.
7
To deactivate the feature execute the following: • •
g
To set the feature state to OFF, set the value of the RRCReDirEnabled to 0. To enable the signaling unit overload, set the value of the RRCReDirEnabled to 2. For more information, see Deactivating RAN147: RRC Connection Setup Redirection due to signaling unit overload reasons
For IPA-RNC, use the following MML command: ZW7M: FEA=4780:OFF; For mcRNC, use the following SCLI command:
Issue: 01F
DN09146788
163
Radio resource management features
RU50 Feature Descriptions and Instructions
set license feature-mgmt code 0000004780 feature-admin-state off
2.12.4.2
Deactivating RAN147: RRC Connection Setup Redirection due to signaling unit overload reasons Purpose Follow this procedure to deactivate this feature. Before you start Make sure you have access to the following applications: •
Application Launcher
1
Open the OMS Element Manager.
2
Go to the Topology Tree View. Select: Network Management ► Topology Tree View
3
Expand the RNFC object.
4
Configure the RNFC object. a) From the drop-down menu select Edit ► Edit Parameters. b) Set the RRCReDirEnabled parameter value to Disabled (0 or 1).
5
Save the changes. a) Click the Apply button.
6
Open the MMI session. Open the Secure MMI Window application from the Application Launcher. Alternatively, any other configured MMI client can be used.
7
To deactivate the feature execute the following: • •
g
To set the feature state to OFF, set the value of the RRCReDirEnabled to 0. To enable the admission control modifications, set the value of the RRCReDirEnabled to 1. For more information, see Deactivating RAN147: RRC Connection Setup Redirection due to admission control reasons
For IPA-RNC, use the following MML command:
164
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
ZW7M: FEA=4780:OFF; For mcRNC, use the following SCLI command: set license feature-mgmt code 0000004780 feature-admin-state off
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. This feature enables the redirection of the RRC connection to another 3G frequency or GSM, in the event that the RRC connection establishment is rejected during the RRC connection setup attempt. The Redirection info sent in the RRC message RRC CONNECTION REJECT depends on the target system. If the target system is GSM, then the redirection info is a list of target cells in case the UE release is rel-6 or newer. If the Ue release is older than rel-6, then the redirection info is just the target system, for example GSM. If the target system is 3G, then the redirection info is a target frequency. Parameters The HOPI AdjiPriorityReDir parameter defines the priority of each cell in 3G inter frequency neighbor cell list. This priority is used to select the target frequency for redirected RRC connection in case the target system is 3G, and the reason of the rejection is Iub transmission or BTS congestion (for example, any BTS failure). The existing HOPI AdjiPriorityQuality parameter defines priority for cells in the neighbor cell list if the RRC connection is rejected because of downlink power, uplink interference, downlink spreading code congestion, or RNC HW congestion (for example, DSP congestion). The frequency of feasible target cells with the highest priority are selected to be the target frequency for redirection. The GSM target cell list is selected with lower priority. The priority of the particular GSM cell is defined by the value of the AdjgPriorityCoverage parameter under the HOPG object. It is identified by the ADJG RtHopgIdentifier parameter of te GSM neighbor cell. There can be a maximum of 10 GSM cells in the target cell list. This feature uses the existing failure reason to decide when the redirection is needed. The failure is reported by the Base Station Resource Manager with the specific failure reasons being in the Admission Control cases, RC3, and RM3, when Unit overload in question. uplink interference: ul_prx_nc_overload, no_prx_capacity, ul_load_factor_overload,no_load_capacity, ul_load_and_prx_overload, rno_load_and_prx_capacity downlink power: preemp_no_capacity, no_ptx_capacity, dl_cell_overload downlink spreading code: no_free_codes Hardware congestion: overload, prev_oload_ctrl, dsp_cpu_overload
Issue: 01F
DN09146788
165
Radio resource management features
RU50 Feature Descriptions and Instructions
Test environment • • • • • • • •
1 RNC, 1 NodeB, Flexi WCDMA, three cells, 1 MGW, 1 MSC/MSS, 1 SGSN, 1 GGSN, UE, Iub interface monitoring tool or UE monitoring tool (able to decode the RRC Messages).
Before you start The following optional feature related license keys should be switched on for RNC: •
WBTS 1 Cell 1 is defined as source cell, and WBTS 1 Cell 2, and WBTS 2 Cell 2 as a target cell where redirection will be done.
For more inforamtion, see Activating RAN147: RRC Connection Setup Redirection
g
These parameter values are defined for lab testing to get trigger with couple of UE’s camped to WBTS1. The following RNC parameters under the RNFC and WCEL objects should be set: •
The specified target frequency WBTS1 WCEL2 has the highest priority defined by HOPI2- AdjiPriorityQuality on source cell 1.
For more inforamtion, see Activating RAN147: RRC Connection Setup Redirection Admission Control decision for SRBs is rejected Downlink power as a trigger for RRC Connection Setup redirection
166
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Radio resource management features
1
Set the power on UE, and check if Location Update, and Attach works on Cell 1.
2
Set the value of the PtxTargetPSMax parameter to 11dBm, PtxTargetPSMin to 11, and PtxTarget to 11.
3
Check, if the value of the RRCReDirTargetSys parameter (under WCEL objects) is set to 4 for the used data service (for example, PS Backround data call).
4
Set the value of the RRCReDirEnabled parameter to 1 (Enabled AC).
5
Make a PS call to check if the UE is rejected in RRC connection setup phase with redirection info specifying frequency Info and directed successfully to Cell 2. For more information see, Appendix 1.
6
If GSM is a target system to be tested, then set the value of the RRCReDirTargetSys parameter to 1, 2, or 3. Next repeat the test. If the value 2 is used, then 3G WCEL needs to be unavailable. Verify, if GSM related redirection info is sent correctly on the RRC Connection Setup Reject message, and UE is Re-directed correctly to GSM. For more information see Appendix 1.
Expected outcome Signaling Unit Load decision for SRBs is rejected SRB Target system is GSM.
g
Cannot be tested on Lab without traffic generator.
2.13 RAN3069: RSRQ-based LTE Reselection 2.13.1 Description of RAN3069: RSRQ-based LTE Reselection Introduction to the feature The RAN3069: RSRQ-based LTE Reselection feature provides support for LTE cell reselection based on the reference signal received quality (RSRQ).
2.13.1.1
Benefits End-user benefits This feature maximizes end-user’s LTE experience.
Issue: 01F
DN09146788
167
Radio resource management features
RU50 Feature Descriptions and Instructions
Operator benefits This feature assures smooth WCDMA-LTE interworking when in LTE network RSRQ criteria are used for cell reselection.
2.13.1.2
Requirements Software requirements Table 85: Software requirements lists the software required for this feature. Table 85
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
Flexi BTS
RU50
Not planned RN8.0
mcRNC4.1
Not planned OMS3.0 1) OMS3.1 2)
Support not required
MGW
UE
Flexi Lite BTS
Flexi 10 BTS
NetAct
MSC
SGSN
Support not required
Support not required
NetAct 8 EP1 1)
Support not Support not Support not required required required
3GPP Rel-9
NetAct 8 EP2 (NetAct 15) 2)
1) for RU50 2) for RU50 EP1
Hardware requirements This feature does not require any new or additional hardware.
2.13.1.3
Functional description Functional overview In current system implementation the RAN2067: LTE Interworking feature supports reference symbol received power (RSRP)-based LTE reselection. The RAN3069: RSRQbased LTE Reselection feature introduces an upgrade by including quality thresholds for LTE priority-based cell reselection. These quality thresholds are specified in 3GPP Rel-9 and they include the UTRA serving cell Ec/N0 threshold and E-UTRA neighbor cell RSRQ quality threshold. These thresholds are broadcast in the system information block type 19 (SIB19).
168
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
2.13.1.4
Radio resource management features
System impact Interdependencies between features This feature requires the RAN2067: LTE Interworking feature.
Impact on commands There are no commands related to this feature.
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.
2.13.1.5
RAN3069: RSRQ-based LTE Reselection management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
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 86: New parameters lists parameters introduced with this feature and the corresponding SIB19 parameters specified in 3GPP Rel-9. Table 86
New parameters
Full name
Abbreviated name
SIB19 IE
Managed object
Thresh serving low 2
Threshservlow2
Threshserving,low2
WCEL
Qqualmin for LTE cell reselection
AdjLQqualminEUTRA
QqualminEUTRA
HOPL
Threshold high 2 for LTE cell reselection
AdjLThreshigh2
Threshx,high2
HOPL
Threshold low 2 for LTE cell reselection
AdjLThreslow2
Threshx,low2
HOPL
Issue: 01F
DN09146788
169
Radio resource management features
2.13.1.6
RU50 Feature Descriptions and Instructions
Sales information Table 87
Sales information
BSW/ASW
SW component
License control in network element
ASW1)
RAN
RNC LK
1) the RAN2067: LTE Interworking feature license also controls the RAN3069: RSRQ-
based LTE Reselection feature
2.13.2 Activating RAN3069: RSRQ-based LTE Reselection Purpose Follow this procedure to activate the RAN3069: RSRQ-based LTE Reselection feature. Before you start After activating this feature there is no need to restart RNC or BTS. Activating procedure does not cause downtime and the feature can be activated at any time of the day.
g
The RAN2067: LTE Interworking feature license also controls the RAN3069: RSRQ-based LTE Reselection feature. Activate the RAN2067: LTE Interworking feature controlled by the license key LTE Interworking. For more information, see Activating RAN2067: LTE Interworking. For information on managing licenses, see Licensing. To provide seamless priority-based cell reselection between GSM, WCDMA, and LTE, make sure to admit each Radio Access Technology a different priority: •
•
•
•
g
AbsPrioCellReselec WCEL parameter, introduced with the RAN2067:LTE Interworking feature, defines the priority of the WCDMA serving cell (UTRA priority info list/UTRA Serving Cell IE) AdjiAbsPrioCellReselec HOPI parameter, introduced with the RAN2881: WCDMA and GSM Layer Priorities feature, defines the WCDMA inter-frequency priority (UTRA priority info list/UTRAN FDD Frequencies IE) AdjgAbsPrioCellReselec HOPG parameter, introduced with the RAN2881: WCDMA and GSM Layer Priorities feature, defines the GSM priority (GSM priority info list/GSM Priority Info IE) AdjLAbsPrioCellReselec HOPL parameter, introduced with the RAN2067: LTE Interworking feature, defines the LTE priority (E-UTRA frequency and priority info list/E-UTRA frequency and priority IE) Priority-based cell-reselection between GSM and WCDMA radio technologies is provided by the RAN2881: WCDMA and GSM Layer Priorities feature.
WCDMA priority is broadcast per UARFCN in SIB19 message. The same priority value should be given for each inter-frequency WCDMA neighbor. If more than one value is given, the highest priority is broadcast in SIB19 message.
170
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
g g
Radio resource management features
If quality criteria are chosen to be used for LTE absolute-priority-based cell reselection, ensure that both Threshx, high2 (AdjLThreshigh2 HOPL parameter) and Threshx, low2 (AdjLThreslow2 HOPL parameter) are configured at the same time and broadcast in SIB19. Otherwise UE is not using these parameters. Also, ensure that priorities for which both Threshx, high2 and Threshx, low2 are provided in SIB19 are always different from the priorities for which these parameters are not provided in SIB19. By default Threshx, high2 and Threshx, low2 are not broadcast in SIB19. To allow lower priority layer measurements before reaching minimum required quality level in the WCDMA cell, the value of Sprioritysearch2 WCEL parameter needs be higher than the value of Threshservlow2 WCEL parameter. Note that the activation procedure for the RAN3069: RSRQ-based LTE Reselection feature is the same as for the RAN2067: LTE Interworking feature.
1
Open the OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object and then the WBTS object.
4
Configure the WCEL object: a) Right-click on the WCEL object and select Edit parameters. b) In System Info tab, set the values of LTECellReselection parameter to Enabled.
Further information
g
Note that the UE does not use Hierarchical Cell Structure (HCS) for inter-frequency or inter-RAT reselection if absolute-priority-based cell reselection is used.
2.13.3 Verifying RAN3069: RSRQ-based LTE Reselection Purpose Follow these tips to verify that the RAN3069: RSRQ-based LTE Reselection feature works properly in the network. Before you start To verify the usage of the quality criteria for LTE absolute-priority-based cell reselection, you also need to activate and verify the RAN2067: LTE Interworking feature. For more information, see Activating RAN2067: LTE Interworking and Verifying RAN2067: LTE Interworking.
g
Issue: 01F
There are no counters involved in cell reselection process. The UE reselects the cell according to the parameters broadcast by the network in SIB19 message.
DN09146788
171
Radio resource management features
RU50 Feature Descriptions and Instructions
When the RAN3069: RSRQ-based LTE Reselection feature is active, it is visible in the content of SIB19 message. After activating this feature and ascribing values to the parameters listed in RAN3069: RSRQ-based LTE Reselection management data section, the E-UTRA frequency and priority info list/E-UTRA frequency and priority information elements will be broadcast in SIB19 message. Content of SIB19 message can be monitored by using UE and network protocol analyzer. Further information Camping on a desired layer is performed by the UE using SIB19 parameters. Cell reselection algorithm is specified in 3GPP TS 25.304 User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode.
2.13.4 Deactivating RAN3069: RSRQ-based LTE Reselection Purpose Follow this procedure to deactivate the RAN3069: RSRQ-based LTE Reselection feature. Before you start
g
In order to verify usage of the quality criteria for LTE absolute priority based cell reselection, activation of the RAN2067: LTE Interworking feature was needed. Therefore, for deactivating the RAN3069: RSRQ-based LTE Reselection feature, instructions on the RAN2067: LTE Interworking feature deactivation are also included. For more information, see Deactivating RAN2067: LTE Interworking.
1
Open the OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object and then the WBTS object.
4
Configure the WCEL object: a) Right-click on the WCEL object and select Edit parameters. b) In System Info tab, set the values of LTECellReselection parameter to Disabled.
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. Purpose
172
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
The purpose of this test case is verifying if the RNC can deliver new RSRQ parameters in SIB19 information element.
g
The RAN3069: RSRQ-based LTE Reselection feature is an extension to the RAN2067: LTE Interworking feature and provides quality thresholds, defined in 3GPP Rel-9, for LTE priority-based cell reselection. Test environment • • •
RNC with RN8.0 software or newer BTS with WN9.0 software or newer network protocol analyzer
Before you start The following feature needs to be activated: •
g
RAN2067: LTE Interworking The RAN2067: LTE Interworking feature license also controls the RAN3069: RSRQ-based LTE Reselection feature. For information on how to activate the RAN2067: LTE Interworking feature, see Activating RAN2067: LTE Interworking.
Configure the listed parameters in the following way: • •
set the value of Threshservlow2 WCEL parameter to 2 dB under the RNC object, create one HOPL object and set the values of the following HOPL parameters: – – –
Issue: 01F
AdjLQqualminEUTRA to -19 dB AdjLThreshigh2 to 6 dB AdjLThreslow2 to 5 dB
DN09146788
173
Radio resource management features
RU50 Feature Descriptions and Instructions
1
Open the OMS Element Manager.
2
Go to the Topology.
3
Expand the ROOT.
4
Lock and unlock the cell, for which the Threshservlow2 parameter value was set to 2dB. a) Go to the WCEL object by following the path: RNC object ► WBTSs folder ► WBTS object ► WCELs folder ► WCEL object b) Right-click on the WCEL object and selectAdministrative State Change ► Lock Cell c) Unlock the cell by selecting Administrative State Change ► Unlock Cell
5
Check the NBAP: SYSTEM INFORMATION UPDATE REQUEST and verify if the values broadcast in the SIB19 IE are the same as preconfigured. Example Example of SIB19 IE content v920NonCriticalExtensions { sysInfoType19-v920ext { utra-PriorityInfoList-v920ext { threshServingLow2 2 }, eutra-FrequencyAndPriorityInfoList-v920ext { { qqualMinEUTRA -19, threshXhigh2 6, threshXlow2 5
g
Content of SIB19 message can be monitored by using network protocol analyzer.
2.14 RAN2264: Smart LTE Handover 2.14.1 Description of RAN2264: Smart LTE Handover Introduction to the feature The RAN2264: Smart LTE Handover feature introduces inter-RAT WCDMA to LTE handover. This feature supports traffic steering to LTE layers, providing seamless handover experience for the end-users.
174
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
2.14.1.1
Radio resource management features
Benefits End-user benefits End user benefits from seamless WCDMA to LTE handover experience.
Operator benefits Thanks to this feature WCDMA to LTE mobility becomes faster end more reliable, as handover is preceded with compressed mode measurements.
2.14.1.2
Requirements Software requirements Table 88: Software requirements lists the software required for this feature. Table 88
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi OMS Direct RNC
RU50
Flexi Direct RU50
mcRNC4.1
ADA6.0
RN8.0
OMS3.0 1)
Flexi BTS
WN9.0
OMS3.1 2) IHO 6.0 3)
Flexi Lite BTS
Flexi 10 BTS
Support not WN9.1 required
NetAct
MSC
NetAct 8 EP1 1)
Support not Planned for Support not 3GPP Relrequired later required 8 (optional) releases
NetAct 8 EP2 (NetAct 15)
SGSN
MGW
UE
2) 3)
1) for RU50 2) for RU50 EP1 3) for Flexi Direct RU50
Hardware requirements This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF or Flexi Lite BTS WCDMA.
Issue: 01F
DN09146788
175
Radio resource management features
2.14.1.3
RU50 Feature Descriptions and Instructions
Functional description The RAN2264: Smart LTE Handover feature introduces inter-system handover from WCDMA to LTE. Inter-RAT handover from WCDMA to LTE can be started if compressed mode measurements indicate that LTE coverage is available. The following events can trigger compressed mode measurements for LTE handover: • • • •
T1: Cell_DCH to Cell_FACH, Cell_PCH, or URA_PCH selection T2: HSDPA reconfiguration to traditional DCH, for example reconfiguration caused by high HSDPA load and lack of HSDPA cell resources T3: CS call release with active PS RAB T4: Periodic trigger
In uplink DCH is used during compressed mode. However, if HSUPA compressed mode supported by the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature is active, then HSUPA compressed mode is used in uplink. In cases when WCDMA cell load is not high and users can be provided with good enough experience in WCDMA layer, measurements and handover to LTE can be bypassed. Cell level load parameters can be used to define if load is low enough for keeping UEs in WCDMA. The RAN2264: Smart LTE Handover feature supports inter-RAT handover from WCDMA to both FDD-LTE and TDD-LTE. Smart LTE Handover is supported also if there are DRNC-controlled cells in the active set. LTE measurements and handover are allowed if there is at least one cell in the active set controlled by SRNC. LTE measurements are started based on the triggers and parameters of the SRNC cell. LTE neighbors of the DRNC cells reported over Iur are considered as possible LTE handover target cells. This feature also offers a possibility to limit UEs allowed to be handed over to LTE. When the limitation is activated, handover to LTE is allowed only to UEs, that are indicated to be redirected from LTE to WCDMA and/or are indicated to be in WCDMA because of CS fallback (CSFB). Each limitation guarantees that the user has the LTE subscription and it has been in LTE (that is, LTE coverage was available when the UE came to WCDMA). The first limitation is activated with the 002:1916 RN60_MAINT_41 PRFILE parameter and the latter with the CSFBDetection RNMOBI parameter.
2.14.1.4
System impact Interdependencies between features The RAN2067: LTE Interworking feature is a prerequisite for using this feature. For HSUPA compressed mode measurements, the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature is required.
g
176
This feature requires also support from the UE, 3G core network, LTE core network, and LTE eNB.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Impact on interfaces This feature causes rise of signaling traffic on Uu, Iub, Iur, and IuPS interfaces (compressed mode related signaling, LTE neighbor reporting over Iur, relocation related signaling between RNC and core network).
Impact on network and network element management tools • •
New Managed Object Class (MOC): ADJE is introduced for defining E-UTRA (LTE) neighbor cells. New counters for monitoring outgoing LTE PS Handover are introduced.
Impact on system performance and capacity •
•
2.14.1.5
This feature supports traffic steering and network load balancing scenarios. Offloading WCDMA network during high load states via seamless handover to LTE (resources are reserved in advance on LTE side in contrast to layering features) increases available HSDPA power per user ratio in WCDMA cell. This feature impacts the maximum number of UEs that are simultaneously in compressed mode in the cell due to a non-critical handover measurement reason (both DCH and HSPA compressed modes).
RAN2264: Smart LTE Handover management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms There are no alarms related to this feature.
Measurements and counters Table 89: New counters lists counters introduced with this feature. Table 89
Issue: 01F
New counters
Counter ID
Counter name
Measurement
M1010C240
LTE NRT ISHO MEAS WITH CM DUE TO DCH TO CCH
Inter System Hard Handover
M1010C241
LTE NRT ISHO MEAS WITH CM DUE TO HSPA TO DCH
Inter System Hard Handover
M1010C242
LTE NRT ISHO MEAS WITH CM DUE TO CS RAB RELEASE
Inter System Hard Handover
M1010C243
LTE NRT ISHO MEAS WITH CM DUE TO PERIODIC TRIGGER
Inter System Hard Handover
M1010C244
LTE NRT ISHO MEAS WITHOUT CM DUE TO DCH TO CCH
Inter System Hard Handover
DN09146788
177
Radio resource management features
Table 89
178
RU50 Feature Descriptions and Instructions
New counters (Cont.)
Counter ID
Counter name
Measurement
M1010C245
LTE NRT ISHO MEAS WITHOUT CM DUE TO HSPA TO DCH
Inter System Hard Handover
M1010C246
LTE NRT ISHO MEAS WITHOUT CM DUE TO CS RAB RELEASE
Inter System Hard Handover
M1010C247
LTE NRT ISHO MEAS WITHOUT CM DUE TO PERIODIC TRIGGER
Inter System Hard Handover
M1010C248
LTE NRT ISHO NO CELL FOUND DUE TO DCH TO CCH
Inter System Hard Handover
M1010C249
LTE NRT ISHO NO CELL FOUND DUE TO HSPA TO DCH
Inter System Hard Handover
M1010C250
LTE NRT ISHO NO CELL FOUND DUE TO CS RAB RELEASE
Inter System Hard Handover
M1010C251
LTE NRT ISHO NO CELL FOUND DUE TO PERIODIC TRIGGER
Inter System Hard Handover
M1010C252
LTE NRT ISHO ATTEMPTS DUE TO DCH TO CCH
Inter System Hard Handover
M1010C253
LTE NRT ISHO ATTEMPTS DUE TO HSPA Inter System Hard Handover TO DCH
M1010C254
LTE NRT ISHO ATTEMPTS DUE TO CS RAB RELEASE
Inter System Hard Handover
M1010C255
LTE NRT ISHO ATTEMPTS DUE TO PERIODIC TRIGGER
Inter System Hard Handover
M1010C256
LTE NRT ISHO SUCCESS DUE TO DCH TO CCH
Inter System Hard Handover
M1010C257
LTE NRT ISHO SUCCESS DUE TO HSPA TO DCH
Inter System Hard Handover
M1010C258
LTE NRT ISHO SUCCESS DUE TO CS RAB RELEASE
Inter System Hard Handover
M1010C259
LTE NRT ISHO SUCCESS DUE TO PERIODIC TRIGGER
Inter System Hard Handover
M1010C260
LTE NRT ISHO UE NACK DUE TO DCH TO CCH
Inter System Hard Handover
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 89
Issue: 01F
Radio resource management features
New counters (Cont.)
Counter ID
Counter name
Measurement
M1010C261
LTE NRT ISHO UE NACK DUE TO HSPA TO DCH
Inter System Hard Handover
M1010C262
LTE NRT ISHO UE NACK DUE TO CS RAB RELEASE
Inter System Hard Handover
M1010C263
LTE NRT ISHO UE NACK DUE TO PERIODIC TRIGGER
Inter System Hard Handover
M1010C264
LTE NRT ISHO UE LOST DUE TO DCH TO Inter System Hard Handover CCH
M1010C265
LTE NRT ISHO UE LOST DUE TO HSPA TO DCH
M1010C266
LTE NRT ISHO UE LOST DUE TO CS RAB Inter System Hard Handover RELEASE
M1010C267
LTE NRT ISHO UE LOST DUE TO PERIODIC TRIGGER
Inter System Hard Handover
M1010C268
LTE NRT ISHO PREPARATION FAIL
Inter System Hard Handover
M1019C0
LTE ISHO ATTEMPTS
AutoDef LTE
M1019C1
LTE ISHO SUCCESSFUL
AutoDef LTE
M1036C0
LTE PS ISHO OUT PREP REQ
LTE Relocation
M1036C1
LTE PS ISHO OUT PREP SUCC
LTE Relocation
M1036C2
LTE PS ISHO OUT PREP FAIL DUE TO RN LAYER CAUSE
LTE Relocation
M1036C3
LTE PS ISHO OUT PREP FAIL DUE TO TR LTE Relocation LAYER CAUSE
M1036C4
LTE PS ISHO OUT PREP FAIL DUE TO NAS CAUSE
LTE Relocation
M1036C5
LTE PS ISHO OUT PREP FAIL DUE TO PROT CAUSE
LTE Relocation
M1036C6
LTE PS ISHO OUT PREP FAIL DUE TO MISC CAUSE
LTE Relocation
M1036C7
LTE PS ISHO OUT PREP FAIL DUE TO NON STAN CAUSE
LTE Relocation
DN09146788
Inter System Hard Handover
179
Radio resource management features
Table 89
RU50 Feature Descriptions and Instructions
New counters (Cont.)
Counter ID
Counter name
Measurement
M1036C8
LTE PS ISHO CANCEL TOTAL
LTE Relocation
M1036C9
LTE PS ISHO FAIL DUE TO RELOC OVERALL TIMER EXPIRY
LTE Relocation
M1036C10
LTE PS ISHO CANCEL DUE TO RELOC PREP TIMER EXPIRY
LTE Relocation
Table 90: Related existing counters lists existing counters related to this feature. Table 90
Related existing counters
Counter ID
Counter name
Measurement
M1010C239
DURATION OF LTE CARRIER MEASUREMENT
Inter System Hard Handover
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table 91: New parameters lists parameters introduced with this feature. Table 91
180
New parameters
Full name
Abbreviated name
Managed object
Outgoing LTE Handover Enabled
LTEHandoverEnabled
RNC/WBTS/WCEL
Minimum Interval Between LTE HOs
LTEMinHoInterval
RNC/FMCL
ADJE Identifier
ADJEId
RNC/WBTS/WCEL /ADJE
Change origin for ADJE object
ADJEChangeOrigin
RNC/WBTS/WCEL /ADJE
Inter-RAT LTE adjacent physical cell identifier
AdjePhysicalCellId
RNC/WBTS/WCEL /ADJE
Mobile Country Code
AdjeMCC
RNC/WBTS/WCEL /ADJE
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 91
Radio resource management features
New parameters (Cont.)
Full name
Abbreviated name
Managed object
Mobile Network Code
AdjeMNC
RNC/WBTS/WCEL /ADJE
Mobile Network Code Length
AdjeMNCLength
RNC/WBTS/WCEL /ADJE
Macro eNB ID
AdjeENodeBId
RNC/WBTS/WCEL /ADJE
Cell ID
AdjeCellId
RNC/WBTS/WCEL /ADJE
Tracking Area Code
AdjeTAC
RNC/WBTS/WCEL /ADJE
ADJL Identifier
AdjLIdentifier
RNC/WBTS/WCEL /ADJE
CSFBDetection
CSFB detection for LTE layering
RNMOBI
Table 92: Modified parameters lists parameters modified by this feature. Table 92
Issue: 01F
Modified parameters
Full name
Abbreviated name
Managed object
RNC Options
RncOptions
RNC
BTS support for HSPA CM
BTSSupportForHSPACM
RNC/WBTS
Max number of UEs in HSDPA CM due to NCHO
MaxNumberUEHSPACmNCH O
RNC/WBTS/WCEL
LTE Layer Cell HSDPA Load
LTELayerCellHSLoad
WCEL
Smart LTE Layering NRT user amount threshold
SmartLTELayeringUA
WCEL
Smart LTE Layering service control
SmartLTELayeringServ
RNMOBI
Smart LTE Layering Target System Selection
SmartLTELayeringTSysSel
WCEL
LTE Periodic trigger timer
LTEPeriodicTriggerTimer
RNC
LTE Measurement Averaging Window
LTEMeasAveWindow
RNC/FMCL
DN09146788
181
Radio resource management features
Table 92
RU50 Feature Descriptions and Instructions
Modified parameters (Cont.)
Full name
Abbreviated name
Managed object
LTE Maximum Measurement Period
LTEMaxMeasPeriod
RNC/FMCL
LTE Minimum Measurement Interval
LTEMinMeasInterval
RNC/FMCL
LTE Neighbor Carrier Frequency Search LTENcarrFreqSearchPeriod Period
RNC/FMCL
Adjacent LTE Frequency Priority
AdjLFreqPriority
RNC/HOPL
LTE Carrier frequency selection Minimum Rx Power level
AdjLMinRSRPLevel
RNC/HOPL
LTE Carrier frequency selection Minimum Rx qual level
AdjLMinRSRQLevel
RNC/HOPL
Identifier of inter- system adjacency to LTE
ADJLId
RNC/WBTS/WCEL /ADJL
FMCL Identifier
FMCLIdentifier
RNC/WBTS/WCEL
Maximum number of UEs in CM due to SLHO measurement
MaxNumberUECmSLHO
RNC/WBTS/WCEL
Table 93: Related PRFILE parameters lists existing PRFILE parameters related to this feature. Table 93
2.14.1.6
Related PRFILE parameters
Parameter ID
Parameter name
002:1916
RN60_MAINT_41
Sales information Table 94
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
RNC LK
2.14.2 Activating RAN2264: Smart LTE Handover Purpose Follow this procedure to activate this feature.
182
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Before you start Restart of the RNC and 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: OMS Element Manager Application Launcher Man-machine interface (MMI)
• • •
Before activating this feature, activate the license of the RAN2067: LTE Interworking feature (feature code 1755, see Activating RAN2067: LTE Interworking). This feature is controlled by the long-term ON/OFF license key. For information on managing licenses, see Licensing.
g
The feature code for this feature is 3414. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M: FEA=3414:ON; for mcRNC: set license feature-mgmt code 0000003414 feature-admin-state on
• •
g
No license is required for Flexi Direct RNC. Before activating this feature configure the following database objects and relevant parameters and attach them to WCDMA cell: •
HOPL (Inter-RAT (LTE) neighbor frequency parameter set) – – –
•
– –
•
Issue: 01F
AdjLFreqPriority (optional, default value exists) AdjLMinRSRPLevel (optional, see Further information section) AdjLMinRSRQLevel (optional, see Further information section)
ADJL (Inter-RAT (LTE) neighbor frequency definitions) –
g
LTEMinHoInterval (optional, default value exists) LTEMeasAveWindow (optional, default value exists) LTEMaxMeasPeriod (optional, default value exists) LTEMinMeasInterval (optional, default value exists) LTENcarrFreqSearchPeriod (optional, default value exists)
AdjLEARFCN (mandatory) HopLIdentifier (mandatory) AdjLMeasBw (optional, default value exists) Note that even though configuring AdjLMeasBw parameter is not mandatory for creating ADJL-object, it is important for network planning.
ADJE (Inter-RAT (LTE) neighbor cell definitions)
DN09146788
183
Radio resource management features
– – – – – – – –
RU50 Feature Descriptions and Instructions
AdjePhysicalCellId (mandatory) AdjeMCC (mandatory) AdjeMNC (mandatory) AdjeMNCLength (optional, default value exists for the 2 digit MNC) AdjeENodeBId (mandatory) AdjeCellId (mandatory) AdjeTAC (mandatory) AdjLIdentifier (mandatory)
Additionally, the following parameters can be used for tuning the RAN2264: Smart LTE Handover feature: • • • • • •
RNC parameter LTEPeriodicTriggerTimer (optional, default value exists) RNMOBI parameter SmartLTELayeringServ (optional, default value exists) WCEL parameter LTELayerCellHSLoad (optional, default value exists) WCEL parameter SmartLTELayeringUA (optional, default value exists) WCEL parameter SmartLTELayeringTSysSel (optional, default value exists) RNHSPA parameter TGPLForLTEMeas (optional, default value exists)
Before activating this feature ensure the correctness of the following neighboring LTE and CN configuration and identifier parameters: • • • • • • • • • •
RNC O&M is not able to verify the values of these parameters.
g
184
The RAN2264: Smart LTE Handover feature is activated on cell basis.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
1
Open the OMS Element Manager.
2
Go to Topology.
3
Expand the ROOT.
4
Expand the RNC object.
5
Expand the WBTS object.
6
Configure the WCEL object: a) Select Edit Parameters from the WCEL object. b) Activate the RAN2264: Smart LTE Handover feature with the LTEHandoverEnabled parameter.
g g
WCEL should be associated with FMCL object.
State of the licenses must not be changed after activating the feature. Further information WCEL parameter LTEHandoverEnabled enables triggers for the Smart LTE Handover as follows: • • • • • • • • •
value (0) = all triggers disabled value (1) = T1 enabled value (2) = T1 and T2 enabled value (3) = T1 and T3 enabled value (4) = T1, T2, and T3 enabled value (5) = T1 and T4 enabled value (6) = T1, T2, and T4 enabled value (7) = T1, T3, and T4 enabled value (8) = all triggers enabled (T1, T2, T3, and T4)
where: • • • •
T1: RRC state change Cell_DCH to CCH T2: HSDPA/HSPA to DCH/DCH CTS T3: CS RAB release T4: Periodic trigger
For more information, see Description of RAN2264: Smart LTE Handover. Limiting the UEs allowed to be handed over to LTE can be activated with the following parameters:
When the limitation is activated, handover to LTE is allowed only to UEs, that are indicated to be redirected from LTE to WCDMA and/or are indicated to be in WCDMA because of CS fallback (CSFB). For more information on CSFBDetection and 002:1916 RN60_MAINT_41 parameters, see Description of RAN2264: Smart LTE Handover and Reference documentation. The HSUPA compressed mode measurement support for LTE is provided by the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature. If the feature is not available, E-DCH to UL DCH switch is needed before starting the LTE measurements for handover. For instructions on how to activate and configure DCH/DCH compressed mode (CM) and HSDPA/DCH CM for LTE handover, see Activating RAN2980: Measurement Based LTE Layering. For information on how to activate and configure HSPA CM for LTE handover, see Activating RAN1668 HSUPA Compressed Mode for LTE and Inter-frequency Handover. The minimum required RSRP (AdjLMinRSRPLevel) and RSRQ (AdjLMinRSRQLevel) levels of the cell under LTE carrier frequency should be aligned with the corresponding thresholds in the LTE network. Ensure that the UE is not redirected or handed over from WCDMA to LTE with the RSRP or RSRQ levels, which are lower than the thresholds for the coverage (RSRP) or quality (RSRQ)-based handover from LTE to WCDMA. For example, if the coverage (RSRP) based handover from LTE to WCDMA is configured to trigger with RSRP level – 115 dBm, then the recommended minimum RSRP threshold for the WCDMA to LTE handover is – 112 dBm (3 dB hysteresis) in order to avoid immediate handover back to WCDMA. Correspondingly, if the quality (RSRQ)-based handover from LTE to WCDMA is configured to trigger with RSRQ level - 15 dB, then the minimum RSRQ threshold for the WCDMA to LTE handover should be set to - 12 dB (3 dB hysteresis). Inter-RAT handover from WCDMA to LTE is supported for the following PS QoS classes: • •
Interactive (NRT) Background (NRT)
2.14.3 Verifying RAN2264: Smart LTE Handover Purpose Follow this procedure to verify that this feature works properly in the network. The functioning of the RAN2264: Smart LTE Handover feature can be verified with the following counters for the inter-RAT LTE handover attempts and successes: • • • • • •
186
M1010C252 LTE NRT ISHO ATTEMPTS DUE TO DCH TO CCH M1010C253 LTE NRT ISHO ATTEMPTS DUE TO HSPA TO DCH M1010C254 LTE NRT ISHO ATTEMPTS DUE TO CS RAB RELEASE M1010C255 LTE NRT ISHO ATTEMPTS DUE TO PERIODIC TRIGGER M1010C256 LTE NRT ISHO SUCCESS DUE TO DCH TO CCH M1010C257 LTE NRT ISHO SUCCESS DUE TO HSPA TO DCH
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
• •
Radio resource management features
M1010C258 LTE NRT ISHO SUCCESS DUE TO CS RAB RELEASE M1010C259 LTE NRT ISHO SUCCESS DUE TO PERIODIC TRIGGER
Expected outcome Outgoing inter-RAT LTE handover is successful and visible in the attempt and success counters. Further information More detailed monitoring of the RAN2264: Smart LTE Handover feature can be performed with the following counters: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
Issue: 01F
M1010C239 DURATION OF LTE CARRIER MEASUREMENT M1010C240 LTE NRT ISHO MEAS WITH CM DUE TO DCH TO CCH M1010C241 LTE NRT ISHO MEAS WITH CM DUE TO HSPA TO DCH M1010C242 LTE NRT ISHO MEAS WITH CM DUE TO CS RAB RELEASE M1010C243 LTE NRT ISHO MEAS WITH CM DUE TO PERIODIC TRIGGER M1010C244 LTE NRT ISHO MEAS WITHOUT CM DUE TO DCH TO CCH M1010C245 LTE NRT ISHO MEAS WITHOUT CM DUE TO HSPA TO DCH M1010C246 LTE NRT ISHO MEAS WITHOUT CM DUE TO CS RAB RELEASE M1010C247 LTE NRT ISHO MEAS WITHOUT CM DUE TO PERIODIC TRIGGER M1010C248 LTE NRT ISHO NO CELL FOUND DUE TO DCH TO CCH M1010C249 LTE NRT ISHO NO CELL FOUND DUE TO HSPA TO DCH M1010C250 LTE NRT ISHO NO CELL FOUND DUE TO CS RAB RELEASE M1010C251 LTE NRT ISHO NO CELL FOUND DUE TO PERIODIC TRIGGER M1010C260 LTE NRT ISHO UE NACK DUE TO DCH TO CCH M1010C261 LTE NRT ISHO UE NACK DUE TO HSPA TO DCH M1010C262 LTE NRT ISHO UE NACK DUE TO CS RAB RELEASE M1010C263 LTE NRT ISHO UE NACK DUE TO PERIODIC TRIGGER M1010C264 LTE NRT ISHO UE LOST DUE TO DCH TO CCH M1010C265 LTE NRT ISHO UE LOST DUE TO HSPA TO DCH M1010C266 LTE NRT ISHO UE LOST DUE TO CS RAB RELEASE M1010C267 LTE NRT ISHO UE LOST DUE TO PERIODIC TRIGGER M1010C268 LTE NRT ISHO PREPARATION FAIL M1019C0 LTE ISHO ATTEMPTS M1019C1 LTE ISHO SUCCESSFUL M1036C0 LTE PS ISHO OUT PREP REQ M1036C1 LTE PS ISHO OUT PREP SUCC M1036C2 LTE PS ISHO OUT PREP FAIL DUE TO RN LAYER CAUSE M1036C3 LTE PS ISHO OUT PREP FAIL DUE TO TR LAYER CAUSE M1036C4 LTE PS ISHO OUT PREP FAIL DUE TO NAS CAUSE M1036C5 LTE PS ISHO OUT PREP FAIL DUE TO PROT CAUSE M1036C6 LTE PS ISHO OUT PREP FAIL DUE TO MISC CAUSE M1036C7 LTE PS ISHO OUT PREP FAIL DUE TO NON STAN CAUSE M1036C8 LTE PS ISHO CANCEL TOTAL M1036C9 LTE PS ISHO FAIL DUE TO RELOC OVERALL TIMER EXPIRY M1036C10 LTE PS ISHO CANCEL DUE TO RELOC PREP TIMER EXPIRY
DN09146788
187
Radio resource management features
RU50 Feature Descriptions and Instructions
2.14.4 Deactivating RAN2264: Smart LTE Handover Purpose Follow this procedure to deactivate this feature.
g
The RAN2264: Smart LTE Handover feature is deactivated on cell basis.
1
Open the OMS Element Manager.
2
Go to Topology.
3
Expand the ROOT.
4
Expand the RNC object.
5
Expand the WBTS object.
6
Configure the WCEL object: a) Select Edit Parameters from the WCEL object. b) Deactivate the RAN2264: Smart LTE Handover feature with the LTEHandoverEnabled parameter.
2.14.5 Testing RAN2264: Smart LTE Handover
g 2.14.5.1
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.
Testing that RRC state change from Cell_DCH to CCH triggers LTE handover Purpose This test case verifies that the compressed mode is activated and a handover from WCDMA to LTE is triggered after the UE sends a valid measurement report. The trigger for starting LTE measurements is T1: RRC state change from Cell_DCH to CCH. Testing environment • • • • • • •
188
CS core PS core RNC WBTS x 2 MMEe UE, Rel-8 category, that is capable of LTE handover interface monitoring equipment for Iub and Iu interfaces
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Before you start The following features must be activated: • •
HSPA must be activated for the 3G cell. The following parameters must be set in the RNC RNW database:
•
The WCEL1 - LTEHandoverEnabled parameter must be set to 8 (Enabled for all triggers). The WCEL1 - SmartLTELayeringUA parameter must be set to 0.
1
Establish a PS-NRT call on HSPA and start data transfer.
2
Stop data transfer to trigger the state transition to CCH.
3
Adjust the radio conditions so that the UE reports candidate cells with RSRP/RSRQ values exceeding the required thresholds and the PS handover to LTE is started.
4
Verify that:
•
• • • •
2.14.5.2
The RANAP: Relocation Required message is sent from the RNC to the PS CN. The RANAP: Relocation Command message is sent from the PS CN to the RNC. The RANAP: IU Release Command message is sent from the PS CN to the RNC. The UE is successfully relocated to LTE.
Testing that change from HSDPA/HSPA to DCH/DCH CTS triggers LTE handover Purpose This test case verifies that the compressed mode is activated and a handover from WCDMA to LTE is triggered after the UE sends a valid measurement report. The trigger for starting LTE measurements is T2: HSDPA/HSPA to DCH/DCH CTS. Testing environment • • • • • • •
Issue: 01F
CS core PS core RNC WBTS x 2 MMEe UE, Rel-8 category, that is capable of LTE handover interface monitoring equipment for Iub and Iu interfaces
DN09146788
189
Radio resource management features
RU50 Feature Descriptions and Instructions
Before you start The following features must be activated: • •
HSPA must be activated for the 3G cell. The following parameters must be set in the RNC RNW database:
•
The WCEL1 - LTEHandoverEnabled parameter must be set to 8 (Enabled for all triggers). The WCEL1 - SmartLTELayeringUA parameter must be set to 0.
1
Establish a PS-NRT call on HSPA and start data transfer.
2
Attenuate the cell to trigger the CTS from HSPA to DCH/DCH.
•
Verify that measurements for LTE are initiated because of T2 trigger. 3
Adjust the radio conditions so that the UE reports candidate cells with RSRP/RSRQ values exceeding the required thresholds and PS handover to LTE is started.
4
Verify that: • • • •
2.14.5.3
The RANAP: Relocation Required message is sent from the RNC to the PS CN. The RANAP: Relocation Command message is sent from the PS CN to the RNC. The RANAP: IU Release Command message is sent from the PS CN to the RNC. All UE-related resources are released in the SRNC.
Testing that CS RAB release triggers LTE handover Purpose This test case verifies that the compressed mode is activated and a handover from WCDMA to LTE is triggered after the UE sends a valid measurement report. The trigger for starting LTE measurements is T3: CS RAB Release. Test environment • • • • • • •
190
CS core PS core RNC WBTS x 2 MMEe UE, Rel-8 category, that is capable of LTE handover interface monitoring equipment for Iub and Iu interfaces
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Before you start The following features must be activated: • • •
RAN2264: Smart LTE Handover RAN2067: LTE Interworking RAN974: HSUPA with Simultaneous AMR Voice Call
HSPA must be activated for the 3G cell. The following parameters must be set in the RNC RNW database:
•
The WCEL1 - LTEHandoverEnabled parameter must be set to 8 (Enabled for all triggers). The WCEL1 - SmartLTELayeringUA parameter must be set to 0. The RNFC – AMRWithEDCH parameter must be set to 1 (Enabled).
1
Establish an AMR call and a PS-NRT call in 3G. Start data transfer on HSPA.
2
Release the AMR call.
• •
Verify that measurements for LTE are initiated because of T3 trigger. CTS from HSPA to HSDPA is triggered because the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature is not enabled (compressed mode is not allowed on HSUPA). 3
Adjust the radio conditions so that the UE reports candidate cells with RSRP/RSRQ values exceeding the required thresholds and PS handover to LTE is started.
4
Verify that: • • • • •
2.14.5.4
The RANAP: Relocation Required message is sent from the RNC to the PS CN. The RANAP: Relocation Command message is sent from the PS CN to the RNC. The RANAP: IU Release Command message is sent from the PS CN to the RNC. All UE-related resources are released in the SRNC. The UE is successfully relocated to LTE.
Testing that periodic trigger triggers LTE handover Purpose This test case verifies that the compressed mode is activated and a handover from WCDMA to LTE is triggered after the UE sends a valid measurement report. The trigger for starting LTE measurements is T4: Periodic trigger. Before you start The following features must be activated:
HSPA must be activated for the 3G cell. The following parameters must be set in the RNC RNW database:
•
The RNC - LTEPeriodicTriggerTimer parameter must be set to 10 sec. The WCEL1 - LTEHandoverEnabled parameter must be set to 8 (Enabled for all triggers). The WCEL1 - SmartLTELayeringUA parameter must be set to 0.
1
Establish a PS-NRT call on HSPA and start data transfer.
• •
• •
Verify that measurements for LTE are initiated 10 seconds after the RRC connection setup because of T4 trigger. CTS from HSPA to HSDPA is triggered because the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature is not enabled (CM is not allowed on HSUPA).
2
Adjust the radio conditions so that the UE reports candidate cells with RSRP/RSRQ values exceeding the required thresholds and PS handover to LTE is started.
3
Verify that: • • • •
The RANAP: Relocation Required message is sent from the RNC to the PS CN. The RANAP: Relocation Command message is sent from the PS CN to the RNC. The RANAP: IU Release Command message is sent from the PS CN to the RNC. The UE is successfully relocated to LTE.
2.15 RAN2546: VHS Receiver for High Speed Train 2.15.1 Description of RAN2546: VHS Receiver for High Speed Train Introduction to the feature The feature introduces the new BTS receiver algorithm, for serving the UEs moving at the speed higher than 250 km/h (155 mph), up to the 350 km/h (217 mph).
2.15.1.1
Benefits End-user benefits This feature provides the end-user with the following benefits::
192
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
• •
Radio resource management features
The possibility of making better-quality voice calls, for UEs moving at high speed (for example in trains). Experiencing throughput enhancement when moving at a high speed.
Operator benefits This feature provides the operator with the following benefits (when the UE is moving at high speed): • • • • •
2.15.1.2
increase of the end-user satisfaction improvement in the call-related KPIs improvement in the power control stability better DCH and HSPA throughputs and coverage avoiding the UL interference spikes at the beginning of the connection
Requirements Software requirements Table 95: Software requirements lists software required for this feature. Table 95
Software requirements
RAS
Flexi Direct
IPA-RNC
mcRNC
Flexi Direct RNC
OMS
Flexi BTS Flexi Lite BTS
RU50 EP1
Support not required
Support not required
Support not required
Support not required
Support not required
WN9.1
Not planned
Flexi 10 BTS
NetAct
MSC
SGSN
MGW
UE
WN9.1
NetAct 8 EP2 (NetAct 15)
Support not required
Support not required
Support not required
Support not required
Hardware requirements This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF.
2.15.1.3
Functional description The new algorithm introduced with the RAN2546: VHS Receiver for High Speed Train feature is called: Very High Speed approach (the VHS approach). The feature improves the receiver performance in terms of power stability and decoding performance at a high speed up to 350 km/h (217 mph). This feature is controlled by the license and activated on the BTS level.
2.15.1.4
System impact Interdependencies between features This feature affects the following feature: •
Issue: 01F
RAN1702: Frequency Domain Equalizer
DN09146788
193
Radio resource management features
RU50 Feature Descriptions and Instructions
Impact on interfaces The feature does not impact the system interface.
Impact on network and network element management tools The feature does not impact the network and network element management tools.
Impact on system performance and capacity The feature impacts the system performance and capacity as follows: • • • • • •
2.15.1.5
stabilizing the power control function both in the UL and DL improving the UL channel decoding performance (for the UEs moving at high speed) achieving from 3 to 4 dB gain in decoding performance for the R99 CS/PS service at high speed (350 km/h; 217 mph) improving the HS-DPCCH ACK/NACK decoding performance resulting in improved the HS-DSCH throughput at a high speed improving the E-DCH throughput increasing the CPU cycles in DSP(Rake) consumption
RAN2546: VHS Receiver for High Speed Train management data Alarms There are no new alarms related to this feature.
Measurements and counters There are no new measurements or counters related to this feature.
Key performance indicators There are no new key performance indicators related to this feature.
Parameters There are no new parameters related to this feature.
2.15.1.6
Sales information Table 96
Sales information
BSW/ASW
RAS SW component
License control in network element
ASW
RAN
BTS LK
2.15.2 Activating RAN2546: VHS Receiver for High speed Train Purpose Follow this procedure to activate this feature. Before you start Make sure you fulfilled SW and HW requirements for this feature. For more information on the feature and its requirements, seeRequirements feature description.
194
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Make sure RAN1808: High Speed Train Support feature is active.
1
Install feature-related license and switch its status on a BTS to ON.
2
Begin re-configuration of BTS in BTS Site Manager. a) b) c) d)
Open BTS Element Manager. From the menu on the left hand side, select Commissioning. Select Reconfiguration Commissioning type. Click Next to confirm.
Figure 12
3
Re-configuration enabling
Activate VHS on the BTS. Proceed by clicking Next to the menu shown in the Figure 13: BTS Settings menu. Select VHS receiver for high speed train enabled.
Issue: 01F
DN09146788
195
Radio resource management features
Figure 13
4
RU50 Feature Descriptions and Instructions
BTS Settings menu
Send parameters to the BTS. Go the last page of BTS commissioning settings and send parameters to the BTS. Click Send Parameters as shown in the Figure 14: Send parameters menu. Figure 14
t
196
Send parameters menu
Save setting before transferring them out.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Radio resource management features
This action takes approximately seven minutes. BTS will be restarted. 5
Finish the activation. Proceed by clicking Next to Commissioning Report menu and click Finish.
Result The feature is enabled without any additional RNC, OMS and NetAct configuration steps. Table 97
Post configuration conditions
Condition
State
Result
Feature license is on for the BTS and VHS is activated in the BTS
yes
VHS is enabled for the BTS
Feature license is on for the BTS and VHS is activated in the BTS
no
VHS is disabled for the BTS
VHS is enabled for a certain BTS
yes
BTS is working in Mode 2. Good performance is up to 350km/h.
VHS is enabled for a certain BTS
no
BTS is working in Mode 1. Good performance is up to 250km/h.
2.15.3 Verifying RAN2546: VHS Receiver for High speed Train 1
Check BTS setting in the commissioning report. Open the saved configuration report and check whether VHS receiver for high speed train enabled:stats is Yes as on the Figure 15: Commissioning report.
Issue: 01F
DN09146788
197
Radio resource management features
Figure 15
RU50 Feature Descriptions and Instructions
Commissioning report
2.15.4 Deactivating RAN2546: VHS Receiver for High speed Train 1
Switch the feature license on a BTS to OFF.
2
Re-commission BTS without feature enabled. Perform all steps from Begin re-configuration of BTS in BTS Site Manager. to Finish the activation..
t
Remember to untick VHS receiver for high speed train enabled in step Activate VHS on the BTS.. Result The feature has been disabled.
198
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
2.16 RAN2881: WCDMA and GSM Layer Priorities 2.16.1 Description of RAN2881: WCDMA and GSM Layer Priorities Introduction to the feature The RAN2881: WCDMA and GSM Layer Priorities feature allows idle mode traffic steering according to priorities given for WCDMA and GSM layers.
2.16.1.1
Benefits End-user benefits This feature provides end-user higher data rates and faster response times.
Operator benefits Introduced idle-mode traffic steering reduces the need for handovers and reselects the best possible layer for the end-user. Operator controls the priorities of the layers.
2.16.1.2
Requirements Software requirements Table 98: Software requirements lists the software required for this feature. Table 98
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
Flexi BTS
RU50
Not planned RN8.0
mcRNC4.1
Not planned OMS3.0 1)
Support not required
OMS3.1 2)
Flexi Lite BTS
Flexi 10 BTS
NetAct
MSC
SGSN
MGW
Support not required
Support not required
NetAct 8 EP1 1)
Support not Support not Support not required required required
UE
3GPP Rel-8
NetAct 8 EP2 (NetAct 15) 2)
1) for RU50 2) for RU50 EP1
Issue: 01F
DN09146788
199
Radio resource management features
RU50 Feature Descriptions and Instructions
Hardware requirements This feature does not require any new or additional hardware.
2.16.1.3
Functional description Functional overview The RAN2881: WCDMA and GSM Layer Priorities feature enables WCDMA and GSM cell reselection based on layer/Radio Access Technology priorities. When layer-specific absolute priority information is provided in the system information block type 19 (SIB19), UE periodically measures higher priority layers. UE measurements are applicable when the UE is in idle mode, Cell_PCH, or URA_PCH state. Also lower and equal priority layers are measured by UE, if radio conditions in the camped frequency fall below criteria defined with search thresholds. Based on results of these measurements, UE performs priority-based cell reselection using both coverage and quality thresholds broadcast in SIB19. For WCDMA and GSM priority-based cell reselection these thresholds are specified in 3GPP Rel-8. In addition to the priority number for the layer, signal strength and quality thresholds are provided for cell reselection. Frequency band prioritization can be adjusted with thresholds, for example, 900 MHz can be preferred for cell edge UEs and 2100 MHz - for close by UEs. UEs above certain threshold move to higher priority layer, whereas cell edge UEs prefer low priority layer as they are below the threshold. Figure 16: WCDMA and GSM cell reselection based on layer priorities shows the mechanism of cell reselection. The absolute priority mechanism is 3GPP Rel-8 feature. Figure 16
2.16.1.4
WCDMA and GSM cell reselection based on layer priorities
System impact Interdependencies between features Hierarchical Cell Structure cannot be used simultaneously with RAN2881: WCDMA and GSM Layer Priorities feature.
200
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Radio resource management features
Impact on commands There are no commands related to this feature.
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.
2.16.1.5
RAN2881: WCDMA and GSM Layer Priorities management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
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 99: New parameters lists parameters introduced with this feature and the corresponding SIB19 parameters specified in 3GPP Rel-8. Table 99
New parameters
Full name
Abbreviated name
SIB19 IE
Managed object
WCDMA Cell Reselection
WCDMACellReselection
N/A
WCEL
GSM Cell Reselection
GSMCellReselection
N/A
WCEL
Absolute priority for inter-frequency cell reselection
AdjiAbsPrioCellReselec
priority
HOPI
Threshold high for inter-frequency cell reselection
AdjiThreshigh
Threshx,high
HOPI
Threshold low for inter-frequency cell reselection
AdjiThreslow
Threshx,low
HOPI
QqualminFDD for inter-frequency cell reselection
AdjiQqualminFDD
QqualminFDD
HOPI
Issue: 01F
DN09146788
201
Radio resource management features
Table 99
RU50 Feature Descriptions and Instructions
New parameters (Cont.)
Full name
Abbreviated name
SIB19 IE
Managed object
QrxlevminFDD for inter-frequency cell reselection
AdjiQrxlevminFDD
QrxlevminFDD
HOPI
Absolute priority for GSM cell reselection
AdjgAbsPrioCellReselec
priority
HOPG
Threshold high for GSM cell reselection
AdjgThreshigh
Threshx,high
HOPG
Threshold low for GSM cell reselection
AdjgThreslow
Threshx,low
HOPG
Thresh serving low 2
Threshservlow2
Threshserving,low2
WCEL
System Information Block 19 Compmask 5
SIB19Compmask5
N/A
WCEL
System Information Block 19 Compmask 6
SIB19Compmask6
N/A
WCEL
System Information Block 19 Compmask 7
SIB19Compmask7
N/A
WCEL
Table 100: Modified parameters lists parameters modified by this feature and the corresponding SIB19 parameters specified in 3GPP Rel-8. Table 100
Modified parameters
Full name
Abbreviated name
SIB19 IE
Managed object
RNC Options
RncOptions
N/A
RNC
Absolute priority level for cell reselection
AbsPrioCellReselec
priority
WCEL
S prioritysearch1
Sprioritysearch1
Sprioritysearch1
WCEL
S prioritysearch2
Sprioritysearch2
Sprioritysearch2
WCEL
Thresh serving low
Threshservlow
Threshserving,low
WCEL
UTRA Absolute Radio Frequency Channel Number
AdjiUARFCN
UARFCN
ADJI
RT HOPI Identifier
RtHopiIdentifier
N/A
ADJI
Cell Re-selection Minimum RX Level
AdjgQrxlevMin
QrxlevminGSM
HOPG
RT HOPG Identifier
RtHopgIdentifier
N/A
ADJG
Cell Reselection Absolute Priority
AdjLAbsPrioCellReselec
priority
HOPL
202
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 100
Radio resource management features
Modified parameters (Cont.)
Full name
Abbreviated name
SIB19 IE
Managed object
Priority for SIB19
SIB19Priority
N/A
RNC
List of Compmasks in System Information Block 19
SIB19CompmaskInfo
N/A
WCEL
Block 19 Compmask 1
SIB19Compmask1
N/A
WCEL
System Information Block 19 Compmask 2
SIB19Compmask2
N/A
WCEL
System Information Block 19 Compmask 3
SIB19Compmask3
N/A
WCEL
System Information Block 19 Compmask 4
SIB19Compmask4
N/A
WCEL
Table 101: Related existing parameters lists existing parameters related to this feature and the corresponding SIB19 parameters specified in 3GPP Rel-8. Table 101
Related existing parameters
Full name
Abbreviated name
SIB19 IE
Managed object
BCCH ARFCN
AdjgBCCH
GSM cell group List / Starting ARFCN
ADJG
GSM cell group List / List of ARFCNs Band Indicator
2.16.1.6
AdjgBandIndicator
GSM cell group List / Band Indicator
ADJG
Sales information Table 102
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
RNC LK
2.16.2 Activating RAN2881: WCDMA and GSM Layer Priorities Purpose Follow this procedure to activate the RAN2881: WCDMA and GSM Layer Priorities feature.
Issue: 01F
DN09146788
203
Radio resource management features
RU50 Feature Descriptions and Instructions
Before you start After activating this feature there is no need to restart neither the RNC, nor the BTS. Activating procedure does not cause downtime and the feature can be activated at any time of the day. Activate the license of the RAN2881: WCDMA and GSM Layer Priorities feature using WCDMA and GSM Layer Priorities license key. To set the feature state to ON, use the following command: • •
for IPA-RNC: ZW7M: FEA=4781:ON; for mcRNC: set license feature-mgmt code 0000004781 feature-admin-state on
For information on managing licenses, see Licensing. To provide seamless priority-based cell reselection between GSM, WCDMA, and LTE, make sure to admit each Radio Access Technology a different priority: •
•
•
•
g
AbsPrioCellReselec WCEL parameter, introduced with the RAN2067:LTE Interworking feature, defines the priority of the WCDMA serving cell (UTRA priority info list/UTRA Serving Cell IE) AdjiAbsPrioCellReselec HOPI parameter, introduced with the RAN2881: WCDMA and GSM Layer Priorities feature, defines the WCDMA inter-frequency priority (UTRA priority info list/UTRAN FDD Frequencies IE) AdjgAbsPrioCellReselec HOPG parameter, introduced with the RAN2881: WCDMA and GSM Layer Priorities feature, defines the GSM priority (GSM priority info list/GSM Priority Info IE) AdjLAbsPrioCellReselec HOPL parameter, introduced with the RAN2067: LTE Interworking feature, defines the LTE priority (E-UTRA frequency and priority info list/E-UTRA frequency and priority IE) Priority-based cell reselection between WCDMA and LTE radio technologies is provided by the RAN2067: LTE Interworking feature. The RAN3069: RSRQ-based LTE Reselection feature is an extension to the RAN2067: LTE Interworking feature and provides quality thresholds for LTE prioritybased cell reselection.
RtHopiIdentifier (RT HOPI Identifier) ADJI parameter is used for defining parameter set for WCDMA inter-frequency absolute priority cell reselection. RtHopgIdentifier (RT HOPG Identifier) ADJG parameter is used for defining parameter set for GSM absolute priority cell reselection.
g
To allow equal/lower priority layer measurements before reaching minimum required quality level in the WCDMA cell, the value of Sprioritysearch2 WCEL parameter needs be higher than the value of Threshservlow2 WCEL parameter. WCDMA priority is broadcast per UARFCN in SIB19 message. The same priority value should be given for each inter-frequency WCDMA neighbor. If more than one value is given, the highest priority is broadcast in SIB19 message. Correspondingly, GSM priority is broadcast per GSM cell group (BCCH ARFCN + Band Indicator) in SIB19 message. Thus, priority should be defined so that the same priority value is given for each GSM neighbor within the same frequency. If more than one value is given, the highest priority is broadcast in SIB19 message.
204
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Radio resource management features
Before enabling the GSMCellReselection WCEL parameter in the cell, make sure that GSM priority (AdjgAbsPrioCellReselec parameter) is defined for each GSM neighbor cell. If priority information is provided for any GSM layer, cells belonging to GSM layer for which no priority is assigned are not considered for reselection. Default value of AdjgAbsPrioCellReselec parameter means that GSM priority is not defined.
1
Open the OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object and then the WBTS object.
4
Configure the WCEL object: a) Right-click on the WCEL object and select Edit parameters. b) In System Info tab, set the values of WCDMACellReselection and GSMCellReselection parameter to Enabled.
Further information
g
Note that the UE does not use Hierarchical Cell Structure (HCS) for inter-frequency or inter-RAT reselection if absolute-priority-based cell reselection is used.
2.16.3 Verifying RAN2881: WCDMA and GSM Layer Priorities Purpose Follow these tips to verify that the RAN2881: WCDMA and GSM Layer Priorities feature works properly in the network. Before you start
g
There are no counters involved in cell reselection process. UE reselects the cell according to the parameters broadcast by the network in SIB19 message. When the RAN2881: WCDMA and GSM Layer Priorities feature is active, it is visible in the content of SIB19 message. After activating this feature and ascribing values to the parameters listed in RAN2881: WCDMA and GSM Layer Priorities management data section, the following information elements will be broadcasted in SIB19 message: • • •
UTRA priority info list/UTRA Serving Cell UTRA priority info list/UTRAN FDD Frequencies GSM priority info list/GSM Priority Info
Content of SIB19 message can be monitored by using UE and network protocol analyzer. Further information
Issue: 01F
DN09146788
205
Radio resource management features
RU50 Feature Descriptions and Instructions
Camping on a desired layer is perfomed by UE using SIB19 parameters. Cell reselection algorithm is specified in 3GPP TS 25.304 User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode.
2.16.4 Deactivating RAN2881: WCDMA and GSM Layer Priorities Purpose Follow this procedure to deactivate the RAN2881: WCDMA and GSM Layer Priorities feature.
1
Open the OMS Element Manager.
2
Go to Topology and expand the ROOT directory.
3
Expand the RNC object and then the WBTS object.
4
Configure the WCEL object: a) Right-click on the WCEL object and select Edit parameters. b) In System Info tab, set the values of WCDMACellReselection and GSMCellReselection parameter to Disabled.
206
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Telecom features
3 Telecom features 3.1 RAN2211: Multi-Cell HSDPA (trial) 3.1.1 Description of RAN2211: Multi-Cell HSDPA
g
The RAN2211 feature description presents the trial functionalities of the feature. The feature in this state cannot be tried on the live network. For more information on testing possibilities and limitations, contact Nokia directly.
Introduction to the feature This feature enables usage of up to 3 simultaneous HSDPA DL frequency carriers for one user.
3.1.1.1
Benefits End-user benefits This feature allows for the usage of three frequency carriers, what in combination with the RAN1643: 64QAM feature, enables the end-user achieving downlink peak data rates up to 63 Mbps. The gains to the end-user can be noticed when using the Internet and transmitting packet data.
Operator benefits By implementing this feature, operator benefits from the enhanced average user and cell throughput and enhanced end-user satisfaction. The throughput in the cell can be on average even 5% to 50% bigger, compared to the DC + 64QAM usage (depending on the network load).
3.1.1.2
Requirements Software requirements Lab trial capability for Multi-Cell HSDPA is a separate trial SW intended to be used in Nokia R&D lab. RAN2211 trial SW is not intended for field or live operation. For more information on the trial software requirements, contact your local customer support.
Hardware requirements For more information on the trial hardware requirements, contact Nokia directly.
3.1.1.3
Functional description The feature supports 3C-HSDPA configuration for one UE with one NRT service in the laboratory-conditions trial. The trial software is not intended for field or live operation. The scope of the trial is to demonstrate the 63 Mbps single user peak rate. For more information on the trial feature functionalities, contact Nokia directly.
Issue: 01F
DN09146788
207
Telecom features
3.1.1.4
RU50 Feature Descriptions and Instructions
System impact Interdependencies between features This feature requires the following features: • •
RAN826: Basic HSUPA RAN1906: DC-HSDPA 42 Mbps
The following features are related to the RAN2211: Multi-Cell HSDPA feature: • • • • • • • • • • • • • •
RAN2179: Dual Band HSDPA 42Mbps RAN1643: HSDPA 64QAM RAN1645: HSUPA 16QAM RAN981: HSUPA 5.8 Mbps RAN1262: QoS Aware HSPA Scheduling RAN1803: L2 resource management RAN955: Power saving mode for BTS RAN2394: Extended BTS Site Capacity RAN2398: Chaining of Several Flexi Release 2 System Modules (>2) RAN2879: Mass Event Handler RAN2509: Application aware RAN RAN1881: RF Chaining RAN2736: 18 cells BTS RAN1644: CPC
The RAN2211: Multi-Cell HSDPA feature supports the following Iub transport modes: • •
RAN74: IP Based Iub for Flexi WCDMA BTS RAN1449: Dual Iub for Flexi WCDMA BTS
Impact on interfaces The Additional HS Cell Information IE will be modified for the following NBAP messages: • • • •
RADIO LINK SETUP REQUEST RADIO LINK RECONFIGURATION PREPARE RADIO LINK SETUP RESPONSE RADIO LINK RECONFIGURATION READY
The Ordinal Number of Frequency IE is added to HS-DSCH FDD Secondary Serving Information IE. The RNC assigns to the Ordinal Number of Frequency values for each of the secondary serving HS-DSCH RLs in consecutive order, starting with value 1. The Physical Channel capability IE is added to the RRC CONNECTION SETUP COMPLETE message. This IE corresponds to the HS-DSCH category supported by the UE when it is configured with multicell operation. The information is preserved for the lifetime of the RRC Connection. The Additional downlink secondary cell information IE is added to the following messages:
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 The RAN2211: Multi-Cell HSDPA feature impacts the system performance as follows: • • •
It increases the data rate up to 63Mbps In the uplink, about 1.5 % of the FTP downlink data rate is needed for TCP ACKs (40 Byte ACK for every second TCP packet of ~1500 Bytes). The amount signalling is increased: RRC and NBAP messages contain more data, when the MC-HSDPA is used (one new secondary carrier).
The RAN2211: Multi-Cell HSDPA feature impacts the system capacity as follows: • •
3.1.1.5
The feature multiplies the UE throughput for single carrier in the sector by aggregating the carriers It increases the frequency diversity in the cells
RAN2211: Multi-Cell HSDPA management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms There are no alarms related to the feature.
Measurements and counters The Table 103: Counters presents the counters related to the feature Table 103
Issue: 01F
Counters
Counter ID
Counter name
Measurement
M1001C743
ACCESS STRATUM RELEASE INDICATOR RELEASE 10
Service Level (RNC)
M1001C744
ACCESS STRATUM RELEASE INDICATOR RELEASE 11
Service Level (RNC)
M5000C449
DATA VOLUME OF MC HSDPA USERS SCHEDULED IN ONE CARRIER
HSPA in WBTS (WBTS)
DN09146788
209
Telecom features
RU50 Feature Descriptions and Instructions
Table 103
Counters (Cont.)
Counter ID
Counter name
Measurement
M5000C450
DATA VOLUME OF MC HSDPA USERS SCHEDULED IN TWO CARRIERS
HSPA in WBTS (WBTS)
M5000C451
DATA VOLUME OF MC HSDPA USERS SCHEDULED IN THREE CARRIERS
HSPA in WBTS (WBTS)
M5002C130
ORIGINAL HSDPA DATA
Cell Throughput in WBTS (WBTS)
M5002C126
ACKNOWLEDGED MC HSDPA DATA FOR PRIMARY CELL
Cell Throughput in WBTS (WBTS)
M5002C127
ACKNOWLEDGED MC HSDPA DATA FOR SECONDARY CELL
Cell Throughput in WBTS (WBTS)
M5000C436
MC HSDPA DATA DISCARDED IN MAC-D PDUS
HSPA in WBTS (WBTS)
M5000C435
MC HSDPA DATA RECEIVED IN MAC-D PDUS HSPA in WBTS (WBTS)
M5002C128
INAL MC HSDPA DATA FOR PRIMARY CELL
Cell Throughput in WBTS (WBTS)
M5002C129
ORIGINAL MC HSDPA DATA FOR SECONDARY CELL
Cell Throughput in WBTS (WBTS)
M1006C306
RADIO BEARER CONFIGURATION FOR MCHSDPA ATTEMPT
RRC signalling (RNC)
M1006C308
RADIO BEARER CONFIGURATION FOR MCHSDPA FAILED
RRC signalling (RNC)
M1006C307
RADIO BEARER CONFIGURATION FOR MCHSDPA SUCCESSFUL
RRC signalling (RNC)
M1001C745
UE SUPPORT FOR HSDSCH CLASS 29 OR 30
Service Level (RNC)
M1001C746
UE SUPPORT FOR HSDSCH CLASS 31 OR 32
Service Level (RNC)
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table 104: New parameters lists parameters introduced with this feature. Table 104
210
New parameters
Full name
Abbreviated name
Managed object
Multi Cell HSDPA Enabled
MCellHSDPAEnabled
WCEL
AM RLC maximum buffer AMRLCMaximumBufferUE1500 allocation for UE capability 1500
RNRLC
AM RLC maximum buffer AMRLCMaximumBufferUE1800 allocation for UE capability 1800
RNRLC
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 104
Telecom features
New parameters (Cont.)
Full name
Abbreviated name
Managed object
AM RLC maximum buffer AMRLCMaximumBufferUE2550 allocation for UE capability 2550
RNRLC
AM RLC maximum buffer AMRLCMaximumBufferUE2300 allocation for UE capability 2300
RNRLC
Table 105: Modified parameters lists parameters modified by this feature. Table 105
3.1.1.6
Modified parameters
Full name
Abbreviated name
Managed object
RNC Options
RncOptions
RNC
Dual Band HSDPA Enabled
DBandHSDPAEnabled
WCEL
DC HSDPA Enabled
DCellHSDPAEnabled
WCEL
Sector Identifier
SectorID
WCEL
Frame timing offset of a cell
Tcell
WCEL
DRRC connection setup for HSDPA layer enhancements
DirectedRRCForHSDPALayerEnhanc
RNMOBI
Maximum bit rate of NRT MAC-d flow
MaxBitRateNRTMACDFlow
RNHSPA
CQI Feedback Cycle for CPC NRT 2ms TTI
N2msCQIFeedbackCPC
RNHSPA
CQI Feedback Cycle for CPC NRT 10ms TTI
N10msCQIFeedbackCPC
RNHSPA
AM RLC maximum buffer allocation for UE
AMRLCMaximumBufferUE
RNRLC
Sales information Table 106
Sales information
BSW/ASW SW component License control in network element ASW
Issue: 01F
HSPA
RNC LK
DN09146788
211
Transmission and transport features
RU50 Feature Descriptions and Instructions
4 Transmission and transport features 4.1 RAN2913: Local and Remote IP Traffic Capturing 4.1.1 Description of RAN2913: Local and Remote IP Traffic Capturing Introduction to the feature RAN2913: Local and Remote IP Traffic Capturing feature allows the capture of ingress and egress IP traffic of the C-plane, U-plane, M-plane, or S-plane traffic for post analysis. It uses a Web interface for configuration and for capturing file retrieval. Through Web interface, it is possible to select layer 3 internal measurement points. In addition, the capture of the U-plane traffic can be excluded to maximize the capturing duration.
4.1.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature benefits the operator by reducing the operational expenditure (OPEX). It allows the operator to remotely capture the BTS traffic for faster troubleshooting and to avoid site visits to retrieve transport capture files, saving time, cost, and effort.
4.1.1.2
Requirements Software requirements The following table lists the software that is required for this feature.
Table 107
Software requirements
RAS release
Flexi Direct
IPA-RNC
mcRNC
OMS
Flexi BTS
Flexi Lite BTS
RU50 EP1
Support not required
Support not required
Support not required
Support not required
WN9.1
WL9.1
Flexi 10 BTS
NetAct
MSC
SGSN
MGW
UE
WN9.1
NetAct 8 EP2 (NetAct 15)
Support not required
Support not required
Support not required
Support not required
Hardware requirements This feature requires Flexi Multiradio System Module (FSMF) or Flexi Lite BTS WCDMA. • •
212
For Flexi Multiradio 10 BTS WCDMA, the RAN2262: Flexi Multiradio System Modules (FSMF) feature with or without Transport sub-module (FTIF) is required. For Flexi Lite BTS WCDMA, the RAN2157: Flexi Lite BTS 2100 feature is required.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
4.1.1.3
Transmission and transport features
Functional description The RAN2913: Local and Remote IP traffic Capturing feature allows the capturing of BTS backhaul interfaces' IP packet information at different capture points inside the traffic path of the BTS.
g
This feature specifies capturing on IP layer, therefore Layer 2 information and protocol, such as Ethernet headers, Ethernet slow protocols, or Address Resolution Protocol (ARP) are not captured. It extends the troubleshooting capabilities of the BTS by facilitating the capturing or the streaming of the BTS traffic via a BTS-local Ethernet interface. It can also save the captured information into a libpcap file for a remote-triggered upload to the Network Operation Center. For more information, see IP traffic capturing setup. Figure 17
IP traffic capturing setup NetAct Local Access
BTS RNC IPsec GW
Transport Network
IPsec GW
This feature uses a Web interface for configuration for a high reliability when selecting measurement point, configuring output port (on-site), or when initiating a file transfer. The streaming output is available only to a MAC entity in the same L2 broadcast domain as the selected BTS Ethernet interface. The Web interface provides increased robustness, being able to operate even in faulty conditions of the BTS, in which the remote connection to the Site Element Manager is not operative. Through Web interface, it is possible to select the Layer 3 internal measurement points. Additionally, the capture of the U-plane traffic can be excluded to maximize the capturing duration. Capturing of IP traffic is supported in two different ways: • •
Issue: 01F
Streaming of the captured IP packets to an on-site-connected laptop or storage device. Capturing into a libpcap file, which can be downloaded via local or remote connection. The libpcap file format is the main capture file format that is used in TcpDump/WinDump, Wireshark/TShark, snort, and many other networking tools.
DN09146788
213
Transmission and transport features
RU50 Feature Descriptions and Instructions
The feature allows the capturing of the BTS backhaul interfaces' IP packet information (ingress and egress IP traffic) at different capture points inside the traffic path of the BTS. The capture points are: •
•
Capture Point A: IP traffic to/from the BTS. At this capture point, the traffic is captured non-fragmented and IPsec decrypted (if in use). TLS-encrypted M-plane is still encrypted. If TLS is not in use, M-plane is contained unencrypted or decrypted (in case IPsec is in use). At this capture point, downlink traffic is not filtered by the system firewall while the uplink traffic has already passed it. Capture Point B: IP traffic to/from the BTS and Site Support Equipment (SSE) captured at the transport network interfaces. At this capture point, it is possible that the captured traffic is fragmented and encrypted (if in use).
At all of these capture points, the traffic is captured in both ingress and egress directions. Capturing at point A simplifies the troubleshooting since it allows accessing of the decrypted/unencrypted traffic. The capturing is independent of the used layer 2 protocol (for example Ethernet, IP/ML-PPP). At capture points A and B, the user-plane payload (such as data beyond the UE TCP/UDP headers, terminating and originating at the UE) of unencrypted or decrypted packets is completely stripped off from the captured packets. At capture point B, the encrypted part of packets ciphered with IPsec ("inner packet") are stripped off from the captured packets and the IP header of the "outer packet" up to the ESP header of the inner packet is captured. The ESP header is still captured to help in identifying IPsec customer issues. It is possible to completely exclude the capturing of end user plane packets (headers). All other packets of IP based protocols (for example ICMP, TWAMP) are always captured if IP traffic capturing is ongoing. At all capture points, the original IP packets (all the portion packet before the IP header is stripped off and before the capture point and the portion packet from the IP header onwards is preserved) are conveyed unmodified to their destination. Throughout a capturing session, capturing is possible at one of the capture points. Capturing at multiple capture points is not supported, see Capture points in BTS. Figure 18
Capture points in BTS
IP/MLPPP termination
A
Fragment Reassembly
IPsecGateway Function Fragment Reassembly
O&M Function
SSL/TLS
BaseStation
TDM Interfaces
B
Transport Ethernet Interface(s) OtherBaseStation Functions (BasebandRadio)
L2Switching Function IP LayerCapturePoints
Capturing mechanism summarizes the capturing mechanism, the provisioning of the local packet stream and the libpcap file creation and provisioning:
packettiming information Packetstream(ingressandegress)
The feature includes the capability to mirror traffic into a libpcap file and fetch the compressed and optionally password-protected file via remote connection. Alternatively, the traffic can be mirrored to the local management port (LMP) or a free transport Ethernet port. For all of these output options, mirroring of user plane is limited to the header information. The UE-level payload beyond the UE-level TCP/UDP headers is never captured. The mirroring of the user plane traffic can be enabled/disabled via the Web interface. The remote traffic capturing eases the activities of maintenance engineers and it avoids extra site visits to retrieve transport capture files, saving time, cost, and effort. For remote traffic capturing, the size of the file is fixed at 150MB before compression and 40MB for the compressed libpcap file. This fixed file size ensures that the data for a single UE (peak-throughput, IPv4, with header up to the UE TCP level, no payload bytes, and not more than 100Mbps) is captured in about 2.5 minutes. This feature specifies capturing on IP layer, therefore Layer 2 information and protocols (such as Ethernet header, Ethernet protocol and ARP) are not captured. The configured value of sensitive parameter like password is neither stored nor displayed. Optional encryption of compressed libpcap file enhances security. The local traffic capturing can collect BTS traffic up to several days to investigate unexpected BTS behavior, support bug-fixing and customer trials. This feature provides the means to collect the transport capture files as often as needed so that they can be included to the ticket, contributing to the reduction of the time spent in resolving tickets. The feature provides a robust and simple configuration interface to facilitate IP traffic capturing management even in faulty and congested situations. If only a single UE is connected to the BTS, this feature allows maintenance engineers to capture the transport IP traffic that is related to that single UE at a BTS in the field. It allows them to calculate the KPIs, prove correct BTS behavior, and evaluate actual network performance. It enables the remote analysis of faults and it contributes to a quicker solution of those faults.
Issue: 01F
DN09146788
215
Transmission and transport features
4.1.1.4
RU50 Feature Descriptions and Instructions
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 On Flexi Multiradio 10 HW, the output data rate of the local streaming of IP capturing data via the NE Local Management Port (LMP) is limited to Fast Ethernet since the LMP does not support Gigabit Ethernet. IP traffic capturing is competing with normal BTS services for the same resources so there might not be enough resources to concurrently run IP traffic capturing and normal BTS services. This could happen: • • •
if there is a lack of resources in the packet buffers, which prevent the copy operation of the captured packets in case of local streaming if there is a lack of allocated processing time for the capturing process if the data rate of streamed IP traffic capturing data exceeds the available data rate on the Local Ethernet Port
If one of these cases happens, the IP traffic capturing might drop capturing packets (that is, IP packets are not captured or streamed). The user is not notified about this.
Impact on system performance and capacity System performance IP traffic capturing is competing with normal BTS services for the same resources so there might not enough resources to concurrently run IP traffic capturing and normal BTS services. The following are the possible causes: • • •
if there is a lack of resources in the packet buffers, which prevents the copy operation of the captured packets when local streaming if there is a lack of allocated processing time for the capturing process if the data rate of the streamed IP traffic capturing exceeds the available data rate on the Local Ethernet Port
If one of the scenarios listed above happens, the IP traffic capturing might drop capturing packets (for example IP packets are not captured or streamed). The user is not notified about this. System capacity On Flexi Multiradio 10 HW, the output data rate of the local streaming of the IP capturing data via the NE Local Management Port is limited to Fast Ethernet since the Local Management Port does not support Gigabit Ethernet.
4.1.1.5
RAN2913: Local and Remote IP Traffic Capturing management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
216
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Transmission and transport features
Alarms Table 108
Related existing alarms
Fault ID
Fault name
Alarm ID
Alarm name
Meaning of the alarm
61641
IP Traffic Capturing Ongoing
7665
Base station Transmission Alarm
The base station is currently capturing IP traffic towards local port or into a file on the base station.
Measurements and counters There are no measurements and counters related to this feature.
Key performance indicators There are no key performance indicators related to this feature.
Parameters There are no parameters related to this feature.
4.1.1.6
Sales information Table 109
Sales information
BSW/ASW
SW component
License control in network element
BSW
RAN
Not defined
4.1.2 Activating RAN2913: Local and Remote IP Traffic Capturing Purpose There is no separate feature activation scenario for Local streaming of IP packet information. This is embedded in the operator scenario "Local streaming of IP packet information". Before you start BTS transport SW is running.
g
RAN2913: Local and Remote IP Traffic Capturing feature allocates memory once session started. This memory can only be unallocated by a system reset. The RAN2913: Local and Remote IP Traffics Capturing feature requires 192 MB of free system memory for the optimal operation of the local file capture mode. If the said amount of free memory is not available, the system automatically falls back to 50 MB memory usage profile, with proportionally reduced capture duration. In case the free system memory falls below that required for even the fallback memory usage profile, only the local file capture mode becomes unavailable, and only the streaming mode of IP traffic capture is available.
Issue: 01F
DN09146788
217
Transmission and transport features
1
Connect to the local BTS Web interface (use the Private Network IP address https://192.168.255.129/) or BTS Remote Web Interface (use the management plane IP address https://MP IP address/). Figure 20
218
RU50 Feature Descriptions and Instructions
Local BTS Web interface
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 21
Transmission and transport features
BTS Remote Web interface
2
Log in using your credentials.
3
Select the Capture point for IP traffic capturing.
4
Select whether the user plane can be included by enable or disable the Uplane capture.
5
Select the Capture Output either libpcap file or streaming as output option. Optionally, provide a password for libpcap file encryption.
Issue: 01F
DN09146788
219
Transmission and transport features
Figure 22
• •
6
RU50 Feature Descriptions and Instructions
Capture Output Option
Select streaming and chose the local management port(LMP) or a free transport Ethernet port (if available on the BTS) and write the MAC address. Select file as the ouput
Start the IP traffic capturing. • • •
The BTS deletes the content of the capturing history data structure. The BTS raises the IP traffic capturing alarm. The BTS starts the IP traffic capturing.
7
Log off from BTS Web interface.
8
(Optional) BTS stops IP traffic capturing after the 24-hour timeout has been reached.
Result The BTS captures the selected IP traffic into the ring buffer structure in random access memory (RAM).
4.1.3 Verifying RAN2913: Local and Remote IP Traffic Capturing Before you start Make sure that the BTS SW is running and the Activating an IP Traffic Capturing session to libpcap file is performed.
220
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Transmission and transport features
The maximum size of the compressed libpcap file is 40MB. The compression ratio achievable during compression of the capture buffer into the compressed libpcap file varies with the compressibility of the information contained within the packets contained within the capture buffer. Therefore, BTS cannot guarantee inclusion of all packets from the capture buffer into the compressed libpcap file.
1
Connect to the BTS Web interface.
2
Log in using your credentials.
3
Select GEN&DOWNLOAD_PCAP.
g
In case the “Generate and Download” operation fails due to lack of memory, the user should retry the operation by re-clicking GEN&DOWNLOAD_PCAP after some minutes. Result The BTS Web interface displays a warning that IP traffic capturing will be stopped. The BTS stops IP traffic capturing and generates the libpcap trace file from the capturing history data structure. 4
Refresh the status of the BTS Web interface.
5
Store the downloaded file in laptop or the server in the network operations center.
6
Log off from the BTS Web interface.
7
(Optional) The BTS stops the IP traffic capturing after the 24-hour timeout has been reached.
Result The IP traffic capturing file is downloaded from BTS and is available for offline analysis.
g
No trace file will be generated if the maintenance engineer stops the session or the BTS resets during the IP traffic capturing session.
4.1.4 Deactivating RAN2913: Local and Remote IP Traffic Capturing 4.1.4.1
Stopping an IP Traffic Capturing session Before you start Ensure that the IP traffic capturing session ongoing.
Issue: 01F
DN09146788
221
Transmission and transport features
RU50 Feature Descriptions and Instructions
1
Connect to the BTS Web interface.
2
Log in using your credentials.
3
Stop the IP Traffic capturing. The IP traffic capturing will stops if one of the following happens: • • •
4
The BTS stops streaming of the IP traffic capturing data to the local port. The BTS stops writing into the capturing history data structure but does not delete it. The BTS clears the IP traffic capturing alarm.
Log off from the BTS Web interface.
Result The active BTS IP traffic capturing is stopped.
4.1.5 Testing RAN2913: Local and Remote IP Traffic Capturing Purpose This is an example of the verification; do not use it for the feature as such in live network. The configuration and parameter settings described are only examples and they can vary in different networks.
4.1.5.1
Test case 1: Capture traffic in Streaming mode Purpose This test case verifies the function of capturing traffic in Streaming mode. Before you start Required test environment and settings: •
1 WBTS (operational) 1 laptop
1
Connect to the local BTS Web interface.
2
Log in using your credentials.
3
Select Capture point for IP traffic capturing.
•
Capture point A or B can be selected but only one point can be selected at a time.
222
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Transmission and transport features
4
Select whether user plane can be included by enable or disable Uplane capture.
5
Set the Capture Output to Streaming as output option.
6
Set the Streaming option to LMP. Select the available transport ethernet interfaces, such as FSM-EIF1, FSM-EIF2, or FTIF-EIF1 to EIF4.
7
Connect the laptop/PC to LMP.
8
Set the Destination MAC Addr. The destination MAC address is the laptop MAC address.
9
Start wireshark capturing.
10 Click Start to start IP capturing. 11 Check the alarm/s in the BTS Site Manager. 12 Click Stop to stop IP capturing. 13 Check the alarm/s in the BTS Site Manager. Expected outcome 1. 2. 3. 4.
Log on successfully. Every parameter can be selected correctly. BTS streaming traffic to the selected Ethernet port is available. The 61641 IP Traffic Capturing Ongoing alarm is raised in BTS Site Manager to remind that the feature is running. 5. Once the capturing is stopped, no new IP traffic is received in the selected Ethernet port and 61641 alarm is cleared.
4.1.5.2
Test case 2: Capture traffic in File mode Purpose This test case verifies the function of capturing traffic in File mode. Before you start Required test environment and settings: •
Issue: 01F
1 WBTS (operational)
DN09146788
223
Transmission and transport features
RU50 Feature Descriptions and Instructions
•
1 laptop
1
Connect to the local BTS Web interface.
2
Log in using your credentials.
3
Select Capture point for IP traffic capturing. Capture point A or B can be selected but only one point can be selected at one time.
4
Select whether the user plane can be included by enabling or disabling Uplane capture.
5
Set the Capture Output to File as output option.
6
Set the password in the Capture File Option.
7
Click Start to start IP capturing.
8
Check the alarm/s in the BTS Site Manager.
9
Click Stop to stop IP capturing.
10 Generate and download the file. Result •
•
The file is generated and dowloaded as expected with the file name format _. (12345_20130412T231130.zip/.pcap/.zip.enc). If the captured traffic exceeds 40Mb, the BTS will discard the oldest packets until it can fit the captured traffic into the 40Mb file size limit. Some of the captured packets will be dropped during file generation and the generated file name should append "truncated". The file is generated and downloaded with the file name format __truncated..
11 Check the alarm/s in the BTS Site Manager. Expected outcome 1. Log on successfully. 2. Every parameter can be selected correctly. 3. IP traffics are successfully captured.
224
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Transmission and transport features
4. The 61641 IP Traffic Capturing Ongoing alarm is raised in the BTS Site Manager to remind that the RAN2913: Local and Remote IP Traffic Capturing feature is running. 5. Once the capturing is stopped, the 61641 alarm is cleared.
4.1.5.3
Test case 3: Capture traffic in different monitoring point Purpose This test case verifies the function of capturing traffic in different monitoring point. Before you start Required test environment and settings: •
1 WBTS (operational) 1 laptop
1
Connect to the local BTS Web interface.
2
Log in using your credentials.
3
Set the Capture point to B.
4
Set Uplane capture to Enable.
5
Set the Capture Output to Streaming as output option.
6
Set the Streaming option to LMP.
•
Select the available transport Ethernet interfaces, such as FSM-EIF1, FSM-EIF2 or FTIF-EIF1 to EIF4. 7
Connect the laptop/PC to LMP.
8
Set the Destination MAC Addr. The destination MAC address is the laptop MAC address.
Issue: 01F
DN09146788
225
Transmission and transport features
9
RU50 Feature Descriptions and Instructions
Start wireshark capturing.
10 Click Start to start IP capturing. 11 Check the alarm/s in the BTS Site Manager. 12 Check the traffics on every plane including ICMP, TWAMP, and BFD traffics. Result All related packets are all streamed to the LMP port. 13 Send large-sized ICMP packets with more than 1500 bytes to the BTS via DCN. Result The first fragment packets are captured and the second fragment packet are not captured. 14 Configure and enable IPsec on WBTS. Result IKE and IPsec traffics are captured but only includes the outer and ESP headers. 15 Click Stop to stop IP capturing at capture point B. Result Once the IP traffic capturing is stopped, no new IP packets is streamed at the LMP port. 16 Check the alarm/s in the BTS Site Manager. 17 Start IP traffic capturing at point A. 18 Click Start to start IP capturing. Result Captured IP packets are streamed at the LMP port and the payload is visible. 19 Check the alarm/s in the BTS Site Manager. 20 Click Stop to stop IP capturing at capture point A. 21 Check the alarm/s in the BTS Site Manager. Result
226
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Transmission and transport features
The 61641 alarm is cleared. Expected outcome 1. Log on successfully. 2. Every parameter can be selected correctly. 3. The 61641 IP Traffic Capturing Ongoing alarm is raised in the BTS Site Manager to remind that the feature is running. 4. Once the capturing is stopped, no new IP traffic is received in the selected Ethernet port and 61641 alarm is cleared.
4.2 RAN2243: Performance Monitoring Based on ETH Service OAM 4.2.1 Description of RAN2243: Performance Monitoring Based on ETH Service OAM Introduction to the feature This feature enhances the RAN1880: Ethernet OAM in BTS feature to provide performance monitoring functionality using Ethernet Service OAM frames. Performance monitoring according to the ITU-T Y.1731 provides Ethernet performance measurements between Maintenance End Points (MEPs) that are placed at the edges of each maintenance domain. The performance monitoring feature supports the Frame Loss and Frame Delay Measurements. The Frame Delay Measurements are shown with maximum, minimum and average data provided through the Two-way Frame Delay Measurement whereas the One-way Frame Delay Variation data is provided through the One-way Frame Delay Variation Measurement.
4.2.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature provides the performance monitoring functionality that permits to perform the performance measurements between the MEPs of the same grade of hierarchy. Different grades of hierarchy monitor different Ethernet network segments to find the problems more efficiently.
4.2.1.2
Requirements Software requirements Table 110: Software requirements lists software required for this feature.
Issue: 01F
DN09146788
227
Transmission and transport features
RU50 Feature Descriptions and Instructions
RAS
Flexi Direct
IPA-RNC
RU50
Not planned
Support not Support not Not planned required required
Table 110
mcRNC
Flexi Direct RNC OMS
Flexi BTS
OMS3.01)
WN9.0
OMS3.12)
Software requirements
Flexi Lite Flexi 10 BTS BTS
NetAct
WL9.1
NetAct 8 EP11) Support not Support not Support not Support not required required required required NetAct 8 EP2 (NetAct 15)2)
WN9.1
MSC
SGSN
MGW
UE
1) RU50 2) RU50 EP1
Hardware requirements This feature requires one of the following Flexi Multiradio BTS Transport Sub-Modules: • • • • •
This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF or Flexi Lite BTS WCDMA.
4.2.1.3
Functional description This feature enhances the RAN1880: Ethernet OAM in BTS feature to provide performance monitoring (PM) functionality using Ethernet Service OAM frames. The Ethernet OAM performance monitoring functions are defined by ITU-T Y.1731 standard. The ITU-T Y.1731 standard sets up an L2 network on hierarchy, which conforms maintenance domains. Different maintenance domains are assigned to the customer, service providers or operators. The edges of each domain are Maintenance End Points (MEPs). The ports within the domains can be Maintenance Intermediate Points (MIPs). The maintenance hierarchy permits to monitor different segments of the Ethernet network, which are under the responsibility of different hierarchy departments. The segmentation of maintenance domains simplifies finding the problems on the L2 Ethernet network. When the performance monitoring feature is not activated, the L2 (Ethernet) performance monitoring functions are not possible to be performed.
228
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 23
Transmission and transport features
Performance monitoring using Ethernet Service OAM frames EthPM EthPM EthPM
MEP
MEP
MEP
MEP
BTS
Eth
Ethernet
Ethernet
The performance monitoring functions supported by the performance monitoring feature are Frame Loss and Frame Delay Measurement. There are different modes of each measurement: •
This feature provides also configurable thresholds for triggering alarms for Frame Loss Measurement and Frame Delay/Delay Variation Measurement. The thresholds are configurable per measurement session. The Frame Loss Measurements are obtained by means of counters for received and transmitted data frames between a pair of MEPs. These counters are provided by the performance monitoring feature. The Frame Loss Measurement can be calculated for each direction. Far-end and near-end Frame Loss Measurements are supported. The BTS supports both kinds of Frame Loss Measurements. The operator configures the measurement nature. The Frame Delay Measurements are shown with maximum, minimum and average data provided through the Two-way Frame Delay Measurement whereas the One-way Frame Delay Variation data is provided through the One-way Frame Delay Variation Measurement. The One-way Frame Delay Variation is counted as the maximum variation gained between one-way delays of two consecutive DMM/DMR PDUs during the measurement. Note that the variations between any two one-way delays during the measurement can be greater than the obtained maximum variation but these variations are distorted through the inevitable clock drift between the measurement MEPs. The Frame Delay Measurements are impacted through the inevitable clock drift between the measurement MEPs cause the MEPs cannot be assumed to be frequency synchronized. The inevitable clock drift between the measurement MEPs depends on the Delay measurement transmission interval.
Issue: 01F
DN09146788
229
Transmission and transport features
RU50 Feature Descriptions and Instructions
The FE and GE devices are needed to obtain the frequency accuracy within +/- 100 ppm. Note that when the operated BTS is assumed to be frequency synchronized and performs the measurement against the certain switch, the worst case clock drifts of 100 ppm are expected. The obtained worst case clock drifts are dependent on the Delay measurement transmission intervals: •
Delay measurement transmission interval: 100 ms –
•
Delay measurement transmission interval: 1 s –
•
worst case clock drift (100 ppm): 1 ms
Delay measurement transmission interval: 1 min –
•
worst case clock drift (100 ppm): 100 us
Delay measurement transmission interval: 10 s –
•
worst case clock drift (100 ppm): 10 us
worst case clock drift (100 ppm): 6 ms
Delay measurement transmission interval: 10 min –
worst case clock drift (100 ppm): 60 ms
The usage of greater intervals does not make sense when the clock drift dominates the One-way Frame Delay Variation. The recommendation is to configure the Delay measurement transmission interval for the manner that the gained delays are much greater than the expected clock drift.
g 4.2.1.4
Note that mesh, chain, tree, and circle topology should have point-to-point Ethernet connections between MEPs to perform accurate Frame Loss Measurement, whereas there are no similar limitations for Frame Delay/Delay Variation Measurement.
System impact Interdependencies between features This feature does not need a separate license. This feature needs the licenses of the features: • •
RAN1880: Ethernet OAM in BTS RAN1900: IP Transport Network Measurement
This feature needs the activation of the feature: •
RAN1880: Ethernet OAM in BTS
Impact on interfaces This feature has no impact on interfaces.
Impact on network and network element management tools This feature has an impact on network element management tools as beneath: •
230
NetAct supports the new alarms/faults.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Transmission and transport features
NetAct supports the new counters. NetAct supports the new parameters.
• •
Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath: The Service OAM can consume significant amount of bandwidth, particularly when pro-active functions (ETH-CC) are activated simultaneously and using high transmission rates. However, the Service OAM performance monitoring functions are not meant to use high transmission rates. The feature standard recommends 10 fps. The usage of these functions must be confined then. The capacity demand for Service OAM performance monitoring functions is usually not significant. With default settings, each ETH-CCM measurement consumes less than 1 kbps, whereas ETH-LM and ETH-DM measurements - less than 0.1 kbps. The default measurement transmission intervals are:
•
•
ETH-CCM measurement - 1 s ETH-LM measurement - 10 s ETH-DM measurement - 1 s
– – –
At maximum (not recommended), ETH-CCM Frame Loss Measurement can consume 312 kbps at Ethernet layer when 3.33 ms interval is configured.
•
4.2.1.5
RAN2243: Performance Monitoring Based on ETH Service OAM management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Faults Table 111: New faults lists faults and reported alarms introduced with this feature.
g
Table 111
New faults
Fault ID
Fault name
Reported alarms
61635
Frame loss threshold exceeded on mac $m
7665 BASE STATION TRANSMISSION ALARM
61636
Two way delay threshold exceeded on mac $m
7665 BASE STATION TRANSMISSION ALARM
61637
OneWay delay variation threshold exceed on mac $m
7665 BASE STATION TRANSMISSION ALARM
The performance monitoring faults are presented as alarms at: • •
Issue: 01F
OMS Fault Management NetAct Monitor
DN09146788
231
Transmission and transport features
RU50 Feature Descriptions and Instructions
Measurements and counters Table 112: New counters lists counters introduced with this feature. Table 112
New counters
Counter ID
Counter name
Measurement
M5141C0
soamIngressFramesLost
M5141 (Frame Loss)
M5141C1
soamIngressTotalFrames
M5141 (Frame Loss)
M5141C2
soamNearEndFrameLossRatio
M5141 (Frame Loss)
M5141C3
soamEgressFramesLost
M5141 (Frame Loss)
M5141C4
soamEgressTotalFrames
M5141 (Frame Loss)
M5141C5
soamFarEndFrameLossRatio
M5141 (Frame Loss)
M5142C0
soamTwowayAverageDelay
M5142 (Frame Delay)
M5142C1
soamTwowayMaxDelay
M5142 (Frame Delay)
M5142C2
soamTwowayMinDelay
M5142 (Frame Delay)
M5143C0
soamOnewayNearEnDelayVariation
M5143 (Frame Delay)
M5143C1
soamOnewayFarEndDelayVariation
M5143 (Frame Delay)
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table 113: New parameters lists parameters introduced with this feature. Table 113
232
New parameters
Full name
Abbreviated name
Managed object
Enable service OAM performance monitoring
enableSoamPm
IPNO
Flag for enabling/disabling SOAM frame loss measurement
enableSoamFrameLossMeas
OAMFLM
MAC address of the frame loss measurement remote MEP
macAddr
OAMFLM
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 113
Transmission and transport features
New parameters (Cont.)
Full name
Abbreviated name
Managed object
Service OAM frame loss alarm threshold
soamFrameLossAlarmThres
OAMFLM
Service OAM frame loss measurement interval
soamFrameLossMeasInt
OAMFLM
Service OAM Frame loss Measurement Mode
soamFrameLossMeasMode
OAMFLM
Enable service OAM delay measurement
enableSoamDelayMeasure
OAMDM
MAC address of the delay measurement remote MEP
macAddr
OAMDM
Service OAM oneway delay variation 15m alarm threshold
soamDelayAlarmThresOneway
OAMDM
Service OAM two-way delay 1 min alarm threshold
soamDelayAlarmThresTwoway
OAMDM
Service oam delay measurement PDU length
soamDmmPduSize
OAMDM
Service OAM frame delay measurement interval
soamFrameDelayMeasInt
OAMDM
Commands There are no commands related to this feature.
4.2.1.6
Sales information Table 114
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
TRS LK
4.2.2 Activating RAN2243: Performance Monitoring Based on ETH Service OAM Purpose The purpose of this procedure is to activate the performance monitoring (PM) feature.
Issue: 01F
DN09146788
233
Transmission and transport features
RU50 Feature Descriptions and Instructions
Before you start The activating procedure does not cause downtime. The activating procedure can be performed at any time of the day. The activating procedure does not need a separate license. The activating procedure needs the licenses of the features: • •
RAN1880: Ethernet OAM in BTS RAN1900: IP Transport Network Measurement
The activating procedure needs the activation of the feature: •
RAN1880: Ethernet OAM in BTS
The activating procedure to activate the Ethernet Service OAM PM on the BTS needs: • •
BTS Site Manager NetAct Configuration Management software
The activating procedure to configure the PM measurement sessions on the BTS needs: • •
BTS Site Manager NetAct Configuration Management software
The activating procedure to start the measurements at OMS needs: • •
RNW Measurement Management NetAct Administration of Measurements
The activating procedure to monitor the PM measurement sessions data needs: • •
BTS Site Manager NetAct Performance Manager
The activating procedure consists of three procedures: • • •
4.2.2.1
activating Ethernet Service OAM PM activating Frame Loss Measurement session activating Frame Delay Measurement session
Activating Ethernet Service OAM PM Purpose This procedure is used to activate the Ethernet Service OAM PM on the BTS. Before you start 1. Determine the Maintenance Domain and Maintenance Association. 2. Determine the Maintenance End Point(s) within given Maintenance Association. 3. Determine the Ethernet Service OAM performance monitoring switch.
234
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Transmission and transport features
Note that when you do not meet the preconditions, you must know that: • • •
1
g
The Ethernet Service OAM PM features are not operable but can be set. The PM messages from the remote MEPs are discarded. The PM measurements are not generated.
Open the BTS Site Manager. The NetAct Configuration Management software can be used alternatively.
2
Turn on the Ethernet Service OAM PM feature on the BTS. Perform the actions on the BTS: a) b) c) d)
g
Open the TRS Hardware from the View bar. Open the Ethernet Service OAM menu. Mark the Ethernet Service OAM in use checkbox. Mark the Ethernet Service OAM performance monitoring in use checkbox.
Note that to complete the step, you must send the configuration to the BTS.
Expected outcome The Ethernet Service OAM PM is activated successfully on the BTS. The Ethernet Service OAM PM statistics are cleared. The BTS only answers to the incoming PM messages from the remote MEPs. The PM measurement sessions are supported on the BTS: Frame Loss Measurement session Frame Delay Measurement session
• •
The PM measurement sessions with active status are automatically restarted on the BTS.
g g
The PM measurement sessions have to be further activated separately on the BTS. The proper measurements have to be started at OMS. The measurements are: • • •
g
Issue: 01F
M5141 - Soam Frame Loss statistics M5142 - Soam Two Way Delay Statistics M5143 - Soam One Way Delay Variation Statistics
The operator can set the BTS thresholds for triggering alarms. The PM thresholds are set on the BTS for each measurement separately.
DN09146788
235
Transmission and transport features
4.2.2.2
RU50 Feature Descriptions and Instructions
Activating Frame Loss Measurement session Purpose This procedure is used to activate the Frame Loss Measurement session on the BTS. This procedure consists also of the step to start the associated measurement at OMS. Before you start This procedure needs the activation of the Ethernet Service OAM PM on the BTS. The Frame Loss statistics are fifteen-minutes statistics.
g
The Frame Loss Measurement session at single-ended mode cannot be activated when: The Maintenance Association has more than one remote MEP. There are measurements with the same mode under the same MEP. The activation causes the total ingress of Service OAM frames to surpass 1000 fps.
• • •
g
The Frame Loss Measurement session at dual-ended mode cannot be activated when: The Maintenance Association has zero or more than one remote MEP. The Maintenance Association does not have the ETH-CC activated. There are measurements with the same mode under the same MEP.
• • •
1
Open the BTS Site Manager.
g
The NetAct Configuration Management software can be used alternatively.
2
Turn on the Frame Loss Measurement session on the BTS. Perform the actions on the BTS: a) b) c) d)
3
Open the TRS Hardware from the View bar. Open the Ethernet Service OAM menu. Open the New drop-down menu and create Frame loss measurement session. Mark the Frame loss measurement in use checkbox.
Determine the Frame Loss Measurement session parameters. The Frame Loss Measurement session needs configuration of the parameters: • • • • •
g 236
MAC address of remote MEP Frame loss measurement mode Frame loss transmission interval (for single-ended measurements) Frame loss alarm ratio threshold MEP with hereditary VLAN ID and PCP from Maintenance Association Note that to complete the step, you must send the configuration to the BTS.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
4
Transmission and transport features
Monitor the measurement session using the BTS Site Manager. Expected outcome The Frame Loss Measurement session is activated on the BTS. When Frame Loss Measurement session is activated on the BTS then: The BTS purges the current Frame Loss statistics. The BTS starts to measure the Frame Loss statistics again. The BTS measures the Frame Loss Ratio every fifteen minutes. The BTS sends the measurement data to the OMS every hour. The BTS sends the CCM messages to the remote MEP (dual-ended mode). The BTS sends the LMM messages to the remote MEP (single-ended mode). The LMR messages are transmitted from the remote MEP (single-ended mode). The Frame Loss alarm occurs when the threshold is surpassed.
• • • • • • • •
5
g
Start the Soam Frame Loss statistics measurement (M5141) at OMS. This step must be performed using: • •
g
RNW Measurement Management NetAct Administration of Measurements
The OMS does not store the measurement data to database. The OMS transfers the measurement data from the BTS to the NetAct. Expected outcome The Soam Frame Loss statistics measurement is started at OMS. The OMS sends the measurement data to the NetAct ten minutes after every hour. 6
g
Monitor the measurement session using the NetAct Performance Manager. This step must be performed after the proper time. The BTS sends the measurement data to the OMS every hour. The measurement data comprises four fifteen-minutes statistics. The OMS sends the measurement data to the NetAct ten minutes after. The measurement data of each fifteen minutes can be monitored then using: •
NetAct Performance Manager
Expected outcome The Frame Loss Measurement session is activated on the BTS.
4.2.2.3
Activating Frame Delay Measurement session Purpose This procedure is used to activate the Frame Delay Measurement session on the BTS.
Issue: 01F
DN09146788
237
Transmission and transport features
RU50 Feature Descriptions and Instructions
This procedure consists also of the steps to start the associated measurements at OMS. Before you start This procedure needs the activation of the Ethernet Service OAM PM on the BTS. The One-way Frame Delay Variation statistics are fifteen-minutes statistics. The Two-way Frame Delay statistics are one-minute and fifteen-minutes statistics.
g
The Frame Delay Measurement session cannot be activated when: There are 80 Frame Delay Measurement sessions already created. The activation causes the total ingress of Service OAM frames to surpass 1000 fps. The Frame Delay Measurement session with the same remote MAC is already activated.
• • •
1
Open the BTS Site Manager.
g
The NetAct Configuration Management software can be used alternatively.
2
Turn on the Frame Delay Measurement session on the BTS. Perform the actions on the BTS: a) b) c) d)
3
Open the TRS Hardware from the View bar. Open the Ethernet Service OAM menu. Open the New drop-down menu and create Delay measurement session. Mark the Delay measurement in use checkbox.
Determine the Frame Delay Measurement session parameters. The Frame Delay Measurement session needs configuration of the parameters: • • • • • •
g
MAC address of remote MEP Delay measurement transmission interval Delay measurement message PDU size One-way delay variation 15 min alarm threshold Two-way delay measurement 1 min alarm threshold MEP with hereditary VLAN ID and PCP from Maintenance Association Note that to complete the step, you must send the configuration to the BTS.
4
Monitor the measurement session using the BTS Site Manager. Expected outcome The Frame Delay Measurement session is activated on the BTS. When Frame Delay Measurement session is activated on the BTS then: • •
238
The BTS purges the current Frame Delay statistics. The BTS starts to measure the Frame Delay statistics again.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
The BTS sends the measurement data to the OMS every hour. The BTS sends the DMM messages to the remote MEP. The DMR messages are transmitted from the remote MEP. The Frame Delay alarms occur when the thresholds are surpassed.
• • • •
5
g
Transmission and transport features
Start the Soam Two Way Delay Statistics measurement (M5142) at OMS. This step must be performed using: • •
g
RNW Measurement Management NetAct Administration of Measurements
The OMS does not store the measurement data to database. The OMS transfers the measurement data from the BTS to the NetAct. Expected outcome The Soam Two Way Delay Statistics measurement is started at OMS. The OMS sends the measurement data to the NetAct ten minutes after every hour. 6
g
Start the Soam One Way Delay Variation Statistics measurement (M5143) at OMS. This step must be performed using: • •
g
RNW Measurement Management NetAct Administration of Measurements
The OMS does not store the measurement data to database. The OMS transfers the measurement data from the BTS to the NetAct. Expected outcome The Soam One Way Delay Variation Statistics measurement is started at OMS. The OMS sends the measurement data to the NetAct ten minutes after every hour. 7
g
Monitor the measurement session using the NetAct Performance Manager. This step must be performed after the proper time. The BTS sends the measurement data to the OMS every hour. The measurement data comprises four fifteen-minutes statistics. The OMS sends the measurement data to the NetAct ten minutes after. The measurement data of each fifteen minutes can be monitored then using: •
g Issue: 01F
NetAct Performance Manager
NetAct does not support one-minute statistics.
DN09146788
239
Transmission and transport features
RU50 Feature Descriptions and Instructions
Expected outcome The Frame Delay Measurement session is activated on the BTS.
4.2.3 Verifying RAN2243: Performance Monitoring Based on ETH Service OAM Purpose The purpose of this procedure is to verify activation of PM feature. Before you start The verifying procedure does not cause downtime. The verifying procedure can be performed at any time of the day. The verifying procedure needs the PM measurement sessions activation on the BTS: • •
Frame Loss Measurement session Frame Delay Measurement session
The verifying procedure to start the measurements at OMS needs: • •
RNW Measurement Management NetAct Administration of Measurements
The verifying procedure to monitor the PM measurement sessions data needs: • •
BTS Site Manager NetAct Performance Manager
The verifying procedure to monitor the PM alarms needs: • • •
BTS Site Manager NetAct Monitor OMS Fault Management
The Frame Loss statistics are fifteen-minutes statistics. The One-way Frame Delay Variation statistics are fifteen-minutes statistics. The Two-way Frame Delay statistics are one-minute and fifteen-minutes statistics.
1
g
Open the RNW Measurement Management. The NetAct Administration of Measurements application can be used alternatively.
2
Start the proper measurements at OMS. The Frame Loss Measurement is M5141 measurement. The Two-way Frame Delay Measurement is M5142 measurement. The One-way Frame Delay Variation Measurement is M5143 measurement.
240
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Transmission and transport features
The OMS does not store the measurement data to database. The OMS transfers the measurement data from the BTS to the NetAct. 3
Open the BTS Site Manager.
4
After one minute verify that the proper PM counters are greater than zero.
g g
This step must be performed one minute after the measurement start. The PM counters are non-zero when non-SOAM frames are transmitted. When performing the current step, the proper PM counters are: Two-way Frame Delay Measurement counters:
The Frame Delay counters must be always greater than zero at the present moment. The measurement data of each minute can be monitored only for: •
Two-way Frame Delay Measurement
The measurement data of each minute can be monitored only using: •
BTS Site Manager
Expected outcome The Two-way Frame Delay counters are greater than zero.
g
The proper PM counters are presented during the one minute of measurement. The proper PM counters are updated after the completion of one minute of measurement.
5
Verify that the proper alarm is raised when the threshold is surpassed.
g
This step must be performed one minute after the measurement start. When performing the current step, the proper alarm occurs for: •
g
Issue: 01F
Two-way Frame Delay Measurement The proper alarms are presented as faults at the BTS Site Manager.
DN09146788
241
Transmission and transport features
g
RU50 Feature Descriptions and Instructions
The proper alarms are reported from the BTS to the OMS/NetAct promptly. The proper alarms can be monitored also using: NetAct Monitor OMS Fault Management
• •
Expected outcome The proper alarm is raised when the threshold is surpassed.
g
The proper alarm does not occur when the threshold is set to zero. The proper alarm occurs only when the threshold is surpassed after the one minute of measurement. Further information The proper alarms are canceled when the thresholds are not surpassed after the next one minute of measurement for: Two-way Frame Delay Measurement
•
6
After fifteen minutes verify that the proper PM counters are greater than zero.
g g
This step must be performed fifteen minutes after the measurement start. The PM counters are non-zero when non-SOAM frames are transmitted. When performing the current step, the proper PM counters are: Frame Loss Measurement counters:
The Two-way Frame Delay Measurement counters can be verified again. The Frame Loss counters are non-zero when non-SOAM frames are lost. The Frame Delay counters must be always greater than zero at the present moment. The measurement data of each fifteen minutes can be monitored using: •
BTS Site Manager
Expected outcome
242
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Transmission and transport features
The One-way Frame Delay Variation counters are greater than zero. The Two-way Frame Delay counters are greater than zero. The Frame Loss counters are greater than zero.
g
The proper PM counters are presented during the fifteen minutes of measurement. The proper PM counters are updated after the completion of fifteen minutes of measurement. 7
Verify that the proper alarm is raised when the threshold is surpassed.
g
This step must be performed fifteen minutes after the measurement start. When performing the current step, the proper alarm occurs for: One-way Frame Delay Variation Measurement Frame Loss Measurement
• •
g g
The proper alarms are presented as faults at the BTS Site Manager. The proper alarms are reported from the BTS to the OMS/NetAct promptly. The proper alarms can be monitored also using: • •
NetAct Monitor OMS Fault Management
Expected outcome The proper alarm is raised when the threshold is surpassed.
g
The proper alarm does not occur when the threshold is set to zero. The proper alarm occurs only when the threshold is surpassed after the fifteen minutes of measurement. Further information The proper alarms are canceled when the thresholds are not surpassed after the next fifteen minutes of measurement for: One-way Frame Delay Variation Measurement Frame Loss Measurement
• •
8
g
Monitor the measurement session using the NetAct Performance Manager. This step must be performed after the proper time. The BTS sends the measurement data to the OMS every hour. The measurement data comprises four fifteen-minutes statistics. The OMS sends the measurement data to the NetAct ten minutes after. The measurement data of each fifteen minutes can be monitored then using: •
Issue: 01F
NetAct Performance Manager
DN09146788
243
Transmission and transport features
g
RU50 Feature Descriptions and Instructions
NetAct does not support one-minute statistics. 9
Verify that the proper PM counters are greater than zero. Expected outcome The One-way Frame Delay Variation counters are greater than zero. The Two-way Frame Delay counters are greater than zero. The Frame Loss counters are greater than zero.
Expected outcome The Frame Loss/Delay Measurement sessions are activated successfully.
4.2.4 Deactivating RAN2243: Performance Monitoring Based on ETH Service OAM Purpose The purpose of this procedure is to deactivate the performance monitoring (PM) feature. Before you start The deactivating procedure does not cause downtime. The deactivating procedure can be performed at any time of the day. The deactivating procedure needs that the feature is activated successfully. The deactivating procedure to deactivate the Ethernet Service OAM PM (BTS) needs: • •
BTS Site Manager NetAct Configuration Management software
The deactivating procedure to deactivate the PM measurement sessions (BTS) needs: • •
BTS Site Manager NetAct Configuration Management software
The deactivating procedure to stop the measurements at OMS needs: • •
RNW Measurement Management NetAct Administration of Measurements
The deactivating procedure consists of three procedures: • • •
4.2.4.1
deactivating Ethernet Service OAM PM deactivating Frame Loss Measurement session deactivating Frame Delay Measurement session
Deactivating Ethernet Service OAM PM Purpose This procedure is used to deactivate the Ethernet Service OAM PM on the BTS.
244
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Transmission and transport features
Before you start This procedure needs the activation of the Ethernet Service OAM PM on the BTS. This procedure can be performed by deleting the license of one of the features: RAN1880: Ethernet OAM in BTS RAN1900: IP Transport Network Measurement
• •
g
The Ethernet Service OAM PM features are stopped after one of the actions: • •
1
g
The Ethernet Service OAM PM is deactivated. The Ethernet Service OAM is deactivated.
Open the BTS Site Manager. The NetAct Configuration Management software can be used alternatively.
2
Turn off the Ethernet Service OAM PM feature on the BTS. Perform the actions on the BTS: a) Open the TRS Hardware from the View bar. b) Open the Ethernet Service OAM menu. c) Unmark the Ethernet Service OAM performance monitoring in use checkbox.
g
Note that to complete the step, you must send the configuration to the BTS.
Expected outcome The Ethernet Service OAM PM is deactivated successfully on the BTS. The BTS discards the incoming PM messages from the remote MEPs. The PM measurement sessions are not supported on the BTS. The PM measurement sessions are stopped on the BTS and PM alarms are canceled. The PM measurement sessions activation on the BTS does not have any effect. The Frame Loss/Delay statistics are not cleared but they are not further updated.
g
The proper measurements have to be stopped at OMS. The measurements are: • • •
g
Issue: 01F
M5141 - Soam Frame Loss statistics M5142 - Soam Two Way Delay Statistics M5143 - Soam One Way Delay Variation Statistics
The operator can also deactivate a single PM measurement session. The operation can be performed without a complete deactivation of PM feature.
DN09146788
245
Transmission and transport features
4.2.4.2
RU50 Feature Descriptions and Instructions
Deactivating Frame Loss Measurement session Purpose This procedure is used to deactivate the Frame Loss Measurement session on the BTS. This procedure consists also of the step to stop the associated measurement at OMS. Before you start This procedure needs the activation of the Frame Loss Measurement session on the BTS. This procedure needs the activation of the associated measurement at OMS. This procedure can be performed by deleting the license of one of the features: RAN1880: Ethernet OAM in BTS RAN1900: IP Transport Network Measurement
• •
g
The Frame Loss Measurement session (BTS) stops after one of the actions: The Frame Loss Measurement session is deactivated. The Ethernet Service OAM PM is deactivated. The Ethernet Service OAM is deactivated.
• • •
1
Open the BTS Site Manager.
g
The NetAct Configuration Management software can be used alternatively.
2
Turn off the Frame Loss Measurement session on the BTS. Perform the actions on the BTS: a) Open the TRS Hardware from the View bar. b) Open the Ethernet Service OAM menu. c) Perform one of the actions: • •
g
Unmark the Frame loss measurement in use checkbox. Delete the selected measurement session using Delete button.
Note that to complete the step, you must send the configuration to the BTS. Expected outcome The Frame Loss Measurement session is stopped on the BTS. When Frame Loss Measurement session is stopped on the BTS then: • • • • •
246
The BTS stops measuring the Frame Loss statistics. The BTS stops sending the Frame Loss Measurement data to the OMS. The BTS discards the incoming Frame Loss messages from the remote MEPs. The Frame Loss messages are not transmitted anymore. The Frame Loss alarm is canceled.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
The Frame Loss statistics are not cleared but they are not further updated.
•
3
g
Transmission and transport features
Stop the Soam Frame Loss statistics measurement (M5141) at OMS. This step must be performed using: • •
RNW Measurement Management NetAct Administration of Measurements
Expected outcome The Soam Frame Loss statistics measurement is stopped at OMS. The OMS stops sending the Frame Loss Measurement data to the NetAct.
4.2.4.3
Deactivating Frame Delay Measurement session Purpose This procedure is used to deactivate the Frame Delay Measurement session on the BTS. The procedure consists also of the steps to stop the associated measurements at OMS. Before you start This procedure needs the activation of the Frame Delay Measurement session on the BTS. This procedure needs the activation of the associated measurements at OMS. This procedure can be performed by deleting the license of one of the features: RAN1880: Ethernet OAM in BTS RAN1900: IP Transport Network Measurement
• •
g
The Frame Delay Measurement session (BTS) stops after one of the actions: • • •
1
g
The Frame Delay Measurement session is deactivated. The Ethernet Service OAM PM is deactivated. The Ethernet Service OAM is deactivated.
Open the BTS Site Manager. The NetAct Configuration Management software can be used alternatively.
2
Turn off the Frame Delay Measurement session on the BTS. Perform the actions on the BTS: a) Open the TRS Hardware from the View bar. b) Open the Ethernet Service OAM menu. c) Perform one of the actions:
Issue: 01F
DN09146788
247
Transmission and transport features
Unmark the Delay measurement in use checkbox. Delete the selected measurement session using Delete button.
• •
g
RU50 Feature Descriptions and Instructions
Note that to complete the step, you must send the configuration to the BTS. Expected outcome The Frame Delay Measurement session is stopped on the BTS. When Frame Delay Measurement session is stopped on the BTS then: The BTS stops measuring the Frame Delay statistics. The BTS stops sending the Frame Delay Measurement data to the OMS. The BTS discards the incoming Frame Delay messages from the remote MEPs. The Frame Delay messages are not transmitted anymore. The Frame Delay alarms are canceled. The Frame Delay statistics are not cleared but they are not further updated.
• • • • • •
3
g
Stop the Soam Two Way Delay Statistics measurement (M5142) at OMS. This step must be performed using: • •
RNW Measurement Management NetAct Administration of Measurements
Expected outcome The Soam Two Way Delay Statistics measurement is stopped at OMS. The OMS stops sending the Two-way Frame Delay Measurement data to the NetAct. 4
g
Stop the Soam One Way Delay Variation Statistics measurement (M5143) at OMS. This step must be performed using: • •
RNW Measurement Management NetAct Administration of Measurements
Expected outcome The Soam One Way Delay Variation Statistics measurement is stopped at OMS. The OMS stops sending the One-way Frame Delay Variation Measurement data to the NetAct.
4.2.5 Testing RAN2243: Performance Monitoring Based on ETH Service OAM Purpose
g
248
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.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Transmission and transport features
The purpose of this procedure is to verify activation and proper working of PM feature. Test environment • • •
Wiresharks connected to the network one Cisco L2 switch two BTSs
Before you start The testing procedure does not cause downtime. The testing procedure can be performed at any time of the day. The testing procedure does not need a separate license. The testing procedure needs the licenses of the features: • •
RAN1880: Ethernet OAM in BTS RAN1900: IP Transport Network Measurement
The testing procedure needs the activation of the feature: •
RAN1880: Ethernet OAM in BTS
The testing procedure to configure the PM measurement sessions on the BTS needs: • •
BTS Site Manager NetAct Configuration Management software
The testing procedure to start the measurements at OMS needs: • •
RNW Measurement Management NetAct Administration of Measurements
The testing procedure to monitor the PM measurement sessions data needs: • •
BTS Site Manager NetAct Performance Manager
The testing procedure to monitor the PM alarms needs: • • •
Issue: 01F
BTS Site Manager NetAct Monitor OMS Fault Management
DN09146788
249
Transmission and transport features
Figure 24
RU50 Feature Descriptions and Instructions
Proper network setup for test cases
CiscoL2switch
BTS1
EIF3
OperatorNetwork
BTS2
EIF 2
The testing procedure consists of three procedures: testing Frame Loss Measurement session using dual-ended mode testing Frame Loss Measurement session using single-ended mode testing Frame Delay Measurement session
• • •
4.2.5.1
Testing Frame Loss Measurement session using dual-ended mode Purpose This procedure verifies Frame Loss Measurement session at dual-ended mode. Before you start This procedure needs the activation of the Ethernet Service OAM PM on two BTSs. The Frame Loss statistics are fifteen-minutes statistics.
g
The Frame Loss Measurement session at dual-ended mode cannot be activated when: • • •
1
g
The Maintenance Association has zero or more than one remote MEP. The Maintenance Association does not have the ETH-CC activated. There are measurements with the same mode under the same MEP.
Open the BTS Site Manager. The NetAct Configuration Management software can be used alternatively.
2
Turn on the Frame Loss Measurement session on the BTS. Perform the actions on the BTS: a) b) c) d)
250
Open the TRS Hardware from the View bar. Open the Ethernet Service OAM menu. Open the New drop-down menu and create Frame loss measurement session. Mark the Frame loss measurement in use checkbox.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Transmission and transport features
The Frame Loss Measurement session can be turned on on two BTSs. The measurement data can be monitored then on two BTSs. 3
Determine the Frame Loss Measurement session parameters. The Frame Loss Measurement session parameters are configured as presented: •
BTS1 – – –
•
MAC address Frame loss measurement mode: Dual ended Frame loss alarm ratio threshold: 1.00%
BTS2
g
Determine when needed. – – –
g
MAC address Frame loss measurement mode: Dual ended Frame loss alarm ratio threshold: 1.00%
Note that to complete the step, you must send the configuration to the BTS.
4
Monitor the measurement session using the Wireshark.
g
The PM counters are non-zero when non-SOAM frames are transmitted. Expected outcome The CCM messages are sent out from the BTS. The Frame Loss counters from the CCM messages are greater than zero. 5
Monitor the measurement session using the BTS Site Manager. Expected outcome The Frame Loss Measurement session is activated on the BTS. When Frame Loss Measurement session is activated on the BTS then: • • • • •
Issue: 01F
The BTS purges the current Frame Loss statistics. The BTS starts to measure the Frame Loss statistics again. The BTS measures the Frame Loss Ratio every fifteen minutes. The BTS sends the measurement data to the OMS every hour. The Frame Loss alarm occurs when the threshold is surpassed.
DN09146788
251
Transmission and transport features
6
RU50 Feature Descriptions and Instructions
Start the Soam Frame Loss statistics measurement (M5141) at OMS.
g
This step must be performed using: RNW Measurement Management NetAct Administration of Measurements
• •
g
The OMS does not store the measurement data to database. The OMS transfers the measurement data from the BTS to the NetAct. Expected outcome The Soam Frame Loss statistics measurement is started at OMS. The OMS sends the measurement data to the NetAct ten minutes after every hour. 7
Break connection by disconnecting Ethernet cable from one of the devices.
g
The connection break generates lost frames. The connection break must be performed only for some time.
8
After fifteen minutes verify that the proper PM counters are greater than zero.
g g
This step must be performed fifteen minutes after the measurement start. The PM counters are non-zero when non-SOAM frames are transmitted. When performing the current step, the proper PM counters are: Frame Loss Measurement counters:
The Frame Loss counters are non-zero when non-SOAM frames are lost. The measurement data of each fifteen minutes can be monitored using: •
BTS Site Manager
Expected outcome The Frame Loss counters from the CCM messages are greater than zero.
252
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Transmission and transport features
The proper PM counters are presented during the fifteen minutes of measurement. The proper PM counters are updated after the completion of fifteen minutes of measurement. 9
Verify that the proper alarm is raised when the threshold is surpassed.
g
This step must be performed fifteen minutes after the measurement start. The proper statistics for Frame Loss Measurement: alarm:
•
–
threshold:
•
–
g g
Frame loss threshold exceeded on mac
Frame loss alarm ratio threshold
The proper alarms are presented as faults at the BTS Site Manager. The proper alarms are reported from the BTS to the OMS/NetAct promptly. The proper alarms can be monitored also using: • •
NetAct Monitor OMS Fault Management
Expected outcome The proper alarm is raised when the threshold is surpassed.
g
The proper alarm does not occur when the threshold is set to zero. The proper alarm occurs only when the threshold is surpassed after the fifteen minutes of measurement. Further information The proper alarms are canceled when the thresholds are not surpassed after the next fifteen minutes of measurement. 10 Monitor the measurement session using the NetAct Performance Manager.
g
This step must be performed after the proper time. The BTS sends the measurement data to the OMS every hour. The measurement data comprises four fifteen-minutes statistics. The OMS sends the measurement data to the NetAct ten minutes after. The measurement data of each fifteen minutes can be monitored then using: •
Issue: 01F
NetAct Performance Manager
DN09146788
253
Transmission and transport features
RU50 Feature Descriptions and Instructions
11 Verify that the proper PM counters are greater than zero. Expected outcome The Frame Loss counters from the CCM messages are greater than zero. 12 Turn off the Frame Loss Measurement session on the BTS. Expected outcome The Frame Loss Measurement session is stopped on the BTS. When Frame Loss Measurement session is stopped on the BTS then: • • • • • •
The BTS stops measuring the Frame Loss statistics. The BTS stops sending the Frame Loss Measurement data to the OMS. The BTS discards the incoming Frame Loss messages from the remote MEPs. The Frame Loss messages are not transmitted anymore. The Frame Loss alarm is canceled. The Frame Loss statistics are not cleared but they are not further updated.
Expected outcome The Frame Loss Measurement session at dual-ended mode works properly.
4.2.5.2
Testing Frame Loss Measurement session using single-ended mode Purpose This procedure verifies Frame Loss Measurement session at single-ended mode. Before you start This procedure needs the activation of the Ethernet Service OAM PM on two BTSs. The Frame Loss statistics are fifteen-minutes statistics.
g
The Frame Loss Measurement session at single-ended mode cannot be activated when: • • •
1
g
The Maintenance Association has more than one remote MEP. There are measurements with the same mode under the same MEP. The activation causes the total ingress of Service OAM frames to surpass 1000 fps.
Open the BTS Site Manager. The NetAct Configuration Management software can be used alternatively.
2
Turn on the Frame Loss Measurement session on the BTS. Perform the actions on the BTS: a) Open the TRS Hardware from the View bar.
254
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Transmission and transport features
b) Open the Ethernet Service OAM menu. c) Open the New drop-down menu and create Frame loss measurement session. d) Mark the Frame loss measurement in use checkbox.
g
The Frame Loss Measurement session can be turned on on two BTSs. The measurement data can be monitored then on two BTSs. 3
Determine the Frame Loss Measurement session parameters. The Frame Loss Measurement session parameters are configured as presented: •
BTS1 – – – –
•
MAC address Frame loss measurement mode: Single ended Frame loss transmission interval: 100 ms Frame loss alarm ratio threshold: 0.01%
BTS2
g
Determine when needed. – – – –
g
MAC address Frame loss measurement mode: Single ended Frame loss transmission interval: 100 ms Frame loss alarm ratio threshold: 0.01%
Note that to complete the step, you must send the configuration to the BTS.
4
Monitor the measurement session using the Wireshark. Expected outcome The LMM messages are sent out from the BTS to the remote MEP. The LMR messages are transmitted from the remote MEP at the same time.
5
Monitor the measurement session using the BTS Site Manager. Expected outcome The Frame Loss Measurement session is activated on the BTS. When Frame Loss Measurement session is activated on the BTS then: • • • • •
Issue: 01F
The BTS purges the current Frame Loss statistics. The BTS starts to measure the Frame Loss statistics again. The BTS measures the Frame Loss Ratio every fifteen minutes. The BTS sends the measurement data to the OMS every hour. The Frame Loss alarm occurs when the threshold is surpassed.
DN09146788
255
Transmission and transport features
6
RU50 Feature Descriptions and Instructions
Start the Soam Frame Loss statistics measurement (M5141) at OMS.
g
This step must be performed using: RNW Measurement Management NetAct Administration of Measurements
• •
g
The OMS does not store the measurement data to database. The OMS transfers the measurement data from the BTS to the NetAct. Expected outcome The Soam Frame Loss statistics measurement is started at OMS. The OMS sends the measurement data to the NetAct ten minutes after every hour. 7
Break connection by disconnecting Ethernet cable from one of the devices.
g
The connection break generates lost frames. The connection break must be performed only for some time.
8
After fifteen minutes verify that the proper PM counters are greater than zero.
g g
This step must be performed fifteen minutes after the measurement start. The PM counters are non-zero when non-SOAM frames are transmitted. When performing the current step, the proper PM counters are: Frame Loss Measurement counters:
The Frame Loss counters are non-zero when non-SOAM frames are lost. The measurement data of each fifteen minutes can be monitored using: •
BTS Site Manager
Expected outcome The Frame Loss counters from the LMM messages are greater than zero.
256
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Transmission and transport features
The proper PM counters are presented during the fifteen minutes of measurement. The proper PM counters are updated after the completion of fifteen minutes of measurement. 9
Verify that the proper alarm is raised when the threshold is surpassed.
g
This step must be performed fifteen minutes after the measurement start. The proper statistics for Frame Loss Measurement: alarm:
•
–
threshold:
•
–
g g
Frame loss threshold exceeded on mac
Frame loss alarm ratio threshold
The proper alarms are presented as faults at the BTS Site Manager. The proper alarms are reported from the BTS to the OMS/NetAct promptly. The proper alarms can be monitored also using: • •
NetAct Monitor OMS Fault Management
Expected outcome The proper alarm is raised when the threshold is surpassed.
g
The proper alarm does not occur when the threshold is set to zero. The proper alarm occurs only when the threshold is surpassed after the fifteen minutes of measurement. Further information The proper alarms are canceled when the thresholds are not surpassed after the next fifteen minutes of measurement. 10 Monitor the measurement session using the NetAct Performance Manager.
g
This step must be performed after the proper time. The BTS sends the measurement data to the OMS every hour. The measurement data comprises four fifteen-minutes statistics. The OMS sends the measurement data to the NetAct ten minutes after. The measurement data of each fifteen minutes can be monitored then using: •
Issue: 01F
NetAct Performance Manager
DN09146788
257
Transmission and transport features
RU50 Feature Descriptions and Instructions
11 Verify that the proper PM counters are greater than zero. Expected outcome The Frame Loss counters from the LMM messages are greater than zero. 12 Turn off the Frame Loss Measurement session on the BTS. Expected outcome The Frame Loss Measurement session is stopped on the BTS. When Frame Loss Measurement session is stopped on the BTS then: • • • • • •
The BTS stops measuring the Frame Loss statistics. The BTS stops sending the Frame Loss Measurement data to the OMS. The BTS discards the incoming Frame Loss messages from the remote MEPs. The Frame Loss messages are not transmitted anymore. The Frame Loss alarm is canceled. The Frame Loss statistics are not cleared but they are not further updated.
Expected outcome The Frame Loss Measurement session at single-ended mode works properly.
4.2.5.3
Testing Frame Delay Measurement session Purpose This procedure verifies Frame Delay Measurement session. Before you start This procedure needs the activation of the Ethernet Service OAM PM on two BTSs. The One-way Frame Delay Variation statistics are fifteen-minutes statistics. The Two-way Frame Delay statistics are one-minute and fifteen-minutes statistics.
g
The Frame Delay Measurement session cannot be activated when: • • •
1
g
There are 80 Frame Delay Measurement sessions already created. The activation causes the total ingress of Service OAM frames to surpass 1000 fps. The Frame Delay Measurement session with the same remote MAC is already activated.
Open the BTS Site Manager. The NetAct Configuration Management software can be used alternatively.
2
Turn on the Frame Delay Measurement session on the BTS. Perform the actions on the BTS:
258
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
a) b) c) d)
g
Transmission and transport features
Open the TRS Hardware from the View bar. Open the Ethernet Service OAM menu. Open the New drop-down menu and create Delay measurement session. Mark the Delay measurement in use checkbox.
The Frame Delay Measurement session can be turned on on two BTSs. The measurement data can be monitored then on two BTSs. 3
Determine the Frame Delay Measurement session parameters. The Frame Delay Measurement session parameters are configured as presented: •
BTS1 – – – – –
•
MAC address Delay measurement transmission interval: 100 ms Delay measurement message PDU size: 1490 One-way delay variation 15 min alarm threshold: 3.0 ms Two-way delay measurement 1 min alarm threshold: 4.0 ms
BTS2
g
Determine when needed. – – – – –
g
MAC address Delay measurement transmission interval: 100 ms Delay measurement message PDU size: 46 One-way delay variation 15 min alarm threshold: 5.0 ms Two-way delay measurement 1 min alarm threshold: 6.0 ms
Note that to complete the step, you must send the configuration to the BTS.
4
Monitor the measurement session using the Wireshark. Expected outcome The DMM messages are sent out from the BTS to the remote MEP. The DMR messages are transmitted from the remote MEP at the same time.
5
Monitor the measurement session using the BTS Site Manager. Expected outcome The Frame Delay Measurement session is activated on the BTS. When Frame Delay Measurement session is activated on the BTS then: • • • •
Issue: 01F
The BTS purges the current Frame Delay statistics. The BTS starts to measure the Frame Delay statistics again. The BTS sends the measurement data to the OMS every hour. The Frame Delay alarms occur when the thresholds are surpassed.
DN09146788
259
Transmission and transport features
6
RU50 Feature Descriptions and Instructions
Start the Soam Two Way Delay Statistics measurement (M5142) at OMS.
g
This step must be performed using: RNW Measurement Management NetAct Administration of Measurements
• •
g
The OMS does not store the measurement data to database. The OMS transfers the measurement data from the BTS to the NetAct. Expected outcome The Soam Two Way Delay Statistics measurement is started at OMS. The OMS sends the measurement data to the NetAct ten minutes after every hour. 7
Start the Soam One Way Delay Variation Statistics measurement (M5143) at OMS.
g
This step must be performed using: RNW Measurement Management NetAct Administration of Measurements
• •
g
The OMS does not store the measurement data to database. The OMS transfers the measurement data from the BTS to the NetAct. Expected outcome The Soam One Way Delay Variation Statistics measurement is started at OMS. The OMS sends the measurement data to the NetAct ten minutes after every hour. 8
After one minute verify that the proper PM counters are greater than zero.
g g
This step must be performed one minute after the measurement start. The PM counters are non-zero when non-SOAM frames are transmitted. When performing the current step, the proper PM counters are: •
The Frame Delay counters must be always greater than zero at the present moment.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Transmission and transport features
The measurement data of each minute can be monitored only for: Two-way Frame Delay Measurement
•
The measurement data of each minute can be monitored only using: BTS Site Manager
•
Expected outcome The Two-way Frame Delay counters are greater than zero.
g
The proper PM counters are presented during the one minute of measurement. The proper PM counters are updated after the completion of one minute of measurement. 9
Verify that the proper alarm is raised when the threshold is surpassed.
g
This step must be performed one minute after the measurement start. The proper statistics for Two-way Frame Delay Measurement: alarm:
•
–
threshold:
•
–
g g
Two way delay threshold exceeded on mac
Two-way delay measurement 1 min alarm threshold
The proper alarms are presented as faults at the BTS Site Manager. The proper alarms are reported from the BTS to the OMS/NetAct promptly. The proper alarms can be monitored also using: • •
NetAct Monitor OMS Fault Management
Expected outcome The proper alarm is raised when the threshold is surpassed.
g
The proper alarm does not occur when the threshold is set to zero. The proper alarm occurs only when the threshold is surpassed after the one minute of measurement.
10 After next one minute verify that the proper alarm is canceled.
g
This step must be performed next one minute after the measurement start. Expected outcome The proper alarms are canceled when the thresholds are not surpassed after the next one minute of measurement.
Issue: 01F
DN09146788
261
Transmission and transport features
RU50 Feature Descriptions and Instructions
The proper alarms are not canceled when the thresholds are surpassed after the next one minute of measurement. 11 After fifteen minutes verify that the proper PM counters are greater than zero.
g g
This step must be performed fifteen minutes after the measurement start. The PM counters are non-zero when non-SOAM frames are transmitted. When performing the current step, the proper PM counters are: One-way Frame Delay Variation Measurement counters:
The Two-way Frame Delay Measurement counters can be verified again. The Frame Delay counters must be always greater than zero at the present moment. The measurement data of each fifteen minutes can be monitored using: BTS Site Manager
•
Expected outcome The One-way Frame Delay Variation counters are greater than zero. The Two-way Frame Delay counters are greater than zero.
g
The proper PM counters are presented during the fifteen minutes of measurement. The proper PM counters are updated after the completion of fifteen minutes of measurement.
12 Verify that the proper alarm is raised when the threshold is surpassed.
g
This step must be performed fifteen minutes after the measurement start. The proper statistics for One-way Frame Delay Variation Measurement: •
alarm: –
•
threshold: –
g
262
OneWay delay variation threshold exceed on mac
One-way delay variation 15 min alarm threshold
The proper alarms are presented as faults at the BTS Site Manager.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Transmission and transport features
The proper alarms are reported from the BTS to the OMS/NetAct promptly. The proper alarms can be monitored also using: • •
NetAct Monitor OMS Fault Management
Expected outcome The proper alarm is raised when the threshold is surpassed.
g
The proper alarm does not occur when the threshold is set to zero. The proper alarm occurs only when the threshold is surpassed after the fifteen minutes of measurement. 13 After next fifteen minutes verify that the proper alarm is canceled.
g
This step must be performed next fifteen minutes after the measurement start. Expected outcome The proper alarms are canceled when the thresholds are not surpassed after the next fifteen minutes of measurement. The proper alarms are not canceled when the thresholds are surpassed after the next fifteen minutes of measurement. 14 Monitor the measurement session using the NetAct Performance Manager.
g
This step must be performed after the proper time. The BTS sends the measurement data to the OMS every hour. The measurement data comprises four fifteen-minutes statistics. The OMS sends the measurement data to the NetAct ten minutes after. The measurement data of each fifteen minutes can be monitored then using: •
g
NetAct Performance Manager
NetAct does not support one-minute statistics.
15 Verify that the proper PM counters are greater than zero. Expected outcome The One-way Frame Delay Variation counters are greater than zero. The Two-way Frame Delay counters are greater than zero. Expected outcome The Frame Delay Measurement session works properly.
Issue: 01F
DN09146788
263
Operability features
RU50 Feature Descriptions and Instructions
5 Operability features 5.1 RAN2199: BTS Event Triggered Symptom Data Collection 5.1.1 Description of RAN2199: BTS Event Triggered Symptom Data Collection Introduction to the feature This feature introduces automatic fault-triggered BTS symptom data collection. The triggering BTS faults are defined in the Site Configuration File (SCF) using the NetAct Configurator.
5.1.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature benefits the operator as follows: • •
5.1.1.2
Automatic symptom data collection reduces the workload. The immediate data collection following the fault occurrence assists the troubleshooting process. Self-triggered symptom data generation is more accurate and thus more efficient in solving failures.
Requirements Software requirements Software requirements lists the software required for this feature.
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
Flexi Multiradio BTS
RU50
Not planned RN8.0
mcRNC4.1
Not planned OMS3.0 1)
WN9.0
OMS3.1 2)
264
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Operability features
Flexi Lite BTS
Flexi Multiradio 10 BTS
NetAct
MSC
SGSN
MGW
UE
WL9.1
WN9.1
Support not required
Support not required
Support not required
Support not required
Support not required
1) for RU50 2) for RU50 EP1
Hardware requirements This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF or Flexi Lite BTS WCDMA.
5.1.1.3
Functional description The event triggered symptom data collection can be divided into following steps: 1. 2. 3. 4.
Selection of the triggering faults Data collection after the selected faults occur Data transfer and storage Viewing the collected data
Figure 25: Symptom data collection from the BTS illustrates the log collection mechanism. Figure 25
Symptom data collection from the BTS
Selection of the triggering faults The automatic symptom data collection is triggered by BTS faults selected by the user, who should contact the NSN Technical Support personnel to get the list of recommended triggers. The list of faults is defined with the symptomDataTriggerL parameter.
Issue: 01F
DN09146788
265
Operability features
RU50 Feature Descriptions and Instructions
g
The list of BTS faults is available in the Flexi Multiradio BTS WCDMA Faults document. The TRS faults (IDs within range 61000-61999) are not considered as triggers for the symptom data collection. A triggering threshold can be set - it defines how many times a certain fault should occur for the same fault source to trigger the data collection. By default no triggers are defined. Data collection after the selected faults occur The log collection happens only when the fault occurs. The log consists of, for example: • • • • • • • •
computer log writings HW configuration alarm history active SW version transport configuration black box data performance data auto-connection report
Data transfer and storage Symptom data consists of one or several files that are transferred separately to OMS immediately after the data has been collected. The OMS is able to perform simultaneous uploads from several BTSs. The existing file transfer mechanism through the BTSOM interface is used to transfer the data to OMS. If the triggering fault leads to a recovery reset of the BTS, the upload to OMS is stopped and it is not restarted automatically. In the OMS, the files are combined into one package file. This file is named in a common way: TSUPL___BTS__..tar The name contains the following information: • • • • • •
TSUPL: used by OMS to identify the file type as a symptom data file : identifies the controller (for example, RNC) : the controller ID number : the BTS ID number : identifies the troubleshooting task in the BTS : indicates when the file is created (using the OMS local time). The date and time format is YYYYMMDDhhmmss.
The files are stored in the following directory: /var/opt/OMSftproot/NE/TroubleshootingData
g
The 71106 TROUBLESHOOTING DATA RECEIVED alarm indicates that the log file has been transferred to OMS. The dwAlarmForUploadCompleted parameter is used for disabling/enabling the alarm setting in OMS. The 71129 TROUBLESHOOTING DATA CREATION OR UPLOAD FAILED indicates that the data creation or upload to OMS has failed. Old symptom data files are deleted automatically from the BTS (after being transferred to OMS). When the clean up procedure starts in the OMS, the OMS deletes files older than certain number of days (defined with the dwNELogDaysSpan parameter). By default, files older than 10 days are removed. Additionally, the OMS monitors the disk space use and if needed, performs additional clean up procedure.
266
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Operability features
With the dwBTSUploadEnabled parameter, the automatic data transfer to OMS can be enabled/disabled. Viewing the collected data The files can be viewed using the Log Viewer in the OMS Element Manager. The Log Viewer introduces the Troubleshooting data filter component to allow user to filter troubleshooting files to show only those files not older than a defined period of days (user can specify value from 1 to 30). When user logs in to OMS Element Manager, the Troubleshooting data filter component contains the default value which is taken from the HideTRSFilesOlderThanDaysFilter LDAP parameter (2 days) or from the web browser cookie (if any is stored). When the user sets new value in this component, this new value is preserved within the same session and also restored next time when the user logs in to OMS Element Manager (web browser cookie mechanism is used to preserve the value set by the user). The troubleshooting data files can also be downloaded to the client's computer using the Log Viewer. Only the archive files can be downloaded and not the content of the archive. The log files are sent to OMS even if the BTS fault was filtered by the BTS alarm system and the related alarm was not displayed in OMS.
5.1.1.4
System impact Interdependencies between features This feature is a part of generic troubleshooting data collection function that consists of the following features: • • •
RAN1873: OMS Troubleshooting Data Collection RAN1805: RNC Event Triggered Symptom Data Collection RAN2446: Emergency Symptom Data Collection in IPA-RNC
Impact on interfaces This feature has no impact on interfaces.
Impact on commands There are no commands related to this feature.
Impact on network and network element management tools This feature has no impact on network element management tools.
Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.1.1.5
RAN2199: BTS Event Triggered Symptom Data Collection management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Issue: 01F
DN09146788
267
Operability features
RU50 Feature Descriptions and Instructions
Alarms Table Related existing alarms lists existing alarms related to this feature. Table 115
Related existing alarms
Alarm ID
Alarm name
71106
TROUBLESHOOTING DATA RECEIVED
71129
TROUBLESHOOTING DATA CREATION OR UPLOAD FAILED
Measurements and counters There are no measurements or counters related to this feature.
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table New parameters lists parameters introduced with this feature. Table 116
When the LDAP parameter value is changed, the new value immediately takes effect (no additional action is necessary). It applies to all parameters in this table.
Sales information Table 119
Sales information
BSW/ASW
SW component
License control in network element
BSW
RAN
Not defined
5.1.2 Activating RAN2199: BTS Event Triggered Symptom Data Collection Purpose Follow this procedure to activate the RAN2199: BTS Event Triggered Symptom Data Collection feature. For more information on the feature, see the RAN2199: BTS Event Triggered Symptom Data Collection feature description in RU50 Feature Descriptions and Instructions. Before you start
g
The feature is activated when the operator enables automatic upload of symptom data to OMS using the dwBTSUploadEnabled LDAP parameter. By default the functionality is turned on. The actual symptom data collection takes place if any triggering faults have been defined during the BTS commissioning. The list of faults is defined using the Symptom data trigger list (symptomDataTriggerL) parameter under the MRBTS object. Restart of the RNC, OMS or BTS is not required after the activation of this feature. This procedure does not cause downtime, and it can be performed at any time of the day. Make sure you have access to the Parameter Tool in the OMS Element Manager.
1
Log in to OMS Element Manager.
2
Open the Parameter Tool. The Parameter Tool is available in the External Applications (in the Application Launcher window that is displayed).
Issue: 01F
DN09146788
269
Operability features
RU50 Feature Descriptions and Instructions
3
Change the dwBTSUploadEnabled LDAP parameter value to 1. Path: ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwBTSUpload Enabled
Expected outcome The RAN2199: BTS Event Triggered Symptom Data Collection feature is turned on. Further information It takes approximately 10 minutes to make the change effective in the OMS.
5.1.3 Deactivating RAN2199: BTS Event Triggered Symptom Data Collection Purpose Follow this procedure to deactivate the RAN2199: BTS Event Triggered Symptom Data Collection feature. For more information on the feature, see the RAN2199: BTS Event Triggered Symptom Data Collection feature description in RU50 Feature Descriptions and Instructions. Before you start Restart of the RNC, OMS or BTS is not required after the deactivation of this feature. This procedure does not cause downtime, and it can be performed at any time of the day. Make sure you have access to the Parameter Tool in the OMS Element Manager.
1
Log in to OMS Element Manager.
2
Open the Parameter Tool. The Parameter Tool is available in the External Applications (in the Application Launcher window that is displayed).
3
Change the dwBTSUploadEnabled LDAP parameter value to 0. Path: ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwBTSUpload Enabled
Expected outcome The RAN2199: BTS Event Triggered Symptom Data Collection feature is turned off. Further information It takes approximately 10 minutes to make the change effective in the OMS.
270
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Operability features
5.1.4 Testing RAN2199: BTS Event Triggered Symptom Data Collection Purpose
g
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 basic functionality of the RAN2199: BTS Event Triggered Symptom Data Collection feature. Test environment • •
Flexi BTS integrated with RNC Log Viewer in the OMS Element Manager
Before you start The following prerequisites need to be fulfilled: • • • • •
1
System is up and running without alarms. The O&M Iub link is connected. The cells are on air. All required licenses are active. Proper fault IDs are included during commissioning (the faults used to test the feature are mentioned in the procedure).
Power up and commission the BTS. Expected outcome: All cells are on air, no alarms visible.
Issue: 01F
DN09146788
271
Operability features
RU50 Feature Descriptions and Instructions
2
Check if requested fault IDs (10 and 49) are set in commissioning.
Expected outcome: Site is recommissioned. 3
Power off or remove the connection between the RM and FSM and wait for the Failure in optical RP3 interface fault (10) to appear.
It might take up to 10 minutes. During this time do not make any changes or take snapshots from the BTS. Expected outcome: The Failure in optical RP3 interface fault (10) is visible. . 4
Check if logs are gathered in the OMS. The logs are stored in the following directory: /var/opt/OMSftproot/NE/TroubleshootingData/
272
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
5
Operability features
Power on or establish the connection between the RM and the FSM. Expected outcome: The Failure in optical RP3 interface fault (10) cleared, all cells are on air.
6
Block one of the cells, wait for the Cell blocked fault (49) to appear.
It might take up to 10 minutes. During this time do not make any changes or take snapshot from BTS. Expected outcome: The Cell blocked fault (49) is visible. 7
Check if logs are gathered in the OMS. The logs are stored in the following directory: /var/opt/OMSftproot/NE/TroubleshootingData/
8
Unblock the cell. Expected outcome: The Cell blocked fault (49) is cleared, all cells are on air.
Issue: 01F
DN09146788
273
Operability features
RU50 Feature Descriptions and Instructions
5.2 RAN2919: OMS Certificate Update and Revocation Support 5.2.1 Description of RAN2919: OMS Certificate Update and Revocation Support Introduction to the feature The OMS supports the automated certificate life cycle management by autonomous update of the operator entity certificate. The certificate can be signed by a multilayer Public Key Infrastructure (PKI) system consisting of sub-ordinate Certificate Authorities (CAs) and the root CA on top. Revocation lists provided by the signing CAs are loaded and regularly updated.
5.2.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature benefits the operator as follows: •
•
5.2.1.2
The operator is able to use a usual Public Key Infrastructure (PKI) with a root CA on top and use case-specific sub-ordinate CAs in charge for signing both the RAN and OMS nodes. 3GPP-compliant life cycle management allows flexibility on PKI vendor selection and harmonized certificate management for OMS in the same fashion as for BTS and Security Gateways. This results in severe OPEX reductions.
Requirements Software requirements The following table lists the software required for this feature. Table 120
274
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
OMS
BTS Flexi
Flexi Lite
RU50 EP1
support not required
support not required
OMS3.1
support not required
support not required
support not required
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
support not required
NetAct 8 EP2 (NetAct 15)
support not required
support not required
support not required
support not required
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Operability features
Hardware requirements This feature requires no new or additional hardware.
5.2.1.3
Functional description This certificate management feature supports the autonomous update of the OMS operator certificate and the provision of revocation information to the secure transport layers, such as TLS or HTTPS. With the help of the revocation lists the secure transport layers check if it is allowed to establish a secure connection to a particular remote communication peer.
3GPP-compliant life cycle management The Certificate Management Protocol (CMP) protocol and procedures are implemented as specified in 3GPP TS 33.310.This affects especially trust anchor delivery to OMS and CMP message signing by the CA or alternatively by the Registration Authority closing the CMP protocol session.
Multilayer support The OMS certificate can be signed by a trust chain, for example, the OMS end entity certificate is signed by a sub-ordinate CA which itself is signed by the root CA. The OMS has the complete trust chain for its own operator certificate stored and supports a chain of trust of four layers, that is maximum three sub-ordinate CAs except for the root CA.
Certificate format OMS supports X.509v3 certificates. The following formats have to be supported: • • •
PEM: it is the format used for user interface. DER: it is the format used for transferring certificates over CMP. PKCS#12: it is the required format for transferring certificates and keys to OMS.
Automated OMS operator certificate update The CMPv2 protocol implementation is enhanced by the key update procedure. The OMS renews its operator certificate automatically before the lifetime expires. In addition, the operator is able to use the NWI3 Mediation Fragment Configuration Tool to trigger the operator certificate update on demand remotely.
Trust anchor deployment and update The trust anchors, root CA certificate, and optional sub-ordinates CA certificates are delivered using either the CMP protocol exchange (for key signing request or key update) or by the manual OMS set-up configuration (files in the PKSC#12 or PEM format). When the certificate is close to expiration and OMS is not able to update it or it has already expired, the OMS sends a notification to NetAct.
Local certificate enrollment If the operator has no online PKI in service, it is then possible to load the operator certificate and trust anchors manually as part of the OMS set-up configuration procedures with files. The off-line created key-pair and the related certificate are included within a passphrase protected PKCS #12 file. In addition, certificates and RSA keys are accepted as PEM formatted files.
Issue: 01F
DN09146788
275
Operability features
RU50 Feature Descriptions and Instructions
3GPP algorithms In addition to SHA-1 the OMS supports SHA_256 as hash algorithm for certificates as required by 3GPP TS 33.310 chapter 6.1.1 Common rules to all certificates.
Certificate Revocation List (CRL) check CRL support can be activated/deactivated by operator's configuration. If activated, the OMS performs the CRL housekeeping.
CRL distribution points (CRLDP) given by certificates of the own PKI By default the OMS uses found CRLDP received within CA certificates of the own trust chain to address and download the CRLs for the own PKI. The OMS downloads and updates these lists automatically from the LDAP servers. In addition, the operator is able to trigger the update with the NetAct MNCTool or OMS CLI omscertificate tool.
Configurable CRL distribution points Alternatively, configurable CRL sources are available (IP addresses/FQDN and path). The OMS offers 10 additional CRL distribution points which can be configured with IP addresses/FQDN and path defined per certificate.
5.2.1.4
System impact Interdependencies between features This feature is related to the RAN2267: Certificate Management for OMS Products feature.
Impact on interfaces This feature has impact on the following OMS interfaces: • • • • •
HTTPS: Server and Client RUIM-LDAP: Client OMS LDAPS: Client and Server BTSOM: Server EMI: Server
Impact on commands This feature is related to the following commands: • • • • • • • •
Impact on network and network element management tools This feature simplifies network management by automatic and centralized certificate management functions.
Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.2.1.5
RAN2919: OMS Certificate Update and Revocation Support management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms Table 121: New alarms lists alarms introduced with this feature. Table 121
New alarms
Alarm ID
Alarm name and description
71122
CRL UPDATE FAILURE. This alarm is raised when the NE fails to retrieve or validate a CRL from the server.
71123
CERTIFICATE REVOKED. This alarm is raised when the OMS own certificate is listed on CRL.
71133
CERTIFICATE CAPACITY REACHED. The OMS sets this alarm when its own CA certificate storage capacity or CRL storage space is about to be reached.
71134
CERTIFICATE EXPIRED. The OMS sets this alarm when its own EE or intermediate CA or root CA certificate expires.
70381
CRL DOWNLOAD FAILURE. This alarm is raised when the OMS fails to retrieve or validate a CRL for peer certificate from the server.
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 122: New OMS LDAP parameters lists parameters introduced with this feature.
Issue: 01F
DN09146788
277
Operability features
Table 122
RU50 Feature Descriptions and Instructions
New OMS LDAP parameters
Attribute ClusterRoot/OMS/SW/SS_Nwi3Certificate/Nwi3Certificate/CANECloseCertUpdateTimerAdv This parameter defines how many days in advance the OMS triggers the operator certificate update procedure or fetches CA certificates from the certificate repository (if CR is configured). ClusterRoot/OMS/SW/SS_Nwi3Certificate/Nwi3Certificate/CANECloserCertUpdateTimerAdv This parameter defines how many days in advance the OMS raises the 71125 CERTIFICATE EXPIRING alarm and triggers the operator certificate update procedure or fetches CA certificates from the certificate repository (if CR is configured). ClusterRoot/OMS/SW/SS_Nwi3Certificate/Nwi3Certificate/CRLPeriodicDownloadTimer This parameter defines how often the OMS downloads CRLs from CRL distribution points.
There are no PRFILE parameters related to this feature.
5.2.1.6
Sales information Table 123
Sales information
BSW/ASW
SW component
License control in network element
BSW
RAN
not defined
5.2.2 Testing RAN2919: OMS Certificate Update and Revocation Support Purpose
g
These are examples 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 these procedures is to verify that the activation of the RAN2919: OMS Certificate Update and Revocation Support feature has been successful. Test environment •
one OMS – –
•
278
private key, public key, CA root certificate and EE certificate are available CMP server related parameters is configured in OMS
one Certificate Management Protocol (CMP) server
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Operability features
5.3 RAN2699: OMS System Status View 5.3.1 Description of RAN2699: OMS System Status View Introduction to the feature This feature introduces easy to use general OMS System Status View that enables an instant real time view of OMS node's overall status.
5.3.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature benefits the operator as follows: • •
5.3.1.2
It makes monitoring and troubleshooting of OMS easier and faster. It lowers the operating costs and improves OMS service level in the long term.
Requirements Software requirements The following table lists the software required for this feature. Table 124
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
Flexi BTS
RU50 EP1
support not required
support not required
support not required
support not required
OMS3.1
support not required
Flexi Lite BTS
Flexi 10 BTS
NetAct
MSC
SGSN
MGW
UE
support not required
support not required
support not required
support not required
support not required
support not required
support not required
Hardware requirements This feature requires no new or additional hardware.
Issue: 01F
DN09146788
279
Operability features
5.3.1.3
RU50 Feature Descriptions and Instructions
Functional description This feature is designed as a set of area-specific views that display different types of information helping the operator to monitor the OMS system. Operator accesses status view and the provided system information after selecting appropriate OMS System Status View web page. Area-specific views are divided into two main groups: •
•
OMS Resources. Views available within this group inform the operator about status of OMS server and its generic services. From the information presented here the operator is able to verify if OMS operates correctly as a server. These views focus on hardware, software, and network configuration. There are also processes running on OMS server presented along with their states. The OMS Resources views allow the operator to conclude the condition of server regardless of its OSS responsibilities. OMS Services. Views available within this group inform the operator about the more detailed status of O&M Services provided by the OMS. From the information presented here the operator is able to verify if OMS operates correctly as an Operations Support System element. Core mediation operations are tracked here using two perspectives: current tasks and historical events. The operator is also presented counters and alarms related to particular O&M areas.
The OMS provides OMS System Status View main page with triggers allowing to display the following child views: 1. OMS Resources • • • •
Each of the child views consists of several components that are shown in Figure 26: OMS System Status View application structure diagram.
280
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 26
Operability features
OMS System Status View application structure diagram OMSSystemStatusView
OMSResources
Hardware
Network & Applic.
OMS Software
OMSServices
OMS Processes
PM
FM
CM/TOPO
SWM
Security Manag.
Connect. Manag.
OMSHW Specification
Net&IP layer Conf. view
OMS SW Specification
HASManag. Objectsview
Active Alarms view
Active Alarms view
Active Alarms view
Processes view
Active Alarms view
OMS Connectivity
Disks&RAID Monitoring
Northbound M.-Plane Interf. view
Op. History view
Active Alarms view
Processes view
Processes view
Processes view
CurrentOp. view
Processes view
Active Alarms view
Active Alarms view
Southbound M.-Plane Interf. view
Current Op. view
Config. view
CurrentOp. view
CurrentOp. view
Op.History view
RUIM view
Processes view
Op. History view
Active Alarms view
Op.History view
Op.History view
Op.History view
Config. view
CMP Server view
CurrentOp. view
RUIM view
Config. view
File Transfers view
Op.History view
CMP Server view
Processes view
Config. view
CRL Manag. view
File Transfers view
Certificates view
CRL Management view NTP Management view Active Alarms view DNS Config. view
The list of components view and their short descriptions are presented in Table 125: Functional scope of OMS System Status View components: Table 125
Issue: 01F
Functional scope of OMS System Status View components
Component view name
Short description
Active Alarms view
Active Alarms view displays information about currently active alarms within a particular domain or area.
Processes view
Processes view provides a list and the current state of all processes necessary to produce services provided by a particular OMS domain.
Operation History view
Operation History presents details of events being a part of operations which are performed within certain area. This view provides advanced filter functionality allowing to find any operation-related information.
Current Operations view
Current Operations view provides information about currently ongoing or recently finished operations inside particular OMS domain/area.
DN09146788
281
Operability features
RU50 Feature Descriptions and Instructions
Table 125
282
Functional scope of OMS System Status View components (Cont.)
Component view name
Short description
Configuration view
Configuration view displays information about essential configuration of some OMS domains or areas. Configuration parameter values are usually retrieved from LDAP.
Certificates view
Certificates view displays list of certificates installed in the OMS certificate storage. The list contains whole chain of trust: end entity (EE), root CA and intermediate CA certificates.
OMS Connectivity
OMS Connectivity view summarizes the quantities of connected RNCs, BTSs and cells and also presents OMS connectivity limits.
OMS HW Specification
OMS HW Specification view displays information about OMS hardware resources: server, CPUs, RAM memories, disks, network cards, RAID controllers, and BIOS.
Disks & RAID Monitoring
Disks & RAID Monitoring view displays information about hardware and software RAID configuration and status, physical drives and logical disks information and health status. It also contains summary of partitions and their usage.
Network & IP Layer Configuration view
Network & IP Layer Configuration view provides detailed information on the OMS IP layer network configuration, the network interfaces status and defined routing policy.
OMS SW Specification
OMS SW Specification view provides information on the currently used OMS software components, including OMS application itself, OMS Platform, operating system, and essential third party software components. Additionally a list of the currently installed software sets (stored) on OMS server is provided, accompanied by the staging area correction level.
Northbound MPlane Interface view
Northbound M-Plane Interface view enables monitoring of different aspects of communication interface to NetAct.
Southbound MPlane Interface view
The Southbound M-Plane Interface view enables monitoring of the BTSOM interface configuration and status.
RUIM view
RUIM view enables monitoring of the Centralized User Authentication and Authorization (CUAA) service configuration and accessibility. Even though CUAA is not a service provided by the OMS, it requires monitoring in the OMS System Status View. It is one of the external services that OMS operation depends on.
CMP Server view
CMP Server view enables monitoring of the external CMP server configuration and accessibility. CMP Server is another external service required by the OMS, therefore it is monitored in the OMS System Status View.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 125
Operability features
Functional scope of OMS System Status View components (Cont.)
Component view name
Short description
File Transfers view
File Transfers view enables monitoring of the configuration related to the file transfers in OMS operations, statuses of accounts necessary for file transfers functionality, and state of secure/insecure file transfer protocols according to the current configuration
CRL Management view
CRL Management view provides configuration details of CRL usage in certificate verification process, rules of CRL retrieving from distribution points and certificate lifetime monitoring rules.
NTP Management view
NTP Management view enables monitoring of the OMS clock synchronization status with remote NTP server(s).
DNS Configuration view
DNS Configuration view provides information on the DNS configuration on the OMS.
HAS Management Objects view
HAS Management Objects view provides information about all nodes, recovery groups, recovery units, and processes present in the OMS environment.
The OMS System Status View is implemented within OMS Web UI.
5.3.1.4
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 simplifies network management by introducing easy to use and instant real time status view.
Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.3.1.5
RAN2699: OMS System Status View management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms Table 126: New Alarms lists alarms introduced with this feature.
Issue: 01F
DN09146788
283
Operability features
RU50 Feature Descriptions and Instructions
Table 126
New Alarms
Alarm ID Alarm name
w
70359
HARD DISK DRIVE FAILURE.
70377
SYSTEM CLOCK OUT-OF-SYNC WITH NTP SERVER.
NOTICE: These alarms are available in the basic OMS software version and do not require any additional licenses.
Measurements and counters Information on measurements and counters related to this feature will be provided in further deliveries.
Key performance indicators There are no key performance indicators related to this feature.
Parameters Information on parameters related to this feature will be provided in further deliveries.
5.3.1.6
Sales information Table 127
Sales information
BSW/ASW
License control in network element
License control attributes
Activated by default
ASW
OMS LK
Long-term ON/OFF licence
No
5.3.2 Activating RAN2699: OMS System Status View Purpose Follow the procedure below to activate the RAN2699: OMS System Status View. Before you start The OMS System Status View license file (in xml format) has to be stored in /home// directory on OMS (for example /home/Nemuadmin/). For information on copying files to OMS, see Transfering files from NOLS to FEWS or OMS in Installing and Commissioning OMS.
284
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Operability features
1
Log in to the OMS as root user.
2
Import the license file. Enter to following command for the OMS System Status View license file: # lmcli importLicence /home//
3
Activate the feature. Enter the following command to activate RAN2699 feature: # lmcli activateFeature 5335
Result The feature RAN2699: OMS System Status View is activated.
5.3.3 Verifying RAN2699: OMS System Status View Purpose Follow steps below to verify that the activation of the RAN2699: OMS System Status View feature has been successful. 1
Log in to the OMS as root user.
2
Verify the feature statuses. Enter the following command: lmcli getFeatureStatus 5335
Expected outcome FEATURE STATUS Feature Code: 5335 Feature Name: OMS_System_Status_View Feature State: Active Licences corresponding to this feature: Licence Filename:
3
Open supported web browser. List of supported web browsers can be found in OMS Element Manager of Using Element Manager in OMS.
4
Browse to OMS Element Manager main page at the OMS server IP address. In the internet browser enter the OMS IP address in the following way: https:///OMSElementManager/. Note that only HTTP over SSL (HTTPS) connections are allowed and the protocol indicator https: needs to be used in the URL before the host address.
5
Provide login credentials and click Login. Default login is Nemuadmin and default password is nemuuser. It is recommended to change the password after the first login to prevent unauthorized access.
Issue: 01F
DN09146788
285
Operability features
RU50 Feature Descriptions and Instructions
6
Run the OMS System Status View application.
Result If the OMS System Status View application is visible on the main page of OMS Element Manager, it has been activated successfully.
5.3.4 Deactivating RAN2699: OMS System Status View Purpose To deactivate RAN2699: OMS System Status View feature, follow this procedure. 1
Log in to the OMS as root user.
2
Deactivate the feature. Enter the following command: lmcli deactivateFeature 5335
3
Delete license file (optional). Enter the following command: lmcli deleteLicence
4
Open supported web browser. List of supported web browsers can be found in OMS Element Manager of Using Element Manager in OMS.
5
Browse to OMS Element Manager main page at the OMS server IP address. In the internet browser enter the OMS IP address in the following way: https:///OMSElementManager/. Note that only HTTP over SSL (HTTPS) connections are allowed and the protocol indicator https: needs to be used in the URL before the host address.
6
Provide login credentials and click Login. Default login is Nemuadmin and default password is nemuuser. It is recommended to change the password after the first login to prevent unauthorized access.
Result OMS System Status View application is not visible on the main page of OMS Element Manager. The feature RAN2699: OMS System Status View is deactivated and the license file is removed from the OMS.
286
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Operability features
5.4 RAN2393: Optical Fiber: RX/TX Level Monitoring 5.4.1 Description of RAN2393: Optical Fiber: RX/TX Level Monitoring Introduction to the feature With this feature it is possible to obtain optical interface diagnostics information from the SFP connector. Such information can be used for troubleshooting purposes.
5.4.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits The feature can be mainly used for troubleshooting purposes or on a new site installation in case of SFP optical interface problem between the RF Module and the System Module. The diagnostics information gives a very good indication of the fiber link quality between the RF Module and the System Module.
5.4.1.2
Requirements Software requirements Table 128: Software requirements lists the software required for this feature.
RAS
Flexi Direct IPA-RNC
RU50 EP1
Support not required
Table 128
mcRNC
OMS
BTS Flexi
Support not Support not Support not WN9.1 required required required
Flexi Lite Not relevant
Software requirements
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
WN9.1
Support not required
Support not required
Support not required
Support not required
Support not required
Hardware requirements This feature is not supported with any single-sector and dual-sector Radio Module, FRGF three-sector Radio Module and FRGG RRH. This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF.
Issue: 01F
DN09146788
287
Operability features
5.4.1.3
RU50 Feature Descriptions and Instructions
Functional description Functional overview The inter-module (RP3) link connectivity troubleshooting feature monitors the optical interface condition. The feature supports on-demand polling and shows data from both ends of the link - the near end and the far end. The BTS Site Manager shows the SFP online diagnostic information. The following data is shown: • • • • • • •
SFP Vendor SFP Type Module temperature Transceiver Tx supply voltage Transceiver Tx bias current Transceiver Tx power Transceiver Rx optical power
The BTS Site Manager presents the statistics of the monitored indicators and allows to set the cumulative LCV counter to zero.
5.4.1.4
System impact Interdependencies between features There are no interdependencies between this and any other feature.
Impact on interfaces This feature has no impact on interfaces.
Impact on network and network element management tools This feature has no impact on network management or network element management tools.
Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.4.1.5
RAN2393 Optical fiber: RX/TX level monitoring management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms There are no alarms related to this feature.
Measurements and counters There are no measurements or counters related to this feature.
288
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Operability features
Key performance indicators There are no key performance indicators related to this feature.
Parameters There are no parameters related to this feature.
5.4.1.6
Sales information Table 129
Sales information
BSW/ASW
SW component
License control in network element
BSW
RAN
Not defined
5.4.2 Testing RAN2393: Optical Fiber: RX/TX Level Monitoring Purpose The purpose of this test is to verify if the RAN2393: Optical Fiber: RX/TX Level Monitoring feature, which is mainly used for troubleshooting purposes or on new site installation in case of Small Form Pluggable (SFP) optical interface problem between RF Module and System Module or System Module (SM) and extension module, is working properly. The diagnostics information gives a very good indication of the fiber quality link between the radion and its anchor SM. Before you start Required test environment: • •
Operational radio access network (RAN) and core network (CN) WBTS is in On Air status
During the test, the following information should be verified: •
Static Parameters: – – – – – – – –
•
Issue: 01F
Vendor - representing the vendor name PartNumber - representing SFP part number SerialNumber - representing SFP serial number Revision - representing SFP revision information ComplianceCode - revision of SFF-8472 spec the SFP complies with ConnectorType NominalSpeed - nominal speed that supported by SFP in units of 100 Mbps LowLimit - units of 1% for the lowest supported speed compared to NominalSpeed HighLimit - units of 1% for the highest supported speed compared to NominalSpeed
Dynamic measurements:
DN09146788
289
Operability features
RU50 Feature Descriptions and Instructions
–
– – – – –
1
bit error rate estimate (BER) - In digital transmission, the number of bit errors is the number of received bits of a data stream over a communication channel that have been altered due to noise, interference, distortion, or bit synchronization errors. The bit error rate or bit error ratio (BER) is the number of bit errors divided by the total number of transferred bits during a studied time interval. BER is a unitless performance measure, often expressed as a percentage. transceiver Rx optical Power (Transceiver Rx received optical power) module temperature (Internally measured transceiver temperature) transceiver Tx supply voltage (Internally measured transceiver supply voltage) transceiver Tx bias current (Transceiver Tx bias current) transceiver Tx Power (Transceiver Tx output power)
Enable RAN2393: Optical Fiber: RX/TX Level Monitoring feature. a) Open the BTS site manager to connect to the BTS. b) Select Tests and then Rx/TX Level Monitoring c) Click monitor icon to enable RAN2393: Optical Fiber: RX/TX Level Monitoring feature
2
Check static parameters and dynamic measurements for each optical interface. In the Current Values window, all parameters are measured in real time. In History Values window, all dynamic measurements statistics are saved with each range. Expected result: Each working optical interface should be visible in the RX/TX Level Monitoring window. All parameters should be shown correctly. History Values window can show dynamic measurements' history.
g
If the BTS has just started, wait for one minute for generating history values. Unexpected result: RAN2393: Optical Fiber: RX/TX Level Monitoring feature is not working properly if: • • • •
3
Working optical interface is not shown in the Rx/Tx Level Monitoring window. Static paremeters do not conform to SFP's specification. There is no data in dynamic measurements. There is no data in history values.
Compare static parameters with SFP's specification. a) Lock one RF module or extension module and change its SFP. b) Unlock the locked RF module or the locked extension module. Expected result: The optical interface for which SFP has been changed should update static parameters. New parameters should be the same as changed SFP's specification.
290
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Operability features
Unexpected result: Static parameters are not updated for the optical interface which for SFP has been changed. New values are different from SFP's specification. 4
(Optional) Attenuate the fiber and check if Rx optical power decreases for that optical interface. Ideally, an optical attenuator is used to change the fiber's loss and check if Rx optical power can be changed accordingly. However, if the optical attenuator is not available, replace the fiber between System module and RF module or System module and Extention module with a long fiber. For example, replace 10-meter fiber to onekilometer fiber. Expected result: Since longer fiber would increase the optical signal loss, Rx received optical power should decrease. Unexpected result: Rx optical power does not decrease after changing into a longer fiber.
5.5 RAN3004: Parameter Categorization 5.5.1 Description of RAN3004: Parameter Categorization Introduction to the feature The RAN3004: Parameter Categorization feature introduces Radio Network (RNW) and IP plan parameters categorization in NetAct Configurator. The goal is to differentiate between the parameters for simplified operations (Basic parameters) and the parameters that are out of primary focus during regular network operation (Advanced parameters).
5.5.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature facilitates the network configuration by dividing the RNW and IP plan parameters into Basic and Advanced categories.
5.5.1.2
Requirements Software requirements The following table lists software required for this feature.
Issue: 01F
DN09146788
291
Operability features
RU50 Feature Descriptions and Instructions
Table 130
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
Flexi Multiradio BTS
RU50 EP1
Not planned RN8.1
mcRNC4.1
Not planned Support not required
Support not required
Flexi Lite BTS
Flexi Multiradio 10 BTS
NetAct
MSC
SGSN
MGW
UE
Support not required
Support not required
NetAct 8 Support not EP2 (NetAct required 15)
Support not required
Support not required
Support not required
Hardware requirements This feature requires no new or additional hardware.
5.5.1.3
Functional description The RAN3004: Parameter Categorization feature introduces RNW and IP plan parameters categorization into two pre-defined groups in the Editor Views of the CM Editor. The first group (Basic parameters) is meant for parameters used during cell deployment that are adjusted to particular scenario. The other group (Advanced parameters) holds the network optimization and fine tuning parameters (including those related to advanced or complex features). The following list shows the key characteristics of parameter categories: •
Basic – – – –
•
configuration parameters (for example, network element identifiers, IP addresses, and so on) planning parameters (for example, neighbor definitions, frequency plan, scrambling code plan, PCI plan, RA preamble plan, and so on) parameters related to the dimensioning parameters that define the operator strategy (for example, traffic steering, thresholds for power control, handovers, cell reselections, high level parameters defining feature behavior, and so on)
Advanced – –
network optimization and fine tuning parameters (including those related to advanced or complex features) parameters that are out of primary focus during regular network operation
In Netact CM Editor there are pre-defined Parameter Views called Basic parameters and Advanced parameters. They group parameters according to the category. These two pre-defined groups can be used as a template to create the custom Views (Editor Views).
292
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 27
5.5.1.4
Operability features
CM Editor - Basic and Advanced parameters views
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 NetAct Configurator introduces two pre-defined Views for the RNW and IP plan parameters (Basic parameters and Advanced parameters).
Impact on system performance and capacity This feature has no impact on system performance or capacity.
5.5.1.5
RAN3004: Parameter Categorization management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Faults and alarms There are no faults and 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.
Issue: 01F
DN09146788
293
Operability features
5.5.1.6
RU50 Feature Descriptions and Instructions
Sales information Table 131
Sales information
BSW/ASW
SW component
License control in network element
BSW
RAN
Not defined
5.6 RAN2507: RNW Plan Progress Indicator and Abort 5.6.1 Description of RAN2507: RNW Plan Progress Indicator and Abort Introduction to the feature RAN2507: RNW Plan Progress Indicator and Abort feature introduces the following functions: • •
5.6.1.1
allows the user to abort radio network (RNW) configuration management operations at any point of their execution shows the progress of RNW configuration management operations via NetAct CM Operations Manager, providing the percentage of the completed operation and the estimated time left
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature benefits the operator as follows: • • •
5.6.1.2
Operators can abort the RNW plan download, activation, rollback, and upload operations (when needed) without waiting for the planned action to finish. Operators can abort a long-running operation to allow them to perform a more critical operation. It provides better visibility to RNW plan operation progress, which is crucial when activating big plans such as RNW plan download, activate, rollback, and upload.
Requirements Software requirements Table 132: Software requirements lists the software that is required for this feature.
294
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 132
Operability features
Software requirements
RAS
Flexi Direct
IPA-RNC
mcRNC
Flexi Direct RNC
OMS
BTS Flexi
RU50 EP1
Not planned
RN8.1
mcRN4.1
Not planned
OMS3.1
Support not required
Flexi Lite
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
Support not required
Support not required
NetAct 8 EP2 (NetAct 15)
Support not required
Support not required
Support not required
Support not required
Hardware requirements This feature requires no new or additional hardware.
5.6.1.3
Functional description The RAN2507: RNW Plan Progress Indicator and Abort feature provides better monitoring and control for radio network (RNW) configuration management operations. This feature is able to show progress information for: • • •
RNW plan download RNW plan activation RNW plan rollback
OMS forwards operation progress information from RNC to NetAct. The NetAct CM operations manager shows the plan download/activation/rollback progress for each RNC that is included in the plan, as well as for the overall plan download. The NetAct CM operations manager displays the progress indicator, which shows the percentage of overall operation completion and the estimated time left to finish the operation.
g
For configuration changes that impact the BTS, the estimated time left reported in progress indications from the RNC considers an estimated latency due to messages exchanged between the RNC and the BTS. Unexpected delays in the BTS response to such messaging may cause an operation's time left to increase as the operation progress, rather than decrease, as it is typically expected. This feature also introduces the ability to abort RNW configuration management operations: • • • •
Issue: 01F
RNW plan download RNW plan activation RNW plan rollback RNW configuration upload
DN09146788
295
Operability features
RU50 Feature Descriptions and Instructions
The operator is able to abort the configuration management operations for all RNCs or for a single RNC within the plan. The NetAct CM operations manager shows the result of the abort request, which is either successful (abort operation was initiated), or a failure (the network element rejected the abort request).
Monitoring RNW configuration management operations message flow The monitoring of RNW configurations management operations are explained in Figure 28: Monitoring RNW configuration management operations message flow Figure 28
The RNC is responsible for calculating the overall progress for plan activation/download/rollback operation. The RNC also estimates the total amount of time that the activation/download/rollback operation will be completed. The overall calculations and time estimation are delivered as "operation progress message" via OMS-RNC interface. The RNC forwards the operation progress message to the OMS every 60 seconds. The OMS serves as a mediator between the RNC and NetAct. The OMS receives the operation progress message from the RNC that contains the activation/download/rollback progress information. The OMS forwards the message to NetAct. NetAct receives the operation progress message via the NetAct-OMS interface. The operation progress message is processed in NetAct and serves as the source of information in updating the NetAct CM operation manager that displays percentage completion and estimated time left to complete the activation/download/rollback operation of each RNC in the plan, as well as the overall plan.
296
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Operability features
Aborting RNW configuration management operations message flow The operator can abort RNW plan activation/download/rollback/upload operation of a single RNC or all the RNCs within the plan. The abort function of plan activation, download, rollback, and upload operations are initiated in the NetAct CM operation manager as shown in Figure 29: Aborting RNW configuration management operations message flow Figure 29
NetAct generates the begin operation abort message via the NetAct-OMS interface to abort RNW plan operations and sends the message to the OMS. The OMS processes the message from NetAct and releases new message operation abort to the RNC via the OMS-RNC interface. The OMS is also responsible for canceling other operation processing that has not started in the RNC. The RNC processes the operation abort message and decides if the abort request is possible based on the current state of the ongoing operation. If the abort request is still possible, the RNC acknowledges the request and performs the abort of: • • •
the RNW plan download operation by terminating the consistency checking that is in progress. the RNW plan activation and rollback operation by terminating the activation or rollback operation at a safe condition. the RNW plan upload by terminating the creation of the configuration upload file if it is in progress or by removing the configuration upload file if already created.
During the plan activation and rollback abort operation, the RNC is in the safe condition that ensures the RNC database is in a state that is ready to receive subsequent operations. The RNC generates a response with the aborted cause value and forwards the response via the OMS-RNC interface. The response is different for each RNW plan operation: • • • •
File load completed message for plan download File activation acknowledgement message for plan activation Rollback acknowledgement message for plan rollback File load prepared message for plan upload
The OMS receives and processes the response message with the aborted cause value. The OMS generates new response operation completed message and forwards this message to NetAct via the NetAct-OMS interface. The NetAct receives the operation completed message and displays aborted status of the aborted operation in the NetAct CM operation manager. The RNC raises a minor alarm, 3173 RNW PLAN ACTIVATION OR ROLLBACK FAILED, if the ongoing RNW plan activation or rollback operation is aborted. The alarm notifies the operator about the possible inconsistency in RNW database (RNWDB) because of the abort operation. The system will automatically cancel the alarm when the operator resolves any potential RNWDB consistency issues, either by performing a plan rollback or by provisioning a new plan with the RNC-FullConsCheckRequest parameter set.
g
298
The RNW plan operation abort during RNW plan activation or rollback scenario might create inconsistencies in RNW database which may get applied on actual radio network. These inconsistencies, if they exist, can only be cleared when RNWDB becomes consistent by performing either a plan rollback or by provisioning a new plan with the RNC-FullConsCheckRequest parameter set.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
5.6.1.4
Operability features
System impact Interdependencies between features There are no interdependencies between this and any other feature.
Impact on interfaces This feature impacts interfaces as follows: •
NetAct-OMS –
–
–
•
There is a new progress in operation message to be used by OMS for forwarding to NetAct that indicates the percentage of completed tasks and the estimated time left to complete the RNW plan management operation. There is an operation abort message to be used by OMS for requesting abort of RNW plan management operation in RNC, which includes the task identifier of the operation to be aborted. There is an operation abort acknowledgement message to be used by RNC as a response to the operation abort message received from OMS, which includes the task identifier of the operation to be aborted, code indicating the reason of the rejection of the abort request (optional), and text describing the reason of the rejection of the abort request (optional).
OMS-RNC –
–
There is a new operation abort message to be used by OMS for requesting abort of RNW plan management operation in RNC. The new message includes the task identifier of the operation to be aborted. There is a new operation abort acknowledge message to be used by RNC as a response to the operation abort message from the OMS. This message includes: • • •
–
task identifier of the operation to be aborted unacknowledged reason code that indicates the reason of the abort request rejection (optional) unacknowledged text that describes the reason of the abort request rejection (optional)
There is a new operation progress message to be used by the RNC to indicate the progress information of the ongoing plan download, activation, or rollback operation in the RNC. The new message includes the percentage of completed tasks and the estimated time left to complete the plan management operation.
Impact on network and network element management tools This feature has an impact on O&M system performance. The abort function is considered as a performance improvement to the users, since the operators are able to stop the processing of activities that are not crucial to them.
Impact on system performance and capacity The funcionality of this feature will be executed on the following situations: •
Issue: 01F
during the maintenance window when the system capacity impacts are not likely to occur
DN09146788
299
Operability features
RU50 Feature Descriptions and Instructions
•
5.6.1.5
during emergency situations when the system capacity impacts are less important than the functionality that this feature provides
RAN2507: RNW Plan Progress Indicator and Abort management data For information on alarm, counter, key performance indicator, and parameter, see Reference documentation.
Alarms Table 133: Alarms lists the alarm that is related to this feature. Table 133
Alarms
Alarm ID
Alarm name
3173
RNW PLAN ACTIVATION OR ROLLBACK FAILED
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 134: Parameters lists the new parameter that is related to this feature. Table 134
Parameters
Full name
Abbreviated name
Managed object
Full Consistency Check Request
FullConsCheckRequest
RNC
Commands The RNW plan operation abort is triggered using NetAct user interface (UI). However, in the event of RNC-OMS link failure, RNW plan operation abort can also be done using the following commands: •
to stop the ongoing task: – –
•
300
for mcRNC stop radio-network rnw-plan-operation confirm-command yes for cRNC Z1MPS;
to stop the operation with identified "task-id-value":
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
–
–
5.6.1.6
Operability features
for mcRNC stop radio-network rnw-plan-operation task-id confirm-command yes for cRNC Z1MPS:;
Sales information BSW/ASW
SW component
License control in network element
ASW NetAct
RAN
CM Activation Options
5.7 RAN2554: Transport Configuration Fall-back 5.7.1 Description of RAN2554: Transport Configuration Fall-back Introduction to the feature If after a configuration update the Flexi Multiradio BTS fails to connect to its management network, self healing measures are taken. This applies for failures during normal operation after a configuration-update.
5.7.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature benefits the operator as follows: • • •
5.7.1.2
Self healing reduces the effort for network management and maintenance and increases the Flexi Multiradio BTS availability due to less outage. Site visits can be avoided when a changed BTS transmission configuration prohibits remote management connections.
Requirements Software requirements Table 135: Software requirements lists the software that is required for this feature.
Issue: 01F
RAS
Flexi Direct RU50
Flexi Direct RNC
IPARNC
mcRNC
OMS
BTS Flexi
Flexi Lite
RU50
Flexi Direct RU50
Support not required
Support not required
Support not required
Support not required
WN9.0
WL9.1
DN09146788
301
Operability features
RU50 Feature Descriptions and Instructions
Table 135
Software requirements
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
WN9.1
Support not required
Support not required
Support not required
Support not required
Support not required
Hardware requirements This feature requires Flexi Multimode System Module FSMC/D/E, or Flexi Multiradio System Module FSMF or Flexi Lite BTS WCDMA.
5.7.1.3
Functional description Autonomous fallback to previous configuration A fallback to the previous configuration happens when the BTS fails to successfully (re)connect the M-plane to the Network Management System after a remote configuration update and activation. If the M-plane can be established with the old configuration, a notification is sent to the Network Management System indicating that the new configuration was not activated. If the old one fails as well, the received new one is activated again and the BTS continues with the regular link failure mechanism. The self healing recovery is initiated only after Transport Network Layer (TNL) configuration changes via BTS Site Configuration file (SCF) activation. The TNL configuration refers to the parameters defined in the Transport System (TRS) PDDB.
302
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 30
g 5.7.1.4
Operability features
RAN2554: Transport Configuration Fallback
Self-healing is not allowed when BTSSM is connected to the BTS.
System impact Interdependencies between features There are no interdependencies between features.
Impact on interfaces This feature has no impact on interfaces.
Impact on commands There are no commands related to this feature.
Impact on network and network element management tools The self healing functionality and logic are implemented in the BTS. There are new parameters introduced, which impact NetAct adaptation.
Impact on system performance and capacity This feature has no impact on system performance or capacity.
Issue: 01F
DN09146788
303
Operability features
5.7.1.5
RU50 Feature Descriptions and Instructions
RAN2554: Transport Configuration Fallback management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms The following table lists alarms and faults, which are related to this feature. Table 136
New fault
Alarm ID
Alarm name
7665
New fault coming with: BASE STATION TRANSMISSION ALARM. Meaning of new fault: the base station has recovered the M-plane connection by falling back to the old transport configuration after the configuration change
Parameters Table 137
5.7.1.6
New parameter
Full name
Abbreviated name
Managed object
Enable transport configuration fallback
enableTransportConfigF allback
IPNO
Sales information Table 138
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
BTS LK
5.7.2 Activating RAN2554: Transport Configuration Fallback Purpose Follow this procedure to activate RAN2554: Transport Configuration Fallback feature. For more information on this feature, see Description of RAN2554: Transport Configuration Fallback. The feature can be activated using BTS Site Manager or NetAct CM Editor. Before you start This feature requires that FSMrel2 (excluding FSIA and FSIB), FSMrel3, or FlexiLite is present.
304
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
5.7.2.1
Operability features
Activating RAN2554: Transport Configuration Fallback using BTS Site Manager
1
Open the BTS Site manager.
2
Download feature license to BTS. a) In the Configuration menu, choose License Management. b) A License Managament window opens. Select the appropriate license file and click Download to BTS.
3
Enable transport configuration fallback. a) In the Configuration menu, choose IP Configuration. b) Choose IP Adresses tab. Or in the IP view, choose the IP Addresses tab. c) Check the Enable Transport Configuration Fallback checkbox.
5.7.2.2
Activating RAN2554: Transport Configuration Fallback from NetAct CM Editor
1
Open NetAct CM Editor
2
Configure IPNO/enableTransportConfigFallback to "True".
3
Activate SCF in BTS from NetAct. When enableTransportConfigFallback is set to "True" using SCF then corresponding license is automatically downloaded to BTS.
5.7.3 Verifying RAN2554: Transport Configuration Fallback Purpose Follow this procedure to verify that this feature has been activated successfully.
1
Activate the transport configuration fallback feature. For more information see, Activating RAN2554: Transport Configuration Fallback.
2
Testing the transport configuration fallback feature. For more information see, Testing RAN2554: Transport Configuration Fallback.
5.7.4 Deactivating RAN2554: Transport Configuration Fallback Purpose
Issue: 01F
DN09146788
305
Operability features
RU50 Feature Descriptions and Instructions
Follow this procedure to deactivate RAN2554: Transport Configuration Fall-back. For more information, see Description of RAN2554: Transport Configuration Fall-back. The feature can be activated using BTS Site Manager or NetAct CM Editor. Before you start Make sure that RAN2554: Transport Configuration Fallback feature is already activated.
5.7.4.1
Deactivating RAN2554: Transport Configuration Fallback using BTS Site Manager
1
Disabling the feature a) Open BTS Site manager. b) Choose the IP Addresses tab. c) Uncheck the Enable Transport Configuration Fallback checkbox.
5.7.4.2
Deactivating RAN2554: Transport Configuration Fallback from NetAct CM Editor
1
Disabling the feature a) Open NetAct CM Editor b) Configure IPNO/enableTransportConfigFallback to "False". c) Activate SCF in BTS from NetAct.
5.7.5 Testing RAN2554: Transport Configuration Fallback Purpose The purpose of this test is to verify if the RAN2554 Transport Configuration Fallback feature is activated and working correctly. Before you start Required test environment: • • •
1 Flexi Multiradio BTS WCDMA integrated to the network with FSMrel2 (excluding FSIA and FSIB), FSMrel3, or FlexiLite NetAct integrated to the network. RNC/mcRNC integrated to network
The following conditions must be true before testing: • • •
5.7.5.1
Enable transport configuration fallback from SEM, or from NetAct. Make sure that the license for RAN2554 Transport Configuration Fallback is valid on NetAct. Ensure that the BTSOM is connected with source RNC on OMS GUI, the DCNLinkStatus on OMS is Enabled, and the WCELs are alive.
Test Case 1: Transport configuration fallback Steps
306
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
1
Operability features
Create a new TRS plan. a) Open NetAct CM Editor. b) Modify the TNL parameters to an unreachable RNC IP address;. For example, the reachable RNC IP address is 10.68.178.18, we may modify it to 10.82.1.1 which is unreachable.
g
It is also feasible to modify TNL parameters by recommisionning the WBTS via SEM. Result The paremeters are modified successfully in the plan. 2
Download and activate the plan to the WBTS. Result The plan provisions successfully and after the TRS/BTS restart, the BTS is disconnected to the unreachable RNC.
3
Connect to the WBTS locally, and monitor the O&M status of the WBTS. Result RNC IP has been modified to new target IP on WBTS IP configuration, and WBTS OAM status is disconnected
4
Check the WBTS and WCELs status on target RNC on Netact GUI. There will be no new target RNC because it is not a valid IP address. Result After the WBTS initiates re-establishment to the new target RNC for 10 connection attempts, the WBTS falls back to the original RNC. Then DCNLinkStatus with original RNC is Enabled, and the WCELs are alive.
5
Check the BTS status. Check the alarm on BTS, OMS, and NetAct. Result The WBTS modifies its RNC IP into the original RNC IP address, and O&M's connection to the original RNC is established.
g
An alarm is issued indicating that the planned configuration changes are not used in the WBTS --- 7665 BASE STATION TRANSMISSION ALARM is present. 6
Create a new TRS plan. a) Open the NetAct CM Editor. b) Modify the TNL parameters to a reachable IP address. c) Provision the plan. Result
Issue: 01F
DN09146788
307
Operability features
RU50 Feature Descriptions and Instructions
The parameter modification and provision are successful, and the BTS connects to the new target RNC.
g 5.7.5.2
The configuration change is a corrective configuration change for an earlier recovery ending in the fallback operation. The alarm 7665 BASE STATION TRANSMISSION ALARM is cancelled on BTSSM, OMS, and NetAct GUI.
Test Case 2: Transport configuration roll forward Steps
1
Create a new TRS plan. a) Open NetAct CM Editor. b) Modify the TNL parameters to an unreachable RNC IP address;. For example, the reachable RNC IP address is 10.68.178.18, we may modify it to 10.82.1.1 which is unreachable. Result The parameters are modified successfully in the plan.
2
Download and activate the new plan to WBTS. Result The plan provisions successfully and after the TRS/BTS restart the BTS is disconnected to the unreachable RNC.
3
Connect to WBTS locally, and monitor the O&M status of the WBTS. Result After the WBTS initiates re-establishment to the new target RNC for 10 connection attempts, the WBTS falls back to the original RNC.
4
Check the BTS and WCELS status on a new target RNC on NetAct GUI. Result After WBTS initiates re-establishment to the new target RNC for ten connection attempts, WBTS fall back to the original RNC
5
Disable the O&M of the WBTS. a) When the WBTS is trying to connect to new target RNC, log on to the original RNC. b) Use the following command to delete the O&M route: ZQKA:[]:[,[]];
Result
308
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Operability features
The WBTS modifies its RNC IP to original RNC IP address, but WBTS will not be able to connect because O&M is disabled on original RNC. After 10 times attempts, the WBTS roll forward to the new target RNC once more. 6
Check the BTS status. Check the alarm on BTS, OMS, and NetAct. Result The O&M connection to both RNC is unestablished. In the WBTS site manager, the RNC IP address should be the new target RNC. No RAN2554 alarm would be present in the SEM.
7
Create a new TRS plan. a) Open the NetAct CM Editor. b) Use the following command to create a new O&M route: ZQKC:,: [| def, []]:: []:[];
c) Modify the TNL parameters to a reachable IP address. d) Provision the plan. Result The parameter modification and provision are successful, and the BTS connects to the target RNC.
5.8 RAN2229: Troubleshooting Data Management by NetAct 5.8.1 Description of RAN2229: Troubleshooting Data Management by NetAct Introduction to the feature This feature allows a NetAct user to trigger symptom data collection from RNC OMS and IPA-RNCs, and upload the collected symptom data from them. This feature also provides the functionality for RNC OMS to automatically transfer symptom data generated from it's managed RNCs and Flexi BTSs to NetAct, whether it was created spontaneously due to an internal trigger, or due to an operator request from a local NE user interface. Troubleshooting data can be collected based on different profiles. This feature provides only the "Emergency" profile for data collection from the RNCs. Feature RAN2872 will provide additional profiles for troubleshooting data collection.
Issue: 01F
DN09146788
309
Operability features
5.8.1.1
RU50 Feature Descriptions and Instructions
Benefits Operator benefits This feature provides OPEX savings for the operator when resolving problems that require troubleshooting data to diagnose.
5.8.1.2
Requirements Software requirements The following table lists software required for this feature.
Table 139
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
Flexi Multiradio BTS
RU50 EP1
Not planned Support not required
Support not required
Not planned OMS3.1
Support not required
Flexi Lite BTS
Flexi Multiradio 10 BTS
NetAct
MSC
SGSN
MGW
UE
Support not required
Support not required
NetAct 8 Support not EP2 (NetAct required 15)
Support not required
Support not required
Support not required
Hardware requirements This feature does not have any hardware requirements.
5.8.1.3
Functional description This feature provides a centralized mechanism to request and collect troubleshooting data from various Network Elements, eliminating the need for the user to log in to individual NEs directly. Troubleshooting data is transferred to the OMS, stored there and forwarded to NetAct, which provides the central point of control. Simultaneous collection requests are possible for at least one OMS and up to 20 RNCs managed by that OMS. RAN2229 builds upon the data collection functionality of RAN2199: BTS Event Triggered Symptom Data Collection, RAN1805: Alarm triggered log collection for RNC, RAN1873: OMS trouble shooting data collection and RAN2446: RNC symptom data collection.
5.8.1.4
System impact Interdependencies between features RAN2229 depends upon the following features: • • • •
310
RAN2199: BTS Event Triggered Symptom Data Collection RAN1805: Alarm triggered log collection for RNC RAN1873: OMS trouble shooting data collection RAN2446: RNC symptom data collection
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Operability features
Impact on interfaces This feature has no impact on interfaces.
Impact on network and network element management tools This feature adds new functionality to the NetAct network management tool.
Impact on system performance and capacity This feature has no impact on system performance and capacity.
5.8.1.5
RAN2229: Troubleshooting Data Management by NetAct management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms Table Related existing alarms lists existing alarms related to this feature. Table 140
Related existing alarms
Alarm ID
Alarm name
71106
TROUBLESHOOTING DATA RECEIVED
71129
TROUBLESHOOTING DATA CREATION OR UPLOAD FAILED
Measurements and counters There are no measurements or counters related to this feature.
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table New OMS LDAP parameters lists parameters introduced with this feature. Table 141
New OMS LDAP parameters
Attribute ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/NetActNotifyEnabled This parameter controls whether the OMS will automatically upload troubleshooting data to NetAct when it is available.
Issue: 01F
DN09146788
311
Operability features
5.8.1.6
RU50 Feature Descriptions and Instructions
Sales information Table 142
312
Sales information
BSW/ASW
SW component
License control in network element
BSW
RAN
-
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
6 Performance monitoring features 6.1 RAN2496: 3GPP Minimization of Drive Tests 6.1.1 Description of RAN2496: 3GPP Minimization of Drive Tests Introduction to the feature The RAN2496: 3GPP Minimization of Drive Tests feature provides automatic User Equipment (UE) measurements collection and data logging which replace the manual drive testing that the operators have to perform in their networks. Minimization of Drive Tests (MDT) allows also to evaluate the network performance per physical location.
6.1.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature minimizes the drive tests, and thus allows significant cost savings in the coverage optimization during network deployment and maintenance.
6.1.1.2
Requirements Software requirements The following table lists software required for this feature. Table 143
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
Flexi Multiradio BTS
RU50 EP1
Not planned RN8.1
mcRNC4.1
Not planned Support not required
WN9.1
Flexi Lite BTS
Flexi Multiradio 10 BTS
MSC
SGSN
MGW
UE
Support not required
Support not required
Support not required
Not planned WN9.1
NetAct
NetAct 8 Support not EP2 (NetAct required 15)
Hardware requirements This feature requires the L3 Data Collector (Megamon) connected to the RNC. For L3 Data Collector product-specific information, see Care ► Software Supply Tool ► Product Related Tools ► L3 Data Collector (Megamon) in NOLS PIC. This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF.
Issue: 01F
DN09146788
313
Performance monitoring features
6.1.1.3
RU50 Feature Descriptions and Instructions
Functional description The goal of this feature is to minimize the drive tests by using immediate MDT mode concept introduced in 3GPP TS 37.320. The immediate MDT functionality applies to UEs in RRC CELL_DCH state and supports the collection of the following measurements: Figure 31
Common Pilot Channel received signal code power (CPICH RSCP) and Common Pilot Channel ratio of energy per modulating bit to the noise spectral density (CPICH Ec/No) Downlink block error ratio (DL BLER) UE transmission power (UE Tx Power) Rx-Tx time difference type 1 GPS location
Signal to interference ratio (SIR) SIR error Round-trip time (RTT) for R99 and HSPA calls Propagation delay
Measurements reported by RNC: – –
Data Volume measurement (reported separately for downlink and uplink, per QoS class, and per UE) Throughput measurement (reported separately for dowlnink and uplink, per RAB per UE, and per UE)
Measurements collection can be enabled in two ways: • •
for all UEs within the cell with the MDTPeriodicMeasEnabled parameter of the WCEL object for a particular connection (per IMSI) with the IMSIMeasMDTEnabled parameter of the RNFC object and related MML/SCLI commands in RNC
The interval for the UE periodic measurement report is controlled with the UePeriodicMeasInterval parameter of the RNC object.
314
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
6.1.1.4
Performance monitoring features
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 L3 Data Collector gathers the measurement data while NetAct TraceViewer is used to present the measurement reports.
Impact on system performance and capacity This feature impacts system performance and capacity as follows: •
•
•
6.1.1.5
It may cause a minor degradation of the call retainability KPIs. This happens when the UEs periodically send additional measurement reports and thus increase a probability that an RLC unrecoverable error occurs in bad radio conditions. Without the periodical reporting, the UE does not have any message to send using AM-RLC and a failure situation does not happen. When activated on a cell level, it causes additional CPU load for the RNC. In IPARNC this impacts ICSU units and in mcRNC the impact is on the USPU units. Even if CPU load increases, the RNC traffic handling capacity does not degrade. This is because MDT measurement activation for calls is restricted if the RNC control plane CPU load exceeds the threshold defined by the UePeriodicMeasCpuLimit parameter of the RNC object. When activated on a cell level, SIR, SIR Error, and RRT measurements contribute to the BTS load. With high traffic BTS this may cause some degradation of accessibility KPIs.
RAN2496: 3GPP Minimization of Drive Tests management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Faults and alarms There are no faults and 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 The following table lists parameters introduced with this feature.
Issue: 01F
DN09146788
315
Performance monitoring features
Table 144
RU50 Feature Descriptions and Instructions
New parameters
Full name
Abbreviated name
Managed object
Periodic Measurements in UE and WBTS for MDT
MDTPeriodicMeasEnabled
WCEL
IMSI based MDT Measurements
IMSIMeasMDTEnabled
RNFC
Pre-emption capability for emergency call
EmeCallPCIValue
RNAC
Pre-emption vulnerability for emergency call
EmeCallPVIValue
RNAC
Priority level for emergency call
EmeCallLevelValue
RNAC
The following table lists parameters modified by this feature.
g
These parameters are new in mcRNC. This is because they were not present in mcRNC3.0 and are introduced in mcRNC4.1. Table 145
6.1.2 Activating RAN2496: Minimization of Drive Tests Purpose Follow this procedure to activate RAN2496: Minimization of Drive Tests feature for IPARNC and mcRNC. There are two activation scenarios: • •
enabling MDT measurements collection for all UEs within the cell enabling MDT measurements collection for a particular subscriber based on IMSI
Before you start Impact on network elements operation:
316
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
• • • •
Performance monitoring features
This activation procedure does not require reset of the RNC or BTS. This activation procedure does not require cell-locking . This activation procedure does not require any additional configuration for the BTS. However, to support this feature the BTS must be on WN9.1 or later software level. This activation procedure can be used to enable cell-based MDT for all the WCELs under certain RNC even if some of the BTSs are using older software builds. However, in such a case the calls under BTSs that do not support the feature are not measured.
Requirements for network elements: • • •
This feature requires the RNC to be integrated to NetAct. This feature requires the L3 Data Collector (Megamon) connected to the RNC. This feature requires the NetAct TraceViewer to be properly configured with L3 Data Collector (GeoServer parameters).
Required applications: • • • • •
SSH client (for example PuTTY) is used to create the MML/SCLI session to the RNC. MML/SCLI commands or NetAct License Manager are used to install the license and change the feature state to ON. OMS Element Manager or NetAct Configurator is used to modify the RNW parameters-related to the feature. MML/SCLI commands are used to activate the feature for a particular subscriber (based on IMSI). NetAct TraceViewer is used to present the measurements gathered by L3 Data Collector.
License requirements: • •
RAN2496: Minimization of Drive Tests feature is controlled by a license with the feature code 1798. There are two prerequisites for activating the RAN2496: Minimization of Drive Tests feature for a particular subscriber (based on IMSI): – –
•
Subscriber Trace license with the feature code 975 is installed in the RNC SubscriberTrace parameter of the RNFC-1 object is set to Enabled (1)
For more information, see Activating and Operating Subscriber and Equipment Trace in Activating and Verifying RAN04 Features. NetAct TraceViewer requires additional licenses to support RAN2496: Minimization of Drive Tests feature: – –
Subscriber Tracing for WCDMA license is required to support MDT for a particular subscriber. Trace based monitoring for WCDMA license is required to support MDT on the cell level.
For more information, see Checking installed licenses in TraceViewer Help and Tracing licensing in Tracing Technical Reference Guide.
Issue: 01F
DN09146788
317
Performance monitoring features
6.1.2.1
RU50 Feature Descriptions and Instructions
Installing license and configuring the feature state Purpose Follow this procedure to install RAN2496: Minimization of Drive Tests feature license, and change the feature state to ON. For this procedure all the configuration tasks are performed using MML/SCLI commands (NetAct License Manager can be used as an alternative).
1
Retrieve the license file from Nokia.
2
Transfer the license file to the RNC. For IPA-RNC, transfer the license file to the /shadows/LICENCE directory. For mcRNC, transfer the license file to the /home directory. If NetAct License Manager is used, import the license to the repository. For information on license management from NetAct see, License Manager Overview and License Manager Help in NetAct Operating Documentation.
3
Install the license and set the feature state to ON. For IPA-RNC: a) Make an SSH session to IPA-RNC IP address (OMU) and start MML session. b) Install the license and set the feature state to ON. ZW7L:LICENSEFILE.XML:ON;
c) Verify the feature state. ZW7I:FEA,FULL:FEA=1798;
For mcRNC: a) Make an SSH session to mcRNC IP address (/SSH) and start SCLI session. b) Install the license and set the feature state to ON. add license file /home/LICENSEFILE.XML auto-set-features on
c) Verify the feature state. show license feature-mgmt code 0000001798
Result The license for RAN2496: Minimization of Drive Tests feature is installed and the feature state is set to ON.
6.1.2.2
Enabling MDT measurements collection for all UEs within the cell Purpose Follow this procedure to enable the MDT measurements collection for all UEs within the selected cell. For this scenario all the configuration tasks are performed using OMS Element Manager (alternatively NetAct Configurator).
318
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
1
Make an HTTPS connection to OMS IP address and open OMS Element Manager.
2
Navigate to the WCEL object that is a subject for the MDT measurements activation. Option
Description
Use Quick Access Enter the distinguished name (DN) of the parent objects (RNC text box and WBTS) and desired WCEL, for example: RNC-37/WBTS-1/WCEL-11 Use Topology tree Browse through the topology, for example: RNC-37 ► WBTSs ► WBTS-1 ► WCELs ► WCEL-11
3
Configure the WCEL object to enable MDT measurements collection within the cell. a) Right-click on the WCEL object and select Edit Parameters. b) In the Handover Measurement tab, use the MDTPeriodicMeasEnabled parameter to enable individual MDT measurements. The MDTPeriodicMeasEnabled is a bit mask parameter, where the particular bits are used to control the individual MDT measurements. By default all measurements are disabled and set to False (0). To enable the measurement, switch the corresponding bit to True (1). Table 147
Issue: 01F
MDTPeriodicMeasEnabled parameter description
Bit position
Measurement
Additional information
0
CPICH EcNo/CPICH RSCP
-
1
UE Tx Power
-
2
DL BLER
-
3
UE RxTx time difference/BTS RTT
-
4
SIR and SIR Error
-
5
CS GPS
It is operator responsibility to ensure that use of GPS is legally allowed.
6
PS GPS
Using GPS increases UE power consumption.
7
Call Type Selection; CS or both CS and PS
If the value is set to False (0), all the MDT measurements are collected only for CS calls.
If the value is set to True (1), all the MDT measurements are collected for CS and PS calls. Note that bit 5 and bit 6 are used separately to control GPS usage for CS and PS calls. It is then possible to enable MDT for both domains with bit 7 set to True (1) and restrict GPS usage only for CS calls with bit 5 set to True (1) and bit 6 set to False (0). 8-15
-
Spare bits that are not used and set to False (0) by default.
Recommendations for using CS GPS and PS GPS measurements: •
•
Setting the bit 5 (CS GPS) to True (1) and bit 6 (PS GPS) to False (0) enables CS GPS measurements for UEs with either CS RAB or CS+PS RAB. However, if the UE has PS RAB only, the measurements will not be produced. This feature applies only to the UEs in RRC CELL_DCH state. For PS calls it is typical that when UE gets to CELL_DCH state it stays there only for a few seconds until inactivity triggers transition back to lower states. Commanding the UE to perform PS GPS measurements in such a short CELL_DCH state of PS sessions is useless as in many cases the GPS is not able to produce the first measurement report until inactivity moves the UE out of CELL_DCH state. Therefore, the attempts to request PS GPS measurements cause only unnecessary signaling load and consume UE battery. In most cases it is relevant to set CS GPS to True (1) and PS GPS to False (0). Setting PS GPS to True (1) is useful only for special troubleshooting or optimization use case that requires it.
c) Select Apply button to save the changes. Result The RAN2496: Minimization of Drive Tests feature is activated for all UEs within the selected cell(s).
6.1.2.3
Enabling MDT measurement collection for a particular subscriber Purpose Follow this procedure to enable the MDT measurements collection for a particular connection based on the IMSI. For this scenario the configuration tasks are performed with OMS Element Manager (alternatively NetAct Configurator) and MML/SCLI commands in the RNC. Note that IMSI-based MDT measurements can be enabled simultaneously for maximum of 25 subscribers (IMSIs).
320
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
1
Make an HTTPS connection to OMS IP address and open OMS Element Manager.
2
Navigate to the RNFC-1 object. Option
Description
Use Quick Access text Enter the distinguished name (DN) of the parent RNC box object and RNFC-1, for example: RNC-37/RNFC-1 Use Topology tree
Browse through the topology, for example: RNC-37 ► RNFCs ► RNFC-1
3
Configure the RNFC-1 object to enable IMSI-based MDT measurements collection. a) Right-click on the RNFC-1 object and select Edit Parameters. b) In the Handover Measurement tab, set the value of the IMSIMeasMDTEnabled parameter to Enabled (1). c) Select Apply button to save the changes.
4
Configure RNC to enable MDT measurements collection for a particular IMSI. For IPA-RNC: a) Make an SSH session to IPA-RNC IP address (OMU) and start MML session. b) Enable MDT measurement collection with the following command. ZT7T:IMSI=:REF=,TYPE=;
Command syntax:
Issue: 01F
Parameter
Description
IMSI=international mobile subscriber identity
This parameter specifies the A decimal value with a IMSI of the subscriber for maximum of 15 digits. whom MDT measurement collection is to be activated. This parameter is mandatory.
REF=trace reference
This parameter is used to identify the trace session and must be defined uniquely. This parameter is mandatory.
1-65534
TYPE=trace type
This parameter is used to select detail level of the trace data. This parameter is optional (default is
BASIC (default)
DN09146788
Value
HO
321
Performance monitoring features
RU50 Feature Descriptions and Instructions
Parameter
Description
Value
BASIC). However, to enable MDT MDT measurement MDTGPS collection, it must be set either to MDT or MDTGPS RADIO (MDT with GPS support).
Command example: Example below shows how to activate the MDT measurement collection for a subscriber whose IMSI is 2440511223344. The trace reference is 10 and the detail level of MDT measurements is set to MDT. ZT7T:IMSI=2440511223344:REF=10,TYPE=MDT;
For mcRNC: a) Make an SSH session to mcRNC IP address (/SSH) and start SCLI session. b) Enable MDT measurement collection with the following command. set radio-network subs-trace activate-trace imsi trace-ref trace-type
Command syntax: Parameter
Description
Value
imsi
This parameter specifies the A decimal value with a IMSI of the subscriber for maximum of 15 digits. whom MDT measurement collection is to be activated. This parameter is mandatory.
trace-ref-value
This parameter is used to identify the trace session and must be defined uniquely. This parameter is mandatory.
1-65534
trace-type-value
This parameter is used to select detail level of the trace data. This parameter is optional (default is BASIC) however to enable MDT measurement collection, it must be set either to mdt or mdtgps (MDT with GPS support).
basic (default) handover mdt mdtgps radio
Command example: Example below shows how to activate the MDT measurement collection for a subscriber whose IMSI is 2440511223344. The trace reference is 10 and the detail level of MDT measurements is set to MDT. set radio-network subs-trace activate-trace imsi 2440511223344 trace-ref 10 trace-type mdt
Result The RAN2496: Minimization of Drive Tests feature is activated for a particular subscriber based on IMSI.
322
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
6.1.2.4
Performance monitoring features
Configuring feature optional parameters Purpose Follow this procedure to configure RAN2496: Minimization of Drive Tests feature optional parameters. This includes setting up the interval for the UE periodical measurements reports, adjusting RNC units CPU load limit for measurement reports, and defining how feature handles the emergency calls. Optional parameters are configured with OMS Element Manager (alternatively NetAct Configurator). 1
Set the interval for the UE periodical measurement reports. The interval for the UE periodic measurement report is controlled with the UePeriodicMeasInterval parameter of the RNC object and. The default value is set to 16000ms. a) Select the desired RNC from the Topology pane. b) Right-click on the RNC object and select Edit Parameters. c) In the Handover Measurement tab, define the interval with the UePeriodicMeasInterval parameter. d) Select Apply button to save the changes.
2
Set the RNC units CPU load limit for measurement reports (applicable only to cell-based MDT). Activating periodic measurements with MDTPeriodicMeasEnabled parameter of WCEL object causes additional CPU load for the RNC. In IPA-RNC this impacts ICSU units and in mcRNC the impact is on the USPU units. The limit for periodical measurement overload control is defined with UePeriodicMeasCpuLimit parameter of the RNC object. The default value is set to 70%. If the CPU load of ICSU or USPU (control plane) averaged over 1 minute interval exceeds the limit, periodic measurements are not started. Exceeding of the CPU load limit does not impact calls for which periodic measurement reporting is already active. For comparison, the IMSI-based periodic measurements are always activated regardless of the RNC CPU load. This is because only maximum of 25 UEs can be simultaneously traced with IMSI based activation and such a small number does not cause any real capacity degradation for the RNC. a) Select the desired RNC from the Topology pane. b) Right-click on the RNC object and select Edit Parameters. c) In the Handover Measurement tab, define the CPU load limit with the UePeriodicMeasCpuLimit parameter. d) Select Apply button to save the changes.
3
Define how feature handles the emergency calls. The RNC does not initiate periodic measurements for a UE whose CS call is identified as emergency call. This is to avoid any risk for the call reliability potentially caused by the additional signaling. The call is considered as an emergency call if either one of the following conditions is true:
Issue: 01F
DN09146788
323
Performance monitoring features
•
RU50 Feature Descriptions and Instructions
If the Establishment Cause information element of RRC: INITIAL DIRECT TRANSFER is set to Emergency Call.
or •
If the RAB parameters match with the emergency call identification settings configured with the radio network parameters so that all of the following is true: – – –
Pre-emption capability of the RAB matches with the value of EmeCallPCIValue parameter of RNAC object. Pre-emption vulnerability of the RAB matches with the value of EmeCallPVIValue parameter of the RNAC object. Priority level of the RAB matches with the value of EmeCallLevelValue parameter of the RNAC object.
Identification of emergency call based on RAB parameters can be disabled by setting EmeCallPCIValue parameter as RAB parameters are not considered. The disabling may be necessary if Enhanced Multi-Level Precedence and Pre-emption Service (eMLPP) feature is enabled in the core network and also some normal users calls are using the same RAB parameters as emergency calls. This setting does not disable emergency call identification based on INITIAL DIRECT TRANSFER establishment cause. Generally, it is recommended that the emergency calls are excluded from periodic measurements. This means that the operator configures EmeCallPCIValue, EmeCallPVIValue, and EmeCallLevelValue to match with the RAB parameters used by core network for emergency calls. a) Select the desired RNC from the Topology pane. b) Navigate to the RNAC-1 object. c) Right-click on the RNAC-1 object and select Edit Parameters. d) In the Admission Control tab, define emergency call handling with the EmeCallPCIValue, EmeCallPVIValue, and EmeCallLevelValue parameters. e) Select Apply button to save the changes. Result The optional parameters for RAN2496: Minimization of Drive Tests feature are configured.
6.1.3 Verifying RAN2496: Minimization of Drive Tests Purpose Follow this procedure to verify that RAN2496: Minimization of Drive Tests feature works properly in the network. There are two verification scenarios: • •
324
verifying MDT measurements collection for all UEs within the cell verifying MDT measurements collection for a particular subscriber based on IMSI
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
Note that the NetAct TraceViewer is documented in the NetAct Operating Documentation. That is why all the verification steps that involve this application are generic and include references to the application-specific documents.
6.1.3.1
Verifying MDT measurements collection for all UEs within the cell Purpose Follow this procedure to verify the MDT measurements collection for all UEs within the selected cell. For this scenario all the configuration tasks are performed using NetAct TraceViewer. 1
Login to NetAct and launch TraceViewer.
2
Check the L3 Data Collector configuration. For instructions, see: Configuring new GeoServer and Editing GeoServer parameters in TraceViever Help.
3
Create a trace for the cells that are enabled for MDT. Open Tools ► WCDMA Cell Trace Periodical Measurement Management and select for which MDT-enabled cells the trace is to be activated. For instructions, see Trace Viewer Help.
Result The RAN2496: Minimization of Drive Tests feature activation on cell level is successful and feature works properly in the network.
6.1.3.2
Verifying MDT measurements collection for a particular subscriber Purpose Follow this procedure to verify the MDT measurements collection for a particular subscriber. For this scenario the configuration tasks are performed using MML/SCLI commands in the RNC (Step 1) and NetAct TraceViewer (Step 2, Step 3, and Step 4). 1
Display the list of subscribers for whom trace session is active in the RNC. For IPA-RNC: a) Make an SSH session to IPA-RNC IP address (OMU) and start MML session. b) Display the active trace sessions with the following command. ZT7I;
For mcRNC: a) Make an SSH session to mcRNC IP address (/SSH) and start SCLI session. b) Display the active traces session with the following command. show radio-network subs-trace display-trace
Issue: 01F
DN09146788
325
Performance monitoring features
RU50 Feature Descriptions and Instructions
2
Login to NetAct and launch TraceViewer.
3
Check the L3 Data Collector configuration. For instructions, see: Configuring new GeoServer and Editing GeoServer parameters in TraceViewer Help.
4
Create a new Subscriber Trace. Define the Traced Number (IMSI) and Trace Level (Detailed+MDT or Detailed+MDT+GPS). For instructions, see Creating a Subscriber Trace in Trace Viewer Help.
Result The RAN2496: Minimization of Drive Tests feature activation for a particular subscriber is successful and feature works properly in the network.
6.1.4 Deactivating RAN2496: Minimization of Drive Tests Purpose Follow this procedure to deactivate RAN2496: Minimization of Drive Tests feature for IPA-RNC and mcRNC. There are two deactivation scenarios: • •
6.1.4.1
disabling MDT measurements collections for all UEs within the cell disabling MDT measurements collections for a particular connection based on IMSI (this includes disabling MDT for a particular IMSI and disabling IMSI-based MDT entirely for the RNC).
Disabling MDT measurements collection for all UEs within the cell Purpose Follow this procedure to disable the MDT measurements collection for all UEs within the selected cell. For this scenario all the configuration tasks are performed using OMS Element Manager (alternatively NetAct Configurator). 1
Make an HTTPS connection to OMS IP address and open OMS Element Manager.
2
Navigate to the WCEL object that is a subject for the MDT measurements deactivation. Option
Description
Use Quick Access Enter the distinguished name (DN) of the parent objects (RNC text box and WBTS) and desired WCEL, for example: RNC-37/WBTS-1/WCEL-11
326
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Option
Performance monitoring features
Description
Use Topology tree Browse through the topology, for example: RNC-37 ► WBTSs ► WBTS-1 ► WCELs ► WCEL-11
3
Configure the WCEL object to disable MDT measurements collection within the cell. a) Right-click on the WCEL object and select Edit Parameters. b) In the Handover Measurement tab, use the MDTPeriodicMeasEnabled parameter to disable individual MDT measurements. The MDTPeriodicMeasEnabled is a bit mask parameter, where the particular bits are used to control the individual MDT measurements. To disable the measurement, switch the corresponding bit to False (0). c) Select Apply button to save the changes.
Result The RAN2496: Minimization of Drive Tests feature is deactivated for all UEs within the selected cell(s).
6.1.4.2
Disabling MDT measurement collection for a particular subscriber Purpose Follow this procedure to disable the MDT measurements collection for a particular subscriber based on the IMSI (Step 1) or to disable the IMSI-based MDT entirely for the RNC (Step 2, Step 3, and Step 4). For this scenario the configuration tasks are performed with OMS Element Manager (alternatively NetAct Configurator) and MML/SCLI commands in the RNC. 1
Configure RNC to disable MDT measurements collection for a particular IMSI. For IPA-RNC: a) Make an SSH session to IPA-RNC IP address (OMU) and start MML session. b) Disable MDT measurement collection with the following command. ZT7U:IMSI=;
Command syntax: Parameter
Description
Value
IMSI=interna tional mobile subscriber identity
This parameter specifies the IMSI of the subscriber for whom MDT measurement collection is to be deactivated. This parameter is mandatory.
A decimal value with a maximum of 15 digits.
Command example:
Issue: 01F
DN09146788
327
Performance monitoring features
RU50 Feature Descriptions and Instructions
Example below shows how to deactivate the MDT measurement collection for a subscriber whose IMSI is 2440511223344. ZT7U:IMSI=2440511223344;
For mcRNC: a) Make an SSH session to mcRNC IP address (/SSH) and start SCLI session. b) Disable MDT measurement collection with the following command. delete radio-network subs-trace deactivate-trace imsi
Command syntax: Parameter
Description
Value
imsi
This parameter specifies the IMSI of the subscriber for whom MDT measurement collection is to be deactivated. This parameter is mandatory.
A decimal value with a maximum of 15 digits.
Command example: Example below shows how to deactivate the MDT measurement collection for a subscriber whose IMSI is 2440511223344. delete radio-network subs-trace deactivate-trace imsi 2440511223344
2
Make an HTTPS connection to OMS IP address and open OMS Element Manager.
3
Navigate to the RNFC-1 object. Option
Description
Use Quick Access text Enter the distinguished name (DN) of the parent RNC box object and RNFC-1, for example: RNC-37/RNFC-1 Use Topology tree
Browse through the topology, for example: RNC-37 ► RNFCs ► RNFC-1
4
Configure the RNFC-1 object to disable IMSI-based MDT measurements collection. a) Right-click on the RNFC-1 object and select Edit Parameters. b) In the Handover Measurement tab, set the value of the IMSIMeasMDTEnabled parameter to Disabled (0). c) Select Apply button to save the changes.
Result
328
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
The RAN2496: Minimization of Drive Tests feature is deactivated for a particular subscriber based on IMSI or deactivated entirely for the RNC.
6.2 RAN2443: BTS Resource Utilization Monitoring 6.2.1 Description of RAN2443: BTS Resource Utilization Monitoring Introduction to the feature The RAN2443: BTS Resource Utilization Monitoring feature introduces counters to monitor resource utilization inside a BTS on the following levels: • • • •
BTS level Local Cell Group (LCG) level Flexi System Module level (new aggregation level) HSPA Scheduler level (new aggregation level)
This is in addition to existing counters that enable monitoring resource utilization in BTS on the level of subunits (SUs), throughput, Processing Sets, and users.
6.2.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits The feature benefits the operator in the following ways: •
•
6.2.1.2
Improves monitoring possibilities to show how baseband resources commissioned on the BTS and the LCG level are assigned to the actual BTS hardware modules, and thus proactively react to possible congestions. Introduces the resource monitoring on additional levels – per Flexi System Modules and per HSDPA/HSUPA Scheduler.
Requirements Software requirements Table 148: Software requirements lists the software required for this feature. RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
BTS Flexi
Flexi Lite BTS
RU50 EP1
Support not required
Support not required
Support not required
WN9.1
Not planned
Table 148
Issue: 01F
Support not required
OMS 3.1
Software requirements
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
WN9.1
NetAct 8 EP2 (NetAct 15)
Support not required
Support not required
Support not required
Support not required
DN09146788
329
Performance monitoring features
RU50 Feature Descriptions and Instructions
Hardware requirements This feature requires Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF.
6.2.1.3
Functional description The RAN2443: BTS Resource Utilization Monitoring introduces the following counters: •
counters in measurement M5006 for local cell group (LCG) level monitoring: – – – – – – – – – – – – – – –
•
new and modified counters in measurement M5008 for BTS level monitoring: – – –
•
– – – – – – –
average/maximum number of HSDPA users average/maximum HSDPA throughput average/maximum HSUPA throughput available HSDPA throughput available HSDPA users average/maximum number of HSUPA users available HSUPA throughput available HSUPA users
counters in new measurement M5012 for Flexi System Module (FSM) level monitoring: – – – – –
330
number of licensed R99 channel elements (R99CEs) number of configured PIC subunits (SUs) number of configured SUs for HS-FACH
counters in new measurement M5011 for scheduler monitoring: –
•
allocated HSDPA subunits average/maximum number of HSDPA users average/maximum number of HSUPA users average/maximum HSDPA throughput average/maximum HSUPA throughput number of available HSDPA users number of available HSUPA users number of available HSDPA throughput number of available HSUPA throughput average/maximum HSDPA Processing Set utilization average/maximum HSUPA Processing Set utilization hardware resource utilization class 1-6 (0-100%) number of R99 plus HSUPA overlapping subunits Average R99 used from overlapping R99 and HSUPA SUs Average HSUPA used from overlapping R99 and HSUPA SUs
maximum used subunits for R99 maximum used subunits for HSUPA number of available R99 SUs number of available HSUPA SUs number of configured HSUPA SUs
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
– – –
Performance monitoring features
number of configured PIC SUs number of configured SUs for HS-FACH in uplink number of used CCCH SUs
Correction of the counters presented in the Table 150: Modified counters is related to: •
•
•
•
6.2.1.4
In counters: M5006C0 to M5006C20 The modification is related to the change of sampling period from 5 seconds to 5,12 seconds. In counters: M5006C27 to M5006C38 In the BTS it is possible to license more HSPA users than it is supported by the HW capacity. The counters are modified, by changing the denominator. The smaller value is taken to the counters: either the number of Licensed HSDPA/HSUPA users, or the HW capacity limit of HSDPA/HSUPA users. In counters: M5008C22 - M5008C27 In the BTS it is possible to license more HSPA users and more HSPA throughput than it is supported by the HW capacity. The counters are modified, by changing the denominator. The smaller value is taken to the counters, either the number of Licensed HSDPA/HSUPA throughput, or the HW capacity limit of HSDPA/HSUPA throughput. Also the change in calculating each sample was made – now the average value of the users, throughput, and hardware (only in the HSUPA cases) instead of maximum is taken. In counters: M5008C40 - M5008C41 In the BTS it is possible to license more HSPA users than it is supported by the HW capacity. The counters are modified, by changing the denominator. The smaller value is taken to the counters: either the number of Licensed HSDPA/HSUPA users, or the HW capacity limit of HSDPA/HSUPA users.
System impact Interdependencies between features The following features are need to be activated before activation of the RAN2443: BTS Resource Utilization Monitoring feature: • •
The following features are related to the RAN2443: BTS Resource Utilization Monitoring feature: • • •
RAN912: License based BTS channel capacity RAN2262: Flexi Multiradio System Modules RAN2887: CCCH Processing Set
Impact on interfaces This feature impacts the following interfaces: • •
Issue: 01F
BTS-RNC/OMS-NetAct: the two new measurements (M5011 and M5012) with new counters are transferred from BTS to NetAct via external O&M interface. BTS-BTS Manager: the two new measurements (M5011 and M5012) with new counters are transferred from BTSOM to BTS Manager via O&M interface.
DN09146788
331
Performance monitoring features
RU50 Feature Descriptions and Instructions
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 The RAN2443: BTS Resource Utilization Monitoring feature introduces large number of new counters, which impact the OMS server and NetAct. The scope of impact depends on the total number of BTSs reporting to single OMS server/NetAct server.
6.2.1.5
RAN2443: BTS Resource Utilization Monitoring management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms There are no alarms related to this feature.
Measurements and counters Table 149: New counters lists counters introduced with this feature. Table 149
332
New counters
Counter ID
Counter name
Measurement
M5006C45
ALLOCATED HSDPA SUBUNITS IN LCG
WBTS R99 HW Resource (WBTS)
M5006C46
NUMBER OF R99 PLUS HSUPA OVERLAPPING SUBUNITS IN LCG
WBTS R99 HW Resource (WBTS)
M5006C47
AVERAGE USED R99 FROM OVERLAPPING WBTS R99 HW Resource SUBUNITS IN LCG (WBTS)
M5006C48
AVERAGE USED HSUPA FROM OVERLAPPING SUBUNITS IN LCG
Test case 1. Checking M5008C48 - M5008C50 counters Purpose The purpose of this test case is to verify PM counters M5008C48 - M5008C50 with a related configuration. Test environment Required network elements: operational radio network and core network. Before you start Make sure Flexi BTS is fully operational. BTS configuration: FSME+FSME+FRGP+FRGP: F444-x-85-1TX-2RX: UOC 4+4+4 20W/C Parameters: • • • • • • • •
2*LCG 8*BTS HSDPA processing set2 HSDPA scheduler 4+4+4+4 99*BTS HSUPA processing set1 configured 1520*R99 CEs configured 1 PIC pool for every LCG HS-FACH step is 1 in LCG1 HS-FACH step is 3 in LCG2
M5008C48: LICENSED R99 CES IN BTS (LICENSED_R99CE_WBTS) The counter provides information about number of licensed R99 CE in BTS. With this counter operator can monitor the final amount of R99 CEs licenses that can be utilized in the BTS. LICENSED_R99CE_WBTS = MIN (amount of R99 CE licenses; HW capacity available for R99 traffic) Amount of R99 CE licenses = R99 CE + R99 capacity of hybrid HSUPA Processing Set [Flexi Rel2]: HW capacity available for R99 traffic = (BB capacity of BTS) - (PIC resources) - (HS-FACH resources) - (resources allocated for HSDPA) - (resource steps) [Flexi Rel3]: HW capacity available for R99 traffic = (BB capacity of BTS) - (PIC resources) - (HS-FACH resources) - (resources allocated for HSDPA) - (resource steps) HS-FACH resources = MAX (pre-reserved HS-FACH resources; allocated HS-FACH resources)
g
The M5008C48 counter is updated when the HW or the licensed capacity changes in BTS. M5008C49: CONFIGURED PIC SUBUNITS IN BTS (CONF_PIC_SU_WBTS) The counter provides information about all resources allocated for PIC in the BTS. With this counter operator can monitor PIC allocation in BTS.
338
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Performance monitoring features
The M5008C49 counter is updated when PIC pools configuration is changing. M5008C50: CONFIGURED HS-FACH SUBUNITS IN BTS (CONF_HSFACH_SU_WBTS) The counter provides information about all resources allocated for HS-FACH in the BTS. With this counter operator can monitor HS-FACH allocation in BTS.
g
The M5008C50 counter is updated when HS-FACH reservation/allocation changes in BTS. Test execution
1
Start the measurement M5008 using the RNW Measurement Management application in the Application Launcher.
2
Make sure that BTS has been 'On Air' over two full hours (for example from 11:59 to 14:00) and that counters are available in RNW Measurement Presentation GUI of OMS. Expected outcome: Counters are available and all PM counters’ values are ‘0’.
3
Make sure that BTS is commissioned according to Before you start section (Parameters). Expected outcome: BTS is running normally after commissioning.
4
After the measurement data has been collected, use the RNW Measurement Presentation GUI of OMS to verify PM counters. Expected outcome: All supported PM counters’ values are correct (in accordance with formulas from Before you start section).
g 6.2.2.2
You can also use BTS Site Manager to view counters’ values.
Test case 2. Checking M5006C63 and M5006C57 counters Purpose The purpose of this test case is to verify M5006C63 and M5006C57 PM counters with a related configuration. Test environment Required network elements: operational radio network and core network.
Issue: 01F
DN09146788
339
Performance monitoring features
RU50 Feature Descriptions and Instructions
Before you start Make sure Flexi BTS is fully operational. BTS configuration: FSME+FSME+FRGP+FRGP: F444-x-85-1TX-2RX: UOC 4+4+4 20W/C Parameters: • • • • • • •
2*LCG 8*BTS HSDPA processing set2 HSDPA scheduler 4+4+4+4 90% licensed HSDPA users for LCG1 and 10% for LCG2 99*BTS HSUPA processing set1 HSUPA license for all LCG is 50% configured 1520*R99 CEs
M5006C63: AVAILABLE HSDPA THROUGHPUT IN LCG (LCG_AVAIL_HSDPA_THR) The counter provides information about maximum available HSDPA throughput which can be allocated in LCG, with this counter operator can monitor the limitation of HSDPA throughput amount in each LCG separately.
[Flexi Rel2] HSDPA_scheduler_throughput = MIN (Licensed_HSDPA_throughput ; Allocated_HSDPA_Scheduler_throughput) [Flexi Rel3] HSDPA_scheduler_throughput = MIN (Licensed_HSDPA_throughput ; Allocated_HSDPA_Scheduler_throughput) Licensed_HSDPA_throughput - is the maximum licensed HSDPA throughput based on the sum of HSDPA Processing Sets licenses. Allocated_HSDPA_Scheduler_throughput - is the maximum allocated throughput of given HSDPA scheduler, which is calculated based on throughput steps commissioned or (re)calculated by Telecom for each HSDPA scheduler.
g
The M5006C63 counter is updated when LCG HW capacity, LCG configuration, HSDPA cell amount in LCG, or HSDPA PS licenses amount is changed. M5006C57: AVAILABLE NUMBER OF HSDPA USERS IN LCG (LCG_AVAIL_HSDPA_USERS) The counter provides information about maximum amount of available HSDPA users which can be allocated in LCG, with this counter operator can monitor the limitation of HSDPA users amount in each LCG separately. LCG_AVAIL_HSDPA_USERS = MIN (Licensed_HSDPA_users ; HSDPA_user_scheduler_capacity) Licensed_HSDPA_users - is the maximum number of HSDPA users in LCG calculated based on HSDPA Processing Sets licenses available in LCG.
340
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
HSDPA_user_scheduler_capacity - is the sum of all HSDPA schedulers' users capability in LCG, which are calculated based on the amount of allocated HSDPA schedulers and the limitation of maximum amount of HSDPA users of each scheduler. Only HSDPA schedulers, to which LCG has access, are taken into account. On Flexi Rel2 it means only HSDPA schedulers allocated on the SM on which LCG is HSPA capable.
g
The M5006C57 counter is updated when LCG HW capacity, LCG configuration, or HSDPA PS licenses amount is changed. Test execution
1
Start the measurement M5006 using the RNW Measurement Management application in the Application Launcher.
2
Make sure that BTS has been 'On Air' over two full hours (for example from 11:59 to 14:00) and that counters are available in RNW Measurement Presentation GUI of OMS. Expected outcome: Counters are available and all PM counters’ values are ‘0’.
3
Make sure that BTS is commissioned according to Before you start section (Parameters). Expected outcome: BTS is running normally after commissioning.
4
After the measurement data has been collected, use the RNW Measurement Presentation GUI of OMS to verify PM counters. Expected outcome: All supported PM counters’ values are correct (in accordance with formulas from Before you start section).
g 6.2.2.3
You can also use BTS Site Manager to view counters’ values.
Test case 3. Checking M5011C8 and M5011C11 counters Purpose The purpose of this test case is to verify M50011C8 and M5011C11 PM counters with a related configuration. Test environment Required network elements: operational radio network and core network. Before you start Make sure Flexi BTS is fully operational. BTS configuration: FSME+FSME+FRGP+FRGP: F444-x-85-1TX-2RX: UOC 4+4+4 20W/C Parameters: • • •
2*BTS HSUPA processing set1 HSUPA license for all LCG is 50% configured 100*R99 CEs
M5011C8: Available number of HSUPA users in scheduler (SCHED_AVAIL_HSUPA_USERS) The counter provides information about maximum amount of HSUPA users, which can be served by the HSUPA scheduler. With this counter operator can monitor the limitation of HSUPA user amount in each scheduler separately. Avail_Hsupa_Users_Scheduler = MIN (Licensed_HSUPA_users_in_scheduler ; HSUPA_user_scheduler_capacity ; HSUPA_user_HW_capacity ) Licensed_HSUPA_users_in_scheduler - is the maximum number of HSUPA users in Master HSUPA L2 calculated based on HSUPA Processing Set licenses available in Master HSUPA L2. HSUPA_user_scheduler_capacity - is the maximum amount of HSUPA users, which can be handled by HSUPA scheduler. HSUPA_user_HW_capacity - is the HW limitation for maximum HSUPA users. It's calculated as all baseband HW resources, which can be utilized for HSUPA users. Resources utilized for additional CCCH resources, HSDPA allocation, HS-FACH (whole subunit) and PIC is not be counted into it. Subunit capacity is 40 users per subunit in case of SM rel. 2 and 80 users per subunit in case of SM rel. 3.
g
The M5011C8 counter is updated when BTS HW capacity, HSUPA configuration, HSUPA licenses amount is changed. M5011C11: Available HSUPA throughput in Scheduler (SCHED_AVAIL_HSUPA_THR) The counter provides information about maximum available HSUPA throughput in the HSUPA scheduler. Avail_Hsupa_thorughput_Scheduler = MIN (Licensed_HSUPA_throughput_in_scheduler ; HSUPA_throughput_HW_capacity) Licensed_HSUPA_throughput_in_scheduler - is the maximum HSUPA throughput, calculated based on the sum of HSUPA Processing Set licenses, which are available for given HSUPA scheduler. HSUPA_throughput_HW_capacity - is the HW limitation for maximum HSUPA throughput. It's calculated as all baseband HW resources, which can be utilized for HSUPA traffic. Resources utilized for additional CCCH resources, HSDPA allocation, HSFACH (whole subunit) and PIC shall not be counted into it. Maximum HSUPA throughput per subunit can be counted as: • •
11.6 Mbps per one subunit in case of SM rel.2 33 Mbps per one subunit in case of SM rel.3
If only part of a subunit is available, then throughput is counted proportionally: (maximum throughput in subunit * amount of free Resource steps in the subunit/amount of all Resource steps in the subunit).
g 342
The M5011C11 counter is updated when BTS HW capacity, HSUPA configuration, HSUPA licenses amount is changed.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
Test execution
1
Start the measurement M50011 using the RNW Measurement Management application in the Application Launcher.
2
Make sure that BTS has been 'On Air' over two full hours (for example from 11:59 to 14:00) and that counters are available in RNW Measurement Presentation GUI of OMS. Expected outcome: Counters are available and all PM counters’ values are ‘0’.
3
Make sure that BTS is commissioned according to Before you start section (Parameters). Expected outcome: BTS is running normally after commissioning.
4
After the measurement data has been collected, use the RNW Measurement Presentation GUI of OMS to verify PM counters. Expected outcome: All supported PM counters’ values are correct (in accordance with formulas from Before you start section).
g 6.2.2.4
You can also use BTS Site Manager to view counters’ values.
Test case 4. Checking M5012C4 counter Purpose The purpose of this test case is to verify M5012C4 PM counter with a related configuration. Test environment Required network elements: operational radio network and core network. Before you start Make sure Flexi BTS is fully operational. BTS configuration: FSME+FSME+FRGP+FRGP: F444-x-85-1TX-2RX: UOC 4+4+4 20W/C Parameters: • • • • • •
2*LCG 4*BTS HSDPA processing set2 HSDPA scheduler 7+7+7+7 2*BTS HSUPA processing set1 HSUPA license for all LCG is 50% configured 100*R99 CE
M5012C4: The configured HSDPA subunits in FSM (FSM_CONF_HSDPA_SU)
Issue: 01F
DN09146788
343
Performance monitoring features
RU50 Feature Descriptions and Instructions
The counter provides information about amount of configured resources for HSDPA in FSM. With this counter operator can monitor the amount of subunits consumed by HSDPA allocation in given FSM. Allocated subunits is calculated from Subunits_for_HSDPA formula. Subunits_for_HSDPA = Max {Round up ((2 * MIMO cells + non-MIMO cells / 6) + 1 ; Subunits_for_HSDPA_throughput } + number of LCGs * 0.25 where: Subunits_for_HSDPA_throughput - commissioned resources for HSDPA
g
Counter M5012C4 is updated when HSDPA is allocated in FSM (system module startup). Test execution
1
Start the measurement M5012 using the RNW Measurement Management application in the Application Launcher.
2
Make sure that BTS has been 'On Air' over two full hours (for example from 11:59 to 14:00) and that the counters are available in RNW Measurement Presentation GUI of OMS. Expected outcome: Counters are available and all PM counters’ values are ‘0’.
3
Make sure that BTS is commissioned according to Before you start section (Parameters). Expected outcome: BTS is running normally after commissioning.
4
After the measurement data has been collected, use the RNW Measurement Presentation GUI of OMS to verify the PM counter. Expected outcome:The PM counter's value is correct (in accordance with formulas from Before you start section).
g
You can also use BTS Site Manager to view counters’ values.
6.3 RAN2555: Configurable Ranges for User Throughput Counters 6.3.1 Description of RAN2555: Configurable Ranges for User Throughput Counters Introduction to the feature The feature RAN2555: Configurable Ranges for User Throughput Counters enables to overcome current hard coding of ranges for RCPM throughput class counters (existing 13 DL and 5 UL counters). The feature provides configurability option for RCPM throughput counters: • •
344
configurable bins for the 13 existing DL Classes and 5 UL classes, aggregation per data volume in addition to the per session.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
6.3.1.1
Performance monitoring features
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature improves monitoring capabilities by adapting measurements to the operator’s needs.
6.3.1.2
Requirements Software requirements Software requirements lists the software required for this feature.
RAS
Flexi Direct IPA-RNC
mcRNC
OMS
Flexi Multiradio BTS
Flexi Lite BTS
RU50 EP1
Not planned RN8.1
mcRNC4.1
OMS3.1
Support not required
Support not required
Flexi NetAct Multiradio 10 BTS
MSC
SGSN
MGW
UE
Support not required
Support not required
Support not required
Support not required
Support not required
NetAct 8 EP2 (NetAct 15)
Hardware requirements This feature does not require any new or additional hardware.
6.3.1.3
Functional description Functional overview The RAN2555:Configurable Ranges for User Throughput Counters feature enables to overcome current hard coding of ranges for RCPM throughput class counters (existing 13 DL and 5 UL counters). The illustrates the described situation.
Issue: 01F
DN09146788
345
Performance monitoring features
RU50 Feature Descriptions and Instructions
Figure 32
Configurable Ranges for User Throughput Counters
ren
s
ps
Cur
Mb
ps
bps
>8
>84
Mb
8M
bps
4...
4M 2...
1...
512
2M
... 1
bps
Mb
ps
kbp 12 ... 5
256
kbp
128
... 2
56
bps
28
4k
.. 1
.. 6 32.
64.
2k
kbp
.. 3 16.
bps
16
bps 4k
8k
8...
4...
0...
NOW
s
bps
s
kbp
s
tM
ax
Current situation: RCPM t.put counters lose visibility on the high scale of the t.put distribution.
Lost t.put scale, where most of the NEW devices are located for the 4G concept
RAN2555 allows operators to CUSTOMIZE scale distribution for a full visibility, also for future release, allowing a more precise throughput and data volume distributions observation
bps 40.
>84
.. 6
Mb
ps
0M
bps .. 4
0M
bps 36.
30.
.. 3
6M
bps 0M .. 3 25.
bps 24.
.. 2
5M
bps 23.
.. 2
4M
bps 20.
.. 2
3M
bps 0M .. 2 12.
bps .. 1 10.
8...
10
2M
ps Mb
bps 8M 4...
0...
AFTER
4M
bps
EXAMPLE 1
bps ps Mb >84
bps
0M .. 6 40.
36.
.. 4
0M
bps 6M .. 3 30.
bps 0M .. 3 26.
bps 5M .. 2 24.
bps 4M .. 2 23.
bps 3M .. 2 20.
ps Mb 20 8...
bps 8M 6...
bps 6M 4...
bps 4M 2...
0...
2M
bps
EXAMPLE 2
It is possible to configure the ranges for the throughput classes, and the principle of counter updates for the parameters affecting RCPM counter’s behavior. Configurable parameters to provide ranges for the throughput classes Using the RAN2555:Configurable Ranges for User Throughput Countersfeature, when the M1026C38 USER_DL_THRP_DIST_CLASS_5_W counter indicates the PS session throughput between 32...64 kbit/s, it is possible to define this range to, for example, 128...256 kbit/s. Then also other counters ranges must to be adjusted correspondingly, to avoid the overlapping with each other. Configurable parameter to choose the principle of counter updates Without using of the RAN2555: Configurable Ranges for User Throughput Counters feature, the counter corresponding to achieved throughput (within the RCPM throughput class counters functionality) is updated by value 1, when the radio bearer is reconfigured, or released, or some mobility events occurs. The RAN2555: Configurable Ranges for User Throughput Counters feature enables to increment the by the amount of PS data volume transferred during the session counter, instead of updating by value 1.
346
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
6.3.1.4
Performance monitoring features
System impact Interdependencies between features This feature requires the following features: • • •
RAN953: Radio Connection Performance Measurements for RLC Acknowledged Mode RAN190: Radio Connection Performance Measurements for RLC TM and UM and Outer Loop Power Control RAN1188 Pre-Aggregation of RCPM Data in RNC
Impact on interfaces This feature has no impact on interfaces.
Impact on commands There are no commands related to this feature.
Impact on network and network element management tools 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.3.1.5
RAN2555: Configurable Ranges for User Throughput Counters management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms There are no alarms related to this feature.
Measurements and counters There are no new counters related to this feature. Related existing counters lists existing counters related to this feature. Table 152
Issue: 01F
Related existing counters
Counter ID
Counter name
Measurement
M1017C34
USER DL THROUGHPUT DISTRIBUTION - CLASS 1
RCPM RLC
M1017C43
USER DL THROUGHPUT DISTRIBUTION - CLASS 10
RCPM RLC
DN09146788
347
Performance monitoring features
Table 152
RU50 Feature Descriptions and Instructions
Related existing counters (Cont.)
Counter ID
Counter name
Measurement
M1017C50
USER DL THROUGHPUT DISTRIBUTION - CLASS 11
RCPM RLC
M1017C52
USER DL THROUGHPUT DISTRIBUTION - CLASS 13
RCPM RLC
M1026C34
USER DL THROUGHPUT DISTRIBUTION - CLASS 1 FOR WCEL
RCPM RLC WCEL
M1026C43
USER DL THROUGHPUT DISTRIBUTION - CLASS 10 FOR WCEL
RCPM RLC WCEL
M1026C50
USER DL THROUGHPUT DISTRIBUTION - CLASS 11 FOR WCEL
RCPM RLC WCEL
M1026C52
USER DL THROUGHPUT DISTRIBUTION - CLASS 13 FOR WCEL
RCPM RLC WCEL
M1027C34
USER DL THROUGHPUT DISTRIBUTION - CLASS 1 FOR RNC
RCPM RLC RNC
M1027C43
USER DL THROUGHPUT DISTRIBUTION - CLASS 10 FOR RNC
RCPM RLC RNC
M1027C50
USER DL THROUGHPUT DISTRIBUTION - CLASS 11 FOR RNC
RCPM RLC RNC
M1027C52
USER DL THROUGHPUT DISTRIBUTION - CLASS 13 FOR RNC
RCPM RLC RNC
M1017C53
USER UL THROUGHPUT DISTRIBUTION - CLASS 1
RCPM RLC
M1017C57
USER UL THROUGHPUT DISTRIBUTION - CLASS 5
RCPM RLC
M1026C53
USER UL THROUGHPUT DISTRIBUTION - CLASS 1 FOR WCEL
RCPM RLC WCEL
M1026C57
USER UL THROUGHPUT DISTRIBUTION - CLASS 5 FOR WCEL
RCPM RLC WCEL
M1027C53
USER UL THROUGHPUT DISTRIBUTION - CLASS 1 FOR RNC
RCPM RLC RNC
M1027C57
USER UL THROUGHPUT DISTRIBUTION - CLASS 5 FOR RNC
RCPM RLC RNC
Key performance indicators There are no key performance indicators related to this feature.
Parameters New parameters lists parameters introduced with this feature.
348
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 153
Issue: 01F
Performance monitoring features
New parameters
Full name
Abbreviated name
Configure Ranges for RCPM User Throughput Counters enabled
ConfigurableRCPMtputEnable RNFC d
RCPM throughput counters aggregation Level
RCPMtputAggregationLevel
RNC
RCPM DL throughput class 01 to class 02 range limit
RCPMtputDLCl01to02Range
RNC
RCPM DL throughput class 02 to class 03 range limit
RCPMtputDLCl02to03Rangel
RNC
RCPM DL throughput class 03 to class 04 range limit
RCPMtputDLCl03to04Range
RNC
RCPM DL throughput class 04 to class 05 range limit
RCPMtputDLCl04to05Range
RNC
RCPM DL throughput class 05 to class 06 range limit
RCPMtputDLCl05to06Range
RNC
RCPM DL throughput class 06 to class 07 range limit
RCPMtputDLCl06to07Range
RNC
RCPM DL throughput class 07 to class 08 range limit
RCPMtputDLCl07to08Range
RNC
RCPM DL throughput class 08 to class 09 range limit
RCPMtputDLCl08to09Range
RNC
RCPM DL throughput class 09 to class 10 range limit
RCPMtputDLCl09to10Range
RNC
RCPM DL throughput class 10 to class 11 range limit
RCPMtputDLCl10to11Range
RNC
RCPM DL throughput class 11 to class 12 range limit
RCPMtputDLCl11to12Rangeg
RNC
RCPM DL throughput class 12 to class 13 range limit
RCPMtputDLCl12to13Range
RNC
RCPM UL throughput class 01 to class 02 range limit
RCPMtputULCl01to02Range
RNC
RCPM UL throughput class 02 to class 03 range limit
RCPMtputULCl02to03Range
RNC
DN09146788
Managed object
349
Performance monitoring features
Table 153
RU50 Feature Descriptions and Instructions
New parameters (Cont.)
Full name
Abbreviated name
Managed object
RCPM UL throughput class 03 to class 04 range limit
RCPMtputULCl03to04Range
RNC
RCPM UL throughput class 04 to class 05 range limit
RCPMtputULCl04to05Range
RNC
Modified parameters There are no modified parameters related to this feature.
6.3.1.6
Sales information Table 154
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
RNC LK
6.3.2 Activating RAN2555: Configurable Ranges for User Throughput Counters Purpose Follow this procedure to activate RAN2555: Configurable Ranges for User Throughput Counters. For more information on the feature, see the RAN2555: Configurable Ranges for User Throughput Counters feature description. Before you start Ensure that at least one of the RCPM measurements M1017, M1026 or M1027 are active in the system, and producing the data for the following counters accordingly: • • •
Ensure that the following features are activated: • •
350
RAN953: Radio Connection Performance Measurements for RLC Acknowledged Mode RAN190: Radio Connection Performance Measurements for RLC TM and UM and Outer Loop Power Control
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
RAN1188 Pre-Aggregation of RCPM Data in RNC - required for the M1026 and M1027 measurements. If the RAN1188: Pre-Aggregation of RCPM Data in RNC feature is not active, it is possible to use the M1017 measurement with the default settings.
•
Restart of the RNC is not required after activation of this feature. This procedure does not require cell locking. 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: OMS Element Manager Application Launcher
• •
Ensure that RAN2555: Configurable Ranges for User Throughput Counters license exists and the feature state is ON.
g
This is valid only for IPA-RNC and mcRNC. Flexi Direct RNC is not under license control. To set the feature state to ON, use the following command: For IPA-RNC: ZW7M:FEA=5169:ON; For mcRNC: set license feature-mgmt code 0000005169 feature-admin-state on
1
Open the OMS Element Manager.
2
Go to the Topology Tree View. Select: Network Management ► Topology Tree View
3
Expand the RNFC object.
4
Configure the RNFC object. a) From the drop-down menu select Edit ► Edit Parameters. b) Set the ConfigurableRCPMtputEnabled parameter value to Enabled.
5
Save the changes. a) Click the Apply button.
Issue: 01F
DN09146788
351
Performance monitoring features
RU50 Feature Descriptions and Instructions
6
Expand the RNC object.
7
Configure the RNC object. a) From the drop-down menu select Edit ► Edit Parameters. b) Check and configure throughput aggregation level with the parameter RCPMtputaggreLevel .
8
Save the changes. a) Click the Apply button.
9
Expand the RNC object.
10 Configure the RNC object. a) From the drop-down menu select Edit ► Edit Parameters. b) Check and configure UL/DL throughput Class range parameters.
11 Save the changes. a) Click the Apply button.
Expected outcome Above counters are getting updated in line with the configured aggregation level, and UL/ DL class boundaries. Unexpected outcome Above counters are not getting updated properly.
6.3.3 Verifying RAN2555: Configurable Ranges for User Throughput Counters Purpose Follow this procedure to verify that the activation of this feature is successful. Before you start Make sure you have access to the Fault Management application in the Application Launcher. Ensure that at least one of the RCPM measurements M1017, M1026 or M1027 are active in the system, and producing the data for the following counters accordingly: • •
The RAN2555: Configurable Ranges for User Throughput Counters feature should be activated. Throughput aggregation level is configured with the RCPMtputaggreLevel parameter. UL and DL class throughput ranges are configured
1
Check the above counter values after the next measurement interval.
Expected outcome The particular User throughput Class counter is getting updated when RLC PDU gross throughput falls inside the configured range for this class. If the RCPMtputaggreLevel parameter value is Aggregation per session or Aggregation per data volume, the class throughput counter is getting updated by the amount of transferred downlink, or uplink data in 1000 bytes, transferred by the sessions where the RLC PDU gross throughput falls inside this class range.
6.3.4 Deactivating RAN2555: Configurable Ranges for User Throughput Counters Purpose Follow this procedure to deactivate RAN2555: Configurable Ranges for User Throughput Counters. Before you start Ensure that the RAN2555: Configurable Ranges for User Throughput Counters feature is activated.
1
Open the OMS Element Manager.
2
Go to the Topology Tree View. Select: Network Management ► Topology Tree View
3
Expand the RNFC object.
4
Configure the RNFC object. a) From the drop-down menu select Edit ► Edit Parameters. b) Set the ConfigurableRCPMtputEnabled parameter value to Disabled.
5
Save the changes. a) Click the Apply button.
Issue: 01F
DN09146788
353
Performance monitoring features
RU50 Feature Descriptions and Instructions
Expected Outcome Class throughput counter values are getting updated by the number of data transfer sessions where the RLC PDU gross throughput falls inside the default range for this class.
6.3.5 Testing RAN2555: Configurable Ranges for User Throughput Counters
g
Follow the procedure below to verify that the activation of the RAN2555: Configurable Ranges for User Throughput Counters feature has been successful.
g 6.3.5.1
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.
Testing environment Purpose The purpose of test case 1 is to verify if the counters are updated appropriately based on “aggregation per session". The purpose of test case 2 is to verify if the counters are updated appropriately based on “aggregation per data volume”. Network elements For the test case, the following network elements must be at least on the following software level: • • • • • • •
one RNC one GOMS one NodeB, Flexi BTS with Multimode System Module one CS CN one PS CN one UE: Release99 upwards, the new model is preferred. UE throughput monitoring tool ( e.g. DU meter)
Before you start Ensure that the following feature licenses are activated: • • •
•
RAN953: Radio Connection Performance Measurements for RLC Acknowledged Mode RAN190: Radio Connection Performance Measurements for RLC TM and UM and Outer Loop Power Control RAN1188 Pre-Aggregation of RCPM Data in RNC - required for the M1026 and M1027 measurements. If the RAN1188: Pre-Aggregation of RCPM Data in RNC feature is not active, it is possible to use the M1017 measurement with the default settings. RAN2555: Configurable Ranges for User Throughput Counters.
Ensure that the following parameters are set to default value:
354
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
• • • • • • • • • • • • • • • • •
6.3.5.2
Performance monitoring features
ConfigurableRCPMtputEnabled to Enabled RCPMtputDLCl01to02Range to 4kbps RCPMtputDLCl02to03Range to 8kbps RCPMtputDLCl03to04Range to 16kbps RCPMtputDLCl04to05Range to 32kbps RCPMtputDLCl05to06Range to 64kbps RCPMtputDLCl06to07Range to 128kbps RCPMtputDLCl07to08Range to 256kbps RCPMtputDLCl08to09Range to 512kbps RCPMtputDLCl09to10Range to 1000kbps RCPMtputDLCl10to11Range to 2000kbps RCPMtputDLCl11to12Range to 4000kbps RCPMtputDLCl12to13Range to 8000kbps RCPMtputULCl01to02Range to 250kbps RCPMtputULCl02to03Range to 500kbps RCPMtputULCl03to04Range to 1000kbps RCPMtputULCl04to05Range to 1500kbps
Test execution - case 1 Purpose The purpose of this test case is to verify if the counters are updated appropriately based on “aggregation per session" Before you start • •
Follow the prerequisites in Testing environment. Set the value for the following RNC parameter: –
RCPMtputAggregationLevel to Aggregation per session
1
Open the RNW Measurement Management application.
2
Activate the M1017, M1026, M1027 measurements in the RNW and BTS measurements window. The following counters are related to this feature: • • •
For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. 3
Make a PS NRT call. For example, use UL/DL throughput 57/57 kbps, FTP service or HTTP downloading. The 57/57 throughput is just one example. Testing may vary depending on the throughput.
Issue: 01F
DN09146788
355
Performance monitoring features
RU50 Feature Descriptions and Instructions
a) Monitor the call gross throughput. b) Keep the call stable (no state change). c) Wait for the download to complete and continue to the next step.
4
Open the RNW Measurement Presentation application. For details on using the RNW Measurement Presentation application, see Viewing measurement data stored in OMS in Managing and viewing RNC measurements.
5
Check if the value for the following M1017C38, M1017C53, M1026C38, M1026C53, M1027C38, M1027C53 counters has increased. The counters mentioned in the step 5 are only examples based on assumption that throughput is 57 kbps If aggregation level is per session, the counter is updated appropriately when the data transfer session throughput matches.
6
Set the RCPMtputDLCl05to06Range parameter to 35k and the RCPMtputULCl01to02Range parameter to 35k.
7
Repeat steps 3 and 4.
8
Check if the value for the following M1017C39, M1017C54, M1026C39, M1026C54, M1027C39, M1027C54 counters has increased. The counters mentioned in the step 8 are only examples based on assumption that throughput is 57 kbps If aggregation level is per session, the counter is updated appropriately when the data transfer session throughput matches.
9
Restore the parameters to default after testing.
Expected outcome The counters are updated appropriately based on “aggregation per session”
6.3.5.3
Test execution - case 2 Purpose The purpose of this test case is to verify if the counters are updated appropriately based on “aggregation per data volume” Before you start • •
Follow the prerequisites in Testing environment. Set the value for the following RNC parameter: –
356
RCPMtputAggregationLevel to Aggregation per data volume
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
1
Open the RNW Measurement Management application.
2
Activate the M1017, M1026, M1027 measurements in the RNW and BTS measurements window. The following counters are related to this feature: • • •
For details on using the RNW Measurement Management application, see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. 3
Make a PS NRT call. For example, use UL/DL throughput 57/57 kbps, FTP service or HTTP downloading. The 57/57 throughput is just one example. Testing may vary depending on the throughput. a) Monitor the call gross throughput. b) Keep the call stable (no state change). c) Wait for the download to complete and continue to the next step.
4
Open the RNW Measurement Presentation application. For details on using the RNW Measurement Presentation application, see Viewing measurement data stored in OMS in Managing and viewing RNC measurements.
5
Check if the value of the following M1017C38, M1017C53, M1026C38, M1026C53, M1027C38, M1027C53 counters has increased. The counters mentioned in the step 5 are only examples based on assumption that throughput is 57 kbps. If aggregation level is per data volume, the counter is updated appropriately when the data transfer session throughput matches.
6
Set the RCPMtputDLCl05to06Range parameter to 35k and the RCPMtputULCl01to02Range parameter to 35k.
7
Repeat steps 3 and 4.
8
Check if the value of the following M1017C38, M1017C53, M1026C38, M1026C53, M1027C38, M1027C53 counters has increased. The counters mentioned in the step 8 are only examples based on assumption that throughput is 57 kbps. If aggregation level is per data volume, the counter is updated appropriately when the data transfer session throughput matches.
Issue: 01F
DN09146788
357
Performance monitoring features
RU50 Feature Descriptions and Instructions
For details on using the RNW Measurement Presentation application, see Using the RNW Measurement Management Application in Managing and viewing RNC measurements. 9
Restore the parameters to default after testing.
Expected outcome The counters are updated appropriately based on “aggregation per data volume”
6.4 RAN2930: IMSI-based Call Monitoring 6.4.1 Description of RAN2930: IMSI-based Call Monitoring Introduction to the feature Troubleshooting solutions available before RU50 EP1 have had the following drawbacks: 1. Provide too little information on Control Plane messaging (Subscriber trace functionality based on 3GPP TS 32.421) which is not sufficient for troubleshooting majority of problems. 2. Require capturing of Control Plane messaging for all calls in RNC in order to extract monitoring for needed calls (RAN L3 Data Collector and Analyzer) which generate heavy amount of data (several TBytes per day) and require high performance dedicated HW to store and process the data. 3. Wherein the root cause of the problem lies outside Control Plane, for example in Transport or User Plane, additional troubleshooting methods and tools are engaged, such as monitoring data for all calls in units handling user plane and RAN interfaces tracing with Wireshark. Those limitations result in heavy effort needed currently in capturing, extracting and analyzing individual calls. The RAN2930: IMSI- based Call Monitoring feature allows the operator to start the UE monitoring from L3 Data collector by specifying the calls (via their IMSIs) and planes to be monitored (For IPA-RNC, among Control, User and Transport Planes; for mcRNC, only Control Plane can be monitored). Monitored data can then be loaded into L3 Data analyzer for analysis. Monitored data is adequate and small enough to provide inputs on possible error causes.
6.4.1.1
Benefits End-user benefits Fast troubleshooting RNC call related issues, due to one time collection of all needed data related to certain call.
Operator benefits Operator can monitor multiple calls (Test mobiles) without extra hardware. •
358
For IPA-RNC, just one Ethernet cable connection to O&M network of the RNC is needed.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
•
6.4.1.2
Performance monitoring features
For mcRNC, one Ethernet cable to an IP-switch connected to SFP port on BCN modules. Or if megamon setup is existing already, the same could be utilized.
Requirements Software requirements Table 155: Software requirements lists the software required for this feature. Table 155
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
RU50 EP1
Not planned RN8.1
mcRNC4.1
Not planned Support not Support required not required
Flexi Lite BTS
Flexi 10 BTS
NetAct
MSC
SGSN
Support not required
Support not required
Support not Support not Support not Support not required required required required
MGW
Flexi BTS
UE
Support not required
Hardware requirements This feature does not require additional hardware.
6.4.1.3
Functional description Functional overview As the number of connected users per RNC and end-user data rates continue to grow, so does the complexity in being able to troubleshoot problems related to individual calls. Typical use cases for troubleshooting individual calls include (based on 3GPP TS 32.421 Subscriber and equipment trace; Trace concepts and requirements): • • • • • •
g
Issue: 01F
Multivendor UE validation: check how different vendor's UEs are working Subscriber complaint: check how the subscriber's services are working in order to find out the reason for the complaint Malfunctioning UE: when the operator suspects that a UE is not working according to the specifications Checking radio coverage on a particular geographical area Testing a new feature Fine-tuning and optimization of algorithms/procedures RAN2930 monitoring is supported in Serving RNC only. Monitoring of Drift RNC is not supported.
DN09146788
359
Performance monitoring features
Figure 33
RU50 Feature Descriptions and Instructions
Overview of RAN2930: IMSI-based Call Monitoring
In IPA-RNC, this feature introduces collection of Control, User, and Transport planes monitoring data for individual calls based on given IMSI numbers. In mcRNC, this feature introduces collection of Control planes monitoring data for individual calls based on given IMSI numbers. The data capturing is done with the help of the L3 Data Collector running on a standard Windows PC, and connected remotely to the monitored RNC. The data processing and analysis is done with the L3 Data Analyzer running on the same or on a different machine from the L3 Data Collector. The L3 Data Analyzer has the capability of analyzing Control, User and Transport Plane monitored data.
g
RAN2930 monitoring is supported in Serving RNC only. Monitoring of Drift RNC is not supported. The main benefit of this feature is that it allows a small size of the monitored data while providing comprehensive monitored data content for individual monitored calls. RAN2930 can be used in independently and simultaneously with standard L3 Data Collector monitoring.
360
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Performance monitoring features
Neither end-user communication content, that is end-user speech and data, nor messages related to any other call(s) (uninterested calls) is collected by this feature. Data that could reveal customer identity such as the IMSI, the end user or the remote server IP addresses is encrypted at the RNC using a configurable encryption key. The same key is required for analyzing the monitored data at the L3 Data Analyzer tool. Monitored data content 1. Control Plane in control plane processing units (ICSU in RNC2600 and USCP in mcRNC): •
DMX messages from most of call handling program families
2. User Plane in user plane processing units (DMPG/DSP in RNC2600, not supported in mcRNC in this release): • • • • •
Protocol headers on Iu-PS: GTP-U Protocol headers on Iu-CS: RTP, RTCP (not in RNC2600) and Iu-CS UP Protocol headers on Iub: FP, MAC, RLC and PDCP Internal messages related to L3-L2 interfaces L2 internal protocol interfaces (such as RLC-MAC), internal data (such as scheduling info), minor and severe errors, exceptions
3. Transport Plane in transport plane processing units (NPGE in RNC2600, supported only via a separate L3 Data Collector session in mcRNC in this release): • • •
Protocol headers on Iu-PS: outer IP, UDP, GTP-U, inner IP, inner TCP/ICMP/UDP Iu-CS: IP/UDP/RTP/IuUP headers, IP/UDP/RTCP full packet Iub: IP/UDP/FP headers and MAC/RLC headers of the first PDU
Site configuration • •
6.4.1.4
In RNC2600, the monitored data collection is performed via O&M connection to RNC. In mcRNC, it's required to install Ethernet switch onsite as the monitored data collection is done via one SFP port in each BCN box. Existing Megamon/L3Analyzer installed solution can be re-used.
System impact Interdependencies between features Operations causing high OMU load, for example RAN2446 / TN38 Rnclogcol log collection or file compress/uncompress operations, can cause pausing of RAN2930 monitorings.
Impact on network and network element management tools No impact.
Impact on system performance and capacity No impacts to KPIs. CPU loads on monitored units will increase to maximum 5%.
Issue: 01F
DN09146788
361
Performance monitoring features
6.4.1.5
RU50 Feature Descriptions and Instructions
RAN2930: IMSI-based Call Monitoring management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference Documentation.
Alarms There are no alarms related to this feature.
Measurements and counters There are no measurements and counters related to this feature.
Key performance indicators There are no key performance indicators related to this feature.
Parameters There are no parameters related to this feature.
6.4.1.6
Sales information Table 156
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
RNC LK
6.4.2 Activating RAN2930: IMSI-based Monitoring on IPA-RNC 6.4.2.1
Configuring NPEG(P) towards OMU If NPGE is used instead of NPGE(P), use the physical IP address. In the commands, use PHY or P instead of LOG or L. The number of internal IPoAs to be configured is equal to the number of NPGEP pairs on the RNC. For example, the IPA-RNC has 4 NPGEP pairs (8 NPGEPs). If there are WBTSs connected to all of these NPGEPs, this means we have to configure an IFAI interface towards the OMU for each pair of these NPGEs because in effect we do not know which WBTS the IMSI we are monitoring will move to next if the user is mobile configure. So here, there will be 4 internal IPoAs for these 4 NPGEP pairs.
362
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
Before you start Figure 34
Site solution deployment for IPA-RNC
This does not require any additional cables to the NPGEs. However, from external monitoring tool machine, one ethernet cable is sufficient to connect to the DCN. It is sufficient to have one interface card on the monitoring machine In this case, the user needs to login/directly use the external monitoring tool machine to monitor the IPA-RNC. If a second interface card is available at the external monitoring tool machine, then that could be used for using the external monitoring tool remotely. Figure 35
1
IP interfaces between units in the IPA-RNC
Configure TCP/IP ATM interface for internal use at the IFAI interface of the NPGE(P) towards ATM interface of the OMU. ZQMC:NPGEP,0,L:IFAI4:OMU,0,L:AA0:;
2
Configure IFAI interface at NPGE(P) with destination IP as that of the OMU. ZQRN:NPGEP,0:IFAI4,:10.10.10.5(IFAI4),L:24:10.10.10.6:; For NPGE, use: ZQRN:NPGE,0:IFAI4,:10.10.10.5(IFAI4),P:24:10.10.10.6:;
Issue: 01F
DN09146788
363
Performance monitoring features
3
RU50 Feature Descriptions and Instructions
Configure AA0 (ATM) network interface at OMU with destination IP as that of NPGE(P). ZQRN:OMU,0:AA0,N:10.10.10.6,L:24:10.10.10.5(IFAI4):;
4
Interrogate network status to check whether there is already an IP configured from OMU to O&M. ZQRS:OMU,0; Check the output whether the foreign address is that of the O&M (indicated as BSO&M) with state as ESTABLISHED. The Local address is the OMU’s IP address in the output.
6.4.2.2
Configuring EL0 of OMU towards L3 Data Collector (OPTIONAL) If there is an IP configured from OMU to O&M, this step is not necessary. Before you start Check step 2.1.4 of Configuring NPEG(P) towards OMU to verify OMU’s O&M IP address. Use existing OMU’s O&M IP address. If not, continue with steps. 1
Configure EL0 (Ethernet interface) of OMU towards the external monitoring tool. If IP address from OMU to O&M is not configured, configure it with the following command:ZQRN:OMU,:EL0:10.58.239.114 L:32;
6.4.2.3
Configuring GIVAXI/givClient
1
Verify that the deployed givaxi version is the latest one supporting RAN2930: IMSI-based Monitoring: • •
ZDDS;ZSXP:GIV ZWQV:OMU,0:GIV;
Result GIVAXI1X.PAC 6.14-0 14/07/23 PLAENVCB.PAC 14.6-0b.
2
Check Givaxi port status. ZQRS:OMU,0; Result The output must include: The output must include: UNIT: OMU-0 Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address State tcp 0 0 *.8021 LISTEN
364
DN09146788
Foreign Address *.*
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
If not displayed correctly, execute the following command: ZWOC:2,2093,002; Wait until port 8021 status shows LISTEN. It takes approximately 20 seconds.
6.4.2.4
Installing licenses
1
To set the feature state to ON, use the following command: ZW7M: FEA=:ON; The following features need to be turned on: Table 157
g 6.4.2.5
Type
Code
Object Name
Feature
0000005261
IMSI-based Call Monitoring
SW Licence Key SI
RU00552
IMSI-based Call Monitoring Test LK
Software SI
RU00551.T
IMSI-based Call Monitoring LTU
SW Licence Key SI
RU00551
IMSI-based Call Monitoring LK
The feature code should be added to the command.
Installing L3 Data Collector
1
6.4.2.6
Licenses for RAN2930: IMSI-based Monitoring
See RNC L3 Trace Analyzer/Viewer Tool Description in NOLS.
Authorizing Pre-Shared Key (PSK) From GIVAXI1X version 3.1-0 onwards, it is required that PSK authentication is successfully completed before the solution works. This requires that the same PSK is administered in both the external monitoring tool and IPA-RNC.
1
Set the Pre-Shared Key (PSK). The (AES256 crypted) shared key (256bit) must be set by Q4-mml. 256bits/8=32 bytes so the key must be 32 bytes long. ZQ4A:GIVAXIPSK,S:K:H:; Example >ZQ4A:GIVAXIPSK,S:K:H:; ENTER KEY(MAX 64 HEXADECIMAL DIGITS): 1234567890ABCDEFFEDCBA09876543211234567890ABCDEFFEDCBA0987654321
Issue: 01F
DN09146788
365
Performance monitoring features
6.4.2.7
RU50 Feature Descriptions and Instructions
Configuring MSGMONPSK for data encryption
1
For data encryption key authentication, use the following command: ZQ4A:MSGMONPSK,S:K:H; Example ENTER KEY(MAX 64 HEXADECIMAL DIGITS): 1234567890123456789012345678901234567890123456789012345678901234
6.4.2.8
Configuring static IP route to external monitoring tool Create a static route from NPGE(P) (with gateway IP being that of OMU’s AA0 interface) to the external monitoring tool. The destination IP address with netmask depends on the external monitoring tool machine’s IP address.
1
Create a static route from NPGE(P) via gateway AA0 interface to external monitoring tool. ZQKC:NPGEP,0: 10.58.239.0,24:10.10.10.6:LOG:;
2
Enable IP forwarding for both OMUs towards the external monitoring tool. ZQRT:OMU,0:IPF=YES; ZQRT:OMU,1:IPF=YES;
No configuration needed for transfer of UP and CP monitoring data as those involve DMX message based communication.
6.4.2.9
Configuring site routers If there are site routers between RNC and external monitoring tool, static routes to both NPGE and External Monitoring Tool side need to be configured on site routers. Commands to configure the site routers depend on the type of router: Cisco, Huawei, or Juniper. Without the static route configurations, site router will drop the packets with destination to NPGEP. Also, configure the routing table at the External Monitoring Tool workstation and provide the first hop site router’s IP address instead of the OMU’s IP address.
1
Cisco3750G(config)#ip route 1.1.1.0 255.255.255.0 2.2.2.1 Example NPGE IFAI 1.1.1.1/24 ---- OMU EL 2.2.2.1/24 ----- 2.2.2.2/24 cisco 3.3.3.2/24 ------ 3.3.3.1/24 Emil Packets with destination NPGE to be sent to 2.2.2.1 but no static route is needed with destination Emil 3.3.3.0/24 because they are in same subnet. Cisco3750G(config)#ip route 1.1.1.0 255.255.255.0 2.2.2.1
Example
366
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
NPGE IFAI 1.1.1.1/24 ---- OMU EL 2.2.2.1/24 ----- 2.2.2.2/24 cisco1 3.3.3.2/24 ------ 3.3.3.1/24 cisco2 4.4.4.1 --- 4.4.4.2 Emil Packets with destination as 1,1,1,0/24 to be sent to 2.2.2.1 Cisco1(config) towards NPGE #ip route 1.1.1.0 255.255.255.0 2.2.2.1
Packets towards 4.4.4.0/24 to be sent to 3.3.3.1 Cisco1(config) towards Emil: #ip route 4.4.4.0 255.255.255.0 3.3.3.1
Packets towards 1.1.1.0/24 to be sent to 3.3.3.2 Cisco2 towards NPGE ip route 1.1.1.0 255.255.255.0 3.3.3.2
Cisco2 towards Emil is not needed as they are in same subnet.
6.4.2.10
Configuring external monitoring tool (alternative to DHCP) Before you start
1
As an alternative to DHCP, assign an IP address to the external monitoring tool workstation. Linux ip address add 2.2.2.2/24 dev eth0 Microsoft Windows Figure 36
Issue: 01F
Assigning IP address to external monitoring tool workstation
DN09146788
367
Performance monitoring features
2
RU50 Feature Descriptions and Instructions
For the external monitoring tool, configure the routing table so that all packets sent to NPGE(P) (IFAIx) are sent via gateway EL0/EL1 interface on OMU or via site router. Example Linux ip route add 10.10.10.0/24 via 2.2.2.10 dev eth0 Microsoft Windows route -p ADD 10.10.10.0 MASK 255.255.255.0 10.58.239.114
6.4.2.11
Verifying IP configuration
1
Ping from NPGE(P) to external monitoring tool. ZQRX:NPGE,0:IP=10.58.239.142:PING;
2
Ping to NPGE(P) from external monitoring tool. Ping 10.10.10.5
Result Ping is successfully received from either NPGE(P) or external monitoring tool. If not, execute tracert from either side to check where the packets are getting lost or are looping. Possibilities are that the site routers might not have been configured properly or static routes are not present. Pinging between NPGE and OMU must also work fine. If there are no site routers between external monitoring tool and OMU, pinging between them can be checked as well.
6.4.3 Verifying RAN2930: IMSI-based Monitoring on IPA-RNC 6.4.3.1
Verifying RAN2930: IMSI-based call monitoring on IPA-RNC Follow this procedure to verify that this feature has been activated successfully.
1
Verify that the Pre-shared key has been set. ZQ4L:; Result EXECUTION STARTED KEY NAME -------GIVAXIPSK MSGMONPSK
368
KEY TYPE -------PRE-SHARED PRE-SHARED
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
6.4.4 Verifying RAN2930: IMSI-based Monitoring on external monitoring tool 6.4.4.1
Verifying RAN2930: IMSI-based call monitoring on external monitoring tool Follow this procedure to verify that this feature has been configured correctly on the external monitoring tool. Check Message Encrypt option because for RAN2930: IMSIbased call monitoring on external monitoring tool feature encrypt is mandatory.
1
Open the Connect to givaxi window.
2
Add NE in Connections tab. Enter either OMU IP or mmonext@CFPU-0 IP depending on the controller, user name/password, and Pre-Shared Key.
3
Select the switch to IMSI monitoring data set option for the data set.
4
Modify the default connections for mcRNC and IPA-RNC as needed by providing either OMU IP or mmonext@CFPU-0 IP depending on the controller, user name, password, and PSK (administered at the RNC).
5
Check that the Connection status is Connected. Figure 37
Issue: 01F
Connection status in IPA-RNC
DN09146788
369
Performance monitoring features
Figure 38
6
7
g
Connection status in mcRNC
Retain the default profiles for Control Plane that have been selected. Figure 39
IPA-RNC: Control Plane default profiles
Figure 40
mcRNC: Control Plane default profiles
(Only for IPA RNC) If User Plane monitoring is needed, create a profile for User plane in the USUP profiles with the User Plane filters as necessary: Not supported in mcRNC4.1. Figure 41
370
RU50 Feature Descriptions and Instructions
IPA-RNC: User Plane monitoring
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
8
Performance monitoring features
In the IMSI profiles tab, provide the list of IMSIs to be monitored. It accepts a string literal in the format: IMSI=,IMSI=,...,IMSI= Example: IMSI=0123456789012,IMSI=0123456789,IMSI=012345
9
Other values are optional and can be provided if known. Choose the IMSI profile created in the connections tab.
10 (Only for IPA RNC) TP Profiles, note that the IMSI in TP profiles must the same with the one in IMS profiles. IF types should be IPoA interface between OMU and NPGE(P).
g
Not supported in mcRNC4.1. Figure 42
IMSI in TP profile for IPA-RNC
11 Select CP (mandatory), IMSI (mandatory), UP profiles and TP profiles as needed.
g
Issue: 01F
UP and TP monitorings are not supported in mcRNC4.1. Figure 43
IPA-RNC connected with CP profile, US UP profile, TP profile, and IMSI profile
Figure 44
mcRNC connected with CP profile and IMSI profile
DN09146788
371
Performance monitoring features
RU50 Feature Descriptions and Instructions
12 Click on Connect/Fetch Units and verify the progress in the Unit table. 13 Start the calls for the needed IMSIs. 14 Stop the call, wait until the throughput drops to 0kbps after the call is released, then disconnect monitoring. If the disconnect option is selected in Emil even while the call monitoring is in progress, all monitored data collected in the buffers (that has not been sent out of the RNC) is dropped and monitoring is stopped. 15 Monitored data from each plane is saved into its own file. 16 Load these files to the Emil for decoding. Result 1. 2. 3. 4.
Available units on the RNC that can be monitored are displayed in the Unit table. Monitoring throughput from the monitored units keeps getting refreshed. Collected monitored data loaded into Emil must be decoded. Control, User and Transport plane data for a call gets loaded into their own Emil windows.
The user initiated legacy pause/resume functionality from External Monitoring Tools shall work this way: From Emil: 1. Start CP+UP monitoring. 2. Make the call, monitoring ongoing. 3. Click pause all units on Emil. Monitoring will be paused even though the connection to all units are holding on . Receive rate drops to 0 kbps in Emil. 4. Resume the monitoring.The CP and UP data continue receiving. 5. Release the call. 6. Once monitoring throughput drops to 0kbps, disconnect from Emil to stop the monitoring. From megamon: 1. 2. 3. 4. 5. 6.
Start Monitoring for IMSI1. Proceed call with call 1 from IMSI1. Release the call, wait till monitoring throughput for the call drops to 0kbps. Pause monitoring, Megamon closes existing output-files. Resume monitoring, Megamon creates a new output-file. Proceed with a new call 2 from IMSI2, start getting monitored data for call 2 in the new output file. 7. Release the call, wait till monitoring throughput for the call drops to 0kbps. 8. Stop/Pause the monitoring by disconnecting megamon.
372
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
Performance monitoring features
In the Megamon case, if call1 is not released in step 3, but only after step 4, then when monitoring is resumed and call2 is started, the new output file will still have some UP monitored data from call1(of course, along with call2’s data).
6.4.5 Deactivating RAN2930: IMSI-based Monitoring on IPA-RNC 6.4.5.1
Deactivating RAN2930: IMSI-based call monitoring in IPA-RNC Follow this procedure to deactivate this feature.
1
Remove the RAN2930 configured network interface from the OMU towards the external monitoring tool. ZQRG:OMU,0:EL0:;
2
Remove the configured TCP/IP ATM internal interface of NPGE(P) towards OMU. ZQMD:INT:NPGE,0:IFAI4::OMU,0,AA0;
3
Remove IFAI interface at NPGE(P). ZQRG:NPGEP,0:IFAI4,:10.10.10.5; Or ZQRG:NPGE,0:IFAI4,:10.10.10.5;
4
Remove the static route from NPGE(P) to the external monitoring tool. For static route from NPGE(P) via AA0 to Emil use the following command: ZQKA:; Example < ZQKB; LOADING PROGRAM VERSION 2.72-0 RNC
IPA2800
2014-07-25
17:18:22
INTERROGATED STATIC ROUTES
UNIT DESTINATION SESSION ID -------- -----------------------OMU-0 DEFAULT ROUTE NPGE-0 DEFAULT ROUTE NPGE-0 10.56.17.0/24
Delete the pre-shared key using this command: ZQ4D:GIVAXIPSK; ZQ4D:MSGMONPSK;
Issue: 01F
DN09146788
373
Performance monitoring features
g
RU50 Feature Descriptions and Instructions
Deleting the PSK impacts also legacy monitoring. 6
Set the feature state to OFF. ZW7M: FEA=:OFF;
6.4.6 Activating RAN2930: IMSI-based Monitoring on mcRNC 6.4.6.1
Configuring IP connection at mcRNC Before you start If Emil IP is in a different subnet than the one configured in mcRNC, then route configuration is needed in the switch. Otherwise, route configuration is not needed. This needs a 1GE cable from the SFP port (eg. SFP22) of each BCN to the switch. From external monitoring tool machine, one Ethernet cable is sufficient to connect to the switch. It is sufficient to have one interface card on the external monitoring tool machine. In this case, the user needs to login/directly use the external monitoring tool machine to monitor the RNC. If a second interface card is available at the external monitoring tool machine, then that could be used for using the external monitoring tool remotely. IP switch is needed (at least 8 port on mcRNC side and one on the External Monitoring Tool side). As an example, 24*1Gbit/s + 2*10Gbit/s. Figure 45
374
Site solution deployment for mcRNC
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
1
Performance monitoring features
Configure megamon. add troubleshooting megamon network 192.10.XX.0/24 port sfp20
2
Set megamon port enable. set troubleshooting centralized-monitoring administrate ifport ENABLE
3
Set Pre-Shared Key (PSK). set troubleshooting centralized-monitoring administrate if-psk abcdef1234567890abcdef1234567890abcdef1234567890abcdef12345678 90 Figure 46
4
PSK for mcRNC
Set preshared key for opening the call-based monitoring message data (msgmon-psk). set troubleshooting centralized-monitoring administrate msgmon-psk abcdef1234567890abcdef1234567890abcdef1234567890abcdef12345678 90
5
Verify status. show troubleshooting centralized-monitoring administration info Example Administration information: System ID PSK for EXT interface PSK for opening data Activation code for TP Port status Remote IP1 Remote IP2 Remote IP3
Verify that the deployed Givaxi version is the latest one supporting the RAN2930: IMSI-based Monitoring. rpm -qa | grep -i ss_ildiag fsversioninfo /opt/nsn/SS_ILDiagnostic/bin/givclient
Issue: 01F
DN09146788
375
Performance monitoring features
2
RU50 Feature Descriptions and Instructions
Check that Givaxi is running correctly and is waiting for external tool to connect. netstat -taunp | grep giv Example # netstat -taunp | grep giv tcp 0 0 192.10.11.4:8021 LISTEN 7229/givclient
6.4.6.3
0.0.0.0:*
Installing licenses for mcRNC
1
To set the feature state to ON, use the following command: set license feature-mgmt id feature-admin-state on The following features need to be turned on: Table 158
g 6.4.6.4
Licenses for RAN2930: IMSI-based Monitoring
Type
Code
Object Name
Feature
0000005261
IMSI-based Call Monitoring
SW Licence Key SI
RU00552
IMSI-based Call Monitoring Test LK
Software SI
RU00551.T
IMSI-based Call Monitoring LTU
SW Licence Key SI
RU00551
IMSI-based Call Monitoring LK
The feature code should be added to the command. In mcRNC, the code should form a 10-digit number, so it should be preceded with zeros.
Installing L3 Data Collector
1
See RNC L3 Trace Analyzer/Viewer Tool Description in NOLS.
6.4.7 Verifying RAN2930: IMSI-based Monitoring on mcRNC 6.4.7.1
Verifying RAN2930: IMSI-based call monitoring on mcRNC Follow this procedure to verify that this feature has been activated successfully.
376
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
1
Connect to CFPU-0 through O&M network.
2
Show centralized-monitoring in troubleshooting. show troubleshooting centralized-monitoring administration info Result CFPU-0@RNC-427 16:37:55 +0800]
[2014-05-19
Administration information: System ID PSK for EXT interface PSK for opening data
3
: 427 : SET : SET
modified 14/05/15 modified 14/05/19
Verify troubleshooting configuration for external monitoring tool connectivity from all nodes of the mcRNC is available. show troubleshooting megamon Result Port group configuration: Port group Physical port Admin state --------------- -------------------- ----------mmon-1 LMP-1-1-1:sfp22 up mmon-2 LMP-1-2-1:sfp22 up Total count: 2 Ethernet Interface and IP Address configuration: Owner Port group Interface Address ---------- --------------- ------------- -----------------/CFPU-0 mmon-1 mmonext 192.10.10.4/24 /CFPU-1 mmon-2 mmonext 192.10.10.5/24 /CSPU-0 mmon-1 mmonext 192.10.10.6/24 /CSPU-1 mmon-2 mmonext 192.10.10.13/24 /CSPU-2 mmon-1 mmonext 192.10.10.9/24 /CSPU-3 mmon-2 mmonext 192.10.10.16/24 /EIPU-0 mmon-1 mmonext 192.10.10.8/24 /EIPU-1 mmon-2 mmonext 192.10.10.15/24 /EIPU-2 mmon-1 mmonext 192.10.10.12/24 /EIPU-3 mmon-2 mmonext 192.10.10.19/24 /USPU-0 mmon-1 mmonext 192.10.10.7/24 /USPU-1 mmon-2 mmonext 192.10.10.14/24 /USPU-2 mmon-1 mmonext 192.10.10.10/24 /USPU-3 mmon-2 mmonext 192.10.10.17/24 /USPU-4 mmon-1 mmonext 192.10.10.11/24 /USPU-5 mmon-2 mmonext 192.10.10.18/24 Total count: 16
Issue: 01F
DN09146788
377
Performance monitoring features
RU50 Feature Descriptions and Instructions
6.4.8 Verifying RAN2930: IMSI-based Monitoring on external monitoring tool 6.4.8.1
Verifying RAN2930: IMSI-based call monitoring on external monitoring tool Follow this procedure to verify that this feature has been configured correctly on the external monitoring tool. Check Message Encrypt option because for RAN2930: IMSIbased call monitoring on external monitoring tool feature encrypt is mandatory.
1
Open the Connect to givaxi window.
2
Add NE in Connections tab. Enter either OMU IP or mmonext@CFPU-0 IP depending on the controller, user name/password, and Pre-Shared Key.
3
Select the switch to IMSI monitoring data set option for the data set.
4
Modify the default connections for mcRNC and IPA-RNC as needed by providing either OMU IP or mmonext@CFPU-0 IP depending on the controller, user name, password, and PSK (administered at the RNC).
5
Check that the Connection status is Connected. Figure 47
378
Connection status in IPA-RNC
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 48
6
7
g
Connection status in mcRNC
Retain the default profiles for Control Plane that have been selected. Figure 49
IPA-RNC: Control Plane default profiles
Figure 50
mcRNC: Control Plane default profiles
(Only for IPA RNC) If User Plane monitoring is needed, create a profile for User plane in the USUP profiles with the User Plane filters as necessary: Not supported in mcRNC4.1. Figure 51
Issue: 01F
Performance monitoring features
IPA-RNC: User Plane monitoring
DN09146788
379
Performance monitoring features
8
RU50 Feature Descriptions and Instructions
In the IMSI profiles tab, provide the list of IMSIs to be monitored. It accepts a string literal in the format: IMSI=,IMSI=,...,IMSI= Example: IMSI=0123456789012,IMSI=0123456789,IMSI=012345
9
Other values are optional and can be provided if known. Choose the IMSI profile created in the connections tab.
10 (Only for IPA RNC) TP Profiles, note that the IMSI in TP profiles must the same with the one in IMS profiles. IF types should be IPoA interface between OMU and NPGE(P).
g
Not supported in mcRNC4.1. Figure 52
IMSI in TP profile for IPA-RNC
11 Select CP (mandatory), IMSI (mandatory), UP profiles and TP profiles as needed.
g
380
UP and TP monitorings are not supported in mcRNC4.1. Figure 53
IPA-RNC connected with CP profile, US UP profile, TP profile, and IMSI profile
Figure 54
mcRNC connected with CP profile and IMSI profile
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
12 Click on Connect/Fetch Units and verify the progress in the Unit table. 13 Start the calls for the needed IMSIs. 14 Stop the call, wait until the throughput drops to 0kbps after the call is released, then disconnect monitoring. If the disconnect option is selected in Emil even while the call monitoring is in progress, all monitored data collected in the buffers (that has not been sent out of the RNC) is dropped and monitoring is stopped. 15 Monitored data from each plane is saved into its own file. 16 Load these files to the Emil for decoding. Result 1. 2. 3. 4.
Available units on the RNC that can be monitored are displayed in the Unit table. Monitoring throughput from the monitored units keeps getting refreshed. Collected monitored data loaded into Emil must be decoded. Control, User and Transport plane data for a call gets loaded into their own Emil windows.
The user initiated legacy pause/resume functionality from External Monitoring Tools shall work this way: From Emil: 1. Start CP+UP monitoring. 2. Make the call, monitoring ongoing. 3. Click pause all units on Emil. Monitoring will be paused even though the connection to all units are holding on . Receive rate drops to 0 kbps in Emil. 4. Resume the monitoring.The CP and UP data continue receiving. 5. Release the call. 6. Once monitoring throughput drops to 0kbps, disconnect from Emil to stop the monitoring. From megamon: 1. 2. 3. 4. 5. 6.
Start Monitoring for IMSI1. Proceed call with call 1 from IMSI1. Release the call, wait till monitoring throughput for the call drops to 0kbps. Pause monitoring, Megamon closes existing output-files. Resume monitoring, Megamon creates a new output-file. Proceed with a new call 2 from IMSI2, start getting monitored data for call 2 in the new output file. 7. Release the call, wait till monitoring throughput for the call drops to 0kbps. 8. Stop/Pause the monitoring by disconnecting megamon.
Issue: 01F
DN09146788
381
Performance monitoring features
g
RU50 Feature Descriptions and Instructions
In the Megamon case, if call1 is not released in step 3, but only after step 4, then when monitoring is resumed and call2 is started, the new output file will still have some UP monitored data from call1(of course, along with call2’s data).
6.4.9 Deactivating RAN2930: IMSI-based Monitoring on mcRNC 6.4.9.1
Deactivating RAN2930: IMSI-based call monitoring in mcRNC Follow this procedure to deactivate this feature.
1
Connect to CFPU-0 through the O&M network. delete troubleshooting megamon This deletes assigned IP address for each node of a BCN and also deletes the assigned SFP port and subnet for transferring monitoring data from the BCN
2
Set the feature state to OFF. set license feature-mgmt id feature-admin-state off
6.5 RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio 6.5.1 Description of RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio Introduction to the feature The RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature enables mcRNC to have counters for round-trip time (RTT) and packet loss ratio (PLR).
6.5.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature benefits the operator as follows: • •
6.5.1.2
Operators are able to monitor the real-time condition of the network, which leads to a quick reaction to potential service degradations. The introduction of the feature eliminates the acquisition of additional hardware or measurement equipment to monitor the network.
Requirements Software requirements Table 159: Software requirements lists the software required for this feature.
382
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 159
Performance monitoring features
Software requirements
RAS
Flexi Direct
IPA-RNC
RU50 EP1
Not relevant
Flexi Lite Support not required
Flexi Direct RNC
OMS
BTS Flexi
Available in mcRN4.1 earlier release
Support not required
Not relevant
Support not required
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
Support not required
Support not required
Support not required
Support not required
Support not required
Support not required
g
mcRNC
The same functionality is available in IPA-RNC with RAN2402: Traffica IP Reports for RTT and Packet Loss Ratio feature.
Hardware requirements This feature requires Traffica tool to be operational.
Other requirements To use RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature, RAN1900: IP Transport Network Measurement feature must be activated. For more details on software and hardware requirements for Traffica, see the Traffica documentation.
6.5.1.3
Functional description The RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature enables Traffica to monitor Iub, Iu, and Iur IP-based interfaces in real time to support mcRNC. With this feature, Traffica provides the following measurement data reports in a 60second interval: • •
round-trip time (RTT) packet loss ratio (PLR)
The RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature uses the Two-Way Active Measurement Protocol (TWAMP) in mcRNC. TWAMP is used to measure and monitor IP network conditions between two network elements. The RNC serves as the TWAMP sender, as shown in Figure 55: Measuring RTT and PLR with TWAMP, which collects IP networks quality of service (QoS) measurement data from the network. The TWAMP sender session generates test traffic based on the IETF defined TWAMP protocol RFC5357. The RNC analyzes and the related measurements data results are provided to the Traffica tool. The BTS on the other end serves as User Datagram Protocol (UDP) echo server or TWAMP responder.
Issue: 01F
DN09146788
383
Performance monitoring features
Figure 55
RU50 Feature Descriptions and Instructions
Measuring RTT and PLR with TWAMP
BTS UDP echo server OR TWAMP responder
RNC TWAMP sender
Traffica
Router UDP echo server
SGSN
RNC UDP echo server
The measurement reports are only visible in the Traffica tool based on the report type that the RNC provides. These measurement reports are used to assess the quality and performance of the IP-based transport network for each QoS class independently as indicated by the Differentiated Services Code Point (DSCP). For more information, see RAN1900: IP Transport Network Measurement and RAN2255: IP Transport Measurement Initiated from RNC and Flexi Direct BTS feature.
6.5.1.4
System impact Interdependencies between features The RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature depends on RAN2255: IP Transport Network Measurement Initiated from RNC and Flexi Direct BTS and RAN1900: IP Transport Network Measurement features.
Impact on interfaces A Traffica report type is introduced to indicate RTT and PLR to support mcRNC.
Impact on network and network element management tools The feature enhances the Traffica tool functions so that IP-related monitoring can be performed both on the core network (CN) and radio access network (RAN) interfaces.
g
The Traffica tool must be updated to support the new report. The same Traffica that is supported in RAN2402: Traffica IP Reports for RTT and Packet Loss Ratio feature is needed.
Impact on system performance and capacity This feature has no impact on system performance or capacity.
384
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
6.5.1.5
Performance monitoring features
RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio management data For information on alarm, counter, key performance indicator, and parameter, see Reference documentation.
Alarms There are no alarms related to this feature.
Measurements and counters The following are the counters that are reported for each monitored IP-transport path at 60-second interval: • • • • •
average round-trip time minimum round-trip time maximum round-trip time number of sent TWAMP measurement request packets number of lost TWAMP measurement packets
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table 160: Parameters lists the parameters that are introduced in the IP plan interface with this feature. Table 160
Parameters
Full name
Abbreviated name
Managed object
Destination IP address
destIpAddr
TWAMPS
Destination UDP port
destIpPort
TWAMPS
DSCP value for test traffic
dscpVal
TWAMPS
Packet sending frequency
freqOfPacket
TWAMPS
IP TWAMP sender session ID
ipSenderSessId
TWAMPS
Length of the test packet
lenOfPacket
TWAMPS
Source IP address
srcIpAddr
TWAMPS
Session state
stateOfsession
TWAMPS
Commands The following sCLI commands are used to create TWAMP sessions: • •
Issue: 01F
add networking monitoring twamp sender to start TWAMP monitoring delete networking monitoring twamp sender to stop TWAMP monitoring
DN09146788
385
Performance monitoring features
6.5.1.6
Sales information Table 161
g
RU50 Feature Descriptions and Instructions
Sales information
BSW/ASW
SW component
License control in network element
ASW NetAct
RAN
Not defined
The license control of RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature comes from the Traffica tool.
6.5.2 Activating RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio Purpose Follow this procedure to activate RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature. For more information on the feature, see RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature description. Before you start Restarting the mcRNC is not required after the activation of this feature. This procedure does not cause downtime and can be executed any time of the day. Make sure that the mcRNC is up and running, and neighboring network elements (NEs) are integrated with the mcRNC. Check that there is traffic in the network and that you have a working network connection. This procedure requires the enabling of the Traffica interface in the mcRNC. For more information, see RAN1150: RNC Support for Traffica, Feature Activation Manual. Make sure that the correct Traffica server SW release is installed—that is, the version that supports the mcRNC release that you are using and the IP Two Way Active Measurement Protocol (TWAMP) report type. The same Traffica server SW release that is used in RAN2402: Traffica IP Reports for RTT and Packet Loss Ratio. The RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature is licensed via the Traffica tool and does not require licensing via the mcRNC. For measurements on the Iub interface, the TWAMP responder or the User Datagram Protocol (UDP) echo server functionality must be activated in the BTS. For more information, see Activating RAN1900: IP Transport Network Measurement. Steps
1
If the UDP echo server function is not applied, establish the TWAMP reflector session in the neighboring NE (optional). With the TWAMP reflector, more accurate round-trip time (RTT) values can be calculated. To activate the TWAMP reflector for mcRNC, see the related activation instruction sections in this document.
386
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
2
Performance monitoring features
Configure the IP TWAMP sender session in the mcRNC. a) Open the SCLI session Open the Secure SCLI Window application on the Application Launcher. Alternatively, use any other configured MMI client. b) Create the IP TWAMP sender session in the mcRNC Apply SCLI command add networking monitoring twamp using mcRNC QNUP IP as the source address and BTS user plane IP as the destination address.
g
RTT can be measured using the TWAMP session at any logical mcRNC interface. c) Set the session state as active Example configuration: • • • •
g
user plane termination recovery group: QNUP-0 source IP-address of QNUP: 10.15.1.162 destination IP-address: 10.15.1.100 destination UDP port: 5018 For remote reflector, use UDP Port: 7 for echo, 1000 for IPA-RNC, mcRNC, and Flexi Direct RNC TWAMP reflector, and 5018 for BTS reflector.
The BTS TWAMP reflector port number is always 5018. Therefore, when using the RNC as TWAMP sender and the BTS as TWAMP reflector, destination port 5018 will be used. • • • • • •
DSCP code: 34 packet length: 100 bytes alarm threshold for 1 minute average RTT: 500 ms alarm threshold for 15-minute packet loss ratio (0.01%): 5 (this means 5% packet loss ratio) packet sending frequency: 1 packet per second session state: ON
Based on these values, the command to be used is: add networking monitoring twamp sender owner /QNUP-0 session-id 1 src-ip-addr 10.15.1.162 dest-ip-addr 10.15.1.100 port 5018 packetfrequency 1 packet-length 100 dscp 34 plr-threshold 5 rttthreshold 500 session-state on
3
When using NetAct, configure the TWAMP session via IP plan interface to create TWAMPS object class instances.
4
In Traffica, activate the measurement data collection from the mcRNC. In Traffica, subscribe to the IP TWAMP report type from the mcRNC.
g
Issue: 01F
For information on how to start monitoring IP measurements in the BTS, see Activating RAN1900: IP Transport Network Measurement.
DN09146788
387
Performance monitoring features
RU50 Feature Descriptions and Instructions
The TWAMP session is independent from Traffica reporting. If the TWAMP session is activated in the mcRNC, it stays active even if the Traffica does not subscribe to the IP TWAMP report type from the mcRNC. In this case, the statistical data produced by the TWAMP session is discarded internally in the mcRNC. Also, if Traffica subscribes to the report but there are no TWAMP sessions configured, the Traffica does not get any data. Expected outcome The RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature is activated.
6.5.3 Verifying RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio Purpose Follow this procedure to verify that RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature is activated successfully. Before you start Make sure that the mcRNC is up and running and neighboring network elements (NEs) are integrated with the mcRNC. Check that there is traffic in the network and that you have a working network connection. This procedure requires the enabling of the Traffica interface in the mcRNC. For more information, see RAN1150: RNC Support for Traffica, Feature Activation Manual. Make sure that the correct Traffica server SW release is installed—that is, the version that supports the mcRNC release that you are using and the IP Two Way Active Measurement Protocol (TWAMP) report type. Which is the same Traffica server SW release used in RAN2402: Traffica IP Reports for RTT and Packet Loss Ratio. For measurements on the Iub interface, the TWAMP responder or the User Datagram Protocol (UDP) echo server functionality must be activated in the BTS. For more information, see Activating RAN1900: IP Transport Network Measurement. Steps
1
Activate the TWAMP session in the mcRNC and subscribe to the report in Traffica. For more information, see Steps in Activating RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio.
2
Check whether reporting is working—that is, whether the reports are being sent to Traffica.
3
In the RNC Traffica News application, verify that Traffica is receiving the IP TWAMP reports. For information on how to view the IP TWAMP reports in Traffica, see the Traffica documentation.
388
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Performance monitoring features
The TWAMP session is independent from Traffica reporting. If the TWAMP session is activated in the mcRNC, it stays active even if Traffica does not subscribe to the IP TWAMP report type from the mcRNC. In this case, the statistical data produced by the TWAMP session is discarded internally in the mcRNC. Also, if Traffica subscribes to the report but there are no TWAMP sessions configured, Traffica does not get any data. Expected outcome The RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature activation is verified in the mcRNC.
6.5.4 Deactivating RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio Purpose Follow this procedure to deactivate RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature. Before you start Make sure that the mcRNC is up and running and neighboring network elements (NEs) are integrated with the mcRNC. Check that there is traffic in the network and that you have a working network connection. This procedure requires the enabling of the Traffica interface in the mcRNC. For more information, see RAN1150: RNC Support for Traffica, Feature Activation Manual. Steps
1
In Traffica, deactivate the measurement data collection. In Traffica, unsubscribe to the IP TWAMP report type.
2
Open the MMI session. Open the Secure MMI Window application from the application launcher. Alternatively, use any other configured MMI client.
3
Issue: 01F
In the mcRNC, deactivate the TWAMP session.
DN09146788
389
Performance monitoring features
RU50 Feature Descriptions and Instructions
a) If you want to deactivate the TWAMP session completely, delete the IP TWAMP sender session in the mcRNC delete networking monitoring twamp sender session-id 1
This command disables IP measurements and deletes the session configuration stored in the RNC. To enable IP measurements again, you must recreate the TWAMP session. b) If you only want to disable monitoring, put the TWAMP session in OFF state. set networking monitoring twamp sender session-id 1 session-state off
This command only disables IP measurements. Use it if you do not want to lose the session configuration stored in the RNC. You can enable IP measurements again by using this command: set networking monitoring twamp sender session-id 1 session-state on
The TWAMP session is independent from Traffica reporting. If the TWAMP session is activated in the mcRNC, it stays active even if Traffica does not subscribe to the IP TWAMP report type from the mcRNC. In this case, the statistical data produced by the TWAMP session is discarded internally in the mcRNC. Also, if Traffica subscribes to the report but there are no TWAMP sessions configured, Traffica does not get any data. Expected outcome The RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss Ratio feature is deactivated.
390
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
7 RNC solution features 7.1 RAN2251: Automatic mcRNC Resource Optimization 7.1.1 Description of RAN2251: Automatic mcRNC Resource Optimization Introduction to the feature The RAN2251: Automatic mcRNC Resource Optimization feature enables optimal usage of the User Plane and Control Plane resources for the mcRNC's UE-specific Processing Unit (USPU). The multicontroller RNC consists of many multi-core processors called Processing Units. There are several types of Processing Units: CSPU, USPU, EIPU, and CFPU. This feature optimizes the use of hardware resources for the USPU unit (UE specific services). In each USPU unit, there is a Control Plane (CP) and a User Plane (UP) running on different operating systems. In the mcRNC system startup, processor cores are allocated to the Control Plane and User Plane. This feature enables a dynamic core reallocation so that the processor core can be moved from a low-loaded Plane to a highly-loaded Plane in case of an unbalanced load. This feature optimizes resources for Multicontroller RNC HW Rel.2.
7.1.1.1
Benefits End-user benefits This feature benefits the end-user in the following way: • •
better user experience seamless and smooth traffic even if the RNC is highly loaded
Operator benefits This feature benefits the operator in the following way: • • •
7.1.1.2
optimal use of hardware resources in case of unbalanced User Plane and Control Plane load of the USPU unit lower risk of overload situation and thus KPI degradation higher capacity and throughput if Control and User Plane loads are unbalanced
Requirements Software requirements Table 162: Software requirements lists the software required for this feature.
Issue: 01F
DN09146788
391
RNC solution features
RU50 Feature Descriptions and Instructions
Table 162 RAS
Software requirements Flexi Direct
RU50 EP1 Not relevant
IPA-RNC
mcRNC
Not relevant mcRNC 4.1
OMS
BTS Flexi
Flexi Lite
OMS3.1
Support not required
Support not required
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
Support not required
NetAct 8 EP2 (NetAct 15)
Support not required
Support not required
Support not required
Support not required
Hardware requirements This feature requires the Multicontroller RNC HW Rel.2
7.1.1.3
Functional description Functional overview The mcRNC consists of many multi-core processors called Processing Units. There are several types of Processing Units: CSPU, USPU, EIPU, and CFPU. This feature optimizes the use of hardware resources of the USPU unit (UE-specific services) between the User Plane and the Control Plane. UE-specific resources are more dynamic than relatively static Cell-specific resources; therefore, this feature has been implemented for USPU units. In each USPU unit there is a Control Plane (CP) and a User Plane (UP). Both run on different operating systems. During the mcRNC system startup, processor cores are allocated either to the Control Plane or the User Plane. Fixed core allocation is applied without the feature introduction. Dynamic core reallocation is enabled if the feature is activated. The mcRNC consists of multiple Controller Modules, also known as Box Controller Nodes (BCNs). The mcRNC4.1 uses two kinds of controller modules: BCN-A and BCNB. BCN-A contains Octeon+ based add-in cards and BCN-B contains Octeon II based add-in cards. This feature works only for BCN-B (Octeon II) hardware types as Octeon II processor units have more cores and the dynamic core reallocation.
Core reallocation mechanism The mcRNC’s multi-core processors are allocated either to Control Plane or User Plane using a default core allocation in a mcRNC system restart. This feature makes it possible to reallocate between Planes if the loads are unbalanced. A core reallocation from the User Plane to the Control Plane will take place under the following conditions: • •
the CPU load of the Control plane is over high_load_threshold in the whole time period defined by DURATION_TIMES the CPU load of the User Plane is below low_load_threshold in the time period defined by DURATION_TIMES
The core reallocation from the Control Plane to User plane takes place in a similar way. If both the Control Plane and User Plane loads are high, for example, over the value set in the high_load_threshold, the core reallocation cannot take place. Table 163: Thresholds related to RAN2251 feature explains the most important thresholds related to
392
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
this feature. The values of thresholds have been set so that a core reallocation can take place before the overload control mechanism starts to react in the case of an overload situation. Table 163
7.1.1.4
Thresholds related to RAN2251 feature
Name
Meaning
cp_high_load_threshold
A high-load threshold for a CP. The CP can only add a core when its load is above this value.
cp_low_load_threshold
A low-load threshold for a CP. The CP core can only be removed if its load is below this value and its load is still below this value after core removal.
up_high_load_threshold
A high-load threshold for a UMW on SE. If the UMW load is above this value, a UP cannot add additional cores.
up_low_load_threshold
A high-load threshold for a UP. The UP can only add a core when its load is above this value.
DURATION_TIMES
A counter for hysteresis. The core can be moved if a CP is busy and UP is free or CP is free and UP is busy within the duration time.
System impact Interdependencies between features There is no interdependencies with other features.
Impact on interfaces This feature enables to optimize load of Control and User Planes.
Impact on commands The following SCLI commands are affected by this feature: show troubleshooting core-reallocate history
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 provides additional mcRNC capacity in case of an unbalanced resource utilization of the UE-specific Control Plane (USCP) and UE-specific User Plane (USUP). The mcRNC capacity and performance depends on a given traffic profile and processing power of each CPU. The number of cores assigned to the Control Plane or User Plane of the USPU unit can be adjusted based on the actual CPU loads.
Issue: 01F
DN09146788
393
RNC solution features
7.1.1.5
RU50 Feature Descriptions and Instructions
Management data Alarms Table 164: New alarms lists alarms introduced with this feature. Table 164
New alarms
Alarm ID Alarm name 3785
ALL HOT PLUG CORE OF ONE NODE ARE IN INVALID STATE
Table 165: Modified alarms lists alarms modified by this feature. Table 165
Modified alarms
Alarm ID Alarm name 3560
USER PLANE PROCESSING RESOURCE SHORTAGE
Measurements and counters Table 166: Related measurements lists the existing measurements related to this feature. Table 166
Related measurements
Measurement ID Measurement name M2002
CPU Usage Core Level
M2007
CPU Usage Node Level
Key performance indicators There are no key performance indicators related to this feature.
7.1.1.6
Sales information Table 167
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
RNC LK
7.1.2 Activating RAN2251: Automatic mcRNC Resource Optimization Purpose This procedure describes how to activate the RAN2251: Automatic mcRNC Resource Optimization feature.
g
This feature is controlled by a license. For information on managing licenses, see Licensing. Before you start •
394
User must have permission to access SSH client (for example, PuTTY)
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
1
RNC solution features
Install the feature's license on the network element. For instructions on installing the feature's license on the network element, see Installing licenses in the network element in the Managing License-based Features in Multicontroller RNC.
2
Check that the license has been successfully installed. To check that the installed licenses can be found in the network element, enter the following command and check if the license is listed: show license all
3
g
Set the feature's state to ON. The code of this feature is 0000003896. Set the feature's state to ON by executing: set license feature-mgmt code 0000003896 feature-admin-state on
4
Check whether the feature is activated by executing: _nokadmin@CFPU-0 [RNC-38] > show license feature-mgmt code 0000003896 Result The following screen is displayed if the feature is activated correctly: CFPU-0@RNC-38 +0200]
[2014-06-20 10:48:34
Feature Name AutomaticmcRNCResourceOptimization Feature Code Type Admin State + License State = Combined Operational State Feature Description Optimization
: : 0000003896 : on/off : on + on = on : RAN2251 Automatic mcRNC Resource
Result The RAN2251: Automatic mcRNC Resource Optimization feature has been activated.
7.1.3 Verifying RAN2251: Automatic mcRNC Resource Optimization Purpose This procedure describes how to verify if the feature is working properly. To verify that the feature is working properly, do the following:
Issue: 01F
DN09146788
395
RNC solution features
RU50 Feature Descriptions and Instructions
1
Check that core reallocation records are present. Show the core reallocation history on mcRNC when the mcRNC reaches the core moving condition by executing: show troubleshooting core-reallocate history The core reallocation record includes the following information: • • • •
core moving direction (UP-TO-CP or CP-TO-UP) current time the current CPU load of CP and UP (CPU(%)) the core column shows the current state of core deployment in the processing units
Result If no cores have been reallocated, the core reallocation history is empty: Time: 2014-11-06 13:36:37 CPU(%) Core Time Unit name Direction Cause [CP,UP] [CP,UP] Status ------------------- --------- --------- ------ --------- ------- ------Total: 0 COMMAND EXECUTED
If some cores have been reallocated, the core reallocation history contains movement records. The core reallocation history contains data since the last system restart. CFPU-0@RNC-21 +0300]
If a core reallocation takes place many times in one USPU, it is possible that some CPU cores cannot be allocated again and will stay in the invalid status. In this situation, alarm 3785, ALL HOT PLUG CORE OF ONE NODE ARE IN INVALID STATE, is triggered. You need to cancel this alarm after the actions described in the operating instructions of the alarm have been conducted. 2
Check the UPM load status information. show troubleshooting upm status load unit USPU Result This command shows the CPU load of the Control Plane (CP_CPU), User Plane (UP_CPU) and Resource Usage. The output below demonstrates a situation where both CP_CPU and UP_CPU loads of every USPU unit are low and a new core reallocation will not take place. CFPU-0@RNC-21 +0200]
[2014-11-21 15:36:59
Time: 2014-11-21 15:37:00
Unit name --------USPU-0 USPU-1 USPU-2 USPU-3 USPU-4 USPU-5
For the output description, check the manual of SCLI commands by typing ? at the end of the specific SCLI command. 3
Review the counter measurement result. Run the M2002 measurement in the OMS element manager. After a set time, create a measurement presentation and display measurement report. Example of M2002 CPU Usage Core Level measurement from USPU-0 unit shows measurement results M2002 CPU Usage Core Level from the USPU-0 unit for both the Control Plane (FPNODE-USPU-0) and User Plane (FPNODE-USUP-0). If a core reallocation has occurred, you can see it in this measurement. If, for example, a core reallocation occurs from the User Plane to the Control Plane, the new core begins to report its load to the Control Plane (FPNODE-USPU-0) and stops reporting to the User Plane (FPNODE-USUP-0).
398
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
Result Figure 56
Example of M2002 CPU Usage Core Level measurement from USPU-0 unit
7.1.4 Deactivating RAN2251: Automatic mcRNC Resource Optimization Purpose This procedure describes how to deactivate the RAN2251: Automatic mcRNC Resource Optimization feature. To deactivate the feature, do the following:
1
Deactivate the feature. set license feature-mgmt code 0000003896 feature-admin-state off
Issue: 01F
DN09146788
399
RNC solution features
RU50 Feature Descriptions and Instructions
2
Restart all USPU nodes. set has restart force managed-object /QNUSUPProxy
w
User traffic is impacted when the USPU restarts. The time between the reset command and the first call setup on this USPU is about four (4) minutes. 3
Check that no core reallocation was performed. Show the core reallocation history on mcRNC when mcRNC reaches the core moving condition and ensure that no core reallocation was performed. Execute: show troubleshooting core-reallocate history Example Time: 2014-07-02 11:48:55 CPU(%) Core Time Unit name Direction Cause [CP,UP] [CP,UP] Status ------------------- --------- --------- ------ --------- ------- -------
Result The RAN2251: Automatic mcRNC Resource Optimization feature has been deactivated.
7.2 RAN2928: DSP Pool Information in Measurements 7.2.1 Description of RAN2928: DSP Pool Information in Measurements Introduction to the feature Several DSP processes are executed in the RNC to ensure that the usage of the digital signal processor (DSP) is optimized. The main DSP processes are DSP service pooling and DSP measurement. The former enables the optimal use of the DSPs, while the latter provides data on the: • • • • • •
number of calls based on the service type peak number of connections failed connection attempts number of rejected calls number of connected announcements. CPU load, memory usage and processes number of DSPs
The RAN2928: DSP Pool Information in Measurements feature enhances the accuracy of the DSP measurement and improves DSP resource management. This gives the operator more precise statistical information, which is helpful for network analysis and optimization.
400
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
7.2.1.1
RNC solution features
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits Operator has more accurate visibility of the DSP load with this feature. This allows to gain precise measurement data for network analysis and optimization.
7.2.1.2
Requirements Software requirements The following table lists software required for this feature. Table 168
Software requirements
RAS
Flexi Direct
IPA-RNC
mcRNC
OMS
BTS Flexi
Flexi Lite
RU50 EP1
Support not required
RN8.1
Support not required
OMS3.1
Support not required
Support not required
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
Support not required
NetAct 8 EP2 (NetAct 15)
Support not required
Support not required
Support not required
Support not required
Hardware requirements This feature requires RNC2600.
7.2.1.3
Functional description Before the feature is activated The DSP LOAD MEASUREMENT (M617) counters are data from all of the DSPs grouped in the data and macro diversity processor group (DMPG). The measured data provided by M617 is the average DSP load value from the DSPs grouped to one DMPG. See Figure 57: DSP load measurement before the feature activation for an overview of the measurement process:
Issue: 01F
DN09146788
401
RNC solution features
RU50 Feature Descriptions and Instructions
Figure 57
DSP load measurement before the feature activation
DMPG
DSP1
DSP2
M617
DSP Group LoadData
After the feature is activated By activating the RAN2928: DSP Pool Information in Measurements feature the M617 measurement is upgraded to provide single DSP-level data. See Figure 58: DSP load measurement after the feature activation
402
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 58
RNC solution features
DSP load measurement after the feature activation
DMPG
DSP1
DSP2
DSP1 LoadData
DSP2 LoadData
M617
for an overview of the measurement process after the feature activation. The upgraded M617 measurement report contains information related to the DSP service pool. This upgrade gives the user even more accurate load situation overview in different DSP service pools. With this feature activated, the user can improve the efficiency of network analysis and optimization.
7.2.1.4
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 and network element management tools.
Impact on system performance and capacity This feature changes measurement M617 object from DMPG to DSP, so the measurement objects number is doubled. This object measurement increase does not impact on system performance. This feature has no impact on system capacity.
7.2.1.5
RAN2928: DSP Pool Information in Measurements management data For more information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Issue: 01F
DN09146788
403
RNC solution features
RU50 Feature Descriptions and Instructions
Alarms There are no existing alarms related to this feature.
Measurements and counters Table 169: New counters lists counters introduced with this feature: Table 169
New counters
Counter ID Counter name M617C20
Measurement
DSP_SERVICE_POOL_TYPE DSP Load
Key performance indicators There are no existing key performance indicators related to this feature.
Parameters There are no existing parameters related to this feature.
7.2.1.6
Sales information Table 170
Sales information
BSW/ASW
SW component
License control in network element
BSW
RAN
Not defined
7.2.2 Activating RAN2928: DSP Pool Information in Measurements Purpose This chapter describes activation of RAN2928: DSP Pool Information in Measurements feature. For more information on the feature, see Description of RAN2928: DSP Pool Information in Measurements
t
Steps described in this chapter are performed on RNC network element. Before you start This feature is activated after automatic SW release upgrade. This happens only if user performed all the steps described in the procedure from the release upgrade instruction. If the steps were not performed, it is possible that DSP pool information is measured on DMPG level. This situation requires manual activation of the feature. 1
Verify whether DSP pool information is measured on DMPG level. Check the object with the following command: ZT2I:NAME=AMEAS269:OID=001:ICH=B; Result Manual activation is unnecessary when the following message appears: MEASURED COMPUTER UNITS: UNIT TYPE UNIT INDEX DSP 0
g Proceed to manual activation when the following message appears: MEASURED COMPUTER UNITS: UNIT TYPE UNIT INDEX DMPG 0 DMPG 1 Counter 20 DSP_SERVICE_POOL_TYPE does not exist.
g t
Stop, delete and recreate M269 measurement if you find DSP pool information is measured on DMPG level. 2
Stop, delete and recreate M269 measurement (optional). Stop M269 measurement with the following command: ZT2E:NAME=AMEAS269:OID=001:; Delete M269 measurement with the following command: ZT2D:NAME=PMEAS269:OID=001:; Re-create M269 measurement with the following command: ZT2C:MID=269:OID=001::ID="*":; Start M269 measurement with the following command: ZT2S:NAME=PMEAS269:OID=001:;
3
Check the measured object. Type the following command to obtain measurement report: ZT2I:NAME=AMEAS269:OID=001:ICH=B; Result MEASURED COMPUTER UNITS: UNIT TYPE UNIT INDEX DSP 0 DSP 1 DSP 2 DSP 4 Counter 20 DSP_SERVICE_POOL_TYPE exists.
g Result RAN2928: DSP Pool Information in Measurements feature is activated.
Issue: 01F
DN09146788
405
RNC solution features
RU50 Feature Descriptions and Instructions
7.2.3 Verifying RAN2928: DSP Pool Information in Measurements Purpose This chapter describes verification of RAN2928: DSP Pool Information in Measurements feature. For more information on the feature, see Description of RAN2928: DSP Pool Information in Measurements Before you start
1
Verify whether DSP pool information is measured on DMPG level. Check the object with the following command: ZT2I:NAME=AMEAS269:OID=001:ICH=B; Result Manual activation is unnecessary when the following message appears: MEASURED COMPUTER UNITS: UNIT TYPE UNIT INDEX DSP 0 DSP 1 DSP 2 DSP 4 Counter 20 DSP_SERVICE_POOL_TYPE exists.
7.2.4 Deactivating RAN2928: DSP Pool Information in Measurements Post requisites RAN2928: DSP Pool Information in Measurements feature cannot be deactivated.
7.2.5 Testing RAN2928: DSP Pool Information in Measurements Follow these procedures to verify that the activation of the RAN2928: DSP Pool Information in Measurements feature has been successful.
g
These are examples 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. Purpose The purpose of this test case is to verify that the DSP LOAD MEASUREMENT M617 (Measurement Identifier M269 in RNC) counters are upgraded to provide single DSPlevel data after activating the RAN2928: DSP Pool Information in Measurements feature. Before you start This feature is activated after SW release upgrade automatically, if the user performs all described steps of the procedure as mentioned in release upgrade instruction. If does not, it is possible that DSP pool information is measured on DMPG level. This situation requires manual activation of the feature.
Required test environment and settings: • •
406
one IPA-RNC(RNC2600) one OMS
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
1
RNC solution features
Verify whether DSP pool information is measured on DSP level in RNC. a) Create and start M269 with the following commands in RNC: ZT2C:MID=269:OID=001::ID="*":; ZT2S:NAME=PMEAS269:OID=001; b) Check if the object is DMPG with the following command: ZT2I:NAME=AMEAS269:OID=001:ICH=B; Result Manual activation is unnecessary when the following message appears: MEASURED COMPUTER UNITS: UNIT TYPE UNIT INDEX DSP 0 DSP 1 DSP 2 DSP 4 Counter 20 DSP_SERVICE_POOL_TYPE exists.
Proceed to manual activation when the following message appears: Proceed to manual activation when the following message appears: MEASURED COMPUTER UNITS: UNIT TYPE UNIT INDEX DMPG 0 DMPG 1 Counter 20 DSP_SERVICE_POOL_TYPE does not exist.
2
Check measurement report in GOMS. Open RNW Measurement Presentation by Application Launcher, check whether M617C20 counter exists and other M617 counters are DSP level. Result M617C0-19 counters are all in DSP level. M617C20 DSP_SERVICE_POOL_TYPE counter exists as shown in the Figure 59: M617C20 counter visible in GOMS.
Issue: 01F
DN09146788
407
RNC solution features
RU50 Feature Descriptions and Instructions
Figure 59
M617C20 counter visible in GOMS
7.3 RAN2959: mcRNC Step 7 Support 7.3.1 Description of RAN2959: mcRNC Step 7 Support Introduction to the feature This feature adds capacity step 7 (S7-B2) support to the mcRNC HW Rel.2 configurations and increases overall mcRNC capacity to reach the maximum controller's hardware configuration. The mcRNC step 7 contains eight BCN-B modules with Octeon II add-in cards. This feature introduces the expansion path from S3-B2 to S7-B2
g 7.3.1.1
Recovery group and recovery unit restarts are required to re-balance SS7 signaling load during S3-B2 to S7-B2 capacity expansion. Detailed information are in the RAN2959: mcRNC HW capacity expansion support feature description.
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature benefits the operator as follows: • • •
408
high capacity RNC capacity expansion from lower capacity step to higher capacity step provides smooth mcRNC HW capacity expansion
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
7.3.1.2
RNC solution features
Requirements Software requirements The following table lists software required for this feature. Table 171
Software requirements
RAS
Flexi Direct
IPA-RNC
mcRNC
OMS
BTS Flexi
Flexi Lite
RU50 EP1
Support not required
Support not required
mcRNC4.1
OMS3.1
Support not required
Support not required
Table 172
Software requirements
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
Support not required
NetAct 8 EP2 (NetAct 15)
Support not required
Support not required
Support not required
Support not required
Hardware requirements This feature requires mcRNC HW Rel.2 (BCN-B).
7.3.1.3
Functional description General information This feature offers mcRNC hardware capacity step S7-B2 (eight BCN-B module configuration) support to increase mcRNC capacity and cell connectivity. The mcRNC hardware capacity expansion from S3-B2 (four BCN-B module configuration) to S7-B2 is also supported with the feature. The controller with full mesh topology is shown on the Figure 60: mcRNC S7-B2 capacity step with full mesh cabling
Issue: 01F
DN09146788
409
RNC solution features
RU50 Feature Descriptions and Instructions
Figure 60
mcRNC S7-B2 capacity step with full mesh cabling
The mcRNC HW capacity expansion does not require any RNC restart. The RNC and all BTS's cell service continues although RNC capacity is reduced during the HW expansion period. The mcRNC HW expansion time with reduced RNC capacity is less than four hours. Enabling this feature takes nine hours in total. It is recommended to perform the hardware expansion within a maintenance window. Preparation work for the HW expansion, without impacting the RNC's capacity and performance, is needed. The preparation work is done within six hours of one normal day. In case of a failed mcRNC HW expansion, mcRNC is able to go back to the original configuration by restarting the RNC.
410
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
Having hardware expansion done, the user does BTS resource re-balancing to make RNC load sharing. The RAN2959:mcRNC Step 7 Support increases mcRNC capacity. The capacity is measured against Nokia traffic profile.
S7-B2 step capacity figures For more information on detailed capacity figures related to the new S7-B2 step, check Capacity and connectivity chapter in Multicontroller RNC Product Description.
Resource re-balancing The operator can perform BTS resource graceful re-balancing via SCLI if the license of the RAN2591: Selective BTS Resource Re-Balancing in mcRNC feature is activated. Otherwise operator can only select mcRuoste.
7.3.1.4
System impact Interdependencies between features The RAN2591: Selective BTS Resource Re-Balancing in mcRNC feature needs to be activated if the operator wishes to perform BTS resource graceful re-balancing via SCLI.
Impact on interfaces This feature has no impact on interfaces.
Impact on network and network element management tools There are no commands related to this feature.
Impact on system performance and capacity This feature increases system capacity.
7.3.1.5
RAN2959: mcRNC Step 7 Support management data For information on alarm, counter, key performance indicator, and parameter documentation see Reference documentation.
Alarms There are no existing 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 existing parameters related to this feature.
7.3.1.6
Sales information Table 173
412
Sales information
BSW/ASW
SW Component
License in network element
BSW
RAN
Not defined
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
7.4 RAN2512: Network Resiliency for RNC2600 7.4.1 Description of RAN2512: Network Resiliency for RNC2600 General information on RAN2512: Network Resiliency for RNC2600 feature for RNC2600 radio access network controller.
Introduction to the feature The RAN2512: Network Resiliency for RNC2600 feature is dedicated for the WCDMA Radio Network Controller- RNC2600. The feature improves network availability. This feature allows RAN recovery from fatal HW failure of a single controller or the controller's site. When one physical controller has failed, the operator is able to command the earlier-configured and synchronized backup physical controller to take over the responsibility of the failed physical controller. This feature helps to avoid long outages, lasting many hours or days.
7.4.1.1
Benefits End-user benefits This feature improves network services availability in case of catastrophes.
Operator benefits This feature shortens the controller's outage time in the radio network.
7.4.1.2
Requirements Software requirements Table 174: Software requirements lists the software required for this feature. Table 174
Software requirements
RAS
Flexi Direct
IPA-RNC
mcRNC
OMS
BTS Flexi
Flexi Lite
RU50 EP1
Support not required
RN8.1
Support not required
OMS3.1
WN9.1
WL9.1
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
WN9.1
NetAct 8 EP2 (NetAct 15)
Support not required
Support not required
Support not required
Support not required
Hardware requirements This feature requires the following hardware: • •
Issue: 01F
To configure BkPRNC- RNC2600 capacity step 3 with full CCP1D-A is required. To configure PrPRNC- RNC2600 capacity step1 or step2, or step3. Both CCP18-C and CCP1D-A configurations are supported.
DN09146788
413
RNC solution features
RU50 Feature Descriptions and Instructions
•
g
Flexi Multimode System Module FSMC/D/E or Flexi Multiradio System Module FSMF or Flexi Lite BTS. We recommend to purchase new hardware (capacity step 3) to configure BkPRNC on the dedicated PRNC.
Other requirements Only network configured with full IP Iub, Iur, Iu-PS, Iu-CS interfaces allow to fully use the advantages provided by this feature. It requires BTS sites to be connected to the protected RNCs via IP Iub interface in order to have them controlled by BkPRNC after redundancy switch. This is the precondition to enable RNC resiliency synchronization and switchover operations. It is possible to enable the feature in networks where some BTSs have ATM Iub or Dual Iub configuration. In case of a disaster or prepared redundancy switch, only the IP sites are switched over to backup RNC. ATM Iub sites are not switched over, but they do not prohibit the resiliency operations for the IP Iub BTS sites. After redundancy switch, the ATM/dual Iub BTSs remain online as the PrPRNC’s ATM interfaces are not shut down. However, when PrPRNC loses Iu connection, it sends system information block (SIB) that there is no Iu service to the UE connected to BTS configured with ATM Iub interface. After receiving this information, the UEs might not connect to the indicated BTSs. The actual UE behavior depends on the vendor’s implementation. The SIB sending is managed using RNC-IUO-IuBarring* parameters.
t 7.4.1.3
You may restore protected and/or original RNC with the full initial configuration using the normal RNC restore functionality.
Functional description Functional overview The RAN2512: Network Resiliency for RNC2600 is related to RNC2600 WCDMA RAN network controller. The feature improves network availability during single outages and the controllers site outages. This feature introduces the following definitions: • • •
Physical RNC (PRNC) which is a RNC HW with SW installed. Backup PRNC (BkPRNC) which is a PRNC configured only for redundancy purposes; it does not have its own radio access network under control. Protected PRNC (PrPRNC) which is a PRNC with running network services protected by BkPRNC.
With this feature, the operator can introduce BkPRNC to protect a PRNC in the network. In case a PrPRNC fails, the BkPRNC is commanded by the operator to take over the RAN and interfaces, and to run the PrPRNC's services. RNC2600 capacity step3 can backup RNC2600 capacity step1/step2/step3. One RNC2600 configured as BkPRNC is able to protect up to 16 RNC2600s. One PrPRNC has one BkPRNC configured, so that the redundancy mode is N+1. The PrPRNC and the BkPRNC can be in the same physical site or in different sites.
414
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
The intra-site resiliency is useful when the operator wants to do on-site maintenance to the PrPRNC. With the activation of redundancy switch the BkPRNC takes over the PrPRNC's responsibilities. This makes it possible to shut down or isolate the PrPRNC. The benefits of intra-site resiliency are that the network's KPIs do not decrease and that scheduled or sudden maintenance work can be done. The inter-site resiliency is needed in case there is, for example, a fire or a natural disaster like an earthquake that can destroy the whole site. To improve network stability and availability in this case, the BkPRNC must be placed in another site.This site must not be affected by a disaster when the disaster happens in the area where the PrPRNC is placed. This feature feature introduces a new RNC-cluster (RNC-cl) O&M interface, which connects PrPRNC with BkPRNC. This new interface is used for synchronizing the BkPRNC configuration with the PrPRNCs' configurations. The file transfer between PrPRNC and BkPRNC is necessary. Because a configuration package, which is synchronized between PrPRNC and BkPRNC, contains sensitive data the secure file transfer is possible and advised. System supports both secure and insecure file transfer in RNC-cl O&M interface. Figure 61: Network resiliency transport network concept shows in general the resiliency idea and introduces an example network concept.
Issue: 01F
DN09146788
415
RNC solution features
RU50 Feature Descriptions and Instructions
Figure 61 NetAct
Network resiliency transport network concept OMS
RNC
SGSN
SGSN
MSS/MGW
O&M
CBC server
Core
Site A
PrPRNC
SAS server
SiteB
PrPRNC
BkPRNC
PrPRNC
PrPRNC
BkPRNC
Backhaul
Active Standby RNC-clO&M OMS NetAct
7.4.1.4
System impact Interdependencies between features This feature requires full IP protocol support, thus the following features' activation is required: • • • • •
416
RAN74: IP Based Iub for Flexi WCDMA BTS feature RAN75 IP based Iu-CS feature RAN2276 IP based Iu-BC feature RAN750 IP based Iu-PS feature RAN76 IP based Iur feature
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
RAN1874: Automatic OMS Resiliency feature supports RAN2512: Network Resiliency for RNC2600 feature. RAN2512: Network Resiliency for RNC2600 does not impact on RAN1874: Automatic OMS Resiliency
Impact on interfaces This feature introduces a new RNC-cl O&M interface.
Impact on commands This feature introduces new commands, which are listed and described in Managing Software This feature is managed by the parameters listed in Parameters.
Impact on network and network element management tools This feature is not managed using NetAct. This feature introduces a new RNW object called PRNC, which represents either PrPRNC or BkPRNC. The object can be seen in OMS EM regardless of whether the feature is activated or not. Figure 62
PrPRNC icon
Figure 63
BkPRNC icon
This feature impacts network management or network element management tools as described in Appendix 2: Limitations
Impact on system performance and capacity This feature impacts system performance and capacity as follows: •
•
7.4.1.5
For every 1-16 protected controllers, at least one backup BkPRNC is required, with the highest configuration (the amount of BkPRNCs depends on the required redundancy level). Transport links between BTSs under PrRNCs and BkRNC and between BkRNC and core or other controllers must be sufficient to carry whole traffic
RAN2512: Network Resiliency for RNC2600 management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms Table 175
New alarms
Alarm ID Alarm name Schedule problem
Issue: 01F
DN09146788
417
RNC solution features
RU50 Feature Descriptions and Instructions
Table 175
New alarms (Cont.)
Alarm ID Alarm name 3877
RNC RESILIENCY SYNCHRONIZATION MISSING
3876
RNC RESILIENCY ADAPTION MISSING
Configuration problem 3835
RNC SERVICE CONFIGURATION MISSING OR INCOMPLETE
Operation problems and notices 3831
DATA SYNCHRONIZATION FAILURE
3834
BACKUP BUILD FAILURE
0226
RNC SERVICE ACTIVATION
3833
RNC SERVICE DEACTIVATION FAILED IN PEER PRNC
3839
ACTIVITY CHECK WITH BACKUP ASSOCIATED PRNC FAILED
3832
ACTIVATION OF RNC SERVICE FAILURE
3734
RNC CLUSTER O&M CONNECTION FAILURE
3429
CRITICAL FAULT IN BKPRNC
3436
MAJOR FAULT IN BKPRNC
3437
MINOR FAULT IN BKPRNC
Table 176
Related existing alarms
Alarm ID Alarm name 2081
OMS SWITCHOVER HAS BEEN PERFORMED
3295
LICENCE CAPACITY EXCEEDED
Measurements and counters There are no measurements or counters related to this feature.
Key performance indicators There are no key performance indicators related to this feature.
Parameters Table 177: New parameters lists parameters introduced with this feature. Table 177
418
New parameters
Full name
Abbreviated name
Managed object
OAM Connection Establishment Retry Counter
ConnectionRetryCounter
PRNC
OMS backup IP Address
OMSBackupIpAddress
PRNC
OMS IP Address
OMSIpAddress
PRNC
Physical RNC Change Origin
PRNCChangeOrigin
PRNC
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 177
Issue: 01F
RNC solution features
New parameters (Cont.)
Full name
Abbreviated name
Managed object
Physical RNC Identifier
PRNCId
PRNC
Physical RNC IPv4 Address
PRNCIP4Address
PRNC
Physical RNC Mode
PRNCMode
PRNC
Physical RNC Name
PRNCName
PRNC
PRNC Client TLS Mode
PrncClientTLSMode
PRNC
Secondary OMS IP address
SecOMSIpAddress
PRNC
Serving OMS
ServingOMS
PRNC
Serving OMS admin setting
ServingOMSAdminSetting
PRNC
Serving OMS Switchover Request
ServingOMSSwoRequest
PRNC
Activity Mode
ActivityMode
PRNC/RNCSRV
RNC service Change Origin
RNCSRVChangeOrigin
PRNC/RNCSRV
RNC SERVICE Identifier
RNCSRVId
PRNC/RNCSRV
RNC service status
ServiceStatus
PRNC/RNCSRV
Source IP address for IuBC interface
CBCSourceIPAddress
PRNC/RNCSRV
Automatic adaption control
AutoAdaptation
PRNC/RNCSRV/DATSYN
Backup completeness of the backup configuration
BackupCompleteness
PRNC/RNCSRV/DATSYN
Backup update Time for RNC configured data
BackupUpdateTime
PRNC/RNCSRV/DATSYN
Data synchronization Change Origin
DATSYNChangeOrigin
PRNC/RNCSRV/DATSYN
Data Synchronization Identifier
DATSYNId
PRNC/RNCSRV/DATSYN
Data synchronization state
DataSynchState
PRNC/RNCSRV/DATSYN
RNC cluster O&M interface link status
RNCClusterOMLnkState
PRNC/RNCSRV/DATSYN
Scheduling periodic data synchronization in days
DataSyncDays
PRNC/RNCSRV/DATSYN
Scheduling periodic data synchronization in hours
DataSyncHours
PRNC/RNCSRV/DATSYN
Scheduling periodic data synchronization in minutes
DataSyncMinutes
PRNC/RNCSRV/DATSYN
Active Physical RNC
ActivePRNC
RNC
Alarm status at backup PRNC
AlarmStatus
RNC/BKPRNC
Backup Physical RNC Identifier
BkPRNCId
RNC/BKPRNC
Backup PRNC client TLS Mode for RNC Rlc O&M link
BKPRNCTLSClientMode
RNC/BKPRNC
DN09146788
419
RNC solution features
RU50 Feature Descriptions and Instructions
Table 177
New parameters (Cont.)
Full name
Abbreviated name
Managed object
Backup PRNC current Activity Mode
ActivityMode
RNC/BKPRNC
Backup PRNC name
PRNCName
RNC/BKPRNC
Backup PRNC unknown status
UnknownStatus
RNC/BKPRNC
Backup RNC IPv4 Address used for establishing RNC cluster O&M interface
BackUpRNCIP4Address
RNC/BKPRNC
Backup update time at backup BackupUpdateTime PRNC
RNC/BKPRNC
BKPRNC Change Origin
RNC/BKPRNC
BKPRNCChangeOrigin
Configuration completeness at BackupCompleteness backup PRNC
RNC/BKPRNC
RNC cluster O&M interface link status
RNC/BKPRNC
RNCClusterOMLnkState
Table 178: Modified parameters lists parameters modified by this feature. Table 178
Full name
7.4.1.6
Modified parameters
Abbreviated name Managed object
RNC Identifier RncId
RNC
RNC Options
RNC
RncOptions
Sales information Table 179
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
RNC Resiliency LK in PrPRNC.
Other necessary licenses For SFTP enabled, SSH license is necessary.
420
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
7.4.2 RAN2512: Network Resiliency for RNC2600 activation procedure overview Important
f
Keep the BkPRNC always powered on, also in resiliency idle (when RNCSRV is not active on BkPRNC). Trying to save energy by powering off the BkPRNC can cause serious problems because PrPRNC and BkPRNC are not synchronized.
Troubleshooting If any of alarms described in RAN2512: Network Resiliency for RNC2600 management data follow the instructions given by alarm help or refer to Reference documentation.
7.4.3 Activating RAN2512: Network Resiliency for RNC2600 Purpose This chapter provides procedures on how to activate RAN2512: Network Resiliency for RNC2600 feature. Assumed and expected network plan is shown in the Figure 64: Network transport plan Figure 64
Network transport plan
OMS-1
OMS-2
10.43.7.18
10.58.239.68
PrPRNC-221
BkPRNC-301 O&M
RNCId-221 ICSU
...
RNCId-221 ICSU
ICSU
10.43.12.1/26
NPGE
...
...
ICSU
10.43.7.192/26
NPGE
NPGE
10.43.5.1/24
...
NPGE
10.43.6.1/24 O&M:10.63.56.215
O&M:10.62.85.16
instandbyforbackup serviceactivation
7.4.3.1
Commissioning BkPRNC Before you start Before performing of this procedure make sure: • •
Issue: 01F
Capacity licenses of BkPRNC are equal or bigger than capacity licenses in PrPRNC. IDs of PRNCs in resilient network do not collide.
DN09146788
421
RNC solution features
RU50 Feature Descriptions and Instructions
1
Install and activate licenses. The feature requires: •
licenses mandatory only for PrPRNC –
•
licenses mandatory in both PrPRNC and BkPRNC – – –
These license will compare the capacity of BkPRNC against capacity of PrPRNC. If capacity of BkPRNC is less than PrPRNC, then Data Sync will not be performed. 2
Commission PRNC to BkPRNC. a) Log in to active OMU: > ZDDS; b) Start remote session with the following command in order to create a PRNC object: 0000-MAN>ZLE:1,RUOSTEQX c) Create RNC with the following command: 0000RUO>Z1CM:,,[],[] ,[],[],[];
g
The PRNCId of every created BkPRNC must be unique. It cannot collide with the RNCId of any of the PrPRNC’s configured into resilient network. Example Assign ID to PRNC (301), Primary OMS IP address (10.43.7.18), switch controller to backup mode (2), name of the BkPRNC (Brine), Secondary OMS IP address (10.58.239.68), serving_oms(0), retries (10) with the following command: 0000-RUO>Z1CM:301,10.43.7.18,2,Brine,10.58.239.68,0,10 Result Connecting to RNW database... PRNC-301 creation (mode: backup) completed successfully at 13-08-2014 23:45:21.84 Closing RNW database connection...
3
Check if the BkPRNC commissioning is successful. Type the following command: 0000-RUO>Z1C
422
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
Result Operation starting at: 13-08-2014 23:45:27.32 Connecting to RNW database... RNC object not found. PRNC information: ----------------------------------------------------PRNC ID: 301 PRNC name: Brine PRNC mode: 2 (Backup) PRNC IP address: 10.62.85.16 Restart reason: 0 (Normal restart) Primary OMS IP address: 10.43.7.18 Secondary OMS IP address: 10.58.239.68 Backup OMS IP address: 0.0.0.0 Current serving OMS: 1 (primary OMS) Serving OMS selection: 0 (automatic) Connection retry count: 10 RNC Client TLS mode: 2 (Probing) ----------------------------------------------------Closing RNW database connection... 0000-RUO>
The BkPRNC is connected to OMS automatically after BkPRNC commissioning and PRNC object was created. 4
Ensure that one BPS has been generated after the commissioning. < ZWMI; Result LOADING PROGRAM VERSION 1.5-0 BPS NAME ENVIRONMENT
DEF
ROLE
BUILD STATUS
DIRECTORY
RNC-SERVICE-ID
PACKAGE-ID (REP-ID)
DELIVERY CD-ID QX143060DEV 14.30-60
Y
BASE
BU
QX143060DEV
QX
QX 14.30-60 CID000QX 15.1-0 TOTAL BPS: 1 COMMAND EXECUTED
7.4.3.2
Configuring OMS for network resiliency using Element Manager Purpose This chapter instructs how to configure OMS in order to act in the resilient network.
Issue: 01F
DN09146788
423
RNC solution features
RU50 Feature Descriptions and Instructions
1
t
Commission BkPRNC using the RUOSTE (optional). Perform this step only if commissioning of the BkPRNC has not been done yet. If it has been done, ensure BkPRNC managed object presence in GUI and proceed with step Create RNCSRV in BkPRNC. Enable the BkPRNC commissioning procedure using the RUOSTE. Enter the following command: 0000RUO>Z1CM:,,[],[] ,[],[],[]; Example Assign ID to PRNC (301), Primary OMS IP address (10.43.7.18), switch controller to backup mode (2), name of the BkPRNC (Brine), Secondary OMS IP address (10.58.239.68), serving_oms(0), retries (10) with the following command: 0000-RUO>Z1CM:301,10.43.7.18,2,Brine,10.58.239.68,0,10 Result Connecting to RNW database... PRNC-301 creation (mode: backup) completed successfully at 26-03-2014 18:47:16.28 Closing RNW database connection... 0000-RUO> C Operation starting at: 26-03-2014 18:47:21.95 Connecting to RNW database... RNC object not found. PRNC information: ----------------------------------------------------PRNC ID: 301 PRNC mode: 2 (Backup) PRNC IP address: 10.62.85.16 Restart reason: 0 (Normal restart) -----------------------------------------------------
BkPRNC is present on OMS with both PrPRNC objects as shown in the Figure 65: BkPRNC managed object visible in OMS GUI Figure 65
424
BkPRNC managed object visible in OMS GUI
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
2
RNC solution features
Create RNCSRV in BkPRNC. Open OMS Element Manager. Go to the specific BkPRNC ID. Right-click on it and create RNCSRV using Create new object option.
3
Create BkPRNC object for PrPRNC. BkPRNC object must occur under the following path ROOT ► RNC- ► BkPRNCs. BkPRNC IP address is visible under Backup RNC IPv4 Address used for establishing RNC cluster O&M interface.
4
Add another PrPRNC. Repeat steps Create RNCSRV in BkPRNC. and Create BkPRNC object for PrPRNC. if you want to add another PrPRNC.
7.4.3.3
Configuring OMS for network resiliency using MML commands Purpose This is an example configuration of RNCSRV, which shows the rule of network configuration.
t
It is also possible to create RNCSRV using OMS Element Manager. Omit this chapter if it has been already done. Before you start All commands in this procedure are given in base build (ACTIVITY MODE: BACKUP). Ensure that RNC is operating on it with the following command ZE1I;. 1
Create RNC service (RNCSRV). Type the following command: [ZE1A:] Example ZE1A:221:; Result
t
This action takes approximately 6 minutes in background, after the following system output has been displayed. LOADING PROGRAM VERSION 1.17-0 RNC RESILIENCY ASSOCIATION FOR RNCSRV-221 IS ADDED SUCCESSFULLY COMMAND EXECUTED
2
Check service status. Check whether SERVICE STATUS is CREATING SERVICE. < ZE1I;
Issue: 01F
DN09146788
425
RNC solution features
RU50 Feature Descriptions and Instructions
Result LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: CREATING SERVICE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: DISABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED
3
Ensure RNC resiliency association was correctly added to the RNC service. Check the RNC service statuses by displaying it several times using the following command: < ZE1I; LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED
Result RNC resiliency association was correctly added to the RNCSRV when RNC CLUSTER LINK STATUS is ENABLED.
426
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
4
In OMS, check topology after RNCSRV object creation at BkPRNC.
5
Ensure that new backup build has been added to BPS. < ZWMI; Result COMMAND EXECUTED < ZWMI; LOADING PROGRAM VERSION 1.5-0 BPS NAME ENVIRONMENT
DEF
ROLE
BUILD STATUS
DIRECTORY
RNC-SERVICE-ID
PACKAGE-ID (REP-ID)
DELIVERY CD-ID QX143060DEV 14.30-60
Y
BASE
NW
QX143060DEV
QX
QX 14.30-60 CID000QX 15.1-0
BKUP
UD
BK00301_13
QX 14.30-
60 00301
QX 14.30-60
CID000QX 15.1-0 TOTAL BPS:
1
COMMAND EXECUTED
7.4.3.4
Activating PrPRNC for RNC resiliency RNC is automatically configured as a standard PRNC after RU50 EP1 SW upgrade. 1
Interrogate PRNC object. Check RNC is configured as standard PRNC with the following command: < ZE1I; Result LOADING PROGRAM VERSION 1.17-0 RNC TYPE: STANDARD RNC PRNC ID: 221 PRNC IP: 10.63.56.215 RNC SERVICE ID: 221 ACTIVITY MODE: ACTIVE SERVICE STATUS: IDLE
Issue: 01F
DN09146788
427
RNC solution features
RU50 Feature Descriptions and Instructions
2
Install RAN2512 feature license and activate it. Enter the following command: ZW7L:; Result Feature code 4784 is ON.
3
Add RNC resiliency association with BkPRNC. Add RNC resiliency association with BkPRNC by creating BKPRNC object in RNW DB. This enables the RNC-cl O&M at PrPRNC. Type the following command: ZE1A::; Example < ZE1A:301:10.62.85.16:; Result RNC RESILIENCY ASSOCIATION WITH PRNC-301 WAS ADDED SUCCESSFULLY COMMAND EXECUTED
4
Check that the RNC resiliency association has been successfully added. Display RNC status and check BACKUP PRNC IP is visible. < ZE1I; LOADING PROGRAM VERSION 1.17-0 RNC TYPE: PROTECTED RNC PRNC ID: 221 PRNC IP: 10.63.56.215 RNC SERVICE ID: 221 ACTIVITY MODE: ACTIVE SERVICE STATUS: IDLE BACKUP PRNC ID: 301 BACKUP PRNC NAME: NOT UPDATED BACKUP PRNC IP: 10.62.85.16 BKPRNC ACTIVITY MODE: NOT UPDATED BKPRNC TLS CLIENT MODE: OFF BKPRNC ALARM STATUS: NOT UPDATED BACKUP COMPLETENESS: NOT UPDATED BKPRNC BACKUP UPDATE TIME: NOT UPDATED BKPRNC UNKNOWN STATUS: TRUE RNC CLUSTER O&M LINK STATE: DISABLED COMMAND EXECUTED
Result Suitable objects appear in OMS EM
428
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 66
7.4.3.5 7.4.3.5.1
RNC solution features
PRNC and PrPRNC objects
RNC-cl O&M interface configuration solutions and security IP addressing solutions on RNC-cl This chapter describes possible solutions for RNC-cl interface addressing. For IP addressing on RNC-cl there are two alternatives for both PrPRNC and BkPRNC • •
g
Shared IP address solution Dedicated IP addresses solution Note: as with other configuration, if the O&M IP addressing is changed in Base build after RNCSRV is created. The change is not populated to RNCSRVs’ Backup builds but they have to be manually configured to them too.
Shared IP address solution This solution utilizes shared IP address for common RNC-cl traffic and other O&M traffic. It means that in addition to RNC-cl traffic all the other O&M traffic, like BTSOM traffic and RNC-OMS traffic, is terminated to the same IP address. This solution does not require additional IP layer configuration in the RNC. The activated feature automatically assigns existing O&M IP address. Examples in this Activation Instruction assume that the user uses shared IP address solution.
Dedicated IP addresses solution This solution uses dedicated IP addresses for separate RNC-cl and O&M traffic. If you require dedicated IP address for RNC-cl, you must add the relevant address to OMU with ZQRN MML-command. In shared IP address solution the O&M IP address is assigned to the EL0 interface. In dedicated IP address solution you add the IP address for RNC-cl to OMU’s EL1 interface. If the IP address in EL1 is the same as in the EL0 interface (for example
Issue: 01F
DN09146788
429
RNC solution features
RU50 Feature Descriptions and Instructions
carrier-sense is enabled, see Configuring IP and routing in Configuring IP Connection for IPA-RNC) you must add a different IP address to EL1 after the first address. The system will use the additional address for the RNC-cl interface.
7.4.3.5.2
Configuring secure RNC-cl O&M interface This chapter describes how to enable security for RNC-cl interface.
1
Configure cluster O&M interface. Perform these steps in both PrPRNC and BkPRNC. a) Copy the certificate files into both the PrPRNC and BkPRNC under /shadows folder. b) Check the files presence. Check whether the files from the list below are present. • • •
c) Install the certificates. Install the previously copied certificates with the following commands: 1. ZQ4A:TLSPRIVATE,P:F,"W0-/PRIVATE.BIN":; 2. ZQ4A:TLSCERT,C:F,"W0-/CERTXXXX.BIN":; 3. ZQ4A:TLSCACERT,C:F,"W0-/CACERT.BIN":; d) Create SSL/TLS layer definition. ZI3C:OMU:TLSCERT,TLSPRIVATE:TLSCACERT:; e) Change the Client TLS mode to FORCED in PrPRNC. f)
ZE1M:::FORCED; Check the configuration correctness. ZQRS:OMU,0;
Result Port 8023 is used. 2
Configure RNC-OMS interface. a) Copy the certificate files to OMS. Copy the certificate files to /tmp folder with the following commands: • •
b) Install the certificates. In OMS, enter the following commands: 1. omscertificate install-ca-cert -cert-file /tmp/cacertificate.pem 2. omscertificate install-ee-cert -cert-file /tmp/cert.pem -key-file /tmp/private.pem c) Change the Client TLS mode to PROBING (in OMS). Access the relevant parameter by the path: Application Launcher ► ClusterRoot ► OMS ► System ► Network ► TLS ► TLSModeOM ► omsParameterValue d) Change the Client TLS mode to PROBING (in RNC). 1. 2. 3. 4.
ZDDS; ZLE:1,RUOSTEQX; 1 Z1CT:2;
e) Check the configuration correctness: ZQRS:OMU,0; Result Port 8023 is used.
7.4.3.6
Synchronizing RNCSRV Purpose This chapter provides procedures for manual and scheduled RNC service synchronization. Before you start It is recommended that the synchronization takes place when the PrPRNC's OMU load is low. Although the synchronization schedules may overlap, it is also recommended that some phasing is considered so that the synchronization of all PrPRNCs does not start at the same time. During synchronization BkPRNC must be in Backup mode. To switch to the mode, use the following command ZE1C:UNLOAD:;
t
The synchronization takes about 40 minutes per PrPRNC, depending on RNC load, bandwidth, overall network condition. Synchronization works only if PrPRNC and BkPRNC have the same software versions. If PrPRNC and BkPRNC have different software versions, synchronization does not work, but redundancy switch and redundancy switch back can be executed.
1
Check RNC service status. Check RNC service in BkPRNC with the following command: ZE1I;
Issue: 01F
DN09146788
431
RNC solution features
RU50 Feature Descriptions and Instructions
Result ACTIVITY MODE changes to BACKUP after adaptation and tests of downloaded configuration package. RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED
2
Set scheduled synchronization (optional). To schedule a synchronization in BkPRNC, type the following command: ZE1M:::::DAYS=xxx,TIME=HH-MM:; implies following options: /* IDENTIFY DATA SYNC SCHEDULE DAYS: MON TUE WED THU FRI SAT SUN
ON WORKDAYS( MON,TUE,WED,THU,FRI ) ON HOLIDAYS( SAT,SUN ) ON EVERYDAY DAYS ALL CLEAR
(FOUR &-SEPARATORS MAXIMUM, AND 'NON' WILL BE IGNORED WHILE USING &-SEPERATOR)
*/
Example ZE1M:221::::DAYS=THU,TIME=08-13:; Result PARAMETER OF RNCSRV-221 IS MODIFIED PREVIOUS DATA SYNC SCHEDULE: -,00:00
432
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
CURRENT DATA SYNC SCHEDULE: THU,08:13 COMMAND EXECUTED
3
Check the RNC service status. Check the RNC service status with the following command: < ZE1I;
t
It is recommended to check the status at time when the synchronization is ongoing. Result ACTIVITY MODE changes from WAITING FOR SYNCHRONIZATION to BACKUP after synchronization is finished. SERVICE STATUS changes from SYNCHRONIZING DATA to IDLE after synchronization is finished. a) LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: THU,08:13 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED
b) LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: SYNCHRONIZING DATA CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED
Issue: 01F
DN09146788
433
RNC solution features
RU50 Feature Descriptions and Instructions
DATA SYNC SCHEDULE: THU,08:13 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED
c) LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: BACKUP SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: THU,08:13 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: LESS THAN 100% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED
4
Test backup configuration. The backup configuration tests are triggered automatically after each synchronization and transport configuration commit.
5
Start manual synchronization (optional). Start manual synchronization with the following command: ZE1S:START:; Example ZE1S:START:221:; SYNCHRONIZATION OF RNCSRV-221 IS STARTED COMMAND EXECUTED
434
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
7.4.3.7
RNC solution features
Configuring associations to the core network Before you start Because all of the presented commands must be executed in LOADED mode, switch to the LOADED using the following command: < < ZE1C:LOAD:221; Perform described steps after RNC has stared. Associations, which must be configured are shown in the Configuration matrix. Table 180
Configuration matrix
Already done in Necessary for entire base build BkPRNC
Necessary for each RNCSRV
No
1. 2. 3. 4. 5. 6. 7. 8. 9.
Ethernet configurations
1. 2. 3. 4. 5.
Ethernet configurations
1. Cabling configuration
Yes
1
VLAN configuration Configure IP addresses Configure Iu-CS control plane Configure Iu-PS control plane Configure Iu-CS user plane1 Configure Iu-PS user plane1 Configure IuB user plane1 Configure BTS O&M
VLAN configuration Configure IP addresses Configure Iu-CS control plane2 Configure Iu-PS control plane2
Configure alternate IP address of BkPRNC acting as PrPRNC-1 towards MSC. a) Create an association set. Type the following command: ZOYC:MSC2:C:M3UA:; b) Add associations to the association set. Type the following command: ZOYA:MSC2:ICSU,0:IETF:; ZOYA:MSC2:ICSU,1:IETF:; c) Configure association IP addresses: ZOYP:M3UA:MSC2,0:" 10.43.7.192.26 "," 10.43.7.192.26 ",:"10.71.4.215",25,"10.58.251.21",25,:; ZOYP:M3UA:MSC2,1:" 10.43.7.192.26 "," 10.43.7.192.26 ",2906:"10.71.4.214",25,"10.58.251.18",25,2906:; d) Modify association set: ZOYM:MSC2:NETWORK=8:; e) Modify association state: ZOYS:M3UA:MSC2,0:ACT:; ZOYS:M3UA:MSC2,1:ACT:;
Issue: 01F
DN09146788
435
RNC solution features
RU50 Feature Descriptions and Instructions
2
Modify the parameter values of the existing SCCP signaling point parameter set. Type the following command: ZOCM:0:27,1:; a) MSC 1. Create IP type of signaling link set: ZNSP:NA0,D'8438,MSC2:0:MSC2:; 2. Create signaling route set: ZNRC:NA0,D'8438,MSC2,0,:,,,7::::; 3. Allow the activation of a signaling link: ZNLA:0:; 4. Allow the activation of a signaling route: ZNVA:NA0,D'8438::; 5. Change the signaling link state: ZNLC:0,ACT; 6. Change the signaling route state: ZNVC:NA0,D'8438::ACT:; 7. Define SCCP for signaling points with subsystem copy: ZNFD:NA0,D'8438,0:8E,RANAP,0,Y:::::; 8. Modify local broadcast status of SCCP subsystems: ZOBC:NA0,D'8438,01:NA0,8E:Y:; ZOBC:NA0,D'8438,8E:NA0,8E:Y:; 9. Modify broadcast status of SCCP signaling points: ZOBM:NA0,D'8332,01:NA0,D'8438:Y:; ZOBM:NA0,D'8332,8E:NA0,D'8438:Y:; 10. Change the SCCP state of the signaling point: ZNGC:NA0,D'8332:ACT; 11. Change the state of an SCCP subsystem: ZNHC:NA0,D'8332:8E:ACT; 12. Change the SCCP state of the signaling point: ZNGC:NA0,D'8438:ACT; 13. Change the state of an SCCP subsystem: ZNHC:NA0,D'8438:8E:ACT; b) IUR: 1. Create IP type of signaling link set: ZNSP:NA0,D'8331,CRNC1:2:RNCIUR1:; 2. Create signaling route set: ZNRC:NA0,D'8331,CRNC1,0,:,,,7::::; 3. Allow the activation of a signaling link: ZNLA:2:; 4. Allow the activation of a signaling route: ZNVA:NA0,D'8331::; 5. Change the signaling link state: ZNLC:2,ACT; 6. Change the signaling route state: ZNVC:NA0,D'8331::ACT:; 7. Add a subsystem to signaling points: ZNFB:NA0,D'8332:8F,RNSAP,0,Y:; 8. Define SCCP for signaling points with subsystem copy:
436
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
ZNFD:NA0,D'8331,0:8F,RNSAP,0,Y:::::; 9. Modify local broadcast status of SCCP subsystems: ZOBC:NA0,D'8331,01:NA0,8F:Y:; ZOBC:NA0,D'8331,8F:NA0,8F:Y:; 10. Modify broadcast status of SCCP signaling points: ZOBM:NA0,D'8332,01:NA0,D'8331:Y:; ZOBM:NA0,D'8332,8F:NA0,D'8331:Y:; 11. Change the SCCP state of the signaling point: ZNGC:NA0,D'8331:ACT; 12. Change the state of an SCCP subsystem: ZNHC:NA0,D'8331:8F:ACT; 13. Change the state of an SCCP subsystem: ZNHC:NA0,D'8332:8F:ACT;
3
Modify the own signaling point data. Type the following command: ZNRP:NA0,D'8331,RNC:::;
4
Define the signaling service information data of own signaling point. Type the following command: ZNPC:NA0,03,SCCP:Y:Y,::;
5
Create a Signaling Connection Control Part (SCCP) for the signaling point. Type the following command: ZNFD:NA0,D'8331,0:8E,RANAP,0:;
Result Configuration visible at MSC: Configuration at MSC ASSOCIATION SET NAME -------------------RNC221
ASSOC SET ID -----------88
ASSOC. ASSOC ID IND UNIT IN UNIT --------- --------0 SIGU-0 ---
SCTP USER --------M3UA
ROLE -------SERVER
PARAMETER SET NAME STATE ---------------- -------------------IETF SCTP-DOWN
Post requisites Similar configuration has to be done for IUPS and other relevant interfaces as well.
7.4.3.8
Configuring Iur interface towards neighboring RNCs Purpose This chapter describes steps for configuration of Iur interface between BkPRNC and neighboring RNCs. Before you start Ensure RNC is in LOADED mode with the following < ZE1I;. 1
Configure Iur interface's control plane. a) Create an association set. Type the following command: ZOYC:BkPRNCIUR:C:M3UA:; b) Add associations to the association set. Type the following command: ZOYA:BkPRNCIUR:ICSU,0:IETF:; ZOYA:BkPRNCIUR:ICSU,2:IETF:;
438
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
c) Configure association IP addresses: Configure resilient IP addresses for M3UA association. First given IP address is the source IP address, second one is destination IP address (BkPRNCs IP address). Type the following command: ZOYP:M3UA:BkPRNCIUR,0:"10.63.60.83",:"10.63.60.6",29,:; ZOYP:M3UA:BkPRNCIUR,1:"10.63.60.91",:"10.63.60.7",29,:; d) Modify NETWORK appearance in the association set. Type the following command: ZOYM:BkPRNCIUR:NETWORK=8:; e) Modify associations state with the following commands: ZOYS:M3UA:BkPRNCIUR,0:ACT:; ZOYS:M3UA:BkPRNCIUR,1:ACT:; 2
Configure Iur interface's user plane (IPBR). a) Configure a new network interface with the following command: ZQRN:NPGEP,0:VL1260:10.43.7.2,L:28::::; b) Add a new IP-based routes with the following command: ZQRU:ADD:3,"IUR-1":100000:100000:0:0:::; c) Configure IP-based route network parameters with the following commands: ZQRC:NPGEP,0:VL1260:IPV4=10.43.7.2:ID=3::;
7.4.3.9
Configuring Iupc interface The Iupc interface to Standalone SMLC (SAS) is on the SIGTRAN stack. Configure Iupc interface towards SAS in each RNCSRV as described in Creating TCP/IP configuration in RSMU and ICSU units. RNC is a client on Iupc interface. In case SAS validates the RNC’s source IP address, the validation rule is that the SCTP connection establishment is allowed in both PrPRNC and BkPRNC. SAS does not need to support the two simultaneous SCTP connections because the PrPRNC and BkPRNC are not online at the same time.
7.4.3.10
Configuring Iubc interface The Iubc interface to cell broadcast center (CBC) is on the TCP/IP stack. For more information on configuring the Iubc, see Configuring IP for Iu-BC over ATM. CBC and RNC are able to have both the client and the server roles on Iubc ,even though CBC takes mostly the client's role. The client has to know the server's destination IP address whilst the server validates the address. In RNC, the Iubc source and destination IP addresses are defined in RNW DB. When RNW DB is copied from PrPRNC to BkPRNC, the source address is not valid in BkPRNC. The system changes it automatically to the address provided when the BkPRNC is running in the LOADED mode by using the ZE1M MML command. The redundancy switch has no impact the destination address from the BkPRNC's point of view. If Iubc is not enabled in the system, give 0.0.0.0 value as the source address in BkPRNC.
Issue: 01F
DN09146788
439
RNC solution features
RU50 Feature Descriptions and Instructions
CBC has to know both the PrPRNC’s and the BkPRNC’s IP addresses in order to establish the interface, so that CBC has to support the primary IP address, which refers to PrPRNC and the secondary IP address, which refers to BkPRNC. The secondary address is used when connection establishment to the primary address does not work, which is the case after redundancy switch. It is possible that CBC validates the secondary IP addresses meaning that same secondary IP address must not be used for many RNCs. In that case, in BkPRNC each RNCSRV has to have a unique source IP address. If CBC does not support the secondary IP address, the primary IP address has to be changed manually after redundancy switch. In this case it is also necessary to manually verify if broadcasts are ongoing or whether they should be restarted. When the primary RNC (in this case any of PrPRNC) is disabled, the secondary RNC (in this case BkPRNC) starts operating and sends reset request to CBC. This operation indicates to CBC that it has to restart the broadcast, because it is impossible to establish TCP/IP connection to PrPRNC. The CBC must establish connection to BkPRNC and restart the broadcast. However, the actual CBC behavior is vendor specific and may vary from the described example.
7.4.3.11
Committing changes and backup configuration test Enabling backup configuration test The user must commit any manual change of BkPRNC configuration done with MML commands. For example, when the user changes Iu /Iur signaling or transport configuration, committing it with ZE1X command must be executed as the last action. This command triggers the test, which checks the RNCSRV’s configuration health. Without the test, the faulty configuration may remain undetected. Only activation of RNCSRV, so the initiation of network resiliency, causes late malfunction detection. In case of auto-adaptation, the commitment is executed automatically and followed by the test.
Backup configuration test results When the test detects problems in the configuration: • •
PRNC-RNCSRV-DATSYN-BackupCompleteness value is set to Less than 100% 3835 RNC SERVICE CONFIGURATION MISSING OR INCOMPLETE alarm is raised
Troubleshooting Details regarding the problems are stored in commit log file.
7.4.3.12
Reconfiguring BTS
1
Commission BTS using PrPRNC and BkPRNC IP addresses. Provide the following information in BTS SM on Iub interface configuration page:
440
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 181
RNC solution features
BTS configuration values
Parameter
Value
Far end SCTP subnet
BkPRNC IP address
for example: 10.43.7.192 OAM address
BkPRNC IP address
for example: 10.62.85.16 Far end SCTP subnet address mask
BkPRNC FAREND SCTP
for example: 255.255.255.192 (/26)
g 7.4.3.13
Re-homing BTS may require changing of BkPRNC information to values related to the new controller.
Configuring RNCSRV Purpose RNCSRV configuration must be done in the LOADED mode. The general idea of RNCSRV configuration is shown on the Figure 67: RNCSRV configuration. Figure 67
RNCSRV configuration
RNCSRV Specific configuration
RNWDB IPBR
BFD
...
IPRO IP address Planned commonly toall RNCSRVs
VLAN Ethernet Cabling
Every RNCSRV/backup build must contain the whole configurations presented in Figure 67: RNCSRV configuration. The lower part of the figure is planned only once as it is common to all RNCSRVs, but also it has to be configured in each RNCSRV. The upper part of the figure must be unique in all RNCSRVs. Also the SIGTRAN signaling interfaces need to be configured separately to each RNCSRV. However, the lower part of the figure (as well as SIGTRAN configuration) is also configured in the base build. It means that the existing configuration is copied to RNCSERV configuration when RNCSERV is created, but after that any changes to the base build configuration are not populated to the already created RNCSERVs or vice versa. Before you start Table 182: Configuration list BkPRNC show RNC configuration items, which must be configured when configuring BkPRNC.
Issue: 01F
DN09146788
441
RNC solution features
RU50 Feature Descriptions and Instructions
Table 182
Configuration list BkPRNC
RNC configuration item
RNCSRV preconfiguration necessity
Notes
RNC NE account (User Ids)
No
Synchronized from PrPRNC
RNC system name (by default is IPA2800)
No
Synchronized from PrPRNC
RNC time setting (zone, DST)
No
Synchronized from PrPRNC
RNC HW configuration No (functional unit configuration)
Shares PRNC's HW configuration
RNC licenses
No
Synchronized from PrPRNC
Certifications and keys
Yes
RNCSRV shares PRNC's certifications and licenses. Operator installs certification and keys on the base build or the backup build. Resiliency framework aligns the configuration between the builds.
RNCSRV inherits the PRNC's transport configuration. After first configuration synchronization, the mapping XML needs to be completed for autoadaptation The source IP address for Iubc has to be defined with MML
g
442
RNW measurement plan
No
Transport and HW measurement plan
Yes
The IPBR MOs and IPRO MOs are synchronized from PrPRNC when autoadaption is successful. In other case, operator must configure IPBR and IPRO.
Synchronized from PrPRNC
Alarm definitions and filtering No
Synchronized from PrPRNC
Subscriber trace settings
No
Synchronized from PrPRNC
DSP resource configuration
No
Synchronized from PrPRNC
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
1
RNC solution features
Configure BkPRNC. Configure BkPRNC according to the Table 183: Configuration matrix. Table 183
Configuration matrix
Already done in Necessary for entire base build BkPRNC
Necessary for each RNCSRV
No
a) b) c) d) e) f) g) h) i)
Ethernet configurations VLAN configuration Configure IP addresses Configure Iu-CS control plane Configure Iu-PS control plane
a) b) c) d) e)
Ethernet configurations VLAN configuration Configure IP addresses
a) Cabling configuration
Yes
2
Configure Iu-CS user plane1 Configure Iu-PS user plane1 Configure IuB user plane1 Configure BTS O&M
Configure Iu-CS control plane2 Configure Iu-PS control plane2
1
Optional if auto-adaptation is enabled.
2
Optional if RNCSRVs have common destinations.
Commit transport configuration. a) Commit configuration < ZE1X:START; LOADING PROGRAM VERSION 1.17-0 COMMITTING CONFIGURATION CHANGE IS STARTED COMMAND EXECUTED
b) Check configuration committing status •
< ZE1X:SHOW; LOADING PROGRAM VERSION CONFIGURATION COMMITTING RESULT: START TIME = 2014-01-22 10:43:10.94 TERMINATE TIME = 2014-01-22 10:45:17.25 CONFIGURATION TEST = SUCCESS ADAPTATION = SUCCESS DETAILED REPORT CAN BE FOUND IN LOG FILE: /eclipse/BK00017J/ASWDIR/commit221.log COMMAND EXECUTED
Issue: 01F
DN09146788
443
RNC solution features
RU50 Feature Descriptions and Instructions
•
< ZE1I; LOADING PROGRAM VERSION 1.18-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: 221 RNC SERVICE ID: 221 ACTIVITY MODE: LOADED SERVICE STATUS: ADAPTING CONFIGURATION CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: OFF DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: MON,TUE,WED,THU,FRI,SAT,SUN,14:45 BACKUP UPDATE TIME: 11-08-2014;14:49 BACKUP COMPLETENESS: 100% RNC CLUSTER O&M LINK STATE: ENABLED
Result After successful operation, service status is changed to IDLE. Refer to the Reference documentation in case alarm 3835 RNC SERVICE CONFIGURATION MISSING OR INCOMPLETE is set.
t
If you commit transport configuration because you are performing transport configuration/IP connectivity test, use ZE1C to switch to the base build after the test is completely done. 3
Switch to the base build When transport configuration/IP connectivity test is completely done, switch to the base build with the following command: ZE1C:UNLOAD:; Result COMMAND EXECUTION WILL CAUSE SYSTEM RESTART
CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT...
7.4.3.14
IP adress mapping Purpose IP address mapping is needed for auto-adaptation functionality. IP address mapping is RNCSRV-specific. 1
Interrogate mapped IP data from RNCSRV of protected PrPRNC. < ZE1P:MAPPED:221;
444
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
Result LOADING PROGRAM VERSION 1.18-0 INTERROGATING MAPPED IP DATA OF RNCSRV-221 IDX PrPRNCIP BkPRNCIP STATUS INFO ------------------------------------------------------------------------------1 10.43.5.116 10.43.6.116 VALID BTSTRANSPORT 2 10.43.5.117 10.43.6.117 VALID BTS2TRANSPORT 3 10.43.5.124 10.43.6.124 VALID IUCSTRANSPORT 4 10.43.5.132 10.43.6.132 VALID IUPSTRANSPORT COMMAND EXECUTED
2
Interrogate unmapped data from RNCSRV of protected PrRNC. < ZE1P:UNMAPPED:221; Result Listed BkPRNC's IP addresses are not paired with PrRNC's IP addresses so they are not used in auto-adaptation. LOADING PROGRAM VERSION 1.18-0 INTERROGATING UNMAPPED IP DATA OF RNCSRV-221 IDX PrPRNCIP BkPRNCIP -------------------------------------1 10.43.6.254 2 10.43.6.68 3 10.43.6.84 4 10.43.6.100 5 10.43.6.253 6 10.43.6.76 7 10.43.6.92 8 10.43.6.108 9 10.43.6.140 COMMAND EXECUTED
7.4.3.15
Auto-adaptation Auto-adaptation requires IP addresses mapping between PrPRNCs and BkPRNC. PRNCs collect the found UP IP addresses to the mapping files which are managed with MML command. You have to map PrPRNCs and BkPRNCs IP addresses manually to enable the system to choose correct source IP address at BkPRNC for the logical interfaces. Following actions still require manual work in RAN2512 in RU50EP1 release: • • •
Issue: 01F
configuring SIGTRAN's signaling configuring IP addresses configuring TWAMP
DN09146788
445
RNC solution features
RU50 Feature Descriptions and Instructions
Routing (partially) Enabling BFD (both in RNC and BTS) after resiliency switch
• •
Auto-adaptation requires IP addresses mapping between PrPRNCs and BkPRNC.
Auto-adaptation example for new BTS added or deleted in PrPRNC 1. Changes are done PrPRNC. 2. Synchronization to BkPRNC is done. 3. When download is finished, configuration test is done, need for auto-adaptation is noticed. 4. RNCSRV is loaded and auto-adapted. 5. After auto-adaptation is completed, system waits for input for example IP connectivity test execution request. 6. If no input, next RNCSRV needing auto-adaptation is loaded. 7. When all RNCSRVs are auto-adapted, base build is loaded and system waits for the next synchronization round.
g
If system cannot automatically perform the configuration, an alarm 3835 is set and commit log is written to, for example errors are not silently included.
g
If auto-adaptation would lead to making ”configured BTS ” to ”non-configured BTS” (for example due to lacking IP address mapping) the adaptation is not done.
7.4.3.15.1
Performing auto-adaptation manually
1
Add Iu/Iub UP IP address mapping rule for RNCSRV1. Type the following command: ZE1P:ADD::::INFO="";;
2
Trigger data synchronization for RNCSRV1 . ZE1S:START::::INFO="";;
Result If auto-adaptation parameter is ON, then after data synchronization, adaption will be triggered automatically. Otherwise, you need to trigger auto-adaptation manually in LOADED mode using the following command: ZE1X:START;
g 7.4.3.16
Auto-adaptation works also with synchronized scheduling.
Testing IP connectivity (optional) Purpose The IP connectivity test verifies that RNCSRV at BkPRNC has IP layer connectivity. This test can be run after a major configuration change or before redundancy switch to check the network's condition.
446
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
1
RNC solution features
Pre-check external IP connectivity. External IP connectivity pre-check for the RNC service in the BkPRNC helps to ensure that intermediate transport network configuration is correct. This is important when BkPRNC and PrPRNC are in different sites.
t
Perform this test only when RNCSRV is LOADED. Enter the following command: < ZE1T:ENABLE;
Result LOADING PROGRAM VERSION 1.17-0 IP CONNECTIVITY TEST IS ENABLED
COMMAND EXECUTED
2
Execute the test. Enter the following command: < ZE1T:START;
Result LOADING PROGRAM VERSION 1.17-0 ALL IP CONNECTIVITY WILL BE TESTED COMMAND EXECUTED
3
Show test's results Enter the following command: < ZE1T:SHOW;
Result LOADING PROGRAM VERSION *CCI* IP CONNECTIVITY TEST MODE: ENABLE INTERROGATING IP CONNECTIVITY TEST RESULT RNCSRV 017
I/F IUB
IU
PLANE O&M CP UP CP UP
TOTAL 050 050 000 005 000
SUMMARY OF THE TEST: TEST START TIME TEST TERMINATE TIME UNSUCCESS TEST PARTSUCCESS TEST SUCCESS TEST CONFIGURATION WARNING
Issue: 01F
= = = = = =
UNSUCCESS 000 050 000 004 000
2014-01-22 2014-01-22 054 000 000 051
DN09146788
PARTSUCCESS 000 000 000 000 000
SUCCESS 000 000 000 000 000
WARNING 050 000 000 001 000
10:49:31.98 10:54:01.90
447
RNC solution features
RU50 Feature Descriptions and Instructions
TOTAL TEST = 0105 DETAILED TEST REPORT CAN BE FOUND IN LOG FILE: /eclipse/BK00017J/ASWDIR/iptest221.log
4
Close Ethernet ports. Enter the following command: ZE1T:DISABLE;
Post requisites Exact time of the IP connectivity test depends on many factors like: test scope, network condition, network size. Because it is difficult to determine the test time precisely, the best way to check whether the test is still ongoing is to check TEST TERMINATE TIME field in the SUMMARY OF THE TEST: message. No value in this field means the test is still ongoing.
7.4.4 Operating and Maintaining RAN2512: Network Resiliency for RNC2600 7.4.4.1
Operating and Maintaining overview Software operation and maintenance are necessary to ensure resiliency in the protected part of the network. It is essential to ensure that SW builds and configurations of PRNCs up-to-date, and necessary IP connectivity exists. The main user interface utilized to manage the feature are MML commands. With MML commands and Service Terminal Emulator (STE) you are able to fully manage the feature. Besides of MML commands, the OMS Element Manager (OMS EM) supports most of functionalities related to the feature. In addition to legacy functions, like alarm management and the RNW DB parameter management, the following operations are supported in OMS: • • • • •
redundancy switch (RNC Service Activation and Forced RNC Service Activation) redundancy switchback (RNC Service activation in PrPRNC) enabling BACKUP Mode or to LOADED Mode in BkPRNC deleting RNC Service configuration storing synchronization configuration
Moreover, you can use OMS EM to monitor the BkPRNC and the feature in general. In practice this means that feature-related objects like BKPRNC, RNCSRV and DATSYN can be managed in OMS EM. OMS EM allows to upload and download corresponding RNCSRV's IP plan when BkPRNC is in LOADED mode. When using OMS EM you cannot perform operations like: commissioning and preconfiguration, manual data synchronization, and IP connectivity test. For more information see OMS documentation.
448
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
7.4.4.2
RNC solution features
BkPRNC-related alarms in NetAct BkPRNC is able to filter the alarms. Alarms related to RNCSRV-X are reported only to PrPRNC-X instead of being reported to all PrPRNCs. Problems impacting all RNCSRVs, like HW alarms, are nevertheless reported to all PrPRNCs.
Alarm notification mechanism for BkPRNC-related alarms in NetAct. The main tool for managing BkPRNC-related alarms is OMS EM. Because NetAct does not recognize BkPRNC, so that no alarm raised in the controller can be reported to it. If any alarm occurs in BkPRNC, the controller reports this situation to PrPRNCs, which are able to send a report about a fault occurrence directly to NetAct. With this solution, the user receives NetAct alarm notification in case of fault in BkPRNC. The mechanism is based on three alarms, ordered by fault severity: • • •
3429 CRITICAL FAULT IN BkPRNC 3436 MAJOR FAULT IN BkPRNC 3437 MINOR FAULT IN BkPRNC
These alarms do not detail what the actual problem in BkPRNC is, but indicate fault occurrences. When the operator receives an alarm he must check OMS to see what the actual alarm in BkPRNC is.
Alarm notification rules The alarm notification mechanism reports alarms according to rules based on fault severity. NetAct raises the most critical alarm depending on the severity of the faulty occurrence in BkPRNC. For example, a major fault occurs in BkPRNC. Related PrPRNC inform NetAct about it, by setting 3436 alarm, which you can see in NetAct. The alarm is set once even if several major and minor faults occur in BkPRNC at the same time. Another example illustrates how the rule works when different severity faults occur in BkPRNC at the same time. 1. 2. 3. 4.
Alarm 3436 MAJOR FAULT IN BkPRNC is set. New critical fault appears in BkPRNC at the same time. Alarm 3436 MAJOR FAULT IN BkPRNC is canceled. Alarm 3429 CRITICAL FAULT IN BkPRNC is set. NetAct reports the most critical problem. 5. The user resolved only the problem which triggered Alarm 3429 CRITICAL FAULT IN BkPRNC. 6. The problem which triggered 3436 MAJOR FAULT IN BkPRNC still exists. 7. Alarm 3436 MAJOR FAULT IN BkPRNC is set.
7.4.4.3
Managing Software This chapter presents MML commands helpful for managing PRNC software configuration.
With the commands of this command group, you can add RNC association, remove RNC association, interrogate RNC association configuration, change RNC service mode, handle synchronization, test IP connectivity, manage IP mapping and commit configuration changes. A
ADD RNC ASSOCIATION
R
REMOVE RNC ASSOCIATION
M
MODIFY RNC ASSOCIATION
I
INTERROGATE RNC ASSOCIATION
C
CHANGE RNC SERVICE MODE
S
HANDLE SYNCHRONIZATION
T
TEST IP CONNECTIVITY
P
MANAGE IP MAPPING
X
HANDLE COMMITTING AND AUTO ADAPTATION
(WM) BPSHAN - Backup Physical RNC System Handling Program's function:
New command(s) and menu text(s):
Use the commands in this command group to interrogate Backup Physical RNC System(BPS) information, start BPS fallback copying, check the BPS fallback copying status, quit BPS fallback copying, and delete BPS. D
DELETE BACKUP PHYSICAL RNC SYSTEM
I
INTERROGATE BACKUP PHYSICAL RNC SYSTEM INFORMATION
S
START BACKUP PHYSICAL RNC SYSTEM FALLBACK COPYING
P
INTERROGATE BACKUP PHYSICAL RNC SYSTEM FALLBACK COPYING
Q
QUIT BACKUP PHYSICAL RNC SYSTEM FALLBACK COPYING
This feature is managed by the parameters listed in fd_2512_5/new_parameters.
450
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
7.4.4.4
RNC solution features
Updating SW builds on BkPRNC This chapter describes procedure the user updates SW builds by upgrading PrPRNC1 build, PrPRNC2 build and BkPRNC's base build from CD1 to the CD2.
g
Build update time is approximately one hour (1h). PrPRNC requires approximately one hour to be updated. BkPRNC update requires upgrading both base build and backup builds. Approximated time depends on number of builds stored in BkPRNC.
SW update phases See Phases of SW update to check what are the phases of SW update.
BkPRNC is commissioned and SW build is stored in target BkPRNC.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
• • • • • •
•
Data synchronization had been disabled by update script: ongoing synchronization is stopped and DataSynchState is Blocked. BkPRNC update is performed at backup mode. Updating BkPRNC takes a long time. Plan the update schedule as several parts within the maintenance window. Resiliency maintenance operations (adding or deleting resiliency service) is allowed during two separate update parts. If PrPRNC is out of service, it is possible to execute resiliency switch even during BkPRNC update. After completion of the update, switch to base build's new version. In case some backup builds' update fail or operator wants to activate new base build earlier FORCE option is provided. Perform backup build verification after update. There is no need to activate backup build immediately after update. This verification is combined together with preconfigure verification, made with the following steps: – – –
•
RNC solution features
switch backup build to LOADED state update verification, like units state checking, database integrity checking connectivity verification
After updating the software, store the old backup build for restore or rollback purposes. Remove it only at next update.
Detailed instructions Detailed instructions for CD SW update on BkPRNC are delivered in the RN8.1 Update Instructions for Local SW Installation document stored in NOLS.
7.4.4.5
Synchronizing Purpose To match RNCSRV's configuration at BkPRNC with PrPRNCs configuration. Before you start
t
The synchronization takes about 40 minutes per PrPRNC, depending on RNC load, bandwidth, overall network condition. Synchronization contains:
•
RNCSRV data collection download basic adaptation configuration test
•
Manual synchronization
• • •
Trigger this synchronization when the cluster interface is in Enabled state and service status is IDLE. Use the following command: ZE1S:START:RNCSRVID Example ZE1S:START:221;
Issue: 01F
DN09146788
453
RNC solution features
RU50 Feature Descriptions and Instructions
t
221 is the RNC service ID SYNCHRONIZATION OF RNCSRV-204 WAS STARTED COMMAND EXECUTED
Result Synchronization is over when ACTIVITY MODE is BACKUP and SERVICE STATUS changes from SYNCHRONIZING to IDLE. •
Schedule Synchronization Go the specific BkPRNC and corresponding RNCSRV of the PrPRNC to be synchronized. Right-click and select Show all parameters option. Set the synchronization time by providing values for Scheduling periodic data synchronization in hours and Scheduling periodic data synchronization in minutes.
Maintaining IP connectivity Purpose This chapter describes how to perform IP external connectivity test on BkPRNC. Perform this procedure when in LOADED mode. 1
Enable external IP connectivity test possibility. Enable the test with the following command: ZE1T:ENABLE; Result LOADING PROGRAM VERSION 1.17-0 IP CONNECTIVITY TEST IS ENABLED
COMMAND EXECUTED
2
Start the test. ZE1T:START; Result LOADING PROGRAM VERSION 1.17-0 ALL IP CONNECTIVITY WILL BE TESTED COMMAND EXECUTED
3
Display test results and analyze it. ZE1T:SHOW;
454
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
Result LOADING PROGRAM VERSION *CCI* IP CONNECTIVITY TEST MODE: ENABLE INTERROGATING IP CONNECTIVITY TEST RESULT RNCSRV 0204
I/F IUB
IU
PLANE O&M CP UP CP UP
TOTAL 001 001 001 003 000
UNSUCCESS 000 000 000 000 000
PARTSUCCESS 000 000 000 000 000
SUCCESS 001 001 001 002 000
WARNING 000 000 000 001 000
SUMMARY OF THE TEST: TEST START TIME = 2013-10-14 16:21:54.79 TEST TERMINATE TIME = 2013-10-14 16:21:56.07 UNSUCCESS TEST = 000 PARTSUCCESS TEST = 000 SUCEESS TEST = 005 CONFIGURATION WARNING = 001 TOTAL TEST = 006 DETAILED TEST REPORT CAN BE FOUND IN LOG FILE: /eclipse/BK00204A/ASWDIR/iptest00 204.log
COMMAND EXECUTED
t 7.4.4.7
Detailed test is in log file: /eclipse/BK00204A/ASWDIR/iptest00204.log
Interpreting of the system logs Log interpretation is crucial for obtaining information about state of controllers configured to work in resilient network. Table 184: RNC Resiliency Logs contains information helpful for interpreting logs: • • • •
g
Test: type of performed test Description: detailed description of performed test with a list of possible statuses obtained Result: detailed description of possible statuses obtained Logs: log file name Status information, which is included in log, are for internal debugging.
Table 184 Test
RNC Resiliency Logs Description
RNC Resiliency Commit log Commit records RNC service adaptation and configuration
Issue: 01F
Results •
INCOMPLETE: means MISSING or MISMATCH.
DN09146788
Logs commit.log
455
RNC solution features
RU50 Feature Descriptions and Instructions
Table 184
RNC Resiliency Logs (Cont.)
Test
g
Description This test is done in BkPRNC .
Results
test result in commit phase. Test results are classified as INCOMPLETE, UNNECESSAR Y and COMPLETE.
–
•
Auto-adaption requires complete IP mapping configuration. If there is log complaining 'NO IPMAPPING' or 'INVALID IPMAPPING', operator needs check IP mapping configuration. UNNECESSARY: records which exist in BkPRNC but not exist in PrPRNC. UNNECESSARY IPBR/IPRO means extra IPRO configuration in BkPRNC side when comparing to PrPRNC. It has a risk that later once different IPRO is configured in PrPRNC. It may result in an inconsistent state in BkPRNC after synchronization. COMPLETE: configuration items in BkPRNC are okay.
g RNC Resiliency IPtestlog IP Test records system configuration This test issues and IP is done connectivity only in status which are BkPRNC found during IP . connectivity testing. Test results are classified as WARNING, NOK, PARTOK and OK.
•
RNC Resiliency Sync log Sync records RNC service This test adaptation and is done configuration in test result in BkPRNC synchronization . phase. Test results are classified as
•
g
g
456
MISSING means that records exist in PrPRNC but do not exist in BkPRNC. MISMATCH means that records exist both in PrPRNC and BkPRNC,but parameters mismatch.
–
•
• •
•
Logs
If EXPECTED SPC is N/A it means that a SPC is found in RNW DB but corresponding configuration does not exist in platform.
WARNING: configuration error iptest.log NOK: pinging from source to destination fails, all packets lost. PART OK: some packets lost, but connectivity is held. Packet lost rate provided, 20% packet lost rate means one packet dropped (five packets sent during IP test). OK: pinging from source to destination succeeds, no packet lost
INCOMPLETE: means MISSING or MISMATCH. –
–
DN09146788
sync.log
MISSING means that records exist in PrPRNC but do not exist in BkPRNC. MISMATCH means that records exist both in PrPRNC and BkPRNC,but parameters
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 184
RNC solution features
RNC Resiliency Logs (Cont.)
Test
Description
Results
INCOMPLETE, UNNECESSAR Y and COMPLETE.
Logs mismatch. Auto-adaption requires complete IP mapping configuration. If there is log complaining 'NO IPMAPPING' or 'INVALID IPMAPPING', operator needs check IP mapping configuration.
•
•
•
UNNECESSARY: records which exist in BkPRNC but not exist in PrPRNC. UNNECESSARY IPBR/IPRO means extra IPRO configuration in BkPRNC side when comparing to PrPRNC. It has a risk that later once different IPRO is configured in PrPRNC. It may result in an inconsistent state in BkPRNC after synchronization. COMPLETE: configuration items in BkPRNC are okay.
The directories which store the logs are available with the following commands: ZE1T and ZE1X. For more information, refer to MML Commands.
7.4.4.8 7.4.4.8.1 7.4.4.8.1.1
Network Resiliency operations Redundancy switch Activity model Figure 69: Activity model shows available Activity Modes of BkPRNC and PrPRNC and transitions between them. Figure 69
Activity model TransitionsinBackupPRNC
Waitingfor synchronization
System restart
5
6
1
TransitionsinprotectedPRNC
Active
Active
1
1
2
2
7 Backup
3 4
Loaded
Loaded
1. RNCSRV Activation. 2. RNCSRV Inactivation; 3GPP interfaces are blocked. 3. RNCSRV is set from BACKUP mode to LOADED mode; a backup build is loaded to memory for configuration and testing. 4. In BkPRNC, the base configuration package is loaded to memory.
Issue: 01F
DN09146788
457
RNC solution features
RU50 Feature Descriptions and Instructions
5. RNCSRV configuration has been deleted, or the conversion in SW upgrade has failed. 6. Initial synchronization has been completed. 7. Another RNCSRV is loaded to memory.
g 7.4.4.8.1.2
Synchronization is done at Backup mode, configuration is done at LOADED mode Use cases
Overview of possible use cases Table 185
w
Use cases
Use case
Description
Instruction
Normal redundancy switch
Normal redundancy switch
Performing normal redundancy switch from PrPRNC to BkPRNC
Forced redundancy switch
Forced redundancy switch
Performing forced redundancy switch from PrPRNC to BkPRNC
Normal redundancy switch when BkPRNC is not idle
Normal redundancy switch when BkPRNC is not idle
-
Changing RNCSRV to RNCSRV-308 at BkPRNC
Changing any RNCSRV to RNCSRV-308 at BkPRNC
-
Redundancy Switchback
Redundancy Switchback
Redundancy switchback
System recovery from redundancy conflict
System recovery from redundancy conflict
Redundancy conflict
In the following simplified examples RNCSRV, PrPRNC and BkPRNC with fixed ID numbers show the NE behavior in different use cases.
Normal redundancy switch Preconditions • • •
Resiliency association between PrPRNC and BkPRNC was created. RNC-cl interface is established. BkPRNC is in BACKUP mode.
1. Redundancy switch is executed at BkPRNC (using MML when directly connected to RNC or with OMS GUI). 2. After self-validation BkPRNC restarts. 3. RNCSRV-221 switches to LOADED mode. 4. PrPRNC wants to establish a connection and BkPRNC acknowledges it. 5. Once BkPRNC started and RNC-cl is up, BkPRNC orders PrPRNC to deactivate its RNCSRV. 6. After getting acknowledgment from PrPRNC, BkPRNC activates the RNCSRV-221.
g
458
Redundancy switch might be executed also if BkPRNC-301 has RNCSRV-221 already in LOADED mode.
6 RNCSRV-221 to ACTIVEmode ALARM;RNCSRV ACTIVATION
Forced redundancy switch
g
In forced redundancy switch BkPRNC does not try to shutdown the PrPRNC even though RNC-cl interface is up and running. Preconditions • • • •
RNC-cl interface is established. Resiliency association between PrPRNC and BkPRNC was created. RNC-cl between PrPRNC and BkPRNC is not working properly. BkPRNC is in BACKUP mode.
1. Normal PrPRNC redundancy switch fails, which is indicated by no reply from PrPRNC or PrPRNC replies with error. 2. a) BkPRNC does not recognize the status of PrPRNC, whilst RNCSRV-221 is disabled or enabled. User must verify the status and isolate PrPRNC. b) Timer expires and alarm is raised. 3. Forced redundancy switch is executed.
Forcedredundancy switch RNCSRV-221 Validation RNCSRV-221 to ACTIVEmode ALARM;RNCSRV ACTIVATION
Normal redundancy switch when BkPRNC is not idle Preconditions • •
RNC-cl interface is established. RNCSRV-221 in LOADED mode as a result of auto-adaptation.
1. Execution of redundancy switch. 2. An error indicating the ongoing auto-adaptation of RNCSRV-221 is returned. 3. The user decides to either wait or stop the adaptation. If the adaptation has been stopped it is necessary to adapt the RNCSRV-221 later once again. 4. Reset and load RNCSRV-221. 5. Execute redundancy switch. After validation, BkPRNC orders PrPRNC to deactivate its service. 6. After getting acknowledgment, BkPRNC activates the RNCSRV.
Validation Deactivate Deactivating RNCSRV-221to LOADEDmode OK
6 RNCSRV-221 to ACTIVEmode ALARM;RNCSRV ACTIVATION
Changing any RNCSRV to RNCSRV-308 at BkPRNC Preconditions • • •
RNC-cl interface is established. Redundancy switch was executed some time ago. BkPRNC-301 is running RNCSRV-221. PrPRNC-221 has no active RNCSRV. Request reported for BkPRNC-301 running RNCSRV-308 instead of RNCSRV-221.
1. Command BkPRNC-301 from the ACTIVE to the LOADED mode. 2. Load RNCSRV-308. 3. Execute redundancy switch.
Issue: 01F
DN09146788
461
RNC solution features
RU50 Feature Descriptions and Instructions
4. After validation, BkPRNC-301 orders PrPRNC-308 to deactivate its service. 5. After getting acknowledgment, BkPRNC-301 activates the RNCSRV-308. Figure 73
RNCSRV-308 to ACTIVEmode ALARM;RNCSRV ACTIVATION
Redundancy Switchback Preconditions • • •
Redundancy switch was executed. PrPRNC was restored (HW, SW and configuration). PrPRNC is in LOADED mode RNC-cl interface is established.
1. Redundancy switchback is triggered at PrPRNC. 2. After command validation, PrPRNC orders BkPRNC to deactivate RNCSRV-221. 3. After getting acknowledgment PrPRNC activates RNCSRV-221 and sets an alarm. BkPRNC stays in LOADED mode. 4. Verification of PrPRNC proper behavior after switchback.
462
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 74
RNC solution features
Redundancy Switchback
PrPRNC-221 RNCSRV-221
BkPRNC-301 RNCSRV-221
RNCSRV-221inLOADEDmode
1 Redundancy switchback
Validation
2
Deactivate
Deactivating RNCSRV-221to LOADEDmode
3 OK
RNCSRV-221 to ACTIVEmode
4a
Reset
4b ALARM;RNCSRV ACTIVATION
BACKUP mode
System recovery from redundancy conflict Preconditions • • •
1. 2. 3. 4.
Issue: 01F
Forced redundancy switch has been executed. BkPRNC-301 is running RNCSRV221. PrPRNC-221 has been just powered off. PrPRNC-221 has not been isolated. RNC-cl might be established. PrPRNC is started and it runs RNCSRV-221. PrPRNC establishes the RNC-cl and performs ”activity mode query”. When replied, PrPRNC detects the redundancy conflict PrPRNC shuts down the interfaces and remains in the LOADED mode. The redundancy conflict is cleared.
DN09146788
463
RNC solution features
RU50 Feature Descriptions and Instructions
Figure 75
1
System recovery from redundancy conflict
PrPRNC-221 RNCSRV-221
BkPRNC-301 RNCSRV-221
RNCSRV-221to ACTIVEmode
RNCSRV-221in ACTIVEmode
RNC-clestablishment
2 Activitymodequery
3
4
Redundancyconflictdetected
Deactivating RNCSRV-221 toLOADEDmode
7.4.4.8.1.3
Detecting redundancy switch necessity The user considers redundancy switch in the case of: • • •
planning and performing any maintenance actions which may cause a break in delivering controller's services catastrophe in the area where the controller's site is placed occurance of a breakdown precluding an immediate restoration of the controller
Although there is no automatic detection or triggering mechanism for redundancy switch, some existing symptoms like alarms in peer NEs, drop of KPIs or even loss of O&M connection inform the user about the necessity of the redundancy switch execution.
g
Note that if the O&M connection to PrPRNC is interrupted and forced redundancy switch was performed, there is a danger of redundancy conflict unless PrPRNC had been isolated physically. What must be taken into consideration is that in case the O&M connection to PrPRNC is interrupted and forced redundancy switch was performed, there is a danger of redundancy conflict unless PrPRNC had been isolated physically.
7.4.4.8.1.4
Comparison of prepared and unprepared redundancy switch The redundancy switch can be considered either as a prepared redundancy switch or as an unprepared redundancy switch. The difference between these two lies in the activity mode the BkPRNC is in when redundancy switch is being executed. The unprepared redundancy switch takes place when redundancy switch is executed while BkPRNC is in backup mode (for example base build SW is in memory). After redundancy switch command, a system reset takes place and the wanted RNCSRV is activated.
464
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
In prepared redundancy switch, the RNCSRV you want to activate is already in LOADED mode (for example the respective backup build SW is already in memory) when the redundancy switch is executed. The benefit of prepared redundancy switch is that no system reset, which takes several minutes, is needed when command is being executed because the correct sW is already in RNC’s memory and the RNCSRV is faster back online. Both the prepared and unprepared redundancy switch can be done in normal or forced mode. 7.4.4.8.1.5
Redundancy conflict
Origin of redundancy conflict Redundancy conflict is an undesired situation where both PrPRNC and BkPRNC are online and both of them have the same RNCId. This leads to a situation where both the PrPRNC and BkPRNC attempt to establish a connection with BTS. Because only one PRNC has BTSs under control, roughly half of the connection which are established to colliding PRNC fails. In the result, bad end user experience arise, as well as KPIs which measure Core Network decrease. Thus it is crucial to solve the redundancy conflict quickly. Redundancy conflict emerges if PrPRNC is restarted accidentally after forced redundancy switch operation. The reason is that the PrPRNC which becomes active after restart and has not been isolated properly, is not aware of the previous redundancy switch and goes online in the network. Thus the best way to prevent a redundancy conflict is to isolate the PrPRNC after redundancy switch.
Avoiding and solving redundancy conflict When PrPRNC restarts and becomes active, it establishes the RNC-cl O&M interface and performs activity mode query towards BkPRNC. If BkPRNC is active, the PrPRNC switches to LOADED mode, which means it shuts down the interfaces and goes offline. If there is RNC-cl O&M interface, the system is able to recover the redundancy conflict in few minutes after the RNC-cl O&M interface establishment. Without the interface BkPRNC does not perform the activity mode query and it is impossible to resolve the redundancy conflict automatically. Another redundancy conflict situation is when both PRNCs try to establish the Iub control plane (CP) connections to BTS. If BTS has working control plane connection, it rejects the CP establishment attempt from colliding PRNC.
Redundancy conflict in NetAct Redundancy conflict is problematic for NetAct, because NetAct cannot determine which of the connected RNCs is the correct one. In redundancy conflict situation, all RNC management operations and events in NetAct are related to the connected RNC, and not necessarily to the RNC to which the WBTSs are connected to. If redundancy conflict takes place there will be two PRNCs online with same RNC ID. In redundancy conflict the second PRNC reports the RNC to the NetAct topology without knowing the RNC is already active in another PRNC. As NetAct topology has only one instance of the RNC, the latter RNC will replace the original RNC in NetAct topology. In case the latter RNC is activated accidentally, only this one will be visible in the NetAct
Issue: 01F
DN09146788
465
RNC solution features
RU50 Feature Descriptions and Instructions
but not the RNC which has the control of the related WBTSs. The ActivePRNC parameter of the RNC object in NetAct can be used to identify which PRNC is actually connected to NetAct.
BTS behavior in a redundancy conflict A BTS is able to tolerate a redundancy conflict. It operates in a way that both the Iub control plane and O&M connections are towards the same PRNC. If a BTS has an existing Iub control plane connection to PRNC (for example to PrPRNC) and another PRNC (for example a BkPRNC) has been started accidentally, the BTS rejects the control plane connection establishment from the BkPRNC. The O&M connection follows the control plane connection in order to have them terminated in the same PRNC. If no PRNC is online, the BTS has neither an O&M nor a CP connection. As soon as the PRNC establishes the CP connection, the BTS establishes the O&M connection to the same PRNC. When the PrPRNC is not isolated properly after the redundancy switch and is able to establish a control plane connection to some of the BTSs, those BTSs are beyond the BkPRNC’s control. Therefore, it is crucial to isolate the PrPRNC after the redundancy switch.
7.4.4.8.2 7.4.4.8.2.1
Performing redundancy switch operations with MML commands Performing normal redundancy switch
1
g
Execute the redundancy switch. This action requires a confirmation. After the confirmation system is restarted automatically. At BkPRNC, enter the following command: ZE1C:ACTIVATE:221; Result LOADING PROGRAM VERSION 1.17-0 PLEASE NOTE THAT THIS RNC SERVICE'S BACKUP COMPLETENESS IS NOT 100% COMMAND EXECUTION WILL CAUSE SYSTEM RESTART CONFIRM COMMAND EXECUTION: Y/N ? CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT... RNCSRV-221 WILL BE ACTIVATED COMMAND EXECUTED
2
Check the Interface status (optional). Interrogate the state of an SCCP subsystem and its replication. Correct state indicator is STATE: AV. Execute below command after system restart: < ZNHI; Result LOADING PROGRAM VERSION 7.6-0 RNC
IPA2800
2013-10-17
09:48:12
SUBSYSTEM STATES
466
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
NETWORK: NA0 POINT H/D: 0391/00913 SP NAME: LIISA ============ ============================= ========================= DESTINATION: ROUTING: SP NO H/D SS NAME STATE RM NET SP CODE H/D NAME STATE ------ ------- ----- -- --- ------------------ ---------------- ------01/001 SCMG AV NA0 0391/00913 LIISA AV-EX 8E/142
RANAP
AV
-
NA0
0391/00913
LIISA
AV-EX
NETWORK: NA0 POINT H/D: 0607/01543 SP NAME: SGSN ============ ============================= ========================= DESTINATION: ROUTING: SP NO H/D SS NAME STATE RM NET SP CODE H/D NAME STATE ------ ------- ----- -- --- ------------------ ---------------- ------01/001 SCMG AV NA0 0607/01543 SGSN AV-EX 8E/142
RANAP
AV
-
NA0
0607/01543
SGSN
AV-EX
NETWORK: NA0 POINT H/D: 2704/09988 SP NAME: PATE4 ============ ============================= ========================= DESTINATION: ROUTING: SP NO H/D SS NAME STATE RM NET SP CODE H/D NAME STATE ------ ------- ----- -- --- ------------------ ---------------- ------01/001 SCMG AV NA0 2704/09988 PATE4 AV-EX 8E/142
RANAP
AV
-
NA0
2704/09988
PATE4
AV-EX
WPS:P; DMPG PQ PROCESSING CAPACITY AVAILABILITY: ID PPC SETUP CURRENT % AVERAGE % LOWEST % UNITS ----------------------------------------------------------------------0 DSP_POOL 99 99 99 4
DSP_POOL : PPC SETUP FOR DMPGS USING DSP POOLING DSP CAPACITY AVAILABILITY: ID SERVICE POOL CURRENT % AVERAGE % LOWEST % UNITS -------------------------------------------------------------------3 CCH 97 99 97 1 8 HS_DCH 100 100 100 6 11 HS_CCH 100 100 100 1 SERVICE POOL DESCRIPTIONS: CCH HS_DCH HS_CCH
: CCH DSP : HS_DCH DSP : HS-FACH
SERVICE ALLOCATION COUNTERS: ID SERVICE POOL CURRENT_NUMBER PEAK_NUMBER TOTAL_NUMBER ---------------------------------------------------------------------------3 CCH 2 2 2 8 HS_DCH 0 0 0 11 HS_CCH 0 0 0
3
Check the status of BkPRNC and PrPRNC. Enter the following command: < ZE1I;
Issue: 01F
DN09146788
467
RNC solution features
RU50 Feature Descriptions and Instructions
Result Activity mode in PrPRNC must be LOADED. LOADING PROGRAM VERSION 1.17-0 RNC TYPE: PROTECTED RNC PRNC ID: 221 PRNC IP: 10.63.56.215 RNC SERVICE ID: 221 ACTIVITY MODE: LOADED SERVICE STATUS: IDLE BACKUP PRNC ID: 301 BACKUP PRNC NAME: BRINE BACKUP PRNC IP: 10.62.85.16 BKPRNC ACTIVITY MODE: ACTIVE BKPRNC TLS CLIENT MODE: OFF BKPRNC ALARM STATUS: CRITICAL BACKUP COMPLETENESS: 100% BKPRNC BACKUP UPDATE TIME: 19-11-2014;14:22 BKPRNC UNKNOWN STATUS: FALSE RNC CLUSTER O&M LINK STATE: ENABLED COMMAND EXECUTED
Result Check the output of < ZE1I;. Activity in mode BkPRNC must be ACTIVE. LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: 102 RNC SERVICE ID: 102 ACTIVITY MODE: ACTIVE SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: OFF DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: 19-11-2014;14:22 BACKUP COMPLETENESS: 100% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED
468
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
7.4.4.8.2.2
RNC solution features
Performing forced redundancy switch
1
f
Execute forced redundancy switch. When forced redundancy switch is executed, there is no communication between PrPRNC and BkPRNC even though RNC-cl O&M interface exists. When you execute the forced redundancy switch, you have to isolate the PrPRNC manually to prevent the redundancy conflict where both PrPRNC and BkPRNC would be online at the same time.
g
This action requires a confirmation. After the confirmation system is restarted automatically. At BkPRNC, enter the following command: < ZE1C:ACTIVATE::221:FCD;
Result LOADING PROGRAM VERSION 1.17-0 PLEASE MAKE SURE THE RNC SERVICE IN PEER RNC HAS BEEN DEACTIVATED OR ISOLATED CONFIRM COMMAND EXECUTION: Y/N ? Y CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT... RNC SRV-221 IS ACTIVATED FORCEDLY COMMAND EXECUTED
7.4.4.8.2.3
Performing redundancy switch back
1
Execute the redundancy switchback At PrPRNC, execute below command to start the switch back < ZE1C:ACTIVATE; Result LOADING PROGRAM VERSION 1.17-0 CONFIRM COMMAND EXECUTION: Y/N ? Y CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT... RNC SERVICE IS ACTIVATED COMMAND EXECUTED
7.4.4.8.3
Performing Network Resiliency operations using OMS EM In OMS EM you can perform the following Network Resiliency operations: • • • • • • •
Issue: 01F
Show RNW Topology RNC Service Activate RNC Service Force Activation RNC Service Deactivate RNC Service Load for Configuration RNC Service Unload RNC Service Delete Backup Configuration
DN09146788
469
RNC solution features
RU50 Feature Descriptions and Instructions
Using Element Manager in OMS shows impacts from the feature on OMS Element Manager.
7.4.5 Deactivating RAN2512: Network Resiliency for RNC2600 1
Remove RNC association at PrPRNC. Delete BkPRNC object via MML command: ZE1R; Result LOADING PROGRAM VERSION 1.17-0 RNC RESILIENCY ASSOCIATION WITH PRNC-221 WILL BE REMOVED CONFIRM COMMAND EXECUTION: Y/N ? Y CONFIRM COMMAND EXECUTION: Y/N ? Y RNC RESILIENCY ASSOCIATION WITH PRNC-221 IS REMOVED SUCCESSFULLY COMMAND EXECUTED
2
Verify that the RNC association has been successfully removed. ZE1I; Result LOADING PROGRAM VERSION 1.17-0 RNC TYPE: STANDARD RNC PRNC ID: 221 PRNC IP: 10.63.56.215 RNC SERVICE ID: 221 ACTIVITY MODE: ACTIVE SERVICE STATUS: IDLE COMMAND EXECUTED
RNC RESILIENCY ADMINISTRATION COMMAND
3
Verify that the successful deletion information has been sent. The O&M application SW sends BTS O&M interface ConfigurationChangeNotification message to OMS when BkPRNC object is deleted successfully.
4
Delete the BKPRNC object at the PrPRNC object using OMS GUI.
5
Verify that the BKPRNC object in OMS has been successfully deleted.
6
Delete RNCSRV object in BkRNC. Delete RNCSRV object via MML command:
470
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
ZE1R: LOADING PROGRAM VERSION 1.17-0 RNC RESILIENCY ASSOCIATION FOR CONFIRM COMMAND EXECUTION: Y/N CONFIRM COMMAND EXECUTION: Y/N RNC RESILIENCY ASSOCIATION FOR COMMAND EXECUTED
RNCSRV-221 WILL BE REMOVED ? Y ? Y RNCSRV-221 IS REMOVED SUCCESSFULLY
Result Check the result with the following command: < ZE1I; LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: NUMBER OF RNC SERVICES DISPLAYED = 0 COMMAND EXECUTED
7
Verify that the RNCSRV object has been successfully deleted.
8
Verify that the corresponding backup build presence has been deleted. Verify that the backup build is deleted from disk, including relevant temporary files. RNC00xxxSYC is a unzip temporary folder and it only exists after data synchronization.
7.4.6 Verifying RAN2512: Network Resiliency for RNC2600 Before you start Correct configuration of PrPRNC and BkPRNC provides synchronization possibility between PrPRNC and BkPRNC, which is verified by performing redundancy switch. 1
Trigger the switchover with MML or via OMS. Follow the instructions described in Performing normal redundancy switch from PrPRNC to BkPRNC.
Result When configuration is done properly, the PrPRNC automatically shuts down 3GPP services and BkPRNC starts the services. After restart, the BkPRNC starts and the 3GPP services are back online.
Troubleshooting in case of redundancy switch failure If the RNC-cl O&M interface is down, the PrPRNC cannot be shut down from BkPRNC but it has to be shutdown manually. An alarm indicates the loss of RNC-cl O&M interface.
Issue: 01F
DN09146788
471
RNC solution features
RU50 Feature Descriptions and Instructions
IP connectivity test helps to find any problems in IP layer, what might be a reason of verification failure.
7.4.7 Testing RAN2512: Network Resiliency for RNC2600 This is an example of the verification; do not use it for the feature as such in live network. The configuration and parameter settings described are only examples and they can vary in different networks. Purpose The purpose of the test case is to verify if the RNC resiliency function is working after activating this feature. Before you start For the test case, the following network elements and equipment is used: •
Three RNCs (All have RU50EP1 installed) – – – – –
• • • •
Assume PrPRNC-221, StPRNC-1, BkPRNC-301 PrPRNC-221 and StPRNC-1 has Iur connection. BkPRNC-301 is commissioned and is not integrated. BkPRNC-301 has physical connection for Iu, Iur and Iub. BkPRNC-301 has license capacity equal or larger than the PrPRNC-221
Two Flexi BTSes, one is ATM based, the other is IP based. One CS CN (the IuBC and IuPC is optional.) One PS CN One UE
The following feature related licenses need to be activated for this test case: • • •
The basic licenses are required for the basic AMR all and PS call SFTP and SSH license RAN2512_Network_Resiliency_for_RNC2600
No parameter needs modification to perform this test case.
7.4.7.1
Setup the Network Resiliency for RNC Before you start The PrPRNC is upgraded to RU50EP1. The user installs BkPRNC from scratch. The SW build is the same as PrPRNC's. 1
g
Commission BkPRNC for resiliency. Commands are executed in BkPRNC which ID is 301 (BkPRNC-301). a) Install the RU50EP1 software package b) Install the license and make sure the license capacity is equal or larger than the PrPRNC's. c) Execute the following procedure to commission as BkPRNC: 1. < ZDDS:OMU; 2. 0000-MAN>ZLE:1,RUOSTEQX
472
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
3. 0000-RUO>Z1CM:301,2
g
301 is RNC ID, 2 is backup mode Connecting to RNW database... PRNC-301 creation (mode: backup) completed successfully at 2101-2014 14:47:05.63 Closing RNW database connection...
4. < ZE1I; LOADING PROGRAM VERSION RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: NUMBER OF RNC SERVICES DISPLAYED = 0 COMMAND EXECUTED
2
Create RNC service (RNCSRV). Type the following command: [ZE1A:] Example ZE1A:221:; Result
t
This action takes approximately 6 minutes in background, after the following system output has been displayed. LOADING PROGRAM VERSION 1.17-0 RNC RESILIENCY ASSOCIATION FOR RNCSRV-221 IS ADDED SUCCESSFULLY COMMAND EXECUTED
3
Interrogate RNC association. Check RNC is configured as standard BkPRNC with the following command: < ZE1I; Result LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 RNC SERVICE ID: 301 ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: CREATING SERVICE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00
Issue: 01F
DN09146788
473
RNC solution features
RU50 Feature Descriptions and Instructions
BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: DISABLED COMMAND EXECUTED
4
Install RAN2512 feature license and activate it. Enter the following command: ZW7L:; Result Feature code 4784 is ON.
5
Add RNC resiliency association with BkPRNC. Add RNC resiliency association with BkPRNC by creating BKPRNC object in RNW DB. This enables the RNC-cl O&M at PrPRNC. Type the following command: ZE1A::; Example < ZE1A:301:10.62.85.16:; Result RNC RESILIENCY ASSOCIATION WITH PRNC-301 WAS ADDED SUCCESSFULLY COMMAND EXECUTED
6
Start manual synchronization Start manual synchronization with the following command: ZE1S:START:;
t
The synchronization takes about 40 minutes per PrPRNC, depending on RNC load, bandwidth, overall network condition. Example ZE1S:START:221:; SYNCHRONIZATION OF RNCSRV-221 IS STARTED COMMAND EXECUTED
7
Check the RNC service status. Check the RNC service status with the following command: < ZE1I;
t
474
It is recommended to check the status at time when the synchronization is ongoing.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
Result ACTIVITY MODE changes from WAITING FOR SYNCHRONIZATION to BACKUP after synchronization is finished. SERVICE STATUS changes from SYNCHRONIZING to IDLE after synchronization is finished. LOADING PROGRAM VERSION 1.17-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: RNC SERVICE ID: 221 ACTIVITY MODE: WAITING FOR SYNCHRONIZATION SERVICE STATUS: SYNCHRONIZING DATA CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: NO BACKUP DATA FOR RNC SERVICE BACKUP COMPLETENESS: 0% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED
8
Pre-configure RNCSRV. The commands are executed in BkPRNC-301. a) Switch to backup build: < ZE1C:LOAD:221; COMMAND EXECUTION WILL CAUSE SYSTEM RESTART
CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT...
RNCSRV-221 WILL BE LOADED COMMAND EXECUTED
Show software package information: < ZWQO:CR; LOADING PROGRAM VERSION 15.10-0 PACKAGES CREATED IN OMU:
DEF
SW-PACKAGE ACT
STATUS
DIRECTORY
ENVIRONMENT
PACKAGE-ID (REP-ID) DELIVERY
Issue: 01F
DN09146788
475
RNC solution features
RU50 Feature Descriptions and Instructions
CD-ID
-
Y
QX144600 Y
BK00301 Y
BU
NW
QX144600
QX 14.46-0
QX 14.46-0
CID000QX 15.1-0
BK00301_11
QX 14.26-2
QX 14.26-2
CID000QX 15.2-0
b) Check whether BACKUP COMPLETENESS is INCOMPLETED before transport configuration is done. Interrogate RNC association: < ZE1I; LOADING PROGRAM VERSION *CCI* RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: 221 RNC SERVICE ID: 221 ACTIVITY MODE: LOADED SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: 19-11-2014;14:22 BACKUP COMPLETENESS: LESS THAN 100% RNC CLUSTER O&M LINK STATE: ENABLED NUMBER OF RNC SERVICES DISPLAYED = 1
9
Configure BkPRNC. Configure BkPRNC according to the Table 183: Configuration matrix. Table 186
Configuration matrix
Already done in Necessary for entire base build BkPRNC
Necessary for each RNCSRV
No
a) b) c) d) e) f) g) h) i)
a) Cabling configuration
Yes
476
Ethernet configurations VLAN configuration Configure IP addresses Configure Iu-CS control plane Configure Iu-PS control plane Configure Iu-CS user plane1 Configure Iu-PS user plane1 Configure IuB user plane1 Configure BTS O&M
a) Ethernet configurations b) VLAN configuration
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 186
RNC solution features
Configuration matrix (Cont.)
Already done in Necessary for entire base build BkPRNC
Necessary for each RNCSRV
c) Configure IP addresses d) Configure Iu-CS control plane2 e) Configure Iu-PS control plane2 1
Optional if auto-adaptation is enabled.
2
Optional if RNCSRVs have common destinations.
10 Commit transport configuration. a) Commit configuration < ZE1X:START; LOADING PROGRAM VERSION 1.17-0 COMMITTING CONFIGURATION CHANGE IS STARTED COMMAND EXECUTED
b) Check configuration committing status •
< ZE1X:SHOW; LOADING PROGRAM VERSION CONFIGURATION COMMITTING RESULT: START TIME = 2014-01-22 10:43:10.94 TERMINATE TIME = 2014-01-22 10:45:17.25 CONFIGURATION TEST = SUCCESS ADAPTATION = SUCCESS DETAILED REPORT CAN BE FOUND IN LOG FILE: /eclipse/BK00017J/ASWDIR/commit221.log COMMAND EXECUTED
•
< ZE1I; LOADING PROGRAM VERSION 1.18-0 RNC TYPE: BACKUP RNC PRNC ID: 301 PRNC IP: 10.62.85.16 LOADED RNC SERVICE: 221 RNC SERVICE ID: 221 ACTIVITY MODE: LOADED SERVICE STATUS: IDLE CBC SOURCE IP: 0.0.0.0 AUTO ADAPTATION: ON DATA SYNC STATE: UNBLOCKED DATA SYNC SCHEDULE: -,00:00 BACKUP UPDATE TIME: 19-11-2014;14:22 BACKUP COMPLETENESS: 100% RNC CLUSTER O&M LINK STATE: ENABLED
Issue: 01F
DN09146788
477
RNC solution features
RU50 Feature Descriptions and Instructions
NUMBER OF RNC SERVICES DISPLAYED = 1 COMMAND EXECUTED
Result After successful operation, service status is changed to IDLE. Refer to the Reference documentation in case alarm 3835 RNC SERVICE CONFIGURATION MISSING OR INCOMPLETE is set.
t
If you commit transport configuration because you are performing transport configuration/IP connectivity test, use ZE1C to switch to the base build after the test is completely done. 11 Pre-check external IP connectivity. External IP connectivity pre-check for the RNC service in the BkPRNC helps to ensure that intermediate transport network configuration is correct. This is important when BkPRNC and PrPRNC are in different sites.
t
Perform this test only when RNCSRV is LOADED. Enter the following commands: < ZE1T:ENABLE; Result LOADING PROGRAM VERSION 1.17-0 IP CONNECTIVITY TEST IS ENABLED
COMMAND EXECUTED
12 Execute the test. Enter the following command: < ZE1T:START; Result LOADING PROGRAM VERSION 1.17-0 ALL IP CONNECTIVITY WILL BE TESTED COMMAND EXECUTED
13 Show test's results Enter the following command: < ZE1T:SHOW; Result LOADING PROGRAM VERSION *CCI*
478
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
IP CONNECTIVITY TEST MODE: ENABLE INTERROGATING IP CONNECTIVITY TEST RESULT RNCSRV 017
I/F IUB
IU
PLANE O&M CP UP CP UP
TOTAL 050 050 000 005 000
UNSUCCESS 000 050 000 004 000
PARTSUCCESS 000 000 000 000 000
SUCCESS 000 000 000 000 000
WARNING 050 000 000 001 000
SUMMARY OF THE TEST: TEST START TIME = 2014-01-22 10:49:31.98 TEST TERMINATE TIME = 2014-01-22 10:54:01.90 UNSUCCESS TEST = 054 PARTSUCCESS TEST = 000 SUCCESS TEST = 000 CONFIGURATION WARNING = 051 TOTAL TEST = 0105 DETAILED TEST REPORT CAN BE FOUND IN LOG FILE: /eclipse/BK00017J/ASWDIR/iptest221.log
7.4.7.2
Normal redundancy switch from PrPRNC to BkPRNC Before you start
•
Resiliency association between PrPRNC-221 and BkPRNC-301 has been created. RNC-cl O&M is configured and permeable. BkPRNC-301 is in BACKUP mode. The RNC supports basic CS call, PS call. Iur interface is working.
1
Make the CS call, PS call and do inter-RNC handover to StPRNC-1.
• • • •
Result Calls and Iur handover are successful. 2
Execute the redundancy switch. ZE1C:ACTIVATE:221:; LOADING PROGRAM VERSION 1.17-0 PLEASE NOTE THAT THIS RNC SERVICE'S BACKUP COMPLETENESS IS NOT 100% COMMAND EXECUTION WILL CAUSE SYSTEM RESTART CONFIRM COMMAND EXECUTION: Y/N ? CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT... RNCSRV-221 WILL BE ACTIVATED COMMAND EXECUTED
Result • •
Issue: 01F
BkPRNC-301 restarts and switch to active RNCSRV-221. PrPRNC-221 deactivates its RNCSRV-221.
DN09146788
479
RNC solution features
RU50 Feature Descriptions and Instructions
No relevant alarm raise up.
•
g
There some other expect behaviors which might be seen during testing: • • • • • • •
3
PrPRNC-221 switches to LOADED mode permanently. BTSOM and IuB connection will re-establish to BkPRNC-301. CN connection will re-establish to BkPRNC-301. IuR connection will re-establish to BkPRNC-301. OMS connection will re-establish to BkPRNC-301. IuBC connection will re-establish to BkPRNC-301. IuPC connection will establish to BkPRNC-301.
Make the CS call, PS call and do inter-RNC handover to StPRNC-1. After all the signaling links in BkPRNC-301 are created, make the CS call, PS call and do the Inter-RNC handover to StPRNC-1. Result Performing calls finished with success.
7.4.7.3
Redundancy switchback from BkPRNC to PrPRNC Before you start
•
Resiliency switchover has been done. RNC-cl O&M is configured and permeable. PrPRNC-221 is in LOADED mode.
1
Make the CS call, PS call and do inter-RNC handover to StPRNC-1.
• •
Make the CS call, PS call and do Inter-RNC handover to StPRNC-1 when the RNCSRV-221 is in BkPRNC-301. Result Calls and Iur handover are successful. 2
Start the switch back from PrPRNC. Execute the below command to start the switch back from PrPRNC: < ZE1C:ACTIVATE; Result LOADING PROGRAM VERSION 1.17-0 CONFIRM COMMAND EXECUTION: Y/N ? Y CONFIRM COMMAND EXECUTION: Y/N ? Y OPERATION IS STARTED AND IT MAY TAKE A FEW MINUTES,PLEASE WAIT... RNC SERVICE IS ACTIVATED COMMAND EXECUTED
3
Make the CS call, PS call and do inter-RNC handover to StPRNC-1. After all the signaling links in PrPRNC-221 are created, make the CS call, PS call and do the Inter-RNC handover to StPRNC-1.
480
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
Result Performing calls finished with success.
7.4.8 Appendix 1: Term Bank Table 187
Descriptions of feature-related terms
Term
Descriptions
Adaptation
Replacing the local information of PrPRNC by local information of BkPRNC.
Auto-adaptation
Adaptation done automatically according to mapping tables configured by the user.
Automatic procedure of autoadaptation
The sequence of auto-adaptations of all BkRNCSRVs, including automatic loading of each BkBuild before doing the auto-adaptation for it.
Backup build
A build that BkPRNC runs when certain RNC service was selected for operation.
t Backup configuration
Configuration package of a backup build. Backup configuration consists of global part that is copied from PrPRNC and local part that is configured by operator using MML (or using OMS EM, when it becomes available).
t Base build
See also: Base configuration, Preconfiguring
A build that BkPRNC runs when no RNC service has been selected for operation.
t Base configuration
See also: Base build.
See also: Backup build.
Configuration package of the base build.
t
See also: Backup configuration.
BkPRNC
Backup PRNC - PRNC that can back up the RNC services of up to 16 PrPRNCs.
BTS (WBTS)
WCDMA BTS
BTSOM
BTS O&M application protocol - the protocol used in RNC O&M I/F, BTS O&M I/F and RNC-cl O&M I/F.
BTS O&M I/F
BTS O&M interface - O&M interface between RNC and BTS, using BTSOM as the protocol.
t
See also RNC O&M I/F and RNC-cl O&M I/F.
BTSSM
BTS site manager
Build
Collection of programs and files performing required functions of a system. BkPRNC has a base build for the PRNC and a backup build per each related PrPRNC. In RNC2600 build consists of configuration data and SW image.
cRNC
Classic RNC
Issue: 01F
DN09146788
481
RNC solution features
Table 187
RU50 Feature Descriptions and Instructions
Descriptions of feature-related terms (Cont.)
Term
Descriptions
t Configuration (package)
See IPA-RNC
The whole configuration of a build, which does not contain the SW image.
t
See also: Build.
Configuration committing
A command which tells to the system that the user configuration is done and is ready for configuration adaptation and integrity check.
Conversion
Converting a configuration package from old SW build to new SW build.
g IPA-RNC
Conversion is not particularly related to RNC resiliency. Conversion is done at any SW upgrade, with or without resiliency.
IPA-RNC - Old RNC HW •
HW: Cabinets, subracks, different PIUs
•
OS: DMX, Chorus, OSE
•
Platform: IPA2800
LRNC
Logical RNC - RNC as defined by 3GPP. See also PRNC, RNC, RNC service. In standard system, LRNC is 1-1 with RNC and PRNC. In RAN2512, LRNC is 1-1 with RNC but 1-2 with PRNC.
NetAct
Nokia product for network management
OMS
O&M server for RNC.
Object configuration
Configuration of the local part of a backup configuration, which includes the adaptation rules. Operator configure required objects any time after first synchronization but before activating the RNC service. A manual configuration step must be done when RNCSRV is created in BkPRNC, and at certain modifications.
PRNC
Physical RNC - RNC HW and SW. This term is introduced because BkPRNC cannot be called as a RNC. It does not run RNC service but waits to be switched on in case of PrPRNC outage.
t
See also LRNC, RNC, RNC service.
PrRNC
Protected RNC - RNC that has more than one redundant RNC service, one in PrPRNC and another in BkPRNC
Redundancy conflict
The undesirable situation where certain RNC is active in more than one PRNC simultaneously. Redundancy conflict is a new fault scenario introduced by RNC resiliency. Redundancy conflict could happen for example, if redundancy switch to BkPRNC is done when PrPRNC is down and thus the RNC service in PrPRNC cannot be deactivated. If then PrPRNC recovers and if operator has not physically isolated it, there will be redundancy conflict. In redundancy conflict, network may not work, because other NEs may connect to more than one PRNC simultaneously.
Redundancy switch
Switch of (activity of) certain RNC from PrPRNC to BkPRNC. Two redundancy types can be distinguished:
482
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 187
RNC solution features
Descriptions of feature-related terms (Cont.)
Term
Descriptions •
•
Prepared redundancy switch: redundancy switch where the activating RNCSRV has been raised to LOADED mode before commanding the switch. Unprepared redundancy switch: redundancy switch where the activating RNCSRV not been raised LOADED mode before commanding the switch.
Redundancy switchback
Switch of (activity of) certain RNC from BkPRNC to PrPRNC.
RNC
Common meaning: Radio network controller. In RNC pool context also: Logical functionality that can run simultaneously as an RNC service in a PRNC.
RNC activity mode
Defines the state in which the RNCSRV is. Values are: waiting for synchronization, backup, loaded and active.
RNC area
Geographical area covered by the BTSs and cells that the RNC controls.
RNC-cl O&M I/F
RNC cluster O&M interface (Informally Cluster O&M interface) - O&M interface between two RNCs, using BTSOM as the protocol.
t RNC O&M I/F
See also BTS O&M I/F and RNC O&M I/F.
RNC O&M interface - O&M interface between OMS and RNC, using BTSOM as the protocol.
t
See also BTS O&M I/F and RNC-cl O&M I/F.
RNC resiliency group
A BkPRNC and all the PrPRNCs protected by it.
RNC service
The instance of an RNC in certain PRNC.
t RNCSRV activation / deactivation
See also LRNC, PRNC, RNC.
Transition between different RNC modes which can be a separate operation or a phase of redundancy switch or switchback. • •
RNCSERV activation refers to RNC mode changed from LOADED to ACTIVE RNCSERV deactivation refers to RNC mode changed from ACTIVE to LOADED
. Service status
Defines what the BkPRNC is actually doing. This is useful with long lasting operations. Some values are: Idle, creating RNC service, synchronizing data.
StPRNC
Standard PRNC - PRNC that does not participate in RNC resiliency.
Synchronization
Automatic fetching of configuration package of certain RNC service from corresponding PrPRNC and adaptation to BkPRNC according to adaptation rules.
Issue: 01F
DN09146788
483
RNC solution features
RU50 Feature Descriptions and Instructions
7.4.9 Appendix 2: Miscellaneous notes Table 188
Limitations
Limited area
Description of the limitation
Network and network element management tools
•
•
•
Software management
•
BkPRNC is not visible in NetAct as individual RNC object if RNCSRV is not active in BkPRNC. In this case, the status of BkPRNC is visible in NetAct through parameters of RNC object of PrPRNC. When RNCSRV is active, BkPRNC takes the role of PrPRNC in NetAct. Do not to execute RNW or IP plan uploads or downloads at PrPRNC during synchronization because of high risk of plan operation failure. Do not execute synchronization when planned operation is ongoing because of risk of synchronization failure. The failure or success of the operation depends on the phase of other ongoing operation. TRIAL configuration TRIAL configuration is a standard upgrade method applicable only when updated PrPRNC's RNCSRV is in ACTIVE mode. Nevertheless, there are some restrictions related to this method:
1. During TRIAL configuration resiliency relevant operation are rejected.
2. When RNCSRV is in LOADED mode, any TRIAL relevant operation is rejected.
g
TRIAL is strongly forbidden in BkPRNC. Because BkPRNC operates after the user performed redundancy switch, there is usually no active RNCSRV.
7.5 RAN3047: RTT Improvement to enhance user experience management data 7.5.1 Description of RAN3047: RTT Improvement to enhance user experience management data Introduction to the feature This feature will reduce RTT RNC delay in an end to end environment.
7.5.1.1
Benefits End-user benefits This feature provides better end user experience in terms of RTT delay.
Operator benefits The feature provides faster data transfer for interactive applications and background traffic.
484
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
7.5.1.2
RNC solution features
Requirements Software requirements Table 189: Software requirements lists the software required for this feature. Table 189
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
Flexi Direct OMS RNC
Flexi BTS
RU50
Flexi Direct RU50
RN8.0
mcRNC4.1
ADA6.0
Support not Support required not required
Flexi Lite BTS
Flexi 10 BTS
NetAct
MSC
SGSN
MGW
Support not required
Support not required
NetAct 8 Support not Support not Support not EP1/ required required required NetAct 8 EP2 (NetAct 15)
UE Support not required
Hardware requirements This feature requires no new or additional hardware.
7.5.1.3
Functional description Functional overview This feature enables faster data transfer for interactive applications and background traffic by reducing delay in data handling, and push end to end HSPA RTT delay for a 32 Byte Ping with 2 ms UL TTI. Improvement in Round Trip Time (RTT) is achieved by reducing the delay components in the data path between the network and UE. The feature focuses on reducing RNC internal processing delay in HS(D)PA Downlink data path. Reduction of RTT improves the response times for interactive services and faster data transfer for background traffic, thereby enhancing the user experience.
7.5.1.4
System impact Interdependencies between features This feature has no feature interdependencies.
Impact on interfaces This feature has no impact on interfaces.
Impact on commands There are no commands related to this feature.
Issue: 01F
DN09146788
485
RNC solution features
RU50 Feature Descriptions and Instructions
Impact on network and network element management tools This feature has no impact on network management or network element management tools.
Impact on system performance and capacity This feature has no impact on system performance or capacity.
7.5.1.5
RAN3047: RTT Improvement to enhance user experience management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms There are no alarms related to this feature.
Measurements and counters There are no key performance indicators related to this feature at this time.
Key performance indicators There are no key performance indicators related to this feature.
Parameters There are no key performance indicators related to this feature at this time.
7.5.1.6
Sales information Table 190
Sales information
BSW/ASW
SW component
License control in network element
BSW
RAN
Not defined
7.6 RAN2671: Upgrading of mcBSC to mcRNC 7.6.1 Description of RAN2671:Upgrading of mcBSC to mcRNC Overview The huge growth of traffic expected has brought new challenges to radio network elements. To satisfy current and future needs, Nokia has developed a novel, compact, and highly scalable Multicontroller Platform which enables operators to provide the needed capacity in an unrivaled footprint. Both mcBSC and mcRNC hardware are based on the Multicontroller hardware Platform. The platform is made so that mcBSC and mcRNC can share most of the hardware. When the network changes and more capacity
486
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
is required for mcRNC, the mcBSC modules can be transformed to mcRNC modules by making minor HW changes in the module and/or by installing the corresponding SW. This hardware solution provides relatively low-cost and low-effort possibility to: • •
7.6.1.1
transform mcBSC modules in order to set up new mcRNC reuse existing or transformed mcBSC modules in order to expand mcRNC capacity
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits Secure mcBSC hardware investment in GSM by reuse of mcBSC HW module(s) for mcRNC in WCDMA network.
7.6.1.2
Requirements Software requirements Table 191: Software requirements lists the software required for this feature Table 191
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
OMS
BTS Flexi
Flexi Lite
RU50 EP1
Support not required
Support not required
mcRNC4.1
Support not required
Support not required
Support not required
BTS Flexi 10`
NetAct
MSC
OMS
SGSN
MGW
UE
Support not required
Support not required
Support not required
Support not required
Support not required
Support not required
Support not required
Hardware requirements Depending on the actual mcBSC to mcRNC upgrade scenario, some new hardware is required for this feature: • •
t
BMPP2-B add-in cards backplane cables The minimum mcRNC configuration is made from two mcRNC modules, hence when only one mcBSC module is transformed into mcRNC module, the user must buy additional mcRNC module.
For more details see Upgrade scenarios. This feature is applicable only to mcRNC Rel2. HW BMPP2-B add-in cards
Issue: 01F
DN09146788
487
RNC solution features
RU50 Feature Descriptions and Instructions
According to mcBSC hardware architecture, there are some specific add-in cards which are not supported in mcRNC. During the upgrading from mcBSC to mcRNC, those must be replaced or removed. Table 192: mcBSC module card changes requirements shows overall the amount of add-in cards to be replaced or removed according to mcBSC module type. Table 192
mcBSC module card changes requirements
mcBSC module type
Required BMPP2-B add-in cards
mcBSC PS extension module
0
mcBSC TRX extension module
2
mcBSC basic modules
7
Power and grounding cables
w
Necessary power and grounding cables might be reused from mcBSC if the module is located in the same cabinet and in the same location of the cabinet. Customer must order cable sets depending on upgrade scenario: • •
new mcRNC set up mcRNC capacity expansion
Table 193
Cable set for new RNC set up
Obtained capacity step
Cable sales item
Quantity
S1-B2
mcRNC 3157 S1 inter-module basic cable set
1
mcRNC 3158 S1 inter-module secondary cable set
1
mcRNC 3157 S1 inter-module basic cable set
1
mcRNC 3152 S1 to S3 inter-module cable set
1
mcRNC 3157 S1 inter-module basic cable set
1
mcRNC 3152 S1 to S3 inter-module cable set
1
mcRNC 3153 S3 to S7 inter-module cable set
1
S3-B2
S7-B2
For more information on cabling and connecting modules into full mesh topology, please refer to Multicontroller RNC Hardware Description. Table 194
The mcBSC is fully compliant with any core network supporting IP based GSM access network and it is fully optimized to most modern and efficient IP only transmission solutions. Depending on the capacity needs, one mcBSC consists of two to several modules. Seven reference capacity steps are used in current mcBSC. They differ in the number of BCN modules used, from two (step 1) to eight (step 7). mcBSC with Rel2 hardware is built with four module types, Typically, the hardware combination consists of BCN-B box and BMPP2 add-in cards. Each module type of mcBSC with Rel2 hardware consists of below add-in cards: Main module • • • •
2x BJC-A, Jasper Forest Card 6x BMPP2-B, Octeon II Card
PS extension module •
8x BMPP2-B, Octeon II Card
Basic standalone mcBSC configuration consists of two modules (mcBSC basic modules). Additional capacity steps are available by steps of one mcBSC TRX extension module to increase TRX and PS data connectivity. Maximum TRX connectivity can be reached with capacity step 4 containing 5 modules, and on top of that, even higher PS data connectivity can be reached with additional mcBSC PS data extension modules. Maximum configuration with BCN-B hardware consists of 8 modules. For more information, please see Multicontroller BSC and Multicontroller Transcoder Product Description.
490
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
mcRNC introduction Figure 77
Multicontroller RNC capacity steps AMC1
S7-B2 (step7)
AMC2
RESET PO NS A1 SER
SFP+0
SFP+2
SFP+4
SFP+6
SFP+12
SFP+14
SFP+16
SFP+18
SFP+20
SFP+22
MGT
LAN2
A2 ALARM2
USB3
AMC1
SAS
Trace
SFP+1
SFP+3
SFP+5
SFP+11
SFP+13
SFP+153
SFP+17
SFP+19
SFP+21
LAN1
SFP+0
SFP+2
SFP+4
SFP+6
SFP+12
SFP+14
SFP+16
SFP+18
SFP+20
SFP+22
LAN2
USB1/ 2
SYNC2
ALARM1
SYNC1
ALARM2
SYNC2
P1
P5
P2
P6
P3
P7
P4
P8
AMC2
RESET PO NS A1 SER
USB3
AMC1
SAS
Trace
SFP+1
SFP+3
SFP+5
SFP+11
SFP+13
SFP+153
SFP+17
SFP+19
SFP+21
LAN1
MGT
USB1/ 2
A2
ALARM1
SYNC1
P1
P5
P2
P6
P3
P7
P4
P8
S5-A1 (step 5)
AMC2
RESET PO NS A1 SER
SFP+0
SFP+2
SFP+4
SFP+6
SFP+12
SFP+14
SFP+16
SFP+18
SFP+20
SFP+22
MGT
LAN2
A2 ALARM2
USB3
AMC1
SAS
Trace
SFP+1
SFP+3
SFP+5
SFP+11
SFP+13
SFP+153
SFP+17
SFP+19
SFP+21
LAN1
SFP+0
SFP+2
SFP+4
SFP+6
SFP+12
SFP+14
SFP+16
SFP+18
SFP+20
SFP+22
LAN2
USB1/ 2
SYNC2
ALARM1
SYNC1
ALARM2
SYNC2
P1
P5
P2
P6
P3
P7
P4
P8
AMC2
RESET PO NS A1 SER
USB3
AMC1
SAS
Trace
SFP+1
SFP+3
SFP+5
SFP+11
SFP+13
SFP+153
SFP+17
SFP+19
SFP+21
LAN1
MGT
USB1/ 2
A2
ALARM1
SYNC1
P1
P5
P2
P6
P3
P7
P4
P8
S3-B2 (step3)
AMC2
RESET PO NS A1 SER
SFP+0
SFP+2
SFP+4
SFP+6
SFP+12
SFP+14
SFP+16
SFP+18
SFP+20
SFP+22
MGT
LAN2
A2 ALARM2
USB3
AMC1
SAS
Trace
SFP+1
SFP+3
SFP+5
SFP+11
SFP+13
SFP+153
SFP+17
SFP+19
SFP+21
LAN1
SFP+0
SFP+2
SFP+4
SFP+6
SFP+12
SFP+14
SFP+16
SFP+18
SFP+20
SFP+22
LAN2
USB1/ 2
SYNC2
ALARM1
SYNC1
ALARM2
SYNC2
P1
P5
P2
P6
P3
P7
P4
P8
AMC2
RESET PO NS A1 SER
USB3
AMC1
SAS
Trace
SFP+1
SFP+3
SFP+5
SFP+11
SFP+13
SFP+153
SFP+17
SFP+19
SFP+21
LAN1
MGT
USB1/ 2
A2
ALARM1
SYNC1
P1
P5
P2
P6
P3
P7
P4
P8
S1-B2 (step1)
AMC2
RESET PO NS A1 SER
SFP+0
SFP+2
SFP+4
SFP+6
SFP+12
SFP+14
SFP+16
SFP+18
SFP+20
SFP+22
MGT
LAN2
A2 ALARM2
USB3
AMC1
SAS
Trace
SFP+1
SFP+3
SFP+5
SFP+11
SFP+13
SFP+153
SFP+17
SFP+19
SFP+21
LAN1
SFP+0
SFP+2
SFP+4
SFP+6
SFP+12
SFP+14
SFP+16
SFP+18
SFP+20
SFP+22
LAN2
USB1/ 2
SYNC2
ALARM1
SYNC1
ALARM2
SYNC2
P1
P5
P2
P6
P3
P7
P4
P8
AMC2
RESET PO NS A1 SER
USB3
SAS
Trace
SFP+1
SFP+3
SFP+5
SFP+11
SFP+13
SFP+153
SFP+17
SFP+19
SFP+21
LAN1
MGT
USB1/ 2
A2
ALARM1
SYNC1
P1
P5
P2
P6
P3
P7
P4
P8
DN09122897
The mcRNC is highly optimized for the IP network environment. The Multicontroller module is tightly integrated and has only a few field-replaceable parts. The key enablers of this approach are IP/Ethernet technology and advanced CPU technology. The mcRNC consists of a number of similar BCN modules which are connected internally by cables. Depending on the capacity needs, the latest mcRNC with Rel2 hardware can consist of two,four, or eight modules. Every module consists of BCN-B box and BMPP2-B add-in cards. The possible module types for Rel2 hardware are either mc01B or mc02B. The difference between mc01B and mc02B is that mc01B has a hard Disk AMC and mc02B does not. The main components of mc01B are: • •
Issue: 01F
8x BMPP2-B, Octeon II Card HDS30-A, 300GB HDD
DN09146788
491
RNC solution features
RU50 Feature Descriptions and Instructions
The main components of mc02B are: •
8x BMPP2-B, OcteonII Card
Basic mcRNC configuration with Rel2 HW consists of two mc01B modules. The supported mcRNC Rel2 hardware capacity expansion is to add two mc02B modules to mc01B basic modules for S3-B2, then add four more mc02B modules to S3-B2 for S7B2. For more information, please see Multicontroller RNC Product Description.
Upgrade scenarios The target of reusing mcBSC hardware for mcRNC is mainly for two user scenarios: • •
492
mcRNC hardware expansion commissioning a new mcRNC with transformed mcBSC modules
Using mcBSC modules to expand existing mcRNC • • • • •
mcBSC modules can be transferred into mcRNC using module by module or multiple modules at the same time mcBSC PS data extension modules and mcBSC TRX extension modules have to be transferred first into mcRNC use last two modules to be transferred at the same time into mcRNC use are mcBSC basic modules maximum number of modules in a mcRNC configuration is eight perform mcRNC HW expansion procedures with the transformed mcBSC modules, procedures are described: –
Issue: 01F
for S1-B2 to S3-B2 expansion in RAN2874: mcRNC HW Capacity Expansion Support feature description
DN09146788
493
RNC solution features
RU50 Feature Descriptions and Instructions
–
w
for S3-B2 to S7-B2 expansion in RAN2959: mcRNC Step 7 Support feature description eSW off-line upgrade for the transformed mcBSC module is mandatory - procedure is described in the Upgrading embedded software chapter in the Commissioning Multicontroller RNC HW Rel.2.
Using mcBSC modules to set up new mcRNC • • •
the complete mcBSC configuration (maximum eight modules) can be transferred into mcRNC use at the same time a part of mcBSC can be transferred into mcRNC use (minimum number of modules in an mcRNC configuration is two) perform a clean installation, which is described in the Clean installation in the Commissioning Multicontroller RNC HW Rel.2
Hardware modification from mcBSC module to mcRNC module
For mcBSC PS extension module - no change to mcRNC PS extension module
• • •
494
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 79
•
Issue: 01F
RNC solution features
mcBSC PS extension module necessary changes
For mcBSC TRX extension module - slot 1,2 add-in cards are removed, and replaced with BMPP2- B
DN09146788
495
RNC solution features
RU50 Feature Descriptions and Instructions
Figure 80
•
496
mcBSC TRX extension module necessary changes
For mcBSC Spare module - slot 1, 2, and 3 add-in cards are removed and replaced with BMPP2- B (PTU (BSAC-A) is removed)
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 81
•
Issue: 01F
RNC solution features
mcBSC Spare module necessary changes
For mcBSC main module - slot 1, 2, 3, and 8 add-in cards are removed and replaced with BMPP2- B (PTU (BSAC-A) is removed)
DN09146788
497
RNC solution features
RU50 Feature Descriptions and Instructions
Figure 82
7.6.1.4
mcBSC main module necessary changes
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.
498
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
RNC solution features
Impact on commands This feature has no impact on commands.
Impact on network and network element management tools This feature has no impact on network management or network element management tools.
Impact on system performance and capacity This feature has no impact on system performance or capacity.
7.6.1.5
RAN2671:Upgrading of mcBSC to mcRNC management data 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 existing parameters related to this feature.
7.6.1.6
Sales information Table 195
Issue: 01F
Software requirements
BSW/ASW
SW component
License control in network element
BSW
RAN
Not defined
DN09146788
499
BTS solution features
RU50 Feature Descriptions and Instructions
8 BTS solution features 8.1 RG302084/RAN2556/LTE1556: 3-RAT RF Sharing 2G-3G and 2G-4G 8.1.1 Description of RG302084/RAN2556/LTE1556: 3-RAT RF Sharing 2G-3G and 2G-4G Introduction to the feature This feature allows WCDMA-GSM and LTE-GSM RF sharing on one site, using one GSM System Module. Synchronization between all the System Modules is needed.
g
SRAN Feature availability with the SRAN 15 Release C5 - including RG40 (GSM 15), RU50 EP1 (WCDMA 15) and RL70 (FDD-LTE 15)
Benefits Operator benefits This feature provides the following benefits to the operator: Smooth LTE introduction to the existing WCDMA-GSM RF sharing site. Cost savings by reusing the existing WCDMA/GSM RF Modules.
• •
Requirements Hardware and software requirements Table 196
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Flexi Zone Micro OMS
RL70
-
LBTS7.0
-
-
UE
NetAct
MME
SAE GW
-
NetAct 15.2
-
-
Table 197
500
LTE Hardware and software requirements
WCDMA Hardware and software requirements
RAS
Flexi Direct IPA-RNC
RU50 EP1
Support not required
mcRNC
OMS
Flexi BTS
Flexi Lite BTS
Support not Support not Support not Support not Support not required required required required required
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
g
BTS solution features
Flexi 10 BTS
NetAct
MSC
SGSN
MGW
UE
WN9.1
NetAct 8 EP2 (NetAct 15)
Support not required
Support not required
Support not required
Support not required
The feature requires also GSM support. The GSM SW requirements are to be declared. Additional hardware requirements This feature requires no new or additional hardware.
Functional description Figure 83
3-RAT RF sharing architecture overview
2Gmanagement
3Gmanagement
4Gmanagement
NetAct Q3
NWI3
NWI3
OMS
FlexiBSC
IOMS
RNC
OMU
OMU
Abis IP
sync reference
FlexiMultiradio BTSGSM
FlexiMultiradio BTSWCDMA
FlexiMultiradio BTSLTE
Dedicated RFM Shared RFM
Dedicated RFM Shared RFM
RP3-01 sync
3-RAT RF sharing site consists of three System Modules, one for each technology: • • •
Issue: 01F
ESMB/C for GSM FSMF for WCDMA FSMF for LTE
DN09146788
501
BTS solution features
RU50 Feature Descriptions and Instructions
Both SIMO and MIMO can be used on WCDMA or LTE side, SIMO or IDD on GSM side. WCDMA and LTE can have additional dedicated RF Modules, within the limits of the System Module's optical connectivity and baseband capacity. Two RP3 optical connections for O&M purposes are needed: • •
between WCDMA and GSM between WCDMA and LTE
The frequency or phase synchronization (1PPS/ToD) is fed via Sync IN/OUT ports, from LTE to WCDMA and from WCDMA to GSM. The shared band can be combined with any valid cell set dedicated for LTE.
System impact Interdependencies between features The following features are required: • • •
LTE447/BSS21520: SW support for RF sharing GSM-LTE RAN1770/BSS21403: RF Sharing WCDMA-GSM LTE1710/RAN3001: Sync Hub Direct Forward
Impact on interfaces This feature has no impact on interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature impacts system capacity as follows: • •
In WCDMA, comparing to regular RF sharing WCDMA-GSM, one additional RP3 port is occupied for O&M connection with LTE System Module. The GSM System Module's capacity is divided between RF sharing WCDMA-GSM and LTE-GSM.
Management data 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
502
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 198
BTS solution features
Modified parameters
Full name
Abbreviated name
Managed object
Shared RF Technologies
sharedRfTechnologies
MRBTS
Link list
linkList
SMOD
Synchronization master
syncMaster
SMOD
Technology
technology
SMOD
Connection list
connectionList
RMOD
Sales information Table 199
Sales information
RAT
BSW/ASW
SW component
License control in network element
Activated by default
GSM
ASW
N/A
License controlled per BCF
No
WCDMA
BSW
RAN
N/A
Yes
LTE
BSW
N/A
N/A
Yes
8.2 RAN3010: 24 Cell Support with Flexi FSMF + FSMD/E System Modules 8.2.1 Description of RAN3010: 24 Cell Support with Flexi FSMF + FSMD/E System Modules Introduction to the feature Up to 24 cells per BTS is supported with FSMF + FSMD/E System Modules.
8.2.1.1
Benefits Operator benefits Evolution for multicarrier, multiband and multisector sites with FSMF + FSMD/E.
8.2.1.2
Requirements Software requirements Table 200: Software requirements lists the software required for this feature.
Issue: 01F
DN09146788
503
BTS solution features
RU50 Feature Descriptions and Instructions
Table 200
Software requirements
RAS
RNC
IPA-RNC
mcRNC
BTS Flexi
Flexi Lite
RU50 EP1
Support not required
Support not required
Support not required
WN9.1
Support not required
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
WN9.1
NetAct 8 EP2 (NetAct 15)
Support not required
Support not required
Support not required
Support not required
Hardware requirements Flexi Multiradio System Module FSMF as master System Module and Flexi Multimode System Module FSMD/E as extension System Module are required. Flexi WCDMA System Module FSMB is not supported. This feature is not supported with single-sector and dual-sector Radio Modules.
8.2.1.3
Functional description 24 cells are supported with FSMF as master System Module and FSMD/E as extension System Module. The master System Module can have zero, one or two Capacity Extension Sub-Modules (FBBA). RF Modules needs to be connected to master System Module. Two OBSAI links between Master and extension System Module is required. Maximum amount of cells per BTS is 24. More than 12 cells configurations need additional 6 WCDMA cell activation license key: • •
13-18 cells configuration: one additional LK 19-24 cells configuration: two additional LKs
The required transport mode is IP Iub. For supported configurations please see "Flexi Multiradio BTS WCDMA Supported and Planned Configurations" and "Flexi Multiradio BTS RF Sharing Released Configurations".
8.2.1.4
System impact Current Implementation 18 cells per BTS with FSMF + FSMD/E configuration is supported
Interdependencies between features Supplementary Internal Information Requires RAN2732: Flexi System Module extension, FSMF + FSMD/E.
504
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
BTS solution features
Impact on interfaces This feature has no impact on interfaces.
Impact on MML commands There are no MML commands related to this feature.
Impacts on network and network element management tools This feature has no impact on network management and network element management tools.
Impacts on system performance and capacity This feature has no impact on system performance and capacity.
8.2.1.5
Sales information Table 201
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
Not defined
8.2.2 Activating RAN3010: 24 cell support with Flexi FSMF + FSMD/E System Modules Purpose Follow the procedure below to activate the RAN3010: 24 cell support with Flexi FSMF + FSMD/E System Modules. Before you start The BTS must be already commissioned. The BTS Site Manager (BTSSM) can be connected to the BTS either locally or from a remote place.
1
Start the WCDMA BTS Site Manager application and establish the connection to the BTS.
2
Commission the feature a) Start commissioning. b) Select Local cell groups in use ► Sector based grouping. c) Commission 1 LCG on MSM (FSMF) and 1 LCG on ESM (SM Rel2 – FSMD or FSME) and 24 cells.
Result The feature RAN3010: 24 cell support with Flexi FSMF + FSMD/E System Modules is activated.
Issue: 01F
DN09146788
505
BTS solution features
RU50 Feature Descriptions and Instructions
8.2.3 Deactivating RAN3010: 24 cell support with Flexi FSMF + FSMD/E System Modules Purpose To deactivate the RAN3010: 24 cell support with Flexi FSMF + FSMD/E System Modules feature, follow this procedure. 1
Recommission the BTS. To deactivate the 24 cell support with Flexi FSMF + FSMD/E System Modules feature, simply commission cell only on MSM.
8.2.4 Verifying RAN3010: 24 cell support with Flexi FSMF + FSMD/E System Modules Purpose Follow steps below to verify that the activation of the RAN3010: 24 cell support with Flexi FSMF + FSMD/E System Modules feature has been successful. 1
Check if all cells are up and running. Calls are possible.
8.2.5 Testing RAN3010: 24 cell support with Flexi FSMF + FSMD/E System Modules Purpose To activate the RAN3010: 24 cell support with Flexi FSMF + FSMD/E System Modules. Test environment • • • • • • • •
One System Module hardware Release 3 FSMF (472181A) with two FBBAs (472182A) and transmission sub-module FTIF (472311A) One System Module hardware Release 2 FSME (471469A) Two RF Module hardware Release 3 FRGT (472810A) Eight SFPS FOSH (472579A) in sockets FSMF RF/EXT1, FSMF RF/EXT2, FBBA RF/EXT, FSME OPT-EXT 1, FSME OPT-EXT 2 and FRGT OPT1 One fiber link (472894A) connection between FSMF1 RF/EXT1 and FRGT1.1.1 OPT1 One fiber link (472894A) connection between FSMF1 RF/EXT2 and FRGT1.2.1 OPT1 One fiber link (472894A) connection between FBBA2 RF/EXT and FSME2 OPT-EXT 1 One fiber link (472894A) connection between FBBA3 RF/EXT, FSME2 OPT-EXT 1
CCCH Processing Set = 6, Flexi WCDMA BTS Second Carrier Support = 18,
1)
506
WCDMA RAN, Rel. RU50, Operating Documentation, Issue 02 > Operate and Maintain > Monitor and Measure > Managing WCDMA RAN and Flexi Direct Capacity > Multiradio Flexi BTS WCDMA capacity > BTS baseband capacity.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
BTS solution features
•
20W Incremental Power Licence Key for Flexi = 18,
•
Additional 6 WCDMA Cell Activation = 2.2)
On the other hand, this configuration should support a feature3). Thus, for the test purpose, these licences have been loaded: • • • • • • • • • • • • • • • • • •
RAN2887: CCCH Processing Set = 99 RAN2123: Flexi BTS Gigabit Baseband (R99 CE capacity*) = 2000 RAN2123: Flexi BTS Gigabit Baseband (HSDPA BTS processing set 3*) = 99 RAN2123: Flexi BTS Gigabit Baseband (HSDPA BTS processing set 2*) = 99 RAN2123: Flexi BTS Gigabit Baseband (HSDPA BTS processing set 1*) = 99 RAN1001: Flexi WCDMA BTS Second Carrier Support = 18 RAN2225: 20W Incremental Power Licence Key for Flexi = 18 RAN3017: Additional 6 WCDMA Cell Activation = 2 RAN1702: Frequency Domain Equalizer RAN1308: HSUPA Interference Cancellation Receiver RAN1254: Timing over Packet for BTS Application SW RAN119: Antenna Alarm with Receiver Signal Comparison RAN908: Flexi WCDMA BTS AISG MHA Support RAN906: Flexi WCDMA BTS 3GPP Antenna Tilt Support RAN907: Antenna Line Supervision RAN905: Flexi WCDMA BTS MHA support RAN849: HSDPA Proportional Fair Resource Packet Scheduler RAN764: HSDPA 16QAM support
Before you start The BTS has to be already commissioned according to RAN2732, on air, OAM connected. The BTS Site Manager (BTSSM) can be connected to the BTS either locally or from a remote place. 24 cells should be crated and configured in OMS.
2) 3)
Issue: 01F
WCDMA RAN, Rel. RU50, Operating Documentation, Issue 02 > System Descriptions > WCDMA RAN License Operation > Licenses in WCDMA RAN. Other features are out of scope of RAN3010 and should be activated and tested according to their own procedures.
DN09146788
507
BTS solution features
RU50 Feature Descriptions and Instructions
Figure 84
BTS configuration according to RAN2732
508
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
BTS solution features
1
Start Commissioning page ‘Local Cell Resources’.
2
Check box ‘20W incremental power for flexi in use’.
3
Create 12 cells (A Type configuration)4) and assign them to FRGT module 1.1.1. Figure 85
Create 12 cells (A Type configuration)4 and assign them to FRGT module 1.2.1 Figure 86
510
Local Cell Resources 24 cells
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
BTS solution features
5
Go to commissioning page ‘WCDMA Carrier Candidates and Local Cell Group Settings’
6
In table ‘Carrier candidates and local cell groups’ assign fields ‘local cell’ 1-12 to ‘Local cell group’ 1 and ‘local cell’ 13-24 to ‘Local cell group’ 2 Figure 87
WCDMA Carrier Candidates and Local Cell Group Settings
Result Check if all cells are up and running without any fault. The feature RAN3010: 24 cell support with Flexi FSMF + FSMD/E System Modules is activated.
Issue: 01F
DN09146788
511
BTS solution features
RU50 Feature Descriptions and Instructions
Figure 88
BTS configuration according to RAN3010
8.3 RAN3017: Additional 6 WCDMA Cell Activation 8.3.1 Description of RAN3017: Additional 6 WCDMA Cell Activation Introduction to the feature RAN3017: Additional 6 WCDMA Cell Activation license key increases the number of supported cells in the BTS configuration. Step size of one license key is 6 cells. In RU50 the number of cells can be up to 18.
8.3.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits Increasing traffic, demand for multicarrier, multiband, and multi-sector sites leads operator needs towards larger BTS site configurations, especially in hot spot areas. This feature enables to build such configurations with simple SW configuration.
512
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
8.3.1.2
BTS solution features
Requirements Software requirements Table 202: Software requirements lists the software required for this feature. Table 202
Software requirements
RAS
Flexi Direct
IPA-RNC
mcRNC
Flexi Direct RNC
OMS
Flexi Multiradio BTS
RU50
Not planned
Support not required
Support not required
Not planned
Support not required
WN9.0
MGW
UE
Flexi Lite BTS
Flexi NetAct Multiradio 10 BTS
MSC
Not relevant
WN9.1
Support not Support not Support not Support not required required required required
NetAct 8 EP1 (RU50)
SGSN
NetAct 8 EP2 (NetAct 15)
Hardware requirements This feature requires Flexi Multiradio System Module (FSMC/D/E) or Flexi Multiradio 10 System Module (FSMF).
8.3.1.3
Functional description Functional overview Site configuration enables creation up to 12 cells without a license key. To activate additional 6 cells in BTS configuration a license key (LK) is required. Table 203
g
Number of needed license keys
Number of cells
License keys
0 - 12
0 x LK
13 - 18
1 x LK
Need for license key(s) is checked based on the RNC cell setup. Note that after the SW upgrade to WN9.x, the LK has to be provided within two weeks. Otherwise, additional cells stop working. In case of a site that has more than 12 cells, after the upgrade to WN9.x, this feature is automatically switched on. If the extendedBtsSiteCapacity parameter is off and additional cells are not active, this feature remains switched off also in WN9.x.
Issue: 01F
DN09146788
513
BTS solution features
8.3.1.4
RU50 Feature Descriptions and Instructions
System impact Interdependencies between features Currently, RAN2736 Extended BTS Site Capacity license key is needed if BTS site configuration has more than 12 cells. RAN3017: Additional 6 WCDMA Cell Activation replaces the existing solution. Note that old RAN2736 license keys are not converted to new license keys.
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 enables the operator to enlarge site configuration by adding new cells.
8.3.1.5
RAN3017: Additional 6 WCDMA Cell Activation management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms Table 204: Existing alarms lists existing alarms related to this feature. Table 204
Existing alarms
Alarm ID
Alarm name
7660
BASE STATION LICENCE EXPIRED Related fault: 1885: EFaultId_MissingLicenseAl
7661
BASE STATION LICENCE NOTIFICATION Related fault: 1885: EFaultId_MissingLicenseAl
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 205: Modified parameters lists parameters modified by this feature.
514
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 205
8.3.1.6
BTS solution features
Modified parameters
Full name
Abbreviated name
Managed object
Extended BTS site capacity enabled
extendedBtsSiteCapacity
BTSSCW
Sales information Table 206
Sales information
BSW/ASW
SW component
License control in network element
ASW
RAN
BTS LK
8.3.2 Activating RAN3017: Additional 6 WCDMA Cell Activation Purpose Follow the procedure below to activate the RAN3017: Additional 6 WCDMA Cell Activation. Before you start Make sure you have access to the BTS Site Manager.
g
Note that this feature is under license control. This feature requires a valid license file. The feature code is 0000005171. See WCDMA RAN License Operation document for details.
1
Start the WCDMA BTS Site Manager application and establish the connection to the BTS. Flexi Multiradio BTS WCDMA can autonomously request for missing license file(s) from NetAct Licence Manager during feature activation (RAN2131: Automatic Licence Distribution to Flexi BTS). Make sure that you have selected Automatic licensing in use checkbox in the Automatic License Distribution Settings page.
g
If RAN2131: Automatic Licence Distribution to Flexi BTS is not activated, relevant license must be uploaded manually.
2
Upload the configuration plan file from the BTS. When BTS Site Manager is connected to the BTS, it automatically uploads the current configuration plan file from the BTS. •
3
Select View ► Commissioning or click Commissioning on the View bar.
Activate RAN3017: Additional 6 WCDMA Cell Activation feature. Go to Local Cell Resources page and select the Extended BTS site capacity enabled checkbox.
Send the commissioning plan file to the BTS. Click Send Parameters button. You might save the parameters at this point.
5
The new commissioning plan file is automatically activated in the BTS. BTS Site Manager automatically sends an activation command after finishing the file download.
6
Select Next to complete the commissioning. You can save the commissioning report, if required.
7
Backup commissioning files (if applicable). Select File ► Backup commissioning files Save the complete backup commissioning file for further use.
Result The feature RAN3017: Additional 6 WCDMA Cell Activation is activated.
8.3.3 Verifying RAN3017: Additional 6 WCDMA Cell Activation Purpose Follow steps below to verify that the activation of the RAN3017: Additional 6 WCDMA Cell Activation feature has been successful. 1
Start BTS Site Manager application and establish the connection to the BTS.
2
Upload the configuration plan file from the BTS. When BTS Site Manager is connected to the BTS, it automatically uploads the current configuration plan file from the BTS.
516
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
•
3
BTS solution features
Select View ► Commissioning or click Commissioning on the View bar.
Verify that Extended BTS site capacity enabled checkbox is selected. The value of BTSSCW extendedBtsSiteCapacity parameter should be true. Additionally, verify on the main page that all created cells are working: • • •
local cell state is "Operational" operational state is "Enabled" working state is "Working"
Disable RAN3017: Additional 6 WCDMA Cell Activation feature. Go to Local Cell Resources page and remove the selection from the Extended BTS site capacity enabled checkbox.
4
Complete the recommissioning procedure.
8.4 RAN2860/LTE1266: BTS and BTS Site Reset Support 8.4.1 Description of RAN2860/LTE1266: BTS and BTS Site Reset Support Introduction to the feature The RAN2860/LTE1266: BTS and BTS Site Reset Support feature introduces the base transceiver station (BTS) reset in addition to the BTS Site reset. In previous releases, BTS resets have been treated as BTS site reset by BTS Flexi 10 and Flexi Lite BTS.
Issue: 01F
DN09146788
517
BTS solution features
RU50 Feature Descriptions and Instructions
The long term evolution (LTE) or wideband code division multiple access (WCDMA) system module supports traffic aggregation from co-sited other BTS by quality of service (QoS) aware Ethernet switching. To support the required high availability in SRAN15, SR000441: BTS and BTS Site Reset Support feature is introduced. The RAN2860/LTE1266: BTS and BTS Site Reset Support feature introduces separated reset for BTS (excluding TRS) and BTS site (including TRS) and maximizes the availability of the aggregation features.
g
SRAN Feature availability with the SRAN 15 Release C5 - including RG40 (GSM 15), RU50 EP1 (WCDMA 15) and RL70 (FDD-LTE 15).
Benefits End-user benefits This feature does not directly affect end-user experience. However, it provides higher end-user availability, which can be achieved with the RAN2860/LTE1266: BTS and BTS Site Reset Support feature. Operator benefits This feature provides the following benefits to the operator: •
•
• •
The customer requires the highest availability of each radio access technology (RAT) on a multiradio or Single RAN site with an integrated aggregation of the transport master. Only when absolutely required, the aggregated traffic (for example of GSM BTS) will be impacted by aggregation master reset. Without the feature. in order to reach the needed availability, the customer would need to buy expensive cell site gateways, instead of using the integrated aggregation function of the BTS. The customer can remove one additional single point of failure (cell site gateway). The customer can reduce OPEX when using integrated transport, for example, no additional HW, SW maintenance, lower footprint, less cabinets, and so on.
Requirements Hardware and software requirements Table 207
518
WCDMA hardware and software requirements
RAS
Flexi Direct RU50
Flexi Direct RNC
IPA-RNC
mcRNC
OMS
BTS Flexi Flexi Lite
RU50 EP1
Not planned
Support not required
Support not required
Support not required
Support not required
Support not required
WL9.1
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
WN9.1
NetAct 8 EP2 (NetAct 15)
Support not required
Support not required
Support not required
Support not required
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 208
BTS solution features
LTE hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10
Flexi Zone Micro mcRNC
RL70
LBTS7.0
LBTS7.0
not applicable
-
UE
NetAct
MME
SAE GW
-
-
-
-
Additional hardware requirements This feature requires no new or additional hardware.
Functional description The BTS triggers a BTS reset instead of a BTS site reset in the following situations: • • • •
fatal error from SW activation of a new configuration with reset is required (if transport functionality is not affected) BTS reset requested by the operator from the site manager, from the NetAct, or from the OMS. BTS reset requested by SON functionality
In all these use cases, the transport for chained BTSs stays available. Without the feature, there is an interruption in transport that causes a temporary unavailability for the chained BTS as well. Details on implementation: • • • •
During the BTS application reset, Transport SW continues to run on top of lower level SW while the rest of BTS SW is reset. This feature implements the transport SW independence from the platform SW (CC&S). New supervisor component in the platform SW monitors HW, Transport SW, and start-up during BTS reset. For robustness, escalation from unsuccessful BTS reset to BTS site reset is introduced.
Figure 90
Application example
Co-sited BTS (LTE/WCDMA/GSM)
Ethernet
g
Issue: 01F
FlexiMultiradio 10 BTS - FSMF
Ethernet
Backhaul Network
It is recomemded to wait for six minutes after the BTS startup before using the feature.
DN09146788
519
BTS solution features
RU50 Feature Descriptions and Instructions
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 management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity.
Management data 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 209
Sales information
BSW/ASW
License control in network element
Activated by default
BSW
-
yes
8.5 RAN3168: Flexi 3-sector RF Module 900 (FXJB) 8.5.1 Description of RAN3168: Flexi 3-sector RF Module 900 (FXJB) Introduction to the feature The feature introduces Flexi Multiradio RF Module (FXJB) for 900 MHz J-band.
520
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
8.5.1.1
BTS solution features
Benefits Operator benefits The Flexi 3-sector RF Module 900 (FXJB) can be used as a WCDMA RF Module. This feature benefits the operator as follows: • • • • • • • • • • • • • • •
8.5.1.2
the most cost-efficeint as well as size- and weight-optimized 3-sector BTS Site industry leading RF integration level SW configurable radio: the same RF Module for LTE, HSPA+ and WCDMA and GSM/EDGE 3-sector RF in one outdoor IP65 box wide operating temperature range: -35°C to +55°C the lowest power consumption and OPEX ability to be used as feederless site with one DC and 1...2 optical cables ability to build a TX div and 2TX MIMO with two 3-sector RF Modules with an extra RF redundancy option one 3-sector module being more cost effective than three Remote Radio Head (RRH) in feederless installations lesser weight lesser wind load 1/3 of DC and optical cabling compared to the site with an RRH easy installation minor visual impact ability to operate as a powerful 1-sector RRH: 80 + 80 W 2TX MIMO with HW prepared for 4RX
Requirements Software requirements The following table lists software required for this feature.
RAS
Flexi Direct IPA-RNC
RU50 EP1
Support not required
Table 210
Issue: 01F
mcRNC
OMS
Flexi Multiradio BTS
Support not Support not Support not WN9.1 required required required
Flexi Lite BTS
Support not required
Software requirements
Flexi NetAct Multiradio 10 BTS
MSC
SGSN
MGW
UE
Support not required
Support not required
Support not required
Support not required
Support not required
Support not required
DN09146788
521
BTS solution features
RU50 Feature Descriptions and Instructions
Hardware requirements This feature requires new hardware.
8.5.1.3
Functional description The FXJB module is seen in the WCDMA mode as a 3 x 80 W 900 MHz 3TX/6RX RF Module. TX/RX bandwidth is 25 MHz. The main features of the FXJB are as follows: • • •
3GPP 900MHz J-band supported 3 U high with Flexi platform mechanics ability to be used in feederless BTS sites (optical and DC cable up to 200 m)
The following are some basic WCDMA configurations: • •
g 8.5.1.4
up to 4+4+4 cells 8, 20, 40, 60 or 80 W mode per sector (by SW licenses) FXJB is available from WN9.1 2.0 onwards.
System impact Interdependencies between features There are no interdependencies between features.
Impact on interfaces There is no impact on interfaces.
Impact on network and network element management tools There is no impact on network and network element management tools.
Impact on system performance and capacity There is no impact on system performance and capacity.
8.5.1.5
RAN3168: Flexi 3-sector RF Module 900 (FXJB) management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
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.
522
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
BTS solution features
Parameters There are no new or modified parameters related to this feature.
8.5.1.6
Sales information Table 211
Sales information
BSW/ASW
SW component
License control in network element
Not defined
RAN
Not defined
8.6 RAN2784: Flexi Lite BTS 1900 MHz 8.6.1 Description of RAN2784: Flexi Lite BTS 1900 MHz Introduction to the feature Flexi Lite BTS 1900 (FQFA) is a small, all-in-one base station optimized for indoor and outdoor microcell environment. The product design, hardware and software is based on the award winning Flexi Multiradio BTS platform. Figure 91
Issue: 01F
Flexi Lite BTS 1900
DN09146788
523
BTS solution features
8.6.1.1
RU50 Feature Descriptions and Instructions
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature benefits the operator as follows: •
•
•
8.6.1.2
The product can be used in pico- and microcellular applications and also as a coverage fill-in solution. The main use case is in capacity limited networks where the operator needs to start using smaller cells to be able to deliver the required system capacity. Output power is high enough to support indoor coverage building from outdoor sites. It is also high enough to drive distributed antenna system for indoor coverage. It also supports 2TX MIMO. Supports WCDMA/HSPA services.
Requirements Software requirements Table 212: Software requirements lists the software required for this feature.
RAS
Flexi Direct IPA-RNC
RU50 EP1
Not relevant Support not Support not OMS3.1 required required
Table 212
mcRNC
OMS
Flexi Multiradio BTS
Flexi Lite BTS
Not relevant
WL9.1
Software requirements
Flexi NetAct Multiradio 10 BTS
MSC
SGSN
MGW
UE
Not relevant
Support not required
Support not required
Support not required
Support not required
NetAct 8 EP2 (NetAct 15)
Hardware requirements This feature requires no new or additional hardware.
8.6.1.3
Functional description Flexi Lite BTS 1900 is integrated, small in size, lightweight base station which can be installed on walls or poles (IP65). The output power level is adjustable from 5 W + 5 W down to 250 mW + 250 mW in ~1 dB steps for micro cells.
524
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
BTS solution features
Flexi Lite BTS offers flexible deployments options at walls, lamp posts, utility poles, billboards or other street furniture. Typical micro-cell outdoor antenna deployments are below roof-top in heights of about 5 to 15 meters above the ground level. Typical indoor deployments include exhibition halls, shopping malls, large office spaces, airports etc. Antenna height in indoor installations is typically from 2 to 5 meters above ground level. In indoors Flexi Lite BTS is to be mounted either on the wall or connected to an external distributed antenna system. Flexi Lite BTS consists of the following elements: • • • •
core base station module optional integrated antenna optional visual cover optional pole and wall installation kits
Flexi Lite BTS can be mounted on a wall or on a pole with the supplied hardware. Active cooling enables minimum installation clearance, so Flexi Lite BTS can be installed in locations that are not much larger than BTS itself (~12.5 l), for example in utility rooms, inside cabinets (any position possible). All cabling is accessible without dismounting the unit.
Air interface configuration Flexi Lite BTS 1900 has two transceivers: two 5 W transmitters and two -121 dBm (tunable down to -107 dBm in steps) receivers. Flexi Lite BTS operates at band 2: • •
UL: 1850-1910 MHz DL: 1930-1990 MHz
Transport Flexi Lite BTS uses IP as a standard transport protocol. Ethernet, both wireline and fiber, is the standard interface in the Flexi Lite BTS.
8.6.1.4
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 is a new base station designed for pico- and microcellular sites and also as a coverage fill-in solution. The main use case is for capacity-limited networks where the operator needs to start using smaller cells to be able to deliver the required system capacity.
Impact on system performance and capacity This feature has no impact on system performance or capacity.
Issue: 01F
DN09146788
525
BTS solution features
8.6.1.5
RU50 Feature Descriptions and Instructions
RAN2784: Flexi Lite BTS 1900 MHz management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms Information on alarms and faults related to Flexi Lite BTS can be found in Flexi Lite BTS Faults.
Measurements and counters Information on measurements and counters related to Flexi Lite BTS can be found in Flexi Lite BTS Counters.
Key performance indicators There are no key performance indicators related to this feature.
Parameters Information on parameters related to Flexi Lite BTS can be found in Flexi Lite BTS WCDMA Parameters and Flexi Lite BTS Transport Module Parameters.
8.6.1.6
Sales information Table 213
Sales information
BSW/ASW
SW component
License control in network element
BSW
RAN
Not defined
8.6.2 Testing RAN2784: Flexi Lite BTS 1900 MHz 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.
Test Case 1: BTS reset from RNC/OMS Purpose This test case checks the reset scenario with Flexi Lite BTS. Before you start Test environment: • •
526
Operational radio access network (RAN) and core network (CN) UE that supports 1900 MHz UTRAN band
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
1
BTS solution features
Make calls through the tested BTS. The calls have to last.
2
Enter the BTS reset command from RNC/OMS.
3
Make calls in every cell. Possible alarms have to be checked.
Expected outcome 1. Calls are successful. 2. BTS reset command is executed correctly and the corresponding modules are reset. BTS start-up is successful. LEDs and BTS Site Manager indicate the start-up procedure. All cells are configured according to the defined RNC parameters. Channel element status is checked from snapshot. 3. Calls are successful and no unexpected alarms are visible.
Test Case 2: RAB Services HSPA Multi-RAB Purpose This test case checks the supported RAB combinations with Flexi Lite BTS. Multi NRT RABs on HSPA allow mapping of multiple NRT PS RABs to HSPA channel, either alone or in combination with AMR and/or RT PS. This feature offers users with multiple NRT services the benefit of high speed packet throughput. Both channel types DCH/HS-DSCH and E-DCH/HS-DSCH are supported. For RAB combinations that involves streaming service. Before you start Test environment:
•
Operational RAN and PS-CN domain connected to the IP network Iub interface analyzer UEs that support 1900 MHz UTRAN band Megamon, Emil
1
Establish multi-RAB service and start the data transfers.
• • •
Two RABs should be established - one 12.2 kbps AMR voice call and one background HSDPA data download service. 2
Radio Link Reconfiguration. Verify the utilized channel types for RABs. Service quality for each RAB is verified as specified in the test plan. Channel element status can be checked in snapshot.
Issue: 01F
DN09146788
527
BTS solution features
RU50 Feature Descriptions and Instructions
3
Disconnect all RABs. Channel release can be verified in snapshot.
Expected outcome 1. Multi-RAB service and data transfers are successfully established. 2. Service quality for each RAB is acceptable. Voice call and HSDPA throughput are stable. Channel elements reservation is correct (used uplink CE and downlink CE, available CE). This can be checked in snapshot (keyword: INF/TCOM/LRM).
g
One rel. 3 sub-unit provides capacity of 96 Rel99 CE. There are 3 baseband sub-units in Flexi Lite BTS. The traffic capacity is 1.875 sub-units with small HSPA configuration. For HSDPA + AMR multi-RAB service, resources for the AMR service need to be allocated. For more information, see Dimensioning WCDMA RAN: Flexi Lite BTS Baseband. 3. All RABs are properly released. Call is successfully terminated.
Test Case 3: Handover Preconditions Cell 1 is a cell within Flexi Lite BTS. Flexi has two frequency layers. Cell 2 is one of the cells within Flexi BTS set to be intra-frequency with cell 1. Cell 3 is one of the cells within Flexi BTS set to be inter-frequency adjacent with cell 1. Purpose This test case checks the intra/inter frequency handovers between Flexi Lite BTS and Flexi Multiradio BTS. The event identity used in this test case is as follows: • • •
Event 1A triggers the radio link addition (softer HO) or radio link setup (soft HO), and active set update procedures. Event 1B triggers the radio link deletion and active set update procedures. Event 1F triggers the inter-frequency and/or inter-RAT (GSM) measurements.
Step 2-5: intra-frequency handover. Step 6-9: inter-frequency handover. All the procedures can be monitored in ICSU log. Before you start Test environment: • • • • • •
528
Operational RAN and PS-CN domain connected to the IP network Flexi Multiradio BTS Iub interface analyzer Adjustive attenuator Megamon, Emil UEs that support 1900 MHz UTRAN band
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
1
BTS solution features
Attenuate cell 2 and 3. Establish the RAB service(s) to UE via cell 1. Cell 2 and 3 are attenuated so that UE cannot detect these cells. Quality has to be verified during the test period.
2
Decrease cell 2 attenuation until event 1A is triggered. In case of HSDPA and HSUPA, first adjust the attenuator to the level so that UE can “hear” cell 1 better than cell 2, then attenuation of cell 2 is further decreased until (EDCH)/HS-DSCH serving cell change is triggered because of CPICH Ec/No reason.
3
Increase cell 1 attenuation until event 1B is triggered.
4
Decrease cell 1 attenuation until event 1A is triggered. In case of HSDPA and HSUPA, first adjust the attenuator to the level so that UE can “hear” cell 2 better than cell 1, then attenuation of cell 1 is further decreased until (EDCH)/HS-DSCH serving cell change is triggered because of CPICH Ec/No reason.
5
Increase cell 2 attenuation until event 1B is triggered.
6
Increase cell 1 attenuation until event 1F is triggered. The BTS enters CM mode.
7
Decrease cell 2 attenuation until HO is triggered.
8
Increase further cell 1 attenuation, so that HO to that cell is not possible. Increase cell 2 attenuation until event 1F is triggered The BTS enters CM mode.
9
Decrease cell 1 attenuation until HO is triggered.
10 RAB service is terminated. Expected outcome 1. RAB service(s) is (are) successfully established. 2. The intra-frequency measurements and criteria (event 1A) message from UE indicates to the RNC to initiate the radio link setup for cell 2 and the procedure is successful. UE's active set update is successful. In case of HSPA, the (E-DCH)/HS-DSCH serving cell change from cell 1 to cell 2 is successfully done after cell 2 attenuation has been decreased. DL throughput might be instantaneously dropped because MAC-hs entity changes. UL data transfer and AMR in case of Multi-RAB are not affected. Radio Link Reconfiguration Prepare, Radio Link Reconfiguration Ready, and Radio Link Reconfiguration Commit messages are correct.
Issue: 01F
DN09146788
529
BTS solution features
RU50 Feature Descriptions and Instructions
3. The intra-frequency measurements and criteria (event 1B) message from UE indicates to the RNC to initiate the radio link deletion for cell 1 and the procedure is successful. The active set update procedure removes cell 1 from the active set of the UE. Channel release is done correctly. Quality is acceptable. 4. Results as in step 2. 5. Results as in step 3. 6. The intra- and inter-frequency measurement and criteria (event 1F) message from UE indicates to the RNC to initiate the Compressed Mode preparation procedure. The activation of CM and the correct CM parameters are signaled to the BTS and UE. If E-DCH is used, it is switched to DCH before CM is triggered as CM is not supported by HSUPA. UE sends intra- and inter-frequency measurement results to the RNC. But HO is not triggered because of high attenuation in the target cell. The deactivation of the CM is signaled correctly. After a while the correct CM parameters are signaled again, CM is activated. 7. Intra- and inter-frequency measurements indicate to the RNC to initiate the radio link setup procedure. The radio link setup to the cell 3 is successful. New radio resources are indicated by physical channel reconfiguration procedure. In case of HSUPA, DCH is switched to E-DCH in cell 3. New AAL2 connections are established for (EDCH)/HS-DSCH and old AAL2 connections are released. The radio link is deleted from cell 1 with radio link deletion procedure. 8. Results as in step 6. 9. Results as in step 7. 10. RAB service(s) is (are) successfully terminated.
8.7 RAN2733: Flexi Multiradio System Module extension, FSMF + FSMF 8.7.1 Description of RAN2733: Flexi Multiradio System Module Extension, FSMF + FSMF Introduction to the feature This feature introduces support for new configurations that can be based on two Flexi Multiradio 10 BTS System Modules (FSMFs). In such configuration one FSMF acts as a master and the second one as an extension (slave) unit.
8.7.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
Operator benefits This feature benefits the operator as follows: • •
530
Allows to increase the site capacity by adding another FSMF with up to two Capacity Extension Sub-Modules (FBBAs). Allows to create sites with up to 24 cells (RU50 EP1).
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
8.7.1.2
BTS solution features
Requirements Software requirements Table 214: Software requirements lists the software required for this feature. Table 214
Software requirements
RAS
Flexi Direct IPA-RNC
RU50 EP1
Support not required
Flexi Lite BTS
Flexi Multiradio 10 BTS
Not relevant WN9.1
mcRNC
Flexi Direct OMS RNC
Support not Support not Support not required required required
OMS3.1
Flexi Multiradio BTS Support not required
NetAct
MSC
SGSN
MGW
UE
NetAct 8 EP2
Support not required
Support not required
Support not required
Support not required
Hardware requirements This feature requires RAN2262: Flexi Multiradio System Modules (FSMF). Additionally, master unit requires two FBBAs.
8.7.1.3
Functional description Functional overview With this feature it is possible to use Flexi Multiradio 10 System Module (master) together with Flexi Multiradio 10 System Module as an extension module (slave). Master System Module must contain two FBBAs. In such a configuration master System Module is responsible for the following tasks: • • • •
Iub transport (only IP Iub is supported) RP3 topology detection for the whole BTS under one RAT dynamic RP3 allocation for the whole BTS under one RAT capability detection of all connected System Modules (number of supported timing sets, baseband resources, for example)
Note that extension System Module SW must be upgraded before connecting it to the master System Module.
Configuration Flexi Multiradio 10 BTS System Modules are connected through two RP3-01 interfaces and one SRIO interface. RP3-01 and SRIO interfaces require 6 Gbit/s SFP+ cables.
Issue: 01F
DN09146788
531
BTS solution features
w
RU50 Feature Descriptions and Instructions
NOTICE: When Flexi Multiradio 10 System Module is extracted from an existing site and added as an extension module to another BTS, it is mandatory to perform its configuration reset. Configuration reset deletes the existing configuration data and clears the System Module role. The process is performed by pressing and holding the reset button for five seconds. The button is located next to the EIF1 interface on the front panel. If the extracted Flexi Multiradio 10 System Module is to be used as the master, then its configuration reset is not required. During the commissioning the local cell groups' (LCGs) IDs must be in order (LCG1, LCG2 and so on). For more information, see Cabling Flexi Multiradio 10 Base Station and Flexi Multiradio BTS WCDMA Supported Configurations.
8.7.1.4
System impact Interdependencies between features This feature allows creating more advanced site configurations with RAN2262: Flexi Multiradio System Modules (FSMFs).
Impact on interfaces This feature has no impact on interfaces.
Impact on commands There are no commands related to this feature.
Impact on network and network element management tools This feature has no impact on network management or network element management tools.
Impact on system performance and capacity This feature allows creating new kind of configurations that consist of several Flexi Multiradio 10 BTS System Modules.
8.7.1.5
RAN2733: Flexi Multiradio System Module extension, FSMF + FSMF management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms Table 215: Related existing alarms lists existing alarms related to this feature.
532
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Table 215
BTS solution features
Related existing alarms
Alarm ID
Alarm name
7650
BASE STATION FAULTY Fault 4106 SRIO connection failure between system module
7651
BASE STATION OPERATION DEGRADED Fault 2069 SRIO link drop Fault 4199 Extension System Module cannot be taken into use Fault 4202 Extension System Module is connected through incorrect RP3-01 line rate
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.
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. Purpose Follow the procedure below to verify that the activation of the RAN2733: Flexi Multiradio System Module extension, FSMF + FSMF feature has been successful. Before you start Testing environment is as follows: •
Issue: 01F
Operational radio access network and core network.
DN09146788
533
BTS solution features
RU50 Feature Descriptions and Instructions
•
HW: FSMF + FSMF + two FRGTs. Master System Module must have two capacity extension sub-modules (FBBAs). Extension System Module can have one, two, or no FBBAs at all. Configuration: F444444-x-387-1TX/2RX: 4+4+4+4+4+4 20 W.
1
Connect the extension System Module.
•
The cabling instruction is in Cabling Flexi Multiradio 10 Base Station. 2
Upgrade the BTS SW to the latest supported version via BTS Site Manager or NetAct.
3
Perform the commissioning and integration. The information on the autodetected configuration has to be checked in BTS Site Manager. The commissioning should be performed via the Commissioning Wizard. The commissioning file has to be checked, saved, and sent to the BTS. Test AMR, PS, HSPA calls have to be performed in every cell.
4
Block and unblock the extension System Module. Possible alarms have to be checked in the BTS and OMS. Calls should be made in all working cells, both before and after the recovery.
Result 1. The extension System Module is detected successfully in BTS Site Manager. 2. SW is upgraded successfully to the latest version in all modules. 3. All modules are autodetected correctly. Each step of the commissioning is executed successfully. The commissioning file content is correct, so that it can be saved and sent to the BTS. Once the commissioning file is sent, BTS is reset, and new parameters' values are used. All calls are successful. 4. The extension System Module is blocked successfully. Cells allocated to extension System Module do not work. Extension System Module works after the unblocking. All affected cells are recovered. Calls are successful. Cell and extension System Module outage alarms are correctly reported in BTS Site Manager and OMS .
8.8 RAN2998: Flexi RRH 2TX 2100 (FRGY) 8.8.1 Description of RAN2998: Flexi RRH 2TX 2100 (FRGY) Introduction to the feature This feature introduces Flexi Multiradio Remote RF Head (RRH) FRGY with 2TX/2RX for 3GPP band I (1920-1980 MHz uplink, 2110-2170 MHz downlink).
8.8.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
534
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
BTS solution features
Operator benefits Flexi Remote Radio Head provides up to 60+60 W output power at the antenna connector for full 60 MHz bandwidth in both TX and RX. In addition, it has two 6 Gbit/s OBSAI optical interfaces. The Remote Radio Head can be easily installed outdoors, close to antennas, thus maximizing BTS site capacity and area coverage. FRGY supports both WCDMA/HSPA and LTE in dedicated or concurrent mode.
8.8.1.2
Requirements Software requirements Table 217: Software requirements lists software required for this feature. Table 217
8.8.1.3
Software requirements
RAS
Flexi Direct IPA-RNC
mcRNC
OMS
RU50 EP1
Support not required
Support not required
Not relevant WN9.1
Support not required
Flexi BTS
Flexi Lite BTS Not relevant
Flexi 10 BTS
NetAct
MSC
SGSN
MGW
UE
WN9.1
NetAct 8 EP2 (NetAct 15)
Support not required
Support not required
Support not required
Support not required
Functional description FRGY provides the following features: • • • • • • • •
2 x 60 W at antenna connector 60 MHz (TX/RX) bandwidth support for up to 4+4 WCDMA configurations (4 carriers per antenna connector) support for up to two LTE cells with 2TX MIMO (up to 40 MHz (occupied bandwidth) in total per antenna connector) two 6 Gbit/s OBSAI interfaces IP65 with -35°C-+55°C (-31°F-+131°F) with convectional cooling 15 l volume (18 l with solar shield) input for external alarms
For more information, see Flexi Multiradio BTS Radio Module and Remote Radio Head Description.
8.8.1.4
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.
Issue: 01F
DN09146788
535
BTS solution features
RU50 Feature Descriptions and Instructions
Impact on network and network element management tools This feature has no impact on network management and network element management tools.
Impact on system performance and capacity New configurations are available.
8.8.1.5
RAN2998: Flexi RRH 2TX 2100 (FRGY) management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
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.
8.8.1.6
Sales information Table 218
Sales information
BSW/ASW
SW component
License control in network element
BSW
RAN
Not defined
8.9 RAN2732: Flexi System Module Extension, FSMF + FSMD/E 8.9.1 Description of RAN2732: Flexi System Module Extension, FSMF + FSMD/E Introduction to the feature This feature introduces support for new Flexi BTS configurations that can consist of both Flexi Multiradio BTS System Module (FSMD/E) and Flexi Multiradio 10 BTS System Module (FSMF).
8.9.1.1
Benefits End-user benefits This feature does not affect the end-user experience.
536
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
BTS solution features
Operator benefits This feature benefits the operator as follows: • •
8.9.1.2
Smooth site upgrade Evolution path for existing sites to increase capacity
Requirements Software requirements Table 219: Software requirements lists the software required for this feature. Table 219
Software requirements
RAS
Flexi Direct IPA-RNC
RU50 EP1
Support not required
Flexi Lite BTS
Flexi Direct RNC
Support not Support not Support not required required required
Flexi NetAct Multiradio 10 BTS
Not relevant WN9.1
mcRNC
MSC
NetAct 8 Support not EP2 (NetAct required 15)
OMS
Flexi Multiradio BTS
OMS3.1
WN9.1
SGSN
MGW
UE
Support not required
Support not required
Support not required
Hardware requirements This feature requires Flexi Multiradio System Module (FSMD/E) and Flexi Multiradio 10 System Module (FSMF).
8.9.1.3
Functional description Functional overview With this feature it is possible to use FSMF (master) together with FSMD/E as an extension module (slave). In such configuration FSMF as a master is responsible for the following tasks: • • • • •
Issue: 01F
Iub transport (only IP Iub is supported) synchronization of other modules (RF Modules, Remote Radio Heads (RRHs), extension/slave units) RP3 topology detection for the whole BTS under one RAT dynamic RP3 allocation for the whole BTS under one RAT SW download and distribution to extension System Module
DN09146788
537
BTS solution features
RU50 Feature Descriptions and Instructions
Note that configurations with more than 12 cells are not supported with one- and twosector RF Modules/RRHs. For supported configurations, see Flexi Multiradio BTS WCDMA Supported Configurations. FSMF capacity can be additionally increased with one or two optional Capacity Extension Sub-Modules (FBBAs). Such configuration allows connecting up to three RF Modules/RRHs. Up to two RF Modules/RRHs can be connected with no FBBA at all. The maximum number of chains is three with up to two RF Modules/RRHs per chain. See also Impact on system performance and capacity.
Configuration FSMF and FSMD/E are connected through two RP3-01 interfaces: • •
one for communication purposes (1 Gbit Ethernet mode) one for antenna data and synchronization information exchange
RF Modules/RRHs can be connected only to RF/EXT1-3 ports of the master System Module. Additionally, if the extension System Module is not commissioned before connecting it to the master System Module, fault 4199 Extension System Module cannot be taken into use is raised. For more information, see Cabling Flexi Multiradio 10 Base Station.
8.9.1.4
System impact Interdependencies between features This feature allows to use RAN2262: Flexi Multiradio System Modules together with: • •
RAN1016: Flexi BTS Multimode System Module - FSMD RAN1848: Flexi BTS Multimode System Module - FSME
Impact on interfaces This feature has no impact on interfaces.
Impact on commands There are no commands related to this feature.
Impact on network and network element management tools This feature has no impact on network management or network element management tools.
Impact on system performance and capacity This feature allows creating sites based on Flexi Multiradio 10 System Module together with the FSMD/E. In such configuration the supported types of baseband pooling are only fixed baseband allocations (fixed to FSMD/E and FSMF with optional 0-2 FBBAs). Two local cell groups (LCGs) are required, one per System Module. LCG1 has to be allocated to FSMF and LCG2 to FSMD/E.
538
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
8.9.1.5
BTS solution features
RAN2732: Flexi System Module Extension, FSMF + FSMD/E management data For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms Table 220: Related existing alarms lists existing alarms related to this feature. Table 220
Related existing alarms
Alarm ID
Alarm name
7651
BASE STATION OPERATION DEGRADED Fault 4200 Incorrect BB pooling Fault 4199 Extension System Module cannot be taken into use
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 221: Modified parameters lists existing parameters related to this feature. Table 221
8.9.1.6
Full name
Abbreviated name
Managed object
RP3 link Id
linkId
RMOD
Link Id
linkId
SMOD
Access baseband capacity
accessBbCapacity
LCELGW
System module identifier
sModId
LCELGW
Sales information Table 222
Issue: 01F
Modified parameters
Sales information
BSW/ASW
SW component
License control in network element
BSW
RAN
Not defined
DN09146788
539
BTS solution features
RU50 Feature Descriptions and Instructions
8.9.2 Testing RAN2732: Flexi System Module Extension, FSMF + FSMD/E Purpose Follow this procedure to activate the RAN2732: Flexi System Module Extension, FSMF + FSMD/E feature. Test environment • • • • • • • •
One System Module FSMF (472181A) with two FBBAs (472182A) and transmission sub-module FTIF (472311A) One System Module FSME (471469A) Two RF Modules FRGT (472810A) Eight SFPs FOSH (472579A) in sockets FSMF RF/EXT1, FSMF RF/EXT2, FBBA RF/EXT, FSME OPT-EXT 1, FSME OPT-EXT 2, and FRGT OPT1 One fiber link (472894A) connection between FSMF1 RF/EXT1 and FRGT1.1.1 OPT1 One fiber link (472894A) connection between FSMF1 RF/EXT2 and FRGT1.2.1 OPT1 One fiber link (472894A) connection between FBBA2 RF/EXT and FSME2 OPT-EXT 1 One fiber link (472894A) connection between FBBA3 RF/EXT and FSME2 OPT-EXT 1
This feature does not require a license5). However, during the testing period, the following licenses6) have been installed: • • • • • • • • • • • • • • •
RAN2887: CCCH Processing Set = 99 RAN2123: Flexi BTS Gigabit Baseband (R99 CE capacity*) = 2000 RAN2123: Flexi BTS Gigabit Baseband (HSDPA BTS processing set 3*) = 99 RAN2123: Flexi BTS Gigabit Baseband (HSDPA BTS processing set 2*) = 99 RAN2123: Flexi BTS Gigabit Baseband (HSDPA BTS processing set 1*) = 99 RAN1702: Frequency Domain Equalizer RAN1308: HSUPA Interference Cancellation Receiver RAN1254: Timing over Packet for BTS Application SW RAN119: Antenna Alarm with Receiver Signal Comparison RAN908: Flexi WCDMA BTS AISG MHA Support RAN906: Flexi WCDMA BTS 3GPP Antenna Tilt Support RAN907: Antenna Line Supervision RAN905: Flexi WCDMA BTS MHA support RAN849: HSDPA Proportional Fair Resource Packet Scheduler RAN764: HSDPA 16QAM support
Before you start The BTS must already be commissioned, on air, and in OAM-connected state. The BTS Site Manager (BTS SM) can be connected to the BTS either locally or remotely.
5) 6)
540
WCDMA RAN, Rel. RU50, Operating Documentation, Issue 02 > System Descriptions > WCDMA RAN License Operation > Licenses in WCDMA RAN. Other features are out of scope of RAN2732 and should be activated and tested according to their own procedures.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 92
1
BTS solution features
BTS initial configuration.
Connect the fiber links. The connection is as follows: • •
2
System Module FSME2 interface OPT-EXT1 to master system BB extension module FBBA2 interface RF/EXT System Module FSME2 interface OPT-EXT2 to master system BB extension module FBBA3 interface RF/EXT
Switch on the power of FSME2 module. Wait a few minutes until the System Module FSME2 is detected.
Issue: 01F
DN09146788
541
BTS solution features
RU50 Feature Descriptions and Instructions
3
If an alarm with the fault name Incompatible SW version detected in unit: FSM2/FCM (0023) appears, it is necessary to update the extension module SW (Software ► Update SW to BTS Site...). Otherwise, skip to the next step. Figure 93
g
542
BTS configuration after connecting the extension System Module FSME.
The BTS resets on completion of the SW update.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
4
Alarm Extension System Module cannot be taken into use (4199) should be visible. Figure 94
5
BTS solution features
BTS configuration with connected extension System Module FSME without proper configuration.
Commission the feature. a) Open the commissioning page WCDMA Carrier Candidates and Local Cell Group Settings. b) Select the Local cell groups in use ► Fixed BB allocation check box. c) In the table Carrier candidates and local cell groups, assign the first local cell to Local cell group 1 and the second local cell to Local cell group 2. d) In the table Baseband (BB) and HSPA license allocation, assign Local cell group 1 to System Module FSMF 1 and Local cell group 2 to System Module FSME 2.
Issue: 01F
DN09146788
543
BTS solution features
RU50 Feature Descriptions and Instructions
Figure 95
WCDMA Carrier Candidates and Local Cell Group Settings.
Result Make sure that all cells are up and running without any faults. The feature RAN2732: Flexi System Module Extension, FSMF + FSMD/E is active. Figure 96
544
BTS configuration according to RAN2732.
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
BTS solution features
8.10 RG602339/RAN3001/ LTE1710: Sync Hub Direct Forward 8.10.1 Description of RG602339/RAN3001/ LTE1710: Sync Hub Direct Forward Introduction to the feature Sync Hub Direct Forward provides a more efficient and accurate Phase/Time synchronization distribution to all BTSs at the same site, regardless if RF sharing is used or not. This allows all RF sharing sites to support applications that require Phase/Time Synchronization like Dynamic Frequency and Channel Allocation (DFCA), Enhanced Inter-Cell Interference Coortination (eICIC), Observed Time Difference of Arrival (OTDOA) and/or other. The feature improves the reliability of RF sharing solution also based on temporary radio master role functionality.
Benefits This feature does not affect the end-user experience. Operator benefits Operators can get the lowest TCO site solution with RF sharing. At the same time operators can exploit the great benefits of the following features: • • •
DFCA OTDOA LTE-A eICIC
More flexible site solution as Phase and Time synchronization can be distributed to all BTS at the site with a single Synchronization source. The feature ensures better reliability and availability of RF sharing site. This is possible thanks to the holdover function and the ability of a radio slave to take over radio master role, in case the previous radio master has failed.
Requirements Hardware and software requirements Table 223
Issue: 01F
Hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
RL55TD / RL70 / RU50 EP1 / RG40
LBTS7.0 / WBTS9.1 / EX5_2
TD-LBTS5.0 / LBTS7.0 / WBTS9.1
OMS
UE
NetAct
MME
SAE GW
Support not required
Support not required
Support not required
Support not required
Support not required
DN09146788
545
BTS solution features
RU50 Feature Descriptions and Instructions
Additional hardware requirements Flexi Multiradio 10 BTS system module:can be used as Sync Hub Master or Sync Hub Slaves. Flexi Multiradio system module ESMB/C:can be used as Sync Hub Master only if the Sync Hub Slaves do not use features that require Phase/Time synchronization. It can always be used as Sync Hub Slaves. Flexi Multiradio system module FSME:can only be used Sync Hub Slaves
g
It is recommended to configure Sync Hub Direct Forward master BTS first, before Sync Hub Direct Forward slave BTS. In 2G configure required BCF settings in BSC first, before commissioning the BTS. In case 2G BTS has already been commissioned and changes for BCF in BSC are blocked by BSC, lock the BCF again (using the ZEFM command) to enable BCF configuration changes.
Functional description Functional overview Sync Hub Direct Forward mechanism High phase accuracy between system modules is provided by Sync Out/Sync In connection instead of RP3-01 connection. Any sync sources can be used as sync input to Sync Hub Master, with the exception of sync from RP3-01/CPRI. The Sync Hub Master provides 1PPS AND ToD as output to Sync Hub Slaves. If there are multiple Sync Hub Slaves, each Sync Hub slave directly forwards 1PPS AND ToD to next Sync Hub Slaves in the chain wihtout modification/regeneration. In the event of the Sync Hub Slaves losing synchronization input (for example: fail of Sync Hub Master), Sync Hub Slaves rely on their own holdover tuning algorithm and still stays operational. The synchronization chainging solution based on 1PPS AND ToD is also enhanced with the ability for Sync Hub Master to provide phase error information to all Sync Hub Slaves in the chain during its holdover period. This allows the Sync Hub Slaves to be able to fully rely on Sync Hub Master holdover performance and is able to decide by itself the necessary action when phase error exceeds the required threshold.
546
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
Figure 97
BTS solution features
Sync Hub Direct forward chaining
AnySyncInput SyncIn
SyncOut
GE
SyncHubMaster
SyncIn
1PPS&T oD
SyncOut SyncHubSlave1
SyncIn
SyncOut
1PPS&T oD
Tofurtherslaves ifneeded
SyncHubSlave2
Sync Hub Direct Forward RF sharing Sync Hub Direct Forward provides BTS site phase/time synchronization for RF sharing without a need to transfer synchronization information through the RP3-01 interface. The transfer of phase/time synchronization between system modules sharing a RF module is done with the use of 1PPS AND ToD signals and interfaces. The use of 1PPS AND ToD improves/keeps the availability of RF sharing solution (for example: a radio slave can temporary take over a radio master role, in case previous radio master has failed). The ability to serve as a head element of a Sync Hub Direct Forward chain or as an intermediated element is independent no matter if a BTS acts as radio master or radio slave with a RF sharing configuration. The ability to serve as head element of a Sync Hub Direct Forward chain or as intermediate element is independent of the RAT of a BTS. The RP3-01 connection between system modules involved in RF sharing is required to perform RF sharing topology scan to build a communication among RF sharing elements.
Issue: 01F
DN09146788
547
BTS solution features
RU50 Feature Descriptions and Instructions
Figure 98
Sync Hub Direct Forward RF sharing RFsharing
RP3-01link
AnySyncInput Radio/LinkSlave SyncHubMaster
Radio/Link Master SyncHub Slave 1PPS&T oD
Tobackhaul
Tobackhaul
RFport TransportInterface SyncIn/SyncOut
RAN and BTS Site phase/time synchronization application scenarios is supported concurrent and can be combined. Not all BTSs at a site being a part of a Sync Hub Direct Forward configuration need to be a part of the RF sharing setup. When RF sharing master fails, Radio slave attempts to take over Radio master role. When the commissioned Radio master is back, the temporary Radio master switches back to its commissioned role of Radio slave. Takeover of the Radio master role by a Radio slave is independent of the Sync Hub Master/slave role. If the Radio slave is Sync Hub Master it can continue to rely on the external synchronization. If the Radio slave is Sync Hub slave it relies on its own holdover function. Sync Hub Direct Forward GNSS phase sync support for WCDMA A WCDMA NodeB needs to support phase synchronization when using an external GNSS receiver as synchronization input source. This allows a WCDMA NodeB to serve as a Sync Hub master. A radio master and a Sync Hub Slave (GSM BTS, LTE eNB) can use phase synchronization-dependent radio applications (for example: DFCA, eICIC, OTDOA). Universal BTS site sync chaining Distributing synchronization between BTS elements at a site using 1PPS AND ToD is the default approach. As a result it is possible to operate a sync chain at a frequency synchronization mode only. This does not support RF sharing and phase synchronization-dependent radio applications to operate at a BTS element. The independence from phase synchronization enhances the resilience. In case the 1PPS AND ToD input is not available, each BTS element can start operating using its own oscillator. Improved reporting of Rejected Samples for 1pps synchronization algorithm
548
DN09146788
Issue: 01F
RU50 Feature Descriptions and Instructions
BTS solution features
With the introduction of the feature RG602339/RAN3001/LTE1710 Sync Hub Direct Forward, the information presented in the field “Rejected Samples (%)” in the FrequencyHistory.xml file has a different interpretation with respect to previous releases. In previous releases, the synchronization from a GPS 1pps input used a algorithm to identify and discard a predefined and fixed 12% of 1pps outlier phase samples. The 12% of the 1pps samples with the biggest distance to the phase mean were discarded on each reporting period on the FrequencyHistory.xml file. The actual value shown in the field “Rejected Samples (%) was the difference between the rejected phase samples and the predefined 12% which was always 0%. With RG602339/RAN3001/LTE1710 Sync Hub Direct Forward, each single pps phase sample input is evaluated independently to determine whether it is accepted or rejected. There is no pre-defined percentage of phase samples to be rejected. For this reason, the field “Rejected Samples (%) represents now the actual percentage of rejected outlier samples in each reporting period in the FrequencyHistory.xml, not the difference with respect to a predefined rejection rate. In good conditions, the field “Rejected Samples (%) shows a value 0%. In normal conditions, sporadically the field Rejected Samples can show small values. This indicates that the Sync Hub Direct Forward synchronization algorithm is correctly identifying and discarding phase sample outliers to reduce the input noise from the GPS 1pps input signal.
g
The same information, “Rejected Samples (%)“ is also shown in BTS Clock Tuning History in BTS Site Manager.
System impact Current Implementation WCDMA does not support Phase sync mode. It cannot be used to provide phase synchronization to another BTS. WCDMA is always Sync Master in RF sharing configuration even though it does not have sufficient synchronization functionalities (phase sync, holdover, ToP with Phase sync etc.) required by its Sync Slave. Sync role and RF sharing role cannot be decoupled because of RP3-01 based synchronization. This makes changing of role difficult and poses many limitations. Interdependencies between features • • • • •
Impact on interfaces This feature has no impact on interfaces. Impact on network management tools This feature has no impact on network management tools.
Issue: 01F
DN09146788
549
BTS solution features
RU50 Feature Descriptions and Instructions
Impact on system performance and capacity This feature has no impact on system performance or capacity. Dependency to other RATs UTRAN GSM
• •
Management data 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 below lists parameters related to the RG602339/RAN3001/LTE1710: Sync Hub Direct Forward feature. Table 224
Related parameters
Full name
550
Abbreviated name
Managed object LTE
WCDMA
GSM
GPS control interface blocked for co-located BTS
gpsCtrlBlockForC BTSSCL oLocatedBts
BTSSCW
-
-
syncHubEnabled
-
-
SMOD
Forward synchronization in co-siting
syncPropagation Enabled
BTSSCL
BTSSCW
SMOD
Network synchronization mode
btsSyncMode
BTSSCL
BTSSCW
-
-
btsSyncSource
-
-
BTSNE
GPS antenna line gpsTotalAntennaL BTSSCL delay ineDelay
