Nokia Networks
LTE Radio Access, Rel. FDDLTE 16A, Operating Documentation, Pre-release, Issue 01 FDD-LTE16A, Feature Descriptions and Instructions DN09237915 Issue 01 Draft Approval Date 2016-04-24
FDD-LTE16A, Feature Descriptions and Instructions
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof. The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of the process of continuous development and improvement of the documentation. This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the right to change any such information and statements without notice. Nokia Solutions and Networks has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product will be uninterrupted or error-free. NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT. This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © 2016 Nokia Solutions and Networks. All rights reserved.
f
Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for any additional information.
2
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table of Contents This document has 409 pages
Summary of changes................................................................... 26
1
Introduction.................................................................................. 27
2
Activating and deactivating LTE features using BTS Site Manager. 28
3
Descriptions of radio resource management and telecom features. 30 LTE1092: Uplink Carrier Aggregation – 2CC............................... 30 LTE1092 benefits......................................................................... 30 LTE1092 functional description.................................................... 30 LTE1092 system impact............................................................... 34 LTE1092 reference data...............................................................35 LTE1130: Dynamic PUCCH Allocation.........................................37 LTE1130 benefits..........................................................................37 LTE1130 functional description.................................................... 37 LTE1130 system impact............................................................... 40 LTE1130 reference data............................................................... 41 LTE1723: S1-based Handover towards Home eNB.....................46 LTE1723 benefits......................................................................... 47 LTE1723 functional description.................................................... 47 LTE1723 system impact............................................................... 47 LTE1723 reference data...............................................................48 LTE2057: Extended Measurement Control ................................. 50 LTE2057 benefits......................................................................... 51 LTE2057 functional description.................................................... 51 Measurements and measurement reports................................... 51 Inter-frequency handover............................................................. 52 LTE2057 overview........................................................................52 LTE2057 system impact............................................................... 55 LTE2057 reference data...............................................................56 LTE2276: Measurement-based SCell Selection...........................58 LTE2276 benefits......................................................................... 58 LTE2276 functional description.................................................... 58 LTE2276 system impact............................................................... 60 LTE2276 reference data...............................................................61 LTE2291: Support for Carrier Aggregation on CL16A Release... 63 LTE2291 benefits......................................................................... 63 LTE2291 functional description.................................................... 63 LTE2291 system impact............................................................... 64 LTE2291 reference data...............................................................65 LTE2400: Support of User Location Information ......................... 66
3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.4 3.4.1 3.4.2 3.4.2.1 3.4.2.2 3.4.2.3 3.4.3 3.4.4 3.5 3.5.1 3.5.2 3.5.3 3.5.4 3.6 3.6.1 3.6.2 3.6.3 3.6.4 3.7
Issue: 01 Draft
DN09237915
3
FDD-LTE16A, Feature Descriptions and Instructions
3.7.1 3.7.2 3.7.2.1 3.7.2.2 3.7.2.3 3.7.3 3.7.4 3.8 3.8.1 3.8.2 3.8.3 3.8.4 3.9 3.9.1 3.9.2 3.9.3 3.9.4 3.10 3.10.1 3.10.2 3.10.3 3.10.4 3.11 3.11.1 3.11.2 3.11.3 3.11.4 3.12 3.12.1 3.12.2 3.12.3 3.12.4 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.14.4
4
LTE2400 benefits......................................................................... 66 LTE2400 functional description.................................................... 66 S1 Application Protocol................................................................ 66 Location Report message............................................................ 67 LTE2400 overview........................................................................67 LTE2400 system impact............................................................... 68 LTE2400 reference data...............................................................68 LTE2445: Combined Supercell.....................................................69 LTE2445 benefits......................................................................... 69 LTE2445 functional description.................................................... 69 LTE2445 system impact............................................................... 73 2445 reference data..................................................................... 75 LTE2460: Automatic Access Class Barring with PLMN Disabling.... 78 LTE2460 benefits......................................................................... 78 LTE2460 functional description.................................................... 78 LTE2460 system impact............................................................... 79 LTE2460 reference data...............................................................79 LTE2479: 256QAM in Downlink................................................... 81 LTE2479 benefits......................................................................... 81 LTE2479 functional description.................................................... 81 LTE2479 system impact............................................................... 82 LTE2479 reference data...............................................................83 LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I........................................................................... 85 LTE2511 benefits..........................................................................86 LTE2511 functional description.................................................... 86 LTE2511 system impact............................................................... 87 LTE2511 reference data............................................................... 87 LTE2527: Additional Carrier Aggregation Band Combinations – IV. 88 LTE2527 benefits......................................................................... 88 LTE2527 functional description.................................................... 89 LTE2527 system impact............................................................... 90 LTE2527 reference data...............................................................90 LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II................................................................................................. 91 LTE2528 benefits......................................................................... 91 LTE2528 functional description.................................................... 91 LTE2528 system impact............................................................... 92 LTE2528 reference data...............................................................93 LTE2531: FDD Downlink Carrier Aggregation 4CC .................... 94 LTE2531 benefits......................................................................... 94 LTE2531 functional description.................................................... 94 LTE2531 system impact............................................................... 97 LTE2531 reference data...............................................................98
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
3.15 3.15.1 3.15.2 3.15.2.1 3.15.2.2 3.15.3 3.15.4 3.16 3.16.1 3.16.2 3.16.2.1 3.16.2.2 3.16.2.3 3.16.2.4 3.16.3 3.16.4 3.17 3.17.1 3.17.2 3.17.2.1 3.17.2.1.1 3.17.2.1.2 3.17.2.1.3 3.17.2.2 3.17.3 3.17.4 3.18 3.18.1 3.18.2 3.18.3 3.18.4 3.19 3.19.1 3.19.2 3.19.2.1 3.19.2.2 3.19.3 3.19.4 3.20 3.20.1 3.20.2 3.20.2.1
Issue: 01 Draft
LTE2551: RSRQ-based A5........................................................ 107 LTE2551 benefits....................................................................... 107 LTE2551 functional description.................................................. 107 LTE2551 overview......................................................................108 A5 RSRQ and RSRP conditions.................................................110 LTE2551 system impact............................................................. 110 LTE2551 reference data............................................................. 111 LTE2557: Supplemental DL Carrier Extension...........................112 LTE2557 benefits........................................................................112 LTE2557 functional description.................................................. 112 A barred cell from the perspective of LTE2557: Supplemental DL Carrier Extension........................................................................114 Mobility towards supplemental DL carrier (SDLC)......................114 Load-balancing relation with supplemental DL carrier (SDLC)........ 114 Idle-mode mobility relation with supplemental DL carrier (SDLC).... 114 LTE2557 system impact............................................................. 114 LTE2557 reference data............................................................. 115 LTE2559: ARP-based Partial Admission Control for Handover ...... 116 LTE2559 benefits........................................................................116 LTE2559 functional description.................................................. 116 EPS bearers............................................................................... 116 Bearer management...................................................................118 Quality of service (QoS)............................................................. 119 ARP............................................................................................121 LTE2559 overview......................................................................121 LTE2559 system impact............................................................. 123 LTE2559 reference data.............................................................125 LTE2564: Centralized RAN CL16A Release.............................. 126 LTE2564 benefits....................................................................... 126 LTE2564 functional description.................................................. 127 LTE2564 system impact............................................................. 127 LTE2564 reference data.............................................................128 LTE2572: RSRQ-based B2........................................................ 130 LTE2572 benefits....................................................................... 130 LTE2572 functional description.................................................. 130 LTE2572 overview......................................................................132 B2 RSRQ conditions.................................................................. 132 LTE2572: system impact............................................................ 133 LTE2572 reference data.............................................................133 LTE2583: Support of High-power UE......................................... 135 LTE2583 benefits....................................................................... 135 LTE2583 functional description.................................................. 135 Extended power headroom report (ePHR).................................136
DN09237915
5
FDD-LTE16A, Feature Descriptions and Instructions
3.20.2.2 3.20.2.3 3.20.3 3.20.4 3.21 3.21.1 3.21.2 3.21.3 3.21.4 3.22 3.22.1 3.22.2 3.22.3 3.22.4 3.23 3.23.1 3.23.2 3.23.3 3.23.4 3.24 3.24.1 3.24.2 3.24.3 3.24.4 3.25 3.25.1 3.25.2 3.25.3 3.25.4 3.26 3.26.1 3.26.2 3.26.3 3.26.4 3.27 3.27.1 3.27.2 3.27.2.1 3.27.2.2 3.27.2.3 3.27.3 3.27.4 3.28 3.28.1
6
Detection of power-class-1 UEs based on the ePHR................ 136 Joint scheduling of UEs with a different power class within the same cell.................................................................................... 136 LTE2583 system impact............................................................. 137 LTE2583 reference data.............................................................137 LTE2601: CA-aware Idle Mode Load Balancing........................ 139 LTE2601 benefits....................................................................... 139 LTE2601 functional description.................................................. 139 LTE2601 system impact............................................................. 141 LTE2601 reference data.............................................................142 LTE2611: Introduction of Public Safety Specific QCI Bearers....145 LTE2611 benefits........................................................................146 LTE2611 functional description.................................................. 146 LTE2611 system impact............................................................. 147 LTE2611 reference data............................................................. 149 LTE2612: ProSe Direct Communications for Public Safety........159 LTE2612 benefits....................................................................... 159 LTE2612 functional description.................................................. 159 LTE2612 system impact............................................................. 161 LTE2612 reference data.............................................................165 LTE2629: FDD-LTE Dual-cell (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS......................................................169 LTE2629 benefits....................................................................... 169 LTE2629 functional description.................................................. 169 LTE2629 system impact............................................................. 170 LTE2629 reference data.............................................................171 LTE2630: Uplink Control Information Only Transmission...........172 LTE2630 benefits....................................................................... 172 LTE2630 functional description.................................................. 172 LTE2630 system impact............................................................. 173 LTE2630 reference data.............................................................173 LTE2754: Frequency Bands Priority Change in mFBI................175 LTE2754 benefits....................................................................... 175 LTE2754 functional description.................................................. 175 LTE2754 system impact............................................................. 176 LTE2754 reference data.............................................................177 LTE2832: SRVCC Due to Admission Control Rejection ............179 LTE2832 benefits....................................................................... 179 LTE2832 functional description.................................................. 179 VoLTE general information......................................................... 179 SRVCC general information....................................................... 179 LTE2832 overview......................................................................180 LTE2832 system impact............................................................. 182 LTE2832 reference data.............................................................184 LTE3092: Enhanced CSAT Support for LTE-U Small Cells....... 185 LTE3092 benefits....................................................................... 185
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
3.28.2 3.28.3 3.28.4 3.29 3.29.1 3.29.2 3.29.3 3.29.4
LTE3092 functional description.................................................. 186 LTE3092 system impact............................................................. 186 LTE3092 reference data.............................................................187 LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells..... 189 LTE3093 benefits....................................................................... 189 LTE3093 functional description.................................................. 189 LTE3093 system impact............................................................. 190 LTE3093 reference data.............................................................190
4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.2
Descriptions of transport and transmission features.................. 193 LTE563: Synchronous Ethernet Generation.............................. 193 LTE563 benefits......................................................................... 193 LTE563 functional description.................................................... 193 LTE563 system impact............................................................... 196 LTE563 reference data...............................................................196 LTE1554: 10GBase-SR Optical GE Interface, LTE1652: Small Form Factor Pluggable (Plus) Slot (SFP/SFP+ Slot), LTE1738: 10GBase-LR Optical GE Interface............................................. 198 LTE1554, LTE1652, LTE1738 benefits.......................................198 LTE1554, LTE1652, LTE1738 functional description................. 198 LTE1554, LTE1652, LTE1738 system impact............................ 200 LTE1554, LTE1652, LTE1738 reference data............................ 200 LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels......................... 202 LTE1980 benefits....................................................................... 202 LTE1980 functional description.................................................. 202 LTE1980 system impact............................................................. 204 LTE1980 reference data.............................................................205 LTE1981: IPv6 for S-plane......................................................... 205 LTE1981 benefits....................................................................... 205 LTE1981 functional description.................................................. 206 LTE1981: system impact............................................................ 206 LTE1981 reference data.............................................................207 LTE2417 IP Traffic Capacity.......................................................208 LTE2417 benefits....................................................................... 208 LTE2417 functional description.................................................. 209 LTE2417 system impact............................................................. 213 LTE2417 reference data.............................................................213 LTE2645: GNSS Manual Location Entry for Macro BTS............215 LTE2645 benefits....................................................................... 215 LTE2645 functional description.................................................. 215 LTE2645 system impact............................................................. 218 LTE2645 reference data.............................................................219 Other instructions....................................................................... 221 LTE2763: Fronthaul Passive WDM............................................ 224 LTE2763 benefits....................................................................... 225 LTE2763 functional description.................................................. 225
4.2.1 4.2.2 4.2.3 4.2.4 4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.4 4.4.1 4.4.2 4.4.3 4.4.4 4.5 4.5.1 4.5.2 4.5.3 4.5.4 4.6 4.6.1 4.6.2 4.6.3 4.6.4 4.6.5 4.7 4.7.1 4.7.2
Issue: 01 Draft
DN09237915
7
FDD-LTE16A, Feature Descriptions and Instructions
8
4.7.3 4.7.4
LTE2763 system impact............................................................. 225 LTE2763 reference data.............................................................226
5 5.1 5.1.1 5.1.2 5.1.3 5.1.4 5.2 5.2.1 5.2.2 5.2.2.1 5.2.2.2 5.2.3 5.2.4 5.3 5.3.1 5.3.2 5.3.3 5.3.4 5.4 5.4.1 5.4.2 5.4.3 5.4.4 5.5 5.5.1 5.5.2 5.5.3 5.5.4 5.6 5.6.1 5.6.2 5.6.3 5.6.4 5.7 5.7.1 5.7.2 5.7.3 5.7.4 5.8 5.8.1 5.8.2 5.8.3 5.8.4
Descriptions of operability features ........................................... 227 LTE678: MDT – UE Radio Link Failure Report Evaluation ........227 LTE678 benefits......................................................................... 227 LTE678 functional description.................................................... 227 LTE678 system impact............................................................... 228 LTE678 reference data...............................................................228 LTE2121: Radio Unit Reset........................................................230 LTE2121 benefits....................................................................... 230 LTE2121 functional description.................................................. 230 Reset of radio unit via NetAct configuration plan....................... 230 Reset of radio unit via BTS Site Manager interface................... 231 LTE2121 system impact............................................................. 232 LTE2121 reference data.............................................................232 LTE2202: Addition of MAC Measurements to Cell Trace...........233 LTE2202 benefits....................................................................... 233 LTE2202 functional description.................................................. 233 LTE2202 system impact............................................................. 234 LTE2202 reference data.............................................................235 LTE2237: Log Collection Triggered by BTS Fault Cancellation. 236 LTE2237 benefits....................................................................... 237 LTE2237 functional description.................................................. 237 LTE2237 system impact............................................................. 238 LTE2237 reference data.............................................................238 LTE2331: Multi-language Support for Selected Parameters...... 240 LTE2331 benefits....................................................................... 240 LTE2331 functional description.................................................. 240 LTE2331 system impact............................................................. 241 LTE2331 reference data.............................................................241 LTE2360: Login Restriction with CNUM..................................... 243 LTE2360 benefits....................................................................... 243 LTE2360 functional description.................................................. 243 LTE2360 system impact............................................................. 244 LTE2360 reference data.............................................................245 LTE2361: Configurable BTS Login Banner................................ 246 LTE2361 benefits....................................................................... 246 LTE2361 functional description.................................................. 246 LTE2361 system impact............................................................. 246 LTE2361 reference data.............................................................247 LTE2403: MHAs Auto-detection and Configuration................... 248 LTE2403 benefits....................................................................... 248 LTE2403 functional description.................................................. 248 LTE2403 system impact............................................................. 250 LTE2403 reference data.............................................................250
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
5.8.5 5.9 5.9.1 5.9.2 5.9.3 5.9.4 5.10 5.10.1 5.10.2 5.10.3 5.10.4 5.11 5.11.1 5.11.2 5.11.3 5.11.4 5.12 5.12.1 5.12.2 5.12.3 5.12.4 5.13 5.13.1 5.13.2 5.13.3 5.13.4 5.14 5.14.1 5.14.2 5.14.3 5.14.4 5.15 5.15.1 5.15.2 5.15.3 5.15.4 5.16 5.16.1 5.16.2 5.16.3 5.16.4 5.17
Issue: 01 Draft
Other instructions....................................................................... 251 LTE2507: Energy Efficiency Shut Down Mode with RF Sharing...... 252 LTE2507 benefits....................................................................... 253 LTE2507 functional description.................................................. 253 LTE2507 system impact............................................................. 254 LTE2507 reference data.............................................................255 LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring.................................................................................. 256 LTE2508 benefits....................................................................... 256 LTE2508 functional description.................................................. 256 LTE2508 system impact............................................................. 258 LTE2508 reference data.............................................................259 LTE2562: ANR Inter-RAT 1xRTT – O&M Assisted.................... 261 LTE2562 benefits....................................................................... 261 LTE2562 functional description.................................................. 261 LTE2562 system impact............................................................. 263 LTE2562 reference data.............................................................264 LTE2591: UE-level MRO............................................................ 266 LTE2591 benefits....................................................................... 266 LTE2591 functional description.................................................. 266 LTE2591 system impact............................................................. 267 LTE2591 reference data.............................................................267 LTE2621: eNodeB Limitation Actions for License Management in LTE............................................................................................. 269 LTE2621 benefits....................................................................... 269 LTE2621 functional description.................................................. 269 LTE2621 system impact............................................................. 270 LTE2621 reference data.............................................................271 LTE2633: System Upgrade to FDD-LTE 16A.............................272 LTE2633 benefits....................................................................... 272 LTE2633 functional description.................................................. 272 LTE2633 system impact............................................................. 275 LTE2633 reference data.............................................................275 LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules........................................................................... 276 LTE2816 benefits....................................................................... 276 LTE2816 functional description.................................................. 277 LTE2816 system impact............................................................. 277 LTE2816 reference data.............................................................278 LTE2828: LNCEL LNBTS Refactoring ...................................... 279 LTE2828 benefits....................................................................... 279 LTE2828 functional description.................................................. 279 LTE2828 system impact............................................................. 282 LTE2828 reference data.............................................................285 LTE3043: Remote Power Port Control for FPFD PDU ..............293
DN09237915
9
FDD-LTE16A, Feature Descriptions and Instructions
5.17.1 5.17.2 5.17.3 5.17.4 5.18 5.18.1 5.18.2 5.18.3 5.18.4 5.18.5
LTE3043 benefits....................................................................... 293 LTE3043 functional description.................................................. 293 LTE3043 system impact............................................................. 295 LTE3043 reference data.............................................................296 LTE3051: Eden-NET Replacing iSON as Centralized SON Solution...................................................................................... 297 LTE3051 benefits....................................................................... 298 LTE3051 functional description.................................................. 298 LTE3051 system impact............................................................. 300 LTE3051 reference data.............................................................304 Other instructions....................................................................... 304
6 6.1 6.1.1 6.1.2 6.1.3 6.1.4 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.3 6.3.1 6.3.2 6.3.3 6.3.4 6.4 6.4.1 6.4.2 6.4.3 6.4.4 6.5 6.5.1 6.5.2 6.5.3 6.5.4
Descriptions of performance monitoring features...................... 307 LTE2140: New Performance Counters LTE16A.........................307 LTE2140 benefits....................................................................... 307 LTE2140 functional description.................................................. 307 LTE2140 system impact............................................................. 308 LTE2140 reference data.............................................................308 LTE2493: Enhanced VoLTE Performance Monitoring................315 LTE2493 benefits....................................................................... 315 LTE2493 functional description.................................................. 315 LTE2493 system impact............................................................. 316 LTE2493 reference data.............................................................316 LTE2766: Flexible QCI/ARP PM Counter Profiles......................319 LTE2766 benefits....................................................................... 319 LTE2766 functional description.................................................. 319 LTE2766 system impact............................................................. 320 LTE2766 reference data.............................................................321 LTE2804: RSRP and RSRQ Histograms................................... 325 LTE2804 benefits....................................................................... 325 LTE2804 functional description.................................................. 325 LTE2804 system impact............................................................. 326 LTE2804 reference data.............................................................326 LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles.............. 329 LTE2915 benefits....................................................................... 329 LTE2915 functional description.................................................. 330 LTE2915 system impact............................................................. 331 LTE2915 reference data.............................................................331
7 7.1
Description of Flexi Zone Controller features.............................335 LTE2576: Integrated GMC and BC Support on Flexi Zone Controller....................................................................................335 LTE2576 benefits....................................................................... 335 LTE2576 functional description.................................................. 335 LTE2576 system impact............................................................. 335 LTE2576 reference data.............................................................336 LTE2373: Vendor Certificate Usage for Flexi Zone Controller... 337
7.1.1 7.1.2 7.1.3 7.1.4 7.2
10
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Issue: 01 Draft
7.2.1 7.2.2 7.2.3 7.2.4
LTE2373 benefits....................................................................... 337 LTE2373 functional description.................................................. 337 LTE2373 system impact............................................................. 337 LTE2373 reference data.............................................................338
8 8.1 8.1.1 8.1.2 8.1.3 8.1.4 8.2 8.2.1 8.2.2 8.2.3 8.2.4
Descriptions of OAM/Troubleshoot features.............................. 339 LTE2805: Monitoring RX Sensitivity .......................................... 339 LTE2805 benefits....................................................................... 339 LTE2805 functional description.................................................. 339 LTE2805 system impact............................................................. 340 LTE2805 reference data.............................................................340 LTE2883: Application of Diagnostic and Maintenance for Intelligent Network......................................................................341 LTE2883 benefits....................................................................... 341 LTE2883 functional description.................................................. 341 LTE2883 system impact............................................................. 342 LTE2883 reference data.............................................................342
9 9.1 9.1.1 9.1.2 9.1.3 9.1.4 9.2 9.2.1 9.2.2 9.2.3 9.2.4 9.3 9.3.1 9.3.2 9.3.3 9.3.4 9.4 9.4.1 9.4.2 9.4.3 9.4.4 9.5 9.5.1 9.5.2 9.5.3 9.5.4 9.6 9.6.1 9.6.2
Descriptions of BTS site solution features................................. 343 LTE180: Cell Radius Max 100 km.............................................. 343 LTE180 benefits......................................................................... 343 LTE180 functional description.................................................... 343 LTE180 system impact............................................................... 343 LTE180 reference data...............................................................345 LTE2114: AirScale Common ASIA............................................. 346 LTE2114 benefits........................................................................346 LTE2114 functional description.................................................. 347 LTE2114 system impact............................................................. 348 LTE2114 reference data............................................................. 349 LTE2252: FSM OD-Cabinet FCOB............................................ 350 LTE2252: benefits...................................................................... 350 LTE2252 functional description.................................................. 351 LTE2252 system impact............................................................. 351 LTE2252 reference data.............................................................352 LTE2261: AirScale Capacity ABIA............................................. 352 LTE2261 benefits....................................................................... 352 LTE2261 functional description.................................................. 353 LTE2261 system impact............................................................. 354 LTE2261 reference data.............................................................354 LTE2262: AirScale Subrack AMIA..............................................355 LTE2262 benefits....................................................................... 355 LTE2262 functional description.................................................. 356 LTE2262 system impact............................................................. 358 LTE2262 reference data.............................................................359 LTE2335: Outdoor GNSS receiver FYGM .................................359 LTE2335 benefits....................................................................... 359 LTE2335 functional description.................................................. 360
DN09237915
11
FDD-LTE16A, Feature Descriptions and Instructions
9.6.3 9.6.4 9.7 9.7.1 9.7.2 9.7.3 9.7.4 9.8 9.8.1 9.8.2 9.8.3 9.8.4 9.9 9.9.1 9.9.2 9.9.3 9.9.4 9.10 9.10.1 9.10.2 9.10.3 9.10.4 9.11 9.11.1 9.11.2 9.11.3 9.11.4 9.12 9.12.1 9.12.2 9.12.3 9.12.4 9.13 9.13.1 9.13.2 9.13.3 9.13.4 9.14 9.14.1 9.14.2 9.14.3 9.14.4 9.15 9.15.1
12
LTE2335 system impact............................................................. 361 LTE2335 reference data.............................................................361 LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator ................................................................. 363 LTE2387 benefits....................................................................... 363 LTE2387 functional description.................................................. 363 LTE2387 system impact............................................................. 366 LTE2387 reference data.............................................................366 LTE2516: FRIJ AirScale RRH 4T4R B66 160 W........................367 LTE2516 benefits....................................................................... 367 LTE2516 functional description.................................................. 367 LTE2516 system impact............................................................. 369 LTE2516 reference data.............................................................370 LTE2517: AirScale HW capacity activation licence.................... 371 LTE2517 benefits....................................................................... 371 LTE2517 functional description.................................................. 371 LTE2517 system impact............................................................. 371 LTE2517 reference data.............................................................372 LTE2605: 4RX Diversity 20MHz Optimized Configurations....... 373 LTE2605 benefits....................................................................... 373 LTE2605 functional description.................................................. 373 LTE2605 system impact............................................................. 373 LTE2605 reference data.............................................................374 LTE2609: Dual Carrier Support LTE1.4 and LTE3..................... 375 LTE2609 benefits....................................................................... 375 LTE2609 functional description.................................................. 375 LTE2609 system impact............................................................. 375 LTE2609 reference data.............................................................376 LTE2610: Support for classical WCDMA/LTE RF-sharing on 2Tx/2Rx RRH FHDB.................................................................. 377 LTE2610 benefits....................................................................... 377 LTE2610 functional description.................................................. 377 LTE2610 system impact............................................................. 377 LTE2610 reference data.............................................................378 LTE2637: Quad Carrier on Single RF Unit ................................ 378 LTE2637 benefits....................................................................... 379 LTE2637 functional description.................................................. 379 LTE2637 system impact............................................................. 379 LTE2637 reference data.............................................................380 LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W.........................380 LTE2650 benefits....................................................................... 381 LTE2650 functional description.................................................. 381 LTE2650 system impact............................................................. 382 LTE2650 reference data.............................................................382 LTE2679: FRCJ Flexi RRH 2T4R 873 120 W............................ 382 LTE2679 benefits....................................................................... 383
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
9.15.2 9.15.3 9.15.4 9.16 9.16.1 9.16.2 9.16.3 9.16.4 9.17 9.17.1 9.17.2 9.17.3 9.17.4 9.18 9.18.1 9.18.2 9.18.3 9.18.4 9.19 9.19.1 9.19.2 9.19.3 9.19.4 9.20 9.20.1 9.20.2 9.20.3 9.20.4 9.21 9.21.1 9.21.2 9.21.3 9.21.4 9.22 9.22.1 9.22.2 9.22.3 9.22.4 9.23 9.23.1 9.23.2 9.23.3
Issue: 01 Draft
LTE2679 functional description.................................................. 383 LTE2679 system impact............................................................. 383 LTE2679 reference data.............................................................384 LTE2680: FHEL AirScale RRH 2T2R B3 120 W........................ 385 LTE2680 benefits....................................................................... 385 LTE2680 functional description.................................................. 385 LTE2680 system impact............................................................. 387 LTE2680 reference data.............................................................387 LTE2722: Basic FDD Configurations for AirScale...................... 388 LTE2722 benefits....................................................................... 388 LTE2722 functional description.................................................. 388 LTE2722 system impact............................................................. 389 LTE2722 reference data.............................................................390 LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W......................... 390 LTE2767 benefits....................................................................... 391 LTE2767 functional description.................................................. 391 LTE2767 system impact............................................................. 392 LTE2767 reference data.............................................................393 LTE2880: Support of classical WCDMA/LTE RF-sharing on 4Tx/4Rx Remote Radio Head (RRH Rel. 4.3-family)................. 393 LTE2880 benefits....................................................................... 394 LTE2880 functional description.................................................. 394 LTE2880 system impact............................................................. 394 LTE2880 reference data.............................................................395 LTE2911: Classical LTE-GSM RF-sharing with FXEF Flexi RFM 3pipe 1800 240 W........................................................................ 395 LTE2911 benefits........................................................................396 LTE2911 functional description.................................................. 396 LTE2911 system impact............................................................. 397 LTE2911 reference data............................................................. 397 LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz).... 398 LTE2914 benefits....................................................................... 398 LTE2914 functional description.................................................. 398 LTE2914 system impact............................................................. 399 LTE2914 reference data.............................................................399 LTE2920: Classical WCDMA/LTE-RF sharing support for narrowband LTE (LTE 1.4 and 3 MHz).......................................400 LTE2920 benefits....................................................................... 400 LTE2920 functional description.................................................. 400 LTE2920 system impact............................................................. 401 LTE2920 reference data.............................................................401 LTE2950: B3+B7 FZ G2 Indoor Multi-Band Pico (FW2EHA, FW2EHWA)................................................................................402 LTE2950 benefits....................................................................... 402 LTE2950 functional description.................................................. 403 LTE2950 system impact............................................................. 403
DN09237915
13
FDD-LTE16A, Feature Descriptions and Instructions
9.23.4 9.24 9.24.1 9.24.2 9.24.3 9.24.4 9.25 9.25.1 9.25.2 9.25.3 9.25.4
14
LTE2950 reference data.............................................................404 LTE3027: FRPD Flexi RFM 6-pipe 700 240 W.......................... 405 LTE3027 benefits....................................................................... 405 LTE3027 functional description.................................................. 405 LTE3027 system impact............................................................. 406 LTE3027 reference data.............................................................406 LTE3177: B7+B7 FZ G2 Indoor Multi-Band Pico (FW2HHA, FW2HHWA)................................................................................407 LTE3177 benefits....................................................................... 407 LTE3177 functional description.................................................. 408 LTE3177 system impact............................................................. 408 LTE3177 reference data.............................................................409
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
List of Figures
Issue: 01 Draft
Figure 1
Example of co-located cells with a specified PCell, DL+UL SCell, and DL-only SCell......................................................................................30
Figure 2
LTE2057 functionality......................................................................... 54
Figure 3
SCell discovery measurement............................................................58
Figure 4
Scenario 1 for LTE2276...................................................................... 60
Figure 5
Scenario 2 for LTE2276...................................................................... 60
Figure 6
Location Report procedure................................................................. 67
Figure 7
Downlink carrier aggregation for four component carriers..................94
Figure 8
LTE A5 event.................................................................................... 109
Figure 9
LTE/EPC service data flows..............................................................117
Figure 10
LTE/EPC EPS high-level bearer model............................................ 118
Figure 11
LTE B2 event.................................................................................... 132
Figure 12
Inter-band carrier aggregation example........................................... 140
Figure 13
An example of deployment of dual-cell operation cells.................... 170
Figure 14
HO messages...................................................................................180
Figure 15
Example of SRVCC due to admission control rejection (temporary overbooking is possible)................................................................... 181
Figure 16
SyncE master functionality – SyncE is synchronization reference... 194
Figure 17
SyncE master functionality – ToP is synchronization reference....... 194
Figure 18
SyncE master functionality in eNB – E1/T1/JT1, 1 pps or ext. 2M048 is synchronization reference.............................................................195
Figure 19
SyncE master functionality in an eNB holdover mode......................196
Figure 20
SFP+ slot.......................................................................................... 199
Figure 21
10GBase interface............................................................................200
Figure 22
Overview of IPsec implementation in LTE O&M network................. 203
Figure 23
IPv6 in the IPsec policy.................................................................... 204
Figure 24
LTE1981 Overview........................................................................... 206
Figure 25
Overview of the LTE2417: IP Traffic Capacity feature...................... 209
Figure 26
KPI generation..................................................................................210
Figure 27
KPI average daily IP traffic volume................................................... 211
Figure 28
KPI quarterly IP traffic volume ......................................................... 212
Figure 29
Typical environment with a minimum of four satellites..................... 216
Figure 30
Urban canyon environment.............................................................. 217
Figure 31
Possible Deployment of SAR-O/VWM..............................................225
Figure 32
Features related to the log collection functionality............................237
Figure 33
Local account log-in scenarios......................................................... 244
Figure 34
Default login banner visible in BTS Site Manager............................ 246
Figure 35
From power meter to Energy Efficiency Monitoring .........................257
Figure 36
An example of Energy Efficiency Monitoring display in BTS SM (may differ in later releases)...................................................................... 258
DN09237915
15
FDD-LTE16A, Feature Descriptions and Instructions
16
Figure 37
Radio module memory threshold level............................................. 277
Figure 38
New MOCs in the LNBTS tree..........................................................281
Figure 39
New MOCs in the LNCEL tree..........................................................282
Figure 40
Connection flow with a PDU power port........................................... 294
Figure 41
Example of Power Control dialog window in BTS SM...................... 295
Figure 42
AirScale SM Indoor...........................................................................347
Figure 43
Front panel of the ASIA.................................................................... 348
Figure 44
AirScale SM Indoor...........................................................................353
Figure 45
Front panel of the ABIA.................................................................... 354
Figure 46
AMIA AirScale Subrack (factory default).......................................... 357
Figure 47
Nokia AirScale System Module Indoor in maximum configuration (2xASIA, 6xABIA)............................................................................. 358
Figure 48
Exemplary LTE2387 cabling configuration - Example 1................... 364
Figure 49
Exemplary LTE2387 cabling configuration - Example 2................... 365
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
List of Tables
Issue: 01 Draft
Table 1
LTE1092 hardware and software requirements..................................35
Table 2
Existing counters related to LTE1092................................................. 36
Table 3
Existing parameters related to LTE1092............................................ 36
Table 4
LTE1092 sales information................................................................. 36
Table 5
CSI and SR periodicity values............................................................ 37
Table 6
LTE1130: Dynamic PUCCH Allocation hardware and software requirements.......................................................................................41
Table 7
New BTS faults introduced by LTE1130............................................. 41
Table 8
New counters introduced by LTE1130................................................ 41
Table 9
New parameters introduced by LTE1130............................................42
Table 10
Parameters modified by LTE1130.......................................................43
Table 11
Existing parameters related to LTE1130.............................................44
Table 12
LTE1130 sales information................................................................. 46
Table 13
LTE1723 hardware and software requirements..................................48
Table 14
New counters introduced by LTE1723................................................49
Table 15
New parameters introduced by LTE1723........................................... 50
Table 16
Existing parameters supported by LTE1723.......................................50
Table 17
LTE1723 sales information................................................................. 50
Table 18
LTE2057 hardware and software requirements..................................56
Table 19
New parameters introduced by LTE2057........................................... 57
Table 20
Existing parameters related to LTE2057............................................ 57
Table 21
LTE2057 sales information................................................................. 57
Table 22
LTE2276 hardware and software requirements..................................61
Table 23
New parameters introduced by LTE2276........................................... 62
Table 24
Existing parameters related to LTE2276............................................ 63
Table 25
LTE2276 sales information................................................................. 63
Table 26
LTE2291 hardware and software requirements..................................65
Table 27
BTS faults related to LTE2291 ...........................................................65
Table 28
Existing parameters related to LTE2291............................................ 66
Table 29
LTE2291 sales information................................................................. 66
Table 30
LTE2400 S1AP messages..................................................................68
Table 31
LTE2400 hardware and software requirements..................................68
Table 32
New parameters introduced by LTE2400........................................... 69
Table 33
LTE2400 sales information................................................................. 69
Table 34
LTE2445 hardware and software requirements..................................76
Table 35
Existing alarms related to LTE2445.................................................... 76
Table 36
New parameters introduced by LTE2445........................................... 76
Table 37
Existing parameters related to LTE2445............................................ 77
Table 38
LTE2445 sales information................................................................. 78
DN09237915
17
FDD-LTE16A, Feature Descriptions and Instructions
18
Table 39
LTE2460 hardware and software requirements..................................80
Table 40
New counters introduced by LTE2460................................................80
Table 41
New key performance indicators introduced by LTE2460.................. 80
Table 42
New parameters introduced by LTE2460........................................... 80
Table 43
Existing parameters related to LTE2460............................................ 81
Table 44
LTE2460 sales information................................................................. 81
Table 45
LTE2479 hardware and software requirements..................................83
Table 46
New counters introduced by LTE2479................................................83
Table 47
New parameters introduced by LTE2479........................................... 85
Table 48
Existing parameters related to LTE2479............................................ 85
Table 49
LTE2479 sales information................................................................. 85
Table 50
LTE2511 hardware and software requirements.................................. 87
Table 51
LTE2511 sales information................................................................. 88
Table 52
LTE2527: Additional Carrier Aggregation Band Combinations – IV hardware and software requirements................................................. 90
Table 53
LTE2527: Additional Carrier Aggregation Band Combinations – IV sales information................................................................................ 91
Table 54
LTE2528 hardware and software requirements..................................93
Table 55
LTE2528 sales information................................................................. 94
Table 56
LTE2531 hardware and software requirements..................................98
Table 57
New counters introduced by LTE2531................................................99
Table 58
New parameters introduced by LTE2531........................................... 99
Table 59
Existing parameters related to LTE2531.......................................... 100
Table 60
LTE2531 sales information............................................................... 106
Table 61
A5 RSRP and A5 RSRQ activation conditions................................. 110
Table 62
LTE2551 hardware and software requirements................................ 111
Table 63
New parameters introduced by LTE2551..........................................111
Table 64
LTE2551 sales information............................................................... 112
Table 65
LTE2557 hardware and software requirements................................ 115
Table 66
Parameters modified by LTE2557.....................................................116
Table 67
LTE2557 sales information............................................................... 116
Table 68
QoS scheme for LTE.........................................................................119
Table 69
Standard QCI characteristics (3GPP TS 23.203)............................. 120
Table 70
Partial admission decision table....................................................... 122
Table 71
LTE2559 hardware and software requirements................................125
Table 72
New counters introduced by LTE2559..............................................125
Table 73
New parameters introduced by LTE2559......................................... 126
Table 74
Existing parameters related to LTE2559.......................................... 126
Table 75
LTE2559 sales information............................................................... 126
Table 76
LTE2564 feature hardware and software requirements................... 129
Table 77
BTS fault related to the LTE2564 feature......................................... 129
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Issue: 01 Draft
Table 78
Existing parameters related to the LTE2564 feature........................ 129
Table 79
The LTE2564 feature sales information............................................130
Table 80
Conditions for the inter-RAT measurements period......................... 133
Table 81
LTE2572 hardware and software requirements................................133
Table 82
New parameters introduced by LTE2572......................................... 134
Table 83
LTE2572 sales information............................................................... 135
Table 84
LTE2583 hardware and software requirements................................138
Table 85
New counters introduced by LTE2583..............................................138
Table 86
Parameters related to the LTE2583..................................................138
Table 87
Parameters modified by LTE2583.................................................... 138
Table 88
LTE2583 sales information............................................................... 139
Table 89
LTE2601 hardware and software requirements................................142
Table 90
New parameters introduced by LTE2601......................................... 142
Table 91
Existing parameters related to LTE2601.......................................... 144
Table 92
LTE2601 sales information............................................................... 145
Table 93
LTE2611 hardware and software requirements................................ 149
Table 94
New counters introduced by LTE2611.............................................. 149
Table 95
New parameters introduced by LTE2611..........................................150
Table 96
Existing parameters related to LTE2611...........................................152
Table 97
LTE2611 sales information............................................................... 159
Table 98
LTE2612 hardware and software requirements................................165
Table 99
New BTS faults introduced by LTE2612........................................... 165
Table 100
New counters introduced by LTE2612..............................................166
Table 101
New parameters introduced by LTE2612......................................... 166
Table 102
Existing parameters related to LTE2612.......................................... 168
Table 103
LTE2612 sales information............................................................... 169
Table 104
LTE2629 hardware and software requirements................................171
Table 105
New BTS faults introduced by LTE2629........................................... 171
Table 106
LTE2629 sales information............................................................... 172
Table 107
LTE2630 hardware and software requirements................................174
Table 108
New parameters introduced by LTE2630......................................... 174
Table 109
Existing parameters related to LTE2630.......................................... 174
Table 110
LTE2630 sales information............................................................... 175
Table 111
LTE2754 hardware and software requirements................................178
Table 112
New BTS faults introduced by LTE2754........................................... 178
Table 113
New parameters introduced by LTE2754......................................... 178
Table 114
LTE2754 sales information............................................................... 178
Table 115
LTE2832 hardware and software requirements................................184
Table 116
New counters introduced by LTE2832..............................................184
Table 117
New parameters introduced by LTE2832......................................... 185
DN09237915
19
FDD-LTE16A, Feature Descriptions and Instructions
20
Table 118
Existing parameters related to LTE2832.......................................... 185
Table 119
LTE2832 sales information............................................................... 185
Table 120
LTE3092 hardware and software requirements................................187
Table 121
New parameter introduced by LTE3092........................................... 188
Table 122
Existing parameters related to LTE3092.......................................... 188
Table 123
LTE3092 sales information............................................................... 188
Table 124
LTE3093 hardware and software requirements................................191
Table 125
New counters introduced by LTE3093..............................................191
Table 126
New parameters introduced by LTE3093......................................... 192
Table 127
LTE3093 sales information............................................................... 192
Table 128
LTE563 hardware and software requirements..................................196
Table 129
Existing alarms related to LTE563.................................................... 197
Table 130
New BTS faults related to LTE563................................................... 197
Table 131
New parameters............................................................................... 197
Table 132
LTE563 sales information................................................................. 198
Table 133
LTE1554, LTE1652, LTE1738 hardware and software requirements..... 201
Table 134
Existing BTS faults used by LTE1554, LTE1652, LTE1738..............201
Table 135
Parameters modified by LTE1554, LTE1652, LTE1738....................201
Table 136
LTE1554, LTE1652, LTE1738 sales information.............................. 202
Table 137
LTE1980 hardware and software requirements................................205
Table 138
LTE1980 sales information............................................................... 205
Table 139
LTE1981 hardware and software requirements................................207
Table 140
Existing parameters related to LTE1981.......................................... 207
Table 141
LTE1981 sales information............................................................... 208
Table 142
LTE2417 hardware and software requirements................................213
Table 143
New alarms introduced by LTE2417.................................................214
Table 144
New BTS faults introduced by LTE2417........................................... 214
Table 145
New counters introduced by LTE2417..............................................214
Table 146
New parameters introduced by LTE2417......................................... 214
Table 147
Existing parameters related to LTE2417.......................................... 214
Table 148
LTE2417 sales information............................................................... 215
Table 149
LTE2645 hardware and software requirements................................219
Table 150
New BTS faults introduced by LTE2645........................................... 220
Table 151
Existing BTS faults related to LTE2645............................................ 220
Table 152
Parameters modified by LTE2645.................................................... 220
Table 153
LTE2645 sales information............................................................... 221
Table 154
LTE2763 Fronthaul Passive WDM................................................... 226
Table 155
LTE2763 sales information............................................................... 226
Table 156
LTE678 hardware and software requirements..................................229
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Issue: 01 Draft
Table 157
New parameters introduced by LTE678........................................... 229
Table 158
Existing parameters related to LTE678............................................ 229
Table 159
LTE678 sales information................................................................. 230
Table 160
LTE2121 hardware and software requirements................................232
Table 161
New parameters introduced by LTE2121......................................... 232
Table 162
LTE2121 sales information............................................................... 233
Table 163
Measurements newly added to the cell trace content...................... 233
Table 164
LTE2202 hardware and software requirements................................235
Table 165
New parameters introduced by LTE2202......................................... 236
Table 166
Existing parameters related to LTE2202.......................................... 236
Table 167
LTE2202 sales information............................................................... 236
Table 168
LTE2237 hardware and software requirements................................239
Table 169
New parameters introduced by LTE2237......................................... 239
Table 170
LTE2237 sales information............................................................... 239
Table 171
Supported local language characters............................................... 240
Table 172
LTE2331 hardware and software requirements................................241
Table 173
Parameters modified by LTE2331.................................................... 242
Table 174
LTE2331 sales information............................................................... 242
Table 175
LTE2360 hardware and software requirements................................245
Table 176
New parameters introduced by LTE2360......................................... 245
Table 177
LTE2360 sales information............................................................... 245
Table 178
LTE2361 hardware and software requirements................................247
Table 179
New parameters introduced by LTE2361......................................... 247
Table 180
LTE2361 sales information............................................................... 247
Table 181
Wiring MHAs.....................................................................................249
Table 182
LTE2403 hardware and software requirements................................250
Table 183
New parameters introduced by LTE2403......................................... 250
Table 184
Parameters modified by LTE2403.................................................... 251
Table 185
LTE2403 sales information............................................................... 251
Table 186
LTE2507 hardware and software requirements................................255
Table 187
LTE2507 sales information............................................................... 256
Table 188
LTE2508 hardware and software requirements................................259
Table 189
Static values used to create energy consumption counters for FSMr3 modules............................................................................................ 260
Table 190
New counters introduced by LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring....................................................... 260
Table 191
New parameters introduced by LTE2508......................................... 260
Table 192
LTE2508 sales information............................................................... 261
Table 193
LTE2562 hardware and software requirements................................264
Table 194
New counters introduced by LTE2562..............................................264
Table 195
New parameters introduced by LTE2562......................................... 264
DN09237915
21
FDD-LTE16A, Feature Descriptions and Instructions
22
Table 196
Parameters modified by LTE2562.................................................... 265
Table 197
LTE2562: ANR InterRat 1xRTT - O&M Assisted sales information.. 266
Table 198
LTE2591 hardware and software requirements................................268
Table 199
New counters introduced by LTE2591..............................................268
Table 200
Existing counters related to LTE2591............................................... 268
Table 201
New key performance indicators introduced by LTE2591................ 268
Table 202
New parameters introduced by LTE2591......................................... 269
Table 203
LTE2591 sales information............................................................... 269
Table 204
LTE2621 hardware and software requirements................................271
Table 205
BTS faults related to LTE2621..........................................................271
Table 206
New counters introduced by LTE2621..............................................271
Table 207
New parameters introduced by LTE2621......................................... 271
Table 208
LTE2621 sales information............................................................... 272
Table 209
LTE2633 hardware and software requirements................................275
Table 210
Existing alarms related to LTE2633.................................................. 276
Table 211
LTE2633 sales information............................................................... 276
Table 212
LTE2816 hardware and software requirements................................278
Table 213
New BTS faults introduced by LTE2816........................................... 278
Table 214
New parameters introduced by LTE2816......................................... 279
Table 215
LTE2816 sales information............................................................... 279
Table 216
LNBTS and LNCEL refactoring changes..........................................280
Table 217
LTE2828 hardware and software requirements................................285
Table 218
Existing mandatory parameters from SIB area related to LTE2828. 286
Table 219
Existing mandatory parameters from DRX area related to LTE2828..... 288
Table 220
Existing mandatory structures from DRX area related to LTE2828.. 288
Table 221
Existing structures from SDRX area related to LTE2828................. 289
Table 222
Existing mandatory parameters from RIM area related to LTE2828...... 290
Table 223
Existing mandatory parameters from ANR area related to LTE2828..... 291
Table 224
Existing mandatory structures from ANR area related to LTE2828.. 292
Table 225
LTE2828 sales information............................................................... 292
Table 226
LTE3043 hardware and software requirements................................296
Table 227
Existing alarms related to LTE3043.................................................. 296
Table 228
New BTS faults introduced by LTE3043........................................... 297
Table 229
LTE3043 sales information............................................................... 297
Table 230
LTE3051 hardware and software requirements................................304
Table 231
LTE3051 sales information............................................................... 304
Table 232
LTE2140 hardware and software requirements................................308
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Issue: 01 Draft
Table 233
New counters introduced by the LTE2140: New Performance Counters LTE 16A feature................................................................ 308
Table 234
Existing counters realted to the LTE2140: New Performance Counters LTE 16A feature................................................................................313
Table 235
LTE2140 sales information............................................................... 315
Table 236
LTE2493 hardware and software requirements................................316
Table 237
New counters introduced by LTE2493..............................................317
Table 238
New parameters introduced by LTE2493......................................... 318
Table 239
LTE2493 sales information............................................................... 319
Table 240
LTE2766 hardware and software requirements................................321
Table 241
New counters introduced by LTE2766..............................................321
Table 242
New counters related to LTE2766.................................................... 322
Table 243
New parameters introduced by LTE2766......................................... 324
Table 244
LTE2766 sales information............................................................... 325
Table 245
LTE2804 hardware and software requirements................................326
Table 246
New counters introduced by LTE2804..............................................327
Table 247
New parameters introduced by LTE2804......................................... 328
Table 248
LTE2804 sales information............................................................... 329
Table 249
LTE2915 hardware and software requirements................................331
Table 250
New counters related to LTE2915.................................................... 332
Table 251
New parameters introduced by LTE2915......................................... 334
Table 252
New parameters related to LTE2915................................................ 334
Table 253
LTE2915 sales information............................................................... 334
Table 254
LTE2576 hardware and software requirements................................336
Table 255
LTE2576 sales information............................................................... 337
Table 256
LTE2373 hardware and software requirements................................338
Table 257
Existing BTS faults related to LTE2373............................................ 338
Table 258
LTE2373 sales information............................................................... 338
Table 259
FDD RTWP threshold values .......................................................... 339
Table 260
LTE2805 hardware and software requirements................................340
Table 261
New BTS faults introduced by LTE2805........................................... 340
Table 262
New parameters introduced by LTE2805......................................... 341
Table 263
LTE2805 sales information............................................................... 341
Table 264
LTE2883 hardware and software requirements................................342
Table 265
LTE2883 sales information............................................................... 342
Table 266
LTE180 impact on system performance........................................... 344
Table 267
LTE180 hardware and software requirements..................................345
Table 268
Parameters modified by LTE180...................................................... 345
Table 269
Existing parameters related to LTE180............................................ 345
Table 270
LTE180 sales information................................................................. 346
Table 271
LTE2114 hardware and software requirements................................ 349
DN09237915
23
FDD-LTE16A, Feature Descriptions and Instructions
24
Table 272
New BTS faults introduced by LTE2114........................................... 349
Table 273
New parameters introduced by LTE2114..........................................350
Table 274
Parameters modified by LTE2114.....................................................350
Table 275
LTE2114 sales information............................................................... 350
Table 276
LTE2252: FSM OD-Cabinet FCOB hardware and software requirements.....................................................................................352
Table 277
LTE2252: FSM OD-Cabinet FCOB sales information...................... 352
Table 278
LTE2261 hardware and software requirements................................355
Table 279
LTE2261 sales information............................................................... 355
Table 280
AMIA dimensions and weight........................................................... 357
Table 281
LTE2262 hardware and software requirements................................359
Table 282
LTE2262 sales information............................................................... 359
Table 283
LTE2335 LTE FDD hardware and software requirements................ 361
Table 284
Alarms modified by LTE2335............................................................362
Table 285
New BTS faults introduced by LTE2335........................................... 362
Table 286
Existing faults related to LTE2335Parameters ................................ 362
Table 287
Existing counters related to LTE2335............................................... 362
Table 288
Modified parameters introduced by LTE2335................................... 363
Table 289
LTE2335 sales information............................................................... 363
Table 290
LTE2387 hardware and software requirements................................366
Table 291
LTE2387 sales information............................................................... 367
Table 292
FRIJ dimensions and weight............................................................ 368
Table 293
LTE2516 hardware and software requirements................................370
Table 294
LTE2516 sales information............................................................... 371
Table 295
LTE2517 hardware and software requirements................................372
Table 296
New BTS faults introduced by LTE2517........................................... 372
Table 297
New parameters introduced by LTE2517......................................... 372
Table 298
LTE2517 sales information............................................................... 372
Table 299
LTE2605 hardware and software requirements................................374
Table 300
LTE2605 sales information............................................................... 375
Table 301
LTE2609: Dual Carrier Support LTE1.4 and LTE3 hardware and software requirements...................................................................... 376
Table 302
LTE2609 sales information............................................................... 376
Table 303
Configurations introduced by the feature..........................................377
Table 304
LTE2610 hardware and software requirements................................378
Table 305
LTE2610 sales information............................................................... 378
Table 306
LTE2637 hardware and software requirements................................380
Table 307
LTE2637 sales information............................................................... 380
Table 308
LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W hardware and software requirements...................................................................... 382
Table 309
LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W sales information...382
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Issue: 01 Draft
Table 310
LTE2679: FRCJ Flexi RRH 2T4R 873 120 W hardware and software requirements.....................................................................................385
Table 311
LTE2679: FRCJ Flexi RRH 2T4R 873 120 W sales information...... 385
Table 312
FHEL dimensions and weight...........................................................386
Table 313
LTE2680 hardware and software requirements................................388
Table 314
LTE2680 sales information............................................................... 388
Table 315
LTE2722 hardware and software requirements................................390
Table 316
LTE2722 sales information............................................................... 390
Table 317
LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W hardware and software requirements.....................................................................................393
Table 318
LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W sales information... 393
Table 319
Configurations introduced by the feature..........................................394
Table 320
LTE2880 hardware and software requirements................................395
Table 321
LTE2880 sales information............................................................... 395
Table 322
LTE2911 hardware and software requirements................................ 398
Table 323
LTE2911 sales information............................................................... 398
Table 324
LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) hardware and software requirements............................................... 399
Table 325
LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) sales information........................................................................................400
Table 326
LTE2920 hardware and software requirements................................402
Table 327
LTE2920 sales information............................................................... 402
Table 328
LTE2950 hardware and software requirements................................404
Table 329
LTE2950 sales information............................................................... 405
Table 330
LTE3027: FRPD Flexi RFM 6-pipe 700 240 W hardware and software requirements.....................................................................................406
Table 331
LTE3027: FRPD Flexi RFM 6-pipe 700 240 W sales information.... 407
Table 332
LTE3177 hardware and software requirements................................409
Table 333
LTE3177 sales information............................................................... 409
DN09237915
25
Summary of changes
FDD-LTE16A, Feature Descriptions and Instructions
Summary of changes This is the first issue of FDD-LTE16A (2016-04-24, FDD-LTE16A)
26
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
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: 01 Draft
DN09237915
27
Activating and deactivating LTE features using BTS Site Manager
FDD-LTE16A, Feature Descriptions and Instructions
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.
28
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
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: 01 Draft
Note: For information on possible restarts, see section Before you start of every feature -specific procedure.
DN09237915
29
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
3 Descriptions of radio resource management and telecom features 3.1 LTE1092: Uplink Carrier Aggregation – 2CC The LTE1092: Uplink Carrier Aggregation – 2CC feature introduces inter-band and intraband uplink (UL) carrier aggregation (CA) with a combined bandwidth of up to 40 MHz. It also introduces dynamic uplink traffic steering across component carriers (CCs). The feature supports combination of UL-CA-capable and UL-CA-non-capable UEs.
3.1.1 LTE1092 benefits The LTE1092: Uplink Carrier Aggregation – 2CC feature provides the following benefits: • • •
up to twice as high peak uplink throughput per UE in areas with overlapping cell deployments and within supported band combinations balancing the UL load across two UL component carriers (2CC UL), thus maximizing the utilization of each carrier enabling 2CC UL CA is supported in combination with up to three carrier component downlink carrier aggregation (3CC DL CA)
3.1.2 LTE1092 functional description Functional overview Carrier aggregation consists of a primary cell (PCell) and one or more secondary cells (SCells). With the LTE1092: Uplink Carrier Aggregation – 2CC feature, uplink carrier aggregation (UL CA) only works in combination with downlink carrier aggregation (DL CA). Both DL and UL CA share the same PCell. The SCells can be DL-only SCells, or DL+UL SCells. There is no such thing as a UL-only SCell; UL CA can be enabled only if DL CA is enabled. The physical uplink control channel (PUCCH) is transmitted on the PCell only. Figure 1
Example of co-located cells with a specified PCell, DL+UL SCell, and DLonly SCell eNB
L L +U +U DL DL only CA DL CA
UE
Carrier1(PCell) Carrier2(DL+ULSCell) Carrier3(DLScell)
30
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
With the LTE1092: Uplink Carrier Aggregation – 2CC feature, the Flexi Multiradio BTS supports UL CA for two component carriers with a combined bandwidth of up to 40 MHz. The receivers (RX points) of the cells must be co-located. To support an additional UL CC, the following functions are supported by the 3GPP specification: •
•
•
Extended Buffer Status Report (BSR). For UL-CA-capable UEs to be able to support increased UL throughput, increased sizes of buffer for pending data are supported in the extended BSR at the expense of lesser granularity of buffer size values. Extended Power Headroom Report (PHR). The eNB requires power headroom reports for both the PCell and the SCell. The extended PHR provides a power headroom report for each CC. Maximum Power Reduction (MPR) and Additional MPR (A-MPR). There are additional MPR/A-MPR requirements when the eNB is configured with an intra-band CA carrier. MPR is specified in 3GPP 36.101, section 6.2.3A. A-MPR is enabled by the operator with the Additional MPR for UL intra-band carrier aggregation (caUlIntraBandAmpr) LNBTS parameter.
The following is a list of supported 2CC DL + 2CC UL band combinations (bandwidth combination set is 0, if not mentioned otherwise): • • • • • • • • • • • • • • • • • • • • • • • • • • • •
Issue: 01 Draft
band 1 + band 3 band 1 + band 5 (bandwidth combination set 0 and 1) band 1 + band 7 band 1 + band 8 (bandwidth combination set 0 and 1) band 1 + band 18 (bandwidth combination set 0 and 1) band 1 + band 28 (bandwidth combination set 0 and 1) band 2 + band 2 (contiguous) band 2 + band 4 (bandwidth combination set 0, 1 and 2) band 2 + band 12 band 2 + band 13 (bandwidth combination set 0 and 1) band 3 + band 3 (contiguous) band 3 + band 5 (bandwidth combination set 0, 1 and 2) band 3 + band 7 band 3 + band 8 (bandwidth combination set 0 and 1) band 3 + band 20 (bandwidth combination set 0 and 1) band 4 + band 4 (non-contiguous) band 4 + band 5 band 4 + band 7 band 4 + band 12 (bandwidth combination set 0, 1, 2, 3 and 4) band 4 + band 13 (bandwidth combination set 0 and 1) band 4 + band 17 band 5 + band 7 band 5 + band 12 band 5 + band 17 band 7 + band 7 (contiguous) band 7 + band 20 (bandwidth combination set 0 and 1) band 7 + band 28 band 18 + band 28
DN09237915
31
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
LTE1092: Uplink Carrier Aggregation – 2CC supports the following 3CC DL + 2CC UL band combinations: • • • • • • • • • •
g
DL (1+3+5) + UL (1+3, 1+5, 3+5) DL (1+3+8) + UL (1+3, 1+8, 3+8) DL (1+5+7) + UL (1+5, 1+7, 5+7) DL (1+18+28) + UL (1+18, 1+28, 18+28) DL (2+4+12) + UL (2+4, 4+12) DL (2+5+13) + UL (2+13) DL (3+3+7) + UL (3+3, 3+7) – band 3 contiguous DL (3+7+7) + UL (3+7, 7+7) – band 7 contiguous DL (3+7+20) + UL (3+7, 3+20, 7+20) DL (4+5+13) + UL (4+13) Note: LTE1092: Uplink Carrier Aggregation – 2CC supports only deployment scenarios 1, 2, and 3; bandwidth combination sets and deployment scenarios are described in 3GPP TS 36.300.
LTE1092: Uplink Carrier Aggregation – 2CC supports the following cell bandwidth combinations: • • • • • • • • • •
5 MHz + 5 MHz 5 MHz + 10 MHz 5 MHz + 15 MHz 5 MHz + 20 MHz 10 MHz + 10 MHz 10 MHz + 15 MHz 10 MHz + 20 MHz 15 MHz + 15 MHz 15 MHz + 20 MHz 20 MHz + 20 MHz
A mix of non-carrier aggregation UEs and carrier aggregation DL or DL+UL UEs is supported. UE capabilities are considered when applying uplink carrier aggregation. LTE1092: Uplink Carrier Aggregation – 2CC can coexist with up to 4CC DL CA; however, to enable DL+UL CA, the existing SCells need to be reconfigured either to 3CC DL + 2CC UL or 2CC DL + 2CC UL. Configured carrier aggreation relations (CARELs) for DL CA also apply to UL CA. PCell/SCell pairs must be co-located to be eligible for UL CA as LTE1092: Uplink Carrier Aggregation – 2CC supports only a single UL timing alignment group.
g g
Note: Since there is no software enforcement of this restriction, it is up to the operator to ensure the configuration is correct. Note: LTE1092: Uplink Carrier Aggregation – 2CC does not support the physical random access channel (PRACH) on an SCell, cross-CC scheduling, and it is not supported with FZ Micro TD-LTE. Functional extensions Radio admission control
32
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
UEs are admitted based on the PCell admission control settings. The same thresholds as for carrier-aggregation-non-capable UEs are applied. Mobility The following mobility scenarios are supported: • • •
handover of UEs with activated UL CA to cells with enabled UL CA handover of UEs with activated UL CA to cells without enabled UL CA handover from a cell without enabled UL CA to cells with enabled UL CA
In case a handover fails, the UE might initiate an RRC:RRCConnectionReestablishment procedure. The mobility for CA-configured UEs is based on PCell measurements. The same measurement configurations as for CA-non-configured UEs are applied; for example, A3 and/or A5 measurements. The SCell is deconfigured during a handover, and, after the handover is completed, a new SCell might be set up on the target cell. SCell handling The SCell selection is downlink centric, which means that the downlink load of the SCells and the DL CA capabilities are considered. However, in case there are multiple SCells avilable, uplink comparison value (ULCV) will be taken in account in the selection. An addition of a further SCell may even lead to a deconfiguration of a previously configured DL+UL SCell and, consequently, to the adding of the DL-only SCell. LTE1092: Uplink Carrier Aggregation – 2CC provides the operator with the Preference for SCell addition (dlCaPreferred) LNBTS parameter. Setting this parameter to DLonly will cause the eNB to reconfigure the UE with either 3CC or 4CC DL CA only (from 2CC DL + 2CC UL CA and 3CC DL + 2CC UL respectively) if the DL Scell is needed by the UE. Setting this parameter to DLandUL will cause the eNB to keep the UE in 2CC DL + 2CC UL CA or 3CC DL + 2CC UL mode. The SCell is activated when either UL or DL CA is required, and it will be deactivated only if both UL and DL CA are no longer needed. The UL CA will be activated when UE requires UL CA based on the buffer status reports (BSRs) and the uplink radio condition of the PCell. The scheduling of UL on the SCell is stopped in case of a bad uplink radio condition on the SCell. The UL CA is eligible to be configured if the UE's aggregated maximum bit rate (AMBR) uplink is above an operator-configurable threshold (with the parameter Min UE-AMBR uplink for carrier aggregation (caMinUlAmbr)), and the eNB is configured accordingly. The DL+UL SCell is configured with an RRC:RRCConnectionReconfiguration message. Scheduling UEs with an activated SCell are scheduled by separate and coordinated uplink schedulers (based on the configured Pathloss threshold UE scheduled on single cell (ulCaPathlossThr) LNBTS parameter). The uplink fairness between CA-capable UEs and CA-non-capable UEs is pre-configured (using the parameter Scheduling CA fairness control factor (caSchedFairFact)).
Issue: 01 Draft
DN09237915
33
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
UE's AMBR and the nominal bit rate (NBR), if enabled, are enforced in the PCell only. The same timing advance group (TAG) is used in uplink component carriers. UEs that support UL CA will be configured to supply an extended BSR report when configured with UL CA. The UE TX power split between two CCs is done dynamically, considering a potential back-off for intra-band cases and the power headroom report (PHR) of both component carriers.
3.1.3 LTE1092 system impact Interdependencies between features The following features must be activated before activating the LTE1092: Uplink Carrier Aggregation – 2CC feature: • •
• •
•
LTE1089: Downlink Carrier Aggregation – 20 MHz LTE1332: Downlink Carrier Aggregation – 40 MHz 2CC DL CA features must be enabled for LTE1092 for band combinations 2CC DL + 2CC UL CA. LTE1803: Downlink Carrier Aggregation 3 CC – 40 MHz LTE1804: Downlink Carrier Aggregation 3 CC – 60 MHz 3CC DL CA features must be enabled for LTE1092 for band combinations 3CC DL + 2CC UL CA. LTE2006: Flexible SCell Selection Required for 3GPP Scenario 3 support.
For the inter-eNB UL CA, the following features must be activated before activating the LTE1092: Uplink Carrier Aggregation – 2CC feature: • •
LTE2007: Inter-eNodeB Carrier Aggregation LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs LTE1092 supports both intra-eNB UL CA and inter-eNB UL CA when inter-eNB DL CA is enabled.
The LTE1092: Uplink Carrier Aggregation – 2CC feature impacts the following features: • •
LTE2275: PCell Swap UEs with a configured DL+UL SCell will not be eligible for a PCell swap. LTE1059: Uplink Multi-cluster Scheduling LTE1092 will exclude UEs with an activated DL+UL SCell from being eligible for multi-cluster scheduling.
The LTE1092: Uplink Carrier Aggregation – 2CC feature is impacted by the following features: •
• • •
34
LTE907: TTI Bundling UEs in TTI bundling cannot perform UL CA; UEs configured for TTI are deconfigured from CA. LTE117: Cell Bandwidth – 1.4 MHz LTE116: Cell Bandwidth – 3 MHz LTE1092 cannot be activated with these bandwidths. LTE1541: Advanced SCell Measurement Handling Changing the SCell can change the SCell for UL CA.
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• • •
•
•
Descriptions of radio resource management and telecom features
LTE2233: N-out-of-M Downlink Carrier Aggregation The SCell used for UL CA can be dynamically changed. LTE1402: Uplink Intra-eNB CoMP The nominal bit rate for a UL CA is be supported on the PCell. LTE2531: FDD Downlink Carrier Aggregation 4CC LTE1092 and LTE2531 can be enabled on the same eNB; however, that eNB will not support 2CC UL CA on the same UE when 4CC CA is active. LTE2557: Supplemental Downlink Carrier Extensions Supplemental cells that are barred will be eligible neither for a connection nor for UL CA. LTE73: UL MU MIMO 4RX The eNB will not prevent LTE1092 and LTE73 from being simultaneously enabled, but it is not reccommended in the field as this point.
Impact on interfaces The LTE1092: Uplink Carrier Aggregation – 2CC feature has no impact on interfaces. Impact on network management tools The LTE1092: Uplink Carrier Aggregation – 2CC feature has no impact on network management tools. Impact on system performance and capacity The LTE1092: Uplink Carrier Aggregation – 2CC feature impacts system performance and capacity with up to twice as high UE's peak uplink throughput and increased load across two UL component carriers.
3.1.4 LTE1092 reference data Requirements Table 1
LTE1092 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Flexi Multiradio 10 BTS
AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
Not supported
Not supported
Not supported
NetAct
MME
SAE GW
UE
Not supported LTE OMS16A
3GPP R10R12 UE capabilities
NetAct 16.8
Support not required
Support not required
Alarms There are no alarms related to the LTE1092: Uplink Carrier Aggregation – 2CC feature. BTS faults and reported alarms There are no faults related to the LTE1092: Uplink Carrier Aggregation – 2CC feature. Commands There are no commands related to the LTE1092: Uplink Carrier Aggregation – 2CC feature. Measurements and counters
Issue: 01 Draft
DN09237915
35
Descriptions of radio resource management and telecom features
Table 2
FDD-LTE16A, Feature Descriptions and Instructions
Existing counters related to LTE1092
Counter ID
Counter name
Measurement
M8001C 284
Average number of UL CA UE with one activated Scell
LTE Cell Load
M8011C 171
Number of SCell configuration attempts with UL CA
LTE Cell Resource
M8011C 172
Number of successful SCell configurations with UL CA
LTE Cell Resource
M8012C 174
PCell RLC data volume in UL via Scell
LTE Cell Throughput
M8051C 53
Average number of CA UE with one configured UL Scell
LTE UE Quantity
M8051C 54
Average Number of UL carrier aggregated LTE UE Quantity capable UEs for 2CCs
For counter descriptions, see LTE Performance Measurements. Key performance indicators There are no key performance indicators related to the LTE1092: Uplink Carrier Aggregation – 2CC feature. Parameters Table 3
Existing parameters related to LTE1092 Full name
Abbreviated name
Managed object
Parent structure
Activation of Uplink Carrier Aggregation
actULCAggr
LNBTS
-
Pathloss threshold UE scheduled on single cell
ulCaPathlossThr
LNBTS
-
Min UE-AMBR uplink for carrier aggregation
caMinUlAmbr
LNBTS
-
Activate inter-eNB UL carrier aggregation
actInterEnbULCAggr LNBTS
-
Additional MPR for UL intra-band carrier aggregation
caUlIntraBandAmpr
LNBTS
-
Preference for SCell addition
dlCaPreferred
LNBTS
-
For parameter descriptions, see Flexi Multiradio BTS LTE Commissioning, RNW and Transmission Parameters. Sales information Table 4
LTE1092 sales information
Product structure class Application software (ASW)
36
License control SW Asset Monitoring
DN09237915
Activated by default No
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
3.2 LTE1130: Dynamic PUCCH Allocation The LTE1130: Dynamic PUCCH Allocation feature introduces support for a dynamic allocation of the physical uplink control channel (PUCCH) resources. This is done by adjusting the channel state indicator (CSI) and uplink scheduling request (SR) periodicity for the UEs, based on system load. Dynamic adaptation of CSI and SR periodicity with respect to cell load, allows to serve more UEs compared to the number of UEs assigned with static periodicities.
3.2.1 LTE1130 benefits The LTE1130: Dynamic PUCCH Allocation feature provides the following benefits: • • •
The operator can configure the physical uplink control channel (PUCCH) with simplified O&M settings. In higher load conditions, the freature enables economizing the PUCCH resource allocation, thus increasing the number of users in a cell. In low load conditions all UEs have a short CSI or SRI periodicity. Thanks to that performance is improved. When the load increases, all UEs get a slower pace periodicity, and the eNB tries to allocate CSI or SR in an optimal way. Depending on which features are active in the cell (for example carrier aggregation-related features), it is possible that CSI resources distribution is based on the UE capability (UE configured or not configured for CA support), and not on the cell load. However, SR resources are always allocated according to the cell load method.
3.2.2 LTE1130 functional description The LTE1130: Dynamic PUCCH Allocation feature introduces dynamic switching between channel state indicator (CSI) and scheduling request (SR) periodicity. Switching between periodicities depends on cell load which is related with number of RRC Connected UEs in the cell. The adaptation of the CSI or SR periodicity is done only for UEs for which reconfiguration needs to be applied. To avoid generating extra signaling, new CSI or SR periodicity is given to every UE experiencing one of the following events: • • •
RRC Idle to RRC Connected state transition UE entering the cell via handover secondary cell (SCell) configuration or reconfiguration
The functionality can be enabled or disabled per cell with the O&M setting, which requires cell locking. The following CSI and SR periodicity values are used by LTE1130: Table 5
Issue: 01 Draft
CSI and SR periodicity values
CSI Period
SR Period
40 ms
10 ms
80 ms
20 ms
DN09237915
37
Descriptions of radio resource management and telecom features
Table 5
FDD-LTE16A, Feature Descriptions and Instructions
CSI and SR periodicity values (Cont.) 40 ms
Parameters configuration The system is able to automatically calculate the PRB resources required for PUCCH. For this purpose, it takes the following operator settings into account: •
parameter configuration – –
–
–
–
–
–
–
– –
– –
38
actAutoPucchAlloc – This is an activation flag for the LTE1130 feature. maxNumActUE – This is a threshold for the maximum number of active UEs in the cell. Active UEs are UEs with at least one data radio bearer (DRB). This parameter needs to be configured based on the differences in bandwidth and a BTS type. aPucchMinNumEmergencySessions – This parameter determines the resources reserved for emergency calls. The maximum margin depends on the bandwidth of a cell. aPucchAddAUeTcHo – This is an additional margin for the maximum number of active UEs in the cell, accessing the cell via handover with HO-cause: "Time Critical HO". This margin is added to the maxNumActUE threshold. The maximum margin depends on the bandwidth of a cell. aPucchAddAUeRrHo – This is an additional margin for the maximum number of active UEs in the cell, accessing the cell via handover with HO-cause: "HO desirable for radio reasons". This margin is added to the maxNumActUE threshold. The maximum margin depends on the bandwidth of a cell. aPucchMinNumRrc – This parameter specifies the minimum number of RRCconnected UEs to be supported per cell; if the operator wants to have a dynamic PUCCH configuration with at least four PRBs, instead of only two, this can be managed with this parameter. aPucchMinNumRrcNoDrb – This parameter configures a reserve for UEs that shall be able to do bearerless actions such as tracking area updates when the maxNumActUe threshold is configured near to the HW limit of a cell (which also depends on bandwidth). Additionally this is margin for UE entering the cell with the RRC connection request cause: MO signaling. blankedPucch – This parameter defines the pointer to PRB from where the channel state indicator (CSI) allocation starts to leave some PRBs free and therefore avoid interference with neighbor bands. When set to 0, the Flexible UL Bandwidth feature is deactivated. This parameter is dependent on the configuration of the LTE786: Flexible UL Bandwidth Allocation feature. aPucchSrPeriodUpperLimit – This parameter defines the upper limit of the scheduling request periodicity to be used in the cell by the PUCCH algorithm. selectPrachRegion – This parameter defines the selected PRACH region automatically assigned by the PUCCH algorithm when the LTE1130: Dynamic PUCCH Allocation feature is activated. aPucchId – This parameter is the naming atrribute of APUCCH managed object class and does not require manual configuration. mPucchId – This parameter is the naming atrribute of MPUCCH managed object class and does not require manual configuration.
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
Descriptions of radio resource management and telecom features
Already implemented features. The following feature activation and configuration are taken into account: –
–
– – –
Carrier-aggregation-related features, which are activated with the actDLCAggr parameter. Additionally, the maxNumScells parameter needs to be configured; value 1 supports 2CC-capable UEs, and value 3 supports 2CC- and 3CCcapable UEs. MIMO-related features. The dlMimoMode parameter configuration is mandatory. The number of required CSI resources to each UE when the rank indication (RI) reporting is required depends on this parameter value. Enhanced inter-cell interference coordination (eICIC) features. The actEicic parameter activates eICIC-related features. Discontinuous-reception (DRX)-related features, which are activated with the actDrx or actSmartDrx parameter. LTE825: Uplink Outer Region Scheduling, which is activated with the selectOuterPuschRegion parameter.
The system derives PUCCH configuration parameters automatically and fills the following read-only attributes in the APUCCH managed object class in BTS Site Manager: • • • • • • • • •
assignedN1PucchAn assignedDeltaPucchShift assignedPhichDur assignedPhichRes assignedPrachFreqOff assignedNPucchF3Prbs assignedNCqiRb assignedRiConfigIndex assignedR10CsiConfIndex2Ri
With the LTE1130 feature, the following parameters which were used for manual configuration of PUCCH are now located under the MPUCCH managed object class in BTS Site Manager: • • • • • • • • •
n1PucchAn deltaPuchShift nCqiRb nPucchF3Prbs riEnable riPerM riPerOffset cqiPerNp cellSrPeriod
Performance monitoring The purpose of the counters introduced with the LTE1130 feature is to indicate how many PUCCH resources are used within the same transmission time interval (TTI). Meaning of the reported faults
Issue: 01 Draft
DN09237915
39
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
During feature configuration the following faults can be reported: •
•
6294 – Not enough PUSCH resources for PRACH This fault is reported when the operator configures parameters in such a way that the PRACH channel is not configurable. 6295 – PUCCH configuration inconsistency This fault is reported when the number of UEs requested by the operator is not achievable (this is because the maximum PUCCH size defined by the automatic PUCCH configuration has been reached). In this case the configuration with the highest available number of UEs is selected instead. The BTS informs the operator through the fault report that the requested number of UEs is not achievable, and then operates normally.
3.2.3 LTE1130 system impact Interdependencies between features The following features must be deactivated before activating the LTE1130: Dynamic PUCCH Allocation feature: • • •
LTE116: LTE 3 MHz Bandwidth LTE117: LTE 1.4 MHz Bandwidth LTE1808: Automatic PUCCH Capacity Optimization
The LTE1130: Dynamic PUCCH Allocation feature is impacted by the following features: • • • • • •
Carrier-aggregation-related features MIMO-related features Enhanced-inter-cell-interference-coordination (eICIC)-related features Discontinuous-reception (DRX)-related features LTE825: Uplink Outer Region Scheduling LTE786: Flexible UL Bandwidth
All these features are taken into account for the correct calculation of the PRB resources required for PUCCH allocation. Impact on interfaces The LTE1130: Dynamic PUCCH Allocation feature has no impact on interfaces. Impact on network management tools The LTE1130: Dynamic PUCCH Allocation feature has no impact on network management tools. Impact on system performance and capacity The LTE1130: Dynamic PUCCH Allocation feature impacts system performance as follows: •
40
The dynamic PUCCH allocation feature adjusts the CQI and SR periodicity, for UEs changing the RRC configuration, based on the PUCCH load. In low-loaded cells, the throughput might be slightly increased due to more frequent CQI reports. However, the resulting PUCCH efficiency does not significantly impact throughput performance. Therefore, the feature does not warrant performance requirements for throughput.
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
The LTE1130: Dynamic PUCCH Allocation feature has no impact on system capacity.
3.2.4 LTE1130 reference data Requirements Table 6
LTE1130: Dynamic PUCCH Allocation hardware and software requirements
System release FDD-LTE 16A Flexi Zone Controller FL16A
Flexi Multiradio BTS not supported
Flexi Multiradio 10 BTS FL16A
OMS
UE
LTE OMS16A
3GPP R8 mandatory
Flexi Zone Micro BTS FL16A
NetAct NetAct 16.8
Flexi Zone Access Point FL16A
MME
SAE GW
support not required
support not required
BTS faults and reported alarms Table 7
New BTS faults introduced by LTE1130
Fault ID
Fault name
Reported alarms Alarm ID
Alarm name
6294
Not enough PUSCH resources for PRACH
7653
CELL FAULTY
6295
PUCCH configuration inconsistency
7655
CELL NOTIFICATION
For fault descriptions, see FDD-LTE BTS Alarms and Faults. Commands There are no commands related to the LTE1130: Dynamic PUCCH Allocation feature. Measurements and counters Table 8
New counters introduced by LTE1130
Counter ID
Counter name
Measurement
M8011C18 9
Allocation of 40 ms CQI reporting periodicity on PUCCH
LTE Cell Resource
M8011C19 0
Allocation of 80 ms CQI reporting periodicity on PUCCH
LTE Cell Resource
M8011C19 1
Allocation of 10 ms SR reporting periodicity on PUCCH
LTE Cell Resource
M8011C19 2
Allocation of 20 ms SR reporting periodicity on PUCCH
LTE Cell Resource
M8011C19 3
Allocation of 40 ms SR reporting periodicity on PUCCH
LTE Cell Resource
For counter descriptions, see LTE Performance Measurements and Key Performance Indicators. Key performance indicators
Issue: 01 Draft
DN09237915
41
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
There are no key performance indicators related to the LTE1130: Dynamic PUCCH Allocation feature. Parameters Table 9
New parameters introduced by LTE1130 Full name
42
Abbreviated name
Managed object
Parent structure
Activation of automatic PUCCH allocation
actAutoPucchAlloc
MRBTS/LNBTS/LNCEL
Automatic PUCCH allocation, add number UEs RR HO
aPucchAddAUeRrHo
MRBTS/LNBTS/LNCEL/A PUCCH
Automatic PUCCH allocation, add number UEs TC HO
aPucchAddAUeTcHo
MRBTS/LNBTS/LNCEL/A PUCCH
Automatic PUCCH allocation, min num. emergency sessions
aPucchMinNumEmergenc ySessions
MRBTS/LNBTS/LNCEL/A PUCCH
Automatic PUCCH allocation, min number RRC
aPucchMinNumRrc
MRBTS/LNBTS/LNCEL/A PUCCH
Automatic PUCCH allocation, min number RRC TAU
aPucchMinNumRrcNoDrb
MRBTS/LNBTS/LNCEL/A PUCCH
Automatic PUCCH allocation, upper SR periodicity
aPucchSrPeriodUpperL imit
MRBTS/LNBTS/LNCEL/A PUCCH
Delta cyclic shift assignedDeltaPucchSh used in PUCCH ift allocation
MRBTS/LNBTS/LNCEL/A PUCCH
ACK/NACK offset used in PUCCH allocation
assignedN1PucchAn
MRBTS/LNBTS/LNCEL/A PUCCH
PUCCH bandwidth for CQI used in PUCCH allocation
assignedNCqiRb
MRBTS/LNBTS/LNCEL/A PUCCH
PRBs for HARQ Format 3 used in PUCCH allocation
assignedNPucchF3Prbs
MRBTS/LNBTS/LNCEL/A PUCCH
PHICH duration used in PUCCH allocation
assignedPhichDur
MRBTS/LNBTS/LNCEL/A PUCCH
PHICH resource used in PUCCH allocation
assignedPhichRes
MRBTS/LNBTS/LNCEL/A PUCCH
PRACH frequency offset used in PUCCH allocation
assignedPrachFreqOff
MRBTS/LNBTS/LNCEL/A PUCCH
DN09237915
-
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 9
New parameters introduced by LTE1130 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
RI configuration index used in the Scell
assignedR10CsiConfIn dex2Ri
MRBTS/LNBTS/LNCEL/A PUCCH
RI configuration index used in PUCCH allocation
assignedRiConfigInde x
MRBTS/LNBTS/LNCEL/A PUCCH
Selection of PRACH selectPrachRegion region in automatic PUCCH allocation
MRBTS/LNBTS/LNCEL/A PUCCH
Automatic PUCCH configuration identifier
aPucchId
MRBTS/LNBTS/LNCEL/A PUCCH
Manual PUCCH configuration identifier
mPucchId
MRBTS/LNBTS/LNCEL/M PUCCH
Table 10
Parameters modified by LTE1130 Full name
Issue: 01 Draft
Descriptions of radio resource management and telecom features
Abbreviated name
Managed object
Add number active UEs radio reason handover
addAUeRrHo
MRBTS/L NBTS/LN CEL/MPU CCH
Add number active UEs time critical handover
addAUeTcHo
MRBTS/L NBTS/LN CEL/MPU CCH
Add Emergency Sessions
addEmergencySessi MRBTS/L ons NBTS/LN CEL/MPU CCH
Cell Sr Periodicity
cellSrPeriod
MRBTS/L NBTS/LN CEL/MPU CCH
CQI periodicity network cqiPerNp period
MRBTS/L NBTS/LN CEL/MPU CCH
Delta cyclic shift for PUCCH
deltaPucchShift
MRBTS/L NBTS/LN CEL/MPU CCH
Max Number RRC
maxNumRrc
MRBTS/L NBTS/LN CEL/MPU CCH
DN09237915
Parent structure
43
Descriptions of radio resource management and telecom features
Table 10
FDD-LTE16A, Feature Descriptions and Instructions
Parameters modified by LTE1130 (Cont.) Full name
Abbreviated name
Parent structure
Max Number RRC Emergency
maxNumRrcEmergenc MRBTS/L y NBTS/LN CEL/MPU CCH
ACK/NACK offset
n1PucchAn
MRBTS/L NBTS/LN CEL/MPU CCH
PUCCH bandwidth for CQI nCqiRb
MRBTS/L NBTS/LN CEL/MPU CCH
Number of PUCCH PRBs for HARQ Format 3
nPucchF3Prbs
MRBTS/L NBTS/LN CEL/MPU CCH
PHICH duration
phichDur
MRBTS/L NBTS/LN CEL/MPU CCH
PHICH resource
phichRes
MRBTS/L NBTS/LN CEL/MPU CCH
Rank indication reporting enable
riEnable
MRBTS/L NBTS/LN CEL/MPU CCH
Multiplier M for periodic RI reporting period
riPerM
MRBTS/L NBTS/LN CEL/MPU CCH
Periodic RI reporting offset
riPerOffset
MRBTS/L NBTS/LN CEL/MPU CCH
Table 11
Existing parameters related to LTE1130 Full name
Abbreviated name
Managed object
Parent structure
Activate support of conversational voice bearer
actConvVoice
MRBTS/L NBTS
-
Activation of downlink carrier aggregation
actDLCAggr
MRBTS/L NBTS
-
MRBTS/L NBTS
-
Activate emergency call actEmerCallRedir via redirection
44
Managed object
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 11
Descriptions of radio resource management and telecom features
Existing parameters related to LTE1130 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
Activate support of IMS actIMSEmerSessR9 emergency sessions for Rel 9 UE
MRBTS/L NBTS
-
Activate multiple bearers
actMultBearers
MRBTS/L NBTS
-
Activate DRX
actDrx
MRBTS/L NBTS/LN CEL
-
Activate fast adaptive MIMO switch
actFastMimoSwitch MRBTS/L NBTS/LN CEL
Activate load adaptive PDCCH
actLdPdcch
Add number DRB radioReasHo
addNumDrbRadioRea MRBTS/L sHo NBTS/LN CEL
Add number DRB timeCriticalHo
addNumDrbTimeCrit MRBTS/L icalHo NBTS/LN CEL
MRBTS/L NBTS/LN CEL
-
Add number QCI1 DRB for addNumQci1DrbRadi MRBTS/L radioReasHo oReasHo NBTS/LN CEL Add number QCI1 DRB for addNumQci1DrbTime MRBTS/L timeCriticalHo CriticalHo NBTS/LN CEL
Issue: 01 Draft
Blanked PUCCH resources blankedPucch
MRBTS/L NBTS/LN CEL
-
Downlink channel bandwidth
dlChBw
MRBTS/L NBTS/LN CEL
-
Downlink MIMO mode
dlMimoMode
MRBTS/L NBTS/LN CEL
-
Maximum number of OFDM symbols for PDCCH
maxNrSymPdcch
MRBTS/L NBTS/LN CEL
-
Max number act DRB
maxNumActDrb
MRBTS/L NBTS/LN CEL
-
Maximum number of active UEs
maxNumActUE
MRBTS/L NBTS/LN CEL
-
Max number QCI1 DRBs (GBRs)
maxNumQci1Drb
MRBTS/L NBTS/LN CEL
-
DN09237915
45
Descriptions of radio resource management and telecom features
Table 11
FDD-LTE16A, Feature Descriptions and Instructions
Existing parameters related to LTE1130 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
Max number of secondary maxNumScells cells for DL carrier aggr
MRBTS/L NBTS/LN CEL
-
PRACH frequency offset
prachFreqOff
MRBTS/L NBTS/LN CEL
-
PUCCH cyclic shift for mixed formats
pucchNAnCs
MRBTS/L NBTS/LN CEL
-
Target UL outer scheduling region
selectOuterPuschR MRBTS/L egion NBTS/LN CEL
SRS feature srsActivation activation/deactivation
MRBTS/L NBTS/LN CEL
-
Uplink channel bandwidth
ulChBw
MRBTS/L NBTS/LN CEL
-
DRX smart profile 2
drxSmartProfile2
MRBTS/L NBTS/LN CEL/SDR X
-
DRX smart profile 3
drxSmartProfile3
MRBTS/L NBTS/LN CEL/SDR X
-
DRX smart profile 4
drxSmartProfile4
MRBTS/L NBTS/LN CEL/SDR X
-
DRX smart profile 5
drxSmartProfile5
MRBTS/L NBTS/LN CEL/SDR X
-
For parameter descriptions, see FDD-LTE BTS Parameters. Sales information Table 12
LTE1130 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
3.3 LTE1723: S1-based Handover towards Home eNB The LTE1723: S1-based Handover towards Home eNB feature enhances the LTE54: Intra-LTE Handover via S1 and LTE1442: Open-access Home eNodeB Mobility features.
46
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
While LTE54: Intra-LTE Handover via S1 allows an S1 handover to regular (not home eNB (HeNB)) neighbors, LTE1723: S1-based Handover towards Home eNB enhances this functionality to allow the S1 handover to HeNBs. The LTE1442: Open-access Home eNodeB Mobility feature allows mobility to an HeNB via release with redirection. This delays the handover as the UE must transition to an idle state and reconnect to the target HeNB. The LTE1723: S1-based Handover towards Home eNB reduces the delay by allowing a connected-mode handover to the HeNB.
3.3.1 LTE1723 benefits The LTE1723: S1-based Handover towards Home eNB feature provides the following benefit: •
reduction of the delay by allowing a connected-mode handover to HeNB
3.3.2 LTE1723 functional description The LTE1723: S1-based Handover towards Home eNB feature enables a handover towards an open-access HeNB, using the S1 interface. The HeNBs are identified by an operator-configurable range of pre-reserved physical cell IDs (PCIs) per frequency layer. Physical cell ID The same PCI might be used by multiple HeNBs within a single macro cell. A common cell individual offset can be applied to all PCIs in the HeNB's range for a given frequency. This enables prioritizing handovers to the HeNB's neighbors. Additionally, the HeNB PCIs can be blacklisted, which causes the HeNB's exclusion from a handover selection. The PCI is configured by the Home eNB first PCI (pciFirst) and Home eNB last PCI (pciLast) parameters. S1 handover towards an HeNB If the UE’s handover measurement report includes a neighbor PCI in the reserved range, the neighbor eNB is considered as an HeNB. Automatic neighbor relation (ANR) is not triggered for such PCIs. If the target selection algorithm determines that a handover to this HeNB is required, a reportCGI measurement with autonomous gaps is triggered to uniquely identify the neighbor HeNB. The autonomous gaps allow UE to halt Tx/Rx of the serving cell to perform measurements to read MIB/SIB of the neighbor cell without informing the serving cell. After successfully retrieving the target HeNB E-UTRAN cell global identifier (ECGI), an S1 handover is triggered using the target global eNB ID. In case the target cell ECGI cannot be retrieved (not supported by a UE or due to procedure timeout/failure), an RRC connection release with redirection is triggered by the LTE1442: Open-access Home eNodeB Mobility feature.
3.3.3 LTE1723 system impact Interdependencies between features The following features must be activated before activating the LTE1723: S1-based Handover towards Home eNB feature: • •
Issue: 01 Draft
LTE1442: Open-access Home eNodeB Mobility LTE54: Intra-LTE Handover via S1
DN09237915
47
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
The following features must be enabled if the feature functionality is required for Home eNBs: • • • • • •
LTE55: Inter-frequency Handover LTE1060: TDD–FDD Handover LTE1127: Service-based Mobility Trigger LTE1387: Intra-eNodeB Inter-frequency LB LTE1170: Inter-frequency Load Balancing Management Data LTE1531: Inter-frequency Load Balancing Extension
The LTE1723: S1-based Handover towards Home eNB feature impacts the following features: •
LTE2503: Emergency-call-based Mobility Trigger The LTE2503: Emergency-call-based Mobility Trigger feature is supported for home eNB targets.
Impact on interfaces The LTE1723: S1-based Handover towards Home eNB feature has no impact on interfaces. Impact on network management tools The LTE1723: S1-based Handover towards Home eNB feature has no impact on network management tools. Impact on system performance and capacity The LTE1723: S1-based Handover towards Home eNB feature impacts system performance and capacity as follows: •
• • •
Latency: Instead of redirection (LTE1442), the feature allows mobility to an HeNB with an S1-based handover. This reduces the service interrupt time, since the UE does not have to release the active connection and reconnect to the target HeNB. The execution time of the S1 handover is not different from usual Intra-LTE S1 HO times, but the HO preparation time is longer due to the CGI measurement. Quality: slight increase in the E-RAB drop rate due to a longer handover preparation time Throughput: possible temporary reduction during a handover VoLTE: Due to longer handover preparation times, a slight increase in the voice packet loss rate, and a slight degradation of voice quality and VoLTE call drop rates are possible.
3.3.4 LTE1723 reference data Requirements Table 13
48
LTE1723 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
not supported
Flexi Multiradio 10 BTS
Multiradio S4
FL16A
FL17
DN09237915
Flexi Zone Micro BTS FL16A
Flexi Zone Access Point FL16A
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 13 Flexi Zone Controller FL16A
Descriptions of radio resource management and telecom features
LTE1723 hardware and software requirements (Cont.) OMS
UE
LTE OMS16A
3GPP R8 UE capabilities
NetAct NetAct 16.8
MME support not required
SAE GW support not required
Alarms There are no alarms related to the LTE1723: S1-based Handover towards Home eNB feature. BTS faults and reported alarms There are no faults related to the LTE1723: S1-based Handover towards Home eNB feature. Commands There are no commands related to the LTE1723: S1-based Handover towards Home eNB feature. Measurements and counters Table 14 Counter ID
Issue: 01 Draft
New counters introduced by LTE1723 Counter name
Measurement
M8008C24
Requested SI reports for Home eNB
LTE RRC
M8008C25
Successful SI reports for Home eNB
LTE RRC
M8008C26
Incomplete SI reports for Home eNB
LTE RRC
M8042C1
Inter-eNB S1 Handover preparations for VoLTE (QCI1) to Home eNB
LTE Inter Home eNB Handover
M8042C2
Inter-eNB S1 Handover attempts for VoLTE LTE Inter Home eNB Handover (QCI1) to Home eNB
M8042C3
Successful Inter-eNB S1 Handovers for VoLTE (QCI1) to Home eNB
LTE Inter Home eNB Handover
M8042C4
Inter-eNB S1 HO preparations to Home eNB
LTE Inter Home eNB Handover
M8042C5
Failed Inter-eNB HO preparations per neighbor HENB due to expiry of guarding timer
LTE Inter Home eNB Handover
M8042C6
Failed Inter-eNB S1 HO preparations per neighbor HENB due to AC in the target eNB
LTE Inter Home eNB Handover
M8042C7
Failed Inter-eNB S1 HO preparations per neighbor HENB due to other reasons
LTE Inter Home eNB Handover
M8042C8
Inter-eNB S1 Handover attempts per neighbor Home eNB
LTE Inter Home eNB Handover
M8042C9
Successful Inter-eNB S1 Handovers to Home eNB
LTE Inter Home eNB Handover
M8042C10
Failed Inter-eNB S1 Handover to Home eNB
LTE Inter Home eNB Handover
M8042C11
Inter-Frequency Handover to Home eNB
LTE Inter Home eNB Handover
M8042C12
Successful Inter-Frequency Handover to Home eNB
LTE Inter Home eNB Handover
DN09237915
49
Descriptions of radio resource management and telecom features
Table 14
FDD-LTE16A, Feature Descriptions and Instructions
New counters introduced by LTE1723 (Cont.)
Counter ID
Counter name
M8042C13
Measurement
Inter-Frequency Handover failures to Home eNB due to expiry of guarding timer
LTE Inter Home eNB Handover
For counter descriptions, see LTE Radio Access Operating Documentation/Reference/Counters. Key performance indicators There are no key performance indicators related to the LTE1723: S1-based Handover towards Home eNB feature. Parameters Table 15
New parameters introduced by LTE1723 Full name
Abbreviated name
Managed object
Parent structure
Activate home eNB S1 mobility
actHeNBS1Mobility LNBTS
eNB ID size
enbIdSize
LNHENB
-
LTE inter home eNB handover
mtInterHomeeNBHo
PMRNL
-
Table 16
-
Existing parameters supported by LTE1723 Full name
Abbreviated name
Managed object
Parent structure
Activate home eNB mobility
actHeNBMobility
LNBTS
-
Activate intra LTE S1based handover
actLTES1Ho
LNBTS
-
Home eNB first PCI
pciFirst
LNHENB
-
Home eNB last PCI
pciLast
LNHENB
-
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 17
LTE1723 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
3.4 LTE2057: Extended Measurement Control The LTE2057: Extended Measurement Control feature provides extended measurement control in mobility. It concerns networks with overlapping multiple inter-frequency layers. The feature enables efficient handling of the A3, A4, and A5 inter-frequency measurement configurations.
50
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
3.4.1 LTE2057 benefits The LTE2057: Extended Measurement Control feature provides the following benefits: • • •
better traffic management less signalling involved less UE power consumption
The benefits are achieved by selecting the most suitable frequencies and controling the order of frequency groups.
3.4.2 LTE2057 functional description 3.4.2.1
Measurements and measurement reports Handover initiation caused by measurements reports The UE assists the eNB regarding a handover by sending measurement reports. When verifying radio conditions due to UE mobility (for example when the UE moves from one LTE cell to another or because of limited LTE coverage), measurement reports may initiate a handover. The type of measurements to be made by the UE, and the details of reporting them to the eNB, can be configured (measurement configuration and report configuration), and the eNB informs the UE about the configurations via the RRC: CONNECTION RECONFIGURATION message. Measurement reports In order to limit the amount of signaling, the UE only sends measurement reports (RRC: MEASUREMENT REPORT messages) to the eNB when certain conditions (events) are met by the UEs' measurements. The following events are defined in the LTE standard: • • • • • • • •
Event A1: The serving cell becomes better than an absolute threshold. Event A2: The serving cell becomes worse than an absolute threshold. Event A3: An LTE neighbor cell becomes better than an offset relative to the serving cell. Event A4: An LTE neighbor cell becomes better than an absolute threshold. Event A5: The serving cell becomes worse than an absolute threshold, and an LTE neighbor cell becomes better than another absolute threshold. Event A6: Neighbour becomes offset better than secondary cell (SCell) Event B1: A non-LTE neighbor cell becomes better than an absolute threshold. Event B2: The serving cell becomes worse than an absolute threshold, and a nonLTE neighbor cell becomes better than another absolute threshold.
The events from A1 to A6 are related to intra-LTE handovers; B1 and B2 events are related to inter-RAT handovers. A1 is useful for restricting UE measurements to the serving cell only; A3 is connected with a better cell handover and A5 with a coverage handover. The events correspond with the type of measurements the UE performs. Currently, A1, A2, A3, A5, A6 and B1, B2 events are supported. The measurement reports contain a list of target cells for a handover. The target cells are listed in order of decreasing value of the reporting quantity, that is, the best cell is reported first. As a consequence of the definition of the events, the target cell list cannot be empty. Handover conditions due to A5 get a higher priority than handovers due to A3.
Issue: 01 Draft
DN09237915
51
Descriptions of radio resource management and telecom features
3.4.2.2
FDD-LTE16A, Feature Descriptions and Instructions
Inter-frequency handover The eNB supports an inter-frequency handover in which the handover decision is based on reference symbol received power (RSRP) or reference signal received quality (RSRQ) (DL measurement). Triggers can be "coverage HO" and "Better Cell HO." Typically, a UE requires measurement gaps for doing inter-frequency measurements, depending on the UE capability. The UE performance measurements are typically done while data transmission between the UE and source eNB is still performed. Therefore, such KPIs as a U-plane break duration or C-plane break duration do not depend on these UE performance measurements, and the system performance of an inter-frequency HO is expected to be the same as for an intra-frequency HO. An inter-frequency handover enables service continuity for an LTE deployment in different frequency bands as well as for LTE deployments within one frequency band but with different center frequencies. These center frequencies can also cover cases with different bandwidths, for example 5 MHz and 10 MHz.
3.4.2.3
LTE2057 overview Final frequency list The main idea of the LTE2057: Extended Measurement Control feature is to support the enhanced mechanism of managing the inter-frequency measurement configuration. It allows the operator to select and organize LTE frequencies for the A3, A4, and A5 measurements. The specific priority groups determine the way frequencies are handled when configuring the UE for inter-frequency measurements. This list of frequencies is composed according to different inputs: group priority and frequency priority. The selection of frequencies belonging to one group is done according to an operatorconfigurable preference. With the LTE2057: Extended Measurement Control feature, the operator is able to assign: • • • • •
frequencies to different frequency groups frequency priority (within the assigned group) to a frequency group priority to each defined group that determines the group's position in the final frequency list group size to each defined group to reserve a certain number of places in the final frequency list for the related group's frequencies frequency selection method to each defined group that determines the way frequencies are selected from the related group
Frequency selection methods Several groups can be defined in one cell. For each group, a selection method can be established (which is independent from the selection methods defined for other groups in a cell). Frequency selection methods are: 1. Fixed order within a group – the frequencies are selected for the final list in descending order of priority.
52
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
2. Equal probability randomization – for each slot in group x, a frequency is selected out of the frequencies assigned to this group by applying the same probability. One frequency is drawn randomly out of the number of frequencies for each slot in the group. 3. Weighted probability randomization within a group – for each slot in group x, a frequency is selected out of the frequencies assigned to this group by applying a weighted probability. The algorithm starts with an empty final frequency list. Frequencies are chosen for the final list from groups according to their descending group priority. The selection starts from the highest priority group and ends with the group of the lowest priority. Number of frequencies equalling group size is chosen from a group according to a selection method of that group. It is placed on the end of a current list until there are no more frequencies on the final list. A selection method can be choosen by an operator with the following parameters (new MOCs introduced): • •
Selection method in default group profile (algSelection) from the IFGDPR group (default frequencies group with the lowest priority) Selection method in dedicated group profile (algSelection) from the IFGPR group (frequencies group)
LTE2057 algorithm The frequencies for the final list are selected and ordered according to the operator's parameter settings. The ordered set of the frequencies influences the content of the RRC: Connection Reconfiguration message in the following way: •
•
The measId IEs (from the lowest to the highest ID) are assigned to measurements according to the order of the frequencies they are based on (from the highest to the lowest priority). The measId IEs are ordered in the RRC: Connection Reconfiguration message (MeasIdToAddModList IE) from the lowest to the highest ID.
From all the LTE neighbor frequencies that are known in the cell, a certain subset is determined by legacy filters (with the exclusion of certain frequencies resulting from UE capabilities, used services, etc.). This subset of frequencies is the input for the LTE2057 selection algorithm (see Figure 2: LTE2057 functionality). The algorithm selects and sorts the frequencies according to the operator's parameter settings (groups, priorities, selection methods). The algorithm's output is the final frequency list. Depending on the activated features, a multiple frequency band indicator (MFBI) is applied to the entries of the final frequency list.
Issue: 01 Draft
DN09237915
53
Descriptions of radio resource management and telecom features
Figure 2
FDD-LTE16A, Feature Descriptions and Instructions
LTE2057 functionality
LNHOIF=frequenciesinanetwork g=group fp=frequencypriority
LNHOIF1 g fp
LNHOIF2 g fp
LNHOIF3 g fp
...
LNHOIF16 g fp
LEGACYFILTER (LTE1060,LTE490,LTE1905,LTE1942)
LNHOIF3 g fp
LNHOIF5 g fp
LNHOIF6 g fp
LNHOIF 14 g fp
pre-finalfrequencylist(LTE2008)
LTE2057alghorithm
MFBIfrequencytranslation
54
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
g
Descriptions of radio resource management and telecom features
Note: With a new Activation of 3FDD plus 3TDD restriction (act3fdd3tddRestrict) parameter, it is possible to configure maximum three FDD and three TDD inter-frequencies in the final frequency list if the UE supports only 3GPP Release 8 and 9. If the
Activate support for up to six Inter-freq measurement (actSixIfMeasurements) parameter is set to true, then the Activation of 3FDD plus 3TDD restriction (act3fdd3tddRestrict) parameter must be configured.
3.4.3 LTE2057 system impact Interdependencies between features The LTE2057: Extended Measurement Control feature is impacted by the following features: •
•
•
•
•
•
•
•
• •
•
•
Issue: 01 Draft
LTE55: Inter-frequency Handover An additional algorithm for A3/A5 measurement event responsible for selecting frequencies needs to be configured. LTE1060: TDD – FDD Handover An additional algorithm for A3/A5 measurement event responsible for selecting frequencies needs to be configured. LTE1127: Service-based Mobility Trigger An additional algorithm for A4 measurement event responsible for selecting frequencies needs to be configured. Some additional filter criteria from LTE1127 have to be taken into account before the LTE2057 selection algorithm becomes active. LTE1387: Intra-eNodeB IF Load Balancing An additional algorithm for A4 measurement event responsible for selecting frequencies needs to be configured. LTE1170: Inter-eNodeB IF Load Balancing An additional algorithm for A4 measurement event responsible for selecting frequencies needs to be configured. Some additional filter criteria from LTE2008 have to be taken into account before the LTE2057 selection algorithm becomes active. LTE1531: Inter-frequency Load Balancing Extension An additional algorithm for A4 measurement event responsible for selecting frequencies needs to be configured. LTE1841: Inter-Frequency Load Equalization An additional algorithm for A4 measurement event responsible for selecting frequencies needs to be configured. LTE2008: Extended Inter-frequency Measurements If the actSixIfMeasurements parameter is set to true, then the act3fdd3tddRestrict parameter must be configured. LTE2051: Measurement-based Idle Mode Load Balancing No change in the selection of frequency has to be measured (A4). LTE2108: Redirected VoLTE Call Setup An additional algorithm for A4 measurement event responsible for selecting frequencies needs to be configured. LTE2388: VoLTE Call Steering Enhancement An additional algorithm for A4 measurement event responsible for selecting frequencies needs to be configured. LTE490: Subscriber Profile-based Mobility
DN09237915
55
Descriptions of radio resource management and telecom features
•
•
FDD-LTE16A, Feature Descriptions and Instructions
There is an expansion of additional algorithm for selecting target frequencies based on filters from mobility profiles selected with SPID. LTE1905: PLMN ID and SPID Selected Mobility Profiles There is an expansion of additional algorithm for selecting target frequencies. It is based on filters from mobility profiles selected with public land mobile network (PLMN) ID or combined values of service provider identification (SPID) and PLMN ID. LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List An expansion of additional filter criteria from LTE1942 has to be taken into account before the LTE2057 selection algorithm becomes active.
Impact on interfaces The LTE2057: Extended Measurement Control feature has no impact on interfaces. Impact on network management tools The LTE2057: Extended Measurement Control feature has no impact on network management tools. Impact on system performance and capacity The LTE2057: Extended Measurement Control feature impacts system performance and capacity as follows: •
•
The LTE2057 algorithm selects frequency based on available neighbor relation knowledge (the default selection method is weighted probability randomization). This leads to an improved measurement success rate and faster handover decisions. The usage of group priorities and selection methods leads to a UE contribution to the preferred frequency layers. If the feature is configured, all available frequencies are used for inter-frequency mobility. This can lead to a more balanced usage of different frequencies and have a positive impact on system capacity.
3.4.4 LTE2057 reference data Requirements Table 18
LTE2057 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
AirScale BTS
FL16A
not supported
UE
LTE OMS16A
3GPP R8 UE capabilities
NetAct NetAct 16.8
Flexi Zone Micro BTS FL16A MME support not required
Flexi Zone Access Point FL16A SAE GW support not required
Alarms There are no alarms related to the LTE2057: Extended Measurement Control feature. Commands There are no commands related to the LTE2057: Extended Measurement Control feature. Measurements and counters
56
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
There are no measurements or counters related to the LTE2057: Extended Measurement Control feature. Key performance indicators There are no key performance indicators related to the LTE2057: Extended Measurement Control feature. Parameters Table 19
New parameters introduced by LTE2057 Full name
Abbreviated name
Managed object
Parent structure
LNBTS
-
Activation of 3FDD plus act3fdd3tddRestri LNCEL 3TDD restriction ct
-
Activation for extended actExtMeasCtrl inter-freq measurement control
Selection method in default group profile
algSelection
IFGDPR
-
Group priority in default group profile
groupPrio
IFGDPR
-
Group Size in default group profile
groupSize
IFGDPR
-
Selection method in algSelection dedicated group profile
IFGPR
-
Group priority in groupPrio dedicated group profile
IFGPR
-
Group Size in dedicated groupSize group profile
IFGPR
-
Inter-frequency group priority
iFGroupPrio
LNHOIF
-
Inter-frequency priority
iFPrio
LNHOIF
-
Table 20
Existing parameters related to LTE2057 Full name
Abbreviated name
Managed object
Activate support for up actSixIfMeasureme LNCEL to six Inter-freq nts measurement
Parent structure -
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 21
LTE2057 sales information
Product structure class Application software (ASW)
Issue: 01 Draft
License control SW asset monitoring
DN09237915
Activated by default No
57
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
3.5 LTE2276: Measurement-based SCell Selection The LTE2276: Measurement-based SCell Selection feature introduces a measurementbased secondary cell (SCell) selection for carrier aggregation (CA).
3.5.1 LTE2276 benefits The main benefit of the LTE2276: Measurement-based SCell Selection feature is that the eNB can select the secondary cells (SCells) which are to be added, based on the respective UE quality indication rather than blindly via configuration parameters. Additionally, by selecting the SCells for carrier aggregation (CA) based on the UE measurements, the LTE2276 feature optimizes: • • •
SCell resource utilization UE power consumption data throughput
3.5.2 LTE2276 functional description The LTE2276: Measurement-based SCell Selection feature enhances the eNB secondary cell (SCell) selection criteria for carrier aggregation (CA). It is done by supplying the list of candidate SCells that are measured by the UE with a pre-defined minimum channel quality. The operator can decide per frequency layer whether to enable a measurement-based SCell selection or a blind SCell selection. The measurement type to apply to SCell discovery is the A3 event with “report on leave” – a neighbor cell becomes offset better than a serving cell. Figure 3
SCell discovery measurement
Measured quantity
PCell
candidateSCell
Time-to-trigger
Time
In order to minimize the impacts on the UE throughput, the inter-frequency measurements are activated only on those frequencies for which the UE does not require measurement gaps. The eNB first tries to add SCells that have been measured
58
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
by the UE with sufficient quality, using normalized load compare value (NLCV biased by the respective sFreqPrio) as discriminating factor if there are multiple choices for the SCell addition selection, for more information, see LTE2233: N-out-of-M Downlink Carrier Aggregation feature. Only if no UE measured SCell can be added, the eNB will try to add SCells blindly, that is not measured SCells. The LTE2276: Measurement-based SCell Selection feature works only with step-wise SCell addition (when the numTxWithHighNonGbr parameter value is greater than 0) and is activated with the Activate A3-based SCell selection (actA3ScellSelect) activation flag. The operator decides for which frequency layer the measurement for A3 event is enabled by configuring the Enable measurements for A3 event (enableA3Event) parameter. Additionally the following parameters are defined for A3 event configuration: •
A3 trigger quantity (a3TriggerQuantity) – this parameter defines which quantity (reference symbol received power (RSRP) or reference signal received quality (RSRQ)) the UE has to use for triggering an event A3 SCell discovery measurement report. Additionally thresholds for filtering candidate SCells out of the cells reported by the UE can be defined by setting: – –
•
•
•
SCell measurement threshold for RSRP (scellMeasThreshRsrp) SCell measurement threshold for RSRQ (scellMeasThreshRsrq)
A3 time to trigger (a3TimeToTrigger) This parameter defines the time for which the specific criteria for the A3 event SCell discovery measurement must be met in order to trigger a measurement report. A3 offset (a3Offset) This parameter defines a margin for the A3 event for an SCell discovery measurement. The default value of this parameter is -3. Negative values for this parameter are recommended. Related hysteresis of offset a3Offset neighbor becomes offset better than serving cell (hysA3Offset) This parameter defines a related hysteresis of a3Offset.
Candidate SCells on a frequency layer that has not been enabled for the A3 event SCell discovery measurement is assumed by the system to have the same radio coverage of the PCell and therefore have assigned the same priority as the UE measured candidate SCells in the SCell addition selection. Candidate SCells on a frequency layer that has been enabled for the A3 event SCell discovery measurement but that not measured by the UE (because it would have needed measurement gaps) have assigned lower priority than the UE measured candidate SCells, therefore are selected for addition only if there is no better choice. The LTE2276 feature is beneficial in the following scenarios: • •
Issue: 01 Draft
Scenario 1: the PCell has two candidate SCells on the same frequency layer, with different radio coverage Scenario 2: the PCell has several candidate micro SCells on the same frequency layer, with different radio coverage
DN09237915
59
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
Figure 4
Scenario 1 for LTE2276
Figure 5
Scenario 2 for LTE2276
3.5.3 LTE2276 system impact Interdependencies between features The following features must be activated before activating the LTE2276: Measurementbased SCell Selection feature:
60
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
Descriptions of radio resource management and telecom features
At least one of the following downlink (DL) carrier aggregation features: – – – – –
LTE1089: Downlink Carrier Aggregation – 20 MHz LTE1558: TDD Downlink Carrier Aggregation LTE1858: FDD Inter-band/Intra-band Carrier Aggregation with Two Flexi Zone Micro BTSs LTE1332: Downlink Carrier Aggregation – 40 MHz LTE1803: Downlink Carrier Aggregation 3CC – 40 MHz
The LTE2276: Measurement-based SCell Selection feature is impacted by the following features: •
LTE1541: Advanced SCell Measurement Handling In the step-wise Scell selection, UE measured candidate SCells as well as candidate SCells on a frequency layer not enabled for A3 event Scell discovery measurements have highest priority in the Scell addition selection.
Impact on interfaces The LTE2276: Measurement-based SCell Selection feature has no impact on interfaces. Impact on network management tools The LTE2276: Measurement-based SCell Selection feature has no impact on network management tools. Impact on system performance and capacity The LTE2276: Measurement-based SCell Selection feature has no impact on system performance and capacity.
3.5.4 LTE2276 reference data Requirements Table 22
LTE2276 hardware and software requirements
System release FDD-LTE 16A Flexi Zone Controller FL16A
Flexi Multiradio BTS not supported OMS
Flexi Multiradio 10 BTS FL16A UE
LTE OMS16A
Flexi Zone Micro BTS FL16A
NetAct
3GPP R10 UE NetAct 16.8 capabilities
Flexi Zone Access Point FL16A
MME Support not required
SAE GW Support not required
3GPP R11 UE capabilities 3GPP R12 UE capabilities
BTS faults and reported alarms There are no faults related to the LTE2276: Measurement-based SCell Selection feature. Commands
Issue: 01 Draft
DN09237915
61
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
There are no commands related to the LTE2276: Measurement-based SCell Selection feature. Measurements and counters There are no measurements or counters related to the LTE2276: Measurement-based SCell Selection feature. Key performance indicators There are no key performance indicators related to the LTE2276: Measurement-based SCell Selection feature. Parameters Table 23
New parameters introduced by LTE2276 Full name
62
Abbreviated name
Managed object
Parent structure
Activate A3-based SCell selection
actA3ScellSelec t
MRBTS/LNBTS
-
A3 offset
a3Offset
MRBTS/LNBTS/CADPR
-
A3 time to trigger
a3TimeToTrigger
MRBTS/LNBTS/CADPR
-
A3 trigger quantity
a3TriggerQuanti ty
MRBTS/LNBTS/CADPR
-
Enable measurements for A3 event
enableA3Event
MRBTS/LNBTS/CADPR
-
Related hysteresis of offset a3Offset neighbor becomes offset better than serving cell
hysA3Offset
MRBTS/LNBTS/CADPR
-
SCell measurement threshold for RSRP
scellMeasThresh Rsrp
MRBTS/LNBTS/CADPR
-
SCell measurement threshold for RSRQ
scellMeasThresh Rsrq
MRBTS/LNBTS/CADPR
-
A3 offset
a3Offset
MRBTS/LNBTS/LNCEL/C APR
A3 time to trigger
a3TimeToTrigger
MRBTS/LNBTS/LNCEL/C APR
A3 trigger quantity
a3TriggerQuanti ty
MRBTS/LNBTS/LNCEL/C APR
Enable measurements for A3 event
enableA3Event
MRBTS/LNBTS/LNCEL/C APR
Related hysteresis of offset a3Offset neighbor becomes offset better than serving cell
hysA3Offset
MRBTS/LNBTS/LNCEL/C APR
SCell measurement threshold for RSRP
scellMeasThresh Rsrp
MRBTS/LNBTS/LNCEL/C APR
SCell measurement threshold for RSRQ
scellMeasThresh Rsrq
MRBTS/LNBTS/LNCEL/C APR
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 24
Descriptions of radio resource management and telecom features
Existing parameters related to LTE2276 Full name
Abbreviated name
Managed object
Parent structure
Activation of downlink carrier aggregation
actDLCAggr
MRBTS/LNBTS
-
Number of sampled subframes with High Non-GBR traffic
numTxWithHighNonG MRBTS/LNBTS br
-
For parameter descriptions, see FDD-LTE BTS Parameters. Sales information Table 25
LTE2276 sales information
Product structure class
License control
Application software (ASW)
SW Asset Monitoring
Activated by default No
3.6 LTE2291: Support for Carrier Aggregation on CL16A Release The LTE2291: Support for Carrier Aggregation on CL16A Release feature introduces CRAN support for the LTE2007: Inter-eNodeB Carrier Aggregation feature. The CRAN system is employed to support inter-eNB DL carrier aggregation (CA) for two different, co-located eNBs.
3.6.1 LTE2291 benefits The LTE2291: Support for Carrier Aggregation on CL16A Release feature provides the following benefit: •
It supports a DL capacity increase via an inter-eNB carrier aggregation (CA) solution as well as a UL capacity increase via CRAN.
3.6.2 LTE2291 functional description The LTE2291: Support for Carrier Aggregation on CL16A Release feature allows the carrier aggregation between eNBs. The carriers may be of the same or different frequency bands. Since within a CRAN system all UL carriers of a eNB must be the same, and UL and DL carriers are the same within an eNB, no CA pairing is allowed between cells within that system. The LTE2291: Support for Carrier Aggregation on CL16A Release feature utilizes all CRAN functionalities from the LTE2564: CRAN Evolution CL16A feature with one exception, CA activation does not allow using the 4Tx2Rx MIMO mode in the CRAN system. CA with CRAN uses only CA in DL as two transmitters (2Tx) with associated DL performance. There are two possible CA configuration scenarios: Double-sided CRAN system
Issue: 01 Draft
DN09237915
63
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
Two separate CRAN systems exist with different frequencies: f1 and f2. The FSMFs are paired together so that FSMF at f1 frequency is a part of 1st cranID (1st CRAN system), and the other FSMF at f2 frequency is part of 2nd cranID (2nd CRAN system). In a double-sided CRAN system, CA is established between two FSMFs (primary (P) and secondary (S) cells are configured across the pair). Single-sided CRAN system One CRAN system exists with the f1 frequency. The FSMFs at f2 frequency might be paired for CA, but FSMFs at f2 frequency are not part of a CRAN system. FSMFs synchronization In CRAN, an eNB configured as a sync hub direct forward (SHDF) master, uses GPS or timing over packet (ToP) as a source of timing signal. ToP can be used either in phase or frequency mode. The GPS signal is the recommended source of timing signal. If an eNB is configured as a sync hub master, the interconnected eNBs have to be configured as sync hub slaves and have to use the phase sync mode.
g
Note: The frequency mode on sync hub master is not recommended as it causes restarts of all eNBs in a sync chain when the sync hub master eNB is restarted. The eNBs that are connected in the CA cluster use sync source options supported by the LTE1710: Sync Hub Direct Forward feature. The LTE2291: Support for Carrier Aggregation on CL16A Release feature's recommendation as a sync source is GPS. If a Master eNB with ToP in frequency mode synchronization is restarted, all interconnected eNBs in a synchronization chain might restart autonomously to align to a new synchronization signal from the synchronization Master; hence, ToP in a frequency mode is not recommended.
g
Note: It is required that the btsSyncMode parameter be in a phase synchronization mode setting for SHDF in the LTE2007: Inter-eNodeB Carrier Aggregation feature. This applies to all eNBs which employ the LTE2291: Support for Carrier Aggregation on CL16A Release feature.
3.6.3 LTE2291 system impact Interdependencies between features The following features must be activated before activating the LTE2291: Support for Carrier Aggregation on CL16A Release feature: • • •
LTE2007: Inter-eNB Carrier Aggregation LTE1710: Sync Hub Direct Forward LTE2564: CRAN Evolution CL16A
The LTE2291: Support for Carrier Aggregation on CL16A Release feature impacts the following features: •
LTE2007: Inter-eNB Carrier Aggregation The part of this feature which is related to 3CC is not supported in conjunction with the LTE2291: Support for Carrier Aggregation on CL16A Release feature. The LTE2007: Inter-eNB Carrier Aggregation feature provides a deliverable that enables CA operation on the necessary 4 DSP deployment that CRAN uses.
Impact on interfaces
64
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
The LTE2291: Support for Carrier Aggregation on CL16A Release feature has no impact on interfaces. Impact on network management tools The LTE2291: Support for Carrier Aggregation on CL16A Release feature has no impact on network management tools. Impact on system performance and capacity The LTE2291: Support for Carrier Aggregation on CL16A Release feature has no impact on system performance or capacity expectations of CRAN for UL outside of what is already specified in the LTE2564: CRAN Evolution CL16A feature. The LTE2291: Support for Carrier Aggregation on CL16A Release feature has no impact on system performance or capacity expectations of DL CA outside of what is already specified in the LTE2007: Inter-eNB Carrier Aggregation feature.
3.6.4 LTE2291 reference data Requirements Table 26
LTE2291 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
not supported
Flexi Zone Controller
OMS
not supported
Flexi Multiradio 10 BTS
Multiradio S4
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
not supported
not supported
not supported
NetAct
MME
SAE GW
UE
LTE OMS16
support not required
support not required
support not required
support not required
BTS faults and reported alarms Table 27
BTS faults related to LTE2291
Fault ID
Fault name
Reported alarms Alarm ID
110014
Optical cable inter-BTS or inter FSP cards too long for CRAN
7651
Alarm name
BASE STATION OPERATION DEGRADED
For fault descriptions, see LTE Radio Access Operating Documentation/Reference/Faults and Alarms. Commands There are no commands related to the LTE2291: Support for Carrier Aggregation on CL16A Release feature. Measurements and counters There are no measurements or counters related to the LTE2291: Support for Carrier Aggregation on CL16A Release feature. Key performance indicators There are no key performance indicators related to the LTE2291: Support for Carrier Aggregation on CL16A Release feature. Parameters
Issue: 01 Draft
DN09237915
65
Descriptions of radio resource management and telecom features
Table 28
FDD-LTE16A, Feature Descriptions and Instructions
Existing parameters related to LTE2291 Full name
Abbreviated name
Managed object
Parent structure
MRBTS/LNBTS
–
Activate inter-eNB DL carrier aggregation
actInterEnbDLCAggr MRBTS/LNBTS
–
BTS ID of the parent eNB of the cell to be aggregated
lnBtsId
Activation of downlink actDLCAggr carrier aggregation
MRBTS/LNBTS/LNCE L/CAREL
–
For parameter descriptions, see LTE Radio Access Operating Documentation/ Reference/Parameters. Sales information Table 29
LTE2291 sales information
Product structure class
License control
Activated by default
Basic Software (BSW)
–
Yes
3.7 LTE2400: Support of User Location Information The LTE2400: Support of User Location Information feature changes the manner of reporting UE location in the S1 Application Protocol (S1AP).
3.7.1 LTE2400 benefits The LTE2400: Support of User Location Information feature provides the following benefit: •
Less signalling is required between the eNB and the MME because the E-UTRAN cell global identifier (CGI) and tracking area identifier (TAI) are sent via three messages instead of one message S1AP: Location Report. The three messages are: – – –
E-RAB Release Response E-RAB Release Indication UE Context Release Complete
3.7.2 LTE2400 functional description 3.7.2.1
S1 Application Protocol The S1 Application Protocol (S1AP) is the E-UTRAN radio network layer signalling protocol for the S1 interface. The S1AP protocol mechanisms handle all procedures between E-UTRAN and the evolved packet core (EPC). The S1AP protocol has, among others, the following functions (see 3GPP TS 36.413, release 13):
66
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• • • • • •
Descriptions of radio resource management and telecom features
E-RAB management (responsible for setting up, modifying, and releasing ERABs, which are triggered by the MME) Initial context transfer (used to establish an S1UE context in the eNB or to set up the default IP connectivity) Mobility (responsible for the eNB change or RAT change) S1 UE context release (responsible for managing the release of UE-specific context in the eNB and the MME) Tracing (used to control a trace session recording for a UE in an ECM_CONNECTED mode) Location reporting (allows the MME to be aware of the UE’s current location)
S1AP services are divided into two groups: • •
3.7.2.2
Non UE-associated services – related to the whole S1 interface instance between the eNB and MME UE-associated services – related to one UE
Location Report message One of the S1AP functions is to provide the MME with the UE's current location. This information is in the S1AP: Location Report message, which is sent by the eNB. Figure 6
Location Report procedure
S1AP:LOCATIONREPORT
MME
ENB
There are six information elements (IEs) in the Location Report message: Message Type, MME UE S1AP ID, eNB UE S1AP ID, E-UTRAN CGI, TAI, and Request Type. If reporting upon the change of a serving cell is requested, the eNB informs whenever the UE changes its serving cell to another cell belonging to the eNB. The Request Type IE indicates what type of location information the eNB should report (E-UTRAN cell global identifier (CGI) or tracking area identifier (TAI)). E-UTRAN CGI is used to globally identify the E-UTRAN cell while the TAI information element is used to uniquely identify a tracking area which the eNBs belong to (at a cell level).
3.7.2.3
LTE2400 overview In general, the location reporting functionality allows MME to be aware of the UE’s current location. The procedure uses UE-associated signalling. The LTE2400: Support of User Location Information feature makes it possible for EUTRAN cell global identity (CGI) and tracking area identity (TAI) IEs to be placed in the following messages:
Issue: 01 Draft
DN09237915
67
Descriptions of radio resource management and telecom features
• • •
FDD-LTE16A, Feature Descriptions and Instructions
E-RAB Release Response E-RAB Release Indication UE Context Release Complete
The different messages have been tabulated below. Table 30
LTE2400 S1AP messages
Message
Sent from/to
Location Report eNB to MME
Function Providing the UE's location to the MME
E-RAB Release Response
eNB to MME
Reporting the outcome of the request from the E-RAB Release Command message
E-RAB Release Indication
eNB to MME
Indicating to the MME to release one or several E-RABs for one UE
UE Context Release Complete
eNB to MME
Confirming the release of the UE-associated S1-logical connection over the S1 interface
User location information which is now placed in the above three messages enables the operator to know where the E-RAB or data sessions are established or dropped. This functionality reduces the amount of signalling between the eNB and the MME. The eNB, if supported, reports the UE location information in the User Location Information IE in the three S1AP messages: • • •
E-RAB Release Response, E-RAB Release Indication, and UE Context Release Complete.
If the User Location Information IE is included in the three messages, the MME handles this information as specified in 3GPP TS 23.401 [11]. The functionality of LTE2400 is activated or deactivated by the Activate support of user location information reporting (actUeLocInfo) parameter.
3.7.3 LTE2400 system impact The LTE2400: Support of User Location Information feature has no impact on features, interfaces, network management tools, and system performance and capacity.
3.7.4 LTE2400 reference data Requirements Table 31
68
LTE2400 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
not supported
Flexi Multiradio 10 BTS
AirScale BTS
FL 16A
FL 16A
DN09237915
Flexi Zone Micro BTS FL 16A
Flexi Zone Access Point FL 16A
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 31
Descriptions of radio resource management and telecom features
LTE2400 hardware and software requirements (Cont.)
Flexi Zone Controller FL 16A
OMS
UE
LTE OMS16A
3GPP R8 mandatory
NetAct
MME
NetAct 16.8
SAE GW
Flexi NS 17
support not required
There are no alarms, commands, measurements and counters, key performance indicators related to the LTE2400: Support of User Location Information feature. Parameters Table 32
New parameters introduced by LTE2400 Full name
Abbreviated name
Activate support of user location information reporting
actUeLocInfo
Managed object LNBTS
Parent structure -
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 33
LTE2400 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
3.8 LTE2445: Combined Supercell The LTE2445: Combined Supercell feature enables combining up to six 2Tx2Rx cells into one supercell.
3.8.1 LTE2445 benefits The LTE2445: Combined Supercell feature provides the following benefits: • •
inter-cell interference reduction in dense network deployments reduction in the number of handovers in a cell combined into a supercell
3.8.2 LTE2445 functional description Up to six 2Tx2Rx cells may be combined into one supercell. The supercell has its own ID and a single physical cell ID (PCI). The Flexi Multiradio BTS supports configuration options for supercells. The radio modules that are utilized in subcells (cells that constitute a supercell) can be either RRH or RF modules. In the case of RRH radio module, subcells may be either co-located or located at different geographical locations.
g Issue: 01 Draft
Note: It is recommended that subcells are not spaced more than 1 km from each other.
DN09237915
69
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
Downlink supercell operation DL supercell operation is performed as follows: • • •
The same signals in DL from every subcell are transmitted simultaneously. Every subcell might be configured with a different maximum power value; In this case, the DL signals are power scaled copies of each other. 2x2 MIMO modes TM3 or TM4 and Tx diversity TM2 are supported.
Uplink supercell operation The eNB selects dynamically the most suitable subcell for each UE. The selection is based on the signal-to-interference-pluse-noise ratio (SINR) for physical uplink shared channel/physical uplink control channel (PUSCH/PUCCH) and preamble strength for physical random access channel (PRACH). For uplink operation, the SINR is measured by the UL physical layer (PHY) for each UE. The SINR is also measured on PUCCH and PUSCH if a periodic channel quality indicator (CQI) report is replaced by an aperiodic report. Subcells' classification The role of a subcell may change when the measured SINR changes. Especially, the candidate subcell is expected to take the role of the serving subcell next. The decision about the role of a subcell is taken in each TTI. The decision is based on the SINR measurements for each UE and for all subcells. The SINR measurements are low-pass filtered and then compared with SINR thresholds. Hysteresis is in place to control the switching between subcell roles (measurement-only -> candidate, candidate -> serving, etc.). SINR measurements from SRS are not used for subcell selection. PRACH is received in all subcells. The subcell with best SINR on PRACH is selected as initial serving subcell. All other subcells are initially classified as measurement-only. Every subcell classification reflects differences in their behavior. •
•
•
Serving subcell The subcell receives: data on a PUSCH, the UE report with CSI + HARQ ACK/NACK feedback (channel quality information + hybrid automatic repeat request with acknowledgement/negative-acknowledgement) on PUCCH and PUSCH and the sounding reference signal (SRS). Received data is forwarded to the media access control (MAC) layer. The serving subcell sends TA commands to the UE, based on the TA measurements. Based on the serving cell measurement, a frequency offset (FO) is estimated and fixed. The serving cell drives a closed-loop UL power control and measures SINR. Candidate subcell The candidate subcell estimates the TA and FO. These values are prepared in case the candidate cell is switched over to become a serving subcell. Then, they are used as the initial values for the TA and FO. The SINR is measured. Measurement-only subcell The subcells that have not been selected as a serving subcell or candidate subcell. A measurement-only subcell measures SINR.
Receiver types Receiver type depends on UE's speed: •
70
The existing 2Rx maximum ratio combining (MRC) or 2Rx interference rejection combining (IRC) receivers are used in the serving subcell if normal speed is configured (prachHsFlag set to false).
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
Descriptions of radio resource management and telecom features
The existing 2Rx MRC HST receiver introduced with LTE48: Support of High Speed Users is used if high speed is configured (prachHsFlag set to true).
High-speed scenarios The high-speed receiver introduced in LTE48: Support of High Speed Users is used for combined supercells. The maximum speed of 360 km/h is supported at 2.1 GHz carrier frequency. The scenarios 1 and 3 (HST1, HST3) from 3GPP TS36.104, Annex B.3. are a reference scenario for testing. The scenarios define the minimum distance between the receiver and the railway track, along with the maximum speed, which maps into the maximum change rate of the Doppler shift.
g
Note: The HST1 scenario applies the maximum Doppler shift of 1340 Hz. The factor of 360 km/h with 2.1 GHz yields a maximum Doppler shift of 1400 Hz. Test scenarios might be extended to cover 1400 Hz, but the maximum Doppler change rate derived from HST1 cannot be exceeded. Supercell configurations supported with Flexi Multiradio 10 System Module The eNB supports combined supercell configurations according to the LTE2445: Combined Supercell feature on top of suitable eNB configurations for normal cells. This is the case when: • • • • • •
the eNB supports 3x5/10/15/20 MHz 2Tx2Rx with a basic cell set the eNB supports 6x5/10 MHz 2Tx2Rx, single band with a basic cell set the eNB supports 6x5/10 MHz 2Tx2Rx, dual band with a basic cell set the eNB supports 2x15/20 MHz plus 2x5/10MHz 2Tx2Rx, dual band with a basic cell set the eNB supports 6x15/20 MHz 2Tx2Rx, single band with an extended cell set up to 3-subcell supercells of 15/20-MHz bandwidth (BW) chained with two 3-subcell supercells of 5/10-MHz BW built by any valid dual- or triple-band three-sector BTS configuration
In the case of up to 3 normal cells per frequency band inside the same cell set, the eNB shall support one combined supercell comprising up to 3 sub-cells. In the case of up to 6 normal cells per frequency band inside the same cell set, the eNB shall support either one combined supercell comprising up to 6 sub-cells, or two combined supercells comprising 2 to 4 sub-cells, or three combined supercells comprising 2 sub-cells each. Supercell configurations supported with AirScale System Module The eNB supports combined supercell configurations according to the LTE2445: Combined Supercell feature on top of suitable eNB configurations for normal cells. This is the case when: • • • • •
the eNB supports 3x15/20 MHz 2Tx2Rx with a basic cell set r4 the eNB supports 4x5/10 MHz 2Tx2Rx, single band with a basic cell set r4 the eNB supports 2x5/10 MHz + 2x15/20 MHz 2Tx2Rx, dual band with a basic 2-cell set r4 the eNB supports 6x5/10/15/20 MHz 2Tx2Rx, single band with an extended 4-cell set r4 the eNB supports 6x5/10/15/20 MHz 2Tx2Rx, multiple bands with an extended 6-cell set r4
In the case of up to 3 normal cells per frequency band inside the same cell set, the eNB shall support one combined supercell comprising up to 3 sub-cells. In the case of 4 normal cells per frequency band inside the same cell set, the eNB shall support either
Issue: 01 Draft
DN09237915
71
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
one combined supercell comprising up to 4 sub-cells or two combined supercells comprising 2 sub-cells each. In the case of up to 6 normal cells per frequency band inside the same cell set, the eNB shall support either one combined supercell comprising up to 6 sub-cells, or two combined supercells comprising 2 to 4 sub-cells, or three combined supercells comprising 2 sub-cells each.
g
Note: It is not recommended to create more subcells per baseband board than could be supported by the same baseband resources if they were all normal cells. Speed of subcell classification In high-speed scenarios, there is a number of factors that influence the speed at which the classification of subcells has to be updated so that the serving subcell can follow the UE sufficiently: distance between antenna sites and railway track radiation pattern of the antennas, including strenght of the backlobe sites with antennas mounted back to back, pointing in different directions vs. antennas that point in one direction only expected maximum speed in a supercell
• • • •
Depending on an individual situation, it is recommended to configure the periodicity of the periodic CQI reports to a value no larger than 20 ms to allow faster switching to a new serving subcell, if required.
g
Note: For normal cells configured to high speed, and: • •
the hsScenario parameter set to Scenario 1, a periodicity of no more than 40 ms is recommended for a periodic CQI. the hsScenario parameter set to Scenario 3, a periodicity of no more than 20 ms is recommended for a periodic CQI.
Following the above recommendations for combined supercells reduces the CQI reporting period by half for cases that have so far been handled with the Scenario 1 configuration. Channel-aware and interference-aware uplink scheduling The available bandwidth for both channel-aware uplink scheduling and interferenceaware scheduling in a normal cell is subdivided into scheduling areas. When a UE is allocated, the interference situation per scheduling area is taken into account. In the case of a supercell, the interference is averaged across subcells. The averaged interference, which does not reflect the actual interference in the subcell where the UE is currently located, is considered when deciding on the preferred scheduling area. This leads to a decreased gain of interference-aware scheduler (IAS) and channel-aware scheduler (CAS) in scheduling. As for supercells, a SRS is measured only from the serving subcell of the UE. When the serving subcell changes, measurements taken before the change will be discarded. Support of location services The LTE2445: Combined Supercell feature supports location services, based on the LTE495: OTDOA feature. A UE's location is determined based on the positioning reference signal (PRS) and antenna's position. In the case of a supercell, there is no single reference transmission point for a signal propagation measurement. The LTE495:
72
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
OTDOA feature configured with the LTE2445: Combined Supercell feature ensures PRS transmission from all subcells. Hence, any location result provided by a supercell is inherently inaccurate.
3.8.3 LTE2445 system impact Interdependencies between features The following features can interwork with the LTE2445: Combined Supercell feature: • • • • •
g
Note: Any combination of normal cells and supercells might interoperate in DL CA. Supercells may take both PCell and SCell roles. •
g
LTE2233: N-out-of-M Downlink Carrier Aggregation Note: Can be supported with restrictions made for the LTE2445 feaure and DL CA (maximum 3CC, no inter-eNB CA).
• • •
g
LTE1541: Advanced SCell Measurement Handling LTE2006: Flexible SCell Selection LTE2276: Measurement-based SCell Selection Note: It is recommended to activate the LTE1541: Advanced SCell Measurement Handling, LTE2006: Flexible SCell Selection, LTE2276: Measurement-based SCell Selection features together with the LTE2445: Combined Supercell feature because it is likely that the cells involved in CA have different coverage.
•
g
LTE2275: PCell Swap Note: The shape of a supercell might have an impact on the UL SINR seen at different locations across the supercell area. As the UL SINR must exceed a lower limit for a PCell swap to be triggered, this might impact the probability of a PCell swap and its success. For example, in a supercell consisting of a macro + low-power RRHs to fill coverage gaps at the cell border, the boundary up to which PCell swaps are initiated might be shifted to the cell border. The target SCell of the swapping should still provide sufficient coverage for smooth operation.
• • • • • • • • • •
Issue: 01 Draft
LTE1089: Downlink Carrier Aggregation – 20 MHz LTE1332: Downlink Carrier Aggregation – 40 MHz LTE1562: Carrier Aggregation for Multicarrier eNBs LTE1803: Downlink Carrier Aggregation 3CC – 40 MHz LTE1804: Downlink Carrier Aggregation 3CC – 60 MHz
LTE1092: Uplink Carrier Aggregation LTE1367: Automatic Cell Combination Assignment for Carrier Aggregation LTE1951: Automatic Configuration Support for Multi-Carrier eNBs LTE468: PCI Management LTE1103: Load-based Power Saving for Multi-Layer Networks LTE783: ANR Inter-RAT UTRAN LTE784: ANR Inter-RAT GERAN LTE27: Open Loop UL Power Control and DL Power Setting LTE28: Closed Loop UL Power Control LTE1336: Interference-aware UL Power Control
DN09237915
73
Descriptions of radio resource management and telecom features
g
FDD-LTE16A, Feature Descriptions and Instructions
Note: The LTE1336: Interference-aware UL Power Control feature is: – –
• • • • •
g
supported when the subcells of the supercell have the same power levels not allowed when the subcells of the supercell have different power levels
LTE46: Channel-aware Scheduler LTE619: Interference-aware UL Scheduling LTE979: IRC for 2Rx Antennas LTE48: Support of High-speed Users LTE2080: LTE-WCDMA RF Sharing with Full FBBC Support Note: The interoperation with RF sharing features refers to FSMr3 only. RF sharing for FSMr4 is not in the scope of FL16A.
•
g
LTE2628: FHCG Repeater Interface Module 2-pipe Note: For appropriate system operation, the repeaters must have symmetric gains in UL and DL direction.
• • • • • • • • •
LTE2630: Uplink-control-information-only Transmission LTE2479: 256 QAM in DL LTE2612: ProSe Direct Communication for Public Safety LTE2661: FDD-LTE 16A FSMr3 Capacity and Dimensioning LTE2776: FDD-LTE 16A FSM4 Capacity and Dimensioning LTE2477: 3GPP Baseline R12 06/2015 LTE1117: MBMS LTE556: ANR Intra-LTE, Inter-Frequency, UE-based LTE782: ANR Fully UE-based
The LTE2445: Combined Supercell feature impacts the following features: •
LTE495: OTDOA
For more information, see Support of location services section. The following features are not supported in combination with the LTE2445: Combined Supercell feature: • • • • • • • • • •
g
74
LTE72: 4-way Rx Diversity LTE980: 4Rx IRC for 4Rx Path LTE1195: FHCC Flexi 850 Repeater Interface Unit LTE568: 4x2 MIMO or any Higher Order MIMO LTE1987: Downlink Adaptive Closed Loop SU MIMO (4x4) LTE2605: 4Rx Diversity 20MHz Optimized Configurations LTE1709: Liquid Cell LTE187: Single TX Path Mode LTE1203: Load-based Power Saving with Tx Path Switching Off LTE1542: FDD Supercell Note: The LTE2445 and the LTE1542 are mutually exclusive on a cell level, but might coexist in the same eNB. The features have different feature activation flags. The LTE1542 and LTE2091 have the same activation flag.
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
g
LTE2091: FDD Supercell Extension Note: The LTE2445 and the LTE2091 are mutually exclusive on a cell level, but might coexist in the same eNB. The features have different feature activation flags. The LTE1542 and LTE2091 have the same activation flag.
• • • • • • • • • • • • • • • • • •
g
Descriptions of radio resource management and telecom features
LTE1402: UL CoMP 2Rx LTE1691: UL CoMP 4Rx LTE1900: Centralized RAN LTE2470: Centralized RAN CL16 Release LTE2305: Inter eNodeB Carrier Aggregation for 2 Macro eNodeBs LTE2007: Inter eNode B Carrier Aggregation LTE2270: LTE TDD+FDD Inter eNB CA-basic BTS Configurations LTE2079: RF Sharing LTE-GSM LTE1113: eICIC - Macro LTE1496: eICIC – Micro LTE2133: eICIC for HetNet eNodeB Configurations LTE2149: Supplemental Downlink Carrier LTE2557: Supplemental Downlink Carrier Extensions LTE951: Enhanced Cell ID Location Service LTE914: Graceful Cell Shutdown LTE2531: FDD Downlink Carrier Aggregation 4CC/5CC LTE1914: RIP (Received Interference Power) Measurement Report Extension/Support RIP Initiated Alarms. LTE1130: Dynamic PUCCH Allocation Note: When the prachHsFlag parameter is set to true, the CQI period may have to be adjusted to speed up the subcell selection with combined supercells ( for more information, see the speed of subcell selection section. Slow subcell selection may lead to a degraded transmission performance. Therefore, it is not recommended to enable LTE1130 with supercells configured for high speed. The LTE2445 does not introduce any mechanisms to coordinate the LTE1130 and LTE2445 operation e.g. regarding the periodicity of the CQI reporting.
Impact on interfaces The LTE2445: Combined Supercell feature has no impact on interfaces. Impact on network management tools The LTE2445: Combined Supercell feature can be activated/deactivated from Netact or BTS Site Manager. Impact on system performance and capacity A supercell has the same capacity as one 2Tx/2Rx normal cell with the same bandwidth configuration. At the same time, a supercell with n subcells allocates the same hardware resources as n normal cells with the same characteristics. Hence, the capacity per deployed hardware decreases with an increasing number of subcells.
3.8.4 2445 reference data Requirements
Issue: 01 Draft
DN09237915
75
Descriptions of radio resource management and telecom features
Table 34
FDD-LTE16A, Feature Descriptions and Instructions
LTE2445 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
not supported
Flexi Zone Controller
OMS
not supported
LTE OMS16A
Flexi Multiradio 10 BTS
AirScale FDD
FL16A
FL16A
UE 3GPP R8 UE capabilities
Flexi Zone Micro BTS
Flexi Zone Access Point
not supported
not supported
MME
SAE GW
NetAct NetAct 16.8
support not required
support not required
Alarms Table 35
Existing alarms related to LTE2445
Alarm ID
Alarm name
7653
CELL FAULTY
7654
CELL OPERATION DEGRADED
For alarm descriptions, see LTE Radio Access Operating Documentation/ Reference/Alarms. Commands There are no commands related to the LTE2445: Combined Supercell feature. Measurements and counters There are no measurements or counters related to the LTE2445: Combined Supercell feature. Key performance indicators There are no key performance indicators related to the LTE2445: Combined Supercell feature. Parameters Table 36
New parameters introduced by LTE2445 Full name
Abbreviated name
Parent structure
Activate combined actCombSuperCell supercell configuration
LNCEL
–
Subcell Configuration
subCellConf
LNCEL
–
Subcell ID
subCellId
LNCEL
subCellConf
Subcell Maximum Transmission Power
pMaxSubCell
LNCEL
subCellConf
LNCEL
–
Supercell parameter set superCellParSet
76
Managed object
UL SINR hysteresis for subcell switch 1
subCellSwitchUlSi LNCEL nrHys1
superCellParSet
UL SINR hysteresis for subcell switch 2
subCellSwitchUlSi LNCEL nrHys2
superCellParSet
UL SINR offset to serving subcell for candidate subcell
candSubCellUlSinr LNCEL Offset
superCellParSet
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 36
Descriptions of radio resource management and telecom features
New parameters introduced by LTE2445 (Cont.) Full name
Abbreviated name
Managed object
UL SINR Hys for removing canidate subcell
remCandSubCellUlS LNCEL inrHys
superCellParSet
UL SINR Hys for replacing canidate subcell
repCandSubCellUlS LNCEL inrHys
superCellParSet
Subcell SINR filter constant 1
subcellSinrFiltCo LNCEL nst1
superCellParSet
Subcell SINR filter constant 2
subcellSinrFiltCo LNCEL nst2
superCellParSet
Table 37
Existing parameters related to LTE2445 Full name
Abbreviated name
Managed object
Parent structure
Activate uplink CoMP
actUlCoMp
LNBTS
–
Activate RIP alarming
actRIPAlarming
LNCEL
ripAlarmingConfig
Enable graceful cell shutdown
enableGrflShdn
LNBTS
–
Enhanced cell vendor specific tracing
enhCellVendorSpec MTRACE Tracing
RIP tracing
ripTracing
MTRACE
Activate liquid cell configuration
actLiquidCell
LNCEL
–
Activate supercell configuration
actSuperCell
LNCEL
–
Cell power reduction for MBMS transmission
cellPwrRedForMBMS LNCEL
–
Cell power reduce
dlCellPwrRed
LNCEL
–
Maximum output power
pMax
LNCEL
–
PRACH high speed flag
prachHsFlag
LNCEL
–
RIP alarming configuration
ripAlarmingConfig LNCEL
–
Method for UL power control
actUlpcMethod
LNCEL
–
Downlink MIMO mode
dlMimoMode
LNCEL
–
Activate enhanced actEicic inter-cell interference coordination
LNCEL
–
Sub cell identifier
LCELL
resourceList
subCellId
Activate load-based actLBRTXPowerSavi LNBTS reduced TX power saving ng
Issue: 01 Draft
Parent structure
DN09237915
–
enhCellVendorSpec Tracing
–
77
Descriptions of radio resource management and telecom features
Table 37
FDD-LTE16A, Feature Descriptions and Instructions
Existing parameters related to LTE2445 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
Activate Centralized RAN
actCRAN
LNBTS
–
Uplink CoMP Cell List
ulCoMpCellList
ULCOMP
–
For parameter descriptions, see LTE Radio Access Operating Documentation/ Reference/Parameters. Sales information Table 38
LTE2445 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
3.9 LTE2460: Automatic Access Class Barring with PLMN Disabling The LTE2460: Automatic Access Class Barring with PLMN Disabling feature reduces user equipment's (UE's) access to a cell. The reduction is done with an automatic removal of further public land mobile network (PLMN) IDs in a high control plane load situation. Additionally, it supports an automatic recovery of removed PLMN IDs when the cell is no longer overloaded. The removal and recovery of PLMN IDs is performed by an eNB.
3.9.1 LTE2460 benefits The LTE2460: Automatic Access Class Barring with PLMN Disabling feature provides the following benefits: • • •
automatic limitation of signalling during a high control plane load monitoring the time that passed when the PLMN IDs are removed planning the potential improvements for the network's capacity
3.9.2 LTE2460 functional description Removal of PLMN IDs The LTE2460: Automatic Access Class Barring with PLMN Disabling feature enhances the LTE1047: Control Plane Overload Handling feature with a possibility to disable the broadcast of further public land mobile network (PLMN) IDs from the SystemInformationBlockType 1 (SIB1). Consequently, if the PLMN ID is not broadcasted, the cell becomes invisible for the user equipment (UE). The automatic removal of a PLMN ID takes place if both of the following conditions are fulfilled: •
78
A control plane overload level 2 defined in the LTE1047: Control Plane Overload Handling feature is active.
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
g
Descriptions of radio resource management and telecom features
An eNB runs the access class barring operation in an overloaded cell according to the LTE1788: Automatic Access Class Barring feature. Note: Public safety user equipment (PS UE) is allowed to access the cell even if the LTE2460: Automatic Access Class Barring with PLMN Disabling feature is enabled.
Recovery of PLMN IDs The LTE2460: Automatic Access Class Barring with PLMN Disabling feature enables recovering the PLMN IDs broadcasted in the SIB1. The recovery is performed by the eNB, and it takes place in a situation when a cell is no longer overloaded. Monitoring the removal and recovery of PLMN IDs The LTE2460: Automatic Access Class Barring with PLMN Disabling feature enables monitoring the automatic removal of PLMN IDs. In order to make this function available, a new counter is introduced Time period of automatic Access Class Barring with PLMN disabling. The counter informs the operator about how long the subscribers were not able to select a removed further PLMN due to the automatic removal procedure. It is recommended to monitor also the quality of service for the neighbor cells in order to track the call and handover drop rates. High rates, in addition to the long PLMN ID disabling period, inform the operator about a potential need to improve the network's capacity.
3.9.3 LTE2460 system impact Interdependencies between features The following features must be activated before activating the LTE2460: Automatic Access Class Barring with PLMN Disabling feature: •
•
LTE1047: Control Plane Overload Handling The removal of public land mobile network (PLMN) IDs is possible only if the overload achieves a self-defense level (level 2) defined in the LTE1047: Control Plane Overload Handling feature. LTE1788: Automatic AC Barring The LTE1788: Automatic AC Barring feature applies the automatic access class barring in case there is a prolonged overload situation in a control plane. If the overload persists, the LTE2460: Automatic Access Class Barring with PLMN Disabling feature runs the autonomous removal of further PLMN IDs broadcasted in the SystemInformationBlockType 1 (SIB1).
Impact on interfaces The LTE2460: Automatic Access Class Barring with PLMN Disabling feature has no impact on interfaces. Impact on network management tools The LTE2460: Automatic Access Class Barring with PLMN Disabling feature has no impact on network management tools. Impact on system performance and capacity The LTE2460: Automatic Access Class Barring with PLMN Disabling feature has no impact on system performance or capacity.
3.9.4 LTE2460 reference data Requirements
Issue: 01 Draft
DN09237915
79
Descriptions of radio resource management and telecom features
Table 39
FDD-LTE16A, Feature Descriptions and Instructions
LTE2460 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
Not supported
UE
LTE OMS16A
Flexi Zone Micro BTS FL16A
NetAct
Flexi Zone Access Point FL16A
MME
3GPP R8-R12 NetAct 16.8
SAE GW
Flexi NS4.0
Support not required
Alarms There are no alarms related to the LTE2460: Automatic Access Class Barring with PLMN Disabling feature. BTS faults and reported alarms There are no faults related to the LTE2460: Automatic Access Class Barring with PLMN Disabling feature. Commands There are no commands related to the LTE2460: Automatic Access Class Barring with PLMN Disabling feature. Measurements and counters Table 40
New counters introduced by LTE2460
Counter ID
Counter name
Measurement LTE Cell Load
M8001C Time period of automatic 285 Access Class Barring with PLMN disabling
For counter descriptions, see LTE Radio Access Operating Documentation/Reference/Counters. Key performance indicators Table 41
New key performance indicators introduced by LTE2460
KPI ID
KPI name
LTE_6005a
Time period of further PLMN removal
LTE_6006a
Time ratio of further PLMN removal
A full list of KPIs including a change information will be available in the next delivery. Parameters Table 42
New parameters introduced by LTE2460 Full name
Abbreviated name
Managed object
Activate automatic PLMN actAutoPlmnRemova LNBTS removal l
80
DN09237915
Parent structure
-
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 42
Descriptions of radio resource management and telecom features
New parameters introduced by LTE2460 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
autoAcbPlmnRmvlSt SIB opTimer
-
Autonomous further PLMN autoPlmnRmvlStart SIB removal start timer Timer
-
Autonomous PLMN removal autoRemovalAllowe LNCEL allowed d
furtherPlmnIdL
Automatic AC barring and PLMN removal stop timer
Table 43
Existing parameters related to LTE2460 Full name
Abbreviated name
Activation of C-plane overload handling
Managed object
Parent structure
actCplaneOvlHandl LNBTS ing
-
LNBTS
-
Activation of Automatic actAutoAcBarring AC Barring
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 44
LTE2460 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
3.10 LTE2479: 256QAM in Downlink Benefits, functionality, system impact, and reference data of the feature. The LTE2479: 256QAM in Downlink feature introduces 256 quadrature amplitude modulation (QAM) for a dynamic data scheduling in the physical downlink shared channel (PDSCH).
3.10.1 LTE2479 benefits The LTE2479: 256QAM in Downlink feature provides the following benefits: • •
Increased spectral efficiency depending on the 256QAM area probability Higher downlink peak rates depending on the user equipment (UE) categories
3.10.2 LTE2479 functional description If the LTE2479: 256QAM in Downlink feature is enabled in the cell and the user equipment (UE) is 256QAM-capable, the evolved Node B (eNB) configures the UE and applies a dedicated table for the channel quality indicator (CQI) and the modulation and
Issue: 01 Draft
DN09237915
81
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
coding scheme (MCS) index in downlink (DL) link adaptation. The eNB indicates the applicability of the CQI table to the UE in the reconfiguration procedure in case of an initial context setup (ICS), handover (HO), re-establishment, or addition of a secondary cell (SCell). Reconfiguration to the 256QAM-specific CQI and MCS table requires a transient phase where all data scheduling are done based on the legacy table (conservative approach) and can impact the data rates. Hybrid automatic repeat request (HARQ) retransmissions use the same transport format and MCS in the initial transmission to maintain the same transport block size (TBS).
g
Note: In a bad channel quality, the coarser granularity of the 256QAM-specific MCS-toTBS mapping can reduce data rates and lower the transmission efficiency. The radio frequency (RF) power offset that depends on the hardware variant should be applied to meet the 3GPP error vector magnitude (EVM) requirements for DL 256QAM. Corresponding RF power offsets are configured via Cell power reduce (dlCellPwrRed) LNCEL parameter. For more information about the recommended power offset per radio unit, see Flexi Multiradio BTS RF Module and Remote Radio Head Description. In case of carrier aggregation (CA) scenarios, the applicability of 256QAM is decided on a per-component-carrier (CC) basis and depends on the feature activation and UE capabilities.
3.10.3 LTE2479 system impact LTE2479: 256QAM in Downlink impact on features, system performance and capacity. Interdependencies between features The LTE2479: 256QAM in Downlink feature can be enabled together with the LTE2531: FDD Downlink Carrier Aggregation 4CC feature to facilitate a downlink peak data rate of up to 780 Mbps. The LTE2479: 256QAM in Downlink feature impacts the following features: •
• •
LTE1117: LTE MBMS The 256QAM is not supported for the multimedia broadcast/multicast service (MBMS)-related signaling. LTE2275: PCell Swap The modulation and coding scheme (MCS)-related signaling are updated. LTE819: DL Inter-cell Interference Generation This feature is not included in the operation and maintenance (O&M) consistency check from the simultaneous operation with 256QAM.
Impact on interfaces The LTE2479: 256QAM in Downlink feature has no impact on interfaces. Impact on network management tools The LTE2479: 256QAM in Downlink feature has no impact on network management tools. Impact on system performance and capacity The LTE2479: 256QAM in Downlink feature impacts system performance and capacity as follows:
82
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• •
Descriptions of radio resource management and telecom features
Increased UE peak throughput Increased downlink peak data rates of up to 780 Mbps with 4CC carrier aggregation
3.10.4 LTE2479 reference data LTE2479: 256QAM in Downlink requirements, measurements and counters, parameters, and sales information. Requirements Table 45
LTE2479 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Not supported Support not required
Flexi Multiradio 10 BTS
Nokia AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
Not supported
Not supported
Not supported
NetAct
MME
SAE GW
UE
3GPP R12 UE NetAct 16.8 capabilities
Support not required
Support not required
Alarms There are no alarms related to the LTE2479: 256QAM in Downlink feature. Commands There are no commands related to the LTE2479: 256QAM in Downlink feature. Measurements and counters Table 46 Counter ID
Issue: 01 Draft
New counters introduced by LTE2479 Counter name
Measurement
M8010C116 UE Reported CQI Level 00 for 256QAM configured UEs
LTE Power and Quality DL
M8010C117 UE Reported CQI Level 01 for 256QAM configured UEs
LTE Power and Quality DL
M8010C118 UE Reported CQI Level 02 for 256QAM configured UEs
LTE Power and Quality DL
M8010C119 UE Reported CQI Level 03 for 256QAM configured UEs
LTE Power and Quality DL
M8010C120 UE Reported CQI Level 04 for 256QAM configured UEs
LTE Power and Quality DL
M8010C121 UE Reported CQI Level 05 for 256QAM configured UEs
LTE Power and Quality DL
M8010C122 UE Reported CQI Level 06 for 256QAM configured UEs
LTE Power and Quality DL
M8010C123 UE Reported CQI Level 07 for 256QAM configured UEs
LTE Power and Quality DL
M8010C124 UE Reported CQI Level 08 for 256QAM configured UEs
LTE Power and Quality DL
DN09237915
83
Descriptions of radio resource management and telecom features
Table 46 Counter ID
FDD-LTE16A, Feature Descriptions and Instructions
New counters introduced by LTE2479 (Cont.) Counter name
Measurement
M8010C125 UE Reported CQI Level 09 for 256QAM configured UEs
LTE Power and Quality DL
M8010C126 UE Reported CQI Level 10 for 256QAM configured UEs
LTE Power and Quality DL
M8010C127 UE Reported CQI Level 11 for 256QAM configured UEs
LTE Power and Quality DL
M8010C128 UE Reported CQI Level 12 for 256QAM configured UEs
LTE Power and Quality DL
M8010C129 UE Reported CQI Level 13 for 256QAM configured UEs
LTE Power and Quality DL
M8010C130 UE Reported CQI Level 14 for 256QAM configured UEs
LTE Power and Quality DL
M8010C131 UE Reported CQI Level 15 for 256QAM configured UEs
LTE Power and Quality DL
M8011C196 PDSCH transmission using QPSK of 256QAM configured UE
LTE Cell Resource
M8011C197 PDSCH transmission using 16QAM of 256QAM configured UE
LTE Cell Resource
M8011C198 PDSCH transmission using 64QAM of 256QAM configured UE
LTE Cell Resource
M8011C199 PDSCH transmission using 256QAM of LTE Cell Resource 256QAM configured UE M8011C200 PDSCH transmission nacks using QPSK of 256QAM configured UE
LTE Cell Resource
M8011C201 PDSCH transmission nacks using 16QAM of 256QAM configured UE
LTE Cell Resource
M8011C202 PDSCH transmission nacks using 64QAM of 256QAM configured UE
LTE Cell Resource
M8011C203 PDSCH transmission nacks using 256QAM of 256QAM configured UE
LTE Cell Resource
M8011C204 Failed PDSCH transmission using QPSK of 256QAM configured UE
LTE Cell Resource
M8011C205 Failed PDSCH transmission using 16QAM of 256QAM configured UE
LTE Cell Resource
M8011C206 Failed PDSCH transmission using 64QAM of 256QAM configured UE
LTE Cell Resource
M8011C207 Failed PDSCH transmission using 256QAM of 256QAM configured UE
LTE Cell Resource
M8012C175 MAC PDU volume PDSCH using QPSK of LTE Cell Throughput 256QAM configured UE
84
M8012C176 MAC PDU volume PDSCH using 16QAM of 256QAM configured UE
LTE Cell Throughput
M8012C177 MAC PDU volume PDSCH using 64QAM of 256QAM configured UE
LTE Cell Throughput
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 46
Descriptions of radio resource management and telecom features
New counters introduced by LTE2479 (Cont.)
Counter ID
Counter name
Measurement
M8012C178 MAC PDU volume PDSCH using 256QAM of 256QAM configured UE
LTE Cell Throughput
Key performance indicators There are no key performance indicators related to the LTE2479: 256QAM in Downlink feature. Parameters Table 47
New parameters introduced by LTE2479 Full name
Abbreviated name
Activate modulation scheme DL
Table 48
actModulationSchemeDl
Managed object LNCEL
Existing parameters related to LTE2479 Full name
Abbreviated name
Managed object
Initial MCS in downlink
iniMcsDl
LNCEL
PCell swap configuration
pcellSwapConfig
LNCEL
Threshold for a SCell detected - bad channel quality
scellBadChQualThr
LNCEL
Threshold for a SCell detected - good channel quality
scellGoodChQualThr
LNCEL
Threshold for a not detectable Scell
scellNotDetectableThr
LNCEL
CQI threshold for fallback to MIMO diversity
mimoOlCqiThD
LNCEL
CQI threshold for activation of OL MIMO SM
mimoOlCqiThU
LNCEL
CQI threshold for fallback to CL MIMO 1 CW mode
mimoClCqiThD
LNCEL
CQI threshold for activation of CL MIMO 2 CW mode
mimoClCqiThU
LNCEL
Sales information Table 49
LTE2479 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
3.11 LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I Benefits, functionality, system impact, and reference data of the feature.
Issue: 01 Draft
DN09237915
85
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
The LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I feature supports additional band combinations for downlink (DL) FDD-TDD carrier aggregation (CA).
3.11.1 LTE2511 benefits The LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I feature provides higher DL peak rates in areas with overlapping cell deployments for the supported FDD-TDD band combinations.
3.11.2 LTE2511 functional description The LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I feature allows the Flexi Multiradio 10 BTS to support the following band combinations for FDDTDD CA: •
FDD-TDD 2CC: – – – – – – – – – –
•
FDD-TDD 3CC: –
–
–
86
band 3 (FDD 15 MHz or 20 MHz, TM3 or TM4) + band 38 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4) band 3 (FDD 5 MHz, 10 MHz, 15 MHz, or 20 MHz; TM3 or TM4) + band 41 (TDD 20 MHz, frame configuration 1 or 2; TM3, TM4, or TM9) band 3 (FDD 5 MHz, 10 MHz, 15 MHz, or 20 MHz; TM3 or TM4) + band 42 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4) band 8 (FDD 5 MHz or 10 MHz, TM3 or TM4) + band 41 (TDD 20 MHz, frame configuration 1 or 2; TM3, TM4, or TM9) band 8 (FDD 5 MHz or 10 MHz, TM3 or TM4) + band 42 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4) * band 20 (FDD 5 MHz, 10 MHz, 15 MHz, or 20 MHz; TM3 or TM4) + band 38 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4) band 20 (FDD 10 MHz, 15 MHz, or 20 MHz; TM3 or TM4) + band 40 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4) band 28 (FDD 5 MHz, 10 MHz, 15 MHz, or 20 MHz; TM3 or TM4) + band 40 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4) band 28 (FDD 5 MHz or 10 MHz, TM3 or TM4) + band 41 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4) band 28 (FDD 5 MHz or 10 MHz, TM3 or TM4) + band 42 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4)
band 3 (FDD 5 MHz, 10 MHz, 15 MHz, or 20 MHz; TM3 or TM4) + band 42 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4) + band 42 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4) band 8 (FDD 5 MHz or 10 MHz, TM3 or TM4) + band 41 (TDD 20 MHz, frame configuration 1 or 2; TM3, TM4, or TM9) + band 41 (TDD 20 MHz, frame configuration 1 or 2; TM3, TM4, or TM9) band 8 (FDD 5 MHz or 10 MHz, TM3 or TM4) + band 42 (TDD 20 MHz, frame configuration 1 or 2; TM3, TM4, or TM9) + band 42 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4) *
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
–
–
g
Descriptions of radio resource management and telecom features
band 28 (FDD 5 MHz or 10 MHz, TM3 or TM4) + band 41 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4) + band 41 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4) band 28 (FDD 5 MHz or 10 MHz, TM3 or TM4) + band 42 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4) + band 42 (TDD 20 MHz, frame configuration 1 or 2, TM3 or TM4)
Note: The bandwidth combination set is 0 if not indicated as described in 3GPP TS 36.101. The combinations marked with an asterisk (*) are not covered in 3GPP TS 36.101.
3.11.3 LTE2511 system impact LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I impact on features. Interdependencies between features The LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I feature is enabled together with the following features: • •
LTE2180: FDD-TDD Downlink Carrier Aggregation 2CC LTE2316: FDD-TDD Downlink Carrier Aggregation 3CC
Impact on interfaces The LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I feature has no impact on interfaces. Impact on network management tools The LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I feature has no impact on network management tools. Impact on system performance and capacity The LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I feature has no impact on system performance or capacity.
3.11.4 LTE2511 reference data LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I requirements and sales information Requirements Table 50
Issue: 01 Draft
LTE2511 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Multiradio 10 BTS
Nokia AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
Not supported
Not supported
Not supported
DN09237915
87
Descriptions of radio resource management and telecom features
Table 50
FDD-LTE16A, Feature Descriptions and Instructions
LTE2511 hardware and software requirements (Cont.)
Flexi Zone Controller
OMS
UE
Not supported LTE OMS16A
•
•
3GPP R11 UE capabilities 3GPP R12 UE capabilities
NetAct NetAct 16.8
MME Support not required
SAE GW Support not required
Alarms There are no alarms related to the LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I feature. Commands There are no commands related to the LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I feature. Measurements and counters There are no measurements or counters related to the LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I feature. Key performance indicators There are no key performance indicators related to the LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I feature. Parameters There are no parameters related to the LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations - I feature. Sales information Table 51
LTE2511 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
3.12 LTE2527: Additional Carrier Aggregation Band Combinations – IV The LTE2527: Additional Carrier Aggregation Band Combinations – IV feature supports additional downlink (DL) carrier aggregation (CA) band combinations, expanding the functionality introduced by LTE2200: Additional Carrier Aggregation Band Combinations – III, LTE2168: Additional Carrier Aggregation Band Combinations – II, and LTE2033: Additional Carrier Aggregation Band Combinations – I features.
3.12.1 LTE2527 benefits The LTE2527: Additional Carrier Aggregation Band Combinations – IV feature provides the following benefits:
88
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• •
Descriptions of radio resource management and telecom features
when carrier aggregation (CA) is enabled, it supports more band combinations; this guarantees higher peak data rates for the users within the network the operator is offered additional downlink (DL) CA band combinations
3.12.2 LTE2527 functional description Functional overview In addition to the allowed CA band combinations from: • • • • •
LTE1089: Downlink Carrier Aggregation – 20 MHz LTE1332: Downlink Carrier Aggregation – 40 MHz LTE2033: Additional Carrier Aggregation Band Combinations – I LTE2168: Additional Carrier Aggregation Band Combinations – II LTE2200: Additional Carrier Aggregation Band Combinations – III
the LTE2527: Additional Carrier Aggregation Band Combinations – IV feature allows the Flexi Multiradio 10 BTS to support: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
Issue: 01 Draft
band 1 + band 11 band 1 + band 26 * band 2 + band 5 (bandwidth combination set 0, 1) band 2 + band 7 band 2 + band 12 (bandwidth combination set 2) band 2 + band 66 (bandwidth combination set 0, 1, 2) band 3 + band 3 (non-contiguous, bandwidth combination set 1) band 3 + band 5 (bandwidth combination set 3) band 3 + band 26 * band 3 + band 31 band 3 + band 32 band 4 + band 4 (non-contiguous, bandwidth combination set 1) band 4 + band 7 (bandwidth combination set 1) band 4 + band 12 (bandwidth combination set 5) band 5 + band 5 (non-contiguous) band 5 + band 5 (contiguous) band 5 + band 7 (bandwidth combination set 1) band 5 + band 13 band 5 + band 66 band 7 + band 7 (bandwidth combination set 2) band 7 + band 12 band 7 + band 32 band 8 + band 8 (contiguous) band 8 + band 11 band 8 + band 20 band 11 + band 18 band 11 + band 28 band 12 + band 66 (bandwidth combination set 0, 1, 2, 3, 4, 5) band 13 + band 66 band 20 + band 28 band 20 + band 31
DN09237915
89
Descriptions of radio resource management and telecom features
• • •
g
FDD-LTE16A, Feature Descriptions and Instructions
band 20 + band 32 (bandwidth combination set 0, 1) band 66 + band 66 (contiguous) band 66 + band 66 (non-contiguous) Note: The bandwidth combination set is 0 if not indicated otherwise. CA bandwidth combination sets are covered by 3GPP (TS 36.101 V13.0.0). For more details, see the LTE1089: Downlink Carrier Aggregation – 20 MHz and LTE1332: Downlink Carrier Aggregation – 40 MHz feature descriptions. * denotes band combinations required for fallback from a three-component carrier (3CC) aggregation (band 1 + band 3 + band 26) of LTE2528: Additional Carrier Aggregation Band Combinations 3CC – II feature.
3.12.3 LTE2527 system impact Interdependencies between features The LTE2527: Additional Carrier Aggregation Band Combinations – IV feature is enabled together with LTE1089: Downlink Carrier Aggregation – 20 MHz and LTE1332: Downlink Carrier Aggregation – 40 MHz features. Impact on interfaces The LTE2527: Additional Carrier Aggregation Band Combinations – IV feature has no impact on interfaces. Impact on network management tools The LTE2527: Additional Carrier Aggregation Band Combinations – IV feature has no impact on network management tools. Impact on system performance and capacity The LTE2527: Additional Carrier Aggregation Band Combinations – IV feature has no impact on system performance or capacity.
3.12.4 LTE2527 reference data Requirements Table 52
LTE2527: Additional Carrier Aggregation Band Combinations – IV hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Flexi Multiradio 10 BTS
AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
Not supported
Not supported
Not supported
NetAct
MME
SAE GW
Not supported
Not supported
UE
Not supported LTE OMS16A
3GPP R11 UE NetAct 16.8 capabilities, 3GPP R12 UE capabilities
Alarms There are no alarms related to the LTE2527: Additional Carrier Aggregation Band Combinations – IV feature. BTS faults and reported alarms
90
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
There are no faults related to the LTE2527: Additional Carrier Aggregation Band Combinations – IV feature. Commands There are no commands related to the LTE2527: Additional Carrier Aggregation Band Combinations – IV feature. Measurements and counters There are no measurements or counters related to the LTE2527: Additional Carrier Aggregation Band Combinations – IV feature. Key performance indicators There are no key performance indicators related to the LTE2527: Additional Carrier Aggregation Band Combinations – IV feature. Parameters There are no parameters related to the LTE2527: Additional Carrier Aggregation Band Combinations – IV feature. Sales information Table 53
LTE2527: Additional Carrier Aggregation Band Combinations – IV sales information
Product structure class Application software (ASW)
License control SW asset monitoring
Activated by default No
3.13 LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II Benefits, functionality, system impact, and reference data of the feature. The LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II feature supports additional band combinations for a three component carrier (3CC) downlink (DL) carrier aggregation (CA).
3.13.1 LTE2528 benefits The LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II feature provides higher DL peak rates in areas with overlapping cell deployments for the supported band combinations.
3.13.2 LTE2528 functional description The LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II feature allows Flexi Multiradio 10 BTS to support the following band combinations for 3CC DL CA: • • • • • •
Issue: 01 Draft
band 1 + band 3 + band 3 (band 3 contiguous) band 1 + band 3 + band 26 band 1 + band 7 + band 7 (band 7 contiguous) * band 1 + band 7 + band 8 band 1 + band 7 + band 20 band 1 + band 8 + band 11
DN09237915
91
Descriptions of radio resource management and telecom features
• • • • • • • • • • • • • • • • • • • • • • • • •
g
FDD-LTE16A, Feature Descriptions and Instructions
band 2 + band 2 + band 4 (band 2 non-contiguous) band 2 + band 2 + band 5 (band 2 contiguous) band 2 + band 2 + band 12 (band 2 contiguous) band 2 + band 2 + band 30 (band 2 contiguous) band 2 + band 4 + band 7 * band 2 + band 4 + band 30 band 2 + band 5 + band 12 band 2 + band 5 + band 13 band 2 + band 7 + band 12 * band 3 + band 3 + band 8 (band 3 non-contiguous) band 3 + band 3 + band 20 (band 3 contiguous, non-contiguous) * band 3 + band 3 + band 28 (band 3 contiguous) * band 3 + band 7 + band 7 (band 7 contiguous) band 3 + band 7 + band 32 * band 3 + band 20 + band 32 * band 4 + band 4 + band 29 (band 4 non-contiguous) * band 4 + band 4 + band 30 (band 4 non-contiguous) * band 4 + band 5 + band 13 band 4 + band 5 + band 29 band 4 + band 7 + band 12 (BCS 0) band 4 + band 7 + band 12 (BCS 1) band 5 + band 12 + band 12 (band 12 contiguous) band 7 + band 7 + band 28 (band 7 contiguous) band 7 + band 8 + band 20 band 7 + band 20 + band 32 * Note: The bandwidth combination set is 0 if not indicated as described in 3GPP TS 36.101. The combinations marked with an asterisk (*) are not covered in 3GPP TS 36.101.
3.13.3 LTE2528 system impact LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II impact on features. Interdependencies between features The LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II feature is enabled together with the following features: • •
LTE1803: Downlink Carrier Aggregation 3CC - 40 MHz LTE1804: Downlink Carrier Aggregation 3CC - 60 MHz
Impact on interfaces The LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II feature has no impact on interfaces. Impact on network management tools
92
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
The LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II feature has no impact on network management tools. Impact on system performance and capacity The LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II feature has no impact on system performance or capacity.
3.13.4 LTE2528 reference data LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II requirements and sales information. Requirements Table 54
LTE2528 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
Not supported
Not supported
Not supported
MME
SAE GW
UE
Not supported LTE OMS16A
•
•
3GPP R11 UE capabilities 3GPP R12 UE capabilities
NetAct NetAct 16.8
Support not required
Support not required
Alarms There are no alarms related to the LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II feature. Commands There are no commands related to the LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II feature. Measurements and counters There are no measurements or counters related to the LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II feature. Key performance indicators There are no key performance indicators related to the LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II feature. Parameters There are no parameters related to the LTE2528: Additional Carrier Aggregation Band Combinations 3CC - II feature. Sales information
Issue: 01 Draft
DN09237915
93
Descriptions of radio resource management and telecom features
Table 55
FDD-LTE16A, Feature Descriptions and Instructions
LTE2528 sales information
Product structure class Application software (ASW)
License control
Activated by default
SW Asset Monitoring
No
3.14 LTE2531: FDD Downlink Carrier Aggregation 4CC The LTE2531: FDD Downlink Carrier Aggregation 4CC feature enables aggregating air interface resources of up to four overlapping cells in order to reach high downlink peak rates for an individual user. The maximum bandwidth aggregated with the feature is 80 MHz.
3.14.1 LTE2531 benefits The LTE2531: FDD Downlink Carrier Aggregation 4CC feature provides the benefit of downlink peak rates of up to 780 Mbps enabled in combination with the LTE2479: 256 QAM in Downlink feature. Without 256 QAM, the maximum possible downlink peak rates are up to 600 Mbps in ideal conditions (downlink peak rates are determined by UE capabilities, radio conditions, other traffic, and HW capabilities).
3.14.2 LTE2531 functional description Feature overview Figure 7
Downlink carrier aggregation for four component carriers
Component Carrier4
Component Carrier 3 CarrierAggregation
UE Component Carrier 2
Component Carrier 1
94
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
The LTE2531: FDD Downlink Carrier Aggregation 4CC feature enables eNB to support carrier aggregation in downlink for up to four component carriers (CCs). The feature is a continuation of the LTE1804: Downlink Carrier Aggregation 3CC – 60 MHz and LTE2233: N-out-of-M Downlink Carrier Aggregation features with the following functionality improvements and enhancements: • • • •
Third SCell configuration/deconfiguration (4CC) Extension of SCell selection, based on normalized load compare value (NLCV) to three SCells out of up to six frequency layers Stepwise activation of the third SCell Extension of UE-throughput-based division algorithms to 4CC for: – – – –
• • • •
Buffer division Peak data rate division Aggregate maximum bit rate (AMBR) division Nominal bit rate (NBR) division
Aperiodic channel state information (CSI) triggering for 4CC Periodic CSI handling for 4CC by static PUCCH configuration only A 15-bit long, extended packet data convergence protocol sequence number (PDCPSN) is supported (applicable to all 3GPP R11 UEs and higher) RLC parameter modifications to handle increased peak data rates and to handle an increased number of transmission buffers
The maximum aggregated downlink bandwidth is up to 80 MHz. 4CC 80 MHz CA in combination with 256 QAM allows achieving downlink peak rates of up to 780 Mbps in ideal conditions. Without 256 QAM, maximum possible downlink peak rates for 4CC 80 MHz CA are up to 600 Mbps and for 4CC 60 MHz CA are up to 450 Mbps. Downlink peak rates are determined by UE capabilities, radio conditions, other traffic, and hardware capabilities. The supported band combinations, with the bandwidth combination set 0 for the deployment scenario 1 and 2 as described by 3GPP TS 36.300, are: • • • • • • • • • • •
Issue: 01 Draft
Band 3 + Band 7 + Band 20 + Band 32; maximum aggregated bandwidth: 80 MHz Band 2 + Band 2 + Band 12 + Band 30; Band 2 contiguous; maximum aggregated bandwidth: 60 MHz Band 2 + Band 2 + Band 5 + Band 30; Band 2 contiguous; maximum aggregated bandwidth: 60 MHz Band 2 + Band 2 + Band 29 + Band 30; Band 2 contiguous; maximum aggregated bandwidth: 60 MHz Band 2 + Band 4 + Band 12 + Band 30; maximum aggregated bandwidth: 60 MHz Band 2 + Band 4 + Band 5 + Band 30; maximum aggregated bandwidth: 60 MHz Band 2 + Band 4 + Band 5 + Band 29; maximum aggregated bandwidth: 60 MHz Band 2 + Band 4 + Band 29 + Band 30; maximum aggregated bandwidth: 60 MHz Band 4 + Band 4 + Band 5 + Band 30; Band 4 non-contiguous; maximum aggregated bandwidth: 60 MHz Band 4 + Band 4 + Band 12 + Band 30; Band 4 non-contiguous; maximum aggregated bandwidth: 60 MHz Band 4 + Band 4 + Band 29 + Band 30; Band 4 non-contiguous; maximum aggregated bandwidth: 60 MHz
DN09237915
95
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
On Flexi Multiradio 10 System Module, the following bandwidth combinations are supported (for three-sector per eNB per eNB cluster deployment): •
The supported bandwidth combinations for 4CC for a 2RX/2TX configuration per component carrier are any combinations up to: – –
•
The supported bandwidth combinations for 4CC with a 4RX/4TX configuration (maximum two layers per CC) on one or two component carriers with the highest cell bandwidths are any combinations up to: – –
g
5/10 + 5/10 + 15/20 + 15/20 MHz in the intra-eNB scenario 15/20 + 15/20 + 15/20 + 15/20 MHz in the inter-eNB scenario
5/10 + 5/10 + 5/10 + 5/10 MHz in the intra-eNB scenario 15/20 + 15/20 + 15/20 + 15/20 MHz in the inter-eNB scenario Note: 4RX/4TX + 4RX/4TX + 4RX/4TX + 4RX/4TX can be supported even for 20 MHz + 20 MHz + 20 MHz + 20 MHz 4CC CA with a limited number of cells per eNB.
A mix of non-carrier aggregation UEs and carrier aggregation UEs with up to four aggregated CCs is supported in downlink on each cell. Downlink carrier aggregation is only applied to UEs with the related UE capabilities. The feature serves guaranteed bit rate data radio bearers (GBR DRBs) only on the PCell. SCell handling • • • •
Each SCell is configured/deconfigured individually. Each SCell is activated/de-activated individually. DL AMBR and DL NBR enforcements on 4CC are introduced. Barred cells are handled according to the rules of LTE2557: SCell Configuration of Barred Cells and LTE2149: Supplemental Downlink Carrier.
Scheduling UEs with activated SCells are scheduled by separate and coordinated downlink schedulers. Handling the discontinuous reception (DRX) as well as measurement gap is synchronized between the four downlink schedulers. The aperiodic channel quality indicator (CQI) report is extended to report four CCs. Physical uplink control channel (PUCCH) PUCCH format 3 is used for downlink carrier aggregation with four CCs. Mobility The mobility for CA-configured UEs is based on PCell measurements. The same measurement configurations as for non-CA-configured UEs are applied, for example A3 and/or A5. The feature does not support cross-CC scheduling (PDCCH and the corresponding PDSCH cannot be on different cells).
96
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
g
Descriptions of radio resource management and telecom features
Note: The feature may not offer UE's peak data rate gains or average UE's throughput gains in certain load conditions if the Sched Carrier Aggr fairness control factor (caSchedFairFact) LNBTS parameter is set to 1; nevertheless, it will still offer fast load balancing benefits.
g
Note: In uplink, carrier aggregation is supported with the dedicated feature LTE1092: Uplink Carrier Aggregation – 2CC. Inter-eNB carrier aggregation is supported with the dedicated feature LTE2007: Inter-eNodeB Carrier Aggregation, and one SRIO link is enough for inter-eNB connections.
3.14.3 LTE2531 system impact Interdependencies between features The following features must be activated before activating the LTE2531: FDD Downlink Carrier Aggregation 4CC feature or will be activated during the activation of LTE2531: FDD Downlink Carrier Aggregation 4CC 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 LTE2006: Flexible SCell Selection LTE2630: Uplink Control Information Only Transmission
If inter-eNB CA is used, the following features must be activated before activating the LTE2531: FDD Downlink Carrier Aggregation 4CC feature: • •
LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs LTE2007: Inter-eNodeB Carrier Aggregation
If band 29 is used, the following feature must be activated before activating the LTE2531: FDD Downlink Carrier Aggregation 4CC feature: •
LTE2149: Supplemental Downlink Carrier
If 256 QAM in downlink is used, the following feature must be activated before activating the LTE2531: FDD Downlink Carrier Aggregation 4CC feature: •
LTE2479: 256 QAM in Downlink
The following features must be deactivated before activating the LTE2531: FDD Downlink Carrier Aggregation 4CC feature: • • • • • • •
Issue: 01 Draft
LTE117: Cell Bandwidth 1.4 MHz LTE116: Cell Bandwidth 3 MHz LTE1130: Dynamic PUCCH Allocation LTE1496: eICIC – Micro LTE1382: Cell Resource Groups LTE1691: Uplink Intra-eNB CoMP 4Rx in Intra-eNB 4CC/5CC CA Scenarios LTE1542: FDD Supercell
DN09237915
97
Descriptions of radio resource management and telecom features
• •
FDD-LTE16A, Feature Descriptions and Instructions
LTE2091: FDD Supercell Extension LTE2445: Combined Supercell
The LTE2531: FDD Downlink Carrier Aggregation 4CC feature impacts the following features: • •
• • • • •
LTE1042: Nominal Bitrate for Non-GBR Bearers LTE1092: Uplink Carrier Aggregation – 2CC LTE1092 and LTE2531 can be enabled on the same eNB; however, that eNB will not support 2CC UL CA on the same UE when 4CC CA is active. LTE1638: Inter-frequency RSTD Measurement Support CQI reporting of SCells can be reconfigured for more than two SCells. LTE2133: eICIC for HetNet eNodeB Configurations LTE2275: PCell Swap 4CC-configured UEs are excluded from the PCell swap procedure. LTE2276: Measurement-based SCell Selection LTE2479: 256 QAM in Downlink
The LTE2531: FDD Downlink Carrier Aggregation 4CC feature is impacted by the following features: •
LTE1103: Load-based Power Saving for Multi-layer Networks In the case of multi-eNB CA, LTE1103 can power up/shut down cells if the current load requires it.
Impact on interfaces The LTE2531: FDD Downlink Carrier Aggregation 4CC feature has no impact on interfaces. Impact on network management tools The LTE2531: FDD Downlink Carrier Aggregation 4CC feature has no impact on network management tools. Impact on system performance and capacity The LTE2531: FDD Downlink Carrier Aggregation 4CC feature impacts system performance and capacity by increasing a single UE's DL throughput peak rates up to 780 Mbps for 4CC with 80 MHz with 256 QAM (or, alternatively, up to 600 Mbps without 256 QAM).
3.14.4 LTE2531 reference data Requirements Table 56
LTE2531 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
Not supported
Not supported
Not supported
NetAct
MME
SAE GW
UE
Not supported LTE OMS16A
98
Flexi Multiradio 10 BTS
3GPP R12 UE NetAct 16.8 capabilities,
DN09237915
Support not required
Support not required
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 56
Descriptions of radio resource management and telecom features
LTE2531 hardware and software requirements (Cont.)
Flexi Zone Controller
OMS
UE
NetAct
MME
SAE GW
3GPP R13 UE capabilities
Additional requirements LTE2531 BTS Site Solutions/HW deployment requires any feature that provides more than three frequency layers. Alarms There are no alarms related to the LTE2531: FDD Downlink Carrier Aggregation 4CC feature. BTS faults and reported alarms There are no faults related to the LTE2531: FDD Downlink Carrier Aggregation 4CC feature. Commands There are no commands related to the LTE2531: FDD Downlink Carrier Aggregation 4CC feature. Measurements and counters Table 57
New counters introduced by LTE2531
Counter ID
Counter name
Measurement
M8051C Average number of DL carrier 17 aggregated capable UEs for 4 CCs
LTE UE Quantity
M8051C Average number of UEs with 19 three configured SCells
LTE UE Quantity
M8051C Average number of UEs with 21 three activated SCells
LTE UE Quantity
For counter descriptions, see LTE Performance Measurements. Key performance indicators There are no key performance indicators related to the LTE2531: FDD Downlink Carrier Aggregation 4CC feature. Parameters Table 58
New parameters introduced by LTE2531 Full name
Managed object
Parent structure
Profile 7 of RLC parameters
rlcProf7
LNBTS
-
PollPDU
pollPdu
LNBTS
Profile 7 of RLC parameters (RrlcProf7)
rlcProfileId
LNBTS
Profile 7 of RLC parameters (RrlcProf7)
RLC Profile Id
Issue: 01 Draft
Abbreviated name
DN09237915
99
Descriptions of radio resource management and telecom features
Table 58
FDD-LTE16A, Feature Descriptions and Instructions
New parameters introduced by LTE2531 (Cont.) Full name
Abbreviated name
Parent structure
Timer poll retransmit
tPollRetr
LNBTS
Profile 7 of RLC parameters (RrlcProf7)
Timer status prohibit
tProhib
LNBTS
Profile 7 of RLC parameters (RrlcProf7)
Timer reordering
tReord
LNBTS
Profile 7 of RLC parameters (RrlcProf7)
Table 59
Existing parameters related to LTE2531 Full name
100
Managed object
Abbreviated name
Managed object
Parent structure
Profile 1 of PDCP parameters
pdcpProf1
LNBTS
-
PDCP profile ID
pdcpProfileId
LNBTS
Profile 1 of PDCP parameters (pdcpProf1)
Sequence number size
snSize
LNBTS
Profile 1 of PDCP parameters (pdcpProf1)
Status report required
statusRepReq
LNBTS
Profile 1 of PDCP parameters (pdcpProf1)
Timer discard
tDiscard
LNBTS
Profile 1 of PDCP parameters (pdcpProf1)
Profile 2 of PDCP parameters
pdcpProf2
LNBTS
-
PDCP profile ID
pdcpProfileId
LNBTS
Profile 2 of PDCP parameters (pdcpProf2)
Sequence number size
snSize
LNBTS
Profile 2 of PDCP parameters (pdcpProf2)
Status report required
statusRepReq
LNBTS
Profile 2 of PDCP parameters (pdcpProf2)
Timer discard
tDiscard
LNBTS
Profile 2 of PDCP parameters (pdcpProf2)
Profile 3 of PDCP parameters
pdcpProf3
LNBTS
-
PDCP profile ID
pdcpProfileId
LNBTS
Profile 3 of PDCP parameters (pdcpProf3)
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 59
Existing parameters related to LTE2531 (Cont.) Full name
Issue: 01 Draft
Descriptions of radio resource management and telecom features
Abbreviated name
Managed object
Parent structure
Sequence number size
snSize
LNBTS
Profile 3 of PDCP parameters (pdcpProf3)
Status report required
statusRepReq
LNBTS
Profile 3 of PDCP parameters (pdcpProf3)
Timer discard
tDiscard
LNBTS
Profile 3 of PDCP parameters (pdcpProf3)
Profile 4 of PDCP parameters
pdcpProf4
LNBTS
-
PDCP profile ID
pdcpProfileId
LNBTS
Profile 4 of PDCP parameters (pdcpProf4)
Sequence number size
snSize
LNBTS
Profile 4 of PDCP parameters (pdcpProf4)
Status report required
statusRepReq
LNBTS
Profile 4 of PDCP parameters (pdcpProf4)
Timer discard
tDiscard
LNBTS
Profile 4 of PDCP parameters (pdcpProf4)
Profile 5 of PDCP parameters
pdcpProf5
LNBTS
-
PDCP profile ID
pdcpProfileId
LNBTS
Profile 5 of PDCP parameters (pdcpProf5)
Sequence number size
snSize
LNBTS
Profile 5 of PDCP parameters (pdcpProf5)
Status report required
statusRepReq
LNBTS
Profile 5 of PDCP parameters (pdcpProf5)
Timer discard
tDiscard
LNBTS
Profile 5 of PDCP parameters (pdcpProf5)
QCI translation table QCI 6
qciTab6
LNBTS
-
DRX profile index
drxProfileIndex
LNBTS
QCI translation table QCI 6 (qciTab6)
DSCP
dscp
LNBTS
QCI translation table QCI 6 (qciTab6)
Enforce TTI bundling
enforceTtiBundlin LNBTS g
QCI translation table QCI 6 (qciTab6)
DN09237915
101
Descriptions of radio resource management and telecom features
Table 59
FDD-LTE16A, Feature Descriptions and Instructions
Existing parameters related to LTE2531 (Cont.) Full name
102
Abbreviated name
Managed object
Parent structure
Logical channel group identifier
lcgid
LNBTS
QCI translation table QCI 6 (qciTab6)
Nominal bit rate downlink
nbrDl
LNBTS
QCI translation table QCI 6 (qciTab6)
Nominal bit rate uplink nbrUl
LNBTS
QCI translation table QCI 6 (qciTab6)
PDCP profile index
pdcpProfIdx
LNBTS
QCI translation table QCI 6 (qciTab6)
Priority
prio
LNBTS
QCI translation table QCI 6 (qciTab6)
QCI
qci
LNBTS
QCI translation table QCI 6 (qciTab6)
QCI support
qciSupp
LNBTS
QCI translation table QCI 6 (qciTab6)
Resource type
resType
LNBTS
QCI translation table QCI 6 (qciTab6)
RLC mode
rlcMode
LNBTS
QCI translation table QCI 6 (qciTab6)
RLC profile index
rlcProfIdx
LNBTS
QCI translation table QCI 6 (qciTab6)
RLC profile index for 3 rlcProfIdx3cc CC CA
LNBTS
QCI translation table QCI 6 (qciTab6)
RLC profile index for 4 rlcProfIdx4cc5cc CC and 5CC CA
LNBTS
QCI translation table QCI 6 (qciTab6)
Scheduling bucket size duration
schedulBSD
LNBTS
QCI translation table QCI 6 (qciTab6)
Scheduling priority
schedulPrio
LNBTS
QCI translation table QCI 6 (qciTab6)
Scheduling weight
schedulWeight
LNBTS
QCI translation table QCI 6 (qciTab6)
QCI translation table QCI 7
qciTab7
LNBTS
-
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 59
Existing parameters related to LTE2531 (Cont.) Full name
Issue: 01 Draft
Descriptions of radio resource management and telecom features
Abbreviated name
Managed object
Parent structure
DRX profile index
drxProfileIndex
LNBTS
QCI translation table QCI 7 (qciTab7)
DSCP
dscp
LNBTS
QCI translation table QCI 7 (qciTab7)
Enforce TTI bundling
enforceTtiBundlin LNBTS g
QCI translation table QCI 7 (qciTab7)
Logical channel group identifier
lcgid
LNBTS
QCI translation table QCI 7 (qciTab7)
Nominal bit rate downlink
nbrDl
LNBTS
QCI translation table QCI 7 (qciTab7)
Nominal bit rate uplink nbrUl
LNBTS
QCI translation table QCI 7 (qciTab7)
PDCP profile index
pdcpProfIdx
LNBTS
QCI translation table QCI 7 (qciTab7)
Priority
prio
LNBTS
QCI translation table QCI 7 (qciTab7)
QCI
qci
LNBTS
QCI translation table QCI 7 (qciTab7)
QCI support
qciSupp
LNBTS
QCI translation table QCI 7 (qciTab7)
Resource type
resType
LNBTS
QCI translation table QCI 7 (qciTab7)
RLC mode
rlcMode
LNBTS
QCI translation table QCI 7 (qciTab7)
RLC profile index
rlcProfIdx
LNBTS
QCI translation table QCI 7 (qciTab7)
RLC profile index for 3 rlcProfIdx3cc CC CA
LNBTS
QCI translation table QCI 7 (qciTab7)
RLC profile index for 4 rlcProfIdx4cc5cc CC and 5CC CA
LNBTS
QCI translation table QCI 7 (qciTab7)
Scheduling bucket size duration
LNBTS
QCI translation table QCI 7 (qciTab7)
schedulBSD
DN09237915
103
Descriptions of radio resource management and telecom features
Table 59
FDD-LTE16A, Feature Descriptions and Instructions
Existing parameters related to LTE2531 (Cont.) Full name
104
Abbreviated name
Managed object
Parent structure
Scheduling priority
schedulPrio
LNBTS
QCI translation table QCI 7 (qciTab7)
Scheduling weight
schedulWeight
LNBTS
QCI translation table QCI 7 (qciTab7)
QCI translation table QCI 8
qciTab8
LNBTS
-
DRX profile index
drxProfileIndex
LNBTS
QCI translation table QCI 8 (qciTab8)
DSCP
dscp
LNBTS
QCI translation table QCI 8 (qciTab8)
Enforce TTI bundling
enforceTtiBundlin LNBTS g
QCI translation table QCI 8 (qciTab8)
Logical channel group identifier
lcgid
LNBTS
QCI translation table QCI 8 (qciTab8)
Nominal bit rate downlink
nbrDl
LNBTS
QCI translation table QCI 8 (qciTab8)
Nominal bit rate uplink nbrUl
LNBTS
QCI translation table QCI 8 (qciTab8)
PDCP profile index
pdcpProfIdx
LNBTS
QCI translation table QCI 8 (qciTab8)
Priority
prio
LNBTS
QCI translation table QCI 8 (qciTab8)
QCI
qci
LNBTS
QCI translation table QCI 8 (qciTab8)
QCI support
qciSupp
LNBTS
QCI translation table QCI 8 (qciTab8)
Resource type
resType
LNBTS
QCI translation table QCI 8 (qciTab8)
RLC mode
rlcMode
LNBTS
QCI translation table QCI 8 (qciTab8)
RLC profile index
rlcProfIdx
LNBTS
QCI translation table QCI 8 (qciTab8)
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 59
Existing parameters related to LTE2531 (Cont.) Full name
Issue: 01 Draft
Descriptions of radio resource management and telecom features
Abbreviated name
Managed object
Parent structure
RLC profile index for 3 rlcProfIdx3cc CC CA
LNBTS
QCI translation table QCI 8 (qciTab8)
RLC profile index for 4 rlcProfIdx4cc5cc CC and 5CC CA
LNBTS
QCI translation table QCI 8 (qciTab8)
Scheduling bucket size duration
schedulBSD
LNBTS
QCI translation table QCI 8 (qciTab8)
Scheduling priority
schedulPrio
LNBTS
QCI translation table QCI 8 (qciTab8)
Scheduling weight
schedulWeight
LNBTS
QCI translation table QCI 8 (qciTab8)
QCI translation table QCI 9
qciTab9
LNBTS
-
DRX profile index
drxProfileIndex
LNBTS
QCI translation table QCI 9 (qciTab9)
DSCP
dscp
LNBTS
QCI translation table QCI 9 (qciTab9)
Enforce TTI bundling
enforceTtiBundlin LNBTS g
QCI translation table QCI 9 (qciTab9)
Logical channel group identifier
lcgid
LNBTS
QCI translation table QCI 9 (qciTab9)
Nominal bit rate downlink
nbrDl
LNBTS
QCI translation table QCI 9 (qciTab9)
Nominal bit rate uplink nbrUl
LNBTS
QCI translation table QCI 9 (qciTab9)
PDCP profile index
pdcpProfIdx
LNBTS
QCI translation table QCI 9 (qciTab9)
Priority
prio
LNBTS
QCI translation table QCI 9 (qciTab9)
QCI
qci
LNBTS
QCI translation table QCI 9 (qciTab9)
QCI support
qciSupp
LNBTS
QCI translation table QCI 9 (qciTab9)
DN09237915
105
Descriptions of radio resource management and telecom features
Table 59
FDD-LTE16A, Feature Descriptions and Instructions
Existing parameters related to LTE2531 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
Resource type
resType
LNBTS
QCI translation table QCI 9 (qciTab9)
RLC mode
rlcMode
LNBTS
QCI translation table QCI 9 (qciTab9)
RLC profile index
rlcProfIdx
LNBTS
QCI translation table QCI 9 (qciTab9)
RLC profile index for 3 rlcProfIdx3cc CC CA
LNBTS
QCI translation table QCI 9 (qciTab9)
RLC profile index for 4 rlcProfIdx4cc5cc CC and 5CC CA
LNBTS
QCI translation table QCI 9 (qciTab9)
Scheduling bucket size duration
schedulBSD
LNBTS
QCI translation table QCI 9 (qciTab9)
Scheduling priority
schedulPrio
LNBTS
QCI translation table QCI 9 (qciTab9)
Scheduling weight
schedulWeight
LNBTS
QCI translation table QCI 9 (qciTab9)
QCI translation table operator specific QCIs
qciTabOperator
LNBTS
-
LNCEL
-
Activation of automatic actAutoPucchAlloc LNCEL PUCCH allocation
-
Activate enhanced actEicic inter-cell interference coordination
LNCEL
-
Activate UCI only grant actUciOnlyGrants transmission
LNCEL
-
Cell type
LNCEL
-
Max number of secondary maxNumScells cells for DL carrier aggr
cellType
For parameter descriptions, see Flexi Multiradio BTS LTE Commissioning, RNW and Transmission Parameters. Sales information Table 60
LTE2531 sales information
Product structure class Application software (ASW)
106
License control SW Asset Monitoring
DN09237915
Activated by default No
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
3.15 LTE2551: RSRQ-based A5 The LTE2551: RSRQ-based A5 feature introduces an additional quality-related trigger to start the A5 inter-frequency and intra-RAT measurement. In addition, it provides a combined RSRP and RSRQ measurement check for inter-frequency handovers.
3.15.1 LTE2551 benefits The LTE2551: RSRQ based A5 feature provides the following benefits: • •
It is possible to measure the signal strength and the signal quality of neighbor cells in the A5 event; it allows reducing potential inter-frequency ping-pong handovers. The load is better deployed throughout the network, so the end user gets better quality of calls; the call failure rate is reduced.
3.15.2 LTE2551 functional description Handover in mobile networks In order to secure service continuity and quality as a UE moves, UEs not only have to be connected to a serving cell but also need to be able to change a connection to one of the neighbor cells. If the current connection is poor (due to signal level or quality), the UE has to search for better service. The signal strength of neighboring cells is measured periodically, and a handover occurs when specific conditions are fulfilled. During the handover procedure, running services are maintained; a call is not interrupted, and for an intra-LTE handover no data is lost. Handovers in LTE are network controlled and UE assisted. The goal of the handover procedure is to allocate the same resources for the UE in the target cell after the handover as those used prior to the handover. From the UE's point of view, a handover is always “hard,” meaning that a connection exists to only one cell at a time. Handovers result from such factors as: •
•
Quality: Handovers due to quality are typically initiated as a result of a UE measurement report indicating that the UE can communicate with a neighbor cell with a better channel quality than that of the current serving cell. Coverage: Handovers due to coverage are also initiated as a result of a UE measurement report indicating that the serving cell becomes worse than an absolute threshold.
Measurement and measurement reports The UE assists the eNB regarding a handover by sending measurement reports. When verifying radio conditions due to UE mobility (for example when the UE moves from one LTE cell to another or because of limited LTE coverage), measurement reports may initiate a handover. The type of measurements to be made by the UE, and the details of reporting them to the eNB, can be configured (measurement configuration and report configuration), and the eNB informs the UE about the configurations via the RRC: CONNECTION RECONFIGURATION message.
Issue: 01 Draft
DN09237915
107
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
The LTE reference signal received power (RSRP) measurement ensures a cell-specific signal strength metric. On the other hand, the LTE reference signal received quality (RSRQ) measurement provides a cell-specific signal quality metric. LTE handover events Before a handover is performed, a UE sends measurement reports to the network, and it is the network which decides whether a handover takes place or not. 3GPP defines a few types of such events within measurement reports. In order to limit the amount of signaling, the UE only sends measurement reports (RRC: MEASUREMENT REPORT messages) to the eNB when certain conditions (events) are met by the UEs' measurements. The following events are defined in the LTE standard: • • • • • • • •
Event A1: The serving cell becomes better than an absolute threshold. Event A2: The serving cell becomes worse than an absolute threshold. Event A3: An LTE neighbor cell becomes better than an offset relative to the serving cell. Event A4: An LTE neighbor cell becomes better than an absolute threshold. Event A5: The serving cell becomes worse than an absolute threshold, and an LTE neighbor cell becomes better than another absolute threshold. Event A6: Neighbour becomes offset better than secondary cell (SCell) Event B1: A non-LTE neighbor cell becomes better than an absolute threshold. Event B2: The serving cell becomes worse than an absolute threshold, and a nonLTE neighbor cell becomes better than another absolute threshold.
The events from A1 to A6 are related to intra-LTE handovers; B1 and B2 events are related to inter-RAT handovers. A1 is useful for restricting UE measurements to the serving cell only; A3 is connected with a better cell handover and A5 with a coverage handover. The events correspond with the type of measurements the UE performs. The measurement reports contain a list of target cells for a handover. The target cells are listed in order of decreasing value of the reporting quantity, that is, the best cell is reported first. As a consequence of the definition of the events, the target cell list cannot be empty. Handover conditions due to A5 get a higher priority than handovers due to A3.
3.15.2.1
LTE2551 overview There are two functionalities introduced with the LTE2551: RSRQ-based A5 feature: • •
Additional A5 event for the reference signal received quality (RSRQ) Combined RSRQ and reference signal received power (RSRP) check
Additional A5 event for the RSRQ The LTE A5 event is triggered when the serving cell becomes worse than A5-threshold1 while a neighboring cell becomes better than A5-threshold2. It means that the current cell is below the acceptable level.
108
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Figure 8
Descriptions of radio resource management and telecom features
LTE A5 event AservingcellbecomesworsethanA5-threshold1(condition1), andaneighborcellbecomesbetterthanA5-threshold2(condition2)
condition2fulfilled condition1fulfilled
RSRQquantitytrigger [dB]
A5-threshold2 offset
hysteresis
serving cell A5-threshold1 hysteresis
neighbor cell time [ms]
signalofaneighborcell
A5start
signalofaservingcell
A5end
LEGEND
The LTE2551: RSRQ-based A5 feature introduces an additional A5 event for the RSRQ. The A5 event with the trigger quantity RSRQ is introduced in addition to the A5 RSRP event. The parameter used for RSRQ-based A5 activation is Activate RSRQ-based A5 (actRsrqInterFreqMobility). The RSRQ A5-threshold1 is activated with the RSRQ A5 inter-frequency threshold1 (threshold3RsrqInterFreq) parameter, while the RSRQ A5-threshold2 is activated with the RSRQ A5 interfrequency threshold2 (threshold3aRsrqInterFreq) parameter. If the feature is disabled, the legacy RSRP A5 behavior applies for a target carrier.
g
Note: Without LTE2551, the A5 event was intended only for the RSRP. With LTE2551, it is possible to have A5 event for both the RSRP and RSRQ. Combined RSRQ and RSRP measurement check It is possible to perform a combined RSRQ and RSRP measurement post-check at the eNB when either the A5 RSRP or A5 RSRQ report is received. This is an additional LTE2551 functionality, and it is activated with the Enable combined RSRP and RSRQ check (enableCombRsrpRsrq) parameter. The eNB verifies both reported measurement quantities (RSRP and RSRQ) of the target carrier based on an operator-configurable A5-thresholds. Without LTE2551, it was possible to verify the A5 report only for the RSRP. The combined RSRQ and RSRP measurement check allows rejecting the handover reported cells based on both RSRP and RSRQ measurements. The combined RSRP and RSRQ check is service-specific for RSRP (in case, for example, LTE64: Service-based Handover Thresholds is enabled). After a target cell has been successfully selected, a handover preparation phase is initiated.
Issue: 01 Draft
DN09237915
109
Descriptions of radio resource management and telecom features
g
3.15.2.2
FDD-LTE16A, Feature Descriptions and Instructions
Note: The LTE2551: RSRQ-based A5 feature does not increase the number of simultaneously active measurements at UEs. Either the A5 RSRP or A5 RSRQ measurement is active at a given time. If the feature is disabled, the legacy RSRP A5 behavior applies. If A5 RSRQ parameters are not configured for a target carrier, the legacy RSRP A5 behavior applies to the target carrier.
A5 RSRQ and RSRP conditions The A5 RSRQ and A5 RSRP measurements start when the quality conditions listed in the Table 61: A5 RSRP and A5 RSRQ activation conditions are fulfilled. During that period, a decision on whether to initiate an inter-frequency handover is made by the eNB; consequently, after a successful target cell selection a handover preparation phase is initiated. Table 61
A5 RSRP and A5 RSRQ activation conditions
A5 RSRP measurement is deactivated, and A5 RSRQ is activated when:
g
A5 RSRQ measurement is deactivated, and A5 RSRP is activated when:
A5 RSRP is already active
A5 RSRQ is already active
the A2 RSRQ event occurs
the A2 RSRP even occurs
the serving cell RSRP measurement is greater than the inter-frequency A2 RSRP threshold
the serving cell RSRQ measurement is greater than the A2 RSRQ threshold
If the serving cell RSRP is lower or equal to the inter-frequency A2 RSRP threshold, then A5 RSRQ is not configured, and the A5 RSRP measurement is retained.
If the serving cell RSRQ is lower or equal to the A2 RSRQ threshold, then A5 RSRP is not configured, and the A5 RSRQ measurement is retained.
Note: There is only one A2 RSRQ treshold, and there are multiple A2 RSRP tresholds.
3.15.3 LTE2551 system impact Interdependencies between features The following features must be activated to enable the A5 RSRQ in the LTE2551: RSRQ-based A5 feature: • •
LTE55: Inter-frequency Handover LTE1198: RSRQ Triggered Mobility
The LTE2551: RSRQ-based A5 feature impacts the following features: •
•
•
110
LTE64: Service-based Handover Thresholds LTE64 introduces the QCI1-based RSRP offset and thresholds for the A3 and A5 events. This feature has to be enabled if the QCI1-specific RSRP thresholds are used when the combined check on RSRP and RSRQ is supported at the eNB. It also has to be enabled if the RSRP measurement is compared with a QCI1-specific threshold for the A2 event. LTE556: ANR Intra-LTE, Inter-frequency – UE-based New A5-RSRQ reports are considered for passive automated neighbor relation (ANR). LTE1060: TDD-FDD Handover
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
Descriptions of radio resource management and telecom features
This feature must be enabled if LTE2551 is active and the FDD handover needs to be supported. LTE2008: Extended Inter-frequency Measurements Up to eight inter-frequency layers (combination of FDD and TDD) can be broadcasted with SIB5 for a cell reselection. Up to six inter-frequency measurements (combination of FDD and TDD) can be configured per UE, depending on the configured inter-frequency bands.
Impact on interfaces The LTE2551: RSRQ-based A5 feature has no impact on interfaces. Impact on network management tools The LTE2551: RSRQ-based A5 feature has no impact on network management tools. Impact on system performance and capacity The LTE2551: RSRQ-based A5 feature has no impact on system performance or capacity.
3.15.4 LTE2551 reference data Requirements Table 62
LTE2551 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE16A
not supported
Flexi Zone Controller
OMS
FL 16A
Flexi Multiradio 10 BTS
AirScale BTS
FL 16A
FL 16A
UE
LTE OMS 16A 3GPP R8 UE capabilities
Flexi Zone Micro BTS FL 16A
NetAct
FL 16A
MME
NetAct 16.8
Flexi Zone Access Point
SAE GW
Support not required
Support not required
Alarms There are no alarms related to the LTE2551: RSRQ-based A5 feature. Commands There are no commands related to the LTE2551: RSRQ-based A5 feature. Measurements and counters There are no measurements or counters related to the LTE2551: RSRQ-based A5 feature. Key performance indicators There are no key performance indicators related to the LTE2551: RSRQ-based A5 feature. Parameters Table 63
New parameters introduced by LTE2551 Full name
Issue: 01 Draft
Abbreviated name
Managed object
Parent structure
Activate RSRQ-based A5
actRsrqInterFreqM LNBTS obility
-
Enable combined RSRP and RSRQ check
enableCombRsrpRsr LNBTS q
-
DN09237915
111
Descriptions of radio resource management and telecom features
Table 63
FDD-LTE16A, Feature Descriptions and Instructions
New parameters introduced by LTE2551 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
A5 RSRQ inter-frequency rsrqA5InterFreqMo LNHOIF mobility parameters bilityParams
-
RSRQ A5 inter-frequency a5ReportIntervalR LNHOIF report interval srqInterFreq
rsrqA5InterFreqMo bilityParams
RSRQ A5 inter-frequency a5TimeToTriggerRs LNHOIF time to trigger rqInterFreq
rsrqA5InterFreqMo bilityParams
RSRQ A5 inter-frequency hysThreshold3Rsrq LNHOIF hysteresis InterFreq
rsrqA5InterFreqMo bilityParams
RSRQ A5 inter-frequency threshold3aRsrqIn LNHOIF threshold2 terFreq
rsrqA5InterFreqMo bilityParams
RSRQ A5 inter-frequency threshold3RsrqInt LNHOIF threshold1 erFreq
rsrqA5InterFreqMo bilityParams
For parameter descriptions, see LTE Radio Access Operating Documentation/ Reference/Parameters. Sales information Table 64
LTE2551 sales information
Product structure class Application software (ASW)
License control SW Asset Monitoring
Activated by default No
3.16 LTE2557: Supplemental DL Carrier Extension The LTE2557: Supplemental DL Carrier Extension feature enhances LTE2149: Supplemental Downlink Carrier. A supplemental DL carrier (SDLC) is a cell only with downlink channel and not with the physical hybrid-ARQ indicator channel (PHICH). An SDLC can be used only as a secondary cell (SCell) in combination with downlink carrier aggregation for LTE.
3.16.1 LTE2557 benefits The LTE2557: Supplemental DL Carrier Extension feature improves network coverage, capacity, and peak rates for the end user. This feature enables configuring cells as DL only which is beneficial in situations where interference on UL is too high, or UL spectrum is reserved (for example for military usage), but operators would like to make use of the DL spectrum.
3.16.2 LTE2557 functional description The LTE2557: Supplemental DL Carrier Extension feature enhances the LTE2149: Supplemental Downlink Carrier feature. This feature allows configuring the DL-only cell as a supplemental DL carrier (SDLC) and as an enhancement this feature allows to configure SDLC: •
112
on any FDD band used by an eNB
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• • •
Descriptions of radio resource management and telecom features
for cells with any allowed bandwidth (5, 10, 15, and 20 MHz) for 1 TX, 2 TX, as well as 4 TX cell configurations for intra-eNB and inter-eNB carrier aggregation (CA) configurations
There are two possible scenarios for feature deployment: • •
All neighbor cells on a given frequency are DL-only cells; the whole frequency can be set as an SDLC frequency. Only part of neighbor cells are DL-only; such DL-only cells should be blacklisted to avoid unnecessary mobility, or the LTE1944: Dynamic Handover Blacklisting feature should be used.
It is possible to configure any cell as a DL-only cell by setting the TX and RX usage (txRxUsage) LCELL parameter to a Tx value. This parameter change triggers BTS Site Manager (BTS SM) to automatically set the Activate supplemental downlink carrier (actSdlc) LNCEL activation flag to true.
g
Note: Any reconfiguration from a DL and UL cell to DL-only, and vice versa, may lead to a BTS restart. It depends on what kind of parameters were modified. If the eNB decides that a BTS restart is needed, all UEs will be lost, affecting also the shutdown of all other cells served by this eNB. A barred cell from the perspective of LTE2557: Supplemental DL Carrier Extension In the LTE2557: Supplemental DL Carrier Extension feature, after configuring a cell as a supplemental DL carrier (SDLC), its status is broadcasted over an air interface, in a system information block 1 (SIB1), as a barred cell so that it cannot act as a primary cell (PCell) and is not used for mobility purposes. This is unrelated to the configuration of O&M parameter for a cell barred status (the cellBarred LNCEL parameter has a notBarred value). Since a cell is not barred from the O&M's perspective, adding SDLC as an SCell for downlink carrier aggregation is also possible. Mobility towards supplemental DL carrier (SDLC) Mobility towards SDLC is not possible. When a cell is declared as an SDLC cell, to avoid unnecessary signaling and measurements for handover to DL-only cells or SDLC cells, there is a need to blacklist such a cell for a handover or use the LTE1944: Dynamic Handover Blacklisting feature (this allows temporarily blacklisting the neighbor relation). On such a cell, any incoming Handover Request will be rejected by the eNB with cause Radio Network Layer (Cell not Available) value in Handover Preparation Failure message. Outgoing handovers targeting SDLC cells can be forbidden by configuring the Supplemental DL carrier frequency list (sdlcFreqList) LNBTS parameter list. This parameter list contains the frequencies (DL E-UTRA absolute radio frequency channel numbers) of cells that are operated in downlink only and are used as SCells in carrier aggregation. This list can be used to forbid outgoing mobility procedures. Load-balancing relation with supplemental DL carrier (SDLC) DL-only cells are excluded from all types of load balancing, apart from the one available for an SCell of the LTE2006: Flexible SCell Selection feature. For an SCell selection, the LTE2006 feature uses the normalized load compare value (NLCV) mechanism which selects a less loaded SCell when radio admission control has the choice between two or more SCells on different frequency layers.
Issue: 01 Draft
DN09237915
113
Descriptions of radio resource management and telecom features
3.16.2.1
FDD-LTE16A, Feature Descriptions and Instructions
A barred cell from the perspective of LTE2557: Supplemental DL Carrier Extension In the LTE2557: Supplemental DL Carrier Extension feature, after configuring a cell as a supplemental DL carrier (SDLC), its status is broadcasted over an air interface, in a system information block 1 (SIB1), as a barred cell so that it cannot act as a primary cell (PCell) and is not used for mobility purposes. This is unrelated to the configuration of O&M parameter for a cell barred status (the cellBarred LNCEL parameter has a notBarred value). Since a cell is not barred from the O&M's perspective, adding SDLC as an SCell for downlink carrier aggregation is also possible.
3.16.2.2
Mobility towards supplemental DL carrier (SDLC) Mobility towards SDLC is not possible. When a cell is declared as an SDLC cell, to avoid unnecessary signaling and measurements for handover to DL-only cells or SDLC cells, there is a need to blacklist such a cell for a handover or use the LTE1944: Dynamic Handover Blacklisting feature (this allows temporarily blacklisting the neighbor relation). On such a cell, any incoming handover request will be rejected. When the whole frequency is configured as an SDLC frequency, the BTS will not start any mobility towards target cells on the SDLC frequency.
3.16.2.3
Load-balancing relation with supplemental DL carrier (SDLC) DL-only cells are excluded from all types of load balancing, apart from the one available for an SCell of the LTE2006: Flexible SCell Selection feature. For an SCell selection, the LTE2006 feature uses the normalized load compare value (NLCV) mechanism to select a less loaded SCell when radio admission control (RAC) has the choice between two or more SCells on different frequency layers.
3.16.2.4
Idle-mode mobility relation with supplemental DL carrier (SDLC) An SDLC cell is always broadcasted as a barred cell (via SIB); therefore, even if the SDLC frequency is used in reselection, SDLC cells should be excluded from idle-mode mobility. In addition, idle-mode-related managed object classes (MOCs) cannot point to the frequency which is configured as an SDLC frequency.
3.16.3 LTE2557 system impact Interdependencies between features The following features must be activated before activating the LTE2557: Supplemental DL Carrier Extension feature: • •
any of the downlink carrier aggregation features are a prerequisite LTE2149: Supplemental DL Carrier This feature is a baseline for the LTE2557 feature.
The LTE2557: Supplemental DL Carrier Extension feature is impacted by the following features: •
114
The following features can be used together with LTE2557 to increase flexibility of Carrier Aggregation configurations:
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
– –
–
•
Descriptions of radio resource management and telecom features
LTE2006: Flexible SCell Selection An SDLC cells play a role of candidates for SCell swap. LTE2233: N-out-of-M Downlink Carrier Aggregation An SDLC cells play a role of candidates for SCell swap based on A6 measurement reports or average cell load. LTE2007: Inter-eNodeB Carrier Aggregation An SDLC cells can be configured in inter-eNB CA deployments (including cases where one of the eNBs hosts SDLC cells only).
LTE1944: Dynamic Handover Blacklisting This feature allows temporarily blacklisting the neighbor relation. It is recommended to use LTE1944 together with LTE2557 to avoid unnecessary signaling and measurements for a handover to DL-only cells (SDLC cells).
Impact on interfaces The LTE2557: Supplemental DL Carrier Extension feature has no impact on interfaces. Impact on network management tools The LTE2557: Supplemental DL Carrier Extension feature has no impact on network management tools. Impact on system performance and capacity The LTE2557: Supplemental DL Carrier Extension feature can improve peak and download throughput for non-GBR UEs with the secondary cell (SCell) configured. Additionally, a system capacity gain is expected. It can be doubled for bandwidth combinations with an equal bandwidth of two involved cells.
3.16.4 LTE2557 reference data Requirements Table 65
LTE2557 hardware and software requirements
System release FDD-LTE 16A Flexi Zone Controller FL16A
Flexi Multiradio BTS not supported OMS
Flexi Multiradio 10 BTS FL16A UE
LTE OMS16A
Flexi Zone Micro BTS FL16A
NetAct
3GPP R10 UE NetAct 16.8 capabilities is the minimum
Flexi Zone Access Point FL16A
MME support not required
SAE GW support not required
BTS faults and reported alarms There are no faults related to the LTE2557: Supplemental DL Carrier Extension feature. Commands There are no commands related to the LTE2557: Supplemental DL Carrier Extension feature. Measurements and counters There are no measurements or counters related to the LTE2557: Supplemental DL Carrier Extension feature.
Issue: 01 Draft
DN09237915
115
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
Key performance indicators There are no key performance indicators related to the LTE2557: Supplemental DL Carrier Extension feature. Parameters Table 66
Parameters modified by LTE2557 Full name
Abbreviated name
Managed object
Parent structure
TX and RX usage
txRxUsage
LCELL
resourceList
Activate supplemental downlink carrier
actSdlc
LNCEL
-
For parameter descriptions, see FDD-LTE BTS Parameters. Sales information Table 67
LTE2557 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
3.17 LTE2559: ARP-based Partial Admission Control for Handover The LTE2559: ARP-based Partial Admission Control for Handover feature introduces a partial radio admission control (in the S1AP: Initial Context Setup and ERAB Setup scenarios) for voice-call clients, regarding the allocation and retention priority (ARP) value.
3.17.1 LTE2559 benefits The LTE2559: ARP-based Partial Admission Control for Handover feature provides the following benefits: • •
It is possible to improve the LTE handover success rate by introducing a partial admission control. It is possible to monitor the number of bearers released by the eNB as a result of partial admission control.
3.17.2 LTE2559 functional description 3.17.2.1
EPS bearers The evolved packet system bearer (EPS bearer) is used to transport user data between the UE and the P-GW/S-GW. The bearer is a set of network parameters that defines how the UE data is treated when it travels across the network.
116
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
Evolved packet system (EPS) defines a packet data network (PDN) connection service as an IP connection between a UE and an external PDN of the public land mobile network (PLMN). The PDN connection service supports the transmission of one or more service data flows (SDFs). SDF is a virtual connection which carries data plane traffic. SDFs mapped to the same EPS bearer receive the same bearer-level packet forwarding treatment, for example, scheduling policy, queue management policy, rate shaping policy. For a group-termination-point (GTP)-based S5/S8 reference point, PDN connectivity is provided by an EPS bearer running between the UE and the packet data network gateway (P-GW). Figure 9: LTE/EPC service data flows illustrates the LTE/EPC service data flow in more detail. A traffic flow template (TFT) defines which data flows can be mapped to which bearers. It exists in the UE for the uplink, and in P-GW for the downlink. Figure 9
LTE/EPC service data flows Application / Service Layer
UL Service Data Flows
DL Service Data Flows
UL-TFT
DL-TFT
UL-TFT → RB-ID
DL-TFF →
RB-ID ↔ S1-TEID
S1-TEID ↔
Radio Bearers
S5/S8a-TEID
GTP-U
GTP-U
GTP-U
GTP-U
S-GW
eNB
UE
S5/S8aTEID
S1 Bearers
P-GW S5 /S8 Bearers
The EPS bearers correspond to the packet data protocol (PDP) context in 2G/3G networks, composed of the sub-bearers, as illustrated in Figure 10: LTE/EPC EPS highlevel bearer model. •
• •
A radio bearer transports the packets of an EPS bearer between the UE and the eNB. If a radio bearer exists, there is a one-to-one mapping between an EPS bearer and this radio bearer. An S1 bearer transports the packets of an EPS bearer between the eNB and the serving gateway (S-GW). An S5/S8a bearer transports the packets of an EPS bearer between the serving GW and the PDN gateway (P-GW).
An E-UTRAN radio access bearer (E-RAB) refers to the connection of an S1 bearer and a corresponding radio bearer. A data radio bearer transports the packets of an EPS bearer between a UE and an eNB. When a data radio bearer exists, there is a one-toone mapping between this data radio bearer and the EPS bearer/E-RAB. Figure 10: LTE/EPC EPS high-level bearer model shows the EPS bearer services' layered architecture.
Issue: 01 Draft
DN09237915
117
Descriptions of radio resource management and telecom features
Figure 10
FDD-LTE16A, Feature Descriptions and Instructions
LTE/EPC EPS high-level bearer model EPC
E-UTRAN
UE
eNB
S-GW
Internet
Peer Entity
P-GW
End-to-endService
EPSBearer E-RAB RadioBearer
ExternalBearer
S5/S8Bearer s1Bearer
Radio
S1
S5/S8
Gi
When the UE is active, all sub-bearers exist for the UE, but when it moves to an idle state, S1 and radio bearers are released. However, the EPS bearer and associated contexts in a UE and EPS remain even though the UE is in an idle state. An EPS bearer can be a default bearer or a dedicated bearer. A default EPS bearer is set up when a UE attaches to the EPS network. There will be one default EPS bearer setup per PDN. The default EPS bearer is a non-GBR bearer, and it is “always-on”; that is, it is not released until the UE detaches from the PDN. The default EPS bearer's traffic flow template (TFT) matches all packets, which means, it can be used for any kind of traffic. In addition to a default EPS bearer, dedicated EPS bearers can be set up for the UE. The dedicated EPS bearer can be either a GBR or a non-GBR bearer, and it is set up on network control, for example, for VoIP calls. The Flexi Multiradio BTS supports up to three GBR EPS radio bearers per UE. Up to six data radio bearers (DRBs) can be established per UE. Multiple DRBs can be either multiple default EPS bearers or a combination of default and dedicated EPS bearers. The different EPS bearers per UE can have the same or a different QCI. The operator is able to offer additional service combinations. Some data might be treated in a special way, for example, a flow of data might be provided a guaranteed bit rate while another one may face a low transfer.
3.17.2.1.1
Bearer management Bearer management provides basic procedures to establish the default EPS bearer that provides an always-on service to the user. Bearer management is part of the LTE control plane and handles the establishment, modification, and release of bearers. Bearer management includes: •
118
establishment and release of S1 bearers on the S1 interface
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• •
•
Descriptions of radio resource management and telecom features
establishment, modification, and release of data radio bearers on the air interface translation of S1AP QoS parameters into configuration parameters of the U-plane in the eNB and UE, taking into account the UE capabilities and the QoS requirements of already established EPS bearers of the UE radio layer 2 configuration of SRB1 and SRB2
Bearer management supports: • • • • • • • • •
3.17.2.1.2
establishment of one non-GBR EPS bearer upon attach and upon UE- or EPCinitiated service request preparation of one non-GBR EPS bearer and SRBs during a handover provisioning of UE radio capabilities for a radio bearer configuration activation of AS security (all security algorithms) service differentiation for non-GBR EPS bearers establishment and release for multiple default and dedicated EPS bearers support of the conversational voice EPS bearer that is mapped to a GBR with RLC UM control of robust header compression (ROHC) rate capping – support of the UE AMBR by the S1AP Initial UE Context Setup procedure
Quality of service (QoS) The evolved packet system bearer (EPS bearer) QoS is controlled by QoS parameters. Each bearer uses a set of QoS parameters to describe the properties of the transporting channel such as bit rates, packet delay, packet loss, bit error rate, and scheduling policy. LTE/EPC provides a substantially optimized bearer handling and a QoS model, compared to 3G networks. In LTE/EPC, a single scalar label pointer, that is, the quality class indicator (QCI), is used for a set of QoS parameters, as highlighted in Table 68: QoS scheme for LTE. P-GW, S-GW, and eNB mainly use the QCI to classify the IP flows and request or allocate network resources. Table 68
QoS scheme for LTE
3G (QoS-aware) Residual BER
LTE (non-QoS-aware) Quality class indicator (QCI)
SDU error ratio Delivery of erroneous SDUs Maximum SDU size Delivery order Transfer delay Traffic class
Issue: 01 Draft
DN09237915
119
Descriptions of radio resource management and telecom features
Table 68
FDD-LTE16A, Feature Descriptions and Instructions
QoS scheme for LTE (Cont.)
3G (QoS-aware)
LTE (non-QoS-aware)
Traffic priority handling Allocation and retention priority (ARP) Maximum bit rate (MBR) Guaranteed bit rate (GBR) Aggregate maximum bit rate (AMBR)
The following summarizes the main features of the LTE/EPC QoS model: network-centric QoS scheme, deployed in LTE, reduces the complexity of UE implementations always-on default EPS bearer available after initial access further dedicated EPS bearer setup on network control (for example, for VoIP calls) no need for support from terminal application clients or the device operating system
• • • •
Table 69: Standard QCI characteristics (3GPP TS 23.203) shows an example of standard QCI characteristics, identifying the possible packet delay budgets, packet loss rates, and appropriate services. Table 69
QCI
Resource Type
Priority
Packet Delay Budget
Packet Loss Rate
Example of Services
2
100 ms
10-2
Conversational voice (VoIP)
2
4
150 ms
10-3
Conversational video (Live streaming)
3
3
50 ms
10-3
Real time gaming
4
5
300 ms
10-6
Non-conversational video (Buffered Streaming)
1
100 ms
10-6
IMS signaling
6
6
300 ms
10-6
Video (Buffered streaming) TCP-based (for example, www, e-mail, chat, ftp, p2p file sharing, progressive video)
7
7
100 ms
10-3
Voice, Video (Live streaming) interactive gaming
1
5
120
Standard QCI characteristics (3GPP TS 23.203)
GBR
Non-GBR
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 69
QCI
g
3.17.2.1.3
Descriptions of radio resource management and telecom features
Standard QCI characteristics (3GPP TS 23.203) (Cont.)
Resource Type
Priority
8
8
9
9
Packet Delay Budget 300 ms
Packet Loss Rate 10-6
Example of Services
Video (Buffered streaming) TCP-based (for example, www, e-mail, chat, ftp, p2p file sharing, progressive video)
Note: The standardized characteristics are not signaled on any interface. They should be understood as guidelines for the pre-configuration of node-specific parameters for each QCI. The goal of standardizing a QCI with corresponding characteristics is to ensure that applications/services mapped to that QCI receive the same minimum level of QoS in multi-vendor network deployments and in the case of roaming. A standardized QCI and its corresponding characteristics are independent of the UE's current access (3GPP or non-3GPP).
ARP The primary purpose of allocation and retention priority (ARP) is to decide whether a bearer establishment or modification request can be accepted or needs to be rejected as a result of resource limitations. In addition, the ARP can be used by the eNB to decide which bearer(s) to drop during exceptional resource limitations (for example, during a handover). ARP is defined by 3GPP TS 23.203 and TS 36.413. It is based on one ERAB parameter comprising the following three values: • • •
ARP priority level, defining the importance of the E-RAB. A more important E-RAB gets and keeps needed resources more prioritized than less important E-RABs pre-emption vulnerability, defining if the E-RAB may be pre-empted by an E-RAB with higher ARP priority pre-emption capability, defining if the E-RAB may pre-empt any E-RAB with lower ARP priority
Pre-emption is a procedure by which a call with a higher priority can cause the release of an ongoing call with a lower priority. It is limited by the maxNumPreEmptions parameter. This parameter limits the number of pre-emptions, which may be caused by admitting a set of E-RABs (for example, at initial context setup, E-RAB setup, handover request).
3.17.2.2
LTE2559 overview The ARP-based admission control (AC) was originally introduced with the LTE534: ARPbased Admission Control for E-RABs feature. This feature offers a priority-controlled admission and pre-emption for GBR and non-GBR bearers. The LTE534 functionality allows the end user to make use of high-bit-rate GBR services. Current Nokia implementation for the target eNB uses the All-or-Nothing principle when allocating resources for an incoming handover (either all E-RABs are admitted, or the handover preparation is rejected).
Issue: 01 Draft
DN09237915
121
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
The LTE2559: ARP-based Partial Admission Control for Handover feature changes this behavior of the target eNB, and it allows partial admission in the following scenarios: • •
incoming handover with a cause value Handover Desirable for Radio Reasons or Time Critical Handover incoming service-based handover for UEs with an established bearer assigned to an emergency ARP (not only QCI1)
A handover preparation is considered successful if it is possible to admit all non-preemptable bearers. ARP-based partial AC has already been introduced for the S1AP: Initial Context Setup and ERAB Setup scenarios. Now the LTE2559 functionality also applies partial admission to incoming handovers. Since the bearers subject to a handover are not new from a UE's point of view, the vulnerability of the existing ERABs is considered. No nonpre-emptable ERAB must be released due to partial admission; this introduces a third operational mode to the AC: all non-pre-emptable ERABs must be admitted. With the LTE2559 feature, it is also possible that: •
•
The list of superfluous bearers can be released for partial admission by the target eNB, and it is now also applicable to X2 handovers and intra-eNB handovers. The list is not taken from the S1 message but from the AC result. A target cell implementation ensures that partial admission is only applied in cases where a source cell implementation would not cancel the handover preparation.
As a result, the handover success rate is increased for some important services (for example, VoLTE). Whether to apply partial admission or not is presented in the table: Table 70
122
Partial admission decision table
Handover type
Topology
X2AP/S1AP cause value
Handover due to radio reasons
Intra-eNB
n/a
Not relevant
Partial admission
E-RAB with vulnerability non-preemptable
Handover due to radio reasons
X2 or S1
Handover desirable for radio reasons
Not relevant
Partial admission
E-RAB with vulnerability non-preemptable
Handover due to radio reasons
X2 or S1
Time critical handover
Not relevant
Partial admission
E-RAB with vulnerability non-preemptable
Service-based Intra-eNB handover
n/a
No
All-orNothing
All
Service-based Intra-eNB handover
n/a
Yes
Partial admission
E-RAB with vulnerability non-preemptable
Service-based X2 or S1 handover
Resource optimisation handover
No
All-orNothing
All
DN09237915
Emergency Admission session concept
Admitted bearers
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 70
Descriptions of radio resource management and telecom features
Partial admission decision table (Cont.)
Handover type
Topology
X2AP/S1AP cause value
Emergency Admission session concept
Admitted bearers
Service-based X2 or S1 handover
Resource optimisation handover
Yes
Partial admission
E-RAB with vulnerability non-preemptable
Load-based handover
Any
Reduce load in a serving cell
Not relevant
All-orNothing
All
Foreign vendor source eNB
X2 or S1
Anything else
Not relevant
All-orNothing
All
As the source eNB cancels any handover preparation for a load-based handover (even for emergency services in case of partial admission by the target eNB) the target eNB does not perform partial admission for a load-based handover for emergency services. This change does not apply to a service-based handover.
3.17.3 LTE2559 system impact Interdependencies between features The following features must be activated before activating the LTE2559: ARP-based Partial Admission Control for Handover feature: • •
LTE53: Intra and Inter-eNB Handover with X2 LTE534: ARP-based Admission Control for E-RABs
The LTE2559: ARP-based Partial Admission Control for Handover feature impacts the following features: •
•
•
•
•
Issue: 01 Draft
LTE10: EPS Bearers for Conversational Voice Service This feature introduces QCI1 bearers. If it is deactivated at a target eNB, the incoming handover requests for a UE with the established QCI1 bearer are rejected. With the LTE2559, these handover requests can be accepted if the vulnerability of the QCI is pre-emptable. The QCI1 E-RAB would then also be released. LTE54: Intra-LTE Handover via S1 This feature introduces the functionality of intra-LTE S1-based handover. LTE2559 introduces partial admission to the target eNB behavior in case of the intra-LTE S1 handover. LTE57: Inter-RAT Handover from UTRAN This feature enables the functionality of S1-based handover from UTRAN (WCDMA or TD-SCDMA in case of TD-LTE). LTE2559 introduces partial admission to the target eNB behavior in the case of a handover from UTRAN. LTE439: SGW Relocation with X2 Connection This feature introduces the E-RAB release as part of the Path Switch Request procedure in the completion phase of X2 handover. Partial admission, along with LTE2559, increases the possibility that the MME requests a release of an additional E-RAB. LTE735: RRC Re-establishment
DN09237915
123
Descriptions of radio resource management and telecom features
•
• •
•
•
•
•
•
FDD-LTE16A, Feature Descriptions and Instructions
This feature introduces RRC: RRC Re-Establishment in multiple scenarios. If a target eNB applies partial admission during a handover preparation, ERABs which have not been admitted need to be released in a UE as part of RRC ReEstablishment. LTE1074: Multimedia Priority Services This feature introduces the ARP mechanism, raising incoming handover requests for high priority services. With the introduction of partial admission, ARP raising is no longer needed as the low priority E-RAB may be rejected individually without rejecting the complete handover request. LTE1127: Service-based Mobility Trigger LTE2503 Emergency-call-based Mobility Trigger The LTE1127: Service-based Mobility Trigger feature defines a specific functionality in the source eNB to cancel a service-based X2 handover or S1 handover. With the LTE2559, it is ensured that no service-based intra-eNB handover with partial admission will be allowed. The same rules apply to a service-based inter-eNB handover from LTE2503. LTE1170: Inter-eNB IF Load Balancing This feature defines the functionality of temporary blacklisting for the exceptional scenario where a foreign vendor's peer eNB has performed partial admission (for any type of handover) due to an overload. With LTE2559, this functionality becomes a regular use case. Furthermore, LTE1170 has defined a specific functionality in the source eNB to cancel a load-based X2 handover or S1 handover if foreign vendor's peer eNB performs partial admission. With LTE2559, it is ensured that no load-based intra-eNB handover with partial admission is allowed (not even for emergency services). LTE1617: RLF-triggered Handover This feature introduces RRC: RRC Re-Establishment towards the unprepared target cells. If a UE requests RRC: RRC Re-Establishment, the target eNB sends RLF Indication to a source cell and waits for a handover preparation request for this UE. With LTE2559, the target eNB may apply partial admission during the handover preparation. The ERABs which have not been admitted need to be released in the UE as part of RRC: RRC Re-Establishment. LTE2275: PCell Swap PCell swap is considered as a special case of the intra-eNB handover. It is handled as an intra-eNB handover due to load reasons. LTE2402: SCell Configuration during Handover This feature introduces the setup of SCells during a handover. In case LTE2559 releases some of the E-RABs, it may no longer make sense to set up SCells. LTE2611: Introduction of Public-safety-specific QCI Bearers This feature introduces public safety bearers with dedicated QCI 65, 66, 69, and 70. If LTE2559 and LTE2611 are deactivated at the target eNB, the incoming handover requests for a UE with PS QCI would be rejected. With LTE2559, these handover requests are accepted if the vulnerability of all PS QCI is pre-emptable. The PS QCI ERABs are released at the same time.
Impact on interfaces The LTE2559: ARP-based Partial Admission Control for Handover feature impacts interfaces as follows: •
124
S1
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
–
•
Descriptions of radio resource management and telecom features
The feature adds support for E-RABs Failed to Setup List in the S1AP: Handover Request Acknowledge message.
X2 –
The feature adds support for E-RABs Not Admitted List in the X2AP: Handover Request Acknowledge message.
Impact on network management tools The LTE2559: ARP-based Partial Admission Control for Handover feature has no impact on network management tools. Impact on system performance and capacity The LTE2559: ARP-based Partial Admission Control for Handover feature has no impact on system performance or capacity.
3.17.4 LTE2559 reference data Requirements Table 71
LTE2559 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
AirScale BTS
FL16A
not supported
UE
LTE OMS16A
3GPP R8 UE capabilities
NetAct NetAct 16.8
Flexi Zone Micro BTS FL16A
Flexi Zone Access Point FL16A
MME support not required
SAE GW support not required
Alarms There are no alarms related to the LTE2559: ARP-based Partial Admission Control for Handover feature. BTS faults and reported alarms There are no faults related to the LTE2559: ARP-based Partial Admission Control for Handover feature. Commands There are no commands related to the LTE2559: ARP-based Partial Admission Control for Handover feature. Measurements and counters Table 72 Counter ID
Issue: 01 Draft
New counters introduced by LTE2559 Counter name
Measurement
M8006C E-RABs released due to 261 partial Handover regardless of the bearers QCI
LTE EPS Bearer
M8006C QCI1 E-RABs released due to 273 partial Handover
LTE EPS Bearer
M8006C Number of successful partial 281 admission control checks
LTE EPS Bearer
DN09237915
125
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
For counter descriptions, see LTE Radio Access Operating Documentation/Reference/Counters and Key Performance Indicators. Key performance indicators There are no key performance indicators related to the LTE2559: ARP-based Partial Admission Control for Handover feature. Parameters Table 73
New parameters introduced by LTE2559 Full name
Abbreviated name
Activate partial admission for handover
Table 74
actPartialAcHo
Managed object LNBTS
Parent structure -
Existing parameters related to LTE2559 Full name
Activate enhanced AC and GBR services
Abbreviated name
Managed object
actEnhAcAndGbrSer LNBTS vices
Parent structure -
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 75
LTE2559 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
3.18 LTE2564: Centralized RAN CL16A Release The LTE2564: Centralized RAN CL16A Release feature extends the LTE2470: Centralized RAN CL16 Release feature with: • •
CRAN operation with 4Tx/2Rx MIMO on downlink (DL). Selectable (enable/disable) control over interference rejection combining coordinated cultipoint (IRC CoMP) mode
3.18.1 LTE2564 benefits The LTE2564: Centralized RAN CL16A Release feature provides the following benefits: • •
126
Possibility to use 4x2 MIMO on DL for better throughput while using CRAN on UL. Possibility to enable/disable the CRAN gain for demo and testing purposes, without an eNB restart; as a precondition, the CRAN feature flag actCRAN must be set to true.
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
3.18.2 LTE2564 functional description The LTE2564: Centralized RAN CL16A Release feature is the successor of the LTE2470: Centralized RAN CL16 Release feature. The feature enables increasing throughput in DL. A mix of 4Tx per cell and 2Tx per cell is allowed in the same CRAN system. Additionally, untill the LTE2564: Centralized RAN CL16A Release feature, any change in configuration required a reset of CRAN. The feature ensures a dynamical CRAN gain configuration without the reset. It is possible by option enable/disable of all helper cells so that only a serving cell is considered a baseline (non-CRAN) gain. Migration from FL16 to FL16A During migration from FL16 (LTE2470: Centralized RAN CL16 Release) to FL16A (LTE2564: Centralized RAN CL16A Release), the same helper cell association is preserved. This provides identical system functionality as the one in FL16 (LTE2470: Centralized RAN CL16 Release). The LTE2564: Centralized RAN CL16A Release feature does not change the general CRAN configuration concept introduced by the LTE2470: Centralized RAN CL16 Release feature and allows only the same chain/loop configuration as the legacy LTE2470: Centralized RAN CL16 Release feature. The LTE2564: Centralized RAN CL16A Release feature supports the same system size of the CRAN system (up to 9 FSMFs) and the same topology as the LTE2470: Centralized RAN CL16 Release feature.
3.18.3 LTE2564 system impact Interdependencies between features The following features have to be activated before activating the LTE2564: Centralized RAN CL16A Release feature: • • • •
g
LTE1710: Sync Hub Direct Forward LTE2901: Centralized RAN Supported Configurations CL16 Release LTE2883: Application of Diagnostic and Maintenance for Intelligent Network In case 4T2R MIMO per cell needs to be configured, the LTE568: DL Adaptive Closed Loop MIMO (4x2) feature must be activated. Note: The LTE2883: Application of Diagnostic and Maintenance for Intelligent Network (ADMIN) feature introduces a web-based tool for eNB diagnostic and maintenance tasks. ADMIN is an embedded eNB tool, and it does not require any additional package installation at the end user's station. The ADMIN tool provides the same possibility of enabling and disabling the CRAN gain as BTS SM or NetAct. With ADMIN, it is possible to have CRAN-related counters updated every other minute (instead of standard 15minute intervals). ADMIN utilizes an eNB-internal data model; thus, the enabling and disabling of CRAN gain is performed directly by eNB mechanisms. As a result, the whole reconfiguration process takes place much faster. For more information, see LTE2883: Application of Diagnostic and Maintenance for Intelligent Network feature.
The LTE2564: Centralized RAN CL16A Release feature impacts the following features:
Issue: 01 Draft
DN09237915
127
Descriptions of radio resource management and telecom features
•
FDD-LTE16A, Feature Descriptions and Instructions
LTE2291: Support for Carrier Aggregation on CL16A Release The LTE2291 feature utilizes the LTE2564 feature.
The following legacy features are not supported by the LTE2564: Centralized RAN CL16A Release feature: • • • • • • • • • • • • • • • • • • • • • • •
LTE1092: Uplink Carrier Aggregation – 2CC LTE180: Cell Radius Max 100 km LTE2387: Classical LTE(MORAN)–GSM(MOBSS) RF Sharing with One SM per Operator LTE2445: Combined Supercell LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations – I LTE2516: FRIJ Flexi RRH 4-pipe 1700/2100 160 W LTE2528: Extension of Downlink 3CC Carrier Aggregation – II LTE2531: FDD Downlink Carrier Aggregation 4CC/5CC LTE2576: Integrated GMC & BC Support on Flexi Zone Controller LTE2605: 4RX Diversity 20 MHz Optimized Configurations LTE2609: Dual Carrier Support LTE1.4 and LTE3 LTE2629: FDD-LTE Dual Carrier (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W LTE2637: Quad Carrier on Single RF Unit LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W LTE2680: FHEL Flexi RRH 2-pipe 1800 120 W LTE2729: FW2FIWA – Flexi Zone G2 Indoor Pico Dual Band BTS (Band AWS & Band 2) LTE2880: Support of Classical WCDMA/LTE RF-sharing on 4Tx/4Rx Remote Radio Head (RRH Rel. 4.3-family) LTE2920: Classical WCDMA/LTE-RF Sharing Support for Narrowband LTE (LTE 1.4 and 3 MHz) LTE3027: FRPD Flexi RFM 6-pipe 700 240 W LTE3092: Support for Dual-Band Indoor/Outdoor FZ BTS (Pre–Rel 13) – Enhanced CSAT for LTE-U LTE3093: Support for Dual-Band Indoor/Outdoor FZ BTS (Pre–Rel 13) – UNII-1 Band Support All legacy features not supported by the LTE2470: Centralized RAN CL16 Release feature.
Impact on interfaces The LTE2564: Centralized RAN CL16A Release feature has no impact on interfaces. Impact on network management tools The LTE2564: Centralized RAN CL16A Release feature has no impact on network management tools. Impact on system performance and capacity The LTE2564: Centralized RAN CL16A Release feature increases throughput and service quality for the UEs on the cell edge regions of the cells from the CoMP set.
3.18.4 LTE2564 reference data Requirements
128
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 76
Descriptions of radio resource management and telecom features
LTE2564 feature hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
not supported
Flexi Zone Controller
OMS
not supported
LTE OMS16A
Flexi Multiradio 10 BTS FL16A UE 3GPP R8 mandatory
Airscale
Flexi Zone Micro BTS
Flexi Zone Access Point
not supported
not supported
not supported
NetAct
MME
SAE GW
NetAct 16.8
support not required
support not required
BTS faults and reported alarms Table 77
BTS fault related to the LTE2564 feature
Fault ID
Fault name
Reported alarms Alarm ID
110014
Optical cable inter-BTS or 7651 inter FSP cards too long for CRAN
Alarm name
BASE STATION OPERATION DEGRADED
For fault descriptions, see LTE Radio Access Operating Documentation/Reference/Faults and Alarms. Commands There are no commands related to the LTE2564: Centralized RAN CL16A Release feature. Measurements and counters There are no measurements or counters related to the LTE2564: Centralized RAN CL16A Release feature. Key performance indicators There are no key performance indicators related to the LTE2564: Centralized RAN CL16A Release feature.
g
Note: No additional performance counters and KPIs are included since the LTE2564 counters and KPIs are reused from the LTE1900/2470 features. Parameters Table 78
Existing parameters related to the LTE2564 feature Full name
Issue: 01 Draft
Abbreviated name
Managed object
Parent structure
Activate Centralized RAN
actCRAN
LNBTS
-
Activation of interfrequency load balancing (iFLB)
actInterFreqLB
LNBTS
-
CRAN gain configuration cranGain
CRAN
-
CRAN node identifier
cranNodeId
CRAN
-
CRAN identifier
cranId
CRAN
-
DN09237915
129
Descriptions of radio resource management and telecom features
Table 78
FDD-LTE16A, Feature Descriptions and Instructions
Existing parameters related to the LTE2564 feature (Cont.) Full name
Abbreviated name
Managed object
Parent structure
Downlink MIMO mode
dlMimoMode
CRAN
-
Resource list
resourceList
LCELL
-
Antenna line id
antlId
LCELL
Resource list
Sub cell identifier
subCellId
LCELL
Resource list
TX and RX usage
txRxUsage
LCELL
Resource list
For parameter descriptions, see LTE Radio Access Operating Documentation/ Reference/Parameters. Sales information Table 79
The LTE2564 feature sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
3.19 LTE2572: RSRQ-based B2 The LTE2572: RSRQ-based B2 feature introduces a new reference-signal-receivedquality-related (RSRQ) trigger to run the B2 inter-RAT measurements.
3.19.1 LTE2572 benefits The LTE2572: RSRQ-based B2 feature provides the following benefits: • •
It is possible to initiate an inter-RAT handover during periods of the high interference. The quality of service is sustained when the reference signal received quality (RSRQ) for the serving cell becomes worse than for the neighbor cell.
3.19.2 LTE2572 functional description Handover in mobile networks In order to secure service continuity and quality as a UE moves, UEs not only have to be connected to a serving cell but also to their neighbor cells. If the current connection is poor (due to signal level or quality), the UE has to search for better service. The signal strength of neighboring cells is measured periodically, and a handover occurs when specific conditions are fulfilled. During the handover procedure, running services are maintained; a call is not interrupted, and for an intra-LTE handover no data is lost. Handovers in LTE are network controlled and UE assisted. The goal of the handover procedure is to allocate the same resources for the UE in the target cell after the handover as those used prior to the handover. From the UE's point of view, a handover is always “hard,” meaning that a connection exists to only one cell at a time. Handovers result from such factors as:
130
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
•
Descriptions of radio resource management and telecom features
Quality: Handovers due to quality are typically initiated as a result of a UE measurement report indicating that the UE can communicate with a neighbor cell with a better channel quality than that of the current serving cell. Coverage: Handovers due to coverage are also initiated as a result of a UE measurement report indicating that the serving cell becomes worse than an absolute threshold.
Measurement and measurement reports The UE assists the eNB regarding a handover by sending measurement reports. When verifying radio conditions due to UE mobility (for example when the UE moves from one LTE cell to another or because of limited LTE coverage), measurement reports may initiate a handover. The type of measurements to be made by the UE, and the details of reporting them to the eNB, can be configured (measurement configuration and report configuration), and the eNB informs the UE about the configurations via the RRC: CONNECTION RECONFIGURATION message. The LTE reference signal received power (RSRP) measurement ensures a cell-specific signal strength metric. On the other hand, the LTE reference signal received quality (RSRQ) measurement provides a cell-specific signal quality metric. LTE handover events Before a handover is performed, a UE sends measurement reports to the network, and it is the network which decides whether a handover takes place or not. 3GPP defines a few types of such events within measurement reports. In order to limit the amount of signaling, the UE only sends measurement reports (RRC: MEASUREMENT REPORT messages) to the eNB when certain conditions (events) are met by the UEs' measurements. The following events are defined in the LTE standard: • • • • • • • •
Event A1: The serving cell becomes better than an absolute threshold. Event A2: The serving cell becomes worse than an absolute threshold. Event A3: An LTE neighbor cell becomes better than an offset relative to the serving cell. Event A4: An LTE neighbor cell becomes better than an absolute threshold. Event A5: The serving cell becomes worse than an absolute threshold, and an LTE neighbor cell becomes better than another absolute threshold. Event A6: Neighbour becomes offset better than secondary cell (SCell) Event B1: A non-LTE neighbor cell becomes better than an absolute threshold. Event B2: The serving cell becomes worse than an absolute threshold, and a nonLTE neighbor cell becomes better than another absolute threshold.
The events from A1 to A6 are related to intra-LTE handovers; B1 and B2 events are related to inter-RAT handovers. A1 is useful for restricting UE measurements to the serving cell only; A3 is connected with a better cell handover and A5 with a coverage handover. The events correspond with the type of measurements the UE performs. The measurement reports contain a list of target cells for a handover. The target cells are listed in order of decreasing value of the reporting quantity, that is, the best cell is reported first. As a consequence of the definition of the events, the target cell list cannot be empty. Handover conditions due to A5 get a higher priority than handovers due to A3.
Issue: 01 Draft
DN09237915
131
Descriptions of radio resource management and telecom features
3.19.2.1
FDD-LTE16A, Feature Descriptions and Instructions
LTE2572 overview The LTE2572: RSRQ-based B2 feature introduces an additional trigger, which is represented by the quantity of reference signal received quality (RSRQ). The trigger activates the quality-related B2 event, which takes place when the quality of serving cell becomes worse than B2-threshold1 (that is, during the RSRQ-based A2 event), and the quality of inter-RAT neighbor cell becomes better than B2-threshold2. The new event is introduced in addition to the already existing B2 RSRP event. Figure 11: LTE B2 event illustrates this scenario in detail. Figure 11
LTE B2 event Aservingcellbecomesworsethanthreshold1(condition1), andaninter-RATneighborcellbecomesbetterthanthreshold2(condition2)
condition2fulfilled condition1fulfilled
RSRQquantitytrigger [dB]
B2-Threshold2 offset
hysteresis
serving cell B2-Threshold1 hysteresis
neighbor cell time [ms]
signalofaneighborcell
B2start
signalofaservingcell
B2end
LEGEND
g g
3.19.2.2
Note: Without LTE2572: RSRQ-based B2, the B2 event was intended only for the RSRP. With LTE2572: RSRQ-based B2, it is possible to have also a B2 event for the RSRQ which allows to monitor the quality of service. Note: The LTE2572: RSRQ-based B2 feature does not increase the number of simultaneously active measurements at UEs, and either the B2 RSRP or B2 RSRQ measurement is active at a given time. However, the same B2 target thresholds are applied regardless of the source quantity. If the feature is disabled, the legacy RSRP B2 behavior applies. If the B2 RSRQ parameters are not configured for a target carrier, the legacy RSRP B2 behavior applies to the target carrier.
B2 RSRQ conditions The conditions for beginning and end of inter-RAT measurements are listed in Table 80: Conditions for the inter-RAT measurements period. During that period, a decision about whether to initiate an inter-RAT handover or not is made; consequently, after a successful target cell selection, a handover preparation phase is initiated.
132
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 80
Descriptions of radio resource management and telecom features
Conditions for the inter-RAT measurements period
Beginning of inter-RAT measurements
End of inter-RAT measurements
The quality of serving cell becomes worse than threshold1.
The quality of serving cell becomes better than threshold1.
The quality of inter-RAT neighbor cell becomes better than threshold2.
The quality of inter-RAT neighbor cell becomes worse than threshold2.
3.19.3 LTE2572: system impact Interdependencies between features The following feature must be activated before activating the LTE2572: RSRQ-based B2 feature: •
LTE1198: RSRQ-triggered Mobility The RSRQ-based A2 event takes a major role in the RSRQ-based B2 event; therefore, the LTE1198: RSRQ-triggered Mobility feature needs to be enabled.
Impact on interfaces The LTE2572: RSRQ-based B2 feature has no impact on interfaces. Impact on network management tools The LTE2572: RSRQ-based B2 feature has no impact on network management tools. Impact on system performance and capacity The LTE2572: RSRQ-based B2 feature has no impact on system performance or capacity.
3.19.4 LTE2572 reference data Requirements Table 81
LTE2572 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL16A
UE
LTE OMS 16A 3GPP R8
NetAct NetAct 16.8
Flexi Zone Micro BTS FL16A MME Support not required
Flexi Zone Access Point FL16A SAE GW Support not required
Alarms There are no alarms related to the LTE2572: RSRQ-based B2 feature. BTS faults and reported alarms There are no faults related to the LTE2572: RSRQ-based B2 feature. Commands There are no commands related to the LTE2572: RSRQ-based B2 feature. Measurements and counters There are no measurements or counters related to the LTE2572: RSRQ-based B2 feature. Key performance indicators
Issue: 01 Draft
DN09237915
133
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
There are no key performance indicators related to the LTE2572: RSRQ-based B2 feature. Parameters Table 82
New parameters introduced by LTE2572 Full name
Abbreviated name
Managed object
Parent structure
Activate RSRQ-based B2
actRsrqInterRatMo LNBTS bility
-
RSRQ B2 GERAN threshold1
b2Threshold1RsrqG LNHOG ERAN
rsrqB2GERANMobili tyParams
RSRQ B2 GERAN time to trigger
b2TimeToTriggerRs LNHOG rqGERANMeas
rsrqB2GERANMobili tyParams
RSRQ B2 GERAN hysteresis
hysB2ThresholdRsr LNHOG qGERAN
rsrqB2GERANMobili tyParams
RSRQ B2 GERAN report interval
reportIntervalRsr LNHOG qGERAN
rsrqB2GERANMobili tyParams
RSRQ B2 HRPD threshold1 b2Threshold1RsrqH LNHOH rpd
rsrqB2HrpdMobilit yParams
b2TimeToTriggerRs LNHOH rqHrpdMeas
rsrqB2HrpdMobilit yParams
RSRQ B2 HRPD hysteresis hysB2ThresholdRsr LNHOH qHrpd
rsrqB2HrpdMobilit yParams
reportIntervalRsr LNHOH qHrpd
rsrqB2HrpdMobilit yParams
RSRQ B2 UTRA threshold1 b2Threshold1RsrqU LNHOW tra
rsrqB2UtraMobilit yParams
b2TimeToTriggerRs LNHOW rqUtraMeas
rsrqB2UtraMobilit yParams
RSRQ B2 UTRA hysteresis hysB2ThresholdRsr LNHOW qUtra
rsrqB2UtraMobilit yParams
RSRQ B2 UTRA report interval
reportIntervalRsr LNHOW qUtra
rsrqB2UtraMobilit yParams
RSRQ B2 1XRTT threshold1
b2Threshold1RsrqR LNHOX tt
rsrqB2RttMobility Params
RSRQ B2 1XRTT time to trigger
b2TimeToTriggerRs LNHOX rqRttMeas
rsrqB2RttMobility Params
RSRQ B2 1XRTT hysteresis
hysB2ThresholdRsr LNHOX qRtt
rsrqB2RttMobility Params
RSRQ B2 1XRTT report interval
reportIntervalRsr LNHOX qRtt
rsrqB2RttMobility Params
RSRQ B2 HRPD time to trigger
RSRQ B2 HRPD report interval
RSRQ B2 UTRA time to trigger
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information
134
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 83
Descriptions of radio resource management and telecom features
LTE2572 sales information
Product structure class
License control
Application software (ASW)
SW Asset Monitoring
Activated by default No
3.20 LTE2583: Support of High-power UE The LTE2583: Support of High-power UE feature introduces the support of high-power devices for public safety communication (for services such as the police, fire brigade, and ambulance).
3.20.1 LTE2583 benefits The LTE2583: Support of High-power UE feature improves the coverage of an LTE network and reduces network deployment costs.
3.20.2 LTE2583 functional description Currently there is only one power class defined for E-UTRAN UE, power-class-3 (with UL power 23 dBm), for a public safety band (3GPP band 14). This limitation on UL power was a bottleneck to enable higher achievable data rate with better coverage (particularly in rural areas), which is essential to provide the necessary population coverage and UL throughput for public safety purposes. For this reason, the LTE2583: Support of Highpower UE feature has been introduced, and power-class-1 UEs (with UL power target 31 dBm) are supported; this is compliant with 3GPP release 11. Increasing UL power up to 8 dB leads to extended coverage and increases interference in adjacent cells. The LTE2583: Support of High-power UE feature introduces the extended power headroom report (ePHR) for cells supporting high-power UEs. The ePHR is an information element that is contained in a medium access control (MAC) service data unit to indicate the available uplink transmission power resources, including the maximum power the UE can apply to UL transmissions. The eNB uses this information for detecting the high-power UEs. The LTE2583: Support of High-power UE feature does not require a feature flag for activation. The support of high-power UEs is activated by an appropriate O&M parameter setting: •
•
The earfcnUl LNCEL parameter refers by the selected E-UTRA absolute radio frequency channel number in UL to an E-UTRAN band for which power-class-1 is specified by 3GPP (currently only E-UTRAN band 14 supports power-class-1 UEs). The maximum transmission power in the cell is set by the O&M pMaxOwnCell SIB parameter to a value greater than 23 dBm. This parameter is relevant whenever the power condition is propagated during a handover.
Performance measurement To monitor the presence of high-power UEs in the network, the following measurements are introduced: • •
Issue: 01 Draft
Sum of Active UEs with power class 1 Denominator for Active UEs with power class 1
DN09237915
135
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
The counter Sum of Active UEs with power class 1, divided by the counter Denominator for Active UEs with power class 1, provides the average number of active high-power UEs. A UE is active if at least a single non-guaranteed bit rate (non-GBR) data radio bearer (DRB) has been successfully configured for it.
3.20.2.1
Extended power headroom report (ePHR) The LTE2583: Support of High-power UE feature introduces the extended power headroom report (ePHR) for cells supporting high-power UEs. The ePHR is an information element that is contained in a medium access control (MAC) service data unit to indicate the available uplink transmission power resources, including the maximum power the UE can apply to UL transmissions. The eNB uses this information for detecting the high-power UEs. Whenever the cell is configured to maintain high-power UEs (the pMaxOwnCell parameter is greater than 23 dBm for the E-UTRAN band supporting power-class-1 UEs), the UE that is compliant to 3GPP release 11 and higher reports its power condition by means of the extended power headroom report (ePHR). The reporting of power conditions by the ePHR is configured as soon as the UE capabilities are known in the eNB. This means that the ePHR cannot be applied before the Initial Context Setup or Incoming Handover has been completed. The legacy power headroom report (PHR) is applied to the UEs to which the ePHR cannot be applied. Provided the O&M parameter pMaxOwnCell changes after the Initial Context Setup or Incoming Handover has been completed, the initially assigned PHR format is kept. With the introduction of ePHR, the relevant MAC overhead for calculating the transport block size (TBS) varies depending on which format of the power headroom report is applied to the UE. Whereas the legacy PHR consumes a 2-byte-inclusive MAC subheader, the ePHR allocates at least 4 bytes. The ePHR MAC-c is bigger than 4 bytes (Type 1, PCell) only if the ePHR provides the power conditions of a UE which transfers the user data in a UL carrier aggregation mode, and hence the conditions of a PCell and SCell have to be reported.
3.20.2.2
Detection of power-class-1 UEs based on the ePHR The classification of UE power class is based on the maximum power which is available for UL transmissions. UEs that are compliant to 3GPP release 11 specification provide, by means of the extended power headroom report (ePHR), the present power condition (power headroom (PH) information element) and, in addition, the maximum transmission power available for UL transmissions. UEs which provide the present power conditions by means of the legacy PHR are not compliant to 3GPP release 11 and did not belong to the set of power-class-1 UEs. UEs reporting the present power conditions by means of the legacy PHR are always UEs of power-class-3. Once a UE is assigned to the set of power-class-1 UEs, the classification is kept until the UE is released. The UEs which are assigned to the set of power-class-1 UEs are registered by the UL scheduler and are available when required.
3.20.2.3
Joint scheduling of UEs with a different power class within the same cell Even though UEs with different power classes (power-class-1 and 3) remain in the same cell, the UL scheduler must schedule all the UEs jointly. In this context, the scheduling criterion of the interference-aware UL scheduler (IAS) is affected. The scheduling
136
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
criterion which is based on the UE’s transmission power is different for UEs of powerclass-1 and power-class-3 and cannot be deduced simply by evaluating the power headroom reports (PHRs). The main principle of the interference-aware UL scheduler (IAS) is to separate in the UL spectrum the UEs with high inter-cell interference power between adjacent cells. For this purpose, the IAS evaluates the power conditions of the UEs by means of the power headroom report (PHR) and, based on the evaluation, deduces the transmission power spent for the UL transmission the PHR is carried. The higher the UE’s transmission power, the higher the inter-cell interference the UE is contributing.
3.20.3 LTE2583 system impact Interdependencies between features The LTE2583: Support of High-power UE feature impacts the following features: •
LTE619: Interference Aware UL Scheduling Even though UEs with different power classes (power-class-1 and 3) remain in the same cell, the UL scheduler must schedule all the UEs jointly. In this context, the scheduling criterion of the interference-aware UL scheduler (IAS) is affected. The scheduling criterion which is based on the UE’s transmission power is different for UEs of powerclass- 1 and power-class-3 and cannot be deduced simply by evaluating the power headroom reports (PHRs). The main principle of the IAS is to separate in the UL spectrum the UEs with high inter-cell interference power between adjacent cells. For this purpose, the IAS evaluates the power conditions of the UEs by means of the power headroom report (PHR) and, based on the evaluation, deduces the transmission power spent for the UL transmission the PHR is carried. The higher the UE’s transmission power, the higher the inter-cell interference the UE is contributing.
Impact on interfaces The LTE2583: Support of High-power UE feature impacts interfaces as follows: •
Uu interface –
the extended power headroom report (ePHR) has to be supported in the EUTRAN band 14
Impact on network management tools The LTE2583: Support of High-power UE feature has no impact on network management tools. Impact on system performance and capacity The LTE2583: Support of High-power UE feature has no impact on system performance or capacity.
3.20.4 LTE2583 reference data Requirements
Issue: 01 Draft
DN09237915
137
Descriptions of radio resource management and telecom features
Table 84
FDD-LTE16A, Feature Descriptions and Instructions
LTE2583 hardware and software requirements
System release FDD-LTE 16A
Flexi Multiradio BTS not supported
Flexi Zone Controller
OMS
not supported
LTE OMS16A
Flexi Multiradio 10 BTS FL16A UE
Flexi Zone Micro BTS not supported
NetAct
Flexi Zone Access Point not supported
MME
3GPP R11 UE NetAct 16.8 capabilities
SAE GW
support not required
support not required
BTS faults and reported alarms There are no faults related to the LTE2583: Support of High-power UE feature. Commands There are no commands related to the LTE2583: Support of High-power UE feature. Measurements and counters Table 85
New counters introduced by LTE2583
Counter ID
Counter name
Measurement
M8051C Sum of Active UEs with power 94 class 1
LTE Cell Load
M8051C Denominator for Active UEs 95 with power class 1
LTE Cell Load
For counter descriptions, see LTE Performance Measurements. Key performance indicators There are no key performance indicators related to the LTE2583: Support of High-power UE feature. Parameters Table 86
Parameters related to the LTE2583 Full name
Abbreviated name
EARFCN uplink
Table 87
earfcnUL
Managed object LNCEL
Parent structure -
Parameters modified by LTE2583 Full name
Abbreviated name
Max. uplink transmission power own cell
pMaxOwnCell
Managed object SIB
Parent structure -
For parameter descriptions, see FDD-LTE BTS Parameters. Sales information
138
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 88
Descriptions of radio resource management and telecom features
LTE2583 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default No
3.21 LTE2601: CA-aware Idle Mode Load Balancing The LTE2601: CA-aware Idle Mode Load Balancing feature introduces a carrieraggregation-based (CA) mechanism for idle mode load balancing. The new mechanism improves an idle mode load balancing method as follows: • •
Differentiating CA-capable UEs from the ones that are not CA capable Differentiating CA-capable UEs that support various CA component carrier (CC) combinations, that is, 2CC, 3CC, 4CC, and 5CC
3.21.1 LTE2601 benefits The LTE2601: CA-aware Idle Mode Load Balancing feature improves the peak rates by ensuring that carrier-aggregation-capable (CA) user equipment (UE) uses CA before it goes to the RRC connected mode.
3.21.2 LTE2601 functional description Idle mode overview The idle mode is used for saving a power during inactivity of a user equipment (UE). In this mode, there is no RRC connection established and only the following services are available: • • • •
selection of public land mobile network (PLMN) cell selection and reselection location registration reception of system information
If the UE gets an incoming data or a call, it is able to establish the RRC connection and move to the RRC connected state; consequently, the data transfer or a voice call is possible. Load balance in the idle mode As there can be a lot of UEs in the RRC idle mode, a mechanism of balancing the load is introduced. The eNB supports adding an IdleModeMobilityControlInfo information element (IE) to the RRC: RRC Connection Release message for intraLTE and inter-RAT load balancing targets. This support is offered for an operatorconfigurable percentage of UEs with RRC: RRC Connection Release without redirection. The eNB uses a weighted round robin algorithm for selecting targets for load balancing, which are sent to the UE. The LTE2601: CA-aware Idle Mode Load Balancing enhances that algorithm with a carrier-aggregation-based (CA) mechanism. LTE-Advanced carrier aggregation overview
Issue: 01 Draft
DN09237915
139
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
Carrier aggregation is used in LTE-Advanced in order to increase the bandwidth and data rate. Each aggregated carrier is referred to as a component carrier (CC). The component carrier can have a bandwidth of up to 20 MHz, and a maximum of five component carriers can be aggregated. The individual component carriers can also be of different bandwidths. There are several features which support different carrier aggregation scenarios.
g
Note: Aggregation of carriers can be performed only for certain band combinations. To make carrier aggregation possible, a dual-band configuration is needed. The figure below presents an overview of the carrier aggregation functionality for two bands with the same frequency. Figure 12 BandB
BandA
Inter-band carrier aggregation example Upto10MHz
carrier aggregation
Upto 150Mbps
Upto10MHz
CA-based idle mode load balancing for intra-LTE target selection The carrier-aggregation-based (CA) idle mode mobility is achieved by introducing dedicated CA-specific weights. The weights are used to determine dedicated cell reselection priorities for the CA-capable user equipment (UE). Moreover, the CA-specific weights and dedicated priorities are differentiated depending on the UE capabilities, that is, depending on the maximum number of supported intra-LTE CA component carriers (CCs): 2CC, 3CC, 4CC, and 5CC. For example, there are different reselection priorities defined for the 2CC UE (targeting 20 + 20 MHz CA) than for the 3CC UE (targeting 10 + 15 + 20 MHz CA). The CA-based algorithm for idle mode load balancing optimizes the intra-LTE primary target selection for the highest possible CC combination supported by the UE. If the UE does not support that combination, an eNB tries to assign a primary target configured for a lower CC combination. When the primary target is found within a specific CC combination, then also the intra-LTE secondary target of the same CC combination is used. Otherwise, if the primary target is empty, then the intra-LTE secondary target of the lowest possible CC combination configured by the operator is used.
g
Note: For inter-RAT secondary targets and a non-CA-capable UEs, the parameters defined within the LTE1677: Idle Mode Mobility Balancing Extensions and the LTE2166: Support of Dedicated Idle Mode Mobility Priorities features are used for all the idle mode load balancing algorithms. New parameters The LTE2601: CA-aware Idle Mode Load Balancing feature introduces the following parameters for configuring the CA-based idle mode load balancing for the CA-capable UEs: •
•
140
A percentage of UEs for a CA-based idle mode load balancing (a Percentage of
UE for idle mode load balancing for CA capable UEs (idleLBPercCaUe) parameter) Weight factors for all inter-LTE target frequencies: 2CC, 3CC, 4CC, and 5CC (a set of Cell reselection weight factor for idle mode load balancing for xCC CA UEs (idleLBCelResWeightxCC) parameters is defined)
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
•
Descriptions of radio resource management and telecom features
Dedicated cell reselection priorities for all inter-LTE target frequencies: 2CC, 3CC, 4CC, and 5CC (a set of xxx cell carrier freq prio for idle mode load balancing for xCC CA UE (idleLBxxxCelResPrioxCC) parameters is defined for both serving cell and EUTRA) A load threshold for an idle mode load balancing for CA-capable UEs (the Idle
mode load balancing capacity threshold for CA capable UEs (idleLBCapThreshCaUe) parameter)
3.21.3 LTE2601 system impact Interdependencies between features The LTE2601: CA-aware Idle Mode Load Balancing feature is impacted by the following feature: •
LTE1677: Idle Mode Mobility Balancing Extensions If the LTE1677: Idle Mode Mobility Balancing Extensions feature is enabled, a noncarrier-aggregation-capable (CA) user equipment (UEs) and CA-capable UEs are handled separately by dedicated idle mode load balancing mechanisms and according to the dedicated parameter settings.
The LTE2601: CA-aware Idle Mode Load Balancing feature impacts the following features: •
•
•
LTE2166: Support of Dedicated Idle Mode Mobility Priorities The LTE2166: Support of Dedicated Idle Mode Mobility Priorities feature can be enabled if the LTE2601: CA-aware Idle Mode Load Balancing feature is used without activation of the LTE1677: Idle Mode Mobility Balancing Extensions feature. In that scenario, the LTE2601: CA-aware Idle Mode Load Balancing feature-specific method for target frequency selection is used. LTE2050: Load-triggered Idle Mode Load Balancing The LTE2050: Load triggered Idle Mode Load Balancing feature is used together with the LTE2601: CA-aware Idle Mode Load Balancing feature if the idleLBCapThreshCaUe (Idle mode load balancing capacity threshold for CA capable UEs) LNCEL parameter is set to a value other than 100. In that scenario, an idle mode load balancing is done according to the LTE2050: Load triggered Idle Mode Load Balancing feature-related load threshold settings. LTE2051: Measurement-based Idle Mode Load Balancing The LTE2051: Measurement-based Idle Mode Load Balancing feature can be enabled if the LTE2601: CA-aware Idle Mode Load Balancing feature is used without activation of the LTE1677: Idle Mode Mobility Balancing Extensions feature. In that scenario, and if the primary target is empty, only the information about secondary targets is sent to the user equipment (UE).
Impact on interfaces The LTE2601: CA-aware Idle Mode Load Balancing feature has no impact on interfaces. Impact on network management tools The LTE2601: CA-aware Idle Mode Load Balancing feature has no impact on network management tools. Impact on system performance and capacity The LTE2601: CA-aware Idle Mode Load Balancing feature has no impact on system performance or capacity.
Issue: 01 Draft
DN09237915
141
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
3.21.4 LTE2601 reference data Requirements Table 89
LTE2601 hardware and software requirements
System release FDD-LTE16A Flexi Zone Controller FL16A
Flexi Multiradio BTS FL16A OMS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL16A
UE
LTE OMS16A
3GPP R8
Flexi Zone Micro BTS FL16A
NetAct
FL16A
MME
NetAct 16.8
Flexi Zone Access Point
SAE GW
Support not required
Support not required
Alarms There are no alarms related to the LTE2601: CA-aware Idle Mode Load Balancing feature. BTS faults and reported alarms There are no faults related to the LTE2601: CA-aware Idle Mode Load Balancing feature. Commands There are no commands related to the LTE2601: CA-aware Idle Mode Load Balancing feature. Measurements and counters There are no measurements or counters related to the LTE2601: CA-aware Idle Mode Load Balancing feature. Key performance indicators There are no key performance indicators related to the LTE2601: CA-aware Idle Mode Load Balancing feature. Parameters Table 90
New parameters introduced by LTE2601 Full name
Abbreviated name
Parent structure
LNBTS
-
idleLBCapThreshCa LNCEL Ue
-
Serving cell carrier idleLBCellReSelPr LNCEL freq prio for idle mode io2CC load balancing for 2CC CA UEs
-
Serving cell carrier idleLBCellReSelPr LNCEL freq prio for idle mode io3CC load balancing for 3CC CA UEs
-
Serving cell carrier idleLBCellReSelPr LNCEL freq prio for idle mode io4CC
-
Activation of idle mode actIdleLBCaAware load balancing for CA capable UEs Idle mode load balancing capacity threshold for CA capable UEs
142
Managed object
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 90
Descriptions of radio resource management and telecom features
New parameters introduced by LTE2601 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
load balancing for 4CC CA UEs Serving cell carrier idleLBCellReSelPr LNCEL freq prio for idle mode io5CC load balancing for 5CC CA UEs
-
Cell reselection weight idleLBCelResWeigh LNCEL factor for idle mode t2CC load balancing for 2CC CA UEs
-
Cell reselection weight idleLBCelResWeigh LNCEL factor for idle mode t3CC load balancing for 3CC CA UEs
-
Cell reselection weight idleLBCelResWeigh LNCEL factor for idle mode t4CC load balancing for 4CC CA UEs
-
Cell reselection weight idleLBCelResWeigh LNCEL factor for idle mode t5CC load balancing for 5CC CA UEs
-
LNCEL
-
Percentage of UE for idle mode load balancing for CA capable UEs
Issue: 01 Draft
idleLBPercCaUe
EUTRA carrier freq prio idleLBEutCelResPr IRFIM for idle mode load io2CC balancing for 2CC CA UEs
-
EUTRA carrier freq prio idleLBEutCelResPr IRFIM for idle mode load io3CC balancing for 3CC CA UEs
-
EUTRA carrier freq prio idleLBEutCelResPr IRFIM for idle mode load io4CC balancing for 4CC CA UEs
-
EUTRA carrier freq prio idleLBEutCelResPr IRFIM for idle mode load io5CC balancing for 5CC CA UEs
-
EUTRA carrier weight factor for idle mode load balancing for 2CC CA UEs
idleLBEutCelResWe IRFIM ight2CC
-
EUTRA carrier weight factor for idle mode load balancing for 3CC CA UEs
idleLBEutCelResWe IRFIM ight3CC
-
DN09237915
143
Descriptions of radio resource management and telecom features
Table 90
FDD-LTE16A, Feature Descriptions and Instructions
New parameters introduced by LTE2601 (Cont.) Full name
Abbreviated name
Parent structure
EUTRA carrier weight factor for idle mode load balancing for 4CC CA UEs
idleLBEutCelResWe IRFIM ight4CC
-
EUTRA carrier weight factor for idle mode load balancing for 5CC CA UEs
idleLBEutCelResWe IRFIM ight5CC
-
Percentage of UE for idle mode load balancing for CA capable UEs
idleLBPercCaUe
MODPR
-
Percentage of UE for idle mode load balancing for CA capable UEs
idleLBPercCaUe
MOPR
-
Table 91
Existing parameters related to LTE2601 Full name
Abbreviated name
Managed object
Parent structure
Activation of idle mode actIdleLB load balancing (IdleLB)
LNBTS
-
Activate measurementbased idle mode load balancing
actMeasBasedIMLB
LNBTS
-
Activate selective mobility profiles
actSelMobPrf
LNBTS
-
Cell resource sharing mode
cellResourceShari LNCEL ngMode
-
Serv cell carr freq idleLBCellReSelPr LNCEL prio for idle mode load io balancing
-
LNCEL
-
Cell reselection method targetSelMethod for idle mode load balancing
LNCEL
-
CDMA2000 HRPD band class list
hrpdBdClList
CDFIM
-
CDMA2000 1xRTT band class list
rttBdClList
CDFIM
-
Intra- and inter-freq. load bal. common load settings
144
Managed object
loadSettings
GERAN carrier freq prio idleLBGeranCelRes GNFL for idle mode load Prio balancing
-
EUTRA carrier freq prio idleLBEutCelResPr IRFIM for idle mode load io balancing
-
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 91
Descriptions of radio resource management and telecom features
Existing parameters related to LTE2601 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
UFFIM
-
CDMA HRPD band list for cdmaHrpdBdClL idle mode load balancing
MODIMP
-
CDMA 1xRTT band list for idle mode load balancing
cdmaRttBdClL
MODIMP
-
EUTRA carrier list for idle mode load balancing
dlCarFrqEutL
MODIMP
-
GERAN band parameters for idle mode load balancing
geranCarFrqBd
MODIMP
-
UTRA FDD carrier list for idle mode load balancing
utrFddCarFrqL
MODIMP
-
CDMA HRPD band list for cdmaHrpdBdClL idle mode load balancing
MOIMP
-
CDMA 1xRTT band list for idle mode load balancing
cdmaRttBdClL
MOIMP
-
EUTRA carrier list for idle mode load balancing
dlCarFrqEutL
MOIMP
-
GERAN band parameters for idle mode load balancing
geranCarFrqBd
MOIMP
-
UTRA FDD carrier list for idle mode load balancing
utrFddCarFrqL
MOIMP
-
List of UTRA FDD carrier frequencies
utrFddCarFrqL
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 92
LTE2601 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
3.22 LTE2611: Introduction of Public Safety Specific QCI Bearers Benefits, functionality, system impact, reference data, instructions of the feature
Issue: 01 Draft
DN09237915
145
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
The LTE2611: Introduction of Public Safety Specific QCI Bearers feature introduces new evolved packet system (EPS) unicast QoS Class Identifier (QCI) bearers to support public safety (PS) push-to-talk (PTT) and data services.
3.22.1 LTE2611 benefits The LTE2611: Introduction of Public Safety Specific QCI Bearers feature deploys unicast EPS bearers with optimized QCI support to enable the operator to support PS PTT and data services.
3.22.2 LTE2611 functional description The LTE2611: Introduction of Public Safety Specific QCI Bearers feature enables PTT communication service to support mission-critical applications for PS and commercial applications with faster setup times and priority handling. The PTT service provides an arbitration method where two or more users can engage in communication. This differs from the regular voice over LTE (VoLTE). The PTT service allows users to request for a permission to talk (transmit voice or audio) and provides a mechanism to decide between requests that are in contention (for example, floor control). This feature establishes, maintains, and terminates communication paths among PTT users. The LTE2611: Introduction of Public Safety Specific QCI Bearers feature supports the following standardized QCI bearer values (For more details, see 3GPP Release 12 TS 23.203.): • • • •
QCI65 (mission-critical user plane PTT voice) QCI66 (non-mission-critical user plane PTT voice) QCI69 (mission-critical delay sensitive signaling) QCI70 (mission-critical data)
The new QCIs are supported within the existing quality of service (QoS) and service differentiation framework. The QCI69 and QCI70 are handled with proportional scheduling based on an operator-configurable weight and with no delay based on the scheduling needs to be introduced. The following deployment of the discontinuous reception (DRX) profiles with operatorconfigurable priorities are recommended for PS QCIs: • • • •
QCI65: DRX profiles 1 and 2 QCI66: DRX profiles 1 and 2 QCI69: DRX profiles 1, 2, and 3 QCI70: DRX profiles 1, 3, 4, and 5
The same packet data convergence protocol (PDCP) and radio link control (RLC) characteristics in QCI1 are used for PTT voice QCI65 and QCI66 bearers. The range of inactivity timer for calls with QCI69 bearer is extended to ensure faster call setup. The value of the inactivity timer is operator-configurable and ranges up to 30 minutes.
g
146
Note: The default value of the inactivity timer is increased with this feature. Therefore, the battery life and the eNB capacity of the UEs might be affected because of the extended inactivity timer.
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
The parameters for radio link failure and re-establishment control with established PTT voice QCI bearers (T310 and N310) are optimized to ensure faster re-establishment.
g
Note: Transmission time interval (TTI) bundling can be activated or deactivated individually for each PS QCI. The LTE2611: Introduction of Public Safety Specific QCI Bearers feature deploys counters as specified in the LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles and LTE2766: Counter Profiling per Service (QCI) features.
3.22.3 LTE2611 system impact LTE2611: Introduction of Public Safety Specific QCI Bearers impact on features, interfaces, and system performance and capacity Interdependencies between features The following features must be activated before activating the LTE2611: Introduction of Public Safety Specific QCI Bearers feature: • • • • •
LTE7: Support of Multiple EPS Bearers LTE9: Service Differentiation LTE10: EPS Bearers for Conversational Voice LTE497: Smart Admission Control LTE534: ARP-based Admission Control for E-RABs
The LTE2611: Introduction of Public Safety Specific QCI Bearers feature is dependent on the following features: • • • • • • •
g
Note: These features are designed for the QCI configuration framework. A consistency check and an independent feature flag are required to enable them. •
LTE2559: ARP-based Partial Admission Control for Handover The user equipment (UE) with PS bearers and higher address resolution protocol (ARP) values can benefit from this feature because it increases the probability of a successful handover of the E-UTRAN radio access bearers (E-RABs).
•
LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles LTE2766: Counter Profiling per Service (QCI)
•
g
Note: These features reuse and support all the counters that are relevant to QCI65, QCI66, QCI69, and QCI70 bearers. • •
Issue: 01 Draft
LTE11: Robust Header Compression LTE42: DRX in RRC Connected Mode LTE496: Support of QCI Classes 2, 3, and 4 LTE 519: eRAB Modification LTE1321: eRAB Modification - GBR LTE1042: Nominal Bitrate for Non-GBR Bearers LTE1569: QCI1 Specific RLF and Re-establishment Control
LTE2465: CSG Cell Support LTE1723: S1-based Handover towards Home eNodeB
DN09237915
147
Descriptions of radio resource management and telecom features
• •
g
FDD-LTE16A, Feature Descriptions and Instructions
LTE2351: S1-based Handover towards CSG Cells LTE1442: Open-access Home eNodeB Mobility Note: The LTE2611: Introduction of Public Safety Specific QCI Bearers feature has to block handovers to the caller subscriber geography (CSG) or home evolved Node B (eNB) if there are any PS bearers that exist for the UE.
• •
g
LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz LTE2531: FDD Downlink Carrier Aggregation 4 CC Note: The QCI70 bearer configuration can have an optimized RLC setting when configured with RLC acknowledged mode (AM) for these carrier aggregation (CA) features.
Impact on interfaces The LTE2611: Introduction of Public Safety Specific QCI Bearers feature affects interfaces as follows: •
S1-AP – –
•
Setup of multiple E-RABs to include new QCI values (QCI65, QCI66, QCI69, and QCI70) QCI modifications and switching support between QCI5 and QCI69
X2-AP –
Handover support of multiple E-RABs to include new QCI values (QCI65, QCI66, QCI69, and QCI70)
Impact on network management tools The LTE2611: Introduction of Public Safety Specific QCI Bearers feature has no impact on network management tools. Impact on system performance and capacity When the LTE2611: Introduction of Public Safety Specific QCI Bearers feature is activated, the selection of the QCI priority values influence the congestion handling within the radio access network (RAN). Congestion handling might be configured based on the QCI priority or based on the ARP priority which the admission control also uses. To ensure that the PS bearers are handled accordingly during congestion, they are expected to have higher priority as compared to the normal UEs. The operator must be careful with the ARP setting when congestion handling is based on ARP. The ARP value assigned to the PS bearer reflects the QCI priority so that the admission control allows new incoming PS bearers. The eNB must meet the performance requirements from the standard specification since the standardized QCIs carry a specific packet delay budget and packet error loss rate.
g
Note: The existing bearer-handover interruption time requirements also apply to these QCIs. Because of high uncertainty on the core network architecture, the mission-critical pushto-talk (MCPTT)-related requirements are omitted. The specific bearer QCI packet loss rate and delay budget requirements contributes to the eNB end-to-end quality.
148
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
The control plane latency must be considered given the PS context of the new bearers. The MCPTT call setup time required is less than 300 ms; this is the sum of all delayed components from various network entities. The eNB contribution is limited to service request and bearer setup call flow latencies. They form the eNB latency budget within the MCPTT call setup time. PTT (QCI65 or QCI66) mirrors VoLTE. The existing VoLTE call setup success and retainability requirements are applied. For mission-critical data calls (QCI69), the existing E-RAB setup success and retainability requirements are applied.
3.22.4 LTE2611 reference data LTE2611: Introduction of Public Safety Specific QCI Bearers requirements, measurements and counters, parameters, and sales information Requirements Table 93
LTE2611 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
Not supported
UE
LTE OMS16A
Flexi Zone Micro BTS FL16A
NetAct
3GPP R12 UE NetAct 16.8 capabilities
Flexi Zone Access Point FL16A
MME Support not required
SAE GW Support not required
Alarms There are no alarms related to the LTE2611: Introduction of Public Safety Specific QCI Bearers feature. Commands There are no commands related to the LTE2611: Introduction of Public Safety Specific QCI Bearers feature. Measurements and counters Table 94 Counter ID
New counters introduced by LTE2611 Counter name
M8013C Number of UEs released due to 74 expiration of Public Safety inactivity timer
Measurement LTE UE State
Key performance indicators There are no key performance indicators related to the LTE2611: Introduction of Public Safety Specific QCI Bearers feature. Parameters
Issue: 01 Draft
DN09237915
149
Descriptions of radio resource management and telecom features
Table 95
FDD-LTE16A, Feature Descriptions and Instructions
New parameters introduced by LTE2611 Full name
150
Abbreviated name
Managed object
Parent structure
Activate public safety bearers
actPubSafetyBearers
LNBTS
-
QCI translation table QCI 65
qciTab65
LNBTS
-
Delay target
delayTarget
LNBTS
qciTab65
DRX profile index
drxProfileIndex
LNBTS
qciTab65
DSCP
dscp
LNBTS
qciTab65
Enforce TTI bundling
enforceTtiBundling
LNBTS
qciTab65
Logical channel group identifier
lcgid
LNBTS
qciTab65
Maximum GBR downlink
maxGbrDl
LNBTS
qciTab65
Maximum GBR uplink
maxGbrUl
LNBTS
qciTab65
PDCP profile index
pdcpProfIdx
LNBTS
qciTab65
Priority
prio
LNBTS
qciTab65
QCI
qci
LNBTS
qciTab65
QCI support
qciSupp
LNBTS
qciTab65
Resource type
resType
LNBTS
qciTab65
RLC mode
rlcMode
LNBTS
qciTab65
RLC profile index
rlcProfIdx
LNBTS
qciTab65
Scheduling bucket size duration
schedulBSD
LNBTS
qciTab65
Scheduling priority
schedulPrio
LNBTS
qciTab65
QCI translation table QCI 66
qciTab66
LNBTS
-
Delay target
delayTarget
LNBTS
qciTab66
DRX profile index
drxProfileIndex
LNBTS
qciTab66
DSCP
dscp
LNBTS
qciTab66
Enforce TTI bundling
enforceTtiBundling
LNBTS
qciTab66
Logical channel group identifier
lcgid
LNBTS
qciTab66
Maximum GBR downlink
maxGbrDl
LNBTS
qciTab66
Maximum GBR uplink
maxGbrUl
LNBTS
qciTab66
PDCP profile index
pdcpProfIdx
LNBTS
qciTab66
Priority
prio
LNBTS
qciTab66
QCI
qci
LNBTS
qciTab66
QCI support
qciSupp
LNBTS
qciTab66
Resource type
resType
LNBTS
qciTab66
RLC mode
rlcMode
LNBTS
qciTab66
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 95
New parameters introduced by LTE2611 (Cont.) Full name
Issue: 01 Draft
Descriptions of radio resource management and telecom features
Abbreviated name
Managed object
Parent structure
RLC profile index
rlcProfIdx
LNBTS
qciTab66
Scheduling bucket size duration
schedulBSD
LNBTS
qciTab66
Scheduling priority
schedulPrio
LNBTS
qciTab66
QCI translation table QCI 69
qciTab69
LNBTS
-
DRX profile index
drxProfileIndex
LNBTS
qciTab69
DSCP
dscp
LNBTS
qciTab69
Enforce TTI bundling
enforceTtiBundling
LNBTS
qciTab69
Logical channel group identifier
lcgid
LNBTS
qciTab69
PDCP profile index
pdcpProfIdx
LNBTS
qciTab69
Priority
prio
LNBTS
qciTab69
QCI
qci
LNBTS
qciTab69
QCI support
qciSupp
LNBTS
qciTab69
Resource type
resType
LNBTS
qciTab69
RLC mode
rlcMode
LNBTS
qciTab69
RLC profile index
rlcProfIdx
LNBTS
qciTab69
Scheduling bucket size duration
schedulBSD
LNBTS
qciTab69
Scheduling priority
schedulPrio
LNBTS
qciTab69
QCI Translation Table QCI 70
qciTab70
LNBTS
-
DRX profile index
drxProfileIndex
LNBTS
qciTab70
DSCP
dscp
LNBTS
qciTab70
Enforce TTI bundling
enforceTtiBundling
LNBTS
qciTab70
Logical channel group identifier
lcgid
LNBTS
qciTab70
Nominal Bit Rate Downlink
nbrDl
LNBTS
qciTab70
Nominal Bit Rate Uplink nbrUl
LNBTS
qciTab70
PDCP profile index
pdcpProfIdx
LNBTS
qciTab70
Priority
prio
LNBTS
qciTab70
QCI
qci
LNBTS
qciTab70
QCI support
qciSupp
LNBTS
qciTab70
Resource type
resType
LNBTS
qciTab70
RLC Mode
rlcMode
LNBTS
qciTab70
RLC profile index
rlcProfIdx
LNBTS
qciTab70
DN09237915
151
Descriptions of radio resource management and telecom features
Table 95
FDD-LTE16A, Feature Descriptions and Instructions
New parameters introduced by LTE2611 (Cont.) Full name
Abbreviated name
Parent structure
RLC profile index for 3 rlcProfIdx3cc CC CA
LNBTS
qciTab70
RLC profile index for 4 rlcProfIdx4cc5cc CC and 5CC CA
LNBTS
qciTab70
Scheduling bucket size duration
schedulBSD
LNBTS
qciTab70
Scheduling priority
schedulPrio
LNBTS
qciTab70
Inactivity timer for public safety bearer
inactivityTimerPubS afety
LNCEL
-
N310 for QCI65/66
n310PubSafety
LNCEL
-
T310 for QCI65/66
t310PubSafety
LNCEL
-
Table 96
Existing parameters related to LTE2611 Full name
152
Managed object
Abbreviated name
Managed object
Parent structure
Activate support of conversational voice bearer
actConvVoice
LNBTS
-
Activate E-RAB modification
actERabModify
LNBTS
-
Activate PDCP robust header compression
actPdcpRohc
LNBTS
-
QCI translation table QCI 1
qciTab1
LNBTS
-
Delay target
delayTarget
LNBTS
qciTab1
DRX profile index
drxProfileIndex
LNBTS
qciTab1
DSCP
dscp
LNBTS
qciTab1
Enforce TTI bundling
enforceTtiBundling
LNBTS
qciTab1
Logical channel group identifier
lcgid
LNBTS
qciTab1
Maximum GBR downlink
maxGbrDl
LNBTS
qciTab1
Maximum GBR uplink
maxGbrUl
LNBTS
qciTab1
PDCP profile index
pdcpProfIdx
LNBTS
qciTab1
Priority
prio
LNBTS
qciTab1
QCI
qci
LNBTS
qciTab1
QCI support
qciSupp
LNBTS
qciTab1
Resource type
resType
LNBTS
qciTab1
RLC mode
rlcMode
LNBTS
qciTab1
RLC profile index
rlcProfIdx
LNBTS
qciTab1
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 96
Existing parameters related to LTE2611 (Cont.) Full name
Issue: 01 Draft
Descriptions of radio resource management and telecom features
Abbreviated name
Managed object
Parent structure
Scheduling bucket size duration
schedulBSD
LNBTS
qciTab1
Scheduling priority
schedulPrio
LNBTS
qciTab1
QCI translation table QCI 2
qciTab2
LNBTS
-
Delay target
delayTarget
LNBTS
qciTab2
DRX profile index
drxProfileIndex
LNBTS
qciTab2
DSCP
dscp
LNBTS
qciTab2
Enforce TTI bundling
enforceTtiBundling
LNBTS
qciTab2
L2 overhead factor GBR DL
l2OHFactorDL
LNBTS
qciTab2
L2 overhead factor GBR UL
l2OHFactorUL
LNBTS
qciTab2
Logical channel group identifier
lcgid
LNBTS
qciTab2
Maximum GBR downlink
maxGbrDl
LNBTS
qciTab2
Maximum GBR uplink
maxGbrUl
LNBTS
qciTab2
PDCP profile index
pdcpProfIdx
LNBTS
qciTab2
Priority
prio
LNBTS
qciTab2
QCI
qci
LNBTS
qciTab2
QCI support
qciSupp
LNBTS
qciTab2
Resource type
resType
LNBTS
qciTab2
RLC mode
rlcMode
LNBTS
qciTab2
RLC profile index
rlcProfIdx
LNBTS
qciTab2
Scheduling bucket size duration
schedulBSD
LNBTS
qciTab2
Scheduling priority
schedulPrio
LNBTS
qciTab2
QCI translation table QCI 3
qciTab3
LNBTS
-
Delay target
delayTarget
LNBTS
qciTab3
DRX profile index
drxProfileIndex
LNBTS
qciTab3
DSCP
dscp
LNBTS
qciTab3
Enforce TTI bundling
enforceTtiBundling
LNBTS
qciTab3
L2 overhead factor GBR DL
l2OHFactorDL
LNBTS
qciTab3
L2 overhead factor GBR UL
l2OHFactorUL
LNBTS
qciTab3
Logical channel group identifier
lcgid
LNBTS
qciTab3
DN09237915
153
Descriptions of radio resource management and telecom features
Table 96
FDD-LTE16A, Feature Descriptions and Instructions
Existing parameters related to LTE2611 (Cont.) Full name
154
Abbreviated name
Managed object
Parent structure
Maximum GBR downlink
maxGbrDl
LNBTS
qciTab3
Maximum GBR uplink
maxGbrUl
LNBTS
qciTab3
PDCP profile index
pdcpProfIdx
LNBTS
qciTab3
Priority
prio
LNBTS
qciTab3
QCI
qci
LNBTS
qciTab3
QCI support
qciSupp
LNBTS
qciTab3
Resource type
resType
LNBTS
qciTab3
RLC mode
rlcMode
LNBTS
qciTab3
RLC profile index
rlcProfIdx
LNBTS
qciTab3
Scheduling bucket size duration
schedulBSD
LNBTS
qciTab3
Scheduling priority
schedulPrio
LNBTS
qciTab3
QCI translation table QCI 4
qciTab4
LNBTS
-
Delay target
delayTarget
LNBTS
qciTab4
DRX profile index
drxProfileIndex
LNBTS
qciTab4
DSCP
dscp
LNBTS
qciTab4
Enforce TTI bundling
enforceTtiBundling
LNBTS
qciTab4
L2 overhead factor GBR DL
l2OHFactorDL
LNBTS
qciTab4
L2 overhead factor GBR UL
l2OHFactorUL
LNBTS
qciTab4
Logical channel group identifier
lcgid
LNBTS
qciTab4
Maximum GBR downlink
maxGbrDl
LNBTS
qciTab4
Maximum GBR uplink
maxGbrUl
LNBTS
qciTab4
PDCP profile index
pdcpProfIdx
LNBTS
qciTab4
Priority
prio
LNBTS
qciTab4
QCI
qci
LNBTS
qciTab4
QCI support
qciSupp
LNBTS
qciTab4
Resource type
resType
LNBTS
qciTab4
RLC mode
rlcMode
LNBTS
qciTab4
RLC profile index
rlcProfIdx
LNBTS
qciTab4
Scheduling bucket size duration
schedulBSD
LNBTS
qciTab4
Scheduling priority
schedulPrio
LNBTS
qciTab4
QCI translation table QCI 5
qciTab5
LNBTS
-
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 96
Existing parameters related to LTE2611 (Cont.) Full name
Issue: 01 Draft
Descriptions of radio resource management and telecom features
Abbreviated name
Managed object
Parent structure
DRX profile index
drxProfileIndex
LNBTS
qciTab5
DSCP
dscp
LNBTS
qciTab5
Enforce TTI bundling
enforceTtiBundling
LNBTS
qciTab5
Logical channel group identifier
lcgid
LNBTS
qciTab5
Nominal bit rate downlink
nbrDl
LNBTS
qciTab5
Nominal bit rate uplink nbrUl
LNBTS
qciTab5
PDCP profile index
pdcpProfIdx
LNBTS
qciTab5
Priority
prio
LNBTS
qciTab5
QCI
qci
LNBTS
qciTab5
QCI support
qciSupp
LNBTS
qciTab5
Resource type
resType
LNBTS
qciTab5
RLC mode
rlcMode
LNBTS
qciTab5
RLC profile index
rlcProfIdx
LNBTS
qciTab5
Scheduling bucket size duration
schedulBSD
LNBTS
qciTab5
Scheduling priority
schedulPrio
LNBTS
qciTab5
Scheduling type
schedulType
LNBTS
qciTab5
Scheduling weight
schedulWeight
LNBTS
qciTab5
QCI translation table QCI 6
qciTab6
LNBTS
-
DRX profile index
drxProfileIndex
LNBTS
qciTab6
DSCP
dscp
LNBTS
qciTab6
Enforce TTI bundling
enforceTtiBundling
LNBTS
qciTab6
Logical channel group identifier
lcgid
LNBTS
qciTab6
Nominal bit rate downlink
nbrDl
LNBTS
qciTab6
Nominal bit rate uplink nbrUl
LNBTS
qciTab6
PDCP profile index
pdcpProfIdx
LNBTS
qciTab6
Priority
prio
LNBTS
qciTab6
QCI
qci
LNBTS
qciTab6
QCI support
qciSupp
LNBTS
qciTab6
Resource type
resType
LNBTS
qciTab6
RLC mode
rlcMode
LNBTS
qciTab6
RLC profile index
rlcProfIdx
LNBTS
qciTab6
DN09237915
155
Descriptions of radio resource management and telecom features
Table 96
FDD-LTE16A, Feature Descriptions and Instructions
Existing parameters related to LTE2611 (Cont.) Full name
156
Abbreviated name
Managed object
Parent structure
RLC profile index for 3 rlcProfIdx3cc CC CA
LNBTS
qciTab6
Scheduling bucket size duration
schedulBSD
LNBTS
qciTab6
Scheduling priority
schedulPrio
LNBTS
qciTab6
Scheduling weight
schedulWeight
LNBTS
qciTab6
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
PDCP profile index
pdcpProfIdx
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
RLC profile index for 3 rlcProfIdx3cc CC CA
LNBTS
qciTab7
Scheduling bucket size duration
schedulBSD
LNBTS
qciTab7
Scheduling priority
schedulPrio
LNBTS
qciTab7
Scheduling weight
schedulWeight
LNBTS
qciTab7
QCI translation table QCI 8
qciTab8
LNBTS
-
DRX profile index
drxProfileIndex
LNBTS
qciTab8
DSCP
dscp
LNBTS
qciTab8
Enforce TTI bundling
enforceTtiBundling
LNBTS
qciTab8
Logical channel group identifier
lcgid
LNBTS
qciTab8
Nominal bit rate downlink
nbrDl
LNBTS
qciTab8
Nominal bit rate uplink nbrUl
LNBTS
qciTab8
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 96
Existing parameters related to LTE2611 (Cont.) Full name
Issue: 01 Draft
Descriptions of radio resource management and telecom features
Abbreviated name
Managed object
Parent structure
PDCP profile index
pdcpProfIdx
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
RLC profile index for 3 rlcProfIdx3cc CC CA
LNBTS
qciTab8
Scheduling bucket size duration
schedulBSD
LNBTS
qciTab8
Scheduling priority
schedulPrio
LNBTS
qciTab8
Scheduling weight
schedulWeight
LNBTS
qciTab8
QCI translation table QCI 9
qciTab9
LNBTS
-
DRX profile index
drxProfileIndex
LNBTS
qciTab9
DSCP
dscp
LNBTS
qciTab9
Enforce TTI bundling
enforceTtiBundling
LNBTS
qciTab9
Logical channel group identifier
lcgid
LNBTS
qciTab9
Nominal bit rate downlink
nbrDl
LNBTS
qciTab9
Nominal bit rate uplink nbrUl
LNBTS
qciTab9
PDCP profile index
pdcpProfIdx
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
RLC profile index for 3 rlcProfIdx3cc CC CA
LNBTS
qciTab9
Scheduling bucket size duration
schedulBSD
LNBTS
qciTab9
Scheduling priority
schedulPrio
LNBTS
qciTab9
Scheduling weight
schedulWeight
LNBTS
qciTab9
QCI translation table operator specific QCIs
qciTabOperator
LNBTS
-
DN09237915
157
Descriptions of radio resource management and telecom features
Table 96
FDD-LTE16A, Feature Descriptions and Instructions
Existing parameters related to LTE2611 (Cont.) Full name
158
Abbreviated name
Managed object
Parent structure
Counter group
counterGroup
LNBTS
qciTabOperator
Delay target
delayTarget
LNBTS
qciTabOperator
DRX profile index
drxProfileIndex
LNBTS
qciTabOperator
DSCP
dscp
LNBTS
qciTabOperator
Enforce TTI bundling
enforceTtiBundling
LNBTS
qciTabOperator
L2 overhead factor GBR DL
l2OHFactorDL
LNBTS
qciTabOperator
L2 overhead factor GBR UL
l2OHFactorUL
LNBTS
qciTabOperator
Logical channel group identifier
lcgid
LNBTS
qciTabOperator
Maximum GBR downlink
maxGbrDl
LNBTS
qciTabOperator
Maximum GBR uplink
maxGbrUl
LNBTS
qciTabOperator
Nominal bit rate downlink
nbrDl
LNBTS
qciTabOperator
Nominal bit rate uplink nbrUl
LNBTS
qciTabOperator
PDCP profile index
pdcpProfIdx
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
RLC profile index for 3 rlcProfIdx3cc CC CA
LNBTS
qciTabOperator
Scheduling bucket size duration
schedulBSD
LNBTS
qciTabOperator
Scheduling priority
schedulPrio
LNBTS
qciTabOperator
Scheduling weight
schedulWeight
LNBTS
qciTabOperator
Activate DRX
actDrx
LNCEL
-
Activate nominal bitrate for non-GBR bearers
actNbrForNonGbrBear ers
LNCEL
-
Inactivity timer
inactivityTimer
LNCEL
-
N310 for QCI1
n310Qci1
LNCEL
-
T310 for QCI1
t310Qci1
LNCEL
-
Maximum number of outof-sync indications
n310
SIB
-
Timer T310
t310
SIB
-
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
Sales information Table 97
LTE2611 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
3.23 LTE2612: ProSe Direct Communications for Public Safety Benefits, functionality, system impact, reference data, instructions of the feature The LTE2612: ProSe Direct Communications for Public Safety feature introduces one of the functions of proximity service (ProSe) that is defined in the 3GPP Release 12 standards called ProSe direct communication. This function enables the user equipment (UE) to perform a device-to-device (D2D) communication.
3.23.1 LTE2612 benefits The LTE2612: ProSe Direct Communications for Public Safety feature is intended for public safety (PS) operators trying to leverage the long-term evolution (LTE) technology to replace the existing mobile radio systems. The PS provider can support ProSe direct communication among the PS UEs in proximity.
3.23.2 LTE2612 functional description The LTE2612: ProSe Direct Communications for Public Safety feature includes the following components: • •
ProSe authorization indication on S1 and X2 ProSe direct communications with UE-selected resource allocation
The LTE2612: ProSe Direct Communications for Public Safety feature is supported in the 5 MHz and 10 MHz bandwidth. The LTE2612: ProSe Direct Communications for Public Safety feature allows communication between an in-coverage UE and another UE using ProSe D2D communication, which is also known as sidelink (SL). Coverage refers to being in the coverage of an LTE cell operating on a PS carrier. A UE is considered incoverage for SL direct communication whenever it detects a cell on a PS carrier, and out-of-coverage when it does not. SLs use uplink resources and physical channel structure that is similar to the uplink transmissions. UEs directly communicate with each other using the SLs. To use the D2D communication channels, the UE must be authorized. It is expected that most PS UEs are configured and pre-authorized. When the authorized and capable SL UEs are in-coverage, they rely on the system information broadcast 18 (SIB18) to attain SL communications configuration from the PS cell. The evolved Node B (eNB) needs provisioning data to configure the information in the SIB18. The resources specify the time domain and the frequency domain information corresponding to the receiving SL direct communications. To reduce interference issues with the Uu transmissions, the scheduler reserves the UL resources that can be used for SL communication transmissions.
Issue: 01 Draft
DN09237915
159
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
If the UE is in the RRC idle state, the information on transmit pool is broadcasted in SIB18. An authorized UE expresses an interest in ProSe direct communication using a SidelinkUEInformation message to the eNB in an RRC connected state when it receives an SIB18 broadcast from a PS cell. Mobility management is modified to try and keep the UEs interested in PS communication on a PS carrier. Regardless of whether SIB18 is configured with transmit pool resources, a dedicated transmit resource must be provided to a connected UE, that is, the UE is RRC connected on a PS carrier. The eNB sends an RRC reconfiguration message with an independent resource selection and provides the dedicated transmit resources. The transmit pool configuration is identical in the dedicated configuration and in the SIB18. The same procedure is used to remove SL resources to UEs that are no longer interested in SL communications or when ProSe authorization is stopped. In the UE-independent resource allocation selection scheme, the eNB has a slight involvement in the specific SL transmission resource selection process. This scheme is applicable to both RRC idle and RRC connected states using transmit pool resources, which the dedicated signaling or the SIB18 broadcasts. An out-of-coverage UE must be synchronized in the system before communicating with other elements. In this feature, the eNB provides a reference symbol received power (RSRP) threshold in the SIB18 to indicate when the UE has to send SL synchronization information.
g
Note: The SL resource pool configuration is highly flexible to provide various situations that allow different trade-off. The SL resource pool must not overlap with the physical random access channel (PRACH) and other blocked regions like the LTE944: PUSCH Masking feature. Also, it must not overlap with the physical uplink control channel (PUCCH) and must be configured between the upper and lower PUCCH regions. It is expected that the preconfigured pool and the broadcast pool are configured the same as in the standard deployment. Depending on the configuration and trade-offs between quality and capacity, the HARQ retransmission, TTI bundling, and DRX performance can sustain different degree of impact. If uncertain, it is recommended to start with the default SL pool configuration to minimize impacts. The LTE2612: ProSe Direct Communications for Public Safety feature expects the preconfigured Tx/Rx pools for out-of-coverage UEs to match the corresponding pools broadcasted in SIB18. However, this feature allows the operator to define the second Rx pool to be broadcasted in SIB18 in case the assumption is not true with the following restrictions: • •
The preconfigured Rx pools must contain the SIB18 Tx pool so that the out-ofcoverage UE can listen to the in-coverage transmission. One of the Rx pool broadcasted by the SIB18 must accommodate the out-ofcoverage Tx pool so that the in-coverage UEs can listen to the out-of-coverage transmission.
ProSe authorization indication on S1 and X2 The component includes ProSe-authorized indication defined by the 3GPP Release 12 TS 23.303 in the S1-AP and X2-AP messages. This is to indicate whether the PS UE is authorized to use ProSe. The ProSe authorized indication can be included in the following: •
S1-AP messages –
160
Initial Context Setup Request
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
– – – •
Descriptions of radio resource management and telecom features
UE Context Modification Request Handover Request (in the case of S1 handover) Path Switch Request Acknowledge
X2-AP message –
Handover Request
The LTE2612: ProSe Direct Communications for Public Safety feature assumes that the eNB receives the ProSe authorization indication over the S1/X2 messages from the mobility management entity (MME) and the neighboring eNBs forwards it. If the ProSeauthorized information element (IE) includes one or more IEs that are set to not authorized in the UE Context Modification Request S1-AP message, the eNB sends an RRC connection reconfiguration message to the UE. This ensures that the UE is no longer accessing the relevant ProSe. ProSe direct communication with UE-selected resource allocation The ProSe Release 12 direct communication is only applicable for PS-authorized and PS-capable UEs. From the radio access network (RAN) perspective, both the quality of service (QoS) and session management are transparent and responsible for the PS UE application level. The ProSe direct communication over the SL channel is supported assuming that the UE-selected resource allocation of SL resources is sufficient for this feature. The operator can configure the following: • •
pools of SL resources for both receive and transmit other SL channel items such as cyclic prefix and power control
To ensure continuous service between cells for ProSe UEs in active SL communication, a common SL configuration in SIB18 and the UE-dedicated SL configuration between adjacent ProSe-enabled carrier cells must be coordinated. This is enabled using an identical and common SL configuration on SIB18 for all ProSe-enabled carrier cell cluster within the same region. Also, to ensure communications with out-of-coverage UEs, the preconfigured SL configuration in the UE must be considered.
3.23.3 LTE2612 system impact LTE2612: ProSe Direct Communications for Public Safety impact on features, interfaces, and system performance and capacity Interdependencies between features The following features must be deactivated before activating the LTE2612: ProSe Direct Communications for Public Safety feature: • • • • • •
g
Issue: 01 Draft
LTE1382: Cell Resource Groups LTE1092: Uplink Carrier Aggregation - 2 CC LTE1103: Load Based Power Saving for Multi-layer Networks LTE1203: Load Based Power Saving with Tx Path Switching Off LTE1113: eICIC – Macro LTE1059: Uplink Multi-cluster Scheduling Note: The power saving features must be disabled in the PS carrier that has SL resource configured.
DN09237915
161
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
The LTE2612: ProSe Direct Communications for Public Safety feature depends on the following features: •
• •
LTE486: PLMN ID Selected Mobility Profiles and LTE1905: PLMN ID and SPID Selected Mobility Profiles These features ensure that only authorized PS UEs are allowed to use preconfigured SL resources of PS carriers. LTE891: Timing Over Packet with Phase Synchronization LTE80: GPS Synchronization The btsSyncMode BTSSCL parameter must be set to PhaseSync to provide air frame synchronization across all the cells of the eNB that support ProSe carrier. This ensures proper timing alignment of all transmit and received pools of different cells.
The LTE2612: ProSe Direct Communications for Public Safety feature affects the following features: •
•
g
Note: The LTE46: Channel-aware Scheduler (UL) feature can operate even when the SRS is disabled. •
•
• •
•
•
•
•
162
LTE116: Cell Bandwidth – 3 MHz and LTE117: Cell Bandwidth – 1.4 MHz The LTE2612: ProSe Direct Communications for Public Safety feature is supported in the 5 MHz and 10 MHz bandwidth. LTE46: Channel-aware Scheduler (UL) This feature does not need to be disabled. However, sounding reference signal (SRS) cannot be enabled with SL. The SRS must be disabled on the carrier that supports SL resource configuration.
LTE907: TTI Bundling Transmission time interval (TTI) bundling assigns four consecutive TTIs and has to be modified to consider SL resource pool when the UE performs SL. The SL pool configuration needs to consider TTI bundling. LTE619: Interference-aware UL Scheduling The algorithm of this feature assigns a physical resource block (PRB) and should avoid assigning the SL PRB region. LTE1336: Interference-aware UL Power Control The SL resource pool must be excluded for power control calculation. LTE581: PRACH Management and LTE962: RACH Optimization These features automatically calculate the PRACH offset frequency from the PUCCH location. The resources occupied by the SL communication have to be excluded. LTE786: Flexible UL Bandwidth The resources occupied by the SL communication have to be excluded. The SL pool must not be configured in the outer regions and must be between the lower and upper regions of the PUCCH. They must also avoid conflicts with the configured physical uplink shared channel (PUSCH) blanking or PRACH resources. LTE1495: Fast Uplink Link Adaptation Fast uplink link adaptation (FULA) can operate with or without SRS. An interference measurement filter checks and skips the SL occupied resources. LTE944: PUSCH Masking This feature masks certain PRBs for the purpose of interference avoidance. The masked PRB and SL pool must not overlap. LTE825: Uplink Outer Region Scheduling The SL pool must be between the lower and upper regions of the PUCCH and avoid PRACH.
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• •
•
•
Descriptions of radio resource management and telecom features
LTE2275: PCell Swap This feature must consider the PRB assigned for SL purposes. LTE2664: Load Based PUCCH Region This feature must avoid overlapping with SL resources. The PUCCH size changes based on loading. LTE1130: Dynamic PUCCH Allocation This feature must avoid overlapping PUCCH and PRACH locations with SL resources. LTE497: Smart Admission Control, LTE534: ARP-based Admission Control for ERABs, and LTE1042: Nominal Bitrate for Non-GBR Bearers These features assess uplink capacity and should adjust accordingly with SL resource pool.
The LTE2612: ProSe Direct Communications for Public Safety feature affects the following handover features for UEs that have expressed an interest on the ProSe carrier: •
•
•
•
•
•
•
Issue: 01 Draft
LTE423: RRC Connection Release with Redirect A UE that has expressed an interest in SL communication is provided with an A2 SL threshold in addition to the existing A2 redirect thresholds. LTE2166: Support of Dedicated Idle Mode Mobility Priorities, LTE1677: Idle Mode Mobility Balancing Extensions, LTE2051: Measurement-based Idle Mode Load Balancing, LTE487: Idle Mode Mobility Load Balancing, and LTE762: Idle Mode Mobility from LTE To WCDMA, GSM or other LTE Bands A dedicated idle mode mobility priority is not assigned to a UE that has expressed an interest in SL communication when the UE is idle. LTE1387: Intra-eNodeB IF Load Balancing, LTE1170: Inter-frequency Load Balancing, LTE1531: Inter-frequency Load Balancing Extension, LTE2008: Extended Inter-frequency Measurements, LTE1127: Service-based Mobility Trigger, LTE1841: Inter-Frequency Load Equalization, and LTE1357: LTE-UTRAN Load Balancing Inter-frequency is delayed for a UE that expresses an interest in SL communication using a dedicated A2-SL thresholds. The A2-SL thresholds remove and replace the existing evolved universal terrestrial radio access (EUTRA) measurements. The UE is not unloaded since the A4 measurements are deactivated. LTE1905: PLMN ID and SPID Selected Mobility Profiles and LTE490: Subscriber Profile-based Mobility The ProSe UEs might have a specific public land mobile network (PLMN) ID. The profiles might coexist with ProSe UEs. LTE55: Inter-frequency Handover, LTE872: SRVCC to WCDMA, LTE873: SRVCC to GSM, LTE56: Inter-RAT Handover to WCDMA, LTE442: Network Assisted Cell Change To GSM, LTE60: Inter RAT Handover to eHRPD/3GPP2, and LTE738: SRVCC to 1xRTT/CDMA The SL-specific A2 threshold is used to activate handover measurements. The single radio voice call continuity (SRVCC) measurements are removed when the UE expresses an interest in SL communication. LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB), LTE562: CSFB to UTRAN or GSM via Redirect, and LTE736: CS Fallback to UTRAN The circuit switched fallback (CSFB) is supported whether the UEs have expressed interest in SL communication or not. LTE556: ANR Intra-LTE, Inter-frequency - UE-based and LTE908: ANR Inter-RAT UTRAN - Fully UE-based
DN09237915
163
Descriptions of radio resource management and telecom features
•
•
FDD-LTE16A, Feature Descriptions and Instructions
A UE that has expressed an interest in SL communication is excluded in performing active automatic neighbor relation (ANR). LTE2351: S1-based Handover towards CSG Cells , LTE1442: Open Access Home eNodeB Mobility, and LTE1723: S1-based Handover towards Home eNodeB A PS UE that has expressed an interest in SL communication is not handed over to the home eNB or closed subscriber group (CSG) cells. LTE1534: Multiple Frequency Band Indicator and LTE2754: Frequency Bands Priority Change in mFBI The eNB also supports multiple frequency band indicator (mFBI) on ProSe-enabled cells. The freqBandPriority information element (IE) in SIB1 is set if the mapped band is also ProSe-enabled. The UE is expected to send an interest indication on the ProSe-enabled bands.
The LTE2612: ProSe Direct Communications for Public Safety feature affects the following carrier aggregation (CA) features: • • • • • • •
g
LTE2006: Flexible SCell Selection LTE2275: PCell Swap LTE1804: Downlink Carrier Aggregation 3CC - 60 MHz LTE2276: A4 Based SCell Selection LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs LTE1541: Advanced SCell Measurement Handling LTE2531: FDD Downlink Carrier Aggregation 4CC/5CC Note: In the LTE2612: ProSe Direct Communications for Public Safety feature, simultaneous SL and CA are not supported. All SCells are removed along with any A6 measurements when the UE expresses an interest in SL communication. Any A3 SCell discovery measurements are not triggered until the UE expresses lack of interest in SL communication. When the UE is granted SL resources with the new A2 SL threshold, any A3 SCell discovery is also deactivated.
Impact on interfaces The LTE2612: ProSe Direct Communications for Public Safety feature affects interfaces as follows: •
S1 Interface to MME –
•
X2 interface to other eNBs –
•
ProSe authorized IE support over Initial Context Setup Request, UE Context Modification Request, Handover Request, and Path Switch Request Acknowledge
ProSe authorized IE support over Handover Request
Uu interface –
SIB18
–
SidelinkUEInformation messages
A configurable number of PRBs are reserved for SL communication based on the LTE uplink resources. These resources are excluded from the scheduled transmissions for uplink. A set of subframes can be configured for SL transmission. SL UEs are not scheduled in the uplink on these subframes.
164
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
Impact on network management tools The LTE2612: ProSe Direct Communications for Public Safety feature has no impact on network management tools. Impact on system performance and capacity The LTE2612: ProSe Direct Communications for Public Safety provides basic support for SL PS UEs through a set of uplink radio bearer (RB) that is exclusively reserved for SL communication. Since the uplink RB is unavailable to the Uu uplink interface assignment, both the cell and the single UE peak throughput are degraded. A UE that has expressed an interest in the SL communication is not scheduled with an uplink grant for transmission time intervals (TTIs) belonging to the SL pool. The sounding reference signal (SRS) must be turned off when the LTE2612: ProSe Direct Communications for Public Safety feature is enabled. The frequency selective gain is reduced and affects the throughput. The number of RB left for the Uu interface is reduced, which might make it difficult for the scheduler to efficiently utilize all the resources. Additionally, a single UE peak throughput might be reduced if the SL resource pool is provisioned in such a way that the remaining RBs available to the Uu interface are segmented into multiple non-continuous regions.
3.23.4 LTE2612 reference data LTE2612: ProSe Direct Communications for Public Safety requirements, alarms, measurements and counters, parameters, and sales information Requirements Table 98
LTE2612 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
Not supported
Not supported
Not supported
NetAct
MME
SAE GW
UE
Not supported LTE OMS16A
Support not required
NetAct 16.8
Support not required
Support not required
BTS faults and reported alarms Table 99
New BTS faults introduced by LTE2612
Fault ID
Fault name
Reported alarm Alarm ID
6298
Invalid sidelink transmit pool configuration
7653
Alarm name CELL FAULTY
For alarm descriptions, see FDD-LTE BTS Alarms and Faults. Commands There are no commands related to the LTE2612: ProSe Direct Communications for Public Safety feature.
Issue: 01 Draft
DN09237915
165
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
Measurements and counters Table 100
New counters introduced by LTE2612
Counter ID
Counter name
Measurement
M8053C Number of ProSe Direct 0 Communication requests
LTE Proximity Services
M8053C Sum of ProSe UEs using Direct 1 Communication
LTE Proximity Services
M8053C Denominator for ProSe UEs 2
LTE Proximity Services
For counter descriptions, see LTE Performance Measurements and Key Performance Indicators. Key performance indicators There are no key performance indicators related to the LTE2612: ProSe Direct Communications for Public Safety feature. Parameters Table 101
New parameters introduced by LTE2612 Full name
Abbreviated name
LNBTS
Parent structure -
Activate ProSe communication
actProSeComm
Related hysteresis of Th2 For RSRP during sidelink
hysThreshold2Side SLMEAS link
-
Sidelink measurement identifier
slMeasId
SLMEAS
-
Threshold Th2 for RSRP during sidelink
threshold2Sidelin SLMEAS k
-
Time to trigger for A2 measurement during sidelink
a2TimeToTriggerAc SLMEAS tSL
-
LTE proximity services
mtProSe
PMRNL
Sidelink communication profile identifier
slCommProfId
SLCOMM PROF
Sidelink EARFCN uplink
slEarfcnUL
SLCOMM PROF
Sidelink uplink channel slUlChBw bandwidth
166
Managed object
-
SLCOMM PROF
Hopping offset for sidelink
slHoppingConfigRb SLCOMM Offset RES
Number of subbands for sidelink hopping configuration
slHoppingConfigNu SLCOMM mSubBand RES
Offset indicator for sidelink control short
scTFResConfigOffS SLCOMM etInd RES
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 101
Descriptions of radio resource management and telecom features
New parameters introduced by LTE2612 (Cont.) Full name
Abbreviated name
Managed object
Offset indicator for sidelink data short
dataTFResConfigOf SLCOMM fSetInd RES
PRB end for sidelink control
scTFResConfigPrbE SLCOMM nd RES
PRB end for sidelink data
dataTFResConfigPr SLCOMM bEnd RES
PRB num for sidelink control
scTFResConfigPrbN SLCOMM um RES
PRB num for sidelink data
dataTFResConfigPr SLCOMM bNum RES
PRB start for sidelink control
scTFResConfigPrbS SLCOMM tart RES
PRB start for sidelink data
dataTFResConfigPr SLCOMM bStart RES
Sidelink communication resources identifier
slCommResId
SLCOMM RES
Sidelink control CP length
slScCpLen
SLCOMM RES
Sidelink control period slScPeriod
SLCOMM RES
Sidelink data CP length slDataCpLen
SLCOMM RES
Parent structure
Sidelink hopping slHoppingConfigPa SLCOMM configuration parameter ram RES
Issue: 01 Draft
Subframe bitmap for sidelink control
scTFResConfigSubf SLCOMM rBitMap RES
Subframe bitmap for sidelink data
dataTFResConfSubf SLCOMM rBitMap RES
Sidelink communication TX pool identifier
slCommTxId
Sidelink data transmit parameter alpha
slDataTxParameter SLCOMM sAlpha TX
Sidelink data transmit parameter P0
slDataTxParameter SLCOMM sP0 TX
Sidelink SC transmit parameter alpha
slScTxParametersA SLCOMM lpha TX
Sidelink SC transmit parameter P0
slScTxParametersP SLCOMM 0 TX
Sidelink communication synchronization identifier
slCommSyncId
SLCOMM TX
SLCOMM SYNC
Sidelink sync CP length slSyncCpLen
SLCOMM SYNC
Sidelink sync offset indicator
SLCOMM SYNC
slSyncOffsetInd
DN09237915
167
Descriptions of radio resource management and telecom features
Table 101
FDD-LTE16A, Feature Descriptions and Instructions
New parameters introduced by LTE2612 (Cont.) Full name
Abbreviated name
Parent structure
Sidelink sync transmit parameter alpha
syncTxParametersA SLCOMM lpha SYNC
Sidelink sync transmit parameter P0
syncTxParametersP SLCOMM 0 SYNC
Sidelink sync transmit threshold IC
syncTxThreshIC
Table 102
SLCOMM SYNC
Existing parameters related to LTE2612 Full name
Abbreviated name
Managed object
Parent structure
LNBTS
-
Network synchronization btsSyncMode mode
BTSSCL
-
Activate enhanced actEicic inter-cell interference coordination
LNCEL
-
actUlMultiCluster LNCEL
-
Activation of automatic actAutoPucchAlloc LNCEL PUCCH allocation
-
Cell resource sharing mode
cellResourceShari LNCEL ngMode
-
PRACH frequency offset
prachFreqOff
LNCEL
-
PUSCH mask
ulsPuschMask
LNCEL
-
Length of the PUSCH mask
ulsPuschMaskLengt LNCEL h
ulsPuschMask
Start PRB of the PUSCH mask
ulsPuschMaskStart LNCEL
ulsPuschMask
Activation of uplink carrier aggregation
actULCAggr
Activate UL multicluster Scheduling
168
Managed object
SRS feature srsActivation activation/deactivation
LNCEL
-
Threshold th2a for RSRP threshold2a
LNCEL
-
Threshold Th2a for RSRP threshold2aQci1 During QCI1
LNCEL
-
PUCCH bandwidth for CQI nCqiRb
MPUCCH -
System information scheduling list
sibSchedulingList SIB
-
Periodicity
siMessagePeriodic SIB ity
sibSchedulingList
Repetition
siMessageRepetiti SIB on
sibSchedulingList
SIB type
siMessageSibType
SIB
sibSchedulingList
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 102
Descriptions of radio resource management and telecom features
Existing parameters related to LTE2612 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
Load-based power saving lbpsCellList cell list
PSGRP
-
Load-based power saving lbpsCellSOOrder cell switch off order
PSGRP
lbpsCellList
LTE cell configuration identifier
PSGRP
lbpsCellList
lnCelId
Load-based power saving lbpsLastCellSOEna PSGRP last cell switch off bled enabled
-
For parameter descriptions, see FDD-LTE BTS Parameters. Sales information Table 103
LTE2612 sales information
Product structure class Application software (ASW)
License control SW Asset Monitoring
Activated by default No
3.24 LTE2629: FDD-LTE Dual-cell (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS The LTE2629: FDD-LTE Dual-cell (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS feature allows to combine two cells (up to 2x20 MHz) in order to achive higher downlink and uplink peak throughput.
3.24.1 LTE2629 benefits The LTE2629: FDD-LTE Dual-cell (2x20M Hz) Operation Support on a Single Flexi Zone Micro BTS feature increases network's capacity by allowing the operator to configure dual-cell operations on a single Flexi Zone Micro/Pico BTS. Thus, peak throughput is increased up to 300 Mbps in DL and up to 100 Mbps in UL.
3.24.2 LTE2629 functional description The LTE2629: FDD-LTE Dual-cell (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS feature enables configuring two separate cells on the Flexi Zone Micro/Pico BTS. Thus, it requires FDD dual-cell-capable Flexi Zone Micro/Pico hardware. Once the dual-cell-capable hardware is installed, it is possible to configure two separate cells with the software manager. There is also an option to configure the dual-cell Flexi Zone Micro/Pico BTS in a single-cell mode. This feature is intended to be compatible with a broad range of possible future hardware platforms, both indoor Flexi Zone Pico and outdoor Flexi Zone Micro, and it supports an inter-band mode of operation for the two cells.
Issue: 01 Draft
DN09237915
169
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
The feature supports dual-carrier operation where the two cells are located on different bands (inter-band, non-contiguous). Figure 13
An example of deployment of dual-cell operation cells inter-band
Cell1 Cell2
Cell1
Cell2
Band1
Band2
Any combination of two cells with 5, 10, 15, and 20 MHz bandwidth are supported, including a single 5, 10, 15, and 20 MHz cell deployment. LTE2629 also supports the cell combination deployment of 20-MHz licensed bandwidth and 20-MHz unlicensed bandwidth. Single cell deployment on the unlicensed bandwidth is not supported. Two cells can be configured and activated simultaneously or one after another. When it is done separately, any instance of adding/deleting/enabling/disabling of the second cell requires an eNB restart. With the LTE2629 feature enabled, two-carrier (2CC) intra-eNB carrier aggregation becomes a possibility.
3.24.3 LTE2629 system impact Interdependencies between features The LTE2629: FDD-LTE Dual-cell (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS feature impacts the following features: •
•
•
•
•
LTE2729: B2+B4/B66 FZ G2 Indoor Multi-Band Pico (FW2FIA, FW2FIWA, FW2FIWC) This feature introduces the first dual-band indoor pico platform with two licensed bands. LTE2357: B4/66+Unlic FZ G2 Indoor Multi-Band Pico (FW2IRA, FW2IRWA, FW2IRWC) This feature introduces a dual-band indoor pico platform supporting one 3GPPlicensed band and a 5-GHz unlicensed band. LTE2424: LTE-U (2CC) Support for Dual-Band Indoor/Outdoor FZ BTS This feature introduces the software support for downlink carrier aggregation with a 5-GHz unlicensed spectrum. LTE1332: Downlink Carrier Aggregation – 40 MHz This feature enables the eNB to support carrier aggregation in downlink for two component carriers of up to 20-MHz cell bandwidth each and two non-aggregated uplink cells. LTE2060: Add New Frequency or Cell Without Reset This feature enables adding a cell or a carrier without a site outage.
Impact on interfaces The LTE2629: FDD-LTE Dual-cell (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS feature has no impact on interfaces. Impact on network management tools
170
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
The LTE2629: FDD-LTE Dual-cell (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS feature has no impact on network management tools. Impact on system performance and capacity The LTE2629: FDD-LTE Dual-cell (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS feature impacts system performance and capacity as follows: • •
It facilitates a peak throughput of up to 300 Mbps in DL and up to 100 Mbps in UL with two cells of 20-MHz bandwidth. With an increased bandwidth support (2x20 MHz), up to 600 in total RRC-connected UEs, 250 active UEs, and a total of 12 UEs per transmission time interval (TTI) (six UEs per TTI per cell) can be supported. The total of RRC-connected UEs and the total of UEs per TTI are lower for 2x20 MHz compared to 840 UEs in total and 20 in total UEs per TTI, which are possible with 2x10 MHz. This is due to the fact that the increase in total bandwidth doubles the total number of resource blocks to be scheduled.
3.24.4 LTE2629 reference data Requirements Table 104
LTE2629 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
AirScale BTS
FDD-LTE 16A
Not supported
Not supported
Not supported
Flexi Zone Controller
OMS
UE
NetAct
FL16A
LTE OMS16A
3GPP R8-R10 NetAct 16.8 UE capabilities
Flexi Zone Micro BTS FL16A
Flexi Zone Access Point FL16A
MME Support not required
SAE GW Support not required
Alarms There are no alarms related to the LTE2629: FDD-LTE Dual-cell (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS feature. BTS faults and reported alarms Table 105 Fault ID
4339
New BTS faults introduced by LTE2629 Fault name
Reported alarms Alarm ID
U-Plane Computing Environment Container Failure
7650
Alarm name
BASE STATION FAULTY
For fault descriptions, see FDD-LTE BTS Alarms and Faults. Commands There are no commands related to the LTE2629: FDD-LTE Dual-cell (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS feature. Measurements and counters There are no measurements or counters related to the LTE2629: FDD-LTE Dual-cell (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS feature.
Issue: 01 Draft
DN09237915
171
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
Key performance indicators There are no key performance indicators related to the LTE2629: FDD-LTE Dual-cell (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS feature. Parameters There are no parameters related to the LTE2629: FDD-LTE Dual-cell (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS feature. Sales information Table 106
LTE2629 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default No
3.25 LTE2630: Uplink Control Information Only Transmission Benefits, functionality, system impact, reference data, instructions of the feature The LTE2630: Uplink Control Information Only Transmission feature introduces uplink control information (UCI)-only grant to a user equipment (UE). This is used to retrieve the UCI via the physical uplink shared channel (PUSCH) if there is no user data transmission, that is, if the evolved Node B (eNB) has not successfully received a periodic or an aperiodic channel state information (CSI) for a carrier during an operatorconfigurable time.
3.25.1 LTE2630 benefits The LTE2630: Uplink Control Information Only Transmission feature provides an improved downlink channel-aware scheduler performance for scenarios where the eNB cannot receive the channel quality indicator (CQI) information via the existing mechanism.
3.25.2 LTE2630 functional description The Flexi Multiradio BTS introduces enhancements to retrieve the aperiodic UCI. The following are the types of UCI-only transmissions supported: •
Low-priority UCI The uplink UCI-only grants are assigned if: – – –
g
172
there are free physical downlink control channel (PDCCH) and PUSCH resources. the UE is discontinuous reception (DRX)-active (DRX is applied). the eNB has not received a single periodic CQI report or the eNB has not received an aperiodic CSI report during an operator-configurable time. Note: Low-priority UCI-only grant cannot be assigned if the UE is in a transmission time interval (TTI) bundling mode or if the UE is out-of-sync. This is also the same as for the high-priority UCI-only grant.
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
High-priority UCI The uplink UCI-only grants are assigned if: – –
g
Descriptions of radio resource management and telecom features
the UE is DRX-active (DRX is applied). the eNB has not received multiple periodic CQI reports and the eNB has not received an aperiodic CSI report during an operator-configurable time. Note: High-priority grants are prioritized over grants for initial transmission. The operator can configure the maximum number of physical resource blocks (PRBs) assigned for high-priority grants per TTI.
The support of the UCI-only grants are necessary to resolve CSI reporting issues during enhanced inter-cell interference coordination (eICIC) and carrier aggregation (CA) operations in the cell with or without DRX configuration. Therefore, it is strongly recommended to enable the LTE2630: Uplink Control Information Only Transmission feature in the respective cells. This feature also provides means for requesting aperiodic CSI reports from the UEs regardless of the availability of the uplink data, that is, if the uplink scheduler regularly requests the periodic CSI report.
3.25.3 LTE2630 system impact LTE2630: Uplink Control Information Only Transmission impact on features Interdependencies between features The LTE2630: Uplink Control Information Only Transmission feature affects all eICIC and CA features. It is recommended to enable this feature when the eICIC or CA features are used in the cell. Impact on interfaces The LTE2630: Uplink Control Information Only Transmission feature has no impact on interfaces. Impact on network management tools The LTE2630: Uplink Control Information Only Transmission feature has no impact on network management tools. Impact on system performance and capacity The LTE2630: Uplink Control Information Only Transmission feature might cause degradation (less UEs/TTI) because more actions are needed from the media access control protocol stack (MAC PS) side.
3.25.4 LTE2630 reference data LTE2630: Uplink Control Information Only Transmission requirements, parameters, and sales information Requirements
Issue: 01 Draft
DN09237915
173
Descriptions of radio resource management and telecom features
Table 107
FDD-LTE16A, Feature Descriptions and Instructions
LTE2630 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL16A
UE
LTE OMS16A
Flexi Zone Micro BTS FL16A
NetAct
3GPP R8 mandatory
NetAct 16.8
Flexi Zone Access Point FL16A
MME Support not required
SAE GW Support not required
Alarms There are no alarms related to the LTE2630: Uplink Control Information Only Transmission feature. Commands There are no commands related to the LTE2630: Uplink Control Information Only Transmission feature. Measurements and counters There are no measurements or counters related to the LTE2630: Uplink Control Information Only Transmission feature. Key performance indicators There are no key performance indicators related to the LTE2630: Uplink Control Information Only Transmission feature. Parameters Table 108
New parameters introduced by LTE2630 Full name
Abbreviated name
Parent structure
Activate UCI only grant actUciOnlyGrants transmission
LNCEL
-
Adjust max number of high prio UCI-only grants per TTI
multNumUeHighPrioUciGrant
LNCEL
-
Adjust timer for low and high priority UCIonly grants
multUciGrant
LNCEL
-
LNCEL
-
PRB limit for high prio maxPrbHighPrioUciGrant UCI-only grants per TTI
Table 109
Existing parameters related to LTE2630 Full name
174
Managed object
Abbreviated name
Managed object
Parent structure
Downlink channel bandwidth
dlChBw
LNCEL
-
Enable aperiodic CQI reporting on PUSCH
cqiAperEnable
LNCEL
-
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
Sales information Table 110
LTE2630 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default No
3.26 LTE2754: Frequency Bands Priority Change in mFBI Benefits, functionality, system impact, reference data, instructions of the feature The LTE2754: Frequency Bands Priority Change in mFBI feature supports multiple frequency band indicator (mFBI) frequency band prioritization.
3.26.1 LTE2754 benefits The LTE2754: Frequency Bands Priority Change in mFBI feature prioritizes mFBImapped band. The feature targets the UE to select the mapped band with higher priority when both bands are supported. In case the mFBI user equipment (UE) supports a native primary cell (PCell) and mapped PCell band, the mapped band is used to support carrier aggregation (CA). Otherwise, CA is not supported with the band combination of the mapped PCell, and an extra intra-cell handover is needed to support CA for these UEs.
3.26.2 LTE2754 functional description The LTE2754: Frequency Bands Priority Change in mFBI feature introduces support for frequency band priority change in the mFBI. The feature is an extension to the LTE1534: Multiple Frequency Band Indicator feature for UEs that only support certain band-related features (for example, the UE supports CA if PCell works on the mapped band). For more information, see the LTE1534: Multiple Frequency Band Indicator feature description. Currently, the band-applying rule for accessing a carrier that belongs to a different overlapping frequency band causes an additional intra-cell handover to UEs that support certain band-related features in one of the overlapping bands. To avoid additional handovers, a new freqBandIndicatorPriority information element (IE) in the system information broadcast 1 (SIB1) is introduced to change the priorities of the overlapping bands and the corresponding UE capabilities. The freqBandIndicatorPriority IE indicates whether the UE supports the prioritization of the frequency band in the multiBandInfoList IE or the band in the freqBandIndicator IE. The evolved Node B (eNB) considers the UE capabilities to support band priority change and the SIB1 content to determine if the UE uses native or mapped band during initial call setup. During handover, the target eNB considers the UE capabilities to support band priority change and the SIB1 content to select the E-UTRA absolute radio frequency channel number (EARFCN) for the target cell.
Issue: 01 Draft
DN09237915
175
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
When the eNB and the UE support both bands and the UE support frequency band adjustment capability, the mapped EARFCN is selected as an operation EARFCN with higher priority instead of the native EARFCN, which the LTE1534: Multiple Frequency Band Indicator feature introduces in the dedicated signaling for the following procedure: • • •
•
PCell measurement objects Any type of intra-LTE handover SCell handling for CA The native or mapped band is selected as the secondary cell (SCell) operation band. This is depending on the supported CA band combinations. The LTE2754: Frequency Bands Priority Change in mFBI feature affects the CA band combination selection based on the operation band of the PCell. eNB internal checks for UE-supported bands The eNB internal checks for UE-supported bands are extended to consider supported mapped bands with higher priority.
3.26.3 LTE2754 system impact LTE2754: Frequency Bands Priority Change in mFBI impact on features and interfaces Interdependencies between features The LTE1534: Multiple Frequency Band Indicator feature must be activated before activating the LTE2754: Frequency Bands Priority Change in mFBI feature (actMFBI parameter is set to true).
g
Note: Activation of the LTE1534: Multiple Frequency Band Indicator feature must be in the eNB and its neighbor eNBs. The LTE2754: Frequency Bands Priority Change in mFBI feature affects the following features: • •
•
•
•
176
LTE039: System Information Broadcast The mFBI-specific freqBandIndicatorPriority IE extends the content of the SIB1. LTE53: Intra- and Inter-eNodeB Handover with X2 and LTE54: Intra-LTE Handover via S1 The mapped EARFCN is used to communicate between the UE and the eNB. If the UE supports the mapped band adjustment for the inter-frequency handover, the mapped EARFCN is selected with higher priority. LTE55: Inter-frequency Handover and LTE1060: TDD - FDD Handover The selection of the inter-frequency handover targets is extended. If the UE supports the mapped band adjustment for the inter-frequency handover, the mapped EARFCN is selected with higher priority. LTE423: RRC Connection Release with Redirect, LTE487: Idle Mode Load Balancing, LTE1407: RSRQ-based Redirect, and LTE1677: Idle Mode Mobility Balancing Extensions If the UE supports the mapped band adjustment and the redirection target is shown in the multiple frequency band indicator profile (MFBIPR), the native EARFCN is selected as a redirection target instead of the mapped band. LTE1089: Downlink Carrier Aggregation - 20 MHz and LTE1332: Downlink Carrier Aggregation - 40 MHz If the PCell selects the mapped band as its operation band, the eNB checks if the UE supports the band combination for CA against the PCell with the mapped band.
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
•
•
Descriptions of radio resource management and telecom features
LTE2275: PCell Swap The LTE2754: Frequency Bands Priority Change in mFBI feature can be enabled with this feature. When PCell swap is triggered, the target PCell finds the available CA band combination with the mapped band. LTE2838: CA Steering Intra-cell Handover The LTE2838: CA Steering Intra-cell Handover feature targets the UE that selects the native band as the operation band when both bands are supported. If the UE only supports some features on the mapped band, intra-cell handover is triggered to direct the native EARFCN to the mapped EARFCN. If the UE supports the mapped band adjustment with higher priority even if a specific feature cannot be performed on the mapped band, the eNB does not trigger an intracell handover using the steering PCell mapped EARFCN to the native EARFCN. LTE2612: ProSe Direct Communications for Public Safety The LTE2612: ProSe Direct Communications for Public Safety feature covers the interaction with the LTE2754: Frequency Bands Priority Change in mFBI feature.
Impact on interfaces The LTE2754: Frequency Bands Priority Change in mFBI feature affects the following interfaces: •
S1 interface –
•
X2 interface – –
•
freqBandPriorityAdjustment-r12 IE in UE-EUTRA-Capability IE
freqBandPriorityAdjustment-r12 IE in UE-EUTRA-Capability IE freqBandIndicatorPriority IE in X2 setup or X2 eNB configuration update procedure
RRC interface – –
freqBandPriorityAdjustment-r12 IE in UE-EUTRA-capability new freqBandIndicatorPriority-r12 IE added to SIB1
Impact on network management tools The LTE2754: Frequency Bands Priority Change in mFBI feature has no impact on network management tools. Impact on system performance and capacity The LTE2754: Frequency Bands Priority Change in mFBI feature has no impact on system performance or capacity.
3.26.4 LTE2754 reference data LTE2754: Frequency Bands Priority Change in mFBI requirements, parameters, and sales information Requirements
Issue: 01 Draft
DN09237915
177
Descriptions of radio resource management and telecom features
Table 111
FDD-LTE16A, Feature Descriptions and Instructions
LTE2754 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL16A
UE
LTE OMS16A
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
NetAct
FL16A
MME
3GPP R12 UE Support not capabilities required
SAE GW
Support not required
Support not required
BTS faults and reported alarms Table 112
New BTS faults introduced by LTE2754
Fault ID
Fault name
Reported alarm Alarm ID
6278
MFBI cell configuration conflict
Alarm name
7652
BASE STATION NOTIFICATION
Commands There are no commands related to the LTE2754: Frequency Bands Priority Change in mFBI feature. Measurements and counters There are no measurements or counters related to the LTE2754: Frequency Bands Priority Change in mFBI feature. Key performance indicators There are no key performance indicators related to the LTE2754: Frequency Bands Priority Change in mFBI feature. Parameters Table 113
New parameters introduced by LTE2754 Full name
Frequency band indication priority
Abbreviated name
freqBandIndPrio
Managed object MFBIPR
Parent structure -
Sales information Table 114
LTE2754 sales information
Product structure class Application software (ASW)
178
License control Pool license
DN09237915
Activated by default No
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
3.27 LTE2832: SRVCC Due to Admission Control Rejection The LTE2832: SRVCC Due to Admission Control Rejection feature allows a VoLTE user, connected to the LTE cell, to be transferred to WCDMA via single radio voice call continuity (SRVCC). The transfer takes place when there are not enough radio and/or transport resources in the LTE network. A VoLTE call can then be temporarily accepted to perform the SRVCC to WCDMA. This leads to a short-term overbooking in the eNB for voice bearer requests.
3.27.1 LTE2832 benefits The LTE2832: SRVCC Due to Admission Control Rejection feature increases the success rate for VoLTE call setups.
3.27.2 LTE2832 functional description 3.27.2.1
VoLTE general information Voice over LTE (VoLTE) is a technology specification that defines standards and procedures for delivering voice communication over 4G LTE networks using Internet Protocol (IP) multimedia subsystem (IMS). In general, VoLTE enables: • • • •
improved coverage and connectivity superior call quality extended battery life video calling
In practice, VoLTE enables making voice calls and sending data packages at the same time, downloading files, streaming, and web browsing. VoLTE is also used to improve the quality of voice calls and decrease the call drop rate. VoLTE traffic is associated by default with the quality of service class indicator 1 (QCI1).
3.27.2.2
SRVCC general information Single radio voice call continuity (SRVCC) is a procedure which moves the VoLTE users towards WCDMA. This is supported by the LTE872: SRVCC to WCDMA feature from RL40 onwards. The goal of the LTE872 feature is to provide a mechanism to hand over UEs that have the QCI1 bearer activated when changing from an LTE cell to a WCDMA cell. The voice bearer, which is the subject of the handover, is served via the circuitswitched (CS) domain on the WCDMA side. Before implementing the LTE2832: SRVCC Due to Admission Control Rejection feature, SRVCC is triggered only when the QCI1 bearer is established and an ongoing VoLTE call cannot be continued in LTE due to loss of coverage or quality degradation. With LTE2832, it is possible to introduce a new trigger for SRVCC.
Issue: 01 Draft
DN09237915
179
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
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. Figure 14
HO messages
X2AP:HandoverRequest
sourceeNB
3.27.2.3
S1AP:HandoverRequest
targeteNB
MME
LTE2832 overview The LTE2832: SRVCC Due to Admission Control Rejection feature enables moving UEs towards WCDMA to serve voice calls. It happens if the LTE serving cell is congested and cannot serve VoLTE bearers. The voice over IP (VoIP) in LTE is not possible then due to an admission control (AC) rejection. In LTE2832, the voice bearer is shortly accepted to perform the SRVCC, but it is released again if the SRVCC is not possible. Single radio voice call continuity (SRVCC) is used to send a UE to WCDMA so that service interruption for established non-GBR services is minimized, and there is no need to implement the packet-switched (PS) handover. It means that the voice service is still provided for the customer. Only the RRC-connected user can be handed over. As the SRVCC is only possible for a UE with an established QCI1 bearer, it is necessary to temporarily admit (overbook) the VoIP bearer even though AC normally rejects it in case of lack of resources for a particular call. This leads to a short-term overbooking in the eNB for voice bearer requests. Overbooking is only possible for a limited number of bearers in parallel. Operator-configurable limits exist on a cell level for radio resources and on the eNB level for transport resources. If it is not possible to send the overbooked UE to WCDMA within a limited amount of time, the overbooked E-UTRAN radio access bearer (E-RAB) is released again. The LTE2832 feature does not apply the SRVCC to GSM or 1xRTT. RAC and TAC In the LTE2832: SRVCC Due to Admission Control Rejection feature, the procedure to set up E-RABs for voice is extended. If the admission is not possible, the radio admission control (RAC) and transport area control (TAC) support the respective QCI1 bearer with a flag that the bearer is subjected to overbooking. RAC and TAC receive the information that this bearer setup can use the overbooked resources to perform the SRVCC; this decision, however is made by the C-plane beforehand. TAC limits the number of parallel setup requests that may require SRVCC. This maximum number of parallel setup requests is limited and configurable by an operator (by the nOverbookingRac and/or tacOverbookingLimit parameters).
180
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Figure 15
Descriptions of radio resource management and telecom features
Example of SRVCC due to admission control rejection (temporary overbooking is possible)
UE
UTRAN
eNB
SGSN
MME
S-GW/P-GW
S1AP:!E-RAB!SETUP!REQUEST (E-RAB!to!be!Setup!List!(E-RAB!ID!=!X,!QCI=1)) Admission!Control Check Temporary!overbooking!is!possible AC!Overbooking Supervision!timer RRC!Connection!Reconfiguration (ERAB!Setup!for!QCI#1, measConfig „includes!B1!for SRVCC!to!UTRAN“) RRC!Connection Reconfiguration!Complete
S1AP:!E-RAB!SETUP!RESPONSE (E-RAB!Setup!List!(E-RAB!ID!=!X))
loop Loop!as!long!as!Temporary!Overbooking!timer!has!not!expired!and!no!SRVCC!preparation!was!successful RRC!Measurement!Report (MeasResults!(measId of!Event!B1))
loop Loop!for!all!reported!UTRAN!cells!as!long!as!no!SRVCC!preparation!was!successful SuccessfulSRVCCtoWCDMA-Preparation
SRVCC!preparation!was!successful SRVCC!may!be!applicable in!EPC/IMS SuccessfulHOtoWCDMA-Execution
SuccessfulSRVCCtoWCDMA-Completion
If RAC and/or TAC indicates that an E-RAB was only admitted by overbooking, the eNB configures the UE with the B1 measurement for WCDMA. An Overbooking timer is started then. As long as this timer is running, the eNB attempts to get rid of the UE by SRVCC to WCDMA. If the timer expires, the eNB releases the overbooked bearer and deconfigures the B1 measurement for WCDMA. The WCDMA targets to measure are the same as for the event B2 used for coveragetriggered SRVCC (see the LTE872 feature). Also the measurement thresholds are reused from B2 thresholds for the SRVCC (this is possible as B1 parameters are a subset of B2 parameters). After receiving the B1 or B2 report, the eNB attempts SRVCC towards the reported target cells as long as SRVCC is successful. Multiple B1 reports
Issue: 01 Draft
DN09237915
181
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
may be received in the period the timer is running. If during the SRVCC execution, the UE returns to the source cell by the RRC: RRC Re-Establishment message, there is no further SRVCC attempt, and the overbooked E-RAB is released. Feature management The operator can use the AC overbooking supervision timer (tOverbookingAc) parameter to define the duration for the timer which controls the temporary overbooking of RAC and TAC. The timer is started when an ERAB with QCI1 is admitted by overbooking in RAC and/or TAC. As long as the timer is running, the eNB tries to get rid of the UE by SRVCC to WCDMA. On expiry of the timer, the eNodeB triggers the release of the E-RAB admitted by temporary overbooking. There are also two new parameters introduced with LTE2832: •
•
g
RAC overbooking limit (nOverbookingRac) – sets a limit per cell for the number of QCI1 bearers which may be admitted by RAC in the LTE cell by temporary overbooking in parallel. TAC overbooking limit (tacOverbookingLimit) – sets a limit per the eNB for the number of QCI1 bearers which may be admitted by temporary overbooking in parallel. Note: In the case of Zone deployment, the TAC mechanism is performed by the FZAP (not FZC).
3.27.3 LTE2832 system impact Interdependencies between features The following features must be activated before activating the LTE2832: SRVCC Due to Admission Control Rejection feature: • • • • • • •
LTE872: SRVCC to WCDMA LTE10: EPS Bearers for Conversational Voice LTE56: Inter-RAT Handover to WCDMA LTE534: ARP-based Admission Control for E-RAB LTE497: Smart Admission Control LTE496: Support of QCI 2, 3 and 4 LTE1401: Measurement-based TAC
The LTE2832: SRVCC Due to Admission Control Rejection feature impacts the following features: •
•
•
182
LTE735: RRC Connection Re-establishment With LTE735, a UE can re-enter the source cell of the SRVCC by the RRC: ReEstablishment message in case the SRVCC execution fails. No further SRVCC is attempted, and the overbooked E-RAB is released immediately. LTE1127: Service-based Handover LTE1127 triggers a service-based intra-LTE inter-frequency handover. With LTE2832, a service-based handover is not applicable to E-RABs which are only admitted by overbooking. A service-based handover prevents SRVCC to WCDMA which is considered as more important. LTE1127 and LTE2832 may be activated independent of each other. LTE2503: Emergency Call-based Mobility Trigger
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
•
•
•
•
•
•
Descriptions of radio resource management and telecom features
LTE2503 is an extension of LTE1127 where a service-based handover is only triggered for UEs with emergency services. LTE1170: Inter-eNodeB IF Load Balancing LTE1170 uses A4 measurements for load balancing. These measurements are deconfigured if the A2 measurement is received. With LTE2832, the A4 measurements are also deactivated when WCDMA B1 measurements are activated. LTE1387: Intra-eNodeB IF Load Balancing LTE1387 uses A4 measurements for load balancing. These measurements are deconfigured if the A2 measurement is received. With LTE2832, the A4 measurements are also deactivated when WCDMA B1 measurements are activated. LTE1531: Inter-frequency Load Balancing Extension LTE1531 uses A4 measurements for load balancing. These measurements are deconfigured if the A2 measurement is received. With LTE2832, the A4 measurements are also deactivated when WCDMA B1 measurements are activated. LTE1841: Inter-frequency Load Equalization LTE1841 uses A4 measurements for load balancing. These measurements are deconfigured if the A2 measurement is received. With LTE2832, the A4 measurements are also deactivated when WCDMA B1 measurements are activated. LTE2275: PCell Swap LTE2275 introduces a primary cell (PCell) swap. No PCell swap is triggered as long as WCDMA B1 measurements are activated. LTE1382: Cell Resource Groups LTE1382 introduces separate resource pools for public land mobile network (PLMN) groups in radio admission control (RAC). The number of overbooking resources in RAC, introduced by LTE2832, is not split between resource groups. LTE2612: ProSe Direct Communications for Public Safety UEs which are configured for sidelink communication are not subject to overbooking. If an overbooked E-RAB and sidelink communication are set up, LTE2612 deconfigures all WCDMA measurements (except B1 for CSFB) for a UE. The Admission Control Overbooking Supervision timer expires as no measurement is received. Consequently, admission-control-triggered SRVCC does not work for a UE with a sidelink communication.
The LTE2832: SRVCC Due to Admission Control Rejection feature is impacted by the following features: •
LTE55: Inter-frequency Handover SRVCC triggered due to admission control has a priority over intra-LTE interfrequency handover as it is assumed that a potential LTE inter-frequency target cell also suffers from an overload. Therefore, any running A3 or A5 measurements are deactivated when WCDMA B1 measurements are activated.
Impact on interfaces The LTE2832: SRVCC Due to Admission Control Rejection feature has no impact on interfaces. Impact on network management tools The LTE2832: SRVCC Due to Admission Control Rejection feature has no impact on network management tools. Impact on system performance and capacity The LTE2832: SRVCC Due to Admission Control Rejection has no impact on system performance and capacity.
Issue: 01 Draft
DN09237915
183
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
3.27.4 LTE2832 reference data Requirements Table 115
LTE2832 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
AirScale BTS
FL16A
FL16A
UE
LTE OMS16A
3GPP R8 UE capabilities
NetAct NetAct 16.8
Flexi Zone Micro BTS FL16A
Flexi Zone Access Point FL16A
MME Flexi NS4.0
SAE GW support not required
Alarms There are no alarms related to the LTE2832: SRVCC Due to Admission Control Rejection feature. Commands There are no commands related to the LTE2832: SRVCC Due to Admission Control Rejection feature. Measurements and counters Table 116 Counter ID
New counters introduced by LTE2832 Counter name
Measurement
M8006C299
Temporary QCI1 E-RAB setup completion due to RAC overbooking
LTE EPS Bearer
M8006C300
Temporary QCI1 E-RAB setup completion due to TAC overbooking
LTE EPS Bearer
M8006C301
Temporary QCI1 E-RAB release LTE EPS Bearer due to overbooking timer expiry
M8016C58
Inter System Handover attempts with SRVCC due to overbooking
M8016C59
Inter System Handover successes LTE Inter System Handover with SRVCC due to overbooking
M8016C60
Inter System Handover failures with SRVCC due to overbooking
LTE Inter System Handover
LTE Inter System Handover
For counter descriptions, see LTE Radio Access Operating Documentation/ Reference/Counters and Key Performance Indicators. Key performance indicators There are no key performance indicators related to the LTE2832: SRVCC Due to Admission Control Rejection feature. Parameters
184
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 117
Descriptions of radio resource management and telecom features
New parameters introduced by LTE2832 Full name
Abbreviated name
Managed object
Parent structure
Activate AC triggered SRVCC
actAcSrvcc
LNBTS
-
AC overbooking supervision timer
tOverbookingAc
LNBTS
-
RAC overbooking limit
nOverbookingRac
LNCEL
-
TAC overbooking limit
tacOverbookingLim LTAC it
Table 118
-
Existing parameters related to LTE2832 Full name
Activate enhanced AC and GBR services
Abbreviated name
Managed object
Parent structure
actEnhAcAndGbrSer LNBTS vices
-
LNBTS
-
Activate SRVCC to WCDMA actSrvccToWcdma
For parameter descriptions, see LTE Radio Access Operating Documentation/ Reference/Parameters. Sales information Table 119
LTE2832 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
3.28 LTE3092: Enhanced CSAT Support for LTE-U Small Cells Benefits, functionality, system impact, reference data, instructions of the feature The LTE3092: Enhanced CSAT Support for LTE-U Small Cells feature introduces support for downlink carrier aggregation (CA) with 5 GHz unlicensed spectrum (UNII-3). The feature uses enhanced carrier sensing adaptive transmission (CSAT) algorithm to provide a pre-standard implementation of LTE in the unlicensed spectrum.
3.28.1 LTE3092 benefits LTE Unlicensed (LTE-U) extends the benefits of LTE and LTE Advanced (LTE-A) to the unlicensed spectrum. This allows mobile operators to unload data traffic on the unlicensed frequencies more efficiently and effectively. With LTE-U, the operator can offer a more robust and continuous mobile broadband experience with better coverage and faster download speed. Enhanced CSAT (eCSAT) provides better coexistence with Wi-Fi devices and allows smooth transition to 3GPP Release 13 license-assisted access (LAA).
Issue: 01 Draft
DN09237915
185
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
3.28.2 LTE3092 functional description The LTE3092: Enhanced CSAT Support for LTE-U Small Cells feature supports eCSAT to LTE-U-capable hardware. The changes in this feature are based on the LTE2424: LTE-U (2CC) Support for Dual-band Indoor/Outdoor FZ BTS feature, which introduces a semi-static time division sharing strategy where various duty cycles are used with predetermined transmit ON and OFF durations. The LTE3092: Enhanced CSAT Support for LTE-U Small Cells feature also provides software support for prestandard LAA using dual-band Flexi Zone BTS. The eCSAT provides better coexistence with Wi-Fi devices. The fixed duty cycles introduced in the LTE2424: LTE-U (2CC) Support for Dual-band Indoor/Outdoor FZ BTS feature are replaced with basic listen-before-talk (LBT) solution. The scanning function introduced in the LTE2424: LTE-U (2CC) Support for Dual-band Indoor/Outdoor FZ BTS feature is still used in this feature. The scanning is used for evaluation of available LTE-U channel to ensure that the channel with the lowest activity is used. Bands 252 and 255 are used for the unlicensed national information infrastructure-3 (UNII-3) carrier. The band 4 (10 MHz) + band 255 (20 MHz) (BW combination set 0) band and bandwidth combinations are supported. Band 255 consists of five 20 MHz carriers. This feature also supports 20 MHz bandwidth in the licensed carrier. The Flexi Zone BTS selects one unlicensed carrier based on the scanning function introduced in the LTE2424: LTE-U (2CC) Support for Dual-band Indoor/Outdoor FZ BTS feature. The change in secondary cell (SCell) or unlicensed channel happens when the evolved Node B (eNB) stops scheduling a new data on the currently selected SCell. This causes a deconfiguration of an SCell from all UEs under the cell. Only the discovery reference signal (DRS) is transmitted in an 80 ms cycle to keep the UEs synchronized to the unlicensed carrier. No data is transmitted on the unlicensed carrier during the scanning period. The Flexi Zone BTS also uses the OFF scanning period to monitor the unlicensed channel load. The arrival of the non-guaranteed bit rate (non-GBR) data targeted for the SCell triggers the transmissions on the unlicensed channel. These transmission bursts are 10 ms long and are always preceded with a channel activity-energy detection (CCA-ED) measurement. Transmit bursts are only allowed if the CCA-ED is below an operator-configurable threshold. If not, then the CCAED measurements are repeated in the next subframe. The adaptive transmission and the CCA-ED before every transmission burst provides fair coexistence with Wi-Fi neighbors.
g
Note: This feature is enabled using the existing feature activation flag (actLteU LNBTS parameter) from the LTE2424: LTE-U (2CC) Support for Dual-band Indoor/Outdoor FZ BTS feature.
3.28.3 LTE3092 system impact LTE3092: Enhanced CSAT Support for LTE-U Small Cells impact on features and system performance and capacity Interdependencies between features
186
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
The LTE3092: Enhanced CSAT Support for LTE-U Small Cells feature is dependent on the following features: •
•
•
LTE2424: LTE-U (2CC) Support for Dual-band Indoor/Outdoor FZ BTS The changes in the LTE3092: Enhanced CSAT Support for LTE-U Small Cells feature are based on the LTE2424: LTE-U (2CC) Support for Dual-band Indoor/Outdoor FZ BTS feature. LTE2357: B4/66+Unlic FZ G2 Indoor Multi-band Pico (FW2IRA, FW2IRWA, FW2IRWC) This feature introduced the first LTE-U-capable hardware. LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells This feature defines an LTE-U enhancement to allow scanning of both UNII-1 and UNII-3 bands, permitting frequency changes to either band.
Impact on interfaces The LTE3092: Enhanced CSAT Support for LTE-U Small Cells feature has no impact on interfaces. Impact on network management tools The LTE3092: Enhanced CSAT Support for LTE-U Small Cells feature has no impact on network management tools. Impact on system performance and capacity The use of LBT instead of duty cycle affects the throughput. This depends on the amount of traffic on the channel and LBT CCA thresholds. For example, in case all CCA measurements are successful, 10 out of 11 subframes are allowed and used for downlink data transmission. A maximum of 89% of the subframes are used for downlink data when the impact of 10-ms scanning interval is added. This is close to the 90% allowed subframes used when the highest duty cycle defined in the LTE2424: LTE-U (2CC) Support for Dual-band Indoor/Outdoor FZ BTS feature (assuming fast SCell activation option). Up to five UEs are allowed to be SCell-activated in the LTE2424: LTE-U (2CC) Support for Dual-band Indoor/Outdoor FZ BTS feature during the ON duration. This restriction is not needed in the LTE3092: Enhanced CSAT Support for LTE-U Small Cells feature since there is no need to SCell-activate UEs at the start of each ON duration. As a result, the maximum number of SCell-activated UEs is increased.
3.28.4 LTE3092 reference data LTE3092: Enhanced CSAT Support for LTE-U Small Cells requirements, measurements and counters, parameters, and sales information Requirements Table 120
Issue: 01 Draft
LTE3092 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FDD-LTE 16A
Not supported
Not supported
Not supported
DN09237915
Flexi Zone Micro BTS FL16A
Flexi Zone Access Point FL16A
187
Descriptions of radio resource management and telecom features
Table 120
FDD-LTE16A, Feature Descriptions and Instructions
LTE3092 hardware and software requirements (Cont.)
Flexi Zone Controller FL16A
OMS
UE
Support not required
Support not required
NetAct Support not required
MME
SAE GW
Support not required
Support not required
Alarms There are no alarms related to the LTE3092: Enhanced CSAT Support for LTE-U Small Cells feature. Commands There are no commands related to the LTE3092: Enhanced CSAT Support for LTE-U Small Cells feature. Measurements and counters There are no measurements and counters related to the LTE3092: Enhanced CSAT Support for LTE-U Small Cells feature. Key performance indicators There are no key performance indicators related to the LTE3092: Enhanced CSAT Support for LTE-U Small Cells feature. Parameters Table 121
New parameter introduced by LTE3092 Full name
CCA Threshold
Table 122
Abbreviated name
ccaThreshold
Managed object LNUPR
Parent structure -
Existing parameters related to LTE3092 Full name
Abbreviated name
Managed object
Parent structure
Activate LTE-U dual band support
actLteU
LNBTS
-
Activate support for MBMS
actMBMS
LNBTS
-
Frequency Hold-off Timer
freqHoldoffTimer
LAA
-
Activate enhanced inter-cell interference coordination
actEicic
LNCEL
-
MBSFN EARFCN
mbsfnEarfcn
MBSFN
-
Sales information Table 123
LTE3092 sales information
Product structure class Application Software (ASW)
188
License control -
DN09237915
Activated by default No
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of radio resource management and telecom features
3.29 LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells Benefits, functionality, system impact, and reference data of the feature The LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature provides support for the unlicensed national information infrastructure-1 (UNII-1) and UNII-3 bands. LTE Unlicensed (LTE-U)-capable small cells can alternately scan the two bands and select the least loaded unlicensed channel from one of the 5-GHz UNII bands.
3.29.1 LTE3093 benefits The LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature provides better frequency range in the unlicensed 5-GHz spectrum to support LTE-U for supplemental downlink capacity.
3.29.2 LTE3093 functional description The LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature provides support of unlicensed LTE bands UNII-1 and UNII-3 for supplemental downlink (SDL) transmission to the Flexi Zone BTS with LTE-U-capable hardware. LTE-U is deployed in the 5-GHz spectrum. The following are the frequency ranges supported: • •
UNII-1: 5150-5250 MHz (band 252) UNII-3: 5735-5835 MHz (band 255)
The LTE2424: LTE-U (2CC) Support for Dual-band Indoor/Outdoor FZ BTS (Pre-Rel 13) feature only provides support of LTE-U band UNII-3 for SDL transmission. It is possible to perform SDL transmission to UEs through a secondary cell (SCell) that uses a secondary component carrier (SCC) from either the UNII-1 band or the UNII-3 band with the LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature. The bandwidth of the frequency ranges supported in both bands is 100 MHz each. However, only four 20-MHz channels in the UNII-1 band can be used because of hardware limitation. The Flexi Zone BTS scans all the five 20-MHz channels of each band alternately every 500 ms and collects the received signal strength indicator (RSSI) from each channel. The channel activity measurement (CAM) reports that contain the RSSI information are processed periodically to select the carrier from one of the nine channels (four channels of UNII-1 band are used) as the SCC for LTE-U SDL transmission. The least loaded carrier is the selected SCC. The scanning is done during OFF period. The Flexi Zone BTS scans all the five 20-MHz channels of the UNII-3 band once every 500 ms, and the CAM reports are received every 500 ms with the LTE2424: LTE-U (2CC) Support for Dual-band Indoor/Outdoor FZ BTS (Pre-Rel 13) feature. The OFF period is always the first LTE frame in the 500-ms interval. With the LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature, each band is scanned alternately every 500 ms. Therefore, if both bands are configured, the CAM reports are received only once every second. With the LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature, the OFF period used to scan in both 500-ms intervals is configurable.
Issue: 01 Draft
DN09237915
189
Descriptions of radio resource management and telecom features
FDD-LTE16A, Feature Descriptions and Instructions
The LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature uses the dual band indoor Flexi Zone Pico BTS which the LTE2357: B4/66+Unlic FZ G2 Indoor MultiBand Pico (FW2IRA, FW2IRWA, FW2IRWC) feature has introduced. The RF module hardware incorporates a change for support of UNII-1 band.
3.29.3 LTE3093 system impact LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells impact on features, and system performance and capacity Interdependencies between features The LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature is dependent on the following features: •
•
•
LTE2357: B4/66+Unlic FZ G2 Indoor Multi-band Pico (FW2IRA, FW2IRWA, FW2IRWC) This feature introduces a dual-band indoor pico platform that supports a 3GPP licensed band and a 5-GHz unlicensed band. LTE2424: LTE-U (2CC) Support for Dual-band Indoor/Outdoor FZ BTS (Pre-Rel 13) This feature introduces a software support for downlink carrier aggregation (CA) with 5-GHz unlicensed spectrum. The feature provides prestandard implementation of LTE in the unlicensed spectrum. LTE3092: Enhanced CSAT Support for LTE-U Small Cells This feature introduces software support for downlink CA with 5-GHz unlicensed spectrum (UNII-1 and UNII-3). The feature uses an enhanced carrier sensing adaptive transmission (CSAT) algorithm to provide a prestandard implementation of LTE in the unlicensed spectrum. The feature is released with the LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature. Therefore, it assumes Flexi Zone support of UNII-1 and UNII-3 bands for SDL transmission in the SCell.
Impact on interfaces The LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature has no impact on interfaces. Impact on network management tools The LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature has no impact on network management tools. Impact on system performance and capacity The impact on system performance and capacity is the same as in the LTE3092: Enhanced CSAT Support for LTE-U Small Cells feature. For more information, see the LTE3092: Enhanced CSAT Support for LTE-U Small Cells reference data.
3.29.4 LTE3093 reference data LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells requirements, measurements and counters, parameters, and sales information Requirements
190
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 124
Descriptions of radio resource management and telecom features
LTE3093 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FDD-LTE 16A
Not supported
Not supported
Not supported
Flexi Zone Controller
OMS
UE
NetAct
FL16A
LTE OMS16A
Support not required
Support not required
Flexi Zone Micro BTS FL16A
Flexi Zone Access Point FL16A
MME Support not required
SAE GW Support not required
Alarms There are no alarms related to the LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature. Commands There are no commands related to the LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature. Measurements and counters Table 125
New counters introduced by LTE3093
Counter ID
Counter name
Measurement
M8050C0
Long Term LTE-U CAM Average for Channel 1
LTE LTE-U/LAA Resource
M8050C1
Long Term LTE-U CAM Average for Channel 2
LTE LTE-U/LAA Resource
M8050C2
Long Term LTE-U CAM Average for Channel 3
LTE LTE-U/LAA Resource
M8050C3
Long Term LTE-U CAM Average for Channel 4
LTE LTE-U/LAA Resource
M8050C4
Long Term LTE-U CAM Average for Channel 5
LTE LTE-U/LAA Resource
M8050C5
LTE-U Channel Change Count
LTE LTE-U/LAA Resource
M8050C6
Long Term LTE-U CAM Average for Channel 6
LTE LTE-U/LAA Resource
M8050C7
Long Term LTE-U CAM Average for Channel 7
LTE LTE-U/LAA Resource
M8050C8
Long Term LTE-U CAM Average for Channel 8
LTE LTE-U/LAA Resource
M8050C9
Long Term LTE-U CAM Average for Channel 9
LTE LTE-U/LAA Resource
Key performance indicators There are no key performance indicators related to the LTE3093: UNII-1 and UNII-3 Support for LTE-U Small Cells feature. Parameters
Issue: 01 Draft
DN09237915
191
Descriptions of radio resource management and telecom features
Table 126
FDD-LTE16A, Feature Descriptions and Instructions
New parameters introduced by LTE3093 Full name
Abbreviated name
Managed object
Parent structure
LNUPR
-
WIFI channels selection uCellChannelSList LNUPR list
-
CAM Bitmap Offset
camBitmapOffset
Sales information Table 127
LTE3093 sales information
Product structure class Basic Software (BSW)
192
License control -
DN09237915
Activated by default Yes
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of transport and transmission features
4 Descriptions of transport and transmission features 4.1 LTE563: Synchronous Ethernet Generation With the LTE563: Synchronous Ethernet Generation feature, the eNB can generate a frequency-synchronized output signal to other base stations via its transport Ethernet ports (SyncE master). The frequency synchronization of the SyncE outgoing signal can be derived from different synchronization sources. The eNB uses the same source for both its own synchronization and for SyncE output(s).
4.1.1 LTE563 benefits The LTE563: Synchronization Ethernet Generation feature provides the following benefit: There is no need for an additional cable or grandmaster load (as in timing over packet). It is possible due to the fact that Synchronous Ethernet generation allows collocated/daisy chained BTS to obtain frequency synchronization on the already connected Ethernet link needed for backhaul traffic.
4.1.2 LTE563 functional description The objective of the LTE563: Synchronous Ethernet Generation feature is to enable generating/regenerating the synchronous Ethernet signal in the eNB and thus enhancing the use of synchronous Ethernet locally at a site and also between different sites. The eNB can generate an output synchronous Ethernet signal from the following synchronization inputs: • • • •
• • • •
the plesiochronous digital hierarchy (PDH) interface, see Figure 18: SyncE master functionality in eNB – E1/T1/JT1, 1 pps or ext. 2M048 is synchronization reference the 2.048-MHz interface, see Figure 18: SyncE master functionality in eNB – E1/T1/JT1, 1 pps or ext. 2M048 is synchronization reference 1 pps/time of day (ToD) sync from sync hub master, see Figure 18: SyncE master functionality in eNB – E1/T1/JT1, 1 pps or ext. 2M048 is synchronization reference 1 pps/ToD sync from an internal/external GNSS receiver (Internal GNSS receiver not supported in FDD), see Figure 18: SyncE master functionality in eNB – E1/T1/JT1, 1 pps or ext. 2M048 is synchronization reference Timing over packet (ToP) with frequency synchronization, see Figure 17: SyncE master functionality – ToP is synchronization reference Timing over packet with phase synchronization, see Figure 17: SyncE master functionality – ToP is synchronization reference Synchronous Ethernet, Figure 16: SyncE master functionality – SyncE is synchronization reference ) BTS clock during holdover/free run, see Figure 19: SyncE master functionality in an eNB holdover mode
The synchronous Ethernet output is supported on optical and electrical transport backhaul interfaces.
Issue: 01 Draft
DN09237915
193
Descriptions of transport and transmission features
FDD-LTE16A, Feature Descriptions and Instructions
It is possible to synchronize up to seven hops maximum in a SyncE chain of eNBs/BTSs with this feature. Moreover, the eNB can optionally inform the subsequent nodes about the clock quality level, sending out a synchronization status message (SSM). The use of synchronous Ethernet generation on the FSMF system module requires a FTIF transport sub-module. All transport interfaces of the eNB can serve as SyncE master ports then, with the exception, that if the eNB itself is synchronized by SyncE, the used interface for Sync-in is a slave port. Synchronous Ethernet generation on the FSIH system module works without a separate transport sub-module. The following figures provide an overview of the SyncE master functionality. • • • •
Figure 16: SyncE master functionality – SyncE is synchronization reference Figure 17: SyncE master functionality – ToP is synchronization reference Figure 18: SyncE master functionality in eNB – E1/T1/JT1, 1 pps or ext. 2M048 is synchronization reference Figure 19: SyncE master functionality in an eNB holdover mode
Figure 16: SyncE master functionality – SyncE is synchronization reference shows the eNB SyncE master functionality when the eNB receives synchronization reference from SyncE (only applicable to FDD eNB). Figure 16
SyncE master functionality – SyncE is synchronization reference
SSM generator
SSM terminator Synchronous Ethernet
SSM
(SSM)
PHY
PHY PHY
Master
Slave clock
PDH 1pps ext. 2M048
ToP
syncIn
others
Synchronous Ethernet
EEC
Clock Generator
BTSwithSyncE masterandslave
Figure 17: SyncE master functionality – ToP is synchronization reference shows the eNB SyncE generation functionality when the eNB SyncE master receives a timing signal recovered from timing over packet (ToP) synchronization reference. Figure 17
194
SyncE master functionality – ToP is synchronization reference
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of transport and transmission features
SSM terminator
SSM generator SSM
PTP IP/Ethernet
PHY
PHY PHY
Synchronous Ethernet Master
EEC
ToP clock SyncIn
others
PDH ext. 2M048
Clock Generator
BTSwithSyncE master Figure 18: SyncE master functionality in eNB – E1/T1/JT1, 1 pps or ext. 2M048 is synchronization reference shows the eNB SyncE master functionality when the eNB SyncE generator receives synchronization reference from E1/T1/JT1, 1 pps or ext. 2M048. Figure 18
SyncE master functionality in eNB – E1/T1/JT1, 1 pps or ext. 2M048 is synchronization reference
SSM terminator
SSM generator SSM
data Ethernet
1pps/ToD
1pps /ToD
Master EEC
ToP
PDH ext. clock 2M048
SyncIn
others
PHY
PHY PHY
Synchronous Ethernet
Clock Generator
BTSwithSyncE master Figure 19: SyncE master functionality in an eNB holdover mode shows the eNB SyncE master functionality when the eNB is in a holdover mode.
Issue: 01 Draft
DN09237915
195
Descriptions of transport and transmission features
Figure 19
FDD-LTE16A, Feature Descriptions and Instructions
SyncE master functionality in an eNB holdover mode
SSM terminator
SSM generator SSM
data Ethernet
PHY
PHY PHY 1pps /ToD
1pps/ToD
Master EEC
ToP
SyncIn
PDH ext. 2M048
others
Synchronous Ethernet
Clock Generator
BTSwithSyncE master
4.1.3 LTE563 system impact Interdependencies between features There are no interdependencies between the LTE563: Synchronous Ethernet Generation feature and any other feature. Impact on interfaces The LTE563: Synchronous Ethernet Generation feature has no impact on interfaces. Impact on network management tools The LTE563: Synchronous Ethernet Generation feature has no impact on network management tools. Impact on system performance and capacity The LTE563: Synchronous Ethernet Generation feature has no impact on system performance or capacity.
4.1.4 LTE563 reference data Requirements Table 128
196
LTE563 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE16A
not supported
Flexi Multiradio 10 BTS
Nokia Airscale BTS
FL16A
support not required
DN09237915
Flexi Zone Micro BTS
Flexi Zone Access Point
not applicable
not applicable
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 128
Descriptions of transport and transmission features
LTE563 hardware and software requirements (Cont.)
Flexi Zone Controller
OMS
UE
not supported
LTE OMS16A
support not required
NetAct
MME
support not required
support not required
SAE GW support not required
Alarms Table 129
Existing alarms related to LTE563
Alarm ID 7107
Alarm name
BASE STATION CONNECTIVITY PROBLEM
Table 130
New BTS faults related to LTE563
Fault ID
61607
Fault name
Reported alarms Alarm ID
Auto-negotiation mismatch
7107
Alarm name
BASE STATION CONNECTIVITY PROBLEM
Measurements and counters There are no measurements or counters related to the LTE563: Synchronous Ethernet Generation feature. Key performance indicators There are no key performance indicators related to the LTE563: Synchronous Ethernet Generation feature. Parameters Table 131
New parameters Full name
Abbreviated name
Managed object
Synchronous Ethernet Autonegotiation mode syncEAutoNegMode
ETHLK
Feature activation flag for Synchronous Ethernet Generation
actSyncEGen
SYNC
Synchronous Ethernet SSM selection for 1PPS/ToD and Fronthaul source
ssmSel1ppsTodFh
STPG
Synchronous Ethernet SSM selection for 2.048 MHz synchronization source
ssmSelExt2M
STPG
Synchronous Ethernet SSM selection for PDH synchronization source
ssmSelPDH
STPG
Synchronous Ethernet SSM selection for SyncE source
ssmSelSyncE
STPG
Synchronous Ethernet SSM support network standard
ssmType
STPG
Sales information
Issue: 01 Draft
DN09237915
197
Descriptions of transport and transmission features
Table 132
FDD-LTE16A, Feature Descriptions and Instructions
LTE563 sales information
Product structure class
License control
Application software (ASW)
SW Asset Monitoring
Activated by default No
4.2 LTE1554: 10GBase-SR Optical GE Interface, LTE1652: Small Form Factor Pluggable (Plus) Slot (SFP/SFP+ Slot), LTE1738: 10GBase-LR Optical GE Interface With the LTE1652, LTE1554, and LTE1738 features, a new slot for small form factor pluggable (SFP) transceiver and SFP+ transceiver is introduced. The SFP+ slot supports optical 10-Gigabit Ethernet (10GE) interfaces of type 10GBase-LR and 10GBase-SR, which are developed by Nokia. Multi-sourcing agreement (MSA) transceiver modules according to SFF-8074 (SFP) and SFF-8431, SFF-8432 (SFP+) with a limiting amplifier are supported.
4.2.1 LTE1554, LTE1652, LTE1738 benefits The LTE1554: 10GBase-SR Optical GE Interface, LTE1652: Small Form Factor Pluggable (Plus) Slot (SFP/SFP+ Slot), LTE1738: 10GBase-LR Optical GE Interface features provide the following benefits: • • •
The small form factor pluggable plus slot (SFP+ slot) supports 10-Gigabit Ethernet interfaces (LTE1652). Optical 10-Gigabit Ethernet interfaces of type 10GBase-SR (short reach) are supported (LTE1554). Optical 10-Gigabit Ethernet interfaces of type 10GBase-LR (long reach) are supported (LTE1738).
The new optical 10-Gigabit Ethernet interfaces are developed by Nokia.
4.2.2 LTE1554, LTE1652, LTE1738 functional description SFP/SFP+ slot (LTE1652) The LTE1652: Small Form Factor Pluggable (Plus) Slot (SFP/SFP+ Slot) feature makes an SFP/SFP+ slot available by providing generic functions usable with SFP/SFP+ transceiver modules. The mechanical slot for plugging in multi-sourcing-agreement (MSA)-compliant SFP/SFP+ transceiver modules provides: • • • • • •
Module detection SFP transceiver type validation Basic SFP diagnostic support Up to 2.5 Watt SFP transceiver power consumption Loss of signal (LOS) detection pin support Field pluggable/replacable
Utilized SFP/SFP+ transceiver modules have to: •
198
be compliant with an industrial temperature range from -40°C to +85°C
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• •
g
Descriptions of transport and transmission features
be Laser Class1 compliant provide extraction bail latch actuator Note: Do not use SFPs with MSA direct/standard push pull, dog leg latch actuator, with plastic pull tab, or without any extraction handle. Only Nokia branded SFP+ transceivers are supported.
Utilized SFP+ tranceiver modules have to provide a limiting amplifier (modules with linear amplifier are not supported). Figure 20: SFP+ slot shows the small form factor pluggable slot (plus) (SFP+ Slot). Figure 20
SFP+ slot EIF1/2:optionalSFP+1/10GE
DC in
groundingconnector
EAC
SyncIN
SyncOUT
SEI1 SEI2
SRIO1
EIF1
SRIO2
EIF2
EIF3
EIF4
EIF5
LMP
10GBase-SR optical GE interface (LTE1554) The LTE1554: 10GBase-SR Optical GE Interface feature provides the capability to operate a 10-Gigabit Ethernet interface of type 10GBase-SR (short reach) at the transport SFP+ slot. 10GBase-SR according to IEEE802.3-2008, clause 49, 51 and 52: • • • • • •
Wavelength: 850 nm Up to a 33-m distance with a 62.5-um multimode fiber, up to a 300-m distance with 50-um multimode fiber Full-duplex transmission mode only Supported via an optional SFP+ transceiver module (SFF-8431, SFF-8432, SFF committee) with a limiting amplifier Auto-negotiation is not defined anymore with IEEE802.3-2008 for 10-Gigabit Ethernet interfaces of the family 10GBase-R. No support for the FEC option per IEEE802.3-2008 clause 74.
Figure 21: 10GBase interface shows an example of the 10GBase-SR/LR optical 10Gigabit Ethernet interface, which can be used for the SFP+ slot.
Issue: 01 Draft
DN09237915
199
Descriptions of transport and transmission features
Figure 21
FDD-LTE16A, Feature Descriptions and Instructions
10GBase interface
10GBase-LR optical GE interface (LTE1738) The LTE1738: 10GBase-LR Optical GE Interface feature enables operating a 10-Gigabit Ethernet interface of type 10GBase-LR (long reach) at the transport SFP+ slot. 10GBase-LR according to IEEE802.3-2008, clause 49, 51 and 52: • • • • • •
Wavelength: 1310 nm Up to a 10-km distance with a single mode fiber Full-duplex transmission mode only Supported via an optional SFP+ transceiver module (SFF-8431, SFF-8432, SFF committee) with a limiting amplifier Auto-negotiation is not defined anymore with IEEE802.3-2008 for 10-Gigabit Ethernet interfaces of the family 10GBase-R. No support for the FEC option per IEEE802.3-2008 clause 74.
4.2.3 LTE1554, LTE1652, LTE1738 system impact The LTE1554: 10GBase-SR Optical GE Interface, LTE1652: Small Form Factor Pluggable (Plus) Slot (SFP/SFP+ Slot), LTE1738: 10GBase-LR Optical GE Interface features have no impact on other features, interfaces, network management tools, and system performance and capacity.
g
Note: Connections, and here Ethernet connections via SFPs, are relevant life lines between eNBs ↔ Backhaul, and eNBs ↔ eNBs. So as long as eNB interfaces, operating and equipped with LTE1554, and/or LTE1652, and/or LTE1738, are working well the SFPs do not affect services.
4.2.4 LTE1554, LTE1652, LTE1738 reference data Requirements
200
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 133
Descriptions of transport and transmission features
LTE1554, LTE1652, LTE1738 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FDD-LTE16A
not supported
not supported
FL16A
Flexi Zone Controller
OMS
UE
not supported
support not required
support not required
NetAct support not required
Flexi Zone Micro BTS
Flexi Zone Access Point
not supported
not supported
MME
SAE GW
support not required
support not required
BTS faults and reported alarms Table 134
Existing BTS faults used by LTE1554, LTE1652, LTE1738
Fault ID
Fault name
Reported alarms Alarm ID
Alarm name
61050
Missing or non-compliant SFP module on unit $U, interface $IF
7665
BASE STATION TRANSMISSION ALARM
61079
SFP HW Failure
7665
BASE STATION TRANSMISSION ALARM
61029
LOS on unit $U, [Ethernet] interface $IF
7665
BASE STATION TRANSMISSION ALARM
For fault descriptions, see LTE Radio Access Operating Documentation/Reference/Alarms. Commands There are no commands related to the LTE1554, LTE1652, LTE1738 features. Measurements and counters There are no measurements or counters related to the LTE1554, LTE1652, LTE1738 features. Key performance indicators There are no key performance indicators related to the LTE1554, LTE1652, LTE1738 features. Parameters Table 135
Parameters modified by LTE1554, LTE1652, LTE1738 Full name
Issue: 01 Draft
Abbreviated name
Managed object
Speed and duplex configuration
speedAndDuplex
ETHLK
Layer 2 switch member ingress limiting rate
l2IngressRate
ETHLK
DN09237915
201
Descriptions of transport and transmission features
Table 135
FDD-LTE16A, Feature Descriptions and Instructions
Parameters modified by LTE1554, LTE1652, LTE1738 (Cont.) Full name
Abbreviated name
Managed object
Layer 2 switch member egress l2ShaperRate shaping rate
ETHLK
Shaper information rate
sir
IVIF
Shaper information rate
sir
IEIF
Total shaper information rate
sirTotal
IEIF
They are IEIF:sir, IVIF:sir, ETHLK:speedAndDuplex, ETHLK:l2IngressRate, ETHLK:l2ShaperRate, IEIF:sirTotal. For parameter descriptions, see LTE Radio Access Operating Documentation/ Reference/Parameters. Sales information Table 136
LTE1554, LTE1652, LTE1738 sales information
Product structure class Basic Software (BSW)
License control Pool license
Activated by default Yes
4.3 LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels The LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels feature complements the IPv6 support in the eNB by enabling the IPv6 also for the IPsec functionality. With this feature, the IPsec tunnels can use both IPv4 and IPv6 endpoints for tunnel origination or termination.
4.3.1 LTE1980 benefits The LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels feature provides the following benefits: • • •
flexible configuration of IPv4 and/or IPv6 IPsec policies support of a combination of IPv4 and IPv6 tunnels on the same BTS IPv4 application traffic can be carried inside IPv6 tunnel or the other way around
4.3.2 LTE1980 functional description Internet Protocol Security (IPsec) is a protocol suite which provides confidentiality and integrity protection for the eNB traffic. IPsec provides three essential security functions: • • •
202
confidentiality, through the use of encryption integrity, through the use of checksums authentication
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of transport and transmission features
These functions are performed by creating a dedicated VPN tunnel to carry the traffic. Tunneling also ensures separation of different types of traffic, for example, control, user, synchronization, and management plane traffic. The IPsec tunnel is created between two endpoints: the eNB and security gateway. Figure 22
Overview of IPsec implementation in LTE O&M network
Certificate revocation server
NetAct OMS
LDAP
Certification authority
CMP
BTSO&M (overTLS)
Security Gateway
IPsec tunnel
eNB BTS Site Manager
BTSSM (overTLS)
For more information on the IPsec protocol, see LTE Operating Documentation/Integrate and Configure/Configuring Security in eNB/IPsec support. The LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels feature does not change the existing IPsec functionality. It only updates the IPsec policies with the possibility to configure the IPv6 addresses for • • • • • • •
Issue: 01 Draft
local IPsec tunnel endpoint IP address remote IPsec tunnel endpoint IP address IPsec emergency bypass control server IP address IPsec backup tunnel remote endpoint IPSec backup tunnel current remote endpoint IPsec local tunnel endpoint IPsec remote tunnel endpoint
DN09237915
203
Descriptions of transport and transmission features
Figure 23
FDD-LTE16A, Feature Descriptions and Instructions
IPv6 in the IPsec policy
4.3.3 LTE1980 system impact Interdependencies between features The LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels feature is an independent feature (does not require activation of any other feature). However, it complements the following IPv6 features: • • • •
LTE125: IPv6 for C/U-plane LTE2299: Dualstack IPv4/IPv6 for S1/X2 LTE955: IPv4/IPv6 for Management Plane LTE1981: IPv6 for S-Plane
and the following IPsec features: • • •
LTE689: LTE IPsec Support LTE1753: Backup IPsec Tunnel LTE1390: IPsec Emergency Bypass
Impact on interfaces The LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels feature has no impact on interfaces. Impact on network management tools The LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels feature has no impact on network management tools. Impact on system performance and capacity The LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels feature has no impact on system performance or capacity.
204
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of transport and transmission features
4.3.4 LTE1980 reference data Requirements Table 137
LTE1980 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE16A
not supported
Flexi Zone Controller
OMS
not supported
OMS16A
Flexi Multiradio 10 BTS
AirScale BTS
FL16A
FL16A
UE support not required
Flexi Zone Micro BTS
Flexi Zone Access Point
not supported
not supported
MME
SAE GW
NetAct 16.8
support not required
support not required
Alarms There are no alarms related to the LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels feature. Commands There are no commands related to the LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels feature. Measurements and counters There are no measurements or counters related to the LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels feature. Key performance indicators There are no key performance indicators related to the LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels feature. Parameters There are no new parameters related to the LTE1980: IPv4/IPv6 Concurrent IPsec Tunnels feature. Sales information Table 138
LTE1980 sales information
Product structure class Application software (ASW)
License control Pool licence
Activated by default Yes
4.4 LTE1981: IPv6 for S-plane The LTE1981: IPv6 for S-plane feature supports the timing over packet (ToP) synchronization (IEEE1588) based on the precision time protocol (PTP) over IPv6 transport.
4.4.1 LTE1981 benefits The LTE1981: IPv6 for S-plane feature provides the following benefits: It complements the IPv6 support in the eNB by introducing the IPv6 transport option also for the synchronization plane (S-plane). So this feature allows the migration to IPv6 for the ToP synchronization feature.
Issue: 01 Draft
DN09237915
205
Descriptions of transport and transmission features
FDD-LTE16A, Feature Descriptions and Instructions
4.4.2 LTE1981 functional description The LTE1981: IPv6 for S-plane feature enables the eNB to send and receive timing over packet (ToP) protocol data via IPv6 packets. It is shown in Figure 24: LTE1981 Overview. Figure 24
LTE1981 Overview
TimingoverPacket(IEEE1588-2008) (phase-orfrequency-synchronisation)
ToP slave
~
~ BTS
ToP master(s)/BoundaryClock
IPv6/Ethernet
PTP(IEEE1588) UDP IPv6 Ethernet The Synchronization plane application IP address (sPlaneIpAddress) parameter specifies the IP address to be used for the synchronization plane traffic. The parameter supports one IP address, but both IP versions: Either one IPv4 or one IPv6 address. • •
For IPv4, the parameter has to be entered in dotted decimal format. For IPv6, the parameter has to be entered according to formats specified in RFC2460.
The Timing over Packet masters properties table (topMasters) structure specifies a table that holds all properties of the configured Timing over Packet masters of the BTS. Up to four ToP masters can be administered in this table.
4.4.3 LTE1981: system impact Interdependencies between features The LTE1981: IPv6 for S-plane feature impacts the following features: •
LTE610: Timing over Packet Resilience When using IPv6 for S-plane, the IP address version of all configured timing over packet (ToP) servers in the eNB must be IPv6 too.
Impact on interfaces The LTE1981: IPv6 for S-plane feature has no impact on interfaces. Impact on network management tools The LTE1981: IPv6 for S-plane feature has no impact on network management tools. Impact on system performance and capacity The LTE1981: IPv6 for S-plane feature impacts system performance and capacity as follows:
206
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
Descriptions of transport and transmission features
With IPv6 addressing, the system address spacing will increase significantly in the whole network. However, the number of IP addresses per NE does not change.
4.4.4 LTE1981 reference data Requirements Table 139
LTE1981 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
not supported
Flexi Zone Controller
OMS
support not required
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL16A
UE
LTE OMS 16A support not required
Flexi Zone Micro BTS support not required
NetAct
Flexi Zone Access Point not applicable
MME
NetAct 16.8
SAE GW
support not required
support not required
Alarms There are no alarms related to the LTE1981: IPv6 for S-plane feature. BTS faults and reported alarms There are no faults related to the LTE1981: IPv6 for S-plane feature. Measurements and counters There are no measurements or counters related to the LTE1981: IPv6 for S-plane feature. Key performance indicators There are no key performance indicators related to the LTE1981: IPv6 for S-plane feature. Parameters Table 140
Existing parameters related to LTE1981 Full name
Issue: 01 Draft
Abbreviated name
Managed object
Parent structure
Feature Activation Flag ToP with actTopFreqSynch freq synchronization
TOPF
-
Feature Activation Flag ToP with actTopPhaseSynch phase synchronization
TOPP
-
Timing over Packet masters properties table
topMasters
TOPF
Master visibility
masterVisibility
TOPF
topMasters
IP Address of the ToP master
masterIpAddr
TOPF, TOPP
topMasters
Configured priority 1 for ToP master
priority_1
TOPF
topMasters
Configured priority 2 for ToP master
priority_2
TOPF
topMasters
ToP Master lock status
lockState
TOPF
topMasters
ToP Master working status
masterClockState
TOPF
topMasters
DN09237915
207
Descriptions of transport and transmission features
Table 140
FDD-LTE16A, Feature Descriptions and Instructions
Existing parameters related to LTE1981 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
Received clock quality level from receivedClockQuality master
TOPF
topMasters
Received priority 1 for ToP master
receivedPriority_1
TOPF
topMasters
Received priority 2 for ToP master
receivedPriority_2
TOPF
topMasters
ToP Master active status
topMasterActive
TOPF
topMasters
Synchronization plane application IP address
sPlaneIpAddress
IPNO
-
Sales information Table 141
LTE1981 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
4.5 LTE2417 IP Traffic Capacity The LTE2417: IP Traffic Capacity feature enables monitoring and controlling IP transport capacity licenses. Nokia trades in two different types of IP capacity licenses: • •
Daily IP traffic volume of the user-plane data Quarterly (90 days) IP traffic volume of user-plane data
The eNB measures the traffic and sends measurement results to the NetAct, where the Software Entitlement Management (SWEM) assesses how they fit the allocated IP transport capacity.
4.5.1 LTE2417 benefits The LTE2417: IP Traffic Capacity feature provides the following benefits: • •
•
•
208
The operator can align his LTE software capacity costs with the subscriber revenues and profits so that he can justify a higher OPEX. The operator can see the current and historical information on the capacity usage; thus, he can predict future needs and act quickly on capacity bottleneck or licensed capacity quota excess. The operator can notice traffic limitations due to licensed capacity quota excess immediately. This prevents unnecessary corrective actions and helps to directly address the issue by forwarding the information to the procurement department to increase the capacity of license pool. The operator can use an automated license management so that no manual work is required.
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of transport and transmission features
4.5.2 LTE2417 functional description Overview Figure 25: Overview of the LTE2417: IP Traffic Capacity feature shows a context diagram for the LTE2417: IP Traffic Capacity feature. Figure 25
Overview of the LTE2417: IP Traffic Capacity feature
eNB
S-GW Userplane trafficcounter (15-minutes)
Capacity used
Common LicenseServer
License Violation
Activecapacity limitation
-daily -quarterly
SWEM
PM/CM NetAct
Each eNB counts the user-plane data traffic in one 15-minute interval counter. This counter contains the total of uplink and downlink traffic volume for the S1-U (X2 traffic is excluded). NetAct retrieves the counter values from all eNBs. KPI In the NetAct the Software Entitlement Manager (SWEM) calculates key performance indicators for each eNB: •
•
KPI average daily IP traffic volume of the last 14 days: summing up 15-minute userplane-traffic counter values for each day and averaging over 14 days (rolling window). KPI quarterly IP traffic volume: the sum total of the last 90 values of daily IP traffic volume.
Figure 26: KPI generation summarizes the calculation of the KPIs by using an intermediate step in NetAct PM that determines the KPI daily IP traffic volume of a day.
Issue: 01 Draft
DN09237915
209
Descriptions of transport and transmission features
Figure 26
FDD-LTE16A, Feature Descriptions and Instructions
KPI generation eNB
15-minutes IPTrafficVolume
KPIDaily IPTrafficVolume
KPIAverageDaily IPTrafficVolume
KPIQuartely IPTrafficVolume
NetAct PM
NetAct SWEM
Figure 27: KPI average daily IP traffic volume sketches the calculation of KPI average daily IP traffic volume: • • •
210
A BTS delivers the 15-minute-period IP traffic volume counter to NetAct. NetAct sums up all the 15-minute interval values over an entire day (0:15 to 24:00). SWEM averages the values of the last 14 days (sum of 14 days/14).
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Figure 27
Descriptions of transport and transmission features
KPI average daily IP traffic volume
Day:31.12.14
Day:2.1.15
Day:1.1.15
15-minutes IPtraffic volume
BTS
0:00
6:00
12:00
KPIdailyIP trafficvolume
24:00
18:00
Sumof96samples startingat0:00to23:45 NetActPM
30.12 31.12
1.1
2.1
3.1
4.1
5.1
6.1
7.1
8.1
9.1
10.1
11.1
12.1
13.1
14.1
KPIaverage dailyIP trafficvolume Sumofthelast14daily IPtrafficvolumevalues/14 SWEM
30.12 31.12
1.1
2.1
3.1
4.1
5.1
6.1
7.1
8.1
9.1
10.1
11.1
12.1
13.1
14.1
Figure 28: KPI quarterly IP traffic volume sketches the calculation of the KPI quarterly IP traffic volume: • • •
Issue: 01 Draft
A BTS delivers the 15-minute-period IP traffic volume counter to NetAct. NetAct sums up all the 15-minute interval values over an entire day (0:15 to 24:00). SWEM sums up the values of the last 90 days.
DN09237915
211
Descriptions of transport and transmission features
Figure 28
FDD-LTE16A, Feature Descriptions and Instructions
KPI quarterly IP traffic volume
Day:31.12.14
Day:2.1.15
Day:1.1.15
15-minutes IPtraffic volume
BTS
0:00
6:00
12:00
KPIdailyIP trafficvolume
24:00
18:00
Sumof96samples startingat0:15to24:00 NetActPM
30.12 31.12
1.1
2.1
3.1
4.1
5.1
6.1
7.1
8.1
9.1
10.1
11.1
KPIquarterly IPtrafficvolume
12.1
13.1
14.1
Sumofthelast90daily trafficvolumevalues SWEM
30.12 31.12
1.1
2.1
3.1
4.1
5.1
6.1
7.1
8.1
9.1
10.1
11.1
12.1
13.1
14.1
Software Entitlement Manager (SWEM) The Software Entitlement Manager (SWEM) allocates capacity from the capacity license pool maintained in the Centralised SW License Server (CLS). The license pool contains all the capacity that the mobile network operator purchases for his network from Nokia. SWEM checks the consumed capacity (indicated by the used KPI, the default KPI is average daily IP traffic volume) against the allocated capacity for a given BTS. If the consumed capacity exceeds above the allocated capacity, SWEM attempts to allocate more IP traffic capacity from the capacity license pool, managed by the CLS. In case of the capacity of the CLS pool has been used up, SWEM is initiating a limitation action (CM command) to reduce the throughput of that eNodeB.The limitation will start smoothly, but will become impacting more and more over time. There will be a weekly throughput reduction up to 50 %.The traffic limitation starts at 100% of maximum traffic rate and is reduced by 5% - 6% every week down to 50% until CLS is refilled with new licenses. The current traffic volume and throughput can be retrieved by SWEM data. Subject for packet dropping is the low priority traffic in downlink. Once the limitation is enabled the eNB controls the peak rate of this traffic (leaky bucket). If the consumed capacity does not exceed the allocated capacity, SWEM does not free capacity. Alarms / License Violation
212
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of transport and transmission features
The operator will get two alarms: SWEM sends the LICENSE CAPACITY NOT AVAILABLE alarm after SWEM has detected that the license capacity quota is exceeded. Then the operator has a 14 days grace period during which he can load a new capacity license. Was this not done in the grace period the eNB sends the 7658: BASE STATION LICENSE LIMITATION alarm.
4.5.3 LTE2417 system impact Interdependencies between features The following features are a prerequisite for the LTE2417: IP Traffic Capacity feature: •
•
•
LTE2593: SW License Management in LTE The LTE2593: SW License Management in LTE feature introduces a mechanism for LTE software license management. Capacity units, high value features, and hardware activation features can be blocked by applying that license framework. LTE2621: eNodeB Limitation Actions for License Management in LTE The LTE2621: eNodeB Limitation Actions for License Management in LTE feature introduces the action for limiting capacities in connection with NetAct License Management. LTE2414: Transport Overload Protection The LTE2414: Transport Overload Protection feature specifies a vendor-specific differentiated service code point (DSCP) value list for low-priority traffic. The entries in this vendor are used by LTE2417 to define the user-plane-traffic subject for traffic guard policing. LTE2417 requires only this vendor list, not the full functionality of LTE2414.
Impact on interfaces The LTE2417: IP Traffic Capacity feature has no impact on interfaces. Impact on network management tools The LTE2417: IP Traffic Capacity feature has no impact on network management tools. Impact on system performance and capacity The LTE2417: IP Traffic Capacity feature impacts system performance and capacity as follows: •
According to the capacity license, the IP capacity is controlled by the LTE2417 feature.
4.5.4 LTE2417 reference data Requirements Table 142 System release FDD LTE16A
Flexi Zone Controller support not required
Issue: 01 Draft
LTE2417 hardware and software requirements Flexi Multiradio BTS not supported
OMS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
support not required
UE
LTE OMS 16A support not required
DN09237915
NetAct NetAct 16.8
Flexi Zone Micro BTS support not required MME support not required
Flexi Zone Access Point support not required SAE GW support not required
213
Descriptions of transport and transmission features
FDD-LTE16A, Feature Descriptions and Instructions
Alarms Table 143
New alarms introduced by LTE2417
Alarm ID
Alarm name
7658
BASE STATION LICENSE LIMITATION
BTS faults and reported alarms Table 144
New BTS faults introduced by LTE2417
Fault ID
4293
Fault name
Reported alarms Alarm ID
IP Traffic Capacity Limit
7658
Alarm name
BASE STATION LICENSE LIMITATION
Measurements and counters Table 145
New counters introduced by LTE2417
Counter ID
Counter name
Measurement
M51148 ipDataTrafficVolume C0
LTE IP Data Traffic Volume Statistics
M51148 ipDataTrafficVolumeDiscards C1
LTE IP Data Traffic Volume Statistics
M51148 ipDataTrafficVolumePackets C2
LTE IP Data Traffic Volume Statistics
M51148 ipDataTrafficVolumePckDisc C3
LTE IP Data Traffic Volume Statistics
Key performance indicators There are no KPIs for this feature. Parameters Table 146
New parameters introduced by LTE2417 Full name
IP traffic capacity limit enabled
Table 147
Abbreviated name
Managed object
ipTrafficCapacity CAPLIML LimitEnabled
Parent structure -
Existing parameters related to LTE2417 Full name
User plane IP address
Abbreviated name uplaneIPaddress
Managed object IPNO
Parent structure -
Sales information
214
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 148
Descriptions of transport and transmission features
LTE2417 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
4.6 LTE2645: GNSS Manual Location Entry for Macro BTS The LTE2645: GNSS Manual Location Entry for Macro BTS feature introduces a Global Navigation Satellite System (GNSS) Manual Location Entry to macro BTS. This allows a GNSS phase and time synchronization with connectivity to at least two GNSS satellites. The feature is used for macro BTS site locations that are not optimal for satellite reception.
4.6.1 LTE2645 benefits The LTE2645: GNSS Manual Location Entry for macro BTS feature provides the following benefits: • •
GNSS phase and time synchronization with connectivity to at least two GNSS satellites (versus four that are typically required). Indoor deployments or BTSs in urban canyons that tend to deal with poor GNSS reception.
4.6.2 LTE2645 functional description A global positioning system (GPS) is a space-based radio-navigation system that provides precise three-dimensional (3D) positioning (latitude, longitude, altitude) by using time signals transmitted from satellites. The signals also allow the receivers to calculate the current local time with great precision, which is used by the BTS for frequency, phase and time synchronization. This satellite navigation system with global coverage is called a Global Navigation Satellite System (GNSS). GNSS receivers used for synchronization purposes operate in two phases. First phase During start-up the receiver automatically determines the geographical position of the GNSS receiver antenna. In the context of this document this mode is called an automatic mode. Typically, a minimum GPS constellation is arranged so that a minimum of four satellites are in an unobstructed view to determine latitude, longitude, altitude, and the time for a BTS as demonstrated in the Figure 29: Typical environment with a minimum of four satellites:
Issue: 01 Draft
DN09237915
215
Descriptions of transport and transmission features
Figure 29
FDD-LTE16A, Feature Descriptions and Instructions
Typical environment with a minimum of four satellites
GNSS satellite 2
rier
Car
GNSS satellite 3
ncy
que Fre 542
.57
=1 23M
1,0
GNSS satellite 1
z _+
GH
GNSS satellite N
Hz
Second phase In a second phase, when the GNSS receiver has determined the antenna position, the receiver uses the signals from all visible satellites for calculating exact time information. In this phase, it is possible to recover time information from fewer than four satellites; as a minimum, two satellites must be visible all the time. In some cases, the physical obstructions may prevent the required four-or-more-satellite 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.
216
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Figure 30
Descriptions of transport and transmission features
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 manually pre-configure the position coordinates for the GNSS-receiver antenna in a BTS. In addition, the GNSS is configured to operate in a mode where it does not attempt to determine the position itself, and in which it uses the pre-configured antenna coordinates, instead. In the context of this feature, this mode of operation is called a manual mode. In this mode, when the GNNS receiver is constantly receiving signal from at least two satellites, it is able to calculate the exact time, based on the pre-configured position coordinates. The operators have various methods available to collect the coordinate information of the GNSS antenna. Below, there are a few examples: • •
•
Issue: 01 Draft
using a surveyor company using a hand-held GNSS receiver to measure the position of 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 Google Maps
DN09237915
217
Descriptions of transport and transmission features
•
FDD-LTE16A, Feature Descriptions and Instructions
using maps from mapping companies such as HERE
This improves the system's availability in locations with an obstructed GNSS antenna visibility and allows the macro 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 manual method. Four user-configurable GPS location parameters are introduced: • • • •
g
GNSS receiver GNSS receiver GNSS receiver Location mode mode)
altitude (gnssAntennaAltitudeConf) latitude (gnssAntennaLatitudeConf) longitude (gnssAntennaLongitudeConf) (locationMode; automatic mode (default) or manual
Note: The parameters can be configured independently for the external GNSS receiver (MOC SMOD-GNSSE). The parameters can be configured within a configuration file or also be modified on-line. In the manual mode the: •
•
•
GNSS receiver latitude (latitudeConf) data should be accurate to within +/-1 arcsecond, corresponding to about +/-30 meters, using the World Geodetic System 1984 (WGS-84) coordinate system. GNSS receiver longtitude (longitudeConf) data should be accurate to within +/-1 arcsecond, corresponding to about +/-30 meters, using the World Geodetic System 1984 (WGS-84) coordinate system. GNSS receiver altitude (altitudeConf) data should be accurate to within +/-30 m relative to a GPS ellipsoid, sometimes also called Height Above Ellipsoid (HAE).
The manual 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. This mode does not reduce the satellite acquisition time and should not be used for this purpose. It 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.
g
Note: When using GNSS receivers with a separated antenna, the coordinate information must be given for the antenna, not for the GNSS receiver. Generic user scenarios show how the GNSS antenna location can manually be entered, modified or deactivated: • • •
GNSS Manual Location Entry for macro BTS, on-line entry via Site Manager GNSS Manual Location Entry for macro BTS, modification of location data GNSS Manual Location Entry for macro BTS, feature deactivation
4.6.3 LTE2645 system impact LTE2645: GNSS Manual Location Entry for macro BTS impact on features Interdependencies between features One of the following features is required as a pre-requisite for the LTE2645: GNSS Manual Location Entry for Macro BTS feature:
218
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• •
Descriptions of transport and transmission features
LTE80: GPS Synchronisation LTE1125: GNSS Receiver FYGB
• • •
LTE2028: Outdoor External GNSS Module with Enhanced Holdover – FYGG LTE2335: Outdoor GNSS Receiver FYGM
The LTE2645: GNSS Manual Location Entry for Macro BTS feature is impacted by the following features: •
LTE2645 is inherited from LTE2063: GNSS Manual Location Entry (implemented in the FZM in FL/TL15A). LTE2645 is functionally compatible with LTE2063. The same parameters are used for controlling the feature in the FZM and in the macro eNB.
Impact on interfaces The LTE2645: GNSS Manual Location Entry for Macro BTS feature has no impact on interfaces. Impact on network management tools The LTE2645: GNSS Manual Location Entry for Macro BTS feature has no impact on network management tools. Impact on system performance and capacity The LTE2645: GNSS Manual Location Entry for Macro BTS feature has no impact on system performance or capacity.
4.6.4 LTE2645 reference data LTE2645: GNSS Manual Location Entry for macro BTS requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements Table 149
LTE2645 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE16A
not applicable
Flexi Zone Controller
OMS
not supported
LTE OMS16A
Flexi Multiradio 10 BTS
Nokia AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
not supported
not supported
not supported
NetAct
MME
SAE GW
UE Support not required
NetAct 16.8
Support not required
Support not required
Additional hardware requirements This feature is supported with the following GNSS receiver types: • • •
FYGB (external GNSS antenna/receiver from Trimble) FYGG (external receiver supporting holdover) FYGM (external receiver for outdoor use)
BTS faults and reported alarms
Issue: 01 Draft
DN09237915
219
Descriptions of transport and transmission features
Table 150
FDD-LTE16A, Feature Descriptions and Instructions
New BTS faults introduced by LTE2645
Fault ID
Fault name
Reported alarms Alarm ID
4328
Manual location entry not 7652 supported (4328: EFaultId_ManualLocationEnt ryNotSupportedAl )
Table 151
Alarm name
BASE STATION NOTIFICATION
Existing BTS faults related to LTE2645
Fault ID
Fault name
Reported alarms Alarm ID
Alarm name
4123
GPS receiver alarm: survey 7652 in progress (4123: EFaultId_GpsReceiverSurvey InProgressAl)
BASE STATION NOTIFICATION
4124
GPS receiver alarm: no 7652 stored position (4124: EFaultId_GpsReceiverNoStor edPositionAl )
BASE STATION NOTIFICATION
4153
Reference clock missing in 7651 startup (4153: EFaultId_PpsRefClcMissInSt rtAl )
BASE STATION OPERATION DEGRADED
For fault descriptions, see Radio Access Operating Documentation/Reference/Alarms. Commands There are no commands related to the LTE2645: GNSS Manual Location Entry for Macro BTS feature. Measurements and counters There are no measurements or counters related to the LTE2645: GNSS Manual Location Entry for Macro BTS feature. Key performance indicators There are no key performance indicators related to the LTE2645: GNSS Manual Location Entry for Macro BTS feature. Parameters Table 152
Parameters modified by LTE2645 Full name
220
Abbreviated name
Managed object
GNSS receiver altitude
gnssAntennaAltitudeConf
GNSSE
GNSS receiver latitude
gnssAntennaLatitudeConf
GNSSE
GNSS receiver longitude
gnssAntennaLongitudeConf
GNSSE
Location mode
locationMode
MRBTS
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of transport and transmission features
For parameter descriptions, see LTE Radio Access Operating Documentation/ Reference/Parameters. Sales information Table 153
LTE2645 sales information
Product structure class
License control
Application software (ASW)
Pool license
Activated by default No
4.6.5 Other instructions These generic user scenarios show how the operator can configure the system depending on the environmental conditions. Example: User scenario 1-GNSS Manual Location Entry for macro BTS, on-line entry via Site Manager This user scenario describes a BTS Site Manager user manually entering the GNSS antenna location while the BTS is in a challenging environment with fewer than four satellite transmissions available. Actors: Operator Preconditions: • • • •
The BTS is connected to an external GNSS receiver. The GNSS receiver has been configured as a sync reference source. The GNSS antenna has limited sky visibility (fewer than four satellites). The Site Configuration File contains no GNSS antenna coordinates, and the locationMode parameter is set to automatic.
Hardware requirements: •
The eNB based on FSMF/Nokia AirScale BTS is connected to an external GNSS receiver (FYGB, FYGG or FYGM).
Required features: • • • • •
LTE2645: GNSS Manual Location Entry for Macro BTS LTE80: GPS Synchronization LTE1125: GNSS Receiver FYGB LTE2028: Outdoor External GNSS Module with Enhanced Holdover – FYGG LTE2335: Outdoor GNSS Receiver FYGM
Description: • •
g
Issue: 01 Draft
The GNSS receiver starts up autonomously. The BTS indicates that the GNSS receiver is still searching for the position (for example by Fault 4123, 4124, 4153). Note: The operator should check the number of visible satellites at the BTS Site Manager (typically fewer than four).
DN09237915
221
Descriptions of transport and transmission features
g
FDD-LTE16A, Feature Descriptions and Instructions
Note: The operator should check whether the GNSS receiver has attempted to determine the position for at least 1 hr. • • • • • •
The operator sets the locationMode parameter to manual and configures antenna coordinates via BTS Site Manager. The operator submits the delta commissioning file. The BTS downloads antenna coordinates into GNSS receiver. The GNSS receiver uses the manually-configured position for generating the 1 pps/ToD sync signal. The BTS cancels the related faults. The BTS goes to an OnAir state.
Post-condition: The GNSS receiver is using the manually-configured position, and the eNB is operational. Exception: When the GNSS receiver in use does not support the manual location entry, the BTS issues fault Manual Location Entry Not Supported.
g
Note: If satellite visibility improves and the FYGB/FYGG receiver determines the provided manual position is inaccurate, it may stop using the manual position and start automatic position acquisition. The BTS indicates that the GNSS receiver has not yet found the position by issuing one or several of the following faults: • • •
g
Fault 4123: GPS receiver alarm: survey in progress Fault 4124: GPS receiver alarm: no stored position Fault 4153: Reference clock missing in startup Note: The Fault 4328: Manual Location Entry Not supported is issued when a GNSS receiver does not accept the requested manual location entry. This happens if the operator enters a manual location that may be determined by some receivers under certain conditions to be in error greater than allowed for the receiver. In this case the GNSS receiver itself supports a manual location entry but the actual values have been determined as erroneous.
Example: User scenario 2-GNSS Manual Location Entry for macro BTS, modification of location data This user scenario describes a BTS Site Manager user manually modifying the GNSS antenna location while the BTS is in a challenging environment with fewer than four satellite transmissions available. Actors: Operator Preconditions: • •
222
The BTS is in normal operation, synchronized by an external GNSS receiver. The GNSS antenna has limited sky visibility (fewer than four satellites).
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
Descriptions of transport and transmission features
The locationMode parameter is set to manual, and the GNSS receiver is using the configured antenna coordinates for generating the 1 pps/ToD signal.
Hardware requirements: •
The eNB based on FSMF/Nokia AirScale BTS is connected to an external GNSS receiver (FYGB, FYGG or FYGM).
Required features: • • • • •
LTE2645: GNSS Manual Location Entry for Macro BTS LTE80: GPS Synchronization LTE1125: GNSS Receiver FYGB LTE2028: Outdoor External GNSS Module with Enhanced Holdover – FYGG LTE2335: Outdoor GNSS Receiver FYGM
Description: • • • • • •
The operator configures new antenna coordinates via BTS Site Manager. The operator triggers a manual reset of the GNSS receiver via BTS Site Manager. The GNSS receiver restarts. The operator submits the delta commissioning file. The BTS downloads antenna coordinates into the GNSS receiver. The GNSS receiver uses the configured new position for generating the 1 pps/ToD sync signal.
Postcondition: The GNSS receiver is using the manually-configured position, and the eNB is operational.
g
Note: The delta commissioning file should be downloaded soon after resetting the GNSS receiver (no later than one minute after the reset) since some GNSS receivers do not accept changes of the location parameters after a certain time. Exception:
g
Note: The Fault 4328: Manual Location Entry Not supported is issued when a GNSS receiver does not accept the requested manual location entry. This happens if the operator enters a manual location that may be determined by some receivers under certain conditions to be in error greater than allowed for the receiver. In this case the GNSS receiver itself supports a manual location entry but the actual values have been determined as erroneous. Example: User scenario 3-GNSS Manual Location Entry for macro BTS, feature deactivation This user scenario describes a BTS Site Manager user manually changing back the location mode parameter to automatic when the sky visibility has improved, and a minimum of four satellites are available. Actors: Operator Preconditions:
Issue: 01 Draft
DN09237915
223
Descriptions of transport and transmission features
• • •
FDD-LTE16A, Feature Descriptions and Instructions
The BTS is in normal operation, synchronized by an external GNSS receiver. The GNSS antenna has limited sky visibility (fewer than four satellites). The locationMode parameter is set to manual, and the GNSS receiver is using the configured antenna coordinates for generating the 1 pps/ToD signal.
Hardware requirements: •
The eNB based on FSMF/Nokia AirScale BTS is connected to an external GNSS receiver (FYGB, FYGG or FYGM).
Required features: • • • • •
LTE2645: GNSS Manual Location Entry for Macro BTS LTE80: GPS Synchronization LTE1125: GNSS Receiver FYGB LTE2028: Outdoor External GNSS Module with Enhanced Holdover – FYGG LTE2335: Outdoor GNSS Receiver FYGM
Description: • • • • • • • • • •
The sky visibility has improved. The operator checks the number of visible satellites at BTS Site Manager; at least four satellites must be constantly visible. The operator sets the locationMode parameter to automatic at BTS Site Manager. The operator submits the delta commissioning file. The operator triggers a reset of the GNSS receiver. The GNSS receiver tries to determine the position. The BTS indicates that the GNSS receiver is still searching for the position (for example by Fault 4123, 4124, 4153) The GNSS receiver has determined the position. The GNSS receiver uses the detected position for generating the 1 pps/ToD sync signal. The BTS cancels the related faults.
Post-condition: The GNSS receiver is using the position determined from the satellites, and the eNB is operational. Exception: If the GNSS receiver does not provide a 1 pps/ToD signal while it is determining the position, the BTS may temporarily go into holdover, and additional faults may be raised.
4.7 LTE2763: Fronthaul Passive WDM There is a link between SM and RF modules: On this link, the antenna streams are running, using the OBSAI or CPRI protocol. In addition there is a control channel embedded into OBSAI and CPRI which allows to download software or to run other commands.
224
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of transport and transmission features
The LTE2763: Fronthaul Passive WDM feature introduces fronthaul passive wavelength division multiplexing (WDM) components (mux\demux\CWDM SFPs) to multiplex\demultiplex these CPRI\OBSAI links.
4.7.1 LTE2763 benefits The LTE2763: Fronthaul Passive WDM feature provides the following benefits: With the multiplexing/demultiplexing technics the optical fibers are used more efficiently and this leads to a reduction of costs for the operator.
4.7.2 LTE2763 functional description The LTE2763: Fronthaul Passive WDM feature offers the following characteristics: • • • • • •
The fronthaul passive wavelength division multiplexing (7705 SAR-O, 1830 VWM) is connected between the system module (SM) and the radio frequency (RF) modules. Up to 16 Coarse Wavelength Division Multiplexing (CWDM) channels can be optically multiplexed over a single fiber using SAR-O/VWM. The SAR-O/VWM support a maximum distance of up to 20 km. The SAR-O permits outdoor installation, the VWM is the indoor mux unit . The SAR-O/VWM support point-to-point and linear topology. The SAR-O/VWM have proven interoperabilty with base band system modules and RFMs/RRHs.
An overview is given in the Figure 31: Possible Deployment of SAR-O/VWM. Figure 31
Possible Deployment of SAR-O/VWM RRHwith coloredSFP
SFP
Outdoorhardened PassiveWDMMux: 7705SAR-O
SFP SPF
SFP
Fronthaul fiber
SFP SFP SFP IndoorMux unit:1830VWM
Colorized SFPs
4.7.3 LTE2763 system impact Interdependencies between features There are no interdependencies between the LTE2763: Fronthaul Passive WDM feature and any other feature. Impact on interfaces The LTE2763: Fronthaul Passive WDM feature has no impact on interfaces.
Issue: 01 Draft
DN09237915
225
Descriptions of transport and transmission features
FDD-LTE16A, Feature Descriptions and Instructions
Impact on network management tools The LTE2763: Fronthaul Passive WDM feature has no impact on network management tools. Impact on system performance and capacity The LTE2763: Fronthaul Passive WDM feature has no impact on system performance or capacity.
4.7.4 LTE2763 reference data Requirements Table 154
LTE2763 Fronthaul Passive WDM
System release
Flexi Multiradio BTS
FDD-LTE16A
not supported
Flexi Zone Controller
OMS
not applicable
support not required
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL16A
UE support not required
Flexi Zone Micro BTS
Flexi Zone Access Point
not applicable
not applicable
MME
SAE GW
NetAct support not required
support not required
support not required
Alarms There are no alarms related to the LTE2763: Fronthaul Passive WDM feature. BTS faults and reported alarms There are no faults related to the LTE2763: Fronthaul Passive WDM feature. Measurements and counters There are no measurements or counters related to the LTE2763: Fronthaul Passive WDM feature. Key performance indicators There are no key performance indicators related to the LTE2763: Fronthaul Passive WDM feature. Parameters There are no parameters related to the LTE2763: Fronthaul Passive WDM feature. Sales information Table 155
LTE2763 sales information
Product structure class Basic Software (BSW)
226
License control -
DN09237915
Activated by default Yes
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
5 Descriptions of operability features 5.1 LTE678: MDT – UE Radio Link Failure Report Evaluation Benefits, functionality, system impact, reference data, instructions of the feature The LTE678: MDT – UE Radio Link Failure Report Evaluation feature introduces a new value of the Job type (jobType) parameter by adding the RLFReportsOnly option. It ensures that the corresponding RLF cell trace session traces only the RRC:UEInformationResponse messages which contain a radio link failure (RLF) report.
5.1.1 LTE678 benefits The LTE678: MDT – UE Radio Link Failure Report feature provides the following benefits: • •
More efficient detection and recovery of the physical layer problems (while neither T300, T301, T304 nor T311 is running) by using the newly-added trace session Reduced OPEX by avoiding usage of the minimization of drive test (MDT) method
5.1.2 LTE678 functional description Functional description A radio link failure (RLF) is a common occurrence in all radio access technologies. It occurs when a UE experiences an interference issue and/or poor signal strength with the eNB. After that, when an RLF report is forwarded, it contains measurement information about the last serving and neighbor cells before the RLF took place. The RRC:ConnectionReestablishmentComplete, RRC:ConnectionSetupComplete and RRC:ConnectionReconfigurationComplete message trigger the RLF report to be forwarded via the X2 interface with the X2AP:RLFIndication message, provided the last serving cell is located in a neighbor eNB. The RLF reports are used to enhance the trace information in combination with: • •
Subscriber and equipment trace Cell trace
With the current trace functionality, it is possible to include RLF reports into a cell trace, interface trace, subscriber, and equipment trace when the corresponding messages (for example, RRC:UEInformationResponse and/or X2AP:RLFIndication) are included in the set of messages/protocols to be traced. The LTE678: MDT – UE Radio Link Failure Report Evaluation feature introduces a new value RLFReportsOnly for the Job type (jobType) parameter under the MTRACE instance. When this option is selected, the corresponding RLF cell trace session traces only RRC:UEInformationResponse messages which contain an RLF report. In addition, the LTE678: MDT – UE Radio Link Failure Report Evaluation feature triggers the retrieval of RLF reports from UEs, separately from the LTE1749: Mobility Robustness
Issue: 01 Draft
DN09237915
227
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
Monitoring Inter-RAT feature. The RLF indication is sent on the X2AP protocol only if there are differences between the cell which is causing the failure and the current primary cell (PCell.) The LTE678: MDT – UE Radio Link Failure Report Evaluation feature allows to configure other, parallel trace sessions, such as Trace Only or Immediate MDT and Trace. It can also be enabled or disabled on BTS level.
g
Note: If possible, the following features should use just one UE information procedure: LTE678: MDT – UE Radio Link Failure Report Evaluation LTE1049: MDT – UE Measurement Logs LTE1235: Optimization of PRACH/RACH Power LTE1749: Mobility Robustness Monitoring Inter RAT
• • • •
5.1.3 LTE678 system impact LTE678: MDT – UE Radio Link Failure Report Evaluation impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features There are no interdependencies between the LTE678: MDT – UE Radio Link Failure Report Evaluation feature and any other feature. Impact on interfaces The LTE678: MDT – UE Radio Link Failure Report feature has no impact on interfaces. Impact on network management tools The LTE678: MDT – UE Radio Link Failure Report feature impacts network management tools as follows: •
BTS SM –
•
A new value RLFReportsOnly has been added to the Job type (jobType) parameter.
NetAct –
A new value RLFReportsOnly has been added to the Job type (jobType) parameter.
Impact on system performance and capacity The LTE678: MDT – UE Radio Link Failure Report feature has no impact on system performance or capacity.
5.1.4 LTE678 reference data LTE678: MDT – UE Radio Link Failure Report Evaluation requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements
228
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 156
Descriptions of operability features
LTE678 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
not applicable
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
not supported
UE
LTE OMS 16A not applicable
Flexi Zone Micro BTS FL16A
NetAct NetAct 16.8
Flexi Zone Access Point FL16A
MME
SAE GW
not applicable
not applicable
Alarms There are no alarms related to the LTE678: MDT – UE Radio Link Failure Report Evaluation feature. BTS faults and reported alarms There are no faults related to the LTE678: MDT – UE Radio Link Failure Report Evaluation feature. Commands There are no commands related to the LTE678: MDT – UE Radio Link Failure Report Evaluation feature. Measurements and counters There are no measurements or counters related to the LTE678: MDT – UE Radio Link Failure Report Evaluation feature. Key performance indicators There are no key performance indicators related to the LTE678: MDT – UE Radio Link Failure Report Evaluation feature. Parameters Table 157
New parameters introduced by LTE678 Full name
Activate RLF report evaluation
Table 158
Abbreviated name
actRLFReportEval
Managed object LNBTS
Parent structure
-
Existing parameters related to LTE678 Full name
Activate cell trace
Abbreviated name
actCellTrace
Managed object LNBTS
Parent structure
-
Cell maximum active UEs cellMaxActiveUEsT MTRACE traced raced
-
MTRACE
-
Job type
jobType
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information
Issue: 01 Draft
DN09237915
229
Descriptions of operability features
Table 159
FDD-LTE16A, Feature Descriptions and Instructions
LTE678 sales information
Product structure class
License control
Activated by default
Application software (ASW)
Pool license
No
5.2 LTE2121: Radio Unit Reset The LTE2121: Radio Unit Reset feature provides two improvements to the radio reset procedure: • •
separation of reset and unblocking of a radio module possibility to reset radio module via commissioning or configuration plan
Before this feature, the radio reset was possible only by blocking and unblocking the unit.
5.2.1 LTE2121 benefits The LTE2121: Radio Unit Reset feature provides the following benefits: • • • •
creating a configuration plan in NetAct, which, when activated, will trigger a radio reset (it is possible to perform a reset of multiple radio modules in one plan) resetting radio module using BTS Site Manager (using commissioning procedure or button in user interface) the unblocking function restores services to the radio unit without a reset (service is restored more quickly) the blocking state of a radio module remains the same before and after the module reset
5.2.2 LTE2121 functional description The LTE2121: Radio Unit Reset feature introduces the possibility to reset one or more radio units within BTSs via NetAct or BTS Site Manager. In NetAct, user has ability to reset radios by configuration plan. In BTS, Site Manager user can reset radio in the user interface (with reset button) or by BTS commissioning.
5.2.2.1
Reset of radio unit via NetAct configuration plan To initiate a reset, the RMOD Request radio module reset (resetRequest) parameter should be set by the operator to true. After the configuration plan is downloaded and activated on the BTS, the following scenario happens: 1. BTS calculates the service impact, which depends on the number of disabled cells (no service impact, partial, or total service loss). 2. BTS determines if plan activation is allowed based on the service impact and settings of LNBTS planFileActivationMode and forcedPlanFileActivation parameters. If as a result of plan activation service loss will occur, and those parameters do not allow it, the plan validation will fail (scenario ends).
230
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
g
Descriptions of operability features
Note: The LNBTS planFileActivationMode parameter can have one of the following values: • • •
totalServiceLossAllowed: Plan file activation is allowed to trigger an eNB restart or to drop all cells, if needed. partialServicLossAllowed: Plan file activation is not allowed to trigger an eNB restart or to drop all cells but is allowed to temporarily drop some cells. noServiceLossAllowed: Plan file activation is neither allowed to trigger an eNB restart nor to temporarily drop cells.
If forcedPlanFileActivation parameter is set to true, it enforces the activation of a plan file independent of the configured value of theplanFileActivationMode parameter. 3. BTS initiates reset of radio modules that can be reset, that is, radio modules which are not off-line, not currently resetting or with software update in progress 4. BTS set the resetRequest parameter to false After the reset, blocking state of each radio module ("blocked" or "unblocked") remains the same as before. There are the following exceptions for the radio module reset scenario: •
• • •
•
5.2.2.2
In case of radio modules arranged in a chained configuration, the BTS performs a reset of multiple radios concurrently, starting with the radio furthest from the head of the chain. If a radio module is shared (for example, RF sharing has been enabled), a reset may be initiated only from the BTS that is the radio master. If the configuration plan contains radio parameter updates in addition to radio reset requests, the BTS performs the radio resets first. If an entire BTS is reset (as a result of activating configuration plan), radio unit reset requests do not initiate additional radio resets (the resetRequest parameter is set to false). If a radio module is off-line, is already being reset or the software update is in progress, then the resetRequest parameter is automatically set to false.
Reset of radio unit via BTS Site Manager interface In BTS Site Manager (SM), the user has two options to reset a radio module: • •
using reset button in the equipment view in BTS Hardware menu by performing commissioning and setting the RMOD: resetRequest parameter to true
After the operator clicks reset button, BTS SM sends a request to the reset radio module to the BTS (ResetModuleRequest), and then BTS triggers the reset. After the reset, blocking state of each radio module ("blocked" or "unblocked") remains the same as before. Exceptions for this scenario: • •
Issue: 01 Draft
If the radio module is being reset or has not been detected, the reset button is disabled. If the radio module is shared and the BTS is not a radio master, BTS SM informs the user that a radio reset is not allowed.
DN09237915
231
Descriptions of operability features
•
•
FDD-LTE16A, Feature Descriptions and Instructions
If a radio module is chained, BTS SM informs the user that the radio module is chained and that radio modules further down the chain will also be reset (the operator can cancel or proceed with the reset). If a BTS site reset is initiated or a software download is in progress, BTS SM informs the user that a reset operation has failed.
5.2.3 LTE2121 system impact LTE2121: Radio Unit Reset has no impact on features, interfaces, network management tools, and system performance and capacity.
5.2.4 LTE2121 reference data Requirements Table 160
LTE2121 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE16A
not supported
Flexi Zone Controller
OMS
not supported
support not required
Flexi Multiradio 10 BTS FL16A
AirScale BTS not supported
UE support not required
Flexi Zone Micro BTS not supported
NetAct 16.8
MME
Flexi Zone Access Point not supported
SAE GW
support not required
support not required
Alarms There are no alarms related to the LTE2121: Radio Unit Reset feature. Measurements and counters There are no measurements or counters related to the LTE2121: Radio Unit Reset feature. Key performance indicators There are no key performance indicators related to the LTE2121: Radio Unit Reset feature. Parameters Table 161
New parameters introduced by LTE2121 Full name
Request radio module reset
Abbreviated name
resetRequest
Managed object RMOD
Parent structure -
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameteres. Sales information
232
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 162
Descriptions of operability features
LTE2121 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
5.3 LTE2202: Addition of MAC Measurements to Cell Trace Benefits, functionality, system impact, reference data, instructions of the feature The LTE2202: Addition of MAC Measurements to Cell Trace feature introduces new measurements to the cell trace content. They are related to the MAC layer, collected periodically, and reported per UE basis.
5.3.1 LTE2202 benefits The LTE2202: Addition of MAC Measurements to Cell Trace feature provides the following benefits: •
Better monitoring, diagnosis, and optimization of the UE throughput or transmission due to broader possibilities of data collection
5.3.2 LTE2202 functional description Functional description The cell trace functionality allows to follow the connections ongoing in a cell and verify the intended functionalities within a cell. It can be used for a deeper analysis if problems occur and when various performance measurements do not give a clear indication of the problem. It is the most common form of general troubleshooting within the network. With the cell trace, all the UEs in a target cell that are in the connected state are traced simultaneously. The medium access control (MAC) layer is a part of the LTE air interface user plane (Uplane). MAC covers circuit-switched, packet-switched, as well as signaling traffic. The LTE2202: Addition of MAC Measurements to Cell Trace feature introduces new measurements to the cell trace content, which are related to the MAC layer, collected periodically, and reported per UE basis. The following newly-added measurements, listed in Table 163: Measurements newly added to the cell trace content, can be enabled or disabled per cell trace session with a common switch: Table 163
Issue: 01 Draft
Measurements newly added to the cell trace content Uplink
Downlink
Cumulative number of bytes received on GBR bearers
Cumulative number of bytes sent on GBR bearers
Cumulative number of bytes received on nonGBR bearers
Cumulative number of bytes sent on non-GBR bearers
Maximum delay of GBR in ms
Max delay of GBR in ms; delay inside eNB between PDCP and MAC layers
DN09237915
233
Descriptions of operability features
Table 163
FDD-LTE16A, Feature Descriptions and Instructions
Measurements newly added to the cell trace content (Cont.) Uplink
Downlink
Number of first received transmissions
Single CW Transmission: number of first transmissions
Number of overall received transmissions
Single CW Transmission: number of overall transmissions
Number of first receptions with NACK or DTX
Single CW Transmission: number of first transmissions with NACK or DTX
Number of last retransmissions failed
Single CW Transmission number of failed last retransmissions
Number of TTIs UL buffer status greater than 0
Dual CW Transmission: number of transmissions, first or overall
Mean MCS at first transmission
Dual CW Transmission: number of first transmissions with NACK or DTX
Mean PUSCH RSSI for all transmissions
Dual CW Transmission: number of failed last retransmissions
Mean PUSCH SINR for all transmissions
Number of transmissions leading to no reliable ACK or NACK on PDSCH; DTX received
Mean power headroom at first transmission
Number of TTIs with DL buffer status greater than 0
Mean PUCCH RSSI
Mean delta CQI at first transmission
Mean AGG (1–16) for UL grant; required aggregation for UL grant
Mean WB CQI at first transmissions
Mean AGG (1–16) for DL grant; required aggregation for DL grant
g
Note: For UEs that are configured for carrier aggregation (CA), it is not possible to provide MAC layer measurements for secondary cells (SCells).
5.3.3 LTE2202 system impact LTE2202: Addition of MAC Measurements to Cell Trace impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be activated before activating the LTE2202: Addition of MAC Measurements to Cell Trace feature: •
LTE433: Cell Trace
The LTE2202: Addition of MAC Measurements to Cell Trace feature impacts the following features: •
234
LTE2535: UE Throughput Measurements with BTS Log The LTE2202: Addition of MAC Measurements to Cell Trace feature can be active at the same time as the LTE2535: UE Throughput Measurements with BTS Log feature.
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
Descriptions of operability features
LTE1803: Downlink Carrier Aggregation 3CC – 40 MHz The activated LTE1803: Downlink Carrier Aggregation 3CC – 40 MHz feature allows to provide more than one UE UL/DL measurement report with full trace content, for one PCell and each SCell, available inside an eNB.
Impact on interfaces The LTE2202: Addition of MAC Measurements to Cell Trace feature impacts interfaces as follows: •
U-plane –
It updates the LTE protocol interface specification to include descriptions of new UE measurement reports for the uplink (UL) and downlink (DL).
Impact on network management tools The LTE2202: Addition of MAC Measurements to Cell Trace feature has no impact on network management tools. Impact on system performance and capacity The LTE2202: Addition of MAC Measurements to Cell Trace feature impacts system performance and capacity as follows: •
The additional provisioning of MAC layer measurements has an impact on the performance at a system level in that processing capacity as well as additional bandwidth on the cell trace interface are required. The reduce overload is caused by: – –
Limitations to upload UE trace comes from additional CPU load Backhaul traffic will be increased by more than 0.3 Mbps per BTS with 900 RRC connected users
By limitation of more than 300 RRC connected users per cell or nore than 900 RRC connected users per BTS can increase bandwidth around 8.5%. Also the load effect will be highest for the system module MCU CPU, which will increase to more than 10% units.
5.3.4 LTE2202 reference data LTE2202: Addition of MAC Measurements to Cell Trace requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements Table 164
LTE2202 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
not supported
UE
LTE OMS 16A not applicable
NetAct NetAct 16.8
Flexi Zone Micro BTS FL16A
Flexi Zone Access Point FL16A
MME
SAE GW
not applicable
not applicable
Alarms
Issue: 01 Draft
DN09237915
235
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
There are no alarms related to the LTE2202: Addition of MAC Measurements to Cell Trace feature. BTS faults and reported alarms There are no faults related to the LTE2202: Addition of MAC Measurements to Cell Trace feature. Commands There are no commands related to the LTE2202: Addition of MAC Measurements to Cell Trace feature. Measurements and counters There are no measurements or counters related to the LTE2202: Addition of MAC Measurements to Cell Trace feature. Key performance indicators Parameters Table 165
New parameters introduced by LTE2202 Full name
Abbreviated name
Managed object
Parent structure
Activate UE throughput measurements
actUeThroughputMe LNBTS as
-
Activate UE throughput measurement reports
actUeThroughputMR MTRACE
-
Table 166
Existing parameters related to LTE2202 Full name
Abbreviated name
Managed object
Parent structure
Cell maximum active UEs cellMaxActiveUEsT MTRACE traced raced
-
MTRACE
-
Immediate MDT control
immedMDTControl
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 167
LTE2202 sales information
Product structure class
License control
Activated by default
Application software (ASW)
SW Asset Monitoring
No
5.4 LTE2237: Log Collection Triggered by BTS Fault Cancellation Benefits, functionality, system impact, reference data of the feature
236
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
The LTE2237: Log Collection Triggered by BTS Fault Cancellation feature extends the functionality of the LTE1099: Event Triggered Symptom Data Collection and Provisioning feature’s concept of an automatic event-triggered BTS symptom data (troubleshooting logs) collection. This model allows commissioning a BTS with a new category of automated snapshots collection trigger based on a fault cancellation.
5.4.1 LTE2237 benefits The LTE2237: Log Collection Triggered by BTS Fault Cancellation feature provides the following benefits: • •
Symptom data for trouble analysis collection time is reduced - automated collection process selects only relevant information Troubleshooting data collection of fault cancellation is guaranteed for further error analysis
5.4.2 LTE2237 functional description Feature description The automated log collection helps to find and solve troubles caused by environment equipment (e.g. cables, antennas, wrong parameter's configuration.) Figure 32: Features related to the log collection functionality presents the family of log collection functionality features. Figure 32
Features related to the log collection functionality
LTE1099 Introducesautomaticfault-triggeredBTSsymptomdata(troubleshootinglogs)collection
LTE2250
LTE2237
CommissioningaBTSwiththenewcategory ofautomatedsnapshotcollectiontrigger, basedonasinglesubstringoccurrencefound inthesyslogstream
Commissioning aBTS with the newcategoryof automatedsnapshotscollectiontriggerwhen a fault hasbeen canceled
The LTE2237: Log Collection Triggered by BTS Fault Cancellation feature is designed for collecting and sending fault cancellation data as a snapshot for further analysis. Troubleshooting data is compressed and named in a common way upon data collection. The symptom data file has a catalog which describes the reason for the symptom's creation. The name of troubleshooting data contains information if data was collected at the start or at the end of the fault cancellation. If a snapshot is triggered, and data collection has been started, any further triggers are ignored untill it has finished. A daily limit for collecting snapshots is a maximum of five per 24h per BTS and trigger. When this limit has been exceeded, automated snapshots are blocked for a given trigger. Troubleshooting data transfer takes place automatically in OMS, immediately when the file is ready.
Issue: 01 Draft
DN09237915
237
Descriptions of operability features
g
FDD-LTE16A, Feature Descriptions and Instructions
Note: Triggered snapshot collection of fault cancellations is configurable by the operator.
g
Note: The LTE2237: Log Collection Triggered by BTS Fault Cancellation feature can be activated together with the LTE1099: Event Triggered Symptom Data Collection and Provisioning feature.
5.4.3 LTE2237 system impact LTE2237: Log Collection Triggered by BTS Fault Cancellation impact on features and system performance and capacity Interdependencies between features The LTE2237: Log Collection Triggered by BTS Fault Cancellation feature is impacted by the following features: •
•
LTE1099: Event-triggered Symptom Data Collection The LTE2237: Log Collection Triggered by BTS Fault Cancellation feature depends on the LTE1099: Event-triggered Symptom Data Collection feature; it reuses the existing implementation of the LTE1099: Event-triggered Symptom Data Collection feature. LTE2250: Syslog-triggered Symptom Data Collection The LTE2237: Log Collection Triggered by BTS Fault Cancellation feature reuses the existing implementation of the LTE2250: Syslog-triggered Symptom Data Collection feature.
Impact on interfaces The LTE2237: Log Collection Triggered by BTS Fault Cancellation feature has no impact on interfaces. Impact on network management tools The LTE2237: Log Collection Triggered by BTS Fault Cancellation feature has no impact on network management tools. Impact on system performance and capacity The LTE2237: Log Collection Triggered by BTS Fault Cancellation feature impacts system performance and capacity as follows: •
System capacity may be impacted in relation to reduced system performance by 10% as long as data collection is ongoing.
5.4.4 LTE2237 reference data LTE2237: Log Collection Triggered by BTS Fault Cancellation requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements
238
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 168
LTE2237 hardware and software requirements
System release FDD LTE16A
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
not supported
Flexi Zone Controller FL16A
Descriptions of operability features
FL16A
OMS OMS 16A
Nokia AirScale BTS not supported
UE support not required
Flexi Zone Micro BTS FL16A
NetAct
FL16A
MME
NetAct 16.8
Flexi Zone Access Point
SAE GW
support not required
support not required
Alarms There are no alarms related to the LTE2237: Log Collection Triggered by BTS Fault Cancellation feature. BTS faults and reported alarms There are no faults related to the LTE2237: Log Collection Triggered by BTS Fault Cancellation feature. Commands There are no commands related to the LTE2237: Log Collection Triggered by BTS Fault Cancellation feature. Measurements and counters There are no measurements or counters related to the LTE2237: Log Collection Triggered by BTS Fault Cancellation feature. Key performance indicators There are no key performance indicators related to the LTE2237: Log Collection Triggered by BTS Fault Cancellation feature. Parameters Table 169
New parameters introduced by LTE2237 Full name
Abbreviated name
Trigger Type
triggerType
Managed object TRBLCA DM
Parent structure
MRBTS
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 170
LTE2237 sales information
Product structure class Basic Software (BSW)
Issue: 01 Draft
License control -
DN09237915
Activated by default Yes
239
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
5.5 LTE2331: Multi-language Support for Selected Parameters Benefits, functionality, system impact, reference data of the feature The LTE2331: Multi-language Support for Selected Parameters feature introduces: • •
possibility of using Chinese and Japanese in BTS Site Manager (BTS SM) for selected parameters related to network elements a search mechanism which supports local language characters
5.5.1 LTE2331 benefits The LTE2331: Multi-language Support for Selected Parameters feature provides the following benefits: • •
Improving the management of a fast growing network by employing local language characters to name network elements Support Chinese and Japanese language on BTSSM for some specific BTS parameters (fulfilling the Chinese regulations)
5.5.2 LTE2331 functional description Functional description So far the eNB and the site configuration file have provided support for non-ASCII (American Standard Code for Information Interchange) or non-UTF-8 (Universal Coded Character Set + Transformation Format-8-bit) characters for text parameters. The LTE2331: Multi-language Support for Selected Parameters feature makes possible to input network element's name by a selected parameter in Chinese or Japanese into BTS Site Manager (BTS SM) and NetAct by using local language characters in the UTF8 system. In addition, this feature introduces a search mechanism for BTS SM to support local language characters. The supported languages are listed in Table 171: Supported local language characters. This change does not have an impact on eNB operations (for example, site name, location, description, etc.).
g
Note: The LTE2331: Multi-language Support for Selected Parameters feature fulfills Chinese regulations for BTS SM and NetAct functionalities. Table 171
Supported local language characters Language
Chinese
Local language Chinese (Simplified) Chinese (Traditional)
Japanese
Kanji Hiragana Katakana
240
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
g
Descriptions of operability features
Note: The LTE2331: Multi-language Support for Selected Parameters feature does not enable changing the language used in BTS SM or eNB. The parameters with the formatted UTF-8 character set are listed in Table 173: Parameters modified by LTE2331.
5.5.3 LTE2331 system impact LTE2331: Multi-language Support for Selected Parameters impact on interfaces and network management tools. Interdependencies between features There are no interdependencies between the LTE2331: Multi-language Support for Selected Parameters feature and any other feature. Impact on interfaces The LTE2331: Multi-language Support for Selected Parameters feature impacts interfaces as follows: •
BTS SM –
UTF-8 system character set will be supported in the site commissioning file (SCF) and in BTS SM – BTS OM interface (dataChangeNotif)
Impact on network management tools The LTE2331: Multi-language Support for Selected Parameters feature impacts network management tools as follows: •
BTS SM –
UTF-8 system character set will be supported in the site commissioning file (SCF) and in BTS SM – BTS OM interface (dataChangeNotif)
Impact on system performance and capacity The LTE2331: Multi-language Support for Selected Parameters feature has no impact on system performance or capacity.
5.5.4 LTE2331 reference data LTE2331: Multi-language Support for Selected Parameters requirements, parameters, and sales information Requirements Table 172
Issue: 01 Draft
LTE2331 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FDD-LTE 16A
not applicable
FDD-LTE 16A
FDD-LTE 16A
FDD-LTE 16A
FDD-LTE 16A
DN09237915
241
Descriptions of operability features
Table 172
FDD-LTE16A, Feature Descriptions and Instructions
LTE2331 hardware and software requirements (Cont.)
Flexi Zone Controller FDD-LTE 16A
OMS
UE
OMS 16A
NetAct
not applicable
NetAct 16.8
MME
SAE GW
not applicable
not applicable
Alarms There are no alarms related to the LTE2331: Multi-language Support for Selected Parameters feature. BTS faults and reported alarms There are no faults related to the LTE2331: Multi-language Support for Selected Parameters feature. Measurements and counters There are no measurements or counters related to the LTE2331: Multi-language Support for Selected Parameters feature. Key performance indicators There are no key performance indicators related to the LTE2331: Multi-language Support for Selected Parameters feature. Parameters Table 173
Parameters modified by LTE2331 Full name
Abbreviated name
Managed object
Parent structure
Site Name
btsName
BTSSCL
LNBTS
Cell Name
cellName
LNCEL
LNBTS
BTS System Title
systemTitle
FTM
LNBTS
BTS User Label
userLabel
FTM
LNBTS
BTS Location Name
locationName
FTM
LNBTS
AP System Title
systemTitle
APFTM
APMOD
AP User Label
userLabel
APFTM
APMOD
BTS System Module Location
moduleLocation
SMOD
MRBTS
BTS Radio Module Location
moduleLocation
RMOD
MRBTS
AP Module Location
moduleLocation
APMOD
SMOD
For parameter descriptions, see Operating Documentation > Reference > Parameters. Sales information Table 174
242
LTE2331 sales information
Product structure class
License control
Activated by default
Basic Software (BSW)
-
Yes
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
5.6 LTE2360: Login Restriction with CNUM The LTE2360: Login Restriction with CNUM feature enhances the security of user accounts by preventing a local user account from accessing an eNB when Centralized NE User Management (CNUM) is in use.
5.6.1 LTE2360 benefits The LTE2360: Login Restriction with CNUM feature enforces the use of a centralized user account (that is, CNUM) rather than allowing a local user account to be used to log in (since the local user account credentials are shared by more than one individual). The CNUM account has the following benefits: • •
every user is uniquely identified changes made by each user can be tracked
As a result, the operator will be able to associate all changes made to the system to a specific individual.
5.6.2 LTE2360 functional description Local account (i.e. Nemuadmin) can be used during log-in with BTS Site Manager (BTS SM) or Transport Web Page (TWP), launched from user's PC or NetAct framework. When the user attempts to authenticate with local user account credentials, the eNB determines whether the access should be allowed or blocked. If two conditions are met: • •
login restriction is enabled (the actRestrictLoginToCnum parameter is set to true) the centralized authentication server (LDAP server) is available for CNUM user login.
then the log-in attempt is blocked (BTS SM or TWP displays an error message). Additionally, the blocking of this log-in attempt is logged.
g
Note: If the LDAP server is down or inaccessible, the eNB will allow the local user account credentials to be used. Possible log-in scenarios are shown in the figure below.
Issue: 01 Draft
DN09237915
243
Descriptions of operability features
Figure 33
FDD-LTE16A, Feature Descriptions and Instructions
Local account log-in scenarios
LOGINRESTRICTION DISABLED NetAct
LOGINRESTRICTION DISABLED NetAct
CNUMLDAPserver
login:Nemuadmin loginaccepted
CNUMLDAPserver
login:Nemuadmin
LDAP connection
loginaccepted
login:Nemuadmin
login:Nemuadmin
loginaccepted
loginaccepted
LOGINRESTRICTION ENABLED NetAct
LOGINRESTRICTION ENABLED NetAct
CNUMLDAPserver
login:Nemuadmin loginrejected
LDAP connection
CNUMLDAPserver
login:Nemuadmin loginaccepted
login:Nemuadmin
login:Nemuadmin
loginrejected
loginaccepted
BTSSiteManager
noLDAP connection
TransportWebPage
noLDAP connection
user'sPC Nemuadmin=localaccount
This procedure applies to both users and machines (scripts) attempting to log in by means of a local user account. If user was able to log in with the local user account credentials due to login restriction being disabled, or due to the LDAP server being unavailable, those local user account sessions will not be impact if login restriction is subsequently enabled or the LDAP server becomes available. New attempts to login with the local user account credentials would be blocked.
5.6.3 LTE2360 system impact Interdependencies between features The LTE2360: Login Restriction with CNUM feature impacts the following features: •
•
LTE580: Session Login Delay When attempting to log in with the local user account credentials, the system will only apply the user-based delay and locking functionality of LTE580 to the account if it is not blocked due to LTE2360. LTE967: Password Aging and Account Locking When attempting to log in with the local user account credentials, the system will only apply aging and locking functionality to the account if it is not blocked due to LTE2360.
Impact on interfaces The LTE2360: Login Restriction with CNUM feature has no impact on interfaces.
244
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
Impact on network management tools The LTE2360: Login Restriction with CNUM feature has no impact on network management tools. Impact on system performance and capacity The LTE2360: Login Restriction with CNUM feature has no impact on system performance or capacity.
5.6.4 LTE2360 reference data Requirements Table 175
LTE2360 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE16A
not supported
Flexi Zone Controller
OMS
FL16A
16A
Flexi Multiradio 10 BTS
AirScale BTS
FL16A
not supported
UE support not required
Flexi Zone Micro BTS FL16A
NetAct 16.8
Flexi Zone Access Point FL16A
MME
SAE GW
support not required
support not required
Alarms There are no alarms related to the LTE2360: Login Restriction with CNUM feature. Commands There are no commands related to the LTE2360: Login Restriction with CNUM feature. Measurements and counters There are no measurements or counters related to the LTE2360: Login Restriction with CNUM feature. Key performance indicators There are no key performance indicators related to the LTE2360: Login Restriction with CNUM feature. Parameters Table 176
New parameters introduced by LTE2360 Full name
Abbreviated name
Managed object
Activate restrict login actRestrictLoginT LUAC to CNUM oCnum
Parent structure -
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 177
LTE2360 sales information
Product structure class Application software (ASW)
Issue: 01 Draft
License control SW Asset Monitoring
DN09237915
Activated by default No
245
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
5.7 LTE2361: Configurable BTS Login Banner The LTE2361: Configurable BTS Login Banner feature enables the operator to customize the BTS login banner, that is, the message which appears when logging in to a BTS using BTS Site Manager, Transport Web Page, or Secure Shell (SSH).
5.7.1 LTE2361 benefits The LTE2361: Configurable BTS Login Banner feature provides the means to adapt the login banner to local legal requirements and to fulfil operator's company security policy.
5.7.2 LTE2361 functional description The LTE2361: Configurable BTS Login Banner feature enables the operator to customize a BTS login banner. The login banner is displayed to the user along with a log-in prompt. This banner serves as a legal warning about the consequences of system misuse. The default login banner is shown in the figure below. Figure 34
Default login banner visible in BTS Site Manager
The operator can edit the default banner with BTS Site Manager (for a single BTS) or NetAct (for many sites). If operator does not create a custom login banner, the default one is used. The login banner for SSH connection is created separately from a login banner to BTS Site Manager/Transport Web Page (due to differences in text encoding). Two parameters are used to configure the login banner: • •
g
appLoginBannerText for login session using BTS SM/Transport Web Page platLoginBannerText for login session using SSH Note: There are certain browser limitations when using Transport Web Page login banner. When logging in using Mozilla Firefox or Google Chrome, the configured login banner is displayed. However, when logging in using Internet Explorer, default banner text of 300 character length is shown.
5.7.3 LTE2361 system impact The LTE2361: Configurable BTS Login Banner feature has no impact on features, interfaces, network management tools, and system performance and capacity
246
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
5.7.4 LTE2361 reference data Requirements Table 178
LTE2361 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE16A
not supported
Flexi Zone Controller
OMS
not supported
Flexi Multiradio 10 BTS
AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
not supported
not supported
not supported
NetAct
MME
SAE GW
UE
support not required
support not required
16.8
support not required
support not required
Alarms There are no alarms related to the LTE2361: Configurable BTS Login Banner feature. Commands There are no commands related to the LTE2361: Configurable BTS Login Banner feature. Measurements and counters There are no measurements or counters related to the LTE2361: Configurable BTS Login Banner feature. Key performance indicators There are no key performance indicators related to the LTE2361: Configurable BTS Login Banner feature. Parameters Table 179
New parameters introduced by LTE2361 Full name
Abbreviated name
Managed object
Parent structure
Platform login banner text for service account login via SSH interface
platLoginBannerText SECADM
-
Application login banner text for Transport Web Page and BTS Site Manager login page
appLoginBannerText
SECPRM
-
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 180
LTE2361 sales information
Product structure class Basic Software (BSW)
Issue: 01 Draft
License control -
DN09237915
Activated by default Yes
247
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
5.8 LTE2403: MHAs Auto-detection and Configuration The LTE2403: MHAs Auto-detection and Configuration feature introduces the functionality to auto-configure and commission auto-detectable masthead amplifiers (MHAs). An MHA is auto-detectable when it supports the antenna interface standards group (AISG 2.0).
5.8.1 LTE2403 benefits The LTE2403: MHAs Auto-detection and Configuration feature provides the following benefits: •
•
The BTS automatically detects MHAs and creates management objects (MO MHA) in the BTS SM. The entries of the antenna line to MHA/LNA connections will be automatically filled in, based on matching the detected line with a cell to antenna configuration. The manual configuration of the MHA in plug and play (PnP) installations is not necessary.
5.8.2 LTE2403 functional description Detection of MHAs The BTS detects attached MHAs before commissioning. There is one MHA-managed object, as defined in the site commissioning file (SCF) per low noise amplifier (LNA). When two LNAs belong to the same MHA, they contain the same product code, serial number, and detection line, as indicated by the scannedAntennaInterface parameter. Online commissioning If the operator uses BTS SM for online commissioning, the detected MHAs are visible in BTS SM. The operator cannot modify the self-discovered parameters. However, the operator is allowed to mark the detected MHAs as external and update other modifiable parameters. When the BTS receives the SCF, AISG-compliant MHAs that are marked as external are under user control and are not subject to auto-configuration by the BTS. Any MHAs that cannot be auto-configured need to be entered manually. For online commissioning using BTS SM see Use case 1: Auto-configure MHAs, using BTS SM online commissioning Offline commissioning If the operator uses NetAct or BTS SM for offline commissioning, all types of MHA objects can be configured manually. When the BTS receives a complete commissioning file, with cells configured either via BTS SM or NetAct, it creates the connection parameters. Enabling antenna lines for detection
248
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
After commissioning, the BTS continues periodically to detect newly-installed AISGcompliant MHAs on antennas that have 3GPP communication and DC voltage enabled by the operator. The operator enables an antenna line for detection, using the following three parameters: • • •
AL DC voltage enabled (alDcVoltageEnabled) Communication 3GPP enabled (communication3gppEnabled) Feeder voltage (feederVoltage).
These are the existing parameters, and there is no change as a result of the LTE2403: MHAs Auto-detection and Configuration feature. From the point of view of software, there is no precondition for the installation changes during this discovery procedure. However, for safety reasons, the operator has to block the radio first before MHAs are physically changed or added. When new cells are added, they trigger connection-parameter updates if radios/MHAs are installed. Cell reconfigurations may result in a different connection setting. Wiring MHAs Table 181: Wiring MHAs provides an overview of how to wire the MHAs in order for this feature to work properly. Table 181
Wiring MHAs
Cell to antenna configuration (resource list)
number of MHAs
Rule
1 radio with 2 ANTLs
1
The lower # ANT port is assigned to LNA1, and the higher # ANT is assigned to LNA2.
2 radios with 1 ANTL in each radio
1
The ANT port belonging to the lower instance # of the radio is assigned to LNA1 and ANTL belonging to the higher instance # of the radio is assigned to LNA2.
1 radio with 4 ANTLs
2
•
ANT port n is assigned to MHAx, LNA1
•
ANT port n+1 is assigned to MHAx, LNA2 ANT port n+2 is assigned to MHAy, LNA1 ANT port n+3 is assigned to MHAy, LNA2 n and n+2 are always odd number ports
• • •
2 radios with ANTLs each 2
• • • • •
Issue: 01 Draft
DN09237915
Lower instance radio, ANT port n is assigned to MHAx, LNA1 Lower instance radio, ANT port n+1 is assigned to MHAx, LNA2 Higher instance radio, ANT port n is assigned to MHAy, LNA1 Higher instance radio, ANT port n is assigned to MHAy, LNA2 n is always an odd number port
249
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
5.8.3 LTE2403 system impact Interdependencies between features There are no interdependencies between the LTE2403: MHAs Auto-detection and Configuration feature and any other feature. Impact on interfaces The LTE2403: MHAs Auto-detection and Configuration feature has no impact on interfaces. Impact on network management tools The LTE2403: MHAs Auto-detection and Configuration feature has no impact on network management tools. Impact on system performance and capacity The LTE2403: MHAs Auto-detection and Configuration feature has no impact on system performance or capacity.
5.8.4 LTE2403 reference data Requirements Table 182
LTE2403 hardware and software requirements
System release FDD-LTE16
Flexi Multiradio BTS FL16
Flexi Zone Controller
OMS
Not supported Support not required
Flexi Multiradio 10 BTS FL16
Not supported
UE Support not required
Flexi Zone Micro BTS
NetAct NetAct 16.2
MME Support not required
Flexi Zone Access Point Not supported SAE GW Support not required
Additional hardware requirements This feature requires the following hardware: All MHAs supporting the antenna interface standards group (AISG 2.0) The following hardware is not supported: • • •
MHAs that are configured as external or AISG non-compliant are excluded from this feature Nokia-harmonized MHAs are excluded from this feature Dual-band MHAs with one LNA per band are not supported
Parameters Table 183
New parameters introduced by LTE2403 Full name
Activate MHA autoconfiguration
250
Abbreviated name actMhaAutoConfig
DN09237915
Managed object MRBTS
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 184
Descriptions of operability features
Parameters modified by LTE2403
Full name
Abbreviated name
Managed object
Structure
Antenna band list
antBandList
MHA
-
Antenna beamwidth
antBeamwidth
MHA
antBandList
Antenna operating frequency band
antOperFreqBand
MHA
antBandList
Antenna operation gain
antOperGain
MHA
antBandList
Antenna line identifier
antlId
MHA
-
LNA number
lnaNumber
MHA
-
Sales information Table 185
LTE2403 sales information
Product structure class
License control
Application software (ASW)
-
Activated by default No
5.8.5 Other instructions Example: Use case 1: Auto-configure MHAs, using BTS SM online commissioning Actors: Operator, NetAct, BTS SM, BTS Preconditions: • •
The connection from BTS SM to the BTS is operational. The MHAs are installed according to the guidelines provided by Nokia.
Description: 1. The BTS power is on. 2. The BTS detects all connected and AISG-compliant (AISG2.0) MHAs. 3. The BTS informs BTS SM about the list of detected LNAs. For each LNA, the BTS informs about • •
the parameters obtained from the MHA the antenna line on which the LNA is detected
4. 5. 6. 7.
The operator begins online commissioning. The operator configures radios and cells. The operator sets the actAutoMhaConfig parameter to true. BTS SM presents the detected MHA/LNAs, provided by the BTS in step 3, to the operator for AISG-compliant MHA configurations. 8. The operator can optionally modify some selected MHA parameters (including the setting of the MHA object to external). 9. The operator optionally configures the AISG non-compliant MHAs.
Issue: 01 Draft
DN09237915
251
Descriptions of operability features
10. 11. 12. 13.
FDD-LTE16A, Feature Descriptions and Instructions
The operator finishes commissioning. BTS SM sends the SCF to the BTS. The BTS configures the MHAs. The BTS updates the SCF according to the new configurations and sends the changes to NetAct and BTS SM.
Postconditions: The BTS is commissioned, and the AISG-compliant MHAs are automatically configured.
Example: Use case 2: BTS detects a new MHA after commissioning Actors: NetAct, BTS Preconditions: • • • •
The connection from BTS SM to the BTS is operational. The actAutoMhaConfig feature flag is set to true. The ANTL parameters communication3gppEnabled, alDcVoltageEnabled on the antenna connected to the MHA are enabled. The ANTL parameter feederVoltage is set to the value matching the MHA type.
Description: 1. The BTS detects that an MHA is installed. 2. The BTS evaluates the cell configuration and configures the MHA. 3. The BTS updates the SCF according to the new configurations and sends the changes to NetAct and BTS SM (provided BTS SM is connected). Postconditions: The newly-installed MHA is in service, and all alarms are cleared.
5.9 LTE2507: Energy Efficiency Shut Down Mode with RF Sharing Benefits, functionality, system impact, reference data, instructions of the feature The LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature introduces a power saving mode for radio frequency (RF) sharing BTS configurations. It combines and verifies the existing energy saving features from different radio access technologies: RG301936 for 2G, RAN955 for 3G and LTE1103 for LTE. In areas that have multiple frequency layers, the cells can be switched on/switched off automatically, depending on the traffic, pre-defined load thresholds, and customizable power saving periods.
252
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
5.9.1 LTE2507 benefits The LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature provides the following benefit: •
The automated power amplifier (PA) switch-off during low traffic which can provide up to 45-60W power savings (per PA that is switched off).
5.9.2 LTE2507 functional description LTE2507 functional overview The LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature combines functionalities described in the single radio access technolgy (RAT) power saving features: • • •
RG301936: Intelligent MCPA TRX Shutdown (GSM) RAN955: Power Saving Mode for BTS (WCDMA) LTE1103: Load Based Power Saving for Multi-layer Networks (LTE)
The LTE2507 feature supports the following RF sharing configurations: • • •
GSM with WCDMA LTE with WCDMA LTE with GSM
Power saving group The LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature allows to automatically switch off/switch on the cells in the power saving group (PSGRP) depending on the load conditions (as described in the LTE1103: Load Based Power Saving for Multi-layer Networks feature). A power saving group (PSGRP) is a group of cells with a common coverage area configured together for power saving purposes. The following power saving criteria can be configured via NetAct or Eden-NET for each PSGRP: •
•
•
Switch-off order (Load-based power saving cell switch off order: lbpsCellSOOrder): a value assigned to each cell in a PSGRP defining which cell is next to switch off (on) after the load threshold is met. Low-load threshold (Load-based power saving minimum load: lbpsMinLoad): a level of traffic below which the next cell in a switch-off order is turned off. High-load threshold (Load-based power saving maximum load: lbpsMaxLoad): a level of traffic above which the next cell in a switch-on order is turned on.
Switching off the cell To automatically switch off a cell, the following conditions have to be met: • •
Issue: 01 Draft
The time is within a non-suspended energy saving period. There are no ongoing emergency calls.
DN09237915
253
Descriptions of operability features
• • •
FDD-LTE16A, Feature Descriptions and Instructions
There are no queued messages for Earthquake and Tsunami Warning System (ETWS) or Commercial Mobile Alert System (CMAS) in the cell. The aggregated load in the cells in the PSGRP is below the low-load threshold for at least five minutes. The estimated aggregated load for the PSGRP after the cell switches off does not exceed the high-load threshold.
g
Note: The eNB does not switch off a PSGRP cell, and it switches on a cell in energy saving mode, if eNB degraded or cell impacting faults are detected on the eNB.
g
Note: When all radio access technologies have switched off the pipes that share the power amplifier (PA), the PA is automatically switched off.
g
Note: Power amplifier switch-off is applicable for non-broadcast control channel (nonBCCH) pipe only. Switching on the cell After switching off the PSGRP cell, the eNodeB monitors the load of the active cells in the PSGRP. When the traffic load in the active cells exceeds the high-load threshold for at least two minutes, the switched-off cells are activated again in a reversed switch-off order.
g
Note: When a pipe that shares the PA is switched on, the PA is automatically switched on.
5.9.3 LTE2507 system impact LTE2507 impact on features Interdependencies between features To realize the benefits of the LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature, the LTE1103: Load Based Power Saving for Multi-layer Networks feature and at least one of the following features must be activated (depending on a radio acces technologies supported by the eNodeB): • •
RAN955: Power Saving Mode for BTS for 3G RG301936: Intelligent MCPA TRX Shutdown for 2G
For activating the LTE1103: Load Based Power Saving for Multi-layer Networks feature, see Activating and configuring LTE1103: Load Based Power Saving for Multi-layer Networks. The LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature is impacted by the following features: •
LTE1203: Load-based Power Saving with Tx Path Switching Off
The LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature has mirror features for other radio access technologies: • •
254
RG602496: Energy efficiency Shut Down Mode with RF Sharing for GSM RAN3247: Energy Efficiency Shut Down Mode with RF Sharing for WCDMA
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
Impact on interfaces The LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature has no impact on interfaces. Impact on network management tools The LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature has no impact on network management tools. Impact on system performance and capacity The LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature has no impact on system performance or capacity.
5.9.4 LTE2507 reference data LTE2507: Energy Efficiency Shut Down Mode with RF Sharing requirements and sales information Requirements Table 186 System release
LTE2507 hardware and software requirements Flexi Multiradio BTS
FDD-LTE16A
Not supported
Flexi Zone Controller
OMS
Support not required
Flexi Multiradio 10 BTS FL16A
UE
LTE OMS16A
Support not required
Nokia AirScale BTS
Flexi Zone Micro BTS
Not supported
Support not required
NetAct
MME
16.8
Support not required
Flexi Zone Access Point Support not required SAE GW Support not required
Alarms There are no alarms related to the LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature. BTS faults and reported alarms There are no faults related to the LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature. Commands There are no commands related to the LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature. Measurements and counters There are no measurements or counters related to the LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature. Key performance indicators There are no key performance indicators related to the LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature. Parameters
Issue: 01 Draft
DN09237915
255
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
There are no parameters related to the LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature. Sales information Table 187
LTE2507 sales information
Product structure class
License control
Application software (ASW)
g
–
Activated by default No
Note: The LTE2507: Energy Efficiency Shut Down Mode with RF Sharing feature uses the LTE1103 feature licence.
5.10 LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring The LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature introduces new energy-monitoring software support for radio frequency (RF) modules and system modules (SMs) with power meter hardware on board. New performance measurement (PM) counters with energy consumption values [kWh] are made, based on the power meter's reports. In addition, the voltage and power values of RF and system modules can be viewed in BTS SM in a new Energy Efficiency Monitoring display.
5.10.1 LTE2508 benefits The LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature enables monitoring energy consumption of radio modules and system modules. Based on power reports and traffic load, the usage of BTS modules can be optimized, resulting in energy savings (for example, the additional Power Amplifiers can be switched off).
5.10.2 LTE2508 functional description An overview of power meter measurements and their results: new counters and power reports visible in network management tools Functional overview The LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature introduces new options to gather and view energy-related information from radio frequency (RF) modules and system modules (SMs) equipped with a power meter entity (enabled by the Activate BTS Embedded Power Meter for Energy Efficiency Monitoring flag). A power meter measures voltage [V] and amperage [A] of RF and system modules (along with their extensions). Measurement samples are sent to Operations, Administrations and Maintenance (OAM) software and transformed into new counters. In the case of BTS SM, a new Energy Efficiency Monitoring view can be displayed, showing voltage [V] and power [W] values of RF and system modules, based on power reports created by the OAM software. Figure 35: From power meter to Energy Efficiency Monitoring shows the process, results, and entities involved in the LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature.
256
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Figure 35
Descriptions of operability features
From power meter to Energy Efficiency Monitoring
Power meter: Measuring voltage and amperage The power meter is hardware installed in RF and system modules, capable of doing voltage and amperage measurements. The resolution of power meter's measurement is five digits after decimal point (0.00001). The accuracy of a measurement depends on the hardware used but follows the requirement described in ETSI 202 336-12 standard. The power meter sends measurement samples to the OAM software, where the voltage and amperage values are converted into new energy consumption counters. OAM software: Creating new counters and power reports The OAM software in the LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature performs two main tasks: • •
g
Calculates energy consumption counters based on the power meter's measurement Creates power reports (one-minute samples with voltage and power values of powermeter-capable HW) and sends them to BTS SM in a DataChangeNotif message Note: If an RF module or system module does not have a power meter on board, no voltage and power values are sent by OAM to BTS SM in the form of power reports.
The LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature supports RF sharing. For an RF-shared radio, values reported by RF are counted only in master radio access technology (RAT) for this RF. Also, power reports in BTS SM are visible only in master RAT.
g
Issue: 01 Draft
Note: For an RF-shared radio, where LTE is a slave RAT, the PM counters ENERGY_CONSUMPTION_IN_RF and ENERGY_CONSUMPTION_IN_BTS do not include any power measurements from LTE for this radio.
DN09237915
257
Descriptions of operability features
g
FDD-LTE16A, Feature Descriptions and Instructions
Note: The Energy Efficiency Monitoring display in BTS SM shows no voltage or power measurements from LTE for the radio if LTE is a slave RAT. BTS SM: Displaying the Energy Efficiency Monitoring window The LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature introduces a new Energy Efficiency Monitoring display in BTS Site Manager (BTS SM). The new display window presents the voltage and power information of RF and system modules, based on power reports from OAM (the values are updated every one minute, if changed). Figure 36: An example of Energy Efficiency Monitoring display in BTS SM (may differ in later releases) shows voltage and power values for an FSMF system module (no power meter on board) with an FXED RF module (power meter capable). Figure 36
An example of Energy Efficiency Monitoring display in BTS SM (may differ in later releases)
NetAct: Displaying energy consumption counters New counters introduced by the LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature can be viewed in NetAct (as well as in BTS SM). Counters are based on a sum of measurement samples (by default, in 15- minute blocks, but the counter measurement period is adjustable).
5.10.3 LTE2508 system impact Interdependencies between features There are no interdependencies between the LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature and any other feature. Impact on interfaces The LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature has no impact on interfaces. Impact on network management tools The LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature impacts network management tools as follows:
258
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
Descriptions of operability features
BTS Site Manager (BTS SM): – –
New data fields (voltage and power) have been added to the SiteConf file for radio modules and system modules. A new Energy Efficiency Monitoring display has been added (it can be reached from the Tests menu bar).
Impact on system performance and capacity The LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature has no impact on system performance or capacity.
5.10.4 LTE2508 reference data Requirements Table 188
LTE2508 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
Not supported
Not supported
Not supported
NetAct
MME
SAE GW
UE
Not supported LTE OMS16A
Support not required
NetAct 16.8
Support not required
Support not required
Additional hardware and software requirements:
g
Note: The LTE2508 compatible RF modules and system modules list is not binding and should be treated only as a starting point before confirming power meter support with Nokia sales representatives. The power meter support for any new RF or system modules can be found in a corresponding HW description. LTE2508 compatible RF modules and system modules (with a power meter on board): •
The requirements of system modules for the LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature: – –
– •
The requirements of radio frequency (RF) module or remote radio head (RRH) for the LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature: – – – –
Issue: 01 Draft
FSMr2: not supported FSMr3 (FSMF, FBBA, FBBC): instead of power meter measurements, the static values are used to create counters (there is no power meter HW in FSMr3 system modules). See the Table 189: Static values used to create energy consumption counters for FSMr3 modules section for more details. AirScale system modules: not supported
FHEB, FHDB, FHEF, FHEG and FHEJ are supported FRGU, FXED, FRMF, FRSA are supported FXEE, FXEF and FRGX are supported FRGY, FHFB, FRBE, FRBF, FRNC, FRCC, FRCG, FRBG, FRAA, FHED, FHEH, FRHG, FRGB and FRGA are supported
DN09237915
259
Descriptions of operability features
–
FDD-LTE16A, Feature Descriptions and Instructions
FREG, FHEL and FRIJ are supported
Table 189
Static values used to create energy consumption counters for FSMr3 modules FSMF
FBBA
0.125 kW
g
FBBC
0.085 kW
0.091 kW
Note: As for RF modules (and RRHs) without a power meter, the zero value is used to create energy consumption counters. Alarms There are no alarms related to the LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature. BTS faults and reported alarms There are no faults related to the LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature. Commands There are no commands related to the LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature. Measurements and counters Table 190
New counters introduced by LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring
Counter ID
Counter name
Measurement
M8045C Energy consumption in system 0 modules
LTE BTS Energy Monitoring
M8045C Energy consumption in radio 1 modules
LTE BTS Energy Monitoring
M8045C Energy consumption in BTS 2
LTE BTS Energy Monitoring
For counter descriptions, see LTE Performance Measurements and Key Performance Indicators. Key performance indicators There are no key performance indicators related to the LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring feature. Parameters Table 191
New parameters introduced by LTE2508 Full name
Power meter enabled
260
Abbreviated name
actPowerMeter
DN09237915
Managed object
Parent structure
MRBTS/B TSSCL
-
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 191
Descriptions of operability features
New parameters introduced by LTE2508 (Cont.) Full name
LTE BTS energy monitoring
Abbreviated name
Managed object
mtBtsEnergyMonito MRBTS/L ring NBTS/PM RNL
Parent structure
-
For parameter descriptions, see FDD-LTE BTS Parameters. Sales information Table 192
LTE2508 sales information
Product structure class Application software (ASW)
License control Pool licence
Activated by default No
5.11 LTE2562: ANR Inter-RAT 1xRTT – O&M Assisted The LTE2562: ANR Inter-RAT 1xRTT – O&M Assisted feature introduces UE periodic measurements to detect unknown adjacent CDMA2000 1x radio transmission technology (1xRTT) cells. When the eNB detects a new 1xRTT neighbor cell from a UE, it stores the 1xRTT neighbor in the database visible via SON reports. After detection the neighbor cell is used for related mobility procedures.
5.11.1 LTE2562 benefits The LTE2562: ANR InterRat 1xRTT - O&M Assisted feature provides the following benefits: • •
Reducing operational expenses in neighbor cell planning by the automated detection of unknown adjacent 1xRTT cells. Autonomous removal 1xRTT Neighbour Relations which are not/no longer used by mobility management procedures of the eNB. The removal can be controlled via threshold-settings.
5.11.2 LTE2562 functional description Overview In LTE networks, the UE mobility in the radio-resource-control (RRC)-connected state relies on the information provided by an explicit neighbor cell list. To support and allow the automated configuration of 1xRTT neighbor cells, a special mechanism is implemented to discover unknown cells: 1. The trigger to start searching for 1xRTT neighbors is based on internal radioresource-management (RRM)/mobility-management events. 2. The detection of unknown neighbor cells can take place during periodic measurements activated by the Flexi Multiradio BTS for automatic-neighbor-relation (ANR)-capable UEs.
Issue: 01 Draft
DN09237915
261
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
3. Upon detecting an unknown cell, the Flexi Multiradio BTS uses preconfigured values to fill the remaining parameters of the neighbor cell.
g
Note: The feature LTE2562 is only applicable when parameter rttCellIdInfo value = 0 4. To reduce call drops for a first handover to a newly-detected neighbor cell, the Flexi Multiradio BTS supports specific ANR mechanism: Before the first HO to a newly-detected cell is triggered, it detects and configures any unknown 1xRTT neighbor cell as early as possible. This kind of operational mode of ANR (Fast Search ANR) is intended to build as fast as possible the LTE cell's 1xRTT neighbor relations. Additionally a long-run periodical search for new 1xRTT neighbors (Slow Search Active ANR) is supporting this kind of relations. Fast and slow search mode thresholds can be set by the operator. Fast search active ANR The Flexi Multiradio BTS requests every capable UE to actively scan for unknown 1xRTT neighbor cells on the respective carrier frequency. In the following cases a 1xRTT carrier is in fast search mode: • • •
at feature activation at cell (re-)start and every time a UE reports an unknown 1xRTT cell
Slow search active ANR The 1xRTT carrier frequency enters the slow search mode • •
after a given number of failed attempts at finding a new 1xRTT neighbor cell on that carrier frequency or after the limit for maximum number of neighboring 1xRTT cells for ANR detection has been reached.
The operator is able to control the behavior of these ANR mechanisms via configuration settings: • • •
• •
the switching on/off ANR per Flexi Multiradio BTS (Activate ANR 1xRTT) the operator-configurable parameters for thresholds for fast or slow active ANR (for example: Minimum number threshold of 1xRTT neighbor relations) the limit for a maximum number of neighboring 1xRTT cells per carrier subject to ANR measurements (Limit for ANR created 1xRTT neighbor relations) the configuration of carrier frequencies of the 1xRTT system to be scanned. See MOC ANRPRX and MOC ANR (CDMA2000 1xRTT carrier frequency ) the operator-configurable parameter for the 1xRTT cell identifier resolution mode (CDMA2000 1xRTT reference cell id)
Autonomous removal of 1xRTT Neighbour Relations which are not/no longer used by the mobility management procedures of the eNB With the automatic neighbor relation removal, a neighbor relation is deleted in case it is judged to be no more important, based on its recent history (for example: it was not observed in any mobility procedures during a pre-defined time period). The observation period is operator configurable and characterized by a high granularity (order of day) to
262
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
prevent toggling of object deletion and re-creation in the network. The deletion of a neighbor relation corresponds to the deletion of the corresponding object stored on cell level. Neighbor relations can be protected from auto-deletion by operator settings. The changes done with automatic deletion are reported using CM history in NetAct and SON Reports, if available. Monitoring of ANR The monitoring of ANR is supported by means of performance measurements. The following events can be monitored: • •
the number of attempted ReportStrongestCellForSON counter (RSCFS) the number of received RSCFS counter with an unknown 1xRTT neighbor cell
The Flexi Multiradio BTS sends a configuration change notification (CCN) to NetAct to inform the operator about the new neighbor cell configurations. The CCN is sent after new neighbor cell relations have been successfully included into the local configuration data.
5.11.3 LTE2562 system impact Interdependencies between features The following features must be activated before activating the LTE2562: ANR Inter-RAT 1xRTT – O&M Assisted feature: •
LTE426: System Time Broadcast for SIB8 To configure the ReportStrongestCellforSon measurement, LTE426 has to be enabled automatically for SIB8 system time broadcast when LTE2562 is activated.
The following features must be deactivated before activating the LTE2562: ANR InterRAT 1xRTT – O&M Assisted feature: • • • • • • • • •
LTE56: Inter-RAT Handover to WCDMA LTE442: Network-assisted Cell Change LTE873: SRVCC to GSM LTE908: ANR Inter-RAT UTRAN – Fully UE-based LTE872: SRVCC to WCDMA LTE2162: SRVCC for Network Deployments Not Supporting PS HO LTE736: CS Fallback to UTRAN LTE1073: Measurement-based Redirect to UTRAN LTE1357: LTE-UTRAN Load Balancing
Impact on network management tools The LTE2562: ANR Inter-RAT 1xRTT – O&M Assisted feature has no impact on network management tools. Impact on system performance and capacity The LTE2562: ANR Inter-RAT 1xRTT – O&M Assisted feature impacts system performance and capacity as follows:
Issue: 01 Draft
DN09237915
263
Descriptions of operability features
•
•
FDD-LTE16A, Feature Descriptions and Instructions
The ReportStrongestCellsForSON measurements are done immediately after an initial context setup (for example during the attach or mobile-originated call), handover, or connection re-reestablishment using measurement gaps. There is no impact on the RAN level system capacity.
5.11.4 LTE2562 reference data Requirements Table 193
LTE2562 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Flexi Zone Controller FL16A
Flexi Multiradio 10 BTS
Support not required
Nokia AirScale BTS
FL16A
OMS
FL16A
UE
LTE OMS16A
Flexi Zone Micro BTS FL16A
NetAct
3GPP R8 UE capabilities
NetAct 16.8
Flexi Zone Access Point FL16A
MME Support not required
SAE GW Support not required
Measurements and counters Table 194
New counters introduced by LTE2562
Counter ID
Counter name
Measurement
M8008C22
Number of attempted RSCFS for 1xRTT
This counter provides the number of attempted reportStrongestCellsForSon (RSCFS) measurement reports for 1xRTT.
M8008C23
Number of received RSCFS with unknown 1xRTT neighbor cell
This counter provides the number of received reportStrongestCellsForSon (RSCFS) measurement reports with unknown 1xRTT neighbor cell.
For counter descriptions, see LTE Radio Access Operating Documentation/ Reference/Counters.. Parameters Table 195
New parameters introduced by LTE2562 Full name
264
Abbreviated name
Managed object
Parent structure
Activate ANR 1xRTT
actAnrRtt
LNBTS
-
Activate autonomous removal of 1xRTT neighbors
actAutoRttNeighRemoval
ANR
-
ANR 1xRTT RSCFS timer
anrRttTRSCFS
ANR
-
Idle time threshold for 1xRTT neighbour relations
idleTimeThresRttNR
ANR
-
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 195
Descriptions of operability features
New parameters introduced by LTE2562 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
Minimum not activated minNotActivatedRttRSCFS 1xRTT ReportStrongestCellsForS on
ANR
-
Minimum number threshold minNumThresRttNR of 1xRTT neighbor relations
ANR
_
Sample Number threshold of 1xRTT measurement reports
samNumThresRttNR
ANR
-
Sample Number threshold of 1xRTT measurement reports
tTmpBlacklistRttANR
ANR
-
ANR basic configuration identifier
anrId
ANR
-
ANR 1xRTT pilot strength anrRttPstrThres threshold
ANRPRX
-
Cells to apply list
cellsToApplyList
ANRPRX
-
Enable ANR profile
enableAnrProfile
ANRPRX
-
LNRELX default values
lnRelXDefaults
ANRPRX
-
Limit for ANR created lnRelXLimitForAnr 1xRTT neighbor relations
ANRPRX
-
List of blacklisted PCIs pciBlacklist
ANRPRX
-
CDMA2000 1xRTT carrier rttCarrierFreq frequency CDMA2000 1xRTT carrier frequency
ANRPRX
-
ANR profile for 1xRTT identifier
anrPrXId
ANRPRX
-
Remove allowed
removeAllowed
LNRELX
-
Table 196
Parameters modified by LTE2562 Full name
Abbreviated name
Managed object
Parent structure
CDMA2000 1xRTT cell ID info
rttCellIdInfo
LNCEL
-
CDMA2000 1xRTT reference cell id
rttRefCellId
LNCEL
-
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters.. Sales information
Issue: 01 Draft
DN09237915
265
Descriptions of operability features
Table 197
FDD-LTE16A, Feature Descriptions and Instructions
LTE2562: ANR InterRat 1xRTT - O&M Assisted sales information
Product structure class
License control
Application software (ASW)
-
Activated by default No
5.12 LTE2591: UE-level MRO Benefits, functionality, system impact, reference data, instructions of the feature The LTE2591: UE-level MRO feature adds a configurable offset to the cell individual offset (CIO) value of a neighbor cell to avoid further unnecessary handovers (HOs) when a ping pong HO is detected between a serving cell and a neighbor cell.
5.12.1 LTE2591 benefits The LTE2591: UE-level MRO feature provides the following benefits: • •
The handover performance is improved because of reduced number of unnecessary handovers. A more aggressive CIO can be applied to match the high-speed users' demands while the static users are protected against the ping pong HOs.
5.12.2 LTE2591 functional description Ping pong detection The same rule is applied as for a centralized Mobility Robustness Optimization (MRO) ping pong described in the LTE1768: MRO Ping Pong feature. The eNB detects the ping pong occurrences by analyzing the UE history information during the HO preparation phase. When the eNB detects that the UE previously visited a serving cell and the elapsed time is lower than the configurable threshold, the HO is considered to be a ping pong. The ping pong can be either of the following scenarios: • •
cell 1 ► cell 2 ► cell 1 cell 1 ► cell 2 ► cell 3 ► cell 1
This feature covers only scenarios, where the cell 2 is an LTE cell. The cell 3 and the potential further cells can be a UTRAN cell as long as the UTRAN network supports passing of the UE history. Ping pong prevention When the UE enters a cell by a handover that is considered to be a ping pong, the eNB alters the original CIO value for the neighbor cell (cell 2 in the given scenario) by a configurable offset. The neighbor cell can be either an intra-frequency or an interfrequency LTE cell. The altered CIO value is sent to the UE within the measurement configuration. Interworking with centralized MRO
266
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
After the UE alters the CIO, it is no longer considered for the MRO counter Too Late HO. However, the Too Early and the Ping Pong conditions are handled as per the LTE1768: MRO Ping Pong feature. The original ping pong event is still counted (when the UE alters the CIO). In the Too Late case (after the UE has altered the CIO), a new counter Too Late after UE CIO adjustment must be incremented.
5.12.3 LTE2591 system impact LTE2591: UE-level MRO impact on features and system performance and capacity Interdependencies between features The following features impact the LTE2591: UE-level MRO feature: •
•
•
•
•
LTE533: Mobility Robustness With this feature, CIO modifications are applied on top of the CIO (cellIndOffNeigh parameter) value because of the ping pong handover (HO) provided by centralized MRO algorithms. LTE1113: eICIC - Macro With this feature, the CIO modifications are applied on top of CIO (cellIndOffNeighDelta parameter) value because of the ping pong HO provided by eICIC. LTE1140: Intra-frequency Load Balancing With this feature, the CIO modifications are applied on top of CIO (cellIndOffNeighDelta parameter) value because of the ping pong HO provided by load balancing (LB) algorithms. LTE1170: Inter-frequency Load Balancing In this feature, HOs are not considered for ping pong detection because of the load conditions. LTE1768: MRO Ping Pong This feature provides the ping pong detection function.
Impact on interfaces The LTE2591: UE-level MRO feature has no impact on interfaces. Impact on network management tools The LTE2591: UE-level MRO feature has no impact on network management tools. Impact on system performance and capacity The LTE2591: UE-level MRO feature affects system performance and capacity as follows: •
•
This feature introduces an active CIO management (via RRC Connection Reconfiguration messages) for UEs experiencing ping pong HOs. This might improve the throughput for UEs in ping pong locations. This feature might improve the handover success rate for the affected UEs.
5.12.4 LTE2591 reference data LTE2591: UE-level MRO requirements, measurements and counters, KPIs, parameters, and sales information Requirements
Issue: 01 Draft
DN09237915
267
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
Table 198
LTE2591 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
AirScale FDD
FL16A
Not supported
UE
LTE OMS16A
3GPP R8 mandatory
Flexi Zone Micro BTS FL16A
NetAct NetAct 16.8
Flexi Zone Access Point FL16A
MME
SAE GW
Support not required
Support not required
Alarms There are no alarms related to the LTE2591: UE-level MRO feature. BTS faults and reported alarms There are no faults related to the LTE2591: UE-level MRO feature. Commands There are no commands related to the LTE2591: UE-level MRO feature. Measurements and counters Table 199
New counters introduced by LTE2591
Counter ID
Counter name
M8021C43
MRO_LATE_HO_MOD_UE
Table 200 Counter ID
Measurement LTE Handover
Existing counters related to LTE2591 Counter name
Measurement
M8021C20
MRO_LATE_HO
LTE Handover
M8015C16
MRO_LATE_HO_NB
LTE Neighbor Cell Related Handover
M8015C20
MRO_PING_PONG_HO_NB
LTE Neighbor Cell Related Handover
For counter descriptions, see LTE Performance Measurements and Key Performance Indicators. Key performance indicators Table 201
New key performance indicators introduced by LTE2591
KPI ID LTE_6012a
KPI name E-UTRAN Number of Late HO Events for UEs with modified CIO
For KPI descriptions, see LTE Performance Measurements and Key Performance Indicators. Parameters
268
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 202
Descriptions of operability features
New parameters introduced by LTE2591 Full name
Abbreviated name
Managed object
Parent structure
Activate UE Level MRO
actUeLevelMro
LNBTS
-
UE Level MRO Offset
ueLevelMroOffset
LNCEL
-
For parameter descriptions, see Flexi Multiradio BTS LTE Commissioning, RNW and Transmission Parameters. Sales information Table 203
LTE2591 sales information
Product structure class
License control
Application software (ASW)
Pool license
Activated by default No
5.13 LTE2621: eNodeB Limitation Actions for License Management in LTE The LTE2621: eNodeB Limitation Actions for License Management in LTE feature enhances software license management. This is performed by introducing a mechanism to limit BTS functionality in case licenses are not available.
5.13.1 LTE2621 benefits The LTE2621: eNodeB Limitation Actions for License Management in LTE feature offers a stricter control over the licences.
5.13.2 LTE2621 functional description The LTE2621: eNodeB Limitation Actions for License Management in LTE feature enhances the license management introduced by the LTE2593: SW License Management in LTE feature (release LTE16). It defines a mechanism used to limit BTS functionality in case the required license capacity is missing. For more detailed information on licensing in LTE, see LTE Operating Documentation/System Description/LTE License Operation. License management in LTE All licenses in LTE are pool licenses. After ordering license capacity, pool license keys and ordered capacity can be retrieved via the CLicS tool, which is Nokia Central Licensing System to generate license files. Then, the license is installed in the CLS pool. The OSS SWEM (SW Entitlement Manger, a component of the SW Asset Monitoring) tool calculates the required license capacity. The capacity is determined based on the NetAct Regional Cluster (NetAct RC) database configuration parameters. The OSS SWEM cooperates with the CLS to allocate calculated pool license capacity. Licenses are not downloaded to the eNodeB (eNB), but they are kept in CLS. Limitation mechanism
Issue: 01 Draft
DN09237915
269
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
SWEM is continuously checking NetAct configuration data to verify the activation and capacity of features. For example, if LTE788: Support of 16 QAM (UL) is activated, SWEM is continuously checking for how many cells the feature has been activated and comparing with the available license capacity. In case of missing licenses, a limitation command is raised to the BTS. As a result of limitation, the customer is able to continue using the feature, however: • •
maximum number of concurrent data users is limited to the currently licensed value throughput starts to be reduced (5% reduction per week down to 50%)
This approach eliminates the risk of unintended operational outage of the BTS due to missing licenses. The BTS stays operable, but it is limited stepwise. The effect of limitation can be observed by means of counter Failed setup attempts for initial E-RABs due to missing license. Before limitations start, there is a 14-day grace period, which enables filling up the pool with missing license capacity. Limitations are indicated by alarm 7658 Base Station License Limitation to inform the user about the type of limitation. After filling up the pool with missing license capacity, limitation actions are stopped within one hour. Types of limitations Most sales items (SI) are protected by a general limitation, which means that the BTS will not accept additional data users, and the throughput will be gradually reduced (5% reduction per week down to 50%). Sales items, which are not protected by general litimation, are: • • • •
Data Users Daily User Plane Data Volume Quarterly User Plane Data Volume Configured AirScale BB capacity
The limitations do not affect handovers, re-establishments, emergency calls, high priority calls and LTE1074: Multimedia Priority Services.
5.13.3 LTE2621 system impact Interdependencies between features The following features are connected to the LTE2621: eNodeB Limitation Actions for License Management in LTE feature: • •
LTE2593: SW License Management in LTE – introduces a framework for license management in LTE LTE2417: IP Traffic Capacity – limits the user plane traffic accordingly to the license capacity
Impact on interfaces The LTE2621: eNodeB Limitation Actions for License Management in LTE feature has no impact on interfaces. Impact on network management tools The LTE2621: eNodeB Limitation Actions for License Management in LTE feature has no impact on network management tools. Impact on system performance and capacity If licenses are missing some users will be rejected during the call setup what will be visible in the related KPIs.
270
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
5.13.4 LTE2621 reference data Requirements Table 204
LTE2621 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE16A
not supported
Flexi Zone Controller
OMS
not supported
Flexi Multiradio 10 BTS
AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
not supported
not supported
not supported
NetAct
MME
SAE GW
UE
support not required
support not required
support not required
support not required
support not required
BTS faults and reported alarms Table 205
BTS faults related to LTE2621
Fault ID
4337
Fault name
Reported alarms Alarm ID
Active users license limitation
7658
Alarm name
BASE STATION LICENSE LIMITATION
For fault descriptions, see LTE Operating Documentation/Reference/Alarms and Faults. Measurements and counters Table 206
New counters introduced by LTE2621
Counter ID
Counter name
Measurement
M8006C Failed setup attempts for 302 initial E-RABs due to missing license
LTE EPS Bearer
M8049C Maximum number of active UEs 0 in eNodeB
LTE Sales Item Monitoring
For counter descriptions, see LTE Operating Documentation/Reference/Counters and Key Performance Indicators. Key performance indicators There are no key performance indicators related to the LTE2621: eNodeB Limitation Actions for License Management in LTE feature. Parameters Table 207
New parameters introduced by LTE2621 Full name
Abbreviated name
Maximum number of maxNumActUEeNB active users in the eNB
Issue: 01 Draft
DN09237915
Managed object CAPLIML
Parent structure
-
271
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
For parameter descriptions, see LTE Operating Documentation/Reference/Parameters Sales information Table 208
LTE2621 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
5.14 LTE2633: System Upgrade to FDD-LTE 16A Benefits, functionality, system impact, and reference data of the feature The LTE2633: System Upgrade to FDD-LTE 16A feature supports system upgrade for the following releases: • •
From FDD-LTE 15A to FDD-LTE 16A From FDD-LTE 16 to FDD-LTE 16A
The system upgrade from FDD-LTE 15A release or FDD-LTE 16 release to FDD-LTE 16A release for Flexi Zone (FZ) standalone outdoor and indoor small cells and controller configuration is also supported.
5.14.1 LTE2633 benefits The LTE2633: System Upgrade to FDD-LTE 16A feature provides the operator with a smooth system upgrade.
5.14.2 LTE2633 functional description The system upgrade is possible in one step, and installation of intermediate software version is not needed. The LTE2633: System Upgrade to FDD-LTE 16A feature includes backward compatibility and provides the possibility of automatic fallback or rollback to the previous release that had been activated before the upgrade. The following network elements (NEs) are impacted: • • • • • • •
Flexi Multiradio BTS Flexi Zone (FZ) NetAct including the Optimizer, TraceViewer, and Northbound interfaces Operation and management server (OMS) Traffica Layer 3 Data Collector (L3DC) with its applications as layer 2 data analyzer Self-organizing network (SON) manager
The system upgrade is performed in a top-down approach, which starts with NetAct and ends when all the evolved Node Bs (eNBs) are upgraded. During the upgrade, the management and network elements should maintain compatibility with other management and network elements that are in the active release or in the previous release before the upgrade.
272
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
g
Descriptions of operability features
Note: The operator can perform the activation of the new software from NetAct or BTS site manager (BTSSM). The Traffica and L3DC support local software management. Software upgrade from FDD-LTE 15A to FDD-LTE 16A The system upgrade supports the following software upgrades: • • • • •
NetAct 15.5 to NetAct 16.8 LTO15A to LOMS16A Traffica15.5 to Traffica16.5 L3DC15 to L3DC16.5 eNB upgrades: – – –
FL15A to FL16A FLF15A to FLF16A FLC15A to FLC16A
Software upgrade from FDD-LTE 16 to FDD-LTE 16A The system upgrade supports the following software upgrades: • • • • •
NetAct 16.2 to NetAct 16.8 LOMS16 to LOMS16A Traffica16 to Traffica 16.5 L3DC16 to L3DC16.5 eNB upgrades: – – –
FL16 to FL16A FLF16 to FLF16A FLC16 to FLC16A
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 16.8 supports the OMS and eNB with FDD-LTE 15A and FDD-LTE 16 releases. LOMS16A supports the eNB with FDD-LTE 15A and FDD-LTE 16 releases. Traffica16.5 supports the L3DC and eNB with FDD-LTE 15A and FDD-LTE 16 releases. L3DC16.5 supports the eNB with FDD-LTE 15A and FDD-LTE 16 releases.
Data migration All operator-configured data are maintained in the system. Configuration data created in the earlier release are automatically converted into a new format that is valid for the new release during the upgrade. The data include the following: • • •
Issue: 01 Draft
All configuration data of the Flexi Multiradio BTS, OMS, NetAct, L3DC, and Traffica Customized view in the BTSSM or NetAct user-specified accounts and passwords User-specified accounts and passwords
DN09237915
273
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
The following system data should be uploaded or backed up before the upgrade: • • •
g
Network security-related system data (such as certificates and keys) User security-related data (such as user accounts and passwords) Performance measurement (PM) data Note: Failure to backup the data or upload it to NetAct might cause the data to be lost.
If there are used command lines or scripts, they must be backward compatible, or a converter must be available for the supported upgrade paths. The software converter is available in online or offline mode. Software fallback Software fallback is an automatic activation of an earlier software version that is active before the software upgrade. Fallback is triggered when the eNB or OMS cannot activate its new software version or use a new database configuration version. After a successful fallback, the passive software build is active in all the hardware units. All of the components activate the stored configuration data without reverse migrating or converting to a new configuration data.
g g
Note: In case of minor failures, no software 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 for the failure. Note: In case of an inconsistent fallback where in the eNB does not locally store the complete fallback software for all the hardware units, software download from NetAct is requested. Software rollback Software rollback is a manually initiated software fallback using the BTSSM or NetAct software management (SWM). The operator can trigger software rollback when key services are not successfully activated after the software upgrade. Any configuration updates done with the new software are lost as soon as software rollback is triggered. Software rollback is only guaranteed if the source software version has not been removed or overwritten in a non-volatile storage (NVS). Software rollback is done with the software stored in the passive file system and when no software download from the server is part of the operation. If the passive software has been overwritten with a different software version, rollback to the former release is not possible.
g
Note: Software rollback to the stored software 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 software upgrade must be evaluated before triggering software rollback to avoid service outage. 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 done 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 that is lower than the current software version in the Update SW to BTS Site window on the BTSSM and clicks Update, a software downgrade occurs.
274
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
g
Descriptions of operability features
Note: Software downgrade must not be executed. Software downgrade to an earlier software version is not guaranteed and might end up in an uncommissioned state of the eNB.
g
Note: Software rollback operation from the NetAct might interrupt ongoing local operations triggered from the BTSSM such as commissioning without local user warning.
5.14.3 LTE2633 system impact LTE2633: System Upgrade to FDD-LTE 16A impact on features, system performance, and capacity Interdependencies between features The LTE2378: FSM D/E (FSMr2) Support after FDD-LTE 15A feature supports the upgrade of the FSMr2 evolved Node Bs (eNBs) to the latest FDD-LTE 15A software using the FDD-LTE 16A software package. The FDD-LTE 16 software package might contain the updates, but the FSMr2 reports its software version as FDD-LTE 15A. Impact on interfaces The LTE2633: System Upgrade to FDD-LTE 16A feature has no impact on interfaces. Impact on network management tools The LTE2633: System Upgrade to FDD-LTE 16A feature impacts the BTS site manager (BTSSM) and NetAct for the FSMr2. The BTSSM and NetAct maintain the FDD-LTE 15A configuration management (CM), performance measurements (PM), alarms, and faults. The topology version for the FSMr2 is FDD-LTE 15A as displayed in NetAct. Impact on system performance and capacity The LTE2633: System Upgrade to FDD-LTE 16A feature impacts system performance and capacity as follows: • •
The end user will experience a service degradation and partial service loss during the system upgrade. The downtime for the network entities is reduced to the activation of the new software during the system upgrade.
5.14.4 LTE2633 reference data LTE2633: System Upgrade to FDD-LTE 16A requirements and sales information Requirements Table 209
Issue: 01 Draft
LTE2633 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL16A
DN09237915
Flexi Zone Micro BTS FLF16A
Flexi Zone Access Point FLF16A
275
Descriptions of operability features
Table 209
FDD-LTE16A, Feature Descriptions and Instructions
LTE2633 hardware and software requirements (Cont.)
Flexi Zone Controller
OMS
FLC16A
UE
LTE OMS16A
Support not required
NetAct NetAct 16.8
MME Support not required
SAE GW Support not required
Alarms Table 210
Existing alarms related to LTE2633
Alarm ID
7650
Alarm name
BASE STATION FAULTY
Commands There are no commands related to the LTE2633: System Upgrade to FDD-LTE 16A feature. Measurements and counters There are no measurements or counters related to the LTE2633: System Upgrade to FDD-LTE 16A feature. Key performance indicators There are no key performance indicators related to the LTE2633: System Upgrade to FDD-LTE 16A feature. Parameters There are no parameters related to the LTE2633: System Upgrade to FDD-LTE 16A feature. Sales information Table 211
LTE2633 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
5.15 LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules Benefits, functionality, system impact, reference data, instructions of the feature The LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules feature introduces the sending of an alarm in the base transceiver station (BTS) that is related to the high memory consumption on the radio frequency (RF) module.
5.15.1 LTE2816 benefits The LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules feature enables the BTS to inform the operator in advance that the radio module is running out of memory so the operator can apply mitigating actions.
276
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
5.15.2 LTE2816 functional description This feature introduces the sending of the alarm to the BTS that is related to the high memory consumption on the RF module. The RF module supports two thresholds: • •
Abnormal Critical
If the memory consumption exceeds the abnormal level, the BTS generates a new alarm with a minor severity. However, if the memory consumption exceeds the critical level, the BTS clears an abnormal alarm and generates the alarm with a major severity. The abnormal threshold is configurable and can be set by a new parameter that has a relative value. It has a range of 0% to 100%, and the default value is 50%. For the critical threshold, it is fixed and has a value of 100%. The abnormal and the critical thresholds can have the same value of 100% (as shown in the following figure), but if the threshold level of 100% is reached, only the alarm with the major severity is displayed. Figure 37
Radio module memory threshold level
L4 L3
Abnormalthreshold=100% (sameasthecriticalthreshold)
L2
Abnormalthreshold=0% (normalmemoryconsumption)
Memorysize
L1
Radiomemory The absolute abnormal and the critical memory thresholds depend on the RF module configuration. The feature is applicable for radio units with OBSAI/RP1 and CPRI/L3B protocols.
5.15.3 LTE2816 system impact LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules has no impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features
Issue: 01 Draft
DN09237915
277
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
There are no interdependencies between the LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules feature and any other feature. Impact on interfaces The LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules feature has no impact on interfaces. Impact on network management tools The LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules feature has no impact on network management tools. Impact on system performance and capacity The LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules feature has no impact on system performance or capacity.
5.15.4 LTE2816 reference data LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules requirements, alarms and faults, parameters, and sales information Requirements Table 212
LTE2816 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Support not required
Flexi Multiradio 10 BTS
AirScale FDD
FL16A
FL16A
UE
LTE OMS16A
Support not required
NetAct NetAct 16.8
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
Support not required
Support not required
Alarms There are no alarms related to the LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules feature. BTS faults and reported alarms Table 213 Fault ID
4329
4330
New BTS faults introduced by LTE2816 Fault name
Reported alarms Alarm ID
Alarm name
Radio memory consumption exceeds abnormal threshold
7652
BASE STATION NOTIFICATION
7655
CELL NOTIFICATION
Radio memory consumption exceeds critical threshold
7652
BASE STATION NOTIFICATION
7654
CELL OPERATION DEGRADED
For fault descriptions, see Flexi Multiradio BTS LTE Alarms and Faults. Commands
278
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
There are no commands related to the LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules feature. Measurements and counters There are no measurements or counters related to the LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules feature. Key performance indicators There are no key performance indicators related to the LTE2816: High Memory Consumption Alarm for Nokia RP1/L3B Radio Modules feature. Parameters Table 214
New parameters introduced by LTE2816 Full name
Abbreviated name
Managed object
radioMemAbnormalT RMOD hreshold
Radio memory abnormal threshold
Parent structure -
For parameter descriptions, see Flexi Multiradio BTS LTE Commissioning, RNW and Transmission Parameters. Sales information Table 215
LTE2816 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
5.16 LTE2828: LNCEL LNBTS Refactoring Benefits, functionality, system impact, reference data of the feature The LTE2828: LNCEL LNBTS Refactoring feature improves the usability of a managed object class (MOC). All of selected parameters from the LNCEL and LNBTS instances are moved to the new MOCs from the following areas: SIB, DRX, SDRX, ANR, and RIM.
5.16.1 LTE2828 benefits The LTE2828: LNCEL LNBTS Refactoring feature provides the following benefits: • •
It reduces the time spent on setting parameters by improving access to the parameters related to a selected functionality. It increases the usability of managed object classes (MOCs) by grouping parameters related to the same functionality.
5.16.2 LTE2828 functional description Functional description
Issue: 01 Draft
DN09237915
279
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
The LTE2828: LNCEL LNBTS Refactoring feature reduces the number of LNBTS and LNCEL parameters by moving groups of parameters to new MOCs. The scope of changes covers transfer of the following parameters: Table 216
LNBTS and LNCEL refactoring changes Before
After
SIB related parameters under LNCEL instance
SIB related parameters inside the new cell specific SIB instance
DRX related parameters under LNCEL instance
DRX related parameters insice the new cell specific DRX instance
Smart DRX related parameters under LNCEL instance
Smart DRX related parameters inside the new cell specific SDRX instance
ENB level ANR related parameters
ENB level ANR related parameters inside the new eNB specific ANR instance
RIM related parameters under LNBTS instance RIM related parameters inside the new eNB specific RIM instance
g
Note: All parameters will be automatically migrated to the new model with the same value during a release upgrade. Figure 1 New MOC in the LNBTS tree shows a new instance created for grouping transferred parameters according to their operating range. Changes in the LNCEL instance are shown in a similar way in Figure 2 New MOC in the LNCEL tree.
280
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Figure 38
Descriptions of operability features
New MOCs in the LNBTS tree
LNBTS
ANR CAGENB
ANRPRL CADPR
CSG
CTRLTS
GTPU
ISHPR
LAA
LNADJ
ANRPRW
ANRPRX
CRAN
CRGRP
LNDAJG
LNADJW
LBPUCCHRDPR
LNADJX LBPUCCHRPR LNCEL
LNCSG
LNHENB
LNMME
LNSENB
LNZ1*
MODPR
MOPR
PSGRP
RIM
ULCOMP
VMOD
MFBIPR PMRNL SCTP
LNMCE
-newMOCsrelatedtoLTE2828 -newMOCsintroducedinRL16A *
Issue: 01 Draft
- LNZ1isapplicable only toFZC
DN09237915
281
Descriptions of operability features
Figure 39
FDD-LTE16A, Feature Descriptions and Instructions
New MOCs in the LNCEL tree
LNCEL
AMLEPR
CAPR
DRX
APUCCH
CAREL
CDFIM
GFIM
IAFIM
IFGDPR
IFGPR
IRFIM
LNHOG
LNHOH
LNHOIF
LNHOW
LNHOX
LNNEIH
LNREL
LNRELG
LNRELW
LNRELX
MPUCHH REDRT
UFFIM
SDRX
SIB
VMOD
XPARAM
-newMOCsrelatedtoLTE2828 -newMOCsintroducedinRL16A
For list of moved mandator parameters, see Parameter section.
5.16.3 LTE2828 system impact LTE2828: LNCEL LNBTS Refactoring impact on features, interfaces, and network management tools. Interdependencies between features The LTE2828: LNCEL LNBTS Refactoring feature impacts the following features from the SIB area: •
LTE16A –
•
LTE16 –
282
LTE2562: ANR InterRat 1xRTT – O&M Assisted
LTE1709 Liquid Cell – TM9
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
– – – – – – – •
– – – –
– –
– –
LTE874: CSFB to CDMA/1xRTT for Dual RX UEs LTE1332: Downlink Carrier Aggregation – 40 MHz; Subset A LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB)
LTE50 – – – – – –
•
LTE1113: eICIC – Macro LTE1496: eICIC – Micro LTE1803: Downlink Carrier Aggregation 3CC – 40 MHz
LTE60 –
•
LTE738: SRVCC to 1xRTT/CDMA LTE1117: LTE MBMS LTE1788: Automatic Access Class Baring LTE1804: Downlink Carrier Aggregation 3CC – 60 MHz LTE2085: SIB Reception with Parallel Measurement Gaps
LTE70 –
•
LTE1858: FDD Inter-band/Intra-band Carrier Aggregation with Two Flexi Zone Micro BTSs LTE1891: eNodeB Power Saving – Micro DTX LTE1987: Downlink Adaptive Close Loop SU MIMO (4x4) LTE2351: S1-based Handover Towards CSG Cells LTE2370: Flexi Zone Inter-FZAP Carrier Aggregation LTE2465: CSG Cell Support LTE2505: Access Class Barring Skip
LTE15A –
•
Descriptions of operability features
LTE116: Cell Bandwidth – 3 MHz LTE117: Cell Bandwidth – 1.4 MHz LTE494: Commercial Mobile Alert System LTE495: OTDOA LTE807: Idle Mode Mobility LTE to CDMA/1xRTT LTE1036: RSR–based Cell Reselection
LTE10 –
LTE39: System Information Broadcast
The LTE2828: LNCEL LNBTS Refactoring feature impacts the following features from the DRX and SDRX areas: •
LTE16A –
•
LTE15A –
•
Issue: 01 Draft
LTE1130: Dynamic PUCCH Allocation
LTE1117: LTE MBMS
LTE70
DN09237915
283
Descriptions of operability features
– – – •
LTE1382: Cell Resource Groups
LTE50 – – – –
•
LTE1113: eICIC – Macro LTE1406: Extended VoLTE Talk Time LTE1496: eICIC – Micro
LTE60 –
•
FDD-LTE16A, Feature Descriptions and Instructions
LTE116: Cell Bandwidth – 3 MHz LTE117: Cell Bandwidth – 1.4 MHz LTE495: OTDOA LTE585: Smart DRX
LTE30 – –
LTE42: DRX in RRC Connected Mode LTE473: Extended DRX Settings
The LTE2828: LNCEL LNBTS Refactoring feature impacts the following features from the ANR and RIM areas: •
LTE15A – – –
•
LTE70 – –
•
– – –
–
LTE556: ANR Intra-LTE, Inter-frequency – UE-based LTE1383: Cell-specific Neighbour Relation/PCI handling
LTE40 –
•
LTE125: IPv6 for U/C-Plane LTE498: RAN Information Management for GSM LTE556: ANR Intra-LTE, Inter-frequency – UE-based LTE1708: Extend Maximum Number of X2 Links
LTE50 –
•
LTE908: ANR Inter-RAT UTRAN – Fully UE-based LTE1685: Neighbor Relation Robustness
LTE60 –
•
LTE1196: RAN Information Management for WCDMA LTE1996: Flexi Zone Controller Application LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness
LTE782: ANR Fully UE-based
LTE20 –
LTE492: ANR
Impact on interfaces The LTE2828: LNCEL LNBTS Refactoring feature impacts interfaces as follows:
284
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
BTS SM –
•
Descriptions of operability features
Modified object model
NetAct –
Modified object model
Impact on network management tools The LTE2828: LNCEL LNBTS Refactoring feature impacts network management tools as follows: •
BTS SM –
•
Modified object model
NetAct –
Modified object model
Impact on system performance and capacity The LTE2828: LNCEL LNBTS Refactoring feature has no impact on system performance or capacity.
5.16.4 LTE2828 reference data LTE2828: LNCEL LNBTS Refactoring requirements, parameters, and sales information Requirements Table 217 System release FDD-LTE16A Flexi Zone Controller FL16A
LTE2828 hardware and software requirements Flexi Multiradio BTS FL16A OMS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL16A
UE
LTE OMS 16A not applicable
NetAct NetAct 16.8
Flexi Zone Micro BTS FL16A MME support not required
Flexi Zone Access Point FL16A SAE GW support not required
Alarms There are no alarms related to the LTE2828: LNCEL LNBTS Refactoring feature. BTS faults and reported alarms There are no faults related to the LTE2828: LNCEL LNBTS Refactoring feature. Commands There are no commands related to the LTE2828: LNCEL LNBTS Refactoring feature. Measurements and counters There are no measurements or counters related to the LTE2828: LNCEL LNBTS Refactoring feature. Key performance indicators There are no key performance indicators related to the LTE2828: LNCEL LNBTS Refactoring feature.
Issue: 01 Draft
DN09237915
285
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
Parameters A new SIB MOC is subordinated to the LNCEL instance. After relocation, all the parameters keep their configured values. The several following parameters are relocated during refactoring the LNCEL instance, which means they are permanently removed from an old MO instance. Table 218
Existing mandatory parameters from SIB area related to LTE2828
Full name
Abbreviated name
Parent structure
SIB
-
Cell barred flag cellBarred
SIB
-
Minimum required qrxlevmin RX level in cell
SIB
-
Intra-frequency intrFrqCelRes cell reselection allowed
SIB
-
SI window length siWindowLen
SIB
-
System Information 2 Scheduling
sib2Scheduling
SIB
-
SIB type Message Mapping
siMessageSibType SIB
sib2Scheduling
SIB Type Periodicity
siMessagePeriodi SIB city
sib2Scheduling
SIB Type Repetition
siMessageRepetit SIB ion
sib2Scheduling
System Information 3 Scheduling
sib3Scheduling
SIB type Message Mapping
siMessageSibType SIB
sib3Scheduling
SIB Type Periodicity
siMessagePeriodi SIB city
sib3Scheduling
SIB Type Repetition
siMessageRepetit SIB ion
sib3Scheduling
Twofold transmission of SIBs per SI window
sib2xTransmit
SIB
-
SIB
-
Automatic AC Barring start timer
autoAcBarringSta SIB rtTimer
-
Automatic AC Barring stop timer
autoACBarringSto SIB pTimer
-
Cell reserved primPlmnCellres for operator use
286
Managed object
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 218
Existing mandatory parameters from SIB area related to LTE2828 (Cont.)
Full name
Abbreviated name
g
Managed object
Parent structure
Note: In RL16A, LTE2460 renames this parameter to autoAcbPlmn RmvlStopTim er
Modification period coefficient
modPeriodCoeff
SIB
-
Preamble transmission maximum
preambTxMax
SIB
-
Power ramping step
prachPwrRamp
SIB
-
Preamble initial ulpcIniPrePwr received target power
SIB
-
Timer T300
t300
SIB
-
Timer T301
t301
SIB
-
Timer T310
t310
SIB
-
Maximum number of out-of-sync indications
n310
SIB
-
Timer T311
t311
SIB
-
Maximum number of in-sync indications
n311
SIB
-
Skip Indicator for mobile originating MMTEL voice
acBarSkipForMMTE SIB LVoice
-
Skip Indicator for mobile originating MMTEL video
acBarSkipForMMTE SIB LVideo
-
Skip Indicator for mobile originating SMSoIP or SMS
acBarSkipForSMS
SIB
-
SIB
-
Cell reselection qHyst procedure hysteresis value
Issue: 01 Draft
Descriptions of operability features
DN09237915
287
Descriptions of operability features
Table 218
FDD-LTE16A, Feature Descriptions and Instructions
Existing mandatory parameters from SIB area related to LTE2828 (Cont.)
Full name
Abbreviated name
Managed object
Parent structure
Full Name Approved LNCEL tReselEutr Cell reselection timer
tReselEutr
SIB
-
Threshold serving low
threshSrvLow
SIB
-
Cell reselection cellReSelPrio priority
SIB
-
Min. required RX qrxlevminintraF level for intrafreq neighboring cells
SIB
-
Presence antenna intraPresAntP port1
SIB
-
A new DRX MOC is subordinated to the LNCEL instance. After relocation, all the parameters keep their configured values. The several following mandatory parameters are relocated during refactoring the LNCEL instance, which means they are permanently removed from old an MO instance. Table 219
Existing mandatory parameters from DRX area related to LTE2828
Full name
Managed object
Parent structure
DRX apply device drxApplyDeviceTy DRX type pe
-
DRX
-
Apply UL out-of- applyOutOfSyncSt DRX sync state ate
-
DRX on threshold qci1DrxOnThresho DRX for QCI1 ld
-
qci1DrxOffThresh DRX old
-
Short term inactivity factor
DRX off threshold for QCI1
Table 220
stInactFactor
Existing mandatory structures from DRX area related to LTE2828
Full name
288
Abbreviated name
Abbreviated name
Managed object
Parent structure
DRX profile 1
drxProfile1
DRX
-
DRX profile index
drxProfileIndex
DRX
drxProfile1
DRX profile priority
drxProfilePriori DRX ty
drxProfile1
DRX profile 2
drxProfile2
DN09237915
DRX
-
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 220
Existing mandatory structures from DRX area related to LTE2828 (Cont.)
Full name
g
Descriptions of operability features
Abbreviated name
Managed object
Parent structure
DRX profile 3
drxProfile3
DRX
-
DRX profile 4
drxProfile4
DRX
-
DRX profile 5
drxProfile5
DRX
-
DRX profile index
drxProfileIndex
DRX
drxProfileN
DRX profile priority
drxProfilePriori DRX ty
drxProfileN
DRX long cycle
drxLongCycle
DRX
drxProfileN
DRX on duration timer
drxOnDuratT
DRX
drxProfileN
DRX inactivity timer
drxInactivityT
DRX
drxProfileN
DRX retransmission timer
drxRetransT
DRX
drxProfileN
Note: The drxProfileN parameter describes a structure's profile number from 2 to 5 (for example, drxProfile2-drxProfileIndex). A new SDRX MOC is subordinated to the LNCEL instance. After relocation, all the parameters keep their configured values. The several following mandatory parameters are relocated during refactoring the LNCEL instance, which means they are permanently removed from an old MO instance. Table 221
Existing structures from SDRX area related to LTE2828
Full name
Issue: 01 Draft
Abbreviated name
Managed object
DRX smart profile n
drxSmartProfileN SDRX
DRX smart profile index
drxProfileIndex
Parent structure
-
SDRX
drxSmartProfileN
DRX smart drxProfilePriori SDRX profile priority ty
drxSmartProfileN
DRX long cycle
drxLongCycle
SDRX
drxSmartProfileN
DRX short cycle
drxShortCycle
SDRX
drxSmartProfileN
DRX short cycle timer
drxShortCycleT
SDRX
drxSmartProfileN
DRX on duration timer
drxOnDuratT
SDRX
drxSmartProfileN
DRX inactivity timer
drxInactivityT
SDRX
drxSmartProfileN
DN09237915
289
Descriptions of operability features
Table 221
FDD-LTE16A, Feature Descriptions and Instructions
Existing structures from SDRX area related to LTE2828 (Cont.)
Full name
Managed object
Parent structure
SDRX
drxSmartProfileN
Short term smartStInactFact SDRX inactivity or factor for smart DRX
drxSmartProfileN
DRX retransmission timer
g
Abbreviated name
drxRetransT
Note: The drxSmartProfileN parameter describes a structure's profile number from 2 to 5 (for example, drxSmartProfile2). A new RIM MOC is subordinated to the LNBTS instance. After relocation, all the parameters keep their configured values. The several following mandatory parameters are relocated during refactoring the LNBTS instance, which means they are permanently removed from an old MO instance. Table 222
Existing mandatory parameters from RIM area related to LTE2828
Full name
290
Abbreviated name
Managed object
Parent structure
Full Name Proposal LNBTS tRimRirG Timer to wait for RIR Response from GERAN
tRimRirG
RIM
-
Timer to wait for next RI PDU from GERAN
tRimKaG
RIM
-
Polling timer to tRimPollG ReStart RIR Procedure to GERAN
RIM
-
Maximum RIR attempts to GERAN
nRimRirG
RIM
-
Timer to wait tRimRirU for RIR response from UTRAN
RIM
-
Timer to wait for next RI PDU from UTRAN
RIM
-
Polling timer to tRimPollU ReStart RIR procedure to UTRAN
RIM
-
Max. RIR attempts to UTRAN
RIM
-
tRimKaU
nRimRirU
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
A new ANR MOC is subordinated to the LNBTS instance. After relocation, all the parameters keep their configured values. The several following mandatory parameters are relocated during refactoring the LNBTS instance, which means they are permanently removed from an old MO instance. Table 223
Existing mandatory parameters from ANR area related to LTE2828
Full name
Issue: 01 Draft
Abbreviated name
Managed object
Parent structure
Maximum number of eNBcontrolled outgoing X2links
maxNumX2LinksOut ANR
-
Maximum number of eNBcontrolled incoming X2links
maxNumX2LinksIn
ANR
-
ANR robustness level
anrRobLevel
ANR
-
Consecutive handover execution failure revalidation TH
consecHoFailThre ANR s
-
S1 periodical revalidation wait timer
s1PrdRevalWaitTm ANR r
-
X2 periodical revalidation wait timer
x2PrdRevalWaitTm ANR r
-
Idle time threshold for UTRAN neighbour relations
idleTimeThresUtr ANR anNR
-
Consecutive UTRAN HO execution failure revalidation TH
consecUtranHoFai ANR lThres
-
UTRAN periodical utranPrdRevalWai ANR revalidation tTmr wait timer
-
ANR Robustness Level for UTRAN
anrRobLevelUtran ANR
-
ANR interfrequency RSC timer
anrIfTRSC
ANR
-
DN09237915
291
Descriptions of operability features
Table 223
FDD-LTE16A, Feature Descriptions and Instructions
Existing mandatory parameters from ANR area related to LTE2828 (Cont.)
Full name
Abbreviated name
Managed object
Parent structure
Minimum not minNotActivatedU ANR activated UTRA traRSCFS reportStrongestC ellsForSon
-
ANR UTRA RSCFS timer
anrUtraTRSCFS
ANR
-
Activate autonomous removal of LTE neighbours
actAutoLteNeighR ANR emoval
-
Activate actAutoUtranNeig ANR autonomous hRemoval removal of UTRAN neighbours
-
Table 224
Existing mandatory structures from ANR area related to LTE2828
Full name
Abbreviated name
Managed object
Parent structure
ANR Idle Time Thresholds for LTE
anrIdleTimeThres ANR Lte
-
Idle Time Threshold for LTE Neighbour Relations
idleTimeThresLte ANR NR
anrIdleTimeThres Lte
ANR
anrIdleTimeThres Lte
Idle Time Threshold for Neighbour eNBs
idleTimeThresNbe ANR NB
anrIdleTimeThres Lte
Idle Time Threshold for Neighbour eNB Exchange
idleTimeThresNbE ANR nbExch
anrIdleTimeThres Lte
Neighbour eNB Exchange Wait Timer
nbEnbExchWaitTmr ANR
anrIdleTimeThres Lte
Idle Time idleTimeThresX2 Threshold for X2 links
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 225
292
LTE2828 sales information
Product structure class
License control
Activated by default
Basic Software (BSW)
-
Yes
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
5.17 LTE3043: Remote Power Port Control for FPFD PDU Benefits, functionality, system impact, reference data of the feature The LTE3043: Remote Power Port Control for FPFD PDU feature provides additional options in BTS Site Manager (BTS SM) for managing remotely the power ports feeding RF niodules. It enables selecting the power port to be switched on or off. The feature provides an option to use power reset functionality for maintenance purposes without site visits. Functionality will be used for recovery actions in cases where the radio unit has to be rebooted remotely. Additionally this feature enables operator to switch off the radio unit for a longer time to save energy used by this equipment.
5.17.1 LTE3043 benefits The LTE3043: Remote Power Port Control for FPFD PDU feature provides the following benefits: • •
Accelerates the removal of faults related to the lack of power supply at the PDU power port providing remote access for power control Reduces energy consumption due to easier management of PDU power ports via BTS Site Manager (BTS SM)
5.17.2 LTE3043 functional description Functional description The LTE3043: Remote Power Port Control for FPFD PDU feature will be mainly used for maintenance purposes. For instance, based on a received alarm, it is possible to temporarily switch off a PDU power port connected to a faulty RM or permanently switch off a radio module in order to reduce costs. So far, such actions have been performed manually on site, but the LTE3043: Remote Power Port Control for FPFD PDU feature enables executing them by means of BTS SM. Additionally it prevents excessive energy consumption by controlling power feeds to PDU power ports for example by switching off the power totally from the radio unit when required.
g
Note: A BTS reset switches on all PDU power ports connected to it, that have not been switched off from the front panel. If switched off from the front panel, then the power port remains switched off. Every PDU power port is configured separately. This makes it possible to decide which one should be switched off for a longer period of time for energy saving purposes. It is highly recommended to have knowledge of the relations between connected RM and PDU power ports since the LTE3043: Remote Power Port Control for FPFD PDU feature cannot determine the specific connection structure of any eNB. The decision to switch off the power feed can be made after checking what impact a switched-off RM has on cells. The list of impacted cells includes cells directly supported by the switched-off radio unit as well as cells which are supported by radio units further in the radio unit optical link chain. When the radio unit to be switched off is configured for RF sharing, it is necessary to consider the impact on cells of other RATs since these cells will be in a disabled state.
Issue: 01 Draft
DN09237915
293
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
The connection between an eNB and a PDU power port is checked by using the internal interface of serial communication protocol, see Figure 40: Connection flow with a PDU power port. Also it delivers information about state of the PDU power port and is used to control the power feed on it. Figure 40
Connection flow with a PDU power port
BTSSM XMLoverHTTP OAM
FSM-r3(SMOD)
PDU1
SerialCommunication Protocol PDU1
Managing Power Control in BTS SM BTS Site Manager, together with the LTE3043: Remote Power Port Control for FPFD PDU feature, detects power-distribution units and displays the available ones in a dialog window, based on the information in the siteconf file. The Power Control dialog window is accessible from the Configuration menu of BTS SM. In Figure 41: Example of Power Control dialog window in BTS SM, the statuses of available power lines for a PDU power port are marked with green and yellow icons. The following is a list of tools available for managing remote PDU power ports and their respective additional options: •
BTS Site Manager – – – –
•
NetAct – –
294
Allows switching on and off a PDU power port Presents the state of a PDU power port Presents the set of PDU power ports that can be controlled based on the BSF for the FSM (SMOD) Presents the current state of PDU power port alarms
Allows controlling the PDU power port via BTS SM Presents the current state of PDU power port alarms
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Figure 41
Descriptions of operability features
Example of Power Control dialog window in BTS SM
5.17.3 LTE3043 system impact LTE3043: Remote Power Port Control for FPFD PDU impact on network management tools, and system performance and capacity Interdependencies between features The LTE3043: Remote Power Port Control for FPFD PDU feature impacts the following features: • •
LTE1103: Load Based Power Saving for Multilayer Networks LTE1203: Load-based Power Saving with Tx Path Switching Off
The cells resources switched off by mentioned features can be switched on when other cells are switched off by the LTE3043: Remote Power Port Control for FPFD PDU feature. Any of impacted cells need to be lock first before switching off the PDU power port to indicate that the outage is planned. It means the Number of samples when the cell is planned unavailable (M8020C4) counter is increased instead of the
Number of samples when the cell is unplanned unavailable(M8020C5) counter. Impact on interfaces The LTE3043: Remote Power Port Control for FPFD PDU feature has no impact on interfaces. Impact on network management tools
Issue: 01 Draft
DN09237915
295
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
The LTE3043: Remote Power Port Control for FPFD PDU feature impacts network management tools as follows: •
BTS SM – –
•
Added control to a PDU power port Added view of the PDU power ports' status
NetAct –
Added view of the alarms related to the PDU power ports
Impact on system performance and capacity The LTE3043: Remote Power Port Control for FPFD PDU feature has no impact on system performance or capacity.
5.17.4 LTE3043 reference data LTE3043: Remote Power Port Control for FPFD PDU requirements, alarms and faults, and sales information Requirements Table 226
g
LTE3043 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FDD-LTE16A
not supported
FL16A
not applicable
not supported
not supported
Flexi Zone Controller
OMS
UE
NetAct
MME
SAE GW
not applicable
not applicable
not applicable
not applicable
not applicable
NetAct 16.8
Note: The LTE3043: Remote Power Port Control for FPFD PDU feature supports only ranio unit that has FPFD. Alarms Table 227
Existing alarms related to LTE3043
Alarm ID
7652
Alarm name
BASE STATION NOTIFICATION
For alarm descriptions, see LTE Radio Access Operating Documentation/Reference/Alarms and Faults. BTS faults and reported alarms
296
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 228
New BTS faults introduced by LTE3043
Fault ID
4107
Descriptions of operability features
Fault name
Reported alarms Alarm ID
EFaultId_RfPowerSwitchedOf fFromBtsSmAl
7652
Alarm name
BASE STATION NOTIFICATION
Power feeding for a given radio module has been switched off at the front panel.
4365
EFaultId_RfPowerSwitchedOf fFromFrontPanelAl Power on #smodLogicalId #pwrLineId line switched off at the front panel
g
Note: This fault is strictly related to Flexi Multiradio 10. For fault descriptions, see LTE Radio Access Operating Documentation/Reference/Alarms and Faults. Commands There are no commands related to the LTE3043: Remote Power Port Control for FPFD PDU feature. Measurements and counters There are no measurements or counters related to the LTE3043: Remote Power Port Control for FPFD PDU feature. Key performance indicators There are no key performance indicators related to the LTE3043: Remote Power Port Control for FPFD PDU feature. Parameters There are no parameters related to the LTE3043: Remote Power Port Control for FPFD PDU feature. Sales information Table 229
LTE3043 sales information
Product structure class
License control
Activated by default
Basic Software (BSW)
-
Yes
5.18 LTE3051: Eden-NET Replacing iSON as Centralized SON Solution The LTE3051: Eden-NET Replacing iSON as Centralized SON Solution feature introduces Eden-NET as a new platform for centralized SON.
Issue: 01 Draft
DN09237915
297
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
5.18.1 LTE3051 benefits The LTE3051: Eden-NET Replacing iSON as Centralized SON Solution feature provides the following benefits: The operator obtains new functions offered by Eden-NET while at the same time the functions of the legacy Optimizer/iSON manager are preserved.
5.18.2 LTE3051 functional description Overview Nokia Eden-NET is a leading centralized, multi-vendor, multi-technology SON solution. Eden-NET provides a wide range of SON modules in LTE, WCDMA, and GSM. The platform provides an open SON framework which enables the operator to build and deploy new customized SON modules on their own. Eden-NET provides a complete SON operating system as well as an established toolbox of essential SON modules. Furthermore, Eden-NET is highly extensible; it enables the operator to effectively customize the existing SON modules and create new ones. It provides a data adaptor functionality block, offering its services through a specific application programming interface (API) following a service-oriented architecture model. Eden Net as Centralized SON (cSON) Eden-NET works in a centralized architecture (commonly known as cSON). This allows access to a broader view of network configuration and performance. Eden-NET allows optimization benefits beyond those that can be achieved by distributed SON implementations. Eden-NET SON modules' overview The following is a list of the current and planned Eden-NET SON modules, categorized into four main areas: 1. Autonomous network optimization modules These modules substantially improve network performance and reliability through a dynamic optimization of RAN parameters. Updated parameters produced by these modules persist within the network until the parameters are updated manually. Additional runs of the modules for further optimization are updating the parameters as well. These modules run on a continual basis, determining new optimal settings as networks evolve. The following modules are part of the optimization: • • • • • •
Automatic neighbor relations (ANR) optimization PCI optimization Coverage and capacity optimization (CCO) Mobility robustness optimization (MRO) PRACH parameter optimization CA dynamic configuration
2. Dynamic network adaptation modules These modules improve network performance by dynamically re-configuring network elements to optimally serve the demands of active subscribers during periods of special conditions. The following modules automatically restore the baseline configuration once the condition subsides.
298
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• • •
Descriptions of operability features
Mobility load balancing (MLB) Special events Green networks (Energy Savings)
3. Workflow automation modules The follwing modules substantially improve operational efficiency, eliminate sources of manual error within the network, and help to ensure proper network operation by producing critical actionable reports as well as alerts for operators and automating configuration of network elements. • • • •
Automatic performance reports (includes worst performing cells) Real time alerts Parameter consistency enforcement Automatic site creation
4. Network reliability automation modules These modules substantially improve network reliability by dynamically detecting and responding to failures within the network. This includes the dynamic re-configuration of other network elements to compensate for the failure of a network element so that the network can provide optimal services during the period of such a failure. The following modules are concerned: • • • •
Sleeping cell detection and resolution Cell outage compensation Crossed antenna detection Alarm based outage resolution
Interaction between cSON tool and operator cSON provides an open-loop mode and a closed-loop mode: this applies generically to all cSON modules existing after execution, regardless of whether they are triggered manually or by a scheduler. See use cases in chapter Other instructions. Open-loop mode In the open-loop mode, the modules are running the algorithms, but no changes are applied to the network. The module output consists of a report that lists the proposed changes to improve network performance. In this mode, the modules retrieve configuration information from the Eden-NET internal configuration management cache, and not from the network. It does not force any reading from the OSS for data in the cache that has been modified or that has expired. The open-loop mode therefore places no additional load on the OSS and its interfaces. However, this also means that the data that the module processes in the open-loop mode may not be that which is present in the OSS or in the network elements at that time. To force a refresh of the Eden-NET internal configuration management cache, a 4G_Export module can be run on selected LTE cells for the IRAT neighbor relations managed objects. Eden-NET also enables real-time visualizations of the impact of SON actions. When a SON action is brought up in an alert, users are provided a visualization that portrays different states of network operation – the current state and the simulated state that would follow the proposed SON action.
Issue: 01 Draft
DN09237915
299
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
Closed-loop mode SON actions executed in the closed-loop mode are fully automated and run without operator intervention. As a precondition, the operator must define the scope and the parameters to control the algorithm. Once started by a scheduler or triggered manually by the operator, the module executes the following steps: • • •
cSON refreshes the cache of CM data; if relevant, also the PM data. cSON executes the algorithm. cSON exports the result as a plan to the Configurator and provisions automatically to the network
One principal goal of the closed-loop mode of operation in Eden-NET is to facilitate the workload in such a way that repetitive, time-consuming tasks are executed automatically. Some tasks that would be automated under closed-loop operation include the remote steering of antennas and the gathering of cell power profiles.
5.18.3 LTE3051 system impact Interdependencies between features Since FDD/TD-LTE 16A, Eden-NET replaces iSON as a centralized SON platform. The following features, which were previously supported by iSON or NetAct Optimizer, are supported by Eden-NET: RL10: • •
300
LTE720: SON LTE BTS Auto Configuration LTE468: PCI Management
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
g
Descriptions of operability features
Note: Differencies in Eden Net PCI collision or PCI confusion: only intra frequency are resolved not inter frequency. For example, there are three cells: – – – – –
Cell S has LNREL relation to A (S -> A). Cell S has LNREL relation to B (S -> B). Cell A and Cell B have the same PCI and same frequency. When S uses the same frequency as A and B (intra HO) the confusion will be resolved by PCI Optimization with Eden-Net. When S uses a different frequency as A and B (inter HO) the confusion will be not resolved by PCI Optimization with Eden-Net.
PCI collision resolution: only when there is a confusion. For example there are 2 cells: – – –
Cell A has a LNREL relation to B (A -> B) created by the operator. Cell A and Cell B have the same PCI and same frequency. That means there is a collision. This collision is not resolved by the operator.
Collision is only resolved when there is also a confusion: – – –
Cell S has LNREL relation to A (S -> A). Cell S has LNREL relation to B (S -> B). Cell A and Cell B have the same PCI.
With iSON it was not necessary that LNRELs are created. With iSON only the distance between the cells with same PCI and same frequency was considered. If the distance was smaller than a specified value the PCI conflict was resolved; if it was bigger it was not resolved.
RL20: •
g
LTE771: Optimization of Intra-LTE Neighbor Relations Note: Differencies in Eden Net Common trigger of blacklisting algorithm for all technologies (LTE771/LTE507). From the GUI there is no option to selectively trigger the blacklisting separetely for 4G, or for 3G or for 2G neighbors. The blacklisting is done for all technologies at the same time.
•
g
LTE783: ANR Inter-RAT UTRAN Note: Differencies in Eden Net The ANR algorithm is based also on KPI, not only on distance (LTE783/LTE784). For example the automatic configuration of inter-RAT neighbors is executed towards 2G/3G cells which are co-located with LTE sites whose LTE KPIs are sufficient.
RL30: • • •
Issue: 01 Draft
LTE784: ANR Inter-RAT GERAN LTE533: Mobility Robustness LTE581: PRACH Management
DN09237915
301
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
RL40: • •
LTE1019: SON Reports LTE1222: SON Automation Modes
RL50: •
g
LTE507: Inter-RAT Neighbor Relation Optimization (LTE, UTRAN, GERAN) Note: Differencies in Eden Net Common trigger of blacklisting algorithm for all technologies (LTE771/LTE507). From the GUI there is no option to selectively trigger the blacklisting separetely for 4G, or for 3G or for 2G neighbors. The blacklisting is done for all technologies at the same time.
• • •
LTE962: RACH Optimization LTE1367: Automatic Cell Combination Assignment for Carrier Aggregation LTE1383: Cell-specific Neighbor Relation / PCI Handling
RL60: •
LTE1332: Downlink Carrier Aggregation – 40 MHz
RL70: • • • • • • • •
LTE1685: Neighbor Relation Robustness LTE1768: MRO Ping Pong LTE1803: Downlink Carrier Aggregation 3 CC – 40 MHz LTE1821: Neighbor Detection Optimization for HetNet LTE1822: PCI Assignment Optimization for HetNet LTE1823: Neighbor Prioritization Optimization for HetNet LTE1951: Automatic Configuration Support for CA for Multi-carrier eNBs LTE2020: PRACH Management Optimization for HetNet
FDD-LTE15A: • • • • • • • • • • • • •
302
LTE1058: Plug & Play Extensions LTE1103: Load-based Power Saving for Multi-layer Networks LTE1117: LTE MBMS LTE1635: SIB 8 AC Barring for 1xRTT LTE1951: Automatic Configuration Support for CA for Multi-carrier eNBs LTE1804: Downlink Carrier Aggregation 3 CC – 60 MHz LTE1996: Flexi Zone Controller Application LTE2006: Flexible SCell Selection LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness LTE2149: Supplemental Downlink Carrier LTE2168: Additional Carrier Aggregation Band Combinations – II LTE2172: BTS Configurations Optimized for Distributed RRH Deployment LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
FDD-LTE16: • • • • • • • • • • • • • • • • •
LTE955: IPv6 for Management Plane LTE1203: Load-based Power Saving with Tx Path Switching Off LTE1462: Neighbor Optimization: Non-reachable Neighbors LTE1858: FDD Inter-band/Intra-band Carrier Aggregation with Two Flexi Zone Micro BTSs LTE1996: Flexi Zone Controller Application LTE1997: Discovery Mode Self Configuration for Flexi Zone AP LTE1998: Dynamic FZAP Plug & Play LTE2007: Inter-eNodeB Carrier Aggregation LTE2167: Additional Carrier Aggregation Band Combinations 3 CC – I LTE2180: FDD-TDD Downlink Carrier Aggregation 2 CC LTE2205: Configurable Uplink Interference Regions LTE2233: N-out-of-M Downlink Carrier Aggregation LTE2270: LTE TDD+FDD Inter-eNB CA Basic BTS Configurations LTE2316: FDD-TDD Downlink Carrier Aggregation 3CC LTE2370: Flexi Zone Inter-FZAP Carrier Aggregation LTE2465: CSG Cell Support LTE2539: MRO Inter-RAT UTRAN
The following features are not supported by Eden-NET: • •
•
RL10: LTE539: Central ANR RL20: LTE492: ANR - eNB functionality remains unchanged, but the PCI-IP address map is not generated automatically. The operator needs to provide the map manually or with some external tooling. RL70: LTE1808: Automatic PUCCH Capacity Optimization
The following LTE16A features consider Eden-NET as a cSON platform and will not be supported in the iSON Manager: • • • • • •
LTE1092: Uplink Carrier Aggregation – 2 CC LTE2531: FDD Downlink Carrier Aggregation – 4 CC/5 CC LTE2564: Centralized RAN CL16A Release LTE2557: Supplemental Downlink Carrier Extensions LTE2605: 4RX diversity 20 MHz Optimized Configurations LTE2633: System Upgrade to FDD-LTE 16A
Impact on interfaces The LTE3051: Eden-NET replacing iSON as centralized SON solution feature has no impact on interfaces. Impact on network management tools The LTE3051: Eden-NET replacing iSON as centralized SON solution feature has no impact on network management tools. Impact on system performance and capacity The LTE3051: Eden-NET replacing iSON as centralized SON solution feature has no impact on system performance or capacity.
Issue: 01 Draft
DN09237915
303
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
5.18.4 LTE3051 reference data Requirements Table 230
LTE3051 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS not applicable
FDD-LTE 16A
not applicable
not applicable
Flexi Zone Controller
OMS
UE
not applicable
not applicable
not applicable
Flexi Zone Micro BTS not applicable
NetAct NetAct 16.8
Flexi Zone Access Point not applicable
MME
SAE GW
not applicable
not applicable
Sales information Table 231
LTE3051 sales information
Product structure class
License control
Application software (ASW) NetAct
-
Activated by default No
5.18.5 Other instructions Generic operator use cases and the interoperability with the Configurator describe how cSON handles the interaction with the operator in order to trigger the SON algorithms and how cSON interworks with NetAct Configurator. Example: Use case: execution of a cSON module in an open-loop mode, triggered manually Example: Use case: execution of a cSON module in an open-loop mode, triggered by the scheduler Precondition • • • •
NetAct Configurator and cSON are up and running. The corresponding module of cSON is available and licensed. The periodical refresh of the CM cache is running. The periodical refresh of the PM data is running.
Description 1. The operator selects the cells or an operator-defined set of cells (cluster) that shall be optimized. 2. The operator sets the parameters to control the SON module. For example in carrier aggregation: • • •
304
frequency layers to aggregate the number of cells to aggregate in PCI Management: forbidden PCI, re-use distance, etc.
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of operability features
3. a) Manually triggered: the operator runs the cSON module in an open-loop mode. b) Scheduler triggered: the operator defines the time/schedule for cSON to trigger the module in an open-loop mode. 4. cSON runs the module, either immediately or as scheduled: •
cSON evaluates the data and generates a report that lists the proposed changes. This report cannot be activated in the network automatically.
Post-condition cSON presents a report file with the modifications proposed by the module. Example: Use case: execution of a cSON module in a closed-loop mode, triggered manually Example: Use case: execution of a cSON Module in a closed-loop mode, triggered by the scheduler Precondition • • • •
NetAct Configurator and cSON are up and running. The corresponding module of cSON is available and licensed. The periodical refresh of the CM cache is running. The periodical refresh of PM data is running.
Description 1. The operator selects the cells or an operator-defined set of cells (cluster) that shall be optimized. 2. The operator sets the parameters to control the SON module. For example in carrier aggregation: • • •
3.
frequency layers to aggregate the number of cells to aggregate in PCI Management: forbidden PCI, re-use distance, etc.
a) Manually triggered: the operator runs the cSON module in a closed-loop mode. b) Scheduler triggered: the operator defines the time/schedule for cSON to trigger the module in a closed-loop mode.
4. cSON runs the module, either immediately or as scheduled: •
• •
cSON evaluates the data and generates a RAML file that contains the changes (only changes, not non-changes). cSON provides context information according to LTE1019: SON Report to indicate the origin of the change in the Configurator's CM history. cSON transfers the result to the Configurator. cSON initiates to validate, download, and activate the results in the network.
Post-condition • •
Issue: 01 Draft
cSON presents a log file with the modifications proposed by the module. The latest refreshed configuration of the network is optimized, and the network is configured according to the results of cSON.
DN09237915
305
Descriptions of operability features
FDD-LTE16A, Feature Descriptions and Instructions
Example: Use case: Interactive, tool-assisted planning Precondition • • •
NetAct Configurator and cSON are up and running. The corresponding module of cSON is available and licensed. The periodical refresh of the CM cache is running.
Description 1. The operator selects the cell or an operator-defined set of cells (cluster) that shall be optimized. 2. The operator sets the parameters to control the SON module. For example in carrier aggregation: • • •
frequency layers to aggregate the number of cells to aggregate in PCI Management: forbidden PCI, re-use distance, etc.
3. 4. 5. 6.
The operator runs the cSON module in an open-loop mode. cSON runs the algorithm and provides proposed optimizations in a log file. The operator uses the log file and the map view to inspect the results. In case the result is not as expected and parameters need tuning, the operator goes back to (2.); otherwise, the operator continues to the next step. 7. Optional: In case the result is as expected, the operator triggers, either manually or by using the scheduler, the cSON module in a closed-loop mode to download and activate the changes in the network. cSON provides context information according to LTE1019: SON Report to indicate the origin of the change in the Configurator's CM history Post-condition cSON presents a report with the modifications proposed by the module.
306
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of performance monitoring features
6 Descriptions of performance monitoring features 6.1 LTE2140: New Performance Counters LTE16A The LTE2140: New Performance Counters LTE16A feature introduces new counters which improve performance monitoring capabilities in areas such as multiple inputs multiple outputs (MIMO), carrier aggregation (CA), quality of service (QoS), and voice over LTE (VoLTE).
6.1.1 LTE2140 benefits The LTE2140: New Performance Counters LTE16A feature provides the following benefits: •
improved performance monitoring capabilities, especially in areas such as MIMO, CA, or VoLTE
6.1.2 LTE2140 functional description The LTE2140: New Performance Counters LTE16A feature improves performance monitoring in the following areas: MIMO •
MIMO rank indication attemps
Carrier aggregation (CA) •
the maximum number of users with a configured/activated second cell (SCell) or third CA cell
QoS class identifier (QCI) •
QCI2 bearers release per cause
Voice over LTE (VoLTE) • •
inter-system handover preparation attempts with single radio voice call continuity (SRVCC) to UTRAN and GERAN failed inter-system handover preparation attempts with SRVCC to UTRAN and GERAN per cause
Terminal capabilities • •
terminal-type distribution in cells for appropriate network configuration and planning UE distribution with regard to feature support and such capabilities as CA UL, CoMP UL, inter-frequency ANR, inter-RAT ANR, access stratum RL., CA bandwidth A–F.
Inter-frequency load balancing •
handover preparation failures due to admission control (AC) or not supported QCI
Exemples of features where LTE2140's counters might be activated
Issue: 01 Draft
DN09237915
307
Descriptions of performance monitoring features
• • • • • • • • • • •
FDD-LTE16A, Feature Descriptions and Instructions
LTE1092: Uplink Carrier Aggregation – 2CC LTE2416: TDD Uplink 2CC Carrier Aggregation Extension LTE2493: Enhanced VoLTE Performance Monitoring LTE2511: Additional FDD-TDD Carrier Aggregation Band Combinations – I LTE2527: Additional Carrier Aggregation Band Combinations – IV LTE2528: Extension of Downlink 3CC Carrier Aggregation – II LTE2531: FDD Downlink Carrier Aggregation 4CC/5CC LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO LTE2611: Introduction of Public-safety-specific QCI Bearers LTE2766: Flexible QCI/ARP PM Counter Profiles LTE2782: RRC Reestablishment and RLF PM Counters per QCI Profile
6.1.3 LTE2140 system impact Interdependencies between features There are no interdependencies between the LTE2140: New Performance Counters LTE16A feature and any other feature. Impact on interfaces The LTE2140: New Performance Counters LTE16A feature has no impact on interfaces. Impact on network management tools The LTE2140: New Performance Counters LTE16A feature has no impact on network management tools. Impact on system performance and capacity The LTE2140: New Performance Counters LTE16A feature has no impact on system performance or capacity.
6.1.4 LTE2140 reference data Requirements Table 232
LTE2140 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
Multiradio S4
FL16A
FL16A
UE
LTE OMS16A
support not required
Flexi Zone Micro BTS FL16A
NetAct
MME
NetAct 16.8
support not required
Flexi Zone Access Point FL16A SAE GW support not required
Measurements and counters Table 233
308
New counters introduced by the LTE2140: New Performance Counters LTE 16A feature
Counter ID
Counter name
M8006C282
EPC initiated QCI2 E-RAB releases due to Path Switch
LTE EPS Bearer
M8006C283
eNB initiated QCI2 E-RAB releases due to a failed Handover Completion phase at target cell
LTE EPS Bearer
DN09237915
Measurement
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 233 Counter ID
Issue: 01 Draft
Descriptions of performance monitoring features
New counters introduced by the LTE2140: New Performance Counters LTE 16A feature (Cont.) Counter name
Measurement
M8006C284
Total number of released QCI2 E-RABs initiated by the eNB
LTE EPS Bearer
M8006C285
eNB initiated QCI2 E-RAB releases due to user inactivity
LTE EPS Bearer
M8006C286
eNB initiated QCI2 E-RAB releases due to loss of connection to the UE
LTE EPS Bearer
M8006C287
eNB initiated QCI2 E-RAB releases due to insufficient transport resources
LTE EPS Bearer
M8006C288
eNB initiated QCI2 E-RAB releases due to redirect to another cell
LTE EPS Bearer
M8006C289
eNB initiated QCI2 E-RAB releases due to E-UTRAN Generated Reason
LTE EPS Bearer
M8006C290
eNB initiated QCI2 E-RAB releases due to "Radio Network Layer Cause - Radio resources not available"
LTE EPS Bearer
M8006C291
QCI2 E-RABs released due to partial Handover
LTE EPS Bearer
M8006C292
QCI2 E-RABs attempted to release due to outgoing Handover
LTE EPS Bearer
M8006C293
QCI2 E-RABs released due to successful outgoing Handover
LTE EPS Bearer
M8006C294
QCI2 E-RABs released due to failed Handover
LTE EPS Bearer
M8006C295
EPC initiated EPS Bearer Release requests per QCI2 due to Radio Network Layer cause
LTE EPS Bearer
M8006C296
EPC initiated EPS Bearer Release requests for QCI2 due to Other causes
LTE EPS Bearer
M8006C297
EPC initiated EPS Bearer Release LTE EPS Bearer requests for QCI2 due to Normal release by UE
M8006C298
EPC initiated EPS Bearer Release LTE EPS Bearer requests for QCI2 due to Detach procedure by UE or MME
M8010C115
UE reported RI 3
M8014C41
Failed Inter-eNB X2 Handover preparations LTE Inter eNB Handover due to not supported QCI
M8014C42
Failed Inter-eNB S1 Handover preparations LTE Inter eNB Handover due to not supported QCI
M8014C43
Failed Inter-eNB S1 Handover preparations LTE Inter eNB Handover to CSG cell due to not supported QCI
M8014C44
Failed Inter-eNB X2 Load Balancing Handover preparations due to target admission control
DN09237915
LTE Power and Quality DL
LTE Inter eNB Handover
309
Descriptions of performance monitoring features
Table 233 Counter ID
310
FDD-LTE16A, Feature Descriptions and Instructions
New counters introduced by the LTE2140: New Performance Counters LTE 16A feature (Cont.) Counter name
Measurement
M8014C45
Failed Inter-eNB S1 Load Balancing Handover preparations due to target admission control
LTE Inter eNB Handover
M8015C23
Failed Inter-eNB Handover preparations per neighbor cell relationship due to not supported QCI
LTE Neighbor cell related Handover
M8016C50
Inter-System Handovers preparations to UTRAN with SRVCC
LTE Inter System Handover
M8016C51
Failed Inter-System Handover preparations LTE Inter System Handover to UTRAN with SRVCC due to timer
M8016C52
Failed Inter-System Handover preparations LTE Inter System Handover to UTRAN with SRVCC due to target eNB admission control
M8016C53
Failed Inter-System Handover preparations LTE Inter System Handover to UTRAN with SRVCC caused by other reasons
M8016C54
Inter-System Handover preparations to GERAN with SRVCC
M8016C55
Failed Inter-System Handover preparations LTE Inter System Handover to GERAN with SRVCC due to timer
M8016C56
Failed Inter-System Handover preparations LTE Inter System Handover to GERAN with SRVCC due to target eNB admission control
M8016C57
Failed Inter-System Handover preparations LTE Inter System Handover to GERAN with SRVCC caused by other reasons
M8042C0
Failed Inter-eNB S1 Handover preparations LTE Inter Home eNB Handover to Home eNB due to not supported QCI
M8051C23
Maximum number of DL carrier aggregated LTE UE Quantity capable UEs for 2 CCs.
M8051C24
Maximum number of DL carrier aggregated LTE UE Quantity capable UEs for 3 CCs
M8051C25
Maximum number of UEs with one configured SCell
LTE UE Quantity
M8051C26
Maximum number of UEs with two configured SCells
LTE UE Quantity
M8051C27
Maximum number of UEs with one activated SCell
LTE UE Quantity
M8051C28
Maximum number of UEs with two activated SCells
LTE UE Quantity
M8051C29
Maximum number of UEs with three activated SCells
LTE UE Quantity
M8051C30
Maximum number of UEs with four activated SCells
LTE UE Quantity
M8051C39
Average number of active UEs with UE Category 9
LTE UE Quantity
DN09237915
LTE Inter System Handover
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 233 Counter ID
Issue: 01 Draft
Descriptions of performance monitoring features
New counters introduced by the LTE2140: New Performance Counters LTE 16A feature (Cont.) Counter name
Measurement
M8051C40
Average number of active UEs with UE Category 10
LTE UE Quantity
M8051C41
Maximum number of active UEs with UE Category 1
LTE UE Quantity
M8051C42
Maximum number of active UEs with UE Category 2
LTE UE Quantity
M8051C43
Maximum number of active UEs with UE Category 3
LTE UE Quantity
M8051C44
Maximum number of active UEs with UE Category 4
LTE UE Quantity
M8051C45
Maximum number of active UEs with UE Category 5
LTE UE Quantity
M8051C46
Maximum number of active UEs with UE Category 6
LTE UE Quantity
M8051C47
Maximum number of active UEs with UE Category 7
LTE UE Quantity
M8051C48
Maximum number of active UEs with UE Category 8
LTE UE Quantity
M8051C49
Maximum number of active UEs with UE Category 9
LTE UE Quantity
M8051C50
Maximum number of active UEs with UE Category 10
LTE UE Quantity
M8051C51
Maximum number of active UEs with UE Category 11
LTE UE Quantity
M8051C52
Maximum number of active UEs with UE Category 12
LTE UE Quantity
M8051C64
Average number of UEs supporting Interfrequency ANR
LTE UE Quantity
M8051C65
Average number of UEs supporting InterRAT ANR
LTE UE Quantity
M8051C66
Average number of UEs supporting Rel-10 Access Stratum Release
LTE UE Quantity
M8051C67
Average number of UEs supporting Rel-11 Access Stratum Release
LTE UE Quantity
M8051C68
Average number of UEs supporting Rel-12 Access Stratum Release
LTE UE Quantity
M8051C69
Average number of UEs supporting Rel-8 Access Stratum Release
LTE UE Quantity
M8051C70
Average number of UEs supporting Rel-9 Access Stratum Release
LTE UE Quantity
M8051C71
Average number of UEs supporting UL CA
LTE UE Quantity
M8051C72
Average number of UEs supporting UL CoMP
LTE UE Quantity
DN09237915
311
Descriptions of performance monitoring features
Table 233 Counter ID
312
FDD-LTE16A, Feature Descriptions and Instructions
New counters introduced by the LTE2140: New Performance Counters LTE 16A feature (Cont.) Counter name
Measurement
M8051C73
Average number of UEs with CA bandwidth LTE UE Quantity class A
M8051C74
Average number of UEs with CA bandwidth LTE UE Quantity class B
M8051C75
Average number of UEs with CA bandwidth LTE UE Quantity class C
M8051C76
Average number of UEs with CA bandwidth LTE UE Quantity class D
M8051C77
Average number of UEs with CA bandwidth LTE UE Quantity class E
M8051C78
Average number of UEs with CA bandwidth LTE UE Quantity class F
M8051C79
Maximum number of UEs supporting Interfrequency ANR
LTE UE Quantity
M8051C80
Maximum number of UEs supporting InterRAT ANR
LTE UE Quantity
M8051C81
Maximum number of UEs supporting Rel10 Access Stratum Release
LTE UE Quantity
M8051C82
Maximum number of UEs supporting Rel11 Access Stratum Release
LTE UE Quantity
M8051C83
Maximum number of UEs supporting Rel12 Access Stratum Release
LTE UE Quantity
M8051C84
Maximum number of UEs supporting Rel-8 Access Stratum Release
LTE UE Quantity
M8051C85
Maximum number of UEs supporting Rel-9 Access Stratum Release
LTE UE Quantity
M8051C86
Maximum number of UEs supporting UL CA
LTE UE Quantity
M8051C87
Maximum number of UEs supporting UL CoMP
LTE UE Quantity
M8051C88
Maximum number of UEs with CA bandwidth class A
LTE UE Quantity
M8051C89
Maximum number of UEs with CA bandwidth class B
LTE UE Quantity
M8051C90
Maximum number of UEs with CA bandwidth class C
LTE UE Quantity
M8051C91
Maximum number of UEs with CA bandwidth class D
LTE UE Quantity
M8051C92
Maximum number of UEs with CA bandwidth class E
LTE UE Quantity
M8051C93
Maximum number of UEs with CA bandwidth class F
LTE UE Quantity
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
g
Note: Counters presented in Table 4 are existing counters moved from M8001 to M8051 measurement type LTE UE quantity. For more information see RISE. Table 234 Counter ID
Issue: 01 Draft
Descriptions of performance monitoring features
Existing counters realted to the LTE2140: New Performance Counters LTE 16A feature Counter name
Measurement
M8051C31
Average number of active UEs with UE Category 1
LTE UE Quantity
M8051C32
Average number of active UEs with UE Category 2
LTE UE Quantity
M8051C33
Average number of active UEs with UE Category 3
LTE UE Quantity
M8051C34
Average number of active UEs with UE Category 4
LTE UE Quantity
M8051C35
Average number of active UEs with UE Category 5
LTE UE Quantity
M8051C36
Average number of active UEs with UE Category 6
LTE UE Quantity
M8051C37
Average number of active UEs with UE Category 7
LTE UE Quantity
M8051C38
Average number of active UEs with UE Category 8
LTE UE Quantity
M8051C53
Average number of CA UE with one configured UL Scell
LTE UE Quantity
M8051C54
Average Number of UL carrier aggregated capable UEs for 2CCs
LTE UE Quantity
M8051C55
RRC Connected UEs Avg
LTE UE Quantity
M8051C56
RRC Connected UEs Max
LTE UE Quantity
M8051C57
Active UE per Cell average
LTE UE Quantity
M8051C58
Active UE per Cell max
LTE UE Quantity
M8051C59
Average number of active UEs with UE supporting TM9 and 4 layers transmission simultaneously
LTE UE Quantity
M8051C60
Sum of RRC Connected UEs per cell
LTE UE Quantity
M8051C61
Denominator for RRC Connected UEs per cell
LTE UE Quantity
M8051C62
Sum of Active UEs per cell
LTE UE Quantity
M8051C63
Denominator for Active UEs per cell
LTE UE Quantity
M8051C96
Average number of paired UEs per TTI in UL MU-MIMO mode.
LTE UE Quantity
M8051C97
UEs with buffered UL data for DRB with QCI 1
LTE UE Quantity
M8051C98
UEs with buffered UL data for non-GBR DRB
LTE UE Quantity
M8051C99
Sum of Active UEs with buffered data in UL LTE UE Quantity per cell
DN09237915
313
Descriptions of performance monitoring features
Table 234 Counter ID
314
FDD-LTE16A, Feature Descriptions and Instructions
Existing counters realted to the LTE2140: New Performance Counters LTE 16A feature (Cont.) Counter name
Measurement
M8051C100
Denominator for Active UEs with buffered data in UL per cell
M8051C101
Sum of Active UEs with buffered data in DL LTE UE Quantity per cell
M8051C102
Denominator for Active UEs with buffered data in DL per cell
LTE UE Quantity
M8051C103
Sum of active UEs per cell, which had data scheduled in UL.
LTE UE Quantity
M8051C104
Denominator for active UEs per cell, which had data scheduled in UL.
LTE UE Quantity
M8051C105
Sum of active UEs per cell, which had data scheduled in DL.
LTE UE Quantity
M8051C106
Denominator for active UEs per cell, which had data scheduled in DL.
LTE UE Quantity
M8051C107
Average number of UEs with buffered data in DL
LTE UE Quantity
M8051C108
Max number of UEs with buffered data in DL
LTE UE Quantity
M8051C109
Average number of UEs with buffered data in UL
LTE UE Quantity
M8051C110
Max number of UEs with buffered data in UL
LTE UE Quantity
M8051C111
UEs with buffered DL data for DRB with QCI 1
LTE UE Quantity
M8051C112
UEs with buffered DL data for QCI2 bearer
LTE UE Quantity
M8051C113
UEs with buffered DL data for QCI3 bearer
LTE UE Quantity
M8051C114
UEs with buffered DL data for QCI4 bearer
LTE UE Quantity
M8051C115
UEs with buffered DL data for non-GBR DRB
LTE UE Quantity
M8051C116
Average number of UEs with one activated SCell
LTE UE Quantity
M8051C117
Average number of UEs with two activated SCells
LTE UE Quantity
M8051C118
Average number of UL CA UE with one activated Scell
LTE UE Quantity
M8051C119
Average number of UEs using UL intraeNB CoMP
LTE UE Quantity
M8051C120
Average number of UEs considered by L3 RRM for UL intra-eNB CoMP
LTE UE Quantity
M8051C121
Average number of DL carrier aggregated capable UEs for 2 CCs
LTE UE Quantity
M8051C122
Average number of DL carrier aggregated capable UEs for 3 CCs
LTE UE Quantity
DN09237915
LTE UE Quantity
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 234
Descriptions of performance monitoring features
Existing counters realted to the LTE2140: New Performance Counters LTE 16A feature (Cont.)
Counter ID
Counter name
Measurement
M8051C123
Average number of UEs with one configured SCell
LTE UE Quantity
M8051C124
Average number of UEs with two configured SCells
LTE UE Quantity
For counter descriptions, see LTE Radio Access Operating Documentation/Reference/Counters. Parameters There are no parameters related to the LTE2140: New Performance Counters LTE 16A feature. Sales information Table 235
LTE2140 sales information
Product structure class
License control
Basic Software (BSW)
-
Activated by default Yes
6.2 LTE2493: Enhanced VoLTE Performance Monitoring The LTE2493: Enhanced VoLTE Performance Monitoring feature introduces new counters for monitoring quality of service (QoS) for voice over LTE (VoLTE).
6.2.1 LTE2493 benefits The LTE2493: Enhanced VoLTE Performance Monitoring feature provides the following benefit: •
Deeper insight into the VoLTE performance
6.2.2 LTE2493 functional description The LTE2493: Enhanced VoLTE Performance Monitoring feature enables collecting information about voice over LTE's (VoLTE) performance. VoLTE BLER distribution BLER is a ratio of the number of erroneous transport blocks to the total number of transport blocks. BLER distributions, separately for DL and UL, might be portrayed on an 11-bin histogram as follows: Bin1: 0 <= Residual BLER Rate <= 0.5 Bin2: 0.5 < Residual BLER Rate <= 1 Bin3: 1 < Residual BLER Rate <= 1.5 Bin4: 1.5 < Residual BLER Rate <= 2
Issue: 01 Draft
DN09237915
315
Descriptions of performance monitoring features
FDD-LTE16A, Feature Descriptions and Instructions
Bin5: 2 < Residual BLER Rate <= 2.5 Bin6: 2.5 < Residual BLER Rate <= 3 Bin7: 3 < Residual BLER Rate <= 3.5 Bin8: 3.5 < Residual BLER Rate <= 4 Bin9: 4 < Residual BLER Rate <= 4.5 Bin10: 4.5 < Residual BLER Rate <= 5 Bin11: 5 < Residual BLER Rate
g
Note: The sampling period for histogram counters is 10240 ms, for which at least 200 HARQ transmissions are performed in order to obtain reliable values of BLER samples in the standard loaded cells. The residual BLER is a BLER after maximum number of HARQ transmissions
6.2.3 LTE2493 system impact Interdependencies between features There are no interdependencies between the LTE2493: Enhanced VoLTE Performance Monitoring feature and any other feature. Impact on interfaces The LTE2493: Enhanced VoLTE Performance Monitoring feature has no impact on interfaces. Impact on network management tools The LTE2493: Enhanced VoLTE Performance Monitoring feature has no impact on network management tools. Impact on system performance and capacity The LTE2493: Enhanced VoLTE Performance Monitoring feature has no impact on system performance or capacity.
6.2.4 LTE2493 reference data Requirements Table 236
LTE2493 hardware and software requirements
System release
Flexi Multiradio 10 BTS
Flexi Multiradio 10 Indoor BTS
FDD-LTE 16A
not supported
FL16A
Flexi Zone Controller
OMS
FL16A
UE
LTE OMS16A
support not required
AirScale
FL16A NetAct NetAct 16.8
Flexi Zone Micro BTS FL16A MME support not required
Flexi Zone Access Point FL16A SAE GW support not required
BTS faults and reported alarms There are no faults and alarms related to the LTE2493: Enhanced VoLTE Performance Monitoring feature. Commands There are no commands related to the LTE2493: Enhanced VoLTE Performance Monitoring feature.
316
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of performance monitoring features
Measurements and counters Table 237
New counters introduced by LTE2493
Counter ID
Issue: 01 Draft
Counter name
Measurement
M8026C264
PDCP SDUs QCI1 (VoLTE) received within preconfigured delay in DL
LTE QoS
M8026C265
QCI1 (VoLTE) UEs in good conditions in DL
LTE QoS
M8026C266
QCI1 (VoLTE) UEs in bad conditions in DL
LTE QoS
M8026C267
Number of failed TB transmissions after max HARQ count for QCI1(VoLTE) in DL
LTE QoS
M8026C268
Total number of initial HARQ transmissions for LTE QoS QCI1(VoLTE) in DL
M8026C269
Number of failed TB transmissions after max HARQ count for QCI1(VoLTE) in UL
M8026C270
Total number of initial HARQ transmissions for LTE QoS QCI1(VoLTE) in UL
M8026C272
Average UL Grant after SR reception delay for LTE QoS QCI1 UEs
M8054C0
Downlink QCI1 (VoLTE) Residual BLER Bin1
LTE VoLTE BLER Histogram
M8054C1
Downlink QCI1 (VoLTE) Residual BLER Bin2
LTE VoLTE BLER Histogram
M8054C2
Downlink QCI1 (VoLTE) Residual BLER Bin3
LTE VoLTE BLER Histogram
M8054C3
Downlink QCI1 (VoLTE) Residual BLER Bin4
LTE VoLTE BLER Histogram
M8054C4
Downlink QCI1 (VoLTE) Residual BLER Bin5
LTE VoLTE BLER Histogram
M8054C5
Downlink QCI1 (VoLTE) Residual BLER Bin6
LTE VoLTE BLER Histogram
M8054C6
Downlink QCI1 (VoLTE) Residual BLER Bin7
LTE VoLTE BLER Histogram
M8054C7
Downlink QCI1 (VoLTE) Residual BLER Bin8
LTE VoLTE BLER Histogram
M8054C8
Downlink QCI1 (VoLTE) Residual BLER Bin9
LTE VoLTE BLER Histogram
M8054C9
Downlink QCI1 (VoLTE) Residual BLER Bin10 LTE VoLTE BLER Histogram
M8054C10
Downlink QCI1 (VoLTE) Residual BLER Bin11
LTE VoLTE BLER Histogram
M8054C11
Uplink QCI1 (VoLTE) Residual BLER Bin1
LTE VoLTE BLER Histogram
M8054C12
Uplink QCI1 (VoLTE) Residual BLER Bin2
LTE VoLTE BLER Histogram
M8054C13
Uplink QCI1 (VoLTE) Residual BLER Bin3
LTE VoLTE BLER Histogram
DN09237915
LTE QoS
317
Descriptions of performance monitoring features
Table 237
FDD-LTE16A, Feature Descriptions and Instructions
New counters introduced by LTE2493 (Cont.)
Counter ID
g
Counter name
Measurement
M8054C14
Uplink QCI1 (VoLTE) Residual BLER Bin4
LTE VoLTE BLER Histogram
M8054C15
Uplink QCI1 (VoLTE) Residual BLER Bin5
LTE VoLTE BLER Histogram
M8054C16
Uplink QCI1 (VoLTE) Residual BLER Bin6
LTE VoLTE BLER Histogram
M8054C17
Uplink QCI1 (VoLTE) Residual BLER Bin7
LTE VoLTE BLER Histogram
M8054C18
Uplink QCI1 (VoLTE) Residual BLER Bin8
LTE VoLTE BLER Histogram
M8054C19
Uplink QCI1 (VoLTE) Residual BLER Bin9
LTE VoLTE BLER Histogram
M8054C20
Uplink QCI1 (VoLTE) Residual BLER Bin10
LTE VoLTE BLER Histogram
M8054C21
Uplink QCI1 (VoLTE) Residual BLER Bin11
LTE VoLTE BLER Histogram
Note: Good in counter QCI1 (VoLTE) UEs in good conditions in DL means that there was a QCI1 (VoLTE) UE for which 99,00% of the PDCP service data units (SDUs) have been received within a 100-ms delay in the downlink.
Bad in counter QCI1 (VoLTE) UEs in bad conditions in DL means that there was a QCI1 (VoLTE) UE for which less than 99,00% of the PDCP SDUs have been received within a 100-ms delay in the downlink. The information above is valid for all the UEs in a cell, with an established QCI1 bearer which has sent at least 100 SDUs. For counter descriptions, see LTE Radio Access Operating Documentation/ Reference/Counters. Key performance indicators There are no key performance indicators related to the LTE2493: Enhanced VoLTE Performance Monitoring feature. Parameters Table 238
New parameters introduced by LTE2493 Full name
LTE VoLTE BLER Histogram
Abbreviated name
mtVoLTEBLERHist
Managed object PMRNL
Parent structure –
For parameter descriptions, see LTE Radio Access Operating Documentation/ Reference/Parameters. Sales information
318
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 239
Descriptions of performance monitoring features
LTE2493 sales information
Product structure class
License control
Activated by default
Basic Software (BSW)
–
Yes
6.3 LTE2766: Flexible QCI/ARP PM Counter Profiles Benefits, functionality, system impact, reference data, instructions of the feature The LTE2766: Flexible QCI/ARP PM Counter Profiles feature introduces new configurable counters and provides an additional function with more flexible and dynamic configuration options especially for the operator-configurable QoS class indicators (QCIs). The existing statically defined performance management (PM) counters that are QCI-differentiated are untouched and are available as before.
6.3.1 LTE2766 benefits The LTE2766: Flexible QCI/ARP PM Counter Profiles feature provides the ability to investigate into details the performance of the eNB on a per-QCI and on a per-allocation and retention priority (ARP) resolution.
6.3.2 LTE2766 functional description The LTE2766: Flexible QCI/ARP PM Counter Profiles feature provides a configurable selection or groups of counters with certain QCIs and ARPs that are selected by the operator. A profile is defined as one certain QCI or a combination of one certain QCI and one certain ARP. The QCIs can be chosen from the following: •
Overall range of the standardized (3GPP 23.203) QCIs: – –
•
1 to 9 65, 66, 69, and 70
Operator-specific QCIs (range is 128 to 254)
The ARP further differentiates each profile set up by a certain QCI from a range of 1 to 15, defined as: Profile_x = {QCI_y; ARP_z} or {QCI_y} where • • •
g
Issue: 01 Draft
1 <= x <= 20 1 <= y <= 9 or y = {65, 66, 69, 70} or 128 <= y <= 254 1 <= z <= 15 Note: A maximum of 20 profiles can be configured. Configuring a large number of profiles is not recommended as it has an impact on the overall eNB capacity and performance.
DN09237915
319
Descriptions of performance monitoring features
FDD-LTE16A, Feature Descriptions and Instructions
The following categories can be enabled or disabled separately for every profile collection of the PM counters: • • •
Maximum and average number of active users per cell having established bearers with the specific QCI or ARP combination Data volume in the uplink (UL) and downlink (DL) E-RAB accessibility – –
•
E-RAB retainability – – –
•
Setup attempts and successes For initial and additional E-RAB setups
Normal E-RAB releases Abnormal E-RAB releases (while having data in buffer) E-RAB activity
Integrity – –
Average active packet data convergence protocol (PDCP) cell throughput in the UL and DL Latency
6.3.3 LTE2766 system impact LTE2766: Flexible QCI/ARP PM Counter Profiles impact on features and system performance and capacity Interdependencies between features The LTE2766: Flexible QCI/ARP PM Counter Profiles feature affects the following features: • • • • • • • • • •
LTE7: Support of Multiple EPS Bearers LTE9: Service Differentiation LTE10: EPS Bearer for Conversational Voice – Support of QCI 1 LTE496: Support of QCI 2, 3, and 4 LTE497: Smart Admission Control LTE518: Operator-specific QCIs LTE519: eRAB Modification LTE534: ARP-based Admission Control for E-RABs LTE1231: Operator-specific GBR QCIs LTE1321: eRAB Modification GBR
Impact on interfaces The LTE2766: Flexible QCI/ARP PM Counter Profiles feature has no impact on interfaces. Impact on network management tools The LTE2766: Flexible QCI/ARP PM Counter Profiles feature has no impact on network management tools. Impact on system performance and capacity
320
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of performance monitoring features
The LTE2766: Flexible QCI/ARP PM Counter Profiles feature affects system performance and capacity. Keeping the number of PMQAP profiles as low as possible is advised because a high number of PMQAP profiles have significant impact on system performance and capacity.
6.3.4 LTE2766 reference data LTE2766: Flexible QCI/ARP PM Counter Profiles requirements, measurements and counters, parameters, and sales information Requirements Table 240
LTE2766 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
AirScale FDD
FL16A
FL16A
UE
LTE OMS16A
Support not required
Flexi Zone Micro BTS FL16A
NetAct NetAct 16.8
Flexi Zone Access Point FL16A
MME Support not required
SAE GW Support not required
Alarms There are no alarms related to the LTE2766: Flexible QCI/ARP PM Counter Profiles feature. BTS faults and reported alarms There are no faults related to the LTE2766: Flexible QCI/ARP PM Counter Profiles feature. Commands There are no commands related to the LTE2766: Flexible QCI/ARP PM Counter Profiles feature. Measurements and counters Table 241 Counter ID
Issue: 01 Draft
New counters introduced by LTE2766 Counter name
Measurement
M8046C0
Max Active UE per Cell per Profile
LTE Active Users and Latency Statistics per PMQAP Profile
M8046C1
Avg Active UE per Cell per Profile
LTE Active Users and Latency Statistics per PMQAP Profile
M8046C2
Average PDCP SDU delay on DL DTCH for DRB per Profile
LTE Active Users and Latency Statistics per PMQAP Profile
M8046C3
Average HARQ transmission time per Profile
LTE Active Users and Latency Statistics per PMQAP Profile
M8047C0
IP Throughput data volume in DL per Profile
LTE Data Volume and Throughput Statistics per PMQAP Profile
M8047C1
IP Throughput data volume in UL per Profile
LTE Data Volume and Throughput Statistics per PMQAP Profile
DN09237915
321
Descriptions of performance monitoring features
Table 241 Counter ID
New counters introduced by LTE2766 (Cont.) Counter name
Measurement
M8047C2
IP Throughput time in DL per Profile
LTE Data Volume and Throughput Statistics per PMQAP Profile
M8047C3
IP Throughput time in UL per Profile
LTE Data Volume and Throughput Statistics per PMQAP Profile
M8047C4
PDCP SDU data volume on eUu Interface downlink per Profile
LTE Data Volume and Throughput Statistics per PMQAP Profile
M8047C5
PDCP SDU data volume on eUu Interface uplink per Profile
LTE Data Volume and Throughput Statistics per PMQAP Profile
M8047C6
Number of TTIs in DL with at least one UE scheduled to receive user plane data per Profile
LTE Data Volume and Throughput Statistics per PMQAP Profile
M8048C0
Setup attempts for initial E-RABs per Profile
LTE ERAB Statistics per PMQAP Profile
M8048C1
Successfully established initial E-RABs per QoS Profile
LTE ERAB Statistics per PMQAP Profile
M8048C2
E-RABs Normal releases per Profile
LTE ERAB Statistics per PMQAP Profile
M8048C3
E-RABs Abnormal releases per Profile
LTE ERAB Statistics per PMQAP Profile
M8048C4
In-session ERABs activity time per Profile
LTE ERAB Statistics per PMQAP Profile
M8048C5
Setup attempts for additional E-RABs per Profile
LTE ERAB Statistics per PMQAP Profile
M8048C6
Successfully established additional E-RABs per QoS Profile
LTE ERAB Statistics per PMQAP Profile
Table 242 Counter ID
322
FDD-LTE16A, Feature Descriptions and Instructions
New counters related to LTE2766 Counter name
Measurement
M8006C17 4
Pre-empted GBR bearers
LTE EPS Bearer
M8006C17 5
Pre-empted non-GBR bearers
LTE EPS Bearer
M8006C18 1
In-session activity time for QCI1 ERABs
LTE EPS Bearer
M8006C18 2
In-session activity time for QCI2 ERABs
LTE EPS Bearer
M8006C18 3
In-session activity time for QCI3 ERABs
LTE EPS Bearer
M8006C18 4
In-session activity time for QCI4 ERABs
LTE EPS Bearer
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 242
Issue: 01 Draft
Descriptions of performance monitoring features
New counters related to LTE2766 (Cont.)
Counter ID
Counter name
M8006C18 5
In-session activity time for non-GBR ERABs (QCI5..9)
LTE EPS Bearer
M8013C5
Signaling Connection Establishment completions
LTE UE State
M8026C0
Number of lost PDCP SDUs in UL for QCI 5
LTE QoS
M8026C1
Number of lost PDCP SDUs in UL for QCI 6
LTE QoS
M8026C2
Number of lost PDCP SDUs in UL for QCI 7
LTE QoS
M8026C3
Number of lost PDCP SDUs in UL for QCI 8
LTE QoS
M8026C4
Number of lost PDCP SDUs in UL for QCI 9
LTE QoS
M8026C5
Number of lost PDCP SDUs in DL for QCI 5
LTE QoS
M8026C6
Number of lost PDCP SDUs in DL for QCI 6
LTE QoS
M8026C7
Number of lost PDCP SDUs in DL for QCI 7
LTE QoS
M8026C8
Number of lost PDCP SDUs in DL for QCI 8
LTE QoS
M8026C9
Number of lost PDCP SDUs in DL for QCI 9
LTE QoS
M8026C19
PDCP SDU DL QCI 5
LTE QoS
M8026C20
PDCP SDU DL QCI 6
LTE QoS
M8026C21
PDCP SDU DL QCI 7
LTE QoS
M8026C22
PDCP SDU DL QCI 8
LTE QoS
M8026C23
PDCP SDU DL QCI 9
LTE QoS
M8026C24
PDCP SDU UL QCI 5
LTE QoS
M8026C25
PDCP SDU UL QCI 6
LTE QoS
M8026C26
PDCP SDU UL QCI 7
LTE QoS
M8026C28
PDCP SDU UL QCI 8
LTE QoS
M8026C29
PDCP SDU UL QCI 9
LTE QoS
M8026C25 4
Number of lost PDCP SDUs in UL
LTE QoS
M8026C25 5
Number of lost PDCP SDUs in UL for QCI 1
LTE QoS
M8026C25 6
Number of lost PDCP SDUs in UL for QCI 2
LTE QoS
M8026C25 7
Number of lost PDCP SDUs in UL for QCI 3
LTE QoS
DN09237915
Measurement
323
Descriptions of performance monitoring features
Table 242
FDD-LTE16A, Feature Descriptions and Instructions
New counters related to LTE2766 (Cont.)
Counter ID
Counter name
Measurement
M8026C25 8
Number of lost PDCP SDUs in UL for QCI 4
LTE QoS
M8026C25 9
Number of lost PDCP SDUs in DL
LTE QoS
M8026C26 0
Number of lost PDCP SDUs in DL for QCI 1
LTE QoS
M8026C26 1
Number of lost PDCP SDUs in DL for QCI 2
LTE QoS
M8026C26 2
Number of lost PDCP SDUs in DL for QCI 3
LTE QoS
M8026C26 3
Number of lost PDCP SDUs in DL for QCI 4
LTE QoS
For counter descriptions, see LTE Performance Measurements and Key Performance Indicators. Key performance indicators There are no key performance indicators related to the LTE2766: Flexible QCI/ARP PM Counter Profiles feature. Parameters Table 243
New parameters introduced by LTE2766 Full name
Abbreviated name
Parent structure
Activate Flexible QCI and ARP PM Counter Profiles
actFlexQCIARPPMProfiles LNBTS
ARP Configuration
cfgARP
PMQAP
-
QCI Configuration
cfgQCI
PMQAP
-
Performance Monitoring QCI and ARP Profiles identifier
pmQAPId
PMQAP
-
LTE Active Users and Latency Statistics per PMQAP Profile
mtActUsersLatencyPMQAPP PMRNL rofile
-
LTE Data Volume and Throughput Statistics per PMQAP Profile
mtDataVolThrPMQAPProfil PMRNL e
-
PMRNL
-
LTE ERAB Statistics per mtERABPMQAPProfile PMQAP Profile
g
Managed object -
Note: The profiles are configured for the entire eNB, but the counters are on the LNCEL level. For parameter descriptions, see Flexi Multiradio BTS LTE Parameters. Sales information
324
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 244
Descriptions of performance monitoring features
LTE2766 sales information
Product structure class Application software (ASW)
License control SW Asset Monitoring
Activated by default No
6.4 LTE2804: RSRP and RSRQ Histograms The LTE2804: RSRP and RSRQ Histograms feature introduces new PM counters which enable capturing distribution of reference signal received power (RSRP) and reference signal received quality (RSRQ) values.
6.4.1 LTE2804 benefits The LTE2804: RSRP and RSRQ Histograms feature provides the following benefits: • •
Monitoring radio signal power and quality within a cell. Detecting possible coverage issues and adjusting mobility thresholds.
6.4.2 LTE2804 functional description The LTE2804: RSRP and RSRQ Histograms feature introduces new performance management (PM) counters, supported by Nokia BTS. These counters enable generating RSRP and RSRQ histograms for every served LTE cell. RSRP and RSRQ histograms The histograms consist of 18 RSRP bins and 10 RSRQ bins respectively. The minimum RSRP and RSRQ values and bin’s widths (separate for RSRP and RSRQ) are adjustable. The maximum value is not adjustable directly. That value is determined by the minimum value and the bin's width. The bin width determines the range of RSRQ and RSRP values to be accounted within a given bin. The first bin (Bin#1) and the last bin (Bin#n) count reports with RSRP and RSRQ values below minimum and above maximum. The remaining bins cover the RSRP and RSRQ values between min and max evenly. The customer can choose which reports to include in the histogram. The following events can be selected to contribute to the histograms: • • • • • • •
A3 intra-frequency handover RSRP-triggered A3 inter-frequency handover RSRQ-triggered A3 inter-frequency handover A5 intra-frequency handover A5 inter-frequency handover B2 inter-RAT Report strongest cell periodic
The default values for the RSRP, RSRQ and the bin size are as follows: • • •
Issue: 01 Draft
cfgrsrpmin= –140 dB cfgrsrpbinsize= 6 dB cfgrsrqmin= –19.5 dB
DN09237915
325
Descriptions of performance monitoring features
•
FDD-LTE16A, Feature Descriptions and Instructions
cfgrsrqbinsize= 2 dB
6.4.3 LTE2804 system impact Interdependencies between features There is no strict dependency between this feature and other features, but if the operator wants to collect the RSRP and RSRQ values from A3, A5, and B2 events, the following features must be activated: • • • • •
LTE55: Inter-frequency Handover LTE56: Inter-RAT Handover to WCDMA LTE570: Periodic UE Measurements LTE556: ANR Intra-LTE, Inter-frequency – UE-based LTE782: ANR – UE-based
Impact on interfaces The LTE2804 RSRP and RSRQ Histograms feature has no impact on interfaces. Impact on network management tools The LTE2804 RSRP and RSRQ Histograms feature has no impact on network management tools. Impact on system performance and capacity The LTE2804 RSRP and RSRQ Histograms feature has no impact on system performance or capacity.
6.4.4 LTE2804 reference data Requirements Table 245
LTE2804 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
Multiradio S4
FL16A
FL16A
UE
LTE OMS16A
3GPP R8 mandatory
NetAct NetAct 16.8
Flexi Zone Micro BTS FL16A MME support not required
Flexi Zone Access Point FL16A SAE GW support not required
Alarms There are no alarms related to the LTE2804: RSRP and RSRQ Histograms feature. BTS faults and reported alarms There are no faults related to the LTE2804: RSRP and RSRQ Histograms feature. Commands There are no commands related to the LTE2804: RSRP and RSRQ Histograms feature. Measurements and counters
326
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 246 Counter ID
Issue: 01 Draft
Descriptions of performance monitoring features
New counters introduced by LTE2804 Counter name
Measurement
M8052C 0
Number of RSRP measurements bin1
LTE RSRP and RSRQ Histogram
M8052C 1
Number of RSRP measurements bin2
LTE RSRP and RSRQ Histogram
M8052C 2
Number of RSRP measurements bin3
LTE RSRP and RSRQ Histogram
M8052C 3
Number of RSRP measurements bin4
LTE RSRP and RSRQ Histogram
M8052C 4
Number of RSRP measurements bin5
LTE RSRP and RSRQ Histogram
M8052C 5
Number of RSRP measurements bin6
LTE RSRP and RSRQ Histogram
M8052C 6
Number of RSRP measurements bin7
LTE RSRP and RSRQ Histogram
M8052C 7
Number of RSRP measurements bin8
LTE RSRP and RSRQ Histogram
M8052C 8
Number of RSRP measurements bin9
LTE RSRP and RSRQ Histogram
M8052C 9
Number of RSRP measurements bin10
LTE RSRP and RSRQ Histogram
M8052C 10
Number of RSRP measurements bin11
LTE RSRP and RSRQ Histogram
M8052C 11
Number of RSRP measurements bin12
LTE RSRP and RSRQ Histogram
M8052C 12
Number of RSRP measurements bin13
LTE RSRP and RSRQ Histogram
M8052C 13
Number of RSRP measurements bin14
LTE RSRP and RSRQ Histogram
M8052C 14
Number of RSRP measurements bin15
LTE RSRP and RSRQ Histogram
M8052C 15
Number of RSRP measurements bin16
LTE RSRP and RSRQ Histogram
M8052C 16
Number of RSRP measurements bin17
LTE RSRP and RSRQ Histogram
M8052C 17
Number of RSRP measurements bin18
LTE RSRP and RSRQ Histogram
M8052C 18
Number of RSRQ measurements bin1
LTE RSRP and RSRQ Histogram
M8052C 19
Number of RSRQ measurements bin2
LTE RSRP and RSRQ Histogram
M8052C 20
Number of RSRQ measurements bin3
LTE RSRP and RSRQ Histogram
M8052C 21
Number of RSRQ measurements bin4
LTE RSRP and RSRQ Histogram
DN09237915
327
Descriptions of performance monitoring features
Table 246
FDD-LTE16A, Feature Descriptions and Instructions
New counters introduced by LTE2804 (Cont.)
Counter ID
Counter name
Measurement
M8052C 22
Number of RSRQ measurements bin5
LTE RSRP and RSRQ Histogram
M8052C 23
Number of RSRQ measurements bin6
LTE RSRP and RSRQ Histogram
M8052C 24
Number of RSRQ measurements bin7
LTE RSRP and RSRQ Histogram
M8052C 25
Number of RSRQ measurements bin8
LTE RSRP and RSRQ Histogram
M8052C 26
Number of RSRQ measurements bin9
LTE RSRP and RSRQ Histogram
M8052C 27
Number of RSRQ measurements bin10
LTE RSRP and RSRQ Histogram
For counter descriptions, see LTE Radio Access Operating Documentation/Reference/Counters. Key performance indicators There are no key performance indicators related to the LTE2804: RSRP and RSRQ Histograms feature. Parameters Table 247
New parameters introduced by LTE2804 Full name
328
Abbreviated name
Managed object
Parent structure
Activate RSRP and RSRQ histograms
actRSRPRSRQHist
MRBTS/L NBTS
-
LTE RSRP and RSRQ histogram
mtRSRPRSRQHist
MRBTS/L NBTS/PM RNL
-
Performance monitoring pmRSRPRSRQHist RSRP and RSRQ histogram
MRBTS/L NBTS/PM RNL
-
A3 intra-frequency handover event
actpmA3intrafreqHO
MRBTS/L NBTS/PM RNL
pmRSRPRSRQHist
A5 inter-frequency handover event
actpmA5interfreqHO
MRBTS/L NBTS/PM RNL
pmRSRPRSRQHist
A5 intra-frequency handover event
actpmA5intrafreqHO
MRBTS/L NBTS/PM RNL
pmRSRPRSRQHist
B2 handover event
actpmB2
MRBTS/L NBTS/PM RNL
pmRSRPRSRQHist
Report strongest cell
actpmRSC
MRBTS/L NBTS/PM RNL
pmRSRPRSRQHist
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 247
Descriptions of performance monitoring features
New parameters introduced by LTE2804 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
A3 RSRP inter-frequency actpmrsrpA3interfre handover event qHO
MRBTS/L NBTS/PM RNL
pmRSRPRSRQHist
A3 RSRQ inter-frequency actpmrsrqA3interfre handover event qHO
MRBTS/L NBTS/PM RNL
pmRSRPRSRQHist
RSRP bin size
cfgrsrpbinsize
MRBTS/L NBTS/PM RNL
pmRSRPRSRQHist
Minimum RSRP
cfgrsrpmin
MRBTS/L NBTS/PM RNL
pmRSRPRSRQHist
RSRQ bin size
cfgrsrqbinsize
MRBTS/L NBTS/PM RNL
pmRSRPRSRQHist
Minimum RSRQ
cfgrsrqmin
MRBTS/L NBTS/PM RNL
pmRSRPRSRQHist
For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 248
LTE2804 sales information
Product structure class Application software (ASW)
License control SW Asset Monitoring
Activated by default No
6.5 LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles Benefits, functionality, system impact, reference data, instructions of the feature The LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles feature provides a configurable selection or groups of counters of QoS class indicators (QCIs) and public land mobile network identifications (PLMN-IDs).
6.5.1 LTE2915 benefits The LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles feature provides the ability to investigate into details the performance of the eNB on a per-QCI, on a per PLMN-ID, and on a per-allocation and retention priority (ARP) resolution.
Issue: 01 Draft
DN09237915
329
Descriptions of performance monitoring features
FDD-LTE16A, Feature Descriptions and Instructions
6.5.2 LTE2915 functional description This feature introduces an additional configuration for the PLMN-ID (in the structure of the mobile country code (MCC), mobile network code (MNC), and MNCLength parameters) in the QCI-ARP profiles (introduced in the LTE2766: Flexible QCI/ARP PM Counter Profiles feature). In this feature, up to 20 profiles can be configured in the system. A profile is defined as one certain QCI, one certain PLMN-ID, or any combination. The QCIs can be chosen from the following: •
Overall range of the standardized (3GPP 23.203) QCIs: – –
•
1 to 9 65, 66, 69, and 70
Operator-specific QCIs (range is 128 to 254)
Each profile set up by a certain QCI can be further differentiated by PLMN-IDs: Profile_x = {QCI_y; PLMNID_ z} or {QCI_y} or {PLMNID_ z} where 1 ≤ x ≤ 20 1 ≤ y ≤ 9, y = {65, 66, 69, 70} or 128 ≤ y ≤ 254 1 ≤ z ≤ n
g
Note: A maximum of 20 profiles can be configured. Configuring a large number of profiles is not recommended as it has an impact on the overall eNB capacity and performance. The following categories can be enabled or disabled separately for every profile collection of the performance management (PM) counters: • • •
Maximum and average number of active users per cell having established bearers with specific QCI in the corresponding PLMN Data volume in the uplink (UL) and downlink (DL) E-RAB accessibility – –
•
E-RAB retainability – – –
•
Normal E-RAB releases Abnormal E-RAB releases (while having data in buffer) ERAB activity
Integrity – –
330
Setup attempts and successes For initial and additional E-RAB setups
Average and maximum payload or IP throughput in the UL and DL Latency
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of performance monitoring features
6.5.3 LTE2915 system impact LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles impact on features and network management tools Interdependencies between features The LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles feature affects the following features: •
•
LTE2766: Flexible QCI/ARP PM Counter Profiles This feature provides a configurable selection or groups of counters with certain QCIs and ARPs including the range of the operator-specific QCIs (128 to 254). LTE2782: RRC Re-establishment and RLF PM Counters per QCI Profile This feature introduces counters for monitoring RLF statistics separately for every QCI-ARP profile (introduced in the LTE2766: Flexible QCI/ARP PM Counter Profiles feature), which allows optimization of QCI-dependent parameters.
Impact on interfaces The LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles feature has no impact on interfaces. Impact on network management tools The LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles feature has no impact on network management tools. Impact on system performance and capacity The LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles feature affects system performance and capacity. Keeping the number of PMQAP profiles as low as possible is advised because a high number of PMQAP profiles have significant impact on system performance and capacity.
6.5.4 LTE2915 reference data LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles requirements, measurements and counters, and sales information Requirements Table 249
LTE2915 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
FL16A
Flexi Multiradio 10 BTS
AirScale FDD
SBTS16A
Not supported
UE
LTE OMS16A
Support not required
NetAct NetAct 16.8
Flexi Zone Micro BTS FL16A MME Support not required
Flexi Zone Access Point FL16A SAE GW Support not required
Alarms There are no alarms related to the LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles feature.
Issue: 01 Draft
DN09237915
331
Descriptions of performance monitoring features
FDD-LTE16A, Feature Descriptions and Instructions
BTS faults and reported alarms There are no faults related to the LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles feature. Commands There are no commands related to the LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles feature. Measurements and counters Table 250 Counter ID
332
New counters related to LTE2915 Counter name
Measurement
M8006C17 4
Pre-empted GBR bearers
LTE EPS Bearer
M8006C17 5
Pre-empted non-GBR bearers
LTE EPS Bearer
M8006C18 1
In-session activity time for QCI1 ERABs
LTE EPS Bearer
M8006C18 2
In-session activity time for QCI2 ERABs
LTE EPS Bearer
M8006C18 3
In-session activity time for QCI3 ERABs
LTE EPS Bearer
M8006C18 4
In-session activity time for QCI4 ERABs
LTE EPS Bearer
M8006C18 5
In-session activity time for non-GBR ERABs (QCI5..9)
LTE EPS Bearer
M8013C5
Signaling Connection Establishment completions
LTE UE State
M8026C0
Number of lost PDCP SDUs in UL for QCI 5
LTE QoS
M8026C1
Number of lost PDCP SDUs in UL for QCI 6
LTE QoS
M8026C2
Number of lost PDCP SDUs in UL for QCI 7
LTE QoS
M8026C3
Number of lost PDCP SDUs in UL for QCI 8
LTE QoS
M8026C4
Number of lost PDCP SDUs in UL for QCI 9
LTE QoS
M8026C5
Number of lost PDCP SDUs in DL for QCI 5
LTE QoS
M8026C6
Number of lost PDCP SDUs in DL for QCI 6
LTE QoS
M8026C7
Number of lost PDCP SDUs in DL for QCI 7
LTE QoS
M8026C8
Number of lost PDCP SDUs in DL for QCI 8
LTE QoS
M8026C9
Number of lost PDCP SDUs in DL for QCI 9
LTE QoS
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 250 Counter ID
Descriptions of performance monitoring features
New counters related to LTE2915 (Cont.) Counter name
Measurement
M8026C19
PDCP SDU DL QCI 5
LTE QoS
M8026C20
PDCP SDU DL QCI 6
LTE QoS
M8026C21
PDCP SDU DL QCI 7
LTE QoS
M8026C22
PDCP SDU DL QCI 8
LTE QoS
M8026C23
PDCP SDU DL QCI 9
LTE QoS
M8026C24
PDCP SDU UL QCI 5
LTE QoS
M8026C25
PDCP SDU UL QCI 6
LTE QoS
M8026C26
PDCP SDU UL QCI 7
LTE QoS
M8026C28
PDCP SDU UL QCI 8
LTE QoS
M8026C29
PDCP SDU UL QCI 9
LTE QoS
M8026C25 4
Number of lost PDCP SDUs in UL
LTE QoS
M8026C25 5
Number of lost PDCP SDUs in UL for QCI 1
LTE QoS
M8026C25 6
Number of lost PDCP SDUs in UL for QCI 2
LTE QoS
M8026C25 7
Number of lost PDCP SDUs in UL for QCI 3
LTE QoS
M8026C25 8
Number of lost PDCP SDUs in UL for QCI 4
LTE QoS
M8026C25 9
Number of lost PDCP SDUs in DL
LTE QoS
M8026C26 0
Number of lost PDCP SDUs in DL for QCI 1
LTE QoS
M8026C26 1
Number of lost PDCP SDUs in DL for QCI 2
LTE QoS
M8026C26 2
Number of lost PDCP SDUs in DL for QCI 3
LTE QoS
M8026C26 3
Number of lost PDCP SDUs in DL for QCI 4
LTE QoS
For counter descriptions, see LTE Performance Measurements and Key Performance Indicators. Key performance indicators There are no key performance indicators related to the LTE2915: Flexible QCI/PLMN-ID PM Counter Profiles feature. Parameters
Issue: 01 Draft
DN09237915
333
Descriptions of performance monitoring features
Table 251
FDD-LTE16A, Feature Descriptions and Instructions
New parameters introduced by LTE2915 Full name
Abbreviated name
Activate Flexible QCI and PLMN-ID PM Counter Profiles
Table 252
Managed object
actFlexQCIPLMNIDPMProf iles
LNBTS
Parent structure -
New parameters related to LTE2915 Full name
Abbreviated name
Managed object
Parent structure
ARP Configuration
cfgARP
PMQAP
-
QCI Configuration
cfgQCI
PMQAP
-
LTE Active Users and Latency Statistics per PMQAP Profile
mtActUsersLatencyPMQAPP PMRNL rofile
-
LTE Data Volume and Throughput Statistics per PMQAP Profile
mtDataVolThrPMQAPProfil PMRNL e
-
LTE ERAB Statistics per PMQAP Profile
mtERABPMQAPProfile
PMRNL
-
LTE RLF Statistics per PMQAP Profile
mtRLFPMQAPProfile
PMRNL
-
For parameter descriptions, see Flexi Multiradio BTS LTE Parameters. Sales information Table 253
LTE2915 sales information
Product structure class Application Software (ASW)
334
License control Pool license
DN09237915
Activated by default No
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Description of Flexi Zone Controller features
7 Description of Flexi Zone Controller features 7.1 LTE2576: Integrated GMC and BC Support on Flexi Zone Controller The LTE2576: Integrated GMC & BC Support on Flexi Zone Controller feature provides an integrated IEEE1588v2 Grand Master Clock (GMC) and Boundary Clock (BC). An integrated GMC and BC eliminates the need for an external GMC within or outside the operator's Local Area Network (LAN). It also supports both Time and Phase synchronization.
7.1.1 LTE2576 benefits The LTE2576: Integrated GMC & BC Support on Flexi Zone Controller feature provides the following benefits: • • • • •
complete Zone Controller solution with support for Phase and Time 1588v2 ToP accurate Phase/Time Synchronization sent to FZAPs from the FZC eliminates the need for an external GMC and BC occupies less space and requires less cabling thereby lowering backhaul requirements increases savings and reduces costs for operators
7.1.2 LTE2576 functional description The Flexi Zone Controller hardware platform supports the optional integrated IEEE1588v2 GMC/BC Module. The module provides the following capabilities: • • • • • • • • • • •
Multi-GNSS antenna with integrated receiver Front panel Serial Port for debugging and maintenance Optional 1PPS output for maintenance RS-422 connector for 1PPS and "Time at the Pulse" serial data 100 FZAP supported for a single GMC License with an option to scale up to 500 FZAPs Support for both Time and Phase synchronization Accuracy at client ~±1 us or better Support for ITU-T G.8275.2 Telecom Profile for phase synchronization in non-daisy chained deployments Support for ITU-T G.8261 and G.8271 Telecom Profiles Clock performance to meet TDD-LTE and LTE-A synchronization requirements Support for both Unicast and Multicast modes (G8275.1)
7.1.3 LTE2576 system impact Interdependencies between features The LTE2576: Integrated GMC & BC Support on Flexi Zone Controller feature impacts the following features:
Issue: 01 Draft
DN09237915
335
Description of Flexi Zone Controller features
•
•
FDD-LTE16A, Feature Descriptions and Instructions
LTE1996: Flexi Zone Controller Application This feature provides the basic capability to host the Flexi Zone Controller Application on the BCN platform. LTE2203 (Base FZC features): Flexi Zone Controller Application on BCN Platform The platform provides scalability, capacity, and redundancy required by the Flexi Zone Controller Applications.
Impact on interfaces The LTE2576: Integrated GMC & BC Support on Flexi Zone Controller feature has no impact on interfaces. Impact on network management tools The LTE2576: Integrated GMC & BC Support on Flexi Zone Controller feature has no impact on network management tools. Impact on system performance and capacity The LTE2576: Integrated GMC & BC Support on Flexi Zone Controller feature has no impact on system performance or capacity.
7.1.4 LTE2576 reference data Requirements Table 254 System release FDD-LTE 16A
LTE2576 hardware and software requirements Flexi Multiradio BTS Support not required
Flexi Zone Controller FLC16A
Flexi Multiradio 10 BTS
Nokia AirScale BTS
Support not required
Support not required
OMS
UE
Support not required
Support not required
NetAct NetAct 16.8
Flexi Zone Micro BTS Support not required MME Support not required
Flexi Zone Access Point FL16A
SAE GW Support not required
Alarms Information on alarms for the LTE2576: Integrated GMC & BC Support on Flexi Zone Controller feature will be made available in a future release. Measurements and counters There are no measurements or counters related to the LTE2576: Integrated GMC & BC Support on Flexi Zone Controller feature. Key performance indicators There are no key performance indicators related to the LTE2576: Integrated GMC & BC Support on Flexi Zone Controller feature. Parameters Information on parameters for the LTE2576: Integrated GMC & BC Support on Flexi Zone Controller feature will be made available in a future release. Sales information
336
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 255
Description of Flexi Zone Controller features
LTE2576 sales information
Product structure class Application software (ASW)
License control SW Asset Monitoring
Activated by default Yes
7.2 LTE2373: Vendor Certificate Usage for Flexi Zone Controller The LTE2373: Vendor Certificate Usage for Flexi Zone Controller feature uses the installed vendor certificates on the Flexi Zone Controller for various applications. It extends the support for Certificate Management Protocol (CMP) implementation and secures the Site Manager interface.
7.2.1 LTE2373 benefits The LTE2373: Vendor Certificate Usage for Flexi Zone Controller feature provides enhanced security by using vendor certificates on the Flexi Zone Controller together with the operator's Public Key Infrastructure.
7.2.2 LTE2373 functional description Flexi Zone Controller supports the installation of vendor certificates through factory and repair centers. These installed vendor certificates (including Nokia’s intermediate factory CA and Root certificates) are stored in a secure storage on the BCN platform. This feature uses the installed Nokia’s certificates for: • •
Securing Site Manager interface using Transport Layer Security (TLS) CMP Implementation
The feature also provides alarms to notify the operators when the installed certificates are about to expire. Additionally, the feature supports auto-renewal of installed certificates.
7.2.3 LTE2373 system impact Interdependencies between features The LTE2373: Vendor Certificate Usage for Flexi Zone Controller feature has no interdependencies with other features. Impact on interfaces The LTE2373: Vendor Certificate Usage for Flexi Zone Controller feature has no impact on interfaces. Impact on network management tools The LTE2373: Vendor Certificate Usage for Flexi Zone Controller feature has no impact on network management tools. Impact on system performance and capacity The LTE2373: Vendor Certificate Usage for Flexi Zone Controller feature has no impact on system performance and capacity.
Issue: 01 Draft
DN09237915
337
Description of Flexi Zone Controller features
FDD-LTE16A, Feature Descriptions and Instructions
7.2.4 LTE2373 reference data Requirements Table 256 System release FDD-LTE 16A
LTE2373 hardware and software requirements Flexi Multiradio BTS Support not required
Flexi Zone Controller FLC16A
Flexi Multiradio 10 BTS
Nokia AirScale BTS
Support not required
Not supported
OMS
UE
Support not required
Support not required
Flexi Zone Micro BTS FL16A
NetAct NetAct 16.8
Flexi Zone Access Point FL16A
MME
SAE GW
Support not required
Support not required
BTS faults and reported alarms Table 257
Existing BTS faults related to LTE2373
Fault ID
61616
Fault name
Reported alarms Alarm ID
Vendor BTS certificate is about to expire
7665
Alarm name
BASE STATION TRANSMISSION ALARM
Commands For command descriptions, see Flexi Zone Controller SCLI Commands. Measurements and counters There are no measurements or counters related to the LTE2373: Vendor Certificate Usage for Flexi Zone Controller feature. Key performance indicators There are no key performance indicators related to the LTE2373: Vendor Certificate Usage for Flexi Zone Controller feature. Parameters There are no parameters related to the LTE2373: Vendor Certificate Usage for Flexi Zone Controller feature. Sales information Table 258
LTE2373 sales information
Product structure class Basic Software (BSW)
338
License control -
DN09237915
Activated by default Yes
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of OAM/Troubleshoot features
8 Descriptions of OAM/Troubleshoot features 8.1 LTE2805: Monitoring RX Sensitivity The LTE2805: Monitoring RX Sensitivity feature introduces the possibility of monitoring the signal level of a BTS radio receiver (RX) and raising alarms when it falls below a certain threshold.
8.1.1 LTE2805 benefits The LTE2805: Monitoring RX Sensitivity feature provides the operator with following information: an alarm when RX signal level is below treshold impact of low RX signal on a cell (cell faulty or degraded)
• •
8.1.2 LTE2805 functional description The LTE2805: Monitoring RX Sensitivity feature is activated with the BTSSCL Activate RX monitoring (actRxMonitoring) parameter. When this parameter is set to true, the BTS measures periodically the received total wideband power (RTWP) in the uplink of the enabled cells. The RTWP is the sum of the received user's signal power, all interference, and thermal noise power. Once the BTS detects that the RTWP level is below threshold, it calculates the impact of a radio receiver failure on a cell's operational state. As a result, a RTWP level below threshold (4333) fault is raised, which triggers either 7653 CELL FAULTY or 7654 CELL OPERATION DEGRADED alarm. The thresholds of RTWP level are defined for every bandwidth (see table below). The RTWP fault is correlated with other BTS faults and is active only if no other faults for RX malfunction are raised (for example, RX out of order (1911) or RF Module failure (3010) ). Active alarms raised due to RX monitoring are cancelled when the feature is deactivated (actRxMonitoring is set to false), or when operator performed action which reestablishes carrier (like locking/unlocking cell or radio reset).
g
Note: If feature is deactivated while 7653 CELL FAULTY or 7654 CELL OPERATION DEGRADED alarm is activated, it could lead to scenario of silently degraded cell or sleeping cell. Table 259
FDD RTWP threshold values Bandwidth (MHz)
Issue: 01 Draft
Value (dBm)
1.4
-117
3
-114
5
-112
10
-109
DN09237915
339
Descriptions of OAM/Troubleshoot features
Table 259
FDD-LTE16A, Feature Descriptions and Instructions
FDD RTWP threshold values (Cont.) Bandwidth (MHz)
Value (dBm)
15
-107
20
-106
8.1.3 LTE2805 system impact LTE2805: Monitoring RX Sensitivity has no impact on features, interfaces, network management tools, and system performance and capacity.
8.1.4 LTE2805 reference data Requirements Table 260
LTE2805 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE16A
not supported
Flexi Zone Controller
OMS
not supported
16A
Flexi Multiradio 10 BTS
AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
not supported
not supported
not supported
NetAct
MME
SAE GW
UE support not required
16.8
support not required
support not required
BTS faults and reported alarms Table 261 Fault ID
4333
New BTS faults introduced by LTE2805 Fault name
Reported alarms Alarm ID
Alarm name
RTWP level below threshold
7653
CELL FAULTY
( FaultID_RtwpLevelBelowThresh oldAl)
7654
CELL OPERATION DEGRADED
For fault descriptions, see LTE Operating Documentation/Reference/Alarms and Faults. Commands There are no commands related to the LTE2805: Monitoring RX Sensitivity feature. Measurements and counters There are no measurements or counters related to the LTE2805: Monitoring RX Sensitivity feature. Key performance indicators There are no key performance indicators related to the LTE2805: Monitoring RX Sensitivity feature. Parameters
340
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 262
Descriptions of OAM/Troubleshoot features
New parameters introduced by LTE2805 Full name
Abbreviated name
Activate RX monitoring
actRxMonitoring
Managed object BTSSCL
Parent structure -
For parameter descriptions, see LTE Operating Documentation/Reference/Parameters. Sales information Table 263
LTE2805 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
8.2 LTE2883: Application of Diagnostic and Maintenance for Intelligent Network The LTE2883: Application of Diagnostic and Maintenance for Intelligent Network feature introduces a new web-based tool (called ADMIN) for eNB diagnostic tasks. Its purpose is to help analyze the state of an eNB and propose a solution to abnormal states of the eNB.
8.2.1 LTE2883 benefits The LTE2883: Application of Diagnostic and Maintenance for Intelligent Network feature reduces the time required to solve operability problems of an eNB by providing a dedicated tool in which root causes are more visible.
8.2.2 LTE2883 functional description The LTE2883 feature introduces the Application of Diagnostic and Maintenance for Intelligent Network (ADMIN) tool, which is a web application connected to an eNB. The ADMIN tool reads the available FM (faults and alarms), CM (configuration parameters), and PM (counters and KPIs) data from the BTS. Next, it analyzes the available data, diagnoses the issues present in the BTS, and decides which of the following states the BTS is in: • • • •
fully operational partially operational (not all cells are impacted) not operational (all cells are impacted) abnormal/unpredictable
After recognizing the state, the ADMIN tool determines appropriate recovery actions for the diagnosed issues. Each recovery action is displayed with its service impact, corresponding issues it will resolve, and actions automatically initiated by the BTS. The ADMIN tool allows the operator to apply all of the recommended recovery actions, only a subset of the recommended recovery actions, or none of the recommended recovery actions.
Issue: 01 Draft
DN09237915
341
Descriptions of OAM/Troubleshoot features
FDD-LTE16A, Feature Descriptions and Instructions
ADMIN can be triggered from BTS SM, NetAct, or the operator's PC. When executed from NetAct, it supports the single sign-on. The operator can invoke a maximum of 10 instances of the ADMIN tool on an eNB simultaneously without influencing the throughput of eNB connection.
g
Note: The operator must have a read-write access to the eNB in order to launch the ADMIN tool. As long as the ADMIN tool remains launched and open, it is continuously updated so that it always has the latest BTS information.
8.2.3 LTE2883 system impact LTE2883: Application of Diagnostic and Maintenance for Intelligent Network has no impact on features, interfaces, network management tools, and system performance and capacity.
8.2.4 LTE2883 reference data Requirements Table 264
LTE2883 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE16A
not supported
Flexi Zone Controller
OMS
not supported
Flexi Multiradio 10 BTS
AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
not supported
not supported
not supported
NetAct
MME
SAE GW
UE
LTE OMS 16A support not required
16.8
support not required
support not required
Alarms There are no alarms related to the LTE2883: Application of Diagnostic and Maintenance for Intelligent Network feature. Measurements and counters There are no measurements or counters related to the LTE2883: Application of Diagnostic and Maintenance for Intelligent Network feature. Key performance indicators There are no key performance indicators related to the LTE2883: Application of Diagnostic and Maintenance for Intelligent Network feature. Parameters There are no parameters related to the LTE2883: Application of Diagnostic and Maintenance for Intelligent Network feature. Sales information Table 265
LTE2883 sales information
Product structure class Basic Software (BSW)
342
License control -
DN09237915
Activated by default Yes
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
9 Descriptions of BTS site solution features 9.1 LTE180: Cell Radius Max 100 km Benefits, functionality, system impact, reference data, instructions of the feature The LTE180: Cell radius max 100 km feature extends the Flexi LTE BTS cell coverage to a maximum of 100 km. The feature is activated by configuring a management parameter combination for Packet Random Access Channel (PRACH).
9.1.1 LTE180 benefits The LTE180: Cell radius max 100 km feature is beneficial as it: • • • •
extends the cell coverage in locations like rural areas or coastlines, where an additional eNodeB (eNB) site installation is not possible or justified by the traffic load. extends the cell coverage for public safety use cases. offers cost-efficiency in covering remote location. provides the 100 km cell range support with all the downlink and uplink Carrier Aggregation (CA) features.
9.1.2 LTE180 functional description The feature is activated with the PRACH configuration index management parameter, which must be configured within the range of 51-56. The UE uses PRACH format3 for preamble transmission. Higher capacity (required in the public safety use case, for instance) can be achieved by enabling two PRACH occasions per radio frame with indices 54, 55, and 56. The actual coverage obtained depends on many practical parameters, for example: the RF band in use, BTS and UE antenna type and height, interference from other traffic or systems. In order to achieve the maximum cell radius of 100 km, the PRACH cyclic shift parameter must be configured to zero. Also, high antenna towers or high mountain eNB site deployments are required in that case. LTE180 also supports Guaranteed Bit Rate (GBR) services. However, if the UE is far away from the eNB, this capability is limited. Therefore, the GBR services should be planned and enabled with caution.
9.1.3 LTE180 system impact LTE180: Cell radius max 100 km impact on features, interfaces, and system performance Interdependencies between features The following feature is affected by the LTE180: Cell radius max 100 km feature: •
Issue: 01 Draft
LTE40: Physical & Transport Channels
DN09237915
343
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
With extended cell radius configured, sufficient coding rate used for message 2 and message 4 transmissions of Random Access Procedure must be ensured. Sufficient code rate must also be ensured for System Information Blocks (SIB) and paging messages. The following features should be carefully considered in very long range cells due to potentially degraded KPIs: • •
LTE10: EPS Bearers for Conversational Voice LTE496: Support of QCI 2, 3 and 4
The following features are not supported with the LTE180: Cell radius max 100 km feature: • • • • • • • • • •
LTE48: Support of High Speed Users LTE72: 4-way RX diversity LTE980: IRC for 4 RX paths LTE568: DL adaptive closed loop MIMO (4x2) LTE1987: Downlink Adaptive Close Loop SU MIMO (4x4) LTE117: Cell Bandwidth - 1.4.MHz LTE1542: FDD Supercell LTE2445: Combined Supercell LTE1709: Liquid Cell LTE2091: FDD SuperCell extension
Impact on interfaces The LTE180: Cell radius max 100 km feature impacts interfaces as follows: •
Air interface (Uu) Packet Random Access Channel (PRACH) format3 length is 2.28 ms, thus spanning over three Transmission Time Intervals (TTIs) in uplink.
Impact on network management tools The LTE180: Cell radius max 100 km feature has no impact on network management tools. Impact on system performance The LTE180: Cell radius max 100 km feature impacts system performance in three areas as shown in the table below: Table 266
344
LTE180 impact on system performance
Throughput
Quality
Latency
The slight impact on the UL throughput is caused by three TTIs being used by PRACH preamble format3 per PRACH opportunity. Compare that to one TTI allocated to PRACH format0, or two TTIs to PRACH format1.
The 3GPP PRACH receiver performance requirements specified by TS 36.104 and TS 36.141 are met.
Since extended cell radius with PRACH format3 requires three TTIs for the RACH reception, there is a greater delay compared to format0 (one TTI) or format1 (two TTIs).
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
9.1.4 LTE180 reference data LTE180: Cell radius max 100 km requirements, parameters, and sales information Requirements Table 267
LTE180 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL17
UE
Not supported Support not required
Support not required
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
NetAct NetAct 16.8
Support not required
Support not required
Alarms There are no alarms related to the LTE180: Cell radius max 100 km feature. BTS faults and reported alarms There are no faults related to the LTE180: Cell radius max 100 km feature. Commands There are no commands related to the LTE180: Cell radius max 100 km feature. Measurements and counters There are no measurements or counters related to the LTE180: Cell radius max 100 km feature. Key performance indicators There are no key performance indicators related to the LTE180: Cell radius max 100 km feature. Parameters Table 268
Parameters modified by LTE180 Full name
PRACH configuration index
Table 269
Abbreviated name
prachConfIndex
LNCEL
Parent structure -
Existing parameters related to LTE180 Full name
Abbreviated name
Managed object
Parent structure
Antenna line id
antlId
LCELL
Resource list (resourceList)
Sub cell identifier
subCellId
LCELL
Resource list (resourceList)
TX and RX usage
txRxUsage
LCELL
Resource list (resourceList)
LNCEL
-
Activate combined actCombSuperCell supercell configuration
Issue: 01 Draft
Managed object
DN09237915
345
Descriptions of BTS site solution features
Table 269
FDD-LTE16A, Feature Descriptions and Instructions
Existing parameters related to LTE180 (Cont.) Full name
Abbreviated name
Managed object
Parent structure
Activate liquid cell configuration
actLiquidCell
LNCEL
-
Activate supercell configuration
actSuperCell
LNCEL
-
Downlink channel bandwidth
dlChBw
LNCEL
-
PRACH cyclic shift
prachCS
LNCEL
-
PRACH high speed flag
prachHsFlag
LNCEL
-
Activate timing advance actTaHistCounters MRBTS/L histogram PM counters NBTS Expected Cell Size
expectedCellSize
MRBTS/L NBTS/LN CEL
-
For parameter descriptions, see FDD-LTE BTS Parameters. Sales information Table 270
LTE180 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
9.2 LTE2114: AirScale Common ASIA Benefits, functionality, system impact, reference data of the feature The LTE2114: AirScale Common ASIA feature introduces AirScale Common (ASIA), which is an indoor common plug-in unit for the next generation of a highly integrated System Module, called AirScale System Module Indoor. AirScale Common plug-in unit provides the transport interfaces and centralized processing. Cell specific baseband processing is provided by AirScale Capacity (ABIA) plug-in units. The processing capacity of the AirScale System Module Indoor can be flexibly expanded by adding Capacity and Common plug-in units.
9.2.1 LTE2114 benefits The AirScale System Module Indoor is a successor of the Flexi Multiradio 10 System Module providing enhanced capacity, connectivity and expansion possibilities in the same form factor in indoor installations. The AirScale System Module Indoor is further optimized for supporting LTE advanced features, such as Carrier Aggregation and Coordinated Multi-Point in high capacity system configurations.
346
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
9.2.2 LTE2114 functional description Nokia AirScale System Module Indoor consists of the following items: • • •
One AirScale Subrack (AMIA), including backplane for high bandwidth connectivity between processing plug-in units One or two AirScale Common (ASIA) plug-in units for transport interfacing and for centralized processing Up to six AirScale Capacity (ABIA) plug-in units for baseband processing and for optical interfaces with radio units
The figure below presents the AirScale System Module Indoor. Figure 42
AirScale SM Indoor
AirScale Capacity ABIA
AirScaleSubrackAMIA
AirScale Common ASIA AirScale System Module Indoor consists of the following items in minimum starting configuration: • • •
One AirScale Subrack (AMIA) One AirScale Common (ASIA) One AirScale Capacity (ABIA)
The processing capacity of the AirScale SM Indoor can be extended by adding more ABIA plug-in units. One half of the AMIA can accommodate one ASIA plug-in unit and up to three ABIA plug-in units within the left or right half of the indoor subrack. Further, one AMIA can accommodate two of the above sub-configurations within 3U height. For supported HW configurations, see the Creating Nokia AirScale BTS FDD-LTE Configurations document. The AirScale SM Indoor is IP20 ingress protected and operates at the temperature range from -5 to +55 °C. The following functions are integrated in the ASIA: • •
Issue: 01 Draft
Ethernet transport Clock and control functions
DN09237915
347
Descriptions of BTS site solution features
• •
FDD-LTE16A, Feature Descriptions and Instructions
Fan control Status LEDs
The figure below presents the front view of the AirScale Common (ASIA). Figure 43
Front panel of the ASIA
DC in
groundingconnector
EAC
SyncOUT
SyncIN
SEI1 SEI2
SRIO1
EIF1
SRIO2
EIF2
EIF3
EIF5
EIF4
LMP
The ASIA plug-in card provides the following interfaces: • • • • • • • • •
three electrical 1000Base-T transport interfaces two optical 1000/10GBase-X/R transport interfaces two Mini SAS-HD connectors for an external System Module extension two SRIO (Serial Rapid Input/Output) for an external System Module extension one electrical interface 1000Base-T as an LMP (Local Management Port) one Sync IN and one Sync OUT interface one EAC (External Alarm and Control) interface one -48 VDC power input grounding connector
For more information, see the Nokia AirScale Base Station Product Description document.
9.2.3 LTE2114 system impact LTE2114 impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features are required for AirScale System Module Indoor: • • •
LTE2114: AirScale Common ASIA (described in this document) LTE2261: AirScale Capacity ABIA LTE2262: AirScale Subrack AMIA
Impact on interfaces The LTE2114: AirScale Common ASIA feature has no impact on interfaces. Impact on network management tools
348
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
The LTE2114: AirScale Common ASIA feature has no impact on network management tools. Impact on system performance and capacity New configurations are available. For more information, see the Creating Nokia AirScale BTS FDD-LTE Configurations document.
9.2.4 LTE2114 reference data LTE2114 requirements, alarms and faults, measurements and counters, KPIs, parameters, and sales information Requirements Table 271
LTE2114 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FDD-LTE 16A
Not supported
Not supported
FL16A
Flexi Zone Controller
OMS
UE
Not supported Support not required
Support not required
NetAct Support not required
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
Support not required
Support not required
BTS faults and reported alarms Table 272 Fault ID
New BTS faults introduced by LTE2114 Fault name
Reported alarms Alarm ID
Alarm name
4335
DSP U-Plane computing 7653 environment startup failed
CELL FAULTY
4341
FSP subunit lost
7650
BASE STATION FAULTY
7651
BASE STATION OPERATION DEGRADED
7653
CELL FAULTY
For fault descriptions, see the FDD-LTE BTS Alarms and Faults document. Measurements and counters There are no measurements or counters related to the LTE2114 feature. Key performance indicators There are no key performance indicators related to the LTE2114 feature. Parameters
Issue: 01 Draft
DN09237915
349
Descriptions of BTS site solution features
Table 273
FDD-LTE16A, Feature Descriptions and Instructions
New parameters introduced by LTE2114 Full name
Abbreviated name
positionInSubrack SMOD
Position in subrack
Table 274
Managed object
Parent structure -
Parameters modified by LTE2114 Full name
Abbreviated name
Managed object
Parent structure
Link list
linkList
BBMOD
-
System Module Port Number
sModPort
BBMOD
-
Baseband module identifier
bbModId
BBMOD
-
Connection list
connectionList
RMOD
-
For parameter descriptions, see the FDD-LTE BTS Parameters document. Sales information Table 275
LTE2114 sales information
Product structure class
License control
Basic Software (BSW)
-
Activated by default Yes
9.3 LTE2252: FSM OD-Cabinet FCOB Benefits, functionality, system impact, reference data of the feature The LTE2252: FSM OD-Cabinet FCOB feature introduces the Flexi Cabinet Outdoor (FCOB). FCOB is an outdoor cabinet designed to house indoor System Modules providing them deployment in outdoor environment. The cabinet can accommodate one Flexi Multiradio 10 System Module Indoor (FSIH) or one Nokia AirScale System Module Indoor (AirScale SM Indoor).
9.3.1 LTE2252: benefits The LTE2252: FSM OD-Cabinet FCOB feature provides the following benefits: • • •
• • •
350
Flexi Multiradio 10 System Module Indoor (FSIH) or one Nokia AirScale System Module Indoor (AirScale SM Indoor) deployment in outdoor environment 3U installation space for one indoor System Module (FSIH or AirScale SM Indoor) 1U installation space for one optional indoor unit (OD External GNSS Enhanced Holdover (FYGG), Flexi Enhanced External GPS Box (FYGE), router or third party unit) IP55 protection level for indoor System Modules Two power outputs for internal units: maximum 42 A for output 1 and maximum 5 A for output 2 Protection against earthquakes, external damage or foreign objects
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
Descriptions of BTS site solution features
Possibility of vertical and horizontal installation
9.3.2 LTE2252 functional description The main features of the FCOB are as follows: • • • • • • •
IP55 protection for indoor system module deployment in outdoor environment From -40°C (-40°F) to 50°C (122°F) environment operating temperature and from -5°C (23°F) to 55°C (131°F) operating temperature for internal equipment From 5% to 85% relative humidity 4U internal space Working status of the cabinet monitored and collected via system module EAC interface Flexible installation options: FCOB is designed to be mounted onto a wall, pole or floor 29 kg (63.9 lbs) weight
The dimensions of FCOB are: • • •
Height: 600 mm (23.6 in.) Depth: 600 mm (23.6 in.) Width: 380 mm (15.0 in.)
The FCOB has four external alarms: • • • •
Door alarm Internal fans alarm External fans alarm High temperature alarm
The following are the FCOB installation configurations: • •
FSIH full configuration (FSIH+2xFBIH) + FYGG/E or other optional unit AirScale SM Indoor full configuration (AirScale Subrack (AMIA)+2x AirScale Common (ASIA)+6x AirScale Capacity (ABIA)) + FYGG/E or other optional unit
g
Note: Consult Nokia about your optional unit configuration.
g
Note: AirScale SM Indoor installation inside of the FCOB is supported from FDD-LTE 16A onwards. For more information on FCOB, see Flexi Multiradio Base Station and Flexi Multiradio 10 Base Station Optional Items Description.
9.3.3 LTE2252 system impact LTE2252: FSM OD-Cabinet FCOB has no impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features There are no interdependencies between the LTE2252: FSM OD-Cabinet FCOB feature and any other feature. Impact on interfaces
Issue: 01 Draft
DN09237915
351
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
The LTE2252: FSM OD-Cabinet FCOB feature has no impact on interfaces. Impact on network management tools The LTE2252: FSM OD-Cabinet FCOB feature has no impact on network management tools. Impact on system performance and capacity The LTE2252: FSM OD-Cabinet FCOB feature has no impact on system performance or capacity.
9.3.4 LTE2252 reference data LTE2252: FSM OD-Cabinet FCOB requirements and sales information Requirements Table 276
LTE2252: FSM OD-Cabinet FCOB hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FDD-LTE 16A
Not supported
Not supported
FL16A
Flexi Zone Controller
OMS
UE
Not supported Support not required
Support not required
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
NetAct Support not required
Support not required
Support not required
There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE2252: FSM OD-Cabinet FCOB feature. Sales information Table 277
LTE2252: FSM OD-Cabinet FCOB sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.4 LTE2261: AirScale Capacity ABIA Benefits, functionality, system impact, reference data of the feature The LTE2261: AirScale Common ABIA feature introduces AirScale Capacity (ABIA), which is an indoor common plug-in unit for the next generation of a highly integrated System Module, called AirScale System Module Indoor. AirScale Capacity plug-in unit provides cell-specific baseband processing and optical interfaces to radio units.
9.4.1 LTE2261 benefits The AirScale System Module Indoor is a successor of the Flexi Multiradio 10 System Modules (FSMF and FSIH) providing enhanced capacity, connectivity and expansion possibilities in the same form factor in indoor installations.
352
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
The AirScale System Module Indoor is further optimized for supporting LTE advanced features, such as Carrier Aggregation and Coordinated Multi-Point in high capacity system configurations.
9.4.2 LTE2261 functional description Nokia AirScale System Module Indoor consists of the following items: • • •
One AirScale Subrack (AMIA), including a backplane for high bandwidth connectivity between processing plug-in units One or two AirScale Common (ASIA) plug-in units for transport interfacing and for centralized processing Up to six AirScale Capacity (ABIA) plug-in units for baseband processing and for optical interfaces with radio units
The figure below presents the AirScale System Module Indoor. Figure 44
AirScale SM Indoor
AirScale Capacity ABIA
AirScaleSubrackAMIA
AirScale Common ASIA AirScale System Module Indoor consists of the following items in minimum starting configuration: • • •
One AirScale Subrack (AMIA) One AirScale Common (ASIA) One AirScale Capacity (ABIA)
The processing capacity of the AirScale SM Indoor can be extended by adding more ABIA plug-in units. One half of the AMIA can accommodate one ASIA plug-in unit and up to three ABIA plug-in units within the left or right half of the indoor subrack. Therefore, one AMIA can accommodate two of the above sub-configurations within 3U height. For supported HW configurations, see the Creating Nokia AirScale BTS FDD-LTE Configurations document. The AirScale SM Indoor is IP20 ingress protected and operates at the temperature range from -5 to +55 °C. The following functions are integrated in the ASIA:
Issue: 01 Draft
DN09237915
353
Descriptions of BTS site solution features
• • •
FDD-LTE16A, Feature Descriptions and Instructions
Cell-specific baseband processing Optical interfaces to radio units Status LEDs
The figure below presents the front view of the AirScale Capacity (ABIA). Figure 45
Front panel of the ABIA RF1
RF2
RF3
RF4
RF5
RF6
The ABIA plug-in units provides six optical RP3-01/CPRI interfaces to/from RFs. For more information, see the Nokia AirScale BTS Product Description document.
9.4.3 LTE2261 system impact LTE2261: AirScale Capacity ABIA impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features are required for Nokia AirScale System Module Indoor: • • •
LTE2114: AirScale Common ASIA LTE2261: AirScale Capacity ABIA (described in this document) LTE2262: AirScale Subrack AMIA
Impact on interfaces The LTE2261: AirScale Capacity ABIA feature has no impact on interfaces. Impact on network management tools The LTE2261: AirScale Capacity ABIA feature has no impact on network management tools. Impact on system performance and capacity New configurations are available. For more information, see the Creating Nokia AirScale BTS LTE Configurations document.
9.4.4 LTE2261 reference data LTE2261: AirScale Capacity ABIA requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements
354
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 278
Descriptions of BTS site solution features
LTE2261 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FDD-LTE16A
Not supported
Not supported
FL16A
Flexi Zone Controller
OMS
UE
Not supported Support not required
Support not required
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
NetAct Support not required
Support not required
Support not required
BTS faults and reported alarms There are no faults related to the LTE2261: AirScale Capacity ABIA feature. Measurements and counters There are no measurements or counters related to the LTE2261: AirScale Capacity ABIA feature. Key performance indicators There are no key performance indicators related to the LTE2261: AirScale Capacity ABIA feature. Parameters There are no parameters related to the LTE2261: AirScale Capacity ABIA feature. Sales information Table 279
LTE2261 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.5 LTE2262: AirScale Subrack AMIA Benefits, functionality, system impact, reference data of the feature The LTE2262: AirScale Subrack AMIA feature introduces indoor subrack for the next generation of a highly integrated System Module, called AirScale System Module Indoor. The AirScale Subrack AMIA provides high bandwidth interconnectivity between LTE2114: AirScale Common ASIA and LTE2261: AirScale Capacity ABIA plug-in units.
9.5.1 LTE2262 benefits The AirScale System Module Indoor is a successor of the Flexi Multiradio 10 System Module and it is further optimized for supporting LTE advanced features, such as Carrier Aggregation and Coordinated Multi-Point in high capacity system configurations. The LTE2262: AirScale Subrack AMIA feature provides the following benefits: • • •
Issue: 01 Draft
Enhanced capacity Enhanced connectivity Expanded possibilities in the same 3U form factor in indoor installations
DN09237915
355
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
9.5.2 LTE2262 functional description Nokia AirScale Subrack (AMIA) Nokia AirScale Subrack (AMIA) main properties: • • • • •
It supports up to two AirScale Common plug-in units It supports up to six AirScale Capacity plug-in units IP20 ingress protected Operating temperature range: from -5°C to +55°C It might be installed inside a 19-inch wide rack or cabinet
The AirScale Subrack AMIA includes: • • • •
Subrack frame Backplane for high bandwidth interconnect between AirScale Common and AirScale Capacity plug-in units Fans with changeable airflow direction Blind-units to prevent cooling airflow leakage
Nokia AirScale Subrack factory default consists of a subrack frame, one AirScale Common blind-unit and five AirScale Capacity blind-units as shown in Figure 46: AMIA AirScale Subrack (factory default).
356
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
Figure 46
AMIA AirScale Subrack (factory default)
Table 280
AMIA dimensions and weight Property
Value
Height
128 mm (5 in.)
Depth
400 mm (15.7 in.)
Width
447 mm (17.6 in.)
Weight
Empty: 5.1 kg (11.2 lb)
Dimensions orientation
height
With dummy panels: 6.8 kg (15 lb)
width
With all units: 23.9 kg (52.7 lb)
depth
For more information, see the Nokia AirScale Base Station Product Description document. Nokia AirScale System Module Indoor
Issue: 01 Draft
DN09237915
357
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
Nokia AirScale System Module Indoor consists of the following items: • • •
One AirScale Subrack (AMIA), including backplane for high bandwidth connectivity between processing plug-in units One or two AirScale Common (ASIA) plug-in units for transport interfacing and for centralized processing Up to six AirScale Capacity (ABIA) plug-in units for baseband processing and for optical interfaces with radio units
Figure 47
Nokia AirScale System Module Indoor in maximum configuration (2xASIA, 6xABIA)
AirScale Capacity ABIA
AirScaleSubrackAMIA
AirScale Common ASIA For supported HW configurations, see the Creating Nokia AirScale BTS FDD-LTE Configurations document.
9.5.3 LTE2262 system impact LTE2262: AirScale Subrack AMIA impact on features and system performance and capacity Interdependencies between features The following features are required for AirScale System Module Indoor: •
•
LTE2114: AirScale Common ASIA AirScale Subrack (AMIA) provides high bandwidth interconnectivity between LTE2114 and LTE2261. LTE2261: AirScale Capacity ABIA AirScale Subrack (AMIA) provides high bandwidth interconnectivity between LTE2261 and LTE2114.
Impact on interfaces The LTE2262: AirScale Subrack AMIA feature has no impact on interfaces. Impact on network management tools The LTE2262: AirScale Subrack AMIA feature has no impact on network management tools. Impact on system performance and capacity
358
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
The LTE2262: AirScale Subrack AMIA feature impacts system performance and capacity as follows: • • •
Enhanced capacity Expansion possibilities New configurations are available For more information, see the Creating Nokia AirScale BTS FDD-LTE Configurations document.
9.5.4 LTE2262 reference data LTE2262: AirScale Subrack AMIA requirements and sales information Requirements Table 281
LTE2262 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FDD-LTE 16A
Not supported
Not supported
FL16A
Flexi Zone Controller
OMS
UE
Not supported Support not required
Support not required
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
NetAct Support not required
Support not required
Support not required
There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE2262: AirScale Subrack AMIA feature. Sales information Table 282
LTE2262 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.6 LTE2335: Outdoor GNSS receiver FYGM Benefits, functionality, system impact, reference data, instructions of the feature The LTE2335: Outdoor GNSS receiver FYGM feature introduces the FYGM GNSS receiver to receive the Global Navigation Satellite Systems (GPS, GLONASS, Beidou) signal and provide the synchronization input to Flexi eNB system. FYGM can be deployed in both indoor and outdoor environments, and is compliant to IP65.
9.6.1 LTE2335 benefits The LTE2335: Outdoor GNSS receiver FYGM feature provides the following benefits: • • •
Issue: 01 Draft
Improved synchronization input. FYGM saves costs by using (or reusing) RF GPS antennas. Flexible mounting options available.
DN09237915
359
Descriptions of BTS site solution features
• •
FDD-LTE16A, Feature Descriptions and Instructions
Supported in both indoor and outdoor environments. Saved installation space and easy service engineering due to various applicability options.
9.6.2 LTE2335 functional description FYGM overview The FYGM is a small GNSS receiver for receiving Global Navigation Satellite System signal from an external RF GNSS antenna, and providing synchronization input to Flexi eNB or Nokia AirScale System Module systems. FYGM provides signal conversion from the RF GPS antenna to 1PPS+TOD that can be used for system module synchronization input. The RF antenna can be shared with other GNSS receivers. Flexible mounting options are supported: • • • •
both indoor and outdoor into free FSMF slot on the FSMx side as a stand-alone on a wall, pole, or mast
The FYGM receiver provides an in-line solution between the RF GNSS antenna (at site) and the System Module Sync In port. FYGM is GNSS capable (supporting GPS, GLONASS, and Beidou), with the default constellation- GPS + GLONASS. GNSS operation mode selects how many and which GNSS are used for BTS synchronization: • •
Multi-GNSS operation mode which allows using RF signals from two GNSS for synchronizing the BTS. GNSS operation mode which allows using a dedicated GNSS for the final synchronization of the BTS.
As the FYGM sends sequentially the ToD information to the BTS, the BTS is able to provide a continuous timing reference to the radio interface. The BTS can also provide the exact UTC time for O&M purposes. The FYGM module is compliant with TSIP protocol (which is used for control communication from BTS to GNSS receiver) and backward compatible with the features and SW functioning of all FYGx devices. With the exception of FYGG and FYGE, the FYGM can replace all FYGx. Additionally, it is compatible with existing legacy Sync-In port and plug-and-play to existing synchronization features in AirScale SM, FSIH and FSMF. Using the FYGM GNSS receiver, the BTS is able to synchronize to a highly accurate timing reference signal of several Global Navigation Satellite Systems (GPS, GLONASS, and Beidou). The FYGM GNSS receiver can receive the RF signals from one or from two Global Navigation Satellite Systems in parallel. Using the GUI (NetAct, BTSSM) the operator has the possibility to select which GNSS(s) the BTS will synchronize to. Several operation modes can be selected, each defining with which further GNSS(s) the operator wants the FYGM to communicate. If needed, the FYGM GNSS receiver can be upgraded from the BTS O&M. External characteristics The FYGM receiver has: •
360
A Deutche IMC connector
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• • •
Descriptions of BTS site solution features
DC input from HDMI interface 15 V 125 mA Power on and status LEDs A grounding terminal
The FYGM can provide 5V DC LNA power supply to the antenna. It can be connected directly to the GPS/GNSS antenna or via the GNSS splitter, sharing the antenna with other GNSS receivers. FYGM delivery package includes the HDMI-12pin cable and reuses existing Nokia products like GPS antennas, over-voltage protection solutions, cables, GNSS splitters.
9.6.3 LTE2335 system impact LTE2335: Outdoor GNSS receiver FYGM impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features There are no interdependencies between the features. Impact on interfaces The LTE2335: Outdoor GNSS receiver FYGM feature has no impact on interfaces. Impact on network management tools The LTE2335: Outdoor GNSS receiver FYGM feature has no impact on network management tools. Impact on system performance and capacity The LTE2335: Outdoor GNSS receiver FYGM feature has no impact on system performance or capacity.
9.6.4 LTE2335 reference data LTE2335: Outdoor GNSS receiver FYGM requirements, alarms, faults, measurements and counters, key performance indicators, parameters, and sales information Requirements Table 283
LTE2335 LTE FDD hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Not supported Support not required
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL16A
UE Support not required
NetAct Hardware management
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
Support not required
Support not required
Software management
Alarms
Issue: 01 Draft
DN09237915
361
Descriptions of BTS site solution features
Table 284
FDD-LTE16A, Feature Descriptions and Instructions
Alarms modified by LTE2335
Alarm ID
Alarm name
7651
BASE STATION OPERATION DEGRADED
7652
BASE STATION NOTIFICATION
For fault descriptions, see the FDD-LTE BTS Alarms and Faults document. BTS faults and reported alarms Table 285
New BTS faults introduced by LTE2335
Fault ID
4124
Fault name Alarm ID
EFaultId_GpsReceiverNoStor edPositionAl
Fault ID
4122
7108
BASE STATION SYNCHRONIZATION PROBLEM
7651
BASE STATION OPERATION DEGRADED
7652
BASE STATION NOTIFICATION Reported alarms
Alarm ID
EFaultId_GpsReceiverNotTra ckingSatellitesAl
Alarm name
7651
BASE STATION OPERATION DEGRADED
7652
BASE STATION NOTIFICATION
Fault name
Reported alarms Alarm ID
EFaultId_GpsReceiverSurvey InProgressAl
Table 286
7108
Alarm name
BASE STATION SYNCHRONIZATION PROBLEM
Existing faults related to LTE2335Parameters
Fault ID
4269
Alarm name
Fault name
Fault ID
4123
Reported alarms
Fault name
Reported alarms Alarm ID
EFaultId_SwBuildSignatureM issingAl
7106
Alarm name
SINGLE RAN BASE STATION PROBLEM
For fault descriptions, see the FDD-LTE BTS Alarms and Faults document. Measurements and counters Table 287
Existing counters related to LTE2335
Counter ID 8039
362
Counter name LTE GNSS
Measurement M8039
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
For counter descriptions, see the LTE Performance Measurements and Key Performance Indicators document. Key performance indicators There are no key performance indicators related to the LTE2335 feature. Parameters Table 288
Modified parameters introduced by LTE2335 Full name
Abbreviated name
Managed object
GNSS Receiver Control Mode
gnssControlMode
GNSSE
GNSS Constellation Mode
gnssConstellationMode
GNSSE
For parameter descriptions, see the FDD-LTE BTS Parameters document. Sales information Table 289
LTE2335 sales information
Product structure class
License control
Activated by default
Basic Software (BSW)
-
No
9.7 LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator Benefits, functionality, system impact, reference data, instructions of the feature The LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator feature introduces site configuration where 2 operators have dedicated LTE and GSM System Modules controlling operator dedicated RF units in the LTE-GSM RF sharing mode (for example 1800 band), but also controlling shared RF units in the dedicated LTE mode (for example 800 band).
9.7.1 LTE2387 benefits The LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator feature provides the following benefits: • • •
Customer can roll-out radio unit optimized solution for the MORAN cases where the RF unit HW must be minimized as much as possible. Better flexibility in HW utilization. One radio unit can operate in different (dedicated or shared) modes.
9.7.2 LTE2387 functional description Functional overview
Issue: 01 Draft
DN09237915
363
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
The LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator feature supports site configuration where 2 operators have dedicated LTE and GSM System Modules controlling operator dedicated RF units in the LTE-GSM RF sharing mode (for example 1800 band), but also controlling shared RF units in the dedicated LTE mode (for example 800 band). One RF Module can either be operated in: LTE dedicated mode GSM dedicated mode LTE-LTE RF sharing Classical LTE-GSM RF sharing
• • • •
This feature supports the following multi-operator cases/solutions: LTE MORAN GSM MOBSS
• •
This feature combines the LTE-LTE RF sharing (LTE1829) and LTE-GSM RF sharing (LTE447, LTE2079, LTE1895). Exemplary configurations Figure 48
Exemplary LTE2387 cabling configuration - Example 1
Operator1
Operator1+2
Operator2
FlexiHW 2.3(FXEB)
FlexiHW 3.2(FRMF)
FlexiHW 2.3(FXEB)
G1800444@15W,C-typeconfig LTE1800111@15MHz 2x40W,H-typeconfig
LTE800222@10MHz MIMO2x30W I-typeconfig(1carrierper)
G1800444@15W,C-typeconfig LTE1800111@15MHz 2x40W,H-typeconfig
2Tx&Rx Tx&Rx
Tx&Rx
Tx&Rx
2Tx&Rx
2Tx&Rx 2Tx&Rx
2Tx&Rx
Tx&Rx
Tx&Rx
2 1
RFM3Tx
Tx&Rx
3
Tx&Rx
Tx&Rx
3
2
2
1
RFM3Tx
6Gbpslinks LTEFSMF
1
PPS/ToD FromGPS LTEFSMF
FSMF
FSMF
SyncHubMaster
SyncHubSlave
GSM FSMF
GSM FSMF
FSMF
FSMF
SyncHubSlave
364
Tx&Rx
3
1
RFM6Tx
Tx&Rx
RFM3Tx
Tx&Rx
2
2 1
RFM3Tx
Tx&Rx
2Tx&Rx
3
3
SyncHubSlave
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Figure 49
Descriptions of BTS site solution features
Exemplary LTE2387 cabling configuration - Example 2
Operator1
Operator1+2
FlexiHW 2.3(FXEB)
FlexiHW 3.2(FRMF)
G1800444@15W,C-typeconfig LTE1800111@15MHz 2x40W,H-type
LTE800222@10MHz MIMO2x30W I-typeconfig(1carrierper)
2Tx&Rx Tx&Rx
Tx&Rx
Tx&Rx
2Tx&Rx
2Tx&Rx 2Tx&Rx
2Tx&Rx
2Tx&Rx
3
3
2
2 1
RFM3Tx
Tx&Rx
Tx&Rx
1
RFM6Tx
Tx&Rx
3 2 1
RFM3Tx
6Gbpslinks
LTEFSMF
PPS/ToD FromGPS LTEFSMF
FSMF
FSMF
SyncHubSlave
SyncHubMaster
GSM FSMF FSMF
SyncHubSlave
The list of RF Modules from Flexi HW 2.3 and Flexi HW 3.2 can be found in the LTE Base Stations Supported Configurations document. HW support Pre-condition: The following HW is supported with this feature: •
System Modules: – –
•
RF Modules: – – – – – – – – – – – – – –
Issue: 01 Draft
LTE: FSMF+FBBA/C+FBBC (second extension card is optional) GSM: FSMF
FXEB Flexi RF Module 3TX 1800 Triple 90W* FXDB Flexi RF Module 3TX 900* FXCB Flexi RF Module 3TX 850 FXFC Flexi RF Module 3TX 1900 FXCE Flexi RF Module 3TX 850 FXED Flexi RF Module 6TX 1800 FRME Flexi RF Module 6TX 800 FRGU Flexi RF Module 6TX 2100 FRHF Flexi RF Module 6TX 2600* FRHC Flexi RF Module 6TX 2600* FRMC Flexi RF Module 6TX 800* FRPB Flexi RF Module 6TX 700* FRPA Flexi RF Module 6TX 700* FRII Flexi RF Module 6TX 1700/2100
DN09237915
365
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
Sync Hub Direct Forward RF Sharing Transfer of phase/time synchronization between system modules sharing a RF module is done with the use of 1PPS & ToD signals and interfaces. The ability to serve as head element of a Sync Hub Direct The used synchronization feature LTE1710 Sync Hub Direct Forward also allows to serve as head element of a Sync Hub Direct Forward chain or as intermediate element shall be independent of the RAT of a BTS. However, with LTE-LTE & LTE-GSM RF sharing feature, LTE must be the head element of a Sync Hub Direct Forward chain. The RP3-01 connection between system modules involved in RF sharing is still required to perform RF sharing topology scan to build a communication among RF sharing elements.
9.7.3 LTE2387 system impact LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator feature impacts the following features: •
LTE1829: Inter eNB RF Sharing Requirement is to make this feature RF HW agnostic but HW has to be part of LTE1829 or related CRL adding HW variants.
Impact on interfaces The LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator feature has no impact on interfaces. Impact on network management tools The LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator feature has no impact on network management tools. Impact on system performance and capacity New multi-operator configurations are available.
9.7.4 LTE2387 reference data LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator requirements, alarms and faults, measurements and counters, KPIs, parameters, and sales information Requirements Table 290
LTE2387 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Nokia AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
Not supported
Not supported
Not supported
NetAct
MME
SAE GW
UE
Not supported LTE OMS16A
366
Flexi Multiradio 10 BTS
Support not required
DN09237915
NetAct 16.8
Support not required
Support not required
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
Alarms There are no alarms related to the LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator feature. BTS faults and reported alarms There are no faults related to the LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator feature. Measurements and counters There are no measurements or counters related to the LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator feature. Key performance indicators There are no key performance indicators related to the LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator feature. Parameters There are no parameters related to the LTE2387: Classical LTE(MORAN)-GSM(MOBSS) RF sharing with one SM per operator feature. Sales information Table 291
LTE2387 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
9.8 LTE2516: FRIJ AirScale RRH 4T4R B66 160 W Benefits, functionality, system impact, reference data of the LTE2516 feature The LTE2516: FRIJ AirScale RRH 4T4R B66 160 W feature introduces the FRIJ AirScale RRH 4T4R B66 160 W (uplink: 2110-2200 MHz, downlink: 1710-1780 MHz).
9.8.1 LTE2516 benefits The LTE2516: FRIJ AirScale RRH 4T4R B66 160 W feature provides the following benefits: • • • • • • • •
Four Power Amplifiers that enable supporting one sector with up to 4x40 W 4TX MIMO output power at the BTS antenna connectors. FRIJ RRH supports 1 or 2 sector operation It supports 2x2x40 W that allows using the entire spectrum split over 4-pipes, each 2T2R segment to allow wider Occupied Bandwidth use. Smaller size and weight compared to prior generation. New, industrial designed outer shell and book mount design. IP65 environmental protection class. Its bandwidth filter supports the whole 3GPP band 66 (70/90 MHz). Optional fan module for additional mounting schemes are available.
9.8.2 LTE2516 functional description Main properties FRIJ is a 4-pipe RRH optimized for distributed macro BTS installations.
Issue: 01 Draft
DN09237915
367
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
FRIJ AirScale RRH 4T4R B66 160 W main properties: • • • • • •
It supports 3GPP FDD bands 4, 10 and Band 66, with 10 W, 15 W, 20 W, 30 W, 40 W output power per Tx Support of modulation schemes up to QAM64 (UL) Support of modulation schemes up to QAM256 (DL) RF Sharing Bandwidth FDD-LTE: 5 MHz, 10 MHz, 15 MHz, 20 MHz, 2 x 20 MHz RF Sharing Bandwidth: WCDMA 3.8 MHz, 4.2 MHz, 5 MHz Supported RF frequency FDD: downlink: 2110-2200 MHz, uplink: 1710-1780 MHz External interfaces on band A: – – – – – –
• • • • • •
4 TX/RX ports with 4.3-10 connector EAC with USB3 connector (MDR 36 requires an adapter cable) 3 optical RF ports (SFP slots) OBSAI 6Gbps links One DC IN connector RET with 8-pin circular
-40°C to +40°C with convection cooling Weight: 22 kg Volume: 25 l To enable full output power, one power license per TX pipe is required Supported mounting options: pole, wall Compatible with RAS mounting: book, horizontal (with optional fan module)
Filter BW is 90 MHz downlink, 70 MHz uplink. 5% of sites would require the external filter to be compliant with FCC rules to protect federal spectrum from AWS emissions. Dimensions and weight Table 292
FRIJ dimensions and weight Property
Height
Value With cover: 600 mm (23.6 in.) With cover and fan: 630.2 mm (24.8 in.)
Depth
Dimensions orientation Dimensions orientation in vertical mount with cover
With cover and handle: 409.5: mm (16.1 in.) With cover, fan and handle: 409.5 mm (16.1 in.) width
Width
With cover: 126 mm (5.0 in.) With cover and fan: 126 mm (5.0 in.)
Weight
21 kg (46.3 lbs)
Volume
With cover: 28 l
height depth
Without cover: 20.4 l
368
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 292
Descriptions of BTS site solution features
FRIJ dimensions and weight (Cont.) Property
Value
Dimensions orientation Dimensions orientation in horizontal mount with cover and fan
width height depth
For more information, see Nokia AirScale Radio Description. RF Sharing Configurations For implementation and configurations for RF sharing on the system level, refer to SW release feature roadmap and release documentation. FRIJ HW is prepared for LTEWCDMA RF sharing. Supported BTS configurations Supported BTS configurations: • •
For the single carrier LTE: all released BTS configurations valid for RRH 4Tx RF units For multi-carrier LTE: released LTE BTS configurations supporting dual carrier and multi-carrier configurations as well as inter eNB RF sharing configurations
The same band combines: • • • •
Four ports of the RRH to two ports AWS-1 frequency and AWS-3 frequency to double the power (~75 W) in a 2-pipe configuration Max instantaneous BW is: downlink: 90 MHz, uplink: 70 MHz Max four carriers per pipe, the maximum occupied bandwidth is 40 MHz
9.8.3 LTE2516 system impact LTE2516: FRIJ AirScale RRH 4T4R B66 160 W impact on features and system performance and capacity Interdependencies between features The LTE2516: FRIJ AirScale RRH 4T4R B66 160 W feature is impacted by the following features: • • •
Issue: 01 Draft
LTE115: Cell Bandwidth - 5 MHz It enables LTE 5 MHz carriers. LTE114: Cell Bandwidth - 10 MHz It enables LTE 10 MHz carriers. LTE113: Cell Bandwidth - 15 MHz It enables LTE 15 MHz carriers.
DN09237915
369
Descriptions of BTS site solution features
• •
• • • •
• • •
FDD-LTE16A, Feature Descriptions and Instructions
LTE112: Cell Bandwidth - 20 MHz It enables LTE 20 MHz carriers. LTE614: Distributed Site With LTE614 FRIJ, it might be used in distributed sites with up to 23 km fiber length to the system module. LTE977: RF chaining With LTE977 FRIJ, it supports chains of up to 4 radio units. LTE1891: eNode B power saving - Micro DTX It enables using the Micro DTX feature. LT2508: BTS Embedded Power Meter for Energy Efficiency Monitoring It enables using the energy metering feature. LTE1103: Load based Power Saving for multi-layer networks or LTE1203: Load based Power Saving with Tx path switching off It enables using the PA shutdown feature. LTE2149: Supplemental downlink carrier It enables using an extra 20 MHz in downlink spectrum. LTE2824: Extended frequency band range It supports extended parameter range for band 66. LTE3096: Supported RAS Installation options in FL16A Release With LTE3096 RAS installation options are defined.
Impact on interfaces The LTE2516: FRIJ AirScale RRH 4T4R B66 160 W feature has no impact on interfaces. Impact on network management tools The LTE2516: FRIJ AirScale RRH 4T4R B66 160 W feature has no impact on network management tools. Impact on system performance and capacity The LTE2516: FRIJ AirScale RRH 4T4R B66 160 W feature impacts system performance and capacity as follows: •
New configurations are available.
9.8.4 LTE2516 reference data LTE2516: FRIJ AirScale RRH 4T4R B66 160 W requirements and sales information Requirements Table 293 System release FDD-LTE 16A Flexi Zone Controller
LTE2516 hardware and software requirements Flexi Multiradio BTS FL16A
Not supported
OMS
UE
Not Applicable LTE OMS16A
370
Flexi Multiradio 10 BTS
Support not required
DN09237915
Nokia AirScale BTS FL16A NetAct NetAct 16.8
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
Support not required
Support not required
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE2516: FRIJ AirScale RRH 4T4R B66 160 W feature. Sales information Table 294
LTE2516 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.9 LTE2517: AirScale HW capacity activation licence Benefits, functionality, system impact, reference data, instructions of the feature The LTE2517: AirScale HW capacity activation licence feature introduces the software capacity enabling key for AirScale System Module.
9.9.1 LTE2517 benefits The LTE2517: AirScale HW capacity activation licence feature provides the possibility to utilize baseband cost according to required cell capacity.
9.9.2 LTE2517 functional description For basic capacity (50 %) of AirScale Capacity Indoor plug-in unit, one hardware activation license is needed. Full baseband unit capacity requires two hardware activation licenses. Therefore, up to 12 hardware activation licenses (full system module capacity available from LTE17 releases) are needed for full 6 capacity baseband card configuration in one AirScale System Module Indoor. Feature is controlled with the useFullCapacity parameter (activated by default). The eNB requests respective license keys based on baseband capacity utilization determined by the amount of the used up cells capacity.
9.9.3 LTE2517 system impact LTE2517 impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be active before activating the LTE2517 feature: • • • •
LTE2593: SW License Management in LTE LTE2114: AirScale Common ASIA LTE2262: AirScale Subrack AMIA LTE2261: AirScale Capacity ABIA
Impact on interfaces The LTE2517 feature has no impact on interfaces. Impact on network management tools The LTE2517 feature has no impact on network management tools.
Issue: 01 Draft
DN09237915
371
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
Impact on system performance and capacity The LTE2517: AirScale HW capacity activation licence feature provides the possibility to utilize baseband cost according to required cell capacity.
9.9.4 LTE2517 reference data LTE2517: AirScale HW capacity activation licence requirements, alarms and faults, measurements and counters, KPIs, parameters, and sales information Requirements Table 295
LTE2517 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FDD-LTE 16A
Not supported
Not supported
FL16A
Flexi Zone Controller
OMS
UE
Not supported LTE OMS16A
Support not required
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
NetAct NetAct 16.8
Support not required
Support not required
Alarms There are no alarms related to the LTE2517 feature. BTS faults and reported alarms Table 296
New BTS faults introduced by LTE2517
Fault ID
4349
Fault name
Reported alarms Alarm ID
Cell Shutdown Due To Baseband Capacity License Limit
7658
Alarm name
BASE STATION LICENSE LIMITATION
Measurements and counters There are no measurements or counters related to the LTE2517 feature. Key performance indicators There are no key performance indicators related to the LTE2517 feature. Parameters Table 297
New parameters introduced by LTE2517 Full name
Abbreviated name
Use Full Capacity
useFullCapacity
Managed object BBMOD
Sales information Table 298
LTE2517 sales information
Product structure class Basic software (BSW)
372
License control Unlicensed
DN09237915
Activated by default Yes
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
9.10 LTE2605: 4RX Diversity 20MHz Optimized Configurations Benefits, functionality, system impact, reference data, instructions of the feature The LTE2605: 4RX Diversity 20MHz Optimized Configurations feature introduces BTS configurations which support three cells with 4 Rx diversity on 15 or 20MHz within a single basic cell set.
9.10.1 LTE2605 benefits The LTE2605: 4RX Diversity 20MHz Optimized Configurations feature enables for buiding dual band or triple band configurations with 3-sector 15/20MHz on single Flexi System Module 10.
9.10.2 LTE2605 functional description The existing BTS configuration features for support of 4Rx diversity require at least one FBBA or FBBC extension module (extended cell set) for 15 or 20MHz LTE carriers in 3 sectors. With the LTE2605: 4RX Diversity 20MHz Optimized Configurations feature it is possible to create configurations for 2x2 MIMO with 4Rx diversity for up to 3 cells of 15 or 20 MHz in one basic cell set. No additional baseband extension modules FBBA or FBBC are needed. This feature is an optional feature which is activated/deactivated via an O&M parameter per eNB. For each cell using this new optimized 4Rx implementation, one license key is required.
9.10.3 LTE2605 system impact LTE2605: 4RX Diversity 20MHz Optimized Configurations impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be activated before activating the LTE2605: 4RX Diversity 20MHz Optimized Configurations feature: • •
LTE72: 4-way RX Diversity LTE980: IRC for 4 RX paths
The following features must be deactivated before activating the LTE2605: 4RX Diversity 20MHz Optimized Configurations feature: • • •
LTE568: DL adaptive closed loop MIMO (4x2) LTE1691: Uplink Intra-eNB CoMP (4Rx) LTE1987: Downlink Adaptive Closed Loop SU MIMO (4x4)
For more information on BTS configurations supported with LTE2605, see the Creating LTE Configurations document.
Issue: 01 Draft
DN09237915
373
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
Impact on interfaces The LTE2605: 4RX Diversity 20MHz Optimized Configurations feature has no impact on interfaces. Impact on network management tools The LTE2605: 4RX Diversity 20MHz Optimized Configurations feature has no impact on network management tools. Impact on system performance and capacity The LTE2605: 4RX Diversity 20MHz Optimized Configurations feature has no impact on system performance or capacity.
9.10.4 LTE2605 reference data LTE2605: 4RX Diversity 20MHz Optimized Configurations requirements and sales information Requirements Table 299
LTE2605 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
FDD-LTE 16A
not supported
Flexi Zone Controller
OMS
UE
not applicable
LTE OMS16A
not supported
FL16A
Nokia AirScale
Flexi Zone Micro BTS
Flexi Zone Access Point
not supported
not supported
not supported
NetAct
MME
SAE GW
not supported
not supported
NetAct 16.8
The LTE2605: 4RX Diversity 20MHz Optimized Configurations feature requires BTS configurations with 4Rx support. Alarms There are no alarms related to the LTE2605: 4RX Diversity 20MHz Optimized Configurations feature. BTS faults and reported alarms There are no faults related to the LTE2605: 4RX Diversity 20MHz Optimized Configurations feature. Commands There are no commands related to the LTE2605: 4RX Diversity 20MHz Optimized Configurations feature. Measurements and counters There are no measurements or counters related to the LTE2605: 4RX Diversity 20MHz Optimized Configurations feature. Key performance indicators There are no key performance indicators related to the LTE2605: 4RX Diversity 20MHz Optimized Configurations feature. Parameters The feature must be activated by parameter actOptimizedBbUsage. Additionally cellsWithOptBbCalcApplied is read only parameter that shows how many cells are actually using this feature Sales information
374
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 300
Descriptions of BTS site solution features
LTE2605 sales information
Product structure class
License control
Application software (ASW)
Pool license
Activated by default No
9.11 LTE2609: Dual Carrier Support LTE1.4 and LTE3 Benefits, functionality, system impact, reference data of the feature The LTE2609: Dual Carrier Support LTE1.4 and LTE3 feature introduces two LTE carriers - of which one has 1.4MHz or 3MHz BW - on a single radio unit.
9.11.1 LTE2609 benefits The LTE2609: Dual Carrier Support LTE1.4 and LTE3 feature provides the following benefits: • •
Efficient usage of narrow LTE spectrum chunks becomes possible. Minimum carrier spacing allows to reduce the guard band in case of adjacent dual carriers.
9.11.2 LTE2609 functional description This feature extends the existing feature LTE2019: Advanced Dual Carrier Operation within same RF Unit with support of narrow LTE carriers with 1.4 MHz or 3 MHz carrier bandwidth. In all dual carrier configurations defined by LTE2019 for 2Tx/2Rx with shared antenna, one 5MHz carrier can be replaced with a 1.4 MHz or a 3 MHz carrier. Additionally the combination of 1.4 MHz + 3 MHz is supported as well. For carriers adjacent to each other, the minimum carrier spacing allows for fit two carriers into slightly less spectrum as given by the sum of the nominal bandwidth of both carriers. Minimum spacing supported (distance between center frequency of both carriers): • • • • • • • • •
10.5 MHz for 3 + 20 MHz 8.4 MHz for 3 + 15 MHz 6.0 MHz for 3 + 10 MHz 3.9 MHz for 3 + 5 MHz 3.0 MHZ for 1.4 + 5 MHz 9.6 MHz for 1.4 + 20MHz 7.5 MHz for 1.4 + 15MHz 5.1 MHz for 1.4 + 10MHz 2.1 MHz for 1.4 + 3 MHz
For non adjacent carrier configurations, the max carrier spacing is limited by the instantaneous bandwidth that is supported by the used radio units.
9.11.3 LTE2609 system impact LTE2609: Dual Carrier Support LTE1.4 and LTE3 impact on features, interfaces, network management tools, and system performance and capacity
Issue: 01 Draft
DN09237915
375
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
Interdependencies between features The following features must be activated before activating the LTE2609: Dual Carrier Support LTE1.4 and LTE3 feature: • •
LTE116: Cell Bandwidth - 3 MHz LTE117: Cell Bandwidth - 1.4 MHz
For more information on BTS configurations supported with LTE2609, see the Creating LTE Configurations document. Impact on interfaces The LTE2609: Dual Carrier Support LTE1.4 and LTE3 feature has no impact on interfaces. Impact on network management tools The LTE2609: Dual Carrier Support LTE1.4 and LTE3 feature has no impact on network management tools. Impact on system performance and capacity The LTE2609: Dual Carrier Support LTE1.4 and LTE3 feature has no impact on system performance or capacity.
9.11.4 LTE2609 reference data LTE2609: Dual Carrier Support LTE1.4 and LTE3 requirements and sales information Requirements Table 301
LTE2609: Dual Carrier Support LTE1.4 and LTE3 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
FDD-LTE 16A
not supported
Flexi Zone Controller
OMS
UE
not supported
LTE OMS16A
not supported
FL16A
Nokia AirScale
Flexi Zone Micro BTS
Flexi Zone Access Point
not applicable
not supported
not supported
NetAct
MME
SAE GW
not supported
not supported
NetAct 16.8
The LTE2609: Dual Carrier Support LTE1.4 and LTE3 feature requires FSMF module and any radio unit that supports 3MHz respecively 1.4MHz LTE carriers and allowes dual carrier operation. There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE2609: Dual Carrier Support LTE1.4 and LTE3 feature. Sales information Table 302
LTE2609 sales information
Product structure class Application software (ASW)
376
License control Pool license
DN09237915
Activated by default Yes
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
9.12 LTE2610: Support for classical WCDMA/LTE RFsharing on 2Tx/2Rx RRH FHDB Benefits, functionality, system impact, reference data of the feature The LTE2610: Support for classical WCDMA/LTE RF-sharing on 2Tx/2Rx RRH FHDB feature introduces new WCDMA-LTE RF sharing configurations with 2Tx/2Rx Remote Radio Head (RRH) FHDB.
9.12.1 LTE2610 benefits The LTE2610: Support for classical WCDMA/LTE RF-sharing on 2Tx/2Rx RRH FHDB feature provides the following benefit: the option of using FHDB in WCDMA-LTE RF sharing can make more flexible configurations available.
9.12.2 LTE2610 functional description This feature extends the existing WCDMA-LTE RF sharing functionality to configurations with 2Tx/Rx FHDB. Table 303
Configurations introduced by the feature
Cells/Sectors WCDMA: up to 3+3+3 LTE: 1+1+1
Configurations type
LTE BW
WCDMA: 1Tx/2Tx or Up to 5 MHz 2Tx/2Rx, SIMO/VAM (A/I-type)
System Module WCDMA: FSME or FSMF
RF Modules (shared) FHDB (1-3 sectors)
LTE: FSMF
LTE: 2Tx/2Rx, MIMO (I-type) WCDMA: up to 2+2+2 LTE: 1+1+1
WCDMA: 1Tx/2Tx or Up to 10 MHz 2Tx/2Rx, SIMO/VAM (A/I-type)
WCDMA: FSME or FSMF
FHDB (1-3 sectors)
LTE: FSMF
LTE: 2Tx/2Rx, MIMO (I-type)
Additional dedicated LTE bands are supported as defined in LTE2080: LTE-WCDMA RF sharing with full FBBC support. For more information, see the Flexi Multiradio BTS RF Sharing Released Configurations document.
9.12.3 LTE2610 system impact LTE2610 impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features
Issue: 01 Draft
DN09237915
377
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
The following features must be activated before activating the LTE2610: Support for classical WCDMA/LTE RF-sharing on 2Tx/2Rx RRH FHDB feature: • •
RAN2126: RF Sharing WCDMA - LTE LTE435: RF Sharing WCDMA - LTE
Impact on interfaces The LTE2610: Support for classical WCDMA/LTE RF-sharing on 2Tx/2Rx RRH FHDB feature has no impact on interfaces. Impact on network management tools The LTE2610: Support for classical WCDMA/LTE RF-sharing on 2Tx/2Rx RRH FHDB feature has no impact on network management tools. Impact on system performance and capacity New configurations are available. For more information, see the Flexi Multiradio BTS RF Sharing Released Configurations document.
9.12.4 LTE2610 reference data LTE2610 requirements, alarms and faults, measurements and counters, KPIs, parameters, and sales information Requirements Table 304
LTE2610 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE16A
Not supported
Flexi Zone Controller
OMS
Support not required
Flexi Nokia Multiradio 10 AirScale BTS BTS FL16A
Planned for later releases
UE
LTE OMS16A
Support not required
Flexi Zone Micro BTS
Not supported Not supported
NetAct NetAct 16.8
Flexi Zone Access Point
MME Support not required
SAE GW Support not required
There are no alarms, measurements and counters, key performance indicators, parameters related to the LTE2610: Support for classical WCDMA/LTE RF-sharing on 2Tx/2Rx RRH FHDB feature. Sales information Table 305
LTE2610 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.13 LTE2637: Quad Carrier on Single RF Unit Benefits, functionality, system impact, reference data of the feature
378
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
The LTE2637: Quad Carrier on Single RF Unit feature introduces 3 or 4 LTE carriers in the same band supported on a single RF unit. The total possible LTE carrier bandwidth is up to 40MHz. A 2 x 2 MIMO, some configurations also with 4 RX diversity are supported..
9.13.1 LTE2637 benefits The LTE2637: Quad Carrier on Single RF Unit feature allows the operators to use scattered chunks of spectrum with minimum investment in radio units and antennas. The following benefits are provided: • •
3 or 4 LTE carriers in the same band are supported on a single RF unit. A total LTE carrier bandwidth of up to 40MHz is possible.
9.13.2 LTE2637 functional description This feature allows for configuring up to 4 LTE carriers on a single RF unit per sector. Additionally, a special configuration for two sectors with two carriers on each sector is supported. Either of the Remote Radio Head units with 4 Tx pipes or RF Modules with 6Tx pipes can be used. One unit is required per sector. Four pipes are in use on/in both RF types. The Tx carriers are distributed to the 4 pipes, thus a single pipe can support up to: • • •
one 15 or 20MHz Tx carrier. one 5/10/15/20 MHz Tx carrier plus one 5/10 MHz Tx carrier. one 5/10MHz Tx carrier plus two 5MHz Tx carriers.
The maximum available power per pipe is shared by up to 3 carriers assigned to the same pipe. Power levels for each carrier can differ by up to 6dB based on power spectral density. The following carrier bandwidth combinations are supported in a 3-sector configuration on a Flexi Multirado 10 System Module: • •
Max. 4 carriers: 5/10MHz + 5/10MHz + 5/10MHz + 5/10MHz in 2Tx/2Rx This configuration is served by one extended cell set. Max. 3 carriers: 15/20MHz + 5/10MHz + 5/10MHz: – –
•
in 2Tx/4Rx: served by one XL cell set in 2Tx/2Rx: served by one extended cell set
Max. 4 carriers: 15/20MHz + 5/10MHz + 5MHz + 5MHz in 2Tx/2Rx This configuration is served by one XL cell set.
9.13.3 LTE2637 system impact LTE2637: Quad Carrier on Single RF Unit impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features
Issue: 01 Draft
DN09237915
379
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
The LTE2605: 4Rx Diversity 20MHz Optimized Configurations feature must be enabled for using the 2Tx/4Rx configurations before activating the LTE2637: Quad Carrier on Single RF Unit feature. UL CoMP for 4 Rx cannot be used with these configurations. No concurrent RF sharing is possible with the LTE2637: Quad Carrier on Single RF Unit feature. For more information on BTS configurations supported with LTE2637, see the Creating LTE Configurations document. Impact on interfaces The LTE2637: Quad Carrier on Single RF Unit feature has no impact on interfaces. Impact on network management tools The LTE2637: Quad Carrier on Single RF Unit feature has no impact on network management tools. Impact on system performance and capacity The LTE2637: Quad Carrier on Single RF Unit feature has no impact on system performance or capacity.
9.13.4 LTE2637 reference data LTE2637: Quad Carrier on Single RF Unit requirements and sales information Requirements Table 306
LTE2637 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
Not supported
Not supported
Not supported
NetAct
MME
SAE GW
UE
Not supported LTE OMS16A
Support not required
NetAct 16.8
Support not required
Support not required
The feature needs to be activated by setting LNBTS:actMultipleCarrier to the appropriate value. There are no alarms, measurements and counters, key performance indicators, parameters related to the LTE2637: Quad Carrier on Single RF Unit feature. Sales information Table 307
LTE2637 sales information
Product structure class Application software (ASW)
License control Pool license
Activated by default No
9.14 LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W Benefits, functionality, system impact, reference data of the feature
380
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
The LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W feature introduces the Flexi Multiradio RF Module (FRSA) for 3GPP band 32 at 1450 MHz in TX and 3GPP band 20 at 800 MHz in RX (uplink: 832 - 862 MHz, downlink: 1452 - 1492 MHz). FRSA has six power amplifiers enabling it to support one, two or three sectors with an output power of up to 60+60 Watts 2TX MIMO at the BTS antenna connectors.
9.14.1 LTE2650 benefits The LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W feature provides the following benefits: • • • • • • • • • • • •
The most cost-efficient and compact 3-sector BTS Site Industry leading RF integration level 3-sector RF in one outdoor IP65 box Low power consumption and OPEX Can be used as a feederless site with one DC and 1...2 optical cables A 2TX div or 2TX MIMO for three sectors can be built with a single RF Module One 3-sector module providing a more cost effective solution than three RRHs in feederless installations HW prepared to support one powerful sector RRH with 4x60 W 4TX MIMO with 4RX Reduced weight Reduced wind load Wide operating temperature range: -35°C - +55°C (-31°F - +131°F) without solar load 1/3 of DC and 2/3 of optical cabling compared to a site with an RRH
9.14.2 LTE2650 functional description The FRSA module supports 3GPP band 32 at 1450 MHz in TX and 3GPP band 20 at 800 MHz in RX. It provides an output of 6x60 W at the antenna connector. TX bandwidth is 40 MHz and RX bandwidth is 30 MHz. The main features of the FRSA are as follows: • • • • • •
3U high with Flexi platform mechanics EAC port Optical chaining supported by HW, three optical connectors with up to 6 Gbit/s interfaces AISG2.0 antenna tilt support with external connector (RS485) Ability to be used in feederless BTS sites (optical and DC cable up to 200 m) TX typical output power tolerance ≤ +-0.8dB over full TX RF bandwidth with ambient temperature -35°C (-31°F) to +55°C (+131°F)
The following are some basic LTE configurations: • • •
1, 1+1 or 1+1+1 LTE cells @ max 20 MHz LTE bandwidth and 2TX MIMO/2RX 8, 20, 40 or 60 W 1TX mode per sector (by branch activation SW licenses) 8+8, 20+20, 40+40 or 60+60 W 2TX mode per sector (by branch activation and MIMO SW licenses)
For more information, see Flexi Multiradio BTS RF Module and Remote Radio Head Description.
Issue: 01 Draft
DN09237915
381
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
9.14.3 LTE2650 system impact The LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W feature has no impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features There are no interdependencies between the LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W feature and any other feature. Impact on interfaces The LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W feature has no impact on interfaces. Impact on network management tools The LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W feature has no impact on network management tools. Impact on system performance and capacity The LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W feature has no impact on system performance or capacity.
9.14.4 LTE2650 reference data LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W requirements and sales information Requirements Table 308
LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL17
UE
Not applicable LTE OMS16A
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
NetAct
Not applicable NetAct 16.8
Not applicable Not applicable
There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W feature. Sales information Table 309
LTE2650: FRSA Flexi RFM 6-pipe 1450 360 W sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.15 LTE2679: FRCJ Flexi RRH 2T4R 873 120 W Benefits, functionality, system impact, reference data of the feature
382
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
The LTE2679: FRCJ Flexi RRH 2T4R 873 120 W feature introduces the Flexi Multiradio Remote Radio Head 2TX/4RX (FRCJ) for 3GPP 873 MHz band 26b (uplink: 824 - 835 MHz, downlink: 869 - 880 MHz). FRCJ provides up to 2x60 Watts high output power at the antenna connector with 2TX MIMO.
9.15.1 LTE2679 benefits The LTE2679: FRCJ Flexi RRH 2T4R 873 120 W feature provides the following benefits: • • •
One sector RRH is able to support 2TX MIMO with high output power. Flexible installation options. FRCJ is designed to support book mount. It can be mounted onto a wall or pole and can be integrated into the Radio Antenna System. IP65 environmental protection class.
9.15.2 LTE2679 functional description The FRCJ module can support up to two sectors with a maximum output power of 60 W per TX at the BTS antenna connectors. The main features of the FRCJ are as follows: • • • • • • • • •
873 MHz 3GPP band 26b (sub-band of 850 MHz 3GPP band 26) and band 5 support 11 MHz instantaneous bandwidth per RRH in 2T4R mode 8 W, 10 W, 15 W, 20 W, 30 W, 40 W and 60 W power level support 1.4 MHz, 3 MHz, 5 MHz and 10 MHz LTE bandwidths support Up to 4 external alarms with RJ45 connector AISG2.0 antenna tilt support with external connector (RS485) Compatibility with optional Flexi Power Submodules (FPAD or FPAE) when AC power supply is needed 12.7 l volume (without solar cover and brackets) 12.8 kg weight (without solar cover and brackets)
The FRCJ supports the following modulation schemes: • •
up to QAM64 (DL/UL) up to QAM256 (DL)
The FRCJ module can be installed: • • • •
on a pole. on a wall. with book mount option. inside the Radio Antenna System (RAS).
For more information, see Flexi Multiradio BTS RF Module and Remote Radio Head Description.
9.15.3 LTE2679 system impact LTE2679: FRCJ Flexi RRH 2T4R 873 120 W impact on features, interfaces, network management tools, and system performance and capacity
Issue: 01 Draft
DN09237915
383
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
Interdependencies between features The following features must be activated before activating the LTE2679: FRCJ Flexi RRH 2T4R 873 120 W feature: • • •
LTE117: Cell Bandwidth - 1.4 MHz for the support of the 1.4 MHz LTE carriers LTE116: Cell Bandwidth - 3 MHz for the support of the 3 MHz LTE carriers LTE115: Cell Bandwidth - 5 MHz for the support of the 5 MHz carriers
The LTE2679: FRCJ Flexi RRH 2T4R 873 120 W feature is impacted by the following features: •
• •
•
• • • •
LTE614: Distributed Site With this feature FRCJ can be used in distributed sites with up to 23 km fiber length to the system module. LTE977: RF chaining With this feature FRCJ supports chains of up to 4 radio units. LTE1103: Load based Power Saving for multi-layer networks or LTE1203: Load based Power Saving mode with Tx power reduction or path switching off One of these features need to be enabled to use the PA shutdown feature. LTE2508: BTS Embedded Power Meter for Energy Efficiency Monitoring With this feature FRCJ can use Embedded Power Meter for Energy Efficiency Monitoring. LTE1891: eNode B power saving - Micro DTX This feature needs to be enabled to use Micro DTX extension. LTE1443: UpPTS blanking This feature can be used with FRCJ. LTE2556: Flexi Multiradio BTS Rx-sniffing Enhancements This feature can be used with FRCJ. LTE2902: Rx-Sniffing - PIM Sweep Test This feature can be used with FRCJ.
Impact on interfaces The LTE2679: FRCJ Flexi RRH 2T4R 873 120 W feature has no impact on interfaces. Impact on network management tools The LTE2679: FRCJ Flexi RRH 2T4R 873 120 W feature has no impact on network management tools. Impact on system performance and capacity The LTE2679: FRCJ Flexi RRH 2T4R 873 120 W feature has no impact on system performance or capacity.
9.15.4 LTE2679 reference data LTE2679: FRCJ Flexi RRH 2T4R 873 120 W requirements and sales information Requirements
384
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 310
Descriptions of BTS site solution features
LTE2679: FRCJ Flexi RRH 2T4R 873 120 W hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Not applicable Support not required
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL16A
UE Support not required
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
NetAct Support not required
Support not required
Support not required
There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE2679: FRCJ Flexi RRH 2T4R 873 120 W feature. Sales information Table 311
LTE2679: FRCJ Flexi RRH 2T4R 873 120 W sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.16 LTE2680: FHEL AirScale RRH 2T2R B3 120 W Benefits, functionality, system impact, reference data of the LTE2680 feature. The LTE2680: FHEL AirScale RRH 2T2R B3 120 W feature introduces Remote Radio Head (RRH) FHEL with 2TX downlink MIMO and 2RX uplink diversity for world market LTE operation on 3GPP band 3.
9.16.1 LTE2680 benefits The LTE2680: FHEL AirScale RRH 2T2R B3 120 W feature provides the following benefits: • • • • • • •
Smaller size and lower weight Vertically stackable RAS compatible 2-pipe RRH Improved power consumption Improved reliability Full Band IBW (75MHz) Horizontal Mounting Option (with Fans)
9.16.2 LTE2680 functional description Main properties LTE2680: FHEL AirScale RRH 2T2R B3 120 W main properties: •
Issue: 01 Draft
3GPP Band 3 1800 MHz, with 2x60 W output power
DN09237915
385
Descriptions of BTS site solution features
• • • • • • • • • • •
FDD-LTE16A, Feature Descriptions and Instructions
Single RAT Bandwidth: 75 MHz IBW, 40 MHz OBW RF Sharing Bandwidth: GSM IBW 37.5 MHz, LTE 75 MHz, 40 MHz OBW Weight: 15 kg Volume: 14 l RF Connector : 4.3-10 Connector IP65 with -40 to +55 °C with convection cooling Up to 4 external alarms and outputs AISG2.0 Antenna tilt support with external connector (RS485) Compatible with optional FPAE power supply when needed for AC solutions Optical chaining supported by hardware To enable full output power, two power licenses per TX pipe are required
Dimensions and weight Table 312
FHEL dimensions and weight Property
Value
Height
With cover: 600 mm (23.6 in.) With cover and fan: 630.2 mm (24.8 in.)
Depth
Dimensions orientation Dimensions orientation in vertical mount with cover
With cover and handle: 409.5: mm (16.1 in.) With cover, fan and handle: 409.5 mm (16.1 in.)
Width
width
With cover: 80 mm (3.1 in.)
height
With cover and fan: 80 mm (3.1 in.) Weight
12.5 kg (27.5 lbs)
Volume
With cover: 18 l
depth
Dimensions orientation in horizontal mount with cover and fan
Without cover: 12.5 l
width height depth
For more information, see Nokia AirScale Radio Description. RF Sharing Configurations LTE + GSM RF Sharing Configurations: •
up to 20MHz LTE + 4xGSM per pipe
Supported BTS configurations Supported BTS configurations: •
386
For single carrier LTE: all released BTS configurations valid for RRH 2Tx/2Rx RF units
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
•
Descriptions of BTS site solution features
For dual carrier LTE2019: Advanced Dual Carrier Operation within same RF Unit
9.16.3 LTE2680 system impact LTE2680: FHEL AirScale RRH 2T2R B3 120 W impact on features, system performance and capacity. Interdependencies between features The LTE2680: FHEL AirScale RRH 2T2R B3 120 W feature is impacted by the following features: • • • • • • •
• •
LTE112: Cell Bandwidth - 20 MHz It enables LTE 20 MHz carriers. LTE113: Cell Bandwidth - 15 MHz It enables LTE 15 MHz carriers. LTE114: Cell Bandwidth - 10 MHz It enables LTE 10 MHz carriers. LTE115: Cell Bandwidth - 5 MHz It enables LTE 5 MHz carriers. LTE116: Cell Bandwidth - 3 MHz It enables LTE 3 MHz carriers. LTE117: Cell Bandwidth - 1.4 MHz It enables LTE 1.4 MHz carriers. LTE614: Distributed Site With LTE614 FHEL can be used in distributed sites with up to 23km fiber length to the system module. LTE977: RF chaining With LTE977 FHEL supports chains of up to 4 radio units. LTE2437: Supported RAS Installation options in FL16 Release With LTE2437 RAS installation options are defined
Impact on interfaces The LTE2680: FHEL AirScale RRH 2T2R B3 120 W feature has no impact on interfaces. Impact on network management tools The LTE2680: FHEL AirScale RRH 2T2R B3 120 W feature has no impact on network management tools. Impact on system performance and capacity The LTE2680: FHEL AirScale RRH 2T2R B3 120 W feature has no impact on system performance and capacity.
9.16.4 LTE2680 reference data LTE2680: FHEL AirScale RRH 2T2R B3 120 W requirements and sales information. Requirements
Issue: 01 Draft
DN09237915
387
Descriptions of BTS site solution features
Table 313 System release
FDD-LTE16A, Feature Descriptions and Instructions
LTE2680 hardware and software requirements Flexi Multiradio BTS
Flexi Nokia AirScale Multiradio 10 BTS BTS
FDD-LTE 16A Not supported FL16A Flexi Zone Controller
OMS
Not supported
UE
Not Applicable LTE OMS16
Support not required
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
NetAct NetAct 16.8
Support not required
Support not required
There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE2680: FHEL AirScale RRH 2T2R B3 120 W feature. Sales information Table 314
LTE2680 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.17 LTE2722: Basic FDD Configurations for AirScale Benefits, functionality, system impact, reference data of the feature The LTE2722: Basic FDD Configurations for AirScale feature introduces a comprehensive set of BTS configurations for single carrier deployments with AirScale System Module (one LTE carrier per antenna connector).
9.17.1 LTE2722 benefits The LTE2722: Basic FDD Configurations for AirScale feature provides a comprehensive set of BTS configurations for single carrier deployments with AirScale System Module.
9.17.2 LTE2722 functional description This feature provides BTS configurations for one FDD eNB built with the AirScale System Module Indoor. A complete eNB configuration is composed by a number of the following independent sub-configurations called cell sets: • • •
Sub-configurations can be flexibly combined, the maxium number of supported cells depends on the number of installed ABIA modules. Basic cell set sub-configurations are defined on level of ½ ABIA module. Extended cell set sub-configurations require one whole ABIA.
The possible cell mappings into the cell sets: •
Basic cell set: –
388
up to 4 cells 5/10MHz in 2Tx/2Rx
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
– – – •
Descriptions of BTS site solution features
up to 3 cells 15/20MHz in 2Tx/2Rx up to 2 cells 15/20MHz plus 2 cells 5/10MHz in 2Tx/2Rx up to 2 cells 5/10/15/20MHz with 4Tx/4Rx
Extended cell set: – –
up to 6 cells 5/10/15/20MHz in 2Tx/2Rx up to 3 cells 15/20MHz with 4Tx/4Rx
The difference in call capacity of two basic cell sets in comparison to one extended cell set is related to advanced LTE features. Each capacity module ABIA provides 6 optical RF ports. Following optical interface options are supported (interface technology can be selected per ABIA module, speed can be selected on port base): • •
OBSAI 3 Gbps or OBSAI 6 Gbps CPRI 2.4 Gbps or CPRI 4.9
The cell configurations listed above are supported by many different site deployment solutions using centralized Radio Modules, distributed Radio Modules or Remote Radio Heads. Intra Sector chaining is supported for distributed installations. Most of the BTS topologies known from former releases can be re-used. However, the configuration of a Multiradio 10 base station cannot be used as it is with AirScale System Module. For the replacement of Multiradio 10 system modules with AirScale a manual conversion from Multiradio 10 base station plan file to AirScale plan file is needed.
g
Note: For details regarding supported configurations with different Radio Unit types please check release documentation.
g
Note: By default, both AirScale sub-rack halfs, each one equipped with one ASIA and up to three ABIA modules are operated as separate logical eNBs.
9.17.3 LTE2722 system impact LTE2722: Basic FDD Configurations for AirScale impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features •
• • •
•
LTE2517 AirScale HW capacity activation licenses are needed to use ABIA base band capacity. One license for each basic cell set and two licenses for each extended cell set. LTE1402 Uplink Intra-eNB CoMP: any 3 cells of same band belonging to the same cell set (basic one or extended one) can be selected for UL CoMP. LTE1691 Uplink intra eNode B CoMP 4RX: any 3 cells of same band belonging to the same cell set can be selected for the UL CoMP candidate set. Carrier aggregation is supported between cells assigned to same sector processed on any ASIA capacity module. Supported band and carrier bandwidth combinations are defined by the specific carrier aggregation features. Combined SuperCells according to LTE2445 can be configured between sub-cells served by radio units belonging to the same cell set.
Impact on interfaces
Issue: 01 Draft
DN09237915
389
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
The LTE2722: Basic FDD Configurations for AirScale feature has no impact on interfaces. Impact on network management tools The LTE2722: Basic FDD Configurations for AirScale feature has no impact on network management tools. Impact on system performance and capacity The LTE2722: Basic FDD Configurations for AirScale feature has no impact on system performance or capacity.
9.17.4 LTE2722 reference data LTE2722: Basic FDD Configurations for AirScale requirements and sales information Requirements Table 315
LTE2722 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FDD-LTE 16A
Not supported
Not supported
FL16A
Flexi Zone Controller
OMS
UE
Not supported LTE OMS16A
Support not required
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
NetAct NetAct 16.8
Support not required
Support not required
The LTE2722: Basic FDD Configurations feature requaires AirScale System Module. Mimimum HW configuration: • • •
one AirScale Subrack AMIA one AirScale Common unit ASIA one AirScale Capacity unit ABIA
There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE2722: Basic FDD Configurations for AirScale feature. Sales information Table 316
LTE2722 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.18 LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W Benefits, functionality, system impact, reference data of the feature
390
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
The LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W feature introduces the Flexi Multiradio RF Module (FXEF) for 3GPP 1800 MHz band 3 (uplink: 1710 - 1785 MHz, downlink: 1805 - 1880 MHz). FXEF has three power amplifiers enabling it to support one, two or three sectors with an output power of up to 80 Watts xTX MIMO at the BTS antenna connectors.
9.18.1 LTE2767 benefits The LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W feature provides the following benefits: • • •
Two RF Modules are able to support three sector 2TX MIMO. Flexible installation options. FXEF is designed to be mounted onto a wall or a pole. IP65 environmental protection class.
9.18.2 LTE2767 functional description The main features of the FXEF are as follows: • • • • •
• • • • •
1800 MHz 3GPP band 3 support 75 MHz instantaneous bandwidth 8 W, 10 W, 15 W, 20 W, 30 W, 40 W, 60 W and 80 W power level support 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz and 20 MHz carrier bandwidth support Maximum eight GSM carriers or four WCDMA/LTE carriers per antenna connector with a maximum occupied bandwidth of 40 MHz multiple carriers with a maximum instantaneous bandwidth of 75 MHz in uplink and downlink LTE/LTE and LTE/GSM RF sharing support AISG2.0 antenna tilt support with external connector (RS485) Forced cooling by the integrated fans 25 l volume 25 kg weight
The FXEF supports the following modulation schemes: • •
QAM64 (DL/UL) QAM256 (DL/UL)
The FXEF can be installed: • •
on a pole. on a wall.
The following are some basic LTE configurations with one FXEF for one sector: • • • • •
1 LTE cell @ max 20 MHz LTE bandwidth and 2TX MIMO/2RX 2 LTE cells @ 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) 8, 20, 40, 60 or 80 W 1TX 2RX mode per one, two or three sectors (by branch activation SW licenses) 4RX mode per sector (by activation 4RX SW license)
The following are some basic LTE configurations with two FXEF for two or three sectors:
Issue: 01 Draft
DN09237915
391
Descriptions of BTS site solution features
• • • •
FDD-LTE16A, Feature Descriptions and Instructions
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 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) 4RX mode per sector (by activation 4RX SW license)
The following are some basic GSM configurations: • •
4/4/4 cells @ 20 W with 40 MHz instantaneous bandwidth Up to eight GSM TRX carriers (4+4) per sector from 2TX PA paths
The following are the LTE/GSM configurations example: • •
Up to 20 MHz LTE bandwidth (40 W) and four GSM 4TRX carriers per TX PA path 5 MHz bandwidth and 2TX MIMO + six GSM TRX carriers (3+3) per sector from 2 TX PA paths
For more information, see Flexi Multiradio BTS RF Module and Remote Radio Head Description.
9.18.3 LTE2767 system impact LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be activated before activating the LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W feature: • • • • • •
LTE117: Cell Bandwidth - 1.4 MHz for the support of the 1.4 MHz LTE carriers LTE116: Cell Bandwidth - 3 MHz for the support of the 3 MHz LTE carriers LTE115: Cell Bandwidth - 5 MHz for the support of the 5 MHz LTE carriers LTE114: Cell Bandwidth - 10 MHz for the support of the 10 MHz LTE carriers LTE113: Cell Bandwidth - 15 MHz for the support of the 15 MHz LTE carriers LTE112: Cell Bandwidth - 20 MHz for the support of the 20 MHz LTE carriers
The LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W feature is impacted by the following features: •
• •
•
LTE614: Distributed Site With this feature FXEF can be used in distributed sites with up to 23 km fiber length to the system module. LTE977: RF chaining With this feature FXEF supports chains of up to 4 radio units. LTE1103: Load based Power Saving for multi-layer networks or LTE1203: Load based Power Saving mode with Tx power reduction or path switching off One of these features need to be enabled to use the PA shutdown feature. LTE1891: eNode B power saving - Micro DTX This feature needs to be enabled to use Micro DTX extension.
Impact on interfaces The LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W feature has no impact on interfaces.
392
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
Impact on network management tools The LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W feature has no impact on network management tools. Impact on system performance and capacity The LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W feature has no impact on system performance or capacity.
9.18.4 LTE2767 reference data LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W requirements and sales information Requirements Table 317
LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Zone Controller
OMS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL16A
UE
Not applicable LTE OMS16
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
MME
SAE GW
NetAct
Not applicable NetAct 16.8
Not applicable Not applicable
There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W feature. Sales information Table 318
LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.19 LTE2880: Support of classical WCDMA/LTE RFsharing on 4Tx/4Rx Remote Radio Head (RRH Rel. 4.3-family) Benefits, functionality, system impact, reference data of the feature The LTE2880: Support of classical WCDMA/LTE RF-sharing on 4Tx/4Rx Remote Radio Head (RRH Rel. 4.3-family) feature introduces the configurations of 4Tx/4Rx Remote Radio Heads (RRHs) from Flexi HW 4.3 in WCDMA-LTE RF sharing. The list of RRHs belonging to Flexi HW 4.3 is available in the LTE Base Stations Supported Configurations document.
Issue: 01 Draft
DN09237915
393
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
9.19.1 LTE2880 benefits The LTE2880: Support of classical WCDMA/LTE RF-sharing on 4Tx/4Rx Remote Radio Head (RRH Rel. 4.3-family) feature provides the following benefit: the option of using Flexi HW 4.3 based on 4Tx/4Rx RRHs in WCDMA-LTE RF sharing can make more flexible configurations available.
9.19.2 LTE2880 functional description This feature extends the existing WCDMA-LTE RF sharing functionality to configurations with 4Tx/4Rx RRHs belonging to Flexi HW 4.3. For the list of RRHs from Flexi HW 4.3, see the LTE Base Stations Supported Configurations document. Table 319
Configurations introduced by the feature
Cells/Sectors
Configurations type
WCDMA up to WCDMA: 4+4+4 2Tx/4Rx (J-type) LTE: 1+1+1
5, 10, 15, 20 MHz
LTE: 2Tx/4Rx, MIMO (J-type)
WCDMA up to WCDMA: 4+4+4 2Tx/4Rx (J-type) LTE: 1+1+1
LTE BW
System Module WCDMA: FSMF LTE: FSMF, FBBC
5, 10, 15, 20 MHz
LTE: 4Tx/4Rx, MIMO (M-type)
WCDMA: FSMF LTE: FSMF, FBBC
RF Modules (shared)
Carriers assignment
Up to 3x FRIJ or other RRHs from Flexi HW 4.3 (1-3 sectors)
Both WCDMA and LTE carriers mapped on dedicated Txpipes
Up to 3x FRIJ or other RRHs from Flexi HW 4.3 (1-3 sectors)
Both WCDMA and LTE carriers on shared PAs
Additional information on the configuration: • • • • •
WCDMA-LTE RF sharing is limited to the AWS1 frequency block of AWS-spectrum. The full frequency range support (AWS3) will come in the future release. Additional dedicated LTE bands are supported as defined in LTE2080: LTE-WCDMA RF sharing with full FBBC support. For this purpose, additional FBBC expansion modules might be needed. If LTE UL CoMP is used, an extended FSP cell set is required. An extended FSP cell set is also required if LTE 4Tx/4Rx-mode with 15/20 MHz is running.
For more information, see the Flexi Multiradio BTS RF Sharing Released Configurations document.
9.19.3 LTE2880 system impact LTE2880 impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be activated before activating the LTE2880: Support of classical WCDMA/LTE RF-sharing on 4Tx/4Rx Remote Radio Head (RRH Rel. 4.3family) feature:
394
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• •
Descriptions of BTS site solution features
RAN2126: RF Sharing WCDMA - LTE LTE435: RF Sharing WCDMA - LTE
Impact on interfaces The LTE2880: Support of classical WCDMA/LTE RF-sharing on 4Tx/4Rx Remote Radio Head (RRH Rel. 4.3-family) feature has no impact on interfaces. Impact on network management tools The LTE2880: Support of classical WCDMA/LTE RF-sharing on 4Tx/4Rx Remote Radio Head (RRH Rel. 4.3-family) feature has no impact on network management tools. Impact on system performance and capacity New configurations are available. For more information, see the Flexi Multiradio BTS RF Sharing Released Configurations document.
9.19.4 LTE2880 reference data LTE2880 requirements, alarms and faults, measurements and counters, KPIs, parameters, and sales information Requirements Table 320 System release
LTE2880 hardware and software requirements Flexi Multiradio BTS
FDD-LTE16A
Not supported
Flexi Zone Controller
OMS
Support not required
Flexi Multiradio 10 BTS FL16A
UE
LTE OMS16A
Support not required
Nokia AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
Planned for later releases
Not supported
Not supported
NetAct NetAct 16.8
MME Support not required
SAE GW Support not required
There are no alarms, measurements and counters, key performance indicators, parameters related to the LTE2880: Support of classical WCDMA/LTE RF-sharing on 4Tx/4Rx Remote Radio Head (RRH Rel. 4.3-family) feature. Sales information Table 321
LTE2880 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.20 LTE2911: Classical LTE-GSM RF-sharing with FXEF Flexi RFM 3-pipe 1800 240 W Benefits, functionality, system impact, reference data of the feature
Issue: 01 Draft
DN09237915
395
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
The LTE2911: Classical LTE-GSM RF-sharing with FXEF Flexi RFM 3-pipe 1800 240 W feature introduces classical LTE-GSM RF sharing based on FXEF with both GSM and LTE running on FSMF System Modules.
9.20.1 LTE2911 benefits The LTE2911: Classical LTE-GSM RF-sharing with FXEF Flexi RFM 3-pipe 1800 240 W feature provides the following benefit: the option of using FXEF in LTE-GSM RF sharing can make more flexible configurations available.
9.20.2 LTE2911 functional description This feature extends the existing LTE-GSM RF sharing functionality to configurations with FXEF RF Module. For information on FXEF, see the LTE2767: FXEF Flexi RFM 3-pipe 1800 240 W feature and the Flexi Multiradio BTS RF Module and Remote Radio Head Description document. LTE-GSM RF sharing using FXEF is supported only on FSMF System Modules (both GSM and LTE). FXEF is a replacement for FXEB and FXEE products. All FXEB configurations are supported. The configurations specific to FXEE are not introduced with this feature. Any valid LTE cell set is allowed for a dedicated LTE radio that coexists with FXEF shared radio. There is no power back-off in shared configurations. In case of configurations where GSM uses a dedicated pipe, there are no antenna line management features available for that pipe. RF sharing configurations with FXEF introduced by the feature: •
1 x RFM indoor / Distributed Antenna System (DAS) solution –
•
2 x RFM centralized configuration – – – – – – – – – –
•
LTE 1.4 MHz (H) + 10 GSM TRX (C) or 5 GSM TRX (H) LTE 3 MHz (H) + 10 GSM TRX (C) or 5 GSM TRX (H) LTE 5 MHz (H) + 10 GSM TRX (C) or 5 GSM TRX (H) LTE 10 MHz (H) + 8 GSM TRX (C) or 4 GSM TRX (H) LTE 15 MHz (H) + 6 GSM TRX (C) or 3 GSM TRX (H) LTE 20 MHz (H) + 4 GSM TRX (C) or 2 GSM TRX (H) LTE 5 MHz (K) + 4 GSM TRX (K) LTE 10 MHz (K) + 4 GSM TRX (K) LTE 15 MHz (K) + 2 GSM TRX (K) LTE 20 MHz (K) + 2 GSM TRX (K)
1-3 x RFM distributed site (shared PA, configuration G requires 2 port antenna, configuration J requires 4 port antenna), antenna ports which are not used can be allocated for a dedicated GSM (within the allowed capacity) –
396
LTE (A) + 4 GSM TRX (A) LTE bandwidths: 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, and 20 MHz
LTE 1.4 MHz (G) + 10 GSM TRX (B) or 5 GSM TRX (G)
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
– – – – – – – – – •
Descriptions of BTS site solution features
LTE 3 MHz (G) + 10 GSM TRX (B) or 5 GSM TRX (G) LTE 5 MHz (G) + 10 GSM TRX (B) or 5 GSM TRX (G) LTE 10 MHz (G) + 8 GSM TRX (B) or 4 GSM TRX (G) LTE 15 MHz (G) + 6 GSM TRX (B) or 3 GSM TRX (G) LTE 20 MHz (G) + 4 GSM TRX (B) or 2 GSM TRX (G) LTE 5 MHz (J) + 4 GSM TRX (J) LTE 10 MHz (J) + 4 GSM TRX (J) LTE 15 MHz (J) + 2 GSM TRX (J) LTE 20 MHz (J) + 2 GSM TRX (J)
1-3 x RFM distributed site, dedicated pipes (either 4 port antenna or 2 x 2 port antennas needed) – – – – – –
LTE 1.4 MHz (G) + 6 GSM TRX (A) LTE 3 MHz (G) + 6 GSM TRX (A) LTE 5 MHz (G) + 6 GSM TRX (A) LTE 10 MHz (G) + 6 GSM TRX (A) LTE 15 MHz (G) + 6 GSM TRX (A) LTE 20 MHz (G) + 6 GSM TRX (A)
All current RF sharing configurations are specified in the Flexi Multiradio BTS RF Sharing Released Configurations document.
9.20.3 LTE2911 system impact LTE2911 impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be activated before activating the LTE2911: Classical LTEGSM RF-sharing with FXEF Flexi RFM 3-pipe 1800 240 W feature: • •
LTE447: SW support for RF sharing GSM-LTE BSS21520: SW support for RF sharing GSM-LTE
Impact on interfaces The LTE2911: Classical LTE-GSM RF-sharing with FXEF Flexi RFM 3-pipe 1800 240 W feature has no impact on interfaces. Impact on network management tools The LTE2911: Classical LTE-GSM RF-sharing with FXEF Flexi RFM 3-pipe 1800 240 W feature has no impact on network management tools. Impact on system performance and capacity New configurations are available. For more information, see the Flexi Multiradio BTS RF Sharing Released Configurations document.
9.20.4 LTE2911 reference data LTE2911 requirements, alarms and faults, measurements and counters, KPIs, parameters, and sales information
Issue: 01 Draft
DN09237915
397
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
Requirements Table 322
LTE2911 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE16A
Not supported
Flexi Zone Controller
OMS
Support not required
Support not required
Flexi Multiradio 10 BTS
Nokia AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
Not supported
Not supported
Not supported
NetAct
MME
SAE GW
UE Support not required
NetAct 16.8
Support not required
Support not required
There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE2911: Classical LTE-GSM RF-sharing with FXEF Flexi RFM 3-pipe 1800 240 W feature. Sales information Table 323
LTE2911 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.21 LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) Benefits, functionality, system impact, reference data of the feature The LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) feature introduces the high power Flexi Zone Micro BTS (FW2CA) for 3GPP band 26 (uplink: 817.6 - 824 MHz, downlink: 862.6 - 869 MHz). FW2CA provides up to 2x20 Watts high output power at the antenna connector with 2TX MIMO.
9.21.1 LTE2914 benefits The LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) feature provides the following benefits: • • •
One sector Flexi Zone Micro is able to support 2TX MIMO with high output power Seamless mobility and enhanced user experience in enterprise and public indoor locations by cost effectively improving the coverage and capacity of the network Small size and weight
9.21.2 LTE2914 functional description The main features of the FW2CA are as follows: • • •
398
Frequency: 3GPP 850 MHz (band 26) RF output power: 1 W to 20 W per Tx path Carriers: 1
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• • • • • • • • • • • • •
Descriptions of BTS site solution features
Bandwidth support: 1x5 MHz per carrier Connected users: up to 480 simultaneous users Weight: 17 kg (37.5 lbs) Volume: 17 l Synchronization: RF GPS, IEEE 1588v2 2 x RJ45 and 1 x SFP for backhaul or management Antenna configuration: 2Tx/2Rx MIMO Antenna type: remote, customer provided Connector: 4.1/9.5 Mini-DIN Local Maintenance Ports: Bluetooth or unused RJ45 port Power Consumption: max: 360 W; typical: 290 W Emission: TS36.104 Rev-11 wide area No AISG 2.0 support
The FW2CA dimensions are: • • •
Height: 345 mm (13.6 in.) Width: 380 mm (15.0 in.) Depth: 169 mm (6.6 in.)
9.21.3 LTE2914 system impact LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) has no impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features There are no interdependencies between the LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) feature and any other feature. Impact on interfaces The LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) feature has no impact on interfaces. Impact on network management tools The LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) feature has no impact on network management tools. Impact on system performance and capacity The LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) feature has no impact on system performance or capacity.
9.21.4 LTE2914 reference data LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) requirements and sales information Requirements Table 324
Issue: 01 Draft
LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FDD-LTE 16A
Not supported
Not supported
Not supported
DN09237915
Flexi Zone Micro BTS FL16A
Flexi Zone Access Point FL16A
399
Descriptions of BTS site solution features
Table 324
FDD-LTE16A, Feature Descriptions and Instructions
LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) hardware and software requirements (Cont.)
Flexi Zone Controller
OMS
FL16A
Support not required
UE Support not required
NetAct Support not required
MME Support not required
SAE GW Support not required
There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) feature. Sales information Table 325
LTE2914: FW2CA Flexi Zone Micro High Power B26 (850 MHz) sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.22 LTE2920: Classical WCDMA/LTE-RF sharing support for narrowband LTE (LTE 1.4 and 3 MHz) Benefits, functionality, system impact, reference data of the feature The LTE2920: Classical WCDMA/LTE-RF sharing support for narrowband LTE (LTE 1.4 and 3 MHz) feature introduces classical WCDMA-LTE RF sharing support for narrowband LTE-carriers (1.4 and 3 MHz bandwidth) on all existing RF sharing configurations.
9.22.1 LTE2920 benefits The LTE2920: Classical WCDMA/LTE-RF sharing support for narrowband LTE (LTE 1.4 and 3 MHz) feature provides the following benefit: the option of using narrowband LTEdeployments in WCDMA-LTE RF sharing can make more flexible configurations available.
9.22.2 LTE2920 functional description This feature extends the existing WCDMA-LTE RF sharing functionality to narrowband LTE support. Narrowband LTE carrier support (LTE 1.4 MHz and LTE 3 MHz) for classical WCDMALTE RF sharing is released for the following RF variants: •
1.4 MHz BW – – –
•
400
2-pipe RRHs: FRCG, FHDB 4-pipe RRH: FHFB 3-pipe RFMs: FXFA, FXCA, FXDA, FXFC, FXCB, FXDA, FXDB
3 MHz BW
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
– –
Descriptions of BTS site solution features
2-pipe RRHs: FRCG, FHDB 3-pipe RFMs: FXFA, FXCA, FXDA, FXFC, FXCB, FXDA, FXDB
Narrowband LTE carrier support will be released on all existing WCDMA-LTE RF sharing configurations, that had been already released for 5 MHz LTE carrier on the listed RF units.
g
Note: There are some functional limitations while using LTE 1.4 MHz or 3 MHz, for example, 1.4 MHz and 3 MHz BW with 4RX diversity is not supported. Further limitations are described in the LTE2429: Inheritance of SIMO, RIU and 1.4/3MHz configurations feature. Those limitations are planned to be removed in further LTE releases. All current RF sharing configurations are specified in the Flexi Multiradio BTS RF Sharing Released Configurations document.
9.22.3 LTE2920 system impact LTE2920 impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be activated before activating the LTE2920: Classical WCDMA/LTE-RF sharing support for narrowband LTE (LTE 1.4 and 3 MHz) feature: • •
RAN2126: RF Sharing WCDMA - LTE LTE435: RF Sharing WCDMA - LTE
The LTE2429: Inheritance of SIMO, RIU and 1.4/3MHz configurations feature describes functional limitations when using LTE bandwidth 1.4 or 3 MHz. Impact on interfaces The LTE2920: Classical WCDMA/LTE-RF sharing support for narrowband LTE (LTE 1.4 and 3 MHz) feature has no impact on interfaces. Impact on network management tools The LTE2920: Classical WCDMA/LTE-RF sharing support for narrowband LTE (LTE 1.4 and 3 MHz) feature has no impact on network management tools. Impact on system performance and capacity New configurations are available. For more information, see the Flexi Multiradio BTS RF Sharing Released Configurations document.
9.22.4 LTE2920 reference data LTE2920 requirements, alarms and faults, measurements and counters, KPIs, parameters, and sales information Requirements
Issue: 01 Draft
DN09237915
401
Descriptions of BTS site solution features
Table 326
FDD-LTE16A, Feature Descriptions and Instructions
LTE2920 hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE16A
Not supported
Flexi Zone Controller
OMS
Support not required
Support not required
Flexi Multiradio 10 BTS
Nokia AirScale BTS
Flexi Zone Micro BTS
Flexi Zone Access Point
FL16A
Planned for later releases
Not supported
Not supported
NetAct
MME
SAE GW
UE Support not required
Support not required
Support not required
Support not required
There are no alarms, measurements and counters, key performance indicators, parameters related to the LTE2920: Classical WCDMA/LTE-RF sharing support for narrowband LTE (LTE 1.4 and 3 MHz) feature. Sales information Table 327
LTE2920 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.23 LTE2950: B3+B7 FZ G2 Indoor Multi-Band Pico (FW2EHA, FW2EHWA) Benefits, functionality, system impact, reference data of the feature The LTE2950: B3+B7 FZ G2 Indoor Multi-Band Pico (FW2EHA, FW2EHWA) feature introduces dual-band Flexi Zone Indoor Pico BTS platform in two 3GPP licensed bands. There are two hardware variants introduced under this feature: 1. FW2EHA: Band-3 + Band-7 2. FW2EHWA: Band-3 + Band-7 + World Wide Compliant Wi-Fi
9.23.1 LTE2950 benefits The LTE2950: B3+B7 FZ G2 Indoor Multi-Band Pico (FW2EHA, FW2EHWA) feature provides the following benefits: • • • • •
402
Seamless mobility and enhanced user experience in enterprise and public indoor locations Cost-effective solution for improving the coverage and capacity of the network, delivering the best broadband experience to mobile users The hardware can be deployed as a stand-alone eNodeB, or in a Nokia's Zonebased architecture as a Flexi Zone Indoor Access Point via software upgrade The most compact dual-band Flexi Zone Indoor Pico BTS with macro parity in the industry Advanced features such as Carrier Aggregation across two bands
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
• • • • •
Descriptions of BTS site solution features
Fully 3GPP compliant S1, X2 and Uu interfaces Seamless integration into legacy Nokia architecture and HetNets Software upgradeable to Nokia Zone solution Optional dual-band Wi-Fi including 802.11ac Fully automated Plug & Play
9.23.2 LTE2950 functional description This hardware is the second generation of the Flexi Zone Indoor Pico BTS Platform. Key features include: • • • • • • • • • •
Technology: LTE / LTE-A Frequency: FDD Band-3 (uplink: 1710 - 1785 MHz, downlink: 1805 - 1880 MHz) + Band-7 (uplink: 2500 - 2570 MHz; downlink: 2620 - 2690 MHz) Output Power: 2x250 mW max. per band (configurable in steps of 50 mW) Total output power of the Pico: 1 W Base Station Class: Local Weight and volume: < 3.0 kg / < 3.4 L (not including the mounting brackets) for both LTE and Wi-Fi Carrier bandwidth support: up to 20 MHz per band for the 3GPP licensed LTE Antenna Configuration: Integrated 2Tx / 2Rx (2X2 MIMO) Capacity: 400 users Wi-Fi: Optional integrated dual-band Wi-Fi module supporting 2.4 GHz and 5 GHz, 802.11 b/g/n/ac Backhaul: Two RJ45 Copper Gigabit Ethernet ports Port 1: Main backhaul, PoE++ capable supporting SyncE and IEEE1588v2 Port 2: Used for management, factory testing and also for daisy chaining of additional Indoor Pico Notes on backhaul ports: 1. Only Port 1 is PoE capable. Thus, in daisy chained Picos, only the primary (main) Pico might be powered via PoE. The subsequent Picos will have to be powered via AC adapter. 2. SynchE-based timing cannot be passed to the downstream Picos from the first Pico.
•
Power: Two Options: – –
• •
PoE++ capable AC Power Adapter
Mounting Options: Wall / Ceiling Regulatory Approvals: Market Specific
9.23.3 LTE2950 system impact LTE2950: B3+B7 FZ G2 Indoor Multi-Band Pico (FW2EHA, FW2EHWA) impact on features, system performance, and capacity Interdependencies between features LTE2950: B3+B7 FZ G2 Indoor Multi-Band Pico (FW2EHA, FW2EHWA) feature has interdependencies between the following features:
Issue: 01 Draft
DN09237915
403
Descriptions of BTS site solution features
•
• •
FDD-LTE16A, Feature Descriptions and Instructions
FDD-LTE Dual Carrier (2x10MHz) Operation Support on a Single Flexi Zone Micro BTS FDD-LTE Dual Carrier Operation Supports on a Single Kepler2 SoC FDD Inter-band Dual Carrier Aggregation for Dual-Carrier Flexi Zone Micro BTS FDD Inter-band Dual Carrier Aggregation for two-board Flexi Zone Micro BTS Flexi Zone Controller Application support for multi-carrier Flexi Zone AP Flexi Zone Controller Multi-Carrier AP Support
Impact on interfaces The LTE2950: B3+B7 FZ G2 Indoor Multi-Band Pico (FW2EHA, FW2EHWA) feature has no impact on interfaces. Impact on network management tools The LTE2950: B3+B7 FZ G2 Indoor Multi-Band Pico (FW2EHA, FW2EHWA) feature has no impact on network management tools. This feature is not managed using NetAct. Impact on system performance and capacity The LTE2950: B3+B7 FZ G2 Indoor Multi-Band Pico (FW2EHA, FW2EHWA) feature impacts system performance and capacity as follows: •
It supports up to 400 users.
9.23.4 LTE2950 reference data LTE2950: B3+B7 FZ G2 Indoor Multi-Band Pico (FW2EHA, FW2EHWA) requirements and sales information Requirements Table 328
LTE2950 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FDD-LTE 16A
Not supported
Not supported
Not supported
Flexi Zone Controller
OMS
UE
NetAct
FL16A
Support not required
3GPP R10 mandatory
Support not required
Flexi Zone Micro BTS FL16A MME Support not required
Flexi Zone Access Point FL16A SAE GW Support not required
3GPP R11 mandatory 3GPP R11 UE capabilities 3GPP R12 UE capabilities
There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE2950: B3+B7 FZ G2 Indoor Multi-Band Pico (FW2EHA, FW2EHWA) feature. Sales information
404
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 329
Descriptions of BTS site solution features
LTE2950 sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.24 LTE3027: FRPD Flexi RFM 6-pipe 700 240 W Benefits, functionality, system impact, reference data of the feature The LTE3027: FRPD Flexi RFM 6-pipe 700 240 W feature introduces the Flexi Multiradio RF Module (FRPD) for 3GPP EU700 MHz band 28 (uplink: 703 - 733 MHz, downlink: 758 - 788 MHz). FRPD has six power amplifiers enabling it to support one, two or three sectors with an output power of up to 40+40 Watts 2TX MIMO at the BTS antenna connectors.
9.24.1 LTE3027 benefits The LTE3027: FRPD Flexi RFM 6-pipe 700 240 W feature provides the following benefits: • • •
One RF Module is able to support three sector 2TX MIMO. Flexible installation options. FRPD is designed to be mounted onto a wall or a pole. IP65 environmental protection class.
9.24.2 LTE3027 functional description The main features of the FRPD are as follows: • • • • •
• • • •
EU700 MHz 3GPP band 28 support 30 MHz instantaneous bandwidth 8 W, 10 W, 15 W, 20 W, 30 W and 40 W power level support 3 MHz, 5 MHz, 10 MHz, 15 MHz and 20 MHz carrier bandwidth support Maximum six carriers per antenna connector with a maximum occupied bandwidth of 30 MHz multiple carriers with a maximum instantaneous bandwidth of 30 MHz in uplink and downlink in LTE mode AISG2.0 antenna tilt support with external connector (RS485) Forced cooling by the integrated fans 19.3 l volume 24 kg weight
The FRPD supports the following modulation schemes: • •
QAM64 (DL/UL) QAM256 (DL/UL)
The FRPD module can be installed • •
Issue: 01 Draft
on a pole. on a wall.
DN09237915
405
Descriptions of BTS site solution features
FDD-LTE16A, Feature Descriptions and Instructions
For more information, see Flexi Multiradio BTS RF Module and Remote Radio Head Description.
9.24.3 LTE3027 system impact LTE3027: FRPD Flexi RFM 6-pipe 700 240 W impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be activated before activating the LTE3027: FRPD Flexi RFM 6-pipe 700 240 W feature: • • • •
LTE115: Cell Bandwidth - 5 MHz for the support of the 5 MHz carriers LTE114: Cell Bandwidth - 10 MHz for the support of the 10 MHz carriers LTE113: Cell Bandwidth - 15 MHz for the support of the 15 MHz carriers LTE112: Cell Bandwidth - 20 MHz for the support of the 20 MHz carriers
The LTE3027: FRPD Flexi RFM 6-pipe 700 240 W feature is impacted by the following features: •
• •
•
LTE614: Distributed Site With this feature FRPD can be used in distributed sites with up to 23 km fiber length to the system module. LTE977: RF chaining With this feature FRPD supports chains of up to 4 radio units. LTE1103: Load based Power Saving for multi-layer networks or LTE1203: Load based Power Saving mode with Tx power reduction or path switching off One of these features must be enabled to use the PA shutdown feature. LTE1891: eNode B power saving - Micro DTX This feature must be enabled to use Micro DTX extension.
Impact on interfaces The LTE3027: FRPD Flexi RFM 6-pipe 700 240 W feature has no impact on interfaces. Impact on network management tools The LTE3027: FRPD Flexi RFM 6-pipe 700 240 W feature has no impact on network management tools. Impact on system performance and capacity The LTE3027: FRPD Flexi RFM 6-pipe 700 240 W feature has no impact on system performance or capacity.
9.24.4 LTE3027 reference data LTE3027: FRPD Flexi RFM 6-pipe 700 240 W requirements and sales information Requirements Table 330
406
LTE3027: FRPD Flexi RFM 6-pipe 700 240 W hardware and software requirements
System release
Flexi Multiradio BTS
FDD-LTE 16A
Not supported
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FL16A
FL17
DN09237915
Flexi Zone Micro BTS
Flexi Zone Access Point
Not supported
Not supported
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Table 330
Descriptions of BTS site solution features
LTE3027: FRPD Flexi RFM 6-pipe 700 240 W hardware and software requirements (Cont.)
Flexi Zone Controller
OMS
Not applicable Support not required
UE Support not required
NetAct Support not required
MME Support not required
SAE GW Support not required
There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE3027: FRPD Flexi RFM 6-pipe 700 240 W feature. Sales information Table 331
LTE3027: FRPD Flexi RFM 6-pipe 700 240 W sales information
Product structure class Basic Software (BSW)
License control -
Activated by default Yes
9.25 LTE3177: B7+B7 FZ G2 Indoor Multi-Band Pico (FW2HHA, FW2HHWA) Benefits, functionality, system impact, reference data of the feature The LTE3177: B7+B7 FZ G2 Indoor Multi-Band Pico (FW2HHA, FW2HHWA) feature introduces a dual-band Flexi Zone Indoor Pico BTS platform in 3GPP licensed bands. There will be two hardware variants introduced under this feature: 1. FW2HHA: Band-7 + Band-7 2. FW2HHWA: Band-7 + Band-7 + World Wide Compliant Wi-Fi
9.25.1 LTE3177 benefits The LTE3177: B7+B7 FZ G2 Indoor Multi-Band Pico (FW2HHA, FW2HHWA) feature provides the following benefits: • • • • • • • • •
Issue: 01 Draft
Seamless mobility and enhanced user experience in enterprise and public indoor locations Cost-effective solution for improving the coverage and capacity of the network, delivering the best broadband experience to mobile users The hardware can be deployed as a stand-alone eNodeB, or in a Nokia's Zonebased architecture as a Flexi Zone Indoor Access Point via software upgrade The most compact dual-band Flexi Zone Indoor Pico BTS with macro parity in the industry Advanced features such as Carrier Aggregation across two bands Fully 3GPP compliant S1, X2 and Uu interfaces Seamless integration into legacy Nokia architecture and HetNets Software upgradeable to Nokia Zone solution Optional dual-band Wi-Fi including 802.11ac
DN09237915
407
Descriptions of BTS site solution features
•
FDD-LTE16A, Feature Descriptions and Instructions
Fully automated Plug & Play
9.25.2 LTE3177 functional description This hardware is the second generation of the Flexi Zone Indoor Pico BTS Platform. Key features include: • • • • • • • • • •
Technology: LTE / LTE-A Frequency: FDD Band-7 (uplink: 2510-2550 MHz, downlink: 2630-2670 MHz) + Band-7 (uplink: 2510-2550 MHz; downlink: 2630-2670 MHz) Output Power: 2x250 mW max. per band (configurable in steps of 50 mW) Total output power of the Pico: 1 W Base Station Class: Local Weight and volume: < 3.0 kg / < 3.4 L (not including the mounting bracket) for both LTE and Wi-Fi Carrier bandwidth support: up to 20 MHz per band for the 3GPP licensed LTE Antenna Configuration: Integrated 2Tx / 2Rx (2X2 MIMO) Capacity: 400 users Wi-Fi: Optional integrated dual-band Wi-Fi module supporting 2.4 GHz and 5 GHz, 802.11 b/g/n/ac Backhaul: Two RJ45 Copper Gigabit Ethernet ports Port 1: Main backhaul, PoE++ capable supporting SyncE and IEEE1588v2 Port 2: Used for management, factory testing and also for daisy chaining of additional Indoor Pico Notes on backhaul ports: 1. Only Port 1 is PoE capable. Thus, in daisy chained Picos, only the primary (main) Pico might be powered via PoE. The subsequent Picos will have to be powered via AC adapter. 2. SynchE-based timing cannot be passed to the downstream Picos from the first Pico.
•
Power: Two Options: – –
• •
PoE++ capable AC Power Adapter
Mounting Options: Wall / Ceiling Regulatory Approvals: Market Specific
9.25.3 LTE3177 system impact LTE3177: B7+B7 FZ G2 Indoor Multi-Band Pico (FW2HHA, FW2HHWA) impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features There are no interdependencies between the LTE3177: B7+B7 FZ G2 Indoor Multi-Band Pico (FW2HHA, FW2HHWA) feature and any other feature. Impact on interfaces The LTE3177: B7+B7 FZ G2 Indoor Multi-Band Pico (FW2HHA, FW2HHWA) feature has no impact on interfaces. Impact on network management tools The LTE3177: B7+B7 FZ G2 Indoor Multi-Band Pico (FW2HHA, FW2HHWA) feature has no impact on network management tools.
408
DN09237915
Issue: 01 Draft
FDD-LTE16A, Feature Descriptions and Instructions
Descriptions of BTS site solution features
Impact on system performance and capacity The LTE3177: B7+B7 FZ G2 Indoor Multi-Band Pico (FW2HHA, FW2HHWA) feature impacts system performance and capacity as follows: •
It supports up to 400 users.
9.25.4 LTE3177 reference data LTE3177: B7+B7 FZ G2 Indoor Multi-Band Pico (FW2HHA, FW2HHWA) requirements and sales information Requirements Table 332
LTE3177 hardware and software requirements
System release
Flexi Multiradio BTS
Flexi Multiradio 10 BTS
Nokia AirScale BTS
FDD-LTE 16A
Not supported
Not supported
Not supported
Flexi Zone Controller
OMS
UE
NetAct
FL16A
Support not required
Support not required
Support not required
Flexi Zone Micro BTS FL16A MME Support not required
Flexi Zone Access Point FL16A SAE GW Support not required
There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE3177: B7+B7 FZ G2 Indoor Multi-Band Pico (FW2HHA, FW2HHWA) feature. Sales information Table 333
LTE3177 sales information
Product structure class Basic Software (BSW)
Issue: 01 Draft
License control -
DN09237915
Activated by default Yes
409