335433914-Nokia-LTE-RL60-Feature-Descriptions-and-Instructions-2016.pdf
Comments
Description
NokiaLTE Radio Access, Rel. FDD- LTE16, Operating Documentation, Issue 02, Documentation Change Delivery 3 LTE RL60, Feature Descriptions and Instructions DN09185955 Issue 01J Approval Date 2016-07-25 LTE RL60, Feature Descriptions and Instructions The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective company within Nokia Group of Companies with whom you have entered into the Agreement (as defined below). This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia (“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. 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 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 welcomes 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 reserves the right to change any such information and statements without notice. Nokia has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia will correct errors that You identify in this document. Nokia's total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia 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 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 proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners. Copyright © 2016 Nokia. 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 is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia for any additional information. 2 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions Table of Contents This document has 322 pages Summary of changes................................................................... 22 1 RL60 Features - not supported by Flexi Zone Micro....................23 2 Introduction.................................................................................. 24 3 Activating and deactivating LTE features using BTS Site Manager. 25 4 Descriptions of radio resource management and telecom features. 27 4.1 LTE57: Inter RAT handover from UTRAN.................................... 27 4.1.1 Description of LTE57: Inter RAT handover from UTRAN............. 27 4.1.1.1 Benefits........................................................................................ 27 4.1.1.2 Requirements...............................................................................27 4.1.1.3 Functional description.................................................................. 27 4.1.1.4 System impact..............................................................................29 4.1.1.5 LTE57: Inter RAT handover from UTRAN management data...... 31 4.1.1.6 Sales information......................................................................... 32 4.1.2 Activating LTE57: Inter RAT handover from UTRAN....................32 4.1.3 Deactivating LTE57: Inter RAT handover from UTRAN............... 33 4.2 LTE60: Inter RAT handover to eHRPD/3GPP2............................ 34 4.2.1 Description of LTE60: Inter RAT Handover to eHRPD/3GPP2.... 34 4.2.1.1 Benefits........................................................................................ 34 4.2.1.2 Requirements...............................................................................34 4.2.1.3 Functional description.................................................................. 34 4.2.1.4 System impact..............................................................................36 4.2.1.5 LTE60: Inter RAT handover to eHRPD/3GPP2 management data.. 37 4.2.1.6 Sales information......................................................................... 41 4.2.2 Activating LTE60: Inter RAT handover to eHRPD/3GPP2........... 41 4.2.3 Deactivating LTE60: Inter RAT handover to eHRPD/3GPP2 ...... 45 4.3 LTE498: RAN Information Management for GSM........................ 46 4.3.1 Description of LTE498: RAN Information for GSM....................... 46 4.3.1.1 Benefits........................................................................................ 46 4.3.1.2 Requirements...............................................................................46 4.3.1.3 Functional description.................................................................. 47 4.3.1.4 System impact..............................................................................48 4.3.1.5 Management data........................................................................ 49 4.3.1.6 Sales information......................................................................... 51 4.3.2 Activating LTE498: RAN Information Management for GSM....... 51 4.3.3 Deactivating LTE498: RAN Information Management for GSM... 53 4.4 LTE520: 8 EPS bearers per UE................................................... 53 DN09185955 Issue: 01J © 2016 Nokia 3 LTE RL60, Feature Descriptions and Instructions 4.4.1 Description of LTE520: 8 EPS bearers per UE............................ 53 4.4.1.1 Benefits........................................................................................ 53 4.4.1.2 Requirements...............................................................................53 4.4.1.3 Functional description.................................................................. 54 4.4.1.4 System impact..............................................................................54 4.4.1.5 LTE520: 8 EPS bearers per UE management data..................... 55 4.4.1.6 Sales information......................................................................... 55 4.4.2 Activating and configuring LTE520: 8 EPS bearers per UE......... 55 4.4.3 Deactivating LTE520: 8 EPS bearers per UE...............................57 4.5 LTE801: Group hopping for UL reference signal..........................58 4.5.1 Description of LTE801: Group hopping for UL reference signal...58 4.5.1.1 Benefits........................................................................................ 58 4.5.1.2 Requirements...............................................................................58 4.5.1.3 Functional description.................................................................. 59 4.5.1.4 System impact..............................................................................59 4.5.1.5 LTE801: Group hopping for UL reference signal management data ..................................................................................................... 59 4.5.1.6 Sales information......................................................................... 60 4.5.2 Activating and configuring LTE801: Group hopping for UL reference signal............................................................................60 4.5.3 Deactivating LTE801: Group hopping for UL reference signal..... 61 4.6 LTE874: CSFB to CDMA/1xRTT for dual RX Ues........................62 4.6.1 Description of LTE874: CSFB to CDMA/1xRTT for dual RX Ues..... 62 4.6.1.1 Benefits........................................................................................ 62 4.6.1.2 Requirements...............................................................................62 4.6.1.3 Functional description.................................................................. 62 4.6.1.4 System impact..............................................................................64 4.6.1.5 LTE874: CSFB to CDMA/1xRTT for dual RX Ues management data.............................................................................................. 66 4.6.1.6 Sales information......................................................................... 67 4.6.2 Activating and configuring LTE874: CSFB to CDMA/1xRTT for dual RX UEs.................................................................................67 4.6.3 Deactivating LTE874: CSFB to CDMA/1xRTT for dual RX UEs...... 69 4.7 LTE944: PUSCH masking............................................................ 69 4.7.1 Description of LTE944: PUSCH masking..................................... 69 4.7.1.1 Benefits........................................................................................ 70 4.7.1.2 Requirements...............................................................................70 4.7.1.3 Functional description.................................................................. 70 4.7.1.4 System impact..............................................................................72 4.7.1.5 LTE944: PUSCH masking management data.............................. 73 4.7.1.6 Sales information......................................................................... 73 4.7.2 Activating and configuring LTE944: PUSCH masking..................74 4.7.3 Deactivating LTE944: PUSCH masking....................................... 75 4.8 LTE1047: Control plane overload handling.................................. 76 4.8.1 Description of LTE1047: Control plane overload handling........... 76 4 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions 4.8.1.1 Benefits........................................................................................ 76 4.8.1.2 Requirements...............................................................................77 4.8.1.3 Functional description.................................................................. 77 4.8.1.4 System impact..............................................................................78 4.8.1.5 LTE1047: Control plane overload handling management data.... 79 4.8.1.6 Sales information......................................................................... 80 4.8.2 Activating and configuring LTE1047: Control plane overload handling........................................................................................80 4.8.3 Deactivating LTE1047: Control plane overload handling............. 81 4.9 LTE1074: Multimedia priority services..........................................82 4.9.1 Description of LTE1074: Multimedia priority services...................82 4.9.1.1 Benefits........................................................................................ 82 4.9.1.2 Requirements...............................................................................82 4.9.1.3 Functional description.................................................................. 83 4.9.1.4 System impact..............................................................................84 4.9.1.5 LTE1074: Multimedia priority services management data............84 4.9.1.6 Sales information......................................................................... 85 4.9.2 Activating and configuring LTE1074: Multimedia priority services... 86 4.9.3 Deactivating LTE1074: Multimedia priority services.....................88 4.10 LTE1198: RSRQ triggered mobility.............................................. 88 4.10.1 Description of LTE1198: RSRQ Triggered Mobility...................... 88 4.10.1.1 Benefits........................................................................................ 88 4.10.1.2 Requirements...............................................................................89 4.10.1.3 Functional description.................................................................. 89 4.10.1.4 System impact..............................................................................89 4.10.1.5 LTE1198: RSRQ triggered mobility management data................ 90 4.10.1.6 Sales information......................................................................... 91 4.10.2 Activating LTE1198: RSRQ triggered mobility..............................91 4.10.3 Deactivating LTE1198: RSRQ triggered mobility..........................93 4.11 LTE1231: Operator-specific GBR QCIs........................................94 4.11.1 Description of LTE1231: Operator-specific GBR QCIs.................94 4.11.1.1 Benefits........................................................................................ 94 4.11.1.2 Requirements...............................................................................94 4.11.1.3 Functional description.................................................................. 94 4.11.1.4 System impact..............................................................................95 4.11.1.5 LTE1231: Operator-specific GBR QCIs management data..........95 4.11.1.6 Sales information......................................................................... 97 4.11.2 Activating and configuring LTE1231: Operator-specific GBR QCIs. 97 4.11.3 Deactivating LTE1231: Operator-specific GBR QCIs...................98 4.12 LTE1332: Downlink Carrier Aggregation - 40 MHz...................... 99 4.12.1 Description of LTE1332: Downlink Carrier Aggregation - 40 MHz... 99 4.12.1.1 Benefits........................................................................................ 99 4.12.1.2 Requirements...............................................................................99 DN09185955 Issue: 01J © 2016 Nokia 5 LTE RL60, Feature Descriptions and Instructions 4.12.1.3 Functional description................................................................ 100 4.12.1.4 System impact............................................................................103 4.12.1.5 LTE1332: Downlink Carrier Aggregation - 40 MHz management data............................................................................................ 104 4.12.1.6 Sales information....................................................................... 106 4.12.2 Activating and configuring LTE1332: Downlink Carrier Aggregation - 40 MHz.....................................................................................106 4.12.3 Deactivating LTE1332: Downlink Carrier Aggregation - 40 MHz...... 111 4.13 LTE1336: Interference aware UL power control......................... 111 4.13.1 Description of LTE1336: Interference aware UL power control........ 111 4.13.1.1 Benefits.......................................................................................112 4.13.1.2 Requirements............................................................................. 112 4.13.1.3 Functional description.................................................................112 4.13.1.4 System impact............................................................................ 114 4.13.1.5 LTE1336: Interference aware UL power control management data. 115 4.13.1.6 Sales information........................................................................116 4.13.2 Activating and configuring LTE1336: Interference aware UL power control.........................................................................................116 4.13.3 Deactivating LTE1336: Interference aware UL power control.... 118 4.14 LTE1342: Extended RNC ID.......................................................119 4.14.1 Description of LTE1342: Extended RNC ID................................119 4.14.1.1 Benefits.......................................................................................119 4.14.1.2 Requirements............................................................................. 119 4.14.1.3 Functional description.................................................................119 4.14.1.4 System impact............................................................................120 4.14.1.5 Management data...................................................................... 121 4.14.1.6 Sales information....................................................................... 121 4.14.2 Activating and configuring LTE1342: Extended RNC ID............ 121 4.14.3 Deactivating LTE1342: Extended RNC ID..................................124 4.15 LTE1382: Cell resource groups..................................................125 4.15.1 Description of LTE1382: Cell resource groups ..........................125 4.15.1.1 Benefits...................................................................................... 125 4.15.1.2 Requirements.............................................................................125 4.15.1.3 Functional description................................................................ 126 4.15.1.4 System impact............................................................................127 4.15.1.5 LTE1382: Cell resource groups management data....................128 4.15.1.6 Sales information....................................................................... 131 4.15.2 Activating and configuring LTE1382: Cell resource groups....... 131 4.15.3 Deactivating LTE1382: Cell resource groups............................. 134 4.16 LTE1402: Uplink Intra-eNB CoMP..............................................134 4.16.1 Description of LTE1402: Uplink Intra-eNB CoMP.......................134 4.16.1.1 LTE1402 benefits....................................................................... 134 4.16.1.2 Requirements.............................................................................135 4.16.1.3 Functional description................................................................ 135 6 © 2016 Nokia DN09185955 Issue: 01J ...1.........20 LTE1531: Inter-frequency Load Balancing Extension.....................20...17...............3 Functional description.............17.............................................4 System impact...................................4 System impact....19..................6 Sales information........... 174 4........1... 170 4.....................18. 174 4...................................136 4........ 144 4.............................. 174 4..18..17........ 147 4...................................1 Description of LTE1433: LPPa support for OTDOA.....18...........1... 159 4........17..17.........1............175 DN09185955 Issue: 01J © 2016 Nokia 7 .... 152 4................. 171 4.......5 LTE1495: Fast uplink link adaptation management data.... 140 4....................................................18........................1.....140 4..................2 Requirements....................................................16.............3 Deactivating of LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB)...............168 4.............1.......................5 LTE1402: Uplink Intra-eNB CoMP management data...2 Requirements..................3 Deactivating LTE1495: Fast uplink link adaptation...............18 LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB).........................................................................................18.. 147 4....6 Sales information..16.............17........5 LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) management data............17..3 Deactivating LTE1402: Uplink Intra-eNB CoMP......... 137 4.................2 Activating and configuring LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB)..............20..... 144 4..........5 LTE1433: LPPa support for OTDOA management data. 159 4.............167 4.....3 Functional description..... 166 4.18..................1......................19........................19............147 4..........1...6 Sales information........................1 Benefits...............................3 Functional description.........................................................143 4...................................1... 138 4.............17 LTE1433: LPPa support for OTDOA... 146 4.........................2 Activating and configuring LTE1402: Uplink Intra-eNB CoMP.....2 Activating and configuring LTE1433: LPPa support for OTDOA.....................................................................................................20..1..................... 138 4.......1..............3 Deactivating LTE1433: LPPa support for OTDOA..17...4 System impact... 140 4.....................19.................................................18........... 167 4................................................19....................................1 Description of LTE1531: Inter-frequency Load Balancing Extension.1....6 Sales information... 146 4......1 Benefits......... 167 4..................16...................2 Requirements......................1.. 175 4........1 Benefits...............1........ 143 4...............................................1.1.1 Description of LTE1495: Fast uplink link adaptation.. 166 4............... 141 4... 140 4........1....4 System impact..........................2 Activating and configuring LTE1495: Fast uplink link adaptation.......141 4...........................1..19......................19 LTE1495: Fast uplink link adaptation......1............19.........................1.............................................16.....18.............................................................17.....1....................LTE RL60...............2 Requirements.19. 166 4......16............... 146 4..........1................................................1.....................18.....................................150 4..... 169 4....1 Description of LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB)..................................................... Feature Descriptions and Instructions 4.19......1 Benefits.... ........20............................2 Activating and configuring LTE1755: Multiple emergency areas per cell.............................................211 4...20..1 Description of LTE1534: Multiple Frequency Band Indicator..23........ 207 4..............1................................................ 181 4.176 4......1.. 176 4.6 Sales information...2 Requirements..... 207 4.................................1.. 187 4..................................5 LTE1755: Multiple emergency areas per cell management data...........................4 System impact. 175 4................................21...........1............................21............23... 178 4...4 System impact....................1.21.........3 Deactivating LTE1531: Inter-frequency Load Balancing Extension..............................................1...3 Functional description................ 196 4.......21.1....5 LTE1677: Management data........................1...................21..21................... 207 4...........................212 4.1...................................183 4....................................... 206 4...................1.........................................................4 System impact............................................. 188 4............191 4............1..4 System impact...............23.........6 Sales information.........22 LTE1677: Idle Mode Mobility Balancing Extensions..........186 4.......2 Activating and configuring LTE1677: Idle Mode Mobility Balancing Extensions...........21..........1 Description of LTE2008: Extended Inter-frequency Measurements.............................................21 LTE1534: Multiple Frequency Band Indicator.6 Sales information........3 Deactivating LTE1677: Idle Mode Mobility Balancing Extensions....................2 Requirements.............24 LTE2008: Extended Inter-frequency Measurements.........21..1............................................2 Activating LTE1534: Multiple Frequency Band Indicator...........................1.5 Management data...... 181 4......23.20...........3 Functional description...................209 4.. 188 4.................3 Functional description... Feature Descriptions and Instructions 4.....22....1. 178 4.................... 189 4.23.............22..................................3 Deactivating LTE1534: Multiple Frequency Band Indicator... 209 4........22..............3 Functional description....................... 212 5 Descriptions of transport and transmission features.........22.......23..............................181 4... 181 4..............................20............1..23......22...........208 4....1 Benefits..........6 Sales information................................24....... 209 4............................22........................... 215 8 © 2016 Nokia DN09185955 Issue: 01J .......1....2 Activating LTE1531: Inter-frequency Load Balancing Extension.21.............2 Requirements.............................5 Management data.............23....... 188 4..........1....... 184 4..........1...............1......................1 Description of LTE1755: Multiple emergency areas per cell..........3 Deactivating LTE1755: Multiple emergency areas per cell.....................................................22... 208 4.1 Benefits.................................196 4..................... 180 4......................................20.............................1....... 186 4......23............ 181 4...................1...23 LTE1755: Multiple emergency areas per cell.....................189 4.....................................22..20...1 Benefits...1 Description of LTE1677: Idle Mode Mobility Balancing Extensions........1...................22....................... 192 4..... LTE RL60..........208 4........................ ... 225 5...........2 Activating and configuring LTE1401: Measurement-based Transport Admission Control..................1 Description of LTE1401: Measurement based TAC.......... 238 5.........1......................1..3.............................1 User scenario...... 227 5..................2 LTE125 - IPv6 for U/C-Plane requirements..........215 5...3....2 LTE1401:Measurement based TAC requirements.......2 LTE1460: Local and Remote IP Traffic Capturing requirements......2....3...........1........2..........1 Fast Fallback mechanism................1...1.......3..2........ 228 5..........................................3..221 5......LTE RL60...................4 LTE1390: IPsec Emergency Bypass system impact...............222 5.1...1...........1..........3.1 Description of LTE125: IPv6 for U/C-Plane..............4 LTE125- IPv6 for U/C-Plane system impact..1. 231 5...3..3..1.........1.........3..........1.......3 LTE125 - IPv6 for U/C-Plane functional description...1........2......................3 Deactivating LTE1390: IPsec Emergency Bypass..1...........1........................................................1... 215 5. 217 5...................4 LTE1460: Local and Remote IP Traffic Capturing....4 LTE1401:Measurement based TAC system impact........... 237 5................1. 233 5..3 LTE1390: IPsec Emergency Bypass functional description.. 226 5......1................5 LTE1401:Measurement based TAC management data..........1....2 Local IP Address Configuration.....2.........6 LTE1390: IPsec Emergency Bypass sales information.........................1.1 LTE1390: IPsec Emergency Bypass benefits...............................4.. 231 5...........................3..........1....237 5.......................2..........1.... 241 DN09185955 Issue: 01J © 2016 Nokia 9 ............. 215 5.............218 5............3 LTE1401: Measurement based TAC.1.. 215 5.2 Activating the LTE1390: IPsec Emergency Bypass feature using BTS Site Manager........3 Deactivating LTE1401: Measurement-based Transport Admission Control....... 225 5...3... 235 5..... 232 5...............1 LTE1460: Local and Remote IP Traffic Capturing benefits.1..217 5.................6 LTE1401:Measurement based TAC sales information.............................1....5 LTE125- IPv6 for U/C-Plane management data......1................................5 LTE1390: IPsec Emergency Bypass management data..............3...1 Migration...........1.223 5..4....2 Activating and configuring LTE125: IPv6 for U/C-Plane..... 217 5............. 238 5......1 LTE125 - IPv6 for U/C-Plane benefits..................... 224 5.................2..2.......3 LTE1460: Local and Remote IP Traffic Capturing functional description.....4.1...1 LTE1401:Measurement based TAC benefits......2 LTE1390: Emergency Bypass requirements..2.........................237 5...1.3 LTE1401:Measurement based TAC functional description. 237 5.............................1.....1.........4.............................3 Remote U/C-Plane IP Address Configuration.3 Deactivating LTE125- IPv6 for U/C-Plane................. 236 5.....1....1.229 5.....................................1..... Feature Descriptions and Instructions 5..... 225 5.... 215 5....3....1..........1 LTE125: IPv6 for U/C-Plane...1 Description of LTE1460: Local and Remote IP Traffic Capturing........ 215 5.........1 User scenarios..229 5..6 LTE125- IPv6 for U/C-Plane sales information..1 Description of LTE1390: IPsec Emergency Bypass.......................................1..............1.....4. 237 5..................2 LTE1390: IPsec Emergency Bypass............................1..........................239 5..3......1. 231 5.................1....3. 234 5...................232 5............... 225 5..........3.....1.......... ......... 244 6..257 6................1.......3. 255 6............................................................... 268 6...6 Sales information.........3...1........................................................1 Description of LTE1245: Revocation Management.................1...6 LTE1460: Local and Remote IP Traffic Capturing sales information ..2 LTE954: Intelligent configuration synchronization ..........1.......................................................1......................................................................1.............................. 256 6......... 258 6...................................4 System impact...........3 Functional description.............6 Sales information.2..... Inter-frequency - UE Based.............261 6...............1........................................................1 Benefits...2..................................... 258 6.................4.. 261 6.............. 257 6.1... 244 6.. 258 6...................2................................266 6... 272 10 © 2016 Nokia DN09185955 Issue: 01J .......................2...1...........3................................ 256 6.........2 Requirements...................2 Configuring LTE954: Intelligent configuration synchronization.2 Requirements.................................................... 267 6.................. Inter-frequency - UE Based............................... 243 5.. Inter-frequency - UE Based............................................1.5 Management data.................................... 261 6..........4 LTE1361: Additional QoS performance measurements....... 245 6......2 Requirements............................1...1............ 251 6......3 Removing the configuration of LTE954: Intelligent configuration synchronization.3....1........................ 242 5..............5 LTE1245: Revocation Management management data................4.........3 Deactivating LTE556: ANR Intra-LTE..................3 Deactivating LTE1460: Local and Remote IP Traffic Capturing............1.3......3....249 6................3 Functional description........... 256 6........ 243 5....4 System impact..243 5............................2...1...1.3...... 243 6 Descriptions of operability features..................................................4.......1............... 260 6........2 Activating LTE556: ANR Intra-LTE.......2 Activating and configuring the LTE1245: Revocation Management feature using BTS Site Manager.........................1.........244 6......1..............1 Description of LTE954: Intelligent configuration synchronization....1......................1 LTE556: ANR Intra-LTE........3 Functional description................4........ 268 6..1..2.2...................2.....1.................1..1........................................... LTE RL60....3 LTE1245: Revocation Management ...................................4......................4 LTE1460: Local and Remote IP Traffic Capturing system impact................... 250 6..1................................................................. 260 6...................................1 Description of LTE556: ANR Intra-LTE......................... 244 6.....5 Management data........... Feature Descriptions and Instructions 5........ 251 6...............1.....1.................6 Sales information....4 System impact........ 244 6..3.............................1...1...... 260 6.................................... Inter-frequency - UE Based..1.....1 Benefits...............................1 Benefits............................3 Deactivating LTE1245: Revocation Management....3........................................5 LTE1460: Local and Remote IP Traffic Capturing management data....257 6.............................................................. 272 6..............2 Activating and configuring LTE1460: Local and Remote IP Traffic Capturing..2...................... ........2 Requirements..............4.8 LTE1708: Extend Maximum Number of X2 Links............................................1....................................................... 279 6........................5.............................4.............1 LTE1909 benefits..274 6..................... 287 6...1 Benefits..............................................2 Requirements..4 System impact......3 Functional description.......1............1. 289 6.....................3 Functional description...................................8..8......6........5 Management data.........9 LTE1909: BTS Diagnostics Toolkit used by operator................................1.....5 Management data........... 282 6....... 296 6.......... 279 6.....1...........1.....5...............................292 6.................... 288 6.......1..3 Functional description................1....................5 Management data.......... 286 6......... 288 6...3 Functional description..LTE RL60........1 Description of LTE1361: Additional QoS performance measurements..................................1...5 LTE1560: System Upgrade to RL60 management data.....................................................................7 LTE1657: Support for Multi-antenna RET device ............. 296 6..........................287 6.............................288 6........1 Description of LTE1486 : Parameter Categorization ....................... 280 6..5...1.......1 Benefits..........................................5 Management data.................................................7..................................... 288 6.....1.............6.... 272 6..........286 6......1...1..................1..........8..............................................4 System impact.........................2 Requirements.........................6 Sales information.6...................7......................................6..........................5....1.......7....4.......................................................... 295 6......... 288 6...........................................6.6 Sales information..............1 Benefits............1......4......9.....................5......................................................... 282 6............................1 Description of LTE1708: Extend Maximum Number of X2 Links ..1............................. 293 6..........................1 Benefits............1...7.......................................6 LTE1560: System Upgrade to RL60..........1..................5.........1....6 Sales information.....................280 6....1.285 6.......................9............. 287 6.................................5....8.........5 LTE1486: Parameter Categorization.......................................1...........288 6.............................................................................................282 6.8.4 System impact...............................................1..1........................2 Requirements.......1 Description of LTE1657: Support for Multi-antenna RET device ...............1...............................................1.. 273 6............. 279 6........................4 System impact............................ 282 6...............................6 Sales information............4............1 Description of LTE1909: BTS Diagnostics Toolkit used by operator .......8........................................8.....1...... 281 6.273 6...........................................4..1 Description of LTE1560: System Upgrade to RL60...7.. 275 6............................1.....6......................................7......7................................2 Requirements.........6..1.........1..... 272 6..... 286 6..................1.................................... 280 6........................ 296 DN09185955 Issue: 01J © 2016 Nokia 11 .............. 282 6..........6 Sales information.........................................4................1 Benefits..........3 Functional description..................................................... Feature Descriptions and Instructions 6..... 286 6.................................................................................287 6.281 6...................282 6........4 System impact............ 1 LTE1440: FXFC Flexi RF Module 3TX 1900.......................................1....................................3 LTE1508 Functional description...1...308 7..................1 LTE1444 benefits..................2 LTE1909 requirements................ 297 6...................3 LTE1444 functional description......................9......305 7...... 304 7..................1............................5 LTE1909: BTS Diagnostics Toolkit used by operator management data...........................9....................2.............................2 LTE1440 requirements.......................1...............1 LTE1910 benefits....................1................6 LTE1910 sales information................... 299 6.......1...............................................................3.....6 LTE1444 sales information..............1.......1............3....... 304 7..1............3....9.. 309 7.................................3 LTE1508: Multiradio System Module Full LTE Configurations..2.....................9.. 305 7.1.......3 FXFC functional description....1 LTE1440 benefits............................1.3........ 303 7......1. 300 6...............1...................................1...............................1......1...................298 6.........2.............6 LTE1909 sales information..................301 6...............................................4 LTE1444 system impact...303 7.......................... 306 7......1.10...................2 LTE1910 requirements....................1.........................2 LTE1508 Requirements..1.............1 LTE1508 Benefits...... 297 6...............1...............................................5 LTE1910: S1 lock/unlock management data.....299 6.........9....5 LTE1440: FXFC Flexi RF Module 3TX 1900 management data............................3............................................. 298 6...... 305 7............................. 310 7.. 310 12 © 2016 Nokia DN09185955 Issue: 01J ...1...........302 7 Descriptions of BTS site solution features................ 304 7....................................................... 301 6..................9..........................1.................303 7.....................1..6 LTE1440 sales information.4 LTE1910 system impact..............1.......................................10.......................................................................1 Description of Multiradio System Module full LTE configurations ..................................................299 6....................1 Description of LTE1910: S1 lock/unlock....10........1........4 LTE1440 system impact........... Feature Descriptions and Instructions 6.........10.............1 Description of LTE1444: FBBC Flexi Capacity Extension Sub- Module................10 LTE1910: S1 lock/unlock...1...5 LTE1444: FBBC Flexi Capacity Extension Sub-Module management data.....................................................1 Description of LTE1440: FXFC Flexi RF Module 3TX 1900....1..... 307 7....2 Triggering snapshot collection using LTE1909: BTS Diagnosis Toolkit................305 7.3. LTE RL60.................2 LTE1444 requirements.3 LTE1909 functional description......... 299 6......... 305 7......1..2.............................10.........................2...................... 297 6..1....................................1.............................10................................... 308 7....................... 296 6......307 7.....................................1...........3 LTE1910 functional description.............................1..1.....1....4 LTE1508 System impact....................................... 303 7.5 LTE1508: Multiradio System Module full LTE configurations management data.....3..1....10..... 308 7.........2.................... 303 7.....2.............2 LTE1444: FBBC Flexi Capacity Extension Sub-Module...6 LTE1508 Sales information..1...........................4 LTE1909 system impact. 308 7.. 309 7............ 307 7........ ............6 LTE1644 Sales information...................................2 LTE1644 Requirements...................................319 7.7.....315 7...5................5.............................................5....6.....1.........................6...5................. 318 7.............................................................5 LTE1665: FXFB Flexi 3-sector RF Module 1900 management data.......................6 LTE1895 sales information.........................................................1...1........4 LTE1695 system impact......................................................... 316 7...1 Description of LTE1952: LTE GSM/WCDMA RF-sharing for Band 2 (1900MHz).4 LTE1665 system impact........................................................ 315 7..1...1...4..1 Description of LTE1895: LTE-GSM and LTE-WCDMA RF sharing for dual band configurations..................... 321 DN09185955 Issue: 01J © 2016 Nokia 13 ...6..........6 LTE1695: FXCB Flexi RF Module 850..............310 7...1............................................... 315 7.............. 312 7........6.......1................................................9.............1............................. 313 7. 314 7.......7.........................................5 LTE1695: FXCB Flexi RF Module 850 management data.............................................1 Description of LTE1915: RF sharing LTE-WCDMA with FSMF for WCDMA.....3 LTE1665 functional description......1....................4................1.....................4 LTE1644 System impact.............6........................ 314 7..................................... 313 7..............1 LTE1952 benefits.......... 316 7. 319 7..................1................. 316 7...................1................2 LTE1895 requirements..........9.8........1....... 311 7.....................................................1............ 315 7.......1 LTE1895 benefits......................................4......6 LTE1695 sales information........................... 314 7......311 7............................................5 LTE1895: LTE-GSM and LTE-WCDMA RF sharing for dual band configurations management data.4.....7.8 LTE1915: RF sharing LTE-WCDMA with FSMF for WCDMA... 315 7...... 310 7........ 317 7....................5 LTE1665: FXFB Flexi 3-sector RF Module 1900..................5 LTE1644: Multiradio System Module extended LTE configurations with FBBC management data........... 321 7..2 LTE1695 requirements.................3 LTE1895 functional description.............LTE RL60.......319 7....5........1..........1.................................................1............................5........1...1...... 319 7..................4..............1.......................7 LTE1895: LTE-GSM and LTE-WCDMA RF sharing for dual band configurations...................... 317 7..................................3 LTE1695 functional description........1............4..317 7..........4............3 LTE1644 Functional description....................................4 LTE1895 system impact.......7.......9 LTE1952: LTE GSM/WCDMA RF-sharing for Band 2 (1900MHz)..........2 LTE1665 requirements.....................................1 LTE1695 benefits.....1 Description of Multiradio System Module extended LTE configurations with FBBC................. 318 7..........317 7...........1..............7..............317 7.............. 313 7............... 321 7... 312 7.7.. 310 7...............................1...........................................4 LTE1644: Multiradio System Module Extended LTE Configurations with FBBC...... 315 7......1 Description of LTE1695: FXCB Flexi RF Module 850.......313 7...7...................................................1 Description of LTE1665: FXFB Flexi 3-sector RF Module 1900........................................................6.............1 LTE1665 benefits..... Feature Descriptions and Instructions 7.......5..................1 LTE1644 Benefits..1...6 LTE1665 sales information....6..1.... ................9...............1.1.......1............1.........9.. 322 7........ LTE RL60..................4 LTE1952 system impact..... Feature Descriptions and Instructions 7........................................... 322 7........................................... 322 7........1...322 14 © 2016 Nokia DN09185955 Issue: 01J ......................5 LTE1952: LTE GSM/WCDMA RF-sharing for Band 2 (1900MHz) management data.........................2 LTE1952 requirements... 321 7....................9.............3 LTE1952 functional description.......................6 LTE1952 sales information..9....9................ ................................................................................. 240 Figure 14 Capturing mechanism..............................................LTE RL60.....47 Figure 4 Interference-aware UL power control diagram............................................... 298 Figure 23 Isometric view of FBBC............................................................... 28 Figure 2 HO from UTRAN execution........................ 306 Figure 24 FBBC LEDs........................... 218 Figure 10 Traffic path in IPsec Emergency Bypass mode.......................................... 247 Figure 18 Automatic establishment of an inter-frequency NR.. IPsec enabled..... 262 Figure 21 Top-down approach for the system upgrade...................................217 Figure 9 Migration example with IPsecv4/v6 tunneling in Transport Network...................... 113 Figure 5 UL CoMP scenario.. 283 Figure 22 Selecting triggers for eNB snapshot collection................................................................................................... 136 Figure 6 Protocol layer between E-SMLC and eNB........... 306 DN09185955 Issue: 01J © 2016 Nokia 15 ..................................................... Inter-frequency UE Based neighbor discovery: radio frequency (RF) part............................................... Feature Descriptions and Instructions List of Figures Figure 1 HO from UTRAN preparation......................................... of different type and fully overlap.......................... 262 Figure 20 SEG's chain of trust..................................................................................................................................................... 227 Figure 11 Overview............................................241 Figure 15 ANR Intra-LTE......... 216 Figure 8 Example configuration: U/C - application binding to IPv6........................................................................................................ 141 Figure 7 Example Configuration: IPv6 migration support.............................................................................234 Figure 12 Network Operation Center...... 247 Figure 17 Inter-eNB neighbor cells at different frequency bands. 29 Figure 3 RIM protocol structure between E-UTRAN and GERAN...................................239 Figure 13 Capture points............................... 248 Figure 19 Cross-signed certificates in eNB............................................ 246 Figure 16 Intra-eNB neighbor cells at different frequencies and fully overlap......................................................................................................................... ..................................... 23 Table 2 Software requirements.......... 54 Table 19 Sales information.........................................................................................................................60 Table 23 Software requirements........................................................................................... 74 Table 34 Software requirements........................................................................... 62 Table 24 Counters.......................73 Table 33 Parameters used for activating and configuring LTE944: PUSCH masking................. 50 Table 16 Sales information....................51 Table 17 Parameters used for activating and configuring LTE498: RAN Information Management for GSM......................................................................32 Table 5 Parameters used for activating and configuring LTE57: Inter RAT handover from UTRAN................................................................................. 38 Table 9 Parameters...............................................................................................................................................66 Table 27 Sales information................................................................................................................................................... 60 Table 22 Sales information.................. 67 Table 29 Software requirements............................................................... 39 Table 10 Sales information...................... 31 Table 4 Sales information.................................................................................................................................................................................................................................................................................................................................................................. 49 Table 14 New parameters...............................................................41 Table 12 Software requirements..................................................................................... 73 Table 31 Related existing parameters................................................... 66 Table 25 New parameter..............................................................................................................................41 Table 11 Parameters used for activating and configuring LTE60: Inter RAT handover to eHRPD/3GPP2....................... 70 Table 30 New parameters.................................................................................. 66 Table 26 Updated or reused parameters....................55 Table 20 Software requirements..................................38 Table 8 Counters.................................................................................................67 Table 28 Parameters used for activating and configuring LTE874: CSFB to CDMA/1xRTT for dual RX UEs..................................... LTE RL60................................................. 32 Table 6 Software requirements......................79 16 © 2016 Nokia DN09185955 Issue: 01J ...........................................................................................................................................................73 Table 32 Sales information................................................................................. 46 Table 13 Modified alarms............................... 50 Table 15 Related parameters..... 77 Table 35 New counters............................................................................................... 59 Table 21 New parameter......................................................................................................... 27 Table 3 New parameters............................ 51 Table 18 Software requirements.......................... 34 Table 7 Measurements...................................................................... Feature Descriptions and Instructions List of Tables Table 1 RL60 Features - not supported by Flexi Zone Micro.................................................... ....................... 104 Table 56 Related existing key performance indicators..........................................................121 Table 68 Sales information........................................85 Table 44 Parameters used for activating and configuring LTE1074: Multimedia priority services..........121 Table 69 Parameters used for configuring LTE1342: Extended RNC ID...................................................................................................................................................................105 Table 57 New parameters............................................................................................ 90 Table 47 Sales information.......................... 115 Table 63 New parameters..................................................................................... 85 Table 43 Sales information............................................................91 Table 48 Parameters used for activating and configuring LTE1198: RSRQ triggered mobility.......................................................................................... 79 Table 37 Sales information.....................................................................................................................................................................................................................................................................................................................................................................97 Table 53 Parameters used for activating and configuring LTE1231: Operator specific GBR QCIs.....................112 Table 62 Existing counters...... 89 Table 46 Parameters................................ 105 Table 58 Related existing parameters................................................................................................................................................................................................................... 80 Table 39 Software requirements...86 Table 45 Software requirements...............................106 Table 60 Parameters used for activating and configuring the LTE1332: Downlink Carrier Aggregation - 40 MHz........................................................... 115 Table 64 Sales information....................................................97 Table 54 Software requirements..... 96 Table 51 Related existing parameters........................... 125 Table 71 Related existing counters.................................................................... 106 Table 61 Software requirements.............................................. 100 Table 55 Related existing counters....................................................................................... 82 Table 40 Existing counters...............................80 Table 38 Parameters used for activating and configuring LTE1047: Control plane overload handling.......................105 Table 59 Sales information.............................................................................................................................................................................................................................96 Table 52 Sales information..............................................................................................119 Table 67 Related existing parameters....................................................................................................................................... 94 Table 50 New parameters............ 122 Table 70 Software requirements............................................................................................... Feature Descriptions and Instructions Table 36 New parameters...... 116 Table 65 Parameters used for activating and configuring LTE1336: Interference aware UL power control.. 116 Table 66 Software requirements..................................................... 91 Table 49 Software requirements..................................................................... 84 Table 41 New parameters.................................................................LTE RL60................ 85 Table 42 Related parameters................ 128 DN09185955 Issue: 01J © 2016 Nokia 17 ............................................................. ........................ 152 Table 88 New parameters...................................... 181 Table 107 New parameters......................................................................................................................................................169 Table 96 New parameter.. 178 Table 106 Software requirements.......................................................................................... 159 Table 93 Software requirements.....................................170 Table 100 Parameters used for activating and configuring LTE1495: Fast uplink link adaptation................................................................144 Table 84 Sales information................................................................................................................................ 129 Table 73 Related existing parameters..... 137 Table 79 Sales Information.......... LTE RL60...........131 Table 76 Software Requirements............................................129 Table 74 Sales information............................................................................................. 135 Table 77 New counters..............................................................................170 Table 99 Sales information.....................................................................................................................................................................................................................................................178 Table 105 Parameters used for activating and configuring LTE1531: Inter- frequency Load Balancing Extension...............................................................144 Table 86 Software requirements................138 Table 81 Software requirements................................................................ 143 Table 83 Related existing parameters......................138 Table 80 Parameters used for activating and configuring LTE1402: Uplink Intra- eNB CoMP.. 175 Table 102 New parameters........................................................................................................................................................................................................................... 167 Table 94 Related existing counters................................................................................................................................. 147 Table 87 Related existing counters.............................................................................................. 169 Table 95 Related existing key performance indicators...........144 Table 85 Parameters used for activating and configuring LTE1433: LPPa support for OTDOA.................................................... 185 18 © 2016 Nokia DN09185955 Issue: 01J ............158 Table 91 Sales information................................................131 Table 75 Parameters used for activating and configuring LTE1382: Cell resource groups..................................................................................................................................................................................... 141 Table 82 New parameters..159 Table 92 Parameters used for activating and configuring LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB)......................................................................................... 177 Table 104 Sales information........................................................................................170 Table 98 Related existing parameters........ 177 Table 103 Related parameters......................................................................................................................................................................... 155 Table 90 Related existing parameters........................... 153 Table 89 New parameters.................... Feature Descriptions and Instructions Table 72 New parameters................................................................................. 170 Table 97 Modified parameters.....................................................137 Table 78 New parameters............................................. 171 Table 101 Software requirements........................................................ ........................... 193 Table 113 Related existing parameters..................... 208 Table 117 Related existing parameters............194 Table 114 Sales information....LTE RL60................................... 233 Table 136 New counters............. Feature Descriptions and Instructions Table 108 Related existing parameters.....214 Table 123 Software requirements.................................................................................................... 223 Table 129 Software requirements................................................................... 209 Table 120 Hardware and software requirements... 244 Table 143 Resulting ANR method toward target frequency F2......................................................................................................................... 186 Table 111 Software requirements............. 228 Table 131 New parameters....................185 Table 109 Sales information................................................................................................................................................................ 238 Table 140 New Alarms............ 237 Table 138 Sales information.............................................................................................. 249 DN09185955 Issue: 01J © 2016 Nokia 19 .................................................................................237 Table 139 Software requirements...........................................196 Table 115 Parameters used for activating and configuring LTE1677: Idle Mode Mobility Balancing Extensions........................................................................ 221 Table 125 New parameters.........................................................................222 Table 128 Parameters used for activating and configuring LTE125- IPv6 for U/C- Plane....................................................................................................... 226 Table 130 New Alarms............... 232 Table 135 Standardized QCI characteristics............................................................................. 189 Table 112 New parameters..........................................................236 Table 137 New parameters........................... 215 Table 124 New Alarms................................................................................................................................. 214 Table 122 Sales information...........................................................................................................................................................................................................................................................................................................................................................................................................................................................186 Table 110 Parameters used for activating and configuring LTE1534: Multiple Frequency Band Indicator......................................................................243 Table 142 Software requirements..................................................................... 229 Table 134 Software requirements....................... 212 Table 121 New parameters............................. 243 Table 141 Sales information................................................................................................................................................ 229 Table 132 Sales information......209 Table 119 Parameters used for configuring LTE1755: Multiple emergency areas per cell................................................. 197 Table 116 Software requirements..............................................................................................................................209 Table 118 Sales information....................................................229 Table 133 Parameters used for activating and configuring the LTE1390: IPsec Emergency Bypass feature..........................................................................................222 Table 127 Sales information.................................. 222 Table 126 New Parameters with structure Static IPv6 Routes Set (staticIpv6Routes).................................................................................... ................................. 295 Table 175 Related existing parameters........................................................................279 Table 162 Sales information................258 Table 152 Software Requirements....................................................................... 282 Table 166 Related existing alarm...........282 Table 165 Software Requirements.................................................................................................................................... 303 20 © 2016 Nokia DN09185955 Issue: 01J ..... 289 Table 172 Related existing alarms.....................................298 Table 179 Software Requirements................. 293 Table 174 New parameters........................................................................................................................................... 278 Table 161 New Parameters......................................................288 Table 170 Software Requirements.................................................................................................................. 299 Table 180 New Alarms............279 Table 163 Software Requirements..................................................................... 293 Table 173 Related existing counters....................................................................................................................................................... LTE RL60........................................................................................................................................................................ 286 Table 167 Sales Information. 287 Table 169 Sales Information....................... Inter-frequency - UE Based.....................................................................................251 Table 147 Sales information.................................268 Table 157 Parameters used for activating and configuring the LTE1245: Revocation Management feature.............................. 261 Table 153 Modified alarms..................................................................... 289 Table 171 Maximum number of supported neighbor objects........................ 280 Table 164 Sales Information.........................................................251 Table 148 Parameters used for activating and configuring LTE556: ANR Intra- LTE............................................................................................................275 Table 160 New key performance indicators ..............................................................................................................................302 Table 182 Software Requirements................................................................... 267 Table 154 New parameters......................... 268 Table 158 Software Requirements..................................................................................................... 257 Table 150 New parameters..................................................................................................................................................... 250 Table 146 Related existing parameters................................286 Table 168 Software Requirements...................................... Feature Descriptions and Instructions Table 144 Related existing counters.295 Table 177 Software requirements......................................................................................................................... 296 Table 178 Sales Information........................................................................................... 267 Table 155 Related existing parameters................................................................ 302 Table 181 Sales Information.............................295 Table 176 Sales Information.............................268 Table 156 Sales Information.................................................................................................. 250 Table 145 New parameters............................................................................ 258 Table 151 Sales Information................................... 273 Table 159 New Measurements and counters..........................251 Table 149 Software Requirements............................................................................. .....................LTE RL60...................................................307 Table 186 Software Requirements.............................................................. 311 Table 190 Existing parameters related to LTE1644.........................310 Table 189 Software Requirements.................... 308 Table 187 Number of extra new RF units ................... 316 Table 195 Sales Information...........................................................................................................................322 DN09185955 Issue: 01J © 2016 Nokia 21 .................................................309 Table 188 Sales Information..................................................................................................................................................313 Table 192 Software Requirements........................................................315 Table 194 Software Requirements............................................................................. 317 Table 197 Sales Information........................................................................................................................... 305 Table 185 Sales information...................................................... 312 Table 191 Sales Information.........................................317 Table 196 Software Requirements....................................................319 Table 198 Hardware and software requirements...................................321 Table 200 Software Requirements............................................. 320 Table 199 Sales information........................................................................... 321 Table 201 Sales Information................................................................................................................................................. 314 Table 193 Sales Information..................................................................... Feature Descriptions and Instructions Table 183 Sales Information.................................305 Table 184 Software requirements..... RL60) and 01H (2016-02-19. FDD-LTE16A) and 01J (2016-07-25. FDD- LTE16A) Radio Resource Management The following feature has been updated: • LTE1382: Cell resource groups • LTE498: RAN Information Management for GSM • LTE874: CSFB to CDMA/1xRTT for dual RX Ues • LTE1441: Enhanced CS fallback to CDMA/1xRTT (e1xCSFB) • LTE1332: Downlink Carrier Aggregation - 40 MHz Operability The following features have been updated: • LTE556: ANR Intra-LTE. Feature Descriptions and Instructions Summary of changes Changes between issues 01I (2016-06-29. FDD-LTE16) and 01I (2016-06-29. Inter-frequency - UE Based • LTE1708: Extend Maximum Number of X2 Links Transport The following feature has been updated: • LTE125: IPv6 for U/C-Plane • LTE1460: Local and Remote IP Traffic Capturing Changes between issues 01G (2015-09-30. FDD-LTE 16) BTS Site Solution The following features have been updated: • LTE1508: Multiradio System Module full LTE configurations • LTE1644: Multiradio System Module extended LTE configurations with FBBC 22 © 2016 Nokia DN09185955 Issue: 01J . FDD- LTE16) Radio Resource Management The following feature has been updated: • LTE1332: Downlink Carrier Aggregation - 40 MHz Changes between issues 01H (2016-02-19. Summary of changes LTE RL60. LTE RL60. Feature Descriptions and Instructions RL60 Features - not supported by Flexi Zone Micro 1 RL60 Features .not supported by Flexi Zone Micro The following features are not supported by Flexi Zone Micro: Table 1 RL60 Features - not supported by Flexi Zone Micro Features Category LTE1332: Downlink carrier aggregation - 40 MHz RRM LTE1402: Uplink Intra-eNB CoMP RRM LTE1440: FXFC Flexi RF Module 3TX 1900 BTS LTE1444: FBBC Flexi Capacity Extension Sub-Module BTS LTE1508: Multiradio System Module full LTE configurations BTS LTE1560: System Upgrade to RL60 Operability LTE1644: Multiradio System Module extended LTE configurations with FBBC BTS LTE1657: Support for Multi-antenna RET device Operability LTE1665: FXFB Flexi 3-sector RF Module 1900 BTS LTE1695: FXCB Flexi RF Module 850 BTS LTE1895: LTE-GSM and LTE-WCDMA RF sharing for dual band configurations BTS LTE1915: RF sharing LTE-WCDMA with FSMF for WCDMA BTS LTE1952: LTE GSM/WCDMA RF-sharing for Band 2 (1900MHz) BTS DN09185955 Issue: 01J © 2016 Nokia 23 . Feature Descriptions and Instructions 2 Introduction This document provides the list of feature descriptions for the LTE Radio Access Network Release. Introduction LTE RL60. The subchapter Interdependencies between features lists only dependencies among Nokia RAN LTE features. If the feature has no specific hardware requirements. 24 © 2016 Nokia DN09185955 Issue: 01J . Hardware (HW) requirements indicate if the feature requires specific HW from the RAN LTE portfolio. it means that only LTE System Module should be used. located in the Target section. or from a remote location. For information on feature-specific prerequisites. For details. Feature Descriptions and Instructions Activating and deactivating LTE features using BTS Site Manager 3 Activating and deactivating LTE features using BTS Site Manager Purpose Follow this general BTS Site Manager (BTSSM) procedure to activate or deactivate LTE features. For details. it automatically uploads the current configuration plan file from the eNB. This is the recommended setting. Before you start The eNB must already be commissioned. b) The BTS Site checkbox. c) Choose the commissioning type. see Launching BTS Site Manager in Commissioning Flexi Multiradio BTS LTE or the BTSSM online help (section Instructions). The BTS Site Manager can be connected to the eNB either locally. 2 Upload the configuration plan file from the eNB. The feature-related settings are found in the set of Commissioning pages. or Reconfiguration option depending on the actual state of the eNB. When the BTSSM is connected to the eNB. see section Before you start of every feature-specific procedure. Steps 1 Start the BTSSM application and establish the connection to the eNB. Manual. In the top right-hand corner of the BTSSM window. see Manual commissioning. Performing template commissioning. a) Select View ► Commissioning or click Commissioning on the View bar. there is a location bar that shows at which stage of the Commissioning process the user is. LTE RL60. and Performing reconfiguration commissioning in Commissioning Flexi Multiradio BTS LTE. is selected by default. 3 Modify the feature-specific eNB configuration settings. Use the Template. It is recommended that the user carefully reads the pages containing full eNB configuration information. DN09185955 Issue: 01J © 2016 Nokia 25 . g Note: For information on possible restarts. Sub-steps a) After successful transmission of the parameters. or a whole set of parameters: All parameters (requires reset). 5 The new commissioning plan file is automatically activated in the eNB. b) If the configuration changes require restart. c) Click the Send Parameters button. Activating and deactivating LTE features using BTS Site LTE RL60. see section Before you start of every feature -specific procedure. 26 © 2016 Nokia DN09185955 Issue: 01J . the new configuration is automatically activated. the eNB performs the restart now. The BTSSM automatically sends an activation command after finishing the file download. Sub-steps a) Go to the Send Parameters page. choose whether the BTSSM should send to the eNB only the changed parameters: Only changes (may require reset). b) In section Send. Feature Descriptions and Instructions Manager 4 Send the commissioning plan file to the eNB. 3 Functional description The LTE57: Inter RAT handover from UTRAN feature provides support for inter-IRAT handover of UEs from UTRAN (WCDMA & TD-SCDMA).2 Requirements Software requirements Table 2: Software requirements lists software required for this feature.1. DN09185955 Issue: 01J © 2016 Nokia 27 . peak rates and latency. - Hardware requirements This feature requires no new or additional hardware.1. 4.1. Table 2 Software requirements System release Flexi Multiradio BTS Flexi Multiradio OMS 10 BTS RL60 LBTS6.1. LTE RL60. 4. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4 Descriptions of radio resource management and telecom features 4. Operator benefits The operator delivers an improved service quality for his customers.1 LTE57: Inter RAT handover from UTRAN 4. in LTE as in UTRAN.1.1 Benefits End-user benefits This feature provides a better service quality experience for the end user.1. The handover procedure is initiated by the RNC (Radio Network Controller).1. 4.0 LBTS6. An inter-RAT handover for a UE from UTRAN (WCDMA and TD-SCDMA) to LTE is possible. Incoming IRAT Handover Requests are treated the same way as incoming intra-LTE S1-based handover requests with the exception that data forwarding is not supported and no delta configuration is done.0 - UE NetAct MME SAE GW 3GPP R8 UE capabilities NetAct8 EP1 .1 Description of LTE57: Inter RAT handover from UTRAN Introduction to the feature The LTE57: Inter RAT handover from UTRAN introduces active mode mobility from UTRAN to LTE. If the IE NAS Security Parameters to E-UTRAN is missing. as the handover source is outside LTE. as-Context. Descriptions of radio resource management and LTE RL60. the eNB rejects the HO Request with the cause value Protocol Cause(Abstract Syntax Error (Reject)). • UTRAN Source System-specific security setting is applied. • NAS Security Parameters to E-UTRAN are present. • The RRC Container within the Source eNB to Target eNB Transparent Container does not contain as-Config. If LTE57: Inter RAT handover from UTRAN is deactivated. The eNB gets during the handover preparation phase an S1AP:HANDOVER REQUEST message from the MME. 28 © 2016 Nokia DN09185955 Issue: 01J . the eNB verifies that feature LTE57: Inter RAT handover from UTRAN is activated. Feature Descriptions and Instructions telecom features Handover from UTRAN is - similar as S1-based intra-LTE handover - one application of the generic incoming S1-based handover procedure. For Handover from UTRAN the eNB can only have the role of the Target eNB. Figure 1 HO from UTRAN preparation UE eNB UTRAN SGSN MME S-GW/P-GW RANAP:Relocation Required HOpreparationwithinEPC S1AP:HandoverRequest (HandoverType=UTRANtoLTE) AdmissionControl and ResourceAllocation S1AP:HandoverRequestAcknowledge (RRCContainerincludingHandoverCommandmessageforUE) TS1RELOCexec Messageforwarding RANAP:Relocation Command Following Parameters have a specific use in case of incoming HO from UTRAN: • The handover type is set to UTRANtoLTE. • Measurement configuration via the target cell after handover execution becomes mandatory as no previous measurement configuration is configured in the UE. If the eNB detects that the incoming HO is from Source RAT UTRAN. From a Target eNB's point of view the procedure is very similar to incoming intra-LTE handover with the following exceptions: • No data forwarding is applied. • Usage of contention-based RACH access to target cell might be forced. • Full configuration is applied as no source configuration from UTRAN can be used for delta configuration. or ue-ConfigRelease-r9. the eNB rejects the HO Request with the cause value Radio Network Layer (Handover Target not allowed). 1. and either acknowledges or rejects the handover request. The following O&M parameters are new: • Feature-flag/feature (de-)activation • Switch for (Non) contention based RACH access The feature can be enabled/disabled per BTS by setting the Activate handover from UTRAN parameter to true/false. LTE RL60. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features The eNB applies the same admission control thresholds for the handover request as for other incoming mobility handovers. each incoming UE would be released by eNB shortly after HO completion. a handover command to the UE with embedded RRCConnectionReconfiguration information. 4. The RNC issues. DN09185955 Issue: 01J © 2016 Nokia 29 . As it is very likely that MME triggers a security key update shortly after an incoming handover from UTRAN.1. no crosscheck for feature activation is needed.4 System impact Interdependencies between features The following features have interdependencies to the LTE57: Inter RAT handover from UTRAN feature: • LTE511: Intra-Cell handover : The LTE511: Intra-Cell handover feature describes the application of intra cell handover for security key update. As LTE511: Intra-Cell handover is a basic feature of RL50. intra-LTE handovers. The MME might trigger after a successful handover a security key update via the S1AP:UEContextModificationRequest message. The eNB sends afterwards a S1AP:HandoverNotify message to the MME. after a successful handover preparation phase. the LTE511: Intra-Cell handover feature is a prerequisite for the LTE57: Inter RAT handover from UTRAN feature. Figure 2 HO from UTRAN execution UE eNB UTRAN SGSN MME S-GW/P-GW RRC:HOfromUTRANCommand DetachfromUTRANsourcecellperform randomaccessprocedureonLTEtargetcell RRC:Connection ReconfigurationComplete T S1RELOCexec UplinkUserData UplinkUserData The UE accesses the LTE and finalizes the handover with a RRC:RRCConnectionReconfigurationComplete message to the eNB. The eNB performs the security key update via an intra-cell handover. Otherwise. With the introduction of the LTE57: Inter RAT handover from UTRAN feature. • FC085_000698 Commercial level 2G/3G & LTE interworking (Gn based): The FC085_000698 Commercial level 2G/3G & LTE interworking (Gn based) feature is a corresponding feature on SAE GW side that was introduced to support Handover from UTRAN to LTE. • LTE534: ARP-based Admission Control for E-RABs: The LTE534: ARP-based Admission Control for E-RABs feature handles incoming handovers from UTRAN transparently in the same way as intra-LTE handovers. • FC085_000407 3G Gn based handover: The FC085_000407 3G Gn based handover feature is a corresponding feature on MME side which was introduced to support Handover from UTRAN to LTE. • LTE1089: Downlink Carrier Aggregation: The LTE1089: Downlink Carrier Aggregation feature foresees that carrier aggregation might be applied in the target cell to incoming UE after Handover completion. Feature Descriptions and Instructions telecom features • LTE54: Intra-LTE handover via S1: The LTE54: Intra-LTE handover via S1 feature has introduced the general procedure handling for incoming S1-based handover. the same rules shall be applied for load based IRAT handovers. incoming IRAT handover is rejected according to the same rules. This functionality is reused for the LTE57: Inter RAT handover from UTRAN feature. • FC085_000448 Gn based mobility: The FC085_000448 Gn based mobility feature is a corresponding feature on SAE GW side that was introduced to support Handover from UTRAN to LTE. • LTE497: Smart Admission Control: The LTE497: Smart Admission Control feature handles incoming handovers from UTRAN transparently in the same way as intra- LTE handovers. • LTE1382: Cell Resource Groups: PLMN-ID selective Admission Control applied for Cell resource groups handles incoming handovers from UTRAN transparently in the same way as intra LTE handovers. • LTE1170: Inter eNodeB IF Load Balancing: The LTE1170: Inter eNodeB IF Load Balancing feature specified rules to reject incoming handover requests for load based intra LTE handovers. • FC085_001505 S3 based Inter-system handover: The FC085_001505 S3 based Inter-system handover feature is a corresponding feature on MME side that was introduced to support Handover from UTRAN to LTE. 30 © 2016 Nokia DN09185955 Issue: 01J . • LTE1047: Control plane overload handling: One measure to defend against C-Plane overload defined in the LTE1047: Control plane overload handling feature is to reject incoming intra-LTE inter eNB handover requests. However both features may be activated independently from each other • RAN2264: Smart LTE Handover: The RAN2264: Smart LTE Handover feature is a corresponding feature on UTRAN side that was introduced to support Handover from UTRAN to LTE. This is applied to a UE entering from UTRAN as well. • FC085_000535 Rel-8 architecture support for inter system mobility: The FC085_000535 Rel-8 architecture support for inter system mobility feature is a corresponding feature on MME side that was introduced to support Handover from UTRAN to LTE. Descriptions of radio resource management and LTE RL60. • FC085_000418 10A_601_Inter RAT Handover 3G: The FC085_000418 10A_601_Inter RAT Handover 3G feature is a corresponding feature on SAE GW side that was introduced to support Handover from UTRAN to LTE. If the LTE1170: Inter eNodeB IF Load Balancing feature and the LTE57: Inter RAT handover from UTRAN feature are activated commonly. • LTE1139: ZUC security algorithm: The LTE1139: ZUC security algorithm is applied for UE entering from UTRAN according to the same rules as for UE entering from LTE.1. Incoming Handover from UTRAN according to LTE will be treated in the same was as incoming intra-LTE Handover. The HANDOVER REQUEST contains the new IE "NAS Security Parameters to E- UTRAN" Impact on network and network element management tools This feature has no impact on network management or network element management tools. Table 3 New parameters Full name Abbreviated name Managed object Activate handover from UTRAN actHoFromUtran LNBTS RACH access for handover from rachAccessForHoFromUtran LNBTS UTRAN DN09185955 Issue: 01J © 2016 Nokia 31 . Impact on interfaces S1 - Interface The existing messages • HANDOVER REQUEST • HANDOVER REQUEST ACKNOWLEDGE are extended to support the additional value "UTRANtoLTE" as Handover Type.5 LTE57: Inter RAT handover from UTRAN management data Alarms There are no alarms related to this feature. 4. Impact on system performance and capacity This feature has no impact on system performance or capacity. Measurements and counters There are no measurements and counters related to this feature. Parameters The table lists parameters introduced with this feature. LTE RL60. Key performance indicators There are no key performance indicators related to this feature. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features • LTE1074: Multimedia Priority Services: The LTE1074: Multimedia Priority Services feature introduces special handling for High Priority Services. Especially Admission Control for incoming Handover is extended.1. Descriptions of radio resource management and LTE RL60, Feature Descriptions and Instructions telecom features 4.1.1.6 Sales information Table 4 Sales information BSW/ASW License control in network License control attributes element ASW SW Asset Monitoring - 4.1.2 Activating LTE57: Inter RAT handover from UTRAN Before you start The eNB has activated the RNW (Radio Network ) database and the LTE cells have been set up. Table 5 Parameters used for activating and configuring LTE57: Inter RAT handover from UTRAN Parameter Purpose Requires eNB restart or object locking Activate handover activation flag no from UTRAN (actHofromUtran) RACH access for optional configuration no handover from UTRAN By default UEs are configured to ( perform contention based RACH rachAccessForHoFrom access. If the eNodeB shall Utran) provide and reserve a dedicated RACH preamble for HO from UTRAN the LNBTS rachAccessForHoFromUtra must be set to NonContentionBased'. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. 2 Activate/Configure the feature LTE57: Inter RAT handover from UTRAN. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. c) Select the LNBTS object. d) Set the Activate handover from UTRAN (actHoFromUtran) parameter value to 1 (true). 32 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 3 Configure the RACH access (optional). a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. c) Select the LNBTS object. d) Set the RACH access for handover from UTRAN (rachAccessForHoFromUtran.) parameter value to 1 (nonContentionBased). 4 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Expected Outcome The feature LTE57: Inter RAT handover from UTRAN is configured and activated in eNB. eNB accepts and processes S1-HANDOVER REQUEST messages with handover type UTRANtoLTE. 4.1.3 Deactivating LTE57: Inter RAT handover from UTRAN Before you start The Activate handover from UTRAN (actHoFromUtran) parameter is used for deactivation. Modification of this parameter does not require eNB restart. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. 2 Deactivate the feature LTE57: Inter RAT handover from UTRAN a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. c) Select the LNBTS object. d) Set the Activate handover from UTRAN (actHoFromUtran) parameter value to 0 (false). 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Expected Outcome The feature LTE57: Inter RAT handover from UTRAN is deactivated. DN09185955 Issue: 01J © 2016 Nokia 33 Descriptions of radio resource management and LTE RL60, Feature Descriptions and Instructions telecom features 4.2 LTE60: Inter RAT handover to eHRPD/3GPP2 4.2.1 Description of LTE60: Inter RAT Handover to eHRPD/3GPP2 Introduction to the feature The LTE60: Inter RAT handover to eHRPD/3GPP2 feature introduces prepared coverage-based inter-RAT handover from an LTE cell to a CDMA2000 eHRPD cell. 4.2.1.1 Benefits End-user benefits This feature reduces the service interruption time. Operator benefits The operator can deliver higher quality/less service interruption time to the customer. 4.2.1.2 Requirements Software requirements Table 6: Software requirements lists software required for this feature. Table 6 Software requirements System release Flexi Multiradio BTS Flexi Multiradio OMS 10 BTS RL60 - LBTS6.0 - UE NetAct MME SAE GW 3GPP R8 UE capabilities NetAct8 EP1 - - Hardware requirements There are no hardware requirements related to this feature. 4.2.1.3 Functional description The LTE to eHRPD optimized handover functionality of the Flexi Multiradio BTS allows for a service continuity of data services with minimal interruption time when changing from an LTE cell to a CDMA2000 eHRPD cell. The functionality is only applicable for multimode devices supporting both LTE and CDMA2000 eHRPD for the relevant frequency band and the relevant feature support. g Note: Handover to a HRPD configuration (i.e. actHOtoHrpd is 'true') is ONLY allowed when eNodeB is configured in phase sync mode( i.e. btsSyncMode is 'PhaseSync') and not as the sync hub slave (i.e. gpsCtrlBlockForCoLocatedBts is 'False' ). Pre-registration 34 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions Descriptions of radio resource management and telecom features The UE initiates the pre-registration to the CDMA2000 eHRPD Access. Based on a Radio Layer trigger, the UE decides to initiate a pre-registration procedure with potential target HRPD access. The pre-registration procedure allows the UE to establish and maintain a session in the target HRPD access, while attached to the E-UTRAN/MME. The eNB provides up to three operator-configurable Zone ID for the preregistration either in SIB8 for RRC Idle UEs, or in the measurement configuration IE for RRC Connected UEs. The three Zone IDs (Primary Zone ID and two Secondary Zone IDs) are operator- configurable per cell. The same Zone IDs are applied for SIB 8 and the measurement configuration. However, different preRegistrationAllowed flags can be configured for SIB8 and the measurement configuration. The eNB supports the following messages for the pre-registration: • the RRC:ULInformationTransfer message • the RRC:DLInformationTransfer message are supported between the UE and the eNB. • the S1AP:DownlinkS1CDMA2000Tunneling message and • the S1AP:UplinkS1CDMA2000Tunneling are supported between the eNB and the MME. The eNB adds during the pre-registration procedure a CDMA2000 Sector ID to the S1AP:UplinkS1CDMA2000Tunneling message. The sector ID for the pre-registration is selected with a weighted round robin mechanism out of an operator- configurable pool of sector IDs. Handover trigger The handover is a network controlled handover with support of the UE. The following measurement events are used: • A1 - deactivate IRAT/IF measurements (RSRP) • A2 - activate IRAT eHRPD measurements (RSRP) • B2 - IRAT eHRPD measurements The operator-configurable measurements events A2 and A1 are used to start and stop IRAT measurements. The UE capabilities are considered for the IRAT measurements, for example UE support of measurement gaps and UE support of the target cell frequency band. The measurement gap gp0 is used. The target cells for the IRAT measurements are operator- configurable. The operator can select whether cells are considered for IRAT measurement or not. A target cell load balancing between different frequency layers is applied for the initial target frequency considering operator-configurable weights. The selection valid as long as the UE is RRC CONNECTED in the same cell. The B2 measurement configuration of the source cell thresholds (RSRP), target cell threshold (pilotStrength), hysteresis (specific to eHRPD), time to trigger (specific to eHRPD) and speed dependent scaling are operator- configurable on a per eHRPD carrier basis. Handover DN09185955 Issue: 01J © 2016 Nokia 35 Descriptions of radio resource management and LTE RL60, Feature Descriptions and Instructions telecom features The Flexi Multiradio BTS initiates the optimized eHRPD handover after receiving a B2 measurement report from the UE. A handover will be triggered if no QCI 1 bearer nor an emmergency session are on the UE. Upon receiving a B2 measurement report, the eNB takes the first target cell indicated by the UE measurements for the handover to eHRPD. The handover comprises of the following steps: 1. A RRC:HandoverFromEUTRAPreparationRequest message is sent to the selected UE. 2. The content of the response message from the UE (RRC:ULHandoverPreparationTransfer) is forwarded with the S1AP:UplinkS1CDMA2000Tunneling message via the MME to the CDMA2000 HRPD Access. The CDMA2000 Sector ID is set to the first target indicated by the UE measurement report. The S1AP:UplinkS1CDMA2000Tunneling message also contains the EUTRAN Round Trip Delay Estimation IE. 3. The CDMA2000 HRPD Access provides the responses via the S1AP:DownlinkS1CDMA2000Tunneling message. 4. The eNB sends, in case of a positive handover preparation response, a RRC:MobilityFromEUTRA message to the UE. The UE leaves LTE and starts to establish a traffic channel to CDMA2000 HRPD Access. 5. The eNB receives in case of a successful handover a S1AP:UEContextReleaseCommand message. The handover functionality can be enabled or disabled per eNB by OAM settings. 4.2.1.4 System impact Interdependencies between features This feature requires the support of GPS time retrieval, i.e. handover to a HRPD is only allowed when SIB8 CDMA system time is broadcasted, which is only possible when eNodeB is in phase sync mode and GPS time is available. As a result, Handover to a HRPD configuration (i.e.actHOtoHrpd is 'true') is ONLY allowed when eNodeB is configured in phase sync mode( i.e. btsSyncMode is 'PhaseSync') and not as the sync hub slave (i.e.gpsCtrlBlockForCoLocatedBts is 'False' ). And the following features need to be enabled: • LTE870: Idle Mode Mobility from LTE to CDMA/eHRPD The following features cannot be enabled in parallel with this functionality: • LTE56: Inter RAT Handover to WCDMA • LTE872: SRVCC to WCDMA • LTE873: SRVCC to GSM • LTE442: Network Assisted Cell Change to GSM • LTE736: CS Fallback to UTRAN • LTE898: TDD inter-RAT Handover to TD-SCDMA • LTE908: ANR Inter-RAT UTRAN - Fully UE Based Impact on interfaces S1 - Interface The following messages are new: 36 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions Descriptions of radio resource management and telecom features • Downlink S1 CDMA2000 Tunneling • Uplink S1 CDMA2000 Tunneling RRC - Interface The following messages are new: • HandoverFromEUTRAPreparationRequest(CDMA2000) • ULHandoverPreparationTransfer(CDMA2000) The following messages have new content: • DLInformationTransfer -> support of PDU-Type "dedicatedInfoCDMA2000-eHRPD" • ULInformationTransfer -> support of PDU-Type "dedicatedInfoCDMA2000-eHRPD" • MobilityFromEUTRACommand -> support of targetRAT-Type "cdma2000-eHRPD" Impact on network and network element management tools Interface to Netact The following parameters are added: • preregistation parameters for SIB8 • A2-threshold for eHRPD in LNCEL • supervision timer(s) in LNBTS The following managed object classes (MOCS) are added • eHRPD-specific measurement objects below LNCEL: CDFIM • eHRPD neighbour cell Object below LNBTS: LNADJX • eHRPD neighbour relation Object below LNCEL: LNNEIH Impact on system performance and capacity This feature has following impact on the system performance: • Service Interrupt Time (UP & CP): Interruption Time will be dominated by the target RAT and might therefore deviate from other known IRAT service interruption times. • Handover Success Rate: Decreased, because of longer IRAT HO preparation time. • Single User Throughput: Reduced LTE throughput due to measurement gap. TCP throughput/loss impact because of lack of data forwarding during HO. eHRPD throughput on target is not dependent on LTE60: Inter RAT Handover to eHRPD/3GPP2. There is no impact on capacity. 4.2.1.5 LTE60: Inter RAT handover to eHRPD/3GPP2 management data Alarms There are no alarms related to this feature. Measurements and counters The following measurement is new in the LTE60: Inter RAT handover to eHRPD/3GPP2 feature: DN09185955 Issue: 01J © 2016 Nokia 37 Feature Descriptions and Instructions telecom features Table 7 Measurements Measurement Measurement Measurement target MO Measured ID Name Description Object (MO) Descriptor (eNB) 8025 LTE Handover The measurement LTE Handover LNCEL/eHR to eHRPD per Handover to eHRPD per relationship PD eHRPD eHRPD bandclass between LNCEL bandclass bandclass contains counters which and eHRPD measure the Inter System bandclass Handover to eHRPD per eHRPD bandclass. The following counters are new (belong to the measurement above) Table 8 Counters PI ID Network element name NetAct name M8025C0 Inter System Handover preparations to ISYS_HO_EHRPD_PREP_BC eHRPD per eHRPD bandclass M8025C1 Failed Inter System Handover preparations ISYS_HO_EHRPD_PREP_FAIL1_ to eHRPD caused by expiration of guarding BC timer TUlHoPrepTransferHrpd per eHRPD bandclass M8025C2 Failed Inter System Handover preparations ISYS_HO_EHRPD_PREP_FAIL2_ to eHRPD caused by expiration of guarding BC timer TC2KRelocPrepHrpd per eHRPD bandclass M8025C3 Failed Inter System Handover preparations ISYS_HO_EHRPD_PREP_FAIL3_ to eHRPD caused by received HO Failure BC indication message per eHRPD bandclass M8025C4 Successful Inter System Handover ISYS_HO_EHRPD_PREP_SUCC_ preparations to eHRPD per eHRPD BC bandclass M8025C5 Inter System Handover attempts to eHRPD ISYS_HO_EHRPD_ATT_BC per eHRPD bandclass 38 © 2016 Nokia DN09185955 Issue: 01J . Descriptions of radio resource management and LTE RL60. For each handover relationship between the LTE cell (source of the inter system handover) and the eHRPD bandclass (target of the inter system handover) a separate counter is provided. LTE RL60. hrpdSecPreRegZoneI CDFIM hoRegParamHrpd registration Zone ID1 d1 HRPD secondary pre.) PI ID Network element name NetAct name M8025C6 Failed Inter System Handover attempts to ISYS_HO_EHRPD_FAIL_TIM_BC eHRPD caused by expiration of guarding timer TC2KRelocOverallHRPD per eHRPD bandclass M8025C7 Successful Inter System Handover ISYS_HO_EHRPD_SUCC_BC completions to eHRPD per eHRPD bandclass Key performance indicators There are no key performance indicators related to this feature. Parameters The following parameters are new: Table 9 Parameters Full name Abbreviated name Managed object Structure HRPD pre-registration hoRegParamHrpd CDFIM info HRPD pre-registration hrpdPreRegAllowed CDFIM hoRegParamHrpd allowed HRPD pre-registration hrpdPreRegZoneId CDFIM hoRegParamHrpd zone ID HRPD secondary pre. hrpdSecPreRegZoneI CDFIM hoRegParamHrpd registration Zone ID2 d2 CDMA2000 HRPD hrpdNCList CDFIM neighbor cell list CDMA2000 HRPD hrpdArfcn CDFIM hrpdNCList frequency CDMA2000 HRPD hrpdBdCl CDFIM hrpdNCList Band Class CDMA2000 HRPD hrpdBdClNcl CDFIM hrpdNCList band class CDMA2000 HRPD hrpdCellId CDFIM hrpdNCList physical cell identity DN09185955 Issue: 01J © 2016 Nokia 39 . Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 8 Counters (Cont. Descriptions of radio resource management and LTE RL60.) Full name Abbreviated name Managed object Structure CDMA2000 HRPD hrpdExSel CDFIM hrpdNCList NCL extension selector CDMA2000 1xRTT rttNCList CDFIM neighbor cell list CDMA2000 1xRTT rttArfcn CDFIM rttNCList frequency CDMA2000 1xRTT rttBdClNcl CDFIM rttNCList band class (NCL) CDMA2000 1xRTT rttCellId CDFIM rttNCList physical cell identity CDMA2000 1xRTT rttExSel CDFIM rttNCList NCL extension selector Activate handover actHOtoHrpd LNBTS from LTE to eHRPD Time to Trigger for A2 a2TimeToTriggerActHr LNCEL to activate C2K-HRPD pdMeas Measurement eHRPD sector-ID list eHrpdSectList LNCEL for pre-registration Loadbalancing factor preRegLoadBalFactor LNCEL eHrpdSectList for pre-registration with eHRPD SectorID of eHRPD sectorID LNCEL eHrpdSectList access network HRPD Timers hrpdTimers LNCEL CDMA2000 HRPD tC2KRelocOverallHrpd LNCEL hrpdTimers Handover Relocation Execution Timer CDMA2000 HRPD tC2KRelocPrepHrpd LNCEL hrpdTimers Handover Relocation Preparation Timer CDMA2000 HRPD UL tUlHoPrepTransferHrp LNCEL hrpdTimers Handover Preparation d Transfer Timer 40 © 2016 Nokia DN09185955 Issue: 01J . Feature Descriptions and Instructions telecom features Table 9 Parameters (Cont. Activate SRVCC to mandatory configuration no restart required GSM(actSrvccToGsm) Deactivates LTE873:SRVCC from LTE to GSM.2 Activating LTE60: Inter RAT handover to eHRPD/3GPP2 Before you start Table 11 Parameters used for activating and configuring LTE60: Inter RAT handover to eHRPD/3GPP2 Parameter Purpose Requires eNB restart or object locking Activate handover activation flag no restart required from LTE to eHRPD(actHOtoHrpd) Activation idle mandatory configuration no restart required mode mobility CDMA/eHRPD Activates LTE870: Idle mode (actImmHRPD) mobility from LTE to CDMA/eHRPD.) Full name Abbreviated name Managed object Structure Related Hysteresis of hysThreshold2Hrpd LNCEL Threshold2 C2K- HRPD for RSRP Threshold Th2 threshold2Hrpd LNCEL CDMA2000-HRPD for RSRP Threshold th2a for threshold2a LNCEL RSRP 4. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 9 Parameters (Cont. LTE RL60. DN09185955 Issue: 01J © 2016 Nokia 41 .2.6 Sales information Table 10 Sales information BSW/ASW License control in network License control attributes element ASW SW Asset Monitoring - 4. Activate eNACC to mandatory configuration no restart required GSM(acteNACCtoGSM) Deactivates LTE442: Network Assisted Cell Change from LTE to GSM. Activate handover mandatory configuration no restart required from LTE to WCDMA((actHotoWCDM Deactivates LTE56: Inter RAT A) handover to WCDMA.1.2. Feature Descriptions and Instructions telecom features Table 11 Parameters used for activating and configuring LTE60: Inter RAT handover to eHRPD/3GPP2 (Cont.) Parameter Purpose Requires eNB restart or object locking Activate UE-based mandatory configuration no restart required ANR for UTRAN(actUeBasedAn Deactivates LTE908: ANR Inter-RAT rUtran) UTRAN - Fully UE Based. HRPD pre. It must be configured in all LNCEL instances. mandatory configuration no restart required registration info(hoRegParamHrp This structure contains parameters d) associated with eHRPD Pre- registration used in SIB8. It must be configured in all LNCEL instances. eHRPD sector-ID mandatory configuration no restart required list for pre- registration This structure contains a list of (eHrpdSectList) eHRPD Sector-IDs which are used to address eHRPD-AN when tunneling cdma2000 HRPD PDU for Pre-Registration with eHRPD. Related Hysteresis mandatory configuration no restart required of Threshold2 C2K- HRPD for This parameter describes the RSRP(hysThreshold2 related hysteresis of threshold for Hrpd) RSRP of serving cell for start of CDMA2000-eHRPD measurements. It must be configured in all LNCEL instances. Each Sector-ID is associated with a loadbalancing factor to allow loadbalancing between multiple eHRPD-AN. HRPD mandatory configuration no restart required Timers(hrpdTimers) Defines the timers used to control mobility to CDMA2000 HRPD. Threshold Th2 mandatory configuration no restart required CDMA2000-HRPD for RSRP This parameter describes the (threshold2Hrpd) Threshold for RSRP of serving cell for start of CDMA2000-eHRPD measurements . Descriptions of radio resource management and LTE RL60. Time to Trigger mandatory configuration for A2 to activate C2K-HRPD Measurement (a2TimeToTriggerAc tHrpdMeas) 42 © 2016 Nokia DN09185955 Issue: 01J . Network Mandatory configuration BTS restart needed synchronization mode (btsSyncMode) GPS control Mandatory configuration BTS restart needed interface blocked for co-located BTS ( gpsCtrlBlockForCoL ocatedBts) The LTE870: Idle Mode Mobility from LTE to CDMA/eHRPD feature needs to be activated before activation of LTE60: Inter RAT handover to eHRPD/3GPP2 . a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. LTE RL60. It must be configured in all LNCEL instances. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. The following features need to be deactivated before activation of LTE60: Inter RAT handover to eHRPD/3GPP2 • LTE56: Inter RAT Handover to WCDMA • LTE442: Network Assisted Cell Change to GSM • LTE873: SRVCC to GSM • LTE908: ANR Inter-RAT UTRAN - Fully UE based • Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. d) Set the Activation idle mode mobility CDMA/eHRPD (actImmHRPD) parameter value to true. 2 Activate/Deactivate related features to LTE60: Inter RAT handover to eHRPD/3GPP2. DN09185955 Issue: 01J © 2016 Nokia 43 . Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 11 Parameters used for activating and configuring LTE60: Inter RAT handover to eHRPD/3GPP2 (Cont.) Parameter Purpose Requires eNB restart or object locking This is the time during which specific RSRP criteria for the event A2 needs to be met to trigger a measurement report. c) Select the LNTBS object. g) Set Threshold Th2 CDMA2000-HRPD for RSRP (threshold2Hrpd) parameter in all configured LNCEL instances. f) Set the Activate SRVCC to GSM (actSrvccToGsm) parameter value to false. c) Select the LNTBS object. f) Set Related hysteresis of threshold C2K . d) Create at least one LNCEL instance e) Set hrpdTimers structure in all configured LNCEL instances. a) Go to the Radio Network Configuration page. g) Set the Activate handover from LTE to WCDMA (actHotoWCDMA) parameter value to false. Configure the CDMA2000 HRPD band class list (hrpdBdCIList ) and the CDMA2000 HRPD neighbor cell list (hrpdNCList): the band class numbers must be supported by the UE. Set the periodicity ( siMessagePeriodicity) parameter. 2. 1. Set the siMessageSibType ( siMessageSibType ) parameter value to SIB8.HRPD for RSRP (hysThreshold2HRPD) parameter in all configured LNCEL instances.HRPD measurements ( a2TimeToTriggerActHrpdMeas) parameter in all configured LNCEL instances. 2. 1. 44 © 2016 Nokia DN09185955 Issue: 01J . The HRPD pre-registration allowed (hrpdPreRegAllowed ) parameter needs to be set as true. h) Set eHrpdSectListstructure in all configured LNCEL instances. m) Create at least one LNHOH instance. i) Set Time to Trigger for A2 to activate C2K . l) Set the HRPD pre-registration Info (hoRegParamHrpd) structure in all configured CDFIM instances. k) Create CDFIM instance in at least one LNCEL instance. b) Expand the MRBTS object. j) Set the System information scheduling list (sibSchedulingList) structure in all configured LNCEL instances. 3 Activate/Configure the feature LTE60: Inter RAT handover to eHRPD/3GPP2. h) Set the Activate UE-based ANR for UTRAN ( actUeBasedAnrUtran) parameter value to false. n) Create at least one LNNEIH instance. LNHOH/hrpdCarrierFreq/hrpdArfcn and LNHOH/hrpdCarrierFreq/hrpdBandClass must be the same as the related parameters from CDFIM instance CDFIM/hrpdNCList/hrpdArfcn and CDFIM/hrpdNCList/hrpdBdClNcl and must be the same as the related parameters from LNNEIH instance LNNEIH/hrpdArfcn and LNNEIH/hrpdBandClass. 1. Feature Descriptions and Instructions telecom features e) Set the Activate eNACC to GSM (acteNACCtoGSM) parameter value to false. Descriptions of radio resource management and LTE RL60. LTE RL60.2.gpsCtrlBlockForCoLocatedBts is 'False' ) 4 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.e. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. 2 Deactivate the feature: LTE60: Inter RAT handover to eHRPD/3GPP2 a) Go to the Radio Network Configuration page.e.e. Set the PS handover allowed psHoAllowed to allowed. q) Set the Activate handover from LTE to eHRPD (actHotoHrpd ) parameter value to true. LNADJL/fDIEarfcn must be the same as the related parameter from LNHOIF instance LNHOIF/eutraCarrierInfo. 4. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 2. o) Create at least one LNADJL instance.3 Deactivating LTE60: Inter RAT handover to eHRPD/3GPP2 Before you start The Activate handover from LTE to eHRPD(actHOtoHrpd) is used for deactivation.actHOtoHrpd is 'true') is ONLY allowed when eNodeB is configured in phase sync mode( i. Modification of this parameter does not require a restart. p) Create at least one LNHOIF instance. 1. btsSyncMode is 'PhaseSync') and not as the sync hub slave (i. d) Set the Activate handover from LTE to eHRPD (actHOtoHrpd) parameter value to false. b) Expand the MRBTS object. LNNEIH/hrpdSectorId must be the same as the related parameter LNCEL/eHRPDSectList/sectorID. c) Select the LNBTS object. 3. g Note: Handover to a HRPD configuration (i. DN09185955 Issue: 01J © 2016 Nokia 45 . In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. 1 Description of LTE498: RAN Information for GSM Introduction to the feature The LTE498: RAN Information for GSM feature allows the transfer of information between the source and target cell via the core network.3 LTE498: RAN Information Management for GSM 4.3. This mechanism allows for a reduction of parameter setting.1.3. 4. Operator benefits This feature provides the operator with the following benefits: • reducing the number of parameters needed to configure the network assisted cell change or the RRC connection release with redirect and SIB 4. Table 12 Software requirements System release Flexi Multiradio BTS Flexi Multiradio OMS 10 BTS RL60 LBTS6.0 LBTS6. the GSM system information message is included in the RRCConnectionRelease and MobilityFromEutranCommand messages.2 Requirements Software requirements Table 12: Software requirements lists software required for this feature. - Hardware requirements This feature requires no new or additional hardware. 46 © 2016 Nokia DN09185955 Issue: 01J .1 Benefits End-user benefits During the following procedures: • CSFB • NACC • normal redirection to Global System for Mobile Communications (GSM). Feature Descriptions and Instructions telecom features 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.1. 4.0 - UE NetAct MME SAE GW 3GPP R8 UE capabilities NetAct8 EP1 .3. This feature reduces the time the UE uses to access the GSM network because the UE does not need to read the system information from GSM. Descriptions of radio resource management and LTE RL60. LTE RL60. SI3.NACC) (forexample. and SI13) from a target GSM cell. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4. The systemInfoListGeran optional parameter contains SI that is manually entered.1. see Figure 3: RIM protocol structure between E-UTRAN and GERAN Figure 3 RIM protocol structure between E-UTRAN and GERAN eNB S1 S3/Gn Gb BSC MME SGSN (controlling) (serving) RIM RIM Container Container RIM-App RIM-App RIM RIM-App RIM-App RIM RIM-App RIM-App (forexample.NACC) RIMPDUs RIMPDUs Relay Relay GTP-C GTP-C S1AP S1AP UDP UDP BSSGP BSSGP IP IP SCTP SCTP NS NS L2 L2 IP/L2andL1 IP/L2andL1 L1 L1 L1 L1 The RAN information management (RIM) function enables the eNB to retrieve system information (SI1. that is: • if the LTE498: RAN Information Management for GSM feature is activated and • the PLMN of the cell is not blacklisted for RIM and • the gTargetRac parameter is configured The following RIM procedures are supported: • RAN Information Request/Multiple Report procedure • RAN Information Request/Stop procedure DN09185955 Issue: 01J © 2016 Nokia 47 . The eNB acts always as a controller. set by the operator. The systemInfoType parameter. which are used to populate GERAN System Information for eNACC procedure and redirection to GSM procedure. indicates which type of GERAN System Information (if any) is included in the RRC MOBILITYFROMEUTRANCOMMAND message. The systemInfoType and systemInfoListGeran parameters become meaningless under the same conditions.3. The LTE498: RAN Information Management for GSM feature introduces the RIM for GSM functionality to transfer up-to-date System Information of GERAN neighbor cells from a remote base station controller (BSC) to a local eNB.3 Functional description Generic RAN Information Management (RIM) procedures support the exchange of information via the core network. between peer application entities located in the access networks. This parameter can have the values as follows: • disabled The GERAN neighbor cell is not RIM enabled.4 System impact Interdependencies between features 48 © 2016 Nokia DN09185955 Issue: 01J . and during enhanced UE Context Release with Redirect to GSM for CS fallback and/or the "normal" redirect (the LTE984: GSM Redirect with System Information feature). The received GERAN SIBs are used during eNACC to GSM (the LTE442: Network Assisted Cell Change to GSM feature). the RIM applies for all GERAN neighbor cells of the eNB. – The PLMN of the GERAN cell is blacklisted for RIM. • unavailable The GERAN neighbor cell is RIM-enabled but no valid system information from the RIM procedure is available. 4. one of the following options happens: – The LTE498: RAN Information Management for GSM feature is not activated. Descriptions of radio resource management and LTE RL60. – No RAC value is configured. Support of Direct Information Transfer via S1 interface To transmit RIM information between the eNB and the MME.1. The Blacklisted GSM PLMNs for RIM (blacklistedGsmPlmnsForRim) parameter allows blacklisting of RIM for all GERAN neighbor cells belonging to one of the configured PLMNs.3. two following procedures are supported: • the eNB Direct Information Transfer procedure to transmit an information container from the eNB to the MME • the MME Direct Information Transfer procedure to transmit an information container from the MME to the eNB Blacklisting GSM PLMNs for RIM In case of multi-operator configurations. • available The GERAN neighbor cell is RIM-enabled and a valid system information from the RIM procedure is available. With the rimStatus=disabled. It is possible to blacklist the GSM PLMNs to avoid periodical attempts to establish RIM associations. Feature Descriptions and Instructions telecom features • RAN Information Send procedure • RAN Information Application Error procedure • RAN Information Error procedure The LTE498: RAN Information Management for GSM feature allows the eNB to receive GERAN SIB information from BSC without the need for configuration of GERAN SIBs by the operator. the RIM might not be supported by all GSM networks. If the blacklistedGsmPlmnsForRim parameter is omitted. RIM interface status The RIM interface status (rimStatus) parameter provides the status of the RIM association to a serving base station system (BSS). The raised alarm remains active as long as there is an active fault for the PLMN even if the fault for DN09185955 Issue: 01J © 2016 Nokia 49 . Table 13 Modified alarms Alarm ID Alarm name 7657 BASE STATION CONNECTIVITY DEGRADED The alarm is caused by the following BTS faults: • RIM interface timeout • RIM interface error If an RIM association to a GERAN neighbor cell cannot be established after several attempts or if a RAN INFORMATION ERROR PDU is received or if an application error is detected in Application Container IE of RAN INFORMATION PDU or if Application Error Container IE is included in RAN INFORMATION PDU. then GSM redirection procedure is populated with up-to-date system information acquired by RIM procedure. • LTE442: Network Assisted Cell Change to GSM When both features: the LTE498: RAN Information Management for GSM and the LTE442: Network Assisted Cell Change to GSM are activated. Impact on system performance and capacity This feature has no impact on system performance or capacity. Impact on interfaces This feature impacts: • the RRC protocol in the LTE-Uu interface • the S1AP protocol in the S1-MME interface Impact on network and network element management tools This feature has no impact on network management or network element management tools. • LTE984: GSM Redirect with System Information When both features: the LTE498: RAN Information Management for GSM and the LTE984: GSM Redirect with System Information are activated. the RIM interface timeout or RIM interface error fault is reported. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Activation of the LTE498: RAN Information Management for GSM feature is reasonable if at least one of the features: the LTE442: Network Assisted Cell Change to GSM or the LTE984: GSM Redirect with System Information is activated.5 Management data Alarms Table 13: Modified alarms lists existing alarms related to this feature.3. LTE RL60.1. This avoids alarm floods and reporting of several alarms for the same root cause. 4. then eNACC to GERAN procedure is populated with up-to-date system information acquired by RIM procedure. Only one fault can be reported per GERAN public land mobile network (PLMN). Feature Descriptions and Instructions telecom features the cell. Descriptions of radio resource management and LTE RL60. The RIM alarms do not suppress BASE STATION CONNECTIVITY DEGRADED alarms that are raised because of S1 and/or X2 interface failures. Parameters Table 14: New parameters lists parameters introduced with this feature. Updating of alarm information is not required (a risk for message floods). has been cleared. whose routing area code (RAC) and cell global identification (CGI) are reported in the alarm. Table 15 Related parameters Name Abbreviation Managed object System info list GERAN systemInfoListGeran LNADJG 50 © 2016 Nokia DN09185955 Issue: 01J . Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Table 14 New parameters Full name Abbreviated name Managed object Structure RAC GERAN gTargetRac LNADJG RIM interface status rimStatus LNADJG Activate RAN actRIMforGSM LNBTS Information Management for GSM Blacklisted GSM blacklistedGsmPlmnsF LNBTS PLMNs for RIM orRim MCC mcc LNBTS blacklistedGsmPlmnsF orRim MNC mnc LNBTS blacklistedGsmPlmnsF orRim MNC length mncLength LNBTS blacklistedGsmPlmnsF orRim Maximum RIR nRimRirG LNBTS attempts to GERAN Timer to wait for next tRimKaG LNBTS RI PDU from GERAN Polling timer to tRimPollG LNBTS ReStart RIR Procedure to GERAN Timer to wait for RIR tRimRirG LNBTS Response from GERAN Table 15: Related parameters lists existing parameters related with the feature. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 15 Related parameters (Cont.6 Sales information Table 16 Sales information BSW/ASW License control in License control Activated by default network element attributes ASW SW Asset Monitoring . No 4.2 Activating LTE498: RAN Information Management for GSM Before you start Table 17 Parameters used for activating and configuring LTE498: RAN Information Management for GSM Parameter Purpose Requires eNB restart or object locking Activate RAN activation flag no Information Management for GSM (actRIMforGSM) RAC GERAN optional configuration no (gTargetRac) g Note: If it is not configured for the GERAN target cell. Blacklisted GSM optional configuration no PLMNs for RIM (blacklistedGsmPlm nsForRim) parameter structure Maximum RIR mandatory configuration no attempts to GERAN (nRimRirG) Timer to wait for mandatory configuration no next RI PDU from GERAN (tRimKaG) Polling timer to mandatory configuration no ReStart RIR Procedure to GERAN (tRimPollG) Timer to wait for mandatory configuration no RIR Response from GERAN ( tRimRirG) DN09185955 Issue: 01J © 2016 Nokia 51 .3.1.3.) Name Abbreviation Managed object System information type systemInfoType LNADJG 4. RAN Information Management (RIM) will not be used. LTE RL60. Feature Descriptions and Instructions telecom features Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. b) Expand the MRBTS object. c) Right-click the LNBTS object. 5 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. b) Expand the MRBTS object. Once RIM association is successfully established. 52 © 2016 Nokia DN09185955 Issue: 01J . a) Go to the Radio Network Configuration page. a) Go to the Radio Network Configuration page. e) For the LNADJG object set all the mandatory parameters' values. the RIM interface status (rimStatus) parameter. Polling timer to ReStart RIR Procedure to GERAN (tRimPollG). 3 Configure the RAC GERAN. Timer to wait for RIR Response from GERAN (tRimRirG) parameters’ values. perform the steps described in this procedure. Descriptions of radio resource management and LTE RL60. set by the system. b) Expand the MRBTS object. c) Select the LNBTS object. a) Go to the Radio Network Configuration page. f) Set the RAC GERAN (gTargetRac) parameter value. d) Set the Activate RAN Information Management for GSM (actRIMforGSM) parameter value to true. Timer to wait for next RI PDU from GERAN (tRimKaG). If RIM association is not established. d) Select New LNADJG. alarm will be raised and the RIM interface status (rimStatus) parameter will be changed automatically to unavailable. 4 Configure the parameters. is changed automatically to available. d) Set the Maximum RIR attempts to GERAN (nRimRirG). In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. c) Select the LNBTS object. 2 Activate the feature. 1. DN09185955 Issue: 01J © 2016 Nokia 53 . c) Select the LNBTS object. d) Set the Activate RAN Information Management for GSM (actRIMforGSM) parameter value to false.4. 4. will be changed automatically to disabled for all LNADJG’s.4 LTE520: 8 EPS bearers per UE 4.1.1 Description of LTE520: 8 EPS bearers per UE Introduction to the feature The LTE520: 8 EPS bearers per UE feature establishes up to eight EPS bearers per UE. Operator benefits This feature offers an always-on service with multiple concurrent sessions.3. b) Expand the MRBTS object. set by the system.3 Deactivating LTE498: RAN Information Management for GSM Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. The RIM interface status (rimStatus) parameter. a) Go to the Radio Network Configuration page.4. 4. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. LTE RL60. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. 2 Deactivate the feature. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4.1 Benefits End-user benefits This feature does not affect the end-user experience. 4.4. perform the steps described in this procedure.2 Requirements Software requirements Table 18: Software requirements lists the software required for this feature. 1.4. The support of up to eight EPS bearers is requested to use the emergency calls when six EPS bearers are active. it applies the all-or-nothing approach and supports the following scenarios: • establish individual EPS bearers • release individual EPS bearers • add multiple EPS bearers to existing EPS bearers • release multiple EPS bearers from existing EPS bearers Various EPS bearers per UE can have the same or a different QCI. 4. 4. Descriptions of radio resource management and LTE RL60. - capabilities Hardware requirements This feature requires no new or additional hardware. The downlink scheduler provides prioritization among multiple non-GBR EPS bearers and provides means to avoid starvation of downlink traffic.0 - UE NetAct MME SAE GW 3GPP R8 UE NetAct8 EP1 . The UE indicates its capabilities with a feature bit in the UE capabilities.3 Functional description The Flexi Multiradio BTS supports up to eight EPS bearers for multiple-bearer-capable UEs.4 System impact Interdependencies between features The following features have to be enabled: 54 © 2016 Nokia DN09185955 Issue: 01J .4.0 LBTS6. since eNB does not fully support pre-emption of one of the six EPS bearers. The Flexi Multiradio BTS supports the following radio bearer combinations per UE: • SRB1 + SRB2 + 6 x AM DRB • SRB1 + SRB2 + 7 x AM DRB • SRB1 + SRB2 + 8 x AM DRB • SRB1 + SRB2 + 4 x AM DRB + 3 UM DRB • SRB1 + SRB2 + 5 x AM DRB + 2 x UM DRB • SRB1 + SRB2 + 5 x AM DRB + 3 x UM DRB Multiple data radio bearers (DRB) can be either multiple default EPS bearers or a combination of default and dedicated EPS bearers. For the Intra-LTE handovers.1. The Flexi Multiradio BTS provides checks for the total number of DRB per cell and maximum possible number of DRB per UE. Feature Descriptions and Instructions telecom features Table 18 Software requirements System release Flexi Multiradio BTS Flexi Multiradio 10 OMS BTS RL60 LBTS6. 6 Sales information Table 19 Sales information BSW/ASW License control in License control Activated by default network element attributes ASW SW Asset Monitoring .4.1. Impact on system performance and capacity This feature has no impact on system performance or capacity. DN09185955 Issue: 01J © 2016 Nokia 55 . Modification of this parameter requires object locking. Impact on network and network element management tools This feature has no impact on network management or network element management tools. No 4. 3 and 4 • LTE497: Smart Admission Control The following features are suggested to be enabled: • LTE10: EPS bearers for conversational voice To support the IMS conversational voice. 4. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features • LTE7: Support of Multiple EPS bearer • LTE534: ARP Based Admission Control • LTE496: Support of QCI 2. 4.2 Activating and configuring LTE520: 8 EPS bearers per UE Before you start The Activate Support of 8 EPS Bearers (act8EpsBearers) parameter is used for activation. Measurements and counters There are no measurements or counters related to this feature.4. • LTE587: Multiple GBR EPS Bearers per UE To support the multiple UM DRBs.4. Parameters There are no parameters related to this feature.5 LTE520: 8 EPS bearers per UE management data Alarms There are no alarms related to this feature. Impact on interfaces This feature has no impact on interfaces. Key performance indicators There are no key performance indicators related to this feature. LTE RL60.1. perform the steps described in this procedure. c) Expand the LNBTS object. 5 Cells unlocking. Descriptions of radio resource management and LTE RL60. g Note: In case the LTE914: Graceful cell shut down feature is active. d) Select the LNCEL object. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. Feature Descriptions and Instructions telecom features The following features need to be activated and configured before activation of LTE520: 8 EPS bearers per UE: • LTE7: Support of Multiple EPS bearer • LTE496: Support of QCI 2. b) Expand the MRBTS object. a) Go to the Radio Network Configuration page. a) Go to the Radio Network Configuration page. a) Go to the Radio Network Configuration page. d) Select the LNCEL object. 3 Cells locking. 2 Activate the LTE520: 8 EPS bearers per UE feature. e) Set the Administrative state (administrativeState) parameter value to locked for all cells configured in eNB. set the Administrative state (administrativeState) parameter value to shutting down for all cells configured in eNB. 3 and 4 • LTE497: Smart Admission Control • LTE534: ARP Based Admission Control Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. d) Set the Activate Support of 8 EPS Bearers ( act8EpsBearers) parameter value to true. c) Select the LNBTS object. 56 © 2016 Nokia DN09185955 Issue: 01J . b) Expand the MRBTS object. b) Expand the MRBTS object. c) Expand the LNBTS object. 4 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. d) Set the Activate Support of 8 EPS Bearers ( act8EpsBearers) parameter value to false. 3 Cells locking a) Go to the Radio Network Configuration page. LTE RL60.3 Deactivating LTE520: 8 EPS bearers per UE Before you start The Activate Support of 8 EPS Bearers (act8EpsBearers) parameter is used for deactivation. c) Select the LNBTS object. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. b) Expand the MRBTS object. 4. DN09185955 Issue: 01J © 2016 Nokia 57 .4. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features e) Set the Administrative state (administrativeState) parameter value to unlocked for all cells configured in eNB. perform the steps described in this procedure. b) Expand the MRBTS object. c) Expand the LNBTS object. e) Set the Administrative state (administrativeState) parameter value to locked for all cells configured in eNB. 2 Deactivate the LTE520: 8 EPS bearers per UE feature. Expected Outcome Feature LTE520: 8 EPS bearers per UE has been activated and up to eight EPS bearers can be established per UE. d) Select the LNCEL object. 6 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Modification of this parameter requires object locking. g Note: In case the LTE914: Graceful cell shut down feature is active. set the Administrative state (administrativeState) parameter value to shutting down for all cells configured in eNB. a) Go to the Radio Network Configuration page. 5. Feature Descriptions and Instructions telecom features 4 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Otherwise.1 Benefits End-user benefits The end-user benefits from reduced crosstalk between cells. as well as the base sequence for sounding reference signal (SRS) on a per slot basis. Expected Outcome Feature LTE520: 8 EPS bearers per UE has been deactivated. Descriptions of radio resource management and LTE RL60.5 LTE801: Group hopping for UL reference signal 4. 4. the end-user experience will be similar if careful network planning is done.1. 4.2 Requirements Software requirements Table 20: Software requirements lists the software required for this feature. 4.1 Description of LTE801: Group hopping for UL reference signal Introduction to the feature The LTE801: Group hopping for UL reference signal randomizes the base sequence for the uplink (UL) demodulation reference signal of the physical uplink shared channel (PUSCH) and the physical uplink control channel (PUCCH). This is only if the planning for the UL demodulation reference signal in the network is not optimal.5. 6 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. 58 © 2016 Nokia DN09185955 Issue: 01J . which may result to improvements in the UL and DL performance of the network. b) Expand the MRBTS object.1. 5 Cells unlocking a) Go to the Radio Network Configuration page.5. e) Set the Administrative state (administrativeState) parameter value to unlocked for all cells configured in eNB. c) Expand the LNBTS object. Operator benefits This feature does not require reference signal planning or configuration. d) Select the LNCEL object. 4. The UEs are informed via the SIB2 broadcast message whenever group hopping in a cell is enabled/disabled. planning of the UL demodulation reference signal is unnecessary.3 Functional description With the LTE801: Group hopping for UL reference signal activated. g Note: The actual value of the parameter grpAssigPusch for the UL demodulation reference signal for PUSCH does not matter in network planning because of the overlaying UL group hopping pattern.0 - UE NetAct MME SAE GW 3GPP R8 mandatory NetAct8 EP1 . Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 20 Software requirements System release Flexi Multiradio BTS Flexi Multiradio OMS 10 BTS RL60 LBTS6. counter. for example. key performance indicator. and SRS if planning for the UL demodulation reference signal in the network is not optimal. LTE RL60.5. Impact on interfaces This feature has no impact on interfaces (but reference signal hopping is visible on Uu). The downlink (DL) performance may be impacted if. The random pattern changes with the underlying physical cell ID so that each physical cell ID gives a unique group pattern within the radio frame.1. the base sequence for the UL demodulation reference signal for PUSCH and PUCCH. - Hardware requirements This feature requires no new or additional hardware.5. 4. The parameter actUlGrpHop is used to activate this feature.0 LBTS6. as well as the base sequence for SRS are changed randomly. Impact on network and network element management tools If this feature is activated in the radio access network (RAN). 4. Impact on system performance and capacity This feature brings performance improvement for the PUSCH. Alarms DN09185955 Issue: 01J © 2016 Nokia 59 .5. the ACK/NACK in UL is improved. and parameter documents.1.1. Applying group hopping. see Reference documentation.4 System impact Interdependencies between features There are no interdependencies between this and any other feature. the cell planning of the UL reference signal is unnecessary since the crosstalk of the sequence is on a very small level and averaged across the network. PUCCH.5 LTE801: Group hopping for UL reference signal management data For information on alarm. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 21: New parameter lists the parameter introduced with this feature. b) Expand the MRBTS object. d) Select the LNCEL object corresponding to the cell where the LTE801: Group hopping for UL reference signal feature will be activated. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. Feature Descriptions and Instructions telecom features There are no alarms related to this feature.2 Activating and configuring LTE801: Group hopping for UL reference signal Before you start Restart of the eNB is not required after activation of this feature. 60 © 2016 Nokia DN09185955 Issue: 01J . Measurements and counters There are no measurements or counters related to this feature. Table 21 New parameter Full name Abbreviated name Managed object Activation of uplink group actUlGrpHop LNCEL hopping 4.5. Modification of this parameter requires object locking. a) Go to the Radio Network Configuration page.5. c) Expand the LNBTS object.6 Sales information Table 22 Sales information BSW/ASW License control in network Activated by default element ASW SW Asset Monitoring No 4.1. The Activation of uplink group hopping (actUlGrpHop) parameter is used to activate the feature. perform the steps described in this procedure. 2 Set the activation flag. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. Descriptions of radio resource management and LTE RL60. Expected Outcome The LTE801: Group hopping for UL reference signal feature is activated in the cell. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. The Activation of uplink group hopping (actUlGrpHop) parameter is used to deactivate the feature.3 Deactivating LTE801: Group hopping for UL reference signal Before you start Restart of the eNB is not required after deactivation of this feature. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. c) Select the LNCEL object corresponding to the cell where the LTE801: Group hopping for UL reference signal feature will be deactivated. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features e) Set the Activation of uplink group hopping (actUlGrpHop) parameter value to true. perform the steps described in this procedure. 2 Go to the Radio Network Configuration page. Modification of this parameter requires object locking. b) Expand the LNBTS object. 4. g Note: This parameter activates the feature. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. LTE RL60. DN09185955 Issue: 01J © 2016 Nokia 61 . a) Expand the MRBTS object.5. d) Set the Activation of uplink group hopping (actUlGrpHop) parameter value to false. Expected outcome The LTE801: Group hopping for UL reference signal feature is deactivated in the cell. 0 LBTS6. Table 23 Software requirements System release Flexi Multiradio BTS Flexi Multiradio OMS 10 BTS RL60 LBTS6. Feature Descriptions and Instructions telecom features 4. When voice call is initiated or received on CDMA/1xRTT system by the UE.0 - UE NetAct MME SAE GW 3GPP R9 UE capabilities NetAct8 EP1 . 4.3 Functional description The Flexi Multiradio BTS supports the RRC-release-based Circuit Switched Fallback (CSFB) to CDMA/1xRTT for dual receiver multimode UEs and for single radio UEs emulating dual receiver mode. The eNB indicates with the SIB 8 the related capabilities to the UE.1 Benefits End-user benefits This feature does not affect the end-user experience.6. With the feature.6 LTE874: CSFB to CDMA/1xRTT for dual RX Ues 4.6.2 Requirements Software requirements The table lists software required for this feature. - Hardware requirements This feature requires no new or additional hardware. the eNB releases the RRC connection to allow voice call setup on CDMA. Descriptions of radio resource management and LTE RL60.1 Description of LTE874: CSFB to CDMA/1xRTT for dual RX Ues Introduction to the feature The LTE874: CSFB to CDMA/1xRTT for dual RX Ues feature introduces service continuity for CS voice. 4.1.6.6. The following scenarios are supported: • Mobile-originated CSFB with an Initial context setup (UE in IDLE prior to CSFB) • Mobile-originated CSFB with a UE context modification (UE in RRC-connected prior to CSFB) 62 © 2016 Nokia DN09185955 Issue: 01J . Operator benefits This feature benefits the operator by redirecting call setup for voice calls 4.1. UE supporting dual Rx 1xCSFB stays attached to CDMA/1xRTT network to perform idle mode mobility procedures and to listen paging also while being in RRC-connected state to the LTE network.1. An Emergency Session is active for a UE if: • feature LTE874: CSFB to CDMA/1xRTT for dual RX Ues is activated in the eNB (actDualRx1xCsfb) • AND – RRC establishment cause for this UE has been set to “emergency” AND the INITIAL UE MESSAGE has not been sent yet or – Initial Context Setup Request has been received with “CS Fallback Indicator” = “CS Fallback High Priority”. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features • Mobile-terminated CSFB with an Initial context setup (UE in IDLE prior to CSFB) • Mobile-terminated CSFB with a UE context modification (UE in RRC-connected prior to CSFB) • Mobile-originated CSFB with a UE in RRC IDLE • Mobile-terminated CSFB with a UE in RRC IDLE The MME triggers in all cases the CSFB procedure at the eNB by sending the IE CS Fallback Indicator within the S1AP:UE Context Modification Request (RRC connected cases) or Initial context setup request (RRC idle cases) message to the eNB. RRCConnectionRelease message has not been sent yet and the Initial Context Setup Request is not rejected by the eNB. Towards MME. or DN09185955 Issue: 01J © 2016 Nokia 63 . There is no need for redirect information or measurements as the UE is already attached to CDMA/1xRTT. the eNB will send S1AP: UE context release request with cause value “Redirection towards 1xRTT” (though terminal still gets an RRC release without actual redirection). LTE RL60. The eNB performs upon the CSFB trigger an RRC connection release without redirect information for UEs. The following performance counters are supported. Emergency session The eNB is able to determine whether an Emergency Session is active for the feature LTE874: CSFB to CDMA/1xRTT for dual RX Ues. The eNB indicates within the SIB8 the capability to support dual receiver UEs. The following existing PM counters under LNCEL are updated: • CS Fallback attempts with redirection via RRC Connection Release (M8016C11) • CS Fallback attempts (UE in Connected Mode) with redirection via RRC Connection Release (M8016C12) • CS Fallback attempts for emergency call reason with redirection via RRC Connection Release (M8016C13) The following existing PM counters under LNCEL are reused: • UE Context modification attempts (M8000C23) • UE Context modification failures (M8000C25) • UE Context modification attempts because of to CS Fallback (M8000C31) The operator can enable/disable the functionality per cell by O&M setting. and RRCConnectionRelease message has not been sent yet and the UE Context Modification Request is not rejected by the eNB. the R8/R9 (e)1xCSFB options defined in LTE1441: Enhanced CS fallback to CDMA/1xRTT (e1xCSFB) are attempted. The CDMA system time is broadcasted together with other SIB8 parameters. these features need to be deactivated. Descriptions of radio resource management and LTE RL60. if UE have dual receiver but not support R9 e1xCSFB. which will be treated as emergency call during 1xCSFB procedure. LTE807: Idle mode mobility LTE to CDMA/1xRTT is not a precondition for LTE874: CSFB to CDMA/1xRTT for dual RX Ues. otherwise. When both LTE874: CSFB to CDMA/1xRTT for dual RX Ues and LTE1074: Multimedia priority services are activated. – in case that LTE874: CSFB to CDMA/1xRTT for dual RX Ues is deactivated but LTE1441: Enhanced CS fallback to CDMA/1xRTT (e1xCSFB) is activated.1. the eNB will perform the legacy R8/R9 (e)1xCSFB • LTE807: Idle mode mobility LTE to CDMA/1xRTT LTE807: Idle mode mobility LTE to CDMA/1xRTT introduces the broadcast of SIB8. Enabling of LTE874: CSFB to CDMA/1xRTT for dual RX Ues implicitly enables LTE426: System time broadcast for SIB8 automatically. SIB8 broadcasting is enabled automatically if LTE874: CSFB to CDMA/1xRTT for dual RX Ues is activated • LTE426: System time broadcast for SIB8 This feature introduces the CDMA system time support from the GPS timing. Feature Descriptions and Instructions telecom features – UE Context Modification Request has been received with “CS Fallback Indicator” = “CS Fallback High Priority”. LTE874: CSFB to CDMA/1xRTT for dual RX Ues will not have any special handling for high priority call except the case of receipt of Initial Context Setup Request/UE Context Modification Request with CS Fallback High Priority indicator. • LTE562: CSFB to UTRAN or GSM via redirect • LTE22: Emergency call handling • LTE736: CS Fallback to UTRAN The following features have also impact to LTE874: CSFB to CDMA/1xRTT for dual RX Ues: • LTE1441: Enhanced CS fallback to CDMA/1xRTT (e1xCSFB) LTE1441: Enhanced CS fallback to CDMA/1xRTT (e1xCSFB) could be activated parallel with LTE874: CSFB to CDMA/1xRTT for dual RX Ues. 4. eNB will make 1xCSFB decision according to UE capability: – in case that both LTE874: CSFB to CDMA/1xRTT for dual RX Ues and LTE1441: Enhanced CS fallback to CDMA/1xRTT (e1xCSFB) are activated. • LTE1074: Multimedia priority services LTE1074: Multimedia priority services feature introduces the priority-controlled admission and pre-emption of RRC connections and active UEs as well as paging priority handling.4 System impact Interdependencies between features The following features introduce CSFB to GERAN/UTRAN. When LTE874: CSFB to CDMA/1xRTT for dual RX Ues is active. then eNB will execute Dual Rx 1xCSFB option. • LTE572: IMS emergency sessions 64 © 2016 Nokia DN09185955 Issue: 01J .6. LTE RL60. But for one specific UE. Impact on system performance and capacity This feature has no impact on system performance or capacity. LTE874: CSFB to CDMA/1xRTT for dual RX Ues is supported while other CDMA interworking features are still not supported.4 MHz/3 MHz) configuration. During such an RRC Reconfiguration no other RRC procedure may be performed to avoid inconsistent configuration in the UE.4 MHz These features can be activated with LTE874: CSFB to CDMA/1xRTT for dual RX Ues in parallel (no feature dependency rule is defined in eNB between these features and LTE874: CSFB to CDMA/1xRTT for dual RX Ues). • LTE116: Cell Bandwidth - 3 MHz • LTE117: Cell Bandwidth - 1. only LTE572: IMS emergency sessions or LTE874: CSFB to CDMA/1xRTT for dual RX Ues could happen. RRC: RRCConnectionRelease for LTE874: CSFB to CDMA/1xRTT for dual RX Ues might have to be delayed if an SCell addition/release is ongoing. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features LTE572: IMS emergency sessions introduces IMS emergency session. In small cell bandwidth (1. • LTE1089: Downlink carrier aggregation - 20 MHz • LTE1558: TDD Downlink carrier aggregation • LTE1830: TDD downlink carrier aggregation enhancement Impact on interfaces This feature impacts interfaces as follows: • S1–Interface – S1AP: INITIAL CONTEXT SETUP REQUEST and S1AP: UE CONTEXT MODIFICATION REQUEST -> reuse field “CS Fallback indicator” • RRC – Interface: – RRC: UECapabilityInformation -> reuse and newly support EUTRA Capability: rx- Config1xRTT – RRC: RRCConnectionRelease -> reuse – RRC: SIB8 -> add csfb-SupportForDualRxUEs support Impact on network and network element management tools This feature has no impact on network management or network element management tools. • LTE56: Inter RAT handover to WCDMA • LTE442: Network Assisted Cell Change • LTE898: TDD inter-RAT handover to TD-SCDMA • LTE873: SRVCC to GSM • LTE908: ANR Inter-RAT UTRAN - Fully UE based For (de-)configuration of SCell RRC Connection Reconfiguration procedures are started without any eNB external triggering event. DN09185955 Issue: 01J © 2016 Nokia 65 . Therefore. This feature could be active in parallel with LTE874: CSFB to CDMA/1xRTT for dual RX Ues. 5 LTE874: CSFB to CDMA/1xRTT for dual RX Ues management data Alarms There are no alarms related to this feature. Table 25 New parameter Full name Abbreviated name Managed object Activate CSFB to CDMA 1xRTT for dual actDualRx1xCsfb LNBTS Rx UEs The table lists parameters which are updated or reused with this feature. Table 24 Counters Counter ID Counter name Measurement M8016C11 CS Fallback attempts via RRC Connection 8016 - LTE Inter System Release Handover (WBTS) M8016C12 CS Fallback attempts (UE in Connected 8016 - LTE Inter System Mode) via RRC Connection Release Handover (WBTS) M8000C23 UE Context modification attempts 8000 - LTE S1AP (WBTS) M8000C25 UE Context modification failures 8000 - LTE S1AP (WBTS) M8000C31 UE Context modification attempts due to 8000 - LTE S1AP (WBTS) CS Fallback Key performance indicators There are no key performance indicators related to this feature. Descriptions of radio resource management and LTE RL60.6. Parameters There is only one new parameters related to this feature.1. Feature Descriptions and Instructions telecom features 4. Measurements and counters The table lists counters which are updated or reused with this feature. Table 26 Updated or reused parameters Full name Abbreviated name Managed object Activate CS Fallback Via Redirection actCSFBRedir LNBTS Activate Emergency Call Via Redirection actEmerCallRedir LNBTS Activate CS Fallback with PS-HO to actCsfbPsHoToUtra LNBTS UTRA System Information Scheduling List sibSchedulingList SIB 66 © 2016 Nokia DN09185955 Issue: 01J . LTE736: CS Fallback to UTRAN) must be deactivated. Table 28 Parameters used for activating and configuring LTE874: CSFB to CDMA/1xRTT for dual RX UEs Parameter Purpose Requires eNB restart or object locking Activate CSFB to CDMA activation flag no 1xRTT for dual Rx UEs (actDualRx1xCsfb) System Information mandatory configuration no Scheduling List (sibSchedulingList) SIB Type mandatory configuration no (siMessageSibType) The following features need to be deactivated before activation of LTE874: CSFB to CDMA/1xRTT for dual RX UEs: • LTE22: Emergency Call Handling (actEmerCallRedir is set to Disabled ) • LTE562: CSFB To UTRAN or GSM Via Redirect (actCSFBRedir is set to Disabled ) • LTE736: CS Fallback to UTRAN (actCsfbPsHoToUtra is set to false) DN09185955 Issue: 01J © 2016 Nokia 67 .) Full name Abbreviated name Managed object SIB Type siMessageSibType SIB Naming attribute of MOC CDFIM cdfimId CDFIM 4.6 Sales information Table 27 Sales information BSW/ASW License control in License control Activated by default network element attributes ASW SW Asset Monitoring No 4.2 Activating and configuring LTE874: CSFB to CDMA/1xRTT for dual RX UEs Before you start Before activating LTE874: CSFB to CDMA/1xRTT for dual RX UEs all CSFB to GERAN/UTRAN features (LTE22: Emergency call handling. LTE562: CSFB to UTRAN or GSM via redirect.6.1. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 26 Updated or reused parameters (Cont.6. LTE RL60. Restart of the eNB is not required after activation of this feature. .. e) Set the CDMA search window size to a value between 0 . f) Set the Repetition (siMessageRepetition ) parameter to a value between 1– 4. Feature Descriptions and Instructions telecom features Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. a) Go to the Radio Network Configuration page. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. b) Expand the MRBTS object... a) Go to the Radio Network Configuration page. 7 g) Set the CDMA2000 HRPD cell reselection timer to a value between 0 . c) Create CDFIM object. b) Go to MRBTS ► LNBTS ► LNCEL object. c) Select System information scheduling list and create a new SIB list g Note: To create a new SIB list. 15 f) Set the CDMA2000 1xRTT cell reselection timer to a value between 0 . click the right mouse button and select New System Information Schedule list d) Set the SIB type (siMessageSibType) parameter value to SIB8. a) Go to the Radio Network Configuration page. click the right mouse button and select CDFIM d) Set the CDMA2000 frequency idle mode configuration identifier parameter value to 1. perform the steps described in this procedure. 2 Activate/Configure the feature LTE874: CSFB to CDMA/1xRTT for dual RX UEs. Descriptions of radio resource management and LTE RL60. 3 Create the System information scheduling list. d) Set the Activate CSFB to CDMA 1xRTT for dual RX UEs (actDualRx1xCsfb) parameter value to true. The following parameters are optional - no need to set for activation. g Note: To create a new CDFIM. 7 68 © 2016 Nokia DN09185955 Issue: 01J . c) Select the LNBTS object. 4 Create the CDFIM parameters. b) Go to MRBTS ► LNBTS ► LNCEL ► SIB object. e) Set the Periodicity (siMessagePeriodicity) parameter to a value between 80ms and 5120ms... 2 Deactivate the feature LTE874: CSFB to CDMA/1xRTT for dual RX UEs. a) Go to the Radio Network Configuration page. c) Select the LNBTS object. 4.6. Modification of this parameter does not require eNB restart. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 5 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.3 Deactivating LTE874: CSFB to CDMA/1xRTT for dual RX UEs Before you start The Activate CSFB to CDMA 1xRTT for dual Rx UEs (actDualRx1xCsfb) parameter is used for deactivation.7. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.7 LTE944: PUSCH masking 4. perform the steps described in this procedure. 4. Expected outcome The feature LTE874: CSFB to CDMA/1xRTT for dual RX UEs is deactivated. b) Expand the MRBTS object. d) Set the Activate CSFB to CDMA 1xRTT for dual RX UEs (actDualRx1xCsfb) parameter value to false. LTE RL60. Result The feature LTE874: CSFB to CDMA/1xRTT for dual RX UEs is activated. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager.1 Description of LTE944: PUSCH masking Introduction to the feature DN09185955 Issue: 01J © 2016 Nokia 69 . 4.7. Maximum of two PUSCH masks can be configured. In addition. An FD scheduler considers only the non-masked PRBs for scheduling in the PUSCH spectrum.0 - UE NetAct MME SAE GW n/a NetAct8 EP1 . such as static reuse schemes.0 LBTS6.1. Only PUSCH physical resource blocks (PRBs) are masked by this feature.7. Typically. - Hardware requirements This feature requires no new or additional hardware. Feature Descriptions and Instructions telecom features The LTE944: PUSCH masking feature provides an option for masking physical uplink shared channel (PUSCH) sub-areas that are not supposed to be granted to the UEs with data in the uplink (UL) transmission buffer. Descriptions of radio resource management and LTE RL60.3 Functional description The Flexi Multiradio BTS supports O&M-based masking of PRBs for PUSCH in the frequency domain scheduler.2 Requirements Software requirements Table 29: Software requirements lists the software required for this feature. 4. The LTE944: PUSCH masking provides a simple way to permanently mask a PUSCH sub-spectrum.7.1 Benefits End-user benefits This feature does not affect the end-user experience. PRBs that are allocated by the physical random access channel (PRACH) at least once per radio frame cannot be selected for masking.1. Operator benefits This feature provides a flexible way of handling the UL interference problems. The PUSCH sub-area being masked is defined by two O&M parameters: the starting PRB 70 © 2016 Nokia DN09185955 Issue: 01J . 4. The PUSCH sub-area to be masked is identified by two O&M parameters: the first parameter defines the starting PRB and the second parameter specifies PUSCH mask size by the number of PRBs.1. which should not be granted to the UEs. a masked PUSCH sub-area is affected by the UL interference. Table 29 Software requirements System release Flexi Multiradio BTS Flexi Multiradio OMS 10 BTS RL60 LBTS6. The PRB mask is treated by the UL scheduler as permanent virtual users blocking certain PRBs. The LTE944: PUSCH masking feature provides a way to overcome static interference issues between adjacent cells (to set up or to guard other services which use a small spectrum inside the LTE spectrum) or cells that may be disturbed by crosstalk. This feature can be enabled or disabled per cell O&M settings. Disabling the SRS affects the LTE46: Channel Aware Scheduler (UL) and LTE1495: Fast uplink link adaptation features. This leads to a decrease in channel aware scheduler gain as compared to the case where SRS is enabled. Whenever the PUSCH mask affects more than half of the PRBs. When SRS is enabled. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features and the number of PRBs to be masked. DN09185955 Issue: 01J © 2016 Nokia 71 . which leads to strong PUSCH sub-areas of varying sizes. the evaluation of channel state and carrier frequencies is based only on PUSCH transmission. The move of any UE from the initially allocated PUSCH sub-area to one of the remaining PUSCH sub-areas is prevented due to the lack of resources in the considerably smaller PUSCH sub-areas. LTE RL60. If for such a PUSCH mask configuration. The PRB mask is operator-configurable per cell and up to two areas of consecutive PUSCH PRBs can be masked. These two features can be enabled even though the SRS is not configured. The PUSCH mask is configured to guarantee enough resources for the configuration of the PRACH (6 PRBs) within the PUSCH spectrum. The channel aware scheduler is allowed in combination with PUSCH masking. When SRS is disabled. The SRS has to be disabled whenever this feature is enabled to protect the services located in the masked PUSCH sub-area from interfering signals. If this is not possible. the UL scheduler has to schedule the UEs based only on the CSI coming from PUSCH transmissions. which leads to restrictions in the overall PRB allocations and hence in peak as well as in cell throughput. Since the SRS is disabled whenever PUSCH masking is enabled. Certain conditions apply to LTE944: PUSCH masking: • PUSCH masking cannot be performed with the following narrow-band features: – LTE115: 5MHz system bandwidth – LTE116: 3 MHz system bandwidth – LTE117: 1. For such a scenario. it is likely that not all available PUSCH PRBs are assigned to the UEs with non-GBR bearers. then the PRB assignment procedure might stop after all the resources of the initially allocated PUSCH sub-area are exhaust. PRACH regions cannot be masked. the scheduling area cannot be selected as the preferred scheduling area. the number of scheduling areas shall be defined when applicable so that the PUSCH mask falls completely within one or more scheduling area(s) and the masked scheduling areas can be excluded from the determination of the preferred scheduling area. PUSCH transmission is also used as a basis to obtain channel state information (CSI) measurements that indicate link quality. The restrictions in scheduling non-GBR bearers are possible for PUSCH mask configuration. By configuring the eNB. The PRB assignment is done by the weighted round robin (WRR) scheduler. the UL scheduler evaluates the average I+N power for the restricted scheduling area only for the non-masked PUSCH PRBs and handles the affected scheduling area in a similar manner as the unaffected scheduling areas.4 MHz system bandwidth • Concurrent allocation of PUSCH mask and PRACH in the PUSCH spectrum is prohibited since allocation of PUSCH mask overrules the PRACH allocation. the LTE619: Interference aware UL Scheduler or LTE46: Channel Aware Scheduler (UL) feature is selected and the preferred scheduling area falls into the largest PUSCH sub-area. The PUSCH PRB mask cannot be used in combination with sounding reference signal (SRS). The use of the PRB mask might lead to decrease in: • peak rate for normal users • less frequency diversity for normal users as the UL scheduler is restricted in random hopping for channel unaware scheduler • less fair resource assignment 4.1. Descriptions of radio resource management and LTE RL60. – The random access channel (RACH) optimization process has to consider the location of the PUSCH masks within the PUSCH spectrum and has to prevent the overlapping of PRACH and PUSCH mask.7.4 MHz cell bandwidth • LTE116: 3 MHz cell bandwidth • LTE115: 5 MHz cell bandwidth Impact on interfaces This feature has no impact on interfaces.4 System impact Interdependencies between features The LTE46: Channel Aware Scheduler and LTE1495: Fast uplink link adaptation features can be enabled together with this feature. Feature Descriptions and Instructions telecom features g Note: – In case the PRACH Management feature determines the optimum PRACH location within the PUSCH mask area. • Two PUSCH masks cannot overlap. The following features are affected by this feature: • LTE619: Interference aware UL Scheduler • LTE581: PRACH Management • LTE962: RACH Optimization • LTE28: Closed Loop UL Power Control The following features are not supported in combination with this feature: • LTE117: 1. 72 © 2016 Nokia DN09185955 Issue: 01J . however. the next best configuration that does not overlap with the PUSCH mask is selected for the location of the PRACH. g Note: The setting of all other O&M parameters that can affect the suitable behavior of the eNB is controlled by the operator. only PUSCH information is used. Impact on network and network element management tools This feature has no impact on network management or network element management tools. • SRS is disabled independent of the selected FD scheduling approach whenever a PUSCH mask is specified for a cell. Impact on system performance and capacity System performance is impacted because the peak rate and the maximum cell throughput are decreased. Parameters Table 30: New parameters lists parameters introduced with this feature. LTE RL60. counter. Alarms There are no alarms related to this feature.6 Sales information Table 32 Sales information BSW/ASW License control in network Activated by default element ASW SW Asset Monitoring No DN09185955 Issue: 01J © 2016 Nokia 73 . see Reference documentation.5 LTE944: PUSCH masking management data For information on alarm.1. Table 31 Related existing parameters Full name Abbreviated name Managed object Structure Method for UL power actUlpcMethod LNCEL control PRACH frequency prachFreqOff LNCEL offset Uplink channel ulChBw LNCEL bandwidth 4. and parameter documents. key performance indicator. Key performance indicators There are no key performance indicators related to this feature.1. Measurements and counters There are no measurements or counters related to this feature.7. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features The reduction of the RAN system capacity is proportional to the number of PRBs. Table 30 New parameters Full name Abbreviated name Managed object Structure Activate PUSCH actPuschMask LNCEL masking PUSCH mask ulsPuschMask LNCEL Length of the PUSCH ulsPuschMaskLength LNCEL ulsPuschMask mask Start PRB of the ulsPuschMaskStart LNCEL ulsPuschMask PUSCH mask Table 31: Related existing parameters lists existing parameters related to this feature.7. 4. which are spent for the PUSCH mask. PUSCH information is used and SRS will not be used. These features will work in modified modes. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. however. which may result in reduced gains. Table 33 Parameters used for activating and configuring LTE944: PUSCH masking Parameter Purpose Requires eNB restart or object locking Activate PUSCH masking Activation flag Object locking (actPuschMask) PUSCH mask Mandatory configuration Object locking (ulsPuschMask) set of parameters Length of the PUSCH Mandatory configuration Object locking mask (ulsPuschMaskLengt h) Start PRB of the PUSCH Mandatory configuration Object locking mask (ulsPuschMaskStart ) g Note: The LTE46: Channel Aware Scheduler and LTE1495: Fast uplink link adaptation can be enabled together with this feature. perform the steps described in this procedure. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. Feature Descriptions and Instructions telecom features 4.7. 74 © 2016 Nokia DN09185955 Issue: 01J . These features are expected to cause the following: • The channel aware scheduler will derive the channel state information (CSI) exclusively from the demodulation reference signal. Descriptions of radio resource management and LTE RL60. The following features are not supported in combination with this feature: • LTE117: 1. • The fast UL link adaptation evaluates only the received signal strength indicator (RSSI) coming from PUSCH.4 MHz cell bandwidth • LTE116: 3 MHz cell bandwidth • LTE115: 5 MHz cell bandwidth The channel bandwidth must be greater than or equal to 10 MHz.2 Activating and configuring LTE944: PUSCH masking Before you start Activation of this feature requires object locking. The SRS does not provide any measurements for this case. c) In each LNCEL object under selected LNBTS. Select and right-click on the PUSCH mask under LNCEL object. g Note: Maximum of two masks can be defined/created. 4. d) Select the LNCEL object corresponding to the cell where the LTE944: PUSCH masking feature will be activated. 3. 5. Select New PUSCH mask-2 and define all the parameters within this object. 2. b) Expand the MRBTS object. 4. 4 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.3 Deactivating LTE944: PUSCH masking Before you start Deactivation of this feature requires object locking. a) Go to the Radio Network Configuration page. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 2 Set the activation flag. a) Expand the MRBTS object. g Note: This parameter activates the feature. right-click on the LNCEL object and select New PUSCH mask.7. Select PUSCH mask-1 and define all the parameters within this object. e) Set the Activate PUSCH masking (actPuschMask) parameter value to true. repeat the following actions: 1. Expand PUSCH mask under LNCEL object. b) Expand the LNBTS object. DN09185955 Issue: 01J © 2016 Nokia 75 . c) Expand the LNBTS object. 3 Define PUSCH mask (ulsPuschMask). LTE RL60. Expected Outcome The LTE944: PUSCH masking feature is activated in the cell. If the PUSCH mask is not available under LNCEL. b) Expand the MRBTS object. 2 Set the Activate PUSCH masking (actPuschMask) parameter.8.8. c) Expand the LNBTS object. perform the steps described in this procedure. S1-MME (S1AP) and X2 (X2AP) interfaces. Operator benefits This feature provides the following benefits to the operator: • It helps to maintain reasonable control plane throughput during overload scenarios (for example. d) Select the LNCEL object corresponding to the cell where the LTE944: PUSCH masking feature will be deactivated. sport events. e) Set the Activate PUSCH masking (actPuschMask) parameter value to false. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. Expected outcome The LTE944: PUSCH masking feature is deactivated in the cell.1. a) Go to the Radio Network Configuration page.1 Description of LTE1047: Control plane overload handling Introduction to the feature The LTE1047: Control plane overload handling feature is introduced to deal with control plane overload resulting from signaling messages on Uu (RRC). but it helps to maintain the basic network services during overload situations. Feature Descriptions and Instructions telecom features Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. • Provides countermeasures to regulate the control plane load. 76 © 2016 Nokia DN09185955 Issue: 01J . 4. The functionality comprises of an overload management function and a set of overload countermeasures.8 LTE1047: Control plane overload handling 4. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Descriptions of radio resource management and LTE RL60. during New Year's Eve. 4. or in disaster areas) and prevents the eNB from crashing.1 Benefits End-user benefits This feature does not affect the end-user experience directly. the eNB is able to: • continue to process signaling messages during overload and successfully complete high percentage of the corresponding signaling procedures • operate under conditions where the CPU load of 70-80% is exceeded • protect itself against crashing The functionality is enabled with the Activation of C-plane overload handling (actCplaneOvlHandling) parameter. • overload level 2 (self-defense) DN09185955 Issue: 01J © 2016 Nokia 77 . With the introduction of the LTE1047: Control plane overload handling feature.1. which might last for longer periods of time. 4. ongoing services should be maintained and emergency/high priority calls should be prioritized. which last only for a short time.8. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4. The admission of new connections might be reduced and the quality of the connection decreased (for example. or by sustainable traffic increase.0 - UE NetAct MME SAE GW 3GPP R8 mandatory NetAct8 EP1 . the following overload levels are defined: • overload level 0 (normal operation) At normal state. Table 34 Software requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 LBTS6. Overload levels To deal with control plane overload effectively.8.1. because of delayed handovers). the following conditions are fulfilled: – KPIs are on target – the BHCA load does not exceeds the eNB capacity – the message queues are practically empty – overload thresholds are not exceeded • overload level 1 (graceful overload handling) At this overload level.0 LBTS6. LTE RL60.3 Functional description Functional overview Overload can be caused by traffic peaks.2 Requirements Software requirements Table 34: Software requirements lists the software required for this feature. - Hardware requirements This feature requires no new or additional hardware. Only the establishment of emergency sessions and high priority access are admitted. Applies countermeasures depending on overload state. If the parameter is set to false. Control plane overload countermeasures The following countermeasures are introduced: • Rejection of incoming handovers The incoming handover (HO) requests are rejected to reduce the load. the eNB rejects all non-emergency HO. All these actions are performed on the cell level. 2. The functionality is enabled with the Activate RRC connection reduction (actRrcConnRed) parameter. Monitors the C-Plane processing behavior. The same rule applies for level 2. the C-Plane overload state is always set to level 0 for all cells. and no countermeasures are applied. If the Activation of C-plane overload handling (actCplaneOvlHandling) parameter is set to true. New performance counters The countermeasures applied during overload might distort counters defined for different LTE features. 3.1.4 System impact Interdependencies between features Rejection of incoming handover requests affects the following handover-related features: • LTE53: Intra and Inter eNB Handover with X2 • LTE54: Intra-LTE Handover via S1 78 © 2016 Nokia DN09185955 Issue: 01J . the following performance counters are introduced to monitor the control plane overload functionality of the affected cells: • number of rejected RRC connection establishment requests for both emergency and non-emergency access • aggregated time period of control plane in overload level 1 and 2 For the detailed list. Feature Descriptions and Instructions telecom features At this overload level the system should protect itself against queue overflow and a system crash. In overload level 1. 4. The distortion of these counters should be proportional to the overload duration. the eNB: 1. In overload level 1. Descriptions of radio resource management and LTE RL60. • Rejection of RRC connection requests When an RRC connection request is received by the eNB. see the Measurements and counters section. or mo- signaling). mo-data. the reject message is sent back to the UE. The control plane overload level is evaluated based on message queuing time. Identifies the overload state. the eNB rejects low priority RRC connection requests (with Establishment Causes: delayTolerantAccess. For level 2. The functionality is enabled with the Activate incoming HO reduction (actInHORed) parameter. the eNB rejects incoming non-emergency HO without GBR bearer and HO cause other than Time Critical Handover or Handover Desirable for Radio Reasons. To quantify this distortion.8. 8. Parameters Table 36: New parameters lists parameters introduced with this feature. Impact on interfaces The overload countermeasures aim to reduce the signaling on Uu.5 LTE1047: Control plane overload handling management data Alarms There are no alarms related to this feature. Measurements and counters Table 35: New counters lists counters introduced with this feature. Table 35 New counters Counter ID Counter name Measurement M8013C29 Number of rejected RRC Connection LTE UE State Establishment Requests for non- emergency access M8013C30 Number of rejected RRC Connection LTE UE State Establishment Requests for emergency access M8001C149 Aggregated time period of Control Plane LTE Cell Load in overload level 1 M8001C152 Aggregated time period of Control Plane LTE Cell Load in overload level 2 Key performance indicators There are no key performance indicators related to this feature. Impact on system performance and capacity This feature has no impact on system performance or capacity. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features • LTE55: Inter-frequency Handover • LTE1060: TDD - FDD Handover • LTE1170: Inter-frequency Load Balancing Rejection of RRC Connection Request affects the LTE50: UE State Management feature.1. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Table 36 New parameters Full name Abbreviated name Managed object Structure Activation of C-plane actCplaneOvlHandling LNBTS overload handling Overload handling ovlha LNBTS DN09185955 Issue: 01J © 2016 Nokia 79 . LTE RL60. S1 and X2 interfaces. 4. Descriptions of radio resource management and LTE RL60, Feature Descriptions and Instructions telecom features Table 36 New parameters (Cont.) Full name Abbreviated name Managed object Structure Activate incoming HO actInHORed LNBTS ovlha reduction Activate RRC actRrcConnRed LNBTS ovlha connection reduction 4.8.1.6 Sales information Table 37 Sales information BSW/ASW License control in License control Activated by default network element attributes ASW SW Asset Monitoring - No 4.8.2 Activating and configuring LTE1047: Control plane overload handling Before you start Table 38 Parameters used for activating and configuring LTE1047: Control plane overload handling Parameter Purpose Requires eNB restart or object locking Activation of C-plane activation flag no overload handling (actCplaneOvlHand ling) Activate incoming HO mandatory configuration no reduction (actInHORed) Activate RRC connection mandatory configuration no reduction (actRrcConnRed) Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. 2 Set the activation flag. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. c) Select the LNBTS object. 80 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions Descriptions of radio resource management and telecom features d) Set the Activation of C-plane overload handling (actCplaneOvlHandling) parameter value to true. 3 Enable the overload countermeasures. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. c) Select the LNBTS object. d) Right-click on LNBTS object and add new Overload handling (ovlha) parameter structure. • To enable the incoming handover reduction, set the Activate incoming HO reduction (actInHORed) parameter value to true. • To enable the RRC Connection reduction, set the Activate RRC connection reduction (actRrcConnRed) parameter value to true. 4 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Expected Outcome The LTE1047: Control plane overload handling feature together with the enabled overload countermeasures is active in the eNB. 4.8.3 Deactivating LTE1047: Control plane overload handling Before you start The Activation of C-plane overload handling (actCplaneOvlHandling) parameter is used for deactivation. Modification of this parameter does not require eNB restart or cell locking. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. 2 Set the activation flag. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. c) Select the LNBTS object. DN09185955 Issue: 01J © 2016 Nokia 81 Descriptions of radio resource management and LTE RL60, Feature Descriptions and Instructions telecom features d) Set the Activation of C-plane overload handling (actCplaneOvlHandling) parameter value to false. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Expected Outcome The LTE1047: Control plane overload handling feature together with all the overload countermeasures is deactivated in the eNB. 4.9 LTE1074: Multimedia priority services 4.9.1 Description of LTE1074: Multimedia priority services Introduction to the feature The LTE1074: Multimedia priority services feature supports admission control for high priority services that require resources during network congestion. It extends the functionality of the LTE572: IMS Emergency Sessions feature, to support also other - not usual IMS emergency - prioritized sessions. 4.9.1.1 Benefits End-user benefits This feature does not affect the end-user experience directly, but it helps to: • maintain mobile-terminated accessibility for important services (for example, emergency calls or internal communication of rescue teams) in case of paging congestion • prioritize connection requests for these services during network congestion Operator benefits This feature allows the operator to control the connection requests in a prioritized manner. 4.9.1.2 Requirements Software requirements Table 39: Software requirements lists the software required for this feature. Table 39 Software requirements System release Flexi Multiradio BTS Flexi Multiradio OMS 10 BTS RL60 LBTS6.0 LBTS6.0 - UE NetAct MME SAE GW 3GPP R8 mandatory NetAct8 EP1 - - 82 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Hardware requirements This feature requires no new or additional hardware. 4.9.1.3 Functional description Functional overview The LTE1074: Multimedia priority services feature deals with priority services by introducing the following concepts: • Paging prioritization Paging resources are assigned according to the paging priority information element (IE) of its related S1AP: PAGING request. This solution helps to maintain mobile-terminated availability during paging congestion. • Recognition and handling high-priority RRC connections and E-RABs RRC connection requests and E-RABs with a high-priority allocation and retention priority (ARP) are recognized and prioritized using a method similar to the one already introduced with the LTE572: IMS Emergency Sessions feature. This solution allows prioritized services to get required resources. • Emergency callback If an RRC connection request is caused by an S1AP: PAGING message containing the paging priority IE, it is handled like a request with establishment cause set to Emergency. This solution allows the network to establish an emergency session with a UE that is prioritized like a mobile-originated emergency session. Handling prioritized services The whole functionality is enabled with the Activate high priority services (actHighPrioServices) parameter. If it is switched on, the following scenarios are applied: • During paging congestion, the surplus paging requests are discarded considering the priority. In practice, the requests without the paging priority are dropped first, and requests with the paging priority are dropped in the order of descending priority level. • The high priority access UEs are identified either by the RRC connection establishment cause (set to highPriorityAccess) or by dedicated operator- configurable high priority ARP values associated with data radio bearer. High priority calls are treated as emergency calls during admission control in serving cell and in target cell (during the handover). • A subsequent RRC connection request from a UE that has been paged with a paging priority is admitted like an emergency RRC connection request. Feature configuration The operator can define a range of ARP priority levels. Any ARP parameter matching this range is recognized as a high-priority ARP parameter. To define the minimum priority level, configure the High-priority session ARP priority level minimum (hpsSessArpMin) parameter. To define the maximum priority level, configure the High-priority session ARP priority level maximum (hpsSessArpMax) parameter. The operator can also configure the time interval for correlating S1 paging requests with the relevant RRC connection request messages. It is defined with the Timer paging correlation interval (tPageCorrInt) parameter. DN09185955 Issue: 01J © 2016 Nokia 83 Descriptions of radio resource management and LTE RL60, Feature Descriptions and Instructions telecom features For details on feature activation and configuration, see Activating and configuring LTE1074: Multimedia priority services. New performance counters To monitor the scale of prioritized connections, new counters are introduced to measure: • the number of signaling connection establishment attempts and completions for high priority calls • the E-RAB setup requests and completions for high priority calls For a detailed list of counters, see the Measurements and counters section. 4.9.1.4 System impact Interdependencies between features The following features need to be enabled before the activation of the LTE1074: Multimedia Priority Services feature : • LTE572: IMS emergency session • LTE534: ARP based admission control • LTE496: Support of QCI 2, 3, and 4 • LTE497: Smart admission control Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity When prioritized calls are served during network congestion, some connection requests for normal sessions might be dropped. 4.9.1.5 LTE1074: Multimedia priority services management data Alarms There are no alarms related to this feature. Measurements and counters Table 40: Existing counters lists existing counters for this feature. Table 40 Existing counters Counter ID Counter name Measurement M8006C186 E-RAB setup attempts LTE EPS Bearer (requests) for high priority calls M8006C187 E-RAB setup completions for LTE EPS Bearer high priority calls M8013C31 Signaling Connection LTE UE State Establishment attempts for high priority calls 84 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 40 Existing counters (Cont.) Counter ID Counter name Measurement M8013C32 Signaling Connection LTE UE State Establishment completions for high priority calls M8013C33 Number of rejected Signaling LTE UE State Connection Establishment Requests for high priority calls Key performance indicators There are no key performance indicators related to this feature. Parameters Table 41: New parameters lists parameters introduced with this feature. Table 41 New parameters Full name Abbreviated name Managed object Structure Activate high priority actHighPrioServices LNBTS services High-priority session hpsSessConfig LNBTS configurations High-priority session hpsSessArpMax LNBTS hpsSessConfig ARP priority level maximum High-priority session hpsSessArpMin LNBTS hpsSessConfig ARP priority level minimum Timer paging tPageCorrInt LNCEL correlation interval Table 42: Related parameterslists parameters related to other features that need to be activated. Table 42 Related parameters Full name Abbreviated name Managed object Activate enhanced AC and actEnhAcAndGbrServices LNBTS GBR services Activate support of IMS actIMSEmerSessR9 LNBTS emergency sessions for Rel 9 UE 4.9.1.6 Sales information Table 43 Sales information BSW/ASW License control in License control Activated by default network element attributes ASW SW Asset Monitoring - no DN09185955 Issue: 01J © 2016 Nokia 85 and 4 • LTE497: Smart Admission Control For details. the parameters in the IMS emergency PLMN configurations (imsEmerPlmnConfig) structure under the LNBTS object need to be configured for the selected PLMN. LTE497: Smart Admission Control. 86 © 2016 Nokia DN09185955 Issue: 01J . 2 Set the activation flag. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. 3 and 4. Feature Descriptions and Instructions telecom features 4. b) Expand the MRBTS object. Descriptions of radio resource management and LTE RL60.2 Activating and configuring LTE1074: Multimedia priority services Before you start Table 44 Parameters used for activating and configuring LTE1074: Multimedia priority services Parameter Purpose Requires eNB restart or object locking Activate high priority activation flag no services (actHighPrioServices) Timer paging correlation mandatory configuration no interval (tPageCorrInt) High-priority session ARP mandatory configuration no priority level minimum (hpsSessArpMin) High-priority session ARP mandatory configuration no priority level maximum (hpsSessArpMax) The following features need to be activated before activation of the LTE1074: Multimedia priority services feature: • LTE572: IMS Emergency Session • LTE534: ARP-based Admission Control for E-RABs • LTE496: Support of QCI 2. c) Select the LNBTS object. see Activating LTE496: Support of QCI 2. a) Go to the Radio Network Configuration page.9. 3. To handle the emergency callback and high priority access properly. LTE534: ARP Based Admission Control and Activating LTE572: IMS Emergency Sessions using BTS Site Manager. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. 3 Define the high priority level range for allocation and retention priority (ARP) parameters. b) Expand the MRBTS object. g Note: The hpsSessArpMin value must be less than or equal to hpsSessArpMax value. c) Expand the LNBTS object. a) Go to the Radio Network Configuration page. DN09185955 Issue: 01J © 2016 Nokia 87 . • To define the minimum priority level. b) Expand the MRBTS object. • To define the maximum priority level. g Note: Repeat this step for all cells of the eNB. LTE RL60. configure the High-priority session ARP priority level minimum (hpsSessArpMin) parameter. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features d) Set the Activate high priority services (actHighPrioServices) parameter value to true. c) Select the LNBTS object. 5 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. d) Select the LNCEL object. Expected Outcome The LTE1074: Multimedia priority services feature is enabled in the eNB. configure the High-priority session ARP priority level maximum (hpsSessArpMax) parameter. e) Define the correlation interval time using the Timer paging correlation interval (tPageCorrInt) parameter. d) Right-click on LNBTS object and add new High-priority session configurations (hpsSessConfig) parameter structure. a) Go to the Radio Network Configuration page. 4 Configure the time interval for correlating S1 paging and RRC connection request messages. for example.9. b) Expand the MRBTS object. Feature Descriptions and Instructions telecom features 4. 4.10. c) Select the LNBTS object. Modification of this parameter does not require eNB restart or cell locking. because of missing neighbor cell relations or tight site re-use scheme in re-farming scenarios. 88 © 2016 Nokia DN09185955 Issue: 01J .1 Description of LTE1198: RSRQ Triggered Mobility Introduction to the feature The LTE1198: RSRQ triggered mobility introduces inter-frequency and inter-RAT mobility based on RSRQ triggers. 4. Operator benefits This feature benefits the operator by allowing it to better cope with high inter-cell interference scenarios.1 Benefits End-user benefits This feature does not affect the end-user experience. d) Set the Activate high priority services (actHighPrioServices) parameter value to false.10 LTE1198: RSRQ triggered mobility 4. Descriptions of radio resource management and LTE RL60. Expected Outcome The LTE1074: Multimedia priority services feature is deactivated in the eNB. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.10.1. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. 2 Set the activation flag. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure.3 Deactivating LTE1074: Multimedia priority services Before you start The Activate high priority services (actHighPrioServices) parameter is used for deactivation. a) Go to the Radio Network Configuration page. 4.1. The functionality can be enabled / disabled per eNode B by O and M settings.10. 4.0 LBTS6. LTE RL60.1.3 Functional description The Flexi Multiradio BTS supports besides the A2 RSRP trigger.10. The report amount for the A1 event is set to infinity and the report interval for the A1 event is operator- configurable. • LTE55: Inter-frequency Handover • LTE56: Inter RAT Handover to WCDMA • LTE872: SRVCC to WCDMA • LTE1060: TDD - FDD handover • LTE60: Inter-RAT Handover to eHRPD/3GPP2 • LTE442: Network Assisted Cell Change to GSM • LTE873: SRVCC to GSM • LTE898: TDD Inter-RAT Handover to TD-SCDMA Impact on interfaces This feature has no impact on interfaces. The related inter-frequency or IRAT measurement events (e.0 - UE NetAct MME SAE GW 3GPP R8 UE capabilities NetAct8 EP1 .g.10. The termination of the inter-frequency and the inter-RAT measurements is extended in such a way that the RSRP triggered A1 measurement report contains also an RSRQ measurement that is compared to an operator-configurable threshold. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4. Table 45 Software requirements System release Flexi Multiradio BTS Flexi Multiradio OMS 10 BTS RL60 LBTS6.4 System impact Interdependencies between features The following mobility features need to be enabled in order to be triggered by this feature. A3. a parallel A2 RSRQ trigger in order to start inter-frequency and IRAT measurements.1.2 Requirements Software requirements Table 45: Software requirements lists software required for this feature. - Hardware requirements This feature requires no new or additional hardware. Impact on network and network element management tools Interface to Netact DN09185955 Issue: 01J © 2016 Nokia 89 . A5 or B2) remain unchanged. 5 LTE1198: RSRQ triggered mobility management data Alarms There are no alarms related to this feature.1.10. Feature Descriptions and Instructions telecom features New parameters are added in the structure rsrqMobility: • threshold2MobRsrq • hysThreshold2MobRsrq • a2TimeToTriggerMobRsrq • a1ReportInterval • threshold2aRsrq Impact on system performance and capacity This feature has a negligible impact in terms of system capacity (MCU processing capacity) of eNB. Key performance indicators There are no key performance indicators related to this feature. Measurements and counters There are no measurements and counters related to this feature. Descriptions of radio resource management and LTE RL60. 4. Parameters The following parameters are new: Table 46 Parameters Full name Abbreviated name Manage Structure d object RSRQ mobility parameters rsrqMobilityParams LNCEL A1 report interval for serving rsrqMobilityParams LNCEL rsrqMobilityParams becomes better than RSRP Time to trigger A2-RSRQ to a2TimeToTriggerMobRsrq LNCEL rsrqMobilityParams start mobility measurement Related hysteresis of threshold hysThreshold2MobRsrq LNCEL rsrqMobilityParams Th2 for RSRQ mobility Threshold Th2 for RSRQ threshold2MobRsrq LNCEL rsrqMobilityParams mobility Threshold Th2a for RSRQ threshold2aRsrq LNCEL rsrqMobilityParams mobility RSRQ redirection parameters rsrqRedirectParams LNCEL Time to trigger for A2 by RSRQ a2TimeToTriggerRedirectRsr LNCEL rsrqRedirectParams to start redirect q 90 © 2016 Nokia DN09185955 Issue: 01J . such that bRsrq) mobility measurements with measurement gaps are activated. The parameters below are part of this structure. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 46 Parameters (Cont.10. Related hysteresis mandatory configuration no of threshold Th2 for RSRQ mobility DN09185955 Issue: 01J © 2016 Nokia 91 . LTE RL60.6 Sales information Table 47 Sales information BSW/ASW License control in network License control attributes element ASW SW Asset Monitoring - 4.2 Activating LTE1198: RSRQ triggered mobility Before you start The eNB has activated the RNW (Radio Network) database and is in service. rsrqMobilityParams ) This is a structure. A1 report interval mandatory configuration no for serving becomes better For the RSRP based A1 event of than serving cell for stopping of Inter-RAT RSRP(a1ReportInter (InterFreq) Measurements the UE val) performs periodical reporting with this indicated interval. measurement Duration for which the event A2- (a2TimeToTriggerMo RSRQ must be valid.) Full name Abbreviated name Manage Structure d object Related hysteresis of threshold hysThreshold4Rsrq LNCEL rsrqRedirectParams Th4 for RSRQ Threshold Th4 for RSRQ threshold4Rsrq LNCEL rsrqRedirectParams 4. Time to trigger mandatory configuration no A2-RSRQ to start mobility Time to trigger for A2-RSRQ.1. Table 48 Parameters used for activating and configuring LTE1198: RSRQ triggered mobility Parameter Purpose Requires eNB restart or object locking RSRQ mobility The feature is activated by no parameters configuring the parameters ( contained in the structure.10. Descriptions of radio resource management and LTE RL60, Feature Descriptions and Instructions telecom features Table 48 Parameters used for activating and configuring LTE1198: RSRQ triggered mobility (Cont.) Parameter Purpose Requires eNB restart or object locking ( Related Hysteresis of Threshold for hysThreshold2MobRs RSRQ of serving cell for mobility rq) measurements activation. Parameter is used within the entry and leave condition of the A2-RSRQ triggered reporting condition. The dB values are mapped to 3GPP IE values according to TS 36.331: IE value = value [dB] * 2. Threshold Th2 for mandatory configuration no RSRQ mobility (threshold2MobRsrq Threshold for RSRQ of serving cell. ) If RSRQ of serving value is less than threshold2MobRsrq, then mobility measurements with measurement gaps are activated. Threshold Th2a for mandatory configuration no RSRQ mobility (threshold2aRsrq) Threshold for RSRQ of serving cell for stopping of Inter-RAT (Inter-Freq) measurements. The RSRP based A1 event reports also the RSRQ value which is compared with this threshold in eNB. It is recommended to configure the feature LTE1407: RSRQ Based Redirect in parallel. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. 2 Activate/Configure the LTE1198:RSRQ Triggered Mobility feature. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. c) Select the LNBTS object. d) Select at least one LNCEL object. e) Create the optional structure RSRQ mobility parameters ( rsrqMobilityParams). 92 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions Descriptions of radio resource management and telecom features f) Set the included parameters of the RSRQ mobility parameters (rsrqMobilityParams) parameter value to appropriate or default values. 1. Set the A1 report interval for serving becomes better than RSRP(a1ReportInterval) to an appropriate or default value. 2. Set the Related hysteresis of threshold Th2 for RSRQ mobility (hysThreshold2MobRsrq) to an appropriate or default value. 3. Set the Threshold Th2 for RSRQ mobility (threshold2MobRsrq) to an appropriate or default value. 4. Set the Threshold Th2a for RSRQ mobility(threshold2aRsrq to an appropriate or default value. 5. Set the Time to trigger A2-RSRQ to start mobility measurement (a2TimeToTriggerMobRsrq) to an appropriate or default value. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. 4.10.3 Deactivating LTE1198: RSRQ triggered mobility Before you start The eNB has activated the RNW database and is in service, and the optional LNCEL structure parameter rsrqMobilityParams is configured, that is the feature is activated in at least one cell The RSRQ mobility parameters (rsrqMobilityParams) structure is used for deactivation. Modification of this structure does require neither eNB restart, nor cell locking. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure, perform the steps described in this procedure. 2 Deactivate the LTE1198: RSRQ triggered mobility feature. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. c) Select the LNBTS object. d) Select at least one LNCEL object. e) Delete the optional structure RSRQ mobility parameters ( rsrqMobilityParams ). DN09185955 Issue: 01J © 2016 Nokia 93 Descriptions of radio resource management and LTE RL60, Feature Descriptions and Instructions telecom features 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Expected outcome The feature LTE1198:RSRQ Triggered Mobility is deactivated. 4.11 LTE1231: Operator-specific GBR QCIs 4.11.1 Description of LTE1231: Operator-specific GBR QCIs Introduction to the feature The LTE1231: Operator specific GBR QCIs feature defines its own quality of service (QoS) profiles for guaranteed bit rate (GBR) evolved packet system (EPS) bearers. 4.11.1.1 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits The operator-specific QCIs allows better user and service differentiation of the GBR services. 4.11.1.2 Requirements Software requirements Table 49: Software requirements lists the software required for this feature. Table 49 Software requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 LBTS6.0 LBTS6.0 - UE NetAct MME SAE GW 3GPP R8 mandatory NetAct8 EP1 - - Hardware requirements This feature requires no new or additional hardware. 4.11.1.3 Functional description Up to 21 operator-specific QCIs for GBR EPS bearers are supported per eNB. The operator-specific QCIs allow for better user and service differentiation of GBR services. The QCI value for each QCI is operator configurable in the range from 128 to 254. 94 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions Descriptions of radio resource management and telecom features The PM counter groups for non-GBR QCIs are applied as well to operator-specific GBR QCIs. Operator-specific GBR bearers are treated by admission control as standard GBR bearers. Robust header compression is not applied for operator-specific GBR QCIs. The total maximum number of operator-specific QCIs (GBR and non GBR) is 21. 4.11.1.4 System impact Interdependencies between features The following features need to be enabled: • LTE496: Support of QCI 2, 3 and 4 • LTE497: Smart admission control • LTE534: ARP based admission control for E-RABs The LTE587: Multiple GBR EPS Bearers per UE feature needs to be activated if the operator wants to use more than one GBR bearer at the same time. The LTE518: Operator specific QCI feature covers the operator-specific non-GBR QCIs and can be enabled separately or at the same time as LTE1231: Operator specific GBR QCIs feature. The differentiation between non-GBR and GBR is done by the Resource type (resType) parameter. One QCI value might be configured either for non-GBR or for GBR. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity. 4.11.1.5 LTE1231: Operator-specific GBR QCIs management data Alarms There are no alarms related to this feature. Measurements and counters Counters defined for LTE518: Operator-specific QCI are applicable also for LTE1231: Operator-specific GBR QCIs. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 50: New parameters lists parameters introduced with this feature. DN09185955 Issue: 01J © 2016 Nokia 95 Descriptions of radio resource management and LTE RL60, Feature Descriptions and Instructions telecom features Table 50 New parameters Full name Abbreviated name Managed object Structure Activate support of actOperatorQCIGBR LNBTS operator specific GBR QCIs Delay target delayTarget LNBTS qciTabOperator L2 overhead factor l2OHFactorDl LNBTS qciTabOperator GBR Dl L2 overhead factor l2OHFactorUl LNBTS qciTabOperator GBR Ul Maximum GBR maxGbrDl LNBTS qciTabOperator downlink Maximum GBR uplink maxGbrUl LNBTS qciTabOperator Priority prio LNBTS qciTabOperator Table 51: Related existing parameters lists existing parameters related to this feature. Table 51 Related existing parameters Full name Abbreviated name Managed object Structure Activate enhanced AC actEnhAcAndGbrServi LNBTS and GBR services ces QCI translation table qciTabOperator LNBTS operator specific QCIs Counter group counterGroup LNBTS qciTabOperator DRX profile index drxProfileIndex LNBTS qciTabOperator DSCP dscp LNBTS qciTabOperator Enforce TTI bundling enforceTtiBundling LNBTS qciTabOperator Logical channel group lcgid LNBTS qciTabOperator identifier PDCP profile index pdcpProfIdx 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 Scheduling bucket schedulBSD LNBTS qciTabOperator size duration Scheduling priority schedulPrio LNBTS qciTabOperator Scheduling weight schedulWeight LNBTS qciTabOperator 96 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4.11.1.6 Sales information Table 52 Sales information BSW/ASW License control in License control Activated by default network element attributes ASW SW Asset Monitoring - No 4.11.2 Activating and configuring LTE1231: Operator-specific GBR QCIs Before you start Table 53 Parameters used for activating and configuring LTE1231: Operator specific GBR QCIs Parameter Purpose Requires eNB restart or object locking Activate support activation flag no of operator specific GBR QCIs (actOperatorQCIGB R) QCI translation mandatory configuration no table operator specific QCIs (qciTabOperator) parameter structure The following features need to be activated/configured before activation of LTE1231: Operator specific GBR QCIs: • LTE534: ARP-based Admission Control for E-RABs • LTE496: Support of QCI 2, 3 and 4 • LTE497: Smart Admission Control If the operator wants to use more then one GBR bearer at the same time, the LTE587: Multiple GBR EPS bearers per UE feature has to be activated. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. 2 Activate the LTE1231: Operator specific GBR QCIs. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. DN09185955 Issue: 01J © 2016 Nokia 97 g Note: If the QCI translation table operator specific QCIs (qciTabOperator) parameter structure is not configured or parameter Resource type (resType) is not equal to GBR value for all entries in qciTabOperator. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. the feature LTE1231: Operator specific GBR QCIs is not activated. 4 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Modification of this parameter does not require neither the eNB restart. nor cell locking. d) Select and right-click on the QCI translation table operator specific QCIs (qciTabOperator) parameter structure and select New QCI translation table operator specific QCI-x. Expected outcome The feature LTE1231: Operator specific GBR QCIs has been activated and operator can define its own QoS profiles for GBR EPS bearers. Feature Descriptions and Instructions telecom features c) Select the LNBTS object.3 Deactivating LTE1231: Operator-specific GBR QCIs Before you start The Activate support of operator specific GBR QCIs (actOperatorQCIGBR) parameter is used for deactivation. b) Expand the MRBTS object. 98 © 2016 Nokia DN09185955 Issue: 01J . e) Set the parameters in the created parameter structure. d) Set the Activate support of operator specific GBR QCIs (actOperatorQCIGBR) parameter value to true. a) Go to the Radio Network Configuration page. 4.11. 3 Configure the LTE1231: Operator specific GBR QCIs. Descriptions of radio resource management and LTE RL60. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. g Note: If QCI translation table operator specific QCIs (qciTabOperator) parameter structure does not exist right-click on LNBTS object and add New QCI translation table operator specific QCIs parameter structure. c) Expand the LNBTS object. The Resource type (resType) parameter value must be set to GBR. The maximum aggregated DL bandwidth is 40 MHz.12.40 MHz Introduction to the feature The LTE1332: Downlink Carrier Aggregation - 40 MHz feature supports carrier aggregation (CA) in downlink (DL) for two component carriers of up to 20 MHz cell bandwidth each and two non-aggregated uplink cells as an extension to LTE1089: Downlink Carrier Aggregation - 20 MHz feature.2 Requirements Software requirements Table 54: Software requirements lists the software required for this feature. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. 4. A mix of non-CA and CA UEs is supported in DL. Operator benefits This feature supports 40 MHz DL Carrier Aggregation. Expected outcome The LTE1231: Operator specific GBR QCIs feature has been deactivated. DN09185955 Issue: 01J © 2016 Nokia 99 . It also enables fast load balancing for CA UEs and consolidates fragmented spectrum. b) Expand the MRBTS object. a) Go to the Radio Network Configuration page. 4.1. c) Select the LNBTS object. d) Set the Activate support of operator specific GBR QCIs (actOperatorQCIGBR) parameter value to false. LTE RL60.1. 4.12 LTE1332: Downlink Carrier Aggregation .11 Variable Definitions 4.1 Benefits End-user benefits This feature offers the end-user an improved peak and average UE downlink throughput.40 MHz 4. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 2 Deactivate the LTE1231: Operator specific GBR QCIs.12.1 Description of LTE1332: Downlink Carrier Aggregation .12. A/N spatial bundling on scheduling request 100 © 2016 Nokia DN09185955 Issue: 01J . The CA UEs can transmit on only one UL cell (PCell). and 10 MHz + 10 MHz with 2RX antennas. Note that each of the cells can serve non-CA UEs in parallel to CA UEs. Note that this only works if neither of the two cells is fully loaded. The physical downlink shared channel (PDSCH) on the primary cell (PCell) and secondary cell (SCell) can be transmitted to the CA UE in a single TTI that is up to 4 transport blocks (TBs) (2 TBs per cell). the distance between the center frequencies of cells that can be aggregated is used to distinguish if the aggregation is contiguous or non-contiguous. please see Flexi Multiradio and Multiradio 10 BTS LTE Supported Configurations. 4. are supported on FSMF only. • The transient period with the ambiguity on the ACK/NACK codebook size on physical uplink shared channel (PUSCH). two extension cards are needed for DL CA (FSMF + FBBA + FBBC or FSMF + FBBC + FBBC).300 in the same way as the LTE1089: Downlink Carrier Aggregation - 20 MHz feature.1. Support of DL CA – 40 MHz The support of DL CA - 40 MHz is described as follows: • It supports setting and signaling of deltaF-PUCCH-Format1bCS-r10 and deltaF- PUCCH-Format3-r10 in system information. Otherwise. FSMF + 1xFBBA or FSMF + 1xFBBC are needed. One cell should have a maximum bandwidth of 10 MHz. and 4TX4RX + 4TX4RX. However. 2TX4RX + 4TX4RX. the system capacity gains may be observed depending on the network deployment type and/or the UE traffic profile. LBTS6.12. including the ones introduced in RL60. In case of intra-band DL CA. This feature supports the scenario 1 and scenario 2 from 3GPP TS 36. The feature does not increase the overall capacity of the system. The feature is for FDD only. 5 MHz + 10 MHz. All other bandwidth combinations. Descriptions of radio resource management and LTE RL60. Two cells are aggregated in the DL so that CA UEs can achieve higher peak data rates. no extension cards are needed. - Hardware requirements The following are the limitations regarding FSME/FMSF: • 5 MHz + 5 MHz and 10 MHz + 10 MHz are supported on both FSME and FSMF.3 Functional description The LTE1332: Downlink Carrier Aggregation - 40 MHz feature supports (intra-eNB) intra- band contiguous/non-contiguous and (intra-eNB) inter-band DL CA. Feature Descriptions and Instructions telecom features Table 54 Software requirements System release Flexi Multiradio BTS Flexi Multiradio OMS 10 BTS RL60 . For more information. • Special requirements are valid for the following antenna configurations: 2TX4RX + 2TX4RX. in some scenarios.0 - UE NetAct MME SAE GW 3GPP R10 UE capabilities NetAct8 EP1 . Note that once actFlexBbUsage is set to true for 5 MHz + 5 MHz. • If the DL channel BW is greater than 10 MHz for one of the CA cells with 4RX antennas. LTE RL60. Instead. • Alignment of DRX start offset with PCell's periodic channel state information (CSI). then the measurement gaps are set up by the eNB. contiguous) – band 3 + band 5 – band 3 + band 7 – band 3 + band 8 – band 3 + band 20 – band 3 + band 28 – band 4 + band 4 (non-contiguous. If either the Release 8/9 or Release 10 need for gaps information (or even both) indicates that the measurement gaps are needed for the related inter-frequency or inter-RAT measurements. Feature deployment The deployment for the feature is as follows: • The aggregated cells are co-located. • The measurement gap configuration for the UEs with an added SCell is based on checking the MeasParameters-v1020. • The aggregated cells are contiguous in the same band or non-contiguous in the same band or in different bands (inter-band DL CA is already in LTE1089: Downlink Carrier Aggregation - 20 MHz feature). A UE is camped in the SCell when a MAC CE activates the SCell. • Handling of delayed SCell activation. • The TX diversity fallback is not used and the multiple inputs multiple outputs (MIMO) is always used for the UEs with an active SCell. which is sent in the subframe n and acknowledged on the layer 1 by the UE. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features indicator (SRI). The prevention from entering the TX diversity is applied only for the closed-loop MIMO. • SCell outage/lock/shutdown causes an SCell release (it causes a UE Context Release including an RRC Connection Release in LTE1089: Downlink Carrier Aggregation - 20 MHz feature). The UE is not a candidate for dynamic packet scheduling in the SCell until periodic/aperiodic CQI other than 0/OOR is received for the SCell or until subframe n + 33 (subframe n + 33 inclusive). The precoding matrix indicator (PMI) values might be not up-to-date due to CA-specific dropping of periodic CSI or due to infrequent aperiodic CSI in certain traffic conditions. and the downlink control information (DCI) 0/1A size between the UE and eNB during SCell addition and SCell release is mitigated. only the wideband periodic CSI is recommended to be configured. • The allowed band combinations are the following (with bandwidth combination set to 0 if not mentioned): – band 1 + band 5 – band 1 + band 7 – band 1 + band 8 – band 1 + band 18 – band 2 + band 4 – band 2 + band 5 – band 2 + band 17 – band 3 + band 3 (non-contiguous. contiguous) – band 4 + band 7 – band 4 + band 12 DN09185955 Issue: 01J © 2016 Nokia 101 . g Note: The sub-band periodic CSI is not recommended to be configured when the DL CA is enabled. 1TX + 2TX (but not part of the officially supported and tested configurations). • The following cell bandwidth combinations are supported (as well for cell bandwidth combinations introduced in LTE1089: Downlink Carrier Aggregation - 20 MHz feature): – 5 MHz + 5 MHz – 5 MHz + 10 MHz – 10 MHz + 10 MHz – 5 MHz + 15 MHz – 5 MHz + 20 MHz – 10 MHz + 15 MHz – 10 MHz + 20 MHz – 15 MHz + 15 MHz – 15 MHz + 20 MHz – 20 MHz + 20 MHz g Note: Only 3GPP defined cell band and cell bandwidth combinations are tested and released. • The antennas of the aggregated cells shall be pointed to the same geographical area (ignoring possible down tilt. 3. Descriptions of radio resource management and LTE RL60. 2. However. This modification provides more predictable behavior and better fairness across the CA and non-CA UEs within each cell. • Two cells are aggregated in the DL (aggregation of more than two cells is not supported. contiguous) – band 7 + band 20 g Note: The bandwidth configuration set must be checked at the SCell configuration for band combination 4 + 12. • The TX configurations of the aggregated cells are: – 1TX + 1TX – 1TX + 2TX – 1TX + 4TX – 2TX + 2TX – 2TX + 4TX – 4TX + 4TX g Note: The TX configurations 1TX + 1TX. 102 © 2016 Nokia DN09185955 Issue: 01J . Feature Descriptions and Instructions telecom features – band 4 + band 17 – band 5 + band 7 – band 7 + band 7 (non-contiguous. UL CA is not supported). The dynamic throughput and caSchedFairFact-based division of per UE weights onto serving cells are replaced with static division of per UE weight onto the serving cells based only on caSchedFairFact parameter. The modification might reduce the load balancing benefit of the DL CA. the modification might provide some suboptimal or inexact fairness across the CA and non-CA UEs in case the radio/load conditions on the serving cells are unbalanced. and 4 for band combination 4 + 12 must be supported. if any). and 2TX + 2TX are already specified in LTE1089: Downlink Carrier Aggregation - 20 MHz feature. The throughput differentiation between the CA and non-CA UEs is still provided according to the configuration of the caSchedFairFact parameter. The bandwidth configuration sets 1. the only allowed bandwidth is 10 MHz and both aggregated cells must have the same activation status of the supercell function. LTE568: DL Adaptive Closed Loop MIMO (4x2).1.12. In case of an FSP failure. CA-related modifications are introduced only together with the scheduling metric calculation specified in LTE496: Support of QCI 2. and avoiding of spatial ACK/NACK bundling on SRI resources. This restriction is used to avoid CA-related modifications of multiple types of scheduling metric calculation. however.3 and 4. it is not clear when the UE will apply the configuration.3 and 4 feature is enabled. During the transient period. Improved handling of an SCell lock/shutdown is introduced so that it causes an SCell release. The LTE72: 4-way RX Diversity. An SCell lock/shutdown causes an RRC connection release in LTE1089: Downlink Carrier Aggregation - 20 MHz feature. This feature mitigates any one the following: • the uncertainty on the ACK/NACK codebook size on PUSCH • the A/N spatial bundling on SRI • the DCI 0/1A size between the UE and eNB The specific mitigation methods during the transient period include scheduling only the PCell in the DL (no SCell scheduling). The LTE1089: Downlink Carrier Aggregation - 20 MHz and LTE1332: Downlink Carrier Aggregation - 40 MHz features can only be enabled if the LTE496: Support of QCI 2.4 System impact Interdependencies between features The LTE1332: Downlink Carrier Aggregation - 40 MHz feature is enabled together with the LTE1089: Downlink Carrier Aggregation - 20 MHz feature. 4. The UE is still configured with cqi- ReportConfig-r10 after an SCell release by dedicated RRC signaling. LTE RL60. and LTE980: IRC for 4 RX Paths features work together with LTE1332: Downlink Carrier Aggregation - 40 MHz. ACK/NACK spatial bundling with positive scheduling request is avoided by scheduling one TB per TTI to the UE in the DL on the PCell. Since the UE changes the L1 configuration during the SCell addition and release. DN09185955 Issue: 01J © 2016 Nokia 103 . An automatic BTS restart is performed if the alarm is raised to all configured cells in the eNB. not scheduling UL and DL in the same TTI. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features • The DL SFN/subframe and radio frame timing of the aggregated cells are synchronized at the eNB. however. the affected cells may be disabled and the automatic cell recovery not possible alarm is raised. The LTE1382: Cell Resource Groups feature has a function of virtually splitting cell resources up to four operators. This also means that ARP handling is enabled with LTE1089: Downlink Carrier Aggregation - 20 MHz and LTE1332: Downlink Carrier Aggregation - 40 MHz features. additional limitations might be in place regarding capacity of the eNB. The LTE1542: FDD Supercell feature can be enabled together with CA. This feature can run in parallel with LTE1332: Downlink Carrier Aggregation - 40 MHz feature. 40 MHz management data For information on alarm. Table 55 Related existing counters Counter ID Counter name Measurement M8001C494 Average number of DL carrier LTE Cell Load aggregated capable UEs M8001C495 Average number of UEs with a LTE Cell Load configured Scell M8001C496 Average number of UEs with LTE Cell Load an activated Scell M8011C67 Number of SCell configuration LTE Cell Resource attempts M8011C68 Number of successful SCell LTE Cell Resource configurations M8012C151 PCell RLC data volume in DL LTE Cell Throughput via SCell 104 © 2016 Nokia DN09185955 Issue: 01J . Feature Descriptions and Instructions telecom features The LTE1367: Automatic Cell Combination Assignment for Carrier Aggregation feature automatically pairs the cells to be used together for the CA features. counter. and updates the BTS configuration. Alarms There are no alarms related to this feature. level of GBR traffic. Impact on interfaces This feature affects the interfaces as follows: • Uu – new parameter in system information – SCell release because of SCell lock/shutdown Impact on network and network element management tools This feature has no impact on network management or network element management tools. see Reference documentation. These throughput figures can be at maximum doubled (for bandwidth combinations with equal bandwidth of two involved cells). Descriptions of radio resource management and LTE RL60.1. The actual gain depends on many factors like CA deployment type (level of overlapping of two involved layers). and parameter documents. 4.5 LTE1332: Downlink Carrier Aggregation . Impact on system performance and capacity An improved peak and mean user DL throughput (for non-GBR) for the UEs with the secondary cell configured is the main goal of this feature.12. and parameterization of scheduling fairness factor. proper PCell/SCell pairing have to be assured manually on a cell-to-cell basis. Without this feature. Measurements and counters lists existing counters for this feature. key performance indicator. network load. Table 58 Related existing parameters Full name Abbreviated name Managed object Local cell resource ID of cell to lcrId CAREL be aggregated Activation of downlink carrier actDLCAggr LNBTS aggregation EARFCN downlink earfcnDL LNCEL Carrier aggregation pool ID caPoolId LNCEL Sched Carrier Aggr fairness caSchedFairFact LNBTS control factor SCell activation cycle period sCellActivationCyclePeriod LNBTS Max number Carrier Aggr maxNumCaConfUeDc LNCEL configured UEs double carrier Min UE-AMBR downlink for caMinDlAmbr LNBTS carrier aggregation SCell activation method sCellActivationMethod LNBTS DN09185955 Issue: 01J © 2016 Nokia 105 . Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Key performance indicators lists the existing key performance indicators related to this feature. Table 56 Related existing key performance indicators KPI ID KPI name LTE_5318a E-UTRAN Average CA Capable UEs in DL LTE_5319a E-UTRAN Average UEs with a Configured SCell in DL LTE_5320a E-UTRAN Average UEs with an Activated SCell in DL LTE_5321a E-UTRAN Penetration of the CA Capable UEs into the Network LTE_5323a E-UTRAN SCell Configuration Success Ratio LTE_5323a E-UTRAN RLC PDU Volume DL via Scell Parameters Table 57: New parameters lists parameters introduced with this feature. LTE RL60. Table 57 New parameters Full name Abbreviated name Managed object Structure Uplink power control uplinkPCCommonr10 LNCEL common rel10 add- ons UL power offset for deltaFPucchF1bCSr10 LNCEL uplinkPCCommonr10 PUCCH format 1bCS UL power offset for deltaFPucchF3r10 LNCEL uplinkPCCommonr10 PUCCH format 3 Table 58: Related existing parameters lists existing parameters related to this feature. In operating the CA features.40 MHz Before you start The LTE1332: Downlink Carrier Aggregation - 40 MHz feature is enabled together with the LTE1089: Downlink Carrier Aggregation - 20 MHz feature (both features have the same activation flag). Descriptions of radio resource management and LTE RL60.1.) Full name Abbreviated name Managed object Disable PDCCH outer loop link disableSCellPDCCHOlLa CADPR/CAPR adaptation in SCell SCell and PCell ambiguous sCellpCellHARQFdbkUsage LNBTS HARQ feedback usage SCell deactivation timer eNB sCellDeactivationTimereNB LNBTS Carrier aggregation relation caRelId CAREL identifier 4. Feature Descriptions and Instructions telecom features Table 58 Related existing parameters (Cont.12. This is described in the Commissioning Flexi Multiradio BTS LTE document. it might be necessary to set the link speed parameter.2 Activating and configuring LTE1332: Downlink Carrier Aggregation . Table 60 Parameters used for activating and configuring the LTE1332: Downlink Carrier Aggregation - 40 MHz Parameter Purpose Requires eNB restart or object locking Activation of downlink carrier activation flag eNB restart aggregation (actDLCAggr) UL power offset for PUCCH format optional configuration no 1bCS (deltaFPucchF1bCSr10) UL power offset for PUCCH format 3 optional configuration no (deltaFPucchF3r10) Local cell resource ID of cell to be mandatory configuration object locking aggregated (lcrId) Sched Carrier Aggr fairness control mandatory configuration object locking factor (caSchedFairFact) Min UE-AMBR downlink for carrier optional configuration no aggregation (caMinDlAmbr) 106 © 2016 Nokia DN09185955 Issue: 01J . Note that the default value (Auto) of this parameter is normally the optimal selection.6 Sales information Table 59 Sales information BSW/ASW License control in network Activated by default element ASW SW Asset Monitoring No 4.12. A maximum of two cells can have the same CA pool ID.9 MHz for 5 + 10 MHz and 10 + 5 MHz • 4.8 MHz for 5 + 5 MHz Nominal channel spacing for carrier aggregation are provided in 3GPP specification 36. Minimum carrier spacing requirements between the aggregated carriers are: • 18. DN09185955 Issue: 01J © 2016 Nokia 107 .3 MHz for 20 + 20 MHz • 15. Not all MIMO modes can be mixed. g Note: In order for the channel spacing to be configured properly. 5 + 15 MHz and 15 + 5 MHz • 6. For intra-band contiguous DL CA. nominal channel spacing and channel spacing lower than the nominal channel spacing are allowed (proper configuration by the operator is required since there are no consistency checks) (available on the LTE Carriers page).) Parameter Purpose Requires eNB restart or object locking SCell activation cycle period optional configuration no (sCellActivationCyclePerio d) SCell activation method optional configuration no (sCellActivationMethod) SCell and PCell ambiguous HARQ optional configuration no feedback usage (sCellpCellHARQFdbkUsage) SCell deactivation timer eNB optional configuration no (sCellDeactivationTimereNB ) EARFCN downlink (earfcnDL) optional configuration object locking Max number Carrier Aggr configured optional configuration no UEs double carrier (maxNumCaConfUeDc) All LCELLs in the eNB must have the Carrier aggregation pool ID (caPoolId) parameter configured when the LTE1332: Downlink Carrier Aggregation - 40 MHz feature is enabled.45 x (BW_Channel(1) + BW_Channel(2)) < Channel spacing for intra-band contiguous DL CA <= Nominal channel spacing. The CA cells with subordinated CAREL or CA cells linked by CAREL-lcrId of another LNCEL must have the same CA pool ID.4 MHz for 10 + 15 MHz. this must be fulfilled: 0. Channel spacing for intra-band contiguous CA can be adjusted to any multiple of 300 kHz less than the nominal channel spacing. Each non-CA cell must have a unique CA pool ID. 15 + 10 MHz. This equation is valid only for contiguous intra-band CA. 10 + 20 MHz and 20 + 10 MHz • 11.9 MHz for 15 + 20 MHz and 20 + 15 MHz • 13. Only the combinations that have the same maximum number of TB per TTI are allowed in the same CA pool ID. 5 + 20 MHz and 20 + 5 MHz • 9.3 MHz for 10 + 10 MHz.8 MHz for 15 + 15 MHz.101. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 60 Parameters used for activating and configuring the LTE1332: Downlink Carrier Aggregation - 40 MHz (Cont. LTE RL60. then maxNumRrcEmergency <= min(nCqiRb * 6 * cqiPerNp/2. and LTE1542: FDD Supercell features is possible if the following conditions are fulfilled: • Baseband HW platform is Flexi MR 10 BTS. addAUeTcHo) <= min(nCqiRb * 6 * cqiPerNp. • In P-LNCEL. • In P-LNCEL. 6 * cellSrPeriod). then maxNumRrc + max(addAUeRrHo. periodicCqiFeedbackType. if the parameter actEmerCallRedir is set to true or actIMSEmerSessR9 is set to true and riEnable is set to true and n1PucchAn <> 10. then maxNumRrc + max(addAUeRrHo. (n1PucchAn – 36) * cellSrPeriod). • In P-LNCEL. if (actEmerCallRedir is set to true or actIMSEmerSessR9 is set to X) and riEnable is set to true and n1PucchAn = 10. then the parameter cqiPerNp must be <= 40 ms. • If the parameter riEnable is set to false in P-LNCEL. • The parameter deltaPucchShift in P-LNCEL must be <= 2. • In P-LNCEL. • Both supercells have overlapping coverage. then maxNumRrcEmergency <= min(nCqiRb * 6 * cqiPerNp/2. The parallel use of LTE1332: Downlink Carrier Aggregation - 40 MHz/LTE1089: Downlink Carrier Aggregation - 20 MHz. then maxNumRrc + max(addAUeRrHo. addAUeTcHo) <= min(nCqiRb * 6 * cqiPerNp. (n1PucchAn – 48) * cellSrPeriod). g Note: CA specific dependencies for the parameters defining the PUCCH configuration were introduced to handle the multi-cell ACK/NACK in the PCell (no CA in uplink direction means that all signaling traffic related to both primary and secondary cell is routed via PCell only). • Both aggregated supercells have 10 MHz bandwidth. • In P-LNCEL. addAUeTcHo) <= min(nCqiRb * 6 * cqiPerNp/2. and cqiPerSbCycK must be configured similarly in P-LNCEL and S-LNCEL. 108 © 2016 Nokia DN09185955 Issue: 01J . • The LTE1542: FDD Supercell feature is enabled on both aggregated supercells. 2 * cellSrPeriod). Feature Descriptions and Instructions telecom features The following requirements must be fulfilled for the primary (P-LNCEL) and the secondary (S-LNCEL): • If parameter riEnable is configured to true for P-LNCEL and S-LNCEL. • In P-LNCEL. (n1PucchAn – 36) * cellSrPeriod). Descriptions of radio resource management and LTE RL60. • In P-LNCEL. if (actEmerCallRedir is set to true or actIMSEmerSessR9 is set to true) and riEnable is set to false and n1PucchAn = 10. if the parameter riEnable is set to true and the parameter n1PucchAn = 10. then maxNumRrcEmergency <= min(nCqiRb * 6 * cqiPerNp. if the parameter riEnable) is set to false and the parameter n1PucchAn <> 10. • The parameter (cqiPerNp) in P-LNCEL must be >= 5 ms. • The parameter n1PucchAn in P-LNCEL must be 10 or >= 72. • In P-LNCEL. • The parameters riEnable. addAUeTcHo) <= min(nCqiRb * 6 * cqiPerNp/2. if the parameter riEnable is set to true and the parameter n1PucchAn is <> 10. then maxNumRrc + max(addAUeRrHo. if the parameter riEnable is set to false and the parameter n1PucchAn = 10. if (actEmerCallRedir is set to true or actIMSEmerSessR9 is set to true) and riEnable is set to false and n1PucchAn <> 10. 6 * cellSrPeriod). then parameter riPerM must be set to 1. Note that setting the value to 10 is for demo use only and it is not suitable for field deployment. then maxNumRrcEmergency <= min(nCqiRb * 6 * cqiPerNp. (n1PucchAn – 48) * cellSrPeriod). 2 * cellSrPeriod). This causes cell service break. a) Go to the Radio Network Configuration page. a) Go to the Radio Network Configuration page. d) Set the Activation of downlink carrier aggregation (actDLCAggr) parameter value to true. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. g Note: Modification of the Local cell resource ID of cell to be aggregated (lcrId) parameter requires object locking. 4 Define the power offset (optional). 2 Set the activation flag. a) Expand the LNBTS object. d) Select the CAREL object. d) Right-click LNCEL object. c) Select New object. 3 Create new CAREL. LTE RL60. b) Expand the MRBTS object. and add new Uplink power control common rel10 add-ons (uplinkPCCommonr10) parameter structure. c) Select the LNBTS object. c) Expand the LNBTS object. b) Expand the MRBTS object. e) Configure the following child parameters: • UL power offset for PUCCH format 1bCS (deltaFPucchF1bCSr10) • UL power offset for PUCCH format 3 (deltaFPucchF3r10) DN09185955 Issue: 01J © 2016 Nokia 109 . e) Define the value for the following parameters: • Local cell resource ID of cell to be aggregated (lcrId) • Sched Carrier Aggr fairness control factor (caSchedFairFact) g Note: CAREL object deletion and addition cause short service break on cell level because of a required object (cell) lock. b) Select the LNCEL object. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. perform the steps described in this procedure. b) Expand the MRBTS object. Descriptions of radio resource management and LTE RL60. b) Expand the MRBTS object. a) Go to the Radio Network Configuration page. e) Set the value for the following parameters: • EARFCN downlink (earfcnDL) • Max number Carrier Aggr configured UEs double carrier (maxNumCaConfUeDc) 7 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. c) Select the LNBTS object. a) Go to the Radio Network Configuration page. Feature Descriptions and Instructions telecom features 5 Configure the following parameters for LNBTS (optional). c) Expand the LNBTS object. d) Set the value for the following parameters: • SCell activation cycle period (sCellActivationCyclePeriod) • Min UE-AMBR downlink for carrier aggregation (caMinDlAmbr) • SCell activation method (sCellActivationMethod) • SCell and PCell ambiguous HARQ feedback usage (sCellpCellHARQFdbkUsage) • SCell deactivation timer eNB (sCellDeactivationTimereNB) g Note: The SCell deactivation timer eNB (sCellDeactivationTimereNB) parameter value is not recommended to be set to infinity. 6 Configure the following parameters for LNCEL (optional). 110 © 2016 Nokia DN09185955 Issue: 01J . Result Expected outcome The LTE1332: Downlink Carrier Aggregation - 40 MHz feature is enabled in the eNB. d) Select the LNCEL object. 1 Description of LTE1336: Interference aware UL power control Introduction to the feature The LTE1336: Interference aware UL power control feature improves the uplink (UL) cell capacity and the cell-edge performance. 2 Set the activation flag.40 MHz Before you start The Activation of downlink carrier aggregation (actDLCAggr) parameter is used for deactivation. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. The interference-aware uplink power control is used for the power control on the physical uplink shared channel (PUSCH). as well as the carrier aggregation.12. Expected outcome The LTE1332: Downlink Carrier Aggregation - 40 MHz and LTE1089: Downlink carrier aggregation - 20 MHz feature is deactivated in the eNB. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager.13. DN09185955 Issue: 01J © 2016 Nokia 111 . c) Select the LNBTS object. b) Expand the MRBTS object. 4. d) Set the Activation of downlink carrier aggregation (actDLCAggr) parameter value to false. Modification of this parameter requires eNB restart. LTE RL60. The eNB controls the UE-specific transmit power to optimize the trade-off between the throughput achieved in its own cell and the UL interference in the neighboring cells. a) Go to the Radio Network Configuration page.13 LTE1336: Interference aware UL power control 4.3 Deactivating LTE1332: Downlink Carrier Aggregation . In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4. The eNB uses its own measurements and the UE's measurements as input for the algorithm. 2 Requirements Software requirements Table 61: Software requirements lists the software required for this feature. 4.13.1. 112 © 2016 Nokia DN09185955 Issue: 01J . When activated in all eNBs of an area. The main function of this feature’s mechanism is to make the UE UL power achieve the optimum system-wide throughput. The power control loop converts deviations of the measured SINRs from the target SINR into power-up and power-down commands that are sent to the UE. achieving a higher throughput in a whole range of cells is possible by reducing the uplink interference level in a complete area. which is pronounced in cell centers and less visible in cell borders. but it reduces the interference in the neighboring cells. - Hardware requirements This feature requires no new or additional hardware. UEs closer to the cell border cause high interference to the neighboring cells. Some downlink (DL) traffic is needed for the UEs to reliably report the channel quality indicator (CQI). 4.13. Operator benefits This feature provides higher uplink cell capacity and improved cell-edge throughput that offers additional services and better service coverage. This mechanism produces and updates the target signal-to-interference- plus-noise ratio (SINR) value for each UE based on the eNB measurements and UE- reported data. With this feature. The UL PUSCH transmissions from the UE are received as wanted signal from the cell. Especially. Descriptions of radio resource management and LTE RL60. Feature Descriptions and Instructions telecom features 4. Decreasing the transmit power of UEs close to the cell border decreases on first view the achieved throughput in the serving cell.0 - UE NetAct MME SAE GW 3GPP R8 mandatory NetAct8 EP1 . the operation of the feature shows an increase in the overall UL throughput.0 LBTS6. This feature must be activated in all cells of an area to attain its full benefits. This results in the decrease in SINR and degraded UL throughput.3 Functional description The LTE1336: Interference aware UL power control feature provides improved throughput over the existing closed-loop and open-loop UL power controls. the reduced UL power in the cell is not accompanied by a reduced interference from the adjacent cells.13. If this feature is activated on a single eNB. Table 61 Software requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 LBTS6.1 Benefits End-user benefits This feature increases the uplink throughput of end users.1.1. but are received as interference from the neighboring cells. but with an even distribution of the UEs. • Networks with repeaters that operate with different gains between uplink and downlink directions. The DL SINR is a measure of the ratio of the path loss from the UE towards another eNB and the path loss towards its own eNB. which the eNB derives from DL SINR. and ulpcSrsEn parameters from the previous releases. Figure 4 Interference-aware UL power control diagram owncell ownUE othercells Pown. and the sounding reference signal (SRS). the UEs reach their power limits. and offers to select one of the valid modes of UL power control. The UL SINR is one input to the control loop and it is compared to a variable threshold. Unexpected results are acquired if the DL gain differs from the UL gain. In noise-limited scenarios. This feature is not suitable for the following: • Scenarios with neighboring cells whose DL powers differ by more than ~12 dB. over interference and noise level at the eNB’s receiver(s). The parameter actUlpcMethod is used for feature activation and offers various combinations between the open-loop. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features The UE transmit power can be reduced at the same time the interference level is reduced. The DL SINR is reflected in the UE’s CQI reports which are received at eNB and used to derive the path loss ratio that enters into the SINR_Target equation. ulpcPuschEn. • DL SINR is the UE’s SINR at the UE. LTE RL60. closed-loop. SINR_Target. • SINR_Target is the UE-specific target value for the UL SINR. UL Signal RSSI UL SINR UL interference This feature deals with various SINR values: • UL SINR is the UE-specific SINR of the UE’s UL transmission. the eNB calculates and transmits power-up/down commands to its UEs to keep the UL SINR as close as possible to the calculated SINR_Target.PL DL SINR Pother . received at the eNB. The SINR_Target depends on the ratio PL’/PL of path losses at the UE’s location. Repeaters with asymmetric gains distort the eNB's calculation of path loss ratio. physical uplink control channel (PUCCH).PL' SINR Target DL CQI UL interference + power command . With the LTE1336: Interference aware UL power control feature activated. ulpcPucchEn. The following parameters are also introduced in this feature: DN09185955 Issue: 01J © 2016 Nokia 113 . and interference-aware power control for the PUSCH. Reducing the transmit power directly affects the UL throughput. The LTE1336: Interference aware UL power control feature introduces the actUlpcMethod parameter that replaces ulpcEnable. 1. • The Maximum RSSI for interference-aware UL-PC (ulpcRssiMaxIAw) parameter sets the upper limit for the received signal strength indicator (RSSI). The ulpcCEBalanceIAw. ulpcMinQualIAw. • Interference rejection combining (IRC) (LTE979: IRC for 2 RX paths and LTE980: IRC for 4 RX paths) The IRC can significantly reduce the influence of one single source of interference against an individual wanted transmission. 114 © 2016 Nokia DN09185955 Issue: 01J . Regardless of the path loss ratio. Descriptions of radio resource management and LTE RL60. This benefit also applies to all kinds of UL-PC. Feature Descriptions and Instructions telecom features • The Cell-center/edge balancing for interference-aware UL- PC (ulpcCEBalanceIAw) parameter controls the target SINR in the interference- aware UL-PC and provides a tilt in balancing the target SINR in the cell center and cell edge. and ulpcRssiMaxIAw parameters are used for tuning the UL-PC algorithm. • The Minimum UL quality for interference-aware UL- PC (ulpcMinQualIAw) parameter defines the minimum quality for the interference- aware UL-PC. Impact on interfaces This feature has no impact on interfaces. the next power command indicates a -1 dB UL power change even if the current UL power is insufficient for reaching the target SINR. This benefit applies to both OL-PC and interference-aware UL-PC. • The Reference UL power value for interference-aware UL- PC (ulpcRefPwrIAw) parameter controls the target SINR in the interference-aware UL-PC. cells are decoupled from each other and both outer-loop power control (OL-PC) and interference-aware UL-PC achieve higher throughput. • The Nominal PUSCH P0 for interference-aware UL- PC (p0NomPuschIAw) parameter is used for SIB2 broadcasting of the P0 when the interference-aware UL-PC is activated. ulpcRefPwrIAw. which is received from the UE. this parameter provides an equal shift of the target SINR for all the UEs in the cell. The target SINR for the UEs during poor condition cannot be lower than the limit defined by this parameter even if it generates a higher UL interference. 4.4 System impact Interdependencies between features This feature requires one of the following features to be activated: • LTE27: Open loop UL power control and DL power setting • LTE28: Closed-Loop UL power control The feature gain (throughput improvement over open-loop UL-PC) is limited if the influence of interference from the adjacent cells is mitigated by other features. • LTE619: Interference-aware UL Scheduler (in conditions of fractional UL load) The interference-aware UL schedulers in adjacent cells can reduce mutual interference by assigning UL transmissions in different areas of the UL spectrum. such as: • Antenna tilt (LTE160: Flexi BTS 3GPP antenna tilt support) With the antenna downtilt. ulpcMinWaitForPc. • The Minimum waiting time for next UL-PC decision (ulpcMinWaitForPc) parameter defines the minimum transmission time interval (TTI) (ms) before another UL power decision is made for the UE. If this upper limit is exceeded.13. 13. key performance indicator.5 LTE1336: Interference aware UL power control management data For information on alarm. Impact on system performance and capacity The feature is expected to show an increase in the overall UL throughput. Measurements and counters Table 62: Existing counters lists existing counters for this feature. see Reference documentation. Table 62 Existing counters Counter ID Counter name Measurement M8012C21 PDCP Throughput UL Min LTE Cell Throughput M8012C22 PDCP Throughput UL Max LTE Cell Throughput M8012C23 PDCP Throughput UL Mean LTE Cell Throughput Key performance indicators There are no key performance indicators related to this feature. Parameters Table 63: New parameters lists parameters introduced with this feature. 4. Table 63 New parameters Full name Abbreviated name Managed object Structure Maximum RSSI for ulpcRssiMaxIAw LNBTS interference-aware UL-PC Method for UL power control actUlpcMethod LNCEL Interference aware UL-PC ulpcIAwConfig LNCEL configuration Nominal PUSCH P0 for p0NomPuschIAw LNCEL ulpcIAwConfig interference-aware UL-PC Cell-center/edge balancing for ulpcCEBalanceIAw LNCEL ulpcIAwConfig interference-aware UL-PC Minimum UL quality for ulpcMinQualIAw LNCEL ulpcIAwConfig interference-aware UL-PC Minimum waiting time for next ulpcMinWaitForPc LNCEL ulpcIAwConfig UL-PC decision Reference UL power value for ulpcRefPwrIAw LNCEL ulpcIAwConfig interference-aware UL-PC DN09185955 Issue: 01J © 2016 Nokia 115 . and parameter documents.1. pronounced in cell centers and less visible at cell borders. LTE RL60. Alarms There are no alarms related to this feature. counter. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Impact on network and network element management tools This feature has no impact on network management or network element management tools. Feature Descriptions and Instructions telecom features 4. Descriptions of radio resource management and LTE RL60.13. • The LNCEL parameter Enabled TB size impact to UE PUSCH power calculation (deltaTfEnabled) is set to false.13.1. • The LNCEL parameter Enable DL AMC (dlamcEnable) is set to true. g Note: Activation and deactivation of this feature cause an execution of the System Information Modification procedure and increase the valueTag parameter (see. The following must be set before the activation of LTE1336: Interference aware UL power control: • The LNCEL parameter Alpha (ulpcAlpha) is set to 1. There can be a mismatch between SIB in the cell and SIB data held by a UE if the valueTag is increased 31 or more times within 3 hours.2 Activating and configuring LTE1336: Interference aware UL power control Before you start Restart of the eNB is not required after activation of this feature.331). • The LNCEL parameter Enable OLQC (dlOlqcEnable) is set to true. 3GPP TS36. Table 65 Parameters used for activating and configuring LTE1336: Interference aware UL power control Parameter Purpose Requires eNB restart or object locking Method for UL power control activation value no (actUlpcMethod) Interference aware UL-PC configuration optional configuration no (ulpcIAwConfig) set of parameters Maximum RSSI for interference-aware optional configuration no UL-PC (ulpcRssiMaxIAw) One of the following features needs to be activated/configured before activation of LTE1336: Interference aware UL power control. in order to provide PUCCH power control: • LTE27: Open loop UL power control and DL power setting • LTE28: Closed-Loop UL power control 116 © 2016 Nokia DN09185955 Issue: 01J .6 Sales information Table 64 Sales information BSW/ASW License control in network Activated by default element ASW SW Asset Monitoring No 4. repeat the following actions: 1. c) Expand the LNBTS object. LTE RL60. a) Go to the Radio Network Configuration page. 3 Define Interference aware UL-PC configuration (ulpcIAwConfig). g Note: This action is optional because the Interference aware UL-PC configuration (ulpcIAwConfig) parameter's structure has default values set during the object creation. right-click the LNCEL object and then select New Interference aware UL-PC configuration. 2. e) Set the Method for UL power control (actUlpcMethod) parameter value to either: • PuschIawPucchOL • PuschIawPucchCL g Note: This parameter activates the feature. DN09185955 Issue: 01J © 2016 Nokia 117 . a) Expand the MRBTS object. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. perform the steps described in this procedure. Expand Interference aware UL-PC configuration under LNCEL object. The modification of the default values is not mandatory. 2 Set the activation value. b) Expand the MRBTS object. d) Select the LNCEL object corresponding to the cell where the LTE1336: Interference aware UL power control feature will be activated. Select Interference aware UL-PC configuration-1 and define all the parameters within this object. c) In each LNCEL object under selected LNBTS. c) Select the LNBTS object. 3. a) Go to the Radio Network Configuration page. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. If the Interference aware UL-PC configuration object is not available under LNCEL. 4 Configure the Maximum RSSI for interference-aware UL- PC (ulpcRssiMaxIAw) (optional). b) Expand the LNBTS object. b) Expand the MRBTS object. Feature Descriptions and Instructions telecom features d) Set the value for the Maximum RSSI for interference-aware UL- PC (ulpcRssiMaxIAw) parameter. b) Expand the MRBTS object. e) Set the Method for UL power control (actUlpcMethod) parameter to any value other than: • PuschIawPucchOL • PuschIawPucchCL 118 © 2016 Nokia DN09185955 Issue: 01J . In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. d) Select the LNCEL object corresponding to the cell where the LTE1336: Interference aware UL power control feature will be deactivated. a) Go to the Radio Network Configuration page. 3GPP TS36. There can be a mismatch between SIB in the cell and SIB data held by a UE if the valueTag is increased 31 or more times within 3 hours. Expected Outcome The LTE1336: Interference aware UL power control feature is activated in the cell.3 Deactivating LTE1336: Interference aware UL power control Before you start Restart of the eNB is not required after deactivation of this feature. The Method for UL power control (actUlpcMethod) parameter is used to deactivate the feature. g Note: Activation and deactivation of this feature cause an execution of the System Information Modification procedure and increase the valueTag parameter (see. 2 Set the Method for UL power control (actUlpcMethod) parameter. 5 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.331). Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. 4. Descriptions of radio resource management and LTE RL60. c) Expand the LNBTS object.13. 2 Requirements Software requirements Table 66: Software requirements lists software required for this feature.1 Description of LTE1342: Extended RNC ID Introduction to the feature The LTE1342: Extended RNC ID provides support for extended RNC IDs. Table 66 Software requirements System release Flexi Multiradio BTS Flexi Multiradio OMS 10 BTS RL60 .1.1.14. - Hardware requirements This feature requires the following hardware: • Flexi Multiradio 10 BTS 4. LBTS6.1 Benefits End-user benefits This feature does not affect the end-user experience. LTE RL60. Expected Outcome The LTE1336: Interference aware UL power control feature is deactivated in the cell.3 Functional description The Flexi Multiradio BTS supports the extended RNC IDs for I-HSPA interworking.1. Operator benefits This feature provides the following benefit to the operator: • an opportunity to interwork with UTRAN networks using extended RNC IDs 4.14. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.14. 4.14.0 - UE NetAct MME SAE GW . 4. NetAct8 EP1 . Following mobility types are enhanced with support of extended RNC ID in the S1AP: HANDOVER REQUIRED message : DN09185955 Issue: 01J © 2016 Nokia 119 .14 LTE1342: Extended RNC ID 4. the Extended RNC-ID is used by the target system. the NetAct Optimizer and BTS Site Manager. Impact on interfaces The following Information Element is supported by the S1AP interface: • Extended RNC-Id IE Impact on network and network element management tools Extension of RNC-Id range is adapted by: the NetAct Configuration Management. PS HO to WCDMA is enhanced with I-HSPA targets support. The eNB builds the Target Cell ID by concatenating 16 bit RNC-ID with 12 LSB of C-ID. in case UTRAN does not use extended RNC-ID. Otherwise. the new consistency check mechanism guarantees that at the same time the Target cell id (uTargetCid) parameter is not configured with value higher than 4095. whenever the Target RNC id (uTargetRncId) parameter is configured with value higher than 4095. In case UTRAN uses extended RNC-ID. 120 © 2016 Nokia DN09185955 Issue: 01J .14. If RNC-ID of the Target Cell has a value smaller than 4096. Descriptions of radio resource management and LTE RL60. • LTE736: CS Fallback to UTRAN CS Fallback to UTRAN is enhanced with I-HSPA targets support. • LTE783: ANR InterRAT UTRAN ANR inter-RAT UTRAN allows to configure I-HSPA targets in LTE database for IRAT mobility towards UTRAN. 4. the regular RNC-ID is used by the target system. Nokia I-HSPA system uses a generic rule used by the eNB to allow interoperability between Nokia LTE and Nokia I-HSPA.4 System impact Interdependencies between features • LTE56: Inter RAT Handover to WCDMA The LTE56: Inter RAT Handover to WCDMA feature need to be activated/configured before activation of the LTE1342: Extended RNC ID feature. • RAN2054: Extension of RNC ids The WCDMA/I-HSPA feature is required to ensure the proper end-to-end functionality of the LTE1342: Extended RNC ID feature. • LTE872: SRVCC to WCDMA SRVCC to WCDMA is enhanced with I-HSPA targets support. Feature Descriptions and Instructions telecom features • PS HO to WCDMA • CSFB to UTRAN • SRVCC to WCDMA Extended RNC ID IE allows to configure target RNC ID in scope of range from 4096 to 65535. The Target RNC id (uTargetRncId) parameter's range is enhanced to cover the range from 0 to 65535.1. With the LTE1342: Extended RNC ID feature. Additionally. In this case the eNB builds the Target Cell ID by concatenating 12 least significant bit (LSB) of RNC-ID with 16 bit C-ID. Target Cell ID The eNB constructs the Target Cell ID from the available parameters. A Target Cell ID is composed of the RNC-ID and the RNC internal C-ID. 2 Activating and configuring LTE1342: Extended RNC ID Before you start There is no separate flag for feature activation. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. . No 4. Table 67 Related existing parameters Name Abbreviated name Managed Object Target cell id uTargetCid LNADJW Target RNC id uTargetRncId LNADJW Target cell Id in UTRAN CGI of uTargetCid LNRELW related neighbor cell Target RNC Id uTargetRncId LNRELW 4.14. LTE RL60.5 Management data Alarms There are no alarms related to this feature.6 Sales information Table 68 Sales information BSW/ASW License control in License control Activated by default network element attributes BSW . Table 67: Related existing parameters lists existing parameters related to this feature. Parameters There are no new parameters related to this feature.1.14. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Impact on system performance and capacity This feature has no impact on system performance or capacity.1. 4. DN09185955 Issue: 01J © 2016 Nokia 121 .14. 122 © 2016 Nokia DN09185955 Issue: 01J . perform the steps described in this procedure. related to no (uTargetRncId) the LTE1342: Extended RNC ID feature Target cell Id in mandatory configuration. Descriptions of radio resource management and LTE RL60. Feature Descriptions and Instructions telecom features Table 69 Parameters used for configuring LTE1342: Extended RNC ID Parameter Purpose Requires eNB restart or object locking Target cell id mandatory configuration. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. related to no UTRAN CGI of the LTE1342: Extended RNC ID related neighbor feature cell (uTargetCid) Neighbor WCDMA BTS mandatory configuration not modifiable cell identifier (lnAdjWId) Primary scrambling mandatory configuration no code (FDD) (uTargetScFdd) Target frequency mandatory configuration no (uTargetFreq) Target location mandatory configuration no area code (uTargetLac) Target routing mandatory configuration no area code (uTargetRac) Target primary mandatory configuration no PLMN identity (primaryPlmnId) parameter structure WCDMA neighbor mandatory configuration not modifiable relation identifier (lnRelWId) Primary PLMN mandatory configuration no identity in CGI of UTRAN neighbor cell (plmnId) parameter structure The LTE56: Inter RAT Handover to WCDMA feature needs to be activated/configured before activation of the LTE1342: Extended RNC ID feature. related to no (uTargetCid) the LTE1342: Extended RNC ID feature Target RNC id mandatory configuration. . c) Expand the LNBTS object. g) Expand the Target primary PLMN identity (primaryPlmnId) parameter structure. DN09185955 Issue: 01J © 2016 Nokia 123 . e) Select New LNRELW. j) For the Primary PLMN identity in CGI of UTRAN neighbor cell-1 Properties set the MCC (mcc). f) For LNRELW Properties set the parameters values. set the MCC (mcc).4095. a) Go to the Radio Network Configuration page. h) Expand the Primary PLMN identity in CGI of UTRAN neighbor cell (plmnId) parameter structure. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 2 Configure the LNADJW parameters. a) Go to the Radio Network Configuration page. d) Select New LNADJW. h) Select the Target primary PLMN identity-1 (primaryPlmnId) parameter structure. the value range of the Target cell id (uTargetCid) is restricted to 0. the value range of the Target cell Id in UTRAN CGI of related neighbor cell (uTargetCid) is restricted to 0. d) Right-click the LNCEL object. b) Expand the MRBTS object. g Note: If the Target RNC id (uTargetRncId) parameter's value is greater than 4095. 3 Configure the LNRELW parameters.. MNC (mnc). MNC length (mncLength) parameters' values. MNC (mnc). b) Expand the MRBTS object. e) For LNADJW-1 Properties set the parameters' values. c) Right-click the LNBTS object. i) For the Target primary PLNN identity-1 Properties. i) Select the Primary PLMN identity in CGI of UTRAN neighbor cell-1 (plmnId) parameter structure.. LTE RL60. g Note: If the Target RNC Id (uTargetRncId) parameter's value is greater than 4095.. MNC length (mncLength) parameters' values.4095. g) Expand LNRELW-1 object. f) Expand LNADJW object. e) Select delete LNADJW. c) Select the LNBTS object. c) Expand the LNBTS object. b) Expand the MRBTS object. d) Right-click the LNADJW object. e) Right-click the LNRELW object. b) Expand the MRBTS object. a) Go to the Radio Network Configuration page. 124 © 2016 Nokia DN09185955 Issue: 01J .3 Deactivating LTE1342: Extended RNC ID Before you start The LTE56: Inter RAT Handover to WCDMA activation flag: Activate Handover from LTE to WCDMA (actHOtoWcdma) is used for deactivation the LTE1342: Extended RNC ID feature. Feature Descriptions and Instructions telecom features 4 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. d) Set the Activate Handover from LTE to WCDMA (actHOtoWcdma) parameter value to false. d) Expand the LNCEL object. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. 2 Deactivate the feature.14. 3 Delete the LNADJW parameters (optional). c) Expand the LNBTS object. a) Go to the Radio Network Configuration page. 4. 4 Delete the LNRELW parameters (optional). f) Select delete LNRELW. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. Descriptions of radio resource management and LTE RL60. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. - Hardware requirements DN09185955 Issue: 01J © 2016 Nokia 125 . 4.1 Description of LTE1382: Cell resource groups Introduction to the feature The LTE1382: Cell resource groups allows to virtually split the cell resources. Operator benefits The feature provides the operator with the following benefits: • allows the operator to define the size of shares per each cell resource group (the CRG) (for example for the MOCN usage) • allows for savings when using the shared hardware and the LTE/EPS infrastructure 4.0 - UE NetAct MME SAE GW 3GPP R8 mandatory NetAct8 EP1 .1 Benefits End-user benefits The feature provides the end-user with the following benefits: • The LTE1382: Cell resource groups feature provides the broader access to the LTE network and services.15 LTE1382: Cell resource groups 4. as the operators are able to share the network among each others.15.0 LBTS6.2 Requirements Software requirements Table 70: Software requirements lists the software required for this feature. 4.15.14 Variable Definitions 4.15. LTE RL60. Table 70 Software requirements System release Flexi Multiradio BTS Flexi Multiradio 10 OMS BTS RL60 LBTS6. Expected outcome This step deactivates both features: the LTE56: Inter RAT Handover to WCDMA and the LTE1342: Extended RNC ID.1. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 5 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.1. DRBs. The resource shares are as well applied for emergency sessions. The resource split is configured via the O&M. The feature can be activated either in the DL direction or both in the UL and DL. TTIs not used by the dedicated CRG are automatically reused by other cell resource groups. The sum of all per-CRG resource shares in the cell must be 100% on the per-cell level. Feature Descriptions and Instructions telecom features This feature requires no new or additional hardware. and the proper amount of resources (TTIs). and CA-UEs) up to four resource groups (that can be used by different operators). The minimum share for the CRG is 20%. The total cell capacity can be divided according to the operator's needs and agreements with other operators. with a 1% step size granularity (for example. The following performance counters are provided in order to track the performance per resource group: • number of used TTIs per direction and resource group • number of available TTIs in UL and DL in total per measurement interval The functionality can be enabled/disabled per cell by O&M setting.3 Functional description The feature allows the operator to split the physical cell resources (PDSCH and PUSCH of the user plane as well as a number of active UEs. This only applies if no bad side effects on service quality (for example voice service) and feature functionalities like DRX is expected. Descriptions of radio resource management and LTE RL60. The feature can be used only on the 10. In the first case. 4. when there is a need for transmission in other CRGs.. There is no possibility for the online modification of parameters (PLMN ID mapping. Not assigned PLMN-IDs are mapped to a default CRG. 30% - 40% - 30% in case of three cell resource groups). and 20 MHz bandwidths. etc) 126 © 2016 Nokia DN09185955 Issue: 01J . The pre-emption functionality at the radio admission control considers the share that is set to the specific CRG which is performing the admission control operation. The resource split is configured on cell level and always can be configured and changed. the per-cell limits are weighted with a CRGs share in order to derive the per-CRG admission limits. what is checked by the consistency check via the O&M. 15.1. The resources sharing in the cell has higher priority than the QoS requirements of the individual UE/bearer. resource shares.15. Emergency sessions without a resource group assignment are mapped to a default resource group. the configured share per CRG applies to both DL and UL. In the second case. when the feature is created both in the UL and DL. The resource group share is applied to the following: • admission control thresholds and counters (exception: RRC connection requests) • TTI assignments for PDSCH and PUSCH (when the DL and UL is configured) • congestion control limits in scheduling In the above mentioned cases. It is not allowed to map the same PLMN to multiple resource groups. Mapping of multiple PLMNs to one resource group is allowed. the shares created for the CRG are applied only for the DL direction (the UL is scheduled without the CRGs usage). • LTE907: TTI bundling g Note: The LTE907: TTI bundling feature needs to be deactivated only when feature LTE1382: Cell resource groups is activated by setting Cell resource sharing mode (cellResourceSharingMode) parameter value to DLandUL. Protection against load balancing traffic works on a cell level. In case this parameter value is none or DLonly the LTE907: TTI bundling does not have to be deactivated. but load balancing handovers to a CRG in the target cell must be rejected. when the cell enters inter-frequency load balancing active state. – The load balancing target cell accepts load balancing handovers as long as the composite available capacity (CAC) is higher than 0.4 MHz • LTE616: Usage Based PDCCH Adaptation • LTE1531: Inter-Frequency Load Balancing Extension From FDD LTE15A onwards. inter-frequency load balancing is triggered not for CRG’s high load. – From a cell load. not to the CRG level.15. The LTE1382: Cell resource groups feature needs the following features to be enabled: • LTE496: Support of QCI 2. and the high loaded CRGs might happen to accept load balancing handovers.4 System impact Interdependencies between features The interworking with the following features is not supported: • LTE1387: Intra eNodeB Inter-Frequency Load Balancing • LTE1170: Inter-Frequency Load Balancing g Note: The LTE1387: Intra eNodeB Inter-Frequency Load Balancing and LTE1170: Inter-Frequency Load Balancing features consider cell limits and not the limits configured by the LTE1382: Cell Resource Groups feature. DN09185955 Issue: 01J © 2016 Nokia 127 . simultaneous activation LTE1382: Cell Resource Groups with LTE1387: Intra eNodeB Inter-Frequency Load Balancing. – The user equipment candidate's selection for inter-frequency load balancing is done on a cell's scope. The mentioned LB thresholds apply to the cell level only. It might be possible that CAC is higher than 0. • LTE115: Cell Bandwidth - 5 MHz • LTE116: Cell Bandwidth - 3 MHz • LTE117: Cell Bandwidth - 1.1. LTE RL60.3 and 4 • LTE497: Smart admission control • LTE534: ARP based admission control Impact on interfaces This feature has no impact on interfaces. LTE1170:Inter- frequency load balancing and LTE1531: Inter-Frequency Load Balancing Extension is allowed by O&M and can cause the following effects: – One threshold is assigned to start inter-frequency load balancing in the cell and another one to stop it. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4. – It makes no difference which CRG causes high load and which not. because CRG's thresholds are reached. 4. Parameters Table 72: New parameters lists parameters introduced with this feature.5 LTE1382: Cell resource groups management data Alarms There are no alarms related to this feature. note that the CRGs are normally configured across several network elements with the same shares. Descriptions of radio resource management and LTE RL60. Feature Descriptions and Instructions telecom features Impact on network and network element management tools This feature has no impact on network management or network element management tools. The total cell capacity (the sum of resource group capacities per cell) is not affected Depending on the resource group configuration the UL and DL throughput will decrease proportional to the fraction of TTIs assigned to the resource group. Impact on system performance and capacity The cell throughput per resource group is proportional to the number of TTIs assigned. For a given resource group the assignment of complete TTIs to other resource groups causes additional waiting times for the next TTI assigned to the resource group. Table 71 Related existing counters Counter ID Counter Name Measurement M8011C70 TTIs used in UL by cell resource group 1 8011 - LTE Cell Resource (WBTS) M8011C71 TTIs used in UL by cell resource group 2 8011 - LTE Cell Resource (WBTS) M8011C72 TTIs used in UL by cell resource group 3 8011 - LTE Cell Resource (WBTS) M8011C73 TTIs used in UL by cell resource group 4 8011 - LTE Cell Resource (WBTS) M8011C74 Number of available TTIs for PUSCH 8011 - LTE Cell Resource (WBTS) M8011C75 TTIs used in DL by cell resource group 1 8011 - LTE Cell Resource (WBTS) M8011C76 TTIs used in DL by cell resource group 2 8011 - LTE Cell Resource (WBTS) M8011C77 TTIs used in DL by cell resource group 3 8011 - LTE Cell Resource (WBTS) M8011C78 TTIs used in DL by cell resource group 4 8011 - LTE Cell Resource (WBTS) M8011C79 Number of available TTIs for PDSCH 8011 - LTE Cell Resource (WBTS) Key performance indicators There are no key performance indicators related to this feature.15. The cell throughput per resource group is proportional to the number of TTIs assigned and to the share for the specific CRG.1. and PLMN-IDs are then used as criteria to differentiate between the CRGs. 128 © 2016 Nokia DN09185955 Issue: 01J . Nevertheless. Measurements and counters Table 71: Related existing counters lists existing counters related to this feature. LTE RL60. Table 73 Related existing parameters Full name Abbreviated name Managed Structure object Activate enhanced AC actEnhAcAndGbrServices LNBTS and GBR services Activation of inter. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 72 New parameters Full name Abbreviated name Managed Structure object Cell resource group crgPrId CRGPR profile identifier Cell resource group crgSkipThreshold CRGPR subframe skipping threshold Default PLMN defaultPlmnGroupId CRGPR group PLMN group list plmnGroupList CRGPR Mobile country mcc CRGPR plmnGroupList code Mobile network mnc CRGPR plmnGroupList code Mobile network mncLength CRGPR plmnGroupList code length PLMN group plmnGroupId CRGPR plmnGroupList identifier Plmn group share plmnGroupShareList CRGPR list PLMN group plmnGroupId CRGPR plmnGroupShareList identifier Cell resource group plmnGroupShare CRGPR plmnGroupShareList share Assigned cell cellResourceGroupPrId LNCEL resource group profile Cell resource cellResourceSharingMode LNCEL sharing mode Table 73: Related existing parameters lists existing parameters related to this feature. actInterFreqLB LNBTS frequency load balancing (iFLB) Activate UE-based actUeBasedAnrInterFreqLte LNBTS ANR for Inter- frequency LTE Activate UE-based actUeBasedAnrIntraFreqLte LNBTS ANR for intra- Frequency LTE Activate DRX actDrx LNCEL DN09185955 Issue: 01J © 2016 Nokia 129 . .5]) • DRX smart profile [2...5] LNCEL [2.5]) The drxProfile[2. only the DRX on duration timer (drxOnDuratT) is related to the LTE1382: Cell resource groups feature.5] g Note: The structures listed below contain more parameters.) Full name Abbreviated name Managed Structure object Activate load adaptive actLdPdcch LNCEL PDCCH Activate smart DRX actSmartDrx LNCEL Activate TTI bundling actTtiBundling LNCEL Downlink channel dlChBw LNCEL bandwidth DRX profile 101 drxProfile101 LNCEL DRX on duration timer drxOnDuratT LNCEL drxProfile101 DRX profile 103 drxProfile103 LNCEL DRX on duration timer drxOnDuratT LNCEL drxProfile103 DRX profile [2.5] (drxProfile[2..5] DRX smart profile drxSmartProfile[2.....5]: – drxSmartProfile2 – drxSmartProfile3 – drxSmartProfile4 – drxSmartProfile5 130 © 2016 Nokia DN09185955 Issue: 01J .5] (drxSmartProfile[2....5] drxProfile[2. however..5] LNCEL DRX on duration timer drxOnDuratT LNCEL drxProfile[2........ Descriptions of radio resource management and LTE RL60.5] listed in Table 73: Related existing parameters contains the following parameters: • drxProfile[2.5] DRX on duration timer drxOnDuratT LNCEL drxSmartProfile[2...5]: – drxProfile2 – drxProfile3 – drxProfile4 – drxProfile5 • drxSmartProfile[2.... Feature Descriptions and Instructions telecom features Table 73 Related existing parameters (Cont. These are the following structures: • DRX profile 101 (drxProfile101) • DRX profile 103 (drxProfile103) • DRX profile [2..5] and the drxSmartProfile[2.... No 4. 3 and 4 • LTE497: Smart Admission Control The following features need to be deactivated before activation of the LTE1382: Cell resource groups feature: • LTE616: Usage based PDCCH adaptation • LTE907: TTI bundling DN09185955 Issue: 01J © 2016 Nokia 131 .2 Activating and configuring LTE1382: Cell resource groups Before you start Table 75 Parameters used for activating and configuring LTE1382: Cell resource groups Parameter Purpose Requires eNB restart or object locking Cell resource group mandatory configuration no profile identifier (crgPrId) Cell resource group mandatory configuration no subframe skipping threshold (crgSkipThreshold) Default PLMN group mandatory configuration object locking (defaultPlmnGroupId) PLMN group list mandatory configuration object locking (plmnGroupList)parameter structure Plmn group share list mandatory configuration object locking (plmnGroupShareList ) parameter structure Assigned cell resource mandatory configuration object locking group profile (cellResourceGroupPrId) Cell resource sharing activation flag object locking mode (cellResourceSharingMod e) The following features need to be activated/configured before activation of the LTE1382: Cell resource groups feature: • LTE534: ARP-based Admission Control for E-RABs • LTE496: Support of QCI 2.15.6 Sales information Table 74 Sales information BSW/ASW License control in License control Activated by default network element attributes ASW SW Asset Monitoring . LTE RL60.1.15. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4. 4 MHz. e) Set the parameters in the CRGPR object. f) Expand the CRGPR object. Descriptions of radio resource management and LTE RL60. perform the steps described in this procedure. d) Right-click on the LNBTS object and select New CRGPR. 5 MHz. The following parameters: • DRX inactivity timer (drxInactivityT) • DRX on duration timer (drxOnDuratT) • DRX retransmission timer (drxRetransT) are set to values higher than 8 to ensure sufficient time for scheduling all resource groups. 132 © 2016 Nokia DN09185955 Issue: 01J . 3 MHz. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. a) Go to the Radio Network Configuration page. In case this parameter value is none or DLonly the LTE907: TTI bundling does not have to be deactivated. • LTE1387: Intra-eNode B IF Load Balancing • LTE1170: Inter-frequency load balancing The cell bandwidth must be higher than 5 MHz. which means that the parameter Downlink channel bandwidth (dlChBw) located in LNCEL object. cannot be equal to the following values: 1. c) Select the LNBTS object. Feature Descriptions and Instructions telecom features g Note: The LTE907: TTI bundling feature needs to be deactivated only when feature LTE1382: Cell resource groups is activated by setting Cell resource sharing mode (cellResourceSharingMode) parameter value to DLandUL. 2 Cell resource group profile creation. All these parameters are located in the following parameter structures in LNCEL object: • DRX profile 101 (drxProfile101) • DRX profile 103 (drxProfile103) • DRX profile 2 (drxProfile2) • DRX profile 3 (drxProfile3) • DRX profile 4 (drxProfile4) • DRX profile 5 (drxProfile5) • DRX smart profile 2 (drxSmartProfile2) • DRX smart profile 3 (drxSmartProfile3) • DRX smart profile 4 (drxSmartProfile4) • DRX smart profile 5 (drxSmartProfile5) Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. b) Expand the MRBTS object. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features g) At least two. d) Select the LNCEL object. h) Set the parameters located in the Plmn group share list (plmnGroupShareList) parameter structure. 4 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Expected outcome The LTE1382: Cell resource groups is activated. g Note: Plmn group share list (plmnGroupShareList) must be defined and assigned by PLMN group identifier (plmnGroupId) parameter to each PLMN group list (plmnGroupList). b) Expand the MRBTS object. Set parameters in those structures. The parameter value must be equal to the Cell resource group profile identifier (crgPrId) parameter value in CRGPR object. LTE RL60. g Note: In one PLMN group list (plmnGroupList) parameter structure the following parameters: • Mobile country code (mcc) • Mobile network code (mnc) • Mobile network code length (mncLength) gets the same values as parameters: • MCC in PLMN (mcc) • MNC in PLMN (mnc) • MNC length in PLMN (mncLength) in LNBTS managed object. f) Set the Cell resource sharing mode (cellResourceSharingMode) parameter value to DLonly or DLandUL to activate the LTE1382: Cell resource groups feature. e) Set the Assigned cell resource group profile (cellResourceGroupPrId) parameter. up to four. DN09185955 Issue: 01J © 2016 Nokia 133 . The sum of Cell resource group share (plmnGroupShare) values in Plmn group share list (plmnGroupShareList) must be equal to 100%. PLMN group list (plmnGroupList) parameter structures are needed. a) On the Radio Network Configuration page. c) Expand the LNBTS object. 3 Activate the LTE1382: Cell resource groups feature. 4.1 LTE1402 benefits End-user benefits This feature increases throughput and hence also service quality for UEs on the cell edge regions of cells from the CoMP set. 4. Operator benefits 134 © 2016 Nokia DN09185955 Issue: 01J . 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Expected outcome The LTE1382: Cell resource groups feature is deactivated. Feature Descriptions and Instructions telecom features 4. remove the CRGPR object.16.1 Description of LTE1402: Uplink Intra-eNB CoMP Introduction to the feature The uplink intra evolved node B (eNB) Co-ordinated Multipoint (CoMP) feature improves average cell throughput and the cell edge performance by taking into account uplink information from neighbor cell antennas. e) Set the Cell resource sharing mode (cellResourceSharingMode) parameter value to none. 2 Deactivate the LTE1382: Cell resource groups feature. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. c) Expand the LNBTS object. f) Optionally. a) Go to the Radio Network Configuration page. Descriptions of radio resource management and LTE RL60. b) Expand the MRBTS object.15.16.16 LTE1402: Uplink Intra-eNB CoMP 4. Modification of this parameter requires object locking. d) Select the LNCEL object.3 Deactivating LTE1382: Cell resource groups Before you start The Cell resource sharing mode (cellResourceSharingMode) parameter is used for deactivation. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager.1. 1.16. The eNB selects automatically per UE and per TTI the most suitable neighbor cell out of the CoMP set. the eNB can use two pairs of Rx antennas (one pair from serving cell and one pair from one of the cells in the UL CoMP set) depending on the measured SINR in the neighbor cells. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features The uplink intra-eNB CoMP provides up to 50% cell edge improvement in comparison to two Rx receiver.16.3 Functional description The eNB supports uplink intra-eNB CoMP that is applied for cells with two RX paths. Table 76 Software Requirements System release Flexi Multiradio Flexi Multiradio 10 iOMS BTS BTS RL60 . Cells within a CoMP set must have: • the same UL carrier frequency (EARFCN) • the same UL bandwidth UL CoMP example DN09185955 Issue: 01J © 2016 Nokia 135 . The selection of the neighbor cell for the joint reception is based on uplink SINR measurement before combining. the eNB uses two Rx antennas only from serving cell. is operator- configurable. The CoMP set. LBTS6. From these six Rx antennas. 4. 4. CoMP set This feature is supported with two Rx antennas in cell. - Hardware requirements This feature is not supported on FSMD and FSME . and the operator configures UL CoMP set that consists of maximum three cells. CoMP sets can be just defined within a single eNB (UL intra-eNB CoMP).2 Requirements Software requirements Table 76: Software Requirements lists the software required for this feature. Combining is done only for the Physical UL Shared Channel (PUSCH) to receive the UL Shared Channel (UL-SCH). This means there is no combining gain for overlapping cells from separate CoMP sets or separate eNBs. that is neighbor cells that are considered for the selection.0 - UE NetAct MME SAE GW 3GPP R8 mandatory NetAct8 EP1 . The joint reception is applied for the PUSCH. LTE RL60.1. It means that one cell belonging to UL CoMP set monitors up to six Rx antennas. If SINR measurements in neighbor cells are under a threshold defined by the Uplink CoMP SINR Threshold (ulCoMpSinrThreshold) parameter. Therefore the UL Rx is done either with two Rx or four Rx algorithm (IRC). 4 System impact Interdependencies between features 136 © 2016 Nokia DN09185955 Issue: 01J . When the UE is close to cell edge. Feature Descriptions and Instructions telecom features Figure 5: UL CoMP scenario presents an example of the LTE1402: Uplink Intra-eNB CoMP feature scenario.1. it requires BTS restart. The operator modifies the overlapping region where antennas from two cells are combined using the Uplink CoMP SINR Threshold (ulCoMpSinrThreshold) for each CoMP set. the eNB uses only two Rx antennas from the serving cell because in the cell 1 and 3 signal from this UE is too low. 4. In the ULCOMP managed object class (MOC). the operator defines two or three cells that belong to CoMP set.twoRxantennaspersector) UEinthecenterofthecell UEonthecelledge 2 1 ULCoMPset 3 Feature configuration The Activate Uplink CoMP (actUlCoMp ) parameter is used for activation of the feature. Each cell can be included only into one ULCOMP instance. It is possible to add/remove cells from CoMP sets. Descriptions of radio resource management and LTE RL60. Figure 5 UL CoMP scenario 2 1 3 eNB(threesectors/cells. The Uplink CoMP SINR Threshold (ulCoMpSinrThreshold) can be modified online. To receive a signal from the UE in the center of the cell number 2. however. The operator-defined UL CoMP set consists of three cells.16. This parameter determines the signal quality difference between the serving cell and the neighbor cells. the eNB combines signal received via two Rx antennas from the serving cell 2 and two Rx antennas from the neighbor cell 3 using IRC algorithm. 4 MHz • LTE116: Cell Bandwidth - 3 MHz • LTE72: 4-way Rx diversity • LTE980: IRC for 4 Rx paths • LTE1542: FDD Supercell The LTE614: Distributed Site feature is supported together with the LTE1402: Uplink Intra-eNB CoMP feature. Impact on interfaces This feature has no impact on interfaces. LTE RL60.1.16. Parameters Table 78: New parameters lists parameters introduced with this feature. however. it is recommended that the distance between related RRHs is less than 1km and the maximum difference in Doppler shift experienced at the RRHs is less than 250Hz. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features The LTE979: IRC for 2 RX paths feature has to be activated. The following features need to be deactivated: • LTE48: Support of high speed users • LTE117: Cell Bandwidth - 1. (WBTS) eNB CoMP Key performance indicators There are no key performance indicators related to this feature. 4. Table 78 New parameters Full name Abbreviated name Managed object Activate Uplink CoMP actUlCoMp LNBTS DN09185955 Issue: 01J © 2016 Nokia 137 . Impact on system performance and capacity This feature improves cell capacity and the cell edge performance by taking into account uplink information from neighbor cells. Table 77 New counters Counter ID Counter name Measurement M8001C198 Average number of 8001 - LTE Cell Load UEs utilizing UL intra. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Measurements and counters Table 77: New counters lists counters introduced with this feature.5 LTE1402: Uplink Intra-eNB CoMP management data Alarms There are no alarms related to this feature. 4 MHz • LTE116: Cell Bandwidth - 3 MHz • LTE72: 4-way Rx diversity 138 © 2016 Nokia DN09185955 Issue: 01J . Feature Descriptions and Instructions telecom features Table 78 New parameters (Cont.) Full name Abbreviated name Managed object Uplink CoMP Cell List ulCoMpCellList ULCOMP Uplink coordinated multipoint ulCoMpId ULCOMP identifier Uplink CoMP SINR Threshold ulCoMpSinrThreshold ULCOMP 4. the LTE979: IRC for 2 RX feature must be activated before activation of the LTE1402: Uplink Intra-eNB CoMP feature.1. Descriptions of radio resource management and LTE RL60.16.2 Activating and configuring LTE1402: Uplink Intra-eNB CoMP Before you start The operator has defined cells that operates on the same channel bandwidth and the same EARFCN value. No 4.6 Sales information Table 79 Sales Information BSW/ASW License control in network License control Activated by default element attributes ASW SW Asset Monitoring . Table 80 Parameters used for activating and configuring LTE1402: Uplink Intra-eNB CoMP Parameter Purpose Requires eNB restart or object locking Activate Uplink CoMP activation flag restart (actUlCoMp) Uplink CoMP Cell List mandatory configuration restart (ulCoMpCellList) Uplink coordinated mandatory configuration restart multipoint identifier (ulCoMpId) Uplink CoMP SINR mandatory configuration no Threshold (ulCoMpSinrThreshold) In each of the cells that will be assigned to the UL CoMP set. The following features need to be deactivated before activation of LTE1402: Uplink Intra- eNB CoMP: • LTE48: Support of high speed users • LTE117: Cell Bandwidth - 1.16. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure...X].. For each of these cells create Uplink CoMP Cell List-[1. d) Set the Activate Uplink CoMP (actUlCoMp) parameter to true. a) Go to the Radio Network Configuration page.. 2 Set the activation flag. b) Expand the MRBTS object. 3 Define and configure UL CoMP set. f) Expand the Uplink CoMP Cell List object.X] by right-clicking on the Uplink CoMP Cell List and selecting New Uplink CoMP Cell List-[1.. Expected Outcome The LTE1402: Uplink Intra-eNB CoMP feature is activated and the eNB uses UL CoMP sets to improve average cell throughput and the cell edge performance. DN09185955 Issue: 01J © 2016 Nokia 139 . g) Up to three cells can be assigned to the UL CoMP set. e) Expand the ULCOMP object. LTE RL60. 4 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. h) In each of Uplink CoMP Cell List-[1.. g Note: Each of the cells of UL CoMP set must operate on the same channel bandwidth and the same EARFCN value. d) Set the Uplink coordinated multipoint identifier (ulCoMpId) parameter value. g Note: The Uplink CoMP Cell property must be equal to the LTE cell configuration identifier (lnCelId) parameter of the cell that is to be included to the CoMP set. set the Uplink CoMP Cell property. c) Right-click on the LNBTS object and select New ULCOMP.X]. a) Go to the Radio Network Configuration page. where X is the number of cells to be assigned to the UL CoMP set. b) Expand the MRBTS object. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features • LTE980: IRC for 4 Rx paths • LTE1542: FDD Supercell Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. c) Select the LNBTS object. 4.1 Benefits End-user benefits This feature does not affect the end-user experience.17. The LPPa uses S1AP transport services on the S1 interface. b) Expand the MRBTS object. Operator benefits This feature allows the E-SMLC to retrieve automatically OTDOA-related cell information from the eNB.1 Description of LTE1433: LPPa support for OTDOA Introduction to the feature The LTE1433: LPPa support for OTDOA allows the Enhanced Serving Mobile Location Center (E-SMLC) to retrieve the Observed Time Difference of Arrival (OTDOA) related cell information from the eNB to support OTDOA-based UE positioning. 140 © 2016 Nokia DN09185955 Issue: 01J .16. a) Go to the Radio Network Configuration page. c) Select the LNBTS object. 4. Descriptions of radio resource management and LTE RL60. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. Feature Descriptions and Instructions telecom features 4. 2 Set the (de)activation flag. d) Set the Activate Uplink CoMP (actUlCoMp) parameter to false.1.17. which is an application protocol between E-SMLC and eNB. Modification of this parameter requires eNB restart.17 LTE1433: LPPa support for OTDOA 4.3 Deactivating LTE1402: Uplink Intra-eNB CoMP Before you start The Activate Uplink CoMP (actUlCoMp) parameter is used for deactivation. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. Expected Outcome The LTE1402: Uplink Intra-eNB CoMP feature is deactivated and the eNB does not use cells from the UL CoMP sets to improve average cell throughput and the cell edge performance. The OTDOA information request procedure uses LTE Positioning Protocol Annex (LPPa). AP LCS. LTE RL60. The following LTE cell specific information are sent via S1AP if requested by LPPA: OTDOA INFORMATION REQUEST message: • Physical Cell Identity (PCI) • Cell ID DN09185955 Issue: 01J © 2016 Nokia 141 .2 Requirements Software requirements Table 81: Software requirements lists the software required for this feature. The E-SMLC interacts also with other network entities such as MME and UE. - Hardware requirements This feature requires no new or additional hardware. 4.1.17. LPPa is an application layer protocol for positioning purposes between Enhanced Serving Mobile Location Centre (E-SMLC) and eNB.0 LBTS6. Figure 6: Protocol layer between E-SMLC and eNB shows the protocol layering between E-SMLC and eNB. In the LTE positioning architecture the E-SMLC acts as central control entity being responsible for processing of positioning requests. In this context the related LPPa procedures and S1AP transport services are supported.1.3 Functional description The LTE1433: LPPa support for OTDOA feature introduces LTE Positioning Protocol Annex (LPPa) in the eNB. Table 81 Software requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 LBTS6.0 - UE NetAct MME SAE GW 3GPP R9 UE capabilities NetAct8 EP1 . Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4.AP SCTP SCTP SCTP SCTP IP IP IP IP L2 L2 L2 L2 L1 L1 L1 L1 S1-MME SLs eNodeB MME E-SMLC The LTE1433: LPPa support for OTDOA feature allows the E-SMLC to retrieve OTDOA- related cell information from the eNB to support OTDOA-based UE positioning. Figure 6 Protocol layer between E-SMLC and eNB LPPa LPPa S1-AP S1-AP LCS.17. SFN Initialisation Time is the only OTDOA information type. the eNB responds with the LPPA: OTDOA INFORMATION FAILURE message that contains a failure cause indicating why the required OTDOA information cannot be provided. Descriptions of radio resource management and LTE RL60. if configured this information is available. If the requested OTDOA information type is not configured for an OTDOA-activated cell. Availability of E-UTRAN Access Point Position and PRS Muting Configuration depends on configuration. Feature Descriptions and Instructions telecom features • Tracking Area Code (TAC) • E-UTRA Absolute Radio Frequency Channel Number (EARFCN) • Positioning Reference Signal (PRS) Bandwidth • Positioning Reference Signal (PRS) Configuration Index • Positioning Reference Signal (PRS) Muting Configuration • Cyclic Prefix (CP) Length • Number of DL Frames • Number of Antenna Ports • System Frame Number (SFN) Initialization Time • E-UTRAN Access Point Position The Flexi Multiradio BTS supports the LPPa OTDOA information request procedure via the S1AP. that has to be dynamically calculated at requested time. The LPPa protocol is encapsulated in the S1AP: DOWNLINK NON UE ASSOCIATED LPPA TRANSPORT and S1AP: UPLINK NON UE ASSOCIATED LPPA TRANSPORT messages as shown below: • S1AP: DOWNLINK NON UE ASSOCIATED LPPA TRANSPORT – LPPA: OTDOA INFORMATION REQUEST – LPPA: ERROR INDICATION • S1AP: UPLINK NON UE ASSOCIATED LPPA TRANSPORT – LPPA: OTDOA INFORMATION RESPONSE – LPPA: OTDOA INFORMATION FAILURE – LPPA: ERROR INDICATION OTDOA Information Exchange procedure The E-SMLC initiates the procedure by sending the LPPA: OTDOA INFORMATION REQUEST message (encapsulated in S1AP: DOWNLINK NON UE ASSOCIATED LPPA TRANSPORT message) to the eNB including requested OTDOA information types. none of the requested OTDOA information types can be provided because they are not configured). The eNB responds with the LPPA: OTDOA INFORMATION RESPONSE message (encapsulated in S1AP: UPLINK NON UE ASSOCIATED LPPA TRANSPORT message) that contains requested OTDOA information types for all OTDOA-activated cells served by the eNB. Additionally PRS Muting Configuration is an optional information type for the LTE495: OTDOA feature. 142 © 2016 Nokia DN09185955 Issue: 01J . all OTDOA information types should be available in the eNB as these are related to the LTE495: OTDOA feature. feature is not activated. In case some exceptions (for example. it is not provided in the LPPA: OTDOA INFORMATION RESPONSE message. The eNB supports multiple OTDOA Information Exchange procedures in parallel. Except E-UTRAN Access Point Position and SFN Initialisation Time. This procedure can be initiated by E- SMLC or eNB by sending the LPPA: ERROR INDICATION message.1.17. 4. and traced as known message. logged. here LPPA: OTDOA INFORMATION FAILURE message sent by eNB. Table 82 New parameters Full name Abbreviated name Managed object Structure Activate LPPa support actLPPaOtdoa LNBTS for OTDOA E-UTRAN access eutranAccessPointPos LNCEL point position ition Altitude altitude LNCEL eutranAccessPointPos ition DN09185955 Issue: 01J © 2016 Nokia 143 . Parameters Table 82: New parameters lists parameters introduced with this feature. Impact on interfaces This feature impacts the S1-MME interface by introducing new messages: • S1AP: DOWNLINK NON UE ASSOCIATED LPPA TRANSPORT • S1AP: UPLINK NON UE ASSOCIATED LPPA TRANSPORT Impact on network and network element management tools This feature has no impact on network management or network element management tools. that the received LPPA: ERROR INDICATION message is received.5 LTE1433: LPPa support for OTDOA management data Alarms There are no alarms related to this feature. LTE RL60. If initiated by the E- SMLC the eNB supports the procedure in the sense. Key performance indicators There are no key performance indicators related to this feature. Impact on system performance and capacity System performance impact might vary between high and negligible dependent on the number of requests send by E-SMLC to the eNB. 4.1. The purpose of the procedure is to report to the remote node that the received LPPa message includes errors which cannot be reported by an LPPa Location Information Transfer procedure-specific failure message.17. but no further action is taken on functional level. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features The eNB supports the Error Indication procedure on the LPPa layer (between E-SMLC and eNB). Measurements and counters There are no measurements or counters related to this feature.4 System impact Interdependencies between features The LTE495: OTDOA feature needs to be enabled. 6 Sales information Table 84 Sales information BSW/ASW License control in License control Activated by default network element attributes ASW SW Asset Monitoring . Descriptions of radio resource management and LTE RL60.1. Feature Descriptions and Instructions telecom features Table 82 New parameters (Cont.17. No 4.2 Activating and configuring LTE1433: LPPa support for OTDOA Before you start Table 85 Parameters used for activating and configuring LTE1433: LPPa support for OTDOA Parameter Purpose Requires eNB restart or object locking Activate LPPa activation flag no support for OTDOA (actLPPaOtdoa) 144 © 2016 Nokia DN09185955 Issue: 01J . uncertaintySemiMinor LNCEL eutranAccessPointPos minor ition Table 83: Related existing parameters lists existing parameters related to this feature.) Full name Abbreviated name Managed object Structure Confidence confidence LNCEL eutranAccessPointPos ition Degrees of latitude degreesOfLatitude LNCEL eutranAccessPointPos ition Degrees of longitude degreesOfLongitude LNCEL eutranAccessPointPos ition Direction of altitude directionOfAltitude LNCEL eutranAccessPointPos ition Latitude sign latitudeSign LNCEL eutranAccessPointPos ition Orientation of major orientationOfMajorAxis LNCEL eutranAccessPointPos axis ition Uncertainty altitude uncertaintyAltitude LNCEL eutranAccessPointPos ition Uncertainty semi. uncertaintySemiMajor LNCEL eutranAccessPointPos major ition Uncertainty semi.17. Table 83 Related existing parameters Full name Abbreviated name Managed object PRS activation actOtdoa LNCEL 4. d) Set the Activate LPPa support for OTDOA (actLPPaOtdoa) parameter value to true. Expected outcome The LTE1433: LPPa support for OTDOA feature is activated. d) Right click on LNCEL object and add E-UTRAN access point position parameter structure.) Parameter Purpose Requires eNB restart or object locking E-UTRAN access optional configuration no point position (eutranAccessPoint Position) parameter structure The LTE495: OTDOA feature needs to be activated/configured before activation of LTE1433: LPPa support for OTDOA. c) Expand the LNBTS object. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. b) Expand the MRBTS object. 4 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 85 Parameters used for activating and configuring LTE1433: LPPa support for OTDOA (Cont. DN09185955 Issue: 01J © 2016 Nokia 145 . 3 Configure the E-UTRAN access point position (optional). LTE RL60. c) Select the LNBTS object. e) Select the E-UTRAN access point position and set all parameters included there. a) Go to the Radio Network Configuration page. a) Go to the Radio Network Configuration page. 2 Activate the LTE1433: LPPa support for OTDOA feature. b) Expand the MRBTS object. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. 146 © 2016 Nokia DN09185955 Issue: 01J .1 Description of LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) Introduction to the feature The eNB supports an enhanced circuit switch (CS) fallback to 1xRTT without concurrent PS handover (Rel-9. b) Expand the MRBTS object. The UE capabilities are checked if the UE supports enhanced CS fallback to 1xRTT (e-CSFB-1XRTT-r9). a) Go to the Radio Network Configuration page. then it falls back to R8 1xCSFB. Feature Descriptions and Instructions telecom features 4. Furthermore.3 Deactivating LTE1433: LPPa support for OTDOA Before you start The Activate LPPa support for OTDOA (actLPPaOtdoa) parameter is used for deactivation. if R9 1xCSFB is not possible.17. R8 1xCSFB is also a part of this feature. Modification of this parameter does not require neither eNB restart. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Descriptions of radio resource management and LTE RL60. The network advertises its support for enhanced 1xCSFB by broadcasting 1xRTT pre- registration and longCodeState1xRTT parameters in the system information (SIB8). In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. e1xCSFB). Expected outcome The LTE1433: LPPa support for OTDOA feature is deactivated.18.18 LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) 4. which is passed on to CDMA upper layer in the UE. d) Set the Activate LPPa support for OTDOA (actLPPaOtdoa) parameter value to false. 2 Deactivate the LTE1433: LPPa support for OTDOA feature. c) Select the LNBTS object. 4. nor cell locking. Registration information is tunneled between the UE and the CDMA2000 1xRTT network over LTE and the S102 interface between LTE and CDMA2000 1xRTT IWS. Table 86 Software requirements System release Flexi Multiradio BTS Flexi Multiradio 10 iOMS BTS RL60 . The EPC must support CS inter-working for mobility management and paging. CS Fallback supports both mobile-originated (MO) and mobile-terminated (MT) voice calls for both active and idle UEs in LTE. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4. Operator benefits CS Fallback mechanism enables the operator to provide voice and other CS services for its LTE end-users without the expense of deploying an IMS core and VoIP applications. DN09185955 Issue: 01J © 2016 Nokia 147 .18. When the operator uses the existing CDMA 1x CS infrastructure. to use the operator's CDMA 1x circuit network for voice and other CS services. LTE RL60.18. 4. the CDMA 1x paging messages are delivered over the LTE air interface.1 Benefits End-user benefits This feature affects the end-user experience as follows: in case of a CS fallback the end- user can use the CDMA circuit network for voice and other CS services.3 Functional description Functional overview 1xRTT CS Fallback function allows the UE. For the UE-terminated calls. For idle UEs. 1xRTT CS Fallback mechanism includes the ability for the UE that is under LTE coverage to pre-register on the CDMA2000 1xRTT network for CS services based on SIB8.18.0 - UE NetAct MME SAE GW 3GPP R8 UE .1.1.1. the CS Fallback mechanism enables the operator to provide voice and other CS services for its LTE end- users without the expense of deploying an IMS core and VoIP applications. 4.2 Requirements Software requirements Software requirements lists the software required for this feature. which is normally camped on the LTE network. . LBTS6. - capabilities Hardware requirements This feature is not supported with FSMD and FSME. these messages are delivered after the UE is located using standard LTE paging. 1xRTT CS Fallback solution for MO/MT voice calls is based on RRC connection release with redirection. This function does not need FGI bit. gpsCtrlBlockForCoLocatedBts is 'False' ) 1xRTT CS Fallback functionality is divided into 3 phases (but only phase 1 is covered by LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB)): 1. ignores restriction list for priority 1xCSFB calls) • Measurement: “report strongest cells” • Support only one target 1x RTT Bandclass for R9 CSFB measurement for one UE (but multiple 1x bandclass/frequencies could be configured per LTE cell) g Note: The LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature supports only a common CDMA1x target neighbor cell list for both normal (that is S1AP CSFB indicator set to "CSFB required" ) and high priority (that is S1AP CSFB indicator is set to "CSFB high priority") R9 e1xCSFB call. UE capabilities are checked if the UE supports enhanced CS fallback to 1xRTT (e-CSFB-1XRTT-r9). MWI.e. • 3GPP Rel-9 e1xCSFB without concurrent PS HO • Fallback to CSFB R8. and other failure/exception handling.e.e. btsSyncMode is 'PhaseSync') and not as the sync hub slave (i. out of sync case. RRC connection release with redirection. coarse LBS. Descriptions of radio resource management and LTE RL60. ignores restriction list for emergency 1xCSFB call) • Priority 1xCSFB calls (that is "CSFB high priority" indicator in S1AP also. In 3GPP R8. which is assumed to be the single radio UE from the eNB point of view. CS fallback to 1xRTT for CS services The network advertises its support for enhanced 1xCSFB by broadcasting 1xRTT pre- registration and longCodeState1xRTT parameters in system information (SIB8). which is passed on to CDMA upper layer in the UE. and so on) transparently without leaving the LTE domain. but it also works for dual receiver (and/or transmitter) UEs. 1xRTT CS Fallback solution for MO/MT voice calls has been enhanced via mobility from LTE with CDMA2000 handover preparation to reduce overall 1x CS Fallback call setup time (compared with R8 1x CSFB solution) and is called e1xCSFB (R9 Enhanced 1xRTT CS Fallback). to support legacy UEs. • MO/MT SMS over S102 (note: independent with 1xCSFB procedure) • Emergency 1xCSFB calls (that is "CSFB high priority" indicator in S1AP. From 3GPP R9 onward. Feature Descriptions and Instructions telecom features CS Fallback supports reception and transmission of CDMA 1x SMS messages and other CDMA 1xRTT native high-layer applications (for example. act1xCsfb is 'true' and rttCsfbType is 'R9e1xCsfb') is ONLY allowed when eNodeB is configured in phase sync mode( i. g Note: R9 e1xCSFB configuration (i. e1xCSFB Phase 1 (within the scope of this feature): • 1xRTT CS pre-registration • MO/MT e1xCSFB with UE in RRC idle/connected state. R8 1xCSFB is a baseline function for the R8 UEs that supports LTE and CDMA2000 1xRTT. This solution is designed for single radio UEs. 148 © 2016 Nokia DN09185955 Issue: 01J . The UE determines whether pre-registration is needed based on 1xRTT pre- registration parameters broadcast in the system information (SIB8). When the eNB receives a CS fallback priority indication from MME in S1AP messages with CS Fallback High Priority. The following scenarios are supported: • mobile originated CSFB with a UE in RRC_IDLE • mobile originated CSFB with a UE in RRC_CONNECTED • mobile terminated CSFB with a UE in RRC_IDLE • mobile terminated CSFB with a UE in RRC_CONNECTED • emergency Calls • priority calls • mobile originating SMS • mobile terminating SMS As a prerequisite. A 1xCSFB capable terminal might pre-register in the 1xRTT network via the E- UTRAN to establish CS services (for example. The eNB forwards the 1xRTT CS paging request to the UE for MT CS fallback. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features On receiving S1AP message (UE Context Modification or Initial UE Context Setup) with CSFB indicator. E- UTRAN sends an S1 UE Context Release Request (Cause: Redirection towards 1xRTT) message to the MME. the eNB sends a Handover From EUTRA Preparation Request message to the UE with an indication that the concurrent HRPD handover preparation is not required. the EPC must support CS inter-working for mobility management and paging. priority call is also taken as emergency call during e1xCSFB procedure). The eNB provides the necessary parameters in the CDMA2000 CSFB Parameters Response message. The management of the pre-registration and re-registration is handled by the 1xRTT upper layer in the UE. This triggers the UE to send UL Handover Preparation Transfer message containing 1xRTT dedicated information for CS fallback. The UE is responsible for maintaining the 1xRTT context. for example by performing re-registrations if needed. DN09185955 Issue: 01J © 2016 Nokia 149 . The MME triggers in all above cases the CS Fallback procedure at the eNB by sending the IE CS FallBack Indicator within the S1AP:UE Context Modification Request or Initial UE Context Request message to the eNB. 2. LTE RL60. 3. the UE requests from the eNB the necessary information to perform the 1xRTT pre-registration using the CDMA2000 CSFB Parameters Request message. 1xRTT CS Pre-Registration 1. MobilityParameters) are O&M pre-configured in the eNB and are transparent to E-UTRAN. After receiving the reportStrongestCell measurement report. the eNB solicits 1xRTT measurements from the UE for e1xCSFB to 1xRTT. The response from the 1xRTT network triggers the eNB to send mobility from EUTRA Command message to the UE with indication that this is for enhanced 1x CS Fallback operation received over the S102 tunnels. otherwise it is handled as a normal call. originating and terminating voice calls) in the 1xRTT network. Without concurrent PS HO enabled. the eNB handles call as Emergency Call (that means. Before performing a 1xRTT pre-registration. The UE retunes to the 1xRTT radio access network and performs 1xchannel acquisition with the 1xRTT CS access. These necessary parameters (RAND. As a result. act1xCsfb is 'true' and rttCsfbType is 'R9e1xCsfb') is ONLY allowed when eNodeB is configured in phase sync mode( i. • LTE736: CS Fallback to UTRAN This feature introduces PS handover-based CS fallback from LTE to UTRAN (WCDMA/TD-SCDMA) for MO and MT call setup. The QuantityConfig parameter has to be set as pilotPnPhaseAndPilotStrength. If no measurement report is received before the timer expiration. R9 enhanced 1x Circuit Switched Fallback (e1xCSFB) will be attempted. The synchronous system time is broadcast together with other SIB8 parameters.18. R9 e1xCSFB is only allowed when SIB8 cdma system time is broadcasted.e. For the UEs that do not support enhanced CS fallback to 1xRTT. R9 e1xCSFB configuration (i.4 System impact Interdependencies between features The following features have dependencies with the LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature: • LTE426: System Time Broadcast for SIB8 This feature introduces the synchronous system time support from the GPS timing. searchWindowSize. This parameter defines the 1xCSFB type which is used in the cell: • If set to forbidden. Activation of the LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature enables this feature automatically. The LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature cannot be activated in parallel with the LTE736: CS Fallback to UTRAN feature.e. the network will use 1xCSFB via RRC connection release with redirection without measurement. In the measurement configuration. The following parameters (CarrierFreq. • If set to R9e1xCsfb. 4. btsSyncMode is 'PhaseSync') and not as the sync hub slave (i.gpsCtrlBlockForCoLocatedBts is 'False') • LTE562: CSFB To UTRAN or GSM via Redirect This feature introduces the CS fallback function. which is only possible when eNodeB is in phase sync mode and GPS time is available. • LTE22: Emergency Call Handling 150 © 2016 Nokia DN09185955 Issue: 01J . Each measurement is guarded by a supervision timer.e.1. The LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature cannot be activated in parallel with the LTE562: CSFB To UTRAN or GSM via Redirect feature. which allows service-based redirection from LTE to UTRAN or to GERAN during the call setup. Descriptions of radio resource management and LTE RL60. The corresponding O&M parameter is rttCsfbType. • If set to R81xCsfbEnforced. Feature Descriptions and Instructions telecom features The eNB solicits an IRAT ReportStrongestCells measurement report from the UE with 1xRTT frequency and transfer to 1xRTT network to assist the target 1xRTT channel assignment for CS fallback to 1xRTT. Both MO and MT call setups are supported. R8 1xCSFB with redirection shall be enforced. The target cell selection is based on the fast measurement solicitation. 1xCSFB is not allowed. physCellId (whitelisting)) in measurement object are O&M-configurable. the redirection will be used for CS fallback to 1xRTT/CDMA. The network forces the UE to use 1xCSFB via RRC connection release with redirection no matter of UE capability. the reportAmount parameter has to be set to 1. The LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature cannot be activated in parallel with the LTE22: Emergency Call Handling feature. Impact on interfaces The following new messages are supported: • the RRC:CSFBParametersRequestCDMA2000 message (between the UE and the eNB) • the RRC:CSFBParametersResponseCDMA2000 message (between the UE and the eNB) • RRC:HandoverFromEUTRAPreparationRequest message (between the UE and the eNodeB) • the RRC:ULHandoverPreparationTransfer message (between the UE and the eNodeB) • the S1AP:DownlinkS1CDMA2000Tunneling message (between the eNB and the MME) • the S1AP:UplinkS1CDMA2000Tunneling message (between the eNB and the MME) The following messages are modified (with a new IE in it): • the RRC:ULInformationTranfer message (between the UE and the eNB) • the RRC:DLInformationTransfer message (between the UE and the eNB) DN09185955 Issue: 01J © 2016 Nokia 151 . based on source cell downlink RSRP measurements (event A2). The LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature reuses the extended csFallBPrio and emerCallPrio introduced by the LTE562: CSFB To UTRAN or GSM via Redirect and the LTE22: Emergency Call Handling features. the LTE487: Idle Mode Mobility Load Balancing round robin algorithm applies to R8 1xCSFB redirection target selection. LTE RL60. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features This feature introduces emergency call handling through CS fallback with redirection procedure to GSM or to WCDMA and RRC connection establishment handling for emergency call. DRX is always disabled during e1xCSFB procedure. which can also be used for measurement during DRX off period. LTE473: Extended DRX Settings. • LTE423: RRC Connection Release with Redirect This feature introduces the redirection functionality enabling the UEs to redirect to other frequency layers in case of poor radio conditions. The functionality of RRC connection establishment handling with cause value "emergency" and CSFB emergency call handling with CSFB indicator "CSFB high priority" are always automatically supported when the LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature is activated. The LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature always uses gap for 1xRTT measurement instead of DRX. but does not make use of redirectPrio of the REDRT MOC. • DRX-related features (LTE42: Support of DRX in RRC Connected Mode. and LTE585: Smart DRX) These features provide DRX configuration. • LTE487: Idle Mode Mobility Load Balancing This feature introduces idle mode mobility load balancing between various LTE carrier frequencies as well as for IRAT scenarios. When both the LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) and the LTE487: Idle Mode Mobility Load Balancing features are activated. The LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature reuses RRC Connection Release with redirection mechanism for some failure cases and R8 1x CSFB. key performance indicator.5 LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) management data For information on alarm. Parameters Table 88: New parameters and list parameters introduced with this feature. Table 87 Related existing counters Counter ID Counter name Measurement M8016C11 CS Fallback attempts with redirection via 8016 - LTE Inter System RRC Connection Release Handover (WBTS) M8016C12 CS Fallback attempts (UE in Connected 8016 - LTE Inter System Mode) with redirection via RRC Connection Handover (WBTS) Release M8016C13 CS Fallback attempts for emergency call 8016 - LTE Inter System reason with redirection via RRC Connection Handover (WBTS) Release M8000C23 UE Context modification attempts 8000 - LTE S1AP (WBTS) M8000C31 UE Context modification attempts due to 8000 - LTE S1AP (WBTS) CS Fallback M8000C25 UE Context modification failures 8000 - LTE S1AP (WBTS) Key performance indicators There are no key performance indicators related to this feature.1. Descriptions of radio resource management and LTE RL60. Measurements and counters The table below lists existing counters related to this feature. see Reference documentation. Feature Descriptions and Instructions telecom features • the RRC: MobilityfromEUTRACommand message (from eNodeB to the UE) • the RRC: RRCConnectionRelease message ( from eNodeB to the UE) Impact on network and network element management tools This feature has no impact on network management or network element management tools. counter. and parameter documents.18. Alarms There are no alarms related to this feature. Impact on system performance and capacity This feature has no impact on system performance or capacity. 4. 152 © 2016 Nokia DN09185955 Issue: 01J . Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 88 New parameters Full name Abbreviated name Managed object Neighbor 1x carrier frequency arfcn LNADJX Neighbor 1x band class bandClass LNADJX Neighbor 1x cell ID cellId LNADJX CDMA2000 1xRTT neighbor lnadjxId LNADJX cell identifier Neighbor 1x market ID marketId LNADJX Neighbor 1x PN offset pnOffset LNADJX Neighbor 1x sector ID sectorId LNADJX Neighbor 1x switch number swNo LNADJX Activate 1xCSFB act1xCsfb LNBTS Random challenge value rand LNCEL CDMA2000 1xRTT CSFB rttCsfbType LNCEL type CDMA2000 1xRTT neighbor lnhoxId LNHOX cell handover identifier Maximum number of rttMaxNumCsfbTargets LNHOX e1xCSFB target cells per frequency CDMA2000 1XRTT search rttSearchWindowSize LNHOX Window size CDMA2000 1xRTT strength rttStrengthThresh LNHOX threshold Neighbor 1x carrier frequency arfcn LNRELX Neighbor 1x band class bandClass LNRELX Neighbor 1x cell ID cellId LNRELX E1xCSFB allowed e1xCsfbAllowed LNRELX CDMA2000 1xRTT neighbor lnrelxId LNRELX relation identifier Neighbor 1x market ID marketId LNRELX DN09185955 Issue: 01J © 2016 Nokia 153 . LTE RL60. Feature Descriptions and Instructions telecom features Table 88 New parameters (Cont.) Full name Abbreviated name Managed object Neighbor 1x PN offset pnOffset LNRELX Neighbor 1x sector ID sectorId LNRELX Neighbor 1x switch number swNo LNRELX CDMA2000 1xRTT auth auth XPARAM mode indicator CDMA2000 1xRTT auth authIncluded XPARAM mode indicator included CDMA2000 1xRTT band bandClass XPARAM class Day light savings time dayLt XPARAM indicator Include day light savings time dayLtIncluded XPARAM indicator FPC FCH INIT SETPT for fpcFchInitSetptRC11 XPARAM RC11 FPC FCH INIT SETPT for fpcFchInitSetptRC12 XPARAM RC12 FPC FCH INIT SETPT for fpcFchInitSetptRC3 XPARAM RC3 FPC FCH INIT SETPT for fpcFchInitSetptRC4 XPARAM RC4 FPC FCH INITSETPT for fpcFchInitSetptRC5 XPARAM RC5 GCSNAL2Ack timer indicator gcsnaL2AckTimer XPARAM GCSNA sequence context gcsnaSequenceContextTimer XPARAM timer indicator CDMA2000 1xRTT home homeRegIncluded XPARAM registration included IMSI 11th and 12th digit imsi11and12 XPARAM IMSI T supported imsiTSupported XPARAM Leap second lpSec XPARAM 154 © 2016 Nokia DN09185955 Issue: 01J . Descriptions of radio resource management and LTE RL60. LTE RL60.) Full name Abbreviated name Managed object Leap seconds included lpSecIncluded XPARAM Local time offset ltmOff XPARAM Local time offset included ltmOffIncluded XPARAM CDMA2000 1xRTT max maxNumAltSo XPARAM number of alt SO Mobile country code mcc XPARAM CDMA2000 1xRTT minimum minPRev XPARAM protocol revision 1x protocol revision pRev XPARAM Pilot increment pilotInc XPARAM Pilot increment included pilotIncIncluded XPARAM Preferred mobile station prefMSIDType XPARAM identifier type CDMA2000 1xRTT mobility xparamId XPARAM parameters identifier Table 89 New parameters Full name Abbreviated name Managed object Structure CDMA2000 rttCarrierFreq LNHOX 1XRTT carrier frequency CDMA2000 rttArfcn LNHOX rttCarrierFreq 1XRTT ARFCN CDMA2000 rttBandClass LNHOX rttCarrierFreq 1XRTT band class CDMA2000 rttPreregRefCellId LNCEL 1xRTT pre- registration reference cell id DN09185955 Issue: 01J © 2016 Nokia 155 . Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 88 New parameters (Cont. ) Full name Abbreviated name Managed object Structure CDMA2000 rttPreregCellId LNCEL rttPreregRefCellId 1xRTT pre- registration cell ID CDMA2000 rttPreregMarketId LNCEL rttPreregRefCellId 1xRTT pre- registration market ID CDMA2000 rttPreregSectorId LNCEL rttPreregRefCellId 1xRTT pre- registration sector ID CDMA2000 rttCellIdInfo LNCEL 1xRTT cell ID info CDMA2000 c2KTimers LNCEL timers CDMA2000 tC2KMeasReport LNCEL c2KTimers 1xRTT measurement report timer CDMA2000 tC2KRelocPrep LNCEL c2KTimers relocation preparation timer CDMA2000 tC2kRelocExec LNCEL c2KTimers relocation execution timer UL Handover tULHOPrepTransfer LNCEL c2KTimers preparation transfer timer CDMA2000 csfbRegParam1xRtt CDFIM 1xRTT CSFB registration parameters CDMA2000 foreignNidReg CDFIM csfbRegParam1xRtt 1xRTT NID roamer registration indicator 156 © 2016 Nokia DN09185955 Issue: 01J . Feature Descriptions and Instructions telecom features Table 89 New parameters (Cont. Descriptions of radio resource management and LTE RL60. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 89 New parameters (Cont. LTE RL60.) Full name Abbreviated name Managed object Structure CDMA2000 foreignSidReg CDFIM csfbRegParam1xRtt 1xRTT SID roamer registration indicator CDMA2000 homeReg CDFIM csfbRegParam1xRtt 1xRTT home registration indicator CDMA2000 multiNid CDFIM csfbRegParam1xRtt 1xRTT multiple NID storage indicator CDMA2000 multiSid CDFIM csfbRegParam1xRtt 1xRTT multiple SID storage indicator CDMA2000 nid CDFIM csfbRegParam1xRtt 1xRTT network identification CDMA2000 paramReg CDFIM csfbRegParam1xRtt 1xRTT parameter- change registration indicator CDMA2000 powerDownReg CDFIM csfbRegParam1xRtt 1xRTT power- down registration indicator CDMA2000 powerUpReg CDFIM csfbRegParam1xRtt 1xRTT power- up registration indicator CDMA2000 regPeriod CDFIM csfbRegParam1xRtt 1xRTT registration period DN09185955 Issue: 01J © 2016 Nokia 157 . Feature Descriptions and Instructions telecom features Table 89 New parameters (Cont. Descriptions of radio resource management and LTE RL60.) Full name Abbreviated name Managed object Structure CDMA2000 regZone CDFIM csfbRegParam1xRtt 1xRTT registration zone CDMA2000 sid CDFIM csfbRegParam1xRtt 1xRTT system identification CDMA2000 totalZone CDFIM csfbRegParam1xRtt 1xRTT number of registration zones CDMA2000 zoneTimer CDFIM csfbRegParam1xRtt 1xRTT zone timer length lists existing parameters related to this feature. Table 90 Related existing parameters Full name Abbreviated name Managed Structure object Activate CS fallback via actCSFBRedir LNBTS redirection Activate CS fallback with PS-HO actCsfbPsHoToUtra LNBTS to UTRA Activate emergency call via actEmerCallRedir LNBTS redirection Redirection priority for CS csFallBPrio REDRT fallback with redirection Redirection priority for emerCallPrio REDRT emergency call CDMA band redirBandCdma REDRT CDMA frequency redirFreqCdma REDRT RAT for redirection redirRat REDRT 158 © 2016 Nokia DN09185955 Issue: 01J . ) Full name Abbreviated name Managed Structure object Redirection target configuration redrtId REDRT identifier CDMA2000 frequency idle mode cdfimId CDFIM configuration identifier System information scheduling sibSchedulingList SIB list SIB type siMessageSibType SIB sibSchedulingL ist Network synchronization mode btsSyncMode BTSSCL GPS control interface blocked for gpsCtrlBlockForCoLocat BTSSCL co-located BTS edBts 4.6 Sales information Table 91 Sales information BSW/ASW License control in network element License control attributes ASW .1. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 90 Related existing parameters (Cont. - 4.2 Activating and configuring LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) Before you start Table 92 Parameters used for activating and configuring LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) Parameter Purpose Requires eNB restart or object locking Activate activation flag no 1xCSFB(act1xCsfb) Activate CS mandatory configuration no fallback via redirection Only if actCSFBRedir is set to (actCSFBRedir) disabled act1xCsfb can be configured to true. LTE RL60. Activate CS mandatory configuration no fallback with PS- HO to DN09185955 Issue: 01J © 2016 Nokia 159 .18.18. CDMA2000 1xRTT mandatory configuration no CSFB regristation parameters This is a structure that contains (csfbRegParam1xRtt) CDMA2000 1xRTT CSFB Registration Parameters CDMA2000 1xRTT mandatory configuration no band class list ( rttBdClList) This is a structure that contains a list of CDMA2000 1xRTT frequency bands System information mandatory configuration no scheduling list (sibSchedulingList) sibSchedulingList must contain a siMessageSibType SIB8 configuration if act1xCsfb set to true (and additionally rttCsfbType not set to forbidden). CDMA2000 1xRTT mandatory configuration no CSFB type(rttCsfbType rttCsfbType must be configured for each LNCEL instance if act1xCsfb is set to true CDMA2000 timers mandatory configuration no (c2KTimers) c2KTimers must be configured if act1xcsfb is set to true (precondition: rttCsfbType is set to R9e1xCsfb) CDMA2000 1xRTT mandatory configuration no cell ID info (rttCellIdInfo) rttCellIdInfo must be configured if act1xcsfb is set to true (precondition: rttCsfbType is set to R9e1xCsfb) Network Mandatory Configuration BTS restart needed synchronization mode(btsSyncMode) 160 © 2016 Nokia DN09185955 Issue: 01J . Descriptions of radio resource management and LTE RL60.) Parameter Purpose Requires eNB restart or object locking UTRA(actCsfbPsHoToU Only if actcsfbPsHoToUtra is tra) set to false act1xCsfb can be configured to true. Activate emergency mandatory configuration no call via redirection Only if actEmerCallRedir is set (actEmerCallRedir to disabled act1xCsfb can be configured to true. Feature Descriptions and Instructions telecom features Table 92 Parameters used for activating and configuring LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) (Cont. 3 Configure the LNADJX for the CDMA2000 1xRTT CSFB type. c) Expand the LNBTS object.) Parameter Purpose Requires eNB restart or object locking GPS control Mandatory configuration BTS restart needed interface blocked for co-located BTS ( gpsCtrlBlockForCoL ocatedBts) The following features need to be deactivated before activation of LTE1441: Enhanced CS Fallback to CDMA/1xRTT: • LTE22: Emergency call handling • LTE562: CSFB to UTRAN or GSM via redirect • LTE736: CS fallback to UTRAN Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. 2 Deactivate the forbidden features for LTE1441: Enhanced CS Fallback to CDMA/1xRTTfeature. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 92 Parameters used for activating and configuring LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) (Cont. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. LTE RL60. b) Expand the MRBTS object. d) Expand the LNADJX objects. a) Go to the Radio Network Configuration page. d) Set the Activate CS fallback via redirection(actCSFBRedir) parameter value to disabled. c) Select the LNBTS object. if there are none create at least on LNADJX instance. e) Set the Activate emergency call via redirection(actEmerCallRedir) parameter value to disabled. a) Go to the Radio Network Configuration page. DN09185955 Issue: 01J © 2016 Nokia 161 . b) Expand the MRBTS object. f) Set the Activate CS fallback with PS-HO to UTRA(actCsfbPsHoToUtra) parameter value to false. Configure the Neighbor PN offset (pnOffset) to an appropriate value. 3. If the CDMA2000 1xRTT CSFB type(rttCsfbType) parameter is set to R9e1xCsfb. Configure the Neighbor 1x cell ID (cellId) to an appropriate value. 4 Configure the CDMA2000 1xRTT CSFB type. the CDMA2000 1xRTT cell ID info(rttCellIdInfo) must be configured to suitable values. the CDMA2000 timers( c2KTimers) must be entered ( if it does not exist) and configured to suitable values. Configure the Neighbor 1x sector ID (sectorId) to an appropriate value. 5. e) Configure the CDMA2000 1xRTT CSFB type (rttCsfbType) for each LNCEL instance with appropiate values. g Note: R9 e1xCSFB configuration (i. Descriptions of radio resource management and LTE RL60. 4. 2. 3. b) Expand the MRBTS object. btsSyncMode is 'PhaseSync') and not as the sync hub slave (i. gpsCtrlBlockForCoLocatedBts is 'False'.e. if there are none create at least one LNCEL instance. Configure the Neighbor 1x band class (bandClass) to an appropriate value. 6. Configure the CDMA2000 1xRTT neighbor cell identifier (lnadjxId) to a appropriate value. 162 © 2016 Nokia DN09185955 Issue: 01J . If the CDMA2000 1xRTT CSFB type(rttCsfbType) parameter is set to R9e1xCsfb. act1xCsfb is 'true' and rttCsfbType is 'R9e1xCsfb') is ONLY allowed when eNodeB is configured in phase sync mode( i. Feature Descriptions and Instructions telecom features 1. Configure the Neighbor 1x market ID (marketId) to an appropriate value.e. select new CDMA2000 timers. c) Expand the LNBTS object. Configure the Neighbor 1x switch number (swNo) to an appropriate value. To enter the CDMA2000 timers press the right mouse button onto the LNCEL instance and. Configure the Neighbor 1x carrier frequency (arfcn) to an appropriate value. 7. 8. If the CDMA2000 1xRTT CSFB type(rttCsfbType) is not set to forbidden the SIB8 must be entered (if it does not exist) and configured in the System information scheduling list (sibSchedulingList). 1. 2. d) Expand the LNCEL objects. a) To create a new System information scheduling list ( sibSchedulingList) go to SIB ► System information scheduling list and select New System Information Schedule List. a) Go to the Radio Network Configuration page.e. d) Set the Number of SI-Message Repetitions (siMessageRepetition(Repetition) to a value between 1.. Configure the CDMA2000 1xRTT neighbor cell handover identifier (inhoxId) to a appropiate value. d) Expand the LNCEL objects. b) Expand the MRBTS object. f) Under the LNHOX object. e) Expand the CDFIM object. 1. if there are none create at least one LNCEL instance. if there are none create at least on LNHOX instance. 4.. 6 Configure the LNHOX for CDMA 1xRTT. Configure the CDMA2000 1xRTT ARFCN (rttArfcn) to a appropiate value.. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features b) Set the System information scheduling list(sibSchedulingList ) SIB Type parameter value to SIB8. 2. LTE RL60. expand the CDMA2000 1xRTT carrier frequency-1 list. e) Expand the LNHOX object. 3. To configure the CDMA2000 1xRTT CSFB registration parameters (csfbRegParam1xRtt ) press the right button onto the CDFIM instance and select New CDMA2000 1xRTT CSFB registration parameters. Configure the CDMA search window size (searchWinSize ) to a value between 0 . Provide the parameters with appropriate values. Configure the CDMA2000 1xRTT strength threshold (rttStrengthThresh) to a appropiate value. 1. a) Go to the Radio Network Configuration page. 3. 15. Configure the Maximum number of e1xCSFB target cells per frequency (rttMaxNumCsfbTargets) to a appropiate value.4 5 Configure the CDFIM for CDMA2000 1xRTT. c) Expand the LNBTS object. c) Expand the LNBTS object. Configure the CDMA2000 1xRTT search Window size (rttSearchWindowSize) to a appropiate value. 2. a) Go to the Radio Network Configuration page. if there are none create at least one CDFIM instance. Configure the CDMA2000 frequency idle mode configuration identifier ( cdfimId ) with an appropriate value. d) Expand the LNCEL objects. 1. b) Expand the MRBTS object. DN09185955 Issue: 01J © 2016 Nokia 163 . c) Set the Periodicity of the SI-message (siMessagePeriodicity(Periodicity))parameter to a value between 80ms and 5120 ms. if there are none create at least one LNRELX instance. e) Expand the LNRELX object. Configure the E1xCSFB allowed (e1xCsfbAllowed) to an appropriate value. 8. d) Set the Activate 1xCSFB(act1xCsfb) parameter value to true. 1. 5. Expand the LNCEL objects. 8 Activate the LTE1441: Enhanced CS Fallback to CDMA/1xRTT. 2. Expand the MRBTS object. 164 © 2016 Nokia DN09185955 Issue: 01J . Configure the CDMA2000 1XRTT neighbor relation identifier ( lnrelxId ) to an appropriate value. b) Expand the MRBTS object. c) Expand the LNBTS object. Configure the Neighbor 1x market ID (marketId) to an appropriate value. 1. 2. Feature Descriptions and Instructions telecom features 2. 6. 7 Configure the LNRELX for CDMA2000 1xRTT a) Go to the Radio Network Configuration page. Configure the Neighbor 1x PN offset (pnOffset) to an appropriate value. 7. if there are none create at least one XPARAM instance. e) Add XPARAM instance. Expand the XPARAM object. 3. Configure the CDMA2000 1xRTT band class (rttBandClass) to a appropiate value. Descriptions of radio resource management and LTE RL60. a) Go to the Radio Network Configuration page. Configure the XPARAM for CDMA 1xRTT. 6. Go to the Radio Network Configuration page. Configure the Neighbor 1x cellId (cellId) to an appropriate value. Expand the LNBTS object. d) Expand the LNCEL objects. Configure the Neighbor 1x carrier frequency (arfcn) to an appropriate value. Configure the Neighbor 1x band class (bandClass) to an appropriate value. Configure the Neighbor 1x switch number (swNo) to an appropriate value. b) Expand the MRBTS object. 5. Configure the Neighbor 1x sector ID (sectorId) to an appropriate value. 4. 3. c) Expand the LNBTS object. 9. 4. 5. 2. Expand the REDRT object. f) Add REDRT instance. g) Configure all other REDRT parameters to appropriate values. then right click to add New CDMA2000 1xRTT pre- registration reference cell id. Go to the Radio Network Configuration page. f) Configure the Redirection priority for emergency call (emerCallPrio) to a appropriate value. 4. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features a) Configure the CDMA2000 1XRTT mobility parameters identifier ( xparamId ) to a appropriate value. Expand the LNBTS object. g) Add RAND value 1. Expand the LNBTS object. 2. 1. Configure the Random challenge value (rand) to a appropriate value. 5. 3. c) Configure the CDMA frequency (redirFreqCdma) to a appropriate value. Expand the LNBTS object. Expand the LNCEL objects. . 3. DN09185955 Issue: 01J © 2016 Nokia 165 . Expand the MRBTS object. 4. Configure the for CDMA 1xRTT Pre-registration Cell Id instance. e) Configure the Redirection priority for CS fallback with redirection (csFallBPrio) to a appropriate value. Configure the REDRT for CDMA 1xRTT. 2. Go to the Radio Network Configuration page. Expand the MRBTS object. d) Configure the RAT for redirection (redirRAT) to a appropriate value. b) Configure the CDMA2000 1XRTT band class identifier (bandClass) to a appropriate value. c) Configure the Mobile country code (mcc) to a appropriate value. 5. Click on LNCEL. a) Configure the Redirection target configuration identifier (redrtId) to a appropriate value. Expand the MRBTS object. Expand the LNCEL objects. b) Configure the CDMA band (redirBandCdma) to a appropriate value. if there are none create at least one REDRT instance. 4. 3. h) Add Pre-registration list 1. LTE RL60. Configure the LNRELX for CDMA 1xRTT. 6. d) Configure all other XPARAM parameters to appropriate values. Go to the Radio Network Configuration page. 6. c) Select the LNBTS object. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. b) Configure the CDMA2000 1xRTT pre-registration market ID ( rttPreregMarketID ) to a appropriate value. d) Configure the CDMA2000 1xRTT pre-registration switch number ( rttPreregSwNo ) to a appropriate value. d) Set the Activate 1xCSFB (act1xCsfb) parameter value to false. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. 4. 2 Deactivate the feature: LTE1441: Enhanced CS fallback to CDMA/1xRTT (e1CSFB).3 Deactivating of LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. 9 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. c) Configure the CDMA2000 1xRTT pre-registration sector ID ( rttPreregSectorID ) to a appropriate value.19. This step deactivates the feature. 4. a) Go to the Radio Network Configuration page b) Expand the MRBTS object.1 Description of LTE1495: Fast uplink link adaptation Introduction to the feature 166 © 2016 Nokia DN09185955 Issue: 01J . Feature Descriptions and Instructions telecom features a) Configure the CDMA2000 1xRTT pre-registration cell ID ( rttPreregCellID ) to a appropriate value.18. Descriptions of radio resource management and LTE RL60.19 LTE1495: Fast uplink link adaptation 4. 1.1.19.0 - UE NetAct MME SAE GW 3GPP R8 mandatory NetAct8 EP1 . such as handover and call setup: fast MCS ramp-up starting from the (low) initial MCS • during normal operation: link adaptation is able to better follow the varying radio conditions 4. Table 93 Software requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 LBTS6. DN09185955 Issue: 01J © 2016 Nokia 167 .1 Benefits End-user benefits This feature improves the peak data rate and coverage reliability by the adaptation of transmission settings of the MCS and the physical resource block (PRB) according to radio channel conditions. - Hardware requirements This feature requires no new or additional hardware.19. – The UL ATB is used for defining the maximum number of PRBs that can be assigned to a particular UE by the UL scheduler (UEs with power limitations will be assigned with lesser number of PRBs). which is enabled/disabled per cell.19.3 Functional description The following describes the LTE1495: Fast uplink link adaptation feature: • This feature consists of adaptive modulation and coding (AMC) scheme and adaptive transmission bandwidth (ATB): – The UL AMC scheme selects appropriate MCS for UL transmission according to actual transmission reliability and block error ratio (BLER). LTE RL60.2 Requirements Software requirements Table 93: Software requirements lists the software required for this feature. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features The LTE1495: Fast uplink link adaptation feature improves the uplink performance with a faster link adaptation by immediately selecting the appropriate modulation and coding scheme (MCS). 4.1.0 LBTS6. Operator benefits This feature improves cell average and cell edge throughput: • after events. 4. • This feature is for the physical uplink shared channel (PUSCH). • This feature is a new option besides the previous link adaptation methods like the LTE1034: Extended uplink link adaptation feature. appropriate adaptation has been introduced in order to trigger the switch to and from the TTI-bundling. which is derived from the regular PUSCH transmission. • LTE1336: Interference Aware Close loop Power Control: It is recommended that the LTE1495: Fast uplink link adaptation working pace is faster than the closed-loop power control pace in general. The default configurations by the LTE1336: Interference Aware Close loop Power Control and LTE1495: Fast uplink link adaptation features ensure that the closed-loop power control works according to the above recommendation. 4.4 System impact Interdependencies between features This feature depends on the following features: • LTE27: Open loop UL power control and DL power setting: The Open loop power control settings defined in this function affects the level of signal in the cell and the level of interference in the other cells. Impact on system performance and capacity This feature has the following impact on system performance: • throughput A positive throughput impact is basically expected: – After events such as handover and call setup due to fast MCS ramp-up starting from the (low) initial MCS. Impact on interfaces This feature has no impact on interfaces. • This feature immediately selects appropriate MCS in one step performing a much faster adaptation when compared to step-wise methods (as in LTE1034: Extended uplink link adaptation).19. the MAX_NUM_PRB and allocated MCS vary rapidly. Descriptions of radio resource management and LTE RL60. such as demodulation reference signal (DMRS). Impact on network and network element management tools This feature has no impact on network management or network element management tools. This feature is affected by the following features: • LTE907: TTI Bundling: UEs in TTI bundling mode are handled by its own link adaptation mechanism. and is considered as an optional feature that needs to be monitored by the software asset monitoring (SWAM) client. • LTE46: Channel- aware Scheduler (UL): The SRS can be activated independently from the activation of this feature. Since in the LTE1495: Fast uplink link adaptation. • This feature uses channel state information (CSI). The setting related to open loop power control affects the SINR level and the LTE1495: Fast uplink link adaptation feature. 168 © 2016 Nokia DN09185955 Issue: 01J . It is up to the operators to modify the parameter settings of any of the features to implement the recommendations. Feature Descriptions and Instructions telecom features • This feature may use sounding reference signal (SRS) information either mandatorily or optionally depending on the scheduler configuration. • LTE559: SW monitoring Module for LTE: The LTE1495: Fast uplink link adaptation feature is an ASW feature.1. • LTE28: Closed loop UL power control: It is recommended not to use the closed-loop power control together with the fast UL link adaptation. and parameter documents.19. • latency/quality – Faster link adaptation is expected after handover and call setup. counter. link adaptation is able to better follow the varying radio conditions. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features – During normal operation. RAN View LTE_5119a E-UTRAN E-RAB Drop Ratio. Alarms There are no alarms related to this feature. User Perspective DN09185955 Issue: 01J © 2016 Nokia 169 . see Reference documentation.1.5 LTE1495: Fast uplink link adaptation management data For information on alarm. Table 94 Related existing counters Counter ID Counter name Measurement M8005C140 UL AMC upgrades LTE Power and Quality UL M8005C141 UL AMC downgrades LTE Power and Quality UL M8007C5 Number of released Data Radio LTE Radio Bearer Bearers due to Lost Radio Connection M8007C6 Number of released Data Radio LTE Radio Bearer Bearers due to Other Reasons M8006C12 Released E-RABs due to Radio LTE EPS Bearer Link Failure initiated by eNB M8006C13 eNB initiated EPS Bearer Release LTE EPS Bearer requests due to Other causes M8006C8 EPC initiated EPS Bearer LTE EPS Bearer Release requests due to Radio Network Layer cause M8006C9 EPC initiated EPS Bearer LTE EPS Bearer Release requests due to Other causes Key performance indicators Table 95: Related existing key performance indicators lists the existing key performance indicators related to this feature. Table 95 Related existing key performance indicators KPI ID KPI name LTE_5004a E-UTRAN Radio Bearer Drop Ratio LTE_5119a E-UTRAN E-RAB Drop Ratio. 4. – Lower call drop rate is expected under impaired radio frequency (RF) conditions. Measurements and counters Table 94: Related existing counters lists existing counters related to this feature. key performance indicator. LTE RL60. Table 97 Modified parameters Full name Abbreviated name Managed object Activate uplink link adaptation actUlLnkAdp LNCEL SRS Configuration srsConfiguration LNCEL Table 98: Related existing parameters lists existing parameters related to this feature.19. Descriptions of radio resource management and LTE RL60. Table 98 Related existing parameters Full name Abbreviated name Managed object Power offset for SRS transmission srsPwrOffset LNCEL power calculation Periodic PHR timer tPeriodicPhr LNCEL Enabled TB size impact to UE deltaTfEnabled LNCEL PUSCH power calculation Uplink channel bandwidth ulChBw LNCEL Scheduling method of the UL ulsSchedMethod LNCEL scheduler Initial amount of PRBs in uplink iniPrbsUl LNCEL Initial MCS in uplink iniMcsUl LNCEL Minimum PRB allocation for UEs ulsMinRbPerUe LNCEL which are power limited Extended uplink link adaptation low eUlLaLowPrbThr LNCEL PRB threshold Extended uplink link adaptation low eUlLaLowMcsThr LNCEL MCS threshold UL AMC target BLER ulTargetBler LNCEL 4.1. Feature Descriptions and Instructions telecom features Parameters Table 96: New parameter lists parameter introduced with this feature. Table 96 New parameter Full name Abbreviated name Managed object Fast uplink link ATB trigger fUlLAAtbTrigThr LNCEL threshold Table 97: Modified parameters lists parameters modified by this feature.6 Sales information Table 99 Sales information BSW/ASW License control in network Activated by default element ASW SW Asset Monitoring No 170 © 2016 Nokia DN09185955 Issue: 01J . LTE RL60.2 Activating and configuring LTE1495: Fast uplink link adaptation Before you start Restart of the eNB is required when changes are applied to the following parameters: • SRS Configuration (srsConfiguration) • Scheduling method of the UL scheduler (ulsSchedMethod) Modification of the following parameters requires object locking: • SRS Configuration (srsConfiguration) • Scheduling method of the UL scheduler (ulsSchedMethod) Table 100 Parameters used for activating and configuring LTE1495: Fast uplink link adaptation Parameter Purpose Requires eNB restart or object locking Activate uplink link Activation flag No adaptation (actUlLnkAdp) Fast uplink link ATB Mandatory configuration No trigger threshold (fUlLAAtbTrigThr) Scheduling method of the Optional configuration eNB restart/object locking UL scheduler (ulsSchedMethod) SRS Configuration Mandatory/optional configuration Object locking/eNB restart (srsConfiguration) Power offset for SRS Mandatory configuration No transmission power calculation (srsPwrOffset) Periodic PHR timer Optional configuration No (PeriodicPhr) Enabled TB size impact Mandatory configuration No to UE PUSCH power calculation (deltaTfEnabled) Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. DN09185955 Issue: 01J © 2016 Nokia 171 .19. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4. perform the steps described in this procedure. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. it is automatically off. a) Go to the Radio Network Configuration page. g Note: This action is mandatory if Activate uplink link adaptation (actUlLnkAdp) parameter is set to fUlLa. set the value for Fast uplink link ATB trigger threshold (fUlLAAtbTrigThr) parameter. 4 (Optional) Configure the Scheduling method of the UL scheduler (ulsSchedMethod) parameter. d) Select the LNCEL object corresponding to the cell where the LTE1495: Fast uplink link adaptation feature will be activated. it is recommended to enable mixedFD method even with channel unaware scheduling to provide a higher throughput performance. If this parameter is set to channel aware or interference aware. Descriptions of radio resource management and LTE RL60. The default value of this parameter is -2. Feature Descriptions and Instructions telecom features 2 Set the activation value. set the value for Scheduling method of the UL scheduler (ulsSchedMethod) parameter to either: • channel unaware • channel aware • interference aware g Note: • The default value of this parameter is channel unaware. On the selected LNCEL object. c) Expand the LNBTS object. When no value is set (empty). e) Set the Activate uplink link adaptation (actUlLnkAdp) parameter value to fUlLa. 172 © 2016 Nokia DN09185955 Issue: 01J . 3 Configure the Fast uplink link ATB trigger threshold (fUlLAAtbTrigThr) parameter. On the selected LNCEL object. • Although ExhaustiveFD is the default setting and is accepted if channel unaware scheduling method is used. 5 Configure the SRS Configuration (srsConfiguration) parameter. the UL scheduler FD type (ulsFdPrbAssignAlg) parameter (requires object locking) must be set to MixedFD. On the selected LNCEL object. b) Expand the MRBTS object. g Note: This parameter activates the feature. set the value (1 to 8) for SRS Configuration (srsConfiguration) parameter. On the selected LNCEL object. DN09185955 Issue: 01J © 2016 Nokia 173 . g Note: The default value of this parameter is false. 7 (Optional) Configure the Periodic PHR timer (tPeriodicPhr) parameter. the Activate uplink link adaptation (actUlLnkAdp) parameter is set to fUlLa. This action is mandatory if: • The Scheduling method of the UL scheduler (ulsSchedMethod) parameter is set to channel aware. LTE RL60. set the value for Periodic PHR timer (tPeriodicPhr) parameter. and SRS Configuration (srsConfiguration) parameter is set. set the value for Enabled TB size impact to UE PUSCH power calculation (deltaTfEnabled) parameter to false. g Note: The default value of this parameter is 7. On the selected LNCEL object. • The Scheduling method of the UL scheduler (ulsSchedMethod) parameter is set to channel unaware or interference aware. • The Activate uplink link adaptation (actUlLnkAdp) is set to eUlLa or fUlLa. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features g Note: This action is: • Mandatory if Scheduling method of the UL scheduler (ulsSchedMethod) parameter is set to channel aware. 6 Configure the Power offset for SRS transmission power calculation (srsPwrOffset) parameter. On the selected LNCEL object. 8 Configure the Enabled TB size impact to UE PUSCH power calculation (deltaTfEnabled) parameter. g Note: This action cannot be set to infinity if Activate uplink link adaptation (actUlLnkAdp) parameter is set to fUlLa. set the value for Power offset for SRS transmission power calculation (srsPwrOffset) parameter. The default value of this parameter is 20sf. This action must be configured to false if at least one of the following conditions is fulfilled: • The Method for UL power control (actUlpcMethod) parameter is set to PuschIAwPucchCL or PuschIAwPucchOL. • Optional if Scheduling method of the UL scheduler (ulsSchedMethod) parameter is set to channel unaware or interference aware and the Activate uplink link adaptation (actUlLnkAdp) parameter is set to fUlLa. 20. a) Go to the Radio Network Configuration page.19. Descriptions of radio resource management and LTE RL60. 4.20 LTE1531: Inter-frequency Load Balancing Extension 4. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. e) Set the Activate uplink link adaptation (actUlLnkAdp) parameter to any value other than fUlLa. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. Feature Descriptions and Instructions telecom features 9 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. c) Expand the LNBTS object. Expected Outcome The LTE1495: Fast uplink link adaptation feature is deactivated in the cell. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.3 Deactivating LTE1495: Fast uplink link adaptation Before you start The Activate uplink link adaptation (actUlLnkAdp) parameter is used for deactivation. Expected Outcome The LTE1495: Fast uplink link adaptation feature is activated in the cell. Modification of this parameter does not require neither eNB restart nor cell locking. 4.1 Description of LTE1531: Inter-frequency Load Balancing Extension Introduction to the feature 174 © 2016 Nokia DN09185955 Issue: 01J . 2 Set the Activate uplink link adaptation (actUlLnkAdp) parameter. d) Select the LNCEL object corresponding to the cell where the LTE1495: Fast uplink link adaptation feature will be deactivated. b) Expand the MRBTS object. 3 Functional description The feature introduces the following extensions for LTE1387: Intra eNodeB inter- frequency LB and/or LTE1170: Inter-frequency load balancing: • A periodic retry of load balancing for RRC-connected users is applied in the following cases: – the load balancing handover was not successful – the load balancing handover preparation was not successful or the UE did not provide an A4 measurement report DN09185955 Issue: 01J © 2016 Nokia 175 . 4. Therefore.20. the end user gets higher quality of his calls and lesser call failure rate. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features The LTE1531: Inter-frequency Load Balancing Extension feature increases the scope of the UEs considered for load balancing.1.1. • The UEs entering a cell via a handover are also considered for inter-frequency load balancing. The feature improves the LTE1387: Intra eNodeB inter-frequency LB and/or LTE1170: Inter-frequency load balancing features with the following extensions: • A periodic retry of load balancing for RRC connected users is applied to all UEs. - NetAct 15.2 for RL70 Hardware requirements This feature requires no new or additional hardware.20. Table 101 Software requirements System release Flexi Multiradio BTS Flexi Multiradio OMS 10 BTS RL60 LBTS6. LTE RL60.0 LBTS6.0 - The functionalities are valid for RL70.20.2 Requirements Software requirements Table 101: Software requirements lists software required for this feature. 4.1. Operator benefits Increasing the likelihood for off-loading a cell because of the increased number of the UEs considered for load balancing 4.1 Benefits End-user benefits The load is better deployed over the network. UE NetAct MME SAE GW 3GPP R8 mandatory NetAct8 EP1 . The UEs enter a cell via the handover are considered as well for inter-frequency load balancing. Impact on network and network element management tools This feature has no impact on network management or network element management tools.1. Impact on system performance and capacity This feature has no impact on system performance or capacity. Measurements and counters There are no measurements and counters related to this feature.4 System impact Interdependencies between features This feature is enabled together with the following: • LTE1387: Intra eNodeB Inter-frequency LB • LTE1170: Inter-frequency Load Balancing Impact on interfaces This feature has no impact on interfaces.20.5 Management data Alarms There are no alarms related to this feature. 4.20. The eNB supports inter-frequency Load Balancing algorithm for all RCC: Connected UEs and for all UEs entering a cell via handover. 4. Descriptions of radio resource management and LTE RL60. Key performance indicators There are no key performance indicators related to this feature.1. If the maximum number of the UEs with A4 are activated. 176 © 2016 Nokia DN09185955 Issue: 01J . On retry timer expiration the same actions are triggered when on bearer check timer expiration. Retry Timer The Inter Freq Load Bal Retry Timer (iFLBRetryTimer) timer is assigned to all active UEs to trigger a cyclic re-check if they can be Inter-frequency load balancing candidates. the retry timer is re- /started without further action. • The retries are performed as long as the source cell is at high load. Feature Descriptions and Instructions telecom features – the UE had already been in active state when the high load state was entered g Note: After re-establishment the ifLbBearerchecktimer parameter is applied. followed by the retry timer when there was no handover. The configured retry timer value becomes dynamically adapted to the number of active UEs. The retry timer is operator-configurable. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Parameters Table 102: New parameters lists parameters introduced with this feature. Table 102 New parameters Name Abbreviation Managed Object Structure Inter Freq Load Bal iFLBRetryTimer LNCEL iFLBLoadThresholds Retry Timer Table 103: Related parameters lists the existing parameters related with the feature. LTE RL60. common load settings Cell capacity class cellCapClass LNCEL loadSettings value Mode for calculating mlbEicicOperMode LNCEL loadSettings the CAC in load bal. loadSettings LNCEL load bal. and eICIC Nominal number of nomNumPrbNonGbr LNCEL loadSettings PRBs for load balancing DL GBR resource targetLoadGbrDl LNCEL loadSettings target load DL non-GBR resource targetLoadNonGbr LNCEL loadSettings target load Dl PDCCH target load targetLoadPdcch LNCEL loadSettings DN09185955 Issue: 01J © 2016 Nokia 177 . Table 103 Related parameters Name Abbreviation Managed Object Structure Inter-frequency load iFLBLoadThreshol LNCEL balancing load ds thresholds Inter-frequency load iFLBBearCheckTim LNCEL iFLBLoadThresholds balancing QCI1 er Bearer check timer Inter-frequency load iFLBHighLoadGBRD LNCEL iFLBLoadThresholds balancing GBR high L load DL Inter-frequency load iFLBHighLoadNonG LNCEL iFLBLoadThresholds balancing non-GBR BRDL high load DL Inter-frequency load iFLBHighLoadPdcc LNCEL iFLBLoadThresholds balancing PDCCH h high load Intra- and inter-freq. No 4. the LTE55: Inter-frequency handover feature has to be activated. and the LTE1531: Inter-frequency Load Balancing Extension features. g Note: After activation of the LTE1531: Inter-frequency Load Balancing Extension feature.6 Sales information Table 104 Sales information BSW/ASW License control in License control Activated by default network element attributes ASW .20. • for each LNHOIF object. mandatory configuration no freq. Verify that • inter-frequency layers are added and properly configured (the LNHOIF object).20.1. Before activation of the LTE1531: Inter-frequency Load Balancing Extension feature. The LTE1531: Inter-frequency Load Balancing Extension feature is beneficial only if there are two or more overlapping (at least partially) frequency layers. the LNHOIF objects have to be configured.and inter. the RSRP (thresholdRsrpIFLBFilter) and/or the RSRQ (thresholdRsrqIFLBFilter) thresholds are configured. Feature Descriptions and Instructions telecom features 4. the LTE1170: Inter eNode B IF Load Balancing. Descriptions of radio resource management and LTE RL60. common load settings (loadSettings) parameter structure The LTE1387: Intra-eNode B IF Load Balancing feature parameter Activation of inter frequency load balancing (iFLB) (actInterFreqLB) activates/deactivates the LTE1387: Intra-eNode B IF Load Balancing. load bal. .2 Activating LTE1531: Inter-frequency Load Balancing Extension Before you start Table 105 Parameters used for activating and configuring LTE1531: Inter-frequency Load Balancing Extension Parameter Purpose Requires eNB restart or object locking Activation of activation flag no inter frequency load balancing (iFLB) (actInterFreqLB) Inter-frequency mandatory configuration no load balancing load thresholds (iFLBLoadThreshold s) parameter structure Intra. 178 © 2016 Nokia DN09185955 Issue: 01J . LTE RL60. perform the steps described in this procedure. set the parameter values for: 1.and inter-freq. the Inter-frequency load balancing load thresholds (iFLBLoadThresholds) structure remains in the configuration. 3 Configure Inter-frequency load balancing load thresholds. a) Go to the Radio Network Configuration page. DN09185955 Issue: 01J © 2016 Nokia 179 . Inter-frequency load balancing GBR high load DL (iFLBHighLoadGBRDL) 3. common load settings. b) Select the New Intra. Inter Freq Load Bal Retry Timer ( iFLBRetryTimer) 2. b) Right-click LNCEL object. Inter-frequency load balancing QCI1 Bearer check timer (iFLBBearCheckTimer) 4 Configure the Intra. c) Select the New Inter-frequency load balancing load thresholds structure.and inter-freq. c) Select the LNBTS object. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. load bal. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. load bal. Inter-frequency load balancing non-GBR high load DL (iFLBHighLoadNonGBRDL) 4. a) Expand the LNBTS object. d) For the Inter-frequency load balancing load thresholds (iFLBLoadThresholds) structure. a) Right-click the LNCEL object. g Note: When the LTE1531: Inter-frequency Load Balancing Extension feature is deactivated and activated again. common load settings structure. d) Set the Activation of inter frequency load balancing (iFLB) (actinterFreqLB) parameter value to true. b) Expand the MRBTS object. 2 Activate the feature. Inter-frequency load balancing PDCCH high load (iFLBHighLoadPdcch) 5. c) Set the Activation of inter-frequency load balancing (iFLB) (actinterFreqLB) parameter value to false. 2 Go to the Radio Network Configuration page. a) Expand the MRBTS object. Cell capacity class value (cellCapClass) 2. Uplink CAC source selection (ulCacSelection) 5 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. common load settings (loadSettings) structure. load bal. perform the steps described in this procedure. Mode for calculating the CAC in load bal. Descriptions of radio resource management and LTE RL60. 180 © 2016 Nokia DN09185955 Issue: 01J . nor cell locking. load bal. Static CAC for uplink (ulStaticCac) 8. Feature Descriptions and Instructions telecom features g Note: When the LTE1531: Inter-frequency Load Balancing Extension feature is deactivated and activated again. b) Select the LNBTS object. set the parameter values for: 1. Modification of this parameter does not require neither eNB restart. common load settings (loadSettings) structure remains in the configuration. c) For the Intra. Nominal number of PRBs for load balancing (nomNumPrbNonGbr) 6. PDCCH target load (targetLoadPdcch) 7.and inter-freq. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure.20. 4.3 Deactivating LTE1531: Inter-frequency Load Balancing Extension Before you start The Activation of inter frequency load balancing (iFLB) (actInterFreqLB) parameter is used for deactivation. and eICIC (mlbEicicOperMode) 5.and inter-freq. the Intra. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. DL GBR resource target load (targetLoadGbrDl) 3. DL non-GBR resource target load (targetLoadNonGbrDl) 4. 1 Description of LTE1534: Multiple Frequency Band Indicator Introduction to the feature The LTE1534: Multiple Frequency Band Indicator feature introduces Intra-LTE MFBI functionality. the native band and the mapped band have the following meanings: • The native band - is the operating band of the cell. 4. and which would otherwise be not able to access the network.0 LBTS6.1. Operator benefits This feature allows the operator to handle UEs with overlapping bands in one network.21. 4. 4. Hardware requirements This feature requires no new or additional hardware.1. 4.2 Requirements Software requirements Table 106: Software requirements lists software required for this feature. The frequency band indicator of the native band is included in the broadcast of the SIB1. The mapped band is (at least partly) overlapping the native band. Table 106 Software requirements System release Flexi Multiradio BTS Flexi Multiradio OMS 10 BTS RL60 LBTS6. The physical frequency of the cell is located within the defined boarders. The frequency indicator of the mapped band is included in the MultibandInfoList broadcast of the SIB1.21 LTE1534: Multiple Frequency Band Indicator 4. • The mapped band - is a different band than the native band.1. which support certain frequency bands.0 - UE NetAct MME SAE GW 3GPP R8 UE capabilities1 NetAct8 EP1 .3 Functional description In the document. DN09185955 Issue: 01J © 2016 Nokia 181 . - 1 - the UE must support the Feature Group Indicator (FGI) bit 31.21. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Expected outcome This step deactivates the feature.1 Benefits End-user benefits This feature allows the users to access the network using handsets. LTE RL60.21.21. Such UEs are treated as the UEs supporting the native band. the operator can define an additional mapped band. Also a UE- associated signaling between peer eNB applies mapped EARFCN. the eNB's functionality is extended to serve also the UEs. • Multiple native EARFCN/mapped band pairs are supported within a network. intra-frequency handover. identified by native E-UTRA absolute radio frequency channel number (EARFCN). the content of the SIB1. the following assumptions apply: • Only one mapped band is supported per native EARFCN within a network. • Each native EARFCN/mapped band configuration is the same across the network. Feature Descriptions and Instructions telecom features The Flexi Multiradio BTS supports Multiple Frequency Band Indicators (MFBIs) for UEs in RRC IDLE and UEs in RRC CONNECTED mode. and indicate that they support MFBI (provided they support the Feature Group Indicator (FGI) bit 31. Functionalities in MFBI support • For the support of Idle mode mobility. UEs supporting MFBI and an overlapping RF band in the RF parameter information element of the UE capabilities are considered for the following functions (if enabled): – RRC connected mobility (inter-frequency handover. as well as intra- and inter-frequency LTE neighbor cells. 2. For every LTE frequency within the network. Each native band supported by the network can be configured to support a maximum of one additional band which overlaps the frequency range of the native band. intra- and inter-frequency cell reselection. The eNB accepts UEs also if they do not support the native band. RRC connection release with redirect and RRC connection release with dedicated priorities) – ANR (intra-frequency ANR. Mapped bands The LTE1534: Multiple Frequency Band Indicator feature allows the eNB to serve the UE not supporting the native band in which the eNB is operating. but supporting the same physical frequency via another band called mapped band. the eNB functionality is enhanced to: • broadcast MultiBandInfoList in System Information Block (SIB) 1. To serve the UE not supporting the native bands. • If multiple native EARFCNs are located within a common band. which do not support the native EARFCN of the eNB's cells. The eNB translates the native EARFCN to a mapped EARFCN while communicating with the UE. they might use different mapped bands (although the difference is not mandatory). inter-frequency ANR) – Carrier Aggregation Multiple Frequency Band Indicator Profile (MFBIPR) 182 © 2016 Nokia DN09185955 Issue: 01J . and 5 is extended to support the UE for intra-LTE. but support a mapped band. The UEs are informed which mapped bands are supported by broadcasting cell. as indicated in the Requirements section). The same MFBI configuration is applied to all eNBs. All MFBI-related parameters are configured via O&M. SIB2 and SIB5 • accept mapped bands when checking UE Capabilities • use mapped EARFCN instead of native EARFCN in any communication with the UE or peer eNB Additionally. Descriptions of radio resource management and LTE RL60. • For the support of RRC-connected UE. • LTE423: RRC Connection Release with Redirect The eNB considers EUTRAN redirection targets if the UE supports their mapped band. • LTE53: Intra and inter eNB handover with X2 Mapped EARFCN is used in communication with a UE and between the eNBs. The eNB configures EUTRAN frequencies for inter-frequency measurements if the UE supports their mapped band. the fault is raised. whose physical frequencies overlap with the band the DL- EARFCN belongs to. when the UE uses mapped EARFCN. SIB 2. DN09185955 Issue: 01J © 2016 Nokia 183 . The fault is related to the 7652: BASE STATION NOTIFICATION alarm. the neighbor cell has configured a band as native band which is configured as mapped band in the own eNB). • LTE54: S1-based Handover Mapped EARFCN is used in communication with a UE and between the eNBs. Mapped EARFCN is used in communication with the UE and between the eNBs. LTE RL60. Each instance of the MOC defines a mapping between a downlink (DL)-EARFCN and an additional frequency band.21. which support an overlapping physical frequency range. to which the EARFCN of the measurement object can be mapped . • LTE490: Subscriber Profile ID Selective Neighbour Cell List Only native EARFCN is used in mobility profiles. The alarm is related to the LNADJ object. Additional information When the neighbor cell configuration conflicts with homogeneous MFBI deployment (instead of homogeneous configuration of native band and mapped band. • LTE55: Interfrequency HO The selection of inter-frequency handover targets is extended. when needed for external communication or UE capability check. an entry is considered as valid if it relates to a mapped EARFCN. • LTE039: System Information Broadcast Content of SIB 1. but indicate a different band than broadcasted in SIB1. The mapping information is used by the eNB to serve the UEs. which enables the eNB to derive mapped band and mapped EARFCN. Mapped EARFCN is used for communication with the UE. • LTE487: Idle Mode Load Balancing The eNB considers mapped bands when evaluating UE capabilities for selecting dedicated cell re-selection priorities.4 System impact Interdependencies between features Affected features • LTE37: Ciphering The eNB uses mapped EARFCN as input to calculate ciphering keys. 4. and SIB 5 is extended by MFBI-specific IE. However.1. • LTE971: Intra-LTE Mobility Offsets The measurement objects for mapped EARFCN include all CIO values stored in neighbor relations towards cells with the native EARFCN. whenever evaluating mobility profiles. Mapped EARFCN is used in communication with the UE. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features The MFBIPR managed object class (MOC) is introduced to define the combinations of the native EARFCN and mapped band. • LTE1014: X2 eNodeB configuration update The eNB supports IE MultibandInfoList in the ENB CONFIGURATION UPDATE message. • LTE1332: Downlink Carrier Aggregation - 40 MHz The eNB considers mapped bands when checking whether the UE supports the band combination for carrier aggregation. SIB 2. Impact on interfaces • X2 interface New IE MultibandInfoList added to X2 SETUP REQUEST.1. Descriptions of radio resource management and LTE RL60.5 Management data Alarms There are no alarms related to this feature. Impact on system performance and capacity This feature has no impact on system performance or capacity. Mapped EARFCN is used for SCC in communication with the UE. • LTE1387: Intra-eNodeB IF Load Balancing The eNB configures an EUTRAN frequency for inter-frequency measurements if the UE supports its mapped band. • LTE1407: RSRQ Based Redirect The eNB considers EUTRAN redirection targets if the UE supports their mapped band. • RRC protocol in LTE-Uu interface New IE MultibandInfoList added to SIB 1. and SIB 5. • LTE1170: Inter eNodeB IF Load Balancing The eNB configures EUTRAN frequencies for inter-frequency measurements if the UE supports their mapped band.21. Mapped EARFCN is used in communication with the UE. Mapped EARFCN is used in communication with the UE and between the eNBs. Mapped EARFCN is used for SCC in communication with the UE. Mapped EARFCN is used in communication to the UE and between the eNBs. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators 184 © 2016 Nokia DN09185955 Issue: 01J . and ENB CONFIGURATION UPDATE. Mapped EARFCN is used in communication with the UE and between eNBs. Mapped EARFCN is used in communication with the UE. 4. • LTE1442: Open Access Home eNodeB Mobility The eNB configures EUTRAN frequencies for inter-frequency measurements if the UE supports their mapped band. • LTE1677: Idle Mode Mobility Balancing Extensions Mapped EARFCN is used for communication with the UE. • LTE1089: Downlink Carrier Aggregation - 20 MHz The eNB considers mapped bands when checking whether the UE supports the band combination for carrier aggregation. X2 SETUP RESPONSE. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Feature Descriptions and Instructions telecom features • LTE1060: TDD - FDD Handover The eNB configures EUTRAN frequencies for inter-frequency measurements if the UE supports their mapped band. Table 108 Related existing parameters Name Abbreviation of name Managed object Downlink channel bandwidth dlChBw LNCEL Uplink channel bandwidth ulChBw LNCEL EARFCN downlink earfcnDL LNCEL EARFCN uplink earfcnUL LNCEL Eutra carrier info eutraCarrierInfo LNHOIF DN09185955 Issue: 01J © 2016 Nokia 185 . Feature Descriptions and Instructions Descriptions of radio resource management and telecom features There are no key performance indicators related to this feature. • The E-UTRA carrier frequency (eturaCarrierFreq) parameter is the Native E-UTRA Carrier Frequency. Table 107 New parameters Name Abbreviation of name Managed object Activate MFBI support actMFBI LNBTS Additional E-UTRA frequency addFreqBandInd MFBIPR band indicator Additional spectrum emission addSpectrEmissReq MFBIPR E-UTRA carrier frequency eutraCarrierFreq MFBIPR MFBI profile identifier mfbiPrId MFBIPR g Note: • The Additional E-UTRA frequency band indicator (addFreqBandInd) parameter is the mapped band. Table 108: Related existing parameters lists parameters related with this feature. Parameters Table 107: New parameters lists parameters introduced with this feature. LTE RL60. • The Additional spectrum emission (addSpectrEmissReq) parameter is for the mapped band. 6 Sales information Table 109 Sales information BSW/ASW License control in License control Activated by default network element attributes ASW SW Asset Monitoring . Descriptions of radio resource management and LTE RL60. perform the steps described in this procedure.2 Activating LTE1534: Multiple Frequency Band Indicator Before you start Table 110 Parameters used for activating and configuring LTE1534: Multiple Frequency Band Indicator Parameter Purpose Requires eNB restart or object locking Activate MFBI activation flag no support (actMFBI) Additional E-UTRA mandatory configuration no frequency band indicator (addFreqBandInd) Additional optional configuration no spectrum emission (addSpectrEmissRe q) E-UTRA carrier mandatory configuration no frequency (eutraCarrierFreq) MFBI profile mandatory configuration no identifier (mfbiPrId) g Note: For the feature to work correctly and consistently across the network.21. b) Expand the MRBTS object. 186 © 2016 Nokia DN09185955 Issue: 01J . the activation and configuration procedure must be performed consistently on all the eNBs within the network Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager.1. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. a) Go to the Radio Network Configuration page. No 4. 2 Activate the LTE1534: Multiple Frequency Band Indicator.21. Feature Descriptions and Instructions telecom features 4. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features c) Select the LNBTS object. a) Go to the Radio Network Configuration page. b) Expand the MRBTS object. 3 Configure the MFBIPR parameters. DN09185955 Issue: 01J © 2016 Nokia 187 . 4.3 Deactivating LTE1534: Multiple Frequency Band Indicator Before you start The Activate MFBI support (actMFBI) parameter is used for deactivation. g Note: The step should be repeated for each mapped band where the native frequency of a local cell (the LNCEL) is supported. The mapped band’s EARFCN will be calculated automatically and will be broadcasted in SIB1. a) Go to the Radio Network Configuration page. Modification of this parameter does not require neither eNB restart. b) Expand the MRBTS object. e) Set the value of the Additional spectrum emission (addSpectrEmissReq) parameter of the mapped band. SIB5 accordingly. c) Expand the LNBTS object. and/or the native frequency of the neighbor LTE frequency (the LNHOIF) of one or more of the local cells is supported. 4 Configure the Additional spectrum emission (optional). c) Right-click the LNBTS object. 5 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. LTE RL60. d) Set the Activate MFBI support (actMFBI) parameter value to true. g Note: The step should be repeated for each mapped band where the native frequency of a local cell (the LNCEL). nor cell locking.21. d) Select New MFBIPR e) Set the value of the Additional E-UTRA frequency band indicator (addFreqBandInd) parameter of the mapped band and the MFBI profile identifier (mfbiPrId) parameter. d) Select MFBIPR object. SIB2. f) Set the value of the E-UTRA carrier frequency (eutraCarrierFreq) parameter to the native band’s EARFCN. 22. a) Go to the Radio Network Configuration page. 4.21 Variable Definitions 4. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. Descriptions of radio resource management and LTE RL60. d) Set the Activate MFBI support (actMFBI) parameter value to false.1 Description of LTE1677: Idle Mode Mobility Balancing Extensions Introduction to the feature The LTE1677: Idle Mode Load Balancing Extensions feature introduces extensions to the LTE487: Idle Mode Mobility Load Balancing feature. 2 Deactivate the LTE1534: Multiple Frequency Band Indicator.22 LTE1677: Idle Mode Mobility Balancing Extensions 4.1 Benefits End-user benefits This feature does not affect the end-user experience. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.22. Feature Descriptions and Instructions telecom features Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager.1. c) Select the LNBTS object. Operator benefits This feature provides the operator the following benefits: • a multi-frequency balancing scheme for RRC IDLE UEs 188 © 2016 Nokia DN09185955 Issue: 01J . b) Expand the MRBTS object. 4. Expected outcome This step deactivates the feature. Also the mechanism for target frequency selection and building IdleModeMobilityControlInfo IE is changed. The algorithm existing for load balancing is replaced by weighted round robin algorithm. perform the steps described in this procedure. 3 Functional description The eNB supports adding IdleModeMobilityControlInfo IE to the RRC Connection Release message for intra-LTE and for inter-RAT load balancing targets. to be used as main target for Idle Mode load balancing.2 Requirements Software requirements Table 111: Software requirements lists software required for this feature. The eNB uses weighted round robin algorithm for selecting targets for load balancing. Table 111 Software requirements System release Flexi Multiradio BTS Flexi Multiradio OMS 10 BTS RL60 LBTS6. which value is lowered by one. - Hardware requirements This feature requires no new or additional hardware. The main and the secondary frequencies are considered by the eNB during target selection algorithm: • If the LTE487: Idle Mode Mobility Load Balancing feature flag is diabled. then the configuration of MODIMP and MOIMP objects is not needed. it is possible to use configured parameters for load balancing target frequencies within Mobility Profiles.1. Dedicated cell reselection priority configured inside this IE is always taken from cell reselection priority configured for SIB broadcast. excluding the one selected for the highest priority. which are sent to the UE.22. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4.0 LBTS6. then weights and frequencies are taken from the LNCEL and the IRFIM objects. and the LTE490: Subscriber Profile Based Mobility feature is not activated. Each weight factor divided by this sum gives probability of each frequency to be selected as the main target for Load Balancing. are used in the IdleModeMobilityControlInfo IE. If the LTE490: Subscriber Profile Based Mobility feature is enabled.1.22. GNFL. The Weighted Round Robin algorithm sums all configured weight factors.0 - UE NetAct MME SAE GW 3GPP R8 UE capabilities NetAct8 EP1 . 4. IRFIM. Weighted Round Robin For each target frequency the operator can configure weight factors idleLBXXXCelResWeight. used by the Weighted Round Robin algorithm in target selection procedure. • If the LTE487: Idle Mode Mobility Load Balancing feature flag is enabled. UFFIM. This target has the highest dedicated priority assigned in the RRC Connection Release message. and CDFIM objects. This support is done for an operator-configurable percentage of UEs with an RRC connection release without redirection. DN09185955 Issue: 01J © 2016 Nokia 189 . and the weight factors are considered for the LNCEL. LTE RL60. The "secondary" target frequencies. The eNB selects one target frequency matching UE Capabilities. the weights and frequencies are taken from IRFIM. • If one highest "Carrier Priority" is found. 190 © 2016 Nokia DN09185955 Issue: 01J . UFFIM. but only within intra-LTE target frequencies. if MODIMP is not present. It is recommended to configure SIB objects for all frequencies configured in MO(D)IMP. if the moProfileSelect=plmn. • The highest "Carrier Priority" between all target carriers for load balancing defined for a specific cell is found in RL50. Feature Descriptions and Instructions telecom features • If the LTE487: Idle Mode Mobility Load Balancing feature flag is enabled. or PLMN value (when the LTE486: PLMN ID Selected Mobility Profiles feature is enabled). (or the UEs don't have SPID. When the LTE487: Idle Mode Mobility Load Balancing feature flag is disabled. and have assigned a mobility profile. idleLBRttCelResWeight migration procedure for a specific LNCEL: • If no "Carrier Priority" is defined in RL50. no Idle Mode Mobility Load balancing is performed. no Idle Mode Mobility Load balancing is performed When Mobility Profiles are mapped and used for Idle Mode Load Balancing. see the LTE486: PLMN ID Selected Mobility Profiles feature). and LNCEL objects – if the autoAdapt=false. and they depend on SPID value. IRFIM. or SPID cannot be mapped to Mobility Profile. and the LTE490: Subscriber Profile Based Mobility feature is activated. If the UE has SPID assigned. Descriptions of radio resource management and LTE RL60. Migration for a specific LNCEL New carrier weight factors are introduced: • LNCEL: idleLBCelResWeight • IRFIM: idleLBEutCelResWeight • UFFIM: idleLBUtranFddCelResWeight • GNFL: idleLBGeranCelResWeight • CDFIM: idleLBHrpdCelResWeight. and SPID is mapped to a MOPR. UFFIM. CDFIM. the corresponding "Carrier weight factor" in RL60 is set to 100. if MOIMP is not present. then only those frequencies from mapped Mobility Profile object are used. GNFL. then the weights and frequencies are taken from MOIMP. and not inside Mobility Profiles. and CDFIM). and weights and frequencies are selected in the following way: – if the autoAdapt=true. then MODIMP objects and configuration of the autoAdapt parameter is checked. When the UE has no SPID assigned. and not all configured for SIB broadcast. then no "Carrier weight factor" is set in RL60. the weights and frequencies are taken from MODIMP. Parameters migration The LTE1677: Idle Mode Mobility Balancing Extensions feature removes parameters that were used in RL50 for setting “dedicated cell reselection priorities”: idleLBXXXReSelPrio from all SIB-related objects (LNCEL. and from MODIMP/MOIMP. then the target frequencies are used from Mobility Profiles objects. the eNB provides support for Idle Mode mobility load balancing using RL60 algorithm. GNFL. • If more than one "Carrier Priority" has the same highest value. Migration for all MODIMPs New carrier weight factors are introduced: • MODIMP: idleLBEutCelResWeight in the dlCarFrqEutL • MODIMP: idleLBUtraFddCelResWeight in the utrFddCarFrqL • MODIMP: idleLBGeranCelResWeight in the geranCarFrqBd • MODIMP: idleLBHrpdCelResWeight in the cdmaHrpdBdClL • MODIMP: idleLBRttCelResWeight in the cdmaRttBdClL migration procedure for MODIMP: • The highest "Carrier Priority" between all target carriers for load balancing defined in all instances of MODIMP is found in RL50. • If more than one "Carrier Priority" has the same highest value. • If "Carrier Priority" is defined in RL50 for other carriers with lower priority.1.22. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features • If more than one "Carrier Priority" has the same highest value. LTE RL60. the corresponding "Carrier weight factor" for each of these carriers in RL60 is set to 100. the corresponding "Carrier weight factor" for each of these carriers in RL60 is omitted.4 System impact Interdependencies between features • LTE487: Idle Mode Mobility Load Balancing DN09185955 Issue: 01J © 2016 Nokia 191 . Migration for MOIMPs under one specific MOPR New carrier weight factors are introduced: • MOIMP: idleLBEutCelResWeight in the dlCarFrqEutL • MOIMP: idleLBUtraFddCelResWeight in the utrFddCarFrqL • MOIMP: idleLBGeranCelResWeight in the geranCarFrqBd • MOIMP: idleLBHrpdCelResWeight in the cdmaHrpdBdClL • MOIMP: idleLBRttCelResWeight in the cdmaRttBdClL migration procedure for MOIMPs under one specific MOPR: • The highest "Carrier Priority" between all target carriers for load balancing defined in all instances of MOIMP under one specific MOPR is found in RL50. the corresponding "Carrier weight factor" for each of these carriers in RL60 is set to 100. • If "Carrier Priority" is defined in RL50 for other carriers with lower priority. the corresponding "Carrier weight factor" for each of these carriers in RL60 is omitted. 4. • If one highest "Carrier Priority" is found. • If one highest "Carrier Priority" is found. the corresponding "Carrier weight factor" for each of these carriers in RL60 is set to 100. the corresponding "Carrier weight factor" in RL60 is set to 100. the corresponding "Carrier weight factor" in RL60 is set to 100. the corresponding "Carrier weight factor" for each of these carriers in RL60 is omitted. • If "Carrier Priority" is defined in RL50 for other carriers with lower priority. If feature activation flag for the LTE487: Idle Mode Mobility Load Balancing feature is enabled in RL60/RL45TD. Idle Mode mobility load balancing for intra-LTE targets is a basic functionality of the eNB. Descriptions of radio resource management and LTE RL60. Load Balancing mechanism for redirection-based mobility and CSFB with redirection are inherited from RL50.22. The LTE1677: Idle Mode Mobility Balancing Extensions feature is enabled using the LTE487: Idle Mode Mobility Load Balancing feature flag. the eNB uses mapped EARFCN instead of native EARFCN in communication with UE for this E-UTRA frequency. If mapped value is supported by the UE.1. the eNB tries to use MFBI Profile to map native EARFCN into mapped EARFCN. • LTE1534: Multi Frequency Band Indicator If the LTE1534: Multi Frequency Band Indicator feature is enabled. Feature Descriptions and Instructions telecom features The LTE487: Idle Mode Mobility Load Balancing feature is partially replaced by the LTE1677: Idle Mode Mobility Balancing Extensions feature in mechanisms for Idle Mode Load Balancing used in RRC Connection Release without redirection. Feature flag does not need to be enabled to support this functionality and new weighted round robin is used for intra-LTE targets independent on feature flag value. Impact on network and network element management tools This feature has no impact on network management or network element management tools. then Idle Mode Load Balancing algorithm is enhanced with Multi Frequency Band Indicator (MFBI)- related functionality. If E-UTRA frequency represented by EARFCN value is not supported by UE.5 LTE1677: Management data Alarms There are no alarms related to this feature. The LTE1677: Idle Mode Mobility Balancing Extensions feature introduces weighted round robin algorithm that replaces load balancing algorithm. • LTE490: Subscriber Profile Based Mobility Mobility profiles can be used only if theLTE490: Subscriber profile based mobility feature is enabled. Measurements and counters There are no measurements and counters related to this feature. Key performance indicators 192 © 2016 Nokia DN09185955 Issue: 01J . existing in the LTE487: Idle Mode Mobility Load Balancing feature. 4. "Enhanced functionality of Idle Mode Load Balancing" is provided with: – intra-LTE target frequencies balanced with weighted round robin algorithm – inter-RAT target frequencies balanced with weighted round robin algorithm – usage of target frequencies for Idle Mode load balancing within Mobility Profiles when the LTE490: Subscriber Profile Based Mobility feature is enabled Additionally. Impact on system performance and capacity This feature has no impact on system performance or capacity. Impact on interfaces This feature has no impact on interfaces. Parameters Table 112: New parameters lists parameters introduced with this feature. LTE RL60. MOIMP dlCarFrqEutL factor idle mode load eight balancing UTRA-FDD carrier idleLBUtraFddCel MODIMP. MOIMP utrFddCarFrqL weight factor idle ResWeight mode load balancing GERAN carrier weight idleLBGeranCelRe MODIMP. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features There are no key performance indicators related to this feature. Table 112 New parameters Structure Name Abbreviation Managed object GERAN carrier weight idleLBGeranCelRe GNFL factor idle mode load sWeight balancing EUTRA carrier weight idleLBEutCelResW IRFIM factor idle mode load eight balancing Cell reselection weight idleLBCelResWeig LNCEL factor idle mode load ht balancing UTRA-FDD carrier idleLBUtranFddCe UFFIM weight factor idle lResWeight mode load balancing CDMA HRPD band idleLBHrpdCelRes CDFIM weight factor idle Weight mode load balancing CDMA 1xRTT band idleLBRttCelResW CDFIM weight factor idle eight mode load balancing EUTRA carrier weight idleLBEutCelResW MODIMP. MOIMP geranCarFrqBd factor idle mode load sWeight balancing CDMA HRPD band idleLBHrpdCelRes MODIMP. MOIMP cdmaHrpdBdClL weight factor idle Weight mode load balancing CDMA 1xRTT band idleLBRttCelResW MODIMP. DN09185955 Issue: 01J © 2016 Nokia 193 . MOIMP cdmaRttBdClL weight factor idle eight mode load balancing Table 113: Related existing parameters lists existing parameters related with this feature. Descriptions of radio resource management and LTE RL60. Feature Descriptions and Instructions telecom features Table 113 Related existing parameters Name Abbreviation Managed Object Structure Activation of idle mode actIdleLB LNBTS load balancing (IdleLB) Activate selective actSelMobPrf LNBTS mobility profiles Mobility profile moProfileSelect LNBTS selection mode Cell reselection priority cellReSelPrio LNCEL Timer T320 t320 LNCEL Percentage of UE for idleLBPercentage LNCEL idle mode load OfUes balancing Mobility profiles moPrMappingList LNCEL mapping list Mobility profile ID moPrId LNCEL moPrMappingList EUTRA frequency dlCarFrqEut IRFIM value EUTRA carrier eutCelResPrio IRFIM frequency absolute priority GERAN frequency bandInd GNFL band indicator GERAN RAT carrier gCelResPrio GNFL frequency absolute priority ARFCN value list gerArfcnVal GNFL CDMA2000 HRPD hrpdBdClList CDFIM band class list CDMA2000 HRPD hrpdBdClBcl CDFIM hrpdBdClList band class CDMA2000 HRPD cell hrpdCResPrio CDFIM hrpdBdClList reselection priority CDMA2000 1xRTT rttBdClList CDFIM band class list CDMA2000 1xRTT rttBdClBcl CDFIM rttBdClList band class BCL CDMA2000 1xRTT rttCResPrio CDFIM rttBdClList cell reselection priority List of UTRA FDD utrFddCarFrqL UFFIM carrier frequencies 194 © 2016 Nokia DN09185955 Issue: 01J . layers of all neighbour cells CDMA HRPD band list cdmaHrpdBdClL MODIMP. MOPR idle mode load OfUes balancing Auto adaptation to autoAdapt MODPR freq. MOIMP for idle mode load balancing UTRA FDD carrier utrFddCarFrq MODIMP. MOIMP utrFddCarFrqL freq for idle mode load balancing DN09185955 Issue: 01J © 2016 Nokia 195 . MOIMP idle mode load balancing EUTRA carrier dlCarFrqEut MODIMP. MOIMP cdmaHrpdBdClL class for idle mode load balancing CDMA 1xRTT band cdmaRttBdClL MODIMP. MOIMP parameters for idle mode load balancing GERAN carrier freq geranBandInd MODIMP. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 113 Related existing parameters (Cont. MOIMP dlCarFrqEutL frequency for idle mode load balancing GERAN band geranCarFrqBd MODIMP.) Name Abbreviation Managed Object Structure UTRA downlink dlCarFrqUtra UFFIM utrFddCarFrqL frequency value UTRA carrier uCelResPrio UFFIM utrFddCarFrqL frequency absolute priority Percentage of UE for idleLBPercentage MODPR. LTE RL60. MOIMP for idle mode load balancing CDMA HRPD band cdmaHrpdBdCl MODIMP. MOIMP geranCarFrqBd band for idle mode load balancing UTRA FDD carrier list utrFddCarFrqL MODIMP. MOIMP list for idle mode load balancing CDMA 1xRTT band cdmaRttBdCl MODIMP. MOIMP cdmaRttBdClL class for idle mode load balancing EUTRA carrier list for dlCarFrqEutL MODIMP. The following parameters on different RAT technologies cannot have the same value assigned: • CDFIM: CDMA2000 HRPD cell reselection priority (hrpdCResPrio) • CDFIM: CDMA2000 1xRTT cell reselection priority (rttCResPrio) • UFFIM: UTRA carrier frequency absolute priority (uCelResPrio) • GNFL: GERAN RAT carrier frequency absolute priority (gCelResPrio) • IRFIM: EUTRA carrier frequency absolute priority (eutCelResPrio) • LNCEL: Cell reselection priority (cellReSelPrio) When using mobility profiles.22. The optional reselection priorities in the CDFIM.1. GNFL. It is re-using the LTE487: Idle Mode Mobility Load Balancing feature activation flag. No 4.2 Activating and configuring LTE1677: Idle Mode Mobility Balancing Extensions Before you start The LTE1677: Idle Mode Mobility Balancing Extensions feature does not have separate feature activation flag. there should be a CDFIM. UFFIM.6 Sales information Table 114 Sales information BSW/ASW License control in License control Activated by default network element attributes ASW SW Asset Monitoring .22. or IRFIM object. or IRFIM objects is recommended to be configured. 196 © 2016 Nokia DN09185955 Issue: 01J . Descriptions of radio resource management and LTE RL60. for all frequencies described in the profiles. UFFIM. GNFL. Feature Descriptions and Instructions telecom features 4. Table 115 Parameters used for activating and configuring LTE1677: Idle Mode Mobility Balancing Extensions Parameter Purpose Requires eNB restart or object locking Activation of idle activation flag no mode load balancing (IdleLB) (actIdleLB). LTE490: Subscriber Profile Based MODIMP. and the LTE1677: Idle Mode Mobility Balancing Extensions feature is activated first time in RL60. MOIMP: the EUTRA carrier weight factor idle mode load balancing (idleLBEutCelResWeight) parameter • MODIMP. MOIMP Mobility feature is activated CDMA 1xRTT band list mandatory configuration if no for idle mode load RAT_CDMA is used as target for Idle balancing Mode Load Balancing and the (cdmaRttBdClL) structure. LTE RL60. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features g Note: If the LTE487: Idle Mode Mobility Load Balancing feature was not activated in RL50. MOIMP Mobility feature is activated DN09185955 Issue: 01J © 2016 Nokia 197 . after migration to RL60. LTE490: Subscriber Profile Based MODIMP. MOIMP: the UTRA-FDD carrier weight factor idle mode load balancing (idleLBUtraFddCelResWeight) parameter • MODIMP. MOIMP: the GERAN carrier weight factor idle mode load balancing (idleLBGeranCelResWeight) parameter • MODIMP. LNBTS CDMA HRPD band list mandatory configuration if no for idle mode load RAT_CDMA is used as target for Idle balancing Mode Load Balancing and the (cdmaHrpdBdClL) structure. MOIMP: the CDMA 1xRTT band weight factor idle mode load balancing (idleLBRttCelResWeight) parameter g Note: If the LTE490: Subscriber Profile Based Mobility feature is not activated. then the weight factors are not configured. If the LTE487: Idle Mode Mobility Load Balancing feature was active in RL50. MOIMP: the CDMA HRPD band weight factor idle mode load balancing (idleLBHrpdCelResWeight) parameter • MODIMP. the configuration of MODIMP and MOIMP objects is not needed at all. the weight factors might have specific values that can be configured (the highest carrier priorities defined in RL50 are converted into carrier weight factor values=100 in RL60): • LNCEL: the Cell reselection weight factor idle mode load balancing (idleLBCelResWeight) parameter • IRFIM: the EUTRA carrier weight factor idle mode load balancing ( idleLBEutCelResWeight) parameter • UFFIM: the UTRA-FDD carrier weight factor idle mode load balancing (idleLBUtranFddCelResWeight) parameter • GNFL: the GERAN carrier weight factor idle mode load balancing (idleLBGeranCelResWeight) parameter • CDFIM: the CDMA HRPD band weight factor idle mode load balancing (idleLBHrpdCelResWeight) parameter • CDFIM: the CDMA 1xRTT band weight factor idle mode load balancing (idleLBRttCelResWeight) parameter • MODIMP. MOIMP Mobility feature is activated GERAN carrier freq mandatory configuration if no list for idle mode RAT_GERAN is used as target for Idle load balancing Mode Load Balancing and the (geranCarFrqIdleModeL). MOIMP Mobility feature is activated CDMA 1xRTT band weight mandatory configuration if no factor idle mode load RAT_CDMA is used as target for Idle balancing Mode Load Balancing and the (idleLBRttCelResWeigh LTE490: Subscriber Profile Based t). MOIMP Mobility feature is activated CDMA2000 HRPD band mandatory configuration if no class list RAT_CDMA2000 is used as target for (hrpdBdClList) structure.) Parameter Purpose Requires eNB restart or object locking EUTRA carrier list for mandatory configuration if no idle mode load RAT_EUTRA is used as target for Idle balancing Mode Load Balancing and the (dlCarFrqEutL) structure. MOIMP feature is activated EUTRA carrier weight mandatory configuration if no factor idle mode load RAT_EUTRA is used as target for Idle balancing Mode Load Balancing and the (idleLBEutCelResWeigh LTE490: Subscriber Profile Based t). Idle Mode Load Balancing CDFIM 198 © 2016 Nokia DN09185955 Issue: 01J . LTE490: Subscriber Profile Based MODIMP. MODIMP. Feature Descriptions and Instructions telecom features Table 115 Parameters used for activating and configuring LTE1677: Idle Mode Mobility Balancing Extensions (Cont. MOIMP Mobility feature is activated UTRA-FDD carrier mandatory configuration if RAT_UTRA no weight factor idle is used as target for Idle Mode Load mode load balancing Balancing and the LTE490: (idleLBUtraFddCelResWe Subscriber Profile Based Mobility ight). LTE490: Subscriber Profile Based MODIMP. Descriptions of radio resource management and LTE RL60. MOIMP feature is activated GERAN carrier weight mandatory configuration if no factor idle mode load RAT_GERAN is used as target for Idle balancing Mode Load Balancing and the (idleLBGeranCelResWeig LTE490: Subscriber Profile Based ht). MOIMP Mobility feature is activated UTRA FDD carrier list mandatory configuration if RAT_UTRA no for idle mode load is used as target for Idle Mode Load balancing Balancing and the LTE490: (utrFddCarFrqL) structure. MODIMP. MODIMP. MOIMP Mobility feature is activated CDMA HRPD band weight mandatory configuration if no factor idle mode load RAT_CDMA is used as target for Idle balancing Mode Load Balancing and the (idleLBHrpdCelResWeigh LTE490: Subscriber Profile Based t). MOIMP Mobility feature is activated GERAN band parameters mandatory configuration if no for idle mode load RAT_GERAN is used as target for Idle balancing Mode Load Balancing and the (geranCarFrqBd) structure. LTE490: Subscriber Profile Based MODIMP. MODIMP. Subscriber Profile Based Mobility MODIMP. MODIMP. LTE RL60. DN09185955 Issue: 01J © 2016 Nokia 199 . Balancing UFFIM UTRA-FDD carrier mandatory configuration if RAT_UTRA no weight factor idle is used as target for Idle Mode Load mode load balancing Balancing (idleLBUtranFddCelResW eight). UFFIM CDMA HRPD band weight mandatory configuration if no factor idle mode load RAT_CDMA is used as target for Idle balancing Mode Load Balancing (idleLBHrpdCelResWeigh t). Idle Mode Load Balancing CDFIM List of UTRA FDD mandatory configuration if RAT_UTRA no carrier frequencies is used as target for Idle Mode Load (utrFddCarFrqL) structure. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. CDFIM GERAN carrier weight mandatory configuration if no factor idle mode load RAT_GERAN is used as target for Idle balancing Mode Load Balancing (idleLBGeranCelResWeig ht). CDFIM CDMA 1xRTT band weight mandatory configuration if no factor idle mode load RAT_CDMA is used as target for Idle balancing Mode Load Balancing (idleLBRttCelResWeigh t). perform the steps described in this procedure.) Parameter Purpose Requires eNB restart or object locking CDMA2000 1xRTT band mandatory configuration if no class list RAT_CDMA2000 is used as target for (rttBdClList) structure. GNFL EUTRA carrier weight mandatory configuration if no factor idle mode load RAT_EUTRA is used as target for Idle balancing Mode Load Balancing (idleLBEutCelResWeigh t). Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Table 115 Parameters used for activating and configuring LTE1677: Idle Mode Mobility Balancing Extensions (Cont. IRFIM Cell reselection optional configuration no weight factor idle mode load balancing (idleLBCelResWeight). LNCEL Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. b) Expand the MRBTS object. b) Expand the MRBTS object. Descriptions of radio resource management and LTE RL60. see the LTE490: Subscriber profile based mobility feature in Feature Descriptions RL30. recommended if the operator wants to use it as target for Idle Mode Mobility Load Balancing) • the CDMA HRPD band list for idle mode load balancing (cdmaHrpdBdCIL) structure – the CDMA HRPD band class for idle mode load balancing (cdmaHrpdBdCl) parameter – the CDMA HRPD band weight factor idle mode load balancing (idleLBHrpdCelResWeight) parameter • the CDMA 1xRTT band list for idle mode load balancing (cdmaRttBdClL) structure – the CDMA 1xRTT band class for idle mode load balancing (cdmaRttBdCl) parameter – the CDMA 1xRTT band weight factor idle mode load balancing (idleLBRttCelResWeight) parameter • the EUTRA carrier list for idle mode load balancing (dlCarFrqEutL) structure – the EUTRA carrier frequency for idle mode load balancing (dlCarFrqEut) parameter – the EUTRA carrier weight factor idle mode load balancing (idleLBEutCelResWeight) parameter 200 © 2016 Nokia DN09185955 Issue: 01J . If the LTE490: Subscriber Profile Based Mobility feature is not activated. needed for technology used as a target for Idle Mode Mobility Load Balancing. c) Expand the LNBTS object. if the LTE490: Subscriber Profile Based Mobility feature is activated). e) Select New MODIMP. a) Go to the Radio Network Configuration page. c) Select the LNBTS object. a) Go to the Radio Network Configuration page. f) For the MODIMP- Properties set the Idle mode mobility default profile identifier (modimpId) parameter value. the configuration of MODIMP is not needed. d) Set the Activation of idle mode load balancing (IdleLB) (actIdleLB) parameter value to true. h) Select new parameters and set the parameters' values for: (optional. g) Right-click the MODIMP object. Feature Descriptions and Instructions telecom features 2 Activate the LTE487: Idle Mode Mobility Load Balancing feature flag. 3 Configure the MODIMP parameters (optional. d) Right-click the MODPR object. the configuration of MOIMP is not needed. a) Go to the Radio Network Configuration page. j) Select new parameters and set the parameters' values for: (optional. f) Right-click the MOPR object. If the LTE490: Subscriber Profile Based Mobility feature is not activated. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features • the GERAN band parameters for idle mode load balancing (geranCarFrqBd) structure – the GERAN carrier freq band for idle mode load balancing (geranBandInd) parameter – the GERAN carrier weight factor idle mode load balancing (idleLBGeranCelResWeight) parameter • the GERAN carrier freq list for idle mode load balancing (geranCarFrqIdleModeL) parameter • the UTRA FDD carrier list for idle mode load balancing (utrFddCarFrqL) structure – the UTRA-FDD carrier weight factor idle mode load balancing (idleLBUtraFddCelResWeight) parameter – the UTRA FDD carrier freq for idle mode load balancing (utrFddCarFrq) parameter 4 Configure the MOIMP parameters (optional. if the LTE490: Subscriber Profile Based Mobility feature is activated). recommended if the operator wants to use it as target for Idle Mode Mobility Load Balancing) • the CDMA HRPD band list for idle mode load balancing (cdmaHrpdBdCIL) structure – the CDMA HRPD band class for idle mode load balancing (cdmaHrpdBdCl) parameter – the CDMA HRPD band weight factor idle mode load balancing (idleLBHrpdCelResWeight) parameter • the CDMA 1xRTT band list for idle mode load balancing (cdmaRttBdClL) structure DN09185955 Issue: 01J © 2016 Nokia 201 . h) For the MOIMP- Properties set the Idle mode mobility profile identifier (moimpId) parameter value. see the LTE490: Subscriber profile based mobility in Feature Descriptions RL30. g) Select New MOIMP. LTE RL60. d) Select New MOPR. i) Right-click the MOIMP object. b) Expand the MRBTS object. e) For the MOPR- Properties set the Mobility profile identifier (moPrId) parameter value. c) Right-click the LNBTS object. needed for technology used as a target for Idle Mode Mobility Load Balancing. b) Expand the MRBTS object. d) Right-click the LNCEL object. a) Go to the Radio Network Configuration page. c) Expand the LNBTS object. h) Right-click the CDFIM object. f) Select the CDFIM object. i) Select new parameters and set the parameters values for: • CDMA2000 HRPD band class list (hrpdBdClList) structure – CDMA2000 HRPD band class (hrpdBdClBcl) – CDMA2000 HRPD cell reselection priority (hrpdCResPrio) 202 © 2016 Nokia DN09185955 Issue: 01J . Feature Descriptions and Instructions telecom features – the CDMA 1xRTT band class for idle mode load balancing (cdmaRttBdCl) parameter – the CDMA 1xRTT band weight factor idle mode load balancing (idleLBRttCelResWeight) parameter • the EUTRA carrier list for idle mode load balancing (dlCarFrqEutL) structure – the EUTRA carrier frequency for idle mode load balancing (dlCarFrqEut) parameter – the EUTRA carrier weight factor idle mode load balancing (idleLBEutCelResWeight) parameter • the GERAN band parameters for idle mode load balancing (geranCarFrqBd) structure – the GERAN carrier freq band for idle mode load balancing (geranBandInd) parameter – the GERAN carrier weight factor idle mode load balancing (idleLBGeranCelResWeight) parameter • the GERAN carrier freq list for idle mode load balancing (geranCarFrqIdleModeL) parameter • the UTRA FDD carrier list for idle mode load balancing (utrFddCarFrqL) structure – the UTRA-FDD carrier weight factor idle mode load balancing (idleLBUtraFddCelResWeight) parameter – the UTRA FDD carrier freq for idle mode load balancing (utrFddCarFrq) parameter 5 Configure the CDFIM parameters (optional. e) Select New CDFIM. g) Set the CDMA2000 frequency idle mode configuration identifier (cdfimId) parameter value. needed for RAT_CDMA2000 technology used as target for Idle Mode Mobility Load Balancing). Descriptions of radio resource management and LTE RL60. Select the CDFIM object. then the CDMA2000 HRPD cell reselection timer (tResHrpd) parameter is mandatory to be set: 1. then the CDMA2000 HRPD neighbor cell list (hrpdNCList) parameter is mandatory to be set: 1. 2. 3. g Note: If the CDMA2000 HRPD cell reselection timer (tResHrpd) parameter in the CDFIM object is not empty. Set the CDMA2000 HRPD cell reselection timer (tResHrpd) paramete value. Expand the LNBTS object. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features – CDMA2000 HRPD reselection high threshold (hrpdFrqThrH) – CDMA2000 HRPD reselection low threshold (hrpdFrqThrL) – CDMA HRPD band weight factor idle mode load balancing (idleLBHrpdCelResWeight) g Note: If the CDMA2000 HRPD band class list (hrpdBdCIList) parameter in the CDFIM object has more than (or equal to) 1 instance(s). Expand the MRBTS object. LTE RL60. 6. 5. 4. Right-click the CDFIM object. 7. Go to the Radio Network Configuration page. 2. Expand the LNCEL object. For the CDMA2000 HRPD neighbor cell list-1 Properties set the parameters' values for: • the CDMA2000 1xRTT band class list (rttBdClList) structure – the CDMA 1xRTT band weight factor idle mode load balancing (idleLBRttCelResWeight) parameter – the CDMA2000 1xRTT band class BCL (rttBdClBcl) parameter – the CDMA2000 1xRTT cell reselection priority (rttCResPrio) parameter – the CDMA2000 1xRTT reselection high threshold (rttFrqThrH) parameter – the CDMA2000 1xRTT reselection low threshold (rttFrqThrL) parameter DN09185955 Issue: 01J © 2016 Nokia 203 . Select the New CDMA2000 HRPD neighbor cell list. needed for RAT_UTRA technology used as target for Idle Mode Mobility Load Balancing). Expand the LNBTS object. then the CDMA2000 1xRTT cell reselection timer (tResRtt) parameter is mandatory to be set: 1. then the CDMA2000 1xRTT neighbor cell list (rttNCList) parameter is mandatory to be set: 1. g Note: If the CDMA2000 1xRTT neighbor cell list (rttNCList) in the CDFIM object has more than (or equal to) one instance(s). Go to the Radio Network Configuration page. f) For the UFFIM- Properties set the parameters' values. 2. c) Expand the LNBTS object. For the CDMA2000 1xRTT neighbor cell list-1 Properties set the parameters values. Note: The CDMA2000 1xRTT band class (NCL) (rttBdCINcl) parameter in g the CDMA2000 1xRTT neighbor cell list (rttNCList) list needs to be eq to the related CDMA 1xRTT band class BCL (rttBdCIBcl) parameter in the CDMA2000 1xRTT band class list (rttBdClList) list. Descriptions of radio resource management and LTE RL60. 3. h) Select and expand the List of UTRA FDD carrier frequencies. a) Go to the Radio Network Configuration page. d) Right-click the LNCEL object. Right-click the CDFIM object. 6 Configure the List of UTRA FDD carrier frequencies in the UFFIM object (optional. g) Right-click the UFFIM object. Expand the MRBTS object. Set the CDMA2000 1xRTT cell reselection timer (tResRtt) parameter value. 3. 6. 4. Select the CDFIM object. Select the New CDMA2000 1xRTT neighbor cell list. Feature Descriptions and Instructions telecom features g Note: If the CDMA2000 1xRTT neighbor cell list (rttBdCIList) parameter in the CDFIM object has more than (or equal to) 1 instance(s). e) Select New UFFIM. 2. 5. b) Expand the MRBTS object. i) For the List of UTRA FDD carrier frequencies-1 Properties set the parameters values for: • UTRA downlink frequency value (dlCarFrqUtra) • UTRA-FDD carrier weight factor idle mode load balancing (idleLBUtranFddCelResWeight) • UTRA maximum allowed transmit power (pMaxUtra) 204 © 2016 Nokia DN09185955 Issue: 01J . Expand the LNCEL object. l) Select the ARFCN value list-1. LTE RL60. needed for RAT_GERAN technology used as target for Idle Mode Mobility Load Balancing). a) Go to the Radio Network Configuration page. m) Set the ARFCN value list (gerArfcnVal) parameter value. f) For the GFIM- Properties set the parameters' values. h) Select New GNFL. a) Go to the Radio Network Configuration page. c) Expand the LNBTS object. DN09185955 Issue: 01J © 2016 Nokia 205 . g) Right-click the GFIM object. d) Right-click the LNCEL object. 8 Configure the EUTRA carrier weight factor idle mode load balancing parameter for the IRFIM object (optional. needed for RAT_EUTRA technology used as target for Idle Mode Mobility Load Balancing). Feature Descriptions and Instructions Descriptions of radio resource management and telecom features • UTRA minimum needed quality parameter (qQualMinUtra) • UTRA minimum required receive level (qRxLevMinUtra) • UTRA carrier frequency absolute priority (uCelResPrio) • UTRA inter-RAT quality threshold high (Rel9) (utraFrqQThrHighR9) • UTRA inter-RAT quality threshold low (Rel9) (utraFrqQThrLowR9) • UTRA inter frequency threshold high (utraFrqThrH) • UTRA inter frequency threshold low (utraFrqThrL) 7 Configure the GERAN carrier weight factor idle mode load balancing parameter for the GNFL object (optional. k) Expand the ANFCN value list. b) Expand the MRBTS object. i) For the GNFL- Properties set the parameters' values for: • GERAN carrier weight factor idle mode load balancing (idleLBGeranCelResWeight) • GERAN neighbour frequency configuration identifier (gnflId) • GERAN frequency band indicator (bandInd) • GERAN inter-frequency threshold high (gerFrqThrH) • GERAN inter-frequency threshold low ( gerFrqThrL) • GERAN maximum allowed transmit power (pMaxGer) • GERAN minimum required receive level (qRxLevMinGer) • GERAN RAT carrier frequency absolute priority (gCelResPrio) j) Expand the GNFL object. e) Select New GFIM. d) Select the LNCEL object. g) For the IRFIM- Properties set the parameters values for: • EUTRA carrier weight factor idle mode load balancing ( idleLBEutCelResWeight) • IRFIM identifier ( irfimId) • Allowed measurement bandwidth (measBdw) • EUTRA carrier frequency absolute priority (eutCelResPrio) • EUTRA cell reselection timer (interTResEut) • EUTRA frequency specific offset (qOffFrq) • EUTRA frequency value ( dlCarFrqEut) • EUTRA inter frequency threshold high (interFrqThrH) • EUTRA inter frequency threshold low (interFrqThrL) • EUTRA presence antenna port1 (interPresAntP) • Min required RSRQ in inter-freq neighbor cells (Rel9) (qQualMinR9) • Minimum required Rx RSRP level (qRxLevMinInterF) • Pmax neighbouring EUTRA cells ( pMaxInterF) 9 Configure the Cell reselection weight factor idle mode load balancing parameter for the LNCEL object (optional). c) Expand the LNBTS object. a) Go to the Radio Network Configuration page. 10 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. f) Select the IRFIM object. b) Expand the MRBTS object. e) Set the Cell reselection weight factor idle mode load balancing (idleLBCelResWeight) parameter value. e) Select New IRFIM. It is re-using the LTE487: Idle Mode Mobility Load Balancing feature activation flag.22. Feature Descriptions and Instructions telecom features b) Expand the MRBTS object. d) Right-click the LNCEL object. 206 © 2016 Nokia DN09185955 Issue: 01J .3 Deactivating LTE1677: Idle Mode Mobility Balancing Extensions Before you start The LTE1677: Idle Mode Mobility Balancing Extensions feature does not have separate feature activation flag. c) Expand the LNBTS object. Descriptions of radio resource management and LTE RL60. 4. and MODRED objects.23 LTE1755: Multiple emergency areas per cell 4. b) Expand the MRBTS object. d) Set the Activation of idle mode load balancing (IdleLB) (actIdleLB) parameter value to false.1. 4. the Redirection priority for UE context release (redirectPrio) and the Redirection priority for CS fallback with redirection (csFallBPrio) parameters must be unique in REDRT. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. When deactivating the LTE1677: Idle Mode Mobility Balancing Extensions feature. a) Go to the Radio Network Configuration page. LTE RL60.1 Description of LTE1755: Multiple emergency areas per cell Introduction to the feature The LTE1755: Multiple emergency areas per cell feature supports multiple emergency area IDs per cell.1 Benefits End-user benefits DN09185955 Issue: 01J © 2016 Nokia 207 . nor cell locking.22 Variable Definitions 4. Modification of this parameter does not require neither eNB restart. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features The Activation of idle mode load balancing (IdleLB) (actIdleLB) parameter is used for deactivation.23. 4. 2 Deactivate the feature flag. c) Select the LNBTS object. Expected outcome When deactivating the LTE1677: Idle Mode Mobility Balancing Extensions feature. the basic part of Idle Mode Mobility Load Balancing with weighted round robin algorithm still works and is supported only for intra-LTE targets (inter-RAT targets and usage of targets from Mobility Profiles are not supported).23. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. perform the steps described in this procedure. MORED. 3 Functional description With LTE1755: Multiple emergency areas per cell feature. 208 © 2016 Nokia DN09185955 Issue: 01J . Descriptions of radio resource management and LTE RL60.1.2 Requirements Software requirements Table 116: Software requirements lists the software required for this feature.0 - UE NetAct MME SAE GW 3GPP R8 UE capabilities NetAct8 EP1 .23. 4. Table 116 Software requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 LBTS6. if at least one of the EAIDs configured for this cell matches with one of the EAIDs received in the request message. 4. The emergency area IDs (EAIDs) are used to check if warning messages need to be broadcasted in a cell. 4. Operator benefits Instead of only one Emergency Area ID (EAID). the Flexi Multiradio BTS allows to configure up to 15 emergency area IDs per cell for Commercial Mobile Alert System (CMAS) or Earthquake and Tsunami Warning System (ETWS). This improvement will allow to trigger the sending of a warning message in a specific eNB cell using different EAIDs.1.23. then the eNB sends or stops sending the warning message in an eNB cell.23. When the eNB receives a S1AP: WRITE-REPLACE WARNING REQUEST or S1AP: KILL REQUEST message including an Emergency Area ID list in the Warning Area List information element. This feature allows to trigger the sending of a warning message to the specific eNB cell by using different EAIDs. - Hardware requirements This feature requires no new or additional hardware. the operator can assign up to 15 different EAIDs per eNB cell.1. Feature Descriptions and Instructions telecom features The end-user located in a certain cell receives warning messages that are sent out using different emergency area IDs.0 LBTS6. The emergency area IDs can be different for different cells.4 System impact Interdependencies between features One of the following features needs to be enabled: • LTE843: ETWS broadcast • LTE494: Commercial Mobile Alert System Impact on interfaces This feature has no impact on interfaces. do not broadcast the received warning message. The cells that are not activated at the time when the S1AP: WRITE-REPLACE WARNING REQUEST or S1AP: KILL REQUEST messages arrives. therefore.23.1. Parameters Table 117: Related existing parameters lists parameters introduced with this feature. .6 Sales information Table 118 Sales information BSW/ASW License control in License control Activated by default network element attributes BSW .2 Activating and configuring LTE1755: Multiple emergency areas per cell Before you start The LTE1755: Multiple emergency areas per cell feature is a BSW feature. Table 119 Parameters used for configuring LTE1755: Multiple emergency areas per cell Parameter Purpose Requires eNB restart or object locking PWS with emergency optional configuration no area DN09185955 Issue: 01J © 2016 Nokia 209 . LTE RL60. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Impact on network and network element management tools This feature has no impact on network management or network element management tools.23.23. Yes 4.1. Measurements and counters There are no measurements or counters related to this feature. It is activated by default. There are several related parameters to this feature. Table 117 Related existing parameters Full name Abbreviated name Managed object PWS with emergency area ID pwsWithEmAreaId LNBTS Emergency area ID list emAreaIdList LNCEL 4. Impact on system performance and capacity This feature has no impact on system performance or capacity. Key performance indicators There are no key performance indicators related to this feature. 4.5 LTE1755: Multiple emergency areas per cell management data Alarms There are no alarms related to this feature. feature configuration is needed. then Emergency area ID list (emAreaIdList) parameter has to be provided for each eNB cell. If PWS with emergency area ID (pwsWithEmAreaId) parameter is set to true.) Parameter Purpose Requires eNB restart or object locking ID (pwsWithEmAreaId ) Emergency area ID optional configuration no list (emAreaIdList) One of the following features need to be activated and configured before LTE1755: Multiple emergency areas per cell feature configuration: • LTE843: ETWS broadcast • LTE494: Commercial Mobile Alert System If either LTE843: ETWS broadcast or LTE494: Commercial Mobile Alert System feature is activated. d) Set the PWS with emergency area ID (pwsWithEmAreaId) parameter value to true. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. Feature Descriptions and Instructions telecom features Table 119 Parameters used for configuring LTE1755: Multiple emergency areas per cell (Cont. 210 © 2016 Nokia DN09185955 Issue: 01J . b) Expand the MRBTS object. then the PWS with emergency area ID (pwsWithEmAreaId) parameter is provided. The feature LTE1755: Multiple emergency areas per cell is activated automatically when one of the following features has been activated: • LTE843: ETWS broadcast • LTE494: Commercial Mobile Alert System 3 Configure the LTE1755: Multiple emergency areas per cell. c) Select the LNBTS object. Descriptions of radio resource management and LTE RL60. With LTE1755: Multiple emergency areas per cell feature it is possible to assign up to 15 Emergency Area IDs for one cell. a) Go to the Radio Network Configuration page. 2 Activate the LTE1755: Multiple emergency areas per cell feature. a) Go to the Radio Network Configuration page. see the corresponding feature deactivation instruction. e) Right click on LNCEL object and add New Emergency area ID list object. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features 4 Assign the emergency area to cell. d) Select the LNCEL object.3 Deactivating LTE1755: Multiple emergency areas per cell Before you start The feature LTE1755: Multiple emergency areas per cell is deactivated when the following features are deactivated: • LTE843: ETWS broadcast • LTE494: Commercial Mobile Alert System Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. g) Set the Emergency area ID list (emAreaIdList) parameter. This information is used by eNB for Earthquake and Tsunami Warning System (ETWS) or Commercial Mobile Alert System (CMAS) message routing. LTE RL60. 2 Deactivate related features. It is possible to assign up to 15 Emergency Area IDs to each cell. c) Expand the LNBTS object. f) Expand Emergency area ID list object and assign at least one Emergency Area ID to each cell. b) Expand the MRBTS object. 5 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. DN09185955 Issue: 01J © 2016 Nokia 211 . Expected outcome Up to 15 Emergency Areas IDs are assigned for each cell. The LTE1755: Multiple emergency areas per cell feature is deactivated when the following features are deactivated: • LTE843: ETWS broadcast • LTE494: Commercial Mobile Alert System For more information. 4.23. 0 LBTS7. Benefits End-user benefits No effect on the end-user experience Operator benefits The number of supported inter-frequency layers for a cell re-selection and inter- frequency measurements for a handover is expanded. Up to 6 inter-frequency measurements (combination of FDD and TDD) can be configured per UE depending on the configured inter-frequency bands. Expected outcome The feature LTE1755: Multiple emergency areas per cell has been deactivated.24 LTE2008: Extended Inter-frequency Measurements 4. Descriptions of radio resource management and LTE RL60.1 Description of LTE2008: Extended Inter-frequency Measurements Introduction to the feature With the LTE2008: Extended Inter-frequency Measurements feature. Requirements Hardware and software requirements Table 120 Hardware and software requirements System release Flexi Multiradio Flexi Multiradio Flexi Zone Micro OMS BTS 10 BTS RL60 LBTS6. Feature Descriptions and Instructions telecom features 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. - Functional description Functional overview The eNode supports the following configurations for inter-frequency measurements: Configuration 1 (Default): The eNode B supports up to N=3 parallel FDD and TDD LTE inter-frequency measurements for coverage-based (A3/A5 Measurements) as well as for load-based (A4 Measurements) handovers. 212 © 2016 Nokia DN09185955 Issue: 01J .0 - UE NetAct MME SAE GW 3GPP R8 . 4.0 LBTS6. the number of supported inter-frequency layers for inter-frequency measurements for handovers expands. .24. LTE RL60. Either all E-UTRA carriers are considered for Fast Measurement Solicitation (E-UTRA handover in case of load balancing) or only those carriers with an EARFCN which do not belong to the band of the serving EARFCN (exclude intra-band load balancing). for example: • N x FDD • N-1 x FDD + 1 x TDD LTE • . • 1 x FDD + N-1 x TDD LTE • N x TDD LTE The maximum allowed number of parallel inter-frequency and IRAT measurements of up to 7 measurements is still valid. for example: • N x FDD • N-1 x FDD + 1 x TDD LTE • . configuration 2 is selected and the number of interfrequency measurements is extended to N=6 (from N=3). If the actSixIfMeasurements is true. If the actNoIntraBandIFMeasurements parameter is set to true: inter-frequency load balancing neighbor frequencies within the same frequency band as the frequency of the own cell are excluded... Any mix of FDD and TDD inter-frequency measurements is allowed. Configuration 2: The eNode B supports up to N=6 parallel FDD and TDD LTE inter-frequency measurements for coverage-based (A3/A5 Measurements) as well as for load-based (A4 Measurements) handovers.. Feature Descriptions and Instructions Descriptions of radio resource management and telecom features Any mix of FDD and TDD inter-frequency measurements is allowed. Default values The default values of both parameters actSixIfMeasurements and actNoIntraBandIFMeasurements are false. The two configurations can be selected by the parameter Activate support for up to six Inter-freq measurement (actSixIfMeasurements). • 1 x FDD + N-1 x TDD LTE • N x TDD LTE The maximum allowed number of parallel inter-frequency and IRAT measurements of up to 7 measurements is still valid. Impact on system performance and capacity No impact on system performance or capacity DN09185955 Issue: 01J © 2016 Nokia 213 . System impact Interdependencies between features The LTE1060: FDD-TDD Handover feature needs to be enabled for the FDD-TDD handover support.. This the operator can select with the Activate support for excluded intra-band IF measurement (actNoIntraBandIFMeasurements ) parameter. Key performance indicators Parameters Table 121 New parameters Full name Abbreviated name Managed object Activate support for up to six actSixIfMeasurements LNCEL Inter-freq measurement Activate support for excluded actNoIntraBandIFMeasuremen LNCEL intra-band IF measurement ts Sales information Table 122 Sales information BSW/ASW License control in network Activated by default element BSW . No 214 © 2016 Nokia DN09185955 Issue: 01J . Descriptions of radio resource management and LTE RL60. Feature Descriptions and Instructions telecom features Management data No alarms related to this feature Measurements and counters The number of measurements (A3/A5or A4) is allowed to extend to N=6 parallel measurements. 5. Feature Descriptions and Instructions Descriptions of transport and transmission features 5 Descriptions of transport and transmission features 5.1. Operator benefits This feature supports migration of the mobile operator networks and IP transport networks from IPv4 to IPv6.1. the eNB supports IPv4 for the IPsec tunnel layer. 5.IPv6 for U/C-Plane functional description 5.1.1.IPv6 for U/C-Plane benefits End-user benefits This feature does not affect the end-user experience.1 Description of LTE125: IPv6 for U/C-Plane Introduction to the feature The eNB supports IPv6 for User-and Control- Plane.1.1 LTE125: IPv6 for U/C-Plane 5. In addition.1. Table 123 Software requirements System release Flexi Multiradio BTS Flexi Multiradio 10 OMS BTS RL60 Not supported LBTS6.2 LTE125 .3.IPv6 for U/C-Plane requirements The table lists the software required for this feature.1.1 LTE125 . The Management- and Synchronization-Plane and also Site Support Equipment (SSE) remain with IPv4.3 LTE125 .0 Not relevant UE NetAct MME SAE GW Not relevant NetAct8 EP1 Not relevant Not relevant Hardware requirements The feature requires the FSMF system module (with and without FTIF).1. LTE RL60.1.1 Migration Step 1 DN09185955 Issue: 01J © 2016 Nokia 215 . 5. IPv4 Addr. the eNB is switched back to IPv4. migration step fails. IPv4 routes and IPsecv4 policies of the previous configuration setup are still available. Principally this can be solved with the download of the original IPv4-based configuration file. IPsec. IPv6-to-IPv4. C S IPsecv4tunnel NoneorsingleVLAN S-Plane M-Plane IPv4Addr. This means the other way round. that all IPv4 addresses. Step 2 After successful backhaul network tests the second and final migration step for the operator is to configure the new IPv6 U- and C-Plane addresses in addition and then bind the U- and C- applications to the corresponding IPv6 address. LTE125FAF=FALSE Ethernet IPv4 C-P Plane IPv4 Addr. Figure 7 Example Configuration: IPv6 migration support ApplicationIPaddresses NetworkIPv4/v6Interfaceaddresses NetworkInterface eNB IPv6Address IPv6 U-Plane U IPv4Addr. M SSEIPv4 LMP Application Network Application IP Address IPv4 IPv4 NetworkInterface IPv6 IPv6 IP Address The stable IPv4 configuration proceeds to work whereas at the network IP interfaces. is using the network IPv4/v6 interface addresses. For this case LTE125 FAF is set to "TRUE". This means in detail that the operator runs the eNB under stable IPv4 operation conditions and has the additional possibility to do in parallel the network test with the new IPv6 based backhaul network. Feature Descriptions and Instructions In the first migration step it is very helpful for operators to remain with the working eNB under IPv4 as long as the operator is really sure that the new IPv6 network works. IPv6 interfaces are available (Dual Stack) for parallel interconnection to the mobile backhaul. Descriptions of transport and transmission features LTE RL60. The figure shows an eNB local address configuration with IPsec enabled 216 © 2016 Nokia DN09185955 Issue: 01J . in addition to the existing network IPv4 interfaces. and final. The figure shows a configuring example. If the second. as fast as possible. However. the previous stable running environment. The LTE125: IPv6 for U/C-Plane feature provides here an IP address pre-configuration mechanism which allows the operator to pre-configure all necessary relevant IPv6 addresses and then activate the eNB operation with IPv6 applications in one step by configuring the LTE125 FAF only. the eNB allows not only the pre-configuration but also the conservation of configuration setups. The U/C/M- applications are bound to virtual IPv4 addresses (VIPs). So the switch back. is easily done by setting the LTE125 FAF from TRUE-to-FALSE. in this case enabled. also after the IPv6 U/C-Plane activation (LTE125 FAF = TRUE).3. In this case it is very helpful that the working IPv4 U/C-Plane setup remains stored on the eNB. Both fields are referred as local IPv4/v6 address field pair.1.1. Then it is simple to switch between both stored U/C-Plane setups. Feature Descriptions and Instructions Descriptions of transport and transmission features Figure 8 Example configuration: U/C - application binding to IPv6. Following different types of remote C- and U-Plane IP addresses are available in the eNB: • S1-U: GTP-U path supervision towards S-GW • S1-C: C-Plane towards MME DN09185955 Issue: 01J © 2016 Nokia 217 .2 Local IP Address Configuration Each configurable local U- and C- Plane Application IP address and each local Network IP Interface address is represented by two configurable IP address fields. IPsec enabled ApplicationIPaddresses NetworkIPv4/v6Interfaceaddresses NetworkInterface eNB IPv6Address IPv6 U-Plane U IPv6Addr. The first address field is configurable with one IP address in IPv4 format whereas the second address field is configurable with one IP address in IPv6 format. Recall here that the new IPv6 U/C-Plane setup is already stored in the IPv6 U/C-Plane setup pre- configuration. Not only the backhaul and the ePC equipment in the operator's network must be tested with IPv6. g Note: The switch of the LTE125 FAF state requires always a BTS restart.1. M SSEIPv4 LMP Application Network Application IP Address IPv4 IPv4 NetworkInterface IPv6 IPv6 IP Address 5. The switch-over between IPv4 and IPv6 setups is controlled with LTE125 FAF FALSE or TRUE.1. LTE125FAF=TRUE Ethernet IPv4 C-P Plane IPv6 Addr.3 Remote U/C-Plane IP Address Configuration In LTE125: IPv6 for U/C-Plane now all of the configurable remote U- and C- Plane Application IP addresses are available for both IP versions.1 Fast Fallback mechanism The introduction of the IPv6 technology is challenging for the operator. 5. IPv4 Addr.1. 5. LTE RL60.3.3.1.1. C S IPsecv4tunnel NoneorsingleVLAN S-Plane M-Plane IPv4Addr. but also in many cases the equipment has to support IPv4/v6 Dual Stack capability because non-migrated and migrated equipment must co-exist and has also some dependencies. Feature Descriptions and Instructions • X2: C-Plane towards adjacent eNBs For each remote U- and C- Plane peer the operator assigns only one IP address/version. the eNb goes on air only if the MME#0 address matches with the current IP version (according to IPv6 FAF). the eNb goes on air only if there is an MME of the main operator (according to p) whose address matches with the current IP version (according to IPv6 FAF).1. The selected remote peers and corresponding IP addresses/version are used during eNB operation. • If S1 flex is enabled. However the eNB selects from the address list of configured remote U- and C- Plane peers those peers whose IP addresses/version are according to the LTE125 FAF status. Each of the remote U- and C- Plane peers is configurable either in IPv4 or in IPv6.IPv6 for U/C-Plane system impact Interdependencies between features • LTE1: S1/X2 Data Path Management 218 © 2016 Nokia DN09185955 Issue: 01J . • if LTE125 FAF = FALSE only IPv4 remote C- and U-Plane address groups is used during operation • if LTE125 FAF = TRUE only IPv6 remote C- and U-Plane address groups is used during operation. g Note: Whether the eNB then goes on air depends of the status of the S1 flex feature: • If S1 flex is disabled. Figure 9 Migration example with IPsecv4/v6 tunneling in Transport Network U/C-planeapplicationsareboundtovirtualIPaddresses S1 (thisexampleshowsapplicationofIPsecbasedonIPv4) HO MME U/C-plane IPv4/v6 SAE-GW M-plane IPv4/v6 IPv4 IPv6 ePCequipmentshall L2/L1 beeNBIPversionaware IPv4 IPv4 IPsecv4 IPv4/IPv6 L2/L1 operatornetwork IPv4 transportnetwork IPv4<->IPv6HostviaS1 RANisland SEG eNB IPv4 IPv4 IPv4 existingRANunchanged L2/L1 O&M IPv4 eNB SEG IPv4 IPv4 eNB U/C-plane IPv4 IPv4/v6 M-plane transportnetwork RANisland IPv6 IPv4 newRAN IPsecv4 application transport eNB L2/L1 IPaddresses network IPv4/v6 IPv4 IPv4 IPv6 IPv6 5.1. To keep the view simpler the figure is focused on U/C/M-Plane only.4 LTE125. The following figure shows how the handover communication between neighbor RAN- islands of different IP versions works. Descriptions of transport and transmission features LTE RL60. In case when LTE125- IPv6 for U/C-Plane system impact is activated the longer IPv6 headers on application IP layer and possibly IPsec layer require additional bandwidth and packet processing performance. Except IPv6 U/C-Plane traffic the LTE FW also considers IPv6 traffic from the Link Local Address and IPv6 Neighbor Disovery multicast traffic. • LTE866: Fast IP Re-Routing BFD bound Static Routes is configurable in addition for IPv6 based U/C-Plane traffic. The C-Plane connection to the MME is configurable either in IPv4 or IPv6 additionally. • LTE689: LTE IPsec Support IPsec tunneling is supported in addition IPv6 at the inner IP layer. • LTE782: ANR - Intra-LTE. The IP version on the secondary IP address shall be identical with the IP version of the primary IP address.5 Gbit/s throughput performance (DL+UL) with or without IPSec at the transport interface. • LTE592: Link Supervision with BFD The LTE592: Link Supervision with BFD feature is configurable in addition with IPv6 addresses. • LTE574: IP Transport Network Measurement DN09185955 Issue: 01J © 2016 Nokia 219 . • LTE649: QoS aware Ethernet Switching The LTE649: QoS aware Ethernet Switchingfeature supports DSCP prioritization scheduling with DSCP priority extraction from IPv4- and IPv6- headers. • LTE734: Transport throughput performance The Flexi Transport sub-module supports (at least) 1. • LTE131: Traffic prioritization on IP layer (Diffserv) The eNB IP layer DSCP (Diffserv) prioritization scheduler supports IP traffic scheduling in IPv4 and in addition IPv6. LTE RL60. • LTE492: ANR The LTE492: ANR feature is controlled via the NetAct. • LTE664: LTE transport protocol stack According to 3GPP specification. • LTE129: Traffic prioritization on Ethernet layer DSCP priority mapping to Ethernet based Priority Code Points (PCP) is supported in IP4- and IPv6- headers. • LTE775: SCTP multi-homing (MME) The LTE775: SCTP multi-homing (MME) feature supports IPv6. • LTE692: LTE Firewall Support The LTE Firewall protects in addition IPv6 traffic. Intra-frequency - Fully UE based feature provides the IPv6 addresses of adjacent eNBs triggered by UEs. • LTE931: Ethernet Jumbo Frames Although the LTE931: Ethernet Jumbo Frames feature is already prepared for IPv6 the corresponding extended MTU size for IPv6 in the Flexi Multiradio 10 BTS HW is tested with IPv6 Jumbo Frame traffic. while the outer layer (IPsec tunnel termination) is limited to IPv4. GTP-U data tunnel for user data transport and SCTP protocol for signaling data uses IPv6. The inner IP layer version and outer IP layer version might be different. The NetAct provides the adjacent eNB IPv6 addresses. Feature Descriptions and Instructions Descriptions of transport and transmission features User data and signaling data transport over S1 and X2 is supported. the U-plane stack is based on GTP-U/UDP/IP and the C-plane stack is based on SCTP/IP. The performance of the sub-module must be sufficient to cover also the bandwidth/performance needs of the LTE125- IPv6 for U/C-Plane system impact feature. The U- and C-Plane IP version are configurable for IPv6. Intra-frequency - Fully UE based The LTE782: ANR - Intra-LTE. • LTE505: Transport Separation for RAN Sharing All operators sharing the same RAN use the same IP version for U/C-Plane. The LTE125- IPv6 for U/C-Plane feature is applied in Flexi Multiradio 10 BTS HW. either it is at one location or is it a distributed processing. • LTE163: Subscriber and Equipment Trace The Tracing Feature. UDP checksum calculation for an IP host means calculation with insertion of the checksum at the TX side and calculation with check at the RX side. as part of the M-Plane. for example during startup. So the UDP checksum calculation requires some HW/SW resources from the eNB transport related subsystem. in which ICMP messages are transmitted with DSCP 0 instead of the configured value. g Note: During reconfiguration/setup of the BTS Firewall. • How many HW/SW resources must be reserved and are there enough resources left for other applications/tasks. The HW processes the UDP checksum calculation of unfragmented IP packets anyway with the built-in HW accelerators. the complete U-Plane application traffic requires UDP checksum calculation. Impact on network and network element management tools This feature has no impact on network management or network element management tools. and this HW uses a high-performance multi-core processing unit with integrated HW accelerators. • LTE1401: Measurement based TAC The LTE1401: Measurement based TAC feature has to measure the used user bandwidth for the TAC. remains with IPv4 when the LTE125- IPv6 for U/C-Plane system impact feature is enabled. For example. • LTE433: Cell Trace The Tracing Feature. remains with IPv4 when the LTE125- IPv6 for U/C-Plane system impact feature is enabled. The UDP protocol is represented in the eNB protocol stack in the U-Plane transport with GTP-U/UDP/IPv6 termination. If the LTE125- IPv6 for U/C-Plane system impact feature is enabled all operators use IPv6 for U/C-Plane. This means that most of the transmitted/received IPv6 packets applies UDP checksum calculation. IPv6 requires UDP checksum calculation mandatorily (according to RFC 2460). Therefore. Therefore the UDP checksum calculation is checked about possible performance impact in the eNB HW/SW. Each operator shall configure separate application IPv6 addresses for U- and C-Plane. Impact on system performance and capacity This feature impacts system performance as follows: In the IPv4 standard the UDP checksum calculation is optional. At the end of the day the result is: • The UDP checksum processing location is known. This feature impacts capacity as follows: 220 © 2016 Nokia DN09185955 Issue: 01J . Now with the LTE125- IPv6 for U/C-Plane system impact feature also IPv6 user packets are considered for the traffic to be measured. it is not implemented up to now in the existing eNB IPv4 transport. Impact on interfaces This feature has no impact on interfaces. there may be a short phase. Descriptions of transport and transmission features LTE RL60. as part of the M-Plane. Feature Descriptions and Instructions IP transport measurements is applicable in addition for IPv6 based U/C-Plane traffic. However. irrelevant of the IP version the packets belong to.IPv6 for U/C-Plane management data For information on alarm. see Reference documentation. The warning contains the corresponding IP address. The DAD detects those duplicated IP addresses and prohibits the operation of this IP address in the BTS. g Note: The corresponding Fault has the Fault ID: 61632: IPV6_DUPLICATE_ADDRESS_DETECTED Meaning: During the BTS IP address configuration the BTS tests the direct attached network whether other. key performance indicator.5 LTE125. Check the reason for the fault from the supplementary information fields and supplementary text field of the alarm. Alarms Table 124 New Alarms Alarm ID Alarm name Meaning of the alarm 7665 BASE STATION A transmission fault (or faults) has occured in TRANSMISSION ALARM the BTS.1. Key performance indicators There are no key performance indicators related to this feature. counter. on the network uses already same IP addresses on their network IP interfaces. Feature Descriptions and Instructions Descriptions of transport and transmission features In the LTE125- IPv6 for U/C-Plane feature on eNB IP transport level the longer header size of the IPv6 header (40 Byte basic header plus extension headers) compared with the IPv4 header (20 Bytes) requires more link bandwidth. All existing IPv4 based counters collect both IPv4 and IPv6 packets together. Parameters New parameters lists parameters introduced with this feature. Measurements and counters There are no additional measurements and counters related to this feature. and parameter documents. in the end to transport the same air interface payload traffic over the Ethernet-based backhaul cost with IPv6 transport protocol more bandwidth than with IPv4 transport protocol. That means.1. and supplementary information are shown in the original FTM format. This means that the alarm number. already configured BTSs. For each DAD event a separate reporting is indicated. LTE RL60. In NetAct this alarm is shown in opened format. DN09185955 Issue: 01J © 2016 Nokia 221 . 5. alarm text. This alarm is an encapsulation alarm that is used to transfer the Flexi Transport Submodule (FTM) alarm data over the BTS O&M connection through iOMS to NetAct. IPv6 for U/C-Plane sales information Table 127 Sales information BSW/ASW License control in License control Activated by default network element attributes ASW No 222 © 2016 Nokia DN09185955 Issue: 01J .1.6 LTE125. Feature Descriptions and Instructions Table 125 New parameters Full name Abbreviated name Managed object Feature Activation Flag IPv6 For U/C. Descriptions of transport and transmission features LTE RL60. actIpv6 IPNO Plane Control plane IPv6 address cPlaneIpv6Address IPNO User plane IPv6 address uPlaneIpv6Address IPNO Neighbor Solicitation Message retransTimer IPNO Retransmit Timer Identifier Of The IPv6 Routing Table ipv6RoutingTableId IPRTV6 Static IPv6 Routes Set staticIpv6Routes IPRTV6 local Ip Prefix Length localIpPrefixLength IPSECC remote Ip Prefix Length remoteIpPrefixLength IPSECC VLAN Ethernet Network Interface IPv6 localIpv6PrefixLength IVIF Prefix-Length Plain Ethernet Network Interface IPv6 localIpv6PrefixLength IEIF Prefix-Length Table 126 New Parameters with structure Static IPv6 Routes Set (staticIpv6Routes) Full name Abbreviated name Managed Object Structure BFD route protection bfdId IPRTV6 Static IPv6 Routes Set session identifier (staticIpv6Routes) staticIpv6Routes destIpv6Addr IPRTV6 Static IPv6 Routes Set (staticIpv6Routes) Destination IPv6 Prefix destinationIpv6PrefixL IPRTV6 Static IPv6 Routes Set Length ength (staticIpv6Routes) Gateway IPv6 gatewayIpv6Addr IPRTV6 Static IPv6 Routes Set Address (staticIpv6Routes) Preference value of preference IPRTV6 Static IPv6 Routes Set the route (staticIpv6Routes) 5.1. Commissioning wizard a) Go to the Application Addresses page. Restart of the eNB is required after the activation of this feature.2 Activating and configuring LTE125: IPv6 for U/C-Plane Before you start The eNB must be already commissioned. perform the steps described in this procedure. 2 Activate/Configure the LTE125. Activation via BTS SM. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. LTE RL60. DN09185955 Issue: 01J © 2016 Nokia 223 . Table 128 Parameters used for activating and configuring LTE125- IPv6 for U/C-Plane Parameter Purpose Requires eNB restart or object locking Feature Activation Flag activation flag restart for IPv6 (actIpv6) Control plane IPv6 mandatory configuration restart address (cPlaneIpv6Address) User plane IPv6 address mandatory configuration restart (uPlaneIpv6Address) Local IP address optional configuration no (localIpAddress) local Ip Prefix Length optional configuration no (localIpPrefixLength) Remote IP address optional configuration no (remotelIpAddress) remote Ip Prefix Length optional configuration no (remoteIpPrefixLength) Primary IPv4/v6 address optional configuration no (ipAddrPrim) Secondary IPv4/v6 optional configuration no address (ipAddrSec) C-Plane IPv4/v6 Address optional configuration no of Neighbor eNB (cPlaneIpAddr) PCI-IP Map (IPv4/IPv6 optional configuration no Address ipAdr) Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager.1. The BTS Site Manager (BTSSM) can be connected to the eNB either locally or remotely. Feature Descriptions and Instructions Descriptions of transport and transmission features 5.IPv6 for U/C-Plane. Expected outcome The feature LTE125 - IPv6 for U/C-Plane is deactivated. Expected outcome The feature LTE125 - IPv6 for U/C-Plane is activated. Descriptions of transport and transmission features LTE RL60. The BTS Site Manager (BTSSM) can be connected to the eNB either locally or remotely. The Feature Activation Flag for IPv6 (actIpv6) parameter is used for deactivation.1. Feature Descriptions and Instructions b) Check the Dual stack IPv4/IPv6 in use for user plane and control plane checkbox. perform the steps described in this procedure. Restart of the eNB is required after activation of this feature.IPv6 for U/C-Plane. b) Uncheck the Dual stack IPv4/IPv6 in use for user plane and control plane checkbox. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. d) Insert a valid IPv6 address in the field for the Control plane.IPv6 for U/C-Plane Before you start The eNB must be already commissioned. g Note: The LNMME-0 must already have a valid IPv6 address - Primary IPv4/v6 address (ipAddrPrim) 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. 5. 2 Deactivate the LTE125. In this section choose send all parameters (requires reset). Activation via BTS SM a) Go to the Application Addresses page. 224 © 2016 Nokia DN09185955 Issue: 01J .3 Deactivating LTE125. Modification of this parameter requires eNB restart. c) Insert a valid IPv6 address in the field for the User plane. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. • In extreme situations. • Even the best resilience solution still poses the potential risk that unexpected failures happen. also the eNB itself can be the root cause for an IPsec failure. 5. based on the concept. it has to be checked carefully in case the feature is used in other scenarios if it matches with customer’s expectations and if existing limitations are acceptable. the IPsec at the eNB can be switched off in an operator-controlled way. LTE RL60. which is recognized and accepted by the target customer. depending on duration of Security Gateway HA cluster failure. • Besides the Security Gateway respectively Security Gateway HA cluster. if the eNB is managed through the IPsec tunnel. with stateful failover. the IPSec becomes a severe point of failure which cannot be circumvented. 5. due to configuration errors or certificate problems.3.1. even site visit would be required. • Security Gateway resilience is broadly implemented by operating a pair of GWs in a HA (high availability) cluster. one GW being active. • In failure case it is not possible to deactivate IPsec in the eNB.1. the feature implies a possible security risk. one being standby. but might not be tolerated by other customers.2. e.1 LTE1390: IPsec Emergency Bypass benefits End-user benefits Short network outage in case of severe IPsec failure. not requiring any site visit. thus eNB remains from operator and maintenance perspective not reachable. DN09185955 Issue: 01J © 2016 Nokia 225 .2.g. which are thus not covered by the solution and might affect the whole HA cluster. Feature Descriptions and Instructions Descriptions of transport and transmission features 5. Further. Operator benefits This feature provides the following benefits to the operator: The feature allows to limit the network outage time in case of a severe IPsec cluster failure to a minimum. The limitation and the possible security risk are described in section 1.2 LTE1390: Emergency Bypass requirements The table lists the software required for this feature.1 Description of LTE1390: IPsec Emergency Bypass Introduction to the feature In case an eNB detects a severe IPsec failure. Therefore. • If whole Security Gateway HA cluster fails larger area will go out of service. The feature fulfills a particular demand of a customer and as such is tightly aligned with the customer’s use case and requirements.2 LTE1390: IPsec Emergency Bypass 5. The details are listed below: • Once the feature LTE1390: IPsec Emergency Bypass is introduced.2. Switching back from IPsec Emergency bypass mode to IPsec mode is exclusively controlled by the operator. In case an IPsec tunnel cannot established or an established one becomes non- operational it enters IPsec Emergency Bypass "probing state".0 Not relevant Table 129 Software requirements UE NetAct MME SAE GW Not relevant NetAct8 EP1 Not relevant Not relevant Hardware requirements This feature requires no new or additional hardware. to check allowance for switching off IPsec The IP address of the Control Server and the timer that controls in what interval eNB accesses the Control Server is configurable in the eNB. the operator typically makes the Control Server accessible by reconfiguration of the core network edge router and/or Security Gateway to accept unprotected traffic.3 LTE1390: IPsec Emergency Bypass functional description The eNB supervises the status of the configured IPsec tunnels. Feature Descriptions and Instructions System release Flexi Multiradio BTS Flexi Multiradio 10 OMS BTS RL60 LBTS6. 5.2. Actual duration depends on the nature of the failure. Reachability of this server is controlled by the operator and in this sense is used as "switch" to allow the eNB to enter active state. stops accessing the Control Server. An IPsec tunnel is regarded as IKE security association with one or more related IPsec (ESP) security associations. IPsec Emergency Bypass state transition from "probing" to "active" happens if the Control Server is reachable and provides the valid return message (ICMP Echo Reply message with source address set to Control Server’s IP address and destination address set to eNB M-plane IP address).0 LBTS6. i. it exits the "probing" state. After having concluded a severe IPsec failure. outside IPsec tunnel(s). 226 © 2016 Nokia DN09185955 Issue: 01J . IKE version and timer configuration with respect to Dead Peer Detection. and ignores return messages from it. Entering "probing" state after failure occurrence will not take more than five minutes.e. During probing state the eNB: • continuously retries establishment of non-operational IPsec tunnels as specified in the IPsec standards • periodically accesses an operator-controlled server by sending unprotected ICMP Echo Request (Ping) messages. In case eNB in "probing" state succeeds with its re-establishment attempts for all failed IPSec tunnels. Descriptions of transport and transmission features LTE RL60.1. g Note: It is not recommended to apply IPsec emergency bypass feature together with LTE505: Transport Separation for RAN Sharing unless this is clearly agreed among operators. Hence. Figure 10 Traffic path in IPsec Emergency Bypass mode Un-trustednetwork Trustednetwork Control BTS Server Permissioncheck outsidetunnel TrafficpathinIPsecmode TrafficpathinIPsecEmergencymode 5. he could trigger entering of "active state" if he manages to interfere eNB - Security Gateway communication (e. LTE RL60. for example in combination with feature LTE505: Transport Separation for RAN Sharing.4 LTE1390: IPsec Emergency Bypass system impact Interdependencies between features The feature can only be applied in conjunction with LTE689: IPsec Support . default gateway and firewall rules as before. If agreed. using same VLAN ID. The feature does not support switching off IPsec selective per tunnel endpoint. When leaving this state IPsec is operational again and the eNB tries to establish all IPsec tunnels as per configuration. This risk might be rated as acceptable depending on the customer's use case. but switches off IPSec completely. "Active state" will last until it is either exited by an operator command via eNB management interface or eNB reboot occurs. application IP addresses.g. DN09185955 Issue: 01J © 2016 Nokia 227 .2. that all connected SEGs (two in the standard case) need to be reconfigured to accept unprotected traffic when operator in charge decides to enter IPsec emergency active state. Thus it is not suited for scenarios where multiple Security Gateways are connected to the eNB.1. it means. Feature Descriptions and Instructions Descriptions of transport and transmission features When entering IPsec Emergency Bypass "active state" all traffic is sent unprotected to same peers. interface IP address. The feature implies a possible security risk due to the fact that entering of IPsec Emergency Bypass "active state" is controlled by means of unprotected communication with the Control Server. Consequently only unprotected traffic is accepted in receive direction. enforce time outs) such that eNB detects IPsec failure although there is no IPsec problem. An attacker might get knowledge about the valid return message (ICMP Echo Reply) and could fake this message towards eNB in "probing state". Feature Descriptions and Instructions Impact on interfaces This feature has no impact on interfaces. key performance indicator. and parameter documents. counter. Impact on system performance and capacity This feature has no impact on system performance and capacity.1. Measurements and counters There are no measurements and counters introduced with this feature. if a policy exists with same traffic selectors. However. the user must not configure any bypass/discard/protect policies with the following traffic selector: localIpAddress = eNB M-plane IP address/32 remoteIpAddress = Control Server IP address/32 protocol = 1 (ICMP) Rationale: When the IPsec Emergency Bypass feature is enabled. Key performance indicators There are no key performance indicators related to this feature. BTS has entered IPsec emergency bypass active state where configured IPsec policies are ignored and all traffic is sent unprotected. g Note: When the IPsec Emergency Bypass feature is enabled. This might cause the ping to fail depending on the configuration. a bypass policy with highest priority to allow ping traffic towards the Control Server will be added by the system. Parameters 228 © 2016 Nokia DN09185955 Issue: 01J . addition of this bypass policy will fail. 5. see Reference documentation. Impact on network and network element management tools This feature has no impact on network management or network element management tools.5 LTE1390: IPsec Emergency Bypass management data For information on alarm.2. Alarms Table 130 New Alarms Alarm ID Alarm name Meaning of the alarm 61639 IPSEC_EMERGENCY_BYPA BTS has entered IPsec emergency bypass SS_ACTIVE active state. Descriptions of transport and transmission features LTE RL60. 2.2 Activating the LTE1390: IPsec Emergency Bypass feature using BTS Site Manager Before you start The feature can be activated without the control server. In case of IPsec problems.1.6 LTE1390: IPsec Emergency Bypass sales information Table 132 Sales information BSW/ASW License control in License control Activated by default network element attributes ASW SW Asset Monitoring no No 5. When the control server is available. LTE RL60. the eNB cannot be switched to unprotected traffic. it can be used by the operator to command the deactivation of IPsec in an eNB. Table 133 Parameters used for activating and configuring the LTE1390: IPsec Emergency Bypass feature Parameter name Parameter type Requires eNB restart or object locking IPsec emergency activation flag no bypass enabled (ipSecEmBypassEnabl ed) IPsec emergency mandatory configuration no bypass control server IP address DN09185955 Issue: 01J © 2016 Nokia 229 .2. Feature Descriptions and Instructions Descriptions of transport and transmission features Table 131 New parameters Full name Abbreviated name Managed object IPsec emergency bypass enabled ipSecEmBypassEnabled IPSECC IPsec emergency bypass state ipSecEmBypassState IPSECC IPsec emergency bypass exit active ipSecEmBypassExit IPSECC state request IPsec emergency bypass control server ipSecEmBypassCtrlIpAddr IPSECC IP address IPsec emergency bypass ping retry ipSecEmBypassPingTimer IPSECC timer 5. perform the steps described in this procedure. d) Set the IPsec emergency bypass ping retry timer (ipSecEmBypassPingTimer) in a range between 5. a) Go to the IP security page. Steps To activate the LTE1390: IPsec Emergency Bypass feature. Feature Descriptions and Instructions Table 133 Parameters used for activating and configuring the LTE1390: IPsec Emergency Bypass feature (Cont. b) Check the IP security in use checkbox. 230 © 2016 Nokia DN09185955 Issue: 01J .. Descriptions of transport and transmission features LTE RL60. default value = 30 seconds). 2 Activate the LTE1390: IPsec Emergency Bypass feature.. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. do the following: Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager.300 seconds (step 1 second. c) Specify the IPsec emergency bypass control server IP address (ipSecEmBypassCtrlIpAddr) with a valid IP address in the IP address field.) Parameter name Parameter type Requires eNB restart or object locking (ipSecEmBypassCtrlIp Addr) IPsec emergency mandatory configuration no bypass ping retry timer (ipSecEmBypassPing Timer) IPsec emergency optional configuration no bypass exit active state request (ipSecEmBypassExit) IPsec emergency optional configuration no bypass state (ipSecEmBypassStat e) The LTE689: IPsec Support feature needs to be activated/configured before the activation of the LTE1390: IPsec Emergency Bypass feature. Expected outcome The Bypass status change from “Standby” to “Off” The feature LTE1390: Emergency Bypass is deactivated. b) Uncheck the IPsec emergency bypass enabled (ipSecEmBypassEnabled) checkbox. The feature LTE1390: IPsec Emergency Bypass must be activated. Modification of this parameter does not require eNB restart.1 Description of LTE1401: Measurement based TAC Introduction to the feature DN09185955 Issue: 01J © 2016 Nokia 231 . 5. LTE RL60. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. The BTS Site Manager (BTSSM) can be connected to the eNB either locally or remotely. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure perform the steps described in this procedure. Feature Descriptions and Instructions Descriptions of transport and transmission features 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.2. 2 Deactivate the feature LTE1390: IPsec Emergency Bypass a) Go to the IP Security page.3.3 Deactivating LTE1390: IPsec Emergency Bypass Before you start The eNB must be already commissioned.3 LTE1401: Measurement based TAC 5. In the BTS Site Manager. the Bypass status changes from “Off” to “Standby. 5. The IPsec emergency bypass enabled (ipSecEmBypassEnabled) parameter is used for deactivation.” Expected outcome The LTE1390: IPsec Emergency Bypass feature is configured and activated in the eNB. 254 as GBR traffic. This means an operator can specify QCIs in the value range 128.2 LTE1401:Measurement based TAC requirements The table lists the software required for this feature. A measurement based approach promises the following benefits: • MB-TAC avoids the main problem that a key parameter (packet size per traffic class and per UE) is not available in the eNB. • MB-TAC avoids any assumptions about codec types (for voice or video) • MB-TAC avoids the introduction of an activity factor (which is not accurate enough when QCI=1.0 Not relevant UE NetAct MME SAE GW Not relevant NetAct8 EP1 Not relevant Not relevant 232 © 2016 Nokia DN09185955 Issue: 01J . and 4 are used. In particular.0 LBTS6. Descriptions of transport and transmission features LTE RL60. and use the information about the current load for the decision whether to accept or reject a new connection.3.3.1 LTE1401:Measurement based TAC benefits End-user benefits This feature improves QoS for GBR services with QCI=2. • MB-TAC works also if different kinds of traffic types share a common QCI (where QCI=1.. Feature Descriptions and Instructions The Measurement Based Transport Admission Control (MBTAC) grants or rejects requests based on measurement of the actually used transport bandwidth. which would then be included in the TAC. which they cannot know at all. MBTAC does not force the operator to configure speculative values like the “expected average packet size per QCI”. It is a functional enhancement of the feature LTE144 Transport Admission Control which is based on book-keeping of estimated transport bearer bandwidths.2.3. Operator benefits The essence of the Measurement-based Transport Admission Control (MBTAC) is to measure the load of GBR traffic on the transport network.4). because this factor essentially reflects user behavior in voice calls. 3..4. 5. • The feature also includes "operator specific QCIs" according to feature LTE1231: Operator specific GBR QCIs.1.1. Table 134 Software requirements System release Flexi Multiradio BTS Flexi Multiradio 10 OMS BTS RL60 LBTS6.3. 2. and is not applicable for other kinds of traffic or in cases of traffic mix) • It relies on measured system behavior and not on speculations over user traffic or operator configurations. This "Transport Admission Control" is done for Guaranteed Bit Rate ("GBR") traffic only. 5. Only if both decisions are "accept". the measurement of the traffic in the LTE system supervised by MB-TAC-includes traffic with QCI values 1. the TAC is called whenever a connection with QCI=1. such that existing Service Level Agreements (SLA) at the transport level for GBR traffic are kept. Table 135 Standardized QCI characteristics QCI Resource Priority Packet delay Packet error Example services type budget loss rate (NOTE 1) (NOTE 2) 1 GBR 2 100 ms 10-2 Conversational voice (NOTE 3) 2 4 150 ms 10-3 Conversational video (live streaming) (NOTE 3) 3 3 50 ms 10-3 Real time gaming (NOTE 3) 4 5 300 ms 10-6 Non-Conversational video (buffered streaming) (NOTE 3) DN09185955 Issue: 01J © 2016 Nokia 233 . New calls (guaranteed bit rate services) are accepted or rejected. TAC measures such types of traffic terminating on the eNB where the TAC instance is located. meaning that: • the bandwidth consumed for GBR connections in the transport network is continuously measured at the transport network interface of an eNB. plus traffic with QCI=5. the measured values and an estimate of future bandwidth consumption of the connection candidates to be set-up. More precisely. The decision about acceptance of a new GBR connection is done separately for uplink and downlink.2. 5.4. Feature Descriptions and Instructions Descriptions of transport and transmission features Hardware requirements This feature requires no new or additional hardware. depending on the transport load situation. TAC accepts set-up of this new connection.4 is to be established.3. LTE RL60. The main purpose of the feature is to limit the total volume of the measured traffic.3 LTE1401:Measurement based TAC functional description The Measurement Based Transport Admission Control (MBTAC) is continuously measuring the actual traffic in DL and UL.3. However. • the decision whether to accept or reject a new GBR connection is based on both. a measurement-based algorithm is used. The table lists the standardized QCI definitions specified in 3GPP TS 23. For traffic which requires a guaranteed bit rate (GBR). This "Transport Admission Control" is done for Guaranteed Bit Rate ("GBR") traffic only. and that QoS for existing transport bearers is maintained by not exceeding the allowed bandwidth limits. plus synchronization traffic.2.203 v831.1.3. Such limits may exist at both the Ethernet layer and the IP layer. plus C-plane traffic. Only if system resources on both the radio and the transport side are expected to be sufficient for avoiding overload conditions. TAC) in order to control GBR (guaranteed bit rate) user traffic. the air interface and the transport interface. and "normal GBR call". it is possible to implement different priorities for handover. Figure 11 Overview 5. RAC signals to MB-TAC the call types "emergency call".) QCI Resource Priority Packet delay Packet error Example services type budget loss rate (NOTE 1) (NOTE 2) 5 Non-GBR 1 100 ms 10-6 IMS signaling (NOTE 3) NOTE 3):This QCI is typically associated with an operator controlled service.3. Descriptions of transport and transmission features LTE RL60. new GBR connections are accepted. Feature Descriptions and Instructions Table 135 Standardized QCI characteristics (Cont. RAC and TAC expect to have the resources available for the time the connection will be active. Basically. admittance to the system is granted if. for example a service where the SDF aggregate's uplink / downlink packet filters are known at the point in time when the SDF aggregate is authorized. both. By using different bandwidth limits for the admission of these calls. at time of connection request. for example in Metro Ethernet (with arbitrary example values) 234 © 2016 Nokia DN09185955 Issue: 01J . while TAC exists once per eNB. However.3. In case of E-UTRAN this is the point in time when a corresponding dedicated EPS bearer is established / modified. Admission Control is required on both the air interface ("Radio Admission Control". RAC) and for the transport network ("Transport Admission Control".1. "handover call". in particular by avoiding overload conditions on both.1 User scenarios Policed traffic. Both functionalities are located on the eNB. Both units need to co-operate in order to efficiently provide QoS to users. The figure shows both functionalities. RAC instances exist per cell/sector. emergency. and normal GBR calls. and wishes to use up to 20 Mb/s for "GBR" traffic (for example more precisely. Note that additional traffic (C-plane. This 20 Mb/s is not policed. and must not be exceeded to keep QoS for all GBR connections. traffic which is measured by MBTAC. The operator configures: • TAC Limit GBR Normal = 16 Mb/s • TAC Limit GBR Handover = 18 Mb/s • TAC Limit GBR Emergency = 20 Mb/s This means that TAC will accept up to 16 Mb/s for all kinds of connections (normal. for example normal Ethernet (with arbitrary example values) An operator connects the eNBs via a 100 Mb/s transport network. As in the previous example. Impact on network and network element management tools This feature has no impact on network management or network element management tools. and the operator would be willing to allow exceeding the threshold for example for emergency calls.3.4 LTE1401:Measurement based TAC system impact Interdependencies between features • LTE144: Transport Admission Control The feature LTE144: Transport Admission Control is replaced by this one. another 2 Mb/s (18 - 16 Mb/s) are still available for handover or emergency calls. LTE RL60. this 20 Mb/s bandwidth limit is policed. Finally. sync and so on) is included in the MB-TAC measurements. The operator wishes to reserve a part of the bandwidth for emergency calls and for handover connections. Starting with this release. and 4 plus QCI=5. TAC will still accept emergency calls up to the available transmission capacity.1. and synchronization traffic). hand-over. • LTE125: Support for IPv6 MB-TAC supports both IPv4 and IPv6 automatically. The operator wishes to reserve a part of the bandwidth for emergency calls and for handover connections. 3. TAC will still accept emergency calls as long as the threshold of 20 Mb/s is not exceeded. Finally. Impact on interfaces This feature has no impact on interfaces. Feature Descriptions and Instructions Descriptions of transport and transmission features An operator connects eNBs via a 100 Mb/s transport network. 5. emergency). handover. when the GBR load exceeds 18 Mb/s. Impact on system performance and capacity DN09185955 Issue: 01J © 2016 Nokia 235 . emergency). After that. additional traffic (C-plane. sync and so on) is included in the MB-TAC measurements. No policed traffic. Since the operator uses an external provider. The operator configures: • TAC Limit GBR Normal = 16 Mb/s • TAC Limit GBR Handover = 18 Mb/s • TAC Limit GBR Emergency = 100 Mb/s This means that TAC will accept up to 16 Mb/s for all kinds of connections (normal. another 2 Mb/s (18 - 16 Mb/s) are available for hand- over or emergency calls. when the GBR load exceeds 18 Mb/s. and wishes to use up to 20 Mb/s for "GBR" traffic. Transport Admission Control for GBR traffic is handled by LTE1401:Measurement based TAC system impact. After that. this traffic includes traffic with QCI values = 1. 2. C-plane. 3.1. Measurements and counters The list New counters lists counters introduced with this feature. Key performance indicators There are no key performance indicators related to this feature. see Reference documentation. and parameter documents.5 LTE1401:Measurement based TAC management data For information on alarm. Descriptions of transport and transmission features LTE RL60. 236 © 2016 Nokia DN09185955 Issue: 01J . counter. 5. Alarms There are no alarms related to this feature. Parameters The list New parameters lists parameters introduced with this feature. Table 136 New counters Counter ID Counter name Measurement M51136C0 Number of normal GBR connection 51136 - LTE TAC Statistics requests accepted by TAC M51136C1 Number of GBR Handover connection 51136 - LTE TAC Statistics requests accepted by TAC M51136C2 Number of GBR Emergency requests 51136 - LTE TAC Statistics accepted by TAC M51136C3 Number of normal GBR connection 51136 - LTE TAC Statistics requests rejected by TAC M51136C4 Number of GBR Handover connection 51136 - LTE TAC Statistics requests rejected by TAC M51136C5 Number of GBR Emergency requests 51136 - LTE TAC Statistics rejected by TAC M51136C6 UL total GBR mean rate 51136 - LTE TAC Statistics M51136C7 UL total GBR peak rate 51136 - LTE TAC Statistics M51136C8 DL total GBR mean rate 51136 - LTE TAC Statistics M51136C9 DL total GBR peak rate 51136 - LTE TAC Statistics There are no measurements related to this feature. Feature Descriptions and Instructions MBTAC improves key performance regarding GBR connection set-up time. key performance indicator. 5. U-plane. the default values are set to the line speed. The operator "activates" the feature (in the sense of possibly rejecting GBR connection requests) by setting an appropriate lower value for the TAC limits.4 LTE1460: Local and Remote IP Traffic Capturing 5.4. M-plane or S-plane traffic DN09185955 Issue: 01J © 2016 Nokia 237 .2 Activating and configuring LTE1401: Measurement-based Transport Admission Control Before you start This feature needs no activation.6 LTE1401:Measurement based TAC sales information Table 138 Sales information BSW/ASW License control in License control Activated by default network element attributes BSW Yes 5. so that all GBR connection requests are accepted by default. Feature Descriptions and Instructions Descriptions of transport and transmission features Table 137 New parameters Full name Abbreviated name Managed object TAC Limit GBR Normal tacLimitGbrNormal LTAC TAC Limit GBR Handover tacLimitGbrHandover LTAC TAC Limit GBR Emergency tacLimitGbrEmergency LTAC 5. However.3.3.1. LTE RL60.3.1 Description of LTE1460: Local and Remote IP Traffic Capturing Introduction to the feature The LTE1460: Local and Remote IP Traffic Capturing feature enables Nokia Technical Support. 5.3 Deactivating LTE1401: Measurement-based Transport Admission Control Before you start This feature needs no deactivation. The feature is always active in the sense that the functionality is always available. R&D personnel and as well customers' staff to capture the IP traffic of an eNB and fetch it for later offline root-cause analysis. With this feature it is possible to: • capture ingress and egress IP traffic such as C-plane. Table 139 Software requirements System release Flexi Multiradio BTS Flexi Multiradio 10 OMS BTS RL60 Not supported LBTS6. • Technical Support engineers will get the transport capture files as often as possible included in the ticket.1. • Maintenance engineers are able to capture BTS/eNB traffic when being connected remotely to investigate unexpected BTS/eNB behavior.4.0 Not relevant UE NetAct MME SAE GW Not relevant NetAct8 EP1 Not relevant Not relevant Hardware requirements 238 © 2016 Nokia DN09185955 Issue: 01J . • For local use. prove correct BTS/eNB behavior and evaluate actual network performance. • Technical Support engineers get local unlimited IP traffic capturing including U-plane headers to cover all possible faults and use cases that require transport traces. cost.1. • Maintenance engineers can avoid extra site visits to retrieve transport capture files so they save time. • allows capturing and storage (compressed libpcap file) of at least 60 s of single UE peak data • IPv6 capturing is supported 5. Feature Descriptions and Instructions • Web interface for configuration and capture file retrieval. For remote use libpcap file is created. to significantly reduce the ticket resolving times. 5. compressed and downloaded by user.4. • Maintenance engineers get a robust and simple configuration interface so they can configure the IP traffic capturing even in fault or congestion situations. Operator benefits This feature provides the following benefits to the operator: • Maintenance engineers are able to capture the transport IP traffic related to a single UE at a BTS/eNB in the field to calculate the KPIs. The vendor is able to analyze and solve faults as quickly as possible so that consequences are as minimal as possible. Descriptions of transport and transmission features LTE RL60.1 LTE1460: Local and Remote IP Traffic Capturing benefits End-user benefits This feature does not affect the end-user experience. and effort.2 LTE1460: Local and Remote IP Traffic Capturing requirements The table lists the software required for this feature. Layer 3 internal measurement points can be selected and U-plane can be excluded to maximize capturing duration. trace is streamed to configurable TRS port or LMP. At this capture point downlink traffic is not filtered by the system firewall. The libpcap file format is the main capture file format used in TcpDump/WinDump.Maintenance Engineer) Network Operation Center RNC BTS TransportNetwork IPsec MME/SAE-GW GW Capturing of IP traffic is supported in two different ways: • streaming of the captured IP packets to a locally connected laptop or storage device • capturing into a libpcap file which can be downloaded via local or remote connection. • point A) IP traffic to/from the BTS. The IP traffic capturing functionality is configured via Web interface. Capturing is possible locally and remotely connected from a Network Operations Center. The access to the Web interface is secured with operator-configurable credentials. The NE supports a single IP traffic capturing session at the same time even though the Web interface can support multiple Web sessions at the same time. At this capture point the traffic is captured non- fragmented and IPsec decrypted (if in use). uplink traffic has already passed it. Figure 12 Network Operation Center LocalAccess (e.g. DN09185955 Issue: 01J © 2016 Nokia 239 . Feature Descriptions and Instructions Descriptions of transport and transmission features The feature is not supported by FSMD/FSME system modules and associated Transport module (FTIB and FTLB) 5. TLS-encrypted M-plane is still encrypted. At this capture point the traffic is encrypted (if in use). If TLS is not in use. At all of these capture points. The NE implementation prevents malfunction of the IP traffic capturing session in case of mutliple Web sessions at the same time.3 LTE1460: Local and Remote IP Traffic Capturing functional description The LTE1460: Local and Remote IP Traffic Capturing feature extends the troubleshooting capabilities of a BTS.1. traffic is captured in both ingress and egress direction. Wireshark/TShark. snort.4. • point B) IP traffic to/from the BTS and SSE captured at the transport network interfaces. and many other networking tools. The feature allows the capturing of the BTS backhaul interfaces' IP packet information (ingress and egress IP traffic) at different capture points inside the traffic path of the BTS. LTE RL60. M-plane is contained unencrypted or decrypted (in case of IPsec in use). At capture point B. TWAMP) is always captured if IP traffic capturing is ongoing. the end-user plane payload of unencrypted or decrypted packets is completely stripped off from the captured packets. Feature Descriptions and Instructions g Note: At capture point B. For LTE. the provisioning of the local packet stream and the libpcap file creation and provisioning: 240 © 2016 Nokia DN09185955 Issue: 01J . It is possible to completely exclude the capturing of end-user plane packets (headers). the encrypted part of packets ciphered with IPsec ("inner packet") are stripped off from the captured packets and the IP header of the "outer packet" is captured (not supported in FlexiZone Micro). Throughout a capturing session. FlexiZone Micro just supports mirroring of complete IP packets. g Note: The present feature does not capture errored IP packets. These packets are dropped without capturing. Figure 13 Capture points BaseStation SSL/TLS O&M IPsecGateway IP/MLPPP TDM Function Function termination Interfaces Reassembly Reassembly Fragment Fragment A B Transport Ethernet OtherBaseStation Interface(s) Functions L2Switching (BasebandRadio) Function IPLayerCapturePoints The figure summarizes the capturing mechanism. Descriptions of transport and transmission features LTE RL60. g Note: Excluding the capturing of end-user plane packets (headers) also excludes non- initial fragments of downlink UDP packets with exactly matching user plane traffic source and destination IP addresses. At all capture points the original packets are conveyed unmodified to their destination. capturing into a file is not supported by FlexiZone Micro. capturing is possible at one of the capture points. The capturing is independent of the used layer 2 protocol (for example Ethernet. for example concurrent capturing at multiple points is not required. Especially capturing at point A simplify the troubleshooting since it allows accessing the decrypted traffic. IP/ML-PPP). At capture points A and B. At capture point B. ICMP. the IP header information up to UE level UDP respective UE level TCP header is included. End-user payload is NOT stripped of here. All other packets of IP-based protocols (for example. 8.1. Start IP traffic capturing. Feature Descriptions and Instructions Descriptions of transport and transmission features Figure 14 Capturing mechanism 2. BTS requestmirroringfile captureto 3. • BTS starts the IP traffic capturing. This memory can only be unallocated by a system reset. 3. Before you start BTS transport SW is running 1. 7. Select whether user plane is included. RemoteUser ile gf rin tu libpcapfile p ca st ue req Mirroredfullpacketsresp. 5. (Optionally) Log off from BTS Web interface. libpcapfile capturinghistory libpcapfile 2. • BTS raises IP traffic capturing alarm. Result BTS captures selected IP traffic into ring buffer structure in RAM. LTE RL60. Select libpcap file as output option.4.1 User scenario Activating an IP Traffic Capturing session to libpcap file g Note: The feature LTE1460: Local and Remote IP Traffic Capturing allocates memory once when being started. Connect to BTS Web interface and logon with credentials. DN09185955 Issue: 01J © 2016 Nokia 241 . (Optionally) BTS stops IP traffic capturing after timeout of 24 hours has been reached. LocalEthernet Port BTS functions capturepoint Laptop packettiming information capturedfullpacketsresp. 4. Select measurement point for IP traffic capturing.leadingn bytes(UP)plustiminginformation orstreaming 3. headersonly(UP) Packetstream(ingressandegress) 5. 2. 6. Optionally provide a password for libpcap file encryption.3. • BTS deletes the content of the capturing history data structure. Stopping an IP Traffic Capturing session Before you start IP traffic capturing session ongoing. No memory Available. including PCAP record meta-data. Impact on network and network element management tools This feature has no impact on network and network element management tools. Impact on system performance and capacity System performance IP traffic capturing is competing with normal BTS services for the same resources. While retrying the memory allocation procedure. BTS should abandon trying to allocate memory for the in-memory storage area if minimum memory. and memory allocation failure persists. On the FTM (Flexi Transport module) webpage the following message appears: Local and Remote IP Traffic Capturing feature disabled. System Capacity On FlexiMultiradio 10 HW. Feature Descriptions and Instructions 1. the BTS must provide up to 150 MB. So it might happen that there are not enough resources to concurrently run IP traffic capturing and normal BTS services. the output data rate of local streaming of IP capturing data via the NE Local Management Port is limited to Fast Ethernet since the Local Management Port does not support Gigabit Ethernet. for captured raw IP traffic. Impact on interfaces This feature has no impact on interfaces. for example 40MB. eNB reboot needed to bring-back this functionality… 5. Result Active BTS IP traffic capturing is stopped.4 LTE1460: Local and Remote IP Traffic Capturing system impact Interdependencies between features There are no interdependencies between this and any other feature. • BTS stops writing into the capturing history data structure but does not delete it..4. Stop IP Traffic capturing.1. The user is not notified about this. g Note: For IP traffic capturing. (Optionally) Logoff from BTS web interface. • BTS stops streaming of IP traffic capturing data to local port or. BTS must de-allocate any earlier allocated memory to prevent chances of system instability due to lack of memory for other BTS system components. the IP traffic capturing might drop capturing packets (for example. • BTS clears the IP traffic capturing alarm. 3. Descriptions of transport and transmission features LTE RL60. Logon to BTS web interface. a reboot of the eNB is needed in order to bring the feature back to operational state. in a circular capture buffer. is unavailable. In this situation. IP packets are not captured or streamed). 242 © 2016 Nokia DN09185955 Issue: 01J . As a result it could happen that: • in case of the lack of resources in the packet buffers that prevent from the copy operation of the captured packets in case of local streaming • in case of a lack of allocated processing time for the capturing process • if the data rate of streamed IP traffic capturing data exceeds the available data rate on the Local Ethernet Port If either of these cases happens. 2. 5.6 LTE1460: Local and Remote IP Traffic Capturing sales information Table 141 Sales information BSW/ASW License control in License control Activated by default network element attributes BSW Yes 5.3 Deactivating LTE1460: Local and Remote IP Traffic Capturing Before you start There is no separate feature deactivation scenario for Local streaming of IP packet information. 5. and parameter documents.4. Parameters There are no new parameters related to this feature. see.4. Alarms Table 140 New Alarms Alarm ID Alarm name Meaning of the alarm 7665 Base station Transmission The base station is currently capturing IP traffic Alarm towards a local port or into a file on the base station Measurements and counters There are no new counters or measurements related to this feature. Key performance indicators There are no key performance indicators related to this feature.4. This is embedded in the operator scenario "Local streaming of IP packet information". Feature Descriptions and Instructions Descriptions of transport and transmission features 5. DN09185955 Issue: 01J © 2016 Nokia 243 . LTE RL60.4. counter.1.5 LTE1460: Local and Remote IP Traffic Capturing management data For information on alarm. Reference documentation.1. key performance indicator.2 Activating and configuring LTE1460: Local and Remote IP Traffic Capturing Before you start There is no separate feature activation scenario for Local streaming of IP packet information. Inter-frequency . • To create new NRs. Operator benefits This feature provides the following benefits to the operator: • The LTE556: ANR Intra-LTE. there is no manual configuration needed.0 - UE NetAct MME SAE GW 3GPP Rel-8 NetAct8 EP1 . Table 142 Software requirements System release Flexi Multiradio BTS Flexi Multiradio 10 OMS BTS RL60 LBTS6.UE Based Introduction to the feature The LTE556: ANR Intra-LTE. inter-frequency neighbor cells is based on UE measurements search on demand for the currently unknown intra-LTE. Inter-frequency - UE Based feature enables establishment of new neighbor relations (NRs) between intra-LTE cells with different frequencies. Descriptions of operability features LTE RL60. - Hardware requirements This feature requires the following hardware: • FSMr2 • FSMr3 244 © 2016 Nokia DN09185955 Issue: 01J .1. Inter-frequency - UE Based feature reduces operational expenses in neighbor cell planning and keeps neighbor relations up-to-date.1. inter- frequency neighbor cells.1. Inter-frequency . 6.1 LTE556: ANR Intra-LTE.0 LBTS6.UE Based 6.1.2 Requirements Software requirements The following table lists software required for this feature.1 Description of LTE556: ANR Intra-LTE. Feature Descriptions and Instructions 6 Descriptions of operability features 6. Automatic Neighbor Relation (ANR) for intra-LTE. inter-frequency LTE cells supports the self-configuration of the neighbor cell list for intra-LTE.1 Benefits End-user benefits This feature provides the following benefits to the end-user: • Automatic detection of unknown adjacent intra-LTE. inter-frequency neighbor cells. It can be started to properly update and configure the neighbor cell list for adjacent LTE cells. 6.1. that is: via an A3. To perform this measurement. the ilReacTimer parameter is left at value other than zero. TAC) of a detected unknown PCI at the indicated LTE carrier frequency. on the other hand.3 Functional description With the LTE556: ANR Intra-LTE Inter-frequency UE Based feature. there are no conflicting neighbors. the eNB automatically establishes for its own cells the dedicated LTE inter-frequency neighbor relations (NRs). when the drxInactivityT and the ilReacTimerUl parameters are set as follows: • The drxInactivityT parameter: suggested default value is 20 ms or 10 ms. The eNB informs the operator when new NRs are automatically created. A mechanism is implemented to discover unknown cells with the support of UE measurements. Detection of unknown cells can also be done via LTE inter-frequency mobility events. Feature Descriptions and Instructions Descriptions of operability features 6. • ReportCGI - used to resolve the cell identities (CGI. If. This way of searching for unknown PCIs in named “Passive ANR”. To perform this measurement. DN09185955 Issue: 01J © 2016 Nokia 245 . With this mechanism. UE measurements and ANR modes The UE measurements are as follows: • ReportStrongestCells (RSC) - used to actively detect unknown PCIs at a LTE carrier frequency. The UE reports CGI. This way to search for unknown cells is named “Active ANR”. a complete pre-planning of the neighbor cell configurations is not needed for the automatic configuration and update of intra-LTE inter-frequency neighbor cells. the UE always requires the configuration of a suited DRX profile.1. Inter-frequency UE Based feature is built on the assumption that geographically separated eNB cells might see LTE inter- frequency neighbors that have different CGI with the same physical identity (PCI and eARFCN). g Note: There are important interactions with DRX and the latency reaction timer that need to be considered when using the inter-frequency ANR. The LTE556: ANR Intra-LTE. the UE generally requires the configuration of measurement gaps. The operator only configures the carrier frequencies (and other parameters if needed) that are used by the eNB for the automatic NR detection. the ReportCGI might fail.1. Since the cells of distributed sites are geographically separated. depending on whether the UE sends Ping messages at the point ANR. • The Latency reaction timer feature must be disabled for reliable CGI measurement results in all RF scenarios. A4. or A5 measurement report. LTE RL60. Upon the detection of an unknown cell.PLMN-IDs ECGI EUTRANCellGlobalIdentifier PCI PhysicalCellIdentifier BCCH BroadcastChannel TAC TrackingAreaCode Detection of unknown cells LTE BTS supports detection of unknown cells reported in A3/A4/A5 event-based inter- frequency measurements and inter-frequency reportStrongestCells periodic measurements. This is done by ordering EGCI measurement at the UE.Measurethesignal(PCIx) 2. Descriptions of operability features LTE RL60. The detection of unknown neighbor cells happens during event-triggered inter-frequency measurements or during periodic measurements activated by the Flexi Multiradio BTS for ANR-capable UEs.etc.) 3.RRCmeasurementreport (PCIx. Detection of unknown cells via reportStrongestCells measurements stops as soon as the pre-configured maximum number of automatically created NRs is achieved.TAC.ReportECGI.F2 (carrierfrequency) 1.Reportrequesttoreport 4.F1 eNB. from X2 interface). Inter-frequency UE Based neighbor discovery: radio frequency (RF) part 0. Feature Descriptions and Instructions Figure 15 ANR Intra-LTE. if supported by the UE.ReadECGIfromBCCH ECGIofPCIx 5. Flexi Multiradio BTS tries to resolve the corresponding E-UTRAN cell global identifier (ECGI). Use cases The LTE556: ANR Intra-LTE Inter-frequency UE Based feature supports the following scenarios: • establishment of NRs between the cells of one eNB operating at different carrier frequencies – the carrier frequencies belonging to different or the same frequency bands – the cells at different carrier frequencies fully/partially overlap – the carrier frequencies can be used paired for providing Carrier Aggregation (CA) 246 © 2016 Nokia DN09185955 Issue: 01J . or via any other information locally available (for example.UEMeasurementConfiguration eNB. of different type and fully overlap F1 F2 NR establishment The LTE556: ANR Intra-LTE Inter-frequency UE Based feature enables the eNB to automatically establish its NRs at LTE inter-carrier frequencies with the support of UE measurements. inter- frequency-specific ANR measurements are required. LTE RL60. At the purpose. the LTE carrier frequencies that are used for automatic neighbor cell detection. via ANR profiles. DN09185955 Issue: 01J © 2016 Nokia 247 . for these carrier frequencies. macro and pico) Figure 17 Inter-eNB neighbor cells at different frequency bands. Feature Descriptions and Instructions Descriptions of operability features Figure 16 Intra-eNB neighbor cells at different frequencies and fully overlap F1 F2 • establishment of NRs between cells of different eNBs operating at different carrier frequencies – the carrier frequencies of different eNBs belonging to different or the same frequency bands – the inter-frequency cells of different eNBs fully/partially overlap – the inter-frequency cells of different eNBs are of the same/different types (for example. The eNB then activates. The operator needs to configure. the relevant measurements at the connected UEs. ARRCconnectionestablishment .z.ARRCconnectionestablishment 0.regularDRXprofile...BRRCConnectionReconfiguration (regularDRXprofile..) 7.TACandPLMNidsforPCI1atfreq...PCI8withPCI1thestrongest) 4.. at least one HO preparation must be attempted to that cell from the respective eNB cell.Z. Descriptions of operability features LTE RL60.ANRDRXprofile) eNBstores 5.z..TACandPLMNidsforPCI1atfreq. The eNB informs the operator via BTSSM and the NetAct when a new NR has to be modeled.BRRCconnectionestablishment 2.eNBConfiguration (LTEANRprofilesforfreq.) 1.Fx 1. that is: before adding a UE-resolved LTE inter-frequency neighbor to the relevant eNB cell.AIFHOpreparedtoCellC eNBestablishes forCellAanNR withCellC eNBinformsabout createdNRtowardsCellC LTE ANR method towards target frequency dependent on feature configuration 248 © 2016 Nokia DN09185955 Issue: 01J .z) localmemory 5. Feature Descriptions and Instructions Before (modelled) NR. Figure 18 Automatic establishment of an inter-frequency NR UE UE1 UE2 eNB NetAct CellA. Figure 18: Automatic establishment of an inter-frequency NR shows the affected network entities and interfaces.) 3..z) CellDdatain localmemory 6.ARRCConnectionReconfiguration (RSCforLTEcarrierfreq.BRRCMeasurementReportforReportCGI eNBstores (CGIofCellD.BRRCMeasurementReportforRSC (PCI1.ARRCConnectionReconfiguration (regularDRXprofile.PCI3withPCI1thestrongest) 3...PCI6.z.ANRDRXprofile) 4..) 6.. for a successful case of NR establishment according to the LTE556: ANR Intra-LTE Inter-frequency UE Based feature.regularDRXprofile.BRRCConnectionReconfiguration (RSCforLTEcarrierfreq...Fx CellB.ARRCMeasurementReportforReportCGI CellCdatain (CGIofCellC.BRRCConnectionReconfiguration (ReportCGIforPCI1atfreq.) 2.ARRCMeasurementReportforRSC (PCI1.ARRCConnectionReconfiguration (ReportCGIforPCI1atfreq.. 8..z. UE. . - F1 F2 . X . From RL60 on. therefore.1. however. ANR ANR Based LTE. X X . UE- frequen frequen ANR ANR ANR profile profile based based cy cy Fully UE Intra. Inter-frequency - UE Based feature needs the services provided by the LTE473: Extended DRX Settings feature. the eNB establishes an enbControlled X2 link only if at least one of the features LTE782: ANR Fully UE based or LTE492: ANR is activated (that is. UE. the operator creates the ANR profile and enables it for UE-based ANR for the target carrier frequency. . . The Table 143: Resulting ANR method toward target frequency F2 shows the ANR method towards a target frequency dependent on the cell frequency and the feature configuration (feature activation parameter. the LTE556: ANR Intra-LTE. Table 143 Resulting ANR method toward target frequency F2 inter-frequency activated feature(s) no dedicated ANR dedicated ANR profile for F2 profile for F2 cell target LTE492: LTE782: LTE556: default default UE. however. • LTE473: Extended DRX Settings As for the LTE782: ANR Fully UE Based feature. Feature Descriptions and Instructions Descriptions of operability features The LTE556: ANR Intra-LTE Inter-frequency UE Based feature activation is done via feature activation flag at eNB level by setting the LNBTS parameter actUeBasedAnrInterFreqLte to TRUE. LTE556 F1 F2 . LTE556 .4 System impact Interdependencies between features • LTE42: DRX in RRC Connected Mode The DRX is required for ReportCGI measurements. either the actUeBasedAnrIntraFreqLte or anrOmExtEnable parameter is set to true). LTE492 LTE492 LTE492 LTE492 F1 F2 X X X LTE492 LTE556 LTE492 LTE556 6. based based deactiva activate Inter. the DRX feature does not need to be enabled (the actDRX flag does not need to be set to TRUE). extended DRX cycles can be required for performing the inter-frequency ReportCGI measurement. Also. ANR ANR ted d frequen deactiva activate cy . LTE RL60. . DN09185955 Issue: 01J © 2016 Nokia 249 . X LTE492 LTE556 LTE492 LTE556 F1 F2 X X . . . . Inter-frequency - UE Based feature needs the functionalities of the LTE42: DRX in RRC Connected Mode feature. . g Note: In RL50. the DRX feature does not need to be enabled (the actDRX flag does not need to be set to TRUE). X . handling of enbControlled X2 links is a basic functionality and is not guarded by any feature flag. LTE556 . the LTE556: ANR Intra-LTE. Therefore. . LTE556 F1 F2 X . LTE492 LTE492 LTE492 LTE492 F1 F2 X .1. . Setting the maxNumX2LinksIn and the maxNumX2LinksOut parameters' values to 0 is now the only way to disable accepting/establishing of enbControlled X2 links from RL60 on. ANR profile configuration).UE ted d based F1 F2 . - F1 F2 . 6. actUeBasedAnrInterFreqLte LNBTS frequency LTE ANR interfrequency RSC timer anrIfTRSC LNBTS Maximum number of eNB-controlled maxNumX2LinksIn LNBTS incoming X2-links 250 © 2016 Nokia DN09185955 Issue: 01J . Table 145 New parameters Full name Abbreviated name Managed Structure object ANR power level threshold for anrThresRSRPNbCellMobE ANRPRL mobility events v Activate UE-based ANR for Inter. Impact on system performance and capacity This feature has no impact on system performance or capacity.1.1. Inter-frequency - UE based feature to establish modeled NRs. Feature Descriptions and Instructions • LTE55: Inter-frequency HO The LTE55: Inter-frequency HO feature is mandatory for the LTE556: ANR Intra-LTE. and consistency check rules of all the LTE556: ANR Intra-LTE. Table 144 Related existing counters Counter ID Counter name Measurement M8000C38 Number of attempted X2 IP address retrievals via S1 8000 - LTE S1AP (WBTS) M8000C37 Number of successful X2 IP address retrievals via S1 8000 - LTE S1AP (WBTS) M8008C10 Number of Report CGI Requests 8008 - LTE RRC (WBTS) M8008C11 Number of successful CGI Reports 8008 - LTE RRC (WBTS) M8022C0 Number of X2 Setup attempts 8022 - LTE X2AP (WBTS) M8022C1 Number of failed X2 Setup attempts 8022 - LTE X2AP (WBTS) Key performance indicators There are no key performance indicators related to this feature. Inter-frequency - UE Based feature related parameters according to their definition. Impact on network and network element management tools The BTS SM/NetAct provides support for creation. update. deletion. Measurements and counters Table 144: Related existing counters lists existing counters related to this feature. Parameters Table 145: New parameters lists parameters introduced with this feature. Descriptions of operability features LTE RL60. Impact on interfaces This feature has no impact on interfaces.5 Management data Alarms There are no alarms related to this feature. 1. .) Full name Abbreviated name Managed Structure object Maximum number of eNB-controlled maxNumX2LinksOut LNBTS outgoing X2-links DRX profile 103 drxProfile103 LNCEL DRX inactivity timer drxInactivityT LNCEL drxProfile103 DRX long cycle drxLongCycle LNCEL drxProfile103 DRX on duration timer drxOnDuratT LNCEL drxProfile103 DRX profile index drxProfileIndex LNCEL drxProfile103 DRX profile priority drxProfilePriority LNCEL drxProfile103 DRX retransmission timer drxRetransT LNCEL drxProfile103 Table 146: Related existing parameters lists existing parameters related to this feature.2 Activating LTE556: ANR Intra-LTE. Inter-frequency .1. LTE RL60. default value: true related to the LTE556: ANR Intra-LTE.UE Based Before you start Table 148 Parameters used for activating and configuring LTE556: ANR Intra-LTE. related DN09185955 Issue: 01J © 2016 Nokia 251 . Feature Descriptions and Instructions Descriptions of operability features Table 145 New parameters (Cont.1. Inter-frequency - UE Based Parameter Purpose Requires eNB restart or object locking Activate also for UE-based mandatory configuration.6 Sales information Table 147 Sales information BSW/AS License control in network License control Activated by default W element attributes ASW . No 6. no ANR (actAlsoForUeBasedANR). Table 146 Related existing parameters Full name Abbreviated name Managed object Activate also for UE-based ANR actAlsoForUeBasedANR ANRPRL ANR profile for LTE identifier anrPrLId ANRPRL Target Carrier frequency targetCarrierFreq ANRPRL ANR quality threshold for neighbor cells anrThresRSRQNbCell ANRPRL 6. Inter-frequency - UE Based feature ANR profile for LTE mandatory configuration not modifiable identifier (anrPrLId). no handover (actIfHo) default value: 1 ANR power level threshold mandatory configuration. default value: 64 links (maxNumX2LinksIn). default value: 60 links (maxNumX2LinksOut). no timer (anrIfTRSC). mandatory configuration. no inter-frequency default value: 16 (nrLimitInterFreq) 252 © 2016 Nokia DN09185955 Issue: 01J . default value: no Inter-frequency LTE false (actUeBasedAnrInterFreqLte) . Inter-frequency - UE Based feature Enable interFrequency mandatory configuration. no neighbor cells default value: -12 dB (anrThresRSRQNbCell) Neighbor relation limit mandatory configuration. mandatory configuration. no controlled incoming X2. no for mobility events default value: -100 dBm (anrThresRSRPNbCellMobEv). Inter-frequency - UE Based feature Maximum number of eNB. Inter- frequency - UE Based feature ANR power level threshold mandatory configuration. related to the LTE556: ANR Intra- LTE.) Parameter Purpose Requires eNB restart or object locking to the LTE556: ANR Intra-LTE. related to the LTE556: ANR Intra-LTE. Descriptions of operability features LTE RL60. related to the default value: 1000 ms LTE556: ANR Intra-LTE. Inter-frequency - UE Based feature Activate UE-based ANR for activation flag. Inter- frequency - UE Based feature Maximum number of eNB. Inter-frequency - UE Based feature ANR interfrequency RSC mandatory configuration. related to the LTE556: ANR Intra-LTE. related to the LTE556: ANR Intra-LTE. no controlled outgoing X2. Inter-frequency - UE Based (Cont. related to the LTE556: ANR Intra-LTE. Inter-frequency - UE Based feature DRX profile 103 mandatory configuration no (drxProfile103) parameter structure. no for neighbor cells default value: -100 dBm (anrThresRSRPNbCell) ANR quality threshold for mandatory configuration. Feature Descriptions and Instructions Table 148 Parameters used for activating and configuring LTE556: ANR Intra-LTE. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. and the Enable interFrequency handover (LNBTS) (actIfHo) parameter value to enabled. d) Set the Activate UE-based ANR for Inter-frequency LTE (actUeBasedAnrInterFreqLte) parameter value to true. This step is necessary to configure parameters for the Profile 103 for LTE inter- frequency ANR measurements a) Go to the Radio Network Configuration page. Maximum number of eNB-controlled incoming X2-links (ANR) (maxNumX2LinksIn). d) Expand LNCEL object. b) Expand the MRBTS object. b) Expand the MRBTS object. Maximum number of eNB-controlled outgoing X2-links (ANR) (maxNumX2LinksOu) parameters values. 3 Configure the LNBTS/ANR parameters. 2 Activate the feature. c) Select the LNBTS object. 4 Configure the DRX profile. DN09185955 Issue: 01J © 2016 Nokia 253 . Feature Descriptions and Instructions Descriptions of operability features Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. Inter-frequency - UE Based feature inter- frequency handover to FDD and TDD neighbor cells a) Set the ANR interfrequency RSC timer (ANR) (anrIfTRSC ). a) Go to the Radio Network Configuration page. c) Expand LNBTS object. perform the steps described in this procedure. This step is necessary to: • define the maximum time at the eNB to wait for an LTE inter-frequency ReportStrongestCells measurement report from a UE configured to perform this measurement • set a point where the the eNB stops accepting establishment requests for new eNB-controlled X2-links from the neighbor eNBs • set a point where the the eNB stops the automatic establishment of new eNB- controlled X2-links • enable the LTE556: ANR Intra-LTE. LTE RL60. e) Expand DRX profile 103. g Note: The setting is only necessary if the default value is not appropriate. 5 Configure the ANRPRL parameters. g) For the DRX profile 103-1 Properties set the parameters values. ANR power level threshold for neighbor cells (anrThresRSRPNbCell). 254 © 2016 Nokia DN09185955 Issue: 01J . g Note: The setting is only necessary if the default value is not appropriate. g Note: In addition to the default profile. g Note: The setting is only necessary if the default value is not appropriate. e) Set the ANR power level threshold for mobility Events (anrThresRSRPNbCellMobEv). b) Expand the MRBTS object. This step is necessary to: • configure threshold to control detection of neighbor cells via passive ANR • activate the profile for UE-based intra- and/or inter-frequency ANR • uniquely identify the ANRPRL object • configure if a cell is accepted by eNB as a neighbor cell for which CGI is needed • configure if the eNB will request to resolve the CGI of unknown cells • set the point. Neighbor relation limit inter-frequency (nrLimitInterFreq) parameters values. Activate also for UE- based ANR (actAlsoForUeBasedANR). ANR profile for LTE identifier (anrPrLId). ANR quality threshold for neighbor cells (anrThresRSRQNbCell). where the eNB stops autonomous learning of new neighbor cells via ANR a) Go to the Radio Network Configuration page. d) Select the ANRPRL object. Descriptions of operability features LTE RL60. one or more ANRPRL profiles for dedicated target carrier frequencies might be created. Feature Descriptions and Instructions f) Select DRX profile 103-1. c) Expand the LNBTS object. This step is necessary to: • Identify E-UTRA carrier frequency for which the configuration is valid • set the measurement bandwidth common for all neighboring cells • indicate whether all the neighboring cells use Antenna Port 1 a) Go to the Radio Network Configuration page.1. When the ANR profile for LTE identifier (anrPrLId) is different than 0. b) Expand the MRBTS object. c) Expand the LNBTS object. then the Target carrier frequency (targetCarrierFreq) must be configured: a) Go to the Radio Network Configuration page. LTE RL60.3 Deactivating LTE556: ANR Intra-LTE. 6. the Target carrier frequency (targetCarrierFreq) must be omitted. Feature Descriptions and Instructions Descriptions of operability features g Note: When the ANR profile for LTE identifier (anrPrLId) is set to 0. DN09185955 Issue: 01J © 2016 Nokia 255 . f) Set the ANR profile for LTE identifier (anrPrLId) parameter value different than 0 and Target carrier frequency (targetCarrierFreq) parameter value. Inter-frequency . f) For the LNHOIF-Properties set the parameters values. e) Select New LNHOIF. 7 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager.UE Based Before you start The Activate UE-based ANR for Interfrequency LTE (actUeBasedAnrInterFreqLte) parameter is used for deactivation. nor cell locking. g Note: For each ANRPRL targetCarrierFrequency there must be a dedicated LNHOIF instance with eutraCarrierInfo equal to targetCarrierFrequency within all LNCEL instances in which LTE inter-frequency ANR will be active. d) Right-click the LNCEL object. Modification of this parameter does not require neither eNB restart. 6 Create the LNHOIF object. b) Expand the MRBTS object. d) Select New ANRPRL e) Select ANRPRL. c) Right-click the LNBTS object. Feature Descriptions and Instructions g Note: It is also possible to deactivate ANR for a certain LTE carrier frequency or to restrict ANR to a set of cells. 2 Deactivate the feature.1. c) Select the LNBTS object. With this feature. b) Expand the MRBTS object.1 Description of LTE954: Intelligent configuration synchronization Introduction to the feature This feature introduces an end-to-end mechanism for data synchronization to avoid unnecessary uploads. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. Operator benefits This feature benefits the operator as follows: • The operator can reduce operating expenses by having more accurate configuration data available in NetAct. Descriptions of operability features LTE RL60.2.2 LTE954: Intelligent configuration synchronization 6. NetAct triggers an upload of the CM data. 6. a) Go to the Radio Network Configuration page. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. Configuration data revision number information is added in the network element and provided to NetAct via change notifications. Inter-frequency - UE Based deactivation on a given carrier frequency requires that the ANR profile has been disabled for UE-based ANR for that target carrier frequency. NetAct uses this information to check if configuration upload is needed. In case an upload is needed.2. perform the steps described in this procedure. In Step 3 (Modify the feature-specific eNB configuration settings) of the general procedure. 256 © 2016 Nokia DN09185955 Issue: 01J .1 Benefits End-user benefits This feature does not affect the end-user experience. d) Set the Activate UE-based ANR for Inter-frequency LTE (actUeBasedAnrInterFreqLte) parameter value to false. The LTE556: ANR Intra-LTE. no upload will be required before applying changes to the configuration of the Network Element. 6. 4 System impact Interdependencies between features There are no interdependencies between this and any other feature.3 Functional description To ensure that the actual configuration stored in NetAct databases is up to date. 6. as e. The configuration change may be caused by an autonomous action in the network element. or CM change executed from BTS SM or NetAct.0 LBTS6. LTE RL60. - Hardware requirements This feature requires no new or additional hardware. NetAct uses the "Configuration data revision number" information to check if configuration upload is needed. NetAct8 EP1 . outage of management plane connection for longer time and limited storage capacity of change notifications in network element. Feature Descriptions and Instructions Descriptions of operability features • The feature increases the grade of service for the end user by maintaining up-to-date network information automatically. NetAct triggers an automatic upload of the CM data of that eNB. Whether the mismatch in the value leads to automatic upload is up to the NetAct application and operator preference. 6. because the eNB will send periodical update of the "cmSyncCheck" parameter.1. With this feature an end to end (e2e) mechanism for data synchronization is introduced. The "Configuration data revision number" information is saved in eNB's permanent memory. but in case of SW update/upgrade with data migration.0 OMS6.1. Impact on interfaces DN09185955 Issue: 01J © 2016 Nokia 257 . Table 149 Software Requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 LBTS6. No scheduled uploads are needed anymore.g. For Configuration Change Notification (CCN). The "Configuration data revision number" is increased in eNB when real changes are done to the configuration. The "Configuration data revision number" will survive a eNB restart and eNB would not reset to “1”.2.2. This is because configuration change events may be lost due to several reasons which may happen in the network. "Configuration data revision number" information is added in eNB and provided via OMS to NetAct. 6. an upload of the CM data of eNB has to be done to NetAct. In case an upload is needed. The "Configuration data revision number" is also checked periodically in phases when no configuration change is reported.2 Requirements Software requirements The following table lists software required for this feature.1. or full recommissioning. eNB starts with "Configuration data revision number" =1.2.0 UE NetAct MME SAE GW . 2. 6.2 Configuring LTE954: Intelligent configuration synchronization Before you start Configuration data synchronization check period (cmSyncCheckPeriod) parameter has no valid value.6 Sales information Table 151 Sales Information BSW/ASW License control in network License control attributes element BSW . Measurements and counters There are no new measurements or counters related to this feature. Impact on system performance and capacity This feature has no impact on system performance or capacity.1.2. Descriptions of operability features LTE RL60. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Table 150 New parameters Full name Abbreviated name Managed Structure object Configuration data cmSyncCheck MRBTS synchronization check Configuration data cmSyncCheckPeriod MRBTS synchronization check period Configuration data revision configDataRevisionNum MRBTS number ber 6.5 Management data Alarms There are no new alarms related to this feature. Feature Descriptions and Instructions This feature has no impact on interfaces. 258 © 2016 Nokia DN09185955 Issue: 01J . - 6.1.2. Key performance indicators Parameters Table 150: New parameters lists parameters introduced with this feature. data synchronization between the eNB and NetAct is automatically verified. The Configuration data synchronization check period (cmSyncCheckPeriod) parameter provides a means for the Operator to force the eNB to periodically issue a change notification so that the data synchronization between NetAct and the eNB is ensured. Expected outcome After setting the Configuration data synchronization check period (cmSyncCheckPeriod) parameter value. g Note: Configuration data synchronization check period parameter value is measure in minutes. Feature Descriptions and Instructions Descriptions of operability features g Note: As mentioned in section 1. However. b) Select the MRBTS object. a) Go to the Radio Network Configuration page. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager. so that the NetAct can determine if the copy of the eNB configuration data matches the actual configuration of the eNB. The Configuration data synchronization check period (cmSyncCheckPeriod) parameter is used for optional configuration. when a configuration plan is activated). 2 Set the configuration value. DN09185955 Issue: 01J © 2016 Nokia 259 . Modification of this parameter does not require neither eNB restart nor cell locking. c) Set the Configuration data synchronization check period (cmSyncCheckPeriod) parameter value to 15 or a decimal value from 10 to 500. The value provided by the operator determines how often the eNB will force data synchronization verification to occur. the eNB issues a change notifications only when the eNB's configuration is modified (for example. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. even if the configuration of the eNB does not change. It is recommended that the operator provide a value for this parameter for all of the eNBs in their network. LTE RL60. the eNB adds information in the change notifications that are delivered to NetAct. a) Go to the Radio Network Configuration page. The Configuration data synchronization check period (cmSyncCheckPeriod) parameter is used for optional configuration. the verification of synchronization between the eNB and NetAct occur only if the configuration of the eNB changes rather than periodically (as defined by the Configuration data synchronization check period (cmSyncCheckPeriod) parameter value).3 Removing the configuration of LTE954: Intelligent configuration synchronization Before you start Configuration data synchronization check period (cmSyncCheckPeriod) has a valid value. Descriptions of operability features LTE RL60. 260 © 2016 Nokia DN09185955 Issue: 01J . 2 Remove the configuration value. Feature Descriptions and Instructions 6. c) Remove the Configuration data synchronization check period (cmSyncCheckPeriod) parameter value. The customer is able to integrate its own PKI with another operator's PKI in the RAN sharing scenario (for example. Expected outcome After removing the Configuration data synchronization check period (cmSyncCheckPeriod) parameter value.1 Description of LTE1245: Revocation Management Introduction to the feature The LTE1245: Revocation Management feature introduces the support of cross-signed certificates and an enhanced certificate revocation list (CRL) management for the eNB.3. 3 Send the parameters to the eNB according to the procedure described in section Activating and deactivating LTE features using BTS Site Manager. b) Select the MRBTS object.3 LTE1245: Revocation Management 6. Procedure 1 Follow the general procedure described in section Activating and deactivating LTE features using BTS Site Manager.2. Modification of this parameter does not require neither eNB restart nor cell locking). multi-operator core network or multi-operator radio access network). 6. A secure connection between the eNB and the Core Networks requires that the eNB is connected to the Security Gateways (SEG) of both RAN-sharing operators. Feature Descriptions and Instructions Descriptions of operability features 6. - Hardware requirements This feature requires no new or additional hardware. the eNB is shared between the two operators.2 Requirements Software requirements Table 152: Software Requirements lists the software required for this feature. while the core networks remain operated and managed independently. including the eNB and the SEG.3. the LTE1245: Revocation Management feature introduces the support of cross-signed certificates. 6.1 Benefits End-user benefits This feature does not affect the end-user experience. The Certification Authority issues operator end-entity certificates to all network elements. It can be accomplished either by adding the peer's operator root CA certificate in the eNB's trust pool or with the use of a cross- signed certificate. The cross-signed certificates are used only for IPsec connections.1.0 UE NetAct MME SAE GW . both RAN-sharing operators run their own Public Key Infrastructure with their own Certification Authority and the root(s) of trust. NetAct8 EP1 . Table 152 Software Requirements System release Flexi Multiradio BTS Flexi Multiradio 10 iOMS BTS RL60 LBTS6. Cross-signed certificate enrollment DN09185955 Issue: 01J © 2016 Nokia 261 . To be able to connect to a SEGs.0 LBTS6. In such scenario. Operator benefits This feature enables the operator to: • support cross-signed certificates (in case of MOCN or MORAN) • configure certificate revocation checking • verify the whole peer's certificate chain against multiple certificate revocation lists 6.3. the eNB needs to have valid trust path leading from the SEG's operator end-entity certificate to any root of trust (represented by an operator root CA certificate) stored in the eNB trust pool. LTE RL60.1.3.0 OMS6.1.3 Functional description Cross-signed certificate support To support secure Radio Access Network sharing scenario. In many cases. 1 (intermediate) (intermediate) CA1.2certcross-signed CA1certificate byoperator'sCA1. the eNB builds a certificate chain up to the eNB's trust anchor (operator root CA certificate). Then.3 endentity endentity certificate certificate network network element element For example.2 (signing) cross-signs (signing) CA1.1 cross-signspeer'sCA2.3 CA2.1certificate (intermediate) Operator'sCA1. Figure 20 SEG's chain of trust CA2.1certificate CA2. Figure 19 Cross-signed certificates in eNB eNBtrustpool SEGtrustpool operator'sroot CA2.1 cross-signs the Intermediate CA2. the eNB validates all certificates of this chain of trust against available CRLs.2 CA2. Descriptions of operability features LTE RL60.2certcross-signed peer'sroot CA1. The cross-certification process is allowed between any layers of the trust chain as shown in Figure 19: Cross-signed certificates in eNB but the resulting chain of trust must not exceed the number of four CA layers (counting the cross-signed certificate on top and up to three intermediate CA certificates below it).1 (signing) CA2.1 CA2certificate bypeer'sCA2.2 cross-signed certificate as shown in Figure 20: SEG's chain of trust. if the Intermediate CA1.2 Peer'sCA2. and CA2.2 of another operator.2 CA2.1 (intermediate) CA1.2certificate CA2.2 cross-signed certificate).3 certificate.2 operator's peer's rootCA1 rootCA2 (intermediate) (intermediate) CA1. Feature Descriptions and Instructions If the trust relation between two operators is to be established by cross-certification. the Certification Authority of one operator signs certificates issued by the other operator's Certification Authority and vice versa. Signing CA2.3certificate CA2.2certificate (intermediate) (intermediate) CA1.2 (signing) (signing) CA1. 262 © 2016 Nokia DN09185955 Issue: 01J .3certificate operator'sCA1.3certificate SEG's certificate With the cross-signed certificate (CA2.2certcross-signed byoperator'sCA1. the eNB will build the following chain of trust to authenticate the SEG: SEG's operator EE certificate. the eNB does not verify certificates against CRLs and. With the BTS Site Manager. The expiring cross-signed certificate is not removed automatically to allow smooth migration to the usage of the new cross-signed certificate. It is up to the operator to decide. Revocation of a certificate that was cross-signed (for example. This reference. also called CRL distribution point. Peer CA2. CRL checking activation With the LTE1245: Revocation Management feature. the operator can enable or disable the certificate verification against the CRLs. By default. the operator removes them from the trust pool of shared eNBs with the BTS Site Manager or the NetAct. the eNB uses: • the CRLDPs that are included in certificates of the eNB's trust chain (the CRLDPs configured with an optional parameter are ignored) DN09185955 Issue: 01J © 2016 Nokia 263 .1. the certificate revocation check is more precise and allows the verification of the peer's chain of trust against CRLs issued by the peer's Certification Authority. CA2. The CRLs are downloaded from CRL distribution points (CRLDP) included in the certificates of the eNB's own chain of trust and/or from the CRLDP configured with an optional parameter. The setting is configurable with the BTS Site Manager or the NetAct (via plan provision) and applies for TLS and IPsec connections. Depending on the configuration. CRL distribution points (CRLDP) CRLs are created by Certification Authorities and stored in a certificate repository server. the eNB uses both the expiring and the new cross-signed certificates for IPsec connections establishment. allows establishment of IPsec or TLS connection with a peer network element presenting a revoked operator certificate.2 certificate) does not imply the revocation of the cross-certificate (for example. Feature Descriptions and Instructions Descriptions of operability features The cross-signed certificate is delivered manually to all shared eNBs and stored in their trust pools. Cross-signed certificates can be installed in each eNB individually. In the migration period. This server is a CRL distribution point for RAN network elements. the operator installs the new cross-signed certificate in the trust pool of all shared eNBs. the feature is enabled and the eNB verifies all certificates against CRLs available in the eNB. Multiple CRL support Current certificate revocation check in the eNB is enhanced by using multiple certificate revocation lists (CRL).2 cross-signed by Operator CA1. The operator might choose to disable the CRL checking for the whole eNB. If disabled. if the trust relation should continue. the eNB needs a reference to the server. for example. LTE RL60. using BTS Site Manager for a single eNB or as a mass operation with the help of a NetAct script were the BTS Site Manager operation for certificate download is automatically executed multiple times. revocation. can be either an IP address or a Fully Qualified Domain Name (FQDN) of the server followed by port number and path (containing the distinguished name of the server). After the migration period or when the cross-signed certificates are expired. To be able to connect to the certificate repository server and download the latest CRLs. Cross-signed certificate update. With multiple CRLs. The BTS checks certificates that are in the validation path of the peer entity certificate. and removal The operator can update the cross-signed certificates in the same manner as during the cross-signed certificate enrollment procedure. The feature is activated with the CRLUsageEnabled parameter. the LDAP search returned an empty value. this is the default setting). If the eNB is configured to use only manually configured CRLDPs (the CRLDPSource parameter set to 1). No alarm is raised if the download from the primary CRLDP fails but from the secondary CRLDP succeeded. received as a part of secure connection establishment.binary • ldap://FQDN:port/<CA distinguished name>?certificateRevocationList. the eNB reads the CRLDistributionPoint parameter for CRLDP entries and use them to downloads CRLs from the server. It is possible to configure up to 20 CRLDPs in the eNB.10. If the eNB cannot download a CRL from the primary CRLDP. Additionally. for example. If the eNB is configured to read CRLDPs only from its own chain of trust (the CRLDPSource parameter set to 0. The eNB allows to configure up to 20 additional CRL distribution points. the eNB checks its operator end-entity certificate and intermediate operator CA certificate(s) for CRLDP entries and use them to download CRLs from the server. All further found CRLDPs are ignored. The eNB reads the whole certificate extension field and uses the first supported entry to download the CRL. All certificates in the peer's chain of trust. If the eNB fails to download the CRL. Certification Authorities might configure more that one CRLDP in the certificate extension field (also with some other protocol than LDAP). With the introduction of LTE1245: Revocation Management feature. are validated against CRLs that are available in the eNB.O=NOKIA.binar y CRL configuration The eNB automatically downloads and periodically updates all CRLs. The CRL update failure BTS fault might occur because of many reasons. Each entry is specified as an IP address of the certificate repository server or as a Fully Qualified Domain Name (FQDN). or many other reasons. the CRL storage limit was reached.C=FI?certificateRevocationList. 264 © 2016 Nokia DN09185955 Issue: 01J . Feature Descriptions and Instructions • the CRLDPs configured with an optional parameter (the CRLDPs in own chain of trust are ignored) • both of the sources The configuration is done with the CRLDPSource parameter.10. The BTS fault is cleared automatically when all CRLs are successfully downloaded to the eNB.10:389/CN=SubCA1.binary for example: ldap://10. each entry might contain two CRLDPs (a primary CRLDP and a secondary CRLDP). the DNS resolution failed. the secondary CRLDP is used. the CRL update failure BTS fault is raised. the eNB does not expect the operator root CA certificate to contain any CRLDP and does not use them. The exact reason for the CRL update failure is included in the CRLInfo parameter of the current CRL (for example CRLDownloadStatus and CRLUpdateFailureReason). the eNB never uses CRLDP included in peer's certificates. The eNB performs case-sensitive search within manually configured CRLDPs and allows to configure only unique CRLDPs. Each CRLDP entry can consist of primary and secondary CRLDP. Descriptions of operability features LTE RL60. Regardless of the CRLDPSource parameter setting. even if configured. If a FQDN is used. the eNB uses only CRLDPs included in the certificate extension field of its own chain of trust. The CRLDP should have one of the following formats: • ldap://IPaddress:port/<CA distinguished name>?certificateRevocationList. the eNB uses a DNS query to resolve the IP address of the server. By default. it is possible to configure additional intermediate CA certificates and operator root CA certificates to allow validation of the CRL origin (CRL signature). Feature Descriptions and Instructions Descriptions of operability features In RAN-sharing scenario. CRL housekeeping The eNB performs CRL housekeeping. If both CRLDP sources are configured (the CRLDPSource parameter set to 2). For this reason. A CRL is kept in the BTS as long as: • there is a reference to it in any CRLDistributionPoint parameter • there is a reference to it in any certificate of the eNB's own trust chain • there is a certificate in the eNB to verify the signature of the CRL If CRLDPs in the eNB's own trust chain or in the CRLDistributionPoint parameter are changed or removed. This includes four in eNB's own trust chain. LTE RL60. The eNB also downloads all CRLs (depending on the CRLDPSource parameter) : • when there is a change in the CRLDPSource parameter • periodically. CRL validation CRLs are created and signed by Certification Authorities. The eNB always validate received certificates against all CRLs available in the eNB. The additional configured CRLDPs are needed to validate the Security Gateway certificates signed by a Certification Authority that belongs to the other RAN- sharing operator. the eNB updates only the corresponding CRL. some CRLs validation will trigger the CRL update failure BTS fault with reason CRL signature validation failure. The CRLs obtained from the configured parameter might be issued by an intermediate CA(s) of a partner operator's PKI hierarchy. and 20 with the CRLDistributionPoint parameter. Wrong CRL signature causes the eNB to raise the CRL update failure fault with more specific failure reason stored in the CRLInfo parameter. If a CRL is issued by an intermediate CA belonging to the eNB's own chain of trust. the eNB removes old CRLs. it is possible to configure 24 CRLDP in total. the CRL can be validated immediately after downloading. The CRLs of the own chain of trust are initially downloaded to the eNB as part of the operator certificate initialization procedure. Then. The eNB does not trigger selective download for only one CRL unless the NextUpdate value of a CRL is reached. DN09185955 Issue: 01J © 2016 Nokia 265 . the eNB might not have enough intermediate CA certificates and operator root CA certificates to allow validation of the CRL origin (CRL signature). the eNB triggers CRL download for all CRLs (depending on the CRLDPSource and CRLDistributionPoint configuration). For this reason. Deactivating the CRL checking function also causes the eNB to remove all stored CRLs. the eNB is usually configured to use the CRLDPs from its own chain of trust and additionally those configured manually (the CRLDPSource parameter set to 2). according to the crlUpdatePeriod parameter in the eNB • according to the NextUpdate value present in each CRL • during the eNB start-up (not in case of auto-connection) • when manually triggered with BTS Site Manager or NetAct • when the CRLUsageEnabled parameter changed to 1 (enabled) • when an existing CRLDistributionPoint is removed from the eNB or a new CRLDistributionPoint is added If any of the above events happen. These CRL verification certificates can be added with the BTS Site Manager. If all 24 CRLDPs are unique. The LTE482: DNS Support for Certificate Examination feature is required if CRL distribution point is given as FQDN (instead of an IP address). This includes: • eNB own trust anchors (four self-signed certificates) – one own trust anchor – one own trust anchor (for update) – one additional trust anchor (to support secure LTE505: RAN Sharing feature) – one additional trust anchor (to support secure LTE505: RAN Sharing feature (for update)) • eNB own trust chain (four certificates) – one operator end-entity certificate – one signing operator CA certificates – two intermediate operator CA certificates • Registration Authority certificate chain (four certificates) – one RA certificate – one RA signing CA certificate – two intermediate RA certificates • additional certificates (up to 14 certificates) – up to two cross-signed certificates (to support secure LTE505: RAN Sharing feature) – peer's intermediate certificates for CRL validation 6. Feature Descriptions and Instructions eNB trust pool The LTE1245: Revocation Management feature extends the eNB pool of trust to support one eNB private key and up to 26 certificates in the eNB trust pool. 266 © 2016 Nokia DN09185955 Issue: 01J .1.3. The LTE505: Transport Separation for RAN Sharing feature uses this feature for secure communication between the eNB and two core networks.4 System impact Interdependencies between features The LTE523: Multi-Layered Certificate Authorities feature is required to support hierarchical PKI. Impact on network and network element management tools Certificate management tools in the BTS Site Manager and the NetAct are updated to allow additional operator CA certificate installation and configuration of additional CRLDPs. Impact on system performance and capacity This feature has no impact on system performance or capacity. Impact on interfaces This feature has no impact on interfaces. Descriptions of operability features LTE RL60. 3. DN09185955 Issue: 01J © 2016 Nokia 267 . Table 153 Modified alarms Alarm ID Alarm name 7665 BASE STATION TRANSMISSION ALARM The alarm is caused by the following BTS faults: • CRL update failure • BTS Trust Anchor expired or due to expire Measurements and counters There are no measurements or counters related to this feature. Parameters Table 154: New parameters lists parameters introduced with this feature. LTE RL60.1. Key performance indicators There are no key performance indicators related to this feature. Feature Descriptions and Instructions Descriptions of operability features 6.5 LTE1245: Revocation Management management data Alarms Table 153: Modified alarms lists existing alarms related to this feature. Table 154 New parameters Full name Abbreviated name Managed Structure object CRL Usage Enabled CRLUsageEnabled CERTH - CRLDP Source CRLDPSource CERTH - CRL distribution point CRLDistributionPoint CERTH Structure CRLDP primary CRLDPPrimary CERTH CRLDistributionPoint CRLDP Secondary CRLDPSecondary CERTH CRLDistributionPoint CRL Info CRLInfo CERTH Structure CRLDP Type CRLDPType CERTH CRLInfo CRL Distribution Point CRLDistributionPoint CERTH CRLInfo Status of the last CRL download CRLDownloadStatus CERTH CRLInfo Issuer of the current certificate CRLIssuer CERTH CRLInfo revocation list Time of the next CRL update CRLNextUpdate CERTH CRLInfo Number of revoked certificates CRLNumOfRevCert CERTH CRLInfo Issue date of the current certificate CRLThisUpdate CERTH CRLInfo revocation list Reason for the last CRL update CRLUpdateFailureRea CERTH CRLInfo failure son Table 155: Related existing parameters lists existing parameters related to this feature. Descriptions of operability features LTE RL60, Feature Descriptions and Instructions Table 155 Related existing parameters Full name Abbreviated name Managed object Certificate Revocation List update period crlUpdatePeriod CERTH Root certificates rootCertificates CERTH 6.3.1.6 Sales information Table 156 Sales Information BSW/ASW License control in License control Activated by default network element attributes BSW - - Yes 6.3.2 Activating and configuring the LTE1245: Revocation Management feature using BTS Site Manager Before you start The LTE1245: Revocation Management feature is activated by default. This procedure describes an optional feature configuration. Activation or deactivation of this feature requires neither an eNB restart nor cell locking. Before activating/configuring the feature, make sure that: • the eNB is commissioned and operational • the eNB has a valid route to the CMP/CA and LDAP server • the firewall allows traffic between the eNB and CMP/CA and LDAP server Table 157 Parameters used for activating and configuring the LTE1245: Revocation Management feature Parameter Purpose Requires eNB restart or object locking CRL Usage Enabled activation flag (enabled by default) No (CRLUsageEnabled) CRLDP Source Configures the CRLDP source (certificate, No (CRLDPSource) CRLDistributionPoint parameter, or both) CRL distribution point Additional user-defined CRL distribution points No (CRLDistributionPoint) Root certificates Additional CA certificates used for validation of No (rootCertificates) the CRLs obtained from user-defined CRL distribution points. Certificate Revocation List Frequency (in hours) of an automatic certificate No update period update interval. (crlUpdatePeriod) The LTE523: Multi-Layered Certificate Authorities feature needs to be configured before the activation of the LTE1245: Revocation Management feature. 268 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions Descriptions of operability features Checking eNB certificates Steps To check the eNB certificates, do the following: Procedure 1 Start the BTS Site Manager application and establish a connection to the eNB. For details, see Launching BTS Site Manager in Commissioning Flexi Multiradio BTS LTE or the BTS Site Manager Online Help (section Instructions). 2 Open the Certificate Management tool From the top menu bar, select Configuration ► Certificate Management. 3 Verify if the eNB has a valid chain of trust already installed. The BTS certificates section lists all certificates installed in the eNB. Check: • if the eNB has a root certificate which is identified by letters TA (for Trust Anchor) in the Type column. There might be more than one root certificates. • if the eNB has a BTS certificate which is identified by letters BTS in the Type column. There might be only one BTS certificate. • if all certificates are valid (check the Valid from and Valid to dates for each certificate) t Tip: Optionally, there might also be intermediate CA certificates installed in the eNB (identified by letters CA in the Type column). If there are intermediate certificates, make sure that those certificates are valid. Expected outcome The eNB has at least one root certificate and one BTS certificate and both/all are valid. Unexpected outcome If there are no certificates installed in the eNB, configure them as described in the LTE523: Multi-Layered Certificate Authorities feature activation instructions. Configuring revocation management Check the Valid from and Valid to dates for each certificate Procedure t Tip: The CRL checking is activated by default and the eNB reads CRLDPs from its chain of trust. If the eNB certificates were installed using the CMP protocol, the CRLs might already be installed in the eNB. DN09185955 Issue: 01J © 2016 Nokia 269 Descriptions of operability features LTE RL60, Feature Descriptions and Instructions 1 Open the Certificate Management tool. From the top menu bar, select Configuration ► Certificate Management. 2 Switch to Certificate Revocation List tab. In the Certificate Management tool, switch to the Certificate Revocation List tab. 3 Check if the CRL checking is active. Make sure the Enable CRL check-box is selected. 4 Configure the CRL update interval. In the CRL update interval field, configure the frequency (in hours) of the CRL update interval. 5 Configure the source of the CRL destination points. In the CRL source field, select one of the following values: • Certificate The CRLDPs are taken only from the certificates of the eNB's chain of trust. • Manual configuration The CRLDPs are taken only from manually configured parameters. • Certificate and manual configuration The CRLDPs are taken from the certificates of the eNB's chain of trust and from manually configured parameters. 6 (Optional) Configure additional CRL distribution points. g Note: Follow this step only if the CRL source was configured to Manual configuration or Certificate and manual configuration. a) In the <Enter primary address> field, enter the primary address of the CRL distribution point, in the following format: ldap://<IP address>:<port>/<CA distinguished name>?certificateRevocationList;binary for example: ldap://10.10.10.10:389/CN=SubCA1,O=NOKIA,C=FI?certificateRevocatio nList;binary g Note: Only the ldap protocol is supported in the eNB for CRL download. b) Optionally, configure also the secondary address for the CRLDP. c) To save the changes, click Send. 270 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions Descriptions of operability features g Note: If the additional CRLs were issued by a Certification Authority which does not belong to the eNB's chain of trust, the CA/TA certificate must be installed in the eNB manually. Otherwise, the verification of the CRL signature is not possible and the CRL cannot be used. 7 If required, add additional CA/TA certificates for the CRL signature verification. g Note: Follow this step only if the CRL source was configured to Manual configuration or Certificate and manual configuration, and the additionally configured CRLs were issued by Certification Authorities which do not belong to the eNB's pool of trust. • Switch to the BTS Certificates tab. • In the Install certificates section, select Additional CA certificates ► <Select> ► Browse... • Using the file explorer, select the CA/TA certificate file in .pem file format. • Click Open. • Click Send. Repeat this step to add all CA/TA certificates that are required to validate the signatures of the configured CRLs. 8 Trigger CRL update. To trigger the CRL update: • Switch to the Certificate Revocation List tab. • Click Trigger CRL Update. 9 Verify if the CRLs were installed. The eNB applies a random delay of up to five minutes before starting the CRL download. After a while, check if the CRLs are present in the CRL information section. Expected outcome The eNB downloaded all CRLs and for each CRL the Download status is OK, and the Failure status is Successful. Unexpected outcome If not all CRLs were downloaded successfully, the eNB raises the CRL Update Failure (61074) BTS fault. Check the reason for the fault: • Open the Certificate Management tool by selecting Configuration ► Certificate Management. • Switch to the Certificate Revocation List tab. • In the CRL information section, check each CRL entry for Failure reason other than Successful. DN09185955 Issue: 01J © 2016 Nokia 271 Descriptions of operability features LTE RL60, Feature Descriptions and Instructions t Tip: The BTS fault is cleared automatically if all configured CRLs are downloaded successfully. It might take up to five minutes for the eNB to download all configured CRLs or trigger the BTS fault. 6.3.3 Deactivating LTE1245: Revocation Management Before you start To deactivate the feature, deactivate the CRL Usage Enabled (CRLUsageEnabled) parameter. Deactivation of this feature does not require eNB restart or cell locking. Procedure 1 Open the Certificate Management tool. From the top menu bar, select Configuration ► Certificate Management. 2 Switch to Certificate Revocation List tab. In the Certificate Management tool, switch to the Certificate Revocation List tab. 3 Deactivate CRL checking. Uncheck the Enable CRL check-box. 4 Save the changes in configuration. To save the changes, click Send. 6.4 LTE1361: Additional QoS performance measurements 6.4.1 Description of LTE1361: Additional QoS performance measurements Introduction to the feature This feature is about PM counters extension. 6.4.1.1 Benefits End-user benefits This feature does not affect the end-user experience. Operator benefits This feature benefits the operator as follows: 272 © 2016 Nokia DN09185955 Issue: 01J LTE RL60, Feature Descriptions and Instructions Descriptions of operability features • PM counters enhancements, according to customer requirements. • QoS-performance monitoring (latency, packet loss) • Trouble-shooting (UE-behaviour, UE-performance for RRC-procedures) • 3GPP-compliancy 6.4.1.2 Requirements Software requirements The following table lists software required for this feature. Table 158 Software Requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 LBTS6.0 LBTS6.0 OMS6.0 UE NetAct MME SAE GW - NetAct8 EP1 - - Hardware requirements This feature requires no new or additional hardware. 6.4.1.3 Functional description This feature implemented the following PM-counters: 1. C-plane counters for monitoring: • Average number of simultaneous E-RABs per QCI (1...9) E-RABs are one of the E-UTRAN cell resources which are limited in number. Hence along with the E-RAB Setup Success Rate, there is a need to monitor the average number of simultaneous E-RABs. Having them at QCI level helps in learning the service distribution in time periods. The average number of simultaneous E-RABs allows to monitor the average utilization of the resources in time periods, and as a result makes the necessary resource capacity engineering easier. The aggregated number of simultaneous E-RABs is counted by samples, and an additional counter measures the number of samples (a common denominator). By dividing the individual QCI-specific counters by this denominator, the operator gets the average number of simultaneous E-RABs per QCI. • Number RRC setup completions and rejections differentiated by the following establishment causes: – mobile originated calls – mobile originated signaling – mobile terminated access – delay tolerant access Additionally, a counter that measures the number of setup attempts for delay tolerant access is introduced. DN09185955 Issue: 01J © 2016 Nokia 273 . g Note: – There will be no packet loss for AM bearers in downlink caused by intra-cell handover. see the Key performance indicators section. It is an indicator for the delay experienced by the end-user.4) have been already implemented . 3. – Packet Loss PM-counters for QCI (1. 4.9) The objective is to measure user plane packets that are lost on the air interface. it can also be used to monitor the packet error loss rate characteristics of the E-RAB's QCI. For a detailed list of all counters.4..1.. 3 and 4 are pre-requisites for the support of QCI 1. see the Measurement and counters section. therefore it is important to provide means to monitor these events. The success or failure of a call/session setup attempt impacts directly the network's quality of service and the end-user experience. that is. the respective counters will almost always be zero. – Because the UE is free to leave gaps in the packet sequence numbering. to 3GPP 36. Descriptions of operability features LTE RL60. For a list of related KPIs.4 System impact Interdependencies between features • LTE10: EPS bearers for conversational voice and LTE496: Support of QCI 2. 6. 274 © 2016 Nokia DN09185955 Issue: 01J . the loss counters in uplink can only report the number of these “missing” packets. Feature Descriptions and Instructions The objective is to provide the RRC connection establishment success and failure rates for RRCConnectionRequest message (from UE to eNB) in order to break down and classify RRC Connection Setup failures for troubleshooting/drill down purposes. Impact on interfaces This feature has no impact on interfaces. • LTE1074: Multimedia priority services is required to have the complementary set of counters to calculate the RRC setup success rate. U-plane counters for monitoring: • Delay Budget per QCI This objective is to provide the PDCP SDU delay per QCI on the downlink.314) per QCI (5. The introduced counters are used to create new KPI formulas. As such. Impact on network and network element management tools iOMS had to implement a new measurement type (M8026) Impact on system performance and capacity This feature has no impact on system performance or capacity. 2.. The measurement is done separately per QCI (1. Differentiating the signaling setup by causes helps in the analysis of the specific reason causing the failure..9) • Number of Uplink and Downlink PDCP Packet Loss (accord.. It also can be used to monitor the packet delay budget characteristics of the E-RAB's QCI. 2. and parameter documents. Table 159 New Measurements and counters Counter ID Counter name Measurement M8006C45 Sum of simultaneous E-RABs LTE EPS Bearer of QCI1 M8006C46 Sum of simultaneous E-RABs LTE EPS Bearer of QCI2 M8006C47 Sum of simultaneous E-RABs LTE EPS Bearer of QCI3 M8006C48 Sum of simultaneous E-RABs LTE EPS Bearer of QCI4 M8006C49 Sum of simultaneous E-RABs LTE EPS Bearer of QCI5 M8006C50 Sum of simultaneous E-RABs LTE EPS Bearer of QCI6 M8006C51 Sum of simultaneous E-RABs LTE EPS Bearer of QCI7 M8006C52 Sum of simultaneous E-RABs LTE EPS Bearer of QCI8 M8006C53 Sum of simultaneous E-RABs LTE EPS Bearer of QCI9 M8006C54 Denominator for Sum of LTE EPS Bearer simultaneous E-RABs M8013C34 Signaling Connection LTE UE State Establishment attempts for delay tolerant access M8013C35 Signaling Connection LTE UE State Establishment completions for mobile originating signaling M8013C36 Signaling Connection LTE UE State Establishment completions for mobile originating calls M8013C37 Signaling Connection LTE UE State Establishment completions for mobile terminating access M8013C38 Signaling Connection LTE UE State Establishment completions for delay tolerant access DN09185955 Issue: 01J © 2016 Nokia 275 . LTE RL60. counter. Measurements and counters Table 159: New Measurements and counters lists measurements and counters introduced with this feature. see Reference documentation. key performance indicator. Feature Descriptions and Instructions Descriptions of operability features 6. Alarms There are no new alarms related to this feature.5 Management data For information on alarm.1.4. Feature Descriptions and Instructions Table 159 New Measurements and counters (Cont. Descriptions of operability features LTE RL60.) Counter ID Counter name Measurement M8013C39 Number of rejected Signaling LTE UE State Connection Establishment Requests for mobile originating signaling M8013C40 Number of rejected Signaling LTE UE State Connection Establishment Requests for mobile originating calls M8013C41 Number of rejected Signaling LTE UE State Connection Establishment Requests for mobile terminating access M8013C42 Number of rejected Signaling LTE UE State Connection Establishment Requests for delay tolerant access M8026C0 Number of lost PDCP SDUs in LTE QoS UL for QCI 5 M8026C1 Number of lost PDCP SDUs in LTE QoS UL for QCI 6 M8026C2 Number of lost PDCP SDUs in LTE QoS UL for QCI 7 M8026C3 Number of lost PDCP SDUs in LTE QoS UL for QCI 8 M8026C4 Number of lost PDCP SDUs in LTE QoS UL for QCI 9 M8026C5 Number of lost PDCP SDUs in LTE QoS DL for QCI 5 M8026C6 Number of lost PDCP SDUs in LTE QoS DL for QCI 6 M8026C7 Number of lost PDCP SDUs in LTE QoS DL for QCI 7 M8026C8 Number of lost PDCP SDUs in LTE QoS DL for QCI 8 M8026C9 Number of lost PDCP SDUs in LTE QoS DL for QCI 9 M8001C309 PDCP SDU delay on DL DTCH LTE Cell Load Mean for non-GBR DRBs of QCI 5 M8001C310 PDCP SDU delay on DL DTCH LTE Cell Load Mean for non-GBR DRBs of QCI 6 M8001C311 PDCP SDU delay on DL DTCH LTE Cell Load Mean for non-GBR DRBs of QCI 7 M8001C312 PDCP SDU delay on DL DTCH LTE Cell Load Mean for non-GBR DRBs of QCI 8 276 © 2016 Nokia DN09185955 Issue: 01J . LTE RL60. Feature Descriptions and Instructions Descriptions of operability features Table 159 New Measurements and counters (Cont.) Counter ID Counter name Measurement M8001C313 PDCP SDU delay on DL DTCH LTE Cell Load Mean for non-GBR DRBs of QCI 9 M8026C30 Average HARQ transmission LTE QoS time for TBs with QCI 1 data M8026C31 Average HARQ transmission LTE QoS time for TBs with QCI 2 data M8026C32 Average HARQ transmission LTE QoS time for TBs with QCI 3 data M8026C33 Average HARQ transmission LTE QoS time for TBs with QCI 4 data M8026C34 Average HARQ transmission LTE QoS time for TBs with QCI 5 data M8026C35 Average HARQ transmission LTE QoS time for TBs with QCI 6 data M8026C36 Average HARQ transmission LTE QoS time for TBs with QCI 7 data M8026C37 Average HARQ transmission LTE QoS time for TBs with QCI 8 data M8026C38 Average HARQ transmission LTE QoS time for TBs with QCI 9 data 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 M8026C254 Number of lost PDCP SDUs in LTE QoS UL M8026C255 Number of lost PDCP SDUs in LTE QoS UL for QCI 1 M8026C256 Number of lost PDCP SDUs in LTE QoS UL for QCI 2 M8026C257 Number of lost PDCP SDUs in LTE QoS UL for QCI 3 M8026C258 Number of lost PDCP SDUs in LTE QoS UL for QCI 4 M8026C259 Number of lost PDCP SDUs in LTE QoS DL DN09185955 Issue: 01J © 2016 Nokia 277 . ) Counter ID Counter name Measurement M8026C260 Number of lost PDCP SDUs in LTE QoS DL for QCI 1 M8026C261 Number of lost PDCP SDUs in LTE QoS DL for QCI 2 M8026C262 Number of lost PDCP SDUs in LTE QoS DL for QCI 3 M8026C263 Number of lost PDCP SDUs in LTE QoS DL for QCI 4 Key performance indicators Table 160: New key performance indicators lists key performance indicators introduced with this feature. QCI9 LTE_5310b E-UTRAN PDCP SDU Loss Ratio in the UL LTE_5311b E-UTRAN PDCP SDU Loss Ratio in the UL. QCI5 278 © 2016 Nokia DN09185955 Issue: 01J . QCI1 LTE_5312b E-UTRAN PDCP SDU Loss Ratio in the UL. QCI6 LTE_5452a E-UTRAN PDCP SDU Loss Ratio in the DL. QCI8 LTE_5454a E-UTRAN PDCP SDU Loss Ratio in the DL. QCI3 LTE_5314b E-UTRAN PDCP SDU Loss Ratio in the UL. QCI3 LTE_5308b E-UTRAN PDCP SDU Loss Ratio in the DL. QCI5 LTE_5451a E-UTRAN PDCP SDU Loss Ratio in the DL. QCI2 LTE_5307b E-UTRAN PDCP SDU Loss Ratio in the DL. QCI4 LTE_5450a E-UTRAN PDCP SDU Loss Ratio in the DL. QCI4 LTE_5455a E-UTRAN PDCP SDU Loss Ratio in the UL. QCI2 LTE_5313b E-UTRAN PDCP SDU Loss Ratio in the UL. QCI7 LTE_5453a E-UTRAN PDCP SDU Loss Ratio in the DL. Table 160 New key performance indicators KPI ID KPI name LTE_5304b E-UTRAN PDCP SDU Loss Ratio in the DL LTE_5305b E-UTRAN PDCP SDU Loss Ratio in the DL. Feature Descriptions and Instructions Table 159 New Measurements and counters (Cont. QCI1 LTE_5306b E-UTRAN PDCP SDU Loss Ratio in the DL. Descriptions of operability features LTE RL60. QCI6 LTE_5457a E-UTRAN PDCP SDU Loss Ratio in the UL. - 6.6 Sales information This feature is a basic software feature.1.4. Table 162 Sales information BSW/ASW License control in network element License control attributes BSW .1 Description of LTE1486 : Parameter Categorization Introduction to the feature DN09185955 Issue: 01J © 2016 Nokia 279 . QCI3 LTE_5259b E-UTRAN PDCP SDU Discard Ratio in DL.) KPI ID KPI name LTE_5456a E-UTRAN PDCP SDU Loss Ratio in the UL. Table 161 New Parameters Full name Full name Managed object Structure LTE QoS mtQoS PMRNL 6. QCI1 LTE_5257b E-UTRAN PDCP SDU Discard Ratio in DL. LTE RL60. QCI8 LTE_5459a E-UTRAN PDCP SDU Loss Ratio in the UL. QCI7 LTE_5458a E-UTRAN PDCP SDU Loss Ratio in the UL. QCI2 LTE_5258b E-UTRAN PDCP SDU Discard Ratio in DL. QCI4 LTE_5260b E-UTRAN PDCP SDU Discard Ratio in DL. Feature Descriptions and Instructions Descriptions of operability features Table 160 New key performance indicators (Cont. QCI9 LTE_5255b E-UTRAN PDCP SDU Discard Ratio in DL LTE_5256b E-UTRAN PDCP SDU Discard Ratio in DL. non GBR Parameters Table 161: New Parameters lists parameters introduced with this feature.5.5 LTE1486: Parameter Categorization 6. 3 Functional description This feature introduces two new predefined Editor Views for CM Editor to show the two parameter categories: • Basic: The ‘Basic Parameters’ category contains primary parameters which should be considered during cell deployment and must be adjusted to a particular scenario.0 LBTS6.5. - Hardware requirements This feature requires no new or additional hardware. frequency plan. • simplified network parameterization • faster product rollouts and less effort for competence development • reduced efforts for network planning commissioning • reduced efforts for trouble-shooting due to decreased probably of wrong configurations 6.1.0 OMS6. Table 163 Software Requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 LBTS6.5.1 Benefits End-user benefits This feature does not affect the end-user experience. Feature Descriptions and Instructions This feature offers the users of Configurator a grouping of the existing CM parameters.2 Requirements Software requirements The following table lists software required for this feature.0 UE NetAct MME SAE GW .5. 6. in order to have easy means to differentiate between parameters the operator needs for daily use (Basic Parameters) and parameters that are needed less frequently (Advanced Parameters).1. 6. – Planning parameters like neighbor definitions. scrambling code plan. RA preamble plan etc – Output from dimensioning (parameters defining amount of resources) 280 © 2016 Nokia DN09185955 Issue: 01J . NetAct8 EP1 .1. Operator benefits This feature benefits the operator as follows: • Simplfication of the plan file and limitation of the number of parameters to be managed reduces the customer expenses (OPEX). PCI plan. IP address etc. These are: – Configuration parameters like NE ids. Descriptions of operability features LTE RL60. Impact on network and network element management tools This feature has no impact on network management or network element management tools. handovers.4 System impact Interdependencies between features There are no interdependencies between this and any other feature. Impact on system performance and capacity This feature has no impact on system performance or capacity. 6. Key performance indicators There are no key performance indicators related to this feature. LTE RL60. thresholds for power control. – Universal defaults ensuring decent network performance need to be defined for all parameters in this category (if this is not possible for given parameter this must be put in Basic parameters Category). Impact on interfaces This feature has no impact on interfaces. traffic steering.5 Management data Alarms There are no new alarms related to this feature Measurements and counters There are no measurements or counters related to this feature. IUO.5. contained in CuDo and explained in NEI's • Advanced: The ‘Advanced Parameters’ category contains the parameters for network optimization and fine tuning. Parameters There are no new parameters related to this feature. – Advanced parameters that require detailed system knowledge and broad experience should be put in this category unless rules for Basic category are violated. cell resections.1. 6. tracing etc are to be defined in Advanced Parameters category. MML and NetAct. etc. – Network optimization and fine tuning parameters. – Parameters are visible in Network Element Manager. – Decent network performance should be achieved without tuning of these parameters.1.g.5. – All parameters (even with no defaults) that are related to advanced features like DFCA. e. Feature Descriptions and Instructions Descriptions of operability features – Parameters defining operators' strategy. DN09185955 Issue: 01J © 2016 Nokia 281 . high level parameters defining feature behavior. 5.1 Benefits End-user benefits This feature does not affect the end-user experience.1. 6.6.2 Requirements Software requirements Table 165: Software Requirements lists the software required for this feature.6. Feature Descriptions and Instructions 6. 282 © 2016 Nokia DN09185955 Issue: 01J .6 Sales information Table 164 Sales Information BSW/ASW License control in network License control attributes element BSW .6.1. - Hardware requirements This feature requires no new or additional hardware.1. 6. Table 165 Software Requirements System release Flexi Multiradio BTS Flexi Multiradio 10 OMS BTS RL60 LBTS6. 6. Operator benefits This feature provides the operator with a smooth upgrade path from release RL50 to release RL60.3 Functional description The LTE1560: System Upgrade to RL60 feature describes the SW upgrade from release RL50 to release RL60.0 LBTS6. Layer 3 Data Collector (L3DC) and Traffica.0 UE NetAct MME SAE GW . - 6.0 OMS6.1. these entities are considered for SW upgrade as well. The feature describes the overall system upgrade strategy and workflow. NetAct8 EP1 . including backward compatibility and possibility to fallback to release RL50. As release RL40 had introduced two new entities.1 Description of LTE1560: System Upgrade to RL60 Introduction to the feature The LTE1560: System Upgrade to RL60 feature enables the smooth system upgrade of the network from release RL50 to release RL60 including the backwards compatibility. Descriptions of operability features LTE RL60.6 LTE1560: System Upgrade to RL60 6.6. No intermediate SW versions are required. g Note: It is recommended to perform the system upgrade during low traffic load (for example during night time) as service degradation and partial service loss cannot be fully avoided during the upgrade. Therefore. Feature Descriptions and Instructions Descriptions of operability features The upgrade from release RL50 to release RL60 is possible in one step. HW upgrade is not combined with the SW upgrade. it is not necessary to take the whole system out of service for introducing a new SW release. the NetAct must be able to manage the network elements (NE) of release RL60 and release RL50.5 -> NetAct 8 EP1 During system upgrade. The upgrade paths for Flexi Multiradio platform are: • FSME to FSME • FSMF to FSMF The following upgrade path needs to be performed for successful system upgrade as presented in Figure 21: Top-down approach for the system upgrade: • Step A1 NetAct upgrade: NetAct OSS5. LTE RL60. DN09185955 Issue: 01J © 2016 Nokia 283 . The eNB upgrade can be managed locally from BTSSM or remotely from NetAct. The system upgrade is performed in a top-down approach as shown in Figure 21: Top- down approach for the system upgrade: Figure 21 Top-down approach for the system upgrade RL70 Optional elements NetAct NetAct Traffica Traffica new release old release new release old release Top down OMS OMS L3DC L3DC new release old release new release old release eNB eNB eNB eNB new release old release old release old release FDD-LTE 15A During the system upgrade from RL50 to RL60. The iOMS upgrade can also be managed locally and can be done using CLI based AMSURT tool. Service outages are minimized by using available resiliency features and hardware redundancy. • Step B1 Traffica upgrade: Traffica 6 SP2 (+ TSN1215) -> Traffica 6 SP3 There is no dependency between the Traffica upgrade and the NetAct. the data conversion performed by the eNB during the upgrade is automatically synchronized with the NetAct Configuration Manager (CM). It is not needed to upgrade all iOMSes of an LTE network to upgrade the first eNB.0 -> iOMS 6. BTS configuration. • Traffica with release RL60 needs to support L3DC and eNB with releases RL50 and RL60. the manual commit from CLI is supported to indicate that the new SW is stable.5 -> L3DC7. Instead.There is no dependency between eNB upgrade and Traffica/L3DC upgrade.0 This step needs to be executed after the controlling iOMS has been upgraded.0 This step is executed after Traffica has been upgraded.0 -> LBTS 6. The NetAct synchronization is covered by the LTE954: Intelligent configuration synchronization feature. the CLI based Automatic Major SW Upgrade Runner Tool (AMSURT) is used. no important information of all NE is lost. trace. After iOMS upgrade. To make the upgrade procedure more efficient. • Step A3 eNB upgrade: LBTS 5. iOMS. RNW configuration. That includes: • network security related system data information (for example certificates. passwords) • symptom. Feature Descriptions and Instructions • Step A2 iOMS upgrade: iOMS 5. Descriptions of operability features LTE RL60. 284 © 2016 Nokia DN09185955 Issue: 01J . it is recommended to upgrade Traffica in parallel with NetAct. since unknown messages will be ignored by L3DC. no problems are expected. keys) • user security related data (for example user accounts. • L3DC with release RL60 needs to support eNB with releases RL50 and RL60. After system upgrade and fallback. it is possible to upgrade a complete branch of the hierarchy from the iOMS to the eNBs. however it is recommended to upgrade the eNB after L3DC has been upgraded. PM data configuration) Backward compatibility Backward compatibility means that interworking between upgraded and non-upgraded NEs is possible during system upgrade.0 The iOMS upgrade needs to be performed after a successful NetAct upgrade. • iOMS with SW release RL60 needs to support eNB with releases RL50 and RL60. If eNB is upgraded and L3DC is still in old version. and eNB upgrade. and log data • configuration data (which includes for example: transport configuration. As a consequence of the top-down approach: • NetAct with release RL60 needs to support iOMS and eNB with releases RL50 and RL60. For the iOMS upgrade. g Note: After the eNB upgrade. • Step B2 L3DC upgrade: L3DC6. The service is re-establihed only after the SW is downloaded from the NetAct. g Note: In case of automatic fallback. Impact on interfaces This feature has no impact on interfaces. Impact on network and network element management tools This feature has no impact on network management or network element management tools. since the eNB takes the configuration database into service that fits to the fallback SW. After a fallback. eNB RL50) must be supported by L3DC and Traffica. After successful fallback. which is used after the eNB upgrade data conversion synchronization with NetAct. Manual software fallback can be triggered by the operator when key services were not activated successfully after the SW upgrade.4 System impact Interdependencies between features The LTE954: Intelligent configuration synchronization feature covers the NetAct synchronization function. Feature Descriptions and Instructions Descriptions of operability features In addition also. A SW downgrade to a SW version that is lower than currently active and that wasn’t active before SW upgrade isn’t guaranteed and may end up in an uncommissioned state of the eNB. the passive software build is active in all HW units and service can be re-established. Software fallback eNB Software fallback can either be triggered manually by the operator or executed automatically by the system. The eNB SW of a new release (RL60) is backward compatible with the configuration data of former base release (RL50). eNB RL50) must be supported by iOMS and NetAct. mixed eNB and OMS configurations (for example iOMS RL60. and read configuration data of former release as input for conversion to the new format. the eNB configuration must be synchronized with NetAct via NetAct CM Upload (LTE954: Intelligent configuration synchronization feature description is not available in RL35TD release). LTE RL60. Note that manual software fallback is only guaranteed if the source SW version has not been removed or overwritten in a non-volatile storage (NVS).6. Since the eNB doesn't store the complete fallback SW for all HW units locally. Automatic software fallback is triggered by the system when the active software build is corrupted or a restart loop is detected or critical exceptions while data is being converted to new format. 6. This is necessary to support automatic online data conversion.1. Any configuration updates done with the new SW will be lost. NE raises an alarm ( 7650 BASE STATION FAULTY) to indicate that the upgrade was not successful. while mixed L3DC and eNB configurations (for example L3DC RL60. The new SW after start up. can access. the eNB requests a software update for the latest active software build version from the NetAct. It is executed in the same way as a software download and activation. Impact on system performance and capacity DN09185955 Issue: 01J © 2016 Nokia 285 . 286 © 2016 Nokia DN09185955 Issue: 01J . 6.5 LTE1560: System Upgrade to RL60 management data For information on alarm. for multi-antenna RET devices connected to the Flexi Multiradio BTS. An antenna may support transmission/reception on different frequency bands within one physical housing.7. . when NEs become fully or partially unavailable. Alarms Table 166: Related existing alarm lists an existing alarm related to this feature. see Reference documentation.6. Yes 6. as described in the Iuant-interface specification 3GPP TS25. but this is out of scope of this feature description. and parameter documents. some new functionalities are implemented which might impact the overall system performance and capacity. whereby the antenna beam downtilt for each frequency band can be controlled separately via a built-in multi-antenna RET-device. 6. Table 166 Related existing alarm Alarm ID Alarm name 7650 BASE STATION FAULTY Measurements and counters There are no measurements or counters related to this feature. counter.6. Descriptions of operability features LTE RL60.1 Description of LTE1657: Support for Multi-antenna RET device Introduction to the feature This feature introduces support. key performance indicator.1.1.7 LTE1657: Support for Multi-antenna RET device 6. Key performance indicators There are no key performance indicators related to this feature.6 Sales information Table 167 Sales Information BSW/ASW License control in network License control Activated by default element attributes BSW . Feature Descriptions and Instructions Overall system performance and capacity might be affected during the upgrade procedure. Parameters There are no parameters related to this feature.466. With the new SW. 7. Impact on interfaces This feature has no impact on interfaces. Flexi Multiradio BTS supports the configuration of the tilt for each supported frequency band (configuration of beam tilt per frequency band per sector). the Flexi Multiradio BTS supports only single antenna RET-device.1.4 System impact Interdependencies between features There are no interdependencies between this and any other feature. - Hardware requirements The Operator can only install Iuant-compliant 3GPP TS25. Table 168 Software Requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 LBTS6. Feature Descriptions and Instructions Descriptions of operability features 6.1. This feature introduces Flexi Multiradio BTS support for communication to a multi- antenna RET-device.7.0 UE NetAct MME SAE GW .1.3 Functional description An operator may deploy antenna types supporting more than one frequency band. At the moment. For each supported frequency band the physical downtilt of the beam can be configured per given frequency band using a built-in multi-antenna RET-device (Remote Electrical Tilt).7. for example.1 Benefits End-user benefits This feature does not affect the end-user experience. NetAct8 EP1 .0 LBTS6. DN09185955 Issue: 01J © 2016 Nokia 287 .7. type 17). 6. LTE RL60. as used by antenna types supporting more than one frequency band (device type '0x11'. according to the Iuant-interface specification (3GPP TS25. 6.466 multi-antenna RET devices. which can be controlled and configured independently by the Nokia network management system (NetAct/3rd party NMS or BTS Site Manager).466).1. 6. Operator benefits This feature benefits the operator as follows: Support for Multi-antenna RET devices by Flexi Multiradio BTS.0 OMS6.2 Requirements Software requirements The following table lists software required for this feature. dual band antenna. From an object-modelling perspective. 6. 6.7.1 Description of LTE1708: Extend Maximum Number of X2 Links Introduction to the feature The LTE1708: Extend Maximum Number of X2 Links feature extends the number of supported X2 links within the eNB from 64 to 256 X2 links for FSMr3 and from 64 to 128 for FSMr2 or FZM.8. - 6.6 Sales information Table 169 Sales Information BSW/ASW License control in network License control attributes element BSW . Impact on system performance and capacity This feature has no impact on system performance or capacity. 288 © 2016 Nokia DN09185955 Issue: 01J . 6. 6. Descriptions of operability features LTE RL60.8.1. Feature Descriptions and Instructions Impact on network and network element management tools This feature has no impact on network management or network element management tools.1 Benefits End-user benefits Learning of new important X2 links is not blocked even when seldomly used X2 links are kept. more flexible handling of neighbor relations (NRs) is possible.5 Management data Measurements and counters There are no measurements or counters related to this feature.8.1.1.8 LTE1708: Extend Maximum Number of X2 Links 6. Key performance indicators There are no key performance indicators related to this feature. Operator benefits With the increase of number of X2 links in the eNB.1.2 Requirements Software requirements Table 170: Software Requirements lists the software required for this feature.7. 2 carriers per cell In case that higher values. LTE RL60. the system performance could be decreased.8. X2 link setup time The setup time for the X2 links is considered independently of eNB restart time. also the learned neighbor cells are considered. - Hardware requirements This feature requires no new or additional hardware. The Table 171: Maximum number of supported neighbor objects shows the maximum number of neighbor objects which are supported: Table 171 Maximum number of supported neighbor objects Object MO per FSMr2 FSMr3 FZM neighbor eNB LNADJ source eNB 128 256 128 neighbor cell LNADJL neighbor eNB 64 64 64 neighbor cell (total) LNADJL source eNB 768 1536 768 source cell LNCEL source eNB 6 18 1 neighbor relationship LNREL source cell 389 389 389 neighbor relationship LNREL source eNB 480 1728* 389 (total) * assumption: 48 LNREL per carrier. The increase of the number of X2 links are realized in the following way: • The size of the X2 black-list table is increased. NetAct8 EP1 .1. • With the setup of 256 (128) X2 links.0 - The functionalities are valid for RL70.3 Functional description The LTE1708 Extend Maximum Number of X2 Links feature introduces the extension of the number of supported X2 links within the eNB from 64 to 256 X2 links for FSMr3 and from 64 to 128 for FSMr2 and FZM. • The X2 links associated/represented by oamControlled LNADJs are set up first within a time limit of 20 minutes. Feature Descriptions and Instructions Descriptions of operability features Table 170 Software Requirements System release Flexi Multiradio BTS Flexi Multiradio 10 BTS OMS RL60 LBTS6. The finalization of the X2 links setup might take much longer than the eNB restart time.0 LBTS6. as presented in the Table 171: Maximum number of supported neighbor objects are used. Taking 6 cells per eNB in average into account an overall amount of 256x6 = 1536 (FSMr3) and 128x6 = 768 (FSMr2 and FZM) neighbor cells can be considered. DN09185955 Issue: 01J © 2016 Nokia 289 . 6. UE NetAct MME SAE GW . . • When the FSMr2 or FZM HW is used: – If the Max number of LNADJ instances (maxNumOfLnadjLimit) parameter is configured in a range between 0 .. – parameter range: 0. It shall never be configured to a value higher than the system supports. or 256 in case of FSMr3 hardware. The LTE1708 Extend Maximum Number of X2 Links feature introduces two new parameters: • Max number of LNADJ instances (maxNumOfLnadjLimit) – This operator-configurable parameter configures the overall number of LNADJ instances. The eNB allows creation of new LNADJs by operator or ANR functions up to this limit. • creation via plan file In case that a plan download fails because the maximum number of LNADJ instances is reached then the related response message contains the text: Maximum number of LNADJ instances reached. then the system accepts the value. but do not need to be established within the time limit.. and 256 for FSMr3. LNADJ limit The limit of maximum number of LNADJ instances is 128 for FSMr2 and FZM. – It is the ENUM type: {128.. • Supported number of LNADJ instances (supportedNumOfLnadj) – This parameter defines the number of system-supported LNADJ instances. The configuration file is sent to the eNB. Descriptions of operability features LTE RL60. Feature Descriptions and Instructions • The X2 links associated/represented by enbControlled LNADJs can be set up after the oamControlled. 290 © 2016 Nokia DN09185955 Issue: 01J . – It has value set by system. • autonomous creation In case that an autonomous LNADJ instance creation (caused by ANR) cannot be executed. It has the value 128 in case of used FSMr2 and FZM. Use cases Configuring the maximum number of LNADJ • When the FSMr3 HW is used: the full range of the Max number of LNADJ instances (maxNumOfLnadjLimit) parameter can be configured. The configuration file is sent to the eNB. for FSMr2. then the existing fault 6265: EFaultId_MaximumNumberOfNeighborEnbsOrCellsExceeded is sent to the operator. because the maximum number of LNADJ instances is reached. 256}. 128.256 – mandatory with default value: 256 g Note: The default value of the maxNumOfLnadjLimit parameter is set for FSMr3. independent of the default. the maximum permitted value is 128. or 256 for FSMr3. Planning based on the HW information per the eNB site is started in the NetAct Optimizer. and the Max number of LNADJ instances (maxNumOfLnadjLimit) parameter is at default 256. 128) LNADJ instances (oamControlled) will be created for the eNBs with FSMr2 or FZM HW variant information in the commissioning part • up to minimum (the Optimizer user preference. Feature Descriptions and Instructions Descriptions of operability features – If the Max number of LNADJ instances (maxNumOfLnadjLimit) parameter is configured in a range between 129 . • FSMr3: supportedNumOfLnadj=256 For configurations with less than 256 LNADJ instances in the plan. and the Supported number of LNADJ instances (supportedNumOfLnadj)). those with priorities from 129 onwards are deleted by the NetAct Optimizer. • up to minimum (the Optimizer user preference. g Note: If the planned HW information is not identical to the variants installed in the field. This is allowed only if the number of LNADJ instances do not exceed the limits given by the system or the user: no more than 128 (FSMr2 or FZM) / 256 (FSMr3). or the Max number of LNADJ instances (maxNumOfLnadjLimit) shall be created. the eNB tries to setup X2/S1 and tries to create an additional LNADJ instance. FZM. The maximum allowed number of instances is min (the Max number of LNADJ instances (maxNumOfLnadjLimit). then the validation in BTS SiteManager indicates a range violation due to the HW limitation. the unitTypeExpected and the Max number of LNADJ instances (maxNumOfLnadjLimit) parameters are used. Planing the network with the Optimizer for N eNBs In case of auto-cofiguration. the Optimizer assignes additional LNADJ instances if applicable. DN09185955 Issue: 01J © 2016 Nokia 291 . following restrictions are expected: • target FSMr2/FZM but real is FSMr3: no optimal configuration could be planned • target FSMr3 but real is FSMr2/FZM: capacity problems are expected (in the worst case: the machine crashes and a site visit is needed) When the real HW information of all planned sites is available (the Supported number of LNADJ instances (supportedNumOfLnadj) parameter is set by system to 128 for FSMr2/FZM. or the user set it to smaller value). 256. Max number of LNADJ instances (maxNumOfLnadjLimit). LTE RL60. Max number of LNADJ instances (maxNumOfLnadjLimit). 256) LNADJ instances (oamControlled) will be created for eNBs with FSMr3 HW variant information in the commissioning part. nor FSMr3.. the planning based on the HW capacity value delivered by eNB is started in the NetAct Optimizer: • FSMr2/FZM: supportedNumOfLnadj=128 For configurations with more than 128 LNADJ instances in the plan. Learning of new neighbor eNBs/cells with ANR activated in the eNB When the UE reports a new neighbor cell not known to the eNB. The Optimizer does not exceed the limit for supported number of LNADJ instances neither for FSMr2.. The configuration file is not sent to the eNB. 8. Descriptions of operability features LTE RL60. and 256 for FSMr3. the validation passes. where N-M is the maximal configured limit for the eNB-controlled X2 links. Migration to RL60 release content The migration is done according to the rules in the MRBTS unitList. g Note: Extending the value to P (>N) results that the new configuration and the UE- based X2 learning is used immediately as long as the maxNumX2LinksOut/maxNumX2LinksIn limit is exceeded. and the operator gets the information that the number of created LNADJ instances exceeds the defined value of the Max number of LNADJ instances (maxNumOfLnadjLimit) parameter. Feature Descriptions and Instructions Reconfiguration of new neighbor eNBs/cells with ANR activated in the eNB When the real HW information of all planned sites is available. 6. the validated file is sent to the eNB to start using the reconfigured BTS configuration. or 256 for FSMr3 • the Max number of LNADJ instances (maxNumOfLnadjLimit) parameter is set to value N (not violating the given fast subscriber management (FSM) variant limit) • the eNB established M (<N) the operator-configured and N-M the UE-reported adjacent eNB. Impact on interfaces 292 © 2016 Nokia DN09185955 Issue: 01J . that is: • the Supported number of LNADJ instances (supportedNumOfLnadj) parameter is set by system to 128 for FSMr2/FZM.4 System impact Interdependencies between features There are no interdependencies between this and any other feature. Affected features The LTE539: Central ANR feature: the values of the current design are changed to 128 for FSMr2 or FZM. then the system validates the change: • If the number of LNADJ instances is less than or equal to the new value O. Change of association of neighbor cell-related handover measurements The association of neighbor cell-related handover measurements is changed as follows: • intra-LTE neighbor cell-related handover counters: MType M8015 The M8015Cxx counters are changed from LNADJL to LNREL objects. then the validation fails. If no other validation error included. • inter-system neighbor cell-related handover counters: MType M8019 (LTE to GSM) The M8019Cxx counters are changed from LNADJG to LNRELG objects. and the operator changes the value of the Max number of LNADJ instances (maxNumOfLnadjLimit) parameter to O (<N).1. • inter-system neighbor cell-related handover counters: MType M8017 (LTE to WCDMA) The M8017Cxx counters are changed from LNADJW to LNRELW objects. • If the number of LNADJ instances is greater than the new value O. The configuration need to be corrected (the number of LNADJ instances should be less than or equal to the new value O). Table 173 Related existing counters Counter ID Counter name Measurement M8015C0 Failed Intra eNB HO preparations per 8015 - LTE Neighbor cell related neighbor cell Handover (WBTS) M8015C1 Intra eNB HO attempts per neighbor cell 8015 - LTE Neighbor cell related Handover (WBTS) M8015C2 Intra eNB HO successes per neighbor cell 8015 - LTE Neighbor cell related Handover (WBTS) M8015C5 Number of failed Inter eNB Handover 8015 - LTE Neighbor cell related preparations per neighbor cell relationship Handover (WBTS) M8015C6 Failed Inter eNB Handover preparations 8015 - LTE Neighbor cell related per neighbor cell due to expir.5 Management data For information on alarm. and LNRELG objects instead of an LNADJL-. of guard Handover (WBTS) timer TX2RELOCprep M8015C7 Failed Inter eNB Handover preparations 8015 - LTE Neighbor cell related per neighbor cell due to admission control Handover (WBTS) in the target eNB M8015C8 Number of Inter eNB Handover attempts 8015 - LTE Neighbor cell related per neighbor cell relationship Handover (WBTS) M8015C9 Number of successful Inter eNB Handover 8015 - LTE Neighbor cell related completions per neighbor cell relationship Handover (WBTS) DN09185955 Issue: 01J © 2016 Nokia 293 . counter.1. Alarms Table 172: Related existing alarms lists existing alarms related to this feature. LTE RL60.8. and LNADJG-based relation. To avoid a significant increase of the PM counter instances the relation of the neighbor cell-related PM counters is changed to LNREL. the increase of LNADJ impacts the SCF file size as well as the number of the X2 links. LNADJW-. LNRELW. Feature Descriptions and Instructions Descriptions of operability features This feature has no impact on interfaces. see Reference documentation. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Table 172 Related existing alarms Alarm ID Alarm name 6265 EFaultId_MaximumNumberOfNeighbourEnbsOrCellsExceeded Measurements and counters Table 173: Related existing counters lists existing counters related to this feature. key performance indicator. and parameter documents. Additionally. SCTP and X2 protocol management is increased by the higher number of active links. 6. Impact on system performance and capacity Increased amount of neighbors gives the increased amount of PM counters. Feature Descriptions and Instructions Table 173 Related existing counters (Cont.) Counter ID Counter name Measurement M8015C10 Number of Inter eNB Handover failures 8015 - LTE Neighbor cell related per cause per neighbor cell relationship Handover (WBTS) M8015C15 Intra eNB HO failures per neighbor cell 8015 - LTE Neighbor cell related Handover (WBTS) M8015C16 Number of Late Handover per neighbor 8015 - LTE Neighbor cell related cell relationship Handover (WBTS) M8015C17 Number of Early Handover Type1 per 8015 - LTE Neighbor cell related neighbor cell relationship Handover (WBTS) M8015C18 Number of Early Handover Type2 per 8015 - LTE Neighbor cell related neighbor cell relationship Handover (WBTS) M8017C4 Failed Inter System Handover 8017 - LTE Inter System Handover to preparations to UTRAN due to expiration UTRAN per Neighbor Cell (WBTS) of guarding timer per neighbor cell relationship M8017C5 Failed Inter System Handover 8017 - LTE Inter System Handover to preparations to UTRAN due to admission UTRAN per Neighbor Cell (WBTS) control in target cell per neighbor cell relationship M8017C6 Failed Inter System Handover 8017 - LTE Inter System Handover to preparations to UTRAN due to other UTRAN per Neighbor Cell (WBTS) reasons in target cell per neighbor cell relationship M8017C7 Inter System Handover attempts to 8017 - LTE Inter System Handover to UTRAN per neighbor cell relationship UTRAN per Neighbor Cell (WBTS) M8017C8 Successful Inter System Handover 8017 - LTE Inter System Handover to completions to UTRAN per neighbor cell UTRAN per Neighbor Cell (WBTS) relationship M8017C9 Failed Inter System Handover attempts to 8017 - LTE Inter System Handover to UTRAN per neighbor cell relationship UTRAN per Neighbor Cell (WBTS) M8017C10 Inter System Handover preparations per 8017 - LTE Inter System Handover to neighbor cell relationship UTRAN per Neighbor Cell (WBTS) M8017C11 Inter System Handover attempts to 8017 - LTE Inter System Handover to UTRAN with SRVCC per neighbor cell UTRAN per Neighbor Cell (WBTS) relationship M8017C12 Successful Inter System Handover 8017 - LTE Inter System Handover to completions to UTRAN with SRVCC per UTRAN per Neighbor Cell (WBTS) neighbor cell relationship M8017C13 Failed Inter System Handover attempts to 8017 - LTE Inter System Handover to UTRAN with SRVCC per neighbor cell UTRAN per Neighbor Cell (WBTS) relationship M8019C0 Number of NACC from LTE to GSM 8019 - LTE Inter System Handover to attempts per neighbor cell relationship GSM per Neighbor Cell (WBTS) M8019C3 Inter System Handover attempts to 8019 - LTE Inter System Handover to GERAN with SRVCC per neighbor cell GSM per Neighbor Cell (WBTS) relationship M8019C4 Successful Inter System Handover 8019 - LTE Inter System Handover to completions to GERAN with SRVCC per GSM per Neighbor Cell (WBTS) neighbor cell relationship 294 © 2016 Nokia DN09185955 Issue: 01J . Descriptions of operability features LTE RL60. ) Counter ID Counter name Measurement M8019C5 Failed Inter System Handover attempts to 8019 - LTE Inter System Handover to GERAN with SRVCC per neighbor cell GSM per Neighbor Cell (WBTS) relationship Key performance indicators There are no key performance indicators related to this feature.1. LTE RL60. Table 174 New parameters Full name Abbreviated name Managed object Max number of LNADJ instances maxNumOfLnadjLimit LNBTS Supported number of LNADJ instances supportedNumOfLnadj LNBTS Maximum number of eNB-controlled maxNumX2LinksIn LNBTS incoming X2-links Maximum number of eNB-controlled maxNumX2LinksOut LNBTS outgoing X2-links Table 175: Related existing parameters lists existing parameters related to this feature.6 Sales information Table 176 Sales Information BSW/ASW License control in License control Activated by network element attributes default BSW . Parameters Table 174: New parameters lists parameters introduced with this feature. Feature Descriptions and Instructions Descriptions of operability features Table 173 Related existing counters (Cont.8. Table 175 Related existing parameters Full name Abbreviated name Managed Structure object Neighbour eNB identifier lnAdjId LNADJ - Global eNB id X2-link glbNbEnbIdX2LinkBl LNBTS - blacklist acklist X2 blacklisted eNB ID enbId LNBTS glbNbEnbIdX2LinkBlacklist X2 blacklisted global eNB mcc LNBTS glbNbEnbIdX2LinkBlacklist id MCC X2 blacklisted global eNB mnc LNBTS glbNbEnbIdX2LinkBlacklist id MNC X2 blacklisted global eNB mncLength LNBTS glbNbEnbIdX2LinkBlacklist id MNC length 6. . Yes DN09185955 Issue: 01J © 2016 Nokia 295 . 9 LTE1909: BTS Diagnostics Toolkit used by operator 6. This feature supports resolving an error at first occurrence given that all the necessary information is available for detailed analysis. BTS snapshot data.9. situations where the fault must be reproduced in the network. technical support and the Nokia developer with efficient data collection from eNB.0 0 UE NetAct MME SAE GW n/a .1 LTE1909 benefits Operator benefits This feature improves the trouble shooting situation by supporting automatic data collection.1. Additionally.1.9. which requires presence of trained engineers at the customer site.1 Description of LTE1909: BTS Diagnostics Toolkit used by operator Introduction to the feature The LTE1909: BTS Diagnostics Toolkit provides the operator.9. 6. Table 177 Software requirements System Release Flexi Multiradio BTS Flexi Multiradio 10 OMS BT RL60 LBTS6. such as: trace data. - Hardware requirements This feature requires that a Layer 3 Data Collector (L3DC) is used in the customer network. . This leads to reduction of OPEX and error-solving time with a high correction hit rate. Descriptions of operability features LTE RL60. Other requirements 296 © 2016 Nokia DN09185955 Issue: 01J . Feature Descriptions and Instructions 6. based on the trigger events in the cell trace content • comes with the SW of the Layer 3 Data Collector • is easy to use and install 6. is sent from the operator to Nokia. become much rarer.2 LTE1909 requirements Software requirements Table 177: Software requirements lists the software required for this feature. The set of data collected.0 LBTS6. The following are the functions/features of this toolkit: • supervises the eNBs via cell tracing • triggers the BTS snapshot creation in a timely manner. These are used as triggers to invoke a snapshot on that specific eNB. the operator can choose which should actually trigger a snapshot.9. Feature Descriptions and Instructions Descriptions of operability features 6.4 LTE1909 system impact Interdependencies between features Impact on Interfaces There are no interdependencies between this and any other feature Impact on commands There are no commands related to this feature Impact on network element management tools This feature has no impact on network management or network element management tools.1. 6. Monitoring of eNBs After the connection with the selected eNBs. When snapshot file is available. and must be "placed" inside a customer secured IP area. and can be changed at any time. Detection of critical situation in eNB and snapshot triggering Some cell trace messages indicate a suspected or actual malfunction. The cell trace content is made visible to the operator by decoding the messages relevant for him. The Layer 3 Data Collector is installed on a PC or server with Windows OS. The operator chooses the eNBs according to the strategic relevance.9.5 LTE1909: BTS Diagnostics Toolkit used by operator management data Alarms There are no alarms related to this feature Measurements and counters DN09185955 Issue: 01J © 2016 Nokia 297 .1.3 LTE1909 functional description Diagnostics toolkit setup The Diagnostics toolkit based on Layer 3 Data Collector can be connected to a relevant bundle (up to 200) of eNB via TCP based connection. the operator may deliver it to Nokia for analysis.9. occurrence of high load. LTE RL60. or suspicion of malfunction. From a set of pre-defined trigger events. cell traces that must be activated are captured online all the time (no user plane data). Impact on system performance and capacity This feature has no impact on system performance or capacity. The configuration data for the connection settings can be easily imported via xls. 6.1. - 6.9. Figure 22 Selecting triggers for eNB snapshot collection 298 © 2016 Nokia DN09185955 Issue: 01J . Parameters There are no parameters related to this feature. it is possible to trigger an eNB snapshot collection based on selected events.9. Descriptions of operability features LTE RL60. Key performance indicators There are no key performance indicators related to this feature.6 LTE1909 sales information Table 178 Sales Information BSW/ASW License control in network License control attributes element BSW .1. Feature Descriptions and Instructions There are no measurements or counters related to this feature. 2 Go to Filter -> Set snapshot filter for TCP. 6.2 Triggering snapshot collection using LTE1909: BTS Diagnosis Toolkit With the LTE1909: BTS Diagnosis Toolkit feature. 3 Configure the triggering options in the opened window. Procedure 1 Open the L3DA. Result Once the selected event occurs. if LTE2 S1 Flex is in use. When the S1_MME link is locked using a new O&M parameter.1. During a new RRC connection setup. all UEs in RRC connected mode. 6. 6.1. 6. When the S1_MME link is unlocked. if present. supported by the locked S1_MME link. Feature Descriptions and Instructions Descriptions of operability features 4 Activate the filter. the eNB snapshot will be collected.10.1 LTE1910 benefits Operator benefits Cells of the eNodeB are kept in service during MME re-homing. the UE will be directed to another MME. allowing several MMEs per eNodeB. Other requirements DN09185955 Issue: 01J © 2016 Nokia 299 .10 LTE1910: S1 lock/unlock 6.1 Description of LTE1910: S1 lock/unlock Introduction to the feature The LTE1910: S1 lock/unlock S1 Lock/Unlock offers the possibility to lock and unlock the eNB S1_MME link to a target MME keeping the cells of the eNodeB in service.2 LTE1910 requirements Software requirements Table 179: Software Requirements lists the software required for this feature. The target MME link is possibly any operator's MME link when RAN sharing is in use.10. Table 179 Software Requirements System Release Flexi Multiradio BTS Flexi Multiradio 10 OMS BT RL60 LBTS6.10. are released and the SCTP association of the eNodeB to the MME is terminated.0 0 UE NetAct MME SAE GW n/a NetAct8 EP1 x - Hardware requirements This feature requires no new or additional hardware. LTE RL60.0 LBTS6. eNodeB establishes the SCTP association to the MME and handles the scenario the same way as the MME link recovery. 3 LTE1910 functional description Functional overview Operator is able to lock and unlock an eNB S1_MME link.10. in case of RAN sharing. Post-Condition For new connection requests the locked S1_MME link will never selected at MME selection. SCTP association of the eNodeB to the MME is terminated. if present. The locked MME is not considered in any MME selection procedures in the eNodeB. For DL data-driven cases. The NetAct Monitor Property Window shows the S1_MME administrative state as "unlocked" or "locked". Description 300 © 2016 Nokia DN09185955 Issue: 01J . GU Group Id list is forwarded to all neighbor eNB via eNB Configuration Update procedure. The GUMMEI-list and GU Group Id list are updated. Descriptions of operability features LTE RL60. The S1 feature is controlled with a new Operation and Maintenance (O&M) parameter per MME. One locked S1_MME link is unlocked. One S1_MME link is now locked via O&M. User Scenario 1910#2 Unlock S1_MME link with S1 flex Pre-Condition S1 flex is activated. Calls of the eNodeB connected to other potential other MMEs are not affected by the lock procedure. the eNodeB releases all the UEs in RRC connected mode supported by the locked S1 while RRC release is made using the cause code "other". No alarm is raised when the operator sets S1_MME as "locked". For UL-driven cases. S1_MME Link is set to be unavailable for new requests. The target MME can be any operator's MME. the UE is called from an available MME connected to the eNodeB.1. eNodeB establishes the SCTP association to the MME and handles the scenario in the same way as the MME link recovery. the UE initiates a new RRC connection setup and is directed to another MME. When S1 is unlocked. When the S1_MME is locked. Some S1_MME links are set to "locked". Feature Descriptions and Instructions 6. with a default value "unlocked". Description eNB C-Plane shuts down the SCTP association to the corresponding MME. while the operational state as "available" or "unavailable". to make a distinction between a locked and a faulty link. User scenario 1910#1 Lock S1_MME link with S1 flex Pre-Condition S1 flex is activated and eNB has more than one S1_MME links available. eNB triggers Reset and releases all impacted UE Contexts supported by this S1_MME link. The S1_MME link is set to be unavailable for new requests. The GU group ID list is forwarded to all neighbor eNB via an eNB configuration update procedure. Feature Descriptions and Instructions Descriptions of operability features The eNB establishes an SCTP association with the corresponding MME and performs S1 setup procedure.4 LTE1910 system impact Interdependencies between features LTE2 S1 Flex is required to get the most benefits of the S1 lock/unlock feature. Impact on network element management tools This feature has no impact on network management or network element management tools.10. If the S1 setup is successful. DN09185955 Issue: 01J © 2016 Nokia 301 . User scenario 1910#3 without S1 flex Pre-Condition S1 flex is deactivated. LTE RL60. S1_MME link is available. Impact on Interfaces There are no interdependencies between this and any other feature.5 LTE1910: S1 lock/unlock management data Alarms Table 180: New Alarms. the S1_MME link is set to be available. 6. The S1_MME link is locked via O&M. Post-Condition No S1_MME link is established anymore. Only one main MME. but is not mandatory. 6. No other S1_MME link is established even if other MMEs are configured in the eNB.10.1. Description The eNB C-Plane shuts down the SCTP association to the MME. The eNB triggers a Reset and releases all impacted UE contexts that is supported by this S1_MME link.1. Impact on commands There are no commands related to this feature. Post-Condition The eNB considers the S1_MME link as operational and uses it at MME selection. The GUMMEI-list and GU group ID list are updated. The GU group ID list is forwarded to all neighbor eNBs via the eNB configuration update procedure. Impact on system performance and capacity This feature has no impact on system performance and capacity. The GUMMEI-list and GU group ID list are updated. Incoming connection requests are rejected. lists alarms introduced with this feature. 6. Parameters All instances of the LNMME MOC new parameter.1.6 LTE1910 sales information Table 181 Sales Information BSW/ASW License control in network License control attributes element BSW . Feature Descriptions and Instructions Table 180 New Alarms Alarm ID Alarm name 6202 EFaultId_S1SctpEndpointAl 6204 EFaultId_S1SctpPathAl 6308 EFaultId_S1SetupRetryOut Measurements and counters There are no measurements or counters related to this feature. 'administrativeState'.10. Key performance indicators There are no key performance indicators related to this feature. - 302 © 2016 Nokia DN09185955 Issue: 01J . Descriptions of operability features LTE RL60. is added and set to "unlocked". +55°C • can be used as feederless site as well with one DC and 1.0 - UE NetAct MME SAE GW 3GPP R8 UE capabilities . DN09185955 Issue: 01J © 2016 Nokia 303 .1 LTE1440: FXFC Flexi RF Module 3TX 1900 7. .. - Hardware requirements This feature requires no new or additional hardware. LTE RL60. Table 182 Software Requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 LBTS6.1.1 Description of LTE1440: FXFC Flexi RF Module 3TX 1900 Introduction to the feature This feature introduces Flexi Multiradio RF Module FXFC for 1900 MHz band 2.1. 7.0 LBTS6.1.2 optical cables • TX div and MIMO 2TX can be build using two 3-sector RF Modules • low windload • easy installation 7..1 LTE1440 benefits End-user benefits This feature does not affect the end-user experience. HSPA+ and WCDMA and GSM/EDGE • 3 sector RF in one outdoor IP65 box • widest ambient temperature range -35°C. Feature Descriptions and Instructions Descriptions of BTS site solution features 7 Descriptions of BTS site solution features 7.1...2 LTE1440 requirements Software requirements Table 182: Software Requirements lists the software required for this feature.1. Operator benefits This feature benefits the operator as follows: • provides the most cost and size and weight optimized 3-sector BTS site • serves industry leading RF integration level • SW configurable radio: the same RF Module for LTE. 60. Impact on system performance and capacity New configurations are available. 1+1 or 1+1+1 LTE cells @ max 20 MHz LTE bandwith and 1TX/2RX • 8.1. 7.1.4 LTE1440 system impact Interdependencies between features There are no interdependencies between this and any other feature. Descriptions of BTS site solution features LTE RL60.3 FXFC functional description New high power 3-sector Flexi Multiradio RF Module introduces industry leading RF integration level and smallest power consumption combined with flexible GSM-WCDMA- LTE site evolution. Parameters There are no parameters related to this feature. The LTE1440: FXFC Flexi RF Module 3TX 1900 offers the following features: Basic LTE configurations: • 1.5 LTE1440: FXFC Flexi RF Module 3TX 1900 management data Alarms There are no alarms related to this feature. 40. Feature Descriptions and Instructions 7. 304 © 2016 Nokia DN09185955 Issue: 01J . 80 W mode per sector (by SW licenses) • 1 sector max 80 + 80 W 2TX/2RX MIMO • HW prepared for 1 sector max 80 + 80 W 2TX/4RX MIMO • 6 Gbps optical link support (OBSAI) • RET connector FXFC can be used in feederless (DC up to 200 m) BTS sites. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Full support for Multioperator sites with 80 W output power and 35 MHz RF bandwidth.1.1. 7. Impact on interfaces This feature has no impact on interfaces.1. 20. Key performance indicators There are no key performance indicators related to this feature.1. WCDMA and GSM/EDGE configurations are described in GSM/EDGE and WCDMA release documents. Measurements and counters There are no measurements or counters related to this feature. Operator benefits This feature benefits the operator as follows: • Increases baseband capacity of Flexi Multiradio 10 BTS System Module. LBTS6.1. g Note: In LBTS6. RF1.1 Description of LTE1444: FBBC Flexi Capacity Extension Sub-Module Introduction to the feature FBBC is a high capacity extension sub-module for Flexi Multiradio 10 BTS (FSMF).2 LTE1444 requirements Software requirements Table 184: Software requirements lists software required for this feature.0.0 RF3 handles the RF unit detection and communication. RF2 and SRIO/RF4 are to be supported in the future LTE SW release. - 7.1 LTE1444 benefits End-user benefits This feature does not affect the end-user experience.2 LTE1444: FBBC Flexi Capacity Extension Sub- Module 7. 7.6 LTE1440 sales information Table 183 Sales Information BSW/ASW License control in network License control attributes element BSW .2. BTS equipped with two FBBC sub-modules provides up to twelve optical RP3-01 6 Gbit/s connections towards RF units.0 - DN09185955 Issue: 01J © 2016 Nokia 305 .2. It increases both baseband capacity and RF connectivity of Flexi Multiradio 10 BTS System Module. 7. Table 184 Software requirements System release Flexi Multiradio BTS Flexi Multiradio 10 OMS BTS RL60 .1. • Expands RF connectivity by adding one optical RP3-01 6 Gbit/s link in LBTS6. Feature Descriptions and Instructions Descriptions of BTS site solution features 7.2. LTE RL60. • Expands RF connectivity by adding the remaining three RP3-01 6 Gbit/s links in the future LTE SW release.1. • Provides the same baseband capacity as FBBA.1. 1. Descriptions of BTS site solution features LTE RL60.2. NetAct8 EP1 . One FBBC provides an additional hardware baseband capacity for up to three 20 MHz LTE cells with 2x2 MIMO enabling 450 Mbps downlink and 150Mbps uplink data speeds.3 LTE1444 functional description FBBC is an optional. high capacity extension sub-module for Flexi Multiradio 10 BTS System Module. FBBC operates at temperature range -35°C-+55°C (-31°F-+131°F). Mixed configurations with FBBA are possible. Figure 23 Isometric view of FBBC DCIN RF1 RF2 BBEXT RF3 SRIO/RF4 Figure 24 FBBC LEDs CLASS1 LASERPRODUCT STATUS RF1 RF2 RF3 SRIO/RF4 One Flexi Multiradio 10 BTS System Module can host up to two FBBC units. Interfaces FBBC provides the following external interfaces: • one -48 VDC input • three optical OBSAI RP3-01 6 Gbit/s interfaces towards RF units • one dual mode combo port which can be configured either as SRIO or as RP3-01 interface • one baseband extension interface towards System Module (QSFP) 306 © 2016 Nokia DN09185955 Issue: 01J . - Hardware requirements This feature requires LTE947: FSMF Flexi Multiradio 10 System Module. FBBC is 1U high and it is rated at IP65. Feature Descriptions and Instructions UE NetAct MME SAE GW . 7. Figure 23: Isometric view of FBBC presents FBBC. 2.1. 7. Parameters There are no parameters related to this feature. For more information. to connect additional Flexi Multiradio 10 BTS System Module in the future LTE SW release. for example.5 LTE1444: FBBC Flexi Capacity Extension Sub-Module management data For information on alarm. see Cabling Flexi Multiradio 10 Base Station. Alarms There are no alarms related to this feature.2. counter. 7.1. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature.1. 7. see Reference documentation.2.4 LTE1444 system impact Interdependencies between features This feature is related to: • LTE1508: Multiradio System Module full LTE configurations • LTE1644: Multiradio System Module extended LTE configurations with FBBC Impact on interfaces This feature provides additional RP3-01 and SRIO interfaces for Flexi Multiradio 10 BTS. Feature Descriptions and Instructions Descriptions of BTS site solution features The SRIO/RF4 combo port can be configured to work as fourth RP3-01 interface or as SRIO interface for external baseband extension. LTE RL60. Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity This feature provides an additional hardware baseband capacity for up to three 20 MHz LTE cells with 2x2 MIMO and other configurations such as 2TX/4RX and 4TX/4RX. and parameter documents. key performance indicator.6 LTE1444 sales information Table 185 Sales information BSW/ASW License control in network License control attributes element BSW . - DN09185955 Issue: 01J © 2016 Nokia 307 . 7.3.1 LTE1508 Benefits Operator benefits Fully extended System capacity Flexi Multiradio System Module configurations (System Module FSMF with two optional capacity extension sub-modules.1 Description of Multiradio System Module full LTE configurations Introduction to the feature This section describes fully extended LTE configurations with Flexi Multiradio System Module FSMF with two optional capacity extension sub-modules (two FBBCs or FBBA and FBBC).3. - Hardware requirements This feature requires the following HW: • LTE947: FSMF Flexi Multiradio 10 System Module • Two Baseband Sub-Modules: – 2 x LTE1444: FBBC Flexi Baseband Sub-Module or – 1 x LTE1444: FBBC Flexi Baseband Sub-Module plus 1 x LTE1137: FBBA Flexi Baseband Sub-Module • If 6 Gbps optical links are to be used. 7. it requires additionally: – 6 Gbps-capable RF Modules/RRHs – 6 Gbps SFPs 308 © 2016 Nokia DN09185955 Issue: 01J . LBTS6.3. Feature Descriptions and Instructions 7.0 - UE NetAct MME SAE GW . two FBBCs or FBBA and FBBC) can support bigger cell and sector configurations and downlink and uplink performance enhancement features like LTE568: DL adaptive closed loop MIMO (4x2) and LTE72: 4-way RX diversity. Table 186 Software Requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 .2 LTE1508 Requirements Software requirements Table 186: Software Requirements lists the software required for this feature.3 LTE1508: Multiradio System Module Full LTE Configurations 7. Descriptions of BTS site solution features LTE RL60. NetAct8 EP1 .1.1. Impact on network and network element management tools This feature has no impact on network management or network element management tools.3.3.3 LTE1508 Functional description FSMF + two FBBC (or FBBA + FBBC) basic supported configurations include: • max 9 cells at 15/20 MHz Bandwidth (BW) 2TX 2RX • max 18 cells at 5/10 MHz BW 2TX 2RX • (max 3 cells at 15/20 MHz BW and max 6 cells at 5/10 MHz BW) OR (max 6 cells at 15/20 MHz BW and max 6 cells at 5/10 MHz BW) 2TX2RX • max 3 cells at 15/20 MHz BW 4TX4RX AND (max 6 cells at 5/10 MHz BW OR max 3 cells 15/20 MHz BW 2TX2RX) • max 6 cells at 5/10 MHz BW 4TX4RX AND (max 6 cells at 5/10 MHz BW OR max 3 cells 15/20 MHz BW 2TX2RX) Table 187: Number of extra new RF units shows the number of extra new RF units that can be connected with the second FBBC (when one link is available from FSMF or the first FBBA/C. 7.1. LTE RL60. Impact on system performance and capacity DN09185955 Issue: 01J © 2016 Nokia 309 . RRHs and detailed configurations are listed in Flexi Multiradio and Multiradio 10 BTS LTE Supported Configurations. and one link from the second FBBC). Table 187 Number of extra new RF units Configuration RFM 3TX RRH 2TX RRH 4TX RFM 6TX 3 x 15/20 MHz 2 3c n/a 1 2TX 2RX 6 x 5/10 MHz n/a 6c n/a 2 2TX 2RX 3 x 5/10 MHz n/a n/a 3c 2 4TX 4RX Notes: c - RRHs chained with 2 links/chain One additional RF band for second FBBC. Feature Descriptions and Instructions Descriptions of BTS site solution features 7.4 LTE1508 System impact Interdependencies between features The LTE977: RF Chainning feature need to be activated for using chained Radio Units. Impact on interfaces This feature has no impact on interfaces.1. or second FBBC adds cells to existing RF bands Max six 6 Gbps links for all RF units with second FBBC or four links by FSMF + two links with two FBBCs For six RRHs at 10 MHz 2TX 2RX two 6 Gbps links chained Supported RF Modules. 7.4. Key performance indicators There are no key performance indicators related to this feature. two FBBCs or FBBA and FBBC) can support bigger cell and sector configurations and downlink and uplink performance enhancement features like LTE568: DL adaptive closed loop MIMO (4x2) and LTE72: 4-way RX diversity.1.3.1. Descriptions of BTS site solution features LTE RL60. Measurements and counters There are no measurements or counters related to this feature.6 LTE1508 Sales information Table 188 Sales Information BSW/ASW License control in network License control attributes element BSW . Parameters There are no parameters related to this feature.1.5 LTE1508: Multiradio System Module full LTE configurations management data Alarms There are no alarms related to this feature.4 LTE1644: Multiradio System Module Extended LTE Configurations with FBBC 7.3. Feature Descriptions and Instructions Fully extended System capacity Flexi Multiradio System Module configurations (System Module FSMF with two optional capacity extension sub-modules.4. 310 © 2016 Nokia DN09185955 Issue: 01J .1 LTE1644 Benefits Operator benefits LTE1644: Multiradio System Module extended LTE configurations with FBBC feature (comprising the FSMF System Module with one optional capacity extension sub-module FBBC) allows bigger cell and sector configurations support and downlink and uplink performance enhancement features like LTE568: DL adaptive closed loop MIMO (4x2) and LTE72: 4-way RX diversity. - 7.1 Description of Multiradio System Module extended LTE configurations with FBBC Introduction to the feature This feature describes the extended LTE configurations with Flexi Multiradio System Module FSMF with one optional capacity extension sub-module FBBC. 7. 7. LTE RL60.1. one RF band configurations with 15 or 20 MHz cell bandwidth with 4TX MIMO and/or 4 RX diversity – LTE980: IRC for 4 RX paths is needed for uplink performance improvement. Support for all four ports is planned in future releases. 7. - Hardware requirements This feature requires the following HW: • LTE947: FSMF Flexi Multiradio 10 System Module • One Baseband Sub-Module: LTE1444: FBBC Flexi Baseband Sub-Module or LTE1137: FBBA Flexi Baseband Sub-Module • If 6 Gbps optical links are to be used. Table 189 Software Requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 .0 - UE NetAct MME SAE GW .4. it requires additionally: – 6 Gbps-capable RF Modules/RRHs – 6 Gbps SFPs 7.3 LTE1644 Functional description The following LTE FDD cell configurations are supported with one Flexi Multiradio System Module FSMF with one optional capacity extension sub-module FBBC: • Five RP3 optical ports in use (4 in FSMF + 1 in FBBC) • Maximum 6-cell configurations with maximum 20 MHz cell bandwidth with 2TX MIMO and 2RX diversity – 6-cell/6-sector configuration with one RF band – Two 3-sector BTS configurations with two different RF bands (dual band LTE configuration) – Triple band BTS configurations with six cells in two sectors • maximum 3-cell.1. LBTS6. Feature Descriptions and Instructions Descriptions of BTS site solution features FBBC provides the same baseband capacity as FBBA but FBBC HW has four 6 Gbps optical RP3 OBSAI links to RF units. – LTE72: 4-way RX diversity is needed for uplink performance improvement • maximum 12-cell configuration with 10 MHz cell bandwidth with 2TX MIMO and 2RX diversity DN09185955 Issue: 01J © 2016 Nokia 311 . RL60 supports one RP3 port in FBBC. NetAct8 EP1 .4.2 LTE1644 Requirements Software requirements Table 189: Software Requirements lists the software required for this feature. Feature Descriptions and Instructions – two 6-sector/cell BTS configurations with two different RF bands (dual band) LTE configuration – up to 12 one-cell RRH in three chains.5 LTE1644: Multiradio System Module extended LTE configurations with FBBC management data Alarms There are no alarms related to this feature. 7. up to three RRHs per chain. Impact on network and network element management tools This feature has no impact on network management or network element management tools. single. 7.4. RRHs and detailed configurations are listed in Flexi Multiradio and Multiradio 10 BTS LTE Supported Configurations. Key performance indicators There are no key performance indicators related to this feature.1. Impact on interfaces This feature has no impact on interfaces. Measurements and counters There are no measurements or counters related to this feature. and triple band configurations are supported Supported RF Modules. Descriptions of BTS site solution features LTE RL60. dual.4.4 LTE1644 System impact Interdependencies between features Additional features are needed for increased performance: • LTE980: IRC for 4 RX paths • LTE72: 4-way RX diversity • LTE977: RF chaining g Note: The LTE977: RF chaining feature needs to be activated while using chained RF Units. Impact on system performance and capacity FBBC provides the same baseband capacity as FBBA but FBBC HW has four 6 Gbps optical RP3 OBSAI links to RF units.1. Parameters Table 190 Existing parameters related to LTE1644 Full name Abbreviated name Managed Parent structure object Radio module reference id rModId ANTL - Antenna line configuration antlId ANTL - identifier 312 © 2016 Nokia DN09185955 Issue: 01J . 5.1.1 Description of LTE1665: FXFB Flexi 3-sector RF Module 1900 Introduction to the feature This feature introduces Flexi Multiradio RF Module FXFB for 1900 MHz band 2.5..1.2 optical cables • TX div and MIMO 2TX can be build using two 3-sector RF Modules DN09185955 Issue: 01J © 2016 Nokia 313 .1 LTE1665 benefits End-user benefits This feature does not affect the end-user experience.6 LTE1644 Sales information Table 191 Sales Information BSW/ASW License control in network License control attributes element BSW . see reference documentation.4. +55°C • can be used as feederless site as well with one DC and 1. HSPA+ and WCDMA and GSM/EDGE • 3 sector RF in one outdoor IP65 box • widest ambient temperature range -35°C.5 LTE1665: FXFB Flexi 3-sector RF Module 1900 7. LTE RL60. Operator benefits FXFB Flexi 3-sector 3x60 W RF Module main benefits: • provides the most cost and size and weight optimized 3-sector BTS site • serves industry leading RF integration level • SW configurable radio: the same RF Module for LTE.. 7... - 7.) Full name Abbreviated name Managed Parent structure object Local cell resource identifier lCellId LCELL - Antenna line identifier antlId MHA - Scanned antenna interface scannedAntennaInterfa MHA - ce Antenna line identifier list antlIdList RET - Scanned antenna interface scannedAntennaInterfa RET - ce Radio module reference id Radio module reference RMOD - id For parameter descriptions. 7. Feature Descriptions and Instructions Descriptions of BTS site solution features Table 190 Existing parameters related to LTE1644 (Cont. Basic LTE configurations: • 1. 20. .1. 7. Full support for Multioperator sites with 60 W output power and 20 MHz RF bandwidth.5.2 LTE1665 requirements Software requirements Table 192: Software Requirements lists the software required for this feature. 7. Table 192 Software Requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 LBTS6. Impact on interfaces This feature has no impact on interfaces.1.0 LBTS6. 1+1 or 1+1+1 LTE cells @ max 20 MHz LTE bandwith and 1TX/2RX • 8. WCDMA and GSM/EDGE configurations are described in GSM/EDGE and WCDMA release documents. Impact on system performance and capacity New configurations are available.5.3 LTE1665 functional description New high power 3-sector Flexi Multiradio RF Module introduces industry leading RF integration level and smallest power consumption combined with flexible GSM-WCDMA- LTE site evolution. 60 W mode per sector (by SW licenses) • 1 sector max 60 + 60 W 2TX/2RX MIMO • HW prepared for 1 sector max 60 + 60 W 2TX/4RX MIMO • separate RET connector FXFB can be used in feederless (DC up to 200 m) BTS sites. Impact on network and network element management tools This feature has no impact on network management or network element management tools. 40. Descriptions of BTS site solution features LTE RL60.4 LTE1665 system impact Interdependencies between features There are no interdependencies between this and any other feature. 314 © 2016 Nokia DN09185955 Issue: 01J .5.0 - UE NetAct MME SAE GW 3GPP R8 UE capabilities . - Hardware requirements This feature requires no new or additional hardware.1. Feature Descriptions and Instructions • low windload • easy installation 7. 1 Description of LTE1695: FXCB Flexi RF Module 850 Introduction to the feature 7.6. Operator benefits FXCB Flexi 3-sector 3x80 W RF Module main benefits: • provides the most cost and size and weight optimized 3-sector BTS site • serves industry leading RF integration level • SW configurable radio: the same RF Module for LTE. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. LTE RL60..6 LTE1695: FXCB Flexi RF Module 850 7.1. 7..6 LTE1665 sales information Table 193 Sales Information BSW/ASW License control in network License control attributes element BSW .6.1. - 7..1.2 optical cables • TX div and MIMO 2TX can be build using two 3-sector RF Modules • low windload • easy installation 7.1.5. HSPA+ and WCDMA and GSM/EDGE • 3 sector RF in one outdoor IP65 box • widest ambient temperature range -35°C.2 LTE1695 requirements Software requirements DN09185955 Issue: 01J © 2016 Nokia 315 . Feature Descriptions and Instructions Descriptions of BTS site solution features 7.6.5. +55°C • can be used as feederless site as well with one DC and 1.. Parameters There are no parameters related to this feature.1 LTE1695 benefits End-user benefits This feature does not affect the end-user experience.5 LTE1665: FXFB Flexi 3-sector RF Module 1900 management data Alarms There are no alarms related to this feature. Basic LTE configurations: • 1.6.1. 7. 7. 60. 7. . 40. Measurements and counters 316 © 2016 Nokia DN09185955 Issue: 01J . 20. Impact on system performance and capacity New configurations are available. - Hardware requirements This feature requires no new or additional hardware.0 - UE NetAct MME SAE GW 3GPP R8 UE capabilities .0 LBTS6. 1+1 or 1+1+1 LTE cells @ max 20 MHz LTE bandwith and 1TX/2RX (LTE BW support is limited by UE capability to max 10 MHz at Band 5 in 3GPP ) • 8.4 LTE1695 system impact Interdependencies between features There are no interdependencies between this and any other feature. 80 W mode per sector (by SW licenses) • 1 sector max 80 + 80 W 2TX/2RX MIMO • HW prepared for 1 sector max 80 + 80 W 2TX/4RX MIMO FXCB can be used in feederless (DC up to 200 m) BTS sites. Table 194 Software Requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 LBTS6. Impact on network and network element management tools This feature has no impact on network management or network element management tools.1. Feature Descriptions and Instructions Table 194: Software Requirements lists the software required for this feature.6.1. WCDMA and GSM/EDGE configurations are described in GSM/EDGE and WCDMA release documents. Descriptions of BTS site solution features LTE RL60.5 LTE1695: FXCB Flexi RF Module 850 management data Alarms There are no alarms related to this feature.6.3 LTE1695 functional description New high power 3-sector Flexi Multiradio RF Module introduces industry leading RF integration level and smallest power consumption combined with flexible GSM-WCDMA- LTE site evolution. Full support for Multioperator sites with 80 W output power and 25 MHz RF bandwidth. Impact on interfaces This feature has no impact on interfaces. LTE RL60.1.1 LTE1895 benefits Operator benefits This feature benefits the operator as follows: • Easy and future-proof BTS site evolution from WCDMA or GSM to multi band multi- RAT by using shared Flexi Multiradio RF modules.6.6 LTE1695 sales information Table 195 Sales Information BSW/ASW License control in network License control attributes element BSW . Key performance indicators There are no key performance indicators related to this feature.7. LBTS6. - 7. Table 196 Software Requirements System release Flexi Multiradio Flexi Multiradio 10 OMS BTS BTS RL60 .1 Description of LTE1895: LTE-GSM and LTE-WCDMA RF sharing for dual band configurations Introduction to the feature This feature extends the existing functionality for LTE-WCDMA and LTE-GSM RF sharing to scenarios with LTE dual band configurations. • This feature helps the operator to allocate and share BTS RF resources between WCDMA/GSM and LTE in a flexible way. 7.1.7.7 LTE1895: LTE-GSM and LTE-WCDMA RF sharing for dual band configurations 7. 7.1. 7. Feature Descriptions and Instructions Descriptions of BTS site solution features There are no measurements or counters related to this feature. Parameters There are no parameters related to this feature.0 - DN09185955 Issue: 01J © 2016 Nokia 317 . • Significant OPEX savings by shared usage of RF HW. • No additional external combiners are required and multiple RATs can share the same feeders and antennas in the same band.2 LTE1895 requirements Software requirements Table 186: Software Requirements lists the software required for this feature.7. For dual band RF sharing with WCDMA WN8. 318 © 2016 Nokia DN09185955 Issue: 01J . Impact on network and network element management tools There is no impact on network and network element management tools. • Allows usage of RF-sharing with 4Rx diversity (respective feature is needed. the following features are needed: • For LTE carrier aggregation: – LTE1089: Downlink carrier aggregation - 20 MHz – LTE1332: Downlink carrier aggregation - 40 MHz • For 4-way RX diversity: LTE72: 4-way RX diversity. The following dual band configurations are possible: – Band A: shared LTE-GSM.3 LTE1895 functional description This feature: • Adds the support of LTE dual band configurations for RF sharing.0.1. shared band in 2Rx mode 7. Band B: dedicated LTE – Band A: shared LTE-WCDMA.1 1.4 LTE1895 system impact Interdependencies between features At least one of the following features must be enabled: • LTE435: RF sharing WCDMA-LTE • LTE447: SW support for RF sharing GSM-LTE For additional functionality. 7.7. Band B: dedicated LTE • Allows configuration of LTE carrier aggregation on top of the dual band configurations.0 is needed. Descriptions of BTS site solution features LTE RL60. see LTE1895 system impact) in the following configuration: – Dedicated LTE band in 4Rx mode.1. see LTE1895 system impact).) UE NetAct MME SAE GW . Impact on system performance and capacity There is no impact on system performance and capacity. (respective features are needed.1 is needed. Impact on interfaces There is no impact on interfaces. .7. Feature Descriptions and Instructions Table 196 Software Requirements (Cont.0 3. - Hardware requirements This feature requires no new or additional hardware. . For dual band RF sharing with GSM EX5. 6 LTE1895 sales information Table 197 Sales Information BSW/ASW License control in network License control attributes element BSW . Measurements and counters There are no measurements or counters related to this feature. Parameters There are no parameters related to this feature.1. - 7. 7. Operator benefits This feature provides the possibility of using FSMF on the WCDMA side in LTE-WCDMA RF sharing. Requirements Hardware and software requirements DN09185955 Issue: 01J © 2016 Nokia 319 .5 LTE1895: LTE-GSM and LTE-WCDMA RF sharing for dual band configurations management data Alarms There are no alarms related to this feature.1 Description of LTE1915: RF sharing LTE-WCDMA with FSMF for WCDMA Introduction to the feature This feature allows the configuration of Flexi Multiradio 10 Base Station System Module (FSMF) on WCDMA in LTE-WCDMA RF sharing. Feature Descriptions and Instructions Descriptions of BTS site solution features 7. Benefits End-user benefits This feature does not affect the end-user experience. Key performance indicators There are no key performance indicators related to this feature.7. LTE RL60.7.1.8 LTE1915: RF sharing LTE-WCDMA with FSMF for WCDMA 7.8. . Descriptions of BTS site solution features LTE RL60. Management data Alarms There are no alarms related to this feature. Feature Descriptions and Instructions Table 198 Hardware and software requirements System release Flexi Multiradio Flexi Multiradio Flexi Zone Micro OMS BTS 10 BTS RL60 not supported LBTS6. 320 © 2016 Nokia DN09185955 Issue: 01J . . - . - Additional hardware requirements This feature requires the following hardware on the LTE side: • LTE947: FSMF Flexi Multiradio 10 System Module Functional description Functional overview This feature extends the existing LTE-WCDMA RF sharing functionality to configurations with Flexi Multiradio 10 Base Station System Module (FSMF) on the WCDMA side as well. The following System Module configurations are supported in LTE-WCDMA RF sharing: • LTE: FSME or FSMF with WCDMA: FSMC/D/E • LTE: FSMF with WCDMA: FSMF (introduced with this feature) System impact Interdependencies between features RAN2126/LTE435: RF Sharing WCDMA - LTE is a prerequisite feature. Measurements and counters There are no measurements or counters related to this feature. Impact on network management tools This feature has no impact on network management tools. . .1 not supported - UE NetAct MME SAE GW . Impact on interfaces This feature has no impact on interfaces.0 not supported - RU50EP1 not supported WN9. Impact on system performance and capacity This feature has no impact on system performance or capacity. Table 200 Software Requirements System release Flexi Flexi Flexi OMS Multiradio BTS Multiradio BTS Multiradio 10 EDGE BTS RL60 . Sales information Table 199 Sales information BSW/ASW License control in network Activated by default element BSW .1.1 LTE1952 benefits Operator benefits This feature allows RF sharing in 1900MHz band. Feature Descriptions and Instructions Descriptions of BTS site solution features Key performance indicators There are no key performance indicators related to this feature.9 LTE1952: LTE GSM/WCDMA RF-sharing for Band 2 (1900MHz) 7.0 - RU40 . LTE RL60.9. Parameters There are no parameters related to this feature. WN8.0 - RG30 EX5. 7.1 1. Yes 7.9. LBTS6.0.0 - UE NetAct MME SAE GW .1 Description of LTE1952: LTE GSM/WCDMA RF-sharing for Band 2 (1900MHz) Introduction to the feature This feature extends the LTE-WCDMA and LTE-GSM RF sharing capabilities to band 2.0 4. . - Hardware requirements DN09185955 Issue: 01J © 2016 Nokia 321 .2 LTE1952 requirements Software requirements Table 186: Software Requirements lists the software required for this feature. 1900MHz. . 7. .9.1. extending the existing functionality of WCDMA-LTE and GSM-LTE RF sharing. Impact on system performance and capacity There is no impact on system performance and capacity.9. 7. Key performance indicators There are no key performance indicators related to this feature.9.4 LTE1952 system impact Interdependencies between features At least one of the following features must be enabled: • LTE435: RF sharing WCDMA-LTE • LTE447: SW support for RF sharing GSM-LTE Impact on interfaces There is no impact on interfaces. Feature Descriptions and Instructions This feature requires 1900 RF Modules.9.3 LTE1952 functional description This feature enables RF sharing in 1900MHz LTE band.1.1. 7.9. Measurements and counters There are no measurements or counters related to this feature.1.5 LTE1952: LTE GSM/WCDMA RF-sharing for Band 2 (1900MHz) management data Alarms There are no alarms related to this feature. The details on configurations are provided in Flexi Multiradio BTS RF Sharing Released Configurations. Impact on network and network element management tools There is no impact on network and network element management tools. Parameters There are no parameters related to this feature. Descriptions of BTS site solution features LTE RL60. 7. - 322 © 2016 Nokia DN09185955 Issue: 01J .1.6 LTE1952 sales information Table 201 Sales Information BSW/ASW License control in network License control attributes element BSW . for details see Flexi Multiradio BTS RF Sharing Released Configurations. 7.
Copyright © 2024 DOKUMEN.SITE Inc.