lte15a_features_rrm

LTE Radio Access, Rel.
LTE
18A, Operating
Documentation, Issue 01
LTE15A Radio Resource

Management and Telecom
Features
DN179848337
Issue 01
Approval Date 2017-11-28
LTE15A Radio Resource Management and Telecom Features
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 © 2018 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 © 2018 Nokia. Nokia confidential. DN179848337 Issue: 01

Table of Contents
This document has 408 pages
1 LTE64: Service based handover thresholds ............................... 18

1.1 Description of LTE64: Service-based Handover Thresholds....... 18
1.2 LTE64 reference data...................................................................20
1.3 Activating and configuring LTE64: Service-based Handover
Thresholds................................................................................... 24
1.4 Deactivating LTE64: Service-based Handover Thresholds..........28
2 LTE569: Downlink Adaptive Closed Loop SU-MIMO 4x4............ 29

2.1 Description of LTE569: Downlink Adaptive Closed Loop SU-MIMO
4x4 - TM 4.................................................................................... 29
2.2 LTE569 reference data.................................................................32
2.3 Activating and configuring LTE569: Downlink Adaptive Closed
Loop SU-MIMO 4x4 - TM 4.......................................................... 35
2.4 Deactivating LTE569: Downlink Adaptive Closed Loop SU-MIMO
4x4 - TM 4.................................................................................... 36
3 LTE738: SRVCC to 1xRTT/CDMA............................................... 38

3.1 Description of LTE738: SRVCC to 1xRTT/CDMA........................ 38
3.3 Activating and configuring LTE738: SRVCC to 1xRTT/CDMA.....49
3.4 Deactivating LTE738: SRVCC to 1xRTT/CDMA.......................... 53
4 LTE825: Uplink Outer Region Scheduliing................................... 54

4.1 Description of LTE825: Uplink Outer Region Scheduling.............54
4.3 Activating and configuring LTE825: Uplink Outer Region
Scheduling................................................................................... 60
4.4 Deactivating LTE825: Uplink Outer Region Scheduling .............. 65
5 LTE951: Enhanced Cell ID Location Service............................... 67

5.1 Description of LTE951: Enhanced Cell ID Location Service........ 67
5.3 Activating and configuring LTE951: Enhanced Cell ID Location
Service......................................................................................... 74
5.4 Deactivating LTE951: Enhanced Cell ID Location Service.......... 80
6 LTE1117: LTE MBMS................................................................... 82

6.1 Description of LTE1117: LTE MBMS............................................ 82
6.2 LTE1117 reference data............................................................... 88
6.3 Activating and configuring LTE1117: LTE MBMS......................... 94
6.4 Configuration details of LTE1117..................................................98
6.5 Deactivating LTE1117: LTE MBMS.............................................102
7 LTE1196: RAN Information Management for WCDMA.............. 104
DN179848337 Issue: 01 © 2018 Nokia. Nokia confidential. 3

7.1 Description of LTE1196: RAN Information Management for

WCDMA..................................................................................... 104
7.2 LTE1196 reference data............................................................. 108
7.3 Activating and configuring LTE1196: RAN Information
Management for WCDMA ......................................................... 112
7.4 Deactivating LTE1196: RAN Information Management for WCDMA
....................................................................................................118
8 LTE1321: eRAB Modification – GBR..........................................119

8.1 LTE1321 reference data.............................................................122
8.2 VoLTE/ViLTE call drops when LTE1321 is enabled in the network..
124
9 LTE1357: LTE-UTRAN Load Balancing..................................... 126

9.1 LTE1357: LTE-UTRAN Load Balancing..................................... 126
9.3 Activating and configuring LTE1357: LTE-UTRAN Load Balancing.
132
9.4 Deactivating LTE1357: LTE-UTRAN Load Balancing................ 137
10 LTE1635: SIB8 AC barring for 1xRTT........................................ 138

10.1 Description of LTE1635: SIB 8 AC Barring for 1xRTT................138
10.3 Activating and configuring LTE1635: SIB 8 AC Barring for 1xRTT..
141
10.4 Deactivating LTE1635: SIB 8 AC Barring for 1xRTT..................144
11 LTE1679: DRX with Parallel UE Measurement Gaps................ 146

11.1 Description of LTE1679: DRX with Parallel UE Measurement
Gaps...........................................................................................146
11.3 Activating and configuring LTE1679: DRX with Parallel UE
Measurement Gaps....................................................................150
11.4 Deactivating LTE1679: DRX with Parallel UE Measurement Gaps..
151
12 LTE1784: Carrier Aggregation for Supercell up to 2CC............. 153

12.1 Description of LTE1784: Carrier Aggregation for Supercell up to
2CC............................................................................................ 153
12.3 Activating and configuring LTE1784: Carrier Aggregation for
Supercell Up to 2CC.................................................................. 156
12.4 Deactivating LTE1784: Carrier Aggregation for Supercell Up to
2CC............................................................................................ 158
13 LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall.....

160
13.1 Description of LTE1787: TM9 with 8TX MU-MIMO and Up to 2
Layers Overall............................................................................ 160

13.3 Activating and configuring LTE1787: TM9 with 8TX MU-MIMO and
Up to 2 Layers Overall............................................................... 164
13.4 Deactivating LTE1787: TM9 with 8TX MU-MIMO and Up to 2
Layers Overall............................................................................ 167
14 LTE1788: Automatic Access Class Barring................................169

14.1 Description of LTE1788: Automatic Access Class Barring.........169
14.3 Activating and configuring LTE1788: Automatic Access Class
Barring........................................................................................177
14.4 Deactivating LTE1788: Automatic Access Class Barring........... 185
15 LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz........... 187

15.2 Activating and configuring LTE1804: Downlink Carrier Aggregation
3 CC - 60 MHz........................................................................... 198
15.3 Deactivating LTE1804: Downlink Carrier Aggregation 3 CC - 60
MHz............................................................................................ 201
16 LTE1836: TDD Downlink Carrier Aggregation - 60 MHz............ 203

16.1 Description of LTE1836: TDD Downlink Carrier Aggregation - 60
MHz............................................................................................ 203
16.3 Activating and configuring LTE1836: TDD Downlink Carrier
Aggregation - 60 MHz................................................................ 210
16.4 Deactivating LTE1836: TDD Downlink Carrier Aggregation - 60
MHz............................................................................................ 212
17 LTE1838: TDD Downlink Inter-band Carrier Aggregation - 40 MHz

................................................................................................... 213
17.1 Description of LTE1838: TDD Downlink Inter-band Carrier
Aggregation - 40 MHz................................................................ 213
17.3 Activating and configuring LTE1838: TDD Downlink Inter-band
Carrier Aggregation - 40 MHz.................................................... 218
17.4 Deactivating LTE1838: TDD Downlink Inter-band Carrier
Aggregation - 40 MHz................................................................ 219
18 LTE1850: TDD Intra-band Dual-carrier Operation within a Flexi

Zone Micro BTS......................................................................... 221
18.1 Description of LTE1850: TDD Intra-band Dual-carrier Operation
within a Flexi Zone Micro BTS................................................... 221
18.3 Activating and configuring LTE1850: TDD Intra-band Dual-carrier
Operation within a Flexi Zone Micro BTS...................................226
18.4 Deactivating LTE1850: TDD Intra-band Dual-carrier Operation
within a Flexi Zone Micro BTS................................................... 227
19 LTE1896: TDD Intra-band Dual-carrier Downlink Aggregation for

Flexi Zone Micro.........................................................................229
19.1 Description of LTE1896: TDD Intra-band Dual-carrier Downlink
Aggregation for Flexi Zone Micro............................................... 229


19.3 Activating and configuring LTE1896: TDD Intra-band Dual-carrier
Downlink Aggregation for Flexi Zone Micro............................... 233
19.4 Deactivating LTE1896: TDD Intra-band Dual-carrier Downlink
Aggregation for Flexi Zone Micro............................................... 237
20 LTE1905: PLMN ID and SPID Selected Mobility Profiles...........238

20.2 Activating and configuring LTE1905: PLMN ID and SPID Selected
Mobility Profiles.......................................................................... 244
20.3 Deactivating LTE1905: PLMN ID and SPID Selected Mobility
Profiles with the actSelMobPrf parameter..................................247
20.4 Deactivating LTE1905: PLMN ID and SPID Selected Mobility
Profiles with the moProfileSelect parameter.............................. 248
21 LTE1925: Cause value for CSFB to GERAN without DTM support .

249
21.1 Description of LTE1925: Cause Value for CSFB to GERAN without
DTM Support..............................................................................249
21.3 Activating and configuring LTE1925: Cause Value for CSFB to
GERAN without DTM Support....................................................252
21.4 Deactivating LTE1925: Cause Value for CSFB to GERAN without
DTM Support..............................................................................253
22 LTE1929: UL Semi-persistent scheduling.................................. 254

22.1 Description of LTE1929: UL Semi-persistent Scheduling.......... 254
22.3 Activating and configuring LTE1929: UL Semi-persistent
Scheduling................................................................................. 262
22.4 Deactivating LTE1929: UL Semi-persistent Scheduling.............264
23 LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List

................................................................................................... 266
23.1 Description of LTE1942: Dedicated VoLTE Inter-frequency Target
Frequency List............................................................................266
23.3 Activating and configuring LTE1942: Dedicated VoLTE Inter-
Frequency Target Frequency List...............................................271
23.4 Deactivating LTE1942: Dedicated VoLTE Inter-Frequency Target
Frequency List............................................................................272
24 LTE1944: Dynamic Handover Blacklisting ................................ 274

24.1 Description of LTE1944: Dynamic Handover Blacklisting.......... 274
24.3 Activating and configuring LTE1944: Dynamic Handover
Blacklisting................................................................................. 278
24.4 Deactivating LTE1944: Dynamic Handover Blacklisting.............279
25 LTE2006: Flexible SCell Selection............................................. 281

25.1 LTE2006 benefits....................................................................... 281

25.2 LTE2006 functional description.................................................. 281

25.3 LTE2006 system impact............................................................. 282
25.5 Activating and configuring LTE2006...........................................285
25.6 Deactivating LTE2006................................................................ 288
26 LTE2023: User plane overload handling ................................... 290

26.1 Description of LTE2023: User Plane Overload Handling .......... 290
26.3 Activating and configuring LTE2023: User Plane Overload
Handling..................................................................................... 297
26.4 Deactivating LTE2023: User Plane Overload Handling............. 298
27 LTE2051: Measurement based Idle Mode Load Balancing....... 300

27.1 Description of LTE2051: Measurement based Idle Mode Load
Balancing................................................................................... 300
27.3 Activating and configuring LTE2051: Measurement based Idle
Mode Load Balancing................................................................ 304
27.4 Deactivating LTE2051: Measurement based Idle Mode Load
Balancing................................................................................... 307
28 LTE2085: SIB Reception with Parallel Measurement Gaps....... 309

28.1 Description of LTE2085: SIB Reception with Parallel
28.3 Activating and configuring LTE2085: SIB Reception with Parallel
Measurement Gaps with the Twofold transmission of SIBs per SI
window parameter......................................................................315
Measurement Gaps with a selected feature ..............................316
28.5 Deactivating LTE2085: Reception with Parallel Measurement
Gaps...........................................................................................322
29 LTE2120: TDD SIB reception with parallel measurement gaps ......

324
29.3.1 Option one (two mandatory transmissions of SIB 2 to SIB 9): the
LTE494: Commercial Mobile Alert System (CMAS) and LTE843:
ETWS Broadcast features are disabled, and the Twofold
transmission of SIBs per SI
window (sib2xTransmit) activation flag is set to true......... 330
29.3.2 Option two (two mandatory transmissions of SIB 10 and 11, and
optionally from SIB 2 to SIB 9): the LTE494: Commercial Mobile
Alert System (CMAS) feature is disabled, the LTE843: ETWS
Broadcast feature is enabled, and the Twofold

window (sib2xTransmit) activation flag is set to true or false.

331
29.3.3 Option three (two mandatory transmissions of SIB 12, and
optionally from SIB 2 to SIB 9): the LTE494: Commercial Mobile
Alert System (CMAS) feature is enabled, the LTE843: ETWS
Broadcast feature is disabled, and the Twofold
window (sib2xTransmit) activation flag is set to true or false.
335
29.4 Deactivating LTE2120: SIB Reception with Parallel Measurement
Gaps...........................................................................................338
30 LTE2128: Uplink Intra eNodeB CoMP 8 RX with Softbit

Combination............................................................................... 339
30.1 Description of LTE2128: Uplink Intra eNodeB CoMP 8 RX with
Softbit Combination....................................................................339
30.3 Activating and configuring LTE2128: Uplink Intra eNodeB CoMP 8
RX with Softbit Combination...................................................... 344
30.4 Deactivating LTE2128: Uplink intra eNodeB CoMP 8 RX with
softbit combination..................................................................... 346
31 LTE2133: eICIC for HetNet eNode B Configurations................. 347

31.1 LTE2133: eICIC for HetNet eNode B Configurations................. 347
32 LTE2149: Supplemental Downlink Carrier................................. 352

32.1 Description of LTE2149: Supplemental Downlink Carrier.......... 352
32.3 Activating and configuring LTE2149: Supplemental Downlink
Carrier........................................................................................ 357
32.4 Deactivating LTE2149: Supplemental Downlink Carrier............ 361
33 LTE2168: Additional Carrier Aggregation Band Combinations - II...

363
33.2 Activating and configuring LTE2168: Additional Carrier
Aggregation Band Combinations - II.......................................... 365
33.3 Deactivating LTE2168: Additional Carrier Aggregation Band
Combinations - II........................................................................ 367
34 LTE2208: eICIC Enhancements - micro.....................................368

35 LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs

................................................................................................... 371
35.2 Activating and configuring LTE2305: Inter-eNodeB Carrier
Aggregation for 2 Macro eNodeBs.............................................376
35.3 Deactivating LTE2305: Inter-eNodeB Carrier Aggregation for 2
Macro eNodeBs......................................................................... 379

36 LTE2314: Configurable sequence of BCCH carriers within GERAN

frequency layer list for CSFB based on UE Context Release.... 381
36.1 Description of LTE2314: Configurable Sequence of BCCH
Carriers within GERAN Frequency Layer List for CSFB Based on
UE Context Release...................................................................381
36.3 Activating and configuring LTE2314: Configurable Sequence of
BCCH Carriers within GERAN Frequency Layer List for CSFB
Based on UE Context Release.................................................. 384
36.4 Deactivating LTE2314: Configurable Sequence of BCCH Carriers
within GERAN Frequency Layer List for CSFB Based on UE
Context Release ........................................................................387
37 LTE2324: Network-requested UE Radio Capabilities................ 389

37.1 Description of LTE2324: Network-requested UE Radio
Capabilities.................................................................................389
37.3 Activating and configuring LTE2324: Network-requested UE Radio
Capabilities.................................................................................393
37.4 Deactivating LTE2324: Network-requested UE Radio Capabilities..
394
38 LTE2388: VoLTE Call Steering Enhancement............................396

38.1 Description of LTE2388: VoLTE Call Steering Enhancement.....396
38.2 Activating and configuring LTE2388: VoLTE Call Steering
Enhancement............................................................................. 398
38.3 Deactivating LTE2388: VoLTE Call Steering Enhancement.......400
39 LTE2430: QCI1 Establishment Triggered Protection Timer....... 403

39.1 Description of LTE2430: QCI1 Establishment Triggered Protection
Timer.......................................................................................... 403
39.3 Activating and configuring LTE2430: QCI1 Establishment
Triggered Protection Timer.........................................................406
39.4 Deactivating LTE2430: QCI1 Establishment Triggered Protection
Timer.......................................................................................... 407

List of Figures
Figure 1 HO messages.....................................................................................38
Figure 2 The comparison of LTE786: Flexible UL Bandwidth and LTE825: UL
Outer Region Scheduling features .................................................... 55
Figure 3 MBMS architecture............................................................................. 83
Figure 4 Different synchronization scenarios....................................................85
Figure 5 MBMS definitions................................................................................86
Figure 6 RIM protocol structure between E-UTRAN and UTRAN.................. 105
Figure 7 Redirection procedure with SI.......................................................... 105
Figure 8 Complete signaling flow....................................................................121
Figure 9 LTE - UTRAN load balancing........................................................... 126
Figure 10 Examples of three-cell CA................................................................ 188
Figure 11 CA scenario 1................................................................................... 214
Figure 12 CA scenario 2................................................................................... 214
Figure 13 Two-cell configurations on the same frequency band...................... 222
Figure 14 Dual-carrier downlink aggregation as an extension of the LTE1850
feature.............................................................................................. 230
Figure 15 Example of frequency layers in the LTE1942 feature....................... 267
Figure 16 Example of frequency layers in the LTE1942 feature when LTE1127 is
active................................................................................................ 267
Figure 17 U-plane overload handling................................................................291
Figure 18 SIB reception with parallel measurement gaps................................ 310
Figure 19 Different types of SIBs...................................................................... 325
Figure 20 CoMP technique using 8 RX antennas.............................................340
Figure 21 Scenario 1........................................................................................ 347
Figure 22 Scenario 2........................................................................................ 348
Figure 23 Scenario 3........................................................................................ 348
Figure 24 A supplementary cell used as a secondary cell (SCell) in carrier
aggregation.......................................................................................353
Figure 25 Redirection of VoLTE call to other layers..........................................396

List of Tables
Table 1 New dedicated thresholds introduced with the LTE64: Service-based
Handover Thresholds feature............................................................. 18
Table 2 LTE64 hardware and software requirements......................................21
Table 3 New counters introduced by LTE64....................................................21
Table 4 New parameters introduced by LTE64............................................... 22
Table 5 Existing parameters related to LTE64................................................ 22
Table 6 LTE64 sales information..................................................................... 23
Table 7 Parameters used for activating and configuring LTE64: Service-based
Handover Thresholds......................................................................... 24
Table 8 Transmission submodes.....................................................................31
Table 9 LTE569 hardware and software requirements....................................33
Table 10 New counters introduced by LTE569..................................................33
Table 11 Existing counters related to LTE569................................................... 34
Table 12 New parameters introduced by LTE569............................................. 34
Table 13 Existing parameters related to LTE569.............................................. 34
Table 14 LTE569 sales information................................................................... 35
Table 15 Parameters used for activating and configuring LTE569: Downlink
Adaptive Closed Loop SU-MIMO 4x4 - TM 4..................................... 35
Table 17 New counters introduced by LTE738..................................................41
Table 19 Parameters modified by LTE738........................................................ 43
Table 22 Parameters used for activating and configuring LTE738: SRVCC to
1xRTT/CDMA..................................................................................... 49
Table 23 LTE825 summary of changes............................................................. 54
Table 25 Counters modified by LTE825............................................................ 57
Table 29 Parameters used for activating and configuring LTE825: Uplink Outer
Region Scheduling............................................................................. 60
Table 31 New counters introduced by LTE951 feature..................................... 71
Table 32 New parameters related to the LTE951 feature..................................72
Table 33 Existing parameters related to the LTE951 feature............................ 72
Table 34 The LTE951 feature sales information................................................74

Table 35 Parameters used for activating and configuring LTE951: Enhanced

Cell ID Location Service..................................................................... 74
Table 36 LTE1117 hardware and software requirements.................................. 88
Table 37 New BTS faults introduced by LTE1117............................................. 89
Table 38 New counters introduced by LTE1117................................................ 89
Table 39 New parameters introduced by LTE1117............................................90
Table 40 Existing parameters related to LTE1117 (for TDD)............................. 92
Table 41 Existing parameters related to LTE1117 (for FDD)............................. 93
Table 42 LTE1117 sales information..................................................................94
Table 43 Parameters used for activating and configuring the LTE1117: LTE
MBMS feature.....................................................................................95
Table 44 MBMS Data Rate table.......................................................................99
Table 45 MBMS Data Rate Table.................................................................... 100
Table 46 LTE1196 hardware and software requirements................................ 108
Table 47 Existing alarms related to LTE1196.................................................. 109
Table 48 New parameters introduced by LTE1196..........................................110
Table 49 LTE1196 sales information................................................................ 111
Table 50 Parameters used for activating and configuring LTE1196: RAN
Information Management for WCDMA..............................................112
Table 51 LTE519 and LTE1321 comparison....................................................119
Table 52 LTE1321 hardware and software requirements................................122
Table 53 New counters....................................................................................123
Table 54 Modified parameters introduced by LTE1321................................... 123
Table 55 LTE1321 sales information............................................................... 123
Table 57 New counters introduced by LTE1357..............................................129
Table 58 New parameters introduced by LTE1357......................................... 130
Table 59 Existing parameters related to LTE1357.......................................... 130
Table 61 Parameters used for activating and configuring LTE1357: LTE-UTRAN
Load Balancing.................................................................................132
Table 65 Parameters used for activating and configuring LTE1635: SIB 8 AC
Barring for 1xRTT............................................................................. 142
Table 70 Parameters used for activating and configuring LTE1679: DRX with
Parallel UE Measurement Gaps....................................................... 150


Table 78 Parameters used for activating and configuring LTE1787: TM9 with
8TX MU-MIMO and Up to 2 Layers Overall......................................164
Table 80 BTS faults......................................................................................... 172
Table 81 New counters....................................................................................173
Table 82 New Parameters...............................................................................173
Table 83 Modified parameters.........................................................................176
Table 84 Sales information..............................................................................177
Table 85 Parameters used for activating and configuring LTE1788: Automatic
Access Class Barring....................................................................... 178
Table 88 New key performance indicators introduced by LTE1804................ 193
Table 90 Parameters modified by LTE1804.................................................... 194
Table 93 Parameters used for activating and configuring the LTE1804:
Downlink Carrier Aggregation 3 CC - 60 MHz feature......................198
Table 94 LTE1836 summary of changes......................................................... 203
Table 96 Existing counters related to LTE1836............................................... 207
Table 101 Parameters used for activating and configuring the LTE1836: TDD
Downlink Carrier Aggregation - 60 MHz feature...............................210
Table 107 The minimum center carrier frequency spacing............................... 222


Table 114 Parameters used for activating and configuring LTE1896: TDD Intra-
band Dual-carrier Downlink Aggregation for Flexi Zone Micro......... 233
Table 119 Parameters used for activating and configuring LTE1905: PLMN ID
and SPID Selected Mobility Profiles................................................. 244
Table 128 Parameters used for activating and configuring LTE1929: UL Semi-
persistent Scheduling....................................................................... 262
Table 133 Parameters used for activating and configuring the LTE1942:
Dedicated VoLTE Inter-Frequency Target Frequency List................271
Table 138 Parameters used for activating and configuring LTE1944: Dynamic
Handover Blacklisting....................................................................... 278

Table 144 Mapping between U-plane overload triggers and the related counter-
measures..........................................................................................292
Table 146 New BTS faults introduced by LTE2023........................................... 295
Table 151 Parameters used for activating and configuring LTE2023: User Plane
Overload Handling............................................................................297
Table 157 Parameters used for activating and configuring LTE2051:
Measurement based Idle Mode Load Balancing feature.................. 305
Table 159 Counters modified by LTE2085........................................................ 312
Table 163 Parameters used for activating and configuring LTE2085: SIB
Reception with Parallel Measurement Gaps.................................... 315
Table 165 Parameters used for deactivating LTE2085: Reception with Parallel
Measurement Gaps.......................................................................... 322
Table 167 Existing counters related to LTE2120............................................... 327
Table 172 LTE2128 Summary of changes........................................................ 339
Table 176 Existing key performance indicators related to LTE2128................. 343


Table 180 Parameters used for activating and configuring LTE2128: Uplink Intra
eNodeB CoMP 8 RX with Softbit Combination.................................344
Table 183 Sales information..............................................................................351
Table 188 Parameters used for activating and configuring LTE2149:
Supplemental Downlink Carrier........................................................ 357
Table 198 Parameters used for activating and configuring the LTE2305: Inter-
eNodeB Carrier Aggregation for 2 Macro eNodeBs feature............. 376
Table 202 Parameters used for configuring LTE2314: Configurable Sequence of
BCCH Carriers within GERAN Frequency Layer List for CSFB Based
on UE Context Release.................................................................... 384
Table 204 New parameters introduced by LTE2324 ........................................ 392
Table 206 Table 4 lists the parameters used for activating and configuring the
LTE2324: Network-requested UE Radio Capabilities feature...........393
Table 207 Parameters used for activating and configuring LTE2388: VoLTE Call
Steering Enhancement..................................................................... 398


Table 217 Parameters used for activating and configuring LTE2430: QCI1
Establishment Triggered Protection Timer feature........................... 406

LTE64: Service based handover thresholds LTE15A Radio Resource Management and Telecom
Features
1 LTE64: Service based handover thresholds
1.1 Description of LTE64: Service-based Handover

Thresholds
Introduction to the feature
The LTE64: Service-based Handover Thresholds feature introduces dedicated handover
(HO) thresholds that are used when a UE has a QCI1 bearer active.
Benefits
End-user benefits
Better radio frequency coverage for VoLTE users is ensured. VoLTE users can be
handed over either earlier or later than data-only users.
Operator benefits
This feature provides:
• different points of activation/deactivation of inter-frequency/inter-RAT measurements

(A1/A2 event)
• different points of triggering of the inter-frequency/inter-RAT handover (A3/A5/B2
event)
Functional description
The operator can configure dedicated thresholds for a UE that has a QCI1 bearer
(VoLTE call) established.
Table 1: New dedicated thresholds introduced with the LTE64: Service-based Handover
Thresholds feature shows which of the new measurements are active in particular
handovers.
Handover Thresholds feature
HO Measurement type New dedicated threshold for
HO measurement
inter-frequency intra- A1 to stop inter-frequency HO A1_QCI1
LTE measurements
A2_QCI1_IF
A2 to start inter-frequency HO
A3_QCI1_IF
measurements
A5_QCI1_IF
A3 for inter-frequency HO measurements
(better cell)
A5 for inter-frequency HO measurements
(coverage)
SRVCC LTE to A1 to stop SRVCC measurements A1_QCI1

WCDMA
B2 for SRVCC measurements B2_QCI1_WCDMA

LTE15A Radio Resource Management and Telecom LTE64: Service based handover thresholds
Features

Handover Thresholds feature (Cont.)
HO Measurement type New dedicated threshold for
HO measurement
GERAN
B2 for SRVCC measurements B2_QCI1_GERAN

1xRTT
A2 to start SRVCC measurements A2_QCI1_C2K
For other dedicated HO thresholds, see the LTE2112: Dedicated Mobility Thresholds for
SRVCC, LTE1198: RSRQ Triggered Mobility, and LTE738: SRVCC to 1xRTT/CDMA
feature descriptions.
The thresholds introduced with the LTE64: Service-based Handover Thresholds feature
are as follows:
• dedicated VoLTE A2 threshold to start LTE inter-frequency measurements
• dedicated VoLTE A2 thresholds to start SRVCC to 1xRTT measurements
• dedicated VoLTE A1 threshold to stop inter-frequency or SRVCC measurements
• dedicated A3/A5 measurement setting per target frequency layer for inter-frequency
HO
• dedicated B2 measurement (GSM, UTRAN) setting per target frequency layer
The A1/A2/A3/A5/B2 measurement configurations are updated with the

establishment/removal of a QCI1 bearer. The usage of separate QCI1 thresholds is
optional. This means that if the LTE64: Service-based Handover Thresholds feature is
activated, and a value for a threshold for QCI1 is given, then this threshold will be used.
If no such separate threshold is given, then a legacy threshold is used instead. The
operator is free to use the separate QCI1 thresholds for each threshold which is
supported.
Upon the establishment of a QCI1 bearer, all thresholds are exchanged by the
configured QCI1 values. The eNB always stores the last reported RSRP value of the UE
and uses this at the QCI1 establishment/release to select (and configure) the correct
thresholds. This is done as thresholds may have to be changed and, therefore, another
set of configured thresholds might be needed based on the last reported RSRP value
(which is stored in the eNB).
Disabling A2-based redirect for VoLTE calls

The LTE64: Service-based Handover Thresholds feature introduces an O&M parameter
to disable an A2-based redirect when a UE has a QCI1 bearer established. When this
parameter is set to disabled, and the first QCI1 bearer is established for the UE, both
RSRP- and RSRQ-based A2-redirect measurements (if configured) will be either
deactivated or not activated. The measurements will be re-activated when the UE has no
longer any QCI1 bearer. When this parameter is set to enabled, then the A2-based
redirect configuration will not change in case of a QCI1 bearer establishment/release.
Disabling the A2-based redirect when a UE has a QCI1 bearer is not controlled by the
LTE64: Service-based Handover Thresholds feature flag. This feature flag controls the
usage of dedicated thresholds only.

Features
System impact
Interdependencies between features
• LTE2112: Dedicated Mobility Thresholds for SRVCC

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

This feature has no impact on network management tools.
Impact on system performance and capacity
The LTE64: Service-based Handover Thresholds feature improves SRVCC and VoLTE
call drop rate by decreasing VoLTE coverage via earlier start of inter-frequency and inter-
RAT measurements and specific HO thresholds for VoLTE leading to earlier handovers.
This depends on how the HO thresholds are set.
1.2 LTE64 reference data

LTE64: Service based handover thresholds requirements, alarms and faults, commands,
measurements and counters, KPIs, parameters, and sales information
Requirements

Features
Table 2 LTE64 hardware and software requirements

FDD TDD
System release FDD-LTE 15A TD-LTE 15A
Flexi Multiradio 10 BTS FL15A TL15A
Flexi Multiradio 10 Indoor BTS Not supported TL15A
Nokia AirScale BTS FL16A TL16A
Flexi Zone BTS FL15A TL15A
Flexi Zone Access Point FL16 TL16
Cloud Flexi Zone Controller FL17A TL17A
OMS Not supported Not supported
NetAct NetAct 15.5 NetAct 15.5
MME Not supported Not supported
SAE GW Not supported Not supported
UE 3GPP R8 UE capabilities 3GPP R8 UE capabilities
Alarms
There are no alarms related to the LTE64: Service based handover thresholds feature.
BTS faults and reported alarms

There are no faults related to the LTE64: Service based handover thresholds feature.
Commands
There are no commands related to the LTE64: Service based handover thresholds
feature.
Measurements and counters
Table 3 New counters introduced by LTE64

Counter ID Counter name Measurement
M8021C37 Inter-frequency handover 8021 - LTE Handover (WBTS)
attempts for UEs with QCI1
(A3/A5 radio related handovers
only)
M8021C38 Successful inter-frequency 8021 - LTE Handover (WBTS)
handover completions for UEs
with QCI1 (A3/A5 radio related
handovers only)
For counters descriptions, see LTE Operating Documentation/Reference/Counters and

Key Performance Indicators.
Key performance indicators

There are no key performance indicators related to the LTE64: Service based handover
thresholds feature.

Features
Parameters
Table 4 New parameters introduced by LTE64

Full name Abbreviated Managed Parent Structure FDD/TDD
name object
RSRP threshold 2 threshold2C2k LNCEL threshold2C2k Common
For CDMA2000 Qci1 Config
during QCI1
A2 based redirect a2RedirectQci LNCEL - Common
for VoLTE calls 1
Threshold Th2 threshold2Int LNCEL - Common
InterFreq for RSRP erFreqQci1
during QCI1
Threshold Th2a for threshold2aQc LNCEL - Common
RSRP During QCI1 i1
A3 Offset RSRP a3OffsetRsrpI LNHOIF - Common
Inter Frequency nterFreqQci1
during QCI1
Threshold Th3 For threshold3Int LNHOIF - Common
RSRP inter erFreqQci1
frequency during
QCI1
Threshold Th3a For threshold3aIn LNHOIF - Common
RSRP inter terFreqQci1
frequency during
QCI1
Threshold1 GERAN b2Threshold1G LNHOG - Common
for RSRP of ERANQci1
serving cell
during QCI1
Threshold2 GERAN b2Threshold2R LNHOG - Common
For RSSI neighbor ssiGERANQci1
cell during QCI1
Threshold1 UTRA b2Threshold1U LNHOW - Common
for RSRP of traQci1
serving cell
during QCI1
for ecNo neighbor traEcn0Qci1
cell during QCI1
for RSCP neighbor traRscpQci1
cell during QCI1
Table 5 Existing parameters related to LTE64

name object
Activate service actServBasedM LNBTS - Common
based mobility obThr
thresholds

Features
Table 5 Existing parameters related to LTE64 (Cont.)

name object
Threshold 2 config threshold2C2k LNCEL - Common
for CDMA2000 HRPD Config
and 1xRTT
Time to trigger a2TimeToTrigg LNCEL threshold2C2k Common
for A2 to activate erActC2kMeas Config
CDMA2000
measurement
Related hysteresis hysThreshold2 LNCEL threshold2C2k Common
of RSRP threshold C2k Config
2 for CDMA2000
RSRP threshold 2 threshold2C2k LNCEL threshold2C2k Common
for CDMA2000 Config
Threshold th2 threshold2GER LNCEL - Common
GERAN for RSRP ANQci1
during QCI1
Threshold th2 threshold2Int LNCEL - Common
interFreq for RSRP erFreq
Threshold th2a for threshold2a LNCEL - Common
RSRP
Threshold th4 for threshold4 LNCEL - Common
RSRP
Threshold th2 threshold2Wcd LNCEL - Common
WCDMA for RSRP maQci1
during QCI1
Threshold th2 threshold2GER LNCEL - Common
GERAN for RSRP AN
Threshold th2 threshold2Wcd LNCEL - Common
WCDMA for RSRP ma
For parameter descriptions, see LTE Operating Documentation/Reference/Parameters
Sales information
Table 6 LTE64 sales information

BSW/ASW License control in network Activated by default
element
ASW SW Asset Monitoring No

Features
1.3 Activating and configuring LTE64: Service-based

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

Handover Thresholds
Parameter Purpose Requires eNB restart or
object locking
Activate service based mobility activation flag no
thresholds (actServBasedMobThr)
Threshold Th2a for RSRP During optional configuration no
QCI1 (threshold2aQci1)
Threshold Th2 InterFreq for RSRP optional configuration no
during QCI1
(threshold2InterFreqQci1)
RSRP threshold 2 For CDMA2000 optional configuration no
during QCI1 (threshold2C2kQci1)
A3 Offset RSRP Inter Frequency optional configuration no
during QCI1
(a3OffsetRsrpInterFreqQci1)
Threshold Th3 For RSRP inter optional configuration no
frequency during QCI1
(threshold3InterFreqQci1)
Threshold Th3a For RSRP inter optional configuration no
frequency during QCI1
(threshold3aInterFreqQci1)
Threshold1 UTRA for RSRP of optional configuration no
serving cell during QCI1
(b2Threshold1UtraQci1)
Threshold2 UTRA for ecNo optional configuration no
neighbor cell during QCI1
(b2Threshold2UtraEcn0Qci1)
Threshold2 UTRA for RSCP optional configuration no
(b2Threshold2UtraRscpQci1)
Threshold1 GERAN for RSRP of optional configuration no
serving cell during QCI1
(b2Threshold1GERANQci1)
Threshold2 GERAN For RSSI optional configuration no
(b2Threshold2RssiGERANQci1)
The following features need to be activated/configured before activation of the LTE64:

Service-based Handover Thresholds feature:

Features

• LTE7: Support of Multiple EPS Bearer
• If SRVCC to WCDMA is required, then the LTE872: SRVCC to WCDMA and LTE56:
Inter-RAT Handover to WCDMA features must be enabled, and corresponding A2/A1
and B2 dedicated thresholds must be configured.
• If SRVCC to GSM is required, then the LTE873: SRVCC to GSM feature must be
enabled, and corresponding A2/A1 and B2 dedicated thresholds must be configured.
• If SRVCC to 1xRTT is required, then the LTE738: SRVCC to 1xRTT/CDMA feature
must be enabled, and corresponding A2/A1 dedicated thresholds must be
configured.
• If inter-frequency handover is required for VoLTE calls, then the LTE55: Inter-
frequency handover feature must be enabled, and corresponding A2/A1 and A3/A5
dedicated thresholds must be configured.
• The LTE1060: TDD - FDD Handover feature needs to be enabled if an FDD/TDD
handover is needed.
Procedure
1 Follow the general procedure described in section Activating and deactivating LTE
features using BTS Site Manager.
In Step 3 (Modify the feature-specific eNB configuration settings) of the general

procedure perform the steps described in this procedure.
2 Activate the LTE64: Service-based Handover Thresholds feature.
a) Go to the Radio Network Configuration page.

b) Expand the MRBTS object.
c) Select the LNBTS object.
d) Set the Activate service based mobility
thresholds (actServBasedMobThr) parameter value to true.
3 Configure the A1 RSRP dedicated threshold (optional).
a) Expand the LNBTS object.

b) Select the LNCEL object.
c) Set the Threshold Th2a for RSRP During QCI1 (threshold2aQci1)
parameter value.
g Note: If the Threshold th1 for RSRP (threshold1) LNCEL parameter

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

Features
4 Configure the A2 RSRP, A3 RSRP offset, and A5 RSRP threshold1 and threshold2
dedicated thresholds for inter-frequency (if the LTE55: Inter-frequency Handover feature
is enabled - optional).
a) Select the LNCEL object.

b) Set the Threshold Th2 InterFreq for RSRP during
QCI1 (threshold2InterFreqQci1) parameter value for A2 measurement.
g Note: The Threshold Th2 InterFreq for RSRP during

QCI1 (threshold2InterFreqQci1) parameter value needs to be lower than
or equal to the Threshold Th2a for RSRP During
QCI1 (threshold2aQci1) LNCEL parameter value.
c) Right-click the LNCEL object.
d) Select the New LNHOIF object.
e) For the LNHOIF object, set the parameter values as follows:
• Neighbor interfrequency LTE cell handover
identifier (lnHoIfId)
• Presence antenna port1 (interPresAntP)
• Measurement bandwidth (measurementBandwidth)
• Eutra carrier info (eutraCarrierInfo)
• A3 measurement: A3 Offset RSRP Inter Frequency during
QCI1 (a3OffsetRsrpInterFreqQci1)
• A5 measurement: Threshold Th3 For RSRP inter frequency
during QCI1 (threshold3InterFreqQci1)
• A5 measurement: Threshold Th3a For RSRP inter frequency
during QCI1 (threshold3aInterFreqQci1)
5 Configure the A2 RSRP, B2 threshold1 RSRP, B2 Ecn0, and B2 RSCP dedicated

thresholds for SRVCC to WCDMA (if the LTE872: SRVCC to WCDMA feature is enabled
- optional).

b) Set the Threshold Th2 WCDMA for RSRP during
QCI1 (threshold2WcdmaQci1) parameter value for A2 measurement.
g Note: The Threshold Th2 WCDMA for RSRP during

QCI1 (threshold2WcdmaQci1) parameter value needs to be lower than or
equal to the Threshold Th2a for RSRP During
d) Select the New LNHOW object.
e) For the LNHOW object, set the parameter values as follows:
• Neighbor WCDMA BTS cell handover identifier (lnHoWId)
• UTRAN carrier frequency (utraCarrierFreq)

Features
• B2 measurement: Threshold1 UTRA for RSRP of serving cell

during QCI1 (b2Threshold1UtraQci1)
• B2 measurement: Threshold2 UTRA for ecNo neighbor cell
during QCI1 (b2Threshold2UtraEcn0Qci1)
• B2 measurement: Threshold2 UTRA for RSCP neighbor cell
during QCI1 (b2Threshold2UtraRscpQci1)
6 Configure the A2 RSRP, B2 threshold1 RSRP, and B2 RSSI dedicated thresholds for
SRVCC to GERAN (if the LTE873: SRVCC to GSM feature is enabled - optional).

b) Set the Threshold th2 GERAN for RSRP during
QCI1 (threshold2GERANQci1) parameter value for A2 measurement.
g Note: The Threshold th2 GERAN for RSRP during

QCI1 (threshold2GERANQci1) parameter value needs to be lower than or
equal to the Threshold Th2a for RSRP During
d) Select the New LNHOG object.
e) For the LNHOG object, set the parameter values as follows:
• Neighbor GERAN BTS cell handover identifier (lnHoGId)
•
1. Expand the LNHOG object.
2. For the ARFCN value list object, set the ARFCN value
list (arfcnValueListGERAN) parameter value.
• B2 measurement: Threshold1 GERAN for RSRP of serving cell
during QCI1 (b2Threshold1GERANQci1)
• B2 measurement: Threshold2 GERAN For RSSI neighbor cell
during QCI1 (b2Threshold2RssiGERANQci1)
7 Configure the A2 RSRP dedicated threshold for SRVCC to 1xRTT (if the LTE738:
SRVCC to 1xRTT/CDMA feature is enabled) (optional).
a) Right-click the LNCEL object.

b) Select the New Threshold 2 config for CDMA2000 HRPD and 1xRTT object (if
not created).
c) For the Threshold 2 config for CDMA2000 HRPD and 1xRTT
parameter structure, set the RSRP threshold 2 For CDMA2000 during
QCI1 (threshold2C2kQci1) parameter value for A2 measurement.
8 Send the parameters to the eNB according to the procedure described in section
Activating and configuring LTE64: Service based Handover Thresholds.

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

Thresholds
Before you start
The Activate service based mobility
thresholds (actServBasedMobThr) parameter is used for deactivation.
Modification of this parameter requires neither eNB restart nor cell locking.
Procedure

2 Deactivate the LTE64: Service-based Handover Thresholds feature.

d) Set the Activate service based mobility
thresholds (actServBasedMobThr) parameter value to false.
Deactivating LTE64: Service-based Handover Thresholds.
Expected outcome
Both features, LTE2112: Dedicated Mobility Thresholds for SRVCC and LTE64: Service-
based Handover Thresholds, are deactivated. The eNB stops support of dedicated
thresholds for VoLTE inter-frequency handovers and for SRVCC to
WCDMA/GERAN/1xRTT. The eNB uses legacy thresholds for inter-frequency handovers
of VoLTE calls and SRVCC.

LTE15A Radio Resource Management and Telecom LTE569: Downlink Adaptive Closed Loop SU-MIMO 4x4
Features
2 LTE569: Downlink Adaptive Closed Loop SU-

MIMO 4x4
2.1 Description of LTE569: Downlink Adaptive Closed

Loop SU-MIMO 4x4 - TM 4
The LTE569: Downlink Adaptive Closed Loop SU-MIMO 4x4 - TM 4 feature enables the
eNB supporting downlink (DL) adaptive closed loop (CL) single-user multiple inputs
multiple outputs (SU-MIMO) 4x4 with transmission mode 4 (TM4). This feature extends
an existing MIMO functionality to support MIMO 4x4 with a transmission of up to four
layers in DL.
Benefits
End-user benefits
This feature provides higher downlink peak rates on a single frequency layer to end
users with category 5 or category 8 UEs supporting spatial multiplexing with up to four
layers.
Operator benefits
The deployment of the LTE569: Downlink Adaptive Closed Loop SU-MIMO 4x4 - TM 4
feature has an impact on a cell, and thus on network capacity (average cell throughput)
and coverage (cell edge throughputs). In an initial simulation in ideal conditions, this
feature produces the following results:
• Compared to the SU-MIMO 4x2 with TM4 enabling this feature causes a 40% to 60%
increase in case of 100% penetration of UEs supporting a maximum of four layers.
However, network's capacity and coverage gains depend also on channel conditions
(such as SINR, etc.).
• In comparison to the performance of MIMO 4x2 TM4, the SU-MIMO 4x4 with TM4
generates a gain of about 48% in cell capacity and 57% in cell edge throughput.
Requirements
For more information, see Reference data section.
Functional overview
The main goal of LTE569: Downlink Adaptive Closed Loop SU MIMO 4x4 - TM 4 is to
support DL transmissions using more than two-layers-spatial multiplexing for category 5
and category 8 UEs. This feature extends the current MIMO functionality to support
MIMO 4x4 TM4 with a transmission of up to four layers in the downlink. In comparison to
the LTE568: DL Adaptive Closed Loop MIMO (4x2) feature, the maximum number of
layers in transmission increases from two to four. Consequently, the DL throughput peak
rates can even be doubled for category 5 and category 8 UEs under very good radio
conditions. Higher cell average and coverage throughputs are also achieved.

LTE569: Downlink Adaptive Closed Loop SU-MIMO 4x4 LTE15A Radio Resource Management and Telecom
Features
The Flexi Multiradio BTS supports 4x4 adaptive closed loop downlink single-user MIMO
transmission mode 4 by providing a fast switch between spatial multiplexing with one,
two, three, four layers and 4-way Tx diversity. This "Fast Adaptive MIMO Switching" is
based on the rank indication (RI) and precoding matrix indication (PMI) reported by the
UE. A submode is always switched in case the RI value is changed, and the chosen
submode depends on RI's value (for more information, see Table 8: Transmission
submodes).
The LTE569: Downlink Adaptive Closed Loop SU MIMO 4x4 - TM 4 feature comprises
the following:
• DL adaptive closed loop MIMO (4x4)
• 4 Tx fast adaptive closed loop MIMO 4x4
• 4-way TxDiv
DL adaptive closed loop MIMO (4x4)

This feature supports the following data channels:
• transmission mode 4 (TM4) supporting a maximum of four layers used as the basic
mode for 3GPP category 5 and category 8 UEs for SU-MIMO as well as for transmit
diversity
• adaptive fast switching between one, two, three, and four layers
• 4-way Tx Diversity based on 4 CRS ports, which is one of the submodes in TM4, and
used in case of no RI/PMI reports
This feature supports the following control channels:
• 4-way Tx diversity based on 4 ports CRS applied for PDCCH, PCFICH, PHICH and
PBCH
• 4-way Tx diversity based on 4 ports CRS is applied to common control channels
transmitted via PDSCH (SIB messages, paging, RA msg2, RA msg4)
• precoding vector switching applied to the primary synchronization signal (PSS) and
secondary synchronization signal (SSS)
g Note: The eNodeB uses:

• transmission mode 4 with DCI format 2 for closed-loop-spatial-multiplexing or
transmit diversity
• transmission mode 4 with DCI format 1A for transmit diversity
• transmission mode 4 with support of 3-layer and 4-layer transmission where one
codeword (CW) is mapped to 2 layers
Based on the RI and PMI provided by the UE, the eNB ensures a fast switch between 1-
layer to 4-layer spatial multiplexing and 4 Tx diversity, and it modifies HARQ to adapt
one CW mapped to two layers.
4 Tx fast adaptive closed loop MIMO 4x4

For the MIMO 4x4 feature, a fast switching algorithm is extended to support three and
four layers. Therefore, based on the RI and the PMI provided by the UE, a fast switch
needs to support switching between spatial multplexing of one to four layers. Data

Features
channels support one codeword mapped to 2-layer spatial multiplexing. Data

transmission via PDSCH uses MIMO 4x4 TM4 and is performed in five transmission
schemes/submodes as shown in Table 8: Transmission submodes.
Table 8 Transmission submodes

Transmission schemes/submodes
single codeword, single layer closed-loop- Reported PMI is used for precoder selection for
spatial-multiplexing in case UE reports rank a single layer transmission.
indicator being one (RI=1)
dual codeword, dual layer closed-loop-spatial- Reported PMI is used for precoder selection for
multiplexing in case UE reports rank indicator a dual layer transmission.
being two (RI=2)
dual codeword, three layer closed-loop-spatial- Reported PMI is used for precoder selection for
multiplexing in case UE reports rank indicator a three layer transmission.
being three (RI=3)
dual codeword, four layer closed-loop-spatial- Reported PMI is used for precoder selection for
multiplexing in case UE reports rank indicator a four layer transmission.
being four (RI=4)
transmit diversity with 4 ports CRS in case of no reports or missing PMI/RI reports
4-way TxDiv
Transmit diversity using four antenna ports is used whenever there is no valid channel
state information and related rank indicator information available for transmissions:
• There is no update of valid closed loop RI/PMI reports for PDSCH transmissions
since a characteristic update time in TTIs. If there is no valid report within this time
period, the eNB switches the transmission scheme to 4-way TxDiv.
• During initialization when the radio resource control (RRC) setup is performed and
no valid joint report for RI and PMI is known to the eNB.
• The UE does not send valid reports including RI and PMI as it is required for TM4 CL
operation.
LTE569: Downlink Adaptive Closed Loop SU MIMO 4x4 - TM 4 configuration

The LTE569: Downlink Adaptive Closed Loop SU MIMO 4x4 - TM 4 feature can be
enabled when four Tx antennas are connected to the eNB, and when they are defined on
the resource list. The feature is activated by setting the dlMimoMode parameter to the
closed loop MIMO (4x4) enumeration value. This feature supports a fast adaptive MIMO
switching, that is, a fast rank selection and fast codebook-based pre-coding of data
transmission, using CL feedback of PMI in combination with RI. Fast adaptive MIMO
switching can be enabled by setting the Activate fast adaptive MIMO switch
(actFastMimoSwitch) parameter to true. PMI and RI reporting delays have to be
minimized by periodic and aperiodic reports sent by UEs.
System impact
The following features are recommended to be enabled before the activation of the
LTE569: Downlink Adaptive Closed Loop SU MIMO 4x4 - TM 4 feature in order to
balance the increased cell throughput and link level gains provided by MIMO 4x4 in the
downlink:

Features
• LTE936: IRC for 4 Rx Paths in Uplink

• LTE1691: Uplink Intra-eNB CoMP 4Rx (in case the bandwidth is 20MHz in BTS Flexi
10)
• LTE72: 4-way RX Diversity
Interworking with carrier aggregation features:

For category 5 and 8 UEs that also support CA, their transmission modes are further
dependent on the value of the cell level O&M parameter, which specifies the preference
between CA and MIMO 4x4, and whether DL CA is enabled or not.
• If CA is enabled and MIMO 4x4 is preferred over CA, then the maximum supported
number of layers for spatial multiplexing is four. They will work with MIMO 4x4 TM4
and there should be no interworking with CA, even when they switch to one or two
layers due to non-ideal channel conditions.
• If CA is enabled and preferred over MIMO 4x4, then the maximum supported number
of layers for spatial multiplexing is restricted to a maximum of two layers by the
codebookSubsetRestriction parameter.
The carrier aggregation features and the LTE569: Downlink Adaptive Closed Loop SU
MIMO 4x4 - TM 4 feature can be enabled together; however, they do not interwork
simultaneously for UEs capable of both functionalities.
The feature has no impact on interfaces.


Depending on channel conditions, the LTE569: Downlink Adaptive Closed Loop SU
MIMO 4x4 - TM 4 feature causes an increase in throughput. The gain is significant when
a UE is in a very good channel condition.
Management data
Sales information

LTE569: Downlink adaptive closed loop SU MIMO 4x4 - TM 4 requirements, alarms and
faults, commands, measurements and counters, KPIs, parameters, and sales
information
Requirements

Features

FDD TDD
System release Not supported TD-LTE 15A
Flexi Multiradio 10 BTS Not supported TL15A
Nokia AirScale BTS Not supported TL16A
Flexi Zone BTS Not supported Not supported
Flexi Zone Access Point Not supported Not supported
Cloud Flexi Zone Controller Not supported Not supported
NetAct Not supported NetAct 15.5
UE Not supported • 3GPP R8 UE capabilities
• 3GPP R10 UE capabilities
Alarms
There are no alarms related to the LTE569: Downlink adaptive closed loop SU MIMO
4x4 - TM 4 feature.

There are no faults related to the LTE569: Downlink adaptive closed loop SU MIMO 4x4
- TM 4 feature.
Commands
There are no commands related to the LTE569: Downlink adaptive closed loop SU
MIMO 4x4 - TM 4 feature.

M8001C234 Average number of active UEs LTE Cell Load
with UE Category 8
M8001C493 Average number of active UEs LTE Cell Load
with UE Category 5
M8010C71 MIMO Closed Loop Double LTE Power and Quality DL
Codeword Three Layer
Codeword Four Layer
M8010C73 MIMO Closed Loop Single LTE Power and Quality DL
Codeword Two Layer
M8010C92 MIMO Fallback to TxDiversity LTE Power and Quality DL

Features
Table 11 Existing counters related to LTE569

M8010C57 MIMO Closed Loop Single LTE Power and Quality DL
Codeword
Codeword


There are no key performance indicators related to the LTE569: Downlink adaptive
closed loop SU MIMO 4x4 - TM 4 feature.
Parameters

Full name Abbreviated name Manage Parent structure FDD/TDD
d object
Preference MIMO 4x4 pref4LayerMimo LNCEL - Common
versus carrier VsCAggr _FDD/_
aggregation TDD

Full name Abbreviated Managed Parent structure FDD/TDD
name object
Activation of actDLCAggr LNBTS - Common
downlink carrier
aggregation
Activate Uplink actUlCoMp LNBTS - Common
CoMP
Activate fast actFastMimoSw LNCEL - Common
adaptive MIMO itch _FDD/_TDD
switch
Spatial Mode for dlInterferenc LNCEL - TDD
Downlink eSpatialMode _FDD/_TDD
Interference
Downlink MIMO mode dlMimoMode LNCEL - Common
_FDD/_TDD
MIMO power dlpcMimoComp LNCEL - Common
compensation
Rank indication riEnable LNCEL - Common
reporting enable
Uplink combination ulCombination LNCEL - Common
mode Mode
Sales information

Features

element
2.3 Activating and configuring LTE569: Downlink

Adaptive Closed Loop SU-MIMO 4x4 - TM 4
Before you start
The Downlink MIMO mode (dlMimoMode) parameter is used to activate the feature.
An activation of SU-MIMO 4x4 with TM4 requires object locking.
The following conditions must be met before the activation of the LTE569: Downlink
Adaptive Closed Loop SU-MIMO 4x4 - TM 4 feature:
• Antenna system with four antenna elements in a transmit direction must be prepared.
• The LTE568: DL Adaptive Closed Loop MIMO 4x2 and LTE72: 4-way RX Diversity
features must be activated.
• The LTE936: IRC for 4 Rx Paths in Uplink feature is recommended to be enabled.
• The LTE1691: Uplink Intra-eNB CoMP 4Rx is recommended to be enabled in case
the bandwidth is 20 MHz in BTS Flexi 10.
Table 15 Parameters used for activating and configuring LTE569: Downlink Adaptive
Closed Loop SU-MIMO 4x4 - TM 4
object locking
Downlink MIMO activation flag object locking
mode (dlMimoMode)
Activate fast adaptive mandatory configuration object locking
MIMO
switch (actFastMIMOSwitch)
Procedure

2 Activate the LTE569: Downlink Adaptive Closed Loop SU-MIMO 4x4 - TM 4 feature.
a) Go to the Cell Resources page.

b) In the Local cells section, select the cell where the LTE569: Downlink Adaptive
Closed Loop SU-MIMO 4x4 - TM 4 feature will be activated.

Features
c) Configure four Tx antennas in the Antennas section.

d) In the MIMO settings section, set the Downlink MIMO mode (dlMimoMode)
parameter to Closed Loop MIMO (4x4).
3 Configure feature-related parameters.

c) Expand the LNBTS object.
d) Select the LNCEL object corresponding to the cell where the LTE569: Downlink
Adaptive Closed Loop SU-MIMO 4x4 - TM 4 feature is being activated.
g Note: From release LTE17 onwards, due to a change in the MO architecture,

you need to select the LNCEL/LNCEL_FDD for FDD object or
LNCEL/LNCEL_TDD for TDD object.
e) Set the Activate fast adaptive MIMO switch (act
FastMIMOSwitch) parameter to true.
Activating and deactivating LTE features using BTS Site Manager.
Expected outcome
The cells of the eNodeB are connected to a multi-antenna system with four antenna
elements, and the LTE569: Downlink Adaptive Closed Loop SU-MIMO 4x4 - TM 4
feature is enabled.
2.4 Deactivating LTE569: Downlink Adaptive Closed

Loop SU-MIMO 4x4 - TM 4
Before you start
The Downlink MIMO mode (dlMimoMode) parameter is used to deactivate the
feature. Deactivation of SU-MIMO 4x4 with TM4 requires object locking.
Procedure


Features
2 Deactivate the LTE569: Downlink Adaptive Closed Loop SU-MIMO 4x4 - TM 4 feature.

b) In the Local cells section, select the cell where the LTE569: Downlink Adaptive
Closed Loop SU-MIMO 4x4 - TM 4 feature will be activated.
c) In the MIMO settings section, set the Downlink MIMO mode (dlMimoMode)
parameter to a value different from Closed Loop MIMO (4x4).
g Note: Chosing different values of the Downlink MIMO mode (dlMimoMode)

parameter activates other features. Thus, it might be neccessary to set other
parameters in the Antennas section and on the Radio Network Configuration
page, in the LNCEL object.
Expected outcome
The LTE569: Downlink Adaptive Closed Loop SU-MIMO 4x4 - TM 4 feature is
deactivated.

LTE738: SRVCC to 1xRTT/CDMA LTE15A Radio Resource Management and Telecom
Features
3 LTE738: SRVCC to 1xRTT/CDMA
3.1 Description of LTE738: SRVCC to 1xRTT/CDMA

With the LTE738: SRVCC to 1xRTT/CDMA feature, coverage and service-based single
radio voice call continuity (SRVCC) from LTE to 1xRTT/CDMA are possible.
Benefits
End-user benefits
This feature can keep up VoLTE call continuity SRVCC to 1xRTT/CDMA network.
Operator benefits
This feature provides seamless handover for voice services to 1xRTT/CDMA when
leaving the LTE coverage.
Functional overview
The LTE738: SRVCC to 1xRTT/CDMA feature enables service continuity of voice
services from the packet-switched (PS) to the circuit-switched (CS) domain when a UE
with at least one voice service bearer (QCI1) changes from an LTE to a 1xRTT cell.
The SRVCC capability of the UE and the MME is indicated by the MME with the S1AP:
Initial Context Setup Request message. In case of a handover (HO), the
target eNB is informed either by the MME via the S1AP: Handover Request
message or by the source eNB via the X2AP: Handover Request message.
Figure 1 HO messages
X2AP:HandoverRequest S1AP:HandoverRequest
sourceeNB targeteNB MME
SRVCC to 1xRTT/CDMA process

The SRVCC is split into three areas: triggering, preparation, and execution.
SRVCC trigger
• If the UE has an EPS bearer with at least QCI1 established, and the MME and UE
are SRVCC-capable, 1xSRVCC B2 is activated in a UE, based on the air conditions
via mobility A2.
• Only one target 1xRTT carrier can be measured by one UE.
• QCI1 bearer:
– The eNB supports the SRVCC if there is at least one QCI1 bearer established. If
the QCI1 bearer is established/released during ongoing measurement, the

LTE15A Radio Resource Management and Telecom LTE738: SRVCC to 1xRTT/CDMA
Features
measurement targets are modified according to 1xSRVCC and HRPD HO

measurements (if HO to eHRPD is enabled).
– The eNB supports 1xSRVCC in case of multiple QCI1 bearers. An evolved
packet core (EPC) selects the bearer to execute the SRVCC.
SRVCC preparation
• If the eNB receives a measurement report from the UE, it initiates an inter-RAT HO
by sending the RRC: Handover From EUTRA Preparation Request
message to the UE.
• The eNB gets the RRC: ULHandoverPreparationTransfer message
containing the 1xRTT origination message from the UE and sends the S1AP:
UPLINK S1 CDMA2000 TUNNELING message with the CDMA2000 HO Required
Indication to the MME.
SRVCC execution
• The MME responds to the eNB with the S1AP: DOWNLINK S1 CDMA2000
TUNNELING message including the CDMA2000 HO Status information element (IE).
• The CDMA2000 HO Status IE indicates an HO preparation status as follows:
– a successful HO preparation: the eNB forwards the 1x Handoff direction
message embedded in the RRC: MobilityFromEUTRACommand message to
the UE; as a result, the UE is moved to the 1xRTT area
– a failed HO preparation: the eNB sends the RRC: DLInformationTransfer
that indicates the failure to the UE; as a result, the UE is maintained in the
EUTRAN area
System impact
• LTE426: System Time Broadcast for SIB8

The LTE738: SRVCC to 1xRTT/CDMA feature reuses the LTE426: System Time
Broadcast for SIB8 feature. The eNB broadcasts the CDMA system time in SIB8 if
the LTE738: SRVCC to 1xRTT/CDMA feature is enabled, and the time source is
available.
The LTE10: EPS Bearers for Conversational Voice feature is a pre-condition to
establish a VoIP bearer. The LTE10: EPS Bearers for Conversational Voice feature
must be activated to activate the LTE738: SRVCC to 1xRTT/CDMA feature.
• LTE7: Support of Multiple EPS Bearers
The LTE7: Support of Multiple EPS Bearers feature is a pre-condition to establish a
VoIP bearer. The LTE7: Support of Multiple EPS Bearers feature must be activated to
activate the LTE738: SRVCC to 1xRTT/CDMA feature.
• LTE572: IMS Emergency Sessions
To support an IMS emergency call over LTE, the LTE572: IMS Emergency Sessions
feature needs to be enabled. 1xSRVCC for emergency calls is supported in case of
an ongoing emergency bearer using QCI1.
• LTE490: Subscriber Profile-based Mobility, LTE486: PLMN ID Selected Mobility
Profiles
The LTE490: Subscriber Profile-based Mobility or LTE486: PLMN ID Selected
Mobility Profiles feature might be active parallel to the LTE738: SRVCC to
1xRTT/CDMA feature. Mobility profiles shall not be supported in the LTE738: SRVCC
to 1xRTT/CDMA feature.

Features
• LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB), LTE874: CSFB to

CDMA/1xRTT for Dual RX UEs
The LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB), LTE874: CSFB
to CDMA/1xRTT for Dual RX UEs and LTE738: SRVCC to 1xRTT/CDMA features
can be activated independently. The LTE738: SRVCC to 1xRTT/CDMA feature
serves the SRVCC-capable UE, while the LTE1441: Enhanced CS Fallback to
CDMA/1xRTT (e1xCSFB)/LTE874: CSFB to CDMA/1xRTT for Dual RX UEs feature
serves UEs without the SRVCC capability, but with the CSFB capability.
• LTE761: Advanced Target Cell Selection and Handover Retry for Intra-frequency
Handover
An HRL might be used to prohibit handover to cdma2000 systems, which needs to
be considered by the LTE738: SRVCC to 1xRTT/CDMA feature.
• LTE116: Cell Bandwidth - 3 MHz, LTE117: Cell Bandwidth - 1.4 MHz
When 1.4M/3MHz LTE cell bandwidth is used, the LTE738: SRVCC to 1xRTT/CDMA
feature should be deactivated.
• The following features must be deactivated because only EUTRAN and CDMA target
layers are supported for the LTE738: SRVCC to 1xRTT/CDMA feature:
– 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
• LTE64: Service-based Handover Thresholds

The LTE738: SRVCC to 1xRTT/CDMA and LTE64: Service-based Handover
Thresholds features could exist in parallel. When the LTE64: Service-based
Handover Thresholds feature is disabled, the LTE738: SRVCC to 1xRTT/CDMA
feature-defined parameters (A1 and A2 related) are used. When the LTE64: Service-
based Handover Thresholds feature is enabled, parameters covered by the LTE64:
Service-based Handover Thresholds feature are applicable.
For S1 and X2 interfaces, the EUTRA capability is newly supported with feature group
indicators (FGIs) bit 11 and 24.


This feature has no impact on system performance or capacity.

LTE738: SRVCC to 1xRTT/CDMA requirements, alarms and faults, commands,
Requirements

Features

FDD TDD
Cloud Flexi Zone Controller FL17A FL17A
Alarms
There are no alarms related to the TE738: SRVCC to 1xRTT/CDMA feature.

There are no faults related to the TE738: SRVCC to 1xRTT/CDMA feature.
Commands
There are no commands related to the TE738: SRVCC to 1xRTT/CDMA feature.

M8016C41 Inter System Handover 8016 - LTE Inter System
attempts to 1xRTT with Handover (WBTS)
SRVCC
M8016C36 Inter System Handover 8016 - LTE Inter System
preparations to 1xRTT with Handover (WBTS)
SRVCC
M8016C37 Failed Inter System Handover 8016 - LTE Inter System
SRVCC due to expiration of
guarding timer
TUlHoPrepTransfer1xSrvcc
SRVCC due to expiration of
guarding timer
TC2KRelocPrep1xSrvcc

Features
Table 17 New counters introduced by LTE738 (Cont.)

M8016C42 UE context release due to Inter 8016 - LTE Inter System
System Handover to 1xRTT Handover (WBTS)
with SRVCC
M8016C40 Successful Inter System 8016 - LTE Inter System
Handover preparations to Handover (WBTS)
1xRTT with SRVCC
SRVCC due to received HO
Failure indication message


There are no key performance indicators related to the TE738: SRVCC to 1xRTT/CDMA
feature.
Parameters

name object
Activate SRVCC to act1xSrvcc LNBTS_FD - FDD
CDMA/1xRTT D
Activate SRVCC to act1xSrvcc LNBTS_TD - TDD
CDMA/1xRTT D
CDMA2000 SRVCC to measConfigSrv LNHOX - Common
1xRTT measurement ccRtt
configuration
Threshold1 b2Threshold1R LNHOX measConfigSrv Common
CDMA2000-1XRTT for tt ccRtt
RSRP of serving
cell
Threshold2 b2Threshold2P LNHOX measConfigSrv Common
CDMA2000 for 1XRTT strRtt ccRtt
neighbour cell
Time to trigger b2TimeToTrigg LNHOX measConfigSrv Common
CDMA2000-1XRTT erRttMeas ccRtt
measurement report
Related hysteresis hysB2Threshol LNHOX measConfigSrv Common
of CDMA2000-1XRTT dRtt ccRtt
B2Th1 and B2Th2
CDMA2000 1XRTT offsetFreqRtt LNHOX measConfigSrv Common
frequency specific ccRtt
offset
Interval for reportInterva LNHOX measConfigSrv Common
periodical lRtt ccRtt

Features
Table 18 New parameters introduced by LTE738 (Cont.)

name object
CDMA2000-1XRTT
meas reporting
Single radio voice srvccAllowed LNRELX - Common
call continuity
allowed
Table 19 Parameters modified by LTE738

Pre LTE15A LTE15A and beyond
Full name Abbreviat Managed Parent Abbreviat Managed Parent FDD/TDD
ed name object Structure ed name object Structure
CDMA200 rttPrer LNCEL - rttRefC LNCEL - Common
0 1xRTT egRefCe ellId
referen llId
ce cell
id
CDMA200 rttPrer LNCEL rttPrer rttCell LNCEL rttRefC Common
0 1xRTT egCellI egRefCe Id ellId
referen d llId
ce cell
cell ID
CDMA200 rttPrer LNCEL rttPrer rttMark LNCEL rttRefC Common
0 1xRTT egMarke egRefCe etId ellId
referen tId llId
ce cell
market
ID
CDMA200 rttPrer LNCEL rttPrer rttSect LNCEL rttRefC Common
0 1xRTT egSecto egRefCe orId ellId
referen rId llId
ce cell
sector
ID
CDMA200 rttPrer LNCEL rttPrer rttSwNo LNCEL rttRefC Common
0 1xRTT egSwNo egRefCe ellId
referen llId
ce cell
switch
number
Thresho - - - thresho LNCEL - Common
ld 2 ld2C2kC
config onfig
for
CDMA200
0 HRPD
and
1xRTT
Time to a2TimeT LNCEL - a2TimeT LNCEL thresho Common
trigger oTrigge oTrigge ld2C2kC
for A2 rActHrp rActC2k onfig
to dMeas Meas
activat

Features
Table 19 Parameters modified by LTE738 (Cont.)

Pre LTE15A LTE15A and beyond
Full name Abbreviat Managed Parent Abbreviat Managed Parent FDD/TDD
ed name object Structure ed name object Structure
e
CDMA200
0
measure
ment
Related hysThre LNCEL - hysThre LNCEL thresho Common
hystere shold2H shold2C ld2C2kC
sis of rpd 2k onfig
RSRP
thresho
ld 2
for
CDMA200
0
RSRP thresho LNCEL - thresho LNCEL thresho Common
thresho ld2Hrpd ld2C2k ld2C2kC
ld 2 onfig
for
CDMA200
0

name object
CDMA2000 1xRTT csfbRegParam1 CDFIM - Common
CSFB registration xRtt
parameters
CDMA2000 1xRTT NID foreignNidReg CDFIM csfbRegParam1 Common
roamer xRtt
registration
indicator
CDMA2000 1xRTT SID foreignSidReg CDFIM csfbRegParam1 Common
roamer xRtt
registration
indicator
CDMA2000 1xRTT homeReg CDFIM csfbRegParam1 Common
home registration xRtt
indicator
CDMA2000 1xRTT multiNid CDFIM csfbRegParam1 Common
multiple NID xRtt
storage indicator
CDMA2000 1xRTT multiSid CDFIM csfbRegParam1 Common
multiple SID xRtt
storage indicator
CDMA2000 1xRTT nid CDFIM csfbRegParam1 Common
network xRtt
identification
CDMA2000 1xRTT paramReg CDFIM csfbRegParam1 Common
parameter-change xRtt

Features

name object
registration
indicator
CDMA2000 1xRTT powerDownReg CDFIM csfbRegParam1 Common
power-down xRtt
registration
indicator
CDMA2000 1xRTT powerUpReg CDFIM csfbRegParam1 Common
power-up xRtt
registration
indicator
CDMA2000 1xRTT regPeriod CDFIM csfbRegParam1 Common
registration xRtt
period
CDMA2000 1xRTT regZone CDFIM csfbRegParam1 Common
registration zone xRtt
CDMA2000 1xRTT sid CDFIM csfbRegParam1 Common
system xRtt
identification
CDMA2000 1xRTT totalZone CDFIM csfbRegParam1 Common
number of xRtt
registration zones
CDMA2000 1xRTT zoneTimer CDFIM csfbRegParam1 Common
zone timer length xRtt
CDMA2000 HRPD hrpdNCList CDFIM - Common
neighbor cell list
CDMA2000 HRPD hrpdArfcn CDFIM hrpdNCList Common
frequency
CDMA2000 HRPD band hrpdBdClNcl CDFIM hrpdNCList Common
class
CDMA2000 HRPD hrpdCellId CDFIM hrpdNCList Common
physical cell
identity
CDMA2000 HRPD NCL hrpdExSel CDFIM hrpdNCList Common
extension selector
CDMA2000 1xRTT rttNCList CDFIM - Common
neighbor cell list
CDMA2000 1xRTT rttArfcn CDFIM rttNCList Common
frequency
CDMA2000 1xRTT rttBdClNcl CDFIM rttNCList Common
band class (NCL)
CDMA2000 1xRTT rttCellId CDFIM rttNCList Common
physical cell
identity
CDMA2000 1xRTT NCL rttExSel CDFIM rttNCList Common
extension selector
Neighbor 1x arfcn LNADJX - Common
carrier frequency

Features

name object
Neighbor 1x band bandClass LNADJX - Common
class
Activate 1xCSFB act1xCsfb LNBTS - Common
Activate handover actHOtoWcdma LNBTS - Common
from LTE to WCDMA
Activate UE-based actUeBasedAnr LNBTS - Common
ANR for UTRAN Utran
Activate eNACC to acteNACCtoGSM LNBTS - Common
GSM
Activate support actConvVoice LNBTS - Common
of conversational
voice bearer
Activate handover actHOtoHrpd LNBTS - Common
from LTE to eHRPD
Activate handover actHOtoTdscdm LNBTS_FD - FDD
from LTE to TD- a D
SCDMA
Activate handover actHOtoTdscdm LNBTS_TD - TDD
from LTE to TD- a D
SCDMA
Time to trigger a1TimeToTrigg LNCEL - Common
for A1 to erDeactInterM
deactivate inter eas
measurement
CDMA2000 timers c2KTimers LNCEL - Common
CDMA2000 1xRTT tC2KMeasRepor LNCEL c2KTimers Common
measurement report t
timer
CDMA2000 tC2KRelocPrep LNCEL c2KTimers Common
relocation
preparation timer
CDMA2000 tC2kRelocExec LNCEL c2KTimers Common
relocation
execution timer
UL Handover tULHOPrepTran LNCEL c2KTimers Common
preparation sfer
transfer timer
Random challenge rand LNCEL - Common
value
CDMA2000 1xRTT rttCellIdInfo LNCEL - Common
cell ID info
CDMA2000 1xRTT rttCsfbType LNCEL - Common
CSFB type
Threshold th2a for threshold2a LNCEL - Common
RSRP

Features

name object
Threshold th4 for threshold4 LNCEL - Common
RSRP
System information sibScheduling SIB - Common
scheduling list List
Periodicity siMessagePeri SIB sibScheduling Common
odicity List
Repetition siMessageRepe SIB sibScheduling Common
tition List
SIB type siMessageSibT SIB sibScheduling Common
ype List
Threshold1 b2Threshold1H LNHOH - Common
CDMA2000-HRPD for rpd
RSRP of serving
Cell
CDMA2000 1XRTT rttCarrierFre LNHOX - Common
carrier frequency q
CDMA2000 1XRTT rttArfcn LNHOX rttCarrierFre Common
ARFCN q
CDMA2000 1XRTT rttBandClass LNHOX rttCarrierFre Common
band class q
Neighbor 1x arfcn LNRELX - Common
carrier frequency
Neighbor 1x band bandClass LNRELX - Common
class
Local time offset ltmOff XPARAM - Common
CDMA2000 1xRTT xparamId XPARAM - Common
mobility
parameters
identifier
CDMA2000 1xRTT auth XPARAM - Common
auth mode
indicator
CDMA2000 1xRTT authIncluded XPARAM - Common
auth mode
indicator included
CDMA2000 1xRTT bandClass XPARAM - Common
band class
Day light savings dayLt XPARAM - Common
time indicator
Include day light dayLtIncluded XPARAM - Common
savings time
indicator
FPC FCH INIT SETPT fpcFchInitSet XPARAM - Common
for RC11 ptRC11
for RC12 ptRC12

Features

name object
for RC3 ptRC3
for RC4 ptRC4
FPC FCH INITSETPT fpcFchInitSet XPARAM - Common
for RC5 ptRC5
GCSNAL2Ack timer gcsnaL2AckTim XPARAM - Common
indicator er
GCSNA sequence gcsnaSequence XPARAM - Common
context timer ContextTimer
indicator
CDMA2000 1xRTT homeRegInclud XPARAM - Common
home registration ed
included
IMSI 11th and 12th imsi11and12 XPARAM - Common
digit
IMSI T supported imsiTSupporte XPARAM - Common
d
Leap second lpSec XPARAM - Common
Leap seconds lpSecIncluded XPARAM - Common
included
Local time offset ltmOffInclude XPARAM - Common
included d
CDMA2000 1xRTT max maxNumAltSo XPARAM - Common
number of alt SO
Mobile country mcc XPARAM - Common
code
CDMA2000 1xRTT minPRev XPARAM - Common
minimum protocol
revision
1x protocol pRev XPARAM - Common
revision
Pilot increment pilotInc XPARAM - Common
Pilot increment pilotIncInclu XPARAM - Common
included ded
Preferred mobile prefMSIDType XPARAM - Common
station identifier
type
Sales information

Features

element
ASW SW asset monitoring No
3.3 Activating and configuring LTE738: SRVCC to

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

1xRTT/CDMA
object locking
Activate SRVCC to CDMA/1xRTT activation flag no
(act1xSrvcc)
CDMA2000 SRVCC to 1xRTT optional configuration no
measurement configuration
(measConfigSrvccRtt) parameter
structure
Single radio voice call continuity optional configuration no
allowed (srvccAllowed), LNRELX
CDMA2000 1XRTT carrier mandatory configuration no
frequency (rttCarrierFreq)
Neighbor 1x carrier frequency optional configuration no
(arfcn)
Neighbor 1x band class optional configuration no
(bandClass)
CDMA2000 timers (c2KTimers) mandatory configuration no
parameter structure
Threshold 2 config for CDMA2000 mandatory configuration no
HRPD and 1xRTT
(threshold2C2kConfig) parameter
structure
Random challenge value (rand) mandatory configuration no
CDMA2000 1xRTT cell ID info optional configuration no
(rttCellIdInfo)
CDMA2000 1xRTT reference cell mandatory configuration no
id (rttRefCellId) parameter
structure
Time to trigger for A1 to deactivate optional configuration no
inter measurement
(a1TimeToTriggerDeact InterMeas)

Features

1xRTT/CDMA (Cont.)
object locking
System information scheduling list mandatory configuration no
(sibSchedulingList)
Threshold th2a for RSRP optional configuration no
(threshold2a)
Threshold th4 for RSRP optional configuration no
(threshold4)
Local time offset (ltmOff) mandatory configuration no
CDMA2000 1xRTT CSFB optional configuration no
registration parameters
(csfbRegParam1xRtt) parameter
structure
Neighbor 1x carrier frequency optional configuration no
(arfcn)
Neighbor 1x band class optional configuration no
(bandClass)
The following features need to be activated before the activation of the LTE738: SRVCC
to 1xRTT/CDMA feature:

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

• LTE442: Network Assisted Cell Change to GSM
• LTE898: TDD Inter-RAT Handover to TD-SCDMA
• LTE873: SRVCC to GSM
• LTE908: ANR Inter-RAT UTRAN - Fully UE-based
Procedure

2 Activate the LTE738: SRVCC to 1xRTT/CDMA feature.


Features

you need to select the LNBTS/LNBTS_FDD for FDD object or
LNBTS/LNBTS_TDD for TDD object.
d) Set the Activate SRVCC to CDMA/1xRTT (act1xSrvcc) parameter's
value to true.
3 Configure the LNHOX parameters.

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

c) Right-click the LNCEL object and select the New LNRELX object.
d) For the LNRELX object, set the parameter values.
e) For the 1x neighbor cells supporting 1xSRVCC, set the srvccAllowed
LNRELX parameter's value to true.
5 Configure the LNCEL parameter structures.

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

Features
6 Configure the Random challenge value and CDMA2000 1xRTT cell ID info
LNCEL parameters.

c) Set the Random challenge value (rand) and CDMA2000 1xRTT cell
ID info (rttCellIdInfo) parameters' values.
7 Configure the other LNCEL parameters (optional).

c) Set the parameter values.
8 Configure the XPARAM parameters.

c) Right-click the LNCEL object and select the New XPARAM object.
d) For the XPARAM object, set all the parameters' values.
9 Configure the SIB8.

c) Select the SIB object.
d) For the System information scheduling
list (sibSchedulingList) parameter structure, add SIB8.
10 Configure the CDMA2000 1xRTT CSFB registration parameters parameters'

structure.

b) Right-click the LNCEL object and select the New CDFIM object.
c) Right-click the CDFIM object and select the New CDMA2000 1xRTT CSFB
registration parameters.
d) For the selected structure, set the parameter values.
11 Configure the Network synchronization mode BTSSCL parameter.
a) Right-click the MRBTS object.

Features
b) Select the New ► BTSSCL object.

c) Set the Network synchronization mode (btsSyncMode) parameter's
value to equal the PhaseSync.
Expected outcome
The LTE738: SRVCC to 1xRTT/CDMA feature is activated.
3.4 Deactivating LTE738: SRVCC to 1xRTT/CDMA

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

2 Deactivate the LTE738: SRVCC to 1xRTT/CDMA feature.


d) Set the Activate SRVCC to CDMA/1xRTT (act1xSrvcc) parameter's
value to false.
Expected outcome
The LTE738: SRVCC to 1xRTT/CDMA feature is deactivated.

LTE825: Uplink Outer Region Scheduliing LTE15A Radio Resource Management and Telecom
Features
4 LTE825: Uplink Outer Region Scheduliing
4.1 Description of LTE825: Uplink Outer Region

Scheduling
Table 23 LTE825 summary of changes
Date of change Section Change description
25.05.2017 Functional description The following sentence has been deleted: "The
automatic SRS configuration is done even if the
LTE786: Flexible UL Bandwidth and LTE825:
UL Outer Region Scheduling features are
deactivated."

The LTE825: Uplink Outer Region Scheduling feature increases the number of physical
resource blocks (PRBs) available for data allocation in uplink (UL). For this purpose, this
feature allows using the blanked outer region for the physical uplink shared channel
(PUSCH). In addition, it enables the scheduling of the physical random access channel
(PRACH) in the outer region.
Benefits
End-user benefits
This feature does not affect the end-user experience.
Operator benefits
• PRBs in one of the blanked physical uplink control channel (PUCCH) regions for
PUSCH and PRACH
• more efficient exploitation of the available UL spectrum
• the RAN configuration flexibility and simplicity
Requirements
Functional overview
The implementation of the LTE825: Uplink Outer Region Scheduling feature is
inseparably connected with the LTE786: Flexible UL Bandwidth feature. The latter aims
at reducing the UL bandwidth below the nominal system bandwidth. The bandwidth is
reduced symmetrically on both edges of the UL spectrum by leaving the outmost PRBs
unused. In order to improve the feature's functionality (for example, to reduce the UL
bandwidth in an asymmetrical way or to enable an automatic SRS configuration), the
LTE825: Uplink Outer Region Scheduling feature enhances its previous counterpart;
therefore, it can be perceived as an addition to the already existing one.

LTE15A Radio Resource Management and Telecom LTE825: Uplink Outer Region Scheduliing
Features
The LTE825: Uplink Outer Region Scheduling feature is supported by >3MHz system
bandwidths. It enables the eNB to allocate the PUSCH and PRACH resources in one
blanked PUCCH edge. The set of PUSCH PRBs in the blanked PUCCH edge is called
an outer PUSCH region. The minimum recommended outer region's size is three PRBs.
The PRACH can be placed in the outer PUSCH region when six or more consecutive
PRBs are available. It ensures that the RAN configuration is more flexibile.
In addition, this feature enables the eNB to utilize additional UL resources for the
PUSCH scheduling (see ). This feature provides a method for setting up the PUSCH and
PRACH in the blanked non-disturbed outer UL spectrum, and allows the allocation of
unused PRBs for the outer region scheduling. An O&M parameter defines which one of
the outer regions is permitted for PUSCH scheduling and which one of the two blanked
PUCCH regions is added.
Figure 2 The comparison of LTE786: Flexible UL Bandwidth and LTE825: UL Outer

Region Scheduling features
Nominalsystem LTE786:Flexible LTE825:UL Outer
bandwith UL Bandwidth RegionScheduling
PUSCH
blanked (outerregion)
PUCCH
PUCCH PUCCH
PUSCH PUSCH PRACH

PUSCH (eitheror)
and and (innerregion)
PRACH PRACH
PUCCH PUCCH
PUCCH
blanked blanked
• activationinoneouterregion
• toavoidinterference
• asymmetricalbandwidth
• bothbandedgesblanked
reductionpossible
Depending on the number of PRBs which are assigned to the inner PUSCH region, the
eNB selects a proper sounding reference signal (SRS) configuration. The SRS
configuration is selected out of a set of predefined SRS configurations. The selected
SRS configuration is one with the largest SRS bandwidth that does not overlap the outer
PUSCH region or the blanked PUCCH edges. Instead, it can overlap the used PUCCH
PRBs. This method simplifies the RAN configuration. For the configuration of the outer
scheduling region, the same RRM algorithms for power control (OLPC, CLPC, or
IawPC), link adaptation (slowAMC, eULA, or fULA – fULA without the support of SRS in
the outer region), and the same scheduling algorithms (CUS, IAS, or CAS – CAS without
the support of SRS in the outer region) are applied.
Automatic SRS configuration
In the LTE825: UL Outer Region Scheduling feature, the sounding configuration is
chosen automatically, depending on the number of PUSCH PRBs assigned to the inner
scheduling region. The eNB selects the SRS configuration from a set of predefined

Features
configurations in such a way that the sounding in the blanked PUCCH, or rather in the
outer PUSCH region, is prevented. It also covers the inner PUSCH region as much as
possible. The coexistence of sounding resources and PUCCH is allowed.
System impact
There are interdependencies between the following features:
• LTE786: Flexible UL Bandwidth

The size of the blanked outer region which can be utilized for PUSCH and PRACH is
defined by the LTE786: Flexible UL Bandwidth feature. The size of the configured
outer PUSCH region is blankedPucch/2.
The LTE825: Uplink Outer Region Scheduling feature impacts the Uu interface in such a
way that a second PUSCH region is additionally assigned to the already existing PUSCH
region around the central frequency.


This feature impacts system performance and capacity as follows:
• The RAN-level system capacity increases in direct proportion to the number of

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

LTE825: Uplink outer region scheduling requirements, alarms and faults, commands,
Requirements

Features

FDD TDD
System release FDD-LTE 15A Not supported
Flexi Multiradio 10 BTS FL15A Not supported
Flexi Multiradio 10 Indoor BTS Not supported Not supported
Nokia AirScale BTS FL16A Not supported
Flexi Zone BTS FL15A Not supported
Flexi Zone Access Point FL16 Not supported
Cloud Flexi Zone Controller FL17A Not supported
NetAct NetAct 15.5 Not supported
SAE GW 3GPP R8 mandatory Not supported
UE Not supported Not supported
Alarms
There are no alarms related to the LTE825: Uplink outer region scheduling feature.

There are no faults related to the feature.
Commands
There are no commands related to the LTE825: Uplink outer region scheduling feature.
Table 25 Counters modified by LTE825

M8011C50 PRB used PUSCH LTE Cell Resource
M8011C22 UL PRB utilization per TTI Min LTE Cell Resource
M8011C23 UL PRB utilization per TTI Max LTE Cell Resource
M8011C24 UL PRB utilization per TTI Mean LTE Cell Resource
M8011C12 UL PRB utilization per TTI Level 1 LTE Cell Resource

Features
Table 25 Counters modified by LTE825 (Cont.)

M8005C231 Minimum of cell-wide RSSI on PUSCH LTE Power and Quality UL
M8005C232 Maximum of cell-wide RSSI on PUSCH LTE Power and Quality UL
M8005C233 Mean of cell-wide RSSI on PUSCH LTE Power and Quality UL
M8005C234 Cell-wide RSSI on PUSCH level 1 LTE Power and Quality UL
M8005C281 Minimum of cell-wide SINR on PUSCH LTE Power and Quality UL
M8005C282 Maximum of cell-wide SINR on PUSCH LTE Power and Quality UL
M8005C283 Mean of cell-wide SINR on PUSCH LTE Power and Quality UL
M8005C284 Cell-wide SINR on PUSCH level 1 LTE Power and Quality UL

Features

M8011C47 PRB used UL total LTE Cell Resource
M8011C49 PRB used PUCCH LTE Cell Resource
M8011C50 PRB used PUSCH LTE Cell Resource
M8011C51 PRB used DL total LTE Cell Resource
M8011C54 PRB used PDSCH LTE Cell Resource


There are no key performance indicators related to the LTE825: Uplink outer region
scheduling feature.
Parameters

name object
Target UL outer selectOuterPu LNCEL _ FDD
scheduling region schRegion _FDD/_TDD
SRS feature srsActivation LNCEL _ FDD
activation/deactiv _FDD/_TDD
ation

Features

name object
Activate PUSCH actPuschMask LNCEL _ FDD
masking _FDD/_TDD
Activate uplink actUlLnkAdp LNCEL _ FDD
link adaptation
Blanked PUCCH blankedPucch LNCEL _ FDD
resources _FDD/_TDD
PRACH frequency prachFreqOff LNCEL _ FDD
offset _FDD/_TDD
Power offset for srsPwrOffset LNCEL _ FDD
SRS transmission _FDD/_TDD
power calculation
Uplink channel ulChBw LNCEL _ FDD
bandwidth _FDD/_TDD
Scheduling method ulsSchedMetho LNCEL _ FDD
of the UL d
scheduler
Sales information

element
4.3 Activating and configuring LTE825: Uplink Outer

Region Scheduling
Before you start
Table 29: Parameters used for activating and configuring LTE825: Uplink Outer Region
Scheduling lists parameters used for the activation and configuration of the LTE825:
Uplink Outer Region Scheduling feature.
Region Scheduling
object locking
Target UL outer scheduling region activation flag restart
(selectOuterPuschRegi on)
Blanked PUCCH resources mandatory configuration object locking
(blankedPucch)

Features
Region Scheduling (Cont.)
object locking
PRACH frequency offset mandatory configuration restart
(prachFreqOff)
PUCCH bandwidth for CQI mandatory configuration object locking
(nCqiRb)
The LTE786: Flexible UL Bandwidth feature needs to be activated and configured before
activating the LTE825: Uplink Outer Region Scheduling feature.
Procedure

2 Configure the PUCCH bandwidth for CQI (nCqiRb) parameter.

d) Select the LNCEL object.

you need to select the LNCEL_FDD/MPUCCH_FDD for FDD object or
LNCEL_TDD/MPUCCH_TDD for TDD object.
e) Configure the PUCCH bandwidth for CQI (nCqiRb) parameter.
3 Configure the Blanked PUCCH resources (blankedPucch) parameter.
a) Expand the LNCEL object

.
b) Set the Blanked PUCCH resources (blankedPucch) parameter to the
following values:
• 12 or higher for PRACH scheduling in the outer scheduling region
• 6 or higher for PUSCH scheduling in the outer scheduling region

Features
g Note: PUSCH scheduling is also permitted in case

Blanked PUCCH resources (blankedPucch) = 12
4 Activate the LTE825: Uplink Outer Region Scheduling feature.

b) Set the Target UL outer scheduling
region (selectOuterPuschRegion) parameter's value to UpperEdge or
LowerEdge.
g Note: Target UL outer scheduling

region (selectOuterPuschRegion) can only be set to UpperEdge or
LowerEdge if Uplink channel bandwith (ulChBw) is higher or equal to 5
MHz.
5 Set the PRACH frequency offset (prachFreqOff) parameter's value (if the
LNCEL Target UL outer scheduling region (selectOuterPuschRegion)
parameter is set to LowerEdge and the LNCEL Blanked PUCCH
resources (blankedPucch) parameter is higher or equal 12).

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

Features
g Note: PRACH has to be placed either in the outer PUSCH region or in the inner
region at a place where the calculation rule is specified. The permitted range for
PRACH frequency offset (prachFreqOff) is produced by a calculation
formula:
• from the lower limit: 0 to the upper limit: roundup (
Blanked PUCCH resources (blankedPucch) / 2 - 6, and
• from the lower limit: roundup (LNCEL Maximum PUCCH resource
size(MaxPucchResourceSize) + (blankedPucch) / 2) to the upper
limit: LNCEL Uplink channel bandwith (ulChBw) (in PRBs) - 6 -
roundup (MaxPucchResourceSize + blankedPucch) / 2)
Note: From release LTE17 onwards, due to a change in the MO architecture,

g you need to select the LNCEL/LNCEL_FDD for FDD object or
The above parameters must be configured so that the lower limit is always below
or equal to the upper limit of the permitted range. This is not enforced by the SW
but needs to be followed during the configuration.
g Note: LNCEL Maximum PUCCH resource

size (MaxPucchResourceSize) is a calculated value that is computed by
means of other O&M parameters. MaxPucchResourceSize is utilized to
determine the correct offset allocation of the PRACH resources and to verify that
the maximal allowed number of PUCCH resources per BW is not exceeded.
MaxPucchResourceSize is produced by a calculation formula:
• MaxPucchResourceSize = nCqiRb + roundup {[((rounddown
(((maxNrSymPdcch*12 - X)*dlChBw - roundup (phichRes*(dlChBw /
8))*12 - 16) / 36)) + n1PucchAn - pucchNAnCs*3 / deltaPucchShift)
*deltaPucchShift] / (3*12)} + roundup (pucchNAnCs / 8) –
blankedPucch, where:
– X = 4, when maxNrSymPdcch = 1 or dlMimoMode set to SingleTX,
TXDiv, Dynamic Open Loop MIMO or Closed Loop Mimo
– X = 8, when maxNrSymPdcch > 1 and dlMimoMode set to
4-way TXDiv or Closed Loop MIMO (4x2)
6 Set the PRACH frequency offset (prachFreqOff) parameter's value (if the
LNCEL Target UL outer scheduling region (selectOuterPuschRegion)
parameter is set to UpperEdge and the LNCEL Blanked PUCCH
resources (blankedPucch) parameter is higher or equal 12).

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

Features
g Note: PRACH has to be placed either in outer PUSCH region or in the inner
region at a place where the calculation rule is specified. The permitted range for
LNCEL: PRACH frequency offset (prachFreqOff) is produced by a
calculation formula:
• from the lower limit: roundup (
LNCEL: Maximum PUCCH resource
size (MaxPucchResourceSize) +
LNCEL: Blanked PUCCH resources (blankedPucch) / 2) to the
upper limit: LNCEL: Uplink channel bandwith (ulChBw) in PRBs - 6
- roundup (MaxPucchResourceSize + blankedPucch) / 2, and

• from the lower limit: LNCEL: Uplink channel bandwith (ulChBw) in
PRBs - roundup (blankedPuccch/2) to the upper limit: ulChBw (in PRBs) -
6

g Note: LNCEL Maximum PUCCH resource

size (MaxPucchResourceSize) is a calculated value that is computed by
means of other O&M parameters. MaxPucchResourceSize is utilized to
determine the correct offset allocation of the PRACH resources and to verify that
the maximal allowed number of PUCCH resources per BW is not exceeded.
MaxPucchResourceSize is produced by a calculation formula:
• MaxPucchResourceSize = nCqiRb + roundup {[((rounddown
(((maxNrSymPdcch*12 – X)*dlChBw - roundup (phichRes*(dlChBw /
8))*12 - 16) / 36)) + n1PucchAn - pucchNAnCs*3 / deltaPucchShift)
*deltaPucchShift] / (3*12)} + roundup (pucchNAnCs / 8) -
blankedPucch, where:
– X = 4, when maxNrSymPdcch = 1 or dlMimoMode set to SingleTX,
TXDiv, Dynamic Open Loop MIMO or Closed Loop Mimo
– X = 8, when maxNrSymPdcch > 1 and dlMimoMode set to
4-way TXDiv or Closed Loop MIMO (4x2)
Expected outcome
The LTE825: Uplink Outer Region Scheduling feature is activated; PUSCH and PRACH
scheduling in the outer scheduling area is possible.

Features
4.4 Deactivating LTE825: Uplink Outer Region

Scheduling
Before you start
The Target UL outer scheduling region (selectOuterPuschRegion)
parameter is used for deactivation. Modification of this parameter requires an eNB
restart.
Procedure

2 Deactivate the Target UL outer scheduling

region (selectOuterPuschRegion) parameter.

c) Select the LNCEL object.

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

Features
g Note: If selectOuterPuschRegion is configured to None or

blankedPucch is less than 12, then the permitted range for prachFreqOffis
produced by a calculation formula:
• from the lower limit: roundup
LNCEL: Maximum PUCCH resource
size (MaxPucchResourceSize)+
LNCEL: Blanked PUCCH resources (blankedPucch) / 2) to the
upper limit: LNCEL: Uplink channel bandwith (ulChBw) (in PRBs) -
6 - roundup LNCEL: Maximum PUCCH resource
size (MaxPucchResourceSize) +
LNCEL: Blanked PUCCH resources (blankedPucch) / 2)
Expected outcome
The LTE825: Uplink Outer Region Scheduling feature is deactivated.

LTE15A Radio Resource Management and Telecom LTE951: Enhanced Cell ID Location Service
Features
5 LTE951: Enhanced Cell ID Location Service
5.1 Description of LTE951: Enhanced Cell ID Location

Service
The LTE951: Enhanced Cell ID Location Service feature improves location reporting by
introducing enhanced cell ID reporting (E-CID) to the E-Serving Mobile Location Center
(E-SMLC).
Benefits
End-user benefits
This feature:
• enables determining UE position in case of emergency calls

• enables using applications requesting UE positioning (for example maps, etc.)
Operator benefits
This feature allows the operator to turn the location services in a cell on and off.
Functional overview
The LTE951: Enhanced Cell ID Location Service feature introduces enhanced cell ID (E-
CID) location services.
The location service is performed in two steps:
1. The UE is positioned based on its serving cell's ID.

2. The UE is positioned more accurately inside a single cell, using one of the following
four methods:
• Timing advance type 1
• Timing advance type 2
• Intra-frequency Reference Signal Received Power (RSRP) and/or Reference
Signal Received Quality (RSRQ)
• Angle of arrival
g Note: The Angle of arrival is TDD specific only.
In a location measurement procedure, information about the position of a UE is

transmitted from an eNodeB to E-SMLC in the LTE Positioning Protocol A (LPPa) LPPA:
E-CID MEASUREMENT INITIATION RESPONSE message, which is encapsulated
within the S1AP: UPLINK UE ASSOCIATED LPPA TRANSPORT message.
Only on-demand measurements are supported by an eNB. The eNB can perform
multiple measurements simultaneously.

LTE951: Enhanced Cell ID Location Service LTE15A Radio Resource Management and Telecom
Features
Providing a measurement request is received by an eNB while performing a handover of

a UE, the failure response is sent back to the E-SMLC.
When employing the LTE951: Enhanced Cell ID Location Service feature in cells with
spatially separated antennas (for example a super cell), the measurements provided by
LTE951: Enhanced Cell ID Location Service cannot be referenced to a single antenna as
they do not have a well-defined reference point. Whether to use the LTE951: Enhanced
Cell ID Location Service feature with separated antennas and an unclear reference point
is left for the operator to decide.
When deploying the feature, there are two scenarios for an operator to consider:
• not to configure an E-UTRAN access point information in the eNodeB. The eNodeB
will then not report the E-UTRAN access point information to the E-SMLC, and it is
assumed that the E-SMLC will cope with this (the E-UTRAN access point information
element (IE) is optional in the E-CID measurement result).
• define the E-UTRAN access point position as a geographical mean value of the
antenna positions (logical antenna position). Use the uncertaintyAltitude,
uncertaintySemiMajor, and uncertaintySemiMinor attributes of the
eutranAccessPointPosition configuration parameter to express the
geographical inaccuracy of this logical antenna position.
Measurement types
Timing advance type 2 (TA type 2)

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

This approach measures the following two timing differences:
• the time difference between the reception of a downlink radio frame #i and the
transmission of a corresponding uplink radio frame #i, measured by the UE (UE Rx-
Tx time difference)
• the time difference between the reception of an uplink radio frame #i and the
transmission of a downlink radio frame #i at the eNB (eNB Rx-Tx time difference)
The measurement is conducted only after an E-SMLC request. After receiving such a
request, an eNB instructs a UE to perform the UE Rx-Tx measurements.
After receiving a UE Rx-Tx measurement from the UE, the eNB computes the Timing
advance type 1 and sends it to the E-SMLC.
Before performing the Timing advance type 1 procedure, the E-SMLC verifies the UE's
capability to perform measurements via an LPP protocol.
The reference point used by an eNB to perform the measurements is the antenna
connector.
Intra-frequency Reference Signal Received Power (RSRP) and/or Reference Signal

Received Quality (RSRQ)

Features
These measurements are performed by a UE and reported to an eNB. When a request

for the RSRP, or RSRQ, or both of them arrives at an eNB, the eNB initiates an intra-
frequency measurement configuration at the UE with a reportStrongestCells purpose.
The exact type of this measurement is set by the value of triggerQuantity. Subject to a
desired measurement, its value is set either to RSRP (in case the RSRP or both
measurements are requested), or RSRQ (in case only this measurement is needed).
The UE sends a measurement report to the eNodeB, which in turn sends the RSRP
and/or RSRQ measurements to the E-SMLC, which calculates the UE's position.
Angle of arrival (AoA)

This measurement provides a UE direction relative to the northern direction measured
clockwise.
For a proper measurement, the eNB requires theAntenna Bearing for AoA
calculation (antBearingForAoaCalc) parameter . The scale for the AoA
measurement is from 0 to 360 degree, with a resolution of 0,5 degrees. Also, the
Antenna Element Spacing for AoA Calculation (antElementSpacing)
LNCEL parameter needs to be configurated to the an appropriate value, according to the
operator's antenna hardware configuration.
The Angle of arrival measurement is impacted by radio propagation conditions. In case
of a non-line-of-sight propagation, the angle of arrival measurement will correspond to a
multi-path scattered component and not necessarily coincide with the physical direction
of a UE seen from the eNB.
System impact
The following features are prerequisite for the LTE951: Enhanced Cell ID Location
Service feature:
• LTE513: Suppport of Sounding Reference Signal in TDD UpPTS

• LTE540: Sounding Reference Signal in Normal Frames
g Note: During an activation procedure, a consistency check is not performed, and this
prerequisite is ignored. The LTE951: Enhanced Cell ID Location Service feature can be
activated without the LTE513: Suppport of Sounding Reference Signal in TDD UpPTS
and LTE540: Sounding Reference Signal in Normal Frames features, nevertheless, it
will not work properly.
g Note: The prerequisites above are required in case TDD only.
The following features are interrelated with the LTE951: Enhanced Cell ID Location
Service feature:
• LTE433: Cell Trace

The feature enables operators to simultaneously trace all UEs that are in an
RRC_CONNECTED state in a target cell.
• LTE644: Configurable Cell Trace Content
The feature allows operators to select a message type, based on which the UEs that
are in an RRC_CONNECTED state are filtered and traced in a target cell.
• LTE163: Subscriber and Equipment Trace
The feature enables operators to trace a specific IMSI or IMEI.

Features
• LTE782: ANR Fully UE-based

Providing the LTE782: ANR Fully UE-based and LTE951: Enhanced Cell ID Location
Service features are enabled, the location service measurement request takes higher
priority than an ANR measurement.
• LTE1501: Measurement Report (MR) Addition to Cell Trace
If the LTE1501: Measurement Report (MR) Addition to Cell Trace and LTE951:
Enhanced Cell ID Location Service features are enabled, the location service
measurement request takes higher priority over the measurement requested by the
LTE1501: Measurement Report (MR) Addition to Cell Trace feature.
The LTE951: Enhanced Cell ID Location Service feature adds support to the E-CID
measurement initiation procedure. This procedure utilizes the UL/DL LPPa messages to
convey the E-CID measurement messages between an eNB and E-SMLC.
This feature impacts the following interfaces:
• The following new messages are added to an S1AP interface for LPPa PDU
transport:
– S1AP: DOWNLINK UE ASSOCIATED LPPA TRANSPORT
– S1AP: UPLINK UE ASSOCIATED LPPA TRANSPORT
• The following new messages are supported for an E-CID measurement:

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



LTE951: Enhanced Cell ID Location Service requirements, alarms and faults,
commands, measurements and counters, KPIs, parameters, and sales information
Requirements

FDD TDD
Flexi Multiradio 10 Indoor BTS FL15A TL15A

Features
Table 30 LTE951 hardware and software requirements (Cont.)

FDD TDD
OMS support not required support not required
MME support not required support not required
SAE GW support not required support not required
UE 3GPP R9 3GPP R9
g Note: For Timing advance (TA) type1, a UE should support the UE Rx-Tx time
difference measurement capability.
Additional hardware requirements

Providing the operator's network contains a mobility management entity (MME) and
ESMLC provided by other vendors, it is assumed that these network elements support
the LPPa messaging for E-CID before the LTE951: Enhanced Cell ID Location Service
feature is deployed. It is also assumed that any timers on the MME and E-SMLC (that
are preventing message response timeouts) can be adjusted as they are needed to
ensure successful inter-operability with an eNB.
The Angle of Arrival (AoA) measurement can only be performed in the Flexi Multiradio 10
BTS with 8Tx 8Rx configuration.
Alarms
There are no alarms related to the LTE951: Enhanced Cell ID Location Service feature.

Table 31 New counters introduced by LTE951 feature
M8000C43 Number of downlink UE LTE S1AP
associated LPPa transport
messages with E-CID
measurement initiation request
per eNB
M8000C44 Number of uplink UE LTE S1AP
messages with E-CID
measurement initiation
response per eNB
messages with E-CID
response with cause

Features
Table 31 New counters introduced by LTE951 feature (Cont.)

"Requested Item not
Supported" per eNB
messages with E-CID
response with cause
"Requested Item Temporarily
not Available" per eNB
For counter descriptions, see LTE Radio Access Operating Documentation/

Reference/Counters.

There are no key performance indicators related to this feature.
Parameters
Table 32 New parameters related to the LTE951 feature

Full name Abbreviated Managed object Structure FDD/TDD
name
Activate LPPa actLPPaEcid LNBTS - common
enhanced cell ID
location service
Antenna Element antElementSpaci LNCEL - TDD
Spacing for AoA ng
Calculation
Periodical perMeasLocServ LNCEL - common
measurements
for location
services
Report interval reportIntervalPerL LNCEL perMeasLocServ common
periodical meas oc
for location
Report amount reportAmountPer LNCEL perMeasLocServ common
periodical meas Loc
for location
Overall ecidMeasSupervi LNCEL - common
supervision timer sionTimer
for ECID
measurements
Table 33 Existing parameters related to the LTE951 feature

Full name Abbreviated name Managed object FDD/TDD
Downlink sector dlSectorBFWeightCus LNBTS TDD
beamforming weight Prof
customized profile

Features
Table 33 Existing parameters related to the LTE951 feature (Cont.)

Antenna element antennaElementSpaci LNBTS TDD
spacing ng
Downlink sector dlSectorBFWeightProf LNBTS TDD
beamforming weight Name
profile name
Modulus of weight for modulusOfWeighforAn LNBTS TDD
antenna group 0 tGrp0
Phase of weight for phaseOfWeighforAntG LNBTS TDD
antenna group 0 rp0
antenna group 1 rp1
antenna group 2 rp2
antenna group 3 rp3
Antenna bearing for antBearingForAoaCalc LNCEL TDD
AoA calculation
E-UTRAN access eutranAccessPointPos LNCEL common
point position ition
Altitude altitude LNCEL common
Confidence confidence LNCEL common
Degrees of latitude degreesOfLatitude LNCEL common
Degrees of longitude degreesOfLongitude LNCEL common
Direction of altitude directionOfAltitude LNCEL common
Latitude sign latitudeSign LNCEL common
Orientation of major orientationOfMajorAxis LNCEL common
axis
Uncertainty altitude uncertaintyAltitude LNCEL common
Uncertainty semi- uncertaintySemiMajor LNCEL common
major
Uncertainty semi- uncertaintySemiMinor LNCEL common
minor
For parameter descriptions, see LTE Radio Access Operating Documentation/

Reference/Parameters.
Sales information

Features
Table 34 The LTE951 feature sales information

element
5.3 Activating and configuring LTE951: Enhanced Cell

ID Location Service
Before you start
Table 6 presents the parameters used for activating and configuring the LTE951:
Enhanced Cell ID Location Service feature.
Table 35 Parameters used for activating and configuring LTE951: Enhanced Cell ID
Location Service
Parameter Purpose Requires eNB FDD/TDD
restart or object
locking
Activate LPPa activation flag no common
enhanced cell ID
location
service (actLPPaEci
d)
E-UTRAN access mandatory in case no common
point geographical position
position (eutranAcc of the transmit
essPointPosition) antenna needs to be
supported
Altitude (altitude) Mandatory in case no common
the E-UTRAN
access point
position
(eutranAccessPo
intPosition)
structure is
configured
Confidence Mandatory in case no common
(confidence) the E-UTRAN
access point
position
(eutranAccessPo
intPosition)
structure is
configured
Degrees of Mandatory in case no common
latitude the E-UTRAN
(degreesOfLatitude) access point
position
(eutranAccessPo
intPosition)
structure is
configured

Features
Location Service (Cont.)
restart or object
locking
Direction of Mandatory in case no common
altitude the E-UTRAN
(directionOfAltitud access point
e) position
(eutranAccessPo
intPosition)
structure is
configured
Latitude Mandatory in case no common
sign (latitudeSign) the E-UTRAN
access point
position
(eutranAccessPo
intPosition)
structure is
configured
Degrees of Mandatory in case no common
longitude the E-UTRAN
(degreesOfLongitude access point
) position
(eutranAccessPo
intPosition)
structure is
configured
Orientation of Mandatory in case no common
major the E-UTRAN
axis (orientationOf access point
MajorAxis) position
(eutranAccessPo
intPosition)
structure is
configured
Uncertainty Mandatory in case no common
altitude the E-UTRAN
(uncertaintyAltitud access point
e) position
(eutranAccessPo
intPosition)
structure is
configured
Uncertainty semi- Mandatory in case no common
major the E-UTRAN
(uncertaintySemiMaj access point
or) position
(eutranAccessPo
intPosition)
structure is
configured
Uncertainty semi- Mandatory in case no common
minor the E-UTRAN
(uncertaintySemiMin access point
or) position
(eutranAccessPo

Features
Location Service (Cont.)
restart or object
locking
intPosition)
structure is
configured
Overall mandatory no common
supervision timer configuration
for ECID
measurements
(ecidMeasSupervisio
nTimer)
Periodical optional configuration no common
measurements for in case Intra-
location frequency Reference
services (perMeasLo Signal Received
cServ) Power (RSRP) and/or
Reference Signal
Received Quality
(RSRQ) is to be
supported
Report amount mandatory in case no common
periodical meas the Periodical
for measurements
location (reportAmo for location
untPerLoc) services
(perMeasLocServ)
structure is
configured
Report interval mandatory in case no common
periodical meas the Periodical
for measurements
location (reportInt for location
ervalPerLoc) services
(perMeasLocServ)
structure is
configured
Antenna Bearing mandatory in case of no TDD
for AoA Angle of arrival is to
calculation be requested
(antBearingForAoaCa
lc)
Antenna Element mandatory in case of no TDD
Spacing for AoA Angle of arrival is to
Calculation be requested
(antElementSpacing)
The Activate LPPa enhanced cell ID location

service (actLPPaEcid) LNBTS parameter is used for activation. Modification of this
parameter requires neither an eNB restart nor cell locking.
In case the Angle of arrival is to be supported, one of the following features need to be
activated/configured before activation of the LTE951: Enhanced Cell ID Location Service
feature:

Features
• LTE513: Suppport of Sounding Reference Signal in TDD UpPTS

• LTE540: Sounding Reference Signal in Normal Frames
The Angle of arrival is supported only on such software and hardware deployments that
support 8RX MIMO antenna configuration.
g Note: The feature parameters' configuration applies only to forthcoming requests. It

does not affect any ongoing or queued request procedures. The eNB takes the
configuration changes into account without affecting any service (without restarting).
Procedure
To activate the feature, do the following:

2 Activate the LTE951: Enhanced Cell ID Location Service feature.

d) Set the Activate LPPa enhanced cell ID location
service (actLPPaEcid) LNBTS parameter value to true.
3 Configure the Overall supervision timer for ECID

measurements (ecidMeasSupervisionTimer) LNCEL parameter.

c) Set the Overall supervision timer for ECID
measurements (ecidMeasSupervisionTimer) LNCEL parameter to an
appropriate value.
g Note: The
Overall supervision timer for ECID
measurements (ecidMeasSupervisionTimer) LNCEL parameter must be
configured in all LNCEL objects in one eNB.
4 If an eNB is to send the E-UTRAN access point position to E-SMLC, configure the E-
UTRAN access point position (eutranAccessPointPosition) object
(optional).

Features
b) Right-click the LNCEL object and, from the drop-down list, select New ► E-
UTRAN access point position object.
g Note: Perform the following step only if you executed the previous step.
5 Configure the E-UTRAN access point

position (eutranAccessPointPosition) structure.
a) Expand the LNCEL object.

b) Expand the E-UTRAN access point position.
c) Select the E-UTRAN access point position-1.
d) Configure the following parameters (mandatory):
• Altitude (altitude)
• Confidence (confidence)
• Degrees of latitude (degreesOfLatitude)
• Degrees of longitude (degreesOfLongitude)
• Direction of altitude (directionOfAltitude)
• Latitude sign (latitudeSign)
• Orientation of major axis (orientationOfMajorAxis)
• Uncertainty altitude (uncertaintyAltitude)
• Uncertainty semi-major (uncertaintySemiMajor)
• Uncertainty semi-minor (uncertaintySemiMinor)
6 To be able to provide the RSRP and/or RSRQ LPPa measurements, configure the RSRP
and RSRQ measurements (optional).

b) Right-click the LNCEL object and, from the drop-down list, select New ►
Periodical measurements for location services (perMeasLocServ) object.
g Note: Perform the following step only if you executed the previous step.
7 Configure the Periodical measurements for location

services (perMeasLocServ) LNCEL structure.
a) Expand the LNCEL object.

b) Expand the Periodical measurements for location services.
c) Select the Periodical measurements for location services-1.
d) Configure parameters in the structure to required values.

Features
g Note: When configuring the structure, remember that the value of the
Overall supervision timer for ECID
measurements (ecidMeasSupervisionTimer) LNCEL parameter must be
greater than Report amount periodical meas for
location (reportAmountPerLoc) multiplied by
Report interval periodical meas for
location (reportIntervalPerLoc).
You can start your configuration with the following values:
• Overall supervision timer for ECID
measurements (ecidMeasSupervisionTimer) set to 3000 ms.
• Report interval periodical meas for
location (reportIntervalPerLoc) set to 640 ms.
• Report amount periodical meas for
location (reportAmountPerLoc) set to 2.
8 If the eNB is to support sending Angle of arrival to the E-SMLC, configure the Antenna
Bearing for AoA calculation (antBearingForAoaCalc) parameter.

b) Set the Antenna Bearing for AoA
calculation (antBearingForAoaCalc) parameter to the proper value.
g Note: This step is required in case TDD only.
9 If the eNB is to support Angle of arrival, configure the Antenna Element Spacing
for AoA Calculation (antElementSpacing) parameter.

b) Set the Antenna Element Spacing for AoA
Calculation (antElementSpacing) parameter according to your current
antenna hardware configuration.
g Note: This step is required in case TDD only.
Expected outcome
• The eNB persistently stores all new and modified configuration data.
• The eNB informs NetAct and BTS Site Manager about the changed configuration via
configuration change notifications (CCNs).
• The eNB takes the configuration changes into account without affecting the service
(without restarting).

Features
• The LTE951: Enhanced Cell ID Location Service feature activation flag is set to true.
• The eNB reports E-CID measurements in the E-CID MEASUREMENT INITIATION
RESPONSE message when requested by the E-SMLC. The E-SMLC uses the E-
CID measurements to calculate the UE's location.
5.4 Deactivating LTE951: Enhanced Cell ID Location

Service
Before you start
The Activate LPPa enhanced cell ID location
service (actLPPaEcid) LNBTS parameter is used for deactivation. Modification of
this parameter requires neither an eNB restart nor cell locking.
g Note: Feature deactivation applies only to forthcoming requests. It does not affect any
ongoing or queued request procedures. The eNB takes the configuration changes into
account without affecting any service (without restarting).
Procedure
To deactivate the feature, do the following:

2 Deactivate the LTE951: Enhanced Cell ID Location Service feature.

d) Set the Activate LPPa enhanced cell ID location
service (actLPPaEcid) LNBTS parameter's value to false.
3 Send the parameter to the eNB according to the procedure described in section
Expected outcome
• The eNB deactivates the LTE951: Enhanced Cell ID Location Service feature for any
upcoming requests.
• The eNB informs NetAct and BTS Site Manager about the changed configuration via
configuration change notifications (CCNs).

Features
• The eNB takes the configuration change into account without affecting the service
(without restarting).
• The LTE951: Enhanced Cell ID Location Service feature activation flag is set to
false.
• The eNB will respond to any E-CID MEASUREMENT INITIATION REQUEST
message with an E-CID MEASUREMENT INITIATION FAILURE message with a
failure cause: Requested Item not Supported.

LTE1117: LTE MBMS LTE15A Radio Resource Management and Telecom
Features
6 LTE1117: LTE MBMS
6.1 Description of LTE1117: LTE MBMS

The LTE1117: LTE MBMS feature introduces the Multimedia Broadcast Multicast Service
(MBMS), which is a point-to-multipoint service allowing efficient multimedia delivery from
a single source entity to multiple recipients, using broadcast services. The MBMS can be
used, for example, for mobile TV and radio broadcasting.
g Note: From release LTE17 onwards, the LTE1117: LTE MBMS feature is enhanced with
LTE3199: Support for Multiple MBSFN and Synchronization Areas, which changes
some of the LTE1117 functionality. Please refer to the LTE3199 feature for more
information.
g Note: The MBMS functionality is not available in TDD LTE17 release.
Benefits
End-user benefits
The goal of the MBMS is to provide the end users with a possibility to receive high
quality and cheap broadcasts services over the cellular network.
Operator benefits
The LTE1117: LTE MBMS feature provides a basic framework at an eNodeB to support
the MBMS. It enables the distribution of broadcast content with substantial savings of the
bandwidth.
Requirements
MBMS overview
The MBMS delivers simultaneously the same content to multiple users with guaranteed
quality of service in a predefined MBMS serving area. The exemplary MBMS use cases
are:
• mobile TV
• broadcast during sports/concerts events (instant replays, player/artist statistics/info)
• broadcast of promotional messages (store promotions for shoppers at a mall)
• radio broadcasting
• file delivery
• emergency alerts (tsunami warnings, tornado/storm warnings, terrorist attacks)
• group calls
Architecture overview

LTE15A Radio Resource Management and Telecom LTE1117: LTE MBMS
Features
The radio network supports the MBMS via the Multicell/multicast Coordinating Entity
(MCE). It is a software unit, integrated in the eNodeB. The MCE takes care of MBMS
resource management and control information scheduling across cells.
The core network supports the MBMS via the MBMS Gateway (MBMS-GW) and
Broadcast Multicast Service Center (BM-SC).
The figure below shows a reference architecture for an MBMS broadcast mode in E-
UTRAN.
Figure 3 MBMS architecture
EvolvedPacketCore
S1U S5
S-GW
SGi
S11
P-GW IPServices
S1-MME
M3
eNodeB M1 MME
eMBMSNodes Sm SGi
M2
MCE MBMS-GW BM-SC ContentProvider
IntroducedbyMBMS
Since release LTE16A, MBMS is also supported in the Zone eNB deployment scenario
and on Flexi Zone Micro (all-in-one deployment).
Architecture details
MBMS entities and their functions:
• Broadcast/Multicast Service Center (BM-SC)
– MBMS user service provisioning and delivery
– MBMS bearer service authorization and initiation
– MBMS transmission scheduling and delivery
– entry point for content provider's transmissions
• MBMS Gateway (MBMS-GW)

– MBMS packet delivery to eNBs
– MBMS session control towards E-UTRAN
• Multi-cell/multicast coordination entity (MCE)

– MBMS admission control
– MBMS radio resource allocation
MBMS control plane interfaces and their functions:

Features
• M2 interface between MCE and eNB

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

– does not convey radio configuration data
– point-to-point SCTP used as signalling transport
• Sm interface between MBMS GW and MME

– MBMS service area control
• SGmb interface between BM-SC and MBMS GW

– MBMS service area control
MBMS user plane interfaces and their functions:

• M1 interface between MBMS GW and eNB
– IP multicast used for user plane data delivery
• SGi/SGi-mb interface between BM-SC and PDN/MBMS GW

– point-to-point MBMS data delivery
Protocol architecture
• The support of MBMS in LTE requires new logical (MTCH, MCCH), transport (MCH)
and physical channels (PMCH). It also extends the existing SIB2 and SIB3 and
introduces SIB13.
MBMS concepts and definitions

The following concepts and definitions are used:
• MBMS single frequency network (MBSFN)
– exactly the same signal is transmitted at the same time from a cluster of
neighboring cells
– energy is combined without experiencing inter-cell interference
• MBMS service area

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

Features
– All eNBs are synchronized and perform MBSFN transmissions.

– MBSFN synchronization areas support one or more MBSFN areas.
– On a given frequency layer, an eNB can only belong to a single MBSFN
synchronization area.
Figure 4 Different synchronization scenarios

Allcellshavethesame Interferingcellswithadifferent
synchronizationareaID synchronizationareaID.
MBSFNoperationcantakeafull
Nosynchronizationbetween
advantageofthemulti-cell
neighboreNBs-interference.
transmission
• MBSFN area
– a group of cells within an MBSFN synchronization area of a network, coordinated
to achieve an MBSFN transmission
• MBMS Service ID
Uniquely identifies MBMS bearer service within a public land mobile network
(PLMN), which identifies part of temporary mobile group identity
– allocated by BM-SC
– provided to the UE via service announcement
• Temporary mobile group identity

The TMGI is uniquely used by the UE and BM-SC to identify an MBMS bearer. It is
an equivalent to an IP multicast address and APN
– allocated by BM-SC
– provided to UE via service announcement
• MBMS user service

May use one or more multicast services at a time within MBMS service area bound
to a user service.
– A single broadcast service can only have one broadcast session at any time
within the MBMS service area bound to this user service.
– A broadcast service may consist of multiple successive broadcast sessions.
• Session ID
It is an integer broadcast over the air in MCCH.

Features
– It is assigned by the BM-SC, which, together with TMGI, allows the UE to

distinguish MBMS transmissions/retransmissions of a specific MBMS session.
– This information is included in the individual PMCH along with other configuration
parameters sent to the UE.
Figure 5 MBMS definitions
MBMSServiceArea4
MBMSServiceArea2 MBMSServiceArea3
MBMSServiceArea1
MBSFNSyncArea1 MBSFNSyncArea2
MBSFNArea1 MBSFNArea2
servicearea1,2,4 servicearea1,3
eNB1 eNB2 eNB3
cell1-6 cell1-6 cell1-6
MBSFNSubframe MBSFNSubframe MBSFNSubframe

Allocation Allocation Allocation
Feature limitations:
• Content synchronization across cells of multiple eNodeBs can be only guaranteed by
proper configuration of each eNodeB’s MCE. This is ensured by NetAct.
• 1.4, 3, 5 MHz are not supported for MBMS
• Deployed on a single frequency plane only. Consequently, mobility procedures for
MBMS reception over more than one frequency will not be supported.
• MBSFN Area reserved cell which does not perform MBSFN transmission is not
supported.
• MBMS Service counting is not supported.
System impact
The following features have to be enabled before the activation of the LTE1117: LTE
MBMS feature:
• LTE80: GPS Synchronization or
• LTE891: Timing over Packet with Phase Synchronization

Features
• LTE648: SCTP Multi-homing (optional)
The following features must be disabled before the LTE1117: LTE MBMS feature
activation:
• LTE4: RAN Sharing
• LTE48: High Speed User
• LTE116: Cell Bandwidth 3 MHz
• LTE117: Cell Bandwidth 1.4 MHz
• LTE125: IPv6 for U/C-plane (can be enabled since release LTE16A)
• LTE505: Transport Separation for RAN Sharing
• LTE819: DL Inter-cell Interference Generation
• LTE1113: eICIC - Macro
• LTE1382: Cell Resource Groups
• LTE1496: eICIC - Micro
• For the FDD: LTE1891: eNodeB Power Saving - Micro DTX
• For the TDD: LTE2461: eNodeB Power Saving - Micro DTX
The following features might have a negative impact on the LTE1117: LTE MBMS:
• LTE442: Network assisted cell change to GSM
• LTE736: CS fallback to UTRAN
• LTE872: SRVCC to WCDMA
The following features have an impact on the LTE1117: LTE MBMS feature
(interoperation required):
• LTE42: DRX in RRC Connected Mode
• LTE585: Smart DRX
• LTE1089: Downlink Carrier Aggregation - 20 MHz
• For the TDD: LTE1558: TDD Downlink Carrier Aggregation
• LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz
• LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs
• LTE1910: S1 Lock/Unlock
• For the TDD: LTE2120: TDD SIB Reception with Parallel Measurement Gaps
• For the FDD: LTE2085: SIB Reception with Parallel Measurement Gaps
• For the TDD: LTE113: Cell Bandwidth 15 MHz
• LTE1709: Liquid Cell
• LTE843: ETWS Broadcast
• LTE495: OTDOA (Observed Timer Difference of Arrival)
• LTE494: CMAS (Commercial Mobile Alert System)
• For the TDD: LTE2120: TDD SIB reception with parallel measurement gaps

Features
System impact for Flexi Zone Micro and post LTE15A features
• LTE2182: Enhanced Flexi Zone Plug & Play for Non-Operator Owned Backhaul –
LTE1117 is not expected to be used in enterprise and public backhaul deployments
since it does not support IPsec protection for M1 traffic.
• LTE2299: Dual Stack IPv4/IPv6 for S1/X2 – restriction that IPv6 and MBMS are
mutually exclusive is not valid anymore with LTE2299
• LTE689: LTE IPsec Support – total number of IPsec tunnels supported by FZM (and
corresponding PROTECT security policies) will be reduced from 30 to 29. Operators
that have 30 IPsec tunnels must reduce the number to 29 before upgrading to
LTE16A release.
Management data
Sales information

Requirements

FDD TDD
Nokia AirScale BTS FL16A FL16A
Flexi Zone BTS FL16A FL16A
Flexi Zone Controller Not supported Not supported
NetAct 15.5 15.5
MME Support not required Support not required
SAE GW Support not required Support not required
UE 3GPP R9 3GPP R9
Alarms
There are no alarms related to the LTE1117: LTE MBMS feature.

Features
Table 37 New BTS faults introduced by LTE1117

Fault ID Fault name Reported alarms
Alarm ID Alarm name
6850: M3 interface 7657 BASE STATION
EFaultId_M3ResetRet recovery failure CONNECTIVITY
ryOut DEGRADED
6851: M3 interface 7657 BASE STATION
EFaultId_M3SetupFail setup failure CONNECTIVITY
ure DEGRADED
6205: Transport layer 7657 BASE STATION
EFaultId_M3SctpEndp connection CONNECTIVITY
ointAl failure in M3 DEGRADED
interface
6206: M3 SCTP path 7652 BASE STATION
EFaultId_M3SctpPath failure NOTIFICATION
Al
6852: MBMS subframe 7651 BASE STATION
EFaultId_MbmsSubfra pattern share OPERATION
mePatternExceededAl exceeds DEGRADED
available share
6853: MBMS session 7652 BASE STATION
EFaultId_MbmsSessio cannot be NOTIFICATION
nSuspendedAl resumed
6854: MCE 7652 BASE STATION
EFaultId_MceConfigF configuration NOTIFICATION
ailureAl update failure
6855: MCE internal
EFaultId_MceInternal communication
ComFailureAl failure
4331: FZC LTE time out 7652 BASE STATION
EFaultId_FzcLteTime of sync NOTIFICATION
OutOfSyncAl
For alarm descriptions, see LTE Radio Access Operating Documentation > Reference >
Alarms and Faults
Commands
There are no commands related to the LTE1117: LTE MBMS feature.

M8030C1 Average number of 8030 - LTE MBMS (WBTS)
activated MBMS
sessions
M8030C2 MBMS user data volume 8030 - LTE MBMS (WBTS)
(eUu interface)
M8030C3 MBMS user data volume 8030 - LTE MBMS (WBTS)
(M1 interface)

Features

M8030C4 Lost MBMS user data 8030 - LTE MBMS (WBTS)
volume (M1 interface)
M8030C5 Dropped MBMS user data 8030 - LTE MBMS (WBTS)
volume 1 (M1
interface)
M8030C6 Dropped MBMS user data 8030 - LTE MBMS (WBTS)
volume 2

Reference/Counters.

There are no key performance indicators related to the LTE1117: LTE MBMS feature.
Parameters
The LTE1117 feature introduces over 20 new parameters and 4 new managed objects
(MOC) which are used in the configuration of the MBMS. The new managed objects are:
• LNBTS: LNMCE – identifies the MCE (one instance per eNB)
• LNMCE: LNM3 – represent an M3 link between eNB MCE entity and MME. It
contains address, link state information and provides link management parameters
(one instance per eNB)
• LNMCE: MBFSN – contains radio transmission, scheduling, synchronization and
physical channel information (MCCH, PMCH)
• MCAPP - required to receive multicast user plane traffic
Table below lists all new parameters introduced by this feature.
name object
Activate support for actMBMS LNBTS - common
MBMS
MBMS neighbour cells mbmsNeighCellCo SIB - common
configuration nfigIntraF
Cell power reduction for cellPwrRedForMB LNCEL - common
MBMS transmission MS
Twofold transmission of sib2xTransmit SIB - common
SIBs per SI window
LTE MBMS mtMBMS PMRNL - common
Multi-cell multicast lnMceId LNMCE - common
coordination entity
identifier
MCE Identity mceId LNMCE - common
MCE Name mceName LNMCE - common

Features

name object
Administrative state administrativeState LNM3 - common
LTE MME M3 link lnM3Id LNM3 - common
identifier
M3 Link Status m3LinkStatus LNM3 - common
M3 Primary IPv4 address m3ipAddrPrim LNM3 - common
M3 Secondary IPv4 m3ipAddrSec LNM3 - common
address
MBMS SYNC reference mbmsSyncRef M1SYNC - common
MBSFN Area Identity mbsfnAreaId MBSFN_FD - common
D for FDD
and
MBSFN_TD
D for TDD
MBSFN downlink channel mbsfnDlChBw MBSFN - common
bandwidth SYNCAREA
_FDD
SYNCAREA
_TDD
MBSFN EARFCN mbsfnEarfcn MBSFN - common
SYNCAREA
_FDD
SYNCAREA
_TDD
MBMS single frequency mbsfn_FddId MBSFN_FD - FDD
network identifier D
MBMS single frequency mbsfn_TddId MBSFN_TD - TDD
network identifier D
Multicast channel info mchInfo MBSFN - common
_FDD_TDD
Signalling Modulation and signallingMCS MBSFN - common
coding scheme _FDD_TDD
Fractional seconds fractionalSecs M1SYNC mbmsSyncRef common
Integral seconds integralSecs M1SYNC mbmsSyncRef common
Data Modulation Code dataMCS MBSFN mchInfo common
Scheme _FDD_TDD
MBMS SYNC period mbmsSyncPeriod M1SYNC - common
Multicast channel mchSchedulingPeri MBSFN mchInfo common
Scheduling period od _FDD_TDD
QCI qci MBSFN_FD mchInfo common
DLNBTS

Features

name object
Multicast application mcAppId MCAPP - common
identifier
IPv4 Multicast Application mcAppType MCAPP - common
Type
IPv4 Multicast Used Link usedLinkLayerIf MCAPP - common
Layer Interface
Maximum MBSFN sync maxSyncSubfrPSh MBSFNSY - common
area subframe pattern are NCAREA_F
share DD for FDD
and
MBSFNSY
NCAREA_T
DD for TDD
Maximum MBSFN maxSubfrPShare MBSFN_FD - common
subframe pattern share D for FDD
and
MBSFN_TD
D for TDD
Additionaly, a several dozen already exsisting parameters and structure of parameters

need to be configured in order to make MBMS functional. Those parameters are listed in
the table below.
Table 40 Existing parameters related to LTE1117 (for TDD)
Full name Abbreviated Managed Structure FDD/TDD
name object
Activation Flag Dual U- actDualUPlaneIpA IPNO - common
Plane Ip Addresses ddress
Activation Flag Transport actSeparationRan IPNO - common
Separation For RAN Sharing
Sharing
Cell resource sharing cellResourceShari LNCEL - common
mode ngMode
Channel bandwidth TDD chBw LNCEL - TDD
_TDD
CSI-RS configuration csiRsConfigInfo LNCEL - TDD
information _TDD
Cell power reduce dlCellPwrRed LNCEL - common
DRX profile 2 drxProfile2 DRX - common
DRX smart profile 2 drxSmartProfile2 SDRX - common

Features
Table 40 Existing parameters related to LTE1117 (for TDD) (Cont.)

name object
EARFCN for both earfcn LNCEL - TDD
Downlink and Uplink _TDD
(TDD)
LTE cell configuration lnCelId LNCEL - common
identifier
Maximum output power pMax LNCEL - common
PRACH high speed flag prachHsFlag LNCEL - TDD
_TDD
PRS configuration index prsConfigurationIn LNCEL - TDD
dex _TDD
Random access response raRespWinSize LNCEL - common
window size
System information sibSchedulingList SIB - common
scheduling list
TDD subframe tddFrameConf LNCEL - TDD
configuration _TDD
TDD special subframe tddSpecSubfConf LNCEL - TDD
configuration _TDD
Administrative state administrativeState LNM3 - common
LTE MME M3 link lnM3Id LNM3 - common
identifier
MBMS neighbour cells mbmsNeighCellCo SIB - common
configuration nfigIntraF
Table 41 Existing parameters related to LTE1117 (for FDD)

name object
Carrier aggregation caRelId CAREL - common
relation identifier
Local cell resource ID of lcrId CAREL - common
cell to be aggregated
Activation Flag Dual U- actDualUPlaneIpA IPNO - common
Plane Ip Addresses ddress
Activation Flag Transport actSeparationRan IPNO - common
Separation For RAN Sharing
Sharing
Activate liquid cell actLiquidCell LNCEL - FDD
configuration _FDD
PRS activation actOtdoa LNCEL - common
Cell resource sharing cellResourceShari LNCEL - common
mode ngMode

Features
Table 41 Existing parameters related to LTE1117 (for FDD) (Cont.)

name object
Cell power reduce dlCellPwrRed LNCEL - common
Downlink channel dlChBw LNCEL - FDD
bandwidth _FDD
Liquid cell configuration liquidCellConfigInfo LNCEL - FDD
information _FDD
LTE cell configuration lnCelId LNCEL - common
identifier
Maximum output power pMax LNCEL - common
PRACH high speed flag prachHsFlag LNCEL - FDD
_FDD
PRS configuration index prsConfigurationIn LNCEL - FDD
dex _FDD
Random access response raRespWinSize LNCEL - common
window size
Twofold transmission of sib2xTransmit SIB - common
SIBs per SI window
SI window length siWindowLen SIB - common
System information sibSchedulingList SIB - common
scheduling list
Sales information

Product structure class License control Activated by default
6.3 Activating and configuring LTE1117: LTE MBMS

Before you start
The following information provides the details and conditions for correct activation of the
LTE1117: LTE MBMS feature.
The table below lists the parameters used for activating and configuring the LTE1117:
LTE MBMS feature.

Features
Table 43 Parameters used for activating and configuring the LTE1117: LTE MBMS
feature
object locking
Activate support for MBMS activation flag no
(actMBMS)
LNBTS: LNMCE parameters mandatory configuration no
LNMCE: LNM3 parameters mandatory configuration no
LNMCE: MBSFN parameters mandatory configuration no
All the parameters can be found in and configuration details and examples can be found
in Configuration details of LTE1117.
g Note: The LTE1117: LTE MBMS feature has to be activated on all the eNBs with the
same MBSFN SYNC using the NetAct Configurator for this purpose. More information
can be found in the NetAct documentation following the path below:
NetAct Documentation ► Configuration Management ►
Configuration Management Operating Procedures ►
Managing the Network with NetAct Configurator ►
Managing Multimedia Broadcast Multicast Service (MBMS) with a workflow
The Activate support for MBMS (actMBMS) parameter can only be set to true
only if all the following conditions are fulfilled:
• At least one S1 link is established.

• MBMS-related information in the transport domain is configured.
• At least one LNCEL instance with earfcn equal to
MBSFNSYNCAREA_FDDSYNCAREA_TDD mbsfnEarfcn and chBw equal to
MBSFNSYNCAREA_FDDSYNCAREA_TDD mbsfnDlChBw must be created.
• The following conditions must be fulfilled in all cells which are candidates for MBMS
broadcasting, that is with earfcn equal to
MBSFNSYNCAREA_FDDSYNCAREA_TDD mbsfnEarfcn and chBw equal to
MBSFNSYNCAREA_FDDSYNCAREA_TDD mbsfnDlChBw:
– The LTE48: High speed users feature is deactivated, that is prachHsFlag is
equal to false in all LNCEL/LNCEL_FDD/LNCEL_TDD instances with
earfcnDL equal to MBSFNSYNCAREA_FDDSYNCAREA_TDD
mbsfnEarfcn.
– The LTE1382: Cell resource groups feature is deactivated, that is
cellResourceSharingMode equal to none.
– The LTE1113: eICIC-macro and LTE1496 eICIC-micro features are deactivated,
that is actEicic is equal to false.
– If the LTE495: OTDOA is activated, that is if actOtdoa is equal to ‘true’
restriction for configuration of the parameter prsConfigurationIndex is
considered.
– TDD subframe configuration sa2 (3GPP 36.331) is selected, that is
tdFrameConf is equal to '2'.
– The restrictions on the configuration of the CSI-RS subframe configuration
(LNCEL_FDD_TDD parameter csiRsSubfrConf) are considered.
• The drxOnDuratT, drxRetransT and raRespWinSize parameters must be:

Features
– greater than or equal to 6 if subfrPShareRequired is less than or equal to

20.
– greater than or equal to 10 if subfrPShareRequired is greater than 20.
• SIB13 must be present in sibSchedulingList-siMessageSibType.
• The following configuration rules apply.

– The LTE124: IPv6 feature must not be activated, that is the IPNO parameter
actIpv6 is equal to false (not applicable since LTE16A release).
– The LTE4: RAN Sharing feature is not configured, that is no further PLMN-Ids are
configured in LNCEL parameter furtherPlmnIdL. Multiple S1 links are only
used for redundancy but not for RAN sharing.
g Note:
• The MCE configuration must be aligned between eNBs/cells belonging to the same
MBSFN synchronization area.
• The configuration of features LTE495 (OTDOA), LTE843 (ETWS), LTE494 (CMAS)
and the setting of the sib2xTransmit parameter must be aligned between
adjacent eNBs with activated feature ‘MBMS' and belonging to the same MBSFN
area, that is with the same mbsfnAreaId.
To activate and configure the feature, do the following:
Procedure
features using the BTS Site Manager.

2 Define the MBMS application.
a) Go to the IP Interfaces page.

b) Click the New MBMS application.
c) Select the Multimedia Broadcast Multicast from the table on the left, and set
the required value of the MBMS Interface parameter from the drop-down
menu.
3 Change the Network synchronisation mode to Phase synchronization.
a) Go to the BTS Synchronization Settings page.

b) Change the Network synchronization mode by choosing Phase synchronization
from the drop-down menu.

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

• LNBTS: LNMCE
• LNMCE: LNM3
• LNMCE: MBSFN_FDD_TDD

c) Right-click on the LNBTS and create a new LNMCE object.
d) Right-click on the LNMCE and create a new LNM3 and
MBSFNSYNCAREA_TDDSYNCAREA_FDD objects.
e) Right-click on MBSFNSYNCAREA_FDDMBSFNSYNCAREA_TDD and create
MBSFN_FDDMBSFN_TDD object.
5 Set the required values in the MBSFN object.

d) Expand the LNMCE object.
e) Expand the MBSFNSYNCAREA_FDDMBSFNSYNCAREA_TDD object.
f) Expand the MBSFN_FDDMBSFN_TDD object and configure the required
parameters:
• Set the required value of the MBSFN Area Identity (mbsfnAreaId)
between 0 and 225.
• Set the required value of the Signaling Modulation and coding
scheme (signallingMCS) from the drop down menu.
g) Expand the MBSFN_TDDLNMCE object
h) Select the MBMS Service Area and type the required service area identifier.
i) Select the MBSFN SYNC reference object from MRBTS ► LNBTS ► M1SYNC
and type in the desired values of the following parameters:
• Fractional seconds
• Integral seconds
• MBMS Sync period (It is recommend to set the MBMS Sync period to
at least twice the value of Multicast channel Scheduling period)
j) Select the Multicast channel info object from MRBTS ► LNBTS ► LNMCE ►
MBSFNSYNCAREA_FDD ► MBSFN_FDDMRBTS ► LNBTS ► LNMCE ►
MBSFNSYNCAREA_TDD ► MBSFN_TDD and type in the desired values of the
following parameters:
• Data modulation Code Scheme
• Multicast channel Scheduling period

Features
k) Select the LNM3 object from MRBTS ► LNBTS ► LNMCE; set the required
value of the LTE MME M3 link identifier parameters and type in the
desired IPv4 address under the M3Primary IPv4 address using the correct
IP format.
6 Define a new SIB Type dedicated for the SIB13 in the System Information
Scheduling list for each LNCEL instance of an eNB supporting MBMS.

d) Expand the LNCEL object.
e) Expand the SIB object.
f) Select and click the System information scheduling list.
g) SelectSIB13 in SIB Type dropdown list and define Periodicity and
Repetition
h) Proceed with definition of SIB13 in System information scheduling
list for each LNCEL managed object defined for LNBTS
7 Activate the feature flag for LTE1117.

d) Set the Activate support for MBMS (actMBMS) parameter value to true.
Result
MBMS is configured and activated
6.4 Configuration details of LTE1117

Consistency between eNBs and BM-SC
Certain parameters have to be set consistently between eNBs and BM-SC. Please refer
to the sections below for more information.
When determining the percentage of downlink subframes that need to be allocated to
MBMS, the operator needs to consider the following items:
• data rates of MBMS services that will be transmitted simultaneously
• MCS at which the MBMS data will be transmitted (Data MCS)

Features
• system bandwidth (10, 15, or 20 MHz)

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

Data Bits/Second versus MBMS Data MCS*
Cell BW % SD for MCS 5 MCS 10 MCS 15 MCS 20
(MHz) MBMS
10 40 1581120 3153600 5080320 7698240
15 40 2416320 4665600 7698240 11828160
20 40 3153600 6324480 10200960 15773760
10 35 1383480 2759400 4445280 6735960
15 35 2114280 4082400 6735960 10349640
20 35 2759400 5533920 8925840 13802040
10 30 1185840 2365200 3810240 5773680
15 30 1812240 3499200 5773680 8871120
20 30 2365200 4743360 7650720 11830320
10 25 988200 1971000 3175200 4811400
15 25 1510200 2916000 4811400 7392600
20 25 1971000 3952800 6375600 9858600
10 20 790560 1576800 2540160 384912
15 20 1208160 2332800 3849120 5914080
20 20 1576800 3162240 5100480 7886880
10 15 592920 1182600 1905120 2886840
15 15 906120 1749600 2886840 4435560
20 15 1182600 2371680 3825360 5915160
10 10 395280 788400 1270080 1924560
15 10 604080 1166400 1924560 2957040
20 10 788400 1581120 2550240 3943440
10 5 197640 394200 635040 962280
15 5 302040 583200 962280 1478520
20 5 394200 790560 1275120 1971720
10 2.5 98820 197100 317520 481140
15 2.5 151020 291600 481140 739260
20 2.5 197100 395280 637560 985860

Features
Table 45 MBMS Data Rate Table

BW (MHz) % SD for MCS 5 MCS 10 MCS 15 MCS 20
MBMS
10 37 1462536 2917080 4699296 7698240
15 37 2235096 4315680 7120872 10941048
20 37 2917080 5850144 9435888 14590728
10 34 1343952 2680560 4318272 6543504
15 34 2053872 3965760 6543504 10053936
20 34 2680560 5375808 8670816 13407696
10 31 1225368 2444040 3937248 5966136
15 31 1872648 3615840 5966136 9166824
20 31 2444040 4901472 7905744 12224664
10 28 1106784 2207520 3556224 5388768
15 28 1691424 3265920 5388768 8279712
20 28 2207520 4427136 7140672 11041632
10 25 988200 1971000 3175200 4811400
15 25 1510200 2916000 4811400 7392600
20 25 1971000 3952800 6375600 9858600
10 22 869616 1734480 2794176 4234032
15 22 1328976 2566080 4234032 6505488
20 22 1734480 3478464 5610528 8675568
10 19 751032 1497960 2413152 3656664
15 19 1147752 2216160 3656664 5618376
20 19 1497960 3004128 4845456 7492536
15 16 966528 1866240 3079296 4731264
20 16 1261440 2529792 4080384 6309504
10 12 474336 946080 1524096 2309472
15 12 724896 1399680 2309472 3548448
20 12 946080 1897344 3060288 4732128
10 9 355752 709560 1143072 1732104
15 9 543672 1049760 1732104 2661336
20 9 709560 1423008 2295216 3549096
10 6 237168 473040 762048 1154736
15 6 362448 699840 1154736 1774224
20 6 473040 948672 1530144 2366064
10 3 118584 236520 381024 577368
15 3 181224 349920 577368 887112

Features
Table 45 MBMS Data Rate Table (Cont.)

BW (MHz) % SD for MCS 5 MCS 10 MCS 15 MCS 20
MBMS
20 3 236520 474336 765072 1183032
* Bits/Second is reduced by 10% due to MBMS signaling subframes and RLC/MAC

header overhead.
MBMS Subframe Percentage Examples

Example 1: Single service
• video stream with 720p @ 2 Mbps
• cell BW = 15 MHz
• data MCS selected = 10
Based on the video specifications, and using the MBMS Data Rate table, 30% MBMS
subframes is the lowest MBMS subframe percentage that provides at least 2 Mbps
(2,365,200 bps) with the given parameters.
Example 2: Multiple services with multiple data MCSs

Video stream with 720p @ 2 Mbps
Audio Streaming @ 100 kbps
The video stream will require at least 30% MBMS sub frames to achieve 2 Mbps
(2,365,200 bps) ) at 10 MHz and MCS = 10. The audio streams will require an additional
100 Kbps at 10MHz and MCS = 15. Since the 30% of MBMS sub frames selected
provides 2,365,200 Kbps, the remaining bandwidth is more than is necessary for the
audio, this excess bandwidth is more than enough to support the 100 Kbps required by
the audio streams. No additional MBMS sub frames need to be allocated for the audio.
Example 2: Multiple services with multiple data MCSs

Video stream with 720p @ 2 Mbps
Audio Streaming @ 100 kbps
The video stream will require at least 19% MBMS subframes to achieve 2 Mbps
(2,216,160) at 15 MHz and MCS = 10. The audio streams will require an additional 100
Kbps at 15MHz and MCS = 15. Since the 19% of MBMS subframes selected provides

Features
2,216,160 bps, there is an excess bandwidth of 216 Kbs. This excess bandwith is more
than enough to support the 100 Kbps required by the audio streams. No additional
MBMS sub frames need to be allocated for the audio.
Configuration for MBMS data flow synchronization

In order to ensure synchronized radio interface, MBMS transmission from the cells
controlled by different eNBs, MBMS SYNC-protocol [TS 25.446] support is needed
between BM-SC and the eNBs.
As part of the SYNC-protocol, certain parameters have to be set consistently between
the BM-SC and the eNBs, namely:
• Common time reference: on the eNB, this parameter is called MBMS SYNC
Reference. This parameter has to be set in the same way on both the eNB and BM-
SC after ensuring that both the eNB and BM-SC are synchronized to the same clock
source such as NTP or GPS synchronization. Example: Based on NTP on the eNB, if
MBMS SYNC Reference::Integral Seconds is set to 3615771600, and MBMS SYNC
Reference::Fractional Seconds is set to 0, then the same equivalent value has to be
provisioned on the BM-SC.
• Synchronization Period: as part of the SYNC-protocol, both BM-SC and eNB for
each service have to maintain the same synchronization period. On the eNB, this
parameter is called MBMS SYNC Period, after which the relative timestamps within
the SYNC PDUs can wrap around.
• Synchronization sequence: Each SYNC PDU contains a timestamp that indicates the
start time of a sequence for an MBMS service. Since the BM-SC is not aware of the
MCE/eNB scheduling boundaries, the synchronization sequence length that is
configured on the BM-SC has to be proportional to the Multicast Channel Scheduling
Period (MSP) on the eNB. The MSP length provisioned in the eNB is one or multiple
times of the synchronization sequence length for MBMS services in the MCH.
The BM-SC includes a timestamp in the SYNC PDUs, based on which the eNB has to
send MBMS data over the air interface. The time stamping of SYNC PDUs, is based
upon a relative time value from the above common time reference, which refers to the
start time of the synchronization period.
The eNB will schedule the received data packets in the first MSP following the time point
indicated by the timestamp. If they are not configured properly, a poor MBMS service
may be observed due to excessive packet drops. Too long of an MSP with a high
dataMCS will require that large amounts of data are buffered at the eNB prior to the
MBMS transmission. If the buffered data size becomes too large, packets may become
lost.
6.5 Deactivating LTE1117: LTE MBMS

Before you start
g Note: The Activate support for MBMS (actMBMS) parameter is used for
deactivation.
The LTE1117: LTE MBMS feature has also to be deactivated on all the eNBs which have
the same MBSFN SYNC using the NetAct Configurator for this purpose. More
information can be found in the NetAct documentation following the below path:

Features
NetAct Documentation ► Configuration Management ► Configuration

Management Operating Procedures ► Managing the Network with NetAct
Configurator ► Managing Multimedia Broadcast Multicast Service (MBMS) with a
workflow
Procedure

2 Deactivate the feature.

b) Expand the MRBTS object(s).
c) Select the LNBTS object(s).
d) Set the Activate support for MBMS (actMBMS) parameter value to
false.
Expected outcome
The LTE1117: LTE MBMS feature has been deactivated.

LTE1196: RAN Information Management for WCDMA LTE15A Radio Resource Management and Telecom
Features
7 LTE1196: RAN Information Management for

WCDMA
7.1 Description of LTE1196: RAN Information

Management for WCDMA
The LTE1196: RAN Information Management for WCDMA feature allows transferring
information between the source and target cell by the core network. This mechanism
allows to reduce the number of setting parameters.
Benefits
End-user benefits
This feature provides the end user with:
• faster CS fallback
• faster regular redirection
Operator benefits
• reduction of the parameters needed to configure CS fallback with redirection

• reduction of the parameters needed to configure regular redirection to WCDMA
• support of LTE multi-operator core network (MOCN) and WCDMA MOCN
deployment
Functional overview
The RAN information management (RIM) procedures support the core network in an
information exchange between peer application entities located in GERAN, UTRAN, or
the E-UTRAN access network. The LTE1196: RAN Information Management to WCDMA
feature allows up-to-date system information (SI) of WCDMA neighbor cells to be
transferred from a remote radio network controller (RNC) to a local eNB. This proccess is
used to populate WCDMA SI for redirection to the WCDMA procedure. Figure 6: RIM
protocol structure between E-UTRAN and UTRAN presents the process of transporting
protocols between LTE and WCDMA.

LTE15A Radio Resource Management and Telecom LTE1196: RAN Information Management for WCDMA
Features
Figure 6 RIM protocol structure between E-UTRAN and UTRAN
ENB S1 S3 /GN IU RNC

MME SGSN
(controlling) (Serving)
RIMContainer RIMContainer
RIM-App RIM-App
RIM RIM-App RIM-App RIM

RIM-App RIM-App
(forexampleUTRASI) (forexampleUTRASI)
RIMPDUs RIMPDUs
Relay Relay
S1AP S1AP GTP-C GTP-C RANAP RANAP

UDP UDP
SCTP SCTP NS NS
SCTP
IP IP
L2 L2
IP/L2&L1 IP/L2&L1 L1
IP/L2&L1 L1
L1 L1
The RIM function enables the eNB to retrieve SI from the target UTRAN cell and allows
the eNB to receive WCDMA SI from a remote RNC.
The eNB supports the RIM for CS fallback with a redirect and a normal redirect to
WCDMA.
The RIM function enables the eNB to retrieve SI from a target WCDMA cell. The
retrieved information is used to automatically fill and update the related SI attributes for
all the enabled features to which an RRC connection release with a redirect to WCDMA
is applied. This proccess is presented in Figure 7: Redirection procedure with SI.
Figure 7 Redirection procedure with SI
UE .eNB MME
RRC:RRCConnectionRelease
(1)
(releaseCause,RedirectedCarierInfo,
[cellinfoList-r9]) S1AP:UECONTEXTRELEASEREQUEST
(2)
S1AP:UECONTEXTRELEASECOMMAND
(3)
S1AP:UECONTEXTRELEASECOMPLETE
(4)
For each neighbor WCDMA frequency of an LTE cell, up to 16 WCDMA neighbor cells
can be enabled to provide SI via RIM in the redirect message. The same SI is sent in
case of:
• a normal RRC connection release with a redirect to WCDMA

Features
• a normal redirect based on CS fallback to WCDMA

• an emergency CS fallback to WCDMA to the UE
The assigned mobility profile and the UE capabilities are considered when selecting the
SI to be added to the redirect message.
g Note: In extreme conditions, the RIM UTRA SI application (ENBC) is running on FSMr2
board, and the memory for RIM UTRAN SI storage may be used up. For the new
coming up LTE cells, the UTRAN SI for some WCDMA neighbor cells might be
temporarily unavailable (not in UEC) until the next UTRAN SI update or RIM association
re-establishment. If the WCDMA neighbor cells’ RIM interface
status (rimStatus) is set to available at eNB level, it does not have impact on
this process. It is caused due to memory capacity limitation of FSMr2 board.
RAN information procedure for the enabled WCDMA neighbor cell

The RIM protocol is encapsulated in the S1AP.MME DIRECT INFORMATION
TRANSFER and the S1AP:ENB DIRECT INFORMATION TRANSFER messages.
The following RIM procedures are supported:
• RAN information request/multiple report

• RAN information request/stop
• RAN information send
• RAN information application error
• RAN information error
Redirection procedure
Selecting suitable cells
The following conditions must be fulfilled for the eNB to check the RIM interface
status (rimStatus) parameter for each suitable WCDMA cell:
• if rimStatus is available, SI for the WCDMA cell is taken from RIM.
• if rimStatus is unavailable or disable, SI for the WCDMA cell is not
included (theWCDMA cell is omitted by the eNB).
The following conditions must be fulfilled to check all objects (LNRELW object instances)
related to the WCDMA neighboring cell for the LTE cell:
• the WCDMA cell's frequency is the same as the chosen target frequency
represented by the UARFCN value
• an active flag allows adding SI in a release message
Elimination of unsuitable cells by CS fallback

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

Features
• If the list is empty, eNB checks again all the targets from the original list as it was
before, but only the PLMN value will be checked. Primary/secondary PLMNs
configured for the WCDMA cell (in LNADJW) must be included in RegisteredLAI IE.
Otherwise, SI for that WCDMA cell is eliminated from the list.
If the RegisteredLAI was not received, the handover restriction list was received and
there was no emergency call, at least one of the primary/secondary PLMNs configured
for the WCDMA cell (in LNADJW) must be included in the set of PLMN IDs allowed by
the UE (a combination of Serving PLMN ID and Equivalent PLMN IDs optionally provided
within the handover restriction list). Otherwise, SI for this WCDMA cell is eliminated from
the list.
g Note: For a selected UTRAN frequency, the O&M is configured for a UE context
release only; the eNB will not add the WCDMA SI to the CSFB redirection message.
Elimination of unsuitable cells by the UE context with redirection

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

On the S1 interface, the following procedures are supported to transmit RIM information:
• the eNB Direct Information Transfer procedure to transmit an information container
from the eNB to the MME
• the MME Direct Information Transfer procedure to transmit an information container
from the MME to the eNB
System impact
The following features will make use of UTRA SI acquired via the RIM function:
• LTE562: CSFB to UTRAN/GERAN via Redirection

• LTE22: Emergency Call Handling
• LTE423: RRC Connection Release with Redirect
• LTE1073: Measurement-based Redirect to UTRAN
• LTE1407: RSRQ-based Redirect
• LTE2108: Redirected VoLTE Call Setup
• LTE2388: VoLTE Call Steering Enhancement

Features
g Note: The LTE1196: RAN Information Management for WCDMA feature reuses most of
the procedures of the LTE498 RAN Information Management for GSM feature, but there
is no dependency relationship between both features.
g Note: The LTE908: ANR Inter-RAT UTRAN – fully UE-based feature should also be
considered as RIM-enabled (if automatically created UTRAN neighbor cells are not on
the RIM PLMN blacklist).
The LTE1342: Extended RNC ID feature interact with the LTE1196: RAN Management
Information for WCDMA feature. If the LTE1342: Extended RNC ID feature is enabled,
the LTE1196: RAN Information Management for WCDMA feature will use extended RNC-
ID in RIM messages. The extended RNC-ID is configured for a UTRAN neighbor cell.
The LTE915: S1 eNode B Configuration Update feature interact with the LTE1196: RAN
Management Information for WCDMA feature. If the possible feature interaction will be
covered by the LTE915: S1 eNode B Configuration Update feature.
This feature impacts:
• the RRC protocol in the LTE-Iu interface

• the S1AP protocol in the S1-MME interface
• the interface to NetAct

This feature has no impact on network management or network element management
tools.


LTE1196: RAN Information Management for WCDMA requirements, alarms and faults,
Requirements

FDD TDD

Features

FDD TDD
Alarms
Table 47 Existing alarms related to LTE1196

Alarm ID Alarm name
7657 BASE STATION CONNECTIVITY DEGRADED
The alarm is caused by the following BTS faults:
• RIM interface timeout (fault id 6322)
• RIM interface error (fault id 6323)
For alarm descriptions, see LTE Operating Documentation/Reference/Alarms and Faults

There are no faults related to the LTE1196: RAN Information Management for WCDMA
feature.
Commands
There are no commands related to the LTE1196: RAN Information Management for
WCDMA feature.

There are no measurements or counters related to the LTE1196: RAN Information
Management for WCDMA feature.

There are no key performance indicators related to the LTE1196: RAN Information
Management for WCDMA feature.
Parameters

Features

Full name Abbreviated name Managed Parent Structure FDD/TDD
object
RIM rimStatus LNADJW - Common
interface
status
Activate RAN actRIMforUTRA LNBTS - Common
information N
management
for UTRAN
Blacklisted blacklistUtra RIM - Common
UTRAN cells nCellsForRim
for RIM
MCC Mcc RIM blacklistUtr Common
anCellsForRi
m
MNC Mnc RIM blacklistUtr Common
anCellsForRi
m
MNC length mncLength RIM blacklistUtr Common
anCellsForRi
m
RNC ID rncId RIM blacklistUtr Common
anCellsForRi
m
UTRAN utranCarrierF RIM blacklistUtr Common
carrier req anCellsForRi
frequency m
Max. RIR nRimRirU RIM - Common
attempts to
UTRAN
Timer to tRimKaU RIM - Common
wait for
next RI PDU
from UTRAN
Polling tRimPollU RIM - Common
timer to
ReStart RIR
procedure to
UTRAN
Timer to tRimRirU RIM - Common
wait for RIR
response
from UTRAN
Good radio goodRadioCond RIM - common
condition ForCsfbThres
threshold
for CSFB
redirect
Max. UTRA SI maxSizeUtraSI RIM - common
size for GoodRadioCond
good radio
condition

Features

Full name Abbreviated name Managed Parent Structure FDD/TDD
object
Max. UTRA SI maxSizeUtraSI RIM - common
size for WeakRadioCond
weak radio
condition
Reachable rimReachableP LNMME - Common
PLMNs for LMNList
RIM
MCC mcc LNMME rimReachable Common
PLMNList
MNC mnc LNMME rimReachable Common
PLMNList
MNC length mncLength LNMME rimReachable Common
PLMNList
Redirect redirWithSysI LNRELW - Common
with system nfoAllowed
information
allowed
Add UTRAN addUtranSIToR MODRED - Common
system edirMsg
information
to
redirection
message
Add UTRAN addUtranSIToR MORED - Common
system edirMsg
information
to
redirection
message
Add UTRAN addUtranSIToR REDRT - Common
system edirMsg
information
to
redirection
message
g Note: Manual configuration of WCDMA system information is no longer supported. The

SystemInformationListWCDMA LNBTS parameter is removed.
Sales information

element
ASW Pool license No

Features
7.3 Activating and configuring LTE1196: RAN

Information Management for WCDMA
Before you start
Table 50: Parameters used for activating and configuring LTE1196: RAN Information
Management for WCDMA lists parameters used for activation and configuration of the
LTE1196: RAN Information Management for WCDMA feature.
Table 50 Parameters used for activating and configuring LTE1196: RAN Information
object locking
Active RAN Information activation flag no
Management for UTRAN
(actRIMforUTRAN)
Timer to wait for RIR response mandatory configuration no
from UTRAN (tRimRirU)
Timer to wait for next RI PDU from mandatory configuration no
UTRAN (tRimKaU)
Polling timer to ReStart RIR mandatory configuration no
procedure to UTRAN (tRimPollU)
Max. RIR attempts to UTRAN mandatory configuration no
(nRimRirU)
Redirection target configuration mandatory configuration no
identifier (redir)
RAT for redirection (redirRat) mandatory configuration no
Mobility default profile identifier for mandatory configuration no
redirection (moDRedId)
Redirection priority for CS fallback mandatory configuration no
with redirection (csFallBPrio)
Reachable PLMNs for RIM mandatory configuration no
(rimReachablePLMNList)
Mobility profile identifier (moPrId) mandatory configuration no
Mobility default profile identifier for mandatory configuration no
redirection (moRedId)
Blacklisted UTRAN cells for RIM optional configuration no
(blacklistUtranCellsForRim)
MCC (mcc) optional configuration no
MNC (mnc) optional configuration no
MNC length (mncLength) optional configuration no
RNC Id (rncId) optional configuration no
UTRAN carrier frequency optional configuration no
(utranCarrierFreq)
Redirect with system information optional configuration no
allowed (redirWithSysInfoAllowed)

Features
Table 50 Parameters used for activating and configuring LTE1196: RAN Information
Management for WCDMA (Cont.)
object locking
Target cell Id in UTRAN CGI of optional configuration no
related neighbor cell (uTargetCid)
Target RNC Id (uTargetRncId) optional configuration no
Add UTRAN system information to optional configuration no
redirection message
(addUtranSIToRedirMsg)
eUTRA frequency (redirFreqEutra) optional configuration no
Before activation and configuration of the LTE1196: RAN Information Management for
WCDMA feature ensure that there is an LNADJW object configured with all required
parameters. If there is no LNADJW object configured, the handover is not possible.
Procedure

2 Optional: If not yet configured, configure the LNADJW object with all parameters.

d) Add the LNADJW object.
e) Set the Neighbor WCDMA BTS cell identifier (InAdjWId)
parameter's value to a desired value from 0 to 255.
f) Set the Primary scrambling code (FDD) (uTargetScFdd) parameter's
value to a desired value from 0 to 511.
g) Set the Target cell ID (uTargetCid) parameter's value to a desired value
from 0 to 65535.
h) Set the Target frequency (uTargetFreq) parameter's value to a desired
value from 0 to 16383.
i) Set the Target location area code (uTargetLac) parameter's value to
a desired value from 0 to 65535.
j) Set the Target RNC ID (uTargetRncId) parameter's value to a desired
k) Set the Target routing area code (uTargetRac) parameter's value to a
desired value from 0 to 255.
l) Expand the Target primary PLMN identy object.

Features
m) Set the MCC, MNC (mcc, mnc) parameters' value to a desired value from 0 to
999.
n) Set the MNC length (mncLength) parameter's value to a desired value from 2
to 3.
3 Activate the feature flag of the LTE1196: RAN Information Management for WCDMA
feature.

d) Set the Active RAN Information Management for
UTRAN (actRIMforUTRAN) parameter's value to true.
4 Optional: Adapt RIM-specific timer and retransmission counter.

d) Select and expand the RIM object.
e) Set the Timer to wait for RIR response from UTRAN (tRimRirU)
f) Set the Timer to wait for next RI PDU from UTRAN (tRimKaU)
g) Set the Polling timer to ReStart RIR procedure to
UTRAN (tRimPollU) parameter's value to a desired value from 5 to 14400.
h) Set the Max. RIR attempts to UTRAN (nRimRirU) parameter's value to a
5 Optional: Blacklist cells for WCDMA.

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

Features
g Note: It is also possible to set the MCC, MNC, MNC length, RNC Id and
UTRAN carrier frequency parameters by expanding the
Blacklisted UTRAN cells for RIM object.
6 Optional: Configure one or more PLMN Ids.

e) Expand the LNMME object.
f) Add New Reachable PLMNs for RIM (rimReachablePLMNList)
parameter.
g) Set the MCC, MNC (mcc, mnc) parameters' value to a desired value from 0 to
999.
h) Set the MNC length (mncLength) parameter's value to a desired value from 2
to 3.
g Note: It is also possible to set the MCC, MNC and MNC length parameters
by expanding the Reachable PLMNs for RIM object.
7 Set the WCDMA neighbor relations which are not considered for redirection.

e) Select the LNCEL object.
f) Expand the LNRELW object.
g) Set the WCDMA neighbor relation identifier (lnRelWId)
h) Set the Redirect with system information
allowed (redirWithSysInfoAllowed) parameter's value to allowed.
i) Set the Target cell Id in UTRAN CGI of related neighbor
cell (uTargetCid) parameter's value to a desired value from 0 to 65535.
j) Set the and Target RNC Id (uTargetRncId) parameter's value to a desired
k) Set the and Target RNC Id (uTargetRncId) parameter's value to a desired
l) Expand the LNRELW object.
m) Select the Primary PLMN identity in CGI of UTRAN neighbor cell object.
n) Set the MCC, MNC (mcc, mnc) parameters' value to a desired value from 0 to
999.
o) Set the MNC length (mncLength) parameter's value to a desired value from 2
to 3.
p) Select the LNCEL object.

Features
q) Set the Threshold th2 WCDMA for RSRP (threshold2) parameter's

value to a desired value from -140 dBm to -43 dBm.
r) Set the Time to trigger for A2 to active WCDMA
measurement (a2TimeToTriggerActWcdmaMess) parameter's value to a
desired value from a drop-down list.
8 Optional: If for a certain frequency, UTRAN SI shall be provided in the RRC Connection
Release message only in case of a CS fallback or only in case of a redirection with
context release, configure the Add UTRAN system information to
redirection message (addUtranSIToRedirMsg) parameter in REDRT, or
MORED, or MODRED instance.
Configuration steps for REDRT instance:

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

e) Add the MODPR object.
f) Expand the MODPR object.
g) Add the MODRED object.
h) Set the Mobility default profile identifier for redirection
(moDRedId) parameter's value to a desired value from 0 to 5.
i) Set the Add UTRAN system information to redirection message
(addUtranSIToRedirMsg) parameter's value to a desired value from drop-
down list.

Features
j) Set the RAT for redirection (redirRat) parameter's value to utraFDD.

k) Set the Redirection priority for CS fallback with
6 or
l) Set the Redirection priority for emergency
m) Set the Redirection priority for UE context
n) Set the UTRA frequency (redirFreqUtra) parameter's value to a desired
Configuration steps for MORED instance.

e) Add the MOPR object.
f) Set the Mobility profile identifier (moPrId) parameter's value to a
g) Select the MOPR object.
h) Add the MORED object.
i) Set the Mobility default profile identifier for redirection
(moRedId) parameter's value to a desired value from 0 to 5.
j) Set the Add UTRAN system information to redirection message
(addUtranSIToRedirMsg) parameter's value to a desired value from a drop-
down list.
k) Set the RAT for redirection (redirRat) parameter's value to utraFDD.
l) Set the Redirection priority for CS fallback with
6 or
m) Set the Redirection priority for emergency
n) Set the Redirection priority for UE context
o) Set the UTRA frequency (redirFreqUtra) parameter's value to a desired
Expected outcome
The LTE1196: RAN Information Management for WCDMA feature has been activated.
RIM associations are established and supervised for all RIM-enabled WCDMA neighbour
cells.

Features
7.4 Deactivating LTE1196: RAN Information

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

2 Deactivate the feature flag of the LTE1196: RAN Information Management for WCDMA
feature.

d) Set the Active RAN Information Management for
UTRAN (actRIMforUTRAN) parameter's value to false.
Expected outcome
The LTE1196: RAN Information Management for WCDMA feature has been deactivated.
RIM associations to UTRAN are terminated. The LNADJW:rimStatus instances are
disabled. All alarms related to RIM for UTRAN feature are cleared.

LTE15A Radio Resource Management and Telecom LTE1321: eRAB Modification – GBR
Features
8 LTE1321: eRAB Modification – GBR

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

adjustment according to UE/MME needs, especially during inter-technology
handovers
• flexible bandwidth usage adjusted to current eNB, MME, and end-user needs
• a dynamic GBR bandwidth increase and decrease when starting or terminating a
VoLTE call and a three-party conference call
Requirements
Functional overview
The LTE1321: eRAB Modification - GBR feature introduces functionalities on top of the
LTE519: eRAB Modification feature. Before the implementation of the LTE1321: eRAB
Modification - GBR feature, the LTE519: eRAB Modification feature allowed, among
others, an ARP parameter modification (in the GBR bearer).
The LTE1321: eRAB Modification - GBR feature additionally allows the guaranteed bit
rate (GBR)-related and maximum bit rate (MBR)-related QoS parameters modification
(for the GBR bearers) to facilitate the requirements made by the MME or UE, as
presented in Table 51: LTE519 and LTE1321 comparison.
Table 51 LTE519 and LTE1321 comparison

LTE519 LTE1321
• non-GBR: • non-GBR:
– QCI – QCI
– ARP – ARP

LTE1321: eRAB Modification – GBR LTE15A Radio Resource Management and Telecom
Features
Table 51 LTE519 and LTE1321 comparison (Cont.)

LTE519 LTE1321
– UE-AMBR – UE-AMBR
• GBR: • GBR:
– ARP – ARP
– GBR
– MBR
In the case of an MBR, the eNB assumes that the value of the MBR equals GBR's value.
GBR's modification is triggered by the following network elements:
• P-GW
In this case, for example, additional resources can be guaranteed for the established
bearer.
• HSS
In this case, for example, additional resources can be added to an aggregated pool
for downloaded data.
P-GW-triggered eRAB modification

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

Features
Figure 8 Complete signaling flow
System impact
There are interdependancies between the LTE1321: eRAB Modification - GBR feature
and the following features:
• LTE9: Service Differentiation

This feature allows assigning relative scheduling weights to each non-GBR QCI on a
cell level. The LTE1321: eRAB Modification - GBR feature can only be activated
when the LTE9: Service Differentiation feature is activated.
The LTE1321: eRAB Modification - GBR feature can modify the parameters for QCI1
bearers introduced by the LTE10: EPS Bearers for Conversational Voice feature.
• LTE13: Rate Capping
The Flexi Multiradio BTS uses the UE-AMBR parameter. The LTE1321: eRAB
Modification - GBR feature modifies the UE-AMBR introduced by the LTE13: Rate
Capping feature.
• LTE518: Operator-specific QCIs
The LTE1321: eRAB Modification – GBR feature modifies the QoS parameters for
operator-specific QCI bearers introduced by the LTE518: Operator-specific QCIs
feature.
• LTE496: Support of QCI 2, 3, and 4
The LTE1321: eRAB Modification – GBR feature can modify parameters for QCI 2, 3,
4 bearers introduced by the LTE496: Support of QCI 2, 3, and 4 feature.
• LTE497: Smart Admission Control
The LTE1321: eRAB Modification - GBR feature can modify the GBR of an EPS
bearer, which has already been admitted by admission control (AC). When the E-
RAB modification is in place, smart admission control mechanisms are triggered to
check if such a modification can be done from a resources' point of view.
• LTE534: ARP-based Admission Control for E-RABs or LTE1231: Operator-specific
GBR QCIs

Features
The LTE534: ARP-based Admission Control for E-RABs feature is based on ARP
priorities, which are considered when a cell is highly loaded. LTE1321: eRAB
Modification - GBR feature can change the ARP priority for the already admitted
bearers.
• LTE587: Multiple GBR EPS Bearers per UE
• LTE519: eRAB Modification
• LTE1231: Operator-specific GBR QCIs
The LTE1321: eRAB Modification - GBR feature can modify parameters for operator-
specific GBR QCIs.
• LTE1401: Measurement-based TAC
g Note: It is not allowed to use the LTE534: ARP-based Admission Control for eRABs
and LTE1231: Operator-specific GBR QCIs features at the same time.
The LTE1321: eRAB Modification - GBR feature is activated along with the
LTE519: eRAB Modification feature, using the same activation parameter.



LTE1321:eRAB modification - GBR requirements, alarms and faults, commands,
Requirements

FDD TDD
Flexi Zone Access Point not supported not supported
Cloud Flexi Zone Controller not supported not supported

Features

FDD TDD
UE 3GPP R8 3GPP R8
Alarms
There are no alarms related to this feature.

Table 53 New counters
M8006C237 Failed modification of E-RABs LTE EPS Bearer
due to "Radio Network Layer
Cause - Radio resources not
available"
M8006C238 Failed modification of E-RABs LTE EPS Bearer
due to "Transport Layer Cause
- Transport Resource
Unavailable"
For counters descriptions, see LTE Radio Access Operating Documentation/

Reference/Counters.

Parameters
Table 54 Modified parameters introduced by LTE1321

Full name Abbreviated Managed Parent FDD/TDD
name object structure
Activate E-RAB actERabModify LNBTS – common
Modification

Sales information

Product structure class License control in network Activated by default
element

Features
8.2 VoLTE/ViLTE call drops when LTE1321 is enabled in

the network
The LTE1321 feature introduces an check on e-RAB-GuaranteedBitrate (GBR) if the
GBR is increased during E-RAB modification. This could lead to VoLTE/ViLTE call drops
during voice/video conference setup phase if the eNB maximum GBR parameters do not
take GBR overhead during voice/video conference setup into account.
Solution
Possible cause
In releases before FL15A/TL15A, the eNB did not check the e-RAB-
GuaranteedBitrateDL/UL if this E-RAB parameter is changed during E-RAB modification
procedure. With introduction of the LTE1321: eRAB modification – GBR feature, the eNB
is checking whether an increased GBR value is still in the allowed range that is defined
by the Maximum GBR uplink and Maximum GBR downlink parameters in QCI1
and QCI2 parameter tables of the LNBTS object, respectively.
If VoLTE or ViLTE calls are extended to include additional parties or if VoLTE/ViLTE
conference calls are started, the E-RAB modification procedure is used to temporarily
increase the QCI1/QCI2 GBR by a factor of 2 or 3. As a consequence, the GBR
configured by an MME for an existing E-RAB might exceed the “Maximum GBR” as
defined in the eNB configuration (LNBTS object) and the call might be dropped.
In order to avoid this call drop during VoLTE/ViLTE conference set-up, it is recommended
to increase the Maximum GBR uplink and Maximum GBR downlink parameters
in QCI1 and QCI2 parameter tables of LNBTS object to at least 3 times the value used
for a simple (non-conference) VoLTE/ViLTE call in order to have sufficient margin for the
GBR increase during conference call setup.
Troubleshooting procedure: Increasing value of maximum GBR

downlink/uplink using BTS SM
Procedure
1 Open BTS Site Manager and establish connection to the BTS.
2 Start commissioning.
3 Go to the Radio Network Configuration page.
4 Go to LNBTS object.

Features
5 Go to QCI translation table QCI 1 (qciTab1).
6 Set the following parameters to value at least 3 times the value used for a simple call.
Parameters:
Maximum GBR downlink (maxGbrDl)
Maximum GBR uplink (maxGbrUl)
7 Repeat step 6 for QCI translation table QCI 2 (qciTab2).

LTE1357: LTE-UTRAN Load Balancing LTE15A Radio Resource Management and Telecom
Features
9 LTE1357: LTE-UTRAN Load Balancing
9.1 LTE1357: LTE-UTRAN Load Balancing

The LTE1357: LTE-UTRAN Load Balancing feature enables load balancing from LTE to
WCDMA.
Benefits
End-user benefits
In case of a highly loaded LTE network, optimized service for the end user is provided.
Operator benefits
The LTE1357: LTE-UTRAN Load Balancing feature reduces the probability of overload
situations in the LTE network due to offloading sufficient UEs to the WCDMA network.
With the LTE1357: LTE-UTRAN Load Balancing feature, the eNB monitors the load in its
own cells. If a cell load is high, the eNB initiates a load-based handover (HO) from an
LTE to a WCDMA cell, as shown in Figure 9: LTE - UTRAN load balancing.
Figure 9 LTE - UTRAN load balancing
3GCORE
eNB NB RNC
eNB
LTECORE
Load supervision
If the LTE1357: LTE-UTRAN Load Balancing feature is activated (the
actUtranLoadBal paramater value is set to true), each cell constantly measures and
calculates the load for GBR, non-GBR, and PDCCH load types. The operator can
configure new load thresholds for these load types. If at least one of the high load
threshold is exceeded, the load balancing function becomes active.

LTE15A Radio Resource Management and Telecom LTE1357: LTE-UTRAN Load Balancing
Features
g Note: Generally, load balancing with inter-RAT targets is started if one of the loadtypes:
loadtype1, loadtype2, or loadtype3 is bigger than the relevant typehighthreshold
(type1highthreshold, type2highthreshold, or type3highthreshold). Load balancing with
inter-RAT targets is stopped if all of the loadtypes: loadtype1, loadtype2, and loadtype3
are smaller than the relevant typetargetthreshold (type1targetthreshold,
type2targetthreshold, and type3targetthreshold).
If the load of all load types in the source LTE cell is reduced below the target threshold,
all load balancing is stopped in that cell. Load balacing is in an inactive state, and the
load monitoring is ongoing.
Load balancing candidates
The UE, to be handed over from an LTE to a WCDMA cell, must be a load balancing
candidate (UE entering the cell, UE in an RRC connected state (every time when the
periodic retry timer of the UE expires), or UE coming in with an HO) and meet the
following conditions:
• The UE has UTRAN UE capabilities (feature group index bit 15 and 114 optionally).
• The UE has data bearers only (no QCI1 bearer).
• An emergency bearer is not active.
• The UE is not configured for carrier aggregation.
• The UE has the B1 measurement objects configured.
• The UE reports sufficient coverage with WCDMA.
The load balancing candidate measures the radio conditions of the WCDMA target cells
using the B1 measurement.
LTE-WCDMA handover
If the S1 handover is triggered for inter-RAT load balancing, the source eNB sets the
Cause IE value to Reduce load in serving cell. As long as load balancing handovers
are accepted, the WCDMA cell is a target cell for load balancing. If the WCDMA target
cell rejects load balancing handovers (cause: No Radio Resources Available in Target
Cell or load reject reasons), the target cell is temporarily blacklisted for load balancing. In
this case, no further load is shifted to that cell.
The eNB allocates a load-balancing handover target list to WCDMA. This target cell list
is taken from the newly-defined white list for load balancing.
System impact
• LTE56: Inter-RAT Handover to UTRAN

The LTE56: Inter-RAT Handover to UTRAN feature must be activated together with
the activation of load balancing.
• LTE1073: Measurement-based Redirect to UTRAN
The LTE1073: Measurement-based Redirect to UTRAN feature must not be
configured to apply redirect to all UEs if the LTE1357: LTE-UTRAN Load Balancing
feature is activated.
• LTE736: CS Fallback to UTRAN
The CS fallback reduces load independently of the LTE1357: LTE-UTRAN Load
Balancing feature.

Features
• If one of the following features is activated along with the LTE1357: LTE-UTRAN
Load Balancing feature, a round robin offloading might be done (either B1 or A4 is
configured for a candidate UE).
– LTE1170: Inter eNB IF Load Balancing
– LTE1387: Intra eNB IF Load Balancing
– LTE1531: Inter-frequency Load Balancing Extension
– LTE1140: Intra eNB IF Load Balancing
• LTE1841: Inter-frequency Load Equalization

If the LTE1841: Inter-frequency Load Equalization and LTE1357: LTE-UTRAN Load
Balancing features are activated parallel to one another, a round robin might be done
(either B1 or A4 is configured for a candidate UE).
A proposal of how to configure several load balancing functions in parallel is as
follows:
– low load in the cell - execution of load equalization
– higher load in the cell - execution of the LTE1170: Inter eNB IF Load Balancing
feature
– much higher load in the cell - execution of the LTE1357: LTE-UTRAN Load
Balancing feature
• LTE1749: MRO Inter-RAT UTRAN

MRO adapts thresholds for an inter-RAT HO.
• LTE2062: Inter-RAT UTRAN Neighbor Relation Robustness, LTE908: ANR Inter-RAT
UTRAN - Fully UE-based
The ANR features and the LTE1357: LTE-UTRAN Load Balancing feature are
mutually exclusive because of set up measurements. It must be avoided that ANR
deletes all UTRAN neighbor cells because then UTRAN load balancing cannot
reduce the load immediately after the highload is triggered.
• LTE2162: SRVCC for Network Deployments Not Supporting PS HO
A UE which is sent to UTRAN by a measurement-based redirect, instead of a PS
HO, is not used for inter-RAT load balancing. If the LTE1357: LTE-UTRAN Load
Balancing feature is activated, the LTE2162: SRVCC for Network Deployments Not
Supporting PS HO feature does not have to be configured to send all UEs without
QCI1 to UTRAN by redirect.
There are dependencies between the load balancing thresholds and the
maxGbrTrafficLimit smart AC threshold. The thresholds should be configured
that the load balancing starts first before the congestion handling is started.
• LTE1103: Load-based Power Saving for Multi-layer Networks
Load balancing and energy saving functions might work in opposite direction,
depending on traffic distribution. The recommendation is that the LTE1103: Load-
based Power Saving for Multi-layer Networks and LTE1357: LTE-UTRAN Load
Balancing features are not used at the same time.


Features
The LTE cells are offloaded due to a unidirectional load balancing mechanism between
LTE and UTRAN cells.

LTE1357: LTE-UTRAN Load Balancing requirements, alarms and faults, commands,
Requirements

FDD TDD
Cloud Flexi Zone Controller FL17A Not supported
OMS Support not needed Not supported
UE 3GPP R8 UE Capabilities Not supported
Alarms
There are no alarms related to the LTE1357: LTE-UTRAN Load Balancing feature.

There are no faults related to the LTE1357: LTE-UTRAN Load Balancing feature.
Commands
There are no commands related to the LTE1357: LTE-UTRAN Load Balancing feature.

M8016C43 Inter System load balancing 8016 - LTE Inter System
handover attempts to UTRAN Handover (WBTS)
M8016C44 Successful Inter System load 8016 - LTE Inter System
balancing handover Handover (WBTS)
completions to UTRAN

Features

M8011C162 High cell load indicator for load 8011 - LTE Cell Resource
balancing to UTRAN (WBTS)
For counter descriptions, see LTE Performance Measurements and Key Performance
Indicators document.

There are no key performance indicators related to the LTE1357: LTE-UTRAN Load
Balancing feature.
Parameters

d object
Activate inter-RAT actUtranLoadBa LNBTS_ - FDD
UTRAN load l FDD
balancing
UTRAN balancing utranLbLoadThr LNCEL_ - FDD
load threshold esholds FDD
DL GBR resource highLoadGbrDl LNCEL utranLbLoadThr FDD
high load esholds
DL non-GBR resource highLoadNonGbr LNCEL utranLbLoadThr FDD
high load Dl esholds
PDCCH high load highLoadPdcch LNCEL utranLbLoadThr FDD
esholds
EcN0 threshold for thresholdEcn0U LNHOW - FDD
load bal. handover tranLbFilter
to UTRAN
RSCP threshold for thresholdRscpU LNHOW - FDD
load bal. handover tranLbFilter
to UTRAN
LTE-UTRAN load utranLbAllowed LNREL - FDD
balancing allowed W

d object
Activate handover actHOtoWcdmal LNBTS - FDD
from LTE to WCDMA
Prohibit Load based prohibitLBHOTi LNBTS - FDD
handover timer mer
Cell resource cellResourceSh LNCEL - FDD
sharing mode aringMode

Features

d object
Filtering filterCoeffici LNCEL - FDD
coefficient used entCpichEcn0
for cpich ecN0
Filtering filterCoeffici LNCEL - FDD
coefficient used entCpichRscp
for cpich RSCP
Inter-frequency iFLBLoadThresh LNCEL - FDD
load balancing load olds
thresholds
Inter-frequency iFLBBearCheckT LNCEL iFLBLoadThresh FDD
load balancing QCI1 imerd olds
Bearer check timer
Inter-frequency iFLBHighLoadGB LNCEL iFLBLoadThresh FDD
load balancing GBR RDL olds
high load DL
Inter-frequency iFLBHighLoadNo LNCEL iFLBLoadThresh FDD
load balancing non- nGBRDL olds
GBR high load DL
Inter-frequency iFLBHighLoadPd LNCEL iFLBLoadThresh FDD
load balancing cch olds
PDCCH high load
Inter Freq Load Bal iFLBRetryTimer LNCEL iFLBLoadThresh FDD
Retry Timer olds
Intra- and inter- loadSettings LNCEL - FDD
freq. load bal.
common load
settings
Cell capacity class cellCapClass LNCEL loadSettings FDD
value
Mode for mlbEicicOperMo LNCEL loadSettings FDD
calculating the CAC de
in load bal. and
eICIC
Nominal number of nomNumPrbNonGb LNCEL loadSettings FDD
PRBs for load r
balancing
DL GBR resource targetLoadGbrD LNCEL loadSettings FDD
target load l
DL non-GBR resource targetLoadNonG LNCEL loadSettings FDD
target load brDl
PDCCH target load targetLoadPdcc LNCEL loadSettings FDD
h
Uplink CAC source ulCacSelection LNCEL loadSettings FDD
selection
Static CAC for ulStaticCac LNCEL loadSettings FDD
uplink

Features

d object
Remove allowed removeAllowed LNREL - FDD
W
For parameter descriptions, see LTE Radio Access Operating

Documentation/Reference/Parameters document.
Sales information

element
9.3 Activating and configuring LTE1357: LTE-UTRAN

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

Load Balancing
object locking
Activate inter-RAT UTRAN load activation flag no
balancing (actUtranLoadBal)
UTRAN balancing load thresholds mandatory configuration no
(utranLbLoadThresholds)
parameters' structure
Inter-frequency load balancing load mandatory configuration no
thresholds (iFLBLoadThresholds)
Activate handover from LTE to mandatory configuration no
WCDMA (actHOtoWcdma)
Prohibit Load based handover optional configuration no
timer (prohibitLBHOTimer)
Cell resource sharing mode optional configuration object locking
(cellResourceSharingMode)
Filtering coefficient used for cpich optional configuration no
ecN0 (filterCoefficientCpichEcn0)
Filtering coefficient used for cpich optional configuration no
RSCP (filterCoefficientCpichRscp)

Features

Load Balancing (Cont.)
object locking
Intra- and inter-freq. load bal. optional configuration no
common load settings
(loadSettings) parameters'
structure
EcN0 threshold for load bal. optional configuration no
handover to UTRAN
(thresholdEcn0UtranLbFilter)
RSCP threshold for load bal. optional configuration no
handover to UTRAN
(thresholdRscpUtranLbFilter)
LTE-UTRAN load balancing optional configuration no
allowed (utranLbAllowed)
Remove allowed (removeAllowed) optional configuration no
The LTE56: Inter-RAT Handover to UTRAN feature needs to be activated

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

2 Activate the LTE1357: LTE-UTRAN Load Balancing feature.

d) Select the LNBTS_FDD object.
e) Set the Activate inter-RAT UTRAN load
balancing (actUtranLoadBal) parameter's value to true.
3 Configure the LNADJW parameters.
a) Right-click the LNBTS object.

b) Select the New LNADJW object.

Features
c) For the LNADJW object, set the parameters' values.

d) Expand the LNADJW object.
e) For the Target primary PLMN identity parameters' structure, set the
parameters' values.
4 Configure the UTRAN balancing load thresholds parameters' structure.

b) Right-click the LNCEL object.

you need to select the LNCEL/LNCEL_FDD object.
c) Select the New UTRAN balancing load thresholds object.
d) For the UTRAN balancing load thresholds parameters' structure, set
the parameters' values as follows:
• DL GBR resource high load (highLoadGbrDl)
g Note: The DL GBR resource target load (targetLoadGbrDl)

parameter's value in the
Intra- and inter-freq. load bal. common load
settings (loadSettings) parameters' structure needs to be lower than or
equal to the DL GBR resource high load (highLoadGbrDl) parameter
in the UTRAN balancing load
thresholds (utranLbLoadThresholds) parameters' structure.
• DL non-GBR resource high load (highLoadNonGbrDl)
• PDCCH high load (highLoadPdcch)
5 Configure the Intra- and inter-freq. load bal. common load

settings parameters' structure.

c) Select the New Intra- and inter-freq. load bal. common load settings object.
d) For the Intra- and inter-freq. load bal. common load
settings parameters' structure, set the parameters' values.
6 Configure the Inter-frequency load balancing load thresholds

parameters' structure.

c) Select the New Inter-frequency load balancing load thresholds object.
d) For the Inter-frequency load balancing load thresholds
parameters' structure, set the parameters' values as follows:

Features
• Inter Freq Load Bal Retry Timer (iFLBRetryTimer)

• Inter-frequency load balancing GBR high load
DL (iFLBHighLoadGBRDL)
• Inter-frequency load balancing non-GBR high load
DL (iFLBHighLoadNonGBRDL)
• Inter-frequency load balancing PDCCH high
load (iFLBHighLoadPdcch)
• Inter-frequency load balancing QCI1 Bearer check timer
(iFLBBearCheckTimer)
7 Configure the other LNBTS parameters (optional).
a) Select the LNBTS object.

b) Set the parameters' values as follows:
• Prohibit Load based handover timer (prohibitLBHOTimer)
8 Configure the other LNCEL parameters (optional).

c) Set the parameters' values as follows:
• Cell resource sharing mode (cellResourceSharingMode)
g Note: For the cellResourceSharingMode different that none, set additional

parameters as follows:
– Assigned cell resource group
profile (cellResourceGroupPrId) LNCEL parameter
–
1. Right-click the LNBTS object.
2. Select the New CRGPR object.
3. For the CRGPR object, set the parameters' values.
– Set the Activate downlink interference

shaping (actDlIntShaping) LNBTS parameter's value to false.
– Set the DL interference shaping active (actDlIsh) parameter's
value in the Downlink interference shaping
configuration (dlIshConfig) parameters' structure to false.
– Set the Activate inter-RAT UTRAN load
balancing (actUtranLoadBal) LNBTS parameter's value to false.
• Filtering coefficient used for cpich

ecN0 (filterCoefficientCpichEcn0)
• Filtering coefficient used for cpich
RSCP (filterCoefficientCpichRscp)

Features
• Intra- and inter-freq. load bal. common load

settings (loadSettings) parameters' structure
9 Configure the LNHOW parameters (optional).

b) Select the New LNHOW object.
c) For the LNHOW object, set the parameters' values as follows:
• EcN0 threshold for load bal. handover to
UTRAN (thresholdEcn0UtranLbFilter)
• RSCP threshold for load bal. handover to
UTRAN (thresholdRscpUtranLbFilter)
• Neighbor WCDMA BTS cell handover identifier (lnHoWId)
10 Configure the LNRELW parameters (optional).

b) Select the New LNRELW object.
c) For the LNRELW object, set the parameters' values as follows:
• LTE-UTRAN load balancing allowed (utranLbAllowed)
• Remove allowed (removeAllowed)
• WCDMA neighbor relation identifier (lnRelWId)
• Target cell Id in UTRAN CGI of related neighbor
cell (uTargetCid)
• Target RNC Id (uTargetRncId)
•
1. Expand the LNRELW object.
2. For the Primary PLMN identity in CGI of UTRAN neighbor
cell (plmnId) parameters' structure, set the parameters' values.
Expected outcome
• The LTE1357: LTE-UTRAN Load Balancing feature is activated.

• The eNB starts CAC monitoring in all its cells.

Features
9.4 Deactivating LTE1357: LTE-UTRAN Load Balancing

Before you start
The Activate inter-RAT UTRAN load balancing (actUtranLoadBal)
parameter is used for deactivation. Modification of this parameter requires neither eNB
restart nor cell locking.
Procedure

2 Deactivate the LTE1357: LTE-UTRAN Load Balancing feature.

d) Select the LNBTS_FDD object.
e) Set the Activate inter-RAT UTRAN load
balancing (actUtranLoadBal) parameter's value to false.
Expected outcome
The LTE1357: LTE-UTRAN Load Balancing feature is deactivated.

LTE1635: SIB8 AC barring for 1xRTT LTE15A Radio Resource Management and Telecom
Features
10 LTE1635: SIB8 AC barring for 1xRTT
10.1 Description of LTE1635: SIB 8 AC Barring for

1xRTT
The LTE1635: SIB 8 AC Barring for 1xRTT feature supports the dedicated access class
(AC) barring for 1xRTT as an extension of LTE1441: Enhanced CS Fallback to
CDMA/1xRTT (e1xCSFB). The 1xRTT AC barring information is broadcast as part of
system information block 8 (SIB8).
Benefits
End-user benefits
This feature provides an equally effective access bar as the one in a native network
during CS fallback.
Operator benefits
This feature guarantees CS services without the expense of deploying an IMS core and
VoIP applications.
Requirements
The LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature is deployed in
the LTE network and CDMA2000 1xRTT network in the same geographical area, where
the 1xRTT network always has overlapping coverage with the LTE network. In a situation
when the 1xRTT network conditions are overloaded, it is reasonable to relieve it by
managing the native 1xRTT layer.
The 1xRTT AC barring information is broadcast as part of system information block 8
(SIB8) to the UEs. Parameters for 1xRTT AC barring are operator-configurable. The eNB
supports adapting SIB8 1xRTT AC barring broadcast on the air interface, based on the
combination of:
• the SIB8 1xRTT AC barring O&M configuration value

• the SIB2:ac-BarringInfo IE value
The algorithm of ac-Barring0To9-r9 IE adaption, based on SIB2 AC barring

information, is not applied if acBarring0To9Adapt = false. The ac-
Barring0To9-r9 IE of SIB8 should be set as RttAcbDb.
Otherwise, the algorithm of ac-Barring0To9-r9 IE adaption, based on SIB2 AC
barring information, is applied.

LTE15A Radio Resource Management and Telecom LTE1635: SIB8 AC barring for 1xRTT
Features
The RttAcbDb factor is a source one, expected by the operator of the CDMA AC
barring pass rate in CDMA 1xRTT native network. In case of static 1xAC barring, the
RttAcbDb = CDFIM:rttAcBar:acBarring0To9 or in case of automatic 1xAC
barring, CDFIM:rttAcBarOvl:acBarring0To9. The 1xACB adaption is applicable
for both static AC barring and automatic AC barring for overload.
g Note: RttAcbDb = 0 means that the operator expects the CDMA AC barring pass
rate equal 100% for the CDMA access overload class 0-9 native 1xRTT network. There
is no need to enforce any extra LTE SIB8 AC barring.
RttAcbDb = 63 means that the operator expects the CDMA AC barring pass rate
equal 0% for the CDMA access overload class 0-9 native 1xRTT network.
Because SIB8 1xRTT AC barring will only apply to UE's that have successfully accessed
the LTE network, and SIB2 LTE AC barring may prevent some accessing, this can result
in a higher overall 1xRTT barring than the customer might desire. The purpose of
Adaption is to adjust the barring factors in SIB8 slightly based on how much SIB2 barring
is in effect, to give the customer the same overall 1xRTT AC barring they would see on
the native 1xRTT system with the same 1xRTT database settings.
In the LTE1635: SIB 8 AC Barring for 1xRTT feature, when a UE is in R8/R9 1xCSFB
mode access 1xRTT network via LTE access the LTE1441: Enhanced CS Fallback to
CDMA/1xRTT (e1xCSFB) feature, during 1xCSFB, 1xSMS, 1xRegistration and others,
will follow both SIB8 AC barring and SIB2 AC barring.
System impact
Activation of the LTE1635: SIB 8 AC Barring for 1xRTT feature is meaningful only when
the LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature is activated,
and SIB8 CSFB-RegistrationParam1xRTT IE is broadcast. When a UE is in
R8/R9 e1xCSFB mode, access the 1xRTT network via the LTE network; the SIB8 AC
barring is following together with SIB2 AC barring.
The LTE1635: SIB 8 AC Barring for 1xRTT feature is not supported by the following
features:
• LTE874: DualRx 1xCSFB

SIB8 AC barring is not applicable the DualRx 1xCSFB since there is no interworking
between the LTE/EPC network and 1XRTT network.
g Note: When a UE is in DualRx, 1xCSFB mode triggers

EMM:Extended Service Request for CS fallback; then, only SIB2 AC
barring will be followed while SIB8 AC Barring will be skipped.
• LTE116: Cell Bandwidth - 3 MHz
SIB8 AC barring is not supported on the 3MHz LTE cell bandwidth since the
LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature is not
supported on the 3MHz LTE cell bandwidth.
• LTE117 Cell Bandwidth - 1.4 MHz
SIB8 AC barring is not supported on the 1.4MHz LTE cell bandwidth since the
LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature is not
supported on the 1.4MHz LTE cell bandwidth.
Management data

Features
Sales information

Requirements

FDD TDD
System release FDD-LTE15A TD-LTE15A
Flexi Zone Controller FL16 TL16
OMS Support not required Support not required
NetAct 15.5 15.5
Alarms
There are no alarms related to the LTE1635: SIB 8 AC Barring for 1xRTT feature.

There are no faults related to the LTE1635: SIB 8 AC Barring for 1xRTT feature.
Commands
There are no commands related to the LTE1635: SIB 8 AC Barring for 1xRTT feature.

There are no measurements or counters related to the LTE1635: SIB 8 AC Barring for
1xRTT feature.

There are no key performance indicators related to the LTE1635: SIB 8 AC Barring for
1xRTT feature.
Parameters

Features

name object
AC barring 0To9 adaption acBarring0To9Ada CDFIM - common
pt
AC barring for CDMA2000 rttAcBar CDFIM - common
1xRTT
AC barring factor for acBarring0To9 CDFIM rttAcBar common
overload classes 0 to 9
AC barring factor for acBarring10 CDFIM rttAcBar common
overload class 10
overload class 11
overload class 12
overload class 13
overload class 14
overload class 15
AC barring factor for acBarringEmg CDFIM rttAcBar common
emergency
AC barring modification acBarringMsg CDFIM rttAcBar common
factor for message
AC barring modification acBarringReg CDFIM rttAcBar common
factor for registration
Sales information

10.3 Activating and configuring LTE1635: SIB 8 AC

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

Features
Table 65 Parameters used for activating and configuring LTE1635: SIB 8 AC Barring
for 1xRTT
object locking
AC Barring for CDMA2000 1xRTT activation flag no
(rttAcBar)
AC Barring 0To9 adaptation mandatory configuration no
(acBarring0To9Adapt)
AC Barring factor for overload mandatory configuration no
classes 0 to 9 (acBarring0To9)
AC Barring factor for emergency mandatory configuration no
(acBarringEmg)
classes 10 (acBarring10)
AC Barring modification factor for mandatory configuration no
message (acBarringMsg)
AC Barring modification factor for mandatory configuration no
registration (acBarringReg)
The LTE1441 Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) feature needs to be

activated before the activation of the LTE1635: SIB 8 AC Barring for 1xRTT feature.
Procedure

2 Activate the feature flag of the LTE1635: SIB 8 AC Barring for 1xRTT feature.


Features

f) Select the CDFIM object.
g) Set the AC Barring 0To9 adaptation (acBarring0To9Adapt)
parameter's value to true or false.
h) If the AC Barring 0To9 adaptation (acBarring0To9Adapt)
parameter's value is set to true, do the following:
• Select the LNCEL object.
• Add the Access class barring for originating
calls (acBarOc) parameter.
• Set the Access class barring time for originating
calls (ocAcBarTime) parameter's value to a desired value from a drop-
down list.
• Set the Access probability factor for originating
calls(ocAcProbFac) parameter's value to a desired value from a drop-
down list.
i) Select the CDFIM object.

j) Add the AC Barring for CDMA2000 1xRTT (rttAcBar) object.
k) Set the AC Barring factor for overload classes 0 to
9 (acBarring0To9) parameter's value to a desired value from 0 to 63.
g Note: It is also possible to set the

AC Barring factor for overload classes 0 to
9 (acBarring0To9) parameter's value by expanding the
AC Barring for CDMA2000 1xRTT object.
3 Optional: Change parameters' default value of the CDFIM:rttAcBar instance.
a) If it is necessary, change the value of listed parameters:

• the AC Barring factor for overload classes
10 (acBarring10) parameter's value to a desired value from 0 to 7.
• the AC Barring modification factor for
message (acBarringMsg) parameter's value to a desired value from 0 to
7.
• the AC Barring factor for emergency (acBarringEmg)

Features
• the AC Barring modification factor for

registration (acBarrinReg) parameter's value to a desired value from
0 to 7.
Expected outcome
The validation of the configuration plan file is successfully done; the LTE1635: SIB 8 AC
Barring for 1xRTT feature is activated.
Further information
A warning will be issued if any of the parameters of the CDFIM:rttAcBar structure or
acBarring0To9Adapt parameter are changed, which results in that SIB1
systemInfoValueTag changes more than 31 times in three hours.
10.4 Deactivating LTE1635: SIB 8 AC Barring for 1xRTT

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

2 Deactivate the feature flag of the LTE1635: SIB 8 AC Barring for 1xRTT feature.


Features

f) Expand the LNCEL object.
g) Expand the CDFIM object.
h) Delete the rttAcBar instance.
g Note: The CDFIM:rttAcBar structure and its mandatory parameters can be

modified online, which means the activation of this delta plan will not cause a
service outage in case the configuration plan file contains only these parameters.
Expected outcome
The validation of the configuration plan file is successfully done; the LTE1635: SIB 8 AC
Barring for 1xRTT feature is deactivated.

LTE1679: DRX with Parallel UE Measurement Gaps LTE15A Radio Resource Management and Telecom
Features
11 LTE1679: DRX with Parallel UE Measurement

Gaps
11.1 Description of LTE1679: DRX with Parallel UE

Measurement Gaps
The LTE1679: DRX with Parallel UE Measurement Gaps feature allows using
discontinuous reception (DRX) for a UE when a measurement gap is installed. The
objective of this feature is to increase a UE's battery savings.
Benefits
End-user benefits
This feature increases a UE's battery savings achieved by using DRX during the time
when a measurement gap is installed.
Operator benefits
This feature is operator-modifiable, but it has no direct impact on the operator's actions.
Requirements
Functional overview
The LTE1679: DRX with Parallel UE Measurement Gaps feature is an extension of the
LTE42: Support of DRX in RRC Connected Mode feature that introduced the support of
DRX in a CONNECTED mode. It brought an eNB's support for discontinuous monitoring
of the DL control channel (PDCCH) by the UE (DRX). This solution employed a periodic
active/sleep pattern, thus creating phases where the UE is not able to receive or transmit
data instantaneously. For more information about the support of DRX in an RRC
connected mode, see LTE42: Support of DRX in RRC Connected Mode. The solutions in
both of the features allow increasing a UE's battery lifetime. Maximum power savings are
expected for a very bursty kind of traffic patterns (short phases with data followed by
long phases with no data at all) and very long inactivity time, however, at the expense of
increasing the DL latency (at the start of a downlink data transmission).
g Note: The LTE1679: DRX with Parallel UE Measurement Gaps feature can be enabled
only if the LTE42: Support of DRX in RRC Connected Mode feature is enabled.
The description of this feature comprises the following:
• Measurement gaps in DRX mode
• Measurement gap installation
• Alignment of measurement gaps
• DRX/measurement gaps activation rules
Measurement gaps in DRX mode

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

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

, the
When the DRX and measurement gaps compete, and the LTE1679: DRX with Parallel
UE Measurement Gaps feature is activated, the eNB proceeds as follows:

Features
• If the measurement gaps are already enabled and the DRX profile needs to be set
up at the UE, the eNB releases the measurement gaps and sets the DRX profile if
and only if the DRX is required for resolving the cell identity of a target cell for a
handover, or the measurements which are currently using the gaps are not event-
based. Otherwise, measurement gaps are always kept.
• When the conditions for keeping the measurement gaps or the DRX profile end, the
eNB evaluates whether to set up another DRX profile or measurement gaps,
depending on the actual RRC connection status.
System impact
The following feature has to be enabled before the activation of the LTE1679: DRX with
Parallel UE Measurement Gaps feature:
• LTE42: Support of DRX in RRC Connected Mode
The following features do not cooperate with the LTE1679: DRX with Parallel UE
Measurement Gaps feature:
• LTE736: CS Fallback to UTRAN

• LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB)
The LTE1679: DRX with Parallel UE Measurement Gaps feature allows the DRX to be
considered during non-CSFB measurement gaps. During CSFB measurement gaps, the
DRX has to be disabled.
The following features cooperate with the LTE1679: DRX with Parallel UE Measurement
Gaps feature:
• LTE56: Inter RAT Handover to WCDMA

• LTE442: Network Assisted Cell Change to GSM
The features utilize the measurement gaps. Previously, the DRX had to be disabled
when a measurement gap was installed. The LTE1679: DRX with Parallel UE
Measurement Gaps feature removes this restriction so that the DRX can potentially stay
enabled during the time when a measurement gap is installed in the UE.


Requirements

Features

FDD TDD
NetAct 15.5 15.5
UE 3GPP R8 mandatory 3GPP R8 mandatory
Alarms
There are no alarms related to the LTE1679: DRX with Parallel UE Measurement Gaps
feature.

There are no faults related to the LTE1679: DRX with Parallel UE Measurement Gaps
feature.
Commands
There are no commands related to the LTE1679: DRX with Parallel UE Measurement
Gaps feature.

There are no measurements or counters related to the LTE1679: DRX with Parallel UE
Measurement Gaps feature.

There are no key performance indicators related to the LTE1679: DRX with Parallel UE
Parameters

name object
Activate DRX actDrxDuringM LNCEL - common
during measurement easGap
gap

Features

name object
Activate DRX actDrx LNCEL - common

Sales information

11.3 Activating and configuring LTE1679: DRX with

Parallel UE Measurement Gaps
Before you start
The Activate DRX during measurement gap (actDrxDuringMeasGap)
parameter is used to activate the LTE1679: DRX with Parallel UE Measurement Gaps
feature. Modification of this parameter requires neither an eNB restart nor cell locking.
The following features have to be enabled before the activation of the LTE1679: DRX
with Parallel UE Measurement Gaps feature:
• LTE42: Support of DRX in RRC Connected Mode
Table 70 Parameters used for activating and configuring LTE1679: DRX with Parallel
UE Measurement Gaps
object locking
Activate DRX during measurement activation flag no
gap (actDrxDuringMeasGap)
Activate DRX (actDrx) mandatory configuration no
Procedure


Features
2 Activate the LTE1679: DRX with Parallel UE Measurement Gaps feature.

d) Select the LNCEL object corresponding to the cell where the LTE1679: DRX with
Parallel UE Measurement Gaps feature is being activated.
e) Set the Activate DRX (actDrx) parameter to true.
f) Set the Activate DRX during measurement
gap (actDrxDuringMeasGap) parameter to true.
Expected outcome
The LTE1679: DRX with Parallel UE Measurement Gaps feature is activated and allows
using discontinuous reception (DRX) for a UE when a measurement gap is installed.
11.4 Deactivating LTE1679: DRX with Parallel UE

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

2 Deactivate the LTE1679: DRX with Parallel UE Measurement Gaps feature.

d) Select the LNCEL object corresponding to the cell where the LTE1679: DRX with
Parallel UE Measurement Gaps feature is being deactivated.

Features
e) Set the Activate DRX during measurement

gap (actDrxDuringMeasGap) parameter to false.
Expected outcome
The LTE1679: DRX with Parallel UE Measurement Gaps feature is deactivated.

LTE15A Radio Resource Management and Telecom LTE1784: Carrier Aggregation for Supercell up to 2CC
Features
12 LTE1784: Carrier Aggregation for Supercell

up to 2CC
12.1 Description of LTE1784: Carrier Aggregation for

Supercell up to 2CC
The LTE1784: Carrier Aggregation for Supercell up to 2CC feature enables the Flexi
Multiradio BTS to support the enhanced supercell interworking with carrier aggregation
(CA) up to two component carriers (CCs).
Benefits
End-user benefits
This feature offers the end user an improved downlink (DL) throughput with two carriers
aggregated on the supercells.
Operator benefits
This feature provides higher peak rate for supercell users (for example, indoor cell with
remote radio head (RRH)).
Requirements
The LTE1784: Carrier Aggregation for Supercell up to 2CC feature enables the Flexi
Multiradio BTS to support the enhanced supercell interworking with CA up to two CCs.
This feature only supports the deployment scenario 1 as defined by the 3rd Generation
Partnership Project (3GPP) for CA.
The following band combinations are supported for DL CA with supercell configuration:
• band 38 + band 38
The following are the supported transmission modes (TMs) with supercell CA:
• CA (PCell + SCell): TM1 + TM1
• CA (PCell + SCell): TM2/3/4 + TM2/3/4
g Note: The TM between the primary cell (PCell) and secondary cell (SCell) can
be different among the TM2, TM3, and TM4.
For the supported site configurations, see the LTE1778: RL55 Site configuration CPRI
feature description.

LTE1784: Carrier Aggregation for Supercell up to 2CC LTE15A Radio Resource Management and Telecom
Features
g Note: This feature is only applied to a supercell indoor scenario. For more details, see
the LTE1558: TDD Downlink Carrier Aggregation and
LTE1830: TDD Downlink Carrier Aggregation Enhancement feature descriptions.
System impact
This feature is enabled together with the following features:
• LTE1558: TDD Downlink Carrier Aggregation
• LTE1830: TDD Downlink Carrier Aggregation Enhancement
g Note: The LTE1558: TDD Downlink Carrier Aggregation and

LTE1830: TDD Downlink Carrier Aggregation Enhancement features have the same
activation flag, which is the actDLCAggr parameter.
This feature depends on the following features:

• LTE1778: RL55 Site configuration CPRI
This feature introduces FSIH-based indoor dual carrier supercell configurations. It is
the site configuration for supercell CA and it defines the digital signal processor
(DSP) deployment for a supercell, which is the base for a supercell CA case.
• LTE48: Support of High Speed Users
This feature introduces the new supercell solution where the supercell for CA is
based from.
• LTE993: Cell Combination (Super cell)
This feature originally introduces the supercell. It is enhanced in the LTE48: Support
of High Speed Users feature.
This feature is affected by the following features:

• LTE1545: UL MU MIMO 8Rx
This feature must be disabled if the LTE1784: Carrier Aggregation for Supercell up to
2CC feature is enabled because the supercell and the uplink (UL) multiple inputs
multiple outputs (MIMO) cannot coexist.
• LTE1691: Uplink intra-eNB CoMP 4Rx
The supercell must be disabled when this feature is enabled and when the LNCEL
instance belongs to the ulCoMpCellList parameter. The supercell CA is disabled
respectively.


The user equipment (UE) DL throughput is increased with two carriers aggregated.
Only 20 MHz + 20 MHz CA is supported in this feature.

Features
• The maximum number of CA-configured UEs per cell is 100 in case the physical
uplink control channel (PUCCH) format 3 resource is configured. In case the PUCCH
format 3 resource is not configured, the maximum number of CA-configured UEs per
cell is 80.
• The maximum number of RRC_Connected UEs per cell is 600.
• The maximum number of scheduled UEs per cell per transmission time interval (TTI)
is 12.
Management data
Sales information

Requirements

FDD TDD
UE Not supported 3GPP R10 UE capabilities
Alarms
There are no alarms related to the LTE1784: Carrier Aggregation for Supercell up to 2CC
feature.

There are no faults related to the LTE1784: Carrier Aggregation for Supercell up to 2CC
feature.
Commands

Features
There are no commands related to the LTE1784: Carrier Aggregation for Supercell up to
2CC feature.

There are no measurements or counters related to the LTE1784: Carrier Aggregation for
Supercell up to 2CC feature.

There are no key performance indicators related to the LTE1784: Carrier Aggregation for
Supercell up to 2CC feature.
Parameters

name object
Activate actSuperCell LNCEL_TDD - TDD
supercell
configuration
Max number of maxNumScells LNCEL - TDD
secondary cells
for DL carrier
aggr
Activation of actDLCAggr LNBTS - TDD
downlink carrier
aggregation
For parameter descriptions, see LTE Operating Documentation/ Reference/ Parameters.
Sales information

12.3 Activating and configuring LTE1784: Carrier

Aggregation for Supercell Up to 2CC
Before you start
The Activate supercell configuration (actSuperCell) parameter
(available in the Cell Resource page) must be enabled. Enabling this parameter
requires evolved Node B (eNB) restart.
The LTE1784: Carrier Aggregation for Supercell Up to 2CC feature is enabled together
with the LTE1558: TDD Downlink Carrier Aggregation and LTE1830: TDD Downlink
Carrier Aggregation Enhancement features.

Features
g Note: The LTE1558: TDD Downlink Carrier Aggregation and

LTE1830: TDD Downlink Carrier Aggregation Enhancement features use the same
activation flag, which is the Activation of downlink carrier aggregation
(actDLCAggr) parameter. For more information about feature dependencies, see
Interdependencies between features.
The LNCEL-Downlink MIMO mode (dlMimoMode) parameter must be set to

SingleTx for one transceiver (1TRX) supercell configuration and TXDiv, Dynamic Open
Loop MIMO, or Closed Loop MIMO (2x2) for 2TRX supercell configuration.
In operating the CA features, it might be necessary to set the link speed parameter.
This is described in the Commissioning Flexi Multiradio BTS LTE document. Note that
the default value (Auto) of this parameter is normally the optimal selection.
Procedure

procedure, perform the steps described in this procedure.
2 Configure the Activation of downlink carrier

aggregation (actDLCAggr) parameter.

d) Set the Activation of downlink carrier
aggregation (actDLCAggr) parameter value to true.
g Note: The Scheduling CA fairness control

factor (caSchedFairFact) and Carrier aggregation pool
ID (caPoolId) parameters must be configured when the
Activation of downlink carrier aggregation (actDLCAggr)
parameter is set to true.
3 Create a new CADPR object.
a) Right-click the selected LNBTS object.

b) Create a new CADPR object.
c) Define the value of each parameter within this object.
g Note: The default values for the parameters within this object are set.
Modification of the default values is not mandatory.

Features
4 Create a new CAREL object.

c) Create a new CAREL object
d) Define the value of each parameter within this object.
Expected outcome
The LTE1784: Carrier Aggregation for Supercell Up to 2CC is enabled in the eNB.
12.4 Deactivating LTE1784: Carrier Aggregation for

Supercell Up to 2CC
Before you start
The Activate supercell configuration (actSuperCell) parameter
(available in the Cell Resource page) must be enabled.
Procedure



aggregation (actDLCAggr) parameter value to false.
g Note: CA is completely deactivated when the parameter value is set to false.

Features
Expected outcome
The LTE1784: Carrier Aggregation for Supercell Up to 2CC feature is disabled in the
eNB.

LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers LTE15A Radio Resource Management and Telecom
Overall Features
13 LTE1787: TM9 with 8TX MU-MIMO and Up to 2

Layers Overall
13.1 Description of LTE1787: TM9 with 8TX MU-MIMO

and Up to 2 Layers Overall
The LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall feature enables
spatial multiplexing of two beamforming users. As a result, the radio resources are
maximally exploited while the cell coverage performance and cell throughout are
improved. The feature is an extension of the LTE1169: LTE TM8-based Dual-user Single-
layer MU-MIMO feature and supports TM9 MU-MIMO and TM8 MU-MIMO as well as the
pairing of UEs in both modes.
Benefits
End-user benefits
This feature improves user experience with better network coverage, faster download
speed, and shorter latency due to a higher spectral efficiency, cell throughput and
capacity.
Operator benefits
This feature increases the cell coverage via the pairing of two single-layer users. Due to
multiplexing two beamforming users spatially, the radio resources are maximally
exploited and the cell coverage performance as well as cell throughout are improved.
Functional differences between the LTE1787: TM9 with 8TX MU-MIMO and Up to 2
Layers Overall and the LTE1169: LTE TM8 based Dual-user Single-layer MU-MIMO
features
The LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall feature is an
extension of the LTE1169: LTE TM8-based Dual-user Single-layer MU-MIMO feature,
and there are following updates introduced:
• Pairing algorithm update for TM9 MU-MIMO
The algorithm has been adopted to predict the MU gain before pairing.
• Multi-User interference aware link adaptation update for TM9 MU-MIMO
An additional compensation for a power difference between TM8 UEs and TM9 UEs
has been introduced.
• TM8 UEs MU-MIMO handling within CSI-RS sub-frames
TM8 UEs are allowed to be paired in CSI-RS subframes. In this case, the impact
from both the CSI-RS and MU will be considered in link adaptation.
• Update of Multi-User interference aware pairing
An update of the algorithm which calculates gain for separated UEs has been
introduced.

LTE15A Radio Resource Management and Telecom LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers
Features Overall
MU-MIMO is a set of advanced MIMO technology. It can be seen as an extended

concept of the SDMA (space-division multiple access), which allows transmitting a signal
to multiple users with the same resources simultaneously. For more information, see
LTE1169: LTE TM8-based Dual-user Single-layer MU-MIMO.
In the LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall feature, the Flexi
Multiradio BTS supports DL MU MIMO evolved to Transmission Mode 9 (TM9) and
applicable to the 8TX antenna system. This feature is dependent on the LTE1169: LTE
TM8-based Dual-user Single-layer MU-MIMO feature and enables pairing TM9 UEs with
TM8 UEs or other TM9 UEs in the following manner:
• TM8 UE + TM8 UE pairing (covered by the LTE1169: LTE TM8-based Dual-user

Single-layer MU-MIMO
• TM8 UE + TM9 UE pairing
• TM9 UE + TM9 UE pairing
In order to guarantee fairness, two UEs can be paired only if each UE benefits a higher
spectrum efficiency (SE) from the MU. More specifically, one UE can be paired only if its
SE in an MU PRB is larger than half of its SE in an SU PRB.
One critical difference between TM8 and TM9 is the feedback of channel state
information (CSI). TM8 gets the CSI from the SRS measurement while TM9 gets it from
a UE report. TM8 uses a hybrid-BF algorithm to derive the pre-coding weights while TM9
uses the reported precoding matrix indicator (PMI) for pre-coding weights. Although their
CSI feedback is different, they calculate the pre-coding weights for the same channel
and the same cell polarized antenna deployment. This indicates that TM8 and TM9 are
similar. In the LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall feature, the
pairing is improved by:
• MU interference-aware pairing
• MU interference-aware link adaptation
The underlying idea of the MU interference-aware pairing and link adaptation is to predict
MU modulation and coding scheme (MCS), as well as the MU gain based on two factors:
correlation and its own CQI.
System impact
The following features are the basis of the LTE1787: TM9 with 8TX MU-MIMO and Up to
2 Layers Overall feature:
• LTE 1169: LTE TM8-based Dual-user Single-layer MU-MIMO and LTE2022:

Beamforming Enhancement
The LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall feature adapts
and reuses the algorithm used in the features.
• LTE 1543: 8x2 SU MIMO with TM9
A TTI and RBG-based dynamic switch between a single-user beamforming (SU-
MIMO) and multi-user beamforming (MU-MIMO) is required; that is, the TM9 capable
user may dynamically stay on a single-user single-layer beamforming mode (TM9,
single CW, SU-MIMO mode), single-user dual-layer beamforming mode (TM9, two
CWs, SU-MIMO mode), or a dual-user single-layer beamforming mode (TM9, single
CW, MU-MIMO mode).
• LTE541: Dual layer beamforming

Overall Features
The feature introduced a dual-layer beamforming TM8, which is the base of the LTE
1169: LTE TM8-based Dual-user Single-layer MU-MIMO and the LTE1787: TM9 with
8TX MU-MIMO and Up to 2 Layers Overall features.
• LTE496: Support of QCI 2, 3 and 4
The feature introduced an updated DL scheduling method which is used in the
LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall feature.
The following features have to be enabled before the activation of the LTE1787: TM9
with 8TX MU-MIMO and Up to 2 Layers Overall feature:
• LTE31: Link Adaptation by AMC (UL/DL)

• LTE1170: Inter-frequency Inter-eNB Load Balance
The following feature has to be considered when calculating MU interference from TM8
or TM9 UEs to TM8 UEs:
• LTE1783: Constrained Beamforming

This feature increases the cell capacity via pairing two single-layer users.

LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall requirements, alarms
and faults, commands, measurements and counters, KPIs, parameters, and sales
information
Requirements

FDD TDD
Nokia AirScale BTS Not supported Not supported
Flexi Zone Access Point Not supported TL16A

Features Overall

FDD TDD
Alarms
There are no alarms related to the LTE1787: TM9 with 8TX MU-MIMO and Up to 2
Layers Overall feature.

There are no faults related to the LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers
Overall feature.
Commands
There are no commands related to the LTE1787: TM9 with 8TX MU-MIMO and Up to 2
Layers Overall feature.

M8010C70 TM9 dual-user single-stream LTE Power and Quality DL
mode


There are no key performance indicators related to the LTE1787: TM9 with 8TX MU-
MIMO and Up to 2 Layers Overall feature.
Parameters

name object
Activate Downlink MU- actDlMuMimo LNCEL_FD - FDD
MIMO D
Activate Downlink MU- actDlMuMimo LNCEL_TD - TDD
MIMO D
Downlink MU-MIMO dlMuMimoParSet LNCEL_FD - FDD
Parameter Set D
Downlink MU-MIMO dlMuMimoParSet LNCEL_TD - TDD
Parameter Set D
MU gain maximization actDlMuGainMax LNCEL dlMuMimoParSet TDD

Overall Features

name object
Downlink MU-MIMO dlMuMimoCorrThd LNCEL dlMuMimoParSet TDD
correlation threshold
Downlink MU-MIMO CQI dlMuMimoCqiThd LNCEL dlMuMimoParSet TDD
threshold
Sales information

element
ASW Pool license No
13.3 Activating and configuring LTE1787: TM9 with 8TX

MU-MIMO and Up to 2 Layers Overall
Before you start
The Activate Downlink MU-MIMO (actDlMuMimo) parameter is used to activate
the LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall feature.
The TM9 SU-MIMO is a prerequisite for the TM9 MU-MIMO. To activate TM9 SU-MIMO,
the Closed Loop MIMO (8x2) has to be selected as a value of the MIMO mode, and the
object locking is required.
The activation of the LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall
feature requires object locking also if any parameter in the CSI-RS configuration
information structure needs to be changed.
Table 78 Parameters used for activating and configuring LTE1787: TM9 with 8TX
MU-MIMO and Up to 2 Layers Overall
object locking
Activate Downlink MU-MIMO activation flag no
(actDlMuMimo)
CSI reporting submode mandatory configuration no
(csiRepSubmode)
CSI-RS ports number mandatory configuration object locking
(numOfCsiRsAntennaPorts)
CSI-RS power offset mandatory configuration object locking
(csiRsPwrOffset)
CSI-RS configuration mandatory configuration object locking
(csiRsResourceConf )

Features Overall
Table 78 Parameters used for activating and configuring LTE1787: TM9 with 8TX
MU-MIMO and Up to 2 Layers Overall (Cont.)
object locking
CSI-RS subframe configuration mandatory configuration object locking
(csiRsSubfrConf)
MU gain maximization optional configuration no
(actDlMuGainMax)
Downlink MU-MIMO correlation optional configuration no
threshold (dlMuMimoCorrThd)
Downlink MU-MIMO CQI threshold optional configuration no
(dlMuMimoCqiThd)
The following conditions must be met before the activation of the LTE1787: TM9 with
8TX MU-MIMO and Up to 2 Layers Overall feature:
• Antenna system with eight antenna elements in a transmit direction must be

prepared.
• The LTE31: Link Adaptation by AMC (UL/DL) feature must be enabled: the Rank
indication reporting enable (riEnable) parameter must be set to true.
• The LTE497: Smart Admission Control feature must be enabled: the Activate
enhanced AC and GBR services (actEnhAcAndGbrServices) parameter
must be set to true.
• The LTE1170: Inter-frequency Inter-eNB Load Balance feature must be enabled: the
Activation of inter-frequency load balancing (iFLB)
(actInterFreqLB) parameter must be set to true, and Inter-frequency
load balancing load thresholds list must exist.
• At least one of the parameters: Activate support of conversational
voice bearer (actConvVoice), actEnhAcAndGbrServices must be set to
true.
• The Enable DL AMC (dlamcEnable) must be configured to true.
Procedure

2 Configure the cell resources.

b) Prepare eight antenna elements in a transmit direction in the Antenna section.
For each element, choose the TXRX value.
c) Select the Closed Loop MIMO (8x2) as a value of the MIMO mode.

Overall Features
3 Activate the feature.

d) Select the LNCEL object corresponding to the cell where the LTE1787: TM9 with
8TX MU-MIMO and Up to 2 Layers Overall feature is being activated.

e) Set the Activate Downlink MU-MIMO (actDlMuMimo) parameter's value
to true.
4 Configure feature-related parameters.

d) Select the object corresponding to the cell where the LTE1787: TM9 with 8TX
MU-MIMO and Up to 2 Layers Overall feature is being activated.
e) Set the CSI reporting submode (csiRepSubmode) parameter's value.
f) Set the Activate fast adaptive MIMO
switch (actFastMimoSwitch) parameter's value to true.
g) Right-click on the LNCEL, where the LTE1787: TM9 with 8TX MU-MIMO and Up
to 2 Layers Overall feature is being activated, and select New CSI-RS
configuration information. Set the appropriate values of the following
parameters:
• CSI-RS ports number
• CSI-RS power offset
• CSI-RS resource configuration
• CSI-RS subframe configuration
5 Configure the MIMO parameter set (optional).

8TX MU-MIMO and Up to 2 Layers Overall feature is being activated and expand
this LNCEL object.


Features Overall
e) Select the Downlink MU-MIMO Parameter Set.

f) Set the values of the following parameters:
• MU gain maximization to true
• Downlink MU-MIMO correlation threshold
• Downlink MU-MIMO CQI threshold
Expected outcome
Those LNCEL instances where the TM8/TM9 MU-MIMO is configured are enabled and
operating with the configured gain maximization.
13.4 Deactivating LTE1787: TM9 with 8TX MU-MIMO and

Up to 2 Layers Overall
Before you start
The Activate Downlink MU-MIMO (actDlMuMimo) parameter is used to
deactivate the LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall feature.
Modification of this parameter requires neither an eNB restart nor cell locking.
Procedure

2 Deactivate the LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall feature.

8TX MU-MIMO and Up to 2 Layers Overall feature is being deactivated.


Overall Features
e) Set the Activate Downlink MU-MIMO (actDlMuMimo) parameter's value

to false.
3 Deactivate the MU-MIMO gain maximization (optional).

8TX MU-MIMO and Up to 2 Layers Overall feature is being activated and expand
this LNCEL object.

e) Select the Downlink MU-MIMO Parameter Set.
f) Set the MU gain maximization (actDlMuGainMax) parameter's value to
false.
Expected outcome
The TM8/TM9 MU-MIMO is disabled in those LNCEL instances where the feature has
been activated previously.

LTE15A Radio Resource Management and Telecom LTE1788: Automatic Access Class Barring
Features
14 LTE1788: Automatic Access Class Barring
14.1 Description of LTE1788: Automatic Access Class

Barring
The LTE1788: Automatic Access Class Barring feature provides an automatic access
class (AC) barring for cells that enter a high control plane load. The feature is an
enhancement of the LTE1047: Control Plane Overload Handling feature.
Benefits
End-user benefits
Operator benefits
This feature:
• reduces the number of rejected RRC connection requests during a persistently high
control plane load, thus improving the call setup success rate (CSSR).
• ensures that an eNB in an overload state will not stop working as a result of applying
automatic AC barring procedures.
• improves the stability of an eNB and RAN in a certain area as a result of fast counter
actions in the overload 2 (OVL2) state.
Requirements
Functional overview
The LTE1788: Automatic Access Class Barring feature is an enhancement of the
LTE1047: Control Plane Overload Handling feature. The LTE1788: Automatic Access
Class Barring feature brings an additional value to the OVL2 state of the LTE1047:
Control Plane Overload Handling feature. The feature performs the AC barring for the
control-plane signaling when an eNB remains in the OVL2 state for an operator-
configurable time.
Automatic AC barring is also applied to 1xRTT, which is contained in SIB8.
AC barring is applicable to the following services:
• mobile-originating data
• mobile-originated signaling
• Service Specific Access Control (SSAC) for voice
• SSAC for video
• circuit-switched fallback (CSFB) to UTRA/GSM
• 1xCSFB to CDMA

LTE1788: Automatic Access Class Barring LTE15A Radio Resource Management and Telecom
Features
Operational description
The feature is triggered when an eNB remains in OVL2 for an operator-configurable time
period. The time period is set by the Automatic AC Barring start
timer (autoAcBarringStartTimer) parameter. The timer is started immediately
after the cell enters the OVL2 state.
When triggered, the feature starts an automatic AC barring for SIB2 and (if configured)
SIB8. This means that all signaling that meets the configured criteria will not be admitted.
At the same time, when the feature is triggered, the TIME_AC_BAR_OVL (Aggregated
time period of automatic class class barring due to overload) counter is run.
When the eNB goes back to the OVL0 state, the Automatic AC Barring and
PLMN removal stop timer (autoAcbPlmnRmvlStopTimer) timer is started. If
the base station does not go back to the OVL2 state within that time frame, the automatic
AC barring functionality as well as the TIME_AC_BAR_OVL (Aggregated time period of
automatic access class barring due to overload) counter are turned off. After that, the
static access class barring is applied, if configured. In case there is no static AC barring
configured, no AC barring is applied in the eNB.
After leaving the OVL2 state when the static AC barring is activated, the parameters
(mandatory in the case of automatic AC barring) configured for the automatic AC barring
(for example AC barring for signaling OVL (acBarSigOvl), AC barring
for originating calls OVL (acBarOcOvl), or AC Barring for CDMA2000
1xRTT OVL (rttAcBarOvl)) are ignored.
The frequent switch between automatic AC barring applied and not applied along with
the C-plane overload level change might trigger a frequent SIB2/SIB8 AC barring-related
system information change. This might cause a systemInfoValueTag overflow (the
systemInfoValueTag changes more than 31 times within three hours). To avoid the
overflow solely due to the LTE1788: Automatic Access Class Barring feature, it is
recommended to trigger the feature only when the previous activation time took place at
least (or exactly) 15 minutes before the next activation time (the sum of
autoAcBarringStartTimer and autoAcbPlmnRmvlStopTimer is suggested to
be greater than or equal to 15 minutes).
Possible user scenarios

The benefits of LTE1788: Automatic Access Class Barring are mostly noticeable in times
of a high traffic load, for example, New Year's Eve or in overcrowded spaces such as
stadiums, etc.
• New Year's Eve

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

Features
When a train arrives at a station or leaves a long tunnel, a large number of

unexpected signaling cases emerge (tracking area updates, RRC connection
requests, etc.). Such a large nominal number of signaling cases exceed the
engineered eNB's capacity and eventually leads to an overload state, which
subsequently leads to triggering the automatic AC barring procedure. In these
scenarios, in order to achieve a quick response from the eNB to the increasing
overload, a very small Tstart_acb guard timer value is expected to be configured by
the operator.
• Disaster area
When a natural disaster takes place in a certain geographical area, an overload state
on an eNB serving that area is expected to take a long time. An increase in the
number of SMSs being sent, emergency calls being made, high priority accesses,
and any voice calls is expected.
System impact
The following feature is a prerequisite for the LTE1788: Automatic Access Class Barring
feature:
• LTE1047: Control Plane Overload Handling
The are interdependencies between the LTE1788: Automatic Access Class Barring
feature and the following features::
• LTE116: Cell Bandwidth – 3 MHz
The SIB2 AC barring in case of an overload is supported on the 3 MHz LTE cell
bandwidth only if the LTE116: Cell Bandwidth – 3 MHz feature is activated.
• LTE117: Cell Bandwidth – 1.4 MHz
The SIB2 AC barring in case of an overload is supported on the 1.4 MHz LTE cell
bandwidth only if the LTE117: Cell Bandwidth – 1.4 MHz feature is activated.
• LTE1635: SIB 8 AC Barring for 1xRTT
This feature uses the following SIB parameters of the RRC interface:
• SIB2:
– ac-BarringConfig for MO-Signalling
– MO-Data
– ssac-MMTEL-Voice
– ssac-MMTEL-Video
– CSFB
• SIB8:
– ac-BarringConfig for 1xRTT


Features
This feature improves system behavior in overload scenarios. The feature is expected to
improve the accessibility and retainability during overload scenarios and maintain the
throughput at an acceptable level.
There is no direct impact on user-plane connections and their quality.

LTE1788: Automatic Access Class Barring requirements, alarms and faults, commands,
Requirements

FDD TDD
Flexi Zone Access Point FL15A TL15A
Cloud Flexi Zone Controller not supported not supported
NetAct support not required support not required
UE 3GPP R8 3GPP R8

Table 2: BTS faults lists BTS faults related to this feature.
Table 80 BTS faults

Alarm ID Alarm name
6351 System information 3022 NETWORK SERVICE
broadcast parameters VIRTUAL
overflow CONNECTION
BLOCK PROCEDURE
FAILED
For fault descriptions, see LTE Operating Documentation/Reference/Alarms and Faults.

Table 3: New counters lists counters introduced with this feature.

Features
Table 81 New counters

M8001C322 Time period of automatic LTE Cell Load
access class barring due to
overload


Parameters
Table 82 New Parameters

name
AC Barring rttAcBarOvl CDFIM - common
for CDMA2000
1xRTT OVL
AC barring acBarring0To CDFIM rttAcBarOvl common
factor for 9Ovl
overload
classes 0 to
9 OVL
AC barring acBarring10O CDFIM rttAcBarOvl common
factor for vl
overload
class 10 OVL
factor for vl
overload
class 11 OVL
factor for vl
overload
class 12 OVL
factor for vl
overload
class 13 OVL
factor for vl
overload
class 14 OVL
factor for vl
overload
class 15 OVL
AC barring acBarringEmg CDFIM rttAcBarOvl common
Factor for Ovl

Features
Table 82 New Parameters (Cont.)

name
emergency
OVL
AC barring acBarringMsg CDFIM rttAcBarOvl common
modification Ovl
factor for
message OVL
AC barring acBarringReg CDFIM rttAcBarOvl common
modification Ovl
factor for
registration
OVL
Activation actAutoAcBar LNBTS - common
of Automatic ring
AC barring
AC barring acBarCsfbOcO SIB - common
for mobile vl
originating
CS fallback
OVL
AC barring acBarACOvl SIB acBarCsfbOcOvl common
list OVL
AC barring acBarTimeOvl SIB acBarCsfbOcOvl common
time OVL
AC probFacOvl SIB acBarCsfbOcOvl common
probability
factor OVL
AC barring acBarMMTelVi SIB - common
for MMTEL deoOcOvl
video
originating
calls OVL
AC barring acBarACOvl SIB acBarMMTelVideo common
list OVL OcOvl
AC barring acBarTimeOvl SIB acBarMMTelVideo common
time OVL OcOvl
AC probFacOvl SIB acBarMMTelVideo common
probability OcOvl
factor OVL
AC barring acBarMMTelVo SIB - common
for MMTEL iceOcOvl
voice
originating
calls OVL
AC barring acBarACOvl SIB acBarMMTelVoice common
list OVL OcOvl
AC barring acBarTimeOvl SIB acBarMMTelVoice common
time OVL OcOvl

Features
Table 82 New Parameters (Cont.)

name
AC probFacOvl SIB acBarMMTelVoice common
probability OcOvl
factor OVL
AC barring acBarOcOvl SIB - common
for
originating
calls OVL
AC barring ocAcBarACOvl SIB acBarOcOvl common
list for
mobile
originating
calls OVL
AC barring ocAcBarTimeO SIB acBarOcOvl common
time for vl
originating
calls OVL
AC ocAcProbFacO SIB acBarOcOvl common
probability vl
factor for
originating
calls OVL
AC barring acBarSigOvl SIB - common
for
signaling
OVL
AC barring sigAcBarACOv SIB acBarSigOvl common
list mobile l
orig
signaling
OVL
AC barring sigAcBarTime SIB acBarSigOvl common
time for Ovl
signaling
OVL
AC sigAcProbFac SIB acBarSigOvl common
probability Ovl
factor for
signaling
OVL
Automatic AC autoAcbPlmnR SIB - common
Barring and mvlStopTimer
PLMN removal
stop timer
Automatic AC autoAcBarrin SIB - common
barring gStartTimer
start timer
AC barred eCallAcBarre SIB - common
for dOvl
emergency
calls OVL

Features
Table 83 Modified parameters

Activation of actCplaneOvlHan LNBTS common
C-plane dling
overload
handling
Access class acBarCsfbOc SIB common
barring for
mobile
originating CS
fallback
Access class acBarAC SIB common
barring list
Access class acBarTime SIB common
barring time
Access probFac SIB common
probability
factor
Access class acBarMMTelVideo SIB common
barring for Oc
MMTEL video
originating
calls
barring list
barring time
probability
factor
Access class acBarMMTelVoice SIB common
barring for Oc
MMTEL voice
originating
calls
barring list
barring time
probability
factor
Access class acBarOc SIB common
barring for
originating
calls
Access class ocAcBarAC SIB common
barring list
for mobile
originating
calls

Features
Table 83 Modified parameters (Cont.)

Access class ocAcBarTime SIB common
barring time
for originating
calls
Access ocAcProbFac SIB common
probability
factor for
originating
calls
Access barring acBarSig SIB common
for signaling
Access class sigAcBarAC SIB common
barring list
mobile orig
signaling
Access class sigAcBarTime SIB common
barring time
for signaling
Access sigAcProbFac SIB common
probability
factor for
signaling
Access barred eCallAcBarred SIB common
for emergency
calls

Sales information
Table 84 Sales information

element
14.3 Activating and configuring LTE1788: Automatic

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

Features

Access Class Barring
object locking
Activation of Automatic activation flag no
AC Barring (Activation of
Automatic AC Barring)
Automatic AC Barring mandatory configuration no
start
timer (autoAcBarringStart
Timer)
Automatic AC Barring and mandatory configuration no
PLMN removal stop
timer (autoAcbPlmnRmvlSto
pTimer)
AC barred for emergency optional configuration no
calls
OVL (eCallAcBarredOvl)
AC barring for signaling optional configuration no
OVL (acBarSigOvl)
AC barring time for mandatory configuration no
signaling
OVL (sigAcBarTimeOvl)
AC probability factor mandatory configuration no
for signaling
OVL (sigAcProbFacOvl)
AC barring for optional configuration no
originating calls
OVL (acBarOcOvl)
AC barring time for mandatory configuration no
originating calls
OV (ocAcBarTimeOvl)
for originating calls
OVL (ocAcProbFacOvl)
AC barring for MMTEL optional configuration no
voice originating calls
OVL (acBarMMTelVoiceOcOvl)
AC barring time mandatory configuration no
OVL (acBarTimeOvl)
g Note: This parameter refers

to the AC barring for
MMTEL voice
originating calls
OVL structure.

OVL (probFacOvl)

Features

Access Class Barring (Cont.)
object locking

MMTEL voice
originating calls
OVL structure.
AC barring for MMTEL optional configuration no

video originating calls
OVL (acBarMMTelVideoOcOvl)
OVL (acBarTimeOvl)

MMTEL video
originating calls
OVL structure.

OVL (probFacOvl)

MMTEL video
originating calls
OVL structure.
AC barring for mobile optional configuration no

originating CS fallback
OVL (acBarCsfbOcOvl)
OVL (acBarTimeOvl)

mobile originating
CS fallback OVL
structure.

OVL (probFacOvl)

mobile originating
CS fallback OVL
structure.
AC Barring for CDMA2000 optional configuration no

1xRTT OVL (rttAcBarOvl)
g Note: When this parameter

is configured, it's (following)
structure parameters'
configuration is mandatory,

Features

Access Class Barring (Cont.)
object locking
AC barring factor for mandatory configuration no
overload classes 0 to 9
OVL (acBarring0To9Ovl)
AC barring Factor for optional configuration no
emergency
OVL (acBarringEmgOvl)
AC barring factor for optional configuration no
overload class 10
OVL (acBarring10Ovl)
overload class 11
overload class 12
overload class 13
overload class 14
OVL (acBarring14vl)
overload class 15
AC barring modification optional configuration no
factor for message
OVL (acBarringMsgOvl)
AC barring modification optional configuration no
factor for registration
OVL (acBarringRegOvl)
The LTE1047: Control Plane Overload Handling feature needs to be activated/configured

before the activation of the LTE1788: Automatic Access Class Barring feature.
Before activation of the LTE1788: Automatic Access Class Barring feature, ensure that
the static access class barring parameters are configured according to your
expectations. Ensure that the overload AC barring parameters are well coordinated with
static AC barring parameters
It is not recommended to configure both parameters: autoAcbPlmnRmvlStopTimer
and autoAcBarringStartTimer, such that the sum of is smaller than 15 minutes,
as UEs may not be able to access the system for a longer period of time. Short timer
settings may lead to ping pong effect at persistent high load.
Procedure

Features

2 Activate the LTE1788: Automatic Access Class Barring feature.
a) Go to the Radio Network Configutration page.

d) Set the Activation of Automatic AC Barring (actAutoAcBarring)
LNBTS parameter's value to true.
3 Configure the timer after which eNB starts automatic AC barring (optional).

c) Select the SIB object.
d) Set the Automatic AC Barring start
timer (autoAcBarringStartTimer) parameter to a needed value.
The default value is 300 s.
4 Configure the timer after which eNB stops automatic AC barring (optional).
a) Select the SIB object.

b) Set the
Automatic AC Barring stop timer (autoAcbPlmnRmvlStopTimer)
parameter to a needed value.
The default value is 3600 s.
5 Indicate if access is barred for emergency calls in this cell when automatic AC barring
broadcast condition is met due to an eNB C-plane overload.

b) Set the AC barred for emergency calls OVL (eCallAcBarredOvl)
LNCEL parameter's value to barred or Not barred.
g Note: For the feature to function properly, at least one of the parameters defined
in the following steps must be configured.
The parameters are defined for each cell separately.

Features
6 Configure access barring for signaling OVL.

b) If required, right-click the SIB object and select New ► AC barring for
signaling OVL (acBarSigOvl).
c) Expand the created AC barring for signaling OVL object.
d) Select AC barring for signaling OVL-1.
e) Configure at least the following parameters:
• AC barring time for signaling OVL (sigAcBarTimeOvl)
The parameter defines the access class barring time when the automatic AC
barring broadcast condition is met due to an eNB C-plane overload.
• AC probability factor for signaling
OVL (sigAcProbFacOvl)
The parameter defines the probability of a UE establishing an RRC
connection when the automatic AC barring broadcast condition is met due to
an eNB C-plane overload.
f) Optionally, configure access class barring for special access classes from AC11
to AC15 by setting a value to true or false.
7 Configure access class barring for originating calls OVL.

b) If required, right-click the SIB object and select New ► AC barring for
originating calls OVL (acBarOcOvl).
c) Expand the created AC barring for originating calls OVL object.
d) Select AC barring for originating calls OVL- 1.
• AC barring time for originating calls
OV (ocAcBarTimeOvl)
• AC probability factor for originating calls
OVL (ocAcProbFacOvl)
8 Configure access class barring for MMTEL voice originating calls OVL.
g Note: To be able to configure access class barring for MMTEL voice originating
calls, the LTE10: EPS Bearers for Conversational Voice feature must be enabled
first.

Features

b) If required, right-click the SIB object and select New ► AC barring for MMTEL
voice originating calls OVL (acBarMMTelVoiceOcOvl).
c) Expand the created AC barring for MMTEL voice originating calls OVL object.
d) Select AC barring for MMTEL voice originating calls OVL-1.
• AC barring time OVL (acBarTimeOvl)
• AC probability factor OVL (probFacOvl)
to AC15 by setting a value to true or false..
9 Configure access class barring for MMTEL video originating calls OVL.
g Note: To be able to configure access class barring for MMTEL voice originating
calls, the LTE10: EPS Bearers for Conversational Voice feature must be enabled
first.
b) If required, right-click the SIB object and select New ► AC barring for MMTEL
video originating calls OVL (acBarMMTelVideoOcOvl).
c) Expand the created AC barring for MMTEL video originating calls OVL object.
d) Select AC barring for MMTEL video originating calls OVL-1.
10 Configure access class barring for mobile originating CS fallback OVL.
g Note: The CS fallback applies only to the 3GPP CSFB. For more information,
see 3GPP TS36.331.
g Note: To be able to configure access class barring for mobile-originating CS

fallback, the LTE562: CSFB to UTRAN or GSM via Redirect and
LTE736: CS Fallback to UTRAN must be activated.

Features

b) If required, right-click the SIB object and select New ► AC barring for mobile
originating CS fallback OVL (acBarCsfbOcOvl) object.
c) Expand the created AC barring for mobile originating CS fallback OVLobject.
d) Select AC barring for mobile originating CS fallback OVL-1.
11 Configure access class barring for CDMA2000 1xRTT fallback OVL.
The CS fallback applies only to the CDMA2000 1xRTT fallback. For more
information, see C.S0097.
g Note: To be able to configure access class barring for CDMA2000 1xRTT

fallback, the LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB)
feature must be activated.
b) Right-click the LNCEL object and from a drop-down list select the CDFIM object.
c) Right-click the CDFIM object.
d) From the drop-down menu select New ► AC Barring for CDMA2000 1xRTT
OVL (rttAcBarOvl).
e) Expand the AC Barring for CDMA2000 1xRTT OVL object.
f) Select AC Barring for CDMA2000 1xRTT OVL- 1.
g) Configure at least the following parameter:
• AC barring factor for overload classes 0 to 9
OVL (acBarring0To9Ovl)
The parameter defines the access class barring from 0 to 9 when the
automatic AC barring broadcast condition is met due to an eNB C-plane
overload.
h) Optionally configure the following parameters:

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

Features
Default value is: 0

• AC barring modification factor for registration
OVL (acBarringRegOvl)
Default value is: 0
Expected outcome
• The feature has been activated, and the parameter settings are persistently stored in
the eNB.
• NetAct and BTS Site Manager are informed about the changed configuration (which
is visible through notifications).
14.4 Deactivating LTE1788: Automatic Access Class

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

2 Deactivate the LTE1788: Automatic Access Class Barring feature.
a) Go to the Radio Network Configutration page.

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

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

LTE15A Radio Resource Management and Telecom LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz
Features
15 LTE1804: Downlink Carrier Aggregation 3 CC

- 60 MHz
The LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature introduces downlink
(DL) carrier aggregation (CA) in multiples of three cell combinations, where a given user
equipment (UE) is configured with two secondary cells (SCells). The evolved Node B
(eNB) has more than two cells on different frequencies per sector. The feature supports
CA in the DL for three component carriers (CCs) of up to 60 MHz as compared to the
LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz feature.
Benefits
End-user benefits
This feature offers the end user an improved peak and average UE DL throughput. Note
that this is only beneficial in cells that are not fully loaded.
Operator benefits
This feature provides the following benefits to the operator:
• allows the operator to aggregate the air interface of three overlapping cells with the
bandwidths (BWs) of up to 20 MHz + 20 MHz + 20 MHz to reach high DL peak rates
for individual users
• allows the operator to increase the UE's peak data rate by up to 450 Mbps in case of
fragmented spectrum in certain load conditions
• enables fast load balancing for CA UEs within the three DL cells
Functional overview
The LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature introduces CA in the
DL for three CCs and three non-aggregated uplink (UL) cells. A mix of non-CA and CA
UEs with two or three aggregated CCs is supported in the DL on each cell.
The Figure 10: Examples of three-cell CA shows examples of CA with three cells per
sector. Scenarios 1 and 2 correspond to the 3rd Generation Partnership Project (3GPP)
TS 36.300.

LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz LTE15A Radio Resource Management and Telecom
Features
Figure 10 Examples of three-cell CA
f1 f2 f3 f1 f2 f3
Scenario1with3cellspersector Scenario2with3cellspersector
f1 f2 f3
Scenario1or2with3cellspersector(withnon-wirelessrepeater)
Aggregated cell configurations

The following are the cell configurations supported by the LTE1804: Downlink Carrier
Aggregation 3 CC - 60 MHz feature:
• band combinations
The following are the additional supported band combinations for the deployment
scenarios 1 and 2 as described by the 3GPP TS 36.300:
– band 1 + band 3 + band 5 (BW combination set: 0)
– band 1 + band 3 + band 8 (BW combination set: 0 and 2)
– band 1 + band 5 + band 7 (BW combination set: 1)
– band 1 + band 18 + band 28
– band 2 + band 2 + band 5 (band 2 non-contiguous)
– band 2 + band 2 + band 29 (band 2 contiguous)

Features

g Note: The BW combination set is 0 if not indicated.

• BW combinations
The maximum aggregated DL BW is 60 MHz. The following are the additional
supported BW combinations for 2Rx/2Tx configuration per CC:
– 5 MHz + 5 MHz + 5 MHz
– 5 MHz + 5 MHz + 10 MHz
– 5 MHz + 5 MHz + 15 MHz
– 5 MHz + 5 MHz + 20 MHz
– 5 MHz + 10 MHz + 10 MHz
– 5 MHz + 10 MHz + 15 MHz
– 5 MHz + 10 MHz + 20 MHz
– 5 MHz + 15 MHz + 15 MHz
– 5 MHz + 15 MHz + 20 MHz
– 5 MHz + 20 MHz + 20 MHz
– 10 MHz + 10 MHz + 10 MHz
– 10 MHz + 10 MHz + 15 MHz
– 10 MHz + 10 MHz + 20 MHz
– 10 MHz + 15 MHz + 15 MHz
– 10 MHz + 15 MHz + 20 MHz
– 10 MHz + 20 MHz + 20 MHz
– 15 MHz + 15 MHz + 15 MHz
– 15 MHz + 15 MHz + 20 MHz
– 15 MHz + 20 MHz + 20 MHz
– 20 MHz + 20 MHz + 20 MHz
g Note: The 10 MHz + 10 MHz + 20 MHz BW combination is the only

configuration supported in the
LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature from the
LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz feature.
The following are the supported BW combinations with 4Rx/4Tx configuration on the
CC with the highest cell BW:
– 5 MHz + 5 MHz + 5 MHz
– 5 MHz + 5 MHz + 10 MHz
– 5 MHz + 5 MHz + 15 MHz
– 5 MHz + 5 MHz + 20 MHz
– 5 MHz + 10 MHz + 10 MHz
– 5 MHz + 10 MHz + 15 MHz
– 5 MHz + 10 MHz + 20 MHz

Features
– 10 MHz + 10 MHz + 10 MHz

– 10 MHz + 10 MHz + 15 MHz
– 10 MHz + 10 MHz + 20 MHz
g Note: This is with the implicit assumption of nine cells per eNB with three FSPs.
However, because of large user plane deployments, the 4Rx/4Tx + 4Rx/4Tx +
4Rx/4Tx configuration is supported even for the 20 MHz + 20 MHz + 20 MHz BW
combination with a limited number of cells.
• eNB antenna configurations
The following are the supported eNB antenna configurations:
– 2Tx/2Rx + 2Tx/2Rx + 2Tx/2Rx
g Note: Only the 3GPP-defined band and BW combinations are supported. DL CA is only
applied for UEs with related UE capabilities. The parallel use of the UL coordinated
multipoint transmission (CoMP) might be restricted.
Functionality
This feature is an extension to the LTE1803: Downlink Carrier Aggregation 3 CC - 40
MHz feature. For more details, see the LTE1803: Downlink Carrier Aggregation 3 CC -
40 MHz feature description. The functions of the LTE1804: Downlink Carrier Aggregation
3 CC - 60 MHz feature are described as follows:
• Based on the radio admission control (RAC) selection, either one or two SCells for a
three-cell-CA candidate UE is added. A three-cell-CA candidate UE can be a two-
cell-CA candidate UE at the same time. The UE can be configured with one SCell. A
UE supporting CA of three cells that is a three-cell-CA candidate is configured with
physical uplink control channel (PUCCH) format 3 when one SCell is added. A UE
supporting CA of three cells that is not a three-cell-CA candidate is configured with
PUCCH format 1bwcs when one SCell is added.
• The maximum number of UEs with one or two SCells configured is increased.
• SCell release of one from two SCells configured because of cell lock/shutdown is
introduced. The other configured SCell, which is not locked/shutdown, continues to
serve the CA UE.
• The interworking with the nominal bit rate (NBR) is improved. The NBR is allowed in
the DL for three-cell-CA candidate UEs.
• Stepwise SCell activation of two configured SCells because of traffic is introduced.
One SCell is activated if traffic first is required. After that, a check is made if the
second SCell needs to be activated because of traffic or if one active SCell is
sufficient for that UE.
• The configurable SCell activation conservativeness level for one and two configured
SCells is improved. It is recommended to set the
sCellActivationCyclePeriod and scellActivationLevel parameters to
low values to achieve fast activation for Transmission Control Protocol (TCP) traffic
and short response time.
• The simultaneousAckNackAndCQI-Format3-r11 dedicated radio resource control
(RRC) information element is set to true. The periodic channel state information
(CSI) is sent on RRC connection on the PUCCH format 3 with positive
acknowledgment (ACK)/negative acknowledgment (NACK) if it is supported by the

Features
Rel-11 UE. Dropping of the periodic CSI or SCell scheduling restriction to avoid the
dropping is not applied for such UEs.
g Note: The sub-band periodic CSI is not recommended to be configured when

the DL CA is enabled. Instead, only the wideband periodic CSI is recommended
to be configured.
• The PUCCH format 3 resource value selection with configurable (one or two)
PUCCH format 3 physical resource blocks (PRBs) is introduced. The operator can
configure the amount of available PUCCH format 3 resources.
• The scheduling of single or multiple UEs on three serving cells with new band or BW
combinations with configurable CA fairness is supported.
• The interworking with the peak data rate capping for two active SCells is improved.
• The following new performance management (PM) counters are introduced:
– SCell scheduling blocking rate due to conflict on PUCCH format 3 resources
– SCell scheduling blocking rate due to conflict on PUCCH format 1bwcs resources
System impact
• LTE1562: Carrier Aggregation for Multi-carrier eNodeBs
The interworking with the following features is excluded:

• LTE117: Cell Bandwidth 1.4 MHz
• LTE1382: Cell Resource Groups (interworking with DL CA of two serving cells is
possible)
The LTE1542: FDD Supercell and LTE1804: Downlink Carrier Aggregation 3 CC - 60

MHz features can be enabled together. The supercell-enabled cells and supercell-
disabled cells might affect the CA performance because of coverage mismatch.
Therefore, CA relations (CAREL objects) must be planned carefully. In addition, the
features addressing CA coverage mismatch scenarios, such as the LTE2006: Flexible
SCell Selection feature, should be considered for activation.
The LTE1367: Automatic Cell Combination Assignment for Carrier Aggregation and
LTE1951: Automatic Configuration Support for CA for Multi-carrier eNBs features do not
support CA of supercell-enabled cells and supercell-disabled cells. Thus, manual
configuration of CA relations is needed in these mixed configuration scenarios.
This feature affects the Uu interface as follows:
• simultaneousAckNackAndCQI-Format3-r11 set to true
• PUCCH format 3 used for eligible UEs configured with one SCell

Features
• delivery of the three-cell CA specific tReord, tProhib, and tPollRetr

parameters
g Note: It is recommended to use the following:

• optimized RLC profile for three-CC CA
• profile ID 6 (default) for the rlcProfIdx3cc parameter


The LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature enhances the single
user DL-peak throughput by aggregating three carriers up to 20 MHz + 20 MHz + 20
MHz.
g Note: The configurable level of SCell activation conservativeness and stepwise SCell
activation might reduce the throughput of the CA UEs, but it might be beneficial for
other UEs.
The following feature enhancements affect the capacity:

• The number of UEs with one or two SCells configured is increased. This has also an
impact on the number of RRC_CONNECTED UEs in the cells.
• The number of UEs with one SCell (using PUCCH format 1bcws) or two SCells
configured (using PUCCH format 3) per transmission time interval (TTI) per cell is
increased because the number of PUCCH format 3 PRBs is increased.

LTE1804 requirements, alarms and faults, commands, measurements and counters,
KPIs, parameters, and sales information
Requirements

FDD TDD
Flexi Multiradio 10 BTS Support not required Not supported
Nokia AirScale BTS FL16 Not supported
Flexi Zone BTS Support not required Not supported
Flexi Zone Access Point Support not required Not supported
Cloud Flexi Zone Controller Support not required Not supported
OMS Support not required Not supported

Features

FDD TDD
MME Support not required Not supported
SAE GW Support not required Not supported
UE 3GPP R11 UE capabilities Not supported
3GPP R12 UE capabilities
Alarms
There are no alarms related to the LTE1804: Downlink Carrier Aggregation 3 CC - 60
MHz feature.

There are no faults related to the LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz
feature.
Commands
There are no commands related to the LTE1804: Downlink Carrier Aggregation 3 CC -
60 MHz feature.

Counter Counter name Measurement
ID
M8011C SCell scheduling blocking LTE Cell Resource
166 rate due to conflicts on
PUCCH format 1bwcs resources
M8011C SCell scheduling blocking LTE Cell Resource
167 rate due to conflicts on
PUCCH format 3 resources
For counter descriptions, see LTE Performance Measurements and Key Performance
Indicators.
Table 88 New key performance indicators introduced by LTE1804

KPI ID KPI name
LTE_5700a E-UTRAN SCell Scheduling Blocking Rate due to Conflicts on PUCCH Format
1bwcs Resources
LTE_5701a E-UTRAN SCell Scheduling Blocking Rate due to Conflicts on PUCCH Format 3
Resources
For key performance indicator descriptions, see LTE Performance Measurements and

Features
Parameters

d object
BTS ID of the lnBtsId CAREL - common
parent eNB of the
cell to be
aggregated
Carrier aggregation caPoolId LNCEL - common
pool ID
Enable Bandwidth enableBwCombCh LNBTS - common
Combination Checks eck
Profile 6 of RLC rlcProf6 LNBTS - common
parameters
Poll PDU pollPdu LNBTS rlcProf6 common
RLC profile Id rlcProfileId LNBTS rlcProf6 common
Timer poll tPollRetr LNBTS rlcProf6 common
retransmit
Timer status tProhib LNBTS rlcProf6 common
prohibit
Timer reordering tReord LNBTS rlcProf6 common
Conservativeness scellActivatio LNBTS - common
level of SCell nLevel
activation
RLC profile index rlcProfIdx3cc LNBTS qciTab7 common
for 3 CC CA
for 3 CC CA
for 3 CC CA
RLC profile index rlcProfIdx3cc LNBTS qciTabOperator common
for 3 CC CA
Table 90 Parameters modified by LTE1804

d object
Activation of actDLCAggr LNBTS - common
downlink carrier
aggregation
Scheduling CA caSchedFairFac LNBTS - common
fairness control t
factor
SCell activation sCellActivatio LNBTS - common
method nMethod
SCell activation sCellActivatio LNBTS - common
cycle period nCyclePeriod

Features
Table 90 Parameters modified by LTE1804 (Cont.)

d object
Max number carrier maxNumCaConfUe LNCEL_ - FDD
aggr configured UEs FDD
Max number carrier maxNumCaConfUe LNCEL_ - TDD
aggr configured UEs TDD
Max number carrier maxNumCaConfUe LNCEL_ - FDD
aggr configured UEs 3c FDD
3 Carriers
Max number carrier maxNumCaConfUe LNCEL_ - TDD
aggr configured UEs 3c TDD
3 Carriers
Max number Carrier maxNumCaConfUe LNCEL_ - FDD
Aggr configured UEs Dc FDD
double carrier
Max number Carrier maxNumCaConfUe LNCEL_ - TDD
Aggr configured UEs Dc TDD
double carrier
Number of PUCCH nPucchF3Prbs MPUCC - FDD
PRBs for HARQ H_FDD
format 3
Number of PUCCH nPucchF3Prbs MPUCC - TDD
PRBs for HARQ H_TDD
format 3

d object
Max number of maxNumScells LNCEL - common
secondary cells for
DL carrier aggr
QCI translation qciTab7 LNBTS - common
table QCI 7
DRX profile index drxProfileInde LNBTS qciTab7 common
x
DSCP dscp LNBTS qciTab7 common
Enforce TTI enforceTtiBund LNBTS qciTab7 common
bundling ling
Logical channel lcgid LNBTS qciTab7 common
group identifier
Nominal bit rate nbrDl LNBTS qciTab7 common
downlink
Nominal bit rate nbrUl LNBTS qciTab7 common
uplink
Priority prio LNBTS qciTab7 common
QCI qci LNBTS qciTab7 common
QCI support qciSupp LNBTS qciTab7 common

Features

d object
Resource type resType LNBTS qciTab7 common
RLC mode rlcMode LNBTS qciTab7 common
RLC profile index rlcProfIdx LNBTS qciTab7 common
Scheduling bucket schedulBSD LNBTS qciTab7 common
size duration
Scheduling priority schedulPrio LNBTS qciTab7 common
Scheduling weight schedulWeight LNBTS qciTab7 common
table QCI 8
x
bundling ling
group identifier
downlink
uplink
size duration
table QCI 9
x
bundling ling
group identifier

Features

d object
downlink
uplink
size duration
QCI translation qciTabOperator LNBTS - common
table operator
specific QCIs
Counter group counterGroup LNBTS qciTabOperator common
Delay target delayTarget LNBTS qciTabOperator common
DRX profile index drxProfileInde LNBTS qciTabOperator common
x
DSCP dscp LNBTS qciTabOperator common
Enforce TTI enforceTtiBund LNBTS qciTabOperator common
bundling ling
L2 overhead factor l2OHFactorDl LNBTS qciTabOperator common
GBR Dl
L2 overhead factor l2OHFactorUl LNBTS qciTabOperator common
GBR Ul
Logical channel lcgid LNBTS qciTabOperator common
group identifier
Maximum GBR maxGbrDl LNBTS qciTabOperator common
downlink
Maximum GBR uplink maxGbrUl LNBTS qciTabOperator common
Nominal bit rate nbrDl LNBTS qciTabOperator common
downlink
Nominal bit rate nbrUl LNBTS qciTabOperator common
uplink
Priority prio LNBTS qciTabOperator common
QCI qci LNBTS qciTabOperator common
QCI support qciSupp LNBTS qciTabOperator common

Features

d object
Resource type resType LNBTS qciTabOperator common
RLC mode rlcMode LNBTS qciTabOperator common
RLC profile index rlcProfIdx LNBTS qciTabOperator common
Scheduling bucket schedulBSD LNBTS qciTabOperator common
size duration
Scheduling priority schedulPrio LNBTS qciTabOperator common
Scheduling weight schedulWeight LNBTS qciTabOperator common

Documentation/Reference/Parameters.
Sales information

15.2 Activating and configuring LTE1804: Downlink

Carrier Aggregation 3 CC - 60 MHz
Before you start
The Activation of downlink Carrier aggregation (actDLCAggr)
parameter activates the feature. The Max number of secondary cells for DL
carrier aggr (maxNumScells) parameter allows aggregation of three serving cells.
Modification of these parameters requires eNB restart.
It is recommended to set the Sched Carrier Aggr fairness control factor
(caSchedFairFact) parameter value to 0 for the LTE1804: Downlink Carrier
Aggregation 3 CC - 60 MHz feature.
Table 93 Parameters used for activating and configuring the LTE1804: Downlink
Carrier Aggregation 3 CC - 60 MHz feature
object locking
Activation of downlink activation flag eNB restart
Carrier aggregation
(actDLCAggr)
Max number of mandatory configuration eNB restart
secondary cells for DL
carrier aggr
(maxNumScells)

Features
The LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature is enabled together

with the LTE1089: Downlink Carrier Aggregation - 20 MHz, LTE1332: Downlink Carrier
Aggregation - 40 MHz, LTE1562: Carrier Aggregation for Multi-carrier eNodeBs, and
LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz features. These features use the
same activation flag. For more information about feature dependencies, see
The eNB supports the deployment required for CA. All LNCELs in the eNB must have
the Carrier aggregation pool ID (caPoolId) parameter configured when the
LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature is enabled. The CA cells
with subordinated CAREL or CA cells linked by CAREL-lcrId of another LNCEL must
have the same CA pool ID.
If there are more than two cells per sector, each cell can have multiple CARELs and
each cell can be linked by CAREL-lcrId of other multiple cells. The maximum number
of SCell candidates per PCell is two. Multiple CARELs of one cell do not point to the
same cell.
The following parameters must be set before activating the LTE1804: Downlink Carrier
Aggregation 3 CC - 60 MHz feature:
• The PUCCH bandwidth for CQI (nCqiRb) parameter must have a value
greater than 1.
• The Number of PUCCH PRBs for HARQ format 3 (nPucchF3Prbs)
parameter must have a value greater than 0.
• The CQI periodicity network period (cqiPerNp) parameter must have a
value less than or equal to 40ms.
Procedure

2 Configure the Activation of downlink Carrier


d) Set the Activation of downlink Carrier

Features

c) Create a new CAREL object.
g Note: The CA pool ID (LNCEL-caPoolId) must be consistent within the CA

cluster. The CAREL objects must only point to cells in their CA pool.
4 Configure the Max number of secondary cells for DL carrier

aggr (maxNumScells) parameter.
a) Expand the selected LNBTS object.

c) Set the Max number of secondary cells for DL carrier
aggr (maxNumScells) parameter value to 2.
g Note: When the parameter value is set to 2, the eNB uses CA with two or three
CCs and the Number of PUCCH PRBs for HARQ format
3 (nPucchF3Prbs) parameter must not be set to 0.
5 (Optional) Configure the Profile 6 of RLC parameters (rlcProf6) parameter.
On the expanded LNBTS object, select the Profile 6 of RLC parameters object and
define the value of each parameter within this object.
6 (Optional) Configure the RLC profile index for 3 CC CA (rlcProfIdx3cc)

parameter.
On the expanded LNBTS object, select the QCI translation table QCI 6 object and
define the value of the RLC profile index for 3 CC CA (rlcProfIdx3cc)
parameter.
g Note: This step is also applicable for the QCI translation table QCI 7,
QCI translation table QCI 8, and QCI translation table QCI 9 objects.
7 (Optional) Create a new QCI translation table operator specific QCIs object.
a) Right-click on the LNBTS object.

b) Create a new QCI translation table operator specific QCIs object and define
the value of each parameter within this object.

Features
Result
Expected Outcome
The LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature is enabled in the
eNB. The eNB uses CA with two or three CCs.
15.3 Deactivating LTE1804: Downlink Carrier

Aggregation 3 CC - 60 MHz
Before you start
The Max number of secondary cells for DL carrier
aggr (maxNumScells) parameter deactivates the feature. Modification of this
parameter requires eNB restart.
Procedure



e) Set the Max number of secondary cells for DL carrier
g Note: When the parameter value is set to 1, the eNB only uses CA with two CCs
and the Number of PUCCH PRBs for HARQ format
3 (nPucchF3Prbs) parameter must be set to 0. To deactivate CA completely,
set the Activation of downlink carrier

Features
Result
Expected outcome
The LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz feature is deactivated in the
eNB. The eNB only uses CA with two CCs.

LTE15A Radio Resource Management and Telecom LTE1836: TDD Downlink Carrier Aggregation - 60 MHz
Features
16 LTE1836: TDD Downlink Carrier Aggregation -

60 MHz
16.1 Description of LTE1836: TDD Downlink Carrier

Aggregation - 60 MHz
Date of Section Change description
change
August 6, 2018 Feature description The dependency between the LTE1836 feature and the
LTE1382 feature was deleted. Those features can be
activated together.
December 21, Feature description The dependency between the LTE1836 feature and the
2017 LTE1382 feature was added.

The LTE1836: TDD Downlink Carrier Aggregation – 60 MHz feature extends the
downlink (DL) bandwidth (BW) up to 60 MHz with three component carriers (CCs).
Benefits
End-user benefits
This feature offers the end user an improved peak and average user equipment (UE) DL
throughput.
Operator benefits
This feature provides the following benefits to the operator:
• increase in the UE's DL peak rate up to 330 Mbps in case of low or moderate loaded
serving cells
• fast load balancing for CA UEs within the three DL cells
Requirements
Functional overview
The LTE1836: TDD Downlink Carrier Aggregation - 60MHz feature enables the Flexi
Multiradio BTS to support carrier aggregation (CA) in the DL for three CCs. A mix of CA
and non-CA UEs with two or three aggregated CCs is supported in the DL on each cell.
The maximum aggregated DL BW is 60 MHz and the uplink (UL) is only on the primary
cell (PCell). The aggregated carriers can be contiguous or non-contiguous. The DL CA is
applied for UEs with related UE capabilities.
The following are the supported band combinations for the deployment scenarios 1 and
2 as described in the 3rd Generation Partnership Project (3GPP) TS 36.300:

LTE1836: TDD Downlink Carrier Aggregation - 60 MHz LTE15A Radio Resource Management and Telecom
Features
• band 41 + band 41 + band 41

The following are the supported cell BW combinations:

• 20 MHz + 20 MHz + 10 MHz
• 20 MHz + 20 MHz + 20 MHz
Scheduling and PUCCH

The separated and coordinated DL schedulers schedule the UEs with activated SCells.
The fairness factor for three-CC UEs is preconfigured. The discontinuous reception
(DRX) handling and measurement gap handling are synchronized with the three DL
schedulers. The combined DL throughput is used for proportional fair scheduling, UE DL
AMBR control, and UE DL nominal bit rate (NBR) control. The aperiodic channel quality
indicator (CQI) report is extended to report the three CCs. The physical uplink control
channel (PUCCH) format 3 is also introduced for the DL CA with three CCs. For more
information about the DL CA feature extensions, see the LTE1558: TDD Downlink
Carrier Aggregation feature description.
g Note: Only CA UEs use PUCCH format 3 for TDD UL/DL configurations 1 or 2.
Therefore, the nPucchF3Prbs parameter is only set to a non-zero value when CA is
activated and a cell is configured as a PCell.
Configuration limitations
The following are the limitations for the configuration of the LTE1836: TDD Downlink
Carrier Aggregation – 60 MHz feature:
• The TD-LTE 15A supports CA of up to three cells.
• The aggregated cells must be from the same sector.
• The cells cannot be configured as an SCell for more than two PCells (maximum
number of PCell per SCell is two).
• The cells cannot be configured as a PCell for more than two SCells (maximum
number of SCell per PCell is two).
System impact

g Note: Note: These features have the same activation flag, which is the actDLCAggr
parameter.
The LTE1838: TDD Downlink Inter-band Carrier Aggregation – 40 MHz feature needs to
be enabled in case of three-CC inter-band CA.

Features
• LTE1543: 8x2 SU MIMO with TM9

• LTE2022: Beamforming Enhancements
• LTE493: TDD Beamforming
• LTE541: Dual Stream Beamforming
• LTE1013: Dynamic Transmission Mode Switch (with Enhanced Support for
TM3/TM8)
• LTE1636: Extended OBSAI site configuration
• LTE2047: TD-LTE15A Site Configurations
• LTE113:Cell Bandwidth - 15 MHz
• LTE1951: Automatic Configuration support for CA for multi-carrier eNBs

• LTE42: Support of DRX in RRC connected mode
• LTE473: Extended DRX settings
g Note: If the DRX is used with DL CA, the UE activity affects the active time on
the three cells.
• LTE907: TTI Bundling
The UEs configured with transmission time interval (TTI) bundling cannot be
configured with the SCells. Activation of the TTI bundling mode might cause the
release of two SCells while deactivation might trigger the addition of two SCells.
• LTE1929: UL Semi-persistent Scheduling
• LTE1406: Extended VoLTE Talk Time
The extended Voice over LTE (VoLTE) talk time triggers deconfigure two SCells and
might configure two SCells for three-cell-CA candidate UE. The voice bearer is set
up via the E-UTRAN radio access bearer (E-RAB) setup request procedure.
• LTE13: Rate Capping (UL/DL)
Scheduling the UE by multiple DL schedulers affects in fulfilling the AMBR. The UE
AMBR is divided into active cells according to a dynamic split. Fulfilling the divided
UE AMBR within each serving cell is done in the same way as in the case of a single
cell operation. The UE AMBR measurement in each cell considers the total
scheduled UE AMBR over all the active cells. The UE AMBR division is effective on a
cell when the rate capping is triggered by the corresponding measurement.
• LTE1042: Nominal Bitrate for non-GBR bearers
• LTE1170: Inter-frequency Load Balancing
Since the SCell-configured UEs are already load balanced, this feature does not
select these UEs as a load-balancing candidate. Monitoring the average weight for
non-GBR bearers in the DL Scheduler is updated to consider the UEs scheduled on
the three serving cells.
• LTE1534: Multiple Frequency Band Indicator
The eNB must consider the mapped bands when checking if the UE supports the
band combination for the three-cell CA. The mapped E-UTRA absolute radio
frequency channel number (EARFCN) is used for the SCells to communicate with the
UE if the native EARFCN is not supported by the UE. Note that the mapped
EARFCN can also be used for the PCell if it is done in the initial context setup. In
general, the LTE1836: TDD Downlink Carrier Aggregation – 60 MHz feature does not
depend on the LTE1534: Multiple Frequency Band Indicator feature. However, it may
be used to support additional three-cell band combinations.

Features
• LTE1113: eICIC – macro

The LTE1113: eICIC – macro feature interworking with the DL CA on a given serving
cell of the macro eNB is the same and it is not modified by the LTE1836: TDD
Downlink Carrier Aggregation – 60 MHz feature. The CA UE is not scheduled in the
almost blank subframe (ABS) of a given serving cell. Note that there is no special
handling in the time domain scheduling metric calculation of the CA UEs.
This feature affects the Uu interface as follows:
• new configuration options and content in the SCell addition/release of two SCells
• UECapabilityInformation includes the CA-related UE capabilities
(supportedBandCombination for CA of three cells)
• new activation/deactivation combinations in the MAC CE for two SCells
• PUCCH format 3
• multi-serving cells (three CCs) positive acknowledgment/negative acknowledgment
(ACK/NACK) bits on the physical uplink shared channel (PUSCH)


The impact on system performance focuses on a single UE throughput as follows:
• For DL, the single throughput is enhanced significantly by aggregating three CCs
together.
• For UL, the single UE throughput is reduced slightly because of the increase in the
PUCCH-occupied UL resource.
The impact on system capacity focuses at the PUCCH resource aspects as follows:
• The three-CC CA UEs must be applied with PUCCH format 3 so that the maximum
number of supported CCs (three-CC CA UEs) per serving cell depends on the
number of physical resource blocks (PRBs) allocated to the PUCCH format 3.
• The maximum number of supported CCs (two-CC CA UEs) does not only depend on
the legacy-allocated PUCCH format 1bCS resource and the resource overbook rate,
but also on how many three-CC-CA capable UE fallback to the two-CC scenario with
PUCCH format 3 resource.
Management data
Sales information

Requirements

Features

FDD TDD
Alarms
There are no alarms related to the LTE1836: TDD Downlink Carrier Aggregation - 60
MHz feature.

There are no faults related to the LTE1836: TDD Downlink Carrier Aggregation - 60 MHz
feature.
Commands
There are no commands related to the LTE1836: TDD Downlink Carrier Aggregation - 60
MHz feature.

M8001C497 Average number of DL carrier LTE Cell Load
aggregated capable UEs for 3
CCs
M8001C498 Average number of UEs with LTE Cell Load
two configured SCells
M8001C499 Average number of UEs with LTE Cell Load
two activated SCells
M8011C166 SCell scheduling blocking rate LTE Cell Resource
due to conflicts on PUCCH
format 1bwcs resources

Features
Table 96 Existing counters related to LTE1836 (Cont.)

M8011C167 SCell scheduling blocking rate LTE Cell Resource
due to conflicts on PUCCH
format 3 resources
For counter descriptions, see LTE Operating Documentation/ Reference/ Counters and

KPI ID KPI name
LTE_5700a E-UTRAN SCell Scheduling Blocking Rate due to Conflicts on
PUCCH Format 1bwcs Resources
LTE_5701a E-UTRAN SCell Scheduling Blocking Rate due to Conflicts on
PUCCH Format 3 Resources
For KPI descriptions, see LTE Operating Documentation/ Reference/ Counters and Key
Performance Indicators.
Parameters

name object
Conservativene scellActivationL LNBTS - TDD
ss level of SCell evel
activation

Full name Abbreviated Managed object Parent structure FDD/TDD
name
Carrier caRelId CAREL - TDD
aggregation
relation identifier
Local cell lcrId CAREL - TDD
resource ID of
cell to be
aggregated
downlink carrier
aggregation
Scheduling CA caSchedFairFact LNBTS - TDD
fairness control
factor
SCell activation sCellActivationMe LNBTS - TDD
method thod

Features

Full name Abbreviated Managed object Parent structure FDD/TDD
name
Cell resource cellResourceShar LNCEL - TDD
sharing mode ingMode
Maximum maxNumActUE LNCEL_TDD - TDD
number of active
UEs
Max number maxNumCaConf LNCEL_TDD - TDD
carrier aggr Ue3c
configured UEs 3
Carriers
Max number maxNumCaConf LNCEL_TDD - TDD
Carrier Aggr UeDc
configured UEs
double carrier
secondary cells
for DL carrier
aggr
PUCCH nCqiRb MPUCCH - TDD
bandwidth for
CQI
Number of nPucchF3Prbs MPUCCH - TDD
PUCCH PRBs for
HARQ format 3
Enable sim. UL simUlSpsPf3 LNCEL_TDD - TDD
SPS and PUCCH
format 3 for a UE
Uplink power uplinkPCCommo SIB - TDD
control common nr10
rel10 add-ons
UL power offset deltaFPucchF1bC SIB uplinkPCCommo TDD
for PUCCH Sr10 nr10
format 1bCS
UL power offset deltaFPucchF3r1 SIB uplinkPCCommo TDD
for PUCCH 0 nr10
format 3
Sales information


Features
16.3 Activating and configuring LTE1836: TDD Downlink

Carrier Aggregation - 60 MHz
Before you start
parameter activates the feature. The Max number of secondary cells for DL
carrier aggr (maxNumScells) parameter allows aggregation of three serving cells.
Modification of these parameters requires eNB restart.
Table 101 Parameters used for activating and configuring the LTE1836: TDD
Downlink Carrier Aggregation - 60 MHz feature
object locking
Activation of downlink activation flag eNB restart
Carrier aggregation
(actDLCAggr)
Max number of mandatory configuration eNB restart
secondary cells for DL
carrier aggr
(maxNumScells)
The LTE1836: TDD Downlink Carrier Aggregation - 60 MHz feature is enabled together
with the LTE1558: TDD Downlink Carrier Aggregation, LTE1830: TDD Downlink Carrier
Aggregation Enhancement, and LTE1562: Carrier Aggregation for Multi-carrier eNodeBs
features. These features use the same activation flag. For more information about
feature dependencies, see Interdependencies between features.
The eNB supports the deployment required for CA. All LNCELs in the eNB must have
the Carrier aggregation pool ID (caPoolId) parameter configured when the
LTE1836: TDD Downlink Carrier Aggregation - 60 MHz feature is enabled. The CA cells
with subordinated CAREL or CA cells linked by CAREL-lcrId of another LNCEL must
have the same CA pool ID.
If there are more than two cells per sector, each cell can have multiple CARELs and
each cell can be linked by CAREL-lcrId of other multiple cells. The maximum number
of SCell candidates per PCell is two. Multiple CARELs of one cell do not point to the
same cell.
The following parameters must be set before activating the LTE1836: TDD Downlink
Carrier Aggregation - 60 MHz feature:
• The PUCCH bandwidth for CQI (nCqiRb) parameter must have a value
greater than 1 and a value greater than the value of the Number of PUCCH PRBs
for HARQ format 3 (nPucchF3Prbs) parameter.
• The Number of PUCCH PRBs for HARQ format 3 (nPucchF3Prbs)
parameter must have a value greater than 0.

Features
Procedure

2 Configure the Activation of downlink Carrier


d) Set the Activation of downlink Carrier

factor (caSchedFairFact) parameter must be configured when the
3 Create a new CADPR object.


a) Expand the selected LNBTS object.

c) Set the Max number of secondary cells for DL carrier
g Note: When the parameter value is set to 2, the eNB uses CA with two or three
CCs. Two instances of CAREL must be configured for the
LTE1836: TDD Downlink Carrier Aggregation - 60 MHz feature to work.
Result

Features
Expected Outcome
The LTE1836: TDD Downlink Carrier Aggregation - 60 MHz feature is enabled in the
eNB. The eNB uses CA with two or three CCs.
16.4 Deactivating LTE1836: TDD Downlink Carrier

Before you start
The Max number of secondary cells for DL carrier
aggr (maxNumScells) parameter deactivates the feature. Modification of this
parameter requires eNB restart.
Procedure



e) Set the Max number of secondary cells for DL carrier
g Note: When the parameter value is set to 1, the eNB only uses CA with two
CCs. To deactivate CA completely, set the
parameter value to false.
Result
Expected outcome
The LTE1836: TDD Downlink Carrier Aggregation - 60 MHz feature is deactivated in the
eNB. The eNB only uses CA with two CCs.

LTE15A Radio Resource Management and Telecom LTE1838: TDD Downlink Inter-band Carrier
Features Aggregation - 40 MHz
17 LTE1838: TDD Downlink Inter-band Carrier

17.1 Description of LTE1838: TDD Downlink Inter-band

The LTE1838: TDD Downlink Inter-band Carrier Aggregation - 40 MHz feature enables
the Flexi Multiradio BTS to support inter-band carrier aggregation (CA) in the downlink
(DL) for two component carriers (CCs). This feature is an extension to the LTE1558:
TDD Downlink Carrier Aggregation and LTE1830: TDD Downlink Carrier Aggregation
Enhancement features.
Benefits
End-user benefits
Operator benefits
This feature provides higher DL peak data rates for user equipment (UE) with inter-band
CA.
Functional overview
The LTE1838: TDD Downlink Inter-band Carrier Aggregation - 40 MHz feature enables
the Flexi Multiradio BTS to support inter-band CA in the DL for two CCs. A mix of CA and
non-CA UEs is supported in the DL. The maximum aggregated DL bandwidth (BW) is 40
MHz, which is up to 20 MHz for each cell BW and the uplink (UL) is only on the primary
cell (PCell).
The supported band combination for the deployment scenarios 1 and 2 as described in
the 3rd Generation Partnership Project (3GPP) TS 36.300 is the band 41 + band 39
band combination.
Figure 11: CA scenario 1 and Figure 12: CA scenario 2 show examples of the supported
CA scenarios:

LTE1838: TDD Downlink Inter-band Carrier LTE15A Radio Resource Management and Telecom
Aggregation - 40 MHz Features
Figure 11 CA scenario 1
f1 f2
TDD config#2:7 TDD config#2:5, 2/9
CA scenario 1
Figure 12 CA scenario 2
f1 f2
TDD config#2:7 TDD config#2:5, 2/9
CA scenario 2
The following are the supported cell BW combinations:
• 20 MHz + 20 MHz
• 20 MHz + 10 MHz
For the supported site configurations, see the LTE2047: TD-LTE15A Site Configurations
feature description.
The DL CA is applied for UEs with related UE capabilities. The two CCs use the same
time division duplex (TDD) frame configuration and might have the same or different
special subframe (SSF) configuration.
g Note: This feature does not support different UL/DL configurations between inter-band
cells. Instead, it supports different SSF configurations between inter-band cells.
Interworking with LTE1836

The LTE1838: TDD Downlink Inter-band Carrier Aggregation feature also supports inter-
band CA in the DL for three CCs (two serving cells are intra-band and the other serving
cell is inter-band). The feature is also an extension to the LTE1836: TDD Downlink
Carrier Aggregation - 60 MHz feature. Some of the three-CC CA functions are applied in
this feature to interwork with the LTE1836: TDD Downlink Carrier Aggregation - 60 MHz
feature. The physical uplink control channel (PUCCH) format 3 resource is allocated to
UEs that can be configured with two secondary cells (SCells) in the three-carrier site

solution. The uplink control information (UCI) only scheduling algorithm that is
implemented in the LTE1838: TDD Downlink Inter-band Carrier Aggregation feature is
also used in the LTE1836: TDD Downlink Carrier Aggregation - 60 MHz feature. For
more details, see the LTE1836: TDD Downlink Carrier Aggregation - 60 MHz feature
description.
System impact
g Note: These features have the same activation flag, which is the actDLCAggr
parameter.
The LTE993: Cell Combination (Super cell) feature cannot be enabled together with this
feature.
• LTE2047: TD-LTE15A Site Configuration

• LTE1836: TDD Downlink Carrier Aggregation – 60 MHz
• LTE1929: UL Semi-persistent Scheduling


The LTE1838: TDD Downlink Inter-band Carrier Aggregation - 40 MHz feature enhances
the single user DL-peak throughput through aggregation of two CCs of different
frequency band. This is specifically band 41 + band 39.
Only 20 MHz + 20 MHz or 20 MHz + 10 MHz inter-band CA is supported in this feature.
• The maximum number of CA-configured UEs per cell is 100 in case the PUCCH
format 3 resource is configured. In case it is not configured, the maximum number of
CA-configured UEs per cell is 100.
• The maximum number of RRC_Connected UEs per cell is 600 for TDD configuration
1 at 20 MHz BW, 400 for TDD configuration 2 at 20 MHz BW, and 400 for TDD
configuration 1/2 at 10 MHz BW.
• The maximum number of scheduled UEs per cell per transmission time interval (TTI)
is 12 at 20 MHz and 10 at 10 MHz BW.


Requirements

FDD TDD
Flexi Multiradio 10 BTS Not supported Not supported
Alarms
There are no alarms related to the LTE1838: TDD Downlink Inter-band Carrier
Aggregation - 40 MHz feature.

There are no faults related to the LTE1838: TDD Downlink Inter-band Carrier
Commands
There are no commands related to the LTE1838: TDD Downlink Inter-band Carrier

There are no measurements or counters related to the LTE1838: TDD Downlink Inter-
band Carrier Aggregation - 40 MHz feature.

There are no key performance indicators related to the LTE1838: TDD Downlink Inter-
band Carrier Aggregation - 40 MHz feature.
Parameters


name object
Enable sim. UL simUlSpsPf3 LNCEL_TDD - TDD
SPS and
PUCCH format
3 for a UE
Maximum code uciOnlyMaxCod LNCEL_TDD - TDD
rate for UCI- eRate
only TX in UL

name object
Local cell lcrId CAREL - TDD
resource ID of
cell to be
aggregated
downlink carrier
aggregation
Scheduling CA caSchedFairFa LNBTS - TDD
fairness control ct
factor
SCell activation sCellActivation LNBTS - TDD
cycle period CyclePeriod
Max number maxNumCaCon LNCEL_TDD - TDD
carrier aggr fUe3c
configured UEs
3 Carriers
Max number maxNumCaCon LNCEL_TDD - TDD
Carrier Aggr fUeDc
configured UEs
double carrier
secondary cells
for DL carrier
aggr
PUCCH nCqiRb LNCEL - TDD
bandwidth for
CQI
Number of nPucchF3Prbs MPUCCH_TDD - TDD
PUCCH PRBs
for HARQ
format 3
SCell UE sCellTmSetting LNCEL - TDD
transmission WithBf
mode setting
Sales information


17.3 Activating and configuring LTE1838: TDD Downlink

Inter-band Carrier Aggregation - 40 MHz
Before you start
parameter is used to activate the feature. Modification of this parameter requires evolved
Node B (eNB) restart.
The LTE1838: TDD Downlink Inter-band Carrier Aggregation - 40 MHz feature is enabled
together with the LTE1558: TDD Downlink Carrier Aggregation and LTE1830: TDD
Downlink Carrier Aggregation Enhancement features. These features use the same
activation flag. For more information about feature dependencies, see Interdependencies
between features.
The LTE993: Cell Combination (Super cell) feature cannot be enabled together with the
LTE1838: TDD Downlink Inter-band Carrier Aggregation - 40 MHz feature. The Max
number of secondary cells for DL carrier aggr (maxNumScells)
parameter value must be set to 1. The PCell and SCell must not have their carriers in the
same band.
Procedure





factor (caSchedFairFact) and Carrier aggregation pool
ID (caPoolId) parameters must be configured when the
3 (Optional) Create a new CADPR object.


Result
Expected outcome
The LTE1838: TDD Downlink Inter-band Carrier Aggregation - 40 MHz feature is
activated together with all other existing CA features in all LNCELs of the LNBTS.
g Note: The cells enabled with CA must have an SCell configured in the CAREL object. If
an LNCEL has no CAREL object created, there is no CA function.
17.4 Deactivating LTE1838: TDD Downlink Inter-band

Before you start
parameter is used to deactivate the feature. Modification of this parameter requires eNB
restart.

Procedure



Result
Expected outcome
The LTE1838: TDD Downlink Inter-band Carrier Aggregation - 40 MHz feature is
deactivated together with all other existing CA features in all LNCELs of the LNBTS.

LTE15A Radio Resource Management and Telecom LTE1850: TDD Intra-band Dual-carrier Operation within
Features a Flexi Zone Micro BTS
18 LTE1850: TDD Intra-band Dual-carrier

Operation within a Flexi Zone Micro BTS
18.1 Description of LTE1850: TDD Intra-band Dual-

carrier Operation within a Flexi Zone Micro BTS
change
March 08, LTE1850 reference data Added parameters for
2018 configuring maximum amount
of users per TTI.
Activating and configuring LTE1850: TDD Added new step for
Intra-band Dual-carrier Operation within a configuring the maximum
Flexi Zone Micro BTS amount of users per TTI.

The LTE1850: TDD Intra-band Dual-carrier Operation within a Flexi Zone Micro BTS
feature enables a two-cell configuration on the same frequency band to increase the LTE
capacity. Both cells must be adjacent to each other, fully synchronized, have the same
TDD downlink/uplink frame configuration, and the same special subframe configuration.
Benefits
End-user benefits
Operator benefits
feature allows the operator to increase the LTE capacity by configuring a second cell on
the same frequency band.
feature enables a two-cell configuration on the same frequency band to increase the LTE
capacity. With the feature enabled, it is possible to deploy a single cell on the single Flexi
Zone BTS or add a second cell, handling a different carrier, and deploy two cells. The
following Flexi Zone BTSs are supported for this feature:
• Flexi Zone Indoor Pico BTS

• Flexi Zone Micro BTS
• Flexi Zone Multiband Indoor Pico BTS
• Flexi Zone MultiBand Outdoor BTS
• Flexi Zone Mini Macro BTS
TDD bands 38, 39, 40, and 41 are supported, with the following cell bandwidth
combinations, within hardware limits:

LTE1850: TDD Intra-band Dual-carrier Operation within LTE15A Radio Resource Management and Telecom
a Flexi Zone Micro BTS Features
• 20 MHz + 20 MHz
• 20 MHz + 15 MHz
• 15 MHz + 15 MHz
• 20 MHz + 10 MHz
• 15 MHz + 10 MHz
• 10 MHz + 10 MHz
For the dual-carrier operation, the two cells must be adjacent to each other, with center
carrier spacing of Nx300 KHz (where N is an integer).
See Figure 13: Two-cell configurations on the same frequency band below for an
example of configurations.
Figure 13 Two-cell configurations on the same frequency band
A. twocellsofdifferentbandwidth
TBW
C1 BW G C2 BW
Cell1 Cell2
SP
Band frequency
B.twocellsofthesamebandwidth
TBW
C1 BW G C2 BW
Cell1 Cell2
SP
Band frequency
TBW-totalbandwidth
C1 BW -Cell1 bandwidth
C2 BW -Cell2 bandwidth
G-carriergap
SP -centercarrierspacing ofNx300Khz(Nisaninteger)
The minimum center carrier frequency spacing, which must be lower or equal to the
center carrier spacing, depends on the following cell bandwidths:
Table 107 The minimum center carrier frequency spacing

Minimum center Maximum center Cell 1 bandwidth Cell 2 bandwidth
carrier frequency carrier frequency (C1BW) (C2BW)
spacing spacing
19.8 MHz 20 MHz 20 MHz 20 MHz
17.1 MHz 17.7 MHz 20 MHz 15 MHz
17.1 MHz 17.7 MHz 15 MHz 20 MHz
15.0 MHz 15.2 MHz 15 MHz 15 MHz

Table 107 The minimum center carrier frequency spacing (Cont.)

Minimum center Maximum center Cell 1 bandwidth Cell 2 bandwidth
carrier frequency carrier frequency (C1BW) (C2BW)
spacing spacing
14.4 MHz 15.2 MHz 20 MHz 10 MHz
14.4 MHz 15.2 MHz 10 MHz 20 MHz
12.0 MHz 12.7 MHz 15 MHz 10 MHz
12.0 MHz 12.7 MHz 10 MHz 15 MHz
9.9 MHz 10.3 MHz 10 MHz 10 MHz
The total bandwidth (TBW) occupied by both cells (C1BW and C2BW) and the inter-
carrier gap (G) between them must be equal or less than 40 Mhz while the inter-carrier
gap must not exceed 200 kHz. The following inequality represents this relation: C1BW +
C2BW + G = TBW ≤ 40 MHz.
The two cells must also be fully synchronized, have the same TDD downlink/uplink frame
configuration, downlink power settings, the same special subframe configuration, and the
same PRACH configuration index parameter value. Both cells should be
configured and activated simultaneously. Configuring the second cell requires an eNB's
restart. Also, configuring parameters that require cell locking for one cell will lock the
second cell as well.
The feature affects the Flexi Zone Micro/Pico BTS by introducing new software capable
of processing two carriers. The new deployment scheme introduced affects O&M
procedures, software loading, and platform starting.
System impact
feature is related to:
• LTE1919: TDD Intra-band Multi-carrier Operation for Two-board Flexi Zone Micro
BTS, which introduces a multiband solution for Flexi Zone Micro/Pico BTS with a
special dual-board architecture for Band 41 and defines O&M solutions and FZM
RFSW operability for a dual band
• LTE113: Cell Bandwidth 15 MHz, which introduces a 15 MHz LTE cell radio
frequency (RF) bandwidth with 3GPP-specified bit rates and supported UE capability
• LTE2183: RL65TD Capacity and Dimensioning for Flexi Zone Micro, which defines
capacity, dimensioning, and performance requirements for configurations provided by
the LTE1850 feature
• LTE1163: TD-LTE Dual-carrier Operation within One RRH/RF Module, which
provides the basis for a dual-carrier support from one RF module
• LTE1951: Automatic Configuration Support for CA for Multicarrier Cells, which adds
an optimizer support of new site configurations with more than two carriers per sector
and a support of new bandwidth combinations
• LTE689: LTE IPSec Support, which adds both control and bearer security via the
NetCP SA
• LTE2125: eICIC Micro Enhancement for Carrier Aggregation Interworking, which
introduces interworking of the carrier aggregation and eICIC in the Flexi Zone
Micro/Pico BTS

The feature has no impact on interfaces.

The feature has no impact on network management tools.

feature enhances performance by allowing operation on a second cell of up to 20 MHz
bandwidth.
Performance of a cell in the two-cell configuration may not be equal to the performance
of a cell in the single-cell configuration.

LTE1850: TDD Intra-band Dual-carrier Operation within a Flexi Zone Micro BTS
requirements, parameters, and sales information
Requirements

FDD TDD
Flexi Zone BTS Not supported TL15A
Flexi Zone Controller Not supported TL15A
Cloud Flexi Zone Controller Not supported TL17A
OMS Not supported Support not required
NetAct Not supported Support not required
MME Not supported Support not required
SAE GW Not supported Support not required

feature requires one of the following single-board hardware:
• LTE1964: FWHF Flexi Zone BTS 2600 (Band 41 NB), total supported bandwith of 30
MHz

• LTE1729: FWHE Flexi Zone BTS 2600 (Band 41 NB), total supported bandwith of 40
MHz
Alarms
There are no alarms related to the LTE1850: TDD Intra-band Dual-carrier Operation
within a Flexi Zone Micro BTS feature.

There are no faults related to the LTE1850: TDD Intra-band Dual-carrier Operation within
a Flexi Zone Micro BTS feature.

There are no measurements or counters related to the LTE1850: TDD Intra-band Dual-
carrier Operation within a Flexi Zone Micro BTS feature.

There are no key performance indicators related to the LTE1850: TDD Intra-band Dual-
carrier Operation within a Flexi Zone Micro BTS feature.
Parameters

Full name Abbreviated name Managed Parent structure
object
Activate multiple actMultipleCarrie LNBTS -
carrier operation r
PRACH configuration prach Conf Index LNCEL -
index _TDD
Administrative state administrativeSta LNCEL -
te
EARFCN for both earfcn LNCEL -
Downlink and Uplink _TDD
(TDD)
Channel bandwidth TDD chBw LNCEL -
Resource list resourceList LCELL -
Maximum amount of users maxNumUeDl LNCEL -
per TTI in DL _TDD
Maximum amount of users maxNumUeDlDwPTS LNCEL -
per TTI in DL DwPTS _TDD
Maximum amount of users maxNumUeUl LNCEL -
per TTI in UL _TDD
For parameter descriptions, see the FZ BTS parameters document.
Sales information


ASW Pool license No
18.3 Activating and configuring LTE1850: TDD Intra-

band Dual-carrier Operation within a Flexi Zone
Micro BTS
Before you start
The LNBTS: Activate multiple carrier
operation (actMultipleCarrier) parameter is the activation flag. Modification of
this parameter requires eNB restart.
• LTE1964: FWHF Flexi Zone BTS 2600 (Band 41 NB)
• LTE1729: FWHE Flexi Zone BTS 2600 (Band 41 NB)
This feature requires two properly configured cells sharing a maximum power level.
Procedure

2 Configure cell resources.
a) Go to the LTE Carriers page.

b) For each cell, configure the Bandwidth as 10, 15, or 20 MHz.
c) For both cells, configure appropriate EARFCN objects.
3 Configure the same PRACH configuration index parameter value for each cell.

d) For each LNCEL object, set the PRACH configuration
index (prach Conf Index) parameter to the same value in each cell, from
ranges 3 to 7 and 51 to 53.


you need to select the LNCEL/LNCEL_TDD object.
4 Configure the maximum amount of users per TTI.


you need to select the LNCEL/LNCEL_TDD object.
e) For each object, set the maximum amount of users per TTI in DL and UL as
follows:
• Maximum amount of users per TTI in DL (maxNumUeDl) ≤ 6
• Maximum amount of users per TTI in DL
DwPTS (maxNumUeDlDwPTS) ≤ 4
• Maximum amount of users per TTI in UL (maxNumUeUl) ≤ 6
Expected outcome
The LNBTS: Activate multiple carrier operation
(actMultipleCarrier) parameter is automatically set to 2_carrierOperation
value. The eNB is restarted, the feature is activated, and the dual-carrier operation is
enabled.
18.4 Deactivating LTE1850: TDD Intra-band Dual-carrier

Operation within a Flexi Zone Micro BTS
Before you start
The LCELL: Resource list (resourceList) parameter is used for deactivation.
Modification of this parameter requires eNB restart.

Procedure

2 Delete one of the cells.

b) Delete one of the cells.
Expected outcome
The LNBTS: Activate multiple carrier operation
(actMultipleCarrier) parameter is automatically set to false value. The eNB is
restarted, the feature is deactivated, and the dual-carrier operation is disabled.

LTE15A Radio Resource Management and Telecom LTE1896: TDD Intra-band Dual-carrier Downlink
Features Aggregation for Flexi Zone Micro
19 LTE1896: TDD Intra-band Dual-carrier

Downlink Aggregation for Flexi Zone Micro
19.1 Description of LTE1896: TDD Intra-band Dual-

carrier Downlink Aggregation for Flexi Zone Micro
The LTE1896: TDD Intra-band Dual-carrier Downlink Aggregation for Flexi Zone Micro
feature introduces downlink carrier aggregation in a dual-carrier configured eNB with a
maximum of 40 MHz bandwidth. The downlink carrier aggregation can be applied to UEs
with related UE capabilities.
Benefits
End-user benefits
feature provides higher peak data rates for UEs than in the regular coverage and
increases the average UE downlink throughput.
Operator benefits
feature enables operators with a fragmented band spectrum to provide enhanced end-
user experience similar to operators with a single downlink carrier of up to 40 MHz.
Requirements
Functional overview
feature is an extension of the LTE1850: TDD Intra-band Dual-carrier Operation within a
Flexi Zone Micro BTS feature (see Figure 1). It supports downlink carrier aggregation on
band 38 and band 41, in the following cell bandwidth configurations:
• 20 MHz + 20 MHz
• 20 MHz + 15 MHz
• 20 MHz + 10 MHz
• 15 MHz + 15 MHz

LTE1896: TDD Intra-band Dual-carrier Downlink LTE15A Radio Resource Management and Telecom
Aggregation for Flexi Zone Micro Features
Figure 14 Dual-carrier downlink aggregation as an extension of the LTE1850 feature
LTE1850
Cell1 Cell2
LTE1896
Dual-carrier downlink aggregation
Of the two cells used in a dual-carrier operation, for carrier aggregation, the cell that
handles the RRC connection is the primary cell (PCell) and the other cell is the
secondary cell (SCell). The downlink carrier aggregation applies to UEs with related UE
capabilities. Non-guaranteed bit rate (Non-GBR) data radio bearers (DRB) can be served
on both cells. GBR DRB(s) and signaling radio bearers (SRB) are served on the primary
cell (PCell) only.
Feature functional extensions
feature introduces the following functional extensions into the downlink carrier
aggregation:
• Radio admission control - UEs are admitted based on the primary cell's (PCell's) and
secondary cell's (SCell's) admission control settings. The same thresholds apply as
for non-carrier aggregation capable UEs.
• Mobility - the following mobility scenarios are supported:
– handover of UEs with carrier aggregation activated to carrier-aggregation-
enabled cells
– handover from non-carrier-aggregation-enabled cells to carrier-aggregation-
enabled cells
– handover of UEs with carrier aggregation activated to cells without carrier
aggregation
– all types of inter-RAT handovers to and from cells without carrier aggregation
Handovers of UE with a configured, or activated, SCell to another cell with carrier
aggregation enabled will not preserve carrier aggregation automatically.
The mobility for carrier-aggregation-configured UEs is based on PCell
measurements. The same measurement configurations apply as for non-CA
configured UEs, e.g. event A3 and/or event A5.
• SCell handling - the SCell is configured blindly once the UE capabilities are known to
the eNB. The SCell is deactivated when the MAC timer expires. A barred cell can be
used as the SCell for UE that has already configured the SCell. New SCell
configurations are not allowed for barred cells.
• Scheduling - UEs with an activated SCell are scheduled by separate and coordinated
downlink schedulers. Downlink schedulers synchronize the DRX handling and the
measurement gap handling. An operator-configurable parameter controls the
fairness between carrier-aggregation-capable UEs and carrier-aggregation-incapable
UEs. The combined downlink throughput is used for the proportional fair scheduling
and a UE's aggregate maximum bit rate (AMBR) control.

• Physical uplink control channel (PUCCH) - the PUCCH resource allocation for CQI,
SR, and HARQ-ACK is adapted in order to handle two downlink component carriers.
System impact
feature is related to:
• LTE1850: TDD Intra-band Dual-carrier Operation within a Flexi Zone Micro BTS,
which introduces an FZM dual-carrier operation and is the base for enabling
LTE1896
• LTE1920: TDD Intra-band Two Carrier Aggregation for Two-board Flexi Zone Micro
Platform, which introduces carrier aggregation for an FZM multi-carrier. It identifies
U-Plane and C-Plane use cases applicable in the context of LTE1896
• LTE113: Cell Bandwidth 15 MHz, which introduces a 15 MHz LTE cell radio
frequency (RF) bandwidth with 3GPP-specified bit rates and supported UE capability
• LTE2183: RL65TD Capacity and Dimensioning for Flexi Zone Micro, which defines
capacity, dimensioning, and performance requirements for configurations provided by
the LTE1896 feature
• LTE1163: TD-LTE Dual-carrier Operation within One RRH/RF Module, which
provides the basis for a dual-carrier support from one RF module
• LTE1951: Automatic Configuration Support for CA for Multicarrier Cells, which adds
an optimizer support of new site configurations with more than two carriers per
sector, and a support of new bandwidth combinations
• LTE689: LTE IPSec Support, which adds both control and bearer security via the
NetCP SA
• LTE2125: eICIC Micro Enhancement for Carrier Aggregation Interworking, which
introduces interworking of the carrier aggregation and eICIC in the FZM


Management data
Sales information

Requirements


FDD TDD
NetAct Not supported Not supported

Alarms
There are no alarms related to the LTE1896 feature.

There are no measurements or counters related to the LTE1896 feature.

There are no key performance indicators related to the LTE1896 feature.
Parameters
There are no new parameters related to LTE1896 feature.
There are no modified parameters related to LTE1896 feature.

Full name Abbreviated name Managed Parent structure FDD/TDD
object
Maximum number of maxNumRrc LNCEL - common
RRC connections
Maximum number RRC maxNumRrcEmerg LNCEL - common
emergency ency


Full name Abbreviated name Managed Parent structure FDD/TDD
object
Carrier Aggregation caRelId CAREL - common
Relation identifier

Sales information

ASW Pool license No
19.3 Activating and configuring LTE1896: TDD Intra-

band Dual-carrier Downlink Aggregation for Flexi
Zone Micro
Before you start
Table 114: Parameters used for activating and configuring LTE1896: TDD Intra-band
Dual-carrier Downlink Aggregation for Flexi Zone Micro lists parameters used for the
activation and configuration of the LTE1896: TDD Intra-band Dual-carrier Downlink
Aggregation for Flexi Zone Micro feature.
Table 114 Parameters used for activating and configuring LTE1896: TDD Intra-band
Dual-carrier Downlink Aggregation for Flexi Zone Micro
object locking
Activation of downlink carrier activation flag restart
aggregation (actDLCAggr)
Local cell resource ID of cell to be mandatory configuration object locking
aggregated (lcrId)
Before activation of the LTE1896: TDD Intra-band Dual-carrier Downlink Aggregation for
Flexi Zone Micro feature, the LTE1850: TDD Intra-band Dual-carrier Operation within a
Flexi Zone Micro BTS feature needs to be activated and configured.

Procedure

2 If it does not exist, create and configure at least one instance of CAREL under PCell for
the relevant SCell. To configure one instance, do the following:

d) Select the LNCEL object for PCell.
e) On the selected LNCEL object, create a new CAREL instance.
f) In the CAREL instance, set the Local cell resource ID of cell to
be aggregated (lcrId) parameter value to SCell ID.
3 If not activated, enable the feature flag for the LTE1896: TDD Intra-band Dual-carrier
Downlink Aggregation for Flexi Zone Micro feature.

g Note: Configure LNBTS: Scheduling CA fairness control

factor (ca Sched Fair Fact) parameter and
LNCEL: Carrier aggregation pool ID (ca Pool Id) parameters as
required.
4 If required, configure RRC parameters for PCell.

e) Set Maximum number of RRC connections (maxNumRrc) and Maximum
number RRC emergency (maxNumRrcEmergency) parameters values as
required.

g Note: For the Maximum number RRC

emergency (maxNumRrcEmergency) parameter:
if actEmerCallRedir is set to enabled OR actIMSEmerSessR9 is set to
true AND in PCell's LNCEL
• riEnable set to true AND
– n1PucchAn is not set to 10 AND riPerM is set to 2:
maxNumRrcEmergency ≤ min(nCqiRb * 6 * cqiPerNp, (n1PucchAn
– 48) * cellSrPeriod) * X
– n1PucchAn is not set to 10 AND riPerM is set to 1:
maxNumRrcEmergency ≤ min(nCqiRb * 6 * cqiPerNp/2,
(n1PucchAn – 48) * cellSrPeriod) * X
– n1PucchAn is set to 10 AND riPerM is set to 2:
maxNumRrcEmergency ≤ min(nCqiRb * 6 * cqiPerNp, 2 *
cellSrPeriod) * X
– n1PucchAn is set to 10 AND riPerM is set to 1:
maxNumRrcEmergency ≤ min(nCqiRb * 6 * cqiPerNp/2, 2 *
cellSrPeriod) * X
• riEnable set to false AND
– n1PucchAn is not set to 10 : maxNumRrcEmergency ≤ min(nCqiRb *
6 * cqiPerNp, (n1PucchAn – 48) * cellSrPeriod) * X
– n1PucchAn is set to 10 : maxNumRrcEmergency ≤ min(nCqiRb * 6 *
cqiPerNp, 2 * cellSrPeriod) * X
The value X above depends on the TDD frame configuration:

• if tddFrameConf is 1 AND cqiPerNp > 1ms: X=0.4
• if tddFrameConf is 2: X=0.2

g Note: For the Maximum number of RRC connections (maxNumRrc)

parameter:
in PCell's LNCEL:
• riEnable set to true AND
– n1PucchAn is not set to 10 AND riPerM is set to 2: maxNumRrc +
max(addAUeRrHo,addAUeTcHo) ≤ min(nCqiRb * 6 * cqiPerNp,
– n1PucchAn is not set to 10 AND riPerM is set to 1: maxNumRrc +
max(addAUeRrHo,addAUeTcHo) ≤ min(nCqiRb * 6 * cqiPerNp/2,
– n1PucchAn is set to 10 AND riPerM is set to 2: maxNumRrc +
max(addAUeRrHo,addAUeTcHo) ≤ min(nCqiRb * 6 * cqiPerNp, 2 *
cellSrPeriod) * X
– n1PucchAn is set to 10 AND riPerM is set to 1: maxNumRrc +
max(addAUeRrHo,addAUeTcHo) ≤ min(nCqiRb * 6 * cqiPerNp/2, 2 *
cellSrPeriod) * X
• riEnable set to false AND
– n1PucchAn is not set to 10 : maxNumRrc +
max(addAUeRrHo,addAUeTcHo) ≤ min(nCqiRb * 6 * cqiPerNp,
– n1PucchAn is set to 10 : maxNumRrc +
max(addAUeRrHo,addAUeTcHo) ≤ min(nCqiRb * 6 * cqiPerNp, 2 *
cellSrPeriod) * X
The value X above depends on the TDD frame configuration:

• if tddFrameConf is 1 AND cqiPerNp = 1ms: X=1
• if tddFrameConf is 1 AND cqiPerNp > 1ms: X=0.4
• if tddFrameConf is 2: X=0.2
Expected outcome
The eNB is restarted, and the dual-carrier downlink aggregation is enabled for new UEs
with the corresponding UE capabilities.

19.4 Deactivating LTE1896: TDD Intra-band Dual-carrier

Downlink Aggregation for Flexi Zone Micro
Before you start
The LNBTS: Activation of downlink carrier
aggregation (actDLCAggr) parameter is used for deactivating the feature.
Alternatively, to deactivate the feature, removing CAREL instance with Local cell
resource ID of cell to be aggregated (lcrId) parameter value set to
SCell ID is required. Both modifications require eNB restart.
Procedure

2 Deactivate the feature flag for LTE1896 or remove CAREL instance related to SCell.

Or
e) On the selected LNCEL object, remove the CAREL instance with Local cell
resource ID of cell to be aggregated (lcrId) parameter value
set to SCell ID.
Expected outcome
The eNB is restarted, and the feature is disabled.

LTE1905: PLMN ID and SPID Selected Mobility Profiles LTE15A Radio Resource Management and Telecom
Features
20 LTE1905: PLMN ID and SPID Selected Mobility

Profiles
The LTE1905: PLMN ID and SPID Selected Mobility Profiles feature replaces a virtual
SPID calculation, provided by the LTE486: PLMN ID Selected Mobility Profiles feature,
with a provisioned PLMN-SPID-based method for selecting a mobility profile.
Additionally, the LTE1905: PLMN ID and SPID Selected Mobility Profiles feature also is
related to the LTE490: Subscriber profile based mobility feature; with the LTE1905:
PLMN ID and SPID Selected Mobility Profiles feature there are profile selection based
on: SPID only, PLMN only, and SPID-PLMN.
Benefits
End-user benefits
Operator benefits
The UE mobility is optimized because:
• The operator can specify a method for selecting a mobility profile: PLMN ID only,
SPID only, or combined PLMN ID and SPID.
• The operator can provision separate SPIDs and mobility profiles per PLMN.
A mobility profile contains lists of allowed target LTE and inter-RAT frequencies/bands
that are used for a UE's mobility. The eNB selects the mobility profile by comparing one
of the following values with the moPrMappingList LNCEL parameter:
• a UE's Subscriber profile ID (SPID) received from an MME - introduced with the
LTE490: Subscriber Profile-based Mobility feature
• a UE's serving public land mobile network (PLMN)
g Note: A virtual SPID introduced with the

LTE486: PLMN ID Selected Mobility Profiles is replaced with the
LTE1905: PLMN ID and SPID Selected Mobility Profiles feature.
• a UE's serving PLMN ID and SPID - introduced with the LTE1905: PLMN ID and
SPID Selected Mobility Profiles feature
The moProfileSelect parameter values

When the LTE1905: PLMN ID and SPID Selected Mobility Profiles feature is enabled
(the actSelMobPrf parameter is set to true), the eNB's behavior depends on the
profile selection method indicated by the moProfileSelect LNBTS parameter, the
configuration in the moPrMappingList LNCEL parameter, the UE's serving PLMN,
and the SPID value, if provided by the MME.
For the moProfileSelect=spid, the eNB uses the SPID value if provided by the
MME and searches the mobility profile in the moPrMappingList table, using the SPID
value. It ignores the PLMN value in the table. If a match is not found, or the SPID was
not received from the MME, the default mobility profile is used.

LTE15A Radio Resource Management and Telecom LTE1905: PLMN ID and SPID Selected Mobility Profiles
Features
For the moProfileSelect=plmn, the eNB uses the serving PLMN ID of the UE to
search the mobility profile in the moPrMappingList table. It ignores the SPID value if
it was provided by the MME. If a match is not found, then the default mobility profile is
used.
For the moProfileSelect=combined, the eNB uses the serving PLMN ID and the
SPID to search the profile in the moPrMappingList table as follows:
• If both the PLMN ID and SPID values are available, the eNB looks up the table,
using both the PLMN ID and SPID first to find a match. If the match is not found, then
the eNB looks up the table, using only the SPID to find a match. The PLMN is then
represented by an empty wildcard on a mobility profile mapping list. If the match is
not found, then the eNB looks up the table, using only the PLMN ID to find a match.
The SPID is then represented by an empty wildcard on a mobility profile mapping list.
If the match is not found, then the default profile is used.
• If only the PLMN ID value is available (the MME did not provide any SPID value), the
eNB looks up the table, using only the PLMN ID to find a match. If the match is not
found, then the default mobility profile is used.
In all cases, if an entry is found in the moPrMappingList table, the moPrId from the
entry is used to find the mobility profile; otherwise, the MODPR is used.
Mobility profile mapping table

The mobility profile mapping table is extended with the PLMN ID (the mcc, mnc, and
mncLength) attributes in addition to the spid and spidLast attributes. These
attributes are used as a key to search the mobility profile identifier that points to the
actual mobility profile.
System impact
• LTE490: Subscriber Profile-based Mobility

The LTE1905: PLMN ID and SPID Selected Mobility Profiles feature is enabled only
when the LTE490: Subscriber Profile-based Mobility feature is enabled, and
moProfileSelect=plmn or moProfileSelect=combined. The LTE1905:
PLMN ID and SPID Selected Mobility Profiles feature also supports
moProfileSelect=spid.
No impact on interfaces.


No impact on system performance or capacity.

Requirements

Features

FDD TDD
Nokia AirScale BTS FL16 TL16
Cloud Flexi Zone Controller FL17A FL17A
NetAct NetAct 15.5 Support not required
UE Support not required Support not required
Alarms
There are no alarms related to the LTE1905: PLMN ID and SPID Selected Mobility
Profiles feature.

There are no faults related to the LTE1905: PLMN ID and SPID Selected Mobility
Profiles feature.
Commands
There are no commands related to the LTE1905: PLMN ID and SPID Selected Mobility
Profiles feature.

There are no measurements or counters related to the LTE1905: PLMN ID and SPID
Selected Mobility Profiles feature.

There are no key performance indicators related to the LTE1905: PLMN ID and SPID
Selected Mobility Profiles feature.
Parameters

d object
Mobile country code mcc LNCEL moPrMappingLis common
t
Mobile network code mnc LNCEL moPrMappingLis common
t

Features

d object
Mobile network code mncLength LNCEL moPrMappingLis common
length t

d object
Activate selective actSelMobPrf LNBTS - common
mobility profiles
Mobility profile moProfileSelec LNBTS - common
selection mode t
Mobility profiles moPrMappingLis LNCEL - common
mapping list t
Mobility profile ID moPrId LNCEL moPrMappingLis common
t
Subscriber profile spid LNCEL moPrMappingLis common
ID t
Last subscriber spidLast LNCEL moPrMappingLis common
profile ID of a t
range
Idle mode mobility modimpId MODIM - common
default profile P
identifier
Frequency layer freqLayListCsf MODPR - common
list for high bHighWcdma
priority CSFB to
WCDMA
list high priority bHighTdscdma
CSFB to TD-SCDMA
list for normal bNormWcdma
priority CSFB to
WCDMA
list normal bNormTdscdma
priority CSFB to
TD-SCDMA
Frequency layer freqLayListLte MODPR - common
list for LTE inter
frequency mobility
Frequency layer freqLayListPsH MODPR - common
list for packet oWcdma
switched handover
WCDMA
Frequency layer freqLayListPsH MODPR - common
list for PS oTdscdma
handover TD-SCDMA

Features

d object
Frequency layer freqLayListSrv MODPR - common
list for SRVCC to ccWcdma
WCDMA
Reference freq. refFreqListNac MODPR - common
list network cGeran
assisted cell
change GERAN
Band indicator bandIndicator MODPR refFreqListNac common
applied to cGeran
reference ARFCN
Reference ARFCN referenceARFCN MODPR refFreqListNac common
cGeran
Auto adaptation to autoAdapt MODPR - common
freq. layers of all
neighbour cells
Frequency layer freqLayListDed MODPR - common
list for ded. VoLTE VoLteHo
inter-frequency HO
Frequency layer freqLayListSer MODPR - common
list for VoLTE viceBasedHo
service based HO
Percentage of UE idleLBPercenta MODPR - common
for idle mode load geOfUes
balancing
Mobility default moDPrId MODPR - common
profile identifier
Reference frequency refFreqListSrv MODPR - common
list for SRVCC to ccGsm
GSM
Band indicator bandIndicator MODPR refFreqListSrv common
applied to ccGsm
reference ARFCN
Reference ARFCN referenceARFCN MODPR refFreqListSrv common
ccGsm
Idle mode mobility moimpId MOIMP - common
profile identifier
Percentage of UE idleLBPercenta MOPR - common
for idle mode load geOfUes
balancing
Mobility profile moPrId MOPR - common
identifier
Frequency layer freqLayListCsf MOPR - common
list for high bHighWcdma
priority CSFB to
WCDMA
list high priority bHighTdscdma
CSFB to TD-SCDMA

Features

d object
list for normal bNormWcdma
priority CSFB to
WCDMA
list normal bNormTdscdma
priority CSFB to
TD-SCDMA
Frequency layer freqLayListDed MOPR - common
list for ded. VoLTE VoLteHo
inter-frequency HO
Frequency layer freqLayListLte MOPR - common
list for LTE inter
frequency mobility
Frequency layer freqLayListPsH MOPR - common
list for packet oWcdma
switched handover
WCDMA
Frequency layer freqLayListPsH MOPR - common
list for PS oTdscdma
handover TD-SCDMA
Frequency layer freqLayListSer MOPR - common
list for VoLTE viceBasedHo
service based HO
Frequency layer freqLayListSrv MOPR - common
list for SRVCC to ccWcdma
WCDMA
Reference freq. refFreqListNac MOPR - common
list network cGeran
assisted cell
change GERAN
Band indicator bandIndicator MOPR refFreqListNac common
applied to cGeran
reference ARFCN
Reference ARFCN referenceARFCN MOPR refFreqListNac common
cGeran
Reference frequency refFreqListSrv MOPR - common
list for SRVCC to ccGsm
GSM
Band indicator bandIndicator MOPR refFreqListSrv common
applied to ccGsm
reference ARFCN
Reference ARFCN referenceARFCN MOPR refFreqListSrv common
ccGsm

Sales information

Features

20.2 Activating and configuring LTE1905: PLMN ID and

SPID Selected Mobility Profiles
Before you start
Table 119: Parameters used for activating and configuring LTE1905: PLMN ID and SPID
Selected Mobility Profiles lists the parameters used for activating and configuring the
LTE1905: PLMN ID and SPID Selected Mobility Profiles feature.
Table 119 Parameters used for activating and configuring LTE1905: PLMN ID and
SPID Selected Mobility Profiles
object locking
Activate selective mobility profiles activation flag no
(actSelMobPrf) LNBTS
Mobility profile selection mode mandatory configuration no
(moProfileSelect) LNBTS
Mobility profiles mapping list mandatory configuration no
(moPrMappingList) LNCEL
parameters structure
Last subscriber profile ID of a mandatory configuration no
range (spidLast)
Mobile country code (mcc) mandatory configuration requires object locking
Mobile network code (mnc) mandatory configuration requires object locking
Mobile network code length mandatory configuration requires object locking
(mncLength)
Mobility profile ID (moPrId) mandatory configuration no
Subscriber profile ID (spid) mandatory configuration no
Mobility profile identifier (moPrId) mandatory configuration no
MOPR
Idle mode mobility profile identifier mandatory configuration no
(moimpId) MOIMP
Idle mode mobility default profile mandatory configuration no
identifier (modimpId) MODIMP
The LTE1905: PLMN ID and SPID Selected Mobility Profiles feature is activated by the
Activate selective mobility profiles (actSelMobPrf) and
Mobility profile selection mode (moProfileSelect) LNBTS
parameters. The LTE490: Subscriber Profile-based Mobility feature is activated by the
same Activate selective mobility profiles (actSelMobPrf) LNBTS
parameter.

Features
Procedure

2 Activate the LTE1905: PLMN ID and SPID Selected Mobility Profiles feature.

d) If not already done, set the Activate selective mobility profiles
(actSelMobPrf) parameter's value to true.
e) Set the Mobility profile selection mode (moProfileSelect)
parameter's value to plmn or combined.
g Note: During migration from the previous release to the TDFDD-LTE 15A, the
already configured value of the Mobility profile selection mode
(moProfileSelect) parameter is kept. The new value of this parameter,
combined, can only be set after the migration to FDDTDD LTE15A.
3 Configure the Mobility profile ID (moPrMappingList) parameters' structure.

c) Select the New Mobility profiles mapping list object.
d) Set the parameters' values of the Mobility profiles mapping
list (moPrMappingList) structure according to your expectations. When
configuring, follow one of the below scenarios:
• In case Mobility profile selection mode (moProfileSelect)
parameter's value is set to plmn, configuration of the following parameters is
mandatory:
– Mobile country code (mcc)
– Mobile network code (mnc)
– Mobile network code length (mncLength)
– Mobility profile ID (moPrId)
• In case the Mobility profile selection
mode (moProfileSelect) parameter's value is set to combined, follow
one of the following configurations scenarios:
–
• Mobile country code (mcc)
• Mobile network code (mnc)

Features
• Mobile network code length (mncLength)

• Mobility profile ID (moPrId)
–
• Subscriber profile ID (spid)
• Last subscriber profile ID of a range (spidLast)
–
• Last subscriber profile ID of a range (spidLast)
• Mobile network code length (mncLength)
• Subscriber profile ID (spid)
g Note: If there is no element of the moPrMappingList configured, MODPR will

be used.
g Note: If the Mobility profile selection mode

(moProfileSelect) parameter's value was plmn in the previous release
(LTE486: PLMN ID Selected Mobility Profiles was activated), then after migration
to the FDDTD-LTE 15A the operator should check and configure, if needed, the
following LNCEL parameters in the
Mobility profiles mapping list (moPrMappingList) parameters'
structure:
• Mobile network code length (mncLength) LNCEL parameters in
the Mobility profiles mapping list(moPrMappingList)
4 Create the MOPR object.
a) Right-click the LNBTS object.

b) Select the new MOPR object.
c) Set the Mobility profile identifier (moPrId) parameter's value.
g Note: The Mobility profile identifier (moPrId) parameter's

value in the MOPR object needs to be equal to the Mobility profile ID
(moPrId) in the Mobility profiles mapping
list (moPrMappingList) parameters' structure.

Features
Expected outcome
The LTE1905: PLMN ID and SPID Selected Mobility Profiles and LTE490: Subscriber
Profile-based Mobility features are activated.
20.3 Deactivating LTE1905: PLMN ID and SPID Selected

Mobility Profiles with the actSelMobPrf parameter
Before you start
The Activate selective mobility profiles (actSelMobPrf) or
Mobility profile selection mode (moProfileSelect) parameter is used
for deactivation. Modification of the parameter requires neither eNB restart nor cell
locking.
Procedure

2 Deactivate the LTE1905: PLMN ID and SPID Selected Mobility Profiles and LTE490:
Subscriber Profile-based Mobility features with the actSelMobPrf parameter.

d) Set the Activate selective mobility profiles (actSelMobPrf)
parameter's value to false.
Expected outcome
The LTE1905: PLMN ID and SPID Selected Mobility Profiles and LTE490: Subscriber
Profile-based Mobility features are deactivated.

Features
20.4 Deactivating LTE1905: PLMN ID and SPID Selected

Mobility Profiles with the moProfileSelect
parameter
Before you start
The Activate selective mobility profiles (actSelMobPrf) or
Mobility profile selection mode (moProfileSelect) parameter is used
for deactivation. Modification of the parameter requires neither eNB restart nor cell
locking.
Procedure

2 Deactivate the LTE1905: PLMN ID and SPID Selected Mobility Profiles feature.

d) Set the Mobility profile selection mode (moProfileSelect)
parameter's value to spid.
Expected outcome
• The LTE1905: PLMN ID and SPID Selected Mobility Profiles feature is deactivated.
• If the actSelMobPrf = true, the eNB supports SPID-based mobility profile
selection as in the LTE490: Subscriber Profile-based Mobility feature.

LTE15A Radio Resource Management and Telecom LTE1925: Cause value for CSFB to GERAN without
Features DTM support
21 LTE1925: Cause value for CSFB to GERAN

without DTM support
21.1 Description of LTE1925: Cause Value for CSFB to

GERAN without DTM Support
The LTE1925: Cause Value for CSFB to GERAN without DTM Support feature
introduces a new cause value "UE not available for PS service" that can be used in
the S1AP:UE CONTEXT RELEASE REQUEST message. This new cause value is used
when a target GERAN system is not DTM capable. When the MME receives it,
preservation of the non-GBR bearers and suspension of GBR bearers is triggered.
Benefits
End-user benefits
No effect on the end-user experience.
Operator benefits
The operator can define a DTM capability of each eNB in the network.
Paging performance is improved with a PS suspension executed by the MME.
Requirements
Functional overview
The LTE1925: Cause Value for CSFB to GERAN without DTM Support feature
introduces a new parameter LNBTS: DTM capability of the GERAN target
that enhances CS fallback (CSFB) functionality already implemented by the LTE562:
CSFB to UTRAN/GERAN via redirection and LTE22: Emergency Call Handling features.
The new parameter indicates whether the CSFB target GERAN of the serving eNB is
DTM capable (by default it is set to "true").
g Note: DTM (Dual Transfer Mode) - the ability of a UE/eNB to simultaneously

receive/send both data (PS service) and voice (CS service) traffic.
If the target GERAN cell is not DTM capable, then after a CS fallback all data traffic
received or send by a UE must be suspended. The need to preserve the non-GBR
bearers and deactivate the GBR bearers is communicated to the MME via S1AP:UE
CONTEXT RELEASE REQUEST message with a cause set to "UE not available for PS
service."
S1AP: UE Context Release Request message and cause value

LTE1925: Cause value for CSFB to GERAN without LTE15A Radio Resource Management and Telecom
DTM support Features
The S1AP: UE CONTEXT RELEASE REQUEST message enables the eNB to request
the MME to release the UE-associated logical S1-connection due to variously generated
reasons known as cause values. A suitable cause value for an individual situation is
selected by the eNB. Possible cause values are:
• User Inactivity
• Radio Connection with UE lost
• Failure in the Radio Interface Procedure
• Timer TX2RELOCoverall or TS1RELOCoverall Expiry
• E-UTRAN Generated Reason
• Inter-RAT Redirection
• Radio or Transport Resources not Available
• Invalid QoS Combination
• CS Fallback Triggered
• Unspecified (Radio Netwok or Transport Network Layer)
• Redirection Towards 1xRTT
• UE not Available for PS service (introduced by the LTE1925: Cause Value for CSFB
to GERAN without DTM Support feature)
System impact
The LTE1925: Cause Value for CSFB to GERAN without DTM Support feature does not
have an activation flag and is enabled automatically when either LTE562: CSFB to
UTRAN/GERAN via Redirection or LTE22: Emergency Call Handling is activated.
This feature impacts the S1 interface by introducing a new cause value for the S1AP:UE
CONTEXT RELEASE REQUEST message.

No impact on network management tools.

Management data
Sales information


LTE1925: Cause value for CSFB to GERAN without DTM support requirements, alarms
and faults, commands, measurements and counters, KPIs, parameters, and sales
information
Requirements

FDD TDD
System release Not supported TD-LTE15A
Flexi Zone Access Point Not supported TL16
NetAct Not supported Not supported
Alarms
There are no alarms related to the LTE1925: Cause value for CSFB to GERAN without
DTM support feature.

There are no faults related to the LTE1925: Cause value for CSFB to GERAN without
DTM support feature.
Commands
There are no commands related to the LTE1925: Cause value for CSFB to GERAN
without DTM support feature.

There are no measurements or counters related to the LTE1925: Cause value for CSFB
to GERAN without DTM support feature.

There are no key performance indicators related to the LTE1925: Cause value for CSFB
to GERAN without DTM support feature.

LTE1925: Cause value for CSFB to GERAN without LTE15A Radio Resource Management and Telecom
DTM support Features
Parameters

name object
DTM capability of geranDtmCap LNBTS - Common
the GERAN target
Sales information

element
21.3 Activating and configuring LTE1925: Cause Value

for CSFB to GERAN without DTM Support
Before you start
have an activation flag and is enabled automatically when either LTE562: CSFB to
UTRAN/GERAN via Redirection or LTE22: Emergency Call Handling is activated.
The DTM capability of the GERAN target (geranDtmCap) parameter is
used for a mandatory configuration (defining the DTM capability of an eNB). Modification
of this parameter does not require either an eNB restart or cell locking.
To define whether the eNB supports the DTM, do the following:
Procedure
1 Configure the geranDtmCap parameter.

d) Set the DTM capability of the GERAN target (geranDtmCap)
parameter value to true (if the DTM is supported) or false (if the DTM is not
supported).
Activating and deactivating LTE features using the BTS Site Manager.

Expected outcome
DTM capability of the eNB is defined.
21.4 Deactivating LTE1925: Cause Value for CSFB to

GERAN without DTM Support
have an activation flag. To deactivate it, both LTE562: CSFB to UTRAN/GERAN via
Redirection and LTE22: Emergency Call Handling must be deactivated.

LTE1929: UL Semi-persistent scheduling LTE15A Radio Resource Management and Telecom
Features
22 LTE1929: UL Semi-persistent scheduling
22.1 Description of LTE1929: UL Semi-persistent

Scheduling
The LTE1929: UL Semi-persistent Scheduling feature introduces a UL semi-persistent
scheduling (SPS) and, through this, enables the eNB to allocate radio resources to UEs
for a sequence of TTIs that repeat with a certain periodicity via one PDCCH signal.
Consequently, the PDCCH signaling is reduced and more VoLTE users per cell can be
served in the scenario of PDCCH resource limitation.
Benefits
End-user benefits
This feature ensures better voice quality due to decreased end-to-end latency.
Operator benefits
It is possible for the operator to set a higher number of voice calls per cell.
Functional overview
The SPS is supported for a resource allocation on PUSCH. Due to certain periodic and
predictable characteristics of voice traffic (which means a fixed packet size and
frequency) generated from VoLTE calls, the SPS can be used to reduce the PDCCH
signaling. Consequently, the number of VoLTE users per cell is increased, through
allocating radio frequency (RF) resources for periodic TTIs via one PDCCH signal.
Applying the semi-persistent scheduling

SPS can be configured only when supported by UE's capabilities. To start the SPS, the
Flexi Multiradio BTS sends the SPS parameter via radio resource configuration (RRC) to
the UE and activates the SPS by the downlink control information (DCI). Analogically, the
SPS can be stopped either by an implicit or explicit release by the eNB.
Semi-persistent scheduling is applied only to EPS bearers with QCI = 1 (VoLTE call). A
dedicated setting for the QCI1 target BLER is needed for SPS, which is modified through
the Uplink SPS PUSCH BLER target (ulTargetBlerSps) parameter. The SPS
feature is enabled by setting the actUlSps feature flag to true.
The four-step SPS transmission in the uplink proceeds as follows:
1. SPS parameter configuration by RRC
The RRC signaling indicates the SPS configuration to the UE.
g Note: The time interval for the SPS in uplink must be set to 20 ms in the
LTE1929: UL Semi-persistent Scheduling feature.
2. SPS activation

LTE15A Radio Resource Management and Telecom LTE1929: UL Semi-persistent scheduling
Features
The SPS is activated via a PDCCH DCI message, which is also used to determine
the start point of SPS's time interval applying to a UE.
3. Data transmission in the uplink
A UE occupies the SPS resource at SPS reserved TTIs with a fixed modulation and
coding scheme (MCS), and a physical resource block (PRB) assigned by the DCI in
step 2.
4. PUSCH SPS resource release
The SPS resource reservation is valid until released:
• implicitly when the talkspurt ends
• explicitly via PDCCH signaling (it means that a UE clears PUSCH SPS resources
after receiving SPS release PDCCH DCI)
g Note: The number and location of allocated PRBs as well as MCS are fixed for multiple
TTIs via one PDCCH signal. However, they can be modified by another PDCCH signal
if needed, for example, when the RF condition changes.
For more information on a specific relationship between the LTE1929: UL Semi-

persistent Scheduling feature and the different technologies, see the detailed
descriptions in the remainder:
• LTE1929: SPS TBS selection based on AMR-WB or AMR-NB

• UL SPS link adaptation
• UL SPS interworking with handover
• UL SPS interworking with DRX
• UL SPS interworking with measurement gap
• UL SPS interworking with RRC re-establishment
• UL SPS interworking with TTI bundling
• UL SPS interworking with GBR congestion control
• UL SPS interworking with MU-MIMO
• UL SPS interworking with carrier aggregation (CA)
• UL SPS interworking with TM3/7 switch
• UL SPS interworking with extended VoLTE talk time
LTE1929: SPS TBS selection based on AMR-WB or AMR-NB

UL SPS supports both: the narrowband adaptive multi-rate speech codec (AMR-NB) and
wideband adaptive multi-rate speech codec (AMR-WB); the corresponding SPS
transport block size (TBS) is selected based on an AMR WB or NB top codec. An eNB
utilizes GBR requirements of the QCI1 bearer to determine AMR NB and AMR WB. The
SPS TBS is selected as a ulSpsVoicePktTbsNB or ulSpsVoicePktTbsWB
parameter, based on GBR requirement from S1 of the QCI1 EPS bearer.
UL SPS link adaptation (LA)

If the eNB determines the UL SPS's initial MCS and a proper initial MCS is selected, the
SPS is activated via a PDCCH DCI message. If no proper MCS can be selected, there is
no SPS activation attempt. If better RF conditions occur, and an actual MCS selection
succeed, the eNB triggers the SPS reactivation DCI to UE with the newly selected MCS.
In another case, the UE retains the previous MCS selection, and the SPS is not
reactivated. If the MCS downgrade criteria are met and an actual MCS selection
succeed, they cause the triggering of the SPS reactivation through the DCI to UE with

Features
the newly selected MCS. In the case when no lower MCS is available, the UL SPS is
explicitly released. Analogically, if the attempts of the SPS PRB allocation failed, the UL
SPS is also explicitly released.
g Note: The SPS LA follows a dedicated SPS LA MCS/PRB combination.
UL SPS interworking with handover

If a handover from one cell to another is triggered, the target cell should provide SPS
parameters to the source cell in a handover process (if the SPS criteria are met in the
target cell). The SPS parameters should be included in a handover command (mobility
control in RRC connection reconfiguration message).
The source cell releases SPS resources in the following cases:
• the UE's context is deleted because of a handover completion

• initiating the release of source eNB resources due to an abnormal handover
condition
• a UE is re-established to the target cell or another cell
If the target cell does not support UL SPS, the UL SPS is not activated after the
handover.
UL SPS interworking with DRX

An interworking SPS with a DRX is possible; the SPS can be activated in a DRX on
duration time and reactivated in a DRX active time.
UL SPS interworking with measurement gap

If an SPS activation attempt runs when a measurement gap is installed for a UE, the
eNB selects a correct TTI to activate the SPS. The TTI is correct if a UE is not in an
"OFF window" measurement gap in the current TTI and will not be in a measurement
gap window in any future SPS_Reserved_TTI.
If an SPS is already enabled and then the measurement gap is installed, the eNB
explicitly releases the UL SPS resources if a conflict between UL SPS reserved TTI and
the measurement gap window occurs. The UL SPS is activated again in a correct TTI so
that the subsequent SPS reserved TTIs are not in the measurement gap window.
UL SPS interworking with RRC re-establishment

If the UE RRC connection re-establishment request is accepted, the UE’s current bearer
combination meets UL SPS criteria, and the UE is not in a TTI bundling mode, then the
eNB configures the UL SPS parameter to this UE by sending an RRC connection
reconfiguration message. The eNB grants SPS resources when the RRC re-
establishment procedure is initiated. The eNB applies the newly configured UL SPS
parameters by RRC and reassigns new SPS resources for this UE, based on the UL UE
state machine.
UL SPS interworking with TTI bundling

A TTI bundling has a higher priority than the UL SPS for the same UE. The UL SPS
could be configured if the UE is not in a TTI bundling mode. The UL SPS resources are
released if the TTI bundling is triggered.

Features
UL SPS interworking with GBR congestion control

In case a GBR congestion is detected on PUSCH resource utilization, an eNB tries to
keep the guaranteed rates by prioritizing GBR DRBs in UL scheduling accordingly. The
de-prioritizing scheduling bearer does not include the QCI1 bearer of an SPS-activated
UE.
In case the GBR congestion is detected for PDCCH, the eNB releases a bearer or
bearers, which can help to solve the congestion. The released bearer does not include
the QCI1 bearer of an SPS-activated UE.
UL SPS interworking with MU-MIMO

The UL SPS and multi-user MIMO (MU-MIMO) features can be enabled together;
however, they cannot work simultaneously in the same UE. There is no possibility of an
SPS activation if a UE has previously been selected as a final paired UE. The same rule
is applied when a UE is in an SPS_Activated state; then, it cannot be paired with another
UE for the MU-MIMO activation.
UL SPS interworking with carrier aggregation (CA)

The UL semi-persistent scheduling is supported on the PCell only. The UL SPS is
explicitly released when a UE is in a transient period triggered by a release or addition of
an SCell. The UL SPS activation attempt is triggered again after the transient period.
UL SPS interworking with TM3/7 switch

When the LTE1929: UL Semi-persistent Scheduling feature is enabled, and a TM3/7
switching and the transient period are triggered, then the UL SPS configured grant is
explicitly released (by DCI 0) during the transient period. When the TM3/7 switching is
completed successfully, the UL SPS activation attempt should be triggered again.
UL SPS interworking with extended VoLTE talk time

If the SPS and eVTT are in conflict with each other at the UE level, the typically adopted
principle is "first configured, first used." There is no pre-emption or rollback functionality.
The SPS has a higher priority than the eVTT if both criteria are met at the same point
(both features are enabled, and the criteria to configure the SPS and eVTT are fullfilled).
System impact
The following features have to be enabled before the activation of the LTE1929: UL
Semi-persistent Scheduling feature:

• LTE11: Robust Header Compression
The following feature has to be disabled before the activation of the LTE1929: UL Semi-
persistent Scheduling feature:
The following features are affected by the LTE1929: UL Semi-persistent Scheduling

feature:

Features
• LTE42: DRX in RRC Connected Mode

• LTE46: Channel Aware Scheduler (UL)
• LTE619: Interference Aware UL Scheduling
• LTE496: Support of QCI 2, 3 and 4
• LTE587: Multiple GBR EPS Bearers per UE
• LTE9: Service Differentiation
• LTE53: Intra and Inter eNB Handover with X2
• LTE54: Intra-LTE Handover via S1
• LTE1617: RLF Triggered Handover
• LTE735: RRC Connection Re-establishment
• LTE815: Proactive UL Resource Assignment
• LTE1321: eRAB Modification - GBR
• LTE31: Link Adaptation By AMC (UL/DL)
• LTE1034: Extended Uplink Link Adaptation
• LTE1495:Fast Uplink Link Adaptation
• LTE907: TTI Bundling
• LTE1382: Cell Resource Groups
• LTE1113: eICIC - macro
• LTE1496: eICIC - micro
• LTE1545: UL MU-MIMO 8RX
• LTE1836: TDD Downlink Carrier Aggregation - 60Mhz
• LTE1013: Dynamic Transmission Mode Switch (with Enhanced Support for
TM3/TM8)

The feature is mainly targeted to improve the VoLTE capacity, thus improving the system
performance. In addition, the end-to-end latency is decreased due to shorter duration for
scheduling (the user has more opportunities for being scheduled). Consequently, the
quality of connections is improved.
g Note: The LTE1929: UL Semi-persistent Scheduling feature guarantees the capacity

for 16 users per TTI if turned on in a live field, while 20 users per TTI can be configured
for a trial or performance test.

Features

LTE1929: UL Semi-persistent scheduling requirements, alarms and faults, commands,
Requirements

FDD TDD
Alarms
There are no alarms related to the LTE1929: UL Semi-persistent scheduling feature.

There are no faults related to the LTE1929: UL Semi-persistent scheduling feature.
Commands
There are no commands related to the LTE1929: UL Semi-persistent scheduling feature.

M8001C500 First HARQ transmission on LTE Cell Load
PUSCH for SPS
M8001C501 First HARQ transmission LTE Cell Load
NACK on PUSCH for SPS
M8011C108 Number of UL SPS activation LTE Cell Resource
attempts

Features

M8011C109 Number of successful UL SPS LTE Cell Resource
activation attempts
M8011C110 UL SPS utilization LTE Cell Resource
M8011C111 Total number of PRBs LTE Cell Resource
allocated by UL SPS
M8011C163 Number of TTIs used by UL LTE Cell Resource
SPS allocated resources


There are no key performance indicators related to the LTE1929: UL Semi-persistent
scheduling feature.
Parameters

Full name Abbreviated Managed object Parent Structure FDD/TDD
name
Activate UL SPS actUlSps LNCEL_FDD - FDD
Activate UL SPS actUlSps LNCEL_TDD - TDD
SPS ulSpsConfig LNCEL_FDD - FDD
configuration
SPS ulSpsConfig LNCEL_TDD - TDD
configuration
AMR WB/NB amrVoiceBRThre LNCEL ulSpsConfig TDD
voice bitrate shold
threshold
Maximum maxNumSpsUeUl LNCEL ulSpsConfig TDD
number of SPS
scheduled UEs
for UL scheduler
Nominal power p0NomPuschSps LNCEL ulSpsConfig TDD
for SPS UE
PUSCH TX
power calculation
UL SPS interval ulSpsInterval LNCEL ulSpsConfig TDD
Uplink SPS ulSpsMaxNumPr LNCEL ulSpsConfig TDD
maximum b
number PRB
Uplink SPS max ulSpsMaxPrbPer LNCEL ulSpsConfig TDD
PRB per UE for UeNB
AMR NB

Features

Full name Abbreviated Managed object Parent Structure FDD/TDD
name
Uplink SPS max ulSpsMaxPrbPer LNCEL ulSpsConfig TDD
PRB per UE for UeWB
AMR WB
Uplink SPS ulSpsMinVoicePkt LNCEL ulSpsConfig TDD
minimum voice Size
packet size
UL SPS number ulSpsNumEmpty LNCEL ulSpsConfig TDD
of empty Transmissions
transmissions
UL SPS two- ulSpsTwoInterval LNCEL ulSpsConfig TDD
intervals SPS Config
configuration
Uplink SPS ulSpsVoicePktTb LNCEL ulSpsConfig TDD
allocation sNB
transport block
size for AMR NB
Uplink SPS ulSpsVoicePktTb LNCEL ulSpsConfig TDD
allocation sWB
transport block
size for AMR WB
Uplink SPS ulTargetBlerSps LNCEL ulSpsConfig TDD
PUSCH BLER
target

name object Structure
Method for UL power actUlpcMethod LNCEL - Common
control
Maximum amount of maxNumUeUl LNCEL_FDD - FDD
users per TTI in UL
Maximum amount of maxNumUeUl LNCEL_TDD - TDD
users per TTI in UL
Nominal power for UE p0NomPusch LNCEL - Common
PUSCH TX power
calculation
Interference aware UL- ulpcIAwConfig LNCEL - Common
PC configuration
Nominal PUSCH P0 for p0NomPuschIA LNCEL ulpcIAwConfig Common
interference-aware UL- w
PC
PRACH high speed flag prachHsFlag LNCEL - Common
DRX on duration timer drxOnDuratT LNCEL - Common
TTI bundling BLER ttiBundlingBlerT LNCEL - Common
threshold hreshold

Features

Sales information

element
ASW Pool license No
22.3 Activating and configuring LTE1929: UL Semi-

persistent Scheduling
Before you start
The Activate UL SPS (ActUlSps) parameter activates the LTE1929: UL Semi-
persistent Scheduling feature. Modification of this parameter requires object locking.
persistent Scheduling
object locking
Activate UL SPS (ActUlSps) activation flag object locking
SPS configuration (ulSpsConfig) mandatory configuration no
AMR WB/NB voice bitrate optional configuration no
threshold (amrVoiceBRThreshold)
Maximum number of SPS optional configuration no
scheduled UEs for UL scheduler
(maxNumSpsUeUl)
Nominal power for SPS UE mandatory configuration no
PUSCH TX power calculation
(p0NomPuschSps)
Uplink SPS maximum number optional configuration no
PRB (ulSpsMaxNumPrb)
Uplink SPS max PRB per UE for optional configuration no
AMR NB (ulSpsMaxPrbPerUeNB)
Uplink SPS max PRB per UE for optional configuration no
AMR WB (ulSpsMaxPrbPerUeWB)
Uplink SPS minimum voice packet optional configuration no
size (ulSpsMinVoicePktSize)
UL SPS number of empty optional configuration no
transmissions
(ulSpsNumEmptyTransmissions)
Uplink SPS allocation transport optional configuration no
block size for AMR NB
(ulSpsVoicePktTbsNB)

Features
persistent Scheduling (Cont.)
object locking
Uplink SPS allocation transport optional configuration no
block size for AMR WB
(ulSpsVoicePktTbsWB)
Uplink SPS PUSCH BLER target optional configuration no
(ulTargetBlerSps)
The following features need to be activated before the activation of the LTE1929: UL

• LTE11: Robust Header Compression
• The LNBTS_TDD parameter: Activate support of conversational
voice bearer (actConvVoice) and LNBTS parameter: Activate PDCP
robust header compression (actPdcpRohc) must be set to true.
The following features need to be deactivated before the activation of the LTE1929: UL
Procedure

2 Activate the feature.

d) Select the LNCEL object corresponding to the cell where the LTE1929: UL Semi-
persistent Scheduling feature is being activated.

e) Set the Activate UL SPS (actUlSps) parameter's value to true.

Features
3 Configure UL SPS parameters.

d) Right-click on the LNCEL object corresponding to the cell where the LTE1929:
UL Semi-persistent Scheduling feature is being activated.

e) Select New SPS configuration.
f) Set the parameters' values of the SPS configuration object.
g Note: Only the setup of the

Nominal power for SPS UE PUSCH TX power
calculation (p0NomPuschSps) parameter in the SPS configuration object
is mandatory. The parameter's value must be consistent with the related
Nominal power for UE PUSCH TX power
calculation (p0NomPusch) parameter in the managed LNCEL object.
Expected outcome
The LTE1929: UL Semi-persistent Scheduling feature is activated.
22.4 Deactivating LTE1929: UL Semi-persistent

Scheduling
Before you start
The Activate UL SPS (ActUlSps) parameter deactivates the LTE1929: UL Semi-
persistent Scheduling feature. Modification of this parameter requires object locking.
Procedure


Features

d) Select the LNCEL object corresponding to the cell where the LTE1929: UL Semi-
persistent Scheduling feature is being deactivated.

e) Set the Activate UL SPS (actUlSps) parameter's value to false.
Expected outcome
The LTE1929: UL Semi-persistent Scheduling feature is deactivated.

LTE1942: Dedicated VoLTE Inter-frequency Target LTE15A Radio Resource Management and Telecom
Frequency List Features
23 LTE1942: Dedicated VoLTE Inter-frequency

Target Frequency List
23.1 Description of LTE1942: Dedicated VoLTE Inter-

frequency Target Frequency List
The LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List feature
introduces a mechanism for controlling which target layers are used for inter-frequency
handovers during ongoing Voice Over LTE (VoLTE) calls.
Benefits
End-user benefits
No effect on the end-user experience.
Operator benefits
Feature benefits:
• possibility to control the LTE frequency layers used by VoLTE
• the operator can configure a specific list of allowed VoLTE target frequency layers
within mobility profiles
• better resource management
Requirements
Concept of frequency layers in the LTE1942 feature
The LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List feature
introduces a mechanism to control which target layers are used for inter-frequency
handovers (HO) during ongoing VoLTE (Voice Over LTE) calls. When the LTE1942
feature is enabled, the eNB uses a specific dedicated target list of frequencies for all
types of inter-frequency handovers (including coverage, load, and service-based HOs),
both inter- and intra-eNB.
g Note: All eNBs within the same network should be configured with the same list of
frequencies allowed for VoLTE handovers.
Examples of how the frequency layers can be defined, and how it influences the
handovers are shown in Figure 15: Example of frequency layers in the LTE1942 feature.

LTE15A Radio Resource Management and Telecom LTE1942: Dedicated VoLTE Inter-frequency Target
Features Frequency List
Figure 15 Example of frequency layers in the LTE1942 feature
Inter-frequencyVoLTEhandoverscenario:
IFHOnotallowed IFHOallowedto IFHOallowedto
(nofrequency cellsonf1,f2,f3 cellsonf1freq.
layersconfigured) frequencylayers layeronly
neighboringfreq.
f3 f3 f3 layernotallowed
forIFVoLTEHO
f2 f2 f2 neighboringfreq.
layerconfigured
f1 f1 f1 inLTE1942list
serving
f0 f0 f0 frequency
The LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List feature is co-
related with the LTE1127: Service-based Mobility Trigger feature. If LTE1127 is activated,
there is a consistency check between the LTE1127 and LTE1942 features' target layer
lists. All LTE1127 target frequencies must be included within the LTE1942 feature's target
layer list. An exemplary scenario of VoLTE inter-frequency handovers when both
LTE1127 and LTE1942 are active is shown in Figure 16: Example of frequency layers in
the LTE1942 feature when LTE1127 is active.
Figure 16 Example of frequency layers in the LTE1942 feature when LTE1127 is

active
Inter-frequencyVoLTEhandoverscenario:
LTE1127
empty empty f1
frequencylist:
LTE1942
empty f1 f1 f2
frequencylist:
VoLTEHOnotallowed VoLTEHOallowed VoLTEHOallowedonly

inallconfiguredlayers onlytof1(VoLTEcalls tof1andf2(VoLTEcalls
(VoLTEcallsarenot onf2,f3,f4arenotshifted onf2,f3,f4areshifted
shiftedwithSBHO) tof1withSBHO) tof1withSBHO)
f4 f4 f4
f3 f3 f3
f2 f21 f21
f1 f1 f1
neighboringfreq.layer freq.inLTE1942
freq.inLTE1942list
notallowedforIFVoLTEHO andLTE1127list

Target frequencies list in the LTE1942 feature

The LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List enters a new list
inside mobility profiles (MOPR) and mobility default profile (MODPR) objects to configure
a dedicated VoLTE inter-frequency target list. This list is used during inter-frequency
handovers for UEs with an established QCI1 bearer (after establishment of bearer with
QCI1 and in case when QCI1 is already established with Initial Context Setup) or UEs
with established QCI1 entering cell via handover or RRC connection re-establishment.
Configuration of the list is performed by the operator using Frequency layer list
for ded. VoLTE inter-frequency HO parameter. Only target frequencies
layers configured in the LTE1942 list are taken into account before an HO by eNB for:
• measurement configuration
• measurement reports filtering
During a target cell selection, the eNB prevents the UE with an established QCI1 bearer
from being handed over to a target cell which is not located on a dedicated VoLTE target
frequency layer.
g Note: At least the default mobility profile (MODPR) has to be created with the LTE1942
list to make inter-frequency VoLTE handovers possible.
System impact
The following features need to be activated before the activation of the LTE1942:
Dedicated VoLTE Inter-frequency Target Frequency List feature:
• LTE10: EPS bearers for conversational voice
• LTE55: Inter-frequency handover
Features that are affecting the LTE1942: Dedicated VoLTE Inter-frequency Target
Frequency List feature:
• LTE1060: TDD - FDD handover - necessary if FDD/TDD handover is needed
• LTE1127: Service Based Mobility Trigger - when LTE1127 is activated; the content of
the LTE1127 frequency layer list for service-based mobility must be added to the
VoLTE target frequency layer list (LTE1942)
• LTE490: Subscriber profile based mobility
– If LTE490 is deactivated and the Auto adaptation to freq. layers of
all neighbour cells (autoAdapt) is configured with the value 'true,'
the VoLTE inter-frequency handover is not allowed.
– If LTE490 is activated and the UE cannot be mapped to a mobility profile where
the Auto adaptation to freq. layers of all neighbour cells
(autoAdapt) is configured with value 'true,' the VoLTE inter-frequency
handover is not allowed. Otherwise, the configuration in the mobility profile will be
used.
• LTE1170: Inter-frequency load balancing:

The LTE1170/LTE1531/LTE1387 feature bundle provide load balancing for inter-
frequency targets and the LTE1841 feature provides load equalization using LB HO.
They can be activated in parallel with LTE1942, however if QCI1 is established only

target frequencies from LTE1942 shall be used. If LTE1942 is enabled and QCI1 is
established, then list of allowed targets for inter-frequency handover is reduced to
dedicated target list for VoLTE.
Management data
Sales information

Requirements

FDD TDD
NetAct 15.5 15.5
Alarms
There are no alarms related to the LTE1942: Dedicated VoLTE Inter-frequency Target
Frequency List feature.

There are no faults related to the LTE1942: Dedicated VoLTE Inter-frequency Target
Frequency List feature.
Commands
There are no commands related to the LTE1942: Dedicated VoLTE Inter-frequency
Target Frequency List feature.

There are no measurements or counters related to the LTE1942: Dedicated VoLTE Inter-
frequency Target Frequency List feature.

There are no key performance indicators related to the LTE1942: Dedicated VoLTE Inter-
frequency Target Frequency List feature.
Parameters

name object
Activate dedicated actDedVoLteIn LNBTS - common
VoLTE inter- terFreqHo _FDD
frequency handover
Frequency layer freqLayListDe MODPR - common
list for ded. dVoLteHo
VoLTE inter-
frequency HO
Frequency layer freqLayListDe MOPR - common
list for ded. dVoLteHo
VoLTE inter-
frequency HO

name object
Auto adaptation to autoAdapt MODPR - common
freq. layers of
all neighbour
cells
Sales information

Application software (ASW) SW Asset Monitoring No

23.3 Activating and configuring LTE1942: Dedicated

VoLTE Inter-Frequency Target Frequency List
Before you start
Table below lists parameters used during activation and configuration of the feature.
Table 133 Parameters used for activating and configuring the LTE1942: Dedicated
VoLTE Inter-Frequency Target Frequency List
object locking
Activate dedicated VoLTE inter- activation flag no
frequency handover
(actDedVoLteInterFreqHo)
Frequency layer list for ded. VoLTE optional configuration no
inter-frequency HO
(freqLayListDedVoLteHo)
The following features need to be activated before the activation of the LTE1942:
Dedicated VoLTE Inter-frequency Target Frequency List feature:
• LTE10: EPS bearers for conversational voice (Activate support of
conversational voice bearer (actConvVoice)) which requires LTE7:
Support of multiple EPS bearer (Activate Multiple bearers
(ActMultBearers))
• LTE55: Inter-frequency handover (Enable InterFrequency Handover
(actIfHo) )
Additionally, The MODPR Auto adaptation to freq. layers of all

neighbour cells (autoAdapt) parameter must be set to 'false' otherwise inter-
frequency handovers will not start.
Procedure

2 Activate the feature flag for the LTE1942 feature.



d) Set the Activate dedicated VoLTE inter-frequency handover
(actDedVoLteInterFreqHo) parameter value to true.
3 Optional: Configure the frequency layers.

b) If not existing. right click LNBTS object, and then create and configure MOPR
and/or MODPR instance.
c) If not existing. right click MOPR and/or MODPRobject,and then create and
configure the Frequency layer list for ded. VoLTE inter-
frequency HO (freqLayListDedVoLteHo).
g Note: If LTE1127 is enabled , then the MOPR/MODPR Frequency layer

list for ded. VoLTE inter-frequency HO
(freqLayListDedVoLteHo) list must contain frequencies of corresponding
MOPR/MODPR Frequency layer list for VoLTE service based
HO (freqLayListServiceBasedHo) .
Expected outcome
The eNB provides support for dedicated VoLTE inter-frequency target lists.
23.4 Deactivating LTE1942: Dedicated VoLTE Inter-

Frequency Target Frequency List
Before you start
The Activate dedicated VoLTE inter-frequency handover
(actDedVoLteInterFreqHo) parameter is used for deactivation. Modification of this
parameter does not require either an eNB restart or cell locking.

Procedure

2 Deactivate the feature flag for the LTE1942 feature.


d) Set the Activate dedicated VoLTE inter-frequency handover
(actDedVoLteInterFreqHo) parameter value to false.
Expected outcome
The eNB stops supporting dedicated VoLTE inter-frequency target lists.

LTE1944: Dynamic Handover Blacklisting LTE15A Radio Resource Management and Telecom
Features
24 LTE1944: Dynamic Handover Blacklisting
24.1 Description of LTE1944: Dynamic Handover

Blacklisting
With the LTE1944: Dynamic Handover Blacklisting feature, if the success of a handover
(HO) preparation is considered unlikely, the HO is temporarily blacklisted.
Benefits
End-user benefits
Operator benefits
Unnecessary handover preparation retrials are reduced as a result of blacklisting
selected handovers.
Requirements
Dynamic blacklisting is applied to every type of intra-LTE inter-eNB handover, except for
emergency services.
Target cells are temporarily blacklisted for a handover in one of the following cases:
• The handover preparation supervision timer (TX2RELOCPrep for an X2 handover or
TS1RELOCPrep for an S1 handover) expires after several consecutive handover
preparation attempts. The number of HO preparation attempts is operator-
configurable.
• The handover preparation is rejected by the target eNB with one of the following
cause values:
– Radio Network Layer Cause (Cell not Available)
– Miscellaneous Cause (Control Processing Overload)
– Miscellaneous Cause (Not enough User Plane Processing Resources)
Handover Preparation
For a handover preparation, the source eNB sends a message to the target eNB (X2AP:
Handover Request) or to the target MME (S1AP: Handover Required) and starts the
supervision timer for the HO preparation. If the timer (TX2RELOCPrep or
TS1RELOCPrep) expires and the target cell does not respond, the source eNB
increments an internal target cell-specific counter for HO preparation timeouts. If no HO
preparation has timed out before, the counter is initialized with 1. The operator can
configure the counter. If the counter reaches the threshold:

LTE15A Radio Resource Management and Telecom LTE1944: Dynamic Handover Blacklisting
Features
• The source eNB starts the timer for dynamic blacklisting of the target cell.
• The source eNB resets the internal target cell-specific counter for HO preparation
timeouts to 0.
As a result, one of the scenarios might take place:

• The source eNB suspects the target cell to be a sleeping cell and starts counting the
HO preparation timeouts.
• The source eNB considers the target cell to be a sleeping cell. The target cell is
blacklisted for an HO (except an emergency service) as long as the dynamic
blacklisting timer is running. The Number of dynamic handover
blacklisting occurrences counter is incremented.
If the target eNB responds to the HO preparation request by X2AP: Handover Request
Acknowledge, X2AP: Handover Preparation Failure, S1AP: Handover Command or
S1AP: Handover Preparation Failure, the source eNB resets the internal target cell-
specific counter for HO preparation timeouts to 0. The target cell is not suspected to be a
sleeping cell.
The target eNB can reject an HO preparation. Then the source eNB starts the timer for
dynamic blacklisting of the target cell. The target cell is blacklisted for an HO (except an
emergency service) as long as the dynamic blacklisting timer is running. The Number
of dynamic handover blacklisting occurrences counter is incremented.
When the dynamic blacklisting timer for the target cell is running, the source eNB
eliminates this cell from the target cell list. The eNB does not trigger a handover
preparation towards the dynamically-blacklisted target cell.
Cause values
For blacklisting of barred cells or cells with a control plane (C-plane) or user plane (U-
plane) overload, the source eNB relies on the cause values within the Handover
Preparation Failure message.
For an X2 handover:
• The Nokia target eNB sets the cause values correctly.
• A foreign vendor's target eNB behavior is unknown.
For an S1 handover:
• In a pure Nokia environment, for an intra-MME handover, cause values are
propagated correctly from the target eNB via the MME to the source MME.
• If any of the MMEs or the target eNB is from a foreign vendor, the end-to-end
behavior is unknown.
System impact
• LTE53: Intra and Inter eNB Handover with X2

Dynamic blacklisting according to the LTE1944: Dynamic Handover Blacklisting
feature is applied when target cells for an X2-handover according to LTE53: Intra and
Inter eNB Handover with X2 feature are selected.
• LTE54: Intra-LTE Handover via S1

Features

feature is applied when target cells for an S1-handover according to the LTE54: Intra-
LTE Handover via S1 feature are selected.
feature is applied when inter-frequency target cells according to the LTE55: Inter-
frequency Handover feature are selected.
• LTE1047: Control Plane Overload Handling
With the LTE1944: Dynamic Handover Blacklisting feature, reception of a handover
preparation failure with a "Miscellaneous Cause (Control Processing Overload)"
cause value is a trigger condition for dynamic blacklisting. This is the only situation
where a Nokia target eNB uses this cause value. It is not known whether a foreign
vendor's target eNB uses the "Miscellaneous Cause (Control Processing Overload)"
cause value.
• LTE1127: Service Based Mobility Trigger
feature is applied to service-based handovers according to the LTE1127: Service
Based Mobility Trigger feature.
• LTE1170: Inter eNB IF Load Balancing, LTE1531: Inter-frequency Load Balancing
Extension, LTE1841: Inter-Frequency Load Equalization
feature is applied to load-based handovers.
• LTE1617: RLF Triggered Handover
If an RLF-triggered handover preparation is rejected due to a barred target cell, C-
Plane overload, or U-Plane overload, the target cell is blacklisted according to the
LTE1944: Dynamic Handover Blacklisting feature.
• LTE2023: User Plane Overload Handling
With the LTE1944: Dynamic Handover Blacklisting feature, reception of a handover
preparation failure with a "Miscellaneous Cause (Not enough User Plane Processing
Resources)" cause value is a trigger condition for dynamic blacklisting. This is the
only situation where a Nokia target eNB uses this cause value. It is not known
whether a foreign vendor's target eNB uses the "Miscellaneous Cause (Not enough
User Plane Processing Resources)" cause value.
• LTE2108: Redirected VoLTE Call Setup
feature is applied to forced service-based handovers according to the LTE2108:
Redirected VoLTE Call Setup feature.


Management data
Sales information

Features

Requirements

FDD TDD
NetAct Support not required Support not required
Alarms
There are no alarms related to the LTE1944: Dynamic Handover Blacklisting feature.

There are no faults related to the LTE1944: Dynamic Handover Blacklisting feature.
Commands
There are no commands related to the LTE1944: Dynamic Handover Blacklisting feature.

ID
M8014C Number of dynamic handover 8014 - LTE Inter eNB Handover (WBTS)
21 blacklisting occurrences

Reference/Counters.

There are no key performance indicators related to the LTE1944: Dynamic Handover
Blacklisting feature.

Features
Parameters

d object
Activate temporary actTempHoBlack LNBTS - common
handover listing
blacklisting
Duration for dynBlacklistin LNBTS - common
dynamic gHoTimer
blacklisting
Duration for nConsecHOPrepT LNBTS - common
dynamic imeouts
blacklisting

Documentation/Reference/Parameters
Sales information

Basic Software (BSW) - No
24.3 Activating and configuring LTE1944: Dynamic

Handover Blacklisting
Before you start
Table 1 lists Parameters used for activating and configuring LTE1944
Table 138 Parameters used for activating and configuring LTE1944: Dynamic
Handover Blacklisting
object locking
Activate temporary handover activation flag no
blacklisting
(actTempHoBlacklisting)
Duration for dynamic blacklisting mandatory configuration no
(dynBlacklistingHoTimer)
Number of consecutive HO mandatory configuration no
preparation timeouts
(nConsecHOPrepTimeouts)

Features
Procedure

2 Activate the LTE1944: Dynamic Handover Blacklisting feature.

d) Set the Activate temporary handover
blacklisting (actTempHoBlacklisting ) parameter's value to true.
3 Configure the LTE1944: Dynamic Handover Blacklisting feature.

b) Set the Number of consecutive HO preparation
timeouts (nConsecHOPrepTimeouts) and the Duration for dynamic
blacklisting (dynBlacklistingHoTimer) parameters' values.
Expected outcome
The LTE1944: Dynamic Handover Blacklisting feature is activated. The eNB applies
dynamic blacklisting.
24.4 Deactivating LTE1944: Dynamic Handover

Blacklisting
Before you start
The Activate temporary handover
blacklisting (actTempHoBlacklisting) parameter is used for deactivation.
Modification of this parameter requires neither eNB restart nor cell locking.

Features
Procedure

2 Deactivate the LTE1944: Dynamic Handover Blacklisting feature.

d) Set the Activate temporary handover
blacklisting (actTempHoBlacklisting ) parameter's value to false.
Expected outcome
The LTE1944: Dynamic Handover Blacklisting feature is deactivated. The eNB stops
applying dynamic blacklisting.

LTE15A Radio Resource Management and Telecom LTE2006: Flexible SCell Selection
Features
25 LTE2006: Flexible SCell Selection

The LTE2006: Flexible SCell Selection feature optimizes the UE throughput as well as
the SCell resource utilization, changing the current SCell to another one with a better
radio quality, which is detected by the UE.
25.1 LTE2006 benefits

The LTE2006: Flexible SCell Selection feature provides the following benefits:
End-user benefits
This feature optimizes the UE throughput as well as the SCell resource utilization,
changing the current SCell to another suitable one with a better radio quality, which is
detected by the UE. This way, the UE will be always served by the best possible SCells,
without interrupting the carrier aggregation (CA) functionality, which results in faster data
transfer.
Operator requirements
This feature enables a flexible assignment of serving cells in downlink carrier
aggregation. The LTE2006: Flexible SCell Selection feature also allows CA in such
deployment scenarios where a PCell and a candidate SCell do not fully overlap, and
more than one candidate SCell per PCell exists. This refers to scenario #3 from 3GPP
TS 36.300.
25.2 LTE2006 functional description

Functional overview
The Flexi Multiradio BTS supports a flexible SCell selection for downlink carrier
aggregation for up to three aggregated cells per UE. Up to two carrier frequencies and
up to five SCell candidates can be configured per PCell. The candidate SCells with the
same carrier frequency shall also have the same frequency bandwidth. The C-RNTI
code space is equally partitioned among the eNB cells belonging to the same C-RNTI
group and having the same caPoolID.
The configuration of the Carrier aggregation pool ID (caPoolID) has the
following constraints:
• a maximum of thirteen eNB cells can have the same Carrier aggregation
pool ID (caPoolID)
• PCell and all its candidate SCells must have the same Carrier aggregation
pool ID (caPoolID)
The concept of C-RNTI group has been defined to avoid a C-RNTI collision between the
PCell and its candidate SCells. The drawback is that it proportionally reduces the CRNTI
code space available per cell with the number of cells belonging to the same CRNTI
group. SCells are added blindly, according to the respective SCell priority
(SCellPrio); from the UE candidate SCells with the same carrier frequency, the one
having the highest priority (that is, having assigned the lowest value to the
“SCellPrio” parameter in the respective CAREL object) is selected. Together with
the blind SCell configuration, an eNodeB activates a measurement event for UEs with

LTE2006: Flexible SCell Selection LTE15A Radio Resource Management and Telecom
Features
according capabilities in order to find a better intra-frequency SCell. The A6

measurement is operator-configurable per carrier frequency according to the respective
carrier aggregation (default) profile CA(D)PR. Upon receiving an A6 measurement
report, the eNodeB checks whether the reported cell is an SCell candidate for carrier
aggregation, and whether it has sufficient resources to serve as an SCell. SCell
candidates for the flexible SCell functionality are pre-configured cells of the same
eNodeB with a different center frequency as the PCell. They are modeled with CAREL
objects. After the above-mentioned checks have been passed, the new SCell is
configured (replaces the current SCell). All the SCell-related timers and counters are
reset with the SCell change. The SCell change does not trigger a PCell change.
The functionality is enabled/disabled via O&M settings per eNodeB.
25.3 LTE2006 system impact

At least one of the following CA features must be activated/configured before the
activation of the LTE2006: Flexible SCell Selection feature:
• LTE1830: TDD Downlink Carrier Aggregation enhancement
• LTE1836: TDD Downlink Carrier Aggregation - 60 MHz
• LTE1838: TDD Downlink Inter-band Carrier Aggregation - 40 MHz
The LTE1382: Cell Resource Groups feature and the LTE2006: Flexible SCell Selection
feature exclude each other.
The LTE2006: Flexible SCell Selection feature has no impact on interfaces.

With the LTE2006: Flexible SCell Selection feature activated, the iSON manager
supports carrier aggregation for a PCell up to a maximum of five candidate secondary
cells. Each primary cell can have a maximum of five SCells at a given frequency layer.

For some UEs and chip-sets, every SCell configuration/de-configuration and SCell
activation/deactivation, as well as every measurement pertaining to the configured
SCells, might be accompanied by a PDSCH and PUSCH micro interruption on a PCell.
However, since frequent re-configuration should be avoided with appropriate parameter
settings, the throughput impairments should be negligible.

Requirements

Features

FDD TDD
System release FDD-LTE15A TD-LTE 16
Flexi Multiradio 10 BTS FL15A TL16
Flexi Multiradio 10 Indoor BTS not supported TL16
Nokia AirScale BTS FL16 TL16A
Flexi Zone BTS not supported not supported
Flexi Zone Access Point not supported not supported
Flexi Zone Controller not supported not supported
NetAct 15.5 15.5
UE 3GPP R10, 3GPP R11 3GPP R10, 3GPP R11
Alarms
There are no alarms related to the LTE2006: Flexible SCell Selection feature.

There are no faults related to the LTE2006: Flexible SCell Selection feature.

M8011C165 Number of Event A6 triggered 8011 - LTE Cell Resource
SCell swaps (WBTS)

Reference/Counters.

There are no key performance indicators related to the LTE2006: Flexible SCell
Selection feature.
Parameters

name object
Activate flexible actFlexSCellS LNBTS - common
SCell selection elect

Features

name object
A6 offset a6Offset CADPR/CA - common
PR
A6 report interval a6ReportInter CADPR/CA - common
val PR
A6 time to trigger a6TimeToTrigg CADPR/CA - common
er PR
Carrier caDPrId CADPR/CA - common
aggregation PR
default profile
identifier
Disable PDCCH disableSCellP CADPR/CA - common
outer loop link DCCHOl La PR
adaptation in
SCell
Enable enableA6Event CADPR/CA - common
measurements for PR
A6 event
Related hysteresis hysA6Offset CADPR/CA - common
of offset a6Offset PR
neighbor cell
Downlink EARFCN of earfcnDL CAPR - common
the SCell
frequency layer
Enable enableA6Event CAPR - common
measurements for
A6 event
Related hysteresis hysA6Offset CAPR - common
of offset a6Offset
neighbor cell
SCell priority scellPrio CAREL - common
Measurement cycle SCellMeasCycl LNBTS - common
on configured e
SCells
Carrier caPoolId LNCEL - common
aggregation pool
ID

name object
Carrier caRelId CAREL - common
aggregation
relation
identifier
Scheduling CA caSchedFairFa LNBTS - common
fairness control ct
factor

Features

name object
ACK/NACK offset n1PucchAn LNCEL - common
Max number of maxNumScells LNCEL - common
secondary cells
for DL carrier
aggr
Max number carrier maxNumCaConfU LNCEL_FD - common
aggr configured e3c D for FDD
UEs 3 Carriers and
LNCEL_TD
D for TDD
Sales information

25.5 Activating and configuring LTE2006

Before you start
At least two CAREL objects pointing to SCell candidates on the same frequency have to
be configured.
One of the following carrier aggregation features has to be enabled:

Procedure notifications
– Activation procedure does not cause downtime, and the feature can be activated
at any time of the day.
Procedure
1 Start the BTS Site Manager application and establish the connection to the BTS.

Features
Sub-steps
a) Select View ► Commissioning or click Commissioning on the View Bar on the

left.
The BTS Site checkbox, located in the Target section, is selected by default.
This is the recommended setting.
b) Use the Template, Manual, or Reconfiguration option, depending on the actual

state of the BTS.
3 If it does not exist, create a CADPR object in LNBTS
Sub-steps
c) Select the LNBTS object and add a new CADPR object.
4 Configure the Scheduling CA fairness control factor

(caSchedFairFact) parameter.
Sub-steps
d) Set the Scheduling CA fairness control factor

(caSchedFairFact) parameter to the desired value.
5 Configure the Activate flexible Scell selection of downlink

carrier aggregation (actFlexScellSelect) parameter.
Sub-steps

Features
d) Set the Activate flexible Scell selection of downlink

carrier aggregation (actFlexScellSelect) parameter value to
true.
6 Configure the CA Pool ID (caPoolId) parameter.
Sub-steps
e) Set the CA Pool ID (caPoolId) parameter of the PCELL and the possible
SCells to the same value. Remember that max. 13 cells can have the same CA
Pool ID.
7 Create CAREL objects for all possible SCell candidates.
Sub-steps
d) Select the LNCEL object and create CAREL objects.
e) Repeat this step for all LNCEL objects.
8 Send the commissioning plan file to the BTS.
Sub-steps
a) Go to the Send Parameters page.

Features
b) Select an appropriate Send option.
• If the BTS has not been commissioned, select All parameters.

• If the BTS has been already commissioned, select Only changes.
c) Click Send Parameters.
Result
The LTE2006: Flexible SCell Selection feature is configured and activated.
25.6 Deactivating LTE2006

Before you start
The Activate flexible SCell selection (actFlexSCellSelect)
parameter is used for deactivation. Modification of this parameter does not require eNB
restart.
Procedure
1 Start the BTS Site Manager application and establish the connection to the BTS.
Sub-steps
a) Select View ► Commissioning or click Commissioning on the View Bar on the

left.
The BTS Site checkbox, located in the Target section, is selected by default.
This is the recommended setting.
b) Use the Template, Manual, or Reconfiguration option, depending on the actual

state of the BTS.
3 Proceed to the Radio Network Configuration page.
4 Go to the LNBTS object.
Object path: MRBTS ► LNBTS

Features
5 Set the Activate flexible SCell selection (actFlexSCellSelect)

value to false.
6 Ensure that a maximum of 3 LNCEL objects have the same Carrier aggregation
pool ID (caPoolId).
7 Remove all the CAREL objects pointing to a LNCEL with another Carrier
aggregation pool ID (caPoolId).
8 Send the commissioning plan file to the BTS.
Sub-steps
a) Go to the Send Parameters page.
b) Select an appropriate Send option.
• If the BTS has not been commissioned, select All parameters.

• If the BTS has been already commissioned, select Only changes.
c) Click Send Parameters.
Result
The LTE2006: Flexible SCell Selection feature is deactivated.

LTE2023: User plane overload handling LTE15A Radio Resource Management and Telecom
Features
26 LTE2023: User plane overload handling
26.1 Description of LTE2023: User Plane Overload

Handling
The LTE2023: User Plane Overload Handling feature provides a user plane (U-plane)
overload monitoring and handling mechanism for the eNB.
Benefits
End-user benefits
This feature enables an on-going service optimization even in high load or overload
situations.
Operator benefits
This feature:
• guarantees a stable operation of the eNB's high U-plane load, and thus ensures a
high U-plane throughput in case of a heavy load
• issues a warning message via NetAct or the Network Element Manager when the
eNB is overloaded
• helps with network planning
Functional overview
The LTE2023: User Plane Overload Handling feature is one of a series of features
designed to handle overload situations within the eNB. Its aim is to avoid unstable
operation of the eNB due to a high U-plane load. The LTE2023: User Plane Overload
Handling feature intends to handle as much U-plane traffic or load as possible. It is
obtained by:
• avoiding allocation of additional traffic
• implementing a separate U-plane overload state machine
• using the existing overload counter-measures
• adding the additional counter-measures
The high U-plane load, or a U-plane overload, is expected in various situations in which
there is a permanent or temporary increase in traffic and users. If the overload cases
happen too often, it is advisabe to examine both the traffic and the traffic profile in a more
detailed way. The LTE2023: User Plane Overload Handling feature enables issuing
warnings about an overload via NetAct or the Network Element Manager (see Figure 17:
U-plane overload handling). Those alarms are generated by the eNB when a U-plane
overload state transition varies from U-plane overload level 0 (UPOVL0) to U-plane
overload level 1/2 (UPOVL1/2). The alarm is cleared in case of overload state transition
varies from UPOVL1 to UPOVL0. The alarms include the start or end time and the type
of overload. To avoid spamming, they are generated only in the case a U-plane overload
condition lasts longer than one minute. In addition, if the U-plane overload counter-

LTE15A Radio Resource Management and Telecom LTE2023: User plane overload handling
Features
measures are enabled, the eNB handles as much U-plane traffic as possible, even if the
traffic demand is above its specification and keeps itself within a stable operating
condition.
Figure 17 U-plane overload handling

NetAct
U-plane overload
overloadinformation warningmessage
eNB Client
BTSSM
U-plane overload management
The U-plane overload is detected by evaluating a certain overload level metrics. There
are the following overload levels for the U-plane overload:
• overload level 0 (normal operation – when the U-plane overload level is zero)
• overload level 1 (graceful overload handling – the goal of these counter-measures is
to avoid a further U-plane traffic increase and to reduce the U-plane load)
• overload level 2 (preserving stability, self-defense U-plane overload handling – the
goal of these counter-measures is not only to avoid a further U-plane traffic increase
but also to reduce the U-plane load in a non-graceful manner)
The overload detection mechanism allows to differentiate a peak load scenario from a
sustained traffic increase. The overload management function realizes the load control
loop, including timed-out values for the different load levels and the corresponding
overload actions (activation or deactivation).
The LTE2023: U-Plane Overload feature triggers the following mechanisms:
1. U-plane overload trigger based on QoS and packet scheduler load control
(UPOVT1): The number of UEs which can be scheduled by packet scheduler due to
the U-plane load is fewer than the number of UEs which should be scheduled to
meet the guaranteed service quality. This trigger is based on the QoS associated
with VoLTE calls, as VoLTE is expected to be the most critical service in this aspect.
2. U-plane overload trigger based on the number of UEs to be scheduled and packet
scheduler load control (UPOVT2): packet scheduler can schedule only very few UEs
per TTI due to the U-plane load; no matter whether the quality of service is impacted
or not.
3. U-plane overload trigger based on DL-physical layer overload detection (UPOVT3):
DL-physical layer overload might take place, for example, in scenarios with a high
load and where each UE uses two code words. In this case U-plane data packets for
some scheduled UEs cannot be processed in due time by the DL-physical layer and
are not transmitted on the air interface.

Features
Table 144 Mapping between U-plane overload triggers and the related counter-
measures
Rejection of Rejection of Rejection of Switch to No SRS
RRC HO E-RAB TxDiv (UPOVCM5)
(UPOVCM1) (UPOVCM2) (UPOVCM3) (UPOVCM4)
Packet scheduler
load control quality
X X X X X
based trigger
(UPOVT1)
Packet scheduler
load control quantity
X X X - -
based trigger
(UPOVT2)
DL-physical layer
overload trigger - - - X -
(UPOVT3)
U-plane overload counters and actions

In case of overload level 1 (UPOVL1), the eNB performs the following counter actions:
• a rejection of low priority radio resource control (RRC) connection requests
(establishment cause set to delayTolerantAccess, mo-data, mo-signaling, spare2, or
spare1) – UPOVCM1
• a rejection of an incoming non-emergency handover (HO) without a GBR bearer in
combination and/or with HO cause other than time critical handover (TCH) or
handover desirable for radio reasons (HDFRR) – UPOVCM2
In case of overload level 2 (UPOVL2), the eNB performs the following counter actions:
• a rejection of low priority RRC connection requests as defined in overload level 1 –
UPOVCM1
• a rejection of all non-emergency HOs – UPOVCM2
The ‘Miscellaneous cause – not enough user plane processing resources available’
cause value is used in case of a rejection.
This feature is not limited to these overload counter-measures only. In addition, it
introduces three extra counter-measures to enhance its own effectiveness (in case of
overload level 1 and 2):
• a rejection of E-RAB setup requests – UPOVCM3
– initial context setup requests are admitted for all UEs, irrespective of the RRC
establishment cause (in case of UPOVL1 or UPOVL1)
– E-RAB setup requests are admitted if the ARP value of at least one bearer in the
E-RABtobesetup list matches the ARP value of emergency or high priority
access (in case of UPOVL1 or UPOVL2)
– E-RAB setup requests are admitted if E-RABToBeSetupListBearerSUReq list
contains at least one GBR bearer (in case of UPOVL1)
– otherwise, E-RAB setup request is rejected
• the usage of a transmit diversity (TxDiv) transmission – UPOVCM4

Features
– in case of UPOVL1: dynamic switching from the TxDiv or single-stream (one-

code-word) transmission to two code words is prevented as long as UPOVL1 is
active; the TxDiv transmission mode is used instead
– in case of UPOVL2: all transmissions are done as the TxDiv transmission mode
for all of the already established calls and new incoming calls (that is, all two-
code-words transmissions) are switched to the TxDiv mode
• a suspension of the sounding reference symbol (SRS) usage for the UL scheduling
process – UPOVCM5
– SRS is suspended as long as UPOVL1 or UPOVL2 is active
The MIMO Mode Control supports the U-plane Overload Handling by downgrading a
two-codeword transmission into a one-codeword transmission. The overload mode is
called ‘U-plane overload counter-measure case 4’ and its abbreviated name is
UPOVCM4. For a UE which uses two-codeword transmission, the eNB takes the
following actions for UPOVCM4 (in case of overload level 2):
• TM3: falls back to transmit diversity using DCI format 2A
• TM4: falls back to one-layer spatial multiplexing using DCI format 2
• TM8: falls back to single-stream beamforming using DCI format 2B
• TM7 or TM9: UPOVCM4 is not applied
In case of an overload counter-measure ‘Suspend usage of SRS for scheduling’

(UPOVCM5), the UL scheduler must be set to a channel-unaware scheduler; it also
keeps the SRS measurement (for example, beamforming, ulpc, supercell, etc.)
The U-plane overload counters
The U-plane overload counters measure the time when the eNB is in the U-plane
overload level 1 (M8001C299) or in U-plane overload level 2 (M8001C300). In addition,
the M8013C66 counter counts the number of signaling connection requests rejected due
to the U-plane overload.
System impact
There are interdependencies between the following features:
• LTE1047: C-plane Overload Handling

The LTE1047: C-plane Overload Handling feature uses the same overload
philosophy as the LTE2023: User Plane Overload Handling feature, but the two
features have separate procedures to handle overload situations. There are also
different interactions depending on the same counter-measures enabled for a C-
plane and U-plane overload handling.
• LTE1113: eICIC-Macro
If the number of users per TTI is reduced due to eICIC, it is not taken into account for
a U-plane overload decision or calculation.
• LTE1496: eICIC-Micro
If the number of users per TTI is reduced due to eICIC, it is not taken into account for
a U-plane overload decision or calculation.
• LTE1117: MBMS
In case the number of users scheduled within a TTI will be used as an indication for
a U-plane overload, MBMS sub-frames shall be excluded.

Features
• LTE495: OTDOA
In case the number of users scheduled within a TTI will be used as an indication for
a U-plane overload, sub-frames carrying PRS shall be excluded.


In case the system is operated beyond its specification, or with other traffic profiles, or
feature mixes, a U-plane overload might exist. In these cases, the system performance
(values such as latencies, handover performance, and success rates as well as
individual and cell throughput) will be degraded both with and without this feature having
been activated. However, with this feature and counter-measures enabled, this
degradation will be done in a definite way. The goal of these counter-measures is to
ensure the quality of service for the admitted traffic and a stable operation of the system.
In case of a U-plane overload, the system performance might be degraded, especially in
cases where the U-plane overload counter-measures are enabled.
The main impacts of the different counter-measures concern:
• radio resource control (RRC) setup success rate
• uplink (UL) and downlink (DL) cell capacities related to the UL and DL throughput
• cell capacity with respect to the amount of all UEs in an RRC connected mode and
with respect to the activated radio access bearers (RABs)
• HO success and HO preparation success rate
• drop rates
• E-RAB setup success rate
• U-plane throughput of a single UE in UL and DL
• MIMO open loop (OL) or closed loop (CL) usage of a dual stream

LTE2023: User plane overload handling requirements, alarms and faults, commands,
Requirements

FDD TDD

Features

FDD TDD
Alarms
There are no alarms related to the LTE2023: User plane overload handling feature.

Alarm ID Alarm name
6120 EFaultId_UplaneOverlo 7655 CELL NOTIFICATION
adDetectedTrOneAI
adDetectedTrTwoAI
adDetectedTrThreeAI
For fault descriptions, see LTE Radio Access Operating Documentation/

Reference/Alarms.
Commands
There are no commands related to the LTE2023: User plane overload handling feature.

M8001C299 Time period of user plane in LTE cell load
overload level 1
M8001C300 Time period of user plane in LTE cell load
overload level 2
M8013C66 Number of Signaling LTE UE State
Connection Establishment
Requests rejected due to User
Plane overload

Features


KPI ID KPI name
LTE_5709a E-UTRAN Percentage of Time the Cell was in
the U-Plane Overload State
For key performance indicators descriptions, see LTE Operating

Documentation/Reference/Counters and Key Performance Indicators.
Parameters

name object
Activate U-plane actUplaneOvlH LNBTS - Common
overload handling andling
Enable incoming HO enableInHoRed LNBTS cpovlha Common
reduction
Enable RRC enableRrcConn LNBTS cpovlha Common
connection Red
reduction
U-plane overload upovlha LNBTS - Common
handling
Enable rejection enableERabSet LNBTS upovlha Common
of E-RAB setup upRed
requests
Enable rejection enableInHoRed LNBTS upovlha Common
of incoming inter-
eNB HO requests
Enable rejection enableRrcConn LNBTS upovlha Common
of RRC connection Red
requests
Enable suspension enableSuspend LNBTS upovlha Common
of SRS for Srs
scheduling
Enable Tx enableTxDivTr LNBTS upovlha Common
diversity ansmission
transmission

Sales information

Features

element
BSW - No
26.3 Activating and configuring LTE2023: User Plane

Overload Handling
Before you start
Table 151: Parameters used for activating and configuring LTE2023: User Plane
Overload Handling lists parameters used for the activation and configuration of the
LTE2023: User Plane Overload Handling feature.
Table 151 Parameters used for activating and configuring LTE2023: User Plane
Overload Handling
object locking
Activate U-plane overload handling activation flag no
(actUplaneOvlHandling)
U-plane overload handling mandatory configuration no
(upovlha) parameter's structure
g Note: When configuring the feature, note that suitable parameter values may depend,
among other things, on the cell's/eNB's location. For example, an eNB located in places
with a high population density or within a stadium might require other parameter
settings compared to those located in a rural area.
Procedure

2 Activate the LTE2023: User Plane Overload Handling feature.

d) Set the Activate U-plane overload
handling (actUplaneOvlHandling) parameter value to true.

Features
3 Configure the U-plane overload handling (upovlha) parameter.

c) Right-click the LNBTS object and create a new U-plane overload handling
parameter. Set the U-plane overload handling (upovlha) parameter
values.
Expected outcome
The LTE2023: User Plane Overload Handling feature is activated.
Further information
In case all counter-measures are disabled, the operator will still be informed about the
start and end of the U-plane overload condition.
26.4 Deactivating LTE2023: User Plane Overload

Handling
Before you start
The Activate U-plane overload handling (actUplaneOvlhandling)
parameter is used for deactivation. Modification of this parameter requires neither an
eNB restart nor cell locking.
Procedure

2 Deactivate the LTE2023: User Plane Overload Handling feature.

c) Expand the LNBTS.
d) Set the Activate U-plane overload
handling (actUplaneOvlhandling) parameter value to false.

Features
Expected outcome
The LTE2023: User Plane Overload Handling feature is deactivated.

LTE2051: Measurement based Idle Mode Load LTE15A Radio Resource Management and Telecom
Balancing Features
27 LTE2051: Measurement based Idle Mode Load

Balancing
27.1 Description of LTE2051: Measurement based Idle

Mode Load Balancing
The LTE2051: Measurement based Idle Mode Load Balancing feature enhances the Idle
Mode Load Balancing (IMLB) mechanism. In the enhanced mechanism, the eNodeB
uses the A4 based measurement to check the quality of an LTE target inter-frequency,
which is selected as a primary target with a highest priority by the IMLB algorithm.
Considering the measurement results, the eNodeB decides if dedicated priorities are
added to the RRC Release message or not.
Benefits
End-user benefits
Operator benefits
This feature provides the following benefit to the operator:
• prevents continuous cell reselection measurements
Requirements
Functional overview
The LTE2051: Measurement based Idle Mode Load Balancing feature introduces an
enhancement mechanism for the existing idle mode load balancing (IMLB) algorithms.
Within the scope of LTE2051: Measurement based Idle Mode Load Balancing feature,
the eNodeB uses the A4 IMLB measurement to check the quality of LTE target inter-
frequency, which was selected as a primary target with a highest priority by the IMLB
algorithm used in the LTE1677: Idle Mode Mobility Balancing Extensions feature.
Considering the measurement results, the eNodeB decides if a dedicated priorities are
added to the RRC Release message or not.
The LTE2051: Measurement based Idle Mode Load Balancing feature enables the
following functionalities:
• the operator decides whether the LTE target inter-frequency layers configured for
IMLB should be measured with A4 IMLB measurements before sending dedicated
priorities to the idle mode or not
• the operator configures reference symbol received power (RSRP) and/or reference
signal received quality (RSRQ) thresholds used for checking whether the target cell
fulfills the power and quality requirements

LTE15A Radio Resource Management and Telecom LTE2051: Measurement based Idle Mode Load
Features Balancing
• the eNodeB prolongs an existing inactivity timer to give the UE additional time to
perform A4 IMLB measurements
• if the IMLB algorithm selects an LTE inter-frequency as a primary target and that LTE
inter-frequency is allowed to run A4 IMLB measurements, then the eNodeB triggers
the UE to start A4 IMLB measurements for that frequency before sending the RRC
Release message to the UE
• if A4 IMLB report is received, the eNodeB checks the RSRP and/or RSRQ
parameters of a target cell against the configured thresholds so that a requested
minimum power and quality of the target cell is satisfactory before sending dedicated
priorities for the idle mode to UE
Conditions for an RRC connection release with a dedicated priority

The RRC connection of the UE is released with a dedicated priority (target cell frequency
getting the highest absolute priority) if all of the conditions below are true:
• an A4 IMLB measurement report is received before the A4 IMLB measurement timer

expires
• the target cell's RSRP and/or RSRQ parameters are better than the operator-
configurable absolute value in order to avoid a reselection to the cell with bad RF
conditions
• the target cell's RSRP and/or RSRQ parameters are better than the source cell's
RSRP and/or RSRQ increased by the operator-configurable offset (positive or
negative) in order to avoid a reselection to a cell with significantly worse RF
conditions
Otherwise, a normal RRC connection release without sending dedicated priorities is

applied. Data or S1 signaling activity during the A4 IMLB measurements leads to a
cancellation of the RRC Release message, and an inactivity timer is reset.
Conditions for activating A4 IMLB measurements
For the activation of A4 IMLB measurements, the following conditions must be met:
• the selected LTE target inter-frequency is allowed to run A4 IMLB measurements

• the UE supports A4 measurements (FGI bits #14 and #25)
• the RSRP and/or RSRQ thresholds related to the IMLB measurements are
configured (relevant parameters are set)
• there are no ongoing inter-frequency or/and inter-RAT measurements
• the maximum number of UEs with A4-based measurements activated is not reached
The A4 IMLB measurements are controlled with a supervision timer configured by the
operator. If A4 IMLB measurements cannot be applied to the UE, the RRC connection of
this UE is released with a dedicated priority determined originally by the IMLB algorithm
defined in the LTE1677: Idle Mode Mobility Balancing Extensions feature.
System impact
This feature requires the following feature to be enabled:
• LTE1677: Idle Mode Mobility Balancing Extensions
This feature reuses the already existing mechanism used for the RRC Release message
and measurement configuration.

Balancing Features


Management data
Sales information

Requirements

FDD TDD
NetAct NetAct 15.5 Support not required
Alarms
There are no alarms related to the LTE2051: Measurement based Idle Mode Load
Balancing feature.

There are no faults related to the LTE2051: Measurement based Idle Mode Load
Balancing feature.
Commands
There are no commands related to the LTE2051: Measurement based Idle Mode Load
Balancing feature.

Features Balancing

This feature introduces a new measurement type, M8034 LTE EUTRA carrier frequency.
The measurement contains counters which measure an intra LTE related events per E-
UTRA carrier frequency. The counters are provided per the LTE cell and per the E-UTRA
carrier frequency, for example, for each relationship between the LTE cell and the E-
UTRA carrier frequency, a separate counter is provided. This measurement is targeted to
the following objects:
• LNBTS/LNCEL
• MCC/MNC
• EARFCN

ID
M8034C Number of A4 measurement LTE EUTRA carrier frequency
0 activations for Measurement
Based IMLB
M8034C Number of successfully LTE EUTRA carrier frequency
1 evaluated A4 measurement
reports for Measurement Based
IMLB
For counter descriptions, see the LTE Measurements, Counters, and KPIs reference
document.

There are no key performance indicators related to the LTE2051: Measurement based
Idle Mode Load Balancing feature.
Parameters

Enable A4 event for enableA4IMLB IRFIM - common
idle mode load
balancing
Target cell min minDeltaRsrpI IRFIM - common
delta RSRP for idle MLB
mode load balancing
Target cell min minDeltaRsrqI IRFIM - common
delta RSRQ for idle MLB
mode load balancing
Target cell minimum minRsrpIMLB IRFIM - common
RSRP for idle mode
load balancing
Target cell minimum minRsrqIMLB IRFIM - common
RSRQ for idle mode
load balancing

Balancing Features

Activate actMeasBasedI LNBTS - common
measurement-based MLB
idle mode load
balancing
Idle mode load reportTimerIM LNBTS - common
balancing LBA4
supervision timer
for A4 event
LTE EUTRA carrier mtEutraFreque PMRNL - common
frequency ncy

Activation of idle actIdleLB LNBTS - common
mode load balancing
(IdleLB)
For parameter descriptions, see the LTE BTS Parameters reference document.
Sales information

Application software (ASW) SW asset monitoring No
27.3 Activating and configuring LTE2051: Measurement

based Idle Mode Load Balancing
Before you start
The Activate measurement-based idle mode load
balancing (actMeasBasedIMLB) parameter is used for activation. Modification of
this parameter does not require eNB restart or object locking.
Table 157: Parameters used for activating and configuring LTE2051: Measurement
based Idle Mode Load Balancing feature presents the parameters related to activation
and configuration of the LTE2051: Measurement based Idle Mode Load Balancing
feature.

Features Balancing
Table 157 Parameters used for activating and configuring LTE2051: Measurement
based Idle Mode Load Balancing feature
object locking
Activate measurement- activation flag no
based idle mode load
balancing
(actMeasBasedIMLB)
Idle mode load balancing mandatory configuration no
supervision timer for A4
event (reportTimerIMLBA4)
IRFIM identifier (irfimId) mandatory configuration no
EUTRA presence antenna mandatory configuration no
port1 (interPresAntP)
EUTRA frequency mandatory configuration no
value (dlCarFrqEut)
Allowed measurement mandatory configuration no
bandwidth (measBdw)
Enable A4 event for idle mandatory configuration no
mode load
balancing (enableA4IMLB)
Target cell min delta optional configuration no
RSRP for idle mode load
balancing
(minDeltaRsrpIMLB)
Target cell min delta optional configuration no
RSRQ for idle mode load
balancing
(minDeltaRsrqIMLB)
Target cell minimum RSRP optional configuration no
for idle mode load
balancing (minRsrpIMLB)
Target cell minimum RSRQ optional configuration no
for idle mode load
balancing (minRsrqIMLB)
The LTE1677: Idle Mode Mobility Balancing Extensions feature needs to be activated
before the activation of the LTE2051: Measurement based Idle Mode Load Balancing
feature (the value of Activation of idle mode load balancing (IdleLB)
(actIdleLB) parameter needs to be set to true).
Procedure


Balancing Features
2 Activate the LTE2051: Measurement based Idle Mode Load Balancing feature.

d) Set the Activate measurement-based idle mode load balancing
(actMeasBasedIMLB) parameter's value to true.
3 Configure the Idle mode load balancing supervision timer for A4

event (reportTimerIMLBA4) parameter.
a) Expand the MRBTS object.

b) Select the LNBTS object.
c) Set a desired value for the Idle mode load balancing supervision
timer for A4 event (reportTimerIMLBA4) parameter using a drop-
down list.
4 Configure the IRFIM object for every LTE target frequency and enable A4-based
measurements.

b) Expand the LNBTS object.
d) Add the IRFIM object.
e) In the created IRFIM object, configure the following parameters (mandatory):
• IRFIM identifier (irfimId)
• EUTRA presence antenna port1 (interPresAntP)
• EUTRA frequency value (dlCarFrqEut)
• Allowed measurement bandwidth (measBdw)
• Enable A4 event for idle mode load
balancing (enableA4IMLB)
5 Optional: Configure the RSRP and/or RSRQ thresholds.

b) Expand the LNBTS object.
d) Add the IRFIM object.
e) Configure the following parameters (optional).
• Target cell min delta RSRP for idle mode load
balancing (minDeltaRsrpIMLB)

Features Balancing
• Target cell min delta RSRQ for idle mode load

balancing (minDeltaRsrqIMLB)
• Target cell minimum RSRP for idle mode load
balancing (minRsrpIMLB)
• Target cell minimum RSRQ for idle mode load
balancing (minRsrqIMLB)
Expected outcome
The LTE2051: Measurement based Idle Mode Load Balancing feature has been
activated. The eNB provides the support for A4-based measurements for idle mode load
balancing.
27.4 Deactivating LTE2051: Measurement based Idle

Mode Load Balancing
Before you start
The Activate measurement-based idle mode load
balancing (actMeasBasedIMLB) parameter is used for deactivation. Modification of
this parameter does not require eNB restart or object locking.
Procedure

2 Deactivate the LTE2051: Measurement based Idle Mode Load Balancing feature.

d) Set the Activate measurement-based idle mode load balancing
(actMeasBasedIMLB) parameter's value to false.

Balancing Features
Expected outcome
The LTE2051: Measurement based Idle Mode Load Balancing feature has been
deactivated. The eNB continues evaluation of the already started A4-based
measurements and sends the A4 measurement report. New A4-based measurements
for idle mode load balancing are not started.

LTE15A Radio Resource Management and Telecom LTE2085: SIB Reception with Parallel Measurement
Features Gaps
28 LTE2085: SIB Reception with Parallel

Measurement Gaps

Measurement Gaps
A UE with configured measurement gaps will fail to receive a single SIB transmission
with a probability around 15%. The LTE2085: SIB Reception with Parallel Measurement
Gaps feature ensures transmission of SI messages at least two times per SI window,
which guarantees receiving one SI message per SI window even for UEs with configured
measurement gaps.
Benefits
End-user benefits
The LTE2085: SIB Reception with Parallel Measurement Gaps feature enhances the
possibility that the end user will receive at least one SIB during an SI window, regardless
of whether the measurement gaps are configured or not. It ensures a higher possibility to
receive:
• information regarding INTRA-frequency and INTER-frequency neighboring cells
• information for re-selection of a cell (for example, handover)
• ETWS/CMAS notifications/warnings
Operator benefits
The LTE2085: SIB Reception with Parallel Measurement Gaps feature:
• enables sending the SIB information at least twice at an interval greater than 6 ms
within each SI window
• guarantees ETWS/CMAS notifications/warnings broadcast reception for all UEs
• enables the UEs to receive SIBs even if they have a measurement gap configured,
which is essential in case of warning broadcasts (ETWS, CMAS)
Requirements
Functional overview
The SIBs carry relevant information for the UE, which helps the UE, for example, to
access a cell or perform a cell (re-)selection. They are also used to transmit warning
messages; SIB10 and SIB11 carry ETWS notifications, and SIB12 carries the CMAS
notification.
Measurement gaps are configured for UEs in the cell's handover zone; the measurement
gaps are repeated every 40 ms, and they last for 6 ms in DL (7 ms in UL under certain
conditions). The starting points of measurement gaps are distributed in time across all

LTE2085: SIB Reception with Parallel Measurement LTE15A Radio Resource Management and Telecom
Gaps Features
UEs in the cell in order to equalize the UL traffic generated when UEs report their
measurement results. This means the UEs with measurement gaps will fail to receive a
single SIB transmission with a probability of 6/40 = 15%.
The LTE2085: SIB Reception with Parallel Measurement Gaps feature ensures that a UE
having measurement gaps activated is able to receive SIBs at least once during an SI
window. If the code rate of a SIB message is too high, then two or three transmissions
are arranged for this message in the same SI window, see Figure 18: SIB reception with
parallel measurement gaps.
Figure 18 SIB reception with parallel measurement gaps
ExampleswithoutLTE2085 ExamplewithLTE2085
20msSIBwindow 20msSIBwindow 20msSIBwindow
SIBtransmissiontwice SIBtransmissiontwice SIBtransmissionmorethan

perSIwindow perSIwindow twiceperSIwindow
(caseexample excluded
byLTE2085)
Measurementgaps
SIB1
MeasurementgapsthatcoversbothSIBtransmission
SIB1
SIBtransmission
With LTE2085: SIB Reception with Parallel Measurement Gaps, an additional

transmission is scheduled in order to cover the case of any possible overlap between a
measurement gap and transmission of the SI message. Restrictions on the configuration
parameters are introduced to avoid an SI window smaller than 20 ms.
g Note: From LTE-FDD 15A onward (with the introduction of the

LTE2085: SIB Reception with Parallel Measurement Gaps feature), CMAS/ETWS
notifications can be activated only if SI window length (siWindowLen) is equal
or greater than 20 ms.
g Note: From RL70 onward, if the SI window length (siWindowLen) parameter

is set to 10 ms or higher, basic eNB software sends two mandatory transmissions for
SIBs related to ETWS and CMAS and also for SIB2 per SI window, with transmissions
separated by more than 6 ms. The SI window length (siWindowLen)
parameter can still be set to smaller values but the reception of SIB2 for UEs with
measurement gaps is guaranteed only if the SI window length (siWindowLen)
is equal or greater than 10 ms. Activation of the
LTE2085: SIB Reception with Parallel Measurement Gaps feature shows an additional
effect only for SIB3 and higher.
UEs with a certain chipset might experience HO failures under the following rare
conditions:
• inter-frequency HO to an eICIC-enabled eNB which runs in muting pattern 1

Features Gaps
• UEs configured with a measurement gap that covers the subframe in which the small
cell sends a system information block (SIB)
• the SI window length (siWindowLen) parameter is set to 20 ms, therefore,
there will be only one subframe available if the SIB window coincides with the first
half of the eICIC pattern of a 40-ms duration
UEs with the chipset do not use SIB2 data they were provided as part of the HO
procedure. The UEs try to read SIB2 in the target cell and fail if it does not succeed
within a preset time. It is recommended to perform one of the following actions to ensure
smooth service conditions in HetNet scenarios:
• Activate the LTE2085: SIB Reception with Parallel Measurement Gaps feature.
• Set the SI window length (siWindowLen) parameter to 40 ms in all eICIC
small cells.
The LTE494: Commercial Mobile Alert System feature supports SIBs 12, and the
LTE843: ETWS Broadcast feature supports SIBs 10 and SIBs 11; however, the two
features cannot be activated together.
System impact
The following features are affected by the LTE2085: SIB Reception with Parallel
Measurement Gaps feature:
• LTE1113: eICIC Macro and LTE1496: eICIC Micro

If the eICIC is activated, the LTE2085: SIB Reception with Parallel Measurement
Gaps feature verifies whether eICIC muting patterns are compatible with the SIB
transmission's timing and the timing of other affected features.
• LTE1117: Multimedia Broadcast Multicast Service
If the MBMS is activated, the LTE2085: SIB Reception with Parallel Measurement
Gaps feature verifies whether other affected features leave a minimum number of
subframes open for usage by the MBMS.
• LTE495: Observed Time Difference of Arrival
The LTE2085: SIB Reception with Parallel Measurement Gaps feature can be
activated only if OTDOA settings are compatible.
• LTE1709: Liquid Cell
The LTE2085: SIB Reception with Parallel Measurement Gaps feature can be
activated only if liquid cell settings are compatible.
• LTE55: Inter-frequency Handover and LTE1679: DRX with Parallel UE Measurement
Gaps

The Earthquake and Tsunami Warning System (ETWS) and Commercial Mobile Alert
System (CMAS) are rare events, so a duplicated transmission of ETWS/CMAS
messages does not consume noteworthy amounts of resources. Further impact depends
on the Twofold transmission of SIBs per SI window
(sib2xTransmit) parameter.
The LTE2085: SIB Reception with Parallel Measurement Gaps feature impacts system
performance and capacity in the following way:

Gaps Features
• there is no impact if sib2xTransmit = false; thus, it does not limit throughput

or performance
• SIB3 and above are transmitted at least two times per SI window if
sib2xTransmit = true, which consumes double capacity

Requirements

FDD TDD
System release FDD-LTE15A Not supported
Flexi Zone Controller FL16 Not supported
NetAct 15.5 Not supported
UE 3GPP R8 Not supported
Alarms
There are no alarms related to the LTE2085: SIB Reception with Parallel Measurement
Gaps feature.

There are no faults related to the LTE2085: SIB Reception with Parallel Measurement
Gaps feature.
Commands
There are no commands related to the LTE2085: SIB Reception with Parallel
Table 159 Counters modified by LTE2085

M8012C18 Volume of DL RLC PDUs LTE Cell Throughput
transmitted

Features Gaps

M8011C25 DL PRB utilization per TTI LTE Cell Resource
Level 1
Level 2
Level 3
Level 4
Level 5
Level 6
Level 7
Level 8
Level 9
Level 10
M8011C35 DL PRB utilization per TTI Min LTE Cell Resource
M8011C36 DL PRB utilization per TTI Max LTE Cell Resource
Mean
g Note: The following counters are not affected by additional repetitions introduced by
LTE2085: SIB Reception with Parallel Measurement Gaps:
• M8001C231: Number of primary ETWS notifications
• M8001C232: Number of secondary ETWS notifications
• M8001C233: Number of CMAS notifications

Reference/Counters.

There are no key performance indicators related to the LTE2085: SIB Reception with
Parallel Measurement Gaps feature.
Parameters

Gaps Features

d object
Twofold transmission of sib2xTransmit SIB common
SIBs per SI window

d object
Activation CMAS support actCMAS LNBTS common
Activation ETWS support actETWS LNBTS common
Activation MBMS support actMBMS LNBTS common
Activation eICIC support actEicic LNCEL common
Activation Liquid Cell actLiquidCell LNCEL FDD
support _FDD
PRS activation actOtdoa LNCEL common
PRS configuration index prsConfigurati LNCEL common
onIndex _FDD
for FDD
and
LNCEL
_TDD
for TDD
SI window length siWindowLen SIB common
System information sibSchedulingL SIB common
scheduling list ist
Highest allowed muting eIcicMaxMutePa LNCEL common
pattern ttern
CSI-RS subframe csiRsSubfr LNCEL FDD
configuration

Sales information

BSW - No

Features Gaps
28.3 Activating and configuring LTE2085: SIB Reception

with Parallel Measurement Gaps with the Twofold
transmission of SIBs per SI window parameter
Before you start
Table 163: Parameters used for activating and configuring LTE2085: SIB Reception with
Parallel Measurement Gaps lists parameters used for activation and configuration of the
LTE2085: SIB Reception with Parallel Measurement Gaps feature.
Table 163 Parameters used for activating and configuring LTE2085: SIB Reception
with Parallel Measurement Gaps
object locking
Twofold transmission of SIBs configuration object locking
per SI window (sib2xTransmit)
The LTE2085: SIB Reception with Parallel Measurement Gaps feature is activated either
by activating the LTE494: Commercial Mobile Alert System (CMAS) feature for SIB12, or
by activating the LTE843: ETWS Broadcast feature for SIB10 and SIB11, or by setting
the Twofold transmission of SIBs per SI window (sib2xTransmit)
parameter to true for all other SIBs except SIB1.
Procedure

procedure perform the steps described in this procedure
2 Activate and configure the LTE2085: SIB Reception with Parallel Measurement Gaps
feature.

f) Select the SIB object.
g) Set the Twofold transmission of SIBs per SI
window (sib2xTransmit) parameter value to true.

Gaps Features
g Note: The value of the

Twofold transmission of SIBs per SI window (sib2xTransmit)
parameter is not recommended to be set to true provided the
Downlink channel bandwith (dlChBw) is less than 10 MHz.
3 Optional: If it is not yet configured, set the SI window length (siWindowLen)

parameter.

b) Select the SIB object.
c) Set the SI window length (siWindowLen) parameter's value to 20 ms or
40 ms.
Expected outcome
When the Twofold transmission of SIBs per SI
window (sib2xTransmit) parameter is set to true, the SIBs 3 and higher are
transmitted at least twice per SI window, with a time difference higher than 6 ms. For
SIB10 and SIB11 being transmitted twice per SI window, the LTE843: ETWS Broadcast
feature must be activated and for SIB12, the LTE494: Commercial Mobile Alert System
(CMAS) feature must be activated; however, only one of these features can be active at
a time.

with Parallel Measurement Gaps with a selected
feature
Before you start
The LTE2085: SIB Reception with Parallel Measurement Gaps feature does not have an
activation flag and is activated by default.
Parallel Measurement Gaps lists parameters used for activation and configuration of the
LTE2085: SIB Reception with Parallel Measurement Gaps feature.
object locking
Activation ETWS support activation flag no
(actETWS)
Activation CMAS support activation flag no
(actCMAS)

Features Gaps
with Parallel Measurement Gaps (Cont.)
object locking
Twofold transmission of SIBs optional no
SI window length mandatory no
(siWindowLen)
System information scheduling mandatory no
list (sibSchedulingList)
The LTE2085: SIB Reception with Parallel Measurement Gaps feature is activated either
by activating the LTE494: Commercial Mobile Alert System (CMAS) feature for SIB12, or
by activating the LTE843: ETWS Broadcast feature for SIB10 and SIB11, or by setting
the Twofold transmission of SIBs per SI window (sib2xTransmit)
parameter to true.
The LTE494: Commercial Mobile Alert System (CMAS) and LTE843: ETWS Broadcast
features cannot be activated at the same time. Only one can be active at a time and an
activation of that feature will activate LTE2085: SIB Reception with Parallel Measurement
Gaps feature for related SIBs.

Gaps Features
f If the following conditions are not fulfilled, the validation of the configuration plan file will
fail. BTS Site Manager informs the operator about the validation failure:
• If the Activate enhanced inter-cell interference
coordination (actEicic) parameter's value is set to true, and the
Cell type (cellType) parameter's value is not set to large in any LNCELobject
of the eNB, then both parameters DRX profile 5:DRX long
cycle (drxProfile5-drxLongCycle) and
DRX smart profile 5:DRX long cycle (
drxSmartProfile5-drxLongCycle) must be set to 640 ms.
coordination (actEicic) parameter's value is set to true, and the
Cell type (cellType) parameter's value is set to large in any LNCEL object of
the eNB, then the Highest allowed muting
pattern (eIcicMaxMutePattern) parameter must be set as greater than
mp1.
coordination (actEicic) parameter's value is set to true, then the
Activate support for MBMS (actMBMS) parameter must be set to false.
• If the Activate support for MBMS (actMBMS) parameter's values is set to
true, then the
Activate enhanced inter-cell interference
coordination (actEicic) parameter's value must be set to false.
• If the PRS activation (actOtdoa) parameter's value is set to true, and the
number of configured SIBs is seven or smaller, then the
PRS configuration index (prsConfigurationIndex) parameter must
be set to one of the following values: 151, 471, 1111, or 2391.
SI window length (siWindowLen) parameter is set to 20 ms, and the
number of configured SIBs is eight or higher, then the
be set to one of the following values: 471, 1111, or 2391.
number of configured SIBs is eight or higher, then the
be set to one of the following values: 1111 or 2391.
Migration rules for the SI window length (siWindowLen) parameter:

• If the Activation ETWS support (actETWS) parameter or the
Activation CMAS support (actCMAS) parameter is set to true, and the
SI window length (siWindowLen) parameter is smaller than 20 ms in RL70,
then during migration to RL15A the SI window length (siWindowLen)
parameter will change to 20 ms.
Migration rules for the Periodicity (siMessagePeriodicity) parameter:

PRS activation (actOtdoa) parameter is set to true in RL70, then during
migration to RL15A the Periodicity (siMessagePeriodicity) parameter
must be equal or greater than the following equation:

Features Gaps
siWindowLen * (# of SIBs (sets in structure sibSchedulingList + 2))+

10ms
The value of the Periodicity (siMessagePeriodicity) parameter that does

not fulfill this equation needs to be set to the next, higher value that fulfills it. The
possible values are 80, 160, 320, 640, 1280, 2560, or 5120.
PRS activation (actOtdoa) parameter is set to false in RL70, then during
migration to RL15A the Periodicity (siMessagePeriodicity) parameter
must be equal or greater than the following equation:
siWindowLen * ((# of SIBs (sets in structure sibSchedulingList + 2))
The value of the Periodicity (siMessagePeriodicity) parameter that does

not fulfill this equation needs to be set to the next, higher value that fulfills it. The
possible values are 80, 160, 320, 640, 1280, 2560, or 5120.
Migration rules for the PRS configuration

index (prsConfigurationIndex) parameter:
PRS activation (actOtdoa) parameter is set to true, and the number of
configured SIBs is eight or higher, and the PRS configuration
index (prsConfigurationIndex) parameter is set to any other value than
471, 1111, or 2391, then during migration to RL15A the
be set to 471.
PRS activation (actOtdoa) parameter is set to true, and the
number of configured SIBs is eight or higher, and the
PRS configuration index (prsConfigurationIndex) parameter is set
to any other value than 471, 1111, or 2391, then during migration to RL15A the
be set to 471.
PRS activation (actOtdoa) parameter is set to true, and the
number of configured SIBs is eight or higher, and the
PRS configuration index (prsConfigurationIndex) parameter is set
to any other value than 1111, or 2391, then during migration to RL15A the
be set to 1111.
PRS activation (actOtdoa) parameter is set to true, then PRS period must
be equal or greater than:

Gaps Features
siWindowLen * (# of SIBs(sets in structure sibSchedulingList + 2))+

10ms
where, depending on the PRS configuration

index (prsConfigurationIndex) parameter, the PRS period in the above
equation is set to:
– 160 ms for PRS configuration index (prsConfigurationIndex) =
151
471
1111
2391
g
Note: The value of the PRS period that does not fulfill the above equation, shall
be changed to the next, higher value that fulfills the equation.
Modification of some of the mentioned parameters requires object locking or BTS

restart. This means that activation will cause a service outage if the parameters that
require object locking or BTS restart have been modified.
Procedure

2 Activate and configure the LTE2085: SIB Reception with Parallel Measurement Gaps
feature with a selected feature.
Activation with the LTE843: ETWS Broadcast feature:

d) Set the Activation ETWS support (actETWS) parameter's value to true.
Activation with the LTE494: Commercial Mobile Alert System (CMAS) feature:
d) Set the Activation CMAS support (actCMAS) parameter's value to true.

Features Gaps
3 Optional: If not yet configured, configure the PWS with emergency area ID
parameter.
a) Set the PWS with emergency area ID (pwsWithEmAreaId) parameter's

value to true or false.
b) If the PWS with emergency area ID (pwsWithEmAreaId) parameter's
value is set to true, continue as follows.
e) If not yet added, add the Emergency area ID list (emAreaIdList)
parameter and set a value from 0 to 16777215.
4 If not yet configured, set the SI window length (siWindowLen) parameter.

c) Set the SI window length (siWindowLen) parameter's value to 20 ms or
40 ms.
5 If not yet configured, set the System information scheduling

list (sibSchedulingList) parameter.

c) Add the System information scheduling
list (sibSchedulingList) parameter.
d) Set the SIB type (siMessageSibType) parameter's value:
• for the ETWS notifications SIB10 and SIB11 parameters are required
• for the CMAS notifications SIB12 parameter is required
• for SIB4 add LNCEL:IAFIM object and set all required parameters
• for SIB5 add LNCEL:IRFIM object and set all required parameters
• for SIB6 add LNCEL:UFFIM object and set all required parameters
• for SIB7 add LNCEL:GFIM object and set all required parameters
• for SIB8 add LNCEL:CDFIM object and set all required parameters
e) Select and set the Periodicity (siMessagePeriodicity) parameter's

value from a drop-down list for each selected SIB type.
f) Select and set the Repetition (siMessageRepetition) parameter's value
to 1 for each selected SIB type.
Expected outcome

Gaps Features
The LTE2085: SIB Reception with Parallel Measurement Gaps feature is activated
together with the LTE843: ETWS Broadcast feature. There are at least two subframes
available for the transmission of the ETWS notification in SIB10 and SIB11 within each
SI window.
The LTE2085: SIB Reception with Parallel Measurement Gaps feature is activated
together with the LTE494: Commercial Mobile Alert System (CMAS) feature. There are
at least two subframes available for the transmission of the CMAS notification in SIB12
within each SI window.
Further information
When the Twofold transmission of SIBs per SI
window (sib2xTransmit) parameter is set to true, the SIBs 3 and higher are
transmitted at least twice per SI window, with a time difference higher than 6 ms. For
SIB10 and SIB11 being transmitted twice per SI window, the LTE843: ETWS Broadcast
feature must be activated and for SIB12, the LTE494: Commercial Mobile Alert System
(CMAS) feature must be activated; however, only one of these features can be active at
a time.
28.5 Deactivating LTE2085: Reception with Parallel

Measurement Gaps
Before you start
Table 165: Parameters used for deactivating LTE2085: Reception with Parallel
Measurement Gaps lists parameters used for deactivation of the LTE2085: Reception
with Parallel Measurement Gaps feature.
Table 165 Parameters used for deactivating LTE2085: Reception with Parallel
Measurement Gaps
object locking
Twofold transmission of SIBs deactivation object locking
Activation ETWS support deactivation no
(actETWS)
Activation CMAS support deactivation no
(actCMAS)
Procedure


Features Gaps
2 Deactivate the LTE2085: Reception with Parallel Measurement Gaps feature.
If the LTE843: ETWS Broadcast feature is configured:

d) Set the Activation ETWS support (actETWS) parameter's value to false.
If the LTE494: Commercial Mobile Alert System (CMAS) feature is configured:

d) Set the Activation CMAS support (actCMAS) parameter's value to false.
If the Twofold transmission of SIBs per SI window parameter is

configured:
window (sib2xTransmit) parameter's value to false.
Expected outcome
The LTE2085: Reception with Parallel Measurement Gaps feature is deactivated.
Warning notifications are not transmitted any more. SIBs 3 and higher are transmitted
only once per SI window.
Further information
There might still be repetitions of SIBs caused by the code rate of a message.

LTE2120: TDD SIB reception with parallel LTE15A Radio Resource Management and Telecom
measurement gaps Features
29 LTE2120: TDD SIB reception with parallel

measurement gaps

Measurement Gaps
The LTE2120: SIB Reception with Parallel Measurement Gaps feature improves a SIB
schelduling system within a 20 ms/40 ms window size.
Benefits
End-user benefits
This feature guarantees receiving:
• earthquake and tsunami warning system (ETWS) notifications even if measurement

gaps occur
• commercial mobile alert system (CMAS) notifications even if measurement gaps
occur
• other SIBs (from SIB2 to SIB9) even if measurement gaps occur
Operator benefits
• two mandatory transmissions within each SI window

• a longer system information (SI) window
Requirements
Functional overview
The LTE2120: SIB Reception with Parallel Measurement Gaps feature assures that all
UEs receive the system information broadcast (SIB) messages on a first possible
occasion within the SI window even if the measurement gaps occur. The SIBs carry
relevant information which helps UEs to access a cell or perform its re-selection. They
also provide information related to intra-frequency, inter-frequency and inter-RAT cell re-
selections. In TD-LTE 15A, there are 13 types of SIBs and master information block
(MIB). The MIB includes parameters that are essential for the UE's initial access to the
network. Each SIB has a unique role to perform; it contains a specific piece of
information which is related to its assigned function (see Figure 19: Different types of
SIBs). The LTE2120: SIB Reception with Parallel Measurement Gaps feature guarantees
two mandatory transmissions for SIBs related to ETWS and CMAS and also for all other
SIBs: from SIB2 to SIB9.

LTE15A Radio Resource Management and Telecom LTE2120: TDD SIB reception with parallel
Features measurement gaps
Figure 19 Different types of SIBs
SIB1
SIB7 SIB3
MIB SIB2
SIB6
SIB5
SIB8
Every SIB is transferred through an SI message. The SI message contains only one SIB
type, and it is transmitted during the SI window. One SI message can be repeated during
one SI window. Two SIBs transmissions within the window are spaced apart by more
than 6 ms to prevent the SIB reception from being blocked by a measurement gap. The
eNB introduces a minimum length of 20 ms for the SI window. As a result, SIBs are sent
at least twice (on up to four occasions) during each SI window. This ensures that all UEs
in measurement gaps have at least one occasion during the SI window to receive the
SIBs even if there is a collision between the measurement gaps and warning massages.
g Note: From RL55TD onward, if the SI window length (siWindowLen) parameter

is set to 10 ms or higher, basic eNB software sends two mandatory transmissions for
SIBs related to ETWS, CMAS, and also for SIB2 per SI window, with transmissions
separated by more than 6 ms.
DL different sub-frames types

The downlink (DL) scheduler arranges two or three transmissions of the same message
in the same SI window if the code of a SIB message is too high. On the contrary, the
LTE2120: SIB Reception with Parallel Measurement Gaps feature schedules a
mandatory additional transmission to cover the case that one might not be received by a
UE with a measurement gap applied. Resources that are not used by SIB remain
available to the DL scheduler. To ensure that these SIB transmissions can be scheduled,
this feature introduces restrictions to the configuration parameters of all features with a
periodic pattern in a DL direction. In some scenarios, it is hard to find up to four
appropriate SIB transmissions within the 20 ms. In this case, the LTE2120: SIB
Reception with Parallel Measurement Gaps feature tries to find the most adequate SIB
transmissions.
In the LTE2120: SIB Reception with Parallel Measurement Gaps feature, there are
several types of DL sub-frames:
• normal sub-frames selected for the first transmission
• special sub-frames ssp3, ssp4, and ssp7, selected for a SIB transmission following
normal sub-frames
• normal sub-frames with CSI-RS selected if the two types of sub-frames above are
not enough for a SIB transmission
• normal sub-frames with paging (currently, sub-frame 0 for TDD) selected before CSI-
RS subframes if there is enough space for a SIB transmission

System impact
There are the following interdependencies between features:
• LTE494: Commercial Mobile Alert System (CMAS)

If the LTE494: Commercial Mobile Alert System (CMAS) feature is activated, the
LTE2120: SIB Reception with Parallel Measurement Gaps feature activates
automatically.
• LTE843: ETWS Broadcast.
If the LTE843: ETWS Broadcast feature is activated, the LTE2120: SIB Reception
with Parallel Measurement Gaps feature activates automatically.


The LTE2120: SIB Reception with Parallel Measurement Gaps feature influences the
decrease in DL peak throughput.
Management data
Sales information

LTE2120: TDD SIB reception with parallel measurement gaps requirements,
measurements and counters, parameters, and sales information
Requirements

FDD TDD
System release Not Supported TD-LTE 15A
Flexi Multiradio 10 BTS Not Supported TL15A
Flexi Multiradio 10 Indoor BTS Not Supported TL15A
Nokia AirScale BTS Not Supported TL16A
Flexi Zone BTS Not Supported TL15A
Flexi Zone Access Point Not Supported TL16


FDD TDD
Cloud Flexi Zone Controller Not Supported TL17A
OMS Not Supported Not Supported
NetAct Not Supported Not Supported
MME Not Supported Not Supported
SAE GW Not Supported Not Supported
UE Not Supported 3GPP R8 mandatory
Alarms
There are no alarms related to the LTE2120: TDD SIB reception with parallel
measurement gaps feature.

There are no faults related to the LTE2120: TDD SIB reception with parallel
Commands
There are no commands related to the LTE2120: TDD SIB reception with parallel

M8001C231 Number of primary ETWS LTE Cell Load
notifications
M8001C232 Number of secondary ETWS LTE Cell Load
notifications
M8001C233 Number of CMAS notifications LTE Cell Load

There are no key performance indicators related to the LTE2120: TDD SIB reception with
parallel measurement gaps feature.
Parameters

name object
Twofold sib2xTransmit SIB _ common
transmission of
SIBs per SI window


name object
Activation CMAS actCMAS LNBTS _ common
support
Activation ETWS actETWS LNBTS _ common
support
Activate enhanced actEicic LNCEL _ common
inter-cell
interference
coordination
PRS activation actOtdoa LNCEL _ common
Highest allowed eIcicMaxMuteP LNCEL _ common
muting pattern attern
TDD subframe tddFrameConf LNCEL _ common
configuration _FDD/_TDD
TDD special tddSpecSubfCo LNCEL _ common
subframe nf _FDD/_TDD
configuration
SI window length siWindowLen SIB _ common
System information sibScheduling SIB _ common
scheduling list List
Sales information

element
BSW - No

Before you start
Parallel Measurement Gaps lists parameters used for the activation and configuration of
the LTE2120: SIB Reception with Parallel Measurement Gaps.
object locking
Twofold transmission of SIBs per activation flag object locking
SI window (sib2xTransmit)

with Parallel Measurement Gaps (Cont.)
object locking
SI window length (siWindowLen) mandatory configuration no
System information scheduling list mandatory configuration no
(sibSchedulingList)
Activation CMAS support mandatory configuration no
(actCMAS)
Activation ETWS support mandatory configuration no
(actETWS)
Emergency area ID list optional configuration no
(emAreaIdList)
The LTE2120: SIB Reception with Parallel Measurement Gaps feature activates
automatically when one of the following features is configured:
• LTE494: Commercial Mobile Alert System (CMAS)

g Note: It is not supported to set both Activation CMAS support (actCMAS) and
Activation ETWS support (actETWS) parameter values to true. Either
actCMAS or actETWS parameter can be activated at the same time.
To activate the feature, choose one of the following options:
• Option one (two mandatory transmissions of SIB 2 to SIB 9): the LTE494:
Commercial Mobile Alert System (CMAS) and LTE843: ETWS Broadcast features
are disabled, and the Twofold transmission of SIBs per SI window (sib2xTransmit)
activation flag is set to true
• Option two (two mandatory transmissions of SIB 10 and 11, and optionally from SIB
2 to SIB 9): the LTE494: Commercial Mobile Alert System (CMAS) feature is
disabled, the LTE843: ETWS Broadcast feature is enabled, and the Twofold
transmission of SIBs per SI window (sib2xTransmit) activation flag is set to true or
false
• Option three (two mandatory transmissions of SIB 12, and optionally from SIB 2 to
SIB 9): the LTE494: Commercial Mobile Alert System (CMAS) feature is enabled, the
LTE843: ETWS Broadcast feature is disabled, and the Twofold transmission of SIBs
per SI window (sib2xTransmit) activation flag is set to true or false

29.3.1 Option one (two mandatory transmissions of SIB 2 to SIB

9): the LTE494: Commercial Mobile Alert System (CMAS)
and LTE843: ETWS Broadcast features are disabled, and
the Twofold transmission of SIBs per SI
window (sib2xTransmit) activation flag is set to true
Procedure

2 Set the SIB Twofold transmission of SIBs per SI

window (sib2xTransmit) activation flag to true.

e) Select the SIB object.
f) Set the Twofold transmission of SIBs per SI
window (sib2xTransmit) parameter value to true.
3 Set the SI window length (siWindowLen) parameter value.

b) Set the SI window length (siWindowLen) parameter value to 20 ms or 40
ms.
Expected outcome
The LTE2120: SIB Reception with Parallel Measurement Gaps feature is activated; there
are two mandatory transmissions of SIB 2 to SIB 9 within each SI window.

g Note: While activating the LTE2120: SIB Reception with Parallel Measurement Gaps
feature, ensure the following configurations are set:
• If tddFrameConf is set to 1, and actOtdoa is set to true, configure the following
parameters as indicated below:
– if siWindowLen is set to 20 ms, and the number of configured SIBs (that is,
the number of sets in the sibSchedulingList structure + 2) is 8 or higher,
then prsConfigurationIndex must be set to one of the following values:
474, 479, 1114, 1119, 2394, or 2399, or
– if siWindowLen is set to 40 ms, and the number of configured SIBs (for
example, the number of sets in the sibSchedulingList structure + 2) is 8
or higher, then prsConfigurationIndex must be set to one of the following
values: 1114, 1119, 2394, or 2399
• If tddFrameConf is set to 1, and actEicic is set to true, configure the following

– csiRsSubfrConf must be set to one of the following values: 9, 29, 49, 69,
89, 109, 129, 149, or
– if tddSpecSubfConf is not 3, 4, 7, then csiRsSubfrConf must be set to
one of the following values: 29, 49, 69, 89, 109, 129, 149

473, 478, 1113, 1118, 2393, 2398, or
1113, 1118, 2393, 2398

88, 108, 128, 148, or
– if tddSpecSubfConf is not 3, 4, 7, eIcicMaxMutePattern is higher than
or equal to 3, and cellType is set to large, then csiRsSubfrConf must be
set to one of the following values: 28, 48, 68, 88, 108, 128, 148
• If tddFrameConf is set to 1, csiRsSubfrConf must be set to one of the

following values: 4, 9, 29, 49, 69, 89, 109, 129, 149.
• If actMBMS is set to true, then csiRsSubfrConf must be set to either 8, 28, 48,
68, 88, 108, 128 or 148 in all LNCEL_TDD instances with earfcn equal to
mbsfnEarfcn and chBw equal to mbsfnDlChBw. If sib2xTransmit is set to
true, then dlChBw and ChBw should be greater than or equal to 10 MHz.
29.3.2 Option two (two mandatory transmissions of SIB 10 and

11, and optionally from SIB 2 to SIB 9): the LTE494:
Commercial Mobile Alert System (CMAS) feature is
disabled, the LTE843: ETWS Broadcast feature is enabled,

and the Twofold transmission of SIBs per SI

window (sib2xTransmit) activation flag is set to true or
false
Procedure

2 If the LNBTS Activation CMAS support (actCMAS) parameter value is set to

false, and the LNBTS Activation ETWS support (actETWS) parameter value is
set to true, set the SIB Twofold transmission of SIBs per SI
window (sib2xTransmit) activation flag to true or false.

f) For the SIB object, set the parameter values as follows:
• Twofold transmission of SIBs per SI
window (sib2xTransmit) to true or false
• SI window length (siWindowLen) to 20 ms or 40 ms
• Right-click the SIB object and add the System information
scheduling list (sibSchedulingList) parameter. Configure SIB 10
and SIB 11.
3 For the LNBTS object, set the parameter values.
• Expand the LNBTS object.

• Set the Activation ETWS support (actETWS) parameter value to true.
• Set the PWS with emergency area ID (pwsWithEmAreaId) parameter
– If the pwsWithEmAreaId parameter is set to true, add and configure the
LNCEL Emergency area ID list (emAreaIdList) parameter value.
Expected outcome

are two mandatory transmissions of SIBs 10 and 11 (and optionally for SIBs 2 and
higher) within each SI window.

g Note: While activating the LTE2120: SIB Reception with Parallel Measurement Gaps
• If actEicic is set to true, and cellType is not set to large in any LNCEL of the
eNB, then DRX drxProfile5-drxLongCycle must be set to 640 ms and
SDRX drxSmartProfile5-drxLongCycle must be set to 640 ms.
474, 479, 1114, 1119, 2394, or 2399, or
values: 1114, 1119, 2394, or 2399

89, 109, 129, 149, or

– if siWindowLen is set to 20 ms and the number of configured SIBs (that is, the
number of sets in the sibSchedulingList structure + 2) is 8 or higher, then
prsConfigurationIndex must be set to one of the following values: 473,
478, 1113, 1118, 2393, 2398, or
1113, 1118, 2393, 2398

88, 108, 128, 148, or
– if tddSpecSubfConf is not 3, 4, 7, eIcicMaxMutePattern is higher than
or equal to 3, and cellType is set to large, then csiRsSubfrConf must be
set to one of the following values: 28, 48, 68, 88, 108, 128, 148



29.3.3 Option three (two mandatory transmissions of SIB 12, and

optionally from SIB 2 to SIB 9): the LTE494: Commercial
Mobile Alert System (CMAS) feature is enabled, the
LTE843: ETWS Broadcast feature is disabled, and the
Twofold transmission of SIBs per SI
window (sib2xTransmit) activation flag is set to true or
false
Procedure

2 If the LNBTS Activation CMAS support (actCMAS) parameter value is set to

true, and the LNBTS Activation ETWS support (actETWS) parameter value is
set to false, set the SIB Twofold transmission of SIBs per SI
window (sib2xTransmit) activation flag to true or false.

f) For the SIB object, set the parameter values as follows.
g)
• Twofold transmission of SIBs per SI
window (sib2xTransmit) parameter value to true or false
• SI window length (siWindowLen) to 20 ms or 40 ms
• Right-click the SIB object and add the System information
scheduling list (sibSchedulingList) parameter. Configure SIB
12.
3 For the LNBTS object, set the parameter values.
• Expand the LNBTS object.

• Set the Activation CMAS support (actCMAS) parameter value to true.
• Set the PWS with emergency area ID (pwsWithEmAreaId) parameter
– if the pwsWithEmAreaId parameter is set to true, add and configure the
LNCEL Emergency area ID list (emAreaIdList) parameter value.

Expected outcome
are two mandatory transmissions of SIB 12 (and optionally for SIBs 2 and higher) within
each SI window.

g Note: Before activating the LTE2120: SIB Reception with Parallel Measurement Gaps
474, 479, 1114, 1119, 2394, or 2399, or
values: 1114, 1119, 2394, or 2399

89, 109, 129, 149, or

473, 478, 1113, 1118, 2393, 2398, or
1113, 1118, 2393, 2398

88, 108, 128, 148, or
– if tddSpecSubfConf is not 3, 4, 7, and eIcicMaxMutePattern is higher
than or equal to 3, and cellType is set to large, then csiRsSubfrConf
must be set to one of the following values: 28, 48, 68, 88, 108, 128, 148



29.4 Deactivating LTE2120: SIB Reception with Parallel

Measurement Gaps
Before you start
The Twofold transmission of SIBs per SI window (sib2xTransmit)
parameter is used for deactivation of SIBs 2 to 9. Modification of this parameter requires
object locking. The Activation ETWS support (actETWS) parameter is used for
deactivation of SIBs 10 and 11. The Activation CMAS support (actCMAS)
parameter is used for deactivation of SIBs 12.
Procedure

2 Deactivate the LTE2120: SIB Reception with Parallel Measurement Gaps feature.

d) Set the following parameter values to false:
• Activation CMAS support (actCMAS) – twofold transmisssion of SIB
12 is disabled
• Activation ETWS support (actETWS) – twofold transmission of SIBs
10 and 11 is disabled
e) Go to the LNCEL object.

window (sib2xTransmit) parameter value to false – twofold transmission of
SIB 2 to 9 is disabled
Expected outcome
The LTE2120: SIB Reception with Parallel Measurement Gaps feature is deactivated;
warning notifications are not sent; twofold transmission of SIB 2 and higher is disabled.

LTE15A Radio Resource Management and Telecom LTE2128: Uplink Intra eNodeB CoMP 8 RX with Softbit
Features Combination
30 LTE2128: Uplink Intra eNodeB CoMP 8 RX

with Softbit Combination
30.1 Description of LTE2128: Uplink Intra eNodeB CoMP

8 RX with Softbit Combination
Table 172 LTE2128 Summary of changes

Date of change Section Change description
02.07.2018 Functional description, Parameter actUlCoMp is
Activating, Deactivating replaced with actCoMp

The LTE2128: Uplink Intra eNodeB CoMP 8 RX with Softbit Combination feature
enhances previous implementations of the coordinated multipoint (CoMP) technique with
the use of 8 RX antennas and softbit combining. This solution further increases data rate
and throughput for cell-edge UEs and requires less processing power on the baseband
level than IQ combining.
Benefits
End-user benefits
An increase in service quality for the end user in a cell-edge region.
Operator benefits
An increase in throughput for cell-edge UEs by:
• several per cent when MU-MIMO is not enabled
• up to ten per cent when MU-MIMO is enabled
Requirements
Uplink coordinated multipoint technique in the LTE2128 feature
increases data rate and throughput for a UE by combining the signal of antennas from
serving cell and a chosen neighbor cell. This technique is called CoMP (coordinated
multipoint), and neighboring cells which operate on the same signal are in the scope of
one CoMP set. CoMP turns the inter-cell interference (ICI) into a useful signal, especially
at the cell borders where performance may be degraded.
If an uplink intra-eNB CoMP is enabled, the data sent by a cell-edge UE is received by
the antennas of its serving cell and also by the antennas of a corresponding neighboring
cell. In the case of the LTE2128 feature, it is possible to use 8 RX antennas in both cells.
The basic idea is shown in Figure 20: CoMP technique using 8 RX antennas.

LTE2128: Uplink Intra eNodeB CoMP 8 RX with Softbit LTE15A Radio Resource Management and Telecom
Combination Features
Receiving data from two different cells is possible due to soft bit combining of the
PUSCH data in order to receive the UL-SCH channel. Other physical uplink channels
(PRACH, PUCCH) will be received based on the serving cell's antennas. Right
conditions to activate the CoMP are indicated by the UE (by using dedicated A3 event).
Figure 20 CoMP technique using 8 RX antennas
eNBantenna
radiochannel NC
eNB
UE
SC servingcell
NC neighborcell
TX/RX RX
SC NC
CoMP set
supports 8 RX antennas in a cell, and the operator configures uplink CoMP set that
consists of maximum three cells (a cell can belong only to one CoMP set). It means that
one cell belonging to uplink CoMP set monitors up to two other cells. From these, the
serving cell can use one depending on the the UEs’ reported RSRP in the neighbor cells.
CoMP entering condition is:
RSRPneigh > RSRPserv + a3OffsetCoMp + hysA3OffsetCoMp
Location of radio modules in the LTE2128 feature

requires the cells within a CoMP set to be at a single site and span. Without the LTE641:
Distributed Sites feature, the maximum distance between the eNodeB and the radio
module is limited to 200 meters. With the LTE614 feature, the radio modules can be
positioned up to 1km apart, with the maximum difference in Doppler shift of 250Hz.
System impact

requires the LBT2134: Large User Plane Deployments feature to be activated. The
LTE2128 feature will provide higher gains if run in combination with the LTE1545: UL
MU-MIMO 8RX feature.
The following features are not supported together with the LTE2128: Uplink Intra eNodeB
CoMP 8 RX with Softbit Combination feature:
• LTE72: 4-way RX diversity
• LTE74: FSMD Flexi System Module
• LTE82: FSME High Capacity Flexi System Module
• LTE106: 6 Cell Support with One System Module
• LTE993: Cell Combination (Supercell)
Previous implementations of the uplink CoMP, which cannot be activated together with
the LTE2128: Uplink Intra eNodeB CoMP 8 RX with Softbit Combination feature:
• LTE1402: Uplink Intra-eNB CoMP
• LTE1691: Uplink Intra-eNB CoMP 4Rx
There is no impact on interfaces.

There is no impact on network management tools.

improves the cell-edge throughput and, to a certain extent, also the average cell
throughput. While a gain of up to 10 per cent is expected for the majority of the cell-edge
users under uplink CoMP reception, a few users may nevertheless experience a
(temporary) loss due to an inappropriate selection of a neighbor cell.
Management data
Sales information

LTE2128: Uplink Intra eNodeB CoMP 8 RX with Softbit Combination requirements,
alarms and faults, measurements and counters, KPIs, parameters, and sales information
Requirements


FDD TDD
System release Not supported TD-LTE15A
Alarms
There are no alarms related to the LTE2128: Uplink Intra eNodeB CoMP 8 RX with
Softbit Combination feature.

There are no faults related to the LTE2128: Uplink Intra eNodeB CoMP 8 RX with Softbit
Combination feature.
Commands
There are no commands related to the LTE2128: Uplink Intra eNodeB CoMP 8 RX with
Softbit Combination feature.

M8051C120 Average number of UEs LTE UE Quantity
considered by L3 RRM
for UL intra-eNB CoMP


KPI ID KPI name
LTE_5746a E-UTRAN Average number of UEs considered by L3 RRM for UL intra-eNB CoMP

Table 176 Existing key performance indicators related to LTE2128

KPI ID KPI name
LTE_5003a E-UTRAN Data Radio Bearer Setup Success Ratio
For KPI descriptions, see LTE Operating Documentation/Reference/Counters and Key

Performance Indicators.
Parameters

Full name Abbreviated name Managed Parent FDD/TDD
object Structure
UL CoMP mode ulCoMpMode ULCOMP - common
Uplink ulCoMpId ULCOMP - common
coordinated
multipoint
identifier
Uplink Comp Cell ulCoMpCellList ULCOMP - common
List
A3 measurement a3UlCoMpConfig ULCOMP - common
parameters for
UL CoMP
A3 offset for UL a3OffsetCoMp ULCOMP A3 common
CoMP measurement
parameters
for UL CoMP
(a3UlCoMpCon
fig)
Hysteresis A3 hysA3OffsetCoMp ULCOMP A3 common
offset RSRP measurement
intra-frequency parameters
for UL CoMP for UL CoMP
(a3UlCoMpCon
fig)
A3 time to a3TimeToTriggerC ULCOMP A3 common
trigger for UL oMp measurement
CoMP parameters
for UL CoMP
(a3UlCoMpCon
fig)
A3 report a3ReportInterval ULCOMP A3 common
interval for UL CoMp measurement
CoMP parameters
for UL CoMP
(a3UlCoMpCon
fig)

name object
Activate CoMP actCoMp LNBTS - common


Sales information

ASW Pool licence No
30.3 Activating and configuring LTE2128: Uplink Intra

eNodeB CoMP 8 RX with Softbit Combination
Before you start
Table 180: Parameters used for activating and configuring LTE2128: Uplink Intra eNodeB
CoMP 8 RX with Softbit Combination lists parameters used during activation and
configuration of the feature.
Table 180 Parameters used for activating and configuring LTE2128: Uplink Intra
eNodeB CoMP 8 RX with Softbit Combination
object locking
Activate CoMP (actCoMp) activation flag restart required
UL CoMP mode (ulCoMpMode) mandatory configuration restart required
A3 measurement parameters for mandatory configuration no
UL CoMP (a3UlCoMpConfig)
Uplink CoMP Cell List mandatory configuration restart required
(ulCoMpCellList)
The following features are not supported together with the LTE2128: Uplink Intra eNodeB
CoMP 8 RX with Softbit Combination feature:
• LTE72: 4-way RX diversity
• LTE74: FSMD Flexi System Module
• LTE82: FSME High Capacity Flexi System Module
• LTE106: 6 Cell Support with One System Module
• LTE993: Cell Combination (Supercell)
Previous implementations of the uplink CoMP, which cannot be activated together with
the LTE2128: Uplink Intra eNodeB CoMP 8 RX with Softbit Combination feature:
• LTE1402: Uplink Intra-eNB CoMP
• LTE1691: Uplink Intra-eNB CoMP 4Rx
The eNodeB must be configured with 8 RX paths and at least two cells. Additionally, all
cells that are in the same CoMP set (see Functional description) must have identical:

• carrier frequency (EARFCN)

• system bandwidth
• UL/DL subframe configuration
• special subframe configuration
Procedure

2 Activate the LTE2128 feature activation flag parameter.

d) Set the Activate CoMP (actCoMp) parameter value to fixedUlCoMp.
3 Configure at least one ULCOMP instance.

d) Right click the LNBTS object and choose ULCOMP
e) Set value of the Uplink coordinated multipoint identifier
f) Set the UL CoMP mode (ulCoMpMode) parameter value to
SoftBit_Combining.
g) Set the Uplink CoMP Cell List (ulCoMpCellList) parameter to
desired value.
h) Right click the ULCOMP object and create new A3 measurement
parameters for UL CoMP (a3UlCoMpConfig) structure.

30.4 Deactivating LTE2128: Uplink intra eNodeB CoMP 8

RX with softbit combination
Before you start
The Activate Uplink CoMP (actUlCoMP) parameter is used for deactivation.
Modification of this parameter requires an eNB restart.
Procedure

2 Deactivate the feature flag for LTE2128.

d) Set the Activate Uplink CoMP (actUlCoMP) parameter value to false.
Expected outcome
The LTE2128: Uplink intra eNodeB CoMP 8 RX with softbit combination feature is
deactivated in all cells and softbit combining is not used (ULCOMP instances may
remain with the configured content).

LTE15A Radio Resource Management and Telecom LTE2133: eICIC for HetNet eNode B Configurations
Features
31 LTE2133: eICIC for HetNet eNode B

Configurations
31.1 LTE2133: eICIC for HetNet eNode B Configurations

The LTE2133: eICIC for HetNet eNode B Configurations feature provides an enhanced
inter-cell interference coordination (eICIC) support for the following eNB configurations:
• eNBs hosting both the macro and small cells
• eNBs hosting only the small cells
• eNBs hosting only the macro cells
Benefits
End-user benefits
Operator benefits
This feature provides support for heterogeneous networks so that eICIC partnerships
can be established in the following scenarios:
• between macro and small cells which are hosted by the same eNB
• between multiple small cells in one eNB and either the same macro cell or individual
macro cells on another eNB
Functional overview
The LTE2133: eICIC for HetNet eNode B Configurations feature introduces the internal
X2 interface communication extensions for eICIC to enable:
• eICIC support between the macro and small cells located in the same eNB. Figure
21: Scenario 1 shows an example where low power remote radio heads (RRHs) are
connected to the same system module with the overlapping high power RRH.
Figure 21 Scenario 1
low
power
eNB RRH
fiber
eICIC
area

LTE2133: eICIC for HetNet eNode B Configurations LTE15A Radio Resource Management and Telecom
Features
g Note: The high power RRHs are used in the macro cells while the low power
RRHs are used in the small cells.
• eICIC support between the macro cell hosted by an eNB and the small cells hosted
by another eNB. Figure 22: Scenario 2 shows an example where a high power RRH
and the low power RRHs are connected to different system modules linked via X2
interface.
low
eNB1 power eNB2
RRH
fiber
eICIC
fiber area
high
power
RRH
X2
• eICIC support for the macro and small cells configured in both scenarios. Figure 23:
Scenario 3 shows an example where a high power RRH and some of the low power
RRHs are connected to the same system module and other low power RRHs are
connected to a different system module linked via X2 interface.
eICIC high
area power
#2 RRH
fiber
fiber
eNB1 low eNB2
power
RRH eICIC
area
#1
fiber
high fiber
power
RRH
X2
g Note: This scenario can be extended to include additional permutations such as

multiple macro cells of eNB1 in eICIC partnership with the small cells of eNB2.
Note that only one active eICIC partnership is allowed per small cell.
There is a limitation imposed by an X2 reset procedure in any scenario where multiple

eICIC areas use the same X2 link. This procedure is used in recovering from cases such
as supervision timer expiry, and missing and unexpected responses. In this scenario, it is
possible that one small cell terminates all eICIC partnerships for all involved eICIC areas.

Features
System impact
The LTE2133: eICIC for HetNet eNode B Configurations feature is enabled together with
the LTE1496: eICIC - micro feature.
g Note: The eICIC feature activation is prohibited for small cells with carrier aggregation
(CA) enabled. Simultaneous support for eICIC and CA in small cell eNBs will be
available on a later release.
Phase synchronization is required for the LTE2133: eICIC for HetNet eNode B
Configurations feature and can be achieved by activating one of the following features:
• LTE80: GPS Synchronization
• LTE891: Timing over Packet with Phase Synchronization
• LTE1710: Sync Hub Direct Forward
g Note: For phase synchronization, the Network synchronization

mode (btsSyncMode) parameter value must be set to PhaseSync.
This feature introduces the X2 interface for eICIC functions over the optical fiber cable.



LTE2133: eICIC for HetNet eNode B Configurations requirements, alarms and faults,
Requirements

FDD TDD

LTE2133: eICIC for HetNet eNode B Configurations LTE15A Radio Resource Management and Telecom
Features

FDD TDD
OMS Support not needed Not supported
g Note: The small cells can also be configured on the Flexi Multiradio 10 BTS.
Alarms
There are no alarms related to the LTE2133: eICIC for HetNet eNode B Configurations
feature.

There are no faults related to the LTE2133: eICIC for HetNet eNode B Configurations
feature.
Commands
There are no commands related to the LTE2133: eICIC for HetNet eNode B
Configurations feature.

There are no measurements or counters related to the LTE2133: eICIC for HetNet
eNode B Configurations feature.

There are no key performance indicators related to the LTE2133: eICIC for HetNet
eNode B Configurations feature.
Parameters

d object
ECGI of the eICIC eIcicPartnerEc LNCEL - FDD
macro partner gi
Identity of the eNB enbId LNCEL eIcicPartnerEc FDD
in the ECGI of the gi
eICIC macro partner
Identity of the lcrId LNCEL eIcicPartnerEc FDD
cell in the ECGI of gi
the eICIC macro
partner
MCC in the ECGI of mcc LNCEL eIcicPartnerEc FDD
the eICIC macro gi
partner

Features

d object
MNC in the ECGI of mnc LNCEL eIcicPartnerEc FDD
the eICIC macro gi
partner
MNC length in the mncLength LNCEL eIcicPartnerEc FDD
ECGI of the eICIC gi
macro partner

Documentation/Reference/Parameters document.
Sales information
Table 183 Sales information

element
ASW - No

LTE2149: Supplemental Downlink Carrier LTE15A Radio Resource Management and Telecom
Features
32 LTE2149: Supplemental Downlink Carrier
32.1 Description of LTE2149: Supplemental Downlink

Carrier
The LTE2149: Supplemental Downlink Carrier feature introduces supplemental cells only
with downlink channels and not with the physical hybrid-ARQ indicator channel (PHICH).
A supplemental cell can be used only as a secondary cell (SCell) in combination with
downlink carrier aggregation for LTE.
Benefits
End-user benefits
The LTE2149: Supplemental Downlink Carrier feature provides the end-user with an
improved peak and average UE downlink throughput, enhancing the already utilized
carrier aggregation features.
Operator benefits
Using the carrier aggregation feature, the LTE2149: Supplemental Downlink Carrier
feature boosts downlink capacity by utilizing an unpaired spectrum as an additional
carrier along with the originally paired downlink and uplink carriers. It has a maximum of
30 MHz aggregated bandwidth for a two-band combination downlink carrier and a
maximum of 50 MHz aggregated bandwidth for a three-band combination downlink
carrier.
Introduction to carrier aggregation in relation to LTE2149
Carrier aggregation (CA) increases the bandwidth by combining two or more component
carriers (CC). The individual CCs can be of different bandwidths. Aggregation is possible
by using contiguous CCs within the same operating frequency band (intra-band
contiguous). Non-contiguous aggregation is possible either as intra-band with separated
CCs of the same operating frequency band, or as inter-band when CCs are from
different operating frequency bands.
A supplementary cell is a cell operating in the carrier aggregation mode only with
downlink channels and not with the physical hybrid-ARQ indicator channel (PHICH) (see
Figure 24: A supplementary cell used as a secondary cell (SCell) in carrier aggregation).

LTE15A Radio Resource Management and Telecom LTE2149: Supplemental Downlink Carrier
Features
Figure 24 A supplementary cell used as a secondary cell (SCell) in carrier

aggregation
PCell
PDCCH
PDSCH
PHICH
ULChannels
SCell
PDCCH
PDSCH
NoPHICH
NoULChannels
CarrierAggregation
Feature deployment
The LTE2149: Supplemental Downlink Carrier feature allows utilizing an unpaired
spectrum in band 29 with a cell bandwidth of 5 or 10 MHz. The feature supports up to
400 configured and activated secondary cell (SCell) UEs in a supplemental cell.
The LTE2149: Supplemental Downlink Carrier feature supports the following two-band
combinations for supplemental cells:
• band 2 + band 29 (bandwidth combination set: 0, 1, 2)

• band 4 + band 29 (bandwidth combination set: 0, 1, 2)
• band 30 + band 29 (bandwidth combination set: 0)
with a maximum of 30 MHz aggregated bandwidth.

The LTE2149: Supplemental Downlink Carrier feature supports the following three-band
combinations for supplemental cells:
• band 2 + band 29 + band 30 (bandwidth combination set: 0)

with a maximum of 50 MHz aggregated bandwidth.

The supplemental cell cannot act as a primary cell (PCell). To avoid camping UEs on the
supplemental cell it is declared as barred in system information block 1 (SIB1). System
information block 3 (SIB3) is permamently disable and higher SIBs are conditionally
present (if provisioned they can be scheduled). The supplemental cell cannot be used as
a mobility target. Positioning reference symbols can be configured for supplemental
cells.
System impact
The LTE2149: Supplemental Downlink Carrier feature depends on:

Features

• LTE1562: Carrier Aggregation for Multi-carrier eNBs
because the carrier aggregation is a precondition.
The feature also depends on LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz
and LTE1804: Downlink Carrier Aggregation 3CC - 60 MHz as a precondition for the
three-band combination carrier.
The feature depends on LTE2006: Flexible SCell Selection defining SCell selection for
the supplemental downlink carrier.
The feature must be activated together with LTE1089: Downlink Carrier Aggregation - 20
MHz and LTE1332: Downlink Carrier Aggregation - 40 MHz.
The following features cannot be enabled for supplemental cells:
• LTE1542: FDD Supercell, LTE1709 Liquid Cell

• any uplink related features
• LTE1117: LTE MBMS
• cell configurations with 4 TX
• LTE1113: eICIC - Macro and LTE1496: eICIC - Micro
• LTE784: ANR Inter-RAT GERAN, LTE556: ANR Intra-LTE, Inter-frequency - UE-
based and LTE908: ANR Inter-RAT UTRAN - Fully UE-based
• any kind of intra-frequency, inter-frequency or IRAT handover
no impact on interfaces

The LTE2149: Supplemental Downlink Carrier feature impacts network management
tools as follows:
• Uu:
– no uplink channels
– no physical hybrid-ARQ indicator channel
• S1/X2:
– S1 and X2 inactive for a user-data transfer
• BTSOM/NWI3:
– unidirectional radio frequency hardware

The LTE2149: Supplemental Downlink Carrier feature can improve peak and mean-user
download throughput of non-GBR UEs with the secondary cell (SCell) configured.
Additionally, a system capacity gain is also expected. The actual gain depends on many
factors; for example, network's load, level of GBR traffic, parametrization of the
scheduling fairness factor, but it can be doubled for bandwidth combinations with an
equal bandwidth of two involved cells.

Features

LTE2149: Supplemental Downlink Carrier requirements, parameters, and sales
information
Requirements

FDD TDD
Additional requirements
The LTE2149: Supplemental Downlink Carrier feature uses new, dedicated radio
frequency modules supporting only downlink on band 29:
• LTE2143: FRBE Flexi RRH 2TX 2RX 750 2TX 720
• LTE2266: FRBG Flexi RRH 2TX 4RX 730 2TX 720
Because of 3GPP limitation for supplementary downlink carrier cell bandwidth on band
29 must be of 5 or 10 MHz.
Alarms
There are no alarms related to the LTE2149: Supplemental Downlink Carrier feature.

There are no faults related to the LTE2149: Supplemental Downlink Carrier feature.
Commands
There are no commands related to the LTE2149: Supplemental Downlink Carrier feature.

Features
There are no measurements or counters related to the LTE2149: Supplemental Downlink

Carrier feature.

There are no key performance indicators related to the LTE2149: Supplemental
Downlink Carrier feature.
Parameters

name object
Activate actSdlc LNCEL_FDD - FDD
supplemental
downlink carrier
Supplemental DL sdlcFreqList LNBTS_FDD - FDD
carrier frequency
list
Ending DL EARFCN in endEarfcnDl LNBTS_FDD sdlcFreqList FDD
suppl. DL carrier
frequency list
Starting DL EARFCN startEarfcnDl LNBTS_FDD sdlcFreqList FDD
in suppl. DL
carrier frequency
list

Activate actCRAN LNBTS - FDD
Centralized RAN
EUTRA frequency dlCarFrqEut IRFIM - FDD
value
Activate actSdlc LNCEL_FDD - FDD
supplemental
downlink carrier
Maximum number of maxNumRrc LNCEL_FDD - FDD
RRC connections
Maximum number RRC maxNumRrcEmer LNCEL_FDD - FDD
emergency gency
PDCCH LA UL DL pdcchUlDlBal LNCEL - FDD
allocation balance
initial value
eUTRA frequency redirFreqEutr MODRED - FDD
a
eUTRA frequency redirFreqEutr MORED - FDD
a
eUTRA frequency redirFreqEutr REDRT - FDD
a

Features

Eutra carrier info eutraCarrierI LNHOIF - FDD
nfo
Resource list resourceList LCELL - FDD
For parameter descriptions, see LTE Radio Access Operating Documentation >
Reference > Parameters.
Sales information

ASW - No
32.3 Activating and configuring LTE2149: Supplemental

Downlink Carrier
Before you start
Table 188: Parameters used for activating and configuring LTE2149: Supplemental
Downlink Carrier lists parameters used for the activation and configuration of the
LTE2149: Supplemental Downlink Carrier feature.
Table 188 Parameters used for activating and configuring LTE2149: Supplemental
Downlink Carrier
object locking
Activate supplemental downlink activation flag restart
carrier (actSdlc)
Supplemental DL carrier frequency mandatory configuration no
list (sdlcFreqList)
PDCCH LA UL DL allocation mandatory configuration no
balance initial value
(pdcchUlDlBal)
The feature must be activated together with LTE1089: Downlink Carrier Aggregation - 20
MHz and LTE1332: Downlink Carrier Aggregation - 40 MHz - The value of the LNBTS:
parameter must be set to true.
The feature uses new, dedicated radio frequency modules supporting only downlink on
band 29:
• LTE2143: FRBE Flexi RRH 2TX 2RX 750 2TX 720
• LTE2266: FRBG Flexi RRH 2TX 4RX 730 2TX 720

Features
Additionally, this feature can be enabled if and only if hardware is configured for downlink
operation only.
This feature requires two or three properly configured cells, one of which will act as a
supplemental downlink carrier (SDLC) cell.
In order to ensure the allocation of minimal resources is used for not transmitted PHICH,
it is recommended to use default values for the PHICH-related management LNCEL
parameters:
• PHICH duration (phichDur) - Normal
• PHICH resource (phichRes) - N=1/6
• Downlink PHICH transmission power boost (dlPhichBost) - 0dB
Ensure that parameters that are not used on the SDLC (i.e. managing the uplink
operation) are configured and provide benign settings, not interfering with regular
operation, for the following LNCEL _FDD parameters:
• Add GBR-DRB traffic for time critical reason handover
(addGbrTrafficTcHo)
• Add GBR-DRB traffic for radio reason handover
(addGbrTrafficRrHo)
• Add number DRB radioReasHo (addNumDrbRadioReasHo)
• Add number DRB timeCriticalHo (addNumDrbTimeCriticalHo)
• Additional active UE with reason radio reason handover
(addAUeRrHo)
• Additional active UE with reason time critical handover
(addAUeTcHo)
• Add number QCI1 DRB for radioReasHo
(addNumQci1DrbRadioReasHo)
• Add number QCI1 DRB for timeCriticalHo
(addNumQci1DrbTimeCriticalHo)
• Max number act DRB (maxNumActDrb)
• Max number carrier aggr configured UEs (maxNumCaConfUe)
• Max number carrier aggr configured UEs 3 Carriers
(maxNumCaConfUe3c)
• Max number Carrier Aggr configured UEs double carrier
(maxNumCaConfUeDc)
• Max number QCI1 DRBs (GBRs) (maxNumQci1Drb)
• Maximum bitrate selector (mbrSelector)
• Maximum bitrate uplink (maxBitRateUl)
• Maximum bitrate uplink (maxBitRateDl)
• Maximum GBR-DRB Traffic Limit (maxGbrTrafficLimit)
• Maximum number of active UEs (maxNumActUE)
• Maximum number RRC emergency (maxNumRrcEmergency)
g Note: There are no new, dedicated consistency checks for the LTE2149: Supplemental
Downlink Carrier feature in NetAct or BTSSM preventing nonfunctional configuration of
parameters.

Features
Procedure

2 Reconfigure cell resources.

b) For the SDLC cell, reconfigure the ANT object's TX/RX usage mapping to TX (to
support band 29).
c) Configure the MIMO mode.
3 Configure downlink carriers.
a) Go to the LTE Carriers page.

b) For each cell, configure the Bandwidth as required.
c) For each cell, configure appropriate EARFCN objects.
4 If no CAREL instance exists, create and configure at least one, in any of the non-
supplemenatal downlink carrier cells, which has the supplemental downlink carrier cell as
the target cell.

e) On the selected LNCEL object, create a new CAREL instance.
5 Configure CAREL instance.
In the CAREL instance, configure the following parameters to desired values:

a) Carrier aggregation relation identifier
b) Local cell resource ID of cell to be aggregated
c) SCell priority
d) BTS ID of the parent eNB of the cell to be aggregated
6 Prohibit outgoing mobility toward the cells on supplemental DL carrier.

Features


you need to select the LNBTS/LNBTS_FDD object.
d) On the selected LNBTS object, create a new Supplemental DL carrier
frequency list (sdlcFreqList) instance.

you need to select the LNBTS/LNBTS_FDD object.
e) Select the Supplemental DL carrier frequency list instance.
f) Set the Ending DL EARFCN in suppl. DL carrier frequency
list (endEarfcnDl) parameter as required.
g) Set the Starting DL EARFCN in suppl. DL carrier frequency
list (startEarfcnDl) parameter as required.
g Note: The Supplemental DL carrier frequency list parameter will

also be used by an eNB which does not provide a supplemental downlink carrier,
so it is vital to configure this list properly.
There are no new, dedicated consistency checks for the LTE2149: Supplemental
Downlink Carrier feature in NetAct or BTSSM preventing nonfunctional
configuration of parameters.
7 Set PDCCH LA UL DL allocation balance initial value to 0 for the SDLC

cell.

d) Select the LNCEL object related to the SDLC cell.
e) Set the PDCCH LA UL DL allocation balance initial
value (pdcchUlDlBal) parameter's value to 0.
8 Ensure that SDLC cell's administrative state is unlocked.

d) Select the LNCEL object related to the SDLC cell.
e) Ensure that Administrative state (administrativeState) parameter
status is set to the unlocked value.
Expected outcome

Features
The eNB is restarted, the LTE2149: Supplemental Downlink Carrier feature is activated,
and the LNCEL: Activate supplemental downlink carrier (actSdlc)
parameter for SDLC cell is automatically set to true.
The SDLC cell is unlocked, and the eNB can start to use the cell on the supplemental
downlink carrier in carrier aggregation as an SCell.
32.4 Deactivating LTE2149: Supplemental Downlink

Carrier
Before you start
The LCELL: Resource list (resourceList) parameter is used for deactivation.
Modification of this parameter requires object locking.
Procedure

2 Reconfigure cell resources.

b) For the SDLC cell, unselect the ANT objects.
c) Depending on the radio frequency modules' hardware capability:
• Reconfigure the ANT objects to move the cell to a different band, supported
by radio frequency module.
OR
• Delete the local cell related to the SDLC cell.
g Note: With SDLC cell dedicated radio frequency hardware modules, it is not
possible to keep the cell on band 29 after deactivating the
LTE2149: Supplemental Downlink Carrier feature due to hardware restrictions.
Expected outcome

Features
The LTE2149: Supplemental Downlink Carrier feature is deactivated. The SDLC cell is
deleted, or if the cell is reconfigured into a different band, the LNCEL: Activate
supplemental downlink carrier (actSdlc) parameter for the cell is
automatically set to false, and the cell cannot be used as an SDLC cell.

LTE15A Radio Resource Management and Telecom LTE2168: Additional Carrier Aggregation Band
Features Combinations - II
33 LTE2168: Additional Carrier Aggregation

Band Combinations - II
The LTE2168: Additional Carrier Aggregation Band Combinations - II feature supports
additional downlink (DL) carrier aggregation (CA) band combinations.
Benefits
End-user benefits
CA supports more band combinations that bring higher peak data rates for the users in
the network.
Operator benefits
This feature offers the operator additional DL CA band combinations.
In addition to the allowed CA band combinations from the LTE1089: Downlink Carrier
Aggregation - 20 MHz, LTE1332: Downlink Carrier Aggregation - 40 MHz, and LTE2033:
Additional Carrier Aggregation Band Combinations - I features, the LTE2168: Additional
Carrier Aggregation Band Combinations - II feature allows the Flexi Multiradio 10 BTS to
support:

• band 2 + band 2 (non-contiguous, contiguous)
• band 4 + band 5 (bandwidth combination set: 0 and 1)
• band 7 + band 7 (bandwidth combination set: 1, contiguous)
• band 7 + band 8
g Note: The bandwidth combination set is 0 if not indicated. For more details, see the
LTE1089: Downlink Carrier Aggregation - 20 MHz and
LTE1332: Downlink Carrier Aggregation - 40 MHz feature descriptions.
System impact

LTE2168: Additional Carrier Aggregation Band LTE15A Radio Resource Management and Telecom
Combinations - II Features
The LTE2168: Additional Carrier Aggregation Band Combinations - II feature is enabled

together with the LTE1089: Downlink Carrier Aggregation - 20 MHz and LTE1332:
Downlink Carrier Aggregation - 40 MHz features. These features have the same
activation flag, which is the actDLCAggr parameter.



Requirements

FDD TDD
Flexi Multiradio 10 Indoor BTS FL15A Not supported
Nokia AirScale BTS Support not required Not supported
Alarms
There are no alarms related to the LTE2168: Additional Carrier Aggregation Band
Combinations - II feature.

There are no faults related to the LTE2168: Additional Carrier Aggregation Band

Commands
There are no commands related to the LTE2168: Additional Carrier Aggregation Band

There are no measurements or counters related to the LTE2168: Additional Carrier
Aggregation Band Combinations - II feature.

There are no key performance indicators related to the LTE2168: Additional Carrier
Aggregation Band Combinations - II feature.
Parameters
There are no parameters related to the LTE2168: Additional Carrier Aggregation Band
Sales information

33.2 Activating and configuring LTE2168: Additional

Carrier Aggregation Band Combinations - II
Before you start
Setting the Activation of downlink carrier aggregation (actDLCAggr)
parameter value to true activates the feature. Modification of this parameter requires
evolved Node B (eNB) restart.
The LTE2168: Additional Carrier Aggregation Band Combinations - II feature is enabled
together with the LTE1089: Downlink Carrier Aggregation - 20 MHz and LTE1332:
Downlink Carrier Aggregation - 40 MHz features. These features use the same activation
flag.
Procedure


LTE2168: Additional Carrier Aggregation Band LTE15A Radio Resource Management and Telecom
Combinations - II Features



factor (caSchedFairFact) parameter must be configured when the
3 (Optional) Create a new CADPR object.


Expected Outcome
The LTE2168: Additional Carrier Aggregation Band Combinations - II feature is activated
in the eNB.

33.3 Deactivating LTE2168: Additional Carrier

Aggregation Band Combinations - II
Before you start
Setting the Activation of downlink carrier aggregation (actDLCAggr)
parameter value to false deactivates the feature. Modification of this parameter requires
eNB restart.
Procedure



Expected outcome
The LTE2168: Additional Carrier Aggregation Band Combinations - II, LTE2033:
Additional Carrier Aggregation Band Combinations – I, LTE1332: Downlink Carrier
Aggregation - 40 MHz, and LTE1089: Downlink Carrier Aggregation - 20 MHz features
are deactivated in the eNB.

LTE2208: eICIC Enhancements - micro LTE15A Radio Resource Management and Telecom
Features
34 LTE2208: eICIC Enhancements - micro

The LTE2208: eICIC Enhancements – micro feature introduces the following functions:
• Handling of evolved node B (eNB) synchronization loss during enhanced inter-cell
interference coordination (eICIC) operation
• Dedicated system information block type 1 (SIB1) signaling for R11 user equipment
(UEs) connected to the small cell.
Benefits
End-user benefits
This feature avoids eICIC performance degradation caused by phase synchronization
error in the eICIC area.
Operator benefits
This feature enhances eICIC implementation for the Flexi base station (BTS) by handling
the loss of eNB synchronization.
Functional overview
The eICIC feature requires synchronization on the subframe level because of the
application of the almost blank subframe (ABS). The maximum tolerable phase error for
eICIC is 5 μs. The LTE2208: eICIC Enhancements - micro feature handles the loss of
eNB synchronization as follows:
• The LTE1496: eICIC - micro feature is enabled in the small cell and an eICIC
partnership is established in the macro cell.
• If the eNB looses all the synchronization reference signals, it will continue to operate
in holdover mode.
• The eNB continuous to monitor the estimated phase error.
• When the estimated phase error exceeds 5 μs for more than two minutes, an alarm
will be raised.
• Synchronization is lost in the eICIC operation.
• The eICIC partnership is terminated.
The ABS pattern is switched off after all the eICIC partnerships are terminated. The
eICIC feature remains enabled in the small cell and the eICIC partnership can be
established again and operation will be resumed once the synchronization is recovered.
The requests for eICIC partnership establishment are rejected as long as the phase error
remains higher than 5 μs.
The LTE2208: eICIC Enhancements - micro feature also deals with the dedicated SIB1
signaling for R11 UEs that are connected to the small cell. It handles the SIB1 update
case for UEs located more than 6 dB in the small-cell cell range expansion (CRE).
Dedicated signaling for the SIB1 update is sent when there is a modification in the SIB1
content. The updates are sent periodically to ensure that CRE UE receives the dedicated
signaling. The 6 dB CRE limit is considered the safe value for UEs to read the PDCCH
when receiving SIB1.

LTE15A Radio Resource Management and Telecom LTE2208: eICIC Enhancements - micro
Features
The small cell CRE UEs encounter a high inter-cell interference from the macro cell
when decoding SIB1 data on the PDCCH. However, because of the application of ABS,
the PDSCH is blanked in the macro cell. This advantage, together with the R11 UE
capability, is used to update SIB1 through dedicated RRC signaling to R11 UEs located
more than 6 dB in the small cell CRE. The small cell eNB reconfigures all qualified UEs.
System impact
This feature is enabled together with LTE1496: eICIC - micro feature.
This feature affects the following features:
• LTE494: Commercial Mobile Alert System

g Note: The specific time constraints of Commercial Mobile Alert System (CMAS)
and Earthquake and Tsunami Warning System (ETWS) must be kept during the
UE bulk reconfiguration procedure following the SIB1 modification.


• provides the necessary failure handling to avoid eICIC performance degradation

when phase synchronization error exceeds 5 μs
• supports the SIB1 updates to be sent through the dedicated RRC signaling on the
PDSCH for R11 UEs

LTE2208: eICIC enhancements - micro requirements, alarms and faults, commands,
Requirements

FDD TDD

LTE2208: eICIC Enhancements - micro LTE15A Radio Resource Management and Telecom
Features

FDD TDD
NetAct Support not required Support not required
UE • 3GPP R10 UE capabilities • 3GPP R10 UE capabilities
• 3GPP R11 UE capabilities • 3GPP R10 UE capabilities
Alarms
There are no alarms related to the LTE2208: eICIC enhancements - micro feature.

Fault Fault name Reported alarms
ID
Alarm Alarm name
ID
6280 Phase error exceeds 5 s 7651 BASE STATION OPERATION
limit DEGRADED
Commands
There are no commands related to the LTE2208: eICIC enhancements - micro feature.

There are no measurements or counters related to the LTE2208: eICIC enhancements -
micro feature.

There are no key performance indicators related to the LTE2208: eICIC enhancements -
micro feature.
Parameters
There are no parameters related to the LTE2208: eICIC enhancements - micro feature.
Sales information


LTE15A Radio Resource Management and Telecom LTE2305: Inter-eNodeB Carrier Aggregation for 2
Features Macro eNodeBs
35 LTE2305: Inter-eNodeB Carrier Aggregation

for 2 Macro eNodeBs
The LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature enables
the Flexi Multiradio BTS to support inter-evolved Node B (eNodeB) Carrier Aggregation
(CA) between two macro eNodeBs.
Benefits
End-user benefits
Operator benefits
This feature enables the operator to support CA across two system modules. This
means that there is a larger cell configuration per cluster site (for example, 4Rx UL
CoMP and 3CC CA are in parallel).
Functional overview
The LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature allows DL
CA for cells that are hosted in two different co-located macro eNodeBs. This is needed to
support large configurations that require CA across multiple eNodeBs. The eNodeBs are
connected together with a sync and a serial rapid I/O (SRIO) cable. The sync cable
provides synchronization of the information required to keep the two eNodeBs in phase
sync. The SRIO cable is used for signaling messages and bearer data transfer between
the eNodeBs for CA. The interconnected eNodeBs can still act as an independent
eNodeB toward the core network, other eNodeBs, and the LTE OMS or NetAct. This
feature is activated using the Activate inter-eNB DL carrier aggregation
(actInterEnbDLCAggr) parameter.
CA cluster
The eNBs connected together for the purpose of inter-eNB CA are referred to as a CA
cluster. The CA cluster is loosely coupled so that if one eNB fails, the other eNB remains
operational; or if the SRIO cable fails, both eNBs remain operational, but the inter-eNB
CA is disabled. An alarm is introduced to indicate an SRIO link outage.
The following changes are introduced in the eNB CA cluster management as compared
to the management of individual eNBs:
• The eNB software interface versions must be compatible within the eNB CA cluster.
• The CA cluster must be configured by assigning a common CA cluster ID and a
unique CA cluster member ID to each eNB in the CA cluster.
• The value of the set of parameters for the LTE2305: Inter-eNodeB Carrier
Aggregation for 2 Macro eNodeBs feature must be consistent between all eNBs in
the CA cluster.

LTE2305: Inter-eNodeB Carrier Aggregation for 2 LTE15A Radio Resource Management and Telecom
Macro eNodeBs Features
The operator configures the CA cluster topology (Carrier aggregation cluster ID

parameter) using the NetAct Configurator tools. This topology identifies which eNBs are
connected together in the CA cluster. The operator has the option to perform consistency
check using CM Analyzer in the NetAct Configurator.
In the NetAct Configurator, a new CM Analyzer Nokia-defined rule set
(Nokia.InterENodeBCarrierAggregation) is introduced for the LTE2305: Inter-eNodeB
Carrier Aggregation for 2 Macro eNodeBs feature to verify the consistency of some of
the parameters between all eNBs in the CA cluster. For more details about the rules, see
the rule descriptions in the CM Analyzer application user interface.
Parameter inconsistency alarm

Each eNodeB in the CA cluster raises the
EFaultId_InterEnbCaParamsInconsistencyAl alarm if the Activate inter-
eNB DL carrier aggregation (actInterEnbDLCaggr) parameter is set to
true and the required parameters between the eNodeBs are inconsistent. The activation
of the new configuration in each eNodeB does not happen at the same time, and
therefore it is possible that the alarm is raised for a short-time interval. This indicates the
transient period when the inter-eNodeB CA is disabled because the eNodeBs are not
synchronized with consistent parameters.
The alarm persists in a scenario where the configuration of the parameters between the
eNodeBs in the CA cluster is inconsistent. In this case, the erroneous configuration must
be identified using the CM Analyzer check or with the information given in the alarm. If
the CM Analyzer check does not report a consistency error, the erroneous configuration
needs to be identified manually. Once the error is identified, the configuration plan needs
to be corrected accordingly and provisioned to the eNodeB that has the error. The nature
of the plan provisioning operation causes the alarm to persist until the plan is
successfully activated to each eNodeB in the CA cluster. For handling issues related on
plan provisioning operation, see the NetAct Configurator documentation.
Required cell configurations

The CA cluster of two FSMFs and four FBBCs supports the following:
• up to 6 5/10 MHz cells with 2Tx/Rx configuration are supported together with up to 9
5/10 MHz cells with 4Tx/4Rx configuration (at most, 6 out of 9 cells with 4Tx/4Rx can
support UL CoMP 4Rx)
• up to 3 5/10 MHz cell with 2Tx/Rx configuration are supported together with up to 3
5/10 MHz cell with 4Tx/4Rx configuration and 3 15/20 MHz cell with 4Tx/4Rx
configuration (all 6 cells with 4Tx/4Rx can support UL CoMP 4Rx)
5/10 MHz cell with 4Tx/4Rx configuration and 3 15/20 MHz cell with 4Tx/4Rx
configuration (all 6 cells with 4Tx/4Rx can support UL CoMP 4Rx)
• up to 3 5/10 MHz cell with 2Tx/Rx configuration are supported together with up to 9
5/10 MHz cells with 4Tx/4Rx configuration (at most, 6 out of 9 cells with 4Tx/4Rx can
support UL CoMP 4Rx)
5/10 MHz cells with 4Tx/4Rx configuration and 3 15/20 MHz cell with 4Tx/4Rx
configuration (at most, 6 out of 9 cells with 4Tx/4Rx can support UL CoMP 4Rx)

The LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature supports
band 2, band 4, band 5, band 12, band 17, band 29, and band 30 band combinations.
For more information about the configurations supported by this feature, see LTE Base
Stations Supported Configurations.
System impact
At least one of the following CA features must be activated:
The LTE2006: Flexible SCell Selection feature must be enabled in case of a flexible
secondary cell (SCell) selection.
The LTE1710: Sync Hub Direct Forward feature must be enabled to forward the
synchronization signal from one eNodeB to another eNodeB.
The configurations of the following features are supported:
• LTE1746: LTE Extended Configurations Up to 6 Frequency Bands
• LTE2019: Advanced Dual Carrier Operation within Same RF Unit
• LTE2172: BTS Configurations Optimized for Distributed RRH Deployment
• LTE2168: Additional Carrier Aggregation Band Combinations – II
• LTE2149: Supplemental Downlink Carrier
The LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature does not
support the following features:
• LTE2091: FDD Supercell Extension
• The LTE1195: FHCC Flexi 850 Repeater Interface Unit (RIU)
The following features are not supported in the LTE2305: Inter-eNodeB Carrier
Aggregation for 2 Macro eNodeBs feature:
• LTE1367: Automatic Cell Combination Assignment for Carrier Aggregation
• LTE1951: Automatic Configuration Support for CA for Multi-carrier eNBs
This feature affects the SRIO interface, which is the connection between the two macro
eNBs. New and existing messages are on this interface. These new messages are for
inter-radio resource operation and maintenance (RROM) communication and serve the
following purposes:
• validating parameter consistency for inter-eNB CA
• validating of SW consistency for the eNBs in the CA cluster
• obtaining SCell parameters as required by the primary cell (PCell)
• exchanging addressing information that permits inter-cell communication

• sending bearer data from the SCell to the PCell

This feature affects the following network elements:
• eNodeB
• NetAct

This feature enhances the capacity that can support CA using three component carriers
with three sectors and an UL CoMP, where some of the cells are operating in 4Tx/4Rx
configuration.

Requirements

FDD TDD
Flexi Multiradio 10 Indoor BTS FL15A Not supported
Nokia AirScale BTS Support not required Not supported
Alarms
There are no alarms related to the LTE2305: Inter-eNodeB Carrier Aggregation for 2
Macro eNodeBs feature.


Fault Fault name Reported alarms
ID
Alarm Alarm name
ID
6282 Inter eNB CA parameter(s) 7651 BASE STATION OPERATION
inconsistency in between DEGRADED
eNBs
6283 Inter eNB SW inconsistency 7651 BASE STATION OPERATION
in between cluster members DEGRADED
6284 Inter eNB communication 7651 BASE STATION OPERATION
failure DEGRADED
4262 SRIO link outage 7651 BASE STATION OPERATION
DEGRADED
4263 SRIO domain ID collision 7651 BASE STATION OPERATION
DEGRADED
Commands
There are no commands related to the LTE2305: Inter-eNodeB Carrier Aggregation for 2
Macro eNodeBs feature.

There are no measurements or counters related to the LTE2305: Inter-eNodeB Carrier
Aggregation for 2 Macro eNodeBs feature.

There are no key performance indicators related to the LTE2305: Inter-eNodeB Carrier
Aggregation for 2 Macro eNodeBs feature.
Parameters

d object
BTS ID of the lnBtsId CAREL - common
parent eNB of the
cell to be
aggregated
Activate inter-eNB actInterEnbDLC LNBTS - common
DL carrier Aggr
aggregation
Carrier aggregation caClusterId LNBTS - common
cluster ID
Carrier aggregation caClusterMembe LNBTS - common
cluster member ID rId

Sales information


35.2 Activating and configuring LTE2305: Inter-eNodeB

Carrier Aggregation for 2 Macro eNodeBs
Before you start
g Note: To be able to use the inter-eNB CA functionality, the operator must ensure
compatibility (SW and parameters) in the two eNBs. Otherwise, activation of the feature
could still be possible, but an alarm or warning might be raised and the inter-eNB CA
feature might not be enabled.
The Activate inter-eNB DL carrier

aggregation (actInterEnbDLCAggr) parameter activates the feature. Modification
of this parameter does not require an eNodeB restart or object locking.
Table 198 Parameters used for activating and configuring the LTE2305: Inter-eNodeB
Carrier Aggregation for 2 Macro eNodeBs feature
Parameter Purpose Requires eNodeB restart or
object locking
Activate inter-eNB DL activation flag No
carrier aggregation
(actInterEnbDLCAgg
r)
Carrier aggregation mandatory configuration eNodeB restart
cluster ID
(caClusterId)
Carrier aggregation mandatory configuration eNodeB restart
cluster member ID
(caClusterMemberId
)
At least one of the following CA features must be activated/configured before the

activation of the LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs
feature:
g Note: For more information about feature dependencies, see

The eNodeB software interface versions must be compatible within the eNodeB CA
cluster. The eNodeBs must be connected together with a sync and SRIO cable. The
SRIO cable (6 Gbps link) must not exceed 25 meters and the sync cable (2-meter HDMI

cable) is also defined to a short distance. The CM Analyzer is used to check the
following set of parameters that must be consistent between all eNodeBs in the CA
cluster:
• The Periodic CQI subbands cycles (cqiPerSbCycK), Rank
indication reporting enable (riEnable), and Periodic CQI
feedback type (periodicCqiFeedbackType) parameters must have the
same value in the primary cell (PCell) and all of its associated secondary cells
(SCells).
• The Multiplier M for periodic RI reporting period (riPerM)
parameter is used for each LNCEL in the set of cells that consists of a PCell and all
of its associated SCells. If the Rank indication reporting
enable (riEnable) parameter is set to true, the Multiplier M for
periodic RI reporting period (riPerM) parameter must be set to 1.
• The combination of the BTS ID of the parent eNB of the cell to be
aggregated (lnBtsId) and Local cell resource ID of cell to be
aggregated (lcrId) parameters must be unique in the PCell and all of its
associated SCells in each LNBTS in the CA cluster. The value of the EARFCN
downlink (earfcnDL) (LNCEL) parameter of the PCell must be different than the
value of the EARFCN downlink (earfcnDL) parameter of all the PCell's
associated SCells in each LNBTS in the CA cluster.
• The Activate inter-eNB DL carrier
aggregation (actInterEnbDLCAggr), Scheduling CA fairness
control factor (caSchedFairFact), SCell deactivation timer eNB
(sCellDeactivationTimerEnb), and Activate flexible SCell
selection (actFlexScellSelect) parameters in each LNBTS with the same
CA cluster ID must have the same value.
• The Cell resource sharing mode (cellResourceSharingMode) and
Activate supercell configuration (actSuperCell) parameters must
be set to none and false respectively in the PCell and all of its associated SCells if
the Activation of downlink carrier aggregation (actDLCAggr)
parameter is set to true and the value of the Max number of secondary
cells for DL carrier aggr (maxNumSCells) parameter is greater than or
equal to 1.
• The Carrier aggregation pool ID (caPoolID) parameter must have the
same value for the set of LNCELs that consists of a PCell and all of its associated
SCells. This parameter must also be configured in non-CA cells. A maximum of 13
LNCELs in all LNBTSs in the CA cluster can have the same CA pool ID.

g Note: The CM Analyzer does not check the following for consistency:
• For the set of SCells associated with a PCell, there are at most two different
EARFCN downlink (earfcnDL) parameter values if the
Max number of secondary cells for DL carrier
aggr (maxNumSCells) parameter is greater than 1.
• For the set of SCells associated with a PCell, there are at most six SCells with the
same EARFCN downlink (earfcnDL) parameter value if the
aggr (maxNumSCells) parameter is greater than 1.
• For the set of SCells associated with a PCell, there is at most one SCell with the
same EARFCN downlink (earfcnDL) parameter value if the
aggr (maxNumSCells) parameter is equal to 1.
The eNodeBs in the CA cluster must be configured with sync hub direct forwarding. The
sync hub master must be configured with the Forward synchronization in co-
siting (syncPropagationEnabled) parameter set to true. The sync hub slave
must be configured with the SyncHub Master BTS as reference
source (gpsCtrlBlockForColocatedBTS) parameter set to true and the
Network synchronization mode (btsSyncMode) parameter set to phase sync.
If the Activate inter-eNB DL carrier
aggregation (actInterEnbDLCAggr) parameter is set to true, the integrated self-
organizing network (iSON) manager does not support any CA functions for the
respective eNodeB. Therefore, the Carrier aggregation control (caControl)
parameter must be set to manual in NetAct.
Procedure
In Step 3 (Modify the feature-specific eNodeB configuration settings) of the general

2 Configure the CA cluster.

d) Set the values for the following parameters:
• Carrier aggregation cluster ID (caClusterId)
• Carrier aggregation cluster member
ID (caClusterMemberId)

g Note: The eNodeBs in the CA cluster must have the same CA cluster ID. The
CA cluster member ID identifies the eNodeBs in the CA cluster and each
eNodeB must have a unique member ID. Modification of these parameters
requires eNodeB restart.
3 Activate the Activate inter-eNB DL carrier

aggregation (actInterEnbDLCAggr) parameter.
On the selected LNBTS object, set the value of the Activate inter-eNB DL
carrier aggregation (actInterEnbDLCAggr) parameter to true.

g Note: The CA pool ID (LNCEL-caPoolId) must be consistent within the CA

cluster. The CAREL objects must only point to cells in their CA pool.
5 Send the parameters to the eNodeB according to the procedure described in section
Expected outcome
The LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature is
activated and used for inter-eNodeB CA.
Further information
In case one eNodeB fails, the other eNodeB remains operational. On one hand, in case
the SRIO cable fails, both eNodeBs remain operational but the inter-eNodeB CA is
disabled.
35.3 Deactivating LTE2305: Inter-eNodeB Carrier

Aggregation for 2 Macro eNodeBs
Before you start
The Activate inter-eNB DL carrier
aggregation (actInterEnbDLCAggr) parameter deactivates the feature.

Procedure
In Step 3 (Modify the feature-specific eNodeB configuration settings) of the general

2 Configure the Activate inter-eNB DL carrier

aggregation (actInterEnbDLCAggr) parameter.

d) Set the value of the Activate inter-eNB DL carrier
aggregation (actInterEnbDLCAggr) parameter to false.
g Note: The CA cluster ID, CA cluster member ID, and CAREL objects on the
other eNodeB has to be deleted to completely deactivate the feature.
3 Send the parameters to the eNodeB according to the procedure described in section
Expected outcome
The LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs feature is
deactivated in all eNodeBs and no inter-eNodeB CA takes place. CA with aggregated
cells from one eNodeB (intra-eNodeB) continues to work in all eNodeBs.

LTE15A Radio Resource Management and Telecom LTE2314: Configurable sequence of BCCH carriers
Features within GERAN frequency layer list for CSFB based on
UE Context Release
36 LTE2314: Configurable sequence of BCCH

carriers within GERAN frequency layer list for
CSFB based on UE Context Release
36.1 Description of LTE2314: Configurable Sequence of

BCCH Carriers within GERAN Frequency Layer List
for CSFB Based on UE Context Release
The LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency
Layer List for CSFB Based on UE Context Release feature adds a new functionallity to a
circuit-switched fallback (CSFB) mechanism. It enables the operator to prioritize the
sequence of broadcast control channel (BCCH) carriers within the GERAN frequency
layer list. In the case of some operators, prior to this feature, the fixed sequence of
BCCH carriers caused the UE to select suboptimal cells. With LTE2314 activated, the
UE choses an optimal GERAN cell.
Benefits
End-user benefits
This feature increases call success rate.
Operator benefits
This feature enables the operator to configure a unique priority value for a single
absolute radio frequency number (ARFCN).
Layer List for CSFB Based on UE Context Release feature enables the operator to
prioritize the sequence of broadcast control channel (BCCH) carriers within the GERAN
frequency layer list. In the case of some operators, prior to this feature, the fixed
sequence of BCCH carriers caused the UE to select suboptimal cells. With LTE2314
activated, the UE choses an optimal GERAN cell.
This feature is an extension of the LTE562: CSFB to UTRAN or GSM via Redirect
feature.
GERAN BCCH carrier frequency priority is O&M configurable and no duplication is
allowed within configured carriers' priorities. Carriers without defined priorities are treated
as the lowest priority carriers and are added at the end of the sequence list. After the
operator has configured the priority of ARFCN values, the eNB sends a sorted list to the
UE. When there is no priority set for BCCH carriers, the functionality of this feature
switches off.
System impact

LTE2314: Configurable sequence of BCCH carriers LTE15A Radio Resource Management and Telecom
within GERAN frequency layer list for CSFB based on Features
UE Context Release
For the LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency
Layer List for CSFB Based on UE Context Release feature, the LTE562: CSFB to
UTRAN or GSM via Redirect feature must be enabled. The LTE562 feature is used to
keep circuit-switched (CS) service voice continuity in the initial phase of LTE
implementation, which does not support CS services. As a consequence of this feature,
the UE leaves an LTE network and is handled by radio access technology (RAT),
capable of the CS service.


• call success rate KPI is increased

• VoLTE call success rate KPI is increased

LTE2314: Configurable sequence of BCCH carriers within GERAN frequency layer list
for CSFB based on UE Context Release requirements, alarms and faults, commands,
Requirements

FDD TDD
Alarms

UE Context Release
There are no alarms related to the LTE2314: Configurable sequence of BCCH carriers
within GERAN frequency layer list for CSFB based on UE Context Release feature.

There are no faults related to the LTE2314: Configurable sequence of BCCH carriers
within GERAN frequency layer list for CSFB based on UE Context Release feature.
Commands
There are no commands related to the LTE2314: Configurable sequence of BCCH
carriers within GERAN frequency layer list for CSFB based on UE Context Release
feature.

There are no measurements or counters related to the LTE2314: Configurable sequence
of BCCH carriers within GERAN frequency layer list for CSFB based on UE Context
Release feature.

There are no key performance indicators related to the LTE2314: Configurable sequence
of BCCH carriers within GERAN frequency layer list for CSFB based on UE Context
Release feature.
Parameters

name object
GERAN ARFCN redirGeranAr MODRED - Common
values list fcnStructL
GERAN ARFCN redirGeranAr MODRED redirGeranArfcnStr Common
priority order fcnPrio uctL
GERAN ARFCN value redirGeranAr MODRED redirGeranArfcnStr Common
fcnValue uctL
GERAN ARFCN redirGeranAr MORED - Common
GERAN ARFCN redirGeranAr MORED redirGeranArfcnStr Common
GERAN ARFCN value redirGeranAr MORED redirGeranArfcnStr Common
fcnValue uctL
GERAN ARFCN redirGeranAr REDRT - Common
GERAN ARFCN redirGeranAr REDRT redirGeranArfcnStr Common
GERAN ARFCN value redirGeranAr REDRT redirGeranArfcnStr Common
fcnValue uctL

Sales information

UE Context Release

element
36.3 Activating and configuring LTE2314: Configurable

Sequence of BCCH Carriers within GERAN
Frequency Layer List for CSFB Based on UE
Context Release
Before you start
Layer List for CSFB Based on UE Context Release feature does not have an activation
flag and is activated by default. Table 202: Parameters used for configuring LTE2314:
Configurable Sequence of BCCH Carriers within GERAN Frequency Layer List for CSFB
Based on UE Context Release lists the parameters used for the configuration of this
feature.
Table 202 Parameters used for configuring LTE2314: Configurable Sequence of

BCCH Carriers within GERAN Frequency Layer List for CSFB Based on
UE Context Release
object locking
GERAN ARFCN values list optional configuration no
(redirGeranArfcnStructL)
GERAN ARFCN priority order optional configuration no
(redirGeranArfcnPrio)
GERAN ARFCN value mandatory configuration no
(redirGeranArfcnValue)
For the LTE2314: Configurable Sequence of BCCH Carriers within GERAN Frequency
Layer List for CSFB Based on UE Context Release feature to be used, the LTE562:
CSFB to UTRAN or GSM via Redirect feature must be enabled (actCSFBRedir set to
Enabled).
To configure the feature, do the following:
Procedure


UE Context Release
2 Configure the REDRT instance, for which redirRAT is set to a GERAN value, with the
redirGeranfcnStructL structure and its members (redirGeranArfcnValue,
redirGeranArfcnPrio).

d) Select the LNCEL object and add a new REDRT object.
e) In the REDRT object set the following parameters:
• Redirection target configuration identifier to a value
between 0 and 5
• GERAN band indicator to deasired value
• RAT for redirection to a GERAN value.
Set at least one of the following parameters:
• Redirection priority for CS fallback with redirection
to a value between 1 and 6
• Redirection priority for emergency call to a value between 1
and 6
• Redirection priority for UE context release to a value
between 1 and 6
f) Select the REDRT object and add a new GERAN ARFCN values list object.
g) In the GERAN ARFCN values list object, set the GERAN ARFCN priority
order (redirGeranArfcnPrio) parameter to a value between 1 and 32
and GERAN ARFCN value (redirGeranArfcnValue) parameter to a
value between 0 and 1023.
3 In the MODRED instance, configure the redirGeranArfcnStructL structure with its

members (redirGeranArfcnValue, redirGeranArfcnPrio).

c) Select the LNBTS object and add a new MODPR object.
d) Select the MODPR object and add a new MODRED object..
e) In the MODRED object, set the following parameters:
• Mobility profile identifier for redirection to a value
between 0 and 5
• GERAN band indicatorto desired value
• RAT for redirection to a GERAN value
Set at least one of the following parameters:
• Redirection priority for CS fallback with redirection
to a value between 1 and 6
• Redirection priority for emergency call to a value between 1
and 6

UE Context Release
• Redirection priority for UE context release to a value

between 1 and 6
f) Select the MODRED object, and add a new GERAN ARFCN values list object.
g) In the GERAN ARFCN values list object, set the GERAN ARFCN priority
order (redirGeranArfcnPrio) parameter to a value between 1 and 32
and GERAN ARFCN value (redirGeranArfcnValue) parameter to a
4 In the MORED instance, configure the redirGeranArfcnStructL structure with its

members (redirGeranArfcnValue, redirGeranArfcnPrio).

c) Select the LNBTS object and add a new MOPR object.
d) Select the MOPR object and set the Mobility profile identifier to a
e) Select the MOPR object and add a new MORED object.
f) In the MORED object, set the following parameters:
• Mobility profile identifier for redirection to a value
between 0 and 5
• RAT for redirection to a GERAN value
• GERAN band indicator to desired value
g) Select the MORED object and add a new GERAN ARFCN values list object.
h) In the GERAN ARFCN values list object, set the GERAN ARFCN priority
order (redirGeranArfcnPrio) and GERAN ARFCN value
(redirGeranArfcnValue) parameters to desired values.
Expected outcome
Layer List for CSFB Based on UE Context Release feature is activated and configured
for CSFB with redirection to GERAN. Target frequency values represented by ARFCN
will be set according to the priorities configured by the operator.

UE Context Release
36.4 Deactivating LTE2314: Configurable Sequence of

BCCH Carriers within GERAN Frequency Layer List
for CSFB Based on UE Context Release
Before you start
Deactivation of LTE2314: Configurable Sequence of BCCH Carriers within GERAN
Frequency Layer List for CSFB Based on UE Context Release requires the user to
delete the parameters previousely configured. Modification of these parameters does not
require a BTS restart.
Procedure

2 In the REDRT instance, for which redirRAT is set to a GERAN value, deactivate the
redirGeranArfcnStructL structure with its member (redirGeranArfcnPrio).

e) Expand the REDRT object.
f) On the GERAN ARFCN values list, delete the value in the GERAN ARFCN
priority order (redirGeranArfcnPrio) parameter.
3 In the MODRED instance, deactivate the redirGeranArfcnStructL structure with

its member (redirGeranArfcnPrio)

d) Expand the MODPR object.
e) Expand the MODRED object.
f) In the GERAN ARFCN values list object, delete the value in the GERAN ARFCN

UE Context Release
4 In the MORED instance, deactivate the redirGeranArfcnStructL structure with its

member (redirGeranArfcnPrio).

d) Expand the MOPR object.
e) Expand the MORED object.
f) In the GERAN ARFCN values list object, delete the value in the GERAN ARFCN
Expected outcome
Layer List for CSFB Based on UE Context Release feature is deactivated.

LTE15A Radio Resource Management and Telecom LTE2324: Network-requested UE Radio Capabilities
Features
37 LTE2324: Network-requested UE Radio

Capabilities
37.1 Description of LTE2324: Network-requested UE

Radio Capabilities
The LTE2324: Network-requested UE Radio Capabilities feature enables supporting the
UE with more than 128 carrier aggregation (CA) band combinations. The additional CA
band combinations (supportedBandCombinationAdd) are valid only for 3CC band
combinations.
Benefits
End-user benefits
This feature ensures end users' mobiles greater flexibly since they support more band
combinations (more than 128 different band combinations); thus, end users may
experience higher throughput.
Operator benefits
This feature allows the operator to reduce the number of 3CC band combinations sent
from UE to eNB based on the priority list provided by the operator. Moreover, it enables
the operator to avoid the latency introduced from the IDLE to ACTIVE transition because
the eNB would have the available UE capabilities at initial attach. Without this feature
implemented, the operator may not be able to provide the 3CC carrier aggregation to the
end user if the band combinations of the operator's network are not contained in the UE
capabilities sent from UE to eNB.
Requirements
The LTE2324: Network-requested UE Radio Capabilities feature introduces an operator
configurable list of required carrier aggregation (CA) bands. The additional CA band
combinations (supportedBandCombinationAdd) are valid only for 3CC band
combinations. This feature enables the UE to provide additional 256 supported CA band
combinations upon the eNB's request compared with the currently available 128 band
combinations. If the initially provided UE radio capabilities are not sufficient to configure
CA in the eNB, a dedicated UE capability enquiry with carrier aggregation bands will be
initiated for UEs with suitable capabilities. The feature can be enabled/disabled per eNB
through the O&M settings. Operation of the LTE2324: Network-requested UE Radio
Capabilities feature consists of the following two mechanisms:
• filtering, where the eNB requests the UE to provide supported band combinations
within a limited set of bands
• adding a supportedBandCombinationAdd list in the UE-EUTRA-Capability, enabling
additional 256 CA band combinations in a UE capability signalling

LTE2324: Network-requested UE Radio Capabilities LTE15A Radio Resource Management and Telecom
Features
System impact
The LTE2014: 3GPP Baseline R11 09/2014 (v2) feature introduces SASN.1 required for
the LTE2324: Network-requested UE Radio Capabilities.
If the operator uses mapped bands, the LTE1534: Multiple Frequency Band Indicator
feature must be active for the LTE2324: Network-requested UE Radio Capabilities
feature.
The LTE2324: Network-requested UE Radio Capabilities feature introduces additional
256 band combinations signaled by the UE for the following CA features. These
combinations need to be considered by the eNB for a CA configuration.
• LTE747: Support of UE Radio Capabilities
• LTE1541: Advanced SCell Measurement Handling
• LTE1803: Downlink Carrier Aggregation 3CC - 40 MHz
• LTE1804: Downlink Carrier Aggregation 3CC - 60 MHz
• For FDD: LTE1836: TDD Downlink Carrier Aggregation - 60 MHz
• For TDD: LTE1838: TDD Downlink Inter-band Carrier Aggregation - 40 MHz
• LTE2006: Flexible SCell Selection
LTE2324: Network-requested UE Radio Capabilities introduces additional 256 band

combinations signaled by the UE for the following handover and ANR features. These
combinations need to be considered by the eNB for the calculation of measurements.
• LTE60: Inter-RAT Handover to eHRPD/3GPP2
• LTE442: Network-assisted Cell Change
• LTE556: ANR Intra-LTE, Inter-frequency - UE-based
• LTE736: CSFB to UTRAN via PS HO
• LTE738: SRVCC to1xRTT/CDMA
• For TDD:LTE898: TDD Inter-RAT Handover to TD-SCDMA
• LTE908: ANR Inter-RAT UTRAN - Fully UE-based
• LTE1357: LTE-UTRAN Load Balancing
For TDD solution: For the following features, LTE2324: Network-requested UE Radio
Capabilities introduces additional 256 band combinations signaled by UE to be
considered by the eNB for the calculation of a maximum number of MIMO layers.
• LTE1543: 8x2 SU MIMO with TM9
For the following handover features, the LTE2324: Network-requested UE Radio

Capabilities feature retrieves again the UE radio capabilities from the UE. If the radio
capabilities are not sufficient for CA, this capability retrieval also contains also the
request for other-RAT capabilities if they are required by the feature and are not provided
by MME.

Features

• LTE736: CSFB to UTRAN via PS HO
• LTE738: SRVCC to1xRTT/CDMA
This feature impacts the RAN system NE external interfaces by introducing new
information elements to the following existing messages:
• requestedFrequencyBands-r11 in the RRC::UECapabilityEnquiry message

• supportedBandCombinationAdd-r11 in the RRC::UECapabilityInformation message


This feature may increase attach latency due to the size of the UECapabilityInformation
message, resulting from the reporting of additional supported band combinations in the
long term. This depends on the number of bands actually supported by the UE.
Management data
Sales information

Requirements

FDD TDD
Flexi Multiradio 10 Indoor BTS not supported TL15A
NetAct 15.5 15.5

Features

FDD TDD
UE 3GPP R11 3GPP R11
Alarms
There are no alarms related to the LTE2324: Network-requested UE Radio Capabilities
feature.

There are no faults related to the LTE2324: Network-requested UE Radio Capabilities
feature.
Commands
There are no commands related to the LTE2324: Network-requested UE Radio
Capabilities feature.

There are no measurements or counters related to the LTE2324: Network-requested UE
Radio Capabilities feature.

There are no key performance indicators related to the LTE2324: Network-requested UE
Radio Capabilities feature.
Parameters

d object
Activate Network actNwReqUeCapa LNBTS - common
Requested UE Radio
Capabilities
Requested frequency reqFreqBands LNBTS - common
bands
3GPP band number bandNumber LNBTS reqFreqBands common
Band priority bandPrio LNBTS reqFreqBands common
Sales information

Features

Basic Software (BSW) - No
37.3 Activating and configuring LTE2324: Network-

requested UE Radio Capabilities
Before you start
The Activate Network Requested UE Radio Capabilities
(actNwReqUeCapa) parameter is used for activation. Modification of this parameter
does not require eNB restart.
Table 206 Table 4 lists the parameters used for activating and configuring the
LTE2324: Network-requested UE Radio Capabilities feature
object locking
Activate Network Requested UE activation flag no
Radio Capabilities
(actNwReqUeCapa)
Requested frequency bands mandatory configuration no
(reqFreqBands)
The following features must be activaterd before the LTE2324: Network-requested UE

Radio Capabilities feature can be activated:
• The LTE2014: 3GPP Baseline R11 09/2014 (v2) feature introduces SASN.1 required
for the LTE2324: Network-requested UE Radio Capabilities.
• If the operator uses mapped bands, the LTE1534: Multiple Frequency Band Indicator
feature must be active for the LTE2324: Network-requested UE Radio Capabilities
feature.
Procedure

2 Configure the Requested frequency bands (reqFreqBands) parameter.


Features
c) Select the LNBTS object and create a new Requested frequency bands object.
d) Set the desired values of the reqFreqBands parameter.
3 Activate the Activate network requested UE radio capabilities

(actNwReqUeCapa) parameter.

c) Click the LNBTS object.
d) Set the Activate network requested UE radio capabilities
(actNwReqUeCapa) parameter value to true.
Expected outcome
The LTE2324: Network-requested UE Radio Capabilities feature has been activated.
37.4 Deactivating LTE2324: Network-requested UE

Radio Capabilities
Before you start
The Activate Network Requested UE Radio Capabilities
(actNwReqUeCapa) parameter is used for deactivation. Modification of this parameter
does not require eNB restart.
Procedure


d) Set the Activate Network Requested UE Radio
Capabilities (actNwReqUeCapa) parameter value to false.
Expected outcome

Features
The LTE2324: Network-requested UE Radio Capabilities feature has been deactivated.

LTE2388: VoLTE Call Steering Enhancement LTE15A Radio Resource Management and Telecom
Features
38 LTE2388: VoLTE Call Steering Enhancement
38.1 Description of LTE2388: VoLTE Call Steering

Enhancement
The LTE2388: VoLTE Call Steering Enhancement feature enables redirection of VoLTE
calls during the initial context setup phase to an FDD or WCDMA layer. This solution
bypasses the limitation caused by spectrum license conditions in certain TDD networks
which do not allow sending VoLTE data packets (QCI1) over the air.
Benefits
End-user benefits
This feature have no effect on the end-user experience.
Operator benefits
This feature enables the operator to redirect a VoLTE call to another LTE layer or
WCDMA layer. The license conditions will no longer have an influence on VoLTE calls.
In certain TDD networks, spectrum licence conditions do not allow to transmit VoLTE
calls over the air. To make VoLTE calls possible in such networks, VoLTE data packets
can be redirected to the overlaying LTE FDD layer or WCDMA layer (see Figure 25:
Redirection of VoLTE call to other layers.)
Figure 25 Redirection of VoLTE call to other layers
LTE-TDD
VoLTEcall
1.TDD/FDD
layer
handover
LTE-FDD 1 2.CSfallback
layer
(WCDMAhandover)
WCDMAlayer 2
The reason behind this is that in certain TDD networks, the LTE10: EPS Bearers for
Conversational Voice is deactivated in an eNB. It means that when a UE requests the
VoLTE call with an initial context setup request (QCI1,QCI5,QCI9), it will be rejected.
When the LTE2388: VoLTE Call Steering Enhancement feature is activated, a VoLTE
bearer (QCI1) is established towards the UE despite feature LTE10: EPS Bearers for
Conversational Voice is deactivated.

LTE15A Radio Resource Management and Telecom LTE2388: VoLTE Call Steering Enhancement
Features
At first, the eNB attempts to redirect the call to an FDD layer. The initial context setup
response, including the ERAB setup list IE, is sent to the MME, and the eNodeB starts
the redirect timer (configurable by the operator) and begins a force service-based
handover. A target cell for a handover preparation is selected only if the UE
measurements are above an RSRP and/or RSRQ threshold, and the cell is not
blacklisted.
If a handover to the FDD layer is not successful, the eNB attempts a redirection to a
WCDMA layer (CS fallback). A blind RRC connection release with a redirect is
performed to the target layer, which is defined for the redirect-based CS fallback (e.g. the
LTE562: CSFB to UTRAN or GSM via Redirect feature target list). An S1AP UE context
release request with a respective cause value is sent to the MME.
System impact
The following features must be activated before the activation of the LTE2388: VoLTE
Call Steering Enhancement feature:
• LTE2108: Redirected VoLTE Call Setup, which requires
– LTE55: Support of Inter-frequency Handover
– LTE1060: TDD-FDD Handover
Features that cannot be activated together with LTE2388: VoLTE Call Steering
Enhancement
The LTE2388: VoLTE Call Steering Enhancement feature is correlated with the following
features:
• LTE562: CSFB to UTRAN or GSM via Redirect - target frequencies configured for
CSFB are reused by LTE2388, but the activation of LTE562 is not required
• LTE1127: Service-based Mobility Trigger - an RSRP and RSRQ threshold filter for A4
SB HO and a VoLTE targets list introduced by this feature are reused in LTE2388.
The LTE1127 feature cannot be activated together with LTE2388
• LTE1442: Open Access Home eNB Mobility - HeNB targets shall be excluded as
valid targets for LTE2388
• LTE1170/LTE1531/LTE1387/ LTE1841 Inter-frequency Load Balancing features -
they can be activated in parallel with LTE2388; however, if QCI1 is established for a
UE, this UE can no longer be used for a load balancing purpose
• LTE1617: RLF-triggered Handover - when LTE1617 is triggered while an LTE2338
use case applies, the RRC connection re-establishment request is rejected on target
eNB side
• LTE1944: Temporary Handover Blacklisting - the LTE1944 blacklist also applies to
LTE2388 target selection
• LTE572 : IMS Emergency Session - an emergency VoLTE call is treated as a regular
VoLTE call

Features
• LTE423: RRC Connection Release with Redirect and LTE1407: RSRQ-based

Redirect - when LTE2388 is enabled, during the initial context setup procedure, A2
(redirect) measurements and LTE2388 specific A4 measurements will be configured
and activated
There is no impact on interfaces.

There is no impact on network management tools.

There is no impact on system performance or capacity.
38.2 Activating and configuring LTE2388: VoLTE Call

Steering Enhancement
Before you start
Table 207: Parameters used for activating and configuring LTE2388: VoLTE Call Steering
Enhancement lists parameters related to the LTE2388: VoLTE Call Steering
Enhancement feature
Table 207 Parameters used for activating and configuring LTE2388: VoLTE Call
Steering Enhancement
object locking
Activate VoLTE call steering activation flag no
(actVoLteCallSteering)
Frequency layer list for VoLTE mandatory configuration no
service based HO
(freqLayListServiceBasedHo)
The following features and their parameters must be activated before the activation of
the LTE2388: VoLTE Call Steering Enhancement feature:
• LTE7: Support of Multiple EPS Bearer - LNBTS: Activate multiple bearers
(actMultBearers)
• LTE2108: Redirected VoLTE Call Setup - LNBTS_TDD: Activate redirect
VoLTE (actRedirVoLte) and LNCEL_TDD: Redirected VoLTE call
setup supervision timer (voLteRedirTimer)
Features that cannot be activated together with LTE2388: VoLTE Call Steering
Enhancement

Features
Before activation of this feature, redirection and handovers functionalities must be

configured. To configure redirection functionality:
• setLNBTS: Activate CS fallback via redirection
(actCSFBRedir) and LNBTS: Enable UE context release with
redirect (actRedirect) parameters to value 'true'
• configure Redirection priority for CS fallback with
redirection (csFallBPrio) and Redirection priority for UE
context release (redirectPrio) parameters in correct instance:
– if the LTE490 feature and SPID mapping are enabled configure MOPR: MORED
instance
– if the LTE490 feature is enabled, there is no SPID mapping, and autoAdapt is
set to 'false' configure MODPR: MODRED instance
– if the LTE490 feature is disabled configure LNCEL: REDRT instance
To configure handovers, set autoAdapt to 'false' in correct instance:

• if the LTE490 feature and SPID mapping are enabled configure LNBTS: MOPR
instance
• if the LTE490 feature is disabled configure LNBTS: MODPR instance
Additionally:
• In the LNCEL instances, the Mobility profiles mapping list
(moPrMappingList) should be configured.
• LNCEL: LNHOIF instances should be properly configured, with at least one of the
follwoing parameters:
– Inter-freq. service based threshold RSRP target filter
(thresholdRsrpIFSBFilter)
– Inter-freq. service based threshold RSRQ target filter
(thresholdRsrqIFSBFilter)
Procedure

2 Set the activation flag of the LTE2388 feature.

d) Select the LNBTS_TDD object.

Features
e) Set the Activate VoLTE call steering (actVoLteCallSteering)

parameter value to true.
3 Configure the frequency layer list for a VoLTE service-based HO.

d) Select the MODPR object, then create and configure Frequency layer
list for VoLTE service based
HO (freqLayListServiceBasedHo) list.
e) Check which MOPR instances are listed in Mobility profile ID in the
LNCEL: Mobility profiles mapping list. Then for each MOPR
listed, create and configure Frequency layer list for VoLTE
service based HO (freqLayListServiceBasedHo) list.
g Note: If the Frequency layer list for VoLTE service based HO

parameter is not configured or defined as an empty list, all inter-frequency targets
are not allowed for a VoLTE handover to FDD layer. In this case, the redirect is
targeted to 3G directly if those are configured; otherwise, a UE context release
will occur.
Expected outcome
All LNCEL instances are operating with the configured and activated LTE2388 feature
using the frequency layer list. VoLTE calls are possible in TDD network.
38.3 Deactivating LTE2388: VoLTE Call Steering

Enhancement
Before you start
The Activate VoLTE call steering (actVoLteCallSteering) parameter
is used for deactivation. Modification of this parameter does not require either an eNB
restart or a cell locking.

Features
Procedure

2 Deactivate the feature activation flag.

d) Select the LNBTS_TDD object.
e) Set the Activate VoLTE call steering (actVoLteCallSteering)
parameter value to false.
Expected outcome
VoLTE calls are no longer possible in the TDD network.

Requirements

FDD TDD
System release Not Supported TD-LTE 15A
Flexi Multiradio 10 BTS Not Supported TL15A
Flexi Multiradio 10 Indoor BTS Not Supported TL15A
Nokia AirScale BTS Not Supported TL16A
Flexi Zone BTS Not Supported TL15A
Flexi Zone Access Point Not Supported TL16
Flexi Zone Controller Not Supported TL16
OMS Not Supported Support not required
NetAct Not Supported Support not required
MME Not Supported Support not required
SAE GW Not Supported Support not required
UE Not Supported 3GPP R8 UE

Features
Alarms
There are no alarms related to the LTE2388 :VoLTE call steering enhancement feature.

There are no faults related to the LTE2388 :VoLTE call steering enhancement feature.
Commands
There are no commands related to the LTE2388 :VoLTE call steering enhancement
feature.

There are no measurements or counters related to the LTE2388 :VoLTE call steering
enhancement feature.

There are no key performance indicators related to the LTE2388 :VoLTE call steering
enhancement feature.
Parameters

d object
Activate VoLTE call actVoLteCallSt LNBTS - TDD
steering eering _TDD

d object
Frequency layer actVoLteCallSt MODPR - common
list for VoLTE eering /MOPR
service based HO

Documentation/Reference/Parameters
Sales information

Application software (ASW) SW Asset Monitoring No

LTE15A Radio Resource Management and Telecom LTE2430: QCI1 Establishment Triggered Protection
Features Timer
39 LTE2430: QCI1 Establishment Triggered

Protection Timer
39.1 Description of LTE2430: QCI1 Establishment

Triggered Protection Timer

change
07.07.2017 Activating and Updated the possible allowed values for the QCI1
configuring protection timer (qci1ProtectionTimer)
LTE2430: QCI1 parameter in Step 3 of the activation procedure.
Establishment
Triggered
Protection Timer

The LTE2430: QCI1 Establishment Triggered Protection Timer feature allows keeping
the UE in an RRC-connected mode even if there is no activity, for example, during a
ringtone. The connection sustain time is defined by a dedicated timer-type parameter.
Benefits
End-user benefits
This feature improves a VoLTE setup success rate.
Operator benefits
This feature:
• provides a VoLTE UE from going to the RRC idle mode caused by inactivity, for
example, during a ringtone, which might last longer than a normal inactivity timer
• saves a signalling capacity
• improves a VoLTE setup success rate
• prevents a ringing UE from being idle balanced to a layer where the QCI1 traffic is
not desired
Requirements
The LTE2430: QCI1 Establishment Triggered Protection Timer feature enables a
configurable QCI1 protection timer. The timer is used for preventing the UEs from falling
into the RRC idle mode during a ringtone, when there is potentially no traffic on any of
the bearers or on the S1 link. However, if the protection timer and all other inactivity
timers expire before the ringtone is finished, the UE is released to the RRC idle mode.

LTE2430: QCI1 Establishment Triggered Protection LTE15A Radio Resource Management and Telecom
Timer Features
The timer is started or restarted by an eNodeB every time the QCI1 is established. The
intention is to set the timer value higher than a normal user plane inactivity timer; it
should be set according to the time that the end-user is expected to answer the call
when the phone is ringing. In this scenario, the UE is not released to the RRC idle mode
until the established QCI1 timer and all other inactivity timers expire.
In case the end-user terminates the call, and no other QCI1 related to that UE is
established, then the QCI1 protection timer stops. Consequently, if additionally all other
inactivity timers expire, the UE is released to the RRC idle mode.
The value of QCI1 protection timer is defined with the QCI1 protection
timer (qci1ProtectionTimer) parameter.
System impact
This feature requires the following features to be enabled:



This feature has the following impact on the system performance:
• signalling capacity: saved

• VoLTE setup success rate: can be improved, but depends on the operator's network
configuration
Management data
Sales information

Requirements

FDD TDD

Features Timer

FDD TDD
Alarms
There are no alarms related to the LTE2430: QCI1 Establishment Triggered Protection
Timer feature.

There are no faults related to the LTE2430: QCI1 Establishment Triggered Protection
Timer feature.
Commands
There are no commands related to the LTE2430: QCI1 Establishment Triggered
Protection Timer feature.

There are no measurements or counters related to the LTE2430: QCI1 Establishment
Triggered Protection Timer feature.

There are no key performance indicators related to the LTE2430: QCI1 Establishment
Triggered Protection Timer feature.
Parameters
Activate RRC actRrcConnNoA LNBTS - common
connected mode ctivity
while no activity
QCI1 protection qci1Protectio LNCEL - common
timer nTimer

Timer Features

Inactivity timer inactivityTim LNCEL - common
er
For parameter descriptions, see the LTE BTS Parameters reference document.
feature.
Sales information

Application software (ASW) SW asset monitoring No
39.3 Activating and configuring LTE2430: QCI1

Establishment Triggered Protection Timer
Before you start
The Activate RRC connected mode while no
activity (actRrcConnNoActivity) parameter is used for activation. Modification
of this parameter does not require eNB restart or object locking.
Table 217: Parameters used for activating and configuring LTE2430: QCI1 Establishment
Triggered Protection Timer feature presents the parameters related to activation and
configuration of the LTE2430: QCI1 Establishment Triggered Protection Timer feature.
Table 217 Parameters used for activating and configuring LTE2430: QCI1
Establishment Triggered Protection Timer feature
object locking
Activate RRC connected activation flag no
mode while no
activity (actRrcConnNoAct
ivity)
QCI1 protection optional configuration no
timer (qci1ProtectionTime
r)
The following features need to be activated before the activation of the LTE2430: QCI1
Establishment Triggered Protection Timer feature:


Features Timer
Procedure

2 Configure the Activate RRC connected mode while no

activity (actRrcConnNoActivity) parameter.

d) Set the Activate RRC connected mode while no
activity (actRrcConnNoActivity) parameter's value to true.
3 Optional: Configure the QCI1 protection timer (qci1ProtectionTimer)

parameter.

b) Check the value of the Inactivity timer (inactivityTimer) parameter.
c) Set the QCI1 protection timer (qci1ProtectionTimer) parameter's
value to a value that is equal to or higher than the Inactivity
timer (inactivityTimer) parameter's value.
Expected outcome
The LTE2430: QCI1 Establishment Triggered Protection Timer feature has been
activated. The UE is kept in the RRC connection mode even if there is no activity, for
example, during a ringtone, until the established QCI1 timer and all other inactivity timers
expire.
39.4 Deactivating LTE2430: QCI1 Establishment

Triggered Protection Timer
Before you start
The Activate RRC connected mode while no
activity (actRrcConnNoActivity) parameter is used for deactivation.
Modification of this parameter does not require eNB restart or object locking.

Timer Features
Procedure

2 Deactivate the LTE2430: QCI1 Establishment Triggered Protection Timer feature.

d) Set the Activate RRC connected mode while no
activity (actRrcConnNoActivity) parameter's value to false.
Expected outcome
The LTE2430: QCI1 Establishment Triggered Protection Timer feature has been
deactivated. QCI1 protection timer is not started or restarted every time the QCI1 bearer
is established. The UE is kept in the RRC connection mode even if there is no activity,
for example, during a ringtone, until the established QCI1 timer (if it is already running)
and all other inactivity timers expire.

lte15a_features_rrm

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

lte15a_features_rrm

Uploaded by

Copyright:

Available Formats

LTE Radio Access, Rel.

LTE15A Radio Resource

Copyright © 2018 Nokia. All rights reserved.

f Important Notice on Product Safety

2 © 2018 Nokia. Nokia confidential. DN179848337 Issue: 01

1 LTE64: Service based handover thresholds ............................... 18

2 LTE569: Downlink Adaptive Closed Loop SU-MIMO 4x4............ 29

3 LTE738: SRVCC to 1xRTT/CDMA............................................... 38

4 LTE825: Uplink Outer Region Scheduliing................................... 54

5 LTE951: Enhanced Cell ID Location Service............................... 67

6 LTE1117: LTE MBMS................................................................... 82

7 LTE1196: RAN Information Management for WCDMA.............. 104

DN179848337 Issue: 01 © 2018 Nokia. Nokia confidential. 3

7.1 Description of LTE1196: RAN Information Management for

8 LTE1321: eRAB Modification – GBR..........................................119

9 LTE1357: LTE-UTRAN Load Balancing..................................... 126

10 LTE1635: SIB8 AC barring for 1xRTT........................................ 138

11 LTE1679: DRX with Parallel UE Measurement Gaps................ 146

12 LTE1784: Carrier Aggregation for Supercell up to 2CC............. 153

13 LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall.....

4 © 2018 Nokia. Nokia confidential. DN179848337 Issue: 01

14 LTE1788: Automatic Access Class Barring................................169

15 LTE1804: Downlink Carrier Aggregation 3 CC - 60 MHz........... 187

16 LTE1836: TDD Downlink Carrier Aggregation - 60 MHz............ 203

17 LTE1838: TDD Downlink Inter-band Carrier Aggregation - 40 MHz

18 LTE1850: TDD Intra-band Dual-carrier Operation within a Flexi

19 LTE1896: TDD Intra-band Dual-carrier Downlink Aggregation for

DN179848337 Issue: 01 © 2018 Nokia. Nokia confidential. 5

19.2 LTE1896 reference data.............................................................231

20 LTE1905: PLMN ID and SPID Selected Mobility Profiles...........238

21 LTE1925: Cause value for CSFB to GERAN without DTM support .

22 LTE1929: UL Semi-persistent scheduling.................................. 254

23 LTE1942: Dedicated VoLTE Inter-frequency Target Frequency List

24 LTE1944: Dynamic Handover Blacklisting ................................ 274

25 LTE2006: Flexible SCell Selection............................................. 281

6 © 2018 Nokia. Nokia confidential. DN179848337 Issue: 01

25.2 LTE2006 functional description.................................................. 281

26 LTE2023: User plane overload handling ................................... 290

27 LTE2051: Measurement based Idle Mode Load Balancing....... 300

28 LTE2085: SIB Reception with Parallel Measurement Gaps....... 309

29 LTE2120: TDD SIB reception with parallel measurement gaps ......

DN179848337 Issue: 01 © 2018 Nokia. Nokia confidential. 7

window (sib2xTransmit) activation flag is set to true or false.

30 LTE2128: Uplink Intra eNodeB CoMP 8 RX with Softbit

31 LTE2133: eICIC for HetNet eNode B Configurations................. 347

32 LTE2149: Supplemental Downlink Carrier................................. 352

33 LTE2168: Additional Carrier Aggregation Band Combinations - II...

34 LTE2208: eICIC Enhancements - micro.....................................368

35 LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs

8 © 2018 Nokia. Nokia confidential. DN179848337 Issue: 01

36 LTE2314: Configurable sequence of BCCH carriers within GERAN

37 LTE2324: Network-requested UE Radio Capabilities................ 389

38 LTE2388: VoLTE Call Steering Enhancement............................396

39 LTE2430: QCI1 Establishment Triggered Protection Timer....... 403

DN179848337 Issue: 01 © 2018 Nokia. Nokia confidential. 9

10 © 2018 Nokia. Nokia confidential. DN179848337 Issue: 01

DN179848337 Issue: 01 © 2018 Nokia. Nokia confidential. 11

Table 35 Parameters used for activating and configuring LTE951: Enhanced

12 © 2018 Nokia. Nokia confidential. DN179848337 Issue: 01

Table 71 LTE1784 hardware and software requirements................................155

DN179848337 Issue: 01 © 2018 Nokia. Nokia confidential. 13

Table 108 LTE1850 hardware and software requirements................................224

14 © 2018 Nokia. Nokia confidential. DN179848337 Issue: 01

DN179848337 Issue: 01 © 2018 Nokia. Nokia confidential. 15