Feature Descriptions FDD-LTE

Features FDD-LTE17, Feature Descriptions and Instructions DN09237915 Issue 01A Approval Date 2017-02-03

FDD-LTE17, Feature Descriptions and Instructions

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

© 2017 Nokia

DN09237915 Issue: 01A


Table of Contents This document has 195 pages

Summary of changes................................................................... 13

1

Introduction.................................................................................. 14

2

Activating and deactivating LTE features using BTS Site Manager. 15

3

Descriptions of radio resource management and telecom features. 17 LTE1834: LTE MBMS Service Continuity.....................................17 LTE1834 benefits......................................................................... 17 LTE1834 functional description.................................................... 17 LTE1834 system impact............................................................... 18 LTE1834 reference data...............................................................22 Activating LTE1834: LTE MBMS Service Continuity ................... 25 Configuring LTE1834: LTE MBMS Service Continuity................. 26 Configuring Prioritize VoLTE over MBMS (prioritizeVoLTEoverMBMS) and inter-frequency related parameters................................................................................... 26 Assigning a SIB15 profile with the SIB15 profile identifier (sib15ProfileId) parameter.......................27 Configure SAIs of inter-frequency neighbor cells in SIB15PR..... 28 Configure SAIs of intra-frequency neighbor cells.........................30 Adding a list item to the SIB instance of any cell which shall broadcast SIB15...........................................................................31 Deactivating LTE1834: LTE MBMS Service Continuity................ 33 LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls.......................................................................... 34 LTE2410 benefits......................................................................... 34 LTE2410 functional description.................................................... 34 LTE2410 system impact............................................................... 35 LTE2410 reference data...............................................................35 LTE2466: S1 Handover towards Hybrid Cells.............................. 36 LTE2466 benefits......................................................................... 37 LTE2466 functional description.................................................... 37 LTE2466 system impact............................................................... 38 LTE2466 reference data...............................................................40 Activating and configuring LTE2466.............................................42 Deactivating LTE2466.................................................................. 45 LTE2572: RSRQ-based B2.......................................................... 47 LTE2572 benefits......................................................................... 47 LTE2572 functional description.................................................... 47 LTE2572 overview........................................................................49 B2 RSRQ conditions.................................................................... 50

3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.1.6 3.1.6.1

3.1.6.2 3.1.6.3 3.1.6.4 3.1.6.5 3.1.7 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6 3.4 3.4.1 3.4.2 3.4.2.1 3.4.2.2

DN09237915 Issue: 01A

© 2017 Nokia

3


3.4.3 3.4.4 3.4.5 3.4.6 3.5 3.5.1 3.5.2 3.5.3 3.5.4 3.5.5 3.5.6 3.6 3.6.1 3.6.2 3.6.3 3.6.4 3.7 3.7.1 3.7.2 3.7.3 3.7.4 3.8 3.8.1 3.8.2 3.8.3 3.8.4 3.9 3.9.1 3.9.2 3.9.3 3.9.4 3.9.5 3.9.6 3.10 3.10.1 3.10.2 3.10.3 3.10.4 3.10.5 3.10.6 3.11 3.11.1

4

LTE2572: system impact.............................................................. 50 LTE2572 reference data...............................................................50 Activating LTE2572...................................................................... 52 Deactivating LTE2572.................................................................. 54 LTE2664: Load-based PUCCH Region........................................55 LTE2664 benefits......................................................................... 55 LTE2664 functional description.................................................... 56 LTE2664 system impact............................................................... 60 LTE2664 reference data...............................................................60 Activating and configuring LTE2664.............................................63 Deactivating LTE2664.................................................................. 66 LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V................................................................................................68 LTE3047 benefits......................................................................... 68 LTE3047 functional description.................................................... 69 LTE3047 system impact............................................................... 69 LTE3047 reference data...............................................................70 LTE3048: Additional Carrier Aggregation Band Combinations 3CC – III............................................................................................... 71 LTE3048 benefits......................................................................... 71 LTE3048 functional description.................................................... 71 LTE3048 system impact............................................................... 72 LTE3048 reference data...............................................................73 LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II......................................................................... 74 LTE3049 benefits......................................................................... 74 LTE3049 functional description.................................................... 74 LTE3049 system impact............................................................... 75 LTE3049 reference data...............................................................75 LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) ........................................................................................ 76 LTE3056 benefits......................................................................... 77 LTE3056 functional description.................................................... 77 LTE3056 system impact............................................................... 77 LTE3056 reference data...............................................................78 Activating and configuring LTE3056.............................................80 Deactivating LTE3056.................................................................. 82 LTE3073: 256 QAM Extensions................................................... 84 LTE3073 benefits......................................................................... 84 LTE3073 functional description.................................................... 84 LTE3073 system impact............................................................... 85 LTE3073 reference data...............................................................85 Activating LTE3073...................................................................... 90 Deactivating LTE3073.................................................................. 90 LTE3199: Support for Multiple MBSFN and Synchronization Areas ..................................................................................................... 90 LTE3199 benefits......................................................................... 90

© 2017 Nokia

DN09237915 Issue: 01A


3.11.2 3.11.3 3.11.4 3.12 3.12.1 3.12.2 3.12.3 3.12.4 3.13 3.13.1 3.13.2 3.13.3 3.13.4 3.14 3.14.1 3.14.2 3.14.3 3.14.4 3.14.5 3.14.6 3.14.7 3.15 3.15.1 3.15.2 3.15.3 3.15.4 3.15.5 3.15.6 3.16 3.16.1 3.16.2 3.16.3 3.16.4 3.16.5 3.16.5.1 3.16.6 3.17 3.17.1 3.17.2 3.17.3 3.17.4 3.17.5 3.17.6 3.18

DN09237915 Issue: 01A

LTE3199 functional description.................................................... 91 LTE3199 system impact............................................................... 92 LTE3199 reference data...............................................................95 LTE3201: eMBMS in RAN-sharing Deployment Support............. 99 LTE3201 benefits......................................................................... 99 LTE3201 functional description.................................................. 100 LTE3201 system impact............................................................. 100 LTE3201 reference data.............................................................101 LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I........................................................................ 103 LTE3213 benefits....................................................................... 103 LTE3213 functional description.................................................. 103 LTE3213 system impact............................................................. 103 LTE3213 reference data.............................................................104 LTE3230: UL Interference Offsets..............................................105 LTE3230 benefits....................................................................... 105 LTE3230 functional description.................................................. 105 LTE3230 system impact............................................................. 108 LTE3230 reference data.............................................................109 Activating and configuring LTE3230 for band 18........................110 Activating and configuring LTE3230 for band 30........................113 Deactivating LTE3230................................................................ 115 LTE3264: Additional PRS Subframe Configurations.................. 117 LTE3264 benefits........................................................................117 LTE3264 functional description.................................................. 117 LTE3264 system impact............................................................. 118 LTE3264 reference data............................................................. 119 Activating LTE3264.................................................................... 121 Deactivating LTE3264................................................................ 121 LTE3279: Support for Configurable eMBMS SYNC Protocol.....121 LTE3279 benefits....................................................................... 122 LTE3279 functional description.................................................. 122 LTE3279 system impact............................................................. 124 LTE3279 reference data.............................................................125 Activating and configuring LTE3279...........................................127 Configuration details of LTE3279............................................... 129 Deactivating LTE3279................................................................ 130 LTE3290: SRVCC Trigger Enhancement................................... 131 LTE3290 benefits....................................................................... 132 LTE3290 functional description.................................................. 132 LTE3290 system impact............................................................. 133 LTE3290 reference data.............................................................134 Activating and configuring LTE3290...........................................136 Deactivating LTE3290................................................................ 138 LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I............................................................................................... 140

© 2017 Nokia

5


6

3.18.1 3.18.2 3.18.3 3.18.4

LTE3439 benefits....................................................................... 140 LTE3439 functional description.................................................. 140 LTE3439 system impact............................................................. 141 LTE3439 reference data.............................................................142

4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.1.6 4.2 4.2.1 4.2.2 4.2.3 4.2.4

Descriptions of transport and transmission features.................. 143 LTE2807: IPv6 Support for M1 and M3 Interfaces..................... 143 LTE2807 benefits....................................................................... 143 LTE2807 functional description.................................................. 143 LTE2807 system impact............................................................. 147 LTE2807 reference data.............................................................147 Activating and configuring LTE2807...........................................149 Deactivating LTE2807................................................................ 151 LTE2855: Fronthaul Active WDM............................................... 152 LTE2855 benefits....................................................................... 152 LTE2855 functional description.................................................. 152 LTE2855 system impact............................................................. 154 LTE2855 reference data.............................................................154

5 5.1 5.1.1 5.1.2 5.1.3 5.1.4 5.1.5 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.3 5.3.1 5.3.2 5.3.3 5.3.4 5.4 5.4.1 5.4.2 5.4.3 5.4.4

Descriptions of operability features ........................................... 156 LTE684: DHCP Server for Flexi LTE BTS Site Devices............. 156 LTE684 benefits......................................................................... 156 LTE684 functional description.................................................... 156 LTE684 system impact............................................................... 157 LTE684 reference data...............................................................157 Other instructions....................................................................... 158 LTE3134: FDD-LTE 17 System Upgrade................................... 161 LTE3134 benefits....................................................................... 161 LTE3134 functional description.................................................. 162 LTE3134 system impact............................................................. 165 LTE3134 reference data.............................................................166 Upgrading the LTE eNB to LTE 17............................................. 167 Rolling back the upgrade........................................................... 168 LTE3296/SR001527: Harmonized Object Model for SRAN and LTE............................................................................................. 170 LTE3296/SR001527 benefits..................................................... 170 LTE3296/SR001527 functional description................................ 170 LTE3296/SR001527 system impact........................................... 177 LTE3296/SR001527 reference data...........................................178 LTE3303: Enhanced VoLTE, CA, and RF Quality Monitoring.... 179 LTE3303 benefits....................................................................... 179 LTE3303 functional description.................................................. 179 LTE3303 system impact............................................................. 179 LTE3303 reference data.............................................................179

6 6.1

Descriptions of BTS site solution features................................. 184 LTE2495: Plug-in Radio SW Interface for Nokia CPRI ..............184

© 2017 Nokia

DN09237915 Issue: 01A


6.1.1 6.1.2 6.1.3 6.1.4 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.3 6.3.1 6.3.2 6.3.3 6.3.4 6.4

DN09237915 Issue: 01A

LTE2495 benefits....................................................................... 184 LTE2495 functional description.................................................. 184 LTE2495 system impact............................................................. 185 LTE2495 reference data.............................................................186 LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W........................ 186 LTE2769 benefits....................................................................... 187 LTE2769 functional description.................................................. 187 LTE2769 system impact............................................................. 188 LTE2769 reference data.............................................................188 LTE3133: FRCI Flexi RRH 2T2R 875 120 W............................. 189 LTE3133 benefits....................................................................... 189 LTE3133 functional description.................................................. 189 LTE3133 system impact............................................................. 191 LTE3133 reference data.............................................................192 Interdependencies between CPRI-A features and other features.... 193

© 2017 Nokia

7


List of Figures

8

Figure 1

LTE B2 event...................................................................................... 49

Figure 2

PUCCH resource allocation in LTE2664............................................ 56

Figure 3

PUCCH expansion procedure............................................................ 58

Figure 4

PUCCH expansion procedure (systemInfoValueTag > LNBTS: sibUpdateThreshold)..................................................................58

Figure 5

Content of the SIB16, as described in 3GPP TS 36.331....................77

Figure 6

LTE825: Uplink Outer Region Scheduling and LTE3230: UL Interference Offsets feature comparison.......................................... 106

Figure 7

VoLTE call setup with SRVCC delay timer....................................... 132

Figure 8

Handling the SRVCC delay timer during SRVCC (to WCDMA/GSM).... 133

Figure 9

Overview M1/M3 interface................................................................144

Figure 10

M3 interface......................................................................................146

Figure 11

M1 interface......................................................................................146

Figure 12

Fronthaul Active WDM components................................................. 154

Figure 13

Path DHCP Server........................................................................... 159

Figure 14

DHCP configurations........................................................................ 160

Figure 15

Top level objects in the hierarchy..................................................... 171

Figure 16

The EQM and EQM_R object trees..................................................172

Figure 17

The MNL tree....................................................................................174

Figure 18

The MNLENT subtree.......................................................................174

Figure 19

The LNBTS tree................................................................................176

Figure 20

The LNCEL tree................................................................................177

Figure 21

FULL DELIVERY MODE without the LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature...................................................... 185

Figure 22

FAST DELIVERY MODE with the LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature...................................................... 185

© 2017 Nokia

DN09237915 Issue: 01A


List of Tables Table 1

LTE1834: LTE MBMS Service Continuity hardware and software requirements.......................................................................................22

Table 2

New alarms introduced by LTE1834: LTE MBMS Service Continuity..... 22

Table 3

New BTS faults introduced by LTE1834: LTE MBMS Service Continuity............................................................................................22

Table 4

New counters introduced by LTE1834: LTE MBMS Service Continuity.. 23

Table 5

New parameters introduced by LTE1834: LTE MBMS Service Continuity............................................................................................23

Table 6

Existing parameters related to LTE1834: LTE MBMS Service Continuity............................................................................................24

Table 7

LTE1834: LTE MBMS Service Continuity sales information............... 24

Table 8

LTE2410 hardware and software requirements..................................35

Table 9

New parameters introduced by LTE2410........................................... 36

Table 10

LTE2410 sales information................................................................. 36

Table 11


Table 12

New counters introduced by LTE2466................................................40

Table 13

New key performance indicators introduced by LTE2466.................. 41

Table 14


Table 15

Existing parameters related to LTE2466............................................ 42

Table 16


Table 17

Conditions for the inter-RAT measurements period........................... 50

Table 18


Table 19


Table 20


Table 21


Table 22


Table 23

Existing counters related to LTE2664................................................. 61

Table 24


Table 25


Table 26


Table 27


Table 28


Table 29


Table 30

LTE3049 hardware and software requirements for FDD.................... 75

Table 31

LTE3049 hardware and software requirements for TDD.................... 75

Table 32


Table 33

LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) hardware and software requirements................................................. 78

DN09237915 Issue: 01A

© 2017 Nokia

9


10

Table 34

New parameters introduced by LTE3056: GPS and UTC Time Information Broadcast Support (SIB16)..............................................79

Table 35

Parameters modified by LTE3056: GPS and UTC Time Information Broadcast Support (SIB16).................................................................79

Table 36

Existing parameters related to LTE3056: GPS and UTC Time Information Broadcast Support (SIB16)..............................................79

Table 37

Parameters migrated from MOC XPARAM to MOC SIB for LTE3056: GPS and UTC Time Information Broadcast Support (SIB16).............80

Table 38

LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) sales information................................................................................ 80

Table 39


Table 40


Table 41

Existing counters related to LTE3073................................................. 86

Table 42


Table 43

Parameters modified by LTE3073...................................................... 88

Table 44


Table 45


Table 46


Table 47

Existing alarms related to LTE3199.................................................... 95

Table 48

New BTS faults introduced by LTE3199............................................. 95

Table 49


Table 50

Parameters modified by LTE3199...................................................... 96

Table 51

Existing parameters related to LTE 3199........................................... 97

Table 52


Table 53

LTE3201 hardware and software requirements................................101

Table 54

Existing alarms related to LTE3201.................................................. 101

Table 55

Existing BTS faults related to LTE3201............................................ 101

Table 56

New parameters introduced by LTE3201: eMBMS in RAN-sharing Deployment Support.........................................................................102

Table 57

Modified/impacted parameters by LTE3201: eMBMS in RAN-sharing Deployment Support.........................................................................102

Table 58

LTE3201 sales information............................................................... 102

Table 59


Table 60


Table 61

LTE3230: UL Interference Offsets parameter actUlPwrRestrScn configuration cases...........................................................................107

Table 62

LTE3230: UL Interference Offsets hardware and software requirements.....................................................................................109

Table 63

New parameters introduced by LTE3230: UL Interference Offsets........ 110

Table 64

LTE3230: UL Interference Offsets sales information........................ 110

Table 65

LTE3264 hardware and software requirements................................ 119

Table 66

Existing parameters related to LTE3264...........................................119

© 2017 Nokia

DN09237915 Issue: 01A


Table 67


Table 68


Table 69

New counters introduced by LTE3279..............................................125

Table 70

New parameters introduced by LTE3279......................................... 126

Table 71

Existing parameters related to LTE3279.......................................... 126

Table 72


Table 73


Table 74

Existing counters related to LTE3290............................................... 134

Table 75

Existing key performance indicators related to LTE3290................. 135

Table 76


Table 77


Table 78


Table 79


Table 80


Table 81

Explanations: Overview of the M1/M3 interface............................... 144

Table 82


Table 83

Existing alarms related to LTE2807.................................................. 148

Table 84

BTS faults introduced by LTE2807................................................... 148

Table 85


Table 86


Table 87


Table 88


Table 89


Table 90


Table 91


Table 92


Table 93


Table 94


Table 95

LTE3296/SR001527 software requirements.....................................178

Table 96

LTE3296/SR001527 sales information............................................. 179

Table 97


Table 98

E-RAB release due to inter-RAT handovers to UTRAN or GERAN counters introduced by LTE3303...................................................... 180

Table 99

E-RAB release due to S1 interface reasons counters introduced by LTE3303........................................................................................... 180

Table 100

VoLTE PRB usage counter introduced by LTE3303......................... 181

Table 101

HARQ BLER counters introduced by LTE3303................................ 181

Table 102

UE context release counters introduced by LTE3303...................... 182

Table 103

VoLTE TTI bundling counters introduced by LTE3303..................... 182

Table 104

Carrier aggregation (CA) downlink deconfiguration counters introduced by LTE3303.....................................................................182

DN09237915 Issue: 01A

© 2017 Nokia

11


12

Table 105

PMQAP profile counters introduced by LTE3303............................. 183

Table 106


Table 107


Table 108


Table 109

LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W hardware and software requirements...................................................................... 189

Table 110

LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W sales information.. 189

Table 111

FRCI functional specification............................................................ 189

Table 112


Table 113


Table 114

Interdependencies between CPRI-A features and other features.... 193

© 2017 Nokia

DN09237915 Issue: 01A


Summary of changes

Summary of changes Changes between issues 01 (2016-12-30, FDD-LTE17) and 01A (2017-02-03, FDDLTE17) The following features have been updated: Radio Resource Management • • • • • • • • •

LTE1834: eMBMS service continuity (only partly, feature to be split) LTE2466: S1 handover towards hybrid cells LTE2572: RSRQ based B2 LTE2664: Load Based PUCCH Region LTE3056: GPS and UTC time information broadcast support (SIB16) LTE3199: eMBMS capacity enhancement and multi-MBSFN support LTE3230: UL interference offsets LTE3279: Support for configurable eMBMS sync protocol LTE3290: SRVCC trigger enhancement

Operability •

LTE684: DHCP Server for Flexi LTE BTS Site Devices

The following features have been added: BTS Site Solution •

Information on the following features has bee added to the Interdependencies between CPRI-A features and other features section: – – – – – – –

DN09237915 Issue: 01A

LTE3307: UHIE B66a RRH4X45 CPRI-A RRH 4-Pipe 1.7/2.1 160W LTE3308: UHFD AA B25 A + 700/900 P CPRI-A Active Antenna 2-Pipe 1900 80W LTE3309: UHCB RRH2x60-850 CPRI-A RRH 2-Pipe 850 80W LTE3350: UHFF RRH2x60-1900 CPRI-A RRH 2-Pipe 1900 120W LTE3409: UHIF 9768 MRO B4 1W CPRI-A MRO RRH 2-Pipe 1700/2100 LTE3410: UHIG 9768 cMRO B4/66 5W CPRI-A MRO RRH 2-Pipe 1700/2100 LTE3413: UHBF 9768 MRO B13 1W CPRI-A MRO RRH 2-Pipe 700

© 2017 Nokia

13

Introduction


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

14

© 2017 Nokia

DN09237915 Issue: 01A


Activating and deactivating LTE features using BTS Site Manager

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

Steps

1

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

2

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

3

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

DN09237915 Issue: 01A

© 2017 Nokia

15

Activating and deactivating LTE features using BTS Site Manager

4


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

5

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

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

g

16

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

© 2017 Nokia

DN09237915 Issue: 01A


Descriptions of radio resource management and telecom features

3 Descriptions of radio resource management and telecom features 3.1 LTE1834: LTE MBMS Service Continuity The LTE1834: LTE MBMS Service Continuity feature is a package of functionalities introduced for multimedia broadcast/multicast service (MBMS) operation in networks with multiple carriers deployed. The feature enables UEs to receive MBMS services in a radio resource control (RRC) idle mode as well as in an RRC-connected mode.

3.1.1 LTE1834 benefits The LTE1834: LTE MBMS Service Continuity feature provides the following benefit: •

It enables the operators to offer seamless MBMS broadcast services to end users in multi-carrier LTE networks.

3.1.2 LTE1834 functional description Functional description The LTE1834: LTE MBMS Service Continuity feature is a package of functionalities required for MBMS operation in a multi-carrier deployment where MBMS services are available only on a subset of carriers. An eNB transmit system information broadcast 15 (SIB15), containing the information about the availability of MBMS service area identifiers (SAIs), on the serving frequency of a cell as well as on other frequencies to support the UEs in an RRC idle mode. The SIB15 contains also useful information for UE-based or UE-assisted positioning methods. After reading SIB15, the UEs in an RRC connected mode may send an MBMS Interest Indication (MBMS II) to the eNB, listing LTE frequencies on which they want to receive the MBMS services. The eNB uses this MBMS II to keep the UE interested in MBMS services on those frequencies. If, on the other hand, a certain UE is interested in different frequencies than the serving one, the eNB tries to move the UE to the frequency of interest. The eNB supports a broadcast of SIB15 in MBMS cells and non-MBMS cells. This broadcast indicates SAI lists to all UEs in an RRC idle and RRC connected mode. The exchange of a SAI list via an X2 link is not supported. The primary cell (PCell) of eNB supports the reception of MBMS II sent by the UEs in an RRC connected mode. The eNB uses the MBMS II for the UE’s mobility decisions. The eNB does its best to ensure that the UE is able to receive MBMS and unicast services simultaneously. If a UE indicates an interest in an MBMS frequency that is the secondary cell (SCell) carrier frequency, the eNB triggers a PCell swap procedure to steer the UE to the MBMS layer.

DN09237915 Issue: 01A

© 2017 Nokia

17



Emergency and high priority calls are the subject of MBMS-based mobility only if they are not impacted. Emergency calls' mobility is always prioritized over MBMS. The LTE1834: LTE MBMS Service Continuity feature is supported in 1.4-MHz, 3-MHz and 5-Mhz cells in a limited scope. SIB15 contains only an inter-frequency eMBMS SAI list. The eMBMS is not supported in narrowband cells, so the cells do not need the functionality which keeps the UE interested in an eMBMS serving frequency. Subfeatures The LTE1834: LTE MBMS Service Continuity feature is split into three subfeatures: •

The LTE1834-A: MBMS Service Continuity Suport for Idle Mode UE subfeature has the following functionalities: – –

•

The LTE1834-B: Keep RRC CONNECTED MBMS Interested UE on MBMS Carrier subfeature has the following functionalities: – – – – –

•

feature activation transmission of SIB15

handling an MBMS Interest Indication received from a UE forwarding an MBMS Interest Indication during handover excluding a UE with an MBMS interest on a serving frequency from a load-based handover excluding a UE with MBMS interest on serving frequency (optionally) from a service-based handover excluding a UE with an MBMS interest on a serving frequency from idle mode load balancing

The LTE1834-C: Move RRC CONNECTED MBMS Interested UE to MBMS Carrier subfeature has the following functionalities: – –

best-effort-service-based-handover for a UE with an MBMS interest in a nonserving frequency PCell swap for a UE with an MBMS interest in a frequency of a configured SCell

3.1.3 LTE1834 system impact Interdependencies between features The following features interact with the LTE1834: LTE MBMS Service Continuity feature: •

•

•

18

LTE1117: LTE MBMS The LTE1117: LTE MBMS feature should be enabled in the ecosystem, but its enabling is not a precondition to activate the LTE1834: LTE MBMS Service Continuity feature. LTE1127: Service-based Mobility Trigger The LTE1127: Service-based Mobility Trigger feature introduced a best effort HO based on A4 measurements to send a UE to another frequency. Activation of the LTE1127: Service-based Mobility Trigger feature is not a precondition for the LTE1834: LTE MBMS Service Continuity feature, the implemented functions are simply reused. LTE2275: PCell Swap

© 2017 Nokia

DN09237915 Issue: 01A



The LTE1834: LTE MBMS Service Continuity feature requests a PCell swap in case a UE with established SCell(s) indicated MBMS interest in the frequency of a configured SCell. The LTE2275: PCell Swap feature needs to be activated to support this option. The LTE2275: PCell Swap feature is no mandatory precondition for the LTE1834: LTE MBMS Service Continuity feature; however, the performance of LTE1834: LTE MBMS Service Continuity will be reduced without LTE2275: PCell Swap as SCells will not be reported by a regular A4 measurement. Thus, no best effort HO can be done towards a configured SCell.

g

Note: A PCell swap triggered for MBMS traffic steering will not be considered when counting the load-based PCell swaps for triggering a load balancing (LB) PCell swap. The LTE1834: LTE MBMS Service Continuity feature impacts the following features: •

• •

• • • • •

• • • • •

• • • •

DN09237915 Issue: 01A

LTE1534: Multiple Frequency Band Indicator LTE1534: Multiple Frequency Band Indicator introduces general support for multiple frequency band indicators (MFBIs) for UEs in an RRC-idle and RRC-connected mode. The MFBI functionality is supported for homogenous network deployments, that is, the same MFBI configuration is applied to all eNBs. SIB15 allows to broadcast multiple frequency bands for inter-frequency MBMS configurations. Only if LTE1534: Multiple Frequency Band Indicator is activated, the LTE1834: LTE MBMS Service Continuity feature shall support the broadcast of multiple frequency bands for inter-frequency MBMS configurations. LTE53: Intra- and Inter-eNodeB Handover with X2 LTE54: Intra-LTE Handover via S1 The intra-LTE handover functionality has to be extended to transfer MBMS II from a source cell to a target cell. Furthermore, all features reusing the intra-LTE handover preparation from the LTE53: Intra- and Inter-eNodeB Handover with X2 or LTE54: Intra-LTE Handover via S1 features are impacted in the same way. LTE1387: Intra-eNodeB IF Load Balancing LTE1170: Inter-eNodeB IF Load Balancing LTE1531: Inter-frequency Load Balancing Extension LTE1357: LTE-UTRAN Load Balancing LTE1841: Inter-frequency Load Equalization The five features above make use of a load-based handover. They are extended to exclude a UE interested in MBMS from LBHO. LTE487: Idle Mode Mobility Load Balancing LTE1677: Idle Mode Mobility Balancing Extensions LTE2050: Load Triggered Idle Mode Mobility Load Balancing LTE2601: CA Aware Idle Mode Mobility Load Balancing LTE2051: Measurement Based Idle Mode Mobility Load Balancing The five features above are extended to exclude a UE interested in MBMS from idle mode load balancing. This feature is extended to immediately release a UE which is executing A4 measurements for idle mode load balancing when an MBMS II is received. LTE1127: Service-based Mobility Trigger LTE55: Inter-frequency Handover LTE1060: TDD – FDD Handover LTE56: Inter-RAT Handover to WCDMA

© 2017 Nokia

19


• • • • •

•

•

•

•

•

•

• • •

20


LTE872: SRVCC to WCDMA LTE442: eNACC to GSM LTE873: SRVCC to GSM LTE898: TDD inter-RAT Handover to TD-SCDMA LTE60: Inter-RAT Handover to eHRPD/3GPP2 The eight features above make use of either A3/A5 inter-frequency measurements or B2 inter-RAT measurements if an A2 measurement indicates that the radio conditions in the serving cell have become so bad that an inter-frequency or an interRAT handover due to radio reasons is desirable. A4 measurements for an MBMS steering HO shall be deconfigured when A3, A5, or B2 is set up. LTE2224: Uplink-triggered Mobility This feature makes use of either A3/A5 inter-frequency measurements and/or B1/B2 inter-RAT measurements if an eNB internal trigger indicates that the radio conditions in the serving cell have become so bad that an inter-frequency or an inter-RAT handover due to radio reasons is desirable. A4 measurements for MBMS steering HO shall be deconfigured when A3, A5, B1, or B2 is set up. LTE2108: Redirected VoLTE Call Setup This feature introduces forced service-based handover (SBHO) to move a UE which wants to set up a quality class indicator 1 (QCI1) but is served in a cell which does not allow a setup of QCI1 towards another frequency, where the setup of QCI1 is allowed. Forced SBHO according to the LTE2108: Redirected VoLTE Call Setup feature shall always have a priority over MBMS call steering according to the LTE1834: LTE MBMS Service Continuity feature. LTE2503: Emergency Call Based Mobility Trigger This feature extends the behavior of LTE1127: Service-based Mobility Trigger to enforce SBHO for a UE with emergency allocation and retention priority (ARP). SBHO for EC UE according to the LTE2503: Emergency Call Based Mobility Trigger feature shall have a priority over MBMS interest. LTE2612: ProSe Direct Communications for Public Safety This feature includes the functionality to keep a UE with sidelink interest on the current serving frequency. Therefore, no A4 measurements are configured for a sidelink interested UE at all. It is assumed that the sidelink interest of a UE (which is for public safety purposes) shall always have a priority over MBMS interest (which is most likely for a commercial service in early deployments). Therefore, no A4 measurements for an MBMS steering handover are configured for a UE with sidelink interest. LTE572: IMS Emergency Sessions This feature introduces the support for emergency sessions. In case an emergency call (with QCI1 with emergency ARP) is present, an eNB shall always prioritize SBHO over MBMS steering HO, ignoring operator's prioritization. LTE556: ANR Intra-LTE, Inter-frequency – UE-based This feature makes use of A4 measurements intended for service-based handover or load-based handover for passive ANR detection. With the LTE1834: LTE MBMS Service Continuity feature, the LTE556: ANR Intra-LTE, Inter-frequency – UE-based feature may make use of A4 measurements for MBMS steering handover as well. LTE163: Subscriber and Equipment Trace LTE433: Cell Trace LTE644: Configurable Cell Trace Content The three features above are tracing RRC messages. They are extended to support the new RRC message MBMS II introduced by the LTE1834: LTE MBMS Service Continuity feature.

© 2017 Nokia

DN09237915 Issue: 01A


•

• • •

•


LTE2057: Extended Measurement Control This feature introduced mechanisms to select a set of inter-frequency measurement objects to be configured in a UE considering the maximum number of measurement objects allowed. This mechanism shall be applied to the A4 measurements for MBMS steering HO. It is the last step in the selection process for measurements after the frequencies within the MBMS II have been filtered for other criterias (for example, mobility profiles). LTE2585: MDT Inter-frequency UE Periodic Measurement LTE3348: MDT Inter-RAT UE Periodic Measurement of GSM LTE3272: MDT Inter-RAT UE Periodic Measurement of UTRAN The three MDT feature candidates above will require inter-frequency measurements which might need measurement gaps. A UE interested in MBMS should therefore be excluded. As these features are expected to come later than LTE1834: LTE MBMS Service Continuity, it is up to these features to specify the interdependency. LTE2834: PCell Swap Enhancements This feature introduces an inter-eNB PCell swap. Only with the LTE2834: PCell Swap Enhancements feature, it will be possible to move an MBMS-interested UE to a configured inter-eNB SCell. (The configured SCells will not be reported by A4, so also no regular handover will be possible.) As the LTE2834: PCell Swap Enhancement feature is expected to come later than LTE1834: LTE MBMS Service Continuity, it is up to the LTE2834: PCell Swap Enhancement feature to specify the interdependency.

Impact on interfaces The LTE1834: LTE MBMS Service Continuity feature impacts interfaces as follows: •

S1 –

•

X2 –

•

Adds support for mbmsInterestIndication-r11 within the RRC container of the S1AP: HANDOVER REQUIRED message and S1AP: HANDOVER REQUEST message.

Adds support for mbmsInterestIndication-r11 within the RRC container of the X2AP: HANDOVER REQUEST message.

RRC – –

Adds support for the new RRC message RRC:MBMSInterestIndication. Adds support for SIB15

Impact on network management tools The LTE1834: LTE MBMS Service Continuity feature has no impact on network management tools. Impact on system performance and capacity The LTE1834: LTE MBMS Service Continuity feature does not impact on system performance. The LTE1834: LTE MBMS Service Continuity feature impacts system capacity as follows:

DN09237915 Issue: 01A

© 2017 Nokia

21


•


As MBMS interested UEs are excluded from load balancing, the total number of UEs available for load balancing is reduced. If too many UEs are MBMS interested, the performance of the load balancing algorithms may be reduced, resulting in a reduced overall capacity. The effect can hardly be quantified.

3.1.4 LTE1834 reference data Requirements Table 1

LTE1834: LTE MBMS Service Continuity hardware and software requirements

System release FL17

Flexi Multiradio BTS not supported

Flexi Zone Controller FL17

Flexi Air Scale BTS Multiradio 10 BTS FL17

OMS FL17

FL17 UE

not applicable

Flexi Zone Micro BTS FL17

NetAct NetAct 17.2

Flexi Zone Access Point FL17

MME

SAE GW

not applicable

not applicable

Alarms Table 2

New alarms introduced by LTE1834: LTE MBMS Service Continuity

Alarm ID

7655

Alarm name

CELL NOTIFICATION

For alarm descriptions, see LTE Radio Access Operating Documentation/Reference/Alarms and Faults. BTS faults and reported alarms Table 3

New BTS faults introduced by LTE1834: LTE MBMS Service Continuity

Fault ID

5502

Fault name

Reported alarms Alarm ID

SIB15 information incomplete

7655

Alarm name

CELL NOTIFICATION

For fault descriptions, see LTE Radio Access Operating Documentation/Reference/Alarms and Faults. Commands There are no commands related to the LTE1834: LTE MBMS Service Continuity feature. Measurements and counters

22

© 2017 Nokia

DN09237915 Issue: 01A


Table 4


New counters introduced by LTE1834: LTE MBMS Service Continuity

Counter ID

Counter name

Measurement

M8030C Number of MBMS Service based 13 Handover Attempts

8030 - LTE MBMS (WBTS)

M8030C Number of MBMS Service based 14 Handover Successes


M8030C Number of MBMS Service based 15 Handover Failures due to timer


M8051C Average number of UEs with 127 MBMS interest

8051 - LTE UE Quantity (WBTS)

M8030C Number of Carrier Aggregation 17 PCell swap completions for MBMS Steering


M8051C Average Number of MBMS 129 interested UEs with configured measurement gap


M8030C Number of Successful 16 Handovers Leaving Interested MBMS Frequency


M8030C 12


Number of MBMS Service based Handover Preparation Attempts

M8051C Maximum number of UEs with 128 MBMS interest


For counter descriptions, see LTE Radio Access Operating Documentation/Reference/Counters and Key Performance Indicators. Key performance indicators There are no key performance indicators related to the LTE1834: LTE MBMS Service Continuity feature. Parameters Table 5

New parameters introduced by LTE1834: LTE MBMS Service Continuity Full name

Abbreviated name

Managed object

Parent structure

Inter-freq. service based threshold for RSRP target filter

thresholdRsrpIFSB LNHOIF Filter

-

Inter-freq. service based HO retry timer

iFServiceBasedHoR LNCEL etryTimer

-

Prioritize VoLTE over MBMS

prioritizeVoLTEov LNBTS erMBMS

-

Activate MBMS service continuity

actMBMSServiceCon LNBTS tinuity

-

SIB15 Profile (SIB15PR) sib15PrId identifier

DN09237915 Issue: 01A

© 2017 Nokia

SIB15PR

-

23


Table 5


New parameters introduced by LTE1834: LTE MBMS Service Continuity (Cont.) Full name

Abbreviated name

Managed object

Parent structure

Inter frequency MBMS SAI list (IRSAILIST) identifier

irSaiListId

IRSAILIS T

-

SIB15 profile identifier

sib15ProfileId

SIB

-

SAI list of intrafrequency neighbor cells

saiListIntraFreqN SIB eighbors

-

MBMS service area identity list of the cell

saiListIntraFreq

SIB15PR

-

Downlink Earfcn of the MBMS service area identity list

saiListEarfcnDl

IRSAILIS T

-

SAI list of interfrequency neighbor cells

saiListInterFreqN IRSAILIS eighbors T

-

Table 6

Existing parameters related to LTE1834: LTE MBMS Service Continuity Full name

Abbreviated name

Managed object

Parent structure

System Information Scheduling List

sibSchedulingList SIB

-

SIB Type

siMessageSibType

SIB

-

MBMS Service Area

mbmsServiceArea

MBSFN

-

MBMS Service Area list

mbmsSaiList

MBSFN

-

For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 7

LTE1834: LTE MBMS Service Continuity sales information

Product structure class Application software (ASW)

24

License control Pool license

© 2017 Nokia

Activated by default No

DN09237915 Issue: 01A



3.1.5 Activating LTE1834: LTE MBMS Service Continuity Procedure 1

Start the BTS Site Manager application and establish the connection to the BTS.

2

Start commissioning. 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

5

Set the Activate MBMS service continuity (actMBMSServiceContinuity) value to true.

6

Configure the LTE1834: LTE MBMS Service Continuity feature. For a detailed description of the configuration procedure, see Configuring LTE1834: LTE MBMS Service Continuity.

7

Send the commissioning plan file to the BTS. Sub-steps a) Go to the Send Parameters page. b) Select an appropriate Send option. • •

DN09237915 Issue: 01A

If the BTS has not been commissioned, select All parameters. If the BTS has been already commissioned, select Only changes.

© 2017 Nokia

25



c) Click Send Parameters.

Result The eNB broadcasts SIB15 in all configured cells.

3.1.6 Configuring LTE1834: LTE MBMS Service Continuity Purpose This procedure is neccessary to configure the cells in which eNB broadcast SIB15. For this configuration the following procedures have to be performed in sequential order. Before you start The LTE1834: LTE MBMS Service Continuity feature is activated; the Activate MBMS service continuity (actMBMSServiceContinuity) parameter is set to true. For the activation of the LTE1834: LTE MBMS Service Continuity feature see Activating LTE1834: LTE MBMS Service Continuity Procedure

3.1.6.1

1

Configuring Prioritize VoLTE over MBMS (prioritizeVoLTEoverMBMS) and interfrequency related parameters

2

Assigning a SIB15 profile with the SIB15 profile identifier (sib15ProfileId) parameter

3

Configure SAIs of inter-frequency neighbor cells in SIB15PR

4

Configure SAIs of intra-frequency neighbor cells

5

Adding a list item to the SIB instance of any cell which shall broadcast SIB15

Configuring Prioritize VoLTE over MBMS (prioritizeVoLTEoverMBMS) and inter-frequency related parameters Purpose This procedure is necessary to configure Prioritize VoLTE over MBMS (prioritizeVoLTEoverMBMS) and inter-frequency related parameters.

26

© 2017 Nokia

DN09237915 Issue: 01A



Procedure 1


2


3

Configure the Prioritize VoLTE over MBMS (prioritizeVoLTEoverMBMS) parameter to the desired value.

4

Go to the LNCEL object. Object path: MRBTS ► LNBTS ► LNCEL

5

Configure the Inter-freq. service based HO retry timer (iFServiceBasedHoRetryTimer) parameter to the desired value. Repeat this step in all LNCEL instances where needed.

6

Go to the LNHOIF object. Object path: MRBTS ► LNBTS ► LNCEL ► LNHOIF

7

Configure either the Inter-freq. service based threshold RSRP target filter (thresholdRsrpIFSBFilter) or Inter-freq.

service based threshold RSRQ target filter (thresholdRsrqIFSBFilter) parameter in all LNHOIF instances. Repeat this step in all LNHOIF instances where needed. Procedure result The Prioritize VoLTE over MBMS (prioritizeVoLTEoverMBMS) parameter and inter-frequency related parameters are configured. 8

3.1.6.2

Continue with Assigning a SIB15 profile with the SIB15 profile identifier (sib15ProfileId) parameter

Assigning a SIB15 profile with the SIB15 profile identifier (sib15ProfileId) parameter Purpose This feature is related to configuring the LTE1834: LTE MBMS Service Continuity feature and is necessary if assigning a SIB15 profile is needed. Before you start The succesfull completion of Configuring Prioritize VoLTE over MBMS (prioritizeVoLTEoverMBMS) and inter-frequency related parameters is required.

DN09237915 Issue: 01A

© 2017 Nokia

27



Procedure 1


2


3

Create a SIB15 profile. Sub-steps a) Right-click the LNBTS object. b) Select New and find the SIB15PR object. c) Configure the SIB15 profile (SIB15PR) identifier (sib15PrId) parameter to the desired value.

4

Assign the SIB15 newly created profile with sib15ProfileId Sub-steps a) Go to the SIB object. Object path: MRBTS ► LNBTS ► LNCEL ► SIB b) Assign the value configured for the SIB15 profile (SIB15PR) identifier (sib15PrId) parameter to the SIB15 profile identifier (sib15ProfileId) parameter. Repeat all the sub-steps of this step in all SIB instances where needed.

Procedure result A SIB15 profile is assigned. 5

3.1.6.3

Continue with Configure SAIs of inter-frequency neighbor cells in SIB15PR

Configure SAIs of inter-frequency neighbor cells in SIB15PR Purpose This procedure is related to configuring the LTE1834: LTE MBMS Service Continuity feature and is necessary if service area identifiers (SAIs) for the referencing cell and for inter-frequency neighbor cells shall be broadcasted. Before you start

28

© 2017 Nokia

DN09237915 Issue: 01A



The succesfull completion of Assigning a SIB15 profile with the SIB15 profile identifier (sib15ProfileId) parameter is required. Procedure 1


2

Go to the SIB15PR object. Object path: MRBTS ► LNBTS ► SIB15PR

3

Configure the SAI list of inter-frequency neighbor cells (saiListInterFreqNeighbors) object. Sub-steps a) Right-click the SIB15PR object. b) Select New and find the IRSAILIST object. c) Configure the Inter frequency MBMS SAI list (IRSAILIST) identifier (irSaiListId) parameter to the desired value. d) Configure the Downlink earfcn of the MBMS service area identity list (saiListEarfcnDl) parameter to the desired value. e) Go to the SAI list of inter-frequency neighbor cells object. Object path: MRBTS ► LNBTS ► SIB15PR ► IRSAILIST ► SAI list of interfrequency neighbor cells f)

Configure the SAI list of inter-frequency neighbor cells (saiListInterFreqNeighbors) parameter to the desired value.

Procedure result Service area identifiers (SAIs) for the referencing cell and for inter-frequency neighbor cells shall be broadcasted.

DN09237915 Issue: 01A

© 2017 Nokia

29


4

3.1.6.4


Continue with Configure SAIs of intra-frequency neighbor cells

Configure SAIs of intra-frequency neighbor cells Purpose This procedure is related to configuring the LTE1834: LTE MBMS Service Continuity feature and is necessary if service area identifiers (SAIs) for the referencing cell and intra-frequency neighbor cells shall be broadcasted. Before you start The succesfull completion of Assigning a SIB15 profile with the SIB15 profile identifier (sib15ProfileId) parameter is required. Procedure 1


2

Go to the SIB object. Object path: MRBTS ► LNBTS ► LNCEL ► SIB

3

Configure the SAI list of intra-frequency neighbor cells (saiListIntraFreqNeighbors) object. Sub-steps a) Right-click the SIB object. b) Select New and find the SAI list of intra-frequency neighbor cells object. c) Configure the SAI list of intra-frequency neighbor cells (saiListIntraFreqNeighbors) parameter to the desired value. Repeat all the sub-steps of this step in all SIB instances where needed.

4

Go to the SIB15PR object. Object path: MRBTS ► LNBTS ► SIB15PR

30

© 2017 Nokia

DN09237915 Issue: 01A


5


Configure the MBMS service area identity list of the cell (saiListIntraFreq) object. Sub-steps a) Right-click the SIB15PR object. b) Select New and find the MBMS service area identity list of the cell object. c) Configure the MBMS service area identity list of the cell (saiListIntraFreq) parameter to the desired value.

g g

Note: Please note that the sum of SAIs configured in the lists saiListIntraFreq and saiListIntraFreqNeighbors of a referencing cell is maximum 63. If saiListIntraFreqNeighbors is not configured in any referencing cell the maximum number of SAIs in saiListIntraFreq is 64. eNB will omit SAIs if one of the above limits is exceeded! Note: One or more SAIs may not be broadcasted if the sum of SAIs configured with parameters saiListIntraFreqNeighbors, saiListIntraFreq and saiListInterFreqNeighbors exceeds the maximum available SIB15 length of a cell. In this case, a 'SIB15 information incomplete' warning will be reported. Procedure result Service area identifiers (SAIs) for the referencing cell and intra-frequency neighbor cells shall be broadcasted. 6

3.1.6.5

Continue with Adding a list item to the SIB instance of any cell which shall broadcast SIB15

Adding a list item to the SIB instance of any cell which shall broadcast SIB15 Purpose This procedure is related to configuring the LTE1834: LTE MBMS Service Continuity feature and adds a list item to the SIB instance of any cell which shall broadcast SIB15. Before you start The succesfull completion of Configure SAIs of intra-frequency neighbor cells is required.

DN09237915 Issue: 01A

© 2017 Nokia

31



Procedure 1


2

Add a list item to the SIB instance of any cell which shall broadcast SIB15. Sub-steps a) Right-click the SIB object. b) Select New and find the System information scheduling list object. c) Configure the Periodicity (siMessagePeriodicity) parameter to the desired value. d) Configure the Repetition (siMessageRepetition) parameter to the desired value. e) Set the SIB type (siMessageSibType) parameter to the value SIB15. Repeat all the sub-steps of this step in all SIB instances where needed.

3




Result The cells in which eNB broadcast SIB15 are configured.

32

© 2017 Nokia

DN09237915 Issue: 01A



3.1.7 Deactivating LTE1834: LTE MBMS Service Continuity Before you start The LTE1834: LTE MBMS Service Continuity feature is activated; the Activate MBMS service continuity (actMBMSServiceContinuity) parameter is set to true. Procedure 1


2


3


4


5

Set the Activate MBMS service continuity (actMBMSServiceContinuity) value to false.

6


DN09237915 Issue: 01A


© 2017 Nokia

33




Result The eNB stops broadcasting SIB15 in all cells.

3.2 LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls The LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature introduces an enhancement of the existing roaming and access restrictions algorithm during circuit-switched fallback (CSFB). This allows distinguishing emergency and high-priority calls from one another.

3.2.1 LTE2410 benefits The LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature provides the following benefit: •

distinction between emergency and high-priority access calls, which meets the requirements of 3GPP standard

3.2.2 LTE2410 functional description Emergency call (EC) and high-priority access (HPA) calls during CSFB both have a high priority indicator; therefore, the eNB is not able to distinguish them. Since ECs have a higher priority than HPA calls, the intention of 3GPP is to introduce a distinction between the two call types in order to apply different roaming and access restrictions. The LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature enables the eNB to distinguish between an emergency call and a high-priority call. This allows to apply restrictions only in the case of high-priority calls. During an emergency call, a handover restriction list (HRL) is not applied. Current behavior of a roaming and access restriction handling based on HRL An eNB checks the HRL and, if the CSFB indicator is set to a high-priority indication value, the additional CSFB indicator IE is checked as well. The following options are possible: •

•

•

34

An additional CSFB indicator IE is set to No restriction – emergency call is ongoing; HRL is not taken into account at all (neither for a CSFB packet switch (PS) HO nor CSFB redirection) An additional CSFB indicator IE is set to Restriction – high-priority access call is ongoing; HRL is taken into account, and the eNB applies the received roaming and access restriction (both for CSFB PS HO and CSFB redirection) An additional CSFB indicator IE is missing – current behavior, without the LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature; the eNB applies restrictions from HRL, received for an emergency call, and checks if the

© 2017 Nokia

DN09237915 Issue: 01A



target list is empty after applying the HRL restrictions. If the target list is not empty, the restricted target list with HRL checks is used. If the target list is empty, HRL checks are reverted and a full target list is used.

g

Note: If the LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature is disabled, the behavior of the network from previous releases is kept.

3.2.3 LTE2410 system impact Interdependencies between features The LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature impacts the following features: LTE22: Emergency Call Handling With the LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature activated, an eNB will distinguish between the EC and HPA call and apply different algorithms for roaming and access restrictions in both cases. In the case of EC, the eNB will not apply any restrictions from HRL. LTE572: IMS Emergency Sessions With the LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature activated, an eNB will distinguish between an EC and HPA call and apply different algorithms for roaming and access restrictions in both cases. In the case of EC, the eNB will not apply any restrictions from HRL. LTE736: CS Fallback to UTRAN With the LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature activated, an eNB will distinguish between an EC and HPA call and apply different algorithms for roaming and access restrictions in both cases.

•

•

•

Impact on interfaces The LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature has no impact on interfaces. Impact on network management tools The LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature has no impact on network management tools. Impact on system performance and capacity The LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature has no impact on system performance or capacity.

3.2.4 LTE2410 reference data Requirements Table 8 System release FDD-LTE 17

DN09237915 Issue: 01A

LTE2410 hardware and software requirements Flexi Multiradio BTS not supported

Flexi Multiradio 10 BTS FL17

© 2017 Nokia

AirScale

FL17



35


Table 8


LTE2410 hardware and software requirements (Cont.)


OMS

UE

LTE OMS16A

3GPP R8 mandatory

NetAct

MME

NetAct 17.2

SAE GW

support not required


Alarms There are no alarms related to the LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature. Commands There are no commands related to the LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature. Measurements and counters There are no measurements or counters related to the LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature. Key performance indicators There are no key performance indicators related to the LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls feature. Parameters Table 9

New parameters introduced by LTE2410 Full name

Abbreviated name

Managed object

Activate CSFB EC access actCsfbECRestrRem LNBTS restriction removal

Parent structure –


LTE2410 sales information

Product structure class Basic Software (BSW)

License control –

Activated by default Yes

3.3 LTE2466: S1 Handover towards Hybrid Cells The LTE2466: S1 Handover towards Hybrid Cells feature enhances the LTE54: Intra-LTE Handover via S1 feature with a possibility of handovers towards hybrid cells. Hybrid cells are the closed-subscriber-group (CSG) cells which allow a non-CSG members to access

36

© 2017 Nokia

DN09237915 Issue: 01A



it. The access is granted with an operator-configurable range of hybrid physical cell identities (PCIs). The range is set in the serving eNB and defines a list of neighboring cells towards which a handover is allowed.

3.3.1 LTE2466 benefits The LTE2466: S1 Handover towards Hybrid Cells feature enables any user equipment (UE) to sustain the connection in a situation of handover towards a cell normally configured as closed-subscriber-group (CSG) cell.

3.3.2 LTE2466 functional description Hybrid cells A hybrid cell allows non-closed-subscriber-group (non-CSG) users to access it even if it is defined as a closed-subscriber-group (CSG) cell (that is, one which is deliberately reserved for a family or an institution). The LTE2466: S1 Handover towards Hybrid Cells feature preserves the access priority for the CSG users and if the hybrid cell is overloaded, none of non-CSG users can access it. The operator can set a cell as hybrid only for neighboring cells, and the definition is done in the serving eNB by setting a dedicated range of physical cell IDs (PCI). Additionaly, a carrier frequencies need to be defined for each PCI with a dedicated EUTRA carrier frequency (freqEutra) LNHBD parameters. The range is defined with the Hybrid neighbor first PCI (pciFirst) and Hybrid neighbor last PCI (pciLast) LNHBD parameters. The values are set within the 0–503 range.

g

Note: The PCI range defined for hybrid cells cannot overlap with the following PCI ranges: • •

Home eNB PCI range CSG PCI range

S1-based handover towards hybrid cells The PCI range of hybrid neighbor cells is defined per eNB and is reused at the first stage of handover; that is, when user equipment (UE) creates a measurement report including a PCI. If the received PCI falls into the hybrid PCI range, the cell in question is a hybrid cell. After the cell is selected as a target, an eNB starts a reportCGI procedure to retrieve the following information required to initiate an S1 handover from the UE: • • • •

ID of target eNB because the PCIs can be reused accross eNBs CSG ID of a target cell tracking area code (TAC) public land mobile network ID (PLMN)

Handovers towards hybrid cells can be prioritized and de-prioritized to, for example, limit the number of outdoor UEs getting connected to the indoor cell. There are dedicated operator-configurable offsets for all PCIs in the hybrid range for a given frequency. Configuration is done with the Hybrid cell individual offset (cellIndOff) LNHBD parameter.

DN09237915 Issue: 01A

© 2017 Nokia

37



Monitoring the S1-based handover to hybrid cells The LTE2466: S1 Handover towards Hybrid Cells feature allows the operator to monitor the execution of S1-based handover towards hybrid cells. For that purpose, there are new monitoring possibilities introduced, which can be divided into the following categories: •

Monitoring the success rate of reportCGI procedure with the following counters: – – –

•

Monitoring the success rate of inter-eNB S1 handover to hybrid cells with the following counters: – – – – – – –

•

Number of requested SI reports for hybrid cells Number of successful SI reports for hybrid cells Number of incomplete SI reports for hybrid cells

Inter-eNB S1 handover preparations to hybrid cell Failed inter-eNB S1 handover preparations to a hybrid cell due to expiration of guarding timer Failed inter-eNB S1 handover preparations to a hybrid cell due to admission control in the target eNB Failed inter-eNB S1 handover preparations to a hybrid cell due to other reasons Attempted inter-eNB S1 handover to a hybrid cell Successful inter-eNB S1 handover to a hybrid cell Failed Inter-eNB S1 handover to hybrid cell due to timer expiry

Monitoring the VoLTE-specific success rate of inter-eNB S1 handover to hybrid cells with the following counters: – – –

Inter-eNB S1 handover preparations for VoLTE (QCI1) to a hybrid cell Attempted Inter-eNB S1 handover for VoLTE (QCI1) to a hybrid cell Successful Inter-eNB S1 handover for VoLTE (QCI1) to a hybrid cell

3.3.3 LTE2466 system impact Interdependencies between features The following features must be activated before activating the LTE2466: S1 Handover towards Hybrid Cells feature: •

LTE54: Intra-LTE Handover via S1

The following features are not supported for hybrid neighboring cells when the LTE2466: S1 Handover towards Hybrid Cells feature is enabled: • • • • • • • •

38

LTE533: Mobility Robustness LTE956: MRO Evolution LTE1617: RLF-triggered Handover LTE1140: Intra-frequency Load Balancing LTE1113: eICIC – Macro LTE1496: eICIC – Micro LTE1841: Inter-Frequency Load Equalization LTE492: ANR

© 2017 Nokia

DN09237915 Issue: 01A


• •


LTE556: ANR Intra-LTE, Inter-frequency – UE-based LTE782: ANR Fully-UE-based

The LTE2466: S1 Handover towards Hybrid Cells feature impacts the following features: •

•

LTE1442: Open Access Home eNodeB Mobility The home eNB PCI range defined with the LTE1442: Open Access Home eNodeB Mobility feature cannot overlap with the PCI range defined with the LTE2466: S1 Handover towards Hybrid Cells feature for the same frequency. LTE2351: S1-based Handover towards CSG Cells The PCI range defined with the LTE2351: S1-based Handover towards CSG Cells feature for a closed-subscriber-group (CSG) cell cannot overlap with the PCI range for a given frequency defined with the LTE2466: S1 Handover towards Hybrid Cells feature.

The LTE2466: S1 Handover towards Hybrid Cells feature is impacted by the following features: •

•

•

•

•

LTE55: Inter-frequency Handover The LTE55: Inter-frequency Handover feature must be enabled to allow an interfrequency S1 handover to a hybrid cell. LTE1060: TDD – FDD Handover The LTE1060: TDD – FDD Handover feature must be enabled to allow an S1 handover to a hybrid cell from a different technology (FDD/TDD). LTE1127: Service-based Mobility Trigger The LTE1127: Service-based Mobility Trigger feature must be enabled to allow a service-based handover to a hybrid cell. LTE1387: Intra-eNodeB Inter-frequency LB, LTE1170: Inter-frequency Load Balancing Management Data, LTE1531: Inter-frequency Load Balancing Extension The features must be enabled to allow a load-balancing-based handover to a hybrid cell. LTE2503: Emergency Call-based Mobility Trigger The LTE2503: Emergency Call-based Mobility Trigger feature must be enabled to allow an emergency-call-based handover to a hybrid cell.

Impact on interfaces The LTE2466: S1 Handover towards Hybrid Cells feature impacts interfaces as follows: •

S1AP interface –

Handover Required message is updated with the following information elements (IE) defining the target cell: • •

an identifier for a closed subscriber group (CSG ID) Cell Access Mode

Impact on network management tools The LTE2466: S1 Handover towards Hybrid Cells feature has no impact on network management tools. Impact on system performance and capacity

DN09237915 Issue: 01A

© 2017 Nokia

39



The LTE2466: S1 Handover towards Hybrid Cells feature has no impact on system performance or capacity.

3.3.4 LTE2466 reference data Requirements Table 11 System release FDD-LTE 17 Flexi Zone Controller FL17

LTE2466 hardware and software requirements Flexi Multiradio BTS Not supported

Flexi Multiradio 10 BTS

Nokia AirScale BTS

FL17

FL17

OMS Support not required

UE 3GPP R9


NetAct NetAct 17.2


MME Flexi NS4.0

SAE GW Flexi NG3.0

Alarms There are no alarms related to the LTE2466: S1 Handover towards Hybrid Cells feature. BTS faults and reported alarms There are no faults related to the LTE2466: S1 Handover towards Hybrid Cells feature. Measurements and counters Table 12 Counter ID

New counters introduced by LTE2466 Counter name

Measurement

M8008C27 Number of requested SI reports for hybrid cell

LTE RRC

M8008C28 Number of successful SI reports for hybrid cell

LTE RRC

M8008C29 Number of incomplete SI reports for hybrid cell

LTE RRC

M8014C46 Inter eNB S1 HO preparations LTE Inter eNB Handover to hybrid cell M8014C47 Failed Inter eNB S1 HO preparations to hybrid cell due to expiration of guarding timer

LTE Inter eNB Handover

M8014C48 Failed Inter eNB S1 HO preparations to hybrid cell due to admission control in the target eNB


M8014C49 Failed Inter eNB S1 HO preparations to hybrid cell due to other reasons


M8014C50 Attempted Inter eNB S1 HO to LTE Inter eNB Handover hybrid cell

40

© 2017 Nokia

DN09237915 Issue: 01A


Table 12 Counter ID


New counters introduced by LTE2466 (Cont.) Counter name

Measurement

M8014C51 Successful Inter eNB S1 HO to hybrid cell


M8014C52 Failed Inter eNB S1 HO to hybrid cell due to timer expiry


M8014C53 Inter eNB S1 HO preparations LTE Inter eNB Handover for VoLTE (QCI1) to hybrid cell M8014C54 Attempted Inter eNB S1 HO for VoLTE (QCI1) to hybrid cell


M8014C55 Successful Inter eNB S1 HO for VoLTE (QCI1) to hybrid cell


For counter descriptions, see LTE Radio Access Operating Documentation/Reference/Counters. Key performance indicators Table 13

New key performance indicators introduced by LTE2466

KPI ID

KPI name

LTE_6130a

E-UTRAN SI Report Attempts for hybrid cells

LTE_6131a

E-UTRAN SI Report SR for hybrid cells

LTE_6132a

E-UTRAN Incomplete SI Report Ratio for hybrid cells

LTE_6133a

E-UTRAN S1 HO Preparation Success Ratio, inter eNB to a Hybrid cell

LTE_6134a

E-UTRAN S1 HO Preparations, inter eNB to a Hybrid cell

LTE_6135a

E-UTRAN S1 HO Preparation Failure Ratio per Cause, inter eNB to a Hybrid cell

LTE_6136a


LTE_6137a


LTE_6138a

E-UTRAN S1 HO Success Ratio, inter eNB to a Hybrid cell

LTE_6139a

E-UTRAN S1 HO Attempts, inter eNB to a Hybrid cell

LTE_6140a

E-UTRAN S1 HO Failure Ratio, inter eNB to a Hybrid cell

LTE_6141a

E-UTRAN Total S1 HO Success Ratio, inter eNB to a Hybrid cell

LTE_6142a

E-UTRAN S1 HO Preparation Success Ratio, inter eNB for QCI1 to a Hybrid cell

LTE_6143a

E-UTRAN S1 HO Preparations, inter eNB for QCI1 to a Hybrid cell

LTE_6144a

E-UTRAN S1 HO Success Ratio, inter eNB for QCI1 to a Hybrid cell

LTE_6145a

E-UTRAN S1 HO Attempts, inter eNB for QCI1 to a Hybrid cell

Parameters

DN09237915 Issue: 01A

© 2017 Nokia

41


Table 14



Abbreviated name

Managed object

Parent structure

Activate Hybrid S1 mobility

actHybridS1Mobili MRBTS/LNBTS ty

Hybrid neighbor first PCI

pciFirst

MRBTS/LNBTS/LNHBD -

Hybrid neighbor last PCI

pciLast

MRBTS/LNBTS/LNHBD -

Hybrid cell individual offset

cellIndOff

MRBTS/LNBTS/LNHBD -

eNB ID Size

enbIdSize

MRBTS/LNBTS/LNHBD -

EUTRA carrier frequency freqEutra

MRBTS/LNBTS/LNHBD -

Hybrid identifier

MRBTS/LNBTS/LNHBD -

Table 15

InHbdId

-

Existing parameters related to LTE2466 Full name

Abbreviated name

Managed object

Parent structure

Activate intra LTE S1based handover

actLTES1Ho

MRBTS/LNBTS

Neighbour relation status

nrStatus

MRBTS/LNBTS/LNCEL/ LNREL

-

EUTRA carrier frequency csgFreqEutra

MRBTS/LNBTS/LNCSG -

CSG neighbor first PCI

csgPciFirst

MRBTS/LNBTS/LNCSG -

Number of PCI in CSG neighbor range

csgPciRange

MRBTS/LNBTS/LNCSG -

Home eNB EUTRA carrier frequency

freqEutra

MRBTS/LNBTS/LNHEN B

Home eNB first PCI

pciFirst

MRBTS/LNBTS/LNHEN B

Home eNB last PCI

pciLast

MRBTS/LNBTS/LNHEN B




License control SW Asset Monitoring


3.3.5 Activating and configuring LTE2466 Instructions to activate and configure the LTE2466: S1 Handover Towards Hybrid Cells feature using the BTS Site Manager

42

© 2017 Nokia

DN09237915 Issue: 01A



Before you start •

Procedure notifications –

•

The activation procedure requires: – – – –

•

The parameters described below can be modified online. The activation will not cause a service outage.

The eNB must be in service. NetAct must be in service and have a connection to the eNB via OMS. Alternatively, BTS Site Manager must be set up and connected to the eNB. The LNBTS parameter actLTES1Ho is enabled. The LTE2466 feature is not activated; the LNBTS activation parameter actHybridS1Mobility is set to false.

Feature interdependencies –

The following features must be activated before activating the LTE2466: S1 Handover towards Hybrid Cells feature: •

LTE54: Intra-LTE Handover via S1

Procedure 1


2


3


4


DN09237915 Issue: 01A

© 2017 Nokia

43


5

Set the parameter values. • • •

Set the LNBTS activation parameter actHybridS1Mobility to true. Create at least one instance of the MOC LNHBD. The following LNHBD parameters are configured:

freqEutra is configured to a unique value within the LNHBD instances of the eNB pciFirst pciLast cellIndOff enbIdSize

– – – – –

g

Note: If defined, the following PCI ranges must not overlap for the same frequency: –

PCI range defined by parameters LNHENB-pciFirst and LNHENB-pciLast PCI range defined by parameters LNCSG-csgPciFirst and

–

LNCSG-csgPciRange PCI range defined by parameters LNHBD-pciFirst and LNHBD-pciLast

–

g

Note: –

– –

•

6


The hybrid cells' PCI range, defined by parameters LNHBD-pciFirst and LNHBD-pciLast, is configured as a forbidden range in order to exclude the PCIs from PCI planning of the open cells. The non-hybrid cells' PCI range is configured as a forbidden range in cSON in order to exclude the PCIs from PCI planning of the hybrid cells. Alternatively, the PCI assignment of the hybrid cells may be done manually. For more information, refer to PCI planning of the CSG cells introduced by the LTE2351 feature.

For inter-frequency S1 handover to hybrid cells, set the LNBTS parameter actIfHo to enabled.


44


© 2017 Nokia

DN09237915 Issue: 01A




Result Expected outcome •

The LTE2466 feature is activated and S1-based intra- and inter-frequency handover towards hybrid cells is supported.

Unexpected outcome If the conditions described above are not fulfilled, the validation of the configuration file will fail. NetAct performs the validation and informs the operator of the failure. The BTS Site Manager shows error messages according to the configuration.

3.3.6 Deactivating LTE2466 Instructions to deactivate the LTE2466: S1 Handover Towards Hybrid Cells feature using the BTS Site Manager Before you start •


•

The deactivation procedure requires: – – –

DN09237915 Issue: 01A

The parameters described below can be modified online. The activation will not cause a service outage.

The eNB must be in service. NetAct must be in service and have a connection to the eNB via OMS. Alternatively, the BTS Site Manager must be set up and connected to the eNB. The LTE2466 feature must be activated; the LNBTS activation parameter actHybridS1Mobility is set to true.

© 2017 Nokia

45



Procedure 1


2


3


4


5

Set the actHybridS1Mobility value to false.

6

Send the commissioning plan file to the BTS. Sub-steps a) Go to the Send Parameters page. All configured LNHBD objects will be ignored by the eNB if the actHybridS1Mobility parameter is set to false. b) Select an appropriate Send option. • •



Result Expected outcome

46

© 2017 Nokia

DN09237915 Issue: 01A



The LTE2466 feature is deactivated and S1-based intra- and inter-frequency handover towards hybrid cells is not supported.

3.4 LTE2572: RSRQ-based B2 The LTE2572: RSRQ-based B2 feature introduces a new reference-signal-receivedquality-related (RSRQ) trigger to run the B2 inter-RAT measurements.

3.4.1 LTE2572 benefits The LTE2572: RSRQ-based B2 feature provides the following benefits: • •

It is possible to initiate an inter-RAT handover during periods of the high interference. The quality of service is sustained when the reference signal received quality (RSRQ) for the serving cell becomes worse than for the neighbor cell.

3.4.2 LTE2572 functional description The LTE2572 feature introduces a new RSRQ trigger that allows for a handover to occur between an LTE network and a network of a different Radio Access Technology (interRAT handover) while sustaining quality of service. The inter-RAT handover occurs when the following conditions are met: the reference signal received quality (RSRQ) for the serving LTE cell becomes worse than the defined absolute threshold, and the quantity of the reference signal of the other RATs target neighboring cell becomes better than the defined absolute threshold. Handover in mobile networks In order to secure service continuity and quality as a UE moves, UEs not only have to be connected to a serving cell but should also have to monitor neighbor cells. The signal strength or quality of neighboring cells is measured periodically, and a handover occurs when specific conditions are fulfilled. During the handover procedure, running services are maintained; a call is not interrupted, and for an intra-LTE handover no data is lost. Handovers in LTE are network controlled and UE assisted. The goal of the handover procedure is to allocate the same resources for the UE in the target cell after the handover as those used prior to the handover. From the UE's point of view, a handover is always “hard,” meaning that a connection exists to only one cell at a time. Handovers result from such factors as: •

•

Quality: Handovers due to quality are typically initiated as a result of a UE measurement report indicating that the UE can communicate with a neighbor cell with a better channel quality than that of the current serving cell. Coverage: Handovers due to coverage are also initiated as a result of a UE measurement report indicating that the serving cell becomes worse than an absolute threshold.

Measurement and measurement reports

DN09237915 Issue: 01A

© 2017 Nokia

47



The UE assists the eNB regarding a handover by sending measurement reports. When verifying radio conditions due to UE mobility (for example when the UE moves from one LTE cell to another or because of limited LTE coverage), measurement reports may initiate a handover. The type of measurements to be made by the UE, and the details of reporting them to the eNB, can be configured (measurement configuration and report configuration), and the eNB informs the UE about the configurations via the RRC: CONNECTION RECONFIGURATION message. The LTE reference signal received power (RSRP) measurement ensures a cell-specific signal strength metric. On the other hand, the LTE reference signal received quality (RSRQ) measurement provides a cell-specific signal quality metric. LTE handover events Before a handover is performed, a UE sends measurement reports to the network, and it is the network which decides whether a handover takes place or not. 3GPP defines a few types of such events within measurement reports. In order to limit the amount of signaling, the UE only sends measurement reports (RRC: MEASUREMENT REPORT messages) to the eNB when certain conditions (events) are met by the UEs' measurements. The following events are defined in the LTE standard: • • • • • • • •

Event A1: The serving cell becomes better than an absolute threshold. Event A2: The serving cell becomes worse than an absolute threshold. Event A3: An LTE neighbor cell becomes better than an offset relative to the serving cell. Event A4: An LTE neighbor cell becomes better than an absolute threshold. Event A5: The serving cell becomes worse than an absolute threshold, and an LTE neighbor cell becomes better than another absolute threshold. Event A6: Neighbour becomes offset better than secondary cell (SCell) Event B1: A non-LTE neighbor cell becomes better than an absolute threshold. Event B2: The serving cell becomes worse than an absolute threshold, and a nonLTE neighbor cell becomes better than another absolute threshold.

The events from A1 to A6 are related to intra-LTE handovers; B1 and B2 events are related to inter-RAT handovers. A1 events controlled by LNCEL:threshold1 are useful for restricting UE measurements to the serving cell. A3 is connected with a better cell handover and A5 with a coverage handover. The events correspond with the type of measurements the UE performs. The measurement reports contain a list of target cells for a handover. The target cells are listed in order of decreasing value of the reporting quantity, that is, the best cell is reported first. As a consequence of the definition of the events, the target cell list cannot be empty.

48

© 2017 Nokia

DN09237915 Issue: 01A


Figure 1


LTE B2 event Aservingcellbecomesworsethanthreshold1(condition1), andaninter-RATneighborcellbecomesbetterthanthreshold2(condition2)

condition2fulfilled condition1fulfilled

RSRQquantitytrigger [dB]

B2-Threshold2 offset

hysteresis

serving cell B2-Threshold1 hysteresis

neighbor cell time [ms]

signalofaneighborcell

B2start

signalofaservingcell

B2end

LEGEND

3.4.2.1

LTE2572 overview The LTE2572: RSRQ-based B2 feature introduces an additional trigger, which is represented by the quantity of reference signal received quality (RSRQ). The trigger activates the quality-related B2 event, which takes place when the quality of serving cell becomes worse than B2-threshold1 (that is, during the RSRQ-based A2 event), and the quality of inter-RAT neighbor cell becomes better than B2-threshold2. The new event is introduced in addition to the already existing B2 RSRP event. The measurement quantities are: WCDMA: RSCP or ECN0 GSM: RSSI HRPD and 1XRTT: pilotStrength

• • •

g g

Note: Without LTE2572: RSRQ-based B2, the B2 event was intended only for the RSRP. With LTE2572: RSRQ-based B2, it is possible to have also a B2 event for the RSRQ which allows to monitor the quality of service. Note: The LTE2572: RSRQ-based B2 feature does not increase the number of simultaneously active measurements at UEs, and either the B2 RSRP or B2 RSRQ measurement is active at a given time. However, the same B2 target thresholds are applied regardless of the source quantity. If the feature is disabled, the legacy RSRP B2 behavior applies. If the B2 RSRQ parameters are not configured for a target carrier, the legacy RSRP B2 behavior applies to the target carrier.

DN09237915 Issue: 01A

© 2017 Nokia

49


3.4.2.2


B2 RSRQ conditions The conditions for beginning and end of inter-RAT measurements are listed in Table 17: Conditions for the inter-RAT measurements period. During that period, a decision about whether to initiate an inter-RAT handover or not is made; consequently, after a successful target cell selection, a handover preparation phase is initiated. Table 17

g

Conditions for the inter-RAT measurements period

Beginning of inter-RAT measurements*

End of inter-RAT measurements**

The quality of serving cell becomes worse than threshold1 - hysteresis.

The quality of serving cell becomes better than threshold1 + hysteresis.

AND

OR

The quality of inter-RAT neighbor cell becomes better than threshold2 + hysteresis.

The quality or power of inter-RAT neighbor cell becomes worse than threshold2 hysteresis.

Note: * Both conditions must be met before the inter-RAT measurements begin. ** Either of the conditions must be met before the inter-RAT measurements are ended.

3.4.3 LTE2572: system impact Interdependencies between features The following feature must be activated before activating the LTE2572: RSRQ-based B2 feature: •

LTE1198: RSRQ-triggered Mobility The RSRQ-based A2 event takes a major role in the RSRQ-based B2 event; therefore, the LTE1198: RSRQ-triggered Mobility feature needs to be enabled.

Impact on interfaces The LTE2572: RSRQ-based B2 feature has no impact on interfaces. Impact on network management tools The LTE2572: RSRQ-based B2 feature has no impact on network management tools. Impact on system performance and capacity The LTE2572: RSRQ-based B2 feature has no impact on system performance or capacity.

3.4.4 LTE2572 reference data Requirements

50

© 2017 Nokia

DN09237915 Issue: 01A


Table 18


LTE2572 hardware and software requirements

System release FDD-LTE 17

Flexi Multiradio BTS Not supported



Nokia AirScale BTS

FL17

FL17

OMS

UE

LTE OMS 16A 3GPP R8


NetAct

FL17

MME

NetAct 17.2

Flexi Zone Access Point

SAE GW

Support not required


Alarms There are no alarms related to the LTE2572: RSRQ-based B2 feature. BTS faults and reported alarms There are no faults related to the LTE2572: RSRQ-based B2 feature. Commands There are no commands related to the LTE2572: RSRQ-based B2 feature. Measurements and counters There are no measurements or counters related to the LTE2572: RSRQ-based B2 feature. Key performance indicators There are no key performance indicators related to the LTE2572: RSRQ-based B2 feature. Parameters Table 19


Abbreviated name

Managed object

Parent structure

Activate RSRQ-based B2

actRsrqInterRatMo LNBTS bility

-

RSRQ B2 GERAN threshold1

b2Threshold1RsrqG LNHOG ERAN

rsrqB2GERANMobili tyParams

RSRQ B2 GERAN time to trigger

b2TimeToTriggerRs LNHOG rqGERANMeas


RSRQ B2 GERAN hysteresis

hysB2ThresholdRsr LNHOG qGERAN


RSRQ B2 GERAN report interval

reportIntervalRsr LNHOG qGERAN


RSRQ B2 HRPD threshold1 b2Threshold1RsrqH LNHOH rpd

rsrqB2HrpdMobilit yParams

b2TimeToTriggerRs LNHOH rqHrpdMeas


RSRQ B2 HRPD time to trigger

DN09237915 Issue: 01A

© 2017 Nokia

51


Table 19


New parameters introduced by LTE2572 (Cont.) Full name

Abbreviated name

Managed object

Parent structure

RSRQ B2 HRPD hysteresis hysB2ThresholdRsr LNHOH qHrpd


reportIntervalRsr LNHOH qHrpd


RSRQ B2 UTRA threshold1 b2Threshold1RsrqU LNHOW tra

rsrqB2UtraMobilit yParams

b2TimeToTriggerRs LNHOW rqUtraMeas


RSRQ B2 UTRA hysteresis hysB2ThresholdRsr LNHOW qUtra


RSRQ B2 UTRA report interval

reportIntervalRsr LNHOW qUtra


RSRQ B2 1XRTT threshold1

b2Threshold1RsrqR LNHOX tt

rsrqB2RttMobility Params

RSRQ B2 1XRTT time to trigger

b2TimeToTriggerRs LNHOX rqRttMeas


RSRQ B2 1XRTT hysteresis

hysB2ThresholdRsr LNHOX qRtt


RSRQ B2 1XRTT report interval

reportIntervalRsr LNHOX qRtt


RSRQ B2 HRPD report interval

RSRQ B2 UTRA time to trigger



Product structure class

License control

Application software (ASW)

SW Asset Monitoring


3.4.5 Activating LTE2572 Instructions to activate the LTE2572: RSRQ-based B2 feature using the BTS Site Manager Before you start •

The activation procedure requires the following: – – – – –

52

The eNB must be operational, and the RNW database must be running. The LTE2572: RSRQ-based B2 feature must be deactivated; its LNBTS activation parameter actRsrqInterRatMobility must be set to false. The LTE1198 feature must be configured. Any relevant inter-RAT mobility functionalities are activated. Vendor-specific parameters are configured in the vendor file.

© 2017 Nokia

DN09237915 Issue: 01A


–


Mandatory and optional operator-specific parameters are configured.

Procedure 1


2


3


4


5

g

Set the actRsrqInterRatMobility value to true. Note: As an alternative, activation can also be done by reconfiguring the mandatory and optional operator-specific parameters.

6


DN09237915 Issue: 01A


© 2017 Nokia

53




Result Expected outcome The Flexi Multiradio BTS supports inter-RAT mobility based on the B2 RSRQ measurement reporting.

3.4.6 Deactivating LTE2572 Instructions to deactivate the LTE2572: RSRQ-based B2 feature using the BTS Site Manager Before you start •

The deactivation procedure requires: – –

The eNB must be operational, and the RNW database must be running. The LTE2572 feature must be activated; the LNBTS activation parameter actRsrqInterRatMobility must be set to true.

Procedure 1


2

Start commissioning. 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.

54

© 2017 Nokia

DN09237915 Issue: 01A



b) Use the Template, Manual, or Reconfiguration option, depending on the actual state of the BTS.

3


4


5

Set the actRsrqInterRatMobility value to false.

6




Result Expected outcome The LTE2572 feature is deactivated. The Flexi Multiradio BTS is no longer able to use inter-RAT mobility.

3.5 LTE2664: Load-based PUCCH Region The LTE2664: Load-based PUCCH Region feature introduces live allocation of physical uplink control channel (PUCCH) resources corresponding to the number of connected UEs.

3.5.1 LTE2664 benefits The LTE2664: Load-based PUCCH Region feature provides the following benefits: •

DN09237915 Issue: 01A

Automatic adaptation of PUCCH resources according to current cell load

© 2017 Nokia

55


• •


Relocation of unused PUCCH resources to PUSCH during a low-traffic period, resulting in a higher uplink throughput Operator is required to configure 7 parameters only in contrary to 17 in standard configuration

3.5.2 LTE2664 functional description Functional overview The LTE2664: Load-based PUCCH Region feature adjusts the range of physical resource blocks (PRB) allocated to the physical uplink control channel (PUCCH). The adjustment is made proportionally to the number of UEs connecting to a cell. Cooperation with the LTE1130: Dynamic PUCCH Allocation feature enables the operator to expand or compress the PUCCH region according to the actual cell’s load. Thanks to the live adjustment of scheduling request (SR) and channel state information (CSI) periodicities, defined with the LTE1130: Dynamic PUCCH Allocation feature, the adaptation of PRBs assigned to PUCCH is swift and efficient; that is, adequate to the number of UEs connected to the cell.

g

Note: The PUCCH region may be released once there are PUCCH resources in it that are no longer occupied. To avoid undesirable bandwidth fragmentation, the system stops assigning new calls to the PUCCH area at the risk of being soon converted to PUSCH. Figure 2

PUCCH resource allocation in LTE2664

Contribution of the LTE1130: Dynamic PUCCH Allocation feature

56

© 2017 Nokia

DN09237915 Issue: 01A



The physical uplink control channel (PUCCH) is used to transmit the uplink control information (UCI), which includes: • • •

Scheduling requests (SR) HARQ ACK/NACK in response to DL transmissions in the physical downlink shared channel (PDSCH) Channel state information (CSI), which includes: – –

Channel quality indicators (CQI) MIMO-related feedback such as the rank indicators (RI) or the precoding matrix indicators (PMI)

The LTE1130: Dynamic PUCCH Allocation feature simplifies the process of PUCCH configuration by introducing: • •

Dynamic switching between channel state indicator (CSI) periodicities: 40 ms and 80 ms Dynamic switching between UL scheduling request (SR) periodicities: 10 ms, 20 ms, and 40 ms

Switching between SR periodicities depends on cell load, which is related to number of RRC Connected UEs in the cell. Switching between CSI periodicities depends on a cell load and configuration of MIMO, carrier aggregation and enhanced inter-cell interference coordination (eICIC). The adaptation of the CSI or SR periodicity is done only for UEs for which reconfiguration needs to be applied. To avoid generating extra signaling, new CSI or SR periodicity is given to every UE experiencing one of the following events: • • •

RRC-idle to RRC-connected state transition UE entering the cell via handover Secondary cell (SCell) configuration or reconfiguration

Enhancements introduced by LTE2664: Load-based PUCCH Region feature In addition to the shift in CSI and SR periodicities managed by the LTE1130: Dynamic PUCCH Allocation feature, the LTE2664: Load-based PUCCH Region feature allows operator to expand or contract PUCCH region according to the minimal configuration of resources allocated to PUCCH (2 PRBs assigned) . The eNB responds in advance to the rising number of UEs connecting to the cell by expanding the PUCCH area. A configurable safety margin prevents the PUCCH resources from running out and helps to avoid the radio resource control (RRC) blocking. When the PUCCH expansion process is triggered, eNB calculates new parameter values for the next PUCCH expansion step. Parameters that define PUCCH area size and PRACH offset (APUCCH_FDD:assignedNCqiRb, APUCCH_FDD:assignedPrachFreqOff and APUCCH_FDD:assignedN1PucchAn) are modified. UEs get the new parameter values through a SIB broadcast (SIB#2 in the image) which contains the new values for nRB-CQI, prach-FreqOffset, and n1PUCCH-AN.

DN09237915 Issue: 01A

© 2017 Nokia

57


Figure 3


PUCCH expansion procedure

APUCCH_FDD/TDD assignedPrachFreqOff AssignedN1PucchAn assignedNCqiRB

SIB#2 nRB-CQI Prach-FreqOffset N1PUCCH-AN

SIB#2

If the PUCCH expansion process is triggered because the systemInfoValueTag is above the value set in LNBTS:sibUpdateRateThreshold, then new parameter values are calculated for maximum possible PUCCH configuration. A SIB update (SIB#2 in the image) containing the new information is broadcasted. Figure 4

PUCCH expansion procedure (systemInfoValueTag > LNBTS: sibUpdateThreshold)

SIB#1

LNBTS

systemInfoValueTag 28

sibUpdateRateThreshold 25

SIB#1 SIB#2

SIB#2 nRB-CQI Prach-FreqOffset n1PUCCH-AN When a cell’s load decreases, spare physical uplink control channel (PUCCH) capacity is acquired. To reconfigure the area assigned to PUCCH, a system information block (SIB) sent by the eNB must be modified. Introducing SIB modifications requires a sufficient amount of time. Due to restrictions, they cannot occur too often and cannot be delayed too much either to avoid the RRC blocking. That is why a PUCCH area downgrade has to be carried out with an appropriate time margin in regard to the previous PUCCH modification. After the established interval has passed, some of the PUCCH-allocated physical resource blocks (PRB) exceeding the threshold are reassigned by the eNB to be used by the physical uplink shared channel (PUSCH). The operator is enabled to define the amount of supported UEs. This includes the maximum number of UEs calculated considering parameters: •

58

maxNumActUe

© 2017 Nokia

DN09237915 Issue: 01A



aPucchMinNumRrcNoDrb aPucchMinNumEmergencySessions aPucchAddAUeRrHo aPucchAddAUeTcHo

• • • •

Setting correctly parameters for minimum number of UEs hosted by the cell allows to reach minimal configuration containing only 2 or 4 PRBs.

aPucchMinNumRrc aPucchMinNumRrcNoDrb aPucchMinNumEmergencySessions aPucchAddAUeRrHo aPucchAddAUeTcHo

• • • • •

Expansion or compression of PUCCH resources is followed by shift of PRBs used by physical random access channel (PRACH). Location of these resources is corresponding to the changes of the area occupied by PUCCH.

g

Note: When LTE944: PUSH Masking feature is active PRACH resources are steadily allocated due to the PUSCH masking. PRACH resources are allocated according to the LTE1130: Dynamic PUCCH allocation feature calculated largest PUCCH BW occupation. Reconfiguration of PUCCH resources Reconfiguration of PUCCH is a complex process that might be divided into three distinctive phases: 1. Preparation phase when the UE in the cell is prepared for the process to trigger. Changes in the system information are introduced and notifications in the eNB software are prepared. 2. Communication phase when notifications are sent to UEs, informing that in the next broadcast control channel (BCCH) modification window new SIBs will be available. 3. Broadcasting phase when the new SIBs are transmitted. Resources reconfiguration event is triggered when UE's reosurces must be relocated. Each UE subbmited to reconfiguration recieves a RRCConnectionReconfiguration message from eNB followed by a feedback RRCConnectionReconfigurationComplete message from the UE. Extending the PUCCH region is a fast process, devoid of risk of dropping the UEs. The default value for the parameter countdownPucchExp defining the extent of time that need to pass between following expansions is set for 10 minutes. In contrast the compression is carried out with much more attention. The default value for the parameter countdownPucchCompr is set to 60 minutes. To avoid unnecessary repositioning,the number of UEs requiring reconfiguration must be below 50. Borderline PUCCH reconfiguration instances There is possibility that after triggering PUCCH reconfiguration, cell's load may substantially change which requires appropriate LTE2664: Load-based PUCCH Region feature response.

DN09237915 Issue: 01A

© 2017 Nokia

59


•

•


When expansion of PUCCH region is triggered and the number of SIB modification per interval is above sibUpdateRateThresholdthreshold, PUCCH area is expanded to the maximal configurable value. When compression of PUCCH region is triggered and the number of SIB modification is above sibUpdateRateThreshold threshold, the compression is aborted and postponed to the next countdown expiration.

Data carried in PUCCH The physical uplink control channel (PUCCH) is used to transmit the uplink control information (UCI), which includes: • • •

Scheduling requests (SR) HARQ ACK/NACK in response to DL transmissions in the physical downlink shared channel (PDSCH) Channel state information (CSI), which includes: – –

Channel quality indicators (CQI) MIMO-related feedback such as the rank indicators (RI) or the precoding matrix indicators (PMI)

3.5.3 LTE2664 system impact Interdependencies between features The following features must be activated before activating the LTE2664: Load-based PUCCH Region feature: •

LTE1130: Dynamic PUCCH Allocation

The following features must be deactivated before activating the LTE2664: Load-based PUCCH Region feature: • • •

LTE116: Cell Bandwidth – 3 MHz LTE117: Cell Bandwidth – 1.4 MHz LTE1203: Load-based Power Saving with Tx Path Switching Off

Impact on interfaces The LTE2664: Load-based PUCCH Region feature has no impact on interfaces. Impact on network management tools The LTE2664: Load-based PUCCH Region feature has no impact on network management tools. Impact on system performance and capacity The LTE2664: Load-based PUCCH Region feature has no measurable impact on system performance or capacity. However, a cell access can be limited if the process of PUCCH region expansion is not fast enough.

3.5.4 LTE2664 reference data Requirements

60

© 2017 Nokia

DN09237915 Issue: 01A


Table 21



System release

Flexi Multiradio BTS

FDD-LTE 17

Not supported

Flexi Zone Controller


Nokia AirScale BTS

FL17

FL17

OMS

FL17

UE

LTE OMS16A

3GPP R8


NetAct NetAct 17.2


MME Support not required

SAE GW Support not required

BTS faults and reported alarms There are no faults related to the LTE2664: Load-based PUCCH Region feature. Measurements and counters Table 22

New counters introduced by LTE2664

Counter ID

Counter name

Measurement

M8011C194

Load-based PUCCH region expansion

LTE Cell Resource

M8011C195

Load-based PUCCH region compression

LTE Cell Resource

Table 23

Existing counters related to LTE2664

Counter ID

Counter name

Measurement LTE Cell Resource

M8011C49

PRB used PUCCH

M8013C67

Number of Signaling LTE UE State Connection Establishment Requests rejected due to lack of PUCCH resources

For counter descriptions, see LTE Radio Access Operating Documentation/Reference/Counters. Key performance indicators There are no key performance indicators related to the LTE2664: Load-based PUCCH Region feature. Parameters Table 24

Existing parameters related to LTE2664

Full name

Activation of automatic PUCCH allocation

DN09237915 Issue: 01A

Abbreviated name

actAutoPucchAlloc

© 2017 Nokia

Managed object MRBTS/LNBTS/LNCEL/LNCEL_FD D

Parent structure

-

61


Table 24

Existing parameters related to LTE2664 (Cont.)

Full name

62


Abbreviated name

Managed object

Parent structure

Maximum number of active UEs

maxNumActUE

MRBTS/LNBTS/LNCEL/LNCEL_FD D

-

Activate load-based PUCCH region

actLbPucchReg

MRBTS/LNBTS/LNCEL/LNCEL_FD D/APUCCH_FDD

-

Load-based PUCCH region profile identifier

lbPucchRPrId

MRBTS/LNBTS/LNCEL/LNCEL_FD D/APUCCH_FDD

-

Countdown timer SIB modification by PUCCH compression

countdownPucchComp MRBTS/LNBTS/LBPUCCHRDPR r

-

Countdown timer SIB modification by PUCCH expansion

countdownPucchExp

MRBTS/LNBTS/LBPUCCHRDPR

-

Lower threshold UEs in RRC connected

rrcConnectedLowerT MRBTS/LNBTS/LBPUCCHRDPR hresh

-

Upper threshold UEs in RRC connected

rrcConnectedUpperT MRBTS/LNBTS/LBPUCCHRDPR hresh

-

Load based PUCCH region default profile identifier

lbPucchRDPrId

MRBTS/LNBTS/LBPUCCHRDPR

-

Countdown timer SIB modification by PUCCH compression

countdownPucchComp MRBTS/LNBTS/LBPUCCHRPR r

-

Countdown timer SIB modification by PUCCH expansion

countdownPucchExp

MRBTS/LNBTS/LBPUCCHRPR

-

Lower threshold UEs in RRC connected

rrcConnectedLowerT MRBTS/LNBTS/LBPUCCHRPR hresh

-

Upper threshold UEs in RRC connected

rrcConnectedUpperT MRBTS/LNBTS/LBPUCCHRPR hresh

-

© 2017 Nokia

DN09237915 Issue: 01A


Table 24

Existing parameters related to LTE2664 (Cont.)

Full name

Load based PUCCH region profile identifier

g


Abbreviated name

Managed object MRBTS/LNBTS/LBPUCCHRPR

lbPucchRPrId

Parent structure

-

Note: The parameters are shared with the LTE1130: Dynamic PUCCH Allocation feature. For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters. Sales information Table 25



License control


Pool license


3.5.5 Activating and configuring LTE2664 Instructions to activate and configure the LTE2664: Load-based PUCCH Region feature using the BTS Site Manager Before you start •


Activation procedure uses the following parameters and activation flags: •

•


The following features must be activated before activating the LTE2664: Loadbased PUCCH Region feature: •

–

• • –

LTE116: Cell Bandwidth – 3 MHz LTE117: Cell Bandwidth – 1.4 MHz LTE1203: Load-based Power Saving with Tx Path Switching Off

LTE1808 and LTE2664 can not be activated together.

The activation procedure requires: –

DN09237915 Issue: 01A

LTE1130: Dynamic PUCCH Allocation This feature is activated by the actAutoPucchAlloc flag.

The following features must be deactivated before activating the LTE2664: Loadbased PUCCH Region feature: •

•

actLbPucchReg

A connection between the eNB and the management system must be established and working.

© 2017 Nokia

63


– – – – – –

g


All LNCEL and other class instance parameters needed for an operating eNB must be configured. Parameter configuration follows the guidelines. In case of reconfiguration, no validation error exists. LTE1130 is activated in at least one LNCEL/LNCEL_FDD instance of the eNB; actAutoPucchAlloc is set to true under the LNCEL/LNCEL_FDD instance. A new object APUCCH_FDD must be created. Set the value of the aPucchSrPeriodUpperLimit (Automatic PUCCH allocation, upper SR periodicity) parameter to 20 ms or 40 ms. The LTE2664 feature must be inactive. The actLbPucchReg parameter under the APUCCH_FDD object is set to false. Note: The actAutoPucchAlloc parameter must be set to the same value on all LNCELs with carrier aggregation.

Procedure 1


2


3


4

Go to the LNCEL object.

g

Note: From release LTE17 onwards, due to a change in the MO architecture, you need to select the LNCEL/LNCEL_FDD object. Object path: MRBTS ► LNBTS ► LNCEL ► LNCEL_FDD 5

g

64

Set the parameter values. Note: From release LTE17 onwards, due to a change in the MO architecture, you need to select the LNBTS/LNBTS_FDD object.

© 2017 Nokia

DN09237915 Issue: 01A


g


Note: From release LTE17 onwards, due to a change in the MO architecture, you need to select the LNCEL_FDD/APUCCH_FDD object. For each LNCEL_FDD instance the feature is activated on, perform the following: • •

Change actAutoPucchAlloc to true. Under the child class APUCCH_FDD of the LNCEL_FDD, configure actLbPucchReg to true.

g

Note: LNCEL instances will short stop service and will be reestablished due to actLbPucchReg modification via cell lock. Configure the parameters accordingly:

g

Note: LBPUCCHRDPR is under the LNBTS object. •

•

Case 1. The same Load-based PUCCH Region configuration for all LNCELs Change all the settings under class LBPUCCHRDPR (load-based PUCCH region default profile identifier) as required. Case 2. Partially specific Load Based PUCCH Region configuration for the LNCEL This case describes the reuse of settings from the default LBPUCCHRDPR profile. For this scenario, do the following: –

–

•

Case 3. Fully-specific Load-based PUCCH Region configuration for the LNCEL In this case, none of the default configurations are used. For this scenario, do the following: – –

6

Create or modify an existing LBPUCCHRPR (load-based PUCCH region profile identifier) instance where only the parameters that are intended to be modified can be configured. Under the APUCCH_FDD instance, configure the lbPucchRPrId parameter with the value of the LBPUCCHRPR instance.

Create or modify an existing LBPUCCHRPR instance where all parameters in the LBPUCCHRPR instance will be configured. Under the APUCCH_FDD instance, configure the lbPucchRPrId parameter with the value of the LBPUCCHRPR instance.


DN09237915 Issue: 01A


© 2017 Nokia

65




Result Expected outcome • • •

•

The LNCEL instance(s) and all parameter settings are stored on the eNB. NetAct and BTS Site Manager are informed of the modified configuration via notifications. The LTE2664 feature is activated and, in case a dedicated profile is used, the configuration of the referenced instance LBPUCCHRPR is considered in the application. If no dedicated profile is assigned, the default profile LBPUCCHRDPR is used. The cell(s) are operating as expected.

3.5.6 Deactivating LTE2664 Instructions to deactivate the LTE2664: Load-based PUCCH Region feature using the BTS Site Manager Before you start •

Preconfiguration The deactivation procedure requires: – – – – –

66

A connection between the eNB and the management system must be established and working. All LNCEL and other class instance parameters needed for an operating eNB must be configured. Parameter configuration follows the guidelines. In case of reconfiguration, no validation error exists. LTE1130 is activated; actAutoPucchAlloc is set to true. LTE2664 is activated in at least one LNCEL_FDD instance of the eNB; actLbPucchReg is set to true.

© 2017 Nokia

DN09237915 Issue: 01A



Procedure 1


2


3


4

Go to the LNCEL object.

g

Note: From release LTE17 onwards, due to a change in the MO architecture, you need to select the LNCEL/LNCEL_FDD object. Object path: MRBTS ► LNBTS ► LNCEL ► LNCEL_FDD 5

Edit the eNB configuration with the following content:

g

Note: From release LTE17 onwards, due to a change in the MO architecture, you need to select the LNBTS/LNBTS_FDD object.

g

Note: From release LTE17 onwards, due to a change in the MO architecture, you need to select the LNCEL_FDD/APUCCH_FDD object. •

To deactivate LTE2664 on an LNCEL_FDD instance while keeping LTE1130 active – – –

•

To deactivate LTE2664 and LTE1130 –

DN09237915 Issue: 01A

Under the child class APUCCH of the LNCEL_FDD instance, change the actLbPucchReg parameter to false. Delete the parameter value of lbPucchRPrId and leave it empty. Optionally, under APUCCH_FDD, delete the LBPUCCHRPR instance the lbPucchRPrId parameter points to.

Under the LNCEL_FDD instance, change the actAutoPucchAlloc parameter to false.

© 2017 Nokia

67


g

Note: The actAutoPucchAlloc parameter must be set to the same value on all LNCELs with carrier aggregation. –

6


Under the child class APUCCH_FDD of the LNCEL_FDD instance, change the actLbPucchReg parameter to false.




Result Expected outcome • • • •

The LNCEL instances and all parameter settings are stored in the eNB. NetAct and BTS Site Manager are informed of the configuration modifications via notifications. The LTE2664 is deactivated. Any specific configuration for the referenced instance LBPUCCHRPR or the default profile LBPUCCHRDPR is not considered by the eNB. The cells are operating as expected.

3.6 LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V The LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature supports additional band combinations for two-component-carrier (2CC) downlink (DL) carrier aggregation (CA).

3.6.1 LTE3047 benefits The LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature provides higher DL peak rates in areas with overlapping cell deployments for the supported two-component-carrier (2CC) band combinations.

68

© 2017 Nokia

DN09237915 Issue: 01A



3.6.2 LTE3047 functional description The LTE3047 feature introduces the following additional carrier aggregation band combinations with the bandwidth combination set 0 (BCS 0), if not mentioned otherwise: • • • • • • • •

band 3 + band 3 (non-contiguous; BCS 2) band 3 + band 5 (BCS 4) band 5 + band 28 band 7 + band 7 (non-contiguous; BCS 1, 2, 3) band 7 + band 8 (BCS 2) band 12 + band 25 band 29 + band 66 band 30 + band 66

3.6.3 LTE3047 system impact Interdependencies between features The LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature is enabled together with the following features: • •

LTE1089: Downlink Carrier Aggregation – 20 MHz LTE1332: Downlink Carrier Aggregation – 40 MHz

The LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature impacts the following features: •

•

•

LTE3048: Additional Carrier Aggregation Band Combinations 3CC – III The LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature provides 2CC fallback band combinations for the LTE3048: Additional Carrier Aggregation Band Combinations 3CC – III feature. LTE1089 Downlink Carrier Aggregation – 20 MHz The LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature adds additional 2CC CA band combinations. LTE1332 Downlink Carrier Aggregation – 40 MHz The LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature adds additional 2CC CA band combinations.

Impact on interfaces The LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature has no impact on interfaces. Impact on network management tools The LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature has no impact on network management tools. Impact on system performance and capacity The LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature has no impact on system performance or capacity.

DN09237915 Issue: 01A

© 2017 Nokia

69





Flexi Zone Controller not supported


Nokia AirScale BTS

FL17

FL17

OMS

UE


Flexi Zone Micro BTS


not supported

not supported

MME

SAE GW

NetAct

3GPP R12 UE NetAct 17.2 capabilities



3GPP R13 UE capabilities

Alarms There are no alarms related to the LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature. BTS faults and reported alarms There are no faults related to the LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature. Commands There are no commands related to the LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature. Measurements and counters There are no measurements or counters related to the LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature. Key performance indicators There are no key performance indicators related to the LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature. Parameters There are no parameters related to the LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature. Sales information Table 27



70


© 2017 Nokia


DN09237915 Issue: 01A



3.7 LTE3048: Additional Carrier Aggregation Band Combinations 3CC – III The LTE3048: Additional Carrier Aggregation Band Combinations 3CC – III feature supports additional downlink (DL) carrier aggregation (CA) band combinations for three component carriers (CCs), thereby providing more options to increase downlink throughput.

3.7.1 LTE3048 benefits The LTE3048: Additional Carrier Aggregation Band Combinations 3CC – III feature supports new band combinations that provide higher DL peak rates in areas with overlapping cell deployments and when carrier aggregation (CA) is enabled; this guarantees higher peak data rates for the users within the network.

3.7.2 LTE3048 functional description When the LTE3048: Additional Carrier Aggregation Band Combinations 3CC – III feature is enabled, the eNB supports the following additional carrier aggregation (CA) band combinations: •

CA band combination with one band: –

•

CA band combination with two bands: – – – – – – – – – – – – – – – – – –

DN09237915 Issue: 01A

Band 66 + Band 66 + Band 66 (two contiguous carriers)

Band 1 + Band 7 + Band 7 (non-contiguous) Band 2 + Band 5 + Band 5 (contiguous) Band 2 + Band 2 + Band 29 (non-contiguous) Band 2 + Band 2 + Band 30 (non-contiguous) Band 2 + Band 2 + Band 66 (contiguous, non-contiguous) Band 2 + Band 66 + Band 66 (contiguous for bandwidth class B and C, otherwise non-contiguous) Band 3 + Band 3 + Band 5 (contiguous) Band 3 + Band 3 + Band 7 (non-contiguous, bandwidth combination set 0, 1) Band 3 + Band 7 + Band 7 (non-contiguous, bandwidth combination set 0, 1) Band 3 + Band 3 + Band 8 (contiguous) Band 3 + Band 3 + Band 32 (contiguous) Band 4 + Band 5 + Band 5 (contiguous) Band 4 + Band 7 + Band 7 (non-contiguous) Band 5 + Band 7 + Band 7 (contiguous, non-contiguous) Band 5 + Band 5 + Band 30 (contiguous, non-contiguous) Band 5 + Band 5 + Band 66 (contiguous, non-contiguous) Band 5 + Band 66 + Band 66 (contiguous for bandwidth class B and C, otherwise non-contiguous) Band 7 + Band 7 + Band 8 (non-contiguous, bandwidth combination set 0, 1)

© 2017 Nokia

71


– – – –

•

Band 12 + Band 66 + Band 66 (contiguous for bandwidth class C, otherwise noncontiguous) Band 13 + Band 66 + Band 66 (contiguous for bandwidth class B and C, otherwise non-contiguous) Band 29 + Band 66 + Band 66 (contiguous, non-contiguous) (available from LTE17 SP release) Band 30 + Band 66 + Band 66 (contiguous, non-contiguous) (available from LTE17 SP release)

CA band combination with three bands: – – – – – – – – – – – – –

g


Band 1 + Band 5 + Band 28 Band 1 + Band 7 + Band 20 (bandwidth combination set 1) Band 1 + Band 18 + Band 28 (bandwidth combination set 1) Band 2 + Band 5 + Band 66 Band 2 + Band 12 + Band 66 (bandwidth combination set 0, 1) Band 2 + Band 13 + Band 66 Band 2 + Band 29 + Band 66 Band 2 + Band 30 + Band 66 Band 3 + Band 5 + Band 7 Band 3 + Band 5 + Band 28 Band 5 + Band 30 + Band 66 Band 12 + Band 30 + Band 66 Band 29 + Band 30 + Band 66

Note: As described in 3GPP TS 36.101, the bandwidth combination set is 0 if not indicated otherwise.

3.7.3 LTE3048 system impact Interdependencies between features The LTE3048: Additional Carrier Aggregation Band Combinations 3CC – III feature is enabled together with the following features: • •

LTE1803: Downlink Carrier Aggregation 3CC – 40 MHz LTE1804: Downlink Carrier Aggregation 3CC – 60 MHz

Impact on interfaces The LTE3048: Additional Carrier Aggregation Band Combinations 3CC – III feature has no impact on interfaces. Impact on network management tools The LTE3048: Additional Carrier Aggregation Band Combinations 3CC – III feature has no impact on network management tools. Impact on system performance and capacity The LTE3048: Additional Carrier Aggregation Band Combinations 3CC – III feature has no impact on system performance or capacity.

72

© 2017 Nokia

DN09237915 Issue: 01A







AirScale BTS

FL17

FL17

OMS

UE

Not supported Support not required



Not supported

Not supported

MME

SAE GW

NetAct




Alarms There are no alarms related to the LTE3048: Additional Carrier Aggregation Band Combinations 3CC - III feature. BTS faults and reported alarms There are no faults related to the LTE3048: Additional Carrier Aggregation Band Combinations 3CC - III feature. Commands There are no commands related to the LTE3048: Additional Carrier Aggregation Band Combinations 3CC - III feature. Measurements and counters There are no measurements or counters related to the LTE3048: Additional Carrier Aggregation Band Combinations 3CC - III feature. Key performance indicators There are no key performance indicators related to the LTE3048: Additional Carrier Aggregation Band Combinations 3CC - III feature. Parameters There are no parameters related to the LTE3048: Additional Carrier Aggregation Band Combinations 3CC - III feature. Sales information Table 29



DN09237915 Issue: 01A


© 2017 Nokia


73



3.8 LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II The LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II feature supports additional band combinations for downlink (DL) FDD-TDD carrier aggregation (CA), thereby providing more options to increase downlink throughput.

3.8.1 LTE3049 benefits The LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II feature provides additional options for CA and, consequently, higher DL peak rates in areas with overlapping cell deployments for the supported FDD-TDD band combinations.

3.8.2 LTE3049 functional description With the LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II feature enabled, the eNB supports the following additional FDD-TDD carrier aggregation band combinations: •

FDD-TDD 2CC (FDD as PCell, one FDD and one TDD cell): – –

•

FDD-TDD 3CC (FDD as PCell, one FDD and two TDD cells): – – – – – – –

•

Band 1 (FDD 5/10/15/20 Mhz) + Band 41 (TDD 20 Mhz) + Band 41 (TDD 10/20 Mhz) Band 1 (FDD 5/10/15/20 Mhz) + Band 41 (TDD 10/20 Mhz) + Band 42 (TDD 20 Mhz) Band 1 (FDD 5/10/15/20 Mhz) + Band 42 (TDD 20 Mhz) + Band 42 (TDD 20 Mhz) Band 3 (FDD 5/10/15/20 Mhz) + Band 41 (TDD 20 Mhz) + Band 41 (TDD 10/20 Mhz) Band 3 (FDD 5/10/15/20 Mhz) + Band 41 (TDD 10/20 Mhz) + Band 42 (TDD 20 Mhz) Band 8 (FDD 5/10 Mhz) + Band 41 (TDD 20 Mhz) + Band 41 (TDD 10/20 Mhz) Band 28 (FDD 5/10 Mhz) + Band 41 (TDD 20 Mhz) + Band 41 (TDD 10/20 Mhz)

FDD-TDD 3CC (FDD as Pcell, two FDD and one TDD cell): –

g

Band 1 (FDD 5/10/15/20 Mhz) + Band 41 (TDD 10/20 Mhz) Band 1 (FDD 5/10/15/20 Mhz) + Band 42 (TDD 20 Mhz)

Band 1 (FDD 5/10/15/20 Mhz) + Band 3 (FDD 5/10/15/20 Mhz) + Band 41 (TDD 10/20 Mhz)

Note: The bandwidth combination set is 0 as described in 3GPP TS 36.101. In FDD-TDD CA, the FDD cell acts as a PCell or an SCell, and TDD cells act only as SCells. The transmission mode 3 (TM 3), TM 4, or TM 9 can be configured for site configurations as required.

74

© 2017 Nokia

DN09237915 Issue: 01A



TDD frame configuration 1 or 2 is supported in TDD cells and is used with TDD component carriers (CCs).

3.8.3 LTE3049 system impact Interdependencies between features The LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II feature is enabled together with the following features: LTE2180: FDD-TDD Downlink Carrier Aggregation 2CC LTE2316: FDD-TDD Downlink Carrier Aggregation 3CC LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD

• • •

Impact on interfaces The LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II feature has no impact on interfaces. Impact on network management tools The LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II feature has no impact on network management tools. Impact on system performance and capacity The LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II feature has no impact on system performance or capacity.

3.8.4 LTE3049 reference data Requirements Table 30 System release FDD-LTE 17 Flexi Zone Controller

LTE3049 hardware and software requirements for FDD Flexi Multiradio BTS Not supported

System release TD-LTE 17

DN09237915 Issue: 01A

AirScale BTS



FL17

Not supported

Not supported

Not supported

NetAct

MME

SAE GW

OMS

UE


Table 31


3GPP R12-14 UE capabilities




LTE3049 hardware and software requirements for TDD Flexi Multiradio 10 BTS

Flexi Multiradio 10 Indoor BTS

AirScale BTS



TL17

TL17

Not supported

Not supported

Not supported

© 2017 Nokia

75


Table 31


LTE3049 hardware and software requirements for TDD (Cont.)


OMS

UE


3GPP R12-14 UE capabilities

NetAct Support not required



Alarms There are no alarms related to the LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II feature. BTS faults and reported alarms There are no faults related to the LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II feature. Commands There are no commands related to the LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II feature. Measurements and counters There are no measurements or counters related to the LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II feature. Key performance indicators There are no key performance indicators related to the LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II feature. Parameters There are no parameters related to the LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II feature. Sales information Table 32





3.9 LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) The LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) feature introduces the LTE BTS support of GPS and UTC time information broadcast in system information block type 16 (SIB16).

76

© 2017 Nokia

DN09237915 Issue: 01A



3.9.1 LTE3056 benefits The LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) feature allows to retrieve system and local time from the common broadcasting channel. Broadcasting reference time from the LTE network is useful in the following use cases: • • •

GPS time for GNSS Coordinated Universal Time (UTC) for MBMS Local time provisioning

3GPP proposed to introduce a new SIB to provide the GPS time and UTC time.

3.9.2 LTE3056 functional description Flexi Multiradio BTS supports the broadcast of SIB16. The SIB16 information element (IE) contains information related to the GPS time and Coordinated Universal Time (UTC). The UE may use the parameters provided in this system information block to obtain the UTC, the GPS, and the local time. Figure 5

Content of the SIB16, as described in 3GPP TS 36.331

The SIB16 broadcast is not supported for 1.4-Mhz and 3-Mhz cells. The LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) feature introduces an LNBTS feature flag to enable or disable the SIB16 broadcast function on a BTS level. If SIB16 is enabled on the BTS, its configuration in a specific cell schedule list can enable or disable the SIB16 on the cell level.

3.9.3 LTE3056 system impact Interdependencies between features The LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) feature affects the following features: •

• • • •

DN09237915 Issue: 01A

LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) This feature introduces the ltmOff and dayLt O&M parameters. These two parameters have the same meaning as localTimeOffset and dayLightSavingTime parameters in SIB16. LTE2149: Supplemental Downlink Carrier SIB16 is not broadcasted in a supplemental downlink carrier (SDLC) cell. LTE2353: SIB Multiplexing This feature removes the static combination and supports dynamic SIB multiplexing. LTE117: Cell Bandwidth 1.4 MHz LTE116: Cell Bandwidth 3 MHz

© 2017 Nokia

77


•

•

• •


SIB16 is not broadcasted on a 1.4-MHz and 3-MHz LTE bandwidth cell even if LTE3056 is activated on a BTS level. LTE891: Timing Over Packet With Phase Synch When both LTE3056 and LTE891 are activated, UTC timing information for LTE3056 can be acquired through LTE891 instead of GPS. LTE80: GPS Synchronisation This feature can provide phase synchronization; UTC timing information for LTE3056 can be acquired. LTE1710: Sync Hub Direct Forward LTE3071: NB-IoT Inband The transmission of SIB16 message is not supported in NB-IoT.

Impact on interfaces The LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) feature has no impact on interfaces. Impact on network management tools The LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) feature has no impact on network management tools. Impact on system performance and capacity The LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) feature has no impact on system performance or capacity.

3.9.4 LTE3056 reference data Requirements Table 33 System release FDD-LTE 17 Flexi Zone Controller FL17A

LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) hardware and software requirements Flexi Multiradio BTS Not supported


AirScale FDD

FL17

FL17


UE

NetAct

3GPP R12 UE NetAct 17.2 capabilities, 3GPP R13 UE capabilities

Flexi Zone Micro BTS FL17A MME Support not required

Flexi Zone Access Point FL17A SAE GW Support not required

Alarms There are no alarms related to the LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) feature. BTS faults and reported alarms There are no faults related to the LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) feature.

78

© 2017 Nokia

DN09237915 Issue: 01A



Commands There are no commands related to the LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) feature. Measurements and counters There are no measurements or counters related to the LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) feature. Key performance indicators There are no key performance indicators related to the LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) feature. Parameters Table 34

New parameters introduced by LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) Full name

Abbreviated name

Activate GPS and UTC Time Broadcast

Table 35

actUTCBroadcast

Managed object LNBTS

Parent structure

-

Parameters modified by LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) Full name

Abbreviated name

Managed object

Parent structure

System Information Scheduling List, extended for SIB16

sibSchedulingList SIB

-

Indicates which SIB is contained in the SIMessage, extended for SIB16

siMessageSibType SIB (sibSchedulingLis t)

-

Include day light savings time indicator

dayLtIncluded

XPARAM

-

Local time offset included

ltmOffIncluded

XPARAM

-

Table 36

Existing parameters related to LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) Full name

Abbreviated name

Managed object

Parent structure

Network synchronization btsSyncMode mode

BTSSCL

Downlink channel bandwidth

LNCEL_F DD

DN09237915 Issue: 01A

dlChBw

© 2017 Nokia

-

79


Table 37


Parameters migrated from MOC XPARAM to MOC SIB for LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) Full name

Abbreviated name

Managed object

Parent structure

Day light savings time indicator

dayLt

SIB

-

Local time offset

ltmOff

SIB

-

For parameter descriptions, see Flexi Multiradio BTS LTE Commissioning, RNW and Transmission Parameters. Sales information Table 38

LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) sales information


License control


Pool license


3.9.5 Activating and configuring LTE3056 Before you start •

Procedure notifications – –

•

Feature interdependencies The LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) feature affects the following features: – – – – – – – – – –

•

LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB) LTE2149: Supplemental Downlink Carrier LTE2353: SIB Multiplexing LTE117: Cell Bandwidth 1.4 MHz LTE116: Cell Bandwidth 3 MHz LTE891: Timing Over Packet With Phase Synch LTE80: GPS Synchronisation LTE1710: Sync Hub Direct Forward LTE3128: LTE-M LTE3071: NB-IoT Inband

Preconfiguration – –

80

The eNB is configured for phase synchronized mode; Network synchronization mode (btsSyncMode) parameter is set to PhaseSync. The LTE3056: GPS and UTC time information broadcast support (SIB16) feature must be deactivated; Activate GPS and UTC Time Broadcast (actUTCBroadcast) parameter is set to false.

The eNB is operational, and the radio network database is up and running. NetAct is operational, and a DCN connection to the eNB is available via OMS.

© 2017 Nokia

DN09237915 Issue: 01A



Procedure 1


2


3


4


5

Set the Activate GPS and UTC Time Broadcast (actUTCBroadcast) parameter value to true.

6


DN09237915 Issue: 01A

© 2017 Nokia

81



7

Create new System information scheduling list and set the SIB type to SIB16.

8

Configure the Periodicity (siMessagePriodicity) and Repetition (siMessageRepetition) parameters.

9

Optionally, configure the Day light savings time indicator (dayLt) and Local time offset (ltmOff) SIB parameters.

10 Send the commissioning plan file to the BTS. Sub-steps a) Go to the Send Parameters page. b) Select an appropriate Send option. • •



Result The SIB16 is broadcasted in all eNB cells whose bandwidth is equal neither to 1.4 MHz nor 3 MHz.

3.9.6 Deactivating LTE3056 Before you start •

•

Procedure notifications The LTE3056: GPS and UTC time information broadcast support (SIB16) feature must be deactivated; Activate GPS and UTC Time Broadcast (actUTCBroadcast) parameter is set to true. Preconfiguration – –

82

The eNB is operational, and the radio network database is up and running. NetAct is operational, and a DCN connection to the eNB is available via OMS.

© 2017 Nokia

DN09237915 Issue: 01A



Procedure 1


2


3


4


5

Set the Activate GPS and UTC Time Broadcast (actUTCBroadcast) parameter value to false.

6




Result The SIB16 broadcasting is stopped in all eNB cells.

DN09237915 Issue: 01A

© 2017 Nokia

83



3.10 LTE3073: 256 QAM Extensions The LTE3073: 256 QAM Extensions feature enhances LTE2479: 256 QAM in Downlink. The LTE3073: 256 QAM Extensions feature introduces: a performance monitoring mechanism to automatically restrict/allow the usage of 256 QAM modulation and coding schemes. This mechanism works on a UE level. a new activation/deactivation mechanism which enables modifying the activation parameter without locking the cell.

• •

3.10.1 LTE3073 benefits The LTE3073: 256 QAM Extensions feature provides the following benefit: In 256 QAM deployments, transmission efficiency is improved in low signal-tointerference-plus-noise ratio (SINR) regions by using the 256 QAM channel monitoring mechanism. If a UE is capable of 256 QAM, it is configured to use the 256 QAM channel quality indicator (CQI) table only if it is in high SINR conditions. Otherwise, it is configured with the original 64 QAM CQI table.

•

3.10.2 LTE3073 functional description If the UE experiences insufficient channel quality for 256 QAM to be used, it is reconfigured to legacy CQI/MCS/TBS tables. Due to higher granularity, this allows for higher transmission efficiency in low SINR regions. If the UE's perceived channel quality gets sufficient gain for 256 QAM to be used, it is reconfigured back to 256 QAM CQI/MCS/TBS tables, which allows for higher data rates in high SINR regions. This mechanism can be enabled/disabled by setting the actDl256QamChQualEst parameter. Further adjustments of the algorithm can be done using the following operator-configurable parameters: Decision period for channel quality estimation – perDl256QamChQualEst MCS threshold for deactivating 256 QAM for the UE –

• •

dl256QamDeactChQualThr MCS threshold for reactivating 256 QAM for the UE – dl256QamReactChQualThr

•

g

Note: Depending on the radio hardware variant and its configured operating TX power, the RF power offset must be modified to comply with the 3GPP-defined 256 QAM error vector magnitude (EVM) requirements (EVM = 3.5%). For the recommended RF power offsets, see: • •

for FDD: Flexi Multiradio BTS RF Module and Remote Radio Head Description for TD: Flexi Multiradio 10 Base Station TD-LTE RF Module and Remote Radio Head Description.

The RF power offset, dlCellPwrRed, is a dedicated, O&M, operator-configurable parameter.

84

© 2017 Nokia

DN09237915 Issue: 01A



3.10.3 LTE3073 system impact Interdependencies between features The LTE3073: 256 QAM Extensions feature is impacted by the following feature: LTE2479: 256 QAM in Downlink The LTE2479: 256 QAM in Downlink must be enabled.

•

The LTE3073: 256 QAM Extensions feature impacts the following features: LTE1541: Advanced SCell Measurement Handling This feature defines MCS thresholds based on which SCell(s) and PCell can be added, de-activated, or released. The respective O&M configurable parameters are scellBadChQualThr, scellGoodChQualThr and scellNotDetectableThr. These quality thresholds are defined for prerelease12 UEs. Starting with release12 UEs, configured to use 256 QAM in downlink, the eNB does the internal conversion. LTE1496: eICIC – Micro The cell range expansion (CRE) UE tagging uses UE-reported CQI. Every CQI/MCS/TBS parameter is converted for 256-QAM-configured UEs as they use new CQI tables.

•

•

Impact on interfaces The LTE3073: 256 QAM Extensions feature has no impact on interfaces. Impact on network management tools The LTE3073: 256 QAM Extensions feature has no impact on network management tools. Impact on system performance and capacity The LTE3073: 256 QAM Extensions feature has no impact on system performance or capacity.

3.10.4 LTE3073 reference data Requirements Table 39 System release FDD-LTE17 Flexi Zone Controller

LTE3073 hardware and software requirements Flexi Multiradio BTS not supported OMS



Airscale

FL17 UE

UE: 3GPP R12 UE capabilities

NetAct NetAct 17.2



Not supported

Not supported

MME

SAE GW



Alarms

DN09237915 Issue: 01A

© 2017 Nokia

85



There are no alarms related to the LTE3073: 256 QAM Extensions feature. BTS faults and reported alarms There are no faults related to the LTE3073: 256QAM Extensions feature. Commands There are no commands related to the LTE3073: 256 QAM Extensions feature. Measurements and counters Table 40 Counter ID


M8010C CQI Level 00-Level 15 for 132Codeword 1 Reported by M8010C 256QAM-configured UEs 147

Table 41 Counter ID

86

Measurement LTE Power and Quality DL

Existing counters related to LTE3073 Counter name

Measurement

M8011C 196

PDSCH transmission using QPSK of 256QAM-scheduled UE

LTE Cell Resource

M8011C 197

PDSCH transmission using 16QAM of 256QAM-scheduled UE

LTE Cell Resource

M8011C 198


LTE Cell Resource

M8011C 199


LTE Cell Resource

M8011C 200

PDSCH transmission nacks using QPSK of 256QAM-scheduled UE

LTE Cell Resource

M8011C 201

PDSCH transmission nacks using 16QAM LTE Cell Resource of 256QAM-scheduled UE

M8011C 202

PDSCH transmission nacks using 64QAM LTE Cell Resource of 256QAM-scheduled UE

M8011C 203

PDSCH transmission nacks using 256QAM of 256QAM-scheduled UE

LTE Cell Resource

M8011C 204

Failed PDSCH transmission using QPSK of 256QAM-scheduled UE

LTE Cell Resource

M8011C 205

Failed PDSCH transmission using 16QAM of 256QAM-scheduled UE

LTE Cell Resource

M8011C 206


LTE Cell Resource

M8011C 207


LTE Cell Resource

M8012C 175

MAC PDU volume PDSCH using QPSK of 256QAM-scheduled UE

LTE Cell Throughput

© 2017 Nokia

DN09237915 Issue: 01A


Table 41


Existing counters related to LTE3073 (Cont.)

Counter ID

Counter name

Measurement

M8012C 176

MAC PDU volume PDSCH using 16QAM of 256QAM-scheduled UE

LTE Cell Throughput

M8012C 177


LTE Cell Throughput

M8012C 178


LTE Cell Throughput

M8010C 116– M8010C 131

UE Reported CQI Level 00–Level 15 for 256QAM-configured UEs

LTE Power and Quality DL

For counter descriptions, see LTE Performance Measurements. Key performance indicators There are no key performance indicators related to the LTE3073: 256 QAM Extensions feature. Parameters Table 42


Abbreviated name

Managed object

Activate channel quality monitoring for 256QAM usage

actDl256QamChQual MRBTS/L Est NBTS

Decision period for channel quality estimation

perDl256QamChQual MRBTS/L Est NBTS/LN CEL

Parent structure

MCS threshold for dl256QamDeactChQu MRBTS/L deactivating 256QAM for alThr NBTS/LN the UE CEL MCS threshold for dl256QamReactChQu MRBTS/L reactivating 256QAM for alThr NBTS/LN the UE CEL Percentage of MCS samples as bad channel quality for 256QAM

dl256QamBadChQual MRBTS/L Perc NBTS

Percentage of MCS dl256QamGoodChQua MRBTS/L samples as good channel lPerc NBTS quality for 256QAM Transmission mode switch profile identifier

tmSwitchProfileId MRBTS/L NBTS/LN CEL

Transmission mode switch profile identifier

tmSwPrId

DN09237915 Issue: 01A

© 2017 Nokia

MRBTS/L NBTS/TM SWPR

87


Table 42


New parameters introduced by LTE3073 (Cont.) Full name

Abbreviated name

Parent structure

TM switching threshold definition 256QAM

tmSwitchThreshold MRBTS/L Def256Qam NBTS/TM SWPR

CQI threshold for switch from TM3 to TM7 for 256QAM

tm3to7CqiTh256Qam MRBTS/L tmSwitchThreshold NBTS/TM Def256Qam SWPR











CQI threshold from TxDiv to single layer BF for 256QAM

mimoBfslCqiThD256 MRBTS/L Qam NBTS/TM SWPR

CQI threshold from single layer BF to TxDiv for 256QAM

mimoBfslCqiThU256 MRBTS/L Qam NBTS/TM SWPR

Table 43

Parameters modified by LTE3073 Full name

Abbreviated name

Active transmission mode switch

actTmSwitch

Beamforming fallbacking actBfFallback activation

88

Managed object

Managed object

Parent structure

MRBTS/L NBTS/LN CEL/LNC EL_TDD

-

MRBTS/L NBTS/LN CEL/LNC EL_TDD

-

TM switching threshold definition

tmSwitchThreshold MRBTS/L Def NBTS/TM SWPR

CQI threshold for switch from TM3 to TM7

tm3to7CqiTh

MRBTS/L tmSwitchThreshold NBTS/TM Def SWPR


tm3to8CqiTh


© 2017 Nokia

DN09237915 Issue: 01A


Table 43


Parameters modified by LTE3073 (Cont.) Full name

Abbreviated name

Managed object

Parent structure


tm3to9CqiTh



tm7to3CqiTh



tm8to3CqiTh



tm9to3CqiTh


CQI threshold from single layer BF to TxDiv

mimoBfslCqiThU


Transmission mode switch profile identifier

tmSwPrId


CQI threshold from TxDiv to single layer BF

mimoBfslCqiThD


CQI threshold from single layer BF to TxDiv.

mimoBfslCqiThU


Prohibit timer for dynamic TM mode switch

prohibitTimerTmSw MRBTS/L itch NBTS/TM SWPR

Table 44


Abbreviated name

Managed object

Parent structure

Activate modulation scheme DL

actModulationSche MRBTS/L meDl NBTS/LN CEL

Cell power reduce

dlCellPwrRed

MRBTS/L NBTS/LN CEL

-




DN09237915 Issue: 01A


© 2017 Nokia


89



3.10.5 Activating LTE3073 Before you start The LTE3073: 256 QAM Extensions feature is activated together with LTE2479: 256 QAM in Downlink. The modification of activation parameter Activate modulation scheme DL (actModulationSchemeDl) does not require cell locking and has no impact on services.

g

Note: • •

If the LTE1117: LTE MBMS feature is activated, 256 QAM is not supported for MBMS-related signaling. Depending on the power back-off, the cell may still need to be locked based on the definition of the dlCellPwrRed parameter.

3.10.6 Deactivating LTE3073 Before you start The LTE3073: 256 QAM Extensions feature is deactivated together with LTE2479: 256 QAM in Downlink. The modification of activation parameter Activate modulation scheme DL(actModulationSchemeDl) does not require cell locking and has no impact on services.

3.11 LTE3199: Support for Multiple MBSFN and Synchronization Areas Benefits, functionality, system impact, reference data, instructions of the feature The LTE3199: Support for Multiple MBSFN and Synchronization Areas feature enhances the existing Multimedia Broadcast Multicast Service (MBMS) feature LTE1117 with multiple Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN) support. This feature allows the operator to configure multiple MBSFNs in a cell and provides additional capacity per Evolved Node B (eNB) to deploy multiple services across different carriers.

g

Note: For the LTE17 release, this feature will only be usable in laboratory conditions and is not suitable for field deployment. For more information on limitations, see Limitations.

3.11.1 LTE3199 benefits The LTE3199: Support for Multiple MBSFN and Synchronization Areas feature benefits the operator as follows: •

90

The operator can provision up to eight MBSFNs per cell, without any radio resource overlap.

© 2017 Nokia

DN09237915 Issue: 01A



The operator can provision up to six MBMS synchronization areas, on a single carrier, per Multi-cell/Multicast Coordinating Entity (MCE).

•

g

Note: The maximum number of MBSFNSYNCAREA instances depends on the eNB hardware. The operator can use all, or a subset of, frequencies supported by the eNB to provide eMBMS sessions.

•

3.11.2 LTE3199 functional description Overview Under LTE1117, the eNB manages a single frequency layer with one MBSFN area only. The LTE3199: Support for Multiple MBSFN and Synchronization Areas feature enhances that capability with the ability to provision multiple MBSFN SYNC areas. Each MBSFN SYNC area will correspond to a carrier. A cell may have the capability to support multiple MBSFN areas. The feature can be enabled in one eNB on cells working on different carrier frequencies. Up to eight non-overlapping MBSFN areas can be configured per cell. A maximum MBSFN subframe allocation per MBSFN area, and a total per synchronization area, is configurable via O&M setting. Up to six eMBMS synchronization areas can be configured on each eNB. A cell on a given frequency layer can belong to only one MBSFN synchronization area. The LTE3199: Support for Multiple MBSFN and Synchronization Areas feature also enables warning operators if there are resource constraints, and if MBMS sessions cannot be started.

g

Note: In the LTE3199: Support for Multiple MBSFN and Synchronization Areas feature, MBSFN resources can not be overlapped, thus the subframe configuration for those MBSFNs should ensure that the resources do not overlap. The MBSFN overlap capability is introduced with LTE3552. Specifically, the LTE3199: Support for Multiple MBSFN and Synchronization Areas feature brings the following enhancements: • • • • • • •

Eight MBSFN areas per cell Up to six MBSFN SYNC Areas per MCE/eNB allowing multiple carrier support The maximum subframe allocation per MBSFN and per SYNC area can be configured Ability to configure multiple MBSFNs with non-overlapping MBSFN subframes Advertising of the MBSFN neighbor configuration in SIB3 and SIB5 New alarms when sessions cannot be started due to resource constraints Sessions are not started or suspended due to resource constraints

The feature can be enabled or disabled per eNB using O&M settings. It shares a common feature activation flag with LTE1117. Limitations For the LTE17 release, this feature will only be usable in laboratory conditions and is not suitable for field deployment.

DN09237915 Issue: 01A

© 2017 Nokia

91



The following functionalities are not supported in LTE17: • •

Multiple MBSFN areas Multiple MBSFN Sync areas

The following restriction is added in the LTE17 release: •

Dynamic change of the Object Model (NIDD/PDDB) parameters is not supported in the xL17. As a work around, the customer can restart the eMBMS service (FR flag set to OFF/ON) to apply any changes made to the parameters. In such a case, eNB reset is not required and eNB cells stay online.

Other feature limitations: • • • • • • •

g

LTE3199 does not support any carrier bandwidth lower than 10 MHz No support for preemption of MBMS bearers using Address Resolution Protocol (ARP) MBMS service counting not supported MBSFN Area Reserved cell is not supported QCI-65/66 not supported as MBMS bearers MBSFN Area reserved cell which does not perform MBSFN transmission is not supported Multiple eMBMS radio bearers (in different MBSFN Areas) for the same session, as identified by a unique TMGI, are not supported in the single cell; this functionality is added by LTE3552 Note: It is recommended to modify the M1SYNC MOC parameters only if there are no active MBMS sessions.

The following legacy eMBMS LTE1117 functionalities remain in LTE17: •

Supported: – –

•

Single MBSFN area Single MBSFN Sync area

Modified: – – –

Session suspension Absolute time based admission control Admission control related alarms

LTE4: RAN Sharing, LTE125 and LTE2299: IPv6 for U/C-plane can be enabled along with LTE3199 and LTE2807.

3.11.3 LTE3199 system impact LTE3199: Support for Multiple MBSFN and Synchronization Areas impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be activated before activating the LTE3199: Support for Multiple MBSFN and Synchronization Areas feature:

92

© 2017 Nokia

DN09237915 Issue: 01A


•

LTE1117: LTE MBMS The LTE1117 feature introduced support for broadcast of the MBMS service in LTE cells. The feature activation from LTE1117 will be used for LTE3199 as well. Existing MOCs, as well as the MBSFN design, are modified for multiple MBSFN support. New migration rules have been implemented. The existing design impacts the following: –

– –

• •


The MCE shall perform admission control and session allocation before the time of MBMS data, and not on arrival. If the time is in the past, the session shall be started immediately based on the sorted order of time of the MBMS data. The MCE shall keep the session suspended when a session cannot be admitted due to resource constraints. The session resumes when possible. The MCE shall not send Partial RESET if there is an admission control failure since sessions are kept suspended and resumed.

LTE891: Timing over Packet with Phase Synchronization LTE80: GPS Synchronisation The LTE3199 feature depends on SYNC-btsSyncMode to be set to PhaseSync to provide over-the-air frame synchronization across all the cells of the eNB supporting the eMBMS using Global Positioning System (GPS) or Timing over Packet (ToP).

The LTE3199: Support for Multiple MBSFN and Synchronization Areas feature may be enabled in parallel with the following features: • • •

•

•

DN09237915 Issue: 01A

LTE2085: SIB Reception with Parallel Measurement Gaps LTE1103: Load-based Power Savings for Multi-layer Networks LTE1203: Load-based Power Saving with Tx Path Switching Off A cell configured to support MBMS can participate in load-based reduced energy saving. The MBMS is sent over port 4 in any transmission mode. Since all antennas at all cells in that layer are sending the same MBMS signal at the same time, there is less impact on the MBMS compared to other services if some of the Tx paths are switched off. Hence, the operator has to be warned not to activate LTE1203 in areas that have low cell overlap to avoid losing any service, MBMS or otherwise. The operator may choose to ensure that the MBMS cell is not configured for reduced energy saving (activate the power savings feature) or, alternatively, can choose an MBMS cell as the last cell switched to reduced energy saving. No new consistency rules will be added to ensure the cell should be the last one to be considered for energy saving candidate, if any MBSFN is active. LTE3201: eMBMS in RAN-sharing Deployment Support The LTE3199 feature should be able to receive session start/stop messages from any of the provisioned M3 links and start the session in the corresponding service area on all the relevant SYNC/MBSFN areas. Admission control is not performed if the MCE/eNB determines that the new session request is a session reestablishment. Feature interaction also includes informing the MME that relevant application parameters have been updated. The LTE3201 feature is not a prerequisite for the LTE3199 feature. LTE1834: LTE MBMS Service Continuity The LTE3199 feature leverages the capabilities offered by LTE1834 on MBMS carriers to move the UEs to the corresponding carriers to ensure MBMS service continuity. When actMBMS is deactivated, the contents of mbms-SAIIntraFreqr11 IE in SIB15 is updated only with the SAIs provisioned for intra-frequency neighbor cells (if configured). The LTE1834 feature is not a prerequisite for the LTE3199 feature.

© 2017 Nokia

93


•

•

•


LTE2299: Dual Stack IPv4/IPv6 for S1/X2 The LTE2299 feature has to be enabled along with the actMBMS feature flag to be able to use IPv6 capability. LTE2807: IPv6 Support for M1 & M3 Interfaces LTE2807 has to be enabled along with the actMBMS feature flag to benefit from the IPv6 capability LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) The SIB16 will enable UEs to receive accurate timing information for time display, and for other purposes, besides eMBMS service announcements. It is preferred to have cells that broadcast both MBMS and SIB16. This feature is needed for DASH players on the UE. Operators have to ensure SIB16 is broadcasted in cells which broadcast eMBMS. There are no consistency checks added to ensure this behavior.

The LTE3199: Support for Multiple MBSFN and Synchronization Areas feature affects the following features: •

• • •

•

LTE1891: eNB Power Saving – Micro DTX The support of ON/OFF switching per OFDM symbol to reduce power consumption cannot be applied during MBMS subframe transmission. This feature cannot be enabled along with the LTE3199 feature in FDD. LTE48: Support of High-speed Users This feature cannot be enabled along with the actMBMS feature. LTE1496: eICIC-micro LTE1113: eICIC-macro With the LTE3199 feature, LTE1113 must remain deactivated as a precondition for feature activation. LTE1382: Cell Resource Groups With the LTE3199 feature, configuring specific PLMNs is allowed, however from the MBSFN perspective, these are considered fully pooled resources. MBSFN subframes will be available to all the configured PLMNs. It is recommended to keep LTE1382 deactivated when MBMS is enabled since it is highly complex to configure different percentages within the MBSFN resources.

Impact on interfaces The LTE3199: Support for Multiple MBSFN and Synchronization Areas feature impacts interfaces as follows: •

RRC interface – – –

NeighCellConfig updates to SIB5 SIB13 to include multiple MBSFN areas Multiple MCCH support increase in number of PMCH in MBSFNAreaConfiguration

Impact on network management tools The LTE3199: Support for Multiple MBSFN and Synchronization Areas feature has no impact on network management tools. Impact on system performance and capacity

94

© 2017 Nokia

DN09237915 Issue: 01A



The LTE3199: Support for Multiple MBSFN and Synchronization Areas feature impacts system performance and capacity as follows: Throughput eMBMS multicarrier deployment enables the eNB to support multiple MBSFN areas and eMBMS on multiple carriers. Quality eMBMS multicarrier deployment feature does warrant new quality requirements, since the tagging of the existing eMBMS User Data Transmission Success Rate requirement is not applicable to customer eMBMS packet loss KPIs.

•

•

3.11.4 LTE3199 reference data LTE3199: Support for Multiple MBSFN and Synchronization Areas requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements Table 46


System release FDD-LTE 17 Flexi Zone Controller not supported



Nokia AirScale BTS

SBTS17A

FL17

OMS support not required

UE 3GPP R9 UE capabilities


NetAct support not required

Flexi Zone Access Point FL17A

MME support not required

SAE GW support not required

Alarms Table 47

Existing alarms related to LTE3199

Alarm ID

Alarm name

7651

BASE STATION OPERATION DEGRADED

7652

BASE STATION NOTIFICATION

BTS faults and reported alarms Table 48 Fault ID

New BTS faults introduced by LTE3199 Fault name


Alarm name

6856

MBMS session admission failure - not enough resources

7652


6857

MBMS session admission partial admission only

7652


DN09237915 Issue: 01A

© 2017 Nokia

95



Commands There are no commands related to the LTE3199: Support for Multiple MBSFN and Synchronization Areas feature. Measurements and counters There are no measurements or counters related to the LTE3199: Support for Multiple MBSFN and Synchronization Areas feature. Key performance indicators There are no key performance indicators related to the LTE3199: Support for Multiple MBSFN and Synchronization Areas feature. Parameters Table 49


Managed object

M3 Time Reference

m3TimeRef

LNMCE

M1 Time Reference

m1TimeRef

M1SYNC

MBMS Sync Time Offset

mbmsSyncTimeOffse M1SYNC t

Elapsed Count Includes M1 Sync Header

elapsedCountInclu M1SYNC desHeader

MBSFN Starting Subframe

mbsfnStartingSF

MBSFN _FDD

MBSFN Sync Area In Use

syncAreaInUse

MBSFNC EL

MBSFN Area In Use List

mbsfnAreaInUseLis MBSFNC t EL

MBSFN Hidden List

mbsfnHiddenList

MBSFNC EL

MBSFN Sync Area Id

syncAreaId

MBSFNS YNCARE A

MBSFN Overlapping Allowed

mbsfnOverlapAllow MBSFNS ed YNCARE A

MBSFN Sync Area PLMN identity list

syncAreaPlmnIdLis MBSFNS t YNCARE A

MBSFN sync area identifier

mbsfnSyncArea_Fdd MBSFNS Id YNCARE A_FDD

Table 50

Parent structure

Parameters modified by LTE3199 Full name

MBMS SYNC Period

96

Abbreviated name

Abbreviated name

mbmsSyncPeriod

© 2017 Nokia

Managed object

Parent structure

M1SYNC

DN09237915 Issue: 01A


Table 50


Parameters modified by LTE3199 (Cont.) Full name

Abbreviated name

Managed object

Parent structure

MBMS SYNC Reference

mbmsSyncRef

M1SYNC

Integral Seconds

integralSecs

M1SYNC

mbmsSyncRef

Fractional Seconds

fractionalSecs

M1SYNC

mbmsSyncRef

Maximum MBSFN subframe pattern share

maxSubfrPShare

MBSFN _FDD

MBMS Service Area list

mbmsSaiList

MBSFN

Table 51

Existing parameters related to LTE 3199 Full name

Abbreviated name

Managed object

Parent structure

EARFCN Downlink

earfcnDL

LNCEL _FDD


dlChBw

LNCEL _FDD

Default paging cycle

defPagCyc

LNCEL

Modification period coefficient

modPeriodCoeff

SIB

MBMS neighbour cells configuration

mbmsNeighCellConf SIB igIntraF

Neighbor cells configuration

mbmsNeighCellConf IRFIM igInterF

MBSFN Area Identity

mbsfnAreaId

MBSFN

Mobile Country Code

mcc

MBSFNS YNCARE A

syncAreaPlmnIdList

Mobile Network Code

mnc

MBSFNS YNCARE A

syncAreaPlmnIdList

Mobile Network Code length

mncLength

MBSFNS YNCARE A

syncAreaPlmnIdList

MBSFN EARFCN

mbsfnEarfcn

MBSFNS YNCARE A_FDD

MBSFN downlink channel bandwidth

mbsfnDlChBw

MBSFNS YNCARE A_FDD

Allowed MBSFN Sync Area subframe pattern share

syncSubfrPShareAl MBSFNS lowed YNCARE A

Maximum MBSFN Sync Area subframe pattern share

maxSyncSubfrPShar MBSFNS e YNCARE A_FDD

MBMS Service Area

mbmsServiceArea

DN09237915 Issue: 01A

© 2017 Nokia

MBSFN

97


Table 51


Existing parameters related to LTE 3199 (Cont.) Full name

98

Abbreviated name

Managed object

Parent structure

MBMS Service Area Characteristics

servAreaCharacter LNMCE istics

MBMS Service Area Id

servAreaId

LNMCE

servAreaCharacteristics

MBMS Service Area FEC s

ervAreaFec

LNMCE


MBMS Service Area Maximum Bit Rate

servAreaMaxBitRat LNMCE e


MBMS Service Area Maximum Session Bit Rate

servAreaMaxSessio LNMCE nBitRate


MBSFN Sessions Active

mbsfnSessionsActi MBSFN ve

Allowed MBSFN subframe pattern share

subfrPShareAllowe MBSFN d

Multicast channel Scheduling period

mchSchedulingPeri MBSFN od

mchInfo

MBMS SYNC Period

mbmsSyncPeriod

MBSFN

mchInfo

DRX on duration timer

drxOnDuratT

DRX

drxProfile2

DRX Retransmission Timer

drxRetransT

DRX

drxProfile2


drxOnDuratT

DRX

drxProfile3


drxRetransT

DRX

drxProfile3


drxRetransT

DRX

drxProfile4


drxRetransT

DRX

drxProfile5


drxRetransT

LNCEL

drxProfile101


drxRetransT

LNCEL

drxProfile102


drxRetransT

LNCEL

drxProfile103

DRX On Duration Timer

drxOnDuratT

SDRX

drxSmartProfile2


drxRetransT

SDRX

drxSmartProfile2


drxOnDuratT

SDRX

drxSmartProfile3


drxRetransT

SDRX

drxSmartProfile3


drxRetransT

SDRX

drxSmartProfile4


drxRetransT

SDRX

drxSmartProfile5

MBMS single frequency network mbsfnId identifier

MBSFN

MBSFN Sync Area identifier

mbsfnSyncAreaId

MBSFNS YNCARE A_FDD

MBSFN Cell identifier

mbsfnCelId

MBSFNC EL

M1 Sync identifier

m1SyncId

M1SYNC

Activate support for MBMS

actMBMS

LNBTS

© 2017 Nokia

DN09237915 Issue: 01A


Table 51


Existing parameters related to LTE 3199 (Cont.) Full name

Abbreviated name

Managed object

Parent structure

EARFCN for both Downlink and Uplink (TDD)

earfcn

LNCEL

DRX Retransmission Timer (Profile 2)

drxRetransT

DRX

drxProfile2


drxRetransT

DRX

drxProfile3


drxOnDuratT 1

LNCEL

drxProfile10


drxRetransT

LNCEL

drxProfile101


drxRetransT

LNCEL

drxProfile102


drxOnDuratT

LNCEL

drxProfile103


drxRetransT

LNCEL

drxProfile103

DRX Retransmission Timer (DRX Smart Profile 2)

drxRetransT

SDRX

drxSmartProfile2

DRX Retransmission Timer (DRX Smart Profile 3)

drxRetransT

SDRX

drxSmartProfile3

Sales information Table 52





3.12 LTE3201: eMBMS in RAN-sharing Deployment Support The LTE3201: eMBMS in RAN-sharing Deployment Support feature enables different operators to share evolved multimedia broadcast/multicast service (eMBMS) resources from their own core network on the same eNB. This is performed in a manner similar to the Multiple Operator Core Network (MOCN) concept.

3.12.1 LTE3201 benefits The LTE3201: eMBMS in RAN-sharing Deployment Support feature provides the following benefits: •

DN09237915 Issue: 01A

The eMBMS services can be enabled in radio-access-networks (RAN)-sharing deployments. The LTE3201: eMBMS in RAN-sharing Deployment Support feature benefits the operator with an efficient and low-cost solution to deliver common multimedia content, offered by the LTE1117: LTE MBMS feature, and with such advantages provided by the LTE4: RAN sharing feature as

© 2017 Nokia

99


– – – – – •


finding more easily additional cell sites in cities deploying LTE in rural areas reducing LTE upfront investment cost enhancing peak throughput optimizing overall spectrum capacity.

The eMBMS sessions are not dropped in case of a link failure between an eNB and mobility management entity (MME), thereby providing the user with a seamless reception of multimedia content.

3.12.2 LTE3201 functional description Functional overview The LTE3201: eMBMS in RAN-sharing Deployment Support feature allows provisioning more than one active links between the eNB and MMEs (M3 link). Multiple MMEs can establish links (M3 links) and eMBMS sessions with the same eNB, thereby allowing RAN sharing where multiple operators are sharing the same eNB / multi-cell coordination entity (MCE) for providing eMBMS services. eNB / MCE support eMBMS data sessions with multiple MBMS gateways (MBMS-GW). Session tear-down and the release of resources are delayed with a configurable amount of time after the stream control transmission protocol (SCTP) link down is detected. During this delay, existing eMBMS sessions may be switched over to another MME.

3.12.3 LTE3201 system impact Interdependencies between features The LTE3201: eMBMS in RAN-sharing Deployment Support feature is an extension of the LTE1117: LTE MBMS feature. There is no specific feature activation flag for the LTE3201: eMBMS in RAN-sharing Deployment Support feature. The LTE3201: eMBMS in RAN-sharing Deployment Support feature functionality is available when the LTE1117: LTE MBMS feature is activated. The LTE3201: eMBMS in RAN-sharing Deployment Support feature impacts the following features: •

•

g

LTE4: RAN Sharing This feature can be enabled along with LTE1117: LTE MBMS. The eNB/MCE supports multiple M3 links to different MMEs. eMBMS sessions can be established with different MMEs and different MBMS-GWs. LTE2807: IPv6 Support for M1 & M3 Interfaces The eNB supports a mix of IPv4- and IPv6-based M1 and M3 links. Note: The eNB's support of a mix of IPv4- and IPv6-based M1 and M3 links is not a dual-stack support.

Impact on interfaces The LTE3201: eMBMS in RAN-sharing Deployment Support feature has no impact on interfaces.

100

© 2017 Nokia

DN09237915 Issue: 01A



Impact on network management tools The LTE3201: eMBMS in RAN-sharing Deployment Support feature has no impact on network management tools. Impact on system performance and capacity The LTE3201: eMBMS in RAN-sharing Deployment Support feature has no impact on system performance or capacity.



System release


FDD LTE17

not supported


OMS

not supported

not applicable

Table 54

Flexi Multiradio 10 Indoor BTS

AirScale BTS

FL17

FL17 UE

3GPP R9

NetAct NetAct 17.2



not supported

not supported

MME

SAE GW

3GPP R11

not applicable


Alarm ID

Alarm name 7657 Base station connectivity degraded

For alarm descriptions, see LTE Radio Access Operating Documentation/Reference/Alarms and Faults. BTS faults and reported alarms Table 55

Existing BTS faults related to LTE3201

Fault ID

Fault name


Alarm name

M3 interface recovery failure

7657 Base station connectivity degraded

M3 interface setup failure

7657 Base station connectivity degraded

For fault descriptions, see LTE Radio Access Operating Documentation/Reference/Alarms and Faults. Commands There are no commands related to the LTE3201: eMBMS in RAN-sharing Deployment Support feature.

DN09237915 Issue: 01A

© 2017 Nokia

101



Measurements and counters There are no measurements or counters related to the LTE3201: eMBMS in RANsharing Deployment Support feature. Key performance indicators There are no key performance indicators related to the LTE3201: eMBMS in RANsharing Deployment Support feature. Parameters Table 56

New parameters introduced by LTE3201: eMBMS in RAN-sharing Deployment Support Full name

Abbreviated name

m3LinkBounceSupTi LNMCE mer

M3 link bounce supervision timer

Table 57

Managed object

Parent structure

-

Modified/impacted parameters by LTE3201: eMBMS in RAN-sharing Deployment Support Full name

Abbreviated name

Managed object

Parent structure

M3 Primary address

m3ipAddrPrim

LNM3

-

Administrative state

administrativeSta LNM3 te

-

LTE MME M3 link identifier

lnM3Id

LNM3

-


actMBMS

LNBTS

-




g

102



Note: The LTE3201: eMBMS in RAN-sharing Deployment Support feature functionality is available when the LTE1117: LTE MBMS feature is activated. There is a common license for the LTE1117: LTE MBMS and LTE3201: eMBMS in RAN-sharing Deployment Support features.

© 2017 Nokia

DN09237915 Issue: 01A



3.13 LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I The LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I feature supports additional uplink (UL) carrier aggregation (CA) band combinations, thereby providing more options to increase uplink throughput.

3.13.1 LTE3213 benefits The LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I feature supports additional band combinations for CA. Consequently, it guarantees higher UL peak rates in areas with overlapping cell deployments.

3.13.2 LTE3213 functional description With the LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I feature enabled, the eNB supports the following additional carrier aggregation band combinations (3CC in downlink and 2CC in uplink): DL (Band 1 + Band 3 + Band 7) + UL (Band 1 + Band 3) DL (Band 1 + Band 3 + Band 7) + UL (Band 1 + Band 7) DL (Band 1 + Band 3 + Band 7) + UL (Band 3 + Band 7) DL (Band 2 + Band 12 + Band 30) + UL (Band 2 +Band 12) DL (Band 2 + Band 12 + Band 12) + UL (Band 2 +Band 12) – Band 12 contiguous DL (Band 4 + Band 12 + Band 30) + UL (Band 4 +Band 12) DL (Band 4 + Band 12 + Band 12) + UL (Band 4 +Band 12) – Band 12 contiguous

• • • • • • •

g

Note: The bandwidth combination set is 0 as described in 3GPP TS 36.101.

3.13.3 LTE3213 system impact Interdependencies between features The LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I feature is enabled together with the LTE1092: Uplink Carrier Aggregation – 2CC feature. Impact on interfaces The LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I feature has no impact on interfaces. Impact on network management tools The LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I feature has no impact on network management tools. Impact on system performance and capacity The LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I feature has no impact on system performance or capacity.

DN09237915 Issue: 01A

© 2017 Nokia

103







Airscale BTS

FL17

FL17

OMS

UE




Not supported

Not supported

MME

SAE GW

NetAct




Alarms There are no alarms related to the LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I feature. BTS faults and reported alarms There are no faults related to the LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I feature. Commands There are no commands related to the LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I feature. Measurements and counters There are no measurements or counters related to the LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I feature. Key performance indicators There are no key performance indicators related to the LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I feature. Parameters There are no parameters related to the LTE3213: Additional Uplink Carrier Aggregation Band Combinations – I feature. Sales information Table 60



104


© 2017 Nokia


DN09237915 Issue: 01A



3.14 LTE3230: UL Interference Offsets 3GPP TS36.101 introduces restrictions concerning UEs' maximum transmit power. Those restrictions are introduced to protect other services from interference. The LTE3230: UL Interference Offsets feature helps operator to cope with the restrictions affecting outer regions of bandwidth. To stay in line with the maximum transmission power restriction requirements LTE3230: UL Interference Offsets allows operator to influence the uplink scheduler (UL-S) interference measurements by introducing a configurable offset.

3.14.1 LTE3230 benefits The LTE3230: UL Interference Offsets feature helps the operator to handle situations when the UE is operating with a reduced transmit power in a part of the UL spectrum. It is supported by: • •

introducing adjustable offset to the uplink interference measurement to affect scheduling process enabling the operator to keep the physical uplink control channel (PUCCH) unaffected by allocating its resources closer to the center of the band

3.14.2 LTE3230 functional description Functional overview 3GPP TS36.101 holds several lists of restrictions regarding UEs' maximum transmit power. Transmit power restrictions are typically introduced to protect other services from interference, such as: • • •

spurious emissions harmonic interference intermodulation products

They depend on the physical resource block (PRB) location, including the allocation size given to the UE. Particular restrictions concentrate on the outer regions of the radio spectrum, constituting bandwidth boundaries, which are usually submitted to the resource configuration of the physical uplink control channel (PUCCH). To avoid those restrictions affecting the PUCCH, the LTE3230: UL Interference Offsets feature relocates the PUCCH regions towards the center of the cell’s bandwidth. This establishes one inner physical shared channel (PUSCH) section located between PUCCH resources and two outer PUSCH regions, with at least one of them under a maximum UE power restriction. This is contrary to the LTE825: Uplink Outer Region Scheduling feature which supports scheduling of one outer region only.

DN09237915 Issue: 01A

© 2017 Nokia

105


Figure 6

LTE825: Uplink Outer Region Scheduling and LTE3230: UL Interference Offsets feature comparison

Nominalsystem bandwidth

PUCCH

systembandwidth


PUSCH and PRACH

PUCCH

LTE825:UL Outer RegionScheduling

LTE3230:UL Interference Offsets

PUSCH (outerregion)

PUSCH (outerregion)

PUCCH

PUCCH

PUSCH (innerregion)

PRACH (eitheror)

PUSCH (innerregion)

PUCCH

PUCCH

blanked

PUSCH blanked (outerregion)

LTE3230: UL Interference Offsets introduces support for two of the listed restrictions. A specific restriction is indicated and configured by O&M, establishing the extent of power limitation assumed by the eNB. The selected restriction defines the range of UEs submmited to a configured setting. Those UEs are presumed by the eNB to operate with reduced UL maximum power. It can relate to all UEs or a certain scope. UEs require notification about established restrictions via information elements in a system information block type 2 (SIB2). UL power reduction results in a decrease of UEs' maximum throughput along with lower interference created in the restricted PRB ranges. Reduced interference causes those ranges to be favored by the UL scheduler, which is counterproductive. To avoid scheduling in the restricted ranges, an offset is introduced into the UL interference measurements. The offset is a percentage of a default interference correction value.The offset value is added in the UL scheduler, so that preferred scheduling areas are separated from those with power restrictions. Through the introduction of interference offset operator affects the probability of selection power restricted PRBs as preffered scheduling area.

g

Note: In situations when the Additional Maximum Power Reduction (A-MPR) concerns more than two aspects (sets of restrictions pertaining to PRB starting offset and allocation size), LTE3230: UL Interference Offsets will avoid these restrictions by either moving the allocation to a PRB range where the restrictions does not apply or moving the allocation into a later transmission time interval (TTI) where resources without restriction can be allocated. Dividing the UL spectrum is a complex task leading to the creation of several areas where different rules apply. LTE3230: UL Interference Offsets simplifies the process for the operator, limiting necessary actions to: •

106

specifying the parameter actUlPwrRestrScn value (identifying applicable restrictions set)

© 2017 Nokia

DN09237915 Issue: 01A



specifying the value of a single interference offset introduced in one PRB region. It may also apply to certain PRB ranges in both outer scheduling regions.

•

Table 61

LTE3230: UL Interference Offsets parameter actUlPwrRestrScn configuration cases Parameter Active UL Power Restriction Scenario (actUlPwrRestrScn)set to band18_26

g

Parameter Active UL Power Restriction Scenario (actUlPwrRestrScn)set to band30_ns21

LTE3230: UL Interference Offsets supported UEs

The Tx power restriction applies to UEs supporting both band 18 and 26 (restriction introduced only in band 18)

The Tx power restriction applies to all UEs

Cell's bandwidth

10 MHz

10 MHz

Established PUSCH regions

UL spectrum reconfiguration done by the eNB results in establishing two outer PUSCH regions, 15 PBRs each. Lower, consisting of PRBs #0 to #14, and upper #35 to #49

UL spectrum reconfiguration done by the eNB results in establishing two outer PUSCH regions, 7 PRBs each. Lower, consisting of PRBs #0 to #6, and upper #43 to #49

Applicable offset

A configurable offset is added to the UL interference measurements related to lowest 15 PRBs, whenever UL scheduler encounters UEs supporting both band 18 and 26

An interference offset is added to outer regions UL interference measurements, whenever UL scheduler assesses UE’s allocation possibilities

Comments

The outer PUSCH regions may be considered as scheduling areas if the central bandwidth resources are used up.

Note: When LTE3230: UL Interference Offsets is activated, and the actUlPwrRestrScn parameter is configured, the value assumed by the blanked PUCCH (blankedPucch)parameter is ignored. The PUCCH PRBs are selected in a manner that narrows down the Tx power restriction set of the configured scenario to the following cases: •

•

•

The UE’s PUSCH allocation is subject to a restriction, and the operator-configured interference offset is applied. This occurs in either the lower frequency (parameter actUlPwrRestrScn value is set to band18_26) or in both outer scheduling regions (parameter actUlPwrRestrScn value is set to band30_ns21). The UE’s PUSCH allocation would fall under a restriction, but the structure of the UL spectrum (with PUCCH shifted inward) no longer allow this allocation – no further action is required. The UE’s PUSCH allocation would fall under a restriction, but the scheduler will not use it, meaning that the allocation is moved to a scheduling area with no restrictions applied.

Sounding reference signal (SRS) resources are unaffected by any restrictions regarding LTE3230: UL Interference Offsets. Restrictions do not affect UL bandwidth, concentrating on limiting the maximum UL power in certain PRB ranges.

DN09237915 Issue: 01A

© 2017 Nokia

107


g


Note: Sounding reference signal (SRS) is a reference signal received by eNB from UE. It is used to determine the channel state and the carrier frequencies it should assign to the UE for transmission.

3.14.3 LTE3230 system impact LTE3230: UL Interference Offsets impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be activated parallel to the LTE3230: UL Interference Offsets feature: • •

LTE1130: Dynamic PUCCH Allocation One of the following features: – –

LTE46: Channel-aware Scheduler (UL) LTE619: Interference-aware UL Scheduling

The following features must be deactivated when the LTE3230: UL Interference Offsets feature is activated: • • • • • • • • • •

LTE1336: Interference Aware UL Power Control LTE2224: UL Triggered Mobility LTE1092: UL Carrier Aggregation – 2CC LTE944: PUSCH Masking LTE1059: Uplink Multi-cluster Scheduling LTE825: Uplink Outer Region Scheduling LTE1709: Liquid Cell LTE1542: FDD Supercell LTE2445: Combined Supercell LTE3268: Combined Supercell for HetNet

The LTE3230: UL Interference Offsets feature is impacted by the following features: •

•

LTE2664: Load-based PUCCH Region The LTE2664: Load-based PUCCH Region feature can change the number of PUCCH PRBs during runtime. The LTE3230: UL Interference Offsets feature will adjust its scheduling areas when this is done. LTE3128: LTE-M It is recommended to configure the LTE-M narrowband so that it is located in the central PUSCH region.

Impact on interfaces The LTE3230: UL Interference Offsets feature has no impacts on interfaces. Impact on network management tools The LTE3230: UL Interference Offsets feature has no impact on network management tools.

108

© 2017 Nokia

DN09237915 Issue: 01A



Impact on system performance and capacity LTE3230: UL Interference Offsets will impact UL peak throughput in every situation that includes shifting PUCCH resources. In both band 18 (only UEs with band 26 capability) and band 30, the inner region of the bandwidth is used for peak throughput. In band 18, peak throughput is not reduced by physical random access channel transmission time interval (PRACH TTI) because PRACH can be allocated in one of the side regions containing 15 PRBs. In band 30, peak throughput would be reduced by PRACH TTI because both outer regions are affected by the power limitation restrictions.

3.14.4 LTE3230 reference data LTE3230: UL Interference Offsets requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements Table 62 System release FDD-LTE17 Flexi Zone Controller FL17

LTE3230: UL Interference Offsets hardware and software requirements Flexi Multiradio BTS


Not supported FL17 OMS

FL17 UE


Nokia AirScale BTS

3GPP R8 mandatory

NetAct NetAct 17.2





Alarms There are no alarms related to the LTE3230: UL Interference Offsets feature. BTS faults and reported alarms There are no faults related to the LTE3230: UL Intrference Offsets feature. Commands There are no commands related to the LTE3230: UL Interference Offsets feature. Measurements and counters There are no measurements or counters related to the LTE3230: UL Interference Offsets feature. Key performance indicators There are no key performance indicators related to the LTE3230: UL Interference Offsets feature. Parameters

DN09237915 Issue: 01A

© 2017 Nokia

109


Table 63


New parameters introduced by LTE3230: UL Interference Offsets Full name

Abbreviated name

Managed object

Parent structure

MRBTS/L NBTS/LN CEL/LNC EL_FDD

Activate UL Power Restriction Scenario

actUlPwrRestrScn

UL interference offset

ulInterferenceOff MRBTS/L set NBTS/LN CEL/LNC EL_FDD


LTE3230: UL Interference Offsets sales information


License control


Pool license


3.14.5 Activating and configuring LTE3230 for band 18 Instructions to activate and configure the LTE3230: UL Interference Offsets feature for band 18 using the BTS Site Manager Before you start •


Activation procedure requires object locking. Activation procedure uses the following parameters and activation flags: • •

•

actUlPwrRestrScn ulInterferenceOffset


The following features must be activated parallel to the LTE3230: UL Interference Offsets feature: • •


–

The following features must be deactivated when the LTE3230: UL Interference Offsets feature is activated: • • • •

110


LTE1336: Interference Aware UL Power Control LTE2224: UL Triggered Mobility LTE1092: UL Carrier Aggregation – 2CC LTE944: PUSCH Masking

© 2017 Nokia

DN09237915 Issue: 01A


• • • • • •

•


LTE1059: Uplink Multi-cluster Scheduling LTE825: Uplink Outer Region Scheduling LTE1709: Liquid Cell LTE1542: FDD Supercell LTE2445: Combined Supercell LTE3268: Combined Supercell for HetNet

Preconfiguration – – – – – – – – – – –

The LNCEL object parameter value ulsSchedMethod must be set either to channel aware or interference aware. The LNCEL_FDD object parameter value actAutoPucchAlloc must be set to true. The LNCEL_FDD object parameter value ulChBw must be set to 10 MHz. The LNCEL object parameter value actUlpcMethod must be set neither to PusschlAwPucchCL nor PuschlAwPucchOL. The LNBTS object parameter value actULCAggr must be set to false. The LNCEL_FDD object parameter value actPuschMask must be set to false. The LNCEL_FDD object parameter value actUlMultiCluster must be set to false. The LNCEL_FDD object parameter value selectOuterPuschRegion must be set to none. The LNCEL_FDD object parameter value actLiquidCell must be set to false. The LNCEL_FDD object parameter value actSuperCell must be set to false. The LNCEL_FDD object parameter value actCombSuperCell must be set to false.

Procedure 1


2


DN09237915 Issue: 01A

© 2017 Nokia

111




3

Proceed to the LTE Carriers page.

4

Set the Downlink (TX) carriers object parameter EARFCN to 5900.

5


6

Go to the LNCEL_FDD object. Object path: MRBTS ► LNBTS ► LNCEL ► LNCEL_FDD

7

Set parameter values. Sub-steps a) Set the actUlPwrRestrScn parameter value to band18_26. If the actUlPwrRestrScn parameter value is set to band18_26 then: •

The LNCEL object parameter earfcnUl should show the value 23900.

b) Set the ulInterferenceOffset parameter value.

8

Go to the APUCCH_FDD object. Object path: MRBTS ► LNBTS ► LNCEL ► LNCEL_FDD ► APUCCH_FDD

9

Set the selectPrachRegion parameter value to OuterUpperEdge.


112


© 2017 Nokia

DN09237915 Issue: 01A




3.14.6 Activating and configuring LTE3230 for band 30 Instructions to activate and configure the LTE3230: UL Interference Offsets feature for band 30 using the BTS Site Manager Before you start •


Activation procedure requires object locking. Activation procedure uses the following parameters and activation flags: • •

•

actUlPwrRestrScn ulInterferenceOffset


The following features must be activated parallel to the LTE3230: UL Interference Offsets feature: • •


–

The following features must be deactivated when the LTE3230: UL Interference Offsets feature is activated: • • • • • • • • • •

•

LTE1336: Interference Aware UL Power Control LTE2224: UL Triggered Mobility LTE1092: UL Carrier Aggregation – 2CC LTE944: PUSCH Masking LTE1059: Uplink Multi-cluster Scheduling LTE825: Uplink Outer Region Scheduling LTE1709: Liquid Cell LTE1542: FDD Supercell LTE2445: Combined Supercell LTE3268: Combined Supercell for HetNet

Preconfiguration – –

DN09237915 Issue: 01A


The LNCEL object parameter value ulsSchedMethod must be set either to channel aware or interference aware. The LNCEL_FDD object parameter value actAutoPucchAlloc must be set to true.

© 2017 Nokia

113


– – – – – – – – –


The LNCEL_FDD object parameter value ulChBw must be set to 10 MHz. The LNCEL object parameter value actUlpcMethod must be set neither to PusschlAwPucchCL nor PuschlAwPucchOL. The LNBTS object parameter value actULCAggr must be set to false. The LNCEL_FDD object parameter value actPuschMask must be set to false. The LNCEL_FDD object parameter value actUlMultiCluster must be set to false. The LNCEL_FDD object parameter value selectOuterPuschRegion must be set to none. The LNCEL_FDD object parameter value actLiquidCell must be set to false. The LNCEL_FDD object parameter value actSuperCell must be set to false. The LNCEL_FDD object parameter value actCombSuperCell must be set to false.

Procedure 1


2


3

Proceed to the LTE Carriers page.

4

Set the Downlink (TX) carriers object parameter EARFCN to 9820

5


6


114

© 2017 Nokia

DN09237915 Issue: 01A


7


Set parameter values. Sub-steps a) Set the actUlPwrRestrScn parameter value to band30_ns21. If the actUlPwrRestrScn parameter value is set to band30_ns21 then: • •

The MFBIPR object parameter (MRBTS ► LNBTS ► MFBIPR) addSpectrEmissReq must be set to 21. The LNCEL object parameter earfcnUl should show the value 27710.

b) Set the parameter ulInterferenceOffset value.

8

Go to the APUCCH_FDD object. Object path: MRBTS ► LNBTS ► LNCEL ► LNCEL_FDD ► APUCCH_FDD

9

Set the selectPrachRegion parameter value to InnerUpperEdge.




3.14.7 Deactivating LTE3230 Instructions to deactivate the LTE3230: Ul Interference Offsets feature using the BTS Site Manager Before you start •


•

DN09237915 Issue: 01A

Deactivation procedure requires object locking.

Preconfiguration

© 2017 Nokia

115


– –


A connection between the eNB and the management system must be established and working. The LTE3230 feature is activated. The LNCEL object parameter actUlPwrRestrScn is set to either band18_26 or band30_ns21.

Procedure 1


2


3


4


5

Set the actUlPwrRestrScn value to none.

6


116


© 2017 Nokia

DN09237915 Issue: 01A




3.15 LTE3264: Additional PRS Subframe Configurations The LTE3264: Additional PRS Subframe Configurations feature introduces support for additional subframe configurations for the positioning reference signal (PRS) transmission. The support of location services (LCS) allows to determine the position of a UE within the RAN. The UEs are able to detect the PRS and derive measurements, based on the PRS.

3.15.1 LTE3264 benefits The LTE3264: Additional PRS Subframe Configurations feature provides the following benefit: •

In markets where customers have a mix of AirScale/FSMF equipment, the observed time difference of arrival (OTDOA) feature runs using positioning reference signal (PRS) transmission on the subframes, thus allowing for a more adaptive and diverse deployment.

3.15.2 LTE3264 functional description Functional overview The feature allows Nokia equipment to operate in market regions already committed to sending PRS symbols in predetermined subframes. The following additional subframe configurations are supported for the PRS transmission: •

• •

FDD (5, 10, 15, and 20 MHz) 7, 14, 27, 47, 67, 87, 107, 127 and 147 with a repetition = 1 and a periodicity of 160 ms. In addition, the 5-MHz cell bandwidth supports a repetition = 2. TDD UL/DL configuration 1 (10 and 20 MHz) 49, 69, 129, 149 with a repetition = 1 and a periodicity of 160 ms. TDD UL/DL configuration 2 (10 and 20 MHz) 28, 48, 68, 108, 128, 148 with a repetition = 1 and a periodicity of 160 ms.

The UE is informed about the PRS configuration via the LTE positioning protocol (LPP). The LPP is a protocol defined between the UE and the enhanced serving mobile location centre (E-SMLC). It communicates the PRS settings of the network to the UEs as well as the OTDOA measurements (also called a reference signal time difference (RSTD)) from the UEs to the E-SMLC. The LPP protocol entities are transparent to the eNBs, and the computation of the UE positions is done in the E-SMLC. The operator needs to provide PRS settings of the network and antenna positions of eNBs to the E-SMLC.

DN09237915 Issue: 01A

© 2017 Nokia

117



3.15.3 LTE3264 system impact Interdependencies between features The LTE3264: Additional PRS Subframe Configurations feature is an extension of the LTE495: OTDOA feature. The LTE3264: Additional PRS Subframe Configurations feature is enabled together with the LTE495: OTDOA. The LTE3264: Additional PRS Subframe Configurations feature impacts the following features: •

•

•

•

•

• • • • •

LTE1117: LTE MBMS The operator has additional choices on where to position the PRS subframes. FDDspecific MBMS subframe patterns now support prsConfigurationIndex parameter values of 7, 14, 27, 47, 67, 87, 107, 127, 147. LTE3199: Support for Multiple MBSFN and Synchronization Areas This feature is a follow-up to the LTE1117: eMBMS feature, in which a cell can support multiple MBSFN areas, and an eNB can provide eMBMS services on multiple carriers. LTE3200: Dynamic Allocation of eMBMS Resources This feature is a follow-up to the LTE1117: eMBMS feature, in which an active number of eMBMS sessions will dynamically adjust the number of eMBMS subframes allocated. New subframes that can be used for OTDOA must be excepted from MBMS usage. LTE1891: eNode B Power Saving – Micro DTX If the LTE3264: Additional PRS Subframe Configurations feature is activated, micro DTX has to consider that OFDM symbols used for OTDOA are found in different locations. LTE2085: SIB Reception with Parallel Measurement Gaps The list showing the subframe usage for various functions has to be updated. The current SIB timing allows new PRS locations. LTE1987: Downlink Adaptive Closed Loop SU MIMO (4x4) LTE1709: Liquid Cell LTE1543: 8x2 SU MIMO with TM9 LTE3128: LTE-M This feature needs to adapt the pattern of valid subframes. LTE2120: TDD SIB Reception with Parallel Measurement Gaps DL scheduler has to handle the collision between the new PRS configurations and SIB scheduling subframes when LTE2120 is activated.

Impact on interfaces The LTE3264: Additional PRS Subframe Configurations feature has no impact on interfaces. Impact on network management tools The LTE3264: Additional PRS Subframe Configurations feature has no impact on network management tools. Impact on system performance and capacity

118

© 2017 Nokia

DN09237915 Issue: 01A



The LTE3264: Additional PRS Subframe Configurations feature has no impact on system performance or capacity.



System release FDD LTE17




AirScale BTS

FL17

FL17

OMS

UE

-

3GPP R8 UE capabilities


NetAct


MME

NetAct 17.2

-

SAE GW -

Alarms There are no alarms related to the LTE3264: Additional PRS Subframe Configurations feature. BTS faults and reported alarms There are no faults related to the LTE3264: Additional PRS Subframe Configurations feature. Commands There are no commands related to the LTE3264: Additional PRS Subframe Configurations feature. Measurements and counters There are no measurements or counters related to the LTE3264: Additional PRS Subframe Configurations feature. Key performance indicators There are no key performance indicators related to the LTE3264: Additional PRS Subframe Configurations feature. Parameters Table 66


Abbreviated name

Managed object

Parent structure

Max phase drifting

maxPhaseDrifting

BTSSCL

-

PRS activation

actOtdoa

LNCEL

-

PRS Tx diversity activation

actPrsTxDiv

LNCEL

-

PRS bandwidth

prsBandwidth

LNCEL

-

DN09237915 Issue: 01A

© 2017 Nokia

119


Table 66


Existing parameters related to LTE3264 (Cont.) Full name

Abbreviated name

Managed object

Parent structure

PRS configuration index prsConfigurationI LNCEL ndex

-

PRS muting

prsMuting

LNCEL

-

PRS muting info

prsMutingInfo

LNCEL

prsMuting

PRS muting info pattern prsMutingInfoPatt LNCEL length ernLen

prsMuting

PRS Number of DL frames prsNumDlFrames

LNCEL

-

PRS power boost

prsPowerBoost

LNCEL

-

SI window length

siWindowLen

LNCEL

-


drxOnDuratT

LNCEL

-


dlChBw

LNCEL

-

Network synchronization btsSyncMode mode

BTSSCL

-

Activate supercell configuration

actSuperCell

LNCEL

-

Activate liquid cell configuration

actLiquidCell

LNCEL

-

Activate LPPa support for OTDOA

actLPPaOtdoa

LNCEL

-


actMBMS

LNCEL

-

MBSFN EARFCN

mbsfnEarfcn

MBSFN

-

MBSFN downlink channel bandwidth

mbsfnDlChBw

MBSFN

-

Activation ETWS support actETWS

LNBTS

-

Activation CMAS support actCMAS

LNBTS

-

Twofold transmission of sib2xTransmit SIBs per SI window

SIB

-

Activate enhanced actEicic inter-cell interference coordination

LNCEL

-

CSI-RS subframe configuration

LNCEL

-

csiRsSubfrConf

Parameter relationships: • •

If btsSyncMode is set to PhaseSync, maxPhaseDrifting must be configured. If actOtdoa is set to true: –

120

siWindowLen must be set appropriately, depending on the individual PRS configuration. For details on appropriate values, see the siWindowLen parameter in Reference documentation.

© 2017 Nokia

DN09237915 Issue: 01A


–


configuration of the following parameters is required: prsPowerBoost, prsConfigurationIndex, prsBandwidth, prsNumDlFrames, actPrsTxDiv.

If numOfTxPorts is set to 1, actPrsTxDiv must be set to false. If actPrsTxDiv is set to true:

•

– –

drxProfile2-drxOnDuratT must be greater than 3. drxProfile3-drxOnDuratT must be greater than 3.

The range of the prsBandwidth parameter depends on dlChBw.

•




License control


Pool license


3.15.5 Activating LTE3264 Before you start The LTE3264: Additional PRS Subframe Configurations feature is enabled as long as the LTE495: OTDOA feature is enabled.

3.15.6 Deactivating LTE3264 Before you start The LTE3264: Additional PRS Subframe Configurations feature is deactivated when the LTE495: OTDOA feature is deactivated.

3.16 LTE3279: Support for Configurable eMBMS SYNC Protocol Benefits, functionality, system impact, reference data, instructions of the feature The LTE3279: Support for Configurable eMBMS SYNC Protocol feature enhances the LTE1117: LTE Multimedia Broadcast Multicast Service (MBMS) feature by introducing SYNC protocol configuration, and integration to work with different Broadcast/Multicast Service Centers (BM-SC).

g

Note: For the LTE17 release, this feature will only be usable in laboratory conditions and is not suitable for field deployment. For more information on limitations, see Limitations.

DN09237915 Issue: 01A

© 2017 Nokia

121



3.16.1 LTE3279 benefits The LTE3279: Support for Configurable Evolved Multimedia Broadcast Multicast Service (eMBMS) SYNC Protocol feature improves the operability of the eMBMS service by giving the operator access to more configuration options through the introduction of: • •

SYNC protocol configuration SYNC protocol integration to work with different BM-SCs

3.16.2 LTE3279 functional description Overview Evolved Multimedia Broadcast Multicast Service (eMBMS) is the multicast standard for LTE. It allows multimedia content to be sent once and then distributed to and received by multiple end users. This distribution method is an alternative to unicast for scenarios wherein a large number of users are interested in the same content. In LTE, eMBMS allows the combining of MBMS transmissions. This is known as a Multimedia Broadcast Single Frequency Network (MBSFN) transmission. In an MBSFN transmission, all eNBs in a given MBSFN area must have the radio transmissions sent within the same timing sequence. The SYNC protocol is used to synchronize the radio interface transmissions of data from all eNBs belonging to that MBSFN area. It allows the eNB to identify the timing for radio frame transmissions and detect packet loss. The SYNC protocol in a BM-SC sets a time stamp value indicating the time of the synchronization sequence. This time stamp is based on a time reference; different BMSC vendors, however, use different time references. The LTE3279: Support for Configurable eMBMS SYNC Protocol feature provides the flexibility to switch between different time reference configuration options used by different BM-SC vendors. The feature is required for Internet of Things (IoT) with different BM-SC vendors. The following channels and interfaces are used in the operation of the LTE3279 feature: • • • •

Multicast control channels (MCCH) - this channel transports control content such as MBMS sub-frame allocation information and modulation scheme for mobile users M1 interface: a user plane interface; the SYNC protocol is used to ensure that content is synchronized for MBSFN transmissions M2 interface: a control plane interface, the M2 interface carries session control signaling to the eNB M3 interface: a control plane interface, the M3 interface carries session control signaling, including MBMS 'Session Start' and 'Session Stop' messages.

With the LTE3279: Support for Configurable eMBMS SYNC Protocol feature, the following O&M configuration options are provided on the eNB and BM-SC: •

Configurable M3 time reference Time base used by BM-SC for M3: – – –

122

Coordinated Universal Time (UTC) International Atomic Time (TAI) Global Positioning System (GPS)

© 2017 Nokia

DN09237915 Issue: 01A



Configurable M1 time reference Time base used by BM-SC for M1:

•

Gregorian UTC Auto Adjust Leap UTC GPS

– – –

Time offset Time offset to account for the time stamp not falling within the eNB scheduling window for the eNB and BM-SC Elapsed Octet Count including or excluding Sync Header The inclusion or exclusion of the M1 SYNC PDU header in the elapsed octet counter

•

•

The feature is an enhancement of the LTE1117: LTE MBMS feature and is available once the LTE1117 feature is enabled. It uses the actMBMS feature flag used by the LTE1117 feature. Configurable M3 time reference A configurable common time reference with BM-SC, indicated over the M3 interface, is supported. This common time reference interprets the absolute time of the MBMS data from the BM-SC. M3 time reference - time formats The three possible time formats are: TAI: Continuous time in seconds from Jan-01-1900 (Does not include leap seconds) UTC: Time in seconds from Jan-01-1970 (Unix Time – Does not automatically adjust for leap seconds) GPS: Continuous time in seconds from Jan-06-1980 (Does not include leap seconds)

• • •

Depending on the time format selected, the time needs to be adjusted appropriately.

g

Note: • • • •

TAI = International Atomic Time (the same reference as Gregorian Jan-01-1900) GPS = Global Positioning System TAI = GPS + 19 seconds (fixed offset) TAI = UTC + 19 seconds (fixed offset) + 17 seconds (current value of variable offset)

Configurable M1 time reference The eNB identifies the timing of radio frame transmissions, based on the information received and the configurable common time reference. The eNB supports a configurable common time reference with BM-SC to interpret the time stamp in the SYNC PDU from the BM-SC. M1 time reference - time formats The three possible time formats are:

DN09237915 Issue: 01A

© 2017 Nokia

123


• • •


Gregorian – UTC: Time in seconds from Jan-01-1900 (Does not automatically adjust for leap seconds) Auto Adjust Leap – UTC: Time in seconds from Jan-01-1900 (Automatically adjusts for leap seconds) GPS – Continuous time in seconds from Jan-06-1980 (Does not include Leap Seconds)

Depending on the time format selected, the time needs to be adjusted appropriately. Time offset With the LTE3279 feature, the eNB supports a configurable Sync Time Offset that is used when the M1 time reference is set to GPS. Elapsed Octet Count including or excluding Sync Header With the LTE3279 feature, the eNB supports a configurable parameter which indicates whether the Elapsed Octet Count (sent by the BM-SC) includes or excludes the Sync Header. Limitations For the LTE17 release, this feature will only be usable in laboratory conditions and is not suitable for field deployment. The following restriction is added in LTE17 release: •

All eMBMS scenarios must be presented with the following default time synchronization settings – –

M1 link time reference: Gregorian UTC M3 link time reference: TAI

The above settings are aligned with the 3GPP recommendations.

3.16.3 LTE3279 system impact LTE3279: Support for Configurable eMBMS SYNC Protocol impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following feature must be activated before the LTE3279: Support for Configurable eMBMS SYNC Protocol feature can be used: •

LTE1117: LTE MBMS

The LTE3279: Support for Configurable eMBMS SYNC Protocol feature is automatically enabled when LTE1117 is enabled and does not require activation. Impact on interfaces The LTE3279: Support for Configurable eMBMS SYNC Protocol feature has no impact on interfaces. Impact on network management tools

124

© 2017 Nokia

DN09237915 Issue: 01A



The LTE3279: Support for Configurable eMBMS SYNC Protocol feature has no impact on network management tools. Impact on system performance and capacity The LTE3279: Support for Configurable eMBMS SYNC Protocol feature has no impact on system performance or capacity.

3.16.4 LTE3279 reference data LTE3279: Support for Configurable eMBMS SYNC Protocol requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements Table 68


System release FDD-LTE 17 Flexi Zone Controller not supported



Nokia AirScale BTS

SBTS17

FL17

OMS support not required

UE 3GPP R9 UE capabilities



Flexi Zone Access Point FL17A

MME support not erquired


Alarms There are no alarms related to the LTE3279: Support for Configurable eMBMS SYNC Protocol feature. BTS faults and reported alarms There are no faults related to the LTE3279: Support for Configurable eMBMS SYNC Protocol feature. Commands There are no commands related to the LTE3279: Support for Configurable eMBMS SYNC Protocol feature. Measurements and counters Table 69 Counter ID


Measurement

M8030C 7

M1 SYNC Average Sequences Delay

M8030 - LTE MBMS

M8030C 8

M1 SYNC Control PDUs

M8030 - LTE MBMS

M8030C 9

M1 SYNC Not Received Control PDUs

M8030 - LTE MBMS

DN09237915 Issue: 01A

© 2017 Nokia

125


Table 69

New counters introduced by LTE3279 (Cont.)

Counter ID M8030C 10


Counter name

Measurement M8030 - LTE MBMS

M1 SYNC Data PDUs

Key performance indicators There are no key performance indicators related to the LTE3279: Support for configurable eMBMS SYNC protocol feature. Parameters Table 70


Abbreviated name

Managed object

M1 time reference

m1TimeRef

MRBTS/L NBTS/M1 SYNC

M3 time reference

m3TimeRef

MRBTS/L NBTS/LN MCE

MBMS sync time offset

mbmsSyncTimeOffse MRBTS/L t NBTS/M1 SYNC

Parent structure

Elapsed count includes M1 Sync elapsedCountInclu MRBTS/L header desHeader NBTS/M1 SYNC

Table 71


Abbreviated name

Managed object


actMBMS

MRBTS/L NBTS

MBMS SYNC period

mbmsSyncPeriod


MBMS SYNC reference

mbmsSyncRef


Parent structure




126

License control Pool License

© 2017 Nokia


DN09237915 Issue: 01A



3.16.5 Activating and configuring LTE3279 Instructions to activate and configure the LTE3279: Support for Configurable eMBMS SYNC Protocol feature using the BTS Site Manager Before you start The LTE3279 feature is an enhancement of LTE1117 and LTE3199. It is recommended to check the activation procedure for the actMBMS parameter used by LTE1117 and LTE3199 prior to activating and configuring LTE3279. •

The activation procedure requires the following: – – – – – – –

•

The eNB must have an activated RNW database. The eNB must be in service. NetAct must be in service. A DCN connection to the eNB must be established via OMS. At least one S1 link must be established. MBMS-related information in the transport domain must be configured. MBMS must be deactivated. The LNBTS parameter actMBMS is set to false. At least one MBSFNCEL (LNCEL: MBSFNCEL) object must be defined per MBSFNSYNCAREA_FDD object.


The following feature must be activated together with the LTE3279: Support for Configurable eMBMS SYNC Protocol feature: •

g –

Note: The LTE3279 feature is an enhancement of LTE1117. The LTE1117 feature uses the same activation parameter as LTE3279. The following feature is related to the LTE3279: Support for Configurable eMBMS SYNC Protocol: •

•

LTE1117: LTE MBMS

LTE3199: Support for Multiple MBSFN and Synchronization Areas

Other information: –

–

The MCE configuration must be aligned between cells belonging to the same MBSFN synchronization area. Parameters and the configuration options are listed in Configuration details of LTE3279. The confiugration of the LTE3199: Support for Multiple MBSFN and Synchronization Areas may have an effect on the LTE3279 feature. Refer to the LTE3199 feature document for the activation and configuration procedure.

Procedure 1

DN09237915 Issue: 01A


© 2017 Nokia

127


2



3


4


5

Set the actMBMS value to true.

6

Set the parameter values as specified in Configuration details of LTE3279.

7




Result Expected outcome • •

128

The LTE3279 feature is enabled. The configured information is persistently stored in the eNB.

© 2017 Nokia

DN09237915 Issue: 01A


3.16.5.1


Configuration details of LTE3279 The following must be configured: Name

Range and step

M1 time reference

•

GregorianUTC (0)

M1SYNC:m1TimeRef

•

AutoAdjustLeapUTC (1)

•

GPS (2)

•

TAI (0)

•

UTC (1)

•

GPS (2)

M3 time reference

LNMCE:m3TimeRef

MBMS sync time offset

0 to 599990 ms, step 10 ms

Default Setting GregorianUTC (0)

TAI (0)

0

M1SYNC:mbmsSyncTimeOf fset Elapsed count includes M1 Sync header

•

0 (false)

•

1 (true)

0 (false)

M1SYNC:elapsedCountIn cludesHeader

g

Note: • •

•

If M1SYNC:m1TimeRef is set to GregorianUTC or AutoAdjustLeapUTC, parameters from structure M1SYNC:mbmsSyncRef are mandatory. If M1SYNC:m1TimeRef is se to to GPS, then the M1SYNC:mbmsSyncTimeOffset parameter is used to specify the time offset between BM-SC and eNB. If M1SYNC:m1TimeRef is set to GPS, then M1SYNC:mbmsSyncTimeOffset is mandatory.

M1SYNC parameters •

•

•

DN09237915 Issue: 01A

m1TimeRef – M1 Time Reference This parameter represents the time reference used for the M1 interface. It reflects the time reference used by the BM-SC to timestamp MBMS sync PDUs. The value of this parameter must be the same as used by the BM-SC as the Common Time Reference. mbmsSyncTimeOffset – MBMS Sync Time Offset This parameter specifies the time offset between the BM-SC and the eNB. The time stamp in the sync header minus mbmsSyncTimeOffset will be used by the eNB. All the eNBs have the same offset for a given bearer service. Any modifications made should also be made on the BM-SC. This parameter, however, can be useful if eNBs are not synchronized with one or several BM-SCs. The value specified in this parameter applies to all M1 bearers. elapsedCountIncludesHeader – Elapsed Count Includes M1 Sync Header This parameter indicates if the elapsed octet count includes the sync header. This parameter needs to be set carefully based on BMSC compatibility.

© 2017 Nokia

129



MCE parameters •

m3TimeRef – M3 Time Reference This parameter represents the time reference used by the BM-SC over the M3 interface. The default value of TAI is considered the 3GPP standard default value. The value of this parameter must be the same as used by the BM-SC as the Common Time Reference.

3.16.6 Deactivating LTE3279 Instructions to deactivate the LTE3279:Support for Configurable eMBMS SYNC Protocol feature using the BTS Site Manager Before you start The LTE3279 feature is an enhancement of LTE1117 and LTE3199. It is recommended to check the deactivation procedure for the actMBMS parameter used by LTE1117 and LTE3199 prior to deactivating LTE3279. •

The deactivation procedure requires: – – –

The eNB must be in service, and have an activated RNW database. NetAct is in service and a DCN connection to the eNB is established via OMS. The LTE3279 feature is activated. The LNBTS parameter actMBMS is set to true.

Procedure 1


2


130

© 2017 Nokia

DN09237915 Issue: 01A




3


4


5

g

Set the actMBMS value to false. Note: Optionally, all MBMS-related configuration in LNMCE, M1SYNC,

MBSFNSYNCAREA_FDD, MBSFN_FDD, LNM3, LNCEL, MBSFNCEL, SIB and IRFIM may be removed.

6




Result Expected outcome The LTE3279 feature is deactivated.

3.17 LTE3290: SRVCC Trigger Enhancement Benefits, functionality, system impact, reference data, instructions of the feature The LTE3290: SRVCC Trigger Enhancement feature introduces a new parameter to control the trigger of the single radio voice call continuity (SRVCC) procedure. The SRVCC allows a seamless handover procedure between LTE and WCDMA/GSM, but it

DN09237915 Issue: 01A

© 2017 Nokia

131



can be rejected by the IMS if triggered too early. The new, operator-configurable parameter delays the start of the SRVCC and prevents the procedure from being rejected by the IMS.

3.17.1 LTE3290 benefits The LTE3290: SRVCC Trigger Enhancement feature improves the success rate of interRAT handovers. The IMS no longer rejects the single radio voice call continuity (SRVCC) procedure during the early phase of the VoLTE call setup if the srvccDelayTimer parameter is active.

3.17.2 LTE3290 functional description An overview of how the configurable timer prevents the SRVCC procedure from being rejected during the initial phase of VoLTE establishment Functional overview The LTE3290: SRVCC Trigger Enhancement feature prevents the single radio voice call continuity (SRVCC) procedure from being rejected by the IMS. Single radio voice call continuity (SRVCC) is a mechanism to hand over UEs that have a QCI-1 bearer (VoIP) activated when changing from an LTE cell to a WCDMA/GSM cell. The voice bearer, that is subject to a handover (HO), is served via the circuit-switched (CS) domain on the WCDMA/GSM side. SRVCC is always executed without a packetswitched (PS)-handover support (it means that established non-voice bearers are not handed over to WCDMA/GSM). Figure 7

132

VoLTE call setup with SRVCC delay timer

© 2017 Nokia

DN09237915 Issue: 01A



IMS may reject the SRVCC procedure during the pre-alerting and alerting phases of VoLTE call setup procedure, which may lead to VoLTE call drops. To avoid such a rejection, the srvccDelayTimer parameter (which is also used to activate the LTE3290: SRVCC Trigger Enhancement feature) delays the start of the SRVCC procedure. The timer starts after the first QCI-1 bearer setup. When the eNB receives the A2 event trigger, it configures and activates SRVCC-related B2 measurements. Every B2 SRVCC-related measurement report sent by the UE is discarded by the eNB during the srvccDelayTimer period. When the srvccDelayTimer timer expires, the next B2 SRVCC-related measurement report can trigger the SRVCC procedure normally, as described in the LTE872: SRVCC to WCDMA and LTE873: SRVCC to GSM features.

g

Note: When the SRVCC delay timer is running for a UE, and a UE performs a handover or re-establishment procedure, the SRVCC delay timer will not be restarted at a target cell after the HO or re-establishment procedure. Figure 8

Handling the SRVCC delay timer during SRVCC (to WCDMA/GSM)

3.17.3 LTE3290 system impact LTE3290: SRVCC Trigger Enhancement impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be activated before activating the LTE3290: SRVCC Trigger Enhancement feature: • •

LTE10: EPS Bearers for Conversational Voice at least one of the following features: – –

LTE872: SRVCC to WCDMA LTE873: SRVCC to GSM

The following features must be deactivated before activating the LTE3290: SRVCC Trigger Enhancement feature: •

LTE2832: SRVCC Due to Admission Control Rejection

Impact on interfaces The LTE3290: SRVCC Trigger Enhancement feature has no impact on interfaces.

DN09237915 Issue: 01A

© 2017 Nokia

133



Impact on network management tools The LTE3290: SRVCC Trigger Enhancement feature has no impact on network management tools. Impact on system performance and capacity The LTE3290: SRVCC Trigger Enhancement feature has no impact on system performance or capacity.

3.17.4 LTE3290 reference data LTE3290: SRVCC Trigger Enhancement requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements Table 73 System release FDD-LTE 17 Flexi Zone Controller FL17



Nokia AirScale BTS

FL17

FL17



UE

NetAct

3GPP R8





Alarms There are no alarms related to the LTE3290: SRVCC Trigger Enhancement feature. BTS faults and reported alarms There are no faults related to the LTE3290: SRVCC Trigger Enhancement feature. Commands There are no commands related to the LTE3290: SRVCC Trigger Enhancement feature. Measurements and counters Table 74 Counter ID

134

Existing counters related to LTE3290 Counter name

Measurement

M8016C Inter-System Handovers 50 preparations to UTRAN with SRVCC

LTE Inter System Handover

M8016C Failed Inter-System Handover 51 preparations to UTRAN with SRVCC due to timer


M8016C Failed Inter-System Handover 52 preparations to UTRAN with


© 2017 Nokia

DN09237915 Issue: 01A


Table 74


Existing counters related to LTE3290 (Cont.)

Counter ID

Counter name

Measurement

SRVCC due to target eNB admission control

g

M8016C Failed Inter-System Handover 53 preparations to UTRAN with SRVCC caused by other reasons


M8016C Inter-System Handover 54 preparations to GERAN with SRVCC


M8016C Failed Inter-System Handover 55 preparations to GERAN with SRVCC due to timer


M8016C Failed Inter-System Handover 56 preparations to GERAN with SRVCC due to target eNB admission control


M8016C Failed Inter-System Handover 57 preparations to GERAN with SRVCC caused by other reasons


Note: Measurements discarded due to a delay timer introduced by the LTE3290: SRVCC Trigger Enhancement feature do not increment counter M8009C0. For counter descriptions, see LTE Performance Measurements and Key Performance Indicators. Key performance indicators The LTE3290: SRVCC Trigger Enhancement feature may improve the handover preparation success rate, which is visible in the following KPIs: Table 75

Existing key performance indicators related to LTE3290

KPI ID

KPI name

LTE_6102a

Inter RAT HO Preparation Attempts to UTRAN with SRVCC

LTE_6103a

Inter RAT HO Preparation Failure Ratio to UTRAN with SRVCC due to timer expiry

LTE_6104a

Inter RAT HO Preparation Failure Ratio to UTRAN with SRVCC due to admission control

LTE_6105a

Inter RAT HO Preparation Failure Ratio to UTRAN with SRVCC due to other reasons

LTE_6106a

Inter RAT HO Preparation Success Ratio to UTRAN with SRVCC

LTE_6107a

Inter RAT HO Preparation Attempts to GERAN with SRVCC

LTE_6108a

Inter RAT HO Preparation Failure Ratio to GERAN with SRVCC due to timer expiry

LTE_6109a

Inter RAT HO Preparation Failure Ratio to GERAN with SRVCC due to admission control

LTE_6110a

Inter RAT HO Preparation Failure Ratio to GERAN with SRVCC due to other reasons

DN09237915 Issue: 01A

© 2017 Nokia

135


Table 75


Existing key performance indicators related to LTE3290 (Cont.)

KPI ID

KPI name

LTE_6111a

Inter RAT HO Preparation Success Ratio to GERAN with SRVCC

LTE_6115a

E-UTRAN Total Inter RAT HO UTRAN with SRVCC Success Ratio

LTE_6116a

E-UTRAN Total Inter RAT HO GERAN with SRVCC Success Ratio

For KPI descriptions, see LTE Performance Measurements and Key Performance Indicators. Parameters Table 76


SRVCC delay timer

Table 77

Abbreviated name

Managed object

Parent structure

srvccDelayTimer

MRBTS/L NBTS

–

Managed object

Parent structure

MRBTS/L NBTS

–


Abbreviated name

Activate AC triggered SRVCC

actAcSrvcc

For parameter descriptions, see FDD-LTE BTS Parameters. Sales information Table 78



License control


Pool license


3.17.5 Activating and configuring LTE3290 The SRVCC procedure is prevented from being rejected during the initial phase of VoLTE establishment after activating the LTE3290: SRVCC Trigger Enhancement feature. Before you start •


–

136

Activation procedure does not impact ongoing single radio voice call continuity (SRVCC) procedures. Only the first QCI1 setup starts the SRVCC delay timer; modification of timer value does not impact the SRVCC timer when it is already running. Activation procedure does not cause downtime, and the feature can be activated at any time of the day.

© 2017 Nokia

DN09237915 Issue: 01A


•

Feature interdependencies The following features must be activated before activating the LTE3290: SRVCC Trigger Enhancement feature: – –

LTE10: EPS Bearers for Conversational Voice at least one of the following features: • •

•


LTE872: SRVCC to WCDMA LTE873: SRVCC to GSM

Preconfiguration –

– –

The LTE2832: SRVCC Due to Admission Control Rejection feature is disabled (the Activate AC triggered SRVCC (actAcSrvcc) parameter is set to false). The SRVCC delay timer (srvccDelayTimer) value is set to 0. If the LTE3290: SRVCC Trigger Enhancement feature may support the SRVCC to WCDMA, then the LTE872: SRVCC to WCDMA activating parameters have to be configured (set to true): • • •

–

Activate SRVCC to WCDMA (actSrvccToWcdma) Activate handover from LTE to WCDMA (actHOtoWcdma) Activate support of conversational voice bearer (actConvVoice)

Other LTE872-related mandatory parameters have to be configured as described in the LTE872: SRVCC to WCDMA. If the LTE3290: SRVCC Trigger Enhancement feature may support the SRVCC to GSM, then the LTE873: SRVCC to GSM activating parameters have to be configured (set to true): • •

Activate SRVCC to GSM (actSrvccToGsm) Activate support of conversational voice bearer (actConvVoice)

Other LTE873-related mandatory parameters have to be configured as described in the LTE873: SRVCC to GSM.

Procedure 1


2


DN09237915 Issue: 01A

© 2017 Nokia

137




3


4


5

Set SRVCC delay timer (srvccDelayTimer) to a value different than 0. Setting the timer parameter to a value different than 0 activates the LTE3290 feature and defines the time period during which the SRVCC B2 measurements are discarded by the eNB after QCI1 bearer establishment. The SRVCC delay timer (srvccDelayTimer) value range is from 0 to 20 seconds with a step of 0.5 s.

6




Result The LTE3290 feature is activated, and the eNB is ready to discard the B2 measurements during the timer-defined period (after the establishment of the first QCI1 E-RAB).

3.17.6 Deactivating LTE3290 The SRVCC procedure is no longer prevented from rejection after deactivating the LTE3290: SRVCC Trigger Enhancement feature. Before you start •

138

Procedure notifications

© 2017 Nokia

DN09237915 Issue: 01A


–

•


Deactivation procedure does not cause downtime, and the feature can be deactivated at any time of the day.

Preconfiguration –

The SRVCC delay timer (srvccDelayTimer) value is different than 0.

Procedure 1


2


3


4


5

Set SRVCC delay timer (srvccDelayTimer) to 0. Changing SRVCC delay timer (srvccDelayTimer) to 0 does not stop the ongoing timer. Modification of SRVCC delay timer (srvccDelayTimer)'s value is valid on the next timer expiry.

6

Send the commissioning plan file to the BTS. Sub-steps a) Go to the Send Parameters page. b) Select an appropriate Send option. •

DN09237915 Issue: 01A

If the BTS has not been commissioned, select All parameters.

© 2017 Nokia

139


•


If the BTS has been already commissioned, select Only changes.


Result The SRVCC delay timer is turned off (after the ongoing timer expires) and no longer prevents the SRVCC procedure from being rejected.

3.18 LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I The LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I feature supports additional downlink (DL) carrier aggregation (CA) band combinations for four component carriers (CCs).

3.18.1 LTE3439 benefits The LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I feature provides new band combinations that support higher downlink peak rates in areas with overlapping cell deployments when carrier aggregation is enabled; this offers higher data peak rates for the users within the network.

3.18.2 LTE3439 functional description When the LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I feature is enabled, the eNB supports the following additional carrier aggregation (CA) band combinations: CA band combinations with two bands: • • • •

Band 2 + Band 2 + Band 4 + Band 4 (band 2 and band 4 non-contiguous) Band 2 + Band 2 + Band 66 + Band 66 (band 2 non-contiguous, band 66 noncontiguous, band 66 contiguous for bandwidth class B and C) Band 2 + Band 2 + Band 66 + Band 66 (band 2 contiguous; band 66 non-contiguous, contiguous for bandwidth class B and C) Band 3 + Band 3 + Band 7 + Band 7 (band 3 non-contiguous; band 7 noncontiguous, bandwidth combination set 0, 1)

CA band combinations with three bands: • • • •

140

Band 1 + Band 3 + Band 3 + Band 5 (band 3 contiguous) Band 1 + Band 3 + Band 7 + Band 7 (band 7 non-contiguous) Band 1 + Band 3 + Band 3 + Band 8 (band 3 contiguous) Band 1 + Band 5 + Band 7 + Band 7 (band 7 non-contiguous, contiguous)

© 2017 Nokia

DN09237915 Issue: 01A



Band 2 + Band 2 + Band 4 + Band 12 (band 2 and band 4 non-contiguous) Band 2 + Band 4 + Band 7 + Band 7 (band 7 non-contiguous) Band 2 + Band 4 + Band 4 + Band 12 (band 4 non-contiguous) Band 2 + Band 2 + Band 5 + Band 30 (band 2 non-contiguous) Band 2 + Band 5 + Band 5 + Band 30 (band 5 contiguous) Band 2 + Band 2 + Band 5 + Band 66 (band 2 non-contiguous) Band 2 + Band 2 + Band 12 + Band 30 (band 2 non-contiguous) Band 2 + Band 12 + Band 66 + Band 66 (band 66 non-contiguous, contiguous for bandwidth class B and C) Band 2 + Band 2 + Band 12 + Band 66 (band 2 non-contiguous, contiguous) Band 2 + Band 2 + Band 29 + Band 30 (band 2 non-contiguous) Band 3 + Band 5 + Band 7 + Band 7 (band 7 non-contiguous, contiguous) Band 3 + Band 3 + Band 7 + Band 8 (band 3 non-contiguous, bandwidth combination set 0, 1) Band 3 + Band 7 + Band 7 + Band 8 (band 7 non-contiguous, bandwidth combination set 0, 1) Band 3 + Band 3 + Band 7 + Band 20 (band 3 contiguous) Band 3 + Band 3 + Band 7 + Band 32 (band 3 contiguous)

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

CA band combinations with four bands: Band 1 + Band 3 + Band 5 + Band 7 Band 1 + Band 3 + Band 7 + Band 8 Band 1 + Band 3 + Band 7 + Band 20 Band 1 + Band 3 + Band 7 + Band 28 Band 2 + Band 5 + Band 30 + Band 66 Band 2 + Band 12 + Band 30 + Band 66

• • • • • •

g

Note: The bandwidth combination set equals 0 according to 3GPP TS 36.101., if not mentioned otherwise.

3.18.3 LTE3439 system impact Interdependencies between features The LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I feature is activated together with the LTE2531: FDD Downlink Carrier Aggregation 4CC feature. Impact on interfaces The LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I feature has no impact on interfaces. Impact on network management tools The LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I feature has no impact on network management tools. Impact on system performance and capacity The LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I feature has no impact on system performance or capacity.

DN09237915 Issue: 01A

© 2017 Nokia

141







AirScale BTS

FL17

FL17

OMS

UE




Not supported

Not supported

MME

SAE GW

NetAct

3GPP R12 UE capabilities 3GPP R13 UE capabilities

-

-

Alarms There are no alarms related to the LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I feature. BTS faults and reported alarms There are no faults related to the LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I feature. Commands There are no commands related to the LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I feature. Measurements and counters There are no measurements or counters related to the LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I feature. Key performance indicators There are no key performance indicators related to the LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I feature. Parameters There are no parameters related to the LTE3439: Additional Carrier Aggregation Band Combinations 4CC – I feature. Sales information Table 80



142


© 2017 Nokia


DN09237915 Issue: 01A


Descriptions of transport and transmission features

4 Descriptions of transport and transmission features 4.1 LTE2807: IPv6 Support for M1 and M3 Interfaces The LTE2807: IPv6 Support for M1 and M3 Interfaces feature extends the evolved multimedia broadcast/multicast service (eMBMS) (LTE1117: LTE MBMS) by adding the IPv6 support for M3 and M1 interfaces. M3 is a control plane interface between MME and eNB. The main function of the M3 interface is session management (MBMS sessions start/stop/update). M1 is a user plane interface between the MBMS-GW and the eNB used for MBMS data delivery.

4.1.1 LTE2807 benefits The LTE2807: IPv6 Support for M1 and M3 Interfaces feature enables eMBMS services over the operator's IPv6 transport network. The operator can use the existing IPv6 transport network with its greater address capacity.

4.1.2 LTE2807 functional description IPv6 IPv6 is an extension of the address room of IPv4 (factor 7.9 * 1028). The IPv6 addresses are 128 bits long. They are given in the hexadecimal format (eight blocks with 16 bits each), for example, 2001:db58:85a3:08d3:1319:8a2e:0370:7344. eMBMS eMBMS is MBMS for LTE. It is introduced with the LTE1117: LTE MBMS feature. Multimedia broadcast/multicast services (MBMS) are point-to-multipoint services, which are designed to provide efficient delivery of broadcast and multicast services – both within a cell and in the core network. Target applications include mobile and radio broadcasting, live streaming video services, as well as file delivery and emergency alerts.

DN09237915 Issue: 01A

© 2017 Nokia

143


Figure 9


Overview M1/M3 interface

Contents Provider

PDN Gateway

BMSC SGmb

SGi-mb

Sm

MME M3

MBMS GW

M3 M1

MCE

M1 MCE

MCE

MCE eNB

Table 81

Explanations: Overview of the M1/M3 interface Abbreviation

BMSC

eNB

Long text Broadcast/multicast service center

function • • • •

144

© 2017 Nokia

eMBMS user service provisioning and delivery eMBMS bearer service authorization and initiating eMBMS transmission scheduling and delivery Entry point for content providers' transmissions

DN09237915 Issue: 01A


Table 81


Explanations: Overview of the M1/M3 interface (Cont.) Abbreviation

Long text

MBMS GW

function

Multimedia broadcast/multicast • services gateway •

MCE

Sm

Multicell/multicast coordination entity

•

eMBMS admission control

•

eMBMS radio resources allocations

MBMS GW - MME (control plane interfaces)

•

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

•

SGmb

BMSC - MBMS GW (control plane interfaces)

• •

SGi-mb

eMBMS packet delivery to eNBs eMBMS session control towards LTE

BMSC - MBMS GW

•

eMBMS session control (session start/stop/update) eMBMS service area control point-to-point data delivery

M3 interface: MME – eNB The LTE2807: IPv6 Support for M1 and M3 Interfaces feature extends the eNB to support M3 over IPv6. Stream Control Transmission Protocol (SCTP) on top of the IP layer is used as the signaling method. The main function of the M3 application protocol is the control signaling of the MBMS session (for example, MBMS session start and stop). The M3 control plane interface is terminated at the logical MBMS coordinating entity (MCE) within the eNB. The main MBMS feature, LTE1117: LTE MBMS, requires that the S1 C-plane IPv4 addresses are identical with the M3 IPv4 addresses. This is also valid for the LTE2807: IPv6 Support for M1 and M3 Interfaces feature, using M3 IPv6 addresses.

DN09237915 Issue: 01A

© 2017 Nokia

145


Figure 10


M3 interface

M3AP

SCTP IP Datalinklayer) Physicallayer

M1 interface: MBMS GW – eNB The network element (NE) supports the eMBMS M1 interface transport in IPv6 multicast. The status of the LTE2807 feature's activation flag status determines whether the M1 interface can work in IPv6. The M1 interface is terminated at the eNB. Figure 11

M1 interface

U-PlanePDUs SYNC

GTP-U UDP IP(multicast) Datalinklayer

Physicallayer

146

© 2017 Nokia

DN09237915 Issue: 01A



4.1.3 LTE2807 system impact LTE2807: IPv6 Support for M1 and M3 Interfaces impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The LTE2807: IPv6 Support for M1 and M3 Interfaces feature interacts with the following features: •

•

•

LTE3201: eMBMS in RAN Sharing Deployment The LTE1117: LTE MBMS feature supports only one M1 and one M3 link. The LTE3201: eMBMS in RAN Sharing Deployment feature introduces multiple M3 and M1 links. LTE1117: LTE MBMS The LTE2807: IPv6 Support for M1 and M3 Interfaces feature is based on the LTE1117: LTE MBMS feature. LTE2299: Dual Stack IPv4/ IPv6 for S1/X2 The LTE2299: Dual Stack IPv4/ IPv6 for S1/X2 feature is a successor and an extension of LTE125 (IPv6 for U/C-plane). This feature introduced IPv4/v6 dual stack functionality for S1/X2 transport in xL16. The LTE2299 C-plane part is being reused and extended for the LTE2807 M3.

Impact on interfaces The LTE2807: IPv6 Support for M1 and M3 Interfaces feature impacts interfaces as follows: •

M3 interface –

•

IPv6 support

M1 interface –

Introduction of IPv6 multicasting

Impact on network management tools The LTE2807: IPv6 Support for M1 and M3 Interfaces feature has no impact on network management tools. Impact on system performance and capacity The LTE2807: IPv6 Support for M1 and M3 Interfaces feature has no impact on system performance or capacity.

4.1.4 LTE2807 reference data LTE2807: IPv6 Support for M1 and M3 Interfaces requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements

DN09237915 Issue: 01A

© 2017 Nokia

147


Table 82



System release



Nokia Airscale BTS

not applicable

not applicable

FL17


OMS

UE

not applicable

not applicable

not applicable

FDD-LTE 17



not applicable

not applicable

NetAct

MME

SAE GW

not applicable

not applicable

not applicable

Alarms Table 83


Alarm ID

Alarm name

7604

BTS OPERATION DEGRADED

7657

BASE STATION CONNECTIVITY DEGRADED

BTS faults and reported alarms Table 84

BTS faults introduced by LTE2807

Fault ID

Fault name


Alarm name

6850

M3 interface recovery failure

7657

BTS CONNECTIVITY DEGRADED

6851

M3 interface setup failure

7657

BTS CONNECTIVITY DEGRADED

Measurements and counters There are no measurements or counters related to the LTE2807: IPv6 Support for M1 and M3 Interfaces feature. Key performance indicators There are no key performance indicators related to the LTE2807: IPv6 Support for M1 and M3 Interfaces feature. Parameters Table 85


Abbreviated name

Activate IPv6 MBMS M1 Interface Support

148

actIPv6MBMS

© 2017 Nokia

Managed object

Parent structure

LNBTS

DN09237915 Issue: 01A


Table 86



Abbreviated name

Managed object

M3 Primary Access

m3ipAddrPrim

LNM3

M3 Secondary IPv4 address

m3ipAddrSec

LNM3

Parent structure




License control Software Asset Monitoring


4.1.5 Activating and configuring LTE2807 Before you start •

Feature interdependencies The LTE2807: IPv6 Support for M1 and M3 Interfaces feature interacts with the following features: –

–

–

•

LTE3201: eMBMS in RAN Sharing Deployment The LTE1117: LTE MBMS feature supports only one M1 and one M3 link. The LTE3201: eMBMS in RAN Sharing Deployment feature introduces multiple M3 and M1 links. LTE1117: LTE MBMS The LTE2807: IPv6 Support for M1 and M3 Interfaces feature is based on the LTE1117: LTE MBMS feature. LTE2299: Dual Stack IPv4/ IPv6 for S1/X2 The LTE2299: Dual Stack IPv4/ IPv6 for S1/X2 feature is a successor and an extension of LTE125 (IPv6 for U/C-plane). This feature introduced IPv4/v6 dual stack functionality for S1/X2 transport in xL16. The LTE2299 C-plane part is being reused and extended for the LTE2807 M3.

Preconfiguration – – –

The LTE1117: LTE MBMS feature is activated (actMBMS =true). The LTE2299: Dual Stack IPv4 / IPv6 feature is enabled for IPv6 support (actIpv6 = true) The LTE2807 feature uses the same IPv6 licence as LTE2299: Dual Stack IPv4/ IPv6 for S1/X2

•

Procedure 1

DN09237915 Issue: 01A


© 2017 Nokia

149


2



3


4


5

Set the actIPv6MBMS value to true.

actIPv6MBMS is only allowed to be set to true for AirScale eNBs. 6




Result • • •

150

The feature is activated and any parameter settings are permanently stored. Only IPv6 addresses will be allowed to be configured on the M1 interface. NetAct and BTS Site Manager are notified about the changed configuration.

© 2017 Nokia

DN09237915 Issue: 01A



4.1.6 Deactivating LTE2807 Before you start Preconfiguration • • •

The LTE1117: LTE MBMS feature is activated. The LNBTS parameter actMBMS = true. The LTE2807 feature uses the same IPv6 licence as LTE2299: Dual Stack IPv4/ IPv6 for S1/X2 One or more IPv6 MBMS multicast sessions are active.

Procedure 1


2


3


4


DN09237915 Issue: 01A

© 2017 Nokia

151



5

Set the actIPv6MBMS value to false.

6

Send the commissioning plan file to the BTS. Sub-steps a) Go to the Send Parameters page. b) Select an appropriate Send option. •

As the BTS has been already commissioned, select Only changes.


Result • • •

The feature is deactivated and any parameter settings are permanently stored. Only IPv4 multicast addresses will be allowed to be configured on M1 interface. NetAct and BTS Site Manager are notified about the changed configuration.

4.2 LTE2855: Fronthaul Active WDM The LTE2855: Fronthaul Active WDM feature introduces new components for multiplexing/de-multiplexing of CPRI/OBSAI links between baseband units (BBUs) and RRHs/RFMs. It supports proven interoperability and performance, using active WDM components with Nokia Flexi System Modules release 3 or higher and all remote radio head/radio frequency modules (RRHs/RFMs).

4.2.1 LTE2855 benefits The LTE2855: Fronthaul Active WDM feature provides cost reduction involved in deploying multiple fiber optics, thereby utilizing the optical fibers more efficiently.

4.2.2 LTE2855 functional description LTE2855 functional description The LTE2855: Fronthaul Active WDM feature supports the following characteristics: •

152

The solution supports multiplexing and de-multiplexing of CPRI/OBSAI links between Flexi System Module release 3 or higher and RFM/RRH.

© 2017 Nokia

DN09237915 Issue: 01A


• • • • •


The active WDM components include a passive WDM filter with active management and an SFP color conversion unit. The SFP color conversion unit allows deploying RRH/RFM with optical grey SFPs. It converts grey to colored signals and vice versa. Separate variants of active WDM Mux units for indoor and outdoor deployments are provided. The maximum supported distance between a system module and RFMs/RRHs is 20 km. The solution supports: – – – –

chain and star topologies. DC and AC as inputs to an active WDM unit. link rates up to CPRI rate 7. network management functionality that enables continuous monitoring of E2E network`s health.

The active WDM network management functionality enables the following information to be displayed: ingress/egress optical levels, fiber cuts. In addition to the network monitoring functionality, the solution supports external alarm inputs and outputs. This functionality monitors customer-defined inputs, providing inventory and alarm monitoring, while at the same time supporting outputs to external devices such as generators, cooling systems, video surveillance, and so on to be turned on/off. Customers are able to remotely monitor the alarms at the remote sites from hum locations via the optical supervisory functionality. The Network management system (NMS) connectivity as well as the alarms are transported via an independent Optical supervisory channel (OSC), enabling local and remote management. This solution also enables Fiber break monitoring for the respective link. An overview of the functionality is provided in Figure 12: Fronthaul Active WDM components.

DN09237915 Issue: 01A

© 2017 Nokia

153


Figure 12


Fronthaul Active WDM components

Outdoorhardenedactive WDMMux(TLU/PMU/SSM)

SFP

SFP

RRHwith B&WSFP

NMS

SFP

RRHwith B&WSFPs

Fronthaul fiber

SystemModules

SFP SFP SFP

Indoor Black&White ActiveWDMMux SFPs (TLU/PMU/OSU)

4.2.3 LTE2855 system impact The LTE2855: Fronthaul Active WDM feature has no impact on features, interfaces, network management tools, and system performance and capacity.

4.2.4 LTE2855 reference data LTE2855: Fronthaul Active WDM requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements Table 88 System release FDD-LTE17 Flexi Zone Controller not supported

LTE2855 hardware and software requirements Flexi Multiradio BTS not supported OMS support not required


Nokia AirScale BTS

FL17

FL17 UE





not supported

not supported

MME

SAE GW



The LTE2855: Fronthaul Active WDM feature requires the following WDM components: • • •

154

1830 VWM TLU : Translator Line Unit 1830 VWM OSU : Optical Supervisory Unit 1830 VWM PMU : Photonic Managed Unit

© 2017 Nokia

DN09237915 Issue: 01A



5620 SAM: Service Aggregation Manager (Network management system) or NetAct SSM: Site Monitoring Module (optional)

• •

All this HW components are described in separate descriptions in NOLS (https://online.networks.nokia.com/entry/open/DoUp?action=login&TYPE=33554433&RE ALMOID=06-00016567-e062-1083-acba-8). Alarms Alarms are provided via the NMS and NetAct. More details are described in the Product manual. BTS faults and reported alarms There are no faults related to the LTE2855: Fronthaul Active WDM feature. Commands There are no commands related to the LTE2855: Fronthaul Active WDM feature. Measurements and counters There are no measurements or counters related to the LTE2855: Fronthaul Active WDM feature. Key performance indicators The NMS as well as the NetAct system provide KPI`s. Parameters There are no parameters related to the LTE2855: Fronthaul Active WDM feature. Sales information Table 89



DN09237915 Issue: 01A

License control -

© 2017 Nokia


155

Descriptions of operability features


5 Descriptions of operability features 5.1 LTE684: DHCP Server for Flexi LTE BTS Site Devices The LTE684: DHCP Server for Flexi LTE BTS Site Devices feature introduces an internal dynamic host configuration protocol (DHCP) server for Flexi Multiradio BTS site devices. Dynamic Host Configuration Protocol (DHCP) is used to automatically provide IP configuration parameters to the equipment or hosts connected to the local management port of the Flexi Multiradio BTS. BTS Site Manager allows the configuration of DHCP parameters for the BTS.

5.1.1 LTE684 benefits The LTE684: DHCP Server for Flexi LTE BTS Site Devices feature enables: • • •

Adding a new DHCP configuration Modifying an existing DHCP configuration Deleting a DHCP configuration

5.1.2 LTE684 functional description Functional Overview Dynamic Host Configuration Protocol (DHCP) is used to automatically provide IP configuration parameters to the equipment or hosts connected to the site support equipment (SSE) of the BTS. BTS Site Manager allows the configuration of DHCP parameters for the BTS. The SSE can be connected to the local port (or ports) of the system/control modules.

g

Note: Depending on the HW variant, the port can be a dedicated port for SSE or a local maintenance port. The public IP address of the transmission sub-module must be configured before setting the DHCP configurations. All DHCP IP addresses must be in the same subnet as the public IP address of the transmission sub-module. The SSE IP addresses may be configured manually or provided through DHCP. The internal DHCP server for the BTS site devices enables a dynamic IP host configuration for IP devices connected to a system/control module BTS subnet at the BTS site. The planned IP addresses of the SSE can be configured in the DHCP server. The BTS transport supports an IP subnet for SSE and routing between this subnet and the backhaul interface. The site local devices receive an IP configuration from the DHCP server located in the system/control module. Along with the IP address, other network parameters may also be provided to the host. The parameters are, for example: •

156

Default gateway IP address

© 2017 Nokia

DN09237915 Issue: 01A



Lease time Subnet mask

• •

The DHCP server is configured as part of the transport configuration.

5.1.3 LTE684 system impact Interdependencies between features The LTE684: DHCP Server for Flexi LTE BTS Site Devices feature is impacted by the following features: LTE746: IP-based Filtering for BTS SSE The LTE746 IP filtering rule takes care to pass SSE packets through. LTE871: Transport Support for Site Support Equipment LTE871 allows the BTS subnet to be configured on BTS SM, and the DHCP server to assign an IP address to the SSE client from this BTS subnet.

• •

Impact on interfaces The LTE684: DHCP Server for Flexi LTE BTS Site Devices feature has no impact on interfaces. Impact on network management tools The LTE684: DHCP Server for Flexi LTE BTS Site Devices feature has no impact on network management tools. Impact on system performance and capacity The LTE684: DHCP Server for Flexi LTE BTS Site Devices feature has no impact on system performance or capacity.

5.1.4 LTE684 reference data Requirements Table 90 System release RL10

LTE684 hardware and software requirements Flexi Multiradio BTS LBTS1.0


Nokia AirScale BTS

LBTS4.0

FL16S4



not supported

not supported


OMS

UE

NetAct

MME

SAE GW

not supported

not applicable

not applicable

not applicable

not applicable

not appilcable

Alarms There are no alarms related to the LTE684: DHCP Server for Flexi LTE BTS Site Devices feature. BTS faults and reported alarms

DN09237915 Issue: 01A

© 2017 Nokia

157



There are no faults related to the LTE684: DHCP Server for Flexi LTE BTS Site Devices feature. Commands There are no commands related to the LTE684: DHCP Server for Flexi LTE BTS Site Devices feature. Measurements and counters There are no measurements or counters related to the LTE684: DHCP Server for Flexi LTE BTS Site Devices feature. Key performance indicators There are no key performance indicators related to the LTE684: DHCP Server for Flexi LTE BTS Site Devices feature. Parameters Table 91


Abbreviated name

Managed object

Parent structure

dhcpHardwareident IHCP ifier

-

Entry set for DHCP client_identifier IHCP clients identified by a system name

-

DHCP Fixed IP Address

dhcpFixedIpAddres IHCP s

-

DHCP Range Start IP Address

dhcpRangeStart

IHCP

-

DHCP Range End IP Address

dhcpRangeEnd

IHCP

-

DHCP Hardware Identifier




License control

Basic Software (BSW)

-


5.1.5 Other instructions Example: Inspecting and modifying DHCP configurations in BTS Site Manager Purpose Dynamic Host Configuration Protocol (DHCP) is used to automatically provide IP configuration parameters to the equipment or hosts connected to the local management port of the BTS. BTS Site Manager allows the configuration of DHCP parameters for the Flexi Multiradio BTS.

158

© 2017 Nokia

DN09237915 Issue: 01A



Precondition The public IP address of the transmission sub-module must be configured before setting the DHCP configurations. All DHCP IP addresses must be in the same subnet as the public IP address of the transmission sub-module.

Procedure 1

Inspect the DHCP configurations. Click Configuration ► TRS ► IP .... The IP Addresses window opens. Figure 13

DN09237915 Issue: 01A

Path DHCP Server

© 2017 Nokia

159


Figure 14


DHCP configurations

The following DHCP configurations are displayed in the IP Addresses window: • • •

2

Add a new DHCP configuration. •

•

•

160

External equipment IP addresses via DHCP DHCP client address range Other IP addresses via DHCP (client ID and HW ID)

To add an external equipment IP address via the DHCP, select the check box next to the external equipment and modify the IP address in the field (optional). Click send to save the changes. To add a DHCP client address range, select the check box for the DHCP client address range and modify the IP address of the range (optional). Click send to save the changes. To add another IP address via the DHCP, select the type field (client ID or HW ID) and enter the client ID name or HW address in the ID field. Specify the IP address under the IP address column. Click send to save the changes.

© 2017 Nokia

DN09237915 Issue: 01A



Configuration of the external equipment IP address via the the DHCP requires a BTS reset. 3

Modify an existing DHCP configuration. • • •

External equipment IP address via DHCP settings: you can modify the IP address of the corresponding external equipment. DHCP client address range: you can modify the IP address range. Other IP addresses via DHCP: you can modify the Type, ID, or IP address fields.

Click send to save the changes.

4

Delete a DHCP configuration. If you need to delete a DHCP configuration, do the following: • • •

To delete an external equipment IP address via DHCP, clear the check box for the external equipment. To delete the DHCP client address range, clear the check box for DHCP client address range. To delete the DHCP configuration, clear the check box next to the IP address column in the lower part of the tab.

Click send to save the changes.

5.2 LTE3134: FDD-LTE 17 System Upgrade Benefits, functionality, system impact and reference data of the feature The LTE3134: FDD-LTE 17 System Upgrade feature supports a system upgrade for the following releases: • •

From FDD-LTE 16 to FDD-LTE 17 From FDD-LTE 16A to FDD-LTE 17

A system upgrade from FDD-LTE 16 release or FDD-LTE 16A release to FDD-LTE 17 release for Flexi Zone (FZ) stand-alone outdoor and indoor small cells and controller configuration is also supported. For AirScale, an upgrade from LTE 16A to LTE 17 is supported.

5.2.1 LTE3134 benefits The LTE3134: FDD-LTE 17 System Upgrade feature provides the option to upgrade the system in a single step.

DN09237915 Issue: 01A

© 2017 Nokia

161



5.2.2 LTE3134 functional description The system upgrade is possible in one step, and an installation of intermediate software version is not needed. The LTE3134: FDD-LTE 17 System Upgrade feature includes backward compatibility and enables an automatic fallback or rollback to the previous release that had been activated before the upgrade. The following network elements (NEs) are impacted: • • • • • • •

Flexi Multiradio BTS Flexi Zone (FZ) NetAct including the Optimizer, TraceViewer, and Northbound interfaces Operation and management server (OMS) Traffica Layer 3 Data Collector (L3DC) with its applications as layer 3 data analyzer Self-organizing network (SON) manager

The system upgrade is performed in a top-down approach, which starts with NetAct and ends when all the evolved Node Bs (eNBs) are upgraded. During the upgrade, the management and network elements should maintain compatibility with other management and network elements that are in the active release or in the previous release before the upgrade.

g

Note: The operator can perform the activation of the new software from NetAct or BTS Site Manager (BTS SM). The Traffica and L3DC support local software management.

g

Note: The upgrade of all eNBs in the network may take up to several days or even weeks, depending on the upgrade procedure followed by the operator. During this transition period NetAct and LTE OMS are able to manage eNBs of the former release (FDD-LTE 16 in this scenarion) and the new one (FDD-LTE 17) in parallel. Software upgrade from FDD-LTE 16 to FDD-LTE 17 The system upgrade supports the following software upgrades: • • • • •

NetAct 16.2 to NetAct 17.2 LOMS 16 to LOMS 17 Traffica 16 to Traffica 17 L3DC 16 to L3DC 17 eNB upgrades: – – –

FL 16 to FL 17 FLF 16 to FLF 17 FLC 16 to FLC 17

Software upgrade from FDD-LTE 16A to FDD-LTE 17 The system upgrade supports the following software upgrades: • • •

162

NetAct 16.8 to NetAct 17.2 LOMS 16A to LOMS 17 Traffica 16.5 to Traffica 17

© 2017 Nokia

DN09237915 Issue: 01A



L3DC 16.5 to L3DC 17 eNB upgrades:

• •

– – –

FL 16A to FL 17 FLF 16A to FLF 17 FLC 16A to FLC 17

Backward compatibility Backward compatibility means that interworking between the upgraded and the nonupgraded network elements is possible during the system upgrade. Because of the topdown approach, the following backward compatibilities are supported: NetAct 17.2 supports the OMS and eNB with FDD-LTE 16 and FDD-LTE 16A releases. LOMS 17 supports the eNB with FDD-LTE 16 and FDD-LTE 16A releases. Traffica 17 supports the L3DC and eNB with FDD-LTE 16A release. L3DC 17 supports the eNB with FDD-LTE 16 and FDD-LTE 16A releases.

• • • •

g

Note: The LTE 16 version of Traffica (16) must be upgraded to Traffica 16.5 before upgrading to Traffica 17.

g

Note: All hardware related outages on a network element must be resolved before that network element or subtending network element's managed by that network element can be upgraded. For example, any iOMS hardware issues should be resolved before upgrading that LTE OMS or any eNBs currently assigned to that LTE OMS. Data migration All operator-configured data is stored in the system. Configuration data created in the earlier release is automatically converted into a new format that is valid for the new release during the upgrade. The data includes the following: All configuration data of the Flexi Multiradio BTS, OMS, NetAct, L3DC, and Traffica Customized view in the BTS SM or NetAct user-specified accounts and passwords User-specified accounts and passwords

• • •

The following system data should be uploaded or backed up before the upgrade: Network security-related system data (such as certificates and keys) User security-related data (such as user accounts and passwords) Performance measurement (PM) data

• • •

g

Note: Failure to back up the data or upload it to NetAct might cause the data to be lost.

g

Note: Software backup only applies to OMS. The operation does not cause an outage, and it runs in the background.

g

Note: BTS SM is prepared to handle four network elements' releases. LTE 17 BTS SM must support FSMr2 (FDD-LTE 15A).

DN09237915 Issue: 01A

© 2017 Nokia

163



If there are used command lines or scripts, they must be backward compatible, or a converter must be available for the supported upgrade paths. The software converter is available in an online or offline mode. Software fallback Software fallback is an automatic activation of an earlier software version that is active before the software upgrade. Fallback is triggered when the eNB or OMS cannot activate its new software version or use a new database configuration version. After a successful fallback, the passive software build is active in all the hardware units. All of the components activate the stored configuration data without reverse migrating or converting to new configuration data.

g g g

Note: In case of minor failures, no software fallback is initiated, but the error information is indicated. The failures are logged in a non-volatile memory and include a detailed information about the reason for the failure. Note: In case of an inconsistent fallback, where the eNB does not locally store the complete fallback software for all the hardware units, a software download from NetAct is requested. Note: A software fallback causes an NE outage, and it causes the BTS to reset. The outage time is approximately the same as reboot duration. Software rollback Software rollback is a manually initiated software fallback, using the BTS SM or NetAct software management (SWM). The operator can trigger software rollback when key services are not successfully activated after the software upgrade. Any configuration updates done with the new software are lost as soon as software rollback is triggered. Software rollback is only guaranteed if the source software version has not been removed or overwritten in a non-volatile storage (NVS). Software rollback is done with the software stored in the passive file system and when no software download from the server is part of the operation. If the passive software has been overwritten with a different software version, a rollback to the former release is not possible.

g

Note: Software rollback to the stored software load restores the earlier configuration. If there has been a major network reconfiguration after the upgrade, such as reconfiguring the eNB from IPv4 to IPv6 or updating operator certificates, then network connectivity issues can occur after the rollback. Reconfigurations after the software upgrade must be evaluated before triggering software rollback to avoid service outage. Software rollback for a single eNB or for eNBs in bulk can be done using the NetAct SWM. For more information, see the Software Manager Help document under Network Administration in NetAct Operating Documentation. Software rollback for a single eNB can also be done using the Rollback to Passive SW function in the Update SW to BTS Site window on the BTS SM. If the operator selects a software version that is older than the current software version in the Update SW to BTS Site window on the BTS SM and clicks Update, a software downgrade takes place.

g

164

Note: Software downgrade must not be executed. A downgrade to an earlier software version is not guaranteed and might end up in an uncommissioned state of the eNB.

© 2017 Nokia

DN09237915 Issue: 01A



g

Note: A software rollback operation from NetAct might interrupt ongoing local operations triggered from BTS SM such as commissioning without a local user warning.

g

Note: A software rollback causes an NE outage, and it causes the BTS to reset. The outage time is approximately the same as reboot duration.

5.2.3 LTE3134 system impact LTE3134: FDD-LTE 17 System Upgrade impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features As specified in LTE2378: FSM D/E (FSMr2) Support after FDD-LTE 15A feature, the FSMr2 software is frozen on FDD-LTE 15A. The LTE-FDD 17 software packages may contain FDD-LTE 15A updates for FSMr2, but the FSMr2 will report its software version as FDD-LTE 15A. Note that this depends on the latest FDD-LTE 15A always being included in the LTE 17 eNB software build. This feature uses requirements specified in previous LTE software management and system upgrade features. The following upgrade requirements/features of earlier FDD releases are supported : FDD-LTE 16A LTE2633 FDD-LTE 16 LTE2341 FDD-LTE 15A LTE2049 RL70 LTE1854 RL60 LTE1560 RL50 LTE1368 RL40 LTE1078 RL30 LTE882 RL20 LTE185

• • • • • • • • •

g

Note: This feature utilizes both the OM_GEN_SFS_RNWINT and OM_GEN_SFS_SWMGMNT SFS use cases and functional requirements created or updated for LTE3134 as the use cases and functional requirements for the previous release LTE system upgrade features listed above. Impact on interfaces The LTE3134: FDD-LTE 17 System Upgrade feature has no impact on interfaces. Impact on network management tools The LTE3134: FDD-LTE 17 System Upgrade feature impacts system performance and capacity as follows: • •

DN09237915 Issue: 01A

The end user will experience a service degradation and partial service loss during the system upgrade. The downtime for the network entities is reduced to the activation of the new software during the system upgrade.

© 2017 Nokia

165



Impact on system performance and capacity The performance of the LTE 17 network elements during upgrade is expected to be the same as the LTE 16A network elements. The existing LTE eNB and LTE OMS upgraderelated performance requirements apply to the LTE 17 upgrade. The existing LTE eNB and LTE OMS upgrade-related capacity requirements apply to the LTE 17 upgrade.

5.2.4 LTE3134 reference data LTE3134: FDD-LTE 17 System Upgrade requirements and sales information Requirements Table 93


System release FDD-LTE 17

Flexi Multiradio BTS Not supported

Flexi Zone Controller FLC17

OMS

Flexi Multiradio 10 BTS FL17 UE

LTE OMS17


Flexi Zone Micro BTS FLF17

FLF17

NetAct NetAct17.2




Alarms There are no alarms related to the LTE3134: FDD-LTE 17 System Upgrade feature. Commands There are no commands related to the LTE3134: FDD-LTE 17 System Upgrade feature. Measurements and counters There are no measurements or counters related to the LTE3134: FDD-LTE 17 System Upgrade feature. Key performance indicators There are no key performance indicators related to the LTE3134: FDD-LTE 17 System Upgrade feature. Parameters There are no parameters related to the LTE3134: FDD-LTE 17 System Upgrade feature. Sales information Table 94



166

License control Not supported

© 2017 Nokia


DN09237915 Issue: 01A



5.2.5 Upgrading the LTE eNB to LTE 17 Purpose Follow this procedure to avoid losing non-network configuration data when upgraded LTE 17 eNBs are uploaded to Configurator. Before you start The operation is supported for macro eNBs from FDD-LTE16 or FDD-LTE16A to FDDLTE17. The operation is not supported for: • •

Flexi Zone Controller Flexi Zone Micro BTS (micro eNB).

Make sure that Intelligent Configuration Synchronization is disabled (recommended). Working sets are done for grouping the eNBs as the scope for upgrade operations. Procedure 1

In NetAct Start Page click on CM Operations Manager. Step result The CM Operations Manager window opens.

2

In the Tools menu choose Workflow Engine. Step result The Workflow Engine dialog opens.

3

From the Operation list drop-down list, select Upgrade - LTE BTS.

4

In the Working set select the working set or sets containing LTE 16/LTE 16A MRBTSs to be upgraded.

5

Run the Prepare for upgrade operation before the software upgrade to ensure that the parameters are up to date. Step result LTE 16 and LTE 16A non-network data is stored into data export files.

DN09237915 Issue: 01A

© 2017 Nokia

167


6


In the NetAct Start Page click on Software Manager. Step result The Software Manager application opens.

7

Using Software Manager, upgrade the LTE 17 software build for the eNBs. Note that you can use the same working set as the Configurator.

g

Note: BTS SM can also be used for the upgrade.

8

In the Workflow Engine, continue the workflow by selecting Upload configuration data.

9

Click the Start icon next to the operation. Click Start.

10 Update the Configurator non-network data to the LTE 17 MRBTSs by selecting Update non-network parameter data and clicking Start icon next to the operation. Click Start.

Result • • •

The eNB is upgraded to LTE 17 software version. The eNB configuration (according to the new information model) is synchronized to the Configurator configuration database. The non-network configuration is available in the Configurator.

5.2.6 Rolling back the upgrade Before you start • •

LTE 17 software upgrade has been completed for the eNB following the procedure described in Upgrading the LTE eNB to LTE 17. Intelligent Configuration Synchronization is disabled (recommended).

Procedure 1

In NetAct Start Page click on Software Manager. Step result The Software Manager application opens.

168

© 2017 Nokia

DN09237915 Issue: 01A


2

g


Using the Software Manager, roll back the LTE 17 software build for the eNB. For more details, see Software Manager Help. Note: BTS SM can also be used for the rollback procedure. Step result The software version of the eNB is rolled back to the one previously installed (FL16, FL 16A or other).

3

In NetAct Start Page click on CM Operations Manager. Step result The CM Operations Manager dialog opens.

4

In the Tools menu choose Workflow Engine. Step result The Workflow Engine dialog opens.

5

From the Operation list drop-down list, select Upgrade - LTE BTS.

6

Drag and drop the eNB to the MO(s) window.

7

In the Start column, click the Start icon next to Upload configuration data after rollback operation. Click Start. Step result LTE 16 or LTE 16A data is uploaded.

8

In the Start column, click the Start next to Update non-network parameter data after data rollback operation. Click Start. Step result LTE 16 or LTE 16A non-network data is restored.

Result • • •

DN09237915 Issue: 01A

The eNB is rolled back to LTE 16/LTE 16A software version. The eNB configuration is synchronized with the Configurator's configuration database. The non-network configuration in the Configurator has been restored to the earlier state.

© 2017 Nokia

169



For more information, see the Executing NetAct Configurator Workflows document.

5.3 LTE3296/SR001527: Harmonized Object Model for SRAN and LTE Benefits, functionality, system impact, reference data of the feature Introduction The LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature introduces a new object model for both products that harmonizes the approach to configuration and creates a more logical, expandable topology of Managed Object Classes (MOCs) that easily supports adding future technologies. The changes to the current object model reflect a new way of approaching configuration that separates configured hardware from detected hardware, that consolidates parameters according to their purpose, and distinguishes between common management parameters and Radio Access Technology (RAT)-specific ones..

5.3.1 LTE3296/SR001527 benefits The LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature provides the following benefits: • •

Reduced effort to configure and administrate a mixed technology network Less risk when upgrading a site to multi-RAT due to misconfiguration

5.3.2 LTE3296/SR001527 functional description The LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature alters the object model of both LTE and SRAN products to align them in one topology. There are some conceptual changes introduced to make the object model scalable and more useful to the operator, as well as simple relocations. The major changes can be summarized as follows: •

•

•

•

170

Configured hardware is separated from hardware detected at runtime. A new toplevel MOC named EQM holds the configuration of hardware specified by the operator, and a similar MOC named EQM_R holds the configuration of hardware detected by the eNB at runtime. The Distinguished Name (DN) of the object configuring that hardware in the EQM tree is mapped to the detected hardware in EQM_R. Hardware topology is now defined by a new set of objects in the EQM/EQM_R trees. Configured topology is now in the HWTOP tree, split into physical and logical links in CABLINK and LOGLINK objects, and similarly the detected hardware topology is stored in CABLINK_R and LOGLINK_R objects under HWTOP_R in EQM_R. Common management parameters are located in the MNL object tree on the top level. Actions such as SW reset or calibration and testing are located in this tree. The management subtree also holds the new CELLMAPPING tree to configure mapping between cells and physical resources, replacing the BTSSCL/LCELL object. FDD and TDD parameters are aligned into one common model, with technologyspecific parameters being split into new MOCs with the suffix _TDD or _FDD as appropriate.

© 2017 Nokia

DN09237915 Issue: 01A


•


For SRAN, the RAT-specific parameters will have their own top-level subtrees LNBTS, WNBTS and GNBTS for LTE, WCDMA and GSM respectively.

New MOC tree overview Figure 15

Top level objects in the hierarchy

Changes to hardware configuration and detection The LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature introduces a new way of presenting configured and detected hardware to the administrator. Configured hardware is maintained separately in the object hierarachy under the EQM object, and detected hardware is presented under the read-only EQM_R hierarchy. Detected hardware that matches configured hardware is linked via an ID in the relevant object under EQM_R.

DN09237915 Issue: 01A

© 2017 Nokia

171


Figure 16


The EQM and EQM_R object trees

For each MOC under the EQM subtree, there is a corresponding MOC with the suffix of _R in the EQM_R subtree. The two MOCs are related to each other by their names and also via the parameter configDN in the _R object. configDN contains the Distinguished Name (DN) of the MOC in EQM. For the DN format, please refer to the RAML2.1 Specification, section 2.1. It is possible that there are discrepancies between the two subtrees. Even in the normal case, the EQM_R tree contains more objects than the configured list because the BTS is able to provide more information to the operator without manual configurations. There are two cases where the discrepancies are reflected in the configDN and state attributes: 1. Hardware is installed but there is no configured EQM object. In this case, the _R object will be present with configDN set to NULL. This _R object will not be enabled until the corresponding EQM object is configured. 2. An object in EQM is configured but the hardware is not installed. In this case, the _R object will be present with configDN set to the configured object. The states of the _R object will reflect that it is not installed. There are significant changes in the hardware topology area. New objects have been introduced: CABLINK and LOGLINK. CABLINK represents the physical cable, LOGLINK represents a connection between two points, without explicitly defining the environment between them. Topology between System Modules and RF modules are defined as CABLINKs specified only by the Distinguished Names of the endpoints. For an antenna path specification, a full topology is required. These are the configurable objects and their usage for a macro BTS: • • •

172

EQM – The top object of the EQM tree. It must always be present. APEQM – Access point equipment subtree. This subtree consists of equipment that makes up an access point. For macro, there is only 1 instance of it. CABINET – At least one is needed to house the system and baseband modules.

© 2017 Nokia

DN09237915 Issue: 01A


•

• • •

•

•

• •


SMOD – System Module. The controller of the BTS containing the management interface towards NetAct. Depending on the hardware release, it may or may not contain baseband processing. There may also be multiple SMODs but only one will be the main controller. Additional SMODs are for expansion purposes. EAC_IN, EAC_OUT – these are optional environmental control for alarm inputs (EAC_IN) or relay control (EAC_OUT). They can also be present under an RMOD. BBMOD – Baseband Module. Baseband processing module. Additional modules can be added to a System module to expand the processing capacity. PASSDEV – a generic MOC for the operator to document equipment that cannot be detected by the BTS. It can be used for modeling passive ALD devices or simply a way for the operator to record inventory data of other passive devices (e.g. power supply, fan) for the purpose of keeping track of HW inventory. RMOD – Radio module. This can be an RF module that is part of the system module (as in small cell), locally connected to the System Module or remotely connected as a Remote RF Head (RRH). SMOD_EXT – a virtual object to represent a system module from a peer BTS. In RF sharing, the SMOD_EXT represents another BTS that shares resources of one or more radio modules. HWTOP – Hardware Topology top object. It must always be present. CABLINK, LOGLINK – Hardware Topology objects defining physical and logical connections between modules.

Common Management subtree MNL The MNL tree contains three objects: • • •

CMD - Commands, such as hardware reset or RET unit calibration, are activated here. NOTES - Contains NOTE objects that may be freely filled by the operator for any purpose. MNLENT - System module specific objects are placed under MNLENT.

The MNLENT (Management Layer Entity) object contains system module specific parameters and is placed under MNL with one instance for each entity. The related objects under MNLENT are as follows: • • • • • • •

•

DN09237915 Issue: 01A

BBADM - Baseband Administration. Contains BBPOOL objects. CAPADM - Capacity Administration. Capacity configuration and limitations are defined here. CELLMAPPING - Cell Mapping. This replaces the cell mapping list that was previously part of LNCEL. FMCADM - Fault Management Common Administration. Parameters related to fault management are moved here. FEATCADM - Feature Common Administration. Parameters to activate and administer specific features appear here. PMCADM - Performance and Monitoring Common Administration. SECADM - Security Common Administration. Security related parameters are found here, and additional security information detected by the BTS is available in the SECADM_R sub-object. SYNC - Synchronization. Time source and synchronization configuration is made here.

© 2017 Nokia

173


• •


TEST - Tests. Testing is activated here and the results returned as objects under the TEST object. TRBLCADM - Troubleshooting Common Administration. Contains troubleshooting parameters.

Figure 17

The MNL tree

Figure 18

The MNLENT subtree

The CELLMAPPING subtree contains the new scheme for mapping cells to antennas that replaces the previous one in BTSSCL/LCELL. The CELLMAPPING object contains a number of LCELL objects equivalent to the old LCELL object, but each new LCELL object contains a number of CHANNELGROUP objects that contain CHANNEL objects. The CHANNELGROUP and CHANNEL objects replace the legacy resourceList parameter in the old LCELL.

174

© 2017 Nokia

DN09237915 Issue: 01A



Each CHANNEL object is linked to an ANTL object in the EQM tree using the antlDN parameter, and it also contains a direction parameter to specify whether the channel is RX or TX. A TXRX antenna line is configured with two CHANNEL objects, one for each direction. As the ANTL is a child object of an RMOD, there is no need to specify the old rmodId or antId parameters. Unification of LNCEL for FDD and TDD technologies The LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature unifies the previously different hierarchies of the LNBTS/LNCEL tree into one form. The LNCEL object has a new parameter cellTechnology that may be set as FDD or TDD. TDD- and FDD-specific parameters in LNCEL are moved to technology-specific objects LNCEL_TDD and LNCEL_FDD respectively, which contain technology-specific objects for MPUCCH and APUCCH with the _TDD and _FDD suffix. LNCEL child objects belonging to one specific technology are configured only if that technology is specified by the cellTechnology parameter in the LNCEL parent, and objects common to both technologies are consistency-checked according to that same parameter. The LNBTS object has a similar controlling parameter named supportedCellTechnology that applies to the whole eNB, and again TDD- and FDD-specific parameters are moved to child objects named LNBTS_TDD and LNBTS_FDD respectively. Common child classes are aligned and consistency-checked according to that parameter, with the exception of MBSFNSYNCAREA and MBSFNSYNC which are split into technology-specific classes with the _TDD and _FDD suffix.

DN09237915 Issue: 01A

© 2017 Nokia

175


Figure 19

176


The LNBTS tree

© 2017 Nokia

DN09237915 Issue: 01A


Figure 20


The LNCEL tree

5.3.3 LTE3296/SR001527 system impact LTE3296/SR001527: Harmonized Object Model for SRAN and LTE impact on network management tools Interdependencies between features There are no interdependencies between the LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature and any other feature. Impact on interfaces The LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature has no impact on interfaces. Impact on network management tools The LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature impacts network management tools as follows: •

WebUI Element Manager –

The WebUI EM will display the new MOC tree in the parameter view

Impact on system performance and capacity

DN09237915 Issue: 01A

© 2017 Nokia

177



The LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature has no impact on system performance or capacity.

5.3.4 LTE3296/SR001527 reference data LTE3296/SR001527: Harmonized Object Model for SRAN and LTE requirements and sales information Software requirements Table 95

LTE3296/SR001527 software requirements

System Release LTE17

SBTS SBTS17

Flexi Multiradio BTS not supported Flexi Zone Controller FL17

BSC Support not required


RNC Support not required

Nokia AirScale BTS FL17

OMS

UE





NetAct 17.2

NetAct NetAct 17


MME support not required


Hardware requirements This feature has no hardware requirements There are no alarms related to the LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature. Faults and reported alarms There are no faults related to the LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature. Measurements and counters There are no measurements or counters related to the LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature. Key performance indicators There are no key performance indicators related to the LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature. Parameters There are no parameters related to the LTE3296/SR001527: Harmonized Object Model for SRAN and LTE feature. The full list of parameters that have been relocated or altered due to this feature will be available in a future delivery.

178

© 2017 Nokia

DN09237915 Issue: 01A




LTE3296/SR001527 sales information


License control


-


5.4 LTE3303: Enhanced VoLTE, CA, and RF Quality Monitoring The LTE3303: Enhanced VoLTE, CA, and RF Quality Monitoring feature introduces new counters and KPIs in the following areas: Voice over LTE (VoLTE) Carrier aggregation (CA) Radio frequency (RF) quality monitoring.

• • •

5.4.1 LTE3303 benefits The LTE3303: Enhanced VoLTE, CA, and RF Quality Monitoring feature enables the operator to monitor the LTE RAN network in more detail.

5.4.2 LTE3303 functional description The LTE3303: Enhanced VoLTE, CA, and RF Quality Monitoring feature introduces several new counters in a few categories. For more information, see the reference data section.

5.4.3 LTE3303 system impact The LTE3303: Enhanced VoLTE, CA, and RF Quality Monitoring feature has no impact on features, interfaces, network management tools, and system performance and capacity.

5.4.4 LTE3303 reference data Requirements Table 97 System release FDD-LTE17 Flexi Zone Controller FL17

DN09237915 Issue: 01A

LTE3303 hardware and software requirements Flexi Multiradio BTS not supported OMS support not required


Nokia AirScale BTS

FL17

FL17 UE


© 2017 Nokia

NetAct 17.2

Flexi Zone Micro BTS FL17 MME support not required

Flexi Zone Access Point FL17 SAE GW support not required

179



Alarms There are no alarms related to the LTE3303: Enhanced VoLTE, CA, and RF Quality Monitoring feature. Measurements and counters Table 98

E-RAB release due to inter-RAT handovers to UTRAN or GERAN counters introduced by LTE3303

Counter ID

Measurement

M8006C303

Total number of released E-RABs due to successful IRAT HO to UTRAN (ERAB_REL_SUCC_HO_UTRAN)

8006 - LTE EPS Bearer

M8006C304

Total number of released E-RABs due to successful IRAT HO to UTRAN QCI1 (ERAB_REL_SUCC_HO_UTRAN_QCI1)


M8006C305

Total number of released E-RABs due to successful IRAT HO to UTRAN QCI5 ( ERAB_REL_SUCC_HO_UTRAN_QCI5)


M8006C306

Total number of released E-RABs due to successful IRAT HO to GERAN (ERAB_REL_SUCC_HO_GERAN)


M8006C307

Total number of released E-RABs due to successful IRAT HO to GERAN QCI1 (ERAB_REL_SUCC_HO_GERAN_QCI1)


M8006C308

Total number of released E-RABs due to successful IRAT HO to GERAN QCI5 (ERAB_REL_SUCC_HO_GERAN_QCI5)


Table 99

E-RAB release due to S1 interface reasons counters introduced by LTE3303

Counter ID

180

Counter name

Counter name

Measurement

M8006C309

E-RAB releases due to eNB Initiated Global S1 Reset (ERAB_REL_ENB_INI_S1_GLOB_RESET)


M8006C310

E-RAB releases due to MME Initiated Global S1 Reset (ERAB_REL_MME_INI_S1_GLOB_RESET)


M8006C311

E-RAB releases due to eNB Initiated Partial S1 Reset (ERAB_REL_ENB_INI_S1_PART_RESET)


M8006C312

E-RAB releases due to MME Initiated Partial S1 Reset (ERAB_REL_MME_INI_S1_PART_RESET)


M8006C313

E-RAB releases due to S1 Outage (ERAB_REL_S1_OUTAGE)


M8006C314

E-RAB releases due to double S1 detected (ERAB_REL_DOUBLE_S1)


M8006C315

E-RAB releases due to double S1 detected QCI1 (ERAB_REL_DOUBLE_S1_QCI1)


© 2017 Nokia

DN09237915 Issue: 01A


Table 100

VoLTE PRB usage counter introduced by LTE3303

Counter ID

Counter name

Measurement

M8011C208

Number of UL PRBs Used for VoLTE (PRB_USED_UL_VOLTE)

8011 - LTE Cell Resource

M8011C215

Number of UL PRBs used for TTI Bundling (PRB_USED_UL_TTIB)


Table 101

HARQ BLER counters introduced by LTE3303

Counter ID

g


Counter name

Measurement

M8026C273

Total number of Initial HARQ Transmission for SRB in Downlink (TOT_N_INI_HARQ_TX_SRB_DL)

8026 - LTE QoS

M8026C274

Total number of Initial HARQ Transmission for nonGBR in Downlink (TOT_N_INI_HARQ_TX_NONGBR_DL)

8026 - LTE QoS

M8026C275

Total number of Failed Initial HARQ Transmission for SRB in Downlink (TOT_N_FAIL_INI_HARQ_TX_SRB_DL)

8026 - LTE QoS

M8026C276

Total number of Failed Initial HARQ Transmission for nonGBR in Downlink (TOT_N_F_INI_HARQ_TX_NONGBR_DL)

8026 - LTE QoS

M8026C277

Total number of NO Feedback for 8026 - LTE QoS Initial HARQ Transmission for SRB in Downlink (T_N_NO_FB_INI_HARQ_TX_SRB_DL)

M8026C278

Total number of NO Feedback for Initial HARQ Transmission for nonGBR in Downlink (T_N_NO_FB_INI_HARQ_TX_NGBR_DL)

8026 - LTE QoS

M8026C279

Total number of Initial HARQ Transmission for GBR excluding VoLTE in Downlink (TOT_N_INI_HARQ_TX_GBR_DL)

8026 - LTE QoS

M8026C280

Total number of Failed Initial HARQ Transmission for VoLTE in Downlink (TOT_N_F_INI_HARQ_TX_VOLTE_DL)

8026 - LTE QoS

M8026C281

Total number of Failed Initial HARQ Transmission for GBR excluding VoLTE in Downlink (TOT_N_F_INI_HARQ_TX_GBR_DL)

8026 - LTE QoS

M8026C282

Total number of NO Feedback for Initial HARQ Transmission for VoLTE in Downlink (T_N_NO_FB_INI_HARQ_TX_VOLTE_DL)

8026 - LTE QoS

M8026C283

Total number of NO Feedback for Initial HARQ Transmission for GBR excluding VoLTE in Downlink (T_N_NO_FB_INI_HARQ_TX_GBR_DL)

8026 - LTE QoS

Note: The following counters are available in the LTE17 software release, however, they will not be verified untill the LTE17 SP software release.

DN09237915 Issue: 01A

© 2017 Nokia

181


Table 102


UE context release counters introduced by LTE3303

Counter ID

g

eNB initiated UE Context releases with radio network layer cause "Inter-RAT redirection" due to coverage reasons (UE_CTX_REL_ENB_RNL_IRAT_RED_CO)

M8013C77

eNB initiated UE Context releases due 8013 - LTE UE to Global S1 Reset State (UE_CTX_REL_ENB_GLOB_S1_RESET)

M8013C78

eNB initiated UE Context releases due 8013 - LTE UE to Partial S1 Reset State (UE_CTX_REL_ENB_PART_S1_RESET)

M8013C79

eNB initiated UE Context releases due 8013 - LTE UE to S1 Outage State (UE_CTX_REL_ENB_S1_OUTAGE)

M8013C80

MME initiated UE Context releases due 8013 - LTE UE to Global S1 Reset State (UE_CTX_REL_MME_GLOB_S1_RESET)

M8013C81

MME initiated UE Context releases due 8013 - LTE UE to Partial S1 Reset State (UE_CTX_REL_MME_PART_S1_RESET)

M8013C82

MME Initiated UE Context releases due 8013 - LTE UE to detected double S1 State (UE_CTX_REL_DOUBLE_S1)

8013 - LTE UE State

Note: The following counters are available in the LTE17 software release, however, they will not be verified untill the LTE17 SP software release. VoLTE TTI bundling counters introduced by LTE3303

Counter ID

Counter name

Measurement

M8011C209

Number of TTI Bundling Switch on attempts (TTI_BUNDLING_SWITCH_ON_ATTS)


M8011C210

Number of TTI Bundling Switch on successes (TTI_BUNDLING_SWITCH_ON_SUCCS)


M8011C211

Number of TTI Bundling Switch off 8011 - LTE Cell attempts (TTI_BUNDLING_SWITCH_OFF_ATTS) Resource

M8011C212

Number of TTI Bundling Switch off successes (TTI_BUNDLING_SWITCH_OFF_SUCCS)


Note: The following counters are available in the LTE17 software release, however, they will not be verified untill the LTE17 SP software release. Table 104

Carrier aggregation (CA) downlink deconfiguration counters introduced by LTE3303

Counter ID M8011C213

182

Measurement

M8013C76

Table 103

g

Counter name

Counter name

Measurement

Downlink CA Deconfiguration Attempts (DL_CA_DECONFIG_ATT)

© 2017 Nokia


DN09237915 Issue: 01A


Table 104


Carrier aggregation (CA) downlink deconfiguration counters introduced by LTE3303 (Cont.)

Counter ID M8011C214

Table 105

Counter name

Measurement

Downlink CA Deconfiguration Successes 8011 - LTE Cell (DL_CA_DECONFIG_SUCC) Resource

PMQAP profile counters introduced by LTE3303

Counter ID

Counter name

Measurement

M8048C9

E-RABs attempted to release due to outgoing Intra LTE Handover (ERAB_REL_INTRA_LTE_HO_ATT_PR)

8048 - LTE ERAB Statistics per PMQAP Profile

M8048C10

E-RABs released due to successful outgoing Intra LTE Handover (ERAB_REL_INTRA_LTE_HO_SUCC_PR)


M8048C8

E-RABs All Abnormal releases per Profile (ERAB_REL_ALL_ABNORMAL_PROFILE)


M8048C3

E-RABs Abnormal releases per Profile (ERAB_REL_ABNORMAL_ACT_PROFILE)


Parameters There are no parameterss related to the LTE3303: Enhanced VoLTE, CA, and RF Quality Monitoring feature. Sales information Table 106



DN09237915 Issue: 01A

License control -

© 2017 Nokia


183

Descriptions of BTS site solution features


6 Descriptions of BTS site solution features 6.1 LTE2495: Plug-in Radio SW Interface for Nokia CPRI Benefits, functionality, system impact, reference data of the feature The LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature enables new RFM/RRH HW to be launched without delays caused by waiting for the main SW release upgrade.

6.1.1 LTE2495 benefits The LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature enables to introduce new RFM/RRH HW variants equipped with Nokia CPRI interface without waiting for new SW releases.

6.1.2 LTE2495 functional description Without the LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature, new RFM/RRH HW variant requires the deployment of a new SW release in the Mobile Operator Network, because all RFM/RRH unit information and parameters are delivered together with the main SW release packet in the System Module. This process is called FULL DELIVERY MODE. This LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature allows the user to connect new RFM/RRH HW variant (equipped with Nokia CPRI interface) without the requirement of upgrading the main SW release in the Mobile Operator Network. This process is called FAST DELIVERY MODE. It is at Nokia’s discretion to decide which new RFM/RRH HW variant can support FAST DELIVERY MODE. Please refer to the figures below with the comparision of two cases: 1. FULL DELIVERY MODE without the LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature 2. FAST DELIVERY MODE with the LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature

184

© 2017 Nokia

DN09237915 Issue: 01A


Figure 21


FULL DELIVERY MODE without the LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature ThegapbetweenNewRadioModulevariant availabilityanddeploymentofRelease(n+1) intheMobileOperatorNetwork

MobileOperator perspective

InternalNokia's perspective

Nokia'sinternalprocess todevelopRelease(n+1) NewRadioModulevariant includedintheRelease(n+1) FULLDELIVERYMODE

Nokia'sinternalprocesstodevelop newRadioModulevariant

P8 Release(n) Example:RL16

Figure 22

Release(n+1)deployedin theMobileOperatorNetwork

Release(n)deployedintheMobileOperatorNetwork

Nokia'sinternalprocess todevelopRelease(n)

P8N+1Release Release(n+1) Example:RL16A

NewRadio Modulevariant isready

Time

FAST DELIVERY MODE with the LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature MobileOperatorcanuseNewRadioModule variantinitsnetworkwithRelease(n)

MobileOperator perspective

NewRadioModule variantcanbeusedwith Release(n)alreadydeployed intheMobileOperatorNetwork FASTDELIVERYMODE

Nokia'sinternalprocesstodevelop newRadioModulevariant

P8 Release(n) Example:RL16

NewRadio Modulevariant isready

MobileOperatorcanuseNew RadioModulevariantinits networkwithRelease(n+1)

Release(n+1)deployedin theMobileOperatorNetwork

Release(n)deployedintheMobileOperatorNetwork

Nokia'sinternalprocess todevelopRelease(n)

InternalNokia's perspective

MobileOperatorcanuseNew RadioModulevariantinits networkwithRelease(n+1)

Nokia'sinternalprocess todevelopRelease(n+1) NewRadioModulevariant includedintheRelease(n+1) FULLDELIVERYMODE

N+1Release

P8 Release(n+1) Example:RL16A

Time

6.1.3 LTE2495 system impact LTE2495: Plug-in Radio SW Interface for Nokia CPRI impact on features and network management tools Interdependencies between features The LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature impacts RF/RRH HW variant equipped with Nokia CPRI interface features deployed in FAST DELIVERY MODE.

g

Note: CPRI interface types other than Nokia CPRI are not supported with LTE2495: Plug-in Radio SW Interface for Nokia CPRI (e.g. CPRI-A radios are not supported with LTE2495: Plug-in Radio SW Interface for Nokia CPRI). Impact on interfaces

DN09237915 Issue: 01A

© 2017 Nokia

185



The LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature has no impact on interfaces. Impact on network management tools The NetAct and BTS Site Manager have to be updated with the plug-in module. Impact on system performance and capacity The LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature has no impact on system performance or capacity.

6.1.4 LTE2495 reference data LTE2495: Plug-in Radio SW Interface for Nokia CPRI requirements and sales information Requirements Table 107 System release FDD-LTE 17


Flexi Zone Controller Support not required


Nokia AirScale BTS

FL17

FL17

OMS

UE

LTE OMS17




Not supported

Not supported

MME

SAE GW

NetAct NetAct 17.2



There are no alarms, measurements and counters, key performance indicators, parameters related to the LTE2495: Plug-in Radio SW Interface for Nokia CPRI feature. Sales information Table 108



License control -


6.2 LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W Benefits, functionality, system impact, reference data of the feature The LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W feature introduces the Flexi Multiradio RF Module (FRGX) for 3GPP 2100 MHz band 1 (uplink: 1920 - 1980 MHz, downlink: 2110 - 2170 MHz). FRGX has three power amplifiers enabling it to support one, two or three sectors with an output power of up to 80 Watts xTX MIMO at the BTS antenna connectors.

186

© 2017 Nokia

DN09237915 Issue: 01A



6.2.1 LTE2769 benefits The LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W feature provides the following benefits: • • •

Two RF Modules are able to support three sectors with full 2100 MHz RF spectrum utilization for WCDMA and LTE mode. Flexible installation options. FRGX is designed to be mounted onto a wall or a pole. IP65 environmental protection class.

6.2.2 LTE2769 functional description The main features of the FRGX are as follows: • • • • •

• • • •

2100 MHz 3GPP band 1 support 60 MHz instantaneous bandwidth 8 W, 10 W, 15 W, 20 W, 30 W, 40 W, 60 W and 80 W power level support 5 MHz, 10 MHz, 15 MHz and 20 MHz carrier bandwidth support Maximum eight WCDMA/LTE carriers per antenna connector with a maximum occupied bandwidth of 40 MHz multiple carriers with a maximum instantaneous bandwidth of 60 MHz in uplink and downlink LTE-LTE and LTE-WCDMA RF sharing support Forced cooling by the integrated fans 25 l volume 25 kg weight

The FRGX supports the following modulation schemes: • •

QAM64 (DL/UL) QAM256 (DL/UL)

The FRGX can be installed: • • • • •

on a pole. on a wall. on a floor. on top of another module. inside of a 19-inch rack or a cabinet.

For more information on FRGX, see the Flexi Multiradio BTS RF Module and Remote Radio Head Description document. For all supported configurations including those for FRGX, see the Creating LTE Configurations document. For implementation and configurations for RF sharing, see the Flexi Multiradio BTS RF Sharing Released Configurations document.

DN09237915 Issue: 01A

© 2017 Nokia

187



6.2.3 LTE2769 system impact LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be activated before activating the LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W feature: • • • •

LTE115: Cell Bandwidth - 5 MHz for the support of the 5 MHz carriers LTE114: Cell Bandwidth - 10 MHz for the support of the 10 MHz carriers LTE113: Cell Bandwidth - 15 MHz for the support of the 15 MHz carriers LTE112: Cell Bandwidth - 20 MHz for the support of the 20 MHz carriers

The LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W feature is impacted by the following features: •

• •

•

LTE614: Distributed Site With this feature FRGX can be used in distributed sites with up to 23 km fiber length to the system module. LTE977: RF chaining With this feature FRGX supports chains of up to 3 radio units. LTE1103: Load based Power Saving for multi-layer networks or LTE1203: Load based Power Saving mode with Tx power reduction or path switching off One of these features must be enabled to use the PA shutdown feature. LTE1891: eNode B power saving - Micro DTX This feature must be enabled to use Micro DTX extension.

Impact on interfaces The LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W feature has no impact on interfaces. Impact on network management tools The LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W feature has no impact on network management tools. Impact on system performance and capacity New configurations are available.

6.2.4 LTE2769 reference data LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W requirements, alarms and faults, measurements and counters, KPIs, parameters, and sales information Requirements

188

© 2017 Nokia

DN09237915 Issue: 01A


Table 109 System release FDD-LTE 17

LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W hardware and software requirements Flexi Multiradio BTS Not supported

Flexi Zone Controller Support not required



Nokia AirScale BTS

FL17

FL17

OMS

UE





Not supported

Not supported

MME

SAE GW

NetAct Support not required



There are no alarms, measurements and counters, key performance indicators, parameters related to the LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W feature. Sales information Table 110

LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W sales information


License control


-


6.3 LTE3133: FRCI Flexi RRH 2T2R 875 120 W Benefits, functionality, system impact, reference data, instructions of the feature The LTE3133: FRCI Flexi RRH 2T2R 875 120 W feature introduces Flexi Multiradio Remote Radio Head (RRH) FRCI for the Indian market with 2TX MIMO for 3GPP FDD Band 5 (uplink: 824 - 843.2 MHz, downlink: 869 - 888.4 MHz). FRCI is a 2-pipe RRH optimized for distributed macro BTS installations.

6.3.1 LTE3133 benefits The LTE3133:FRCI Flexi RRH 2T2R 875 120 W feature provides the following benefits: Two Power Amplifiers enable FRCI to support one sector with up to 2X60 W 2TX MIMO output power at the BTS antenna connector. Support for book mount installation.

• •

6.3.2 LTE3133 functional description Functional specification Table 111

FRCI functional specification Property

Value

Output power

2x60 W

MIMO

2TX

DN09237915 Issue: 01A

© 2017 Nokia

189


Table 111


FRCI functional specification (Cont.) Property

Value

Outdoor installation

Yes

SW supported technologies

FDD-LTE

TX frequency range

869 MHz – 888.4 MHz

RX frequency range

824 MHz – 843.4 MHz

DL instantaneous bandwidth

19.4 MHz

UL instantaneous bandwidth

19.4 MHz

DL filter bandwidth

19.4 MHz

UL filter bandwidth

19.4 MHz

Modulation schemes

QAM64 (DL), QAM64 (UL), QAM256 (DL)

Supported carrier bandwidths

5 MHz, 10 MHz, 15 MHz

Supported power levels

8, 10, 15, 20, 30, 40, 60 W

The FRCI RRH can use max. two LTE carriers per pipe. The FRCI RRH has the volume of 26.6 L. It weighs 23 kg without the cover and brackets. The environmental protection class is IP65. For more information, see Flexi Multiradio BTS RF Module and Remote Radio Head Description. External interfaces FRCI has the following external interfaces: • • • • • •

2 TX/RX ports with 4.3-10 connector 2 pcs of 6 Gbps OBSAI optical interfaces One DC in connector One AISG2.0 Antenna tilt support with external connector (RS485) Compatible with optional FPAD power supply when needed for AC solutions Up to 4 external alarms with the USB connector

Environmental operating conditions The FRCI Flexi RRH has the option of convectional cooling. General environmental operating conditions are as follows: -35°C to +55°C with -40°C cold start (with 70% load, no solar load & 3m/s wind). Mounting options The following are the supported mounting options for FRCI RRH: • • • •

190

Pole mounting Wall mounting Compatible to RAS mounting Book mounting

© 2017 Nokia

DN09237915 Issue: 01A



Supported Configurations For single carrier LTE: all released BTS configurations valid for RRH 2Tx2Rx RF units. For multi carrier LTE: released LTE BTS configurations supporting dual carrier and multicarrier configurations as well as inter eNB RF sharing configuration.

6.3.3 LTE3133 system impact LTE3133: FRCI Flexi RRH 2T2R 875 120 W impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be activated before activating the LTE3133: FRCI Flexi RRH 2T2R 875 120 W feature: • • • •

LTE117 needs to be enabled to use LTE 1.4MHz carriers LTE116 needs to be enabled to use LTE 3MHz carriers LTE115 needs to be enabled to use LTE 5MHz carriers LTE114 needs to be enabled to use LTE 10MHz carriers

The LTE3133: FRCI Flexi RRH 2T2R 875 120 W feature is impacted by the following features: •

• • •

•

•

• •

LTE614 With this feature the FRCI can be used in distributed sites with up to 23 km fiber length to the system module. LTE977 With this feature the FRCI supports chains of up to 4 radio units. LTE3096 With this feature the RAS installation options are defined. LTE1103 This feature needs to be enabled to use Load-based Power Saving for multi-layer networks. LTE1203 This feature needs to be enabled to use Load-based Power Saving with Tx path switching off. LTE2508 This feature needs to be enabled to use BTS Embedded Power Meter for Energy Efficiency Monitoring. To enable full output power, 4 power licenses per TX pipe are required. Following RF-sniffing features can be used with FRCI: – –

LTE1434:Flexi Multiradio BTS antenna Rx RF-sniffing LTE2556:Flexi Multiradio BTS Rx-Sniffing enhancements

Impact on interfaces The LTE3133: FRCI Flexi RRH 2T2R 875 120 W feature has no impact on interfaces. Impact on network management tools

DN09237915 Issue: 01A

© 2017 Nokia

191



The LTE3133: FRCI Flexi RRH 2T2R 875 120 W feature has no impact on network management tools. Impact on system performance and capacity New configurations are available.

6.3.4 LTE3133 reference data LTE3133: FRCI Flexi RRH 2T2R 875 120W requirements, alarms and faults, measurements and counters, KPIs, parameters, and sales information Requirements Table 112 System release FDD-LTE 17




Nokia AirScale BTS

FL17

FL17

OMS

UE





Not supported

Not supported

MME

SAE GW

NetAct NetAct 17.2



Alarms There are no alarms related to the LTE3133: FRCI Flexi RRH 2T2R 875 120W feature. BTS faults and reported alarms There are no faults related to the LTE3133: FRCI Flexi RRH 2T2R 875 120W feature. Measurements and counters There are no measurements or counters related to the LTE3133: FRCI Flexi RRH 2T2R 875 120W feature. Key performance indicators There are no key performance indicators related to the LTE3133: FRCI Flexi RRH 2T2R 875 120W feature. Parameters There are no parameters related to the LTE3133: FRCI Flexi RRH 2T2R 875 120W feature. Sales information Table 113



192

License control -

© 2017 Nokia


DN09237915 Issue: 01A



6.4 Interdependencies between CPRI-A features and other features Information on features related to CPRI-A features, features that require activation before using CPRI-A features, and features not supported with CPRI-A features Related documentation Technical descriptions of CPRI-A RFMs can be found in the following path: LTE17 Operating documentation -> LTE BTS and OMS Descriptions -> CPRI-A Installation instructions for CPRI-A RFMs can be found under the following path: LTE17 Operating Documentation -> Install and Commission -> CPRI-A For information about compatibility of CPRI-A RFMs with Nokia BTS, see LTE/EPC RAN Compatibility at: LTE17 Operating Documentation -> Reference -> Compatability For all supported configurations including CPRI-A RFMs, see: Creating LTE Configurations located at LTE17 Operating Documentation -> Install and Commission Creating Nokia AirScale BTS FDD-LTE Configurations located at LTE17 Operating Documentation -> Install and Commission LTE Base Stations Supported Configurations located at LTE17 Operating Documentation -> Integrate and Configure

• • •

CPRI-A feature list The CPRI-A features are: LTE3307: UHIE B66a RRH4X45 CPRI-A RRH 4-Pipe 1.7/2.1 160 W LTE3308: UHFE AA B25 A + 700/900 P CPRI-A Active Antenna 2-Pipe 1900 80 W LTE3309: UHCB RRH2x60-850 CPRI-A RRH 2-Pipe 850 80 W LTE3350: UHFF RRH2x60-1900 CPRI-A RRH 2-Pipe 1900 120 W LTE3409: UHIF 9768 MRO B4 1 W CPRI-A MRO RRH 2-Pipe 1700/2100 LTE3410: UHIG 9768 cMRO B4/66 5 W CPRI-A MRO RRH 2-Pipe 1700/2100 LTE3413: UHBF 9768 MRO B13 1 W CPRI-A MRO RRH 2-Pipe 700

• • • • • • •

Interdependencies between CPRI-A features and other features This table expresses the allowed and disallowed feature interactions of CPRI-A features with several pertinent feature groups. Each of these feature groups is represented by one column. The specific features in each of the feature groups are listed in Features with interdependencies with CPRI-A features. Table 114

Interdependencies between CPRI-A features and other features

CPRI-A features LTE3307 (UHIE)

DN09237915 Issue: 01A

PA shutdown features S

Carrier bandwidth features S

© 2017 Nokia

RF-sniffing features NS

Supercell features

-

193


Table 114


Interdependencies between CPRI-A features and other features (Cont.)

CPRI-A features

PA shutdown features

Carrier bandwidth features

RF-sniffing features

Supercell features

LTE3308 (UHFE)

S

S

NS

-

LTE3309 (UHCB)

S

S

NS

-

LTE3350 (UHFF)

S

S

NS

-

LTE3409 (UHIF)

S

S

NS

-

LTE3410 (UHIG)

S

S

NS

-

LTE3413 (UHBF)

S

S

NS

-

S => Supported NS => Not Supported - => not determined at this time

Features with interdependencies with CPRI-A features PA shutdown features The PA (power amplifier) shutdown capability requires one of these features: • •

LTE1103: Load based Power Saving for multi-layer networks LTE1203: Load based Power Saving with Tx path switching off

Carrier bandwidth features To use LTE 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz carriers, one or more of the following features needs to be enabled: • • • • •

LTE116: Cell Bandwidth - 3 MHz LTE115: Cell Bandwidth - 5 MHz LTE114: Cell Bandwidth - 10 MHz LTE113: Cell Bandwidth - 15 MHz LTE112: Cell Bandwidth - 20 MHz

For details about the supported bandwidth configurations for all RFMs including CPRI-A RFMs, see LTE Base Stations Supported Configurations located at LTE17 Operating Documentation -> Integrate and Configure RF-sniffing features All available CPRI-A features do not support the following features: • • •

194

LTE1434: Flexi Multiradio BTS antenna Rx RF-sniffing LTE1634: Remote RF-diagnostics for Flexi Multiradio BTS LTE2556: Flexi Multiradio BTS Rx-Sniffing enhancements

© 2017 Nokia

DN09237915 Issue: 01A



Supercell features The supercell features are: • • • •

DN09237915 Issue: 01A

LTE1542: FDD Supercell LTE1709: Liquid Cell LTE2091: FDD SuperCell extension LTE2445: Combined Supercell

© 2017 Nokia

195

Feature Descriptions FDD-LTE

Recommend Documents