You are on page 1of 195

Features

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

FDD-LTE17,FeatureDescriptionsandInstructions

The information in this document applies solely to the hardware/software product (Product) specified
herein,andonlyasspecifiedherein.ReferencetoNokialaterinthisdocumentshallmeantherespective
companywithinNokiaGroupofCompanieswithwhomyouhaveenteredintotheAgreement(asdefined
below).

ThisdocumentisintendedforusebyNokia'scustomers(You)only,anditmaynotbeusedexceptforthe
purposes defined in the agreement between You and Nokia (Agreement) under which this document is
distributed.Nopartofthisdocumentmaybeused,copied,reproduced,modifiedortransmittedinanyform
or means without the prior written permission of Nokia. If You have not entered into an Agreement
applicabletotheProduct,orifthatAgreementhasexpiredorhasbeenterminated,Youmaynotusethis
documentinanymannerandYouareobligedtoreturnittoNokiaanddestroyordeleteanycopiesthereof.

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

This document and its contents are provided as a convenience to You. Any information or statements
concerningthesuitability,capacity,fitnessforpurposeorperformanceoftheProductaregivensolelyon
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
limitedtothecorrectionofsucherror(s).NokiadoesnotwarrantthattheuseofthesoftwareintheProduct
willbeuninterruptedorerror-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDINGBUTNOTLIMITEDTOSPECIAL,DIRECT,INDIRECT,INCIDENTALORCONSEQUENTIAL
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
FROMTHISDOCUMENTORITSCONTENT.

ThisdocumentisNokiaproprietaryandconfidentialinformation,whichmaynotbedistributedordisclosed
toanythirdpartieswithoutthepriorwrittenconsentofNokia.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
maybetrademarksoftheirrespectiveowners.

Copyright2017Nokia.Allrightsreserved.

f Important Notice on Product Safety


Thisproductmaypresentsafetyrisksduetolaser,electricity,heat,andothersourcesofdanger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this
productandonlyafterhavingcarefullyreadthesafetyinformationapplicabletothisproduct.

The safety information is provided in the Safety Information section in the Legal, Safety and
EnvironmentalInformationpartofthisdocumentordocumentationset.

Nokiaiscontinuallystrivingtoreducetheadverseenvironmentaleffectsofitsproductsandservices.We
would like to encourage you as our customers and users to join us in working towards a cleaner, safer
environment.Pleaserecycleproductpackagingandfollowtherecommendationsforpoweruseandproper
disposalofourproductsandtheircomponents.

IfyoushouldhavequestionsregardingourEnvironmentalPolicyoranyoftheenvironmentalserviceswe
offer,pleasecontactusatNokiaforanyadditionalinformation.

2 2017Nokia DN09237915Issue:01A
FDD-LTE17,FeatureDescriptionsandInstructions

Table of Contents
Thisdocumenthas195pages

Summaryofchanges................................................................... 13

1 Introduction.................................................................................. 14

2 ActivatinganddeactivatingLTEfeaturesusingBTSSiteManager.
15

3 Descriptionsofradioresourcemanagementandtelecomfeatures.
17
3.1 LTE1834:LTEMBMSServiceContinuity.....................................17
3.1.1 LTE1834benefits......................................................................... 17
3.1.2 LTE1834functionaldescription.................................................... 17
3.1.3 LTE1834systemimpact............................................................... 18
3.1.4 LTE1834referencedata...............................................................22
3.1.5 ActivatingLTE1834:LTEMBMSServiceContinuity................... 25
3.1.6 ConfiguringLTE1834:LTEMBMSServiceContinuity................. 26
3.1.6.1 ConfiguringPrioritize VoLTE over MBMS
(prioritizeVoLTEoverMBMS)andinter-frequencyrelated
parameters................................................................................... 26
3.1.6.2 AssigningaSIB15profilewiththeSIB15 profile
identifier (sib15ProfileId)parameter.......................27
3.1.6.3 ConfigureSAIsofinter-frequencyneighborcellsinSIB15PR..... 28
3.1.6.4 ConfigureSAIsofintra-frequencyneighborcells.........................30
3.1.6.5 AddingalistitemtotheSIBinstanceofanycellwhichshall
broadcastSIB15...........................................................................31
3.1.7 DeactivatingLTE1834:LTEMBMSServiceContinuity................ 33
3.2 LTE2410:RoamingandAccessRestrictionsRemovalforCSFB
EmergencyCalls.......................................................................... 34
3.2.1 LTE2410benefits......................................................................... 34
3.2.2 LTE2410functionaldescription.................................................... 34
3.2.3 LTE2410systemimpact............................................................... 35
3.2.4 LTE2410referencedata...............................................................35
3.3 LTE2466:S1HandovertowardsHybridCells.............................. 36
3.3.1 LTE2466benefits......................................................................... 37
3.3.2 LTE2466functionaldescription.................................................... 37
3.3.3 LTE2466systemimpact............................................................... 38
3.3.4 LTE2466referencedata...............................................................40
3.3.5 ActivatingandconfiguringLTE2466.............................................42
3.3.6 DeactivatingLTE2466.................................................................. 45
3.4 LTE2572:RSRQ-basedB2.......................................................... 47
3.4.1 LTE2572benefits......................................................................... 47
3.4.2 LTE2572functionaldescription.................................................... 47
3.4.2.1 LTE2572overview........................................................................49
3.4.2.2 B2RSRQconditions.................................................................... 50

DN09237915Issue:01A 2017Nokia 3
FDD-LTE17,FeatureDescriptionsandInstructions

3.4.3 LTE2572:systemimpact.............................................................. 50
3.4.4 LTE2572referencedata...............................................................50
3.4.5 ActivatingLTE2572...................................................................... 52
3.4.6 DeactivatingLTE2572.................................................................. 54
3.5 LTE2664:Load-basedPUCCHRegion........................................55
3.5.1 LTE2664benefits......................................................................... 55
3.5.2 LTE2664functionaldescription.................................................... 56
3.5.3 LTE2664systemimpact............................................................... 60
3.5.4 LTE2664referencedata...............................................................60
3.5.5 ActivatingandconfiguringLTE2664.............................................63
3.5.6 DeactivatingLTE2664.................................................................. 66
3.6 LTE3047:AdditionalCarrierAggregationBandCombinations2CC
V................................................................................................68
3.6.1 LTE3047benefits......................................................................... 68
3.6.2 LTE3047functionaldescription.................................................... 69
3.6.3 LTE3047systemimpact............................................................... 69
3.6.4 LTE3047referencedata...............................................................70
3.7 LTE3048:AdditionalCarrierAggregationBandCombinations3CC
III............................................................................................... 71
3.7.1 LTE3048benefits......................................................................... 71
3.7.2 LTE3048functionaldescription.................................................... 71
3.7.3 LTE3048systemimpact............................................................... 72
3.7.4 LTE3048referencedata...............................................................73
3.8 LTE3049:AdditionalFDD-TDDCarrierAggregationBand
CombinationsII......................................................................... 74
3.8.1 LTE3049benefits......................................................................... 74
3.8.2 LTE3049functionaldescription.................................................... 74
3.8.3 LTE3049systemimpact............................................................... 75
3.8.4 LTE3049referencedata...............................................................75
3.9 LTE3056:GPSandUTCTimeInformationBroadcastSupport
(SIB16)........................................................................................ 76
3.9.1 LTE3056benefits......................................................................... 77
3.9.2 LTE3056functionaldescription.................................................... 77
3.9.3 LTE3056systemimpact............................................................... 77
3.9.4 LTE3056referencedata...............................................................78
3.9.5 ActivatingandconfiguringLTE3056.............................................80
3.9.6 DeactivatingLTE3056.................................................................. 82
3.10 LTE3073:256QAMExtensions................................................... 84
3.10.1 LTE3073benefits......................................................................... 84
3.10.2 LTE3073functionaldescription.................................................... 84
3.10.3 LTE3073systemimpact............................................................... 85
3.10.4 LTE3073referencedata...............................................................85
3.10.5 ActivatingLTE3073...................................................................... 90
3.10.6 DeactivatingLTE3073.................................................................. 90
3.11 LTE3199:SupportforMultipleMBSFNandSynchronizationAreas
..................................................................................................... 90
3.11.1 LTE3199benefits......................................................................... 90

4 2017Nokia DN09237915Issue:01A
FDD-LTE17,FeatureDescriptionsandInstructions

3.11.2 LTE3199functionaldescription.................................................... 91
3.11.3 LTE3199systemimpact............................................................... 92
3.11.4 LTE3199referencedata...............................................................95
3.12 LTE3201:eMBMSinRAN-sharingDeploymentSupport............. 99
3.12.1 LTE3201benefits......................................................................... 99
3.12.2 LTE3201functionaldescription.................................................. 100
3.12.3 LTE3201systemimpact............................................................. 100
3.12.4 LTE3201referencedata.............................................................101
3.13 LTE3213:AdditionalUplinkCarrierAggregationBand
CombinationsI........................................................................ 103
3.13.1 LTE3213benefits....................................................................... 103
3.13.2 LTE3213functionaldescription.................................................. 103
3.13.3 LTE3213systemimpact............................................................. 103
3.13.4 LTE3213referencedata.............................................................104
3.14 LTE3230:ULInterferenceOffsets..............................................105
3.14.1 LTE3230benefits....................................................................... 105
3.14.2 LTE3230functionaldescription.................................................. 105
3.14.3 LTE3230systemimpact............................................................. 108
3.14.4 LTE3230referencedata.............................................................109
3.14.5 ActivatingandconfiguringLTE3230forband18........................110
3.14.6 ActivatingandconfiguringLTE3230forband30........................113
3.14.7 DeactivatingLTE3230................................................................ 115
3.15 LTE3264:AdditionalPRSSubframeConfigurations.................. 117
3.15.1 LTE3264benefits........................................................................117
3.15.2 LTE3264functionaldescription.................................................. 117
3.15.3 LTE3264systemimpact............................................................. 118
3.15.4 LTE3264referencedata............................................................. 119
3.15.5 ActivatingLTE3264.................................................................... 121
3.15.6 DeactivatingLTE3264................................................................ 121
3.16 LTE3279:SupportforConfigurableeMBMSSYNCProtocol.....121
3.16.1 LTE3279benefits....................................................................... 122
3.16.2 LTE3279functionaldescription.................................................. 122
3.16.3 LTE3279systemimpact............................................................. 124
3.16.4 LTE3279referencedata.............................................................125
3.16.5 ActivatingandconfiguringLTE3279...........................................127
3.16.5.1 ConfigurationdetailsofLTE3279............................................... 129
3.16.6 DeactivatingLTE3279................................................................ 130
3.17 LTE3290:SRVCCTriggerEnhancement................................... 131
3.17.1 LTE3290benefits....................................................................... 132
3.17.2 LTE3290functionaldescription.................................................. 132
3.17.3 LTE3290systemimpact............................................................. 133
3.17.4 LTE3290referencedata.............................................................134
3.17.5 ActivatingandconfiguringLTE3290...........................................136
3.17.6 DeactivatingLTE3290................................................................ 138
3.18 LTE3439:AdditionalCarrierAggregationBandCombinations4CC
I............................................................................................... 140

DN09237915Issue:01A 2017Nokia 5
FDD-LTE17,FeatureDescriptionsandInstructions

3.18.1 LTE3439benefits....................................................................... 140


3.18.2 LTE3439functionaldescription.................................................. 140
3.18.3 LTE3439systemimpact............................................................. 141
3.18.4 LTE3439referencedata.............................................................142

4 Descriptionsoftransportandtransmissionfeatures.................. 143
4.1 LTE2807:IPv6SupportforM1andM3Interfaces..................... 143
4.1.1 LTE2807benefits....................................................................... 143
4.1.2 LTE2807functionaldescription.................................................. 143
4.1.3 LTE2807systemimpact............................................................. 147
4.1.4 LTE2807referencedata.............................................................147
4.1.5 ActivatingandconfiguringLTE2807...........................................149
4.1.6 DeactivatingLTE2807................................................................ 151
4.2 LTE2855:FronthaulActiveWDM............................................... 152
4.2.1 LTE2855benefits....................................................................... 152
4.2.2 LTE2855functionaldescription.................................................. 152
4.2.3 LTE2855systemimpact............................................................. 154
4.2.4 LTE2855referencedata.............................................................154

5 Descriptionsofoperabilityfeatures........................................... 156
5.1 LTE684:DHCPServerforFlexiLTEBTSSiteDevices............. 156
5.1.1 LTE684benefits......................................................................... 156
5.1.2 LTE684functionaldescription.................................................... 156
5.1.3 LTE684systemimpact............................................................... 157
5.1.4 LTE684referencedata...............................................................157
5.1.5 Otherinstructions....................................................................... 158
5.2 LTE3134:FDD-LTE17SystemUpgrade................................... 161
5.2.1 LTE3134benefits....................................................................... 161
5.2.2 LTE3134functionaldescription.................................................. 162
5.2.3 LTE3134systemimpact............................................................. 165
5.2.4 LTE3134referencedata.............................................................166
5.2.5 UpgradingtheLTEeNBtoLTE17............................................. 167
5.2.6 Rollingbacktheupgrade........................................................... 168
5.3 LTE3296/SR001527:HarmonizedObjectModelforSRANand
LTE............................................................................................. 170
5.3.1 LTE3296/SR001527benefits..................................................... 170
5.3.2 LTE3296/SR001527functionaldescription................................ 170
5.3.3 LTE3296/SR001527systemimpact........................................... 177
5.3.4 LTE3296/SR001527referencedata...........................................178
5.4 LTE3303:EnhancedVoLTE,CA,andRFQualityMonitoring.... 179
5.4.1 LTE3303benefits....................................................................... 179
5.4.2 LTE3303functionaldescription.................................................. 179
5.4.3 LTE3303systemimpact............................................................. 179
5.4.4 LTE3303referencedata.............................................................179

6 DescriptionsofBTSsitesolutionfeatures................................. 184
6.1 LTE2495:Plug-inRadioSWInterfaceforNokiaCPRI..............184

6 2017Nokia DN09237915Issue:01A
FDD-LTE17,FeatureDescriptionsandInstructions

6.1.1 LTE2495benefits....................................................................... 184


6.1.2 LTE2495functionaldescription.................................................. 184
6.1.3 LTE2495systemimpact............................................................. 185
6.1.4 LTE2495referencedata.............................................................186
6.2 LTE2769:FRGXFlexiRFM3-pipe2100240W........................ 186
6.2.1 LTE2769benefits....................................................................... 187
6.2.2 LTE2769functionaldescription.................................................. 187
6.2.3 LTE2769systemimpact............................................................. 188
6.2.4 LTE2769referencedata.............................................................188
6.3 LTE3133:FRCIFlexiRRH2T2R875120W............................. 189
6.3.1 LTE3133benefits....................................................................... 189
6.3.2 LTE3133functionaldescription.................................................. 189
6.3.3 LTE3133systemimpact............................................................. 191
6.3.4 LTE3133referencedata.............................................................192
6.4 InterdependenciesbetweenCPRI-Afeaturesandotherfeatures....
193

DN09237915Issue:01A 2017Nokia 7
FDD-LTE17,FeatureDescriptionsandInstructions

List of Figures
Figure1 LTEB2event...................................................................................... 49
Figure2 PUCCHresourceallocationinLTE2664............................................ 56
Figure3 PUCCHexpansionprocedure............................................................ 58
Figure4 PUCCHexpansionprocedure(systemInfoValueTag>LNBTS:
sibUpdateThreshold)..................................................................58
Figure5 ContentoftheSIB16,asdescribedin3GPPTS36.331....................77
Figure6 LTE825: Uplink Outer Region Scheduling andLTE3230: UL
Interference Offsetsfeaturecomparison.......................................... 106
Figure7 VoLTEcallsetupwithSRVCCdelaytimer....................................... 132
Figure8 HandlingtheSRVCCdelaytimerduringSRVCC(toWCDMA/GSM)....
133
Figure9 OverviewM1/M3interface................................................................144
Figure10 M3interface......................................................................................146
Figure11 M1interface......................................................................................146
Figure12 FronthaulActiveWDMcomponents................................................. 154
Figure13 PathDHCPServer........................................................................... 159
Figure14 DHCPconfigurations........................................................................ 160
Figure15 Toplevelobjectsinthehierarchy..................................................... 171
Figure16 TheEQMandEQM_Robjecttrees..................................................172
Figure17 TheMNLtree....................................................................................174
Figure18 TheMNLENTsubtree.......................................................................174
Figure19 TheLNBTStree................................................................................176
Figure20 TheLNCELtree................................................................................177
Figure21 FULLDELIVERYMODEwithouttheLTE2495:Plug-inRadioSW
InterfaceforNokiaCPRIfeature...................................................... 185
Figure22 FASTDELIVERYMODEwiththeLTE2495:Plug-inRadioSW
InterfaceforNokiaCPRIfeature...................................................... 185

8 2017Nokia DN09237915Issue:01A
FDD-LTE17,FeatureDescriptionsandInstructions

List of Tables
Table1 LTE1834: LTE MBMS Service Continuityhardwareandsoftware
requirements.......................................................................................22
Table2 NewalarmsintroducedbyLTE1834: LTE MBMS Service Continuity.....
22
Table3 NewBTSfaultsintroducedbyLTE1834: LTE MBMS Service
Continuity............................................................................................22
Table4 NewcountersintroducedbyLTE1834: LTE MBMS Service Continuity..
23
Table5 NewparametersintroducedbyLTE1834: LTE MBMS Service
Continuity............................................................................................23
Table6 ExistingparametersrelatedtoLTE1834: LTE MBMS Service
Continuity............................................................................................24
Table7 LTE1834: LTE MBMS Service Continuitysalesinformation............... 24
Table8 LTE2410hardwareandsoftwarerequirements..................................35
Table9 NewparametersintroducedbyLTE2410........................................... 36
Table10 LTE2410salesinformation................................................................. 36
Table11 LTE2466hardwareandsoftwarerequirements..................................40
Table12 NewcountersintroducedbyLTE2466................................................40
Table13 NewkeyperformanceindicatorsintroducedbyLTE2466.................. 41
Table14 NewparametersintroducedbyLTE2466........................................... 42
Table15 ExistingparametersrelatedtoLTE2466............................................ 42
Table16 LTE2466salesinformation................................................................. 42
Table17 Conditionsfortheinter-RATmeasurementsperiod........................... 50
Table18 LTE2572hardwareandsoftwarerequirements..................................51
Table19 NewparametersintroducedbyLTE2572........................................... 51
Table20 LTE2572salesinformation................................................................. 52
Table21 LTE2664hardwareandsoftwarerequirements..................................61
Table22 NewcountersintroducedbyLTE2664................................................61
Table23 ExistingcountersrelatedtoLTE2664................................................. 61
Table24 ExistingparametersrelatedtoLTE2664............................................ 61
Table25 LTE2664salesinformation................................................................. 63
Table26 LTE3047hardwareandsoftwarerequirements..................................70
Table27 LTE3047salesinformation................................................................. 70
Table28 LTE3048hardwareandsoftwarerequirements..................................73
Table29 LTE3048salesinformation................................................................. 73
Table30 LTE3049hardwareandsoftwarerequirementsforFDD.................... 75
Table31 LTE3049hardwareandsoftwarerequirementsforTDD.................... 75
Table32 LTE3049salesinformation................................................................. 76
Table33 LTE3056: GPS and UTC Time Information Broadcast Support (SIB16)
hardwareandsoftwarerequirements................................................. 78

DN09237915Issue:01A 2017Nokia 9
FDD-LTE17,FeatureDescriptionsandInstructions

Table34 NewparametersintroducedbyLTE3056: GPS and UTC Time


Information Broadcast Support (SIB16)..............................................79
Table35 ParametersmodifiedbyLTE3056: GPS and UTC Time Information
Broadcast Support (SIB16).................................................................79
Table36 ExistingparametersrelatedtoLTE3056: GPS and UTC Time
Information Broadcast Support (SIB16)..............................................79
Table37 ParametersmigratedfromMOCXPARAMtoMOCSIBforLTE3056:
GPS and UTC Time Information Broadcast Support (SIB16).............80
Table38 LTE3056: GPS and UTC Time Information Broadcast Support (SIB16)
salesinformation................................................................................ 80
Table39 LTE3073hardwareandsoftwarerequirements..................................85
Table40 NewcountersintroducedbyLTE3073................................................86
Table41 ExistingcountersrelatedtoLTE3073................................................. 86
Table42 NewparametersintroducedbyLTE3073........................................... 87
Table43 ParametersmodifiedbyLTE3073...................................................... 88
Table44 ExistingparametersrelatedtoLTE3073............................................ 89
Table45 LTE3073salesinformation................................................................. 89
Table46 LTE3199hardwareandsoftwarerequirements..................................95
Table47 ExistingalarmsrelatedtoLTE3199.................................................... 95
Table48 NewBTSfaultsintroducedbyLTE3199............................................. 95
Table49 NewparametersintroducedbyLTE3199........................................... 96
Table50 ParametersmodifiedbyLTE3199...................................................... 96
Table51 ExistingparametersrelatedtoLTE3199........................................... 97
Table52 LTE3199salesinformation................................................................. 99
Table53 LTE3201hardwareandsoftwarerequirements................................101
Table54 ExistingalarmsrelatedtoLTE3201.................................................. 101
Table55 ExistingBTSfaultsrelatedtoLTE3201............................................ 101
Table56 NewparametersintroducedbyLTE3201:eMBMSinRAN-sharing
DeploymentSupport.........................................................................102
Table57 Modified/impactedparametersbyLTE3201:eMBMSinRAN-sharing
DeploymentSupport.........................................................................102
Table58 LTE3201salesinformation............................................................... 102
Table59 LTE3213hardwareandsoftwarerequirements................................104
Table60 LTE3213salesinformation............................................................... 104
Table61 LTE3230: UL Interference OffsetsparameteractUlPwrRestrScn
configurationcases...........................................................................107
Table62 LTE3230: UL Interference Offsetshardwareandsoftware
requirements.....................................................................................109
Table63 NewparametersintroducedbyLTE3230: UL Interference Offsets........
110
Table64 LTE3230: UL Interference Offsetssalesinformation........................ 110
Table65 LTE3264hardwareandsoftwarerequirements................................ 119
Table66 ExistingparametersrelatedtoLTE3264...........................................119

10 2017Nokia DN09237915Issue:01A
FDD-LTE17,FeatureDescriptionsandInstructions

Table67 LTE3264salesinformation............................................................... 121


Table68 LTE3279hardwareandsoftwarerequirements................................125
Table69 NewcountersintroducedbyLTE3279..............................................125
Table70 NewparametersintroducedbyLTE3279......................................... 126
Table71 ExistingparametersrelatedtoLTE3279.......................................... 126
Table72 LTE3279salesinformation............................................................... 126
Table73 LTE3290hardwareandsoftwarerequirements................................134
Table74 ExistingcountersrelatedtoLTE3290............................................... 134
Table75 ExistingkeyperformanceindicatorsrelatedtoLTE3290................. 135
Table76 NewparametersintroducedbyLTE3290......................................... 136
Table77 ExistingparametersrelatedtoLTE3290.......................................... 136
Table78 LTE3290salesinformation............................................................... 136
Table79 LTE3439hardwareandsoftwarerequirements................................142
Table80 LTE3439salesinformation............................................................... 142
Table81 Explanations:OverviewoftheM1/M3interface............................... 144
Table82 LTE2807hardwareandsoftwarerequirements................................148
Table83 ExistingalarmsrelatedtoLTE2807.................................................. 148
Table84 BTSfaultsintroducedbyLTE2807................................................... 148
Table85 NewparametersintroducedbyLTE2807......................................... 148
Table86 ExistingparametersrelatedtoLTE2807.......................................... 149
Table87 LTE2807salesinformation............................................................... 149
Table88 LTE2855hardwareandsoftwarerequirements................................154
Table89 LTE2855salesinformation............................................................... 155
Table90 LTE684hardwareandsoftwarerequirements..................................157
Table91 NewparametersintroducedbyLTE684........................................... 158
Table92 LTE684salesinformation................................................................. 158
Table93 LTE3134hardwareandsoftwarerequirements................................166
Table94 LTE3134salesinformation............................................................... 166
Table95 LTE3296/SR001527softwarerequirements.....................................178
Table96 LTE3296/SR001527salesinformation............................................. 179
Table97 LTE3303hardwareandsoftwarerequirements................................179
Table98 E-RABreleaseduetointer-RAThandoverstoUTRANorGERAN
countersintroducedbyLTE3303...................................................... 180
Table99 E-RABreleaseduetoS1interfacereasonscountersintroducedby
LTE3303........................................................................................... 180
Table100 VoLTEPRBusagecounterintroducedbyLTE3303......................... 181
Table101 HARQBLERcountersintroducedbyLTE3303................................ 181
Table102 UEcontextreleasecountersintroducedbyLTE3303...................... 182
Table103 VoLTETTIbundlingcountersintroducedbyLTE3303..................... 182
Table104 Carrieraggregation(CA)downlinkdeconfigurationcounters
introducedbyLTE3303.....................................................................182

DN09237915Issue:01A 2017Nokia 11
FDD-LTE17,FeatureDescriptionsandInstructions

Table105 PMQAPprofilecountersintroducedbyLTE3303............................. 183


Table106 LTE3303salesinformation............................................................... 183
Table107 LTE2495hardwareandsoftwarerequirements................................186
Table108 LTE2495salesinformation............................................................... 186
Table109 LTE2769: FRGX Flexi RFM 3-pipe 2100 240 Whardwareand
softwarerequirements...................................................................... 189
Table110 LTE2769: FRGX Flexi RFM 3-pipe 2100 240 Wsalesinformation.. 189
Table111 FRCIfunctionalspecification............................................................ 189
Table112 LTE3133hardwareandsoftwarerequirements................................192
Table113 LTE3133salesinformation............................................................... 192
Table114 InterdependenciesbetweenCPRI-Afeaturesandotherfeatures.... 193

12 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Summaryofchanges

Summary of changes
Changes between issues 01 (2016-12-30, FDD-LTE17) and 01A (2017-02-03, FDD-
LTE17)
Thefollowingfeatureshavebeenupdated:
Radio Resource Management

LTE1834: eMBMS service continuity (only partly, feature to be split)


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

Operability

LTE684: DHCP Server for Flexi LTE BTS Site Devices

Thefollowingfeatureshavebeenadded:
BTS Site Solution
InformationonthefollowingfeatureshasbeeaddedtotheInterdependencies
between CPRI-A features and other featuressection:
LTE3307:UHIEB66aRRH4X45CPRI-ARRH4-Pipe1.7/2.1160W
LTE3308:UHFDAAB25A+700/900PCPRI-AActiveAntenna2-Pipe1900
80W
LTE3309:UHCBRRH2x60-850CPRI-ARRH2-Pipe85080W
LTE3350:UHFFRRH2x60-1900CPRI-ARRH2-Pipe1900120W
LTE3409:UHIF9768MROB41WCPRI-AMRORRH2-Pipe1700/2100
LTE3410:UHIG9768cMROB4/665WCPRI-AMRORRH2-Pipe1700/2100
LTE3413:UHBF9768MROB131WCPRI-AMRORRH2-Pipe700

DN09237915Issue:01A 2017Nokia 13

Introduction FDD-LTE17,FeatureDescriptionsandInstructions

1 Introduction
ThisdocumentprovidesthelistoffeaturedescriptionsfortheLTERadioAccess
NetworkRelease.
Hardware(HW)requirementsindicateifthefeaturerequiresspecificHWfromtheRAN
LTEportfolio.Ifthefeaturehasnospecifichardwarerequirements,itmeansthatonly
LTESystemModuleshouldbeused.
Thesubchapter Interdependencies between featureslistsonlydependenciesamong
NokiaRANLTEfeatures.
FDD-LTE17supportsonlyAirScalehardware.

14 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions ActivatinganddeactivatingLTEfeaturesusingBTSSite
Manager

2 Activating and deactivating LTE features


using BTS Site Manager
Purpose
FollowthisgeneralBTSSiteManager(BTSSM)proceduretoactivateordeactivateLTE
features.

Before you start


TheeNBmustalreadybecommissioned.TheBTSSiteManagercanbeconnectedto
theeNBeitherlocally,orfromaremotelocation.Forinformationonfeature-specific
prerequisites,seesectionBefore you start ofeveryfeature-specificprocedure.

Steps

1 Start the BTSSM application and establish the connection to the eNB.
Fordetails,seeLaunching BTS Site ManagerinCommissioning Flexi Multiradio BTS
LTEortheBTSSMonlinehelp(section Instructions).

2 Upload the configuration plan file from the eNB.


WhentheBTSSMisconnectedtotheeNB,itautomaticallyuploadsthecurrent
configurationplanfilefromtheeNB.
a) SelectViewCommissioningorclickCommissioningontheViewbar.
b) TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.
c) Choosethecommissioningtype.UsetheTemplate,Manual,or
ReconfigurationoptiondependingontheactualstateoftheeNB.
Fordetails,seeManual commissioning,Performing template commissioning,and
Performing reconfiguration commissioninginCommissioning Flexi Multiradio BTS
LTE.

3 Modify the feature-specific eNB configuration settings.


Thefeature-relatedsettingsarefoundinthesetofCommissioning pages.Inthetop
right-handcorneroftheBTSSMwindow,thereisalocationbarthatshowsatwhich
stageoftheCommissioning processtheuseris.Itisrecommendedthattheuser
carefullyreadsthepagescontainingfulleNBconfigurationinformation.

DN09237915Issue:01A 2017Nokia 15

ActivatinganddeactivatingLTEfeaturesusingBTSSite FDD-LTE17,FeatureDescriptionsandInstructions
Manager

4 Send the commissioning plan file to the eNB.


Sub-steps

a) Go to the Send Parameters page.

b) In section Send, choose whether the BTSSM should send to the eNB only
the changed parameters: Only changes (may require reset), or a whole set
of parameters: All parameters (requires reset).

c) Click the Send Parameters button.

5 The new commissioning plan file is automatically activated in the eNB.


Sub-steps

a) After successful transmission of the parameters, the new configuration is


automatically activated.
TheBTSSMautomaticallysendsanactivationcommandafterfinishingthefile
download.

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

g Note: Forinformationonpossiblerestarts,seesectionBefore you startofevery


feature-specificprocedure.

16 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

3 Descriptions of radio resource management


and telecom features

3.1 LTE1834: LTE MBMS Service Continuity


TheLTE1834: LTE MBMS Service Continuityfeatureisapackageoffunctionalities
introducedformultimediabroadcast/multicastservice(MBMS)operationinnetworkswith
multiplecarriersdeployed.ThefeatureenablesUEstoreceiveMBMSservicesinaradio
resourcecontrol(RRC)idlemodeaswellasinanRRC-connectedmode.

3.1.1 LTE1834 benefits


TheLTE1834: LTE MBMS Service Continuityfeatureprovidesthefollowingbenefit:
ItenablestheoperatorstoofferseamlessMBMSbroadcastservicestoendusersin
multi-carrierLTEnetworks.

3.1.2 LTE1834 functional description


Functional description
TheLTE1834: LTE MBMS Service Continuityfeatureisapackageoffunctionalities
requiredforMBMSoperationinamulti-carrierdeploymentwhereMBMSservicesare
availableonlyonasubsetofcarriers.
AneNBtransmitsysteminformationbroadcast15(SIB15),containingtheinformation
abouttheavailabilityofMBMSserviceareaidentifiers(SAIs),ontheservingfrequency
ofacellaswellasonotherfrequenciestosupporttheUEsinanRRCidlemode.The
SIB15containsalsousefulinformationforUE-basedorUE-assistedpositioning
methods.
AfterreadingSIB15,theUEsinanRRCconnectedmodemaysendanMBMSInterest
Indication(MBMSII)totheeNB,listingLTEfrequenciesonwhichtheywanttoreceive
theMBMSservices.TheeNBusesthisMBMSIItokeeptheUEinterestedinMBMS
servicesonthosefrequencies.If,ontheotherhand,acertainUEisinterestedin
differentfrequenciesthantheservingone,theeNBtriestomovetheUEtothefrequency
ofinterest.
TheeNBsupportsabroadcastofSIB15inMBMScellsandnon-MBMScells.This
broadcastindicatesSAIliststoallUEsinanRRCidleandRRCconnectedmode.The
exchangeofaSAIlistviaanX2linkisnotsupported.
Theprimarycell(PCell)ofeNBsupportsthereceptionofMBMSIIsentbytheUEsinan
RRCconnectedmode.TheeNBusestheMBMSIIfortheUEsmobilitydecisions.
TheeNBdoesitsbesttoensurethattheUEisabletoreceiveMBMSandunicast
servicessimultaneously.
IfaUEindicatesaninterestinanMBMSfrequencythatisthesecondarycell(SCell)
carrierfrequency,theeNBtriggersaPCellswapproceduretosteertheUEtotheMBMS
layer.

DN09237915Issue:01A 2017Nokia 17

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

EmergencyandhighprioritycallsarethesubjectofMBMS-basedmobilityonlyifthey
arenotimpacted.Emergencycalls'mobilityisalwaysprioritizedoverMBMS.
TheLTE1834: LTE MBMS Service Continuityfeatureissupportedin1.4-MHz,3-MHz
and5-Mhzcellsinalimitedscope.SIB15containsonlyaninter-frequencyeMBMSSAI
list.TheeMBMSisnotsupportedinnarrowbandcells,sothecellsdonotneedthe
functionalitywhichkeepstheUEinterestedinaneMBMSservingfrequency.

Subfeatures
TheLTE1834: LTE MBMS Service Continuityfeatureissplitintothreesubfeatures:
TheLTE1834-A: MBMS Service Continuity Suport for Idle Mode UEsubfeaturehas
thefollowingfunctionalities:
featureactivation
transmissionofSIB15

TheLTE1834-B: Keep RRC CONNECTED MBMS Interested UE on MBMS Carrier


subfeaturehasthefollowingfunctionalities:
handlinganMBMSInterestIndicationreceivedfromaUE
forwardinganMBMSInterestIndicationduringhandover
excludingaUEwithanMBMSinterestonaservingfrequencyfromaload-based
handover
excludingaUEwithMBMSinterestonservingfrequency(optionally)froma
service-basedhandover
excludingaUEwithanMBMSinterestonaservingfrequencyfromidlemode
loadbalancing

TheLTE1834-C: Move RRC CONNECTED MBMS Interested UE to MBMS Carrier


subfeaturehasthefollowingfunctionalities:
best-effort-service-based-handoverforaUEwithanMBMSinterestinanon-
servingfrequency
PCellswapforaUEwithanMBMSinterestinafrequencyofaconfiguredSCell

3.1.3 LTE1834 system impact


Interdependencies between features
ThefollowingfeaturesinteractwiththeLTE1834: LTE MBMS Service Continuityfeature:
LTE1117: LTE MBMS
TheLTE1117: LTE MBMSfeatureshouldbeenabledintheecosystem,butits
enablingisnotapreconditiontoactivatetheLTE1834: LTE MBMS Service
Continuityfeature.
LTE1127: Service-based Mobility Trigger
TheLTE1127: Service-based Mobility TriggerfeatureintroducedabesteffortHO
basedonA4measurementstosendaUEtoanotherfrequency.Activationofthe
LTE1127: Service-based Mobility Triggerfeatureisnotapreconditionforthe
LTE1834: LTE MBMS Service Continuityfeature,theimplementedfunctionsare
simplyreused.
LTE2275: PCell Swap

18 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

TheLTE1834: LTE MBMS Service ContinuityfeaturerequestsaPCellswapincase


aUEwithestablishedSCell(s)indicatedMBMSinterestinthefrequencyofa
configuredSCell.
TheLTE2275: PCell Swapfeatureneedstobeactivatedtosupportthisoption.
TheLTE2275: PCell SwapfeatureisnomandatorypreconditionfortheLTE1834:
LTE MBMS Service Continuityfeature;however,theperformanceofLTE1834: LTE
MBMS Service ContinuitywillbereducedwithoutLTE2275: PCell SwapasSCells
willnotbereportedbyaregularA4measurement.Thus,nobesteffortHOcanbe
donetowardsaconfiguredSCell.

g Note: APCellswaptriggeredforMBMStrafficsteeringwillnotbeconsideredwhen
countingtheload-basedPCellswapsfortriggeringaloadbalancing(LB)PCellswap.

TheLTE1834: LTE MBMS Service Continuityfeatureimpactsthefollowingfeatures:


LTE1534: Multiple Frequency Band Indicator
LTE1534: Multiple Frequency Band Indicatorintroducesgeneralsupportformultiple
frequencybandindicators(MFBIs)forUEsinanRRC-idleandRRC-connected
mode.TheMFBIfunctionalityissupportedforhomogenousnetworkdeployments,
thatis,thesameMFBIconfigurationisappliedtoalleNBs.SIB15allowsto
broadcastmultiplefrequencybandsforinter-frequencyMBMSconfigurations.Onlyif
LTE1534: Multiple Frequency Band Indicatorisactivated,theLTE1834: LTE MBMS
Service Continuityfeatureshallsupportthebroadcastofmultiplefrequencybands
forinter-frequencyMBMSconfigurations.
LTE53: Intra- and Inter-eNodeB Handover with X2
LTE54: Intra-LTE Handover via S1
Theintra-LTEhandoverfunctionalityhastobeextendedtotransferMBMSIIfroma
sourcecelltoatargetcell.Furthermore,allfeaturesreusingtheintra-LTEhandover
preparationfromtheLTE53: Intra- and Inter-eNodeB Handover with X2orLTE54:
Intra-LTE Handover via S1featuresareimpactedinthesameway.
LTE1387: Intra-eNodeB IF Load Balancing
LTE1170: Inter-eNodeB IF Load Balancing
LTE1531: Inter-frequency Load Balancing Extension
LTE1357: LTE-UTRAN Load Balancing
LTE1841: Inter-frequency Load Equalization
Thefivefeaturesabovemakeuseofaload-basedhandover.Theyareextendedto
excludeaUEinterestedinMBMSfromLBHO.
LTE487: Idle Mode Mobility Load Balancing
LTE1677: Idle Mode Mobility Balancing Extensions
LTE2050: Load Triggered Idle Mode Mobility Load Balancing
LTE2601: CA Aware Idle Mode Mobility Load Balancing
LTE2051: Measurement Based Idle Mode Mobility Load Balancing
ThefivefeaturesaboveareextendedtoexcludeaUEinterestedinMBMSfromidle
modeloadbalancing.
ThisfeatureisextendedtoimmediatelyreleaseaUEwhichisexecutingA4
measurementsforidlemodeloadbalancingwhenanMBMSIIisreceived.
LTE1127: Service-based Mobility Trigger
LTE55: Inter-frequency Handover
LTE1060: TDD FDD Handover
LTE56: Inter-RAT Handover to WCDMA

DN09237915Issue:01A 2017Nokia 19

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

LTE872: SRVCC to WCDMA


LTE442: eNACC to GSM
LTE873: SRVCC to GSM
LTE898: TDD inter-RAT Handover to TD-SCDMA
LTE60: Inter-RAT Handover to eHRPD/3GPP2
TheeightfeaturesabovemakeuseofeitherA3/A5inter-frequencymeasurementsor
B2inter-RATmeasurementsifanA2measurementindicatesthattheradio
conditionsintheservingcellhavebecomesobadthataninter-frequencyoraninter-
RAThandoverduetoradioreasonsisdesirable.A4measurementsforanMBMS
steeringHOshallbedeconfiguredwhenA3,A5,orB2issetup.
LTE2224: Uplink-triggered Mobility
ThisfeaturemakesuseofeitherA3/A5inter-frequencymeasurementsand/orB1/B2
inter-RATmeasurementsifaneNBinternaltriggerindicatesthattheradioconditions
intheservingcellhavebecomesobadthataninter-frequencyoraninter-RAT
handoverduetoradioreasonsisdesirable.A4measurementsforMBMSsteering
HOshallbedeconfiguredwhenA3,A5,B1,orB2issetup.
LTE2108: Redirected VoLTE Call Setup
Thisfeatureintroducesforcedservice-basedhandover(SBHO)tomoveaUEwhich
wantstosetupaqualityclassindicator1(QCI1)butisservedinacellwhichdoes
notallowasetupofQCI1towardsanotherfrequency,wherethesetupofQCI1is
allowed.ForcedSBHOaccordingtotheLTE2108: Redirected VoLTE Call Setup
featureshallalwayshaveapriorityoverMBMScallsteeringaccordingtothe
LTE1834: LTE MBMS Service Continuityfeature.
LTE2503: Emergency Call Based Mobility Trigger
ThisfeatureextendsthebehaviorofLTE1127: Service-based Mobility Triggerto
enforceSBHOforaUEwithemergencyallocationandretentionpriority(ARP).
SBHOforECUEaccordingtotheLTE2503: Emergency Call Based Mobility Trigger
featureshallhaveapriorityoverMBMSinterest.
LTE2612: ProSe Direct Communications for Public Safety
ThisfeatureincludesthefunctionalitytokeepaUEwithsidelinkinterestonthe
currentservingfrequency.Therefore,noA4measurementsareconfiguredfora
sidelinkinterestedUEatall.ItisassumedthatthesidelinkinterestofaUE(whichis
forpublicsafetypurposes)shallalwayshaveapriorityoverMBMSinterest(whichis
mostlikelyforacommercialserviceinearlydeployments).Therefore,noA4
measurementsforanMBMSsteeringhandoverareconfiguredforaUEwithsidelink
interest.
LTE572: IMS Emergency Sessions
Thisfeatureintroducesthesupportforemergencysessions.Incaseanemergency
call(withQCI1withemergencyARP)ispresent,aneNBshallalwaysprioritize
SBHOoverMBMSsteeringHO,ignoringoperator'sprioritization.
LTE556: ANR Intra-LTE, Inter-frequency UE-based
ThisfeaturemakesuseofA4measurementsintendedforservice-basedhandoveror
load-basedhandoverforpassiveANRdetection.WiththeLTE1834: LTE MBMS
Service Continuityfeature,theLTE556: ANR Intra-LTE, Inter-frequency UE-based
featuremaymakeuseofA4measurementsforMBMSsteeringhandoveraswell.
LTE163: Subscriber and Equipment Trace
LTE433: Cell Trace
LTE644: Configurable Cell Trace Content
ThethreefeaturesabovearetracingRRCmessages.Theyareextendedtosupport
thenewRRCmessageMBMSIIintroducedbytheLTE1834: LTE MBMS Service
Continuityfeature.

20 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

LTE2057: Extended Measurement Control


Thisfeatureintroducedmechanismstoselectasetofinter-frequencymeasurement
objectstobeconfiguredinaUEconsideringthemaximumnumberofmeasurement
objectsallowed.ThismechanismshallbeappliedtotheA4measurementsfor
MBMSsteeringHO.Itisthelaststepintheselectionprocessformeasurements
afterthefrequencieswithintheMBMSIIhavebeenfilteredforothercriterias(for
example,mobilityprofiles).
LTE2585: MDT Inter-frequency UE Periodic Measurement
LTE3348: MDT Inter-RAT UE Periodic Measurement of GSM
LTE3272: MDT Inter-RAT UE Periodic Measurement of UTRAN
ThethreeMDTfeaturecandidatesabovewillrequireinter-frequencymeasurements
whichmightneedmeasurementgaps.AUEinterestedinMBMSshouldthereforebe
excluded.AsthesefeaturesareexpectedtocomelaterthanLTE1834: LTE MBMS
Service Continuity,itisuptothesefeaturestospecifytheinterdependency.
LTE2834: PCell Swap Enhancements
Thisfeatureintroducesaninter-eNBPCellswap.OnlywiththeLTE2834: PCell Swap
Enhancementsfeature,itwillbepossibletomoveanMBMS-interestedUEtoa
configuredinter-eNBSCell.(TheconfiguredSCellswillnotbereportedbyA4,so
alsonoregularhandoverwillbepossible.)AstheLTE2834: PCell Swap
EnhancementfeatureisexpectedtocomelaterthanLTE1834: LTE MBMS Service
Continuity,itisuptotheLTE2834: PCell Swap Enhancementfeaturetospecifythe
interdependency.

Impact on interfaces
TheLTE1834: LTE MBMS Service Continuityfeatureimpactsinterfacesasfollows:
S1
AddssupportformbmsInterestIndication-r11withintheRRCcontainerofthe
S1AP: HANDOVER REQUIREDmessageandS1AP: HANDOVER REQUEST
message.

X2
AddssupportformbmsInterestIndication-r11withintheRRCcontainerofthe
X2AP: HANDOVER REQUESTmessage.
RRC
AddssupportforthenewRRCmessageRRC:MBMSInterestIndication.
AddssupportforSIB15

Impact on network management tools


TheLTE1834: LTE MBMS Service Continuityfeaturehasnoimpactonnetwork
managementtools.

Impact on system performance and capacity


TheLTE1834: LTE MBMS Service Continuityfeaturedoesnotimpactonsystem
performance.
TheLTE1834: LTE MBMS Service Continuityfeatureimpactssystemcapacityasfollows:

DN09237915Issue:01A 2017Nokia 21

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

AsMBMSinterestedUEsareexcludedfromloadbalancing,thetotalnumberofUEs
availableforloadbalancingisreduced.IftoomanyUEsareMBMSinterested,the
performanceoftheloadbalancingalgorithmsmaybereduced,resultinginareduced
overallcapacity.Theeffectcanhardlybequantified.

3.1.4 LTE1834 reference data


Requirements

Table 1 LTE1834: LTE MBMS Service Continuityhardwareandsoftware


requirements
System Flexi Flexi Air Scale BTS Flexi Zone Flexi Zone
release Multiradio Multiradio 10 Micro BTS Access Point
BTS BTS
FL17 notsupported FL17 FL17 FL17 FL17

Flexi Zone OMS UE NetAct MME SAE GW


Controller
FL17 FL17 notapplicable NetAct17.2 notapplicable notapplicable

Alarms

Table 2 NewalarmsintroducedbyLTE1834: LTE MBMS Service Continuity


Alarm ID Alarm name
7655 CELL NOTIFICATION

Foralarmdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Alarms and Faults.

BTS faults and reported alarms

Table 3 NewBTSfaultsintroducedbyLTE1834: LTE MBMS Service Continuity


Fault Fault name Reported alarms
ID
Alarm Alarm name
ID
5502 SIB15 information 7655 CELL NOTIFICATION
incomplete

Forfaultdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Alarms and Faults.

Commands
TherearenocommandsrelatedtotheLTE1834: LTE MBMS Service Continuityfeature.

Measurements and counters

22 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Table 4 NewcountersintroducedbyLTE1834: LTE MBMS Service Continuity


Counter Counter name Measurement
ID
M8030C Number of MBMS Service based 8030-LTEMBMS(WBTS)
13 Handover Attempts
M8030C Number of MBMS Service based 8030-LTEMBMS(WBTS)
14 Handover Successes
M8030C Number of MBMS Service based 8030-LTEMBMS(WBTS)
15 Handover Failures due to
timer
M8051C Average number of UEs with 8051-LTEUEQuantity(WBTS)
127 MBMS interest
M8030C Number of Carrier Aggregation 8030-LTEMBMS(WBTS)
17 PCell swap completions for
MBMS Steering
M8051C Average Number of MBMS 8051-LTEUEQuantity(WBTS)
129 interested UEs with
configured measurement gap
M8030C Number of Successful 8030-LTEMBMS(WBTS)
16 Handovers Leaving Interested
MBMS Frequency
M8030C Number of MBMS Service based 8030-LTEMBMS(WBTS)
12 Handover Preparation Attempts
M8051C Maximum number of UEs with 8051-LTEUEQuantity(WBTS)
128 MBMS interest

Forcounterdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Counters and Key Performance Indicators.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE1834: LTE MBMS Service
Continuityfeature.

Parameters

Table 5 NewparametersintroducedbyLTE1834: LTE MBMS Service Continuity


Full name Abbreviated name Managed Parent structure
object
Inter-freq. service thresholdRsrpIFSB LNHOIF -
based threshold for Filter
RSRP target filter
Inter-freq. service iFServiceBasedHoR LNCEL -
based HO retry timer etryTimer
Prioritize VoLTE over prioritizeVoLTEov LNBTS -
MBMS erMBMS
Activate MBMS service actMBMSServiceCon LNBTS -
continuity tinuity
SIB15 Profile (SIB15PR) sib15PrId SIB15PR -
identifier

DN09237915Issue:01A 2017Nokia 23

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Table 5 NewparametersintroducedbyLTE1834: LTE MBMS Service Continuity


(Cont.)
Full name Abbreviated name Managed Parent structure
object
Inter frequency MBMS irSaiListId IRSAILIS -
SAI list (IRSAILIST) T
identifier
SIB15 profile sib15ProfileId SIB -
identifier
SAI list of intra- saiListIntraFreqN SIB -
frequency neighbor eighbors
cells
MBMS service area saiListIntraFreq SIB15PR -
identity list of the
cell
Downlink Earfcn of the saiListEarfcnDl IRSAILIS -
MBMS service area T
identity list
SAI list of inter- saiListInterFreqN IRSAILIS -
frequency neighbor eighbors T
cells

Table 6 ExistingparametersrelatedtoLTE1834: LTE MBMS Service Continuity


Full name Abbreviated name Managed Parent structure
object
System Information sibSchedulingList SIB -
Scheduling List
SIB Type siMessageSibType SIB -
MBMS Service Area mbmsServiceArea MBSFN -
MBMS Service Area list mbmsSaiList MBSFN -

Forparameterdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Parameters.

Sales information

Table 7 LTE1834: LTE MBMS Service Continuitysalesinformation


Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense No

24 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

3.1.5 Activating LTE1834: LTE MBMS Service Continuity

Procedure

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

2 Start commissioning.
Sub-steps

a) Select View Commissioning or click Commissioning on the View Bar on


the left.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

5 Set the Activate MBMS service continuity


(actMBMSServiceContinuity) value to true.

6 Configure the LTE1834: LTE MBMS Service Continuity feature.


Foradetaileddescriptionoftheconfigurationprocedure,seeConfiguringLTE1834:
LTEMBMSServiceContinuity.

7 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

DN09237915Issue:01A 2017Nokia 25

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

c) Click Send Parameters.

Result

TheeNBbroadcastsSIB15inallconfiguredcells.

3.1.6 Configuring LTE1834: LTE MBMS Service Continuity


Purpose
ThisprocedureisneccessarytoconfigurethecellsinwhicheNBbroadcastSIB15.For
thisconfigurationthefollowingprocedureshavetobeperformedinsequentialorder.

Before you start


TheLTE1834: LTE MBMS Service Continuityfeatureisactivated;theActivate MBMS
service continuity (actMBMSServiceContinuity)parameterissettotrue.
FortheactivationoftheLTE1834: LTE MBMS Service ContinuityfeatureseeActivating
LTE1834:LTEMBMSServiceContinuity

Procedure

1 Configuring Prioritize VoLTE over MBMS (prioritizeVoLTEoverMBMS) and inter-


frequency related parameters

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


parameter

3 Configure SAIs of inter-frequency neighbor cells in SIB15PR

4 Configure SAIs of intra-frequency neighbor cells

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

3.1.6.1 Configuring Prioritize VoLTE over MBMS


(prioritizeVoLTEoverMBMS) and inter-frequency related
parameters
Purpose
ThisprocedureisnecessarytoconfigurePrioritize VoLTE over MBMS
(prioritizeVoLTEoverMBMS)andinter-frequencyrelatedparameters.

26 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Procedure

1 Proceed to the Radio Network Configuration page.

2 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

3 Configure the Prioritize VoLTE over MBMS


(prioritizeVoLTEoverMBMS) parameter to the desired value.

4 Go to the LNCEL object.


Objectpath:MRBTSLNBTSLNCEL

5 Configure the Inter-freq. service based HO retry timer


(iFServiceBasedHoRetryTimer) parameter to the desired value.
RepeatthisstepinallLNCELinstanceswhereneeded.

6 Go to the LNHOIF object.


Objectpath:MRBTSLNBTSLNCELLNHOIF

7 Configure either the Inter-freq. service based threshold RSRP


target filter (thresholdRsrpIFSBFilter) or Inter-freq.
service based threshold RSRQ target filter
(thresholdRsrqIFSBFilter) parameter in all LNHOIF instances.
RepeatthisstepinallLNHOIFinstanceswhereneeded.

Procedure result
ThePrioritize VoLTE over MBMS (prioritizeVoLTEoverMBMS)
parameterandinter-frequencyrelatedparametersareconfigured.

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

3.1.6.2 Assigning a SIB15 profile with the SIB15 profile identifier


(sib15ProfileId) parameter
Purpose
ThisfeatureisrelatedtoconfiguringtheLTE1834: LTE MBMS Service Continuityfeature
andisnecessaryifassigningaSIB15profileisneeded.

Before you start


ThesuccesfullcompletionofConfiguringPrioritizeVoLTEoverMBMS
(prioritizeVoLTEoverMBMS)andinter-frequencyrelatedparametersisrequired.

DN09237915Issue:01A 2017Nokia 27

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Procedure

1 Proceed to the Radio Network Configuration page.

2 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

3 Create a SIB15 profile.


Sub-steps

a) Right-click the LNBTS object.

b) Select New and find the SIB15PR object.

c) Configure the SIB15 profile (SIB15PR) identifier (sib15PrId)


parameter to the desired value.

4 Assign the SIB15 newly created profile with sib15ProfileId


Sub-steps

a) Go to the SIB object.


Objectpath:MRBTSLNBTSLNCELSIB

b) Assign the value configured for the SIB15 profile (SIB15PR)


identifier (sib15PrId) parameter to the SIB15 profile
identifier (sib15ProfileId) parameter.

Repeatallthesub-stepsofthisstepinallSIBinstanceswhereneeded.

Procedure result
ASIB15profileisassigned.

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

3.1.6.3 Configure SAIs of inter-frequency neighbor cells in SIB15PR


Purpose
ThisprocedureisrelatedtoconfiguringtheLTE1834: LTE MBMS Service Continuity
featureandisnecessaryifserviceareaidentifiers(SAIs)forthereferencingcellandfor
inter-frequencyneighborcellsshallbebroadcasted.

Before you start

28 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

ThesuccesfullcompletionofAssigningaSIB15profilewiththeSIB15profileidentifier
(sib15ProfileId)parameterisrequired.

Procedure

1 Proceed to the Radio Network Configuration page.

2 Go to the SIB15PR object.


Objectpath:MRBTSLNBTSSIB15PR

3 Configure the SAI list of inter-frequency neighbor cells


(saiListInterFreqNeighbors) object.
Sub-steps

a) Right-click the SIB15PR object.

b) Select New and find the IRSAILIST object.

c) Configure the Inter frequency MBMS SAI list (IRSAILIST)


identifier (irSaiListId) parameter to the desired value.

d) Configure the Downlink earfcn of the MBMS service area


identity list (saiListEarfcnDl) parameter to the desired value.

e) Go to the SAI list of inter-frequency neighbor cells object.


Objectpath:MRBTSLNBTSSIB15PRIRSAILISTSAI list of inter-
frequency neighbor cells

f) Configure the SAI list of inter-frequency neighbor cells


(saiListInterFreqNeighbors) parameter to the desired value.

Procedure result
Serviceareaidentifiers(SAIs)forthereferencingcellandforinter-frequencyneighbor
cellsshallbebroadcasted.

DN09237915Issue:01A 2017Nokia 29

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

4 Continue with Configure SAIs of intra-frequency neighbor cells

3.1.6.4 Configure SAIs of intra-frequency neighbor cells


Purpose
ThisprocedureisrelatedtoconfiguringtheLTE1834: LTE MBMS Service Continuity
featureandisnecessaryifserviceareaidentifiers(SAIs)forthereferencingcelland
intra-frequencyneighborcellsshallbebroadcasted.

Before you start


ThesuccesfullcompletionofAssigningaSIB15profilewiththeSIB15profileidentifier
(sib15ProfileId)parameterisrequired.

Procedure

1 Proceed to the Radio Network Configuration page.

2 Go to the SIB object.


Objectpath:MRBTSLNBTSLNCELSIB

3 Configure the SAI list of intra-frequency neighbor cells


(saiListIntraFreqNeighbors) object.
Sub-steps

a) Right-click the SIB object.

b) Select New and find the SAI list of intra-frequency neighbor cells object.

c) Configure the SAI list of intra-frequency neighbor cells


(saiListIntraFreqNeighbors) parameter to the desired value.

Repeatallthesub-stepsofthisstepinallSIBinstanceswhereneeded.

4 Go to the SIB15PR object.


Objectpath:MRBTSLNBTSSIB15PR

30 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

5 Configure the MBMS service area identity list of the cell (saiListIntraFreq)
object.
Sub-steps

a) Right-click the SIB15PR object.

b) Select New and find the MBMS service area identity list of the cell object.

c) Configure the MBMS service area identity list of the cell


(saiListIntraFreq) parameter to the desired value.

g Note: PleasenotethatthesumofSAIsconfiguredinthelistssaiListIntraFreq
andsaiListIntraFreqNeighborsofareferencingcellismaximum63.If
saiListIntraFreqNeighborsisnotconfiguredinanyreferencingcellthe
maximumnumberofSAIsinsaiListIntraFreqis64.eNBwillomitSAIsifoneof
theabovelimitsisexceeded!

g Note: OneormoreSAIsmaynotbebroadcastedifthesumofSAIsconfiguredwith
parameterssaiListIntraFreqNeighbors,saiListIntraFreqand
saiListInterFreqNeighborsexceedsthemaximumavailableSIB15lengthofa
cell.
Inthiscase,a'SIB15informationincomplete'warningwillbereported.

Procedure result
Serviceareaidentifiers(SAIs)forthereferencingcellandintra-frequencyneighborcells
shallbebroadcasted.

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

3.1.6.5 Adding a list item to the SIB instance of any cell which shall
broadcast SIB15
Purpose
ThisprocedureisrelatedtoconfiguringtheLTE1834: LTE MBMS Service Continuity
featureandaddsalistitemtotheSIBinstanceofanycellwhichshallbroadcastSIB15.

Before you start


ThesuccesfullcompletionofConfigureSAIsofintra-frequencyneighborcellsisrequired.

DN09237915Issue:01A 2017Nokia 31

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Procedure

1 Go to the SIB object.


Objectpath:MRBTSLNBTSLNCELSIB

2 Add a list item to the SIB instance of any cell which shall broadcast SIB15.
Sub-steps

a) Right-click the SIB object.

b) Select New and find the System information scheduling list object.

c) Configure the Periodicity (siMessagePeriodicity) parameter to


the desired value.

d) Configure the Repetition (siMessageRepetition) parameter to the


desired value.

e) Set the SIB type (siMessageSibType) parameter to the value SIB15.

Repeatallthesub-stepsofthisstepinallSIBinstanceswhereneeded.

3 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

c) Click Send Parameters.

Result
ThecellsinwhicheNBbroadcastSIB15areconfigured.

32 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

3.1.7 Deactivating LTE1834: LTE MBMS Service Continuity


Before you start
TheLTE1834: LTE MBMS Service Continuityfeatureisactivated;theActivate MBMS
service continuity (actMBMSServiceContinuity)parameterissettotrue.

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

5 Set the Activate MBMS service continuity


(actMBMSServiceContinuity) value to false.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

DN09237915Issue:01A 2017Nokia 33

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

c) Click Send Parameters.

Result

TheeNBstopsbroadcastingSIB15inallcells.

3.2 LTE2410: Roaming and Access Restrictions


Removal for CSFB Emergency Calls
TheLTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls
featureintroducesanenhancementoftheexistingroamingandaccessrestrictions
algorithmduringcircuit-switchedfallback(CSFB).Thisallowsdistinguishingemergency
andhigh-prioritycallsfromoneanother.

3.2.1 LTE2410 benefits


TheLTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls
featureprovidesthefollowingbenefit:
distinctionbetweenemergencyandhigh-priorityaccesscalls,whichmeetsthe
requirementsof3GPPstandard

3.2.2 LTE2410 functional description


Emergencycall(EC)andhigh-priorityaccess(HPA)callsduringCSFBbothhaveahigh
priorityindicator;therefore,theeNBisnotabletodistinguishthem.SinceECshavea
higherprioritythanHPAcalls,theintentionof3GPPistointroduceadistinctionbetween
thetwocalltypesinordertoapplydifferentroamingandaccessrestrictions.The
LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Callsfeature
enablestheeNBtodistinguishbetweenanemergencycallandahigh-prioritycall.This
allowstoapplyrestrictionsonlyinthecaseofhigh-prioritycalls.Duringanemergency
call,ahandoverrestrictionlist(HRL)isnotapplied.

Current behavior of a roaming and access restriction handling based on HRL


AneNBcheckstheHRLand,iftheCSFBindicatorissettoahigh-priorityindication
value,theadditionalCSFBindicatorIEischeckedaswell.Thefollowingoptionsare
possible:

AnadditionalCSFBindicatorIEissettoNo restrictionemergencycallisongoing;
HRLisnottakenintoaccountatall(neitherforaCSFBpacketswitch(PS)HOnor
CSFBredirection)
AnadditionalCSFBindicatorIEissettoRestrictionhigh-priorityaccesscallis
ongoing;HRListakenintoaccount,andtheeNBappliesthereceivedroamingand
accessrestriction(bothforCSFBPSHOandCSFBredirection)
AnadditionalCSFBindicatorIEismissingcurrentbehavior,withouttheLTE2410:
Roaming and Access Restrictions Removal for CSFB Emergency Callsfeature;the
eNBappliesrestrictionsfromHRL,receivedforanemergencycall,andchecksifthe

34 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

targetlistisemptyafterapplyingtheHRLrestrictions.Ifthetargetlistisnotempty,
therestrictedtargetlistwithHRLchecksisused.Ifthetargetlistisempty,HRL
checksarerevertedandafulltargetlistisused.

g Note: Ifthe
LTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls
featureisdisabled,thebehaviorofthenetworkfrompreviousreleasesiskept.

3.2.3 LTE2410 system impact


Interdependencies between features
TheLTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls
featureimpactsthefollowingfeatures:
LTE22: Emergency Call Handling
WiththeLTE2410: Roaming and Access Restrictions Removal for CSFB Emergency
Callsfeatureactivated,aneNBwilldistinguishbetweentheECandHPAcalland
applydifferentalgorithmsforroamingandaccessrestrictionsinbothcases.Inthe
caseofEC,theeNBwillnotapplyanyrestrictionsfromHRL.
LTE572: IMS Emergency Sessions
WiththeLTE2410: Roaming and Access Restrictions Removal for CSFB Emergency
Callsfeatureactivated,aneNBwilldistinguishbetweenanECandHPAcalland
applydifferentalgorithmsforroamingandaccessrestrictionsinbothcases.Inthe
caseofEC,theeNBwillnotapplyanyrestrictionsfromHRL.
LTE736: CS Fallback to UTRAN
WiththeLTE2410: Roaming and Access Restrictions Removal for CSFB Emergency
Callsfeatureactivated,aneNBwilldistinguishbetweenanECandHPAcalland
applydifferentalgorithmsforroamingandaccessrestrictionsinbothcases.

Impact on interfaces
TheLTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls
featurehasnoimpactoninterfaces.

Impact on network management tools


TheLTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls
featurehasnoimpactonnetworkmanagementtools.

Impact on system performance and capacity


TheLTE2410: Roaming and Access Restrictions Removal for CSFB Emergency Calls
featurehasnoimpactonsystemperformanceorcapacity.

3.2.4 LTE2410 reference data


Requirements

Table 8 LTE2410hardwareandsoftwarerequirements
System Flexi Flexi AirScale Flexi Zone Flexi Zone
release Multiradio Multiradio 10 Micro BTS Access Point
BTS BTS
FDD-LTE17 notsupported FL17 FL17 FL17 FL17

DN09237915Issue:01A 2017Nokia 35

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Table 8 LTE2410hardwareandsoftwarerequirements(Cont.)
Flexi Zone OMS UE NetAct MME SAE GW
Controller
FL17 LTEOMS16A 3GPPR8 NetAct17.2 supportnot supportnot
mandatory required required

Alarms
TherearenoalarmsrelatedtotheLTE2410: Roaming and Access Restrictions Removal
for CSFB Emergency Callsfeature.

Commands
TherearenocommandsrelatedtotheLTE2410: Roaming and Access Restrictions
Removal for CSFB Emergency Callsfeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE2410: Roaming and Access
Restrictions Removal for CSFB Emergency Callsfeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE2410: Roaming and Access
Restrictions Removal for CSFB Emergency Callsfeature.

Parameters

Table 9 NewparametersintroducedbyLTE2410
Full name Abbreviated name Managed Parent structure
object
Activate CSFB EC access actCsfbECRestrRem LNBTS
restriction removal

Forparameterdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Parameters.

Sales information

Table 10 LTE2410salesinformation
Product structure class License control Activated by default
BasicSoftware(BSW) Yes

3.3 LTE2466: S1 Handover towards Hybrid Cells


TheLTE2466: S1 Handover towards Hybrid CellsfeatureenhancestheLTE54: Intra-LTE
Handover via S1featurewithapossibilityofhandoverstowardshybridcells.Hybridcells
aretheclosed-subscriber-group(CSG)cellswhichallowanon-CSGmemberstoaccess

36 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

it.Theaccessisgrantedwithanoperator-configurablerangeofhybridphysicalcell
identities(PCIs).TherangeissetintheservingeNBanddefinesalistofneighboring
cellstowardswhichahandoverisallowed.

3.3.1 LTE2466 benefits


TheLTE2466: S1 Handover towards Hybrid Cellsfeatureenablesanyuserequipment
(UE)tosustaintheconnectioninasituationofhandovertowardsacellnormally
configuredasclosed-subscriber-group(CSG)cell.

3.3.2 LTE2466 functional description


Hybrid cells
Ahybridcellallowsnon-closed-subscriber-group(non-CSG)userstoaccessitevenifit
isdefinedasaclosed-subscriber-group(CSG)cell(thatis,onewhichisdeliberately
reservedforafamilyoraninstitution).TheLTE2466: S1 Handover towards Hybrid Cells
featurepreservestheaccesspriorityfortheCSGusersandifthehybridcellis
overloaded,noneofnon-CSGuserscanaccessit.
Theoperatorcansetacellashybridonlyforneighboringcells,andthedefinitionisdone
intheservingeNBbysettingadedicatedrangeofphysicalcellIDs(PCI).Additionaly,a
carrierfrequenciesneedtobedefinedforeachPCIwithadedicatedEUTRA carrier
frequency(freqEutra)LNHBDparameters.
TherangeisdefinedwiththeHybrid neighbor first PCI(pciFirst)and
Hybrid neighbor last PCI(pciLast)LNHBDparameters.Thevaluesareset
withinthe0503range.

g Note: ThePCIrangedefinedforhybridcellscannotoverlapwiththefollowingPCI
ranges:
HomeeNBPCIrange
CSGPCIrange

S1-based handover towards hybrid cells


ThePCIrangeofhybridneighborcellsisdefinedpereNBandisreusedatthefirststage
ofhandover;thatis,whenuserequipment(UE)createsameasurementreportincluding
aPCI.IfthereceivedPCIfallsintothehybridPCIrange,thecellinquestionisahybrid
cell.Afterthecellisselectedasatarget,aneNBstartsareportCGIproceduretoretrieve
thefollowinginformationrequiredtoinitiateanS1handoverfromtheUE:
IDoftargeteNBbecausethePCIscanbereusedaccrosseNBs
CSGIDofatargetcell
trackingareacode(TAC)
publiclandmobilenetworkID(PLMN)

Handoverstowardshybridcellscanbeprioritizedandde-prioritizedto,forexample,limit
thenumberofoutdoorUEsgettingconnectedtotheindoorcell.Therearededicated
operator-configurableoffsetsforallPCIsinthehybridrangeforagivenfrequency.
ConfigurationisdonewiththeHybrid cell individual offset(cellIndOff)
LNHBDparameter.

DN09237915Issue:01A 2017Nokia 37

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Monitoring the S1-based handover to hybrid cells


TheLTE2466: S1 Handover towards Hybrid Cellsfeatureallowstheoperatortomonitor
theexecutionofS1-basedhandovertowardshybridcells.Forthatpurpose,thereare
newmonitoringpossibilitiesintroduced,whichcanbedividedintothefollowing
categories:
MonitoringthesuccessrateofreportCGIprocedurewiththefollowingcounters:
NumberofrequestedSIreportsforhybridcells
NumberofsuccessfulSIreportsforhybridcells
NumberofincompleteSIreportsforhybridcells

Monitoringthesuccessrateofinter-eNBS1handovertohybridcellswiththe
followingcounters:
Inter-eNBS1handoverpreparationstohybridcell
Failedinter-eNBS1handoverpreparationstoahybridcellduetoexpirationof
guardingtimer
Failedinter-eNBS1handoverpreparationstoahybridcellduetoadmission
controlinthetargeteNB
Failedinter-eNBS1handoverpreparationstoahybridcellduetootherreasons
Attemptedinter-eNBS1handovertoahybridcell
Successfulinter-eNBS1handovertoahybridcell
FailedInter-eNBS1handovertohybridcellduetotimerexpiry

MonitoringtheVoLTE-specificsuccessrateofinter-eNBS1handovertohybridcells
withthefollowingcounters:
Inter-eNBS1handoverpreparationsforVoLTE(QCI1)toahybridcell
AttemptedInter-eNBS1handoverforVoLTE(QCI1)toahybridcell
SuccessfulInter-eNBS1handoverforVoLTE(QCI1)toahybridcell

3.3.3 LTE2466 system impact


Interdependencies between features
ThefollowingfeaturesmustbeactivatedbeforeactivatingtheLTE2466: S1 Handover
towards Hybrid Cellsfeature:
LTE54: Intra-LTE Handover via S1

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

38 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

LTE556: ANR Intra-LTE, Inter-frequency UE-based


LTE782: ANR Fully-UE-based

TheLTE2466: S1 Handover towards Hybrid Cellsfeatureimpactsthefollowingfeatures:


LTE1442: Open Access Home eNodeB Mobility
ThehomeeNBPCIrangedefinedwiththeLTE1442: Open Access Home eNodeB
MobilityfeaturecannotoverlapwiththePCIrangedefinedwiththeLTE2466: S1
Handover towards Hybrid Cellsfeatureforthesamefrequency.
LTE2351: S1-based Handover towards CSG Cells
ThePCIrangedefinedwiththeLTE2351: S1-based Handover towards CSG Cells
featureforaclosed-subscriber-group(CSG)cellcannotoverlapwiththePCIrange
foragivenfrequencydefinedwiththeLTE2466: S1 Handover towards Hybrid Cells
feature.

TheLTE2466: S1 Handover towards Hybrid Cellsfeatureisimpactedbythefollowing


features:
LTE55: Inter-frequency Handover
TheLTE55: Inter-frequency Handoverfeaturemustbeenabledtoallowaninter-
frequencyS1handovertoahybridcell.
LTE1060: TDD FDD Handover
TheLTE1060: TDD FDD HandoverfeaturemustbeenabledtoallowanS1
handovertoahybridcellfromadifferenttechnology(FDD/TDD).
LTE1127: Service-based Mobility Trigger
TheLTE1127: Service-based Mobility Triggerfeaturemustbeenabledtoallowa
service-basedhandovertoahybridcell.
LTE1387: Intra-eNodeB Inter-frequency LB,LTE1170: Inter-frequency Load
Balancing Management Data,LTE1531: Inter-frequency Load Balancing Extension
Thefeaturesmustbeenabledtoallowaload-balancing-basedhandovertoahybrid
cell.
LTE2503: Emergency Call-based Mobility Trigger
TheLTE2503: Emergency Call-based Mobility Triggerfeaturemustbeenabledto
allowanemergency-call-basedhandovertoahybridcell.

Impact on interfaces
TheLTE2466: S1 Handover towards Hybrid Cellsfeatureimpactsinterfacesasfollows:
S1APinterface
Handover Requiredmessageisupdatedwiththefollowinginformation
elements(IE)definingthetargetcell:
anidentifierforaclosedsubscribergroup(CSGID)
CellAccessMode

Impact on network management tools


TheLTE2466: S1 Handover towards Hybrid Cellsfeaturehasnoimpactonnetwork
managementtools.

Impact on system performance and capacity

DN09237915Issue:01A 2017Nokia 39

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

TheLTE2466: S1 Handover towards Hybrid Cellsfeaturehasnoimpactonsystem


performanceorcapacity.

3.3.4 LTE2466 reference data


Requirements

Table 11 LTE2466hardwareandsoftwarerequirements
System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 Notsupported FL17 FL17 FL17 FL17

Flexi Zone OMS UE NetAct MME SAE GW


Controller
FL17 Supportnot 3GPPR9 NetAct17.2 FlexiNS4.0 FlexiNG3.0
required

Alarms
TherearenoalarmsrelatedtotheLTE2466: S1 Handover towards Hybrid Cellsfeature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE2466: S1 Handover towards Hybrid Cellsfeature.

Measurements and counters

Table 12 NewcountersintroducedbyLTE2466
Counter ID Counter name Measurement
M8008C27 Number of requested SI LTERRC
reports for hybrid cell
M8008C28 Number of successful SI LTERRC
reports for hybrid cell
M8008C29 Number of incomplete SI LTERRC
reports for hybrid cell
M8014C46 Inter eNB S1 HO preparations LTEIntereNBHandover
to hybrid cell
M8014C47 Failed Inter eNB S1 HO LTEIntereNBHandover
preparations to hybrid cell
due to expiration of
guarding timer
M8014C48 Failed Inter eNB S1 HO LTEIntereNBHandover
preparations to hybrid cell
due to admission control in
the target eNB
M8014C49 Failed Inter eNB S1 HO LTEIntereNBHandover
preparations to hybrid cell
due to other reasons
M8014C50 Attempted Inter eNB S1 HO to LTEIntereNBHandover
hybrid cell

40 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Table 12 NewcountersintroducedbyLTE2466(Cont.)
Counter ID Counter name Measurement
M8014C51 Successful Inter eNB S1 HO LTEIntereNBHandover
to hybrid cell
M8014C52 Failed Inter eNB S1 HO to LTEIntereNBHandover
hybrid cell due to timer
expiry
M8014C53 Inter eNB S1 HO preparations LTEIntereNBHandover
for VoLTE (QCI1) to hybrid
cell
M8014C54 Attempted Inter eNB S1 HO LTEIntereNBHandover
for VoLTE (QCI1) to hybrid
cell
M8014C55 Successful Inter eNB S1 HO LTEIntereNBHandover
for VoLTE (QCI1) to hybrid
cell

Forcounterdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Counters.

Key performance indicators

Table 13 NewkeyperformanceindicatorsintroducedbyLTE2466
KPI ID KPI name
LTE_6130a E-UTRANSIReportAttemptsforhybridcells
LTE_6131a E-UTRANSIReportSRforhybridcells
LTE_6132a E-UTRANIncompleteSIReportRatioforhybridcells
LTE_6133a E-UTRANS1HOPreparationSuccessRatio,intereNBtoaHybridcell
LTE_6134a E-UTRANS1HOPreparations,intereNBtoaHybridcell
LTE_6135a E-UTRANS1HOPreparationFailureRatioperCause,intereNBtoaHybridcell
LTE_6136a E-UTRANS1HOPreparationFailureRatioperCause,intereNBtoaHybridcell
LTE_6137a E-UTRANS1HOPreparationFailureRatioperCause,intereNBtoaHybridcell
LTE_6138a E-UTRANS1HOSuccessRatio,intereNBtoaHybridcell
LTE_6139a E-UTRANS1HOAttempts,intereNBtoaHybridcell
LTE_6140a E-UTRANS1HOFailureRatio,intereNBtoaHybridcell
LTE_6141a E-UTRANTotalS1HOSuccessRatio,intereNBtoaHybridcell
LTE_6142a E-UTRANS1HOPreparationSuccessRatio,intereNBforQCI1toaHybridcell
LTE_6143a E-UTRANS1HOPreparations,intereNBforQCI1toaHybridcell
LTE_6144a E-UTRANS1HOSuccessRatio,intereNBforQCI1toaHybridcell
LTE_6145a E-UTRANS1HOAttempts,intereNBforQCI1toaHybridcell

Parameters

DN09237915Issue:01A 2017Nokia 41

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Table 14 NewparametersintroducedbyLTE2466
Full name Abbreviated name Managed object Parent
structure
Activate Hybrid S1 actHybridS1Mobili MRBTS/LNBTS -
mobility ty
Hybrid neighbor first pciFirst MRBTS/LNBTS/LNHBD -
PCI
Hybrid neighbor last pciLast MRBTS/LNBTS/LNHBD -
PCI
Hybrid cell individual cellIndOff MRBTS/LNBTS/LNHBD -
offset
eNB ID Size enbIdSize MRBTS/LNBTS/LNHBD -
EUTRA carrier frequency freqEutra MRBTS/LNBTS/LNHBD -
Hybrid identifier InHbdId MRBTS/LNBTS/LNHBD -

Table 15 ExistingparametersrelatedtoLTE2466
Full name Abbreviated name Managed object Parent
structure
Activate intra LTE actLTES1Ho MRBTS/LNBTS -
S1based handover
Neighbour relation nrStatus MRBTS/LNBTS/LNCEL/ -
status LNREL
EUTRA carrier frequency csgFreqEutra MRBTS/LNBTS/LNCSG -
CSG neighbor first PCI csgPciFirst MRBTS/LNBTS/LNCSG -
Number of PCI in CSG csgPciRange MRBTS/LNBTS/LNCSG -
neighbor range
Home eNB EUTRA carrier freqEutra MRBTS/LNBTS/LNHEN -
frequency B
Home eNB first PCI pciFirst MRBTS/LNBTS/LNHEN -
B
Home eNB last PCI pciLast MRBTS/LNBTS/LNHEN -
B

Forparameterdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Parameters.

Sales information

Table 16 LTE2466salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) SWAssetMonitoring No

3.3.5 Activating and configuring LTE2466


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

42 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Before you start


Procedurenotifications
Theparametersdescribedbelowcanbemodifiedonline.Theactivationwillnot
causeaserviceoutage.

Theactivationprocedurerequires:
TheeNBmustbeinservice.
NetActmustbeinserviceandhaveaconnectiontotheeNBviaOMS.
Alternatively,BTSSiteManagermustbesetupandconnectedtotheeNB.
TheLNBTSparameteractLTES1Hoisenabled.
TheLTE2466featureisnotactivated;theLNBTSactivationparameter
actHybridS1Mobilityissettofalse.
Featureinterdependencies
ThefollowingfeaturesmustbeactivatedbeforeactivatingtheLTE2466: S1
Handover towards Hybrid Cellsfeature:
LTE54: Intra-LTE Handover via S1

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

DN09237915Issue:01A 2017Nokia 43

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

5 Set the parameter values.

SettheLNBTSactivationparameteractHybridS1Mobilitytotrue.
CreateatleastoneinstanceoftheMOCLNHBD.
ThefollowingLNHBDparametersareconfigured:
freqEutraisconfiguredtoauniquevaluewithintheLNHBDinstancesof
theeNB
pciFirst
pciLast
cellIndOff
enbIdSize

g Note: Ifdefined,thefollowingPCIrangesmustnotoverlapforthesamefrequency:
PCIrangedefinedbyparametersLNHENB-pciFirstandLNHENB-pciLast
PCIrangedefinedbyparametersLNCSG-csgPciFirstand
LNCSG-csgPciRange
PCIrangedefinedbyparametersLNHBD-pciFirstandLNHBD-pciLast

g Note:
Thehybridcells'PCIrange,definedbyparametersLNHBD-pciFirstand
LNHBD-pciLast,isconfiguredasaforbiddenrangeinordertoexcludethePCIs
fromPCIplanningoftheopencells.
Thenon-hybridcells'PCIrangeisconfiguredasaforbiddenrangeincSONinorder
toexcludethePCIsfromPCIplanningofthehybridcells.
Alternatively,thePCIassignmentofthehybridcellsmaybedonemanually.For
moreinformation,refertoPCIplanningoftheCSGcellsintroducedbytheLTE2351
feature.

Forinter-frequencyS1handovertohybridcells,settheLNBTSparameter
actIfHotoenabled.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

44 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

c) Click Send Parameters.

Result

Expectedoutcome
TheLTE2466featureisactivatedandS1-basedintra-andinter-frequencyhandover
towardshybridcellsissupported.

Unexpectedoutcome
Iftheconditionsdescribedabovearenotfulfilled,thevalidationoftheconfigurationfile
willfail.NetActperformsthevalidationandinformstheoperatorofthefailure.TheBTS
SiteManagershowserrormessagesaccordingtotheconfiguration.

3.3.6 Deactivating LTE2466


Instructions to deactivate the LTE2466: S1 Handover Towards Hybrid Cells feature using
the BTS Site Manager

Before you start


Procedurenotifications
Theparametersdescribedbelowcanbemodifiedonline.Theactivationwillnot
causeaserviceoutage.

Thedeactivationprocedurerequires:
TheeNBmustbeinservice.
NetActmustbeinserviceandhaveaconnectiontotheeNBviaOMS.
Alternatively,theBTSSiteManagermustbesetupandconnectedtotheeNB.
TheLTE2466featuremustbeactivated;theLNBTSactivationparameter
actHybridS1Mobilityissettotrue.

DN09237915Issue:01A 2017Nokia 45

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

5 Set the actHybridS1Mobility value to false.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.


AllconfiguredLNHBDobjectswillbeignoredbytheeNBifthe
actHybridS1Mobilityparameterissettofalse.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

c) Click Send Parameters.

Result

Expectedoutcome

46 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

TheLTE2466featureisdeactivatedandS1-basedintra-andinter-frequencyhandover
towardshybridcellsisnotsupported.

3.4 LTE2572: RSRQ-based B2


TheLTE2572: RSRQ-based B2featureintroducesanewreference-signal-received-
quality-related(RSRQ)triggertoruntheB2inter-RATmeasurements.

3.4.1 LTE2572 benefits


TheLTE2572: RSRQ-based B2featureprovidesthefollowingbenefits:
Itispossibletoinitiateaninter-RAThandoverduringperiodsofthehighinterference.
Thequalityofserviceissustainedwhenthereferencesignalreceivedquality
(RSRQ)fortheservingcellbecomesworsethanfortheneighborcell.

3.4.2 LTE2572 functional description

TheLTE2572featureintroducesanewRSRQtriggerthatallowsforahandovertooccur
betweenanLTEnetworkandanetworkofadifferentRadioAccessTechnology(inter-
RAThandover)whilesustainingqualityofservice.Theinter-RAThandoveroccurswhen
thefollowingconditionsaremet:thereferencesignalreceivedquality(RSRQ)forthe
servingLTEcellbecomesworsethanthedefinedabsolutethreshold,andthequantityof
thereferencesignaloftheotherRATstargetneighboringcellbecomesbetterthanthe
definedabsolutethreshold.
Handover in mobile networks
InordertosecureservicecontinuityandqualityasaUEmoves,UEsnotonlyhavetobe
connectedtoaservingcellbutshouldalsohavetomonitorneighborcells.Thesignal
strengthorqualityofneighboringcellsismeasuredperiodically,andahandoveroccurs
whenspecificconditionsarefulfilled.
Duringthehandoverprocedure,runningservicesaremaintained;acallisnot
interrupted,andforanintra-LTEhandovernodataislost.
HandoversinLTEarenetworkcontrolledandUEassisted.Thegoalofthehandover
procedureistoallocatethesameresourcesfortheUEinthetargetcellafterthe
handoverasthoseusedpriortothehandover.FromtheUE'spointofview,ahandoveris
alwayshard,meaningthataconnectionexiststoonlyonecellatatime.
Handoversresultfromsuchfactorsas:

Quality:HandoversduetoqualityaretypicallyinitiatedasaresultofaUE
measurementreportindicatingthattheUEcancommunicatewithaneighborcell
withabetterchannelqualitythanthatofthecurrentservingcell.
Coverage:HandoversduetocoveragearealsoinitiatedasaresultofaUE
measurementreportindicatingthattheservingcellbecomesworsethananabsolute
threshold.

Measurement and measurement reports

DN09237915Issue:01A 2017Nokia 47

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

TheUEassiststheeNBregardingahandoverbysendingmeasurementreports.When
verifyingradioconditionsduetoUEmobility(forexamplewhentheUEmovesfromone
LTEcelltoanotherorbecauseoflimitedLTEcoverage),measurementreportsmay
initiateahandover.ThetypeofmeasurementstobemadebytheUE,andthedetailsof
reportingthemtotheeNB,canbeconfigured(measurementconfigurationandreport
configuration),andtheeNBinformstheUEabouttheconfigurationsviatheRRC:
CONNECTION RECONFIGURATIONmessage.
TheLTEreferencesignalreceivedpower(RSRP)measurementensuresacell-specific
signalstrengthmetric.Ontheotherhand,theLTEreferencesignalreceivedquality
(RSRQ)measurementprovidesacell-specificsignalqualitymetric.

LTE handover events


Beforeahandoverisperformed,aUEsendsmeasurementreportstothenetwork,andit
isthenetworkwhichdecideswhetherahandovertakesplaceornot.3GPPdefinesa
fewtypesofsucheventswithinmeasurementreports.
Inordertolimittheamountofsignaling,theUEonlysendsmeasurementreports(RRC:
MEASUREMENT REPORTmessages)totheeNBwhencertainconditions(events)are
metbytheUEs'measurements.ThefollowingeventsaredefinedintheLTEstandard:

EventA1:Theservingcellbecomesbetterthananabsolutethreshold.
EventA2:Theservingcellbecomesworsethananabsolutethreshold.
EventA3:AnLTEneighborcellbecomesbetterthananoffsetrelativetotheserving
cell.
EventA4:AnLTEneighborcellbecomesbetterthananabsolutethreshold.
EventA5:Theservingcellbecomesworsethananabsolutethreshold,andanLTE
neighborcellbecomesbetterthananotherabsolutethreshold.
EventA6:Neighbourbecomesoffsetbetterthansecondarycell(SCell)
EventB1:Anon-LTEneighborcellbecomesbetterthananabsolutethreshold.
EventB2:Theservingcellbecomesworsethananabsolutethreshold,andanon-
LTEneighborcellbecomesbetterthananotherabsolutethreshold.

TheeventsfromA1toA6arerelatedtointra-LTEhandovers;B1andB2eventsare
relatedtointer-RAThandovers.A1eventscontrolledbyLNCEL:threshold1are
usefulforrestrictingUEmeasurementstotheservingcell.A3isconnectedwithabetter
cellhandoverandA5withacoveragehandover.Theeventscorrespondwiththetypeof
measurementstheUEperforms.
Themeasurementreportscontainalistoftargetcellsforahandover.Thetargetcellsare
listedinorderofdecreasingvalueofthereportingquantity,thatis,thebestcellis
reportedfirst.Asaconsequenceofthedefinitionoftheevents,thetargetcelllistcannot
beempty.

48 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Figure 1 LTEB2event
Aservingcellbecomesworsethanthreshold1(condition1),
andaninter-RATneighborcellbecomesbetterthanthreshold2(condition2)

condition2fulfilled

condition1fulfilled
B2-Threshold2

hysteresis offset
RSRQquantitytrigger
[dB]

serving cell

B2-Threshold1

hysteresis neighbor
cell

time [ms]

signalofaneighborcell B2start
LEGEND
signalofaservingcell B2end

3.4.2.1 LTE2572 overview

TheLTE2572: RSRQ-based B2featureintroducesanadditionaltrigger,whichis


representedbythequantityofreferencesignalreceivedquality(RSRQ).Thetrigger
activatesthequality-relatedB2event,whichtakesplacewhenthequalityofservingcell
becomesworsethanB2-threshold1(thatis,duringtheRSRQ-basedA2event),andthe
qualityofinter-RATneighborcellbecomesbetterthanB2-threshold2.Theneweventis
introducedinadditiontothealreadyexistingB2RSRPevent.
Themeasurementquantitiesare:
WCDMA:RSCPorECN0
GSM:RSSI
HRPDand1XRTT:pilotStrength

g Note: WithoutLTE2572: RSRQ-based B2,theB2eventwasintendedonlyforthe


RSRP.WithLTE2572: RSRQ-based B2,itispossibletohavealsoaB2eventforthe
RSRQwhichallowstomonitorthequalityofservice.

g Note: TheLTE2572: RSRQ-based B2featuredoesnotincreasethenumberof


simultaneouslyactivemeasurementsatUEs,andeithertheB2RSRPorB2RSRQ
measurementisactiveatagiventime.However,thesameB2targetthresholdsare
appliedregardlessofthesourcequantity.Ifthefeatureisdisabled,thelegacyRSRPB2
behaviorapplies.IftheB2RSRQparametersarenotconfiguredforatargetcarrier,the
legacyRSRPB2behaviorappliestothetargetcarrier.

DN09237915Issue:01A 2017Nokia 49

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

3.4.2.2 B2 RSRQ conditions

Theconditionsforbeginningandendofinter-RATmeasurementsarelistedinTable17:
Conditionsfortheinter-RATmeasurementsperiod.Duringthatperiod,adecisionabout
whethertoinitiateaninter-RAThandoverornotismade;consequently,aftera
successfultargetcellselection,ahandoverpreparationphaseisinitiated.

Table 17 Conditionsfortheinter-RATmeasurementsperiod
Beginning of inter-RAT measurements* End of inter-RAT measurements**
Thequalityofservingcellbecomesworsethan Thequalityofservingcellbecomesbetterthan
threshold1 - hysteresis. threshold1 + hysteresis.
AND OR
Thequalityofinter-RATneighborcellbecomes Thequalityorpowerofinter-RATneighborcell
betterthanthreshold2 + hysteresis. becomesworsethanthreshold2 -
hysteresis.

g Note: *Bothconditionsmustbemetbeforetheinter-RATmeasurementsbegin.
**Eitheroftheconditionsmustbemetbeforetheinter-RATmeasurementsareended.

3.4.3 LTE2572: system impact


Interdependencies between features
ThefollowingfeaturemustbeactivatedbeforeactivatingtheLTE2572: RSRQ-based B2
feature:
LTE1198: RSRQ-triggered Mobility
TheRSRQ-basedA2eventtakesamajorroleintheRSRQ-basedB2event;
therefore,theLTE1198: RSRQ-triggered Mobilityfeatureneedstobeenabled.

Impact on interfaces
TheLTE2572: RSRQ-based B2featurehasnoimpactoninterfaces.

Impact on network management tools


TheLTE2572: RSRQ-based B2featurehasnoimpactonnetworkmanagementtools.

Impact on system performance and capacity


TheLTE2572: RSRQ-based B2featurehasnoimpactonsystemperformanceor
capacity.

3.4.4 LTE2572 reference data


Requirements

50 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Table 18 LTE2572hardwareandsoftwarerequirements
System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 Notsupported FL17 FL17 FL17 FL17

Flexi Zone OMS UE NetAct MME SAE GW


Controller
FL17 LTEOMS16A 3GPPR8 NetAct17.2 Supportnot Supportnot
required required

Alarms
TherearenoalarmsrelatedtotheLTE2572: RSRQ-based B2feature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE2572: RSRQ-based B2feature.

Commands
TherearenocommandsrelatedtotheLTE2572: RSRQ-based B2feature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE2572: RSRQ-based B2
feature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE2572: RSRQ-based B2
feature.

Parameters

Table 19 NewparametersintroducedbyLTE2572
Full name Abbreviated name Managed Parent structure
object
Activate RSRQ-based B2 actRsrqInterRatMo LNBTS -
bility
RSRQ B2 GERAN b2Threshold1RsrqG LNHOG rsrqB2GERANMobili
threshold1 ERAN tyParams
RSRQ B2 GERAN time to b2TimeToTriggerRs LNHOG rsrqB2GERANMobili
trigger rqGERANMeas tyParams
RSRQ B2 GERAN hysB2ThresholdRsr LNHOG rsrqB2GERANMobili
hysteresis qGERAN tyParams
RSRQ B2 GERAN report reportIntervalRsr LNHOG rsrqB2GERANMobili
interval qGERAN tyParams
RSRQ B2 HRPD threshold1 b2Threshold1RsrqH LNHOH rsrqB2HrpdMobilit
rpd yParams
RSRQ B2 HRPD time to b2TimeToTriggerRs LNHOH rsrqB2HrpdMobilit
trigger rqHrpdMeas yParams

DN09237915Issue:01A 2017Nokia 51

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Table 19 NewparametersintroducedbyLTE2572(Cont.)
Full name Abbreviated name Managed Parent structure
object
RSRQ B2 HRPD hysteresis hysB2ThresholdRsr LNHOH rsrqB2HrpdMobilit
qHrpd yParams
RSRQ B2 HRPD report reportIntervalRsr LNHOH rsrqB2HrpdMobilit
interval qHrpd yParams
RSRQ B2 UTRA threshold1 b2Threshold1RsrqU LNHOW rsrqB2UtraMobilit
tra yParams
RSRQ B2 UTRA time to b2TimeToTriggerRs LNHOW rsrqB2UtraMobilit
trigger rqUtraMeas yParams
RSRQ B2 UTRA hysteresis hysB2ThresholdRsr LNHOW rsrqB2UtraMobilit
qUtra yParams
RSRQ B2 UTRA report reportIntervalRsr LNHOW rsrqB2UtraMobilit
interval qUtra yParams
RSRQ B2 1XRTT b2Threshold1RsrqR LNHOX rsrqB2RttMobility
threshold1 tt Params
RSRQ B2 1XRTT time to b2TimeToTriggerRs LNHOX rsrqB2RttMobility
trigger rqRttMeas Params
RSRQ B2 1XRTT hysB2ThresholdRsr LNHOX rsrqB2RttMobility
hysteresis qRtt Params
RSRQ B2 1XRTT report reportIntervalRsr LNHOX rsrqB2RttMobility
interval qRtt Params

Forparameterdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Parameters.

Sales information

Table 20 LTE2572salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) SWAssetMonitoring No

3.4.5 Activating LTE2572


Instructions to activate the LTE2572: RSRQ-based B2 feature using the BTS Site
Manager

Before you start


Theactivationprocedurerequiresthefollowing:
TheeNBmustbeoperational,andtheRNWdatabasemustberunning.
TheLTE2572: RSRQ-based B2featuremustbedeactivated;itsLNBTS
activationparameteractRsrqInterRatMobilitymustbesettofalse.
TheLTE1198featuremustbeconfigured.
Anyrelevantinter-RATmobilityfunctionalitiesareactivated.
Vendor-specificparametersareconfiguredinthevendorfile.

52 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Mandatoryandoptionaloperator-specificparametersareconfigured.

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

5 Set the actRsrqInterRatMobility value to true.

g Note: Asanalternative,activationcanalsobedonebyreconfiguringthemandatory
andoptionaloperator-specificparameters.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

DN09237915Issue:01A 2017Nokia 53

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

c) Click Send Parameters.

Result

Expectedoutcome
TheFlexiMultiradioBTSsupportsinter-RATmobilitybasedontheB2RSRQ
measurementreporting.

3.4.6 Deactivating LTE2572


Instructions to deactivate the LTE2572: RSRQ-based B2 feature using the BTS Site
Manager

Before you start


Thedeactivationprocedurerequires:
TheeNBmustbeoperational,andtheRNWdatabasemustberunning.
TheLTE2572featuremustbeactivated;theLNBTSactivationparameter
actRsrqInterRatMobilitymustbesettotrue.

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

54 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

5 Set the actRsrqInterRatMobility value to false.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

c) Click Send Parameters.

Result

Expectedoutcome
TheLTE2572featureisdeactivated.TheFlexiMultiradioBTSisnolongerabletouse
inter-RATmobility.

3.5 LTE2664: Load-based PUCCH Region


TheLTE2664: Load-based PUCCH Regionfeatureintroducesliveallocationofphysical
uplinkcontrolchannel(PUCCH)resourcescorrespondingtothenumberofconnected
UEs.

3.5.1 LTE2664 benefits


TheLTE2664: Load-based PUCCH Regionfeatureprovidesthefollowingbenefits:
AutomaticadaptationofPUCCHresourcesaccordingtocurrentcellload

DN09237915Issue:01A 2017Nokia 55

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

RelocationofunusedPUCCHresourcestoPUSCHduringalow-trafficperiod,
resultinginahigheruplinkthroughput
Operatorisrequiredtoconfigure7parametersonlyincontraryto17instandard
configuration

3.5.2 LTE2664 functional description


Functional overview
TheLTE2664: Load-based PUCCH Regionfeatureadjuststherangeofphysical
resourceblocks(PRB)allocatedtothephysicaluplinkcontrolchannel(PUCCH).The
adjustmentismadeproportionallytothenumberofUEsconnectingtoacell.
CooperationwiththeLTE1130: Dynamic PUCCH Allocationfeatureenablestheoperator
toexpandorcompressthePUCCHregionaccordingtotheactualcellsload.Thanksto
theliveadjustmentofschedulingrequest(SR)andchannelstateinformation(CSI)
periodicities,definedwiththeLTE1130: Dynamic PUCCH Allocationfeature,the
adaptationofPRBsassignedtoPUCCHisswiftandefficient;thatis,adequatetothe
numberofUEsconnectedtothecell.

g Note: ThePUCCHregionmaybereleasedoncetherearePUCCHresourcesinitthat
arenolongeroccupied.Toavoidundesirablebandwidthfragmentation,thesystem
stopsassigningnewcallstothePUCCHareaattheriskofbeingsoonconvertedto
PUSCH.

Figure 2 PUCCHresourceallocationinLTE2664

Contribution of the LTE1130: Dynamic PUCCH Allocation feature

56 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Thephysicaluplinkcontrolchannel(PUCCH)isusedtotransmittheuplinkcontrol
information(UCI),whichincludes:
Schedulingrequests(SR)
HARQACK/NACKinresponsetoDLtransmissionsinthephysicaldownlinkshared
channel(PDSCH)
Channelstateinformation(CSI),whichincludes:
Channelqualityindicators(CQI)
MIMO-relatedfeedbacksuchastherankindicators(RI)ortheprecodingmatrix
indicators(PMI)

TheLTE1130: Dynamic PUCCH AllocationfeaturesimplifiestheprocessofPUCCH


configurationbyintroducing:
Dynamicswitchingbetweenchannelstateindicator(CSI)periodicities:40msand80
ms
DynamicswitchingbetweenULschedulingrequest(SR)periodicities:10ms,20ms,
and40ms
SwitchingbetweenSRperiodicitiesdependsoncellload,whichisrelatedtonumberof
RRCConnectedUEsinthecell.SwitchingbetweenCSIperiodicitiesdependsonacell
loadandconfigurationofMIMO,carrieraggregationandenhancedinter-cellinterference
coordination(eICIC).
TheadaptationoftheCSIorSRperiodicityisdoneonlyforUEsforwhich
reconfigurationneedstobeapplied.Toavoidgeneratingextrasignaling,newCSIorSR
periodicityisgiventoeveryUEexperiencingoneofthefollowingevents:
RRC-idletoRRC-connectedstatetransition
UEenteringthecellviahandover
Secondarycell(SCell)configurationorreconfiguration

Enhancements introduced by LTE2664: Load-based PUCCH Region feature


InadditiontotheshiftinCSIandSRperiodicitiesmanagedbytheLTE1130: Dynamic
PUCCH Allocationfeature,theLTE2664: Load-based PUCCH Regionfeatureallows
operatortoexpandorcontractPUCCHregionaccordingtotheminimalconfigurationof
resourcesallocatedtoPUCCH(2PRBsassigned).TheeNBrespondsinadvancetothe
risingnumberofUEsconnectingtothecellbyexpandingthePUCCHarea.A
configurablesafetymarginpreventsthePUCCHresourcesfromrunningoutandhelpsto
avoidtheradioresourcecontrol(RRC)blocking.
WhenthePUCCHexpansionprocessistriggered,eNBcalculatesnewparametervalues
forthenextPUCCHexpansionstep.ParametersthatdefinePUCCHareasizeand
PRACHoffset(APUCCH_FDD:assignedNCqiRb,
APUCCH_FDD:assignedPrachFreqOffand
APUCCH_FDD:assignedN1PucchAn)aremodified.UEsgetthenewparameter
valuesthroughaSIBbroadcast(SIB#2intheimage)whichcontainsthenewvaluesfor
nRB-CQI,prach-FreqOffset,andn1PUCCH-AN.

DN09237915Issue:01A 2017Nokia 57

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Figure 3 PUCCHexpansionprocedure

APUCCH_FDD/TDD
assignedPrachFreqOff
AssignedN1PucchAn
SIB#2 assignedNCqiRB
nRB-CQI
Prach-FreqOffset
N1PUCCH-AN

SIB#2

IfthePUCCHexpansionprocessistriggeredbecausethesystemInfoValueTagisabove
thevaluesetinLNBTS:sibUpdateRateThreshold,thennewparametervaluesare
calculatedformaximumpossiblePUCCHconfiguration.ASIBupdate(SIB#2inthe
image)containingthenewinformationisbroadcasted.
Figure 4 PUCCHexpansionprocedure(systemInfoValueTag>
LNBTS: sibUpdateThreshold)
SIB#1 LNBTS
systemInfoValueTag 28 sibUpdateRateThreshold 25

SIB#1

SIB#2

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

Whenacellsloaddecreases,sparephysicaluplinkcontrolchannel(PUCCH)capacityis
acquired.ToreconfiguretheareaassignedtoPUCCH,asysteminformationblock(SIB)
sentbytheeNBmustbemodified.IntroducingSIBmodificationsrequiresasufficient
amountoftime.Duetorestrictions,theycannotoccurtoooftenandcannotbedelayed
toomucheithertoavoidtheRRCblocking.ThatiswhyaPUCCHareadowngradehas
tobecarriedoutwithanappropriatetimemargininregardtothepreviousPUCCH
modification.Aftertheestablishedintervalhaspassed,someofthePUCCH-allocated
physicalresourceblocks(PRB)exceedingthethresholdarereassignedbytheeNBto
beusedbythephysicaluplinksharedchannel(PUSCH).
TheoperatorisenabledtodefinetheamountofsupportedUEs.Thisincludesthe
maximumnumberofUEscalculatedconsideringparameters:

maxNumActUe

58 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

aPucchMinNumRrcNoDrb
aPucchMinNumEmergencySessions
aPucchAddAUeRrHo
aPucchAddAUeTcHo

SettingcorrectlyparametersforminimumnumberofUEshostedbythecellallowsto
reachminimalconfigurationcontainingonly2or4PRBs.

aPucchMinNumRrc
aPucchMinNumRrcNoDrb
aPucchMinNumEmergencySessions
aPucchAddAUeRrHo
aPucchAddAUeTcHo

ExpansionorcompressionofPUCCHresourcesisfollowedbyshiftofPRBsusedby
physicalrandomaccesschannel(PRACH).Locationoftheseresourcesiscorresponding
tothechangesoftheareaoccupiedbyPUCCH.

g Note: WhenLTE944: PUSH MaskingfeatureisactivePRACHresourcesaresteadily


allocatedduetothePUSCHmasking.PRACHresourcesareallocatedaccordingtothe
LTE1130: Dynamic PUCCH allocationfeaturecalculatedlargestPUCCHBW
occupation.

Reconfiguration of PUCCH resources


ReconfigurationofPUCCHisacomplexprocessthatmightbedividedintothree
distinctivephases:

1. PreparationphasewhentheUEinthecellispreparedfortheprocesstotrigger.
ChangesinthesysteminformationareintroducedandnotificationsintheeNB
softwareareprepared.
2. CommunicationphasewhennotificationsaresenttoUEs,informingthatinthenext
broadcastcontrolchannel(BCCH)modificationwindownewSIBswillbeavailable.
3. BroadcastingphasewhenthenewSIBsaretransmitted.

ResourcesreconfigurationeventistriggeredwhenUE'sreosurcesmustberelocated.
EachUEsubbmitedtoreconfigurationrecievesaRRCConnectionReconfiguration
messagefromeNBfollowedbyafeedbackRRCConnectionReconfigurationComplete
messagefromtheUE.
ExtendingthePUCCHregionisafastprocess,devoidofriskofdroppingtheUEs.The
defaultvaluefortheparametercountdownPucchExpdefiningtheextentoftimethat
needtopassbetweenfollowingexpansionsissetfor10minutes.Incontrastthe
compressioniscarriedoutwithmuchmoreattention.Thedefaultvaluefortheparameter
countdownPucchComprissetto60minutes.Toavoidunnecessaryrepositioning,the
numberofUEsrequiringreconfigurationmustbebelow50.

Borderline PUCCH reconfiguration instances


ThereispossibilitythataftertriggeringPUCCHreconfiguration,cell'sloadmay
substantiallychangewhichrequiresappropriateLTE2664: Load-based PUCCH Region
featureresponse.

DN09237915Issue:01A 2017Nokia 59

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

WhenexpansionofPUCCHregionistriggeredandthenumberofSIBmodification
perintervalisabovesibUpdateRateThresholdthreshold,PUCCHareais
expandedtothemaximalconfigurablevalue.
WhencompressionofPUCCHregionistriggeredandthenumberofSIB
modificationisabovesibUpdateRateThresholdthreshold,thecompressionis
abortedandpostponedtothenextcountdownexpiration.

Data carried in PUCCH


Thephysicaluplinkcontrolchannel(PUCCH)isusedtotransmittheuplinkcontrol
information(UCI),whichincludes:
Schedulingrequests(SR)
HARQACK/NACKinresponsetoDLtransmissionsinthephysicaldownlinkshared
channel(PDSCH)
Channelstateinformation(CSI),whichincludes:
Channelqualityindicators(CQI)
MIMO-relatedfeedbacksuchastherankindicators(RI)ortheprecodingmatrix
indicators(PMI)

3.5.3 LTE2664 system impact


Interdependencies between features
ThefollowingfeaturesmustbeactivatedbeforeactivatingtheLTE2664: Load-based
PUCCH Regionfeature:
LTE1130: Dynamic PUCCH Allocation

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

Impact on interfaces
TheLTE2664: Load-based PUCCH Regionfeaturehasnoimpactoninterfaces.

Impact on network management tools


TheLTE2664: Load-based PUCCH Regionfeaturehasnoimpactonnetwork
managementtools.

Impact on system performance and capacity


TheLTE2664: Load-based PUCCH Regionfeaturehasnomeasurableimpactonsystem
performanceorcapacity.However,acellaccesscanbelimitediftheprocessofPUCCH
regionexpansionisnotfastenough.

3.5.4 LTE2664 reference data


Requirements

60 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Table 21 LTE2664hardwareandsoftwarerequirements
System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 Notsupported FL17 FL17 FL17 FL17

Flexi Zone OMS UE NetAct MME SAE GW


Controller
FL17 LTEOMS16A 3GPPR8 NetAct17.2 Supportnot Supportnot
required required

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE2664: Load-based PUCCH Regionfeature.

Measurements and counters

Table 22 NewcountersintroducedbyLTE2664
Counter ID Counter name Measurement
M8011C194 Load-based PUCCH region LTECellResource
expansion
M8011C195 Load-based PUCCH region LTECellResource
compression

Table 23 ExistingcountersrelatedtoLTE2664
Counter ID Counter name Measurement
M8011C49 PRB used PUCCH LTECellResource
M8013C67 Number of Signaling LTEUEState
Connection Establishment
Requests rejected due to lack
of PUCCH resources

Forcounterdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Counters.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE2664: Load-based PUCCH
Regionfeature.

Parameters

Table 24 ExistingparametersrelatedtoLTE2664
Full name Abbreviated name Managed object Parent
structure
Activation of actAutoPucchAlloc MRBTS/LNBTS/LNCEL/LNCEL_FD -
automatic D
PUCCH
allocation

DN09237915Issue:01A 2017Nokia 61

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Table 24 ExistingparametersrelatedtoLTE2664(Cont.)
Full name Abbreviated name Managed object Parent
structure
Maximum maxNumActUE MRBTS/LNBTS/LNCEL/LNCEL_FD -
number of D
active UEs
Activate actLbPucchReg MRBTS/LNBTS/LNCEL/LNCEL_FD -
load-based D/APUCCH_FDD
PUCCH region
Load-based lbPucchRPrId MRBTS/LNBTS/LNCEL/LNCEL_FD -
PUCCH region D/APUCCH_FDD
profile
identifier
Countdown countdownPucchComp MRBTS/LNBTS/LBPUCCHRDPR -
timer SIB r
modification
by PUCCH
compression
Countdown countdownPucchExp MRBTS/LNBTS/LBPUCCHRDPR -
timer SIB
modification
by PUCCH
expansion
Lower rrcConnectedLowerT MRBTS/LNBTS/LBPUCCHRDPR -
threshold UEs hresh
in RRC
connected
Upper rrcConnectedUpperT MRBTS/LNBTS/LBPUCCHRDPR -
threshold UEs hresh
in RRC
connected
Load based lbPucchRDPrId MRBTS/LNBTS/LBPUCCHRDPR -
PUCCH region
default
profile
identifier
Countdown countdownPucchComp MRBTS/LNBTS/LBPUCCHRPR -
timer SIB r
modification
by PUCCH
compression
Countdown countdownPucchExp MRBTS/LNBTS/LBPUCCHRPR -
timer SIB
modification
by PUCCH
expansion
Lower rrcConnectedLowerT MRBTS/LNBTS/LBPUCCHRPR -
threshold UEs hresh
in RRC
connected
Upper rrcConnectedUpperT MRBTS/LNBTS/LBPUCCHRPR -
threshold UEs hresh
in RRC
connected

62 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Table 24 ExistingparametersrelatedtoLTE2664(Cont.)
Full name Abbreviated name Managed object Parent
structure
Load based lbPucchRPrId MRBTS/LNBTS/LBPUCCHRPR -
PUCCH region
profile
identifier

g Note: TheparametersaresharedwiththeLTE1130: Dynamic PUCCH Allocation


feature.

Forparameterdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Parameters.

Sales information

Table 25 LTE2664salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense No

3.5.5 Activating and configuring LTE2664


Instructions to activate and configure the LTE2664: Load-based PUCCH Region feature
using the BTS Site Manager

Before you start


Procedurenotifications
Activationprocedureusesthefollowingparametersandactivationflags:
actLbPucchReg

Featureinterdependencies
ThefollowingfeaturesmustbeactivatedbeforeactivatingtheLTE2664: Load-
based PUCCH Regionfeature:
LTE1130: Dynamic PUCCH Allocation
ThisfeatureisactivatedbytheactAutoPucchAllocflag.

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

LTE1808andLTE2664cannotbeactivatedtogether.

Theactivationprocedurerequires:
AconnectionbetweentheeNBandthemanagementsystemmustbe
establishedandworking.

DN09237915Issue:01A 2017Nokia 63

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

AllLNCELandotherclassinstanceparametersneededforanoperatingeNB
mustbeconfigured.
Parameterconfigurationfollowstheguidelines.Incaseofreconfiguration,no
validationerrorexists.
LTE1130isactivatedinatleastoneLNCEL/LNCEL_FDDinstanceoftheeNB;
actAutoPucchAllocissettotrueundertheLNCEL/LNCEL_FDDinstance.
AnewobjectAPUCCH_FDDmustbecreated.
SetthevalueoftheaPucchSrPeriodUpperLimit(AutomaticPUCCH
allocation,upperSRperiodicity)parameterto20 msor40 ms.
TheLTE2664featuremustbeinactive.TheactLbPucchRegparameterunder
theAPUCCH_FDDobjectissettofalse.

g Note: TheactAutoPucchAllocparametermustbesettothesamevalueonall
LNCELswithcarrieraggregation.

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNCEL object.

g Note: FromreleaseLTE17onwards,duetoachangeintheMOarchitecture,youneed
toselectthe LNCEL/LNCEL_FDDobject.
Objectpath:MRBTSLNBTSLNCELLNCEL_FDD

5 Set the parameter values.

g Note: FromreleaseLTE17onwards,duetoachangeintheMOarchitecture,youneed
toselectthe LNBTS/LNBTS_FDDobject.

64 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

g Note: FromreleaseLTE17onwards,duetoachangeintheMOarchitecture,youneed
toselectthe LNCEL_FDD/APUCCH_FDDobject.
ForeachLNCEL_FDDinstancethefeatureisactivatedon,performthefollowing:
ChangeactAutoPucchAlloctotrue.
UnderthechildclassAPUCCH_FDDoftheLNCEL_FDD,configure
actLbPucchRegtotrue.

g Note: LNCELinstanceswillshortstopserviceandwillbereestablisheddueto
actLbPucchRegmodificationviacelllock.

Configuretheparametersaccordingly:

g Note: LBPUCCHRDPRisundertheLNBTSobject.

Case1.ThesameLoad-basedPUCCHRegionconfigurationforallLNCELs
ChangeallthesettingsunderclassLBPUCCHRDPR(load-basedPUCCHregion
defaultprofileidentifier)asrequired.
Case2.PartiallyspecificLoadBasedPUCCHRegionconfigurationforthe
LNCEL
ThiscasedescribesthereuseofsettingsfromthedefaultLBPUCCHRDPRprofile.
Forthisscenario,dothefollowing:
CreateormodifyanexistingLBPUCCHRPR(load-basedPUCCHregion
profileidentifier)instancewhereonlytheparametersthatareintendedtobe
modifiedcanbeconfigured.
UndertheAPUCCH_FDDinstance,configurethelbPucchRPrIdparameter
withthevalueoftheLBPUCCHRPRinstance.

Case3.Fully-specificLoad-basedPUCCHRegionconfigurationfortheLNCEL
Inthiscase,noneofthedefaultconfigurationsareused.Forthisscenario,dothe
following:
CreateormodifyanexistingLBPUCCHRPRinstancewhereallparametersin
theLBPUCCHRPRinstancewillbeconfigured.
UndertheAPUCCH_FDDinstance,configurethelbPucchRPrIdparameter
withthevalueoftheLBPUCCHRPRinstance.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

DN09237915Issue:01A 2017Nokia 65

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

c) Click Send Parameters.

Result

Expectedoutcome
TheLNCELinstance(s)andallparametersettingsarestoredontheeNB.
NetActandBTSSiteManagerareinformedofthemodifiedconfigurationvia
notifications.
TheLTE2664featureisactivatedand,incaseadedicatedprofileisused,the
configurationofthereferencedinstanceLBPUCCHRPRisconsideredinthe
application.Ifnodedicatedprofileisassigned,thedefaultprofileLBPUCCHRDPRis
used.
Thecell(s)areoperatingasexpected.

3.5.6 Deactivating LTE2664


Instructions to deactivate the LTE2664: Load-based PUCCH Region feature using the
BTS Site Manager

Before you start


Preconfiguration
Thedeactivationprocedurerequires:
AconnectionbetweentheeNBandthemanagementsystemmustbe
establishedandworking.
AllLNCELandotherclassinstanceparametersneededforanoperatingeNB
mustbeconfigured.
Parameterconfigurationfollowstheguidelines.Incaseofreconfiguration,no
validationerrorexists.
LTE1130isactivated;actAutoPucchAllocissettotrue.
LTE2664isactivatedinatleastoneLNCEL_FDDinstanceoftheeNB;
actLbPucchRegissettotrue.

66 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNCEL object.

g Note: FromreleaseLTE17onwards,duetoachangeintheMOarchitecture,youneed
toselectthe LNCEL/LNCEL_FDDobject.
Objectpath:MRBTSLNBTSLNCELLNCEL_FDD

5 Edit the eNB configuration with the following content:

g Note: FromreleaseLTE17onwards,duetoachangeintheMOarchitecture,youneed
toselectthe LNBTS/LNBTS_FDDobject.

g Note: FromreleaseLTE17onwards,duetoachangeintheMOarchitecture,youneed
toselectthe LNCEL_FDD/APUCCH_FDDobject.
TodeactivateLTE2664onanLNCEL_FDDinstancewhilekeepingLTE1130
active
UnderthechildclassAPUCCHoftheLNCEL_FDDinstance,changethe
actLbPucchRegparametertofalse.
DeletetheparametervalueoflbPucchRPrIdandleaveitempty.
Optionally,underAPUCCH_FDD,deletetheLBPUCCHRPRinstancethe
lbPucchRPrIdparameterpointsto.
TodeactivateLTE2664andLTE1130
UndertheLNCEL_FDDinstance,changetheactAutoPucchAlloc
parametertofalse.

DN09237915Issue:01A 2017Nokia 67

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

g Note: TheactAutoPucchAllocparametermustbesettothesamevalueonall
LNCELswithcarrieraggregation.
UnderthechildclassAPUCCH_FDDoftheLNCEL_FDDinstance,changethe
actLbPucchRegparametertofalse.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

c) Click Send Parameters.

Result

Expectedoutcome
TheLNCELinstancesandallparametersettingsarestoredintheeNB.
NetActandBTSSiteManagerareinformedoftheconfigurationmodificationsvia
notifications.
TheLTE2664isdeactivated.Anyspecificconfigurationforthereferencedinstance
LBPUCCHRPRorthedefaultprofileLBPUCCHRDPRisnotconsideredbytheeNB.
Thecellsareoperatingasexpected.

3.6 LTE3047: Additional Carrier Aggregation Band


Combinations 2CC V
TheLTE3047: Additional Carrier Aggregation Band Combinations 2CC Vfeature
supportsadditionalbandcombinationsfortwo-component-carrier(2CC)downlink(DL)
carrieraggregation(CA).

3.6.1 LTE3047 benefits


TheLTE3047: Additional Carrier Aggregation Band Combinations 2CC Vfeature
provideshigherDLpeakratesinareaswithoverlappingcelldeploymentsforthe
supportedtwo-component-carrier(2CC)bandcombinations.

68 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

3.6.2 LTE3047 functional description


TheLTE3047featureintroducesthefollowingadditionalcarrieraggregationband
combinationswiththebandwidthcombinationset0(BCS0),ifnotmentionedotherwise:

band3+band3(non-contiguous;BCS2)
band3+band5(BCS4)
band5+band28
band7+band7(non-contiguous;BCS1,2,3)
band7+band8(BCS2)
band12+band25
band29+band66
band30+band66

3.6.3 LTE3047 system impact


Interdependencies between features
TheLTE3047: Additional Carrier Aggregation Band Combinations 2CC Vfeatureis
enabledtogetherwiththefollowingfeatures:
LTE1089: Downlink Carrier Aggregation 20 MHz
LTE1332: Downlink Carrier Aggregation 40 MHz

TheLTE3047: Additional Carrier Aggregation Band Combinations 2CC Vfeature


impactsthefollowingfeatures:
LTE3048:AdditionalCarrierAggregationBandCombinations3CCIII
TheLTE3047: Additional Carrier Aggregation Band Combinations 2CC Vfeature
provides2CCfallbackbandcombinationsfortheLTE3048: Additional Carrier
Aggregation Band Combinations 3CC IIIfeature.
LTE1089 Downlink Carrier Aggregation 20 MHz
TheLTE3047: Additional Carrier Aggregation Band Combinations 2CC Vfeature
addsadditional2CCCAbandcombinations.
LTE1332 Downlink Carrier Aggregation 40 MHz
TheLTE3047: Additional Carrier Aggregation Band Combinations 2CC Vfeature
addsadditional2CCCAbandcombinations.

Impact on interfaces
TheLTE3047: Additional Carrier Aggregation Band Combinations 2CC Vfeaturehas
noimpactoninterfaces.

Impact on network management tools


TheLTE3047: Additional Carrier Aggregation Band Combinations 2CC Vfeaturehas
noimpactonnetworkmanagementtools.

Impact on system performance and capacity


TheLTE3047: Additional Carrier Aggregation Band Combinations 2CC Vfeaturehas
noimpactonsystemperformanceorcapacity.

DN09237915Issue:01A 2017Nokia 69

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

3.6.4 LTE3047 reference data


Requirements

Table 26 LTE3047hardwareandsoftwarerequirements
System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 notsupported FL17 FL17 notsupported notsupported

Flexi Zone OMS UE NetAct MME SAE GW


Controller
notsupported supportnot 3GPPR12UE NetAct17.2 supportnot supportnot
required capabilities required required

3GPPR13UE
capabilities

Alarms
TherearenoalarmsrelatedtotheLTE3047: Additional Carrier Aggregation Band
Combinations 2CC Vfeature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE3047: Additional Carrier Aggregation Band
Combinations 2CC Vfeature.

Commands
TherearenocommandsrelatedtotheLTE3047: Additional Carrier Aggregation Band
Combinations 2CC Vfeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE3047: Additional Carrier
Aggregation Band Combinations 2CC Vfeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3047: Additional Carrier
Aggregation Band Combinations 2CC Vfeature.

Parameters
TherearenoparametersrelatedtotheLTE3047: Additional Carrier Aggregation Band
Combinations 2CC Vfeature.

Sales information

Table 27 LTE3047salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense No

70 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

3.7 LTE3048: Additional Carrier Aggregation Band


Combinations 3CC III
TheLTE3048: Additional Carrier Aggregation Band Combinations 3CC IIIfeature
supportsadditionaldownlink(DL)carrieraggregation(CA)bandcombinationsforthree
componentcarriers(CCs),therebyprovidingmoreoptionstoincreasedownlink
throughput.

3.7.1 LTE3048 benefits


TheLTE3048: Additional Carrier Aggregation Band Combinations 3CC IIIfeature
supportsnewbandcombinationsthatprovidehigherDLpeakratesinareaswith
overlappingcelldeploymentsandwhencarrieraggregation(CA)isenabled;this
guaranteeshigherpeakdataratesfortheuserswithinthenetwork.

3.7.2 LTE3048 functional description


WhentheLTE3048: Additional Carrier Aggregation Band Combinations 3CC IIIfeature
isenabled,theeNBsupportsthefollowingadditionalcarrieraggregation(CA)band
combinations:
CAbandcombinationwithoneband:
Band66+Band66+Band66(twocontiguouscarriers)

CAbandcombinationwithtwobands:
Band1+Band7+Band7(non-contiguous)
Band2+Band5+Band5(contiguous)
Band2+Band2+Band29(non-contiguous)
Band2+Band2+Band30(non-contiguous)
Band2+Band2+Band66(contiguous,non-contiguous)
Band2+Band66+Band66(contiguousforbandwidthclassBandC,otherwise
non-contiguous)
Band3+Band3+Band5(contiguous)
Band3+Band3+Band7(non-contiguous,bandwidthcombinationset0,1)
Band3+Band7+Band7(non-contiguous,bandwidthcombinationset0,1)
Band3+Band3+Band8(contiguous)
Band3+Band3+Band32(contiguous)
Band4+Band5+Band5(contiguous)
Band4+Band7+Band7(non-contiguous)
Band5+Band7+Band7(contiguous,non-contiguous)
Band5+Band5+Band30(contiguous,non-contiguous)
Band5+Band5+Band66(contiguous,non-contiguous)
Band5+Band66+Band66(contiguousforbandwidthclassBandC,otherwise
non-contiguous)
Band7+Band7+Band8(non-contiguous,bandwidthcombinationset0,1)

DN09237915Issue:01A 2017Nokia 71

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Band12+Band66+Band66(contiguousforbandwidthclassC,otherwisenon-
contiguous)
Band13+Band66+Band66(contiguousforbandwidthclassBandC,
otherwisenon-contiguous)
Band29+Band66+Band66(contiguous,non-contiguous)(availablefrom
LTE17SPrelease)
Band30+Band66+Band66(contiguous,non-contiguous)(availablefrom
LTE17SPrelease)

CAbandcombinationwiththreebands:
Band1+Band5+Band28
Band1+Band7+Band20(bandwidthcombinationset1)
Band1+Band18+Band28(bandwidthcombinationset1)
Band2+Band5+Band66
Band2+Band12+Band66(bandwidthcombinationset0,1)
Band2+Band13+Band66
Band2+Band29+Band66
Band2+Band30+Band66
Band3+Band5+Band7
Band3+Band5+Band28
Band5+Band30+Band66
Band12+Band30+Band66
Band29+Band30+Band66

g Note: Asdescribedin3GPPTS36.101,thebandwidthcombinationsetis0ifnot
indicatedotherwise.

3.7.3 LTE3048 system impact


Interdependencies between features
TheLTE3048: Additional Carrier Aggregation Band Combinations 3CC IIIfeatureis
enabledtogetherwiththefollowingfeatures:
LTE1803: Downlink Carrier Aggregation 3CC 40 MHz
LTE1804: Downlink Carrier Aggregation 3CC 60 MHz

Impact on interfaces
TheLTE3048: Additional Carrier Aggregation Band Combinations 3CC IIIfeaturehas
noimpactoninterfaces.

Impact on network management tools


TheLTE3048: Additional Carrier Aggregation Band Combinations 3CC IIIfeaturehas
noimpactonnetworkmanagementtools.

Impact on system performance and capacity


TheLTE3048: Additional Carrier Aggregation Band Combinations 3CC IIIfeaturehas
noimpactonsystemperformanceorcapacity.

72 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

3.7.4 LTE3048 reference data


Requirements

Table 28 LTE3048hardwareandsoftwarerequirements
System Flexi Flexi AirScale BTS Flexi Zone Flexi Zone
release Multiradio Multiradio 10 Micro BTS Access Point
BTS BTS
FDD-LTE17 Notsupported FL17 FL17 Notsupported Notsupported

Flexi Zone OMS UE NetAct MME SAE GW


Controller
Notsupported Supportnot 3GPPR13UE NetAct17.2 Supportnot Supportnot
required capabilities required required

Alarms
TherearenoalarmsrelatedtotheLTE3048: Additional Carrier Aggregation Band
Combinations 3CC - IIIfeature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE3048: Additional Carrier Aggregation Band
Combinations 3CC - IIIfeature.

Commands
TherearenocommandsrelatedtotheLTE3048: Additional Carrier Aggregation Band
Combinations 3CC - IIIfeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE3048: Additional Carrier
Aggregation Band Combinations 3CC - IIIfeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3048: Additional Carrier
Aggregation Band Combinations 3CC - IIIfeature.

Parameters
TherearenoparametersrelatedtotheLTE3048: Additional Carrier Aggregation Band
Combinations 3CC - IIIfeature.

Sales information

Table 29 LTE3048salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense No

DN09237915Issue:01A 2017Nokia 73

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

3.8 LTE3049: Additional FDD-TDD Carrier Aggregation


Band Combinations II
TheLTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations IIfeature
supportsadditionalbandcombinationsfordownlink(DL)FDD-TDDcarrieraggregation
(CA),therebyprovidingmoreoptionstoincreasedownlinkthroughput.

3.8.1 LTE3049 benefits


TheLTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations IIfeature
providesadditionaloptionsforCAand,consequently,higherDLpeakratesinareaswith
overlappingcelldeploymentsforthesupportedFDD-TDDbandcombinations.

3.8.2 LTE3049 functional description

WiththeLTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations II


featureenabled,theeNBsupportsthefollowingadditionalFDD-TDDcarrieraggregation
bandcombinations:

FDD-TDD2CC(FDDasPCell,oneFDDandoneTDDcell):
Band1(FDD5/10/15/20Mhz)+Band41(TDD10/20Mhz)
Band1(FDD5/10/15/20Mhz)+Band42(TDD20Mhz)

FDD-TDD3CC(FDDasPCell,oneFDDandtwoTDDcells):
Band1(FDD5/10/15/20Mhz)+Band41(TDD20Mhz)+Band41(TDD10/20
Mhz)
Band1(FDD5/10/15/20Mhz)+Band41(TDD10/20Mhz)+Band42(TDD20
Mhz)
Band1(FDD5/10/15/20Mhz)+Band42(TDD20Mhz)+Band42(TDD20
Mhz)
Band3(FDD5/10/15/20Mhz)+Band41(TDD20Mhz)+Band41(TDD10/20
Mhz)
Band3(FDD5/10/15/20Mhz)+Band41(TDD10/20Mhz)+Band42(TDD20
Mhz)
Band8(FDD5/10Mhz)+Band41(TDD20Mhz)+Band41(TDD10/20Mhz)
Band28(FDD5/10Mhz)+Band41(TDD20Mhz)+Band41(TDD10/20Mhz)

FDD-TDD3CC(FDDasPcell,twoFDDandoneTDDcell):
Band1(FDD5/10/15/20Mhz)+Band3(FDD5/10/15/20Mhz)+Band41(TDD
10/20Mhz)

g Note: Thebandwidthcombinationsetis0asdescribedin3GPPTS36.101.

InFDD-TDDCA,theFDDcellactsasaPCelloranSCell,andTDDcellsactonlyas
SCells.
Thetransmissionmode3(TM3),TM4,orTM9canbeconfiguredforsiteconfigurations
asrequired.

74 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

TDDframeconfiguration1or2issupportedinTDDcellsandisusedwithTDD
componentcarriers(CCs).

3.8.3 LTE3049 system impact


Interdependencies between features
TheLTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations IIfeature
isenabledtogetherwiththefollowingfeatures:
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
TheLTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations IIfeature
hasnoimpactoninterfaces.

Impact on network management tools


TheLTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations IIfeature
hasnoimpactonnetworkmanagementtools.

Impact on system performance and capacity


TheLTE3049: Additional FDD-TDD Carrier Aggregation Band Combinations IIfeature
hasnoimpactonsystemperformanceorcapacity.

3.8.4 LTE3049 reference data


Requirements

Table 30 LTE3049hardwareandsoftwarerequirementsforFDD
System Flexi Flexi AirScale BTS Flexi Zone Flexi Zone
release Multiradio Multiradio 10 Micro BTS Access Point
BTS BTS
FDD-LTE17 Notsupported FL17 Notsupported Notsupported Notsupported

Flexi Zone OMS UE NetAct MME SAE GW


Controller
Notsupported Supportnot 3GPPR12-14 Supportnot Supportnot Supportnot
required UE required required required
capabilities

Table 31 LTE3049hardwareandsoftwarerequirementsforTDD
System Flexi Flexi AirScale BTS Flexi Zone Flexi Zone
release Multiradio 10 Multiradio 10 Micro BTS Access Point
BTS Indoor BTS
TD-LTE17 TL17 TL17 Notsupported Notsupported Notsupported

DN09237915Issue:01A 2017Nokia 75

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Table 31 LTE3049hardwareandsoftwarerequirementsforTDD(Cont.)
Flexi Zone OMS UE NetAct MME SAE GW
Controller
Notsupported Supportnot 3GPPR12-14 Supportnot Supportnot Supportnot
required UE required required required
capabilities

Alarms
TherearenoalarmsrelatedtotheLTE3049: Additional FDD-TDD Carrier Aggregation
Band Combinations IIfeature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE3049: Additional FDD-TDD Carrier Aggregation
Band Combinations IIfeature.

Commands
TherearenocommandsrelatedtotheLTE3049: Additional FDD-TDD Carrier
Aggregation Band Combinations IIfeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE3049: Additional FDD-TDD
Carrier Aggregation Band Combinations IIfeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3049: Additional FDD-TDD
Carrier Aggregation Band Combinations IIfeature.

Parameters
TherearenoparametersrelatedtotheLTE3049: Additional FDD-TDD Carrier
Aggregation Band Combinations IIfeature.

Sales information

Table 32 LTE3049salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense No

3.9 LTE3056: GPS and UTC Time Information


Broadcast Support (SIB16)
TheLTE3056: GPS and UTC Time Information Broadcast Support (SIB16)feature
introducestheLTEBTSsupportofGPSandUTCtimeinformationbroadcastinsystem
informationblocktype16(SIB16).

76 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

3.9.1 LTE3056 benefits


TheLTE3056: GPS and UTC Time Information Broadcast Support (SIB16)featureallows
toretrievesystemandlocaltimefromthecommonbroadcastingchannel.
BroadcastingreferencetimefromtheLTEnetworkisusefulinthefollowingusecases:

GPStimeforGNSS
CoordinatedUniversalTime(UTC)forMBMS
Localtimeprovisioning

3GPPproposedtointroduceanewSIBtoprovidetheGPStimeandUTCtime.

3.9.2 LTE3056 functional description


FlexiMultiradioBTSsupportsthebroadcastofSIB16.
TheSIB16informationelement(IE)containsinformationrelatedtotheGPStimeand
CoordinatedUniversalTime(UTC).TheUEmayusetheparametersprovidedinthis
systeminformationblocktoobtaintheUTC,theGPS,andthelocaltime.

Figure 5 ContentoftheSIB16,asdescribedin3GPPTS36.331

TheSIB16broadcastisnotsupportedfor1.4-Mhzand3-Mhzcells.
TheLTE3056: GPS and UTC Time Information Broadcast Support (SIB16)feature
introducesanLNBTSfeatureflagtoenableordisabletheSIB16broadcastfunctionona
BTSlevel.IfSIB16isenabledontheBTS,itsconfigurationinaspecificcellschedulelist
canenableordisabletheSIB16onthecelllevel.

3.9.3 LTE3056 system impact


Interdependencies between features
TheLTE3056: GPS and UTC Time Information Broadcast Support (SIB16)feature
affectsthefollowingfeatures:
LTE1441: Enhanced CS Fallback to CDMA/1xRTT (e1xCSFB)
ThisfeatureintroducestheltmOffanddayLtO&Mparameters.Thesetwo
parametershavethesamemeaningaslocalTimeOffsetand
dayLightSavingTimeparametersinSIB16.
LTE2149: Supplemental Downlink Carrier
SIB16isnotbroadcastedinasupplementaldownlinkcarrier(SDLC)cell.
LTE2353: SIB Multiplexing
ThisfeatureremovesthestaticcombinationandsupportsdynamicSIBmultiplexing.
LTE117: Cell Bandwidth 1.4 MHz
LTE116: Cell Bandwidth 3 MHz

DN09237915Issue:01A 2017Nokia 77

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

SIB16isnotbroadcastedona1.4-MHzand3-MHzLTEbandwidthcellevenif
LTE3056isactivatedonaBTSlevel.
LTE891: Timing Over Packet With Phase Synch
WhenbothLTE3056andLTE891areactivated,UTCtiminginformationforLTE3056
canbeacquiredthroughLTE891insteadofGPS.
LTE80: GPS Synchronisation
Thisfeaturecanprovidephasesynchronization;UTCtiminginformationforLTE3056
canbeacquired.
LTE1710: Sync Hub Direct Forward
LTE3071: NB-IoT Inband
ThetransmissionofSIB16messageisnotsupportedinNB-IoT.

Impact on interfaces
TheLTE3056: GPS and UTC Time Information Broadcast Support (SIB16)featurehas
noimpactoninterfaces.

Impact on network management tools


TheLTE3056: GPS and UTC Time Information Broadcast Support (SIB16)featurehas
noimpactonnetworkmanagementtools.

Impact on system performance and capacity


TheLTE3056: GPS and UTC Time Information Broadcast Support (SIB16)featurehas
noimpactonsystemperformanceorcapacity.

3.9.4 LTE3056 reference data


Requirements

Table 33 LTE3056: GPS and UTC Time Information Broadcast Support (SIB16)
hardwareandsoftwarerequirements
System Flexi Flexi AirScale FDD Flexi Zone Flexi Zone
release Multiradio Multiradio 10 Micro BTS Access Point
BTS BTS
FDD-LTE17 Notsupported FL17 FL17 FL17A FL17A

Flexi Zone OMS UE NetAct MME SAE GW


Controller
FL17A Supportnot 3GPPR12UE NetAct17.2 Supportnot Supportnot
required capabilities, required required
3GPPR13UE
capabilities

Alarms
TherearenoalarmsrelatedtotheLTE3056: GPS and UTC Time Information Broadcast
Support (SIB16)feature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE3056: GPS and UTC Time Information Broadcast
Support (SIB16)feature.

78 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Commands
TherearenocommandsrelatedtotheLTE3056: GPS and UTC Time Information
Broadcast Support (SIB16)feature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE3056: GPS and UTC Time
Information Broadcast Support (SIB16)feature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3056: GPS and UTC Time
Information Broadcast Support (SIB16)feature.

Parameters

Table 34 NewparametersintroducedbyLTE3056: GPS and UTC Time Information


Broadcast Support (SIB16)
Full name Abbreviated name Managed Parent structure
object
Activate GPS and UTC actUTCBroadcast LNBTS -
Time Broadcast

Table 35 ParametersmodifiedbyLTE3056: GPS and UTC Time Information


Broadcast Support (SIB16)
Full name Abbreviated name Managed Parent structure
object
System Information sibSchedulingList SIB -
Scheduling List,
extended for SIB16
Indicates which SIB is siMessageSibType SIB -
contained in the SI- (sibSchedulingLis
Message, extended for t)
SIB16
Include day light dayLtIncluded XPARAM -
savings time indicator
Local time offset ltmOffIncluded XPARAM -
included

Table 36 ExistingparametersrelatedtoLTE3056: GPS and UTC Time Information


Broadcast Support (SIB16)
Full name Abbreviated name Managed Parent structure
object
Network synchronization btsSyncMode BTSSCL -
mode
Downlink channel dlChBw LNCEL_F -
bandwidth DD

DN09237915Issue:01A 2017Nokia 79

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Table 37 ParametersmigratedfromMOCXPARAMtoMOCSIBforLTE3056: GPS


and UTC Time Information Broadcast Support (SIB16)
Full name Abbreviated name Managed Parent structure
object
Day light savings time dayLt SIB -
indicator
Local time offset ltmOff SIB -

Forparameterdescriptions,seeFlexi Multiradio BTS LTE Commissioning, RNW and


Transmission Parameters.

Sales information

Table 38 LTE3056: GPS and UTC Time Information Broadcast Support (SIB16)
salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense No

3.9.5 Activating and configuring LTE3056


Before you start
Procedurenotifications
TheeNBisconfiguredforphasesynchronizedmode;Network
synchronization mode (btsSyncMode)parameterissettoPhaseSync.
TheLTE3056: GPS and UTC time information broadcast support (SIB16)feature
mustbedeactivated;Activate GPS and UTC Time Broadcast
(actUTCBroadcast)parameterissettofalse.
Featureinterdependencies
TheLTE3056: GPS and UTC Time Information Broadcast Support (SIB16)feature
affectsthefollowingfeatures:
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
TheeNBisoperational,andtheradionetworkdatabaseisupandrunning.
NetActisoperational,andaDCNconnectiontotheeNBisavailableviaOMS.

80 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

5 Set the Activate GPS and UTC Time Broadcast (actUTCBroadcast)


parameter value to true.

6 Go to the SIB object.


Objectpath:MRBTSLNBTSLNCELSIB

DN09237915Issue:01A 2017Nokia 81

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

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

8 Configure the Periodicity (siMessagePriodicity) and Repetition


(siMessageRepetition) parameters.

9 Optionally, configure the Day light savings time indicator (dayLt)


and Local time offset (ltmOff) SIB parameters.

10 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

c) Click Send Parameters.

Result

TheSIB16isbroadcastedinalleNBcellswhosebandwidthisequalneitherto1.4MHz
nor3MHz.

3.9.6 Deactivating LTE3056


Before you start
Procedurenotifications
TheLTE3056: GPS and UTC time information broadcast support (SIB16)feature
mustbedeactivated;Activate GPS and UTC Time Broadcast
(actUTCBroadcast)parameterissettotrue.
Preconfiguration
TheeNBisoperational,andtheradionetworkdatabaseisupandrunning.
NetActisoperational,andaDCNconnectiontotheeNBisavailableviaOMS.

82 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

5 Set the Activate GPS and UTC Time Broadcast (actUTCBroadcast)


parameter value to false.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

c) Click Send Parameters.

Result

TheSIB16broadcastingisstoppedinalleNBcells.

DN09237915Issue:01A 2017Nokia 83

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

3.10 LTE3073: 256 QAM Extensions


TheLTE3073: 256 QAM ExtensionsfeatureenhancesLTE2479: 256 QAM in Downlink.
TheLTE3073: 256 QAM Extensionsfeatureintroduces:

aperformancemonitoringmechanismtoautomaticallyrestrict/allowtheusageof256
QAMmodulationandcodingschemes.ThismechanismworksonaUElevel.
anewactivation/deactivationmechanismwhichenablesmodifyingtheactivation
parameterwithoutlockingthecell.

3.10.1 LTE3073 benefits


TheLTE3073: 256 QAM Extensionsfeatureprovidesthefollowingbenefit:
In256QAMdeployments,transmissionefficiencyisimprovedinlowsignal-to-
interference-plus-noiseratio(SINR)regionsbyusingthe256QAMchannel
monitoringmechanism.IfaUEiscapableof256QAM,itisconfiguredtousethe
256QAMchannelqualityindicator(CQI)tableonlyifitisinhighSINRconditions.
Otherwise,itisconfiguredwiththeoriginal64QAMCQItable.

3.10.2 LTE3073 functional description


IftheUEexperiencesinsufficientchannelqualityfor256QAMtobeused,itis
reconfiguredtolegacyCQI/MCS/TBStables.Duetohighergranularity,thisallowsfor
highertransmissionefficiencyinlowSINRregions.IftheUE'sperceivedchannelquality
getssufficientgainfor256QAMtobeused,itisreconfiguredbackto256QAM
CQI/MCS/TBStables,whichallowsforhigherdataratesinhighSINRregions.
Thismechanismcanbeenabled/disabledbysettingtheactDl256QamChQualEst
parameter.Furtheradjustmentsofthealgorithmcanbedoneusingthefollowing
operator-configurableparameters:

DecisionperiodforchannelqualityestimationperDl256QamChQualEst
MCSthresholdfordeactivating256QAMfortheUE
dl256QamDeactChQualThr
MCSthresholdforreactivating256QAMfortheUE
dl256QamReactChQualThr

g Note: DependingontheradiohardwarevariantanditsconfiguredoperatingTXpower,
theRFpoweroffsetmustbemodifiedtocomplywiththe3GPP-defined256QAMerror
vectormagnitude(EVM)requirements(EVM=3.5%).FortherecommendedRFpower
offsets,see:
forFDD:Flexi Multiradio BTS RF Module and Remote Radio Head Description
forTD:Flexi Multiradio 10 Base Station TD-LTE RF Module and Remote Radio
Head Description.

TheRFpoweroffset,dlCellPwrRed,isadedicated,O&M,operator-configurable
parameter.

84 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

3.10.3 LTE3073 system impact


Interdependencies between features
TheLTE3073: 256 QAM Extensionsfeatureisimpactedbythefollowingfeature:

LTE2479: 256 QAM in Downlink


TheLTE2479: 256 QAM in Downlinkmustbeenabled.

TheLTE3073: 256 QAM Extensionsfeatureimpactsthefollowingfeatures:


LTE1541: Advanced SCell Measurement Handling
ThisfeaturedefinesMCSthresholdsbasedonwhichSCell(s)andPCellcanbe
added,de-activated,orreleased.TherespectiveO&Mconfigurableparametersare
scellBadChQualThr,scellGoodChQualThrand
scellNotDetectableThr.Thesequalitythresholdsaredefinedforpre-
release12UEs.Startingwithrelease12UEs,configuredtouse256QAMin
downlink,theeNBdoestheinternalconversion.
LTE1496: eICIC Micro
Thecellrangeexpansion(CRE)UEtaggingusesUE-reportedCQI.Every
CQI/MCS/TBSparameterisconvertedfor256-QAM-configuredUEsastheyusenew
CQItables.

Impact on interfaces
TheLTE3073: 256 QAM Extensionsfeaturehasnoimpactoninterfaces.

Impact on network management tools


TheLTE3073: 256 QAM Extensionsfeaturehasnoimpactonnetworkmanagement
tools.

Impact on system performance and capacity


TheLTE3073: 256 QAM Extensionsfeaturehasnoimpactonsystemperformanceor
capacity.

3.10.4 LTE3073 reference data


Requirements

Table 39 LTE3073hardwareandsoftwarerequirements
System Flexi Flexi Airscale Flexi Zone Flexi Zone
release Multiradio Multiradio 10 Micro BTS Access Point
BTS BTS
FDD-LTE17 notsupported FL17 FL17 Notsupported Notsupported

Flexi Zone OMS UE NetAct MME SAE GW


Controller
Notsupported Supportnot UE:3GPP NetAct17.2 Supportnot Supportnot
required R12UE required required
capabilities

Alarms

DN09237915Issue:01A 2017Nokia 85

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

TherearenoalarmsrelatedtotheLTE3073: 256 QAM Extensionsfeature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE3073: 256QAM Extensionsfeature.

Commands
TherearenocommandsrelatedtotheLTE3073: 256 QAM Extensionsfeature.

Measurements and counters

Table 40 NewcountersintroducedbyLTE3073
Counter Counter name Measurement
ID
M8010C CQI Level 00-Level 15 for LTEPowerandQualityDL
132- Codeword 1 Reported by
M8010C 256QAM-configured UEs
147

Table 41 ExistingcountersrelatedtoLTE3073
Counter Counter name Measurement
ID
M8011C PDSCHtransmissionusingQPSKof LTECellResource
196 256QAM-scheduledUE
M8011C PDSCHtransmissionusing16QAMof LTECellResource
197 256QAM-scheduledUE
M8011C PDSCHtransmissionusing64QAMof LTECellResource
198 256QAM-scheduledUE
M8011C PDSCHtransmissionusing256QAMof LTECellResource
199 256QAM-scheduledUE
M8011C PDSCHtransmissionnacksusingQPSK LTECellResource
200 of256QAM-scheduledUE
M8011C PDSCHtransmissionnacksusing16QAM LTECellResource
201 of256QAM-scheduledUE
M8011C PDSCHtransmissionnacksusing64QAM LTECellResource
202 of256QAM-scheduledUE
M8011C PDSCHtransmissionnacksusing LTECellResource
203 256QAMof256QAM-scheduledUE
M8011C FailedPDSCHtransmissionusingQPSK LTECellResource
204 of256QAM-scheduledUE
M8011C FailedPDSCHtransmissionusing LTECellResource
205 16QAMof256QAM-scheduledUE
M8011C FailedPDSCHtransmissionusing LTECellResource
206 64QAMof256QAM-scheduledUE
M8011C FailedPDSCHtransmissionusing LTECellResource
207 256QAMof256QAM-scheduledUE
M8012C MACPDUvolumePDSCHusingQPSK LTECellThroughput
175 of256QAM-scheduledUE

86 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Table 41 ExistingcountersrelatedtoLTE3073(Cont.)
Counter Counter name Measurement
ID
M8012C MACPDUvolumePDSCHusing16QAM LTECellThroughput
176 of256QAM-scheduledUE
M8012C MACPDUvolumePDSCHusing64QAM LTECellThroughput
177 of256QAM-scheduledUE
M8012C MACPDUvolumePDSCHusing LTECellThroughput
178 256QAMof256QAM-scheduledUE
M8010C UEReportedCQILevel00Level15for LTEPowerandQualityDL
116 256QAM-configuredUEs
M8010C
131

Forcounterdescriptions,seeLTE Performance Measurements.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3073: 256 QAM Extensions
feature.

Parameters

Table 42 NewparametersintroducedbyLTE3073
Full name Abbreviated name Managed Parent structure
object
Activate channel actDl256QamChQual MRBTS/L -
quality monitoring for Est NBTS
256QAM usage
Decision period for perDl256QamChQual MRBTS/L -
channel quality Est NBTS/LN
estimation CEL
MCS threshold for dl256QamDeactChQu MRBTS/L -
deactivating 256QAM for alThr NBTS/LN
the UE CEL
MCS threshold for dl256QamReactChQu MRBTS/L -
reactivating 256QAM for alThr NBTS/LN
the UE CEL
Percentage of MCS dl256QamBadChQual MRBTS/L -
samples as bad channel Perc NBTS
quality for 256QAM
Percentage of MCS dl256QamGoodChQua MRBTS/L -
samples as good channel lPerc NBTS
quality for 256QAM
Transmission mode tmSwitchProfileId MRBTS/L -
switch profile NBTS/LN
identifier CEL
Transmission mode tmSwPrId MRBTS/L -
switch profile NBTS/TM
identifier SWPR

DN09237915Issue:01A 2017Nokia 87

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Table 42 NewparametersintroducedbyLTE3073(Cont.)
Full name Abbreviated name Managed Parent structure
object
TM switching threshold tmSwitchThreshold MRBTS/L -
definition 256QAM Def256Qam NBTS/TM
SWPR
CQI threshold for tm3to7CqiTh256Qam MRBTS/L tmSwitchThreshold
switch from TM3 to TM7 NBTS/TM Def256Qam
for 256QAM SWPR
CQI threshold for tm3to8CqiTh256Qam MRBTS/L tmSwitchThreshold
switch from TM3 to TM8 NBTS/TM Def256Qam
for 256QAM SWPR
CQI threshold for tm3to9CqiTh256Qam MRBTS/L tmSwitchThreshold
switch from TM3 to TM9 NBTS/TM Def256Qam
for 256QAM SWPR
CQI threshold for tm7to3CqiTh256Qam MRBTS/L tmSwitchThreshold
switch from TM7 to TM3 NBTS/TM Def256Qam
for 256QAM SWPR
CQI threshold for tm8to3CqiTh256Qam MRBTS/L tmSwitchThreshold
switch from TM8 to TM3 NBTS/TM Def256Qam
for 256QAM SWPR
CQI threshold for tm9to3CqiTh256Qam MRBTS/L tmSwitchThreshold
switch from TM9 to TM3 NBTS/TM Def256Qam
for 256QAM SWPR
CQI threshold from mimoBfslCqiThD256 MRBTS/L -
TxDiv to single layer Qam NBTS/TM
BF for 256QAM SWPR
CQI threshold from mimoBfslCqiThU256 MRBTS/L -
single layer BF to Qam NBTS/TM
TxDiv for 256QAM SWPR

Table 43 ParametersmodifiedbyLTE3073
Full name Abbreviated name Managed Parent structure
object
Active transmission actTmSwitch MRBTS/L -
mode switch NBTS/LN
CEL/LNC
EL_TDD
Beamforming fallbacking actBfFallback MRBTS/L -
activation NBTS/LN
CEL/LNC
EL_TDD
TM switching threshold tmSwitchThreshold MRBTS/L -
definition Def NBTS/TM
SWPR
CQI threshold for tm3to7CqiTh MRBTS/L tmSwitchThreshold
switch from TM3 to TM7 NBTS/TM Def
SWPR
CQI threshold for tm3to8CqiTh MRBTS/L tmSwitchThreshold
switch from TM3 to TM8 NBTS/TM Def
SWPR

88 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Table 43 ParametersmodifiedbyLTE3073(Cont.)
Full name Abbreviated name Managed Parent structure
object
CQI threshold for tm3to9CqiTh MRBTS/L tmSwitchThreshold
switch from TM3 to TM9 NBTS/TM Def
SWPR
CQI threshold for tm7to3CqiTh MRBTS/L tmSwitchThreshold
switch from TM7 to TM3 NBTS/TM Def
SWPR
CQI threshold for tm8to3CqiTh MRBTS/L tmSwitchThreshold
switch from TM8 to TM3 NBTS/TM Def
SWPR
CQI threshold for tm9to3CqiTh MRBTS/L tmSwitchThreshold
switch from TM9 to TM3 NBTS/TM Def
SWPR
CQI threshold from mimoBfslCqiThU MRBTS/L -
single layer BF to NBTS/TM
TxDiv SWPR
Transmission mode tmSwPrId MRBTS/L -
switch profile NBTS/TM
identifier SWPR
CQI threshold from mimoBfslCqiThD MRBTS/L -
TxDiv to single layer NBTS/TM
BF SWPR
CQI threshold from mimoBfslCqiThU MRBTS/L -
single layer BF to NBTS/TM
TxDiv. SWPR
Prohibit timer for prohibitTimerTmSw MRBTS/L -
dynamic TM mode switch itch NBTS/TM
SWPR

Table 44 ExistingparametersrelatedtoLTE3073
Full name Abbreviated name Managed Parent structure
object
Activate modulation actModulationSche MRBTS/L -
scheme DL meDl NBTS/LN
CEL
Cell power reduce dlCellPwrRed MRBTS/L -
NBTS/LN
CEL

Forparameterdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Parameters.

Sales information

Table 45 LTE3073salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense No

DN09237915Issue:01A 2017Nokia 89

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

3.10.5 Activating LTE3073


Before you start
TheLTE3073: 256 QAM ExtensionsfeatureisactivatedtogetherwithLTE2479: 256
QAM in Downlink.
ThemodificationofactivationparameterActivate modulation scheme DL
(actModulationSchemeDl)doesnotrequirecelllockingandhasnoimpacton
services.

g Note:
IftheLTE1117: LTE MBMSfeatureisactivated,256QAMisnotsupportedfor
MBMS-relatedsignaling.
Dependingonthepowerback-off,thecellmaystillneedtobelockedbasedonthe
definitionofthedlCellPwrRedparameter.

3.10.6 Deactivating LTE3073


Before you start
TheLTE3073: 256 QAM ExtensionsfeatureisdeactivatedtogetherwithLTE2479: 256
QAM in Downlink.
ThemodificationofactivationparameterActivate modulation scheme
DL(actModulationSchemeDl)doesnotrequirecelllockingandhasnoimpacton
services.

3.11 LTE3199: Support for Multiple MBSFN and


Synchronization Areas
Benefits, functionality, system impact, reference data, instructions of the feature

TheLTE3199: Support for Multiple MBSFN and Synchronization Areasfeatureenhances


theexistingMultimediaBroadcastMulticastService(MBMS)featureLTE1117with
multipleMultimediaBroadcastMulticastServiceSingleFrequencyNetwork(MBSFN)
support.ThisfeatureallowstheoperatortoconfiguremultipleMBSFNsinacelland
providesadditionalcapacityperEvolvedNodeB(eNB)todeploymultipleservices
acrossdifferentcarriers.

g Note: FortheLTE17release,thisfeaturewillonlybeusableinlaboratoryconditions
andisnotsuitableforfielddeployment.Formoreinformationonlimitations,see
Limitations.

3.11.1 LTE3199 benefits


TheLTE3199: Support for Multiple MBSFN and Synchronization Areasfeaturebenefits
theoperatorasfollows:
TheoperatorcanprovisionuptoeightMBSFNspercell,withoutanyradioresource
overlap.

90 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

TheoperatorcanprovisionuptosixMBMSsynchronizationareas,onasingle
carrier,perMulti-cell/MulticastCoordinatingEntity(MCE).

g Note: ThemaximumnumberofMBSFNSYNCAREAinstancesdependsontheeNB
hardware.

Theoperatorcanuseall,orasubsetof,frequenciessupportedbytheeNBto
provideeMBMSsessions.

3.11.2 LTE3199 functional description


Overview
UnderLTE1117,theeNBmanagesasinglefrequencylayerwithoneMBSFNareaonly.
TheLTE3199: Support for Multiple MBSFN and Synchronization Areasfeatureenhances
thatcapabilitywiththeabilitytoprovisionmultipleMBSFNSYNCareas.EachMBSFN
SYNCareawillcorrespondtoacarrier.Acellmayhavethecapabilitytosupportmultiple
MBSFNareas.
ThefeaturecanbeenabledinoneeNBoncellsworkingondifferentcarrierfrequencies.
Uptoeightnon-overlappingMBSFNareascanbeconfiguredpercell.Amaximum
MBSFNsubframeallocationperMBSFNarea,andatotalpersynchronizationarea,is
configurableviaO&Msetting.UptosixeMBMSsynchronizationareascanbeconfigured
oneacheNB.AcellonagivenfrequencylayercanbelongtoonlyoneMBSFN
synchronizationarea.
TheLTE3199: Support for Multiple MBSFN and Synchronization Areasfeaturealso
enableswarningoperatorsifthereareresourceconstraints,andifMBMSsessions
cannotbestarted.

g Note: IntheLTE3199: Support for Multiple MBSFN and Synchronization Areasfeature,


MBSFNresourcescannotbeoverlapped,thusthesubframeconfigurationforthose
MBSFNsshouldensurethattheresourcesdonotoverlap.TheMBSFNoverlap
capabilityisintroducedwithLTE3552.

Specifically,theLTE3199: Support for Multiple MBSFN and Synchronization Areas


featurebringsthefollowingenhancements:
EightMBSFNareaspercell
UptosixMBSFNSYNCAreasperMCE/eNBallowingmultiplecarriersupport
ThemaximumsubframeallocationperMBSFNandperSYNCareacanbe
configured
AbilitytoconfiguremultipleMBSFNswithnon-overlappingMBSFNsubframes
AdvertisingoftheMBSFNneighborconfigurationinSIB3andSIB5
Newalarmswhensessionscannotbestartedduetoresourceconstraints
Sessionsarenotstartedorsuspendedduetoresourceconstraints

ThefeaturecanbeenabledordisabledpereNBusingO&Msettings.Itsharesa
commonfeatureactivationflagwithLTE1117.

Limitations
FortheLTE17release,thisfeaturewillonlybeusableinlaboratoryconditionsandisnot
suitableforfielddeployment.

DN09237915Issue:01A 2017Nokia 91

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

ThefollowingfunctionalitiesarenotsupportedinLTE17:
MultipleMBSFNareas
MultipleMBSFNSyncareas
ThefollowingrestrictionisaddedintheLTE17release:
DynamicchangeoftheObjectModel(NIDD/PDDB)parametersisnotsupportedin
thexL17.
Asaworkaround,thecustomercanrestarttheeMBMSservice(FRflagsetto
OFF/ON)toapplyanychangesmadetotheparameters.Insuchacase,eNBreset
isnotrequiredandeNBcellsstayonline.

Otherfeaturelimitations:

LTE3199doesnotsupportanycarrierbandwidthlowerthan10MHz
NosupportforpreemptionofMBMSbearersusingAddressResolutionProtocol
(ARP)
MBMSservicecountingnotsupported
MBSFNAreaReservedcellisnotsupported
QCI-65/66notsupportedasMBMSbearers
MBSFNAreareservedcellwhichdoesnotperformMBSFNtransmissionisnot
supported
MultipleeMBMSradiobearers(indifferentMBSFNAreas)forthesamesession,as
identifiedbyauniqueTMGI,arenotsupportedinthesinglecell;thisfunctionalityis
addedbyLTE3552

g Note: ItisrecommendedtomodifytheM1SYNCMOCparametersonlyifthereareno
activeMBMSsessions.

ThefollowinglegacyeMBMSLTE1117functionalitiesremaininLTE17:
Supported:
SingleMBSFNarea
SingleMBSFNSyncarea

Modified:
Sessionsuspension
Absolutetimebasedadmissioncontrol
Admissioncontrolrelatedalarms

LTE4: RAN Sharing,LTE125andLTE2299: IPv6 for U/C-planecanbeenabledalong


withLTE3199andLTE2807.

3.11.3 LTE3199 system impact


LTE3199: Support for Multiple MBSFN and Synchronization Areas impact on features,
interfaces, network management tools, and system performance and capacity

Interdependencies between features


ThefollowingfeaturesmustbeactivatedbeforeactivatingtheLTE3199: Support for
Multiple MBSFN and Synchronization Areasfeature:

92 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

LTE1117: LTE MBMS


TheLTE1117featureintroducedsupportforbroadcastoftheMBMSserviceinLTE
cells.ThefeatureactivationfromLTE1117willbeusedforLTE3199aswell.Existing
MOCs,aswellastheMBSFNdesign,aremodifiedformultipleMBSFNsupport.New
migrationruleshavebeenimplemented.
Theexistingdesignimpactsthefollowing:
TheMCEshallperformadmissioncontrolandsessionallocationbeforethetime
ofMBMSdata,andnotonarrival.Ifthetimeisinthepast,thesessionshallbe
startedimmediatelybasedonthesortedorderoftimeoftheMBMSdata.
TheMCEshallkeepthesessionsuspendedwhenasessioncannotbeadmitted
duetoresourceconstraints.Thesessionresumeswhenpossible.
TheMCEshallnotsendPartial RESETifthereisanadmissioncontrolfailure
sincesessionsarekeptsuspendedandresumed.

LTE891: Timing over Packet with Phase Synchronization


LTE80: GPS Synchronisation
TheLTE3199featuredependsonSYNC-btsSyncModetobesettoPhaseSyncto
provideover-the-airframesynchronizationacrossallthecellsoftheeNBsupporting
theeMBMSusingGlobalPositioningSystem(GPS)orTimingoverPacket(ToP).

TheLTE3199: Support for Multiple MBSFN and Synchronization Areasfeaturemaybe


enabledinparallelwiththefollowingfeatures:
LTE2085: SIB Reception with Parallel Measurement Gaps
LTE1103: Load-based Power Savings for Multi-layer Networks
LTE1203: Load-based Power Saving with Tx Path Switching Off
AcellconfiguredtosupportMBMScanparticipateinload-basedreducedenergy
saving.TheMBMSissentoverport4inanytransmissionmode.Sinceallantennas
atallcellsinthatlayeraresendingthesameMBMSsignalatthesametime,thereis
lessimpactontheMBMScomparedtootherservicesifsomeoftheTxpathsare
switchedoff.Hence,theoperatorhastobewarnednottoactivateLTE1203inareas
thathavelowcelloverlaptoavoidlosinganyservice,MBMSorotherwise.The
operatormaychoosetoensurethattheMBMScellisnotconfiguredforreduced
energysaving(activatethepowersavingsfeature)or,alternatively,canchoosean
MBMScellasthelastcellswitchedtoreducedenergysaving.Nonewconsistency
ruleswillbeaddedtoensurethecellshouldbethelastonetobeconsideredfor
energysavingcandidate,ifanyMBSFNisactive.
LTE3201: eMBMS in RAN-sharing Deployment Support
TheLTE3199featureshouldbeabletoreceivesessionstart/stopmessagesfrom
anyoftheprovisionedM3linksandstartthesessioninthecorrespondingservice
areaonalltherelevantSYNC/MBSFNareas.Admissioncontrolisnotperformedif
theMCE/eNBdeterminesthatthenewsessionrequestisasessionreestablishment.
FeatureinteractionalsoincludesinformingtheMMEthatrelevantapplication
parametershavebeenupdated.TheLTE3201featureisnotaprerequisiteforthe
LTE3199feature.
LTE1834: LTE MBMS Service Continuity
TheLTE3199featureleveragesthecapabilitiesofferedbyLTE1834onMBMS
carrierstomovetheUEstothecorrespondingcarrierstoensureMBMSservice
continuity.WhenactMBMSisdeactivated,thecontentsofmbms-SAIIntraFreq-
r11IEinSIB15isupdatedonlywiththeSAIsprovisionedforintra-frequency
neighborcells(ifconfigured).TheLTE1834featureisnotaprerequisiteforthe
LTE3199feature.

DN09237915Issue:01A 2017Nokia 93

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

LTE2299: Dual Stack IPv4/IPv6 for S1/X2


TheLTE2299featurehastobeenabledalongwiththeactMBMSfeatureflagtobe
abletouseIPv6capability.
LTE2807: IPv6 Support for M1 & M3 Interfaces
LTE2807hastobeenabledalongwiththeactMBMSfeatureflagtobenefitfromthe
IPv6capability
LTE3056: GPS and UTC Time Information Broadcast Support (SIB16)
TheSIB16willenableUEstoreceiveaccuratetiminginformationfortimedisplay,
andforotherpurposes,besideseMBMSserviceannouncements.Itispreferredto
havecellsthatbroadcastbothMBMSandSIB16.ThisfeatureisneededforDASH
playersontheUE.OperatorshavetoensureSIB16isbroadcastedincellswhich
broadcasteMBMS.Therearenoconsistencychecksaddedtoensurethisbehavior.

TheLTE3199: Support for Multiple MBSFN and Synchronization Areasfeatureaffects


thefollowingfeatures:
LTE1891: eNB Power Saving Micro DTX
ThesupportofON/OFFswitchingperOFDMsymboltoreducepowerconsumption
cannotbeappliedduringMBMSsubframetransmission.Thisfeaturecannotbe
enabledalongwiththeLTE3199featureinFDD.
LTE48: Support of High-speed Users
ThisfeaturecannotbeenabledalongwiththeactMBMSfeature.
LTE1496: eICIC-micro
LTE1113: eICIC-macro
WiththeLTE3199feature,LTE1113mustremaindeactivatedasapreconditionfor
featureactivation.
LTE1382: Cell Resource Groups
WiththeLTE3199feature,configuringspecificPLMNsisallowed,howeverfromthe
MBSFNperspective,theseareconsideredfullypooledresources.MBSFN
subframeswillbeavailabletoalltheconfiguredPLMNs.Itisrecommendedtokeep
LTE1382deactivatedwhenMBMSisenabledsinceitishighlycomplextoconfigure
differentpercentageswithintheMBSFNresources.

Impact on interfaces
TheLTE3199: Support for Multiple MBSFN and Synchronization Areasfeatureimpacts
interfacesasfollows:
RRCinterface
NeighCellConfigupdatestoSIB5
SIB13toincludemultipleMBSFNareas
MultipleMCCHsupportincreaseinnumberofPMCHin
MBSFNAreaConfiguration

Impact on network management tools


TheLTE3199: Support for Multiple MBSFN and Synchronization Areasfeaturehasno
impactonnetworkmanagementtools.

Impact on system performance and capacity

94 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

TheLTE3199: Support for Multiple MBSFN and Synchronization Areasfeatureimpacts


systemperformanceandcapacityasfollows:
Throughput
eMBMSmulticarrierdeploymentenablestheeNBtosupportmultipleMBSFNareas
andeMBMSonmultiplecarriers.
Quality
eMBMSmulticarrierdeploymentfeaturedoeswarrantnewqualityrequirements,
sincethetaggingoftheexistingeMBMSUserDataTransmissionSuccessRate
requirementisnotapplicabletocustomereMBMSpacketlossKPIs.

3.11.4 LTE3199 reference data


LTE3199: Support for Multiple MBSFN and Synchronization Areas requirements, alarms
and faults, commands, measurements and counters, KPIs, parameters, and sales
information

Requirements

Table 46 LTE3199hardwareandsoftwarerequirements
System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 notsupported SBTS17A FL17 FL17 FL17A

Flexi Zone OMS UE NetAct MME SAE GW


Controller
notsupported supportnot 3GPPR9UE supportnot supportnot supportnot
required capabilities required required required

Alarms

Table 47 ExistingalarmsrelatedtoLTE3199
Alarm ID Alarm name
7651 BASE STATION OPERATION DEGRADED
7652 BASE STATION NOTIFICATION

BTS faults and reported alarms

Table 48 NewBTSfaultsintroducedbyLTE3199
Fault Fault name Reported alarms
ID
Alarm Alarm name
ID
6856 MBMS session admission 7652 BASE STATION NOTIFICATION
failure - not enough
resources
6857 MBMS session admission - 7652 BASE STATION NOTIFICATION
partial admission only

DN09237915Issue:01A 2017Nokia 95

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Commands
TherearenocommandsrelatedtotheLTE3199: Support for Multiple MBSFN and
Synchronization Areasfeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE3199: Support for Multiple
MBSFN and Synchronization Areasfeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3199: Support for Multiple
MBSFN and Synchronization Areasfeature.

Parameters

Table 49 NewparametersintroducedbyLTE3199
Full name Abbreviated name Managed Parent structure
object
M3TimeReference m3TimeRef LNMCE
M1TimeReference m1TimeRef M1SYNC
MBMSSyncTimeOffset mbmsSyncTimeOffse M1SYNC
t
ElapsedCountIncludesM1 elapsedCountInclu M1SYNC
SyncHeader desHeader
MBSFNStartingSubframe mbsfnStartingSF MBSFN
_FDD
MBSFNSyncAreaInUse syncAreaInUse MBSFNC
EL
MBSFNAreaInUseList mbsfnAreaInUseLis MBSFNC
t EL
MBSFNHiddenList mbsfnHiddenList MBSFNC
EL
MBSFNSyncAreaId syncAreaId MBSFNS
YNCARE
A
MBSFNOverlappingAllowed mbsfnOverlapAllow MBSFNS
ed YNCARE
A
MBSFNSyncAreaPLMN syncAreaPlmnIdLis MBSFNS
identitylist t YNCARE
A
MBSFNsyncareaidentifier mbsfnSyncArea_Fdd MBSFNS
Id YNCARE
A_FDD

Table 50 ParametersmodifiedbyLTE3199
Full name Abbreviated name Managed Parent structure
object
MBMSSYNCPeriod mbmsSyncPeriod M1SYNC

96 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Table 50 ParametersmodifiedbyLTE3199(Cont.)
Full name Abbreviated name Managed Parent structure
object
MBMSSYNCReference mbmsSyncRef M1SYNC
IntegralSeconds integralSecs M1SYNC mbmsSyncRef
FractionalSeconds fractionalSecs M1SYNC mbmsSyncRef
MaximumMBSFNsubframe maxSubfrPShare MBSFN
patternshare _FDD
MBMSServiceArealist mbmsSaiList MBSFN

Table 51 ExistingparametersrelatedtoLTE3199
Full name Abbreviated name Managed Parent structure
object
EARFCNDownlink earfcnDL LNCEL
_FDD
Downlinkchannelbandwidth dlChBw LNCEL
_FDD
Defaultpagingcycle defPagCyc LNCEL
Modificationperiodcoefficient modPeriodCoeff SIB
MBMSneighbourcells mbmsNeighCellConf SIB
configuration igIntraF
Neighborcellsconfiguration mbmsNeighCellConf IRFIM
igInterF
MBSFNAreaIdentity mbsfnAreaId MBSFN
MobileCountryCode mcc MBSFNS syncAreaPlmnIdList
YNCARE
A
MobileNetworkCode mnc MBSFNS syncAreaPlmnIdList
YNCARE
A
MobileNetworkCodelength mncLength MBSFNS syncAreaPlmnIdList
YNCARE
A
MBSFNEARFCN mbsfnEarfcn MBSFNS
YNCARE
A_FDD
MBSFNdownlinkchannel mbsfnDlChBw MBSFNS
bandwidth YNCARE
A_FDD
AllowedMBSFNSyncArea syncSubfrPShareAl MBSFNS
subframepatternshare lowed YNCARE
A
MaximumMBSFNSyncArea maxSyncSubfrPShar MBSFNS
subframepatternshare e YNCARE
A_FDD
MBMSServiceArea mbmsServiceArea MBSFN

DN09237915Issue:01A 2017Nokia 97

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Table 51 ExistingparametersrelatedtoLTE3199(Cont.)
Full name Abbreviated name Managed Parent structure
object
MBMSServiceArea servAreaCharacter LNMCE
Characteristics istics
MBMSServiceAreaId servAreaId LNMCE servAreaCharacteristics
MBMSServiceAreaFECs ervAreaFec LNMCE servAreaCharacteristics
MBMSServiceAreaMaximum servAreaMaxBitRat LNMCE servAreaCharacteristics
BitRate e
MBMSServiceAreaMaximum servAreaMaxSessio LNMCE servAreaCharacteristics
SessionBitRate nBitRate
MBSFNSessionsActive mbsfnSessionsActi MBSFN
ve
AllowedMBSFNsubframe subfrPShareAllowe MBSFN
patternshare d
MulticastchannelScheduling mchSchedulingPeri MBSFN mchInfo
period od
MBMSSYNCPeriod mbmsSyncPeriod MBSFN mchInfo
DRXondurationtimer drxOnDuratT DRX drxProfile2
DRXRetransmissionTimer drxRetransT DRX drxProfile2
DRXondurationtimer drxOnDuratT DRX drxProfile3
DRXRetransmissionTimer drxRetransT DRX drxProfile3
DRXRetransmissionTimer drxRetransT DRX drxProfile4
DRXRetransmissionTimer drxRetransT DRX drxProfile5
DRXRetransmissionTimer drxRetransT LNCEL drxProfile101
DRXRetransmissionTimer drxRetransT LNCEL drxProfile102
DRXRetransmissionTimer drxRetransT LNCEL drxProfile103
DRXOnDurationTimer drxOnDuratT SDRX drxSmartProfile2
DRXRetransmissionTimer drxRetransT SDRX drxSmartProfile2
DRXOnDurationTimer drxOnDuratT SDRX drxSmartProfile3
DRXRetransmissionTimer drxRetransT SDRX drxSmartProfile3
DRXRetransmissionTimer drxRetransT SDRX drxSmartProfile4
DRXRetransmissionTimer drxRetransT SDRX drxSmartProfile5
MBMSsinglefrequencynetwork mbsfnId MBSFN
identifier
MBSFNSyncAreaidentifier mbsfnSyncAreaId MBSFNS
YNCARE
A_FDD
MBSFNCellidentifier mbsfnCelId MBSFNC
EL
M1Syncidentifier m1SyncId M1SYNC
ActivatesupportforMBMS actMBMS LNBTS

98 2017Nokia DN09237915Issue:01A

FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Table 51 ExistingparametersrelatedtoLTE3199(Cont.)
Full name Abbreviated name Managed Parent structure
object
EARFCNforbothDownlinkand earfcn LNCEL
Uplink(TDD)
DRXRetransmissionTimer drxRetransT DRX drxProfile2
(Profile2)
DRXRetransmissionTimer drxRetransT DRX drxProfile3
(Profile3)
DRXOnDurationTimer drxOnDuratT 1 LNCEL drxProfile10
DRXRetransmissionTimer drxRetransT LNCEL drxProfile101
(Profile101)
DRXRetransmissionTimer drxRetransT LNCEL drxProfile102
(Profile102)
DRXOnDurationTimer drxOnDuratT LNCEL drxProfile103
DRXRetransmissionTimer drxRetransT LNCEL drxProfile103
(Profile103)
DRXRetransmissionTimer drxRetransT SDRX drxSmartProfile2
(DRXSmartProfile2)
DRXRetransmissionTimer drxRetransT SDRX drxSmartProfile3
(DRXSmartProfile3)

Sales information

Table 52 LTE3199salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense No

3.12 LTE3201: eMBMS in RAN-sharing Deployment


Support
TheLTE3201: eMBMS in RAN-sharing Deployment Supportfeatureenablesdifferent
operatorstoshareevolvedmultimediabroadcast/multicastservice(eMBMS)resources
fromtheirowncorenetworkonthesameeNB.Thisisperformedinamannersimilarto
theMultipleOperatorCoreNetwork(MOCN)concept.

3.12.1 LTE3201 benefits


TheLTE3201: eMBMS in RAN-sharing Deployment Supportfeatureprovidesthe
followingbenefits:
TheeMBMSservicescanbeenabledinradio-access-networks(RAN)-sharing
deployments.TheLTE3201: eMBMS in RAN-sharing Deployment Supportfeature
benefitstheoperatorwithanefficientandlow-costsolutiontodelivercommon
multimediacontent,offeredbytheLTE1117: LTE MBMSfeature,andwithsuch
advantagesprovidedbytheLTE4: RAN sharingfeatureas

DN09237915Issue:01A 2017Nokia 99

Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

findingmoreeasilyadditionalcellsitesincities
deployingLTEinruralareas
reducingLTEupfrontinvestmentcost
enhancingpeakthroughput
optimizingoverallspectrumcapacity.

TheeMBMSsessionsarenotdroppedincaseofalinkfailurebetweenaneNBand
mobilitymanagemententity(MME),therebyprovidingtheuserwithaseamless
receptionofmultimediacontent.

3.12.2 LTE3201 functional description


Functional overview
TheLTE3201: eMBMS in RAN-sharing Deployment Supportfeatureallowsprovisioning
morethanoneactivelinksbetweentheeNBandMMEs(M3link).MultipleMMEscan
establishlinks(M3links)andeMBMSsessionswiththesameeNB,therebyallowing
RANsharingwheremultipleoperatorsaresharingthesameeNB/multi-cellcoordination
entity(MCE)forprovidingeMBMSservices.
eNB/MCEsupporteMBMSdatasessionswithmultipleMBMSgateways(MBMS-GW).
Sessiontear-downandthereleaseofresourcesaredelayedwithaconfigurableamount
oftimeafterthestreamcontroltransmissionprotocol(SCTP)linkdownisdetected.
Duringthisdelay,existingeMBMSsessionsmaybeswitchedovertoanotherMME.

3.12.3 LTE3201 system impact


Interdependencies between features
TheLTE3201: eMBMS in RAN-sharing Deployment Supportfeatureisanextensionof
theLTE1117: LTE MBMSfeature.
ThereisnospecificfeatureactivationflagfortheLTE3201: eMBMS in RAN-sharing
Deployment Supportfeature.TheLTE3201: eMBMS in RAN-sharing Deployment
SupportfeaturefunctionalityisavailablewhentheLTE1117: LTE MBMSfeatureis
activated.
TheLTE3201: eMBMS in RAN-sharing Deployment Supportfeatureimpactsthe
followingfeatures:
LTE4: RAN Sharing
ThisfeaturecanbeenabledalongwithLTE1117: LTE MBMS.
TheeNB/MCEsupportsmultipleM3linkstodifferentMMEs.
eMBMSsessionscanbeestablishedwithdifferentMMEsanddifferentMBMS-GWs.
LTE2807: IPv6 Support for M1 & M3 Interfaces
TheeNBsupportsamixofIPv4-andIPv6-basedM1andM3links.

g Note: TheeNB'ssupportofamixofIPv4-andIPv6-basedM1andM3linksisnota
dual-stacksupport.

Impact on interfaces
TheLTE3201: eMBMS in RAN-sharing Deployment Supportfeaturehasnoimpacton
interfaces.

100 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Impact on network management tools


TheLTE3201: eMBMS in RAN-sharing Deployment Supportfeaturehasnoimpacton
networkmanagementtools.

Impact on system performance and capacity


TheLTE3201: eMBMS in RAN-sharing Deployment Supportfeaturehasnoimpacton
systemperformanceorcapacity.

3.12.4 LTE3201 reference data


Requirements

Table 53 LTE3201hardwareandsoftwarerequirements
System Flexi Flexi AirScale BTS Flexi Zone Flexi Zone
release Multiradio Multiradio 10 Micro BTS Access Point
BTS Indoor BTS
FDDLTE17 notsupported FL17 FL17 notsupported notsupported

Flexi Zone OMS UE NetAct MME SAE GW


Controller
notsupported notapplicable 3GPPR9 NetAct17.2 3GPPR11 notapplicable

Table 54 ExistingalarmsrelatedtoLTE3201
Alarm ID Alarm name
7657Basestationconnectivitydegraded

Foralarmdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Alarms and Faults.

BTS faults and reported alarms

Table 55 ExistingBTSfaultsrelatedtoLTE3201
Fault Fault name Reported alarms
ID
Alarm Alarm name
ID
M3 interface recovery 7657 Base station
failure connectivity degraded
M3 interface setup failure 7657 Base station
connectivity degraded

Forfaultdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Alarms and Faults.

Commands
TherearenocommandsrelatedtotheLTE3201: eMBMS in RAN-sharing Deployment
Supportfeature.

DN09237915Issue:01A 2017Nokia 101


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE3201: eMBMS in RAN-
sharing Deployment Supportfeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3201: eMBMS in RAN-
sharing Deployment Supportfeature.

Parameters

Table 56 NewparametersintroducedbyLTE3201:eMBMSinRAN-sharing
DeploymentSupport
Full name Abbreviated name Managed Parent structure
object
M3 link bounce m3LinkBounceSupTi LNMCE -
supervision timer mer

Table 57 Modified/impactedparametersbyLTE3201:eMBMSinRAN-sharing
DeploymentSupport
Full name Abbreviated name Managed Parent structure
object
M3 Primary address m3ipAddrPrim LNM3 -
Administrative state administrativeSta LNM3 -
te
LTE MME M3 link lnM3Id LNM3 -
identifier
Activate support for actMBMS LNBTS -
MBMS

Forparameterdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Parameters.

Sales information

Table 58 LTE3201salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense Yes

g Note: TheLTE3201: eMBMS in RAN-sharing Deployment Supportfeaturefunctionality


isavailablewhentheLTE1117: LTE MBMSfeatureisactivated.Thereisacommon
licensefortheLTE1117: LTE MBMSand
LTE3201: eMBMS in RAN-sharing Deployment Supportfeatures.

102 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

3.13 LTE3213: Additional Uplink Carrier Aggregation


Band Combinations I
TheLTE3213: Additional Uplink Carrier Aggregation Band Combinations Ifeature
supportsadditionaluplink(UL)carrieraggregation(CA)bandcombinations,thereby
providingmoreoptionstoincreaseuplinkthroughput.

3.13.1 LTE3213 benefits


TheLTE3213: Additional Uplink Carrier Aggregation Band Combinations Ifeature
supportsadditionalbandcombinationsforCA.Consequently,itguaranteeshigherUL
peakratesinareaswithoverlappingcelldeployments.

3.13.2 LTE3213 functional description

WiththeLTE3213: Additional Uplink Carrier Aggregation Band Combinations Ifeature


enabled,theeNBsupportsthefollowingadditionalcarrieraggregationband
combinations(3CCindownlinkand2CCinuplink):
DL(Band1+Band3+Band7)+UL(Band1+Band3)
DL(Band1+Band3+Band7)+UL(Band1+Band7)
DL(Band1+Band3+Band7)+UL(Band3+Band7)
DL(Band2+Band12+Band30)+UL(Band2+Band12)
DL(Band2+Band12+Band12)+UL(Band2+Band12)Band12contiguous
DL(Band4+Band12+Band30)+UL(Band4+Band12)
DL(Band4+Band12+Band12)+UL(Band4+Band12)Band12contiguous

g Note: Thebandwidthcombinationsetis0asdescribedin3GPPTS36.101.

3.13.3 LTE3213 system impact


Interdependencies between features
TheLTE3213: Additional Uplink Carrier Aggregation Band Combinations Ifeatureis
enabledtogetherwiththeLTE1092: Uplink Carrier Aggregation 2CCfeature.

Impact on interfaces
TheLTE3213: Additional Uplink Carrier Aggregation Band Combinations Ifeaturehas
noimpactoninterfaces.

Impact on network management tools


TheLTE3213: Additional Uplink Carrier Aggregation Band Combinations Ifeaturehas
noimpactonnetworkmanagementtools.

Impact on system performance and capacity


TheLTE3213: Additional Uplink Carrier Aggregation Band Combinations Ifeaturehas
noimpactonsystemperformanceorcapacity.

DN09237915Issue:01A 2017Nokia 103


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

3.13.4 LTE3213 reference data


Requirements

Table 59 LTE3213hardwareandsoftwarerequirements
System Flexi Flexi Airscale BTS Flexi Zone Flexi Zone
release Multiradio Multiradio 10 Micro BTS Access Point
BTS BTS
FDD-LTE17 Notsupported FL17 FL17 Notsupported Notsupported

Flexi Zone OMS UE NetAct MME SAE GW


Controller
Notsupported Supportnot 3GPPR13UE NetAct17.2 Supportnot Supportnot
required capabilities required required

Alarms
TherearenoalarmsrelatedtotheLTE3213: Additional Uplink Carrier Aggregation Band
Combinations Ifeature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE3213: Additional Uplink Carrier Aggregation Band
Combinations Ifeature.

Commands
TherearenocommandsrelatedtotheLTE3213: Additional Uplink Carrier Aggregation
Band Combinations Ifeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE3213: Additional Uplink
Carrier Aggregation Band Combinations Ifeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3213: Additional Uplink
Carrier Aggregation Band Combinations Ifeature.

Parameters
TherearenoparametersrelatedtotheLTE3213: Additional Uplink Carrier Aggregation
Band Combinations Ifeature.

Sales information

Table 60 LTE3213salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense No

104 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

3.14 LTE3230: UL Interference Offsets


3GPPTS36.101introducesrestrictionsconcerningUEs'maximumtransmitpower.
Thoserestrictionsareintroducedtoprotectotherservicesfrominterference.The
LTE3230: UL Interference Offsetsfeaturehelpsoperatortocopewiththerestrictions
affectingouterregionsofbandwidth.Tostayinlinewiththemaximumtransmission
powerrestrictionrequirementsLTE3230: UL Interference Offsetsallowsoperatorto
influencetheuplinkscheduler(UL-S)interferencemeasurementsbyintroducinga
configurableoffset.

3.14.1 LTE3230 benefits


TheLTE3230: UL Interference Offsetsfeaturehelpstheoperatortohandlesituations
whentheUEisoperatingwithareducedtransmitpowerinapartoftheULspectrum.It
issupportedby:
introducingadjustableoffsettotheuplinkinterferencemeasurementtoaffect
schedulingprocess
enablingtheoperatortokeepthephysicaluplinkcontrolchannel(PUCCH)
unaffectedbyallocatingitsresourcesclosertothecenteroftheband

3.14.2 LTE3230 functional description


Functional overview
3GPPTS36.101holdsseverallistsofrestrictionsregardingUEs'maximumtransmit
power.Transmitpowerrestrictionsaretypicallyintroducedtoprotectotherservicesfrom
interference,suchas:
spuriousemissions
harmonicinterference
intermodulationproducts
Theydependonthephysicalresourceblock(PRB)location,includingtheallocationsize
giventotheUE.
Particularrestrictionsconcentrateontheouterregionsoftheradiospectrum,constituting
bandwidthboundaries,whichareusuallysubmittedtotheresourceconfigurationofthe
physicaluplinkcontrolchannel(PUCCH).Toavoidthoserestrictionsaffectingthe
PUCCH,theLTE3230: UL Interference OffsetsfeaturerelocatesthePUCCHregions
towardsthecenterofthecellsbandwidth.Thisestablishesoneinnerphysicalshared
channel(PUSCH)sectionlocatedbetweenPUCCHresourcesandtwoouterPUSCH
regions,withatleastoneofthemunderamaximumUEpowerrestriction.Thisis
contrarytotheLTE825: Uplink Outer Region Schedulingfeaturewhichsupports
schedulingofoneouterregiononly.

DN09237915Issue:01A 2017Nokia 105


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Figure 6 LTE825: Uplink Outer Region Scheduling and


LTE3230: UL Interference Offsetsfeaturecomparison
Nominalsystem LTE825:UL Outer LTE3230:UL Interference
bandwidth RegionScheduling Offsets

PUSCH PUSCH
(outerregion) (outerregion)
PUCCH
PUCCH PUCCH
systembandwidth

PUSCH PUSCH
PRACH
PUSCH
and (eitheror)
(innerregion) (innerregion)
PRACH

PUCCH PUCCH

PUCCH PUSCH
blanked blanked
(outerregion)

LTE3230: UL Interference Offsetsintroducessupportfortwoofthelistedrestrictions.A


specificrestrictionisindicatedandconfiguredbyO&M,establishingtheextentofpower
limitationassumedbytheeNB.TheselectedrestrictiondefinestherangeofUEs
submmitedtoaconfiguredsetting.ThoseUEsarepresumedbytheeNBtooperatewith
reducedULmaximumpower.ItcanrelatetoallUEsoracertainscope.UEsrequire
notificationaboutestablishedrestrictionsviainformationelementsinasystem
informationblocktype2(SIB2).
ULpowerreductionresultsinadecreaseofUEs'maximumthroughputalongwithlower
interferencecreatedintherestrictedPRBranges.Reducedinterferencecausesthose
rangestobefavoredbytheULscheduler,whichiscounterproductive.Toavoid
schedulingintherestrictedranges,anoffsetisintroducedintotheULinterference
measurements.Theoffsetisapercentageofadefaultinterferencecorrectionvalue.The
offsetvalueisaddedintheULscheduler,sothatpreferredschedulingareasare
separatedfromthosewithpowerrestrictions.Throughtheintroductionofinterference
offsetoperatoraffectstheprobabilityofselectionpowerrestrictedPRBsaspreffered
schedulingarea.

g Note: InsituationswhentheAdditionalMaximumPowerReduction(A-MPR)concerns
morethantwoaspects(setsofrestrictionspertainingtoPRBstartingoffsetand
allocationsize),LTE3230: UL Interference Offsetswillavoidtheserestrictionsbyeither
movingtheallocationtoaPRBrangewheretherestrictionsdoesnotapplyormoving
theallocationintoalatertransmissiontimeinterval(TTI)whereresourceswithout
restrictioncanbeallocated.

DividingtheULspectrumisacomplextaskleadingtothecreationofseveralareas
wheredifferentrulesapply.LTE3230: UL Interference Offsetssimplifiestheprocessfor
theoperator,limitingnecessaryactionsto:
specifyingtheparameteractUlPwrRestrScnvalue(identifyingapplicable
restrictionsset)

106 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

specifyingthevalueofasingleinterferenceoffsetintroducedinonePRBregion.It
mayalsoapplytocertainPRBrangesinbothouterschedulingregions.

Table 61 LTE3230: UL Interference OffsetsparameteractUlPwrRestrScn


configurationcases
Parameter Active UL Parameter Active UL
Power Restriction Power Restriction
Scenario Scenario
(actUlPwrRestrScn)set (actUlPwrRestrScn)set to
to band18_26 band30_ns21
LTE3230: UL Interference TheTxpowerrestriction TheTxpowerrestriction
OffsetssupportedUEs appliestoUEssupporting appliestoallUEs
bothband18and26
(restrictionintroducedonlyin
band18)
Cell'sbandwidth 10MHz 10MHz
EstablishedPUSCHregions ULspectrumreconfiguration ULspectrumreconfiguration
donebytheeNBresultsin donebytheeNBresultsin
establishingtwoouterPUSCH establishingtwoouterPUSCH
regions,15PBRseach. regions,7PRBseach.Lower,
Lower,consistingofPRBs#0 consistingofPRBs#0to#6,
to#14,andupper#35to#49 andupper#43to#49
Applicableoffset Aconfigurableoffsetisadded Aninterferenceoffsetisadded
totheULinterference toouterregionsUL
measurementsrelatedto interferencemeasurements,
lowest15PRBs,wheneverUL wheneverULscheduler
schedulerencountersUEs assessesUEsallocation
supportingbothband18and possibilities
26
Comments TheouterPUSCHregionsmaybeconsideredasscheduling
areasifthecentralbandwidthresourcesareusedup.

g Note: WhenLTE3230: UL Interference Offsetsisactivated,andthe


actUlPwrRestrScnparameterisconfigured,thevalueassumedbythe
blanked PUCCH (blankedPucch)parameterisignored.
ThePUCCHPRBsareselectedinamannerthatnarrowsdowntheTxpowerrestriction
setoftheconfiguredscenariotothefollowingcases:
TheUEsPUSCHallocationissubjecttoarestriction,andtheoperator-configured
interferenceoffsetisapplied.Thisoccursineitherthelowerfrequency(parameter
actUlPwrRestrScnvalueissettoband18_26)orinbothouterscheduling
regions(parameteractUlPwrRestrScnvalueissettoband30_ns21).
TheUEsPUSCHallocationwouldfallunderarestriction,butthestructureoftheUL
spectrum(withPUCCHshiftedinward)nolongerallowthisallocationnofurther
actionisrequired.
TheUEsPUSCHallocationwouldfallunderarestriction,buttheschedulerwillnot
useit,meaningthattheallocationismovedtoaschedulingareawithnorestrictions
applied.

Soundingreferencesignal(SRS)resourcesareunaffectedbyanyrestrictionsregarding
LTE3230: UL Interference Offsets.RestrictionsdonotaffectULbandwidth,concentrating
onlimitingthemaximumULpowerincertainPRBranges.

DN09237915Issue:01A 2017Nokia 107


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

g Note: Soundingreferencesignal(SRS)isareferencesignalreceivedbyeNBfromUE.
Itisusedtodeterminethechannelstateandthecarrierfrequenciesitshouldassignto
theUEfortransmission.

3.14.3 LTE3230 system impact


LTE3230: UL Interference Offsets impact on features, interfaces, network management
tools, and system performance and capacity

Interdependencies between features


ThefollowingfeaturesmustbeactivatedparalleltotheLTE3230: UL Interference Offsets
feature:
LTE1130: Dynamic PUCCH Allocation
Oneofthefollowingfeatures:
LTE46: Channel-aware Scheduler (UL)
LTE619: Interference-aware UL Scheduling

ThefollowingfeaturesmustbedeactivatedwhentheLTE3230: UL Interference Offsets


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

TheLTE3230: UL Interference Offsetsfeatureisimpactedbythefollowingfeatures:


LTE2664: Load-based PUCCH Region
TheLTE2664: Load-based PUCCH Regionfeaturecanchangethenumberof
PUCCHPRBsduringruntime.TheLTE3230: UL Interference Offsetsfeaturewill
adjustitsschedulingareaswhenthisisdone.
LTE3128: LTE-M
ItisrecommendedtoconfiguretheLTE-Mnarrowbandsothatitislocatedinthe
centralPUSCHregion.

Impact on interfaces
TheLTE3230: UL Interference Offsetsfeaturehasnoimpactsoninterfaces.

Impact on network management tools


TheLTE3230: UL Interference Offsetsfeaturehasnoimpactonnetworkmanagement
tools.

108 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Impact on system performance and capacity


LTE3230: UL Interference OffsetswillimpactULpeakthroughputineverysituationthat
includesshiftingPUCCHresources.
Inbothband18(onlyUEswithband26capability)andband30,theinnerregionofthe
bandwidthisusedforpeakthroughput.Inband18,peakthroughputisnotreducedby
physicalrandomaccesschanneltransmissiontimeinterval(PRACHTTI)because
PRACHcanbeallocatedinoneofthesideregionscontaining15PRBs.Inband30,
peakthroughputwouldbereducedbyPRACHTTIbecausebothouterregionsare
affectedbythepowerlimitationrestrictions.

3.14.4 LTE3230 reference data


LTE3230: UL Interference Offsets requirements, alarms and faults, commands,
measurements and counters, KPIs, parameters, and sales information

Requirements

Table 62 LTE3230: UL Interference Offsetshardwareandsoftwarerequirements


System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 Notsupported FL17 FL17 FL17 FL17

Flexi Zone OMS UE NetAct MME SAE GW


Controller
FL17 Supportnot 3GPPR8 NetAct17.2 Supportnot Supportnot
required mandatory required required

Alarms
TherearenoalarmsrelatedtotheLTE3230: UL Interference Offsetsfeature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE3230: UL Intrference Offsetsfeature.

Commands
TherearenocommandsrelatedtotheLTE3230: UL Interference Offsetsfeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE3230: UL Interference Offsets
feature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3230: UL Interference Offsets
feature.

Parameters

DN09237915Issue:01A 2017Nokia 109


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Table 63 NewparametersintroducedbyLTE3230: UL Interference Offsets


Full name Abbreviated name Managed Parent structure
object
Activate UL Power actUlPwrRestrScn MRBTS/L
Restriction Scenario NBTS/LN
CEL/LNC
EL_FDD
UL interference offset ulInterferenceOff MRBTS/L
set NBTS/LN
CEL/LNC
EL_FDD

Sales information

Table 64 LTE3230: UL Interference Offsetssalesinformation


Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense No

3.14.5 Activating and configuring LTE3230 for band 18


Instructions to activate and configure the LTE3230: UL Interference Offsets feature for
band 18 using the BTS Site Manager

Before you start


Procedurenotifications
Activationprocedurerequiresobjectlocking.
Activationprocedureusesthefollowingparametersandactivationflags:
actUlPwrRestrScn
ulInterferenceOffset

Featureinterdependencies
ThefollowingfeaturesmustbeactivatedparalleltotheLTE3230: UL Interference
Offsetsfeature:
LTE1130: Dynamic PUCCH Allocation
Oneofthefollowingfeatures:
LTE46: Channel-aware Scheduler (UL)
LTE619: Interference-aware UL Scheduling

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

110 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

LTE1059: Uplink Multi-cluster Scheduling


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

Preconfiguration
TheLNCELobjectparametervalueulsSchedMethodmustbeseteitherto
channel awareorinterference aware.
TheLNCEL_FDDobjectparametervalueactAutoPucchAllocmustbesetto
true.
TheLNCEL_FDDobjectparametervalueulChBwmustbesetto10 MHz.
TheLNCELobjectparametervalueactUlpcMethodmustbesetneitherto
PusschlAwPucchCLnorPuschlAwPucchOL.
TheLNBTSobjectparametervalueactULCAggrmustbesettofalse.
TheLNCEL_FDDobjectparametervalueactPuschMaskmustbesettofalse.
TheLNCEL_FDDobjectparametervalueactUlMultiClustermustbesetto
false.
TheLNCEL_FDDobjectparametervalueselectOuterPuschRegionmust
besettonone.
TheLNCEL_FDDobjectparametervalueactLiquidCellmustbesetto
false.
TheLNCEL_FDDobjectparametervalueactSuperCellmustbesettofalse.
TheLNCEL_FDDobjectparametervalueactCombSuperCellmustbesetto
false.

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

DN09237915Issue:01A 2017Nokia 111


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the LTE Carriers page.

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

5 Proceed to the Radio Network Configuration page.

6 Go to the LNCEL_FDD object.


Objectpath:MRBTSLNBTSLNCELLNCEL_FDD

7 Set parameter values.


Sub-steps

a) Set the actUlPwrRestrScn parameter value to band18_26.


IftheactUlPwrRestrScnparametervalueissettoband18_26then:
TheLNCELobjectparameterearfcnUlshouldshowthevalue23900.

b) Set the ulInterferenceOffset parameter value.

8 Go to the APUCCH_FDD object.


Objectpath:MRBTSLNBTSLNCELLNCEL_FDDAPUCCH_FDD

9 Set the selectPrachRegion parameter value to OuterUpperEdge.

10 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

112 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

c) Click Send Parameters.

3.14.6 Activating and configuring LTE3230 for band 30


Instructions to activate and configure the LTE3230: UL Interference Offsets feature for
band 30 using the BTS Site Manager

Before you start


Procedurenotifications
Activationprocedurerequiresobjectlocking.
Activationprocedureusesthefollowingparametersandactivationflags:
actUlPwrRestrScn
ulInterferenceOffset

Featureinterdependencies
ThefollowingfeaturesmustbeactivatedparalleltotheLTE3230: UL Interference
Offsetsfeature:
LTE1130: Dynamic PUCCH Allocation
Oneofthefollowingfeatures:
LTE46: Channel-aware Scheduler (UL)
LTE619: Interference-aware UL Scheduling

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

Preconfiguration
TheLNCELobjectparametervalueulsSchedMethodmustbeseteitherto
channel awareorinterference aware.
TheLNCEL_FDDobjectparametervalueactAutoPucchAllocmustbesetto
true.

DN09237915Issue:01A 2017Nokia 113


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

TheLNCEL_FDDobjectparametervalueulChBwmustbesetto10 MHz.
TheLNCELobjectparametervalueactUlpcMethodmustbesetneitherto
PusschlAwPucchCLnorPuschlAwPucchOL.
TheLNBTSobjectparametervalueactULCAggrmustbesettofalse.
TheLNCEL_FDDobjectparametervalueactPuschMaskmustbesettofalse.
TheLNCEL_FDDobjectparametervalueactUlMultiClustermustbesetto
false.
TheLNCEL_FDDobjectparametervalueselectOuterPuschRegionmust
besettonone.
TheLNCEL_FDDobjectparametervalueactLiquidCellmustbesetto
false.
TheLNCEL_FDDobjectparametervalueactSuperCellmustbesettofalse.
TheLNCEL_FDDobjectparametervalueactCombSuperCellmustbesetto
false.

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the LTE Carriers page.

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

5 Proceed to the Radio Network Configuration page.

6 Go to the LNCEL_FDD object.


Objectpath:MRBTSLNBTSLNCELLNCEL_FDD

114 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

7 Set parameter values.


Sub-steps

a) Set the actUlPwrRestrScn parameter value to band30_ns21.


IftheactUlPwrRestrScnparametervalueissettoband30_ns21then:
TheMFBIPRobjectparameter(MRBTSLNBTSMFBIPR)
addSpectrEmissReqmustbesetto21.
TheLNCELobjectparameterearfcnUlshouldshowthevalue27710.

b) Set the parameter ulInterferenceOffset value.

8 Go to the APUCCH_FDD object.


Objectpath:MRBTSLNBTSLNCELLNCEL_FDDAPUCCH_FDD

9 Set the selectPrachRegion parameter value to InnerUpperEdge.

10 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

c) Click Send Parameters.

3.14.7 Deactivating LTE3230


Instructions to deactivate the LTE3230: Ul Interference Offsets feature using the BTS
Site Manager

Before you start


Procedurenotifications
Deactivationprocedurerequiresobjectlocking.

Preconfiguration

DN09237915Issue:01A 2017Nokia 115


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

AconnectionbetweentheeNBandthemanagementsystemmustbe
establishedandworking.
TheLTE3230featureisactivated.TheLNCELobjectparameter
actUlPwrRestrScnissettoeitherband18_26orband30_ns21.

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNCEL_FDD object.


Objectpath:MRBTSLNBTSLNCELLNCEL_FDD

5 Set the actUlPwrRestrScn value to none.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

116 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

c) Click Send Parameters.

3.15 LTE3264: Additional PRS Subframe Configurations


TheLTE3264: Additional PRS Subframe Configurationsfeatureintroducessupportfor
additionalsubframeconfigurationsforthepositioningreferencesignal(PRS)
transmission.Thesupportoflocationservices(LCS)allowstodeterminethepositionof
aUEwithintheRAN.TheUEsareabletodetectthePRSandderivemeasurements,
basedonthePRS.

3.15.1 LTE3264 benefits


TheLTE3264: Additional PRS Subframe Configurationsfeatureprovidesthefollowing
benefit:
InmarketswherecustomershaveamixofAirScale/FSMFequipment,theobserved
timedifferenceofarrival(OTDOA)featurerunsusingpositioningreferencesignal
(PRS)transmissiononthesubframes,thusallowingforamoreadaptiveanddiverse
deployment.

3.15.2 LTE3264 functional description


Functional overview
ThefeatureallowsNokiaequipmenttooperateinmarketregionsalreadycommittedto
sendingPRSsymbolsinpredeterminedsubframes.
ThefollowingadditionalsubframeconfigurationsaresupportedforthePRS
transmission:

FDD(5,10,15,and20MHz)
7,14,27,47,67,87,107,127and147witharepetition=1andaperiodicityof160
ms.Inaddition,the5-MHzcellbandwidthsupportsarepetition=2.
TDDUL/DLconfiguration1(10and20MHz)
49,69,129,149witharepetition=1andaperiodicityof160ms.
TDDUL/DLconfiguration2(10and20MHz)
28,48,68,108,128,148witharepetition=1andaperiodicityof160ms.

TheUEisinformedaboutthePRSconfigurationviatheLTEpositioningprotocol(LPP).
TheLPPisaprotocoldefinedbetweentheUEandtheenhancedservingmobilelocation
centre(E-SMLC).ItcommunicatesthePRSsettingsofthenetworktotheUEsaswellas
theOTDOAmeasurements(alsocalledareferencesignaltimedifference(RSTD))from
theUEstotheE-SMLC.TheLPPprotocolentitiesaretransparenttotheeNBs,andthe
computationoftheUEpositionsisdoneintheE-SMLC.Theoperatorneedstoprovide
PRSsettingsofthenetworkandantennapositionsofeNBstotheE-SMLC.

DN09237915Issue:01A 2017Nokia 117


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

3.15.3 LTE3264 system impact


Interdependencies between features
TheLTE3264: Additional PRS Subframe Configurationsfeatureisanextensionofthe
LTE495: OTDOAfeature.
TheLTE3264: Additional PRS Subframe Configurationsfeatureisenabledtogetherwith
theLTE495: OTDOA.
TheLTE3264: Additional PRS Subframe Configurationsfeatureimpactsthefollowing
features:
LTE1117: LTE MBMS
TheoperatorhasadditionalchoicesonwheretopositionthePRSsubframes.FDD-
specificMBMSsubframepatternsnowsupportprsConfigurationIndex
parametervaluesof7,14,27,47,67,87,107,127,147.
LTE3199: Support for Multiple MBSFN and Synchronization Areas
Thisfeatureisafollow-uptotheLTE1117: eMBMSfeature,inwhichacellcan
supportmultipleMBSFNareas,andaneNBcanprovideeMBMSserviceson
multiplecarriers.
LTE3200: Dynamic Allocation of eMBMS Resources
Thisfeatureisafollow-uptotheLTE1117: eMBMSfeature,inwhichanactive
numberofeMBMSsessionswilldynamicallyadjustthenumberofeMBMS
subframesallocated.NewsubframesthatcanbeusedforOTDOAmustbeexcepted
fromMBMSusage.
LTE1891: eNode B Power Saving Micro DTX
IftheLTE3264: Additional PRS Subframe Configurationsfeatureisactivated,micro
DTXhastoconsiderthatOFDMsymbolsusedforOTDOAarefoundindifferent
locations.
LTE2085: SIB Reception with Parallel Measurement Gaps
Thelistshowingthesubframeusageforvariousfunctionshastobeupdated.
ThecurrentSIBtimingallowsnewPRSlocations.
LTE1987: Downlink Adaptive Closed Loop SU MIMO (4x4)
LTE1709: Liquid Cell
LTE1543: 8x2 SU MIMO with TM9
LTE3128: LTE-M
Thisfeatureneedstoadaptthepatternofvalidsubframes.
LTE2120: TDD SIB Reception with Parallel Measurement Gaps
DLschedulerhastohandlethecollisionbetweenthenewPRSconfigurationsand
SIBschedulingsubframeswhenLTE2120isactivated.

Impact on interfaces
TheLTE3264: Additional PRS Subframe Configurationsfeaturehasnoimpacton
interfaces.

Impact on network management tools


TheLTE3264: Additional PRS Subframe Configurationsfeaturehasnoimpacton
networkmanagementtools.

Impact on system performance and capacity

118 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

TheLTE3264: Additional PRS Subframe Configurationsfeaturehasnoimpactonsystem


performanceorcapacity.

3.15.4 LTE3264 reference data


Requirements

Table 65 LTE3264hardwareandsoftwarerequirements
System Flexi Flexi AirScale BTS Flexi Zone Flexi Zone
release Multiradio Multiradio 10 Micro BTS Access Point
BTS BTS
FDDLTE17 notsupported FL17 FL17 FL17 FL17

Flexi Zone OMS UE NetAct MME SAE GW


Controller
FL17 - 3GPPR8UE NetAct17.2 - -
capabilities

Alarms
TherearenoalarmsrelatedtotheLTE3264: Additional PRS Subframe Configurations
feature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE3264: Additional PRS Subframe Configurations
feature.

Commands
TherearenocommandsrelatedtotheLTE3264: Additional PRS Subframe
Configurationsfeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE3264: Additional PRS
Subframe Configurationsfeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3264: Additional PRS
Subframe Configurationsfeature.

Parameters

Table 66 ExistingparametersrelatedtoLTE3264
Full name Abbreviated name Managed Parent structure
object
Max phase drifting maxPhaseDrifting BTSSCL -
PRS activation actOtdoa LNCEL -
PRS Tx diversity actPrsTxDiv LNCEL -
activation
PRS bandwidth prsBandwidth LNCEL -

DN09237915Issue:01A 2017Nokia 119


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Table 66 ExistingparametersrelatedtoLTE3264(Cont.)
Full name Abbreviated name Managed Parent structure
object
PRS configuration index prsConfigurationI LNCEL -
ndex
PRS muting prsMuting LNCEL -
PRS muting info prsMutingInfo LNCEL prsMuting
PRS muting info pattern prsMutingInfoPatt LNCEL prsMuting
length ernLen
PRS Number of DL frames prsNumDlFrames LNCEL -
PRS power boost prsPowerBoost LNCEL -
SI window length siWindowLen LNCEL -
DRX on duration timer drxOnDuratT LNCEL -
Downlink channel dlChBw LNCEL -
bandwidth
Network synchronization btsSyncMode BTSSCL -
mode
Activate supercell actSuperCell LNCEL -
configuration
Activate liquid cell actLiquidCell LNCEL -
configuration
Activate LPPa support actLPPaOtdoa LNCEL -
for OTDOA
Activate support for actMBMS LNCEL -
MBMS
MBSFN EARFCN mbsfnEarfcn MBSFN -
MBSFN downlink channel mbsfnDlChBw MBSFN -
bandwidth
Activation ETWS support actETWS LNBTS -
Activation CMAS support actCMAS LNBTS -
Twofold transmission of sib2xTransmit SIB -
SIBs per SI window
Activate enhanced actEicic LNCEL -
inter-cell interference
coordination
CSI-RS subframe csiRsSubfrConf LNCEL -
configuration

Parameterrelationships:

IfbtsSyncModeissettoPhaseSync,maxPhaseDriftingmustbeconfigured.
IfactOtdoaissettotrue:
siWindowLenmustbesetappropriately,dependingontheindividualPRS
configuration.Fordetailsonappropriatevalues,seethesiWindowLen
parameterinReference documentation.

120 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

configurationofthefollowingparametersisrequired:prsPowerBoost,
prsConfigurationIndex,prsBandwidth,prsNumDlFrames,
actPrsTxDiv.
IfnumOfTxPortsissetto1,actPrsTxDivmustbesettofalse.
IfactPrsTxDivissettotrue:
drxProfile2-drxOnDuratTmustbegreaterthan3.
drxProfile3-drxOnDuratTmustbegreaterthan3.
TherangeoftheprsBandwidthparameterdependsondlChBw.

Forparameterdescriptions,seeLTE Radio Access Operating


Documentation/Reference/Parameters.

Sales information

Table 67 LTE3264salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense No

3.15.5 Activating LTE3264


Before you start
TheLTE3264: Additional PRS Subframe Configurationsfeatureisenabledaslongasthe
LTE495: OTDOAfeatureisenabled.

3.15.6 Deactivating LTE3264


Before you start
TheLTE3264: Additional PRS Subframe Configurationsfeatureisdeactivatedwhenthe
LTE495: OTDOAfeatureisdeactivated.

3.16 LTE3279: Support for Configurable eMBMS SYNC


Protocol
Benefits, functionality, system impact, reference data, instructions of the feature

TheLTE3279: Support for Configurable eMBMS SYNC Protocolfeatureenhancesthe


LTE1117: LTE Multimedia Broadcast Multicast Service (MBMS)featurebyintroducing
SYNCprotocolconfiguration,andintegrationtoworkwithdifferentBroadcast/Multicast
ServiceCenters(BM-SC).

g Note: FortheLTE17release,thisfeaturewillonlybeusableinlaboratoryconditions
andisnotsuitableforfielddeployment.Formoreinformationonlimitations,see
Limitations.

DN09237915Issue:01A 2017Nokia 121


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

3.16.1 LTE3279 benefits


TheLTE3279: Support for Configurable Evolved Multimedia Broadcast Multicast Service
(eMBMS) SYNC ProtocolfeatureimprovestheoperabilityoftheeMBMSserviceby
givingtheoperatoraccesstomoreconfigurationoptionsthroughtheintroductionof:
SYNCprotocolconfiguration
SYNCprotocolintegrationtoworkwithdifferentBM-SCs

3.16.2 LTE3279 functional description


Overview
EvolvedMultimediaBroadcastMulticastService(eMBMS)isthemulticaststandardfor
LTE.Itallowsmultimediacontenttobesentonceandthendistributedtoandreceivedby
multipleendusers.Thisdistributionmethodisanalternativetounicastforscenarios
whereinalargenumberofusersareinterestedinthesamecontent.
InLTE,eMBMSallowsthecombiningofMBMStransmissions.Thisisknownasa
MultimediaBroadcastSingleFrequencyNetwork(MBSFN)transmission.InanMBSFN
transmission,alleNBsinagivenMBSFNareamusthavetheradiotransmissionssent
withinthesametimingsequence.TheSYNCprotocolisusedtosynchronizetheradio
interfacetransmissionsofdatafromalleNBsbelongingtothatMBSFNarea.Itallows
theeNBtoidentifythetimingforradioframetransmissionsanddetectpacketloss.The
SYNCprotocolinaBM-SCsetsatimestampvalueindicatingthetimeofthe
synchronizationsequence.Thistimestampisbasedonatimereference;differentBM-
SCvendors,however,usedifferenttimereferences.
TheLTE3279: Support for Configurable eMBMS SYNC Protocolfeatureprovidesthe
flexibilitytoswitchbetweendifferenttimereferenceconfigurationoptionsusedby
differentBM-SCvendors.ThefeatureisrequiredforInternetofThings(IoT)withdifferent
BM-SCvendors.
ThefollowingchannelsandinterfacesareusedintheoperationoftheLTE3279feature:
Multicastcontrolchannels(MCCH)-thischanneltransportscontrolcontentsuchas
MBMSsub-frameallocationinformationandmodulationschemeformobileusers
M1interface:auserplaneinterface;theSYNCprotocolisusedtoensurethat
contentissynchronizedforMBSFNtransmissions
M2interface:acontrolplaneinterface,theM2interfacecarriessessioncontrol
signalingtotheeNB
M3interface:acontrolplaneinterface,theM3interfacecarriessessioncontrol
signaling,includingMBMS'SessionStart'and'SessionStop'messages.

WiththeLTE3279: Support for Configurable eMBMS SYNC Protocolfeature,the


followingO&MconfigurationoptionsareprovidedontheeNBandBM-SC:
Configurable M3 time reference
TimebaseusedbyBM-SCforM3:
CoordinatedUniversalTime(UTC)
InternationalAtomicTime(TAI)
GlobalPositioningSystem(GPS)

122 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Configurable M1 time reference


TimebaseusedbyBM-SCforM1:
GregorianUTC
AutoAdjustLeapUTC
GPS

Time offset
TimeoffsettoaccountforthetimestampnotfallingwithintheeNBscheduling
windowfortheeNBandBM-SC
Elapsed Octet Count including or excluding Sync Header
TheinclusionorexclusionoftheM1SYNCPDUheaderintheelapsedoctetcounter

ThefeatureisanenhancementoftheLTE1117: LTE MBMSfeatureandisavailableonce


theLTE1117featureisenabled.ItusestheactMBMSfeatureflagusedbytheLTE1117
feature.

Configurable M3 time reference


AconfigurablecommontimereferencewithBM-SC,indicatedovertheM3interface,is
supported.ThiscommontimereferenceinterpretstheabsolutetimeoftheMBMSdata
fromtheBM-SC.
M3 time reference - time formats
Thethreepossibletimeformatsare:

TAI:ContinuoustimeinsecondsfromJan-01-1900(Doesnotincludeleapseconds)
UTC:TimeinsecondsfromJan-01-1970(UnixTimeDoesnotautomaticallyadjust
forleapseconds)
GPS:ContinuoustimeinsecondsfromJan-06-1980(Doesnotincludeleap
seconds)

Dependingonthetimeformatselected,thetimeneedstobeadjustedappropriately.

g Note:
TAI=InternationalAtomicTime(thesamereferenceasGregorianJan-01-1900)
GPS=GlobalPositioningSystem
TAI=GPS+19seconds(fixedoffset)
TAI=UTC+19seconds(fixedoffset)+17seconds(currentvalueofvariable
offset)

Configurable M1 time reference


TheeNBidentifiesthetimingofradioframetransmissions,basedontheinformation
receivedandtheconfigurablecommontimereference.TheeNBsupportsaconfigurable
commontimereferencewithBM-SCtointerpretthetimestampintheSYNCPDUfrom
theBM-SC.
M1 time reference - time formats
Thethreepossibletimeformatsare:

DN09237915Issue:01A 2017Nokia 123


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

GregorianUTC:TimeinsecondsfromJan-01-1900(Doesnotautomaticallyadjust
forleapseconds)
AutoAdjustLeapUTC:TimeinsecondsfromJan-01-1900(Automaticallyadjusts
forleapseconds)
GPSContinuoustimeinsecondsfromJan-06-1980(DoesnotincludeLeap
Seconds)

Dependingonthetimeformatselected,thetimeneedstobeadjustedappropriately.

Time offset
WiththeLTE3279feature,theeNBsupportsaconfigurableSyncTimeOffsetthatis
usedwhentheM1timereferenceissettoGPS.

Elapsed Octet Count including or excluding Sync Header


WiththeLTE3279feature,theeNBsupportsaconfigurableparameterwhichindicates
whethertheElapsedOctetCount(sentbytheBM-SC)includesorexcludestheSync
Header.

Limitations
FortheLTE17release,thisfeaturewillonlybeusableinlaboratoryconditionsandisnot
suitableforfielddeployment.
ThefollowingrestrictionisaddedinLTE17release:
AlleMBMSscenariosmustbepresentedwiththefollowingdefaulttime
synchronizationsettings
M1linktimereference:GregorianUTC
M3linktimereference:TAI

Theabovesettingsarealignedwiththe3GPPrecommendations.

3.16.3 LTE3279 system impact


LTE3279: Support for Configurable eMBMS SYNC Protocol impact on features,
interfaces, network management tools, and system performance and capacity

Interdependencies between features


ThefollowingfeaturemustbeactivatedbeforetheLTE3279: Support for Configurable
eMBMS SYNC Protocolfeaturecanbeused:
LTE1117: LTE MBMS
TheLTE3279: Support for Configurable eMBMS SYNC Protocolfeatureisautomatically
enabledwhenLTE1117isenabledanddoesnotrequireactivation.

Impact on interfaces
TheLTE3279: Support for Configurable eMBMS SYNC Protocolfeaturehasnoimpact
oninterfaces.

Impact on network management tools

124 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

TheLTE3279: Support for Configurable eMBMS SYNC Protocolfeaturehasnoimpact


onnetworkmanagementtools.

Impact on system performance and capacity


TheLTE3279: Support for Configurable eMBMS SYNC Protocolfeaturehasnoimpact
onsystemperformanceorcapacity.

3.16.4 LTE3279 reference data


LTE3279: Support for Configurable eMBMS SYNC Protocol requirements, alarms and
faults, commands, measurements and counters, KPIs, parameters, and sales
information

Requirements

Table 68 LTE3279hardwareandsoftwarerequirements
System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 notsupported SBTS17 FL17 FL17 FL17A

Flexi Zone OMS UE NetAct MME SAE GW


Controller
notsupported supportnot 3GPPR9UE supportnot supportnot supportnot
required capabilities required erquired required

Alarms
TherearenoalarmsrelatedtotheLTE3279: Support for Configurable eMBMS SYNC
Protocolfeature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE3279: Support for Configurable eMBMS SYNC
Protocolfeature.

Commands
TherearenocommandsrelatedtotheLTE3279: Support for Configurable eMBMS
SYNC Protocolfeature.

Measurements and counters

Table 69 NewcountersintroducedbyLTE3279
Counter Counter name Measurement
ID
M8030C M1 SYNC Average Sequences M8030-LTEMBMS
7 Delay
M8030C M1 SYNC Control PDUs M8030-LTEMBMS
8
M8030C M1 SYNC Not Received Control M8030-LTEMBMS
9 PDUs

DN09237915Issue:01A 2017Nokia 125


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Table 69 NewcountersintroducedbyLTE3279(Cont.)
Counter Counter name Measurement
ID
M8030C M1 SYNC Data PDUs M8030-LTEMBMS
10

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3279: Support for
configurable eMBMS SYNC protocolfeature.

Parameters

Table 70 NewparametersintroducedbyLTE3279
Full name Abbreviated name Managed Parent structure
object
M1timereference m1TimeRef MRBTS/L
NBTS/M1
SYNC
M3timereference m3TimeRef MRBTS/L
NBTS/LN
MCE
MBMSsynctimeoffset mbmsSyncTimeOffse MRBTS/L
t NBTS/M1
SYNC
ElapsedcountincludesM1Sync elapsedCountInclu MRBTS/L
header desHeader NBTS/M1
SYNC

Table 71 ExistingparametersrelatedtoLTE3279
Full name Abbreviated name Managed Parent structure
object
ActivatesupportforMBMS actMBMS MRBTS/L
NBTS
MBMSSYNCperiod mbmsSyncPeriod MRBTS/L
NBTS/M1
SYNC
MBMSSYNCreference mbmsSyncRef MRBTS/L
NBTS/M1
SYNC

Sales information

Table 72 LTE3279salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) PoolLicense No

126 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

3.16.5 Activating and configuring LTE3279


Instructions to activate and configure the LTE3279: Support for Configurable eMBMS
SYNC Protocol feature using the BTS Site Manager

Before you start


TheLTE3279featureisanenhancementofLTE1117andLTE3199.Itisrecommended
tochecktheactivationprocedurefortheactMBMSparameterusedbyLTE1117and
LTE3199priortoactivatingandconfiguringLTE3279.

Theactivationprocedurerequiresthefollowing:
TheeNBmusthaveanactivatedRNWdatabase.
TheeNBmustbeinservice.
NetActmustbeinservice.ADCNconnectiontotheeNBmustbeestablishedvia
OMS.
AtleastoneS1linkmustbeestablished.
MBMS-relatedinformationinthetransportdomainmustbeconfigured.
MBMSmustbedeactivated.TheLNBTSparameteractMBMSissettofalse.
AtleastoneMBSFNCEL(LNCEL:MBSFNCEL)objectmustbedefinedper
MBSFNSYNCAREA_FDDobject.

Featureinterdependencies
ThefollowingfeaturemustbeactivatedtogetherwiththeLTE3279: Support for
Configurable eMBMS SYNC Protocolfeature:
LTE1117: LTE MBMS

g Note: TheLTE3279featureisanenhancementofLTE1117.TheLTE1117featureuses
thesameactivationparameterasLTE3279.

ThefollowingfeatureisrelatedtotheLTE3279: Support for Configurable eMBMS


SYNC Protocol:
LTE3199: Support for Multiple MBSFN and Synchronization Areas

Otherinformation:
TheMCEconfigurationmustbealignedbetweencellsbelongingtothesame
MBSFNsynchronizationarea.Parametersandtheconfigurationoptionsare
listedinConfigurationdetailsofLTE3279.
TheconfiugrationoftheLTE3199: Support for Multiple MBSFN and
Synchronization AreasmayhaveaneffectontheLTE3279feature.Refertothe
LTE3199featuredocumentfortheactivationandconfigurationprocedure.

Procedure

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

DN09237915Issue:01A 2017Nokia 127


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

2 Start commissioning.
Sub-steps

a) Select View Commissioning or click Commissioning on the View Bar on


the left.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

5 Set the actMBMS value to true.

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

7 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

c) Click Send Parameters.

Result

Expectedoutcome

TheLTE3279featureisenabled.
TheconfiguredinformationispersistentlystoredintheeNB.

128 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

3.16.5.1 Configuration details of LTE3279

Thefollowingmustbeconfigured:

Name Range and step Default Setting


M1timereference GregorianUTC(0) GregorianUTC(0)
M1SYNC:m1TimeRef AutoAdjustLeapUTC(1)
GPS(2)

M3timereference TAI(0) TAI(0)


LNMCE:m3TimeRef UTC(1)
GPS(2)

MBMSsynctimeoffset 0to599990ms,step10ms 0
M1SYNC:mbmsSyncTimeOf
fset

ElapsedcountincludesM1 0(false) 0(false)


Syncheader 1(true)
M1SYNC:elapsedCountIn
cludesHeader

g Note:
IfM1SYNC:m1TimeRef issettoGregorianUTCorAutoAdjustLeapUTC,
parametersfromstructureM1SYNC:mbmsSyncRefaremandatory.
IfM1SYNC:m1TimeRefissetotoGPS,thenthe
M1SYNC:mbmsSyncTimeOffsetparameterisusedtospecifythetimeoffset
betweenBM-SCandeNB.
IfM1SYNC:m1TimeRefissettoGPS,thenM1SYNC:mbmsSyncTimeOffsetis
mandatory.

M1SYNC parameters

m1TimeRefM1TimeReference
ThisparameterrepresentsthetimereferenceusedfortheM1interface.Itreflects
thetimereferenceusedbytheBM-SCtotimestampMBMSsyncPDUs.Thevalueof
thisparametermustbethesameasusedbytheBM-SCastheCommonTime
Reference.
mbmsSyncTimeOffsetMBMSSyncTimeOffset
ThisparameterspecifiesthetimeoffsetbetweentheBM-SCandtheeNB.Thetime
stampinthesyncheaderminusmbmsSyncTimeOffsetwillbeusedbytheeNB.
AlltheeNBshavethesameoffsetforagivenbearerservice.Anymodifications
madeshouldalsobemadeontheBM-SC.Thisparameter,however,canbeusefulif
eNBsarenotsynchronizedwithoneorseveralBM-SCs.Thevaluespecifiedinthis
parameterappliestoallM1bearers.
elapsedCountIncludesHeaderElapsedCountIncludesM1SyncHeader
Thisparameterindicatesiftheelapsedoctetcountincludesthesyncheader.This
parameterneedstobesetcarefullybasedonBMSCcompatibility.

DN09237915Issue:01A 2017Nokia 129


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

MCE parameters

m3TimeRefM3TimeReference
ThisparameterrepresentsthetimereferenceusedbytheBM-SCovertheM3
interface.ThedefaultvalueofTAIisconsideredthe3GPPstandarddefaultvalue.
ThevalueofthisparametermustbethesameasusedbytheBM-SCasthe
CommonTimeReference.

3.16.6 Deactivating LTE3279


Instructions to deactivate the LTE3279:Support for Configurable eMBMS SYNC Protocol
feature using the BTS Site Manager

Before you start


TheLTE3279featureisanenhancementofLTE1117andLTE3199.Itisrecommended
tocheckthedeactivationprocedurefortheactMBMSparameterusedbyLTE1117and
LTE3199priortodeactivatingLTE3279.

Thedeactivationprocedurerequires:
TheeNBmustbeinservice,andhaveanactivatedRNWdatabase.
NetActisinserviceandaDCNconnectiontotheeNBisestablishedviaOMS.
TheLTE3279featureisactivated.TheLNBTSparameteractMBMSissetto
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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

130 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

5 Set the actMBMS value to false.

g Note: Optionally,allMBMS-relatedconfigurationinLNMCE, M1SYNC,


MBSFNSYNCAREA_FDD, MBSFN_FDD, LNM3, LNCEL, MBSFNCEL, SIBand
IRFIMmayberemoved.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

c) Click Send Parameters.

Result

Expectedoutcome
TheLTE3279featureisdeactivated.

3.17 LTE3290: SRVCC Trigger Enhancement


Benefits, functionality, system impact, reference data, instructions of the feature

TheLTE3290: SRVCC Trigger Enhancementfeatureintroducesanewparameterto


controlthetriggerofthesingleradiovoicecallcontinuity(SRVCC)procedure.The
SRVCCallowsaseamlesshandoverprocedurebetweenLTEandWCDMA/GSM,butit

DN09237915Issue:01A 2017Nokia 131


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

canberejectedbytheIMSiftriggeredtooearly.Thenew,operator-configurable
parameterdelaysthestartoftheSRVCCandpreventstheprocedurefrombeing
rejectedbytheIMS.

3.17.1 LTE3290 benefits


TheLTE3290: SRVCC Trigger Enhancementfeatureimprovesthesuccessrateofinter-
RAThandovers.TheIMSnolongerrejectsthesingleradiovoicecallcontinuity(SRVCC)
procedureduringtheearlyphaseoftheVoLTEcallsetupifthesrvccDelayTimer
parameterisactive.

3.17.2 LTE3290 functional description


An overview of how the configurable timer prevents the SRVCC procedure from being
rejected during the initial phase of VoLTE establishment

Functional overview
TheLTE3290: SRVCC Trigger Enhancementfeaturepreventsthesingleradiovoicecall
continuity(SRVCC)procedurefrombeingrejectedbytheIMS.
Singleradiovoicecallcontinuity(SRVCC)isamechanismtohandoverUEsthathavea
QCI-1bearer(VoIP)activatedwhenchangingfromanLTEcelltoaWCDMA/GSMcell.
Thevoicebearer,thatissubjecttoahandover(HO),isservedviathecircuit-switched
(CS)domainontheWCDMA/GSMside.SRVCCisalwaysexecutedwithoutapacket-
switched(PS)-handoversupport(itmeansthatestablishednon-voicebearersarenot
handedovertoWCDMA/GSM).

Figure 7 VoLTEcallsetupwithSRVCCdelaytimer

132 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

IMSmayrejecttheSRVCCprocedureduringthepre-alertingandalertingphasesof
VoLTEcallsetupprocedure,whichmayleadtoVoLTEcalldrops.Toavoidsucha
rejection,thesrvccDelayTimerparameter(whichisalsousedtoactivatethe
LTE3290: SRVCC Trigger Enhancementfeature)delaysthestartoftheSRVCC
procedure.ThetimerstartsafterthefirstQCI-1bearersetup.WhentheeNBreceives
theA2eventtrigger,itconfiguresandactivatesSRVCC-relatedB2measurements.
EveryB2SRVCC-relatedmeasurementreportsentbytheUEisdiscardedbytheeNB
duringthesrvccDelayTimerperiod.WhenthesrvccDelayTimertimerexpires,
thenextB2SRVCC-relatedmeasurementreportcantriggertheSRVCCprocedure
normally,asdescribedintheLTE872: SRVCC to WCDMAandLTE873: SRVCC to GSM
features.

g Note: WhentheSRVCCdelaytimerisrunningforaUE,andaUEperformsa
handoverorre-establishmentprocedure,theSRVCCdelaytimerwillnotberestartedat
atargetcellaftertheHOorre-establishmentprocedure.

Figure 8 HandlingtheSRVCCdelaytimerduringSRVCC(toWCDMA/GSM)

3.17.3 LTE3290 system impact


LTE3290: SRVCC Trigger Enhancement impact on features, interfaces, network
management tools, and system performance and capacity

Interdependencies between features


ThefollowingfeaturesmustbeactivatedbeforeactivatingtheLTE3290: SRVCC Trigger
Enhancementfeature:
LTE10: EPS Bearers for Conversational Voice
atleastoneofthefollowingfeatures:
LTE872: SRVCC to WCDMA
LTE873: SRVCC to GSM

ThefollowingfeaturesmustbedeactivatedbeforeactivatingtheLTE3290: SRVCC
Trigger Enhancementfeature:
LTE2832: SRVCC Due to Admission Control Rejection

Impact on interfaces
TheLTE3290: SRVCC Trigger Enhancementfeaturehasnoimpactoninterfaces.

DN09237915Issue:01A 2017Nokia 133


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Impact on network management tools


TheLTE3290: SRVCC Trigger Enhancementfeaturehasnoimpactonnetwork
managementtools.

Impact on system performance and capacity


TheLTE3290: SRVCC Trigger Enhancementfeaturehasnoimpactonsystem
performanceorcapacity.

3.17.4 LTE3290 reference data


LTE3290: SRVCC Trigger Enhancement requirements, alarms and faults, commands,
measurements and counters, KPIs, parameters, and sales information

Requirements

Table 73 LTE3290hardwareandsoftwarerequirements
System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 notsupported FL17 FL17 FL17 FL17

Flexi Zone OMS UE NetAct MME SAE GW


Controller
FL17 Supportnot 3GPPR8 Supportnot Supportnot Supportnot
required required required required

Alarms
TherearenoalarmsrelatedtotheLTE3290: SRVCC Trigger Enhancementfeature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE3290: SRVCC Trigger Enhancementfeature.

Commands
TherearenocommandsrelatedtotheLTE3290: SRVCC Trigger Enhancementfeature.

Measurements and counters

Table 74 ExistingcountersrelatedtoLTE3290
Counter Counter name Measurement
ID
M8016C Inter-System Handovers LTEInterSystemHandover
50 preparations to UTRAN with
SRVCC
M8016C Failed Inter-System Handover LTEInterSystemHandover
51 preparations to UTRAN with
SRVCC due to timer
M8016C Failed Inter-System Handover LTEInterSystemHandover
52 preparations to UTRAN with

134 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Table 74 ExistingcountersrelatedtoLTE3290(Cont.)
Counter Counter name Measurement
ID
SRVCC due to target eNB
admission control
M8016C Failed Inter-System Handover LTEInterSystemHandover
53 preparations to UTRAN with
SRVCC caused by other reasons
M8016C Inter-System Handover LTEInterSystemHandover
54 preparations to GERAN with
SRVCC
M8016C Failed Inter-System Handover LTEInterSystemHandover
55 preparations to GERAN with
SRVCC due to timer
M8016C Failed Inter-System Handover LTEInterSystemHandover
56 preparations to GERAN with
SRVCC due to target eNB
admission control
M8016C Failed Inter-System Handover LTEInterSystemHandover
57 preparations to GERAN with
SRVCC caused by other reasons

g Note: Measurementsdiscardedduetoadelaytimerintroducedbythe
LTE3290: SRVCC Trigger EnhancementfeaturedonotincrementcounterM8009C0.

Forcounterdescriptions,seeLTE Performance Measurements and Key Performance


Indicators.

Key performance indicators


TheLTE3290: SRVCC Trigger Enhancementfeaturemayimprovethehandover
preparationsuccessrate,whichisvisibleinthefollowingKPIs:

Table 75 ExistingkeyperformanceindicatorsrelatedtoLTE3290
KPI ID KPI name
LTE_6102a InterRATHOPreparationAttemptstoUTRANwithSRVCC
LTE_6103a InterRATHOPreparationFailureRatiotoUTRANwithSRVCCduetotimerexpiry
LTE_6104a InterRATHOPreparationFailureRatiotoUTRANwithSRVCCduetoadmission
control
LTE_6105a InterRATHOPreparationFailureRatiotoUTRANwithSRVCCduetoother
reasons
LTE_6106a InterRATHOPreparationSuccessRatiotoUTRANwithSRVCC
LTE_6107a InterRATHOPreparationAttemptstoGERANwithSRVCC
LTE_6108a InterRATHOPreparationFailureRatiotoGERANwithSRVCCduetotimerexpiry
LTE_6109a InterRATHOPreparationFailureRatiotoGERANwithSRVCCduetoadmission
control
LTE_6110a InterRATHOPreparationFailureRatiotoGERANwithSRVCCduetoother
reasons

DN09237915Issue:01A 2017Nokia 135


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

Table 75 ExistingkeyperformanceindicatorsrelatedtoLTE3290(Cont.)
KPI ID KPI name
LTE_6111a InterRATHOPreparationSuccessRatiotoGERANwithSRVCC
LTE_6115a E-UTRANTotalInterRATHOUTRANwithSRVCCSuccessRatio
LTE_6116a E-UTRANTotalInterRATHOGERANwithSRVCCSuccessRatio

ForKPIdescriptions,seeLTE Performance Measurements and Key Performance


Indicators.

Parameters

Table 76 NewparametersintroducedbyLTE3290
Full name Abbreviated name Managed Parent structure
object
SRVCC delay timer srvccDelayTimer MRBTS/L
NBTS

Table 77 ExistingparametersrelatedtoLTE3290
Full name Abbreviated name Managed Parent structure
object
Activate AC triggered actAcSrvcc MRBTS/L
SRVCC NBTS

Forparameterdescriptions,seeFDD-LTE BTS Parameters.

Sales information

Table 78 LTE3290salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense No

3.17.5 Activating and configuring LTE3290


The SRVCC procedure is prevented from being rejected during the initial phase of
VoLTE establishment after activating the LTE3290: SRVCC Trigger Enhancement
feature.

Before you start


Procedurenotifications
Activationproceduredoesnotimpactongoingsingleradiovoicecallcontinuity
(SRVCC)procedures.OnlythefirstQCI1setupstartstheSRVCCdelaytimer;
modificationoftimervaluedoesnotimpacttheSRVCCtimerwhenitisalready
running.
Activationproceduredoesnotcausedowntime,andthefeaturecanbeactivated
atanytimeoftheday.

136 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Featureinterdependencies
ThefollowingfeaturesmustbeactivatedbeforeactivatingtheLTE3290: SRVCC
Trigger Enhancementfeature:
LTE10: EPS Bearers for Conversational Voice
atleastoneofthefollowingfeatures:
LTE872: SRVCC to WCDMA
LTE873: SRVCC to GSM

Preconfiguration
TheLTE2832: SRVCC Due to Admission Control Rejectionfeatureisdisabled
(theActivate AC triggered SRVCC (actAcSrvcc)parameterissetto
false).
TheSRVCC delay timer (srvccDelayTimer)valueissetto0.
IftheLTE3290: SRVCC Trigger EnhancementfeaturemaysupporttheSRVCC
toWCDMA,thentheLTE872: SRVCC to WCDMAactivatingparametershaveto
beconfigured(settotrue):
Activate SRVCC to WCDMA (actSrvccToWcdma)
Activate handover from LTE to WCDMA (actHOtoWcdma)
Activate support of conversational voice bearer
(actConvVoice)
OtherLTE872-relatedmandatoryparametershavetobeconfiguredasdescribed
intheLTE872:SRVCCtoWCDMA.
IftheLTE3290: SRVCC Trigger EnhancementfeaturemaysupporttheSRVCC
toGSM,thentheLTE873: SRVCC to GSMactivatingparametershavetobe
configured(settotrue):
Activate SRVCC to GSM (actSrvccToGsm)
Activate support of conversational voice bearer
(actConvVoice)
OtherLTE873-relatedmandatoryparametershavetobeconfiguredasdescribed
intheLTE873:SRVCCtoGSM.

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

DN09237915Issue:01A 2017Nokia 137


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

5 Set SRVCC delay timer (srvccDelayTimer) to a value different than 0.


Settingthetimerparametertoavaluedifferentthan0activatestheLTE3290feature
anddefinesthetimeperiodduringwhichtheSRVCCB2measurementsare
discardedbytheeNBafterQCI1bearerestablishment.TheSRVCC delay timer
(srvccDelayTimer)valuerangeisfrom0to20secondswithastepof0.5s.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

c) Click Send Parameters.

Result

TheLTE3290featureisactivated,andtheeNBisreadytodiscardtheB2measurements
duringthetimer-definedperiod(aftertheestablishmentofthefirstQCI1E-RAB).

3.17.6 Deactivating LTE3290


The SRVCC procedure is no longer prevented from rejection after deactivating the
LTE3290: SRVCC Trigger Enhancement feature.

Before you start


Procedurenotifications

138 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Deactivationproceduredoesnotcausedowntime,andthefeaturecanbe
deactivatedatanytimeoftheday.

Preconfiguration
TheSRVCC delay timer (srvccDelayTimer)valueisdifferentthan0.

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

5 Set SRVCC delay timer (srvccDelayTimer) to 0.


ChangingSRVCC delay timer (srvccDelayTimer)to0doesnotstopthe
ongoingtimer.ModificationofSRVCC delay timer (srvccDelayTimer)'s
valueisvalidonthenexttimerexpiry.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.

DN09237915Issue:01A 2017Nokia 139


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

IftheBTShasbeenalreadycommissioned,selectOnly changes.

c) Click Send Parameters.

Result

TheSRVCCdelaytimeristurnedoff(aftertheongoingtimerexpires)andnolonger
preventstheSRVCCprocedurefrombeingrejected.

3.18 LTE3439: Additional Carrier Aggregation Band


Combinations 4CC I
TheLTE3439: Additional Carrier Aggregation Band Combinations 4CC Ifeature
supportsadditionaldownlink(DL)carrieraggregation(CA)bandcombinationsforfour
componentcarriers(CCs).

3.18.1 LTE3439 benefits


TheLTE3439: Additional Carrier Aggregation Band Combinations 4CC Ifeature
providesnewbandcombinationsthatsupporthigherdownlinkpeakratesinareaswith
overlappingcelldeploymentswhencarrieraggregationisenabled;thisoffershigherdata
peakratesfortheuserswithinthenetwork.

3.18.2 LTE3439 functional description


WhentheLTE3439: Additional Carrier Aggregation Band Combinations 4CC Ifeature
isenabled,theeNBsupportsthefollowingadditionalcarrieraggregation(CA)band
combinations:
CAbandcombinationswithtwobands:
Band2+Band2+Band4+Band4(band2andband4non-contiguous)
Band2+Band2+Band66+Band66(band2non-contiguous,band66non-
contiguous,band66contiguousforbandwidthclassBandC)
Band2+Band2+Band66+Band66(band2contiguous;band66non-contiguous,
contiguousforbandwidthclassBandC)
Band3+Band3+Band7+Band7(band3non-contiguous;band7non-
contiguous,bandwidthcombinationset0,1)

CAbandcombinationswiththreebands:

Band1+Band3+Band3+Band5(band3contiguous)
Band1+Band3+Band7+Band7(band7non-contiguous)
Band1+Band3+Band3+Band8(band3contiguous)
Band1+Band5+Band7+Band7(band7non-contiguous,contiguous)

140 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofradioresourcemanagementand
telecomfeatures

Band2+Band2+Band4+Band12(band2andband4non-contiguous)
Band2+Band4+Band7+Band7(band7non-contiguous)
Band2+Band4+Band4+Band12(band4non-contiguous)
Band2+Band2+Band5+Band30(band2non-contiguous)
Band2+Band5+Band5+Band30(band5contiguous)
Band2+Band2+Band5+Band66(band2non-contiguous)
Band2+Band2+Band12+Band30(band2non-contiguous)
Band2+Band12+Band66+Band66(band66non-contiguous,contiguousfor
bandwidthclassBandC)
Band2+Band2+Band12+Band66(band2non-contiguous,contiguous)
Band2+Band2+Band29+Band30(band2non-contiguous)
Band3+Band5+Band7+Band7(band7non-contiguous,contiguous)
Band3+Band3+Band7+Band8(band3non-contiguous,bandwidthcombination
set0,1)
Band3+Band7+Band7+Band8(band7non-contiguous,bandwidthcombination
set0,1)
Band3+Band3+Band7+Band20(band3contiguous)
Band3+Band3+Band7+Band32(band3contiguous)

CAbandcombinationswithfourbands:

Band1+Band3+Band5+Band7
Band1+Band3+Band7+Band8
Band1+Band3+Band7+Band20
Band1+Band3+Band7+Band28
Band2+Band5+Band30+Band66
Band2+Band12+Band30+Band66

g Note: Thebandwidthcombinationsetequals0accordingto3GPPTS36.101.,ifnot
mentionedotherwise.

3.18.3 LTE3439 system impact


Interdependencies between features
TheLTE3439: Additional Carrier Aggregation Band Combinations 4CC Ifeatureis
activatedtogetherwiththeLTE2531: FDD Downlink Carrier Aggregation 4CCfeature.

Impact on interfaces
TheLTE3439: Additional Carrier Aggregation Band Combinations 4CC Ifeaturehasno
impactoninterfaces.

Impact on network management tools


TheLTE3439: Additional Carrier Aggregation Band Combinations 4CC Ifeaturehasno
impactonnetworkmanagementtools.

Impact on system performance and capacity


TheLTE3439: Additional Carrier Aggregation Band Combinations 4CC Ifeaturehasno
impactonsystemperformanceorcapacity.

DN09237915Issue:01A 2017Nokia 141


Descriptionsofradioresourcemanagementand FDD-LTE17,FeatureDescriptionsandInstructions
telecomfeatures

3.18.4 LTE3439 reference data


Requirements

Table 79 LTE3439hardwareandsoftwarerequirements
System Flexi Flexi AirScale BTS Flexi Zone Flexi Zone
release Multiradio Multiradio 10 Micro BTS Access Point
BTS BTS
FDD-LTE17 Notsupported FL17 FL17 Notsupported Notsupported

Flexi Zone OMS UE NetAct MME SAE GW


Controller
Notsupported Supportnot 3GPPR12UE - - -
required capabilities
3GPPR13UE
capabilities

Alarms
TherearenoalarmsrelatedtotheLTE3439: Additional Carrier Aggregation Band
Combinations 4CC Ifeature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE3439: Additional Carrier Aggregation Band
Combinations 4CC Ifeature.

Commands
TherearenocommandsrelatedtotheLTE3439: Additional Carrier Aggregation Band
Combinations 4CC Ifeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE3439: Additional Carrier
Aggregation Band Combinations 4CC Ifeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3439: Additional Carrier
Aggregation Band Combinations 4CC Ifeature.

Parameters
TherearenoparametersrelatedtotheLTE3439: Additional Carrier Aggregation Band
Combinations 4CC Ifeature.

Sales information

Table 80 LTE3439salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) Poollicense No

142 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsoftransportandtransmissionfeatures

4 Descriptions of transport and transmission


features

4.1 LTE2807: IPv6 Support for M1 and M3 Interfaces


TheLTE2807: IPv6 Support for M1 and M3 Interfacesfeatureextendstheevolved
multimediabroadcast/multicastservice(eMBMS)(LTE1117: LTE MBMS)byaddingthe
IPv6supportforM3andM1interfaces.
M3isacontrolplaneinterfacebetweenMMEandeNB.ThemainfunctionoftheM3
interfaceissessionmanagement(MBMSsessionsstart/stop/update).
M1isauserplaneinterfacebetweentheMBMS-GWandtheeNBusedforMBMSdata
delivery.

4.1.1 LTE2807 benefits


TheLTE2807: IPv6 Support for M1 and M3 InterfacesfeatureenableseMBMSservices
overtheoperator'sIPv6transportnetwork.TheoperatorcanusetheexistingIPv6
transportnetworkwithitsgreateraddresscapacity.

4.1.2 LTE2807 functional description


IPv6

IPv6isanextensionoftheaddressroomofIPv4(factor7.9*1028).TheIPv6addresses
are128bitslong.Theyaregiveninthehexadecimalformat(eightblockswith16bits
each),forexample,2001:db58:85a3:08d3:1319:8a2e:0370:7344.

eMBMS
eMBMSisMBMSforLTE.ItisintroducedwiththeLTE1117: LTE MBMSfeature.
Multimediabroadcast/multicastservices(MBMS)arepoint-to-multipointservices,which
aredesignedtoprovideefficientdeliveryofbroadcastandmulticastservicesboth
withinacellandinthecorenetwork.
Targetapplicationsincludemobileandradiobroadcasting,livestreamingvideoservices,
aswellasfiledeliveryandemergencyalerts.

DN09237915Issue:01A 2017Nokia 143


Descriptionsoftransportandtransmissionfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Figure 9 OverviewM1/M3interface

Contents
Provider

PDN BMSC
Gateway
SGmb SGi-mb

Sm

MME MBMS
M3 GW

M3 M1 M1

MCE MCE

MCE MCE
eNB eNB

Table 81 Explanations:OverviewoftheM1/M3interface
Abbreviation Long text function
BMSC Broadcast/multicastservice eMBMSuserservice
center provisioninganddelivery
eMBMSbearerservice
authorizationandinitiating
eMBMStransmission
schedulinganddelivery
Entrypointforcontent
providers'transmissions

144 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsoftransportandtransmissionfeatures

Table 81 Explanations:OverviewoftheM1/M3interface(Cont.)
Abbreviation Long text function
MBMSGW Multimediabroadcast/multicast eMBMSpacketdeliveryto
servicesgateway eNBs
eMBMSsessioncontrol
towardsLTE

MCE Multicell/multicastcoordination eMBMSadmissioncontrol


entity eMBMSradioresources
allocations

Sm MBMSGW-MME(control eMBMSsessioncontrol
planeinterfaces) (sessionstart/stop/update)
eMBMSservicearea
control

SGmb BMSC-MBMSGW(control eMBMSsessioncontrol


planeinterfaces) (sessionstart/stop/update)
eMBMSservicearea
control

SGi-mb BMSC-MBMSGW point-to-pointdatadelivery

M3 interface: MME eNB


TheLTE2807: IPv6 Support for M1 and M3 InterfacesfeatureextendstheeNBto
supportM3overIPv6.
StreamControlTransmissionProtocol(SCTP)ontopoftheIPlayerisusedasthe
signalingmethod.ThemainfunctionoftheM3applicationprotocolisthecontrol
signalingoftheMBMSsession(forexample,MBMSsessionstartandstop).
TheM3controlplaneinterfaceisterminatedatthelogicalMBMScoordinatingentity
(MCE)withintheeNB.
ThemainMBMSfeature,LTE1117: LTE MBMS,requiresthattheS1C-planeIPv4
addressesareidenticalwiththeM3IPv4addresses.ThisisalsovalidfortheLTE2807:
IPv6 Support for M1 and M3 Interfacesfeature,usingM3IPv6addresses.

DN09237915Issue:01A 2017Nokia 145


Descriptionsoftransportandtransmissionfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Figure 10 M3interface

M3AP

SCTP

IP

Datalinklayer)

Physicallayer

M1 interface: MBMS GW eNB


Thenetworkelement(NE)supportstheeMBMSM1interfacetransportinIPv6multicast.
ThestatusoftheLTE2807feature'sactivationflagstatusdetermineswhethertheM1
interfacecanworkinIPv6.
TheM1interfaceisterminatedattheeNB.

Figure 11 M1interface

U-PlanePDUs

SYNC

GTP-U

UDP

IP(multicast)

Datalinklayer

Physicallayer

146 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsoftransportandtransmissionfeatures

4.1.3 LTE2807 system impact


LTE2807: IPv6 Support for M1 and M3 Interfaces impact on features, interfaces, network
management tools, and system performance and capacity

Interdependencies between features


TheLTE2807: IPv6 Support for M1 and M3 Interfacesfeatureinteractswiththefollowing
features:
LTE3201: eMBMS in RAN Sharing Deployment
TheLTE1117: LTE MBMSfeaturesupportsonlyoneM1andoneM3link.The
LTE3201: eMBMS in RAN Sharing DeploymentfeatureintroducesmultipleM3and
M1links.
LTE1117: LTE MBMS
TheLTE2807: IPv6 Support for M1 and M3 Interfacesfeatureisbasedonthe
LTE1117: LTE MBMS feature.
LTE2299: Dual Stack IPv4/ IPv6 for S1/X2
TheLTE2299: Dual Stack IPv4/ IPv6 for S1/X2 featureisasuccessorandan
extensionofLTE125(IPv6forU/C-plane).ThisfeatureintroducedIPv4/v6dualstack
functionalityforS1/X2transportinxL16.TheLTE2299C-planepartisbeingreused
andextendedfortheLTE2807 M3.

Impact on interfaces
TheLTE2807: IPv6 Support for M1 and M3 Interfacesfeatureimpactsinterfacesas
follows:
M3interface
IPv6support

M1interface
IntroductionofIPv6multicasting

Impact on network management tools


TheLTE2807: IPv6 Support for M1 and M3 Interfacesfeaturehasnoimpactonnetwork
managementtools.

Impact on system performance and capacity


TheLTE2807: IPv6 Support for M1 and M3 Interfacesfeaturehasnoimpactonsystem
performanceorcapacity.

4.1.4 LTE2807 reference data


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

Requirements

DN09237915Issue:01A 2017Nokia 147


Descriptionsoftransportandtransmissionfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Table 82 LTE2807hardwareandsoftwarerequirements
System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 Airscale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 notapplicable notapplicable FL17 notapplicable notapplicable

Flexi Zone OMS UE NetAct MME SAE GW


Controller
notapplicable notapplicable notapplicable notapplicable notapplicable notapplicable

Alarms

Table 83 ExistingalarmsrelatedtoLTE2807
Alarm ID Alarm name
7604 BTS OPERATION DEGRADED
7657 BASE STATION CONNECTIVITY DEGRADED

BTS faults and reported alarms

Table 84 BTSfaultsintroducedbyLTE2807
Fault Fault name Reported alarms
ID
Alarm Alarm name
ID
6850 M3 interface recovery 7657 BTS CONNECTIVITY DEGRADED
failure
6851 M3 interface setup failure 7657 BTS CONNECTIVITY DEGRADED

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE2807: IPv6 Support for M1
and M3 Interfacesfeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE2807: IPv6 Support for M1
and M3 Interfacesfeature.

Parameters

Table 85 NewparametersintroducedbyLTE2807
Full name Abbreviated name Managed Parent structure
object
Activate IPv6 MBMS M1 actIPv6MBMS LNBTS
Interface Support

148 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsoftransportandtransmissionfeatures

Table 86 ExistingparametersrelatedtoLTE2807
Full name Abbreviated name Managed Parent structure
object
M3 Primary Access m3ipAddrPrim LNM3
M3 Secondary IPv4 m3ipAddrSec LNM3
address

Sales information

Table 87 LTE2807salesinformation
Product structure class License control Activated by default
Applicationsoftware(ASW) SoftwareAssetMonitoring No

4.1.5 Activating and configuring LTE2807


Before you start
Featureinterdependencies
TheLTE2807: IPv6 Support for M1 and M3 Interfacesfeatureinteractswiththe
followingfeatures:
LTE3201: eMBMS in RAN Sharing Deployment
TheLTE1117: LTE MBMSfeaturesupportsonlyoneM1andoneM3link.The
LTE3201: eMBMS in RAN Sharing DeploymentfeatureintroducesmultipleM3
andM1links.
LTE1117: LTE MBMS
TheLTE2807: IPv6 Support for M1 and M3 Interfacesfeatureisbasedonthe
LTE1117: LTE MBMS feature.
LTE2299: Dual Stack IPv4/ IPv6 for S1/X2
TheLTE2299: Dual Stack IPv4/ IPv6 for S1/X2 featureisasuccessorandan
extensionofLTE125(IPv6forU/C-plane).ThisfeatureintroducedIPv4/v6dual
stackfunctionalityforS1/X2transportinxL16.TheLTE2299C-planepartis
beingreusedandextendedfortheLTE2807 M3.

Preconfiguration
TheLTE1117: LTE MBMS featureisactivated(actMBMS=true).
TheLTE2299: Dual Stack IPv4 / IPv6featureisenabledforIPv6support
(actIpv6=true)
TheLTE2807featureusesthesameIPv6licenceasLTE2299: Dual Stack IPv4/
IPv6 for S1/X2

Procedure

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

DN09237915Issue:01A 2017Nokia 149


Descriptionsoftransportandtransmissionfeatures FDD-LTE17,FeatureDescriptionsandInstructions

2 Start commissioning.
Sub-steps

a) Select View Commissioning or click Commissioning on the View Bar on


the left.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

5 Set the actIPv6MBMS value to true.


actIPv6MBMSisonlyallowedtobesettotrueforAirScaleeNBs.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

IftheBTShasnotbeencommissioned,selectAll parameters.
IftheBTShasbeenalreadycommissioned,selectOnly changes.

c) Click Send Parameters.

Result

Thefeatureisactivatedandanyparametersettingsarepermanentlystored.
OnlyIPv6addresseswillbeallowedtobeconfiguredontheM1interface.
NetActandBTSSiteManagerarenotifiedaboutthechangedconfiguration.

150 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsoftransportandtransmissionfeatures

4.1.6 Deactivating LTE2807


Before you start
Preconfiguration

TheLTE1117: LTE MBMS featureisactivated.TheLNBTSparameteractMBMS=


true.
TheLTE2807featureusesthesameIPv6licenceasLTE2299: Dual Stack IPv4/ IPv6
for S1/X2
OneormoreIPv6MBMSmulticastsessionsareactive.

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.
TheBTS Sitecheckbox,locatedintheTargetsection,isselectedbydefault.
Thisistherecommendedsetting.

b) Use the Template, Manual, or Reconfiguration option, depending on the


actual state of the BTS.

3 Proceed to the Radio Network Configuration page.

4 Go to the LNBTS object.


Objectpath:MRBTSLNBTS

DN09237915Issue:01A 2017Nokia 151


Descriptionsoftransportandtransmissionfeatures FDD-LTE17,FeatureDescriptionsandInstructions

5 Set the actIPv6MBMS value to false.

6 Send the commissioning plan file to the BTS.


Sub-steps

a) Go to the Send Parameters page.

b) Select an appropriate Send option.

AstheBTShasbeenalreadycommissioned,selectOnly changes.

c) Click Send Parameters.

Result

Thefeatureisdeactivatedandanyparametersettingsarepermanentlystored.
OnlyIPv4multicastaddresseswillbeallowedtobeconfiguredonM1interface.
NetActandBTSSiteManagerarenotifiedaboutthechangedconfiguration.

4.2 LTE2855: Fronthaul Active WDM


TheLTE2855: Fronthaul Active WDMfeatureintroducesnewcomponentsfor
multiplexing/de-multiplexingofCPRI/OBSAIlinksbetweenbasebandunits(BBUs)and
RRHs/RFMs.
Itsupportsproveninteroperabilityandperformance,usingactiveWDMcomponentswith
NokiaFlexiSystemModulesrelease3orhigherandallremoteradiohead/radio
frequencymodules(RRHs/RFMs).

4.2.1 LTE2855 benefits


TheLTE2855: Fronthaul Active WDMfeatureprovidescostreductioninvolvedin
deployingmultiplefiberoptics,therebyutilizingtheopticalfibersmoreefficiently.

4.2.2 LTE2855 functional description


LTE2855 functional description
TheLTE2855: Fronthaul Active WDMfeaturesupportsthefollowingcharacteristics:

Thesolutionsupportsmultiplexingandde-multiplexingofCPRI/OBSAIlinksbetween
FlexiSystemModulerelease3orhigherandRFM/RRH.

152 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsoftransportandtransmissionfeatures

TheactiveWDMcomponentsincludeapassiveWDMfilterwithactivemanagement
andanSFPcolorconversionunit.
TheSFPcolorconversionunitallowsdeployingRRH/RFMwithopticalgreySFPs.It
convertsgreytocoloredsignalsandviceversa.
SeparatevariantsofactiveWDMMuxunitsforindoorandoutdoordeploymentsare
provided.
ThemaximumsupporteddistancebetweenasystemmoduleandRFMs/RRHsis20
km.
Thesolutionsupports:
chainandstartopologies.
DCandACasinputstoanactiveWDMunit.
linkratesuptoCPRIrate7.
networkmanagementfunctionalitythatenablescontinuousmonitoringofE2E
network`shealth.

TheactiveWDMnetworkmanagementfunctionalityenablesthefollowinginformationto
bedisplayed:ingress/egressopticallevels,fibercuts.Inadditiontothenetwork
monitoringfunctionality,thesolutionsupportsexternalalarminputsandoutputs.This
functionalitymonitorscustomer-definedinputs,providinginventoryandalarmmonitoring,
whileatthesametimesupportingoutputstoexternaldevicessuchasgenerators,
coolingsystems,videosurveillance,andsoontobeturnedon/off.Customersareableto
remotelymonitorthealarmsattheremotesitesfromhumlocationsviatheoptical
supervisoryfunctionality.
TheNetworkmanagementsystem(NMS)connectivityaswellasthealarmsare
transportedviaanindependentOpticalsupervisorychannel(OSC),enablinglocaland
remotemanagement.ThissolutionalsoenablesFiberbreakmonitoringforthe
respectivelink.
AnoverviewofthefunctionalityisprovidedinFigure12:FronthaulActiveWDM
components.

DN09237915Issue:01A 2017Nokia 153


Descriptionsoftransportandtransmissionfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Figure 12 FronthaulActiveWDMcomponents

Outdoorhardenedactive
SFP
WDMMux(TLU/PMU/SSM) SFP

RRHwith
B&WSFP NMS
SFP

RRHwith
B&WSFPs Fronthaul
fiber SystemModules

SFP

SFP

SFP

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

4.2.3 LTE2855 system impact


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

4.2.4 LTE2855 reference data


LTE2855: Fronthaul Active WDM requirements, alarms and faults, commands,
measurements and counters, KPIs, parameters, and sales information.

Requirements

Table 88 LTE2855hardwareandsoftwarerequirements
System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 notsupported FL17 FL17 notsupported notsupported

Flexi Zone OMS UE NetAct MME SAE GW


Controller
notsupported supportnot supportnot supportnot supportnot supportnot
required required required required required

TheLTE2855: Fronthaul Active WDMfeaturerequiresthefollowingWDMcomponents:

1830VWMTLU:TranslatorLineUnit
1830VWMOSU:OpticalSupervisoryUnit
1830VWMPMU:PhotonicManagedUnit

154 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsoftransportandtransmissionfeatures

5620SAM:ServiceAggregationManager(Networkmanagementsystem)orNetAct
SSM:SiteMonitoringModule(optional)

AllthisHWcomponentsaredescribedinseparatedescriptionsinNOLS
(https://online.networks.nokia.com/entry/open/DoUp?action=login&TYPE=33554433&RE
ALMOID=06-00016567-e062-1083-acba-8).

Alarms
AlarmsareprovidedviatheNMSandNetAct.MoredetailsaredescribedintheProduct
manual.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE2855: Fronthaul Active WDMfeature.

Commands
TherearenocommandsrelatedtotheLTE2855: Fronthaul Active WDMfeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE2855: Fronthaul Active WDM
feature.

Key performance indicators


TheNMSaswellastheNetActsystemprovideKPI`s.

Parameters
TherearenoparametersrelatedtotheLTE2855: Fronthaul Active WDMfeature.

Sales information

Table 89 LTE2855salesinformation
Product structure class License control Activated by default
BasicSoftware(BSW) - Yes

DN09237915Issue:01A 2017Nokia 155


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

5 Descriptions of operability features

5.1 LTE684: DHCP Server for Flexi LTE BTS Site


Devices
TheLTE684: DHCP Server for Flexi LTE BTS Site Devicesfeatureintroducesaninternal
dynamichostconfigurationprotocol(DHCP)serverforFlexiMultiradioBTSsitedevices.
DynamicHostConfigurationProtocol(DHCP)isusedtoautomaticallyprovideIP
configurationparameterstotheequipmentorhostsconnectedtothelocalmanagement
portoftheFlexiMultiradioBTS.BTSSiteManagerallowstheconfigurationofDHCP
parametersfortheBTS.

5.1.1 LTE684 benefits


TheLTE684: DHCP Server for Flexi LTE BTS Site Devicesfeatureenables:
AddinganewDHCPconfiguration
ModifyinganexistingDHCPconfiguration
DeletingaDHCPconfiguration

5.1.2 LTE684 functional description


Functional Overview
DynamicHostConfigurationProtocol(DHCP)isusedtoautomaticallyprovideIP
configurationparameterstotheequipmentorhostsconnectedtothesitesupport
equipment(SSE)oftheBTS.BTSSiteManagerallowstheconfigurationofDHCP
parametersfortheBTS.TheSSEcanbeconnectedtothelocalport(orports)ofthe
system/controlmodules.

g Note: DependingontheHWvariant,theportcanbeadedicatedportforSSEoralocal
maintenanceport.

ThepublicIPaddressofthetransmissionsub-modulemustbeconfiguredbeforesetting
theDHCPconfigurations.AllDHCPIPaddressesmustbeinthesamesubnetasthe
publicIPaddressofthetransmissionsub-module.
TheSSEIPaddressesmaybeconfiguredmanuallyorprovidedthroughDHCP.The
internalDHCPserverfortheBTSsitedevicesenablesadynamicIPhostconfiguration
forIPdevicesconnectedtoasystem/controlmoduleBTSsubnetattheBTSsite.
TheplannedIPaddressesoftheSSEcanbeconfiguredintheDHCPserver.TheBTS
transportsupportsanIPsubnetforSSEandroutingbetweenthissubnetandthe
backhaulinterface.
ThesitelocaldevicesreceiveanIPconfigurationfromtheDHCPserverlocatedinthe
system/controlmodule.AlongwiththeIPaddress,othernetworkparametersmayalso
beprovidedtothehost.Theparametersare,forexample:
DefaultgatewayIPaddress

156 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

Leasetime
Subnetmask

TheDHCPserverisconfiguredaspartofthetransportconfiguration.

5.1.3 LTE684 system impact


Interdependencies between features
TheLTE684: DHCP Server for Flexi LTE BTS Site Devicesfeatureisimpactedbythe
followingfeatures:
LTE746: IP-based Filtering for BTS SSE
TheLTE746IPfilteringruletakescaretopassSSEpacketsthrough.
LTE871: Transport Support for Site Support Equipment
LTE871allowstheBTSsubnettobeconfiguredonBTSSM,andtheDHCPserverto
assignanIPaddresstotheSSEclientfromthisBTSsubnet.

Impact on interfaces
TheLTE684: DHCP Server for Flexi LTE BTS Site Devicesfeaturehasnoimpacton
interfaces.

Impact on network management tools


TheLTE684: DHCP Server for Flexi LTE BTS Site Devicesfeaturehasnoimpacton
networkmanagementtools.

Impact on system performance and capacity


TheLTE684: DHCP Server for Flexi LTE BTS Site Devicesfeaturehasnoimpacton
systemperformanceorcapacity.

5.1.4 LTE684 reference data


Requirements

Table 90 LTE684hardwareandsoftwarerequirements
System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
RL10 LBTS1.0 LBTS4.0 FL16S4 notsupported notsupported

Flexi Zone OMS UE NetAct MME SAE GW


Controller
notsupported notapplicable notapplicable notapplicable notapplicable notappilcable

Alarms
TherearenoalarmsrelatedtotheLTE684: DHCP Server for Flexi LTE BTS Site Devices
feature.

BTS faults and reported alarms

DN09237915Issue:01A 2017Nokia 157


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

TherearenofaultsrelatedtotheLTE684: DHCP Server for Flexi LTE BTS Site Devices


feature.

Commands
TherearenocommandsrelatedtotheLTE684: DHCP Server for Flexi LTE BTS Site
Devicesfeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE684: DHCP Server for Flexi
LTE BTS Site Devicesfeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE684: DHCP Server for Flexi
LTE BTS Site Devicesfeature.

Parameters

Table 91 NewparametersintroducedbyLTE684
Full name Abbreviated name Managed Parent structure
object
DHCP Hardware dhcpHardwareident IHCP -
Identifier ifier
Entry set for DHCP client_identifier IHCP -
clients identified by a
system name
DHCP Fixed IP Address dhcpFixedIpAddres IHCP -
s
DHCP Range Start IP dhcpRangeStart IHCP -
Address
DHCP Range End IP dhcpRangeEnd IHCP -
Address

Sales information

Table 92 LTE684salesinformation
Product structure class License control Activated by default
BasicSoftware(BSW) - Yes

5.1.5 Other instructions

Example: Inspecting and modifying DHCP configurations in BTS Site Manager


Purpose
DynamicHostConfigurationProtocol(DHCP)isusedtoautomaticallyprovideIP
configurationparameterstotheequipmentorhostsconnectedtothelocalmanagement
portoftheBTS.BTSSiteManagerallowstheconfigurationofDHCPparametersforthe
FlexiMultiradioBTS.

158 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

Precondition
ThepublicIPaddressofthetransmissionsub-modulemustbeconfiguredbeforesetting
theDHCPconfigurations.AllDHCPIPaddressesmustbeinthesamesubnetasthe
publicIPaddressofthetransmissionsub-module.

Procedure

1 Inspect the DHCP configurations.


Click ConfigurationTRSIP ....
TheIPAddresseswindowopens.

Figure 13 PathDHCPServer

DN09237915Issue:01A 2017Nokia 159


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Figure 14 DHCPconfigurations

ThefollowingDHCPconfigurationsaredisplayedintheIPAddresseswindow:
ExternalequipmentIPaddressesviaDHCP
DHCPclientaddressrange
OtherIPaddressesviaDHCP(clientIDandHWID)

2 Add a new DHCP configuration.

ToaddanexternalequipmentIPaddressviatheDHCP,selectthecheckbox
nexttotheexternalequipmentandmodifytheIPaddressinthefield(optional).
Clicksendtosavethechanges.
ToaddaDHCPclientaddressrange,selectthecheckboxfortheDHCPclient
addressrangeandmodifytheIPaddressoftherange(optional).Clicksendto
savethechanges.
ToaddanotherIPaddressviatheDHCP,selectthetypefield(clientIDorHW
ID)andentertheclientIDnameorHWaddressintheIDfield.SpecifytheIP
addressundertheIPaddresscolumn.Clicksendtosavethechanges.

160 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

ConfigurationoftheexternalequipmentIPaddressviathetheDHCPrequiresaBTS
reset.

3 Modify an existing DHCP configuration.

ExternalequipmentIPaddressviaDHCPsettings:youcanmodifytheIP
addressofthecorrespondingexternalequipment.
DHCPclientaddressrange:youcanmodifytheIPaddressrange.
OtherIPaddressesviaDHCP:youcanmodifytheType,ID,orIPaddressfields.

Clicksendtosavethechanges.

4 Delete a DHCP configuration.


IfyouneedtodeleteaDHCPconfiguration,dothefollowing:
TodeleteanexternalequipmentIPaddressviaDHCP,clearthecheckboxfor
theexternalequipment.
TodeletetheDHCPclientaddressrange,clearthecheckboxforDHCPclient
addressrange.
TodeletetheDHCPconfiguration,clearthecheckboxnexttotheIPaddress
columninthelowerpartofthetab.
Clicksendtosavethechanges.

5.2 LTE3134: FDD-LTE 17 System Upgrade


Benefits, functionality, system impact and reference data of the feature

TheLTE3134: FDD-LTE 17 System Upgradefeaturesupportsasystemupgradeforthe


followingreleases:
FromFDD-LTE16toFDD-LTE17
FromFDD-LTE16AtoFDD-LTE17

AsystemupgradefromFDD-LTE16releaseorFDD-LTE16AreleasetoFDD-LTE17
releaseforFlexiZone(FZ)stand-aloneoutdoorandindoorsmallcellsandcontroller
configurationisalsosupported.
ForAirScale,anupgradefromLTE16AtoLTE17issupported.

5.2.1 LTE3134 benefits


TheLTE3134: FDD-LTE 17 System Upgradefeatureprovidestheoptiontoupgradethe
systeminasinglestep.

DN09237915Issue:01A 2017Nokia 161


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

5.2.2 LTE3134 functional description


Thesystemupgradeispossibleinonestep,andaninstallationofintermediatesoftware
versionisnotneeded.TheLTE3134: FDD-LTE 17 System Upgradefeatureincludes
backwardcompatibilityandenablesanautomaticfallbackorrollbacktotheprevious
releasethathadbeenactivatedbeforetheupgrade.Thefollowingnetworkelements
(NEs)areimpacted:
FlexiMultiradioBTS
FlexiZone(FZ)
NetActincludingtheOptimizer,TraceViewer,andNorthboundinterfaces
Operationandmanagementserver(OMS)
Traffica
Layer3DataCollector(L3DC)withitsapplicationsaslayer3dataanalyzer
Self-organizingnetwork(SON)manager

Thesystemupgradeisperformedinatop-downapproach,whichstartswithNetActand
endswhenalltheevolvedNodeBs(eNBs)areupgraded.Duringtheupgrade,the
managementandnetworkelementsshouldmaintaincompatibilitywithother
managementandnetworkelementsthatareintheactivereleaseorintheprevious
releasebeforetheupgrade.

g Note: TheoperatorcanperformtheactivationofthenewsoftwarefromNetActorBTS
SiteManager(BTSSM).TheTrafficaandL3DCsupportlocalsoftwaremanagement.

g Note: TheupgradeofalleNBsinthenetworkmaytakeuptoseveraldaysoreven
weeks,dependingontheupgradeprocedurefollowedbytheoperator.Duringthis
transitionperiodNetActandLTEOMSareabletomanageeNBsoftheformerrelease
(FDD-LTE16inthisscenarion)andthenewone(FDD-LTE17)inparallel.

Software upgrade from FDD-LTE 16 to FDD-LTE 17


Thesystemupgradesupportsthefollowingsoftwareupgrades:
NetAct16.2toNetAct17.2
LOMS16toLOMS17
Traffica16toTraffica17
L3DC16toL3DC17
eNBupgrades:
FL16toFL17
FLF16toFLF17
FLC16toFLC17

Software upgrade from FDD-LTE 16A to FDD-LTE 17


Thesystemupgradesupportsthefollowingsoftwareupgrades:
NetAct16.8toNetAct17.2
LOMS16AtoLOMS17
Traffica16.5toTraffica17

162 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

L3DC16.5toL3DC17
eNBupgrades:
FL16AtoFL17
FLF16AtoFLF17
FLC16AtoFLC17

Backward compatibility
Backwardcompatibilitymeansthatinterworkingbetweentheupgradedandthenon-
upgradednetworkelementsispossibleduringthesystemupgrade.Becauseofthetop-
downapproach,thefollowingbackwardcompatibilitiesaresupported:
NetAct17.2supportstheOMSandeNBwithFDD-LTE16andFDD-LTE16A
releases.
LOMS17supportstheeNBwithFDD-LTE16andFDD-LTE16Areleases.
Traffica17supportstheL3DCandeNBwithFDD-LTE16Arelease.
L3DC17supportstheeNBwithFDD-LTE16andFDD-LTE16Areleases.

g Note: TheLTE16versionofTraffica(16)mustbeupgradedtoTraffica16.5before
upgradingtoTraffica17.

g Note: Allhardwarerelatedoutagesonanetworkelementmustberesolvedbeforethat
networkelementorsubtendingnetworkelement'smanagedbythatnetworkelement
canbeupgraded.Forexample,anyiOMShardwareissuesshouldberesolvedbefore
upgradingthatLTEOMSoranyeNBscurrentlyassignedtothatLTEOMS.

Data migration
Alloperator-configureddataisstoredinthesystem.Configurationdatacreatedinthe
earlierreleaseisautomaticallyconvertedintoanewformatthatisvalidforthenew
releaseduringtheupgrade.Thedataincludesthefollowing:
AllconfigurationdataoftheFlexiMultiradioBTS,OMS,NetAct,L3DC,andTraffica
CustomizedviewintheBTSSMorNetActuser-specifiedaccountsandpasswords
User-specifiedaccountsandpasswords

Thefollowingsystemdatashouldbeuploadedorbackedupbeforetheupgrade:
Networksecurity-relatedsystemdata(suchascertificatesandkeys)
Usersecurity-relateddata(suchasuseraccountsandpasswords)
Performancemeasurement(PM)data

g Note: FailuretobackupthedataoruploadittoNetActmightcausethedatatobelost.

g Note: SoftwarebackuponlyappliestoOMS.Theoperationdoesnotcauseanoutage,
anditrunsinthebackground.

g Note: BTSSMispreparedtohandlefournetworkelements'releases.LTE17BTSSM
mustsupportFSMr2(FDD-LTE15A).

DN09237915Issue:01A 2017Nokia 163


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Ifthereareusedcommandlinesorscripts,theymustbebackwardcompatible,ora
convertermustbeavailableforthesupportedupgradepaths.Thesoftwareconverteris
availableinanonlineorofflinemode.

Software fallback
Softwarefallbackisanautomaticactivationofanearliersoftwareversionthatisactive
beforethesoftwareupgrade.FallbackistriggeredwhentheeNBorOMScannotactivate
itsnewsoftwareversionoruseanewdatabaseconfigurationversion.Afterasuccessful
fallback,thepassivesoftwarebuildisactiveinallthehardwareunits.Allofthe
componentsactivatethestoredconfigurationdatawithoutreversemigratingor
convertingtonewconfigurationdata.

g Note: Incaseofminorfailures,nosoftwarefallbackisinitiated,buttheerror
informationisindicated.Thefailuresareloggedinanon-volatilememoryandincludea
detailedinformationaboutthereasonforthefailure.

g Note: Incaseofaninconsistentfallback,wheretheeNBdoesnotlocallystorethe
completefallbacksoftwareforallthehardwareunits,asoftwaredownloadfromNetAct
isrequested.

g Note: AsoftwarefallbackcausesanNEoutage,anditcausestheBTStoreset.The
outagetimeisapproximatelythesameasrebootduration.

Software rollback
Softwarerollbackisamanuallyinitiatedsoftwarefallback,usingtheBTSSMorNetAct
softwaremanagement(SWM).Theoperatorcantriggersoftwarerollbackwhenkey
servicesarenotsuccessfullyactivatedafterthesoftwareupgrade.Anyconfiguration
updatesdonewiththenewsoftwarearelostassoonassoftwarerollbackistriggered.
Softwarerollbackisonlyguaranteedifthesourcesoftwareversionhasnotbeen
removedoroverwritteninanon-volatilestorage(NVS).Softwarerollbackisdonewith
thesoftwarestoredinthepassivefilesystemandwhennosoftwaredownloadfromthe
serverispartoftheoperation.Ifthepassivesoftwarehasbeenoverwrittenwitha
differentsoftwareversion,arollbacktotheformerreleaseisnotpossible.

g Note: Softwarerollbacktothestoredsoftwareloadrestorestheearlierconfiguration.If
therehasbeenamajornetworkreconfigurationaftertheupgrade,suchas
reconfiguringtheeNBfromIPv4toIPv6orupdatingoperatorcertificates,thennetwork
connectivityissuescanoccuraftertherollback.Reconfigurationsafterthesoftware
upgrademustbeevaluatedbeforetriggeringsoftwarerollbacktoavoidserviceoutage.

SoftwarerollbackforasingleeNBorforeNBsinbulkcanbedoneusingtheNetAct
SWM.Formoreinformation,seetheSoftware Manager HelpdocumentunderNetwork
AdministrationinNetActOperatingDocumentation.SoftwarerollbackforasingleeNB
canalsobedoneusingtheRollback to Passive SWfunctionintheUpdate SW to BTS
SitewindowontheBTSSM.
Iftheoperatorselectsasoftwareversionthatisolderthanthecurrentsoftwareversionin
theUpdate SW to BTS SitewindowontheBTSSMandclicksUpdate,asoftware
downgradetakesplace.

g Note: Softwaredowngrademustnotbeexecuted.Adowngradetoanearliersoftware
versionisnotguaranteedandmightendupinanuncommissionedstateoftheeNB.

164 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

g Note: AsoftwarerollbackoperationfromNetActmightinterruptongoinglocal
operationstriggeredfromBTSSMsuchascommissioningwithoutalocaluserwarning.

g Note: AsoftwarerollbackcausesanNEoutage,anditcausestheBTStoreset.The
outagetimeisapproximatelythesameasrebootduration.

5.2.3 LTE3134 system impact


LTE3134: FDD-LTE 17 System Upgrade impact on features, interfaces, network
management tools, and system performance and capacity

Interdependencies between features


AsspecifiedinLTE2378: FSM D/E (FSMr2) Support after FDD-LTE 15Afeature,the
FSMr2softwareisfrozenonFDD-LTE15A.TheLTE-FDD17softwarepackagesmay
containFDD-LTE15AupdatesforFSMr2,buttheFSMr2willreportitssoftwareversion
asFDD-LTE15A.NotethatthisdependsonthelatestFDD-LTE15Aalwaysbeing
includedintheLTE17eNBsoftwarebuild.
ThisfeatureusesrequirementsspecifiedinpreviousLTEsoftwaremanagementand
systemupgradefeatures.
Thefollowingupgraderequirements/featuresofearlierFDDreleasesaresupported:
FDD-LTE16ALTE2633
FDD-LTE16LTE2341
FDD-LTE15ALTE2049
RL70LTE1854
RL60LTE1560
RL50LTE1368
RL40LTE1078
RL30LTE882
RL20LTE185

g Note: ThisfeatureutilizesboththeOM_GEN_SFS_RNWINTand
OM_GEN_SFS_SWMGMNTSFSusecasesandfunctionalrequirementscreatedor
updatedforLTE3134astheusecasesandfunctionalrequirementsfortheprevious
releaseLTEsystemupgradefeatureslistedabove.

Impact on interfaces
TheLTE3134: FDD-LTE 17 System Upgradefeaturehasnoimpactoninterfaces.

Impact on network management tools


TheLTE3134: FDD-LTE 17 System Upgradefeatureimpactssystemperformanceand
capacityasfollows:
Theenduserwillexperienceaservicedegradationandpartialservicelossduring
thesystemupgrade.
Thedowntimeforthenetworkentitiesisreducedtotheactivationofthenew
softwareduringthesystemupgrade.

DN09237915Issue:01A 2017Nokia 165


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Impact on system performance and capacity


TheperformanceoftheLTE17networkelementsduringupgradeisexpectedtobethe
sameastheLTE16Anetworkelements.TheexistingLTEeNBandLTEOMSupgrade-
relatedperformancerequirementsapplytotheLTE17upgrade.
TheexistingLTEeNBandLTEOMSupgrade-relatedcapacityrequirementsapplytothe
LTE17upgrade.

5.2.4 LTE3134 reference data


LTE3134: FDD-LTE 17 System Upgrade requirements and sales information

Requirements

Table 93 LTE3134hardwareandsoftwarerequirements
System release Flexi Multiradio Flexi Multiradio Flexi Zone Micro Flexi Zone
BTS 10 BTS BTS Access Point
FDD-LTE17 Notsupported FL17 FLF17 FLF17

Flexi Zone OMS UE NetAct MME SAE GW


Controller
FLC17 LTEOMS17 Supportnot NetAct17.2 Supportnot Supportnot
required required required

Alarms
TherearenoalarmsrelatedtotheLTE3134: FDD-LTE 17 System Upgradefeature.

Commands
TherearenocommandsrelatedtotheLTE3134: FDD-LTE 17 System Upgradefeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE3134: FDD-LTE 17 System
Upgradefeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3134: FDD-LTE 17 System
Upgradefeature.

Parameters
TherearenoparametersrelatedtotheLTE3134: FDD-LTE 17 System Upgradefeature.

Sales information

Table 94 LTE3134salesinformation
Product structure class License control Activated by default
BasicSoftware(BSW) Notsupported Yes

166 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

5.2.5 Upgrading the LTE eNB to LTE 17

Purpose
Followthisproceduretoavoidlosingnon-networkconfigurationdatawhenupgraded
LTE17eNBsareuploadedtoConfigurator.

Before you start


TheoperationissupportedformacroeNBsfromFDD-LTE16orFDD-LTE16AtoFDD-
LTE17.
Theoperationisnotsupportedfor:

FlexiZoneController
FlexiZoneMicroBTS(microeNB).

MakesurethatIntelligentConfigurationSynchronizationisdisabled(recommended).
WorkingsetsaredoneforgroupingtheeNBsasthescopeforupgradeoperations.

Procedure

1 In NetAct Start Page click on CM Operations Manager.

Step result
TheCMOperationsManagerwindowopens.

2 In the Tools menu choose Workflow Engine.

Step result
TheWorkflow Enginedialogopens.

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

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

5 Run the Prepare for upgrade operation before the software upgrade to ensure
that the parameters are up to date.

Step result
LTE16andLTE16Anon-networkdataisstoredintodataexportfiles.

DN09237915Issue:01A 2017Nokia 167


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

6 In the NetAct Start Page click on Software Manager.

Step result
TheSoftwareManagerapplicationopens.

7 Using Software Manager, upgrade the LTE 17 software build for the eNBs.
NotethatyoucanusethesameworkingsetastheConfigurator.

g Note: BTSSMcanalsobeusedfortheupgrade.

8 In the Workflow Engine, continue the workflow by selecting Upload


configuration data.

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

10 Update the Configurator non-network data to the LTE 17 MRBTSs by selecting


Update non-network parameter data and clicking Start icon next to the
operation. Click Start.

Result

TheeNBisupgradedtoLTE17softwareversion.
TheeNBconfiguration(accordingtothenewinformationmodel)issynchronizedto
theConfiguratorconfigurationdatabase.
Thenon-networkconfigurationisavailableintheConfigurator.

5.2.6 Rolling back the upgrade

Before you start


LTE17softwareupgradehasbeencompletedfortheeNBfollowingtheprocedure
describedinUpgradingtheLTEeNBtoLTE17.
IntelligentConfigurationSynchronizationisdisabled(recommended).

Procedure

1 In NetAct Start Page click on Software Manager.

Step result
TheSoftwareManagerapplicationopens.

168 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

2 Using the Software Manager, roll back the LTE 17 software build for the eNB.
For more details, see Software Manager Help.

g Note: BTSSMcanalsobeusedfortherollbackprocedure.

Step result
ThesoftwareversionoftheeNBisrolledbacktotheonepreviouslyinstalled(FL16,
FL16Aorother).

3 In NetAct Start Page click on CM Operations Manager.

Step result
TheCMOperationsManagerdialogopens.

4 In the Tools menu choose Workflow Engine.

Step result
TheWorkflowEnginedialogopens.

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

6 Drag and drop the eNB to the MO(s) window.

7 In the Start column, click the Start icon next to Upload configuration data after
rollback operation. Click Start.

Step result
LTE16orLTE16Adataisuploaded.

8 In the Start column, click the Start next to Update non-network parameter data
after data rollback operation. Click Start.

Step result
LTE16orLTE16Anon-networkdataisrestored.

Result

TheeNBisrolledbacktoLTE16/LTE16Asoftwareversion.
TheeNBconfigurationissynchronizedwiththeConfigurator'sconfiguration
database.
Thenon-networkconfigurationintheConfiguratorhasbeenrestoredtotheearlier
state.

DN09237915Issue:01A 2017Nokia 169


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Formoreinformation,seetheExecuting NetAct Configurator Workflowsdocument.

5.3 LTE3296/SR001527: Harmonized Object Model for


SRAN and LTE
Benefits, functionality, system impact, reference data of the feature

Introduction
TheLTE3296/SR001527: Harmonized Object Model for SRAN and LTEfeature
introducesanewobjectmodelforbothproductsthatharmonizestheapproachto
configurationandcreatesamorelogical,expandabletopologyofManagedObject
Classes(MOCs)thateasilysupportsaddingfuturetechnologies.
Thechangestothecurrentobjectmodelreflectanewwayofapproachingconfiguration
thatseparatesconfiguredhardwarefromdetectedhardware,thatconsolidates
parametersaccordingtotheirpurpose,anddistinguishesbetweencommon
managementparametersandRadioAccessTechnology(RAT)-specificones..

5.3.1 LTE3296/SR001527 benefits


TheLTE3296/SR001527: Harmonized Object Model for SRAN and LTEfeatureprovides
thefollowingbenefits:
Reducedefforttoconfigureandadministrateamixedtechnologynetwork
Lessriskwhenupgradingasitetomulti-RATduetomisconfiguration

5.3.2 LTE3296/SR001527 functional description


TheLTE3296/SR001527:HarmonizedObjectModelforSRANandLTEfeaturealtersthe
objectmodelofbothLTEandSRANproductstoaligntheminonetopology.Thereare
someconceptualchangesintroducedtomaketheobjectmodelscalableandmore
usefultotheoperator,aswellassimplerelocations.Themajorchangescanbe
summarizedasfollows:
Configuredhardwareisseparatedfromhardwaredetectedatruntime.Anewtop-
levelMOCnamedEQMholdstheconfigurationofhardwarespecifiedbytheoperator,
andasimilarMOCnamedEQM_Rholdstheconfigurationofhardwaredetectedby
theeNBatruntime.TheDistinguishedName(DN)oftheobjectconfiguringthat
hardwareintheEQMtreeismappedtothedetectedhardwareinEQM_R.
HardwaretopologyisnowdefinedbyanewsetofobjectsintheEQM/EQM_Rtrees.
ConfiguredtopologyisnowintheHWTOPtree,splitintophysicalandlogicallinksin
CABLINKandLOGLINKobjects,andsimilarlythedetectedhardwaretopologyis
storedinCABLINK_RandLOGLINK_RobjectsunderHWTOP_RinEQM_R.
CommonmanagementparametersarelocatedintheMNLobjecttreeonthetop
level.ActionssuchasSWresetorcalibrationandtestingarelocatedinthistree.The
managementsubtreealsoholdsthenewCELLMAPPINGtreetoconfiguremapping
betweencellsandphysicalresources,replacingtheBTSSCL/LCELLobject.
FDDandTDDparametersarealignedintoonecommonmodel,withtechnology-
specificparametersbeingsplitintonewMOCswiththesuffix_TDDor_FDDas
appropriate.

170 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

ForSRAN,theRAT-specificparameterswillhavetheirowntop-levelsubtrees
LNBTS,WNBTSandGNBTSforLTE,WCDMAandGSMrespectively.

New MOC tree overview

Figure 15 Toplevelobjectsinthehierarchy

Changes to hardware configuration and detection


TheLTE3296/SR001527:HarmonizedObjectModelforSRANandLTEfeature
introducesanewwayofpresentingconfiguredanddetectedhardwaretothe
administrator.Configuredhardwareismaintainedseparatelyintheobjecthierarachy
undertheEQMobject,anddetectedhardwareispresentedundertheread-onlyEQM_R
hierarchy.DetectedhardwarethatmatchesconfiguredhardwareislinkedviaanIDinthe
relevantobjectunderEQM_R.

DN09237915Issue:01A 2017Nokia 171


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Figure 16 TheEQMandEQM_Robjecttrees

ForeachMOCundertheEQMsubtree,thereisacorrespondingMOCwiththesuffixof
_RintheEQM_Rsubtree.ThetwoMOCsarerelatedtoeachotherbytheirnamesand
alsoviatheparameterconfigDNinthe_Robject.configDNcontainsthe
DistinguishedName(DN)oftheMOCinEQM.FortheDNformat,pleaserefertothe
RAML2.1Specification,section2.1.Itispossiblethattherearediscrepanciesbetween
thetwosubtrees.Eveninthenormalcase,theEQM_Rtreecontainsmoreobjectsthan
theconfiguredlistbecausetheBTSisabletoprovidemoreinformationtotheoperator
withoutmanualconfigurations.Therearetwocaseswherethediscrepanciesare
reflectedintheconfigDNandstateattributes:
1. HardwareisinstalledbutthereisnoconfiguredEQMobject.Inthiscase,the_R
objectwillbepresentwithconfigDNsettoNULL.This_Robjectwillnotbe
enableduntilthecorrespondingEQMobjectisconfigured.
2. AnobjectinEQMisconfiguredbutthehardwareisnotinstalled.Inthiscase,the_R
objectwillbepresentwithconfigDNsettotheconfiguredobject.Thestatesofthe
_Robjectwillreflectthatitisnotinstalled.

Therearesignificantchangesinthehardwaretopologyarea.Newobjectshavebeen
introduced:CABLINKandLOGLINK.CABLINKrepresentsthephysicalcable,
LOGLINKrepresentsaconnectionbetweentwopoints,withoutexplicitlydefiningthe
environmentbetweenthem.TopologybetweenSystemModulesandRFmodulesare
definedasCABLINKsspecifiedonlybytheDistinguishedNamesoftheendpoints.For
anantennapathspecification,afulltopologyisrequired.
ThesearetheconfigurableobjectsandtheirusageforamacroBTS:
EQMThetopobjectoftheEQMtree.Itmustalwaysbepresent.
APEQMAccesspointequipmentsubtree.Thissubtreeconsistsofequipmentthat
makesupanaccesspoint.Formacro,thereisonly1instanceofit.
CABINETAtleastoneisneededtohousethesystemandbasebandmodules.

172 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

SMODSystemModule.ThecontrolleroftheBTScontainingthemanagement
interfacetowardsNetAct.Dependingonthehardwarerelease,itmayormaynot
containbasebandprocessing.TheremayalsobemultipleSMODsbutonlyonewillbe
themaincontroller.AdditionalSMODsareforexpansionpurposes.
EAC_IN,EAC_OUTtheseareoptionalenvironmentalcontrolforalarminputs
(EAC_IN)orrelaycontrol(EAC_OUT).TheycanalsobepresentunderanRMOD.
BBMODBasebandModule.Basebandprocessingmodule.Additionalmodulescan
beaddedtoaSystemmoduletoexpandtheprocessingcapacity.
PASSDEVagenericMOCfortheoperatortodocumentequipmentthatcannotbe
detectedbytheBTS.ItcanbeusedformodelingpassiveALDdevicesorsimplya
wayfortheoperatortorecordinventorydataofotherpassivedevices(e.g.power
supply,fan)forthepurposeofkeepingtrackofHWinventory.
RMODRadiomodule.ThiscanbeanRFmodulethatispartofthesystemmodule
(asinsmallcell),locallyconnectedtotheSystemModuleorremotelyconnectedas
aRemoteRFHead(RRH).
SMOD_EXTavirtualobjecttorepresentasystemmodulefromapeerBTS.InRF
sharing,theSMOD_EXTrepresentsanotherBTSthatsharesresourcesofoneor
moreradiomodules.
HWTOPHardwareTopologytopobject.Itmustalwaysbepresent.
CABLINK,LOGLINKHardwareTopologyobjectsdefiningphysicalandlogical
connectionsbetweenmodules.

Common Management subtree MNL


TheMNLtreecontainsthreeobjects:
CMD-Commands,suchashardwareresetorRETunitcalibration,areactivated
here.
NOTES-ContainsNOTEobjectsthatmaybefreelyfilledbytheoperatorforany
purpose.
MNLENT-SystemmodulespecificobjectsareplacedunderMNLENT.

TheMNLENT(ManagementLayerEntity)objectcontainssystemmodulespecific
parametersandisplacedunderMNLwithoneinstanceforeachentity.Therelated
objectsunderMNLENTareasfollows:
BBADM-BasebandAdministration.ContainsBBPOOLobjects.
CAPADM-CapacityAdministration.Capacityconfigurationandlimitationsaredefined
here.
CELLMAPPING-CellMapping.Thisreplacesthecellmappinglistthatwas
previouslypartofLNCEL.
FMCADM-FaultManagementCommonAdministration.Parametersrelatedtofault
managementaremovedhere.
FEATCADM-FeatureCommonAdministration.Parameterstoactivateand
administerspecificfeaturesappearhere.
PMCADM-PerformanceandMonitoringCommonAdministration.
SECADM-SecurityCommonAdministration.Securityrelatedparametersarefound
here,andadditionalsecurityinformationdetectedbytheBTSisavailableinthe
SECADM_Rsub-object.
SYNC-Synchronization.Timesourceandsynchronizationconfigurationismade
here.

DN09237915Issue:01A 2017Nokia 173


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

TEST-Tests.Testingisactivatedhereandtheresultsreturnedasobjectsunderthe
TESTobject.
TRBLCADM-TroubleshootingCommonAdministration.Containstroubleshooting
parameters.

Figure 17 TheMNLtree

Figure 18 TheMNLENTsubtree

TheCELLMAPPINGsubtreecontainsthenewschemeformappingcellstoantennas
thatreplacesthepreviousoneinBTSSCL/LCELL.TheCELLMAPPINGobjectcontains
anumberofLCELLobjectsequivalenttotheoldLCELLobject,buteachnewLCELL
objectcontainsanumberofCHANNELGROUPobjectsthatcontainCHANNELobjects.
TheCHANNELGROUPandCHANNELobjectsreplacethelegacyresourceList
parameterintheoldLCELL.

174 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

EachCHANNELobjectislinkedtoanANTLobjectintheEQMtreeusingtheantlDN
parameter,anditalsocontainsadirectionparametertospecifywhetherthechannelis
RXorTX.ATXRXantennalineisconfiguredwithtwoCHANNELobjects,oneforeach
direction.AstheANTLisachildobjectofanRMOD,thereisnoneedtospecifytheold
rmodIdorantIdparameters.

Unification of LNCEL for FDD and TDD technologies


TheLTE3296/SR001527:HarmonizedObjectModelforSRANandLTEfeatureunifies
thepreviouslydifferenthierarchiesoftheLNBTS/LNCELtreeintooneform.
TheLNCELobjecthasanewparametercellTechnologythatmaybesetasFDDor
TDD.TDD-andFDD-specificparametersinLNCELaremovedtotechnology-specific
objectsLNCEL_TDDandLNCEL_FDDrespectively,whichcontaintechnology-specific
objectsforMPUCCHandAPUCCHwiththe_TDDand_FDDsuffix.LNCELchildobjects
belongingtoonespecifictechnologyareconfiguredonlyifthattechnologyisspecifiedby
thecellTechnologyparameterintheLNCELparent,andobjectscommontoboth
technologiesareconsistency-checkedaccordingtothatsameparameter.
TheLNBTSobjecthasasimilarcontrollingparameternamed
supportedCellTechnologythatappliestothewholeeNB,andagainTDD-and
FDD-specificparametersaremovedtochildobjectsnamedLNBTS_TDDand
LNBTS_FDDrespectively.Commonchildclassesarealignedandconsistency-checked
accordingtothatparameter,withtheexceptionofMBSFNSYNCAREAandMBSFNSYNC
whicharesplitintotechnology-specificclasseswiththe_TDDand_FDDsuffix.

DN09237915Issue:01A 2017Nokia 175


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Figure 19 TheLNBTStree

176 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

Figure 20 TheLNCELtree

5.3.3 LTE3296/SR001527 system impact


LTE3296/SR001527: Harmonized Object Model for SRAN and LTE impact on network
management tools

Interdependencies between features


TherearenointerdependenciesbetweentheLTE3296/SR001527: Harmonized Object
Model for SRAN and LTEfeatureandanyotherfeature.

Impact on interfaces
TheLTE3296/SR001527: Harmonized Object Model for SRAN and LTEfeaturehasno
impactoninterfaces.

Impact on network management tools


TheLTE3296/SR001527: Harmonized Object Model for SRAN and LTEfeatureimpacts
networkmanagementtoolsasfollows:
WebUIElementManager
TheWebUIEMwilldisplaythenewMOCtreeintheparameterview

Impact on system performance and capacity

DN09237915Issue:01A 2017Nokia 177


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

TheLTE3296/SR001527: Harmonized Object Model for SRAN and LTEfeaturehasno


impactonsystemperformanceorcapacity.

5.3.4 LTE3296/SR001527 reference data


LTE3296/SR001527: Harmonized Object Model for SRAN and LTE requirements and
sales information

Software requirements

Table 95 LTE3296/SR001527softwarerequirements
System SBTS BSC RNC OMS NetAct
Release
LTE17 SBTS17 Supportnot Supportnot Supportnot NetAct17
required required required

Flexi Multiradio Flexi Multiradio Nokia AirScale Flexi Zone Micro Flexi Zone
BTS 10 BTS BTS BTS Access Point
notsupported FL17 FL17 FL17 FL17

Flexi Zone OMS UE NetAct MME SAE GW


Controller
FL17 supportnot supportnot 17.2 supportnot supportnot
required required required required

Hardware requirements
Thisfeaturehasnohardwarerequirements

TherearenoalarmsrelatedtotheLTE3296/SR001527: Harmonized Object Model for


SRAN and LTEfeature.

Faults and reported alarms


TherearenofaultsrelatedtotheLTE3296/SR001527: Harmonized Object Model for
SRAN and LTEfeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE3296/SR001527: Harmonized
Object Model for SRAN and LTEfeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3296/SR001527: Harmonized
Object Model for SRAN and LTEfeature.

Parameters
TherearenoparametersrelatedtotheLTE3296/SR001527: Harmonized Object Model
for SRAN and LTEfeature.
Thefulllistofparametersthathavebeenrelocatedoralteredduetothisfeaturewillbe
availableinafuturedelivery.

178 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

Sales information

Table 96 LTE3296/SR001527salesinformation
Product structure class License control Activated by default
BasicSoftware(BSW) - Yes

5.4 LTE3303: Enhanced VoLTE, CA, and RF Quality


Monitoring
TheLTE3303: Enhanced VoLTE, CA, and RF Quality Monitoringfeatureintroducesnew
countersandKPIsinthefollowingareas:
VoiceoverLTE(VoLTE)
Carrieraggregation(CA)
Radiofrequency(RF)qualitymonitoring.

5.4.1 LTE3303 benefits


TheLTE3303: Enhanced VoLTE, CA, and RF Quality Monitoringfeatureenablesthe
operatortomonitortheLTERANnetworkinmoredetail.

5.4.2 LTE3303 functional description


The LTE3303: Enhanced VoLTE, CA, and RF Quality Monitoring feature introduces
several new counters in a few categories. For more information, see the reference data
section.

5.4.3 LTE3303 system impact


The LTE3303: Enhanced VoLTE, CA, and RF Quality Monitoring feature has no impact
on features, interfaces, network management tools, and system performance and
capacity.

5.4.4 LTE3303 reference data


Requirements

Table 97 LTE3303hardwareandsoftwarerequirements
System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 notsupported FL17 FL17 FL17 FL17

Flexi Zone OMS UE NetAct MME SAE GW


Controller
FL17 supportnot supportnot 17.2 supportnot supportnot
required required required required

DN09237915Issue:01A 2017Nokia 179


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Alarms
TherearenoalarmsrelatedtotheLTE3303: Enhanced VoLTE, CA, and RF Quality
Monitoringfeature.

Measurements and counters

Table 98 E-RABreleaseduetointer-RAThandoverstoUTRANorGERANcounters
introducedbyLTE3303
Counter ID Counter name Measurement
M8006C303 Total number of released E-RABs due 8006-LTEEPS
to successful IRAT HO to UTRAN Bearer
(ERAB_REL_SUCC_HO_UTRAN)
M8006C304 Total number of released E-RABs due 8006-LTEEPS
to successful IRAT HO to UTRAN QCI1 Bearer
(ERAB_REL_SUCC_HO_UTRAN_QCI1)
M8006C305 Total number of released E-RABs due 8006-LTEEPS
to successful IRAT HO to UTRAN QCI5 Bearer
(ERAB_REL_SUCC_HO_UTRAN_QCI5)
M8006C306 Total number of released E-RABs due 8006-LTEEPS
to successful IRAT HO to GERAN Bearer
(ERAB_REL_SUCC_HO_GERAN)
M8006C307 Total number of released E-RABs due 8006-LTEEPS
to successful IRAT HO to GERAN QCI1 Bearer
(ERAB_REL_SUCC_HO_GERAN_QCI1)
M8006C308 Total number of released E-RABs due 8006-LTEEPS
to successful IRAT HO to GERAN QCI5 Bearer
(ERAB_REL_SUCC_HO_GERAN_QCI5)

Table 99 E-RABreleaseduetoS1interfacereasonscountersintroducedby
LTE3303
Counter ID Counter name Measurement
M8006C309 E-RAB releases due to eNB Initiated 8006-LTEEPS
Global S1 Reset Bearer
(ERAB_REL_ENB_INI_S1_GLOB_RESET)
M8006C310 E-RAB releases due to MME Initiated 8006-LTEEPS
Global S1 Reset Bearer
(ERAB_REL_MME_INI_S1_GLOB_RESET)
M8006C311 E-RAB releases due to eNB Initiated 8006-LTEEPS
Partial S1 Reset Bearer
(ERAB_REL_ENB_INI_S1_PART_RESET)
M8006C312 E-RAB releases due to MME Initiated 8006-LTEEPS
Partial S1 Reset Bearer
(ERAB_REL_MME_INI_S1_PART_RESET)
M8006C313 E-RAB releases due to S1 Outage 8006-LTEEPS
(ERAB_REL_S1_OUTAGE) Bearer
M8006C314 E-RAB releases due to double S1 8006-LTEEPS
detected(ERAB_REL_DOUBLE_S1) Bearer
M8006C315 E-RAB releases due to double S1 8006-LTEEPS
detected QCI1 Bearer
(ERAB_REL_DOUBLE_S1_QCI1)

180 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

Table 100 VoLTEPRBusagecounterintroducedbyLTE3303


Counter ID Counter name Measurement
M8011C208 Number of UL PRBs Used for VoLTE 8011-LTECell
(PRB_USED_UL_VOLTE) Resource
M8011C215 Number of UL PRBs used for TTI 8011-LTECell
Bundling (PRB_USED_UL_TTIB) Resource

Table 101 HARQBLERcountersintroducedbyLTE3303


Counter ID Counter name Measurement
M8026C273 Total number of Initial HARQ 8026-LTEQoS
Transmission for SRB in Downlink
(TOT_N_INI_HARQ_TX_SRB_DL)
M8026C274 Total number of Initial HARQ 8026-LTEQoS
Transmission for nonGBR in Downlink
(TOT_N_INI_HARQ_TX_NONGBR_DL)
M8026C275 Total number of Failed Initial HARQ 8026-LTEQoS
Transmission for SRB in Downlink
(TOT_N_FAIL_INI_HARQ_TX_SRB_DL)
M8026C276 Total number of Failed Initial HARQ 8026-LTEQoS
Transmission for nonGBR in Downlink
(TOT_N_F_INI_HARQ_TX_NONGBR_DL)
M8026C277 Total number of NO Feedback for 8026-LTEQoS
Initial HARQ Transmission for SRB in
Downlink(T_N_NO_FB_INI_HARQ_TX_SRB_DL)
M8026C278 Total number of NO Feedback for 8026-LTEQoS
Initial HARQ Transmission for nonGBR
in Downlink
(T_N_NO_FB_INI_HARQ_TX_NGBR_DL)
M8026C279 Total number of Initial HARQ 8026-LTEQoS
Transmission for GBR excluding VoLTE
in Downlink(TOT_N_INI_HARQ_TX_GBR_DL)
M8026C280 Total number of Failed Initial HARQ 8026-LTEQoS
Transmission for VoLTE in Downlink
(TOT_N_F_INI_HARQ_TX_VOLTE_DL)
M8026C281 Total number of Failed Initial HARQ 8026-LTEQoS
Transmission for GBR excluding VoLTE
in Downlink
(TOT_N_F_INI_HARQ_TX_GBR_DL)
M8026C282 Total number of NO Feedback for 8026-LTEQoS
Initial HARQ Transmission for VoLTE
in Downlink
(T_N_NO_FB_INI_HARQ_TX_VOLTE_DL)
M8026C283 Total number of NO Feedback for 8026-LTEQoS
Initial HARQ Transmission for GBR
excluding VoLTE in Downlink
(T_N_NO_FB_INI_HARQ_TX_GBR_DL)

g Note: ThefollowingcountersareavailableintheLTE17softwarerelease,however,
theywillnotbeverifieduntilltheLTE17SPsoftwarerelease.

DN09237915Issue:01A 2017Nokia 181


Descriptionsofoperabilityfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Table 102 UEcontextreleasecountersintroducedbyLTE3303


Counter ID Counter name Measurement
M8013C76 eNB initiated UE Context releases 8013-LTEUE
with radio network layer cause State
"Inter-RAT redirection" due to
coverage reasons
(UE_CTX_REL_ENB_RNL_IRAT_RED_CO)
M8013C77 eNB initiated UE Context releases due 8013-LTEUE
to Global S1 Reset State
(UE_CTX_REL_ENB_GLOB_S1_RESET)
M8013C78 eNB initiated UE Context releases due 8013-LTEUE
to Partial S1 Reset State
(UE_CTX_REL_ENB_PART_S1_RESET)
M8013C79 eNB initiated UE Context releases due 8013-LTEUE
to S1 Outage State
(UE_CTX_REL_ENB_S1_OUTAGE)
M8013C80 MME initiated UE Context releases due 8013-LTEUE
to Global S1 Reset State
(UE_CTX_REL_MME_GLOB_S1_RESET)
M8013C81 MME initiated UE Context releases due 8013-LTEUE
to Partial S1 Reset State
(UE_CTX_REL_MME_PART_S1_RESET)
M8013C82 MME Initiated UE Context releases due 8013-LTEUE
to detected double S1 State
(UE_CTX_REL_DOUBLE_S1)

g Note: ThefollowingcountersareavailableintheLTE17softwarerelease,however,
theywillnotbeverifieduntilltheLTE17SPsoftwarerelease.

Table 103 VoLTETTIbundlingcountersintroducedbyLTE3303


Counter ID Counter name Measurement
M8011C209 Number of TTI Bundling Switch on 8011-LTECell
attempts(TTI_BUNDLING_SWITCH_ON_ATTS) Resource
M8011C210 Number of TTI Bundling Switch on 8011-LTECell
successes Resource
(TTI_BUNDLING_SWITCH_ON_SUCCS)
M8011C211 Number of TTI Bundling Switch off 8011-LTECell
attempts(TTI_BUNDLING_SWITCH_OFF_ATTS) Resource
M8011C212 Number of TTI Bundling Switch off 8011-LTECell
successes Resource
(TTI_BUNDLING_SWITCH_OFF_SUCCS)

g Note: ThefollowingcountersareavailableintheLTE17softwarerelease,however,
theywillnotbeverifieduntilltheLTE17SPsoftwarerelease.

Table 104 Carrieraggregation(CA)downlinkdeconfigurationcountersintroducedby


LTE3303
Counter ID Counter name Measurement
M8011C213 Downlink CA Deconfiguration Attempts 8011-LTECell
(DL_CA_DECONFIG_ATT) Resource

182 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions Descriptionsofoperabilityfeatures

Table 104 Carrieraggregation(CA)downlinkdeconfigurationcountersintroducedby


LTE3303(Cont.)
Counter ID Counter name Measurement
M8011C214 Downlink CA Deconfiguration Successes 8011-LTECell
(DL_CA_DECONFIG_SUCC) Resource

Table 105 PMQAPprofilecountersintroducedbyLTE3303


Counter ID Counter name Measurement
M8048C9 E-RABs attempted to release due to 8048-LTEERAB
outgoing Intra LTE Handover Statisticsper
(ERAB_REL_INTRA_LTE_HO_ATT_PR) PMQAPProfile
M8048C10 E-RABs released due to successful 8048-LTEERAB
outgoing Intra LTE Handover Statisticsper
(ERAB_REL_INTRA_LTE_HO_SUCC_PR) PMQAPProfile
M8048C8 E-RABs All Abnormal releases per 8048-LTEERAB
Profile Statisticsper
(ERAB_REL_ALL_ABNORMAL_PROFILE) PMQAPProfile
M8048C3 E-RABs Abnormal releases per Profile 8048-LTEERAB
(ERAB_REL_ABNORMAL_ACT_PROFILE) Statisticsper
PMQAPProfile

Parameters
TherearenoparameterssrelatedtotheLTE3303: Enhanced VoLTE, CA, and RF
Quality Monitoringfeature.

Sales information

Table 106 LTE3303salesinformation


Product structure class License control Activated by default
BasicSoftware(BSW) - Yes

DN09237915Issue:01A 2017Nokia 183


DescriptionsofBTSsitesolutionfeatures FDD-LTE17,FeatureDescriptionsandInstructions

6 Descriptions of BTS site solution features

6.1 LTE2495: Plug-in Radio SW Interface for Nokia


CPRI
Benefits, functionality, system impact, reference data of the feature

TheLTE2495: Plug-in Radio SW Interface for Nokia CPRIfeatureenablesnew


RFM/RRHHWtobelaunchedwithoutdelayscausedbywaitingforthemainSWrelease
upgrade.

6.1.1 LTE2495 benefits


TheLTE2495: Plug-in Radio SW Interface for Nokia CPRIfeatureenablestointroduce
newRFM/RRHHWvariantsequippedwithNokiaCPRIinterfacewithoutwaitingfornew
SWreleases.

6.1.2 LTE2495 functional description

WithouttheLTE2495:Plug-inRadioSWInterfaceforNokiaCPRIfeature,new
RFM/RRHHWvariantrequiresthedeploymentofanewSWreleaseintheMobile
OperatorNetwork,becauseallRFM/RRHunitinformationandparametersaredelivered
togetherwiththemainSWreleasepacketintheSystemModule.Thisprocessiscalled
FULLDELIVERYMODE.
ThisLTE2495:Plug-inRadioSWInterfaceforNokiaCPRIfeatureallowstheuserto
connectnewRFM/RRHHWvariant(equippedwithNokiaCPRIinterface)withoutthe
requirementofupgradingthemainSWreleaseintheMobileOperatorNetwork.This
processiscalledFASTDELIVERYMODE.
ItisatNokiasdiscretiontodecidewhichnewRFM/RRHHWvariantcansupportFAST
DELIVERYMODE.
Pleaserefertothefiguresbelowwiththecomparisionoftwocases:
1. FULLDELIVERYMODEwithouttheLTE2495:Plug-inRadioSWInterfaceforNokia
CPRIfeature
2. FASTDELIVERYMODEwiththeLTE2495:Plug-inRadioSWInterfaceforNokia
CPRIfeature

184 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions DescriptionsofBTSsitesolutionfeatures

Figure 21 FULLDELIVERYMODEwithoutthe
LTE2495:Plug-inRadioSWInterfaceforNokiaCPRIfeature
ThegapbetweenNewRadioModulevariant MobileOperatorcanuseNew
availabilityanddeploymentofRelease(n+1) RadioModulevariantinits
intheMobileOperatorNetwork networkwithRelease(n+1)

MobileOperator Release(n+1)deployedin
perspective Release(n)deployedintheMobileOperatorNetwork
theMobileOperatorNetwork

Nokia'sinternalprocess Nokia'sinternalprocess
todevelopRelease(n) todevelopRelease(n+1)

NewRadioModulevariant
includedintheRelease(n+1)
InternalNokia's Nokia'sinternalprocesstodevelop FULLDELIVERYMODE
perspective newRadioModulevariant

P8 NewRadio P8N+1Release Time


Release(n) Modulevariant Release(n+1)
Example:RL16 isready Example:RL16A

Figure 22 FASTDELIVERYMODEwiththe
LTE2495:Plug-inRadioSWInterfaceforNokiaCPRIfeature
MobileOperatorcanuseNew
MobileOperatorcanuseNewRadioModule RadioModulevariantinits
variantinitsnetworkwithRelease(n) networkwithRelease(n+1)

MobileOperator
Release(n+1)deployedin
perspective Release(n)deployedintheMobileOperatorNetwork
theMobileOperatorNetwork

Nokia'sinternalprocess NewRadioModule Nokia'sinternalprocess


variantcanbeusedwith
todevelopRelease(n) todevelopRelease(n+1)
Release(n)alreadydeployed
intheMobileOperatorNetwork NewRadioModulevariant
FASTDELIVERYMODE includedintheRelease(n+1)
InternalNokia's Nokia'sinternalprocesstodevelop FULLDELIVERYMODE
perspective newRadioModulevariant

N+1Release
P8 NewRadio P8 Time
Release(n) Modulevariant Release(n+1)
Example:RL16 isready Example:RL16A

6.1.3 LTE2495 system impact


LTE2495: Plug-in Radio SW Interface for Nokia CPRI impact on features and network
management tools

Interdependencies between features


TheLTE2495: Plug-in Radio SW Interface for Nokia CPRIfeatureimpactsRF/RRHHW
variantequippedwithNokiaCPRIinterfacefeaturesdeployedinFASTDELIVERY
MODE.

g Note: CPRIinterfacetypesotherthanNokiaCPRIarenotsupportedwith
LTE2495: Plug-in Radio SW Interface for Nokia CPRI(e.g.CPRI-Aradiosarenot
supportedwithLTE2495: Plug-in Radio SW Interface for Nokia CPRI).

Impact on interfaces

DN09237915Issue:01A 2017Nokia 185


DescriptionsofBTSsitesolutionfeatures FDD-LTE17,FeatureDescriptionsandInstructions

TheLTE2495: Plug-in Radio SW Interface for Nokia CPRIfeaturehasnoimpacton


interfaces.

Impact on network management tools


TheNetActandBTSSiteManagerhavetobeupdatedwiththeplug-inmodule.

Impact on system performance and capacity


TheLTE2495: Plug-in Radio SW Interface for Nokia CPRIfeaturehasnoimpacton
systemperformanceorcapacity.

6.1.4 LTE2495 reference data


LTE2495: Plug-in Radio SW Interface for Nokia CPRI requirements and sales
information

Requirements

Table 107 LTE2495hardwareandsoftwarerequirements


System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 Notsupported FL17 FL17 Notsupported Notsupported

Flexi Zone OMS UE NetAct MME SAE GW


Controller
Supportnot LTEOMS17 Supportnot NetAct17.2 Supportnot Supportnot
required required required required

Therearenoalarms,measurementsandcounters,keyperformanceindicators,
parametersrelatedtotheLTE2495: Plug-in Radio SW Interface for Nokia CPRIfeature.

Sales information

Table 108 LTE2495salesinformation


Product structure class License control Activated by default
BasicSoftware(BSW) - Yes

6.2 LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W


Benefits, functionality, system impact, reference data of the feature

TheLTE2769: FRGX Flexi RFM 3-pipe 2100 240 WfeatureintroducestheFlexi


MultiradioRFModule(FRGX)for3GPP2100MHzband1(uplink:1920-1980MHz,
downlink:2110-2170MHz).FRGXhasthreepoweramplifiersenablingittosupport
one,twoorthreesectorswithanoutputpowerofupto80WattsxTXMIMOattheBTS
antennaconnectors.

186 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions DescriptionsofBTSsitesolutionfeatures

6.2.1 LTE2769 benefits


TheLTE2769: FRGX Flexi RFM 3-pipe 2100 240 Wfeatureprovidesthefollowing
benefits:
TwoRFModulesareabletosupportthreesectorswithfull2100MHzRFspectrum
utilizationforWCDMAandLTEmode.
Flexibleinstallationoptions.FRGXisdesignedtobemountedontoawallorapole.
IP65environmentalprotectionclass.

6.2.2 LTE2769 functional description

ThemainfeaturesoftheFRGXareasfollows:
2100MHz3GPPband1support
60MHzinstantaneousbandwidth
8W,10W,15W,20W,30W,40W,60Wand80Wpowerlevelsupport
5MHz,10MHz,15MHzand20MHzcarrierbandwidthsupport
MaximumeightWCDMA/LTEcarriersperantennaconnectorwithamaximum
occupiedbandwidthof40MHzmultiplecarrierswithamaximuminstantaneous
bandwidthof60MHzinuplinkanddownlink
LTE-LTEandLTE-WCDMARFsharingsupport
Forcedcoolingbytheintegratedfans
25lvolume
25kgweight

TheFRGXsupportsthefollowingmodulationschemes:
QAM64(DL/UL)
QAM256(DL/UL)

TheFRGXcanbeinstalled:
onapole.
onawall.
onafloor.
ontopofanothermodule.
insideofa19-inchrackoracabinet.

FormoreinformationonFRGX,seetheFlexi Multiradio BTS RF Module and Remote


Radio Head Descriptiondocument.
ForallsupportedconfigurationsincludingthoseforFRGX,seetheCreating LTE
Configurationsdocument.
ForimplementationandconfigurationsforRFsharing,seetheFlexi Multiradio BTS RF
Sharing Released Configurationsdocument.

DN09237915Issue:01A 2017Nokia 187


DescriptionsofBTSsitesolutionfeatures FDD-LTE17,FeatureDescriptionsandInstructions

6.2.3 LTE2769 system impact


LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W impact on features, interfaces, network
management tools, and system performance and capacity

Interdependencies between features


ThefollowingfeaturesmustbeactivatedbeforeactivatingtheLTE2769: FRGX Flexi
RFM 3-pipe 2100 240 Wfeature:
LTE115: Cell Bandwidth - 5 MHzforthesupportofthe5MHzcarriers
LTE114: Cell Bandwidth - 10 MHzforthesupportofthe10MHzcarriers
LTE113: Cell Bandwidth - 15 MHzforthesupportofthe15MHzcarriers
LTE112: Cell Bandwidth - 20 MHzforthesupportofthe20MHzcarriers

TheLTE2769: FRGX Flexi RFM 3-pipe 2100 240 Wfeatureisimpactedbythefollowing


features:
LTE614: Distributed Site
WiththisfeatureFRGXcanbeusedindistributedsiteswithupto23kmfiberlength
tothesystemmodule.
LTE977: RF chaining
WiththisfeatureFRGXsupportschainsofupto3radiounits.
LTE1103: Load based Power Saving for multi-layer networksorLTE1203: Load
based Power Saving mode with Tx power reduction or path switching off
OneofthesefeaturesmustbeenabledtousethePAshutdownfeature.
LTE1891: eNode B power saving - Micro DTX
ThisfeaturemustbeenabledtouseMicroDTXextension.

Impact on interfaces
TheLTE2769: FRGX Flexi RFM 3-pipe 2100 240 Wfeaturehasnoimpactoninterfaces.

Impact on network management tools


TheLTE2769: FRGX Flexi RFM 3-pipe 2100 240 Wfeaturehasnoimpactonnetwork
managementtools.

Impact on system performance and capacity


Newconfigurationsareavailable.

6.2.4 LTE2769 reference data


LTE2769: FRGX Flexi RFM 3-pipe 2100 240 W requirements, alarms and faults,
measurements and counters, KPIs, parameters, and sales information

Requirements

188 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions DescriptionsofBTSsitesolutionfeatures

Table 109 LTE2769: FRGX Flexi RFM 3-pipe 2100 240 Whardwareandsoftware
requirements
System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 Notsupported FL17 FL17 Notsupported Notsupported

Flexi Zone OMS UE NetAct MME SAE GW


Controller
Supportnot Supportnot Supportnot Supportnot Supportnot Supportnot
required required required required required required

Therearenoalarms,measurementsandcounters,keyperformanceindicators,
parametersrelatedtotheLTE2769: FRGX Flexi RFM 3-pipe 2100 240 Wfeature.

Sales information

Table 110 LTE2769: FRGX Flexi RFM 3-pipe 2100 240 Wsalesinformation
Product structure class License control Activated by default
BasicSoftware(BSW) - Yes

6.3 LTE3133: FRCI Flexi RRH 2T2R 875 120 W


Benefits, functionality, system impact, reference data, instructions of the feature

TheLTE3133: FRCI Flexi RRH 2T2R 875 120 WfeatureintroducesFlexiMultiradio


RemoteRadioHead(RRH)FRCIfortheIndianmarketwith2TXMIMOfor3GPPFDD
Band5(uplink:824-843.2MHz,downlink:869-888.4MHz).FRCIisa2-pipeRRH
optimizedfordistributedmacroBTSinstallations.

6.3.1 LTE3133 benefits


TheLTE3133:FRCI Flexi RRH 2T2R 875 120 W featureprovidesthefollowingbenefits:
TwoPowerAmplifiersenableFRCItosupportonesectorwithupto2X60W2TX
MIMOoutputpowerattheBTSantennaconnector.
Supportforbookmountinstallation.

6.3.2 LTE3133 functional description


Functional specification

Table 111 FRCIfunctionalspecification


Property Value
Outputpower 2x60W
MIMO 2TX

DN09237915Issue:01A 2017Nokia 189


DescriptionsofBTSsitesolutionfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Table 111 FRCIfunctionalspecification(Cont.)


Property Value
Outdoorinstallation Yes
SWsupportedtechnologies FDD-LTE
TXfrequencyrange 869MHz888.4MHz
RXfrequencyrange 824MHz843.4MHz
DLinstantaneousbandwidth 19.4MHz
ULinstantaneousbandwidth 19.4MHz
DLfilterbandwidth 19.4MHz
ULfilterbandwidth 19.4MHz
Modulationschemes QAM64(DL),QAM64(UL),QAM256(DL)
Supportedcarrierbandwidths 5MHz,10MHz,15MHz
Supportedpowerlevels 8,10,15,20,30,40,60W

TheFRCIRRHcanusemax.twoLTEcarriersperpipe.
TheFRCIRRHhasthevolumeof26.6L.Itweighs23kgwithoutthecoverandbrackets.
TheenvironmentalprotectionclassisIP65.
Formoreinformation,seeFlexi Multiradio BTS RF Module and Remote Radio Head
Description.

External interfaces
FRCIhasthefollowingexternalinterfaces:
2TX/RXportswith4.3-10connector
2pcsof6GbpsOBSAIopticalinterfaces
OneDCinconnector
OneAISG2.0Antennatiltsupportwithexternalconnector(RS485)
CompatiblewithoptionalFPADpowersupplywhenneededforACsolutions
Upto4externalalarmswiththeUSBconnector

Environmental operating conditions


TheFRCIFlexiRRHhastheoptionofconvectionalcooling.Generalenvironmental
operatingconditionsareasfollows:-35Cto+55Cwith-40Ccoldstart(with70%load,
nosolarload&3m/swind).

Mounting options
ThefollowingarethesupportedmountingoptionsforFRCIRRH:
Polemounting
Wallmounting
CompatibletoRASmounting
Bookmounting

190 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions DescriptionsofBTSsitesolutionfeatures

Supported Configurations
ForsinglecarrierLTE:allreleasedBTSconfigurationsvalidforRRH2Tx2RxRFunits.
FormulticarrierLTE:releasedLTEBTSconfigurationssupportingdualcarrierand
multicarrierconfigurationsaswellasintereNBRFsharingconfiguration.

6.3.3 LTE3133 system impact


LTE3133: FRCI Flexi RRH 2T2R 875 120 W impact on features, interfaces, network
management tools, and system performance and capacity

Interdependencies between features


ThefollowingfeaturesmustbeactivatedbeforeactivatingtheLTE3133: FRCI Flexi RRH
2T2R 875 120 Wfeature:
LTE117needstobeenabledtouseLTE1.4MHzcarriers
LTE116needstobeenabledtouseLTE3MHzcarriers
LTE115needstobeenabledtouseLTE5MHzcarriers
LTE114needstobeenabledtouseLTE10MHzcarriers

TheLTE3133: FRCI Flexi RRH 2T2R 875 120 Wfeatureisimpactedbythefollowing


features:
LTE614
WiththisfeaturetheFRCIcanbeusedindistributedsiteswithupto23kmfiber
lengthtothesystemmodule.
LTE977
WiththisfeaturetheFRCIsupportschainsofupto4radiounits.
LTE3096
WiththisfeaturetheRASinstallationoptionsaredefined.
LTE1103
ThisfeatureneedstobeenabledtouseLoad-basedPowerSavingformulti-layer
networks.
LTE1203
ThisfeatureneedstobeenabledtouseLoad-basedPowerSavingwithTxpath
switchingoff.
LTE2508
ThisfeatureneedstobeenabledtouseBTSEmbeddedPowerMeterforEnergy
EfficiencyMonitoring.
Toenablefulloutputpower,4powerlicensesperTXpipearerequired.
FollowingRF-sniffingfeaturescanbeusedwithFRCI:
LTE1434:FlexiMultiradioBTSantennaRxRF-sniffing
LTE2556:FlexiMultiradioBTSRx-Sniffingenhancements

Impact on interfaces
TheLTE3133: FRCI Flexi RRH 2T2R 875 120 Wfeaturehasnoimpactoninterfaces.

Impact on network management tools

DN09237915Issue:01A 2017Nokia 191


DescriptionsofBTSsitesolutionfeatures FDD-LTE17,FeatureDescriptionsandInstructions

TheLTE3133: FRCI Flexi RRH 2T2R 875 120 Wfeaturehasnoimpactonnetwork


managementtools.

Impact on system performance and capacity


Newconfigurationsareavailable.

6.3.4 LTE3133 reference data


LTE3133: FRCI Flexi RRH 2T2R 875 120W requirements, alarms and faults,
measurements and counters, KPIs, parameters, and sales information

Requirements

Table 112 LTE3133hardwareandsoftwarerequirements


System Flexi Flexi Nokia Flexi Zone Flexi Zone
release Multiradio Multiradio 10 AirScale BTS Micro BTS Access Point
BTS BTS
FDD-LTE17 Notsupported FL17 FL17 Notsupported Notsupported

Flexi Zone OMS UE NetAct MME SAE GW


Controller
Notsupported Supportnot Supportnot NetAct17.2 Supportnot Supportnot
required required required required

Alarms
TherearenoalarmsrelatedtotheLTE3133: FRCI Flexi RRH 2T2R 875 120Wfeature.

BTS faults and reported alarms


TherearenofaultsrelatedtotheLTE3133: FRCI Flexi RRH 2T2R 875 120Wfeature.

Measurements and counters


TherearenomeasurementsorcountersrelatedtotheLTE3133: FRCI Flexi RRH 2T2R
875 120Wfeature.

Key performance indicators


TherearenokeyperformanceindicatorsrelatedtotheLTE3133: FRCI Flexi RRH 2T2R
875 120Wfeature.

Parameters
TherearenoparametersrelatedtotheLTE3133: FRCI Flexi RRH 2T2R 875 120W
feature.

Sales information

Table 113 LTE3133salesinformation


Product structure class License control Activated by default
BasicSoftware(BSW) - Yes

192 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions DescriptionsofBTSsitesolutionfeatures

6.4 Interdependencies between CPRI-A features and


other features
Information on features related to CPRI-A features, features that require activation
before using CPRI-A features, and features not supported with CPRI-A features

Related documentation
TechnicaldescriptionsofCPRI-ARFMscanbefoundinthefollowingpath:LTE17
Operating documentation -> LTE BTS and OMS Descriptions -> CPRI-A
InstallationinstructionsforCPRI-ARFMscanbefoundunderthefollowingpath:LTE17
Operating Documentation -> Install and Commission -> CPRI-A
ForinformationaboutcompatibilityofCPRI-ARFMswithNokiaBTS,seeLTE/EPC RAN
Compatibilityat:LTE17 Operating Documentation -> Reference -> Compatability
ForallsupportedconfigurationsincludingCPRI-ARFMs,see:
Creating LTE ConfigurationslocatedatLTE17 Operating Documentation -> Install
and Commission
Creating Nokia AirScale BTS FDD-LTE ConfigurationslocatedatLTE17 Operating
Documentation -> Install and Commission
LTE Base Stations Supported ConfigurationslocatedatLTE17 Operating
Documentation -> Integrate and Configure

CPRI-A feature list


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

Interdependencies between CPRI-A features and other features


ThistableexpressestheallowedanddisallowedfeatureinteractionsofCPRI-Afeatures
withseveralpertinentfeaturegroups.Eachofthesefeaturegroupsisrepresentedby
onecolumn.ThespecificfeaturesineachofthefeaturegroupsarelistedinFeatures
withinterdependencieswithCPRI-Afeatures.

Table 114 InterdependenciesbetweenCPRI-Afeaturesandotherfeatures


CPRI-A PA shutdown Carrier RF-sniffing Supercell features
features features bandwidth features
features
LTE3307 S S NS -
(UHIE)

DN09237915Issue:01A 2017Nokia 193


DescriptionsofBTSsitesolutionfeatures FDD-LTE17,FeatureDescriptionsandInstructions

Table 114 InterdependenciesbetweenCPRI-Afeaturesandotherfeatures(Cont.)


CPRI-A PA shutdown Carrier RF-sniffing Supercell features
features features bandwidth features
features
LTE3308 S S NS -
(UHFE)
LTE3309 S S NS -
(UHCB)
LTE3350 S S NS -
(UHFF)
LTE3409 S S NS -
(UHIF)
LTE3410 S S NS -
(UHIG)
LTE3413 S S NS -
(UHBF)
S=>Supported
NS=>NotSupported
-=>notdeterminedatthistime

Features with interdependencies with CPRI-A features


PA shutdown features
ThePA(poweramplifier)shutdowncapabilityrequiresoneofthesefeatures:
LTE1103: Load based Power Saving for multi-layer networks
LTE1203: Load based Power Saving with Tx path switching off

Carrier bandwidth features


TouseLTE3MHz,5MHz,10MHz,15MHz,or20MHzcarriers,oneormoreofthe
followingfeaturesneedstobeenabled:
LTE116: Cell Bandwidth - 3 MHz
LTE115: Cell Bandwidth - 5 MHz
LTE114: Cell Bandwidth - 10 MHz
LTE113: Cell Bandwidth - 15 MHz
LTE112: Cell Bandwidth - 20 MHz
FordetailsaboutthesupportedbandwidthconfigurationsforallRFMsincludingCPRI-A
RFMs,seeLTE Base Stations Supported ConfigurationslocatedatLTE17 Operating
Documentation -> Integrate and Configure
RF-sniffing features
AllavailableCPRI-Afeaturesdonotsupportthefollowingfeatures:
LTE1434: Flexi Multiradio BTS antenna Rx RF-sniffing
LTE1634: Remote RF-diagnostics for Flexi Multiradio BTS
LTE2556: Flexi Multiradio BTS Rx-Sniffing enhancements

194 2017Nokia DN09237915Issue:01A


FDD-LTE17,FeatureDescriptionsandInstructions DescriptionsofBTSsitesolutionfeatures

Supercell features
Thesupercellfeaturesare:
LTE1542: FDD Supercell
LTE1709: Liquid Cell
LTE2091:FDDSuperCellextension
LTE2445: Combined Supercell

DN09237915Issue:01A 2017Nokia 195