Fdd15A Desc

Nokia Networks

LTE Radio Access, Rel. FDDLTE15A, Operating Documentation, Issue 02, Documentation Change Delivery 1 FDD-LTE15A, Feature Descriptions and Instructions DN09185982 Issue 01D Approval Date 2015-11-02

FDD-LTE15A, Feature Descriptions and Instructions

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

f

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

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

2

DN09185982

Issue: 01D


Table of Contents This document has 526 pages

Summary of changes................................................................... 22

1

Introduction.................................................................................. 25

2

Activating and deactivating LTE features using BTS Site Manager. 26

3

Descriptions of radio resource management and telecom features. 28 LTE64: Service-based Handover Thresholds...............................28 Description of LTE64: Service-based Handover Thresholds....... 28 Activating and configuring LTE64: Service-based Handover Thresholds................................................................................... 33 Deactivating LTE64: Service-based Handover Thresholds..........37 LTE738: SRVCC to 1xRTT/CDMA .............................................. 38 Description of LTE738: SRVCC to 1xRTT/CDMA........................ 38 Activating and configuring LTE738: SRVCC to 1xRTT/CDMA.....47 Deactivating LTE738: SRVCC to 1xRTT/CDMA.......................... 51 LTE825: Uplink Outer Region Scheduling....................................52 Description of LTE825: Uplink Outer Region Scheduling.............52 Activating and configuring LTE825: Uplink Outer Region Scheduling................................................................................... 59 Deactivating LTE825: Uplink Outer Region Scheduling .............. 62 LTE951: Enhanced Cell ID Location Service............................... 63 Description of LTE951: Enhanced Cell ID Location Service........ 63 Activating and configuring LTE951: Enhanced Cell ID Location Service......................................................................................... 69 Deactivating LTE951: Enhanced Cell ID Location Service.......... 73 LTE1117: LTE MBMS................................................................... 74 Description of LTE1117: LTE MBMS............................................ 74 Activating and configuring LTE1117: LTE MBMS......................... 84 Deactivating LTE1117: LTE MBMS...............................................90 LTE1196: RAN Information Management for WCDMA................ 91 Description of LTE1196: RAN Information Management for WCDMA....................................................................................... 91 Activating and configuring LTE1196: RAN Information Management for WCDMA ........................................................... 97 Deactivating LTE1196: RAN Information Management for WCDMA ................................................................................................... 103 LTE1321: eRAB modification - GBR.......................................... 104 Description of LTE1321: eRAB Modification – GBR...................104 LTE1357: LTE-UTRAN Load Balancing..................................... 109 Description of LTE1357: LTE-UTRAN Load Balancing.............. 109

3.1 3.1.1 3.1.2 3.1.3 3.2 3.2.1 3.2.2 3.2.3 3.3 3.3.1 3.3.2 3.3.3 3.4 3.4.1 3.4.2 3.4.3 3.5 3.5.1 3.5.2 3.5.3 3.6 3.6.1 3.6.2 3.6.3 3.7 3.7.1 3.8 3.8.1

Issue: 01D

DN09185982

3


3.8.2 3.8.3 3.9 3.9.1 3.9.2 3.9.3 3.10 3.10.1 3.10.2 3.10.3 3.11 3.11.1 3.11.2 3.11.3 3.12 3.12.1 3.12.2 3.12.3 3.13 3.13.1 3.13.2 3.13.3 3.13.4 3.14 3.14.1 3.14.2 3.14.3 3.15 3.15.1 3.15.2 3.15.3

4

Activating and configuring LTE1357: LTE-UTRAN Load Balancing. 114 Deactivating LTE1357: LTE-UTRAN Load Balancing.................119 LTE1635: SIB8 AC barring for 1xRTT........................................ 120 Description of LTE1635: SIB 8 AC Barring for 1xRTT................120 Activating and configuring LTE1635: SIB 8 AC Barring for 1xRTT.. 123 Deactivating LTE1635: SIB 8 AC Barring for 1xRTT..................126 LTE1679: DRX with Parallel UE Measurement Gaps................ 127 Description of LTE1679: DRX with Parallel UE Measurement Gaps...........................................................................................127 Activating and configuring LTE1679: DRX with Parallel UE Measurement Gaps....................................................................130 Deactivating LTE1679: DRX with Parallel UE Measurement Gaps.. 131 LTE1788: Automatic Access Class Barring................................132 Description of LTE1788: Automatic Access Class Barring.........132 Activating and configuring LTE1788: Automatic Access Class Barring........................................................................................140 Deactivating LTE1788: Automatic Access Class Barring........... 148 LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz........... 149 Description of LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz............................................................................................ 149 Activating and configuring LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz........................................................................... 160 Deactivating LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz............................................................................................ 162 LTE1905: PLMN ID and SPID Selected Mobility Profiles...........163 Description of LTE1905: PLMN ID and SPID Selected Mobility Profiles....................................................................................... 163 Activating and configuring LTE1905: PLMN ID and SPID Selected Mobility Profiles.......................................................................... 168 Deactivating LTE1905: PLMN ID and SPID Selected Mobility Profiles with the actSelMobPrf parameter..................................171 Deactivating LTE1905: PLMN ID and SPID Selected Mobility Profiles with the moProfileSelect parameter.............................. 172 LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List ................................................................................................... 173 Description of LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List............................................................................173 Activating and configuring LTE1942: Dedicated VoLTE InterFrequency Target Frequency List...............................................177 Deactivating LTE1942: Dedicated VoLTE Inter-Frequency Target Frequency List............................................................................179 LTE1944: Dynamic Handover Blacklisting ................................ 179 Description of LTE1944: Dynamic Handover Blacklisting.......... 179 Activating and configuring LTE1944: Dynamic Handover Blacklisting................................................................................. 183 Deactivating LTE1944: Dynamic Handover Blacklisting.............184

DN09185982

Issue: 01D


3.16 3.16.1 3.16.1.1 3.17 3.17.1 3.17.2 3.17.3 3.18 3.18.1 3.18.2 3.18.3 3.19 3.19.1 3.19.2

3.19.3 3.19.4 3.20 3.20.1 3.21 3.21.1 3.21.2 3.21.3 3.22 3.22.1 3.22.2 3.22.3 3.23 3.23.1 3.24 3.24.1 3.24.2

Issue: 01D

LTE2006: Flexible SCell Selection............................................. 185 LTE2006: Flexible SCell Selection............................................. 185 Description of LTE2006: Flexible SCell Selection...................... 185 LTE2023: User Plane Overload Handling.................................. 189 Description of LTE2023: User Plane Overload Handling .......... 189 Activating and configuring LTE2023: User Plane Overload Handling..................................................................................... 195 Deactivating LTE2023: User Plane Overload Handling............. 196 LTE2051: Measurement based Idle Mode Load Balancing....... 197 Description of LTE2051: Measurement based Idle Mode Load Balancing................................................................................... 197 Activating and configuring LTE2051: Measurement based Idle Mode Load Balancing................................................................ 201 Deactivating LTE2051: Measurement based Idle Mode Load Balancing................................................................................... 204 LTE2085: SIB Reception with Parallel Measurement Gaps....... 204 Description of LTE2085: SIB Reception with Parallel Measurement Gaps....................................................................204 Activating and configuring LTE2085: SIB Reception with Parallel Measurement Gaps with the Twofold transmission of SIBs per SI window parameter......................................................................210 Activating and configuring LTE2085: SIB Reception with Parallel Measurement Gaps with a selected feature .............................. 211 Deactivating LTE2085: Reception with Parallel Measurement Gaps...........................................................................................217 LTE2133: eICIC for HetNet eNode B Configurations................. 218 Description of LTE2133: eICIC for HetNet eNode B Configurations ................................................................................................... 218 LTE2149: Supplemental Downlink Carrier................................. 222 Description of LTE2149: Supplemental Downlink Carrier.......... 222 Activating and configuring LTE2149: Supplemental Downlink Carrier........................................................................................ 227 Deactivating LTE2149: Supplemental Downlink Carrier............ 231 LTE2168: Additional Carrier Aggregation Band Combinations - II... 232 Description of LTE2168: Additional Carrier Aggregation Band Combinations - II........................................................................ 232 Activating and configuring LTE2168: Additional Carrier Aggregation Band Combinations - II.......................................... 234 Deactivating LTE2168: Additional Carrier Aggregation Band Combinations - II........................................................................ 235 LTE2208: eICIC Enhancements - micro.....................................236 Description of LTE2208: eICIC Enhancements - micro..............236 LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs ................................................................................................... 239 Description of LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs......................................................................... 239 Activating and configuring LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs.............................................244

DN09185982

5


3.24.3 3.25

3.25.1

3.25.2

3.25.3

3.26 3.26.1 3.26.2 3.26.3 3.27 3.27.1 3.27.2 3.27.3

4 4.1 4.1.1 4.1.2 4.1.3 4.2 4.2.1 4.3 4.3.1 4.4 4.4.1 4.4.2

Descriptions of transport and transmission features.................. 265 LTE942: Hybrid Synchronization................................................ 265 Description of LTE942: Hybrid Synchronization......................... 265 Activating and configuring LTE942: Hybrid Synchronization......271 Deactivating LTE942: Hybrid Synchronization........................... 271 LTE1244: Source-based Routing in BTS................................... 272 Description of LTE1244: Source-based Routing in BTS............ 272 LTE1559: SCTP Enhancements................................................ 279 Description of LTE1559: SCTP Enhancements......................... 279 LTE1771: Dual U-plane IP Addresses........................................282 Description of LTE1771: Dual U-plane IP Addresses................ 282 Activating and configuring LTE1771: Dual U-plane IP Addresses... 288 Deactivating LTE1771: Dual U-plane IP Addresses...................290 LTE2063: GNSS Manual Location Entry for Flexi Zone............. 291 Description of LTE2063: GNSS Manual Location Entry for Flexi Zone........................................................................................... 291 Activating and configuring LTE2063: GNSS Manual Location Entry for Flexi Zone............................................................................. 296 Deactivating LTE2063: GNSS Manual Location Entry for Flexi Zone........................................................................................... 297

4.4.3 4.5 4.5.1 4.5.2 4.5.3

6

Deactivating LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs......................................................................... 247 LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release...................................................................................... 248 Description of LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release...................................................................248 Activating and configuring LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release.................................................. 250 Deactivating LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release ........................................................................253 LTE2324: Network-requested UE Radio Capabilities................ 254 Description of LTE2324: Network-requested UE Radio Capabilities.................................................................................254 Activating and configuring LTE2324: Network-requested UE Radio Capabilities.................................................................................257 Deactivating LTE2324: Network-requested UE Radio Capabilities.. 259 LTE2430: QCI1 Establishment Triggered Protection Timer....... 259 Description of LTE2430: QCI1 Establishment Triggered Protection Timer.......................................................................................... 259 Activating and configuring LTE2430: QCI1 Establishment Triggered Protection Timer.........................................................262 Deactivating LTE2430: QCI1 Establishment Triggered Protection Timer.......................................................................................... 263

DN09185982

Issue: 01D


5 5.1 5.1.1 5.2 5.2.1 5.2.2 5.2.3

Descriptions of operability features............................................ 298 LTE790: Signed SW................................................................... 298 Description of LTE790: Signed SW............................................ 298 LTE1030: Configurable Service Accounts..................................301 Description of LTE1030: Configurable Service Accounts...........301 Configuring LTE1030: Configurable Service Accounts.............. 304 Configuring LTE1030: Configurable Service Accounts using NEAC ................................................................................................... 306 LTE1049: MDT - UE Measurement Logs................................... 308 Description of LTE1049: MDT - UE Measurement Logs............ 308 Activating and configuring LTE1049: MDT - UE Measurement Logs........................................................................................... 313 Deactivating LTE1049: MDT - UE Measurement Logs.............. 316 LTE1052: Transport Configuration Fallback...............................317 Description of LTE1052: Transport Configuration Fallback........317 Activating and configuring LTE1052: Transport Configuration Fallback......................................................................................319 Deactivating LTE1052: Transport Configuration Fallback.......... 320 LTE1058: Plug and Play Extensions.......................................... 320 Description of LTE1058: Plug and Play Extensions................... 320 LTE1103: Load Based Power Saving for Multi-layer Networks.. 335 Description of LTE1103: Load Based Power Saving for Multi-layer Networks.................................................................................... 335 Activating and configuring LTE1103: Load Based Power Saving for Multi-layer Networks............................................................. 341 Deactivating LTE1103: Load Based Power Saving for Multilayer Networks.................................................................................... 344 LTE1225: Parameter Level Logging of BTS User Events.......... 344 Description of LTE1225: Parameter Level Logging of BTS User Events........................................................................................ 344 LTE1227: Flexi Multiradio BTS SW Download for Antenna Line Devices...................................................................................... 347 LTE1227: Flexi Multiradio BTS SW Download for Antenna Line Devices...................................................................................... 347 LTE1408: Remote Syslog for Continuous Log Storage............. 350 Description of LTE1408: Remote Syslog for Continuous Log Storage.......................................................................................350 Activating and configuring LTE1408: Remote Syslog for Continuous Log Storage............................................................ 354 Deactivating LTE1408: Remote Syslog for Continuous Log Storage.......................................................................................356 LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing.............356 Description of LTE1434: Flexi Multiradio BTS Antenna Rx RFsniffing........................................................................................ 356 Activating and configuring LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing.............................................................................360 Deactivating LTE1434: Flexi Multiradio BTS Antenna Rx RFsniffing........................................................................................ 361

5.3 5.3.1 5.3.2 5.3.3 5.4 5.4.1 5.4.2 5.4.3 5.5 5.5.1 5.6 5.6.1 5.6.2 5.6.3 5.7 5.7.1 5.8 5.8.1 5.9 5.9.1 5.9.2 5.9.3 5.10 5.10.1 5.10.2 5.10.3

Issue: 01D

DN09185982

7


5.10.4 5.11 5.11.1 5.11.2 5.11.3 5.12 5.12.1 5.13 5.13.1 5.14 5.14.1 5.15 5.15.1 5.16 5.16.1 5.17 5.17.1 5.17.2 5.17.3 5.18 5.18.1 5.19 5.19.1 5.20 5.20.1 5.20.2 5.20.3 5.21 5.21.1 5.21.2 5.21.3 5.22

8

Performing RF monitoring ......................................................... 362 LTE1749: Mobility Robustness Monitoring Inter RAT.................364 Description of LTE1749: Mobility Robustness Monitoring Inter RAT ................................................................................................... 364 Activating and configuring Mobility Robustness Monitoring Inter RAT............................................................................................ 369 Deactivating LTE1749: Mobility Robustness Monitoring Inter RAT.. 370 LTE1879: Additional PM Counters for Mobility Event Monitoring..... 371 Description of LTE1879: Additional PM Counters for Mobility Event Monitoring........................................................................ 371 LTE1899: Dedicated PM Counters for E-RAB Management Failure Causes........................................................................... 374 Description of LTE1899: Dedicated PM Counters for E-RAB Management Failure Causes..................................................... 374 LTE1912: RRC Establishment Monitoring Extensions............... 380 Description of LTE1912: RRC Establishment Monitoring Extensions..................................................................................380 LTE1949: Extend Power Reduction Range................................383 Description of LTE1949: Extend Power Reduction Range.........383 LTE1996: Flexi Zone Controller Application............................... 384 Description of LTE1996: Flexi Zone Controller Application........ 384 LTE2017: IPSec Support for Flexi Zone Controller.................... 389 Description of LTE2017: IPSec Support for Flexi Zone Controller... 389 Activating and configuring LTE2017: IPSec Support for Flexi Zone Controller....................................................................................393 Deactivating LTE2017: IPSec Support for Flexi Zone Controller..... 398 LTE2049: System Upgrade to FDD-LTE 15A.............................401 Description of LTE2049: System Upgrade to FDD-LTE 15A......401 LTE2061: OMS HP Gen9 HW assignment.................................407 Description of LTE2061: OMS HP Gen9 HW assignment..........407 LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness.... 408 LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness.... 408 Activating and configuring LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness.................................................................. 412 Deactivating LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness ............................................................................... 415 LTE2084: UE MAC Measurement Addition to Cell Trace...........416 Description of LTE2084: UE MAC Measurement Addition to Cell Trace.......................................................................................... 416 Activating and configuring LTE2084: UE MAC Measurement Addition to Cell Trace................................................................. 420 Deactivating LTE2084: UE MAC Measurement Addition to Cell Trace.......................................................................................... 422 LTE2175: PM Counter Enhancement for CSFB to 1xRTT, CQI Level, E-RAB Abnormal Release............................................... 423

DN09185982

Issue: 01D


5.22.1

5.26 5.26.1

Description of LTE2175: PM Counter Enhancement for CSFB to 1xRTT, CQI Level, E-RAB Abnormal Release .......................... 423 LTE2182: Enhanced Flexi Zone Plug and Play for Non-Operator Owned Backhaul........................................................................ 427 Description of LTE2182: Enhanced Flexi Zone Plug and Play for Non-Operator Owned Backhaul................................................. 427 LTE2195: Integrated O&M for Ruckus Wi-Fi.............................. 437 Description of LTE2195: Integrated O&M for Ruckus Wi-Fi....... 437 LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I.................................................................................................. 454 Description of LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I....................................................................... 454 Activating and configuring LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I....................................................... 457 Deactivating LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I....................................................................... 459 LTE2548: BTS EM Support for RHEL 7.1.................................. 461 Description of LTE2548: BTS EM Support for RHEL 7.1........... 461

6 6.1 6.1.1

Descriptions of BTS site solution features................................. 464 LTE1725: FRME Flexi RF Module 6-Pipe 800 240W.................464 Description of LTE1725: FRME Flexi RF Module 6-Pipe 800 240W ................................................................................................... 464 LTE1829: Inter eNB RF sharing................................................. 466 Description of LTE1829: Inter eNB RF sharing.......................... 466 Activating and configuring LTE1829: Inter eNB RF sharing....... 470 Activation requirements..............................................................472 General activation procedure..................................................... 472 Installing a new LTE-LTE RF Sharing Configuration.................. 473 Migration of a single eNB site to an LTE-LTE RF Sharing Configuration with no new shared RFMs/RRHs.........................475 Migration of a single eNB site to an LTE-LTE RF Sharing Configuration with new shared RFMs/RRHs..............................478 Commissioning eNBs for LTE-LTE RF Sharing..........................480 Deactivating LTE1829: Inter eNB RF sharing............................ 484 LTE2028: Outdoor External GNSS Module with Enhanced Holdover - FYGG....................................................................... 485 Description of LTE2028: Outdoor External GNSS Module with Enhanced Holdover - FYGG...................................................... 485 LTE2143: FRBE Flexi RRH 4-Pipe 750&720T 160W.................487 Description of LTE2143: FRBE Flexi RRH 4-Pipe 750&720T 160W ................................................................................................... 487 LTE2146: FRBF Flexi RRH 4-Pipe 760 160W........................... 489 Description of LTE2146: FRBF Flexi RRH 4-Pipe 760 160W.... 489 LTE2147: FHGB Flexi RRH 4-Pipe 2100 120W K..................... 491 Description of LTE2147: FHGB Flexi RRH 4-Pipe 2100 120W K.... 491 LTE2148: FHPC Flexi RRH 2/2-Pipe 700&850 100W K............ 493

5.23 5.23.1 5.24 5.24.1 5.25 5.25.1 5.25.2 5.25.3

6.2 6.2.1 6.2.2 6.2.2.1 6.2.2.2 6.2.2.3 6.2.2.4 6.2.2.5 6.2.2.6 6.2.3 6.3 6.3.1 6.4 6.4.1 6.5 6.5.1 6.6 6.6.1 6.7

Issue: 01D

DN09185982

9


6.7.1 6.8 6.8.1 6.9 6.9.1 6.10 6.10.1 6.11 6.11.1 6.12 6.12.1 6.13 6.13.1 6.14 6.14.1 6.15 6.15.1 6.16 6.16.1 6.17 6.17.1 6.18 6.18.1 6.19 6.19.1 6.20 6.20.1

10

Description of LTE2148: FHPC Flexi RRH 2/2-Pipe 700&850 100W K...................................................................................... 493 LTE2156: Site Aggregation for Flexi Zone................................. 495 Description of LTE2156: Site Aggregation Solution for Flexi Zone.. 495 LTE2172: BTS Configurations optimized for distributed RRH deployment ................................................................................497 Description of LTE2172: BTS Configurations optimized for distributed RRH deployment...................................................... 497 LTE2245: FHEI Flexi Metro RRH 2-pipe 1800 10W L................499 Description of LTE2245: FHEI Flexi Metro RRH 2-pipe 1800 10W L................................................................................................. 499 LTE2263: FRCG Flexi RRH 2-Pipe 850 120W...........................501 Description of LTE2263: FRCG Flexi RRH 2-Pipe 850 120W....501 LTE2264: FRNC Flexi RRH 4-Pipe 2300 120W ........................503 Description of LTE2264: FRNC Flexi RRH 4-Pipe 2300 120W..503 LTE2266: FRBG Flexi RRH 4-Pipe 730&720T 160W................ 505 Description of LTE2266: FRBG Flexi RRH 4-Pipe 730&720T 160W..........................................................................................505 LTE2272: SW-support for classical WCDMA/LTE RF-sharing Indoor configurations..................................................................507 Description of LTE2272: SW-support for classical WCDMA/LTE RF-sharing Indoor configurations...............................................507 LTE2310: FRCC Flexi RRH 2-Pipe 865 80W S..........................511 Description of LTE2310: FRCC Flexi RRH 2-Pipe 865 80W S........ 511 LTE2334: LTE-GSM RF sharing with 4-way RX diversity.......... 513 Description of LTE2334: LTE-GSM RF sharing with 4-way RX diversity ..................................................................................... 513 LTE2420: Supported RAS installation options in FL15A release..... 516 Description of LTE2420: Supported RAS installation options in FL15A release............................................................................516 LTE2448: FASB 2.4m RAS 1.9G 1.7/2.1G 698-894M............... 519 Description of LTE2448: FASB 2.4m RAS 1.9G 1.7/2.1G 698894M.......................................................................................... 519 LTE2449: FASC 2.0m RAS 2.3-2.6G 1.7-2.2G 694-960M......... 522 Description of LTE2449: FASC 2.0m RAS 2.3-2.6G 1.7-2.2G 694960M.......................................................................................... 522 LTE2471: FXEE Flexi RFM 3-Pipe 1800 240W ........................ 524 Description of LTE2471: FXEE Flexi RF Module 3TX 1800.......524

DN09185982

Issue: 01D


List of Figures

Issue: 01D

Figure 1

HO messages.....................................................................................39

Figure 2

The comparison of LTE786: Flexible UL Bandwidth and LTE825: UL Outer Region Scheduling features .................................................... 53

Figure 3

MBMS architecture............................................................................. 75

Figure 4

MBMS definitions................................................................................78

Figure 5

RIM protocol structure between E-UTRAN and UTRAN.................... 92

Figure 6

Redirection procedure with SI............................................................ 93

Figure 7

Complete signaling flow....................................................................106

Figure 8

LTE - UTRAN load balancing............................................................110

Figure 9

Examples of three-cell CA................................................................ 151

Figure 10

Example of frequency layers in the LTE1942 feature....................... 174

Figure 11

Example of frequency layers in the LTE1942 feature when LTE1127 is active................................................................................................ 175

Figure 12

U-plane overload handling................................................................190

Figure 13

SIB reception with parallel measurement gaps................................ 206

Figure 14

Scenario 1........................................................................................ 220

Figure 15

Scenario 2........................................................................................ 220

Figure 16

Scenario 3........................................................................................ 221

Figure 17

A supplementary cell used as a secondary cell (SCell) in carrier aggregation.......................................................................................224

Figure 18

Hybrid Sync, GPS1pps/ToD + SyncE, normal tuning ...................... 267

Figure 19

Hybrid Sync, GPS1pps/ToD + SnycE, assisted holdover ................ 268

Figure 20

Hybrid Sync, ToP-P/PTP + SyncE, normal tuning............................ 268

Figure 21

Hybrid Sync, ToP-P/PTP + SyncE, assisted holdover...................... 269

Figure 22

Configuration example with two U-plane addresses........................ 274

Figure 23

Configuration example with two separate U-plane addresses......... 276

Figure 24

Basic user scenario 1....................................................................... 284

Figure 25


Figure 26


Figure 27

Exemplary scenario with two external Ethernet links and two U-plane addresses......................................................................................... 285

Figure 28

Typical environment with a minimum of 4 satellites..........................292

Figure 29

Urban canyon environment.............................................................. 293

Figure 30

Software verification procedure in LTE790....................................... 299

Figure 31

Service Account Access Settings menu........................................... 305

Figure 32

Changing the toor4nsn password in NEAC tool............................... 307

Figure 33

LTE154 Auto-Connection with DHCP server.................................... 322

Figure 34

LTE1058 Auto Connection without DHCP server............................. 322

Figure 35

Use cases.........................................................................................326

Figure 36

Use case 1: Visualization................................................................. 328

DN09185982

11


12

Figure 37


Figure 38


Figure 39

Logging of parameters using Audit Trail........................................... 346

Figure 40

Activating RF monitoring.................................................................. 362

Figure 41

Executing RF scan........................................................................... 363

Figure 42

Standalone FZM versus LTE1996 Zone eNB deployment of small cells ..........................................................................................................386

Figure 43

Flexi Zone System Architecture management..................................387

Figure 44

Overview of IPSec implementation in Flexi Zone Controller............ 391

Figure 45

Top-down approach for system upgrade.......................................... 402

Figure 46

Overview Flexi Zone Plug and Play Auto Connection...................... 428

Figure 47

Flexi Zone Plug and Play Auto-Connection......................................429

Figure 48

Deployment Scenario 1a: CA-server accessible only in operator's private network AND the initial security gateway and the serving security gateway are the same.........................................................431

Figure 49

Deployment Scenario 1b: CA-server is accessible only in operator's private network AND the initial security gateway and the serving security gateway are different...........................................................432

Figure 50

Deployment Scenario 2: CA-server accessible via the public network... 434

Figure 51

Shared backhaul deployment........................................................... 455

Figure 52

RF Sharing with dedicated Flexi System Modules........................... 468

Figure 53

Enabling RF Sharing........................................................................ 473

Figure 54

Enable EIF2 as RP3-01 interface..................................................... 481

Figure 55

LTE - Concurrent Mode Settings for LTE-LTE.................................. 482

Figure 56

Configuration 1................................................................................. 509

Figure 57

Configuration 2................................................................................. 510

Figure 58

Configurations 3, 4, 5, and 6............................................................ 510

DN09185982

Issue: 01D


List of Tables

Issue: 01D

Table 1

Hardware and software requirements................................................ 28

Table 2

New dedicated thresholds introduced with the LTE64: Service-based Handover Thresholds feature............................................................. 29

Table 3

New counters......................................................................................31

Table 4

New parameters................................................................................. 31

Table 5

Related existing parameters...............................................................32

Table 6

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

Table 7

Parameters used for activating and configuring LTE64: Service-based Handover Thresholds......................................................................... 33

Table 8


Table 9

New counters......................................................................................41

Table 10

New parameters................................................................................. 42

Table 11

Modified parameters...........................................................................43

Table 12


Table 13


Table 14

Parameters used for activating and configuring LTE738: SRVCC to 1xRTT/CDMA..................................................................................... 48

Table 15


Table 16

Modified counters............................................................................... 55

Table 17

New parameters................................................................................. 58

Table 18


Table 19


Table 20

Parameters used for activating and configuring LTE825: Uplink Outer Region Scheduling............................................................................. 59

Table 21


Table 22

New counters......................................................................................67

Table 23

New parameters................................................................................. 68

Table 24


Table 25


Table 26

Parameters used for activating and configuring LTE951: Enhanced Cell ID Location Service..................................................................... 69

Table 27


Table 28

New counters......................................................................................80

Table 29

New parameters................................................................................. 80

Table 30


Table 31


Table 32

Parameters used for activating and configuring the LTE1117: LTE MBMS feature.....................................................................................84

Table 33

MBMS Data Rate table.......................................................................85

Table 34


DN09185982

13


14

Table 35

Related existing alarms...................................................................... 96

Table 36

New parameters................................................................................. 96

Table 37


Table 38

Parameters used for activating and configuring LTE1196: RAN Information Management for WCDMA............................................... 98

Table 39

Hardware and software requirements.............................................. 105

Table 40

LTE519 and LTE1321 comparison................................................... 105

Table 41

New counters....................................................................................108

Table 42

Modified parameters.........................................................................108

Table 43

Sales information..............................................................................108

Table 44


Table 45

New counters.................................................................................... 112

Table 46

New parameters............................................................................... 113

Table 47

Related existing parameters............................................................. 113

Table 48

Sales information.............................................................................. 114

Table 49

Parameters used for activating and configuring LTE1357: LTE-UTRAN Load Balancing................................................................................. 115

Table 50


Table 51

New parameters............................................................................... 122

Table 52


Table 53

Parameters used for activating and configuring LTE1635: SIB 8 AC Barring for 1xRTT............................................................................. 123

Table 54


Table 55

New parameters............................................................................... 130

Table 56

Related existing parameters.............................................................130

Table 57


Table 58

Parameters used for activating and configuring LTE1679: DRX with Parallel UE Measurement Gaps....................................................... 131

Table 59


Table 60

BTS faults......................................................................................... 136

Table 61

New counters....................................................................................136

Table 62

New Parameters...............................................................................136

Table 63


Table 64


Table 65

Parameters used for activating and configuring LTE1788: Automatic Access Class Barring....................................................................... 140

Table 66


Table 67

New counters....................................................................................155

Table 68

New key performance indicators...................................................... 156

Table 69

New parameters............................................................................... 156

Table 70


DN09185982

Issue: 01D


Issue: 01D

Table 71


Table 72


Table 73

Parameters used for activating and configuring the LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature......................160

Table 74


Table 75

New parameters............................................................................... 166

Table 76


Table 77


Table 78

Parameters used for activating and configuring LTE1905: PLMN ID and SPID Selected Mobility Profiles................................................. 168

Table 79


Table 80

New parameters............................................................................... 177

Table 81


Table 82


Table 83

Parameters used for activating and configuring the LTE1942: Dedicated VoLTE Inter-Frequency Target Frequency List................177

Table 84


Table 85

New counters....................................................................................183

Table 86

New parameters............................................................................... 183

Table 87


Table 88

Parameters used for activating and configuring LTE1944: Dynamic Handover Blacklisting....................................................................... 183

Table 89


Table 90

New counters....................................................................................188

Table 91

New parameters............................................................................... 188

Table 92


Table 93


Table 94


Table 95

Mapping between U-plane overload triggers and the related countermeasures..........................................................................................191

Table 96

New BTS faults.................................................................................194

Table 97

New counters....................................................................................194

Table 98


Table 99

New parameters............................................................................... 194

Table 100


Table 101

Parameters used for activating and configuring LTE2023: User Plane Overload Handling............................................................................195

Table 102


Table 103

New counters....................................................................................200

Table 104

New parameters............................................................................... 200

Table 105


Table 106


DN09185982

15


16

Table 107

Parameters used for activating and configuring LTE2051: Measurement based Idle Mode Load Balancing feature.................. 201

Table 108


Table 109

Modified counters............................................................................. 208

Table 110

New parameters............................................................................... 209

Table 111

Related existing parameters ............................................................209

Table 112


Table 113

Parameters used for activating and configuring LTE2085: SIB Reception with Parallel Measurement Gaps.................................... 210

Table 114

Parameters used for activating and configuring LTE2085: SIB Reception with Parallel Measurement Gaps.....................................211

Table 115

Parameters used for deactivating LTE2085: Reception with Parallel Measurement Gaps.......................................................................... 217

Table 116


Table 117


Table 118


Table 119


Table 120

New parameters............................................................................... 226

Table 121


Table 122


Table 123

Parameters used for activating and configuring LTE2149: Supplemental Downlink Carrier........................................................ 227

Table 124


Table 125


Table 126


Table 127

New BTS faults.................................................................................238

Table 128


Table 129


Table 130

New BTS faults.................................................................................243

Table 131

New parameters............................................................................... 243

Table 132


Table 133

Parameters used for activating and configuring the LTE2305: IntereNodeB Carrier Aggregation for 2 Macro eNodeBs feature............. 244

Table 134


Table 135

New parameters............................................................................... 250

Table 136


Table 137

Parameters used for configuring LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release.................................................................... 250

Table 138


Table 139

Parameters list..................................................................................257

Table 140


DN09185982

Issue: 01D


Issue: 01D

Table 141

Table 4 lists the parameters used for activating and configuring the LTE2324: Network-requested UE Radio Capabilities feature...........258

Table 142


Table 143

New parameters............................................................................... 261

Table 144


Table 145


Table 146

Parameters used for activating and configuring LTE2430: QCI1 Establishment Triggered Protection Timer feature........................... 262

Table 147


Table 148

Chosen synchronization source....................................................... 266

Table 149

Meaning of terms in the figures........................................................ 266

Table 150

Related existing alarms.................................................................... 270

Table 151

Related existing faults...................................................................... 270

Table 152

New parameters............................................................................... 270

Table 153


Table 154

Parameters used for activating and configuring LTE942: Hybrid Synchronization................................................................................ 271

Table 155


Table 156

IPRT/static routes............................................................................. 277

Table 157

RTPOL/routingPolicies..................................................................... 277

Table 158

New parameters............................................................................... 278

Table 159


Table 160


Table 161

New counters....................................................................................280

Table 162

New parameters............................................................................... 282

Table 163


Table 164


Table 165


Table 166

Modified BTS faults.......................................................................... 288

Table 167

New parameters............................................................................... 288

Table 168


Table 169


Table 170

Parameters used for activating and configuring LTE1771: Dual Uplane IP Addresses.......................................................................... 289

Table 171


Table 172

New parameters............................................................................... 295

Table 173


Table 174

Parameters used for activating and configuring LTE2063: GNSS Manual Location Entry......................................................................296

Table 175


Table 176

New BTS faults.................................................................................300

DN09185982

17


18

Table 177


Table 178


Table 179

New parameters............................................................................... 304

Table 180


Table 181

Parameters used for configuring LTE1030: Configurable Service Accounts...........................................................................................304

Table 182


Table 183

New parameters............................................................................... 311

Table 184


Table 185

Parameters used for activating and configuring LTE1049: MDT - UE Measurement Logs...........................................................................313

Table 186


Table 187

New BTS faults.................................................................................318

Table 188

New parameters............................................................................... 319

Table 189


Table 190


Table 191


Table 192


Table 193

New counters....................................................................................338

Table 194

Modified counters............................................................................. 338

Table 195

New parameters............................................................................... 339

Table 196


Table 197


Table 198

Parameters used for activating and configuring LTE1103: Load Based Power Saving for Multi-layer Networks feature................................ 341

Table 199


Table 200


Table 201


Table 202

New BTS faults.................................................................................349

Table 203


Table 204


Table 205

Supported combinations of file transfer protocols and syslog formats... 353

Table 206

New parameters............................................................................... 353

Table 207

LTE1408: Sales information............................................................. 354

Table 208

Parameters used for activating and configuring LTE1408: Remote Syslog for Continuous Log Storage..................................................354

Table 209


Table 210

New parameters............................................................................... 359

Table 211


Table 212

Parameters used for activating and configuring LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing............................................360

DN09185982

Issue: 01D


Issue: 01D

Table 213


Table 214

New counters ...................................................................................368

Table 215

New parameters............................................................................... 369

Table 216


Table 217

Parameters used for activating and configuring Mobility Robustness Monitoring Inter RAT.........................................................................369

Table 218


Table 219

New counters....................................................................................373

Table 220

New parameters............................................................................... 374

Table 221


Table 222


Table 223

New counters....................................................................................376

Table 224


Table 225

Modified key performance indicators................................................379

Table 226


Table 227


Table 228

New counters....................................................................................382

Table 229


Table 230


Table 231


Table 232

Related parameters.......................................................................... 384

Table 233


Table 234


Table 235


Table 236


Table 237

New parameters............................................................................... 392

Table 238


Table 239

add fzc-ipsec commands..........................................................394

Table 240

delete fzc-ipsec commands...................................................399

Table 241


Table 242


Table 243


Table 244


Table 245


Table 246

New BTS faults................................................................................. 411

Table 247

New parameters............................................................................... 412

Table 248


Table 249


Table 250


Table 251


DN09185982

19


20

Table 252

Parameters used for activating and configuring LTE2084: UE MAC Measurement Addition to Cell Trace................................................ 420

Table 253


Table 254

New counters....................................................................................425

Table 255


Table 256


Table 257


Table 258

New parameters............................................................................... 437

Table 259


Table 260


Table 261

Related Alarms................................................................................. 439

Table 262

Related counters.............................................................................. 442

Table 263


Table 264


Table 265


Table 266


Table 267


Table 268


Table 269

FRME functional specification.......................................................... 465

Table 270


Table 271


Table 272

New BTS faults.................................................................................469

Table 273

New parameters............................................................................... 469

Table 274


Table 275


Table 276


Table 277

Parameters used for activating and configuring LTE1829: Inter eNB RF Sharing....................................................................................... 470

Table 278


Table 279


Table 280


Table 281

FRBE functional specification...........................................................488

Table 282


Table 283


Table 284

FRBF functional specification........................................................... 490

Table 285


Table 286


Table 287

FHGB functional specification.......................................................... 492

Table 288


Table 289


Table 290

FHPC functional specification...........................................................494

DN09185982

Issue: 01D


Issue: 01D

Table 291


Table 292


Table 293


Table 294


Table 295


Table 296


Table 297

FHEI functional specification............................................................ 500

Table 298


Table 299


Table 300

FRCG functional specification.......................................................... 502

Table 301


Table 302


Table 303

FRNC functional specification.......................................................... 504

Table 304


Table 305


Table 306

FRBG functional specification.......................................................... 506

Table 307


Table 308


Table 309

Configurations introduced by the feature..........................................509

Table 310

Sales information.............................................................................. 511

Table 311


Table 312

FRCC functional specification.......................................................... 512

Table 313


Table 314


Table 315

Shared LTE and GSM pipes, centralized site solution .................... 515

Table 316

Shared LTE and GSM pipes, distributed site solution...................... 515

Table 317


Table 318


Table 319

Supported RAS installation options in FDD-LTE 15A ...................... 517

Table 320


Table 321


Table 322


Table 323


Table 324


Table 325


Table 326


DN09185982

21

Summary of changes


Summary of changes Changes between issues 01C (2015-09-30, FDD-LTE15A) and 01D (2015-11-02, FDD-LTE15A) The following feature has been updated: Operability LTE1408: Remote Syslog for Continuous Log Storage Changes between issues 01B (2015-07-30, FDD-LTE15A) and 01C (2015-09-30, FDD-LTE15A) The following features have been updated: Radio Ressource Management • • • • • • • •

LTE1905: PLMN ID and SPID selected mobility profiles LTE738: SRVCC to 1xRTT/CDMA LTE1804: Downlink carrier aggregation 3CC - 60 MHz LTE2208: eICIC enhancements - micro LTE2023: User plane overload handling LTE2133: eICIC for HetNet eNode B configurations LTE2305: Inter eNodeB Carrier Aggregation for 2 macro eNodeBs LTE825: Uplink outer region scheduling

Operability • • • • • • • • • • • •

LTE1058: Plug & Play extensions LTE1030: Configurable Service Accounts LTE1103: Load based Power Saving for multi-layer networks LTE1408: Remote Syslog for continous log storage LTE1949: Extend Power Reduction Range LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness LTE2195: Integrated O&M for Ruckus WiFi LTE2175: PM counter enhancement for CSFB to 1xRTT, CQI level, E-RAB abnormal Release LTE1899: Dedicated PM-counters for E-RAB Management failure causes LTE1912: RRC establishment monitoring extensions LTE2017: IPSec Support for Flexi Zone Controller LTE2346: Flexi Zone Controller Shared Backhaul Support- Phase I

BTS Site Solution • • • • • •

LTE2147: FHGB Flexi RRH 4TX 2100 LTE2266: FRBG Flexi RRH 2TX 4RX 730 2TX 720 LTE2245: FHEI Flexi Metro RRH 2-pipe 1800 10W L LTE2420: Supported RAS Installation options in FL15A release LTE2272: SW-support for classical WCDMA/LTE RF-sharing Indoor configurations LTE2334: LTE-GSM RF sharing with 4-way RX diversity

The following feature has been added:

22

DN09185982

Issue: 01D


Summary of changes

BTS Site Solution LTE2448: FASB 2.4m RAS 1.9G 1.7/2.1G 698-894M Changes between issues 01A (2015-06-30, FDD-LTE15A) and 01B (2015-07-30, FDD-LTE15A) The following features have been updated: Operability • • • •

LTE1996: Flexi Zone Controller Application LTE2017: IPSec Support for Flexi Zone Controller LTE2049: System Upgrade to FDD-LTE 15A LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I

The following features have been removed: BTS Site Solution • •

LTE2448: FASB 2.4m RAS 1.9G 1.7/2.1G 698-894M LTE2525: FASE 1.8m RAS 2.6G 1.9G 814-894M

Changes between issues 01 (2015-05-15, FDD-LTE15A) and 01A (2015-06-30, FDDLTE15A) The following features have been updated: Radio Resource Management and Telecom • • • • • • • • • • • • • • •

LTE2091: FDD SuperCell extension RL70 LTE1042: Nominal Bitrate for non-GBR bearers RL70 LTE951: Enhanced cell ID location service LTE1905: PLMN ID and SPID selected mobility profiles LTE1942: Dedicated VoLTE inter-frequency target frequency list LTE64: Service based handover thresholds LTE738:SRVCC to 1xRTT/CDMA LTE1804: Downlink carrier aggregation 3CC - 60 MHz LTE1357: LTE-UTRAN load balancing LTE2430: QCI1 Establishment Triggered Protection Timer LTE2168: Additional carrier aggregation band combinations - II LTE2023: User plane overload handling LTE1788: Automatic access class barring LTE2149: Supplemental downlink carrier LTE2305: Inter eNodeB Carrier Aggregation for 2 macro eNodeBs

Transport and Transmission •

LTE1244: Source based routing in BTS

Operability • • •

Issue: 01D

LTE1749: Mobility Robustness Monitoring Inter RAT LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness LTE2049: System Upgrade to FDD-LTE 15A

DN09185982

23

Summary of changes


• • • • • • • • • • • •

LTE1052: Transport Configuration Fall-back LTE1049: MDT - UE measurement logs LTE1030: Configurable Service Accounts LTE1103: Load based Power Saving for multi-layer networks LTE2175: PM counter enhancement for CSFB to 1xRTT, CQI level, E-RAB abnormal Release LTE1879: Additional PM-counters for Mobility Event monitoring LTE1899: Dedicated PM-counters for E-RAB Management failure causes LTE1912: RRC establishment monitoring extensions LTE1996: Flexi Zone Controller Application LTE2017: IPSec Support for Flexi Zone Controller LTE2346: Flexi Zone Controller Shared Backhaul Support- Phase I LTE2061: OMS HP Gen9 HW

BTS Site Solution •

LTE1829: Inter eNB RF sharing

The following features have been added: Radio Resource Management and Telecom • • •

LTE1117: LTE MBMS LTE2006: Flexible Scell selection LTE2324: Network requested UE radio capabilities

BTS Site Solution • • •

24

LTE2272: SW-support for classical WCDMA/LTE RFsharing Indoor configurations LTE2334: LTE-GSM RF sharing with 4-way RX diversity LTE2471: FXEE Flexi RF Module 3TX 1800

DN09185982

Issue: 01D


Introduction

1 Introduction This document provides the list of feature descriptions for the LTE Radio Access Network Release. Hardware (HW) requirements indicate if the feature requires specific HW from the RAN LTE portfolio. If the feature has no specific hardware requirements, it means that only LTE System Module should be used. The subchapter Interdependencies between features lists only dependencies among Nokia RAN LTE features.

Issue: 01D

DN09185982

25

Activating and deactivating LTE features using BTS Site Manager


2 Activating and deactivating LTE features using BTS Site Manager Purpose Follow this general BTS Site Manager (BTSSM) procedure to activate or deactivate LTE features. Before you start The eNB must already be commissioned. The BTS Site Manager can be connected to the eNB either locally, or from a remote location. For information on feature-specific prerequisites, see section Before you start of every feature-specific procedure.

Steps 1

Start the BTSSM application and establish the connection to the eNB. For details, see Launching BTS Site Manager in Commissioning Flexi Multiradio BTS LTE or the BTSSM online help (section Instructions).

2

Upload the configuration plan file from the eNB. When the BTSSM is connected to the eNB, it automatically uploads the current configuration plan file from the eNB. a) Select View ► Commissioning or click Commissioning on the View bar. b) The BTS Site checkbox, located in the Target section, is selected by default. This is the recommended setting. c) Choose the commissioning type. Use the Template, Manual, or Reconfiguration option depending on the actual state of the eNB. For details, see Manual commissioning, Performing template commissioning, and Performing reconfiguration commissioning in Commissioning Flexi Multiradio BTS LTE.

3

Modify the feature-specific eNB configuration settings. The feature-related settings are found in the set of Commissioning pages. In the top right-hand corner of the BTSSM window, there is a location bar that shows at which stage of the Commissioning process the user is. It is recommended that the user carefully reads the pages containing full eNB configuration information.

26

DN09185982

Issue: 01D


4

Activating and deactivating LTE features using BTS Site Manager

Send the commissioning plan file to the eNB. Sub-steps a) Go to the Send Parameters page. b) In section Send, choose whether the BTSSM should send to the eNB only the changed parameters: Only changes (may require reset), or a whole set of parameters: All parameters (requires reset). c) Click the Send Parameters button.

5

The new commissioning plan file is automatically activated in the eNB. Sub-steps a) After successful transmission of the parameters, the new configuration is automatically activated. The BTSSM automatically sends an activation command after finishing the file download.

b) If the configuration changes require restart, the eNB performs the restart now.

g

Issue: 01D

Note: For information on possible restarts, see section Before you start of every feature -specific procedure.

DN09185982

27

Descriptions of radio resource management and telecom features


3 Descriptions of radio resource management and telecom features 3.1 LTE64: Service-based Handover Thresholds 3.1.1 Description of LTE64: Service-based Handover Thresholds Introduction to the feature The LTE64: Service-based Handover Thresholds feature introduces dedicated handover (HO) thresholds that are used when a UE has a QCI1 bearer active. Benefits End-user benefits Better radio frequency coverage for VoLTE users is ensured. VoLTE users can be handed over either earlier or later than data-only users. Operator benefits This feature provides: • •

different points of activation/deactivation of inter-frequency/inter-RAT measurements (A1/A2 event) different points of triggering of the inter-frequency/inter-RAT handover (A3/A5/B2 event)

Requirements Hardware and software requirements Table 1 System release FDD-LTE 15A

Hardware and software requirements Flexi Multiradio BTS FL15A

Flexi Zone Controller FL16

Flexi Multiradio 10 BTS FL15A

OMS -

UE 3GPP R8 UE capabilities

Flexi Zone Micro BTS FL15A

FL16

NetAct NetAct 15.5

Flexi Zone Access Point

MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description The operator can configure dedicated thresholds for a UE that has a QCI1 bearer (VoLTE call) established. Table 2: New dedicated thresholds introduced with the LTE64: Service-based Handover Thresholds feature shows which of the new measurements are active in particular handovers.

28

DN09185982

Issue: 01D


Table 2


New dedicated thresholds introduced with the LTE64: Service-based Handover Thresholds feature HO

Measurement type

inter-frequency intra- A1 to stop inter-frequency HO LTE measurements A2 to start inter-frequency HO measurements A3 for inter-frequency HO measurements (better cell)

New dedicated threshold for HO measurement A1_QCI1 A2_QCI1_IF A3_QCI1_IF A5_QCI1_IF

A5 for inter-frequency HO measurements (coverage) SRVCC LTE to WCDMA

A1 to stop SRVCC measurements

A1_QCI1

B2 for SRVCC measurements

B2_QCI1_WCDMA

SRVCC LTE to GERAN


A1_QCI1

B2 for SRVCC measurements

B2_QCI1_GERAN

SRVCC LTE to 1xRTT


A1_QCI1

A2 to start SRVCC measurements

A2_QCI1_C2K

For other dedicated HO thresholds, see the LTE2112: Dedicated Mobility Thresholds for SRVCC, LTE1198: RSRQ Triggered Mobility, and LTE738: SRVCC to 1xRTT/CDMA feature descriptions. The thresholds introduced with the LTE64: Service-based Handover Thresholds feature are as follows: • • • • •

dedicated VoLTE A2 threshold to start LTE inter-frequency measurements dedicated VoLTE A2 thresholds to start SRVCC to 1xRTT measurements dedicated VoLTE A1 threshold to stop inter-frequency or SRVCC measurements dedicated A3/A5 measurement setting per target frequency layer for inter-frequency HO dedicated B2 measurement (GSM, UTRAN) setting per target frequency layer

The A1/A2/A3/A5/B2 measurement configurations are updated with the establishment/removal of a QCI1 bearer. The usage of separate QCI1 thresholds is optional. This means that if the LTE64: Service-based Handover Thresholds feature is activated, and a value for a threshold for QCI1 is given, then this threshold will be used. If no such separate threshold is given, then a legacy threshold is used instead. The operator is free to use the separate QCI1 thresholds for each threshold which is supported. Upon the establishment of a QCI1 bearer, all thresholds are exchanged by the configured QCI1 values. The eNB always stores the last reported RSRP value of the UE and uses this at the QCI1 establishment/release to select (and configure) the correct

Issue: 01D

DN09185982

29



thresholds. This is done as thresholds may have to be changed and, therefore, another set of configured thresholds might be needed based on the last reported RSRP value (which is stored in the eNB). Disabling A2-based redirect for VoLTE calls The LTE64: Service-based Handover Thresholds feature introduces an O&M parameter to disable an A2-based redirect when a UE has a QCI1 bearer established. When this parameter is set to disabled, and the first QCI1 bearer is established for the UE, both RSRP- and RSRQ-based A2-redirect measurements (if configured) will be either deactivated or not activated. The measurements will be re-activated when the UE has no longer any QCI1 bearer. When this parameter is set to enabled, then the A2-based redirect configuration will not change in case of a QCI1 bearer establishment/release. Disabling the A2-based redirect when a UE has a QCI1 bearer is not controlled by the LTE64: Service-based Handover Thresholds feature flag. This feature flag controls the usage of dedicated thresholds only. System impact Interdependencies between features •

•

•

• •

•

•

•

LTE2112: Dedicated Mobility Thresholds for SRVCC The actServBasedMobThr feature flag is shared by the LTE64: Service-based Handover Thresholds and LTE2112: Dedicated Mobility Thresholds for SRVCC features. LTE10: EPS Bearers for Conversational Voice This feature implements support for a QCI1 bearer and is required for the support of VoLTE calls. LTE55: Inter-frequency Handover The new A2/A3/A5 thresholds for an inter-frequency HO are used only if this feature is enabled. LTE56: Inter-RAT Handover to WCDMA SRVCC to WCDMA can be used only if this feature is enabled. LTE1060: TDD - FDD Handover This feature needs to be enabled together with the LTE64: Service-based Handover Thresholds feature if an FDD-TDD handover is needed for VoLTE calls. LTE1198: RSRQ Triggered Mobility When the A2-RSRQ mobility event is received, if the O&M flag for A2-redirect for QCI1 is disabled, and a UE has a QCI1 bearer, the A2-RSRQ-redirect measurement will not be activated. LTE423: RRC Connection Release with Redirect If the O&M flag for A2-redirect for QCI1 is disabled, and a UE has a QCI1 bearer, the A2-RSRP measurement for redirection will not be activated. LTE1407: RSRQ-based Redirect If the O&M flag for A2-redirect for QCI1 is disabled, and a UE has a QCI1 bearer, the A2-RSRQ measurement for redirection will not be activated.

Impact on interfaces This feature has no impact on interfaces. Impact on network management tools This feature has no impact on network management tools.

30

DN09185982

Issue: 01D



Impact on system performance and capacity The LTE64: Service-based Handover Thresholds feature improves SRVCC and VoLTE call drop rate by decreasing VoLTE coverage via earlier start of inter-frequency and interRAT measurements and specific HO thresholds for VoLTE leading to earlier handovers. This depends on how the HO thresholds are set. Management data Alarms There are no alarms related to this feature. Measurements and counters Table 3: New counters lists counters introduced with this feature. Table 3

New counters Counter ID

Counter name

Measurement

M8021C37

Inter-frequency handover 8021 - LTE Handover (WBTS) attempts for UEs with QCI1 (A3/A5 radio related handovers only)

M8021C38

Successful inter-frequency handover completions for UEs with QCI1 (A3/A5 radio related handovers only)

8021 - LTE Handover (WBTS)

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

New parameters

Full name

Issue: 01D

Abbreviated name

Managed object

Structure

RSRP threshold 2 For CDMA2000 during QCI1

threshold2C2kQci1

LNCEL

threshold2C2kConfig

A2 based redirect for VoLTE calls

a2RedirectQci1

LNCEL

-

Threshold Th2 InterFreq for RSRP during QCI1

threshold2InterFreqQc LNCEL i1

-

Threshold Th2a for RSRP During QCI1

threshold2aQci1

LNCEL

-

A3 Offset RSRP Inter Frequency during QCI1

a3OffsetRsrpInterFreq Qci1

LNHOIF

-

Threshold Th3 For RSRP inter frequency during QCI1

threshold3InterFreqQc LNHOIF i1

-

DN09185982

31


Table 4


New parameters (Cont.)

Full name

Abbreviated name

Managed object

Structure

Threshold Th3a For RSRP inter frequency during QCI1

threshold3aInterFreqQ LNHOIF ci1

-

Threshold1 GERAN for RSRP of serving cell during QCI1

b2Threshold1GERAN Qci1

LNHOG

-

Threshold2 GERAN b2Threshold2RssiGE For RSSI neighbor cell RANQci1 during QCI1

LNHOG

-

Threshold1 UTRA for RSRP of serving cell during QCI1

b2Threshold1UtraQci1 LNHOW

-

Threshold2 UTRA for ecNo neighbor cell during QCI1

b2Threshold2UtraEcn 0Qci1

LNHOW

-

Threshold2 UTRA for RSCP neighbor cell during QCI1

b2Threshold2UtraRsc pQci1

LNHOW

-

Table 5: Related existing parameters lists existing parameters related to this feature. Table 5

Related existing parameters

Full name

32

Abbreviated name

Managed object

Structure

Activate service based actServBasedMobThr mobility thresholds

LNBTS

-

Threshold 2 config for CDMA2000 HRPD and 1xRTT

LNCEL

-

threshold2C2kConfig

Time to trigger for A2 a2TimeToTriggerActC2 LNCEL to activate CDMA2000 kMeas measurement

threshold2C2kConfig

Related hysteresis of RSRP threshold 2 for CDMA2000

hysThreshold2C2k

LNCEL

threshold2C2kConfig

RSRP threshold 2 for CDMA2000

threshold2C2k

LNCEL

threshold2C2kConfig

Threshold th2 GERAN threshold2GERANQci for RSRP during QCI1 1

LNCEL

-

Threshold th2 interFreq for RSRP

threshold2InterFreq

LNCEL

-

Threshold th2a for RSRP

threshold2a

LNCEL

-

Threshold th4 for RSRP

threshold4

LNCEL

-

Threshold th2 WCDMA for RSRP during QCI1

threshold2WcdmaQci1 LNCEL

-

DN09185982

Issue: 01D


Table 5


Related existing parameters (Cont.)

Full name

Abbreviated name

Managed object

Structure

Threshold th2 GERAN threshold2GERAN for RSRP

LNCEL

-

Threshold th2 WCDMA for RSRP

LNCEL

-

threshold2Wcdma

Sales information Table 6

Sales information BSW/ASW

License control in network element

ASW

SW Asset Monitoring

Activated by default No

3.1.2 Activating and configuring LTE64: Service-based Handover Thresholds Before you start Table 7: Parameters used for activating and configuring LTE64: Service-based Handover Thresholds lists the parameters used for activating and configuring the LTE64: Servicebased Handover Thresholds feature. Table 7

Parameters used for activating and configuring LTE64: Service-based Handover Thresholds Parameter

Issue: 01D

Purpose

Requires eNB restart or object locking

Activate service based mobility thresholds (actServBasedMobThr)

activation flag

no

Threshold Th2a for RSRP During QCI1 (threshold2aQci1)

optional configuration

no

Threshold Th2 InterFreq for RSRP during QCI1 (threshold2InterFreqQci1)


no

RSRP threshold 2 For CDMA2000 during QCI1 (threshold2C2kQci1)


no

A3 Offset RSRP Inter Frequency during QCI1 (a3OffsetRsrpInterFreqQci1)


no

Threshold Th3 For RSRP inter frequency during QCI1 (threshold3InterFreqQci1)


no

Threshold Th3a For RSRP inter frequency during QCI1 (threshold3aInterFreqQci1)


no

Threshold1 UTRA for RSRP of serving cell during QCI1 (b2Threshold1UtraQci1)


no

Threshold2 UTRA for ecNo neighbor cell during QCI1 (b2Threshold2UtraEcn0Qci1)


no

DN09185982

33


Table 7


Parameters used for activating and configuring LTE64: Service-based Handover Thresholds (Cont.) Parameter

Purpose


Threshold2 UTRA for RSCP neighbor cell during QCI1 (b2Threshold2UtraRscpQci1)


no

Threshold1 GERAN for RSRP of serving cell during QCI1 (b2Threshold1GERANQci1)


no

Threshold2 GERAN For RSSI neighbor cell during QCI1 (b2Threshold2RssiGERANQci1)


no

The following features need to be activated/configured before activation of the LTE64: Service-based Handover Thresholds feature: • • •

• •

•

•

LTE10: EPS Bearers for Conversational Voice LTE7: Support of Multiple EPS Bearer If SRVCC to WCDMA is required, then the LTE872: SRVCC to WCDMA and LTE56: Inter-RAT Handover to WCDMA features must be enabled, and corresponding A2/A1 and B2 dedicated thresholds must be configured. If SRVCC to GSM is required, then the LTE873: SRVCC to GSM feature must be enabled, and corresponding A2/A1 and B2 dedicated thresholds must be configured. If SRVCC to 1xRTT is required, then the LTE738: SRVCC to 1xRTT/CDMA feature must be enabled, and corresponding A2/A1 dedicated thresholds must be configured. If inter-frequency handover is required for VoLTE calls, then the LTE55: Interfrequency handover feature must be enabled, and corresponding A2/A1 and A3/A5 dedicated thresholds must be configured. The LTE1060: TDD - FDD Handover feature needs to be enabled if an FDD/TDD handover is needed.

Procedure 1

Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure.

2

Activate the LTE64: Service-based Handover Thresholds feature. a) b) c) d)

34

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate service based mobility thresholds (actServBasedMobThr) parameter value to true.

DN09185982

Issue: 01D


3


Configure the A1 RSRP dedicated threshold (optional). a) Expand the LNBTS object. b) Select the LNCEL object. c) Set the Threshold Th2a for RSRP During QCI1 (threshold2aQci1) parameter value.

g

Note: If the Threshold th1 for RSRP (threshold1) LNCEL parameter has a value higher than -140.0, then the Threshold Th2a for RSRP During QCI1 (threshold2aQci1) parameter value needs to be lower than the value of the Threshold th1 for RSRP (threshold1) parameter.

4

Configure the A2 RSRP, A3 RSRP offset, and A5 RSRP threshold1 and threshold2 dedicated thresholds for inter-frequency (if the LTE55: Interfrequency Handover feature is enabled - optional). a) Select the LNCEL object. b) Set the Threshold Th2 InterFreq for RSRP during QCI1 (threshold2InterFreqQci1) parameter value for A2 measurement.

g

Note: The Threshold Th2 InterFreq for RSRP during QCI1 (threshold2InterFreqQci1) parameter value needs to be lower than or equal to the Threshold Th2a for RSRP During QCI1 (threshold2aQci1) LNCEL parameter value. c) Right-click the LNCEL object. d) Select the New LNHOIF object. e) For the LNHOIF object, set the parameter values as follows: • • • • • • •

5

Neighbor interfrequency LTE cell handover identifier (lnHoIfId) Presence antenna port1 (interPresAntP) Measurement bandwidth (measurementBandwidth) Eutra carrier info (eutraCarrierInfo) A3 measurement: A3 Offset RSRP Inter Frequency during QCI1 (a3OffsetRsrpInterFreqQci1) A5 measurement: Threshold Th3 For RSRP inter frequency during QCI1 (threshold3InterFreqQci1) A5 measurement: Threshold Th3a For RSRP inter frequency during QCI1 (threshold3aInterFreqQci1)

Configure the A2 RSRP, B2 threshold1 RSRP, B2 Ecn0, and B2 RSCP dedicated thresholds for SRVCC to WCDMA (if the LTE872: SRVCC to WCDMA feature is enabled - optional). a) Select the LNCEL object. b) Set the Threshold Th2 WCDMA for RSRP during QCI1 (threshold2WcdmaQci1) parameter value for A2 measurement.

Issue: 01D

DN09185982

35


g


Note: The Threshold Th2 WCDMA for RSRP during QCI1 (threshold2WcdmaQci1) parameter value needs to be lower than or equal to the Threshold Th2a for RSRP During QCI1 (threshold2aQci1) LNCEL parameter value. c) Right-click the LNCEL object. d) Select the New LNHOW object. e) For the LNHOW object, set the parameter values as follows: • • • • • •

6

Neighbor WCDMA BTS cell handover identifier (lnHoWId) UTRAN carrier frequency (utraCarrierFreq) B2 measurement: Threshold1 UTRA for RSRP of serving cell during QCI1 (b2Threshold1UtraQci1) B2 measurement: Threshold2 UTRA for ecNo neighbor cell during QCI1 (b2Threshold2UtraEcn0Qci1) B2 measurement: Threshold2 UTRA for RSCP neighbor cell during QCI1 (b2Threshold2UtraRscpQci1) UTRAN carrier frequency (utraCarrierFreq)

Configure the A2 RSRP, B2 threshold1 RSRP, and B2 RSSI dedicated thresholds for SRVCC to GERAN (if the LTE873: SRVCC to GSM feature is enabled - optional). a) Select the LNCEL object. b) Set the Threshold th2 GERAN for RSRP during QCI1 (threshold2GERANQci1) parameter value for A2 measurement.

g

Note: The Threshold th2 GERAN for RSRP during QCI1 (threshold2GERANQci1) parameter value needs to be lower than or equal to the Threshold Th2a for RSRP During QCI1 (threshold2aQci1) LNCEL parameter value. c) Right-click the LNCEL object. d) Select the New LNHOG object. e) For the LNHOG object, set the parameter values as follows: • •

• •

36

Neighbor GERAN BTS cell handover identifier (lnHoGId) 1. Expand the LNHOG object. 2. For the ARFCN value list object, set the ARFCN value list (arfcnValueListGERAN) parameter value. B2 measurement: Threshold1 GERAN for RSRP of serving cell during QCI1 (b2Threshold1GERANQci1) B2 measurement: Threshold2 GERAN For RSSI neighbor cell during QCI1 (b2Threshold2RssiGERANQci1)

DN09185982

Issue: 01D


7


Configure the A2 RSRP dedicated threshold for SRVCC to 1xRTT (if the LTE738: SRVCC to 1xRTT/CDMA feature is enabled) (optional). a) Right-click the LNCEL object. b) Select the New Threshold 2 config for CDMA2000 HRPD and 1xRTT object (if not created). c) For the Threshold 2 config for CDMA2000 HRPD and 1xRTT parameter structure, set the RSRP threshold 2 For CDMA2000 during QCI1 (threshold2C2kQci1) parameter value for A2 measurement.

8

Send the parameters to the eNB according to the procedure described in section Activating and configuring LTE64: Service based Handover Thresholds.

Expected outcome The LTE2112: Dedicated Mobility Thresholds for SRVCC and LTE64: Service-based Handover Thresholds features are activated. The eNB provides support for using dedicated thresholds for inter-frequency VoLTE call handovers, SRVCC to WCDMA, SRVCC to GERAN, and SRVCC to 1xRTT.

3.1.3 Deactivating LTE64: Service-based Handover Thresholds Before you start The Activate service based mobility thresholds (actServBasedMobThr) parameter is used for deactivation. Modification of this parameter requires neither eNB restart nor cell locking. Procedure 1


2

Deactivate the LTE64: Service-based Handover Thresholds feature. a) b) c) d)

Issue: 01D

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate service based mobility thresholds (actServBasedMobThr) parameter value to false.

DN09185982

37


3


Send the parameters to the eNB according to the procedure described in section Deactivating LTE64: Service-based Handover Thresholds.

Expected outcome Both features, LTE2112: Dedicated Mobility Thresholds for SRVCC and LTE64: Servicebased Handover Thresholds, are deactivated. The eNB stops support of dedicated thresholds for VoLTE inter-frequency handovers and for SRVCC to WCDMA/GERAN/1xRTT. The eNB uses legacy thresholds for inter-frequency handovers of VoLTE calls and SRVCC.

3.2 LTE738: SRVCC to 1xRTT/CDMA 3.2.1 Description of LTE738: SRVCC to 1xRTT/CDMA Introduction to the feature With the LTE738: SRVCC to 1xRTT/CDMA feature, coverage and service-based single radio voice call continuity (SRVCC) from LTE to 1xRTT/CDMA are possible. Benefits End-user benefits This feature can keep up VoLTE call continuity SRVCC to 1xRTT/CDMA network. Operator benefits This feature provides seamless handover for voice services to 1xRTT/CDMA when leaving the LTE coverage. Requirements Hardware and software requirements Table 8 System release FDD-LTE 15A

Hardware and software requirements Flexi Multiradio BTS -

FL15A


Flexi Multiradio 10 BTS

OMS -



FL16

NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements The functionality is only applicable to SRVCC-capable multimode devices supporting both LTE and 1xRTT on the respective frequency band. Functional description

38

DN09185982

Issue: 01D



Functional overview The LTE738: SRVCC to 1xRTT/CDMA feature enables service continuity of voice services from the packet-switched (PS) to the circuit-switched (CS) domain when a UE with at least one voice service bearer (QCI1) changes from an LTE to a 1xRTT cell. The SRVCC capability of the UE and the MME is indicated by the MME with the S1AP: INITIAL CONTEXT SETUP REQUEST message. In case of a handover (HO), the target eNB is informed either by the MME via the S1AP: Handover Request message or by the source eNB via the X2AP: Handover Request message; see Figure 1: HO messages. Figure 1

HO messages

X2AP:HandoverRequest

sourceeNB

S1AP:HandoverRequest

targeteNB

MME

SRVCC to 1xRTT/CDMA process The SRVCC is split into three areas: triggering, preparation, and execution. SRVCC trigger •

• •

If the UE has an EPS bearer with at least QCI1 established, and the MME and UE are SRVCC-capable, 1xSRVCC B2 is activated in a UE, based on the air conditions via mobility A2. Only one target 1xRTT carrier can be measured by one UE. QCI1 bearer: –

–

The eNB supports the SRVCC if there is at least one QCI1 bearer established. If the QCI1 bearer is established/released during ongoing measurement, the measurement targets are modified according to 1xSRVCC and HRPD HO measurements (if HO to eHRPD is enabled). The eNB supports 1xSRVCC in case of multiple QCI1 bearers. An evolved packet core (EPC) selects the bearer to execute the SRVCC.

SRVCC preparation •

•

If the eNB receives a measurement report from the UE, it initiates an inter-RAT HO by sending the RRC: Handover From EUTRA Preparation Request message to the UE. The eNB gets the RRC: ULHandoverPreparationTransfer message containing the 1xRTT origination message from the UE and sends the S1AP: UPLINK S1 CDMA2000 TUNNELING message with the CDMA2000 HO Required Indication to the MME.

SRVCC execution • •

The MME responds to the eNB with the S1AP: DOWNLINK S1 CDMA2000 TUNNELING message including the CDMA2000 HO Status information element (IE). The CDMA2000 HO Status IE indicates an HO preparation status as follows: –

Issue: 01D

a successful HO preparation: the eNB forwards the 1x Handoff direction message embedded in the RRC: MobilityFromEUTRACommand message to the UE; as a result, the UE is moved to the 1xRTT area

DN09185982

39


–


a failed HO preparation: the eNB sends the RRC: DLInformationTransfer that indicates the failure to the UE; as a result, the UE is maintained in the EUTRAN area

System impact Interdependencies between features •

•

•

•

•

•

•

•

•

LTE426: System Time Broadcast for SIB8 The LTE738: SRVCC to 1xRTT/CDMA feature reuses the LTE426: System Time Broadcast for SIB8 feature. The eNB broadcasts the CDMA system time in SIB8 if the LTE738: SRVCC to 1xRTT/CDMA feature is enabled, and the time source is available. LTE10: EPS Bearers for Conversational Voice The LTE10: EPS Bearers for Conversational Voice feature is a pre-condition to establish a VoIP bearer. The LTE10: EPS Bearers for Conversational Voice feature must be activated to activate the LTE738: SRVCC to 1xRTT/CDMA feature. LTE7: Support of Multiple EPS Bearers The LTE7: Support of Multiple EPS Bearers feature is a pre-condition to establish a VoIP bearer. The LTE7: Support of Multiple EPS Bearers feature must be activated to activate the LTE738: SRVCC to 1xRTT/CDMA feature. LTE572: IMS Emergency Sessions To support an IMS emergency call over LTE, the LTE572: IMS Emergency Sessions feature needs to be enabled. 1xSRVCC for emergency calls is supported in case of an ongoing emergency bearer using QCI1. LTE490: Subscriber Profile-based Mobility, LTE486: PLMN ID Selected Mobility Profiles The LTE490: Subscriber Profile-based Mobility or LTE486: PLMN ID Selected Mobility Profiles feature might be active parallel to the LTE738: SRVCC to 1xRTT/CDMA feature. Mobility profiles shall not be supported in the LTE738: SRVCC to 1xRTT/CDMA feature. LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB), LTE874: CSFB to CDMA/1xRTT for Dual RX UEs The LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB), LTE874: CSFB to CDMA/1xRTT for Dual RX UEs and LTE738: SRVCC to 1xRTT/CDMA features can be activated independently. The LTE738: SRVCC to 1xRTT/CDMA feature serves the SRVCC-capable UE, while the LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB)/LTE874: CSFB to CDMA/1xRTT for Dual RX UEs feature serves UEs without the SRVCC capability, but with the CSFB capability. LTE761: Advanced Target Cell Selection and Handover Retry for Intra-frequency Handover An HRL might be used to prohibit handover to cdma2000 systems, which needs to be considered by the LTE738: SRVCC to 1xRTT/CDMA feature. LTE116: Cell Bandwidth - 3 MHz, LTE117: Cell Bandwidth - 1.4 MHz When 1.4M/3MHz LTE cell bandwidth is used, the LTE738: SRVCC to 1xRTT/CDMA feature should be deactivated. The following features must be deactivated because only EUTRAN and CDMA target layers are supported for the LTE738: SRVCC to 1xRTT/CDMA feature: – – – –

40

LTE56: Inter-RAT Handover to WCDMA LTE442: Network Assisted Cell Change LTE898: TDD Inter-RAT Handover to TD-SCDMA LTE873: SRVCC to GSM

DN09185982

Issue: 01D


– •


LTE908: ANR Inter-RAT UTRAN - Fully UE-based

LTE64: Service-based Handover Thresholds The LTE738: SRVCC to 1xRTT/CDMA and LTE64: Service-based Handover Thresholds features could exist in parallel. When the LTE64: Service-based Handover Thresholds feature is disabled, the LTE738: SRVCC to 1xRTT/CDMA feature-defined parameters (A1 and A2 related) are used. When the LTE64: Servicebased Handover Thresholds feature is enabled, parameters covered by the LTE64: Service-based Handover Thresholds feature are applicable.

Impact on interfaces For S1 and X2 interfaces, the EUTRA capability is newly supported with feature group indicators (FGIs) bit 11 and 24. 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 Table 9: New counters lists counters introduced with this feature. Table 9


Issue: 01D

Counter name

Measurement

M8016C41

Inter System Handover attempts to 1xRTT with SRVCC

8016 - LTE Inter System Handover (WBTS)

M8016C36

Inter System Handover preparations to 1xRTT with SRVCC


M8016C37

Failed Inter System Handover preparations to 1xRTT with SRVCC due to expiration of guarding timer TUlHoPrepTransfer1xSrvcc


M8016C38

Failed Inter System Handover preparations to 1xRTT with SRVCC due to expiration of guarding timer TC2KRelocPrep1xSrvcc


M8016C42

UE context release due to Inter 8016 - LTE Inter System System Handover to 1xRTT Handover (WBTS) with SRVCC

DN09185982

41


Table 9


New counters (Cont.) Counter ID

Counter name

Measurement

M8016C40

Successful Inter System Handover preparations to 1xRTT with SRVCC


M8016C39

Failed Inter System Handover preparations to 1xRTT with SRVCC due to received HO Failure indication message


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

New parameters

Full name Activate SRVCC to CDMA/1xRTT

Abbreviated name act1xSrvcc

Managed object

Structure

LNBTS

-

CDMA2000 SRVCC to measConfigSrvccRtt 1xRTT measurement configuration

LNHOX

-

Threshold1 CDMA2000-1XRTT for RSRP of serving cell

LNHOX

measConfigSrvccRtt

LNHOX

measConfigSrvccRtt

Time to trigger CDMA2000-1XRTT measurement report

b2TimeToTriggerRttMe LNHOX as

measConfigSrvccRtt

Related hysteresis of CDMA2000-1XRTT B2Th1 and B2Th2

hysB2ThresholdRtt

LNHOX

measConfigSrvccRtt

CDMA2000 1XRTT frequency specific offset

offsetFreqRtt

LNHOX

measConfigSrvccRtt

Interval for periodical CDMA2000-1XRTT meas reporting

reportIntervalRtt

LNHOX

measConfigSrvccRtt

Single radio voice call continuity allowed

srvccAllowed

LNRELX

-

b2Threshold1Rtt

Threshold2 b2Threshold2PstrRtt CDMA2000 for 1XRTT neighbour cell

Table 11: Modified parameters lists parameters modified by this feature.

42

DN09185982

Issue: 01D


Table 11


Modified parameters Pre LTE15A

Full name

Abbreviate d name

LTE15A and beyond

Managed object

Structure

CDMA2000 1xRTT reference cell id

rttPreregRef LNCEL CellId

-

CDMA2000 1xRTT reference cell cell ID

rttPreregCel LNCEL lId

CDMA2000 1xRTT reference cell market ID

Abbreviate d name

Structure

LNCEL

-

rttPreregRef rttCellId CellId

LNCEL

rttRefCellId

rttPreregMa LNCEL rketId

rttPreregRef rttMarketId CellId

LNCEL

rttRefCellId

CDMA2000 1xRTT reference cell sector ID

rttPreregSe ctorId

rttPreregRef rttSectorId CellId

LNCEL

rttRefCellId

CDMA2000 1xRTT reference cell switch number

rttPreregSw LNCEL No

rttPreregRef rttSwNo CellId

LNCEL

rttRefCellId

Threshold 2 config for CDMA2000 HRPD and 1xRTT

LNCEL

-

rttRefCellId

Managed object

-

threshold2C LNCEL 2kConfig

-

Time to a2TimeToTri LNCEL trigger for ggerActHrp A2 to dMeas activate CDMA2000 measureme nt

-

a2TimeToTri LNCEL ggerActC2k Meas

threshold2C 2kConfig

Related hysteresis of RSRP threshold 2 for CDMA2000

hysThreshol LNCEL d2Hrpd

-

hysThreshol LNCEL d2C2k


RSRP threshold 2 for CDMA2000

threshold2H LNCEL rpd

-

threshold2C LNCEL 2k


Table 12: Related existing parameters lists existing parameters related to this feature.

Issue: 01D

DN09185982

43


Table 12


Full name

44


Abbreviated name

Managed object

Structure

CDMA2000 1xRTT CSFB registration parameters

csfbRegParam1xRtt

CDFIM

-

CDMA2000 1xRTT NID roamer registration indicator

foreignNidReg

CDFIM

csfbRegParam1xRtt

CDMA2000 1xRTT SID roamer registration indicator

foreignSidReg

CDFIM

csfbRegParam1xRtt

CDMA2000 1xRTT home registration indicator

homeReg

CDFIM

csfbRegParam1xRtt

CDMA2000 1xRTT multiple NID storage indicator

multiNid

CDFIM

csfbRegParam1xRtt

CDMA2000 1xRTT multiple SID storage indicator

multiSid

CDFIM

csfbRegParam1xRtt

CDMA2000 1xRTT network identification

nid

CDFIM

csfbRegParam1xRtt

CDMA2000 1xRTT parameter-change registration indicator

paramReg

CDFIM

csfbRegParam1xRtt

CDMA2000 1xRTT power-down registration indicator

powerDownReg

CDFIM

csfbRegParam1xRtt

CDMA2000 1xRTT power-up registration indicator

powerUpReg

CDFIM

csfbRegParam1xRtt

CDMA2000 1xRTT registration period

regPeriod

CDFIM

csfbRegParam1xRtt

CDMA2000 1xRTT registration zone

regZone

CDFIM

csfbRegParam1xRtt

CDMA2000 1xRTT system identification

sid

CDFIM

csfbRegParam1xRtt

CDMA2000 1xRTT number of registration zones

totalZone

CDFIM

csfbRegParam1xRtt

CDMA2000 1xRTT zone timer length

zoneTimer

CDFIM

csfbRegParam1xRtt

CDMA2000 HRPD neighbor cell list

hrpdNCList

CDFIM

-

CDMA2000 HRPD frequency

hrpdArfcn

CDFIM

hrpdNCList

CDMA2000 HRPD band class

hrpdBdClNcl

CDFIM

hrpdNCList

CDMA2000 HRPD physical cell identity

hrpdCellId

CDFIM

hrpdNCList

DN09185982

Issue: 01D


Table 12


Full name

Issue: 01D


Abbreviated name

Managed object

Structure

CDMA2000 HRPD NCL extension selector

hrpdExSel

CDFIM

hrpdNCList

CDMA2000 1xRTT neighbor cell list

rttNCList

CDFIM

-

CDMA2000 1xRTT frequency

rttArfcn

CDFIM

rttNCList

CDMA2000 1xRTT band class (NCL)

rttBdClNcl

CDFIM

rttNCList

CDMA2000 1xRTT physical cell identity

rttCellId

CDFIM

rttNCList

CDMA2000 1xRTT NCL extension selector

rttExSel

CDFIM

rttNCList

Neighbor 1x carrier frequency

arfcn

LNADJX

-

Neighbor 1x band class

bandClass

LNADJX

-

Activate 1xCSFB

act1xCsfb

LNBTS

-

Activate handover from LTE to WCDMA

actHOtoWcdma

LNBTS

-

Activate UE-based ANR for UTRAN

actUeBasedAnrUtran

LNBTS

-

Activate eNACC to GSM

acteNACCtoGSM

LNBTS

-

Time to trigger for A1 to deactivate inter measurement

a1TimeToTriggerDeact LNCEL InterMeas

-

CDMA2000 timers

c2KTimers

LNCEL

-

CDMA2000 1xRTT measurement report timer

tC2KMeasReport

LNCEL

c2KTimers

CDMA2000 relocation preparation timer

tC2KRelocPrep

LNCEL

c2KTimers

CDMA2000 relocation execution timer

tC2kRelocExec

LNCEL

c2KTimers

UL Handover preparation transfer timer

tULHOPrepTransfer

LNCEL

c2KTimers

Random challenge value

rand

LNCEL

-

CDMA2000 1xRTT cell ID info

rttCellIdInfo

LNCEL

-

CDMA2000 1xRTT CSFB type

rttCsfbType

LNCEL

-

DN09185982

45


Table 12


Full name

46


Abbreviated name

Managed object

Structure

System information scheduling list

sibSchedulingList

LNCEL

-

Periodicity

siMessagePeriodicity

LNCEL

sibSchedulingList

Repetition

siMessageRepetition

LNCEL

sibSchedulingList

SIB type

siMessageSibType

LNCEL

sibSchedulingList

Threshold th2a for RSRP

threshold2a

LNCEL

-

Threshold th4 for RSRP

threshold4

LNCEL

-

Threshold1 CDMA2000-HRPD for RSRP of serving Cell

b2Threshold1Hrpd

LNHOH

-

CDMA2000 1XRTT carrier frequency

rttCarrierFreq

LNHOX

-

CDMA2000 1XRTT ARFCN

rttArfcn

LNHOX

rttCarrierFreq

CDMA2000 1XRTT band class

rttBandClass

LNHOX

rttCarrierFreq

Neighbor 1x carrier frequency

arfcn

LNRELX

-

Neighbor 1x band class

bandClass

LNRELX

-

Local time offset

ltmOff

XPARAM

-

CDMA2000 1xRTT mobility parameters identifier

xparamId

XPARAM

-

CDMA2000 1xRTT auth mode indicator

auth

XPARAM

-

CDMA2000 1xRTT auth mode indicator included

authIncluded

XPARAM

-

CDMA2000 1xRTT band class

bandClass

XPARAM

-

Day light savings time indicator

dayLt

XPARAM

-

Include day light savings time indicator

dayLtIncluded

XPARAM

-

FPC FCH INIT SETPT fpcFchInitSetptRC11 for RC11

XPARAM

-


XPARAM

-


XPARAM

-


XPARAM

-

DN09185982

Issue: 01D


Table 12



Full name

Abbreviated name

Managed object

Structure

FPC FCH INITSETPT for RC5

fpcFchInitSetptRC5

XPARAM

-

GCSNAL2Ack timer indicator

gcsnaL2AckTimer

XPARAM

-

GCSNA sequence context timer indicator

gcsnaSequenceConte xtTimer

XPARAM

-

CDMA2000 1xRTT home registration included

homeRegIncluded

XPARAM

-

IMSI 11th and 12th digit

imsi11and12

XPARAM

-

IMSI T supported

imsiTSupported

XPARAM

-

Leap second

lpSec

XPARAM

-

Leap seconds included

lpSecIncluded

XPARAM

-

Local time offset included

ltmOffIncluded

XPARAM

-

CDMA2000 1xRTT max number of alt SO

maxNumAltSo

XPARAM

-

Mobile country code

mcc

XPARAM

-

CDMA2000 1xRTT minimum protocol revision

minPRev

XPARAM

-

1x protocol revision

pRev

XPARAM

-

Pilot increment

pilotInc

XPARAM

-

Pilot increment included

pilotIncIncluded

XPARAM

-

Preferred mobile station identifier type

prefMSIDType

XPARAM

-



ASW

License control in network element SW asset monitoring


3.2.2 Activating and configuring LTE738: SRVCC to 1xRTT/CDMA Before you start Table 14: Parameters used for activating and configuring LTE738: SRVCC to 1xRTT/CDMA lists the parameters used for activating and configuring the LTE738: SRVCC to 1xRTT/CDMA feature.

Issue: 01D

DN09185982

47


Table 14


Parameters used for activating and configuring LTE738: SRVCC to 1xRTT/CDMA Parameter

48

Purpose


Activate SRVCC to CDMA/1xRTT (act1xSrvcc)

activation flag

no

CDMA2000 SRVCC to 1xRTT measurement configuration (measConfigSrvccRtt) parameter structure


no

Single radio voice call continuity allowed (srvccAllowed), LNRELX


no

CDMA2000 1XRTT carrier frequency (rttCarrierFreq)

mandatory configuration

no

Neighbor 1x carrier frequency (arfcn)


no

Neighbor 1x band class (bandClass)


no

CDMA2000 timers (c2KTimers) parameter structure


no

Threshold 2 config for CDMA2000 HRPD and 1xRTT (threshold2C2kConfig) parameter structure


no

Random challenge value (rand)


no

CDMA2000 1xRTT cell ID info (rttCellIdInfo)


no

CDMA2000 1xRTT reference cell id (rttRefCellId) parameter structure


no

Time to trigger for A1 to deactivate optional configuration inter measurement (a1TimeToTriggerDeact InterMeas)

no

System information scheduling list (sibSchedulingList)


no

Threshold th2a for RSRP (threshold2a)


no

Threshold th4 for RSRP (threshold4)


no

Local time offset (ltmOff)


no

CDMA2000 1xRTT CSFB registration parameters (csfbRegParam1xRtt) parameter structure


no

Neighbor 1x carrier frequency (arfcn)


no

Neighbor 1x band class (bandClass)


no

DN09185982

Issue: 01D



The following features need to be activated before the activation of the LTE738: SRVCC to 1xRTT/CDMA feature: • •

LTE10: EPS Bearers for Conversational Voice LTE7: Support of Multiple EPS Bearers

The following features need to be deactivated before the activation of the LTE738: SRVCC to 1xRTT/CDMA feature: • • • •

LTE56: Inter-RAT Handover to WCDMA LTE442: Network Assisted Cell Change to GSM LTE873: SRVCC to GSM LTE908: ANR Inter-RAT UTRAN - Fully UE-based

Procedure 1


2

Activate the LTE738: SRVCC to 1xRTT/CDMA feature. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate SRVCC to CDMA/1xRTT (act1xSrvcc) parameter's value to true.

Configure the LNHOX parameters. a) b) c) d)

Expand the LNBTS object. Expand the LNCEL object. Right-click the LNCEL object and select the New LNHOX object. Set the CDMA2000 1xRTT neighbor cell handover identifier (lnhoxId) parameter's value. e) Right-click the LNHOX object and select the New CDMA2000 SRVCC to 1xRTT measurement configuration parameter structure. f) For the CDMA2000 SRVCC to 1xRTT measurement configuration parameter structure, set the parameter values. g) For the CDMA2000 1XRTT carrier frequency parameter structure, set the CDMA2000 1XRTT ARFCN (rttArfcn) and CDMA2000 1XRTT band class(rttBandClass) parameters' values.

4

Configure the LNRELX and LNADJX parameters (optional). a) Expand the LNBTS object.

Issue: 01D

DN09185982

49


b) c) d) e)

5


Expand the LNCEL object. Right-click the LNCEL object and select the New LNRELX object. For the LNRELX object, set the parameter values. For the 1x neighbor cells supporting 1xSRVCC, set the srvccAllowed LNRELX parameter's value to true.

Configure the LNCEL parameter structures. a) Expand the LNBTS object. b) Right-click the LNCEL object and select the New ► New CDMA2000 timers parameter structure. c) Right-click the LNCEL object and select the New ► CDMA2000 1xRTT reference cell id parameter structure. d) Right-click the LNCEL object and select the New ► Threshold 2 config for CDMA2000 HRPD and 1xRTT parameter structure. e) For the created parameter structures, set the parameter values.

6

Configure the Random challenge value and CDMA2000 1xRTT cell ID info LNCEL parameters. a) Expand the LNBTS object. b) Select the LNCEL object. c) Set the Random challenge value (rand) and CDMA2000 1xRTT cell ID info (rttCellIdInfo) parameters' values.

7

Configure the other LNCEL parameters (optional). a) Expand the LNBTS object. b) Select the LNCEL object. c) Set the parameter values.

8

Configure the XPARAM parameters. a) b) c) d)

9

Expand the LNBTS object. Expand the LNCEL object. Right-click the LNCEL object and select the New XPARAM object. For the XPARAM object, set all the parameters' values.

Configure the SIB8. a) Expand the LNBTS object. b) Expand the LNCEL object.

50

DN09185982

Issue: 01D



c) For the System information scheduling list (sibSchedulingList) parameter structure, add SIB8.

10 Configure the CDMA2000 1xRTT CSFB registration parameters parameters' structure. a) Expand the LNBTS object. b) Right-click the LNCEL object and select the New CDFIM object. c) Right-click the CDFIM object and select the New CDMA2000 1xRTT CSFB registration parameters. d) For the selected structure, set the parameter values.

11 Configure the Network synchronization mode BTSSCL parameter. a) Right-click the MRBTS object. b) Select the New ► BTSSCL object. c) Set the Network synchronization mode (btsSyncMode) parameter's value to equal the PhaseSync.

12 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.

Expected outcome The LTE738: SRVCC to 1xRTT/CDMA feature is activated.

3.2.3 Deactivating LTE738: SRVCC to 1xRTT/CDMA Before you start The Activate SRVCC to CDMA/1xRTT (act1xSrvcc) parameter is used for deactivation. Modification of this parameter requires neither eNB restart nor cell locking. Procedure 1


2

Deactivate the LTE738: SRVCC to 1xRTT/CDMA feature. a) Go to the Radio Network Configuration page.

Issue: 01D

DN09185982

51



b) Expand the MRBTS object. c) Select the LNBTS object. d) Set the Activate SRVCC to CDMA/1xRTT (act1xSrvcc) parameter's value to false.

3

Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.

Expected outcome The LTE738: SRVCC to 1xRTT/CDMA feature is deactivated.

3.3 LTE825: Uplink Outer Region Scheduling 3.3.1 Description of LTE825: Uplink Outer Region Scheduling Introduction to the feature The LTE825: Uplink Outer Region Scheduling feature increases the number of physical resource blocks (PRBs) available for data allocation in uplink (UL). For this purpose, this feature allows using the blanked outer region for the physical uplink shared channel (PUSCH). In addition, it enables the scheduling of the physical random access channel (PRACH) in the outer region. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides: • • •

PRBs in one of the blanked physical uplink control channel (PUCCH) regions for PUSCH and PRACH more efficient exploitation of the available UL spectrum the RAN configuration flexibility and simplicity


52



DN09185982


Flexi Zone Access Point FL16

Issue: 01D


Table 15

Hardware and software requirements (Cont.)



OMS -

UE 3GPP R8 mandatory

NetAct NetAct 15.5

MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview The implementation of the LTE825: Uplink Outer Region Scheduling feature is inseparably connected with the LTE786: Flexible UL Bandwidth feature. The latter aims at reducing the UL bandwidth below the nominal system bandwidth. The bandwidth is reduced symmetrically on both edges of the UL spectrum by leaving the outmost PRBs unused. In order to improve the feature's functionality (for example, to reduce the UL bandwidth in an asymmetrical way or to enable an automatic SRS configuration), the LTE825: Uplink Outer Region Scheduling feature enhances its previous counterpart; therefore, it can be perceived as an addition to the already existing one. The LTE825: Uplink Outer Region Scheduling feature is supported by >3MHz system bandwidths. It enables the eNB to allocate the PUSCH and PRACH resources in one blanked PUCCH edge. The set of PUSCH PRBs in the blanked PUCCH edge is called an outer PUSCH region. The minimum recommended outer region's size is three PRBs. The PRACH can be placed in the outer PUSCH region when six or more consecutive PRBs are available. It ensures that the RAN configuration is more flexibile. In addition, this feature enables the eNB to utilize additional UL resources for the PUSCH scheduling (see Figure 2: The comparison of LTE786: Flexible UL Bandwidth and LTE825: UL Outer Region Scheduling features). This feature provides a method for setting up the PUSCH and PRACH in the blanked non-disturbed outer UL spectrum, and allows the allocation of unused PRBs for the outer region scheduling. An O&M parameter defines which one of the outer regions is permitted for PUSCH scheduling and which one of the two blanked PUCCH regions is added. Figure 2

Issue: 01D

The comparison of LTE786: Flexible UL Bandwidth and LTE825: UL Outer Region Scheduling features

DN09185982

53


Nominalsystem bandwith


LTE786:Flexible UL Bandwidth

LTE825:UL Outer RegionScheduling

blanked

PUSCH (outerregion)

PUCCH

PUCCH

PUSCH and PRACH

PUSCH (innerregion)

PUCCH

PUCCH

blanked

blanked

PUCCH

PUSCH and PRACH

PUCCH

• toavoidinterference • bothbandedgesblanked

PRACH (eitheror)

• activationinoneouterregion • asymmetricalbandwidth reductionpossible

Depending on the number of PRBs which are assigned to the inner PUSCH region, the eNB selects a proper sounding reference signal (SRS) configuration. The SRS configuration is selected out of a set of predefined SRS configurations. The selected SRS configuration is one with the largest SRS bandwidth that does not overlap the outer PUSCH region or the blanked PUCCH edges. Instead, it can overlap the used PUCCH PRBs. This method simplifies the RAN configuration. For the configuration of the outer scheduling region, the same RRM algorithms for power control (OLPC, CLPC, or IawPC), link adaptation (slowAMC, eULA, or fULA – fULA without the support of SRS in the outer region), and the same scheduling algorithms (CUS, IAS, or CAS – CAS without the support of SRS in the outer region) are applied. Automatic SRS configuration In the LTE825: UL Outer Region Scheduling feature, the sounding configuration is chosen automatically, depending on the number of PUSCH PRBs assigned to the inner scheduling region. The eNB selects the SRS configuration from a set of predefined configurations in such a way that the sounding in the blanked PUCCH, or rather in the outer PUSCH region, is prevented. It also covers the inner PUSCH region as much as possible. The coexistence of sounding resources and PUCCH is allowed. The automatic SRS configuration is done even if the LTE786: Flexible UL Bandwidth and LTE825: UL Outer Region Scheduling features are deactivated. System impact Interdependencies between features There are interdependencies between the following features: •

54

LTE786: Flexible UL Bandwidth The size of the blanked outer region which can be utilized for PUSCH and PRACH is defined by the LTE786: Flexible UL Bandwidth feature. The size of the configured outer PUSCH region is blankedPucch/2.

DN09185982

Issue: 01D



Impact on interfaces The LTE825: Uplink Outer Region Scheduling feature impacts the Uu interface in such a way that a second PUSCH region is additionally assigned to the already existing PUSCH region around the central frequency. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature impacts system performance and capacity as follows: • •

g

The RAN-level system capacity increases in direct proportion to the number of PUSCH PRBs which are assigned to the UL outer region scheduling area. The average UL cell throughput increases (compared to the LTE786: Flexible UL Bandwidth feature used alone for the cell) by adding the PRBs in the outer PUSCH region. Note: For a 20-Mhz bandwith blanked with two regions of 5 Mhz, the average throughput and capacity approximate those of a 10-Mhz cell (this is without the LTE825: Uplink Outer Region Scheduling feature). With this feature, it is possible to gain one of the 5-Mhz blanked regions and, as a result, obtain a roughly 15-Mhz cell.

Management data Alarms There are no alarms related to this feature. Measurements and counters Table 16: Modified counters lists counters modified by this feature. Table 16

Modified counters Counter ID

Issue: 01D

Counter name

Measurement

M8011C50

PRB used PUSCH

LTE Cell Resource

M8011C22

UL PRB utilization per TTI Min

LTE Cell Resource

M8011C23

UL PRB utilization per TTI Max LTE Cell Resource

M8011C24

UL PRB utilization per TTI Mean

LTE Cell Resource

M8011C12

UL PRB utilization per TTI Level 1

LTE Cell Resource

M8011C13


LTE Cell Resource

M8011C14


LTE Cell Resource

M8011C15


LTE Cell Resource

M8011C16


LTE Cell Resource

DN09185982

55


Table 16

Modified counters (Cont.) Counter ID

56


Counter name

Measurement

M8011C17


LTE Cell Resource

M8011C18


LTE Cell Resource

M8011C19


LTE Cell Resource

M8011C20


LTE Cell Resource

M8011C21


LTE Cell Resource

M8005C231

Minimum of cell-wide RSSI on PUSCH

LTE Power and Quality UL

M8005C232

Maximum of cell-wide RSSI on LTE Power and Quality UL PUSCH

M8005C233

Mean of cell-wide RSSI on PUSCH


M8005C234

Cell-wide RSSI on PUSCH level 1


M8005C235



M8005C236



M8005C237



M8005C238



M8005C239



M8005C240



M8005C241



M8005C242



M8005C243



M8005C244



M8005C245



M8005C246



M8005C247



DN09185982

Issue: 01D


Table 16


Issue: 01D


Counter name

Measurement

M8005C248



M8005C249



M8005C250



M8005C251



M8005C252



M8005C253



M8005C254



M8005C255



M8005C281

Minimum of cell-wide SINR on PUSCH


M8005C282

Maximum of cell-wide SINR on LTE Power and Quality UL PUSCH

M8005C283

Mean of cell-wide SINR on PUSCH


M8005C284

Cell-wide SINR on PUSCH level 1


M8005C285



M8005C286



M8005C287



M8005C288



M8005C289



M8005C290



M8005C291



M8005C292



M8005C293



M8005C294



DN09185982

57


Table 16



Counter name

Measurement

M8005C295



M8005C296



M8005C297



M8005C298



M8005C299



M8005C300



M8005C301



M8005C302



M8005C303



M8005C304



M8005C305



M8011C47

PRB used UL total

LTE Cell Resource

M8011C49

PRB used PUCCH

LTE Cell Resource

M8011C50

PRB used PUSCH

LTE Cell Resource

M8011C51

PRB used DL total

LTE Cell Resource

M8011C54

PRB used PDSCH

LTE Cell Resource

Key performance indicators There are no key performance indicators related to this feature. Parameters Table 17: New parameters lists new parameters introduced by this feature. Table 17

New parameters

Full name

Abbreviated name

Managed object

Target UL outer scheduling region

selectOuterPuschRegi LNCEL on

SRS feature activation/deactivation

srsActivation

LNCEL


58

DN09185982

Issue: 01D


Table 18



Full name

Abbreviated name

Managed object

Activate PUSCH masking

actPuschMask

LNCEL

Activate uplink link adaptation

actUlLnkAdp

LNCEL

Blanked PUCCH resources

blankedPucch

LNCEL

PRACH frequency offset

prachFreqOff

LNCEL

Power offset for SRS transmission power calculation

srsPwrOffset

LNCEL

Uplink channel bandwidth

ulChBw

LNCEL

Scheduling method of the UL scheduler

ulsSchedMethod

LNCEL



ASW



3.3.2 Activating and configuring LTE825: Uplink Outer Region Scheduling Before you start Table 20: Parameters used for activating and configuring LTE825: Uplink Outer Region Scheduling lists parameters used for the activation and configuration of the LTE825: Uplink Outer Region Scheduling feature. Table 20

Parameters used for activating and configuring LTE825: Uplink Outer Region Scheduling Parameter

Purpose


Target UL outer scheduling region (selectOuterPuschRegi on)

activation flag

restart

Blanked PUCCH resources (blankedPucch)


object locking

PRACH frequency offset (prachFreqOff)


restart

PUCCH bandwidth for CQI (nCqiRb)


object locking

The LTE786: Flexible UL Bandwidth feature needs to be activated and configured before activating the LTE825: Uplink Outer Region Scheduling feature.

Issue: 01D

DN09185982

59



Procedure 1


2

Configure the PUCCH bandwidth for CQI (nCqiRb) parameter. a) b) c) d) e)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Select the LNCEL object. Configure the PUCCH bandwidth for CQI (nCqiRb) parameter.

Configure the Blanked PUCCH resources (blankedPucch) parameter. a) Expand the LNCEL object. b) Set the Blanked PUCCH resources (blankedPucch) parameter to the following values: • •

g 4

12 or higher for PRACH scheduling in the outer scheduling region 6 or higher for PUSCH scheduling in the outer scheduling region Note: PUSCH scheduling is also permitted in case Blanked PUCCH resources (blankedPucch) = 12

Activate the LTE825: Uplink Outer Region Scheduling feature. a) Select the LNCEL object. b) Set the Target UL outer scheduling region (selectOuterPuschRegion) parameter's value to UpperEdge or LowerEdge.

g

Note: Target UL outer scheduling region (selectOuterPuschRegion) can only be set to UpperEdge or LowerEdge if Uplink channel bandwith (ulChBw) is higher or equal to 5 MHz.

5

Set the PRACH frequency offset (prachFreqOff) parameter's value (if the LNCEL Target UL outer scheduling region (selectOuterPuschRegion) parameter is set to LowerEdge and the LNCEL Blanked PUCCH resources (blankedPucch) parameter is higher or equal 12). a) Select the LNCEL object.

60

DN09185982

Issue: 01D



b) Set the PRACH frequency offset (prachFreqOff) parameter's value.

g

Note: PRACH has to be placed either in the outer PUSCH region or in the inner region at a place where the calculation rule is specified. The permitted range for PRACH frequency offset (prachFreqOff) is produced by a calculation formula: • •

from the lower limit: 0 to the upper limit: roundup (Blanked PUCCH resources (blankedPucch) / 2 - 6, and from the lower limit: roundup (LNCEL Maximum PUCCH resource size (MaxPucchResourceSize) + (blankedPucch) / 2) to the upper limit: LNCEL Uplink channel bandwith (ulChBw) (in PRBs) - 6 - roundup (MaxPucchResourceSize + blankedPucch) / 2)

The above parameters must be configured so that the lower limit is always below or equal to the upper limit of the permitted range. This is not enforced by the SW but needs to be followed during the configuration.

g

Note: LNCEL Maximum PUCCH resource size (MaxPucchResourceSize) is a calculated value that is computed by means of other O&M parameters. MaxPucchResourceSize is utilized to determine the correct offset allocation of the PRACH resources and to verify that the maximal allowed number of PUCCH resources per BW is not exceeded. MaxPucchResourceSize is produced by a calculation formula: •

MaxPucchResourceSize = nCqiRb + roundup {[((rounddown (((maxNrSymPdcch*12 - X)*dlChBw - roundup (phichRes*(dlChBw / 8))*12 16) / 36)) + n1PucchAn - pucchNAnCs*3 / deltaPucchShift) *deltaPucchShift] / (3*12)} + roundup (pucchNAnCs / 8) – blankedPucch, where: – –

6

X = 4, when maxNrSymPdcch = 1 or dlMimoMode set to SingleTX, TXDiv, Dynamic Open Loop MIMO or Closed Loop Mimo X = 8, when maxNrSymPdcch > 1 and dlMimoMode set to 4-way TXDiv or Closed Loop MIMO (4x2)

Set the PRACH frequency offset (prachFreqOff) parameter's value (if the LNCEL Target UL outer scheduling region (selectOuterPuschRegion) parameter is set to UpperEdge and the LNCEL Blanked PUCCH resources (blankedPucch) parameter is higher or equal 12). a) Select the LNCEL object. b) Set the PRACH frequency offset (prachFreqOff) parameter's value.

Issue: 01D

DN09185982

61


g


Note: PRACH has to be placed either in outer PUSCH region or in the inner region at a place where the calculation rule is specified. The permitted range for LNCEL: PRACH frequency offset (prachFreqOff) is produced by a calculation formula: •

•

from the lower limit: roundup (LNCEL: Maximum PUCCH resource size (MaxPucchResourceSize) + LNCEL: Blanked PUCCH resources (blankedPucch) / 2) to the upper limit: LNCEL: Uplink channel bandwith (ulChBw) in PRBs - 6 - roundup (MaxPucchResourceSize + blankedPucch) / 2, and from the lower limit: LNCEL: Uplink channel bandwith (ulChBw) in PRBs roundup (blankedPuccch/2) to the upper limit: ulChBw (in PRBs) - 6


g

Note: LNCEL Maximum PUCCH resource size (MaxPucchResourceSize) is a calculated value that is computed by means of other O&M parameters. MaxPucchResourceSize is utilized to determine the correct offset allocation of the PRACH resources and to verify that the maximal allowed number of PUCCH resources per BW is not exceeded. MaxPucchResourceSize is produced by a calculation formula: •

MaxPucchResourceSize = nCqiRb + roundup {[((rounddown (((maxNrSymPdcch*12 – X)*dlChBw - roundup (phichRes*(dlChBw / 8))*12 16) / 36)) + n1PucchAn - pucchNAnCs*3 / deltaPucchShift) *deltaPucchShift] / (3*12)} + roundup (pucchNAnCs / 8) - blankedPucch, where: – –

7

X = 4, when maxNrSymPdcch = 1 or dlMimoMode set to SingleTX, TXDiv, Dynamic Open Loop MIMO or Closed Loop Mimo X = 8, when maxNrSymPdcch > 1 and dlMimoMode set to 4-way TXDiv or Closed Loop MIMO (4x2)


Expected outcome The LTE825: Uplink Outer Region Scheduling feature is activated; PUSCH and PRACH scheduling in the outer scheduling area is possible.

3.3.3 Deactivating LTE825: Uplink Outer Region Scheduling Before you start The Target UL outer scheduling region (selectOuterPuschRegion) parameter is used for deactivation. Modification of this parameter requires an eNB restart.

62

DN09185982

Issue: 01D



Procedure 1


2

Deactivate the Target UL outer scheduling region (selectOuterPuschRegion) parameter. a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNCEL object. Set the Target UL outer scheduling region (selectOuterPuschRegion) parameter's value to none.

With the deactivation of the LTE825: Uplink Outer Region Scheduling feature, the outer PUSCH region no longer exists; PRACH is then set up in an inner PUSCH region. In that case PRACH frequency offset (prachFreqOff) parameter needs to be reconfigured accordingly.

g

Note: If selectOuterPuschRegion is configured to None or blankedPucch is less than 12, then the permitted range for prachFreqOff is produced by a calculation formula: •

from the lower limit: roundup LNCEL: Maximum PUCCH resource size (MaxPucchResourceSize)+LNCEL: Blanked PUCCH resources (blankedPucch) / 2) to the upper limit: LNCEL: Uplink channel bandwith (ulChBw) (in PRBs) - 6 - roundup LNCEL: Maximum PUCCH resource size (MaxPucchResourceSize) + LNCEL: Blanked PUCCH resources (blankedPucch) / 2)


Expected outcome The LTE825: Uplink Outer Region Scheduling feature is deactivated.

3.4 LTE951: Enhanced Cell ID Location Service 3.4.1 Description of LTE951: Enhanced Cell ID Location Service Introduction to the feature The LTE951: Enhanced Cell ID Location Service feature improves location reporting by introducing enhanced cell ID reporting (E-CID) to the E-Serving Mobile Location Center (E-SMLC). Benefits

Issue: 01D

DN09185982

63



End-user benefits This feature: • •

enables determining UE position in case of emergency calls enables using applications requesting UE positioning (for example maps, etc.)

Operator benefits This feature allows the operator to turn the location services in a cell on and off. Requirements Hardware and software requirements Table 21 System release FDD-LTE 15A



g


OMS -

FL15A

UE 3GPP R9

Flexi Zone Micro BTS

FL16

NetAct NetAct 15.5


MME -

SAE GW -

Note: For Timing advance (TA) type1, a UE should support the UE Rx-Tx time difference measurement capability. Additional hardware requirements Providing the operator's network contains a mobility management entity (MME) and ESMLC provided by other vendors, it is assumed that these network elements support the LPPa messaging for E-CID before the LTE951: Enhanced Cell ID Location Service feature is deployed. It is also assumed that any timers on the MME and E-SMLC (that are preventing message response timeouts) can be adjusted as they are needed to ensure successful inter-operability with Nokiaan eNB. Functional description Functional overview The LTE951: Enhanced Cell ID Location Service feature introduces enhanced cell ID (ECID) location services. The location service is performed in two steps: 1. The UE is positioned based on its serving cell's ID. 2. The UE is positioned more accurately inside a single cell, using one of the following four methods: • • •

64

Timing advance type 1 Timing advance type 2 Intra-frequency Reference Signal Received Power (RSRP) and/or Reference Signal Received Quality (RSRQ)

DN09185982

Issue: 01D



In a location measurement procedure, information about the position of a UE is transmitted from an eNodeB to E-SMLC in the LTE Positioning Protocol A (LPPa) LPPA: E-CID MEASUREMENT INITIATION RESPONSE message, which is encapsulated within the S1AP: UPLINK UE ASSOCIATED LPPA TRANSPORT message. Only on-demand measurements are supported by an eNB. The eNB can perform multiple measurements simultaneously. Providing a measurement request is received by an eNB while performing a handover of a UE, the failure response is sent back to the E-SMLC. When employing the LTE951: Enhanced Cell ID Location Service feature in cells with spatially separated antennas (for example a super cell), the measurements provided by LTE951: Enhanced Cell ID Location Service cannot be referenced to a single antenna as they do not have a well-defined reference point. Whether to use the LTE951: Enhanced Cell ID Location Service feature with separated antennas and an unclear reference point is left for the operator to decide. When deploying the feature, there are two scenarios for an operator to consider: •

•

not to configure an E-UTRAN access point information in the eNodeB. The eNodeB will then not report the E-UTRAN access point information to the E-SMLC, and it is assumed that the E-SMLC will cope with this (the E-UTRAN access point information element (IE) is optional in the E-CID measurement result). define the E-UTRAN access point position as a geographical mean value of the antenna positions (logical antenna position). Use the uncertaintyAltitude, uncertaintySemiMajor, and uncertaintySemiMinor attributes of the eutranAccessPointPosition configuration parameter to express the geographical inaccuracy of this logical antenna position.

Measurement types Timing advance type 2 (TA type 2) This measurement is performed by an eNB and describes the time difference between the reception of an uplink radio frame #i containing PRACH and the transmision a of downlink radio frame #i. For details, see 3GPP TS36.214. The reference point used by an eNB to perform the measurements is the antenna connector. Timing advance type 1 (TA type 1) This approach measures the following two timing differences: •

•

the time difference between the reception of a downlink radio frame #i and the transmission of a corresponding uplink radio frame #i, measured by the UE (UE RxTx time difference) the time difference between the reception of an uplink radio frame #i and the transmission of a downlink radio frame #i at the eNB (eNB Rx-Tx time difference)

The measurement is conducted only after an E-SMLC request. After receiving such a request, an eNB instructs a UE to perform the UE Rx-Tx measurements. After receiving a UE Rx-Tx measurement from the UE, the eNB computes the Timing advance type 1 and sends it to the E-SMLC. Before performing the Timing advance type 1 procedure, the E-SMLC verifies the UE's capability to perform measurements via an LPP protocol.

Issue: 01D

DN09185982

65



The reference point used by an eNB to perform the measurements is the antenna connector. Intra-frequency Reference Signal Received Power (RSRP) and/or Reference Signal Received Quality (RSRQ) These measurements are performed by a UE and reported to an eNB. When a request for the RSRP, or RSRQ, or both of them arrives at an eNB, the eNB initiates an intrafrequency measurement configuration at the UE with a reportStrongestCells purpose. The exact type of this measurement is set by the value of triggerQuantity. Subject to a desired measurement, its value is set either to RSRP (in case the RSRP or both measurements are requested), or RSRQ (in case only this measurement is needed). The UE sends a measurement report to the eNodeB, which in turn sends the RSRP and/or RSRQ measurements to the E-SMLC, which calculates the UE's position. System impact Interdependencies between features The following features are interrelated with the LTE951: Enhanced Cell ID Location Service feature: •

•

• •

•

LTE433: Cell Trace The feature enables operators to simultaneously trace all UEs that are in an RRC_CONNECTED state in a target cell. LTE644: Configurable Cell Trace Content The feature allows operators to select a message type, based on which the UEs that are in an RRC_CONNECTED state are filtered and traced in a target cell. LTE163: Subscriber and Equipment Trace The feature enables operators to trace a specific IMSI or IMEI. LTE782: ANR Fully UE-based Providing the LTE782: ANR Fully UE-based and LTE951: Enhanced Cell ID Location Service features are enabled, the location service measurement request takes higher priority than an ANR measurement. LTE1501: Measurement Report (MR) Addition to Cell Trace If the LTE1501: Measurement Report (MR) Addition to Cell Trace and LTE951: Enhanced Cell ID Location Service features are enabled, the location service measurement request takes higher priority over the measurement requested by the LTE1501: Measurement Report (MR) Addition to Cell Trace feature.

Impact on interfaces The LTE951: Enhanced Cell ID Location Service feature adds support to the E-CID measurement initiation procedure. This procedure utilizes the UL/DL LPPa messages to convey the E-CID measurement messages between an eNB and E-SMLC. This feature impacts the following interfaces: •

The following new messages are added to an S1AP interface for LPPa PDU transport: – –

•

66

S1AP: DOWNLINK UE ASSOCIATED LPPA TRANSPORT S1AP: UPLINK UE ASSOCIATED LPPA TRANSPORT

The following new messages are supported for an E-CID measurement:

DN09185982

Issue: 01D


– – – –


LPPa: E-CID MEASUREMENT INITIATION REQUEST LPPa: E-CID MEASUREMENT INITIATION RESPONSE LPPa: E-CID MEASUREMENT INITIATION FAILURE LPPa: ERROR INDICATION

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. BTS faults and reported alarms Measurements and counters Table 22: New counters lists counters introduced with this feature. Table 22


Counter name

Measurement

M8000C43

Number of downlink UE LTE S1AP associated LPPa transport messages with E-CID measurement initiation request per eNB

M8000C44

Number of uplink UE associated LPPa transport messages with E-CID measurement initiation response per eNB

LTE S1AP

M8000C45

Number of uplink UE associated LPPa transport messages with E-CID measurement initiation response with cause "Requested Item not Supported" per eNB

LTE S1AP

M8000C46

Number of uplink UE associated LPPa transport messages with E-CID measurement initiation response with cause "Requested Item Temporarily not Available" per eNB

LTE S1AP

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

Issue: 01D

DN09185982

67



Parameters Table 23: New parameters lists new parameters introduced by this feature. Table 23

New parameters

Full name

Abbreviated name

Managed object

Structure

Activate LPPa enhanced cell ID location service

actLPPaEcid

LNBTS

-

Periodical measurements for location services

perMeasLocServ

LNCEL

-

Report interval periodical meas for location

reportIntervalPerLoc

LNCEL

perMeasLocServ

Report amount periodical meas for location

reportAmountPerLoc

LNCEL

perMeasLocServ

Overall supervision timer for ECID measurements

ecidMeasSupervisionT LNCEL imer

-


Related existing parameters Full name

Abbreviated name

Managed object

E-UTRAN access point position

eutranAccessPointPosition

LNCEL

Altitude

altitude

LNCEL

Confidence

confidence

LNCEL

Degrees of latitude

degreesOfLatitude

LNCEL

Degrees of longitude

degreesOfLongitude

LNCEL

Direction of altitude

directionOfAltitude

LNCEL

Latitude sign

latitudeSign

LNCEL

Orientation of major axis

orientationOfMajorAxis

LNCEL

Uncertainty altitude

uncertaintyAltitude

LNCEL

Uncertainty semi-major

uncertaintySemiMajor

LNCEL

Uncertainty semi-minor

uncertaintySemiMinor

LNCEL

Sales information Table 5: Sales information presents the sales information about this feature. Table 25


ASW

68


DN09185982


Issue: 01D



3.4.2 Activating and configuring LTE951: Enhanced Cell ID Location Service Before you start Table 6 presents the parameters used for activating and configuring the LTE951: Enhanced Cell ID Location Service feature. Table 26

Parameters used for activating and configuring LTE951: Enhanced Cell ID Location Service Parameter

Issue: 01D

Purpose


Activate LPPa enhanced cell ID location service (actLPPaEcid)

activation flag

no

E-UTRAN access point position (eutranAccessPointPositio n)

mandatory in case geographical position of the transmit antenna needs to be supported

no

Altitude (altitude)

Mandatory in case the Eno UTRAN access point position (eutranAccessPointPos ition) structure is configured

Confidence (confidence)


Degrees of latitude (degreesOfLatitu de)


Direction of altitude (directionOfAlti tude)


Latitude sign (latitudeSign)


Degrees of longitude (degreesOfLongi tude)


DN09185982

69


Table 26


Parameters used for activating and configuring LTE951: Enhanced Cell ID Location Service (Cont.) Parameter

Purpose


Orientation of major axis (orientationOfMajorAxis)


Uncertainty altitude (uncertaintyAlti tude)


Uncertainty semimajor (uncertaintySemiMaj or)


Uncertainty semiminor (uncertaintySemiMin or)


Overall supervision mandatory configuration timer for ECID measurements (ecidMeasSupervisionTimer )

no

Periodical measurements for location services (perMeasLocServ)

optional configuration in case Intra-frequency Reference Signal Received Power (RSRP) and/or Reference Signal Received Quality (RSRQ) is to be supported

no

Report amount periodical meas for location (reportAmountPer Loc)

mandatory in case the Periodical measurements for location services (perMeasLocS erv) structure is configured

no

Report interval periodical meas for location (reportIntervalPerLoc)

mandatory in case the Periodical measurements for location services (perMeasLocS erv) structure is configured

no

The Activate LPPa enhanced cell ID location service (actLPPaEcid) LNBTS parameter is used for activation. Modification of this parameter requires neither an eNB restart nor cell locking.

70

DN09185982

Issue: 01D


g


Note: The feature parameters' configuration applies only to forthcoming requests. It does not affect any ongoing or queued request procedures. The eNB takes the configuration changes into account without affecting any service (without restarting). Procedure To activate the feature, do the following: 1


2

Activate the LTE951: Enhanced Cell ID Location Service feature. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate LPPa enhanced cell ID location service (actLPPaEcid) LNBTS parameter value to true.

Configure the Overall supervision timer for ECID measurements (ecidMeasSupervisionTimer) LNCEL parameter. a) Expand the LNBTS object. b) Select the LNCEL object. c) Set the Overall supervision timer for ECID measurements (ecidMeasSupervisionTimer) LNCEL parameter to an appropriate value.

g

Note: The

Overall supervision timer for ECID measurements (ecidMeasSupervisionTimer) LNCEL parameter must be configured in all LNCEL objects in one eNB.

4

If an eNB is to send the E-UTRAN access point position to E-SMLC, configure the E-UTRAN access point position (eutranAccessPointPosition) object (optional). a) Select the LNCEL object. b) Right-click the LNCEL object and, from the drop-down list, select New ► EUTRAN access point position object.

g

Issue: 01D

Note: Perform the following step only if you executed the previous step.

DN09185982

71


5

Configure the E-UTRAN access point position (eutranAccessPointPosition) structure. a) b) c) d)

Expand the LNCEL object. Expand the E-UTRAN access point position. Select the E-UTRAN access point position-1. Configure the following parameters (mandatory): • • • • • • • • • •

6


Altitude (altitude) Confidence (confidence) Degrees of latitude (degreesOfLatitude) Degrees of longitude (degreesOfLongitude) Direction of altitude (directionOfAltitude) Latitude sign (latitudeSign) Orientation of major axis (orientationOfMajorAxis) Uncertainty altitude (uncertaintyAltitude) Uncertainty semi-major (uncertaintySemiMajor) Uncertainty semi-minor (uncertaintySemiMinor)

To be able to provide the RSRP and/or RSRQ LPPa measurements, configure the RSRP and RSRQ measurements (optional). a) Select the LNCEL object. b) Right-click the LNCEL object and, from the drop-down list, select New ► Periodical measurements for location services (perMeasLocServ) object.

g

Note: Perform the following step only if you executed the previous step.

7

Configure the Periodical measurements for location services (perMeasLocServ) LNCEL structure. a) b) c) d)

72

Expand the LNCEL object. Expand the Periodical measurements for location services. Select the Periodical measurements for location services-1. Configure parameters in the structure to required values.

DN09185982

Issue: 01D


g


Note: When configuring the structure, remember that the value of the

Overall supervision timer for ECID measurements (ecidMeasSupervisionTimer) LNCEL parameter must be greater than Report amount periodical meas for location (reportAmountPerLoc) multiplied by Report interval periodical meas for location (reportIntervalPerLoc). You can start your configuration with the following values: • • •

8

Overall supervision timer for ECID measurements (ecidMeasSupervisionTimer) set to 3000 ms. Report interval periodical meas for location (reportIntervalPerLoc) set to 640 ms. Report amount periodical meas for location (reportAmountPerLoc) set to 2.


Expected outcome • • • • •

The eNB persistently stores all new and modified configuration data. The eNB informs NetAct and BTS Site Manager about the changed configuration via configuration change notifications (CCNs). The eNB takes the configuration changes into account without affecting the service (without restarting). The LTE951: Enhanced Cell ID Location Service feature activation flag is set to true. The eNB reports E-CID measurements in the E-CID MEASUREMENT INITIATION RESPONSE message when requested by the E-SMLC. The E-SMLC uses the ECID measurements to calculate the UE's location.

3.4.3 Deactivating LTE951: Enhanced Cell ID Location Service Before you start The Activate LPPa enhanced cell ID location service (actLPPaEcid) LNBTS parameter is used for deactivation. Modification of this parameter requires neither an eNB restart nor cell locking.

g

Note: Feature deactivation applies only to forthcoming requests. It does not affect any ongoing or queued request procedures. The eNB takes the configuration changes into account without affecting any service (without restarting). Procedure To deactivate the feature, do the following:

Issue: 01D

DN09185982

73


1



2

Deactivate the LTE951: Enhanced Cell ID Location Service feature. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate LPPa enhanced cell ID location service (actLPPaEcid) LNBTS parameter's value to false.

Send the parameter to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.

Expected outcome • • • • •

The eNB deactivates the LTE951: Enhanced Cell ID Location Service feature for any upcoming requests. The eNB informs NetAct and BTS Site Manager about the changed configuration via configuration change notifications (CCNs). The eNB takes the configuration change into account without affecting the service (without restarting). The LTE951: Enhanced Cell ID Location Service feature activation flag is set to false. The eNB will respond to any E-CID MEASUREMENT INITIATION REQUEST message with an E-CID MEASUREMENT INITIATION FAILURE message with a failure cause: Requested Item not Supported.

3.5 LTE1117: LTE MBMS 3.5.1 Description of LTE1117: LTE MBMS Introduction to the feature The LTE1117: LTE MBMS feature introduces the Multimedia Broadcast Multicast Service (MBMS), which is a point-to-multipoint service allowing efficient multimedia delivery from a single source entity to multiple recipients, using broadcast services. The MBMS can be used, for example, for mobile TV and radio broadcasting. Benefits End-user benefits The goal of the MBMS is to provide the end users with a possibility to receive broadcasts (videos) over the cellular network.

74

DN09185982

Issue: 01D



Operator benefits The LTE1117: LTE MBMS feature provides a basic framework at an eNodeB to support the MBMS. Requirements Hardware and software requirements Table 27

Hardware and software requirements

System release

FDD-LTE 15A

Flexi Multiradio BTS -

Flexi Zone Controller -


OMS -

UE 3GPP R9

Flexi Zone Micro BTS -

-

NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements This feature requires additional hardware for the Broadcast Multicast Service Center (BM-SC). Besides the BM-SC, this feature requires additional logical architectural elements such as the MBMS Gateway (GW). Functional description Functional overview The Flexi Multiradio BTS supports the MBMS by adding the multicell/multicast coordinating entity (MCE) to the existing functionality. The MCE is a software entity integrated in the eNodeB, and it follows a decentralized MCE architecture. The MCE takes care of MBMS resource management and control information scheduling across cells. Architecture The figure below shows a reference architecture for an MBMS broadcast mode in EUTRAN. This includes a multicell/multicast co-ordination (MCE) entity within the eNB. Figure 3

Issue: 01D

MBMS architecture

DN09185982

75



The LTE1117: LTE MBMS feature introduces the following logical entities in its architecture: Broadcast/Multicast Service Center (BM-SC) • • • •

MBMS user service provisioning and delivery MBMS bearer service authorization and initiation MBMS transmission scheduling and delivery entry point for content provider's transmissions

MBMS gateway • •

MBMS packet delivery to eNBs MBMS session control towards E-UTRAN

Multi-cell/multicast coordination entity (MCE) • •

MBMS admission control MBMS radio resource allocation

The LTE1117: LTE MBMS feature introduces the following control plane interfaces: M2 interface between MCE and eNB • • • •

MBMS session control (session start/stop/update) MBMS scheduling information MBMS radio configuration data the M2 interface is not exposed outside the eNB because of the distributed MCE architecture

M3 interface between MME and MCE • • •

MBMS session control (session start/stop/update) does not convey radio configuration data point-to-point SCTP used as signaling transport

Sm interface between MBMS GW and MME • •

MBMS session control (session start/stop/update) MBMS service area control

SGmb interface between BM-SC and MBMS GW • •

MBMS session control (session start/stop/update) MBMS service area control

The LTE1117: LTE MBMS feature introduces the following UP interfaces: M1 interface between MBMS GW and eNB •

IP multicast used for user plane data delivery

SGi/SGi-mb interface between BM-SC and PDN/MBMS GW •

76

point-to-point MBMS data delivery

DN09185982

Issue: 01D



Concepts and definitions MBMS single frequency network (MBSFN) • •

exactly the same signal is transmitted at the same time from a cluster of neighboring cells energy is combined without experiencing inter-cell interference

MBMS service area • •

comprises one or more MBMS service area identities (MBMS SAIs) a cell may belong to one or more MBMS SAs

MBSFN synchronization area • • •

All eNBs are synchronized and perform MBSFN transmissions. MBSFN synchronization areas support one or more MBSFN areas. On a given frequency layer, an eNB can only belong to a single MBSFN synchronization area.

MBSFN area •

a group of cells within an MBSFN synchronization area of a network, coordinated to achieve an MBSFN transmission

MBMS Service ID Uniquely identifies MBMS bearer service within a public land mobile network (PLMN), which identifies part of temporary mobile group identity • •

allocated by BM-SC provided to the UE via service announcement

Temporary mobile group identity The TMGI is uniquely used by the UE and BM-SC to identify an MBMS bearer. It is an equivalent to an IP multicast address and APN • •

allocated by BM-SC provided to UE via service announcement

MBMS user service May use one or more multicast services at a time within MBMS service area bound to a user service. • •

A single broadcast service can only have one broadcast session at any time within the MBMS service area bound to this user service. A broadcast service may consist of multiple successive broadcast sessions.

Session ID It is an integer broadcast over the air in MCCH. •

Issue: 01D

It is assigned by the BM-SC, which, together with TMGI, allows the UE to distinguish MBMS transmissions/retransmissions of a specific MBMS session.

DN09185982

77


•


This information is included in the individual PMCH along with other configuration parameters sent to the UE.

Figure 4

MBMS definitions

Protocol architecture The support of MBMS in LTE requires new logical (MTCH, MCCH), transport (MCH) and physical channels (PMCH). It also extends the existing SIB2 and SIB3 and introduces SIB13.

78

DN09185982

Issue: 01D



Limitations • • • • •

Content synchronization across cells of multiple eNodeBs can be only guaranteed by proper configuration of each eNodeB’s MCE. This is ensured by NetAct. 1.4, 3, 5 MHz are not supported for MBMS Deployed on a single frequency plane only. Consequently, mobility procedures for MBMS reception over more than one frequency will not be supported. MBSFN Area reserved cell which does not perform MBSFN transmission is not supported. MBMS Service counting is not supported.

System impact Interdependencies between features The following features have to be enabled before the activation of the LTE1117: LTE MBMS feature: • • •

LTE80: GPS Synchronization or LTE891: Timing over Packet with Phase Synchronization LTE648: SCTP Multi-homing (optional)

The following features must be disabled before the LTE1117: LTE MBMS feature activation: • • • • • • • • • • • •

LTE1382: Cell Resource Groups LTE4: RAN Sharing LTE125: IPv6 for U/C-plane LTE116: Cell Bandwidth 3 MHz LTE117: Cell Bandwidth 1.4 MHz LTE115: Cell Bandwidth 5 MHz LTE48: High Speed User LTE505: Transport Separation for RAN Sharing LTE1113: eICIC - Macro LTE1496: eICIC - Micro LTE819: DL Inter-cell Interference Generation LTE1891: eNodeB Power Saving - Micro DTX

The following features might have a negative impact on the LTE1117: LTE MBMS: • • • • • •

LTE55: Inter-frequency Handover LTE56: Inter-RAT Handover to WCDMA LTE442: Network assisted cell change to GSM LTE736: CS fallback to UTRAN LTE873: SRVCC to GSM LTE872: SRVCC to WCDMA

The following features have an impact on the LTE1117: LTE MBMS feature (interoperation required): • •

Issue: 01D

LTE42: DRX in RRC Connected Mode LTE585: Smart DRX

DN09185982

79


• • • • • • • • • • •


LTE1089: Downlink Carrier Aggregation - 20 MHz LTE1332: Downlink Carrier Aggregation - 40 MHz LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs LTE1910: S1 Lock/Unlock LTE2085: SIB Reception with Parallel Measurement Gaps LTE1709: Liquid Cell LTE843: ETWS Broadcast LTE495: OTDOA (Observed Timer Difference of Arrival) LTE494: CMAS (Commercial Mobile Alert System)

Management data Measurements and counters The table below lists counters introduced with this feature. Table 28


Counter name

Measurement

M8030C1

Average number of activated MBMS sessions

8030 - LTE MBMS (WBTS)

M8030C2

MBMS user data volume (eUu interface)


M8030C3

MBMS user data volume (M1 interface)


M8030C4

Lost MBMS user data volume (M1 interface)


M8030C5

Dropped MBMS user data volume 1 (M1 interface)


M8030C6

Dropped MBMS user data volume 2


Parameters The table below lists the parameters introduced with this feature. Table 29

New parameters

Full name Activate support for MBMS

80

Abbreviated name actMBMS

Managed object

Structure

LNBTS

-

MBMS neighbour cells mbmsNeighCellConfig LNCEL configuration IntraF

-

Administrative state

administrativeState

LNM3

-

LTE MME M3 link identifier

lnM3Id

LNM3

-

M3 Link Status

m3LinkStatus

LNM3

-

DN09185982

Issue: 01D


Table 29


Full name

Issue: 01D


Abbreviated name

Managed object

Structure

M3 Primary IPv4 address

m3ipAddrPrim

LNM3

-

M3 Secondary IPv4 address

m3ipAddrSec

LNM3

-

Multi-cell multicast coordination entity identifier

lnMceId

LNMCE

-

MCE Identity

mceId

LNMCE

-

MCE Name

mceName

LNMCE

-

MBMS Service Area

mbmsServiceArea

MBSFN

-

MBMS SYNC reference

mbmsSyncRef

MBSFN

-

MBSFN Area Identity

mbsfnAreaId

MBSFN

-

MBSFN downlink channel bandwidth

mbsfnDlChBw

MBSFN

-

MBSFN EARFCN

mbsfnEarfcn

MBSFN

-

MBMS single frequency network identifier

mbsfnId

MBSFN

-

Multicast channel info

mchInfo

MBSFN

-

Signalling Modulation and coding scheme

signallingMCS

MBSFN

-

Required MBSFN subframe pattern share

subfrPShareRequired

MBSFN

-

Fractional seconds

fractionalSecs

MBSFN

mbmsSyncRef

Integral seconds

integralSecs

MBSFN

mbmsSyncRef

Data Modulation Code dataMCS Scheme

MBSFN

mchInfo

MBMS SYNC period

mbmsSyncPeriod

MBSFN

mchInfo

Multicast channel Scheduling period

mchSchedulingPeriod

MBSFN

mchInfo

QCI

qci

MBSFN

mchInfo

Deployed MBSFN subframe pattern share

subfrPShareDeployed

MBSFN

-

Multicast application identifier

mcAppId

MCAPP

-

IPv4 Multicast Application Type

mcAppType

MCAPP

-

IPv4 Multicast Used Link Layer Interface

usedLinkLayerIf

MCAPP

-

LTE MBMS

mtMBMS

PMRNL

-

DN09185982

81


Table 29



Full name Cell power reduction for MBMS transmission

Abbreviated name cellPwrRedForMBMS

Managed object LNCEL

Structure -

The table below lists the existing parameters related to this feature. Table 30


Full name

82

Abbreviated name

Managed object

Structure

Carrier aggregation relation identifier

caRelId

CAREL

-

Local cell resource ID of cell to be aggregated

lcrId

CAREL

-

Activation Flag Dual U-Plane Ip Addresses

actDualUPlaneIpAddre IPNO ss

-

Activation Flag Transport Separation For RAN Sharing

actSeparationRanShar IPNO ing

-

Activate liquid cell configuration

actLiquidCell

LNCEL

-

PRS activation

actOtdoa

LNCEL

-

Cell resource sharing mode

cellResourceSharingM LNCEL ode

-

Cell power reduce

dlCellPwrRed

LNCEL

-

Downlink channel bandwidth

dlChBw

LNCEL

-

DRX profile 2

drxProfile2

LNCEL

-

DRX inactivity timer

drxInactivityT

LNCEL

drxProfile2

DRX long cycle

drxLongCycle

LNCEL

drxProfile2

DRX on duration timer drxOnDuratT

LNCEL

drxProfile2

DRX profile index

drxProfileIndex

LNCEL

drxProfile2

DRX profile priority

drxProfilePriority

LNCEL

drxProfile2

DRX retransmission timer

drxRetransT

LNCEL

drxProfile2

DRX profile 3

drxProfile3

LNCEL

-


drxInactivityT

LNCEL

drxProfile3

DRX long cycle

drxLongCycle

LNCEL

drxProfile3


LNCEL

drxProfile3

DRX profile index

drxProfileIndex

LNCEL

drxProfile3


drxProfilePriority

LNCEL

drxProfile3


drxRetransT

LNCEL

drxProfile3

DN09185982

Issue: 01D


Table 30


Full name

Issue: 01D


Abbreviated name

Managed object

Structure

DRX smart profile 2

drxSmartProfile2

LNCEL

-


drxInactivityT

LNCEL

drxSmartProfile2

DRX long cycle

drxLongCycle

LNCEL

drxSmartProfile2


LNCEL

drxSmartProfile2

DRX profile index

drxProfileIndex

LNCEL

drxSmartProfile2


drxProfilePriority

LNCEL

drxSmartProfile2


drxRetransT

LNCEL

drxSmartProfile2

DRX short cycle

drxShortCycle

LNCEL

drxSmartProfile2

DRX short cycle timer

drxShortCycleT

LNCEL

drxSmartProfile2

Short term inactivity factor for smart DRX

smartStInactFactor

LNCEL

drxSmartProfile2

DRX smart profile 3

drxSmartProfile3

LNCEL

-


drxInactivityT

LNCEL

drxSmartProfile3

DRX long cycle

drxLongCycle

LNCEL

drxSmartProfile3


LNCEL

drxSmartProfile3

DRX profile index

drxProfileIndex

LNCEL

drxSmartProfile3


drxProfilePriority

LNCEL

drxSmartProfile3


drxRetransT

LNCEL

drxSmartProfile3

DRX short cycle

drxShortCycle

LNCEL

drxSmartProfile3

DRX short cycle timer

drxShortCycleT

LNCEL

drxSmartProfile3

Short term inactivity factor for smart DRX

smartStInactFactor

LNCEL

drxSmartProfile3

Liquid cell configuration information

liquidCellConfigInfo

LNCEL

-

CSI-RS power offset overlapping region

csiRsPwrOffsetOverla p

LNCEL


CSI-RS resource configuration

csiRsRes

LNCEL


CSI-RS subframe configuration

csiRsSubfr

LNCEL


LTE cell configuration identifier

lnCelId

LNCEL

-

Maximum output power

pMax

LNCEL

-

PRACH high speed flag

prachHsFlag

LNCEL

-

PRS configuration index

prsConfigurationIndex

LNCEL

-

DN09185982

83


Table 30



Full name

Abbreviated name

Managed object

Structure

Random access response window size

raRespWinSize

LNCEL

-

SI window length

siWindowLen

LNCEL

-

Twofold transmission of SIBs per SI window

sib2xTransmit

LNCEL

-

System information scheduling list

sibSchedulingList

LNCEL

-

Periodicity

siMessagePeriodicity

LNCEL

sibSchedulingList

Repetition

siMessageRepetition

LNCEL

sibSchedulingList

SIB type

siMessageSibType

LNCEL

sibSchedulingList




ASW

SW asset monitoring


3.5.2 Activating and configuring LTE1117: LTE MBMS Before you start The following information provides the details and conditions for correct activation of the LTE1117: LTE MBMS feature.

g

Note: The LTE1117: LTE MBMS feature has to be activated on all the eNBs with the same MBSFN SYNC using the NetAct Configurator for this purpose. More information can be found in the NetAct documentation following the path below: NetAct Documentation ► Configuration Management ► Configuration Management Operating Procedures ► Managing the Network with NetAct Configurator ► Managing Multimedia Broadcast Multicast Service (MBMS) with a workflow The table below lists the parameters used for activating and configuring the LTE1117: LTE MBMS feature. Table 32

Parameters used for activating and configuring the LTE1117: LTE MBMS feature Parameter

84

Purpose


Activate support for MBMS (actMBMS)

activation flag

no

LNBTS: LNMCE parameters


no

LNMCE: LNM3 parameters


no

LNMCE: MBSFN parameters


no

DN09185982

Issue: 01D



All the parameters can be found in Management data. Certain parameters have to be set consistently between eNBs and BM-SC. Please refer to the sections below. MBMS subframe percentage determination When determining the percentage of downlink subframes that need to be allocated to MBMS, the operator needs to consider the following items: data rates of MBMS services that will be transmitted simultaneously MCS at which the MBMS data will be transmitted (Data MCS) system bandwidth (10, 15, or 20 MHz)

• • •

The Table 33: MBMS Data Rate table, derived from TS36.213 section 7.1.7.2.1, provides guidance for making subframe percentage selections based on the above items. Nokia recommends subframe percentage selection not to exceed 40% to ensure that unicast capacity is not adversly affected. Table 33

MBMS Data Rate table Data Bits/Second versus MBMS Data MCS*

Cell BW (MHz)

Issue: 01D

% SD for MBMS

MCS 5

MCS 10

MCS 15

MCS 20

10

40

1581120

3153600

5080320

7698240

15

40

2416320

4665600

7698240

11828160

20

40

3153600

6324480

10200960 15773760

10

35

1383480

2759400

4445280

6735960

15

35

2114280

4082400

6735960

10349640

20

35

2759400

5533920

8925840

13802040

10

30

1185840

2365200

3810240

5773680

15

30

1812240

3499200

5773680

8871120

20

30

2365200

4743360

7650720

11830320

10

25

988200

1971000

3175200

4811400

15

25

1510200

2916000

4811400

7392600

20

25

1971000

3952800

6375600

9858600

10

20

790560

1576800

2540160

384912

15

20

1208160

2332800

3849120

5914080

20

20

1576800

3162240

5100480

7886880

10

15

592920

1182600

1905120

2886840

15

15

906120

1749600

2886840

4435560

20

15

1182600

2371680

3825360

5915160

10

10

395280

788400

1270080

1924560

15

10

604080

1166400

1924560

2957040

20

10

788400

1581120

2550240

3943440

10

5

197640

394200

635040

962280

DN09185982

85


Table 33


MBMS Data Rate table (Cont.) Data Bits/Second versus MBMS Data MCS*

Cell BW (MHz)

% SD for MBMS

MCS 5

MCS 10

MCS 15

MCS 20

15

5

302040

583200

962280

1478520

20

5

394200

790560

1275120

1971720

10

2.5

98820

197100

317520

481140

15

2.5

151020

291600

481140

739260

20

2.5

197100

395280

637560

985860

* Bits/Second is reduced by 10% due to MBMS signaling subframes and RLC/MAC header overhead. MBMS Subframe Percentage Examples Example 1: Single service • • •

video stream with 720p @ 2 Mbps cell BW = 15 MHz data MCS selected = 10

Based on the video specifications, and using the MBMS Data Rate table, 30% MBMS subframes is the lowest MBMS subframe percentage that provides at least 2 Mbps (2,365,200 bps) with the given parameters. Example 2: Multiple services with multiple data MCSs Video stream with 720p @ 2 Mbps • •

cell BW = 10 MHz data MCS selected = 10

Audio Streaming @ 100 kbps • •

cell BW = 10 MHz data MCS selected = 15

The video stream will require at least 30% MBMS sub frames to achieve 2 Mbps (2,365,200 bps) ) at 10 MHz and MCS = 10. The audio streams will require an additional 100 Kbps at 10MHz and MCS = 15. Since the 30% of MBMS sub frames selected provides 2,365,200 Kbps, the remaining bandwidth is more than is necessary for the audio, this excess bandwidth is more than enough to support the 100 Kbps required by the audio streams. No additional MBMS sub frames need to be allocated for the audio. Configuration for MBMS data flow synchronization In order to ensure synchronized radio interface, MBMS transmission from the cells controlled by different eNBs, MBMS SYNC-protocol [TS 25.446] support is needed between BM-SC and the eNBs. As part of the SYNC-protocol, certain parameters have to be set consistently between the BM-SC and the eNBs, namely:

86

DN09185982

Issue: 01D


•

•

•


Common time reference: on the eNB, this parameter is called MBMS SYNC Reference. This parameter has to be set in the same way on both the eNB and BMSC after ensuring that both the eNB and BM-SC are synchronized to the same clock source such as NTP or GPS synchronization. Example: Based on NTP on the eNB, if MBMS SYNC Reference::Integral Seconds is set to 3615771600, and MBMS SYNC Reference::Fractional Seconds is set to 0, then the same equivalent value has to be provisioned on the BM-SC. Synchronization Period: as part of the SYNC-protocol, both BM-SC and eNB for each service have to maintain the same synchronization period. On the eNB, this parameter is called MBMS SYNC Period, after which the relative timestamps within the SYNC PDUs can wrap around. Synchronization sequence: Each SYNC PDU contains a timestamp that indicates the start time of a sequence for an MBMS service. Since the BM-SC is not aware of the MCE/eNB scheduling boundaries, the synchronization sequence length that is configured on the BM-SC has to be proportional to the Multicast Channel Scheduling Period (MSP) on the eNB. The MSP length provisioned in the eNB is one or multiple times of the synchronization sequence length for MBMS services in the MCH.

The BM-SC includes a timestamp in the SYNC PDUs, based on which the eNB has to send MBMS data over the air interface. The time stamping of SYNC PDUs, is based upon a relative time value from the above common time reference, which refers to the start time of the synchronization period. The eNB will schedule the received data packets in the first MSP following the time point indicated by the timestamp. If they are not configured properly, a poor MBMS service may be observed due to excessive packet drops. Too long of an MSP with a high dataMCS will require that large amounts of data are buffered at the eNB prior to the MBMS transmission. If the buffered data size becomes too large, packets may become lost. The Activate support for MBMS (actMBMS) parameter can only be set to true only if all the following conditions are fulfilled: • • • • • •

The eNB has the RNW database activated and is in service. NetAct is in service and the DCN connection to eNB is established via OMS. At least one S1 link is established. MBMS-related information in the transport domain is configured. At least one LNCEL instance with earfcn equal to MBSFN-mbsfnEarfcn and chBw equal to MBSFN-mbsfnDlChBw must be created. The following conditions must be fulfilled in all cells which are candidates for MBMS broadcasting, that is with earfcn equal to MBSFN-mbsfnEarfcn and chBw equal to MBSFN-mbsfnDlChBw: –

– – –

Issue: 01D

The LTE48: High speed users feature is deactivated, that is prachHsFlag is equal to false in all LNCEL instances with earfcnDL equal to MBSFNmbsfnEarfcn. The LTE1382: Cell resource groups feature is deactivated, that is cellResourceSharingMode equal to none. The LTE1113: eICIC-macro and LTE1496 eICIC-micro features are deactivated, that is actEicic is equal to false. If the LTE495: OTDOA is activated, that is if actOtdoa is equal to ‘true’ restriction for configuration of the parameter prsConfigurationIndex is considered.

DN09185982

87


TDD subframe configuration sa2 (3GPP 36.331) is selected, that is tdFrameConf is equal to '2'. The restrictions on the configuration of the CSI-RS subframe configuration (LNCEL parameter csiRsSubfrConf) are considered.

– –

The drxOnDuratT, drxRetransT and raRespWinSize parameters must be:

•

greater than or equal to 6 if subfrPShareRequired is less than or equal to 20. greater than or equal to 10 if subfrPShareRequired is greater than 20.

– – •

SIB13 must be present in sibSchedulingList-siMessageSibType.

•

The following configuration rules apply. The LTE124: IPv6feature must not be activated, that is the IPNO parameter actIpv6 is equal to false. The LTE505: Transport Separation for RAN Sharing must not be activated, that is the IPNO parameter actSeparationRanSharing is equal to false. The LTE4: RAN Sharing feature is not configured, that is no further PLMN-Ids are configured in LNCEL parameter furtherPlmnIdL. Multiple S1 links are only used for redundancy but not for RAN sharing.

– – –

g


Note: • •

The MCE configuration must be aligned between eNBs/cells belonging to the same MBSFN synchronization area. The configuration of features LTE495 (OTDOA), LTE843 (ETWS), LTE494 (CMAS) and the setting of the LNCEL parameter sib2xTransmit must be aligned between adjacent eNBs with activated feature ‘MBMS' and belonging to the same MBSFN area, that is with the same mbsfnAreaId.

To activate and configure the feature, do the following: Procedure 1

Follow the general procedure described in section Activating and deactivating LTE features using the BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure.

2

Change the Network synchronisation mode to Phase synchronization. a) Go to the BTS Synchronization Settings page. b) Change the Network synchronization mode by choosing Phase synchronization from the drop-down menu.

3

Create the managed objects related to the configuration of the MBMS functionality. At least the following managed objects must exist:

88

DN09185982

Issue: 01D


•

LNBTS: LNMCE LNMCE: LNM3 LNMCE: MBSFN

a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Right-click on the LNBTS and create a new LNMCE object. Right-click on the LNMCE and create a new LNM3 and MBSFN objects.

• •

4


Set the required values in the MBSFN object. a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Expand the MBSFN object and configure the required parameters: • • •

Set the required value of the MBSFN Area Identity (mbsfnAreaId) between 0 and 225. Set the required value of the Required MBSFN subframe pattern share (subfrPShareRequired) from the drop down menu. Set the required value of the Signaling Modulation and coding scheme (signallingMCS) from the drop down menu.

e) Expand the MBSFN object f) Select the MBMS Service Area and type the required service area identifier. An example for a valid service area identifiers is: 0x00, 0x01, 0x3c5e. g) Select the MBSFN SYNC reference object and type in the desired values of the following parameters: • •

Fractional seconds Integral seconds

h) Select the Multicast channel info object and type in the desired values of the following parameters: • • •

i)

5

Data modulation Code Scheme MBMS Sync period Multicast channel Scheduling period

Select the LNM3object; set the required value of the LTE MME M3 link identifier parameters and type in the desired IPv4 address under the M3Primary IPv4 address using the correct IP format.

Define a new SIB Type (LNCEL:siMessageSibType) dedicated for the SIB13 in the System Information Scheduling list for each LNCEL instance of an eNB supporting MBMS. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object.

Issue: 01D

DN09185982

89


c) d) e) f)


Expand the LNBTS object. Expand the LNCEL object. Select and click the System information scheduling list. SelectSIB13 in SIB Type dropdown list and define Periodicity and

Repetition g) Proceed with definition of SIB13 in System information scheduling list for each LNCEL managed object defined for LNBTS

6

Activate the feature flag for LTE1117. a) b) c) d)

7

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate support for MBMS (actMBMS) parameter value to true.


Expected outcome MBMS is configured and activated

3.5.3 Deactivating LTE1117: LTE MBMS Before you start

g

Note: The Activate support for MBMS (actMBMS) parameter is used for deactivation. The LTE1117: LTE MBMS feature has also to be deactivated on all the eNBs which have the same MBSFN SYNC using the NetAct Configurator for this purpose. More information can be found in the NetAct documentation following the below path: NetAct Documentation ► Configuration Management ► Configuration Management Operating Procedures ► Managing the Network with NetAct Configurator ► Managing Multimedia Broadcast Multicast Service (MBMS) with a workflow Procedure 1


90

DN09185982

Issue: 01D


2


Deactivate the feature. a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object(s). Select the LNBTS object(s). Set the Activate support for MBMS (actMBMS) parameter value to false.

Expected outcome The LTE1117: LTE MBMS feature has been deactivated.

3.6 LTE1196: RAN Information Management for WCDMA 3.6.1 Description of LTE1196: RAN Information Management for WCDMA Introduction to the feature The LTE1196: RAN Information Management for WCDMA feature allows transferring information between the source and target cell by the core network. This mechanism allows to reduce the number of setting parameters. Benefits End-user benefits This feature provides the end user with: • •

faster CS fallback faster regular redirection

Operator benefits This feature provides: • • •

reduction of the parameters needed to configure CS fallback with redirection reduction of the parameters needed to configure regular redirection to WCDMA support of LTE multi-operator core network (MOCN) and WCDMA MOCN deployment

Requirements Hardware and software requirements Table 34: Hardware and software requirements presents the hardware and software requirements for the LTE1196: RAN Information Management for WCDMA feature.

Issue: 01D

DN09185982

91


Table 34



System release

Flexi Multiradio BTS

FDD 15A

FDD 15A


FDD 15A

OMS

UE

-


FDD 15A

NetAct

3GPP R9 UE capabilities


MME

15.5

-

SAE GW -

Additional hardware requirements There are no additional hardware requirements to this feature. Functional description Functional overview The RAN information management (RIM) procedures support the core network in an information exchange between peer application entities located in GERAN, UTRAN, or the E-UTRAN access network. The LTE1196: RAN Information Management to WCDMA feature allows up-to-date system information (SI) of WCDMA neighbor cells to be transferred from a remote radio network controller (RNC) to a local eNB. This proccess is used to populate WCDMA SI for redirection to the WCDMA procedure. Figure 5: RIM protocol structure between E-UTRAN and UTRAN presents the process of transporting protocols between LTE and WCDMA. Figure 5

RIM protocol structure between E-UTRAN and UTRAN

ENB (controlling)

S1

RIMContainer

RIM

S3 /GN

MME

IU

SGSN

RIM-App

RIM-App

RIM-App

RIM-App

RIM-App

RIM-App

(forexampleUTRASI)

(forexampleUTRASI)

SCTP IP/L2&L1

GTP-C

GTP-C

UDP

UDP

IP

IP

L2

L2

L1

L1

RANAP

RANAP

NS

NS

L1

L1

IP/L2&L1

S1AP

SCTP

IP/L2&L1

RIM

Relay

Relay

SCTP

RIMContainer

RIMPDUs

RIMPDUs

S1AP

RNC (Serving)

The RIM function enables the eNB to retrieve SI from the target UTRAN cell and allows the eNB to receive WCDMA SI from a remote RNC. The eNB supports the RIM for CS fallback with a redirect and a normal redirect to WCDMA.

92

DN09185982

Issue: 01D



The RIM function enables the eNB to retrieve SI from a target WCDMA cell. The retrieved information is used to automatically fill and update the related SI attributes for all the enabled features to which an RRC connection release with a redirect to WCDMA is applied. This proccess is presented in Figure 6: Redirection procedure with SI. Figure 6

Redirection procedure with SI

UE

(1)

MME

.eNB

RRC:RRCConnectionRelease (releaseCause,RedirectedCarierInfo, [cellinfoList-r9]) (2)

(3)

S1AP:UECONTEXTRELEASEREQUEST S1AP:UECONTEXTRELEASECOMMAND

(4)

S1AP:UECONTEXTRELEASECOMPLETE

For each neighbor WCDMA frequency of an LTE cell, up to 16 WCDMA neighbor cells can be enabled to provide SI via RIM in the redirect message. The same SI is sent in case of: • • •

a normal RRC connection release with a redirect to WCDMA a normal redirect based on CS fallback to WCDMA an emergency CS fallback to WCDMA to the UE

The assigned mobility profile and the UE capabilities are considered when selecting the SI to be added to the redirect message.

g

Note: In extreme conditions, the RIM UTRA SI application (ENBC) is running on FSMr2 board, and the memory for RIM UTRAN SI storage may be used up. For the new coming up LTE cells, the UTRAN SI for some WCDMA neighbor cells might be temporarily unavailable (not in UEC) until the next UTRAN SI update or RIM association re-establishment. If the WCDMA neighbor cells’ RIM interface status (rimStatus) is set to available at eNB level, it does not have impact on this process. It is caused due to memory capacity limitation of FSMr2 board. RAN information procedure for the enabled WCDMA neighbor cell The RIM protocol is encapsulated in the S1AP.MME DIRECT INFORMATION TRANSFER and the S1AP:ENB DIRECT INFORMATION TRANSFER messages. The following RIM procedures are supported: • • • • •

Issue: 01D

RAN information request/multiple report RAN information request/stop RAN information send RAN information application error RAN information error

DN09185982

93



Redirection procedure Selecting suitable cells The following conditions must be fulfilled for the eNB to check the RIM interface status (rimStatus) parameter for each suitable WCDMA cell: • •

if rimStatus is available, SI for the WCDMA cell is taken from RIM. if rimStatus is unavailable or disable, SI for the WCDMA cell is not included (theWCDMA cell is omitted by the eNB).

The following conditions must be fulfilled to check all objects (LNRELW object instances) related to the WCDMA neighboring cell for the LTE cell: • •

the WCDMA cell's frequency is the same as the chosen target frequency represented by the UARFCN value an active flag allows adding SI in a release message

Elimination of unsuitable cells by CS fallback If the RegisteredLAI was received, the eNB is checking PLMN and LAC values. At least one of the primary/secondary PLMNs and LAC configured for the WCDMA cell (in LNADJW), which SI is checked for, must be included in RegisteredLAI IE. Otherwise, SI for that WCDMA cell is eliminated from the list. • •

If the list is not empty, elimination of unsuitable targets is stopped. If the list is empty, eNB checks again all the targets from the original list as it was before, but only the PLMN value will be checked. Primary/secondary PLMNs configured for the WCDMA cell (in LNADJW) must be included in RegisteredLAI IE. Otherwise, SI for that WCDMA cell is eliminated from the list.

If the RegisteredLAI was not received, the handover restriction list was received and there was no emergency call, at least one of the primary/secondary PLMNs configured for the WCDMA cell (in LNADJW) must be included in the set of PLMN IDs allowed by the UE (a combination of Serving PLMN ID and Equivalent PLMN IDs optionally provided within the handover restriction list). Otherwise, SI for this WCDMA cell is eliminated from the list.

g

Note: For a selected UTRAN frequency, the O&M is configured for a UE context release only; the eNB will not add the WCDMA SI to the CSFB redirection message. Elimination of unsuitable cells by the UE context with redirection The list of chosen SI is checked in search of any unsuitable targets that need to be deleted. If the handover restriction list was received, and there was no emergency call, at least one of the primary/secondary PLMNs configured for the WCDMA cell (in LNADJW) must be included in the set of PLMN IDs allowed by the UE (a combination of serving PLMN ID and equivalent PLMN IDs optionally provided within the handover restriction list). Otherwise, SI for this WCDMA cell is eliminated from the list.

g

94

Note: For a selected UTRAN frequency, the O&M is configured for CS fallback only; the eNB will not add the WCDMA SI to the UE context release redirection message.

DN09185982

Issue: 01D



Support of Direct Information Transfer by S1 interface On the S1 interface, the following procedures are supported to transmit RIM information: • •

the eNB Direct Information Transfer procedure to transmit an information container from the eNB to the MME the MME Direct Information Transfer procedure to transmit an information container from the MME to the eNB

System impact Interdependencies between features The following features will make use of UTRA SI acquired via the RIM function: • • • • • • •

g

LTE562: CSFB to UTRAN/GERAN via Redirection LTE22: Emergency Call Handling LTE423: RRC Connection Release with Redirect LTE1073: Measurement-based Redirect to UTRAN LTE1407: RSRQ-based Redirect LTE2108: Redirected VoLTE Call Setup LTE2388: VoLTE Call Steering Enhancement Note: The LTE1196: RAN Information Management for WCDMA feature reuses most of the procedures of the LTE498 RAN Information Management for GSM feature, but there is no dependency relationship between both features.

g

Note: The LTE908: ANR Inter-RAT UTRAN – fully UE-based feature should also be considered as RIM-enabled (if automatically created UTRAN neighbor cells are not on the RIM PLMN blacklist). The LTE1342: Extended RNC ID feature interact with the LTE1196: RAN Management Information for WCDMA feature. If the LTE1342: Extended RNC ID feature is enabled, the LTE1196: RAN Information Management for WCDMA feature will use extended RNCID in RIM messages. The extended RNC-ID is configured for a UTRAN neighbor cell. Impact on interfaces This feature impacts: • • •

the RRC protocol in the LTE-Iu interface the S1AP protocol in the S1-MME interface the interface to NetAct

Impact on network 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. Management data

Issue: 01D

DN09185982

95



Alarms The LTE1196: RAN Information Management for WCDMA feature will reuse alarms from the LTE498: RAN Information Management for GSM feature included in Table 35: Related existing alarms. Table 35

Related existing alarms Alarm ID

Alarm name

7657

BASE STATION CONNECTIVITY DEGRADED The alarm is caused by the following BTS faults: •

RIM interface timeout (fault id 6322)

•

RIM interface error (fault id 6323)

Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no new key performance indicators related to this feature. Parameters Table 36: New parameters lists new parameters introduced with this feature. Table 36

New parameters

Full name

96

Abbreviated name

Managed object

Structure

RIM interface status

rimStatus

LNADJW

-

Activate RAN information management for UTRAN

actRIMforUTRAN

LNBTS

-

Blacklisted UTRAN cells for RIM

blacklistUtranCellsForRi m

LNBTS

-

MCC

Mcc

LNBTS

blacklistUtranCellsFor Rim

MNC

Mnc

LNBTS


MNC length

mncLength

LNBTS


RNC ID

rncId

LNBTS


UTRAN carrier frequency

utranCarrierFreq

LNBTS


Max. RIR attempts to UTRAN

nRimRirU

LNBTS

-

Timer to wait for next RI PDU from UTRAN

tRimKaU

LNBTS

-

DN09185982

Issue: 01D


Table 36


Full name

g


Abbreviated name

Managed object

Structure

Polling timer to tRimPollU ReStart RIR procedure to UTRAN

LNBTS

-

Timer to wait for RIR tRimRirU response from UTRAN

LNBTS

-

Reachable PLMNs for RIM

rimReachablePLMNList

LNMME

-

MCC

mcc

LNMME

rimReachablePLMNLi st

MNC

mnc

LNMME


MNC length

mncLength

LNMME


Redirect with system information allowed

redirWithSysInfoAllowed LNRELW

-

Add UTRAN system information to redirection message

addUtranSIToRedirMsg

MODRED

-



MORED

-



REDRT

-

Note: Manual configuration of WCDMA system information is no longer supported. The SystemInformationListWCDMA LNBTS parameter is removed. Sales information Table 37: Sales information lists sales information about this feature. Table 37


ASW

License control in network element Pool license


3.6.2 Activating and configuring LTE1196: RAN Information Management for WCDMA Before you start Table 38: Parameters used for activating and configuring LTE1196: RAN Information Management for WCDMA lists parameters used for activation and configuration of the LTE1196: RAN Information Management for WCDMA feature.

Issue: 01D

DN09185982

97


Table 38


Parameters used for activating and configuring LTE1196: RAN Information Management for WCDMA Parameter

98

Purpose


Active RAN Information Management for UTRAN (actRIMforUTRAN)

activation flag

no

Timer to wait for RIR response from UTRAN (tRimRirU)


no

Timer to wait for next RI PDU from UTRAN (tRimKaU)


no

Polling timer to ReStart RIR procedure to UTRAN (tRimPollU)


no

Max. RIR attempts to UTRAN (nRimRirU)


no

Redirection target configuration identifier (redir)


no

RAT for redirection (redirRat)


no

Mobility default profile identifier for redirection (moDRedId)


no

Redirection priority for CS fallback with redirection (csFallBPrio)


no

Reachable PLMNs for RIM (rimReachablePLMNList)


no

Mobility profile identifier (moPrId)


no

Mobility default profile identifier for redirection (moRedId)


no

Blacklisted UTRAN cells for RIM (blacklistUtranCellsForRim)


no

MCC (mcc)


no

MNC (mnc)


no

MNC length (mncLength)


no

RNC Id (rncId)


no

UTRAN carrier frequency (utranCarrierFreq)


no

Redirect with system information allowed (redirWithSysInfoAllowed)


no

Target cell Id in UTRAN CGI of related neighbor cell (uTargetCid)


no

Target RNC Id (uTargetRncId)


no

Add UTRAN system information to redirection message (addUtranSIToRedirMsg)


no

eUTRA frequency (redirFreqEutra)


no

DN09185982

Issue: 01D



Before activation and configuration of the LTE1196: RAN Information Management for WCDMA feature ensure that there is an LNADJW object configured with all required parameters. If there is no LNADJW object configured, the handover is not possible. To activate the feature, do the following: Procedure 1


2

Optional: If not yet configured, configure the LNADJW object with all parameters. a) b) c) d) e) f) g) h) i) j) k) l) m) n)

3

Activate the feature flag of the LTE1196: RAN Information Management for WCDMA feature. a) b) c) d)

Issue: 01D

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Add the LNADJW object. Set the Neighbor WCDMA BTS cell identifier (InAdjWId) parameter's value to a desired value from 0 to 255. Set the Primary scrambling code (FDD) (uTargetScFdd) parameter's value to a desired value from 0 to 511. Set the Target cell ID (uTargetCid) parameter's value to a desired value from 0 to 65535. Set the Target frequency (uTargetFreq) parameter's value to a desired value from 0 to 16383. Set the Target location area code (uTargetLac) parameter's value to a desired value from 0 to 65535. Set the Target RNC ID (uTargetRncId) parameter's value to a desired value from 0 to 65535. Set the Target routing area code (uTargetRac) parameter's value to a desired value from 0 to 255. Expand the Target primary PLMN identy object. Set the MCC, MNC (mcc, mnc) parameters' value to a desired value from 0 to 999. Set the MNC length (mncLength) parameter's value to a desired value from 2 to 3.

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Active RAN Information Management for UTRAN (actRIMforUTRAN) parameter's value to true.

DN09185982

99


4


Optional: Adapt RIM-specific timer and retransmission counter. a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Timer to wait for RIR response from UTRAN (tRimRirU) parameter's value to a desired value from 1 to 15. e) Set the Timer to wait for next RI PDU from UTRAN (tRimKaU) parameter's value to a desired value from 15 to 14400. f) Set the Polling timer to ReStart RIR procedure to UTRAN (tRimPollU) parameter's value to a desired value from 5 to 14400. g) Set the Max. RIR attempts to UTRAN (nRimRirU) parameter's value to a desired value from 1 to 5.

5

Optional: Blacklist cells for WCDMA. a) b) c) d) e)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Expand the LNBTS object. Add the Blacklisted UTRAN cells for RIM (blacklistUtranCellsForRim) parameter. f) Set the MCC, MNC (mcc, mnc) parameters' value to a desired value from 0 to 999. g) Set the MNC length (mncLength) parameter's value to a desired value from 2 to 3. h) Set the RNC Id (rncId) parameter value to desired value from 0 to 65535. i) Set the UTRAN carrier frequency (utranCarrierFreq) parameter's value to a desired value from 0 to 16383.

g

Note: It is also possible to set the MCC, MNC, MNC length, RNC Id and UTRAN carrier frequency parameters by expanding the Blacklisted UTRAN cells for RIM object.

6

Optional: Configure one or more PLMN Ids. a) b) c) d) e) f)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Expand the LNBTS object. Expand the LNMME object. Add New Reachable PLMNs for RIM (rimReachablePLMNList) parameter. g) Set the MCC, MNC (mcc, mnc) parameters' value to a desired value from 0 to 999.

100

DN09185982

Issue: 01D



h) Set the MNC length (mncLength) parameter's value to a desired value from 2 to 3.

g

Note: It is also possible to set the MCC, MNC and MNC length parameters by expanding the Reachable PLMNs for RIM object.

7

Set the WCDMA neighbor relations which are not considered for redirection. a) b) c) d) e) f) g) h) i) j) k) l) m) n) o) p) q)

8

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Expand the LNBTS object. Select the LNCEL object. Expand the LNRELW object. Set the WCDMA neighbor relation identifier (lnRelWId) parameter's value to a desired value from 0 to 255. Set the Redirect with system information allowed (redirWithSysInfoAllowed) parameter's value to allowed. Set the Target cell Id in UTRAN CGI of related neighbor cell (uTargetCid) parameter's value to a desired value from 0 to 65535. Set the and Target RNC Id (uTargetRncId) parameter's value to a desired value from 0 to 65535. Expand the LNRELW object. Select the Primary PLMN identity in CGI of UTRAN neighbor cell object. Set the MCC, MNC (mcc, mnc) parameters' value to a desired value from 0 to 999. Set the MNC length (mncLength) parameter's value to a desired value from 2 to 3. Select the LNCEL object. Set the Threshold th2 WCDMA for RSRP (threshold2) parameter's value to a desired value from -140 dBm to -43 dBm. Set the Time to trigger for A2 to active WCDMA measurement (a2TimeToTriggerActWcdmaMess) parameter's value to a desired value from a drop-down list.

Optional: If for a certain frequency, UTRAN SI shall be provided in the RRC Connection Release message only in case of a CS fallback or only in case of a redirection with context release, configure the Add UTRAN system information to redirection message (addUtranSIToRedirMsg) parameter in REDRT, or MORED, or MODRED instance. Configuration steps for REDRT instance: a) b) c) d) e)

Issue: 01D

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Expand the LNBTS object. Select the LNCEL object.

DN09185982

101



f) Add the REDRT object. g) Set the Redirection target configuration identifier (redir) parameter's value to a desired value from 0 to 5. h) Set the Add UTRAN system information to redirection message (addUtranSIToRedirMsg) parameter's value to a desired value from a dropdown list. i) Set the RAT for redirection (redirRat) parameter's value to utraFDD. j) Set the Redirection priority for CS fallback with redirection (csFallBPrio) parameter's value to a desired value from 1 to 6 or k) Set the Redirection priority for emergency call (emerCallPrio) parameter's value to a desired value from 1 to 6 or l) Set the Redirection priority for UE context release (redirectPrio) parameter's value to a desired value from 1 to 6. m) Set the UTRA frequency (redirFreqUtra) parameter's value to a desired value from 0 to 16383. Configuration steps for MODRED instance. a) b) c) d) e) f) g) h)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Expand the LNBTS object. Add the MODPR object. Expand the MODPR object. Add the MODRED object. Set the Mobility default profile identifier for redirection (moDRedId) parameter's value to a desired value from 0 to 5. i) Set the Add UTRAN system information to redirection message (addUtranSIToRedirMsg) parameter's value to a desired value from dropdown list. j) Set the RAT for redirection (redirRat) parameter's value to utraFDD. k) Set the Redirection priority for CS fallback with redirection (csFallBPrio) parameter's value to a desired value from 1 to 6 or l) Set the Redirection priority for emergency call (emerCallPrio) parameter's value to a desired value from 1 to 6 or m) Set the Redirection priority for UE context release (redirectPrio) parameter's value to a desired value from 1 to 6. n) Set the UTRA frequency (redirFreqUtra) parameter's value to a desired value from 0 to 16383. Configuration steps for MORED instance. a) b) c) d) e)

102

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Expand the LNBTS object. Add the MOPR object.

DN09185982

Issue: 01D


f) g) h) i) j)

k) l)

m) n) o)

9


Set the Mobility profile identifier (moPrId) parameter's value to a desired value from 1 to 16. Select the MOPR object. Add the MORED object. Set the Mobility default profile identifier for redirection (moRedId) parameter's value to a desired value from 0 to 5. Set the Add UTRAN system information to redirection message (addUtranSIToRedirMsg) parameter's value to a desired value from a dropdown list. Set the RAT for redirection (redirRat) parameter's value to utraFDD. Set the Redirection priority for CS fallback with redirection (csFallBPrio) parameter's value to a desired value from 1 to 6 or Set the Redirection priority for emergency call (emerCallPrio) parameter's value to a desired value from 1 to 6 or Set the Redirection priority for UE context release (redirectPrio) parameter's value to a desired value from 1 to 6. Set the UTRA frequency (redirFreqUtra) parameter's value to a desired value from 0 to 16383.


Expected outcome The LTE1196: RAN Information Management for WCDMA feature has been activated. RIM associations are established and supervised for all RIM-enabled WCDMA neighbour cells.

3.6.3 Deactivating LTE1196: RAN Information Management for WCDMA Before you start The Active RAN Information Management for UTRAN (actRIMforUTRAN) parameter is used for deactivation. Modification of this parameter requires neither eNB restart nor cell locking. Procedure 1


Issue: 01D

DN09185982

103


2

Deactivate the feature flag of the LTE1196: RAN Information Management for WCDMA feature. a) b) c) d)

3


Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Active RAN Information Management for UTRAN (actRIMforUTRAN) parameter's value to false.


Expected outcome The LTE1196: RAN Information Management for WCDMA feature has been deactivated. RIM associations to UTRAN are terminated. The LNADJW:rimStatus instances are disabled. All alarms related to RIM for UTRAN feature are cleared.

3.7 LTE1321: eRAB modification - GBR 3.7.1 Description of LTE1321: eRAB Modification – GBR Introduction to the feature The LTE1321: eRAB Modification – GBR feature enables adapting the bit rate for GBR bearers, based on current needs for resources. This feature is an enhancement of the LTE519: eRAB Modification feature. The feature supports standard GBR bearers (1–4) and operator-defined GBR bearers (128–254). Benefits End-user benefits This feature improves the quality of services, which can be experienced, for example, during conference calls. Operator benefits This feature ensures: •

• •

a dynamic upgrade/downgrade for the GBR bearers, which enables a quality adjustment according to UE/MME needs, especially during inter-technology handovers flexible bandwidth usage adjusted to current eNB, MME, and end-user needs a dynamic GBR bandwidth increase and decrease when starting or terminating a VoLTE call and a three-party conference call

Requirements

104

DN09185982

Issue: 01D



Hardware and software requirements Table 39: Hardware and software requirements presents specific hardware and software requirements for this feature. Table 39


System release


FDD-LTE 15A

FL15A

Flexi Zone Controller

FL15A

OMS

-


-

UE 3GPP R8



FL15A

-

NetAct

MME

NetAct 15.5

-

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview The LTE1321: eRAB Modification – GBR feature introduces functionalities on top of the LTE519: eRAB Modification feature. Before the implementation of the LTE1321: eRAB Modification – GBR feature, the LTE519: eRAB Modification feature allowed, among others, an ARP parameter modification (in the GBR bearer). The LTE1321: eRAB Modification – GBR feature additionally allows the guaranteed bit rate (GBR)-related and maximum bit rate (MBR)-related QoS parameters modification (for the GBR bearers) to facilitate the requirements made by the MME or UE, as presented in Table 40: LTE519 and LTE1321 comparison. Table 40

LTE519 and LTE1321 comparison LTE519

•

•

LTE1321

non-GBR:

•

non-GBR:

–

QCI

–

QCI

–

ARP

–

ARP

–

UE-AMBR

–

UE-AMBR

GBR: –

•

ARP

GBR: –

ARP

–

GBR

–

MBR

In the case of an MBR, the eNB assumes that the value of the MBR equals GBR's value. GBR's modification is triggered by the following network elements: •

Issue: 01D

P-GW In this case, for example, additional resources can be guaranteed for the established bearer.

DN09185982

105


•


HSS In this case, for example, additional resources can be added to an aggregated pool for downloaded data.

P-GW-triggered eRAB modification The procedure is initiated when extra resources are needed to perform an additional service; for example, when a text message is sent during live streaming, the procedure keeps the latter at an unmodified level. In this case, the P-GW sends an UPDATE BEARER REQUEST message to an MME, which initiates the procedure. The MME sends the S1AP: E-RAB MODIFY REQUEST message to the eNB. The eNB analyzes the modification request and decides whether the modification can be handled or not (a standard admission control procedure as if an additional GBR bearer was being established). If any of the parameters for the modification cannot be changed, the whole procedure is rejected. Providing the modification can be performed, the eNB sends an RRC: RRC Connection Reconfiguration message to a UE. Later on confirmations are sent to the eNB, MME and P-GW/HSS. For more details on signaling, see Figure 7: Complete signaling flow. In case the increase in the GBR is not possible, the previous bit rate is configured along with a failure message being sent to the MME. The eRAB modification procedure might involve more than one bearer simultaneously. HSS-triggered eRAB modification This procedure is initiated when the user expends the whole pool of guaranteed resources for data transmission. After exceeding the operator-defined threshold (for example 1 GB), the HSS sends the INSERT SUBSCRIBER DATA message to the MME, which proceeds with the bit rate cut procedure. The MME sends the S1AP: E-RAB MODIFY REQUEST message to an eNB; the remainder of the procedure is the same as in the scenario for P-GW-triggered eRAB modification described above. The end user will now have a treshold value of 1 Mbps, compared to the previous threshold value of 100 Mbps (as a result of exceeding 1 GB transfer). For a more detailed presentation of signaling between the MME and UE, see: Figure 7: Complete signaling flow. Figure 7

Complete signaling flow

System impact

106

DN09185982

Issue: 01D



Interdependencies between features There are interdependancies between the LTE1321: eRAB Modification – GBR feature and the following features: •

•

•

•

•

•

•

• • •

•

g

LTE9: Service Differentiation This feature allows assigning relative scheduling weights to each non-GBR QCI on a cell level. The LTE1321: eRAB Modification – GBR feature can only be activated when the LTE9: Service Differentiation feature is activated. LTE10: EPS Bearers for Conversational Voice The LTE1321: eRAB Modification – GBR feature can modify the parameters for QCI1 bearers introduced by the LTE10: EPS Bearers for Conversational Voice feature. LTE13: Rate Capping The Flexi Multiradio BTS uses the UE-AMBR parameter. The LTE1321: eRAB Modification - GBR feature modifies the UE-AMBR introduced by the LTE13: Rate Capping feature. LTE518: Operator-specific QCIs The LTE1321: eRAB Modification – GBR feature modifies the QoS parameters for operator-specific QCI bearers introduced by the LTE518: Operator-specific QCIs feature. LTE496: Support of QCI 2, 3, and 4 The LTE1321: eRAB Modification – GBR feature can modify parameters for QCI 2, 3, 4 bearers introduced by the LTE496: Support of QCI 2, 3, and 4 feature. LTE497: Smart Admission Control The LTE1321: eRAB Modification - GBR feature can modify the GBR of an EPS bearer, which has already been admitted by admission control (AC). When the ERAB modification is in place, smart admission control mechanisms are triggered to check if such a modification can be done from a resources' point of view. LTE534: ARP-based Admission Control for E-RABs or LTE1231: Operator-specific GBR QCIs The LTE534: ARP-based Admission Control for E-RABs feature is based on ARP priorities, which are considered when a cell is highly loaded. LTE1321: eRAB Modification – GBR feature can change the ARP priority for the already admitted bearers. LTE587: Multiple GBR EPS Bearers per UE LTE519: eRAB Modification LTE1231: Operator-specific GBR QCIs The LTE1321: eRAB Modification - GBR feature can modify parameters for operatorspecific GBR QCIs. LTE1401: Measurement-based TAC Note: It is not allowed to use the LTE534: ARP-based Admission Control for eRABs and LTE1231: Operator-specific GBR QCIs features at the same time. The LTE1321: eRAB Modification - GBR feature is activated along with the LTE519: eRAB Modification feature, using the same activation parameter.

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: 01D

DN09185982

107



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. BTS faults and reported alarms Thera are no BTS faults and reported alarms related to this feature. Measurements and counters Table 41: New counters lists counters introduced with this feature. Table 41


Counter name

Measurement

M8006C237

Failed modification of E-RABs due to "Radio Network Layer Cause - Radio resources not available"

LTE EPS Bearer

M8006C238

Failed modification of E-RABs LTE EPS Bearer due to "Transport Layer Cause - Transport Resource Unavailable"

Key performance indicators There are no key performance indicators related to this feature. Parameters Table 42: Modified parameters lists parameters modified by this feature. Table 42

Modified parameters Full name

Activate E-RAB Modification

Abbreviated name

actERabModify

Managed object LNBTS



ASW

108

License control in network element SW Asset Monitoring

DN09185982


Issue: 01D



3.8 LTE1357: LTE-UTRAN Load Balancing 3.8.1 Description of LTE1357: LTE-UTRAN Load Balancing Introduction to the feature The LTE1357: LTE-UTRAN Load Balancing feature enables load balancing from LTE to WCDMA. Benefits End-user benefits In case of a highly loaded LTE network, optimized service for the end user is provided. Operator benefits The LTE1357: LTE-UTRAN Load Balancing feature reduces the probability of overload situations in the LTE network due to offloading sufficient UEs to the WCDMA network. Requirements Hardware and software requirements Table 44 System release FDD-LTE 15A




OMS -




FL15A

-

NetAct

MME

NetAct 15.5

-

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description With the LTE1357: LTE-UTRAN Load Balancing feature, the eNB monitors the load in its own cells. If a cell load is high, the eNB initiates a load-based handover (HO) from an LTE to a WCDMA cell, as shown in Figure 8: LTE - UTRAN load balancing.

Issue: 01D

DN09185982

109


Figure 8


LTE - UTRAN load balancing

3GCORE eNB

NB

RNC

eNB

LTECORE

Load supervision If the LTE1357: LTE-UTRAN Load Balancing feature is activated (the actUtranLoadBal paramater value is set to true), each cell constantly measures and calculates the load for GBR, non-GBR, and PDCCH load types. The operator can configure new load thresholds for these load types. If at least one of the high load threshold is exceeded, the load balancing function becomes active.

g

Note: Generally, load balancing with inter-RAT targets is started if one of the loadtypes: loadtype1, loadtype2, or loadtype3 is bigger than the relevant typehighthreshold (type1highthreshold, type2highthreshold, or type3highthreshold). Load balancing with inter-RAT targets is stopped if all of the loadtypes: loadtype1, loadtype2, and loadtype3 are smaller than the relevant typetargetthreshold (type1targetthreshold, type2targetthreshold, and type3targetthreshold). If the load of all load types in the source LTE cell is reduced below the target threshold, all load balancing is stopped in that cell. Load balacing is in an inactive state, and the load monitoring is ongoing. Load balancing candidates The UE, to be handed over from an LTE to a WCDMA cell, must be a load balancing candidate (UE entering the cell, UE in an RRC connected state (every time when the periodic retry timer of the UE expires), or UE coming in with an HO) and meet the following conditions: • • • • • •

The UE has UTRAN UE capabilities (feature group index bit 15 and 114 optionally). The UE has data bearers only (no QCI1 bearer). An emergency bearer is not active. The UE is not configured for carrier aggregation. The UE has the B1 measurement objects configured. The UE reports sufficient coverage with WCDMA.

The load balancing candidate measures the radio conditions of the WCDMA target cells using the B1 measurement. LTE-WCDMA handover

110

DN09185982

Issue: 01D



If the S1 handover is triggered for inter-RAT load balancing, the source eNB sets the Cause IE value to Reduce load in serving cell. As long as load balancing handovers are accepted, the WCDMA cell is a target cell for load balancing. If the WCDMA target cell rejects load balancing handovers (cause: No Radio Resources Available in Target Cell or load reject reasons), the target cell is temporarily blacklisted for load balancing. In this case, no further load is shifted to that cell. The eNB allocates a load-balancing handover target list to WCDMA. This target cell list is taken from the newly-defined white list for load balancing. System impact Interdependencies between features •

•

•

•

LTE56: Inter-RAT Handover to UTRAN The LTE56: Inter-RAT Handover to UTRAN feature must be activated together with the activation of load balancing. LTE1073: Measurement-based Redirect to UTRAN The LTE1073: Measurement-based Redirect to UTRAN feature must not be configured to apply redirect to all UEs if the LTE1357: LTE-UTRAN Load Balancing feature is activated. LTE736: CS Fallback to UTRAN The CS fallback reduces load independently of the LTE1357: LTE-UTRAN Load Balancing feature. If one of the following features is activated along with the LTE1357: LTE-UTRAN Load Balancing feature, a round robin offloading might be done (either B1 or A4 is configured for a candidate UE). – – – –

•

LTE1841: Inter-frequency Load Equalization If the LTE1841: Inter-frequency Load Equalization and LTE1357: LTE-UTRAN Load Balancing features are activated parallel to one another, a round robin might be done (either B1 or A4 is configured for a candidate UE). A proposal of how to configure several load balancing functions in parallel is as follows: – – –

• •

•

Issue: 01D

LTE1170: Inter eNB IF Load Balancing LTE1387: Intra eNB IF Load Balancing LTE1531: Inter-frequency Load Balancing Extension LTE1140: Intra eNB IF Load Balancing

low load in the cell - execution of load equalization higher load in the cell - execution of the LTE1170: Inter eNB IF Load Balancing feature much higher load in the cell - execution of the LTE1357: LTE-UTRAN Load Balancing feature

LTE1749: MRO Inter-RAT UTRAN MRO adapts thresholds for an inter-RAT HO. LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness, LTE908: ANR Inter-RAT UTRAN - Fully UE-based The ANR features and the LTE1357: LTE-UTRAN Load Balancing feature are mutually exclusive because of set up measurements. It must be avoided that ANR deletes all UTRAN neighbor cells because then UTRAN load balancing cannot reduce the load immediately after the highload is triggered. LTE2162: SRVCC for Network Deployments Not Supporting PS HO

DN09185982

111


•

•


A UE which is sent to UTRAN by a measurement-based redirect, instead of a PS HO, is not used for inter-RAT load balancing. If the LTE1357: LTE-UTRAN Load Balancing feature is activated, the LTE2162: SRVCC for Network Deployments Not Supporting PS HO feature does not have to be configured to send all UEs without QCI1 to UTRAN by redirect. LTE497: Smart Admission Control There are dependencies between the load balancing thresholds and the maxGbrTrafficLimit smart AC threshold. The thresholds should be configured that the load balancing starts first before the congestion handling is started. LTE1103: Load-based Power Saving for Multi-layer Networks Load balancing and energy saving functions might work in opposite direction, depending on traffic distribution. The recommendation is that the LTE1103: Loadbased Power Saving for Multi-layer Networks and LTE1357: LTE-UTRAN Load Balancing features are not used at the same time.

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 The LTE cells are offloaded due to a unidirectional load balancing mechanism between LTE and UTRAN cells. Management data Alarms There are no alarms related to this feature. Measurements and counters Table 45: New counters lists counters introduced with this feature. Table 45


Counter name

Measurement

M8016C43

Inter System load balancing handover attempts to UTRAN


M8016C44

Successful Inter System load balancing handover completions to UTRAN


M8011C162

High cell load indicator for load 8011 - LTE Cell Resource balancing to UTRAN (WBTS)

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

112

DN09185982

Issue: 01D


Table 46


New parameters

Full name

Abbreviated name

Managed object

Structure

Activate inter-RAT UTRAN load balancing

actUtranLoadBal

LNBTS

-

UTRAN balancing load thresholds

utranLbLoadThreshold LNCEL s

-

DL GBR resource high highLoadGbrDl load

LNCEL

utranLbLoadThreshold s

DL non-GBR resource highLoadNonGbrDl high load

LNCEL


PDCCH high load

highLoadPdcch

LNCEL


EcN0 threshold for load bal. handover to UTRAN

thresholdEcn0UtranLb LNHOW Filter

-

RSCP threshold for load bal. handover to UTRAN

thresholdRscpUtranLb LNHOW Filter

-

LTE-UTRAN load balancing allowed

utranLbAllowed

-

LNRELW



Full name

Issue: 01D

Abbreviated name

Managed object

Structure

Activate handover from LTE to WCDMA

actHOtoWcdma

LNBTS

-

Prohibit Load based handover timer

prohibitLBHOTimer

LNBTS

-

Prohibit PS-HO to WCDMA

prohibitPsHOtoWcdma LNBTS

-

Cell resource sharing mode

cellResourceSharingM LNCEL ode

-

Filtering coefficient used for cpich ecN0

filterCoefficientCpichE cn0

LNCEL

-

Filtering coefficient used for cpich RSCP

filterCoefficientCpichR scp

LNCEL

-

Inter-frequency load balancing load thresholds

iFLBLoadThresholds

LNCEL

-

Inter-frequency load balancing QCI1 Bearer check timer

iFLBBearCheckTimer

LNCEL

iFLBLoadThresholds

Inter-frequency load balancing GBR high load DL

iFLBHighLoadGBRDL

LNCEL

iFLBLoadThresholds

DN09185982

113


Table 47



Full name

Abbreviated name

Managed object

Structure

Inter-frequency load balancing non-GBR high load DL

iFLBHighLoadNonGB RDL

LNCEL

iFLBLoadThresholds

Inter-frequency load balancing PDCCH high load

iFLBHighLoadPdcch

LNCEL

iFLBLoadThresholds

Inter Freq Load Bal Retry Timer

iFLBRetryTimer

LNCEL

iFLBLoadThresholds

Intra- and inter-freq. loadSettings load bal. common load settings

LNCEL

-

Cell capacity class value

cellCapClass

LNCEL

loadSettings

Mode for calculating the CAC in load bal. and eICIC

mlbEicicOperMode

LNCEL

loadSettings

Nominal number of PRBs for load balancing

nomNumPrbNonGbr

LNCEL

loadSettings

DL GBR resource target load

targetLoadGbrDl

LNCEL

loadSettings

DL non-GBR resource targetLoadNonGbrDl target load

LNCEL

loadSettings

PDCCH target load

targetLoadPdcch

LNCEL

loadSettings

Uplink CAC source selection

ulCacSelection

LNCEL

loadSettings

Static CAC for uplink

ulStaticCac

LNCEL

loadSettings

Remove allowed

removeAllowed

LNRELW

-



ASW



3.8.2 Activating and configuring LTE1357: LTE-UTRAN Load Balancing Before you start Table 49: Parameters used for activating and configuring LTE1357: LTE-UTRAN Load Balancing lists parameters for the activation and configuration of the LTE1357: LTEUTRAN Load Balancing feature.

114

DN09185982

Issue: 01D


Table 49


Parameters used for activating and configuring LTE1357: LTE-UTRAN Load Balancing Parameter

Purpose


Activate inter-RAT UTRAN load balancing (actUtranLoadBal)

activation flag

no

UTRAN balancing load thresholds (utranLbLoadThresholds) parameters' structure


no

Inter-frequency load balancing load mandatory configuration thresholds (iFLBLoadThresholds) parameters' structure

no

Activate handover from LTE to WCDMA (actHOtoWcdma)


no

Prohibit Load based handover timer (prohibitLBHOTimer)


no

Prohibit PS-HO to WCDMA (prohibitPsHOtoWcdma)


no

Cell resource sharing mode (cellResourceSharingMode)


object locking

Filtering coefficient used for cpich ecN0 (filterCoefficientCpichEcn0)


no

Filtering coefficient used for cpich RSCP (filterCoefficientCpichRscp)


no

Intra- and inter-freq. load bal. common load settings (loadSettings) parameters' structure


no

EcN0 threshold for load bal. handover to UTRAN (thresholdEcn0UtranLbFilter)


no

RSCP threshold for load bal. handover to UTRAN (thresholdRscpUtranLbFilter)


no

LTE-UTRAN load balancing allowed (utranLbAllowed)


no

Remove allowed (removeAllowed)


no

The LTE56: Inter-RAT Handover to UTRAN feature needs to be activated (actHOtoWcdma=true) before activation of the LTE1357: LTE-UTRAN Load Balancing feature. The LTE1073: Measurement-based Redirect to UTRAN feature needs to be deactivated before activation of the LTE1357: LTE-UTRAN Load Balancing feature.

Issue: 01D

DN09185982

115



Procedure 1


2

Activate the LTE1357: LTE-UTRAN Load Balancing feature. a) b) c) d)

3

Configure the LNADJW parameters. a) b) c) d) e)

4

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate inter-RAT UTRAN load balancing (actUtranLoadBal) parameter's value to true.

Right-click the LNBTS object. Select the New LNADJW object. For the LNADJW object, set the parameters' values. Expand the LNADJW object. For the Target primary PLMN identity parameters' structure, set the parameters' values.

Configure the UTRAN balancing load thresholds parameters' structure. a) b) c) d)

Expand the LNBTS object. Right-click the LNCEL object. Select the New UTRAN balancing load thresholds object. For the UTRAN balancing load thresholds parameters' structure, set the parameters' values as follows: •

g

Note: The DL GBR resource target load (targetLoadGbrDl) parameter's value in the Intra- and inter-freq. load bal. common load settings (loadSettings) parameters' structure needs to be lower than or equal to the DL GBR resource high load (highLoadGbrDl) parameter in the UTRAN balancing load thresholds (utranLbLoadThresholds) parameters' structure. • •

116

DL GBR resource high load (highLoadGbrDl)

DL non-GBR resource high load (highLoadNonGbrDl) PDCCH high load (highLoadPdcch)

DN09185982

Issue: 01D


5

Configure the Intra- and inter-freq. load bal. common load settings parameters' structure. a) b) c) d)

6

Expand the LNBTS object. Right-click the LNCEL object. Select the New Intra- and inter-freq. load bal. common load settings object. For the Intra- and inter-freq. load bal. common load settings parameters' structure, set the parameters' values.

Configure the Inter-frequency load balancing load thresholds parameters' structure. a) b) c) d)

Expand the LNBTS object. Right-click the LNCEL object. Select the New Inter-frequency load balancing load thresholds object. For the Inter-frequency load balancing load thresholds parameters' structure, set the parameters' values as follows: • • • • •

7


Inter Freq Load Bal Retry Timer (iFLBRetryTimer) Inter-frequency load balancing GBR high load DL (iFLBHighLoadGBRDL) Inter-frequency load balancing non-GBR high load DL (iFLBHighLoadNonGBRDL) Inter-frequency load balancing PDCCH high load (iFLBHighLoadPdcch) Inter-frequency load balancing QCI1 Bearer check timer (iFLBBearCheckTimer)

Configure the other LNBTS parameters (optional). a) Select the LNBTS object. b) Set the parameters' values as follows: • •

8

Prohibit Load based handover timer (prohibitLBHOTimer) Prohibit PS-HO to WCDMA (prohibitPsHOtoWcdma)

Configure the other LNCEL parameters (optional). a) Expand the LNBTS object. b) Select the LNCEL object. c) Set the parameters' values as follows: •

Issue: 01D

Cell resource sharing mode (cellResourceSharingMode)

DN09185982

117


g

Note: For the cellResourceSharingMode different that none, set additional parameters as follows: – –

– –

–

• • •

9


Assigned cell resource group profile (cellResourceGroupPrId) LNCEL parameter 1. Right-click the LNBTS object. 2. Select the New CRGPR object. 3. For the CRGPR object, set the parameters' values. Set the Activate downlink interference shaping (actDlIntShaping) LNBTS parameter's value to false. Set the DL interference shaping active (actDlIsh) parameter's value in the Downlink interference shaping configuration (dlIshConfig) parameters' structure to false. Set the Activate inter-RAT UTRAN load balancing (actUtranLoadBal) LNBTS parameter's value to false.

Filtering coefficient used for cpich ecN0 (filterCoefficientCpichEcn0) Filtering coefficient used for cpich RSCP (filterCoefficientCpichRscp) Intra- and inter-freq. load bal. common load settings (loadSettings) parameters' structure

Configure the LNHOW parameters (optional). a) Right-click the LNCEL object. b) Select the New LNHOW object. c) For the LNHOW object, set the parameters' values as follows: • • • •

EcN0 threshold for load bal. handover to UTRAN (thresholdEcn0UtranLbFilter) RSCP threshold for load bal. handover to UTRAN (thresholdRscpUtranLbFilter) Neighbor WCDMA BTS cell handover identifier (lnHoWId) UTRAN carrier frequency (utraCarrierFreq)

10 Configure the LNRELW parameters (optional). a) Right-click the LNCEL object. b) Select the New LNRELW object. c) For the LNRELW object, set the parameters' values as follows: • •

118

LTE-UTRAN load balancing allowed (utranLbAllowed) Remove allowed (removeAllowed)

DN09185982

Issue: 01D


• • • •


WCDMA neighbor relation identifier (lnRelWId) Target cell Id in UTRAN CGI of related neighbor cell (uTargetCid) Target RNC Id (uTargetRncId) 1. Expand the LNRELW object. 2. For the Primary PLMN identity in CGI of UTRAN neighbor cell (plmnId) parameters' structure, set the parameters' values.


Expected outcome • •

The LTE1357: LTE-UTRAN Load Balancing feature is activated. The eNB starts CAC monitoring in all its cells.

3.8.3 Deactivating LTE1357: LTE-UTRAN Load Balancing Before you start The Activate inter-RAT UTRAN load balancing (actUtranLoadBal) parameter is used for deactivation. Modification of this parameter requires neither eNB restart nor cell locking. Procedure 1


2

Deactivate the LTE1357: LTE-UTRAN Load Balancing feature. a) b) c) d)

Issue: 01D

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate inter-RAT UTRAN load balancing (actUtranLoadBal) parameter's value to false.

DN09185982

119


3



Expected outcome The LTE1357: LTE-UTRAN Load Balancing feature is deactivated.

3.9 LTE1635: SIB8 AC barring for 1xRTT 3.9.1 Description of LTE1635: SIB 8 AC Barring for 1xRTT Introduction to the feature The LTE1635: SIB 8 AC Barring for 1xRTT feature supports the dedicated access class (AC) barring for 1xRTT as an extension of LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB). The 1xRTT AC barring information is broadcast as part of system information block 8 (SIB8). Benefits End-user benefits This feature provides an equally effective access bar as the one in a native network during CS fallback. Operator benefits This feature guarantees CS services without the expense of deploying an IMS core and VoIP applications. Requirements Hardware and software requirements Table 50


System release FDD-LTE 15A

FL15A



OMS -



FL15A

NetAct -


MME -

SAE GW -

Functional description The LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature is deployed in the LTE network and CDMA2000 1xRTT network in the same geographical area, where the 1xRTT network always has overlapping coverage with the LTE network. In a situation when the 1xRTT network conditions are overloaded, it is reasonable to relieve it by managing the native 1xRTT layer.

120

DN09185982

Issue: 01D



The 1xRTT AC barring information is broadcast as part of system information block 8 (SIB8) to the UEs. Parameters for 1xRTT AC barring are operator-configurable. The eNB supports adapting SIB8 1xRTT AC barring broadcast on the air interface, based on the combination of: • •

the SIB8 1xRTT AC barring O&M configuration value the SIB2:ac-BarringInfo IE value

The algorithm of ac-Barring0To9-r9 IE adaption, based on SIB2 AC barring information, is not applied if acBarring0To9Adapt = false. The acBarring0To9-r9 IE of SIB8 should be set as RttAcbDb. Otherwise, the algorithm of ac-Barring0To9-r9 IE adaption, based on SIB2 AC barring information, is applied. The RttAcbDb factor is a source one, expected by the operator of the CDMA AC barring pass rate in CDMA 1xRTT native network. In case of static 1xAC barring, the RttAcbDb = CDFIM:rttAcBar:acBarring0To9 or in case of automatic 1xAC barring, CDFIM:rttAcBarOvl:acBarring0To9. The 1xACB adaption is applicable for both static AC barring and automatic AC barring for overload.

g

Note: RttAcbDb = 0 means that the operator expects the CDMA AC barring pass rate equal 100% for the CDMA access overload class 0-9 native 1xRTT network. There is no need to enforce any extra LTE SIB8 AC barring.

RttAcbDb = 63 means that the operator expects the CDMA AC barring pass rate equal 0% for the CDMA access overload class 0-9 native 1xRTT network. Because SIB8 1xRTT AC barring will only apply to UE's that have successfully accessed the LTE network, and SIB2 LTE AC barring may prevent some accessing, this can result in a higher overall 1xRTT barring than the customer might desire. The purpose of Adaption is to adjust the barring factors in SIB8 slightly based on how much SIB2 barring is in effect, to give the customer the same overall 1xRTT AC barring they would see on the native 1xRTT system with the same 1xRTT database settings. In the LTE1635: SIB 8 AC Barring for 1xRTT feature, when a UE is in R8/R9 1xCSFB mode access 1xRTT network via LTE access the LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature, during 1xCSFB, 1xSMS, 1xRegistration and others, will follow both SIB8 AC barring and SIB2 AC barring. System impact Interdependencies between features Activation of the LTE1635: SIB 8 AC Barring for 1xRTT feature is meaningful only when the LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature is activated, and SIB8 CSFB-RegistrationParam1xRTT IE is broadcast. When a UE is in R8/R9 e1xCSFB mode, access the 1xRTT network via the LTE network; the SIB8 AC barring is following together with SIB2 AC barring. The LTE1635: SIB 8 AC Barring for 1xRTT feature is not supported by the following features: •

Issue: 01D

LTE874: DualRx 1xCSFB SIB8 AC barring is not applicable the DualRx 1xCSFB since there is no interworking between the LTE/EPC network and 1XRTT network.

DN09185982

121


g


Note: When a UE is in DualRx, 1xCSFB mode triggers EMM:Extended Service Request for CS fallback; then, only SIB2 AC barring will be followed while SIB8 AC Barring will be skipped. •

•

LTE116: Cell Bandwidth - 3 MHz SIB8 AC barring is not supported on the 3MHz LTE cell bandwidth since the LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature is not supported on the 3MHz LTE cell bandwidth. LTE117 Cell Bandwidth - 1.4 MHz SIB8 AC barring is not supported on the 1.4MHz LTE cell bandwidth since the LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature is not supported on the 1.4MHz LTE cell bandwidth.

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 51: New parameters lists new parameters introduced with this feature. Table 51

New parameters

Full name

122

Abbreviated name

Managed object

Structure

AC barring 0To9 adaption

acBarring0To9Adapt

CDFIM

-

AC barring for CDMA2000 1xRTT

rttAcBar

CDFIM

-

AC barring factor for overload classes 0 to 9

acBarring0To9

CDFIM

rttAcBar

AC barring factor for overload class 10

acBarring10

CDFIM

rttAcBar


acBarring11

CDFIM

rttAcBar


acBarring12

CDFIM

rttAcBar


acBarring13

CDFIM

rttAcBar


acBarring14

CDFIM

rttAcBar


acBarring15

CDFIM

rttAcBar

DN09185982

Issue: 01D


Table 51



Full name

Abbreviated name

Managed object

Structure

AC barring factor for emergency

acBarringEmg

CDFIM

rttAcBar

AC barring modification factor for message

acBarringMsg

CDFIM

rttAcBar

AC barring modification factor for registration

acBarringReg

CDFIM

rttAcBar

Sales information Table 52: Sales information lists sales information about this feature. Table 52



ASW

SW asset monitoring


3.9.2 Activating and configuring LTE1635: SIB 8 AC Barring for 1xRTT Before you start Table 53: Parameters used for activating and configuring LTE1635: SIB 8 AC Barring for 1xRTT lists parameters used for activation and configuration of the LTE1635: SIB 8 AC Barring for 1xRTT feature. Table 53

Parameters used for activating and configuring LTE1635: SIB 8 AC Barring for 1xRTT Parameter

Issue: 01D

Purpose


AC Barring for CDMA2000 1xRTT (rttAcBar)

activation flag

no

AC Barring 0To9 adaptation (acBarring0To9Adapt)


no

AC Barring factor for overload classes 0 to 9 (acBarring0To9)


no

AC Barring factor for emergency (acBarringEmg)


no

AC Barring factor for overload classes 10 (acBarring10)


no



no



no



no

DN09185982

123


Table 53


Parameters used for activating and configuring LTE1635: SIB 8 AC Barring for 1xRTT (Cont.) Parameter

Purpose




no



no

AC Barring modification factor for message (acBarringMsg)


no

AC Barring modification factor for registration (acBarringReg)


no

The LTE1441 Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature needs to be activated before the activation of the LTE1635: SIB 8 AC Barring for 1xRTT feature. To activate the feature, do the following: Procedure 1


2

Activate the feature flag of the LTE1635: SIB 8 AC Barring for 1xRTT feature. a) b) c) d) e) f) g)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Expand the LNBTS object. Select the LNCEL object. Select the CDFIM object. Set the AC Barring 0To9 adaptation (acBarring0To9Adapt) parameter's value to true or false. h) If the AC Barring 0To9 adaptation (acBarring0To9Adapt) parameter's value is set to true, do the following: • • •

•

124

Select the LNCEL object. Add the Access class barring for originating calls (acBarOc) parameter. Set the Access class barring time for originating calls (ocAcBarTime) parameter's value to a desired value from a dropdown list. Set the Access probability factor for originating calls(ocAcProbFac) parameter's value to a desired value from a dropdown list.

DN09185982

Issue: 01D



i) Select the CDFIM object. j) Add the AC Barring for CDMA2000 1xRTT (rttAcBar) object. k) Set the AC Barring factor for overload classes 0 to 9 (acBarring0To9) parameter's value to a desired value from 0 to 63.

g

Note: It is also possible to set the

AC Barring factor for overload classes 0 to 9 (acBarring0To9) parameter's value by expanding the AC Barring for CDMA2000 1xRTT object.

3

Optional: Change parameters' default value of the CDFIM:rttAcBar instance. a) If it is necessary, change the value of listed parameters: • • • • • • •

• •

4

the AC Barring factor for overload classes 10 (acBarring10) parameter's value to a desired value from 0 to 7. the AC Barring factor for overload classes 11 (acBarring11) parameter's value to a desired value from 0 to 7. the AC Barring factor for overload classes 12 (acBarring12) parameter's value to a desired value from 0 to 7. the AC Barring factor for overload classes 13 (acBarring13) parameter's value to a desired value from 0 to 7. the AC Barring factor for overload classes 14 (acBarring14) parameter's value to a desired value from 0 to 7. the AC Barring factor for overload classes 15 (acBarring15) parameter's value to a desired value from 0 to 7. the AC Barring modification factor for message (acBarringMsg) parameter's value to a desired value from 0 to 7. the AC Barring factor for emergency (acBarringEmg) parameter's value to a desired value from 0 to 7. the AC Barring modification factor for registration (acBarrinReg) parameter's value to a desired value from 0 to 7.


Expected outcome The validation of the configuration plan file is successfully done; the LTE1635: SIB 8 AC Barring for 1xRTT feature is activated. Further information A warning will be issued if any of the parameters of the CDFIM:rttAcBar structure or acBarring0To9Adapt parameter are changed, which results in that SIB1 systemInfoValueTag changes more than 31 times in three hours.

Issue: 01D

DN09185982

125



3.9.3 Deactivating LTE1635: SIB 8 AC Barring for 1xRTT Before you start To deactivate the LTE1635: SIB 8 AC Barring for 1xRTT feature, the LNBTS:act1xCsfb has to be set as true, at least one LNCEL:rttCsfbType instance is not set as forbidden, and the CDFIM:rttAcBar with its mandatory parameters is configured. The AC Barring for CDMA2000 1xRTT (rttAcBar) parameter is used for deactivation. Modification of this parameter requires neither eNB restart nor cell locking. To deactivate the feature, do the following: Procedure 1


2

Deactivate the feature flag of the LTE1635: SIB 8 AC Barring for 1xRTT feature. a) b) c) d) e) f) g) h)

g

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Expand the LNBTS object. Select the LNCEL object. Expand the LNCEL object. Expand the CDFIM object. Delete the rttAcBar instance. Note: The CDFIM:rttAcBar structure and its mandatory parameters can be modified online, which means the activation of this delta plan will not cause a service outage in case the configuration plan file contains only these parameters.


Expected outcome The validation of the configuration plan file is successfully done; the LTE1635: SIB 8 AC Barring for 1xRTT feature is deactivated.

126

DN09185982

Issue: 01D



3.10 LTE1679: DRX with Parallel UE Measurement Gaps 3.10.1 Description of LTE1679: DRX with Parallel UE Measurement Gaps Introduction to the feature The LTE1679: DRX with Parallel UE Measurement Gaps feature allows using discontinuous reception (DRX) for a UE when a measurement gap is installed. The objective of this feature is to increase a UE's battery savings. Benefits End-user benefits This feature increases a UE's battery savings achieved by using DRX during the time when a measurement gap is installed. Operator benefits This feature is operator-modifiable, but it has no direct impact on the operator's actions. Requirements Hardware and software requirements Table 54



Flexi Multiradio BTS FL15A


OMS

-

-

Flexi Multiradio 10 BTS FL15A UE

3GPP R8 mandatory


NetAct NetAct 15.5

Flexi Zone Access Point -

MME

SAE GW

-

-

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview The LTE1679: DRX with Parallel UE Measurement Gaps feature is an extension of the LTE42: Support of DRX in RRC Connected Mode feature that introduced the support of DRX in a CONNECTED mode. It brought an eNB's support for discontinuous monitoring of the DL control channel (PDCCH) by the UE (DRX). This solution employed a periodic active/sleep pattern, thus creating phases where the UE is not able to receive or transmit data instantaneously. For more information about the support of DRX in an RRC connected mode, see LTE42: Support of DRX in RRC Connected Mode. The solutions in both of the features allow increasing a UE's battery lifetime. Maximum power savings are expected for a very bursty kind of traffic patterns (short phases with data followed by long phases with no data at all) and very long inactivity time, however, at the expense of increasing the DL latency (at the start of a downlink data transmission).

Issue: 01D

DN09185982

127


g


Note: The LTE1679: DRX with Parallel UE Measurement Gaps feature can be enabled only if the LTE42: Support of DRX in RRC Connected Mode feature is enabled. The description of this feature comprises the following: • • • •

Measurement gaps in DRX mode Measurement gap installation Alignment of measurement gaps DRX/measurement gaps activation rules

Measurement gaps in DRX mode The LTE1679: DRX with Parallel UE Measurement Gaps feature allows the UE to use the DRX in parallel with measurement gaps. However, the following constraints are brought: •

• •

g

The only supported DRX profiles during measurement gaps are the drxProfile2, drxSmartProfile2, or drxProfile1. No other DRX profile is supported during measurement gaps. With the activation of the UE measurement gaps, the drxProfile2 or drxSmartProfile2 are considered regardless whether a bearer with QCI 1 has been established or not. If there is a bearer mapping to drxProfile1 and the drxProfile1 has a higher priority than drxProfile2/drxSmartProfile2, then the drxProfile1 is activated. The "normal DRX profile selection" is applied again when the UE measurements are deactivated. Only the 40ms-measurement gaps are supported. The DRX has to be turned off during the circuit-switched fallback (CSFB) to minimize the delay on the RRC interface. Therefore, CSFB-triggered measurement gaps are excluded and, upon installing the CSFB measurement gap, DRX is turned off via RRC messaging to the UE. Note: In this feature description, the term "measurement gap" refers to non-CSFB measurement gaps.

Measurement gap installation Upon installing a measurement gap, when the LTE1679: DRX with Parallel UE Measurement Gaps feature is enabled, the drxProfile2, drxSmartProfile2, or drxProfile1 is used for a UE. The measurement gap offset calculation algorithm, introduced by this feature, is used to switch the DRX profile when the measurement gap is installed and to calculate the new DRX offset. The measurement gap offset is selected in such a way that the DL scheduling gap caused by the measurement gap does not overlap with the DRX On duration time. In some cases, it is impossible to meet such a criterion, and then the overlap is minimized. The measurement gap offset calculation algorithm is used even if the DRX is not utilized during the measurement gap time, or even if the LTE1679: DRX with Parallel UE Measurement Gaps feature is disabled. The installation of the measurement gap as well as the DRX profile change (if applicable) are communicated to the UE via RRC. Upon uninstalling the measurement gaps at a UE, the eNB shall re-select the DRX profile as "normal," which means without enforcing the drxProfile2/drxSmartProfile2 in the DRX selection algorithm. Alignment of measurement gaps

128

DN09185982

Issue: 01D



It is required to align the measurement gaps with the potential occasions of the scheduling requests so that not all of those occasions are blanked continously. Consequently, an alignment is required whenever the periodicity is the same or different for a scheduling request and measurement gap. DRX/measurement gaps activation rules When the DRX and measurement gaps compete, and the LTE1679: DRX with Parallel UE Measurement Gaps feature is activated, the eNB proceeds as follows: •

•

If the measurement gaps are already enabled and the DRX profile needs to be set up at the UE, the eNB releases the measurement gaps and sets the DRX profile if and only if the DRX is required for resolving the cell identity of a target cell for a handover, or the measurements which are currently using the gaps are not eventbased. Otherwise, measurement gaps are always kept. When the conditions for keeping the measurement gaps or the DRX profile end, the eNB evaluates whether to set up another DRX profile or measurement gaps, depending on the actual RRC connection status.

System impact Interdependencies between features The following feature has to be enabled before the activation of the LTE1679: DRX with Parallel UE Measurement Gaps feature: •

LTE42: Support of DRX in RRC Connected Mode

The following features do not cooperate with the LTE1679: DRX with Parallel UE Measurement Gaps feature: • •

LTE736: CS Fallback to UTRAN LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB)

The LTE1679: DRX with Parallel UE Measurement Gaps feature allows the DRX to be considered during non-CSFB measurement gaps. During CSFB measurement gaps, the DRX has to be disabled. The following features cooperate with the LTE1679: DRX with Parallel UE Measurement Gaps feature: • • •

LTE56: Inter RAT Handover to WCDMA LTE55: Inter-frequency Handover LTE442: Network Assisted Cell Change to GSM

The features utilize the measurement gaps. Previously, the DRX had to be disabled when a measurement gap was installed. The LTE1679: DRX with Parallel UE Measurement Gaps feature removes this restriction so that the DRX can potentially stay enabled during the time when a measurement gap is installed in the UE. Impact on interfaces This feature has no impact on interfaces. Impact on system performance and capacity This feature has no impact on system performance or capacity. Management data

Issue: 01D

DN09185982

129



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 55: New parameters lists new parameters related to this feature. Table 55

New parameters Full name

Activate DRX during measurement gap

Abbreviated name actDrxDuringMeasGap




Activate DRX

Abbreviated name actDrx




ASW



3.10.2 Activating and configuring LTE1679: DRX with Parallel UE Measurement Gaps Before you start The Activate DRX during measurement gap (actDrxDuringMeasGap) parameter is used to activate the LTE1679: DRX with Parallel UE Measurement Gaps feature. Modification of this parameter requires neither an eNB restart nor cell locking. The following features have to be enabled before the activation of the LTE1679: DRX with Parallel UE Measurement Gaps feature: •

130

LTE42: Support of DRX in RRC Connected Mode

DN09185982

Issue: 01D


Table 58


Parameters used for activating and configuring LTE1679: DRX with Parallel UE Measurement Gaps Parameter

Purpose


Activate DRX during measurement activation flag gap (actDrxDuringMeasGap)

no

Activate DRX (actDrx)

no


Procedure 1


2

Activate the LTE1679: DRX with Parallel UE Measurement Gaps feature. a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Select the LNCEL object corresponding to the cell where the LTE1679: DRX with Parallel UE Measurement Gaps feature is being activated. e) Set the Activate DRX (actDrx) parameter to true. f) Set the Activate DRX during measurement gap (actDrxDuringMeasGap) parameter to true.

3


Expected outcome The LTE1679: DRX with Parallel UE Measurement Gaps feature is activated and allows using discontinuous reception (DRX) for a UE when a measurement gap is installed.

3.10.3 Deactivating LTE1679: DRX with Parallel UE Measurement Gaps Before you start The Activate DRX during measurement gap (actDrxDuringMeasGap) parameter is used to deactivate the LTE1679: DRX with Parallel UE Measurement Gaps feature. Modification of this parameter requires neither an eNB restart nor cell locking.

Issue: 01D

DN09185982

131



Procedure 1


2

Deactivate the LTE1679: DRX with Parallel UE Measurement Gaps feature. a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Select the LNCEL object corresponding to the cell where the LTE1679: DRX with Parallel UE Measurement Gaps feature is being deactivated. e) Set the Activate DRX during measurement gap (actDrxDuringMeasGap) parameter to false.

3


Expected outcome The LTE1679: DRX with Parallel UE Measurement Gaps feature is deactivated.

3.11 LTE1788: Automatic Access Class Barring 3.11.1 Description of LTE1788: Automatic Access Class Barring Introduction to the feature The LTE1788: Automatic Access Class Barring feature provides an automatic access class (AC) barring for cells that enter a high control plane load. The feature is an enhancement of the LTE1047: Control Plane Overload Handling feature. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature: • • •

132

reduces the number of rejected RRC connection requests during a persistently high control plane load, thus improving the call setup success rate (CSSR). ensures that an eNB in an overload state will not stop working as a result of applying automatic AC barring procedures. improves the stability of an eNB and RAN in a certain area as a result of fast counter actions in the overload 2 (OVL2) state.

DN09185982

Issue: 01D








FL15A

OMS -

UE 3GPP R8


FL15A

-

NetAct

MME

-

-

SAE GW -

Additional hardware requirements This feature does not require any new or additional hardware. Functional description Functional overview The LTE1788: Automatic Access Class Barring feature is an enhancement of the LTE1047: Control Plane Overload Handling feature. The LTE1788: Automatic Access Class Barring feature brings an additional value to the OVL2 state of the LTE1047: Control Plane Overload Handling feature. The feature performs the AC barring for the control-plane signaling when an eNB remains in the OVL2 state for an operatorconfigurable time. Automatic AC barring is also applied to 1xRTT, which is contained in SIB8. AC barring is applicable to the following services: • • • • • •

mobile-originating data mobile-originated signaling Service Specific Access Control (SSAC) for voice SSAC for video circuit-switched fallback (CSFB) to UTRA/GSM 1xCSFB to CDMA

Operational description The feature is triggered when an eNB remains in OVL2 for an operator-configurable time period. The time period is set by the Automatic AC Barring start timer (autoAcBarringStartTimer) parameter. The timer is started immediately after the cell enters the OVL2 state. When triggered, the feature starts an automatic AC barring for SIB2 and (if configured) SIB8. This means that all signaling that meets the configured criteria will not be admitted. At the same time, when the feature is triggered, the TIME_AC_BAR_OVL (Aggregated time period of automatic class class barring due to overload) counter is run. When the eNB goes back to the OVL0 state, the Automatic AC Barring stop timer (autoACBarringStopTimer) timer is started. If the base station does not go back to the OVL2 state within that time frame, the automatic AC barring functionality as well as the TIME_AC_BAR_OVL (Aggregated time period of automatic access class barring

Issue: 01D

DN09185982

133



due to overload) counter are turned off. After that, the static access class barring is applied, if configured. In case there is no static AC barring configured, no AC barring is applied in the eNB. After leaving the OVL2 state when the static AC barring is activated, the parameters (mandatory in the case of automatic AC barring) configured for the automatic AC barring (for example AC barring for signaling OVL (acBarSigOvl), AC barring for originating calls OVL (acBarOcOvl), or AC Barring for CDMA2000 1xRTT OVL (rttAcBarOvl)) are ignored. The frequent switch between automatic AC barring applied and not applied along with the C-plane overload level change might trigger a frequent SIB2/SIB8 AC barring-related system information change. This might cause a systemInfoValueTag overflow (the systemInfoValueTag changes more than 31 times within three hours). To avoid the overflow solely due to the LTE1788: Automatic Access Class Barring feature, a CCPMconsistency checking rule is applied. This means that the feature can be triggered only when the previous activation time was at least (or exactly) 15 minutes before the next activation time (the sum of autoAcBarringStartTimer and autoACBarringStopTimer must be greater than or equal to 15 minutes). Possible user scenarios The benefits of LTE1788: Automatic Access Class Barring are mostly noticeable in times of a high traffic load, for example, New Year's Eve or in overcrowded spaces such as stadiums, etc. •

•

g

New Year's Eve The eNB's load is increasing in a few hours (2–3 hours). There are no sudden load peaks taking place, but the number of connections is increasing continuously. The traffic mix might include a circuit-switch fallback (CSFB voice), SMS, regular LTE data/signaling, etc., but the subscriber's mobility is kept unchanged. All cells are supporting more traffic than the engineered capacity, which results in at overload at an eNB level. Train arriving at a station Note: In this case, the operator must pay attention to the systemInfoValueTag changes. The maximum value of 31 changes in three hours might be easily exceeded due to a too low value of the autoAcBarringStartTimer and autoACBarringStopTimer.

•

When a train arrives at a station or leaves a long tunnel, a large number of unexpected signaling cases emerge (tracking area updates, RRC connection requests, etc.). Such a large nominal number of signaling cases exceed the engineered eNB's capacity and eventually leads to an overload state, which subsequently leads to triggering the automatic AC barring procedure. In these scenarios, in order to achieve a quick response from the eNB to the increasing overload, a very small Tstart_acb guard timer value is expected to be configured by the operator. Disaster area When a natural disaster takes place in a certain geographical area, an overload state on an eNB serving that area is expected to take a long time. An increase in the number of SMSs being sent, emergency calls being made, high priority accesses, and any voice calls is expected.

System impact Interdependencies between features

134

DN09185982

Issue: 01D



The following feature is a prerequisite for the LTE1788: Automatic Access Class Barring feature: •

LTE1047: Control Plane Overload Handling

The are interdependencies between the LTE1788: Automatic Access Class Barring feature and the following features:: •

•

•

LTE116: Cell Bandwidth – 3 MHz The SIB2 AC barring in case of an overload is supported on the 3 MHz LTE cell bandwidth only if the LTE116: Cell Bandwidth – 3 MHz feature is activated. LTE117: Cell Bandwidth – 1.4 MHz The SIB2 AC barring in case of an overload is supported on the 1.4 MHz LTE cell bandwidth only if the LTE117: Cell Bandwidth – 1.4 MHz feature is activated. LTE1635: SIB 8 AC Barring for 1xRTT

Impact on interfaces This feature uses the following SIB parameters of the RRC interface: •

SIB2: – – – – –

•

ac-BarringConfig for MO-Signalling MO-Data ssac-MMTEL-Voice ssac-MMTEL-Video CSFB

SIB8: –

ac-BarringConfig for 1xRTT

Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature improves system behavior in overload scenarios. The feature is expected to improve the accessibility and retainability during overload scenarios and maintain the throughput at an acceptable level. There is no direct impact on user-plane connections and their quality. Management data BTS faults and reported alarms Table 2: BTS faults lists BTS faults related to this feature.

Issue: 01D

DN09185982

135


Table 60


BTS faults

Fault ID

Fault name

Reported alarms Alarm ID

6351

System information broadcast parameters overflow

Alarm name

3022

NETWORK SERVICE VIRTUAL CONNECTION BLOCK PROCEDURE FAILED

Measurements and counters Table 3: New counters lists counters introduced with this feature. Table 61


Counter name

M8001C322

Time period of automatic access class barring due to overload

Measurement LTE Cell Load

Key performance indicators There are no key performance indicators related to this feature. Parameters Table 4: New Parameters lists parameters introduced with this feature. Table 62

New Parameters

Full name

AC Barring for CDMA2000 1xRTT OVL

136

Abbreviated name

rttAcBarOvl

Managed object CDFIM

Structure -

AC barring acBarring0To9Ovl CDFIM factor for overload classes 0 to 9 OVL

rttAcBarOvl

AC barring factor for overload class 10 OVL

acBarring10Ovl

CDFIM

rttAcBarOvl


acBarring11Ovl

CDFIM

rttAcBarOvl


acBarring12Ovl

CDFIM

rttAcBarOvl


acBarring13Ovl

CDFIM

rttAcBarOvl

DN09185982

Issue: 01D


Table 62

New Parameters (Cont.)

Full name

Issue: 01D


Abbreviated name

Managed object

Structure


acBarring14Ovl

CDFIM

rttAcBarOvl


acBarring15Ovl

CDFIM

rttAcBarOvl

AC barring Factor for emergency OVL

acBarringEmgOvl

CDFIM

rttAcBarOvl

AC barring modification factor for message OVL

acBarringMsgOvl

CDFIM

rttAcBarOvl

AC barring acBarringRegOvl modification factor for registration OVL

CDFIM

rttAcBarOvl

Activation of Automatic AC barring

actAutoAcBarring LNBTS

-

AC barring for mobile originating CS fallback OVL

acBarCsfbOcOvl

LNCEL

-

AC barring list OVL

acBarACOvl

LNCEL

acBarCsfbOcOvl

AC barring time OVL

acBarTimeOvl

LNCEL

acBarCsfbOcOvl

AC probability factor OVL

probFacOvl

LNCEL

acBarCsfbOcOvl

AC barring for MMTEL video originating calls OVL

acBarMMTelVideoO LNCEL cOvl

AC barring list OVL

acBarACOvl

LNCEL

acBarMMTelVideoOcO vl

AC barring time OVL

acBarTimeOvl

LNCEL



probFacOvl

LNCEL


AC barring for MMTEL voice originating calls OVL

acBarMMTelVoiceO LNCEL cOvl

AC barring list OVL

acBarACOvl

DN09185982

LNCEL

-

-

acBarMMTelVoiceOcO vl

137


Table 62


New Parameters (Cont.)

Full name

Abbreviated name

Managed object

Structure

AC barring time OVL

acBarTimeOvl

LNCEL



probFacOvl

LNCEL


AC barring for originating calls OVL

acBarOcOvl

LNCEL

-

AC barring list for mobile originating calls OVL

ocAcBarACOvl

LNCEL

acBarOcOvl

AC barring time for originating calls OVL

ocAcBarTimeOvl

LNCEL

acBarOcOvl

AC probability factor for originating calls OVL

ocAcProbFacOvl

LNCEL

acBarOcOvl

AC barring for signaling OVL

acBarSigOvl

LNCEL

-

AC barring list mobile orig signaling OVL

sigAcBarACOvl

LNCEL

acBarSigOvl

AC barring time for signaling OVL

sigAcBarTimeOvl

LNCEL

acBarSigOvl

AC probability factor for signaling OVL

sigAcProbFacOvl

LNCELActivation of C- acBarSigOvl plane overload handling

Automatic AC barring stop timer

autoACBarringSto LNCEL pTimer

-

Automatic AC barring start timer

autoAcBarringSta LNCEL rtTimer

-

AC barred for emergency calls OVL

eCallAcBarredOvl LNCEL

-

Table 5: Modified parameters lists parameters modified by this feature. Table 63


138

Abbreviated name

Managed object

Activation of C-plane overload handling

actCplaneOvlHandling

LNBTS

Access class barring for mobile

acBarCsfbOc

LNCEL

DN09185982

Issue: 01D


Table 63


Modified parameters (Cont.) Full name

Abbreviated name

Managed object

originating CS fallback

Issue: 01D

Access class barring list

acBarAC

LNCEL

Access class barring time

acBarTime

LNCEL

Access probability factor

probFac

LNCEL

Access class barring for MMTEL video originating calls

acBarMMTelVideoOc

LNCEL


acBarAC

LNCEL


acBarTime

LNCEL


probFac

LNCEL

Access class barring for MMTEL voice originating calls

acBarMMTelVoiceOc

LNCEL


acBarAC

LNCEL


acBarTime

LNCEL


probFac

LNCEL

Access class barring for originating calls

acBarOc

LNCEL

Access class barring list for mobile originating calls

ocAcBarAC

LNCEL

Access class barring time for originating calls

ocAcBarTime

LNCEL

Access probability factor for originating calls

ocAcProbFac

LNCEL

Access barring for signaling

acBarSig

LNCEL

Access class barring list mobile orig signaling

sigAcBarAC

LNCEL

Access class barring time for signaling

sigAcBarTime

LNCEL

Access probability factor for signaling

sigAcProbFac

LNCEL

DN09185982

139


Table 63



Abbreviated name

Access barred for emergency calls

eCallAcBarred





ASW

SW Asset Monitoring


3.11.2 Activating and configuring LTE1788: Automatic Access Class Barring Before you start Table 7 presents the parameters used for activating and configuring the LTE1788: Automatic Access Class Barring feature. Table 65

Parameters used for activating and configuring LTE1788: Automatic Access Class Barring Parameter

Purpose

Activation of Automatic activation flag AC Barring (actAutoAcBarring)

140

Requires eNB restart or object locking no

Automatic AC Barring start timer (autoAcBarringStart Timer)


no

Automatic AC Barring stop timer (autoACBarringStopT imer)


no

AC barred for emergency calls OVL (eCallAcBarredOvl)


no

AC barring for signaling OVL (acBarSigOvl)


no

AC barring time for signaling OVL (sigAcBarTimeOvl)


no

AC probability factor for signaling OVL (sigAcProbFacOvl)


no

AC barring for originating calls OVL (acBarOcOvl)


no

DN09185982

Issue: 01D


Table 65


Parameters used for activating and configuring LTE1788: Automatic Access Class Barring (Cont.) Parameter

Purpose

AC barring time for originating calls OV (ocAcBarTimeOvl)


no

AC probability factor for originating calls OVL(ocAcProbFacOvl)


no

AC barring for MMTEL optional configuration voice originating calls OVL (acBarMMTelVoiceOcOvl) AC barring time OVL (acBarTimeOvl)

g

g

no


no


no

Note: This parameter refers to the AC barring for MMTEL voice originating calls OVL structure.

AC probability factor OVL (probFacOvl) Note: This parameter refers to the AC barring for MMTEL voice originating calls OVL structure.

AC barring for MMTEL optional configuration video originating calls OVL (acBarMMTelVideoOcOvl)

no


no


no

AC barring for mobile originating CS fallback OVL (acBarCsfbOcOvl)


no

AC barring time OVL (acBarTimeOvl)


no

AC barring time OVL (acBarTimeOvl)

g

Note: This parameter refers to the AC barring for MMTEL video originating calls OVL structure.

AC probability factor OVL (probFacOvl)

g

Issue: 01D


Note: This parameter refers to the AC barring for MMTEL video originating calls OVL structure.

DN09185982

141


Table 65



g

Purpose

Note: This parameter refers to the AC barring for mobile originating CS fallback OVL structure. mandatory configuration

no


no

AC barring factor for overload classes 0 to 9 OVL (acBarring0To9Ovl)


no

AC barring Factor for emergency OVL (acBarringEmgOvl)


no

AC barring factor for overload class 10 OVL (acBarring10Ovl)


no



no



no



no

AC barring factor for overload class 14 OVL (acBarring14vl)


no



no

AC barring modification factor for message OVL (acBarringMsgOvl)


no

AC probability factor OVL (probFacOvl)

g

Note: This parameter refers to the AC barring for mobile originating CS fallback OVL structure.

AC Barring for CDMA2000 1xRTT OVL (rttAcBarOvl)

g

142


Note: When this parameter is configured, it's (following) structure parameters' configuration is mandatory,

DN09185982

Issue: 01D


Table 65



Purpose

AC barring modification factor for registration OVL (acBarringRegOvl)



The LTE1047: Control Plane Overload Handling feature needs to be activated/configured before the activation of the LTE1788: Automatic Access Class Barring feature. Before activation of the LTE1788: Automatic Access Class Barring feature, ensure that the static access class barring parameters are configured according to your expectations. Ensure that the overload AC barring parameters are well coordinated with static AC barring parameters Procedure To activate the feature, do the following: 1


2

Activate the LTE1788: Automatic Access Class Barring feature. a) b) c) d)

3

Go to the Radio Network Configutration page. Expand the MRBTS object. Select the LNBTS object. Set the Activation of Automatic AC Barring (actAutoAcBarring) LNBTS parameter's value to true.

Configure the timer after which eNB starts automatic AC barring (optional). a) Expand the LNBTS object. b) Select the LNCEL object. c) Set the Automatic AC Barring start timer (autoAcBarringStartTimer) parameter to a needed value. The default value is 300 s.

4

Configure the timer after which eNB stops automatic AC barring (optional). a) Select the LNCEL object. b) Set the Automatic AC Barring stop timer (autoACBarringStopTimer) parameter to a needed value.

Issue: 01D

DN09185982

143



The default value is 3600 s.

5

Indicate if access is barred for emergency calls in this cell when automatic AC barring broadcast condition is met due to an eNB C-plane overload. a) Select the LNCEL object. b) Set the AC barred for emergency calls OVL (eCallAcBarredOvl) LNCEL parameter's value to barred or Not barred.

g

Note: For the feature to function properly, at least one of the parameters defined in the following steps must be configured. The parameters are defined for each cell separately.

6

Configure access barring for signaling OVL. a) Select the LNCEL object. b) If required, right-click the LNCEL object and select New ► AC barring for signaling OVL (acBarSigOvl). c) Expand the created AC barring for signaling OVL object. d) Select AC barring for signaling OVL-1. e) Configure at least the following parameters: •

•

f)

7

AC barring time for signaling OVL (sigAcBarTimeOvl) The parameter defines the access class barring time when the automatic AC barring broadcast condition is met due to an eNB C-plane overload. AC probability factor for signaling OVL (sigAcProbFacOvl) The parameter defines the probability of a UE establishing an RRC connection when the automatic AC barring broadcast condition is met due to an eNB C-plane overload.

Optionally, configure access class barring for special access classes from AC11 to AC15 by setting a value to true or false.

Configure access class barring for originating calls OVL. a) Select the LNCEL object. b) If required, right-click the LNCEL object and select New ► AC barring for originating calls OVL (acBarOcOvl). c) Expand the created AC barring for originating calls OVL object. d) Select AC barring for originating calls OVL- 1. e) Configure at least the following parameters: •

144

AC barring time for originating calls OV (ocAcBarTimeOvl)

DN09185982

Issue: 01D



The parameter defines the access class barring time when the automatic AC barring broadcast condition is met due to an eNB C-plane overload. •

f)

8

g

AC probability factor for originating calls OVL (ocAcProbFacOvl) The parameter defines the probability of a UE establishing an RRC connection when the automatic AC barring broadcast condition is met due to an eNB C-plane overload.


Configure access class barring for MMTEL voice originating calls OVL. Note: To be able to configure access class barring for MMTEL voice originating calls, the LTE10: EPS Bearers for Conversational Voice feature must be enabled first. a) Select the LNCEL object. b) If required, right-click the LNCEL object and select New ► AC barring for MMTEL voice originating calls OVL (acBarMMTelVoiceOcOvl). c) Expand the created AC barring for MMTEL voice originating calls OVL object. d) Select AC barring for MMTEL voice originating calls OVL-1. e) Configure at least the following parameters: •

•

f)

9

g

AC barring time OVL (acBarTimeOvl) The parameter defines the access class barring time when the automatic AC barring broadcast condition is met due to an eNB C-plane overload. AC probability factor OVL (probFacOvl) The parameter defines the probability of a UE establishing an RRC connection when the automatic AC barring broadcast condition is met due to an eNB C-plane overload.


Configure access class barring for MMTEL video originating calls OVL. Note: To be able to configure access class barring for MMTEL voice originating calls, the LTE10: EPS Bearers for Conversational Voice feature must be enabled first. a) Select the LNCEL object. b) If required, right-click the LNCEL object and select New ► AC barring for MMTEL video originating calls OVL (acBarMMTelVideoOcOvl). c) Expand the created AC barring for MMTEL video originating calls OVL object. d) Select AC barring for MMTEL video originating calls OVL-1. e) Configure at least the following parameters: •

Issue: 01D

AC barring time OVL (acBarTimeOvl) The parameter defines the access class barring time when the automatic AC barring broadcast condition is met due to an eNB C-plane overload.

DN09185982

145


•

f)


AC probability factor OVL (probFacOvl) The parameter defines the probability of a UE establishing an RRC connection when the automatic AC barring broadcast condition is met due to an eNB C-plane overload.


10 Configure access class barring for mobile originating CS fallback OVL.

g g

Note: The CS fallback applies only to the 3GPP CSFB. For more information, see 3GPP TS36.331. Note: To be able to configure access class barring for mobile-originating CS fallback, the LTE562: CSFB to UTRAN or GSM via Redirect and LTE736: CS Fallback to UTRAN must be activated. a) Select the LNCEL object. b) If required, right-click the LNCEL object and select New ► AC barring for mobile originating CS fallback OVL (acBarCsfbOcOvl) object. c) Expand the created AC barring for mobile originating CS fallback OVLobject. d) Select AC barring for mobile originating CS fallback OVL-1. e) Configure at least the following parameters: •

•

f)

AC barring time OVL (acBarTimeOvl) The parameter defines the access class barring time when the automatic AC barring broadcast condition is met due to an eNB C-plane overload. AC probability factor OVL (probFacOvl) The parameter defines the probability of a UE establishing an RRC connection when the automatic AC barring broadcast condition is met due to an eNB C-plane overload.


11 Configure access class barring for CDMA2000 1xRTT fallback OVL. The CS fallback applies only to the CDMA2000 1xRTT fallback. For more information, see C.S0097.

g

Note: To be able to configure access class barring for CDMA2000 1xRTT fallback, the LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature must be activated. a) b) c) d)

Select the LNCEL object. Right-click the LNCEL object and from a drop-down list select the CDFIM object. Right-click the CDFIM object. From the drop-down menu select New ► AC Barring for CDMA2000 1xRTT OVL (rttAcBarOvl). e) Expand the AC Barring for CDMA2000 1xRTT OVL object. f) Select AC Barring for CDMA2000 1xRTT OVL- 1.

146

DN09185982

Issue: 01D



g) Configure at least the following parameter: •

Issue: 01D

AC barring factor for overload classes 0 to 9 OVL (acBarring0To9Ovl) The parameter defines the access class barring from 0 to 9 when the automatic AC barring broadcast condition is met due to an eNB C-plane overload.

DN09185982

147



h) Optionally configure the following parameters: • •

•

•

AC barring Factor for emergency OVL (acBarringEmgOvl) Default value is: 0 The parameter values from AC barring factor for overload class 10 OVL (acBarring10Ovl) to AC barring factor for overload class 15 OVL (acBarring15Ovl) Default values are: 0 AC barring modification factor for message OVL (acBarringMsgOvl) Default value is: 0 AC barring modification factor for registration OVL (acBarringRegOvl) Default value is: 0



The feature has been activated, and the parameter settings are persistently stored in the eNB. NetAct and BTS Site Manager are informed about the changed configuration (which is visible through notifications).

3.11.3 Deactivating LTE1788: Automatic Access Class Barring Before you start The Activation of Automatic AC Barring (actAutoAcBarring) parameter is used for deactivation. Modification of this parameter requires neither an eNB restart nor cell locking. Procedure 1


2

Deactivate the LTE1788: Automatic Access Class Barring feature. a) Go to the Radio Network Configutration page. b) Expand the MRBTS object. c) Select the LNBTS object.

148

DN09185982

Issue: 01D



d) Set the Activation of Automatic AC Barring (actAutoAcBarring) LNBTS parameter's value to false.

3


Expected outcome The feature has been successfully disabled, and the access classes are no longer automatically barred.

3.12 LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz 3.12.1 Description of LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz Introduction to the feature The LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature introduces downlink (DL) carrier aggregation (CA) in multiples of three cell combinations, where a given user equipment (UE) is configured with two secondary cells (SCells). The evolved Node B (eNB) has more than two cells on different frequencies per sector. The feature supports CA in the DL for three component carriers (CCs) of up to 60 MHz as compared to the LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz feature. Benefits End-user benefits This feature offers the end user an improved peak and average UE DL throughput. Note that this is only beneficial in cells that are not fully loaded. Operator benefits This feature provides the following benefits to the operator: •

• •

allows the operator to aggregate the air interface of three overlapping cells with the bandwidths (BWs) of up to 20 MHz + 20 MHz + 20 MHz to reach high DL peak rates for individual users allows the operator to increase the UE's peak data rate by up to 450 Mbps in case of fragmented spectrum in certain load conditions enables fast load balancing for CA UEs within the three DL cells

Requirements Hardware and software requirements

Issue: 01D

DN09185982

149


Table 66 System release FDD-LTE 15A

Hardware and software requirements Flexi Multiradio BTS


-

FL15A



OMS -

UE •

•

3GPP R11 UE capabilities 3GPP R12 UE capabilities



NetAct NetAct 15.5

MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview The LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature introduces CA in the DL for three CCs and three non-aggregated uplink (UL) cells. A mix of non-CA and CA UEs with two or three aggregated CCs is supported in the DL on each cell. The Figure 9: Examples of three-cell CA shows examples of CA with three cells per sector. Scenarios 1 and 2 correspond to the 3rd Generation Partnership Project (3GPP) TS 36.300.

150

DN09185982

Issue: 01D


Figure 9


Examples of three-cell CA

f1

f3

f2

f1

f3

Scenario2with3cellspersector

Scenario1with3cellspersector

f1

f2

f2

f3

Scenario1or2with3cellspersector(withnon-wirelessrepeater)

Aggregated cell configurations The following are the cell configurations supported by the LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature: •

band combinations The following are the additional supported band combinations for the deployment scenarios 1 and 2 as described by the 3GPP TS 36.300: – – – – – – – – – – – – – – – – –

Issue: 01D

band 1 + band 3 + band 5 (BW combination set: 0) band 1 + band 3 + band 8 (BW combination set: 0 and 2) band 1 + band 5 + band 7 (BW combination set: 1) band 1 + band 18 + band 28 band 2 + band 2 + band 5 (band 2 non-contiguous) band 2 + band 2 + band 12 (band 2 non-contiguous) band 2 + band 2 + band 29 (band 2 contiguous) band 2 + band 4 + band 4 (band 4 non-contiguous) band 2 + band 4 + band 5 band 2 + band 4 + band 12 band 2 + band 5 + band 30 band 2 + band 12 + band 30 band 2 + band 29 + band 30 band 3 + band 3 + band 7 band 3 + band 3 + band 8 band 3 + band 7 + band 20 band 4 + band 4 + band 5 (band 4 non-contiguous)

DN09185982

151


– – – –

g


band 4 + band 4 + band 12 (band 4 non-contiguous) band 4 + band 5 + band 30 band 4 + band 12 + band 30 band 4 + band 29 + band 30 Note: The BW combination set is 0 if not indicated.

•

BW combinations The maximum aggregated DL BW is 60 MHz. The following are the additional supported BW combinations for 2Rx/2Tx configuration per CC: – – – – – – – – – – – – – – – – – – – –

g

5 MHz + 5 MHz + 5 MHz 5 MHz + 5 MHz + 10 MHz 5 MHz + 5 MHz + 15 MHz 5 MHz + 5 MHz + 20 MHz 5 MHz + 10 MHz + 10 MHz 5 MHz + 10 MHz + 15 MHz 5 MHz + 10 MHz + 20 MHz 5 MHz + 15 MHz + 15 MHz 5 MHz + 15 MHz + 20 MHz 5 MHz + 20 MHz + 20 MHz 10 MHz + 10 MHz + 10 MHz 10 MHz + 10 MHz + 15 MHz 10 MHz + 10 MHz + 20 MHz 10 MHz + 15 MHz + 15 MHz 10 MHz + 15 MHz + 20 MHz 10 MHz + 20 MHz + 20 MHz 15 MHz + 15 MHz + 15 MHz 15 MHz + 15 MHz + 20 MHz 15 MHz + 20 MHz + 20 MHz 20 MHz + 20 MHz + 20 MHz Note: The 10 MHz + 10 MHz + 20 MHz BW combination is the only configuration supported in the LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature from the LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz feature.

The following are the supported BW combinations with 4Rx/4Tx configuration on the CC with the highest cell BW: – – – – – – – – –

152

5 MHz + 5 MHz + 5 MHz 5 MHz + 5 MHz + 10 MHz 5 MHz + 5 MHz + 15 MHz 5 MHz + 5 MHz + 20 MHz 5 MHz + 10 MHz + 10 MHz 5 MHz + 10 MHz + 15 MHz 5 MHz + 10 MHz + 20 MHz 10 MHz + 10 MHz + 10 MHz 10 MHz + 10 MHz + 15 MHz

DN09185982

Issue: 01D


–

g


10 MHz + 10 MHz + 20 MHz Note: This is with the implicit assumption of nine cells per eNB with three FSPs. However, because of large user plane deployments, the 4Rx/4Tx + 4Rx/4Tx + 4Rx/4Tx configuration is supported even for the 20 MHz + 20 MHz + 20 MHz BW combination with a limited number of cells.

•

eNB antenna configurations The following are the supported eNB antenna configurations: – – – –

g

2Tx/2Rx + 2Tx/2Rx + 2Tx/2Rx 2Tx/2Rx + 2Tx/2Rx + 4Tx/4Rx 2Tx/4Rx + 4Tx/4Rx + 4Tx/4Rx 4Tx/4Rx + 4Tx/4Rx + 4Tx/4Rx

Note: Only the 3GPP-defined band and BW combinations are supported. DL CA is only applied for UEs with related UE capabilities. The parallel use of the UL coordinated multipoint transmission (CoMP) might be restricted. Functionality This feature is an extension to the LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz feature. For more details, see the LTE1803: Downlink Carrier Aggregation 3 CC 40 MHz feature description. The functions of the LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature are described as follows: •

• •

• •

•

•

Issue: 01D

Based on the radio admission control (RAC) selection, either one or two SCells for a three-cell-CA candidate UE is added. A three-cell-CA candidate UE can be a twocell-CA candidate UE at the same time. The UE can be configured with one SCell. A UE supporting CA of three cells that is a three-cell-CA candidate is configured with physical uplink control channel (PUCCH) format 3 when one SCell is added. A UE supporting CA of three cells that is not a three-cell-CA candidate is configured with PUCCH format 1bwcs when one SCell is added. The maximum number of UEs with one or two SCells configured is increased. SCell release of one from two SCells configured because of cell lock/shutdown is introduced. The other configured SCell, which is not locked/shutdown, continues to serve the CA UE. The interworking with the nominal bit rate (NBR) is improved. The NBR is allowed in the DL for three-cell-CA candidate UEs. Stepwise SCell activation of two configured SCells because of traffic is introduced. One SCell is activated if traffic first is required. After that, a check is made if the second SCell needs to be activated because of traffic or if one active SCell is sufficient for that UE. The configurable SCell activation conservativeness level for one and two configured SCells is improved. It is recommended to set the sCellActivationCyclePeriod and scellActivationLevel parameters to low values to achieve fast activation for Transmission Control Protocol (TCP) traffic and short response time. The simultaneousAckNackAndCQI-Format3-r11 dedicated radio resource control (RRC) information element is set to true. The periodic channel state information (CSI) is sent on RRC connection on the PUCCH format 3 with positive acknowledgment (ACK)/negative acknowledgment (NACK) if it is supported by the Rel-11 UE. Dropping of the periodic CSI or SCell scheduling restriction to avoid the dropping is not applied for such UEs.

DN09185982

153


g


Note: The sub-band periodic CSI is not recommended to be configured when the DL CA is enabled. Instead, only the wideband periodic CSI is recommended to be configured. •

• • •

The PUCCH format 3 resource value selection with configurable (one or two) PUCCH format 3 physical resource blocks (PRBs) is introduced. The operator can configure the amount of available PUCCH format 3 resources. The scheduling of single or multiple UEs on three serving cells with new band or BW combinations with configurable CA fairness is supported. The interworking with the peak data rate capping for two active SCells is improved. The following new performance management (PM) counters are introduced: – –

SCell scheduling blocking rate due to conflict on PUCCH format 3 resources SCell scheduling blocking rate due to conflict on PUCCH format 1bwcs resources

System impact Interdependencies between features This feature is enabled together with the following features: • • • •

LTE1089: Downlink Carrier Aggregation - 20 MHz LTE1332: Downlink Carrier Aggregation - 40 MHz LTE1562: Carrier Aggregation for Multi-carrier eNodeBs LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz

The interworking with the following features is excluded: • • •

LTE117: Cell Bandwidth 1.4 MHz LTE116: Cell Bandwidth 3 MHz LTE1382: Cell Resource Groups (interworking with DL CA of two serving cells is possible)

The LTE1542: FDD Supercell and LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz features can be enabled together. The supercell-enabled cells and supercelldisabled cells might affect the CA performance because of coverage mismatch. Therefore, CA relations (CAREL objects) must be planned carefully. In addition, the features addressing CA coverage mismatch scenarios, such as the LTE2006: Flexible SCell Selection feature, should be considered for activation. The LTE1367: Automatic Cell Combination Assignment for Carrier Aggregation and LTE1951: Automatic Configuration Support for CA for Multi-carrier eNBs features do not support CA of supercell-enabled cells and supercell-disabled cells. Thus, manual configuration of CA relations is needed in these mixed configuration scenarios. Impact on interfaces This feature affects the Uu interface as follows: • • •

154

simultaneousAckNackAndCQI-Format3-r11 set to true PUCCH format 3 used for eligible UEs configured with one SCell delivery of the three-cell CA specific tReord, tProhib, and tPollRetr parameters

DN09185982

Issue: 01D


g


Note: It is recommended to use the following: • •

optimized RLC profile for three-CC CA profile ID 6 (default) for the rlcProfIdx3cc parameter

Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity The LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature enhances the single user DL-peak throughput by aggregating three carriers up to 20 MHz + 20 MHz + 20 MHz.

g

Note: The configurable level of SCell activation conservativeness and stepwise SCell activation might reduce the throughput of the CA UEs, but it might be beneficial for other UEs. The following feature enhancements affect the capacity: • •

The number of UEs with one or two SCells configured is increased. This has also an impact on the number of RRC_CONNECTED UEs in the cells. The number of UEs with one SCell (using PUCCH format 1bcws) or two SCells configured (using PUCCH format 3) per transmission time interval (TTI) per cell is increased because the number of PUCCH format 3 PRBs is increased.

Management data Alarms There are no alarms related to this feature. Measurements and counters Table 67: New counters lists the counters introduced with this feature. Table 67


Counter name

Measurement

M8011C166

SCell scheduling blocking rate due to conflicts on PUCCH format 1bwcs resources

LTE Cell Resource

M8011C167

SCell scheduling blocking rate due to conflicts on PUCCH format 3 resources

LTE Cell Resource

Key performance indicators Table 68: New key performance indicators lists the key performance indicators introduced in this feature.

Issue: 01D

DN09185982

155


Table 68


New key performance indicators KPI ID

KPI name

LTE_5700a

E-UTRAN SCell Scheduling Blocking Rate due to Conflicts on PUCCH Format 1bwcs Resources

LTE_5701a

E-UTRAN SCell Scheduling Blocking Rate due to Conflicts on PUCCH Format 3 Resources

Parameters Table 69: New parameters lists the parameters introduced with this feature. Table 69

New parameters

Full name

Abbreviated name

Managed object

Structure

BTS ID of the parent eNB of the cell to be aggregated

lnBtsId

CAREL

-

Carrier aggregation pool ID

caPoolId

LNCEL

-

Enable Bandwidth Combination Checks

enableBwCombCheck

LNBTS

-

Profile 6 of RLC parameters

rlcProf6

LNBTS

-

Poll PDU

pollPdu

LNBTS

rlcProf6

RLC profile Id

rlcProfileId

LNBTS

rlcProf6

Timer poll retransmit

tPollRetr

LNBTS

rlcProf6

Timer status prohibit

tProhib

LNBTS

rlcProf6

Timer reordering

tReord

LNBTS

rlcProf6

Conservativeness level of SCell activation

scellActivationLevel

LNBTS

-

RLC profile index for 3 rlcProfIdx3cc CC CA

LNBTS

qciTab7


LNBTS

qciTab8


LNBTS

qciTab9


LNBTS

qciTabOperator

Table 70: Modified parameters lists the parameters modified by this feature. Table 70


Abbreviated name

Activation of downlink carrier aggregation

156

actDLCAggr

DN09185982


Issue: 01D


Table 70



Abbreviated name

Managed object

Scheduling CA fairness control caSchedFairFact factor

LNBTS

SCell activation method

sCellActivationMethod

LNBTS

SCell activation cycle period

sCellActivationCyclePeriod

LNBTS

Max number carrier aggr configured UEs

maxNumCaConfUe

LNCEL

Max number carrier aggr configured UEs 3 Carriers

maxNumCaConfUe3c

LNCEL

Max number Carrier Aggr configured UEs double carrier

maxNumCaConfUeDc

LNCEL

Number of PUCCH PRBs for HARQ format 3

nPucchF3Prbs

LNCEL

Table 71: Related existing parameters lists the existing parameters related to this feature. Table 71


Full name

Issue: 01D

Abbreviated name

Managed object

Structure

Max number of maxNumScells secondary cells for DL carrier aggr

LNCEL

-

QCI translation table QCI 7

qciTab7

LNBTS

-

DRX profile index

drxProfileIndex

LNBTS

qciTab7

DSCP

dscp

LNBTS

qciTab7

Enforce TTI bundling

enforceTtiBundling

LNBTS

qciTab7

Logical channel group identifier

lcgid

LNBTS

qciTab7

Nominal bit rate downlink

nbrDl

LNBTS

qciTab7

Nominal bit rate uplink nbrUl

LNBTS

qciTab7

Priority

prio

LNBTS

qciTab7

QCI

qci

LNBTS

qciTab7

QCI support

qciSupp

LNBTS

qciTab7

Resource type

resType

LNBTS

qciTab7

RLC mode

rlcMode

LNBTS

qciTab7

RLC profile index

rlcProfIdx

LNBTS

qciTab7

Scheduling bucket size duration

schedulBSD

LNBTS

qciTab7

Scheduling priority

schedulPrio

LNBTS

qciTab7

Scheduling weight

schedulWeight

LNBTS

qciTab7

DN09185982

157


Table 71


Full name

158


Abbreviated name

Managed object

Structure


qciTab8

LNBTS

-

DRX profile index

drxProfileIndex

LNBTS

qciTab8

DSCP

dscp

LNBTS

qciTab8


enforceTtiBundling

LNBTS

qciTab8


lcgid

LNBTS

qciTab8


nbrDl

LNBTS

qciTab8


LNBTS

qciTab8

Priority

prio

LNBTS

qciTab8

QCI

qci

LNBTS

qciTab8

QCI support

qciSupp

LNBTS

qciTab8

Resource type

resType

LNBTS

qciTab8

RLC mode

rlcMode

LNBTS

qciTab8

RLC profile index

rlcProfIdx

LNBTS

qciTab8


schedulBSD

LNBTS

qciTab8

Scheduling priority

schedulPrio

LNBTS

qciTab8

Scheduling weight

schedulWeight

LNBTS

qciTab8


qciTab9

LNBTS

-

DRX profile index

drxProfileIndex

LNBTS

qciTab9

DSCP

dscp

LNBTS

qciTab9


enforceTtiBundling

LNBTS

qciTab9


lcgid

LNBTS

qciTab9


nbrDl

LNBTS

qciTab9


LNBTS

qciTab9

Priority

prio

LNBTS

qciTab9

QCI

qci

LNBTS

qciTab9

QCI support

qciSupp

LNBTS

qciTab9

Resource type

resType

LNBTS

qciTab9

RLC mode

rlcMode

LNBTS

qciTab9

RLC profile index

rlcProfIdx

LNBTS

qciTab9


schedulBSD

LNBTS

qciTab9

Scheduling priority

schedulPrio

LNBTS

qciTab9

DN09185982

Issue: 01D


Table 71



Full name Scheduling weight

Abbreviated name

Managed object

Structure

schedulWeight

LNBTS

qciTab9

QCI translation table qciTabOperator operator specific QCIs

LNBTS

-

Counter group

counterGroup

LNBTS

qciTabOperator

Delay target

delayTarget

LNBTS

qciTabOperator

DRX profile index

drxProfileIndex

LNBTS

qciTabOperator

DSCP

dscp

LNBTS

qciTabOperator


enforceTtiBundling

LNBTS

qciTabOperator

L2 overhead factor GBR Dl

l2OHFactorDl

LNBTS

qciTabOperator

L2 overhead factor GBR Ul

l2OHFactorUl

LNBTS

qciTabOperator


lcgid

LNBTS

qciTabOperator

Maximum GBR downlink

maxGbrDl

LNBTS

qciTabOperator

Maximum GBR uplink

maxGbrUl

LNBTS

qciTabOperator


nbrDl

LNBTS

qciTabOperator


LNBTS

qciTabOperator

Priority

prio

LNBTS

qciTabOperator

QCI

qci

LNBTS

qciTabOperator

QCI support

qciSupp

LNBTS

qciTabOperator

Resource type

resType

LNBTS

qciTabOperator

RLC mode

rlcMode

LNBTS

qciTabOperator

RLC profile index

rlcProfIdx

LNBTS

qciTabOperator


schedulBSD

LNBTS

qciTabOperator

Scheduling priority

schedulPrio

LNBTS

qciTabOperator

Scheduling weight

schedulWeight

LNBTS

qciTabOperator



ASW

Issue: 01D


DN09185982


159



3.12.2 Activating and configuring LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz Before you start The Activation of downlink Carrier aggregation (actDLCAggr) parameter activates the feature. The Max number of secondary cells for DL carrier aggr (maxNumScells) parameter allows aggregation of three serving cells. Modification of these parameters requires eNB restart. It is recommended to set the Sched Carrier Aggr fairness control factor (caSchedFairFact) parameter value to 0 for the LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature. Table 73

Parameters used for activating and configuring the LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature

Parameter

Purpose


Activation of downlink Carrier aggregation (actDLCAggr)

activation flag

eNB restart

Max number of secondary cells for DL carrier aggr (maxNumScells)


eNB restart

The LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature is enabled together with the LTE1089: Downlink Carrier Aggregation - 20 MHz, LTE1332: Downlink Carrier Aggregation - 40 MHz, LTE1562: Carrier Aggregation for Multi-carrier eNodeBs, and LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz features. These features use the same activation flag. For more information about feature dependencies, see Interdependencies between features. In operating the CA features, it might be necessary to set the link speed parameter. This is described in the Commissioning Flexi Multiradio BTS LTE document. Note that the default value (Auto) of this parameter is normally the optimal selection. The eNB supports the deployment required for CA. All LNCELs in the eNB must have the Carrier aggregation pool ID (caPoolId) parameter configured when the LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature is enabled. The CA cells with subordinated CAREL or CA cells linked by CAREL-lcrId of another LNCEL must have the same CA pool ID. If there are more than two cells per sector, each cell can have multiple CARELs and each cell can be linked by CAREL-lcrId of other multiple cells. The maximum number of SCell candidates per PCell is two. Multiple CARELs of one cell do not point to the same cell. The following parameters must be set before activating the LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature: • •

160

The PUCCH bandwidth for CQI (nCqiRb) parameter must have a value greater than 1. The Number of PUCCH PRBs for HARQ format 3 (nPucchF3Prbs) parameter must have a value greater than 0.

DN09185982

Issue: 01D


•


The CQI periodicity network period (cqiPerNp) parameter must have a value less than or equal to 40ms.

Procedure 1

Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure, perform the steps described in this procedure.

2

Configure the Activation of downlink Carrier aggregation (actDLCAggr) parameter. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activation of downlink Carrier aggregation (actDLCAggr) parameter value to true.

Create a new CAREL object. a) Expand the LNBTS object. b) Select the LNCEL object. c) Create a new CAREL object.

g

Note: The CA pool ID (LNCEL-caPoolId) must be consistent within the CA cluster. The CAREL objects must only point to cells in their CA pool.

4

Configure the Max number of secondary cells for DL carrier aggr (maxNumScells) parameter. a) Expand the selected LNBTS object. b) Select the LNCEL object. c) Set the Max number of secondary cells for DL carrier aggr (maxNumScells) parameter value to 2.

g

Note: When the parameter value is set to 2, the eNB uses CA with two or three CCs and the Number of PUCCH PRBs for HARQ format 3 (nPucchF3Prbs) parameter must not be set to 0.

5

(Optional) Configure the Profile 6 of RLC parameters (rlcProf6) parameter. On the expanded LNBTS object, select the Profile 6 of RLC parameters object and define the value of each parameter within this object.

Issue: 01D

DN09185982

161


g


Note: The default values for the parameters within this object are set. Modification of the default values is not mandatory.

6

(Optional) Configure the RLC profile index for 3 CC CA (rlcProfIdx3cc) parameter. On the expanded LNBTS object, select the QCI translation table QCI 6 object and define the value of the RLC profile index for 3 CC CA (rlcProfIdx3cc) parameter.

g

Note: This step is also applicable for the QCI translation table QCI 7, QCI translation table QCI 8, and QCI translation table QCI 9 objects.

7

(Optional) Create a new QCI translation table operator specific QCIs object. a) Right-click on the LNBTS object. b) Create a new QCI translation table operator specific QCIs object and define the value of each parameter within this object.

8


Expected Outcome The LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature is enabled in the eNB. The eNB uses CA with two or three CCs.

3.12.3 Deactivating LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz Before you start The Max number of secondary cells for DL carrier aggr (maxNumScells) parameter deactivates the feature. Modification of this parameter requires eNB restart. Procedure 1


162

DN09185982

Issue: 01D


2

Configure the Max number of secondary cells for DL carrier aggr (maxNumScells) parameter. a) b) c) d) e)

g


Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Select the LNCEL object. Set the Max number of secondary cells for DL carrier aggr (maxNumScells) parameter value to 1.

Note: When the parameter value is set to 1, the eNB only uses CA with two CCs and the Number of PUCCH PRBs for HARQ format 3 (nPucchF3Prbs) parameter must be set to 0. To deactivate CA completely, set the Activation of downlink carrier aggregation (actDLCAggr) parameter value to false.

3


Expected outcome The LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature is deactivated in the eNB. The eNB only uses CA with two CCs.

3.13 LTE1905: PLMN ID and SPID Selected Mobility Profiles 3.13.1 Description of LTE1905: PLMN ID and SPID Selected Mobility Profiles Introduction to the feature The LTE1905: PLMN ID and SPID Selected Mobility Profiles feature replaces a virtual SPID calculation, provided by the LTE486: PLMN ID Selected Mobility Profiles feature, with a provisioned PLMN-SPID-based method for selecting a mobility profile. Additionally, the LTE1905: PLMN ID and SPID Selected Mobility Profiles feature also is related to the LTE490: Subscriber profile based mobility feature; with the LTE1905: PLMN ID and SPID Selected Mobility Profiles feature there are profile selection based on: SPID only, PLMN only, and SPID-PLMN. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The UE mobility is optimized because:

Issue: 01D

DN09185982

163


• •


The operator can specify a method for selecting a mobility profile: PLMN ID only, SPID only, or combined PLMN ID and SPID. The operator can provision separate SPIDs and mobility profiles per PLMN.





OMS -

UE -


FL16

NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description A mobility profile contains lists of allowed target LTE and inter-RAT frequencies/bands that are used for a UE's mobility. The eNB selects the mobility profile by comparing one of the following values with the moPrMappingList LNCEL parameter: • •

g

a UE's Subscriber profile ID (SPID) received from an MME - introduced with the LTE490: Subscriber Profile-based Mobility feature a UE's serving public land mobile network (PLMN) Note: A virtual SPID introduced with the LTE486: PLMN ID Selected Mobility Profiles is replaced with the LTE1905: PLMN ID and SPID Selected Mobility Profiles feature.

•

a UE's serving PLMN ID and SPID - introduced with the LTE1905: PLMN ID and SPID Selected Mobility Profiles feature

The moProfileSelect parameter values When the LTE1905: PLMN ID and SPID Selected Mobility Profiles feature is enabled (the actSelMobPrf parameter is set to true), the eNB's behavior depends on the profile selection method indicated by the moProfileSelect LNBTS parameter, the configuration in the moPrMappingList LNCEL parameter, the UE's serving PLMN, and the SPID value, if provided by the MME. For the moProfileSelect=spid, the eNB uses the SPID value if provided by the MME and searches the mobility profile in the moPrMappingList table, using the SPID value. It ignores the PLMN value in the table. If a match is not found, or the SPID was not received from the MME, the default mobility profile is used. For the moProfileSelect=plmn, the eNB uses the serving PLMN ID of the UE to search the mobility profile in the moPrMappingList table. It ignores the SPID value if it was provided by the MME. If a match is not found, then the default mobility profile is used.

164

DN09185982

Issue: 01D



For the moProfileSelect=combined, the eNB uses the serving PLMN ID and the SPID to search the profile in the moPrMappingList table as follows: •

•

If both the PLMN ID and SPID values are available, the eNB looks up the table, using both the PLMN ID and SPID first to find a match. If the match is not found, then the eNB looks up the table, using only the SPID to find a match. The PLMN is then represented by an empty wildcard on a mobility profile mapping list. If the match is not found, then the eNB looks up the table, using only the PLMN ID to find a match. The SPID is then represented by an empty wildcard on a mobility profile mapping list. If the match is not found, then the default profile is used. If only the PLMN ID value is available (the MME did not provide any SPID value), the eNB looks up the table, using only the PLMN ID to find a match. If the match is not found, then the default mobility profile is used.

In all cases, if an entry is found in the moPrMappingList table, the moPrId from the entry is used to find the mobility profile; otherwise, the MODPR is used. Mobility profile mapping table The mobility profile mapping table is extended with the PLMN ID (the mcc, mnc, and mncLength) attributes in addition to the spid and spidLast attributes. These attributes are used as a key to search the mobility profile identifier that points to the actual mobility profile. System impact Interdependencies between features •

LTE490: Subscriber Profile-based Mobility The LTE1905: PLMN ID and SPID Selected Mobility Profiles feature is enabled only when the LTE490: Subscriber Profile-based Mobility feature is enabled, and moProfileSelect=plmn or moProfileSelect=combined. The LTE1905: PLMN ID and SPID Selected Mobility Profiles feature also supports moProfileSelect=spid.

Impact on interfaces No impact on interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity 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

Issue: 01D

DN09185982

165



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

New parameters

Full name

Abbreviated name

Managed object

Structure

Mobile country code

mcc

LNCEL

moPrMappingList

Mobile network code

mnc

LNCEL

moPrMappingList

Mobile network code length

mncLength

LNCEL

moPrMappingList



Full name

Abbreviated name

Structure

Activate selective mobility profiles

actSelMobPrf

LNBTS

-

Mobility profile selection mode

moProfileSelect

LNBTS

-

Mobility profiles mapping list

moPrMappingList

LNCEL

-

Mobility profile ID

moPrId

LNCEL

moPrMappingList

Subscriber profile ID

spid

LNCEL

moPrMappingList

Last subscriber profile ID of a range

spidLast

LNCEL

moPrMappingList

MODIMP

-

Idle mode mobility modimpId default profile identifier

166

Managed object

Frequency layer list for freqLayListCsfbHighW MODPR high priority CSFB to cdma WCDMA

-

Frequency layer list for freqLayListCsfbNorm normal priority CSFB Wcdma to WCDMA

MODPR

-

Frequency layer list for freqLayListLte LTE inter frequency mobility

MODPR

-

Frequency layer list for freqLayListPsHoWcdm MODPR packet switched a handover WCDMA

-

Frequency layer list for freqLayListSrvccWcd SRVCC to WCDMA ma

MODPR

-

Reference freq. list network assisted cell change GERAN

MODPR

-

Band indicator applied bandIndicator to reference ARFCN

MODPR

refFreqListNaccGeran

Reference ARFCN

MODPR



referenceARFCN

DN09185982

Issue: 01D


Table 76


Full name Auto adaptation to freq. layers of all neighbour cells

Issue: 01D


Abbreviated name autoAdapt

Managed object

Structure

MODPR

-

Frequency layer list for freqLayListDedVoLteH MODPR ded. VoLTE intero frequency HO

-

Frequency layer list for freqLayListServiceBas MODPR VoLTE service based edHo HO

-

Percentage of UE for idle mode load balancing

idleLBPercentageOfU es

MODPR

-

Mobility default profile identifier

moDPrId

MODPR

-

Reference frequency refFreqListSrvccGsm list for SRVCC to GSM

MODPR

-


MODPR

refFreqListSrvccGsm

Reference ARFCN

referenceARFCN

MODPR

refFreqListSrvccGsm

Idle mode mobility profile identifier

moimpId

MOIMP

-

Percentage of UE for idle mode load balancing

idleLBPercentageOfU es

MOPR

-

Mobility profile identifier

moPrId

MOPR

-

Frequency layer list for freqLayListCsfbHighW MOPR high priority CSFB to cdma WCDMA

-

Frequency layer list for freqLayListCsfbNorm normal priority CSFB Wcdma to WCDMA

MOPR

-

Frequency layer list for freqLayListDedVoLteH MOPR ded. VoLTE intero frequency HO

-

Frequency layer list for freqLayListLte LTE inter frequency mobility

MOPR

-

Frequency layer list for freqLayListPsHoWcdm MOPR packet switched a handover WCDMA

-

Frequency layer list for freqLayListServiceBas MOPR VoLTE service based edHo HO

-

Frequency layer list for freqLayListSrvccWcd SRVCC to WCDMA ma

-

DN09185982

MOPR

167


Table 76



Full name Reference freq. list network assisted cell change GERAN

Abbreviated name refFreqListNaccGeran

Managed object

Structure

MOPR

-


MOPR


Reference ARFCN

MOPR


Reference frequency refFreqListSrvccGsm list for SRVCC to GSM

MOPR

-


MOPR

refFreqListSrvccGsm

Reference ARFCN

MOPR

refFreqListSrvccGsm

referenceARFCN

referenceARFCN




ASW

SW asset monitoring


3.13.2 Activating and configuring LTE1905: PLMN ID and SPID Selected Mobility Profiles Before you start Table 78: Parameters used for activating and configuring LTE1905: PLMN ID and SPID Selected Mobility Profiles lists the parameters used for activating and configuring the LTE1905: PLMN ID and SPID Selected Mobility Profiles feature. Table 78

Parameters used for activating and configuring LTE1905: PLMN ID and SPID Selected Mobility Profiles Parameter

168

Purpose


Activate selective mobility profiles (actSelMobPrf) LNBTS

activation flag

no

Mobility profile selection mode (moProfileSelect) LNBTS


no

Mobility profiles mapping list (moPrMappingList) LNCEL parameters structure


no

Last subscriber profile ID of a range (spidLast)


no

Mobile country code (mcc)


requires object locking

Mobile network code (mnc)



Mobile network code length (mncLength)



Mobility profile ID (moPrId)


no

DN09185982

Issue: 01D


Table 78


Parameters used for activating and configuring LTE1905: PLMN ID and SPID Selected Mobility Profiles (Cont.) Parameter

Purpose


Subscriber profile ID (spid)


no

Mobility profile identifier (moPrId) MOPR


no

Idle mode mobility profile identifier (moimpId) MOIMP


no

Idle mode mobility default profile identifier (modimpId) MODIMP


no

The LTE1905: PLMN ID and SPID Selected Mobility Profiles feature is activated by the Activate selective mobility profiles (actSelMobPrf) and Mobility profile selection mode (moProfileSelect) LNBTS parameters. The LTE490: Subscriber Profile-based Mobility feature is activated by the same Activate selective mobility profiles (actSelMobPrf) LNBTS parameter. Procedure 1


2

Activate the LTE1905: PLMN ID and SPID Selected Mobility Profiles feature. a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. If not already done, set the Activate selective mobility profiles (actSelMobPrf) parameter's value to true. e) Set the Mobility profile selection mode (moProfileSelect) parameter's value to plmn or combined.

g

Note: During migration from the previous release to the FDD-LTE 15A, the already configured value of the Mobility profile selection mode (moProfileSelect) parameter is kept. The new value of this parameter, combined, can only be set after the migration to FDD LTE15A.

3

Configure the Mobility profile ID (moPrMappingList) parameters' structure. a) Expand the LNBTS object. b) Right-click the LNCEL object.

Issue: 01D

DN09185982

169



c) Select the New Mobility profiles mapping list object. d) Set the parameters' values of the Mobility profiles mapping list (moPrMappingList) structure according to your expectations. When configuring, follow one of the below scenarios: •

In case Mobility profile selection mode (moProfileSelect) parameter's value is set to plmn, configuration of the following parameters is mandatory: – – – –

•

Mobile country code (mcc) Mobile network code (mnc) Mobile network code length (mncLength) Mobility profile ID (moPrId)

In case the Mobility profile selection mode (moProfileSelect) parameter's value is set to combined, follow one of the following configurations scenarios: –

• • • •

–

• • •

–

• • • • • •

g

170

Mobile country code (mcc) Mobile network code (mnc) Mobile network code length (mncLength) Mobility profile ID (moPrId) Subscriber profile ID (spid) Last subscriber profile ID of a range (spidLast) Mobility profile ID (moPrId) Mobile country code (mcc) Mobile network code (mnc) Last subscriber profile ID of a range (spidLast) Mobile network code length (mncLength) Subscriber profile ID (spid) Mobility profile ID (moPrId)

Note: If there is no element of the moPrMappingList configured, MODPR will be used.

DN09185982

Issue: 01D


g

Note: If the Mobility profile selection mode (moProfileSelect) parameter's value was plmn in the previous release ( LTE486: PLMN ID Selected Mobility Profiles was activated), then after migration to the FDD-LTE 15A the operator should check and configure, if needed, the following LNCEL parameters in the Mobility profiles mapping list (moPrMappingList) parameters' structure: • • •

4


Mobile country code (mcc) Mobile network code (mnc) Mobile network code length (mncLength) LNCEL parameters in the Mobility profiles mapping list(moPrMappingList) parameters' structure

Create the MOPR object. a) Right-click the LNBTS object. b) Select the new MOPR object. c) Set the Mobility profile identifier (moPrId) parameter's value.

g

Note: The Mobility profile identifier (moPrId) parameter's value in the MOPR object needs to be equal to the Mobility profile ID (moPrId) in the Mobility profiles mapping list (moPrMappingList) parameters' structure.

5


Expected outcome The LTE1905: PLMN ID and SPID Selected Mobility Profiles and LTE490: Subscriber Profile-based Mobility features are activated.

3.13.3 Deactivating LTE1905: PLMN ID and SPID Selected Mobility Profiles with the actSelMobPrf parameter Before you start The Activate selective mobility profiles (actSelMobPrf) or Mobility profile selection mode (moProfileSelect) parameter is used for deactivation. Modification of the parameter requires neither eNB restart nor cell locking.

Issue: 01D

DN09185982

171



Procedure 1


2

Deactivate the LTE1905: PLMN ID and SPID Selected Mobility Profiles and LTE490: Subscriber Profile-based Mobility features with the actSelMobPrf parameter. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate selective mobility profiles (actSelMobPrf) parameter's value to false.


Expected outcome The LTE1905: PLMN ID and SPID Selected Mobility Profiles and LTE490: Subscriber Profile-based Mobility features are deactivated.

3.13.4 Deactivating LTE1905: PLMN ID and SPID Selected Mobility Profiles with the moProfileSelect parameter Before you start The Activate selective mobility profiles (actSelMobPrf) or Mobility profile selection mode (moProfileSelect) parameter is used for deactivation. Modification of the parameter requires neither eNB restart nor cell locking. Procedure 1


2

Deactivate the LTE1905: PLMN ID and SPID Selected Mobility Profiles feature. a) Go to the Radio Network Configuration page.

172

DN09185982

Issue: 01D



b) Expand the MRBTS object. c) Select the LNBTS object. d) Set the Mobility profile selection mode (moProfileSelect) parameter's value to spid.

3



The LTE1905: PLMN ID and SPID Selected Mobility Profiles feature is deactivated. If the actSelMobPrf = true, the eNB supports SPID-based mobility profile selection as in the LTE490: Subscriber Profile-based Mobility feature.

3.14 LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List 3.14.1 Description of LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List Introduction to the feature The LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List feature introduces a mechanism for controlling which target layers are used for inter-frequency handovers during ongoing Voice Over LTE (VoLTE) calls. Benefits End-user benefits No effect on the end-user experience. Operator benefits Feature benefits: • • •

possibility to control the LTE frequency layers used by VoLTE the operator can configure a specific list of allowed VoLTE target frequency layers within mobility profiles better resource management

Requirements Hardware and software requirements Table 79: Hardware and software requirements list the hardware and software requirements for the LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List feature.

Issue: 01D

DN09185982

173


Table 79



System release





FDD-LTE15A

-

FL15A

FL15A

-


OMS

UE

NetAct

MME

SAE GW

-

-

-

15.5

-

-

Additional hardware requirements This feature requires no new or additional hardware. Functional description Concept of frequency layers in the LTE1942 feature The LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List feature introduces a mechanism to control which target layers are used for inter-frequency handovers (HO) during ongoing VoLTE (Voice Over LTE) calls. When the LTE1942 feature is enabled, the eNB uses a specific dedicated target list of frequencies for all types of inter-frequency handovers (including coverage, load, and service-based HOs), both inter- and intra-eNB.

g

Note: All eNBs within the same network should be configured with the same list of frequencies allowed for VoLTE handovers. Examples of how the frequency layers can be defined, and how it influences the handovers are shown in Figure 10: Example of frequency layers in the LTE1942 feature. Figure 10

Example of frequency layers in the LTE1942 feature

Inter-frequencyVoLTEhandoverscenario: IFHOnotallowed (nofrequency layersconfigured)

IFHOallowedto cellsonf1,f2,f3 frequencylayers

IFHOallowedto cellsonf1freq. layeronly

f3

f3

f3

f2

f2

f2

f1

f1

f1

f0

f0

f0

neighboringfreq. layernotallowed forIFVoLTEHO neighboringfreq. layerconfigured inLTE1942list serving frequency

The LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List feature is corelated with the LTE1127: Service-based Mobility Trigger feature. If LTE1127 is activated, there is a consistency check between the LTE1127 and LTE1942 features' target layer lists. All LTE1127 target frequencies must be included within the LTE1942 feature's target

174

DN09185982

Issue: 01D



layer list. An exemplary scenario of VoLTE inter-frequency handovers when both LTE1127 and LTE1942 are active is shown in Figure 11: Example of frequency layers in the LTE1942 feature when LTE1127 is active. Figure 11

Example of frequency layers in the LTE1942 feature when LTE1127 is active

Inter-frequencyVoLTEhandoverscenario: LTE1127 frequencylist: LTE1942 frequencylist:

empty

empty

f1

empty

f1

f1 f2

VoLTEHOnotallowed inallconfiguredlayers (VoLTEcallsarenot shiftedwithSBHO)

VoLTEHOallowed onlytof1(VoLTEcalls onf2,f3,f4arenotshifted tof1withSBHO)

VoLTEHOallowedonly tof1andf2(VoLTEcalls onf2,f3,f4areshifted tof1withSBHO)

f4

f4

f4

f3

f3

f3

f2

f21

f21

f1

f1

f1

neighboringfreq.layer notallowedforIFVoLTEHO

freq.inLTE1942list

freq.inLTE1942 andLTE1127list

Target frequencies list in the LTE1942 feature The LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List enters a new list inside mobility profiles (MOPR) and mobility default profile (MODPR) objects to configure a dedicated VoLTE inter-frequency target list. This list is used during inter-frequency handovers for UEs with an established QCI1 bearer (after establishment of bearer with QCI1 and in case when QCI1 is already established with Initial Context Setup) or UEs with established QCI1 entering cell via handover or RRC connection re-establishment. Configuration of the list is performed by the operator using Frequency layer list for ded. VoLTE inter-frequency HO parameter. Only target frequencies layers configured in the LTE1942 list are taken into account before an HO by eNB for: • •

measurement configuration measurement reports filtering

During a target cell selection, the eNB prevents the UE with an established QCI1 bearer from being handed over to a target cell which is not located on a dedicated VoLTE target frequency layer.

g

Note: At least the default mobility profile (MODPR) has to be created with the LTE1942 list to make inter-frequency VoLTE handovers possible. System impact Interdependencies between features

Issue: 01D

DN09185982

175



The following features need to be activated before the activation of the LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List feature: • •

LTE10: EPS bearers for conversational voice LTE55: Inter-frequency handover

Features that are affecting the LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List feature: • •

•

LTE1060: TDD - FDD handover - necessary if FDD/TDD handover is needed LTE1127: Service Based Mobility Trigger - when LTE1127 is activated; the content of the LTE1127 frequency layer list for service-based mobility must be added to the VoLTE target frequency layer list (LTE1942) LTE490: Subscriber profile based mobility –

–

•

If LTE490 is deactivated and the Auto adaptation to freq. layers of all neighbour cells (autoAdapt) is configured with the value 'true,' the VoLTE inter-frequency handover is not allowed. If LTE490 is activated and the UE cannot be mapped to a mobility profile where the Auto adaptation to freq. layers of all neighbour cells (autoAdapt) is configured with value 'true,' the VoLTE inter-frequency handover is not allowed. Otherwise, the configuration in the mobility profile will be used.

LTE1170: Inter-frequency load balancing: The LTE1170/LTE1531/LTE1387 feature bundle provide load balancing for interfrequency targets and the LTE1841 feature provides load equalization using LB HO. They can be activated in parallel with LTE1942, however if QCI1 is established only target frequencies from LTE1942 shall be used. If LTE1942 is enabled and QCI1 is established, then list of allowed targets for inter-frequency handover is reduced to dedicated target list for VoLTE.

Impact on interfaces No impact on interfaces. Impact on network management tools No impact on network management tools. Impact on system performance and capacity No impact on system performance or capacity. Management data Alarms No alarms are related to this feature. Measurements and counters No measurements or counters are related to this feature. Key performance indicators No key performance indicators are related to this feature.

176

DN09185982

Issue: 01D



Parameters Table 80: New parameters lists new parameters related to the LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List feature. Table 80


Abbreviated name

Managed object

Activate dedicated VoLTE inter-frequency handover

actDedVoLteInterFreqHo

LNBTS

Frequency layer list for ded. VoLTE inter-frequency HO

freqLayListDedVoLteHo

MODPR

Frequency layer list for ded. VoLTE inter-frequency HO

freqLayListDedVoLteHo

MOPR

Table 81: Related existing parameters lists existing parameters related to the LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List feature. Table 81


Abbreviated name

Auto adaptation to freq. layers of all neighbour cells

autoAdapt

Managed object MODPR

Sales information Table 82: Sales information list sales information related to the LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List feature. Table 82



ASW

SW Asset Monitoring


3.14.2 Activating and configuring LTE1942: Dedicated VoLTE Inter-Frequency Target Frequency List Before you start Table below lists parameters used during activation and configuration of the feature. Table 83

Parameters used for activating and configuring the LTE1942: Dedicated VoLTE Inter-Frequency Target Frequency List Parameter

Purpose

Activate dedicated VoLTE interfrequency handover (actDedVoLteInterFreqHo)

activation flag

Frequency layer list for ded. VoLTE optional configuration inter-frequency HO (freqLayListDedVoLteHo)

Issue: 01D

DN09185982


no

177



The following features need to be activated before the activation of the LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List feature: •

•

LTE10: EPS bearers for conversational voice (Activate support of conversational voice bearer (actConvVoice)) which requires LTE7: Support of multiple EPS bearer (Activate Multiple bearers (ActMultBearers)) LTE55: Inter-frequency handover (Enable InterFrequency Handover (actIfHo) )

Additionally, The MODPR Auto adaptation to freq. layers of all neighbour cells (autoAdapt) parameter must be set to 'false' otherwise interfrequency handovers will not start. To activate and configure the feature, do the following: Procedure 1

Follow the general procedure described in section Activating and deactivating LTE features using the BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure, perform the steps described in this procedure.

2

Activate the feature flag for the LTE1942 feature. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate dedicated VoLTE inter-frequency handover (actDedVoLteInterFreqHo) parameter value to true.

Optional: Configure the frequency layers. a) Select the LNBTS object. b) If not existing. right click LNBTS object, then create and configure MOPR and/or MODPR instance. c) Set the Frequency layer list for ded. VoLTE inter-frequency HO (freqLayListDedVoLteHo) parameter to a desired value.

g

Note: If LTE1127 is enabled , then the MOPR/MODPR Frequency layer list for ded. VoLTE inter-frequency HO (freqLayListDedVoLteHo) list must contain frequencies of corresponding MOPR/MODPR Frequency layer

list for VoLTE service based HO (freqLayListServiceBasedHo.)

4

Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using the BTS Site Manager.

Expected outcome

178

DN09185982

Issue: 01D



The eNB provides support for dedicated VoLTE inter-frequency target lists.

3.14.3 Deactivating LTE1942: Dedicated VoLTE Inter-Frequency Target Frequency List Before you start The Activate dedicated VoLTE inter-frequency handover (actDedVoLteInterFreqHo) parameter is used for deactivation. Modification of this parameter does not require either an eNB restart or cell locking. To deactivate the feature, do the following: Procedure 1


2

Deactivate the feature flag for the LTE1942 feature. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate dedicated VoLTE inter-frequency handover (actDedVoLteInterFreqHo) parameter value to false.


Expected outcome The eNB stops supporting dedicated VoLTE inter-frequency target lists.

3.15 LTE1944: Dynamic Handover Blacklisting 3.15.1 Description of LTE1944: Dynamic Handover Blacklisting Introduction to the feature With the LTE1944: Dynamic Handover Blacklisting feature, if the success of a handover (HO) preparation is considered unlikely, the HO is temporarily blacklisted. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits

Issue: 01D

DN09185982

179



Unnecessary handover preparation retrials are reduced as a result of blacklisting selected handovers. Requirements Hardware and software requirements Table 84 System release FDD-LTE 15A




OMS -

FL15A

UE -


FL16

NetAct -


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Dynamic blacklisting is applied to every type of intra-LTE inter-eNB handover, except for emergency services. Target cells are temporarily blacklisted for a handover in one of the following cases: •

•

The handover preparation supervision timer (TX2RELOCPrep for an X2 handover or TS1RELOCPrep for an S1 handover) expires after several consecutive handover preparation attempts. The number of HO preparation attempts is operatorconfigurable. The handover preparation is rejected by the target eNB with one of the following cause values: – – –

Radio Network Layer Cause (Cell not Available) Miscellaneous Cause (Control Processing Overload) Miscellaneous Cause (Not enough User Plane Processing Resources)

Handover Preparation For a handover preparation, the source eNB sends a message to the target eNB (X2AP: Handover Request) or to the target MME (S1AP: Handover Required) and starts the supervision timer for the HO preparation. If the timer (TX2RELOCPrep or TS1RELOCPrep) expires and the target cell does not respond, the source eNB increments an internal target cell-specific counter for HO preparation timeouts. If no HO preparation has timed out before, the counter is initialized with 1. The operator can configure the counter. If the counter reaches the threshold: • •

The source eNB starts the timer for dynamic blacklisting of the target cell. The source eNB resets the internal target cell-specific counter for HO preparation timeouts to 0.

As a result, one of the scenarios might take place:

180

DN09185982

Issue: 01D


• •


The source eNB suspects the target cell to be a sleeping cell and starts counting the HO preparation timeouts. The source eNB considers the target cell to be a sleeping cell. The target cell is blacklisted for an HO (except an emergency service) as long as the dynamic blacklisting timer is running. The Number of dynamic handover blacklisting occurrences counter is incremented.

If the target eNB responds to the HO preparation request by X2AP: Handover Request Acknowledge, X2AP: Handover Preparation Failure, S1AP: Handover Command or S1AP: Handover Preparation Failure, the source eNB resets the internal target cellspecific counter for HO preparation timeouts to 0. The target cell is not suspected to be a sleeping cell. The target eNB can reject an HO preparation. Then the source eNB starts the timer for dynamic blacklisting of the target cell. The target cell is blacklisted for an HO (except an emergency service) as long as the dynamic blacklisting timer is running. The Number of dynamic handover blacklisting occurrences counter is incremented. When the dynamic blacklisting timer for the target cell is running, the source eNB eliminates this cell from the target cell list. The eNB does not trigger a handover preparation towards the dynamically-blacklisted target cell. Cause values For blacklisting of barred cells or cells with a control plane (C-plane) or user plane (Uplane) overload, the source eNB relies on the cause values within the Handover Preparation Failure message. For an X2 handover: • •

The Nokia target eNB sets the cause values correctly. A foreign vendor's target eNB behavior is unknown.

For an S1 handover: • •

In a pure Nokia environment, for an intra-MME handover, cause values are propagated correctly from the target eNB via the MME to the source MME. If any of the MMEs or the target eNB is from a foreign vendor, the end-to-end behavior is unknown.

System impact Interdependencies between features •

•

•

Issue: 01D

LTE53: Intra and Inter eNB Handover with X2 Dynamic blacklisting according to the LTE1944: Dynamic Handover Blacklisting feature is applied when target cells for an X2-handover according to LTE53: Intra and Inter eNB Handover with X2 feature are selected. LTE54: Intra-LTE Handover via S1 Dynamic blacklisting according to the LTE1944: Dynamic Handover Blacklisting feature is applied when target cells for an S1-handover according to the LTE54: IntraLTE Handover via S1 feature are selected. LTE55: Inter-frequency Handover Dynamic blacklisting according to the LTE1944: Dynamic Handover Blacklisting feature is applied when inter-frequency target cells according to the LTE55: Interfrequency Handover feature are selected.

DN09185982

181


•

•

•

•

•

•


LTE1047: Control Plane Overload Handling With the LTE1944: Dynamic Handover Blacklisting feature, reception of a handover preparation failure with a "Miscellaneous Cause (Control Processing Overload)" cause value is a trigger condition for dynamic blacklisting. This is the only situation where a Nokia target eNB uses this cause value. It is not known whether a foreign vendor's target eNB uses the "Miscellaneous Cause (Control Processing Overload)" cause value. LTE1127: Service Based Mobility Trigger Dynamic blacklisting according to the LTE1944: Dynamic Handover Blacklisting feature is applied to service-based handovers according to the LTE1127: Service Based Mobility Trigger feature. LTE1170: Inter eNB IF Load Balancing, LTE1531: Inter-frequency Load Balancing Extension, LTE1841: Inter-Frequency Load Equalization Dynamic blacklisting according to the LTE1944: Dynamic Handover Blacklisting feature is applied to load-based handovers. LTE1617: RLF Triggered Handover If an RLF-triggered handover preparation is rejected due to a barred target cell, CPlane overload, or U-Plane overload, the target cell is blacklisted according to the LTE1944: Dynamic Handover Blacklisting feature. LTE2023: User Plane Overload Handling With the LTE1944: Dynamic Handover Blacklisting feature, reception of a handover preparation failure with a "Miscellaneous Cause (Not enough User Plane Processing Resources)" cause value is a trigger condition for dynamic blacklisting. This is the only situation where a Nokia target eNB uses this cause value. It is not known whether a foreign vendor's target eNB uses the "Miscellaneous Cause (Not enough User Plane Processing Resources)" cause value. LTE2108: Redirected VoLTE Call Setup Dynamic blacklisting according to the LTE1944: Dynamic Handover Blacklisting feature is applied to forced service-based handovers according to the LTE2108: Redirected VoLTE Call Setup feature.

Impact on interfaces No impact on interfaces. Impact on network management tools No impact on network management tools. Impact on system performance and capacity No impact on system performance or capacity. Management data Alarms No alarms are related to this feature. Measurements and counters Table 85: New counters lists counters introduced with the LTE1944: Dynamic Handover Blacklisting feature.

182

DN09185982

Issue: 01D


Table 85


New counters

Counter ID

Counter name

M8014C21

Number of dynamic handover blacklisting occurrences

Measurement 8014 - LTE Inter eNB Handover (WBTS)

Key performance indicators No key performance indicators are related to this feature. Parameters Table 86: New parameters lists the parameters introduced with the LTE1944: Dynamic Handover Blacklisting feature. Table 86


Abbreviated name

Managed object

Activate temporary handover blacklisting

actTempHoBlacklisting

LNBTS

Duration for dynamic blacklisting

dynBlacklistingHoTimer

LNBTS

Number of consecutive HO preparation timeouts

nConsecHOPrepTimeouts

LNBTS

Sales information Table 87: Sales information provides sales information regarding the LTE1944: Dynamic Handover Blacklisting feature. Table 87



BSW

-


3.15.2 Activating and configuring LTE1944: Dynamic Handover Blacklisting Before you start Table 1 lists Parameters used for activating and configuring LTE1944 Table 88

Parameters used for activating and configuring LTE1944: Dynamic Handover Blacklisting Parameter

Issue: 01D

Purpose


Activate temporary handover blacklisting (actTempHoBlacklisting)

activation flag

no

Duration for dynamic blacklisting (dynBlacklistingHoTimer)


no

DN09185982

183


Table 88


Parameters used for activating and configuring LTE1944: Dynamic Handover Blacklisting (Cont.) Parameter

Number of consecutive HO preparation timeouts (nConsecHOPrepTimeouts)

Purpose mandatory configuration


Procedure 1


2

Activate the LTE1944: Dynamic Handover Blacklisting feature. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate temporary handover blacklisting (actTempHoBlacklisting ) parameter's value to true.

Configure the LTE1944: Dynamic Handover Blacklisting feature. a) Select the LNBTS object. b) Set the Number of consecutive HO preparation timeouts (nConsecHOPrepTimeouts) and the Duration for dynamic blacklisting (dynBlacklistingHoTimer) parameters' values.

4


Expected outcome The LTE1944: Dynamic Handover Blacklisting feature is activated. The eNB applies dynamic blacklisting.

3.15.3 Deactivating LTE1944: Dynamic Handover Blacklisting Before you start The Activate temporary handover blacklisting (actTempHoBlacklisting) parameter is used for deactivation. Modification of this parameter requires neither eNB restart nor cell locking.

184

DN09185982

Issue: 01D



Procedure 1


2

Deactivate the LTE1944: Dynamic Handover Blacklisting feature. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate temporary handover blacklisting (actTempHoBlacklisting ) parameter's value to false.


Expected outcome The LTE1944: Dynamic Handover Blacklisting feature is deactivated. The eNB stops applying dynamic blacklisting.

3.16 LTE2006: Flexible SCell Selection 3.16.1 LTE2006: Flexible SCell Selection 3.16.1.1

Description of LTE2006: Flexible SCell Selection Introduction to the feature The LTE2006: Flexible SCell Selection feature optimizes the UE throughput as well as the SCell resource utilization, changing the current SCell to another suitable one which is detected by the UE with a better radio quality. Benefits End-user benefits This feature optimizes the UE throughput as well as the SCell resource utilization, changing the current SCell to another suitable one with better radio quality which is detected by the UE. This way the UE will be always served by the best possible SCells, without interrupting the CA functionality, which results in faster data transfer. Operator benefits This feature enables a flexible assignment of serving cells in downlink carrier aggregation. The LTE2006: Flexible SCell Selection feature also allows CA in such deployment scenarios where a PCell and a candidate SCell do not fully overlap, and more than one candidate SCell per PCell exists. This refers to scenario #3 from 3GPP TS 36.300.

Issue: 01D

DN09185982

185



Requirements Hardware and software requirements Table 89


System release

FDD-LTE 15A

Flexi Zone Controller Support not required



OMS

UE

Support not required

3GPP R10

Flexi Zone Micro BTS Support not required

NetAct NetAct 15.5

Flexi Zone Access Point Support not required

MME Support not required

SAE GW Support not required

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview The Flexi Multiradio BTS supports a flexible SCell selection for downlink carrier aggregation for up to three aggregated cells per UE. Up to five SCell candidates can be configured per PCell and up to two carrier frequencies. The candidate SCells with the same carrier frequency shall also have the same frequency bandwidth. The C-RNTI code space is equally partitioned among the eNB cells belonging to the same C-RNTI group and having the same caPoolID. The configuration of the Carrier aggregation pool ID (caPoolID) has the following constraints: •

a maximum of thirteen eNB cells can have the same Carrier aggregation

•

pool ID (caPoolID) PCell and all its candidate SCells must have the same Carrier aggregation pool ID (caPoolID)

The concept of C-RNTI group has been defined to avoid a C-RNTI collision between the PCell and its candidate SCells. The drawback is that it proportionally reduces the CRNTI code space available per cell with the number of cells belonging to the same CRNTI group. SCells are added blindly, according to the respective SCell priority (SCellPrio); from the UE candidate SCells with the same carrier frequency, the one having the highest priority (that is, having assigned the lowest value to the “SCellPrio” parameter in the respective CAREL object) is selected. Together with the blind SCell configuration, an eNodeB activates a measurement event for UEs with according capabilities in order to find a better intra-frequency SCell. The A6 measurement is operator-configurable per carrier frequency according to the respective carrier aggregation (default) profile CA(D)PR. Upon receiving an A6 measurement report, the eNodeB checks whether the reported cell is an SCell candidate for carrier aggregation, and whether it has sufficient resources to serve as an SCell.

186

DN09185982

Issue: 01D



SCell candidates for the flexible SCell functionality are pre-configured cells of the same eNodeB with a different center frequency as the PCell. They are modeled with CAREL objects. After the above-mentioned checks have been passed, the new SCell is configured (replaces the current SCell). All the SCell-related timers and counters are reset with the SCell change. The SCell change does not trigger a PCell change. The functionality is enabled/disabled via O&M settings per eNodeB. System impact Interdependencies between features At least one of the following CA features must be activated/configured before the activation of the LTE2006: Flexible SCell Selection feature: • • • • •

LTE1089: Downlink Carrier Aggregation - 20 MHz LTE1332: Downlink Carrier Aggregation - 40 MHz LTE1562: Carrier Aggregation for Multi-carrier eNodeBs LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz

The LTE1382: Cell Resource Groups feature and the LTE2006: Flexible SCell Selection feature exclude each other. Impact on interfaces This feature has no impact on interfaces. Impact on network management tools With the LTE2006: Flexible SCell Selection feature activated, the iSON manager supports carrier aggregation for a PCell up to max of five candidate secondary cells. Each primary cell can have max of five SCells at a given frequency layer. Impact on system performance and capacity This feature impacts system performance and capacity as follows: For some UEs and chip-sets, every SCell configuration/de-configuration and SCell activation/deactivation, as well as every measurement pertaining to the configured SCells, might be accompanied by a PDSCH and PUSCH micro interruption on a PCell. However, since frequent re-configuration should be avoided with appropriate parameter settings, the throughput impairments should be negligible. Management data Alarms There are no alarms related to this feature. Measurements and counters Table 2: New counters lists counters introduced with this feature.

Issue: 01D

DN09185982

187


Table 90



Counter name

M8011C165

Number of Event A6 triggered SCell swaps

Measurement 8011 - LTE Cell Resource (WBTS)

Key performance indicators There are no key performance indicators related to this feature. Parameters Table 3: New Parameters lists parameters introduced with this feature. Table 91

New parameters

Full name

Abbreviated name

Managed object

Structure

Activate flexible SCell selection

actFlexSCellSelect

LNBTS

-

A6 offset

a6Offset

CADPR/CAPR

-

A6 report interval

a6ReportInterval

CADPR/CAPR

-

A6 time to trigger

a6TimeToTrigger

CADPR/CAPR

-

CADPR/CAPR

-

disableSCellPDCCHOl CADPR/CAPR La

-

Carrier aggregation caDPrId default profile identifier Disable PDCCH outer loop link adaptation in SCell

Enable measurements enableA6Event for A6 event

CADPR/CAPR

-

Related hysteresis of offset a6Offset neighbor cell

hysA6Offset

CADPR/CAPR

-

Downlink EARFCN of the SCell frequency layer

earfcnDL

CAPR

-

Enable measurements enableA6Event for A6 event

CAPR

-

Related hysteresis of offset a6Offset neighbor cell

hysA6Offset

CAPR

-

SCell priority

scellPrio

CAREL

-

Measurement cycle on SCellMeasCycle configured SCells

LNBTS

-

Carrier aggregation pool ID

LNCEL

-

caPoolId


188

DN09185982

Issue: 01D


Table 92



Full name

Abbreviated name

Scheduling CA fairness control factor

caSchedFairFact

Managed object

Structure

LNBTS

-




ASW

SW asset monitoring


3.17 LTE2023: User Plane Overload Handling 3.17.1 Description of LTE2023: User Plane Overload Handling Introduction to the feature The LTE2023: User Plane Overload Handling feature provides a user plane (U-plane) overload monitoring and handling mechanism for the eNB. Benefits End-user benefits This feature enables an on-going service optimization even in high load or overload situations. Operator benefits This feature: guarantees a stable operation of the eNB's high U-plane load, and thus ensures a high U-plane throughput in case of a heavy load issues a warning message via NetAct or the BTS Site Manager (BTS SM) when the eNB is overloaded helps with network planning

• • •

Requirements Hardware and software requirements Table 94: Hardware and software requirements presents the hardware and software requirements for this feature. Table 94 System release FDD-LTE 15A



Issue: 01D


OMS -

UE -

DN09185982



FL15A

-

NetAct

MME

NetAct 15.5

-

SAE GW -

189



Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview The LTE2023: User Plane Overload Handling feature is one of a series of features designed to handle overload situations within the eNB. Its aim is to avoid unstable operation of the eNB due to a high U-plane load. The LTE2023: User Plane Overload Handling feature intends to handle as much U-plane traffic or load as possible. It is obtained by: • • • •

avoiding allocation of additional traffic implementing a separate U-plane overload state machine using the existing overload counter-measures adding the additional counter-measures

The high U-plane load, or a U-plane overload, is expected in various situations in which there is a permanent or temporary increase in traffic and users. If the overload cases happen too often, it is advisabe to examine both the traffic and the traffic profile in a more detailed way. The LTE2023: User Plane Overload Handling feature enables issuing warnings about an overload via NetAct or the BTS SM (see Figure 12: U-plane overload handling). Those alarms are generated by the eNB when a U-plane overload state transition varies from U-plane overload level 0 (UPOVL0) to U-plane overload level 1/2 (UPOVL1/2). The alarm is cleared in case of overload state transition varies from UPOVL1 to UPOVL0. The alarms include the start or end time and the type of overload. To avoid spamming, they are generated only in the case a U-plane overload condition lasts longer than one minute. In addition, if the U-plane overload counter-measures are enabled, the eNB handles as much U-plane traffic as possible, even if the traffic demand is above its specification and keeps itself within a stable operating condition. Figure 12

U-plane overload handling NetAct

overload warningmessage

U-plane overloadinformation

Client

eNB

BTSSM

U-plane overload management The U-plane overload is detected by evaluating a certain overload level metrics. There are the following overload levels for the U-plane overload: •

190

overload level 0 (normal operation – when the U-plane overload level is zero)

DN09185982

Issue: 01D


• •


overload level 1 (graceful overload handling – the goal of these counter-measures is to avoid a further U-plane traffic increase and to reduce the U-plane load) overload level 2 (preserving stability, self-defense U-plane overload handling – the goal of these counter-measures is not only to avoid a further U-plane traffic increase but also to reduce the U-plane load in a non-graceful manner)

The overload detection mechanism allows to differentiate a peak load scenario from a sustained traffic increase. The overload management function realizes the load control loop, including timed-out values for the different load levels and the corresponding overload actions (activation or deactivation). The LTE2023: U-Plane Overload feature triggers the following mechanisms: 1. U-plane overload trigger based on QoS and packet scheduler load control (UPOVT1): The number of UEs which can be scheduled by packet scheduler due to the U-plane load is fewer than the number of UEs which should be scheduled to meet the guaranteed service quality. This trigger is based on the QoS associated with VoLTE calls, as VoLTE is expected to be the most critical service in this aspect. 2. U-plane overload trigger based on the number of UEs to be scheduled and packet scheduler load control (UPOVT2): packet scheduler can schedule only very few UEs per TTI due to the U-plane load; no matter whether the quality of service is impacted or not. 3. U-plane overload trigger based on DL-physical layer overload detection (UPOVT3): DL-physical layer overload might take place, for example, in scenarios with a high load and where each UE uses two code words. In this case U-plane data packets for some scheduled UEs cannot be processed in due time by the DL-physical layer and are not transmitted on the air interface. Table 95

Mapping between U-plane overload triggers and the related countermeasures Rejection of RRC (UPOVCM1)

Rejection of HO (UPOVCM2)

Rejection of E-RAB (UPOVCM3)

Switch to TxDiv (UPOVCM4)

No SRS (UPOVCM5)

Packet scheduler load control quality based trigger (UPOVT1)

X

X

X

X

X

Packet scheduler load control quantity based trigger (UPOVT2)

X

X

X

-

-

DL-physical layer overload trigger (UPOVT3)

-

-

-

X

-

U-plane overload counters and actions In case of overload level 1 (UPOVL1), the eNB performs the following counter actions: •

Issue: 01D

a rejection of low priority radio resource control (RRC) connection requests (establishment cause set to delayTolerantAccess, mo-data, mo-signaling, spare2, or spare1) – UPOVCM1

DN09185982

191


•


a rejection of an incoming non-emergency handover (HO) without a GBR bearer in combination and/or with HO cause other than time critical handover (TCH) or handover desirable for radio reasons (HDFRR) – UPOVCM2

In case of overload level 2 (UPOVL2), the eNB performs the following counter actions: • •

a rejection of low priority RRC connection requests as defined in overload level 1 – UPOVCM1 a rejection of all non-emergency HOs – UPOVCM2

The ‘Miscellaneous cause – not enough user plane processing resources available’ cause value is used in case of a rejection. This feature is not limited to these overload counter-measures only. In addition, it introduces three extra counter-measures to enhance its own effectiveness (in case of overload level 1 and 2): •

a rejection of E-RAB setup requests – UPOVCM3 – –

– – •

the usage of a transmit diversity (TxDiv) transmission – UPOVCM4 –

–

•

initial context setup requests are admitted for all UEs, irrespective of the RRC establishment cause (in case of UPOVL1 or UPOVL1) E-RAB setup requests are admitted if the ARP value of at least one bearer in the E-RABtobesetup list matches the ARP value of emergency or high priority access (in case of UPOVL1 or UPOVL2) E-RAB setup requests are admitted if E-RABToBeSetupListBearerSUReq list contains at least one GBR bearer (in case of UPOVL1) otherwise, E-RAB setup request is rejected

in case of UPOVL1: dynamic switching from the TxDiv or single-stream (onecode-word) transmission to two code words is prevented as long as UPOVL1 is active; the TxDiv transmission mode is used instead in case of UPOVL2: all transmissions are done as the TxDiv transmission mode for all of the already established calls and new incoming calls (that is, all twocode-words transmissions) are switched to the TxDiv mode

a suspension of the sounding reference symbol (SRS) usage for the UL scheduling process – UPOVCM5 –

SRS is suspended as long as UPOVL1 or UPOVL2 is active

The U-plane overload counters The U-plane overload counters measure the time when the eNB is in the U-plane overload level 1 (M8001C299) or in U-plane overload level 2 (M8001C300). In addition, the M8013C66 counter counts the number of signaling connection requests rejected due to the U-plane overload. System impact Interdependencies between features There are interdependencies between the following features: •

192

LTE1047: C-plane Overload Handling

DN09185982

Issue: 01D


•

•

•

•


The LTE1047: C-plane Overload Handling feature uses the same overload philosophy as the LTE2023: User Plane Overload Handling feature, but the two features have separate procedures to handle overload situations. There are also different interactions depending on the same counter-measures enabled for a Cplane and U-plane overload handling. LTE1113: eICIC-Macro If the number of users per TTI is reduced due to eICIC, it is not taken into account for a U-plane overload decision or calculation. LTE1496: eICIC-Micro If the number of users per TTI is reduced due to eICIC, it is not taken into account for a U-plane overload decision or calculation. LTE1117: MBMS In case the number of users scheduled within a TTI will be used as an indication for a U-plane overload, MBMS sub-frames shall be excluded. LTE495: OTDOA In case the number of users scheduled within a TTI will be used as an indication for a U-plane overload, sub-frames carrying PRS shall be excluded.

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 In case the system is operated beyond its specification, or with other traffic profiles, or feature mixes, a U-plane overload might exist. In these cases, the system performance (values such as latencies, handover performance, and success rates as well as individual and cell throughput) will be degraded both with and without this feature having been activated. However, with this feature and counter-measures enabled, this degradation will be done in a definite way. The goal of these counter-measures is to ensure the quality of service for the admitted traffic and a stable operation of the system. In case of a U-plane overload, the system performance might be degraded, especially in cases where the U-plane overload counter-measures are enabled. The main impacts of the different counter-measures concern: • • • • • • • •

radio resource control (RRC) setup success rate uplink (UL) and downlink (DL) cell capacities related to the UL and DL throughput cell capacity with respect to the amount of all UEs in an RRC connected mode and with respect to the activated radio access bearers (RABs) HO success and HO preparation success rate drop rates E-RAB setup success rate U-plane throughput of a single UE in UL and DL MIMO open loop (OL) or closed loop (CL) usage of a dual stream

Management data BTS faults and reported alarms

Issue: 01D

DN09185982

193



Table 96: New BTS faults lists BTS faults introduced with this feature. Table 96

New BTS faults

Fault ID

Fault name


Alarm name

6120

EFaultId_UplaneOverlo 7655 adDetectedTrOneAI

CELL NOTIFICATION

6121

EFaultId_UplaneOverlo 7655 adDetectedTrTwoAI

CELL NOTIFICATION

6053

EFaultId_UplaneOverlo 7655 adDetectedTrThreeAI

CELL NOTIFICATION



Counter name

Measurement

M8001C299

Time period of user plane in overload level 1

LTE cell load

M8001C300

Time period of user plane in overload level 2

LTE cell load

M8013C66

Number of Signaling Connection Establishment Requests rejected due to User Plane overload

LTE UE State

Key performance indicators Table 98: New key performance indicators lists key performance indicators introduced with this feature. Table 98

New key performance indicators KPI ID

KPI name

LTE_5709a

E-UTRAN Percentage of Time the Cell was in the U-Plane Overload State

Parameters Table 99: New parameters lists parameters introduced with this feature. Table 99

New parameters

Full name

194

Abbreviated name

Managed object

Structure

Activate U-plane overload handling

actUplaneOvlHandling LNBTS

-

Enable incoming HO reduction

enableInHoRed

LNBTS

cpovlha

Enable RRC connection reduction

enableRrcConnRed

LNBTS

cpovlha

DN09185982

Issue: 01D


Table 99



Full name

Abbreviated name

Managed object

Structure

U-plane overload handling

upovlha

LNBTS

-

Enable rejection of ERAB setup requests

enableERabSetupRed LNBTS

upovlha

Enable rejection of incoming inter-eNB HO requests

enableInHoRed

LNBTS

upovlha

Enable rejection of RRC connection requests

enableRrcConnRed

LNBTS

upovlha

Enable suspension of SRS for scheduling

enableSuspendSrs

LNBTS

upovlha

Enable Tx diversity transmission

enableTxDivTransmiss LNBTS ion

upovlha


Sales information

BSW/ASW


BSW

-


3.17.2 Activating and configuring LTE2023: User Plane Overload Handling Before you start Table 101: Parameters used for activating and configuring LTE2023: User Plane Overload Handling lists parameters used for the activation and configuration of the LTE2023: User Plane Overload Handling feature. Table 101

Parameters used for activating and configuring LTE2023: User Plane Overload Handling Parameter

g

Issue: 01D

Purpose


Activate U-plane overload handling activation flag (actUplaneOvlHandling)

no

U-plane overload handling (upovlha) parameter's structure

no


Note: When configuring the feature, note that suitable parameter values may depend, among other things, on the cell's/eNB's location. For example, an eNB located in places with a high population density or within a stadium might require other parameter settings compared to those located in a rural area.

DN09185982

195



Procedure 1


2

Activate the LTE2023: User Plane Overload Handling feature. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Set the Activate U-plane overload handling (actUplaneOvlHandling) parameter value to true.

Configure the U-plane overload handling (upovlha) parameter. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. c) Right-click the LNBTS object and create a new U-plane overload handling parameter. Set the U-plane overload handling (upovlha) parameter values.

4


Expected outcome The LTE2023: User Plane Overload Handling feature is activated. Further information In case all counter-measures are disabled, the operator will still be informed about the start and end of the U-plane overload condition.

3.17.3 Deactivating LTE2023: User Plane Overload Handling Before you start The Activate U-plane overload handling (actUplaneOvlhandling) parameter is used for deactivation. Modification of this parameter requires neither an eNB restart nor cell locking.

196

DN09185982

Issue: 01D



Procedure 1


2

Deactivate the LTE2023: User Plane Overload Handling feature. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS. Set the Activate U-plane overload handling (actUplaneOvlhandling) parameter value to false.


Expected outcome The LTE2023: User Plane Overload Handling feature is deactivated.

3.18 LTE2051: Measurement based Idle Mode Load Balancing 3.18.1 Description of LTE2051: Measurement based Idle Mode Load Balancing Introduction to the feature The LTE2051: Measurement based Idle Mode Load Balancing feature enhances the Idle Mode Load Balancing (IMLB) mechanism. In the enhanced mechanism, the eNodeB uses the A4 based measurement to check the quality of an LTE target inter-frequency, which is selected as a primary target with a highest priority by the IMLB algorithm. Considering the measurement results, the eNodeB decides if dedicated priorities are added to the RRC Release message or not. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefit to the operator: •

prevents continuous cell reselection measurements

Requirements

Issue: 01D

DN09185982

197



Hardware and software requirements Table 102 System release FDD-LTE 15A

Hardware and software requirements Flexi Multiradio BTS FL15


Flexi Multiradio 10 BTS FL15

OMS -


Flexi Zone Micro BTS FL15

FL16

NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements The LTE2051: Measurement based Idle Mode Load Balancing feature requires no new or additional hardware. Functional description Functional overview The LTE2051: Measurement based Idle Mode Load Balancing feature introduces an enhancement mechanism for the existing idle mode load balancing (IMLB) algorithms. Within the scope of LTE2051: Measurement based Idle Mode Load Balancing feature, the eNodeB uses the A4 IMLB measurement to check the quality of LTE target interfrequency, which was selected as a primary target with a highest priority by the IMLB algorithm used in the LTE1677: Idle Mode Mobility Balancing Extensions feature. Considering the measurement results, the eNodeB decides if a dedicated priorities are added to the RRC Release message or not. The LTE2051: Measurement based Idle Mode Load Balancing feature enables the following functionalities: •

•

• •

•

the operator decides whether the LTE target inter-frequency layers configured for IMLB should be measured with A4 IMLB measurements before sending dedicated priorities to the idle mode or not the operator configures reference symbol received power (RSRP) and/or reference signal received quality (RSRQ) thresholds used for checking whether the target cell fulfills the power and quality requirements the eNodeB prolongs an existing inactivity timer to give the UE additional time to perform A4 IMLB measurements if the IMLB algorithm selects an LTE inter-frequency as a primary target and that LTE inter-frequency is allowed to run A4 IMLB measurements, then the eNodeB triggers the UE to start A4 IMLB measurements for that frequency before sending the RRC Release message to the UE if A4 IMLB report is received, the eNodeB checks the RSRP and/or RSRQ parameters of a target cell against the configured thresholds so that a requested minimum power and quality of the target cell is satisfactory before sending dedicated priorities for the idle mode to UE

Conditions for an RRC connection release with a dedicated priority The RRC connection of the UE is released with a dedicated priority (target cell frequency getting the highest absolute priority) if all of the conditions below are true:

198

DN09185982

Issue: 01D


• •

•


an A4 IMLB measurement report is received before the A4 IMLB measurement timer expires the target cell's RSRP and/or RSRQ parameters are better than the operatorconfigurable absolute value in order to avoid a reselection to the cell with bad RF conditions the target cell's RSRP and/or RSRQ parameters are better than the source cell's RSRP and/or RSRQ increased by the operator-configurable offset (positive or negative) in order to avoid a reselection to a cell with significantly worse RF conditions

Otherwise, a normal RRC connection release without sending dedicated priorities is applied. Data or S1 signaling activity during the A4 IMLB measurements leads to a cancellation of the RRC Release message, and an inactivity timer is reset. Conditions for activating A4 IMLB measurements For the activation of A4 IMLB measurements, the following conditions must be met: • • • • •

the selected LTE target inter-frequency is allowed to run A4 IMLB measurements the UE supports A4 measurements (FGI bits #14 and #25) the RSRP and/or RSRQ thresholds related to the IMLB measurements are configured (relevant parameters are set) there are no ongoing inter-frequency or/and inter-RAT measurements the maximum number of UEs with A4-based measurements activated is not reached

The A4 IMLB measurements are controlled with a supervision timer configured by the operator. If A4 IMLB measurements cannot be applied to the UE, the RRC connection of this UE is released with a dedicated priority determined originally by the IMLB algorithm defined in the LTE1677: Idle Mode Mobility Balancing Extensions feature. System impact Interdependencies between features This feature requires the following feature to be enabled: •

LTE1677: Idle Mode Mobility Balancing Extensions

Impact on interfaces This feature reuses the already existing mechanism used for the RRC Release message and measurement configuration. 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

Issue: 01D

DN09185982

199



This feature introduces a new measurement type, M8034 LTE EUTRA carrier frequency. The measurement contains counters which measure an intra LTE related events per EUTRA carrier frequency. The counters are provided per the LTE cell and per the E-UTRA carrier frequency, for example, for each relationship between the LTE cell and the EUTRA carrier frequency, a separate counter is provided. This measurement is targeted to the following objects: • • •

LNBTS/LNCEL MCC/MNC EARFCN

Table 103: New counters lists counters introduced with this feature. Table 103

New counters

Counter ID

Counter name

Measurement

M8034C0

Number of A4 measurement activations for Measurement Based IMLB

LTE EUTRA carrier frequency

M8034C1

Number of successfully evaluated A4 measurement reports for Measurement Based IMLB


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


Abbreviated name

Managed object

Enable A4 event for idle mode load balancing

enableA4IMLB

IRFIM

Target cell min delta RSRP for idle mode load balancing

minDeltaRsrpIMLB

IRFIM

Target cell min delta RSRQ for idle mode load balancing

minDeltaRsrqIMLB

IRFIM

Target cell minimum RSRP for idle mode load balancing

minRsrpIMLB

IRFIM

Target cell minimum RSRQ for idle mode load balancing

minRsrqIMLB

IRFIM

Activate measurement-based idle mode load balancing

actMeasBasedIMLB

LNBTS

Idle mode load balancing supervision timer for A4 event

reportTimerIMLBA4

LNBTS


mtEutraFrequency

PMRNL


200

DN09185982

Issue: 01D


Table 105



Abbreviated name

Activation of idle mode load balancing (IdleLB)

actIdleLB



Sales information

BSW/ASW


ASW

SW asset monitoring


3.18.2 Activating and configuring LTE2051: Measurement based Idle Mode Load Balancing Before you start The Activate measurement-based idle mode load balancing (actMeasBasedIMLB) parameter is used for activation. Modification of this parameter does not require eNB restart or object locking. Table 107: Parameters used for activating and configuring LTE2051: Measurement based Idle Mode Load Balancing feature presents the parameters related to activation and configuration of the LTE2051: Measurement based Idle Mode Load Balancing feature. Table 107

Parameters used for activating and configuring LTE2051: Measurement based Idle Mode Load Balancing feature Parameter

Issue: 01D

Purpose


Activate measurementbased idle mode load balancing (actMeasBasedIMLB)

activation flag

no

Idle mode load balancing supervision timer for A4 event (reportTimerIMLBA4)


no

IRFIM identifier (irfimId) mandatory configuration

no

EUTRA presence antenna port1 (interPresAntP)


no

EUTRA frequency value (dlCarFrqEut)


no

Allowed measurement bandwidth (measBdw)


no

Enable A4 event for idle mode load balancing (enableA4IMLB)


no

Target cell min delta RSRP for idle mode load balancing (minDeltaRsrpIMLB)


no

DN09185982

201


Table 107


Parameters used for activating and configuring LTE2051: Measurement based Idle Mode Load Balancing feature (Cont.) Parameter

Purpose


Target cell min delta RSRQ for idle mode load balancing (minDeltaRsrqIMLB)


no

Target cell minimum RSRP for idle mode load balancing (minRsrpIMLB)


no

Target cell minimum RSRQ for idle mode load balancing (minRsrqIMLB)


no

The LTE1677: Idle Mode Mobility Balancing Extensions feature needs to be activated before the activation of the LTE2051: Measurement based Idle Mode Load Balancing feature (the value of Activation of idle mode load balancing (IdleLB) (actIdleLB) parameter needs to be set to true). Procedure 1


2

Activate the LTE2051: Measurement based Idle Mode Load Balancing feature. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate measurement-based idle mode load balancing (actMeasBasedIMLB) parameter's value to true.

Configure the Idle mode load balancing supervision timer for A4 event (reportTimerIMLBA4) parameter. a) Expand the MRBTS object. b) Select the LNBTS object. c) Set a desired value for the Idle mode load balancing supervision timer for A4 event (reportTimerIMLBA4) parameter using a dropdown list.

202

DN09185982

Issue: 01D


4

Configure the IRFIM object for every LTE target frequency and enable A4based measurements. a) b) c) d) e)

Expand the MRBTS object. Expand the LNBTS object. Select the LNCEL object. Add the IRFIM object. In the created IRFIM object, configure the following parameters (mandatory): • • • • •

5

IRFIM identifier (irfimId) EUTRA presence antenna port1 (interPresAntP) EUTRA frequency value (dlCarFrqEut) Allowed measurement bandwidth (measBdw) Enable A4 event for idle mode load balancing (enableA4IMLB)

Optional: Configure the RSRP and/or RSRQ thresholds. a) b) c) d) e)

Expand the MRBTS object. Expand the LNBTS object. Select the LNCEL object. Add the IRFIM object. Configure the following parameters (optional). • • • •

6


Target cell min delta RSRP for idle mode load balancing (minDeltaRsrpIMLB) Target cell min delta RSRQ for idle mode load balancing (minDeltaRsrqIMLB) Target cell minimum RSRP for idle mode load balancing (minRsrpIMLB) Target cell minimum RSRQ for idle mode load balancing (minRsrqIMLB)


Expected outcome The LTE2051: Measurement based Idle Mode Load Balancing feature has been activated. The eNB provides the support for A4-based measurements for idle mode load balancing.

Issue: 01D

DN09185982

203



3.18.3 Deactivating LTE2051: Measurement based Idle Mode Load Balancing Before you start The Activate measurement-based idle mode load balancing (actMeasBasedIMLB) parameter is used for deactivation. Modification of this parameter does not require eNB restart or object locking. Procedure 1


2

Deactivate the LTE2051: Measurement based Idle Mode Load Balancing feature. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate measurement-based idle mode load balancing (actMeasBasedIMLB) parameter's value to false.


Expected outcome The LTE2051: Measurement based Idle Mode Load Balancing feature has been deactivated. The eNB continues evaluation of the already started A4-based measurements and sends the A4 measurement report. New A4-based measurements for idle mode load balancing are not started.

3.19 LTE2085: SIB Reception with Parallel Measurement Gaps 3.19.1 Description of LTE2085: SIB Reception with Parallel Measurement Gaps Introduction to the feature

204

DN09185982

Issue: 01D



A UE with configured measurement gaps will fail to receive a single SIB transmission with a probability around 15%. The LTE2085: SIB Reception with Parallel Measurement Gaps feature ensures transmission of SI messages at least two times per SI window, which guarantees receiving one SI message per SI window even for UEs with configured measurement gaps. Benefits End-user benefits The LTE2085: SIB Reception with Parallel Measurement Gaps feature enhances the possibility that the end user will receive at least one SIB during an SI window, regardless of whether the measurement gaps are configured or not. It ensures a higher possibility to receive: information regarding INTRA-frequency and INTER-frequency neighboring cells information for re-selection of a cell (for example, handover) ETWS/CMAS notifications/warnings

• • •

Operator benefits The LTE2085: SIB Reception with Parallel Measurement Gaps feature: enables sending the SIB information at least twice at an interval greater than 6 ms within each SI window guarantees ETWS/CMAS notifications/warnings broadcast reception for all UEs enables the UEs to receive SIBs even if they have a measurement gap configured, which is essential in case of warning broadcasts (ETWS, CMAS)

• • •

Requirements Hardware and software requirements Table 108: Hardware and software requirements lists hardware and software requirements for this feature. Table 108


System release LTE-FDD 15A


OMS -

FL15A

UE 3GPP R8


LNF15A

NetAct OSS 15.5


MME -

SAE GW -

Functional description Functional overview The SIBs carry relevant information for the UE, which helps the UE, for example, to access a cell or perform a cell (re-)selection. They are also used to transmit warning messages; SIB10 and SIB11 carry ETWS notifications, and SIB12 carries the CMAS notification. Measurement gaps are configured for UEs in the cell's handover zone; the measurement gaps are repeated every 40 ms, and they last for 6 ms in DL (7 ms in UL under certain conditions). The starting points of measurement gaps are distributed in time across all

Issue: 01D

DN09185982

205



UEs in the cell in order to equalize the UL traffic generated when UEs report their measurement results. This means the UEs with measurement gaps will fail to receive a single SIB transmission with a probability of 6/40 = 15%. The LTE2085: SIB Reception with Parallel Measurement Gaps feature ensures that a UE having measurement gaps activated is able to receive SIBs at least once during an SI window. If the code rate of a SIB message is too high, then two or three transmissions are arranged for this message in the same SI window, see Figure 13: SIB reception with parallel measurement gaps. Figure 13

SIB reception with parallel measurement gaps ExampleswithoutLTE2085 20msSIBwindow

SIB1

SIB1

SIBtransmissiontwice perSIwindow (caseexample excluded byLTE2085)

20msSIBwindow

SIBtransmissiontwice perSIwindow

ExamplewithLTE2085 20msSIBwindow

SIBtransmissionmorethan twiceperSIwindow

Measurementgaps MeasurementgapsthatcoversbothSIBtransmission SIBtransmission

With LTE2085: SIB Reception with Parallel Measurement Gaps, an additional transmission is scheduled in order to cover the case of any possible overlap between a measurement gap and transmission of the SI message. Restrictions on the configuration parameters are introduced to avoid an SI window smaller than 20 ms.

g

Note: From LTE-FDD 15A onward (with the introduction of the LTE2085: SIB Reception with Parallel Measurement Gaps feature), CMAS/ETWS notifications can be activated only if SI window length (siWindowLen) is equal or greater than 20 ms.

g

Note: From RL70 onward, if the SI window length (siWindowLen) parameter is set to 10 ms or higher, basic eNB software sends SIB2 twice per SI window, with transmissions separated by more than 6 ms. The SI window length (siWindowLen) parameter can still be set to smaller values but the reception of SIB2 for UEs with measurement gaps is guaranteed only if the SI window length (siWindowLen) is equal or greater than 10 ms. Activation of the LTE2085: SIB Reception with Parallel Measurement Gaps feature shows an additional effect only for SIB3 and higher. UEs with a certain chipset might experience HO failures under the following rare conditions: •

206

inter-frequency HO to an eICIC-enabled eNB which runs in muting pattern 1

DN09185982

Issue: 01D


• •


UEs configured with a measurement gap that covers the subframe in which the small cell sends a system information block (SIB) the SI window length (siWindowLen) parameter is set to 20 ms, therefore, there will be only one subframe available if the SIB window coincides with the first half of the eICIC pattern of a 40-ms duration

UEs with the chipset do not use SIB2 data they were provided as part of the HO procedure. The UEs try to read SIB2 in the target cell and fail if it does not succeed within a preset time. It is recommended to perform one of the following actions to ensure smooth service conditions in HetNet scenarios: • •

Activate the LTE2085: SIB Reception with Parallel Measurement Gaps feature. Set the SI window length (siWindowLen) parameter to 40 ms in all eICIC small cells.

The LTE494: Commercial Mobile Alert System feature supports SIBs 12, and the LTE843: ETWS Broadcast feature supports SIBs 10 and SIBs 11; however, the two features cannot be activated together. System impact Interdependencies between features The following features are affected by the LTE2085: SIB Reception with Parallel Measurement Gaps feature: •

•

•

•

•

LTE1113: eICIC Macro and LTE1496: eICIC Micro If the eICIC is activated, the LTE2085: SIB Reception with Parallel Measurement Gaps feature verifies whether eICIC muting patterns are compatible with the SIB transmission's timing and the timing of other affected features. LTE1117: Multimedia Broadcast Multicast Service If the MBMS is activated, the LTE2085: SIB Reception with Parallel Measurement Gaps feature verifies whether other affected features leave a minimum number of subframes open for usage by the MBMS. LTE495: Observed Time Difference of Arrival The LTE2085: SIB Reception with Parallel Measurement Gaps feature can be activated only if OTDOA settings are compatible. LTE1709: Liquid Cell The LTE2085: SIB Reception with Parallel Measurement Gaps feature can be activated only if liquid cell settings are compatible. LTE55: Inter-frequency Handover and LTE1679: DRX with Parallel UE Measurement Gaps

Impact on system performance and capacity The Earthquake and Tsunami Warning System (ETWS) and Commercial Mobile Alert System (CMAS) are rare events, so a duplicated transmission of ETWS/CMAS messages does not consume noteworthy amounts of resources. Further impact depends on the Twofold transmission of SIBs per SI window (sib2xTransmit) parameter. The LTE2085: SIB Reception with Parallel Measurement Gaps feature impacts system performance and capacity in the following way:

Issue: 01D

DN09185982

207


• •


there is no impact if sib2xTransmit = false; thus, it does not limit throughput or performance SIB3 and above are transmitted at least two times per SI window if sib2xTransmit = true, which consumes double capacity

Management data Alarms There are no alarms related to this feature. Measurements and counters Table 109: Modified counters lists counters modified by this feature. Table 109

208

Modified counters

Counter ID

Counter name

Measurement

M8012C18

Volume of DL RLC PDUs transmitted

LTE Cell Throughput

M8011C25

DL PRB utilization per TTI Level 1

LTE Cell Resource

M8011C26


LTE Cell Resource

M8011C27


LTE Cell Resource

M8011C28


LTE Cell Resource

M8011C29


LTE Cell Resource

M8011C30


LTE Cell Resource

M8011C31


LTE Cell Resource

M8011C32


LTE Cell Resource

M8011C33


LTE Cell Resource

M8011C34


LTE Cell Resource

M8011C35

DL PRB utilization per TTI Min

LTE Cell Resource

M8011C36

DL PRB utilization per TTI Max LTE Cell Resource

M8011C37

DL PRB utilization per TTI Mean

DN09185982

LTE Cell Resource

Issue: 01D


g


Note: The following counters are not affected by additional repetitions introduced by LTE2085: SIB Reception with Parallel Measurement Gaps: • • •

M8001C231: Number of primary ETWS notifications M8001C232: Number of secondary ETWS notifications M8001C233: Number of CMAS notifications

Key performance indicators There are no key performance indicators related to this feature. Parameters Table 110: New parameters lists parameters introduced by this feature. Table 110

New parameters

Full name Twofold transmission of SIBs per SI window

Abbreviated name sib2xTransmit

Managed object

Structure

LNCEL

-



Abbreviated name

Managed object

Activation CMAS support

actCMAS

LNBTS

Activation ETWS support

actETWS

LNBTS

Activation MBMS support

actMBMS

LNBTS

Activation eICIC support

actEicic

LNCEL

Activation Liquid Cell support

actLiquidCell

LNCEL

PRS activation

actOtdoa

LNCEL

PRS configuration index

prsConfigurationIndex

LNCEL

SI window length

siWindowLen

LNCEL

System information scheduling sibSchedulingList list

LNCEL

Highest allowed muting pattern eIcicMaxMutePattern

LNCEL

Sales information Table 112: Sales information lists sales information about this feature. Table 112


BSW

Issue: 01D

License control in network element -

DN09185982

Activated by default Yes

209



3.19.2 Activating and configuring LTE2085: SIB Reception with Parallel Measurement Gaps with the Twofold transmission of SIBs per SI window parameter Before you start Table 113: Parameters used for activating and configuring LTE2085: SIB Reception with Parallel Measurement Gaps lists parameters used for activation and configuration of the LTE2085: SIB Reception with Parallel Measurement Gaps feature. Table 113

Parameters used for activating and configuring LTE2085: SIB Reception with Parallel Measurement Gaps Parameter

Purpose

Twofold transmission of SIBs per SI window (sib2xTransmit)

configuration

Requires eNB restart or object locking object locking

The LTE2085: SIB Reception with Parallel Measurement Gaps feature is activated either by activating the LTE494: Commercial Mobile Alert System (CMAS) feature for SIB12, or by activating the LTE843: ETWS Broadcast feature for SIB10 and SIB11, or by setting the Twofold transmission of SIBs per SI window (sib2xTransmit) parameter to true for all other SIBs except SIB1. To activate the feature, do the following: Procedure 1

Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure

2

Activate and configure the LTE2085: SIB Reception with Parallel Measurement Gaps feature. a) b) c) d) e) f)

g

210

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Expand the LNBTS object. Select the LNCEL object. Set the Twofold transmission of SIBs per SI window (sib2xTransmit) parameter value to true. Note: The value of the Twofold transmission of SIBs per SI window (sib2xTransmit) parameter is not recommended to be set to true provided the Downlink channel bandwith (dlChBw) is less than 10 MHz.

DN09185982

Issue: 01D


3


Optional: If it is not yet configured, set the SI window length (siWindowLen) parameter. a) Select the LNCEL object. b) Set the SI window length (siWindowLen) parameter's value to 20 ms or 40 ms.

Expected outcome When the Twofold transmission of SIBs per SI window (sib2xTransmit) parameter is set to true, the SIBs 3 and higher are transmitted at least twice per SI window, with a time difference higher than 6 ms. For SIB10 and SIB11 being transmitted twice per SI window, the LTE843: ETWS Broadcast feature must be activated and for SIB12, the LTE494: Commercial Mobile Alert System (CMAS) feature must be activated; however, only one of these features can be active at a time.

3.19.3 Activating and configuring LTE2085: SIB Reception with Parallel Measurement Gaps with a selected feature Before you start The LTE2085: SIB Reception with Parallel Measurement Gaps feature does not have an activation flag and is activated by default. Table 114: Parameters used for activating and configuring LTE2085: SIB Reception with Parallel Measurement Gaps lists parameters used for activation and configuration of the LTE2085: SIB Reception with Parallel Measurement Gaps feature. Table 114

Parameters used for activating and configuring LTE2085: SIB Reception with Parallel Measurement Gaps Parameter

Purpose


Activation ETWS support (actETWS)

activation flag

no

Activation CMAS support (actCMAS)

activation flag

no


optional

no

SI window length (siWindowLen)

mandatory

no

System information scheduling mandatory list (sibSchedulingList)

no

The LTE2085: SIB Reception with Parallel Measurement Gaps feature is activated either by activating the LTE494: Commercial Mobile Alert System (CMAS) feature for SIB12, or by activating the LTE843: ETWS Broadcast feature for SIB10 and SIB11, or by setting the Twofold transmission of SIBs per SI window (sib2xTransmit) parameter to true.

Issue: 01D

DN09185982

211



The LTE494: Commercial Mobile Alert System (CMAS) and LTE843: ETWS Broadcast features cannot be activated at the same time. Only one can be active at a time and an activation of that feature will activate LTE2085: SIB Reception with Parallel Measurement Gaps feature for related SIBs.

212

DN09185982

Issue: 01D


f


If the following conditions are not fulfilled, the validation of the configuration plan file will fail. BTS Site Manager informs the operator about the validation failure: •

•

•

•

•

•

•

If the Activate enhanced inter-cell interference coordination (actEicic) parameter's value is set to true, and the Cell type (cellType) parameter's value is not set to large in any LNCELobject of the eNB, then both parameters DRX profile 5:DRX long cycle (drxProfile5-drxLongCycle) and DRX smart profile 5:DRX long cycle ( drxSmartProfile5-drxLongCycle) must be set to 640 ms. If the Activate enhanced inter-cell interference coordination (actEicic) parameter's value is set to true, and the Cell type (cellType) parameter's value is set to large in any LNCEL object of the eNB, then the Highest allowed muting pattern (eIcicMaxMutePattern) parameter must be set as greater than mp1. If the Activate enhanced inter-cell interference coordination (actEicic) parameter's value is set to true, then the Activate support for MBMS (actMBMS) parameter must be set to false. If the Activate support for MBMS (actMBMS) parameter's values is set to true, then the

Activate enhanced inter-cell interference coordination (actEicic) parameter's value must be set to false. If the PRS activation (actOtdoa) parameter's value is set to true, and the number of configured SIBs is seven or smaller, then the PRS configuration index (prsConfigurationIndex) parameter must be set to one of the following values: 151, 471, 1111, or 2391. If the PRS activation (actOtdoa) parameter's value is set to true, and the SI window length (siWindowLen) parameter is set to 20 ms, and the number of configured SIBs is eight or higher, then the PRS configuration index (prsConfigurationIndex) parameter must be set to one of the following values: 471, 1111, or 2391. If the PRS activation (actOtdoa) parameter's value is set to true, and the SI window length (siWindowLen) parameter is set to 40 ms, and the number of configured SIBs is eight or higher, then the PRS configuration index (prsConfigurationIndex) parameter must be set to one of the following values: 1111 or 2391.

Migration rules for the SI window length (siWindowLen) parameter: •

If the Activation ETWS support (actETWS) parameter or the Activation CMAS support (actCMAS) parameter is set to true, and the SI window length (siWindowLen) parameter is smaller than 20 ms in RL70, then during migration to RL15A the SI window length (siWindowLen) parameter will change to 20 ms.

Migration rules for the Periodicity (siMessagePeriodicity) parameter: •

Issue: 01D

If the Activation ETWS support (actETWS) parameter or the Activation CMAS support (actCMAS) parameter is set to true, and the PRS activation (actOtdoa) parameter is set to true in RL70, then during migration to RL15A the Periodicity (siMessagePeriodicity) parameter must be equal or greater than the following equation:

DN09185982

213



siWindowLen * (# of SIBs (sets in structure sibSchedulingList + 2))+ 10ms

•

The value of the Periodicity (siMessagePeriodicity) parameter that does not fulfill this equation needs to be set to the next, higher value that fulfills it. The possible values are 80, 160, 320, 640, 1280, 2560, or 5120. If the Activation ETWS support (actETWS) parameter or the Activation CMAS support (actCMAS) parameter is set to true, and the PRS activation (actOtdoa) parameter is set to false in RL70, then during migration to RL15A the Periodicity (siMessagePeriodicity) parameter must be equal or greater than the following equation: siWindowLen * ((# of SIBs (sets in structure sibSchedulingList + 2))

The value of the Periodicity (siMessagePeriodicity) parameter that does not fulfill this equation needs to be set to the next, higher value that fulfills it. The possible values are 80, 160, 320, 640, 1280, 2560, or 5120. Migration rules for the PRS configuration index (prsConfigurationIndex) parameter: •

•

•

•

214

If the Activation ETWS support (actETWS) parameter or the Activation CMAS support (actCMAS) parameter is set to true, and the PRS activation (actOtdoa) parameter is set to true, and the number of configured SIBs is eight or higher, and the PRS configuration index (prsConfigurationIndex) parameter is set to any other value than 471, 1111, or 2391, then during migration to RL15A the PRS configuration index (prsConfigurationIndex) parameter must be set to 471. If the Activation ETWS support (actETWS) parameter or the Activation CMAS support (actCMAS) parameter is set to true, and the PRS activation (actOtdoa) parameter is set to true, and the SI window length (siWindowLen) parameter is set to 20 ms, and the number of configured SIBs is eight or higher, and the PRS configuration index (prsConfigurationIndex) parameter is set to any other value than 471, 1111, or 2391, then during migration to RL15A the PRS configuration index (prsConfigurationIndex) parameter must be set to 471. If the Activation ETWS support (actETWS) parameter or the Activation CMAS support (actCMAS) parameter is set to true, and the PRS activation (actOtdoa) parameter is set to true, and the SI window length (siWindowLen) parameter is set to 40 ms, and the number of configured SIBs is eight or higher, and the PRS configuration index (prsConfigurationIndex) parameter is set to any other value than 1111, or 2391, then during migration to RL15A the PRS configuration index (prsConfigurationIndex) parameter must be set to 1111. If the Activation ETWS support (actETWS) parameter or the Activation CMAS support (actCMAS) parameter is set to true, and the PRS activation (actOtdoa) parameter is set to true, then PRS period must be equal or greater than:

DN09185982

Issue: 01D



siWindowLen * (# of SIBs(sets in structure sibSchedulingList + 2))+ 10ms

where, depending on the PRS configuration index (prsConfigurationIndex) parameter, the PRS period in the above equation is set to: – – – –

g

160 ms for PRS configuration index (prsConfigurationIndex) = 151 320 ms for PRS configuration index (prsConfigurationIndex) = 471 640 ms for PRS configuration index (prsConfigurationIndex) = 1111 1280 ms for PRS configuration index (prsConfigurationIndex) = 2391 Note: The value of the PRS period that does not fulfill the above equation, shall be changed to the next, higher value that fulfills the equation.

Modification of some of the mentioned parameters requires object locking or BTS restart. This means that activation will cause a service outage if the parameters that require object locking or BTS restart have been modified. To activate the feature, do the following: Procedure 1


2

Activate and configure the LTE2085: SIB Reception with Parallel Measurement Gaps feature with a selected feature. Activation with the LTE843: ETWS Broadcast feature: a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activation ETWS support (actETWS) parameter's value to true.

Activation with the LTE494: Commercial Mobile Alert System (CMAS) feature: a) b) c) d)

Issue: 01D

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activation CMAS support (actCMAS) parameter's value to true.

DN09185982

215


3


Optional: If not yet configured, configure the PWS with emergency area ID parameter. a) Set the PWS with emergency area ID (pwsWithEmAreaId) parameter's value to true or false. b) If the PWS with emergency area ID (pwsWithEmAreaId) parameter's value is set to true, continue as follows. c) Select the LNCEL object. d) Expand the LNCEL object. e) If not yet added, add the Emergency area ID list (emAreaIdList) parameter and set a value from 0 to 16777215.

4

If not yet configured, set the SI window length (siWindowLen) parameter. a) Select the LNCEL object. b) Set the SI window length (siWindowLen) parameter's value to 20 ms or 40 ms.

5

If not yet configured, set the System information scheduling list (sibSchedulingList) parameter. a) Select the LNCEL object. b) Add the System information scheduling list (sibSchedulingList) parameter. c) Set the SIB type (siMessageSibType) parameter's value: • • • • • • •

for the ETWS notifications SIB10 and SIB11 parameters are required for the CMAS notifications SIB12 parameter is required for SIB4 add LNBTS:IAFIM object and set all required parameters for SIB5 add LNCEL:IRFIM object and set all required parameters for SIB6 add LNCEL:UFFIM object and set all required parameters for SIB7 add LNCEL:GFIM object and set all required parameters for SIB8 add LNCEL:CDFIM object and set all required parameters

d) Select and set the Periodicity (siMessagePeriodicity) parameter's value from a drop-down list for each selected SIB type. e) Select and set the Repetition (siMessageRepetition) parameter's value to 1 for each selected SIB type.

6


Expected outcome

216

DN09185982

Issue: 01D



The LTE2085: SIB Reception with Parallel Measurement Gaps feature is activated together with the LTE843: ETWS Broadcast feature. There are at least two subframes available for the transmission of the ETWS notification in SIB10 and SIB11 within each SI window. The LTE2085: SIB Reception with Parallel Measurement Gaps feature is activated together with the LTE494: Commercial Mobile Alert System (CMAS) feature. There are at least two subframes available for the transmission of the CMAS notification in SIB12 within each SI window. Further information When the Twofold transmission of SIBs per SI window (sib2xTransmit) parameter is set to true, the SIBs 3 and higher are transmitted at least twice per SI window, with a time difference higher than 6 ms. For SIB10 and SIB11 being transmitted twice per SI window, the LTE843: ETWS Broadcast feature must be activated and for SIB12, the LTE494: Commercial Mobile Alert System (CMAS) feature must be activated; however, only one of these features can be active at a time.

3.19.4 Deactivating LTE2085: Reception with Parallel Measurement Gaps Before you start Table 115: Parameters used for deactivating LTE2085: Reception with Parallel Measurement Gaps lists parameters used for deactivation of the LTE2085: Reception with Parallel Measurement Gaps feature. Table 115

Parameters used for deactivating LTE2085: Reception with Parallel Measurement Gaps Parameter

Purpose



deactivation

object locking

Activation ETWS support (actETWS)

deactivation

no

Activation CMAS support (actCMAS)

deactivation

no

To deactivate the feature, do the following: Procedure 1


Issue: 01D

DN09185982

217


2


Deactivate the LTE2085: Reception with Parallel Measurement Gaps feature. If the LTE843: ETWS Broadcast feature is configured: a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activation ETWS support (actETWS) parameter's value to false.

If the LTE494: Commercial Mobile Alert System (CMAS) feature is configured: a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activation CMAS support (actCMAS) parameter's value to false.

If the Twofold transmission of SIBs per SI window parameter is configured: a) b) c) d) e) f)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Expand the LNBTS object. Select the LNCEL object. Set the Twofold transmission of SIBs per SI window (sib2xTransmit) parameter's value to false.


Expected outcome The LTE2085: Reception with Parallel Measurement Gaps feature is deactivated. Warning notifications are not transmitted any more. SIBs 3 and higher are transmitted only once per SI window. Further information There might still be repetitions of SIBs caused by the code rate of a message.

3.20 LTE2133: eICIC for HetNet eNode B Configurations 3.20.1 Description of LTE2133: eICIC for HetNet eNode B Configurations Introduction to the feature The LTE2133: eICIC for HetNet eNode B Configurations feature provides an enhanced inter-cell interference coordination (eICIC) support for the following eNB configurations:

218

DN09185982

Issue: 01D



eNBs hosting both the macro and small cells eNBs hosting only the small cells eNBs hosting only the macro cells

• • •

Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides support for heterogeneous networks so that eICIC partnerships can be established in the following scenarios: between macro and small cells which are hosted by the same eNB between multiple small cells in one eNB and either the same macro cell or individual macro cells on another eNB

• •




-


g



OMS -

UE


-

NetAct

3GPP R10 UE NetAct 15.5 capabilities


MME -

SAE GW -

Note: The small cells can also be configured on the Flexi Multiradio 10 BTS. Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview The LTE2133: eICIC for HetNet eNode B Configurations feature introduces the internal X2 interface communication extensions for eICIC to enable: •

Issue: 01D

eICIC support between the macro and small cells located in the same eNB. Figure 14: Scenario 1 shows an example where low power remote radio heads (RRHs) are connected to the same system module with the overlapping high power RRH.

DN09185982

219


Figure 14


Scenario 1 low power RRH

eNB fiber

eICIC area

g

Note: The high power RRHs are used in the macro cells while the low power RRHs are used in the small cells. •

eICIC support between the macro cell hosted by an eNB and the small cells hosted by another eNB. Figure 15: Scenario 2 shows an example where a high power RRH and the low power RRHs are connected to different system modules linked via X2 interface. Figure 15

Scenario 2 low power RRH

eNB1

fiber

eICIC area

fiber

eNB2

high power RRH

X2

•

220

eICIC support for the macro and small cells configured in both scenarios. Figure 16: Scenario 3 shows an example where a high power RRH and some of the low power RRHs are connected to the same system module and other low power RRHs are connected to a different system module linked via X2 interface.

DN09185982

Issue: 01D


Figure 16


Scenario 3 high power RRH

eICIC area #2

fiber

fiber

low power RRH

eNB1

eNB2

eICIC area #1

fiber high power RRH

fiber

X2

g

Note: This scenario can be extended to include additional permutations such as multiple macro cells of eNB1 in eICIC partnership with the small cells of eNB2. Note that only one active eICIC partnership is allowed per small cell. There is a limitation imposed by an X2 reset procedure in any scenario where multiple eICIC areas use the same X2 link. This procedure is used in recovering from cases such as supervision timer expiry, and missing and unexpected responses. In this scenario, it is possible that one small cell terminates all eICIC partnerships for all involved eICIC areas. System impact Interdependencies between features The LTE2133: eICIC for HetNet eNode B Configurations feature is enabled together with the LTE1496: eICIC - micro feature.

g

Note: The eICIC feature activation is prohibited for small cells with carrier aggregation (CA) enabled. Simultaneous support for eICIC and CA in small cell eNBs will be available on a later release. Impact on interfaces This feature introduces the X2 interface for eICIC functions over the optical fiber cable. 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

Issue: 01D

DN09185982

221



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 117: Related existing parameters lists the existing parameters related to this feature. Table 117


Full name

Abbreviated name

Managed object

Structure

ECGI of the eICIC macro partner

eIcicPartnerEcgi

LNCEL

-

Identity of the eNB in the ECGI of the eICIC macro partner

enbId

LNCEL

eIcicPartnerEcgi

Identity of the cell in the ECGI of the eICIC macro partner

lcrId

LNCEL

eIcicPartnerEcgi

MCC in the ECGI of the eICIC macro partner

mcc

LNCEL

eIcicPartnerEcgi

MNC in the ECGI of the eICIC macro partner

mnc

LNCEL

eIcicPartnerEcgi

MNC length in the ECGI of the eICIC macro partner

mncLength

LNCEL

eIcicPartnerEcgi




ASW

-


3.21 LTE2149: Supplemental Downlink Carrier 3.21.1 Description of LTE2149: Supplemental Downlink Carrier Introduction to the feature

222

DN09185982

Issue: 01D



The LTE2149: Supplemental Downlink Carrier feature introduces supplemental cells only with downlink channels and not with the physical hybrid-ARQ indicator channel (PHICH). A supplemental cell can be used only as a secondary cell (SCell) in combination with downlink carrier aggregation for LTE. Benefits End-user benefits The LTE2149: Supplemental Downlink Carrier feature provides the end-user with an improved peak and average UE downlink throughput, enhancing the already utilized carrier aggregation features. Operator benefits Using the carrier aggregation feature, the LTE2149: Supplemental Downlink Carrier feature boosts downlink capacity by utilizing an unpaired spectrum as an additional carrier along with the originally paired downlink and uplink carriers. It has a maximum of 30 MHz aggregated bandwidth for a two-band combination downlink carrier and a maximum of 50 MHz aggregated bandwidth for a three-band combination downlink carrier. Requirements Hardware and software requirements Table 119 System release FDD-LTE 15A


FL15A



OMS -

UE


-

NetAct

3GPP R10 UE NetAct 15.5 capabilities


MME -

SAE GW -

Additional hardware requirements The LTE2149: Supplemental Downlink Carrier feature uses new, dedicated radio frequency modules supporting only downlink on band 29: • •

LTE2143: FRBE Flexi RRH 2TX 2RX 750 2TX 720 LTE2266: FRBG Flexi RRH 2TX 4RX 730 2TX 720

Other requirements Because of 3GPP limitation for supplementary downlink carrier cell bandwidth on band 29 must be of 5 or 10 MHz. Functional description Introduction to carrier aggregation in relation to LTE2149 Carrier aggregation (CA) increases the bandwidth by combining two or more component carriers (CC). The individual CCs can be of different bandwidths. Aggregation is possible by using contiguous CCs within the same operating frequency band (intra-band

Issue: 01D

DN09185982

223



contiguous). Non-contiguous aggregation is possible either as intra-band with separated CCs of the same operating frequency band, or as inter-band when CCs are from different operating frequency bands. A supplementary cell is a cell operating in the carrier aggregation mode only with downlink channels and not with the physical hybrid-ARQ indicator channel (PHICH) (see Figure 17: A supplementary cell used as a secondary cell (SCell) in carrier aggregation). Figure 17

A supplementary cell used as a secondary cell (SCell) in carrier aggregation

PCell PDCCH PDSCH PHICH ULChannels

SCell PDCCH PDSCH NoPHICH NoULChannels

CarrierAggregation Feature deployment The LTE2149: Supplemental Downlink Carrier feature allows utilizing an unpaired spectrum in band 29 with a cell bandwidth of 5 or 10 MHz. The feature supports up to 400 configured and activated secondary cell (SCell) UEs in a supplemental cell. The LTE2149: Supplemental Downlink Carrier feature supports the following two-band combinations for supplemental cells: • • •

band 2 + band 29 (bandwidth combination set: 0, 1, 2) band 4 + band 29 (bandwidth combination set: 0, 1, 2) band 30 + band 29 (bandwidth combination set: 0)

with a maximum of 30 MHz aggregated bandwidth. The LTE2149: Supplemental Downlink Carrier feature supports the following three-band combinations for supplemental cells: • • •

band 2 + band 29 + band 30 (bandwidth combination set: 0) band 4 + band 29 + band 30 (bandwidth combination set: 0) band 2 + band 2 + band 29 (bandwidth combination set: 0)

with a maximum of 50 MHz aggregated bandwidth. The supplemental cell cannot act as a primary cell (PCell). To avoid camping UEs on the supplemental cell it is declared as barred in system information block 1 (SIB1). System information block 3 (SIB3) is permamently disable and higher SIBs are conditionally

224

DN09185982

Issue: 01D



present (if provisioned they can be scheduled). The supplemental cell cannot be used as a mobility target. Positioning reference symbols can be configured for supplemental cells. System impact Interdependencies between features The LTE2149: Supplemental Downlink Carrier feature depends on: • • •

LTE1089: Downlink Carrier Aggregation - 20 MHz LTE1332: Downlink Carrier Aggregation - 40 MHz LTE1562: Carrier Aggregation for Multi-carrier eNBs

because the carrier aggregation is a precondition. The feature also depends on LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz and LTE1804: Downlink Carrier Aggregation 3CC - 60 MHz as a precondition for the three-band combination carrier. The feature depends on LTE2006: Flexible SCell Selection defining SCell selection for the supplemental downlink carrier. The feature must be activated together with LTE1089: Downlink Carrier Aggregation - 20 MHz and LTE1332: Downlink Carrier Aggregation - 40 MHz. The following features cannot be enabled for supplemental cells: • • • • • • •

LTE1542: FDD Supercell, LTE1709 Liquid Cell any uplink related features LTE1117: LTE MBMS cell configurations with 4 TX LTE1113: eICIC - Macro and LTE1496: eICIC - Micro LTE784: ANR Inter-RAT GERAN, LTE556: ANR Intra-LTE, Inter-frequency - UEbased and LTE908: ANR Inter-RAT UTRAN - Fully UE-based any kind of intra-frequency, inter-frequency or IRAT handover

Impact on interfaces no impact on interfaces Impact on network management tools The LTE2149: Supplemental Downlink Carrier feature impacts network management tools as follows: •

Uu: – –

•

S1/X2: –

•

S1 and X2 inactive for a user-data transfer

BTSOM/NWI3: –

Issue: 01D

no uplink channels no physical hybrid-ARQ indicator channel

unidirectional radio frequency hardware

DN09185982

225



Impact on system performance and capacity The LTE2149: Supplemental Downlink Carrier feature can improve peak and mean-user download throughput of non-GBR UEs with the secondary cell (SCell) configured. Additionally, a system capacity gain is also expected. The actual gain depends on many factors; for example, network's load, level of GBR traffic, parametrization of the scheduling fairness factor, but it can be doubled for bandwidth combinations with an equal bandwidth of two involved cells. Management data There are no alarms related to this feature. Measurements and counters Alarms 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 120: New parameters lists new parameters related to this feature. Table 120

New parameters

Full name

Abbreviated name

Managed object

Structure

Activate supplemental downlink carrier

actSdlc

LNCEL

-

Supplemental DL carrier frequency list

sdlcFreqList

LNBTS

-

Ending DL EARFCN in endEarfcnDl suppl. DL carrier frequency list

LNBTS

sdlcFreqList

Starting DL EARFCN in suppl. DL carrier frequency list

LNBTS

sdlcFreqList

startEarfcnDl



226

Abbreviated name

Managed object

Activate Centralized RAN

actCRAN

LNBTS

EUTRA frequency value

dlCarFrqEut

IRFIM

Maximum number of RRC connections

maxNumRrc

LNCEL

Maximum number RRC emergency

maxNumRrcEmergency

LNCEL

PDCCH LA UL DL allocation balance initial value

pdcchUlDlBal

LNCEL

DN09185982

Issue: 01D


Table 121


Related existing parameters (Cont.) Full name

Abbreviated name

Managed object

eUTRA frequency

redirFreqEutra

MODRED

eUTRA frequency

redirFreqEutra

MORED

eUTRA frequency

redirFreqEutra

REDRT

Eutra carrier info

eutraCarrierInfo

LNHOIF

Resource list

resourceList

LCELL


Sales information

BSW/ASW


ASW

-


3.21.2 Activating and configuring LTE2149: Supplemental Downlink Carrier Before you start Table 123: Parameters used for activating and configuring LTE2149: Supplemental Downlink Carrier lists parameters used for the activation and configuration of the LTE2149: Supplemental Downlink Carrier feature. Table 123

Parameters used for activating and configuring LTE2149: Supplemental Downlink Carrier Parameter

Purpose

Activate supplemental downlink carrier (actSdlc)

activation flag

Requires eNB restart or object locking restart

Supplemental DL carrier frequency mandatory configuration list (sdlcFreqList)

no

PDCCH LA UL DL allocation balance initial value (pdcchUlDlBal)

no


The feature must be activated together with LTE1089: Downlink Carrier Aggregation - 20 MHz and LTE1332: Downlink Carrier Aggregation - 40 MHz - The value of the LNBTS:

Activation of downlink carrier aggregation (actDLCAggr) parameter must be set to true. The feature uses new, dedicated radio frequency modules supporting only downlink on band 29: • •

LTE2143: FRBE Flexi RRH 2TX 2RX 750 2TX 720 LTE2266: FRBG Flexi RRH 2TX 4RX 730 2TX 720

Additionally, this feature can be enabled if and only if hardware is configured for downlink operation only.

Issue: 01D

DN09185982

227



This feature requires two or three properly configured cells, one of which will act as a supplemental downlink carrier (SDLC) cell. In order to ensure the allocation of minimal resources is used for not transmitted PHICH, it is recommended to use default values for the PHICH-related management LNCEL parameters: • • •

PHICH duration (phichDur) - Normal PHICH resource (phichRes) - N=1/6 Downlink PHICH transmission power boost (dlPhichBost) - 0dB

Ensure that parameters that are not used on the SDLC (i.e. managing the uplink operation) are configured and provide benign settings, not interfering with regular operation, for the following LNCEL parameters: • • • • • • • • • • • • • • • • • • •

g

Add GBR-DRB traffic for time critical reason handover (addGbrTrafficTcHo) Add GBR-DRB traffic for radio reason handover (addGbrTrafficRrHo) Add number DRB radioReasHo (addNumDrbRadioReasHo) Add number DRB timeCriticalHo (addNumDrbTimeCriticalHo) Additional active UE with reason radio reason handover (addAUeRrHo) Additional active UE with reason time critical handover (addAUeTcHo) Add number QCI1 DRB for radioReasHo (addNumQci1DrbRadioReasHo) Add number QCI1 DRB for timeCriticalHo (addNumQci1DrbTimeCriticalHo) Max number act DRB (maxNumActDrb) Max number carrier aggr configured UEs (maxNumCaConfUe) Max number carrier aggr configured UEs 3 Carriers (maxNumCaConfUe3c) Max number Carrier Aggr configured UEs double carrier (maxNumCaConfUeDc) Max number QCI1 DRBs (GBRs) (maxNumQci1Drb) Maximum bitrate selector (mbrSelector) Maximum bitrate uplink (maxBitRateUl) Maximum bitrate uplink (maxBitRateDl) Maximum GBR-DRB Traffic Limit (maxGbrTrafficLimit) Maximum number of active UEs (maxNumActUE) Maximum number RRC emergency (maxNumRrcEmergency) Note: There are no new, dedicated consistency checks for the LTE2149: Supplemental Downlink Carrier feature in NetAct or BTSSM preventing nonfunctional configuration of parameters.

To activate and configure the feature, do the following:

228

DN09185982

Issue: 01D



Procedure 1


2

Reconfigure cell resources. a) Go to the Cell Resources page. b) For the SDLC cell, reconfigure the ANT object's TX/RX usage mapping to TX (to support band 29). c) Configure the MIMO mode.

3

Configure downlink carriers. a) Go to the LTE Carriers page. b) For each cell, configure the Bandwidth as required. c) For each cell, configure appropriate EARFCN objects.

4

If no CAREL instance exists, create and configure at least one, in any of the non-supplemenatal downlink carrier cells, which has the supplemental downlink carrier cell as the target cell. a) b) c) d) e)

5

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Select the LNCEL object. On the selected LNCEL object, create a new CAREL instance.

Configure CAREL instance. In the CAREL instance, configure the following parameters to desired values: a) b) c) d)

6

Carrier aggregation relation identifier Local cell resource ID of cell to be aggregated SCell priority BTS ID of the parent eNB of the cell to be aggregated

Prohibit outgoing mobility toward the cells on supplemental DL carrier. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. c) Select the LNBTS object.

Issue: 01D

DN09185982

229



d) On the selected LNBTS object, create a new Supplemental DL carrier frequency list (sdlcFreqList) instance. e) Select the Supplemental DL carrier frequency list instance. f) Set the Ending DL EARFCN in suppl. DL carrier frequency list (endEarfcnDl) parameter as required. g) Set the Starting DL EARFCN in suppl. DL carrier frequency list (startEarfcnDl) parameter as required.

g

Note: The Supplemental DL carrier frequency list parameter will also be used by an eNB which does not provide a supplemental downlink carrier, so it is vital to configure this list properly. There are no new, dedicated consistency checks for the LTE2149: Supplemental Downlink Carrier feature in NetAct or BTSSM preventing nonfunctional configuration of parameters.

7

Set PDCCH LA UL DL allocation balance initial value to 0 for the SDLC cell. a) b) c) d) e)

8

Ensure that SDLC cell's administrative state is unlocked. a) b) c) d) e)

9

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Select the LNCEL object related to the SDLC cell. Set the PDCCH LA UL DL allocation balance initial value (pdcchUlDlBal) parameter's value to 0.

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Select the LNCEL object related to the SDLC cell. Ensure that Administrative state (administrativeState) parameter status is set to the unlocked value.


Expected outcome The eNB is restarted, the LTE2149: Supplemental Downlink Carrier feature is activated, and the LNCEL: Activate supplemental downlink carrier (actSdlc) parameter for SDLC cell is automatically set to true. The SDLC cell is unlocked, and the eNB can start to use the cell on the supplemental downlink carrier in carrier aggregation as an SCell.

230

DN09185982

Issue: 01D



3.21.3 Deactivating LTE2149: Supplemental Downlink Carrier Before you start The LCELL: Resource list (resourceList) parameter is used for deactivation. Modification of this parameter requires object locking. To deactivate the feature, do the following: Procedure 1


2

Reconfigure cell resources. a) Go to the Cell Resources page. b) For the SDLC cell, unselect the ANT objects. c) Depending on the radio frequency modules' hardware capability: •

Reconfigure the ANT objects to move the cell to a different band, supported by radio frequency module.

OR •

g

Delete the local cell related to the SDLC cell.

Note: With SDLC cell dedicated radio frequency hardware modules, it is not possible to keep the cell on band 29 after deactivating the LTE2149: Supplemental Downlink Carrier feature due to hardware restrictions.

3


Expected outcome The LTE2149: Supplemental Downlink Carrier feature is deactivated. The SDLC cell is deleted, or if the cell is reconfigured into a different band, the LNCEL: Activate supplemental downlink carrier (actSdlc) parameter for the cell is automatically set to false, and the cell cannot be used as an SDLC cell.

Issue: 01D

DN09185982

231



3.22 LTE2168: Additional Carrier Aggregation Band Combinations - II 3.22.1 Description of LTE2168: Additional Carrier Aggregation Band Combinations - II Introduction to the feature The LTE2168: Additional Carrier Aggregation Band Combinations - II feature supports additional downlink (DL) carrier aggregation (CA) band combinations. Benefits End-user benefits CA supports more band combinations that bring higher peak data rates for the users in the network. Operator benefits This feature offers the operator additional DL CA band combinations. Requirements Hardware and software requirements Table 124 System release FDD-LTE 15A


FL15A



OMS -

UE •

•

•

3GPP R10 UE capabilities 3GPP R11 UE capabilities 3GPP R12 UE capabilities


-

NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description In addition to the allowed CA band combinations from the LTE1089: Downlink Carrier Aggregation - 20 MHz, LTE1332: Downlink Carrier Aggregation - 40 MHz, and LTE2033: Additional Carrier Aggregation Band Combinations - I features, the LTE2168: Additional Carrier Aggregation Band Combinations - II feature allows the Flexi Multiradio 10 BTS to support:

232

DN09185982

Issue: 01D


• • • • • • • • • • • • • • • •

g


band 1 + band 5 (bandwidth combination set: 1) band 1 + band 8 (bandwidth combination set: 2) band 2 + band 2 (non-contiguous, contiguous) band 2 + band 12 (bandwidth combination set: 1) band 2 + band 30 band 3 + band 5 (bandwidth combination set: 2) band 3 + band 8 (bandwidth combination set: 2) band 3 + band 20 (bandwidth combination set: 1) band 4 + band 5 (bandwidth combination set: 0 and 1) band 4 + band 30 band 5 + band 30 band 7 + band 7 (bandwidth combination set: 1, contiguous) band 7 + band 20 (bandwidth combination set: 1) band 7 + band 8 band 12 + band 30 band 18 + band 28 Note: The bandwidth combination set is 0 if not indicated. For more details, see the LTE1089: Downlink Carrier Aggregation - 20 MHz and LTE1332: Downlink Carrier Aggregation - 40 MHz feature descriptions.

System impact Interdependencies between features The LTE2168: Additional Carrier Aggregation Band Combinations - II feature is enabled together with the LTE1089: Downlink Carrier Aggregation - 20 MHz and LTE1332: Downlink Carrier Aggregation - 40 MHz features. These features have the same activation flag, which is the actDLCAggr parameter. 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.

Issue: 01D

DN09185982

233



Parameters There are no parameters related to this feature. Sales information Table 125

Sales information

BSW/ASW ASW



3.22.2 Activating and configuring LTE2168: Additional Carrier Aggregation Band Combinations - II Before you start Setting the Activation of downlink carrier aggregation (actDLCAggr) parameter value to true activates the feature. Modification of this parameter requires evolved Node B (eNB) restart. The LTE2168: Additional Carrier Aggregation Band Combinations - II feature is enabled together with the LTE1089: Downlink Carrier Aggregation - 20 MHz and LTE1332: Downlink Carrier Aggregation - 40 MHz features. These features use the same activation flag. In operating the CA features, it might be necessary to set the link speed parameter. This is described in the Commissioning Flexi Multiradio BTS LTE document. Note that the default value (Auto) of this parameter is normally the optimal selection. Procedure 1


2

Configure the Activation of downlink carrier aggregation (actDLCAggr) parameter. a) b) c) d)

g

234

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activation of downlink carrier aggregation (actDLCAggr) parameter value to true.

Note: The Scheduling CA fairness control factor (caSchedFairFact) parameter must be configured when the Activation of downlink carrier aggregation (actDLCAggr) parameter is set to true.

DN09185982

Issue: 01D


3


(Optional) Create a new CADPR object. a) Right-click the selected LNBTS object. b) Create a new CADPR object. c) Define the value of each parameter within this object.

g

Note: The default values for the parameters within this object are set. Modification of the default values is not mandatory.

4

Create a new CAREL object. a) b) c) d)

5

Expand the LNBTS object. Select the LNCEL object. Create a new CAREL object. Define the value of each parameter within this object.


Expected Outcome The LTE2168: Additional Carrier Aggregation Band Combinations - II feature is activated in the eNB.

3.22.3 Deactivating LTE2168: Additional Carrier Aggregation Band Combinations - II Before you start Setting the Activation of downlink carrier aggregation (actDLCAggr) parameter value to false deactivates the feature. Modification of this parameter requires eNB restart. Procedure 1


2

Configure the Activation of downlink carrier aggregation (actDLCAggr) parameter. a) Go to the Radio Network Configuration page.

Issue: 01D

DN09185982

235



b) Expand the MRBTS object. c) Select the LNBTS object. d) Set the Activation of downlink carrier aggregation (actDLCAggr) parameter value to false.

g

Note: CA is completely deactivated when the parameter value is set to false.

3


Expected outcome The LTE2168: Additional Carrier Aggregation Band Combinations - II, LTE2033: Additional Carrier Aggregation Band Combinations – I, LTE1332: Downlink Carrier Aggregation - 40 MHz, and LTE1089: Downlink Carrier Aggregation - 20 MHz features are deactivated in the eNB.

3.23 LTE2208: eICIC Enhancements - micro 3.23.1 Description of LTE2208: eICIC Enhancements - micro Introduction to the feature The LTE2208: eICIC Enhancements – micro feature introduces the following functions: • •

handling of evolved node B (eNB) synchronization loss during enhanced inter-cell interference coordination (eICIC) operation dedicated system information block type 1 (SIB1) signaling for R11 user equipment (UEs) connected to the small cell

Benefits End-user benefits This feature avoids eICIC performance degradation caused by phase synchronization error in the eICIC area. Operator benefits This feature enhances eICIC implementation for the Flexi base station (BTS) by handling the loss of eNB synchronization. Requirements Hardware and software requirements Table 126



236



DN09185982



Issue: 01D




OMS -

UE •

•

NetAct

3GPP R10 UE capabilities 3GPP R11 UE capabilities

MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview The eICIC feature requires synchronization on the subframe level because of the application of the almost blank subframe (ABS). The maximum tolerable phase error for eICIC is 5 μs. The LTE2208: eICIC Enhancements - micro feature handles the loss of eNB synchronization as follows: • • • • • •

The LTE1496: eICIC - micro feature is enabled in the small cell and an eICIC partnership is established in the macro cell. If the eNB looses all the synchronization reference signals, it will continue to operate in holdover mode. The eNB continuous to monitor the estimated phase error. When the estimated phase error exceeds 5 μs for more than two minutes, an alarm will be raised. Synchronization is lost in the eICIC operation. The eICIC partnership is terminated.

The ABS pattern is switched off after all the eICIC partnerships are terminated. The eICIC feature remains enabled in the small cell and the eICIC partnership can be established again and operation will be resumed once the synchronization is recovered. The requests for eICIC partnership establishment are rejected as long as the phase error remains higher than 5 μs. The LTE2208: eICIC Enhancements - micro feature also deals with the dedicated SIB1 signaling for R11 UEs that are connected to the small cell. It handles the SIB1 update case for UEs located more than 6 dB in the small-cell cell range expansion (CRE). Dedicated signaling for the SIB1 update is sent when there is a modification in the SIB1 content. The updates are sent periodically to ensure that CRE UE receives the dedicated signaling. The 6 dB CRE limit is considered the safe value for UEs to read the PDCCH when receiving SIB1. The small cell CRE UEs encounter a high inter-cell interference from the macro cell when decoding SIB1 data on the PDCCH. However, because of the application of ABS, the PDSCH is blanked in the macro cell. This advantage, together with the R11 UE capability, is used to update SIB1 through dedicated RRC signaling to R11 UEs located more than 6 dB in the small cell CRE. The small cell eNB reconfigures all qualified UEs. System impact Interdependencies between features This feature is enabled together with LTE1496: eICIC - micro feature.

Issue: 01D

DN09185982

237



This feature affects the following features: • •

g

LTE494: Commercial Mobile Alert System LTE843: ETWS Broadcast Note: The specific time constraints of Commercial Mobile Alert System (CMAS) and Earthquake and Tsunami Warning System (ETWS) must be kept during the UE bulk reconfiguration procedure following the SIB1 modification.

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 performance and capacity as follows: • •

provides the necessary failure handling to avoid eICIC performance degradation when phase synchronization error exceeds 5 μs supports the SIB1 updates to be sent through the dedicated RRC signaling on the PDSCH for R11 UEs

Management data BTS faults and reported alarms Table 127: New BTS faults lists BTS faults introduced with this feature. Table 127

New BTS faults

Fault ID

Fault name


6280

Phase error exceeds 5 7651 μs limit

Alarm name BASE STATION OPERATION DEGRADED

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

238

DN09185982

Issue: 01D


Table 128


Sales information

BSW/ASW


ASW

SW Asset Monitoring


3.24 LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs 3.24.1 Description of LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs Introduction to the feature The LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature enables the Flexi Multiradio BTS to support inter-evolved Node B (eNodeB) Carrier Aggregation (CA) between two macro eNodeBs. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature enables the operator to support CA across two system modules. This means that there is a larger cell configuration per cluster site (for example, 4Rx UL CoMP and 3CC CA are in parallel). Requirements Hardware and software requirements Table 129


System release FDD-LTE 15A Flexi Zone Controller -



-

FL15A

OMS

UE

-

•

•


-

NetAct

3GPP R10 NetAct 15.5 UE capabilities 3GPP R11 UE capabilities


MME -

SAE GW -

Additional hardware requirements The eNodeBs that form an eNodeB-CA cluster must be co-located. Functional description Functional overview

Issue: 01D

DN09185982

239



The LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature allows DL CA for cells that are hosted in two different co-located macro eNodeBs. This is needed to support large configurations that require CA across multiple eNodeBs. The eNodeBs are connected together with a sync and a serial rapid I/O (SRIO) cable. The sync cable provides synchronization of the information required to keep the two eNodeBs in phase sync. The SRIO cable is used for signaling messages and bearer data transfer between the eNodeBs for CA. The interconnected eNodeBs can still act as an independent eNodeB toward the core network, other eNodeBs, and the LTE OMS or NetAct. This feature is activated using the Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr) parameter. CA cluster The eNBs connected together for the purpose of inter-eNB CA are referred to as a CA cluster. The CA cluster is loosely coupled so that if one eNB fails, the other eNB remains operational; or if the SRIO cable fails, both eNBs remain operational, but the inter-eNB CA is disabled. An alarm is introduced to indicate an SRIO link outage. The following changes are introduced in the eNB CA cluster management as compared to the management of individual eNBs: • • •

The eNB software interface versions must be compatible within the eNB CA cluster. The CA cluster must be configured by assigning a common CA cluster ID and a unique CA cluster member ID to each eNB in the CA cluster. The value of the set of parameters for the LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature must be consistent between all eNBs in the CA cluster.

The operator configures the CA cluster topology (Carrier aggregation cluster ID parameter) using the NetAct Configurator tools. This topology identifies which eNBs are connected together in the CA cluster. The operator has the option to perform consistency check using CM Analyzer in the NetAct Configurator. In the NetAct Configurator, a new CM Analyzer Nokia-defined rule set (Nokia.InterENodeBCarrierAggregation) is introduced for the LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature to verify the consistency of some of the parameters between all eNBs in the CA cluster. For more details about the rules, see the rule descriptions in the CM Analyzer application user interface. Parameter inconsistency alarm Each eNodeB in the CA cluster raises the EFaultId_InterEnbCaParamsInconsistencyAl alarm if the Activate intereNB DL carrier aggregation (actInterEnbDLCaggr) parameter is set to true and the required parameters between the eNodeBs are inconsistent. The activation of the new configuration in each eNodeB does not happen at the same time, and therefore it is possible that the alarm is raised for a short-time interval. This indicates the transient period when the inter-eNodeB CA is disabled because the eNodeBs are not synchronized with consistent parameters. The alarm persists in a scenario where the configuration of the parameters between the eNodeBs in the CA cluster is inconsistent. In this case, the erroneous configuration must be identified using the CM Analyzer check or with the information given in the alarm. If the CM Analyzer check does not report a consistency error, the erroneous configuration needs to be identified manually. Once the error is identified, the configuration plan needs to be corrected accordingly and provisioned to the eNodeB that has the error. The nature

240

DN09185982

Issue: 01D



of the plan provisioning operation causes the alarm to persist until the plan is successfully activated to each eNodeB in the CA cluster. For handling issues related on plan provisioning operation, see the NetAct Configurator documentation. Required cell configurations The CA cluster of two FSMFs and four FBBCs supports the following: • • • • •

•

Configuration 1: 2 5/10 MHz cells with 2Tx/Rx configuration + 3 5/10 MHz cells with 4Tx/4Rx configuration Configuration 3: 1 5/10 MHz cell with 2Tx/Rx configuration + 1 5/10 MHz cell with 4Tx/4Rx configuration + 1 15/10 MHz cell with 4Tx/4Rx configuration Configuration 4: 2 5/10 MHz cells with 2Tx/Rx configuration + 1 5/10 MHz cell with 4Tx/4Rx configuration + 1 15/10 MHz cell with 4Tx/4Rx configuration Configuration 5: 1 5/10 MHz cell with 2Tx/Rx configuration + 3 5/10 MHz cells with 4Tx/4Rx configuration Configuration 6: 1 5/10 MHz cell with 2Tx/Rx configuration + 1 5/10 MHz cell with 4Tx/4Rx configuration + 1 15/10 MHz cell with 4Tx/4Rx configuration (same summary level as in Configuration 3) Configuration 7: 2 5/10 MHz cells with 2Tx/Rx configuration + 2 5/10 MHz cells with 4Tx/4Rx configuration + 1 15/10 MHz cell with 4Tx/4Rx configuration

The LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature supports band 2, band 4, band 5, band 12, band 17, band 29, and band 30 band combinations. For more information about the configurations supported by this feature, see LTE Base Stations Supported Configurations. System impact Interdependencies between features At least one of the following CA features must be activated: • • • • •

LTE1089: Downlink Carrier Aggregation - 20 MHz LTE1332: Downlink Carrier Aggregation - 40 MHz LTE1562: Carrier Aggregation for Multi-carrier eNodeBs LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz

The LTE2006: Flexible SCell Selection feature must be enabled in case of a flexible secondary cell (SCell) selection. The LTE1710: Sync Hub Direct Forward feature must be enabled to forward the synchronization signal from one eNodeB to another eNodeB. The configurations of the following features are supported: • • • • •

LTE1746: LTE Extended Configurations Up to 6 Frequency Bands LTE2019: Advanced Dual Carrier Operation within Same RF Unit LTE2172: BTS Configurations Optimized for Distributed RRH Deployment LTE2168: Additional Carrier Aggregation Band Combinations – II LTE2149: Supplemental Downlink Carrier

The LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature can interwork with the following radio frequency (RF) sharing features:

Issue: 01D

DN09185982

241


• • •


LTE1829: LTE-LTE RF Sharing LTE2079: LTE-GSM RF Sharing with Full FBBC LTE2080: LTE-WCDMA RF Sharing with Full FBBC

The LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature does not support the following features: • •

LTE2091: FDD Supercell Extension The LTE1195: FHCC Flexi 850 Repeater Interface Unit (RIU)

The following features are not supported in the LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature: • •

LTE1367: Automatic Cell Combination Assignment for Carrier Aggregation LTE1951: Automatic Configuration Support for CA for Multi-carrier eNBs

Impact on interfaces This feature affects the SRIO interface, which is the connection between the two macro eNBs. New and existing messages are on this interface. These new messages are for inter-radio resource operation and maintenance (RROM) communication and serve the following purposes: • • • • •

validating parameter consistency for inter-eNB CA validating of SW consistency for the eNBs in the CA cluster obtaining SCell parameters as required by the primary cell (PCell) exchanging addressing information that permits inter-cell communication sending bearer data from the SCell to the PCell

Impact on network management tools This feature affects the following network elements: • •

eNodeB NetAct

Impact on system performance and capacity This feature enhances the capacity that can support CA using three component carriers with three sectors and an UL CoMP, where some of the cells are operating in 4Tx/4Rx configuration. Management data For more information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation. BTS faults and reported alarms Table 130: New BTS faults lists the BTS faults introduced with this feature.

242

DN09185982

Issue: 01D


Table 130


New BTS faults

Fault ID

Fault name


Alarm name

6282

Inter eNB CA parameter(s) inconsistency in between eNBs

7651

BASE STATION OPERATION DEGRADED

6283

Inter eNB SW inconsistency in between cluster members

7651


6284

Inter eNB communication failure

7651


4262

SRIO link outage

7651


4263

SRIO domain ID collision

7651


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 131: New parameters lists the parameters introduced with this feature. Table 131


Abbreviated name

Managed object

BTS ID of the parent eNB of the cell to be aggregated

lnBtsId

CAREL

Activate inter-eNB DL carrier aggregation

actInterEnbDLCAggr

LNBTS

Carrier aggregation cluster ID

caClusterId

LNBTS

Carrier aggregation cluster member ID

caClusterMemberId

LNBTS


Sales information

BSW/ASW ASW

Issue: 01D


DN09185982


243



3.24.2 Activating and configuring LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs Before you start The Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr) parameter activates the feature. Modification of this parameter does not require an eNodeB restart or object locking. Table 133

Parameters used for activating and configuring the LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature

Parameter

Purpose

Requires eNodeB restart or object locking

Activate inter-eNB DL carrier aggregation (actInterEnbDLCAgg r)

activation flag

No

Carrier aggregation cluster ID (caClusterId)


eNodeB restart

Carrier aggregation cluster member ID (caClusterMemberId )


eNodeB restart

At least one of the following CA features must be activated/configured before the activation of the LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature: • • • • •

g

LTE1089: Downlink Carrier Aggregation - 20 MHz LTE1332: Downlink Carrier Aggregation - 40 MHz LTE1562: Carrier Aggregation for Multi-carrier eNodeBs LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz Note: For more information about feature dependencies, see Interdependencies between features.

The eNodeB software interface versions must be compatible within the eNodeB CA cluster. The eNodeBs must be connected together with a sync and SRIO cable. The SRIO cable (6 Gbps link) must not exceed 25 meters and the sync cable (2-meter HDMI cable) is also defined to a short distance. The CM Analyzer is used to check the following set of parameters that must be consistent between all eNodeBs in the CA cluster: •

244

The Periodic CQI subbands cycles (cqiPerSbCycK), Rank indication reporting enable (riEnable), and Periodic CQI feedback type (periodicCqiFeedbackType) parameters must have the same value in the primary cell (PCell) and all of its associated secondary cells (SCells).

DN09185982

Issue: 01D


The Multiplier M for periodic RI reporting period (riPerM) parameter is used for each LNCEL in the set of cells that consists of a PCell and all of its associated SCells. If the Rank indication reporting enable (riEnable) parameter is set to true, the Multiplier M for periodic RI reporting period (riPerM) parameter must be set to 1. The combination of the BTS ID of the parent eNB of the cell to be aggregated (lnBtsId) and Local cell resource ID of cell to be aggregated (lcrId) parameters must be unique in the PCell and all of its associated SCells in each LNBTS in the CA cluster. The value of the EARFCN downlink (earfcnDL) (LNCEL) parameter of the PCell must be different than the value of the EARFCN downlink (earfcnDL) parameter of all the PCell's associated SCells in each LNBTS in the CA cluster. The Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr), Scheduling CA fairness control factor (caSchedFairFact), SCell deactivation timer eNB (sCellDeactivationTimerEnb), and Activate flexible SCell selection (actFlexScellSelect) parameters in each LNBTS with the same CA cluster ID must have the same value. The Cell resource sharing mode (cellResourceSharingMode) and Activate supercell configuration (actSuperCell) parameters must be set to none and false respectively in the PCell and all of its associated SCells if the Activation of downlink carrier aggregation (actDLCAggr) parameter is set to true and the value of the Max number of secondary cells for DL carrier aggr (maxNumSCells) parameter is greater than or equal to 1. The Carrier aggregation pool ID (caPoolID) parameter must have the same value for the set of LNCELs that consists of a PCell and all of its associated SCells. This parameter must also be configured in non-CA cells. A maximum of 13 LNCELs in all LNBTSs in the CA cluster can have the same CA pool ID.

•

•

•

•

•

g


Note: The CM Analyzer does not check the following for consistency: •

•

•

For the set of SCells associated with a PCell, there are at most two different EARFCN downlink (earfcnDL) parameter values if the

Max number of secondary cells for DL carrier aggr (maxNumSCells) parameter is greater than 1. For the set of SCells associated with a PCell, there are at most six SCells with the same EARFCN downlink (earfcnDL) parameter value if the Max number of secondary cells for DL carrier aggr (maxNumSCells) parameter is greater than 1. For the set of SCells associated with a PCell, there is at most one SCell with the same EARFCN downlink (earfcnDL) parameter value if the Max number of secondary cells for DL carrier aggr (maxNumSCells) parameter is equal to 1.

The eNodeBs in the CA cluster must be configured with sync hub direct forwarding. The sync hub master must be configured with the Forward synchronization in cositing (syncPropagationEnabled) parameter set to true. The sync hub slave must be configured with the SyncHub Master BTS as reference source (gpsCtrlBlockForColocatedBTS) parameter set to true and the Network synchronization mode (btsSyncMode) parameter set to phase sync.

Issue: 01D

DN09185982

245


g


Note: Both eNodeBs must be on phase sync. If the Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr) parameter is set to true, the integrated selforganizing network (iSON) manager does not support any CA functions for the respective eNodeB. Therefore, the Carrier aggregation control (caControl) parameter must be set to manual in NetAct. Procedure 1

Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNodeB configuration settings) of the general procedure, perform the steps described in this procedure.

2

Configure the CA cluster. a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the values for the following parameters: • •

g

3

Carrier aggregation cluster ID (caClusterId) Carrier aggregation cluster member ID (caClusterMemberId) Note: The eNodeBs in the CA cluster must have the same CA cluster ID. The CA cluster member ID identifies the eNodeBs in the CA cluster and each eNodeB must have a unique member ID. Modification of these parameters requires eNodeB restart.

Activate the Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr) parameter. On the selected LNBTS object, set the value of the Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr) parameter to true.

4

Create a new CAREL object. a) b) c) d)

g

246

Expand the LNBTS object. Select the LNCEL object. Create a new CAREL object. Define the value of each parameter within this object.

Note: The CA pool ID (LNCEL-caPoolId) must be consistent within the CA cluster. The CAREL objects must only point to cells in their CA pool.

DN09185982

Issue: 01D


5


Send the parameters to the eNodeB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.

Expected outcome The LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature is activated and used for inter-eNodeB CA. Further information In case one eNodeB fails, the other eNodeB remains operational. On one hand, in case the SRIO cable fails, both eNodeBs remain operational but the inter-eNodeB CA is disabled.

3.24.3 Deactivating LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs Before you start The Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr) parameter deactivates the feature. Procedure 1

Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNodeB configuration settings) of the general procedure, perform the steps described in this procedure.

2

Configure the Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr) parameter. a) b) c) d)

g

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the value of the Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr) parameter to false.

Note: The CA cluster ID, CA cluster member ID, and CAREL objects on the other eNodeB has to be deleted to completely deactivate the feature.

3

Send the parameters to the eNodeB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.

Expected outcome

Issue: 01D

DN09185982

247



The LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature is deactivated in all eNodeBs and no inter-eNodeB CA takes place. CA with aggregated cells from one eNodeB (intra-eNodeB) continues to work in all eNodeBs.

3.24 Variable Definitions

3.25 LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release 3.25.1 Description of LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release Introduction to the feature The LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release feature adds a new functionallity to a circuit-switched fallback (CSFB) mechanism. It enables the operator to prioritize the sequence of broadcast control channel (BCCH) carriers within the GERAN frequency layer list. In the case of some operators, prior to this feature, the fixed sequence of BCCH carriers caused the UE to select suboptimal cells. With LTE2314 activated, the UE choses an optimal GERAN cell. Benefits End-user benefits This feature increases call success rate. Operator benefits This feature enables the operator to configure a unique priority value for a single absolute radio frequency number (ARFCN). Requirements Hardware and software requirements Table 134 System release FDD-LTE 15A



FL15A

OMS -





FL15A

-

NetAct

MME

NetAct 15.5

-

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware.

248

DN09185982

Issue: 01D



Functional description The LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release feature enables the operator to prioritize the sequence of broadcast control channel (BCCH) carriers within the GERAN frequency layer list. In the case of some operators, prior to this feature, the fixed sequence of BCCH carriers caused the UE to select suboptimal cells. With LTE2314 activated, the UE choses an optimal GERAN cell. This feature is an extension of the LTE562: CSFB to UTRAN or GSM via Redirect feature. GERAN BCCH carrier frequency priority is O&M configurable and no duplication is allowed within configured carriers' priorities. Carriers without defined priorities are treated as the lowest priority carriers and are added at the end of the sequence list. After the operator has configured the priority of ARFCN values, the eNB sends a sorted list to the UE. When there is no priority set for BCCH carriers, the functionality of this feature switches off. System impact Interdependencies between features For the LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release feature, the LTE562: CSFB to UTRAN or GSM via Redirect feature must be enabled. The LTE562 feature is used to keep circuit-switched (CS) service voice continuity in the initial phase of LTE implementation, which does not support CS services. As a consequence of this feature, the UE leaves an LTE network and is handled by radio access technology (RAT), capable of the CS service. 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 performance and capacity as follows: • •

call success rate KPI is increased VoLTE call success rate KPI is increased

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.

Issue: 01D

DN09185982

249



Parameters Table 135

New parameters

Full name

Abbreviated name

Managed object

Structure

GERAN ARFCN values redirGeranArfcnStructL list

MODRED

-

GERAN ARFCN priority order

redirGeranArfcnPrio

MODRED

redirGeranArfcnStructL

GERAN ARFCN value

redirGeranArfcnValue

MODRED



MORED

-


redirGeranArfcnPrio

MORED


GERAN ARFCN value


MORED



REDRT

-


redirGeranArfcnPrio

REDRT


GERAN ARFCN value


REDRT


There are no modified parameters related to this feature. Sales information Table 136

Sales information

BSW/ASW ASW



3.25.2 Activating and configuring LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release Before you start The LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release feature does not have an activation flag and is activated by default. Table 137: Parameters used for configuring LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release lists the parameters used for the configuration of this feature. Table 137

Parameters used for configuring LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release Parameter

GERAN ARFCN values list (redirGeranArfcnStructL)

250

Purpose optional configuration

DN09185982


Issue: 01D


Table 137


Parameters used for configuring LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release (Cont.) Parameter

Purpose


GERAN ARFCN priority order (redirGeranArfcnPrio)


no

GERAN ARFCN value (redirGeranArfcnValue)


no

For the LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release feature to be used, the LTE562: CSFB to UTRAN or GSM via Redirect feature must be enabled (actCSFBRedir set to Enabled). To configure the feature, do the following: Procedure 1


2

Configure the REDRT instance, for which redirRAT is set to a GERAN value, with the redirGeranfcnStructL structure and its members (redirGeranArfcnValue, redirGeranArfcnPrio). a) b) c) d) e)

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Select the LNCEL object and add a new REDRT object. In the REDRT object set the following parameters: • • •

Redirection target configuration identifier to a value between 0 and 5 GERAN band indicator to deasired value RAT for redirection to a GERAN value.

Set at least one of the following parameters: • • •

f)

Issue: 01D

Redirection priority for CS fallback with redirection to a value between 1 and 6 Redirection priority for emergency call to a value between 1 and 6 Redirection priority for UE context release to a value between 1 and 6

Select the REDRT object and add a new GERAN ARFCN values list object.

DN09185982

251



g) In the GERAN ARFCN values list object, set the GERAN ARFCN priority order (redirGeranArfcnPrio) parameter to a value between 1 and 32 and GERAN ARFCN value (redirGeranArfcnValue) parameter to a value between 0 and 1023.

3

In the MODRED instance, configure the redirGeranArfcnStructL structure with its members (redirGeranArfcnValue, redirGeranArfcnPrio). a) b) c) d) e)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object and add a new MODPR object. Select the MODPR object and add a new MODRED object.. In the MODRED object, set the following parameters: • • •

Mobility profile identifier for redirection to a value between 0 and 5 GERAN band indicatorto desired value RAT for redirection to a GERAN value

Set at least one of the following parameters: • • •

Redirection priority for CS fallback with redirection to a value between 1 and 6 Redirection priority for emergency call to a value between 1 and 6 Redirection priority for UE context release to a value between 1 and 6

f) Select the MODRED object, and add a new GERAN ARFCN values list object. g) In the GERAN ARFCN values list object, set the GERAN ARFCN priority order (redirGeranArfcnPrio) parameter to a value between 1 and 32 and GERAN ARFCN value (redirGeranArfcnValue) parameter to a value between 0 and 1023.

4

In the MORED instance, configure the redirGeranArfcnStructL structure with its members (redirGeranArfcnValue, redirGeranArfcnPrio). a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object and add a new MOPR object. Select the MOPR object and set the Mobility profile identifier to a value between 1 and 16. e) Select the MOPR object and add a new MORED object. f) In the MORED object, set the following parameters: • • •

252

Mobility profile identifier for redirection to a value between 0 and 5 RAT for redirection to a GERAN value GERAN band indicator to desired value

DN09185982

Issue: 01D



g) Select the MORED object and add a new GERAN ARFCN values list object. h) In the GERAN ARFCN values list object, set the GERAN ARFCN priority order (redirGeranArfcnPrio) and GERAN ARFCN value (redirGeranArfcnValue) parameters to desired values.

5


Expected outcome The LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release feature is activated and configured for CSFB with redirection to GERAN. Target frequency values represented by ARFCN will be set according to the priorities configured by the operator.

3.25.3 Deactivating LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release Before you start Deactivation of LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release requires the user to delete the parameters previousely configured. Modification of these parameters does not require a BTS restart. Procedure 1


2

In the REDRT instance, for which redirRAT is set to a GERAN value, deactivate the redirGeranArfcnStructL structure with its member (redirGeranArfcnPrio). a) b) c) d) e) f)

Issue: 01D

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Expand the LNCEL object. Expand the REDRT object. On the GERAN ARFCN values list, delete the value in the GERAN ARFCN priority order (redirGeranArfcnPrio) parameter.

DN09185982

253


3

In the MODRED instance, deactivate the redirGeranArfcnStructL structure with its member (redirGeranArfcnPrio) a) b) c) d) e) f)

4

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Expand the MODPR object. Expand the MODRED object. In the GERAN ARFCN values list object, delete the value in the GERAN ARFCN priority order (redirGeranArfcnPrio) parameter.

In the MORED instance, deactivate the redirGeranArfcnStructL structure with its member (redirGeranArfcnPrio). a) b) c) d) e) f)

5


Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Expand the MOPR object. Expand the MORED object. In the GERAN ARFCN values list object, delete the value in the GERAN ARFCN priority order (redirGeranArfcnPrio) parameter.


Expected outcome The LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB Based on UE Context Release feature is deactivated.

3.26 LTE2324: Network-requested UE Radio Capabilities 3.26.1 Description of LTE2324: Network-requested UE Radio Capabilities Introduction to the feature The LTE2324: Network-requested UE Radio Capabilities feature enables supporting the UE with more than 128 carrier aggregation (CA) band combinations. The additional CA band combinations (supportedBandCombinationAdd) are valid only for 3CC band combinations. Benefits End-user benefits

254

DN09185982

Issue: 01D



This feature ensures end users' mobiles greater flexibly since they support more band combinations (more than 128 different band combinations); thus, end users may experience higher throughput. Operator benefits This feature allows the operator to reduce the number of 3CC band combinations sent from UE to eNB based on the priority list provided by the operator. Moreover, it enables the operator to avoid the latency introduced from the IDLE to ACTIVE transition because the eNB would have the available UE capabilities at initial attach. Without this feature implemented, the operator may not be able to provide the 3CC carrier aggregation to the end user if the band combinations of the operator's network are not contained in the UE capabilities sent from UE to eNB. Requirements Hardware and software requirements Table 138


System release

FDD-LTE 15A




OMS -

UE 3GPP R11


FL16

NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description The LTE2324: Network-requested UE Radio Capabilities feature introduces an operator configurable list of required carrier aggregation (CA) bands. The additional CA band combinations (supportedBandCombinationAdd) are valid only for 3CC band combinations. This feature enables the UE to provide additional 256 supported CA band combinations upon the eNB's request compared with the currently available 128 band combinations. If the initially provided UE radio capabilities are not sufficient to configure CA in the eNB, a dedicated UE capability enquiry with carrier aggregation bands will be initiated for UEs with suitable capabilities. The feature can be enabled/disabled per eNB through the O&M settings. Operation of the LTE2324: Network-requested UE Radio Capabilities feature consists of the following two mechanisms: • •

filtering, where the eNB requests the UE to provide supported band combinations within a limited set of bands adding a supportedBandCombinationAdd list in the UE-EUTRA-Capability, enabling additional 256 CA band combinations in a UE capability signalling

System impact Interdependencies between features The LTE2014: 3GPP Baseline R11 09/2014 (v2) feature introduces SASN.1 required for the LTE2324: Network-requested UE Radio Capabilities.

Issue: 01D

DN09185982

255



If the operator uses mapped bands, the LTE1534: Multiple Frequency Band Indicator feature must be active for the LTE2324: Network-requested UE Radio Capabilities feature. The LTE2324: Network-requested UE Radio Capabilities feature introduces additional 256 band combinations signaled by the UE for the following CA features. These combinations need to be considered by the eNB for a CA configuration. • • • • •

LTE747: Support of UE Radio Capabilities LTE1541: Advanced SCell Measurement Handling LTE1803: Downlink Carrier Aggregation 3CC - 40 MHz LTE1804: Downlink Carrier Aggregation 3CC - 60 MHz LTE2006: Flexible SCell Selection

LTE2324: Network-requested UE Radio Capabilities introduces additional 256 band combinations signaled by the UE for the following handover and ANR features. These combinations need to be considered by the eNB for the calculation of measurements. • • • • • • • • • • • •

LTE55: Inter-frequency Handover LTE56: Inter-RAT Handover to WCDMA LTE60: Inter-RAT Handover to eHRPD/3GPP2 LTE442: Network-assisted Cell Change LTE556: ANR Intra-LTE, Inter-frequency - UE-based LTE736: CSFB to UTRAN via PS HO LTE738: SRVCC to1xRTT/CDMA LTE872: SRVCC to WCDMA LTE873: SRVCC to GSM LTE908: ANR Inter-RAT UTRAN - Fully UE-based LTE1357: LTE-UTRAN Load Balancing LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB)

For the following handover features, the LTE2324: Network-requested UE Radio Capabilities feature retrieves again the UE radio capabilities from the UE. If the radio capabilities are not sufficient for CA, this capability retrieval also contains also the request for other-RAT capabilities if they are required by the feature and are not provided by MME. • • • • • •

LTE56: Inter-RAT Handover to WCDMA LTE736: CSFB to UTRAN via PS HO LTE738: SRVCC to1xRTT/CDMA LTE872: SRVCC to WCDMA LTE873: SRVCC to GSM LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB)

Impact on interfaces This feature impacts the RAN system NE external interfaces by introducing new information elements to the following existing messages: • •

256

requestedFrequencyBands-r11 in the RRC::UECapabilityEnquiry message supportedBandCombinationAdd-r11 in the RRC::UECapabilityInformation message

DN09185982

Issue: 01D



Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature may increase attach latency due to the size of the UECapabilityInformation message, resulting from the reporting of additional supported band combinations in the long term. This depends on the number of bands actually supported by the UE. 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 139

Parameters list

Full name

Abbreviated name

Managed object

Structure

Activate Network Requested UE Radio Capabilities

actNwReqUeCapa

LNBTS

-

Requested frequency bands

reqFreqBands

LNBTS

-

3GPP band number

bandNumber

LNBTS

reqFreqBands

Band priority

bandPrio

LNBTS

reqFreqBands


Sales information

BSW/ASW BSW



3.26.2 Activating and configuring LTE2324: Network-requested UE Radio Capabilities Before you start The Activate Network Requested UE Radio Capabilities (actNwReqUeCapa) parameter is used for activation. Modification of this parameter does not require eNB restart.

Issue: 01D

DN09185982

257


Table 141


Table 4 lists the parameters used for activating and configuring the LTE2324: Network-requested UE Radio Capabilities feature Parameter

Purpose


Activate Network Requested UE Radio Capabilities (actNwReqUeCapa)

activation flag

no

Requested frequency bands (reqFreqBands)


no

The following features must be activaterd before the LTE2324: Network-requested UE Radio Capabilities feature can be activated: • •

The LTE2014: 3GPP Baseline R11 09/2014 (v2) feature introduces SASN.1 required for the LTE2324: Network-requested UE Radio Capabilities. If the operator uses mapped bands, the LTE1534: Multiple Frequency Band Indicator feature must be active for the LTE2324: Network-requested UE Radio Capabilities feature.

To activate the feature, do the following: Procedure 1


2

Configure the Requested frequency bands (reqFreqBands) parameter. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object and create a new Requested frequency bands object. Set the desired values of the reqFreqBands parameter.

Activate the Activate network requested UE radio capabilities (actNwReqUeCapa) parameter. a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Click the LNBTS object. Set the Activate network requested UE radio capabilities (actNwReqUeCapa) parameter value to true.

Expected outcome The LTE2324: Network-requested UE Radio Capabilities feature has been activated.

258

DN09185982

Issue: 01D



3.26.3 Deactivating LTE2324: Network-requested UE Radio Capabilities Before you start The Activate Network Requested UE Radio Capabilities (actNwReqUeCapa) parameter is used for deactivation. Modification of this parameter does not require eNB restart. To deactivate the feature, do the following: Procedure 1


2

Deactivate the feature. a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate Network Requested UE Radio Capabilities (actNwReqUeCapa) parameter value to false.

Expected outcome The LTE2324: Network-requested UE Radio Capabilities feature has been deactivated.

3.27 LTE2430: QCI1 Establishment Triggered Protection Timer 3.27.1 Description of LTE2430: QCI1 Establishment Triggered Protection Timer Introduction to the feature The LTE2430: QCI1 Establishment Triggered Protection Timer feature allows keeping the UE in an RRC-connected mode even if there is no activity, for example, during a ringtone. The connection sustain time is defined by a dedicated timer-type parameter. Benefits End-user benefits This feature improves a VoLTE setup success rate. Operator benefits This feature:

Issue: 01D

DN09185982

259



provides a VoLTE UE from going to the RRC idle mode caused by inactivity, for example, during a ringtone, which might last longer than a normal inactivity timer saves a signalling capacity improves a VoLTE setup success rate prevents a ringing UE from being idle balanced to a layer where the QCI1 traffic is not desired

• • • •




FL15A


FL15A

OMS -

UE -



FL15A

-

NetAct

MME

NetAct 15.5

-

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description The LTE2430: QCI1 Establishment Triggered Protection Timer feature enables a configurable QCI1 protection timer. The timer is used for preventing the UEs from falling into the RRC idle mode during a ringtone, when there is potentially no traffic on any of the bearers or on the S1 link. However, if the protection timer and all other inactivity timers expire before the ringtone is finished, the UE is released to the RRC idle mode. The timer is started or restarted by an eNodeB every time the QCI1 is established. The intention is to set the timer value higher than a normal user plane inactivity timer; it should be set according to the time that the end-user is expected to answer the call when the phone is ringing. In this scenario, the UE is not released to the RRC idle mode until the established QCI1 timer and all other inactivity timers expire. In case the end-user terminates the call, and no other QCI1 related to that UE is established, then the QCI1 protection timer stops. Consequently, if additionally all other inactivity timers expire, the UE is released to the RRC idle mode. The value of QCI1 protection timer is defined with the QCI1 protection timer (qci1ProtectionTimer) parameter. System impact Interdependencies between features This feature requires the following features to be enabled: • •

LTE7: Support of Multiple EPS Bearer LTE10: EPS Bearers for Conversational Voice

Impact on interfaces

260

DN09185982

Issue: 01D



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 the following impact on the system performance: • •

signalling capacity: saved VoLTE setup success rate: can be improved, but depends on the operator's network configuration

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 143: New parameters lists parameters introduced with this feature. Table 143


Abbreviated name

Managed object

Activate RRC connected mode actRrcConnNoActivity while no activity

LNBTS

QCI1 protection timer

LNCEL

qci1ProtectionTimer



Inactivity timer

Abbreviated name inactivityTimer



Sales information

BSW/ASW ASW

Issue: 01D


DN09185982


261



3.27.2 Activating and configuring LTE2430: QCI1 Establishment Triggered Protection Timer Before you start The Activate RRC connected mode while no activity (actRrcConnNoActivity) parameter is used for activation. Modification of this parameter does not require eNB restart or object locking. Table 146: Parameters used for activating and configuring LTE2430: QCI1 Establishment Triggered Protection Timer feature presents the parameters related to activation and configuration of the LTE2430: QCI1 Establishment Triggered Protection Timer feature. Table 146

Parameters used for activating and configuring LTE2430: QCI1 Establishment Triggered Protection Timer feature Parameter

Purpose


Activate RRC connected mode while no activity (actRrcConnNoAct ivity)

activation flag

no

QCI1 protection timer (qci1ProtectionTime r)


no

The following features need to be activated before the activation of the LTE2430: QCI1 Establishment Triggered Protection Timer feature: • •

LTE7: Support of Multiple EPS Bearer LTE10: EPS Bearers for Conversational Voice

Procedure 1


2

Configure the Activate RRC connected mode while no activity (actRrcConnNoActivity) parameter. a) b) c) d)

262

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate RRC connected mode while no activity (actRrcConnNoActivity) parameter's value to true.

DN09185982

Issue: 01D


3


Optional: Configure the QCI1 protection timer (qci1ProtectionTimer) parameter. a) Select the LNCEL object. b) Check the value of the Inactivity timer (inactivityTimer) parameter. c) Set the QCI1 protection timer (qci1ProtectionTimer) parameter's value higher than the Inactivity timer (inactivityTimer) parameter's value.

4


Expected outcome The LTE2430: QCI1 Establishment Triggered Protection Timer feature has been activated. The UE is kept in the RRC connection mode even if there is no activity, for example, during a ringtone, until the established QCI1 timer and all other inactivity timers expire.

3.27.3 Deactivating LTE2430: QCI1 Establishment Triggered Protection Timer Before you start The Activate RRC connected mode while no activity (actRrcConnNoActivity) parameter is used for deactivation. Modification of this parameter does not require eNB restart or object locking. Procedure 1


2

Deactivate the LTE2430: QCI1 Establishment Triggered Protection Timer feature. a) b) c) d)

Issue: 01D

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate RRC connected mode while no activity (actRrcConnNoActivity) parameter's value to false.

DN09185982

263


3



Expected outcome The LTE2430: QCI1 Establishment Triggered Protection Timer feature has been deactivated. QCI1 protection timer is not started or restarted every time the QCI1 bearer is established. The UE is kept in the RRC connection mode even if there is no activity, for example, during a ringtone, until the established QCI1 timer (if it is already running) and all other inactivity timers expire.

264

DN09185982

Issue: 01D


Descriptions of transport and transmission features

4 Descriptions of transport and transmission features 4.1 LTE942: Hybrid Synchronization 4.1.1 Description of LTE942: Hybrid Synchronization Introduction to the feature The LTE942: Hybrid Synchronization feature combines the application of two different and independent synchronization source modes in two variants: Timing over Packet for phase synchronization (ToP-P) as the primary phase synchronization source and Synchronous Ethernet (SyncE) as the secondary (frequency) synchronization source. GPS/1pps as the primary phase synchronization source and Synchronous Ethernet (SyncE) as the secondary (frequency) synchronization source.

•

•

Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The mixed use of GPS/1pps and SyncE or ToP and SyncE significantly improves the phase accuracy and stability. Requirements Hardware and software requirements Table 147


System release FDDLTE15A



-

FL15A


OMS -

UE -



FL15A

-

NetAct

MME

-

-

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview The LTE942: Hybrid Synchronization feature combines the use of Synchronous Ethernet as a second synchronization source together with either •

Issue: 01D

GPS/1pps

DN09185982

265


•


ToP-P

In the table below an overview is given, which synchronization source is chosen. Table 148

Chosen synchronization source

Primary Sync Source

Status

Secondary Sync Source

Status

chosen Sync Source

GPS/1pps

ok

SyncE

ok

GPS/1pps

GPS/1pps

ok

SyncE

nok

GPS/1pps

GPS/1pps

nok

SyncE

ok

SyncE

GPS/1pps

nok

SyncE

nok

normal holdover

ToP-P

ok

SyncE

ok

ToP-P

ToP-P

ok

SyncE

nok

ToP-P

ToP-P

nok

SyncE

ok

SyncE

ToP-P

nok

SyncE

nok

normal holdover

The key principle underlying the LTE942: Hybrid Synchronization feature is illustrated in the figures below: • • • •

Figure 18: Hybrid Sync, GPS1pps/ToD + SyncE, normal tuning Figure 19: Hybrid Sync, GPS1pps/ToD + SnycE, assisted holdover Figure 20: Hybrid Sync, ToP-P/PTP + SyncE, normal tuning Figure 21: Hybrid Sync, ToP-P/PTP + SyncE, assisted holdover

Table 149

Meaning of terms in the figures

Abbreviation

266

Full name

Meaning

PLL

phase-locked loop

Circuit - where the phase of an oscillator signal is forced to follow exactly the phase of a reference signal.

OCXO

oven-controlled crystal oscillator

Oscillator - in which the crystal and critical circuits are temperature-controlled by an oven.

DAC

digital to analogue converter

Device - that converts a digital input signal to an analogue output signal carrying equivalent information.

PTP

precision time protocol

Protocol - that enables precise information of clocks, which are used in measurement and control systems implemented with network communication, local computing, and distributed objects-based technologies.

DN09185982

Issue: 01D



Essential for the LTE942: Hybrid Synchronization feature are two new functional block elements: •

•

SnycE estimator functional block: The SyncE estimator block requires the provision of a new algorithm which keeps the phase error at a constant value. This property cannot be achieved by the algorithm currently used in the 2MHz frequency synchronization block. Estimator selection block: the estimator selection block is required to separate the input data to the tuning block depending on if the primary sync source is available or not.

Figure 18: Hybrid Sync, GPS1pps/ToD + SyncE, normal tuning illustrates a normal tuning of hybrid synchronization with GPS1pps/ToD as the primary source. The GPS1pps signal is ok; therefore, the estimator selection block decides - that the the GPS1pps as the primary source is taken as the synchronization source. Figure 18

Hybrid Sync, GPS1pps/ToD + SyncE, normal tuning

PLL

SyncE estimator

SyncEestimated frequency/phaseerror

SyncE

estimator selection GPS1pps:ok.

OCXO/ framecounter

tuningblock/ DACword DACword

GPS1pps/ToD

sample&hold GPS1pps

estimatedfrequency/ phaseerrors

Figure 19: Hybrid Sync, GPS1pps/ToD + SnycE, assisted holdover illustrates the assisted holdover with a failure of the GPS1pps signal as the primary synchronization source; therefore, the SyncE (the secondory synchronization source) is taken as the synchronization source.

Issue: 01D

DN09185982

267


Figure 19


Hybrid Sync, GPS1pps/ToD + SnycE, assisted holdover

PLL

SyncE estimator


SyncE

GPS1pps:nok.

estimator selection

OCXO/ tuningblock/ DACword framecounter DACword

GPS1pps/ToD

sample&hold GPS1ppsn/a

estimatedfrequency/ phaseerrorsn/a

Figure 20: Hybrid Sync, ToP-P/PTP + SyncE, normal tuning illustrates the normal tuning of hybrid synchronization with ToP-P/PTP as the primary source. The ToP-P/PTP signal is ok; therefore, the estimator selection block decides, that the the ToP/PTP as the primary source is taken as the synchronization source. Figure 20

Hybrid Sync, ToP-P/PTP + SyncE, normal tuning

PLL

SyncE estimator


SyncE

estimator selection ToP-P/PTP:ok.

OCXO/ framecounter

tuningblock/ DACword DACword

ToP-Pdaemon PTPtime stamps

estimatedfrequency/ phaseerrors

Figure 21: Hybrid Sync, ToP-P/PTP + SyncE, assisted holdover illustrates the assisted holdover with a failure of the ToP/PTP signal as the primary synchronization source; therefore, the SyncE (the secondory synchronization source) is taken as the synchronization source.

268

DN09185982

Issue: 01D


Figure 21


Hybrid Sync, ToP-P/PTP + SyncE, assisted holdover

PLL

SyncE estimator


SyncE

ToP/PTPT:nok.

.estimator selection

OCXO/ tuningblock/ DACword framecounter DACword

ToP-Pdaemon PTPtime stampsn/a

estimatedfrequency/ phaseerrorsn/a

Furthermore, the tuning block has to be modified to become aware of the LTE942: Hybrid Synchronization feature. In case the LTE942: Hybrid Synchronization feature is activated, and the primary sync source is lost, it has to use the phase and frequency error estimation which is provided by the SyncE estimator and is linked to its input by the estimator selection unit to enable the assisted holdover mode. Additionally, in case the secondary, that is the SyncE source is lost, the tuning block has to fall back to a normal holdover mode. If the primary sync source is lost, the already implemented ReferenceClockMissing fault is raised with severity minor and sent within the BASE STATION NOTIFICATION alarm. If both - the primary sync source and the secondary sync source (SyncE) are lost, the ReferenceClockMissing fault is raised with severity major and sent within the BASE STATION OPERATION DEGRADED alarm. System impact Interdependencies between features The following features are necessary for the LTE942: Hybrid Synchronization feature: • • •

LTE891: Timing over Packet with Phase Synchronization LTE911: TDD Frame Synchronization Operation LTE713: Synchronous Ethernet

For the LTE942: Hybrid Synchronization feature, GPS/1pps or ToP-P has to be enabled and SyncE has to be configured, but no additional license or activation flag for SyncE is required (SyncE functionality will be part of this 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.

Issue: 01D

DN09185982

269



Impact on system performance and capacity This feature has no impact on system performance or capacity. Management data Alarms The table below lists existing alarms related to this feature. Table 150

Related existing alarms Alarm ID

Alarm name

7651


7652

BASE STATION NOTIFICATION

BTS faults and reported alarms The table below lists BTS faults related to this feature. Table 151

Related existing faults

Fault ID

Fault name


3080

Alarm name

BTSReferenceClockM 7651 issing


7652

BASE STATION NOTIFICATION

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 152

New parameters

Full name feature activation flag for hybrid synchronization

Abbreviated name actHybridSynch

Managed object SYNC

Structure -


Sales information

BSW/ASW ASW

270


DN09185982


Issue: 01D



4.1.2 Activating and configuring LTE942: Hybrid Synchronization Before you start A primary phase synchronization source must be configured. The configuration of the primary synchronization source is not part of this document. Table 154

Parameters used for activating and configuring LTE942: Hybrid Synchronization Parameter

Purpose

Feature activation flag for hybrid synchronization (actHybridSynch)

activation flag

Requires eNB restart or object locking no eNB restart needed

Procedure 1


2

Activate/Configure the LTE942: Hybrid Synchronization feature. a) Go to the TRS Synchronization page. b) Mark the Hybrid synchronization in use check box. c) Select Synchronous Ethernet in the Timing Sources, (as Prio2, if Timing over Packet is the primary synchronization source).

3


Expected outcome The LTE942: Hybrid Synchronization feature is activated.

4.1.3 Deactivating LTE942: Hybrid Synchronization Before you start The Hybrid Synchronization in use check box is used for deactivation. Modification of this parameter does not require an eNB restart or cell locking.

Issue: 01D

DN09185982

271



Procedure 1


2

Deactivate/Set the LTE942: Hybrid Synchronization feature. a) Go to the TRS Synchronization page. b) Unmark the Hybrid Synchronization in use check box. c) Delete Synchronous Ethernet from Timing sources.

3


Expected outcome The LTE942: Hybrid Synchronization feature is deactivated.

4.2 LTE1244: Source-based Routing in BTS 4.2.1 Description of LTE1244: Source-based Routing in BTS Introduction to the feature The LTE1244: Source-based Routing in BTS feature enables routing the eNB traffic according to the source IP address in addition to the destination IP address. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature increases the IP addressing flexibility by introducing a more sophisticated routing mechanism. The feature may make obsolete the need for address replanning and reconfiguration during network migration cases such as Single RAN or multioperator scenarios which require merging of multiple legacy networks operating on identical or overlapping IP subnets. Requirements Hardware and software requirements

272

DN09185982

Issue: 01D


Table 155 System release FDDLTE15A




not supported


FL15A

OMS -

UE -

-



FL15A

-

NetAct

MME -

SAE GW -

Additional hardware requirements This feature requires FSMr3 or FZM hardware. Functional description Functional overview The LTE1244: Source-based Routing in BTS feature extends the routing decision for egress IP packets to take also the source address of IP packets into account. Although the feature is intended for U-plane traffic, it is applicable to all traffic planes. In fact, the feature is applied to all egress unicast IP packets, independent of the application creating the packet. It is also applied to packets received at the LMP and routed to the backhaul. The feature is not applied while routing traffic to the eNB subnet. The feature is applicable to IPv4 as well as IPv6 packets. When the IP packets have to leave the eNB on two different physical interfaces, this has to be achieved by configuring the relation between network IP interfaces and physical interfaces accordingly. For example, two network IP interfaces with different VLAN IDs can be used and the switching functionality can be configured so that each VLAN is accepted on one physical interface only. As a precondition, the IP packets need to have different IP source addresses to be routed differently. Especially if U-plane packets are to be routed differently based on their source address, there need to be different U-plane addresses in the eNB. Multiple Uplane IP addresses are provided by the LTE505 Transport Separation for RAN Sharing or LTE1771 Dual U-plane IP Addresses feature, for which the LTE1244: Source-based Routing in BTS feature is a prerequisite. Route lookup More than one routing table can be configured. Each routing table can contain static routes, used for ordinary destination-based routing using the longest prefix match. A twostep route lookup is used (following the Linux implementation): •

•

Step1: use policies to determine one out of several routing tables. The policies take the source IP address into account (policies are specified with a subnet, see Configuration example). Step2: based on configured routes in each routing table, the destination-based routing with the longest prefix match is used. When no route is found in a table, the search continues with the next policy.

One routing table is considered the main one; all packets for which no policy or no route is found are handled by the main table. Therefore, when the configuration of policies is omitted, then the same behavior as without this feature is achieved. There is a main routing table for each of IPv4 and IPv6. The main routing table is identified by the id 1 of the managed object. In the system, direct routes are added automatically to the main

Issue: 01D

DN09185982

273



routing table, but not to the additional routing tables. Without direct routes, IP packets for directly connected hosts might be sent to the next-hop gateway first. To avoid this behavior, direct routes have to be added to the additional tables too. A policy consists of an IP subnet and a pointer to a routing table. An IP packet matches a policy when its source address is within the subnet; the packet is routed according to the entries of the routing table to which the policy is pointing. Policies are looked up in a fixed order. The order of policies is defined by the operator. In case the subnets of the policies do not overlap, only one of the additional routing tables, and potentially the main table, is searched for routes. Example: The eNB is configured with two U-plane addresses, 10.1.1.1 and 10.1.1.5, and there is just one SAE-GW with an IP address 20.1.1.1 (a specific IP address from the 20.1.1.0/30 subnet). Each of the two routing tables Tbl_2/3 contains just one route towards the SAEGW, but with different next-hop gateways (10.1.1.2 and 10.1.1.6). The main routing table contains in this example just a default route to some next-hop gateway with an a.b.c.d address. Figure 22

Configuration example with two U-plane addresses Tbl_2

Routingpolicies nbr

SrcIP

Subnet

Routing table

1

10.1.1.1

/30

Tbl_2

2

10.1.1.5

/30

Tbl_3

Packetsnotmatchedby policiesarerouted accordingtothemaintable

DestIP

Subnet

Nexthop

20.1.1.0

/30

10.1.1.2

Tbl_3 SrcIPDestIPSubnetSubnet Routing Nexthop table 20.1.1.0 /30 10.1.1.6 main Routing Nexthop DestIPSubnetSubnet table 0.0.0.0 /0 a.b.c.d

An egress IP packet with a 10.1.1.5 source address would match the second policy, and, therefore, Tbl_3 would determine the routing; the next-hop gateway for this packet has a 10.1.1.6 IP address. In this example, there is no need to configure direct routes in the additional routing tables because the only other host in the subnets of the network interfaces is the respective next-hop gateway. Feature activation scenario Actor: Operator Hardware requirements: FSMr3, FZM Pre-condition: Static routes are configured to one routing table. Description: Configure eNB:

274

DN09185982

Issue: 01D


•

• •


Optional: new network interfaces are configured, Ethernet switch configured in eNB, including VLAN filtering. Next-hop gateways in the mobile backhaul reconfigured to allow use of new network interface. One or more additional routing tables are created. Static routes are added to these routing table(s). Routing policies are added to the routing policy table, establishing a mapping of IP subnets to the new routing tables or the main routing table. It is expected that at least some of the application addresses match the routing policies.

Parameter configuration The operator edits the delta plan file and configures at least the following parameter:

g

Note: The order of steps is relevant to avoid routing policies pointing to not yet created routing tables (such policies will not be allowed). •

the Routing policies (routingPolicies) parameter contains the following further parameters: – – – –

Order number of policy (OrderNumber) Reference to routing table (routingTablePtr) Source IP address (srcIpAddress) Source IP Prefix Length (srcIpPrefixLength)

The operator downloads and activates the plan file. The eNB persistently stores the parameter values. The eNB informs NetAct and BTS Site Manager about the changed configuration via notifications. Alarms: There are no alarms for this feature. Measurements: There are no dedicated measurements. IP IF specific counters can be used to check whether there is the expected amount of traffic on different interfaces. Post-conditions: Egress packets are routed according to the new routing configuration. The routing table from the precondition is considered the 'main' routing table (for example see figure Configuration example with two U-plane addresses. The eNB is using the LTE1244: Source-based Routing in BTS feature. User scenario: Source-based routing (with Dual U-plane and SCTP multihoming) An eNB is configured with two separate U-plane addresses, each on its own VLAN. A third VLAN is used for M and S-plane. Two C-plane addresses are used (SCTP multihoming) to illustrate the combined use of the features. One routing policy is used for each of the U-plane addresses. The M/S-plane traffic are handled by the main routing table. The MME IP addresses are from two disjoint subnets. Each C-plane address is used to communicate with peer MMEs in one of the two MME subnets. The traffic can be distributed to two physical interfaces by the switching functionality, but this has been omitted from this scenario for the sake of simplicity. A neighboring eNB, as shown in the diagram, connected via Ethernet.

Issue: 01D

DN09185982

275



For example, the network interface IP addresses are in the respective VLANs and in the same subnet. The X2 traffic among the two eNBs is exchanged directly among the two eNBs; it is not sent by the source eNB to the gateway first and by the gateway to the target eNB. Figure 23

Configuration example with two separate U-plane addresses NetAct 20.1.3.0/24 MME

10.1.1.1/24 10.1.2.1/24 10.1.3.1/24

VLANIDs 11 10.1.1.253/24 12 10.1.2.253/24 13 10.1.3.253/24

20.1.2.0/24

MBH

X2traffic

SAE-GW 20.1.1.0/24

10.1.1.2/24 Topmaster

10.1.2.2/24

11 12 1

10 20.1.4.0/24 9

10.1.3.2/24

8

neighboreNB

7 6 5

2 3 4

Detailed configuration Three VLANs are configured in the eNB with the following IP addresses: VLAN ID 11: 10.1.1.1/24 VLAN ID 12: 10.1.2.1/24 VLAN ID 13: 10.1.3.1/24 These network IP addresses are also used as application addresses: • • •

U1-plane, C1-plane (cPlaneIpAddress): 10.1.1.1 U2-plane, C2-plane (cPlaneIpAddressSec): 10.1.2.1 M-plane, S-plane: 10.1.3.1

The MME IP addresses are from the 20.1.2.0/24 subnet. They are divided into two subnets: MME1 20.1.2.0/25 and MME2 20.1.2.128/25. SCTP messages are intended to be exchanged among C1 and MME1 as well as C2 and MME2 respectively. Each of the routing tables contains just one default route, sending the traffic via different next-hop gateways. Both C-plane IP addresses are used on S1 for SCTP. On X2 just one C-plane address is used, which is C1 (cPlaneIpAddress), 10.1.1.1. To indicate which local C-plane address for S1 is used towards which MME, IP static routes are configured in the main routing table with the preSrcIpv4Addr parameter. The actual routing of packets uses the routing policies and the routes in the respective routing tables to determine the egress interface and next hop for the packet with the selected local C-plane address. When the source-based routing is used without the SCTP multihoming, there is no need to fill in this parameter. A direct route has to be configured in the additional IPRT-2 routing tables, which is used for X2 traffic of both the U-plane and C-plane. The network interface is a /24 subnet containing neighboring eNBs. Without the direct route, the traffic among neighboring

276

DN09185982

Issue: 01D



eNBs would be sent to the next-hop gateway with the 10.1.1.253 address first. As there is no X2 traffic among the eNB and neighburing eNBs on VLAN 12, it is not strictly needed to configure a direct route in IPRT-3. Nevertheless, it is recommended to do so to keep the routing tables similar.

g

Note: It is not possible to configure the preSrcIpv4Addr parameter in the direct routes in the main table; these routes are configured automatically by the eNB.

g

Note: The use of the preSrcIpv4Addr parameter is actually independent of the use of source-based routing. Table 156

IPRT/static routes

destIpAddr

netmask

gateway

preSrcIpv4Ad dr

bfdId

preference

IPRT-1 (main table) 20.1.2.0

255.255.255.1 10.1.1.253

10.1.1.1

20.1.2.128

255.255.255.1 10.1.2.253

10.1.2.1

0.0.0.0

0.0.0.0

0.0.0.0

0

1

10.1.3.253

IPRT-2 10.1.1.0

255.255.255.0 10.1.1.1

0.0.0.0

0

1

0.0.0.0

0.0.0.0

0.0.0.0

0

1

10.1.1.253

IPRT-3 10.1.2.0

255.255.255.0 10.1.2.1

0.0.0.0

0

1

0.0.0.0

0.0.0.0

0.0.0.0

0

1

10.1.2.253

One routing policy is added for each U-plane address. The remaining traffic is handled by the main table. Table 157

RTPOL/routingPolicies

RTPOL/routingPolici es

routingTablePtr

srcIpAddress

srcIpPrefixLength

10

IPRT-2

10.1.1.1

32

20

IPRT-3

10.1.2.1

32

Configuring direct routes The eNB prevents configuring direct routes to the main routing table(s), but the operator can configure one direct route to the additional routing tables for one subnet. System impact Interdependencies between features No other features are impacted directly. This feature is a prerequisite for certain network configurations of LTE505: Transport Separation for RAN Sharing and LTE1771: Dual Uplane IP Addresses.

Issue: 01D

DN09185982

277


g


Note: A dedicated combination of LTE505: Transport Separation for RAN Sharing, LTE648: SCTP Multihoming and LTE1244: Source-based Routing in BTS will not work. This combination is characterized by overlapping IP addresses of the MMEs of the two operators. 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 and 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 Table 158

New parameters

Full name

Abbreviated name

Managed object

Structure

Routing policies

routingPolicies

RTPOL

-

Order number of policy

orderNumber

RTPOL

routingPolicies

Reference to routing table

routingTablePtr

RTPOL

routingPolicies

Source ip address

srcIPAddress

RTPOL

routingPolicies

Source IP Prefix Length

srcIpPrefixLength

RTPOL

routingPolicies

There are no modified parameters related to this feature. Sales information Table 159

Sales information

BSW/ASW BSW

278


DN09185982


Issue: 01D



4.3 LTE1559: SCTP Enhancements 4.3.1 Description of LTE1559: SCTP Enhancements Introduction to the feature The LTE1559: SCTP Enhancements feature enables enhanced configuration options of eNB Stream Control Transmission Protocol (SCTP) endpoints. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The LTE1559: SCTP Enhancements feature introduces user-configurable parameters and new counters for the SCTP protocol. Before the introduction of the LTE1559: SCTP Enhancements feature these SCTP parameters were hard-coded. This feature enables the operator to: make the eNB's SCTP behavior more flexible and more controllable. impove the interoperability with other vendor's eNBs, MMEs and the transmission network. align eNB SCTP configuration parameters with peer SCTP endpoints such as MME or other vendor's eNBs. apply the same set of SCTP configuration parameters across all eNBs if they have eNBs from Nokia and other vendors for maintenance reasons (for example network planing, operability). optimize eNB SCTP configuration parameters to improve the end-to-end quality for example more successful inter-eNB handovers.

• • • •

•

The introduction of SCTP perfomance counters helps the operator to manage and maintain the eNB's SCTP connections efficiently. Requirements Hardware and software requirements Table 160 System release FDDLTE15A


FL15A



OMS -

UE -



FL15A

-

NetAct

MME

-

-

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description

Issue: 01D

DN09185982

279



The LTE1559 SCTP Enhancements feature provides configuration parameters for the retransmission of SCTP INIT and DATA chunks. Furthermore, this feature offers the SCTP peers more inbound and outbound streams (up to 32) at the S1 and X2 interfaces. In addition, it provides configuration parameters for: • •

selective acknowledgement (SACK) frequency and delay SCTP maximum payload size to prevent IP fragmentation along the SCTP path toward the peer.

and a greater range and finer granularity for the Maximum Retransmission Timeout (rtoMax) and Minimum Retransmission Timeout (rtoMin) configuration parameters used in the SCTP algorithm for retransmission timer. System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This LTE1559: SCTP Enhancements feature introduces new parameters for the global SCTP configuration, which is used in the S1-, X2-, M3 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 The table below lists counters introduced with this feature. Table 161

New counters

Counter ID

280

Counter name

Measurement

M8035C0

Number of data chunks sent to LTE S1 SCTP Statistics S1 SCTP peer

M8035C1

Number of data chunks received from S1 SCTP peer

M8035C2

Number of data chunks re-sent LTE S1 SCTP Statistics to S1 SCTP peer

M8035C3

Duration of congested periods of S1 SCTP association

DN09185982

LTE S1 SCTP Statistics


Issue: 01D


Table 161


New counters (Cont.)

Counter ID

Counter name

Measurement

M8035C4

Number of S1 SCTP association state changes to congested


M8035C5

Duration of unavailable periods LTE S1 SCTP Statistics of S1 SCTP association

M8035C6

Number of S1 SCTP association state changes to unavailable

M8036C0

Number of data chunks sent to LTE X2 SCTP Statistics X2 SCTP peer

M8036C1

Number of data chunks received from X2 SCTP peer

M8036C2

Number of data chunks re-sent LTE X2 SCTP Statistics to X2 SCTP peer

M8036C3

Duration of congested periods of X2 SCTP association

LTE X2 SCTP Statistics

M8036C4

Number of X2 SCTP association state changes to congested


M8036C5

Duration of unavailable periods LTE X2 SCTP Statistics of X2 SCTP association

M8036C6

Number of X2 SCTP association state changes to unavailable

M8037C0

Number of data chunks sent to LTE M3 SCTP Statistics M3 SCTP peer

M8037C1

Number of data chunks received from M3 SCTP peer

M8037C2

Number of data chunks re-sent LTE M3 SCTP Statistics to M3 SCTP peer

M8037C3

Duration of congested periods of M3 SCTP association

LTE M3 SCTP Statistics

M8037C4

Number of M3 SCTP association state changes to congested


M8037C5

Duration of unavailable periods LTE M3 SCTP Statistics of M3 SCTP association

M8037C6

Number of M3 SCTP association state changes to unavailable






Key performance indicators There are no key performance indicators related to this feature. Parameters The table below lists new parameters related to this feature.

Issue: 01D

DN09185982

281


Table 162



Abbreviated name

Managed object

LTE M3 SCTP statistics

mtM3SctpStatistics

PMRNL

LTE S1 SCTP statistics

mtS1SctpStatistics

PMRNL

LTE X2 SCTP statistics

mtX2SctpStatistics

PMRNL

SCTP maximum payload size

sctpMaxPayloadSize

SCTP

Selective acknowledge delay

sctpSackDelay

SCTP

Selective acknowledge frequency

sctpSackFreq

SCTP

Wait Time before starting SCTP init after shutdown

sctpWaitTimeInitSeqRetry

SCTP

The table below lists modified parameters related to this feature. Table 163


Abbreviated name

Managed object

SCTP association failure retransmission counter

assocMaxRetrans

SCTP

Minimum retransmission timeout

rtoMin

SCTP

Maximum retransmission timeout

rtoMax

SCTP


Sales information

BSW/ASW


BSW

-

Activated by default yes

4.4 LTE1771: Dual U-plane IP Addresses 4.4.1 Description of LTE1771: Dual U-plane IP Addresses Introduction to the feature The LTE1771: Dual U-plane IP Addresses feature distributes the S1 U-plane traffic to two IP addresses, which enables the utilization of two physical Ethernet interfaces (2xGE or 2xFE) and/or different paths while keeping UE flows intact. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits • •

282

IP networks with two separate transport paths can be supported exceeding UL/DL 1 GE throughput on backhaul interfaces is supported

DN09185982

Issue: 01D


g


Note: The Flexi Zone Micro (FZM) supports only one physical interface for the U-plane (for example, one main backhaul port). Requirements Hardware and software requirements Table 165 System release FDDLTE15A

Hardware and software requirements Flexi Multiradio BTS not supported



OMS -

UE -



FL15A

-

NetAct

MME

-

-

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview All the GTP-U path management messages are supported by the eNB for both the main local GTP-U path endpoint and the second local GTP-U path endpoint. One example of these messages is the GTP-U Path Supervision’s ECHO REQUEST/RESPONSE message. The X2-U-plane traffic of a UE uses, furthermore, only one IP address, which is always mapped to the main U-plane address U1. S1 GTP-U Path Supervision - Dual U-plane IP addresses When the operator has activated the GTP-U path supervision to an S-GW's IP address, the eNB supervises both GTP-U paths towards that S-GW, in parallel. The existing alarm for S1 GTP-U Path Failures is extended so that the eNB can indicate the specific failed GTP-U path to the S-GW. In case of a GTP-U path failure, the specific failed GTP-U path is indicated in the alarm message by the starting and the endpoint of the specific GTP-U path. When one GTP-U path is not available anymore to the S-GW, the eNB raises the “GTP-U Path Failure” fault (alarm), indicating the specific GTP-U path. The severity is ‘major’, and the reported alarm is 7657 BASE STATION CONNECTIVITY DEGRADED. When also the second GTP-U path is not available to the S-GW, the eNB raises the “GTP-U Path Failure” fault (alarm), indicating the specific GTP-U path. The severity is ‘major,’ and the reported alarm is 7657 BASE STATION CONNECTIVITY DEGRADED. Feature application scenarios

g

Note: All IP addresses in the scenarios are exemplary values only. It is expected that the operator uses GTPu-path-supervision to detect possible connection interruptions between eNBs and SGWs. Basic user scenario 1: two networks, the main goal is routing via separate networks

Issue: 01D

DN09185982

283


Figure 24


Basic user scenario 1

10.1.1.2/30

MBH 10.1.1.1/30 20.1.1.1/30 10.1.1.5/30

MBH 10.1.1.6/30

The basic user scenario 1 shows the following characteristics: • • • •

two separate MBH (Mobile Backhaul) networks DL/UL traffic is distributed to both links based on BTS IP addresses decision criterion: load based (on average over time, ~ 50 % of load per link) ingress and egress traffic of all bearers belonging to the same UE goes over the same path

Basis user scenario 2: one network, the main goal is increasing the throughput Figure 25


10.1.1.1/30

10.1.1.2/30

10.1.1.5/30

10.1.1.6/30

MBH

20.1.1.1/30

The basic user scenario 2 shows the following characteristics: • • • •

one MBH network, two external links to eNB DL/UL traffic is distributed to both links based on BTS IP addresses decision criterion: load based (on average over time, ~ 50 % of load per link) ingress and egress traffic of all bearers belonging to the same UE goes over the same path

Basis user scenario 3: one network, the main goal is to separate traffic in the network (not in eNB). This is the only use case which is supported by FZM. Figure 26


10.1.1.1/30 10.1.1.5/30

10.1.1.2/30 10.1.1.6/30

MBH

20.1.1.1/30

The basic user scenario 3 shows the following characteristics: • • •

one MBH network, one external link to eNB two U-addresses are used, but eNB supports only one physical backhaul interface all DL/UL traffic goes over the same physical link

Configuration of LTE1771: Dual U-plane IP Addresses

284

DN09185982

Issue: 01D



The operator wants to configure the system that the LTE1771: Dual U-plane IP Addresses feature can be used in. Actors Operator: the user at the NetAct configurator Pre-conditions • • • •

The eNB is in service. The NetAct is in service, and the O&M connection to eNB is established via OMS. The user plane IPv4/IPv6 address IPNO-uPlaneIpAddress or IPNOuPlaneIpv6Address is configured. The LTE505: Transport Separation for RAN Sharing feature is deactivated, IPNOactSeparationRanSharing is set to 'false'.

Main flow •

The operator edits the delta plan file with at least the following parameters: – – –

• • • •

secondary U-plane Ipv4 address, IPNO-uPlane2IpAddress respectively secondary U-plane Ipv6 address, IPNO-uPlane2Ipv6Address activation flag dual U-plane IP addresses, IPNO-actDualUPlaneIpAddress is set to ‘true’

The operator downloads and activates the plan file. The eNB persistently stores the parameter values. The eNB is restarted. The eNB informs the NetAct and the BTS Site Manager about the changed configuration via notifications.

Taking the feature into use and configuring two external Ethernet links and two Uplane addresses The following use case is an exemplary configuration with exemplary values. Figure 27

Exemplary scenario with two external Ethernet links and two U-plane addresses

BTS internalEthernetinterface,alwaysup, bandwidthonlylimited byfastpathprocessingcapacity

VlanIF100 10.0.0.1/24 Lo 12.0.0.1/32UP1 12.0.0.2/32UP2

next-hoprouter NHIf1 10.0.0.254/24

SGW1 13.0.0.1/24

EIF1

EIF2

VlanIF200 11.0.0.1/24

routing SRC=12.0.0.1 13.0.0.0/24via10.0.0.254 14.0.0.0/24via10.0.0.254

switching EIF1,memberofVL100 EIF2,memberofVL200

NHIF2 11.0.0.254/24

SGW2 14.0.0.1/24

12.0.0.1/32via10.0.0.1 12.0.0.2/32via11.0.0.1

SRC=12.0.0.2 13.0.0.0/24via11.0.0.254 14.0.0.0/24via11.0.0.254

Pre-condition

Issue: 01D

DN09185982

285


• • • • • • • •


eNB is up and running. The LTE1771: Dual U-plane IP Addresses feature is not active, a second U-plane address is not configured. The LTE649: QoS-aware Ethernet Switching feature is active. The FSMr3 HW is used. The 1 Gb/s Ethernet is used. The transport network uses IPv4. A single mobile backhaul network is used. The MBMS is not used.

Event The operator wishes to provide more than 1 Gb/s throughput. Two external Ethernet links and two U-plane addresses which the LTE1771: Dual U-Plane IP Addresses feature supports are used. Operator activities: preparatory steps – network planning 1. The operator plans the target network configuration, including IP addresses and Firewall settings; for this example, the final configuration as shown in the figure is supposed to be used. 2. The operator decides how much of the total bandwidth available on both interfaces is supposed to be used for the GBR traffic. For this exemplary scenario, a value of 200 Mb/s is assumed. Operator activities: configuration of the eNB 1. The operator creates a plan file with FAF=false. 2. The operator configures a second U-plane address. 3. The operator configures VLANs and source-based routing (LTE1244: Source-based Routing) to distribute traffic from the two U-plane addresses to physical ports. 4. The operator configures TAC, and he wishes to use the admitted GBR traffic to 200 Mb/s for the GBR traffic.

g

Note: It is recommended that this value is < 50% of the total bandwidth. 5. The operator downloads the plan file with FAF=false. The eNB does not restart. Operator activities: preparatory steps – network set-up and configuration 1. The operator performs necessary hardware and configuration modifications in the network and related external devices such as plugging link cables, configuring external routers, SAE gateways, and so on. 2. The operator does a connectivity check (ping) from the newly configured U-plane address to the S-GW IP address. Operator activities: activation of the LTE1771: Dual U-plane IP Addresses feature The operator enables the feature activation flag (actDualUPlaneIpAddress), downloads, and activates a second plan file with the aforementioned settings and FAF=true. Post-condition • •

286

The eNB performs a BTS restart, all previously existing connections are released. After the restart, the eNB is up and running, the LTE1771: Dual U-plane IP Addresses feature is active.

DN09185982

Issue: 01D


•

• • •


All new connections are distributed among the two U-plane addresses (about 50% of UEs use the U1 address, others the U2; the sum user traffic is expected to be distributed to U1 and U2 roughly evenly). The eNB can handle > 1Gb/s user traffic. The X2 traffic uses U1 address only. The eNB measures the GBR traffic for both U-plane addresses together and uses this for a transport admission control.

System impact Interdependencies between features The following features have to interact with LTE1771: Dual U-plane IP Addresses in order to establish a higher user data throughput or route user traffic over different network paths: • •

•

• • •

The LTE125: IPv6 for U/C-Plane feature is required to use LTE1771: Dual U-plane IP Addresses with IPv6. The LTE649: QoS-aware Ethernet Switching feature is required in case the traffic is distributed across two physical interfaces, as it provides the needed "independent VLAN MAC address learning". The LTE1244: Source-based Routing feature is needed for correct routing decisions when having a single core destination or IPsec GW destination IP addresses, but using two physical and/or logical interfaces. The LTE866: Fast IP Rerouting feature is recommended for interface resilience; it is mandatory in cases without the IPsec, or it can be used with the IPsec. The LTE1753: Backup IPsec Tunnel feature may be utilized for interface resilience with the IPsec (recommended without the geo-redundant security gateway). The LTE1401: Measurement-based TAC feature is applied to the sum GBR traffic of both U-plane addresses. The operators must consider this in the measurementbased TAC configuration.

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 The LTE1771: Dual U-plane IP Addresses feature is used to increase the user data throughput of the network between eNB and SGWs; for example, if the 2x 1GE is used for connecting an eNB to the transport network, theoretically up to 2 Gb/s can be achieved. Management data BTS faults and reported alarms

Issue: 01D

DN09185982

287


Table 166


Modified BTS faults

Fault ID

Fault name


6150: EFaultId_GtpuPathFailure

GTP-U Path Failure

Alarm name

7657

BASE STATION CONNECTIVITY DEGRADED

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 167

New parameters

Full name

Abbreviated name

Managed object

Structure

Activation Flag Dual U-Plane Ip Addresses

actDualUPlaneIpAddre IPNO ss

-

Activation Flag Transport Separation For RAN Sharing

actSeparationRanShar IPNO ing

-

Secondary Main UPlane Ipv4 Address

uPlane2IpAddress

IPNO

-

Secondary Main UPlane Ipv6 Address

uPlane2Ipv6Address

IPNO

-

There are no modified parameters related to this feature. Table 168


LTAC identifier

Abbreviated name ltacId

Managed object LTAC


Sales information

BSW/ASW ASW



4.4.2 Activating and configuring LTE1771: Dual U-plane IP Addresses Before you start The eNB must already be commissioned. The BTS Site Manager (BTSSM) can be connected to the eNB either locally or remotely. An eNB restart is required after the activation of this feature.

288

DN09185982

Issue: 01D



The eNB is in service. The NetAct is in service and the O&M connection to eNB is established via OMS. The user plane IPv4/IPv6 address IPNO-uPlaneIpAddress or IPNOuPlaneIpv6Address is configured. The LTE505: Transport Separation for RAN Sharing feature is deactivated, IPNOactSeparationRanSharing is set to 'false'.

• • • •

Table 170

Parameters used for activating and configuring LTE1771: Dual U-plane IP Addresses Parameter

Purpose


Activation Flag Dual U-Plane Ip Addresses (actDualUPlaneIpAddress)

activation flag

restart

Secondary Main U-Plane Ipv4 Address (uPlane2IpAddress)


no

Primary Main U-Plane Ipv6 Address (uPlaneIpv6Address)


no

Secondary Main U-Plane Ipv6 Address (uPlane2Ipv6Address)


no

The following features need to be activated/configured before the activation of the Dual U-plane IP Addresses feature: • •

•

•

The LTE125: IPv6 for U/C-Plane feature is required to use Dual U-plane IP Addresses with IPv6. The LTE649: QoS-aware Ethernet Switching feature is required in case the traffic is distributed across two physical interfaces, as it provides the needed "independent VLAN MAC address learning". The LTE1244: Source-based Routing feature is needed for correct routing decisions when having a single core destination or IPsec GW destination IP addresses, but using 2 physical and/or logical interfaces. The LTE1401: Measurement-based TAC feature is applied to the sum GBR traffic of both U-plane addresses. The operators must consider this in the measurementbased TAC configuration.

The LTE505: Transport Separation for RAN Sharing feature is deactivated, IPNOactSeparationRanSharing is set to 'false'. Procedure 1


2

Activate/Configure the Dual U-plane IP Addresses feature. a) Go to the Application Addresses page. b) Check the Dual user plane IP addresses in use checkbox.

Issue: 01D

DN09185982

289



c) Insert a valid IPv4 address in the field for the secondary user plane (optional). d) In case an IPv6 network is used insert a valid IPv6 address in the field for the user plane (optional). e) In case an IPv6 network is used insert a valid IPv6 address in the field for the secondary user plane (optional).

3


Expected outcome The Dual U-plane IP Addresses feature is activated.

4.4.3 Deactivating LTE1771: Dual U-plane IP Addresses Before you start The eNB must already be commissioned. The BTS Site Manager (BTSSM) can be connected to the eNB either locally or remotely. An eNB restart is required after the deactivation of this feature. The Activation Flag Dual U-Plane Ip Addresses (actDualUPlaneIpAddress) parameter is used for deactivation. Modification of this parameter requires an eNB restart. Procedure 1


2

Deactivate the LTE1771: Dual U-plane IP Addresses feature. a) Go to the Application Addresses page. b) Uncheck the Dual user plane IP addresses in use checkbox.

3


Expected outcome The feature LTE1771: Dual U-plane IP Addresses be is deactivated.

290

DN09185982

Issue: 01D



4.5 LTE2063: GNSS Manual Location Entry for Flexi Zone 4.5.1 Description of LTE2063: GNSS Manual Location Entry for Flexi Zone Introduction to the feature The LTE2063: GNSS Manual Location Entry for Flexi Zone feature introduces a Global Navigation Satellite System (GNSS) Manual Location Entry which allows a GNSS phase and time synchronization with connectivity to only one GNSS satellite. The feature is used for BTS site locations that are not optimal for satellite-reception. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature allows operation with connectivity to only one GNSS satellite (versus four that are typically required). This can be particularly beneficial for indoor deployments (such as indoor FzM) or BTSs in urban canyons that tend to deal with poor GNSS reception. Requirements Hardware and software requirements Table 171 System release FDDLTE15A


-



OMS -

UE -



FL15A

-

NetAct

MME

-

-

SAE GW -

Additional hardware requirements This feature requires one of the following GNSS receivers: • •

FZM with integrated GNSS receiver (LTE1629: Integrated GPS Sync for Flexi Zone Micro) FZM with integrated GNSS receiver (LTE1781: Integrated Multi-GNSS Sync Support)

Functional description Functional overview A GPS is a space-based radio-navigation system that provides precise threedimensional (3D) positioning (latitude, longitude, altitude) by using time signals transmitted from satellites. The signals also allow the receivers to calculate the current

Issue: 01D

DN09185982

291



local time with great precision, which allows time synchronization. This satellite navigation system with global coverage is called a Global Navigation Satellite System GNSS). Typically, a minimum GPS constellation is arranged so that a minimum of 4 satellites are in an unobstructed view to determine latitude, longitude, altitude, and the time for a BTS as demonstrated below: Figure 28

Typical environment with a minimum of 4 satellites

GNSS satellite 2

Car

GNSS satellite 3

rier ncy

que

Fre 542

.57

=1 z GH z MH

023

_+ 1,

GNSS satellite 1

GNSS satellite N

In some cases, the physical obstructions may prevent the required four or more satellites-reception from determining the antenna's position. Such a case can be observed when a BTS is placed in an urban canyon environment (see figure Urban canyon environment) or inside a building.

292

DN09185982

Issue: 01D


Figure 29


Urban canyon environment GPS satellite GPS satellite

obst S sig

d GP

ructe

GPS satellite

GPS satellite

l

na

ob

sig

st

S

ru

GP

ct

ed ct

ed G

ru

PS

st

sig

ob

na

l

nal

GPS satellite

urban canyon obstructed GPS visibility

When a BTS is placed in environments with poor reception of the minimum four GPS satellites, it can result in a huge BTS initialization time increase, or it may fail to be initialized at all. This feature enables the user to enter manually the position coordinates for the GNSS-receiver antenna in a BTS. This improves the system's availability in locations with an obstructed GNSS antenna visibility and allows the Flexi Zone Micro BTS to operate in locations that otherwise might have been prohibited. The user fills in the BTS location data based on the GPS satellite coordinate information via position survey method. Four user-configurable GPS location parameters are introduced: • • • •

GNSS receiver altitude (altitudeConf) GNSS receiver latitude (latitudeConf) GNSS receiver longitude (longitudeConf) Location mode (locationMode)

When a BTS is in an environment with as few as one satellite, the user can set the Location mode (locationMode) to surveyed. Then the user can manually enter the BTS location parameters: GNSS receiver latitude (latitudeConf), GNSS receiver altitude (altitudeConf), and GNSS receiver

Issue: 01D

DN09185982

293



longtitude (longitudeConf). With time information obtained from one satellite which is accessible, this method allows the GPS to calculate the current local time with great precision, which allows time synchronization. The operators have various methods available to collect the coordinate information of the GPS satellite. Below, there are a few examples: • •

•

using a surveyor company using a hand-held GNSS receiver at a nearby location; a calculation which is based on the nearby location's coordinates and the distance of the measured location from the actual BTS using Nokia HERE map

The GNSS receiver latitude (latitudeConf) and GNSS receiver longtitude (longitudeConf) data should be accurate to within +/-1 s (+/-30 m) when operating in the surveyed mode, using the World Geodetic System 1984 (WGS84) coordinate system. The GNSS receiver altitude (altitudeConf) data should be accurate to within +/-30 m when operating in the surveyed mode relative to a GPS ellipsoid. The surveyed mode should be used with extreme care and only in situations where it is impossible or impractical to install the GPS antenna in a position where it can typically receive four or more satellites for a significant period of time. The surveyed mode does not reduce the satellite acquisition time and should not be used for this purpose. The use of the surveyed mode needs to be used with caution as any errors in the supplied location data beyond the specified limits can result in significant timing errors or erratic GPS receiver operation. User scenario: enter BTS location manually from NetAct This user scenario describes a NetAct user manually entering the GNSS antenna location while the BTS is in a challenging environment with less than four satellite transmissions available. Actors Technician: the user attempting to manually enter the GNSS antenna location from NetAct Pre-conditions • •

The user is able to manually collect the BTS location information. The time information is obtained from at least one of the satellites.

Main flow • •

The user sets Location mode (locationMode) to surveyed. The user enters the manually collected BTS location information to GNSS receiver latitude (latitudeConf), GNSS receiver longtitude (longitudeConf), and GNSS receiver altitude (altitudeConf).

Post-condition The BTS is able to initialize and provide the LTE2063: GNSS Manual Location Entry feature. System impact Interdependencies between features One of the following features is required as a prerequisite for FZM:

294

DN09185982

Issue: 01D


• • •


LTE1629: Integrated GPS Synch LTE1781: Multi GNSS Support LTE80: GPS Synchronization

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 new or modified alarms related to this feature. Measurements and counters There are no new or modified measurements or counters related to this feature. Key performance indicators There are no new or modified key performance indicators related to this feature. Parameters Table 172


Abbreviated name

Managed object

GNSS receiver altitude

altitudeConf

MRBTS

GNSS receiver latitude

latitudeConf

MRBTS

GNSS receiver longitude

longitudeConf

MRBTS

Location mode

locationMode

MRBTS


Sales information

BSW/ASW ASW

Issue: 01D


DN09185982


295



4.5.2 Activating and configuring LTE2063: GNSS Manual Location Entry for Flexi Zone Before you start For the LTE2063: GNSS Manual Location Entry for Flexi Zone feature, there is no feature activation flag (FAF). Only the parameters for the GNSS satellite must be configured. Changing the Location mode (locationMode) to surveyed activates this feature. Table 174

Parameters used for activating and configuring LTE2063: GNSS Manual Location Entry Full name

Abbreviated name

Managed object

GNSS receiver altitude

altitudeConf

MRBTS

GNSS receiver latitude

latitudeConf

MRBTS

GNSS receiver longitude

longitudeConf

MRBTS

Location mode

locationMode

MRBTS

One of the following features needs to be activated/configured before the activation of the LTE2063: GNSS Manual Location Entry for Flexi Zone feature: • • •

LTE1629: Integrated GPS Synch LTE1781: Multi GNSS Support LTE80: GPS Synchronization

Procedure 1


2

Configure the LTE2063: GNSS Manual Location Entry for Flexi Zone feature. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. c) Set the GNSS receiver altitude (altitudeConf) parameter's value between -250 ... 10000 (in meters). d) Set the GNSS receiver latitude (altitudeConf) parameter's value between 0° 0' 0'' ... 90° 90' 90'' and select N or S. e) Set the GNSS receiver longitude (longitudeConf) parameter's value between 0° 0' 0'' ... 90° 90' 90''and select E or W. f) Set the Location mode (locationMode) parameter's value to surveyed.

296

DN09185982

Issue: 01D


g


Note: Altitude is entered in meters, latitude and longitude are entered in degrees, minutes, and seconds (DMS format). Select N for north, S for south, E for east, or W for west from the drop-down list and type the degrees (°), minutes (’), and seconds (’’) into the respective cells.

3


Expected outcome The BTS is able to initialize and provide the LTE2063: GNSS Manual Location Entry for Flexi Zone feature.

4.5.3 Deactivating LTE2063: GNSS Manual Location Entry for Flexi Zone Before you start For the LTE2063: GNSS Manual Location Entry for Flexi Zone feature, there is no feature deactivation flag (FAF). Only the parameters for the GNSS satellite must be configured. Changing the Location mode (locationMode) to navigated deactivates the feature. Procedure 1


2

Configure the LTE2063: GNSS Manual Location Entry for Flexi Zone feature. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. c) Set the Location mode (locationMode) parameter's value to navigated.

3


Expected outcome The BTS works in the navigated mode. In this mode, typically, a minimum of four satellites are in an unobstructed view.

Issue: 01D

DN09185982

297

Descriptions of operability features


5 Descriptions of operability features 5.1 LTE790: Signed SW 5.1.1 Description of LTE790: Signed SW Introduction to the feature The LTE790: Signed SW feature guarantees that the eNB software packages are genuine products (proof of origin) and that the software was not modified after leaving factory (integrity verification). The eNB checks the origin and integrity of software before it starts to use it. Benefits End-user benefits There is no effect on the end-user experience. Operator benefits Risk management is enhanced by ensuring that the eNB is running genuine software that was not faked or modified after leaving factory. Requirements Hardware and software requirements Table 175: Hardware and software requirements lists hardware and software requirements for the LTE790: Signed SW feature. Table 175


System release





FDD-LTE 15A

Not supported

FL15A

FL15A

-


OMS

UE

NetAct

MME

SAE GW

-

-

-

15.5

-

-

Additional hardware requirements No new or additional hardware is required. Functional description To be compliant with the 3GPP recommendation TS 33.401, the eNB checks the origin and integrity of any software package installed in it. The LTE790: Signed SW feature ensures that the software package has not been altered after leaving the factory. This functionality enhances an already implemented software verification procedure introduced by LTE940: SW Verification Agent. Software verification procedure The software verification procedure is shown in figure below.

298

DN09185982

Issue: 01D


Figure 30


Software verification procedure in LTE790

softwaredownload fromNOLS softwaretransfer toeNB eNBdownloads: targetBD.xml,hashcontainer,hashcontainersignaturefiles

hashcontainer verification

signature ok?

NO

LTE790

YES extractofsoftwarefiles

YES

softwarefiles integrityverification

secureboot-up

hash ok?

hash ok?

YES

NO

software rejected

NO

LTE940

The software is distributed to customers using Nokia Online Services (NOLS). The customer then may use the NetAct or BTS Site Manager to install software in an individual eNB. Software verification starts after it has been downloaded to an eNB. The first file examined by the eNB is the hash container in TagetBD.xml. First the signature and then the hash value of the hash container itself is examined. The signature must be provided by an entity that can be verified by a Nokia trust chain. If an eNB hash container file or its signature file is not present, or the verification of the signature failed, the Failure to verify the signature of a signed software release fault occures, and the base station notification alarm is raised. As a result, software download fails and must be re-tried. If the hash container files pass verification, the eNB examines all new or modified files. For each individual file, the eNB calculates a hash value and compares it with the hash value stored in the hash container file. If hash validation failed or the hash value is missing, the Failure to verify a signed software release fault occures, and the base station notification alarm is raised. As a result, software download fails and must be re-tried. If the values are matching, it means that the software has not been modified in any way and can be safely used by the eNB. If all individual files pass an integrity check, the eNB stores the signatures received with the signed SW download together with the software package in a non-volatile memory. The local signature is needed for the eNB to perform a secure boot. For more information on the secure boot, see LTE940: SW Verification Agent.

Issue: 01D

DN09185982

299


g


Note: This feature provides full backwards compatibility with older (unsigned) software releases. If a user installs a software package without a signature (for example, a software downgrade to an older release), the eNB continues to download the software but generates the Unsigned software release has been successfully downloaded fault. If it is a download without activation, the unsigned software build is only downloaded to a passive file system, and the previous build is still used. If it is downloaded with activation after a BTS reset, the new, downloaded, unsigned software build is used. System impact Interdependencies between features The LTE940: SW Verification Agent is a prerequisite for the LTE790: Signed SW feature. Impact on interfaces There is no impact on interfaces. Impact on network management tools There is no impact on network management tools. Impact on system performance and capacity There is no impact on system performance or capacity. Management data BTS faults and reported alarms Table 176: New BTS faults lists BTS faults introduced with this feature. Table 176

New BTS faults

Fault ID

Fault name


300

Alarm name

4266: Failure to verify the EFaultId_SwBuildSign signature of a signed atureVerificationAl software release

7652

base station notification

4267: Failure to verify a EFaultId_SwBuildEle signed software mentSignatureVerificat release ionAl

7652


4268: Unsigned software EFaultId_UnsignedSw release has been ReleaseAl successfully downloaded

7652


4269: Failure to download EFaultId_SwBuildSign software due to atureMissingAl missing software signature

7652


DN09185982

Issue: 01D



Measurements and counters No measurements or counters are related to this feature. Key performance indicators No key performance indicators are related to this feature. Parameters No existing parameters are related to this feature. Sales information Table 177: Sales information lists sales information related to the LTE790: Signed SW feature. Table 177

Sales information

BSW/ASW


BSW

-


5.2 LTE1030: Configurable Service Accounts 5.2.1 Description of LTE1030: Configurable Service Accounts Introduction to the feature The LTE1030: Configurable Service Accounts feature allows the configuration of the BTS Service Account's password as well as the configuration of SSH key-based authentication credentials. It also allows the operator to enable/disable access to SSH and R&D services via the BTS Site Manager. Benefits End-user benefits There is no effect on the end-user experience. Operator benefits The configurable BTS Service Account's password and associated access services give the operator full control over local and remote access to the eNB. Requirements Hardware and software requirements Table 178: Hardware and software requirements lists software and hardware requirements of the LTE1030: Configurable Service Accounts feature. Table 178

Issue: 01D


System release





FDD-LTE15A

FL15A (only FCM part of Flexi

FL15A

FLF15A

-

DN09185982

301


Table 178



System release





Multiradio BTS. The FTM part is not in the scope of this feature) Flexi Zone Controller

OMS

UE

NetAct

MME

SAE GW

-

-

-

-

-

-

Additional hardware requirements No additional hardware is required Functional description The BTS Service Account is used by the technical support personnel in response to service requests. A remote or local service access to the eNB is done over the SSH protocol using credential-based (username/password) or key-based authentication. The LTE1030: Configurable Service Accounts feature allows the operator to modify the factory default password for the BTS Service Account ("toor4nsn") and configure up to ten RSA public keys for SSH key-based authentication. The account name is fixed and can't be modified. Additionally, the operator gains control over access to SSH and R&D service port by: • • • •

enabling or disabling the SSH access to the eNB enabling or disabling R&D service port (TCP ports in the 15001-15006 range) configuring the SSH session login delay timer (the time between an unsuccessful login and the next possible login attempt) configuring the SSH Client Alive timer (the time to automatically close idle SSH sessions)

Feature configuration can be done using the BTS Site Manager, NetAct Configurator, and the Network Element Access Control (NEAC) tool with the following scope : •

BTS Site Manager (one eNB at a time): – – – – –

•

NetAct Configurator (individual or multiple eNBs): – – –

302

modify the BTS Service Account's password display, add, modify, and delete RSA public keys stored in the eNB, which are used for BTS Service Account authentication configure the SSH Client Alive timer and SSH session login delay timer enable or disable the SSH access to the eNB enable or disable R&D service ports

display, add, modify, and delete RSA public keys stored in the eNB, which are used for BTS Service Account authentication configure the SSH Client Alive timer and SSH session login delay timer enable or disable the SSH access to the eNB (not recommended)

DN09185982

Issue: 01D


enable or disable R&D service ports (not recommended)

–

g


Note: For the micro eNB, SSH and R&D service ports setting is enabled temporarily (the setting is valid only until the eNB is rebooted). By default, reboot disables the SSH access and R&D services. On the macro eNB, the SSH and R&D service port access setting is retained across reboots. •

NEAC tool (individual or multiple eNBs): –

modify the BTS Service Account's password

Changes in feature configuration using the BTS Site Manager (enabling/disabling SSH access and/or R&D services) as well as any initiation and termination of an SSH session are logged. The BTS also logs commands executed during the SSH session. System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces There is no impact on interfaces. Impact on network management tools There is no impact on network management tools. Impact on system performance and capacity There is no impact on system performance or capacity. Management data Alarms No alarms are related to this feature. Measurements and counters No measurements or counters are related to this feature. Key performance indicators No key performance indicators are related to this feature. Parameters Table 179: New parameters lists new parameters related to the LTE1030: Configurable Service Accounts feature.

Issue: 01D

DN09185982

303


Table 179



Abbreviated name

Managed object

SSH Session Login Delay Timer

sshSessionLoginDelayTimer

SECADM

SSH Client Alive Timer

sshClientAliveTimer

SECADM

Service User Public Keys

serviceUserPublicKeys

SECADM

Key Value

keyValue

SECADM

Key Description

keyDescription

SECADM

Activate Service Account SSH

actServiceAccountSsh

SECADM

Activate Service Port State

actServicePortState

SECADM

Service Account SSH Status

serviceAccountSshStatus

SECADM

Service Port Status

servicePortStatus

SECADM

Sales information Table 180: Sales information lists sales information related to the LTE1030: Configurable Service Accounts feature. Table 180

Sales information

BSW/ASW


BSW

-


5.2.2 Configuring LTE1030: Configurable Service Accounts Before you start The LTE1030: Configurable Service Accounts feature is activated by default; however, there are several parameters that are related to this feature and can be configured along with it. The parameters are listed in table below. Table 181

Parameters used for configuring LTE1030: Configurable Service Accounts Parameter

304

Purpose


Activate Service Account SSH (actServiceAccountSsh)


no

Activate Service Port State (actServicePortState)


no

SSH Client Alive Timer (sshClientAliveTimer)


no

SSH Session Login Delay Timer (sshSessionLoginDelayTimer)


no

Service User Public Keys (serviceUserPublicKeys)


no

Key Value (keyValue)


no

Key Description (keyDescription)


no

DN09185982

Issue: 01D


Table 181


Parameters used for configuring LTE1030: Configurable Service Accounts (Cont.) Parameter

User name/ New password

Purpose optional configuration


Settings related to this feature can be found in Configuration ► Service Account Access Settings menu. Figure 31

Service Account Access Settings menu

The screenshot above is taken from the LTE15A BTS Site Manager. The feature, except service account password, can also be configured using Commisioning option.

g

Note: If you change the default password, it will not be possible to return to it. Every password must have at least two numbers and an upper-case and lower-case character. To configure the feature, do the following:

Issue: 01D

DN09185982

305



Procedure 1


2

Configure the parameters related to this feature. a) Go to the Radio Network Configuration page. b) Select the SECADM object and set the following parameters to desired values: • • • •

Activate Service Account SSH (actServiceAccountSsh) Activate Service Port State (actServicePortState) SSH Client Alive Timer (sshClientAliveTimer) SSH Session Login Delay Timer (sshSessionLoginDelayTimer)

c) Right click the SECADM object and create the Service User Public Keys (serviceUserPublicKeys) list. Set the Key description and Key value to desired values.

3


Expected outcome The paramteres related to the LTE1030: Configurable Service Accounts feature are configured.

5.2.3 Configuring LTE1030: Configurable Service Accounts using NEAC It is possible to change the service account password using NetAct's NEAC tool. Purpose To modify the service account using the Network Element Access Control (NEAC) tool, do the following:

306

DN09185982

Issue: 01D



Procedure 1

Open Start Page on NetAct and navigate to the Security section.

2

Open the Network Element Access Control tool.

3

Open the Credential tab.

4

Press New...

5

Configure the required options. • • • •

for Service type select Privileged User Access from drop-down list in UserName enter toor4nsn in Password and Confirm Password enter the new password for Network Element select the most suitable option

Figure 32

6

Changing the toor4nsn password in NEAC tool

Press Save.

Result The new service account password has been deployed. It is possible to log in to the FSM by using the modified credentials.

Issue: 01D

DN09185982

307



5.3 LTE1049: MDT - UE Measurement Logs 5.3.1 Description of LTE1049: MDT - UE Measurement Logs Introduction to the feature The LTE1049: MDT - UE Measurement Logs feature allows the eNodeB to support the configuration and retrieval of user equipment (UE) measurement logs as well as to report those with a cell trace. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature enables the UE measurement log function to minimize the drive test effort. Requirements Hardware and software requirements Table 182: Hardware and software requirements presents the hardware and software requirements for this feature. Table 182



FL15A



FL15A

OMS -


UE -


NetAct NetAct 15.5

Flexi Zone Access Point FL16

MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview A drive test (DT) is a manual method which allows the operator to gather information about the network in a particular area. Such parameters as the radio signal quality, signaling events or throughput are measured from the field and recorded by dedicated equipment. There are many expensive tools used for drive tests. To have detailed information about network behavior, operators should perform DTs periodically for the whole coverage area, due to constantly changing network traffic conditions and the consequent need for optimization activities. Using such an approach is costly for operators. A minimization of drive tests (MDT) has been proposed in order to meet operator requirements. It is a method of collecting the DT data directly from regular UEs used in the network; it is a less expensive approach to DTs. There are two modes of MDT measurements:

308

DN09185982

Issue: 01D


• •


logged MDT immediate MDT

The LTE1049: MDT – UE Measurement Logs feature is focused only on the logged MDT measurements mode. The logged MDT is a mode where the UE is able to collect measurements during RRC IDLE state and store them for up to 48 hours. However, the configuration parameters for the logged MDT mode and the logged MDT measurement reports shall be sent when the UE is in the RRC CONNECTED state. There are two independent the logged MDT initiation scenarios : •

•

signaling - based activation (SBA) - the operator initiates a subscriber-specific trace session in NetAct or a third-party tool by issuing an MDT trace session activation message towards the core network (CN); it is not in the scope of the feature. management - based activation (MBA) - the operator initiates an area-based trace session in NetAct, TraceViewer, or the BTSSM by issuing an MDT trace session activation message towards an eNodeB.

The operator initiates an area-based trace session in NetAct, TraceViewer, or the BTSSM by issuing an MDT trace session activation message towards an eNodeB. The eNodeB has stored the information that the UE is allowed to perform MDT measurements in RRC IDLE state. After receiving the MDT trace session activation message, the eNodeB starts selecting capable UEs, based on the parameters, and sends them the configuration. When Logged MDT trace session starts, and the UE is in RRC CONNECTED state, it is capable of obtaining the configuration message. Only when the UE is in RRC IDLE state, it is collecting the required measurements and storing them in internal memory. When the UE comes back into RRC CONNECTED state it is able to send collected logs toward the eNodeB. If operator wants to use UE consent functionality, he needs to ensure that relevant information is stored in home subscriber server (HSS). Anonymization of data sent to Trace Collection Entity (TCE) is possible for MBA Logged MDT. The UE measurement logs contain the following information: • • • • •

location info (global navigation satellite system (GNSS) information is optional for the UE) time stamp serving cell ID serving cell measurements neighbor cell measurements

Measurements configuration The MDT measurement configuration procedure for the logged MDT is unidirectional; it is sent to the UE by the RRC signaling procedure. The logged MDT measurement reports are linked to the original logged MDT configuration. It means that any new logged MDT measurement configuration will wipe out any logged MDT measurements obtained with a corresponding previous configuration. Therefore, before sending a new LoggedMeasurementConfiguration message, the eNodeB will obtain collected measurements from the UE. This is to avoid losing any MDT data already stored in the UE.

Issue: 01D

DN09185982

309



The eNodeB activates at the UE the requested MDT measurement via the LoggedMeasurementConfiguration procedure, providing the following information to the UE: • • • • • • •

trace reference trace recording session reference TCE ID (The network has a configured mapping of the IP address of the TCE (to which the Trace records shall be transferred) and the TCE Id) area configuration logging interval logging duration absolute time and reference area's scope, where the UE measurements should be collected

A release operation for the logged MDT measurement configuration is realized by: • •

g

configuration clearance duration timer expiration Note: Data retrieval will be carried out before sending a new logged MDT configuration message.

Measurements reporting Data availability indicator When a UE is configured for a logged MDT and has the measurements in its memory, it sets the data availability indicator within the following messages: • • •

g

RRCConnectionSetupComplete RRCConnectionReestablishmentComplete RRCConnectionReconfigurationComplete Note: This is to notify that the UE has the measurements in its memory and is able to send them towards the eNodeB.

Report retrieval The collected MDT measurements will be requested from eNodeB via UEInformationRequest message and delivered from UE to eNodeB via UEInformationResponse message. The data are normally retrieved in the cell where the availability is signaled. But the data which are retrieved need not to be from the cell where the availability is signaled. The data of the UE logs might be sent in multiple RRC signaling messages. System impact Interdependencies between features The following features are related to LTE1049: MDT – UE Measurement Logs: • • • •

310

LTE53: Intra - and Inter-eNB Handover with X2 LTE54: Intra - LTE Handover via S1 LTE57: Inter - RAT Handover from UTRAN LTE162: Cell Trace with IMSI

DN09185982

Issue: 01D



Impact on interfaces The LTE1049: MDT – UE Measurement Logs feature introduces RRC Logged measurement configuration and RRC UE information procedure which are supported on Uu, X2, and S1. 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 new measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 183: New parameters presents parameters introduced with this feature. Table 183

New parameters

Full name

Issue: 01D

Abbreviated name

Managed object

Structure

Activate MDT logged MBA

actMDTloggedCellTrace

LNBTS

-

TCE ID to IP mapping

tceIdLogMdtIpMap

CTRLTS

-

Trace port number for logged MDT

loggedPortNum

CTRLTS

tceIdLogMdtIpMap

Logged TCE IP address

loggedTCEIP

CTRLTS

tceIdLogMdtIpMap

Logged TCE ID

loggedTCEId

CTRLTS

tceIdLogMdtIpMap

TCE MDT mobile country code

loggedTCEmcc

CTRLTS

tceIdLogMdtIpMap

TCE MDT mobile network code

loggedTCEmnc

CTRLTS

tceIdLogMdtIpMap

TCE MNC length in MDT PLMN identity

loggedTCEmncLen

CTRLTS

tceIdLogMdtIpMap

MDT logged cell trace session identifier

ltraceId

LTRACE

-

MDT logged trace enableLoggedMdtTRSSta LTRACE recording session start rtStopInd stop ind

-

DN09185982

311


Table 183



Full name

Abbreviated name

Managed object

Structure

Cell global ID EUTRA

eutranCellList

LTRACE

-

BTS ID

btsId

LTRACE

eutranCellList

LCR ID

lcrId

LTRACE

eutranCellList

MCC

mcc

LTRACE

eutranCellList

MNC

mnc

LTRACE

eutranCellList

MNC length

mncLength

LTRACE

eutranCellList

MDT logged cell configuration

loggedCellConf

LTRACE

-

Cell global ID list

cellId

LTRACE

loggedCellConf

MDT logged cell working mode

mode

LTRACE

loggedCellConf

Logged MDT configuration

loggedMDTConf

LTRACE

-

Anonymization of MDT data

anonymizationMDTdata

LTRACE

loggedMDTConf

Force UE consent

forceUEconsent

LTRACE

loggedMDTConf

Logged TCE ID in configuration

loggedTCEId

LTRACE

loggedMDTConf

Logging duration

loggingDuration

LTRACE

loggedMDTConf

Logging interval

loggingInterval

LTRACE

loggedMDTConf

MDT logged standalone GNSS UEs selection

selectOnlyStandaloneGN SSUes

LTRACE

loggedMDTConf

Tracking area list

taList

LTRACE

-

PLMN identity per TAC list

plmnPerTAlist

LTRACE

-

MDT per TAC mobile country code

mdtperTAmcc

LTRACE

plmnPerTAlist

MDT per TAC mobile network code

mdtperTAmnc

LTRACE

plmnPerTAlist

MDT per TAC MNC length PLMN identity

mdtPerTAmncLen

LTRACE

plmnPerTAlist

MDT logged trace reference

traceReference

LTRACE

-

Trace ID

traceId

LTRACE

traceReference

MDT logged trace reference MCC

traceReferenceMcc

LTRACE

traceReference

MDT logged trace reference MNC

traceReferenceMnc

LTRACE

traceReference

MDT logged trace reference MNC length

traceReferenceMncLen

LTRACE

traceReference

Sales information

312

DN09185982

Issue: 01D



Table 184: Sales information presents sales information about this feature. Table 184

Sales information

BSW/ASW


ASW

SW asset monitoring


5.3.2 Activating and configuring LTE1049: MDT - UE Measurement Logs Before you start Table 185: Parameters used for activating and configuring LTE1049: MDT - UE Measurement Logs presents parameters used for activating and configuring the feature. Table 185

Parameters used for activating and configuring LTE1049: MDT - UE Measurement Logs Parameter

Purpose


Activate MDT logged MBA (Activate MDT logged MBA)

activation flag

no

TCE ID to IP mapping (tceIdLogMdtIpMap) structure


no

MDT logged cell trace session identifier (ltraceId)


no

MDT logged trace rec. session start stop ind (enableLoggedMdtTRSStartStopIn d)


no

Cell global ID EUTRA (eutranCellList) structure


no

MDT logged cell configuration (loggedCellConf) structure


no

Logged MDT configuration (loggedMDTConf) structure


no

Tracking area list (taList)


no

PLMN identity per TAC list (plmnPerTAlist)


no

MDT logged trace reference (traceReference)


no

To activate the feature, do the following:

Issue: 01D

DN09185982

313



Procedure 1


2

Activate the feature flag. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate MDT logged MBA (actMDTloggedCellTrace) parameter's value to true.

Configure the TCE ID to IP mapping (tceIdLogMdtIpMap) structure. a) b) c) d) e) f) g)

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Right-click the CTRLTS object. Set the NetAct IP address (netActIpAddr). Select the CTRLTS object. Right-click the CTRLTS object and create the TCE ID to IP mapping (tceIdLogMdtIpMap) structure. h) Set the following parameters to desired values: • • • • • •

4

Configure the LTRACE object. a) b) c) d) e) f)

314

Logged TCE ID (loggedTCEId) Logged TCE IP address (loggedTCEIP) TCE MDT mobile country code (loggedTCEmcc) TCE MDT mobile network code (loggedTCEmnc) TCE MNC length in MDT PLMN identity (loggedTCEmncLen) Trace port number for logged MDT (loggedPortNum)

Go to the Radio Network Configuration page. Expand the MRBTS object. Expand the LNBTS object. Select the CTRLTS object. Right-click the CTRLTS object and create the LTRACE object. Set the MDT logged cell trace session identifier (ltraceId) and MDT logged trace rec. session start stop ind (enableLoggedMdtTRSSta rtStopInd) parameter values.

DN09185982

Issue: 01D



g) Right-click the LTRACE object and create the Cell global ID EUTRA (eutranCellList) structure.

g

Note: The Cell global ID EUTRA (eutranCellList) can be configured only if the Tracking area list (taList) does not exist. h) Set the following parameters to desired values: • • • • •

BTS ID (btsId) LCR ID (lcrId) MCC (mcc) MNC (mnc) MNC length (mncLength)

i) j)

Configure the MDT logged cell configuration structure. Set the Cell global ID list (cellId) and MDT logged cell working mode (mode) parameter values. k) Configure the Logged MDT configuration (loggedMDTConf) structure. l) Set the following parameters to desired values: • • • • • •

Anonymization of MDT data (anonymizationMDTdata) Force UE consent (forceUEconsent) Logged TCE ID in configuration (loggedTCEId) Logging duration (loggingDuration) Logging interval (loggingInterval) MDT logged standalone GNSS UEs selection (selectOnlyStandaloneGN SSUes)

m) Configure the MDT logged trace reference (traceReference) structure. n) Set the following parameters to desired values: • • • •

5

g

MDT logged trace reference MCC (traceReferenceMcc) MDT logged trace reference MNC (traceReferenceMnc) MDT logged trace reference MNC length (traceReferenceMncLen) Trace ID (traceId)

Configure the Tracking area list (taList) (optional). Note: The Tracking area list (taList) can be configured only if the Cell global ID EUTRA (eutranCellList) structure is disabled. a) Right-click the LTRACE object and create a Tracking area list (taList). b) Right-click the LTRACE object and create the PLMN identity per TAC list (plmnPerTAlist) structure.

g

Issue: 01D

Note: The PLMN identity per TAC list (plmnPerTAlist) can be set only if the Tracking area list (taList) is present. If the PLMN identity per TAC list (plmnPerTAlist) is present the number of list entries for Tracking area list (taList) and PLMN identity per TAC list (plmnPerTAlist) is equal.

DN09185982

315



c) Set the following parameters to desired values: • • •

6

MDT per TAC MNC length PLMN identity (mdtPerTAmncLen) MDT per TAC mobile country code (mdtperTAmcc) MDT per TAC mobile network code (mdtperTAmnc)


Expected outcome The LTE1049: MDT - UE Measurement Logs feature is activated.

5.3.3 Deactivating LTE1049: MDT - UE Measurement Logs Before you start The Activate MDT logged MBA (actMDTloggedCellTrace) parameter is used for deactivation. Modification of this parameter does not require an eNodeB restart. To deactivate the feature, do the following: Procedure 1


2

Deactivate the LTE1049: MDT - UE Measurement Logs feature. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate MDT logged MBA (actMDTloggedCellTrace) parameter value to false.


Expected outcome The LTE1049: MDT - UE Measurement Logs feature is deactivated.

316

DN09185982

Issue: 01D



5.4 LTE1052: Transport Configuration Fallback 5.4.1 Description of LTE1052: Transport Configuration Fallback Introduction to the feature The LTE1052: Transport Configuration Fallback feature reverts the former working configuration of the base transceiver station (BTS) and informs the operator about the failed configuration update when the BTS fails to connect to its management network after a configuration update. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits A self-healing measure reduces the effort on network management and maintenance by avoiding site visits and increases the availability of the network because of less outages. Requirements Hardware and software requirements Table 186



FL15A



FL15A

OMS -


UE -


NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview When the BTS fails to connect to its management network after a transport configuration update via a full site configuration file (SCF) or a delta SCF, self-healing measures are applied. A self-healing measure automatically activates the previous transport configuration when the BTS fails to connect to its management network. The LTE1052: Transport Configuration Fall-back feature is controlled via a configuration parameter (activation flag). The self-healing measure is initiated only for transport network layer (TNL) configuration changes. The TNL configuration refers to transport parameters. When the configuration changes that contain transport and non-transport changes are initiated and the BTS fails to connect to its management network, self-healing measure is only applied to the transport portion of the configuration changes, that is, only the previous transport configuration is activated and the non-transport configuration changes are not reverted.

Issue: 01D

DN09185982

317



In scenarios where both integrated operation mediation system (iOMS) resiliency and transport configuration fallback are configured, the autonomous fallback to the previous configuration shall be attempted only after iOMS resiliency is activated and did not fix the management plane (M-plane) problem. When the M-plane is established with the previous configuration, an alarm notification is sent to the network management system, which indicates that the new configuration is not activated. If the previous configuration fails, the received new configuration is activated again and the BTS continues with the regular link failure mechanism. This feature does not ensure the full eNB function in all circumstances, but the M-plane connection to the eNB is re-established in case that the failure was on a wrong transport parameter setting. 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 BTS faults and reported alarms Table 187: New BTS faults lists the BTS faults introduced with this feature. Table 187

New BTS faults

Fault ID

Fault name


61638

Configuration change rejected by BTS

7665

Alarm name BASE STATION TRANSMISSION ALARM

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 188: New parameters lists the parameters introduced with this feature.

318

DN09185982

Issue: 01D


Table 188



Abbreviated name

Activate transport configuration actTransportConfigFallback fallback

Managed object MRBTS


Sales information

BSW/ASW ASW



5.4.2 Activating and configuring LTE1052: Transport Configuration Fallback Before you start The Activate transport configuration fallback (actTransportConfigFallback) parameter is used for activation. Modification of this parameter requires eNB restart. Procedure 1


2

Activate the LTE1052: Transport Configuration Fallback feature. a) Go to the Radio Network Configuration page. b) Select the MRBTS object. c) Set the Activate transport configuration fallback (actTransportConfigFallback) parameter value to true.

3


Expected outcome The LTE1052: Transport Configuration Fallback feature is activated.

Issue: 01D

DN09185982

319



5.4.3 Deactivating LTE1052: Transport Configuration Fallback Before you start The Activate transport configuration fallback (actTransportConfigFallback) parameter is used for deactivation. Modification of this parameter requires eNB restart. Procedure 1


2

Deactivate the LTE1052: Transport Configuration Fallback feature. a) Go to the Radio Network Configuration page. b) Select the MRBTS object. c) Set the Activate transport configuration fallback (actTransportConfigFallback) parameter value to false.

3


Expected outcome The LTE1052: Transport Configuration Fallback feature is deactivated.

5.5 LTE1058: Plug and Play Extensions 5.5.1 Description of LTE1058: Plug and Play Extensions Introduction to the feature The LTE1058: Plug and Play Extensions feature provides Plug and Play without the need for a Dynamic Host configuration Protocol (DHCP) server and supports the reset of an already commissioned BTS to "not commissioned" to redo commissioning. In addition, more detailed Plug and Play reports are provided. Benefits End-user benefits No effect on the end-user experience. Operator benefits The LTE1058: Plug and Play Extensions feature allows using powerful iSON autoconfiguration capabilities in networks without a DHCP server.

320

DN09185982

Issue: 01D



In case of misconfigurations or such operative needs as a BTS relocation, the operator can reset the BTS to “not commissioned”, thus executing Plug and Play again. The Plug and Play proceeding is logged in reports. During Plug and Play all important events and statuses are visible in the reports including timing behavior. Requirements Table 190 System release FDD-LTE 15A Flexi Zone Controller FL15A



-

FL15A

OMS LTE OMS15A

UE -


FL15A

NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements The feature supports the FSMr3 and FZM modules. The feature does not support the following modules: • • •

FSME FTLB FTLIB

Functional description Functional overview To get an overview about the auto connection features with or without the DHCP server, please take notice of the features • •

LTE154: SON LTE BTS Auto Connectivity with DHCP server LTE1058: Plug and Play Extensions without DHCP server

. LTE154: SON LTE BTS Auto Connectivity • • • •

Parameters obtained from DHCP server Includes Nokia-specific DHCP options Supports no-touch Plug and Play RL50FZ (LTE154: SON LTE BTS Auto Connectivity) - Legacy RL10 feature

For an overview of Plug and Play auto connection with DHCP server, please see the figure: LTE154 Auto Connection with DHCP server.

Issue: 01D

DN09185982

321


Figure 33


LTE154 Auto-Connection with DHCP server Operator’s Network DHCP

DNS

Flexi Zone Small Cell

CA Server

SeGW

OMS

NetAct iSON Mgr

EPC

LTE1058: Plug and Play Extensions The LTE1058: Plug and Play Extensions feature: • • • •

provides Plug and Play without the need for a DHCP server allows the usage of the BTS Site Manager for manual parameter entry at site supports the reset of an already commissioned BTS to "not commissioned" to either repeat Plug and Play automatically or redo a manual commissioning provides more detailed Plug and Play reports

The BTS needs basic auto-connection parameters in order to establish connection with the operator’s Security Gateway (SeGW), Certificate Authority Server (CA Server), and Configuration Server (iOMS). Figure 34

LTE1058 Auto Connection without DHCP server Operator’s!Network DHCP

Flexi!Zone Small!Cell

DNS

CA!Server

SeGW

OMS

NetAct iSON!Mgr

EPC

Plug and Play without DHCP server To support scenarios where no DHCP server is available in the network, the transport configuration can be commissioned with a minimum set of parameters by the installer who enters only auto-connection relevant IP-addresses and parameters with the BTS site manager.

322

DN09185982

Issue: 01D



Afterwards, the eNB continues auto-connection and connects automatically to the OMS/NetAct for auto-configuration. The NetAct auto-configuration workflow is not influenced. Mandatory configurable parameters: • • • •

IP address of the eNB/management plane subnet mask of the eNB/management plane gateway for the eNB/management plane IP address of the identification server (hosted by an OMS)

Optional configurable parameters: • • • •

the IP address of the certificate authority (CA) server (CMP directory server, or registration authority server) port number of the CA server subject name for the CA server CMP directory (URL) on the CA server (mandatory if an IP address of the CA server is configured and the default directory for the HTTP access is different from http: // IPaddress: port/pkix/)

IPsec: IP address of the security gateway - if configured. The eNB will setup the O&M connection within an IPsec tunnel. Plug and Play Ethernet VLAN: This VLAN ID is used by the eNB to connect to the access network for the autoconfiguration. If not given, the eNB uses untagged Ethernet frames.

g

Note: The usage of the transport layer security protocol (TLS) for PnP is not directly configurable. If the public key infrastructure (PKI) turns out to be configured, the eNB will try to set up a secure TLS connection to the OAM system in the probing mode. If the secure setup fails, the eNB will continue PnP in an unsecure mode. Reset a BTS to “not commissioned” In case of any problems, it is possible to reset a BTS with a local connected BTS site manager to “not commissioned”, thus forcing the BTS to run the complete Plug and Play sequence again or to run a manual commissioning sequence. For the repeated PnP auto-connection phase, the BTS uses the previously configured BTS ID to identify against the identification server or a new one, in case the field engineer entered a new BTS ID. In case of a reset due to BTS relocation, typically a new and unique BTS identifier will be used for a new site (and entered by the field engineer).

g

Note: In case the BTS shall be relocated to another site and the Flexi System Module serial number is used as unique BTS identifier on the NetAct side, special attention is required. The existing configuration plan file needs to be substituted by a new initial plan file before the Flexi System Module starts Plug and Play. Otherwise, for example, the RNW parameters of the old site will be applied to the new site. The identification server and NetAct auto-configuration workflow are enhanced to allow multiple repeated PnP sequences by the same eNB.

Issue: 01D

DN09185982

323



The management-user can choose between two options: 1. Without deleting of the operator security credentials such as the operator certificate, trust anchors, and the local operator user ID and password - this is the default setting. When PnP is subsequently restarted, no new initial key signing request for a new operator entity certificate is sent. 2. With deleting of the operator security credentials. For example, the operator certificate is deleted, the vendor certificate is restored, the local maintenance user account and service user accounts are reset to factory defaults. When PnP is subsequently restarted, a new initial key signing request for a new operator entity certificate is sent, providing the case an operator's PKI is in place. The execution of the command needs to be double confirmed and is logged in the user's log file. Plug and Play Report While auto-connection and auto-configuration are running, important events and the status, which are required to analyze problems, are logged in the Plug and Play report by the BTS. The log contains in a human readable form: • • • • • • • • • • • •

all steps of workflow with results the status and the results of the workflow sub-steps the connection-setup to PKI (if used) the messages (essential parts) sent and received to/from PKI such as the initial request and result (if used) the connection-setup to OMS the messages sent and received to/from OMS such as the connection established indication with a response the identification information and all parameters received from BTSSM, if any the status of NE before the auto-connection starts which includes such information as the certificate name and SW build version the timestamp in all logged messages; note that the time of day (ToD) is not available while auto-connection is running; typically, the relative time is logged details of external messages and replies to the DHCP server, CA server, identification server (IS), OMS and BTSSM IPSec with internet key exchange (IKE) version in case of exceptions, the cause of negative result is included

Plug and Play Report upload by the iSON manager As soon as iSON is informed about the completion of the eNB auto-configuration, it uploads the eNB Plug and Play report. First the report is uploaded from the eNB to the NetAct global file system and second the iSON manager fetches the plug and play report from there. iSON stores the report file in the automatic site creation (ASC) disk area and indicates the plug and play report existence in the ASC Site user interface (UI) to the user.

g

324

Note: the iSON manager shows the hyperlink to the plug and play report file in the site UI as soon as the plug and play report is available. On user request, the iSON manager visualizes the complete human readable PnP report.

DN09185982

Issue: 01D



For details see Use case 4: Plug and Play Report Upload from NetAct to the iSON manager Plug and Play Report upload to BTS Site Manager The user can upload the Plug and Play report to the BTSSM at any time (even while Autoconnection is ongoing). Additional Plug and Play enhancements auto-connection/configuration Auto-connection and auto-configuration can be followed from the auto-connection monitoring dialogue on the BTSSM. The auto-connection monitoring dialogue opens during the BTS auto-connection and includes two additional status indications: 1. certificate update 2. wait for auto-configuration Use cases The following use cases are described: Use case 1: BTS auto-connection without DHCP-server's support Use case 2: eNB commissioned - restart of auto-connection Use case 3: Reset to not commissioned of an eNB in service Use case 4: Plug and Play Report Upload from NetAct to the iSON manager Figure 35: Use cases illustrates auto-connection without DHCP and restart of autoconnection triggered by the user.

Issue: 01D

DN09185982

325



Figure 35

Use cases

Use!case!1:!no!DHCP!server in!operator’s!network,!but auto-configuration!is!available

NetAct!iSON auto-configuration

Start auto-configuration Local configured PnP!transport parameters

Clear PnP!state

BTS!site manager

Use!case!2:!eNB!commissioned PnP!shall!be!repeated “not commissioned”

Repeat PnP

BTS!site manager

Use case 1: BTS auto-connection without DHCP-server's support The BTS auto-connection is used, but the customer does not provide the DHCP. Actors: BTS HW installer Trigger: BTS HW is installed and the BTS is powered up Pre-conditions: • • • •

The NE is configured with a software version supporting DHCP-less auto-connection. The installer has connected the BTSSM locally. The connected BTSSM version supports DHCP-less auto-connection. In the case of a Flexi Zone eNB: all platform startup actions necessary to support this use case have occurred: – – –

the FxP has established an IP connectivity with the m-plane IP address any IPSec tunnels required are established the eNB is connected to the NE3S interface and has downloaded its software/configuration and has completed the startup

Description: 1. The NE starts the auto-connection procedure. 2. The AC-monitoring user Interface (UI) is opened in the BTSSM and the current AC status is displayed. 3. The user requests entry of the AC transport parameters.

326

DN09185982

Issue: 01D



4. The AC-parameter UI is opened; in case any parameters are available already either entered at an earlier time or detected autonomously by the eNB - they are shown in the dialogue. 5. The user enters or modifies the AC transport parameters (plus optionally the AC SiteId) in the AC-parameter dialogue and selects the Send button. 6. A warning informs to the user that the autonomous AC procedure will be stopped, if parameters are sent to the BTS. 7. After user's confirmation, the AC parameters are sent to the BTS. 8. The NE stops the automatic AC-procedure. 9. The NE continues the AC without DHCP. 10. The auto-connection is finished and auto-configuration is requested via the CCN from NetAct. Post-conditions: The BTS auto-connection has been executed with manually entered AC transport parameters. Figure 36: Use case 1: Visualization illustrates a BTS auto-connection without DHCPserver's support.

Issue: 01D

DN09185982

327


Figure 36


Use case 1: Visualization BTSsitemgr

BTS

BTSsitemgris connectedtoBTS

auto-connectionis startedafterHWinstall andpower-up

Open ACmonitoringUI Installerrequestsentryof auto-connectionparameters Showcurrentuser paramcontent

Query ACPARvalues

Reply ACPARparametervalues

BTScollectscontentof AC parameters(ACPAR)thatmay havebeenenteredbyuserat earlierstep

Showcontentof AC parametersinclsiteidtouser Usermodifies ACPARatBTSSM UIandsendsthemtoBTS Opt:update ACsiteid

Update ACPAR byuser Usershowsawarning thatautomaticprocedure maybestopped Userconfirmswarning Update ACPARvalues BTSstopsautomaticprocedure, replacesexisting ACparameter valueswithdownloadedonesand restarts ACprocedure Note:entryof ACsiteidalone doesnotneed ACrestart Reply ACPARparametervalues

Use case 2: eNB commissioned - restart of auto-connection While auto-connection is running, the user wants to trigger “Clear and Restart” of autoconnection in order to remove the AC parameters and restart the auto-connection procedure. Actors: BTS HW installer Trigger: BTS HW is installed and the BTS is powered up Pre-conditions:

328

DN09185982

Issue: 01D


• • • •


The NE is configured with a software version supporting the DHCP-less autoconnection. The NE is currently performing the auto-connection procedure. The installer has connected the BTSSM locally. The connected BTSSM version supports DHCP-less auto-connection.

Description: 1. The AC-monitoring user interface (UI) is opened in the BTSSM and the current AC status is displayed. 2. The user requests “AC Clear and Restart” using a special button in the ACmonitoring user interface. a) The user is offered to remove the AC Site Id parameter, which is otherwise kept per default. b) The user is offered to remove the security credentials. 3. A warning is displayed to indicate that this function will cause the AC procedure to be discontinued and all data (except AC Site Id) will be lost in the BTS. 4. After user's confirmation, the BTSSM triggers the BTS to restart the auto-connection. 5. The NE clears the node: a) The NE deletes all available AC parameters. The ACSiteId is removed at a distinct request only. b) The NE removes the security credentials, if this option was selected by the user. 6. The NE restarts auto-connection. Post-conditions: The BTS auto-connection is restarted and the user can decide whether • •

any transport parameters shall be entered manually the parameters shall be retrieved by the BTS autonomously

Figure 37: Use case 2: Visualization illustrates an eNB-commissioned restart of the autoconnection.

Issue: 01D

DN09185982

329


Figure 37


Use case 2: Visualization

BTS Site Mgr

BTS

Prerequisite: BTS Site Mgr is connected to BTS

Auto-connection is started after HW Install and Power-up

AC Monitoring UI is opened

Installer requests AC Restart from respective button

The AC Restart can be requested by user at anytime while Auto-connection procedure is ongoing. Optionally AC Site Id parameter and security credentials can be removed.

User has to confirm that all data will be lost and AC will start from scratch AC Clear and Restart

After confirmation by user: BTSSM stops AC ClearAutoconnParams Request

Stop the ongoing Auto-connection procedure Reset all AC parameters to default values (except AC Site Id) Remove security credentials if required by user Ack/Nack

Restart Auto-connection

Use case 3: Reset to not commissioned of an eNB in service The use case describes the scenario where the eNB is reset to not commissioned state from BTSSM locally and restarts auto-connection and -configuration. Actors: User at BTSSM Pre-conditions: • •

g

The NE is installed and in service or at least auto-connection/configuration is started. The prepared plan is available in NetAct and up to date with relation to the NE SW version. Note: The plan needs be updated/re-created after a release upgrade of the NE.

•

The BTSSM is connected locally to the NE.

Description:

330

DN09185982

Issue: 01D



1. The user at the BTSSM requests a configuration reset for the locally connected NE. Optionally the user takes the options to: remove the Autoconnection Site Id value remove the security credentials

• •

2. The NE verifies the current state to check whether ConfigReset can be handled, need to be rejected, or other operations need to be aborted. 3. The NE initializes as requested and: removes the configuration data except the AC SiteId parameter, which - if available - is kept per default removes the security credentials, if explicitly requested by the user

• •

4. The NE restarts and finds itself uncommissioned. 5. The NE restarts auto-connection using the stored ACSiteId for identification - if it wasn't removed explicitly - and connects to OMS. 6. The NE sends a notification to iOMS/NetAct to request auto-configuration (CCN with commissioningRequired=TRUE).

g

Note: The CCN includes additional parameters like autoConfBlocked. 7. NetAct verifies, whether the auto-configuration workflow shall be restarted. 8. NetAct (re-)starts the Autoconfiguration workflow.

g

Note: • •

The prepared plan is downloaded to the NE and activated. The SW version is downloaded from NetAct to the NE that is indicated in the prepared configuration plan; in case the same SW version is already installed, the file transfer is skipped.

Post-conditions: • • • •

g

The NE is restarted with the SW version as indicated in the prepared plan. The M-plane connection is re-established. The NE is in service, but the configuration data may be of older version. In case the prepared plan wasn't updated by the user for some time the configuration changes will be missing accordingly. Note: The Reset can be triggered also in state locked/blocked of the NE cells. While reset/re-configuration of the NE those states will vanish.

Figure 38: Use case 3: Visualization illustrates a reset to not commissioned of an eNB in service

Issue: 01D

DN09185982

331


Figure 38


Use case 3: Visualization

BTS Configuration Reset followed by AutoConnection and AutoConfiguration BTSSM

eNB

NetAct

iOMS

User requests Configuration Reset for the connected NE from Configuration menu User is asked for confirmation of the Configuration Reset ConfigurationResetRequest eNB checks status, eventually sends negative reply to CMS on ongoing O&M operations or rejects the Reset (while activation is ongoing). Otherwise configuration data are removed from NVS. Ack/Nack

NE RESET eNB restarts Autoconnection taking former AC Site Id into account - if requested in Configuration Reset eNB requests Autoconfiguration CCN (commissioningRequired)

CCN (commissioningRequired) AC workflow starts SW download swMassDownloadRequest

swUpdateRequest

SW file transfer swUpToDate (success)

swDownloadReply (success) next AC workflow step Plan download

eNB activates SW eNB Reset

beginDownloadRequest

FileLoadPrepare

OMS retries plan download when no reply CB CCN (commissioningRequired)

CCN (commissioningRequired) CCN is ignored Autoconfiguration is ongoing

FileLoadPrepare (Retry) Plan download fileLoadCompleted

operationFeedback next AC workflowstep Plan upload

Plan activation Auto configuration is ended from NE point of view

next AC workflowstep Plan upload

Plan upload

Use case 4: Plug and Play Report Upload from NetAct to the iSON manager

332

DN09185982

Issue: 01D



The use case describes the upload of the auto-configuration report to the iSON manager. The upload is triggered as soon as the auto-configuration is completed and the PnP report file is successfully uploaded to the NetAct file system. Pre-conditions: • • • • • •

Auto-connection has been performed with success. The M-plane connection eNB – iOMS – NetAct is setup. The auto-configuration is finished. The NetAct CM has marked the auto-configuration status according to its result. The PnP report file is uploaded to the NetAct file system. The iSON manager has registered to the auto-configuration status.

Description: 1. iSON is informed about the auto-configuration state (completed/failed) by the status update notification (iSON is registered to the auto configuration status maintained by the NetAct CM). 2. iSON sets up a timer to allow eNB, iOMS and NWI3 mediation to upload the PnP report file to the NetAct file system after the auto-configuration is finished. 3. After the timer expiry, iSON triggers the upload of the PnP report file to the automatic site creation (ASC) disk area that is dedicated for that purpose. 4. iSON indicates the existence of the PnP report to the user in the ASC Site UI (hyperlink to PnP report is shown). 5. On user request iSON visualizes the complete human readable PnP report. Post-conditions: • • •

The auto-configuration report is uploaded to the ASC and stored in the dedicated ASC repository. The auto-configuration report existence is indicated in ASC Site UI. On request the auto-configuration report is visualized to the user.

System impact Interdependencies between features The following features influence LTE1058: Plug and Play Extensions: • •

• •

LTE1992: HW Replacement RP000579 autoconnection without DHCP server This feature covers the DHCP-less PnP for FDSW. It also enables clearing autoconnection parameters in the BTS and restarting the auto-connection. RP000514 Boot up SW The feature defines the auto-connection report for FDSW. RAN2559 Plug and Play Extensions The feature contains the same functionality as LTE1058: Plug and Play Extensions for WCDMA.

Impact on interfaces This feature impacts the following interfaces: •

Issue: 01D

interfaces between the BTS and OMS

DN09185982

333


• •


PnP-report upload to NetAct interfaces between the OMS and NetAct Plug and Play report upload to NetAct interface between the BTS and BTSSM – – – –

enhanced AC status information from the BTSOM to BTSSM AC TRS parameters delivered from the BTSSM to TRS configuration reset including the option to remove security credentials PnP report upload from the BTSOM to BTSSM

Impact on network management tools No impact on network management tools. Impact on system performance and capacity This feature impacts system performance and capacity as follows: • •

OMS supports the storage of the Plug and Play report files for a reasonable number of connected NEs. NetAct supports the storage of the Plug and Play files for the managed eNBs.

Management data Alarms No alarms are related to this feature. Measurements and counters No measurements or counters are related to this feature. Key performance indicators No key performance indicators are related to this feature. Parameters No new parameters are related to this feature. The following parameters can be entered from BTSSM for DHCP less PnP. • • • • • • • • • •

auto-connection Site Id for BTS BTS management plane Default gateway Identification server CMP/CA server CA subject name CMP directory CMP URL Security gateway VLAN ID

Sales information

334

DN09185982

Issue: 01D



Table 191: Sales information presents the sales information for the LTE1058: Plug and Play Extensions feature. Table 191

Sales information

BSW/ASW


BSW

-

Activated by default yes

5.6 LTE1103: Load Based Power Saving for Multi-layer Networks 5.6.1 Description of LTE1103: Load Based Power Saving for Multi-layer Networks Introduction to the feature The LTE1103: Load Based Power Saving for Multi-layer Networks feature saves energy during low-load periods in the network where there is more than one provisioned frequency. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature reduces operating expenditure (OPEX) by saving electricity during off-peak hours. Requirements Hardware and software requirements Table 192



FL15A



FL15A

OMS -


UE -


NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview

Issue: 01D

DN09185982

335



The LTE1103: Load Based Power Saving for Multi-layer Networks feature allows the operator to save energy during low-load periods. The load-based power saving is limited to the resources within a single evolved node B (eNB). The power saving mode (PWSM) allows the operator to use the LTE1103: Load Based Power Saving for Multi-layer Networks feature according to cell configuration and power amplifier mapping. The cells in the eNB can be grouped for PWSM. These power group cells have the same coverage and the Load-based power saving cell switch off order (lbpsCellSOOrder) parameter defines the order in which the power group cells are switched off. The eNB monitors the load in the served cells and triggers cell switch off once all of the following conditions are met: During the time of the day defined by the user for cell switch off. There are no ongoing emergency calls and no queued messages for Earthquake and Tsunami Warning System (ETWS) or Commercial Mobile Alert System (CMAS) in the cell. The complete load of the cells in the power saving group is below the low load threshold. The estimated complete load immediately after cell switch off for the remaining active cells in the power saving group does not exceed the high load threshold.

• •

• •

g

Note: The eNB will not switch off a power group cell and will switch on a cell in energy saving mode if fault 7651 BTS degraded is raised on the eNB or if the cell has any of the following faults: • •

7653 Cell faulty 7654 Cell operations degraded

Similar to the LTE914: Graceful Cell Shutdown feature, the LTE1103: Load Based Power Saving for Multi-layer Networks feature gradually reduces cell power so that the active calls are handed over before cell switch off. The cell is barred before it is switched off in the eNB. The traffic is moved to other cells during cell switch off. The eNB turns the power amplifier to standby mode.

g g

Note: Switching off of all cells in the eNB is possible for special cases such as indoor office environment with macro cell coverage from another eNB. The cell is activated at a defined time of the day. Note: If a cell is beginning to switch off and the operator wants to revert the cell to full power, perform the following steps: 1. Set the Load-Based Power Saving Suspended (lbpsSuspended) PSGRP parameter value to true and the Administrative state (administrativeState) LNCEL parameter value to locked. This completes the cell switch off that must be done before switching on the cell. All other power saving group cells with administrativeState LNCEL parameter set to unlocked will have services enabled. 2. Set the administrativeState LNCEL parameter value to unlocked to enable services in the cell.

336

DN09185982

Issue: 01D



The eNB continues to monitor the load on the active cells after the cell switch off. A cell that was switched off can be activated if the total traffic load of the active cells in the power saving group exceeds the user-defined high traffic threshold. The LTE1103: Load Based Power Saving for Multi-layer Networks feature does not require the exchange of X2 data between Flexi Multiradio BTSs. It is recommended to first switch off the higher frequency layer. System impact Interdependencies between features The LTE1103: Load Based Power Saving for Multi-layer Networks feature affects the following features: •

•

•

•

•

•

•

•

LTE1117: LTE MBMS A cell configured to support multimedia broadcast/multicast service (MBMS) cannot participate in load-based power saving. Energy saving must not be configured to switch off a cell that is configured for MBMS. LTE432: Cell Outage Detection Cell outage detection is not triggered for a cell in energy saving state (energySavingState parameter = 1). LTE494: Commercial Mobile Alert System Energy saving must not be configured to switch off the last enabled cell in the power saving group configured to provide CMAS service. Also, a cell is not set to energy saving state if there are queued CMAS messages. LTE843: ETWS Broadcast Energy saving must not be configured to switch off the last enabled cell in the power saving group that is configured with the LTE843: ETWS Broadcast feature. Also, a cell cannot be set to energy saving state if there are queued ETWS messages. LTE1685: Neighbor Relation Robustness Existing neighbor relations do not change when a cell is in energy saving state. The neighbor cells become available when the cell is restored. LTE495: OTDOA Energy saving is not allowed to switch off the last enabled cell in the power saving group that is configured with the LTE495: OTDOA feature. LTE1542: FDD Supercell The creation of power saving groups must recognize that a super cell is treated as a single cell that has two sub-cells, which serve the same area. enhanced inter-cell interference coordination (eICIC) features: – –

•

LTE1113: eICIC - macro LTE1496: eICIC – micro

The cell that is switched off informs the other cell in an eICIC partnership. load balancing/load equalization features: – – – – –

LTE1140: Intra-frequency Load Balancing LTE1841: Inter-frequency Load Equalization LTE1531: Inter-frequency Load Balancing Extension LTE1170: Inter-frequency Load Balancing LTE1387: Intra eNodeB Inter-frequency LB

The value of the lbpsMaxLoad parameter for energy saving must be less than the value of the following load balancing (LB) threshold parameters:

Issue: 01D

DN09185982

337


– – –

•


highLoadGbrDl highLoadNonGbrDl highLoadPdcch

This reduces the probability that LB will be used to balance the load across the active cells while there are disabled power group cells because of energy saving. radio frequency (RF) sharing features: – – –

LTE435: RF Sharing WCDMA-LTE LTE1556: 3-RAT RF Sharing 2G-3G and 2G-4G LTE1829: LTE-LTE RF sharing

It is recommended that energy saving is not configured for cells in the power saving group that support RF sharing. Impact on interfaces The load on the S1 interface is the same or less when the operator initiates the cell shutdown. Impact on network management tools An integrated self-organizing network (iSON) manager application can be used to create and update the power saving groups at the selected set of eNBs. Impact on system performance and capacity The overall capacity of each power saving group is reduced to only what is needed by the UEs in the system. Management data Alarms There are no alarms related to this feature. Measurements and counters Table 193: New counters lists the counters introduced with this feature. Table 193

New counters

Counter ID

Counter name

Measurement

M8020C7

Samples when the cell is in power saving mode

LTE Cell Availability

M8020C8

Number of cell state changes to power saving mode


Table 194: Modified counters lists the counters modified by this feature. Table 194

Modified counters

Counter ID M8020C1

338

Counter name Number of cell state changes to planned unavailable

DN09185982

Measurement LTE Cell Availability

Issue: 01D


Table 194


Modified counters (Cont.)

Counter ID

Counter name

Measurement

M8020C2

Number of cell state changes to unplanned unavailable


M8020C4

Samples when the cell is planned unavailable


M8020C5

Samples when the cell is unplanned unavailable


Key performance indicators There are no key performance indicators related to this feature. Parameters Table 195: New parameters lists the parameters introduced with this feature. Table 195

New parameters

Full name

Issue: 01D

Abbreviated name

Managed object

Structure

Activate load-based power saving

actLBPowerSaving

LNBTS

-

Energy saving state

energySavingState

LNCEL

-

Load-based power saving iSON control enabled

lbpsISONCtlEnabled

PSGRP

-

Load-based power saving last cell minimum load

lbpsLastCellMinLoad

PSGRP

-

Load-based power saving last cell switch off enabled

lbpsLastCellSOEnabled

PSGRP

-

Load-based power saving maximum load

lbpsMaxLoad

PSGRP

-

Load-based power saving minimum load

lbpsMinLoad

PSGRP

-

Load-based power saving PDCCH load offset

lbpsPdcchLoadOffset

PSGRP

-

Power saving group identifier

psGrpId

PSGRP

-

Load-based power saving cell list

lbpsCellList

PSGRP

-

Load-based power saving cell switch off order

lbpsCellSOOrder

PSGRP

lbpsCellList

LTE cell configuration identifier

lnCelId

PSGRP

lbpsCellList

Load-based power saving period list

lbpsPeriodList

PSGRP

-

DN09185982

339


Table 195



Full name

Abbreviated name

Managed object

Structure

Load-based power saving day of week

lbpsDayOfWeek

PSGRP

lbpsPeriodList

Load-based power saving duration

lbpsDuration

PSGRP

lbpsPeriodList

Load-based power saving start time hour

lbpsStartTimeHour

PSGRP

lbpsPeriodList

Load-based power saving start time minute

lbpsStartTimeMinute

PSGRP

lbpsPeriodList

Load-Based Power Saving Suspended

lbpsSuspended

PSGRP

lbpsPeriodList

Table 196: Related existing parameters lists the existing parameters related to this feature. Table 196


Full name Idle Time Threshold for LTE Neighbour Relations

Abbreviated name idleTimeThresLteNR

Managed object

Structure

LNBTS

-

Intra- and inter-freq. loadSettings load bal. common load settings

LNCEL

-

Cell capacity class value

cellCapClass

LNCEL

loadSettings

Mode for calculating the CAC in load bal. and eICIC

mlbEicicOperMode

LNCEL

loadSettings

Nominal number of PRBs for load balancing

nomNumPrbNonGbr

LNCEL

loadSettings

DL GBR resource target load

targetLoadGbrDl

LNCEL

loadSettings

DL non-GBR resource targetLoadNonGbrDl target load

LNCEL

loadSettings

PDCCH target load

targetLoadPdcch

LNCEL

loadSettings

Uplink CAC source selection

ulCacSelection

LNCEL

loadSettings

Static CAC for uplink

ulStaticCac

LNCEL

loadSettings


Sales information

BSW/ASW ASW

340

License control in network element Pool license

DN09185982


Issue: 01D



5.6.2 Activating and configuring LTE1103: Load Based Power Saving for Multi-layer Networks Before you start The Activate load-based power saving (actLBPowerSaving) parameter is used to activate the feature. Modification of this parameter does not require eNB restart or object locking. Table 198

Parameters used for activating and configuring LTE1103: Load Based Power Saving for Multi-layer Networks feature Parameter

Issue: 01D

Purpose


Activate load-based power saving (actLBPowerSaving)

mandatory

no

Power saving group identifier (psGrpId)

mandatory

no

Load-based power saving iSON control enabled (lbpsISONCtlEnabled)

mandatory

no

Load-based power saving last cell minimum load (lbpsLastCellMinLoad)

mandatory

no

Load-based power saving last cell switch off enabled (lbpsLastCellSOEnabled)

mandatory

no

Load-based power saving maximum load (lbpsMaxLoad)

mandatory

no

Load-based power saving minimum load (lbpsMinLoad)

mandatory

no

Load-based power saving PDCCH load offset (lbpsPdcchLoadOffset)

mandatory

no

LTE cell configuration identifier (lnCelId)

mandatory

no

Load-based power saving cell switch off order (lbpsCellSOOrder)

mandatory

no

Load-based power saving day of week (lbpsDayOfWeek)

mandatory

no

Load-based power saving duration (lbpsDuration)

mandatory

no

Load-based power saving start time hour (lbpsStartTimeHour)

mandatory

no

Load-based power saving start time minute (lbpsStartTimeMinute)

mandatory

no

Load-Based Power Saving Suspended (lbpsSuspended)

mandatory

no

DN09185982

341



Procedure 1


2

Set the activation flag. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate load-based power saving (actLBPowerSaving) parameter value to true.

Create a new PSGRP object. a) Right-click the selected LNBTS object. b) Create a new PSGRP object. c) Define the value for the following parameters: • • • • • • •

g 4

Power saving group identifier (psGrpId) Load-based power saving iSON control enabled (lbpsISONCtlEnabled) Load-based power saving last cell minimum load (lbpsLastCellMinLoad) Load-based power saving last cell switch off enabled (lbpsLastCellSOEnabled) Load-based power saving maximum load (lbpsMaxLoad) Load-based power saving minimum load (lbpsMinLoad) Load-based power saving PDCCH load offset (lbpsPdcchLoadOffset) Note: The parameters, except for the psGrpId parameter, have default values set during the object creation. Modification of the default values is not mandatory.

Define the serving cells and switch-off order in the power saving group. a) Expand the selected PSGRP object. b) Select the Load-based power saving cell list (lbpsCellList) parameter. c) Perform the following configurations: •

342

Create an entry in the LTE cell configuration identifier (lnCelId) parameter for each cell in the power saving group.

DN09185982

Issue: 01D


g


Note: A cell must be a member of only one power saving group and each lnCelId parameter must match the lnCelId of an existing LNCEL. •

g

Set the Load-based power saving cell switch off order (lbpsCellSOOrder) parameter with a unique value for each cell ranging from 1 to 100. Note: The cell assigned with the largest value is not switched off if the lbpsLastCellSOEnable parameter is set to false. The parameter value of 100 can be assigned to multiple cells.

5

Create an entry for each energy saving time period and define all the parameters within the structure for each time period. a) Select the Load-based power saving period list (lbpsPeriodList) parameter. b) Define the value for the following parameters: • • • • •

Load-based power saving day of week (lbpsDayOfWeek) Load-based power saving duration (lbpsDuration) Load-based power saving start time hour (lbpsStartTimeHour) Load-based power saving start time minute (lbpsStartTimeMinute) Load-Based Power Saving Suspended (lbpsSuspended)

The lbpsStartTimeHour and lbpsStartTimeMinute parameters define the start time for the power saving period. The power saving period ends after the number of minutes defined in the lbpsDuration parameter has lapsed.

g 6

Note: The LTE1103: Load Based Power Saving for Multi-layer Networks feature does not support daylight saving time (DST).


Expected outcome The LTE1103: Load Based Power Saving for Multi-layer Networks feature is activated in the eNB. The control parameters and power saving groups are downloaded and activated in the eNB.

Issue: 01D

DN09185982

343



5.6.3 Deactivating LTE1103: Load Based Power Saving for Multilayer Networks Before you start The Activate load-based power saving (actLBPowerSaving) parameter deactivates the feature. Modification of this parameter does not require eNB restart or object locking. Procedure 1


2

Configure the Activate load-based power saving (actLBPowerSaving) parameter. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate load-based power saving (actLBPowerSaving) parameter value to false.


Expected outcome The LTE1103: Load Based Power Saving for Multi-layer Networks feature is deactivated in the eNB. The cells in energy saving state are switched on.

5.7 LTE1225: Parameter Level Logging of BTS User Events 5.7.1 Description of LTE1225: Parameter Level Logging of BTS User Events Introduction to the feature The LTE1225: Parameter Level Logging of BTS User Events feature allows a more detailed audit trail by including changes in parameter values made by the user with the BTS Site Manager or Transport Webpage. Once NetAct retrieves the logged content, the operator is able to track changes with the Audit Trail application in NetAct. Benefits

344

DN09185982

Issue: 01D



End-user benefits There is no effect on the end-user experience. Operator benefits With an enhanced eNB logging, the operator is provided with more detailed information about changes in the eNB's configuration. More detailed logs enhance security and ease troubleshooting. Requirements Hardware and software requirements Table 199: Hardware and software requirements lists software and hardware requirements of the LTE1225: Parameter Level Logging of BTS User Events feature. Table 199


System release





FDD-LTE 15A

FL15A

FL15A

FL15A

-


OMS

UE

NetAct

MME

SAE GW

-

-

-

NetAct 15.5

-

-

Additional hardware requirements No new or additional hardware is required. Functional description The LTE1225: Parameter Level Logging of BTS User Events feature adds parameterlevel information to the Remote User Event Management (RUEM) log for any change that was triggered with the BTS Site Manager or Transport Webpage. Logging changes done with the BTS Site Manager Every change that is done with the BTS Site Manager that modifies eNB's configuration or affects any service is saved in the RUEM log, together with the parameter-level details of the request and a corresponding response. Parameter details typically include: • • •

managed object (MO) parameter name new value of the parameter

Each entry in the RUEM log file also includes information about the system response (whether the request was successfully executed).

g

Note: Parameters with confidential information such as user passwords, certificate reference number, pre-shared keys, private key, bluetooth pairing secrets/site specific secret/relationship/pins/passkeys are masked before they are saved in the RUEM log files. Logging changes done with the Transport Webpage

Issue: 01D

DN09185982

345



Changes done via the Transport Webpage that affect the eNB's service or trigger a configuration change are also logged together with parameter-level details. In this feature, local and remote IP traffic capturing requests issued via Transport WebPage is logged with parameter-level details. Overview of parameters' logging is shown in the figure below. Figure 39

Logging of parameters using Audit Trail

AuditTrail

CentralLog Repository

Name1,Value1 Name2,Value2

Name1,Value1 Name2,Value2

BTS SiteManager Name1,Value1 Name2,Value2 parameters

eNB

LocalLog Repository

WebBrowser

System impact Interdependencies between features The LTE1225: Parameter Level Logging of BTS User Events feature requires the LTE667: User Event Log Management feature to be enabled. Impact on interfaces There is no impact on interfaces. Impact on network management tools There is no impact on network management tools. Impact on system performance and capacity There is no impact on system performance or capacity. Management data Alarms No alarms are related to this feature. Measurements and counters

346

DN09185982

Issue: 01D



No measurements or counters are related to this feature. Key performance indicators No key performance indicators are related to this feature. Parameters No parameters are related to this feature. Sales information Table 200: Sales information lists sales information related to the LTE1225: Parameter Level Logging of BTS User Events feature. Table 200

Sales information

BSW/ASW


BSW

-


5.8 LTE1227: Flexi Multiradio BTS SW Download for Antenna Line Devices 5.8.1 LTE1227: Flexi Multiradio BTS SW Download for Antenna Line Devices Introduction to the feature The LTE1227: Flexi Multiradio BTS SW Download for Antenna Line Devices feature introduces software download capability for antenna line devices (ALDs), like masthead amplifiers and remote electrical tilt actuators via the standard base transceiver station (BTS) software (SW) management from NetAct and BTS site manager (BTSSM). Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • • •

minimizes service interruption eliminates site visits in case of ALD software upgrade eliminates tower crew visits in case of ALD software upgrade


Issue: 01D

DN09185982

347


Table 201




-




OMS -

-

UE -


NetAct -


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview The antenna line devices (ALDs) require periodic software updates since new features and bug fixes are provided by ALD vendors. Without the LTE1227: Flexi Multiradio BTS SW Download for Antenna Line Devices feature, the ALD software update requires both an ALD service interruption (to facilitate communication with the ALD hardware) and a site visit. A tower crew might be required depending on how the ALD equipment is installed at the site. The LTE1227: Flexi Multiradio BTS SW Download for Antenna Line Devices feature introduces the capability for an operator to remotely (from a Nokia management station) update the ALD software on either of the following management stations: • •

NetAct software manager application BTSSM application

The ALD software update requires that the ALD software is packaged according to Nokia software packaging standards. An ALD software update-specific build descriptor is created, which classifies the software elements in a software package. The operator is responsible for obtaining the ALD software image associated with the ALD hardware that is installed at each site. The operator is also responsible for packaging the ALD software image with an appropriate build descriptor. To help the operator in doing this, the LTE1227: Flexi Multiradio BTS SW Download for Antenna Line Devices feature provides a BTSSM application that assists the operator in creating an appropriate ALD software update-specific build descriptor. The operator zips this build descriptor with the ALD software image to create an ALD software package that is ready for staging and distribution. When the ALD software is properly packaged, the operator stages the ALD software either on NetAct or BTSSM. This is achieved by using the existing software staging mechanisms that are available on NetAct and BTSSM. The LTE1227: Flexi Multiradio BTS SW Download for Antenna Line Devices feature does not change the existing software staging interface. The operator starts the ALD software update procedure when the staging is done. The ALD software update procedure is achieved by using the existing software download and activation interfaces that are provided by NetAct and BTSSM. The LTE1227: Flexi Multiradio BTS SW Download for Antenna Line Devices feature does not change the existing software management user interfaces, nor the software management interfaces between the management stations and the evolved Node B (eNB).

348

DN09185982

Issue: 01D



The ALD software update occurs only when both download and activation are specified by the operator. The download and activation of ALD software occur only when the operator initiates the download with automatic activation operation at one of the management stations. If the operator invokes the "download only" option of the software update, it has no effect on the ALD. The eNB simply indicates that the download is successful without performing any software update on the ALD. When the software download with automatic activation operation is initiated, the eNB downloads the ALD software package from the management station that is recognized based on the build descriptor. The software download with automatic activation operation indicates that an ALD software update is being requested. The ALD software image is downloaded and activated to each affected ALD device. After the ALD software image is activated to each affected ALD device, the downloaded ALD software package is removed from the eNB. Finally, the eNB informs the operator if the ALD software update operation is successful or not. When the ALD software update operation is successful, the ALD's site configuration file (SCF) data is updated with the new software version in each successfully updated ALD.

g g

Note: All the ALD instances of a given type or vendor, as specified in the ALD-specific build descriptor, are updated via this procedure. It is not possible to update selected instances of ALDs. Note: The ALD resets autonomously after the new software is downloaded. 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 The impact of the LTE1227: Flexi Multiradio BTS SW Download for Antenna Line Devices feature on RAN-level system performance and capacity is minimal because the ALD software update is performed typically during a maintenance window. Management data BTS faults and reported alarms Table 202: New BTS faults lists the BTS faults introduced with this feature. Table 202

New BTS faults

Fault ID

Fault name


4047

Issue: 01D

Antenna line device SW download failure

DN09185982

7652

Alarm name BASE STATION NOTIFICATION (external ALD;

349


Table 202


New BTS faults (Cont.)

Fault ID

Fault name


Alarm name uncommissioned source)

4048

7655

CELL NOTIFICATION (Otherwise)

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 203

Sales information

BSW/ASW


ASW

-


5.9 LTE1408: Remote Syslog for Continuous Log Storage 5.9.1 Description of LTE1408: Remote Syslog for Continuous Log Storage Introduction to the feature The LTE1408: Remote Syslog for Continuous Log Storage feature enables the operator to continuously push system logs (Syslogs) in real time from a BTS to a remote syslog server. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The feature allows an increased number of BTS syslog messages to be logged regardless of the constraint of the local syslog file-size. This reduces: • •

error correction times service effort from the operator and Nokia

Requirements

350

DN09185982

Issue: 01D



Hardware and software requirements Table 204 System release FL15A


LBTS7.0


g


iOMS -

FL16

UE -


FL16

NetAct -


MME -

SAE GW -

Note: This feature is only applicable to the FSMr3 BTS and the Flexi Zone Micro. Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview Collecting syslog data in local log files by the BTS allows identifying software and hardware issues and any other unidentified misbehavior of the BTS. The syslog data is analyzed by Nokia Technical Support experts. Due to a limited size of such log files, data may get overwritten and therefore is unavailable to Technical Support for fault diagnosis. In order to avoid such situations, the LTE1408: Remote Syslog for Continuous Log Storage feature provides a remote continuous syslog storage solution. This enables to continuously push syslogs in real time from the BTS to the remote syslog server and overcome the disadvantages of locally stored log files. Syslog IP packets are transmitted with a BTS M-plane IP address as a source IP address and with a remote syslog server IP address (configured during commissioning) as a destination IP address.

g

Note: In order to ensure the usability of LTE1408, it is necessary to increase the Mplane link capacity as the average throughput of remote syslog data is 10 Mbps (with 25 Mbps of peak values). Syslog server The remote syslog server is a platform owned by the operator. In emergency situations, when a maximum of five BTSs need diagnosis, the iOMS can serve as the remote syslog server. Some operators may already have a remote syslog server in their networks as this feature is already supported by many switches and routers (for example Cisco). An iOMS allows storing at least 50 GB of remote syslog data. Such capacity is enough to store from about 1 to 2 hours of syslog data from five BTSs. Increasing the maximum accepted number of TLS connections or configuring more UDP syslog clients will decrease the feature's usability and may cause some stability issues in iOMS.

g

Note: In case of an iOMS switchover, the syslog server address (iOMS IP address) has to be changed manually during commissioning so that the BTS can send the syslogs to the new serving iOMS. Syslog format

Issue: 01D

DN09185982

351



The syslog protocol format is by default RFC 5424; hence, the syslog server has to be compliant with RFC 5424. It is also possible to choose a Nokia proprietary format for the remote syslog transmission, but this proprietary format requires a dedicated Nokia application (Rsyslog for Linux or pyRemoteLogServer or Rsyslog + Rsyslog Windows Agent for Windows) to be available on the remote server to accept such syslogs from the BTS. Syslog transmision Either the User Datagram Protocol (UDP) or Transport Layer Security Protocol (TLS) can be used as the remote syslog transport layer protocol. Transport Layer Security Protocol While establishing the TLS, both iOMS and BTS need certificates in order to authenticate each other. Certificate generation is the operator’s responsibility. Certificates can be signed by a Customer certificate authority (CA). Customer CA shall be also used to sign the TLS certificates on the operator’s remote syslog server. It is recommended to use the TLS protocol when a reliable connection with no data loss is essential.

g

Note: When the TLS protocol is configured for a remote syslog, the TLS connection will not automatically reconnect after a recovery of an Ethernet link outage. When the TLS protocol is configured for a remote syslog, the TLS remote syslog connection between a BTS and syslog server should start only after a server is up and running. User Datagram Protocol In a UDP configuration, the UDP does not re-send data in case of packet losses. When no reserved bandwidth is available for syslog traffic, it is recommended to use a higher DSCP value to avoid a loss of packets. Alternatively, the syslogs can be sent securely to the remote syslog server, using a UDP in an IPsec tunnel. If network security is not a concern, a UDP without any kind of encryption (that is, no IPsec) may be used. It is recommended to use the UDP protocol in a situation where an Ethernet link is not stable and a minor data loss is permissible.

g

Note: It is recommended to configure the M-plane traffic with a higher priority as compared to the tracing and syslog traffic. Tracing and syslog may generate a significant traffic volume in the uplink, which could otherwise negatively affect more important O&M operations. Supported file transfer protocols (configurable by the operator) for syslog traffic (see also Table 3): • •

352

UDP/IP TLS/TCP/IP (iOMS and BTS authenticate each other with certificates during the establishment of a TLS connection for a remote syslog transfer)

DN09185982

Issue: 01D


Table 205


Supported combinations of file transfer protocols and syslog formats

Syslog server

Supported Syslog format

Supported transport protocol

Operator Syslog server (Windows or Linux)

RFC5424

Nokia application

Proprietary

UDP/IP

iOMS

RFC5424

UDP/IP

UDP/IP TLS/TCP/IP

TLS/TCP/IP

System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces This feature adds the following new, external interface between a BTS and iOMS: •

syslogs are transmitted from BTS(s) to iOMS through UDP or TLS

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 Table 4: New parameters lists the parameters introduced with this feature. Table 206


Issue: 01D

Abbreviated name

Managed object

Troubleshooting common administration identifier

trblCAdmId

TRBLCADM

Remote syslog configuration

remoteSyslogConfig

TRBLCADM

DN09185982

353


Table 206


New parameters (Cont.) Full name

Abbreviated name

Managed object

Remote syslog server IP address

remoteSyslogServerIPaddress

TRBLCADM

Remote syslog server IP port number

remoteSyslogServerPortNo

TRBLCADM

Remote syslog transport protocol

remoteSyslogTransportProtocol

TRBLCADM

Remote syslog format

remoteSyslogFormat

TRBLCADM

Remote syslog DSCP

remoteSyslogDSCP

TRBLCADM

Remote syslog transmit duration

remoteSyslogTransmitDuration

TRBLCADM

Activate Remote syslog transmission

actRemoteSyslogTransmission

TRBLCADM

Remote syslog transmission status

remoteSyslogTransmissionStatus

TRBLCADM

Sales information Table: Sales information presents sales information about this feature. Table 207

LTE1408: Sales information

BSW/ASW


BSW

-


5.9.2 Activating and configuring LTE1408: Remote Syslog for Continuous Log Storage Before you start The remote syslog client in the BTS is disabled by default and may be enabled through BTS Site Manager or via NetAct 8.0 or newer. It is started without a BTS reset and has no impact on the end-user experience. The remote syslog server running in iOMS is enabled by default. The default supported protocol is TLS on port 6514. Table 208

Parameters used for activating and configuring LTE1408: Remote Syslog for Continuous Log Storage Parameter

Purpose

Remote syslog server IP mandatory address (remoteSyslogServerIPaddr ess)

no

Remote syslog server IP mandatory port number(remoteSyslogServer PortNo)

no

mandatory

no

Remote syslog transport protocol

354


DN09185982

Issue: 01D


Table 208


Parameters used for activating and configuring LTE1408: Remote Syslog for Continuous Log Storage (Cont.) Parameter

Purpose


(remoteSyslogTransportPro tocol)

Remote syslog mandatory format(remoteSyslogFormat )

no

mandatory

no

Remote syslog transmit mandatory duration (remoteSyslogTransmitDura tion)

no

Activate Remote syslog mandatory transmission (actRemoteSyslogTransmiss ion)

no

Remote syslog DSCP(remoteSyslogDSCP)



2

Activate the LTE1408: Remote Syslog for Continuous Log Storagefeature a) b) c) d) e) f)

Go to the Radio Network Configuration page. Expand the MRBTS object. If not present, create the TRBLCADM object. Right-click the TRBLCADM object. Create the Remote syslog configuration object. Set all the parameters in Remote syslog configuration: • • • • • •

Remote syslog DSCP=0 for Best Effort traffic marking or DSCP=8 for FZM Remote syslog format: standard (RFC5424) or proprietary (Nokia) Remote syslog server IP address (iOMS or operator’s server) Remote syslog server port number: 6514 for TLS or 514 for UDP Remote syslog transmit duration; it may be reconfigured later on at any time Remote syslog transport protocol: UDP or TCP

g) Set the Activate remote syslog transmission parameter value to true.

Issue: 01D

DN09185982

355



h) Send the parameters to the BTS according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. The feature can also be also activated from NetAct 8.0 EP1 or newer by configuring the same objects and parameters via CM Editor and sending such a prepared plan via CM Operation Manager.

Expected outcome The LTE1408: Remote Syslog for Continuous Log Storage feature has been activated.

5.9.3 Deactivating LTE1408: Remote Syslog for Continuous Log Storage Procedure To deactivate the feature, do the following: 1


2

Deactivate the LTE1408: Remote Syslog for Continuous Log Storage feature. a) b) c) d)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the TRBLCADM properties. Set the Activate remote syslog transmission parameter value to false.

Expected outcome The LTE1408: Remote Syslog for Continuous Log Storage feature has been deactivated.

5.10 LTE1434: Flexi Multiradio BTS Antenna Rx RFsniffing 5.10.1 Description of LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing Introduction to the feature

356

DN09185982

Issue: 01D



The LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing feature enables a Flexi Multiradio BTS to monitor the spectrum in order to detect radio frequency interference (RFI) and radio disturbance in the peripheral radio frequency (RF) path. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides a toolset which enables testing the BTS for RFI remotely, which reduces the customer's reliance on expensive drive tests. It contributes positively to lowering OPEX. Requirements Hardware and software requirements Table 209: Hardware and software requirements presents hardware and software requirements. Table 209




FL15A



FL15A

OMS -

UE -


-

NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements This feature is supported in the RF modules according to the following list: FHCB, FHCD, FHDA, FHDB, FHEA, FHEB, FHEC, FHEF, FHEG, FHGB,, FRGS, FRGT, FRHD, FRHE, FRIG, FXCA, FXCB, FXCC, FXCE, FXDA, FXDB, FXEA, FXEB, FXFA, FXFB, FXFC, FXJB. Additional software requirements This feature, in addition to BTS Site Manager software, requires installation of free Matlab Compiler Runtime (MCR) for release R2015a (can be downloaded from http://www.mathworks.com/products/compiler/mcr/). Functional description The LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing feature enables the operator to perform an RF scan (also known as RFI snapshot or RF-intercept) and passive intermodulation (PIM) tests via the BTS Site Manager (BTSSM). This feature introduces new tests, including the RF-scan and PIM. On-line tests can be run without putting the BTS in a test mode. Off-line tests do require putting the BTS in a test mode and are service impacting. The data collected by the BTS will automatically be uploaded to the BTS Site Manager. An RF-scan and PIM data viewing application is integrated into the BTS Site Manager to provide visualization of the captured data.

Issue: 01D

DN09185982

357



The on-line tests are: 1. RF scan - collects a snapshot of the RF data received from the base station antenna in uplink. The received RF data can be depicted for the user in the form of frequency spectrum and spectrogram. 2. PIM simulation - it does not require putting the base station into a test mode since the tests involve calculations of potential interference based on the BTS's radio configuration and not actual measurements. The goal of this test is to familiarize the operator with PIM tests. The off-line test is PIM desensitization - the goal of the desensitization test is to verify if the cell configuration is causing uplink (UL) desensitization. RFI is a common hazard for network operators. The RF-scan test provided with this feature allows the operator to remotely retrieve a sample of RF data for an RFI analysis. RFI issues are difficult to diagnose. Detecting RFI typically requires a: • •

BTSSM basic site - visit - a portable spectrum analyzer is typically connected to the antenna, and the band is scanned for interferers drive test - a vehicle equipped with an antenna and a spectrum analyzer is used to drive and scan the band

Site visits and drive tests require: many hours or even days to be performed, human involvement (they cannot be automated), professional experts (technicians or engineers), and additional costs included. RF scan RF scan captures the current signal within the cell receive band. This data can be analyzed for anomalous and peculiar waveforms and radio frequency interference. This interference could be caused by environmental conditions, other high frequency transmitters, or the BTS itself (for example PIM). RF scan collects a snapshot of RF data from the Rx channel. PIM PIM is a special type of RFI, occuring in multi-carrier sites when two or more high power signals encounter non-linear junctions or materials in the RF path produce resonant frequencies (IM values). Resonant frequencies appearing in the receive band increase the floor noise and may degrade a site's capacity. PIM is a hazard for BTSs in a multi-carrier configuration where two or more carrier signals share a single antenna. PIM distortion refers to spurious signals generated when multiple high power frequencies are passed through "passive" components (connectors, cables, antenna). In a multi-carrier BTS, these spurious signals are almost guaranteed to occur; however, they are only a problem when they appear in the Rx band. The PIM tests (PIM desensitization and PIM simulation) give the operator the ability to test a BTS for PIM remotely.

g

Note: Thanks to this feature, the RF-scan and PIM test results data can be analyzed and visualized locally within the BTSSM. RF-scan results are stored in the hierarchical data format.The operator will be able to store the data files with test results for later processing and viewing. User scenarios for RF interference There are three user scenarios for when RF interference testing could be executed:

358

DN09185982

Issue: 01D



1. post installation sanity check - RF scan and PIM tests are triggered manually by an operator typically after installation/commissioning of a new site in order to ensure that there is no internal and external interference. 2. investigation of UL performance degradation - RF scan and PIM tests are triggered manually in cases where UL performance is degraded or degrading slowly over time, measured via ongoing performance measurements. In this case the operator may trigger an RF scan for a certain cell/sector if certain UL-related key performance indicators (KPI) are worse or worsening over time. Internal or external interference can be deduced from the collected data. 3. remote analysis of RF scan and PIM data - RF scan and PIM tests data are collected manually by an operator and exported outside of the BTS Site Manager for a remote analysis. 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 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 Table 210: New parameters presents parameters introduced with this feature. Table 210


Abbreviated name

Managed object

Activate PIM testing

actPimTesting

BTSSCL

Activate RFI testing

actRfiTesting

BTSSCL

Sales information

Issue: 01D

DN09185982

359



Table 211: Sales information presents sales information about this feature. Table 211


ASW



5.10.2 Activating and configuring LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing Before you start Table 212: Parameters used for activating and configuring LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing presents parameters used for activating and configuring the feature. Table 212

Parameters used for activating and configuring LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing Parameter

Purpose


Activate PIM testing (actPimTesting)

activation flag

no

Activate RFI testing (actRfiTesting)

activation flag

no



2

Activate the LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing feature. a) Go to the Commisioning ► BTS Settings page. b) Check the Activate PIM testing (actPimTesting) radio module parameter. c) Check the Activate RFI testing (actRfiTesting) radio module parameter.

3

Configure the cell resources. (optional) a) Go to the Cell Resources page. b) Set the appropriate values of the parameters in the Antennas section.

360

DN09185982

Issue: 01D


4


Configure antenna line settings. (optional) a) Go to the Antenna Line Settings page. b) If required, for any antenna set the RTT delay parameter value.

5


Expected outcome The LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing feature is activated.

5.10.3 Deactivating LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing Before you start The Activate PIM testing (actPimTesting) and Activate RFI testing (actRfiTesting) parameters are used for deactivation. Modification of these parameters does not require an eNB restart. To deactivate the feature, do the following: Procedure 1


2

Deactivate the LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing feature. a) Go to the Commisioning ► BTS Settings page. b) Uncheck the Activate PIM testing (actPimTesting) radio module parameter. c) Uncheck the Activate PIM testing (actPimTesting) radio module parameter.

3


Expected outcome The LTE1434: Flexi Multiradio BTS Antenna Rx RF-sniffing feature is deactivated.

Issue: 01D

DN09185982

361



5.10.4 Performing RF monitoring Follow this procedure to perform activities related to the RF monitoring. Procedure 1

Activate the RFI and PIM testing Go to the Commisioning ► BTS Setting page and check the Activate RFI testing and Activate PIM testing options. Step example Figure 40

2

Activating RF monitoring

Switch to the RF Monitoring tab On the left side of the BTS SM choose RF Monitoring.

g

Note: RF monitoring funcionality requires installed MATLAB Compiler Runtime (MCR) for release R2015a.

3

Choose activity you want to perform. Sub-steps a) Go to the TEST tab to execute PIM desensitizaion or RF scan

b) Go to the FILES tab to visualize test reports c) Go to the SIMULATION tab to perform PIM simulation

4

Optional: Execute RF scan a) Go to the Test tab and choose RF scan. b) Select folder where test results will be saved. c) Choose antena to be scanned and capture type.

362

DN09185982

Issue: 01D



d) Click START. Step example Figure 41

5

g

g

Optional: Execute PIM desensitization test Note: This procedure requires the BTS to be in test mode. To set it, in the upper part of BTS SM click Tests ► Enter BTS test state. Shared radios can be tested on the master or slave side. The peer cell running on the shared radio needs to be manually locked by the operator before putting the BTS in test mode. The same is true when there is antenna sharing (no user traffic can be present on the radio and antenna during test). Note: Before running test mode in BTS that is connected to other peer-RAT radio or antenna that shares cells with it, it is recommended to lock peer side cells to avoid traffic disturbances. a) b) c) d) e)

Issue: 01D

Executing RF scan

Go to the Test tab and choose PIM desensitization. Select folder where test results will be saved. Choose antena to be tested. Choose downlink carriers used in the test. Click START.

DN09185982

363



5.11 LTE1749: Mobility Robustness Monitoring Inter RAT 5.11.1 Description of LTE1749: Mobility Robustness Monitoring Inter RAT Introduction to the feature The LTE1749: Mobility Robustness Monitoring Inter RAT feature introduces UTRAN MRO counters which allow monitoring of too early and too late handover (HO) occurrences. The focus of this feature is the interworking between LTE and UTRAN.

g

Note: In release LTE15A new counters are introduced to evaluate the handover performance. In release LTE16A the full MRO implementation in iSON manager will be realized with feature LTE2539: MRO InterRat UTRAN. Benefits End-user benefits No effect on the end-user experience. Operator benefits The LTE1749: Mobility Robustness Monitoring Inter RAT feature provides counters for mobility and mobility failures to UTRAN. Requirements Table 213 System release FDD-LTE 15A Flexi Zone Controller -



FL15A

FL15A

OMS LTE OMS15A

UE -



FL15A

-

NetAct

MME

NetAct15.5

-

SAE GW -

Additional hardware requirements No new or additional hardware is required Functional description Functional overview The following InterRat handover failure use cases are monitored between LTE and UTRAN: • •

364

Too Late inter-RAT HO from LTE to 3G Too Early inter-RAT HO with an HO failure from LTE to 3G

DN09185982

Issue: 01D



Main purpose of this functionality is to minimize the negative effects caused by the handover threshold not being optimally set, which results in handover failures or radio link failures. Mobility robustness optimization (MRO) Inter-RAT is based on PM counter statistics per eNB-cell and the UTRAN-target frequency layer, resulting in a long-term adaptation. Daily statistics are the basis for the evaluation of the handover performance. The PM counters are aggregated on an LTE cell for each target frequency layer. Feature Description The LTE1749: Mobility Robustness Monitoring Inter RAT feature supports both WCDMA and TD-SCDMA UTRAN networks. The feature is supported on the Flexi Macro and Flexi Zone Micro, and it is licensed on the eNB. PM counters collected by the eNB The LTE1749: Mobility Robustness Monitoring Inter RAT feature introduces a set of PM counters collected by the eNB. Table 214: New counters lists the measurements introduced with this feature. User scenarios The following user scenarios are described: User scenario 1: Activating the LTE1749: Mobility Robustness Monitoring Inter RAT feature on the eNB User scenario 2: Too Late HO when UE returns to the eNB where it had experienced RLF User scenario 3: Too Early HO when UE returns to the eNB where it had experienced handover failure User scenario 1: Activating the LTE1749: Mobility Robustness Monitoring Inter RAT feature on the eNB Pre-conditions The LTE56: Inter-RAT Handover to WCDMA or LTE898: TDD Inter-RAT Handover to TDSCDMA feature is activated on the eNB. Description The operator activates the LTE1749: Mobility Robustness Monitoring Inter RAT feature by configuring related parameters in the plan file: • •

setting a corresponding eNB level O&M activation flag to “true” and configuring feature specific parameters as necessary.

The operator downloads the plan file to the eNB. Post-conditions LTE1749: Mobility Robustness Monitoring Inter RAT is activated on the eNB.

Issue: 01D

DN09185982

365



User scenario 2: Too Late HO when UE returns to the eNB where it had experienced RLF Pre-condition • • • • • •

MRO Inter-RAT UTRAN is activated. UTRAN neighbor topology is configured (either WCDMA or TD-SCDMA). The UE supports the radio link failure report for the inter-RAT MRO. The UE is connected to an LTE cell on the eNB. B1 (for CSFB or Load Balancing) or B2 (for PSHO or VoLTE) is activated at the UE. UEs which are compliant to 3GPP Release 11 or higher

Description •

•

g

The UE encounters RLF on the LTE cell and selects a UTRAN cell to which it connects. The measurement for the selected UTRAN cell at the time of the RLF does not meet one or more of the configured B2 (for PSHO or VoLTE) thresholds. After a period of time (up to 48 hours), the UE connects or hands in to any cell on the original eNB where it had experienced RLF and indicates to the eNB that it has RLF information available. Note: The eNB where the UE finally connects to can be different from the original one where the RLF occurs. In this case, the RLF-report retrieved from the UE will be forwarded by the last accessed eNB to the original eNB via the X2 interface (if present).

• • •

The eNB retrieves the RLF-report information using the RRC-UE-Informationprocedure. Based on the information in the RLF-report, the eNB determines that it contains the cell where the UE had experienced RLF. Based on the information in the RLF-report, the eNB determines that the conditions for Too Late HO to UTRAN - {B2T2-PSHO, B2T2-VoLTE} Not Met are achieved, and it increments the appropriate counters associated with the RLF cell and the UTRAN frequency which had been selected after the RLF occurred.

Post-condition The appropriate Too Late PM counters are incremented and the original procedure (connection setup or hand-in) is completed. User scenario 3: Too Early HO when UE returns to the eNB where it had experienced handover failure Pre-condition • • • • •

MRO Inter-RAT UTRAN is activated. UTRAN neighbor topology is configured (either WCDMA or TD-SCDMA). The UE supports the radio link failure report for the inter-RAT MRO. The UE is connected to an LTE cell on the eNB. B1 (for CSFB or Load Balancing) or B2 (for PSHO or VoLTE) is activated at the UE.

Description

366

DN09185982

Issue: 01D


• •

•

•


The UE meets the B1 (for CSFB or Load Balancing) or B2 (for PSHO or VoLTE) measurement reporting conditions and sends the measurement report to the eNB. The UE encounters handover failure and re-establishes back to any cell on the same eNB on which it had experienced the failure (reestablishmentCause will be “handoverFailure” in this case). The eNB determines that it contains the cell where the UE was last connected (identified by the physCellId from the RRCConnectionReestablishmentRequest), and looks up an UE context (using the existing mechanism to find the UE context). An UE context exists which indicates handover to UTRAN is in progress. Based on information contained in the UE context, the eNB determines that the conditions for “Too Early HO to UTRAN - {B2T2-PSHO, B2T2-VoLTE} Met” are met, and it increments the appropriate counters associated with the source cell and the UTRAN frequency to which handover had been attempted.

Post-condition The appropriate Too Early PM counters are incremented and the original reestablishment procedure completes as per existing functionality. System impact Interdependencies between features The following features influence LTE1749: Mobility Robustness Monitoring Inter RAT: •

•

•

•

•

•

LTE533: MRO LTE1749: Mobility Robustness Monitoring Inter RAT exploits the functionality introduced by LTE533: MRO LTE56: Inter-RAT Handover to WCDMA LTE1749: Mobility Robustness Monitoring Inter RAT can be used when LTE56: InterRAT Handover to WCDMA is enabled. The new feature increments PM counters in LTE56-scenarios. LTE898: TDD Inter-RAT Handover to TD-SCDMA This feature has to be enabled. LTE1749: Mobility Robustness Monitoring Inter RAT increments PM-counters in LTE898. LTE736: CS Fallback to UTRAN Too Late- and Too Early-counters are incremented based on failures triggered by this feature. LTE1357: LTE-UTRAN Load Balancing Too Late and Too Early PM counters are incremented based on the failures triggered by this feature. LTE1049: MDT – UE Measurement Logs The usage of RRC-UE-Information procedure by both features is coordinated.

Impact on RAN system NE external interfaces • • • •

RRC (TS 36.331) RLF Report support RRConnectionSetupComplete, RRCConnectionReconfigurationComplete, UEInformation Request/Response X2AP (TS 36.423) SoC X2AP RLF indication

Impact on network management tools

Issue: 01D

DN09185982

367



No impact on network management tools. Impact on system performance and capacity No impact on system performance or capacity. Management data Alarms No alarms related to this feature. Measurements and counters Table 214: New counters lists measurements introduced with this feature. Table 214

New counters

Counter ID

Counter name

Measurement

M8013C62

Successfully established UE Contexts (for Release 11+ UEs)

8013 - LTE UE State (WBTS)

M8032C0

Late Handover to UTRAN (threshold B2T2-PSHO not met) per UTRAN frequency

8032 - LTE MRO UTRAN frequency related (WBTS)

M8032C1

Late Handover to UTRAN (threshold B2T2-VoLTE not met) per UTRAN frequency


M8032C3

Early Handover to UTRAN (threshold B2T2-PSHO met) per UTRAN frequency


M8032C4

Early Handover to UTRAN (threshold B2T2-VoLTE met) per UTRAN frequency


M8032C6

Inter System Handover 8032 - LTE MRO UTRAN attempts to UTRAN (Event B2- frequency related (WBTS) PSHO Met) per UTRAN frequency

M8032C7

Inter System Handover 8032 - LTE MRO UTRAN attempts to UTRAN (Event B2- frequency related (WBTS) VoLTE Met) per UTRAN frequency

Key performance indicators No key performance indicators related to this feature. Parameters Table 215: New parameters lists parameters introduced with the LTE1749: Mobility Robustness Monitoring Inter RAT feature.

368

DN09185982

Issue: 01D


Table 215



Abbreviated name

Managed object

Activate MRO inter-RAT UTRAN

actMroInterRatUtran

LNBTS

Time connection failure threshold

timeConnFailureThreshold

LNBTS

LTE MRO UTRAN frequency related

mtMroUtranFrequency

PMRNL

Sales information Table 216: Sales information presents the sales information for the LTE1749: Mobility Robustness Monitoring Inter RAT feature. Table 216

Sales information

BSW/ASW ASW



5.11.2 Activating and configuring Mobility Robustness Monitoring Inter RAT Before you start The eNB is in service. Table 217

Parameters used for activating and configuring Mobility Robustness Monitoring Inter RAT Parameter

Purpose


actMroInterRatUtran

Setting corresponding eNB level O&M activation flag to “true”

-

timeConnFailureThreshold:timeCo nnFailureThreshold

If actMroInterRatUtran is set to true, timeConnFailureThres hold must be configured.

The Activate MRO inter-RAT UTRAN (actMroInterRatUtran) parameter is used for activation. Modification of this parameter requires neither an eNB restart nor cell locking. The timeConnFailureThreshold:timeConnFailureThreshold (LNBTS) parameter must be configured if the actMroInterRatUtran parameter is set to true. The following features need to be activated/configured before the activation of the LTE1749: Mobility Robustness Monitoring Inter RAT feature: •

Issue: 01D

The LTE56: Inter-RAT Handover to WCDMA feature must be activated before this procedure.

DN09185982

369



Procedure 1


2

Activate the LTE1749: Mobility Robustness Monitoring Inter RAT feature. a) b) c) d)

3

Go to the Radio Network Configuration page. Select the MRBTS object. Expand the LNBTS object. Set the Activate MRO inter-RAT UTRAN (actMroInterRatUtran) parameter's value to true.

Configure the Time connection failure threshold parameter. a) Select the LNBTS object. b) Set the Time connection failure threshold (timeConnFailureThreshold) parameter's value to 2000.

4


Expected outcome The LTE1749: Mobility Robustness Monitoring Inter RAT feature is activated in the BTS.

5.11.3 Deactivating LTE1749: Mobility Robustness Monitoring Inter RAT Before you start The Activate MRO inter-RAT UTRAN (actMroInterRatUtran) parameter is used for deactivation. Modification of this parameter requires neither an eNB restart nor cell locking. Procedure 1


370

DN09185982

Issue: 01D


2

Deactivate the LTE1749: Mobility Robustness Monitoring Inter RAT feature. a) b) c) d)

3


Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate MRO inter-RAT UTRAN (actMroInterRatUtran) parameter's value to false.


Expected outcome The LTE1749: Mobility Robustness Monitoring Inter RAT feature is deactivated in the BTS.

5.12 LTE1879: Additional PM Counters for Mobility Event Monitoring 5.12.1 Description of LTE1879: Additional PM Counters for Mobility Event Monitoring Introduction to the feature The LTE1879: Additional PM Counters for Mobility Event Monitoring introduces additional performance measurements for monitoring the mobility of subscribers. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature introduces new performance measurements to allow monitoring mobility events of subscribers and finally optimizing mobility-related parameters. Requirements Hardware and software requirements Table 218: Hardware and software requirements presents the hardware and software requirements for this feature. Table 218



Issue: 01D



DN09185982



371




OMS -

UE -

NetAct -

MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description The LTE1879: Additional PM Couters for Mobility Event Monitoring feature enhances a user equipment's (UE's) mobility analysis mechanism in addition to the already existing handover (HO) counters. Within the feature's scope, nine new counters will be created to monitor A2 and/or A1 event(s). The counters are pegged when the eNB receives the RRC measurement report with an A2/A1 event, which indicates that the configured reference signal received power (RSRP) or reference signal received quality (RSRQ) threshold was met and a corresponding event was triggered and sent by the UE. Reported by the UE A2/A1 events with RSRP/RSRQ values are mapped to the nearest upper or nearest lower thresholds. Those thresholds use settings of currently activated in the eNB mobility features which trigger A2/A1 events. UE capabilities, technology for which given measurement was activated and if UE has the QCI1 established or not is less essential than the value of the reported RSRP/RSRQ.

g g

Note: See Measurements and counters for the list of the implemented counters. Note: See Reference/Counters for a full information on measurements and counters. This excel report shows the full set of measurement and counter attributes including the change information. System impact Interdependencies between features The following features are related to the LTE1879: Additional PM Couters for Mobility Event Monitoring: •

•

•

•

•

372

LTE55: Inter-frequency Handover The number of A2 events received which crossed the inter-frequency threshold only applies when LTE55: Inter-frequency Handover is activated. LTE56: Inter-RAT Handover to WCDMA The number of A2 events received which crossed the WCDMA threshold only applies when LTE56: Inter-RAT Handover to WCDMA is activated. LTE1198: RSRQ Triggered Mobility The number of A2 events received which crossed the RSRQ mobility threshold and the number of A1 events triggered for RSRP only apply when LTE1198: RSRQ Triggered Mobility is activated. LTE64: Service-based Handover Thresholds The number of A2 events received which crossed the inter-frequency QCI1 threshold, the number of A2 events received which crossed the WCDMA QCI1 threshold, and the number of A1 events received which crossed the A1 QCI1 threshold only apply when LTE64: Service-based Handover Thresholds is activated. LTE2112: Dedicated Mobility Thresholds for SRVCC

DN09185982

Issue: 01D


•

•


The number of A2 events received which crossed the inter-frequency QCI1 threshold, the number of A2 events received which crossed the WCDMA QCI1 threshold, and the number of A1 events received which crossed the A1 QCI1 threshold only apply when LTE2112: Dedicated Mobility Thresholds for SRVCC is activated. LTE423: RRC Connection Release with Redirect The number of A2 events received which crossed the redirect RSRP threshold only applies when LTE423: RRC Connection Release with Redirect is activated. LTE1407: RSRQ-based Redirect The number of A2 events received which crossed the redirect RSRQ threshold only applies when LTE1407: RSRQ-based Redirect is activated.

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 is new measurement type, M8033-LTE, for mobilty events, introduced with this feature. The measurement contains counters which measure different events triggered by UE, sent in an RRC measurement report, and reported per cell. The counters are updated in the LTE cell. For MCC/MNC primary PLMN-id shall be used. Table 219: New counters lists counters introduced with this feature. Table 219

New counters

Counter ID

Issue: 01D

Counter name

Measurement

M8033C0

The number of A2 events received which crossed interfrequency threshold

8033 - LTE mobility events

M8033C1

The number of A2 events received which crossed interfrequency QCI1 threshold


M8033C2

The number of A2 events received which crossed WCDMA threshold


M8033C3

The number of A2 events received which crossed WCDMA QCI1 threshold


DN09185982

373


Table 219



Counter ID

Counter name

Measurement

M8033C4

The number of A2 events received which crossed RSRQ mobility threshold


M8033C5

The number of A2 events received which crossed redirect RSRP threshold


M8033C6

The number of A2 events received which crossed redirect RSRQ threshold


M8033C7

The number of A1 events triggered for RSRP


M8033C8

The number of A1 events received which crossed A1 QCI1 threshold


Key performance indicators There are no key performance indicators related to this feature. Parameters Table 220: New parameters presents parameters introduced with this feature. Table 220

New parameters

Full name LTE mobility events

Abbreviated name mtMobilityEvents

Managed object PMRNL

Structure -

Sales information Table 221: Sales information presents sales information about this feature. Table 221

Sales information

BSW/ASW


BSW

-


5.13 LTE1899: Dedicated PM Counters for E-RAB Management Failure Causes 5.13.1 Description of LTE1899: Dedicated PM Counters for E-RAB Management Failure Causes Introduction to the feature

374

DN09185982

Issue: 01D



The LTE1899: Dedicated PM Counters for E-RAB Management Failure Causes feature introduces new performance measurements for providing a detailed breakdown of possible failure causes for: • •

E-UTRAN radio access bearer (E-RAB) setup failure E-RAB release failure

Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature improves the quality of E-RAB performance montoring. Requirements Hardware and software requirements Table 222: Hardware and software requirements presents hardware and software requirements. Table 222 System release FDD-LTE 15A



FL15A


FL15A

OMS -

FL15A

UE -


FL16

NetAct -


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description The LTE1899: Dedicated PM Counters for E-RAB Management Failure Causes feature introduces additional performance measurements to support an improved monitoring of E-RAB accessibility and E-RAB retainability key performance indicators (KPIs). This will help to identify a potential resource bottleneck and quantify the impact on the accessibility and retainability KPIs and, thus improving them. The new performance management (PM) counters are embedded into the performance monitoring (PMO) structure for E-RAB monitoring, and some legacy counters are replaced.

g g

Note: See Measurements and couters for the list of the implemented counters. Note: See Reference/Counters for a full information on measurements and counters. This excel report shows the full set of measurement and counter attributes including the change information. System impact

Issue: 01D

DN09185982

375



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 Table 223: New counters presents counters introduced with this feature. Table 223

New counters

Counter ID

376

Counter name

Measurement

M8006C244

Failed setup attempts for initial E-RABs due to "radio network layer cause - radio resources not available"

8006 - LTE EPS bearer

M8006C245

Failed setup attempts for initial E-RABs due to "transport network layer cause -transport resources unavailable"


M8006C246

Failed setup attempts for initial E-RABs due to "radio network layer cause - radio connection with UE lost"


M8006C247

Failed setup attempts for initial E-RABs due to "radio network layer cause - failure in the radio interface procedure"


M8006C248

Failed setup attempts for additional E-RABs due to "radio network layer cause radio resources not available"


DN09185982

Issue: 01D


Table 223


Counter ID

Issue: 01D


Counter name

Measurement

M8006C249

Failed setup attempts for additional E-RABs due to "transport network layer cause - transport resources unavailable"


M8006C250

Failed setup attempts for additional E-RABs due to "radio network layer cause radio connection with UE lost"


M8006C251

Failed setup attempts for additional E-RABs due to "radio network layer cause failure in the radio interface procedure"


M8006C252

Failed setup attempts for additional E-RABs due to "miscellaneous cause - not enough user-plane processing resources"


M8006C253

Failed setup attempts for 8006 - LTE EPS bearer additional E-RABs due to mobility procedures such as handover, redirect, CS fallback

M8006C254

Total number of released ERABs initiated by the eNB


M8006C255

eNB initiated E-RAB releases due to user inactivity


M8006C256

eNB initiated E-RAB releases 8006 - LTE EPS bearer due to loss of connection to the UE

M8006C257

eNB initiated E-RAB releases due to insufficient transport resources


M8006C258

eNB initiated E-RAB releases due to redirect to another cell


M8006C259

eNB initiated E-RAB releases due to E-UTRAN generated reason


M8006C260

eNB initiated E-RAB releases 8006 - LTE EPS bearer due to missing radio resources

DN09185982

377


Table 223



Counter ID

378

Counter name

Measurement

M8006C261

E-RABs released due to partial 8006 - LTE EPS bearer handover regardless of the bearers QCI

M8006C262

E-RABs attempted to release due to outgoing handover regardless of the bearers QCI


M8006C263

E-RABs released due to successful outgoing handover regardless of the bearers QCI


M8006C264

E-RABs released due to failed handover regardless of the bearers QCI


M8006C265

Failed EPC initiated E-RAB releases


M8006C266

Total number of released QCI1 8006 - LTE EPS bearer E-RABs initiated by the eNB

M8006C267

eNB initiated QCI1 E-RAB releases due to user inactivity


M8006C268

eNB initiated QCI1 E-RAB releases due to loss of connection to the UE


M8006C269

eNB initiated QCI1 E-RAB releases due to insufficient transport resources


M8006C270

eNB initiated QCI1 E-RAB releases due to redirect to another cell


M8006C271

eNB initiated QCI1 E-RAB releases due to E-UTRAN generated reason


M8006C272

eNB initiated QCI1 E-RAB releases due to "radio network layer cause - radio resources not available"


M8006C273

QCI1 E-RABs released due to partial Handover


M8006C274

QCI1 E-RABs attempted to release due to outgoing handover


DN09185982

Issue: 01D


Table 223



Counter ID

Counter name

Measurement

M8006C275

QCI1 E-RABs released due to successful outgoing Handover


M8006C276

QCI1 E-RABs released due to failed handover



New key performance indicators

KPI ID

KPI name

LTE_5703a

E-UTRAN E-RAB drop ratio per cause due to E-UTRAN generated reason cause initiated by eNB

LTE_5704a

E-UTRAN E-RAB drop ratio due to failed handover cause initiated by eNB

LTE_5705a

E-UTRAN E-RAB drop ratio due to due to partial handover cause

LTE_5761a

E-UTRAN E-RAB setup failure ratio per cause : "radio network layer cause (RNL) - failure in the radio interface procedure"

LTE_5762a

E-UTRAN E-RAB setup failure ratio per cause "miscellaneous cause not enough user plane processing resources"

LTE_5763a

E-UTRAN E-RAB setup failure ratio per cause "due to mobility procedures like handover, redirect, CS fallback" cause

LTE_5765a

E-UTRAN E-RAB drop ratio per cause TNL unspecified

Table 225: Modified key performance indicators lists key performance indicators modified by this feature. Table 225

Modified key performance indicators

KPI ID

Issue: 01D

KPI name

LTE_5023e

E-UTRAN E-RAB normal release ratio user perspective

LTE_5024e

E-UTRAN E-RAB normal release ratio RAN view

LTE_5025e

E-UTRAN E-RAB drop ratio, RAN view

LTE_5086b

E-UTRAN E-RAB setup failure ratio per cause RNL

LTE_5087b

E-UTRAN E-RAB setup failure ratio per cause TRPORT

LTE_5088b

E-UTRAN E-RAB setup failure ratio per cause RESOUR

LTE_5089b

E-UTRAN E-RAB setup failure ratio per cause OTH

LTE_5090c

E-UTRAN E-RAB drop ratio per cause RNL

LTE_5091c

E-UTRAN E-RAB drop ratio per cause TNL

LTE_5092d

E-UTRAN E-RAB drop ratio due to other (OTH) cause initiated by eNB

LTE_5119d

E-UTRAN E-RAB drop ratio, user perspective

DN09185982

379


Table 225


Modified key performance indicators (Cont.)

KPI ID

KPI name

LTE_5209b

E-UTRAN E-RAB QCI1 normal release ratio user perspective

LTE_5237c

E-UTRAN E-RAB drop ratio per cause RNL EPC

LTE_5238c

E-UTRAN E-RAB drop ratio per cause OTH EPC

LTE_5570d

E-UTRAN E-RAB active drop ratio with data in the buffer due to RNL radio connection with UE lost

LTE_5571c

E-UTRAN E-RAB QCI1 with data in the queue drop ratio, RAN view, RNL failure with UE lost

LTE_5572b

E-UTRAN E-RAB QCI1 drop ratio, RAN view

LTE_5587c

E-UTRAN E-RAB release ratio due to radio resources not available

LTE_5812b

E-UTRAN E-RAB drops per PDCP SDU volume, user perspective

Parameters There are no parameters related to this feature. Sales information Table 226: Sales information presents sales information. Table 226

Sales information

BSW/ASW


BSW


5.14 LTE1912: RRC Establishment Monitoring Extensions 5.14.1 Description of LTE1912: RRC Establishment Monitoring Extensions Introduction to the feature The LTE1912: RRC Establishment Monitoring Extensions feature introduces additional performance measurements for failed connection establishments of the radio resource control (RRC). Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature improves the quality of RRC-related performance monitoring. Requirements

380

DN09185982

Issue: 01D



Hardware and software requirements Table 227: Hardware and software requirements presents the hardware and software requirements for this feature. Table 227 System release FDD-LTE 15A



FL15A


FL15A

OMS -

FL15A

UE -


FL16

NetAct -


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description The LTE1912: RRC Establishment Monitoring Extensions feature introduces additional performance measurements to support an improved monitoring of user equipment's (UE) accessibility key performance indicators (KPIs). This will help to identify potential resource bottleneck and to quantify the impact on the accessibility KPIs and, hence, to improve them.

g g

Note: See Measurements and counters for the list of the implemented counters. Note: See Reference/Counters for a full information on measurements and counters. This excel report shows the full set of measurement and counter attributes including the change information. 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.

Issue: 01D

DN09185982

381




New counters

Counter ID

Counter name

Measurement

M8013C65

Number of signaling connection establishment requests rejected due to control plane overload

8013 - LTE UE state

M8013C66

Number of signaling connection establishment requests rejected due to user plane overload

8013 - LTE UE state

M8013C67

Number of signaling connection establishment requests rejected due to lack of PUCCH resources

8013 - LTE UE state

M8013C68

Number of signaling connection establishment requests rejected due to threshold for the maximum number of RRC connections

8013 - LTE UE state

M8013C69

Number of signaling connection establishment requests rejected due to MME overload

8013 - LTE UE state



KPI ID

KPI name

LTE_5707a

E-UTRAN RRC connection setup failure ratio per cause: RRC connection setup rejection from eNB due to overload and lack of resources

Parameters There are no parameters related to this feature. Sales information Table 230: Sales information presents sales information. Table 230

Sales information

BSW/ASW BSW

382


DN09185982


Issue: 01D



5.15 LTE1949: Extend Power Reduction Range 5.15.1 Description of LTE1949: Extend Power Reduction Range Introduction to the feature The LTE1949: Extend Power Reduction Range feature extends the power reduction range of a cell. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits Currently, the cell power reduction is limited (for example, when the maximum cell power is set to 10 W, only 1.7 dB reduction is possible). This feature extends the power reduction range of a cell (for example, when the maximum cell power is set to 10 W, 10 dB reduction is possible). Requirements Hardware and software requirements Table 231



FL15A



FL15A

OMS -


UE -


-

NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview For a normal cell, the base transceiver station site manager (BTSSM) calculates the maximum value for the Cell power reduce (dlCellpwrRed) parameter. The Cell power reduce (dlCellpwrRed) parameter is dependent on HW capability.

g

Note: BTSSM checks that: 0 <= dlCellPwrRed + cellPwrRedForMBMS <= dlCellpwrRed maximum value. cellPwrRedForMBMS = Cell power reduction for MBMS transmission (cellPwrRedForMBMS) parameter The minimum value of the Cell power reduce (dlCellpwrRed) parameter is 0. System impact

Issue: 01D

DN09185982

383



Interdependencies between features There are no interdependencies between this and any other feature. 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 Table 232: Related parameters lists the new parameters to this feature. Table 232

Related parameters Full name

Abbreviated name

Managed object

Cell power reduction for MBMS transmission

cellPwrRedForMBMS

LNCEL

Cell power reduce

dlCellPwrRed

LNCEL

Maximum output power

pMax

LNCEL


Sales information

BSW/ASW


BSW

-


5.16 LTE1996: Flexi Zone Controller Application 5.16.1 Description of LTE1996: Flexi Zone Controller Application Introduction to the feature The LTE1996: Flexi Zone Controller Application feature consists of a framework to support Flexi Zone Access Points (FZAP) in the same serving area of a macro cell controlled by a Flexi Zone Controller (FZC). This FZC + FZAPs configuration aggregates a number of small cells under a single logical Zone eNB entity. Benefits

384

DN09185982

Issue: 01D



End-user benefits This feature does not affect the end-user experience. Operator benefits This feature: • • • •

reduces mobile core traffic simplifies the deployment of large number of small cells reduces the impact of small cells on macro cells enables a stand-alone solution within multi-vendor macro environments



System release




FDD-LTE 15A

-

-

FLC15A

TDD-LTE15A

-

-

TLC15A

OMS LTE OMS15A

UE -

NetAct NetAct 15.5

MME -

SAE GW -

Additional hardware requirements This feature requires the following hardware: • •

Flexi Zone Controller (FZC) Flexi Zone Access Point (FZAP)

Functional description Overview of Flexi Zone Controller Application LTE1996: Flexi Zone Controller Application is a software package which offers: • • • • • •

support of up to 100 FZAPs operability in both Nokia or multi-vendor macro deployment scenarios S1/X2 aggregation and mobility anchoring/biasing at the FZC support for the new proprietary Z1 interface between FZC and FZAP dynamic addition or removal of FZAPs FZAP management with minimal operator intervention

A comparison between LTE1996: Flexi Zone Controller Application and a standalone Flexi Zone Micro small cell deployment is provided in Figure 42: Standalone FZM versus LTE1996 Zone eNB deployment of small cells.

Issue: 01D

DN09185982

385


Figure 42


Standalone FZM versus LTE1996 Zone eNB deployment of small cells NetAct ZoneeNB Deployment

FZM Deployment SGW

MME NWI3 NE3S

iOMS

S1-U

S1-MME

BTSOM +NE3S

FZC

BTSOM

Z1 FlexieNB

FZM X2

FZAPs X2

UE Uu

Uu

The LTE1996: Flexi Zone Controller Application feature makes it possible for the Flexi Zone Controller to manage FZAPs as logical cells under a single eNB. Architecture overview The LTE1996: Flexi Zone Controller Application feature leverages BCN hardware (Flexi Platform on BCN hardware) and Flexi Zone Micro (FZM) to implement a Zone eNodeB. The Zone eNodeB is comprised of a Flexi Zone Controller (FZC) and one or more Flexi Zone Access Points (FZAP). The Flexi Zone Access Points communicate with their Controller over a wired backhaul. The interface between FZC and FZAP is known as the Z1 interface and carries control, bearer, and management information. The Flexi Zone Controller runs on BCN hardware and provides termination for the S1, X2, and BTSOM links. FZAPs terminate the air interface and the interface towards the controller. FZAPs are based on the same hardware as the FZM AiO (All-in-One), specially configured to run under an FZC in Zone configuration.

386

DN09185982

Issue: 01D


Figure 43


Flexi Zone System Architecture management NetAct

NE3S

SCLI

NWI3

SiteManager

iOMS

LocalManagement ofLTEaspectsofFZC BTSOM/ASN.1

ZoneeNB

WebUI

BTSOM/XoH

FZC S1(To/FromMME) S1-U(To/FromSGW) X2(OthereNB)

LocalManagement ofFZAP Z1

SiteManager

XoH

FZAP

FZAP 0...100 FZAPs

LocalManagement ofLTEaspectsofFZAP

LTE1996: Flexi Zone Controller Application supports up to 100 FZAPs. Each FZAP supports one cell. System impact Interdependencies between features The following features are related to LTE1996: Flexi Zone Controller Application as part of the Flexi Zone solution: • •

LTE2017: IPSec Support for Flexi Zone Controller LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I

Impact on interfaces •

•

• •

Issue: 01D

Flexi Zone Controller aggregates S1 and X2 interfaces. The FZC provides both the S1-MME interface to a Mobility Management Entity (MME) and the S1-U link to the Serving Gateway (SGW). FZC also provides X2 interfaces to neighboring eNBs, independently of whether these are Macro eNBs, another Flexi Zone Controller, or a standalone Flexi Zone Micro eNodeB. A new north-bound O&M interface, named NE3S, connects the FZC with NetAct and is primarily used for FZC platform/transport management. The LTE1996: Flexi Zone Controller Application feature also introduces a new southbound Z1 interface between FZC and FZAPs. The Z1 interface introduces the following FZAP management functionalities:

DN09185982

387


– – – –

g


Discovery, auto-connection and auto-configuration of FZAPs Mapping of FZAPs to pre-configured information model tables (LNCEL/APMOD) Cell setup on configured FZAPs Z1 link management (includes link supervision, link failure detection and link recovery actions)

Note: The LTE1996: Flexi Zone Controller Application feature assumes the existence of an operator-owned L2 network between FZAPs and FZC. Impact on network management tools This feature impacts network management tools as follows: •

From a NetAct point of view there are two interfaces to the Flexi Zone Controller. – –

•

Flexi Zone Controller as Zone eNodeB, controlled via the NWI3 interface to iOMS and the BTSOM/ANS/1 interface from iOMS to FZC Flexi Zone Controller via the NE3S interface, handling platform/transport management.

From the O&M perspective there are different solutions for Flexi Access Points and the Flexi Zone Controller: – –

BTS Site Manager interacts with FZC via the BTSOM/XoH interface. APs can interact with both BTS Site Manager and WebGUI for limited local management capabilities. WebGUI is introduced to support extensions needed for indoor enterprise deployments, supporting the following functionalities: • • • • • • • • • • •

Configure FZAP siteid Show FZAP bluetooth configuration Indicate FZAP PnP progress Show FZAP operation state Creation and download of configuration snapshots Reset FZAPs Reset FZAP configuration Manage FZAP certificates Block and unblock FZAPs Display FZAP hardware information View status of FZAP IPsec connections

Impact on system performance and capacity The maximum Zone eNB capacity configuration for both FDD and TDD solutions is as follows: • • •

388

Flexi Zone Controller limits the number of cells to a maximum of 100 FZAPs Flexi Zone Controller limits the number of active UEs at eNB level to a maximum of 10000 UEs. Each Flexi Zone Access Point limits the number of active UEs on a per-cell basis to the maximum configured value, according to parameter maxNumActUE.

DN09185982

Issue: 01D


–

g


Parameter maxNumActUE ranges from 0 to 840 UEs, depending of the type of FZAP hardware.

Note: Flexi Zone Controller only supports cells consisting of FZAPs. Management data Alarms Flexi Zone Controller Alarms and Faults lists alarms introduced with this feature. BTS faults and reported alarms Flexi Zone Controller Alarms and Faults lists BTS faults introduced with this feature. Measurements and counters FZC Measurements and Counters lists counters introduced with this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters FZC Parameters lists parameters introduced with this feature. Sales information Table 235

Sales information

BSW/ASW


BSW


5.17 LTE2017: IPSec Support for Flexi Zone Controller 5.17.1 Description of LTE2017: IPSec Support for Flexi Zone Controller Introduction to the feature The LTE2017: IPSec Support for Flexi Zone Controller feature introduces Internet Protocol Security (IPSec) support for the Flexi Zone Controller product. Benefits End-user benefits The IPSec protocol suite mitigates the probability of security breaches and data corruption on end-user devices. Operator benefits The implementation of IPSec functionality software within Flexi Zone Controller eliminates the need for external hardware.

Issue: 01D

DN09185982

389





System release




FDD-LTE15A

-

-

FLC15A

TDD-LTE15A

-

-

TLC15A

OMS -

UE -

NetAct -

MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Overview of IPSec Protocol IPSec is a standard that defines how virtual private networks (VPNs) can be set between network elements. In the context of feature LTE2017: IPSec Support for Flexi Zone Controller those elements are: Flexi Zone Access Point (FZAP), Flexi Zone Controller (FZC) and Security Gateway. IPSec provides three essential security functions: • • •

confidentiality, through the use of encryption integrity, through the use of checksums authentication

FZC supports a IKEv1 and IKEv2 (Internet Key Exchange) dual stack with the following capabilities: • • •

support of multiple IKE security associations (SAs) support of multiple IPSec SAs through Encapsulating Security Payload (ESP) support of multiple IPSec SAs per IKE SA

Implementation of IPSec in feature LTE2017 In the LTE2017: IPSec Support for Flexi Zone Controller feature, the IPSec solution is implemented on both south-bound and north-bound interfaces of the Flexi Zone Controller. On south-bound interfaces, the Flexi Zone Controller can establish a separate IPSec tunnel for each Flexi Zone Access Point under its domain. Southbound interfaces are to be protected by IKEv2 policies. On north-bound interfaces, data from separate tunnels is aggregated into up to three IPSec tunnels towards the Security Gateway: one for the user plane (U-plane) and either one or two for the control and management planes (C/M-plane).

g

390

Note: It is strongly recommended that the synchronization plane (S-plane), CMP, LDAP and DHCP traffic are placed outside of a IPSec tunnel. The operator has the ability to enable/disable IPSec separately for each of the traffic planes (U/C/M/S-plane).

DN09185982

Issue: 01D


Overview of IPSec implementation in Flexi Zone Controller

unprotected traffic

optional IPSectunnel

C/M-plane

U-plane

IPSectunnel

S-plane/CMP/LDAP/DHCP

protected traffic

SECURITYGATEWAY

C/M-plane

Figure 44


NORTHBOUND INTERFACES

FLEXIZONECONTROLLER

Z1 SOUTHBOUND INTERFACES

FLEXIZONE ACCESSPOINT

FLEXIZONE ACCESSPOINT

System impact Interdependencies between features The LTE2017: IPSec Support for Flexi Zone Controller feature requires the activation of the following features: •

LTE1996: Flexi Zone Controller Application

The LTE2017: IPSec Support for Flexi Zone Controller feature is required for the activation of the following features: •

LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I

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 The activation of the LTE2017: IPSec Support for Flexi Zone Controller feature can be expected to reduce the maximum LTE throughput. Management data

Issue: 01D

DN09185982

391



Alarms There are no alarms related to this feature. Measurements and counters There are no operative measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 237: New parameters lists new parameters introduced by this feature. Further information can be found in the FZC Parameters document. Table 237

New parameters

Full name

392

Abbreviated name

Managed object

Structure

Authentication Value

authValue

IKE

-

Dpd Action

dpdAction

IKE

-

Dpd Delay

dpdDelay

IKE

-

Dpd Max Fail

dpdMaxFail

IKE

-

Dpd Retry

dpdRetry

IKE

-

Encryption Value

encValue

IKE

-

Ike Authentication

ikeAuth

IKE

-

Ike Dh Group

ikeDhGroup

IKE

-

Ike Encryption

ikeEnc

IKE

-

Ike Hash

ikeHash

IKE

-

Ike Lifetime

ikeLifetime

IKE

-

Ike Version

ikeVersion

IKE

-

Lifetime

lifetime

IKE

-

Mode Value

modeValue

IKE

-

Name

name

IKE

-

PFS Group

pfsGroup

IKE

-

InstanceID

instanceId

IPSEC

-

IKE Version

ikeVersion

IPSGLBL

-

Replay Window Size

replayWsize

IPSGLBL

-

Action

action

IPSRULE

-

Direction

direction

IPSRULE

-

Destination Address

dstAddr

IPSRULE

-

Destination Port

dstPort

IPSRULE

-

Name

name

IPSRULE

-

Priority

priority

IPSRULE

-

DN09185982

Issue: 01D


Table 237



Full name

Abbreviated name

Managed object

Structure

Protocol Number

protoNum

IPSRULE

-

Source Address

srcAddr

IPSRULE

-

Source Port

srcPort

IPSRULE

-

Vpn

vpn

IPSRULE

-

Vrf

vrf

IPSRULE

-

CA Certificate

caCert

IPSVPN

-

Certificate Value

certValue

IPSVPN

-

Local Address

localAddr

IPSVPN

-

localIdentifier

localIdentifier

IPSVPN

-

localIdentifierType

localIdentifierType

IPSVPN

-

Name

name

IPSVPN

-

Private Key Value

privateKeyValue

IPSVPN

-

Remote Address

remoteAddr

IPSVPN

-

Secret Value

secretValue

IPSVPN

-

Template Name

templateName

IPSVPN

-

Vrf

vrf

IPSVPN

-

Name

name

OWNR

-


Sales information

BSW/ASW ASW



5.17.2 Activating and configuring LTE2017: IPSec Support for Flexi Zone Controller The LTE2017: IPSec Support for Flexi Zone Controller feature is activated through SCLI commands. Before you start The activation of feature LTE2017: IPSec Support for Flexi Zone Controller assumes that the Flexi Zone Controller is successfully commissioned and connected via SSH to a field engineering workstation (FEWS). The FEWS SSH connection will serve as the interface to communicate with the controller. The add operation within the fzc-ipsec command domain is used for establishing and bypassing IPsec protection within a specific traffic plane. The show operation within that same fzc-ipsec domain can be used to consult the policy status of said connections.

Issue: 01D

DN09185982

393


Table 239 Command


add fzc-ipsec commands Parame ter

add fzcipsec

nb

add fzcipsec sb

bypass

Attribute Either nb or sb is mandatory

Adds northbound IPsec configuration.

Adds southbound IPsec bypass policy rule.

protect

Either bypass or protect option is mandatory

add fzcipsec sb bypass

allzone

Mandatory

Adds southbound IPsec bypass policy rule for all planes.

add fzcipsec sb protect

allzone

Mandatory

Adds southbound IPsec configuration with protect policy rule for all planes.

add fzcipsec nb

bypass


Adds northbound IPsec bypass policy rule.

Either cmp, cplane or mplane option is mandatory

Adds northbound IPsec bypass policy rule for CMP server

sb

protect add fzcipsec nb bypass

cmp cplane mplane

add fzcipsec nb protect

394

Description

cplane mplane

Adds southbound IPsec configuration.

Adds southbound IPsec configuration with protect policy rule.

Adds northbound IPsec configuration with protect policy rule.

Adds northbound IPsec bypass policy rule for C-plane. Adds northbound IPsec bypass policy rule for M-plane.

Either uplane, cplane or mplane option is mandatory

Adds northbound IPsec configuration with protect policy rule for C-plane. Adds northbound IPsec configuration with protect policy rule for M-plane.

uplane

Adds northbound IPsec configuration with protect policy rule for U-plane.

add fzcipsec nb protect cplane

remote- Mandatory tep < remotetepvalue >

remote IPSec tunnel endpoint IPv4 address

add fzcipsec nb protect cplane remote-tep add fzc-ipsec nb protect mplane

templat e < templat e-value >

IKE template name

Optional

vpn < vpnvalue >

VPN object name

ikeversion < ikeversionvalue >

IKE version [ ikev1 | ikev2 ], default = ikev2

Privatekey <

private key file name, default = defaultPrivatekey.pem

DN09185982

Issue: 01D


Table 239 Command


add fzc-ipsec commands (Cont.) Parame ter

Attribute

Description

privatekeyvalue >

Issue: 01D

certifica te < certifica te-value >

certificate file for IKE authentication,default = defaultCertificate.pem

cacertifica te < cacertifica te-value >

CA certificate file for IKE authentication, default = defaultCaCertificate.pem

add fzcipsec nb protect mplane

remote- Mandatory tep < remotetepvalue >


add fzcipsec nb protect mplane remote-tep

templat e < templat e-value >

IKE template name

Optional

vpn < vpnvalue >

VPN object name

ikeversion < ikeversionvalue >


Privatekey < privatekeyvalue >


certifica te < certifica te value >



CA certificate file for IKE authentication, , default = defaultCaCertificate.pem.

remote- Mandatory tep

DN09185982

395


Table 239 Command


add fzc-ipsec commands (Cont.) Parame ter

Attribute

Description

e-tepvalue > add fzcipsec nb protect uplane remote-tep

templat Optional e

IKE template name

vpn

VPN object name

ikeversion


Privatekey < privatekeyvalue >


certifica te < certifica te value >



CA certificate file for IKE authentication, , default = defaultCaCertificate.pem.

The following sections provide the wrapper commands covering the most common IPsec activation use cases. For more information on these and other commands see Flexi Zone Controller SCLI Commands (DN09210703).

•

Applying IPsec to the FZC southbound interface Z1

add fzc-ipsec sb bypass allzone add fzc-ipsec sb protect allzone

396

DN09185982

Issue: 01D


•


Applying IPsec to the FZC southbound interface (Z1) and to the northbound user plane Sub-steps 1

add fzc-ipsec nb protect uplane remote-tep Where is the particular IP for the northbound U-plane.

2

Protect the southbound interface


•

Applying IPsec to the FZC southbound interface (Z1) and to the northbound control and management planes Sub-steps 1

add fzc-ipsec nb protect cplane remote-tep Where is the particular IP for the northbound C-plane.

2

add fzc-ipsec nb protect mplane remote-tep Where is the particular IP for the northbound M-plane.

3

add fzc-ipsec nb bypass cmp

4



•

Applying IPsec to the FZC southbound interface (Z1) and to the northbound control, management and user planes Sub-steps 1


2


Issue: 01D

DN09185982

397


3



4


5



•

Applying IPsec to the FZC northbound control, management and user planes Sub-steps 1


2


3


4


5.17.3 Deactivating LTE2017: IPSec Support for Flexi Zone Controller The LTE2017: IPSec Support for Flexi Zone Controller feature is deactivated through SCLI commands. Before you start The deactivation of feature LTE2017: IPSec Support for Flexi Zone Controller assumes that the Flexi Zone Controller is successfully commissioned and connected via SSH to a field engineering workstation (FEWS). The FEWS SSH connection will serve as the interface to communicate with the controller. The delete operation within the fzc-ipsec command domain is used for establishing and bypassing IPsec protection within a specific traffic plane. The show operation within that same fzc-ipsec domain can be used to consult the policy status of said connections.

398

DN09185982

Issue: 01D


Table 240 Command

delete fzc-ipsec commands Parame ter

delete fzcipsec

nb

delete fzcipsec sb

bypass

delete fzcipsec sb bypass delete fzcipsec sb protect delete fzcipsec nb

Attribute

Deletes northbound IPsec configuration.

Deletes southbound IPsec bypass policy rule.

protect


allzone

Mandatory

Deletes southbound IPsec bypass policy rule for all zone.

allzone

Mandatory

Deletes southbound IPsec configuration with protect rule for all zone.

bypass


Deletes northbound IPsec bypass policy rule.

Either cmp, cplane or mplane option is mandatory

Deletes northbound IPsec bypass policy rule for CMP server.

sb

cmp cplane mplane

delete fzcipsec nb protect

Description

Either nb or sb option is mandatory

protect delete fzcipsec nb bypass


cplane mplane

Deletes southbound IPsec configuration.

Deletes southbound IPsec protect policy rule.

Deletes northbound IPsec protect policy rule.

Deletes northbound IPsec bypass policy rule for C-plane. Deletes northbound IPsec bypass policy rule for M-plane.

Either uplane, cplane or mplane option is mandatory

uplane

Deletes northbound IPsec configuration with protect policy rule for C-plane. Deletes northbound IPsec configuration with protect policy rule for M-plane. Deletes northbound IPsec configuration with protect policy rule for U-plane.

The following sections provide the wrapper commands covering the most common IPsec deactivation use cases. For more information on these and other commands see Flexi Zone Controller SCLI Commands (DN09210703).

•

Removing IPsec from the FZC southbound interface Z1

delete fzc-ipsec sb bypass allzone •

Removing IPsec from the FZC southbound interface (Z1) and the northbound user plane Sub-steps 1

delete fzc-ipsec nb protect uplane remote-tep Where is the particular IP for the northbound U-plane.

Issue: 01D

DN09185982

399


2


Revoke protection of the southbound interface

delete fzc-ipsec sb bypass allzone

•

Removing IPsec from the FZC southbound interface (Z1) and from the northbound control and management planes Sub-steps 1

delete fzc-ipsec nb protect cplane remote-tep Where is the particular IP for the northbound C-plane.

2

delete fzc-ipsec nb protect mplane remote-tep Where is the particular IP for the northbound M-plane.

3

delete fzc-ipsec nb bypass cmp

4



•

Removing IPsec to the FZC southbound interface (Z1) and to the northbound control, management and user planes Sub-steps 1

delete fzc-ipsec nb protect cplane remote-tep Where is the particular IP for the northbound C-plane.

2

delete fzc-ipsec nb protect mplane remote-tep Where is the particular IP for the northbound M-plane.

3

delete fzc-ipsec nb protect uplane remote-tep Where is the particular IP for the northbound U-plane.

4

delete fzc-ipsec nb bypass cmp

5



400

DN09185982

Issue: 01D



5.18 LTE2049: System Upgrade to FDD-LTE 15A 5.18.1 Description of LTE2049: System Upgrade to FDD-LTE 15A Introduction to the feature The LTE2049: System Upgrade to FDD-LTE 15A feature enables a smooth system upgrade of the network from: release RL60 to release FDD-LTE 15A release RL70 to release FDD-LTE 15A

• •

The feature describes the overall system upgrade strategy and work flow. It includes backward compatibility and the possibility of automatic fallback or rollback to earlier release. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the operator with a smooth upgrade path from release RL60 to release FDD-LTE 15A and from release RL70 to release FDD-LTE 15A. Requirements Hardware and software requirements Table 241 System release FDD-LTE 15A Flexi Zone Controller -



FL15A

FL15A

OMS LTO15A

UE -

Flexi Zone Micro BTS FLF15A

-

NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview The LTE2049: System Upgrade to FDD-LTE 15A feature supports the software (SW) upgrade from release RL60 to release FDD-LTE 15A and from release RL70 to release FDD-LTE 15A. The system upgrade is possible in one step and there are no needed intermediate SW versions to be installed. The feature includes backward compatibility and provides the possibility of automatic fallback or rollback to release RL60 or release RL70.

Issue: 01D

DN09185982

401



The system upgrade is performed in a top-down approach as shown in Figure 45: Topdown approach for system upgrade: Figure 45

Top-down approach for system upgrade

RL70 Optional elements NetAct new release

NetAct old release

Traffica new release

Traffica old release

Top down

OMS new release

OMS old release

L3DC new release

L3DC old release

eNB new release

eNB old release

eNB old release

eNB old release

FDD-LTE 15A Service outages are minimized using available resiliency features and hardware redundancy. Therefore, it is not necessary to take the whole system out of service in introducing a new SW release.

g

Note: It is recommended to perform the system upgrade during low traffic load (for example, during night time) as service degradation and partial service loss cannot be fully avoided during the upgrade. Software upgrade from RL60 to FDD-LTE 15A The system upgrade supports the following software upgrades: •

g

Note: A mixed configuration of three releases is not supported in NetAct. The RL60 NEs must be upgraded directly to FDD-LTE 15A release. •

402

NetAct upgrade: NetAct 8 EP1 > NetAct 15.5 During system upgrade, NetAct must be able to manage the network elements (NEs) of RL60 release and FDD-LTE 15A release.

operation and maintenance server (OMS) upgrade: LTO6.0 > LTO15A The OMS upgrade is performed after a successful NetAct upgrade. Upgrading all OMSs in the network before upgrading the first evolved node B (eNB) is not needed. Instead, it is possible to upgrade a complete branch of the hierarchy from the OMS to the eNBs.

DN09185982

Issue: 01D


g


Note: The OMS upgrade is managed remotely using the NetAct software management (SWM) framework or locally using CLI-based Automatic Major SW Upgrade Runner Tool (AMSURT). •

•

•

eNB upgrade: LN6.0 > FL15A The eNB is upgraded after the controlling OMS has been upgraded. While the eNB is upgrading, NetAct and OMS can manage the eNBs of the former release and the new release in parallel. Traffica upgrade: Traffica 6 SP3 > Traffica 15.5 There is no dependency between the Traffica upgrade and the NetAct/OMS/eNB upgrade. However, it is recommended to upgrade Traffica in parallel with NetAct. Layer 3 Data Collector (L3DC) upgrade: L3DC7.0 > L3DC 15 There is no dependency between the L3DC upgrade and the NetAct/OMS/eNB upgrade. However, it is recommended to upgrade the L3DC before upgrading the eNBs. If the eNB is upgraded and the L3DC is running in the old version, no problems are expected since the L3DC ignores unknown messages.

Software upgrade from RL70 to FDD-LTE 15A The system upgrade supports the following software upgrades: •

•

NetAct upgrade: NetAct 15.2 > NetAct 15.5 During system upgrade, NetAct must be able to manage the NEs of RL70 release and FDD-LTE 15A release. OMS upgrade: LTO7.0 > LTO15A The OMS upgrade is performed after a successful NetAct upgrade. Upgrading all OMSs in the network before upgrading the first eNB is not needed. Instead, it is possible to upgrade a complete branch of the hierarchy from the OMS to the eNBs.

g

Note: The OMS upgrade is managed remotely using the NetAct SWM framework or locally using CLI-based AMSURT. •

eNB upgrade: – –

g

LN7.0 > FL15A LNF7.0 > FLF15A Note: The Flexi Zone Controller (FZC) and Flexi Zone Access Point (FZ AP) are introduced in FDD-LTE 15A release and no upgrade paths are supported.

•

•

The eNB is upgraded after the controlling OMS has been upgraded. While the eNB is upgrading, NetAct and OMS can manage the eNBs of the former release and the new release in parallel. Traffica upgrade: Traffica 7 > Traffica 15.5 There is no dependency between the Traffica upgrade and the NetAct/OMS/eNB upgrade. However, it is recommended to upgrade Traffica in parallel with NetAct. L3DC upgrade: L3DC7.5 > L3DC 15 There is no dependency between the L3DC upgrade and the NetAct/OMS/eNB upgrade. However, it is recommended to upgrade the L3DC before upgrading the eNBs. If the eNB is upgraded and the L3DC is running in the old version, no problems are expected since the L3DC ignores unknown messages.

Configuration data synchronization

Issue: 01D

DN09185982

403



After the eNB upgrade, the data conversion performed by the eNB during the upgrade needs to be synchronized with the NetAct configuration manager (CM). The LTE954: Intelligent configuration synchronization feature automatically synchronizes NetAct. If the LTE954: Intelligent configuration synchronization feature is enabled, automatic upload of the configuration data is not started immediately after the upgrade, but is started after a configurable time interval. If this feature is disabled, data synchronization of NetAct must be executed manually after the upgrade via CM upload. Data management during software upgrade All operator-configured data are maintained in the system. Configuration data created in the earlier release are automatically converted into a new format valid for the new release during the upgrade. The data include the following: • • •

g

all configuration data of the Flexi Multiradio BTS, OMS, NetAct, L3DC, and Traffica customized view in the BTS site manager (BTSSM) or NetAct user specified accounts and passwords Note: In case of off-line migration in the BTSSM, there should only be less than or equal to 16 LNRELW managed objects for each carrier frequency (under LNCEL managed object) with the Redirect with system information allowed (redirWithSysInfoAllowed) parameter set to allowed.

After the system upgrade and fallback, no important NE information is lost. This information includes the following: • • • •

network security-related system data (such as certificates and keys) user security-related data (such as user accounts and passwords) symptom, trace, and log data configuration data (such as transport configuration, base transceiver station (BTS) configuration, radio network (RNW) configuration, and performance management (PM) data configuration)

Backward compatibility Backward compatibility means that interworking between the upgraded and the nonupgraded NEs is possible during the system upgrade. Because of the top-down approach, the following backward compatibilities are supported: • • • •

NetAct 15.5 needs to support the OMS and eNB with releases RL60 and RL70. LTO15A needs to support the eNB with releases RL60 and RL70. Traffica 15.5 needs to support the L3DC and eNB with releases RL60 and RL70. L3DC 15 needs to support the eNB with releases RL60 and RL70.

In addition, mixed eNB and OMS configurations such as LTO15A (FDD-LTE 15A) and LN7.0 (RL70) must be supported by the OMS and NetAct, while mixed L3DC and eNB configurations such as L3DC 15 (FDD-LTE 15A) and LN7.0 (eNB RL70) must be supported by the L3DC and Traffica.

g

404

Note: A mixed configuration of three releases is not supported.

DN09185982

Issue: 01D



The eNB SW of a new release (FDD-LTE 15A) is backward compatible with the configuration data of a former base release RL70 or RL60. After the start up, the new SW can access and read the configuration data of the former release as input for the conversion to a new format. This is necessary to support automatic online data conversion. Software fallback Software fallback is an automatic activation of an earlier SW version that is active before the SW upgrade and is stored in the eNB. Fallback is triggered when the eNB or OMS is unable to activate its new software version or use a new database configuration version. If the eNB does not locally store the complete fallback SW for all the hardware (HW) units, it may request from NetAct a software update for the latest active software build for a managed HW module compatible with the eNB software version. Only after the SW download from NetAct can service be re-established. After the successful fallback, the passive software build is active in all the HW units and service can be re-established. Any configuration updates done with the new SW is lost, since the eNB takes the configuration database into service that fits to the fallback SW.

g

Note: In case of minor failures, no SW fallback is initiated but the error information is indicated. The failures are logged in a non-volatile memory and include a detailed information about the reason of the failure. Software rollback SW rollback is a manually initiated SW fallback using the BTSSM or NetAct SWM. The operator can trigger SW rollback when key services are not activated successfully after the SW upgrade. Note that SW rollback is only guaranteed if the source SW version has not been removed or overwritten in a non-volatile storage (NVS). SW rollback is done with the SW stored in the passive file system and no SW download from the server is part of the operation. If the passive SW has been overwritten with a different SW version, the rollback to the former release is not possible.

g

Note: A software rollback to the stored SW load restores the earlier configuration. If there has been a major network reconfiguration after the upgrade, such as reconfiguring the eNB from IPv4 to IPv6 or updating operator certificates, then network connectivity issues can occur after the rollback. Reconfigurations after the SW upgrade must be evaluated before triggering SW rollback to avoid service outage. Software rollback introduced in RL70 is considered more reliable than software downgrade used in earlier releases. This is because in software rollback the file systems are switched and the original configuration files are used while in software downgrade the current configuration files are copied from the active to the passive bank. Software rollback for a single eNB or for eNBs in bulk can be done using the NetAct SWM. For more information, see the Software Manager Help document under Network Administration in NetAct Operating Documentation. Software rollback for a single eNB can also be performed using the Rollback to Passive SW function in the Update SW to BTS Site window on the BTSSM. If the operator selects a software version lower than the active file in the Update SW to BTS Site window on the BTSSM and clicks Update, a software downgrade occurs.

g

Issue: 01D

Note: Software downgrade should not be executed. Software downgrade to an earlier software version is not guaranteed and might end up in an uncommissioned state of the eNB.

DN09185982

405


g


Note: Software rollback operation from the NetAct might interrupt ongoing local operations triggered from BTSSM like commissioning without local user warning. System impact Interdependencies between features The LTE954: Intelligent configuration synchronization feature covers the NetAct synchronization function, which is used after the eNB upgrade data conversion synchronization with NetAct. 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 When NEs become fully or partially unavailable, overall system performance and capacity might be affected during the upgrade procedure. With the new SW, some new features are implemented that might affect the overall system performance and capacity. The new features are out of scope of this feature description. 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 242

Sales information

BSW/ASW BSW

406


DN09185982


Issue: 01D



5.19 LTE2061: OMS HP Gen9 HW assignment 5.19.1 Description of LTE2061: OMS HP Gen9 HW assignment Introduction to the feature The LTE2061: OMS HP Gen9 HW assignment feature introduces new hardware (HW) for LTE OMS, particularly the HP ProLiant Gen9 blade servers, which replace the HP ProLiant Gen8 server in new deliveries. The OMS applications and functions are the same in G6, Gen8, and Gen9 HW. The preliminary capacity and dimensioning are the same as with the OMS Gen8 HW. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides better performance as compared to Gen8. Gen9 uses less time for event handling and task processing commanded by NetAct. Thus, Network management works faster end to end. It also makes OMS less sensitive to unexpected and extremely high overload situations. The LTE OMS connectivity remains the same as with Gen8 HW. Requirements Hardware and software requirements Table 243 System release FDD-LTE 15A Flexi Zone Controller -


Flexi Multiradio 10 BTS -

OMS LTE OMS15A


UE 0

-

NetAct -


MME -

SAE GW -

Additional hardware requirements This feature requires the HP ProLiant BL460c Gen9 hardware. Functional description Functional overview In LTE2061: OMS HP Gen9 HW assignment feature, when the Gen9 hardware is located in an earlier delivered c7000 chassis (where the G6 and/or Gen8 server blades are located), the firmware of the old blades and c7000 must be checked and updated if it is older than version 4.30 to ensure compatibility with the Gen9 server blades. The technical details of LTE OMS Gen9 are as follows:

Issue: 01D

DN09185982

407


• • • • •


Server type: BL460c (blade) CPU: 2 x 12-core RAM: 64 GB HDD capacity: 2 x 600GB / 15k rpm Ethernet Connectivity: 2 x 10 Gb Ethernet ports (1 Gb Ethernet is also supported)

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 244

Sales information

BSW/ASW


BSW

-

Activated by default -

5.20 LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness 5.20.1 LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness Introduction to the feature

408

DN09185982

Issue: 01D



The LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness feature enhances the inter-radio access technology (RAT) UMTS terrestrial radio access network (UTRAN) neighbor relations and supports the following functions: autonomous removal of unused UTRAN neighbor cells revalidation of UTRAN physical cell identity (PCI) warning for UTRAN PCI's suspect on PCI-confusion

• • •

g

Note: This feature covers wideband code division multiple access (WCDMA) neighbors. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits In the network setup, the important neighbor relations are kept while obsolete neighbor relations are automatically deleted. The learned identification of the neighbors in interRAT automatic neighbor relation (ANR) is revalidated in case it is needed. Handover is executed following the real network setup. Requirements Hardware and software requirements Table 245



FL15A



FL15A

OMS -


UE -


NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview With the LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness feature, the evolved node B (eNB) supports the following functions: •

autonomous removal of unused UTRAN neighbor cells The eNB supports the autonomous removal of stored UTRAN neighbors that are no longer used by the eNB. The autonomous removal function covers: – –

Issue: 01D

removal of UTRAN neighbor relations (LNRELW mocs) not used for a configurable Idle time threshold removal of UTRAN neighbor cell configuration information (LNADJW mocs), if the last LNRELW related to the LNADJW is removed by eNB

DN09185982

409


•

In addition, it is possible to exclude a certain UTRAN neighbor relation from autonomous removal via a suitable operation and maintenance (O&M) configuration. revalidation of UTRAN PCI The eNB supports the checking of the validity of a stored UTRAN neighbor relations by repeating the corresponding cell global identification (CGI) measurement. The following two mechanisms trigger revalidation: –

–

•

g


If the configurable number of consecutive failures of mobility management procedures is observed for a UTRAN neighbor relation, then the eNB suspects that the UTRAN neighbor relation might be no longer correct and triggers a revalidation of the UTRAN neighbor relation. If the operator configures the periodic revalidation, the eNB periodically revalidates all the available UTRAN neighbor relations.

warning for UTRAN PCI's suspects on PCI confusion The eNB uses the UTRAN PCI revalidation process to check if there are PCIs available, which are suspects for PCI confusion. An UTRAN PCI is considered as suspect of PCI confusion if the eNB observes that the UTRAN neighbor relation stored for that UTRAN PCI, toggles between two UTRAN neighbor cells. If the PCI confusion is detected, the eNB raises a PCI confusion warning to the operator. Note: This mechanism does not solve PCI confusions, but the operator can detect this situation and take corresponding actions (for example, modifying of PCI assignments).

System impact Interdependencies between features This feature affects the following features: •

•

•

•

410

LTE908: ANR Inter-RAT UTRAN - Fully UE-based PCI revalidation and PCI confusion detection for UTRAN neighbor cells, as described in the LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness feature, are possible only if UE-based UTRAN ANR is available for the respective UTRAN neighbor cells (CGI measurements for the UTRAN neighbor cells are possible). LTE1073: Measurement-based Redirect to UTRAN Autonomous removal mechanism for UTRAN neighbor relations will take into account triggers for measurement-based redirection to the UTRAN as one of the events that may inhibit removal of a UTRAN neighbor relation. LTE1357: LTE-UTRAN Load Balancing Autonomous removal mechanism for UTRAN neighbor relations will take into account triggers for LTE-UTRAN load balancing (that is, respective B1 measurement report) as one of the events that may inhibit the removal of a UTRAN neighbor relation. LTE507: InterRAT Neighbor Relation Optimization (LTE, UTRAN, GERAN) With the LTE507: InterRAT Neighbor Relation Optimization (LTE, UTRAN, GERAN) feature, the intelligent self-organizing network (iSON) manager evaluates performance measurements use to identify badly performing UTRAN neighbor relations. Once bad UTRAN neighbor relations have been identified, the iSON manager blacklists the respective mobility management procedures of the neighbor relation by using the respective parameters (those are, PS handover allowed (psHoAllowed), Single radio Voice call continuity allowed (srvccAllowed), and Circuit-switched fallback with PS handover allowed (csfbPsHoAllowed) parameters).

DN09185982

Issue: 01D


•


If LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness feature deletes a blacklisted UTRAN neighbor relation or LNRELW, the ANR may recreate the UtranNR or LNRELW as 'not blacklisted' again, that is LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness feature may remove the blacklisting performed by LTE507: InterRAT Neighbor Relation Optimization (LTE, UTRAN, GERAN) feature again. To prevent this, LTE507: InterRAT Neighbor Relation Optimization (LTE, UTRAN, GERAN) feature is enhanced to set the Remove allowed (removeAllowed) parameter to 'false' by default. The operator shall have the option to override this new behavior of the LTE507: InterRAT Neighbor Relation Optimization (LTE, UTRAN, GERAN) feature on the user interface (UI) of the iSON manager. LTE783: ANR InterRAT UTRAN With the LTE783:ANR InterRAT UTRAN feature, the iSON manager might create UTRAN neighbor relations, for example, based on geo-location data. If the LTE783:ANR InterRAT UTRAN feature is applied to create WCDMA UTRAN neighbor relations or LNRELW objects, the LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness feature might autonomously remove these UTRAN neighbor relations. To prevent this, the LTE783: ANR InterRAT UTRAN feature is enhanced to set the Remove allowed (removeAllowed) parameter to 'false' by default. The operator shall have the option to override this new behavior of the LTE783: ANR InterRAT UTRAN feature on the UI of the iSON manager.

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 BTS faults and reported alarms Table 246: New BTS faults lists BTS faults introduced with this feature. Table 246

New BTS faults

Fault ID

Fault name


6281

WCDMA PSC confusion detected

7655

Alarm name CELL NOTIFICATION

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.

Issue: 01D

DN09185982

411



Parameters Table 247: New parameters lists the new parameters modified by this feature. Table 247


Abbreviated name

Managed object

Activate autonomous removal of UTRAN neighbours

actAutoUtranNeighRemoval

LNBTS

ANR Robustness Level for UTRAN

anrRobLevelUtran

LNBTS

Consecutive UTRAN HO execution failure re-validation TH

consecUtranHoFailThres

LNBTS

Idle time threshold for UTRAN neighbour relations

idleTimeThresUtranNR

LNBTS

UTRAN periodical revalidation wait timer

utranPrdRevalWaitTmr

LNBTS

Neighbour relation status

nrStatus

LNRELW

Remove allowed

removeAllowed

LNRELW


Sales information

BSW/ASW ASW



5.20.2 Activating and configuring LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness Before you start The LTE908: ANR Inter-RAT UTRAN - Fully UE Based feature needs to be activated to enable the PCI re-validation and the confusion detection. The Activate autonomous removal of UTRAN neighbours (actAutoUtranNeighRemoval) parameter is used for activation of the autonomous removal function. Modification of this parameter requires neither eNB restart nor cell locking.

g g

412

Note: The re-validation mechanism due to consecutive UTRAN HO execution failures and the periodical re-validation mechanism are activated independently, either at the same time or one at a time. Note: Autonomous removal can be used independently without LTE908: ANR Inter-RAT UTRAN - Fully UE Based feature (though this is not recommended).

DN09185982

Issue: 01D



Procedure 1


2

Activate UTRAN PCI revalidation after consecutive handover failures. On the selected LNBTS object, set the Consecutive UTRAN HO execution failure re-validation TH (consecUtranHoFailThres) parameter to a value different than 0.

g

Note: Modification of this parameter is only necessary if default value does not fit the needed configuration.

g

Note: If the value is set to "0", then no re-validation due to consecutive HO failures is triggered.

g

Note: The valid value for the consecUtranHoFailThres parameter is from 0 to 15.

3

Activate periodic UTRAN PCI revalidation. On the selected LNBTS object, set the UTRAN periodical revalidation wait timer (utranPrdRevalWaitTmr) parameter to a value different than 0.

Issue: 01D

g

Note: Modification of this parameter is only necessary if default value does not fit the needed configuration.

g

Note: If utranPrdRevalWaitTmr parameter is set to "0", then no re-validation is triggered.

DN09185982

413


g


Note: The valid values for the utranPrdRevalWaitTmr parameter are: • • • • • • • • • • • • • • • •

4

Activate the autonomous removal of UTRAN neighbors. a) b) c) d)

5

0min 10min 30min 60min 120min 180min 240min 480min 960min 1440min 2160min 2880min 4320min 5760min 7200min 10080min

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate autonomous removal of UTRAN neighbours (actAutoUtranNeighRemoval) parameter value to true.

Set the Idle time threshold for UTRAN neighbour relations (idleTimeThresUtranNR) parameter value. On the selected LNBTS object, set the Idle time threshold for UTRAN neighbour relations (idleTimeThresUtranNR) parameter value.

g

Note: The valid value for the idleTimeThresUtranNR parameter is from 2h to 360h.

6

g

Set the ANR Robustness Level for UTRAN (anrRobLevelUtran) parameter value. Note: For high level of robustness, the minimum wait time between re-validations of the same neighbor relation becomes shorter. On the selected LNBTS object, set the ANR Robustness Level for UTRAN (anrRobLevelUtran) parameter value.

414

DN09185982

Issue: 01D



g

Note: Modification of this parameter is only necessary if default value (middle) does not fit on the configuration.

g

Note: The valid values for the anrRobLevelUtran parameter are: • • • • • •

7

Configure the Remove allowed (removeAllowed) parameter. a) b) c) d)

g

none very low low middle high very high

Expand the LNBTS object. Expand the LNCEL object. Select the LNRELW object. Configure the Remove allowed (removeAllowed) parameter. Note: The LNRELW objects are created autonomously by eNB via LTE908: ANR Inter-RAT UTRAN - Fully UE Based feature with the removeAllowed parameter that is set to true.

g

Note: The eNB will not autonomously remove the neighbor relation if the removeAllowed parameter value is set to false.

g

Note: The eNB is allowed to autonomously remove the neighbor relation if the removeAllowed parameter value is set to true.

8


Expected outcome The autonomous removal of unused UTRAN neighbor cells, revalidation of UTRAN PCI, and warning for UTRAN PCI's suspects on PCI confusion are activated.

5.20.3 Deactivating LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness Before you start The Activate autonomous removal of UTRAN neighbours (actAutoUtranNeighRemoval) parameter is used for deactivation. Modification of this parameter does not require neither eNB restart nor cell locking.

Issue: 01D

DN09185982

415



Procedure 1


2

Deactivate the autonomous removal of UTRAN neighbors. a) b) c) d)

3

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate autonomous removal of UTRAN neighbours (actAutoUtranNeighRemoval) parameter value to false.

Deactivate UTRAN PCI revalidation after consecutive handover failures. On the selected LNBTS object, set the Consecutive UTRAN HO execution failure re-validation TH (consecUtranHoFailThres) parameter to 0.

4

Deactivate periodic UTRAN PCI revalidation. On the selected LNBTS object, set the UTRAN periodical revalidation wait timer (utranPrdRevalWaitTmr) parameter to 0.

5


Expected outcome The autonomous removal of unused UTRAN neighbor cells, revalidation of UTRAN PCI, and warning for UTRAN PCI's suspects on PCI confusion are deactivated.

5.21 LTE2084: UE MAC Measurement Addition to Cell Trace 5.21.1 Description of LTE2084: UE MAC Measurement Addition to Cell Trace Introduction to the feature The LTE2084: UE MAC Measurement Addition to Cell Trace feature appends additional fields for the following measurements to the trace report: • •

416

user equipment's (UE's) rank indication UE's physical uplink shared channel (PUSCH) scheduled physical resource block (PRB) number

DN09185982

Issue: 01D


• •


UE's physical downlink shared channel (PDSCH) scheduled PRB number UE's buffer status report (BSR)

Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature introduces measurement reports that will be used for network optimization purposes. Requirements Hardware and software requirements Table 249: Hardware and software requirements presents hardware and software requirements for this feature. Table 249 System release FDD-LTE 15A




OMS -

UE -


FL16

NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview The LTE2084: UE MAC Measurement Addition to Cell Trace feature is an extension of the LTE1501: Measurement Report (MR) Addition to Cell Trace feature. The following related periodic measurements are supported by an eNB in the MAC layer: •

•

Issue: 01D

UE's rank indication, where times of RANK1/RANK2/RANK3/RANK4 are reported by a UE for DL scheduling during a periodic measurement report interval.This measurement data is used to analyze the rationality of the double-current shedule, related to the times of downlink double-current schedules/ the number of TB blocks calculated by the network management. PRB numbers scheduled for PUSCH is defined as the PRB number actually occupied by the UE's PUSCH. This measurement data represents the original measured value of the PRB number occupied by the UE's PUSCH of the serving cell. If in this sampling the UE has not been scheduled, then the value of PUSCHPRBNum is 0.

DN09185982

417


•

•

g


PRB number scheduled for PDSCH is defined as the PRB number actually occupied by the UE's PDSCH. This measurement data represents the original measured value of the PRB number occupied by the UE's PDSCH of the serving cell. If in this sampling the UE has not been scheduled, then the value of PDSCHPRBNum is 0. UE's BSR reflects the number of serving cells the UE needs for an uplink data transmission. It can be used to judge whether the slow uplink rate is caused by a small buffer data volume. This measurement data represents the original measured value of a UE buffer status report received in a serving cell.

Note: All measurements are of an average value during the measurement interval. These additional measurements have the same measurement intervals (reportInterval); the report amount can be set to any valid value (2, 4, 8, 16, 32, 64, or infinity, with the default set to infinity). The ms5120, ms10240 and longer (any valid value greater than or equal to 5120 ms can be configured: 5120 ms, 10240 ms, 1 min, 6 min, 12 min, 30 min or 60 min as reportInterval). The above measurement items can be activated or deactivated by the O&M separately. The configuration for the above measurements is done via TraceViewer, NetAct CM, or BTSSM. System impact Interdependencies between features The following features are interrelated LTE2084: UE MAC Measurement Addition to Cell Trace feature : • • • •

•

the LTE953: MDT (Minimization of Drive Tests) feature, which introduces an MDT functionality in RAN the LTE1308: MDT Cell Trace Enhancements feature, which introduces an enhanced MDT functionality the LTE1501: Measurement Report (MR) Addition to Cell Trace feature, which introduces additional cell trace objects the LTE1931: Measurement Report Addition with UE Uplink SINR feature, which enhances the LTE1501: Measurement Report (MR) Addition to Cell Trace feature to provide the UL SINR to the MR collector tool the LTE2054: Measurement Report Addition with PDCP KPI Counter Subset feature, which enhances the LTE1501: Measurement Report (MR) Addition to Cell Trace feature to provide the PDCP KPI counter subset to the MR collector tool

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

418

DN09185982

Issue: 01D



This feature might have a minor impact on the radio access network's (RAN's) level system performance in terms of increased response times and resource usage. However, the collection/upload of these additional periodic trace data items must not negatively impact such KPIs as the RRC setup success rate, HO success rate, cell throughput, and so on. The feature is expected to result in a small increase in the trace data bandwidth. The periodic trace bandwidth increases by about 2%, and the overall total trace bandwidth increases by about 0.5%. 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 250: Related existing parameters presents existing parameters related to this feature. Table 250


Full name

Issue: 01D

Abbreviated name

Managed object

Structure

Activate vendor specific cell trace enhancements

actVendSpecCellTrace LNBTS Enh

-

Enhanced cell vendor specific tracing

enhCellVendorSpecTr acing

MTRACE

-

Angle of arrival tracing aoATracing

MTRACE


PDSCH PRB number tracing

pDSCHPRBNumberTr acing

MTRACE


Power head room tracing

pHRTracing

MTRACE


PUSCH PRB number tracing

pUSCHPRBNumberTr acing

MTRACE


RIP report interval

ripReportInterval

MTRACE


RIP report type

ripReportType

MTRACE


RIP tracing

ripTracing

MTRACE


Timing advance tracing synchronized

tATracingSynch

MTRACE


DN09185982

419


Table 250



Full name

Abbreviated name

Managed object

Structure

UE BSR tracing

uEBSRTracing

MTRACE


UE RANK tracing

uERankTracing

MTRACE


UpLink SINR tracing

uLSINRTracing

MTRACE


Sales information Table 251: Sales information presents sales information about this feature. Table 251

Sales information

BSW/ASW


ASW

Pool license


5.21.2 Activating and configuring LTE2084: UE MAC Measurement Addition to Cell Trace Before you start Table 252: Parameters used for activating and configuring LTE2084: UE MAC Measurement Addition to Cell Trace lists parameters used for the activation and configuration of the LTE2084: UE MAC Measurement Addition to Cell Trace feature. Table 252

Parameters used for activating and configuring LTE2084: UE MAC Measurement Addition to Cell Trace Parameter

Purpose


Activate vendor specific cell trace enhancements (actVendSpecCellTrace Enh)


no

Enhanced cell vendor specific tracing (enhCellVendorSpecTr acing) structure


no

To activate and configure the feature, do the following: Procedure 1


420

DN09185982

Issue: 01D


2

Activate the LTE2084: UE MAC Measurement Addition to Cell Trace feature. a) b) c) d) e) f)

3


Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate cell trace (actCellTrace) parameter value to true. Set the Activate MDT cell trace (Activate MDT cell trace) parameter value to true. Set the Activate vendor specific cell trace enhancements (actVendSpecCellTraceEnh) parameter value to true.

Configure the feature parameter for the LTE2084: UE MAC Measurement Addition to Cell Trace feature. a) b) c) d) e)

Go to the Radio Network Configuration page. Expand the MRBTS object. Select and add the LNBTS object. Select the New CTRLTS object. For the CTRLTS object set the NetAct IP address (netActIpAddr) parameter value. f) Select and add the CTRLTS object. g) Add the New MTRACE object. h) Set the Cell trace session identifier (mTraceId) parameter value. i) Expand the MTRACE object. j) Set the E-UTRAN trace identifier (eutranTraceId) prameter values. k) Set the following parameters to desired values: • • • • •

MCC (eutranTraceIdMcc) MNC (eutranTraceIdMnc) MNC length (eutranTraceIdMncLen) Trace ID (traceId) Trace recording sesssion reference (trcRecSessionRef)

l)

Select the MTRACE object and add Enhanced cell vendor specific tracing (enhCellVendorSpecTracing) object. m) Set the Enhanced cell vendor specific tracing (enhCellVendorSpecTracing) parameter value. n) Set the following parameters' values to true: • • • •

UE BSR tracing (uEBSRTracing) UE RANK tracing (uERankTracing) PDSCH PRB number tracing (pDSCHPRBNumberTr acing) PUSCH PRB number tracing (pUSCHPRBNumberTr acing)

o) Select the MTRACE object. p) Set the Job type (jobType) parameter value to ImmediateMDTOnly or ImmediateMDTandTrace.

Issue: 01D

DN09185982

421



q) Select the MTRACE object and add the Periodic UE measurements (periodicUeMeas) object. r) Select Periodic UE measurements (periodicUeMeas) object and set the required amount of reports and interval. s) If needed, set the following parameters' values to None: • • •

4

Trace S1 setting (traceS1Setting) Trace RRC setting (traceRrcSetting) Trace X2 setting (traceX2Setting)


Expected outcome The LTE2084: UE MAC Measurement Addition to Cell Trace feature is activated.

5.21.3 Deactivating LTE2084: UE MAC Measurement Addition to Cell Trace Before you start The Activate vendor specific cell trace enhancements (actVendSpecCellTrace Enh) parameter is used for deactivation. Modification of this parameter does not require an eNB restart. To deactivate the feature, do the following: Procedure 1


2

Deactivate the LTE2084: UE MAC Measurement Addition to Cell Trace feature. a) b) c) d)

422

Go to the Radio Network Configuration page. Expand the MRBTS object. Select the LNBTS object. Set the Activate vendor specific cell trace enhancements (actVendSpecCellTrace Enh) parameter value to false.

DN09185982

Issue: 01D


3



Expected outcome The LTE2084: UE MAC Measurement Addition to Cell Trace feature is deactivated.

g

Note: At this point MTRACE object is not deleted only the trace is stopped.

5.22 LTE2175: PM Counter Enhancement for CSFB to 1xRTT, CQI Level, E-RAB Abnormal Release 5.22.1 Description of LTE2175: PM Counter Enhancement for CSFB to 1xRTT, CQI Level, E-RAB Abnormal Release Introduction to the feature The LTE2175: PM Counter Enhancement for CSFB to 1xRTT, CQI Level, E-RAB Abnormal Release feature enables performance monitoring (PM) counter enhancements. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature introduces PM counters enhancements according to customer requirements. The operator can monitor the CS fallback to 1xRTT/CDMA2000, the released active radio access bearers (E-RABs) for QCI5, QCI6, QCI7, QCI8 and QCI9, and the events when the UE reports a wideband CQI (Channel Quality Information) level 0 to15 for Codeword (CW) 1. Such monitoring has not been supported before. Requirements Hardware and software requirements Table 253: Hardware and software requirements presents hardware and software requirements. Table 253 System release FDD-LTE 15A

Issue: 01D



DN09185982



423


Table 253




OMS -

UE -

NetAct -

MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview The LTE2175: PM Counter Enhancement for CSFB to 1xRTT, CQI Level, E-RAB Abnormal Release feature implements the following PM counters: 1. PM counters for CS fallback (CSFB) to CDMA2000 1x radio transmission technology (1xRTT) 2. PM counters for UE-reported CQI classes separated for codeword CW 1 3. PM counters enhancement for an abnormal E-UTRAN E-RAB release

g g

Note: See Measurements and counters for the list of the implemented counters. Note: See Reference/Counters for a full information on measurements and counters. This excel report shows the full set of measurement and counter attributes including the change information. 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 Table 254: New counters presents counters introduced with this feature.

424

DN09185982

Issue: 01D


Table 254

New counters

Counter ID

Issue: 01D


Counter name

Measurement

M8016C45

CS fallback 1xRTT parameter requests

8016 - LTE inter system handover

M8016C46

CS fallback 1xRTT parameter responses


M8016C47

CS fallback preparations to 1xRTT


M8016C48

CS fallback UL handover 8016 - LTE inter system preparation transfers to 1xRTT handover

M8016C49

Failed CS fallback preparations to 1xRTT due to received HO failure indication message


M8010C76

UE-reported CQI level 0 for codeword 1

8010 - LTE power and quality DL

M8010C77



M8010C78



M8010C79



M8010C80



M8010C81



M8010C82



M8010C83



M8010C84



M8010C85



M8010C86



M8010C87



DN09185982

425


Table 254



Counter ID

Counter name

Measurement

M8010C88



M8010C89



M8010C90



M8010C91



M8006C239

Released active ERABs QCI5


M8006C240



M8006C241



M8006C242



M8006C243





KPI ID

KPI name

LTE_5706a

E-UTRAN average CQI for Code Word 1

LTE_5740a

E-UTRAN average CQI for Code Word 0

LTE_5741a

CSFB parameter requests to 1xRTT

LTE_5742a

CSFB parameter responserRatio to 1xRTT

LTE_5743a

CSFB preparations to 1xRTT

LTE_5744a

CSFB preparation transfer SR to 1xRTT

LTE_5745a

CSFB preparation failure ratio to 1xRTT due to HO failure

Parameters There are no parameters related to this feature. Sales information Table 256: Sales information presents parameters introduced with this feature.

426

DN09185982

Issue: 01D


Table 256


Sales information

BSW/ASW


BSW

-


5.23 LTE2182: Enhanced Flexi Zone Plug and Play for Non-Operator Owned Backhaul 5.23.1 Description of LTE2182: Enhanced Flexi Zone Plug and Play for Non-Operator Owned Backhaul Introduction to the feature The LTE2182: Enhanced Flexi Zone Plug and Play for Non-Operator Owned Backhaul feature enhances the existing Plug and Play solution for the Flexi Zone Micro/Pico BTS and Flexi Zone Indoor Pico BTS. The feature supports no-touch Plug and Play on nonoperator owned backhaul such as enterprise and public backhaul deployments. End-user benefits This feature does not affect the end-user experience. Operator benefits This feature enables operators to perform no-touch Plug and Play for small cells on nonoperator owned networks such as enterprise and public backhaul deployments without the need to provision the external DHCP servers with eNB- or operator specific information. Requirements Table 257 System release FDD-LTE 15A


-



OMS -

UE -



FL15A

-

NetAct

MME

NetAct15.5

-

SAE GW -

Additional hardware requirements This feature supports the: • •

Flexi Zone Micro/Pico BTS (including future versions such as the Enhanced and High Performance) Flexi Zone Indoor Pico BTS when functioning as a stand-alone eNB connecting to OMS/NetAct

Functional description

Issue: 01D

DN09185982

427



Functional overview This feature allows the Flexi Zone BTS to perform no-touch Plug and Play on un-trusted, non-operator owned backhaul such as enterprise and public backhaul deployments which is not supported by the existing Plug and Play functionality. For an overview of Flexi Zone Plug and Play auto connection, please see the figure: Overview Flexi Zone Plug and Play Auto Connection. The Flexi Zone small cell needs basic auto-connection parameters in order to establish connection with the operator’s Security Gateway (SeGW), Certificate Authority Server (CA Server), and Configuration Server (iOMS). Figure 46

Overview Flexi Zone Plug and Play Auto Connection Operator’s!Network DHCP

DNS

CA!Server

? Flexi!Zone Small!Cell

SeGW

OMS

NetAct iSON!Mgr

EPC

LTE2182: Enhanced Flexi Zone Plug and Play for Non-Operator Owned Backhaul (see blue line in the figure) • • • •

Parameters pre-configured in small cell Pre-stage FQDNs at warehouse or in factory Supports no-touch Plug & Play Release FDD/TD-LTE15A (LTE2182: Enhanced Flexi Zone Plug and Play for NonOperator Owned Backhaul)

Deployment scenarios Flexi Zone small cells are able to intelligently determine which auto connection method to utilize based on the deployment scenario and information made available providing the most dynamic approach to Plug and Play. LTE154: SON LTE BTS Auto Connectivity • • • •

Parameters obtained from DHCP server Includes Nokia-specific DHCP options Supports no-touch Plug and Play Release RL50FZ (LTE154: SON LTE BTS Auto Connectivity) - Legacy RL10 feature

LTE1058: Plug and Play Extensions • •

428

Parameters manually entered at small cell Utilize BTS Site Manager for entry at site

DN09185982

Issue: 01D


• •


Supports low-touch Plug and Play Release FDD/TD-LTE15A (LTE1058: Plug and Play Extensions)

Figure 47

Flexi Zone Plug and Play Auto-Connection

Power up

BTS commissioned?

Yes

Normal Startup

No

Auto connection parameters available?

Yes

TOLD LTE1058 Auto Connection

Yes

LEARN LTE154 Auto Connection

Yes

KNOW LTE2182 Auto Connection

No

Request parameters from DHCP server

Vendor specific parameters in DHCPOFFER?

No

LTE2182 parameters available?

FQDN format used with LTE2182: Enhanced Flexi Zone Plug and Play for Non-Operator Owned Backhaul

g

Note: This feature applies to both the outdoor (Flexi Zone Micro/Pico BTS) and indoor (Flexi Zone Indoor BTS) products, not to the Flexi Zone Controller architecture. The Flexi Zone BTS is pre-provisioned prior to shipment with the following operatorspecific transport information: • • • •

Issue: 01D

the fully qualified domain name (FQDN) or the IP address of the certificate authority (CA) server the port number of the CA-server the subject name for the CA-server the certification management protocol (CMP) directory (URL) on the CA-server

DN09185982

429


the FQDN(s) or the IP address(es) of the initial security gateway (required only if the operator's CA-server is only accessible through a security gateway) the FQDN(s) or the IP address(es) of the serving security gateway the FQDN(s) or IP address(es) of the initial iOMS the operator root certificate (required only if the operator's CA-server is only accessible through a security gateway). This information is required to be preserved during a reset (including config reset and factory reset). The operator has the ability to overwrite this information via the BTS Site Manager.

• • • •

g

Note: Difference between the initial security gateway and the serving security gateway •

•

g


The initial security gateway information must be specified if the operator's CAserver is behind a security gateway. If the operator's CA-server is accessible in the public domain, the initial security gateway must NOT be specified. The serving security gateway information must ALWAYS be specified, irrespective of the location of the CA-server. The operator can set the initial security gateway differently from the serving security gateway, if the operator intends to limit the access of the BTSs creating the IPSec tunnel using the vendor certificates with the initial security gateway. If the operator does not plan to limit the access of such BTSs (or plans to use other mechanisms to limit the access, for example, white lists), the initial security gateway and the serving security gateway can be set to the same values. Both of these must still be specified if the operator's CA-server is behind a security gateway.

Note: Primary and secondary FQDNs or IP addresses: The primary and secondary FQDNs or IP addresses have been provided to allow redundancy. If the primary device is not accessible, the secondary device should be used. The Flexi Zone BTSs that do not have this information pre-provisioned at shipment follow existing Plug and Play procedures (LTE154: SON LTE BTS Auto Connectivity and LTE720: SON LTE BTS Auto Configuration).. If the Flexi Zone BTS receives appropriate information via dynamic host configuration protocol (DHCP), it utilizes the existing Plug and Play procedures. Otherwise, if the Flexi Zone BTS does not receive the necessary information via DHCP, it bypasses the existing Plug and Play procedures and utilizes the modified procedures introduced with this feature to obtain an IP address from the local DHCP server and connects to the local DNS server to resolve the operator specific fully qualified domain names (FQDN) into IP addresses and connects to the operator's transport network. If an FQDN is provided for the OMS, the security gateway provides the IP address of the operator's internal DNS via IKEv2 configuration payload in order to resolve the FQDN. If the operator's security gateway does not support this function, an IP address is provisioned for the initial OMS in the Flexi Zone BTS at the factory. Once the Flexi Zone BTS has connected to the initial OMS, the remaining autoconnection flow remains unchanged as does the auto-configuration flow.

430

DN09185982

Issue: 01D



If more than one FQDN (primary and secondary) is provided for the initial security gateway or if more than one IP address is returned when the FQDN of the initial security gateway is resolved by the public DNS server, the Flexi Zone BTS will use the primary one to connect. If that is not successful, the Flexi Zone BTS will use the secondary one for the connection. A similar approach is applied when connecting to the serving security gateway and the initial iOMS. Use cases The following use cases are described: Use case 1a: CA-server accessible only in operator's private network AND the "initial security gateway" and the "serving security gateway" are the same Use case 1b: CA-server is accessible only in operator's private network AND the initial security gateway and the serving security gateway are different Use case 2: Plug and play deployment of FZM in non-operator owned backhaul when CA server resides in public network Use case 3: Creation / Modification of auto-connection parameters for non-operator owned (untrusted) backhaul Use case 4: Preservation of the pre-configured operator specific transport information for a configuration reset Use case 1a: CA-server accessible only in operator's private network AND the "initial security gateway" and the "serving security gateway" are the same Figure 48

Deployment Scenario 1a: CA-server accessible only in operator's private network AND the initial security gateway and the serving security gateway are the same DHCP

DNS

operator network

enterprise network

DNS

DHCP

CA

FlexiZoneBTS

enterprise transport network

Initialand serving security gateway

operator transport network FlexiZoneBTS

Internet

IOMS

public network

NetAct

FlexiZoneBTS DHCP

DNS

ExistingPlug&PlaySupport

LTE2182Plug&PlaySupport

Use case 1b: CA-server is accessible only in operator's private network AND the initial security gateway and the serving security gateway are different

Issue: 01D

DN09185982

431



The operator can limit access from the initial security gateway to the CA server and private DNS server (shown as a dotted red line). Figure 49

Deployment Scenario 1b: CA-server is accessible only in operator's private network AND the initial security gateway and the serving security gateway are different DHCP

DNS

operator network

enterprise network Initialsecurity gateway

FlexiZoneBTS


DNS

DHCP

CA

Serving security gateway


Internet

IOMS

public network

NetAct

FlexiZoneBTS DHCP

DNS



Pre-conditions • •

The eNB is physically installed in a non-operator owned backhaul. The eNB is pre-configured with the following "minimum" operator-specific transport information: – – – – – – – –

• • • •

the FQDN or the IP address of the primary initial security gateway (SeGW) the FQDN or the IP address of the primary serving SeGW the FQDN or the IP address of the CA-server the port number of the CA-server the subject name for the CA-server the CMP directory (URL) on the CA-server the FQDN or the IP address of the primary initial OMS the operator's root certificate

If the FQDNs need to be resolved, the corresponding IP address(es) at the DNS server(s) are specified. The eNB is pre-loaded with the RL15A software. The OMS is pre-configured with the HW serial number and/or the GPS coordinates for the BTS identification. The LTE2182: Enhanced Flexi Zone Plug and Play for Non-Operator Owned Backhaul feature flag has been enabled.

Description •

432

The eNB is powered up.

DN09185982

Issue: 01D


• •

• •

• • •

• •

• •


The eNB is assigned an IP address by the public/enterprise DHCP server, which also provides the public/enterprise DNS server's address(es). The eNB acquires the IP address of the initial SeGW (pre-configured on the eNB) through the public/enterprise DNS server. (This step is not required if the IP address of the initial SeGW is pre-configured on the eNB). The eNB establishes the IPSec tunnel to the initial SeGW using the vendor certificate. The eNB acquires the IP address of the certificate authority server by resolving the FQDN of the certificate authority server (pre-configured on the eNB) through the private DNS server. (This step is not required if the IP address of the certificate authority server is pre-configured on the eNB). The eNB performs the certificate enrolment and gets the operator's certificate from the CA-server. The eNB tears down the initial IPSec tunnel created using the vendor's certificate. The eNB acquires the IP address of the serving SeGW by resolving the FQDN of the SeGW (pre-configured on the eNB) through the public/enterprise DNS server. (This step is not required if the IP address of the serving SeGW is pre-configured on the eNB) The eNB establishes the IPSec tunnel to the serving SeGW using the operator certificate obtained from the CA-server. The eNB acquires the IP address of the initial iOMS by resolving the FQDN of the iOMS (pre-configured on the eNB) through the private DNS server. (This step is not required if the IP address of the initial iOMS is pre-configured on the eNB). The eNB establishes a connection to the initial iOMS. The identification server on the initial iOMS identifies the eNB based on the identification parameters (HW serial # or GPS coordinates) and provides the final iOMS address from where the eNB acquires the SW and configuration data as part of the auto-configuration.

Post-condition Once the auto-connection to the initial OMS is established, it is followed by the autoconfiguration procedure. Use case 2: Plug and play deployment of FZM in non-operator owned backhaul when CA server resides in public network

Issue: 01D

DN09185982

433


Figure 50


Deployment Scenario 2: CA-server accessible via the public network DHCP

DNS

CA

operator network

enterprise network

DNS

DHCP FlexiZoneBTS


Serving security gateway


Internet

IOMS

public network

NetAct

FlexiZoneBTS DHCP

DNS



Pre-conditions • •

The eNB is physically installed in an non-operator owned backhaul. The eNB is pre-configured with the following "minimum" operator-specific transport information: – – – – – –

• • • •

the FQDN or the IP address of the primary serving SeGW the FQDN or the IP address of the CA-server the port number of the CA-server the subject name of the CA-server the CMP directory (URL) on the CA-server the FQDN or the IP address of the primary initial OMS

If the FQDNs need to be resolved, the corresponding IP address(es) at the DNS server(s) are specified. The eNB is pre-loaded with the RL15A software. The OMS is pre-configured with the HW serial number and/or GPS coordinates for the BTS identification. The LTE2182: Enhanced Flexi Zone Plug and Play for Non-Operator Owned Backhaul feature flag has been enabled.

Description • • •

434

The eNB is powered up. The eNB is assigned an IP address by the public/enterprise DHCP server, which also provides the DNS server's address(es). The eNB acquires the IP address of the certificate authority server by resolving the FQDN of the certificate authority server (pre-configured on the eNB) through the public/enterprise DNS server. (This step is not required if the IP address of the certificate authority server is pre-configured on the eNB).

DN09185982

Issue: 01D


• •

• •

• •


The eNB performs the certificate enrolment and gets the operator certificate from the CA-server. The eNB acquires the IP address of the serving SeGW by resolving the FQDN of the SeGW (pre-configured on the eNB) through the public/enterprise DNS server. (This step is not required if the IP address of the SeGW is pre-configured on the eNB). The eNB creates the IPSec tunnel with the serving SeGW using the operator certificate obtained from the CA-server. The eNB acquires the IP address of the initial iOMS by resolving the FQDN of the iOMS (pre-configured on the eNB) through the private DNS server. (This step is not required if the IP address of the initial iOMS is pre-configured on the eNB. The eNB establishes a connection to the initial iOMS. The identification server on the initial iOMS identifies the eNB based on the identification parameters (HW serial # or GPS coordinates) and provides the final iOMS address from where the eNB acquires the SW and configuration data as part of the auto-configuration.

Post-condition Once the auto-connection to the initial OMS is established, it is followed by the autoconfiguration procedure. Use case 3: Creation / Modification of auto-connection parameters for nonoperator owned (untrusted) backhaul Pre-conditions • •

The BTS Site Manager is connected to the eNB. The eNB is in an un-commissioned state.


The operator uses the BTS Site Manager to launch the auto-connection user interface for the non-operator owned (untrusted) backhaul. The operator modifies some or all of the auto-connection parameters for the nonoperator owned (untrusted) backhaul. If the auto-connection parameters for the non-operator owned (untrusted) backhaul are not configured on the eNB, the information provided using BTSSM is used to create the LTE2182-config file on the eNB. The BTSSM has to ensure that all the mandatory information is specified in this case. It includes the following: – – – – – –

•

If the auto-connection parameters for the non-operator owned (untrusted) backhaul are already configured on the eNB, the information provided using the BTSSM is used to modify the LTE2182-config file on the eNB. The BTSSM has to ensure that once the modification is done, at least the following set of information is present: –

Issue: 01D

the FQDN or the IP address of the primary serving SeGW the FQDN or the IP address of the CA-server the port number of the CA-server the subject name for the CA-server the CMP directory (URL) on the CA-server the FQDN or the IP address of the primary initial OMS

the FQDN or the IP address of the primary serving SeGW

DN09185982

435


– – – – –


the FQDN or the IP address of the CA-server the port number of the CA-server the subject name of the CA-server the CMP directory (URL) on the CA-server the FQDN or the IP address of the primary initial OMS

Post-condition The eNB has updated the auto-connection parameters for the non-operator owned (untrusted) backhaul as specified by the operator using the BTSSM. Use case 4: Preservation of the pre-configured operator specific transport information for a configuration reset Pre-conditions • •

The eNB is in service. The BTSSM is connected to the eNB.


The user triggers the configuration reset of the eNB. The eNB initializes as requested and removes the configuration data. The eNB preserves the auto-connection parameters for the non-operator owned (untrusted) backhaul.

Post-condition The operator-specific transport information is not lost on the configuration reset. System impact Interdependencies between features The following features impact LTE2182: Enhanced Flexi Zone Plug and Play for NonOperator Owned Backhaul: •

•

LTE2002: FWHG Flexi Zone Indoor Pico BTS 2600 The Flexi Zone indoor access point extends the zone-based architecture to include the indoor BTS solutions and provides a one-stop solution for operators, both outdoor and indoor needs. The FZ indoor utilizes the same "Flexi" software and the feature set to seamlessly integrate the indoor small cell solution into the operator heterogeneous networks offering LTE and WiFi in the same box. The operators can enjoy identical features available in FZ outdoor micro such as Plug and Play, common O&M as Macro/FZM, and the software upgrade to the LTEadvanced support. LTE2182 relies on LTE2002 for deployment of FZMs in an indoor setup. LTE1058: Plug & Play Extensions The LTE1058: Plug & Play Extensions feature provides Plug and Play without the need for a DHCP server and supports the reset of an already commissioned BTS to "not commissioned" to re-do commissioning. In addition, more detailed Plug and Play reports are provided.


436

DN09185982

Issue: 01D



This feature has no impact on interfaces. Impact on network management tools The feature impacts network management tools as follows: •

The BTSSM is required to provide the functionality to overwrite the auto-connectioninformation configured at the factory. This requires the ability to deliver the autoconnection parameters from the BTSSM to BTS which is overwriting the factory configured information.

Impact on system performance and capacity This feature has no impact on system performance or capacity. Management data Parameters Table 258


Abbreviated name

Activate Autoconnection in Non-Operator Owned Network

actACNonOpBackhaul

Managed object IPNO

Sales information Table 259: Sales information presents the sales information for the LTE2182: Enhanced Flexi Zone Plug and Play for Non-Operator Owned Backhaul feature. Table 259

Sales information

BSW/ASW


BSW

-


5.24 LTE2195: Integrated O&M for Ruckus Wi-Fi 5.24.1 Description of LTE2195: Integrated O&M for Ruckus Wi-Fi Introduction to the feature The LTE2195: Integrated O&M for Ruckus Wi-Fi feature integrates the operability solution for the Ruckus Wi-Fi access into the Nokia NetAct platform for both fault management (FM) and performance management (PM). Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The LTE2195: Integrated O&M for Ruckus Wi-Fi feature simplifies the operability for small cells by integrating operability into a single element management system (EMS) that allows both long term evolution (LTE) and Wi-Fi FM and PM to be viewable on NetAct.

Issue: 01D

DN09185982

437






-




OMS -

UE -


NetAct NetAct 15.5


MME -

SAE GW -

Additional hardware requirements This feature requires the following hardware: • •

stand-alone Ruckus Wi-Fi access points (APs) Ruckus Wi-Fi integrated in the Flexi Zone base transceiver station (BTS) (both Flexi Zone Micro or Pico BTS and Flexi Zone Indoor BTS)

Functional description Functional overview The LTE2195: Integrated O&M for Ruckus Wi-Fi feature allows NetAct to receive and process faults, alarms, and counters from the Ruckus SmartCell Gateway (SCG). The received and processed faults or alarms and counters are displayed on the integrated NetAct applications for both stand-alone Ruckus Wi-Fi access points and integrated access points in Flexi Zone Micro or Pico Enhanced BTS (outdoor) and Flexi Zone Indoor Pico BTS (indoor). The Ruckus SCG forwards the faults and alarms to NetAct via Simple Network Management Protocol (SNMP). The faults and alarms are viewable on NetAct applications together with the other faults and alarms, including LTE faults and alarms.

g

Note: Additional alarm enrichment, filtering, and correlation on NetAct are outside the scope of this feature. The Ruckus SCG forwards the counters to NetAct via file transfer protocol (FTP). The forwarded counters come in the form of a .csv file. The counters are viewable on NetAct applications together with the other counters, including LTE counters.

g

Note: Additional counter enrichment and KPI calculation on NetAct are outside the scope of this feature. 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.

438

DN09185982

Issue: 01D



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 Table 261: Related Alarms lists the related alarms with this feature Table 261

Related Alarms Alarm ID

Issue: 01D

Alarm name

1000000807

Cluster upgrade failed

1000000813

Cluster node shut down

1000000950

CPU threshold exceeded

1000000951

Memory threshold exceeded

1000000951

Disk usage threshold exceeded

1000000960

License threshold exceeded

1000000306

AP deleted

1000000303

AP disconnected

1000000302

AP rebooted by system

1000000303

AP disconnected

1000000101

AP rejected

1000000102

AP configuration update failed

1000000104

AP swap model mismatched

1000000105

AP pre-provision model mismatched

1000000107

AP firmware update failed

1000000108

AP WLAN oversubscribed

1000000308

AP cable modem interface down

1000000115

AP join zone failed

1000000701

No LS responses

1000000702

LS authentication failure

1000000704

AP failed to connect to LS

1000000614

AP SoftGRE gateway not reachable

1000000501

Data plane configuration update failed

1000000503

Data plane disconnected

1000000504

Data plane physical interface down

1000000510

Data plane rebooted

DN09185982

439


Table 261


Related Alarms (Cont.) Alarm ID

440

Alarm name

1000000516

Data plane packet pool is under low water mark

1000000517

Data plane packet pool is under critical low water mark

1000000519

Data plane core dead

1000000801

New node failed to join

1000000802

Node removal failed

1000000803

Node out of service

1000000804

Cluster in maintenance state

1000000805

Cluster backup failed

1000000806

Cluster restore failed

1000000808

Cluster application stopped

1000000809

Node bond interface down

1000000810

Node physical interface down

1000000862

Configuration backup failed

1000000864

Configuration restore failed

1000000843

Cluster out of service

1000000901

IPMI Voltage

1000000902

IPMI baseboard temperature

1000000903

IPMI front panel temperature

1000000904

IPMI IOH temperature

1000000905

IPMI processor memory temperature

1000000906

IPMI power supply temperature

1000000907

IPMI processor temperature

1000000908

IPMI hot swap backplane temperature

1000000909

IPMI fan

1000000910

IPMI power supply

1000000911

IPMI current output

1000000912

IPMI fan status

1000000913

IPMI power supply status

1000000914

IPMI disk drive status

1000000721

No LS responses

1000000722

LS authentication failure

1000000724

SCG failed to connect to LS

1000001001

Process restart

DN09185982

Issue: 01D


Table 261



Issue: 01D

Alarm name

1000001002

Service unavailable

1000001003

Keepalive failure

1000001006

Resource unavailable

1000001016

HIP failed over

1000001202

DP disconnected

1000001210

GGSN restarted

1000001211

GGSN not reachable

1000001215

GGSN not resolved

1000001601

Authentication server not reachable

1000001602

Accounting server not reachable

1000001610

Connection to CGF failed

1000001614

CDR transfer failed

1000001615

CDR generation failed

1000001618

Destination not reachable

1000001623

App server down

1000001624

App server inactive

1000001626

Association establishment failed

1000001627

Association down

1000001636

Outbound routing failure

1000001637

Did allocation failure

1000001950

PDNGW could not be resolved

1000001952

PDNGW version not supported

1000001953

Associated PDNGW down

1000001954

Create session response failed

1000001955

Decode failed

1000001956

Modify bearer response failed

1000001957

Delete session response failed

1000001958

Delete bearer request failed

1000001959

Update bearer request failed

1000001960

CGF server not configured

1000001242

TTG session critical threshold

1000001243

TTG session license exhausted

1000001901

AP accounting message mandatory parameter missing

DN09185982

441


Table 261



g g

Alarm name

1000001904

AP accounting message decode failed

1000001910

AP account message drop while no accounting start message

1000001911

Unauthorized CoA/DM message dropped

1000001302

Rate limit for TOR surpassed

1000005001

Process initiated

1000005002

PMIPv6 unavailable

1000005003

Memory allocation failed

1000005004

Config update failed

1000005006

LMA ICMP unreachable

1000005008

LMA failed over

1000005010

Binding failed

1000005102

DHCP connection lost

1000000662

AP secure gateway association failure

1000000661

AP is disconnected from secure gateway

Note: Alarm ID is represented on NetAct as Alarm Number. Note: For more information about the alarms, see Ruckus documentation. Measurements and counters Table 262: Related counters lists the related counters related with this feature Table 262

Related counters

Counter name

Measurement

Total airtime of channel utilization in a period of time

442

Measurement group

ZSTAT

statsZoneHour

Minimum number of ZSTAT connected clients (concurrent) during the period

statsZoneHour

Total number of data frames received during the period

ZSTAT

statsZoneHour

Transmit data rate expressed in kilobits per second for the period

ZSTAT

statsZoneHour

Receive data rate expressed in kilobits per second for the period

ZSTAT

statsZoneHour

Number of newly associated clients during the period

ZSTAT

statsZoneHour

DN09185982

Issue: 01D


Table 262


Related counters (Cont.)

Counter name

Measurement

Total number of bytes transmitted during the period

ZSTAT

Total number of bytes received during the period

Issue: 01D

Measurement group statsZoneHour statsZoneHour

Total number of data frames transmitted during the period

ZSTAT

statsZoneHour

Computed based on the Up / Down events from the perspective of the AP,representing the percentage of time during the interval that the AP is considered to be up

ZSTAT

statsZoneHour

Average number of connected ZSTAT clients (concurrent) during the period

statsZoneHour

Number of failed associated clients during the period

ZSTAT

statsZoneHour

Maximum number of ZSTAT connected clients (concurrent) during the period

statsZoneHour


APSTAT

statsAPHour

Minimum number of APSTAT connected clients (concurrent) during the period

statsAPHour


APSTAT

statsAPHour


APSTAT

statsAPHour


APSTAT

statsAPHour


APSTAT

statsAPHour


APSTAT

statsAPHour


APSTAT

statsAPHour

Computed based on the Up / Down events from the perspective of the AP,representing the percentage of time during the interval that the AP is considered to be up

APSTAT

statsAPHour

DN09185982

443


Table 262



Counter name

444

Measurement

Measurement group

Average number of connected APSTAT clients (concurrent) during the period

statsAPHour


APSTAT

statsAPHour


APSTAT

statsAPHour

Maximum number of APSTAT connected clients (concurrent) during the period

statsAPHour


APRAD

statsAPTimeRadioHour

Minimum number of APRAD connected clients (concurrent) during the period


Busy airtime of channel utilization in a period of time

APRAD



APRAD



APRAD



APRAD



APRAD


Total number of bytes received during the period"

APRAD


Total receiving airtime of channel utilization in a period of time

APRAD


Average number of connected APRAD clients (concurrent) during the period


Total transmitting airtime of channel utilization in a period of time

APRAD



APRAD


Maximum number of APRAD connected clients (concurrent) during the period


Number of PHY errors during the period

APRAD



ZNRAD

statsZoneTimeRadioHour

DN09185982

Issue: 01D


Table 262



Counter name

Issue: 01D

Measurement

Measurement group

Minimum number of ZNRAD connected clients (concurrent) during the period


Busy airtime of channel utilization in a period of time

ZNRAD



ZNRAD



ZNRAD



ZNRAD



ZNRAD



ZNRAD


Total receiving airtime of channel utilization in a period of time

ZNRAD


Average number of connected ZNRAD clients (concurrent) during the period


Total transmitting airtime of channel utilization in a period of time

ZNRAD



ZNRAD


Maximum number of ZNRAD connected clients (concurrent) during the period


Number of PHY errors during the period


ZNRAD

Minimum number of APWLAN connected clients (concurrent) during the period

statsAPTimeWlanHour

Transmitted failed package

APWLAN

statsAPTimeWlanHour


APWLAN

statsAPTimeWlanHour


APWLAN

statsAPTimeWlanHour


APWLAN

statsAPTimeWlanHour


APWLAN

statsAPTimeWlanHour


APWLAN

statsAPTimeWlanHour

DN09185982

445


Table 262



Counter name

446

Measurement

Measurement group


APWLAN

statsAPTimeWlanHour

Represents the WLAN in the SCG system

APWLAN

statsAPTimeWlanHour


APWLAN

statsAPTimeWlanHour

Average number of connected APWLAN clients (concurrent) during the period

statsAPTimeWlanHour


APWLAN

statsAPTimeWlanHour

Maximum number of APWLAN connected clients (concurrent) during the period

statsAPTimeWlanHour


ZNWLAN

statsZoneTimeWlanHour

Minimum number of ZNWLAN connected clients (concurrent) during the period



ZNWLAN



ZNWLAN



ZNWLAN


Total number of management frames received during the period

ZNWLAN



ZNWLAN


Represents the WLAN in the SCG system

ZNWLAN



ZNWLAN


Average number of connected ZNWLAN clients (concurrent) during the period


Total number of data bytes transmitt ed during the period

ZNWLAN


Maximum number of ZNWLAN connected clients (concurrent) during the period


Total number of management bytes received during the period


ZNWLAN

DN09185982

Issue: 01D


Table 262


Counter name

Issue: 01D


Measurement

Measurement group

Total number of data bytes received during the period

ZNWLAN



ZNWLAN



ZNWLAN



ZNWLAN


Total number of management frames transmitted during the period

ZNWLAN

sstatsZoneTimeWlanHourtats ZoneTimeWlanHour

Total number of management bytes transmitted during the period

ZNWLAN

statsZoneTimeWlanHourstats ZoneTimeWlanHour

ap

ZNWLAN

sstatsZostatsZoneTimeWlanH ourneTimeWlanHourtatsZone TimeWlanHour


ZNWLAN


Radio channel that the AP is using

ZNWLAN


Received traffic bytes on bond0

CTRPLN

statsCBladeSysMonHour

Minimum transmitted throughput(bps) on eth1

CTRPLN


transmitted packet number on eth1

CTRPLN


Transmitted traffic bytes on eth2

CTRPLN


Received throughput(bps) on eth0

CTRPLN


Minimum transmitted throughput(bps) on bond1

CTRPLN



CTRPLN


Maximum received throughput(bps) on bond1

CTRPLN


transmitted throughput(bps) on eth0

CTRPLN



CTRPLN


Maximum transmitted throughput(bps) on eth1

CTRPLN



CTRPLN


DN09185982

447


Table 262



Counter name

448

Measurement

Measurement group

Droped received packet on bond1

CTRPLN


Minimum received throughput(bps) on eth3

CTRPLN



CTRPLN



CTRPLN


Droped transmitted packet on eth5

CTRPLN



CTRPLN


transmitted packet number on eth0

CTRPLN


Maximum received throughput(bps) on eth4

CTRPLN


Received packet number on eth5

CTRPLN



CTRPLN


Received throughput(bps) on bond2

CTRPLN


Maximum free disk space

CTRPLN


Droped received packet on eth4

CTRPLN


Minimum free disk space

CTRPLN



CTRPLN



CTRPLN


Maximum Memory Percentage CTRPLN



CTRPLN


Minimum Memory Percentage

CTRPLN


Transmitted packet number on CTRPLN eth3


Transmitted traffic Bytes on eth3

CTRPLN


Transmitted traffic Bytes on bond0

CTRPLN



CTRPLN



CTRPLN


DN09185982

Issue: 01D


Table 262


Counter name

Issue: 01D


Measurement

Measurement group


CTRPLN



CTRPLN


Transmitted throughput(bps) on eth4

CTRPLN



CTRPLN



CTRPLN


Transmitted packet number on CTRPLN bond1



CTRPLN



CTRPLN



CTRPLN


Free disk volume

CTRPLN



CTRPLN


Maximum transmitted throughput(bps) on bond0

CTRPLN


Transmitted throughput(bps) on bond0

CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN


Droped transmitted packet on bond0

CTRPLN



CTRPLN



CTRPLN



CTRPLN


Maxium total disk volume

CTRPLN


Mininum total disk volume

CTRPLN


DN09185982

449


Table 262



Counter name

450

Measurement

Measurement group


CTRPLN


Total disk volume

CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN




Received traffic bytes on eth3

CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN





CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN


Minimum CPU usagage percentage

CTRPLN


DN09185982

Issue: 01D


Table 262


Counter name

Issue: 01D


Measurement

Measurement group


CTRPLN



CTRPLN



CTRPLN



CTRPLN


MEMORY usage percent

CTRPLN



CTRPLN





CTRPLN





CTRPLN



CTRPLN


CPU usage percent

CTRPLN



CTRPLN


Received packet number on bond1

CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN


Maximum CPU usagage percentage

CTRPLN





CTRPLN



CTRPLN



CTRPLN



CTRPLN


DN09185982

451


Table 262



Counter name

452

Measurement

Measurement group


CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN



CTRPLN


transmitted rate when datablade generates this report

DATPLN

dpEthPortStatistics

received rate when datablade generates this report

DATPLN

dpEthPortStatistics

incremental transmitted packet counts during this 15 minutes

DATPLN

dpEthPortStatistics

incremental received packet counts during this 15 minutes

DATPLN

dpEthPortStatistics

incremental transmitted drop counts during this 15 minutes

DATPLN

dpEthPortStatistics

incremental received drop counts during this 15 minutes

DATPLN

dpEthPortStatistics

incremental transmitted byte counts during this 15 minutes

DATPLN

dpEthPortStatistics

incremental received byte counts during this 15 minutes

DATPLN

dpEthPortStatistics

DN09185982

Issue: 01D


Table 262


Counter name

g

Issue: 01D


Measurement

Measurement group

TX packet count of GRE interface

STATGRE

statsSoftGREGatewayHourly

TX byte count of GRE interface

STATGRE


RX packet count of GRE interface

STATGRE


RX byte count of GRE interface

STATGRE


TX Error packet count of GRE interface

STATGRE


RX Error packet count of GRE STATGRE interface


TX Drop packet count of GRE interface

STATGRE


RX Drop packet count of GRE interface

STATGRE


Counter of oversize packets

STATGRE


Counter of ICMP

STATGRE


Counter of non-reply ICMP

STATGRE


Counter of disconnected

STATGRE


Zone UUID

STATTUN

statsAPSoftGRETunnel

TX packet count of GRE interface

STATTUN


TX byte count of GRE interface

STATTUN


RX packet count of GRE interface

STATTUN


RX byte count of GRE interface

STATTUN


TX Error packet count of GRE

STATTUN


RX Error packet count of GRE STATTUN interface


TX Drop packet count of GRE interface

STATTUN


rxDropPkts

STATTUN


Counter of oversize packets

STATTUN


Counter of ICMP

STATTUN


Counter of non-reply ICMP

STATTUN


Counter of disconnected

STATTUN


Note: For more information about measurements and counters, see Ruckus documentation.

DN09185982

453



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 263

Sales information

BSW/ASW


ASW NetAct

NetAct


5.25 LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I 5.25.1 Description of LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I Introduction to the feature The LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I feature enables grouping Flexi Zone Access Points (FZAP) managed under a Flexi Zone Controller (FZC) into multiple enterprise networks, using a shared backhaul. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits Lower deployment costs by re-purposing existing network infrastructure. Possibility to define up to nine functional FZAP enterprise groups.

• •



System release FDD-LTE15A



TDD-LTE15A OMS -

UE -


FLC15A

TL15A

TLC15A

NetAct -


MME -

SAE GW -

Additional hardware requirements

454

DN09185982

Issue: 01D



This feature requires the introduction of a L3 router into the backhaul topology. Functional description Functional overview The LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I feature provides the Flexi Zone Controller and all intermediate Layer-2 and Layer-3 devices with the necessary configuration to support shared backhaul under existing enterprise networks. Figure 51: Shared backhaul deployment shows a typical deployment, in which FZAPs are added in parallel in existing enterprises. The feature enables the definition of up to nine FZAP groups. Figure 51

Shared backhaul deployment

Nokiacabling

NokiaFZAP

NokiaL3Router

Enterprisecabling

Enterprisedevice

EnterpriseL2switch

NokiaSwitch

Multi-subnet enterprisecabling (Backbone+South-boundinterfaceZ1) LTE2346!ENABLED

LTE2346!DISABLED

Enterprise1Network FZAP

Subnet “white” 2

Enterprise1Network FZAP

FZAP FZAP

FZAP FZAP

Aggregated L2 Switch

L2 Switches

Subnet “gray” 2 Enterprise0Network

Aggregated L2 Switch

Subnet “gray” 1

Wi-Fi Traffic WANEnterprise0


LTE!CORE

Enterprise0 networktopology

Northbound interface



LTE Traffic


LTE!CORE FZC

FZAP FZAP

L2 Switches

L3!Router


South-boundinterface Z1

FZAP

FZAP FZAP

Backbone

FZAP

Backbone+South-boundinterface Z1

Subnet “white” 1

Enterprise0Network


LTE Traffic Northbound interface

FZC

Switch

LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I is a licensed feature that is enabled/disabled with a feature flag via the Structured Command Line Interface (SCLI). This solution provides: • •

Issue: 01D

easy deployment of FZAPs in new locations existing hardware and cable reuse

DN09185982

455


• • • •


no physical changes to the private networks no disruption to WAN traffic common VLAN for all FZAPs within an enterprise group DHCP hosting within the FZC, assigning IPs to FZAPs across different Subnets

The successful configuration of the LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I includes the following requirements: • • •

The operator manages/owns the L3 router and its configuration. All FZAPs are connected to the aggregation switch via Ethernet cabling. The L3 router must not be configured with any of these: – –

• • • •

Network Address Translation (NAT) Network Address and Port Translation (NAPT)

The FZAPs must be deployed within unique subnets across the enterprise VLANs. The use of IPSec is mandatory within the Zone deployment. The outgoing traffic from FZAP via L3 router needs to go through the FZC southbound (SB) interface. L2/L3 markings must be configured and honored by the intermediate zone devices.

System impact Interdependencies between features The following features have to be enabled before activation of the LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I: • •

LTE1996: Flexi Zone Controller Application LTE2017: IPSec Support for Flexi Zone Controller

The LTE2346 feature can be understood as an extension of the FZC Z1 backhaul capability provided in feature LTE1996. There are no features whose functionality is affected by LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I. The functionality impact of this feature is limited to the FZC. From the FZAP point of view this feature does not result in any change. Impact on interfaces This feature impacts the backhaul configuration for the Z1 interface between FZC and FZAPs. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity The establishment of an enterprise typically adds one or two additional hops for the L3 router and the L2 switch. There may be more hops added, depending upon the operator’s deployment environment. The additional delay introduced by those hops will have a negligible impact on the RAN level system performance.

456

DN09185982

Issue: 01D



The overall capacity of the FZC and its associated FZAPs is affected by the amount of bandwidth available for the Z1 backhaul. Operators are expected to deploy 10 Gbps Ethernet links. Operator deploying 1 Gbps Ethernet links will experience reduced overall throughputs for the FZAPs. Management data Alarms There are no new alarms related to this feature. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Sales information Table 265

Sales information

BSW/ASW ASW



5.25.2 Activating and configuring LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I Before you start All commands supporting the LTE2346 feature are performed via the FxP’s SCLI interface. No commands can be initiated via NetAct. When the Shared Backhaul feature is enabled, the Flexi Zone Controller allows the definition of up to nine additional Enterprises. The Enterprise that is associated with the base LTE1996/LTE2203 functionality, Enterprise 0, is always present. Configuration of Enterprise 0 is outside of the scope of this document. The definition of an Enterprise includes: 1. Enterprise Name (Mandatory) The name can be up to 15 characters in length and must be unique from the other Enterprises. Enterprise 0 has the fixed name of “Base”. 2. Router IP Address (Mandatory) Enterprises must be defined with unique IP subnets that do not overlap with other IP address assignments within the FZC or for other Enterprises supported by the FZC. 3. IP Subnet Mask (Mandatory) 4. Starting IP Address of Allocation Range (Optional; defaults to first valid host IP in the IP subnet) 5. Ending IP Address of Allocation Range (Optional; defaults to last valid host IP in the IP subnet)

Issue: 01D

DN09185982

457



6. MTU Size (Optional; range 576-1644 octets, defaults to 1500 bytes) An Enterprise is based on a separate IP address subnet that applies to FZAPs that are physically connected to the routing/switching hardware that defines the shared backhaul Enterprise. The following features need to be activated/configured before activation of the LTE2346: Flexi Zone Controller Shared Backhaul Support- Phase I: • •

LTE1996: Flexi Zone Controller Application LTE2017: IPsec Support for Flexi Zone Controller

IPsec must be enabled on the south bound Z1 interface prior to the activation of LTE2346. Refer to the LTE2017: IPsec Support for Flexi Zone Controlle activation instructions for more information on enabling IPsec protection. Procedure 1

Access the FZC SCLI shell

2

Verify the state of the LTE2346 feature flag, FZCPAR-sharedZ1Backhaul

show flexizone shared-backhaul state Step result root@FCPU-0 [FZCP_199] > show flexizone shared-backhaul state Shared backhaul state: OFF

3

Enable the LTE2346 feature

set flexizone shared-backhaul state L3 route-ip 196.169.250.3 This sets up the flag to state L3 and establishes the route-ip as the default gateway for the controller southbound interface: 196.169.250.3 4

Verify the state of the LTE2346 feature flag FZCPAR-sharedZ1Backhaul and the GW router IP address

show flexizone shared-backhaul state root@FCPU-0 [FZCP_199] > show flexizone shared-backhaul state Shared backhaul state: L3 L3 route IP: 192.169.250.3

5

Add shared backhaul Enterprise

add flexizone shared-backhaul ent-name Enterprise1 gw-ip 241.241.1.1 subnet-mask 24 allocation-start 241.241.1.10 allocation-end 241.241.241.200 mtu 1500

458

DN09185982

Issue: 01D



This feeds Enterprise1 as example name, gw-ip corresponds to the default AP northbound gateway, and the maximum transmission unit (mtu) corresponds to the default Ethernet value of 1500.

g

Note: Adding an Enterprise may result in resets of FZAPs in other shared backhaul Enterprises, due to the reconfiguration of the IPSec policies.

6

Verify the addition of shared backhaul Enterprise

show flexizone shared-backhaul enterprise root@FCPU-0 [FZCP_199] > show ID Name Subnet end MTU -- ----------- ------------------ ---0 Base 251.251.0.0/24 251.251.251.200 1500 1 Enterprise1 241.241.0.0/24 241.241.241.200 1500

7

flexizone shared-backhaul enterprise Gateway IP Allocation start Allocation ----------- ---------------- ---------251.251.1.1 251.251.1.10 241.241.1.1 241.241.1.10

Save configuration snapshot

save snapshot

Result Shared backhaul support is now enabled.

5.25.3 Deactivating LTE2346: Flexi Zone Controller Shared Backhaul Support - Phase I Before you start 1. Shared backhaul is enabled 2. IPSec is active on south bound interface The disabling of the Shared Backhaul feature can only be done through the FxP SCLI and not by NetAct.

Issue: 01D

DN09185982

459


•


Deactivating an individual Enterprise: Sub-steps 1


2

Remove the desired enterprise

delete flexizone shared-backhaul enterprise ent-name Step example

delete flexizone shared-backhaul enterprise ent-name Enterprise1 This disables the example enterprise Enterprise1

3

Verify removal of shared backhaul Enterprise

show flexizone shared-backhaul enterprise Step result root@FCPU-0 [FZCP_199] > show flexizone shared-backhaul enterprise ID Name Subnet Gateway IP Allocation start Allocation end MTU -- ----- -------------- ----------- ---------------- -------------- ---0 Base 251.251.0.0/24 251.251.1.1 251.251.1.10 251.251.251.200 1500

•

Completely deactivating the LTE2346 Feature Note that disabling the LTE2346 feature deletes the configuration of all Enterprises previously defined. Sub-steps 1


2

Disable the feature by setting the value of the LTE2346 feature flag, FZCPAR-sharedZ1Backhaul to OFF

set flexizone shared-backhaul state OFF 3

Verify the state of the LTE2346 feature flag, FZCPAR-sharedZ1Backhaul

show flexizone shared-backhaul state

460

DN09185982

Issue: 01D



Step result root@FCPU-0 [FZCP_199] > show flexizone shared-backhaul state Shared backhaul state: OFF

•

Save configuration snapshot

save snapshot

5.26 LTE2548: BTS EM Support for RHEL 7.1 5.26.1 Description of LTE2548: BTS EM Support for RHEL 7.1 Introduction to the feature The LTE2548: BTS EM Support for RHEL 7.1 feature introduces support for the Red Hat Enterprise Linux 7.1. (RHEL 7.1.) operating system (OS). This support is needed for remote BTS EM sessions from NetAct. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits • •

support for Linux RHEL 7.1 in BTS Site Manager form FL-15A and TL-15A onwards stability of remote BTS EM sessions from NetAct



System release FL-LTE 15A

Flexi Multiradio BTS Not supported

Flexi Zone Controller Not applicable

Flexi Multiradio 10 BTS Not supported

OMS -


UE -

-

-

NetAct 16.2


MME -

SAE GW -


Issue: 01D

DN09185982

461



The Red Hat Enterprise Linux 7.1. operating system (RHEL 7.1 OS) belongs to a generation of a comprehensive suite of operating systems, designed for mission-critical enterprise computing and certified by top enterprise software and hardware vendors. The RHEL 7.1 OS offers improved development and deployment tools, enhanced interoperability and manageability, and additional security and performance features. This OS provides methods for consistent and predictable naming of network devices. Newly added features change the name of network interfaces on a system in order to make locating and differentiating of the interfaces easier. From a performance perspective, RHEL 7.1 OS supports higher processor and memory limits as well as additional features to improve the performance of applications and virtual machines, especially those running memory-intensive workloads. The LTE BTS EM SWs need to be able to run on RHEL 7.1 OS because NetAct 16.2 will not support RHEL 6.x. The support is needed for remote BTS EM sessions from NetAct. The purpose is to exploit the new features available in the newer version of the OS for the benefit of Nokia products. It should be simple and easy to enable features of the OS that can be easily exploited by the Applications. To find the installation guide for the BTS Site Manager, go to the Install and Commission, Commissioning Flexi Multiradio BTS LTE, Chapter 2 Installing BTS Site Manager document. 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. BTS faults and reported alarms There are no BTS faults and reported 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

462

DN09185982

Issue: 01D



There are no parameters related to this feature. Sales information Table 267

Sales information

BSW/ASW BSW

Issue: 01D


DN09185982

Activated by default no

463

Descriptions of BTS site solution features


6 Descriptions of BTS site solution features 6.1 LTE1725: FRME Flexi RF Module 6-Pipe 800 240W 6.1.1 Description of LTE1725: FRME Flexi RF Module 6-Pipe 800 240W Introduction to the feature The LTE1725: FRME Flexi RF Module 6-Pipe 800 240W feature is based on Flexi RF HW Rel.3 and common 800 MHz design blocks. FRME has six power amplifiers, thanks to which it supports one, two, or three sectors with up to 40+40 W 2TX MIMO output power at the BTS antenna connectors. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • • • • • • • • •

the most cost-efficient as well as size- and weight-optimized three-sector 2TX MIMO BTS site industry leading RF integration level three-sector 2TX MIMO RF in one outdoor IP65 box ability to be used as a feederless site with one DC and 1...2 optical cables ability to build a 3-sector 2TX div and 2TX MIMO BTS with one three-sector RF Module only one three-sector module being more cost effective than three Remote Radio Heads (RRH) in feederless installations 1/3 of DC and 2/3 of optical cabling compared to three-sector site with RRHs easy outdoor installation readiness to support one sector 4x40 W 4TX MIMO with 4RX





Flexi Zone Controller Not supported

OMS -


Not supported

UE 3GPP R8


NetAct -

Flexi Zone Access Point Not supported

MME -

SAE GW -


464

DN09185982

Issue: 01D



This feature requires no new or additional hardware. Functional description Functional overview Table 269

FRME functional specification Property

Value

Output power

6x40 W

MIMO

2TX

Outdoor installation

Yes

SW supported technology

FDD-LTE

TX frequency range

791 - 811 MHz

RX frequency range

832 - 862 MHz

DL instantaneous bandwidth

20 MHz

UL instantaneous bandwidth

30 MHz

DL filter bandwidth

20 MHz

UL filter bandwidth

30 MHz

For more details, see . System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces 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

Issue: 01D

DN09185982

465


Table 270


Sales information

BSW/ASW


BSW

-


6.2 LTE1829: Inter eNB RF sharing 6.2.1 Description of LTE1829: Inter eNB RF sharing Introduction to the feature LTE1829: Inter eNB RF sharing feature allows operators to share common radio modules with two independent LTE networks that are made up of two system modules (SMs). Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • • •

Support for a special mode of multi operator networks (MORAN) configurations. Hardware resources shared by two operators. Shared RF modules, cabling and antennas while still having full access to the dedicated baseband and completely separated S1 and X2 interfaces.



System release FDDLTE15A



OMS -


UE

Flexi Zone Micro BTS Not supported

NetAct

Not applicable -


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview This feature enables the support of configurations where two system modules (making up two independent LTE networks) share common radio modules.

466

DN09185982

Issue: 01D



Support of LTE FDD multi operator network with dedicated system modules for each operator: • • •

•

•

•

Both operator's SMs (optionally equipped with extension cards) are co-located. One SM is configured as the Radio/Link Master for the shared RF modules, the other one as the Slave. Both SMs are connected by one RP3 optical link, like in RF sharing configurations (LTE447, LTE435). Beside port 6 on FSMF also one optical port on FBBA/C can be used (port 3 on FBBC). Transport interfaces for each operator are separate. They can be combined into one physical interface by LTE649 QoS aware Ethernet Switching. Operators can use their own security gateway for IPsec. Both SMs are managed by a single NetAct system. Both SMs are managed by their own dedicated BTSSM, that is, there are two BTSSMs, one per operator. There is no restriction obliging both SMs to be connected to the same iOMS although this is be the expected configuration. Each SM connects to shared radio module(s) via one (or more) optical 3 or 6 Gbit/s optical interfaces.

The Radio Units are shared between two operators: • •

•

Issue: 01D

Each shared RF unit supports one LTE carrier per sector per operator. For each operator, a dedicated spectrum and a dedicated output power is assigned (with the exception of Rel2.1 radios where only equal power levels between carriers are supported). More details about supported configurations can be found in the Creating LTE Configurations and LTE Base Stations Supported Configurations documents.

DN09185982

467


Figure 52

RF Sharing with dedicated Flexi System Modules

FlexiMultiradioUnit

X2 S1

Dedicatedto Operator A 3*LTE5/10/15/20MHz.

LTESM

X2 S1


SharedRadio FlexiMultiradioUnit

Operator A 3*LTE5/10/15/20 MHzz

FlexiMultiradioUnit

OperatorB 3*LTE5/10/15/20Mhzz

LTESM FlexiMultiradioUnit

Dedicatedto OperatorB 3*LTE5/10/15/20MHz.

System impact Interdependencies between features Preconditions for LTE1829: Inter eNB RF sharing are as follows: • •

LTE1710: Sync Hub Direct Forwarding LTE1745: Up to 12 optical RF ports for high capacity BTS configurations

Feature LTE1829: Inter eNB RF sharing cannot be concurrently used with features: • • •

LTE447: SW support for RF sharing GSM-LTE LTE435: LTE RF sharing WCDMA-LTE LTE977: RF chaining

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.

468

DN09185982

Issue: 01D


f


Configuration of the same E-UTRA absolute radio frequency channel number causes severe performance degradation for the radio Master and for the radio Slave simultaneously. Management data BTS faults and reported alarms Table 272: New BTS faults lists BTS faults introduced with this feature. Table 272

New BTS faults

Fault ID

Fault name


4253

Shared radio not synchronized to Radio Master

Alarm name

7651


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 273


Abbreviated name

Owned by this BTS

ownedByThisBts

Managed object SMOD

Table 274: Modified parameters lists parameters modified by this feature. Table 274

Modified parameters

Full name

Issue: 01D

Abbreviated name

Managed object

Structure

Link list

linkList

BBMOD/SMOD

-

Radio master

radioMaster

BBMOD/SMOD

linkList

Rf sharing enabled

rfSharingEnabled

BTSSCL

-

Shared RF technologies

sharedRfTechnologies

MRBTS

-

Synchronization master

syncMaster

SMOD

-

Link Identifier

linkId

RMOD

connectionList

Position in chain

positionInChain

RMOD

connectionList

System Module Identifier

sModId

RMOD

connectionList

DN09185982

469


Table 274


Modified parameters (Cont.)

Full name Baseband Module Identifier

Abbreviated name bbModId

Managed object

Structure

RMOD

connectionList



Full name

Abbreviated name

Managed object

System Module Identifier

sModId

BBMOD

Baseband Module Identifier

bbModId

BBMOD

Synchronization Propagation Enabled

syncPropagationEnabl BTSSCL ed

Technology

technology

SMOD

Link speed

linkSpeed

BBMOD/SMOD

Structure

linkList


Sales information

BSW/ASW ASW



6.2.2 Activating and configuring LTE1829: Inter eNB RF sharing This section shows the activation procedures for the LTE1829: Inter eNB RF Sharing. Related parameters Table 277

Parameters used for activating and configuring LTE1829: Inter eNB RF Sharing

Parameter

470

Purpose

Value


Rf sharing enabled (rfSharingEnabled) BTSSCL

Activation flag

True

No

Owned by this BTS (ownedByThisBts) SMOD

Mandatory configuration

True in this SMOD and false in peer SMOD

No

Link speed (linkSpeed) BBMOD

Optional configuration

Auto

No

Synchronization master (syncMaster) SMOD


True

eNB restart

Radio master (radioMaster) SMOD/BBMOD


True in this SMOD/BBMOD and false in peer SMOD

No

DN09185982

Issue: 01D


Table 277


Parameters used for activating and configuring LTE1829: Inter eNB RF Sharing (Cont.)

Parameter

Purpose

Value


Forward synchronization in co-siting (syncPropagationEnable d) BTSSCL


True

No

Technology (technology) SMOD


EUTRA

eNB restart

When activating the LTE1829: Inter eNB RF Sharing feature, the rfSharingEnabled parameter value is set to "true" and there are two SMODs in the SCF, both with the "EUTRA" technology. At least one RMOD has to be selected to be shared between the two LTE SMODs, then the BTSSM fills with default values for the eNB. The SMODlinkList parameter contains three list items that have a defined linkId (1, 2 and 3) with supported values for interfaces connected to the radios. One value is assigned to each item, only for supported linkIds, based on FSM property RP3.Interfaces. The BBMOD- linkList must contain any of the four items with linkId values 1, 2 , 3 or 4 (one value for each item). Radiomaster has its value set to "true" or "false" for each item where the RM is shared according to end user selection and is set to “true” for each item with dedicated RM. For shared radio modules RMOD- connectionList contains items which points two different SMOD objects which have technology parameter value "EUTRA". One entry must contain the connection to this EUTRA's SMOD or BBMOD and the 2nd contains connection to point to the peer SMOD. Feature dependencies The LTE1710: Sync Hub Direct Forwarding feature needs to be activated or configured before activating the LTE1829: Inter eNB RF Sharing feature. The following features need to be deactivated before activating the LTE1829: Inter eNB RF Sharing feature: • • •

LTE447: SW support for RF sharing GSM-LTE LTE435: LTE RF sharing WCDMA-LTE LTE977: RF chaining

Scenarios Three Cases are presented in this Feature Activation Instruction: 1. Installation of a new LTE-LTE RF Sharing Configuration •

Two eNBs with one FSMF or FSMF with one or two FBBCs are installed.

2. Migration of a single eNB site to an LTE-LTE RF Sharing Configuration with no new shared RFMs/RRHs •

A new eNB is added to an LTE site that is already operational. Only existing RFMs/RRHs are shared.

3. Migration of a single eNB site to an LTE-LTE RF Sharing Configuration with new shared RFMs/RRHs

Issue: 01D

DN09185982

471


•

6.2.2.1


A new eNB is added to an LTE site that is already operational. New shared RFMs/RRHs are a new addition to this feature.

Activation requirements This section describes the requirements for activating the LTE1829: Inter eNB RF Sharing feature. Hardware requirements For activating and configuring the LTE1829: Inter eNB RF Sharing feature make sure you have the following hardware prepared: • • • • • •

Two eNBs including one system module and optional baseband extension modules. One or more shared radio modules between two eNBs. Sync Cable for connection between SMs (from SYNC OUT to SYNC IN connectors). One eNB connected to the external synchronization clock source to assume the SyncHub Master role. Optical RP3-01 connection between eNBs. All other hardware equipment needed for the eNBs to come into service installed.

Site requirements Make sure that the site is prepared for installation, factory SW as defined in LTE1474 is present in the eNBs and OMS is configured and able to support eNB auto connection.

6.2.2.2

General activation procedure Procedure 1


2

Activate the Rf sharing enabled (rfSharingEnabled) parameter. a) b) c) d) e) f)

472

Go to the Concurrent Mode Settings page. Select the RF sharing enabled object. Choose the shared technologies LTE-LTE. Fill in the product code and serial number of the peer SM. Specify the connections. Choose mastership.

DN09185982

Issue: 01D


Figure 53


Enabling RF Sharing

a b c d

f e

3

6.2.2.3


Installing a new LTE-LTE RF Sharing Configuration Purpose The purpose of this scenario is to prepare a new RF sharing site. HW is installed and activated locally during the site visit. After the site visit both eNBs are operational. Ensure that you have all the respective instructions to prepare the desired site. Procedure Before the site visit

Issue: 01D

DN09185982

473



1

Prepare the configurations and Site Configuration Files (SCFs) for both eNBs to save the site visiting time.

2

Install the correct LTE BTS Site Manager version on your computer(s).

g

Note: Note: It is recommended that two computers are used during installation to allow simultaneous connections to both eNB' Site Managers.

3

Check the supported SW for both eNBs in RF Sharing Compatibility Matrix.

4

Optional: Update the SMs' SW. It is recommended that new SMs' SW is updated before the site visit to save time during the site visit. If Incompatible SW version detected (0023) alarm is raised, update the SW again.

During the site visit 5

Install the HW by connecting all the cables and connecting your computer (s) to SMs via Local Management Ports (LMPs). To connect the modules for RF sharing configurations, see LTE Base Stations Supported Configurations. For details, see the respective Installing and Cabling Flexi Multiradio documentation. Ensure that the RFM/RRH has the same SFP type as the SM - 3 Gbps or 6 Gbps. It is recommended to use 6 Gbps SFPs and optical links, when supported by the used HW.

g

474

6

eNBs boot up.

7

Download and activate the SW Release supporting LTE-LTE RF Sharing and Configuration data on the Master eNB.

8

Master eNB restarts to activate software and configuration into use.

9

Once Master eNB's SM boots up, ensure all the RFMs/RRHs and ALDs are detected and appear in the BTS Site Manager. Note: Note: FSMF is delivered with Factory Delivered SW (FDSW). Site Manager does not detect any RFMs/RRHs and ALDs until the SM is updated with correct SW. For the update procedure instructions, see the Delivery Note, provided in the HW delivery box.

DN09185982

Issue: 01D



10 Repeat steps 7-9 for the Slave eNB. Step result The site is ready and both eNBs are operational.

Post requisites Before leaving the site ensure that: • • •

6.2.2.4

both eNBs are working properly without any unexpected alarms. test calls (both data and voice- if supported) are successful in each cell/sector. all unused ports (for example LMP) are secured with IP caps.

Migration of a single eNB site to an LTE-LTE RF Sharing Configuration with no new shared RFMs/RRHs Purpose The purpose of this scenario is to add RF Sharing to the site. While the first eNB is already operating, the second one is being installed and RF Sharing is activated locally during the site visit. After the site visit both eNBs are operational. Ensure that you have all the respective instructions to prepare the desired site. Assumption:Assuming that the eNB-1 is the Master and eNB-2 is the slave, ensure the following pre-conditions are met: • •

eNB-1 is up and running with a SW load that can handle LTE-LTE RF Sharing. eNB-2 including FSMF or FSMF with one or two FBBCs and dedicated RFMs/RRHs is delivered.

Procedure

Before the site visit

g

Issue: 01D

1


2

Install the correct LTE BTS Site Manager version on your computer(s). Note: Note: It is recommended that two computers are used during installation to allow simultaneous connections to both eNB' Site Managers.

DN09185982

475



3


4

Optional: Update the eNB-1 SM's SW. If the SW needs to be updated for the already operating eNB-1, update it remotely to save time during the site visits.

5

Optional: Update the eNB-2 SM's SW. It is recommended that eNB-2 SM's SW is updated before the site visit. This saves time during site visits and the eventual downtime of the already deployed eNB-1 transmission.

g

Note: Note: FSMF is delivered with Factory Delivered SW (FDSW). Site Manager does not detect any RFMs/RRHs and ALDs until the SM is updated with appropriate technology SW. For the update procedure instructions, see the Delivery Note, provided in the HW delivery box.


Install eNB-2's new FSMF or FSMF with one or two FBBCs, dedicated RFMs/RRH/s, antennas, and cabling. Do not connect the new SM to the already deployed SM and RFMs/RRHs. This way prevents disturbance to the technology transmission that is already deployed.

7

Power up the eNB-2 SM. Update the SW, if not done before. This ensures that the new SM is running the correct SW before proceeding.

8

Power off the eNB-1 and the eNB-2 SMs and finalize the HW installation for RF Sharing. To connect the modules for RF Sharing configurations, see LTE Base Stations Supported Configurations. For details, see the respective Installing and Cabling Flexi Multiradio documentation. Ensure that the RFM/RRH has the same SFP type as the SM - 3 Gbps or 6 Gbps. It is recommended to use 6 Gbps SFPs and optical links, when supported by the used HW. Connect the eNB-2 to eNB-1 via RP3-01 optical and sync cables. Step result The eNB-1's traffic is reduced.

476

DN09185982

Issue: 01D


9


Recommended (Optional): Switch the RFM/RRH power cables to the eNB-1. The Shared RFMs/RRHs can be powered from either eNB-1 SM, eNB-2 SM, or an external power supply, depending on the site environment. If the RFMs/RRHs are powered from the eNB-2 SM and a HW reset or a failure occurs in the eNB-2 SM, both eNB' traffic is reduced. If the RFMs/RRHs are powered from the eNB-1 SM (as recommended) and a reset or failure occurs in the eNB-2 SM gets, only the eNB-2 traffic is reduced.

10 Power up the eNB-1's SM and ensure all the RFMs/RRHs and ALDs are detected and shown properly in the BTS Site Manager. If Incompatible SW version detected (0023) alarm is raised, update the SW again. Step result The HW is now ready for commissioning.

11 Configuration data is supplied to eNB-1, either via its Site Manager or NetAct. 12 eNB-1 is re-started in order to take updated configuration into use. Step result The eNB-1 cells become operational (in both shared and dedicated RFMs/RRHs).

13 eNB-2 boots up. 14 SW Release supporting LTE-LTE RF Sharing is installed on the eNB-2. 15 Configuration data is supplied to eNB-2. 16 eNB-2 is re-started in order to take SW and configuration into use. Step result The site is ready and both eNBs are operational.

Post requisites Before leaving the site ensure that: • • • • •

Issue: 01D

no unexpected alarms raised by the eNB's Site Managers. both eNBs are transmitting properly (make test calls). all unused ports (for example LMP) are secured with IP caps. all cables are routed, connected and tied correctly. front and back covers are properly installed, if provided with the module.

DN09185982

477


6.2.2.5


Migration of a single eNB site to an LTE-LTE RF Sharing Configuration with new shared RFMs/RRHs Purpose The purpose of this scenario is to add RF Sharing to the site. While the first eNB is already operating, the second one is being installed and RF Sharing is activated locally during the site visit. After the site visit both eNBs are operational. Ensure that you have all the respective instructions to prepare the desired site. Assuming that the eNB-1 is the Master and eNB-2 is the Slave, ensure the following preconditions are met: • • •

eNB-1 is operational with a SW load that can handle LTE-LTE RF Sharing. New shared RFMs/RRHs and optionally FBBCs are delivered. eNB-2 including FSMF or FSMF with one or two FBBCs and dedicated RFMs/RRHs is delivered.

Procedure Before the site visit 1


2

Install the correct LTE BTS Site Manager version on your computer(s).

g

Note: Note: It is recommended that two computers are used during installation to allow simultaneous connections to both eNB' Site Managers.

3


4

Optional: Update the eNB-1 SM's SW. If the SW needs to be updated for the already operating eNB-1, update it remotely to save time during the site visit.

5

Optional: Update the eNB-2 SM's SW. It is recommended that eNB-2 SM's SW is updated before the site visit. This saves time during site visits and the eventual downtime of the already deployed eNB-1 transmission.

g

478

Note: Note: FSMF is delivered with Factory Delivered SW (FDSW). Site Manager does not detect any RFMs/RRHs and ALDs until the SM is updated with appropriate technology SW. For the update procedure instructions, see the Delivery Note, provided in the HW delivery box.

DN09185982

Issue: 01D




Install new FBBCs if any, new, shared RFMs/RRHs, and cabling on eNB-1. Install eNB-2's new FSMF or FSMF with one or two FBBCs, dedicated RFMs/RRH/s, antennas, and cabling. Do not connect the new SM to the already deployed SM and RFMs/RRHs. This way does not disturb the already deployed technology transmission.

7

Power up the eNB-2 SM. Update the SW, if not done before. This ensures that the new SM is running the correct SW before proceeding.

8

Power off the eNB-1 and the eNB-2 SMs and finalize the HW installation for RF Sharing. To connect the modules for RF Sharing configurations, see LTE Base Stations Supported Configurations. For details, see the respective Installing and Cabling Flexi Multiradio documentation. Ensure that the RFM/RRH has the same SFP type as the SM - 3 Gbps or 6 Gbps. It is recommended to use 6 Gbps SFPs and optical links, when supported by the used HW. Connect the eNB-2 to eNB-1 via RP3-01 optical and sync cables. Step result The eNB-1's traffic is reduced.

9

Recommended (Optional): Switch the RFM/RRH power cables to the eNB-1. The Shared RFMs/RRHs can be powered from either eNB-1 SM, eNB-2 SM, or an external power supply, depending on the site environment. If the RFMs/RRHs are powered from the eNB-2 SM and a HW reset or a failure occurs in the eNB-2 SM, both eNB' traffic is reduced. If the RFMs/RRHs are powered from the eNB-1 SM (as recommended) and a reset or failure occurs in the eNB-2 SM gets, only the eNB-2 traffic is reduced.

10 Power up the eNB-1's SM and ensure all the RFMs/RRHs and ALDs are detected and shown properly in the BTS Site Manager. If Incompatible SW version detected (0023) alarm is raised, update the SW again. Step result The HW is now ready for commissioning.

Issue: 01D

DN09185982

479



11 Configuration data is supplied to eNB-1, either via its Site Manager or NetAct. 12 eNB-1 is re-started in order to take updated configuration into use. Step result The eNB-1 cells become operational (in both shared and dedicated RFMs/RRHs).

13 eNB-2 boots up. 14 SW Release supporting LTE-LTE RF Sharing is installed on the eNB-2. 15 Configuration data is supplied to eNB-2. 16 eNB-2 is re-started in order to take SW and configuration into use. Step result The site is ready and both eNBs are operational.

Post requisites Before leaving the site ensure that: • • • • •

6.2.2.6

no unexpected alarms raised by the eNB's Site Managers. both eNBs are transmitting properly (make test calls). all unused ports (for example LMP) are secured with IP caps. all cables are routed, connected and tied correctly. front and back covers are properly installed, if provided with the module.

Commissioning eNBs for LTE-LTE RF Sharing Steps to commission LTE for LTE-LTE RF Sharing. Purpose Follow these steps to commission LTE-LTE RF Sharing. Make sure that all the appropriate steps for all Scenarios have been completed.

g g

480

Note: Note that the RF Sharing is a part of the commissioning procedure. Commissioning procedures are described in detail in the technology-specific documents. The RF Sharing commissioning steps have to be taken in addition to the technology-specific steps. Note: In RF Sharing configurations, only certain Master-Slave BTS SW combinations, SW upgrade paths and configurations are tested, recommended and officially supported. Using any other SW combinations, upgrade path or configuration might cause unexpected problems.

DN09185982

Issue: 01D



Preconditions: •

• • • •

The BTS Site Manager is running and connection to the BTS is established. Always use the matching BTS Site Manager version, considering the running BTS SW version. Appropriate SW and licenses are downloaded to the BTS. The running BTS SW in the System Module is the correct version before commissioning. Upgrade the BTS SW if required. The RFMs/RRHs and ALDs are correctly detected. There are no unexpected alarms.

Procedure 1

Start commissioning. Select Commissioning, Target: BTS, Commissioning type: Select from available options • • •

when the SCF has been prepared before: Template when there is no SCF file: Manual when the SCF needs to be reconfigured: Reconfiguration

Step result The BTS Settings page appears. Note that the other eNB's System Module is not detected yet.

2

Enable EIF2 as RP3-01 interface If EIF2 at FSMF is in use for RP3-01 connection to other SM, go through the TRS commissioning first and check the "Enable EIF2 as RP3-01 interface". Figure 54

g g

Issue: 01D

Enable EIF2 as RP3-01 interface

Note: Note that it is also possible to enable EIF2 as RP3-01 interface option in "TRS Hardware" section in SEM. To do so, check the Enable FSM EIF2 as RP3-01 interface box in the "Physical interfaces tab. Note: Another option for this connection is to use FBBC port #3. In that case EIF2 can still be used as transport interface.

DN09185982

481


3


Proceed to Concurrent Mode Settings. Tick the RF sharing enabled check box, choose LTE-LTE Shared technologies, enter the product code and serial number of the other technology SM, and choose the shared RFMs/RRHs.

g

Note: At least one RFM/RRH must be selected as shared. Figure 55

4

g

LTE - Concurrent Mode Settings for LTE-LTE

Proceed to Cell Resources. Note: Make sure that the power sums of all carriers TRXs does not exceed the RFM's/RRH's maximum output power.

5

Proceed to LTE Carriers. Enter the EARFCN channel value for each Local Cell. These EARFCN values are stored in the SCF and are later used for commissioning. Select the appropriate Bandwidth. Ensure the Bandwidth is supported by the used HW configuration. For details see LTE Base Stations Supported Configurations.

g

Note: Make sure that all LTE carriers are within the RFM's/RRH's UL/DL instantaneous bandwidth, and that they are not overlapping.

f

Configuration of the same EARFCN on cells from different eNBs will cause severe performance degradation for the radio Master and for a the radio Slave simultaneously.

6

Proceed to Radio Module External Fault and Control Settings. Every Radio Module alarm can be commissioned for either or both of the two eNBs. For example, if an alarm is commissioned for eNB-1, it is visible from the eNB-1 side only.

482

DN09185982

Issue: 01D


7


Proceed to the last page - Send Parameters. Select Send: All parameters. Save Parameters, if the SCF is needed for later commissioning, then Send Parameters Step result The LTE SM resets and the RF Sharing is activated.

Expected outcome The site is ready and both eNBs are on air, RF Sharing is activated, service is being provided. Unexpected outcome • •

•

•

•

•

•

Issue: 01D

If both eNBs are not commissioned, the eNB that detects the shared radios first takes over the mastership and the other eNB takes the slave role. If the configuration plan download (from NetAct) fails for eNB-1 or eNB-2, the user is informed with proper error code and the new failed configuration is not taken into use (no change for current existing procedure). If shared RF parameter activation fails, the shared RF parameter is not changed and user is informed with activation feedback. The failure of eNB-1 configuration leads to the situation in which eNB-2 configuration is invalid (if it is according master configuration). If both BTSs are configured as radio master for the shared radios, the BTS that detects the shared radios first takes over the mastership and uses the shared radios. The other BTS raises alarm (Fault: Radio Master Conflict) and cannot use the shared radios. If both BTSs are configured as radio slave for the shared radios, the BTS that detects the shared radios first configures the shared radios, raises alarm (Fault: Shared radio not synchronized to Radio Master), but does not use the shared radios (as it detects the peer BTS). The other BTS takes the slave role and uses the shared radios. If the slave BTS is activated long before the configured master BTS and LTE1710B is enabled, the slave BTS issues alarm (Fault: Shared radio not synchronized to Radio Master), determines that LTE1710B is enabled, cancels alarm (Fault: Shared radio not synchronized to Radio Master), takes temporary radio mastership of the shared radios, raises alarm (Fault: Temporary Radio Master) and uses the shared radios. Once the configured master BTS is activated, it determines that the shared radios have a master and raises alarm (Fault: Radio Master Conflict). The master and slave BTSs negotiate mastership. The slave BTS releases temporary mastership, cancels alarm (Fault: Temporary Radio Master), and takes over the slave role. The configured master BTS cancels alarm (Fault: Radio Master Conflict) and takes over the master role. The shared radios are in use by both BTSs. If the slave BTS is activated before the configured master BTS and LTE1710B is disabled, the slave BTS issues alarm (Fault: Shared radio not synchronized to Radio Master) and cannot use the shared radios. Once the master BTS is activated, the

DN09185982

483


•


master and slave BTSs negotiate mastership. The slave BTS cancels alarm (Fault: Shared radio not synchronized to Radio Master) and takes the slave role. The master BTS takes over the master role. The shared radios are in use by both BTSs. FSM-1 notes it is connected to RF secondary port. FSM-1 receives a request from the opposite FSM-2, whether FSM-1 wants to have the mastership of this radio. FSM-1 responds 'Yes'. FSM-2 switches the RF primary opt port ownership to FSM-1. In case Ethernet was already enabled for this radio, the radio triggers a recovery reset.

Further information For additional information see Configuring RF Sharing.

6.2.3 Deactivating LTE1829: Inter eNB RF sharing Before you start The Rf sharing enabled (rfSharingEnabled) parameter is used for deactivation. Modification of this parameter does not require neither eNB restart nor cell locking. To deactivate the LTE1829: Inter eNB RF Sharing feature, do the following: Procedure 1


2

Deactivate/Set the Rf sharing enabled(rfSharingEnabled). a) Go to the Concurrent Mode Settings page. b) Uncheck the RF sharing enabled object.

g

Note: This deactivates the feature.

3


Expected outcome The LTE1829: Inter eNB RF Sharing feature is deactivated in the eNB.

484

DN09185982

Issue: 01D



6.3 LTE2028: Outdoor External GNSS Module with Enhanced Holdover - FYGG 6.3.1 Description of LTE2028: Outdoor External GNSS Module with Enhanced Holdover - FYGG Introduction to the feature This feature introduces an outdoor solution of GNSS receiver, for converting RF GNSS signal to 1PPS+ToD and providing extended holdover performance that meets the enhanced deployment scenario requirements by the LTE operators. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits LTE2028: Outdoor External GNSS Module with Enhanced Holdover - FYGG provides the following benefits: Holdover solution allowing the System Module to extend the eNB operating time in case GNSS signal is lost. Operators can reuse existing RF GNSS antennas deployed in the field. Outdoor site deployment is possible. Easy installation on a wall or pole.

• • • •



System release


FDD-LTE15A/TD- FL15A/TL15A LTE15A Flexi Zone Controller -

OMS -

Flexi Multiradio 10 Indoor BTS TL15A

-

UE -


NetAct -


MME -

SAE GW -

Additional hardware requirements This feature requires FYGG Outdoor External GNSS module. Functional description The LTE2028: Outdoor External GNSS Module with Enhanced Holdover - FYGG feature introduces an external GNSS module with the following additional functions: •

Issue: 01D

Support 12 hours holdover with phase drift of less than or equal +/-3us under the ambient temperature variation of +/-20°C.

DN09185982

485


• • •

•


Support deployment and operation in an outdoor (IP65) environment. Primary target for mounting with FSMF is into FPFD slot (similar as with FYGD & FYGE) and support alternative mounting in the existing FYGE Mounting 1U Casing. The -48V DC Input connector will use the Nokia standard as implemented on the System Module programs. The HDMI Sync Out connector of FYGG will use the Nokia standard as implemented on the System Module program. This is to maintain commonality of components and solution approach. Operating temperature range from -35°C to +55°C.

System impact Interdependencies between features The LTE2028: Outdoor External GNSS Module with Enhanced Holdover - FYGG feature is related to LTE1668: Enhanced external GPS box FYGE feature , as basic GPS receiver functions are re-used. List of functionalites re-used in LTE2028: Outdoor External GNSS Module with Enhanced Holdover - FYGG: • • • • •

Enabling/disabling of the FYGG holdover mode. Enabling/disabling the power supply for the GNSS antenna in the FYGG module. Utilization of BTS adaptive holdover algorithm. FYGG status, alarm and satellite data information. FYGG reset functionality.

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 additional alarms related to this feature, compared to the existing FYGE alarms. 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 additional parameters related to this feature, compared to the existing FYGE parameters.

486

DN09185982

Issue: 01D




Sales information

BSW/ASW


BSW

-


6.4 LTE2143: FRBE Flexi RRH 4-Pipe 750&720T 160W 6.4.1 Description of LTE2143: FRBE Flexi RRH 4-Pipe 750&720T 160W Introduction to the feature This feature introduces the Flexi Multiradio Remote Radio Head (RRH) FRBE with 2TX/2RX for 750 MHz 3GPP band 13 (uplink: 777-787 MHz, downlink: 746-756 MHz) and 2TX for 720 MHz 3GPP band 29 (downlink: 718-728 MHz). Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits FRBE provides 2x40 W high output power at the antenna connectors with 2TX/2RX MIMO on band 13 and 2TX MIMO on band 29. FRBE offers two band operation with a single RRH. In addition, it has three 6 Gbit/s OBSAI optical interfaces, one dedicated to chaining. The Remote Radio Head can be easily installed outdoors and close to antennas, thus maximizing the BTS site capacity and area coverage. Requirements Hardware and software requirements Table 280





OMS -


Not supported



NetAct -


MME -

SAE GW -


Issue: 01D

DN09185982

487


Table 281


FRBE functional specification Property

Value

Output power

B13: 2x40 W, B29: 2x40 W

MIMO

2TX on B13 and B29


yes


FDD-LTE

TX frequency range

B13: 746 - 756 MHz B29: 718 - 728 MHz

RX frequency range

B13: 777 - 787 MHz


B13: 10 MHz B29: 10 MHz


10 MHz

DL filter bandwidth

B13: 10 MHz B29: 10 MHz

UL filter bandwidth

10 MHz

For more information, see Flexi Multiradio BTS RF Module and Remote Radio Head Description. The following are some basic LTE configurations: • •

2TX MIMO with 5 and 10 MHz on band 13 2TX MIMO with 5, 10 MHz and 5 + 5 MHz on band 29

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.

488

DN09185982

Issue: 01D




Sales information

BSW/ASW


BSW

-


6.5 LTE2146: FRBF Flexi RRH 4-Pipe 760 160W 6.5.1 Description of LTE2146: FRBF Flexi RRH 4-Pipe 760 160W Introduction to the feature This feature introduces Flexi Multiradio Remote Radio Head (RRH) FRBF with 4TX/4RX for 3GPP band 14 (uplink: 788 - 798 MHz, downlink: 758 - 768 MHz). Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits FRBF provides 4x40 W high output power to the antenna connector with 4TX MIMO. Additionally, it is provided with three 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. Requirements Hardware and software requirements Table 283





Issue: 01D

OMS -


Not supported


DN09185982


NetAct -


MME -

SAE GW -

489



Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview Table 284

FRBF functional specification Property

Value

Output power

4x40 W

MIMO

4TX


Yes


FDD-LTE

TX frequency range

758 - 768 MHz

RX frequency range

788 - 798 MHz


10 MHz


10 MHz

DL filter bandwidth

10 MHz

UL filter bandwidth

10 MHz

For more information, see Flexi Multiradio BTS RF Module and Remote Radio Head Description. 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

490

DN09185982

Issue: 01D



There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Sales information Table 285

Sales information

BSW/ASW


BSW

-


6.6 LTE2147: FHGB Flexi RRH 4-Pipe 2100 120W K 6.6.1 Description of LTE2147: FHGB Flexi RRH 4-Pipe 2100 120W K Introduction to the feature This feature introduces Flexi Multiradio Remote Radio Head (RRH) FHGB with 4TX/4RX for LTE operation at spectrum allocation on 2100 MHz 3GPP band 1 (uplink: 1920-1940 MHz, downlink: 2110-2130 MHz). Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits FHGB provides 4x30 W high output power at the antenna connector with 4TX MIMO. 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. Requirements Hardware and software requirements Table 286


System release FDD-LTE 15A Flexi Zone Controller



OMS

Not supported -

-



Not supported

NetAct -


MME -

SAE GW -


Issue: 01D

DN09185982

491



Functional overview Table 287

FHGB functional specification Property

Value

Output power

4x30 W

MIMO

4TX


Yes


FDD-LTE

TX frequency range

2110 - 2130 MHz

RX frequency range

1920 - 1940 MHz


20 MHz


20 MHz

DL filter bandwidth

20 MHz

UL filter bandwidth

20 MHz

For more information, see Flexi Multiradio BTS RF Module and Remote Radio Head Description. 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 maximizes the BTS site capacity and provides high output power for dense urban sites. 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

492

DN09185982

Issue: 01D



There are no parameters related to this feature. Sales information Table 288

Sales information

BSW/ASW


BSW

-

License control attributes -

6.7 LTE2148: FHPC Flexi RRH 2/2-Pipe 700&850 100W K 6.7.1 Description of LTE2148: FHPC Flexi RRH 2/2-Pipe 700&850 100W K Introduction to the feature The LTE2148: FHPC Flexi RRH 2/2-Pipe 700&850 100W K feature introduces a dual band Remote Radio Head (RRH) operating on 700 MHz (3GPP B28) and 850 MHz (3GPP B18) bands with CPRI interface. FHPC is the first dual band RRH and the first one operating on band 28. FHPC has two independent TX and RX lineups (2T2R 2 x 30W for B18 and 2T2R 2 x 20W for B28) that are internally diplexed to two antenna connectors. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits With this feature the operator can replace the legacy 850 MHz Remote Radio Head with a new, dual band RRH and use the high-capacity FSMF System Module. Requirements Hardware and software requirements Table 289





OMS -


Not supported

UE 3GPP R9


NetAct -


MME -

SAE GW -


Issue: 01D

DN09185982

493



Functional overview Table 290

FHPC functional specification Property

Value

Output power

B18: 2x30 W, B28: 2x20 W

MIMO

2TX


Yes


FDD-LTE

TX frequency range

B18: 860 - 875 MHz B28: 773 - 783 MHz

RX frequency range

B18: 815 - 830 MHz B28: 718 - 728 MHz


B18: 15 MHz B28: 10 MHz


B18: 15 MHz B28: 10 MHz

DL filter bandwidth

B18: 15 MHz B28: 10 MHz

UL filter bandwidth

B18: 15 MHz B28: 10 MHz

For more information, see . 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.

494

DN09185982

Issue: 01D




Sales information

BSW/ASW


BSW

-


6.8 LTE2156: Site Aggregation for Flexi Zone 6.8.1 Description of LTE2156: Site Aggregation Solution for Flexi Zone Introduction to the feature This feature provides capability to aggregate several Flexi Zone BTS in a Controller or Standalone configuration by using routing platforms from Juniper. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits LTE2156: Site Aggregation Solution for Flexi Zone feature provides fan-out and aggregation capabilities for Flexi Zone deployments. Requirements Hardware and software requirements Table 292


System release FL15A/TL15A

Flexi Multiradio BTS not supported

UE -

Flexi Multiradio 10 BTS not supported

NetAct -

Flexi Zone Micro FL15A/TL15A

-

MME -

OMS

SAE GW -

Additional hardware requirements There is no additional hardware requirements to this feature.

Issue: 01D

DN09185982

495



Functional description Functional overview LTE2156: Site Aggregation Solution for Flexi Zone provides site aggregation support for Flexi Zone small cells in both stand-alone and Controller deployments, consolidating connections from multiple small cells into a single connection. Additional information on the feature: • • • • •

reduces port density requirements on the Controller supports small cell connectivity to Flexi Zone Controller via L2 or L3 interface two Juniper hardware platforms optimized for high quality mobile broadband networks are certified: ACX2200 and ACX4000 supports integration, configuration, and testing of both platforms with Flexi Zone small cells performance and equipment monitoring of Juniper platforms can be accomplished using NetAct; and configuration management using Juniper OAM (Junos Space)

System impact Interdependencies between features This feature has no impact on other features. Impact on interfaces This feature has no impact on interfaces. Impact on network 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

496

DN09185982

Issue: 01D


Table 293


Sales information

BSW/ASW


BSW

-


6.9 LTE2172: BTS Configurations optimized for distributed RRH deployment 6.9.1 Description of LTE2172: BTS Configurations optimized for distributed RRH deployment Introduction to the feature The feature LTE2172 provides additional LTE FDD BTS configurations that are specifically designed to provide efficient deployment of distributed RRH units in multiband installations. The configurations of this feature support Small Cells (or Micro Cells) using Low Power Radio Heads as well as standard macro Radio Heads. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides additional chaining options that allow to use a single fiber pair for connecting each multi-band antenna location (or sector) to the system module. Requirements Hardware and software requirements Table 294 System release FDD-LTE 15A Flexi Zone Controller not supported

Hardware and software requirements Flexi Multiradio BTS not supported

OMS not supported


Flexi Zone Micro BTS not supported

Flexi Zone Access Point not supported

UE

NetAct

MME

SAE GW

not supported

not supported

not supported

not supported

Additional hardware requirements Configurations described in this feature can be used with any Radio Head (2Tx or 4Tx) including the Low Power RRH units. For RRH types that support 3Gbps optical link only specific restrictions apply (for details see LTE Base Stations Supported Configurations ). Functional description Functional overview

Issue: 01D

DN09185982

497



This feature introduces new cell set types for using in LTE FDD BTS configurations. It is specifically designed for distributed deployments using Nokia's Low Power Radio Heads and standard macro Radio Heads (2Tx or 4Tx). Following additional BTS 4Tx/4Rx Configurations for RRH are supported: •

Up to 4 sectors, supporting 15/20 MHz or 2x5/10 MHz in 4Tx/4Rx. All radio units in one sector are chained. First radio in chain must support 6Gbps optical links. – – –

up to 4 sectors for 15/20 MHz 4Tx/4Rx (one basic + one extended cell set) single sector, triple band installation for up to 20 MHz 4Tx/4Rx (one extended cell set) up to 4 sectors, dual band for 5/10 MHz in 4Tx/4Rx (one basic + one extended cell set)

Following Multiband and Multi-sector configurations for chained radio modules are supported: •

Using new XL cell set. This XL cell set combines the processing capacity of the extended and the basic cell set and allows more flexibility in assigning the cells to CoMP candidate sets. – –

•

6 sectors in dual band 15/20 MHz + 5/10 MHz in 2Tx/2Rx. All radios of one sector are chained. 4 sectors in triple band 15/20 MHz + 5/10 MHz + 5/10 MHz in 2Tx/2Rx. All radios of one sector are chained.

Using legacy extended cell set. – –

4 sectors in dual band 15/20 MHz + 5/10 MHz in 2Tx/2Rx. All radios of one sector are chained. 3 sectors in dual band 15/20 MHz + 15/20 MHz in 2Tx/2Rx, both radios of one sector are chained. This configuration is supported for distributed Flexi Radio Modules 3Tx/6Rx or 6Tx/6Rx as well.

System impact Interdependencies between features Carrier aggregation according LTE1089, LTE1332, LTE1562, LTE1803, LTE2033 is supported between cells of different bands. For 15/20 MHz cells in 4Tx, Intra eNB Carrier aggregation is limited to cells inside the same extended cell set. UL CoMP (LTE1402, LTE1691) is supported for the configurations provided by this feature: • •

With 4Rx cells: UL CoMP is possible only between 3 cells assigned to same cell set. With 2Rx cells: UL CoMP is supported between any 3 sells of same frequency band.

Feature LTE2133 is needed for support of eICIC between macro and micro cells on the same eNB. Impact on interfaces This feature has no impact on interfaces.

498

DN09185982

Issue: 01D



Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature provides additional chaining options that allow in most cases to use a single fiber pair for connecting each multi-band antenna location (or sector) to the system module. 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 295

Sales information

BSW/ASW


BSW

-


6.10 LTE2245: FHEI Flexi Metro RRH 2-pipe 1800 10W L 6.10.1 Description of LTE2245: FHEI Flexi Metro RRH 2-pipe 1800 10W L Introduction to the feature LTE2245: FHEI Flexi Metro RRH 2-pipe 1800 10W L feature introduces Flexi Metro Remote RF Head (RRH) with 2TX/2RX at low 60 MHz subband for 3GPP band 3. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits One sector Flexi Metro Remote RF Head: • •

Issue: 01D

supports 2TX MIMO with medium range output power (2 x 5 W) for hot spot dense urban capacity sites. enables RX sensitivity adjustment.

DN09185982

499


• • •


enables the power of the TX to be lowered to 50 mW. enables easy outdoor installation close to antennas or with an integrated antenna. minimizes weight and complexity of the BTS site.

Requirements Hardware and software requirements Table 296 System release FL15A

Hardware and software requirements Flexi Multiradio 10 BTS FL15A


OMS

not supported

Flexi Multiradio 10 Indoor BTS

-



not supported

NetAct -


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Other requirements Functional description Functional overview Table 297

FHEI functional specification Porperty

Value

Output power

2x5 W

MIMO

2TX


Yes


FDD-LTE

TX frequency range

1805 - 1865 MHz

RX frequency range

1710 - 1770 MHz


60 MHz


60 MHz

DL filter bandwidth

60 MHz

UL filter bandwidth

60 MHz

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.

500

DN09185982

Issue: 01D



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. BTS faults and reported alarms There are no faults or reported 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 298

Sales information

BSW/ASW


BSW

-


6.11 LTE2263: FRCG Flexi RRH 2-Pipe 850 120W 6.11.1 Description of LTE2263: FRCG Flexi RRH 2-Pipe 850 120W Introduction to the feature This feature introduces Flexi Multiradio Remote Radio Head (RRH) FRCG with 2TX/2RX for 3GPP band 5 (uplink: 824 - 849 MHz, downlink: 869 - 894 MHz). Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits FRCG provides up to 2x60 W high output power to the antenna connector with 2TX MIMO. Additionally, it is provided with 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.

Issue: 01D

DN09185982

501





System release


FDD-LTE 15A

Not supported


OMS

Not supported

-



FL15A

Not supported


NetAct -


MME -

SAE GW -


FRCG functional specification Property

Value

Output power

2x60 W

MIMO

2TX


Yes

SW supported technologies

FDD-LTE, WCDMA

TX frequency range

869 - 894 MHz

RX frequency range

824 - 849 MHz


25 MHz


25 MHz

DL filter bandwidth

25 MHz

UL filter bandwidth

25 MHz

For more information, see Flexi Multiradio BTS RF Module and Remote Radio Head Description. 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.

502

DN09185982

Issue: 01D



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 301

Sales information

BSW/ASW


BSW

-


6.12 LTE2264: FRNC Flexi RRH 4-Pipe 2300 120W 6.12.1 Description of LTE2264: FRNC Flexi RRH 4-Pipe 2300 120W Introduction to the feature This feature introduces the Flexi Multiradio Remote Radio Head (RRH) FRNC with 4TX/4RX for 2300 MHz 3GPP band 30 (uplink: 2305-2315 MHz, downlink: 2350-2360 MHz). Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits FRNC provides 4x30 W high output power at the antenna connector with 4TX MIMO. In addition, it has three 6 Gbit/s OBSAI optical interfaces. The Remote Radio Head can be easily installed outdoors and close to antennas, thus maximizing the BTS site capacity and area coverage. Requirements Hardware and software requirements

Issue: 01D

DN09185982

503


Table 302



System release


FDD-LTE 15A

Not supported


OMS

Not supported

-



FL15A

Not supported


NetAct -


MME -

SAE GW -


FRNC functional specification Property

Value

Output power

4x30 W

MIMO

4TX


Yes


FDD-LTE

TX frequency range

2350 - 2360 MHz

RX frequency range

2305 - 2315 MHz


10 MHz


10 MHz

DL filter bandwidth

10 MHz

UL filter bandwidth

10 MHz

For more information, see Flexi Multiradio BTS RF Module and Remote Radio Head Description. 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

504

DN09185982

Issue: 01D



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 304

Sales information

BSW/ASW


BSW

-


6.13 LTE2266: FRBG Flexi RRH 4-Pipe 730&720T 160W 6.13.1 Description of LTE2266: FRBG Flexi RRH 4-Pipe 730&720T 160W Introduction to the feature This feature introduces Flexi Multiradio Remote Radio Head (RRH) FRBG with 2TX/2RX for 3GPP band 12 (uplink: 699 - 715 MHz, downlink: 729 - 745 MHz), with 2TX/2RX for 3GPP band 17 (uplink: 704 - 715 MHz, downlink: 734 - 745 MHz), and with 2TX for 3GPP band 29 (downlink: 718 - 728 MHz). Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits FRBG enables two band operation by supporting bands 12, 17, and 29 with high power through 2TX MIMO and 2RX exclusively on band 12. Additionally it is provided with three 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. Requirements Hardware and software requirements

Issue: 01D

DN09185982

505


Table 305



System release


FDD-LTE 15A

Not supported


OMS

Not supported

-


Not supported

UE 3GPP R8 mandatory, 3GPP R11 mandatory


NetAct -


MME -

SAE GW -


FRBG functional specification Property

Value

Output power

4x40 W (B12 or B17: 2x40 W, B29: 2x40 W)

MIMO

2TX on B12, B17 and B29


Yes


FDD-LTE

TX frequency range

B12: 729 - 745 MHz B17: 734 - 745 MHz B29: 718 - 728 MHz

RX frequency range

B12: 699 - 715 MHz B17: 704 - 715 MHz


B12: 16 MHz B17: 11MHz B29: 10 MHz


B12: 16 MHz B17: 11MHz

DL filter bandwidth

B12: 16 MHz B17: 11MHz B29: 10 MHz

UL filter bandwidth

B12: 16 MHz B17: 11MHz

506

DN09185982

Issue: 01D



For more information, see Flexi Multiradio BTS RF Module and Remote Radio Head Description.

g

Note: When using FRBG for band 17, there is no filter protection or rejections from 699 MHz to 704 MHz. In cases where additional protection or rejection is required, use an external filter. 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 307

Sales information

BSW/ASW


BSW

-


6.14 LTE2272: SW-support for classical WCDMA/LTE RFsharing Indoor configurations 6.14.1 Description of LTE2272: SW-support for classical WCDMA/LTE RF-sharing Indoor configurations Introduction to the feature

Issue: 01D

DN09185982

507



The LTE2272: SW-support for classical WCDMA/LTE RF-sharing Indoor configurations introduces additional WCDMA/LTE RF-sharing configurations on the following frequency bands (3GPP TS 25.101 V12.3.0 LTE-FDD and 3GPP 36.101 V12.3.0 E-UTRA FDD frequencies): • • • •

Band 1 (2100 MHz) Band 2 (1900 MHz) Band 3+9 (1800 MHz) Band 4+10 (1.7/2.1 GHz)

Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits LTE2272: SW-support for classical WCDMA/LTE RF-sharing Indoor configurations: • • •

provides an easy and future-proof BTS site evolution from WCDMA to multiband, multi RAT technology by sharing Flexi Multiradio RF modules. helps allocate and share BTS RF resources between WCDMA and LTE in a flexible way. does not require additional external combiners, multiple RA technologies can share feeders and antennas in the same band.







OMS -

Not supported

UE -


NetAct -


MME -

SAE GW -

Additional hardware requirements This feature requires one of the following RF Modules: • • • • •

LTE101: Flexi 3-sector RF Module 1900 LTE1440: FXFC Flexi RF Module 3TX 1900 LTE86: FRGP Flexi 3-sector RF Module 2100 LTE986: FRGS Flexi 3-sector RF Module 2100 LTE99: Flexi 3-sector RF Module 1.7/2.1 (FRIE)

Functional description The LTE2272: SW-support for classical WCDMA/LTE RF-sharing Indoor configurations feature introduces additional configurations for indoor deployments.

508

DN09185982

Issue: 01D


g


Note: Following configurations can be also used for outdoor deployments, especially configurations 3, 4, 5, and 6. Table 309

Configurations introduced by the feature

Configuration number (link to the figure)

Cells/sectors

1

WCDMA; 2+2+2

WCDMA: 1Tx/1Rx SIMO (F-Type)

LTE: 1+1+1

LTE: 2Tx/2Rx MIMO (GType)

WCDMA; 2+2+2

WCDMA: 1Tx/1Rx SIMO (F-Type)

LTE: 1+1+1

LTE: 1Tx/1Rx SIMO (AType)1

WCDMA; 1+1

WCDMA: 1Tx/2Rx SIMO (A-Type)

2

3

LTE: 1+1

Configuration type

LTE BW 10 MHz

WCDMA: FSMF

10 MHz

WCDMA: FSMF

15 MHz

WCDMA: FSME

15 MHz

WCDMA: FSME

15 MHz

WCDMA: FSME

15 MHz

WCDMA: FSME

LTE: 1Tx/2Rx SIMO (AType) 4

5

6

WCDMA; 1+1+1


LTE: 1+1+1

LTE: 1Tx/2Rx SIMO (AType)

WCDMA; 1+1+1


LTE: 1+1+1


WCDMA; 1+1+1


LTE: 1+1+1


System Module

LTE: FSME or FSMF

LTE: FSME or FSMF

LTE: FSME or FSMF

LTE: FSME or FSMF

RF Modules (shared)

Carriers assignment

3x FXFA or 3x FXFC

WCDMA: both on a dedicated Power Amplifier (PA) or one on a dedicated PA and one on a shared PA

3x FXFA or 3x FXFC

WCDMA: both on a dedicated PA or one on a dedicated PA and one on a shared PA

1x FRGP.A, 1x FRIE or 1x FRGS

Both WCDMA and LTE carriers on shared PAs.

2x FRGP.A or 2x FRIE


2x FRGS


3x FRGP.A, 3x FRIE or 3x FRGS


LTE: FSMF

LTE: FSME or FSMF

1) The system processes only one Rx path, although configured as A-Type without raising any alarm. The second Rx path is terminated physically with an attenuator.

Figure 56

Configuration 1

WCDMA F-Type 1Tx/1Rx

Issue: 01D

DN09185982

LTE G-Type 2Tx/2Rx

509


Figure 57


Configuration 2

WCDMA F-Type 1Tx/1Rx

LTE 1Tx/1Rx attenuator

A-Type Figure 58

Configurations 3, 4, 5, and 6

Sector2

Sector1

WCDMA/LTE A-Type 1Tx/2Rx

WCDMA/LTE A-Type 1Tx/2Rx

System impact Interdependencies between features

510

DN09185982

Issue: 01D



The following features must be activated before starting up the LTE2272: SW-support for classical WCDMA/LTE RF-sharing Indoor configurations: • •

RAN2126: RF Sharing WCDMA - LTE LTE435: RF Sharing WCDMA - LTE

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 310

Sales information

BSW/ASW


BSW

-


6.15 LTE2310: FRCC Flexi RRH 2-Pipe 865 80W S 6.15.1 Description of LTE2310: FRCC Flexi RRH 2-Pipe 865 80W S Introduction to the feature The LTE2310: FRCC Flexi RRH 2-Pipe 865 80W S feature introduces a new Remote Radio Head (RRH) with 2TX (2x40 W) and 7 MHz sub-band used in North America to support LTE operation on 850 MHz 3GPP band 26A. Benefits End-user benefits

Issue: 01D

DN09185982

511



This feature does not affect the end-user experience. Operator benefits FRCC provides 2x40 W high output power with 2TX MIMO. The RRH can be easily installed outdoors, close to antennas, thus maximizing BTS site capacity and area coverage. Requirements Hardware and software requirements Table 311


System release


FDD-LTE 15A

Not supported


OMS

Not supported

-



FL15A

Not supported

UE 3GPP R11

NetAct -


MME -

SAE GW -


FRCC functional specification Property

Value

Output power

2x40 W

MIMO

2TX


Yes


FDD-LTE

TX frequency range

862.6 - 869 MHz

RX frequency range

817.6 - 824 MHz


6.4 MHz


6.4 MHz

DL filter bandwidth

6.4 MHz

UL filter bandwidth

6.4 MHz

For more details, see . System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on interfaces

512

DN09185982

Issue: 01D



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 313

Sales information

BSW/ASW


BSW

-


6.16 LTE2334: LTE-GSM RF sharing with 4-way RX diversity 6.16.1 Description of LTE2334: LTE-GSM RF sharing with 4-way RX diversity Introduction to the feature The LTE2334: LTE-GSM RF sharing with 4-way RX diversity introduces centralized and distributed configuration solutions for LTE-GSM RF-sharing with 4-way Rx. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The LTE2334: LTE-GSM RF sharing with 4-way RX diversity:

Issue: 01D

DN09185982

513


• • •


can be activated in the existing GSM grid. helps to close uplink related coverage gaps in the network. introduces configurations for the fragmented spectrum without combining an additional antenna line.







OMS -

Not supported

UE -


NetAct -


MME -

SAE GW -

Additional hardware requirements This feature requires one of the following RF Modules: • • •

LTE1040: FXEB RFModule 1800 MHz, 90W LTE1422: FXDB Flexi RF Module 3TX 900 LTE1440: FXFC Flexi RF Module 3TX 1900

This feature requires the following System Modules: • •

LTE947: FSMF Flexi Multiradio 10 System Module Flexi Multiradio BTS GSM/EDGE System Module (ESMB/C)

Functional description The LTE2334: LTE-GSM RF sharing with 4-way RX diversity feature introduces 4-way RX diversity in centralized configurations (stacked RFMs) or in distributed sites (1-3 RFMs). GSM can be configured in 2TX/4RX (IDD) mode in the shared pipes. LTE BW 5 and 10 MHz are supported with up to GSM 4+4+4 in the shared pipe. RF sharing configurations create new types of basic cell sets from LTE perspective. As defined in the LTE2079: LTE-GSM RF sharing with full FBBC support feature, they can be combined with any other valid cell set. Configurations introduced by the LTE2334: LTE-GSM RF sharing with 4-way RX diversity feature can be used with the following hardware: • • • • •

514

LTE1040: FXEB RFModule 1800 MHz, 90W LTE1422: FXDB Flexi RF Module 3TX 900 LTE1440: FXFC Flexi RF Module 3TX 1900 LTE947: FSMF Flexi Multiradio 10 System Module Flexi Multiradio BTS GSM/EDGE System Module (ESMB/C)

DN09185982

Issue: 01D


Table 315


Shared LTE and GSM pipes, centralized site solution

LTE BW

LTE Mode

GSM TRX

GSM Mode

5 MHz

2TX / 4RX (K-type)

Up to 4+4+4

2TX/4RX (K-type)

10 MHz

2TX / 4RX (K-type)

Up to 4+4+4

2TX/4RX (K-type)

5 MHz

2TX / 4RX (K-type)

Up to 8+8+8

1TX/2RX (C-type)

10 MHz

2TX / 4RX (K-type)

Up to 8+8+8

1TX/2RX (C-type)

Table 316

Shared LTE and GSM pipes, distributed site solution

LTE BW

LTE Mode

GSM TRX

GSM Mode

5 MHz

2TX / 4RX (J-type)

4+4+4

2TX/4RX (J-type)

10 MHz

2TX / 4RX (J-type)

4+4+4

2TX/4RX (J-type)

For more information, see Flexi Multiradio BTS RF Sharing Released Configurations. System impact Interdependencies between features The following features must be activated: • •

LTE447 (basic LTE-GSM RF sharing) LTE72 (MRC) or LTE980 (Interference rejection combining)

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

Issue: 01D

DN09185982

515


Table 317


Sales information

BSW/ASW


BSW

-


6.17 LTE2420: Supported RAS installation options in FL15A release 6.17.1 Description of LTE2420: Supported RAS installation options in FL15A release Introduction to the feature This feature introduces Flex Radio Antenna System (RAS). RAS physically encapsulates the RRH into the antenna enclosure. The feature lists the RAS antennas and compatible radios available in FDD-LTE 15A release. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the operator with the following benefits: • • • • •

simplifies cell site design through integration of the radio inside the antenna supports multiple frequency bands in one antenna enabling consolidation of antennas in the operator network better RF performance (reduced cable loss between antenna and RRH) modular architecture enables field maintenance and RRH upgrades independent from antenna the 10-port antenna system supports higher order MIMO (4TX) implementation and 4 Way diversity scheme for high bands






OMS -


Not supported



NetAct -


MME -

SAE GW -


516

DN09185982

Issue: 01D



This feature requires no new or additional hardware. Functional description Functional overview RAS configurations in FDD-LTE 15A consist of a tri-band antenna in two sizes (FASB, FASC) and up to two RRHs encapsulated into the antenna enclosure. Supported RAS installation options in FDD-LTE 15A presents Table 2 . Table 319

Supported RAS installation options in FDD-LTE 15A

RAS Antenna

FASB

Antenna frequency range [MHz]

3GPP bands supported by antenna

Compatible RRHs (maximum 2 RRHs)

Additional info

1850 - 1920/1930 2000 (4 ports)

2, 25

FHFB(4TX)

Any max 4TX/4RX outputs of the same band from separate RF Module or RRH can be connected

1695 - 1780/2095 2690 (4 port)

30, 7, 4, 10

FRNC(4TX)


698 - 894 (2 ports)

12, 29, 13, 14

FRBG(2TX+2TX) only 2TX


5, 18, 19, 27 26, 28

FRBE(2TX+2TX) only 2TX FRBF(4TX) only 2TX FRCG(2TX) FRCC(2TX)

FASC

2300 - 2690 (4 ports)

30, 7

FRNC(4TX)


1695 - 2200 (4 ports)

1, 3

FRGY(2TX)


2, 25 4, 10

Issue: 01D

DN09185982

517


Table 319


Supported RAS installation options in FDD-LTE 15A (Cont.)

RAS Antenna

Antenna frequency range [MHz]

3GPP bands supported by antenna

Compatible RRHs (maximum 2 RRHs)

Additional info

g

694 - 960 (2 ports)

28, 20 8, 5 12, 29, 13, 14

FRBG(2TX+2TX) only 2TX FRBE(2TX+2TX) only 2TX

Note: 1800 MHz 2TX/2RX external radio can be connected if 2100 MHz RRH occupies 2 ports. PCS and AWS should not be mixed at the same time.


FRBF(4TX) only 2TX FRCG(2TX) FRCC(2TX)

For more information, see Flexi Radio Antenna System Description and Flexi Multiradio BTS RF Module and Remote Radio Head Description. System impact Interdependencies between features This feature uses the following features: • • • • • • • • • •

LTE2448: FASB 2.4m RAS 1.9G 1.7/2.1G 698-894M LTE2449: FASC 2.0m RAS 2.3-2.6G 1.7-2.2G 694-960M LTE2310: FRCC Flexi RRH 2-Pipe 865 80W S LTE2263: FRCG Flexi RRH 2-Pipe 850 120W LTE2097: FRGY Flexi RRH 2TX 2100 LTE2264: FRNC Flexi RRH 4-Pipe 2300 120W LTE2266: FRBG Flexi RRH 4-Pipe 730&720T 160W LTE2143: FRBE Flexi RRH 4-Pipe 750&720T 160W LTE2146: FRBF Flexi RRH 4-Pipe 760 160W LTE1149: FHFB Flexi RRH 4TX 1900


518

DN09185982

Issue: 01D



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 performance and capacity as follows: • •

relatively better RF performance due to reduced cable loss between the antenna and RRH support for higher order MIMO (4TX) implementation and 4 Way diversity scheme for FASB and FASC where radios are integrated

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 320

Sales information

BSW/ASW


BSW

-


6.18 LTE2448: FASB 2.4m RAS 1.9G 1.7/2.1G 698-894M 6.18.1 Description of LTE2448: FASB 2.4m RAS 1.9G 1.7/2.1G 698894M Introduction to the feature This feature introduces Flexi Radio Antenna System (RAS) FASB. FASB physically encapsulates the RRH into the antenna enclosure. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits

Issue: 01D

DN09185982

519



This feature provides the following benefits to the operator: • • • • • • •

simplifies cell site design through integration of the radio inside antenna supports multiple frequency bands in one antenna enabling consolidation of antennas in the operator network better RF performance (very low cable loss between antenna and RRH) the 10-port antenna system supports higher order MIMO (4TX) implementation and 4 Way diversity scheme for high bands modular architecture enables field maintenance and RRH upgrades independent from antenna higher gain for low bands use of new lightweight and compact 4.3-10 connectors that have very low, reliable and constant PIM, independent of torque






OMS -


UE


NetAct

Not applicable -


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview RAS consists of the following elements: • • •

Antenna RRH Brackets, covers, cables and accessories

Antenna FASB is a three-cross polarized column antenna (two X-polarized columns for high band: 1695 - 2180 MHz and one X-polarized column for low band 698-894 MHz). FASB has 10 antenna ports using 4.3-10 connectors. RRH FASB encapsulates up to two 4T4R RRHs. The removable back covers provide access to the RRH when performing maintenance in the field. The RRH can be upgraded independent of the antenna. Brackets, covers, cables and accessories

520

DN09185982

Issue: 01D



Brackets that are used to mount Flexi RAS antenna to the pole (with FPKB) or on the wall are installed on both ends of the antenna's extrusion side rails. The bottom covers are removable to allow the RRH to be replaced. System impact Interdependencies between features This feature is related to LTE2420: Supported RAS installation options in FL15A release. 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 performance and capacity as follows: • •

relatively better RF performance due to reduced cable loss between the antenna and RRH support for higher order MIMO (4TX) implementation and 4 Way diversity scheme for high bands

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 322

Sales information

BSW/ASW BSW

Issue: 01D


DN09185982


521



6.19 LTE2449: FASC 2.0m RAS 2.3-2.6G 1.7-2.2G 694960M 6.19.1 Description of LTE2449: FASC 2.0m RAS 2.3-2.6G 1.7-2.2G 694-960M Introduction to the feature This feature introduces Flexi Radio Antenna System (RAS) FASC. FASC physically encapsulates the RRH into the antenna enclosure. Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • • • • • •

simplifies cell site design through integration of the radio inside antenna supports multiple frequency bands in one antenna enabling consolidation of antennas in the operator network better RF performance (very low cable loss between antenna and RRH) the 10-port antenna system supports higher order MIMO (4TX) implementation and 4 Way diversity scheme modular architecture enables field maintenance and RRH upgrades independent from antenna use of new lightweight and compact 4.3-10 connectors that have very low, reliable and constant PIM, independent of torque







OMS -

Not supported

UE -


NetAct -


MME -

SAE GW -

Additional hardware requirements This feature requires no new or additional hardware. Functional description Functional overview RAS consists of the following elements:

522

DN09185982

Issue: 01D


• • •


Antenna RRH Brackets, covers, cables and accessories

Antenna FASC is a three-cross polarized column antenna (two X-polarized columns for high band: 1695 - 2690 MHz and one X-polarized column for low band 694-960 MHz). FASC has 10 antenna ports using 4.3-10 connectors. RRH FASC encapsulates up to two 2T2R RRHs or up to two 4T4R RRHs. The RRH integrated to the antenna can be any Rel 4.0 RRH as long as the antenna supports the frequencies. Ten antenna ports provide connection for up to five 2T2R RRH or three 4T4R RRH. The removable back covers provide access to the RRH when performing maintenance in the field. The RRH can be upgraded independent of the antenna. Brackets, covers, cables and accessories RF and RET cables provide the physical interface between the antenna and the radio. Brackets are installed on both ends of the antenna's extrusion side rails. They are used to mount Flexi RAS antenna to the pole (with FPKB) or on the wall. The bottom covers are removable to allow the RRH to be replaced. System impact Interdependencies between features This feature is related to LTE2420: Supported RAS installation options in FL15A release. 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 performance and capacity as follows: • •

relatively better RF performance due to reduced cable loss between the antenna and RRH support for higher order MIMO (4TX) implementation and 4 Way diversity scheme for high bands

Management data Alarms There are no new alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature.

Issue: 01D

DN09185982

523



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 324

Sales information

BSW/ASW


BSW

-


6.20 LTE2471: FXEE Flexi RFM 3-Pipe 1800 240W 6.20.1 Description of LTE2471: FXEE Flexi RF Module 3TX 1800 Introduction to the feature The LTE2471: FXEE Flexi RFM 3-Pipe 1800 240W feature is a 1800 MHz RF Module that has three power amplifiers enabling it to support one, two, or three sectors with up to 80 W output power at the BTS antenna connectors. HW supports RF sharing with GSM, and GSM only configurations. The size and appearance is similar to existing Flexi RF Modules. The environmental protection class is IP65. The same RF Module HW can be used as powerful one sector RRH with max 2x80 W with 4RX. 4RX is separate SW feature (4RX bandwidth limited to 60 MHz). Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature provides the following benefits to the operator: • • • • • • • • •

Full utilization of fragmented 1800 MHz RF spectrum for GSM and LTE with two RF Module for 3 sectors. FXEE can be used in feeder-less site (optical and DC cable up to 200 m). Cost and power efficient as well as size- and weight-optimized 3-sector 3TX MIMO BTS site. 2/3 of DC and 2/3 of optical cabling compared to 3-sector site with Remote RF Heads (RRH). Operating temperature range: -35°C to +55°C (-31°F to +131°F). Easy installation. Minor visual impact. HW prepared to support one sector 3x80 W 3TX MIMO with 4RX. Small weight and wind load.


524

DN09185982

Issue: 01D


Table 325



System release FDD-LTE 15A Flexi Zone Controller Not applicable



OMS

UE

Not applicable

3GPP R8 mandatory


NetAct


MME

SAE GW

Not applicable Not applicable Not applicable

Additional hardware requirements This feature requires no new or additional hardware. Functional description The main features of the LTE2471: FXEE Flexi RFM 3-Pipe 1800 240W are as follows: • • • • • • •

3GPP band 3 1800 MHz support. Output power 3 x 80 W. Configurable power levels: 8, 20, 40, 60 or 80 W. Instantaneous bandwidth (iBW) max 75MHz DL, and up to 60MHz UL for GSM/Multimode (Up to 75 Mhz With RDSA RX diversity cabling). DL and UL filter bandwidth: 75 MHz. Supported bandwidths: 5, 10, 15, 20 MHz. 3 U high with Flexi platform mechanics.

The following are some basic LTE Configurations with one FXEE for one sector: • • • • •

1 LTE cell @ max 20 MHz LTE bandwidth and 2TX MIMO / 2RX. 2 LTE cells @ max 20 MHz + max 20 MHz LTE bandwidth and 2TX MIMO / 2RX. 8+8, 20+20, 40+40, 60+60 or 80+80 W 2TX per sector (by branch activation and MIMO SW licenses). HW ready for 4RX (support requires 4RX SW license). 8, 20, 40, 60 W or 80 W 1TX 2RX mode for 1, 2 or 3 sectors (by branch activation SW licenses).

The following are some basic LTE Configurations with two FXEE for two or three sectors: • • • •

1+1 or 1+1+1 LTE cells @ max 20 MHz LTE bandwidth and 2TX MIMO / 2RX. 2+2 or 2+2+2 LTE cells @ max 20 MHz + max 20 MHz LTE bandwidth and 2TX MIMO / 2RX. 8+8, 20+20, 40+40, 60+60 or 80+80 W 2TX mode per sector (by branch activation and MIMO SW licenses). HW ready for 4RX (support requires 4RX SW license).

The following are examples of LTE+GSM configurations: • •

Issue: 01D

Up to 20 MHz LTE (40W) + 4 GSM TRX (4x10W) carriers per TX PA path. 5 MHz LTE 2TX MIMO + 6 GSM TRX carriers (3+3) per sector from 2 TX PA pipes. 1-3 sectors supported.

DN09185982

525



The following are basic GSM configurations: • •

4/4/4@20W iBW 40 MHz Up to 8 GSM TRX carriers (4+4) per sector from 2 TX PA pipes.

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. BTS faults and reported alarms 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 326

Sales information

BSW/ASW BSW

526


DN09185982


Issue: 01D

Fdd15A Desc

Recommend Documents