Nokia LTE 17A Features Description and Instructions

LTE Radio Access, Rel. LTE 17A, Operating Documentation, Pre-release2, Issue 01 LTE17A Radio Resource Management and Telecom Features Issue 01

LTE17A Radio Resource Management and Telecom Features

The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective company within Nokia Group of Companies with whom you have entered into the Agreement (as defined below). This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia. If You have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof. The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia welcomes your comments as part of the process of continuous development and improvement of the documentation. This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such information and statements without notice. Nokia has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia will correct errors that You identify in this document. Nokia's total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product will be uninterrupted or error-free. NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY AVAILABILITY,, ACCURACY, ACCURACY, RELIABILITY, RELIABILITY, TITLE, NON-INFRINGEMENT 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

Issue: 01


Table of Contents This document has 179 pages 1 1.1

LTE2337: FDD-TDD Downlink Carrie Carrierr Aggregation 3CC – 2 FDD and 1 TDD ...................................................................................1 ...................................................................................11 LTE2337 benefits..........................................................................11

1.2 1.2 1.3 1.4

LTE TE23 2337 37 fu func ncti tion onal al de desc scri ript ptio ion. n... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... ..... ..... .... .... .... 11 LTE2337 system impact............................................................... impact...............................................................12 12 LTE2337 reference data............................................................... data...............................................................14 14

2

LTE2410: Roaming and Access Res Restrictions trictions Removal for CSFB Emergency Calls..........................................................................16 Calls..........................................................................16 LTE TE24 2410 10 be bene nefi fits ts.. .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... .. 16 LTE2410 functional description.................................................... description....................................................16 16 LTE2410 system impact............................................................... impact...............................................................17 17 LTE2410 reference data............................................................... data...............................................................17 17

2.1 2.1 2.2 2.3 2.4 3 3.1 3.1 3.2 3. 2 3.3 3.4 3.5 3.6 3. 6

LTE2532: TDD Downlink Carrier Agg Aggregation regation with 4 Layers MIMO ..................................................................................................... 19 .....................................................................................................19 LTE TE25 2532 32 be bene nefi fits ts.. .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... .. 19 LTE TE25 2532 32 fu func ncti tion onal al de desc scri ript ptio ion. n... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... ..... ..... .... .... .... 19 LTE2532 system impact............................................................... impact...............................................................20 20 LTE2532 reference data............................................................... data...............................................................21 21 Activating LTE2532...................................................................... 23 23 Deac De acti tiva vati ting ng LTE TE25 2532 32.. .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... 25

4 4.1 4.2 4.3 4. 3 4.4 4. 4 4.5 4. 5 4.6 4. 6

LTE TE26 2623 23:: FD FDDD-TD TDD D Do Down wnli link nk Ca Carr rrie ierr Ag Aggr greg egat atio ion n 4C 4CC. C... .... .... .... .... ....2 ..28 8 LTE2623 benefits......................................................................... 28 28 LTE2623 functional description.................................................... description....................................................28 28 LTE TE26 2623 23 sy syst stem em im impa pact ct.. .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... ....29 ..29 LTE TE26 2623 23 re refe fere renc nce e da data ta... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... ....30 ..30 Acti Ac tiva vati ting ng an and d co conf nfig igur urin ing g LTE TE26 2623 23.. ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... ...32 .32 Deac De acti tiva vati ting ng LTE TE26 2623 23.. .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... 36

5 5.1 5. 1 5.2 5. 2 5.3 5. 3

LTE TE29 2912 12:: TD TD-L -LTE TE Ba Base seba band nd Po Pool olin ing. g.... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... 38 LTE TE29 2912 12 be bene nefi fits ts.. .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... .. 38 LTE TE29 2912 12 fu func ncti tion onal al de desc scri ript ptio ion. n... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... ..... ..... .... .... .... 38 LTE TE29 2912 12 sy syst stem em im impa pact ct.. .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... ....40 ..40

5.4 5.4 5.5 5. 5 5.6 5. 6

LTE TE29 2912 12 re refe fere renc nce e da data ta... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... ....44 ..44 Acti Ac tiva vati ting ng LTE TE29 2912 12.. ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... 47 Deac De acti tiva vati ting ng LTE TE29 2912 12.. .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... 49

6

LTE TE30 301 11: Fl Flex exii Zo Zone ne In Intr traa-FZ FZM M an and d In Intr traa-FZ FZAP AP up upli link nk 2C 2CC C ca carr rrie ier r aggregation.................................................................................. aggrega tion.................................................................................. 51 LTE TE301 3011 1 be benef nefits its... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... .....51 ..51 LTE TE30 301 11 fu func ncti tion onal al de desc scri ript ptio ion. n... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... 51 LTE TE30 301 11 sy syst stem em im impa pact ct.. ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .. 52

6.1 6.2 6. 2 6.3 6. 3

Issue: 01

© 2017 Nokia

3


6.4 6.5 6.5.1 6.5.2 6.6 6.6.1 6.6.2 7 7.1 7.2 7.3 7.4 7.5 7.6 8 8.1 8.2 8.3 8.4 9

4

LTE3011 reference data...............................................................53 Activating and configuring LTE3011.............................................54 FDD..............................................................................................54 TDD..............................................................................................56 Deactivating LTE3011.................................................................. 58 FDD..............................................................................................58 TDD..............................................................................................60 LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE .... 62 LTE3020 benefits......................................................................... 62 LTE3020 functional description....................................................62 LTE3020 system impact...............................................................63 LTE3020 reference data...............................................................64 Activating LTE3020...................................................................... 67 Deactivating LTE3020..................................................................69 LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II.........................................................................71 LTE3049 benefits......................................................................... 71 LTE3049 functional description.................................................... 71 LTE3049 system impact...............................................................72 LTE3049 reference data...............................................................72

9.1 9.2 9.3

LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) ........................................................................................74 LTE3056 benefits......................................................................... 74 LTE3056 functional description....................................................74 LTE3056 system impact...............................................................76

9.4 9.5 9.6

LTE3056 reference data...............................................................76 Activating and configuring LTE3056.............................................79 Deactivating LTE3056.................................................................. 81

10 10.1 10.2 10.3 10.4

LTE3071: NB-IoT Inband..............................................................83 LTE3071 benefits......................................................................... 83 LTE3071: NB-IoT Inband functional description...........................83 LTE3071 system impact...............................................................86 LTE3071 reference data...............................................................92

10.5 10.6

Activating and configuring LTE3071...........................................100 Deactivating LTE3071................................................................ 103

11 11.1

LTE3265: GNSS Outage Handling for OTDOA..........................106 LTE3265 benefits....................................................................... 106

11.2 11.3

LTE3265 functional description.................................................. 106 LTE3265 system impact............................................................. 107

11.4 11.5 11.6

LTE3265 reference data.............................................................108 Activating LTE3265..................................................................... 111 Deactivating LTE3265.................................................................111

© 2017 Nokia

Issue: 01


12

Issue: 01

12.1

LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling... 112 LTE3509 benefits........................................................................112

12.2 12.3 12.4 12.5 12.6

LTE3509 functional description.................................................. 112 LTE3509 system impact.............................................................112 LTE3509 reference data.............................................................114 Activating and configuring LTE3509...........................................115 Deactivating LTE3509................................................................ 119

13 13.1 13.2 13.3 13.4

LTE3582: LTE-M Enhancements I ............................................ 122 LTE3582 benefits....................................................................... 122 LTE3582 functional description..................................................123 LTE3582 system impact.............................................................125 LTE3582 reference data.............................................................127

14 14.1 14.2 14.3 14.4 14.5 14.6

LTE3586: High Power UE Specific Mobility Thresholds.............131 LTE3586 benefits....................................................................... 131 LTE3586 functional description.................................................. 131 LTE3586 system impact.............................................................133 LTE3586 reference data.............................................................134 Activating LTE3586.................................................................... 136 Deactivating LTE3586................................................................ 138

15 15.1 15.2 15.3 15.4

LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND... 140 LTE3612 benefits....................................................................... 140 LTE3612 functional description.................................................. 140 LTE3612 system impact.............................................................142 LTE3612 reference data.............................................................143

16 16.1 16.2 16.3 16.4

LTE3668: NB-IoT: Coverage enhancements..............................144 LTE3668 benefits....................................................................... 144 LTE3668 functional description..................................................144 LTE3668 system impact.............................................................146 LTE3668 reference data.............................................................146

17 17.1 17.2 17.3 17.4

LTE3669: NB-IoT: Paging support..............................................159 LTE3669 benefits....................................................................... 159 LTE3669 functional description.................................................. 159 LTE3669 system impact.............................................................164 LTE3669 reference data.............................................................167

18 18.1 18.2 18.3

LTE3688: Additional FDD-TDD Carrier Aggregation Band Combinations - V........................................................................170 LTE3688 benefits....................................................................... 170 LTE3688 functional description.................................................. 170 LTE3688 system impact.............................................................170

18.4

LTE3688 reference data.............................................................171

© 2017 Nokia

5


19 19.1 19.2 19.3 19.4

6

LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier..173 LTE3819 benefits....................................................................... 173 LTE3819 functional description.................................................. 173 LTE3819 system impact............................................................. 176 LTE3819 reference data.............................................................177

© 2017 Nokia

Issue: 01


List of Figures

Issue: 01

Figure 1

FDD and TDD CA in LTE2337............................................................11

Figure 2

The peak rate can reach up to 410 Mbps...........................................13

Figure 3

2CC FDD + 2CC TDD combination with LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC ................................................................... 28

Figure 4

An example of Nokia AirScale BTS resource allocation (blue lines): LTE2912 not enabled (top), LTE2912 enabled (bottom).....................40

Figure 5

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

Figure 6

Types of NB-IoT..................................................................................84

Figure 7

LTE-M in-band deployment.............................................................. 124

Figure 8

High Power UE extended coverage................................................. 132

Figure 9

Complete view of Nokia AirScale System Module............................141

Figure 10

LTE3612 configuration......................................................................141

Figure 11

Types of NB-IoT................................................................................144

Figure 12

LTE3668 increased coverage concept............................................. 145

Figure 13

Paging procedure.............................................................................160

Figure 14

Transport Block Size (TBS) for 1-10 Resource Units (RU) for NPDSCH RRC Paging-NB...............................................................161

Figure 15

RRC paging not overlapping scenario..............................................161

Figure 16

RRC paging overlapping scenario....................................................162

Figure 17

Basic rule of setting parameter pagingNbNB value........................163

Figure 18

Downlink physical resource block (PRB) allocation for Cat-M and NBIoT.................................................................................................... 175

Figure 19

Uplink physical resource block (PRB) allocation for Cat-M and NB-IoT. 175

© 2017 Nokia

7


List of Tables

8

Table 1

LTE2337 hardware and software requir ements..................................14

Table 2

LTE2337: FDD-TDD Downlink Carr ier Aggregation 3CC – 2 FDD & 1 TDD sales information........................................................................15

Table 3

LTE2410 hardware and software requirements..................................17

Table 4

New parameters introduced by LTE2410........................................... 18

Table 5

LTE2410 sales information.................................................................18

Table 6


Table 7


Table 8

Parameters modified by LTE2532...................................................... 22

Table 9

LTE2532 sales information................................................................. 23

Table 10


Table 11

Existing alarms related to LTE2623....................................................31

Table 12

Existing parameters related to LTE2623............................................ 32

Table 13


Table 14


Table 15

New BTS faults introduced by LTE2912.............................................44

Table 16

New counters introduced by LTE2912................................................45

Table 17


Table 18


Table 19


Table 20


Table 21


Table 22

LTE3020 summary of changes...........................................................62

Table 23


Table 24

Existing counters related to LTE3020.................................................64

Table 25


Table 26


Table 27


Table 28


Table 29

Summary of changes..........................................................................74

Table 30

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

Table 31

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

Table 32

Parameters modyfied by LTE3056: GPS and UTC Time Information Broadcast Support (SIB16).................................................................78

Table 33

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

Table 34

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

© 2017 Nokia

Issue: 01


Issue: 01

Table 35

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

Table 36

LTE3071 summary of changes...........................................................83

Table 37

Examples of DL power settings for the NB-IoT cell............................ 86

Table 38


Table 39

New BTS faults introduced by LTE3071.............................................93

Table 40

New counters introduced by LTE3071................................................93

Table 41

Existing key performance indicators related to LTE3071................... 94

Table 42


Table 43

Parameters modified by LTE3071...................................................... 97

Table 44


Table 45


Table 46

LTE3265 hardware and software requirements................................108

Table 47

New BTS faults introduced by LTE3265...........................................109

Table 48

New parameters introduced by LTE3265......................................... 109

Table 49

Parameters rmodified by LTE3265...................................................109

Table 50

Existing parameters related to LTE3265.......................................... 109

Table 51

LTE3265 sales information................................................................111

Table 52


Table 53

New parameters introduced by LTE3509..........................................115

Table 54

Existing parameters related to LTE3509...........................................115

Table 55

LTE3509 sales information............................................................... 115

Table 56

LTE3582 summary of changes.........................................................122

Table 57

Preamble formats............................................................................. 125

Table 58


Table 59

New counters introduced by LTE3582..............................................127

Table 60

New key performance indicators introduced by LTE3582................ 128

Table 61

Key performance indicators modified by LTE3582........................... 128

Table 62


Table 63


Table 64


Table 65


Table 66

New counters introduced by LTE3586..............................................134

Table 67


Table 68


Table 69

LTE3612-associated hardware.........................................................140

Table 70


Table 71


Table 72


Table 73


Table 74


© 2017 Nokia

9


Table 75


Table 76

RRC Paging-NB free subframes needed to avoid collision with the following paging................................................................................163

Table 77

NPDCCH/NPDSCH repetitions........................................................ 166

Table 78

LTE3669: NB-IoT: Paging support hardware and software requirements.....................................................................................167

Table 79

New counters introduced by LTE3669: NB-IoT: Paging support ...... 168

Table 80

New key performance indicators introduced by LTE3669: NB-IoT: Paging support ................................................................................. 168

Table 81

New parameters introduced by LTE3669: NB-IoT: Paging support ..168

Table 82

Parameters modified by LTE3669: NB-IoT: Paging support .............168

Table 83

LTE3669: NB-Iot: Paging support sales information.........................169

Table 84


Table 85

10


Table 86


Table 87

3GPP Release 13 LTE IoT technologies.......................................... 173

Table 88

Cat-M or NB-IoT...............................................................................174

Table 89


Table 90


Table 91

LTE3819 sales information...............................................................179

© 2017 Nokia

Issue: 01


LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD and 1 TDD

1 LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD and 1 TDD The LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD feature introduces an extended downlink bandwidth with aggregated FDD and TDD component carriers (CCs).

1.1 LTE2337 benefits The LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD feature increases the spectrum efficiency by load balancing between FDD and TDD carriers which ensures higher peak data rates for the users within the network.

1.2 LTE2337 functional description The LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD feature supports FDD-TDD DL CA for three CCs with a combination of two FDD CCs and one TDD CC. A mix of non-CA and CA UEs with two or three aggregated CCs is supported in DL on each cell. The FDD cell acts as a PCell, and FDD or TDD cells act as SCells. FDD and TDD cells are hosted by different logical, co-located eNBs. Figure 1

FDD and TDD CA in LTE2337

The FDD 4RX/4TX configuration are only applicable to 5/10-Mhz FDD carriers in 2 FDD CC + 1 TDD CC combination sites.

Issue: 01

© 2017 Nokia

11



The following band combinations are supported: • • • • • • • • •

band Mhz) band Mhz) band band band band Mhz) band band Mhz) band Mhz)

1 (FDD 5/10/15/20 Mhz) + band 3 (FDD 5/10/15/20 Mhz) + band 40 (TDD 20 1 (FDD 5/10/15/20 Mhz) + band 3 (FDD 5/10/15/20 Mhz) + band 42 (TDD 20 1 1 3 3

(FDD 5/10/15/20 (FDD 5/10/15/20 (FDD 5/10/15/20 (FDD 5/10/15/20

Mhz) Mhz) Mhz) Mhz)

+ + + +

band 5 band 8 band 5 band 7

(FDD (FDD (FDD (FDD

5/10 Mhz) + band 40 (TDD 20 Mhz) 5/10 Mhz) + band 40 (TDD 20 Mhz) 5/10 Mhz) + band 40 (TDD 20 Mhz) 10/15/20 Mhz) + band 38 (TDD 20

3 (FDD 5/10/15/20 Mhz) + band 8 (FDD 5/10 Mhz) + band 40 (TDD 20 Mhz) 3 (FDD 5/10/15/20 Mhz) + band 28 (FDD 5/10/15/20 Mhz) + band 40 (TDD 20 20 (FDD 5/10/15/20 Mhz) + band 7 (FDD 10/15/20 Mhz) + band 38 (TDD 20

TM3 or TM4 or TM9 can be configured for site configurations to which it applies, and a maximum of two layers MIMO can be applied to TDD SCells. It means that eNB select the TM mode according to UE capability and configuration of cell of dlMimoMode parameter. TDD frame configuration 1 or 2 is supported in TDD cells, and the same TDD frame configuration is used with a TDD component carrier. PUCCH format3 is supported for the above-mentioned 3CC FDD/TDD band combinations. The functionality can be enabled/disabled per eNB via O&M settings.

1.3 LTE2337 system impact Interdependencies between features The following features impact the LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD feature: •

LTE1803: Downlink Carrier Aggregation 3CC – 40 MHz

•

LTE1804: Downlink Carrier Aggregation 3CC – 60 MHz LTE2337 is based on the two features above, which are FDD 3CC basic features. LTE2180: FDD+TDD 2CC DLCA – FDD PCell LTE2316: FDD-TDD Downlink Carrier Aggregation 3CC Most functionalities of the above two features, including inter-eNB interaction, version and parameter consistency checking, CA super pool setup, and sync/SRIO exceptional handling can be inherited by LTE2337 . LTE2531: FDD Downlink Carrier Aggregation 1 4CC/5CC LTE2337 reuses the PDCP SN 15, RLC profile and RRM data downgrade and upgrade algorithm from the LTE2531 feature. LTE1092: Uplink Carrier Aggregation – 2 CC With this feature enabled in an FDD eNB, uplink CA of intra-band or inter-band can be supported with respective band combinations. LTE1562: Carrier Aggregation for Multi-carrier eNodeBs

• •

•

•

•

12

© 2017 Nokia

Issue: 01


•

•

•

• • •

• •

•


This feature introduces a cell Normalized Load Comparing Value (NLCV) algorithm and load-based SCell selection. LTE2233: N-out-of-M Downlink Carrier Aggregation The LTE2233 feature is an extension of the LTE1562 feature. With the LTE2233 and LTE1562 features, the operator can make the SCell selection policy he wants, which is also helpful to the LTE2337 feature. LTE1541: Advanced SCell Measurement Handling This feature introduces the solution of L2-measurement-based SCell management, which helps on FDD and TDD CA UE in a mobility scenario. LTE2276: Measurement Based SCell Selection This feature introduces the A3-measurement-based SCell configuration without a measurement gap. LTE2006: Flexible SCell Selection LTE2712: Enhanced PUCCH Format 3 Handling LTE2479: 256QAM in Downlink The LTE2337 feature can benefit from this feature to achieve a higher downlink peak throughput in a good channel condition. LTE2270: FDD + TDD Inter-eNB CA Basic BTS Configurations The LTE2337 FDD + TDD CA site configuration is provided by the LTE2270 feature. LTE2275: PCell Swap The LTE2337 feature supports an FDD SCell, so the FDD PCell can swap to the FDD SCell with the LTE2275 feature enabled. LTE2582: DL 4x4 MIMO with Carrier Aggregation

Impact on interfaces The LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD feature has no impact on interfaces. Impact on network management tools The LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD feature has no impact on network management tools. Impact on system performance and capacity With the LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD feature, UE downlink peak throughput can reach 410 Mbps with 2x2 MIMO. The following image show an increase in the peak rate: Figure 2

The peak rate can reach up to 410 Mbps

~410 Mbps

Issue: 01

s p b M 0 5 1

s p b M 0 5 1

s p b M 0 1 1

2x2 MIMO w/64 QAM

2x2 MIMO w/64 QAM

2x2 MIMO w/64 QAM

© 2017 Nokia

13



1.4 LTE2337 reference data Requirements Table 1

LTE2337 hardware and software requirements

FDD

TDD

System release

FDD-LTE 17A

TD-LTE 17A

Flexi Multiradio 10 BTS

Not supported

TL17A

Flexi Multiradio 10 Indoor BTS

FL17A

TL17A

Nokia AirScale BTS

Not supported

Not supported

Flexi Zone BTS

Not supported

Not supported

Flexi Zone Access Point

Not supported

Not supported

Flexi Zone Controller

Not supported

Not supported

OMS

Support not required


NetAct



MME



SAE GW



UE

3GPP R12 UE capabilities, 3GPP R13 UE capabilities

3GPP R12 UE capabilities, 3GPP R13 UE capabilities

Alarms There are no alarms related to the LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD feature. BTS faults and reported alarms There are no faults related to the LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD feature. Commands There are no commands related to the LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD feature. Measurements and counters There are no measurements or counters related to the LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD feature. Key performance indicators There are no key performance indicators related to the LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD feature. Parameters There are no parameters related to the LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD feature.

14

© 2017 Nokia

Issue: 01



Sales information Table 2

LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD sales information

Product structure class

Application software (ASW)

Issue: 01

License control

Pool license

© 2017 Nokia

Activated by default

No

15

LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls


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.

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

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: •

•

•

g

16

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

© 2017 Nokia

Issue: 01



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.



Issue: 01

FDD

TDD

System release

FDD-LTE 17A

TD-LTE 17


FL17A

TL17A


Not supported

TL17A

Nokia AirScale BTS

FL17A

TL17A

Flexi Zone BTS

FL17A

TL17A

© 2017 Nokia

17


Table 3


LTE2410 hardware and software requirements (Cont.)

FDD

TDD


FL17A

TL17A


FL17A

TL17A

OMS

LTE OMS17

LTE OMS17

NetAct

NetAct 17.2

NetAct 17.2

MME

Flexi NS 17

Flexi NS 17

SAE GW



UE

3GPP R8 mandatory

3GPP R8 mandatory

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 4

New parameters introduced by LTE2410 Full name

Activate CSFB EC access restriction removal

Abbreviated name

Manage d object

actCsfbECRestr Rem

LNBTS

Parent structure

–

FDD/TDD

common

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

LTE2410 sales information


Basic Software (BSW)

18

License control

–

© 2017 Nokia


Yes

Issue: 01


LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO

3 LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO The LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO feature introduces TDD downlink carrier aggregation (CA) with up to four multiple-inputsmultiple-outputs (MIMO) layers of spatial multiplexing.

3.1 LTE2532 benefits The LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO feature provides the following benefit: •

Ensures higher UE downlink peak rates by enabling intra-eNB and inter-eNB carrier aggregation with up to four layers of spatial multiplexing (MIMO). This leads to an overall improvement of the end-to-end performance (for example: up to 420 Mbps for TDD downlink with two component carriers (CC) CA and 4x4 MIMO).

3.2 LTE2532 functional description MIMO is a method used in wireless communications to multiply the capacity of a radio link by using multiple antennas both at the source (transmitter) and the destination (receiver). The antennas at each end of the communication circuit are combined to minimize errors and optimize data speed. In practice, MIMO is a technique of sending and receiving multiple data streams (spatial layers) over a given frequency-time resource (radio channel). The eNB selects for a UE the MIMO transmission mode (TM4 or TM9) and the maximum number of spatial layers per serving cell during the following events: • •

Secondary cell (SCell) addition and release Primary cell (PCell) handover, swap or initial context setup

Within the scope of the LTE2532 feature, TM4 (closed loop spatial multiplexing), which supports maximum four layers of spatial multiplexing, is the preferred transmission mode when the activatedMimoTM parameter of a cell with the serving cell role is set to TM9_maxLayer . Multiple UE MIMO capabilities per CA band combination are supported with TM4. TM9 is selected only if more layers are supported per serving cell than in the case of TM4. This is done based on the eNB’s configuration (TM, maximum number of layers, codebook restriction) and the UE’s capabilities. The UE is informed through the radio resource control signaling protocol (RRC) about the selected configuration per serving cell and the TM to use. The total number of layers per UE is 10. Supported configurations The feature introduces the following new CA configurations:

Issue: 01

© 2017 Nokia

19


• •

The minimum configuration consists of: 2 CC with 4x4 MIMO – TM4 or 4x4 MIMO – TM9 configured on at least one of the serving cells. The maximum configurations are: – – – –

g


2 1 2 1

CC CC CC CC

4x4 MIMO 4x4 MIMO 4x4 MIMO 4x4 MIMO

+ 1 CC 2x2 + 2 CC 2x2 256 QAM + 256 QAM +

MIMO with 64 QAM MIMO with 64 QAM 1 CC 2x2 MIMO with 256 QAM 2 CC 2x2 MIMO with 256 QAM

Note: Any subset of these configurations, with four MIMO layers configured for a UE, on at least one serving cell, is also a new supported configuration. Inter-eNB CA supports up to two collocated eNBs connected via serial rapid IO (SRIO) to form a CA cluster. Inter-eNode B downlink CA with one SRIO connection supports: • •

a maximum of six cross eNB SCell candidates with two MIMO layers per TDD eNB. a maximum of three cross eNB SCell candidates with four MIMO layers (4x4) per TDD eNB.

3.3 LTE2532 system impact Interdependencies between features The following features must be activated before activating the LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO feature: • •

g

LTE569: Downlink Adaptive Closed Loop SU MIMO 4x4 - TM 4 LTE1987: Downlink Adaptive Close Loop SU MIMO (4x4) - TM9 Note: The LTE2479: 256 QAM in Downlink feature is a prerequisite for configurations using 256 QAM on a serving cell. However, the LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO can also function when LTE2479: 256 QAM in Downlink is disabled, this leading to a reduction of the peak data rates.

At least one of the following CA features must be activated before activating the LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO feature: • • • • •

LTE1558: TDD Downlink Carrier Aggregation LTE1830: TDD Downlink Carrier Aggregation Enhancement LTE1836: TDD Downlink Carrier Aggregation – 60 Mhz LTE1838: TDD Downlink Inter-band Carrier Aggregation – 40 Mhz LTE2244: Inter eNode B TDD Carrier Aggregation

Interworking of the LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO feature with other CA features: • • •

20

LTE1541: Advanced SCell Measurement Handling LTE2006: Flexible SCell Selection LTE2105: TDD Uplink Carrier Aggregation for 2 CCs

© 2017 Nokia

Issue: 01



LTE2275: PCell Swap LTE2416: TDD Uplink 2CC Carrier Aggregation Extensions

• •

Impact on interfaces The LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO feature impacts interfaces as follows: RRC

•

– –

Adds new UE capabilities and new RRC IEs to support DL CA with up to 4 layers (per serving cell) based on TM4 (Rel-10). Adds new UE capabilities and new RRC IEs to support carrier specific number of layers in intra-band contiguous CA (Rel-12).

Impact on network management tools The LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO feature has no impact on network management tools. Impact on system performance and capacity The LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO feature has no impact on system performance or capacity.



FDD

TDD

System release

Not supported

TD-LTE 17A


Not supported

TL17A


Not supported

TL17A

Nokia AirScale BTS

Not supported

TL17A

Flexi Zone BTS

Not supported

not supported


Not supported

not supported


Not supported

not supported

OMS

Not supported

LTE OMS16A

NetAct

Not supported

NetAct 17.2

MME

Not supported


SAE GW

Not supported


UE

Not supported

3GPP R10 UE capabilities 3GPP R11 UE capabilities 3GPP R12 UE capabilities 3GPP R13 UE

Issue: 01

© 2017 Nokia

21



Alarms There are no alarms related to the LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO feature. BTS faults and reported alarms There are no faults related to the LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO feature. Commands There are no commands related to the LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO feature. Measurements and counters There are no measurements or counters related to the LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO feature. Key performance indicators There are no key performance indicators related to the LTE2532: TDD Downlink Carrier Aggregation with 4 Layers MIMO feature. Parameters Table 7

New parameters introduced by LTE2532 Full name

g

Manage d object

Parent structure

FDD/TDD

Sequence number size

snSize

LNBTS

pdcpProf1

TDD


snSize

LNBTS

pdcpProf2

TDD


snSize

LNBTS

pdcpProf3

TDD


snSize

LNBTS

pdcpProf4

TDD


snSize

LNBTS

pdcpProf5

TDD

Maximal number of supported MIMO layers

maxNumOfSuppMi moLayer

CAREL

-

common

Note: From LTE17 SP onwards, due to the introduction of the LTE2532 feature, the Preference 4-layer MIMO versus carrier aggregation (pref4LayerMimoVsCAggr) parameter has been removed.

Table 8

Parameters modified by LTE2532 Full name

Activation of downlink carrier aggregation

22

Abbreviated name

Abbreviated name

Manage d object

actDLCAggr

LNBTS

© 2017 Nokia

Parent structure

-

FDD/TDD

common

Issue: 01


Table 8


Parameters modified by LTE2532 (Cont.) Full name

Abbreviated name

Downlink MIMO mode

dlMimoMode

Manage d object

Parent structure

LNCEL_ TDD

FDD/TDD

TDD




License control


Pool license


No

3.5 Activating LTE2532 Before you start Procedure notifications: • • • •

The used antenna system supports four antenna elements. The LTE569 and LTE1987 features are deactivated, that is, the dlMimoMode parameter is not set to Closed Loop MIMO (4x4). Legacy intra-eNB carrier aggregation features are activated, that is, the LNBTS: actDLCAggr is set to true in the connected eNBs. The actInterEnbDlCAggr parameter, related to the LTE2244 feature, is set to true.

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.

Issue: 01

© 2017 Nokia

23



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

3

Go to to the Cell Resources page.

4

Select Closed Loop MIMO (4x4) from the MIMO mode dropdown list. The MIMO mode dropdown list is located in the MIMO settings section of the Cell Resources page.

5

Proceed to the Radio Network Configuration page.

6

Set the activatedMimoTM parameter to the corresponding value (TM4, TM9 or TM9_maxLayer). Object path: MRBTS ► LNBTS ► LNCEL ► LNCEL_TDD

7

Go to MRBTS ► LNBTS ► LNCEL

8

Create the CAREL object. Sub-steps

a) Right-click the LNCEL object

b) Select New and find the CAREL object.

c) Configure the CAREL object.

9

Set the Maximal number of supported MIMO layers maxNumOfSuppMimoLayer ( ) value to 4-layer for four-layer CA support or 2-layer for two-layer CA support. Repeat this step for each SCell.

g

24

Note: If the MIMO mode is set to Closed Loop MIMO (8x4), then the maxNumOfSuppMimoLayer parameter must be set to 2-layer .

© 2017 Nokia

Issue: 01



10 Send the commissioning plan file to the BTS. Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option. • •

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

c) Click Send Parameters.

3.6 Deactivating LTE2532 Before you start Procedure notifications: • • • •

The used antenna system supports four antenna elements. The LTE2532 feature has the dlMimoMode parameter set toClosed Loop MIMO (4x4) in at least one LNCEL instance of the eNB. The LTE1558 feature is activated, that is, the LNBTS: actDLCAggr is set to true in the connected eNBs. The actInterEnbDlCAggr parameter, related to the LTE2244 feature, is set to true.

To deactivate the feature do the following: Procedure

1


2



Issue: 01

© 2017 Nokia

25




3


4

Go to the LNCEL_TDD object. Object path: MRBTS ► LNBTS ► LNCEL Sub-steps

a) Optionally, if inter-eNB CA must be disabled, set the Activate intereNB DL carrier aggregation (actInterEnbDLCAggr) parameter to false. Repeat this step for each LNCEL instance where inter-eNB CA has to be deactivated.

b) Optionally, if intra-eNB CA must be disabled, set the Activation of downlink carrier aggregation (actDLCAggr) parameter to false. Repeat this step for each LNCEL instance where intra-eNB CA has to be deactivated.

5

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

6

Set the Maximal number of supported MIMO layers (maxNumOfSuppMimoLayer) value to 2-layer.

7

Go to the Cell Resources page.

8

Select any other value except Closed Loop MIMO (4x4) from the MIMO mode dropdown list. The MIMO mode dropdown list is located in the MIMO settings section of the Cell Resources page.

g

26

Note: Repeat this step for each SCell where CA with four MIMO layers has to be deactivated.

© 2017 Nokia

Issue: 01


9


Send Send the the commi commissi ssion oning ing plan plan file file to to the the BTS. BTS. Sub-steps

a) Go to to the Sen Send d Parame Paramete ters rs page. page.

b) Select Select an an approp appropriat riate e Send Send option option.. • •

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

c) Click Click Send Send Param Paramete eters. rs.

Issue: 01

© 2017 Nokia

27

LTE2623: FDD-TDD Downlink Carrier Aggregation Aggregation 4CC 4CC

LTE17A Radio Resource Management Management and and Telecom Telecom Features

4 LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC The LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC 4CC feature enables aggregating air interface resources of up to four overlapping cells, FDD and TDD, in order to reach high downlink peak rates for an individual user. The maximum bandwidth aggregated with the feature is 80 MHz.

4.1 LTE2623 benefits The LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC 4CC feature provides the following benefits: •

•

extends downlink carrier aggregation across both FDD and TDD technologies, allowing for a more efficient use of the radio spectrum and resources of four component carriers enables downlink peak rates of up to 690 Mbps for a single UE in ideal conditions (downlink peak rates are determined by UE capabilities, radio conditions, other traffic, and HW capabilities)

4.2 LTE2623 functional description The LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC 4CC feature enables the eNB to support carrier aggregation (CA) in downlink (DL) for up to four component carriers (CCs). A mix of UEs not capable of CA and UEs capable of DL CA with two, three, or four aggregated CCs is supported. Only the 2CC FDD + 2CC TDD combination is supported. Figure 3

2CC FDD + 2CC TDD combination with LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC

FDD Bands

Time

DL

UL

PCell

UL

TDD Bands DL

DL

DL

SCell 1

SCell 2

S Cell 3 SC

UL

UL

DL

UL Frequency

28

© 2017 Nokia

Issue: 01


LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC

An FDD cell acts as a primary cell (PCell) or secondary cell (SCell), and TDD cells act only as SCells. SCell selection is based on normalized load compare value (NLCV) set by eNB. The site configuration has FDD cells and TDD cells hosted by different logical, colocated eNBs, and the following receiver/transmitter configurations are supported: • •

FDD 4Rx/4Tx configuration is only supported with 5 MHz or 10 MHz FDD carriers in 2 FDD CC + 2 TDD CC combination sites FDD 15 MHz or 20 MHz carriers are only supported with 2Rx/2Tx configuration in 2 FDD CC + 2 TDD CC combination sites

All 2CC FDD + 2CC TDD DL CA band combinations listed in 3GPP TS 36.101 are supported. 1CC FDD + 3CC TDD and 3CC FDD + 1CC TDD combinations are not supported. With the use of multiple antennas, LTE2623 LTE2623 supports multiple-input transmission modes TM3 and TM4, and maximum two layers MIMO can be applied to a TDD SCell. TDD frame configurations 1 or 2 are supported, but the same configuration must be in both TDD SCells.

4.3 LTE2623 system impact Interdependencies between features The following features must be activated before activating the LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC 4CC feature: • • • • • • • • •

LTE1803: Downlink Carrier Aggregation 3CC – 40 MHz LTE1804: Downlink Carrier Aggregation 3CC – 60 MHz LTE2531: FDD Downlink Carrier Aggregation 4CC LTE1836: TDD Downlink Carrier Aggregation – 60 Mhz LTE2179: TDD Downlink Carrier Aggregation 4CC – 80 Mhz 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 LTE1562: Carrier Aggregation for Multi-carrier eNodeBs

The LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC 4CC feature is impacted by the following features: • • •

• •

Issue: 01

LTE2275: PCell Swap With LTE2275 enabled, LTE2623 LTE2623 supports an FDD PCell swap to the FDD SCell. LTE1092: Uplink Carrier Aggregation – 2CC LTE2337: FDD-TDD downlink carrier aggregation 3CC - 2 FDD & 1 TDD With this feature enabled inside an FDD eNB, uplink CA for intra-band and interband is supported within the feature's own band combination restrictions. The FDD + FDD UL CA is downgraded to DL CA only when first TDD SCell is added. LTE2582: DL 4x4 MIMO with Carrier Aggregation With this feature enabled, LTE2623 LTE2623 can increase throughput for FDD CC. LTE2479: 256 QAM in Downlink

© 2017 Nokia

29


• •

•


With this feature enabled, LTE2623 can use 256 QAM on a serving cell for a higher downlink peak throughput in good channel conditions. LTE2270: LTE TDD+FDD Inter-eNB CA Basic BTS Configurations LTE2270 provides FDD+TDD site configurations for LTE2623. LTE2276: Measurement-based SCell Selection LTE2276 introduces an A3 measurement-based SCell configuration without a measurement gap. LTE1541: Advanced SCell Measurement Handling LTE1541 introduces L2 measurement-based SCell management, which LTE2623 can benefit from.

Impact on interfaces The LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC feature has no impact on interfaces. Impact on network management tools The LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC feature has no impact on network management tools. Impact on system performance and capacity The LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC feature impacts system performance and capacity as follows: •

•

Downlink peak throughput of up to 690 Mbps for a single UE for 4CC CA, 4x4 MIMO, 256 QAM, and in ideal conditions (with a theoretical peak throughput up to 1.2 Gbps in ideal conditions) Capacity for FDD-TDD DL CA 4CC is up to 50 active UEs and up to 100 connected UEs



30

FDD

TDD

System release

FDD-LTE 17A

TD-LTE 17A


FL17A

TL17A


Not supported

Not supported

Nokia AirScale BTS

Not supported

Not supported

Flexi Zone BTS

Not supported

Not supported


Not supported

Not supported

Cloud Flexi Zone Controller

Not supported

Not supported

OMS



NetAct



© 2017 Nokia

Issue: 01


Table 10



FDD

TDD

MME



SAE GW



UE

3GPP R13 UE capabilities


Additional hardware requirements The required system module's configurations are FSMF (for FDD) and FSMF or FSIH (for TDD). The FDD 4Rx/4Tx configuration is supported only with 5-MHz or 10-MHz carriers in 2CC FDD + 2CC TDD combination sets. Alarms There are no alarms related to the LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC feature. BTS faults and reported alarms Table 11

Existing alarms related to LTE2623

Fault ID

Fault name

Reported alarms Alarm ID

Alarm name

4262

SRIO link outage

7651

BASE STATION OPERATION DEGRADED

6282

Inter eNB CA parameter(s) inconsistency in between eNBs

7651


6283

Inter eNB SW inconsistency in between cluster members

7651


For fault descriptions, see FDD-LTE BTS Alarms and Faults descriptions and TD-LTE BTS Alarms and Faults descriptions. Measurements and counters There are no measurements or counters related to the LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC feature. Key performance indicators There are no key performance indicators related to the LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC feature. Parameters

Issue: 01

© 2017 Nokia

31


Table 12


Existing parameters related to LTE2623

Full name

Abbreviated name

Manage d object

Activate inter-eNB DL carrier aggregation

actInterEnbDLC Aggr

LNBTS

-

common

Carrier aggregation cluster ID

caClusterId

LNBTS

-

common

Carrier aggregation cluster member ID

caClusterMembe rId

LNBTS

-

common

BTS ID of the parent eNB of the cell to be aggregated

lnBtsId

CAREL

-

common

Local cell resource ID of cell to be aggregated

lcrId

CAREL

-

common

Parent structure

FDD/TDD

For parameter descriptions, see FDD-LTE BTS Parameters and TD-LTE BTS Parameters. Sales information Table 13



License control


Pool license


No

4.5 Activating and configuring LTE2623 Before you start •

Procedure notifications –

•

Feature interdependencies The following features must be activated before activating the LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC feature: – – – – – – – – –

32

Activation procedure may require eNB restart.

LTE1803: LTE1804: LTE2531: LTE1836: LTE2179: LTE2180: LTE2316: LTE2337: LTE1562:

Downlink Carrier Aggregation 3CC – 40 MHz Downlink Carrier Aggregation 3CC – 60 MHz FDD Downlink Carrier Aggregation 4CC TDD Downlink Carrier Aggregation – 60 Mhz TDD Downlink Carrier Aggregation 4CC – 80 Mhz FDD-TDD Downlink Carrier Aggregation 2CC FDD-TDD Downlink Carrier Aggregation 3CC FDD-TDD Downlink Carrier Aggregation 3CC – 2 FDD & 1 TDD Carrier Aggregation for Multi-carrier eNodeBs

© 2017 Nokia

Issue: 01



The LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC feature is impacted by the following features: LTE2275: PCell Swap With LTE2275 enabled, LTE2623 supports an FDD PCell swap to the FDD SCell. LTE1092: Uplink Carrier Aggregation – 2CC LTE2337: FDD-TDD downlink carrier aggregation 3CC - 2 FDD & 1 TDD With this feature enabled inside an FDD eNB, uplink CA for intra-band and interband is supported within the feature's own band combination restrictions. The FDD + FDD UL CA is downgraded to DL CA only when first TDD SCell is added. LTE2582: DL 4x4 MIMO with Carrier Aggregation With this feature enabled, LTE2623 can increase throughput for FDD CC. LTE2479: 256 QAM in Downlink With this feature enabled, LTE2623 can use 256 QAM on a serving cell for a higher downlink peak throughput in good channel conditions. LTE2270: LTE TDD+FDD Inter-eNB CA Basic BTS Configurations LTE2270 provides FDD+TDD site configurations for LTE2623. LTE2276: Measurement-based SCell Selection LTE2276 introduces an A3 measurement-based SCell configuration without a measurement gap. LTE1541: Advanced SCell Measurement Handling LTE1541 introduces L2 measurement-based SCell management, which LTE2623 can benefit from.

– – –

– –

– –

–

•

Preconfiguration – – –

–

–

–

–

–

–

The supported system module's hardware configurations are FSMF (for FDD) and FSMF or FSIH (for TDD). SRIO links and sync cables between eNBs are properly connected and SRIO communication between the eNBs is established. Four cells are available for carrier aggregation on a band combination supported by the LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC feature (for example, configured on Cell Resources and LTE Carriers pages). The Activation of downlink carrier aggregation (actDLCAggr) LNBTS parameter is set to true on all the eNBs. The Activate supercell configuration (actSuperCell) LNCEL_FDD parameter on all the FDD eNBs and the LNCEL_TDD parameter for all the TDD eNBs are set to false. The Activate Centralized RAN (actCRAN) LNBTS parameter is set to false. The LTE1710: Sync Hub Direct Forward feature must be configured for the eNBs in the CA cluster, with one eNB as master and the others as slave. The slave(s) must be configured for the phase sync mode (the Network synchronization mode (btsSyncMode) parameter on the BTS Synchronization Settings page must be set to Phase synchronization). LTE2006: Flexible SCell Selection is activated, that is, its feature activation flag, the Activate flexible SCell selection (actFlexScellSelect) LNBTS parameter, is set to true. If exists, for each LNCEL_FDD and LNCEL_TDD instance in CA cluster: •

Activate liquid cell configuration (actLiquidCell) is set to

false

Issue: 01

© 2017 Nokia

33


–

–


•

Activation of automatic PUCCH allocation (actAutoPucchAlloc) is set to false

•

Max number of secondary cells for DL carrier aggr (maxNumScells) is set to 3 for all FDD cells

The Downlink MIMO mode (dlMimoMode) LNCEL_FDD parameter on all the FDD eNBs and the LNCEL_TDD parameter for all the TDD eNBs are configured on Cell Resources page. The eNB software versions are compatible.

Procedure

1


2




3


4

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

5

Set the Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr) value to true.

6

Configure the CA cluster within the LNBTS object by setting the following parameters: Sub-steps

a) Set the Carrier aggregation cluster ID (caClusterId ) parameter to the same value across the CA cluster.

34

© 2017 Nokia

Issue: 01



b) Set the Carrier aggregation cluster member ID (caClusterMemberId ) parameter to a unique value for each of the connected eNBs.

c) Set the Number of eNBs in a carrier aggregation cluster (caClusterNumEnb) parameter to the value equal to number of eNBs in the CA cluster.

7

For FDD PCell candidate, create (if not present) and configure at least three CAREL objects, one pointing to an FDD cell in the same FDD eNB and two pointing to SCells in the TDD eNB. Object path: MRBTS ► LNBTS ► LNCEL ► CAREL

g

Note: The combination of BTS ID of the parent eNB of the cell to be aggregated (lnBtsId) and Local cell resource ID of cell to be aggregated (lcrId)

parameters must be unique in the PCell and all related SCells in all LNBTSs of the CA cluster.

8

Send the commissioning plan file to the BTS. Sub-steps





Result After a positive validation of parameters and software versions, inter-eNB CA is enabled, and FDD and TDD eNBs work in the CA cluster. In case of misconfiguration of inter-eNB CA or other parameters, the 6282 Inter eNB CA parameter(s) inconsistency in between eNBs fault is reported with a related alarm. In case of a SRIO link failure, the 4262 SRIO link outage fault is reported with a related alarm.

Issue: 01

© 2017 Nokia

35



In case of incompatible software for CA operations, the 6283 Inter eNB SW inconsistency in between cluster members fault is reported with a related alarm.

4.6 Deactivating LTE2623 Before you start •


•

Activation procedure requires eNB restart.

Preconfiguration – – –

–

–

–

–

The supported system module's hardware configurations are FSMF (for FDD) and FSMF or FSIH (for TDD). SRIO links and sync cables between eNBs are properly connected and SRIO communication between the eNBs is established. Four cells are available for carrier aggregation on a band combination supported by the LTE2623: FDD-TDD Downlink Carrier Aggregation 4CC feature (for example, configured on Cell Resources and LTE Carriers pages). The Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr) LNBTS parameter is set to true, and carrier aggregation is enabled. The LTE1710: Sync Hub Direct Forward feature must be configured for the eNBs in the CA cluster, with one eNB as master and the others as slave. The slave(s) must be configured for the phase sync mode (the Network synchronization mode (btsSyncMode) parameter on the BTS Synchronization Settings page must be set to Phase synchronization). The Downlink MIMO mode (dlMimoMode) LNCEL_FDD parameter on all the FDD eNBs and the LNCEL_TDD parameter for all the TDD eNBs are configured on Cell Resources page. The eNB software versions are compatible.

Procedure

1


2



36

© 2017 Nokia

Issue: 01




3


4


5

Set the Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr) value to false.

6






Result Inter-eNB CA is disabled in the CA cluster. LNCEL instances and all the parameter settings remain unchanged.

Issue: 01

© 2017 Nokia

37

LTE2912: TD-LTE Baseband Pooling


5 LTE2912: TD-LTE Baseband Pooling The LTE2912: TD-LTE Baseband Pooling feature enables more efficient usage of baseband resources for the Nokia AirScale BTS and a more flexible adjustment of resource allocation to the actual traffic needs of different radio cells. Baseband pooling replaces a fixed and uniform mapping of cells or users to processing resources. It allows for a dynamic or semi-static mapping between cells or users and processing resources allocated to a baseband pool.

5.1 LTE2912 benefits The LTE2912: TD-LTE Baseband Pooling feature provides the following benefits: • •

efficient usage of baseband resources higher individual cell capacity in an unbalanced load situation

5.2 LTE2912 functional description Feature overview The LTE2912: TD-LTE Baseband Pooling feature supports: • • •

maximum two 8Tx8Rx cells per baseband pool the same UL and DL configuration in each pool the same or different special subframe (SSF) configuration for two cells in each pool (in the case of different SSF configuration, the two cells in each baseband pool have the same number of uplink pilot time-slot (UpPTS) symbols)

In a baseband pool, only the following SSF combinations are allowed: • •

SSF5 or SSF7 or SSF6 or SSF9 SSF3 or SSF4

Baseband pooling is possible with every AirScale BTS-based system variant, no matter whether it is an outdoor or indoor version and whether it has one or more core units and one or more baseband units. Each baseband unit or baseband extension unit has at least the capacity of one baseband pool. For TDD, the baseband pool capacity does not take into account the number of antennas. Due to a smaller number of cells per baseband pool, there is no baseband pool limitation on outgoing or incoming PCell-to-SCell carrier aggregation relations. With the LTE2912: TD-LTE Baseband Pooling feature, the following types of cell pools are affected: • •

U-plane cell pool C-plane cell pool

U-plane cell pool

38

© 2017 Nokia

Issue: 01



Each AirScale BTS indoor system module capacity unit supports either one or two Uplane cell pools, depending on the number of activated hardware capacity licenses. The assignment of cells connected to U-plane cell pools on the AirScale BTS is done automatically by the eNB, which is considering, for example, the UL coordinated multipoint transmission (CoMP) set, cell bandwidth, the number of Rx ports per cell, carrier frequency, and so on. The reassignment of cells to U-plane cell pools can be triggered via O&M commands; this is useful after activation of a hardware activation license. It is possible for the operator to configure the assignment of cells to pools using parameters in the BBPOOLALLOC object. The reassignment of a cell from one pool to another requires a reset of the cell. The pooling functionality enables to dynamically share baseband processing resources for U-plane resources among all cells assigned to a pool. Optionally, it is possible to reserve some resources for emergency calls, high priority and incoming handovers for radio reasons, or incoming time-critical handovers. The baseband processing resources for U-plane are: • • • • • • • •

the number of RRC-connected UEs the number of guaranteed bit rate (GBR) or nominal bit rate (NBR) data radio bearers (DRBs) physical uplink control channel (PUCCH) resources physical uplink shared channel (PUSCH) resources (including resources for UL CoMP) sounding reference signal (SRS) resources random access channel (RACH) resources scheduled users per transmission time interval (TTI) (UL and DL) DL/UL throughput (PDCP/RLC pool)

The allocation split of all resources listed above is done dynamically, periodically, or on an as-needed basis. Overbooking of cell resources is supported. The cell's individual peak performance (for example, the number of RRC-connected UEs or UL peak rate) cannot be reached in all cells at the same time. The PDCP and RLC resource pools are shared across all AirScale BTSs. A UE is assigned at an RRC connection setup to the PDCP/RLC pool with the lowest load. The assignment is kept for the lifetime of the RRC connection. Additional admission control and congestion control checks are introduced on a cell-pool level besides cell-level admission control checks, for example: • • •

RRC-connected UEs per U-plane cell pool DRBs per U-plane cell pool GBR bearers per U-plane cell pool

C-plane cell pool Each AirScale BTS supports at least one C-plane pool. The following C-plane pools are available: •

Issue: 01

Without virtual multipoint control units (MCUs):

© 2017 Nokia

39

LTE29 TE2912 12:: TD-L TD-LTE TE Base Baseba band nd Pool Poolin ing g

– –

•

LTE17 TE17A A Radi Radio o Reso Resour urce ce Mana Manage geme ment nt and and Telec elecom om Features

In a single ASIA eNB configuration: configurati on: one C-plane pool In a dual ASIA eNB configuration: one C-plane pool on the first ASIA and one Cplane pool on the second ASIA

With virtual MCUs: – –

In a single ASIA eNB configuration: configurati on: two C-plane pools In a dual ASIA eNB configuration: one C-plane pool on the first ASIA and three or four C-plane pools on the second ASIA (up to final implementation)

The assignment of U-plane cell pools to C-plane cell pools is done automatically by the eNB. The pooling functionality enables to dynamically share baseband processing resources among all cells assigned to a C-plane pool on an as-needed basis. Figure 4

An example of Nokia AirScale BTS resource allocation (blue lines): LTE2912 not enabled (top), LTE2912 enabled (bottom)

Nokia AirScale BTS C-plane Pool

Cell 1

Cell 3

Cell 3

Nokia AirScale BTS C-plane Pool Baseband Pool

Cell 1

Cell 3

Cell 3

Additional admission control checks are introduced introduced on a cell-pool level besides cell-level admission control checks, for example, RRC-connected UEs per C-plane cell pool. On a C-plane cell-pool level, capacity can be reserved for RRC-connected UEs to allow for emergency calls, incoming handovers for radio reasons, or incoming time-critical handovers.

5.3 LTE2912 system impact Interdependencies between features

40

© 2017 Nokia

Issue: 01



The following features must be activated before activating the LTE2912: TD-LTE Baseband Pooling feature: • • • • • • • • • •

LTE534: ARP-based Admission Control for ERABs LTE2114: LTE2114: AirScale Common ASIA LTE2252: FSM OD-Cabinet FCOB LTE2261: AirScale Capacity ABIA LTE2262: AirScale Subrack AMIA LTE3044: AirScale Compact 8Tx8Rx Site Configurations LTE1130: LTE1130: Dynamic PUCCH Allocation LTE2664: Load-based PUCCH Region LTE2306: AirScale TD-LTE TD-LTE 4T4R Site Configurations LTE2720: AirScale TD-LTE TD-LTE 8T8R Site Configurations for TL17

The feature related to LTE2912: TD-LTE Baseband Pooling : •

LTE2517: AirScale HW Capacity Activation Licence

The LTE2912: TD-LTE Baseband Pooling feature impacts the following features: •

Radio admission control (RAC) With the introduction of baseband pools, RAC has to consider the SW deployment within Nokia AirScale BTS as well as cell, baseband pool, and C-plane pool limits. The following RAC-related features are impacted: – – – – –

•

Bearer management All features related to guaranteed guaranteed bit rate (GBR) and nominal bitrate handling are impacted as available resources are to be assigned on a baseband pool and cell level. With the introduction of baseband pools, scheduling has to be done in a quality-of-service-aware manner on a cell and baseband pool level. The following features are impacted: – – – – – –

•

–

Issue: 01

LTE9: Service Differentiation Differentiat ion LTE10: EPS Bearers for Conversational Voice LTE496: Support of QCI 2,3 and 4 LTE1231: Operator-specific Operator-specifi c GBR QCIs LTE1042: Nominal Bitrate for Non-GBR Bearers LTE1321: eRAB Modification Modificati on – GBR

PRACH/RACH The mapping of cells requiring a larger number of PRACH root sequences to baseband pools shall consider the number of available root sequences per baseband pool. The following features are impacted: –

•

LTE20: Admission Control LTE497: Smart Admission Control LTE534: ARP-based Admission Control for ERABs LTE2598: ARP-based QoS QoS Profiling LTE2713: ARP-based Admission Control Offsets

LTE97: Cell Radius Max 77 km LTE48: Support of High-speed Users

Carrier aggregation

© 2017 Nokia

41

LTE29 TE2912 12:: TD-L TD-LTE TE Base Baseba band nd Pool Poolin ing g

•

Since such resources as PUCCH and PUSCH are pooled, all carrier aggregation features are impacted by this feature. Load balancing The pool load and the load of individual cells are considered by the load balancing features. The following load balancing features are impacted: – – – – – – –

•

•

–

LTE1402: Uplink Intra-eNB CoMP

–

LTE1691: Uplink Intra-eNB CoMP 4 RX LTE2128: Uplink Intra-eNB CoMP 8 RX with Soft-bit Combination LTE2104: Uplink Intra-eNodeB CoMP 4 RX with Softbit Combination

–

Sounding reference signal (SRS) With the introduction of baseband pools, the SRS resources are limited by the pool capacity. Therefore, the following features using SRS are impacted as the number of UEs using SRS can be changed: – –

•

– –

• •

42

LTE513: Suppport of Sounding Reference Signal in TDD UpPTS LTE540: Sounding Reference Signal in Normal Frames

Enhanced inter-cell interference coordination (eICIC) If not all resources allocated to a cell are used due to almost blank subframes (ABS), these resources will not be given back to the baseband pool but allocated to other cells. The following eICIC features are impacted: –

•

LTE1387: Intra-eNB IF Load Balancing LTE1170: Inter-eNB IF Load Balancing LTE1531: Inter-frequency Load Balancing Extension LTE1140: Intra-frequency Load Balancing LTE1841: Inter-frequency Load Equalization LTE2050: Load-triggered Idle Mode Load Balancing LTE2210: Intra-frequency Intra-frequenc y Load Balancing Extensions

Power saving LTE1103: Load-based Power Saving for Multi-layer Networks If a cell is switched off for power saving reasons, the static or semi-static pool resources allocated to this cell cannot be given back to the pool for allocation to other cells. UL coordinated multipoint transmission transmissi on (CoMP) This feature is for 4- or 8-pipe, and the softbit combination is used for 4 or 8 Rx UL CoMP. With a softbit combination, it supports inter-ABIA cross pool allocation of cells to a CoMP set. In addition, it supports intra-ABIA inter-baseband pool allocation of cells to a CoMP set and intra-ABIA intra-baseband pool allocation of cells to a CoMP set. The following features are impacted:

–

•


LTE1113: LTE1113: eICIC eICI C – Macro LTE2209: eICIC Enhancements – Macro LTE2133: eICIC for HetNet eNodeB Configurations

LTE907: TTI Bundling It is guaranteed that TTI bundling PUSCH PRBs are pre-allocated from the pool resources to the same cell. This also applies to the number of UEs per TTI. LTE1929: UL Semi-persistent Semi-persist ent Scheduling LTE432: Cell Outage Detection

© 2017 Nokia

Issue: 01


• •

•

•


If a cell outage is detected, no pool optimization is performed. This means that the resources allocated to this cell are not given back to the pool and are not reallocated to other cells of the pool. If a cell is deleted from the pool, the resources allocated to this cell are given back to the pool and are available for reassignment. LTE720: SON LTE BTS Auto-configuration The auto-configuration takes into account the automatic assignment of cells to pools. LTE2060: Add New Frequency or Cell without Reset Adding a new cell or new frequency to a pool is possible without impacting (blocking or reseting) the other cells of the pool or eNB, considering the limitations outlined in the LTE2060 feature (for example UL CoMP). Adding a cell or frequency to a pool is possible without a reset as long as the pool limits are maintained. If a cell or a frequency is added to a pool, the pool resources shall be reallocated within the pool without a reset. LTE1545: UL MU-MIMO 8Rx The number of RX antennas is taken into account for allocation of cells to pools and pool resources to cells. The following 4x2 MIMO, 4x4 MIMO, and 8-pipe beamforming features are impacted by the LTE2912 feature, from the SW capacity point of view: – – – – – – – – – – – –

LTE568: DL Adaptive Closed Loop MIMO (4x2) LTE569: Downlink Adaptive Closed Loop SU-MIMO 4x4 – TM 4 LTE1987: Downlink Adaptive Closed Loop SU MIMO (4x4) LTE493: TDD Beamforming LTE541: Dual Stream Beamforming LTE1025: DL Beamforming Inter-cell Interference Generation LTE1013: Dynamic Transmission Mode Switch LTE1169: DL TM8 Based Dual User Single Layer MU-MIMO LTE1543: 8x2 SU MIMO with TM9 LTE1787: TM9 with 8TX MU-MIMO and Up to 2 Layers Overall LTE1545: UL MU-MIMO 8Rx LTE2068: DL SU MIMO (8x4) with TM9

Impact on interfaces The LTE2912: TD-LTE Baseband Pooling feature has no impact on interfaces. Impact on network management tools The LTE2912: TD-LTE Baseband Pooling feature has no impact on network management tools. Impact on system performance and capacity The advantage of the LTE2912: TD-LTE Baseband Pooling feature is that high-loaded cells can make use of unused resources from low-loaded cells of the same baseband pool, thereby increasing the overall system capacity and performance. The more unbalanced the load on an eNB is, the bigger the gain in system capacity and performance.

Issue: 01

© 2017 Nokia

43



On the other hand, since the baseband pool resources are dynamically or semidynamically assigned to the cells of a baseband pool, it is no longer necessary to permanently allocate all required cell resources to all cells of a baseband pool. As a result, this feature enables increasing the number of cells per eNB. If a cell's resources and/or individual UE resources are reduced due to exhausted Cplane and U-plane pool resources, the end-to-end performance may be degraded as the cell or user does not get all the resources they would have if baseband pooling was switched off.



FDD

TDD

System release

not supported

TD-LTE 17A


not supported

not supported


not supported

not supported

Nokia AirScale BTS

not supported

TL17A

Flexi Zone BTS

not supported

not supported


not supported

not supported


not supported

not supported

OMS

not supported

support not required

NetAct

not supported

17.2

MME

not supported


SAE GW

not supported


UE

not supported

3GPP R8 mandatory

Alarms There are no alarms related to the LTE2912: TD LTE Baseband Pooling feature. BTS faults and reported alarms Table 15 Fault ID

New BTS faults introduced by LTE2912 Fault name


Alarm name

4377

Dynamic Pool Resources Not Sufficient To Setup Cell

7653

CELL FAULTY

4378

Dynamic Pool Resources Pernamently Not Available

7653

CELL FAULTY

For fault descriptions, see TD-LTE BTS Alarms and Faults.

44

© 2017 Nokia

Issue: 01



Commands There are no commands related to the LTE2912: TD-LTE Baseband Pooling feature. Measurements and counters Table 16

New counters introduced by LTE2912

Counter ID

Counter name

Measurement

M8018C10

Number of admission control rejections in a cell due to Cplane cell pool limits

LTE eNB Load

M8055C0

Number of admission control rejections for RRC connections in a cell per U-plane pool

LTE Baseband Pool Monitoring

M8055C1

Number of admission control rejections for E-RAB setup attempts in a cell per U-plane pool


M8055C2

Number of admission control rejections for GBR E-RAB setup attempts in a cell per U-plane pool


M8055C3

Number of admission control rejections for SCell configuration attempts in a cell per U-plane pool


For counter descriptions, see LTE Performance Measurements and Key Performance Indicators. Key performance indicators There are no key performance indicators related to the LTE2912: TD-LTE Baseband Pooling feature. Parameters Table 17

New parameters introduced by LTE2912

Full name

Issue: 01

Abbreviated name

Managed object

FDD/TDD

BBMOD

-

TDD

LNBTS

-

TDD

bbPoolAllocPrioL ist

LNBTS

-

TDD

LNBTS

Baseband pool allocation priority list

TDD

Amount of baseband pools being used per baseband card

bbCardUsage

Activate baseband pooling

actBbPooling

Baseband pool allocation priority list Allocation criterion

allocCriterion

© 2017 Nokia

Parent structure

45


Table 17


New parameters introduced by LTE2912 (Cont.)

Full name

Abbreviated name

Managed object

Parent structure

FDD/TDD

(bbPoolAllocP rioList)

LNBTS

Baseband pool allocation priority list (bbPoolAllocP rioList)

TDD

bbPoolEvalPeriod LNBTS

-

TDD

LNBTS

-

TDD

Baseband pool allocation mode

bbPoolAllocMode BBPOOLA LLOC

TDD

Target baseband pool ID

bbPoolTargetId

BBPOOLA LLOC

TDD

Hosting baseband pool ID

hostingBbPoolId BBPOOLA LLOC

TDD

Baseband pool allocation identifier

bbPoolAllocId

BBPOOLA LLOC

TDD

Baseband pool logical group ID

bbPoolLogicalGro upId

BBPOOLA LLOC

TDD

Min number emergency sessions

minNumEmergencyS essions

MPUCCH _TDD

-

TDD

Min number RRC

minNumRrc

MPUCCH _TDD

-

TDD

Min number RRC No DRB

minNumRrcNoDrb

MPUCCH _TDD

-

TDD

allocPriority

Evaluation period of the pool resources Minimum of baseband pool resources

bbPoolMinResourc e

Table 18


Full name

46

Allocation priority

Abbreviated name

Managed object

Validate plan against detected hardware

validatePlanAgains tDetectedHW

Activate Centralized RAN

actCRAN

Activate enhanced AC and GBR services

actEnhAcAndGbrServ ices

Activate loadbased PUCCH region

actLbPucchReg

© 2017 Nokia

Parent FDD/TD structur D e

MRBTS

-

TDD

LNBTS

-

TDD

LNBTS

-

TDD

APUCCH

-

TDD

Issue: 01


Table 18


Existing parameters related to LTE2912 (Cont.)

Full name

Abbreviated name

Activation of automatic PUCCH allocation

actAutoPucchAlloc

Activate supercell configuration

actSuperCell

Managed object

Parent FDD/TD structur D e

LNCEL_TDD

-

TDD

LNCEL_TDD

-

TDD

For parameter descriptions, see TD-LTE BTS Parameters. Sales information Table 19



License control

BSW

SW Asset Monitoring


No

5.5 Activating LTE2912 Before you start •


• •

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

Feature interdependencies see LTE2912 system impact Preconfiguration – –

Nokia AirScale BTS is required. The MRBTS ► LNBTS ► LNCEL ► BBPOOLALLOC object is configured.

Procedure

1

Issue: 01


© 2017 Nokia

47


2





3


4


5

Set the Activate baseband pooling (actBbPooling) LNBTS parameter value to true. Ensure that • •

Amount of baseband pools being used per baseband card (bbCardUsag) BBMOD Evaluation period of the pool resources (bbPoolEvalPeriod)

LNBTS •

Minimum of baseband pool resources (bbPoolMinResource)

LNBTS •

Activate load-based PUCCH region (actLbPucchReg)

APUCCH_TDD •

Activation of automatic PUCCH allocation (actAutoPucchAlloc) LNCEL_TDD

parameters are configured as required.

6




48


© 2017 Nokia

Issue: 01




Result An automatic procedure for baseband pool assignment is initiated for the entire eNB. The operator will be warned if there are more cells configured than can be supported.



•

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

Preconfiguration Baseband pooling is enabled (the Activate baseband pooling (actBbPooling) LNBTS parameter has the value true.

Procedure

1


2




3


4


Issue: 01

© 2017 Nokia

49



5

Set the Activate baseband pooling (actBbPooling) LNBTS parameter value to false.

6






Result Baseband pooling is disabled, and new resources are allocated based on active legacy features. The operator will be warned if there are more cells configured than can be supported.

50

© 2017 Nokia

Issue: 01


LTE3011: Flexi Zone Intra-FZM and Intra-FZAP uplink 2CC carrier aggregation

6 LTE3011: Flexi Zone Intra-FZM and Intra-FZAP uplink 2CC carrier aggregation Benefits, functionality, system impact, reference data, instructions of the feature The LTE3011: Flexi Zone Intra-FZM / Intra-FZAP uplink 2CC carrier aggregation feature provides uplink carrier aggregation operation with one Flexi Zone Micro BTS to provide up to 40 MHz channel bandwidth in the uplink. The LTE3011 feature introduces this functionality for both FDD and TDD. Note that mixed UL CA (between FDD and TDD) is not supported.

6.1 LTE3011 benefits The LTE3011: Flexi Zone Intra-FZM / Intra-FZAP uplink 2CC carrier aggregation feature allows operators to increase UE peak UL data rate.

6.2 LTE3011 functional description The main features of the LTE3011: Flexi Zone Intra-BTS uplink 2CC carrier aggregation are as follows: • • • • • •

support for up to 2x20 MHz uplink carrier aggregation for two component carriers with up to 40 MHz combined bandwidth support of a mix of non-carrier aggregration UEs and carrier aggregation (downlink only or downlink and uplink) UEs PUCCH is transmitted on the Primary Cell (PCell) only PCell for uplink carrier aggregation is the same as the PCell for downlink carrier aggregation secondary Cell (SCell) for uplink carrier aggregation is a subset of SCells for downlink carrier aggregation can only be configured on a single stand-alone micro/pico, or on an individual FZAP under the Flexi Zone Controller

The following are known supported band combinations supported by TDD Flexi Zone micro/pico described by 3GPP TS 36.200: •

band 38 + band 38

•

band 40 + band 40 band 41 + band 41

•

Note that the FDD band combinations are the same as Flexi Zone micro/pico hardware platforms supported by feature LTE2629. The two aggregated uplink carriers are intra band contiguous and non-contiguous carriers. These two aggregated uplink carriers must be from the same eNode B/FZAP. The supported cell bandwidth commbinations are: •

Issue: 01

20 MHz + 20 MHz

© 2017 Nokia

51


• • • •

20 MHz 20 MHz 15 MHz 10 MHz


+ 10 MHz + 15 MHz + 10 MHz + 10 MHz

The two intra band component carriers use the same TDD frame configuration and special sub frame configuration. The LTE3011 feature does not introduce any specific limitation with regards to supported bands' combinations. Limitations are related only to available hardware. The following functional extensions are: • • •

Radio Admission control UEs are addmitted based on the PCell admission control settings same thresholds as for non-carrier aggregation capable UEs are applied PCell of uplink carrier aggregation is the same as PCell UE used for downlink carrier aggregation

The following performance counters are supported per cell: • • • • • •

average number of uplink carrier aggregation capable UEs for two component carriers number of SCell configuration attempts with uplink carrier aggregation number of successful SCell configurations with uplink carrier aggregation average number of uplink carrier aggregation EUs with one configured SCell average number of uplink carrier aggregation UEs with one activated SCell PCell RLC data volume in UL via one or more SCells.

The functionality of feature LT3011 can be enabled or disabled per eNode B by an O&M setting, and can only be enabled if downlink carrier aggregation is enabled.

6.3 LTE3011 system impact Interdependencies between features The following features must be activated before activating the LTE3011: Flexi Zone IntraBTS uplink 2CC carrier aggregation feature: •

•

•

•

52

LTE2629: FDD-LTE Dual Carrier (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS The LTE3011 feature uses the LTE2629 feature as downlink carrier aggregation base for uplink carrier aggregation functionality in FDD; LTE3011 uses Digital Signal Processor (DSP) deployment of this feature as the only DSP deployment in FDD. LTE1092: Uplink carrier aggregation - 2 CC The LTE3011 feature reuses the functionality of LTE1092 in FDD. LTE1850: TDD Intra-band Dual Carrier Operation within a Flexi Zone Micro BTS and LTE1896: TDD Intra-band Dual Carrier Downlink Aggregation for Flexi Zone Micro The LTE3011 feature uses features LTE1850 and LTE1896 as downlink carrier aggregation base for uplink carrier aggregation functionality in TDD; LTE3011 uses DSP deployment of this feature as the only DSP deployment in TDD. LTE2105: TDD Uplink into band carrier aggregation - 2CC and LTE2416: TDD Uplink 2CC carrier aggregation extension

© 2017 Nokia

Issue: 01



The LTE3011 feature reuses the functionality of features LTE2105 and LTE2416 in TDD. The following features must be deactivated before activating the LTE3011: Flexi Zone Intra-BTS uplink 2CC carrier aggregation feature: LTE-U feature suite LTE2959: Flexi Zone Single Frequency Network Support (TDD)

• •

Impact on interfaces The LTE3011: Flexi Zone Intra-BTS uplink 2CC carrier aggregation feature has no impact on interfaces. Impact on network management tools The LTE3011: Flexi Zone Intra-BTS uplink 2CC carrier aggregation feature has no impact on network management tools. Impact on system performance and capacity The LTE3011: Flexi Zone Intra-BTS uplink 2CC carrier aggregation feature has impact on system performance and capacity: single-UE peak UL throughput and cell average UL throughput are impacted (potentially, KPI-related constraints similar to what is observed in DL CA, will be applicable also in UL CA).



FDD

TDD

System release

FDD-LTE 17SP

TD-LTE 17A


Not supported

Not supported


Not supported

Not supported

Nokia AirScale BTS

Not supported

Not supported

Flexi Zone BTS

FL17SP

TL17A


FL17A

TL17A


FL17A

TL17A

OMS



NetAct



MME



SAE GW



UE



Alarms LTE3011: Flexi Zone Intro-BTS uplink 2CC carrier aggregation feature reuses alarms defined by legacy features.

Issue: 01

© 2017 Nokia

53



BTS faults and reported alarms LTE3011: Flexi Zone Intro-BTS uplink 2CC carrier aggregation feature reuses faults and reported alarms defined by legacy features. Commands LTE3011: Flexi Zone Intro-BTS uplink 2CC carrier aggregation feature reuses commands defined by legacy features. Measurements and counters LTE3011: Flexi Zone Intro-BTS uplink 2CC carrier aggregation feature reuses measurements and counters defined by legacy features. Parameters LTE3011: Flexi Zone Intro-BTS uplink 2CC carrier aggregation feature reuses parameters defined by legacy features. Sales information Table 21



License control


Yes


No

6.5 Activating and configuring LTE3011 Instructions to activate and configure the LTE3011: Flexi Zone Intra-FZM / Intra-FZAP uplink 2CC carrier aggregation feature using the BTS Site Manager

6.5.1

FDD Before you start •


•

Feature interdependencies The following features must be activated before activating the LTE3011: Flexi Zone Intra-FZM / Intra-FZAP uplink 2CC carrier aggregation feature: –

–

•


LTE2629: FDD-LTE Dual Carrier (2x20 MHz) Operation Support on a Single Flexi Zone Micro BTS The LTE3011 feature uses the LTE2629 feature as downlink carrier aggregation base for uplink carrier aggregation functionality in FDD. LTE1092: Uplink carrier aggregation - 2 CC The LTE3011 feature reuses the functionality of LTE1092 in FDD.

Preconfiguration –

FDD downlink carrier aggregation features are activated and the Activation downlink carrier aggregation (actDLCAggr) LNBTS parameter is set to true. of

54

© 2017 Nokia

Issue: 01


– –


CAREL instances for the PCell pointing to SCells are defined. Uplink Carrier The Activation of Aggregation (actULCAggr) LNBTS parameter is set to false.

Procedure

1


2




3


4


5

Set the activation flag, the Activation of Uplink Aggregation (actULCAggr) LNBTS parameter, to UL_CA_with_smartSched.

Carrier

Ensure that •

•

Issue: 01

the Preference for SCell addition (dlCaPreferred) LNBTS is set appropriately. This parameter value is meaningful when N CC DL CA + 2CC UL CA is supported, where N > 2. Otherwise, this parameter can be set to any value. all instances of Nominal bit rate (nbrUl) LNBTS parameter are set to empty value.

6

Configure the Pathloss threshold UE scheduled on single cell (ulCaPathlossThr) LNBTS parameter as desired.

7

Configure the Min UE-AMBR uplink for carrier aggregation (caMinUlAmbr) LNBTS parameter to a desired threshold.

© 2017 Nokia

55



8

Configure the Additional MPR for UL intra-band carrier aggregation (caUlIntraBandAmpr) LNBTS parameter to enable or disable an additional MPR, as required.

9

Ensure that the actUlPwrRestrScn parameter is set to none.






Result The eNB is now supporting UL CA and will enable it if the UE supports it and when an increase in UE's UL traffic requires it.

6.5.2

TDD Before you start •


•

Feature interdependencies The following features must be activated before activating the LTE3011: Flexi Zone Intra-FZM / Intra-FZAP uplink 2CC carrier aggregation feature: –

–

•

56


LTE1850: TDD Intra-band Dual Carrier Operation within a Flexi Zone Micro BTS and LTE1896: TDD Intra-band Dual Carrier Downlink Aggregation for Flexi Zone Micro The LTE3011 feature uses features LTE1850 and LTE1896 as downlink carrier aggregation base for uplink carrier aggregation functionality in TDD. LTE2105: TDD Uplink into band carrier aggregation - 2CC and LTE2416: TDD Uplink 2CC carrier aggregation extension The LTE3011 feature reuses the functionality of features LTE2105 and LTE2416 in TDD.

Preconfiguration

© 2017 Nokia

Issue: 01


–


At least one of the downlink carrier aggregation-related feature is a prerequisite, meaning that the Activation of downlink carrier aggregation (actDLCAggr) LNBTS parameter is set to true and feature is configured.

Procedure

1


2




3


4


5

Set the Activation of uplink carrier aggregation (actULCAggr) value to UL_CA_without_smartSched or UL_CA_with_smartSched. If the Activation of uplink carrier aggregation (actULCAggr) parameter was configured with UL_CA_with_smartSched value, the following parameters require configuring:

•

Pathloss threshold UE scheduled on single cell (ulCaPathlossThr) LNBTS Additional MPR for UL intra-band carrier aggregation (caUlIntraBandAmpr) LNBTS Preference for SCell addition (dlCaPreferred) LNBTS

•

Fast load balancing configuration (fastLoadBalanceConfig)

• •

CAGENB To create this parameter structure, right click on CAGENB managed object and select: New ► Fast load balancing configuration .

Issue: 01

© 2017 Nokia

57


6


Check in LNBTS managed object if the Min UE-AMBR uplink for carrier aggregation (caMinUlAmbr) parameter is set. If not, configure it. This step is applicable only when actULCAggr is set to UL_CA_with_smartSched .

7






Result The LTE3011 feature is activated, UL carrier aggregation is running, the AMBR value is above the threshold and eNB allows UL carrier aggregation for the SCell.

6.6 Deactivating LTE3011 Instructions to deactivate the LTE3011: Flexi Zone Intra-FZM / Intra-FZAP uplink 2CC carrier aggregation feature using the BTS Site Manager

6.6.1

FDD Before you start •


•

Preconfiguration –

58

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

Uplink Carrier The Activation of Aggregation (actULCAggr) LNBTS parameter is set to UL_CA_with_smartSched .

© 2017 Nokia

Issue: 01



Procedure

1


2




3


4


5

Set the activation flag, the Activation of Uplink Aggregation (actULCAggr) LNBTS parameter, to false.

6

Send the commissioning plan file to the BTS.

Carrier

Sub-steps





Result Connected UEs are not reconfigured and continue with uplink carrier aggregation, if supported; however, no uplink carrier aggregation is enabled for new UEs.

Issue: 01

© 2017 Nokia

59


6.6.2


TDD Before you start •


•

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

Preconfiguration – –

The LTE3011 feature is activated and configured. The LTE2959: Flexi Zone Single Frequency Network Support feature is deactivated.

Procedure

1


2




3


4


5

Set the Activation of uplink carrier aggregation (actULCAggr) parameter value to false.

6



60

© 2017 Nokia

Issue: 01






Issue: 01

© 2017 Nokia

61

LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE


7 LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE Benefits, functionality, system impact, reference data, instructions of the feature Table 22 Date of change

July 24, 2017

LTE3020 summary of changes Section

Table 23: LTE3020 hardware and software requirements

Change description

Software release changed to TD-LTE17A.

The LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature introduces an addition of 256 quadrature amplitude modulation (QAM) option in downlink (DL) adaptive modulation and coding (AMC) for the physical downlink shared channel (PDSCH). The 256 QAM option provides higher downlink data rates for supporting user equipment (UE) with corresponding capabilities. The LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature is TD-LTE only.

7.1 LTE3020 benefits The LTE3020 : 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature provides the following benefits: • •

Increased spectral efficiency depending on the 256 QAM area probability and supporting UE distribution Higher downlink peak rates depending on the UE capabilities

7.2 LTE3020 functional description If the LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature is enabled and the UE is 256 QAM capable, the evolved Node B (eNB) configures the UE to apply a dedicated table for the channel quality indicator (CQI) and the modulation and coding scheme (MCS) index in DL adaptation. The eNB indicates the applicability of the CQI table to the UE in the radio resource control (RRC) reconfiguration procedure in case of an initial context setup (ICS), handover (HO), re-establishment, or addition of a secondary cell (SCell). Reconfiguration to the 256 QAM-specific CQI and MCS table requires a transient phase where all data scheduling is done based on the legacy table (conservative approach) and can impact the data rates. Hybrid automatic repeat request (HARQ) retransmissions use the same transport format and MCS as in the initial transmission to maintain the same transport block size (TBS).

62

© 2017 Nokia

Issue: 01


g


Note: In bad channel quality conditions, the coarser granularity of the 256 QAMspecific MCS-to-TBS mapping can reduce data rates and lower the transmission efficiency. To avoid lower transmission efficiency in this case, you can activate the performance monitoring mechanism introduced with LTE3073: 256 QAM Extensions. For performance monitoring mechanism activation and parameter information, see LTE3073: 256 QAM Extensions. The radio frequency (RF) Tx power offset for this feature depends on the hardware variant. During commissioning the Site Validator provides a proper range of Tx offset values (taking into consideration the current antenna power settings) that meet the 3GPP error vector magnitude (EVM) requirements for DL 256 QAM. If needed, one of the offset values must be chosen to apply a proper 256 QAM Tx offset.

g

Note: In cases where a Tx power offset is applied, the cell size may be negatively affected (reduced) due to lower Tx output power used on that cell. In case of carrier aggregation (CA) scenarios, the applicability of 256 QAM is decided on a per component carrier (CC) basis and depends on the feature activation and UE capabilities. The LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature is supported on specific hardware products across the Small Cell platform (for example, Single Band Micro / Pico / Mini-Macro BTSs). Check the product-specific specifications to determine if 256 QAM is supported. The feature can be enabled/disabled per cell by a dedicated operation and maintenance (O&M) setting.

7.3 LTE3020 system impact Interdependencies between features The LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature depends upon the following features: • •

LTE2479: 256 QAM in Downlink LTE3073: 256 QAM Extensions

LTE2479 and LTE3073 provide the software necessary to support LTE3020 on newer Flexi Zone BTS variants. Impact on interfaces The LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature has no impact on interfaces. Impact on network management tools The LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature has no impact on network management tools. Impact on system performance and capacity The LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature impacts system performance and capacity as follows:

Issue: 01

© 2017 Nokia

63


• •


Provides higher downlink data rates for supporting UEs Improves spectral efficiency



System release



Airscale

TD-LTE17A

Not supported

Not supported

Not supported

OMS

UE

NetAct


Not supported Support not required

3GPP R12 UE Support not capabilities required

Flexi Zone Micro BTS

TD-LTE17A


Not supported

MME


SAE GW


Alarms There are no alarms related to the LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature. BTS faults and reported alarms There are no faults related to the LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature. Commands There are no commands related to the LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature. Measurements and counters Table 24 Counter ID

64

Existing counters related to LTE3020 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 256QAMscheduled UE

LTE Cell Resource

© 2017 Nokia

Issue: 01


Table 24 Counter ID

Issue: 01


Existing counters related to LTE3020 (Cont.) Counter name

Measurement

M8011C 201

PDSCH transmission nacks using 16QAM of 256QAMscheduled UE

LTE Cell Resource

M8011C 202


LTE Cell Resource

M8011C 203


LTE Cell Resource

M8011C 204

Failed PDSCH transmission using QPSK of 256QAMscheduled UE

LTE Cell Resource

M8011C 205

Failed PDSCH transmission using 16QAM of 256QAMscheduled 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

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 00Level 15 for 256QAM configured UEs

LTE Power and Quality DL

M8001C 156– M8001C 176

Failed Transmission PDSCH MCS0–MCS20

LTE Cell Load

M8001C 202– M8001C 209


LTE Cell Load

M8001C 242– M8001C 244


LTE Cell Load

M8001C 103– M8001C 131

PDSCH transmission nacks using MCS0–MCS28

LTE Cell Load

© 2017 Nokia

65


Table 24


Existing counters related to LTE3020 (Cont.)

Counter ID

Counter name

Measurement

M8001C 239– M8001C 241

PDSCH transmission nacks using MCS29–MCS31

LTE Cell Load

M8001C 45– M8001C 73

PDSCH transmissions using MCS0–MCS28

LTE Cell Load

M8001C 236– M8001C 238

PDSCH transmissions using MCS29–MCS31

LTE Cell Load

M8012C 27– M8012C 47

MAC PDU volume PDSCH MCS0–MCS20

LTE Cell Throughput

M8012C 81– M8012C 88


LTE Cell Throughput

M8012C 148– M8012C 150


LTE Cell Throughput

M8010C 36– M8010C 51

UE Reported CQI Level 00–Level 15


M8010C 76– M8010C 91

UE Reported CQI Level 0–Level 15 for Codeword 1


M8010C 132M8010C 147

CQI Level 0-Level 15 for Codeword 1 Reported by 256QAM-configured UEs


For counter descriptions, see LTE Performance Measurements . Key performance indicators There are no key performance indicators related to the LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature. Parameters

66

© 2017 Nokia

Issue: 01


Table 25


Existing parameters related to LTE3020 Full name

Abbreviated name

Managed object

Activate modulation scheme DL

actModulationSche MRBTS/L meDl NBTS/LN CEL

Cell power reduce (1)

dlCellPwrRed (1)

Cell power reduction for MBMS transmission

cellPwrRedForMBMS MRBTS/L NBTS/LN CEL

Parent structure

-

MRBTS/L NBTS/LN CEL -

(1)

The Cell power reduce (dlCellPwrRed) parameter value depends on the hardware variant and the carrier power level that is set. For parameter descriptions, see LTE Radio Access Operating Documentation/Reference/Parameters . Sales information Table 26




License control

Pool license


No

7.5 Activating LTE3020 Instructions to activate the LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TDLTE feature using the BTS Site Manager Before you start

g

Note: The LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature is activated together with LTE2479: 256 QAM in Downlink . •

Prerequisites –

The LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE and LTE2479: 256 QAM in Downlink features are not activated in the cell.

Procedure

1

Issue: 01


© 2017 Nokia

67


2



a) Select View ► Commissioning or click Commissioning on the View Bar on the left. The BTS Site check box, located in the Target section, is selected by default. This is the recommended setting.


3


4

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

5

g

Set the actModulationSchemeDl value to 256QAM. Note: The actDl256QamChQualEst parameter must be set to TRUE or FALSE to enable or disable the performance monitoring mechanism introduced with LTE3073: 256 QAM Extensions. Any errors associated with setting this parameter must be resolved before proceeding. Changing actModulationSchemeDl may also require changing dlCellPwrRed. If an error is reported for dlCellPwrRed, resolve this error by choosing one of the proposed values before proceeding.

6






68

© 2017 Nokia

Issue: 01



Result 256 QAM service is activated and used in the cell.

7.6 Deactivating LTE3020 Instructions to deactivate the LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TDLTE feature using the BTS Site Manager Before you start The LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE feature is deactivated together with LTE2479: 256 QAM in Downlink . •


The LTE3020: 256 QAM in Downlink for Flexi Zone BTS on TD-LTE and LTE2479: 256 QAM in Downlink features are activated in the cell.

Procedure

1


2




3


4


5

Issue: 01

Set the actModulationSchemeDl value to QPSK, 16QAM, or 64QAM.

© 2017 Nokia

69


6







Result 256 QAM service is deactivated and not used in the cell.

70

© 2017 Nokia

Issue: 01


LTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations – II

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.

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.

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 Mhz) Band Mhz) Band Mhz) Band Band

1 (FDD 5/10/15/20 Mhz) + Band 42 (TDD 20 Mhz) + Band 42 (TDD 20 3 (FDD 5/10/15/20 Mhz) + Band 41 (TDD 20 Mhz) + Band 41 (TDD 10/20 3 (FDD 5/10/15/20 Mhz) + Band 41 (TDD 10/20 Mhz) + Band 42 (TDD 20 8 (FDD 5/10 Mhz) + Band 41 (TDD 20 Mhz) + Band 41 (TDD 10/20 Mhz) 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.

Issue: 01

© 2017 Nokia

71



The transmission mode 3 (TM 3), TM 4, or TM 9 can be configured for site configurations as required. TDD frame configuration 1 or 2 is supported in TDD cells and is used with TDD component carriers (CCs).

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.



72

FDD

TDD

System release

FDD-LTE 17A

TD-LTE 17A


FL17A

TL17A


Not supported

TL17A

Nokia AirScale BTS

Not supported

Not supported

Flexi Zone BTS

Not supported

Not supported


Not supported

Not supported


Not supported

Not supported

OMS



NetAct



© 2017 Nokia

Issue: 01


Table 27



FDD

TDD

MME



SAE GW



UE

3GPP R12-14 UE capabilities

3GPP R12-14 UE capabilities

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 28




Issue: 01

License control

Pool license

© 2017 Nokia


No

73

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


9 LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) Table 29

Summary of changes

Date of change

28.06.2017

Section

Functional description

Change description

Infromation on automatic timezones migration to proper IANA timezone entries was added.

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).

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.

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.

74

© 2017 Nokia

Issue: 01



To obtain the correct timezone information for a particular BTS, the BTS utilizes the value of Time Zone (timeZone) parameter , and maps this parameter's value to an entry in the IANA timezone database. Some of the existing timezone values in the timeZone did not map to IANA timezone entries. To mitigate this issue, since LTE17SP a code is introduced to automatically migrate "invalid" timeZone entries to valid ones. The migrated values are: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

Issue: 01

17: (GMT-10) SystemV/HST10 migrated to 10: (GMT-10) Etc/GMT+10 28: (GMT-9) SystemV/YST9 migrated to 26: (GMT-9) Etc/GMT+9 29: (GMT-9) SystemV/YST9YDT migrated to 26: (GMT-9) Etc/GMT+9 44: (GMT-8) SystemV/PST8 migrated to 39: (GMT-8) Etc/GMT+8 45: (GMT-8) SystemV/PST8PDT migrated to 39: (GMT-8) Etc/GMT+8 67: (GMT-7) SystemV/MST7 migrated to 61: (GMT-7) Etc/GMT+7 68: (GMT-7) SystemV/MST7MDT migrated to 61: (GMT-7) Etc/GMT+7 103: (GMT-6) SystemV/CST6 migrated to 99: (GMT-6) Etc/GMT+6 104: (GMT-6) SystemV/CST6CDT migrated to 99: (GMT-6) Etc/GMT+6 150: (GMT-5) SystemV/EST5 migrated to 147: (GMT-5) Etc/GMT+5 151: (GMT-5) SystemV/EST5EDT migrated to 147: (GMT-5) Etc/GMT+5 200: (GMT-4) SystemV/AST4 migrated to 198: (GMT-4) Etc/GMT+4 201: (GMT-4) SystemV/AST4ADT migrated to 198: (GMT-4) Etc/GMT+4 1: (GMT-11) MIT migrated to 0: (GMT-11) Etc/GMT+11 21: (GMT-9) AST migrated to 26: (GMT-9) Etc/GMT+9 41: (GMT-8) PSTmigrated to 39: (GMT-8) Etc/GMT+8 66: (GMT-7) PNT migrated to 61: (GMT-7) Etc/GMT+7 93: (GMT-6) CST migrated to 99: (GMT-6) Etc/GMT+6 148: (GMT-5) IET migrated to 147: (GMT-5) Etc/GMT+5 199: (GMT-4) PRT migrated to 198: (GMT-4) Etc/GMT+4 203: (GMT-4.5) CNT migrated to 202: (GMT-4.5) America/St_Johns 205: (GMT-3) AGT migrated to 239: (GMT-3) Etc/GMT+3 237: (GMT-3) BET migrated to 239: (GMT-3) Etc/GMT+3 318: (GMT+1) ECT migrated to 319: (GMT+1) Etc/GMT-1 352: (GMT+2) ART migrated to 377: (GMT+2) Etc/GMT-2 374: (GMT+2) CAT migrated to 377: (GMT+2) Etc/GMT-2 414: (GMT+3) EAT migrated to 415: (GMT+3) Etc/GMT-3 435: (GMT+4) NET migrated to 428: (GMT+4) Etc/GMT-4 449: (GMT+5) PLT migrated to 446: (GMT+5) Etc/GMT-5 453: (GMT+5.5) IST migrated to 450: (GMT+5.5) Asia/Calcutta 464: (GMT+6) BST migrated to 465: (GMT+6) Etc/GMT-6 482: (GMT+7) VST migrated to 480: (GMT+7) Etc/GMT-7 507: (GMT+8) CTT migrated to 508: (GMT+8) Etc/GMT-8 519: (GMT+9) JST migrated to 518: (GMT+9) Etc/GMT-9 523: (GMT+9.5) ACT migrated to 527: (GMT+9.5) Australia/North 530: (GMT+10) AET migrated to 545: (GMT+10) Etc/GMT-10 561: (GMT+11) SST migrated to 555: (GMT+11) Etc/GMT-11 570: (GMT+12) NST migrated to 568: (GMT+12) Etc/GMT-12

© 2017 Nokia

75



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

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

9.4 LTE3056 reference data Requirements

76

© 2017 Nokia

Issue: 01


Table 30


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

FDD

TDD

System release

FDD-LTE 17

TDD-LTE 17A


FL17

TL17A


Not supported

TL17A

Nokia AirScale BTS

FL17

TL17A

Flexi Zone BTS

FL17A

TL17A


FL17A

TL17A


FL17A

TL17A

OMS



NetAct

NetAct 17.2

NetAct 17.2

MME



SAE GW



UE



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. 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 31

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

Full name Activate GPS and UTC Time Broadcast

Issue: 01

Abbreviated name

Manage d object

actUTCBroadcas t

LNBTS

© 2017 Nokia

Parent structure -

FDD/TDD

common

77


Table 32


Parameters modyfied by LTE3056: GPS and UTC Time Information Broadcast Support (SIB16)

Full name

Abbreviated name

Manage d object

System Information Scheduling List, extended for SIB16

sibSchedulingL ist

SIB

-

common

Indicates which SIB is contained in the SI-Message, extended for SIB16

siMessageSibTy pe(sibScheduli ngList)

SIB

-

common

Include day light savings time indicator

dayLtIncluded XPARA M

-

common

Local time offset included

ltmOffIncluded XPARA M

-

common

Table 33

FDD/TDD

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

Full name

Abbreviated name

Network synchronization mode

btsSyncMode

Downlink channel bandwidth

dlChBw

Time Zone

timezone

Table 34

Parent structure

Manage d object

BTSSC L

Parent structure

FDD/TDD

-

common

LNCEL_ FDD

common

TIME

common

-

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

Full name

Abbreviated name

Manage d object

Day light savings time indicator

dayLt

SIB

-

common

Local time offset

ltmOff

SIB

-

common

Parent structure

FDD/TDD

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

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



78

License control

Pool license

© 2017 Nokia


No

Issue: 01




Procedure notifications – –

•

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

•

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.

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 – –

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.

Procedure

1


2



Issue: 01

© 2017 Nokia

79




3


4


5

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

6

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

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. From version FL17SP onwards these parameters are unmodifiable, the values are set by the system.






80

© 2017 Nokia

Issue: 01



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


•

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 – –

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.

Procedure

1


2




3


4


5

Issue: 01

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

© 2017 Nokia

81


6







Result The SIB16 broadcasting is stopped in all eNB cells.

82

© 2017 Nokia

Issue: 01


LTE3071: NB-IoT Inband

10 LTE3071: NB-IoT Inband Table 36

LTE3071 summary of changes

Date of change

Section

07.07.2017

Feature Activation Instruction

24.07.2017

Reference Data

Change description

Added to the documentation. Updated BTS faults, counters, and KPIs.

The LTE3071: NB-IoT Inband feature introduces a new cellular technology standard for narrowband Internet of Things (NB-IoT) by providing a wide-area coverage for the IoT, which is an interconnected network of devices, such as machines, vehicles, or buildings.

10.1 LTE3071 benefits The LTE3071: NB-IoT Inband feature provides the following benefits: • •

• •

Allows for using low cost UEs with the calculated bitrate up to 21 kbps in uplink and 170 kbps in downlink. Extends the UE's battery lifetime by managing the data transmission - the UE is only either receiving or transmitting at a time (half duplex scheduling) and first-come, firstserved principle is followed in scheduling. Preserves orthogonality with adjacent LTE physical resource blocks (PRBs). Legacy network can be seamlessly migrated by means of software upgrade and allows for serving of NB-IoT devices.

10.2 LTE3071: NB-IoT Inband functional description NB-IoT introduction The Internet of Things (IoT) is a system of interrelated UEs, for example computing devices, vehicles, machines, and other objects provided with unique identifiers and the ability to transfer data over a network without human interaction. The term narrowband (NB) denotes a solution implemented in telecommunication technologies to carry data on a limited number of frequency sets. The size of the message sent in a narrowband mode utilizes less bandwidth than the cumulative bandwidth of the underlying channel. There are three types of NB-IoT in use: • • •

Issue: 01

In-band - through flexible use of a part of an LTE carrier Stand-alone - replacing a GSM or a WCDMA carrier with an NB-IoT carrier Guard band – utilizing the guard band of an LTE carrier

© 2017 Nokia

83



Figure 6

Types of NB-IoT

T o I B N

T o I B N

T o I B N

LTE carrier

GSM/WCDMA carriers

LTE carrier

In-band

Stand-alone

Guard band

NB-IoT is designed to operate in the E-UTRA bands 1, 2, 3, 5, 8, 12, 13, 17, 18, 19, 20, 26, 28 and 66. Feature introduction and main characteristics The LTE3071: NB-IoT Inband feature introduces an inband NB-IoT deployment, where a hosting wideband LTE cell dedicates one physical resource block (PRB) for NB-IoT use. The feature allows for configuration of only one narrowband NB-IoT carrier in an existing LTE host cell as an inband cell. This feature introduces a 3GPP Release 13 functionality for NB-IoT and aims to facilitate low cost UEs, reuse of LTE infrastructure, and low data transfer rates per UE. The antenna configuration of an NB-IoT cell is related to the configuration of the host cell. The NB-IoT cell only supports the 2Tx/2Rx antenna configuration for up to three cells per system module, with the host cell configuration deployment between 5 and 20 Mhz. The main physical characteristics of an NB-IoT carrier are: • •

Downlink (DL) – orthogonal frequency-division multiple access (OFDMA) with 15 KHz subcarrier spacing Uplink (UL) – single-tone OFDMA with 15 kHz carrier spacing

The following new physical channels are introduced for NB-IoT cells: • • • • • • •

g

narrowband narrowband narrowband narrowband narrowband narrowband narrowband

physical broadcast channel (NPBCH) physical downlink shared control channel (NPDSCH) primary synchronization signal (NPSS) secondary synchronization signal (NSSS) physical downlink control channel (NPDCCH) physical random access channel (NPRACH (format 1)) physical uplink shared control channel (NPUSCH)

Note: All new physical channels are described in 3GPP TS 36.211. There is no physical uplink control channel (PUCCH) or physical hybrid-ARQ indicator channel (PHICH) defined for NB-IoT carriers. An explicit HARQ ACK/NACK feedback is applied. The following modulation schemes are supported for NB-IoT: •

84

Downlink NPDSCH: quadrature phase shift keying (QPSK)

© 2017 Nokia

Issue: 01


•


Uplink NPUSCH: binary phase shift keying (BPSK), QPSK (rotated)

The NB-IoT secondary synchronization signal (SSS) always broadcasts the same physical cell ID (PCI) as the hosting wideband LTE cell PCI. Routing to core via S1 interface for NB-IoT can be selected either by a dedicated S1 interface for NB-IoT UEs or by PLMN-based S1 interface selection (inband NB-IoT traffic is directed to the same core as legacy LTE traffic of the hosting cell). The LTE3071 does not support handovers or cell reselection. The inband NB-IoT cell is a sub-item of the hosting LTE cell, which means that NB-IoT cells are not units supported via the X2 interface. The host cell and the inband NB-IoT cell are paired, meaning that all the operations for the host cell or the inband NB-IoT cell such as lock, unlock, or shutdown are executed on the host cell. The operation on the inband NB-IoT cell is prohibited. Only 3GPP control plane solution 2 (data over NAS, as as described in 3GPP TS 23.720) is supported for in NB-IoT cell in the LTE3071 feature. The data transmission is going over signaling radio bearer (SRB). No DRBs are established for NB-IoT UEs. UE inactivity is detected using two timers srbInactivityTimerNB and cpInactivityTimerNB. Expiration of both will transfer UE from connected to idle mode. Scheduler Half duplex scheduling is applied per UE, meaning that any given UE is either only receiving or only transmitting at a time. Because only single tone is supported, there may be up to 11 UEs in the cell simultaneously transmitting in the UL. There can be only one scheduled UE per transmission time interval (TTI) in DL. There is no channel awareness for NB-IoT UEs, therefore to minimize UE battery consumption, 'first-in, first-served' principle is followed in scheduling. QoS differentiation or guaranteed bit rates are not supported. TTI length in DL is 4 ms and in UL is 32 ms. Number of repetitions is the same as in wideband LTE TTI bundling. HARQ feedback is only given after the repetition cycle has been completed. Cell settings The hosting cell has to be configured in such a way that a selected NB-IoT PRB does not hit the physical uplink control channel (PUCCH) or physical random access channel (PRACH) area. The host cell will not use the PRB reserved for an inband NB-IoT cell. It ensures that in the UL, PUCCH area expansions are not overlapping with a configured NB-IoT PRB. Only a short cyclic prefix is allowed. In the LTE3071 feature only one PRB is assigned for inband NB-IoT cell in downlink, which is used for NPBCH/NPSSS/NSSS/NPDCCH/NPDSCH transmission. If PDSCH masking is enabled, the NB-IoT PRB must be included into the PDSCH masking area. Dedicated power settings can be applied to the NB-IoT resource elements. The limits for the DL power offset can be a maximum of 6 dB over wideband LTE PRBs (see Table 37: Examples of DL power settings for the NB-IoT cell). DL and UL power settings can be configured separately. The DL power control is not required, but a static configurable Tx power is used by the eNB instead. The open-loop power control is supported in UL.

Issue: 01

© 2017 Nokia

85



Table 37

Examples of DL power settings for the NB-IoT cell

Host cell bandwidth

NB-IoT cell settings

5MHz

inbandPRBIndexDL=17

dlPwrBoost=3dB

5MHz

inbandPRBIndexDL=17

dlPwrBoost=6dB

10MHz

inbandPRBIndexDL=9

dlPwrBoost=3dB

10MHz

inbandPRBIndexDL=9

dlPwrBoost=6dB

15MHz

inbandPRBIndexDL=47

dlPwrBoost=6dB

20MHz

inbandPRBIndexDL=96

dlPwrBoost=6dB

The position of UL inband NB-IoT can be configured from any UL PRB by using one of the following methods: • •

Select PRB that is included into PUCCH blanking area. The sounding reference signal (SRS) can be deployed on outer region by PUCCH blanking. Select PRB that is included into PUSCH masking area.

g

Note: For the LTE3071: NB-IoT Inband feature, the UL and DL PRB position needs to be configured separately. The UL PRB position should avoid the UL bandwidth fragments.

g

Note: The UL and DL absolute radio-frequency channel numbers (ARFCNs) for inband NB-IoT are calculated according to the host cell ARFCN, together with UL and DL PRB selected for inband NB-IoT. The inband NB-IoT cell can share radio frequency (RF) with GSM or WCDMA, only if normal RF sharing is supported for the hosting LTE cell itself. Usage of interfaces NB-IoT cells deployed by the LTE3071: NB-IoT Inband feature support two system information broadcasts (SIBs) of a narrowband master information block (MIB-NB). These are SIB1-NB and SIB2-NB, carried over NB-IoT PRB and are described in 3GPP TS 36.331. In the NB-IoT cell, the UE does not read any information from the hosting LTE cell. All UEs connected to wideband LTE or NB-IoT share a common maximum number of available RRC-connected users in the cell. The maximum number of available RRCconnected states for the NB-IoT cell is 420. This value is operator-configurable, separately from the host cell.

10.3 LTE3071 system impact Interdependencies between features The following features must be deactivated before activating the LTE3071: NB-IoT Inband feature: • •

86

LTE1113: eICIC LTE1117: LTE MBMS

© 2017 Nokia

Issue: 01


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


LTE1496: eICIC - micro LTE1542: FDD Supercell LTE1709: Liquid Cell LTE1900: Centralized RAN LTE2291: CRAN support for Carrier Aggregation LTE2470: Centralized RAN CL16 Release LTE2564: Centralized RAN CL16A Release LTE3264: Additional PRS Subframe Configurations LTE3268: Combined Supercell for HetNet LTE1834: LTE MBMS Service Continuity LTE3199: eMBMS in Multi-carrier Deployment and Multiple MBSFN Areas Support LTE3200: Dynamic Allocation of eMBMS Resources LTE3201: eMBMS in RAN Sharing Deployment Support LTE819: DL Inter-cell Interference Generation LTE1891: eNodeB Power Saving – Micro DTX LTE2091: FDD SuperCell Extension LTE2445: Combined Supercell LTE2465: CSG Cell Support LTE2605: 4Rx Diversity 20 MHz LTE2115: Dual Transmission Mode 1 Operation

The LTE3071: NB-IoT Inband feature impacts the following features: • • • •

•

•

• • • • • •

Issue: 01

LTE2180: FDD-TDD Downlink Carrier Aggregation 2CC LTE2270: LTE TDD+FDD Inter eNB CA Basic BTS Configurations LTE2316: FDD-TDD Downlink Carrier Aggregation 3CC LTE2337: FDD-TDD Downlink Carrier Aggregation 3CC - 2 FDD & 1 TDD FDD+TDD CA is not supported due to conflicting requirements on DSP deployment in eNB FDD. Please note that FDD CA features using the same activation flag are supported. LTE2839: eMBMS Enhancements for Public Safety eMBMS cannot co-exist on cells which has NB-IoT turned ON (no MBSFNCEL) instance. LTE3128: LTE-M NB-IoT and Cat-M can be enabled in the same 10 MHz cell on the eNB if the LTE3819: IoT: Cat-M and NB-IoT on same frequency carrier feature is enabled. Otherwise, NB-IoT and Cat-M can be enabled in different cells on one eNB. LTE2185: Multi-cell Coordinated Scheduler with Flexi Zone This feature is not supported because DL CoMP is not supported for NB-IoT. LTE2754: Frequency Bands Priority Change in Mfbi NB-IoT does not support frequency band priority. LTE2291: Support for Carrier Aggregation on CL16A Release Carrier Aggregation (CA) is not supported by NB-IoT. LTE2206: Extended RLF Handling This function is not supported by NB-IoT. LTE1456: Test Model Support for Energy Efficiency ETSI TS 102 706 This function is not supported by NB-IoT. LTE430: DL Power Boosting for Control Channels

© 2017 Nokia

87


• •

• •

• • • • • • •

•

• •

• •

•

88


This function is not supported by NB-IoT. LTE1111: Inter Cell Load Generation for PDCCH This function is not supported by NB-IoT. LTE72: 4-way RX Diversity LTE3071 supports only 2-way TX/RX therefore this feature is not supported. Moreover, the host LTE cell cannot use LTE72 function. LTE71: 2-way RX Diversity (MRC) The MRC for two antenna ports functionality is supported by NB-IoT. LTE51: Cell Selection and Re-selection The cell selection function is supported by NB-IoT. Neither intra-freqency cell reselection nor inter-freqency cell re-selection is supported by NB-IoT. LTE49: Paging The paging function is not supported in the NB-IoT cell. LTE735: RRC Connection Re-establishment This function is not supported by NB-IoT. LTE2224: Uplink Triggered Mobility This function is not supported by NB-IoT. LTE2551: RSRQ Based A5 This function is not supported by NB-IoT. LTE829: Increased Uplink MCS Range The usage of MCS21 to MCS24 is not supported by NB-IoT. LTE2583: Support of High Power UE This function is not supported by NB-IoT. LTE2612: ProSe Direct Communications for Public Safety NB-IoT UEs do not have the capability of ProSe Direct Communications. The LTE2612: ProSe Direct Communications for Public Safety feature is not supported in an NB-IoT cell. In UL, the NB-IoT PRB are not overlapping with portion of UL PRBs for ProSe Direct Communication Sidelink Transmit Resource Pool in the host cell. LTE944: PUSCH Masking This function is not supported by NB-IoT. The LTE944 feature is not supported in an NB-IoT cell because there is only one PRB in an inband NB-IoT cell. LTE944 can be supported in a host cell. If LTE944 is enabled in host cell, then inband NB-IoT PRB must be in the PRB masking region and cannot be blanked by UL scheduler. Alternatively, NB-IoT PRB can be in all regions except PUCCH PRBs and PRACH region. The NB-IoT scheduler and UL scheduler work independently. LTE1336: Interference Aware UL Power Control Closed-loop uplink power control is not supported in NB-IoT. LTE1800: Downlink Interference Shaping LTE1800 can be supported in a host cell and by NB-IoT. The NB-IoT resource block group (RBG) must be in the blanked PDSCH region if PDSCH masking enabled in LTE1800 . LTE1042: Nominal Bitrate for Non-GBR Bearers This function is not supported by NB-IoT. LTE2023: User Plane Overload Handling Only one NB-IoT UE per TTI for UL or DL is scheduled. Only TM2 is supported. An NB-IoT UE does not support measurement reporting. The only current trigger that will be extended to NB-IoT UEs is the number of RRC connections. LTE786: Flexible UL Bandwidth

© 2017 Nokia

Issue: 01


• • • • •

•


This function is not supported by NB-IoT. The LTE786: Flexible UL Bandwidth feature can be supported in a wide band host cell. LTE786 can be supported in the host cell. In uplink the inband NB-IoT PRB must be in PUSCH area or PUCCH blanking areas and it cannot be in PUCCH region, PRACH region or sidelink region. LTE581: PRACH Management This function is not supported by NB-IoT. LTE962: RACH Optimization This function is not supported by NB-IoT. LTE69: Transmit Diversity for Two Antennas Only transmission mode 2 is supported for NB-IoT UE. LTE801: Group Hopping for UL Reference Signal This function is not supported by NB-IoT. LTE914: Graceful Cell Shut Down Handover is not possible for NB-IoT UEs to other NB-IoT carriers during graceful shutdown. Mobility for NB-IoT is possible as UE idle mode cell reselection. The inband NB-IoT cell requires graceful shutdown in the host cell and separate inband NB-IoT cell graceful cell shut down is not supported. LTE1949: Extend Power Reduction Range The power of normal LTE cell will be inherited. The NB-IoT power will be set based on the power of normal LTE cell.

The following load-based power saving features are supported however both LTE host cell and NB-IoT cell must be in the same power saving group (PSGRP) and assigned orders together: • •

LTE1103: Load Based Power Saving for Multi-layer Networks LTE1203: Load Based Power Saving

The following features are supported in the host cell with a capacity reduction due to NBIoT: • •

LTE2906: FDD-LTE 17 FSMr3 Capacity and Dimensioning LTE2907: FDD-LTE 17 AirScale Capacity and Dimensioning

C-plane overload is supported by NB-IoT: •

LTE1047: C-plane Overload Handling (I)

The PUCCH function is not supported by inband NB-IoT: • •

LTE1130: Dynamic PUCCH Allocation LTE2664: Load Based PUCCH Region

because the inband NB-IoT PRB position cannot overlap with PRACH and PUCCH for the host cell. The NAICS function is not supported by NB-IoT due to a lack of capability: •

LTE2554: Network Assisted Interference Cancellation and Suppression

•

LTE2652: Common Reference Signal Interference Cancellation

LTE-U is not supported by NB-IoT: • •

Issue: 01

LTE2424 LTE-U (2CC) Support for Dual-Band Indoor/Outdoor FZ BTS (Pre-Rel 13) LTE2675: Unlicensed Spectrum Bandwidth Increase for the LTE-U Support (PreRelease 13)

© 2017 Nokia

89



NB-IoT reuses parts of the following features and adds new functions to them: • •

LTE40: Physical & Transport Channels LTE41: PDCP, RLC & MAC Support

The LTE3071: NB-IoT Inband feature impacts the following features from the MIMO area: • • • •

g

LTE70: Downlink Adaptive Open Loop MIMO for Two Antennas LTE568: DL Adaptive Closed Loop MIMO (4x2) LTE703: DL Adaptive Closed Loop MIMO for Two Antennas LTE1987: Downlink Adaptive Closed Loop SU MIMO (4x4) Note: Only TM2 is supported for the NB-IoT UE.

The LTE3071: NB-IoT Inband feature impacts the following features from the SIB broadcasting functionality area: • •

g

LTE426: System Time Broadcast for SIB8 LTE1635: SIB 8 AC Barring for 1xRTT Note: The transmission of SIB8 messages is not supported by NB-IoT.

•

•

LTE2085: SIB Reception with Parallel Measurement Gaps A connected mode mobility, including a handover and a measurement report, is not supported in NB-IoT. LTE3056: GPS and UTC Time Information Broadcast Support (SIB16) The transmission of SIB16 message is not supported in NB-IoT.

The LTE3071: NB-IoT Inband feature impacts the following features from the QAM modulation area:

•

LTE788: Support of 16 QAM (UL) Only QPSK and BPSK are supported in UL by NB-IoT. LTE2479: 256 QAM in Downlink LTE43: Support of 64 QAM in DL LTE793: Support of 16 QAM (DL)

•

LTE3073: 256 QAM Extensions

• • •

g

Note: Only QPSK is supported in DL by NB-IoT. The LTE3071: NB-IoT Inband feature impacts the following features from the CMAS and ETWS transmission: • • •

g

LTE1755: Multiple Emergency Areas per Cell LTE494: Commercial Mobile Alert System LTE843: ETWS Broadcast Note: The transmission of CMAS and ETWS messages is not supported by NB-IoT.

The LTE3071: NB-IoT Inband feature impacts the following features from the DRX area:

90

© 2017 Nokia

Issue: 01


• • • •

g


LTE1679: DRX with Parallel UE Measurement Gaps A measurement gap is not supported by NB-IoT UEs. LTE42: DRX in RRC Connected Mode LTE473: Extended DRX Settings LTE585: Smart DRX Note: DRX is not supported for NB-IoT UEs. Connected DRX has no value for NB-IoT.

The LTE3071: NB-IoT Inband feature impacts the following features from the UESTATE area: • • • • • • • • • • • • •

g

LTE495: OTDOA LTE1308: MDT Cell Trace Enhancements LTE953: MDT (Minimization of Drive Test) LTE570: Periodic UE Measurements LTE1049: MDT – UE Measurement PLogs LTE1788: Automatic Access Class Barring LTE1074: Multimedia Priority Services LTE1569: QCI1 Specific RLF and Re-establishment Control LTE1898: RRC Connection and UE SCell Context Pre-emption LTE2235: RACH Load Triggered Access Class Barring LTE2460: Automatic Access Class Barring with PLMN Disabling LTE2505: Access Class Barring Skip LTE2823: RRC Connection Triggered Access Class Barring Note: None of these features is supported by NB-IoT.

The LTE3071: NB-IoT Inband feature does not support the following features from the IRC functionality: • • •

LTE936: IRC LTE979: IRC for 2 RX Paths LTE980: IRC for 4 RX Paths

The LTE3071: NB-IoT Inband feature impacts the following features from the link adaptation area: • • • •

g

LTE30: CQI Adaption (DL) LTE767: Support of a Periodic CQI Reports LTE31: Link Adaptation by AMC (UL/DL) LTE1495: Fast Uplink Link Adaptation Note: Only inner link adaptation will be considered for NB-IoT, and other kinds of link adaptations will not be supported. Only the coverage level and uplink received signal level (RXLEV) can be used.

Impact on interfaces The LTE3071: NB-IoT Inband feature impacts interfaces by adding new physical channels that are introduced for NB-IoT cells:

Issue: 01

© 2017 Nokia

91


• • • • • • •

g


narrowband narrowband narrowband narrowband narrowband narrowband narrowband

physical broadcast channel (NPBCH) physical downlink shared control channel (NPDSCH) primary synchronization signal (NPSS) secondary synchronization signal (NSSS) physical downlink control channel (NPDCCH) physical random access channel (NPRACH (format 1)) physical uplink shared control channel (NPUSCH)

Note: All new physical channels are described in 3GPP TS 36.211. Impact on network management tools The LTE3071: NB-IoT Inband feature impacts network management tools as follows: •

Newly added MOCs to BTS SM: – –

MRBTS/LNBTS/LNCEL/NBIOT_FDD MRBTS/LNBTS/NBIOTPR

Impact on system performance and capacity The LTE3071: NB-IoT Inband feature impacts system performance and capacity as follows: • •

The peak throughput of legacy UEs is reduced for host LTE cells, as the NB-IoT PRBs cannot be used for legacy LTE. Average throughput of cells with an enabled NB-IoT feature is lowered because the throughput contribution of NB-IoT UEs is low. Therefore, the contributions of legacy UEs and NB-IoT UEs needs to be determined separately (due to the defined resource split) and summed up afterwards.



92

FDD

TDD

System release

FDD LTE 17A

not supported


FL17A

not supported


not supported

not supported

Nokia AirScale BTS

not supported

not supported

Flexi Zone BTS

FL17A

not supported


FL17A

not supported


FL17A

not supported

OMS

LTE OMS17

not supported

NetAct

17.2

not supported

© 2017 Nokia

Issue: 01


Table 38



g

FDD

TDD

MME


not supported

SAE GW


not supported

UE


not supported

Note: The network must support Control plane Cellular IoT EPS optimization. Alarms There are no alarms related to the LTE3071: NB-IoT Inband feature. BTS faults and reported alarms Table 39

New BTS faults introduced by LTE3071

Fault ID

6264

Fault name


No MME capacity assigned by Core Network

Alarm name

7115

BASE STATION INFORMATION

7651


For fault descriptions, see LTE Radio Access Operating Documentation > Reference > Alarms and Faults Commands There are no commands related to the LTE3071: NB-IoT Inband feature. Measurements and counters Table 40 Counter ID

Issue: 01

New counters introduced by LTE3071 Counter name

Measurement

M8066C 0

Maximum number of RRC connected NB-IoT UEs

LTE NB-IoT

M8066C 1

Sum of RRC Connected NB-IoT UEs

LTE NB-IoT

M8066C 2

Attempted RRC Connection Establishment for NB-IoT UEs

LTE NB-IoT

M8066C 3

Successful RRC Connection Establishment for NB-IoT UEs

LTE NB-IoT

M8066C 4

Attempted UE-associated logical S1-Connection Establishments for NB-IoT UEs

LTE NB-IoT

M8066C 5

Successful UE-associated logical S1-Connection Establishments for NB-IoT UEs

LTE NB-IoT

© 2017 Nokia

93



Table 40

New counters introduced by LTE3071 (Cont.)

Counter ID

Counter name

Measurement

M8066C 6

Denominator for average number of RRC connected NBIoT UEs

LTE NB-IoT

M8066C 7

UE movement to ECM idle state due to user inactivity

LTE NB-IoT

M8066C 8

UE movement to ECM idle state due to insufficient radio resources

LTE NB-IoT

M8066C 9

UE movement to ECM idle state due to detach

LTE NB-IoT

M8066C 10

UE movement to ECM idle state due to normal call release

LTE NB-IoT

M8066C 11

UE movement to ECM idle state (eNB initiated)

LTE NB-IoT

M8066C 12

UE movement to ECM idle state (MME initiated)

LTE NB-IoT

M8066C 13

Aggregated time duration of NB-IoT UEs in battery consumption mode

LTE NB-IoT

M8066C 14

MAC PDU volume in UL for NBIoT UEs

LTE NB-IoT

M8066C 15

MAC PDU volume in DL for NBIoT UEs

LTE NB-IoT

M8066C 16

Number of used NB-IoT UL resources

LTE NB-IoT

M8066C 17

Total number of one millisecond intervals reserved for NB-IoT UEs in UL

LTE NB-IoT

M8066C 18

Used NB-IoT DL resources

LTE NB-IoT

M8066C 19

Available NB-IoT DL resources

LTE NB-IoT

For counter descriptions, see LTE Radio Access Operating Documentation > Reference > Counters and Key Performance Indicators Key performance indicators Table 41

Existing key performance indicators related to LTE3071

KPI ID

94

KPI name

LTE_5060i

E-UTRAN Initial E-RAB Accessibility

LTE_6177a

E-UTRAN Average Session Duration for NB IoT UEs

LTE_6185a

E-UTRAN RRC Connection Setup Attempts for NB IoT UEs

© 2017 Nokia

Issue: 01



For KPI descriptions, see LTE Radio Access Operating Documentation > Reference > Counters and Key Performance Indicators Parameters Table 42


Full name

Issue: 01

Abbreviated name

Managed object

Parent structure

FDD/TDD

Supported LTE cell technology

supportedCellTec hnology

LNBTS

-

FDD

Cell technology

cellTechnology

LNCEL

-

FDD

Instance ID of the assigned NBIOTPR profile

nbIoTProfId

NBIOT_FD D

FDD

Number of Coverage Levels

numCoverageLevel s

NBIOT_FD D

FDD

NB-IoT FDD specific cell identifier

nbIoT_FddId

NBIOT_FD D

FDD


dlChBw

NBIOT_FD D

FDD

Downlink channel power boost for inband NB-IoT

dlPwrBoost

NBIOT_FD D

FDD

NBIoT inband downlink PRB index

inbandPRBIndexDL NBIOT_FD D

FDD

NBIoT inband uplink PRB index

inbandPRBIndexUL NBIOT_FD D

FDD

Max Number RRC

maxNumRrcNB

NBIOT_FD D

FDD

Synchronization signals transmission mode

syncSigTxMode

NBIOT_FD D

FDD

Uplink channel bandwidth

ulChBw

NBIOT_FD D

FDD

Common Search Space profile for NB-IoT normal coverage

cssProfNBNorCov NBIOTPR

Maximum number of repetitions for NPDCCH common search space for RA

npdcchMaxNumRepR a

Offset for NPDCCH Common Search Space

npdcchOffsetRa

-

FDD

NBIOTPR

cssProfNBN orCov

FDD

NBIOTPR

cssProfNBN orCov

FDD

Starting subframes of the NPDCCH Common Search Space for RA

npdcchStartSfRa NBIOTPR

cssProfNBN orCov

FDD

MAC profile for NBIoT normal coverage

macProfNBNorCov NBIOTPR

-

FDD

© 2017 Nokia

95



Table 42


Full name

96

Abbreviated name

Managed object

Parent structure

FDD/TDD

Logical channel SR prohibit timer for NB-IoT

logicalChanSrPro NBIOTPR hibitTimerNB

macProfNBN orCov

FDD

Retransmit BSR timer for NB-IoT

tReTxBsrTimeNB

NBIOTPR

macProfNBN orCov

FDD

NBIOTPR identifier

nbIoTPrId

NBIOTPR

-

FDD

NPRACH Cyclic Prefix length

nprachCpLen

NBIOTPR

-

FDD

NPRACH profile for NB-IoT normal coverage

nprachProfNBNorC NBIOTPR ov

-

FDD

Max number of preamble attempts of NPRACH

nprachMaxNumPrea NBIOTPR mbleCE

nprachProf NBNorCov

FDD

Number of repetitions per preamble attempt of NPRACH

nprachNumRepPrea NBIOTPR mble

nprachProf NBNorCov

FDD

Number of subcarriers of NPRACH

nprachNumSubcarr NBIOTPR iers

nprachProf NBNorCov

FDD

NPRACH periodicity

nprachPeriod

NBIOTPR

nprachProf NBNorCov

FDD

NPRACH start time

nprachStartTime NBIOTPR

nprachProf NBNorCov

FDD

NPRACH subcarrier offset

nprachSubcarrier NBIOTPR Offset

nprachProf NBNorCov

FDD

RACH profile for NB-IoT normal coverage

rachProfNBNorCov NBIOTPR

-

FDD

Contention resolution timer for NB-IoT

raContResoTimNB NBIOTPR

rachProfNB NorCov

FDD

RA response window size for NB-IoT

raRespWinSizeNB NBIOTPR

rachProfNB NorCov

FDD

RLC profile for NBIoT normal coverage

rlcProfNBNorCov NBIOTPR

-

FDD

Max retransmission threshold for NBIoT

maxRetxThreNB

NBIOTPR

rlcProfNBN orCov

FDD

Poll retransmit for NB-IoT

tPollRetrNB

NBIOTPR

rlcProfNBN orCov

FDD

Scheduler profile in NB-IoT normal coverage

schedProfNBNorCo NBIOTPR v

-

FDD

© 2017 Nokia

Issue: 01


Table 42


Full name

Abbreviated name

Managed object

Parent structure

FDD/TDD

Repetition Number of ACK/NACK for NBIoT

ackNACKNumRep

NBIOTPR

schedProfN BNorCov

FDD

Repetition Number of Msg4 ACK/NACK for NB-IoT

ackNACKNumRepMsg 4

NBIOTPR

schedProfN BNorCov

FDD

Initial repetition number of NPDCCH for RA

iniNpdcchNumRepR a

NBIOTPR

schedProfN BNorCov

FDD

Initial MCS in downlink

iniMcsDl

NBIOTPR

schedProfN BNorCov

FDD

Initial MCS in uplink

iniMcsUl

NBIOTPR

schedProfN BNorCov

FDD

Initial repetition number of NPDSCH

iniNpdschNumRep NBIOTPR

schedProfN BNorCov

FDD

Initial repetition number of NPUSCH

iniNpuschNumRep NBIOTPR

schedProfN BNorCov

FDD

Number of SIB1-NB repetitions

numSib1RepNB

NBIOTPR

-

FDD

The periodicity of SIB2-NB

sib2PeriodicityN B

NBIOTPR

-

FDD

The repetition pattern of SIB2-NB

sib2RepPatternNB NBIOTPR

-

FDD

Offset of the start of SI-NB window

siRadioFrameOffN B

NBIOTPR

-

FDD

SI-NB window length

siWindowLenNB

NBIOTPR

-

FDD

Timer of T300 for NB-IoT

t300NB

NBIOTPR

-

FDD


t301NB

NBIOTPR

-

FDD


t310NB

NBIOTPR

-

FDD

MME RAT support

mmeRatSupport

LNMME

-

FDD

Table 43

Parameters modified by LTE3071

Full name

Issue: 01


Abbreviated name

Parent structure

FDD/TDD

Power offset for UE PUSCH or NPUSCH TX power calculation

p0UePusch

LNBTS

-

FDD

Group assignment for PUSCH or NPUSCH

grpAssigPUSCH LNCEL

-

FDD

Nominal power for UE PUSCH or NPUSCH

p0NomPusch

-

FDD

© 2017 Nokia

Manage d object

LNCEL

97



Table 43

Parameters modified by LTE3071 (Cont.)

Full name

Abbreviated name

Manage d object

Parent structure

FDD/TDD

Minimum required RSRQ in cell (Rel9)

qQualMinR9

SIB

-

FDD

Power ramping step

prachPwrRamp

SIB

-

FDD

TX power calculation

Table 44


Full name

98

Abbreviated name

Parent structure

FDD/TDD

LNCEL

-

FDD

LNCEL

-

FDD

LNCEL

-

FDD

Further PLMN identity list

furtherPlmnIdL LNCEL

-

FDD

Prevent cell activation

preventCellAct ivation

LNCEL

-

FDD

Timer ExtendedWaitTimer10

tExtendedWait LNCEL

-

FDD

Alpha

ulpcAlpha

LNCEL

-

FDD

Maximum number of message 3 HARQ transmissions

harqMaxMsg3

LNCEL

-

FDD

Maximum number of HARQ transmissions in DL

harqMaxTrDl

LNCEL

-

FDD

Maximum number of HARQ transmissions in UL

harqMaxTxUl

LNCEL

-

FDD

Activation of uplink group hopping

actUlGrpHop

LNCEL

-

FDD

Activate RACH preamable power control

actUlpcRachPwr Ctrl

LNCEL

-

FDD

Administrative state

administrative State

LNCEL

-

FDD

Cell power reduce

dlCellPwrRed

LNCEL

-

FDD

E-UTRAN cell identifier

eutraCelId

LNCEL

-

FDD

E-UTRAN access point position

eutranAccessPo intPosition

LNCEL

-

FDD

Additional spectrum emission mask

addSpectrEmi

Cell name

cellName

Delta preamble random access message 3

deltaPreMsg3

© 2017 Nokia

Manage d object

Issue: 01


Table 44



Full name

Abbreviated name

Manage d object

Parent structure

FDD/TDD

Group assignment PUSCH

grpAssigPUSCH LNCEL

-

FDD

Local Cell Resource ID

lcrId

LNCEL

-

FDD

Operational state

operationalSta te

LNCEL

-

FDD

Physical layer cell identity

phyCellId

LNCEL

-

FDD

Maximum output power

pMax

LNCEL

-

FDD

LTE cell configuration identifier

lnCelId

LNCEL

-

FDD

Cell barred flag

cellBarred

SIB

-

FDD

n310

n310

SIB

-

FDD

n311

n311

SIB

-

FDD

Max. uplink transmission power own cell

pMaxOwnCell

SIB

-

FDD

Preamble transmission maximum

preambTxMax

SIB

-

FDD

Cell reserved for operator use

primPlmnCellre s

SIB

-

FDD

Min. required RSRQ in intra-freq neighbor cell (Rel9)

qQualMinR9

SIB

-

FDD

Minumum required RX level in cell

qrxlevmin

SIB

-

FDD

Preamble initial recieved target power

ulpcIniPrePwr

SIB

-

FDD

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




Issue: 01

License control

-

© 2017 Nokia


No

99




Procedure notifications Activation procedure requires cell locking.

–

g

Note: Relationship between the LTE host cell and the NB-IoT cell will disable LTE host cell whenever the inband NB-IoT cell is locked.

g

Note: Online modification for inband NB-IoT releated parameters is not supported in this feature. The modification of: – – –

LNBTS legacy parameters reused for NB-IoT for the inband NB-IoT cell, LNCEL legacy parameters for the inband NB-IoT cell, new LNBTS, NBIOT_FDD, or NBIOTPR parameters for NB-IoT

require the inband NB-IoT cell locking. • •

Feature interdependencies see LTE3071 system impact Preconfiguration The LNCEL and LNCEL_FDD objects for host LTE FDD cell are configured, the cell is operational, and the MIMO mode for the cell is TXDiv, Dynamic Open Loop MIMO, or Closed Loop MIMO.

Procedure

1


2




3

100

Proceed to the Cell Resources page.

© 2017 Nokia

Issue: 01


4


Create and configure the NB-IoT cell. Sub-steps

a) For the host cell, set the Cell Technology & NBIOT mode value to FDD inband (host). The NB-IOT host cell MIMO mode must be TXDiv, Dynamic Open Loop MIMO, or Closed Loop MIMO. Changing this setting might require additional configuration on Antenna Line Settings page.

b) Create and number a new NB-IoT inband cell with the Cell Technology & NBIOT mode value set to NBIOT inband.

c) For the created NB-IoT cell, set the NBIOT host cell id to the value of the FDD inband host cell.

5


6


7

Complete configuration of the LNCEL object for NB-IoT cell as required. Sub-steps

a) Configure LTE cell configuration identifier (lnCelId ), Physical layer cell identity phyCellId ( ), and Tracking area code (tac) parameters.

b) Optional: Depending on the host cell carrier power setting, reconfiguration of the Maximum Coupling Loss (MCL) maxCoverageMCL ( ) parameter might be required.

c) Configure DRX profiles as required.

d) Configure the SIB object as required.

8

If not present, create and configure the NBIOT_FDD object for NB-IoT cell in the step above. Object path: MRBTS ► LNBTS ► LNCEL ► NBIOT_FDD

Issue: 01

© 2017 Nokia

101



g

Note: LTE3071 supports only one, the normal coverage level and Number of Coverage Levels (numCoverageLevels) parameter must be set to value 1 9

If not present, create and configure the NBIOTPR object as required. Object path: MRBTS ► LNBTS Sub-steps

a) Following parameters must be configured as listed for the first coverage level •

NPRACH subcarrier offset (nprachSubcarrierOffset) to value

0 •

Number of subcarriers of NPRACH (nprachNumSubcarriers) to

value n48 • • •

Repetition Number of ACK/NACK for NBIoT (ackNACKNumRep) to value 1 Repetition Number of Msg4 ACK/NACK for NBIoT (ackNACKNumRepMsg4) to value 1 Initial repetition number of NPDSCH (iniNpdschNumRep) to

value 1 •

Initial repetition number of NPUSCH (iniNpuschNumRep) to

value 1 •

Number of repetitions per preamble attempt of NPRACH (nprachNumRepPreamble) to value n32

b) Optional: If required, configure larger than default values for Number of repetitions per preamble attempt of NPRACH (nprachNumRepPreamble) and Max number of preamble attempts of NPRACH (nprachMaxNumPreambleCE)

Because 2.5 us timing error limit is critical for NB-IoT, 5 us is proposed in RAN4 for all coverage level. Such timing error may introduce more random access process failures and call drops.

10 At least one LNMME object must contain the MME RAT Support mmeRatSupport ( ) parameter set to NB-IoT or to Wideband-LTE and NB-IoT. Do this using one of the options: Select from the available options • •

Set the MME RAT Support (mmeRatSupport) parameter in the existing LNMME object to the required value. Create a new LNMME object and set the MME RAT Support (mmeRatSupport) parameter to the required value.

Object path: MRBTS ► LNBTS ► LNMME

102

© 2017 Nokia

Issue: 01








Result If properly configured, eNB now operates the NB-IoT inband cell within the host LTE FDD cell. Post requisites eNB supports modification on MME RAT support (mmeRatSupport) LNMME parameter with manually locking/unlocking LNMME instance by the operator.

g

Note: Setting LNMME administrativeState to locked will trigger S1 link deactivation. Setting LNMME administrativeState to unlocked will trigger S1 link activation.



• • • •

Issue: 01

Deactivation procedure requires cell locking.

Preconfiguration The LNCEL object for host LTE FDD cell is configured and the cell is operational. The LNCEL object for NB-IoT cell inside host LTE FDD cell is configured and the cell is operational. At least one LNMME object with the MME RAT Support (mmeRatSupport) parameter set to NB-IoT or to Wideband-LTE and NB-IoT exists.

© 2017 Nokia

103



Procedure

1


2




3


4

Delete the NB-IoT cell cell from the list.

5

Change the Cell Technology & NBIOT mode setting for the host cell to the value FDD normal.

6


7


8

Optional: Delete the NBIOTPR object.

9

If there are no other NB-IoT cells present, disable MME RAT Support for NB-IoT. Sub-steps

a) For the LNMME object with the MME RAT Support mmeRatSupport ( ) parameter set to Wideband-LTE and NB-IoT, change parameter value to Wideband-LTE.

b) For the LNMME object with the MME RAT Support mmeRatSupport ( ) parameter set to NB-IoT, delete the entire LNMME object. Object path: MRBTS ► LNBTS ► LNMME

104

© 2017 Nokia

Issue: 01








Result NB-IoT cell is now removed and eNB continues normal operations with legacy cells as configured.

Issue: 01

© 2017 Nokia

105

LTE3265: GNSS Outage Handling for OTDOA


11 LTE3265: GNSS Outage Handling for OTDOA The LTE3265: GNSS Outage Handling for OTDOA feature introduces an enhanced GNSS outage handling for the observed time difference of arrival (OTDOA) service.

11.1 LTE3265 benefits The LTE3265: GNSS Outage Handling for OTDOA feature provides the following benefit: •

prevents the situation when GNSS outage causes incorrect UE localization with OTDOA.

11.2 LTE3265 functional description Functional overview The feature introduces an enhanced GNSS outage handling for the OTDOA. This is a parity feature required to support accurate OTDOA UE localization during emergency calls. To ensure backward compatibility, ToP-P synchronization is still supported as a valid source for OTDOA, yet typical ToP-P installations are not able to consistently provide synchronization of the quality similar to GNSS. The LTE3265 feature allows the operator to decide which synchronization sources are allowed for the OTDOA to operate. The operator can select GNSS or ToP-P or both synchronization sources. The feature treats all GNSS systems equally. Fallback from GPS to other (worse) GNSS synchronization source will not disable PRS transmission. The operator is informed during commissioning that in principle, GPS with threshold set to 100 ns is the only synchronization source recommended if OTDOA is used for emergency call location. Different satellite systems are not necessarily synchronized with each other. To achieve best localization accuracy, it is advised that the whole network is synchronized to one satellite system. Otherwise: •

•

If the eNodeBs are synchronized to different systems, then the location based on PRS signals from those eNBs will not be as accurate as when all are synchronized to the same system. If GNSS receiver switches from one system to the other (depends on the setting of the GNSS receiver) then momentary phase error jump can be observed. This can lead to temporary switching off the PRS signal.

There are two cases when the PRS transmission is stopped: •

•

106

The PRS transmission is automatically switched off when the eNB is synchronized to a synchronization source from outside the configurable list of synchronization sources for OTDOA. The PRS transmission is automatically stopped when the eNB is in holdover and the estimated phase error is larger than the configurable phase error threshold for the synchronization source to which it was synchronized before the holdover.

© 2017 Nokia

Issue: 01



The eNB continues user data blanking (no user data scheduled in PDSCH) during PRS occasions while PRS transmission is stopped. The PRS transmission is automatically resumed when the eNB synchronizes to a source included in the OTDOA-compatible list and the eNB calculated phase error is below the configurable phase error threshold of that source.

11.3 LTE3265 system impact Interdependencies between features The LTE3265: GNSS Outage Handling for OTDOA feature is an extension of the LTE495: OTDOA feature. The LTE3265: GNSS Outage Handling for OTDOA feature is enabled together with the LTE495: OTDOA feature. The LTE80: GPS Synchronization must be enabled for OTDOA operation. LTE3265 will affect the behavior of LTE495 . GNSS synchronization is one of the allowed OTDOA synchronization sources. The LTE3265: GNSS Outage Handling for OTDOA feature impacts the following features: •

• •

•

•

Issue: 01

LTE495: OTDOA The LTE3265 feature extends the functionality of the LTE495 feature. LTE3265 is enabled when LTE495 is enabled with a GNSS synchronization source configured as the primary synchronization source. The LTE3265 feature switches off the PRS signal in all BTS cells when GNSS synchronization phase is configured, and the synchronization accuracy is insufficient. Cells without a PRS signal cannot be used by the UE to perform OTDOA measurements. LTE891: Timing over Packet with Phase Synchronization ToP phase synchronization is one of the allowed OTDOA synchronization sources. LTE1710: Sync Hub Direct Forward With LTE3265 feature activated, the interface between Synchronization Hub Master (SHM) and Slave (SHS) carries additional information about the synchronization source that the SHM uses. The SHS BTS monitors the synchronization source that the SHM uses and switches off the PRS signal when the SHM uses a synchronization source which is not allowed for OTDOA in SHS. PRS is also switched off when the SHM or the SHS are in holdover and the phase error threshold is exceeded. The LTE3265 feature defines the maximum number of synchronization chain hops supported with this feature. eNBs which are farther than 5 hops away from SHM are not able to fulfill 100 ns accuracy on air interface, causing degraded OTDOA positioning accuracy. For those eNBs the system will not detect that failure, in this case the operator needs to configure their phase error threshold higher or change the topology of the synchronization chain. LTE2866: One eNB Dual Common Unit Operation When the phase error threshold is exceeded on master core (synchronization master in dual core operation), the PRS signal is switched off on both core modules at the same time. LTE942: Hybrid Synchronization BTS uses Synchronous Ethernet (SyncE) to support holdover.

© 2017 Nokia

107



LTE2184: Flexible Sync Input Priority The LTE2184 feature defines the synchronization sources priorities. The LTE3265 feature uses configuration parameters defined with LTE2184.

•

The LTE3265: GNSS Outage Handling for OTDOA feature cannot be enabled together with: LTE1372: FSM3 Slave Mode Base on CPRI/Ir Go to Actions LTE2422: CPRI Ir Slave Mode With Holdover Support Go to Actions CPRI Ir synchronization uses third party hardware whose precision is unknown, and which does not report the phase error during holdover. In this case, the LTE3265 feature is unable to switch off PRS after the operator-adjustable phase error threshold is exceeded.

• •

Impact on interfaces The LTE3265: GNSS Outage Handling for OTDOA feature has no impact on interfaces. Impact on network management tools The LTE3265: GNSS Outage Handling for OTDOA feature has no impact on network management tools. Impact on system performance and capacity The LTE3265: GNSS Outage Handling for OTDOA feature has no impact on system performance or capacity.



FDD

TDD

System release

FDD LTE17SP

TD LTE 17A


FL17SP

TL17A


Not supported

TL17A

Nokia AirScale BTS

FL17SP

TL17A

Flexi Zone BTS

Not supported

Not supported


Not supported

Not supported


Not supported

Not supported

OMS



NetAct

NetAct 17.2

NetAct 17.2

MME



SAE GW



UE



Alarms

108

© 2017 Nokia

Issue: 01



There are no alarms related to the LTE3265: GNSS Outage Handling for OTDOA feature. BTS faults and reported alarms Table 47

New BTS faults introduced by LTE3265

Fault ID

Fault name

4389

OTDOA PRS transmission disabled

For fault descriptions, see LTE Radio Access Operating Documentation/Reference/Alarms and Faults. Commands There are no commands related to the LTE3265: GNSS Outage Handling for OTDOA feature. Measurements and counters There are no measurements or counters related to the LTE3265: GNSS Outage Handling for OTDOA feature. Key performance indicators There are no key performance indicators related to the LTE3265: GNSS Outage Handling for OTDOA feature. Parameters Table 48


Full name

Manage d object

Parent structure

FDD/TDD

OTDOA Profile List

otdoaProfileLi st

LNBTS

-

FDD

OTDOA Synchronization Source Type

otdoaSyncSourc eType

LNBTS

otdoaProfileList

FDD

OTDOA Phase Error Threshold

otdoaPhaseErro rThreshold

LNBTS

otdoaProfileList

FDD

Table 49

Parameters rmodified by LTE3265

Full name PRS activation

Table 50

Abbreviated name actOtdoa

Manage d object

LNCEL

Parent structure

-

FDD/TDD

common


Full name PRS Tx diversity activation

Issue: 01

Abbreviated name

Abbreviated name

Manage d object

actPrsTxDiv

LNCEL

© 2017 Nokia

Parent structure

-

FDD/TDD

common

109


Table 50


Full name

110


Abbreviated name

Manage d object

PRS bandwidth

prsBandwidth

LNCEL

PRS configuration index

prsConfigurati onIndex

LNCEL_ FDD

FDD

PRS configuration index

prsConfigurati onIndex

LNCEL_ TDD

TDD

PRS muting

prsMuting

LNCEL

-

common

PRS muting info

prsMutingInfo

LNCEL

prsMuting

common

PRS muting info pattern length

prsMutingInfoP atternLen

LNCEL

prsMuting

common

PRS Number of DL frames

prsNumDlFrames LNCEL_ FDD

FDD

PRS Number of DL frames

prsNumDlFrames LNCEL_ TDD

TDD

PRS power boost

prsPowerBoost

LNCEL

-

common

SI window length

siWindowLen

LNCEL

-

common

DRX on duration timer

drxOnDuratT

LNCEL

-

common


dlChBw

Network synchronization mode

btsSyncMode


actSuperCell

LNCEL_ FDD

FDD


actSuperCell

LNCEL_ TDD

TDD

Activate liquid cell configuration

actLiquidCell LNCEL_ FDD

FDD

Activate LPPa support for OTDOA

actLPPaOtdoa

LNBTS

-

common

Activate support for MBMS

actMBMS

LNBTS

-

common

MBSFN EARFCN

mbsfnEarfcn

MBSFN

-

common

MBSFN downlink channel bandwidth

mbsfnDlChBw

MBSFN

-

common

Activation ETWS support

actETWS

LNBTS

-

common

Activation CMAS support

actCMAS

LNBTS

-

common

Twofold transmission of SIBs per SI window

sib2xTransmit

SIB

-

common

© 2017 Nokia

Parent structure

-

FDD/TDD

common

LNCEL_ FDD

FDD

BTSSC L

common

-

Issue: 01


Table 50



Full name

Abbreviated name

Manage d object

Parent structure

Activate enhanced inter-cell interference coordination

actEicic

LNCEL

CSI-RS subframe configuration

csiRsSubfrConf LNCEL_ FDD

FDD

CSI-RS subframe configuration

csiRsSubfrConf LNCEL_ TDD

TDD

-

FDD/TDD

common





License control

Pool license


No

11.5 Activating LTE3265 Before you start The LTE3265: GNSS Outage Handling for OTDOA feature is enabled as long as the LTE495: OTDOA feature is enabled.

11.6 Deactivating LTE3265 Before you start The LTE3265: GNSS Outage Handling for OTDOA feature is deactivated when the LTE495: OTDOA feature is deactivated.

Issue: 01

© 2017 Nokia

111

LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling


12 LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling The LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature extends the support of the LTE3071: NB-IoT Inband feature introducing a new cellular technology standard for narrowband Internet of Things (NB-IoT) on Airscale System Module. NB-IoT provides a wide-area coverage for the IoT, which is an interconnected network of devices, such as machines, vehicles, or buildings.

12.1 LTE3509 benefits The LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature provides more deployment options of inband NB-IoT by supporting Airscale System Module.

12.2 LTE3509 functional description The LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature brings software parity with the LTE3071: NB-IoT Inband feature on Airscale. It introduces an inband NB-IoT deployment, where a hosting wideband LTE cell dedicates one physical resource block (PRB) for NB-IoT use. Narrowband (NB) term denotes a solution implemented in telecommunication technologies to carry the data on a limited number of frequency sets. On Airscale, each inband NB-IoT cell must be placed in the same C-plane pool as the existing LTE hosting cell of 5, 10, 15, or 20 MHz bandwidth. Both of these cells are allocated into the same L1/L2 baseband processing unit and therefore they are served by the same C-plane. Any additional hardware is not required. Only 2Tx2Rx antennas are supported in hosting LTE cells and their corresponding inband NB-IoT cells. The following inband NB-IoT 2Tx2Rx configurations are supported per pool: • • •

4 * 5/10MHz cells 2Tx/2Rx + 4 inband NB-IoT cells 3 * 15/20MHz cells 2Tx/2Rx + 3 inband NB-IoT cells 2 * 5/10/MHz cells 2Tx/2Rx + 2 * 15/20/MHz cells 2Tx/2Rx + 4 inband NB-IoT cells

12.3 LTE3509 system impact Interdependencies between features The following features must be deactivated before activating the LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature: • • • •

112

LTE495: OTDOA LTE819: DL inter-cell interference generation LTE1113: eICIC - macro LTE1542: FDD Supercell

© 2017 Nokia

Issue: 01


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


LTE1709: Liquid Cell LTE1891: eNode B power saving - Micro DTX LTE1900: Centralized RAN LTE2091: FDD SuperCell extension LTE2180: FDD-TDD downlink carrier aggregation 2CC LTE2270: LTE TDD+FDD inter eNB CA basic BTS configurations LTE2316: FDD-TDD downlink carrier aggregation 3CC LTE2337: FDD-TDD downlink carrier aggregation 3CC - 2 FDD & 1 TDD LTE2465: CSG cell support LTE2623: FDD-TDD downlink carrier aggregation 4CC LTE2723: AirScale FDD multicarrier configurations on single radio LTE2733: Baseband pooling LTE2922: AirScale single carrier BTS configurations FDD LTE3268: Combined Supercell for HetNet LTE3616: AirScale 10 MHz single carrier BTS configurations LTE3617: AirScale 10MHz dual carrier on single radio configurations

The LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature impacts the following features: •

•

LTE2823: RRC Connection Triggered Access Class Barring NB-IoT UEs are considered for triggering ACB by a number of RRC connection. However, NB-IoT UEs are not impacted by ACB as ACB is not applied for NB-IoT UEs. LTE3668: NB-IoT: Coverage enhancements Extreme coverage level (+20dB) on inband NB-IoT cells on AirScale without BB pooling will be covered by the LTE3668 feature.

The LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature is impacted by the following features: •

•

•

•

LTE2483: Classical WCDMA/LTE RF-sharing on AirScale SM Indoor The support for classical WCDMA/LTE RF-sharing using LTE AirScale System Module (Indoor) introduced by the LTE2483 feature is also applicable with presence of inband NB-IoT cells. LTE2517: AirScale HW capacity activation licence The LTE3509 feature interacts with the LTE2517 feature that is only needed when more than one DSP pool is used per ABIA. LTE2722: Basic FDD Configurations for AirScale The number of inband NB-IoT cells deployed per pool in the LTE3509 feature is based on the BTS configurations and subconfigurations introduced by the LTE2722 feature. LTE2866: One eNB Dual Common Unit operation The LTE3509 feature interacts with the LTE2866 that is only needed when one full subrack of eNB shall comprise more than 3 ABIA modules.

Impact on interfaces The LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature has no impact on interfaces. Impact on network management tools

Issue: 01

© 2017 Nokia

113



The LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature has no impact on network management tools. Impact on system performance and capacity The LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature impacts system performance and capacity by reducing the RRC resources for legacy UEs. It is related to the fact that on C-plane pool the resources are shared between NB-IoT UEs and the legacy UEs.



FDD

TDD

System release

FDD-LTE 17A

not supported


not supported

not supported


not supported

not supported

Nokia AirScale BTS

FL17A

not supported

Flexi Zone BTS

not supported

not supported


not applicable

not supported


not applicable

not supported

OMS

not supported

not supported

NetAct

not supported

not supported

MME

not supported

not supported

SAE GW

not supported

not supported

UE


not supported

Alarms There are no alarms related to the LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature. BTS faults and reported alarms There are no faults related to the LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature. Commands There are no commands related to the LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature. Measurements and counters There are no measurements or counters related to the LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature.

114

© 2017 Nokia

Issue: 01



Key performance indicators There are no key performance indicators related to the LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling feature. Parameters Table 53


Full name

Abbreviated name

Minimum number of NB IoT RRC connections

Table 54

minNumRrcNB

Manage d object

Parent structure

NBIOT_ FDD

FDD/TDD

FDD


Full name

Abbreviated name

Manage d object

Activate baseband pooling

actBbPooling

LNBTS

-

FDD

Cell technology

cellTechnology

LNCEL

-

FDD

Max number act DRB

maxNumActDrb

LNCEL_ FDD

FDD

Max Number RRC

maxNumRrcNB

NBIOT_ FDD

FDD

Maximum number of active UEs

maxNumActUE

LNCEL_ FDD

FDD

Parent structure

FDD/TDD




License control

ASW

-


No



g

Issue: 01

Activation procedure requires cell locking. Note: Relationship between the LTE host cell and the NB-IoT cell will disable LTE host cell whenever the inband NB-IoT cell is locked.

© 2017 Nokia

115


g


Note: Online modification for inband NB-IoT releated parameters is not supported in this feature. The modification of: – – –

LNBTS legacy parameters reused for NB-IoT for the inband NB-IoT cell, LNCEL legacy parameters for the inband NB-IoT cell, new LNBTS, NBIOT_FDD, or NBIOTPR parameters for NB-IoT

require the inband NB-IoT cell locking. • • •

Feature interdependencies see LTE3509 system impact Preconfiguration The LNCEL and LNCEL_FDD objects for host LTE FDD cell are configured, the cell is operational, and the MIMO mode for the cell is TXDiv, Dynamic Open Loop MIMO, or Closed Loop MIMO.

Procedure

1


2




3


4

Create and configure the NB-IoT cell. Sub-steps

a) For the host cell, set the Cell Technology & NBIOT mode value to FDD inband (host). The NB-IOT host cell MIMO mode must be TXDiv, Dynamic Open Loop MIMO, or Closed Loop MIMO. Changing this setting might require additional configuration on Antenna Line Settings page.

116

© 2017 Nokia

Issue: 01



b) Create and number a new NB-IoT inband cell with the Cell Technology & NBIOT mode value set to NBIOT inband.

c) For the created NB-IoT cell, set the NBIOT host cell id to the value of the FDD inband host cell.

5


6


7

Complete configuration of the LNCEL object for NB-IoT cell as required. Sub-steps

a) Configure LTE cell configuration identifier (lnCelId ), Physical layer cell identity phyCellId ( ), and Tracking area code (tac) parameters.

b) Optional: Depending on the host cell carrier power setting, reconfiguration of the Maximum Coupling Loss (MCL) maxCoverageMCL ( ) parameter might be required.

c) Configure DRX profiles as required.

d) Configure the SIB object as required.

8

If not present, create and configure the NBIOT_FDD object for NB-IoT cell in the step above. Object path: MRBTS ► LNBTS ► LNCEL ► NBIOT_FDD

g

Note: LTE3509 supports only one, the normal coverage level and Number of Coverage Levels (numCoverageLevels) parameter must be set to value 1

9

If not present, create and configure the NBIOTPR object as required. Object path: MRBTS ► LNBTS

Issue: 01

© 2017 Nokia

117



Sub-steps

a) Following parameters must be configured as listed for the first coverage level •

NPRACH subcarrier offset (nprachSubcarrierOffset) to value

0 •

Number of subcarriers of NPRACH (nprachNumSubcarriers) to

value n48 • • •

Repetition Number of ACK/NACK for NBIoT (ackNACKNumRep) to value 1 Repetition Number of Msg4 ACK/NACK for NBIoT (ackNACKNumRepMsg4) to value 1 Initial repetition number of NPDSCH (iniNpdschNumRep) to

value 1 •

Initial repetition number of NPUSCH (iniNpuschNumRep) to

value 1 •

Number of repetitions per preamble attempt of NPRACH (nprachNumRepPreamble) to value n32

b) Optional: If required, configure larger than default values for Number of repetitions per preamble attempt of NPRACH (nprachNumRepPreamble) and Max number of preamble attempts of NPRACH (nprachMaxNumPreambleCE)

Because 2.5 us timing error limit is critical for NB-IoT, 5 us is proposed in RAN4 for all coverage level. Such timing error may introduce more random access process failures and call drops.

10 At least one LNMME object must contain the MME RAT Support mmeRatSupport ( ) parameter set to NB-IoT or to Wideband-LTE and NB-IoT. Do this using one of the options: Select from the available options • •

Set the MME RAT Support (mmeRatSupport) parameter in the existing LNMME object to the required value. Create a new LNMME object and set the MME RAT Support (mmeRatSupport) parameter to the required value.

Object path: MRBTS ► LNBTS ► LNMME



118

© 2017 Nokia

Issue: 01






Result If properly configured, eNB now operates the NB-IoT inband cell within the host LTE FDD cell. Post requisites eNB supports modification on MME RAT support (mmeRatSupport) LNMME parameter with manually locking/unlocking LNMME LNMME instance by the operator.

g

Note: Setting LNMME administrativeState to locked will locked will trigger S1 link deactivation. deactivation. Setting LNMME administrativeState to unlocked will unlocked will trigger S1 link activation.


Procedure notifications notificat ions –

• • • •

Deactivation Deactivati on procedure requires cell locking.

Preconfiguration The LNCEL LNCEL object for host LTE FDD cell is configured and the cell is operational. The LNCEL LNCEL object for NB-IoT cell inside host LTE FDD cell is configured and the cell is operational. At least one LNMME object LNMME object with the MME RAT Support (mmeRatSupport) parameter set to NB-IoT or NB-IoT or to Wideband-LTE and NB-IoT exists. NB-IoT exists.

Procedure

1

Issue: 01

Start Start the BTS BTS Site Manag Manager er applica application tion and and establ establish ish the the connect connection ion to the the BTS.

© 2017 Nokia

119


2


Star Startt com commi miss ssio ioni ning ng.. Sub-steps

a) Select View ► Commissioning Commissioning or click Commissioning Commissioning on the View View Bar on the left. The BTS Site checkbox, Site checkbox, located in the Target section, Target section, is selected by default. This is the recommended setting.

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

3

Proce Proceed ed to the the Cell Cell Res Resou ource rces s pag page. e.

4

Delet Delete e the the NB-Io NB-IoT T cell cell cell cell from from the the list list..

5

Change Change the Cell Cell Tech Technolo nology gy & NBIOT NBIOT mode setti setting ng for the the host host cell to the the value FDD normal.

6

Proceed Proceed to the Radio Radio Netwo Network rk Conf Configur iguratio ation n page. page.

7

Go to the the LNB LNBTS TS obje object ct.. Object path: MRBTS ► LNBTS

8

Optio Optional nal:: Delet Delete e the the NBIO NBIOTP TPR R objec object. t.

9

If there there are no no other other NB-IoT NB-IoT cells prese present, nt, disabl disable e MME RAT RAT Support Support for for NB-IoT NB-IoT Sub-steps

a) For For the the LNMME LNMME objec objectt with with the the MME RAT Support mmeRatSupport ( ) parameter set to Wideband-LTE and NB-IoT, change parameter value to Wideband-LTE.

b) For the LNMME LNMME objec objectt with with the MME RAT Support mmeRatSupport ( ) parameter set to NB-IoT, delete the entire LNMME object. Object path: MRBTS ► LNMME

120

© 2017 Nokia

Issue: 01



10 Send the the commiss commissioni ioning ng plan file file to the BTS. BTS. Sub-steps

a) Go to to the Sen Send d Parame Paramete ters rs page. page.




Result NB-IoT cell is now removed and eNB continues normal operations with legacy cells as configured.

Issue: 01

© 2017 Nokia

121

LTE3582: LTE-M Enhancements I


13 LTE3582: LTE-M Enhancements I Table 56

LTE3582 summary of changes

Date of change

Section

Change description

17.08.2017

LTE-M enhancements

Supported functions have been added.

17.08.2017

LTE3582 benefits

"10 MHz bandwidth" has been added.

17.08.2017

Narrowband introduction

"Narrowband introduction" has been deleted.

17.08.2017

Signaling radio bearer 1 (SRB1) only call

Two S1AP messages have been added.

17.08.2017

LTE-M enhancements

"Pseudo 1Tx support" has been added.

17.08.2017

LTE-M enhancements

"Interworking with PUCCH blanking" has been deleted.

17.08.2017

Interdependencies between features

LTE116, LTE117 have been corrected, LTE2115 has been deleted.

17.08.2017

Impact on system performance "Impact on system and capacity performance and capacity" has been changed.

17.08.2017

Key performance indicators

Tables have been added.

17.08.2017

The "Existing parameters related to LTE3582" table

The minNumRrcCatM parameter has been deleted.

17.08.2017

1.5 Activating and configuring LTE3582

Activation and deactivation procedures have been added.

The LTE3582: LTE-M Enhancements I feature enhances the LTE3128: LTE-M feature. With the LTE3582: LTE-M Enhancements I feature, the following functions are supported: • • • •

the LTE-M functionality for 5 MHz band signaling radio bearer 1 (SRB1) only call PRACH formats 1 and 3 pseudo 1Tx support

13.1 LTE3582 benefits The LTE3582: LTE-M Enhancements I feature allows the operator to enable machine-tomachine communication (used in the Internet of Things solution) in 5 MHz, additionally to 10 MHz bandwidth of the LTE network.

122

© 2017 Nokia

Issue: 01



13.2 LTE3582 functional description IoT introduction The Internet of Things (IoT) interconnects devices, such as machines, parts of machines, smart meters, or sensors, and autonomously exchanges data between them. Examples of use cases for the IoT are: • • • • •

automotive (connected cars, fleet management, traffic safety, diagnostics) smart cities (energy and utility management, waste management, intelligent transport) smart home (security, automation) healthcare (monitoring of patients, medical devices) smart industry (inventory management, shipment tracking)

The machine-to-machine (M2M) communication is needed to support the IoT. The M2M is defined as data communication among devices without the need for human interaction. The 3GPP has defined three standards for the M2M, which are EC-GSM, NB-IoT, and LTE-M. Requirements for each standard are: • • • • •

long battery life low device cost low deployment cost extended coverage support of a massive number of devices

LTE-M introduction LTE for Machines (LTE-M), also known as Enhanced Machine Type Communications (eMTC), is an extension of the legacy 1.4 MHz LTE. It has a coverage up to 15 km and complements NB-IoT by supporting data rates up to 1 Mbps (maximum data rate for NBIoT is up to 100 kbps). This solution is deployable either in shared spectrum together with normal LTE or as a stand-alone in a refarmed GSM carrier. The devices operating in LTE-M are very simple (around 80% simpler than standard LTE device), and have an estimated battery life of 10 years.

Issue: 01

© 2017 Nokia

123


Figure 7


LTE-M in-band deployment

M E T L

LTE carrier Signaling radio bearer 1 (SRB1) only call A bearer is an information transmission path of a defined capacity, delay, and bit error rate. The eNB supports two main kinds of bearers: signaling radio bearer (SRB) and data radio bearer (DRB). Some of Cellular IoT (CIoT) UEs don't need to use the DRB to send a data message to the operator. With the LTE3582: LTE-M Enhancements I feature, they use SRB1 only. To support the SRB1 only call functionality, this feature introduces three new parameters: •

The C-Plane inactivity timer (cpInactivityTimerCatM) parameter This is a new parameter describing an already existing functionality. This CAT-Mspecific timer monitors activity on the S1 interface. If one of the following S1AP messages were received or sent out, the eNB starts or restarts this timer. It helps to avoid an unwanted transition of the UE from the connected to the idle state due to inactivity. – – – – – –

•

S1AP: S1AP: S1AP: S1AP: S1AP: S1AP:

UE CONTEXT MODIFICATION REQUEST DL NAS Transport UL NAS Transport CONNECTION ESTABLISHMENT INDICATION E-RAB SETUP REQUEST E-RAB RELEASE COMMAND

The Srb inactivity timer (srbInactivityTimerCatM) parameter This parameter monitors the U-u interface in the Cat-M. The parameter defines the time period to indicate the UE's inactivity on SRB in both DL and UL directions.

If both of these timers are inactive or expired, the eNB sends S1AP: UE CONTEXT RELEASE REQUEST with cause: “User Inactivity”, and the eNB starts UE CONTEXT Release procedure. •

124

The CIoT EPS optimisation PLMN Id list (cIoTEpsPlmnIdList) structure

© 2017 Nokia

Issue: 01



The Attach without PDN connectivity support (attachNoPDNConn) parameter controls broadcast in the SIB2-BR information that attached without PDN connectivity Cellular IoT (CIoT) functionality (SMS only transfer) is supported in this cell. LTE-M enhancements The LTE3582: LTE-M Enhancements I feature introduces the following additional enhancements to the LTE-M functionality: •

PRACH formats 1 and 3 as an additional support to format 0 for the Cat-M UEs The eNB supports an MPRACH preamble formats 0, 1, and 3. Each of this format is assigned to the PRACH configuration indices: Table 57

Preamble formats Preamble format

•

PRACH configuration indices

0

3-8

1

19-24

3

51-56

Pseudo 1Tx support: a remote radio head (RRH) is configured in the same way as Transmission Mode 2 (TM2) with 2Tx, where second antenna is “terminated”.

13.3 LTE3582 system impact Interdependencies between features The following feature must be activated before activating the LTE3582: LTE-M Enhancements I feature: •

LTE3128: LTE-M The LTE3128: LTE-M feature is a prerequisite for using the LTE3582: LTE-M Enhancements I feature. Both features have the same feature flag: the actCatM parameter.

The following features must be deactivated before activating the LTE3582: LTE-M Enhancements I feature: • •

•

•

•

Issue: 01

LTE1382: Cell Resource Groups - the cellResourceSharingMode LNCEL parameter must be set to none LTE116: 3 MHz Cell bandwidth - the LTE116: 3 MHz Cell bandwidth feature has no feature flag, but the LTE3582: LTE-M Enhancements I feature cannot be activated on 3 MHz cells LTE117: 1.4 MHz Cell bandwidth - the LTE117: 1.4 MHz Cell bandwidth feature has no feature flag, but the LTE3582: LTE-M Enhancements I feature cannot be activated on 1.4 MHz cells LTE48: Support of High Speed Users - the prachHsFlag LNCEL_FDD (for FDD) or LNCEL_TDD (for TDD) parameter must be set to false, and the HsScenario LNCEL parameter value must be empty LTE1987: DL MIMO 4x4 - the MIMO mode value in the MIMO settings section must be different from Closed Loop MIMO (4x4)

© 2017 Nokia

125


• • • • • •

• •


LTE568: DL MIMO 4x2 - the dlMimoMode parameter in the MIMO settings section must be set to any value other than Closed Loop MIMO (4x2) LTE944: PUSCH masking - the actPuschMask LNCEL_FDD (for FDD) or LNCEL_TDD (for TDD) parameter must be set to false LTE825: Uplink outer region scheduling - the selectOuterPuschRegion LNCEL_FDD (for FDD) or LNCEL_TDD (for TDD) parameter must be set to none LTE1059: Uplink multi-cluster scheduling - the actUlMultiCluster LNCEL_FDD (for FDD) or LNCEL_TDD (for TDD) parameter must be set to false LTE1709: LiquidCell - the actLiquidCell LNCEL_FDD (for FDD) or LNCEL_TDD (for TDD) parameter must be set to false LTE3071: NB-IoT - the nbIoTMode LNCEL parameter must be set to disabled - for detailed information refer to the Deactivating LTE3071 chapter in the LTE3071: NBIoT feature. LTE2445: Combined Supercell - the Activate specific cell configuration value on the Cell resources page must be empty LTE2612: ProSe Direct Communications for Public Safety - the actProSeComm LNBTS_FDD (for FDD) or LNBTS_TDD (for TDD) parameter must be set to false

The LTE3582: LTE-M Enhancements I feature is impacted by the following features: •

•

• •

• • •

LTE115: Cell Bandwidth - 5 MHz The LTE115: Cell Bandwidth - 5 MHz feature supports 5 MHz LTE carrier, or cell RF bandwidth. LTE2664: Load Based PUCCH Region This feature provides support for dynamic allocation for Physical Resource Blocks (PRBs) to be used for physical uplink control channel (PUCCH). LTE2733: Baseband pooling This feature allows an efficient usage of baseband pooling. LTE72: 4-way RX diversity This feature enables a 4-way uplink diversity Maximum Ratio Combining (MRC) reception for Flexi LTE BTS. LTE97: Cell radius max 77 km This feature provides support for PRACH format 1. LTE180: Cell radius max 100 km This feature provides support for PRACH format 3. LTE980: IRC for 4 RX paths The Interference Rejection Combining (IRC) is improved mainly for highly loaded and interference limited cells.

Impact on interfaces The cells with enabled LTE-M support dedicated system information broadcast of MIB, SIB1-BR, SIB2-BR, SIB3-BR, SIB4-BR, and SIB16-BR. Impact on network management tools The LTE3582: LTE-M Enhancements I feature has no impact on network management tools. Impact on system performance and capacity The LTE3582: LTE-M Enhancements I feature has no impact on system performance or capacity.

126

© 2017 Nokia

Issue: 01





FDD

TDD

System release

FDD-LTE 17A

Not supported


FL17A

Not supported


Not supported

Not supported

Nokia AirScale BTS

FL17A

Not supported

Flexi Zone BTS

FL17A

Not supported


Not supported

Not supported


Not supported

Not supported

OMS


Not supported

NetAct

NetAct 17.8

Not supported

MME


Not supported

SAE GW


Not supported

UE


Not supported

Alarms There are no alarms related to the LTE3582: LTE-M Enhancement I feature. Measurements and counters Table 59 Counter ID

Issue: 01


Measurement

M8061C 54

Number of Signaling Connection Establishment Requests rejected due to MME overload for LTE-M

LTE-M per LNCEL

M8061C 55

Number of Signaling Connection Establishment Requests rejected due to Control Plane overload for LTE-M

LTE-M per LNCEL

M8061C 56

Number of Signalling Connection Establishment Requests rejected due to threshold for the maximum number of RRC connections for LTE-M.

LTE-M per LNCEL

M8061C 57

Number of Signaling Connection Establishment Requests rejected due to User Plane overload for LTE-M

LTE-M per LNCEL

© 2017 Nokia

127


Table 59



Counter ID

Counter name

Measurement

M8061C 58

Number of Signalling Connection Establishment Requests rejected due to lack of PUCCH resources for LTE-M

LTE-M per LNCEL

M8061C 59

Number of RRC Paging Requests (records) for LTE-M Ues

LTE-M per LNCEL

M8061C 60

Number of discarded RRC paging qeguests (records) for LTE-M UEs due to paging buffer overflow

LTE-M per LNCEL

M8061C 61

Number of MME Initiated UE Context Release Request due to detected double S1 for LTE-M Ues

LTE-M per LNCEL

M8061C 62

Number of EPC Initiated E-RAB releases due to double S1 detected for LTE-M UEs

LTE-M per LNCEL

For counter descriptions, see LTE Operating Documentation/ Reference/ Counters and Key Performance Indicators. Key performance indicators Table 60

New key performance indicators introduced by LTE3582

KPI ID

KPI name

LTE_6290a; E-UTRAN RRC Connection Setup Failure Ratio per Cause for Cat-M UEs LTE_6291a LTE_6292a

E-UTRAN RRC Paging Discard Ratio for Cat-M UEs due to paging buffer overflow

LTE_6293a

E-UTRAN RRC Paging Records for Cat-M UEs

LTE_6294a

E-UTRAN Discarded RRC Paging Records for Cat-M UEs due to paging buffer overflow

Table 61

Key performance indicators modified by LTE3582

KPI ID

KPI name

LTE_6218b

E-UTRAN E-RAB Drop Ratio per Cause for Cat-M UEs, E-RAB drop ratio due to radio network layer (RNL) cause initiated by EPC

LTE_6222b

E-UTRAN E-RAB Drop Ratio, User Perspective for Cat-M UEs

LTE_6223b

E-UTRAN E-RAB Drops per PDCP SDU volume, User Perspective for Cat-M UEs

LTE_6231b

E-UTRAN Cat-M UE Transaction to ECM-IDLE State Success Ratio

For KPI descriptions, see LTE Operating Documentation/ Reference/ Counters and Key Performance Indicators. Parameters

128

© 2017 Nokia

Issue: 01


Table 62



Full name

Abbreviated name

Managed object

CIoT EPS optimisation PLMN Id list

cIoTEpsPlmnIdLi st

LNBTS_FD D

Attach without PDN connectivity support

attachNoPDNConn LNBTS_FD D

MCC

mcc

MNC

mnc

MNC length

mncLength

C-Plane inactivity timer Srb inactivity timer

Table 63

Parent structure

FDD/TDD

-

FDD

cIoTEpsPlmnIdL ist

FDD

LNBTS_FD D

cIoTEpsPlmnIdL ist

FDD

LNBTS_FD D

cIoTEpsPlmnIdL ist

FDD

LNBTS_FD D

cIoTEpsPlmnIdL ist

FDD

cpInactivityTim erCatM

CATMPR

-

FDD

srbInactivityTi merCatM

CATMPR

-

FDD


Full name

Abbreviated name

Managed object

Parent structure

FDD/TDD

MPDCCH narrowband number for Cat-M

mpdcchNarBandN umCatM

CATMPR

-

FDD

Paging on PDSCH narrowband number for Cat-M

pagPdschNarBan dNumCatM

CATMPR

-

FDD

PDSCH narrowband number for Cat-M

pdschNarBandNu mCatM

CATMPR

-

FDD

PUSCH narrowband number for Cat-M

puschNarBandNu mCatM

CATMPR

-

FDD

SI narrowband number for Cat-M

siNarBandNumCa tM

CATMPR

-

FDD

Activate LTE-M feature

actCatM

LNCEL_FDD

-

FDD


dlChBw

LNCEL_FDD

-

FDD

Downlink MIMO mode

dlMimoMode

LNCEL_FDD

-

FDD

Uplink channel bandwidth

ulChBw

LNCEL_FDD

-

FDD

For parameter descriptions, see LTE Operating Documentation/ Reference/ Parameters . Sales information

Issue: 01

© 2017 Nokia

129


Table 64





130

License control

Pool license

© 2017 Nokia


No

Issue: 01


LTE3586: High Power UE Specific Mobility Thresholds

14 LTE3586: High Power UE Specific Mobility Thresholds The LTE3586: High Power UE Specific Mobility Thresholds feature introduces a set of dedicated High Power UE Reference Signal Received Power (RSRP) thresholds. These thresholds trigger handover measurements in order to extend the coverage.

14.1 LTE3586 benefits The LTE3586: High Power UE Specific Mobility Thresholds feature provides the following benefits: • •

Supporting extended coverage for High Power UEs Reduced number of handover events

14.2 LTE3586 functional description Originally, 3GPP has defined the UE Power Class 3 (for example: 23dBm) as High Power UE. 3GPP release 14 defines the UE Power Class 2 (for example: 26dBm) on LTE Band 41 and the UE Power Class 1 (for example: 31dBm) on LTE Band 14 as the High Power type of UE. The LTE3586: High Power UE Specific Mobility Thresholds feature introduces the following parameters to configure new RSRP thresholds in order to extend the cell size: • • •

threshold2aHpue parameter defines the dedicated High Power UE A1 RSRP

threshold to stop inter-frequency and inter-RAT measurements threshold2InterFreqHpue parameter defines the dedicated High Power UE A2 RSRP threshold to start inter-frequency measurements a3OffsetRsrpInterFreqHpue, threshold3aInterFreqHpue, and threshold3InterFreqHpue parameters define the dedicated High Power UE A3/A5 RSRP thresholds for inter-frequency handover measurements

The eNodeB identifies the High Power UE based on the power class IE reported in the UE capability report. The protocol is RRC protocol, and the message that contains the information is UECapabilityInformation. When the UE goes from idle mode to active mode, as part of the initial context setup or the incoming handover, the following actions occur: • •

Issue: 01

The eNodeB activates the RSRP-based A2 measurement with the highest A2 threshold considering the High Power specific inter-frequency threshold. When the A2 measurement report is received from the High Power UE, the RSRP is compared against the dedicated High Power UE A2 RSRP threshold. If the RSRP is below the threshold, the corresponding inter-frequency handover measurements for A1 and A3/A5 are activated. The handover measurements will use the new High Power UE dedicated thresholds.

© 2017 Nokia

131


•


When the A1 measurement report is received from the High Power UE, all the interfrequency and inter-RAT handover measurements are deactivated. The A2 measurement with the highest A2 threshold is activated, and the A1 measurement is deactivated.

Additionally, three counters are introduced to monitor the High Power inter-frequency mobility performance: •

Inter-frequency handover attempts for High Power UEs (A3/A5 radio related handovers only)

•

Successful inter-frequency handover completions for High Power UEs (A3/A5 radio related handovers only) Average number of high power capable UEs

•

From coverage point of view, the 2.5GHz band supports extended coverage for High Power UEs as on the 1.9GHz band. This functionality is illustrated in the following figure. Figure 8

High Power UE extended coverage

g

Note: In Carrier Aggregation configurations, the LTE3586 feature allows the operator to choose if the High Power dedicated mobility thresholds are applicable for High Power UEs.

g

Note: The High Power UE dedicated mobility thresholds are not applicable if QCI1 bearer is established on the High Power UE. The LTE3586 functionality can be enabled/disabled per cell by the operator.

132

© 2017 Nokia

Issue: 01



14.3 LTE3586 system impact Interdependencies between features The LTE3586: High Power UE Specific Mobility Thresholds feature interacts with the following features: • • • • • • • • • • • • • • •

LTE1060: TDD - FDD handover LTE1198: RSRQ Triggered Mobility LTE1534: Multiple Frequency Band Indicator LTE1558: TDD Downlink Carrier Aggregation LTE2105: TDD Uplink Intra Band Carrier Aggregation - 2CC LTE2224: Uplink Triggered Mobility LTE2275: PCell Swap LTE2551: RSRQ Based A5 LTE2583: Support of High Power UE LTE2754: Frequency Bands Priority Change in mFBI LTE2838: CA Steering Intra Cell Handover LTE3436: High Power UE LTE3590: CA and MFBI Interworking Extensions LTE55: Inter-frequency Handover LTE64: Service Based Handover Thresholds

Impact on interfaces The LTE3586: High Power UE Specific Mobility Thresholds feature impacts interfaces as follows: •

RRC: supportedBandListEUTRA-v1320 IE in UE-EUTRA-Capability IE

•

•

S1: UE-EUTRA-Capability: supportedBandListEUTRA-v1320 encapsulated in Source to Target Transparent Container IE of HANDOVER REQUIRED message and HANDOVER REQUEST messages X2: UE-EUTRA-Capability: supportedBandListEUTRA-v1320 encapsulated in RRC Context IE of HANDOVER REQUEST message

Impact on network management tools The LTE3586: High Power UE Specific Mobility Thresholds feature has no impact on network management tools. Impact on system performance and capacity The LTE3586: High Power UE Specific Mobility Thresholds feature has no impact on system performance or capacity.

Issue: 01

© 2017 Nokia

133





FDD

TDD

System release

Not supported

TDD-LTE 17A


Not supported

TL17A


Not supported

TL17A

Nokia AirScale BTS

Not supported

TL17A

Flexi Zone BTS

Not supported

TL17A


Not supported

TL17ASP


Not supported


OMS

Not supported


NetAct

Not supported

NetAct 17.8

MME

Not supported


SAE GW

Not supported


UE

Not supported

3GPP R13 UE 3GPP R14 UE

Alarms There are no alarms related to the LTE3586: High Power UE Specific Mobility Thresholds feature. BTS faults and reported alarms There are no faults related to the LTE3586: High Power UE Specific Mobility Thresholds feature. Commands There are no commands related to the LTE3586: High Power UE Specific Mobility Thresholds feature. Measurements and counters Table 66 Counter ID

134


Measurement

M8021C 44

Inter-frequency handover attempts for high power UEs (A3/A5 radio related handovers only)

LTE Handover

M8021C 45

Successful inter-frequency handover completions for high

LTE Handover

© 2017 Nokia

Issue: 01


Table 66



Counter ID

Counter name

Measurement

power UEs (A3/A5 radio related handovers only) M8051C 134

Average number of high power capable UEs per cell

LTE UE Quantity

For counter descriptions, see LTE Performance Measurements . Key performance indicators There are no key performance indicators related to the LTE3586: High Power UE Specific Mobility Thresholds feature. Parameters Table 67


Full name

Abbreviated name

Manage d object

Parent structure

FDD/TDD

Activate UE uplink power based mobility thresholds

actUePowerBase dMobThr

LNCEL

-

common

Power Fallback in CA mode

pwrFallbackCa LNBTS

-

common

Threshold th2 interFreq for RSRP of the high power UE

threshold2Inte rFreqHpue

LNCEL

-

common

Threshold th2a for RSRP of the high power UE

threshold2aHpu e

LNCEL

-

common

A3 offset RSRP inter frequency for high power UE

a3OffsetRsrpIn terFreqHpue

LNHOIF

-

common

Threshold th3 for RSRP inter frequency for high power UE

threshold3Inte rFreqHpue

LNHOIF

-

common

Threshold th3a for RSRP inter frequency for high power UE

threshold3aInt erFreqHpue

LNHOIF

-

common




ASW

Issue: 01

License control

Pool license

© 2017 Nokia


No

135



14.5 Activating LTE3586 Before you start Procedure notifications: • •

The LTE3586 feature is deactivated, that is, the LNCEL: actUePowerBasedMobThr parameter is set to false. The LNCEL: cellTechnology parameter is set to TDD.

Procedure

1


2




3


4


5

Set the actUePowerBasedMobThr value to true. Object path: MRBTS ► LNBTS ► LNCEL

6

Optionally, configure the threshold2aHpue parameter. Object path: MRBTS ► LNBTS ► LNCEL

7

Optionally, configure the threshold2InterFreqHpue parameter. Object path: MRBTS ► LNBTS ► LNCEL

136

© 2017 Nokia

Issue: 01


8



9

Optionally, configure the pwrFallbackCa parameter. Object path: MRBTS ► LNBTS

10 Create LNHOIF object. Object path: MRBTS ► LNBTS ► LNCEL Sub-steps

a) Right-click the LNCEL object.

b) Select New and find the LNHOIF object.

c) Configure the LNHOIF object.

11 Optionally, configure the a3OffsetRsrpInterFreqHpue parameter. Object path: MRBTS ► LNBTS ► LNCEL ► LNHOIF

12 Optionally, configure the threshold3aInterFreqHpue parameter. Object path: MRBTS ► LNBTS ► LNCEL ► LNHOIF

13 Optionally, configure the threshold3InterFreqHpue parameter. Object path: MRBTS ► LNBTS ► LNCEL ► LNHOIF






Issue: 01

© 2017 Nokia

137



14.6 Deactivating LTE3586 Before you start Procedure notifications: The LNCEL: actUePowerBasedMobThr parameter is set to true. Procedure

1


2




3


4


5

Set the actUePowerBasedMobThr value to false.

6




138


© 2017 Nokia

Issue: 01




Issue: 01

© 2017 Nokia

139

LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND


15 LTE3612: 4-way RX Diversity Support for 3MHz Cell with FRND Benefits, functionality, system impact, reference data of the feature The LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND feature enhances the LTE72: 4-way RX Diversity feature functionality and complements the LTE3422: Flexi RRH 2T4R 2350 10 W FRND feature deployment by introducing additional configuration.

15.1 LTE3612 benefits The LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND feature provides the following benefits: • • •

Increased cell throughput of approximately 65% in average radio conditions Additional sub-configuration which supports 4RX with FRND Shared benefits with the LTE72: 4-way RX Diversity feature for 3-MHz bandwidth

15.2 LTE3612 functional description Hardware overview Description of the hardware associated with the LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND feature is presented in Table 1. Table 69

LTE3612-associated hardware ABIA plug-in

FRND RRH

Nokia AirScale Capacity (ABIA) plug-in unit is one of the three Nokia AirScale System Module components. It is used for baseband processing and for optical interfaces with radio units. One AirScale System Module can contain up to six ABIA plug-in units.

The FRND is a two-pipe remote radio head (RRH) optimized for distributed macro BTS installations. RRHs are mainly used in outdoor pole installations where support for one sector is needed.

The Figure: Complete view of Nokia AirScale System Module presents its maximum configuration with distinguished ABIA plug-in units and their placement.

140

© 2017 Nokia

Issue: 01


Figure 9


Complete view of Nokia AirScale System Module AirScale Subrack AMIA

AirScale Capacity ABIA

AirScale Common ASIA

LTE3612 feature functionality The LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND feature introduces additional configuration to the AirScale System Module, which has the following characteristics: • • •

Up to two FRND RRHs in one basic cell set, supporting one 3-MHz cell in 2x2 MIMO with 4RX diversity per radio Both radio connections via Common Public Radio Interface (CPRI) 2.4 Gbps to one Nokia AirScale Capacity plug-in (ABIA) Two basic cell sets possible per ABIA

Figure 10

LTE3612 configuration

FSMr4 (2TX/4RX 1+1 J-type, BW 3MHz) Sector

Sector

LCR :Rx

LCR :Rx Sector

LCR :Tx&Rx

Sector2 LCR2:Rx Sector

LCR :Tx&Rx

Band A

Sector2 LCR2:Rx Sector2 LCR2:Tx&Rx

Sector2 LCR2:Tx&Rx

Band A/B 2.4 Gbps CPRI links

Basic cell set requiring 1 pool = FBIP

FSMr4

For more information about FRND RRH, see the LTE3422: Flexi RRH 2T4R 2350 10 W FRND feature documentation.

Issue: 01

© 2017 Nokia

141



For more information about ABIA plug-in, see the LTE2261: AirScale Capacity ABIA feature documentation.

15.3 LTE3612 system impact LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features are a prerequisite for activating the LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND feature: • • • •

LTE116: Cell Bandwidth – 3 MHz LTE3422: Flexi RRH 2T4R 2350 10 W FRND LTE2722: Basic FDD Configurations for AirScale LTE72: 4-way RX Diversity

The following features must be deactivated before activating the LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND feature: • • •

g

LTE2733: Baseband Pooling LTE1691: Uplink intra-eNB CoMP 4Rx LTE1089: Downlink Carrier Aggregation and other carrier aggregation-related features Note: The actDLCAggr parameter is set to false.

•

g

LTE1779: Triple Carrier Operation and other multiple carrier features Note: The actMultipleCarrier parameter is set to false.

• •

LTE442: Network Assisted Cell Change to GSM LTE984: GSM Redirect with System Information

Impact on interfaces The LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND feature has no impact on interfaces. Impact on network management tools The LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND feature has no impact on network management tools. Impact on system performance and capacity The LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND feature impacts system performance and capacity by increasing cell throughput by about 65%.

142

© 2017 Nokia

Issue: 01



15.4 LTE3612 reference data LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements Table 70


FDD

TDD

System release

FDD-LTE 17A

Not supported


Not supported

Not supported


Not supported

Not supported

Nokia AirScale BTS

FL17A

Not supported

Flexi Zone BTS

Not supported

Not supported


Not supported

Not supported


Not supported

Not supported

OMS

Not supported

Not supported

NetAct

NetAct 17.2

Not supported

MME


Not supported

SAE GW


Not supported

UE


Not supported

There are no alarms, commands, measurements and counters, key performance indicators, parameters related to the LTE3612: 4-way RX Diversity Support for 3-MHz Cell with FRND feature. Sales information Table 71



Basic Software (BSW)

Issue: 01

License control

-

© 2017 Nokia


Yes

143

LTE3668: NB-IoT: Coverage enhancements


16 LTE3668: NB-IoT: Coverage enhancements The LTE3668: NB-IoT: Coverage enhancements feature upgrades the LTE3071: NB-IoT Inband feature by improving narrowband Internet of Things (NB-IoT) link budget with additional 20 dB coverage for downlink and uplink.

16.1 LTE3668 benefits The LTE3668: NB-IoT: Coverage enhancements feature allows to reach devices in basements or in greater distance by extending the coverage by 20 dB for NB-IoT cells up to 164 dB maximum pathloss coverage.

16.2 LTE3668 functional description NB-IoT introduction The Internet of Things (IoT) is a system of interrelated UEs, which are for example computing devices, vehicles, machines, and other objects provided with unique identifiers and the ability to transfer data over a network without human interaction. The term narrowband (NB) denotes a solution implemented in telecommunication technologies to carry data on a limited number of frequency sets. The size of the message sent in a narrowband mode utilizes less bandwidth than the cumulative bandwidth of the underlying channel. There are three types of NB-IoT in use: • • •

In-band - through flexible use of a part of an LTE carrier Stand-alone - replacing a GSM or a WCDMA carrier with an NB-IoT carrier Guard band – utilizing the guard band of an LTE carrier

Figure 11

Types of NB-IoT

T o I B N

T o I B N

T o I B N

LTE carrier

GSM/WCDMA carriers

LTE carrier

In-band

Stand-alone

Guard band

NB-IoT is designed to operate in the E-UTRA bands 1, 2, 3, 5, 8, 12, 13, 17, 18, 19, 20, 26, 28 and 66. LTE3668 feature overview

144

© 2017 Nokia

Issue: 01



The LTE3668: NB-IoT: Coverage enhancements feature functionality can only be activated when one of the features, either the LTE3071: NB-IoT Inband or the LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling , is activated. The LTE3071: NB-IoT Inband feature can only support maximum coupling loss (MCL) with 144 dB (normal coverage) by default. The MCL is a limit value of the coupling loss at which the service can be delivered, and therefore defines the coverage of the service. The LTE3668: NB-IoT: Coverage enhancements feature modifies the Maximum Coupling Loss (maxCoverageMCL) parameter enabling the following values: •

144 for default 144 dB

•

154 - 154 dB MCL for robust coverage

•

164 - 164 dB MCL for extreme coverage

Only one coverage level is supported per one NB-IoT cell. Flexi Zone Pico hadware is unable to reach MCL values above. Figure 12

LTE3668 increased coverage concept

Normal Coverage Enhanced Coverage

A consistency check is present for the Minimum required RX level in cell (qrxlevmin) parameter. Its value is based on the power and bandwidth settings of the host FDD cell. It acts as a compensator to ensure that only the UEs with MCL equal or less than set with the Maximum Coupling Loss (maxCoverageMCL) parameter can access the NB-IoT cell. Each coverage level has a dedicated profile with parameters for: • • • • •

NPRACH configuration RACH parameters repetitions NPDCCH search spaces RLC/MAC parameters

(see Table 73: New parameters introduced by LTE3668 and Table 74: Existing parameters related to LTE3668 ). In the LTE17A release, the LTE3668 feature uses normal coverage level profile only.

Issue: 01

© 2017 Nokia

145



In case of different repetitions used in the transmission, timers can be reconfigured as required by the operator (for example: Timer of T300 for NB-IoT , Timer of T310 for NB-IoT , and Timer min lifetime of half-open RRC connection for NB-IoT ). For the synchronization purpose, uplink transmission gaps for long uplink transmissions are supported.

g

Note: This feature requires that below parameters related to the normal coverage profile parameters have specific values: •

NPRACH subcarrier offset (nprachSubcarrierOffset) set to 0

•

Number of subcarriers of NPRACH (nprachNumSubcarriers) set to n48

16.3 LTE3668 system impact Interdependencies between features The LTE3668: NB-IoT: Coverage enhancements feature functionality is activated when one of the following features is activated: • •

LTE3071: NB-IoT Inband LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling

Impact on interfaces The LTE3668: NB-IoT: Coverage enhancements feature has no impact on interfaces. Impact on network management tools The LTE3668: NB-IoT: Coverage enhancements feature impacts BTS Site Manager tool by adding new profiles for robust and extreme coverages to the NBIOTPR object, but only the normal coverage profile is used by the feature. Impact on system performance and capacity The LTE3668: NB-IoT: Coverage enhancements feature impacts system performance by improving quality with higher coverage levels (up to 20 dB). The quality improvement comes at the cost of significant capacity decrease in both uplink and downlink (increased number of repetitions require additional time to transmit the same amount of data).



146

FDD

TDD

System release

FDD-LTE 17A

not supported


FL17A

not supported



not supported

© 2017 Nokia

Issue: 01


Table 72



FDD

TDD

Nokia AirScale BTS

FL17A

not supported

Flexi Zone BTS

FL17A

not supported


not supported

not supported


not supported

not supported

OMS


not supported

NetAct

17.8

not supported

MME


not supported

SAE GW


not supported

UE


not supported

Alarms There are no alarms related to the LTE3668: NB-IoT: Coverage enhancements feature. BTS faults and reported alarms There are no faults related to the LTE3668: NB-IoT: Coverage enhancements feature. Commands There are no commands related to the LTE3668: NB-IoT: Coverage enhancements feature. Measurements and counters There are no measurements or counters related to the LTE3668: NB-IoT: Coverage enhancements feature. Key performance indicators There are no key performance indicators related to the LTE3668: NB-IoT: Coverage enhancements feature. Parameters Table 73


Full name

Issue: 01

Abbreviated name

Managed object

NPRACH RSRP Threshold-1

nprachRsrpThres hold1

NBIOT_F DD

-

FDD

NPRACH RSRP Threshold-2

nprachRsrpThres hold2

NBIOT_F DD

-

FDD

Common Search Space profile for NB-IoT third coverage level

cssProfNBExtCov NBIOTPR

-

FDD

© 2017 Nokia

Parent structure

FDD/TDD

147


Table 73

148



Full name

Abbreviated name

Managed object

Parent structure


npdcchMaxNumRep Ra

NBIOTPR

Common Search Space profile for NB-IoT third coverage level (cssProfNBExt Cov)

FDD




FDD


npdcchOffsetRa NBIOTPR


FDD

Common Search Space profile for NB-IoT second coverage level

cssProfNBRobCov NBIOTPR

-

FDD


npdcchMaxNumRep Ra

NBIOTPR

Common Search Space profile for NB-IoT second coverage level (cssProfNBRob Cov)

FDD




FDD


npdcchOffsetRa NBIOTPR


FDD

© 2017 Nokia

FDD/TDD

Issue: 01


Table 73


Full name

Issue: 01


Abbreviated name

Managed object

Default number of repetition for paging

defaultPagNumRe p

NBIOTPR

-

FDD

MAC profile for NBIoT third coverage level

macProfNBExtCov NBIOTPR

-

FDD


logicalChanSrPr ohibitTimerNB

NBIOTPR

MAC profile for NB-IoT third coverage level (macProfNBExt Cov)

FDD


tReTxBsrTimeNB NBIOTPR

MAC profile for NB-IoT third coverage level (macProfNBExt Cov)

FDD

MAC profile for NBIoT second coverage level

macProfNBRobCov NBIOTPR

-

FDD


logicalChanSrPr ohibitTimerNB

NBIOTPR

MAC profile for NB-IoT second coverage level (macProfNBRob Cov)

FDD


tReTxBsrTimeNB NBIOTPR

MAC profile for NB-IoT second coverage level (macProfNBRob Cov)

FDD

NPRACH profile for NB-IoT third coverage level

nprachProfNBExt Cov

NBIOTPR

-

FDD


nprachMaxNumPre ambleCE

NBIOTPR

NPRACH profile for NB-IoT third coverage level (nprachProfNB ExtCov)

FDD


nprachNumRepPre amble

NBIOTPR

NPRACH profile for NB-IoT third coverage level

FDD

© 2017 Nokia

Parent structure

FDD/TDD

149


Table 73



Full name

Abbreviated name

Managed object

Parent structure

FDD/TDD

(nprachProfNB ExtCov)

150

NBIOTPR


FDD

NBIOTPR NPRACH profile for NB-IoT third coverage level (nprachProfNB ExtCov)

FDD


nprachNumSubcar riers

NPRACH periodicity

nprachPeriod

NPRACH start time



FDD


nprachSubcarrie rOffset

NBIOTPR


FDD

NPRACH profile for NB-IoT second coverage level

nprachProfNBRob Cov

NBIOTPR

-

FDD


nprachMaxNumPre ambleCE

NBIOTPR

NPRACH profile for NB-IoT second coverage level (nprachProfNB RobCov)

FDD


nprachNumRepPre amble

NBIOTPR


FDD


nprachNumSubcar riers

NBIOTPR


FDD

© 2017 Nokia

Issue: 01


Table 73


Full name

Issue: 01


Abbreviated name

Managed object

Parent structure

NBIOTPR NPRACH profile for NB-IoT second coverage level (nprachProfNB RobCov)

FDD/TDD

FDD

NPRACH periodicity

nprachPeriod

NPRACH start time



FDD


nprachSubcarrie rOffset

NBIOTPR


FDD

RACH profile for NB-IoT third coverage level

rachProfNBExtCo v

NBIOTPR

-

FDD



RACH profile for NB-IoT third coverage level (rachProfNBEx tCov)

FDD



RACH profile for NB-IoT third coverage level (rachProfNBEx tCov)

FDD

RACH profile for NB-IoT second coverage level

rachProfNBRobCo v

-

FDD



RACH profile for NB-IoT second coverage level(rachPro fNBRobCov)

FDD



RACH profile for NB-IoT second coverage level(rachPro fNBRobCov)

FDD

© 2017 Nokia

NBIOTPR

151


Table 73


Full name

152


Abbreviated name

Managed object

RLC profile for NBIoT third coverage level

rlcProfNBExtCov NBIOTPR


maxRetxThreNB


tPollRetrNB

RLC profile for NBIoT second coverage level

rlcProfNBRobCov NBIOTPR


maxRetxThreNB


tPollRetrNB

Scheduler profile in NB-IoT third coverage level

schedProfNBExtC ov


ackNACKNumRep


ackNACKNumRepMs g4


iniMcsDl

© 2017 Nokia

Parent structure -

FDD/TDD

FDD

NBIOTPR RLC profile for NB-IoT third coverage level (rlcProfNBExt Cov)

FDD

NBIOTPR RLC profile for NB-IoT third coverage level (rlcProfNBExt Cov)

FDD

-

FDD

NBIOTPR RLC profile for NB-IoT second coverage level (rlcProfNBRob Cov)

FDD

NBIOTPR RLC profile for NB-IoT second coverage level (rlcProfNBRob Cov)

FDD

NBIOTPR

FDD

-

NBIOTPR Scheduler profile in NB-IoT third coverage level (schedProfNBE xtCov)

FDD

NBIOTPR

FDD

Scheduler profile in NB-IoT third coverage level (schedProfNBE xtCov)

NBIOTPR Scheduler profile in

FDD

Issue: 01


Table 73



Full name

Abbreviated name

Managed object

Parent structure

FDD/TDD

NB-IoT third coverage level (schedProfNBE xtCov)

Issue: 01

NBIOTPR Scheduler profile in NB-IoT third coverage level (schedProfNBE xtCov)

FDD

NBIOTPR


FDD




FDD




FDD

Scheduler profile in NB-IoT second coverage level

schedProfNBRobC ov

-

FDD


ackNACKNumRep


ackNACKNumRepMs g4


iniMcsDl


iniMcsUl

Initial repetition number of NPDCCH for RA and unicast NPDSCH transmission

iniNpdcchNumRep Ra

© 2017 Nokia

NBIOTPR

NBIOTPR Scheduler profile in NB-IoT second coverage level (schedProfNBR obCov)

FDD

NBIOTPR

Scheduler profile in NB-IoT second coverage level (schedProfNBR obCov)

FDD

NBIOTPR Scheduler profile in NB-IoT second coverage

FDD

153


Table 73



Full name

Abbreviated name

Managed object

Parent structure

FDD/TDD

level (schedProfNBR obCov)

g

NBIOTPR Scheduler profile in NB-IoT second coverage level (schedProfNBR obCov)

FDD

NBIOTPR


FDD




FDD




FDD

iniMcsUl


iniNpdcchNumRep Ra

Note: Although LTE3668 introduces parameters for robust and extreme, those parameters will not be used by this feature. Table 74


Full name

154


Abbreviated name

Manage d object

Parent structure

FDD/TDD

NB-IoT operation mode

nbIoTMode

LNCEL

-

FDD

Minimum required RX level in cell

qrxlevmin

LNCEL

-

FDD

Maximum Coupling Loss (MCL)

maxCoverageMCL NBIOT_ FDD

FDD

Number of Coverage Levels

numCoverageLev els

NBIOT_ FDD

FDD

Common Search Space profile for NB-IoT first coverage level

cssProfNBNorCo v

NBIOTP R

FDD

© 2017 Nokia

Issue: 01


Table 74

Issue: 01



Full name

Abbreviated name

Manage d object


npdcchMaxNumRe pRa

NBIOTP Common Search Space profile R for NB-IoT first coverage level (cssProfNBNorC ov)

FDD


npdcchStartSfR a

NBIOTP Common Search Space profile R for NB-IoT first coverage level (cssProfNBNorC ov)

FDD


npdcchOffsetRa NBIOTP Common Search Space profile R for NB-IoT first coverage level (cssProfNBNorC ov)

FDD

MAC profile for NBIoT first coverage level

macProfNBNorCo v

NBIOTP R

FDD


logicalChanSrP rohibitTimerNB

NBIOTP MAC profile for NB-IoT R first coverage level (macProfNBNorC ov)

FDD


tReTxBsrTimeNB NBIOTP MAC profile for NB-IoT R first coverage level (macProfNBNorC ov)

FDD

Maximum number of repetitions for NPDCCH common search space for paging

npdcchMaxNumRe pPag

NBIOTP R

FDD

NPRACH profile for NB-IoT first coverage level

nprachProfNBNo rCov

NBIOTP R

FDD


nprachMaxNumPr eambleCE

NBIOTP NPRACH profile for NB-IoT R first coverage level (nprachProfNBN orCov)

FDD

Number of repetitions

nprachNumRepPr eamble

NBIOTP NPRACH profile for NB-IoT R first coverage

FDD

per

© 2017 Nokia

Parent structure

FDD/TDD

155


Table 74



Full name

Abbreviated name

preamble attempt of NPRACH

156

Manage d object

Parent structure

FDD/TDD

level (nprachProfNBN orCov)


nprachNumSubca rriers


FDD

NPRACH periodicity

nprachPeriod


FDD

NPRACH start time

nprachStartTim e


FDD


nprachSubcarri erOffset


FDD

RACH profile for NB-IoT first coverage level

rachProfNBNorC ov

NBIOTP R

FDD


raContResoTimN B

NBIOTP RACH profile for NB-IoT R first coverage level (rachProfNBNor Cov)

FDD


raRespWinSizeN B

NBIOTP RACH profile for NB-IoT R first coverage level ( rachProfNBNorC ov)

FDD

RLC profile for NBIoT first coverage level

rlcProfNBNorCo v

NBIOTP R

FDD


maxRetxThreNB NBIOTP RLC profile for NB-IoT R first coverage level (rlcProfNBNorC ov)

© 2017 Nokia

FDD

Issue: 01


Table 74


Full name

Issue: 01


Abbreviated name

Parent st structure

FDD/TDD

NBIOTP RLC profile for NB-IoT R first coverage level (rlcProfNBNorC ov)

FDD

rrcGuardTimerN B

NBIOTP R

FDD

Scheduler profile in NB-IoT first coverage level

schedProfNBNor Cov

NBIOTP R

FDD


ackNACKNumRep NBIOTP Scheduler profile in NBR IoT first coverage level (schedProfNBNo rCov)

FDD


ackNACKNumRepM sg4

NBIOTP Scheduler profile in NBR IoT first coverage level (schedProfNBNo rCov)

FDD


iniMcsDl


FDD


iniMcsUl


FDD


iniNpdcchNumRe pRa


FDD


iniNpdschNumRe p


FDD


iniNpuschNumRe p

NBIOTP Scheduler profile in NBR IoT first coverage level

FDD


tPollRetrNB

RRC guard timer radio bearer management for NBIoT

© 2017 Nokia

Manage d object

157

LTE36 TE3668 68:: NB-I NB-IoT oT:: Cove Covera rage ge enha enhanc ncem emen ents ts

Table 74



Full name

Abbreviated name

Manage d object

Parent st structure

FDD/TDD

(schedProfNBNo rCov) Timer min lifetime of half-open RRC connection for NBIoT

tHalfRrcConNB NBIOTP R

FDD


t300NB

NBIOTP R

FDD


t310NB

NBIOTP R

FDD

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



ASW

158

License control

-

© 2017 Nokia


No

Issue: 01


LTE3669: NB-IoT: Paging support

17 LTE3669: TE3669 : NB-IoT NB-Io T: Paging support suppor t The LTE3669: NB-IoT: Paging support support feature introduces support for paging functionality for the Inband Narrowband Internet of Things (NB-IoT) mobile terminated (MT) connections. The functionality is applicable in Flexi Multiradio BTS and AirScale hardware.

17.1 LTE3669 benefits The LTE3669: NB-IoT: Paging support support feature provides the following benefits: •

improves the implementation implementati on of Narrowband Internet of Things (NB-IoT) by introducing mobile terminated paging for NB-IoT

17.2 LTE3669 functional description Functional overview The LTE3669: NB-IoT: Paging support support feature enables paging for the Narrowband Internet of Things (NB-IoT) mobile terminated (MT) connections. Paging for both normal and extreme coverage is supported. The functionality applies to Inband NB-IoT cell in AirScale hardware or Flexi Multiradio BTS. Paging The LTE3669: NB-IoT: Paging support support feature supports S1AP: PAGING requests related to the NB-IoT. This message sent for NB-IoT UE is triggering radio resource control (RRC) Paging procedure in the NB-IoT cell. This leads to the eNB calculating the next appropriate Paging Frame for Paging Occasion (based on paging configuration parameters and UE_ID value), in which requested NB-IoT UE needs to be paged in the given cell. Once a RRC Paging-NB is received by the UE, a mobile terminated RRC Connection Establishment procedure is initiated.

Issue: 01

© 2017 Nokia

159


Figure 13


Paging procedure

UE

MME

eNB S1AP: PAGING UE Identity Index value, UE Paging Identity, [Paging DRX], CN domain, List of TAIs, [Paging Priority], [UE Radio Capability for Paging], [Extended UE Identity Index Value] NB-IoT related information elements: Assistance Data for Paging, NB-IoT UE Identity Index Value

Paging for this NB-IoT cell on NPDCCH/NPDSCH

RRC: Paging-NB (pagingRecordList) RRC Connection Establishment

LTE3669: NB-IoT: Paging support feature paging parameters The LTE3669: NB-IoT: Paging support feature allows to modify previously non-modifiable O&M paging parameters. Those parameters are broadcasted in the paging control channel (pcch-Config-NB) system information block type 2 - narrowband (SIB2-NB). The Paging Occasion and Paging Frame, which are calculated by the eNB when RRC Paging-NB is sent in NB-IoT cell, are based on: • •

paging configuration parameters UE_ID

which are received in the S1AP:PAGING message. Paging discard Exceeding the maximum number of paging records included in the RRC paging-NB pagingRecordList information element (IE) will result in paging request being dropped. The pagingRecordList size depends on the iniMcsDl initial downlink modulation parameter.

160

© 2017 Nokia

Issue: 01


Figure 14

g


Transport Block Size (TBS) for 1-10 Resource Units (RU) for NPDSCH RRC Paging-NB

Note: If S1AP:PAGING message contains Assistance Data for Control Element (CE) capable UEs, then Information Element (IE) with E-UTRAN Cell Global Identifier (ECGI) and Paging Attempt Information IE are used to increase NB-IoT Paging capacity. There is a risk of Paging Discard Ratio related to NB-IoT UEs KPI elevation if the two subsequent RRC Pagings-NB are overlapping. This is caused by a high number of Paging Narrowband Physical Downlink Control Channel (NPDCCH) and Narrowband Physical Downlink Shared Channel (NPDSCH) repetitions. In this situation, the second RRC Paging-NB is being silently discarded. Paging overlapping If the interval between Paging Occasions (PO) is not sufficient, it may lead to RRC Paging-NB overlapping. When not all NPDCCH/NPDSCH repetitions fit in the interval between the two following POs, then the second RRC Paging-NB that is overlapped is silently discarded. To avoid RRC paging overlapping situation, a careful planning of Paging, SIB, and a number of repetitions is required. The Paging Frame and Paging Occasion are set by pagingNbNB parameter. The default paging cycle configured with the defPagCycNB parameter value should be set in a way that allows all the repetitions for the RRC Paging-NB to go through. The number of repetitions depends on the npdcchMaxNumRepPag parameter. Figure 15

RRC paging not overlapping scenario Default paging cycle = 5,12 s

Paging occasion RRC paging 1

NPDCCH=1024

NPDSCH=256 x 4ms

RRC paging 2

NPDCCH=1024

NPDSCH=256 x 4ms

Time

Sufficient interval between POs allows for all RRC Paging 1 repetitions to occur. Example for extreme coverage NPDCCH=1024 and NPDSCH=256 repetitions.

Issue: 01

© 2017 Nokia

161


Figure 16


RRC paging overlapping scenario Default paging cycle = 2,56 s

Paging occasion

RRC paging 1

NPDCCH=1024

NPDSCH=256 x 4ms

RRC paging 2

NPDCCH=1024

NPDSCH=256 x 4ms

Time

The interval between consecutive Paging Occasions is not long enough to allow all the repetitions for the RRC paging 1 to occur. This will result in RRC paging 2 to be silently discarded. Example for extreme coverage NPDCCH=1024 and NPDSCH=256 repetitions. Recommendations on setting pagingNbNB and defPagCycNB parameters The follwing parameters are being configured to avoid an overlapping scenario: •

numSib1RepNB

•

sib2PeriodicityNB

•

siWindowLenNB

•

sib2RepPatternNB

•

pagingNbNB

•

defPagCycNB

•

schedProfNBNorCov/iniNpdcchNumRepRa

•

schedProfNBNorCov/iniNpdschNumRep

g

Note: Parameter defPagCycNB value should not be set lower than the pagingNbNB parameter value. Exemplary estimations are done with the numSib1RepNB parameter value set to 16. Recommended pagingNbNB settings in order to accommodate one RRC Paging-NB message without the possibility to overlap next PO depends on the settings of SIB and the number of NPDCCH/NPDSCH parameters. Adaptive Transport Block Size (TBS), ranging from 1 to 10 resource units, results in a varying length of RRC Paging-NB message over NPDSCH. Differences in length rely on a number of paging requests and required paging capacity, for example: • •

1 resource unit (RU) TBS:schedProfNBNorCov/iniNPDSCHNumRepRa*1 10 resource unit (RU) TBS:schedProfNBNorCov/iniNPDSCHNumRepRa*10

This adaptive TBS is unlike other NB-IoT downlink traffic with allocated 4 fixed subframes. The eNB determines the maximum TBS that is allowed for the paging record number. It is based on initial Modulation and Coding Scheme (MCS) set by the operator.

g

162

Note: It is highly recommended to set MME's timer T3413 with the value higher than maximal NB-IoT default paging DRX value configured in all of the connected eNBs.

© 2017 Nokia

Issue: 01


Figure 17


Basic rule of setting parameter pagingNbNB value

PagingNbNB TTIs (excluding SIB2-NB TTIs)

NPDCCH/NPDSCH repetitions

pagingNbNB TTIs (SIB2-NB TTIs excluded) > schedProfNBnorCov/iniNPDCCHNumRepRa+4+ schedProfNBNorCov/iniNPDSCHNumRep *(1-10)

Value of the pagingNbNB parameter should not be smaller than the overall length of the RRC Paging-NB message. Examplary calculations reveal that for extreme coverage situation with the following values set to: •

numSib1RepNB = 16

•

siWindowLenNB = 1600ms

•

sib2RepPatternNb = every 2ndRF

•

sib2PeriodicityNB = 1024RF

•

schedProfNBnorCov/iniNPDCCHNumRepRa = 1024

•

schedProfNBNorCov/iniNPDSCHNumRep = 64, 128 or 256

there are only two appropriate pagingNbNB values recommended. Those values are 1/512 and 1/1024. Table 76

RRC Paging-NB free subframes needed to avoid collision with the following paging iniNPDSCHNumRep

iniNPDCCHNumRepR a

g

Vaild RUs pagingNbN defpagCycN needed for B B Paging NPDCCH/NPDSC H block

1024

64

1220

1/512; 1/1024

512; 1024

1024

128

1412

1/512; 1/1024

512;1024

1024

256

1796

1/512; 1/1024

512; 1024

Note: The final Paging TBS should be set by the eNB according to the actual payload of paging records that are about to be sent. The smallest sufficient number of transmission subframes should be allocated to accommodate paging records and initial MCS requirements. Paging scheduling Type1-Narrowband Physical Downlink Control Channel (Type1-NPDCCH) common search space should be supported by the NB-IoT scheduler for paging procedure. Scheduler copes with situations when Paging Occasion (PO) collides with an invalid subframe or with System Information-Narrowband (SI-NB).

Issue: 01

© 2017 Nokia

163



1. Situation in which PO is not a valid NB-IoT downlink subframe. The starting point for the NPDCCH transmission is the first valid NB-IoT DL subframe after the misplaced PO. 2. Situation in which PO is colliding with the SI-NB transmission. The LTE3669: NB-IoT: Paging support feature supports delaying PO to avoid imposing on the SI-NB transmission.

g

Note: A NB-IoT DL subframe is considered a valid subframe when: •

It does not contain the following transmissions: – – – –

•

Narrowband Narrowband Narrowband Narrowband

Primary Synchronization Signal (NPSS) Secondary Synchronization Signal (NSSS) Physical Broadcast Channel (NPBCH) System Information Block type 1 (SIB1-NB)

It is configured as a NB-IoT DL subframe in the SIB1-NB.

To avoid NB-IoT Type-1 NPDCCH search space collisions following settings of defPagCycNb and npdcchMaxNumRepPag are recomended: • • • •

if defPagCycNb= if defPagCycNb= if defPagCycNb= if defPagCycNb=

rf128, then npdcchMaxNumRepPag < r1024 rf256, then npdcchMaxNumRepPag < r2048 rf512, then no restriction rf1024, then no restriction

NB-IoT scheduler should ensure that the paging message can be sent in the nearest PO. This means that the NB-IoT scheduler prioritizes the paging message over other unicast transmissions. There are two possible ways the scheduler can handle the paging message colliding with the NB-IoT transmissions mentioned below: • • •

NPSS, NSSS, Master Information Block (MIB), SIB1-NB, SI-NB NPDCCH and NPDSCH repetitions ongoing previous paging transmission

1. The paging message (Paging NPDCCH and NPDSCH included) is prioritized and interrupts the ongoing NB-IoT transmission of unicast traffic. This includes unicast NPDCCH and NPDSCH. 2. The NB-IoT transmission of NPSS, NSSS, MIB, SIB1-NB, SI-NB and the ongoing paging transmissions are not being overridden by a paging message.

17.3 LTE3669 system impact Interdependencies between features One of the following features must be activated for the LTE3669: NB-IoT: Paging support feature to be active: • •

LTE3071: NB-IoT Inband LTE3509: NB-IoT: Inband on AirScale

The LTE3669: NB-IoT: Paging support feature impacts the following features:

164

© 2017 Nokia

Issue: 01


•

•

•


LTE3125: eDRX - IDLE The LTE3669: NB-IoT: Paging support feature is a precondition of LTE3125: eDRX IDLE support in NB-IoT cell. LTE3819: IoT: Cat-M and NB-IoT on the same frequency carrier Paging Occasions for Cat-M UEs and for NB-IoT UEs are on different PRBs and are not coordinated. So in the LTE3819: IoT: Cat-M and NB-IoT on the same frequency carrier feature, the paging logic in LTE3669: NB-IoT: Paging support (for NB-IoT UEs) and (for Cat-M UEs) will be followed directly. LTE3543: NB-IoT Standalone Depends on the LTE3669: Paging support feature. It utilizes paging functionality introduced for inband NB-IoT.

The LTE3669: NB-IoT: Paging support feature is impacted by the following features: •

•

•

•

•

LTE3: S1, X2 and RRC common signaling LTE3669: NB-IoT: Paging support uses S1 setup procedure to send to the MME O&M configurable NB-IoT Default Paging DRX. LTE41: PDCP, RLC & MAC support Paging control channel (PCCH) and paging channel (PCH) are used to support paging function in NB-IoT. LTE49: Paging LTE3669: NB-IoT: Paging support uses S1AP: Paging request related to NB-IoT cells. LTE915: eNode B configuration update The eNB Configuration Update procedure is being used to send configurable NB-IoT Default Paging DRX. LTE3668: NB-IoT: Coverage enhancements NB-IoT Paging functionality uses LTE3668: Coverage enhancements to page NB-IoT devices with coverage enhancements.

Impact on interfaces The LTE3669: NB-IoT: Paging support feature impacts interfaces as follows: •

Uu interface: –

•

support of RRC Paging-NB message

S1AP interface: – – – – –

support of NB-IoT Default Paging DRX IE in S1AP:eNB CONFIGURATION UPDATE support of NB-IoT UE Identity Index Value IE in S1AP:PAGING support of Assistance Data for CE Capable UEs IE in S1AP:PAGING support of Paging Attempt Information IE in S1AP:PAGING support of Cell Identifier and Coverage Enhancement Level UEs IE in S1AP:UE CONTEXT COMPLETE

Impact on network management tools The LTE3669: NB-IoT: Paging support feature impacts network management tools as follows:

Issue: 01

© 2017 Nokia

165


•

NetAct: –

•


Introduces new counters: •

NB_IOT_RRC_ESTAB_MT_ATT

•

NB_IOT_RRC_ESTAB_MT_SUCC

•

NB_IOT_RRC_PAGE_REQ

•

NB_IOT_RRC_PAGE_REQ_DISC_OVL

•

NB_IOT_RRC_PAGE_REQ_DISC_OVLAP

BTSSM: –

Introduces a new parameters: •

–

startingCovLevelPagingOptNB

Enables modification of the parameters: •

defPagCycNB

•

npdcchMaxNumRepPag

•

pagingNbNB

Impact on system performance and capacity The LTE3669: NB-IoT: Paging support feature impacts system performance and capacity as follows: •

The LTE3669: NB-IoT: Paging support feature supports mobile terminated call by introducing paging functionality. Different number of paging repetitions can be configured depending on the chosen configuration and desired amount of coverage reach. Increase in the number of paging repetitions results in a lower number of subframes available for traffic bearing. Consumption of subframes dedicated to paging can be calculated using a general formula: –

number of Narrowband Physical Downlink Control Channel (NPDCCH) valid subframes + 4ms gap + number of valid Narrowband Physical Downlink Shared Channel (NPDSCH) subframes, where: • •

number of NPDCCH subframes = NPDCCH-iniRepNumNPDCCH number of NPDSCH subframes = NPDSCH-iniRepNumNPDSCH

Table 77

NPDCCH/NPDSCH repetitions

Channel

166

NPDCCH iniRepNumNPDCCH

NPDSCH - iniRepNumNPDSCH

Deployment Mode

standalone

inband

standalone

inband

Repetitions Normal Coverage

1

2

1

1

Repetitions Robust Coverage

8

128

1

16

© 2017 Nokia

Issue: 01


Table 77


NPDCCH/NPDSCH repetitions (Cont.)

Channel

Repetitions Extreme coverage

NPDCCH iniRepNumNPDCCH

256

1024

NPDSCH - iniRepNumNPDSCH

16

256

In case of inband extreme coverage, there is a possibility to utilize more than 5 consecutive seconds (for adaptive TBS up to 10 ms long) just for paging purpose during a paging cycle.

•

–

Length of paging cycle 1024*1ms + 4ms + 256*10ms = 3588 ms

Assuming that for extreme coverage there is 40% of overhead and pagingNbNB is set to 10240ms, then the overall capacity impact reaches 58,4%: –

3588ms/(10240ms*60%) = 58,4%


LTE3669: NB-IoT: Paging support hardware and software requirements

FDD

TDD

System release

FDD-LTE 17A

-


FL17A

-


-

-

Nokia AirScale BTS

FL17A

-

Flexi Zone BTS

FL17ASP

-


FL17ASP

-


not supported

-

OMS


-

NetAct

not supported

-

MME


-

SAE GW


-

UE


-

Alarms There are no alarms related to the LTE3669: NB-IoT: Pagging support feature. BTS faults and reported alarms There are no faults related to the LTE3669: NB-IoT: Pagging support feature. Commands

Issue: 01

© 2017 Nokia

167



The reference to command the document for WCDMA and SRAN should be provided for PR1. There are no commands related to the LTE3669: NB-IoT: Pagging support feature. Measurements and counters Table 79

New counters introduced by LTE3669: NB-IoT: Paging support

Counter ID

Counter name

Measurement

M8066C 20

RRC paging requests (records) for NB-IoT UEs

LTE NB-IoT

M8066C 21

Discarded RRC paging requests (records) for NB-IoT UEs due to paging record list overflow

LTE NB-IoT

M8066C 22

Discarded RRC paging requests (records) for NB-IoT UEs due to paging occasion overlap

LTE NB-IoT

M8066C 23

Attempted RRC Connection Establishments with cause "mt-Access" for NB-IoT UEs

LTE NB-IoT

M8066C 24

Successful RRC Connection Establishments with cause "mt-Access" for NB-IoT UEs

LTE NB-IoT

Key performance indicators Table 80

New key performance indicators introduced by LTE3669: NB-IoT: Paging support

KPI ID

KPI name

Paging Discard Ratio related to NB-IoT UEs

Parameters Table 81

New parameters introduced by LTE3669: NB-IoT: Paging support

Full name

Abbreviated name

Manage d object

Starting Coverage Level supports Paging Optimization for NB-IoT

startingCovLev elPagingOptNB

MRBTS/ LNBTS/ LNCEL/ NBIOT_ FDD

Table 82

FDD/TDD

FDD

Parameters modified by LTE3669: NB-IoT: Paging support Full name

Default paging cycle for NB-IoT cell

168

Parent structure

Abbreviated name

Managed object

MRBTS/L NBTS/NBI OTPR

defPagCycNB

© 2017 Nokia

Parent structure

Issue: 01


Table 82


Parameters modified by LTE3669: NB-IoT: Paging support (Cont.) Full name

Abbreviated name

Managed object

Maximum number of repetitions for NPDCCH common search space for paging

npdcchMaxNumRepPa MRBTS/L g NBTS/NBI OTPR

Paging nB for NB-IoT

pagingNbNB

Parent structure

MRBTS/L NBTS/NBI OTPR


LTE3669: NB-Iot: Paging support sales information


ASW

Issue: 01

License control

-

© 2017 Nokia


No

169

LTE3688: Additional FDD-TDD Carrier Aggregation Band Combinations - V


18 LTE3688: Additional FDD-TDD Carrier Aggregation Band Combinations - V The LTE3688: Additional FDD-TDD Carrier Aggregation Band Combinations - V feature supports additional downlink (DL) carrier aggregation (CA) band combinations for two and three component carriers (CC).

18.1 LTE3688 benefits The LTE3688: Additional FDD-TDD Carrier Aggregation band combinations - V feature introduces new FDD-TDD band combinations supporting higher downlink rates in areas with overlapping cell deployments and with an enabled carrier aggregation. It provides the user with higher data peak rates within the network.

18.2 LTE3688 functional description The LTE3688: Additional FDD-TDD Carrier Aggregation Band Combinations - V feature allows the Flexi Multiradio BTS to support the following band combinations for two and three CC FDD-TDD carrier aggregation: •

FDD-TDD 2CC: – – –

•

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

FDD-TDD 3CC: –

Band 3 (FDD 5/10/15/20 MHz) + Band 40 (TDD 20 MHz) + Band 40 (TDD 10/20 MHz)

18.3 LTE3688 system impact Interdependencies between features There are no interdependencies between the LTE3688: Additional FDD-TDD Carrier Aggregation Band Combinations - V feature and any other feature. Impact on interfaces The LTE3688: Additional FDD-TDD Carrier Aggregation Band Combinations - V feature has no impact on interfaces. Impact on network management tools The LTE3688: Additional FDD-TDD Carrier Aggregation Band Combinations - V feature has no impact on network management tools. Impact on system performance and capacity

170

© 2017 Nokia

Issue: 01



The LTE3688: Additional FDD-TDD Carrier Aggregation Band Combinations - V feature has no impact on system performance or capacity.

18.4 LTE3688 reference data Requirements Table 84 System release

FDD-LTE 17SP Flexi Zone Controller

not supported

Table 85 System release

TD-LTE 17SP Flexi Zone Controller

not supported

LTE3688 hardware and software requirements Flexi Multiradio BTS

not supported


Nokia AirScale BTS

Flexi Zone BTS


FL17SP

not supported

not supported

not supported

NetAct

MME

SAE GW

OMS

UE


3GPP R12 UE support not capabilities; required 3GPP R13 UE capabilities; 3GPP R14 UE capabilities



LTE3688 hardware and software requirements Flexi Multiradio 10 BTS


Nokia AirScale BTS

Flexi Zone BTS


TL17SP

TL17SP

not supported

not supported

not supported

NetAct

MME

SAE GW

OMS


UE

3GPP R12 UE support not capabilities; required 3GPP R13 UE capabilities; 3GPP R14 UE capabilities



Alarms There are no alarms related to the LTE3688: Additional FDD-TDD Carrier Aggregation band combinations feature. BTS faults and reported alarms There are no faults related to the LTE3688: Additional FDD-TDD Carrier Aggregation band combinations feature. Commands There are no commands related to the LTE3688: Additional FDD-TDD Carrier Aggregation band combinations feature. Measurements and counters

Issue: 01

© 2017 Nokia

171



There are no measurements or counters related to the LTE3688: Additional FDD-TDD Carrier Aggregation band combinations feature. Key performance indicators There are no key performance indicators related to the LTE3688: Additional FDD-TDD Carrier Aggregation band combinations feature. Parameters There are no parameters related to the LTE3688: Additional FDD-TDD Carrier Aggregation band combinations feature. Sales information Table 86



ASW

172

License control

Pool license

© 2017 Nokia


Yes

Issue: 01


LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier

19 LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier Benefits, functionality, system impact, reference data, instructions of the feature The LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature allows the coexistence of Category-M (Cat-M) and Narrowband Internet of Things (NB-IoT) technologies within the same cell (10 MHz) on FSMF hardware.

19.1 LTE3819 benefits The LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature provides the following benefits: • •

simplifying the network configuration: one cell (10 MHz) instead of two overlapping cells can serve both Cat-M and NB-IoT devices savings on hardware: less RF modules and antennas are required, because both Cat-M and NB-IoT devices can be served by the same cell

19.2 LTE3819 functional description LTE Cat-M and Narrowband IoT There are two different standardized solutions used for low-cost IoT communication. The 3GPP Release 13 introduces two types of LTE IoT devices: Cat-M1 (in the LTE3819 feature referred to as Cat-M) and Cat NB1 (in the LTE3819 feature referred to as NBIoT). Table 87: 3GPP Release 13 LTE IoT technologies shows technical parameters of Cat-M and NB-IoT solutions. Table 87

3GPP Release 13 LTE IoT technologies

Technical info

Cat-M

NB-IoT

LTE3128: LTE-M

LTE3071: NB-IoT In-band functional description

UE receive bandwidth

1.4 MHz

200 kHz

Number of UE antennas

1

1

Duplex mode

Half duplex

Half duplex

UE transmit power

20 dBm

23 dBm

LTE IoT technologies were created to meet the requirements for an increasing number of small data packages exchanged by automated devices, such as wearables, sensors, and metering applications. Some devices can be served better with Cat-M solution, while the others require NB-IoT. Table 88: Cat-M or NB-IoT shows few examples of use cases for both Cat-M and NB-IoT technologies, depending on the criteria important for the device (data rate, latency, power consumption).

Issue: 01

© 2017 Nokia

173


Table 88


Cat-M or NB-IoT Criteria

Data rate

Cat-M

Better for a larger amount of data (hundreds of kb). Usage example: healthcare wearables

Latency

Preferred for non-time-critical devices (delay-tolerant applications). Usage example: wearables

Power consumption

Higher throughput allows the devices to go into "sleep mode" faster, which saves energy. Good for devices transmitting data in bigger, but not frequent, packages.

NB-IoT

More suitable for devices requiring very little data (tens of kb). Usage example: temperature sensors Good when bigger latency (few seconds) is not an issue. Usage example: metering devices Better for devices frequently transmitting small packets of data. Usage example: sensors and metering applications

Usage example: health wearables

The LTE3819 feature allows the eNB to serve all the above devices on the same frequency carrier. LTE3819 Functional overview The LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature allows a wider variety among the IoT UEs served by an LTE cell. Depending on its role, the IoT application may require better throughput, latency, or smaller power consumption. Thanks to the LTE3819 feature, different kinds of such applications can be accommodated in a single LTE cell. The LTE3819 feature has no activation flag. It is activated when both Cat-M (LTE3128: LTE-M ) and NB-IoT (LTE3071: NB-IoT Inband ) features are activated. Also, the LTE3582: LTE-M Enhancements I feature should be activated before activating the LTE3819 feature. The total number of Cat-M UEs is limited to 360 per LTE host cell. The maximum number of Cat-M devices that can be served by the cell is also limited by the configurable parameter ( maxNumRrcCatM). The total number of NB-IoT UEs is limited to 420 per LTE host cell. The maximum number of NB-IoT devices that can be served by the cell is also limited by the configurable parameter ( maxNumRrcNB). The LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature supports the following hardware configurations (for hardware type requirements, see the LTE3819 reference data): •

174

one FSMF system module: up to three 10 MHz 2Tx/2Rx cells (with Cat-M enabled) plus up to three in-band NB-IoT cells

© 2017 Nokia

Issue: 01



one FSMF system module plus one FBBC/FBBA extension module: up to six 10 MHz 2Tx/2Rx cells (with Cat-M enabled) plus up to six in-band NB-IoT cells one FSMF system module plus two FBBC/FBBA extension modules: up to nine 10 MHz 2Tx/2Rx cells (with Cat-M enabled) plus up to nine in-band NB-IoT cells

• •

The physical resource block (PRB) allocation for Cat-M and NB-IoT looks as follows: in downlink

•

NB-IoT: PRB 19 or PRB 30 Cat-M: PRB 43-48 (Narrowband #7)

– –

Figure 18

Downlink physical resource block (PRB) allocation for Cat-M and NB-IoT Cat-M Narrowband PDSCH

Area for NB-IoT PDSCH

0

1

2

3

4

5 6

7

8

9

10

11

12 1 3 1 4

15 1 6 1 7

18

19

20 2 1 2 2

23

24 2 5 2 6

27 2 8 2 9 3 0 3 1

32 33 34 35

36

37

38

39

40

41

42 4 3 4 4

45 4 6 4 7

48 49

in uplink (with PUCCH blanking, 8 PUCCH PRBs blanked)

•

NB-IoT: upper end of the blanked PUCCH area Cat-M: PRB 31-36 (Narrowband #5)

– –

in uplink (with PUCCH blanking, less than 8 PUCCH PRBs blanked)

•

NB-IoT: upper or lower end of the blanked PUCCH area Cat-M: PRB 31-36 (Narrowband #5)

– –

in uplink (without PUCCH blanking)

•

NB-IoT: in the inner PUSCH area Cat-M: PRB 37-42 (Narrowband #6)

– –

Figure 19

Uplink physical resource block (PRB) allocation for Cat-M and NB-IoT Cat-M Narrowband Uplink

Area for NB-IoT Uplink PRB

PUCCH blanking

With PUCCH blanking (8 PRBs, 4 PRBs on each side) 0

1

2

3

4

5

6

7

8

9

10

11

12

13 1 4 1 5 1 6 1 7 1 8 19 2 0 2 1 22 2 3 24 2 5 26 2 7 2 8 29 3 0 3 1 32 3 3 3 4 35 3 6 37 3 8 39 4 0 41 4 2 43 4 4 45

11

12 1 3 1 4 1 5 1 6 1 7

10

11

12

46 47 48 49

With PUCCH blanking (6 PRBs, 3 PRBs on each side) 0

1

2 3

4

5

6

7

8

9

10

1 8 1 9 20 2 1 2 2 23 24 2 5 2 6

27 2 8 2 9 3 0 3 1 32

33 3 4 3 5 3 6 3 7 3 8 3 9 4 0 41

42 4 3 4 4 4 5 4 6 4 7 4 8 4 9

With PUCCH blanking (4 PRBs, 2 PRBs on each side ) 0

1

2

3

4

5 6

7

8

9

13

14

15 1 6 1 7 1 8 1 9 2 0 2 1 2 2 2 3 2 4 2 5 2 6 2 7 2 8 2 9 3 0 3 1 3 2 33 3 4 35 36 37 38 3 9 4 0 4 1 4 2 4 3 4 4

45 4 6 4 7 4 8 4 9

With PUCCH blanking (2 PRBs, 1 PRB on each side) 0

1

2 3

4

5

6

7

8

9

10

11

12 1 3 1 4 1 5 1 6 1 7

5 6

7

8

9

10

11

12

1 8 1 9 20 2 1 2 2

23 24 2 5 2 6

27 2 8 2 9 3 0 3 1 32

33 3 4 3 5 3 6 3 7 3 8 3 9 4 0 41

42 4 3 4 4 4 5 4 6 4 7 4 8 4 9

Without PUCCH blanking 0

Issue: 01

1

2

3

4

13

14

15 1 6 1 7 1 8 1 9 2 0 2 1 2 2 2 3 2 4 2 5 2 6 2 7 28 29 30

© 2017 Nokia

31 32

33 3 4 3 5 3 6 3 7 3 8 3 9 4 0 41 42 43 4 4

45 4 6 4 7 4 8 4 9

175



19.3 LTE3819 system impact LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features The following features must be activated before activating the LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature: • • •

LTE3071: NB-IoT Inband LTE3128: LTE-M LTE3582: LTE-M Enhancements I

The following features must be deactivated before activating the LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature: • • • • • • • • • • • • • • • • • • • • • •

LTE48: Support of High Speed Users LTE495: OTDOA LTE825: Uplink outer region scheduling LTE944: PUSCH masking LTE1059: Uplink multi-cluster scheduling LTE1113: eICIC - macro LTE1203: Load based Power Saving with Tx path switching off LTE1382: Cell resource groups LTE1542: FDD Supercell LTE1709: Liquid Cell LTE1800: Downlink interference shaping LTE1891: eNode B power saving - Micro DTX LTE1900: Centralized RAN LTE2091: FDD SuperCell extension LTE2180: FDD-TDD downlink carrier aggregation 2CC LTE2270: LTE TDD+FDD inter eNB CA basic BTS configurations LTE2445: Combined Supercell LTE2465: CSG cell support LTE2612: ProSe Direct Communications for Public Safety LTE2733: Baseband pooling LTE3264: Additional PRS subframe configurations LTE3268: Combined Supercell for HetNet

The LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature impacts the following features: •

•

176

LTE2823: RRC connection triggered access class barring The RRC connection triggered access class barring functionality introduced by the LTE2823 feature takes into account Cat-M (numRrcCatM) and NB-IoT (numRrcNB) users. LTE3722: NB-IoT: Additional configurations (4Rx, 4Tx or 1Tx eNB support)

© 2017 Nokia

Issue: 01



The LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature is impacted by the following features: •

•

• •

LTE786: Flexible UL Bandwidth The Cat-M and NB-IoT in the same cell support both enabled and disabled PUCCH blanking. Up to 4 PRBs on each side of the spectrum can be blanked for PUCCH. If the PUCCH blanking is enabled, the NB-IoT uplink PRB must be located inside the PUCCH blanking area. LTE1130: Dynamic PUCCH allocation The LTE3819 feature supports LTE1130 activated scenarios. Dynamic PUCCH allocation for legacy UEs (not IoT UEs) introduced by the LTE1130 is a prerequisite for the LTE3128 and LTE3819 features. LTE3668: NB-IoT: Coverage enhancements The LTE3668 repetition logic is valid for the LTE3819 feature. LTE3669:NB-IoT: Paging support The LTE3669 paging logic is valid for the LTE3819 feature.

Impact on interfaces The LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature has no impact on interfaces. Impact on network management tools The LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature has no impact on network management tools. Impact on system performance and capacity The LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature impacts system performance and capacity as follows: • • •

Maximum number of Cat-M UEs in the wideband cell is 360. Maximum number of NB-IoT UEs in the cell is 420. The sum of all UE types in the host cell cannot exceed 840 (including Cat-M and NBIoT UEs).

19.4 LTE3819 reference data LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements Table 89


Issue: 01

FDD

TDD

System release

FDD-LTE 17A

Not supported


FL17A

Not supported


Not supported

Not supported

© 2017 Nokia

177


Table 89



FDD

TDD

Nokia AirScale BTS

Not supported

Not supported

Flexi Zone BTS

FL17A

Not supported


Not supported

Not supported


Not supported

Not supported

OMS


Not supported

NetAct


Not supported

MME

NetAct 17.8

Not supported

SAE GW


Not supported

UE


Not supported

Alarms There are no alarms related to the LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature. BTS faults and reported alarms There are no faults related to the LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature. Commands There are no commands related to the LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature. Measurements and counters There are no measurements or counters related to the LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature. Key performance indicators There are no key performance indicators related to the LTE3819: IoT: Cat-M and NB-IoT on Same Frequency Carrier feature. Parameters Table 90


Full name

178

Abbreviated name

Managed object

NBIoT inband downlink PRB index

inbandPRBIndexD L

NBIOT_FDD

-

FDD

NBIoT inband uplink PRB index

inbandPRBIndexU L

NBIOT_FDD

-

FDD

Activate LTE-M feature

actCatM

LNCEL_FDD

-

FDD

© 2017 Nokia

Parent structure

FDD/TDD

Issue: 01

Nokia LTE 17A Features Description and Instructions

Recommend Documents