You are on page 1of 253

NokiaNetworks

LTE Radio Access, Rel. RL70,


Operating Documentation,
Issue 02, Documentation
Change Delivery 8

LTE RL20, Feature


Descriptions
DN0978033
Issue 02M
Approval Date 2016-05-23

LTERL20,FeatureDescriptions

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

ThisdocumentisintendedforusebyNokiaSolutionsandNetworks'customers(You)only,anditmaynot
beusedexceptforthepurposesdefinedintheagreementbetweenYouandNokiaSolutionsandNetworks
(Agreement) under which this document is distributed. No part of this document may be used, copied,
reproduced, modified or transmitted in any form or means without the prior written permission of Nokia
Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that
Agreementhasexpiredorhasbeenterminated,YoumaynotusethisdocumentinanymannerandYou
areobligedtoreturnittoNokiaSolutionsandNetworksanddestroyordeleteanycopiesthereof.

The document has been prepared to be used by professional and properly trained personnel, and You
assumefullresponsibilitywhenusingit.NokiaSolutionsandNetworkswelcomeYourcommentsaspartof
theprocessofcontinuousdevelopmentandimprovementofthedocumentation.

This document and its contents are provided as a convenience to You. Any information or statements
concerningthesuitability,capacity,fitnessforpurposeorperformanceoftheProductaregivensolelyon
anasisandasavailablebasisinthisdocument,andNokiaSolutionsandNetworksreservestheright
tochangeanysuchinformationandstatementswithoutnotice.NokiaSolutionsandNetworkshasmadeall
reasonableeffortstoensurethatthecontentofthisdocumentisadequateandfreeofmaterialerrorsand
omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But,
NokiaSolutionsandNetworks'totalliabilityforanyerrorsinthedocumentisstrictlylimitedtothecorrection
ofsucherror(s).NokiaSolutionsandNetworksdoesnotwarrantthattheuseofthesoftwareintheProduct
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 SOLUTIONS AND NETWORKS BE
LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,
INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF
PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY
ARISEFROMTHEUSEOFTHISDOCUMENTORTHEINFORMATIONINIT,EVENINTHECASEOF
ERRORSINOROMISSIONSFROMTHISDOCUMENTORITSCONTENT.

ThisdocumentisNokiaSolutionsandNetworksproprietaryandconfidentialinformation,whichmaynotbe
distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and
Networks.

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

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

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its
productsandservices.Wewouldliketoencourageyouasourcustomersanduserstojoinusinworking
towardsacleaner,saferenvironment.Pleaserecycleproductpackagingandfollowtherecommendations
forpoweruseandproperdisposalofourproductsandtheircomponents.

IfyoushouldhavequestionsregardingourEnvironmentalPolicyoranyoftheenvironmentalserviceswe
offer,pleasecontactusatNokiaSolutionsandNetworksforanyadditionalinformation.

2 DN0978033 Issue:02M
LTERL20,FeatureDescriptions

Table of Contents
Thisdocumenthas253pages

Summaryofchanges................................................................... 22

1 RL20Features-notsupportedbyFlexiZoneMicro....................23

2 Radioresourcemanagementandtelecomfeatures.................... 24
2.1 LTE2:S1Flex...............................................................................24
2.1.1 Introductiontothefeature............................................................ 24
2.1.2 Benefits........................................................................................ 24
2.1.3 Requirements...............................................................................24
2.1.3.1 Softwarerequirements................................................................. 24
2.1.3.2 Hardwarerequirements................................................................24
2.1.4 Functionaldescription.................................................................. 25
2.1.4.1 S1interface.................................................................................. 25
2.1.4.2 MMEselection..............................................................................25
2.1.4.2.1 Loadbalancing.............................................................................26
2.1.5 Salesinformation......................................................................... 26
2.1.6 Userinterface...............................................................................27
2.1.6.1 Parameters...................................................................................27
2.1.6.2 Alarms.......................................................................................... 27
2.1.6.3 Measurementsandcounters........................................................27
2.1.7 Activatingandconfiguringthefeature..........................................27
2.1.8 Abbreviations............................................................................... 27
2.1.8.1 0Z............................................................................................. 27
2.2 LTE4:RANSharing...................................................................... 28
2.2.1 Introductiontothefeature............................................................ 28
2.2.2 Benefits........................................................................................ 28
2.2.3 Requirements...............................................................................28
2.2.3.1 Interdependenciesbetweenfeatures........................................... 28
2.2.3.2 Softwarerequirements................................................................. 28
2.2.3.3 Hardwarerequirements................................................................29
2.2.4 Requirements...............................................................................29
2.2.4.1 Interdependenciesbetweenfeatures........................................... 29
2.2.4.2 Softwarerequirements................................................................. 29
2.2.4.3 Hardwarerequirements................................................................29
2.2.5 Functionaldescription.................................................................. 29
2.2.5.1 Functionaloverview..................................................................... 30
2.2.5.2 Featureactivation.........................................................................30
2.2.6 Systemimpact..............................................................................30
2.2.6.1 Interdependenciesbetweenfeatures........................................... 30
2.2.7 LTE4:RANSharingmanagementdata........................................ 30
2.2.7.1 Alarms.......................................................................................... 30
2.2.7.2 Measurementsandcounters........................................................30

Issue:02M DN0978033 3
LTERL20,FeatureDescriptions

2.2.7.3 Keyperformanceindicators......................................................... 30
2.2.7.4 Parameters...................................................................................30
2.2.7.5 Salesinformation......................................................................... 31
2.3 LTE7:SupportofmultipleEPSbearer......................................... 31
2.3.1 IntroductionToTheFeature......................................................... 31
2.3.2 Benefits........................................................................................ 31
2.3.3 Requirements...............................................................................31
2.3.3.1 SoftwareRequirements................................................................31
2.3.3.2 HardwareRequirements.............................................................. 32
2.3.4 FunctionalDescription..................................................................32
2.3.5 SystemImpacts............................................................................37
2.3.6 SalesInformation......................................................................... 37
2.3.7 UserInterface...............................................................................37
2.3.7.1 Parameters...................................................................................37
2.3.7.2 MeasurementsandCounters.......................................................38
2.4 LTE9:ServiceDifferentiation........................................................41
2.4.1 Introductiontothefeature............................................................ 41
2.4.2 Benefits........................................................................................ 41
2.4.3 Requirements...............................................................................41
2.4.3.1 Softwarerequirements................................................................. 41
2.4.3.2 Hardwarerequirements................................................................41
2.4.4 Functionaldescription.................................................................. 41
2.4.5 Systemimpacts............................................................................ 43
2.4.6 Salesinformation......................................................................... 43
2.4.7 Userinterface...............................................................................43
2.4.7.1 Parameters...................................................................................43
2.4.7.2 Alarms.......................................................................................... 59
2.4.7.3 Measurementsandcounters........................................................59
2.4.8 Activatingthefeature................................................................... 60
2.5 LTE10:EPSBearersforConversationalVoice............................ 60
2.5.1 Introductiontothefeature............................................................ 60
2.5.2 Benefits........................................................................................ 61
2.5.3 Requirements...............................................................................61
2.5.3.1 Softwarerequirements................................................................. 61
2.5.3.2 Hardwarerequirements................................................................61
2.5.4 Functionaldescription.................................................................. 62
2.5.4.1 DelaybasedschedulinginDLandinULforbearerswithQCI=1....
62
2.5.4.2 OuterloopdelaytargetcontrolinDL........................................... 63
2.5.4.3 HOLpacketdelayestimationinUL..............................................63
2.5.4.4 ConsiderationofGBRbearerinMACmultiplexinginDL.............63
2.5.4.5 Newschedulertype:exhaustiveFDscheduler............................ 64
2.5.4.6 PacketaggregationinUL/DL....................................................... 64
2.5.4.7 Bearerestablishment................................................................... 64
2.5.4.8 Radioadmissioncontrolthresholds............................................. 65
2.5.5 Systemimpacts............................................................................ 65

4 DN0978033 Issue:02M
LTERL20,FeatureDescriptions

2.5.6 Salesinformation......................................................................... 66
2.5.7 Userinterface...............................................................................66
2.5.7.1 Parameters...................................................................................66
2.5.7.2 Measurementsandcounters........................................................71
2.5.8 Activatingthefeature................................................................... 71
2.6 LTE11:Robustheadercompression............................................ 72
2.6.1 IntroductionToTheFeature......................................................... 72
2.6.2 Benefits........................................................................................ 72
2.6.3 Requirements...............................................................................72
2.6.3.1 SoftwareRequirements................................................................72
2.6.3.2 HardwareRequirements.............................................................. 73
2.6.4 FunctionalDescription..................................................................73
2.6.4.1 ShortDescriptionofROHC.......................................................... 73
2.6.4.2 BearerEstablishment...................................................................74
2.6.4.3 PDCPAdaptationforROHC........................................................ 77
2.6.5 SystemImpacts............................................................................78
2.6.6 SalesInformation......................................................................... 78
2.6.7 UserInterface...............................................................................78
2.6.7.1 Parameters...................................................................................78
2.6.8 ActivatingtheFeature.................................................................. 78
2.7 LTE13:RateCapping(UL/DL)..................................................... 79
2.7.1 Introductiontothefeature............................................................ 79
2.7.2 Benefits........................................................................................ 79
2.7.3 Requirements...............................................................................79
2.7.3.1 Softwarerequirements................................................................. 79
2.7.3.2 Hardwarerequirements................................................................79
2.7.4 Functionaldescription.................................................................. 79
2.7.5 Systemimpacts............................................................................ 81
2.7.6 Salesinformation......................................................................... 81
2.7.7 Userinterface...............................................................................81
2.7.7.1 Parameters...................................................................................81
2.7.7.2 Alarms.......................................................................................... 82
2.7.7.3 Measurementsandcounters........................................................82
2.7.8 Activatingthefeature................................................................... 82
2.8 LTE22:EmergencyCallHandling................................................ 82
2.8.1 IntroductiontotheFeature........................................................... 82
2.8.2 Benefits........................................................................................ 83
2.8.3 Requirements...............................................................................83
2.8.3.1 SoftwareRequirements................................................................83
2.8.3.2 HardwareRequirements.............................................................. 83
2.8.4 FunctionalDescription..................................................................83
2.8.4.1 FunctionalOverview/Details.........................................................83
2.8.4.2 EmergencyCallHandling.............................................................84
2.8.4.3 EmergencyCallSupport.............................................................. 84
2.8.4.3.1 EmergencyCalltrigger.................................................................84
2.8.4.3.2 InitiationofCSFallbackwithRedirectduetoEmergencyCall.... 85

Issue:02M DN0978033 5
LTERL20,FeatureDescriptions

2.8.4.3.3 SelectionoftargetRadioAccessTechnologyforEmergencyCall..
85
2.8.4.3.4 InitiatingUEContextRelease..................................................... 85
2.8.4.3.5 EmergencyCall-UnsuccessfulProcedure..................................85
2.8.4.4 RadioAdmissionControl(RAC)...................................................86
2.8.4.4.1 RACintroducesanewThresholdforEmergencyCallHandling......
86
2.8.4.4.2 Admissionofemergencycallswithhigherthresholdvalue..........86
2.8.4.5 RadioNetworkLayer(RNL)supportforEmergencyCallvia
Redirection................................................................................... 87
2.8.5 SystemImpacts............................................................................87
2.8.5.1 DependenciesBetweenFeatures................................................ 87
2.8.5.2 ImpactsonInterfaces...................................................................87
2.8.5.2.1 ExternalInterfaces....................................................................... 87
2.8.5.3 ImpactsonNetworkandNetworkElementManagementtools... 87
2.8.5.4 ImpactsonSystemPerformanceandCapacity........................... 87
2.8.5.4.1 SystemPerformance....................................................................87
2.8.5.4.2 SystemCapacity.......................................................................... 88
2.8.6 SalesInformation......................................................................... 88
2.8.7 UserInterface...............................................................................88
2.8.7.1 Parameters...................................................................................88
2.8.7.2 MeasurementsandCounters.......................................................89
2.8.8 ActivatingtheFeature.................................................................. 89
2.9 LTE54:Intra-LTEhandoverviaS1............................................... 90
2.9.1 IntroductiontotheFeature........................................................... 90
2.9.2 Benefits........................................................................................ 90
2.9.3 Requirements...............................................................................90
2.9.3.1 SoftwareRequirements................................................................90
2.9.3.2 HardwareRequirements.............................................................. 90
2.9.4 LTE54:Intra-LTEHandoverviaS1...............................................91
2.9.4.1 FunctionalOverview/Details.........................................................91
2.9.4.2 Handovertrigger......................................................................... 91
2.9.4.3 HandoverTargetandModeSelection..........................................92
2.9.4.3.1 HandoverModeselectionforS1basedhandover....................... 92
2.9.4.4 HandoveroverS1interface......................................................... 92
2.9.4.4.1 Handoverdecision....................................................................... 93
2.9.4.4.2 Handoverpreparation.................................................................. 93
2.9.4.4.3 Handoverexecution.................................................................... 93
2.9.4.4.4 Handovercompletion................................................................... 93
2.9.4.5 Dataforwarding...........................................................................93
2.9.4.5.1 Supportofindirectdataforwarding.............................................. 93
2.9.4.5.2 Determinationofwhichbearersaresubjecttodataforwardingat
sourceeNBonHOviaS1............................................................ 94
2.9.4.5.3 ResourceAllocationatTargeteNB.............................................. 94
2.9.4.6 PerformanceCounters................................................................. 94
2.9.5 SystemImpact............................................................................. 94

6 DN0978033 Issue:02M
LTERL20,FeatureDescriptions

2.9.5.1 DependenciesBetweenFeatures................................................ 94
2.9.5.2 ImpactonInterfaces.....................................................................95
2.9.5.2.1 ExternalInterfaces....................................................................... 95
2.9.5.3 ImpactonNetworkandNetworkElementManagementtools..... 95
2.9.5.4 ImpactonSystemPerformanceandCapacity.............................95
2.9.5.4.1 SystemPerformance....................................................................95
2.9.5.4.2 SystemCapacity.......................................................................... 95
2.9.6 SalesInformation......................................................................... 96
2.9.7 UserInterface...............................................................................96
2.9.7.1 Parameters...................................................................................96
2.9.7.2 MeasurementsandCounters.......................................................97
2.10 LTE55:Inter-frequencyhandover.................................................99
2.10.1 IntroductiontotheFeature........................................................... 99
2.10.2 Benefits........................................................................................ 99
2.10.3 Requirements...............................................................................99
2.10.3.1 SoftwareRequirements................................................................99
2.10.3.2 HardwareRequirements............................................................ 100
2.10.4 FunctionalDescription................................................................100
2.10.4.1 FunctionalOverview/Details.......................................................100
2.10.4.2 Inter-frequencyHandoverVariants.............................................100
2.10.4.2.1 RSRPforA3event(BetterCellHO).......................................... 101
2.10.4.2.2 RSRQforA3event(BetterCellHO)..........................................102
2.10.4.2.3 RSRPforA5event(CoverageHO)........................................... 102
2.10.4.2.4 Th2afordeactivationofA3andA5events................................ 102
2.10.4.3 Handovertrigger........................................................................ 102
2.10.4.4 Performancecounters................................................................103
2.10.5 SystemImpact........................................................................... 103
2.10.5.1 DependenciesBetweenFeatures.............................................. 103
2.10.5.2 ImpactonInterfaces...................................................................103
2.10.5.3 ImpactonNetworkandNetworkElementManagementtools... 103
2.10.5.4 ImpactonSystemPerformanceandCapacity...........................103
2.10.6 SalesInformation....................................................................... 104
2.10.7 UserInterface.............................................................................104
2.10.7.1 Parameters.................................................................................104
2.10.7.2 MeasurementsandCounters.....................................................108
2.10.8 ActivatingtheFeature................................................................ 109
2.11 LTE703:DLadaptiveclosedloopMIMOfortwoantennas....... 109
2.11.1 Introductiontothefeature.......................................................... 109
2.11.2 Benefits...................................................................................... 109
2.11.3 Requirements............................................................................. 110
2.11.3.1 SoftwareRequirements.............................................................. 110
2.11.3.2 HardwareRequirements.............................................................110
2.11.4 Functionaldescription.................................................................110
2.11.5 Systemimpacts.......................................................................... 111
2.11.5.1 Dependenciesbetweenfeatures................................................ 111
2.11.6 Salesinformation........................................................................ 111

Issue:02M DN0978033 7
LTERL20,FeatureDescriptions

2.11.7 Userinterface............................................................................. 111


2.11.7.1 Parameters................................................................................. 111
2.11.7.2 Measurementsandcounters...................................................... 113
2.11.8 Activatingandconfiguringthefeature........................................ 113
2.12 LTE562:CSFBtoUTRANorGSMviaredirect.......................... 113
2.12.1 Introductiontothefeature...........................................................113
2.12.2 Benefits.......................................................................................114
2.12.3 Requirements............................................................................. 114
2.12.3.1 SoftwareRequirements.............................................................. 114
2.12.3.2 HardwareRequirements.............................................................114
2.12.4 Functionaldescription.................................................................114
2.12.4.1 Functionaloverview....................................................................115
2.12.4.2 SelectionoftargetRAT...............................................................116
2.12.5 Systemimpacts.......................................................................... 116
2.12.5.1 Impactsonsystemperformanceandcapacity........................... 116
2.12.6 Salesinformation........................................................................116
2.12.7 Userinterface............................................................................. 116
2.12.7.1 Parameters................................................................................. 116
2.12.7.2 Alarms........................................................................................ 118
2.12.7.3 Measurementsandcounters...................................................... 118
2.12.8 Activatingthefeature..................................................................118
2.13 LTE819:DLInter-cellInterferenceGeneration...........................119
2.13.1 IntroductionToTheFeature....................................................... 119
2.13.2 Benefits.......................................................................................119
2.13.3 Requirements............................................................................. 119
2.13.3.1 SoftwareRequirements.............................................................. 119
2.13.3.2 HardwareRequirements.............................................................119
2.13.4 FunctionalDescription................................................................ 119
2.13.4.1 FeatureScope............................................................................120
2.13.4.2 UserScenarios...........................................................................120
2.13.5 SystemImpacts..........................................................................120
2.13.5.1 DependenciesBetweenFeatures.............................................. 120
2.13.5.2 ImpactsonNetworkandNetworkElementManagementtools. 120
2.13.5.3 ImpactsonSystemPerformanceandCapacity......................... 120
2.13.5.3.1 SystemPerformance..................................................................121
2.13.5.3.2 SystemCapacity........................................................................ 121
2.13.6 SalesInformation....................................................................... 121
2.13.7 UserInterface.............................................................................121
2.13.7.1 Parameters.................................................................................121
2.13.7.2 Alarms........................................................................................ 122
2.13.7.3 MeasurementsandCounters.....................................................122
2.13.8 ActivatingtheFeature................................................................ 122
2.14 LTE870:IdleModeMobilityfromLTEtoCDMA/eHRPD............122
2.14.1 IntroductiontotheFeature......................................................... 122
2.14.2 Benefits...................................................................................... 122
2.14.2.1 EndUserBenefits...................................................................... 122

8 DN0978033 Issue:02M
LTERL20,FeatureDescriptions

2.14.2.2 OperatorBenefits....................................................................... 122


2.14.3 Requirements.............................................................................122
2.14.3.1 SoftwareRequirements..............................................................122
2.14.3.2 HardwareRequirements............................................................ 123
2.14.4 FunctionalDescription................................................................123
2.14.5 SalesInformation....................................................................... 123
2.14.6 UserInterface.............................................................................123
2.14.6.1 ManagedObjects....................................................................... 124
2.14.6.2 Parameters.................................................................................124
2.14.6.3 Alarms........................................................................................ 125
2.14.6.4 Measurementsandcounters......................................................125
2.14.7 SystemImpacts..........................................................................125
2.14.7.1 ImpactsonTelecomcontrolplane..............................................125
2.14.8 ActivatingtheFeature................................................................ 125
2.15 LTE914:Gracefulcellshutdown.................................................125
2.15.1 DescriptionofLTE914:GracefulCellShutdown........................ 125
2.15.1.1 Benefits...................................................................................... 125
2.15.1.2 Requirements.............................................................................125
2.15.1.3 Functionaldescription................................................................ 126
2.15.1.4 Systemimpact............................................................................128
2.15.1.5 LTE914:Gracefulcellshutdownmanagementdata.................. 129
2.15.1.6 Salesinformation....................................................................... 129
2.15.2 ActivatingLTE914:GracefulCellShutdown...............................129
2.15.3 DeactivatingLTE914:GracefulCellShutdown.......................... 130

3 TransportandTransmissionFeatures........................................132
3.1 LTE140:EthernetOAM.............................................................. 132
3.1.1 Introductiontothefeature.......................................................... 132
3.1.2 Benefits...................................................................................... 132
3.1.2.1 Enduserbenefits....................................................................... 132
3.1.2.2 Operatorbenefits....................................................................... 132
3.1.3 Requirements.............................................................................132
3.1.3.1 Softwarerequirements............................................................... 132
3.1.3.2 Hardwarerequirements..............................................................133
3.1.4 Functionaldescription................................................................ 133
3.1.4.1 LinkLayerOAM......................................................................... 133
3.1.4.2 ServiceOAM.............................................................................. 134
3.1.4.2.1 EthernetContinuityCheckandEthernetRemoteDefectIndication
................................................................................................... 136
3.1.4.2.2 EthernetAlarmIndicationSignal................................................136
3.1.4.2.3 EthernetLoopback..................................................................... 137
3.1.4.2.4 EthernetLinkTrace.................................................................... 138
3.1.5 Salesinformation....................................................................... 138
3.1.6 Userinterface.............................................................................138
3.1.6.1 Parameters.................................................................................138
3.1.6.2 Alarms........................................................................................ 142

Issue:02M DN0978033 9
LTERL20,FeatureDescriptions

3.1.6.3 Measurementsandcounters......................................................143
3.1.7 Activatingandconfiguringthefeature........................................143
3.1.8 Abbreviations............................................................................. 143
3.1.8.1 0Z........................................................................................... 143
3.2 LTE491:FlexiPacketRadioConnectivity................................... 144
3.2.1 Introductiontothefeature.......................................................... 144
3.2.2 Benefits...................................................................................... 145
3.2.3 Requirements.............................................................................145
3.2.3.1 Softwarerequirements............................................................... 145
3.2.3.2 Hardwarerequirements..............................................................145
3.2.4 Functionaldescription................................................................ 145
3.2.4.1 FPRmanagementusesFPRPayloadChannel.........................146
3.2.4.2 FPRmanagementusesseparateRadioChannel......................147
3.2.5 Salesinformation....................................................................... 147
3.2.6 Userinterface.............................................................................147
3.2.6.1 Parameters.................................................................................148
3.2.6.2 Alarms........................................................................................ 148
3.2.6.3 Measurementsandcounters......................................................148
3.2.7 ActivatingandConfiguringtheFeature......................................148
3.2.8 Abbreviations............................................................................. 148
3.2.8.1 0Z........................................................................................... 148
3.3 LTE564:IPseconFTIB.............................................................. 149
3.3.1 Introductiontothefeature.......................................................... 149
3.3.2 Benefits...................................................................................... 149
3.3.3 Requirements.............................................................................149
3.3.3.1 Interdependenciesbetweenfeatures......................................... 149
3.3.3.2 Softwarerequirements............................................................... 149
3.3.3.3 Hardwarerequirements..............................................................149
3.3.4 Functionaldescription................................................................ 149
3.3.5 Salesinformation....................................................................... 150
3.3.6 Userinterface.............................................................................150
3.3.6.1 Parameters.................................................................................150
3.3.6.2 Alarms........................................................................................ 150
3.3.6.3 Measurementsandcounters......................................................150
3.3.7 Abbreviations............................................................................. 150
3.3.7.1 0Z........................................................................................... 150
3.4 LTE592:LinkSupervisionwithBFD........................................... 150
3.4.1 Introductiontothefeature.......................................................... 150
3.4.2 Benefits...................................................................................... 150
3.4.3 Requirements.............................................................................150
3.4.3.1 Softwarerequirements............................................................... 151
3.4.3.2 Hardwarerequirements..............................................................151
3.4.4 Functionaldescription................................................................ 151
3.4.5 Salesinformation....................................................................... 152
3.4.6 Userinterface.............................................................................152
3.4.6.1 Parameters.................................................................................152

10 DN0978033 Issue:02M
LTERL20,FeatureDescriptions

3.4.6.2 Alarms........................................................................................ 156


3.4.6.3 Measurementsandcounters......................................................157
3.4.7 ActivatingandConfiguringtheFeature......................................157
3.4.8 Abbreviations............................................................................. 157
3.4.8.1 0Z........................................................................................... 157
3.5 LTE649:QoSAwareEthernetSwitching....................................157
3.5.1 Introductiontothefeature.......................................................... 157
3.5.2 Benefits...................................................................................... 158
3.5.3 Requirements.............................................................................158
3.5.3.1 Interdependenciesbetweenfeatures......................................... 158
3.5.3.2 Softwarerequirements............................................................... 159
3.5.3.3 Hardwarerequirements..............................................................159
3.5.4 Functionaldescription................................................................ 159
3.5.4.1 VLANawareswitching............................................................... 161
3.5.4.2 VLANunawareswitching........................................................... 162
3.5.4.3 SchedulingandshapingforEthernetQoSswitching................. 162
3.5.5 Salesinformation....................................................................... 164
3.5.6 Userinterface.............................................................................164
3.5.6.1 Parameters.................................................................................164
3.5.6.2 Alarms........................................................................................ 174
3.5.6.3 Measurementsandcounters......................................................174
3.5.7 ActivatingandConfiguringtheFeature......................................175
3.5.8 Abbreviations............................................................................. 175
3.5.8.1 0Z........................................................................................... 175
3.6 LTE775:SCTPMulti-homing(MME).......................................... 176
3.6.1 Introductiontothefeature.......................................................... 176
3.6.2 Benefits...................................................................................... 176
3.6.3 Requirements.............................................................................176
3.6.3.1 Softwarerequirements............................................................... 176
3.6.3.2 Hardwarerequirements..............................................................177
3.6.4 Functionaldescription................................................................ 177
3.6.5 Salesinformation....................................................................... 178
3.6.6 Userinterface.............................................................................178
3.6.6.1 Parameters.................................................................................178
3.6.6.2 Alarms........................................................................................ 179
3.6.6.3 Measurementsandcounters......................................................179
3.6.7 Abbreviations............................................................................. 179
3.6.7.1 0Z........................................................................................... 179

4 Operabilityfeatures.................................................................... 180
4.1 LTE163:SubscriberandEquipmentTrace................................ 180
4.1.1 Benefits...................................................................................... 180
4.1.2 Requirements.............................................................................180
4.1.3 Functionaldescription................................................................ 180
4.1.4 Systemimpact............................................................................185
4.1.5 Salesinformation....................................................................... 185

Issue:02M DN0978033 11
LTERL20,FeatureDescriptions

4.1.6 Userinterface.............................................................................185
4.2 LTE185:SystemUpgrade.......................................................... 186
4.2.1 Introductiontothefeature.......................................................... 186
4.2.2 Benefits...................................................................................... 186
4.2.3 Requirements.............................................................................187
4.2.3.1 Softwarerequirements............................................................... 187
4.2.3.2 Hardwarerequirements..............................................................187
4.2.4 Functionaldescription................................................................ 187
4.2.4.1 LTEupgradeusecases..............................................................189
4.2.5 Systemimpacts..........................................................................195
4.2.5.1 Impactsoninterfaces................................................................. 195
4.2.5.2 Impactonnetworkelements...................................................... 196
4.2.6 Salesinformation....................................................................... 196
4.2.7 Userinterface.............................................................................196
4.2.7.1 Parameters.................................................................................196
4.2.7.2 Alarms........................................................................................ 196
4.2.7.3 Measurementsandcounters......................................................196
4.2.8 Systemresponsestofailures..................................................... 196
4.2.9 Activatingandconfiguringthefeature........................................197
4.3 LTE433:CellTrace.....................................................................198
4.3.1 Benefits...................................................................................... 198
4.3.2 Requirements.............................................................................198
4.3.3 Functionaldescription................................................................ 198
4.3.4 Systemimpact............................................................................203
4.3.5 Salesinformation....................................................................... 203
4.3.6 Userinterface.............................................................................203
4.4 LTE475:AutomaticiOMSResiliency..........................................205
4.4.1 LTE475:AutomaticiOMSResiliency-introduction....................205
4.4.2 Benefits...................................................................................... 206
4.4.3 FunctionalDescription................................................................206
4.4.4 SystemImpacts..........................................................................208
4.4.4.1 InterdependenciesbetweenFeatures........................................208
4.4.5 ManagedObjects....................................................................... 208
4.4.5.1 Parameters.................................................................................208
4.5 LTE521:SecurityonEthernetportsonFCM/FSM2................... 209
4.5.1 Benefits...................................................................................... 209
4.5.2 Requirements.............................................................................210
4.5.3 Functionaldescription................................................................ 210
4.5.4 Systemimpact............................................................................ 211
4.5.5 LTE521:SecurityforEthernetportsonFCM/FSM2management
data............................................................................................ 212
4.5.6 Salesinformation....................................................................... 212
4.6 LTE492:ANR............................................................................. 212
4.6.1 LTE492:ANR............................................................................. 212
4.6.1.1 Benefits...................................................................................... 213
4.6.1.2 Requirements.............................................................................213

12 DN0978033 Issue:02M
LTERL20,FeatureDescriptions

4.6.1.2.1 SoftwareRequirements..............................................................213
4.6.1.2.2 HardwareRequirements............................................................ 213
4.6.1.3 LTE492:AutomaticNeighborRelation(ANR)............................ 214
4.6.1.3.1 Prerequisites.............................................................................. 214
4.6.1.3.2 Functionaloverview/details........................................................ 214
4.6.1.3.2.1 X2linkmanagement.................................................................. 216
4.6.1.3.2.2 NetActOptimizer:Neighborevaluationprocedure.....................218
4.6.1.3.2.3 NetActConfigurator:automatedneighborsiteIPconnectivity
configurationcompletion............................................................ 219
4.6.1.3.2.4 Usecases.................................................................................. 220
4.6.1.4 SystemImpacts..........................................................................220
4.6.1.4.1 InterdependenciesbetweenFeatures........................................220
4.6.1.5 SalesInformation....................................................................... 222
4.6.1.6 UserInterface.............................................................................222
4.6.1.6.1 Parameters.................................................................................222
4.6.1.6.2 Alarms........................................................................................ 224
4.6.1.6.3 MeasurementsandCounters.....................................................224
4.6.1.7 ActivatingandConfiguringtheFeature......................................225
4.7 LTE550:RadioParameterOnlineChangeable.......................... 225
4.7.1 Benefits...................................................................................... 225
4.7.2 Requirements.............................................................................225
4.7.3 Systemimpact............................................................................225
4.7.4 LTE550:RadioParameterOnlineChangeablemanagementdata..
226
4.7.5 Salesinformation....................................................................... 226
4.8 LTE559:SWMonitoringModuleforLTE.................................... 227
4.8.1 Introductiontothefeature.......................................................... 227
4.8.2 Benefits...................................................................................... 227
4.8.2.1 Enduserbenefits....................................................................... 227
4.8.2.2 Operatorbenefits....................................................................... 227
4.8.3 Requirements.............................................................................227
4.8.3.1 Softwarerequirements............................................................... 227
4.8.3.2 Hardwarerequirements..............................................................228
4.8.4 Functionaldescription................................................................ 228
4.8.4.1 Functionaloverview/details........................................................ 228
4.8.5 Systemimpacts..........................................................................229
4.8.5.1 Interdependenciesbetweenfeatures......................................... 229
4.8.5.2 Impactsoninterfaces................................................................. 229
4.8.5.3 Impactsonnetworkandnetworkelementmanagementtools... 229
4.8.5.4 Impactsonsystemperformanceandcapacity...........................229
4.8.6 Salesinformation....................................................................... 229
4.8.7 Userinterface.............................................................................229
4.8.7.1 Parameters.................................................................................229
4.8.8 Activatingandconfiguringthefeature........................................229
4.9 LTE667:LTEUserEventLogManagement...............................229
4.9.1 Introductiontothefeature.......................................................... 229

Issue:02M DN0978033 13
LTERL20,FeatureDescriptions

4.9.2 Benefits...................................................................................... 230


4.9.3 Requirements.............................................................................230
4.9.5 Systemimpact............................................................................230
4.9.6 Salesinformation....................................................................... 230
4.9.7 LTE667:LTEUserEventLogManagementmanagementdata.230
4.9.8 Activatingthefeature................................................................. 231
4.10 LTE796:iOMSConnectivityIncrease.........................................231
4.10.1 IntroductiontotheFeature......................................................... 231
4.10.2 Benefits...................................................................................... 231
4.10.3 Requirements.............................................................................231
4.10.3.1 SoftwareRequirements..............................................................231
4.10.4 FunctionalDescription................................................................231
4.10.5 SystemImpacts..........................................................................231
4.10.5.1 InterdependenciesbetweenFeatures........................................232
4.10.6 SalesInformation....................................................................... 232
4.11 LTE830:LTEAutomaticLock..................................................... 232
4.11.1 IntroductiontotheFeature......................................................... 232
4.11.2 Benefits...................................................................................... 232
4.11.3 Requirements.............................................................................232
4.11.3.1 SoftwareRequirements..............................................................232
4.11.4 FunctionalDescription................................................................232
4.11.5 Parameters.................................................................................234

5 PerformanceMonitoringFeaturesinRL20................................ 235
5.1 LTE805:PMCounterCapacityI.................................................235
5.1.1 Benefits...................................................................................... 235
5.1.2 Requirements.............................................................................235
5.1.3 Functionaldescription................................................................ 235
5.1.4 Systemimpact............................................................................236
5.1.5 Salesinformation....................................................................... 236
5.1.6 Userinterface.............................................................................236

6 FlexiMultiradioBTSLTESiteSolutionfeatures.........................239
6.1 LTE87:Flexi3-sectorRFModule850........................................239
6.1.1 Introductiontothefeature.......................................................... 239
6.1.2 Benefits...................................................................................... 239
6.1.3 Requirements.............................................................................239
6.1.3.1 Softwarerequirements............................................................... 239
6.1.4 Functionaldescription................................................................ 240
6.1.5 Salesinformation....................................................................... 240
6.1.6 Activatingthefeature................................................................ 240
6.2 LTE101:Flexi3-sectorRFModule1800....................................240
6.2.1 Introductiontothefeature.......................................................... 241
6.2.2 Benefits...................................................................................... 241
6.2.3 Requirements.............................................................................241
6.2.3.1 Softwarerequirements............................................................... 241

14 DN0978033 Issue:02M
LTERL20,FeatureDescriptions

6.2.4 Functionaldescription................................................................ 242


6.2.5 Salesinformation....................................................................... 242
6.2.6 Activatingthefeature................................................................ 242
6.3 LTE103:FlexiRRH2TX730...................................................... 242
6.3.1 Introductiontothefeature.......................................................... 242
6.3.2 Benefits...................................................................................... 243
6.3.3 Requirements.............................................................................243
6.3.3.1 Softwarerequirements............................................................... 243
6.3.4 Functionaldescription................................................................ 243
6.3.5 Salesinformation....................................................................... 244
6.3.6 Activatingthefeature................................................................ 244
6.4 LTE104:FlexiRRH2TX1800.................................................... 244
6.4.1 Introductiontothefeature.......................................................... 244
6.4.2 Benefits...................................................................................... 244
6.4.3 Requirements.............................................................................244
6.4.3.1 Softwarerequirements............................................................... 244
6.4.4 Functionaldescription................................................................ 245
6.4.5 Salesinformation....................................................................... 245
6.4.6 Activatingthefeature................................................................ 245
6.5 LTE113:CellBandwidth-15MHz..............................................245
6.5.1 Introductiontothefeature.......................................................... 246
6.5.2 Benefits...................................................................................... 246
6.5.3 Requirements.............................................................................246
6.5.3.1 Softwarerequirements............................................................... 246
6.5.3.2 Hardwarerequirements..............................................................246
6.5.4 Functionaldescription................................................................ 246
6.5.5 Salesinformation....................................................................... 247
6.5.6 Activatingthefeature................................................................. 247
6.6 LTE447:SWsupportforRFsharingGSM-LTE.........................247
6.6.1 Introductiontothefeature.......................................................... 247
6.6.2 Benefits...................................................................................... 247
6.6.3 Requirements.............................................................................247
6.6.3.1 Softwarerequirements............................................................... 247
6.6.3.2 Hardwarerequirements..............................................................248
6.6.4 Functionaldescription................................................................ 248
6.6.5 Salesinformation....................................................................... 249
6.6.6 Activatingthefeature................................................................. 249
6.7 LTE1102:FFCCTRSExternalFilterforFXCA.......................... 250
6.7.1 Benefits...................................................................................... 250
6.7.2 Requirements.............................................................................250
6.7.3 Functionaldescription................................................................ 250
6.7.4 Systemimpacts..........................................................................252
6.7.5 LTE1102:FFCCTRSExternalFilterforFXCAmanagementdata..
252
6.7.6 Salesinformation....................................................................... 253

Issue:02M DN0978033 15
LTERL20,FeatureDescriptions

List of Figures
Figure1 MMEselectionprocedure...................................................................26
Figure2 EPSbearerestablishmentbyS1AP:Initialcontextsetupprocedure
(Attach)............................................................................................... 33
Figure3 EPSbearerestablishmentbyS1AP:Initialcontextsetupprocedure
(Service)............................................................................................. 34
Figure4 EPSbearerestablishmentbyS1AP:E-RABsetuprequest................ 35
Figure5 EPSbearerreleaseprocedurebyS1AP:E-RABreleaseprocedure......
35
Figure6 EPSbearerestablishmentbyS1AP:E-RABsetuprequest............... 65
Figure7 PrincipleofROHC.............................................................................. 73
Figure8 CompressorStates.............................................................................74
Figure9 DecompressorStates......................................................................... 74
Figure10 EPSBearerEstablishmentProcedurebyS1AP:InitialContextSetup
Procedure(Attach)............................................................................. 75
Figure11 EPSBearerEstablishmentProcedurebyS1AP:InitialContextSetup
Procedure(ServiceRequest)............................................................. 76
Figure12 EPSBearerEstablishmentProcedurebyS1AP:E-RABSetup
Procedure........................................................................................... 77
Figure13 UE-AMBRModificationProcedure..................................................... 81
Figure14 MessagesequenceandtimedelayduringCSFBredirection........... 115
Figure15 Txpowerlevelsduringgracefulcellshutdown................................. 127
Figure16 ServiceOAMoverview..................................................................... 135
Figure17 EthernetContinuityCheckandEthernetRemoteDefectIndication.136
Figure18 EthernetAlarmIndicationSignal...................................................... 137
Figure19 EthernetLoopback........................................................................... 138
Figure20 EthernetLinkTrace.......................................................................... 138
Figure21 FlexiPacketRadioConnectivitysolution...........................................146
Figure22 FPRmanagementdataforwarding...................................................147
Figure23 QoSawareEthernetswitching......................................................... 160
Figure24 Chainingconcept..............................................................................161
Figure25 TheEthernetschedulingandshaping.............................................. 162
Figure26 QoSschedulingforswitchedEthernettransportinterfaces-examplefor
FTLBandFTIB................................................................................. 163
Figure27 Signallingtransportstackformulti-homedMMES1interface..........177
Figure28 Multi-homedMME............................................................................ 178
Figure29 Subscribetracegeneralarchitecture................................................182
Figure30 TracefilestransferbetweenNetActandiOMS.................................184
Figure31 Topdownupgradeapproach............................................................ 188
Figure32 Celltracearchitecture.......................................................................200
Figure33 TracefilestransferbetweenNetActandiOMS.................................202

16 DN0978033 Issue:02M
LTERL20,FeatureDescriptions

Figure34 LTE492:ANR....................................................................................214
Figure35 FeaturemonitoringforLTE............................................................... 228
Figure36 ConceptofGSMandLTEconcurrentmode.....................................248
Figure37 IsometricviewoftheFFCC.............................................................. 251
Figure38 FrontviewoftheFFCC.................................................................... 252

Issue:02M DN0978033 17
LTERL20,FeatureDescriptions

List of Tables
Table1 RL20Features-notsupportedbyFlexiZoneMicro.......................... 23
Table2 Softwarerequirementsfordifferentnetworkelements....................... 24
Table3 ParametersforLTE2:S1Flex............................................................ 27
Table4 Softwarerequirementsfordifferentnetworkelements....................... 28
Table5 Softwarerequirementsfordifferentnetworkelements....................... 29
Table6 Salesinformation................................................................................31
Table7 Softwarerequirementsfordifferentnetworkelements....................... 31
Table8 CountersmaintainedbyRAC............................................................. 36
Table9 ParametersfortheLTE7:SupportofmultipleEPSbearer.................. 37
Table10 CountersforLTE7:SupportofmultipleEPSbearer........................... 38
Table11 Softwarerequirementsfordifferentnetworkelements....................... 41
Table12 ParametersfortheLTE9:ServiceDifferentiation............................... 44
Table13 ParametersforAMRLCPollBytestructure....................................... 44
Table14 ParametersforQCITranslationTablestructure................................. 46
Table15 ParametersforprofilesofRLC........................................................... 53
Table16 ParametersforprofilesofPDCP........................................................ 57
Table17 CountersfortheLTE9:Servicedifferentiation.................................... 59
Table18 Softwarerequirementsfordifferentnetworkelements....................... 61
Table19 ParametersfortheLTE10:EPSbearersforconversationalvoice
feature................................................................................................ 66
Table20 CountersfortheLTE10:EPSbearersforconversationalvoicefeature.
71
Table21 Softwarerequirementsfordifferentnetworkelements....................... 72
Table22 ModesofROHC................................................................................. 74
Table23 ParametersfortheLTE11:RobustHeaderCompression.................. 78
Table24 Softwarerequirementsfordifferentnetworkelements....................... 79
Table25 ParametersfortheLTE13:RateCappingUL..................................... 81
Table26 ParametersfortheLTE13:RateCappingDL..................................... 82
Table27 Softwarerequirementsfordifferentnetworkelements....................... 83
Table28 Hardwarerequirementsfordifferentnetworkelements......................83
Table29 Salesinformation................................................................................88
Table30 ParametersfortheLTE22:EmergencyCallHandling........................ 88
Table31 CountersfortheLTE22:EmergencyCallHandling............................ 89
Table32 Softwarerequirementsfordifferentnetworkelements....................... 90
Table33 Hardwarerequirementsfordifferentnetworkelements......................90
Table34 Salesinformation................................................................................96
Table35 ParametersfortheLTE54:IntraLTEHandoverviaS1...................... 96
Table36 CountersforLTE54:IntraLTEHandoverviaS1............................... 97
Table37 Softwarerequirementsfordifferentnetworkelements....................... 99

18 DN0978033 Issue:02M
LTERL20,FeatureDescriptions

Table38 Hardwarerequirementsfordifferentnetworkelements....................100
Table39 Th1andTh2InterFreqarethresholdssetbyO&M.......................... 101
Table40 Th2aInterFreqthresholdsetbyO&M.............................................. 102
Table41 Salesinformation..............................................................................104
Table42 ParametersfortheLTE55:LTEInter-frequencyHandover.............. 104
Table43 CountersfortheLTE55:LTEInter-frequencyHandover.................. 109
Table44 Softwarerequirementsfordifferentnetworkelements..................... 110
Table45 Hardwarerequirementsfordifferentnetworkelements.................... 110
Table46 Salesinformation.............................................................................. 111
Table47 ParametersfortheLTE703:DLadaptiveclosedloopMIMOfortwo
antennas........................................................................................... 112
Table48 CountersfortheLTE703:DLadaptiveclosedloopMIMOfortwo
antennas........................................................................................... 113
Table49 Softwarerequirementsfordifferentnetworkelements..................... 114
Table50 ParametersfortheLTE562:CSFBtoUTRANorGSMviaredirect.......
117
Table51 CountersfortheLTE562:CSFBtoUTRANorGSMviaredirect.......118
Table52 Softwarerequirementsfordifferentnetworkelements..................... 119
Table53 ParametersfortheLTE819DownlinkInter-cellInterferencegeneration
..........................................................................................................121
Table54 Softwarerequirementsfordifferentnetworkelements..................... 122
Table55 ParametersforLTE870:IdleModeMobilityfromLTEto
CDMA/eHRPD..................................................................................124
Table56 Softwarerequirements..................................................................... 126
Table57 Configurationofparametersforthegracefulcellshutdownprocedure..
127
Table58 Minimumoutputpowervaluesforvariousradiounits...................... 128
Table59 Relatedexistingparameters.............................................................129
Table60 Salesinformation..............................................................................129
Table61 Softwarerequirementsfordifferentnetworkelements..................... 133
Table62 L-OAMcapabilities........................................................................... 133
Table63 ParametersforLTE140:EthernetOAM............................................139
Table64 AlarmsforLTE140:EthernetOAM................................................... 142
Table65 Softwarerequirementsfordifferentnetworkelements..................... 145
Table66 Softwarerequirementsfordifferentnetworkelements..................... 149
Table67 Softwarerequirementsfordifferentnetworkelements..................... 151
Table68 ParametersforLTE592:LinkSupervisionwithBFD........................ 152
Table69 AlarmsforLTE592:LinkSupervisionwithBFD................................ 156
Table70 Softwarerequirementsfordifferentnetworkelements..................... 159
Table71 ParametersforLTE649:QoSAwareSwitching................................165
Table72 MesurementandcountersforLTE649:QoSAwareSwitching.........174
Table73 Softwarerequirementsfordifferentnetworkelements..................... 177

Issue:02M DN0978033 19
LTERL20,FeatureDescriptions

Table74 ParametersforLTE775:SCTPMulti-Homing...................................179
Table75 AlarmsforLTE775:SCTPMulti-Homing.......................................... 179
Table76 Softwarerequirements..................................................................... 180
Table77 Salesinformation..............................................................................185
Table78 Relatedalarms................................................................................. 185
Table79 Newparameters............................................................................... 186
Table80 Softwarerequirementsfordifferentnetworkelements..................... 187
Table81 AlarmsfortheLTE185:SystemUpgradefeature............................. 196
Table82 Softwarerequirements..................................................................... 198
Table83 Salesinformation..............................................................................203
Table84 Relatedalarms................................................................................. 203
Table85 Newparameters............................................................................... 204
Table86 ParametersfortheLTE475:AutomaticiOMSResiliency................. 208
Table87 Softwarerequirements..................................................................... 210
Table88 Newparameters............................................................................... 212
Table89 Salesinformation..............................................................................212
Table90 Softwarerequirementsfordifferentnetworkelements..................... 213
Table91 Interdependenciesbetweenfeatures............................................... 220
Table92 Salesinformation..............................................................................222
Table93 ParametersforLTE492:AutomaticNeighborRelation.....................222
Table94 Softwarerequirements..................................................................... 225
Table95 Salesinformation..............................................................................226
Table96 Softwarerequirementsfordifferentnetworkelements..................... 227
Table97 Softwarerequirementsfordifferentnetworkelements..................... 230
Table98 Softwarerequirements..................................................................... 231
Table99 Softwarerequirements..................................................................... 232
Table100 ParametersfortheLTE830:LTEAutomaticLockfeature................ 234
Table101 Softwarerequirements..................................................................... 235
Table102 Salesinformation..............................................................................236
Table103 Newcounters....................................................................................236
Table104 Softwarerequirementsfordifferentnetworkelements..................... 239
Table105 Salesinformation..............................................................................240
Table106 Softwarerequirementsfordifferentnetworkelements..................... 241
Table107 Salesinformation..............................................................................242
Table108 Softwarerequirementsfordifferentnetworkelements..................... 243
Table109 Salesinformation..............................................................................244
Table110 Softwarerequirementsfordifferentnetworkelements..................... 244
Table111 Salesinformation..............................................................................245
Table112 Softwarerequirementsfordifferentnetworkelements..................... 246
Table113 Salesinformation..............................................................................247

20 DN0978033 Issue:02M
LTERL20,FeatureDescriptions

Table114 Softwarerequirementsfordifferentnetworkelements..................... 248


Table115 Salesinformation..............................................................................249
Table116 Softwarerequirements..................................................................... 250
Table117 Salesinformation..............................................................................253

Issue:02M DN0978033 21

Summaryofchanges LTERL20,FeatureDescriptions

Summary of changes
Changes between 02L (2016-01-26, RL30) and 02M (2016-05-23, RL70)
Thefollowingfeaturedescriptionhasbeenupdated:

LTE7:SupportofmultipleEPSbearer

Changes between 02K (2015-06-19, RL30) and 02L (2016-01-26, RL30)


Thefollowingfeaturedescriptionhasbeenupdated:

LTE2:S1Flex

Changes between 02J (2015-03-15, RL30) and 02K (2015-06-19, RL30)


Thefollowingfeaturedescriptionhasbeenupdated:

LTE492:AutomaticNeighborRelation

22 DN0978033 Issue:02M

LTERL20,FeatureDescriptions RL20Features-notsupportedbyFlexiZoneMicro

1 RL20 Features - not supported by Flexi Zone


Micro
ThefollowingfeaturesarenotsupportedbyFlexiZoneMicro:

Table1 RL20Features-notsupportedbyFlexiZoneMicro
Features Category
LTE87:FXCAFlexi3-sectorRFModule850 BTS
LTE101:FXEAFlexi3-sectorRFModule1800 BTS
LTE103:FRLBFlexiRRH2TX730 BTS
LTE104:FHEAFlexiRRH2TX1800 BTS
LTE185:SystemUpgrade Operability
LTE447:SWsupportforRFsharingGSM-LTE BTS
LTE491:FlexiPacketRadioConnectivity Transport
LTE521:SecurityforEthernetportsonFCM/FSM2 Operabiliy
LTE564:IPSeconFTIB Operabiliy
LTE677:FRNA_BFlexi1600MHzRFsolution BTS
LTE1102:FFCCTRSExternalFilterforFXCA BTS

Issue:02M DN0978033 23

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2 Radio resource management and telecom


features

2.1 LTE2: S1 Flex


2.1.1 Introduction to the feature
TheS1FlexallowstheeNBtoestablishmultipleS1links.TheFlexiMultiradioBTScan
beconnectedtoamaximumof16MMEs.
AloadbalancingalgorithmisusedtobalancetheloadbetweentheMMEs.UEsentering
theMMEpoolaredistributedtothedifferentMMEs.

2.1.2 Benefits
TheS1Flexfeatureprovidesnetworkredundancyandtrafficloadsharing.
WithS1FlextheeNBisallowedtoconnecttoamaximumof16MMEs.Theoperator
canincreasetheoverallnetworkavailability.

2.1.3 Requirements

2.1.3.1 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

Table2 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20;RL15TD

eNodeB LBTS2.0;TD-LBTS1.0

MME NS10CD2;NS10CD4

SAEGW NG10CD4

UE 3GPPrelease8

NetAct

2.1.3.2 Hardware requirements

ThisfeaturerequiresFlexiSystemmoduleswhichsupportLTE.

24 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.1.4 Functional description


TheeNBsupportsmultipleS1linkswhenfeatureS1Flexisactivated.

2.1.4.1 S1 interface

WithS1Flexsupport,theeNBmaybeconnectedtoamaximumof16MMEs.Whenan
associatedIPaddressfortheMMEisavailable,theeNBconsidersthatspecificMMEas
allowed.IfanadditionalMMEbecomesconfigured,eNBperformstheS1linkactivation
procedureforthisMME.WhentheMMEisremovedfromthesetofconfiguredMMEs,
theeNBperformstheS1linkdeactivationprocedureforthisMME.AnS1interface
modificationoccurseachtimewhenthesetofavailableMMEschanges.
IftheS1Flexfeatureisdeactivated,theeNBperformstheS1linkdeactivation
procedureforeachMMEexceptfortheMMEthatisconsideredasthemainMME.The
mainMMEisconfiguredinLNMME-0.
SCTP associations
TheeNBstarts/terminatesallassociationstowardsanyMMEatoneeNBSCTP
endpoint.ThatmeansthattheeNBsupportsatoneS1-MMESCTPendpointupto16
SCTPassociationstowardspeerMMEs(oneSCTPassociationforeachMME).Each
MMEpeerendpointisidentifiedwiththepeerMMEprimaryIPaddress.
WhentheS1Flexisdeactivated,theeNBkeepsonlytheSCTPassociationtowardsthe
mainMME.
FormoreinformationonSCTP,seesubchapterSCTPlayerinLTEDatapath
Management.

2.1.4.2 MME selection

DuringtheUEconnectionestablishment,eNBselectsMMEfromthesetofactiveMMEs.
Thechoiceisbasedon:

PLMNIDs(MMEsupportofPLMNs,whichUEwantstoconnectto)
registeredMMEvalue(availableiftheUEhasalreadyregisteredwithaMME)
SAETemporaryMobileSubscriberIdentity(S-TMSI)

ValueofregisteredMMEparameterisprovidedbyoneofthefollowingmessages:

RRCCONNECTIONSETUPCOMPLETE
RRCCONNECTIONREQUEST,withintheoptionalS-TMSI

TheFigure1:MMEselectionprocedureprovidesanoverviewofMMEselection
procedureaftertheRRCconnectionsetupiscompleted.

Issue:02M DN0978033 25

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Figure1 MMEselectionprocedure

RRCConnectionSetupComplete

DeriveselectedPLMNidentity,
S-TMSIandregisteredMME

S-TMSIpresent SearchforMMECodeofS-TMSI
insetofMMECsofLTERAT
S-TMSInotpresent

registeredMMEnotinmessage

SearchforregisteredMMEinsetof SearchforselectedPLMNidentityinsetof
servedGUMMEIsofallactiveMMEs servedPLMNidentitiesofallactiveMMEs
MMEnotfound

SeveralMMEfound
registeredMMEinRRCmessage

MMEfoundinset

MMEfoundinset

MMEfoundinset SelectedPLMNnot
servedbyMME
MMEnotfound
PerformLoadbalancing

SelectedPLMNservedbyMME

MMEselected
MMEselected MMEselected MMEselected ReleaseRRCConnection

2.1.4.2.1 Load balancing

Aload-balancingalgorithmbalancestheloadbetweenMMEs.
UEsenteringtheMMEpoolaredistributedtodifferentMMEswithprobabilitiesthat
correspondtotheassignedweights.
TheeNBperformstheS1connectionsetupload-balancingamongtheMMEs.Only
activeMMEsforwhichthePLMNIDisoneoftheservedPLMNsareconsidered.
SelectionisbasedonweightinginformationprovidedbyeachMMEduringtheS1setup.
RelativeMMEcapacityisincludedinS1AP:S1SETUPRESPONSEmessage.
Algorithmisre-initializedbythefollowingtriggers:

successfulS1setup
S1reset
S1-MMEfailure

2.1.5 Sales information


ThisfeaturebelongstotheApplicationSoftware(ASW)productstructureclass.

26 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.1.6 User interface

2.1.6.1 Parameters

ThefollowingtableshowstheparametersimplementedforthefeatureLTE2:S1Flex.

Table3 ParametersforLTE2:S1Flex

Name Object Description Range Default

actS1Flex LNBTS FeatureactivationflagforLTE2:S1Flex. disabled(0) 1


enabled(1)

ipAddrPrim LNMME TransportnetworkIPv4/v6addressoftheMobility 7...45characters -


ManagementEntity(MME)primaryinterface

administrativeState LNMME AdministrativestateoftheLNMMES1link unlocked(1) unlocked


locked(3)

lnMmeId LNMME SettingofLTEmobilitymanagementidentifier 0...31 -

transportNwId LNMME SettingofTransportnetworkidentifier 0...1 -

2.1.6.2 Alarms

TherearenoAlarmsrelatedtothisfeature.

2.1.6.3 Measurements and counters

Therearenomeasurementsandcountersrelatedtothisfeature.

2.1.7 Activating and configuring the feature


NotethatfeatureactivationflagforLTE2:S1Flex,activatesalsoLTE4:Multi-Operator
CoreNetworkfeature.
Foractivatingandconfiguringthefeature,seeFeatureActivationDocumentation

2.1.8 Abbreviations

2.1.8.1 0Z

GUMMEI

GlobalUniqueMobilityManagementEntityIdentifier

Issue:02M DN0978033 27

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

PLMN

PublicLandMobileNetwork

RAT

RadioAccessTechnology

S-TMSI

SAETemporaryMobileSubscriberIdentity

2.2 LTE4: RAN Sharing


2.2.1 Introduction to the feature
TheFlexiMultiradioBTScanbeconnectedsimultaneouslytotheEPCsofsixdifferent
operators.ThismeansthattheLTEE-UTRANcanbesharedbetweenmobilenetwork
operators.DifferentcorenetworkscanbeconnectedtothecommonsharedeNBs.

2.2.2 Benefits
TheoperatorsareabletosharetheresourcesofoneFlexiMultiradioBTS.

2.2.3 Requirements

2.2.3.1 Interdependencies between features

FeatureLTE2:S1Flexneedstobeactivated.

2.2.3.2 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

Table4 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL40

FlexiMultiradioBTS LBTS2.0

FlexiMultiradio10BTS LBTS4.0

MME

28 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table4 Softwarerequirementsfordifferentnetworkelements(Cont.)

Network element Required software release

SAEGW

UE 3GPPrelease8

NetAct

2.2.3.3 Hardware requirements

ThisfeaturerequiresFlexiSystemmoduleswhichsupportLTE.

2.2.4 Requirements

2.2.4.1 Interdependencies between features

FeatureLTE2:S1Flexneedstobeactivated.

2.2.4.2 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

Table5 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL40

FlexiMultiradioBTS LBTS2.0

FlexiMultiradio10BTS LBTS4.0

MME

SAEGW

UE 3GPPrelease8

NetAct

2.2.4.3 Hardware requirements

ThisfeaturerequiresFlexiSystemmoduleswhichsupportLTE.

2.2.5 Functional description

Issue:02M DN0978033 29

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.2.5.1 Functional overview

TheFlexiMultiradioBTScanbeconnectedsimultaneouslytotheEPCsofsixdifferent
operators-PublicLandMobileNetworks(PLMNs).ThisisdoneviatheS1Flex
mechanismwhichallowsBTStoestablishmultipleS1links.
TheoperatorsaresharingtheentireFlexiMultiradioBTSaswellastheOSSandthe
transport.
TheassignmentofPLMNIDstothesharedcellsisdoneviaSIB1configuration.The
primaryPLMNIDneedstobeconfiguredcommonlyforallcells.IndividualPLMNIDs
canbesetto'reservedforoperatoruse'inordersupportMORANsolutions.
ThePLMNinformationprovidedbytheS1setupisusedtoselectthecorrectS1
interfacefortheS1AP:INITIALUEmessage.
AllenabledBTSfeaturesareavailableforalloperators.
AllO&Msettings,includingneighborcellslists,arecommonforoperatorsincaseof
sharedcells.
ThesameIPsecisappliedonthetransportforalloperators.

2.2.5.2 Feature activation

TheLTE4:RANSharingfeatureisactivated,whentheLTE2:S1Flexisactive.
UseactivationinstructionsforLTE2:S1Flexfeature.See,FeatureActivation
Documentation.

2.2.6 System impact

2.2.6.1 Interdependencies between features

ThefeatureLTE2:S1Flexneedstobeenabled.

2.2.7 LTE4: RAN Sharing management data

2.2.7.1 Alarms

Therearenoalarmsrelatedtothisfeature.

2.2.7.2 Measurements and counters

Therearenomeasurementsandcountersrelatedtothisfeature.

2.2.7.3 Key performance indicators

Therearenokeyperformanceindicatorsrelatedtothisfeature.

2.2.7.4 Parameters

Therearenoparametersrelatedtothisfeature.

30 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.2.7.5 Sales information

Table6 Salesinformation

BSW/ASW License control in network element License control attributes

ASW - -

2.3 LTE7: Support of multiple EPS bearer


2.3.1 Introduction To The Feature
TheeNBsupportsanumberofbearercombinations.Theoperatorcanofferandthe
customercanuseacombinationofdifferentservicesforoneUE.WiththisfeatureLTE7:
SupportofmultipleEPSbeareritispossibletosupportofupto4AMDRB
(acknowledgedmodedataradiobearer)bearersperUE.Furthermoretherecanbetwo
signalingbearers(SRB)combined.
EachcombinationsofSRB1,SRB2anduptothe4AMDRBsareallowed.

2.3.2 Benefits
Theoperatorcanofferattractiveservicecombinationsasmultipleservices,thatcanbe
usedatoneUE.

2.3.3 Requirements

2.3.3.1 Software Requirements

Thefollowingsoftwareisneeded:

Table7 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME NS20

SAEGW NG20

UE 3GPPrelease8

NetAct

Issue:02M DN0978033 31

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.3.3.2 Hardware Requirements

Thisfeaturedoesnotrequireanyneworadditonalhardware.

2.3.4 Functional Description


AnEPS-bearer(Evolvedpacketsystembearer)isaninformationtransmissionpathof
definedcapacity,delayandbiterrorrate.ItisusedbetweenMME,eNBandtheUE.
LTEdistinguishesbetweentwotypesofbearers:

defaultbearer
OnedefaultbearerisestablishedwhentheUEconnectstotheMME(andthe
backbonePDN(packetdatanetwork))andremainsestablishedthroughoutthe
lifetimeoftheconnectiontoprovidetheUEwithalways-onIPconnectivitytothat
PDN.
dedicatedbearer
AnyadditionalEPSbearerthatisestablishedforthesamepacketdatanetwork
connectionisreferredtoasdedicatedbearer.

MultipleDRBs(dataradiobearers)canbeeithermultipledefaultEPSbearersora
combinationofdefaultanddedicatedbearers.Thetypeofthebeareristransparentto
theeNB.
TheradioadmissionisextendedbyadditionalcheckofthetotalnumberofDRBpercell
andmaximumnumberofDRBperUE.
ThedifferentbearersperUEcanhavethesameordifferentQCIs(QualityofService
Classidentifiers).TheQCIisanindexthatidenitifiestheQoSattributes:priority,delay
andlossrate.
TheeNBsupportsthefollowingscenariosforestablishingandreleasingEPSbearers:

establishindividualEPSbearers,
releaseindividualEPSbearers,
addmultipleEPSbearerstoexistingEPSbearers,
releasemultipleEPSbearersfromexistingEPSbearers.

ThereisonerestrictionregardingbearershavingthesameQCI,i.e.therecanonlybe
onebearerofacertainQCIperPDN;multipletrafficflowsrequiringthesameQCIare
alreadymergedintoasinglebearerinEPC.BearersofthesameQCIcanexistto
differentbearers.
Thedownlinkschedulerprovidesprioritizationamongmultiplenon-GBR(non
GuaranteedBitRate)EPS-bearersinordertoavoidstarvationofdownlinktraffic.
ThesingleormultipleEPSbearersareestablishedorreleasedbytheaccordingS1AP
procedure.
InFigure2:EPSbearerestablishmentbyS1AP:Initialcontextsetupprocedure(Attach)
amessageflowisshownfortheestablishingofoneormoreEPSbearerswiththeS1AP:
InitialContextSetupRequest(Attach).Thisprocedureistakenforthefirstaction.The
operatorcanestablishonedefault+optionaladditionalbearers.Thismessagecan
containUEcontextdata(e.g.UEradiocapabilities,securityinformation).

32 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Figure2 EPSbearerestablishmentbyS1AP:Initialcontextsetupprocedure
(Attach)

ThemessageflowforanEPSbearerestablishmentwiththeS1AP:InitialContextSetup
Request(ServiceRequest).isshowninFigure3:EPSbearerestablishmentbyS1AP:
Initialcontextsetupprocedure(Service).

Issue:02M DN0978033 33

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Figure3 EPSbearerestablishmentbyS1AP:Initialcontextsetupprocedure
(Service)

ThemessageflowfortheestablishmentofanadditionalsingleormultipleEPSbearer
withtheS1AP:E-RABsetuprequest(E-RAB:E-UTRANRadioACCESS)isshownin
Figure4:EPSbearerestablishmentbyS1AP:E-RABsetuprequest.TheE-RABSetup
proceduresupports:

Checkofactivationofthemulti-bearerfeature.
Checkofthesupportofthenewbearerconfiguration.
Reconfigurationoftheratecappingfunction,ifanewUE-AMBR(aggregated
maximumbitrate)hasbeenprovidedbyMME.
SetupofanadditionalsingleormultipleDRBsbytheRRCConnection
Reconfigurationprocedure.

34 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Figure4 EPSbearerestablishmentbyS1AP:E-RABsetuprequest

InFigure5:EPSbearerreleaseprocedurebyS1AP:E-RABreleaseprocedureanother
messagesequencechartisshown:ThereleaseofabearerwiththeS1AP:E-RAB
releaseprocedure.ThisS1AP:E-RABreleaseproceduresupportsthereleaseofa
singleormultipleEPSbearers.Thisincludes:

Check,whetheratleastonenon-GBRremains.
ReconfigurationoftheratecappingfunctionsifanewUE-AMBR(aggregated
maximumbitrate)hasbeenprovidedbyMME,
ReleaseofasingleormultipleDBRsbytheRRCConnectionReconfiguration
procedure.

Figure5 EPSbearerreleaseprocedurebyS1AP:E-RABreleaseprocedure

UE eNB MME

TriggeringofEPSBearerdeactivation

S1AP:E-RABRELEASECOMMAND
RRRC:RCConnectionReconfiguration

DRBRelease

RRC:RRCConnectionReconfigurationComplete
S1AP: RABRELEASERESPONSE

RRC: ULInformationTransfer
S1AP: UL NAS TRANSPORT

Postprocessing

Thisfeaturehasinfluenceondifferentfunctionsaslistedbelow:

Issue:02M DN0978033 35

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

RadioAdmissionControl(RAC)
RACchecksthethresholdmaxNumActDrbpercell.Thereforethecounter
NumActDrbcountsthetotalnumberofDRBs.TheRACwillbeinvolvedwhenDRBs
aresetup,whensetupsareaborted,whenDRBsarereleasedorUEsleavethecell.
EachadmissionrequestisprocessedwithinRACaccordingtotheallornothing
principle,e.g.ifn(n>1)DRBsshallbeadmittedandatleastoneDRBcannotbe
admitted,thecompleterequestisrejected.
TomeettherightdecisonsRACmustmaintaincountersfromTable8:Counters
maintainedbyRACandmustcomparethemtosysteminternalthresholds.
Table8 CountersmaintainedbyRAC

counter description

NumRRC counterforSRB1connectedUEs

NumActUE counterforactiveUEs(havingsignallingconnectionandadefaultDRB)

NumActDrb counterforalluserDRBs(QCIindependant)inthecell

TheabovementionedthresholdmaxNumActDrb(andotherslikemaxNumActUe,
maxNumRrc..)areretrievedfromtheOAMdatabaseatsystemsetup.
UL/DLScheduler
TheUL/DLSchedulerisextendedbythefollowngfunctions:
TheUL/DLSchedulerconsidersuptofourDRBs(GBRornot-GBR)perUE.
DRBsofoneUEcanhavethesameordifferentQCI.
TheUL/DLSchedulersupportsproportionalfairtreatmentofdifferentUEs
dependingondataavailabilityof(multiple)radiobearers(interUEfairness).
TheUL/DLSchedulersuppportsproportionalfairtreatmentofdifferentUEs
dependingonradiochannelquality.

AS(AccessStratum)Security
CipheringandintegrityprotectionformultipleDRBsaresupported.
InitialContextSetupProcedure
TheeNBsupportstheestablishmentofmultipleEPSbearersattheInitialContext
Setup-Procedure(seeFigure2:EPSbearerestablishmentbyS1AP:Initialcontext
setupprocedure(Attach)andFigure3:EPSbearerestablishmentbyS1AP:Initial
contextsetupprocedure(Service)).
E-RABSetupandE-RABRelease
TheeNBsupportstheestablishmentandreleaseofadditionalsingleormultipleEPS
bearers(seeFigure4:EPSbearerestablishmentbyS1AP:E-RABsetuprequestand
Figure5:EPSbearerreleaseprocedurebyS1AP:E-RABreleaseprocedure).
Handover
Thehandoverprocedures(intraeNBandintereNB)supportthehandoverfor
multiplenonGBRbearers.
IfthedecisionismadetoperformanintraeNBhandoverwhileabearer
managementprocedure(i.e.bearersetuporrelease)isongoing,thebearer
managementcontinues.TheintraeNB-handoverisdelayedandwillbestartedafter
thecompletionofthebearermanagementprocedure.
PDCPfunctionality
ThenewtimerS1retardtimerisintroduced.

36 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

MACMultiplexing
TheeNBsupportsthemultiplexingofdataofmultiplelogicalchannels
(correspondingtodataradiobearersaswellastosignallingradiobearers)intoa
singleMACPDUinDLdirection.
InULdirectiontheeNBsupportsthereceptionanddemultiplexingofMACPDUs
containingmultiplexeddatafrommultiplelogicalchannels.

2.3.5 System Impacts


ThisfeatureispreconditionforthefeatureLTE10:EPSbearersforconversationalvoice.

2.3.6 Sales Information


Thisfeatureisoptional.

2.3.7 User Interface

2.3.7.1 Parameters

Table9:ParametersfortheLTE7:SupportofmultipleEPSbearershowstheparameters
implementedforthefeatureLTE7:SupportofmultipleEPSbearers.

Table9 ParametersfortheLTE7:SupportofmultipleEPSbearer

Name Short name Object Description Range / Step Default


value

End-TagmaximumAM tagMaxAM LNBTS Themaximumboundfortag 0...1000ms, 10ms


timercalculationvalidforRLC- step1ms
AMDRBs.

End-TagmaximumUM tagMaxUM LNBTS Themaximumboundfortag 0...1000ms, 10ms


timercalculationvalidforRLC- step1ms
UMDRBs.

ActivateMultipleBearers actMultBearers LNBTS Thisparameteractivatesthe true


supportofmultipleEPSBearers.

ULSchedulerFDType ulsFdPrbAssignAl LNCEL SchedulerTypeforFrequency RoundRobinF ExhaustiveF


g Domain(FD)schedulerDefines D(0), D(1)
theschedulingmethodwhich ExhaustiveFD
shallbeappliedinfrequency (1)
domainfortheULscheduler-the
RoundRobinFDscheduler
assignsthephysicalresources
equallyfairtotheUEsselected
bytheTDscheduleruntilthe
PRBsaresufficientforthe
serviceorthephysicalresources
ofthecellareexhaust-theFD
ExhaustiveFDscheduler
assignsintheprioritysequence
definedbytheTDscheduleras

Issue:02M DN0978033 37

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table9 ParametersfortheLTE7:SupportofmultipleEPSbearer(Cont.)

Name Short name Object Description Range / Step Default


value

manyphysicalresourcesas
possibletotheUEsuntilthe
numberofPRBsaresufficient
fortheserviceortheresources
ofthecellareexhaust

2.3.7.2 Measurements and Counters

Table10:CountersforLTE7:SupportofmultipleEPSbearershowsthecountersfor
LTE7:SupportofmultipleEPSbearer

Table10 CountersforLTE7:SupportofmultipleEPSbearer

PI ID Counter long name (short Description


name)

M8000C17 E-RABsetupcompletions ThenumberofsuccessfulE-


(E_RAB_SETUP_SUCC) RABSetupCompletions

M8000C18 E-RABsetupfailuresdueto ThenumberofsuccessfulE-


radionetworklayerproblems RABSetupFailuresdueto
(E_RAB_SETUP_FAIL_RNL) radionetworklayerproblems

M8000C19 E-RABsetupfailuresdueto ThenumberofsuccessfulE-


transportlayerproblems RABSetupFailuresdueto
(E_RAB_SETUP_FAIL_TRAN transportlayerproblems
SPORT)

M8000C20 E-RABsetupfailuresdueto ThenumberofsuccessfulE-


resourceproblems RABSetupFailuresdueto
(E_RAB_SETUP_FAIL_RES resourceproblems
OURCE)

M8000C21 E-RABsetupfailuresdueto ThenumberofsuccessfulE-


otherreasons RABSetupFailuresdueto
(E_RAB_SETUP_FAIL_OTHE otherreasons
R)

M8000C22 E-RABsetuprequests ThenumberofE-RABSetup


(E_RAB_SETUP_ATT) Requests

M8006C16 EPSBearersetupfailuresdue ThenumberofEPSbearer


toPendingHandover setupfailuresdueto
(EPS_BEARER_SETUP_FAI HandoverPendingreason.
L_HO) EachbeareroftheE-RAB
FailedtoSetupListIEis
counted.

38 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table10 CountersforLTE7:SupportofmultipleEPSbearer(Cont.)

PI ID Counter long name (short Description


name)

M8006C17 InitialEPSBearersetup ThenumberofinitialEPS


attemptsforQCI1 bearersetupattemptsper
(EPS_BEARER_STP_ATT_IN QCI1.EachbeareroftheE-
I_QCI_1) RABtoBeSetupListIEis
counted.

M8006C18 InitialEPSBearersetup ThenumberofinitialEPS


attemptsfornon-GBR bearersetupattemptsper
(EPS_BEAR_STP_ATT_INI_ non-GBR.Eachbearerofthe
NON_GBR) E-RABtoBeSetupListIEis
counted.

M8006C26 AdditionalEPSBearersetup ThenumberofadditionalEPS


attemptsforQCI1 bearersetupattemptsper
(EPS_BEARER_STP_ATT_A QCI1.EachbeareroftheE-
DD_QCI_1) RABtoBeSetupListIEis
counted.

M8006C35 InitialEPSBearersetup ThenumberofinitialEPS


completionsforQCI1 bearersetupcompletionsper
(EPS_BEARER_STP_COM_I QCI1.EachbeareroftheE-
NI_QCI1) RABSetupListIEiscounted.

M8006C36 InitialEPSBearersetup ThenumberofinitialEPS


completionsfornon-GBR bearersetupcompletionsper
(EPS_BEAR_STP_COM_INI_ non-GBR.Eachbearerofthe
NON_GBR) E-RABSetupListIEis
counted.

M8006C44 AdditionalEPSBearersetup ThenumberofadditionalEPS


completionsforQCI1 bearersetupcompletionsfor
(EPS_BEAR_SET_COM_AD QCI1.EachbeareroftheE-
DIT_QCI1) RABSetupListIEiscounted.

M8006C89 EPCinitiatedEPSBearer ThenumberofEPC-initiated


ReleaserequestsforQCI1 EPSBearerReleaserequests
duetoNormalreleaseby forQCI1duetonormal
UE(EPC_EPS_BEAR_REL_R releasebyUE.Eachbearerof
EQ_N_QCI1) theE-RABtobeReleased
ListIEiscounted.

M8006C98 EPCinitiatedEPSBearer ThenumberofEPC-initiated


ReleaserequestsforQCI1 EPSBearerReleaserequests
duetoDetachprocedureby forQCI1duetotheDetach
UEorMME procedurebytheUEorthe
(EPC_EPS_BEAR_REL_REQ MME.EachbeareroftheE-
_D_QCI1) RABtobeReleasedListIEis
counted.

Issue:02M DN0978033 39

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table10 CountersforLTE7:SupportofmultipleEPSbearer(Cont.)

PI ID Counter long name (short Description


name)

M8006C107 EPCinitiatedEPSBearer ThenumberofEPC-initiated


ReleaserequestsperQCI1 EPSBearerReleaserequests
duetoRadioNetworkLayer forQCI1duetotheRadio
cause NetworkLayercause.Each
(EPC_EPS_BEAR_REL_REQ beareroftheE-RABtobe
_R_QCI1) ReleasedListIEiscounted.

M8006C116 EPCinitiatedEPSBearer ThenumberofEPC-initiated


ReleaserequestsforQCI1 EPSBearerReleaserequests
duetoOthercauses forQCI1duetoOthercauses.
(EPC_EPS_BEAR_REL_REQ EachbeareroftheE-RABto
_O_QCI1) beReleasedListIEis
counted.

M8006C125 eNBinitiatedEPSBearer ThenumberofeNB-initiated


ReleaserequestsforQCI1 EPSBearerReleaserequests
duetonormalrelease forQCI1duetotheNormal
(ENB_EPS_BEAR_REL_REQ release.IncaseofaUE
_N_QCI1) contextreleaserequest,all
theestablishedEPSBearers
arecounted.

M8006C134 eNBinitiatedEPSBearer ThenumberofeNB-initiated


ReleaserequestsforQCI1 EPSBearerReleaserequests
duetoRadioNetworkLayer forQCI1duetoRadio
cause NetworkLayercause.Incase
(ENB_EPS_BEAR_REL_REQ ofaUEcontextrelease
_R_QCI1) request,alltheestablished
EPSBearersarecounted.

M8006C143 eNBinitiatedEPSBearer ThenumberofeNB-initiated


ReleaserequestsforQCI1 EPSBearerReleaserequests
duetoOthercauses forQCI1duetoOthercauses
(ENB_EPS_BEAR_REL_REQ .IncaseofaUEcontext
_O_QCI1) releaserequest,allthe
establishedEPSBearersare
counted.

M8006C152 eNBinitiatedEPSBearer ThenumberofeNB-initiated


ReleaserequestsforQCI1 EPSBearerReleaserequests
duetoTransportLayerCause forQCI1dueTransportLayer
(ENB_EPS_BEAR_REL_REQ Cause-TransportResource
_T_QCI1) UnavailableCause.

M8006C161 eNBinitiatedEPSBearer ThenumberofeNB-initiated


ReleaserequestsforQCI1 EPSBearerReleaserequests
duetoRadioNetworkLayer forQCI1dueRedirect
causeRedirect (releaseduetoRNLE-
(ENB_EPS_BEAR_REL_REQ UTRANgeneratedreasonor
_RD_QCI1) RNLInter-RATRedirection)

40 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.4 LTE9: Service Differentiation


2.4.1 Introduction to the feature
ThisfeatureintroducesdifferentiationoffivedifferentnonGuaranteedBitRate(GBR)
QoSClassIndicator(QCI)classeswithrelativeschedulingweights.

2.4.2 Benefits
Differentnon-GBRQoSclassescanbeefficientlysupported.

2.4.3 Requirements

2.4.3.1 Software requirements

Table11 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME NS20

SAEGW NG20

UE 3GPPrelease8

NetAct

2.4.3.2 Hardware requirements

Thisfeaturerequiresnoneworadditionalhardware.

2.4.4 Functional description


WiththeFlexiMultiradioBTSservicedifferentiationfunctionality,itispossibletoassign
relativeschedulingweightsforeachnonGBRQCIonBTSlevel.Therelativeweightwill
beconsideredbytheuplinkandthedownlinkscheduler.Italsobringsinthepossibilityto
definethreedifferentRadioLinkControl(RLC)/PacketDataConvergenceProtocol
(PDCP)profilesperBTSwhichcanbeassignedtodifferentQCIs.Theoperatorcan
enable/disablethesupportofindividualQCIs.

TheLTE9:ServiceDifferentiationfeatureisoneoftheQualityofServicefeatures.It
dependsontheframeworkthatcomeswiththesupportofmultiplebearers,seeLTE7:
SupportofmultipleEPSbearer.Servicedifferentiationofnon-GBRbearerssupportsthe
followingfunctionalities:

Issue:02M DN0978033 41

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

ConfigurableweightvaluesperQCI
ConsiderationofweightvaluesinULandDLscheduling
ConsiderationofweightvaluesinMACmultiplexinginDL
Feature characteristics
CharacteristicsfortheQoSfeaturesaremainlydeterminedbythenetworkdeployment
scenariosoffeaturesandUEmobility.
WithLTE9:ServiceDifferentiationfeature,thedifferentiationofnon-GRBbearerswith
QCIfrom{5,6,7,8,9}viaconfigurableweightvaluesisintroduced.SupportofeachQCI
canbeenabledanddisabledbyO&M.Ifthefeatureisnotactivated,allbearersare
consideredwiththesamedefaultvalue.Thedefaultvaluesaretakenfromtheparameter
setofQCI9.Characteristicsofthefeaturearedescribedbelow:

Non-GBR service differentiation for different UEs


SeveralUEsbecomeactiveinonecellunderidenticalradioconditionssuchthatthe
cellisunderload.EachUEhasasingle(ormultiple)non-GBRbearerestablished
buttheQCI(s)ofthesingle(orthemultiple)bearer(s)isdifferentbetweendifferent
UEs.Therearenolimitationstothetrafficarrivalfortheestablishedbearers.Service
differentiationbetweenUEsisperformedbyconsideringschedulingweightsin
schedulers(uplinkanddownlink).
Non-GBR service differentiation in downlink for a single UE
Inacellunderload,multiplebearerswithdifferentQCIsareestablishedforaUE.
Servicedifferentiationisperformedbyusingaweightedroundrobinapproachin
logicalchannelprioritizationinDL(logicalchannelprioritizationinULisdefinedby
3GPPstandardandUEresponsibility,prioritizedbitratesetting,isusedtoprevent
bearerstarvation).Therearenolimitationstothetrafficarrivalfortheestablished
bearers.
Establishment of a bearer when specific QCI is disabled
ServicerequestsforQCIwhicharedisabledarerejected.EPCrequestsfora
connectedUEestablishmentofabearerwithaspecificQCIdifferentfromthedefault
QCI.
Modification of QCI specific weight values
AsetofQCIspecificweightvaluesisconfiguredintheeNodeB.Bearersofthesame
orofdifferentUEsareservedaccordingtotheconfiguredweightvalues.Thespecific
weightvalueforoneorseveralQCIsis/aremodifiedtoadifferentvalueviathe
managementtool(NetAct).Weightvaluesforalreadyestablishedbearersremain
unchanged.ModifiedQCIspecificweightvaluesareappliedfornewUEsinthecell
orforestablishmentofnewbearersforexistingUEs.
UL Scheduler and DL Scheduler
TheULSchedulerandDLSchedulerintroduceservicedependentweightsbeingusedin
theschedulingmetrictodifferentiatebetweendifferentUEsordifferentbearersofthe
sameUE.
TheeNodeBsupportsservicedifferentiationfornon-GBRdataradiobearersinULand
DLscheduling:

UL/DLschedulerconsiders(configurable)QCI-specificrelativeweightvaluesas
providedbythecontrolplaneinscheduling
UL/DLschedulersupportsrelativefairtreatmentofdifferentUEsdependingon
weightvaluesanddataavailabilityofasingleormultipledataradiobearer

MAC Multiplexing

42 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

TheeNodeBsupportsmultiplexingofdataofmultiplelogicalchannels(correspondingto
dataradiobearersaswellastosignallingradiobearers)intoasingleMACPDUinDL.
TheeNodeBsupportsservicedifferentiationforNon-GBRdataradiobearersinMAC
multiplexingandlogicalchannelprioritizationinDL:

FormultiplebearersforoneUE,MACmultiplexingandlogicalchannelprioritization
inDLconsiders(configurable)QCI-specificrelativeweightvaluesasbeingprovided
bycontrolplane
LogicalchannelprioritizationinDLsupportslongtermrelativefairtreatmentof
multiplebearersofoneUEdependingonbearersdataavailability(intra-UEfairness)

Priority handling between logical channels of one UE


ThepriorityhandlingbetweenlogicalchannelsofaUEisperformedinasubframein
whichtheUEisallocatedresourcesforanewtransmission.Thefollowinginput
parametersarerequired:

QCIweight(orschedulingweight)forlogicalchannelsofNon-GBRtype
Thetransportblocksize(TBS)inbitsallocatedtotheUE.TBSisdeterminedbythe
numberofPRBs/RBGsallocatedtotheUEandMCSused.

TheschedulingprocedureoflogicalchannelsofaUEisinitializedassoonasaUEis
admittedandabearerisestablishedinacell.
Allocate resources to Non-GBR bearers of the UE according to scheduling weights
AlltheNon-GBRlogicalchannels(QCI6-9,orQCI5withschedulType=NON-GBR)are
servedaccordingtoaweightedroundrobin(WRR)method.Aschedulingsequenceis
generatedofalltheestablishedNon-GBRlogicalchannelsaccordingtotheQCIweights
ofeachnon-GBRlogicalchannelofUEusingWRRmethod.TheWRRmethod
determineswhichbearertoselectforfillingthetransportblock,whereastheamountof
datatakenfromonebearersisnotlimitedwhichinturnleadstoaWRRlikeallocationof
resourcestobearers(givensametrafficarrivalbehaviourforthebearers)inavergein
thelongterm.

2.4.5 System impacts


Thefeaturehasnoadditionalimpactsonthesystem.

2.4.6 Sales information


TheLTE9:ServiceDifferentiationfeaturebelongstotheApplicationSoftware(ASW)
productstructureclass.

2.4.7 User interface

2.4.7.1 Parameters

ThefollowingtablesshowstheimplementedparametersforLTE9:Service
Differentiation.

Issue:02M DN0978033 43

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table12 ParametersfortheLTE9:ServiceDifferentiation

Name Short name Object Description Range / Step Default


value

Activate actNonGbrService LNBTS Thisparameteractivatesthe true


NonGBR Diff ServiceDifferentiationfornon-
Service GBRBearers.
Differentiation

PrioritizedBit pbrNonGbr LNBTS PrioritizedBitRatefornon- 0kbps(0),8kbps(1), 16kbps(2)


Rate GBRbearersThisprioritizedbit 16kbps(2),32kbps(3),
NonGBR rateisusedbyUEfortheUL 64kbps(4),128kpbs(5),
schedulingalgorithmaccording 256kbps(6)
[36.321].

Table13 ParametersforAMRLCPollBytestructure

Name Short name Object Description Range / Step Default


value

AMRLCPoll amRlcPBTab1 LNBTS AMRLCPollByteTableforUE


ByteTable1 Category1.Itisusedtoobtain
theULpollByteandDLpollByte
valuesforUEcategory1.

DLPollByte dlPollByte LNBTS AMRLCPollBytevalueinDL 25kB(0),50kB(1),75kB(2), 25kB(0)


directionforUEcategory1. 100kB(3),125kB(4),250kB
(5),375kB(6),500kB(7),
750kB(8),1000kB(9),
1250kB(10),1500kB(11),
2000kB(12),3000kB(13),
Infinity(14)

UECategory ueCategory LNBTS CategoryofUE. 1...1,step1 1

ULPollByte ulPollByte LNBTS AMRLCPollBytevalueinUL 25kB(0),50kB(1),75kB(2), 25kB(0)


directionforUEcategory1. 100kB(3),125kB(4),250kB
(5),375kB(6),500kB(7),
750kB(8),1000kB(9),
1250kB(10),1500kB(11),
2000kB(12),3000kB(13),
Infinity(14)

AMRLCPoll amRlcPBTab2 LNBTS AMRLCPollByteTableforUE


ByteTable2 Category2.Itisusedtoobtain
theULpollByteandDLpollByte
valuesforUEcategory2.

DLPollByte dlPollByte LNBTS AMRLCPollBytevalueinDL 25kB(0),50kB(1),75kB(2), 25kB(0)


directionforUEcategory2. 100kB(3),125kB(4),250kB
(5),375kB(6),500kB(7),
750kB(8),1000kB(9),

44 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table13 ParametersforAMRLCPollBytestructure(Cont.)

Name Short name Object Description Range / Step Default


value

1250kB(10),1500kB(11),
2000kB(12),3000kB(13),
Infinity(14)

UECategory ueCategory LNBTS CategoryofUE. 2...2,step1 2

ULPollByte ulPollByte LNBTS AMRLCPollBytevalueinUL 25kB(0),50kB(1),75kB(2), 25kB(0)


directionforUEcategory2. 100kB(3),125kB(4),250kB
(5),375kB(6),500kB(7),
750kB(8),1000kB(9),
1250kB(10),1500kB(11),
2000kB(12),3000kB(13),
Infinity(14)

AMRLCPoll amRlcPBTab3 LNBTS AMRLCPollByteTableforUE


ByteTable3 Category3.Itisusedtoobtain
theULpollByteandDLpollByte
valuesforUEcategory3.

DLPollByte dlPollByte LNBTS AMRLCPollBytevalueinDL 25kB(0),50kB(1),75kB(2), 50kB(1)


directionforUEcategory3. 100kB(3),125kB(4),250kB
(5),375kB(6),500kB(7),
750kB(8),1000kB(9),
1250kB(10),1500kB(11),
2000kB(12),3000kB(13),
Infinity(14)

UECategory ueCategory LNBTS CategoryofUE. 3...3,step1 3

ULPollByte ulPollByte LNBTS AMRLCPollBytevalueinUL 25kB(0),50kB(1),75kB(2), 25kB(0)


directionforUEcategory3. 100kB(3),125kB(4),250kB
(5),375kB(6),500kB(7),
750kB(8),1000kB(9),
1250kB(10),1500kB(11),
2000kB(12),3000kB(13),
Infinity(14)

AMRLCPoll amRlcPBTab4 LNBTS AMRLCPollByteTableforUE


ByteTable4 Category4.Itisusedtoobtain
theULpollByteandDLpollByte
valuesforUEcategory4.

DLPollByte dlPollByte LNBTS AMRLCPollBytevalueinDL 25kB(0),50kB(1),75kB(2), 75kB(2)


directionforUEcategory4. 100kB(3),125kB(4),250kB
(5),375kB(6),500kB(7),
750kB(8),1000kB(9),
1250kB(10),1500kB(11),
2000kB(12),3000kB(13),
Infinity(14)

Issue:02M DN0978033 45

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table13 ParametersforAMRLCPollBytestructure(Cont.)

Name Short name Object Description Range / Step Default


value

UECategory ueCategory LNBTS CategoryofUE. 4...4,step1 4

ULPollByte ulPollByte LNBTS AMRLCPollBytevalueinUL 25kB(0),50kB(1),75kB(2), 25kB(0)


directionforUEcategory4. 100kB(3),125kB(4),250kB
(5),375kB(6),500kB(7),
750kB(8),1000kB(9),
1250kB(10),1500kB(11),
2000kB(12),3000kB(13),
Infinity(14)

AMRLCPoll amRlcPBTab5 LNBTS AMRLCPollByteTableforUE


ByteTable5 Category5.Itisusedtoobtain
theULpollByteandDLpollByte
valuesforUEcategory5.

DLPollByte dlPollByte LNBTS AMRLCPollBytevalueinDL 25kB(0),50kB(1),75kB(2), 125kB(4)


directionforUEcategory5. 100kB(3),125kB(4),250kB
(5),375kB(6),500kB(7),
750kB(8),1000kB(9),
1250kB(10),1500kB(11),
2000kB(12),3000kB(13),
Infinity(14)

UECategory ueCategory LNBTS CategoryofUE. 5...5,step1 5

ULPollByte ulPollByte LNBTS AMRLCPollBytevalueinUL 25kB(0),50kB(1),75kB(2), 50kB(1)


directionforUEcategory5. 100kB(3),125kB(4),250kB
(5),375kB(6),500kB(7),
750kB(8),1000kB(9),
1250kB(10),1500kB(11),
2000kB(12),3000kB(13),
Infinity(14)

Table14 ParametersforQCITranslationTablestructure

Name Short name Object Description Range / Step Default value

QCI qciTab5 LNBTS TabletotranslatetheS1APparameter


Translation QCI5intoQCIcharacteristics
TableQCI5

DSCP dscp LNBTS ThisparameterconfigurestheDSCP 0...63,step1 34


(DifferentiatedServicesCodePoint)value
associatedwiththeQCI.TheDSCPvalue
willbesetineachIPpacketsentforthe
relatedbearertoS-GWortargeteNB.List
ofIETFbasedDSCPvalues(numerical
valuesindecimal):BE(=0),AF11(=10),

46 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table14 ParametersforQCITranslationTablestructure(Cont.)

Name Short name Object Description Range / Step Default value

AF12(=12),AF13(=14),AF21(=18),
AF22(=20),AF23(=22),AF31(=26),
AF32(=28),AF33(=30),AF41(=34),
AF42(=36),AF43(=38),EF(=46)

Logical lcgid LNBTS LogicalChannelGroupIdentifierforbuffer 0(0),2(2),3(3) 2(2)


Channel statusreportingThisparameterisusedfor
Group configurationofthebufferstatusreportsof
Identifier UEaccording[36.321]

PDCPProfile pdcpProfIdx LNBTS ThisparameterspecifiestheIDofthe 1...3,step1 1


Index correspondingPDCPprofile.

Priority prio LNBTS Thisparametergivesthepriorityofthe 1...1,step1 1


EPSbeareraccordingtoTS23.203.

QCI qci LNBTS QoSClassIdentifier 5...5,step1 5

QCISupport qciSupp LNBTS Thisparameterindicateswhetherthe DISABLE(0), ENABLE(1)


givenQCIissupportedandenabled ENABLE(1)

Resource resType LNBTS TheResourceTypeindicateswhether nonGBR(1) nonGBR(1)


Type bearerisaGBRorNON-GBRbearer.The
ResourceTypedeterminesifdedicated
networkresourcesrelatedtoaserviceor
bearerlevelGuaranteedBitRate(GBR)
valuearepermanentlyallocated.

RLCMode rlcMode LNBTS ThisparameterconfigurestheRLCMode RLC_AM(0) RLC_AM(0)


ofthedataradiobearer

RLCProfile rlcProfIdx LNBTS ThisparameterspecifiestheIDofthe 1...3,step1 1


Index correspondingRLCprofile

Scheduling schedulBSD LNBTS Thisparameterisusedtoconfigurethe 50ms(0),100ms 100ms(1)


BucketSize BucketSizeDuration(BSD)oftheUL (1),150ms(2),
Duration schedulerTheBSDissenttoUEforthe 300ms(3),500ms
ULschedulingalgorithmaccording (4),1000ms(5)
[36.321].TheUEcalculatesthebucket
sizeofalogicalchannelbyPBR*BSD.

Scheduling schedulPrio LNBTS LogicalChannelPriorityfortheUE 2...16,step1 9


Priority schedulerThispriorityissenttoUEfor
theULschedulingalgorithmaccordingfor
DRB[36.321].Increasingpriorityvalues
indicatelowerpriority.

Scheduling schedulType LNBTS ThisparameterspecifieshowtheEPS SIGNALLING(0), NON-GBR(1)


Type bearerwithQCI5isscheduled.Forthe NON-GBR(1)
schedulingtypeSIGNALLINGthebearer

Issue:02M DN0978033 47

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table14 ParametersforQCITranslationTablestructure(Cont.)

Name Short name Object Description Range / Step Default value

ishandledlikeSRBs.TheMACLCGID
shallbesetto0andschedulPrioisused
forULandDLscheduling.Forthe
schedulingtypeNON-GBRthebeareris
handledlikeothernon-GBRbearers.The
MACLCGIDshallnotbeto0andthe
schedulWeightisusedforDLscheduling.

Scheduling schedulWeigh LNBTS Thisparameterspecifiesthescheduling 1...100,step1 40


Weight t weightforeNBschedulersThescheduling
weightisusedforMACscheduling(UL
andDL),andMAClogicalchannelpriority
handlingandmultiplexinginDL

QCI qciTab6 LNBTS TabletotranslatetheS1APparameter


Translation QCI6intoQCIcharacteristics
TableQCI6

DSCP dscp LNBTS ThisparameterconfigurestheDSCP 0...63,step1 18


(DifferentiatedServicesCodePoint)value
associatedwiththeQCI.TheDSCPvalue
willbesetineachIPpacketsentforthe
relatedbearertoS-GWortargeteNB.List
ofIETFbasedDSCPvalues(numerical
valuesindecimal):BE(=0),AF11(=10),
AF12(=12),AF13(=14),AF21(=18),
AF22(=20),AF23(=22),AF31(=26),
AF32(=28),AF33(=30),AF41(=34),
AF42(=36),AF43(=38),EF(=46)

Logical lcgid LNBTS LogicalChannelGroupIdentifierforbuffer 2(2),3(3) 3(3)


Channel statusreportingThisparameterisusedfor
Group configurationofthebufferstatusreportsof
Identifier UEaccording[36.321]

PDCPProfile pdcpProfIdx LNBTS ThisparameterspecifiestheIDofthe 1...3,step1 2


Index correspondingPDCPprofile.

Priority prio LNBTS Thisparametergivesthepriorityofthe 6...6,step1 6


EPSbeareraccordingTS23.203.

QCI qci LNBTS QoSClassIdentifier 6...6,step1 6

QCISupport qciSupp LNBTS Thisparameterindicateswhetherthe DISABLE(0), ENABLE(1)


givenQCIissupportedandenabled ENABLE(1)

Resource resType LNBTS TheResourceTypeindicateswhether nonGBR(1) nonGBR(1)


Type bearerisaGBRorNON-GBRbearer.The
ResourceTypedeterminesifdedicated

48 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table14 ParametersforQCITranslationTablestructure(Cont.)

Name Short name Object Description Range / Step Default value

networkresourcesrelatedtoaserviceor
bearerlevelGuaranteedBitRate(GBR)
valuearepermanentlyallocated.

RLCMode rlcMode LNBTS ThisparameterconfigurestheRLCMode RLC_AM(0) RLC_AM(0)


ofthedataradiobearer

RLCProfile rlcProfIdx LNBTS ThisparameterspecifiestheIDofthe 1...3,step1 2


Index correspondingRLCprofile

Scheduling schedulBSD LNBTS Thisparameterisusedtoconfigurethe 50ms(0),100ms 300ms(3)


BucketSize BucketSizeDuration(BSD)oftheUL (1),150ms(2),
Duration schedulerTheBSDissenttoUEforthe 300ms(3),500ms
ULschedulingalgorithmaccording (4),1000ms(5)
[36.321].TheUEcalculatesthebucket
sizeofalogicalchannelbyPBR*BSD.

Scheduling schedulPrio LNBTS LogicalChannelPriorityfortheUE 9...16,step1 9


Priority schedulerThispriorityissenttoUEfor
theULschedulingalgorithmaccordingfor
DRB[36.321].Increasingpriorityvalues
indicatelowerpriority.

Scheduling schedulWeigh LNBTS Thisparameterspecifiesthescheduling 1...100,step1 20


Weight t weightforeNBschedulersThescheduling
weightisusedforMACscheduling(UL
andDL),andMAClogicalchannelpriority
handlingandmultiplexinginDL

QCI qciTab7 LNBTS TabletotranslatetheS1APparameter


Translation QCI7intoQCIcharacteristics
TableQCI7

DSCP dscp LNBTS ThisparameterconfigurestheDSCP 0...63,step1 20


(DifferentiatedServicesCodePoint)value
associatedwiththeQCI.TheDSCPvalue
willbesetineachIPpacketsentforthe
relatedbearertoS-GWortargeteNB.List
ofIETFbasedDSCPvalues(numerical
valuesindecimal):BE(=0),AF11(=10),
AF12(=12),AF13(=14),AF21(=18),
AF22(=20),AF23(=22),AF31(=26),
AF32(=28),AF33(=30),AF41(=34),
AF42(=36),AF43(=38),EF(=46)

Logical lcgid LNBTS LogicalChannelGroupIdentifierforbuffer 2(2),3(3) 2(2)


Channel statusreportingThisparameterisusedfor
Group configurationofthebufferstatusreportsof
Identifier UEaccording[36.321]

Issue:02M DN0978033 49

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table14 ParametersforQCITranslationTablestructure(Cont.)

Name Short name Object Description Range / Step Default value

PDCPProfile pdcpProfIdx LNBTS ThisparameterspecifiestheIDofthe 1...3,step1 1


Index correspondingPDCPprofile.

Priority prio LNBTS Thisparametergivesthepriorityofthe 7...7,step1 7


EPSbeareraccordingTS23.203.

QCI qci LNBTS QoSClassIdentifier 7...7,step1 7

QCISupport qciSupp LNBTS Thisparameterindicateswhetherthe DISABLE(0), ENABLE(1)


givenQCIissupportedandenabled ENABLE(1)

Resource resType LNBTS TheResourceTypeindicateswhether nonGBR(1) nonGBR(1)


Type bearerisaGBRorNON-GBRbearer.The
ResourceTypedeterminesifdedicated
networkresourcesrelatedtoaserviceor
bearerlevelGuaranteedBitRate(GBR)
valuearepermanentlyallocated.

RLCMode rlcMode LNBTS ThisparameterconfigurestheRLCMode RLC_AM(0) RLC_AM(0)


ofthedataradiobearer

RLCProfile rlcProfIdx LNBTS ThisparameterspecifiestheIDofthe 1...3,step1 2


Index correspondingRLCprofile

Scheduling schedulBSD LNBTS Thisparameterisusedtoconfigurethe 50ms(0),100ms 100ms(1)


BucketSize BucketSizeDuration(BSD)oftheUL (1),150ms(2),
Duration schedulerTheBSDissenttoUEforthe 300ms(3),500ms
ULschedulingalgorithmaccording (4),1000ms(5)
[36.321].TheUEcalculatesthebucket
sizeofalogicalchannelbyPBR*BSD.

Scheduling schedulPrio LNBTS LogicalChannelPriorityfortheUE 9...16,step1 10


Priority schedulerThispriorityissenttoUEfor
theULschedulingalgorithmaccordingfor
DRB[36.321].Increasingpriorityvalues
indicatelowerpriority.

Scheduling schedulWeigh LNBTS Thisparameterspecifiesthescheduling 1...100,step1 10


Weight t weightforeNBschedulersThescheduling
weightisusedforMACscheduling(UL
andDL),andMAClogicalchannelpriority
handlingandmultiplexinginDL

QCI qciTab8 LNBTS TabletotranslatetheS1APparameter


Translation QCI8intoQCIcharacteristics
TableQCI8

DSCP dscp LNBTS ThisparameterconfigurestheDSCP 0...63,step1 10


(DifferentiatedServicesCodePoint)value
associatedwiththeQCI.TheDSCPvalue

50 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table14 ParametersforQCITranslationTablestructure(Cont.)

Name Short name Object Description Range / Step Default value

willbesetineachIPpacketsentforthe
relatedbearertoS-GWortargeteNB.List
ofIETFbasedDSCPvalues(numerical
valuesindecimal):BE(=0),AF11(=10),
AF12(=12),AF13(=14),AF21(=18),
AF22(=20),AF23(=22),AF31(=26),
AF32(=28),AF33(=30),AF41(=34),
AF42(=36),AF43(=38),EF(=46)

Logical lcgid LNBTS LogicalChannelGroupIdentifierforbuffer 2(2),3(3) 3(3)


Channel statusreporting.Thisparameterisused
Group forconfigurationofthebufferstatus
Identifier reportsofUEaccording[36.321]

PDCPProfile pdcpProfIdx LNBTS ThisparameterspecifiestheIDofthe 1...3,step1 2


Index correspondingPDCPprofile.

Priority prio LNBTS Thisparametergivesthepriorityofthe 8...8,step1 8


EPSbeareraccordingTS23.203.

QCI qci LNBTS QoSClassIdentifier 8...8,step1 8

QCISupport qciSupp LNBTS Thisparameterindicateswhetherthe DISABLE(0), ENABLE(1)


givenQCIissupportedandenabled ENABLE(1)

Resource resType LNBTS TheResourceTypeindicateswhether nonGBR(1) nonGBR(1)


Type bearerisaGBRorNON-GBRbearer.The
ResourceTypedeterminesifdedicated
networkresourcesrelatedtoaserviceor
bearerlevelGuaranteedBitRate(GBR)
valuearepermanentlyallocated.

RLCMode rlcMode LNBTS ThisparameterconfigurestheRLCMode RLC_AM(0) RLC_AM(0)


ofthedataradiobearer

RLCProfile rlcProfIdx LNBTS ThisparameterspecifiestheIDofthe 1...3,step1 2


Index correspondingRLCprofile

Scheduling schedulBSD LNBTS Thisparameterisusedtoconfigurethe 50ms(0),100ms 300ms(3)


BucketSize BucketSizeDuration(BSD)oftheUL (1),150ms(2),
Duration schedulerTheBSDissenttoUEforthe 300ms(3),500ms
ULschedulingalgorithmaccording (4),1000ms(5)
[36.321].TheUEcalculatesthebucket
sizeofalogicalchannelbyPBR*BSD.

Scheduling schedulPrio LNBTS LogicalChannelPriorityfortheUE 9...16,step1 11


Priority schedulerThispriorityissenttoUEfor
theULschedulingalgorithmaccordingfor
DRB[36.321].Increasingpriorityvalues
indicatelowerpriority.

Issue:02M DN0978033 51

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table14 ParametersforQCITranslationTablestructure(Cont.)

Name Short name Object Description Range / Step Default value

Scheduling schedulWeigh LNBTS Thisparameterspecifiesthescheduling 1...100,step1 5


Weight t weightforeNBschedulersThescheduling
weightisusedforMACscheduling(UL
andDL),andMAClogicalchannelpriority
handlingandmultiplexinginDL

QCI qciTab9 LNBTS TabletotranslatetheS1APparameter


Translation QCI9intoQCIcharacteristics
TableQCI9

DSCP dscp LNBTS ThisparameterconfigurestheDSCP 0...63,step1 0


(DifferentiatedServicesCodePoint)value
associatedwiththeQCI.TheDSCPvalue
willbesetineachIPpacketsentforthe
relatedbearertoS-GWortargeteNB.List
ofIETFbasedDSCPvalues(numerical
valuesindecimal):BE(=0),AF11(=10),
AF12(=12),AF13(=14),AF21(=18),
AF22(=20),AF23(=22),AF31(=26),
AF32(=28),AF33(=30),AF41(=34),
AF42(=36),AF43(=38),EF(=46)

Logical lcgid LNBTS LogicalChannelGroupIdentifierforbuffer 2(2),3(3) 3(3)


Channel statusreportingThisparameterisusedfor
Group configurationofthebufferstatusreportsof
Identifier UEaccording[36.321]

PDCPProfile pdcpProfIdx LNBTS ThisparameterspecifiestheIDofthe 1...3,step1 2


Index correspondingPDCPprofile.

Priority prio LNBTS Thisparametergivesthepriorityofthe 9...9,step1 9


EPSbeareraccordingTS23.203.

QCI qci LNBTS QoSClassIdentifier 9...9,step1 9

QCISupport qciSupp LNBTS Thisparameterindicateswhetherthe DISABLE(0), ENABLE(1)


givenQCIissupportedandenabled ENABLE(1)

Resource resType LNBTS TheResourceTypeindicateswhether nonGBR(1) nonGBR(1)


Type bearerisaGBRorNON-GBRbearer.The
ResourceTypedeterminesifdedicated
networkresourcesrelatedtoaserviceor
bearerlevelGuaranteedBitRate(GBR)
valuearepermanentlyallocated.

RLCMode rlcMode LNBTS ThisparameterconfigurestheRLCMode RLC_AM(0) RLC_AM(0)


ofthedataradiobearer

RLCProfile rlcProfIdx LNBTS ThisparameterspecifiestheIDofthe 1...3,step1 2


Index correspondingRLCprofile

52 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table14 ParametersforQCITranslationTablestructure(Cont.)

Name Short name Object Description Range / Step Default value

Scheduling schedulBSD LNBTS Thisparameterisusedtoconfigurethe 50ms(0),100ms 300ms(3)


BucketSize BucketSizeDuration(BSD)oftheUL (1),150ms(2),
Duration schedulerTheBSDissenttoUEforthe 300ms(3),500ms
ULschedulingalgorithmaccording (4),1000ms(5)
[36.321].TheUEcalculatesthebucket
sizeofalogicalchannelbyPBR*BSD.

Scheduling schedulPrio LNBTS LogicalChannelPriorityfortheUE 9...16,step1 12


Priority schedulerThispriorityissenttoUEfor
theULschedulingalgorithmaccordingfor
DRB[36.321].Increasingpriorityvalues
indicatelowerpriority.

Scheduling schedulWeigh LNBTS Thisparameterspecifiesthescheduling 1...100,step1 1


Weight t weightforeNBschedulersThescheduling
weightisusedforMACscheduling(UL
andDL),andMAClogicalchannelpriority
handlingandmultiplexinginDL

Table15 ParametersforprofilesofRLC

Name Short name Object Description Range / Step Default


value

Profile1of rlcProf1 LNBTS Profile1ofRLCparameters


RLC forDRBsinRLCAMmode
Parameters

PollPDU pollPdu LNBTS Thisparameterspecifiesthe 4(0),8(1),16(2),32(3),64(4),128 infinity(7)


parameterpollPDUof (5),256(6),infinity(7)
[36.331]TheparameterPoll
PDUdefinesthenumberof
RLCPDUsthataresenton
alogicalchannelbeforethe
RLCpollingbitisset.

RLCProfileId rlcProfileId LNBTS IdentityoftheRLCprofile 1...1,step1 1

TimerPoll tPollRetr LNBTS Thisparameterspecifiesthe 5ms(0),10ms(1),15ms(2),20ms 120ms(23)


Retransmit parametert-pollRetransmit (3),25ms(4),30ms(5),35ms(6),
of[36.331]Thistimerisused 40ms(7),45ms(8),50ms(9),55ms
bythetransmittingsideofan (10),60ms(11),65ms(12),70ms
AMRLCentityinorderto (13),75ms(14),80ms(15),85ms
retransmitapoll.Theused (16),90ms(17),95ms(18),100ms
minimumvalueofthetimer (19),105ms(20),110ms(21),115ms
shallbelargerthanthe (22),120ms(23),125ms(24),130ms
calculatedround-triptime (25),135ms(26),140ms(27),145ms
withconsiderationsofHARQ (28),150ms(29),155ms(30),160ms
retransmissionsandout-of- (31),165ms(32),170ms(33),175ms

Issue:02M DN0978033 53

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table15 ParametersforprofilesofRLC(Cont.)

Name Short name Object Description Range / Step Default


value

sequencearrival.Thevalue (34),180ms(35),185ms(36),190ms
ofthetimershallbelarger (37),195ms(38),200ms(39),205ms
thantwiceofthe (40),210ms(41),215ms(42),220ms
timerReorder. (43),225ms(44),230ms(45),235ms
(46),240ms(47),245ms(48),250ms
(49),300ms(50),350ms(51),400ms
(52),450ms(53),500ms(54)

TimerStatus tProhib LNBTS Thisparameterspecifiesthe 0ms(0),5ms(1),10ms(2),15ms 50ms(10)


Prohibit parametert-StatusProhibitof (3),20ms(4),25ms(5),30ms(6),
[36.331]Thistimerisused 35ms(7),40ms(8),45ms(9),50ms
bythereceivingsideofan (10),55ms(11),60ms(12),65ms
AMRLCentityinorderto (13),70ms(14),75ms(15),80ms
prohibittransmissionofa (16),85ms(17),90ms(18),95ms
STATUSPDU (19),100ms(20),105ms(21),110ms
(22),115ms(23),120ms(24),125ms
(25),130ms(26),135ms(27),140ms
(28),145ms(29),150ms(30),155ms
(31),160ms(32),165ms(33),170ms
(34),175ms(35),180ms(36),185ms
(37),190ms(38),195ms(39),200ms
(40),205ms(41),210ms(42),215ms
(43),220ms(44),225ms(45),230ms
(46),235ms(47),240ms(48),245ms
(49),250ms(50),300ms(51),350ms
(52),400ms(53),450ms(54),500ms
(55)

Timer tReord LNBTS Thisparameterspecifiesthe 0ms(0),5ms(1),10ms(2),15ms 50ms(10)


Reordering parametert-Reorderingof (3),20ms(4),25ms(5),30ms(6),
[36.331]Thistimerisused 35ms(7),40ms(8),45ms(9),50ms
bythereceivingsideofan (10),55ms(11),60ms(12),65ms
AMRLCentityfor (13),70ms(14),75ms(15),80ms
reordering,PDUloss (16),85ms(17),90ms(18),95ms
detectionanddelayof (19),100ms(20),110ms(21),120ms
STATUSPDUtransmission. (22),130ms(23),140ms(24),150ms
Thistimerdependson (25),160ms(26),170ms(27),180ms
HARQRTTandnumberof (28),190ms(29),200ms(30)
HARQretransmissions.

Profile2of rlcProf2 LNBTS Profile2ofRLCparameters


RLC forDRBsinRLCAMmode
Parameters

PollPDU pollPdu LNBTS Thisparameterspecifiesthe 4(0),8(1),16(2),32(3),64(4),128 64(4)


parameterpollPDUof (5),256(6),infinity(7)
[36.331]TheparameterPoll
PDUdefinesthenumberof
RLCPDUsthataresenton
alogicalchannelbeforethe
RLCpollingbitisset.

54 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table15 ParametersforprofilesofRLC(Cont.)

Name Short name Object Description Range / Step Default


value

RLCProfileId rlcProfileId LNBTS IdentityoftheRLCprofile 2...2,step1 2

TimerPoll tPollRetr LNBTS Thisparameterspecifiesthe 5ms(0),10ms(1),15ms(2),20ms 120ms(23)


Retransmit parametert-pollRetransmit (3),25ms(4),30ms(5),35ms(6),
of[36.331]Thistimerisused 40ms(7),45ms(8),50ms(9),55ms
bythetransmittingsideofan (10),60ms(11),65ms(12),70ms
AMRLCentityinorderto (13),75ms(14),80ms(15),85ms
retransmitapoll.Theused (16),90ms(17),95ms(18),100ms
minimumvalueofthetimer (19),105ms(20),110ms(21),115ms
shallbelargerthanthe (22),120ms(23),125ms(24),130ms
calculatedround-triptime (25),135ms(26),140ms(27),145ms
withconsiderationsofHARQ (28),150ms(29),155ms(30),160ms
retransmissionsandout-of- (31),165ms(32),170ms(33),175ms
sequencearrival.Thevalue (34),180ms(35),185ms(36),190ms
ofthetimershallbelarger (37),195ms(38),200ms(39),205ms
thantwiceofthe (40),210ms(41),215ms(42),220ms
timerReorder. (43),225ms(44),230ms(45),235ms
(46),240ms(47),245ms(48),250ms
(49),300ms(50),350ms(51),400ms
(52),450ms(53),500ms(54)

TimerStatus tProhib LNBTS Thisparameterspecifiesthe 0ms(0),5ms(1),10ms(2),15ms 50ms(10)


Prohibit parametert-StatusProhibitof (3),20ms(4),25ms(5),30ms(6),
[36.331]Thistimerisused 35ms(7),40ms(8),45ms(9),50ms
bythereceivingsideofan (10),55ms(11),60ms(12),65ms
AMRLCentityinorderto (13),70ms(14),75ms(15),80ms
prohibittransmissionofa (16),85ms(17),90ms(18),95ms
STATUSPDU (19),100ms(20),105ms(21),110ms
(22),115ms(23),120ms(24),125ms
(25),130ms(26),135ms(27),140ms
(28),145ms(29),150ms(30),155ms
(31),160ms(32),165ms(33),170ms
(34),175ms(35),180ms(36),185ms
(37),190ms(38),195ms(39),200ms
(40),205ms(41),210ms(42),215ms
(43),220ms(44),225ms(45),230ms
(46),235ms(47),240ms(48),245ms
(49),250ms(50),300ms(51),350ms
(52),400ms(53),450ms(54),500ms
(55)

Timer tReord LNBTS Thisparameterspecifiesthe 0ms(0),5ms(1),10ms(2),15ms 50ms(10)


Reordering parametert-Reorderingof (3),20ms(4),25ms(5),30ms(6),
[36.331]Thistimerisused 35ms(7),40ms(8),45ms(9),50ms
bythereceivingsideofan (10),55ms(11),60ms(12),65ms
AMRLCentityfor (13),70ms(14),75ms(15),80ms
reordering,PDUloss (16),85ms(17),90ms(18),95ms
detectionanddelayof (19),100ms(20),110ms(21),120ms
STATUSPDUtransmission. (22),130ms(23),140ms(24),150ms
(25),160ms(26),170ms(27),180ms
(28),190ms(29),200ms(30)

Issue:02M DN0978033 55

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table15 ParametersforprofilesofRLC(Cont.)

Name Short name Object Description Range / Step Default


value

Thistimerdependson
HARQRTTandnumberof
HARQretransmissions.

Profile3of rlcProf3 LNBTS Profile3ofRLCparameters


RLC forDRBsinRLCAMmode
Parameters

PollPDU pollPdu LNBTS Thisparameterspecifiesthe 4(0),8(1),16(2),32(3),64(4),128 64(4)


parameterpollPDUof (5),256(6),infinity(7)
[36.331]TheparameterPoll
PDUdefinesthenumberof
RLCPDUsthataresenton
alogicalchannelbeforethe
RLCpollingbitisset.

RLCProfileId rlcProfileId LNBTS IdentityoftheRLCprofile 3...3,step1 3

TimerPoll tPollRetr LNBTS Thisparameterspecifiesthe 5ms(0),10ms(1),15ms(2),20ms 120ms(23)


Retransmit parametert-pollRetransmit (3),25ms(4),30ms(5),35ms(6),
of[36.331]Thistimerisused 40ms(7),45ms(8),50ms(9),55ms
bythetransmittingsideofan (10),60ms(11),65ms(12),70ms
AMRLCentityinorderto (13),75ms(14),80ms(15),85ms
retransmitapoll.Theused (16),90ms(17),95ms(18),100ms
minimumvalueofthetimer (19),105ms(20),110ms(21),115ms
shallbelargerthanthe (22),120ms(23),125ms(24),130ms
calculatedround-triptime (25),135ms(26),140ms(27),145ms
withconsiderationsofHARQ (28),150ms(29),155ms(30),160ms
retransmissionsandout-of- (31),165ms(32),170ms(33),175ms
sequencearrival.Thevalue (34),180ms(35),185ms(36),190ms
ofthetimershallbelarger (37),195ms(38),200ms(39),205ms
thantwiceofthe (40),210ms(41),215ms(42),220ms
timerReorder. (43),225ms(44),230ms(45),235ms
(46),240ms(47),245ms(48),250ms
(49),300ms(50),350ms(51),400ms
(52),450ms(53),500ms(54)

TimerStatus tProhib LNBTS Thisparameterspecifiesthe 0ms(0),5ms(1),10ms(2),15ms 50ms(10)


Prohibit parametert-StatusProhibitof (3),20ms(4),25ms(5),30ms(6),
[36.331]Thistimerisused 35ms(7),40ms(8),45ms(9),50ms
bythereceivingsideofan (10),55ms(11),60ms(12),65ms
AMRLCentityinorderto (13),70ms(14),75ms(15),80ms
prohibittransmissionofa (16),85ms(17),90ms(18),95ms
STATUSPDU (19),100ms(20),105ms(21),110ms
(22),115ms(23),120ms(24),125ms
(25),130ms(26),135ms(27),140ms
(28),145ms(29),150ms(30),155ms
(31),160ms(32),165ms(33),170ms
(34),175ms(35),180ms(36),185ms
(37),190ms(38),195ms(39),200ms
(40),205ms(41),210ms(42),215ms

56 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table15 ParametersforprofilesofRLC(Cont.)

Name Short name Object Description Range / Step Default


value

(43),220ms(44),225ms(45),230ms
(46),235ms(47),240ms(48),245ms
(49),250ms(50),300ms(51),350ms
(52),400ms(53),450ms(54),500ms
(55)

Timer tReord LNBTS Thisparameterspecifiesthe 0ms(0),5ms(1),10ms(2),15ms 50ms(10)


Reordering parametert-Reorderingof (3),20ms(4),25ms(5),30ms(6),
[36.331]Thistimerisused 35ms(7),40ms(8),45ms(9),50ms
bythereceivingsideofan (10),55ms(11),60ms(12),65ms
AMRLCentityfor (13),70ms(14),75ms(15),80ms
reordering,PDUloss (16),85ms(17),90ms(18),95ms
detectionanddelayof (19),100ms(20),110ms(21),120ms
STATUSPDUtransmission. (22),130ms(23),140ms(24),150ms
Thistimerdependson (25),160ms(26),170ms(27),180ms
HARQRTTandnumberof (28),190ms(29),200ms(30)
HARQretransmissions.

Table16 ParametersforprofilesofPDCP

Name Short name Object Description Range / Step Default


value

Profile1of pdcpProf1 LNBTS Profile1ofPDCPparameters


PDCP Structure
parameters {pdcpProfileId,tDiscard,statusR
eportReq}.

PDCPprofile pdcpProfileId LNBTS IdentityofthePDCPprofile;0 1...1,step1 1


ID specifiesaninvaliddummy
profile.

Statusreport statusRepReq LNBTS Thisparameterdetermines Bit0:eNBStatusReport,Bit 0


required whetheraPDCPstatusreport 1:UEStatusReport,
issentfromPDCPreceiverto
PDCPtransmitter.ThePDCP
statusreportmaybesentfrom
eNBtoUE(eNBPDCPstatus
report)orfromUEtoeNB(UE
PDCPstatusreport).Possible
settings:00:nostatusreport
01:eNBstatusreport10:UE
statusreport11:eNBandUE
statusreport

Issue:02M DN0978033 57

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table16 ParametersforprofilesofPDCP(Cont.)

Name Short name Object Description Range / Step Default


value

Timerdiscard tDiscard LNBTS Thisparameterindicatesthe 50ms(0),100ms(1),150ms 300ms(3)


delaybeforeaPDCPPDU (2),300ms(3),500ms(4),
alongwiththecorresponding 750ms(5),1500ms(6),
PDCPSDUisdiscardedfrom infinity(7)
thebuffer.Thistimershouldbe
setinawaythatthepacket
delaydefinedbytheQCI
characteristicsiskept.The
timercanbedisabledby
settingtheparameterto
disabled.

Profile2of pdcpProf2 LNBTS Profile2ofPDCPparameters


PDCP forRLCAMdataradiobearers
parameters

PDCPprofile pdcpProfileId LNBTS IdentityofthePDCPprofile 2...2,step1 2


ID

Statusreport statusRepReq LNBTS Thisparameterdetermines Bit0:eNBStatusReport,Bit 0


required whetheraPDCPStatusReport 1:UEStatusReport,
issentfromPDCPreceiverto
PDCPtransmitter.ThePDCP
StatusReportmaybesent
fromeNBtoUE(eNBPDCP
StatusReport)orfromUEto
eNB(UEPDCPStatusReport).
Possiblesettings:00-no
StatusReport01-eNBStatus
Report10-UEStatusReport
11-eNBandUEStatusReport

Timerdiscard tDiscard LNBTS Thisparameterspecifiesthe 300ms(0),500ms(1),750ms 750ms(2)


parameterdiscardTimerof (2),1500ms(3),infinity(4)
[36.331]Thisparameter
indicatesthedelaybeforea
PDCPPDUalongwiththe
correspondingPDCPSDUis
discardedfromthebuffer.This
timershallbesetinawaythat
thepacketdelaydefinedbythe
QCIcharacteristicsiskept.The
timercanbedisabledby
settingtheparametertoinfinity.

Profile3of pdcpProf3 LNBTS Profile3ofPDCPparameters


PDCP forRLCAMdataradiobearers
parameters

PDCPprofile pdcpProfileId LNBTS IdentityofthePDCPprofile 3...3,step1 3


ID

58 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table16 ParametersforprofilesofPDCP(Cont.)

Name Short name Object Description Range / Step Default


value

Statusreport statusRepReq LNBTS Thisparameterdetermines Bit0:eNBStatusReport,Bit 0


required whetheraPDCPStatusReport 1:UEStatusReport,
issentfromPDCPreceiverto
PDCPtransmitter.ThePDCP
StatusReportmaybesent
fromeNBtoUE(eNBPDCP
StatusReport)orfromUEto
eNB(UEPDCPStatusReport).
Possiblesettings:00-no
StatusReport01-eNBStatus
Report10-UEStatusReport
11-eNBandUEStatusReport

Timerdiscard tDiscard LNBTS Thisparameterspecifiesthe 300ms(0),500ms(1),750ms 750ms(2)


parameterdiscardTimerof (2),1500ms(3),infinity(4)
[36.331]Thisparameter
indicatesthedelaybeforea
PDCPPDUalongwiththe
correspondingPDCPSDUis
discardedfromthebuffer.This
timershallbesetinawaythat
thepacketdelaydefinedbythe
QCIcharacteristicsiskept.The
timercanbedisabledby
settingtheparametertoinfinity.

2.4.7.2 Alarms

Therearenoalarmsforthisfeaturedefinedinthisrelease

2.4.7.3 Measurements and counters

Table17:CountersfortheLTE9:Servicedifferentiationshowsthecountersforthe
feature.

Table17 CountersfortheLTE9:Servicedifferentiation

PI ID Counter long name (short Description


name)

M8001C235 UEswithbufferedDLdata AveragenumberofUEswithbuffereddatainDLfornon-GBRdata


fornon-GBRDRB radiobearers

M8001C270 MeanPDCPSDUdelayon MeanretentiondelayforaPDCPSDU(DL)insideeNBnon-GBRdata


DLDTCHfornon-GBRDRB radiobearers

Issue:02M DN0978033 59

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table17 CountersfortheLTE9:Servicedifferentiation(Cont.)

PI ID Counter long name (short Description


name)

M8001C420 UEswithbufferedULdata TheaveragenumberofUEswithbuffereddatainULperlogical


fornon-GBRDRB channelgroupidmappedtonon-GBRbearers(QCI5..9)

M8006C18 InitialEPSBearersetup ThenumberofinitialEPSbearersetupattemptspernon-GBR.Each


attemptsfornon-GBR beareroftheE-RABtoBeSetupListIEiscounted.

M8006C36 InitialEPSBearersetup ThenumberofinitialEPSbearersetupcompletionspernon-GBR.


completionsfornon-GBR EachbeareroftheE-RABSetupListIEiscounted.

Additionalcounterscanbederivedfromtheexistingcounters:

AdditionalEPSBearersetupattemptsfornon-GBR
AdditionalEPSBearersetupcompletionsfornon-GBR
EPCinitiatedEPSBearerReleaserequestsfornon-GBRpercause
eNBinitiatedEPSBearerReleaserequestsfornon-GBRpercause

2.4.8 Activating the feature


Thisfeaturerequiresactivation.

2.5 LTE10: EPS Bearers for Conversational Voice


2.5.1 Introduction to the feature
TheLTE10:EPSbearersforconversationalvoicefeatureallowstointroducehigh-quality
managedIMS-basedconversationalvoiceservicesinLTE.Aserviceisabi-directional
trafficstream,orequivalently,asetofseveralassociatedtrafficstreamsbetweenaUE
andaremoteendpoint.Thiscreatestheneedtosupportmultipledataradiobearers(as
providedbytheLTE7:SupportofmultipleEPSbearerfeature),andtosupport
appropriatedataradiobearercombinationsperUE.ForIMS-basedconversationalvoice,
thisbearercombinationconsistsofoneUMDRBwhichcarriesthevoicedata,andone
AMDRBwhichcarriestheassociatedIMSsignaling.
ThefollowingradiobearercombinationsperUEaresupportedbytheevolvedNodeB
(eNB)inLTE10:

SRB1+SRB2+1xAMDRB+1xUMDRB
SRB1+SRB2+2xAMDRB+1xUMDRB
SRB1+SRB2+3xAMDRB+1xUMDRB
SRB1+SRB2+4xAMDRB+1xUMDRB

Thusitispossibletousesimultaneouslytwosignalingradiobearers(SRBs),uptofour
AMDRBsandadditionallyoneUMDRB.

60 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Conversationalvoiceservicesupportisrestrictedtodynamicscheduling.Dynamic
schedulingforUL/DLintheuserplaneconsidersQoSrequirementsandperformsproper
prioritizationtomeetthem,whichmightresultinsomedowngradingoftheservicefor
non-GBRbearers.
ConversationalvoiceisassignedtheQoSClassIndicator(QCI)=1.Therequirements
associatedwiththisQCIaremetbyassigningaGBRbearertothevoicedatastream.
Therefore,theeNodeBevaluatescorrespondingUEcapabilitiesandtherequestedbit
ratevalue,asindicatedviaS1APprocedures,andadmitsGBRbearersifneitherthe
supportedmaximumGBRforQCI=1,northespecificadmissionlimitsforGBRbearers
areexceeded.AnyothertrafficthatisalsomappedtoQCI=1willexperiencethesame
QoS,whilethetraffichandlingisstilloptimizedforconversationalvoicetraffic.Tofully
accountfortheprioritizationrequirementsofconversationaltraffic,theassociatedIMS
signalingpacketstreamhastobeassignedadataradiobearerwithanappropriateQCI.
QCI=5isexpectedtoprovidesufficientproperties.TheeNodeBassumesthataDRBof
sufficientpropertiesisalreadyestablishedwhenitreceivestherequestforestablishing
theconversationalvoiceservice.TheeNodeBdoesnotperformanychecksinthis
respect.
TheupperthroughputlimitoftheGBRserviceindownlinkdirectionisenforcedbythe
PDNgateway.InuplinktheeNodeBassumesthattheGBRthroughputlimitisenforced
intheUE.

2.5.2 Benefits
ThisfeatureenablestheoperatortoofferconversationalvoiceoverLTE.

2.5.3 Requirements

2.5.3.1 Software requirements

Thefollowingsoftwareisneeded:

Table18 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME NS20

SAEGW NG20

UE 3GPPrelease8

NetAct

2.5.3.2 Hardware requirements

Thisfeaturerequiresnoneworadditionalhardware.

Issue:02M DN0978033 61

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.5.4 Functional description


TheLTE10:EPSbearersforconversationalvoicefeatureintroducesarangeofnew
functionstouser-planeradioresourcemanagement:

Delay-basedschedulinginDLandinULforbearerswithQCI=1
OuterloopdelaytargetcontrolinDL
HeadofLine(HOL)estimationinUL
ConsiderationofGBRbearerinMACmultiplexinginDL
Newschedulertype:exhaustiveULFrequencyDomainscheduler
PacketaggregationinUL/DL

AdmissionControlintheeNodeBensuresthataconfigurablenumberofactiveGBR-
DRBsinaradiocellisnotexceeded.Anincominghandoverisrejectedifthisnumber
wouldbeexceededbyanewUEenteringaradiocell.

2.5.4.1 Delay based scheduling in DL and in UL for bearers with QCI=1

ThePDCPlayerintheeNodeBprovidesallIPpacketsreceivedviaS1withatimestamp
thatistakenfromthelocal(system)timeoftheeNodeB.AllIPpacketsreceivedfroma
sourcenodeareprovidedwithatimestampconstructedfromthelocaltimeofthetarget
eNodeB,reducedbyaconfigurablecorrectionvalue.Thesetimestampsareforwardedto
theMAClayerandtakenintoaccountbythescheduler,inordertomeetQoS
requirementswithrespecttomaximumpacketdelay.
Inuplink,thescheduler:

assumesthatconversationalvoicetrafficisidentifiedbyQCI=1
performsprioritizationofconversationalvoicedata,basedonthe(configurable)
packetdelaybudgetasprovidedbycontrolplane,andontheexperiencedwaiting
timeinUE,
providesspecifictreatmentoftheseparatedataradiobearerthatcarriesIMS
signalingandisassociatedwiththeQCI=1bearer.Thisspecifictreatmentrequires
thatQCI=5issetforthebearer.

Indownlink,thescheduler:

providesspecifictreatmentoftheseparatedataradiobearerthatcarriesIMS
signaling.ThisspecifictreatmentrequiresthatQCI=5issetforthebearer.
assumesthatthemaximumadmittedguaranteeddatarateforconversationalvoice
serviceislimitedto250kbit/sperUE.
assumesthattheguaranteeddatarateofadmittedbearerswithQCI=1isalready
enforcedintheEPC,andthattimelytransmissionofcorrespondingdatapacketsis
sufficient.
handlestrafficwithQCI=5eitherwithprioritycorrespondingtosignalingdataoras
regularnon-GBRdataradiobearers(withcorrespondingrelativeweight,if
applicable)dependingonindicationfromthecontrolplane.
considersGBRinadditiontoUEAMBRwhendeterminingthemaximumresource
allocationforaUE.

62 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.5.4.2 Outer loop delay target control in DL

Delay-basedprioritizationdoesnotexplicitlycontroltheprobabilityofpacketsbeing
receivedcorrectlywithinagivendelaytargetvalue.Therefore,amechanismcalled
OuterLoopDelayTargetControl(OLDTC)orOuterLoopDelayBudgetControl(OLDBC)
isprovided.ThismechanismcanbeactivatedusingthedlsOldtcEnableparameter.
OLDTCmodifiesthedelay-basedprioritizationvaluesindependenceofthedelaytarget
excessrate,onaper-UEbasis.So,ifpacketsbelongingtoabearerwithQCI=1
establishedtowardsaUEaretransferredcorrectlywithinthedelaytarget,the
prioritizationvaluesaredecreasedbyasmallamount.Conversely,ifthepacketsexceed
thedelaytarget,theprioritizationvalueisincreased.

2.5.4.3 HOL packet delay estimation in UL

Theheadofline(HOL)packetrepresentstheoldestpacketthathasarrivedina
transmissionbufferoftheUE.ThedelayexperiencedbythisHOLpacketisestimatedby
theeNodeB,inordertomaintaintherequiredQoSandalsotofindanestimationofthe
datavolumeintheUEbufferthatmightbetransmittedtogetherusingpacket
aggregation.IntheUE,inULdirection,thearrivalofapacketinahigherprioritylogical
channeltriggersaschedulingrequest(SR)ifnoULgrantfromeNodeBisavailable,
whereasifanULgrantisavailable,aRegularBSR(BufferStatusReport)issent.The
eNodeBevaluatestheBSRsthatarerelatedtothelogicalchannelgroups(LGC)to
whichthebearerwithQCIismapped.
TheestimatedHOLpacketdelayisbasedonasetofdatawhichincludes:

TheULTTIinwhichaBSR(relatedtotheLGCofinterest)wastransmitted.This
instanceoftimeiscalculatedfromthevaluefoundintheBSR,andtheGBR.
TheULTTIinwhichanuplinktransmissionismadewhichcontainsdatafromthe
UE'sVoIPtransmissionbuffer.ThisvalueisestimatedfromthelastULgrantwhich
containsaGBRportion.
Thisestimateiscorrectedassoonastheexpectedpacketiscorrectlyreceivedby
theeNodeB.
TheULTTIinwhichanSRistransmittedbytheUE.ReceivingsuchanSR
immediatelyafteraBSRwithfillingvalue0indicatesthatthelastreceivedpacket
representedtheheadofline.
OtherrelationsbetweenSRtransmission,BSR,andULpackettransmissionyield
furtherindicationaboutthesituationofthecurrentHOLpacketintheUE's
transmissionbuffer.

ThederivedvalueforHOLpacketdelayintheUE'stransmissionbufferistakeninto
accountbytheULschedulerintheeNodeB.

2.5.4.4 Consideration of GBR bearer in MAC multiplexing in DL

TheMAClayerintheeNodeBisupdatedtosupportservicedifferentiationforbearers
withQCI=1inDL,andtoprovidemultiplexingofdatafrommultiplelogicalchannelsinto
singleMACDLPDUs.Dependingontheconfiguration,datafromthebearerwithQCI=5
iseitherinterpretedasbeingcontroldataorasbeingregularnon-GBRdata.This
combineddatatakessecondpriority,aftercontrolelements,datafromsignalingbearers
andothercontroldata,andbeforedataoriginatingfromnon-GBRbearers,assumingthat
GBRbearersalwayshavehigherpriority.Dataoriginatingfromnon-GBRbearersgets
theresidualcapacitythatisleftunusedbyGBRbearers.

Issue:02M DN0978033 63

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.5.4.5 New scheduler type: exhaustive FD scheduler

Inuplink,analternativetotheRoundRobinschedulerisintroduced,whichisthe
exhaustiveULFrequencyDomainscheduler.
Theround-robinschedulerusesatwo-stepapproachtocreatealistofUEs,whichare
candidatesforbeingassignedULresourcesinaTTI.Fromthislist,thescheduler
assignsPRBstotheUEs,startingwiththeentryofhighestpriorityandwalkingthrough
thelistinround-robinfashionforaslongasresourcesareavailable,asdeterminedby
thefastadaptivetransmissionbandwidth(fastATB)function.TheRoundRobin
schedulerallocatesresourcesinafixedsizeofonePRBperallocation,whichmeansits
packetallocationsizeisfixedto1.SincetheRoundRobinschedulermayassign
resourcestoalargenumberofUEs,itmightrunintoashortageofPDCCHspacethatis
requiredtocarrytheassociatedsignalingdata.
TheexhaustiveFrequencyDomainSchedulerselectsasmallnumberofUEs(fewerthan
arespecifiedbytheMax_#_UE_ULparameter)andassignsthemallavailablePRBsfor
theTTIunderconsideration.Thismethodcreateslesssignalingloadandthereforecan
avoidcongestiononPDCCH.Totakethefullbenefitofthis,theexhaustiveFDScheduler
allowstheaggregationoftransportblockscarryingVoIPsamples.
ThetypeoftheuplinkschedulercanbeselectedbytheulsFdPrbAssignAlg
parameter.

2.5.4.6 Packet aggregation in UL/DL

PacketaggregationmeansthatVoIPpacketsarecollectedinabufferandthen
transmittedtogether.Packetaggregationthereforeintroducessomeadditionaldelayin
thetransmissionofVoIPpackets.
PacketaggregationinuplinkrequiresthattheexhaustiveFrequencyDomainScheduler
ischosen.
UEswithestablishedbearerwithQCI=1areprioritizedinschedulingsuchthatdata
belongingtotheQCI=1bearerdonotexperiencemoredelaythanisspecifiedina
configurabledelaytarget.Thequalityexperiencedbynon-GBRtrafficmaybereduced
duetothisprioritization.PrioritizationisappliedtoallkindsoftrafficmappedtoQCI=1.
NoadditionalratecontroloftheGBRtrafficisappliedineNodeB.

2.5.4.7 Bearer establishment

ThevoiceserviceontheGBREPSbearerwithQCI=1(QoSclassindicator)ismapped
toaDRBthatworksonRLCinunacknowledgedmode.
Figure6:EPSbearerestablishmentbyS1AP:E-RABsetuprequestshowsamessage
flowforcreatingthisbearer.TheevolvedNodeB(eNodeB)takestheGBR(guaranteed
bitrate)intoaccount,whichissignaledontheS1interface,forexampleinanS1AP:E-
RABSETUPREQUESTmessage.

64 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Figure6 EPSbearerestablishmentbyS1AP:E-RABsetuprequest

TheS1AP:E-RABSETUPREQUESTmessagehastocontain:

QCI(separatelyforeachEPSbearer)
QCIisdefinedintheE-RABLevelQoSParametersIEandisusedforQCI
interpretation.
GBR(separatelyforeachEPSbearerandeachdirection)
IftheGBRQoSInformationIEismissingforaGBRbearer,thesetupofthisEPS
bearerisrejected.Setupofanyremainingbearersiscontinued.
ARP(allocationandretentionpriority)
ARPisstoredintheeNodeBforlatertransfertoatargeteNodeBduringhandover.

2.5.4.8 Radio admission control thresholds

Twonewthresholdsareintroducedbyradioadmissioncontrol:

GBRthresholdfornewcalls
GBRthresholdforincomingcalls.

TheseadditionalradioadmissionthresholdsforGBRbearerscanbeconfiguredbythe
operatoroncellbasis.
TheuplinkanddownlinkschedulersusetheGBRdelaybudgetfortheirscheduling
decisions.Thedelaybudgetcanbeconfiguredbytheoperator.Non-GBRdata
transmissionmightbereducedtoachievetheGBRforvoiceusers.
DynamicschedulingisappliedforEPSbearerswithQCI=1.
ThesupportofEPSbearerswithQCI=1canbeenabled/disabledpereNodeBviaOAM.

2.5.5 System impacts


ThisfeatureneedstheLTE7:SupportofmultipleEPSbearerfeaturetobeenabled.

Issue:02M DN0978033 65

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.5.6 Sales information


Thisfeatureisoptional.

2.5.7 User interface

2.5.7.1 Parameters

Table19:ParametersfortheLTE10:EPSbearersforconversationalvoicefeatureshows
theparametersimplementedfortheLTE10:EPSbearersforconversationalvoice
feature.

Table19 ParametersfortheLTE10:EPSbearersforconversationalvoicefeature

Name Short name Object Description Range / Default


Step value

MaxNumberQCI1 maxNumQci1D LNCEL Thresholdforthemaximumnumberof 0..200,step 100(for


DRBs(GBRs) rb establishedQCI1-GBR-DRBsinthecell. 1 10MHz
BW)
QCI1-DRBsareadditionaldataradiobearers
inthecellandarealsocheckedagainstthe
thresholdmaxNumActDrb.
Themaximumadditionalmargindependson
thebandwidthofthecell.Thefollowingvalues
areallowed:
5MHzbandwidth0..150
10MHzbandwidth0..200
15MHzbandwidth0..200
20MHzbandwidth0..200
Pleasenotethatthedefaultvalueisnot
suitableforallbandwidths.Therecommended
valuesare:
5MHzbandwidth75
10MHzbandwidth100
15MHzbandwidth100
20MHzbandwidth100
Dependencies:
maxNumQci1Drb+
max(addNumQci1DrbRadioReasHo,
addNumQci1DrbTimeCriticalHo)mustbeless
thanthemarginvaluesfortheusedbandwidth
(seevaluesabove(150,200))

66 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table19 ParametersfortheLTE10:EPSbearersforconversationalvoicefeature
(Cont.)

Name Short name Object Description Range / Default


Step value

AddNumberQCI1 addNumQci1Dr LNCEL Additionalmarginforthemaximumnumberof 0..200,step 15(for10


DRBfor bRadioReasHo activeGBRsinthecellaccessingthecellvia 1 MHzBW)
RadioReasHo handoverwithHO-cause:"HOdesirablefor
radioreasons".Thismarginisaddedtothe
threasoldmaxNumQci1Drb.
Handovertrafficshallhavesomepreference
againstnewupcomingtrafficinthecell.
Themaximumadditionalmargindependson
thebandwidthofthecell.Thefollowingvalues
areallowed:
5MHzbandwidth0..150
10MHzbandwidth0..200
15MHzbandwidth0..200
20MHzbandwidth0..200
Pleasenotethatthedefaultvalueisnot
suitableforallbandwidths.Therecommended
valuesare:
5MHzbandwidth15
10MHzbandwidth15
15MHzbandwidth30
20MHzbandwidth40
Dependencies:
maxNumQci1Drb+
max(addNumQci1DrbRadioReasHo,
addNumQci1DrbTimeCriticalHo)mustbeless
thanthemarginvaluesfortheusedbandwidth
(seevaluesabove(150,200))

AddNumberDrb addNumDrbTi LNCEL Additionalmarginforthemaximumnumberof 0..4200, 60(for10


TimeCriticalHo meCriticalHo activeDRBsinthecellaccessingthecellvia step1 MHzBW)
HOwithHO-cause:"TimeCriticalHO".This
marginisaddedtothethreshold
maxNumActDrb.
Handovertrafficshallhavesomepreference
againstnewupcomingtrafficinthecell.
Themaximumadditionalmargindependson
thebandwidthofthecell.Thefollowingvalues
areallowed:
5MHzbandwidth0..2400
10MHzbandwidth0..2400

Issue:02M DN0978033 67

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table19 ParametersfortheLTE10:EPSbearersforconversationalvoicefeature
(Cont.)

Name Short name Object Description Range / Default


Step value

15MHzbandwidth0..4200
20MHzbandwidth0..4200
Pleasenotethatthedefaultvalueisnot
suitableforallbandwidths.Therecommended
valuesare:
5MHzbandwidth60
10MHzbandwidth60
15MHzbandwidth120
20MHzbandwidth150
Dependencies:
maxNumActDrb+
max(addNumDrbRadioReasHo,
addNumDrbTimeCriticalHo)mustbelessthan
themarginvaluesfortheusedbandwidth(see
valuesabove(2400,4200))

QCITab1 QCITab1 LNBTS TabletotranslatetheS1APparameterQCI1


toQCIcharacteristics.Thisisastructure
includingtheparameters:
delayTarget,dscp,lcgiD,prio,qci,qciSupp,
ScheduleBSD,SchedulePrio

delayTarget delayTarget LNBTS DelayTargetisthemaximumpacketdelay 0(50ms) 3


usedbytheeNBMACschedulingalgorithm. 1(60ms)
PartofthestructureQCITab1. 2(70ms)
3(80ms)
4(90ms)
5(100ms)

Differentiated DSCP LNBTS DifferentiatedServicescodepointvalue 0..63,step1 46


Servicescodepoint associatedwiththeQCI.Possiblevalues
basedontheIETF.Thisparameterispartof
theQCITab1Structure.
Allowedvalues:BE(0),AF11(10),AF12(12),
AF13(14),AF21(18),AF22(20),AF23(22),
AF31(26),AF32(28),AF33(30),AF41(34),
AF42(36),AF43(38),EF(46)

Logicalchannel lcgid LNBTS Logicalchannelgroupidentifierforbuffer 1 1


groupidentifier statusreporting.Thisparameterisusedfor
configurationofthebufferstatusreportsofthe
UEaccording[36.321].Thisparameterispart
oftheQCITab1Structure

68 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table19 ParametersfortheLTE10:EPSbearersforconversationalvoicefeature
(Cont.)

Name Short name Object Description Range / Default


Step value

Priority prio LNBTS ThisparametergivesthepriorityoftheEPS 2 2


beareraccordingTS23.203.Thisparameteris
partoftheQCITab1Structure

QoSClass qci LNBTS QoSClassIdentifier.Thisparameterispartof 1 1


Identifier theQCITab1Structure

QCIsupport qciSupp LNBTS Thisparameterindicateswhetherthegiven disabled 1


QCIissupportedandenabled.Thisparameter (0),
ispartoftheQCITab1Structure enabled(1)

SchedulingBucket scheduleBSD LNBTS ThisparameterisusedtoconfiguretheBucket 0(50ms),1 1


SizeDuration SizeDuration(BSD)oftheUL-scheduler.For (100ms)2
GBRbearersscheduleBSDisusedbytheeNB (150ms)3
andUEfortheULschedulingalgorithm (300ms)4
according[36.321].Thebucketsizeofalogical (500ms)5
channeliscalculatedbyPBR*BSD.This (1000ms)
parameterispartoftheQCITab1Structure.

SchedulingPriority schedulePrio LNBTS Thisparameteristhelogicalchannelpriority 2..16,step 5


fortheMACscheduler.ForGBRbearers 1
schedulePrioisusedbytheenBforthe
schedulingalgorithmandbytheUEfortheUL
schedulingalgorithm.Increasingpriorityvalues
indicatelowerpriorities.Thisparameterispart
oftheQCITab1Structure.

SchedulingType scheduleType LNBTS ThisparameterspecifieshowtheEPSbearer 0 1


withQCI5isscheduled. (SIGNALLI
NG),
FortheschedulingtypeSIGNALLINGthe
bearerishandledlikeSRBs.TheMAClcgidis 1(NON-
setto0andschedulePrioisusedforULand GBR)
DL-scheduling.
FortheschedulingtypeNON-GBRthebearer
ishandledlikeothernon-GBRbearers.The
MAClcgidissettounequal0andthe
scheduleweightisusedforDLscheduling.

Profile101ofPDCP pdcpProf101 LNBTS Profile1ofparametersforRLCUMdataradio


paramters bearers.Thisisastructureincludingthe
parameters:rohcMaxCid,SnSize,tDiscard

ROHCMaximum rohcMaxCid LNBTS Thisparameterconfiguresthemaximum 1..16,step1 4


CID numberofROHCcontextsusedforadata
radiobearerinonedirection.Themaximum
numberofROHCcontextsisalsorestrictedby
theUEcapabilities.

Issue:02M DN0978033 69

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table19 ParametersfortheLTE10:EPSbearersforconversationalvoicefeature
(Cont.)

Name Short name Object Description Range / Default


Step value

ThisparameterispartofthepdcpProf101
structure.

SequenceNumber SnSize LNBTS ThisparameterconfiguresthesizeoftheSN 0(7bit), 0


Size fieldinthePDCPheader.IfUEdoesnot 1(12bit)
supportthevalue7bit,thevalue12bitwill
beused.
ThisparameterispartofthepdcpProf101
structure.

TimerDiscard tDiscard LNBTS Thisparameterspecifiestheparameter 0(100ms), 0


discardTimerof[36.331]Thisparameter 1(150ms),
indicatesthedelaybeforeaPDCPPDUalong 2(300ms),
withthecorrespondingPDCPSDUis 3(500ms),
discardedfromthebuffer.Thistimershallbe 4(750ms),
setinawaythatthepacketdelaydefinedby 5(1500ms),
theQCIcharacteristicsiskept.Thetimercan 6(infinity)
bedisabledbysettingtheparametertoinfinity.
ThisparameterispartofthepdcpProf101
structure.

Profile101ofRLC rlcProf101 LNBTS Profile1ofRLCparemetersforDRBsinRLC


Parameters UMmode.Thisisastructureincludingthe
parameters:snFieldLengthDL,
snFieldLengthUL,tReord.

SNFieldLength snFieldLength LNBTS ThisparameterconfiguresthelengthoftheSN 0(5bit), 0


Downlink DL fieldforRLCUMproceduresindownlink 1(10bit)
direction.IfUEdoesnotsupportthevalue
5bit,thevalue10bitisused.
ThisparameterispartoftherlcProf101
structure.

SNFieldLength snFieldLength LNBTS ThisparameterconfiguresthelengthoftheSN 0(5bit), 0


Uplink UL fieldforRLCUMproceduresinuplink 1(10bit)
direction.IfUEdoesnotsupportthevalue
5bit,thevalue10bitisused.
ThisparameterispartoftherlcProf101
structure.

TimerReordering tReord LNBTS Thisparameterspecifiestheparametert- 0(0ms),1 10


Reorderingof[36.331]Thistimerisusedbythe (5ms),2
receivingsideofanUMRLCentityfor (10ms),3
reorderingandPDUlossdetection.Thistimer (15ms),4
dependsonHARQRTTandnumberofHARQ (20ms),5
retransmissions. (25ms),6
(30ms),7

70 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table19 ParametersfortheLTE10:EPSbearersforconversationalvoicefeature
(Cont.)

Name Short name Object Description Range / Default


Step value

ThisparameterispartoftherlcProf101 (35ms),8
structure. (40ms),9
(45ms)10
(50ms)11
(55ms)12
(60ms)13
(65ms)14
(70ms)15
(75ms)16
(80ms)17
(85ms)18
(90ms)19
(95ms)20
(100ms),21
(110ms),22
(120ms),23
(130ms),24
(140ms),25
(150ms),26
(160ms),27
(170ms),28
(180ms),29
(190ms),30
(200ms)

2.5.7.2 Measurements and counters

Table20:CountersfortheLTE10:EPSbearersforconversationalvoicefeatureshows
thecountersfortheLTE10:EPSbearersforconversationalvoicefeature.

Table20 CountersfortheLTE10:EPSbearersforconversationalvoicefeature

PI ID Counter long name (short name) Description

M8001C419 UEswithbufferedULdataforDRBwithQCI1 AveragenumberofUEswithbuffereddata


inULperlogicalchannelgroupidmapped
toVoIP(QCI1)

M8001C420 UEswithbufferedULdatafornon-GBRDRB AveragenumberofUEswithbuffereddata


inULperlogicalchannelgroupidmapped
tonon-GBRbearers(QCI5..9)

2.5.8 Activating the feature


Thisfeaturerequiresactivation.ForinstructionsseeActivatingLTEFeatures.

Issue:02M DN0978033 71

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.6 LTE11: Robust header compression


2.6.1 Introduction To The Feature
ThefeatureLTE11:RobustheadercompressionintroducestheROHCforEPSbearers
withQCI=1,thesearebearersforvoiceoverIP.ForthosebearersthepayloadoftheIP
packetsisalmostofthesamesizeorevensmallerthantheheader.Overtheend-to-end
connection,comprisedofmultiplehops,theseprotocolheadersareextremelyimportant,
butoverjustonelink(hop-to-hop)theseheaderswillbecompressed(and
decompressedattheotherendofthelink).ApplicationofROHCovertheairlinkis
possiblebecauseIP/UDP/RTPheaderinformationisnotrequiredforrelayingdataover
theairinterfacetothereceivingUE.
ThisfeaturesupportsROHC(Robustheadercompression)forIP/UDPandIP/UDP/RTP
headers.ItisdescribedintheRFC3095andRFC4815.
TheIPoverheadoftheIPv4orIPv6is40respective60bytes.ROHCreducesthese
valuesto2..5bytes(thisisatypicalaveragevalue).

2.6.2 Benefits
Themainbenefitforoperatorandcustomerisaconsiderablereductionoftheoverhead
beingtransmittedovertheairinterfaceinUL/DLinadditiontothevoicedata,i.e.,the
IP(v4/v6))/RTP/UDPheaders

2.6.3 Requirements

2.6.3.1 Software Requirements

Thefollowingsoftwareisneeded:

Table21 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

UE 3GPPrelease8

NetAct

72 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.6.3.2 Hardware Requirements

Thisfeaturedoesnotrequireanyneworadditionalhardware.

2.6.4 Functional Description

2.6.4.1 Short Description of ROHC

TheROHCalgorithmestablishesacommoncontextatthecompressorand
decompressorbytransmittingfullheaderandthengraduallytransitiontohigherlevelof
compression.ROHCisdesignedtobeflexibletosupportseveralprotocolstacksand
eachprotocolstackdefinesaprofile withintheROHCframework.
ThefollowingROHCprofilesaresupportedbythisfeature:

ROHCuncompressed(RFC4995),
ROHCRTP(RFC3095,RFC4815),
ROHCUDP(RFC3095,RFC4815)..

Theprotocolheadersarecompressedduetoredundancyintheheaderfieldsof
consecutivepacketsofthesamepacketstream.Apacketclassifiercanidentifydifferent
packetstreamsbythecombinationofparameterslikeprotocolheadersbeingcarriedin
thepacket,thesourceanddestinationaddressesetc.
Initially,afewpacketsaresentuncompressedandareusedtoestablishthecontexton
bothsidesofthelink.Thecontextcomprisesinformationaboutstaticfields,dynamic
fieldsandtheirchangepatterninprotocolheaders.Thisinformationisusedbythe
compressortocompressthepacketasefficientlyaspossibleandthenbythe
decompressortodecompressthepackettoitsoriginalstate(seeFigure7:Principleof
ROHC)

Figure7 PrincipleofROHC
Theconceptofflowcontextinheadercompression:

Packetflow
eNB UE

Compressedpackets
Header Header
Compression Compression
Packetflowin feedback
Downloaddirection
Context Context

Figure7:PrincipleofROHCshowsthedownloaddirection,thereisalsoROHCinthe
uploaddirection.

Issue:02M DN0978033 73

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

TheROHCcompressoroperatesin3states:InitializationandRefresh(IR),FirstOrder
(FO)andSecondOrder(SO).Thestatesdescribetheincreasinglevelofconfidence
aboutthecorrectnessofthecontextatthedecompressorside.Theconfidenceis
reflectedintheincreasingcompressionofpacketheaders.Incaseoferrorconditions,as
indicatedbythedecompressorusingfeedbackpackets,thecompressorcanmovetoa
lowerstatetosendpacketsthatcarryenoughinformationtofixtheerrorinthecontextof
thedecompressor.
ThecompressoralwaysstartsintheIRstate.Inthisstate,itsendsuncompressed
packetstoestablishthecontextatthedecompressorside.Onceitgainsconfidencethat
thedecompressorhasthecontextinformation,itmovestohigherstatesofoperation,
eitherviaFOstatetoSOstateordirectlytoSOstate,Figure8:CompressorStates.

Figure8 CompressorStates

Thedecompressorstatesareshowninthefollowingfigure,Figure9:Decompressor
States

Figure9 DecompressorStates

ROHCcanruninthefollowingModes:

Table22 ModesofROHC

Mode Description

U-Mode InUnidirectionalmode,packetsaresentinonedirection,fromthe
compressortothedecompressor.Incaseswherethereturnpathofthe
reservechannelsarenotavailableitrequiresperiodicrefresh.

O-Mode InBidirectionalOptimisticmode,afeedbackchannelisutilized.Itdoesnot
requireperiodicrefresh.

R-Mode InBidirectionalReliablemode,itissuesfeadbackforallcontextupdates.

2.6.4.2 Bearer Establishment

Thenextfigures(Figure10:EPSBearerEstablishmentProcedurebyS1AP:Initial
ContextSetupProcedure(Attach)andFigure11:EPSBearerEstablishmentProcedure
byS1AP:InitialContextSetupProcedure(ServiceRequest))showtheEPSBearer
EstablishmentproceduretriggeredbytheS1APmessageINITIALCONTEXTSETUP
REQUESTaccording3GPP:

74 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Attachprocedure,withoutincludedUEradiocapabilities(Figure10:EPSBearer
EstablishmentProcedurebyS1AP:InitialContextSetupProcedure(Attach)),
Servicerequest,withincludedUEradiocapabilities(Figure11:EPSBearer
EstablishmentProcedurebyS1AP:InitialContextSetupProcedure(Service
Request))

TheInitialContextSetupproceduresupportstheROHCconfigurationforthe
conversationalvoiceGBREPSbearer.Thisincludes:

Checkoftheactivationoftherobustheadercompressionfeature,
CheckoftheROHCbytheUE,
ConfigurationoftheROHCbasedontheUEcapabilitiesandthePDCPprofilefor
conversationalvoiceifaDRBshallbesetupforconversationalvoice,
ConfigurationofROHCbytheRRC:ConnectionReconfigurationprocedure,ifa
DRBshallbesetupforconversationalvoice.

Figure10 EPSBearerEstablishmentProcedurebyS1AP:InitialContextSetup
Procedure(Attach)

Issue:02M DN0978033 75

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Figure11 EPSBearerEstablishmentProcedurebyS1AP:InitialContextSetup
Procedure(ServiceRequest)

InFigure12:EPSBearerEstablishmentProcedurebyS1AP:E-RABSetupProcedure
theestablishmentofabearerbytheS1APE-RABSetupprocedureisshown.This
procedureisinitiatedinthefollowingcases:

ThePDNGWrequesttheadditionofanewdedicatedEPSbearer([3GPP23.401),
e.g.:thesetupofavoicecallbyIMS
TheUErequestsaresourcemodificationthatcausestheadditionofanewdedicated
EPSbearer([3GPP24.301]:
TheUErequeststheadditionofanewPDNconnectionincludinganewdefaultEPS
bearer([3GPP23.401]),e.g.:startofanIMSbasedVoIPapplicationorconnectinga
laptoptoamobilephone.
AdditionallytotheUErequestedPDNconnectivity,PDNGWmightrequestthe
additionofnewdedicatedEPSbearersincombinationwiththeUErequestedPDN
connectivityprocedure([3GPP23.401]

TheE-RABSetupproceduresupportstheROHCconfigurationfortheconversational
voiceGBREPSbearertobeestablished.Thisincludes

Checkoftheactivationoftherobustheadercompressionfeature,
CheckofthesupportofconversationalvoicebytheUE,
ConfigurationoftheROHCbasedontheUEcapabilitiesandthePDCPprofilefor
conversationalvoice
ConfigurationofROHCbytheRRCConnectionReconfigurationprocedure.

76 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Figure12 EPSBearerEstablishmentProcedurebyS1AP:E-RABSetupProcedure

2.6.4.3 PDCP Adaptation for ROHC

TheeNBsupportsPDCPControlPDUforinterspersedRoHCfeedbackpackets.The
ROHCfeedbackpacketexchangeisonlyneededforVoIPserviceswhicharesubjectof
headercompressionprofiles.
Thecompressorhasthefollowingattributes:

Itisconfigurablebythelayer3,
ItstartsinU-modeoperation,
Ittransitsbetweenthedifferentmodesaccordingtothefeedbackprovidedbythe
decompressor(UEside),
Itinterpretsandreactsaccordingtoinformationprovidedthroughfeedbackpackets
receivedbythedecompressor(UEside),
Ittransits(upward/downward)betweencompressorstates,i.e.IR-/FO-/SO-state.

FurthermoretheeNBsupportsafeedbackchannelfortheROHC.Thischannelis
mandatoryinO-modeorR-modeofoperation.
TheHeaderRefreshfeatureisafurtherattributeofthecompressor:

headerrefreshesaccordingtoRFC2507,consideringthenumberofpacketsinone
periodandthenumberoftransmittedfullheaders.
theheaderrefreshesapplyforFO-stateandSO-state(i.e.inIR-statefull-headers
areanywaytransmitted).

TheeNBsupportstimerbaseddownwardtransitionfromSO-statetoFO-stateaswellas
timerbaseddownwardtransitionfromSO-/FO-statetoIR-state.
TheeNBsupportsaheaderdecompressorforULdatatransfer:

itisconfigurablebylayerL3,
itstartswithU-modeofoperation,

Issue:02M DN0978033 77

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

itprovidesfeedback(ifapplicable)whicharerelavantforthecompressoronUEside
(e.g.modechangesetc.),
ittransits(upward/downward)betweendecompressorstates,i.e.nocontext,static
contextandfullcontext.

TheeNBsupportsthedecompressorstates:

Theno-context,static-contextandfull-contextstates,.
Thedecompressorstartswiththeno-contextandtransitstohigherstates(no
restrictionforanykindoftransit),
Thedecompressordecidesautonomouslyaboutanystatetransition,
Thedecompressorcantransitallthewaytofull-contextonceithassucessfully
decompressedaheader.

2.6.5 System Impacts


Thefollowingfeaturesmustbeenabled:

LTE7:SupportofmultipleEPSbearer,
LTE10:EPSbearersforconversationalvoice..

2.6.6 Sales Information


Thisfeatureisoptional.

2.6.7 User Interface

2.6.7.1 Parameters

Table23:ParametersfortheLTE11:RobustHeaderCompressionshowstheparameters
implementedforthefeatureLTE11:RobustHeaderCompression.

Table23 ParametersfortheLTE11:RobustHeaderCompression

Name Short name Object Description Range / Step Default


value

ActivatePDCPRobust actPdcpRohc LNBTS Thisparameteractivatesthe 0(false), 0


HeaderCompression usageofthePDCPRobust
1(true)
HeaderCompression.

ROHCMaximumCID rohcMaxCid LNBTS Thisparameterconfiguresthe 1..16,step1 4


maximumnumberofROHC
contextsusedforadataradio
bearerinonedirection.Itispart
ofthestructurepdcpProf101.

2.6.8 Activating the Feature


Thisfeaturerequiresactivation.ForinstructionsseetheFeatureActivationManual:
ActivationofLTE11.

78 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.7 LTE13: Rate Capping (UL/DL)


2.7.1 Introduction to the feature
WiththefeatureLTE13:RateCapping(UL/DL)itispossibletorestrictthemaximum
aggregatednonGBRthroughputinuplinkanddownlink.
TheLTE13:RateCapping(UL/DL)featureintroducesthroughputmeasurementfiltersin
ULScheduler(UL-S)andDLScheduler(DL-S).UL-SandDL-ScontroltheUE
throughputaccordingtotheUEavailableaggregatedmaximumbitrate(UE-AMBR)
values.

2.7.2 Benefits
DSLlikechargingmodelscanbeappliedwithLTE.

2.7.3 Requirements

2.7.3.1 Software requirements

Table24 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME NS10CD2

SAEGW

UE 3GPPrelease8

NetAct

2.7.3.2 Hardware requirements

Thisfeaturerequiresnoneworadditionalhardware.

2.7.4 Functional description


TheFlexiMultiradioBTSusestheparameterUEAggregatedMaximumBitRate(UE-
AMBR)whichisinitiallysentfromtheMMEviatheS1AP:INITIALCONTEXTSETUP
REQUESTmessageforitsbitratemanagement.TheUE-AMBRparameterisstoredin
thesubscriberprofileintheHSS.

Issue:02M DN0978033 79

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

TheFlexiMultiradioBTSlimitstheuplinkanddownlinkbitrateofallnon-GBREPS
bearersperUEtothelevelofthesignaledUE-AMBR.TheFlexiMultiradioBTS
considerstheaggregatedthroughputasaveragedoveronesecondperiod.
TheinitiallyassignedQoSparameterUE-AMBRcanbeaswellchanged.Itcanbe
increasedordecreasedbytheMME.
TheFlexiMultiradioBTSsupportsthefollowingS1APmessagesforthis:

UEcontextmodificationrequest
UEcontextmodificationresponse
UEcontextmodificationfailure

TheMMEmayalsochangetheUE-AMBRparameteratthefollowingprocedures(which
arenotinthescopeofthisdocument):

E-RABSETUPREQUEST
E-RABRELEASEREQUEST
PATHSWITCHREQUEST

Thefollowingperformancecountersaresupportedinordertotrackthefunctionality:

numberofUEcontextmodificationrequest
numberofsuccessfulmodificationrequest
numberofunsuccessfulmodificationspercause

ThechangeoftheUE-AMBRparametertriggersare-initializationoftheUE-AMBR
calculationprocedure.Theoperatorcanenable/disablethefunctionalityoncellbasisby
O&Msettings.
eNB supports rate capping in UL and DL scheduling
Uplinkanddownlinkschedulerisabletolimitthebitrateofallnon-GBREPSbearersper
UEtothelevelofthesignaledUE-AMBR.Theaggregatethroughputofallnon-GBR
EPSbearersisaveragedovertimeforcomparisontoUE-AMBR.
Assoonastheaverageaggregatebitrateofallnon-GBRbearersexceedsthesignaled
UE-AMBR,themaximumrateasscheduledtoaUEislimitedonaper-subframebasis
untiltheaverageaggregatebitratedropsagainbelowthevalueoftheUE-AMBR.
ChangesoftheUE-AMBRresultingfromchangestothebearercombinationofaUEor
fromUEcontextmodificationareindicatedtotheratecappingfunctionalityinschedulers
immediatelyandconsideredaccordingly.

UE-AMBR Modification by S1AP UE CONTEXT MODIFICATION REQUEST


TheFigure13:UE-AMBRModificationProcedureshowstheUE-AMBRModification
proceduretriggedbytheS1APmessageUECONTEXTMODIFICATIONREQUEST.

80 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Figure13 UE-AMBRModificationProcedure

UE eNB MME

TriggerfromHSS:
InsertSubscriberData

S1AP:UECONTEXTMODIFICATIONREQEST
UE-AMBR

CheckofUE-AMBR
modification

Reconfigurationof
UE-AMBRratecapping

S1AP:UECONTEXTMODIFICATIONRESPONSE
UpdateBearer

TheprocedureforUE-AMBRmodificationistriggeredbyInsertSubscriberDatafrom
HSStoMME.MMEreceivesanewSubscribedUE-AMBR.Theprocedurestartsin
eNBwhentheeNBreceivestheS1APmessageUECONTEXTMODIFICATION
REQUESTfromtheMMEandtheinformationelementUEAggregateMaximumBit
Rateisincluded.FirsteNBcheckswhetherthefeatureUE-AMBRmodificationis
activatedandtheninformstheratecappingfunctionofULandDLschedulersaboutthe
modifiedUE-AMBR.TheeNBsendsaS1APacknowledgementUECONTEXT
MODIFICATIONRESPONSEtotheMME.TheMMEmaystartanUpdateBearer
proceduretowardstheServingGatewayorPDNGateway.

2.7.5 System impacts


TheLTE13:RateCapping(UL/DL)featurehasnoadditionalimpactonthesystem.

2.7.6 Sales information


ThisfeaturebelongstotheApplicationSoftware(ASW)productstructureclass.

2.7.7 User interface

2.7.7.1 Parameters

Table25:ParametersfortheLTE13:RateCappingULshowstheMMEparameters
requiredbyULratecappingfeatureinUplinkSchedulerUL-S.

Table25 ParametersfortheLTE13:RateCappingUL
Name Short name Object Description Range / Default
Step value
Enablerate rcEnableUl LNCEL Enabling/disablingofrate 0(false),1 false
cappingin cappinginuplink. (true)
uplink

Issue:02M DN0978033 81

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table25 ParametersfortheLTE13:RateCappingUL(Cont.)
Name Short name Object Description Range / Default
Step value
Rate rcAmbrMgnUl LNCEL Marginfactorforthe 1.00..1.50, 1.02
capping comparisonofthemeasured step0.01
AMBR AMBRandtheUEAMBRin
marginin uplink.
uplink

Table26:ParametersfortheLTE13:RateCappingDLshowstheMMEparameters
requiredforratecappingfunctionalityinDownlinkSchedulerDL-S.

Table26 ParametersfortheLTE13:RateCappingDL
Name Short name Object Description Range / Step Default
value
EnableDL rcEnableDl LNCEL Enabling/disablingofrate 0(false),1 false
rate cappinginDL. (true)
capping
DLrate rcAmbrMgnDl LNCEL Factortocalculatemargin 1.00..1.50, 1.03
capping forAMBRtoaccountfor step0.01
AMBR overheadofPDCPand
margin RLC.

2.7.7.2 Alarms

Therearenoalarmsrelatedtothisfeature.

2.7.7.3 Measurements and counters

Therearenomeaserementsandcountersrelatedtothisfeature.

2.7.8 Activating the feature


Thisfeaturerequiresactivation.
Formoreinformationontheactivation,seeActivatingLTERL10Features

2.8 LTE22: Emergency Call Handling


2.8.1 Introduction to the Feature
ThefeatureLTE22:EmergencyCallHandlingre-usesLTE562toprovideregulatory
requirementsininitialphaseofLTEimplementation.Tograntproperhandlingof
emergencycallUEwillberedirectedfromLTEtoanotherCScapableRAT(WCDMAor
GSM).ThisactionistriggeredbyMMEsendingCSFallbackHighPriorityindicationto
eNB.AsaconsequenceUEwillberedirectedtoanotherRATbyreusingLTE562
solution(butwithaseparatelyconfigurableUEprioritiesdependent
RedirectedCarrierInfoIE).Inaddition,oneseparateadmissionthresholdisusedforUEs
sendingRRCCONNECTIONREQUESTmessagewithestablishmentCausesetto
'emergency'.Thisfeaturecanbeswitchedon/offbyoperator.

82 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.8.2 Benefits
Fulfillmentofregulatoryrequirements.

2.8.3 Requirements

2.8.3.1 Software Requirements

Table27 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME NS20

SAEGW

UE 3GPPrelease8

NetAct

2.8.3.2 Hardware Requirements

Table28 Hardwarerequirementsfordifferentnetworkelements

Network element Required hardware

MME ...

eNodeB FSMR2orFSMR3

UE ...

2.8.4 Functional Description

2.8.4.1 Functional Overview/Details

EmergencycallishandledthroughCSfallbackproceduretoGSMortoWCDMA.The
redirectionisappliedastheinter-RATmobilitymechanism.TheFlexiMultiradioBTS
supportsemergencycallhandlingwhenRRCconnectedorRRCidleinadvanceto
emergencycallsetup:

TheMMEnotifiestheeNBabouttheemergencycallbyCSFallbackHighPriority
indicationbyinitialcontextsetuporbyUEcontextmodificationprocedures.

Issue:02M DN0978033 83

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

TheeNBevaluatestheRRCconnectionestablishmentcauseintheRRCconnection
requestmessageinordertoidentifyemergencycallswhenthecallsetupstartsfrom
theidlestate.Separateemergencyadmissioncontrolthresholdswillbeappliedby
theestablishmentofemergencycallrelatedRRCconnection.Capacitylicenseshall
notrejectprocessingofemergencycall.

TheemergencycallhandlingreusesthefeatureLTE000562:CSfallbackbyredirection
toWCDMAorGSM.
Theseparatepriorityforemergencypurposeperlayerisoperatorconfigurable.The
applicabletargetlayersforemergencypurposemusthaveseamlesscoverageoverthe
coverageofthesourceLTEcell.ThusforexamplefullsetofreusedBCCHcarriersis
recommendedinthecaseofGSMtargetlayer.Theemergencycallfeaturesupports
3GPPdefinedUEbehaviorforscopingunsuccessfulredirectionscenarioforemergency
purpose.
Thefollowingcountersareprovidedoncelllevel:

NumberofSignallingConnectionEstablishmentattemptsforemergencycalls
NumberofSignallingConnectionEstablishmentcompletionsforemergencycalls
NumberofSignallingConnectionEstablishmentfailuresforemergencycallsdueto
missingRB(RadioBearer)resources
NumberofCSFallbackattemptsforemergencycallwithredirectionviaRRC
ConnectionRelease

Thefeaturecanbeenabled/disabledviaO&M.

2.8.4.2 Emergency Call Handling

ThisfeatureisverysimilartoCSFallbackwithredirection,describedinLTE562.
Significantdifferencesare:

FeatureLTE22isenabledandproperlyconfiguredineNB
Operatormayconfiguredifferentredirecttargets(ordifferenttargetpriorities)thanfor
LTE562
MMEusesCSFallbackHighPriorityindicationincaseofEmergencyCall
IncaseUEisinidlemode,eNBcheckstheRRCConnectionRequestforcall
establishmentcauseandincaseitis'Emergency',thenaseparateadmission
thresholdisusedandcallswillnotberejectedduetocapacitylicenselimitations

2.8.4.3 Emergency Call Support

eNodeBsupportsCS-FallbackprocedureusingRRCConnectionReleasewith
redirectiontoanoperatorspecifiableRAT&frequencyifUEorMMEinitiatesan
emergencycall.

2.8.4.3.1 Emergency Call trigger

EmergencycalltriggerforeNB:

MMEissendingCSFallbackIndicatorIEwithvalue'CSFallbackHighPriority'

84 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

IncaseUEisidlemode,eNBchecksRRCConnectionRequestforcallestablishment
causeandincaseitis'Emergency',thenaseparateadmissionthresholdisusedand
callswillnotberejectedduetocapacitylicenselimitations.

2.8.4.3.2 Initiation of CS Fallback with Redirect due to Emergency Call

CSFallbackwithRedirectwillbeinitiatedbytheeNBwhenCSFallbackIndicatorwith
value'CSFallbackHighPriority'willbereceivedfromMME.

2.8.4.3.3 Selection of target Radio Access Technology for Emergency Call

eNBshallcheckO&MparametersprovidedinMOCREDRTandchoosetargetRAT
accordingtoemerCallPrioandredirRATparameters.First,parameterwithhighest
priorityofemerCallPriowillbetakentoconsideration,wherevalue1meanshighest
priorityandhighervalueslowerpriority.Whenthisparameterissetto'notused',such
RATtargetwillnotbeusedforCSFallbackwithredirection.eNBbuiltsalistof
redirectiontargetRATdefinitionsstartingwithlowestvaluesofemerCallPrioparameter,
whichhasuniquevalues,sothatlistcanbebuildinunambiguousway.TargetRATsthat
arenotavailableinUECapabilitiesinformationwillbeexcludedfromthatlist.Each
elementonthelistwillbeaninstanceofMOCREDRTandRedirectedCarrierInfoIEwill
bebuiltaccordingtoredirRATparameter.
IfredirRAT=geraneNodeBbuildstheIERedirectedCarrierInfousingsamemechanism
asforUEContextReleasewithredirection.eNodeBcontructsCarrierFreqsGERANfrom
O&MparametersredirGStartingARFCN,redirGBandIndicatorandredirGARFCNValue.
ForthiseNodeBcheckswhethertheselectedcarrierFreqsarewithinan
SupportedBandGERANlistedintheUE-Capabilities.Thisisdonebycheckingwhether
theARFCN-ValueGERANincludedinCarrierFreqsGERANiswithinoneofthe
SupportedBandGERANlistedintheIRAT-ParametersGERANinUE-Capabilities.Ifthe
selectedcarrierFreqsaresupportedbytheUEeNodeBbuildstheIE
RedirectedCarrierInfo.OtherwiseeNodeBretrieswiththesecondarytarget.
IfredirRAT=utra-FDDeNodeBbuildstheIERedirectedCarrierInfousingsame
mechanismasforUEContextReleasewithredirection.eNodeBusesARFCN-
ValueUTRAfromredirFreqUtra.ForthistheeNodeBcheckswhethertheselected
ARFCN-ValueUTRAiswithinanSupportedBandListUTRA-FDDlistedintheUE-
Capabilities.IftheselectedARFCNissupportedbytheUEeNodeBbuildstheIE
RedirectedCarrierInfo.OtherwiseeNodeBretrieswiththesecondarytarget.

2.8.4.3.4 Initiating UE Context Release

Afterselectionoftheredirectiontarget,eNodeBinitiatesUEContextReleaseProcedure.
InRRCConnectionReleaseRequest,ReleaseCauseissetto"other"and
redirectedCarrierInfoisset.IdleModeMobilityControlInformationisnotbepresent.In
S1APUEContextReleaseRequesttheCausevaluesaresettoRadioNetworkLayer
(CSFallbackTriggered).

2.8.4.3.5 Emergency Call - Unsuccessful Procedure

RRCConnectionRequestisnotacceptedbyeNBwhenUEmakesInitialAccessinidle
modesituation-ifRACrejectsanemergencycall,thereisnodifferencetothe
subsequentstepscomparedtothecase,thatRACrejectsanormalRRCconnection

Issue:02M DN0978033 85

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.8.4.4 Radio Admission Control (RAC)

RACisadaptedtogiveemergencycallsahigherconnectivityprospective(LTE22).RAC
introducesanew(higher)thresholdforemergencycallhandlinginordertogive
emergencycallsahigherchancetobesuccessfullyestablished.Theseemergencycalls
arehandedoverassoonaspossibletoanotherRATusingtheCSfallback,forexample
theemergencycallisonlyforashorttimeframehostedintheLTEsystem.

2.8.4.4.1 RAC introduces a new Threshold for Emergency Call Handling

ForemergencycallsRACusesanewthreshold,whichisneartothesystemlimitsin
ordertoallowasmuchemergencycallsaspossible,butlowenoughtopreventthe
systemfromoverloadinburstysituations.
ThefollowingthresholdisusedforemergencycallsincaseofeventSRBSetup.This
thresholdisretrievedfromQ&Mdatabaseatstartupandisconsideredonlyifthefeature
LTE22isenabled:

maxNumRrcEmergency-thresholdfornewSRB1requestswithestablishmentcause
"emergency".

2.8.4.4.2 Admission of emergency calls with higher threshold value

TheadmissioncontrolfunctionisexpandedforLTE22"EmergencyCallHandling"bythe
followingcomponents:

RACwillreceiveanew"emergencysessionactive"indicationintheeventSRB
setupfromUEStateHandling
RACwilldefineanewthreshold"maxNumRrcEmergency".
Thisthresholdisconfiguredbyoperator(newO&M-parameter)neartothemax.
possiblesystemlimit.
EmergencysessionsarecountedasadditionalRRC-Connections.
Thenewthresholdusedforemergencycallscancauseahighercountervaluefor
maxNumRrcthanitwouldbepossiblefornormalSRBSetupsrespectiveHOcases.
ThecheckontheenabledfeatureLTE22isdonebyUEStateHandling.RACmust
onlyreflectontheindicationemergencysessionactive.
AfterhandovertoanotherRAT(GSMorWCDMA)theUEisreleasedwiththeevent
UEReleaseandRACwilldecrementtheRRC-counter.

EmergencyCallHandlingisanoptionalfeature.Whenenabled,itisbeactivatedforthe
wholeeNodeB.
Ifthefeatureisenabled,eNBusesseparateAdmissionthresholdforincoming
EmergencyCallsandwilluseCSFallbackwithredirectionprocedureforUEtoredirect
emergencycalltoUTRANorGERAN.Inthiscasecapacitylicenseavailabilitywillnotbe
checked.
Ifdeactivated,eNBwillnotuseseparateAdmissionthresholdforincomingEmergency
Callsandcapacitylicensecheckwillbeperformed,soitwillbehandledasnormalcall
andCSFallbackusagewilldependonLTE562featureactivation.Thisisnotcheckedby
RAC.

86 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.8.4.5 Radio Network Layer (RNL) support for Emergency Call via
Redirection

RNLprovidesnewparametersfor:

featureenabling
definitionofadditionaldedicatedredirectiontargets
prioritisationofredirectiontargets
aseparateadmissioncontrolthresholdforemergencycalls

2.8.5 System Impacts

2.8.5.1 Dependencies Between Features

Thereisnorealfeaturedependencyinthesensethatotherfeaturemustbeactivated,
howeverLTE22featureisreusingimplementationoffeatureLTE562CSFallbackwith
redirection.
ThereisanimpactonthefeatureLTE423becausethetargetpriorityisnolongerderived
fromtheinstancenumberbutfromnewpriorityparameterswithinREDRT.

2.8.5.2 Impacts on Interfaces

2.8.5.2.1 External Interfaces

NewmessagesonS1AParesupported:

UEContextModification
UEContextModificationResponse
UEContextModificationFailure

NewmessagesonRRCaresupported:
Nonewormodifiedmessages.RRC:RRCConnectionReleasewithIE
redirectedCarrierInfoisusedalreadyinRL10forLTE423.

2.8.5.3 Impacts on Network and Network Element Management tools

ThefeatureintroducesthefollowingadditionalO&Mparameters:

FeatureactivationflagenableEmerCallRedironBTSlevel
AdditionalPerformanceCounter

2.8.5.4 Impacts on System Performance and Capacity

2.8.5.4.1 System Performance

CSFallbackwithredirectneedslongerthanthedirectcallsetupinUTRANorGERANas
theUEhastoleavetheLTEcellandreconnecttothetargetnetworkfirstbeforesetting
upthecallasusual.

Issue:02M DN0978033 87

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Thebulkoftheadditionaldelay(2.0s)isrelatedtotheUEcellleaveandreconnection
procedureaftertheUEreceivedtheconnectionreleaserequest.eNBorother
componentsontheLTEsidedonotcontributetothisdelay.
IntotaltheCSFBwithredirectadditionaldelayforamobileterminatedcallislessthan
2.15s,wheretheadditionaldelayisdefinedasthetimefromtheRRCConnection
RequestintheLTEnetworktothePagingResponseinthetargetnetwork.

2.8.5.4.2 System Capacity

SystemcapacityisnotimpactedbyCSFB

2.8.6 Sales Information


Table29 Salesinformation

BSW/ASW License control in network element License control attributes

ASW - -

2.8.7 User Interface

2.8.7.1 Parameters

Table30:ParametersfortheLTE22:EmergencyCallHandlingshowstheparameters
implementedforthefeatureLTE22:EmergencyCallhandling.

Table30 ParametersfortheLTE22:EmergencyCallHandling

Name Short name Object Description Range / Step Default


value

RedirectionPriorityfor emerCallPrio REDRT Thisparameterdefinespriority 1..6


EmergencyCall fortargetRATinselectionof
redirectiontargetduring
EmergencyCallhandling
procedure.

MaxNumberRRC maxNumRrcEmer LNCEL Thresholdforthemaximum 0,1,2,...,840 440


Emergency gency numberofUEsinthecellwhich
mayestablishaRRCconnection
foranemergencycall

EnableEmergencyCall enableEmerCallR LNBTS Theparameterenablesthe ENUMERATE disabled


ViaRedirection edir feature'EmergencyCallVia D(enabled,
Redirection'.Thefeaturecanbe disabled)
onlycreatedifatleastone
redirectiontargetforUTRANor
GSMhasbeencreatedbefore.

88 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table30 ParametersfortheLTE22:EmergencyCallHandling(Cont.)

Name Short name Object Description Range / Step Default


value

ActivateEmergencyCall actEmerCallRedir LNBTS Theparameteractivatesthe 0(Disabled), 0


ViaRedirection feature'EmergencyCallVia 1(Enabled)
Redirection'.Thefeaturecanbe
onlyactivatedifatleastone
redirectiontargetforUTRANor
GSMhasbeencreatedbefore.

NamingAttributeOfMOC redrtld REDRT Thisparameteristhenaming 0..5,step1


REDRT attributeoftheMOCREDRT.

2.8.7.2 Measurements and Counters

Table31:CountersfortheLTE22:EmergencyCallHandlingshowsthecountersfor
EmergencyCallHandling

Table31 CountersfortheLTE22:EmergencyCallHandling

PI ID Counter long name (short Description


name)

M8013C21 NumberofSignallingConnection NumberofSignallingConnectionEstablishmentattemptsfor


Establishmentattemptsfor emergencycalls
emergencycalls

M8013C22 NumberofSignallingConnection NumberofSignallingConnectionEstablishmentcompletionsfor


Establishmentcompletionsfor emergencycalls
emergencycalls

M8013C23 NumberofSignallingConnection NumberofSignallingConnectionEstablishmentfailuresfor


Establishmentfailuresfor emergencycallsduetomissingRB(RadioBearer)resources
emergencycallsduetomissing
RB(RadioBearer)resources

M8016C13 CSFallbackattemptsfor ThenumberofCSFallbackattemptsforemergencycallreason


emergencycallreasonwith withredirectionviatheRRCConnectionRelease
redirectionviaRRCConnection
Release

2.8.8 Activating the Feature


ThefeatureEmergencyCallhandlingneedstobeactivatedwiththeparameter
actEmerCallRedir.IfactivateditappliesforthewholeeNB.
ForinstructionsseeActivatingLTEFeatures.

Issue:02M DN0978033 89

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.9 LTE54: Intra-LTE handover via S1


2.9.1 Introduction to the Feature
ThefeatureLTE54:Intra-LTEhandoverviaS1supportsintereNBintra-LTEhandover
overS1.
WithS1-basedhandover,aUEcanbehandedoverfromoneLTEcelltoanotherLTE
cell(ofanothereNB)withouttheusageoftheX2interface.X2interfacebetweenSource
andTargeteNBmaybenon-existent,notoperableoritsuseforhandovermaybe
forbiddenbyO&M.UnliketheX2-basedhandover,theS1-basedhandoverisroutedvia
theCoreNetworkandthereforeprovidesthepossibilitytotheCoretochangethe
servingMMEand/ortheservingS-GW.

2.9.2 Benefits
ThisfeaturesupportsMMEandS-GWrelocationscenarios.

2.9.3 Requirements

2.9.3.1 Software Requirements

Table32 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME NS20

SAEGW NG20

UE 3GPPrelease8

NetAct -

2.9.3.2 Hardware Requirements

Table33 Hardwarerequirementsfordifferentnetworkelements

Network element Required hardware

MME -

eNodeB FSMR2orFSMR3

90 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table33 Hardwarerequirementsfordifferentnetworkelements(Cont.)

Network element Required hardware

UE -

2.9.4 LTE54: Intra-LTE Handover via S1

2.9.4.1 Functional Overview/Details

ThefollowingS1basedintra-LTEhandoverscenariosaresupportedbytheFlexi
MultiradioBTS:

inter-eNB,intra-MMEandintra-S-GW
inter-eNB,inter-MMEandintra-S-GW
inter-eNB,inter-MMEandinter-S-GW

S1basedhandoverisanalternativehandovermechanismtotheX2basedhandover
whichisusedifX2interfaceisnotavailableorcannotbeusedbecauseCoreNetwork
Nodesneedtoberelocated.SourceeNodeBwilldecidewhetherahandoverisexecuted
viatheX2-InterfaceorviaS1-interface.CoreNetworkisnotcapableofinfluencingthis
decision.However,theoperatorcanforceanS1-basedhandoverbyblacklisting
neighbour-cellsforX2-basedhandoverviaO&MConfiguration.X2-handover
mechanismsarereusedasmuchaspossible.EspeciallyontheAirinterfaceno
differenceexistsatall.S1basedhandoverisapplicabletotheintrafrequencyhandover
aswellastotheinterfrequencyhandover.FortheUEitiseventransparentforS1-
handoveradditionswhetherthehandoverisinterfrequencyorintrafrequency.
ForaS1-handover
1. oneinstanceofLNADJ(underLNBTS)foreachneighboredeNBmustbeinstalled.
2. oneinstanceofLNADJL(underLNADJ)foreachneighboredeNBmustbeinstalled.

2.9.4.2 Handover trigger

Ingeneral,theHandovertriggerforallLTEHandovervariants(S1,X2andintraeNB)is
thesame.ThehandoveristriggeredeitherviaLTEintra-frequencymeasurementsorvia
LTEinter-frequencymeasurements(ifthefeatureisenabled).ThesourceeNBinitiates
theS1-handoverafterreceivingameasurementreportformtheUEbysendinga
S1AP:HANDOVERREQUIREDmessagetotheMME.
TheMMEpreparestheresourcesatthetargeteNBviatheS1AP:HANDOVER
REQUESTmessage.
TheS1AP:HANDOVERCANCELmessageshallbesentbythesourceeNBtotheMME
oncethesourceeNBdecidestocancelanongoingS1handover.ReceiptoftheS1AP:
HANDOVERCANCELACKNOWLEDGEindicatesthattheMMEisreadytotakepartin
anewhandoverprocedure.UponreceivingtheS1AP:HANDOVERCANCEL
ACKNOWLEDGEmessageatthesourceeNB,thesourceeNBshallretrythehandover
towardsanotherhandovertargetcell.
HandoverretriesarebasedonthesamelogicforS1,X2andintraeNBhandovers.

Issue:02M DN0978033 91

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.9.4.3 Handover Target and Mode Selection

SeveraltypesofhandoverprocedurescanbeappliedinLTEdependingontheselected
HOtargetcell.Toselecttheapplicableprocedureitneedstobeconsideredwhether:

targetcellisanLTEcelloracellofanotherRAT(forexampleUTRAN,GERAN,...)
targetcellisservedbyowneNodeBoranotherLTEeNodeB
X2connectiontoTargeteNodeBexists

HandoverTargetselectionisexecutedintwosteps.Thefirststepgivesthetriggerthata
HOshallbeexecuted,definestheurgencyoftheHOandidentifiesaprioritizedlistof
HOtargetcells.ThisisbasedonmeasurementreportsfromtheUEbutdoesnot
considernetworkinternalaspectsasforexampleX2connectivityorthepossibilityto
performdataforwarding.Inthesecondstep,thefinalHOtargetdecisionand,ifneeded,
theretryofHOwithanothercellafterHOpreparationfailureisperformed.Furthermorea
newhandoverpreparationisnotinitiatedbeforeaformerHOpreparationhasbeen
finalized(successfullyorunsuccessfully).

2.9.4.3.1 Handover Mode selection for S1 based handover

WiththenewintroducedfeatureLTE54aHOviaS1ispossiblenow.Dependentonthe
outputfromRRMHandoverAlgorithm,theeNBselectsthehandovertargetcelland
derivethehandovermodefromtheselectedtargetcell.PossibleHOModesare:

IntraenBHO
IntraLTEintereNBHOviaX2
IntraLTEintereNBHOviaS1

CellscanbeexcludedascandidatesforHOtargetcellsforseveralreasons:
-cellsareblacklistedforhandover
-cellsaccordingtotheHOrestrictionlistprovidedbyMME
-barredintraeNBcells
eNodeBcheckswhethertheTargetcellisaknownLTETargetCellbutnoX2Handover
ispossible.Ifthisisfulfilled,IntereNodeBHandoverviaS1isexecuted.Thischeckis
notneccessaryforintraeNodeBTargetcells.ForintraeNodeBTargetcellsalwaysintra
eNodeBhandoverisapplied.X2handoverisconsideredasimpossibleif:

NoconnectiontothetargeteNodeBexists(relatedX2-linkstatusisunavailble).
Thetargetcellislistedinthehandoverblacklistwithattribute"Blacklisted
Topologies"setto"onlyX2".
LTEneighborrelationidentifier(LNREL)existsforthetargetcellwhere
handoverAllowedparameterissetto"onlyS1"or"forbidden"value.
TheUEservingPLMN-IDisnotsupportedinthetargetcell.

2.9.4.4 Handover over S1 interface

SuccessfulIntereNBHandoversovertheS1interfacearecomposedofthesamefour
phasesasX2-basedhandover

Handoverdecision

92 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Handoverpreparation
Handoverexecution
Handovercompletion

2.9.4.4.1 Handover decision

Handoverdecisionismadebasedonevaluationofmeasurementsreportwithinsource
eNB.

2.9.4.4.2 Handover preparation

SendS1AP:HANDOVERREQUIREDmessagetosourceMME.Whenthedecisionhas
beenmadetohandovertheUEtoanothereNodeBviaS1ortoanotherRAT,thesource
eNBshallsendanS1AP:HANDOVERREQUIREDmessagetosourceMMEoverthe
S1interface.
DuringthehandoverpreparationphaseMMEsendsanS1AP:HANDOVERREQUEST
messagetothetargeteNodeBcontainingtheneededparameters.Uponreceivingthis
message,thetargeteNBshallinitiatetheHandoverPreparationphase.WiththeS1AP:
HANDOVERCOMMANDthepreparationphaseisfinished.Thehandoverexecutionis
initiatedbytheMMEwiththeS1AP:HANDOVERCOMMANDmessagetothesource
eNB.

2.9.4.4.3 Handover execution

AfterreceptionofthehandovercommandsourceeNBsendsa
RRC:RRCConnectionReconfigurationmessagetotheUE.
ThisRRCmessageforcestheUEtothenewcell.ThetargeteNBsendsa
S1AP:HANDOVERNOTIFYmessageincaseofasuccessfulhandovertotheMME.

2.9.4.4.4 Handover completion

AftertheRRCCONNECTIONRECONFIGURATIONCOMPLETEmessageisreceived
inthetargeteNB,thesourceeNBreleasestheradioresourceassociatedwiththeUEin
thesourcecellafterrecevingS1AP:UECONTEXTRELEASECOMMAND.
AlsotheRRMofsourcecellisinformedthattheUEhasbeenhandedovertoanother
cell.
TheswitchfromsourcecelltotargetcellisseamlessforS1data.Inparticular,itmay
neitherloosenordestroyanyGTP-UPDU.

2.9.4.5 Data forwarding

2.9.4.5.1 Support of indirect data forwarding

eNodeBsupportsindirectdataforwardingofDLdatafromSourceeNodeBtoTarget
eNodeBviatheS1-interface

Issue:02M DN0978033 93

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.9.4.5.2 Determination of which bearers are subject to data forwarding at source


eNB on HO via S1

BeforeconfiguringtheparametersfortheS1AP:HANDOVERREQUIREDmessage,the
sourceeNBshalldeterminewhichbearersaresubjecttodataforwarding.

2.9.4.5.3 Resource Allocation at Target eNB

ResourceallocationatthetargeteNBinvolvesthefollowingsteps:

configuringS1bearer(s)atthetargeteNBandtheS-GW
configuringSRBsandDRB(s)fortheUEinthetargetcell
configuringmeasurementsfortheUEinthetargetcell
storingAMBRinformation
storingUECapabilityInformation
configuringASsecurityfortheUE
configuringafastmethodtoallowtheUEtosynchronisewiththetargetcell
comparesourceandtargetcellconfigurationstogenerateadeltaconfiguration
generatinganRRC:RRCCONNECTIONRECONFIGURATIONmessagetobesent
totheUEviathesourceeNB
configuringS1bearer(s)atthetargeteNBforDLdataforwardingfromthesource
eNB

2.9.4.6 Performance Counters

PerformancecountersaresupportedpercellinordertotracktheperformanceoftheS1
intra-LTEhandoverviaS1,forexample:

NumberofIntereNBS1-basedHandoverpreparations
NumberoffailedIntereNBS1-basedHandoverpreparationspercause
NumberofIntereNBS1-basedHandoverattempts
NumberofsuccessfulIntereNBS1-basedHandovercompletions
NumberofIntereNBS1-basedHandoverfailurespercause

Performancecountersrelatedtoneighborcellrelatedmeasurementare:

NumberoffailedIntereNBHandoverpreparationspercauseperneighbourcell
relationship
NumberofIntereNBHandoverattemptsperneighbourcellrelationship
NumberofsuccessfulIntereNBHandovercompletionsperneighbourcell
relationship
NumberofIntereNBHandoverfailuresperneighbourcellrelationship

2.9.5 System Impact


Thefeaturehasnoadditionalimpactsonthesystem.

2.9.5.1 Dependencies Between Features

Thereareinterdepedenciesbetweenthefollowingfeatures:

94 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

LTE492:Automatedneighborrelation(ANR)

2.9.5.2 Impact on Interfaces

Thefeaturehasnoadditionalimpactsoninterfaces.

2.9.5.2.1 External Interfaces

NewS1messages

S1AP:HANDOVERREQUIRED
S1AP:HANDOVERREQUEST
S1AP:HANDOVERREQUESTACKNOWLEDGE
S1AP:HANDOVERCOMMAND
S1AP:eNBSTATUSTRANSFER
S1AP:MMESTATUSTRANSFER
S1AP:HANDOVERNOTIFY
S1AP:HANDOVERCANCEL
S1AP:HANDOVERCANCELACKNOWLEDGE
S1AP:HANDOVERFAILURE
S1AP:HANDOVERPREPARATIONFAILURE

2.9.5.3 Impact on Network and Network Element Management tools

ThefeatureintroducesthefollowingadditionalO&Mparameters:

FeatureActivationFlag
PriorityindicatorbetweenX2-HO&S1-HO
Interfacespecificblacklists
needtosetthemebyautoconfigurationand/orconfigurationbyNetact
AdditionalPerformanceCounters

2.9.5.4 Impact on System Performance and Capacity

2.9.5.4.1 System Performance

C-planeproceduretime(alsocalledC-planelatency)andU-planeinterruptionduringa
S1handoverarethesameasforX2handover.Anyadditionaldelayintheoverall
sequenceoccurseitherbeforeorafterthecriticaltimewindow,whichstartswhenthe
sourceeNBreceivestheHOcommandandendswhenthetargeteNBreceivesRRC
ConnectionReconfigurationCompleteandresumesdatatransmissiontotheUE.
Backgroundactivity(forexamplethestatustransferorS-GWchange)viaS1which
takeslongerthaninX2handoverisexecutedinparallelwhiletheUEleavestheinitial
cellandattachestothetargeteNB.Therefore,thesedifferencesbetweenX2andS1
handoverdonothaveimpactonC-planelatencyorU-planeinterruption.

2.9.5.4.2 System Capacity

ThefeaturehasnoadditionalimpactsonSystemCapacity.

Issue:02M DN0978033 95

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.9.6 Sales Information


Table34 Salesinformation

BSW/ASW License control in network element License control attributes

ASW - -

2.9.7 User Interface

2.9.7.1 Parameters

Table35:ParametersfortheLTE54:IntraLTEHandoverviaS1showstheparameters
implementedforthefeatureLTE54:IntraLTEHandoverviaS1.

Table35 ParametersfortheLTE54:IntraLTEHandoverviaS1
Structure
Name Short name Object Description Range / Step Default
value

ActivateintraLTE actLTES1Ho LNBTS Thisparameterenablesthe enabled, disabled


S1basedhandover featureIntraLTEIntereNodeB disabled
HandoverviaS1

HandoverTopology prioTopoHO LNBTS Thisparameterisusedto allequal, allequal


Priority defineprioritiesbetweenthe3 intra>inter,intr
topologyoptionsforintraLTE a>X2>S1,low
handover prioS1
1)IntraeNBHO
2)HOviaX2
3)HOviaS1

SupervisionTimer tS1RelPrepL LNBTS Guardagainstfailureofthe 50,100,... 500ms


ForThePreparation MMEtorespondinpreparation 2000ms
ForIntraLTE phaseofintraLTES1
Handover handover

Blacklistedcellfor blacklistHoL LNCEL Thisisalistofblacklistedintra-


intraandinterfreq frequencyneighbouringcells
HOlist foractivemodemobility.Cells
areidentifiedbytheirPCI.

Blacklistedtopologies blacklistTopo LNCEL "Thisparameterisintroduced allEqual(0), allEqual(0) blacklistHoL


toallowblacklistingforX2- onlyX2(1)
HandoveronlyotherHO
variantsarestillallowedIfset
to""all""therespectiveentryin
blacklistHoLisvalidforall
kindsofHandoverTopology.If
setto""onlyX2"",handoverto

96 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table35 ParametersfortheLTE54:IntraLTEHandoverviaS1(Cont.)
Structure
Name Short name Object Description Range / Step Default
value

therespectiveentryin
blacklistHoLshallonlybe
excludedastargetsforX2-
basedhandoverbutmaystill
beusedastargetforS1based
handover.Thisparameteris
onlyevaluatedforinter
eNodeBtargetcellswhichcan
beusedastargetforX2-
HandoveraswellasforS1-
Handover"

eUTRAcarrier freqEutra LNCEL Thisparametermustbe 0...65535, 65536 blacklistHoL


frequency configuredforaninter- step1
frequencycell.Itwillbetaken
asanintra-frequencycellifthis
parameterissetto
ownCarrierFreq

Rangeofphysical phyCellIdRange LNCEL IndicatesthenumberofPCIs n4(0),n8(1), - blacklistHoL


cellidrange intherange(including n12(2),n16
startPCI).IfParameter (3),n24(4),
rangePCIisonlyone,PCI n32(5),n48
(startPCI)isspecified. (6),n64(7),
n84(8),n96
(9),n128(10),
n168(11),
n252(12),
n504(13),
noRange(14)

Startofphysicalcell phyCellIdStart LNCEL IndicatesthelowestPCIinthe 0...503,step1 - blacklistHoL


idrange range

2.9.7.2 Measurements and Counters

Table36:CountersforLTE54:IntraLTEHandoverviaS1.showsthecountersforLTE54

Table36 CountersforLTE54:IntraLTEHandoverviaS1.

PI ID Counter long name (short Description


name)

M8014C14 IntereNBS1-Handover NumberofIntereNBS1-basedHandoverpreparations


preparations

M8014C15 FailedIntereNBS1-Handover NumberoffailedIntereNBS1-basedHandoverpreparationsdue


preparationsduetotimer toexpiryoftheguardingtimerTS1RELOCprep.

Issue:02M DN0978033 97

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table36 CountersforLTE54:IntraLTEHandoverviaS1.(Cont.)

PI ID Counter long name (short Description


name)

M8014C16 FailedIntereNBS1-Handover NumberoffailedIntereNBS1-basedHandoverpreparationswith


preparationsduetotargeteNB cause"NoRadioResourcesAvailableinTargetCell".
admissioncontrol

M8014C17 FailedIntereNBS1-Handover NumberoffailedIntereNBS1-basedHandoverpreparationsdue


preparationsduetootherreason toreceptionoftheS1AP:HANDOVERPREPARATIONFAILURE
messagewithacauseotherthan"NoRadioResourcesAvailable
inTargetCell."

M8014C18 AttemptedintereNBS1-HO NumberofIntereNBS1-basedHandoverattempts

M8014C19 SuccessfulintereNBS1-HO NumberofsuccessfulIntereNBS1-basedHandovercompletions

M8014C20 IntereNBS1-HOfailuresdueto NumberofIntereNBS1-basedHandoverfailures


timer

M8015C5 NumberoffailedIntereNB ThenumberoffailedIntereNBHandoverpreparationspercause


Handoverpreparationsper perneighbourcellrelationship.Note:PartsoftheHandover
neighbourcellrelationship preparationwillbeexecutedinthetargeteNB.

M8015C6 NumberoffailedIntereNB ThenumberoffailedIntereNBHandoverpreparationsper


Handoverpreparationsper neighbourcellrelationshipduetoexpirationoftherespective
neighbourcellrelationshipdueto guardingtimer.Note:PartsoftheHandoverpreparationwillbe
expirationofguardingtimer executedinthetargeteNB.
TX2RELOCprep

M8015C7 NumberoffailedIntereNB ThenumberoffailedIntereNBHandoverpreparationsper


Handoverpreparationsper neighbourcellrelationshipduetofailuresintheHOpreparationon
neighbourcellrelationshipdueto thetargetside,forexamplecausedby"NoRadioResource
admissioncontrolinthetarget AvailableinTargetcell".Note:PartsoftheHandoverpreparation
eNB willbeexecutedinthetargeteNB.

M8015C8 NumberofIntereNBHandover ThenumberofIntereNBHandoverattemptsperneighbourcell


attemptsperneighbourcell relationship
relationship

M8015C9 NumberofsuccessfulIntereNB ThenumberofsuccessfulIntereNBHandovercompletionsper


Handovercompletionsper neighbourcellrelationship
neighbourcellrelationship

M8015C10 NumberofIntereNBHandover ThenumberofIntereNBHandoverfailurespercauseper


failurespercauseperneighbour neighbourcellrelationship
cellrelationship

98 DN0978033 Issue:02M

LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.10 LTE55: Inter-frequency handover


2.10.1 Introduction to the Feature
ThefeatureLTE55:Supportofinter-frequencyhandoversupportsseveralinter-frequency
handoverscenarios.
eNBsupportsinter-frequencyhandoverinwhichhandoverdecisionisbasedonRSRPor
RSRQ(DLmeasurement).Triggerscanbe"coverageHO"and"BetterCellHO".
Typically,theUErequiresmeasurementgapsforperforminginter-frequency
measurements,dependingontheUEcapability.
UEperformancemeasurementsaredonewhiledatatransmissionbetweentheUEand
thesourceeNBstillcontinues.Therefore,KPIslikeU-planebreakdurationorC-plane
breakdurationdonotdependontheseUEperformancemeasurements,andthesystem
performanceofinter-frequencyHOisexpectedtobethesameasforintra-frequency
HO.

2.10.2 Benefits
Inter-frequencyhandoverallowsservicecontinuityforLTEdeploymentindifferent
frequencybandsaswellasforLTEdeploymentswithinonefrequencybandbutwith
differentcenterfrequencies.Thesecenterfrequenciescanalsocovercaseswith
differentbandwiths,forexample5MHzand10MHz.

2.10.3 Requirements

2.10.3.1 Software Requirements

Table37 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME NS20

SAEGW NG20

UE 3GPPrelease8

NetAct

Issue:02M DN0978033 99

Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.10.3.2 Hardware Requirements

Table38 Hardwarerequirementsfordifferentnetworkelements

Network element Required hardware

MME ...

eNodeB FSMR2orFSMR3

UE ...

2.10.4 Functional Description

2.10.4.1 Functional Overview/Details

Thefollowinginter-frequencyhandoverscenariosaresupportedbytheFlexiMultiradio
BTS:

intra-eNB,inter-frequencyband
intra-eNB,intra-frequencybandwithdifferentcenterfrequency
inter-eNB,inter-frequencybandviaX2
inter-eNB,intra-frequencybandwithdifferentcenterfrequencyviaX2
inter-eNB,inter-frequencybandviaS1(ifenabled)
inter-eNB,intra-frequencybandwithdifferentcenterfrequencyviaS1(ifenabled)

2.10.4.2 Inter-frequency Handover Variants

AslongasRSRPoftheservingcellisaboves-measure,aUEinRRC_Connectedonly
monitorsRSRPoftheservingcell.Belows-measure,theUEperformsmeasurementsas
configuredbytheeNB.Toensuresmobilitytoneighbourcellsinthesamefrequency,
eNBconfiguresintra-frequencyRSRPmeasurementreportingforneighbourcellsinthe
samefrequency.Whentheleveloftheservingcellbecomesworseandthereisno
neighbourcellinthesamefrequencythatisreceivedbytheUEwithproperquality,then
inter-frequencymeasurementsareconfiguredintheUEinordertofindaproperinter-
frequencyneighbourcell.eNBsupportsinter-frequencyhandoverinwhichthehandover
decisionisbasedonRSRPand/orRSRQ(DLmeasurement).
Triggerscanbe"CoverageHO"(A5)and"BetterCellHO"(A3)whereasA3eventsare
implementedforboth,RSRPandRSRQ.Inter-frequencymeasurementsmayneed
MeasurementGaps,dependingontheUEcapability.
TheparametermeasQuantInterFreqdefineswhichquantitytouseforEventA3
measurementstowardsthisfrequencysetinQuantityConfigEUTRA.Thequantitiesused
toevaluatethetriggeringconditionfortheEventA3isconfigurable(RSRP,RSRQor
both).ThevaluesRSRPandRSRQcorrespondtoReferenceSignalReceivedPower
(RSRP)andReferenceSignalReceivedQuality(RSRQ).Thisparameterreferstoevent
A3.Ifsetto"both",twoA3eventswillbeconfiguredwhenmeasuringthiscarrier,oneper
specificmeasurementquantity.

100 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.10.4.2.1 RSRP for A3 event (Better Cell HO)

RSRPDefinition:portionofenergyinareceivedsignalcreatedbytheinclusionofa
referencepattern.Referencesymbolreceivedpowercanbeusedtoestimatetheability
ofareceivertoobtainanddecodeinformationsignalsthatacarriersignaltransports.
TheUEmeasuresitsneighborcellenvironmentinastepwisemanner,suchthat
unnecessarymeasurementsareavoided.ThemeasurementisbasedontheReference
SymbolReceivedPower(RSRP)andonlyiftheRSRPvalueofservingcellfallsbelow
certainthresholdsadditionalmeasurementsareactivated.InbestcaseifRSRPof
servingcellishigherthanRSRP-Threshold-1,onlytheservingcellismeasured,andif
RSRPofservingcellfallsbelowRSRP-Threshold-1allintrafrequencycellsare
measuredaswell.Thismeasurementiseasytoprovide.s-measureisthe3GPP
notationforRSRP-Threshold-1.Nevertheless,themeasurementofotherfrequenciesis
difficulttoprovideandshouldbeavoidedifnotnecessary.Therefore,inter-frequency
measurementsareactivatedwhenRSRPoftheservingcellfallsbelowastilllower
thresholdthanRSRP-Threshold-2.

Table39 Th1andTh2InterFreqarethresholdssetbyO&M

RSRP of serving cell Measurement activities in UE

rsrp(s)>RSRP-Threshold-1 nomeasurementexceptservingcell

RSRP-Threshold-1 intra-frequencymeasurement
>rsrp(s)
>RSRP-Threshold-2

rsrp(s)<RSRP-Threshold-2 intra-frequencymeasurementandinterfrequency
measurements

Transitions:WhentheUEentersRRC_CONNECTEDstate,theeNBsendsa
MeasurementConfigurationwhichincludesthevalueRSRP-Threshold-1,suchthatthe
UEautonomouslystarts/stopsintra-frequencymeasurementswhenrsrp(serv)falls
below/becomeshigherthanRSRP-Threshold-1.Theactivation/deactivationofinter-
frequencymeasurementistriggeredbyanewMeasurementConfigurationmessagethat
theeNodeBsendstotheUE.Forthisreasoninthefirststepwhenmeasurement
configurationissetup,theMeasConfigcontainsatriggerthattheUEadviseswhenthe
RSRP(serv)fallsbelowRSRP-Threshold-2.ThisresultsinaMeasResultfromUE.Asa
consequence,theeNBsendsanewMeasConfigwhichcontainsthedetailsaboutthe
otherfrequenciesthathavetobemeasuredinaddition.Additionally,atriggerisadded,
bywhichtheUEadviseswhenrsrp(serv)becomesbetterthanRSRP-Threshold-2.In
thiscase,whentheRSRPbecomesbetter(thanRSRP-Threshold-2),thenthereisno
needtocontinuemeasuringtheinter-frequencyandwithanewMeasConfigtheinter-
frequencymeasurementsaredeactivated.
ForeachMeasurementObjectaseparateReportConfigBetterCellHORSRPIFis
used,wheretheparametervaluesdefinedatthesameinstanceasfortherelatedInter
FrequencyMeasurementObject.ThenumberofReportConfig'sBetterCellHORSRP
IFisequaltothenumberofInterFrequencyMeasurementobjects.Ifthereexistsno
InterFrequencyMeasurementObjectthannoReportConfig'BetterCellHORSRPIF'is
toconfigure.

Issue:02M DN0978033 101


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.10.4.2.2 RSRQ for A3 event (Better Cell HO)

RSRQDefinition:signalstrengthmetricthatiscalculatedasaratioofthereference
symbolreceivedpowermultipliedbythenumberofphysicalresourceblockstothe
receivedsignalstrengthindicator.Whilethereferencesymbolreceivedpowerisan
indicatorofthewantedsignalstrength,thereferencesignalreceivedqualitytakesalso
theinterferenceintoaccountduetotheinclusionofthereceivedsignalstrength
indicator.
ForeachMeasurementObjectaseparateReportConfigBetterCellHORSRQIFis
used,wheretheparametervaluesdefinedatthesameinstanceasfortherelatedInter
FrequencyMeasurementObject.ThenumberofReportConfig'sBetterCellHORSRQ
IFisequaltothenumberofInterFrequencyMeasurementobjects.

2.10.4.2.3 RSRP for A5 event (Coverage HO)

ForeachMeasurementObjectaseparateReportConfig'CoverageHOIF'isused,where
theparametervaluesaredefinedatthesameinstanceasfortherelatedmeasurement
object.ThenumberofReportConfig'sisequaltothenumberofInterRATMeasurement
objects.IfthereexistsnoInterFrequencyMeasurementObjectorUEdoesnotsupport
EventA5,noReportConfig'CoverageHOIF'needstobeconfigured.Supportingof
EventA5isindicatedifBit14ofparameterfeatureGroupIndicatorsof3GPPIE
UE-EUTRA-Capabiltyissetto1.

2.10.4.2.4 Th2a for deactivation of A3 and A5 events

Th2aisthethresholdforRSRPoftheservingcellforstoppingofInter-RAT(InterFreq)
Measurements.WhenRSRPoftheservingcellbecomesbetterthanTh2a,Inter-RAT
measurementsaredeactivatedforallA3andA5events(RSRPandRSRQ).Inorderto
preventping-pongeffectsitisnecessarythatthevalueofTh2ashallbesomewhat
higherthanTh2_InterFreq

Table40 Th2aInterFreqthresholdsetbyO&M

RSRP of serving cell Measurement activities in UE

rsrp(s)>RSRP-Threshold-2a intra-frequencymeasurementstopped

2.10.4.3 Handover trigger

Thefollowingmeasurementeventsareusedforthemeasurementbasedinter-frequency
handover:

A1-deactivateinter-frequencymeasurements
A2-activateinter-frequencymeasurements
A3-inter-frequencymeasurementsBetterCellHOforRSRPandRSRQ
A5-inter-frequencymeasurementsCoverageHOforRSRP

TheeventsA1andA2areusedtocontrolthestartandstopofinter-frequency
measurementsonthetargetcells.

102 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Thetargetcellsfortheinter-frequencyhandovercanbeconfiguredbytheoperator.
TheeventsA3orA5areusedtoreportsuitableinter-frequencyneighbors.TheUEradio
accesscapabilitiesareconsideredforthemeasurementconfiguration.
Thehandoverthresholds,hysteresismarginsandtimerconstrainsfortheinter-frequency
handoverareO&Mparametersthatcanbeconfiguredbytheoperator.
Theevaluationofmeasurementsreports,thehandoverpreparation,execution,
completionanddataforwardingisidenticaltotheintra-frequencyhandoverviaX2
respectivelyS1.

2.10.4.4 Performance counters

Thefollowingcountersaresupportedpercellinordertotracktheperformanceofthe
inter-frequencyhandover,forexample:

NumberofInter-FrequencyHandoverattempts
NumberofInter-FrequencyHandoverattempts-measurementgapassisted
NumberofInter-FrequencyHandovercompletions
NumberofInter-FrequencyHandovercompletions-measurementgapassisted
NumberofInter-FrequencyHandoverfailures
NumberofInter-FrequencyHandoverfailures-measurementgapassisted

Theinter-frequencyhandoverfunctionalitycanbeenabled/disabledpercellviaO&M.

2.10.5 System Impact


Thefeaturehasnoadditionalimpactsonthesystem

2.10.5.1 Dependencies Between Features

Thereareinterdepedenciesbetweenthefollowingfeatures:

LTE54-Intra-LTEhandoverviaS1(needstobeenabledincaseofinter-frequency
handoverviaS1)

2.10.5.2 Impact on Interfaces

Thefeaturehasnoadditionalimpactsoninterfaces.

2.10.5.3 Impact on Network and Network Element Management tools

ThefeaturehasadditionalimpactsonO&Mparameters:

FeatureActivationFlagforinter-frequencyhandover

2.10.5.4 Impact on System Performance and Capacity

ThefeaturehasnoadditionalimpactsonSystemPerformanceandCapacity.

Issue:02M DN0978033 103


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.10.6 Sales Information


Table41 Salesinformation

BSW/ASW License control in network element License control attributes

ASW - -

2.10.7 User Interface

2.10.7.1 Parameters

Table42:ParametersfortheLTE55:LTEInter-frequencyHandovershowsthe
parametersimplementedforthefeatureLTE55.

Table42 ParametersfortheLTE55:LTEInter-frequencyHandover

Name Short name Object Description Range / Step Default


value

EnableInterFrequency actlfHo LNBTS Thisparameterenablesthe enabled, enabled


Handover featureInterFrequency disabled
Handover

EutraCarrierInfo eutraCarrierInfo LNHOIF IdentifiesE-UTRAcarrier 0,1,...,


frequencyforwhichthis maxEARFCN
configurationisvalid.

EUTRACarrierFrequency freqEutra LNCEL Thisparametermustbe 0...65535,


configuredforainterfrequency step1
cell.Itwillbetakenasaintra
frequencycellifthisparameteris
settoownCarrierFreq.This
parameterispartofthestructure
blacklistHoL.

FilteringCoefficientUsed filterCoefficientRS LNCEL Specifiesthefilteringcoefficient ENUMERATE fc4


ForRSRP RP usedforRSRP D{fc0,fc1,
fc2,fc3,fc4,
fc5,fc6,fc7,
fc8,fc9,fc11,
fc13,fc15,
fc17,fc19,
notUsed,
spare1,}

FilteringCoefficientUsed filterCoefficientRS LNCEL Specifiesthefilteringcoefficient ENUMERATE fc4


ForRSRQ RQ usedforRSRQ D{fc0,fc1,
fc2,fc3,fc4,
fc5,fc6,fc7,
fc8,fc9,fc11,
fc13,fc15,

104 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table42 ParametersfortheLTE55:LTEInter-frequencyHandover(Cont.)

Name Short name Object Description Range / Step Default


value

fc17,fc19,
notUsed,
spare1,}

ThresholdTh2InterFreq threshold2InterFre LNCEL ThresholdforRSRPofserving 0...97dBm


ForRSRP q cellforstartofinterfrequency
measurements

RelatedHysteresisof hysThreshold2Inter LNCEL RelatedHysteresisofThreshold 0,0.5,...15 2dB


ThresholdTh2InterFreq Freq forRSRPofservingcellforstart dB
forRSRP ofinterfrequencymeasurements

ThresholdTh2aForRSRP threshold2a LNCEL ThresholdforRSRPofserving 0...97dBm


cellforstoppingofInter-RAT
(InterFreq)Measurements

RelatedHysteresisof hysThreshold2a LNCEL RelatedHysteresisofThreshold 0,0.5,...15 2dB


ThresholdTh2aForRSRP forRSRPofservingcellfor dB
stoppingofInter-RAT(InterFreq)
Measurements

TimeToTriggerForA1To a1TimeToTriggerD LNCEL Timetotriggerdeactivationofall ENUMERATE


DeactivateInter eactInterMeas measurements D{ms0,
Measurement ms40,ms64,
ms80,ms100,
ms128,
ms160,
ms256,
ms320,
ms480,
ms512,
ms640,
ms1024,
ms1280,
ms2560,
ms5120}

TimeToTriggerForA2To a2TimeToTriggerAc LNCEL TimetotriggeractivationofInter- ENUMERATE


ActivateInter tInterFreqMeas Frequencymeasuremenrts D{ms0,
Measurement ms40,ms64,
ms80,ms100,
ms128,
ms160,
ms256,
ms320,
ms480,
ms512,
ms640,
ms1024,

Issue:02M DN0978033 105


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table42 ParametersfortheLTE55:LTEInter-frequencyHandover(Cont.)

Name Short name Object Description Range / Step Default


value

ms1280,
ms2560,
ms5120}

A3OffsetRSRPInter a3OffsetRsrpInterF LNHOIF HandoverMarginforBetterCell INTEGER(-


Frequency req Handover 30..30)

RelatedHysteresisof hysA3OffsetRsrpInt LNHOIF RelatedHysteresisofHandover 0,0.5,...,15 1dB


offseta3OffsetforRSRP erFreq MarginforBetterCellHandover dB
InterFrequency ofInter-Frequency

A3OffsetRSRQInter a3OffsetRsrqInterF LNHOIF HandoverMarginforQuality INTEGER(-


Frequency req Handover 30..30)

RelatedHysteresisof hysA3OffsetRsrqInt LNHOIF 0,0.5,...,15 1dB


offseta3OffsetforRSRQ erFreq dB
InterFrequency

A3ReportIntervalRSRP a3ReportIntervalRs LNHOIF TheRSRPbasedA3event ENUMERATE


InterFrequency rpInterFreq triggerstheUEtoperform D{ms120,
periodicalreportingwiththe ms240,
indicatedinterval. ms480,
ms640,
ms1024,
ms2048,
ms5120,
ms10240,min
1,min6,
min12,min30,
min60}

A3ReportIntervalRSRQ a3ReportIntervalRs LNHOIF TheRSRQbasedA3event ENUMERATE


InterFrequency rqInterFreq triggerstheUEtoperform D{ms120,
periodicalreportingwiththe ms240,
indicatedinterval ms480,
ms640,
ms1024,
ms2048,
ms5120,
ms10240,min
1,min6,
min12,min30,
min60}

A3TimeToTriggerRSRP a3TimeToTriggerR LNHOIF DurationforwhichtheRSRP ENUMERATE


InterFrequency srpInterFreq basedeventA3mustbevalid D{ms0,
ms40,ms64,
ms80,ms100,
ms128,
ms160,

106 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table42 ParametersfortheLTE55:LTEInter-frequencyHandover(Cont.)

Name Short name Object Description Range / Step Default


value

ms256,
ms320,
ms480,
ms512,
ms640,
ms1024,
ms1280,
ms2560,
ms5120}

A3TimeToTriggerRSRQ a3TimeToTriggerR LNHOIF DurationforwhichtheRSRP ENUMERATE


InterFrequency srqInterFreq basedeventA3mustbevalid D{ms0,
ms40,ms64,
ms80,ms100,
ms128,
ms160,
ms256,
ms320,
ms480,
ms512,
ms640,
ms1024,
ms1280,
ms2560,
ms5120}

A5ReportIntervalInter a5ReportIntervalInt LNHOIF TheRSRPbasedA5event ENUMERATE


Frequency erFreq triggerstheUEtoperform D{ms120,
periodicalreportingwiththe ms240,
indicatedinterval ms480,
ms640,
ms1024,
ms2048,
ms5120,
ms10240,min
1,min6,
min12,min30,
min60}

A5TimeToTriggerInter a5TimeToTriggerInt LNHOIF DurationforwhichtheRSRP ENUMERATE


Frequency erFreq basedeventA5mustbevalid D{ms0,
ms40,ms64,
ms80,ms100,
ms128,
ms160,
ms256,
ms320,
ms480,
ms512,
ms640,
ms1024,

Issue:02M DN0978033 107


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table42 ParametersfortheLTE55:LTEInter-frequencyHandover(Cont.)

Name Short name Object Description Range / Step Default


value

ms1280,
ms2560,
ms5120}

PresenceAntennaPort1 interPresAntP LNHOIF TheIEPresenceAntennaPort1is BOOLEAN


usedtoindicatewhetherallthe
neighbouringcellsuseAntenna
Port1

MeasurementQuantity measQuantInterFre LNHOIF Defineswhichquantitytousefor ENUMERATE RSRP


InterFrequency q EventA3measurements D{RSRP,
towardsthisfrequencysetin RSRQ,both}
QuantityConfigEUTRA

MeasurementBandwidth measurementBand LNHOIF Measurementbandwidth ENUMERATE


width commonforallneighbouring D{mbw6,
cellsonthefrequency mbw15,
mbw25,
mbw50,
mbw75,
mbw100}

ThresholdTh3ForRSRP threshold3InterFre LNHOIF ThresholdforRSRPofserving INTEGER


InterFrequency q cell.IfRSRPofservingvalue< (0...97)
threshold3InterFreqandRSRP
ofneighborcell>
threshold3aInterFreqthen
handoveristriggered(A5event)

ThresholdTh3aForRSRP threshold3aInterFr LNHOIF ThresholdforRSRPof INTEGER


InterFrequency eq neighbourcell.IfRSRPof (0..97)
servingvalue<
threshold3InterFreqandRSRP
ofneighborcell>
threshold3aInterFreqthen
handoveristriggered(A5event)

RelatedHysteresisof hysThreshold3Inter LNHOIF RelatedHysteresisofHandover 0,0.5,...,15 0.5dB


ThresholdsTh3andTh3a Freq MarginforCoverageHandover dB
forRSRPInterFrequency ofInter-Frequency

NamingAttributeOfMOC lnHoIfId LNHOIF Thisparameteristhenaming 0...15,step1


LNHOIF attributeoftheMOCLNHOIF.

2.10.7.2 Measurements and Counters

Table43:CountersfortheLTE55:LTEInter-frequencyHandovershowsthecountersfor
LTE55

108 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table43 CountersfortheLTE55:LTEInter-frequencyHandover

PI ID Counter long name (short Description


name)

M8021C0 Numberofinterfrequency NumberofintraLTEinter-frequencyhandoverattempts.It


handoverattempts comprisestheintraandintereNB.

M8021C1 Numberofinterfrequency NumberofintraLTEinter-frequencyhandoverattemptswhen


handoverattempts measurementgapsareconfiguredfortheUE.Itcomprisestheintra
(measurementgapassisted) andintereNBHandoverscenario.

M8021C2 Numberofsuccessfulinter- NumberofsuccessfulintraLTEinter-frequencyhandover


frequencyhandovercompletions completions.ItcomprisestheintraandintereNBHandover
scenario.

M8021C3 Numberofsuccessfulinter- NumberofsuccessfulintraLTEinter-frequencyhandover


frequencyhandovercompletions completionswhenmeasurementgapsareconfiguredfortheUE.It
(measurementgapassisted) comprisestheintraandintereNBHandoverscenario.

M8021C4 Numberoffailedinter-frequency Numberofinter-frequencyhandoverfailures


handovers

M8021C5 Numberoffailedinter-frequency Numberofinter-frequencyhandoverfailureswhenmeasurement


handovers(measurementgap gapswereconfiguredfortheUE.
assisted)

2.10.8 Activating the Feature


ThefeatureInter-frequencyHandoverneedstobeactivatedwiththeparameter
actIFHo.IfactivateditappliesforallcellsoftheeNB.
ForinstructionsseeActivatingLTEFeatures.

2.11 LTE703: DL adaptive closed loop MIMO for two


antennas
2.11.1 Introduction to the feature
WiththefeatureLTE703:DLadaptiveclosedloopMIMOfortwoantennasspatial
multiplexingmodecanbeselecteddynamicallywhileapplyingclosedloopMIMOfortwo
antennas.

2.11.2 Benefits
Theadaptivealgorithmprovidesthegainofhighpeakrates(twocodewords)andgood
celledgeperformance(singlecodeword).

Issue:02M DN0978033 109


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

ClosedloopMIMOSMtransmissionmodegivesthepossibilitytousetheprecoding
whichoffersoptimalperformanceforcertainUEsbecauseofUE-specificPMIreporting.
ThisisapplicableforbothsingleanddualstreamclosedloopMIMOSMtransmissions.
Incaseofdualstreamtransmission,themodulationandcodingschemecanbeselected
separatelyforbothcodewordsthankstocodewordspecificCQIreportingwhichshould
givesomethroughputgainandbetterachievementoftargetedBLERonPDSCH.

2.11.3 Requirements

2.11.3.1 Software Requirements

Table44 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME -

SAEGW -

UE 3GPPrelease8

NetAct -

2.11.3.2 Hardware Requirements

ThefeaturerequiresaMIMOconfigurationfortheRFmodulesrsp.radioheads.

Table45 Hardwarerequirementsfordifferentnetworkelements

Network element Required hardware

MME ...

eNodeB FSMR2orFSMR3

UE ...

2.11.4 Functional description


Theclosedloopadaptivespatialmultiplexingfortwoantennasallowstodynamically
switchbetweenatransmissionwithsinglecodewordandatransmissionwithdouble
codeword,bothwithintransmissionmode4(formoredetailsonthetransmissionmodes
seeSection7.1in[3GPP-36213]).Thedecisionisbasedonradioconditionsandthe
maincriteriasforitareCQI(Channel Quality Indicator)andRankInformation.

110 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

ClosedloopMIMOrequiresthereceptionofPMI(Precoding Matrix Indicator)inUL


andselectsappropriateprecodinginDL.CL(Closed Loop)MIMOalgorithmissimilar
toOL(Open Loop)algorithmfromRL10,however,itisbasedonseparateparameters
andthresholds.AMC(Adaptive Modulation and Coding)andOLQC(Outer Loop
Quality Control)considerappropriateMIMOcompensationvalues.
OperatorcancontrolalgorithmdecisionsbyconfiguringthresholdsviaO&M(Operation
and Maintenance).ClosedLoopMIMOcanhavedifferentthresholdsdefinitionfrom
OpenLoopMIMOSwitch.
FurtherdetailsontherelatedlayermappingcanbefoundinTS36.211.
SpatialmultiplexingisappliedonlyforthePDSCH.Pre-codingisdoneaccordingtothe
codebookdescribedinTS36.211.ZerodelayCDDissupported.
ThefeatureLTE703:DLadaptiveclosedloopMIMOfortwoantennasisoptionalandit
canbeswitchedon/off.
TheFlexiMultiradioBTSsupportsthefollowingperformancecounterspercell:

MIMOmodedistribution
TotalnumberofMIMOmodeswitches

2.11.5 System impacts

2.11.5.1 Dependencies between features


LTE30CQIadaptation
LTE899AntennaLineSupervision
LTE69TransmitDiversityfor2Antennasrequiredand
LTE70DownlinkadaptiveopenloopMIMOrequired

2.11.6 Sales information


Table46 Salesinformation

BSW/ASW License control in network element License control attributes

ASW - -

2.11.7 User interface

2.11.7.1 Parameters

Table47:ParametersfortheLTE703:DLadaptiveclosedloopMIMOfortwoantennas
showstheparametersimplementedforthefeatureLTE703:DLadaptiveclosedloop
MIMOfortwoantennas.

Issue:02M DN0978033 111


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Table47 ParametersfortheLTE703:DLadaptiveclosedloopMIMOfortwo
antennas

Name Short name Object Description Range / Step Default


value

Downlink dlMimoMode LNCEL "TheusedDLmimomodeforeachphysical SingleTX(0), TXDiv(1)


MIMOMode channelisthefollowing: TXDiv(1),
StaticOpen
0:SingleStreamDownlink:Alldownlinkphysical
LoopMIMO
channelsaretransmittedusingthismode;
(2),Dynamic
1:SingleStreamDownlinkTransmitDiversity:All OpenLoop
downlinkphysicalchannelsaretransmittedusing MIMO(3),
thismode; ClosedLoop
Mimo(4)
2:DualStreamMIMOSpatialMultiplexing:SRB1
(DCCH)andRBs(DTCH)onPDSCHare
transmittedusingDualStreamMIMOwithspatial
multiplexing;SRB0(CCCH),BCCHandPCCH
onPDSCHandallotherphysicalchannelsare
transmittedusingSingleStreamDownlink
TransmitDiversity;
3:DynamicOpenLoopMIMO:SRB1(DCCH)
andRBs(DTCH)onPDSCHaretransmitted
usingeitherSingleStreamDownlinkTransmit
DiversityorDualStreamMIMOwithspatial
multiplexingdependingonradioconditions;
SRB0(CCCH),BCCHandPCCHonPDSCH
andallotherphysicalchannelsaretransmitted
usingSingleStreamDownlinkTransmit
Diversity;
4:DynamicClosedLoopMIMO:SRB1(DCCH)
andRBs(DTCH)onPDSCHaretransmitted
usingeitherSingleStreamDownlinkTransmit
DiversityorSingleorDualStreamMIMOwith
ClosedLoopspatialmultiplexingdependingon
radioconditionsandUEcategory;SRB0
(CCCH),BCCHandPCCHonPDSCHandall
otherphysicalchannelsaretransmittedusing
SingleStreamDownlinkTransmitDiversity"

CQI mimoClCqiThD LNCEL CQIThresholdforfallbacktoclosedloopMIMO 0...16,step 9


thresholdfor singlecodewordtransmission(inCQI) 0.1
fallbackto
CLMIMO1
CWmode

CQI mimoClCqiThU LNCEL CQIThresholdforactivationofclosedloop 0...16,step 11


thresholdfor MIMOdualcodewordtransmission(inCQI) 0.1
activationof
CLMIMO2
CWmode

112 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table47 ParametersfortheLTE703:DLadaptiveclosedloopMIMOfortwo
antennas(Cont.)

Name Short name Object Description Range / Step Default


value

Rank mimoClRiThD LNCEL RankThresholdforfallbacktoclosedloopMIMO 1...2,step 1.4


thresholdfor singlecodewordtransmission 0.05
fallbackto
CLMIMO1
CWmode

Rank mimoClRiThU LNCEL RankThresholdforactivationofclosedloop 1...2,step 1.6


thresholdfor MIMOdualcodewordtransmission 0.05
activationof
CLMIMO2
CWmode

2.11.7.2 Measurements and counters

Table48:CountersfortheLTE703:DLadaptiveclosedloopMIMOfortwoantennas
showsthecountersforLTE703:DLadaptiveclosedloopMIMOfortwoantennas

Table48 CountersfortheLTE703:DLadaptiveclosedloopMIMOfortwoantennas

PI ID Counter long name (short Description


name)

M8010C57 MIMOClosedLoopSingle ThesumofMIMOSingleCodewordmodeusage.


Codeword(MIMO_CL_1CW)

M8010C58 MIMOClosedLoopDouble ThesumofMIMODoubleCodewordmodeusage.


Codeword(MIMO_CL_2CW)

2.11.8 Activating and configuring the feature


Thisfeaturerequiresactivation.ForinstructionsseeActivatingtheLTE703:DLadaptive
closedloopMIMOfortwoantennas.

2.12 LTE562: CSFB to UTRAN or GSM via redirect


2.12.1 Introduction to the feature
TheCSFB(Circuit-SwitchedFallback)functionallowsforaservicebasedredirection
fromLTEtoUTRANortoGERANduringthecallsetups.Bothmobileoriginatedand
mobileterminatedcallsetuparesupported.

Issue:02M DN0978033 113


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

ThisfeatureisusedtokeepCS(CircuitSwitched)servicevoicecontinuityintheinitial
phaseofLTEimplementation,whichdoesnotsupportCSservices.Asaconsequenceof
thisfeature,theUEleavesanLTEnetworkandishandledbyRAT(RadioAccess
Technology)capableofCSservice.

2.12.2 Benefits
TheCSinvestmentscanbereusedintheinitialphaseofLTE.Theredirectionprocedure
isthesimplestimplementationintermsoftheIRATinter-workingfunctionality.

2.12.3 Requirements
AnupgradeoftheeNodeB, MME,andSGWisaprerequisiteforCSFBsupport.CSFBis
onlyavailablewhentheLTEnetworkcoverageoverlapswitheitherGSM/EDGEradio
accessnetwork(GERAN)orUMTSterrestrialradioaccessnetwork(UTRAN).

2.12.3.1 Software Requirements

Thefollowingsoftwareisrequired:
Table49:Softwarerequirementsfordifferentnetworkelementsshowsthesoftware
requirementsfordifferentnetworkelementsforthefeatureLTE562:CSFBtoUTRANor
GSMviaredirect

Table49 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME NS20

S-GW NG20

UE 3GPPrelease8

NetAct

2.12.3.2 Hardware Requirements

Thisfeaturedoesnotrequireanyneworadditionalhardware.

2.12.4 Functional description

114 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.12.4.1 Functional overview

TheCSvoiceservicecontinuityisimplementedthroughservicetriggeredredirection
fromLTEtoUTRANorGERANformultimodedevice.Bothmobileoriginatedandmobile
terminatedscenariosaresupported.
AsprerequisiteEPC(EvolvedPacketCore)mustsupportCSinter-workingformobility
managementandpaging.
BothintheMO(Mobile-Originated)andintheMT(Mobile-Terminated)case,theMME
indicatestheCSfallbackscenariototheeNodeB.Packetbasedservicesmaybestarted
againafterCSFBdependingonthecapabilityofthetargetradionetwork.
WheneveraCSserviceforUEisrequested,theeNodeBmovestheUEto Idlefirstwith
aninformationonwhichcarrieritshouldtrytoaccessthetargetUTRAN/GERANcell.
Theoperatorcanconfigureprioritiesforthetargetfrequencybandspercell.TheeNodeB
selectsthehighestprioritylayersupportedbythemultimodedevice.Figure14:Message
sequenceandtimedelayduringCSFBredirectionshowstheCSFBredirectionprocess.

Figure14 MessagesequenceandtimedelayduringCSFBredirection

UE/MS eNB MME

RRC_IDLE Paging
Paging

RandomAccesssequence

RRCConnection
Request
RRCConnection
SetupRequest
RRCConnectionSetup
LTEadditionaldelay

Complete(incl.NASExt. S1AP:InitialUEMessage
ServiceRequest) (incl.NASExt.ServiceRequest)
S1AP:InitialContextSetup
TotalCSFBdelay

(withCSFBindicator)
Optional:UEcapabilityenquiry

S1AP:Init.Cont.SetupResponse
RRCConn.Release
(withredirectinfo)
S1Contextrelease
UEleavesLTEcell
andestablichesRRC
connectionintargetRAT

RRCInitialDirectTransfer
toBSS/RNS
(incl.NASresponsetoPaging)

Theredirectionisperformedbyan:RRC:RRCConnectionReleasemessagewitha
RedirectedCarrierInfoIE.TheRedirectedCarrierInfoforcestheUEtosearchforanycell
firstatthehighestpriorityUTRAcarrierorwithinBCCH(BroadcastControlChannel)
carriersetforGSM.

Issue:02M DN0978033 115


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

TheUTRAandGSMcellsshouldbroadcasttheLTElayerasprioritizedRAT(Radio
AccessTechnology).ThusthemultimodeUEwillcampbackintotheLTEcarrieraftera
CScallisterminated.
WhenUE Connection Release with Redirectionisperformed,theeNodeB
providesSystem Information(sysInfo)foraconfigurablesetofUTRAN-FDD
cells.IncasetheUEdecidestoselectoneofthesecells,itmayusetheprovided
sysInfotoacceleratetheaccesstoUTRAN-FDD.

2.12.4.2 Selection of target RAT

eNodeBevaluatestheO&Mparametersspecifyingtheredirectiontargetaccordingtothe
valueofcsFallBPrioparameter(seeParametersfortheLTE562:CSFBtoUTRANor
GSMviaredirect).Thespecialvaluenotusedmeansthatsucharedirectiontarget
definedinO&MdatabasewillnotbetakenforReleasemessage.eNodeBbuildsalistof
redirectiontargetRATdefinitions,startingwithlowestvaluesofcsFallBPrioparameter,
whichhasuniquevalues,sothislistcanbebuildinanunambiguousway.TargetRATs
thatarenotavailableinUECapabilitiesinformationareexcludedfromthatlist.

2.12.5 System impacts

2.12.5.1 Impacts on system performance and capacity

LTE562:CSFBtoUTRANorGSMviaredirectismoretime-consumingthanthedirectcall
setupinUTRANorGERANbecausetheUEhastoleavetheLTEcellandreconnectto
thetargetnetworkfirstbeforesettingupthecallasusual.Thebulkoftheadditionaldelay
(2.0s)isrelatedtotheUEcellleaveandreconnectionprocedureaftertheUEreceived
theconnectionreleaserequest.eNodeBorothercomponentsontheLTEsidedonot
contributetothisdelay.
Figure14:MessagesequenceandtimedelayduringCSFBredirectionshowstheLTE
contributiontothedeley,whichshouldbelessthan53ms.

2.12.6 Sales information


Thisfeatureisoptional.

2.12.7 User interface


ThefeatureLTE562:CSFBtoUTRANorGSMviaredirectintroducesanumberofnew
countersandparameters.

2.12.7.1 Parameters

Table50:ParametersfortheLTE562:CSFBtoUTRANorGSMviaredirectshowsthe
parametersimplementedforthefeatureLTE562:CSFBtoUTRANorGSMviaredirect.

116 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table50 ParametersfortheLTE562:CSFBtoUTRANorGSMviaredirect

Name Short name Object Description Range / Step Default value

ActivateCSFallbackVia actCSFBRedir LNBTS Theparameteractivatesthe Disabled(0), Disabled(0)


Redirection feature'CircuitSwitchedFallback Enabled(1)
toUTRANorGSMvia
Redirection'.
Ifthefeatureisactivated,mobile
originatedandmobileterminated
CScallsareredirectedtotargets
whicharetobeconfiguredvia
REDRTobjects.

RedirectionPriorityforCS csFallBPrio REDRT Thisparameterdefinesthe 1...6,step1 -


FallbackwithRedirection priorityfortargetRATinselection
oftheredirectiontargetduringa
CSFallbackwiththeredirection
procedure.
Value1meansthehighestpriority
andvalue6lowest.

Redirectiontarget redrtId REDRT Thisparameterdefinesthe 0...5,step1 -


configurationidentifier numberofredirectiontargets
specifiedfortherespectivecell
andthisparameteristhenaming
attributeofMOCREDRT.

Systeminformationlist systemInformatio LNBTS TheconfiguredWCDMAsystem


WCDMA nListWCDMA informationissenttotheUEwith
theRRCConnectionRelease
messageinallkindsofredirection
toWCDMAThesettingapplies
forallLTEcellsoftheeNB.

PhysicalCellId physCellId LNBTS Physicalcellidentifierforwhich 0...511,step1 -


thesysteminformationapplies.

SystemInformation sysInfo LNBTS WCDMAsysteminformation 4...2050 -


whichshallbeincludedinthe characters
RRCConnectionRelease
message.
Theparametermustbeaddedas
characterstringinhexadecimal
notationwithleading'0x',where
foreachoctettwocharactermust
beconfigured,withaminimum
lengthofoneoctet.
Theoctetstringhastobedefined
accordingtoTS25.331section
10.2.48a.

Issue:02M DN0978033 117


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.12.7.2 Alarms

Therearenoalarmsforthisfeaturedefinedinthisrelease.

2.12.7.3 Measurements and counters

Itispossibletomonitorthefeatureusagewithadditionalcountersinordertomeasureits
performance.

Table51:CountersfortheLTE562:CSFBtoUTRANorGSMviaredirectshowsthe
countersforLTE562:CSFBtoUTRANorGSMviaredirect

Table51 CountersfortheLTE562:CSFBtoUTRANorGSMviaredirect

PI ID Counter long name (short Description


name)

M8000C23 UEContextmodificationattempts ThenumberofUEcontextmodificationattempts


(UE_CONTEXT_MOD_ATT)

M8000C25 UEContextmodificationfailures ThenumberofUEcontextmodificationfailures


(UE_CONTEXT_MOD_FAIL)

M8000C31 UEContextmodificationattempts NumberofUEContextmodificationattemptsduetoCSFallback


duetoCSFallback
(UE_CONTEXT_MOD_ATT_CSF
B)

M8016C11 CSFallbackattemptswith NumberofCSFallbackattemptswithredirectionviaRRC


redirectionviaRRCConnection ConnectionRelease
Release
(CSFB_REDIR_CR_ATT)

M8016C12 CSFallbackattempts(UEin NumberofCSFallbackattempts(UEinConnectedMode)with


ConnectedMode)with redirectionviaRRCConnectionRelease
redirectionviaRRCConnection
Release
(CSFB_REDIR_CR_CMODE_AT
T)

2.12.8 Activating the feature


Thisfeaturerequiresactivation.ForinstructionsseeActivatingtheLTE562:CSFBto
UTRANorGSMviaredirect.

118 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.13 LTE819: DL Inter-cell Interference Generation


2.13.1 Introduction To The Feature
Withthedownlinkinterferencegenerationfeature,itcanbeensuredthatdownlinkload
ofneighborcellsisatleastonapre-definedlevel.Byconfiguringaminimumdownlink
cellload,theoperatorisabletotest(intra-frequency)interferencecausedbyneighbor
cellstotheservingcell.Thedownlinkinter-cellinterferencegeneratorallowsrunningthe
testwithouttestUEs:theFlexiBTSsendsdummydatatononexistingUEsinorderto
generatedownlinkinter-cellinterference.

2.13.2 Benefits
Theoperatorcanperformdownlinkinter-cellinterferencerelatedtestsinthefieldwithout
testUEs.

2.13.3 Requirements

2.13.3.1 Software Requirements

Thefollowingsoftwareisrequiredforthisfeature.

Table52 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

UE

NetAct

2.13.3.2 Hardware Requirements

ThisfeaturerequiresFlexiSystemmoduleswhichsupportLTE.

2.13.4 Functional Description


TheFlexiMultiradioBTStransmitsPDSCHdummydata(apseudorandombit
sequence)onresourceelementsnotallocatedbythedownlinkscheduler,whichareonly
addedifnotenoughresourceelementsareallocatedtonormalusers.Thedummydata
aresentonallconfiguredantennas,e.g.singleortwoantennas,andtheirpowerspectral

Issue:02M DN0978033 119


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

densityisthesameasforthePDSCH.Theoperatorconfiguresthemodulationscheme
forthedummydataandtheinterferencelevel,i.e.percentageofPDSCHresource
elementsusedbythenormalusersanddummydata.Thedownlinkschedulerisnot
limitedbythissettinganditcanallocatedataalsoabovetheinterferencelevel.

2.13.4.1 Feature Scope

TheLTE819:DLInter-cellInterferenceGenerationisconfigured,activated,modifiedand
deactivatedeitherbytheNetActorlocallybyBTSSiteManager.TheeNBhasatleast
one,anduptothreeLTEcells.TheLTEcellaUEisconnectedto,isservingcell.Other
cellsareclassifiedasneighborcells.Becausefromthedownlinkinter-cellinterference
generationpointofviewtheeNBdoesnotseeanydifferencebetweenservingand
neighborcells,theLTE819:DLInter-cellInterferenceGenerationcanbeconfiguredand
activatedtoanyeNBcell.

2.13.4.2 User Scenarios

Operatorcanactivateanddeactivatedownlinkinter-cellinterferencegenerationusinga
managementtool,whichiseitherNetActorBTSSiteManager.Thefeaturecanbe:

activatedeitherattheeNBstartup,oronlineincaseacellisalreadyconfigured
deactivatedbysettingthemanagementparameterdlInterferenceEnableto
False

OperatorcanalsomodifytheLTE819:DLInter-cellInterferenceGenerationonline.

2.13.5 System Impacts

2.13.5.1 Dependencies Between Features

Thereareinterdepedenciesbetweenthefollowingfeatures:

LTE793Supportof16QAMinDownlink.Modulationscheme16QAMcannotbe
usedfordownlinkinterferencegenerationunlessLTE793hasbeenenabledand
validlicenseisavailable.
LTE43Supportof64QAMinDownlink.Modulationscheme64QAMcannotbeused
fordownlinkinterferencegenerationunlessbothofthefeatures,LTE793andLTE43
havebeenenabledandvalidlicenseisavailable.

2.13.5.2 Impacts on Network and Network Element Management tools

TheDownlinkinter-cellInterferencegenerationaffectsonlyairinterface(Uu).Managing
(enabling/disabling)thefeaturedoesnotintroducenewfunctionalitiesbetween
NetAct/BTSSiteManagerandtheeNB.

2.13.5.3 Impacts on System Performance and Capacity

120 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.13.5.3.1 System Performance

Thedownlinkinter-cellinterferencegenerationmayaffectneighborcellsperformance,
thefeatureisactuallyimplementedforthat.Theexacteffecttoneighborcellscannotbe
describedprecisely,asitdepends,forexample,onradionetworktopology.

2.13.5.3.2 System Capacity

Thedownlinkinter-cellinterferencegenerationdoesnotaffecttheservingcellcapacity,
asinterferenceisnotaddedifallPDSCHPRBsareusedfordatatransmission.

2.13.6 Sales Information


ThisfeaturebelongstotheApplicationSoftware(ASW)productstructureclass.

2.13.7 User Interface

2.13.7.1 Parameters

Table53:ParametersfortheLTE819DownlinkInter-cellInterferencegenerationshows
theparametersimplementedforthefeatureLTE819DownlinkInter-cellInterference
Generation.

Table53 ParametersfortheLTE819DownlinkInter-cellInterferencegeneration

Name Short name Object Description Range / Step Default


value

EnableDownlink dlInterferenceEna LNCEL Theparameter false,true false


InterferenceGeneration ble dlInterferenceEnableis
usedforenablinganddisabling
interferencegenerationin
downlink.

InterferenceLevelfor dlInterferenceLev LNCEL ThedlInterferenceLevel 0...100%, 0%


GeneratedDownlink el parameterdefinespercentageof step1%
Interference physicalresourceblocks(PRB)
thatareusedfordownlinkdata
andinterferencetransmission.

ModulationSchemefor dlInterferenceMod LNCEL The QPSK(0), QPSK(0)


DownlinkInterference ulation dlInterferenceModulatio 16QAM(1),
nparameterdefinesmodulation 64QAM(2)
schemetobeusedfor
generateddownlinkinterference.
Thatis,foranon-existingUEthe
downlinkinterferenceis
transmitted.

Issue:02M DN0978033 121


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.13.7.2 Alarms

Therearenoalarmsrelatedtothisfeature.

2.13.7.3 Measurements and Counters

Therearenomeasurementsandcountersrelatedtothisfeature.

2.13.8 Activating the Feature


ThefeatureLTE819:DLInter-cellInterferenceGenerationneedstobeactivatedwiththe
parameterdlInterferenceEnable.ForinstructionsseeActivatingtheLTE819:DL
Inter-cellInterferenceGeneration.

2.14 LTE870: Idle Mode Mobility from LTE to


CDMA/eHRPD
2.14.1 Introduction to the Feature
Whenthisfeatureisenabled,informationaboutCDMA2000frequenciesandneighboring
cellsrelevantforcellre-selectionfromLTEtoaCDMA/eHRPDnetworkcanbe
broadcastedtotheUEintheidleandintheactivemode.Thisfunctionalityisinlinewith
therequirementthatthesystemmustsupportaseamlesscellre-selectionfromanLTE
networktoa3GPP2evolvedHighRatePacketData(eHRPD)network.

2.14.2 Benefits

2.14.2.1 End User Benefits

Whencampedonacell,theUEregularlysearchesforabettercellaccordingtothecell
reselectioncriteria(broadcastedparameters).Ifabettercellisfound,thatcellis
selected.ThechangeofcellmayimplyachangeofRAT,incaseofthisfeature,a
changefromLTEtoeHRPD.

2.14.2.2 Operator Benefits

ThisfeatureimprovestheavailabilityofservicefortheLTEsubscribers.

2.14.3 Requirements

2.14.3.1 Software Requirements

Table54 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

122 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Table54 Softwarerequirementsfordifferentnetworkelements(Cont.)

Network element Required software release

eNodeB LBTS2.0

MME NS20

SAEGW NG20

UE 3GPPrelease8

NetAct

2.14.3.2 Hardware Requirements

Thisfeaturedoesnotrequireanyneworadditionalhardware.

2.14.4 Functional Description


Auserequipment(UE)whichisintheRRC-IDLEstatecanbereachedinthosecellsthat
belongtothetrackingarea(TA)wheretheUEiscurrentlyregistered.Informationabout
inwhichtrackingareatheUEislocatedisudpatedtotheUEviathebroadcastchannel
(BCCH).
IffeatureLTE870:IdlemodemobilityfromLTEtoCDMA/eHRPDisenabled,theeNB
sendsinformationaboutCDMA2000frequenciesandneighboringcellstoallUEsin
RRC-IDLEandRRC-CONNECTEDstateinthebroadcast.Thisinformationisneededfor
inter-RATcellre-selectionfromLTEtoCDMA/eHRPD.
Thebroadcastisrepeatedatregularintervals,dependingonthevaluedefinedin
parametersi8Periodicity.
Theparametersthatcanbebroadcasted,withtheirvaluesandinter-dependencies,have
beendescribedinsectionParameters.

2.14.5 Sales Information


ThisfeaturebelongstotheApplicationSoftware(ASW)productstructureclassand
requiresalicensefortheeNB.ThelicensetypeisON/OFF.
Whenthelicensehasbeenacquired,thefeaturecanbeenabledfortheeNBwith
parameteractImmHRPD.
Whenthelicenseisnotavailable,theeHRPD-specificset(parametersHRPD)isomitted
fromSIB8.
Ifnoneofthefeatures,LTE807:IdleModeMobilityfromLTEtoCDMA/1xRTTor
LTE870:IdleModeMobilityfromLTEtoCDMA/eHRPDisavailable,SIB8isnot
broadcastedatall.

2.14.6 User Interface

Issue:02M DN0978033 123


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

2.14.6.1 Managed Objects

TheeHRPD-specificparametersaredefinedintheCDMA2000FrequencyIdleMode
Configuration(managedobjectclassCDFIMoftheeNBobjectmodel).Theparameters
arelistedinthefollowingsection.

2.14.6.2 Parameters

TheparametersthatcanbebroadcastedfromtheeNBtoCDMA/eHRPDarelisted
below.TheseparametersbelongtoSystemInformationBlock8(SIB8).Foradescription
oftheusageandvaluerangeofeachparameter,seetheU-planeProtocolStacksand
SIBfunctionalareadescription.

t Tip: ApartfromthenamingattributecdfimId,theparametersareoptional.However,if
noneoftheotherparametersaredefined,theSIB8informationbroadcastedwouldbe
empty.Inpractice,therefore,atleastthefrequencybandlistandneighborcelllisthave
tobedefined.

Table55 ParametersforLTE870:IdleModeMobilityfromLTEtoCDMA/eHRPD
Full name Abbreviated Managed Structure
name object
CDMAsearchwindowsize searchWinSize CDFIM
CDMA2000HRPDbandclasslist hrpdBdClList CDFIM
CDMA2000HRPDbandclass hrpdBdClBcl CDFIM hrpdBdClList
CDMA2000HRPDcellreselection hrpdCResPrio CDFIM hrpdBdClList
priority
CDMA2000HRPDreselectionhigh hrpdFrqThrH CDFIM hrpdBdClList
threshold
CDMA2000HRPDreselectionlow hrpdFrqThrL CDFIM hrpdBdClList
threshold
CDMA2000HRPDneighborcelllist hrpdNCList CDFIM
CDMA2000HRPDfrequency hrpdArfcn CDFIM hrpdNCList
CDMA2000HRPDbandclass(NCL) hrpdBdClNcl CDFIM hrpdNCList
CDMA2000HRPDphysicalcell hrpdCellId CDFIM hrpdNCList
identity
CDMA2000HRPDNCLextension hrpdExSel CDFIM hrpdNCList
selector
CDMA2000HRPDcellreselection tResHrpd CDFIM
timer
Speeddepscalingfactorstreselection tResHrpdSF CDFIM
HRPD
HRPDcellreselectiontimerfactorhigh hrpResTiFHM CDFIM tResHrpdSF
mobility
HRPDcellreselectiontimerfactormed hrpResTiFMM CDFIM tResHrpdSF
mobility

124 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

ThefrequencyatwhichthebroadcastisrepeatedisdefinedinparameterSystem
Information 8 Periodicity(si8Periodicity),whichbelongstomanaged
objectLNCEL.

2.14.6.3 Alarms

Therearenoalamsrelatedtothisfeature.

2.14.6.4 Measurements and counters

Therearenomeasurementsorcountersrelatedtothisfeature.

2.14.7 System Impacts

2.14.7.1 Impacts on Telecom control plane

SIB8messagedefinition.

2.14.8 Activating the Feature


Thefeaturerequiresactivation.Forinstructions,seeActivatingLTE870:IdleMode
MobilityFromLTEToCDMA/eHRPD.

2.15 LTE914: Graceful cell shutdown


2.15.1 Description of LTE914: Graceful Cell Shutdown
Introduction to the feature
TheLTE914:GracefulCellShutdownfeatureallowstheFlexiMultiradio10BTStoempty
acellfromtheuserequipment(UE)beforelockingthecell.Itisdonebyreducing
graduallythetransmitpowerindownlink,whichforcestheUEtoperformhandover
proceduretoothercellthusminimizingtheimpactofthecelllockontheUE.

2.15.1.1 Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.
Operator benefits
MoreflexiblecellmanagementwithminimizedinterruptionfortheUE.
WithLTE914:GracefulCellShutdownfeature,theUEgetsachancetoperform,for
example,handovertoneighboringcellbeforethecellislockedandtheserviceis
unavailable.

2.15.1.2 Requirements
Software requirements
Table56:Softwarerequirementsliststhesoftwarerequiredforthisfeature.

Issue:02M DN0978033 125


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

System release Flexi Multiradio BTS Flexi Multiradio 10 OMS


BTS

RL35TD - TD-LBTS3.0 -

Table56 Softwarerequirements

UE NetAct MME SAE GW

- - - -

Hardware requirements
ThisfeaturerequiresnoneworadditionalhardwareotherthanstandardFlexiMultiradio
10BTSmodule.

2.15.1.3 Functional description

WheneveracellofanevolvednodeB(eNB)needstobedeactivated,itisfirstemptied
ofusersequipment(UE)beforefollowingthenormaldeactivationsequence.
Gracefulcellshutdown,incontrasttodirecttransitionfromunlockedtolockedstate,isa
secondwaytolockacell,forexample,totakeacelloutofservice.Itprovidessmooth
transitionbetweenstatesvianewshuttingdownstatewithgradualreductionof
transmission(Tx)power.WhenUEsdetecttheirlinkqualitygoingdown(affectedby
lowerlevelofTxpowerindownlink),theUEsstartsearchingforacellcandidateto
preformahandover.Thus,reducingtheTxpowerindownlinkforces:

allUEsinRRC connectedmodetoperformahandoveroraredirectprocedure
allUEsinRRC idlemodetoperformcellreselection

ThecellshutdownmighthaveanimpactonKPIsandenduserperceptionastheUEs
arerequiredtoperformhandovers/redirects,whichduringregularnetworkoperation
wouldnothavebeenperformed.

g Note: Calldropscannotbefullyavoided,forexample,forUEsthatareclosetothe
transmittingantenna,measuringsufficientsignalqualityevenwiththelowestoutput
powerstep.Whenthegracefulshutdownprocedureends,allUEsservedbythe
shuttingdowncellaredisconnected.

IftwoormorecellsofaneNBperformgracefulcellshutdown,thepowerreduction
sequenceisdoneinallcellsatthesametimetoavoidping-ponghandovers(handovers
ofaUEgoingfromonecellthatshutsdowntoanothercellthatalsoisgoingtoshut
down).
Gracefull cell shutdown in micro eNB
ForamicroeNB,thelowestpowerallowedduringagracefulcellshutdownislimitedby
theminimumtransmitpowersupportedbythemicroeNB.Iftransmitpowerissettothe
lowerrange,theeffectivenessofthegracefulcellshutdownisreducedoreven
eliminated.Forexample,iftherangeofmicroeNBtransmitpowerisdefinedas24dBm

126 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

to37dBmandthemaximum output power (Pmax)issetto24dBm,thenthe


transmitpowercannotbereducedanyfurtherandthegracefulcellshutdownis
essentiallydisabled.
Example of use
Inthissectionthereisanexampleofgracefulcellshutdownfeatureconfiguration.

Table57 Configurationofparametersforthegracefulcellshutdownprocedure

Name Short name Value

Maximumoutputpower pMax 40dBm

EnableGracefulCell enableGrflShdn 1(enabled)


Shutdown

ShutdownStepAmount shutdownStepAmount 6

ShutdownWindow shutdownWindow 60s

Intheexampleabove,theShutdown Window (shutdownWindow)isconfiguredto


60secondsandtheShutdown Step Amount (shutdownStepAmount). to6.
TheShutdown Window (shutdownWindow) )isautomaticallydividedbythe
Shutdown Step Amount (shutdownStepAmount)togetthestepduration.In
theexample,everysteplasts10seconds.
TheTxpowerisreducedinstepsfromtheMaximum output power (pMax)tothe
fixedvalueofminimumoutputpower(inthisexampleequalto25dBm).Consideringthe
Maximum output power (pMax)configuredto40dBmandtheShutdown Step
Amount (shutdownStepAmount)to6,eachstepwilldecreasetheTxpowerby2.5
dBm.TheTxpowerreductionisalwaysdoneatthebeginningofeachstep.
TheFigure15:Txpowerlevelsduringgracefulcellshutdown.presentstheTxpower
levelsduringgracefulcellshutdown.

Figure15 Txpowerlevelsduringgracefulcellshutdown.
OutputPowerRampDownduringgracefullcellshutdown
50

45 MinimumOutputPower
(dBm)
40 MaximumOutputPower
(dBm)
35

30

25
shutdownWindow=60seconds
20
shutdownStepAmount=6 10s
15

10

-10 -5 0 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80
Time(s)

Issue:02M DN0978033 127


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Thetablebelowliststhevaluesofminimumoutputpowerforvariousradiounits.
Table58 Minimumoutputpowervaluesforvariousradiounits
Family Models Value [dBm]
WMP2.1 FRHA,FRHB,FRMA,FRKA,FRIE, 25
FRMB
Medusa2.2 FXEA,FXCA,FXCC,FHEA,FXDA, 15
FXFB
Reno2.3 FHDB,FHEB,FHEJ,FHEF 15
Vegas2.3 FXCB,FXDB,FXEB 15
Quattro2.3 FRHE,FRHD 15
FRGT FRGT 15
FRM3.1 FRMC,FRHC,FRME,FRPD 0
Corona4.0 FRGY,FRHG,FRGA 0

Feature activation and configuration


Thisfeatureisactivatedbydefaultwithpredefinedparametervalues.
Forinformationonhowtomodifythedefaultparametervaluesordeactivatethefeature,
seeActivatinganddeactivatingLTE914:GracefulCellShutdown.

2.15.1.4 System impact

Thereareinterdependenciesbetweenthefollowingfeatures:

LTE830:AutomaticLock
IfAutomaticLockofacelloccurs,thecellhastobedeactivated.Ifthe
enableGrflShdnparameterisenabled,thegracefulcellshutdownisapplied
insteadofimmediatecelllock.
Impact on interfaces
TheLTE914:GracefulcellshutdownfeaturehasanimpactontheUuinterface,asthe
eNBcellTxpowerisreducedtomaketheUEstoperformcellreselectionsorhandovers
toothercells.Dependingonthenumberofpowerreductionstepsandtheshutdown
windowsize,ahighnumberofhandoverproceduresfromtheshuttingdowncellmight
occurandintroducesomeextraloadtotheS1andX2interfacethatis,however,
distributedintimeandthereforenotcritical.Asthegracefulcellshutdownendsupwith
deactivatingthecell,thepartialresetofS1interfaceisperformed.
Impact on network and network element management tools
Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.
Impact on system performance and capacity
Thefeaturehasthefollowingimpactonsystemperformance:
DuringtheGracefulcellshutdownproceduretheTxpowerisreducedstepwise.Thecell
becomesincreasinglyunattractivefortheUEsandthecellcoverageshrinksaccordingto
thereducedpower.Therefore,theKPIcountersduringgracefulshutdownmightbe
affected.
Thefeaturehasnoadditionalimpactsoncapacity.

128 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

2.15.1.5 LTE914: Graceful cell shutdown management data

Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.
Alarms
Therearenoalarmsrelatedtothisfeature.
Measurements and counters
Therearenomeasurementsorcountersrelatedtothisfeature.
Key performance indicators
Therearenokeyperformanceindicatorsrelatedtothisfeature.
Parameters
Table59:Relatedexistingparametersshowstheparametersintroducedforthefeature
LTE914:Gracefulcellshutdown.

Table59 Relatedexistingparameters

Full name Abbreviated name Managed object

EnableGracefulCellShutdown enableGrflShdn LNBTS

ShutdownStepAmount shutdownStepAmount LNBTS

ShutdownWindow shutdownWindow LNBTS

2.15.1.6 Sales information

Table60 Salesinformation

BSW/ASW License control in network element License control attributes

BSW - -

2.15.2 Activating LTE914: Graceful Cell Shutdown


Before you start
RestartoftheeNBisnotrequiredafteractivationofthisfeature.
Theenable graceful cell shutdown(enableGrflShdn)parameterisused
toactivatethefeature.
Thefollowingparametersareusedtoperformtheadditionalconfigurationofthefeature:

shutdown step amount(shutdownStepAmount)


shutdown window(shutdownWindow)

Issue:02M DN0978033 129


Radioresourcemanagementandtelecomfeatures LTERL20,FeatureDescriptions

Ifthisfeatureisactivated,itisalsopossibletosettheadministrative
state(administrativeState)ofacelltotheshutting downvalue.

Steps

1 Follow the general procedure described in section Activating and deactivating


LTE features using BTS Site Manager.
InStep3(Modify the feature-specific eNB configuration settings)ofthegeneral
procedureperformthestepsdescribedinthisprocedure.

2 Go to the Radio Network Configuration page.

a) ExpandtheMRBTSobject.
b) SelecttheLNBTSobject.
c) SorttheparametersbychoosingthevalueRelated functionsfromSorting
drop-downlistplacedabovetheparameterlist.
d) Activatethefeaturebysettingthe enable graceful cell
shutdown(enableGrflShdn)parametervaluetoEnabled.
e) Configuretheremainingtwoparameters.
Theshutdown window(shutdownWindow)parameterconfiguresthetotal
timeofgracefulcellshutdownprocedure.Duringthistime,theeNBdecreases
theTxpowerinanumberofstepsconfiguredwiththeshutdown step
amount(shutdownStepAmount)parameter.
Whenthedurationofshuttingdownprocedurereachestheshutdown window
(shutdownWindow)timelimit,allUEsthatarestillconnectedtotheshutting
downcellaredisconnected.

g Note: Theaboveparametersmustbeconfiguredsothattheresultingstepduration
(thedurationofshuttingdownwindowdividedbythenumberofsteps)isgreaterthanor
equaltosixseconds.

2.15.3 Deactivating LTE914: Graceful Cell Shutdown


Before you start
RestartoftheeNBisnotrequiredafterdeactivationofthisfeature.
Theenable graceful cell shutdown(enableGrflShdn)parameterisused
todeactivatethefeature.

130 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Radioresourcemanagementandtelecomfeatures

Steps

1 Follow the general procedure described in section Activating and deactivating


LTE features using BTS Site Manager.
InStep3(Modify the feature-specific eNB configuration settings)ofthegeneral
procedureperformthestepsdescribedinthisprocedure.

2 Go to the Radio Network Configuration page.

a) ExpandtheMRBTSobject.
b) SelecttheLNBTSobject.
c) SorttheparametersbychoosingthevalueRelated functionsfromSorting
drop-downlistplacedabovetheparameterlist.
d) Deactivatethefeaturebysettingthe enable graceful cell
shutdown(enableGrflShdn)parametervaluetoDisabled.

Issue:02M DN0978033 131


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

3 Transport and Transmission Features

3.1 LTE140: Ethernet OAM


3.1.1 Introduction to the feature
ThisfeatureaddsOAMfunctionalityontheEthernetlayer.
TherearetwocomplementaryEthernetOAM(E-OAM)protocols:

LinkLayerOAM(IEEE802.3clause57,L-OAM)
ServiceOAM(IEEE802.1ag,ITU-TY.1731,S-OAM)

L-OAMoffersasinglepoint-to-pointlinkmonitoring.
S-OAMoffers:

end-toendEthernetconnectivitymonitoring
networksegmentconnectivitymonitoring
Ethernetfaultlocalization

3.1.2 Benefits

3.1.2.1 End user benefits

Therearenodirectenduserbenefitsintroducedbythisfeature.

3.1.2.2 Operator benefits

EthernetOAMfeaturedecreasestheEthernetnetworkmaintenanceeffortandinresult
reducesOPEX.E-OAMhelpsto:

identifyandlocatefaultsremotely,avoidingsitevisits
examineandreport:
networkstatus
networkperformance
networkprovisioning

3.1.3 Requirements

3.1.3.1 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

132 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table61 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

NetAct OSS5.3CD1

3.1.3.2 Hardware requirements

ThisfeaturerequiresFlexiSystemmodules,whichsupportLTE.

3.1.4 Functional description

3.1.4.1 Link Layer OAM

L-OAMprotocolisabletomonitoranypoint-to-pointlink.Forexample,alinkbetween
twodirectlyconnected(chained)eNBs.WhenL-OAMisactive,theoperatorcancheck
atafirstglanceifthelinktothepeerisworkingornot.Aftertheconnectivityis
established,theremainingsupportedL-OAMcapabilitiesarechecked.

Table62 L-OAMcapabilities

Capability Function

OAMDiscovery IdentifypeerdeviceanditsOAMcapabilities(activemodesupported)

RemoteFailureIndication Indicatefollowingevents:

CriticalLinkEvents
LinkFault-L-OAMnodestoppedreceivingnotransmitsignalfromitspeer
DyingGasp-L-OAMnodeisabouttoresetorreboot
CriticalEvent-errorcondition,whichdoesnotresultinresetorreboot

LinkEvents(degradedEthernetconnection)
ErroredFramePeriodEvent
ErroredFrameEvent
ErroredFramePeriodEvent
ErroredFrameSecondSummaryEvent

Issue:02M DN0978033 133


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Table62 L-OAMcapabilities(Cont.)

Capability Function

RemoteLoopback Checkthelinkqualityfordiagnosisandtroubleshooting(activemodesupported).L-OAM
nodecanswitcharemotepeertoloopbackmode.Theneveryreceivedframeis
transmittedbacktothesendingpeer.

LinkMonitoring Provideeventnotificationsincludingdiagnosisdata(liketresholdalarms)

Loopback mode
Duringconnectivitytestingthepeernodecanbesettoloopbackmodeto:

checkwhetherthetrafficisbeingcorrectlysentandloopedbacktothelocalnode
checkstatistics(erroredframes)
identifyerroneouspacketsandpacketdropsinthelink

Loopbackmodeinterruptsregulartraffic,thereforeitisrecommendedtouseit:

onlyifallalternativesareexhausted(foronlinetesting)
forofflinetesting

Bydefault,loopbackmodeisOFF,toavoidunintendedusage.
WhenusingL-OAMnotethat:

onlyoneL-OAMsessioncanbeestablishedperEthernetport,independentlyofthe
portconfiguration,likeVLAN
L-OAMframeformathastobeuntagged
onlyfullduplexlinksareabletosupportL-OAM

3.1.4.2 Service OAM

OnceEthernetOAMfeatureisactivated,andS-OAMprotocolisinuse,certainservice
instancescanbemonitoredwithinapureL2network.
ServicemonitoringispossibleafterasetofEthernetlayerpointsinthenetworkcalled
MaintenanceAssociation(MA)hasbeendefined.MAconsistsofatleasttwo
MaintenanceAssociationEndPoints(MEPs)representedbyatriangleandpossibly
MaintenanceAssociationIntermediatePoints(MIPs)inbetweenrepresentedbyacircle.
MAsaredistinguishedonFigure16:ServiceOAMoverviewbydifferentcolors.

134 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Figure16 ServiceOAMoverview
OparatorANes OparatorBNes

UNI
UNI
enB Eth
Eth UNI-N UNI-N MME

UNI UNI UNI UNI

O&M
MDLOAMLevel
mobile
7-5
operator

transport
3-4 service
ETH
provider
S-OAM
point-to-point
2-0 transport
service TRANS
provider

MEP
MIP

AllMEPsandMIPswithinagivenMAsharethesameMAIdentifier(MAID),and
MaintenanceDomainLevel(MDL).MAIDvaluedonothavetobethesameastheMDL
valueinagivenMA.
MDLsseparateS-OAMflowsgeneratedbyspecificMAs.EightMDLsareavailable.Ifa
singleoperatorownstheentireeNBaccessnetwork,alleightMDLscanbeserved.
Typicallynotalllevelsareused.
MaintenanceDomain(MD)isanetworkpart,controlledbyasingleoperator.
Ifmultipleserviceinstances(MaintenanceAssociations)aretobemonitored,morethan
oneMEPneedstobeconfiguredatthesameMaintenanceDomainLevel.
MIPiscapableofreactingtosomeS-OAMframes.However,itdoesnotactively
generateS-OAMframes.NotethattheRL20E-OAMimplementationallowstheeNBto
communicatewithexternalMIPs,butitisnotpossibletocreateanMIPintheeNBitself.
S-OAMiscarriedoutinparalell,butindependentlytothepayloadtransport.
Nevertheless,EOAMconsumessomebandwidthonthetransportlinks.E-OAM
bandwidthconsumptiondependsonthenetworkconfiguration,butusuallyitisnegligible.
OAMlevelsaredefinedonamobilenetworkapplicationbasis:

mobileoperatorlevel
transportserviceproviderlevel
point-to-pointtransportserviceproviderlevel

ThefollowingS-OAMcapabiliesareavailable:

EthernetContinuityCheck(ETH-CC)
EthernetAlarmIndicationSignal(ETH-AIS)
EthernetRemoteDefectIndication(RDI)
EthernetLinkTrace
EthernetLoopback

Issue:02M DN0978033 135


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

3.1.4.2.1 Ethernet Continuity Check and Ethernet Remote Defect Indication

MEPsendsEthernetContinuityCheckMessages(ETH-CCMs)toitspeerMEPs
accordingtotheconfiguredperiod.MEPexpectsETH-CCMsfromeverypeerMEP.
ECCreportscontinuityloss,orunintendedconnectivitybetweenMEPsinthesameMA
aspresentedonFigure17:EthernetContinuityCheckandEthernetRemoteDefect
Indication.

Figure17 EthernetContinuityCheckandEthernetRemoteDefectIndication

eNB

Eth

Ethernet Ethernet MME

EthCC
Level7
O&M
EthCC
Level2

3lostCCM=
LossofContinuity

RDIflagsetinEthernetContinuityCheck

IfnoETH-CCMisreceivedfromaparticularpeerMEP:

1. alarmisraised
2. theETH-CCMsendersetsaRemoteDefectIndication(RDI)flagintheCCMs
towardsallMEPpeersinthecorrespondingMA

3.1.4.2.2 Ethernet Alarm Indication Signal

ETH-AISisuseful,sinceanoperatordoesnotknowwhetherfaultsoriginateathislevel
(fixneeded)oratalowerlevel(providerSLAnotfulfilled).ETH-AISprevents
unnecessarylowerlevelalarmraisingafterafailuredetection.

136 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Figure18 EthernetAlarmIndicationSignal

eNB eNB

Eth Eth Eth UNI UNI

MME

Level7
O&M
EthAIS
Level6

Level2

Level0

WhenaMEPdetectsaconnectivityfailureatspecificMDL,it:

1. sendsoutAIStoallMEPsatthenextconfiguredhigherMDL(AISissentawayfrom
detectederror)
NotethattheremustbeatleastoneMEPorMIPononeofthehigherMDLsinthe
sameNE.OhterwiseitisnotpossibletoinsertETH-AIS.
2. suppressesalarmsforallpeerMEPsonhigherMDLs,soNetActgetsonlytheroot
alarm,causedbythefaultyMDL

3.1.4.2.3 Ethernet Loopback

EthernetLoopbackverifiesbi-directionalconnectivitybetweentwopeerMEPs,or
betweenaMEPandaMIP.ItissimilartoL3"ping"command,withoptional
troubleshootingextensions.

Issue:02M DN0978033 137


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Figure19 EthernetLoopback

eNB

Eth

Ethernet Ethernet MME

O&M
EthLBM
Level7
5sec EthLBR

EthLBM
Level6 EthLBR
5sec

Level2

3.1.4.2.4 Ethernet Link Trace

EthernetLinkTraceretrievesrelationbetweenadjacentMEPsorMIPs.Itallowsthe
detectionofthenumberofS-OAMawarehopsbetweentwoMEPs.ItissimilartoL3
"traceroute"command.

Figure20 EthernetLinkTrace

eNB

Eth

Ethernet Ethernet MME

O&M
EthLTM
Level7
5sec EthLTR

EthLTM
Level6 EthLTR
5sec

EthLTM
Level2 EthLTR

3.1.5 Sales information


ThisfeaturebelongstotheApplicationSoftware(ASW)productstructureclass.

3.1.6 User interface

3.1.6.1 Parameters

ThefollowingtableshowstheparametersimplementedforthefeatureLTE140:Ethernet
OAM.

138 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table63 ParametersforLTE140:EthernetOAM

Name Object Description Range Default

linkOAMEnabled ETHLK EnablesL-OAMforaspecificEthernetlink. 0(false) 0


ChangefromfalsetotrueresetsL-OAM 1(true)
countersandalarmsfortheaffectedinterfaces
andtriggersL-OAMdiscovery.

linkOAMProfile ETHLK ReferencetoaL-OAMprofile 0...40characters -


(toaninstanceofOAMPRFclass).Example:
FTM-1/OAMPRF-1.

linkOAMLoopbackSuppo IPNO L-OAMremoteloopbackOn/Offflag.Iftrue,the 0(false) 0


rt FTMenablesdiscoveryprocessforL-OAM
1(true)
loopbackrequestsinitiatedbyaremotenetwork
elements.OtherwisetheFTMdoesnotaccept
loopbackrequestsinitiatedbyremotenetworks.

oamTlvReply IPNO TLVmessagereplyflag.Dependingonthis 0(false) 0


value,optionalTLVsreceivedinaLinkTraceor
1(true)
Loopbackmessages(LTMsorLBMs)areeither
sentbackuncheckedinthecorrespondingreply
message(LTR,orLBR),orignoredandnotsent
inthereplymessage.

wfqSchedOamWeight IPNO WFQaggregationschedulerweightforS-OAM 1...10000 10


messages.
step1

assocId OAMMA MaintenanceAssociationID.Maximumof15 1...15 -


MAscanexistinaneNB.
step1

maName OAMMA MaintenanceAssociationname. 1...42characters -

vlanId OAMMA VLANIDassociatedtoagivenMA.TheFTM 0...4094 0


usesthisparameterinS-OAMmessagessent
step1
overtheS-OAMEthernetlink(configuredinthe
OAMMEP).TopreventdiscardingofS-OAM
messages,configuredVLANIDmustmatchthe
L2bridgesrestrictions.

domainId OAMMD MaintenanceDomainID.Maximumof10MDs 1...10 -


canexistinaneNB.
step1

ethernetPort OAMMD ReferencetoEthernetlink,forexampletoan 0...40characters -


instanceofETHLKobject.Ifspecified,theeNB
sendsS-OAMmessagesviathisport.

interfacePtr OAMMD Referencetoanetworkinterface,forexampleto 1...40characters -


aninstanceofIEIFobjectclass(plainEthernet
interface)orIVIF(VLANinterface).Ifempty,the
MDisnotassociatedtoanetworkinterface.

Issue:02M DN0978033 139


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Table63 ParametersforLTE140:EthernetOAM(Cont.)

Name Object Description Range Default

mdLevel OAMMD MaintenanceDomainLevel. 0...7 -


step1

mdName OAMMD MaintenanceDomainname. 1...42characters -

networkInterface OAMMD Referencetoanetworkinterfaceforexampleto 0...40characters -


aninstanceofIEIFobject(plainEthernet
interface)orIVIFobject(VLANinterface).If
empty,theMDisnotassociatedtoanetwork
interface.

oamCir OAMMD Committedinformationrate(CIR)forS-OAM 100...1000000kbps 1000


messagessentbytheeNB. kbps
step100kbps

aisEnabled OAMMEP AISretransmissionflag. 0(false) 0


1(true)

aisTxPeriod OAMMEP SendingrateforAISmessages. 0(1s) 0


1(60s)

ccmTxPeriod OAMMEP SendingrateforETH-CCMmessages. 0...6,0(3,33ms);1 3


(10ms);2(100ms);3
(1s);4(10s);5(60s);
6(600s)

enableCcm OAMMEP Flag,whichallowssendingETH-CCMsto 0(false)notallowed false


remoteMEPs.Changefromfalsetotrueresets
1(true)allowed
CCMcountersandalarmsofallremoteMEPs.

ethernetPort OAMMEP EthernetlinkusedbytheFTMforsendingS- 0...40characters -


OAMmessages.
Theparameterisalocalmanagedobject
instanceidentifier(LMOID),Example:reference
toaninstanceofobjectclassETHLK-FTM-
1/ETHLK-1-1.

macAddr OAMMEP RemoteMEPMACaddress. 17characters -

mepId OAMMEP MaintenanceAssociationEndpoint(MEP)ID. 1...8191 -


step1

oammepId OAMMEP MaintenanceAssociationEndpoint(MEP)ID. 1...8191 -


step1

remoteMepList OAMMEP ListofMEPsinagivenMA. - -

140 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table63 ParametersforLTE140:EthernetOAM(Cont.)

Name Object Description Range Default

vlanPrio OAMMEP VLANpriority(PCPbitsvalue)usedinS-OAM 0...7 7


messagesforagivenMEP.
step1

activeMode OAMPRF L-OAMdiscoverymodeflagatthelocalpeer. 0(false) 0


False-eNBonlyrespondstoaremotelyinitiated
1(true)
discoveryprocess.True-eNBproactively
initiatesthediscoveryprocess.

alarmClearanceDelay OAMPRF Periodoftimeafterrecovery,beforetheeNB 1...10s 1s


clearstheL-OAMCriticalEventalarm.
step1s

efEventThreshold OAMPRF ThresholdvalueforcountingErroredFrame 0...4294967295 1


Events.Ifexceeded,theeNBtransmitsOAM
step1
PDUEventNotificationmessage.

efEventWindow OAMPRF MeasurementintervalforcountingtheErrored 1...60s 1s


FrameEvents.
step1s

efpEventThreshold OAMPRF ThresholdvalueforcountingErroredFrame 0...4294967295 1


PeriodEvents.Ifexceeded,theeNBtransmits
step1
OAMPDUEventNotification.

efpEventWindow OAMPRF MeasurementintervalforcountingtheErrored 1


FramePeriodEvents.

efssEventThreshold OAMPRF ThresholdvalueforcountingErroredFrame 0...65535 1


SecondsSummaryEvents.Ifexceeded,theeNB
step1
transmitsOAMPDUEventNotification.

efssEventWindow OAMPRF MeasurementintervalforcountingtheErrored 10...900s 60s


FrameSecondsSummaryEvents.
step1s

espEventThreshold OAMPRF ThresholdvalueforcountingErroredSymbol 0...999999999999 1


PeriodEvents.Ifexceeded,theeNBtransmits
step1
OAMPDUEventNotification.

espEventWindow OAMPRF MeasurementintervalforcountingtheErrored 1...60s 1s


SymbolPeriodEvents.
step1s

eventRepetition OAMPRF MaximumnumberofrepetitiveOAMEvent 1...4 2


Notificationtransmissions.
step1

eventSupport OAMPRF eNBL-OAMsupportflag. 0(false) 0


1(true)

Issue:02M DN0978033 141


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Table63 ParametersforLTE140:EthernetOAM(Cont.)

Name Object Description Range Default

linkLostTime OAMPRF IfnoL-OAMPDUsarereceivedforaperiod 2...10s 10s


specifiedbythisparameter,thealarmisraised.
step1s
ThealarmisclearedifL-OAMPDUshavebeen
continuouslyreceivedagainforthesameperiod
oftime.

linkTimeOut OAMPRF TimebetweentwoconsecutivetriggersofL- 1...10 5


OAMdiscovery.IfFTMdoesnotreceiveany
step1
OAMPDUmessageforthedurationof
linkTimeOut,itrestartsthediscoveryprocess.
OnlyvalidinL-OAMactivemode.

loopBackTime OAMPRF DurationofeNB-initiatedloopbackoperation. 10...600s 10s


step1s

messageRate OAMPRF RateatwhichlocalpeerstransmitOAMPDUs. 1...10messages/s 1


Sincethetransmissiondelaybetweenindividual step1message/s messag
messagesisspecifiedbypduTime,the e/s
messagesmaynotbetransmittedevenlywithin
themessageRatetime.

profileId OAMPRF L-OAMprofileID. 1...5 -


step1

testFrameRate OAMPRF Numberofframespersecondtobesentduring 0...25000 1


L-OAMloopbackoperation.
step1

testFrameSize OAMPRF EthernettestframesizesentduringL-OAM 64...1518 64


loopbackoperation.
step1

3.1.6.2 Alarms

Table64 AlarmsforLTE140:EthernetOAM.

Alarm Alarm name Condition


number

7665 BASE STATION Triggeredbyoneofthefollowingevents:


TRANSMISSION
ALARM faultno61075:L-OAMloopbackalarm
faultno61076:L-OAMlinklostalarm
faultno61077:L-OAMcriticallinkeventalarm
faultno61410:CCMtransmissionfaultsonagivenETHinterface
faultno61411:MEPreceivedavalidETH-AISframe

142 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table64 AlarmsforLTE140:EthernetOAM.(Cont.)

Alarm Alarm name Condition


number

Asaresultthetransportconnectiontowardstheremotepeermightbedeffective,andthe
trafficmightgetlost.

3.1.6.3 Measurements and counters

RelatedmeasurementsandcountersareembeddedwithintheE-OAM,andarenot
availableinNetAct.

3.1.7 Activating and configuring the feature


Foractivatingandconfiguringthefeature,seeFeatureActivationDocumentation.

3.1.8 Abbreviations

3.1.8.1 0Z

ETH-AIS

EthernetAlarmIndicationSignal

ETH-CC

EthernetContinuityCheck

E-OAM

EthernetOperationsandMaintenance

ETH-CCM

EthernetContinuityCheckMessage

L-OAM

LinkLayerOAM

MA

MaintenanceAssociation

Issue:02M DN0978033 143


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

MAID

MaintenanceAssociationIdentifier

MD

MaintenanceDomain

MDL

MaintenanceDomainLevel

MEP

MaintenanceAssociationEndPoint

MIP

MaintenanceAssociationIntermediatePoint

RDI

RemoteDefectIndication

S-OAM

ServiceOAM

3.2 LTE491: FlexiPacket Radio Connectivity


3.2.1 Introduction to the feature
FlexiPacketRadioConnectivityintroducestheeNBcapabilitytomanageaFlexiPacket
Radio(FPR)systemconnectedtoaneNBEthernetinterface.
TheFlexiPacketRadioisamicrowavepoint-to-pointradioforconnecting:

eNBtotheEthernettransportnetwork
eNBtoothereNBs

Thecapacityvariesdependingontheselectedchannelbandwidthandthemodulationin
use.Forexamplea350Mbit/stransportcapacityisavailableina56MHzchannel
bandwidthwith256QAM.TheradiocomprisesbasebandandRFfunctionality,sothere
isonlytheEthernetnetworkconnectionnecessary(besidespower)tomakeitpartofa
network.AP2PFPRlinkconsistsoftworadioterminations,aNear-End(NE)radio
terminationconnectedatthelocalsiteandtheFar-End(FE)radiotermination.

144 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

LTE491:FlexiPacketRadioConnectivityincludesthemanagementofanear-end(NE)
andtheassociatedfar-end(FE)radioterminationfromaLocalManagementTerminal
(LMT)whichisconnectedattheLocalManagementPort(LMP)oftheeNB.Thetwo
mainoperatingusecasesfortheFlexiPacketRadiomanagementarepossible:

TheFPRmanagementtrafficusestheFPRPayloadChanneltogetherwiththe
U/C/M/S-Planetraffic
TheFPRmanagementtrafficiscarriedthroughtheso-calledR-Channelwhichis
dedicatedtoFPRmanagementpurposes

3.2.2 Benefits
FlexiPacketRadiocanbeinstalledattheFlexiMultiradioBTSsitewithoutindoorunit.
Localcommissioningandmanagementdoesnotrequiretointerruptbackhaultrafficorto
touchcablingbetweentheBTSandFlexiPacketRadio.

3.2.3 Requirements

3.2.3.1 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

Table65 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

UE

NetAct OSS5.3CD1

3.2.3.2 Hardware requirements

ThisfeaturerequiresFlexiSystemmoduleswhichsupportLTE.

3.2.4 Functional description


TheFlexiPacketRadioisamicrowavepoint-to-pointradioforconnecting:

eNBtotheEthernettransportnetwork
eNBtoothereNBs

Issue:02M DN0978033 145


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Thecapacityvariesdependingontheselectedchannelbandwidthandthemodulationin
use.Forexample,ifanarrowbandisused(3.5MHz)andamodulationschemeis4/16-
QAMthetransportcapacityis4.4/8.8Mbit/srespectively.Thetransportcapacityraises
upto350Mbit/sina56MHzchannelbandwidthwith256QAM.Theradiotermination
unitcomprisesbasebandandRFfunctionality,sothereisonlytheEthernetnetwork
connectionnecessary(besidespower)tomakeitpartofanetwork.
Apeer-to-peerFlexiPacketRadio(FPR)linkconsistsoftworadioterminations:aNear-
End(NE)radioterminationconnectedatthelocalsiteandtheFar-End(FE)radio
termination.TheFigure21:FlexiPacketRadioConnectivitysolutionshowsthescopeof
theLTE491:FlexiPacketRadioConnectivityfeature.

Figure21 FlexiPacketRadioConnectivitysolution

Host Host
eNB
Flexipacket
Ethernet Radio Ethernet
L2 L2 Network
IP Evolved
NearEnd NearEnd Network PacketCore
termination termination

FPRmanagementdatacanbecarriedbetweentheNEandFEradioterminationsintwo
differentmodes:

TheFPRmanagementtrafficisusingtheFPRPayloadChanneltogetherwiththe
U/C/M/S-Planetraffic
FPRcarriestheFPRpayload(U/C/M/S-Planetraffic)andFPRmanagementtraffic
ontwoseparateradiochannelsfromoneradioterminationtotheother

g Note: RegardlessoftheusedFlexiPacketRadioConnectivitymode,theFPRisnot
awareofIPsec.TheFPRmanagementtrafficmustbesentunsecured.

3.2.4.1 FPR management uses FPR Payload Channel

Inthismodeallpackets,exceptthosematchingwiththeNEradiotermination'sIP
address,areforwardedtotheFEradioterminationviatheFPRPayloadChannel(Figure
22:FPRmanagementdataforwarding).R-Channelisunusedinthismode.
Consequently,themanagementtrafficfortheFEradioterminationisfacingthesame
possibleimpairments(forexamplecongestion)asnormalpayloadtraffic.IntheFEradio
terminationtheEthernettrafficcomingfromtheairinterfaceismonitoredandiftheIP
addressmatcheswiththeFEradiotermination'sIPaddress,thepacketisconsideredas
managementpacket.AlltheotherEthernettrafficisforwardedtotheEthernettransport
networkinterface.
InthismodetheeNBisconfiguredwithoneEthernetnetworkinterfacefortheU/C/M/S-
PlanethatisalsousedfortransportofFPRmanagementtraffic.TheFPRmanagement
trafficusesthesamenetworkinterfaceandthesameDiffServCodePoint(DSCP)
schedulerastheFPRpayloadtraffic.

146 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

3.2.4.2 FPR management uses separate Radio Channel

FPRcarriestheFPRpayload(U/C/M/S-Planetraffic)andFPRmanagementtrafficon
twoseparateradiochannelsfromoneradioterminationtotheother(Figure22:FPR
managementdataforwarding).VLANusagehastobeconfiguredatFPRNEandFE
radioterminations.

Figure22 FPRmanagementdataforwarding

Host
Host Host
R-Channel
R-Channel
FPRPayload
FPRPayload

Switch
Switch Switch
Switch
Ethernet Ethernet

NearEnd FarEnd
termination termination

FPRManagementdataforwardingwhenFPRVLANisON
FPRManagementdataforwardingwhenFPRVLANisOFF

TheFPRmanagementtrafficiscarriedthroughtheso-calledR-Channelwhichis
dedicatedtoFPRmanagementpurposes.ThischannelrunsinparalleltotheFPR
payloadchannelwherethenormalFPRpayloadtraffic(entireU/C/M/S-Plane)iscarried.
AlldataenteringtheFPRarepassingthroughtheL2switchattheNEradiotermination.
FPRmanagementtrafficfortheR-ChannelisidentifiedbyaspecialVLANID.All
packetstaggedwiththeselectedVLANIDareseparatedfromtheFPRpayloadtraffic
stream.IftheIPaddressmatchestheNEradiotermination'sIPaddress,theFPR
managementtrafficisterminated,ifnot,theFPRmanagementpacketsareforwardedvia
R-channeltotheFEradioterminationandterminatedthere(iftheIPaddressmatches
theFEradiotermination'sIPaddress).IftheIPaddressdoesnotmatchtheIPaddress
oftheFEradiotermination,thepacketisforwardedfurtherviaEthernetcable
connection.
TheFigure22:FPRmanagementdataforwardingshowshowtheFPRmanagement
trafficisforwardedtotheNEandFEradioterminationsIPhostswhenFPRVLANisON
(greendottedline)orOFF(reddottedline).

g Note: TheFPRVLANcanbeconfiguredregardlessofthefeature
LTE132:VLANbasedTrafficDifferentiationusage.

TheeNBEthernetportisconfiguredwithaseparateFPRmanagementVLANnetwork
interface.TheFPRmanagementtrafficusesaseparatequeuebelongingtothespecifc
VLANdedicatedtoFPRManagementtraffic.

3.2.5 Sales information


ThisfeaturebelongstoApplicationSoftware(ASW)productstructureclass.

3.2.6 User interface

Issue:02M DN0978033 147


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

3.2.6.1 Parameters

Therearenofeaturespecificparameters.However,thisfeatureenablesfurther
instancesoftheVLANrelatedparameterswhicharenecessarytoconfigurethe
additionalVLANinterfaceifFPRmanagementtrafficiscarriedthroughthededicated,
so-calledR-Channel.FormoredetailsrelatedtoVLANparameters,seeLTE132:VLAN
basedtrafficDifferentiationfeaturedescription.

3.2.6.2 Alarms

Therearenoalarmsrelatedtothisfeature.

3.2.6.3 Measurements and counters

Therearenomeaserementsandcountersrelatedtothisfeature.

3.2.7 Activating and Configuring the Feature


Foractivatingandconfiguringthefeature,seeFeatureActivationDocumentation

3.2.8 Abbreviations

3.2.8.1 0Z

LMT

LocalMaintenanceTerminal

LMP

LocalManagementPort

DSCP

DifferentiatedServicesCodePoint

FPR

FlexiPacketRadio

NE

Near-End

FE

Far-End

148 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

3.3 LTE564: IPsec on FTIB


3.3.1 Introduction to the feature
ThisfeatureaddsIPsecsupportonFTIB.

3.3.2 Benefits
FTIBprovidesmoderateIPsecthroughputperformanceandisthecostoptimized
solutionformanysites.

3.3.3 Requirements

3.3.3.1 Interdependencies between features

ThisfeaturerequiresLTE689:LTEIPsecSupport.

3.3.3.2 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

Table66 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

UE

NetAct

3.3.3.3 Hardware requirements

ThisfeaturerequiresFlexiSystemmoduleswhichsupportLTE.

3.3.4 Functional description


ThisfeatureprovidesIPseconFTIBhardware.ItisderivedfromfeatureLTE689:LTE
IPsecSupportandappliestoFTIBhardwareonly.

Issue:02M DN0978033 149


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Thefunctionalityofthisfeatureaswellassupportedalgorithms,counters,parameters
andalarmsareidenticalwithLTE689:LTEIPsecSupport.Theonlydifferenceislower
throughput-IPsecthroughputperformancebasedonstandardtrafficprofileislimitedto
160Mbit/sDL+UL.

3.3.5 Sales information


ThisfeaturebelongstoBasicSoftware(BSW)productstructureclass.

3.3.6 User interface

3.3.6.1 Parameters

Therearenoparametersrelatedtothisfeature.

3.3.6.2 Alarms

Therearenoalarmsrelatedtothisfeature.

3.3.6.3 Measurements and counters

Therearenomeasurementsandcountersrelatedtothisfeature.

3.3.7 Abbreviations

3.3.7.1 0Z

IPsec

InternetProtocolSecurity

3.4 LTE592: Link Supervision with BFD


3.4.1 Introduction to the feature
Thisfeatureimplementssingle-hopBidirectionalForwardingDetection(BFD)andmulti-
hopBFDsupport.BFDestablishesasessionbetweentheeNBandanEdgeRouter.
BothBFDpeerssendBFDcontrolpackets.IfnoBFDcontrolpacketisreceivedfromthe
peerwithinanegotiatedtimeinterval,alinkfailureisnotified.Onlyasynchronousmode
ofBFDissupported.

3.4.2 Benefits
Thisfeatureallowstodetectpathfailuresandthusenablestransportlinkredundancyin
casethetransportarchitecturesupportsredundantL2pathswhichareterminatedat
redundantEdgeRouters.

3.4.3 Requirements

150 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

3.4.3.1 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

Table67 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

UE

NetAct OSS5.3CD1

3.4.3.2 Hardware requirements

ThisfeaturerequiresFlexiSystemmoduleRelease2.

3.4.4 Functional description


BidirectionalForwardingDetection(BFD)isalinksupervisionprotocolwhichallowsto
detectfaultsbetweentwoforwardingenginesconnectedbyalink.BFDcanbeusedasa
componentinalinkredundancyprotectionscheme,becauseitpermitsdetectionofalink
failuretotherespectiveBFDpeer.TheBidirectionalForwardingDetection(BFD)
protocoldefinesamethodforlivenessdetectionofnetworkpaths.TheBFDsingle-hopis
usedacrosssinglenetworkhops.BFDcanalsobeusefulonpaths,whichmayspan
multiplenetworkhopsandfollowunpredictablepaths.Furthermore,apairofforwarding
enginesmayhavemultiplepathsbetweenthemthatmayoverlap.Inthesecasesthe
multi-hopBFDisused.

g Note: LinksupervisionwithBFDonlydetectslinkfailures.Innextreleasesthis
functionalitywillbeusedtoprovidealinkprotectionmechanism.

BFDestablishesasessionbetweentwoendpointsoveralink.ThedirectroutetoaeNB
issupervisedbyBFD.ItispossibletoestablishmaximumtwoBFDsessionsper
Networkinterface(plainEthernetinterfaceorVLANinterface).Theoperatorhasa
possibilityto:

activateanddeactivateBFDfunctionalityforeachsessionseparately
enableanddisablesendingofBFDalarmsforeachsessionseparately

TheBFDprotocolissupportedinAsynchronousmode.Thatmeans,bothendpoints
periodicallysendcontrolpacketstoeachother.

Issue:02M DN0978033 151


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Duringthesessionsetupphase,thenominalcontrolpacketsintervalis1s(thisisthe
minimumvalue).Whenthesessionisup,theintervalisnegotiatedwiththeremotepeer
basedonthelocalparameters(desMinTxIntandreqMinRxInt).Ifcontrolpackets
arenotreceivedwithinspecifiedtimeinterval,thesessionisconsideredasdown.The
appropriatealarmisraisedifsendingofBFDalarmsisenabled.

3.4.5 Sales information


ThisfeaturebelongstoBasicSoftware(BSW)productstructureclass.

3.4.6 User interface

3.4.6.1 Parameters

Table68:ParametersforLTE592:LinkSupervisionwithBFDshowstheparameters
relatedtotheLTE592:LinkSupervisionwithBFD.

Table68 ParametersforLTE592:LinkSupervisionwithBFD

Name Object Description Range / Step Default


value

bfdActivation IEIF "Thisparameteractivatesordeactivatesthe true,false false


firstBFDsessionofthisinterface.Activate:if
settovaluetrue,thetransmissionofBFD
controlpacketstowardstheremotepeeris
startedand,incasetheBFDsessionfails,
alarmsareraised.Deactivate:ifsettovalue
false,thetransmissionofBFDcontrol
packetstowardstheremotepeerisstopped
andallactivealarmsrelatedtotheBFD
sessionarecleared.AlsotheBTSdiscards
everyreceivedBFDpacketforadeactivated
BFDinstance.TheBFDsessioneffectively
doesnotexistatall."

bfdActivation2 IEIF Thisparameteractivatesordeactivatesthe true,false false


secondBFDsessionofthis
interface.Activate:ifsettovaluetrue,the
transmissionofBFDcontrolpacketstowards
theremotepeerisstartedand,incasethe
BFDsessionfails,alarmsare
raised.Deactivate:ifsettovaluefalse,the
transmissionofBFDcontrolpacketstowards
theremotepeerisstoppedandallactive
alarmsrelatedtotheBFDsessionare
cleared.AlsotheBTSdiscardsevery
receivedBFDpacketforadeactivatedBFD
instance.TheBFDsessioneffectivelydoes
notexistatall."

bfdAdminUp IEIF Thisparametercontrolstheadminstateof true,false true


thefirstBFDsessionoftheinterface.

152 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table68 ParametersforLTE592:LinkSupervisionwithBFD(Cont.)

Name Object Description Range / Step Default


value

Ifsettofalse,thesessionentersthe"Down"
state.Onlycontrolmessageswithstate
"AdminDown"aresenttothepeer.Allactive
alarmsoftheBFDsessionarecleared.
Ifsettotrue,thesessionleavesthe"Down"
state.Itwillreachthe"Up"stateiftheremote
peerisalsoin"Up"state.IftheBFDsession
fails,alarmsareraisedforit.
ThisparameterisonlyrelevantiftheBFD
sessionisactivated.

bfdAdminUp2 IEIF Thisparametercontrolstheadminstateof true,false true


thesecondBFDsessionoftheinterface.
Ifsettofalse,thesessionentersthe"Down"
state.Onlycontrolmessageswithstate
"AdminDown"aresenttothepeer.Allactive
alarmsoftheBFDsessionarecleared.
Ifsettotrue,thesessionleavesthe"Down"
state.Itwillreachthe"Up"stateiftheremote
peerisalsoin"Up"state.IftheBFDsession
fails,alarmsareraisedforit.
ThisparameterisonlyrelevantiftheBFD
sessionisactivated.

bfdDestAddress IEIF ThisisthedestinationIPaddresstobeused 7...15characters -


inthefirstBidirectionalForwardingDetection
sessionofthisinterface.Tobeenteredin
dotteddecimalformat.

bfdDestAddress2 IEIF ThisisthedestinationIPaddresstobeused 7...15characters -


inthesecondBidirectionalForwarding
Detectionsessionofthisinterface.Tobe
enteredindotteddecimalformat.

bfdDetectMult IEIF ThenegotiatedBFDcontrolword 2...10,step1 5


transmissioninterval,multipliedbythis
parameter,providesthedetectiontimefor
lostpacketsintheBFDsessionsofthis
interface.RoughlyspeakingbfdDetectMultis
thenumberofBFDcontrolpacketsthatthe
BTSmayloseinarow,beforeitshalldeclare
theBFDsessiontobedown.

bfdSourceUdpPort IEIF ThisparameterspecifiestheUDPSource 3784...65535,step1 3784


portofBFDsessionsofthisinterface.

Issue:02M DN0978033 153


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Table68 ParametersforLTE592:LinkSupervisionwithBFD(Cont.)

Name Object Description Range / Step Default


value

Note:valuerangeanddefaultvaluedepend
ontheBFDtype.IftheBFDtypeisMultiHop
BFD,valuerangeis4784,49152...65535
andthendefaultvalueequals4784.For
SingleHopBFDthevaluerangeis3784,
49152...65535andthedefaultvalueequals
3784.

bfdType IEIF Thisparameterspecifiesthetypeofthe singleHopBFD(0), multiHopBF


BidirectionalForwardingDetection(BFD) multiHopBFD(1) D(1)
sessionsofthisinterface:SingleHoporMulti
HopBFD.Theparameterisvalidforboth
BFDsessionsoftheinterface.

desMinTxInt IEIF Thisparameterspecifiestheminimum 500...5000ms,step 500ms


interval,thattheBTSwouldliketousewhen 500ms
transmittingBidrectionalForwarding
Detection(BFD)controlpackets.The
parameterisvalidforbothBFDsessionsof
thisinterface.

reqMinRxInt IEIF "Thisparameterspecifiestheminimum 500...5000ms,step 500ms


intervalbetweenreceivedBidirectional 500ms
ForwardingDetection(BFD)controlpackets
thattheBTSshallsupport.Theparameteris
validforbothBFDsessionsoftheinterface.

bfdActivation IVIF "Thisparameteractivatesordeactivatesthe true,false false


firstBFDsessionofthisinterface.Activate:if
settovaluetrue,thetransmissionofBFD
controlpacketstowardstheremotepeeris
startedand,incasetheBFDsessionfails,
alarmsareraised.Deactivate:ifsettovalue
false,thetransmissionofBFDcontrol
packetstowardstheremotepeerisstopped
andallactivealarmsrelatedtotheBFD
sessionarecleared.AlsotheBTSdiscards
everyreceivedBFDpacketforadeactivated
BFDinstance.TheBFDsessioneffectively
doesnotexistatall."

bfdActivation2 IVIF Thisparameteractivatesordeactivatesthe true,false false


secondBFDsessionofthis
interface.Activate:ifsettovaluetrue,the
transmissionofBFDcontrolpacketstowards
theremotepeerisstartedand,incasethe
BFDsessionfails,alarmsare
raised.Deactivate:ifsettovaluefalse,the
transmissionofBFDcontrolpacketstowards
theremotepeerisstoppedandallactive
alarmsrelatedtotheBFDsessionare

154 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table68 ParametersforLTE592:LinkSupervisionwithBFD(Cont.)

Name Object Description Range / Step Default


value

cleared.AlsotheBTSdiscardsevery
receivedBFDpacketforadeactivatedBFD
instance.TheBFDsessioneffectivelydoes
notexistatall."

bfdAdminUp IVIF Thisparametercontrolstheadminstateof true,false true


thefirstBFDsessionoftheinterface.
Ifsettofalse,thesessionentersthe"Down"
state.Onlycontrolmessageswithstate
"AdminDown"aresenttothepeer.Allactive
alarmsoftheBFDsessionarecleared.
Ifsettotrue,thesessionleavesthe"Down"
state.Itwillreachthe"Up"stateiftheremote
peerisalsoin"Up"state.IftheBFDsession
fails,alarmsareraisedforit.
ThisparameterisonlyrelevantiftheBFD
sessionisactivated.

bfdAdminUp2 IVIF Thisparametercontrolstheadminstateof true,false true


thesecondBFDsessionoftheinterface.
Ifsettofalse,thesessionentersthe"Down"
state.Onlycontrolmessageswithstate
"AdminDown"aresenttothepeer.Allactive
alarmsoftheBFDsessionarecleared.
Ifsettotrue,thesessionleavesthe"Down"
state.Itwillreachthe"Up"stateiftheremote
peerisalsoin"Up"state.IftheBFDsession
fails,alarmsareraisedforit.
ThisparameterisonlyrelevantiftheBFD
sessionisactivated.

bfdDestAddress IVIF ThisisthedestinationIPaddresstobeused 7...15characters -


inthefirstBidirectionalForwardingDetection
sessionofthisinterface.Tobeenteredin
dotteddecimalformat.

bfdDestAddress2 IVIF ThisisthedestinationIPaddresstobeused 7...15characters -


inthesecondBidirectionalForwarding
Detectionsessionofthisinterface.Tobe
enteredindotteddecimalformat.

bfdDetectMult IVIF ThenegotiatedBFDcontrolword 2...10,step1 5


transmissioninterval,multipliedbythis
parameter,providesthedetectiontimefor
lostpacketsintheBFDsessionsofthis
interface.RoughlyspeakingbfdDetectMultis

Issue:02M DN0978033 155


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Table68 ParametersforLTE592:LinkSupervisionwithBFD(Cont.)

Name Object Description Range / Step Default


value

thenumberofBFDcontrolpacketsthatthe
BTSmayloseinarow,beforeitshalldeclare
theBFDsessiontobedown.

bfdSourceUdpPort IVIF ThisparameterspecifiestheUDPSource 3784...65535,step1 3784


portofBFDsessionsofthisinterface.
Note:valuerangeanddefaultvaluedepend
ontheBFDtype.IftheBFDtypeisMultiHop
BFD,valuerangeis4784,49152...65535
andthendefaultvalueequals4784.For
SingleHopBFDthevaluerangeis3784,
49152...65535andthedefaultvalueequals
3784.

bfdType IVIF Thisparameterspecifiesthetypeofthe singleHopBFD(0), multiHopBF


BidirectionalForwardingDetection(BFD) multiHopBFD(1) D(1)
sessionsofthisinterface:SingleHoporMulti
HopBFD.Theparameterisvalidforboth
BFDsessionsoftheinterface.

desMinTxInt IVIF Thisparameterspecifiestheminimum 500...5000ms,step 500ms


interval,thattheBTSwouldliketousewhen 500ms
transmittingBidrectionalForwarding
Detection(BFD)controlpackets.The
parameterisvalidforbothBFDsessionsof
thisinterface.

reqMinRxInt IVIF "Thisparameterspecifiestheminimum 500...5000ms,step 500ms


intervalbetweenreceivedBidirectional 500ms
ForwardingDetection(BFD)controlpackets
thattheBTSshallsupport.Theparameteris
validforbothBFDsessionsoftheinterface.

3.4.6.2 Alarms

Table69:AlarmsforLTE592:LinkSupervisionwithBFDshowsalarmsrelatedtothis
feature.

Table69 AlarmsforLTE592:LinkSupervisionwithBFD

Alarm Alarm name Condition


number

61605 BFD Session down in ingress Thealarmisraisedifthealarmisenabled,theBFDstateforthe


direction for session $S sessionisnotAdminDownandneverthelessnoBFDpacketis
receivedatthelocalendduringthedetectiontime.

156 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table69 AlarmsforLTE592:LinkSupervisionwithBFD(Cont.)

Alarm Alarm name Condition


number

Pleasenotethat$symbolcantakevalues1or2and
indicateswhichsessionisdown.

61606 BFD Session down in egress Thealarmisraisedifthealarmisenabled,theBFDstateofthe


direction for session $S sessionisnotAdminDownandtheBFDpacketfromthefarend
containsthediagnosticcode='ControlDetectionTimeExpired'
ANDnoingressalarmispresent..
Pleasenotethat$symbolcantakevalues1or2and
indicateswhichsessionisdown.

61022 BFD DOWN ThealarmisraisediftheBFDserviceisnotavailableanymoreon


theBTSforaparticularinterface(plainEthernetorVLAN
interface).Incaseonly1BFDsessionisconfiguredandactivated
fortheinterface,thealarmisraisedifBFDonthissessionfailsin
eitheringressoregressdirection.
Incase2BFDsessionsareconfiguredandactivatedforthe
interface,thealarmisraisedifthereisasimultaneousBFD
failureonbothsessions.TheBFDfailureforeachsessionmight
beeitheroningressoregressdirection.

3.4.6.3 Measurements and counters

Thearenocountersrelatedtothisfeature.

3.4.7 Activating and Configuring the Feature


Foractivatingandconfiguringthefeature,seeFeatureActivationDocumentation

3.4.8 Abbreviations

3.4.8.1 0Z

BFD

BidirectionalForwardingDetection

3.5 LTE649: QoS Aware Ethernet Switching


3.5.1 Introduction to the feature
Thisfeatureintroducesintegrated,QoSawareEthernetswitchingbetweentheexternal
eNBEthernetports,ortheexternalportsandlocaleNBfunctions.TheFTIBmodule,
mentionedinthisdocumentisonlysupportedinFDD,butnotinTDDreleases.

Issue:02M DN0978033 157


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

DependingonthedeployedHardwaretypetheeNBsystemsub-modulesupports2-3
Ethernetports,connectedthroughanintegratedEthernetswitch.Oneportistypically
usedforthebackhaulconnection,whileotherportsmaybeconnectedtootherradio
equipment.TheEthernetswitchingcanbeusedforaggregationoftrafficfromother
eNBs,NodeBs,or2GBTSs,whichcouldbelocatedatthesameorothersites.Itisalso
possibletodaisy-chainseveralnetworkdevices.
TheEthernetswitchingsupportssixQoSpriorityqueues.(FTIBHardwareislimitedto
fourqueues).TheQoSindicationforswitchingcanbetakenfromtheEthernetp-bits
(VLANPCP)orIPDiffServCodepoints(DSCPs).Theswitchingcanbecarriedoutin
twodifferentmodes:VLANunaware-theVLANIDsaretransparenttotheswitch
(defaultmode)orVLANaware-VLANfilteringisapplied.Thefeatureincludesshaping
oftheaggregatedtrafficonalltransportEthernetegressports.
Inaddition,thefeatureincludesratelimitationforincomingtrafficfromother
eNBs/NodeBs/BTSs.ThisisappliedtoprotecttheeNBfromfloodingandinterferingwith
theinternalmessageflowsofthelocaleNB.Itcanbeconfiguredperingressport,but
canalsobeswitchedoff(default).

3.5.2 Benefits
ThisfeatureeliminatestheneedforaseparateswitchdeviceattheeNBsite.This
meansthattheoperatorscanreduceCAPEXandOPEX.Thebuilt-inswitchisQoS
aware.

3.5.3 Requirements

3.5.3.1 Interdependencies between features

LTE132: VLAN based Traffic Differentiation


TheeNBsupportssimplifiedsetupoftheVLANconfigurationfortheinternalL2switch
port.

LTE138: Traffic Shaping (UL)


Thisfeaturedefinesatrafficshapingfunctionwhichincludesshapingtoafixed,
configurablerate(SIR)whichmaybeexceededforalimiteddurationduringtraffic
bursts.Theallowableburstsizeisaconfigurableparameter(SBS).Incontrast,the
shapingfunctiondefinedintheEthernetswitchallowsonlytoshapethetraffictoafixed
rate.Toavoiddatalosses,thedimensioningoftheLTE138trafficshapingparameters
mustbecloselyalignedwiththeshapingintheEthernetswitchdefinedinthisfeature,
especiallywithrespecttotheallowableburstsize(SBS).Specifically,itisstrongly
recommededtoconfiguretheburstsizeinthelocaleNBandtheother
eNBs/NodeBs/BTSstotheminimumvalue(noburstsatall).

LTE140: Ethernet OAM


TheEthernetswitchsupportshandlingofEthernetOAMframes(LinkOAMandService
OAMframes).

LTE707: Flexi Transport sub-module FTIB


TheLTE649:QoSAwareSwitchingfeaturerequiresatransportsub-modulewhich
supportsLTE.TheFTIBisoneofthesupportedmodules.

158 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

LTE713: Synchronous Ethernet


TheEthernetswitchsupportshandlingofSynchronousEthernetslavefunctionalityinthe
eNB.

LTE800: Flexi Transport sub-module FTLB


TheLTE649:QoSAwareSwitchingfeaturerequirestransportsub-modulewhich
supportsLTE.TheFTLBisoneofthesupportedmodules.

LTE947:Flexi Multimode System Module FSMF


TheLTE649:QoSAwareSwitchingfeaturerequiresasystemmoduleoratransportsub-
modulewhichsupportsLTE.TheFSMFisoneofthesupportedsystemmodules.

3.5.3.2 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

Table70 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

UE

NetAct OSS5.3CD1

3.5.3.3 Hardware requirements

ThisfeaturerequiresFlexiSystemmoduleswhichsupportLTE.

3.5.4 Functional description


ThefunctionalprincipleoftheQoSawareEthernetswitchingisoutlinedbytheexample
shownintheFigure23:QoSawareEthernetswitching.
TheintegratedEthernetswitchingfunctionintheeNBaggregatestheuplinktrafficfrom
itselfandtheuplinktrafficreceivedfromtheconnectedeNBs/NodeBs/BTSs,andsends
itoutonthebackhaullink.Italsoperformsswitchingthedownlinktraffictotheconnected
eNBs/NodeBs/BTSs.Thebuilt-inshapingfunctionlimitstheuplinkdataratetothe
availablebandwidthofthebackhaullink.ThehighprioritytrafficoriginatingfromtheeNB
andfromtheothereNBs/NodeBs/BTSsissentoutimmediately.Ifthevolumeofthelow
prioritytrafficdoesnotcompletelyfitwithintheremainingbandwidth,itistherefore
queuedupandsentoutwithsomedelay,fillinguptheremainingavailablebandwidth

Issue:02M DN0978033 159


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

betweenthehighprioritytrafficandtheshapinglimit.Thisensuresoptimizeduseofthe
bandwidthonthebackhaullink.Incaseofcongestion,traffichastobediscardedwith
droppingthatstartswithlowprioritytraffic.

Figure23 QoSawareEthernetswitching

low
priority

high
priority
low
eNB priority
UplinktrafficeNB

eNB high
priority
low
priority
eNBcollocationexample Aggregateduplinktraffic
high
priority

UplinktrafficeNB

Inaddition,thefeatureincludesratelimitationforincomingtrafficfromother
eNBs/NodeBs/BTSs.ThisisappliedtoprotecttheeNBfromfloodingandinterferingwith
theinternalmessageflowsofthelocaleNB.Itcanbeconfiguredperingressport,but
canalsobeswitchedoff(default).
TheEthernetswitchingsupportssixQoSpriorityqueues.(FTIBHardwareislimitedto
fourqueues).TheQoSindicationforswitchingcanbetakenfromthe:

Ethernetp-bits(VLANPCP)
IPDiffServCodepoints(DSCPs)

Theswitchingcanbecarriedoutintwodifferentmodes:

VLANunaware:theVLANIDsaretransparenttotheswitch(defaultmode)
VLANaware:VLANfilteringisapplied

Transport module variants


Therearetwovariantsoftheswitchingfeature,dependingontheHWused:
Variant1:FSMF,FTLBandFSIH
Variant2:FTIB(FDDonly)
Thedifferencebetweenthistwovariantsarethenumberofoutputqueues,outputbuffer
andthenumberofexternalinterfaces.
Chaining concept
TheFigure24:Chainingconceptshowsthegeneralnetworkscenariousedfor
eNBs/NodeBs/BTSschaining.

160 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Figure24 Chainingconcept

eNB
Ethernet
EPC

Ethernet
backhaul
PacketNetwork

eNB
RNC,
Ethernet BSC,
...

Ethernet
BTS BTS

OneeNBisconnectedtothetransportnetworkviathecommonEthernetbackhaullink.
Otherradiodevices(forexample,othereNBs,UMTSNodeBsorGSMBTSs)canbe
connectedtothateNBviaEthernetinterfaces.Thebuilt-inEthernetswitchwithinthe
eNBaggregatestheuplinktrafficoftheconnecteddevicestothecommonbackhaullink
andswitchingthedownlinktraffictothesedevices.
Theotherradiodevicesmaybeco-locatedwiththeaggregatingeNBorlocatedat
differentsites.IftheconnecteddevicessupportEthernetswitching,itisalsopossibleto
daisy-chainmultipleeNBs/NodeBs/BTSs.
ThetrafficaggregationtowardsthebackhaullinkiscarriedoutinaQoSawaremanner,
usingmultipleschedulerqueuesfordifferentQoSclasses.Shapingmaybeappliedto
theaggregateduplinktrafficsuchthatitdoesnotexceedtheavailabletransport
bandwidth.Iftheaggregatedtrafficvolumeforaportexceedstheconfiguredshaperrate
limit,theuplinkframesarequeuedup,anddroppedifnecessary.

3.5.4.1 VLAN aware switching

ItispossibletoconfiguretheswitchingmodeoftheEthernetswitchforVLANaware
switching.TheEthernetswitchdoesnotmodifytheVLANIDofincomingframes.In
VLANawareswitchingmode:

TheVLANIDofincomingframesischeckedagainsttheVLANsconfiguredonthe
receivingEthernetport.IftheVLANIDmatcheswithoneoftheVLANsconfiguredfor
thatport,theframeissenttotheswitch.Ifnomatchisfound,theframeisdiscarded.
TheswitchforwardsframesaccordingtoIEEE802.1Q.Theegressportdecisionis
basedontheMACaddressandVLANIDlook-up.Onlyiftheidentifiedegressport
belongstotheframe'sVLAN,theframeistransmittedviathisport.Otherwiseitis
dropped.

Switching of untagged frames in VLAN aware switching mode


ThesubsystemsupportsalsoswitchingofuntaggedEthernetframeswhenoperatingin
VLANawareswitchingmode.ThehandlingofuntaggedframesinVLANawareswitching
modeisconfigurable.IfthevalueofacceptableFrameTypesis"AdmitTagged",the
devicewilldiscarduntaggedandPriority-taggedframesreceivedonthisinterface.Ifthe

Issue:02M DN0978033 161


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

valueisAdmitAll,tagged,untaggedandPriority-taggedframesreceivedonthis
interfacewillbeaccepted.UntaggedandPriority-taggedframesareassignedtothe
VLANdefinedbytheportDefaultVlanIdforthisinterface.
Theforwardingofuntaggedtrafficisconfigurableperport.Untaggedexternalframes
leavestheEthernetswitchasuntaggedframes.

3.5.4.2 VLAN unaware switching

WhileoperatinginVLANunawareswitchingmode,thebuiltinQoSawareswitchdoes
nottaketheVLANtagsintoaccountwhentakingforwardingdecisions.Thisapplies
regardlessofwhethertheVLANtrafficdifferentiationisactivatedoneNBsandwheather
eNBsuseseparateVLANs.
Inthiscase,thebroadcastdomainsofthetwoeNBsarenotseparated-thebroadcasts
fromeacheNBarevisiblefortheothereNB,aswellasthebroadcastsfromthenetwork
aredistributedtoeacheNB.

3.5.4.3 Scheduling and shaping for Ethernet QoS switching

TheEthernetschedulingandshapingfollowsthefunctionalmodelshowninFigure25:
TheEthernetschedulingandshaping(examplewithsixqueues).
ThetrafficreceivedfromthelocaleNBandfromchainednetworkequipmentis
aggregatedintheegressportqueues.QoSissupportedoneachportbytheuseof
egressschedulingqueues.Thetrafficismappedtooneoftheegressqueuesdepending
onitspriority.Theshaperattheegressportsensuresthattheconfiguredmaximum
transmissionrateoneachportisnotexceeded.

Figure25 TheEthernetschedulingandshaping

Egress
SPQueue VLAN
Shaper
handling
Queue2 Port
QoS Queue3
Scheduler
Classify Queue4 GE-port1
Queue5
Queue6 Ingress
VLAN
Bandwidth
handling Limiter

Switchingfabric
Egress
SPQueue VLAN
Shaper
handling
Queue2 Port
QoS Queue3
Scheduler
Classify Queue4
GE-port2
Queue5
Queue6 Ingress
VLAN
Bandwidth
handling Limiter

Egress
SPQueue VLAN
Shaper
handling
Queue2 Port
QoS Queue3
Scheduler
Classify Queue4 GE-port3
Queue5
Queue6 Ingress
VLAN
Bandwidth
handling Limiter

162 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

ThetrafficthatisnotlocallyterminatedintheeNBisclassifiedfortheegressqueues
accordingtoitspriorities.Theselectionofqueueintheegressschedulerismade
accordingtothevalueofthe Ethernet Switch Traffic Classification
Selectorparameter:
Ethernet Switch Traffic Classification SelectorsettoPCP
Inthiscase,theEthernetp-bitsaccordingtoIEEE802.1pareusedtoselectthe
queueforthetrafficclass.AnyDSCPvalueofthetrafficisignored.Therangeforthe
VLANpriorityis[0...7].AllpossibleVLANPCPsaremappedtoegressqueues.PCP
toegressqueuemappingisconfigurable.Untaggedframesareputtoafixedqueue,
whichisselectableviaanOAM-parameter.
Ethernet Switch Traffic Classification SelectorsettoDSCP
Inthiscase,theDiffServCodePoints(DSCP)areusedtoselectthequeueforthe
trafficclass.AnyavailablePCPsettingoftaggedframesisignored.Therangeforthe
DSCPvaluesis[0...63].AllpossibleDSCPcodepointsaremappedtoegress
queues.DSCPtoegressqueuemappingisconfigurable.Non-IPpacketswhichhave
noDSCP(forexampleARP,EthernetOAM,SynchronousEthernetmessages)are
puttoafixedqueue,whichisselectableviaanOAM-parameter.

AcombinedStrictPriority(SP)andWeightedRoundRobin(WRR)schedulingscheme
withconfigurableweights(W2-W6forFTLB,FSMF,FSIHandW2-W4forFTIB)isused
perswitchedtransportEthernetport(Figure26:QoSschedulingforswitchedEthernet
transportinterfaces-exampleforFTLBandFTIB).TheweightsforWRRschedulersare
configurable.

Figure26 QoSschedulingforswitchedEthernettransportinterfaces-examplefor
FTLBandFTIB
FTLB FTIB

Q1 SP
Q2 Q1 SP
Q3 Q2 W2
WRR Q3 W3
Q4 WRR
Q5 Q4 W4

Q6

IncontrasttoWFQ(WeightedFairQueuing),wheretheschedulingresultsina
distributionofbandwidthonbytelevel,theWRRschedulingprocessresultsina
distributionofpacketsaccordingtothedistributionoftheconfiguredsetofweights.
Egress port rate shaping
TheEthernetswitchsupportsegressrateshapingonalleNBexternalportsofthe
Ethernetswitch.Theshapinglimitstheaggregatedbandwidthatlayer2oneachportto
aconfigurablemaximumbitrate.Thisvalueisahardlimitwhichwillnotbeexceeded
alsoincaseofshortdatabursts.
EgressshapingismainlyneededontheEthernetportusedforbackhaulintheuplink
direction.Theshapingensuresthattheaggregatedbandwidthdoesnotexceedthe
allowablebandwidthofthetransportnetwork.Egressshapingmayalsobeusedwhen
sendingX2trafficdirectlytowardsachainedeNB.

Issue:02M DN0978033 163


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Incontrasttotheegressportrateshaping,theshapinginthenetworkinterfacesofthe
eNBischaracterizedbytheSIR(ShaperInformationRate)andtheSBS(ShaperBurst
Size).TheconfiguredSBSdefinesthelengthofaburstduringwhichadatastreammay
exceedtheSIR(burstsareplayedoutatfulllinespeed).Suchburstscanleadtobuffer
overflowintheEthernetswitch.Therefore,specialcareisneededinthedimensioningof
theshapingparameterswhenusingaShaperBurstSizeatthenetworkinterfaceshigher
thantheminimumSBSincombinationwithegressportrateshapingintheEthernet
switch.ThevalueoftheallowableSBSatthenetworkinterfacesmainlydependson:

theegressportshapingrateintheEthernetswitch
thebuffersizeintheEthernetswitch
thenumberofaggregatednetworkinterfacesfromthedifferentsources

Thesystemmustbedimensionedsuchthattheaggregatedburstsgeneratedbyall
sourcesdonotcausebufferoverflowintheegressbufferoftheEthernetporttowards
thebackhaulinterface.AconfigurableBurstSizeissupported.
AconfigurableTokenBucketshaperissupportedperswitchedtransportethernetegress
port.Theshaperratecanbeconfiguredwiththefollowingsteps:

1Mbpsstepsupto10Mpbs
5Mbpsstepsbeyond10Mbpsandupto100Mbps
50Mbpsstepsbeyond100Mpbsandupto1Gbps
500Mbpsstepsbeyond1Gbps

Ingress bandwidth limit


Thesubsystemsupportsingresstrafficratelimitinginordertoguaranteethatthe
bandwidth(onlayer2)doesnotexceedadefinedlimit.Themaximumallowedingress
bandwidthatlayer2isconfigurableperexternalEthernetportwiththefollowing
granularity:

1Mbpsstepsupto10Mpbs
5Mbpsstepsbetween10Mbpsand100Mbps
50Mbpsstepsbetween100Mpbsand1Gbps

3.5.5 Sales information


ThisfeaturebelongstoApplicationSoftware(ASW)productstructureclass.

3.5.6 User interface

3.5.6.1 Parameters

Table71:ParametersforLTE649:QoSAwareSwitching...showstheparametersrelated
totheLTE649:QoSAwareSwitching.

164 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table71 ParametersforLTE649:QoSAwareSwitching...

Name Object Description Range / Step Default value

acceptableFrameTypes ETHLK IfthevalueofacceptableFrameTypesis 0(ADMIT_ALL),1 0


"AdmitTagged",thedevicewilldiscard (ADMIT_TAGGED)
untaggedandPriority-taggedframes
receivedonthisinterface.Ifthevalueis
AdmitAll,tagged,untaggedandPriority-
taggedframesreceivedonthisinterfacewill
beaccepted.UntaggedandPriority-tagged
framesareassignedtotheVLANdefinedby
theportDefaultVlanIdforthisinterface.

l2BurstSize ETHLK "Thisparameterspecifiesthemaximum 0...600.1%,step1 00.1%


numberofbytesthatcanbetransmittedina 0.1%
singleburstinegressdirectiononthis
Ethernetinterfaceoflayer2switch.The
parameterisonlyvalidfortheFTLB,FSIH
andFSMFTransport,notvalidforFTIB
hardwareunit.Theparameterisdefinedas
percentageoftheegressshapingrateofthe
Ethenetinterface(parameterl2ShaperRate).
Theunitis0.1%,forexamplevalue50
means5%.Themaximumvalue=6%ofthe
configuredshapingrate."

l2ShaperBurstSize ETHLK Thisparameterdefinesthemaximumburst 0(32);1(64);2 15(1M)


sizeinoctetsthatcanbetransmittedina (128);3(256);4
singleburstinegressdirectiononthis (512);5(1k);6(2k);
Ethernetinterfaceoflayer2switch.The 7(4k);8(8k);9
parameterisonlyvalidfortheFSMr4 (16k);10(32k);11
hardwareunittype.Thedefaultvalueis15 (64k);12(128k);13
(1M). (256k);14(512k);15
(1M)
l2IngressRate ETHLK Thisparameterspecifiestherateforlimiting
RT_LINE_RATE(0), RT_LINE_RATE(0)
ingresstrafficattheethernetlinkinterface
RT_1(1),RT_2(2),
whenitparticipatesintheQOSawarelayer2
RT_3(3),RT_4(4),
switch.Parametervalueunit=MBit/s.TheRT_5(5),RT_6(6),
followinggranularitiesexist: RT_7(7),RT_8(8),
RT_9(9),RT_10
5Mbpsstepsbeyond10Mbpsandupto (10),RT_15(15),
100Mbps RT_20(20),RT_25
1Mbpsstepsupto10Mpbs (25),RT_30(30),
50Mbpsstepsbeyond100Mpbsandup RT_35(35),RT_40
to1Gbps (40),RT_45(45),
RT_50(50),RT_55
(55),RT_60(60),
RT_65(65),RT_70
(70),RT_75(75),
RT_80(80),RT_85
(85),RT_90(90),
RT_95(95),RT_100
(100),RT_150(150),
RT_200(200),
RT_250(250),

Issue:02M DN0978033 165


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Table71 ParametersforLTE649:QoSAwareSwitching...(Cont.)

Name Object Description Range / Step Default value

RT_300(300),
RT_350(350),
RT_400(400),
RT_450(450),
RT_500(500),
RT_550(550),
RT_600(600),
RT_650(650),
RT_700(700),
RT_750(750),
RT_800(800),
RT_850(850),
RT_900(900),
RT_950(950),
RT_1000(1000)

l2ShaperRate ETHLK Thisparameterspecifiesegresstheshaping


RT_LINE_RATE(0), RT_LINE_RATE(0)
rateoftheEthernetinterfacewhen RT_1(1),RT_2(2),
participatingintheQOSawarelayer2 RT_3(3),RT_4(4),
switch.Parametervalueunit=MBit/s.TheRT_5(5),RT_6(6),
followinggranularitiesexist: RT_7(7),RT_8(8),
RT_9(9),RT_10
1Mbpsstepsupto10Mbps (10),RT_15(15),
5Mbpsstepsbeyond10Mbpsandupto RT_20(20),RT_25
100Mbps (25),RT_30(30),
50Mbpsstepsbeyond100Mpbsandup RT_35(35),RT_40
to1Gbps (40),RT_45(45),
RT_50(50),RT_55
(55),RT_60(60),
RT_65(65),RT_70
(70),RT_75(75),
RT_80(80),RT_85
(85),RT_90(90),
RT_95(95),RT_100
(100),RT_150(150),
RT_200(200),
RT_250(250),
RT_300(300),
RT_350(350),
RT_400(400),
RT_450(450),
RT_500(500),
RT_550(550),
RT_600(600),
RT_650(650),
RT_700(700),
RT_750(750),
RT_800(800),
RT_850(850),
RT_900(900),
RT_950(950),
RT_1000(1000)

166 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table71 ParametersforLTE649:QoSAwareSwitching...(Cont.)

Name Object Description Range / Step Default value

l2VlanIdList ETHLK ThisparameterspecifiestheVLANsthatare Datatypeis -


supportedoverthisethernetinterfacewhenit structure-
participatesintheQOSawarelayer2switch. "l2VlanIdList"
Theparameterisalistofupto16entries
whereeachentryrepresentseitherasingle
VLANidentifierorarangeofVLAN
identifiers.TheVLANidentifiersofthe
variousentriesshouldnotbutmayoverlap
eachother.TheBTSinternallywillusea
cleanedlistonnon-overlappingidentifiers.
ThevalueofvlanIdListishowevernot
changedbytheBTS.
Thedefaultvalueoftheparameteristhe
emptylist.

highValue ETHLK Thisparameterspecifiestheuppervalueofa -1,1...4094,step1 -1specialvalue,


rangeofVLANidentifiers. meaning"notused"

g Note: Parameterof
thestructure-
VLANid1isreservedforun-taggedframes
handlingandshouldnotbeconfigured.
"l2VlanIdList"

lowValue ETHLK Thisparameterspecifieseitherasingle 1...4094,step1 1


VLANidentifierorthelowervalueofarange

g Note: Parameterof
thestructure-
ofVLANidentifiers.
VLANid1isreservedforun-taggedframes
"l2VlanIdList" handlingandshouldnotbeconfigured

portDefaultPriority ETHLK DefaultVLANpriorityforuntaggedframes. 0..7,step1 0


EveryuntaggedingressEthernetframeat
thisinterfacegetsassignedthisPortDefault
Priority.IfQoSclassificationmodeis
configuredtoVLAN-PCP,thispriorityisused
forenqueingdecisionoftheframe.Ifthe
frameegressestheswitchtagged,this
priorityshallbeusedintheVLANtagheader.
portDefaultVlanId ETHLK ThisparameterspecifiestheVLANidentifier 1..4094,step1 1
thatisinsertedinternallybytheFTMintoan
untaggedingressframethatentersthelayer
2switchviathisEthernetinterface.Inorder
thattheframewillbetransmittedviaanother
Ethernetinterface,afterlayer2switchinghas
beenperformed,thesameVLANidmustbe
configuredintheVLANidentifierlistofthat
Ethernetinterface(seeparameter
l2VlanIdList).Elsetheframewillbe
discarded.

g Note: DefaultVLANidcannotbe
configuredasapartofinterface's
configuredVLANidlist.

Issue:02M DN0978033 167


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Table71 ParametersforLTE649:QoSAwareSwitching...(Cont.)

Name Object Description Range / Step Default value

dscpMap L2SWI ThisparametermapsDSCPvaluestopriority Datatypeis -


queues.Thetablecontainsatmost64 structure-
entries,oneforeachpossibleDSCPvalue "dscpMap"
(0..63).
DefaultvaluesforFTIBhardwareunittype:
DSCPvalues48and46maptopriority
queue1,thisisthestrictpriorityqueue.
DSCPvalues38,36,34,30,28and26map
topriorityqueue2,thisisthefirstWRR
priorityqueue.
DSCPvalues22,20,18,14,12and10map
topriorityqueue3,thisisthesecondWRR
priorityqueue.
AllotherDSCPvaluesmapbydefaultto
priorityqueue4,thisisthethirdWRRpriority
queue.
DefaultvaluesforFTLB,FSIHandFSMF
hardwareunittype:
DSCPvalues48and46maptopriority
queue1,thisisthestrictpriorityqueue.
DSCPvalues38,36and34maptopriority
queue2,thisisthefirstWRRpriorityqueue.
DSCPvalues30,28and26maptopriority
queue3,thisisthesecondWRRpriority
queue.
DSCPvalues22,20,18,14,12and10map
topriorityqueue4,thisisthethirdWRR
priorityqueue.
AllotherDSCPvaluesmapbydefaultto
priorityqueue6,thisisthefifthWRRpriority
queue.

dscp L2SWI ThisparameterspecifiesaDSCPvalue. 0...63,step1 -

g Note: Parameterof
thestructure-
"dscpMap"

priorityQueue L2SWI Thisparameterspecifiesapriorityqueue. 1...6,step1 4


FTIBhardwareunittype:
g Note: Parameterof
thestructure- Priorityqueuevaluesrangefrom1to4
"dscpMap" where4meanslowestand1meanshighest
priority.Thedefaultvalueoftheparameter=
4.

168 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table71 ParametersforLTE649:QoSAwareSwitching...(Cont.)

Name Object Description Range / Step Default value

FTLB,FSIHandFSMFhardwareunittype:
Priorityqueuevaluesrangefrom1to6
where6meanslowestand1meanshighest
priority.Thedefaultvalueoftheparameter=
6.

enableLayer2Switching L2SWI Thisparameterenablesthelayer2switching true,false false


feature.
Ifthefeatureisswitchedoff,noswitching
betweentransportEthernetinterfaceswillbe
available.Insteadonlyasingletransport
Ethernetinterfacecanbeused.

l2PriorityQueueWeight2 L2SWI "Thisparameterspecifiestheweightforthe 1...8,step1 8


firstWeightedpriorityqueueofallethernet
interfacesthatparticipateintheQOSaware
layer2switch.
Notethattheethernetinterfacecontainsalso
astrictpriorityqueue.Thisqueueisreferred
toasqueuenumber1.

l2PriorityQueueWeight3 L2SWI Thisparameterspecifiestheweightforthe 1...8,step1 1


secondWeightedpriorityqueueofall
ethernetinterfacesthatparticipateinthe
QOSawarelayer2switch.
Thedefaultvalueofthisparameter=1for
theFTIBhardwareunit.
Thedefaultvalueofthisparameter=4for
theFTLB,FSIHandFSMFhardwareunits.
Notethattheethernetinterfacecontainsalso
astrictpriorityqueue.Thisqueueisreferred
toasqueuenumber1.

l2PriorityQueueWeight4 L2SWI Thisparameterspecifiestheweightforthe 1...8,step1 1


thirdWeightedpriorityqueueofallethernet
interfacesthatparticipateintheQOSaware
layer2switch.
Notethattheethernetinterfacecontainsalso
astrictpriorityqueue.Thisqueueisreferred
toasqueuenumber1.

l2PriorityQueueWeight5 L2SWI Thisparameterspecifiestheweightforthe 1...8,step1 1


fourthWeightedpriorityqueueofallethernet
interfacesthatparticipateintheQOSaware
layer2switch.
Thisparameterisonlysupportedforthe
FTLB,FSIHandFSMFhardwareunits.

Issue:02M DN0978033 169


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Table71 ParametersforLTE649:QoSAwareSwitching...(Cont.)

Name Object Description Range / Step Default value

Notethattheethernetinterfacecontainsalso
astrictpriorityqueue.Thisqueueisreferred
toasqueuenumber1.

l2PriorityQueueWeight6 L2SWI Thisparameterspecifiestheweightforthe 1...8,step1 -


fifthWeightedpriorityqueueofallethernet
interfacesthatparticipateintheQOSaware
layer2switch.
Thisparameterisonlysupportedforthe
FTLB,FSIHandFSMFhardwareunits.
Notethattheethernetinterfacecontainsalso
astrictpriorityqueue.Thisqueueisreferred
toasqueuenumber1.

portDefaultPriority L2SWI DefaultVLANpriorityforuntaggedframes. 1..4094,step1 1


EveryuntaggedingressEthernetframeat
thisinterfacegetsassignedthisPortDefault
Priority.IfQoSclassificationmodeis
configuredtoVLAN-PCP,thispriorityisused
forenqueingdecisionoftheframe.Ifthe
frameegressestheswitchtagged,this
priorityshallbeusedintheVLANtagheader.

portDefaultVlanId L2SWI ThisparameterspecifiestheVLANidentifier 1..4094,step1 1


thatisinsertedinternallybytheFTMintoan
untaggedingressframethatentersthelayer
2switchviathisEthernetinterface.To
transmittheframeviathesameoranother
Ethernetinterface,afterlayer2switchinghas
beenperformed,thesameVLANIdmustbe
configuredintheVLANidentifierlistofthat
Ethernetinterface(seeparameter
l2VlanIdList).Elsetheframewillbe
discarded.

priorityQueueNonIP L2SWI Thisparameterspecifieswhichpriorityqueue 1...6,step1 4


shallbeusedfornon-IPframes.Non-IP
framesexamplesareARP-,EthernetOAM-
andSynchronousEthernetmessages.
Thevaluerangeofthisparameter=1..4for
theFTIBhardwareunit.
Thevaluerangeofthisparameter=1..6for
theFTLB,FSIHandFSMFhardwareunits.
Thedefaultvalueofthisparameter=1for
bothhardwareunittypes,thisisthestrict
priorityqueue.

170 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table71 ParametersforLTE649:QoSAwareSwitching...(Cont.)

Name Object Description Range / Step Default value

priorityQueuePcp0 L2SWI Thisparameterspecifieswhichpriorityqueue 1...6,step1 -


shallbeusedforframeswithVLANPCPbits
value0.
Thevaluerangeofthisparameter=1..4for
theFTIBhardwareunit.
Thevaluerangeofthisparameter=1..6for
theFTLB,FSIHandFSMFhardwareunits.
Thedefaultvalueofthisparameter=4for
theFTIBhardwareunit,thisisaWeighted
RoundRobinpriorityqueue.
Thedefaultvalueofthisparameter=6for
theFTLB,FSIHandFSMFhardwareunits,
thisisaWeightedRoundRobinpriority
queue.

priorityQueuePcp1 L2SWI Thisparameterspecifieswhichpriorityqueue 1...6,step1 -


shallbeusedforframeswithVLANPCPbits
value1.
Thevaluerangeofthisparameter=1..4for
theFTIBhardwareunit.
Thevaluerangeofthisparameter=1..6for
theFTLB,FSIHandFSMFhardwareunits.
Thedefaultvalueofthisparameter=4for
theFTIBhardwareunit,thisisaWeighted
RoundRobinpriorityqueue.
Thedefaultvalueofthisparameter=4for
theFTLB,FSIHandFSMFhardwareunits,
thisisaWeightedRoundRobinpriority
queue.

priorityQueuePcp2 L2SWI Thisparameterspecifieswhichpriorityqueue 1...6,step1 -


shallbeusedforframeswithVLANPCPbits
value2.
Thevaluerangeofthisparameter=1..4for
theFTIBhardwareunit.
Thevaluerangeofthisparameter=1..6for
theFTLB,FSIHandFSMFhardwareunits.
Thedefaultvalueofthisparameter=3for
theFTIBhardwareunit,thisisaWeighted
RoundRobinpriorityqueue.
Thedefaultvalueofthisparameter=4for
theFTLB,FSIHandFSMFhardwareunits,
thisisaWeightedRoundRobinpriority
queue.

Issue:02M DN0978033 171


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Table71 ParametersforLTE649:QoSAwareSwitching...(Cont.)

Name Object Description Range / Step Default value

priorityQueuePcp3 L2SWI Thisparameterspecifieswhichpriorityqueue 1...6,step1 -


shallbeusedforframeswithVLANPCPbits
value3.
Thevaluerangeofthisparameter=1..4for
theFTIBhardwareunit.
Thevaluerangeofthisparameter=1..6for
theFTLB,FSIHandFSMFhardwareunits.
Thedefaultvalueofthisparameter=3for
theFTIBhardwareunit,thisisaWeighted
RoundRobinpriorityqueue.
Thedefaultvalueofthisparameter=4for
theFTLB,FSIHandFSMFhardwareunits,
thisisaWeightedRoundRobinpriority
queue.

priorityQueuePcp4 L2SWI Thisparameterspecifieswhichpriorityqueue 1...6,step11...6, -


shallbeusedforframeswithVLANPCPbits step1
value4.
Thevaluerangeofthisparameter=1..4for
theFTIBhardwareunit.
Thevaluerangeofthisparameter=1..6for
theFTLB,FSIHandFSMFhardwareunits.
Thedefaultvalueofthisparameter=2for
theFTIBhardwareunit,thisisaWeighted
RoundRobinpriorityqueue.
Thedefaultvalueofthisparameter=3for
theFTLB,FSIHandFSMFhardwareunits,
thisisaWeightedRoundRobinpriority
queue.

priorityQueuePcp5 L2SWI Thisparameterspecifieswhichpriorityqueue 1...6,step1 1


shallbeusedforframeswithVLANPCPbits
value5.
Thevaluerangeofthisparameter=1..4for
theFTIBhardwareunit.
Thevaluerangeofthisparameter=1..6for
theFTLB,FSIHandFSMFhardwareunits.
Thedefaultvalueofthisparameter=2for
theFTIBhardwareunit,thisisaWeighted
RoundRobinpriorityqueue.
Thedefaultvalueofthisparameter=3for
theFTLB,FSIHandFSMFhardwareunits,
thisisaWeightedRoundRobinpriority
queue.

172 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table71 ParametersforLTE649:QoSAwareSwitching...(Cont.)

Name Object Description Range / Step Default value

priorityQueuePcp6 L2SWI Thisparameterspecifieswhichpriorityqueue 1...6,step1 1


shallbeusedforframeswithVLANPCPbits
value6.
Thevaluerangeofthisparameter=1..4for
theFTIBhardwareunit.
Thevaluerangeofthisparameter=1..6for
theFTLB,FSIHandFSMFhardwareunits.
Thedefaultvalueofthisparameter=1for
theFTIBhardwareunit,thisisthestrict
priorityqueue.
Thedefaultvalueofthisparameter=2for
theFTLB,FSIHandFSMFhardwareunits,
thisisaWeightedRoundRobinpriority
queue.

priorityQueuePcp7 L2SWI Thisparameterspecifieswhichpriorityqueue DSCP(0),PCP(1) DSCP(0)


shallbeusedforframeswithVLANPCPbits
value7.
Thevaluerangeofthisparameter=1..4for
theFTIBhardwareunit.
Thevaluerangeofthisparameter=1..6for
theFTLB,FSIHandFSMFhardwareunits.
Thedefaultvalueofthisparameter=1for
bothhardwareunittypes,thisisthestrict
priorityqueue.

priorityQueueUntagged L2SWI Thisparameterspecifieswhichpriorityqueue 1...1,step1 -


shallbeusedforuntaggedframes.
Thevaluerangeofthisparameter=1..4for
theFTIBhardwareunit.
Thevaluerangeofthisparameter=1..6for
theFTLB,FSIHandFSMFhardwareunits.
Thedefaultvalueofthisparameter=1,this
isthestrictpriorityqueue.

qosClassification L2SWI Thisparameterspecifiesifthelayer2


switchingisbasedonDSCPtoPHB
mappingoronPCPtoPHBmapping.
-IncaseitisDSCPtoPHBmapping,the
priorityqueueforegresstrafficistakenfrom
parameterdscpMapforIPframesandfrom
parameterpriorityQueueNonIPfornon-IP
frames.

Issue:02M DN0978033 173


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Table71 ParametersforLTE649:QoSAwareSwitching...(Cont.)

Name Object Description Range / Step Default value

-IncaseitisPCPtoPHBmapping,the
priorityqueueforegresstrafficistakenfrom
theparameterspriorityQueuePcp0to
priorityQueuePcp7fortaggedframesand
fromparameterpriorityQueueUntaggedfor
untaggedframes.

switchId L2SWI Thisparameteridentifiesthelayer2switch.


Thevalueisalways1.

vlanAwareSwitch L2SWI ThisparameterspecifiestheQOSbased 0(false),1(true) false


switchingmodeasfollows:Ifsetto"true",
ethernetframestaggedwithaVLANIDshall
beswitchedbetweentwoethernetmember
portsofalayer2bridgeonly,ifbothportsare
memberofthesameVLAN.Elsethepacket
shallbedropped.Thehandlingofuntagged
framesdependsontheparameter
discardUntagged.

3.5.6.2 Alarms

Therearenoalarmsrelatedtothisfeature.

3.5.6.3 Measurements and counters

Table72:MesurementandcountersforLTE649:QoSAwareSwitchingshowsthe
countersforLTE649:QoSAwareSwitching.

Table72 MesurementandcountersforLTE649:QoSAwareSwitching

Counter Number Description

EthIfOutDiscShaping_15 M51123C6 NumberofEthernetTXpacketsdiscardedduetorateshaping.

EthIfInUnknownVLAN_15 M51123C7 NumberofreceivedEthernetpacketswithanunknownVLANID.

EthIfInDiscRateLimiting M51123C8 ThenumberofingressEthernetpacketsdiscardedduetorate


limiting.

ethIfOutDiscShaping_AF1 M51123C10 NumberofEthernetTXpacketsdiscardedduetoegressshaping


perqueueperinterface.

ethIfOutDiscShaping_AF2 M51123C11 NumberofEthernetTXpacketsdiscardedduetoegressshaping


perqueueperinterface.

174 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table72 MesurementandcountersforLTE649:QoSAwareSwitching(Cont.)

Counter Number Description

ethIfOutDiscShaping_AF3 M51123C12 NumberofEthernetTXpacketsdiscardedduetoegressshaping


perqueueperinterface.

ethIfOutDiscShaping_AF4 M51123C13 NumberofEthernetTXpacketsdiscardedduetoegressshaping


perqueueperinterface.

ethIfOutDiscShaping_AF5 M51123C14 NumberofEthernetTXpacketsdiscardedduetoegressshaping


perqueueperinterface.

ethIfOutDiscShaping_AF6 M51123C15 NumberofEthernetTXpacketsdiscardedduetoegressshaping


perqueueperinterface.

ethIfOutVlanMismatch M51123C16 NumberofEthernetdiscardedRXframesduetoVLANmismatch

ethIfOutDiscShaping M51131C0 Numberoftransportframes/packetsdiscardedduetoegress


shaping(Bufferoverflow).

3.5.7 Activating and Configuring the Feature


Foractivatingandconfiguringthefeature,seeFeatureActivationDocumentation

3.5.8 Abbreviations

3.5.8.1 0Z

BTS

BasetransceiverStation

CIR

CommittedInformationRate

CBS

CommittedBurstSize

DSCP

DifferentiatedServicesCodePoint

Issue:02M DN0978033 175


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

PCP

PriorityCodePoint

SBS

ShaperBurstSize

SIR

ShaperInformationRate

SP

StrictPriority

WFQ

WeightedFairQueueing

WRR

WeightedRoundRobin

3.6 LTE775: SCTP Multi-homing (MME)


3.6.1 Introduction to the feature
TheeNBsupportstwoIPaddressesforC-planeterminationatMME.
WhenLTE775(multi-homingatMME)isenabled,theeNBsupportsamulti-homedMME.
DuringassociationestablishingtriggeredbytheeNB,theMMEreportsthesecondaryIP
transportaddresstoeNB,accordingtoRFC-4960.

3.6.2 Benefits
HighreliabilityofC-planeduetotheprotectionagainstbreakdownsofthetransport
networkandtheMMEinterfaces.

3.6.3 Requirements

3.6.3.1 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

176 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table73 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

UE

NetAct OSS5.3CD1

3.6.3.2 Hardware requirements

ThisfeaturerequiresFlexiSystemmoduleswhichsupportLTE.

3.6.4 Functional description


Whenthisfeatureisenabled,theeNBsupportsamulti-homedMMEaccordingtoRFC-
4960.TheFigure27:Signallingtransportstackformulti-homedMMES1interfaceshows
theprotocolstackforC-Planeatmulti-homedMMEforS1interface.

Figure27 Signallingtransportstackformulti-homedMMES1interface
RadioNetwork
Layer S1AP

SCTP

Transport IP IP
Layer
LinkLayer LinkLayer

Phys. Layer Phys. Layer

Whenthefeatureisenabled,theMMEisabletouseIPmulti-homedSCTPtransport
service(Figure28:Multi-homedMME).TheS1ApplicationProtocolsupportsalocal
SCTPportnumberthatisboundtotwo(perMME)localIPtransportaddresses.

Issue:02M DN0978033 177


TransportandTransmissionFeatures LTERL20,FeatureDescriptions

Figure28 Multi-homedMME

Singleinterface Dualinterface
SingleIPaddress DualIPaddress

IP

eNB MME
TheMMESCTPendpointisidentifiedbyasourceSCTPportnumberandsourceIP
addresses.AccordingtoRFC-4960,atanygiventimeeachnodecansetupexactlyone
signalingtransportconnection(SCTPassociation)towardsanypeernode(SCTP
endpoint).Themulti-homedMMEintroducesthesupportoftwoMME-eNBtransport
pathswithoneSCTPassociation.
MME addresses handling during an SCTP association procedure
TheMMEprimaryIPaddressisconfiguredintotheeNBbeforehand.DuringanSCTP
initialization,eNBsendsanINITmessagetotheMMEprimaryIPaddress.Primaryand
secondaryIPaddressesaresenttotheeNBwithintheINIT-ACKchunkmessage.Then,
theeNBstoresboththeaddresses,andusesthemasdestinationIPforsendingdata.
TheIPaddressesreceivedintheINITACKmessagearevalidduringthelifetimeofthe
SCTPassociation.
SCTP Path Failure Detection (peer MME is SCTP multi-homed)
AnestablishedSCTPassociationissupervisedbysendingregularHeartbeat/DATA
chunksandreceivingrelatedACKmessageswithinthespecifictimeinterval.Ifthe
SCTPpeerendpointismulti-homed,eachSCTPpathissupervised.WhentheeNB
successfullyestablishestheSCTPassociationtowardsanSCTPmulti-homedMME,the
SCTPPATHFAILUREDETECTIONprocedurestartsautomatically.Formoredetails
relatedtoSCTPPathFailureDetection,seeFADLTEDatapathManagement.

3.6.5 Sales information


ThisfeaturebelongstoBasicSoftware(BSW)productstructureclass.

3.6.6 User interface

3.6.6.1 Parameters

ThefollowingtableshowstheparametersimplementedforthefeatureLTE775:SCTP
Multi-Homing.

178 DN0978033 Issue:02M


LTERL20,FeatureDescriptions TransportandTransmissionFeatures

Table74 ParametersforLTE775:SCTPMulti-Homing.

Full name Abbreviated name Managed object

Primary IPv4/v6 address ipAddrPrim LNMME


Secondary IPv4/v6 address ipAddrSec LNMME
SCTP path failure retransmission pathMaxRetrans SCTP
counter

3.6.6.2 Alarms

Table75 AlarmsforLTE775:SCTPMulti-Homing.

Alarm Alarm name Condition


number

7657 BASESTATIONCONNNECTIVITY Onlyapplicablewhenmulti-homingissupported.


DEGRADED
Causedby6204BTSfault,whichindicatesthatoneoftheS1
transportpathsinSCTPconnectiontoMMEhasfailed.
Afterthealarmisraised,SCTPclientateNBtriestorecoverthe
failedpathautomaticly.

3.6.6.3 Measurements and counters

Therearenomeaserementsandcountersrelatedtothisfeature.

3.6.7 Abbreviations

3.6.7.1 0Z

eNB

EvolvedNodeB

SCTP

StreamControlTransportProtocol

Issue:02M DN0978033 179


Operabilityfeatures LTERL20,FeatureDescriptions

4 Operability features

4.1 LTE163: Subscriber and Equipment Trace


Introduction to the feature
Thisfeatureprovidesdetailedsubscriber-orientedinformationatacall-levelforoneor
morespecificUEs.Theoperatorcanactivatesubscriberandequipmenttracingfora
limitedperiodoftimeforspecificanalysispurposes,forexample,for:

rootcausedeterminationofamalfunctioningmobile
advancedtroubleshooting
optimizationofresourceusageandquality
RFcoveragecontrolandcapacityimprovement
droppedcallanalysis
theE2Eprocedurevalidation

4.1.1 Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.
Operator benefits
Thesubscribertracedatacanbeusedtochecktheradiocoverageandcapacityandto
getfeedbackonthenetworkqualityandcapacityafteroptimizationoperations.Thus,it
bringsOPEXsavingsastheoperatorcanenhancethetroubleshootingandmonitoring
capabilities.

4.1.2 Requirements
Software requirements
Table76:Softwarerequirementsliststhesoftwarerequiredforthisfeature.

Table76 Softwarerequirements

System Release eNode B NetAct MME SAE GW

Release RL20 LBTS2.0 OSS5.3CD1 NS20 NG20

Hardware requirements
ThisfeaturerequireseitherFlexiSystemModule(FSM)R2orFSMR3.

4.1.3 Functional description


Functional overview
ThesubscriberandequipmenttracesupportsthetracingofIMSIorIMEInumbers.The
tracesareactivatedondemand.

180 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

Foreachtracedconnection,theeNBsupportsthetraceofthefollowinginterfacesand
protocols(theycanbetracedsimultaneously):

S1Interface:S1AP
Thefollowingitemsaretraced:
contextmanagement(forexample:contextsetup,release,andmodification
messages)
handoversignaling(forexample:handoverandpathswitchmessages)
S1CDMA2000tunneling
UEcapabilityinfoindication
E-RABmanagement(forexample:E-RABsetup,modify,andreleasemessages)
NAStransport
locationreporting
errorindication

X2Interface:X2AP
Thefollowingitemsaretraced:
basicX2mobility(forexample:handoverandUEcontextmessages)
errorindication

UuInterface:RRC
Thefollowingitemsaretraced:
RRCconnectionestablishment/re-establishment
RRCconnectionreconfiguration
RRCconnectionrelease
countercheck
initialsecurityactivation
inter-RATmobility
measurements
UEcapabilityenquiry
UL/DLinformationtransfer

Theoperatorselectsthetracedinterfaces.
Additionally,viathevendor-specificextension,partsofMACandRLCinformationcanbe
selectedtobetraced(ifitisactivatedintheeNB).
Onlythemaximumtracedepthissupported.ItmeansthatallL3signalingandcontrol
messagesandmeasurementreportsrelatedtoeachtracedcellonS1AP/X2AP/RRC
protocolsaretraced.
Thetracerecordconsistsof:

tracerecordheader,whichincludesforexample:
tracereferencenumber
globalcellID
eNBID
messagetype
timestamp

Issue:02M DN0978033 181


Operabilityfeatures LTERL20,FeatureDescriptions

tracedata(completemessage,accordingtothemaximumtracedepth)
Subscriber trace administration
Thesignaling-basedapproachisapplied.ThetracesessionactivationintheeNBis
triggeredbythecorenetwork(MME).ThetraceparametersaresentfromtheMMEto
theeNBwiththeS1APmessages.Whenthesessionstarts,theeNBnotifiestheiOMS
andtheNetActTraceViewer.

Figure29 Subscribetracegeneralarchitecture

3rdparty NetAct
tool
TraceData
TraceViewer
File

Datacollectiontool
forinternaltrace
support

Signaling-basedactivation NWI3 FileUpload

iOMS
MME Tracedata

Securitygateway

SocketconnectionTCPoverIPSec

Signaling-basedactivation
eNB
Tracedata

TheoperatorcanusetheNetActTraceViewertosetthetraceparameters.Inthiscase,
theNetActTraceViewerisresponsibleforforwardingthetraceparameterstothecore
network.
Tosupportthemultivendorcapability,itisalsopossiblethattheoperatorusesother
networkmanagementsysteminthecorenetworktostartthetracesession.Thenetwork
managementsystemonthecoresideneedstoincludetheIPaddressofitsTrace
CollectionEntity(TCE)inthetraceparameters.

g Note: ThenumberofTCEsconnectedtoasingleeNBmustnotexceed30.

Incaseofmultipletracesessionsofthesamesubscriber,separatetracereference
numbers(andtracereports)arecreated.
IncaseofhandoverusingtheX2interface,thesourceeNBsendsthetraceparameters
tothetargeteNBusingthehandover requestmessage.Thetracesessionis
deactivatedwhentheeNBreceivesthetracedeactivationmessagefromthecore
networkorthelastconnectionofthetracedsubscriberisreleased.

182 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

Subscribertracesessiondetails:

Thetracesessionstartsonlyifthecontrolobjectiscreatedandthelicenseforthis
featureisenabled.
SimultaneoustracingofseveralsubscriberswithintheeNBissupported.
Multipletracesessionsforthesamesubscriberwithdifferenttracereferences(trace
reportsaregeneratedforeachtracereference)aresupported.
Sincethesubscribertracesessionsareverydynamic(frequentcreationanddeletion
oftracesessioninstances),theUEtracesessionisnotmanagedontheO&Mto
avoidsendingalargenumberofnotificationstoNetAct.Thetracecontrolleris
responsibleformanagingthisobjectinternallywithineNB.Changesinthisobjectare
notnotified.

g Note: ThemaximumnumberofsimultaneouslytracedUEsineNBis60.
ThemaximumnumberofsimultaneouslytracedUEsintheNetActclusteris300.

Trace session management during eNB restart


Planned restart
WhentheoperatorperformsaplannedeNBrestart,therunningtracesessionsare
deactivatedintheTraceViewer.ThetraceparametersarestoredintheTraceViewerso
thatwhentheoperatorrestartsthepreviouslydeactivatedsessions,thesametrace
settingsareapplied.
Thesubscribertracesessionsactivatedviaathirdpartytoolmustbestoppedseparately.
ThesocketconnectiontoathirdpartytoolisreleasedaftertheeNBrestart.Itis
establishedwhentheoperatoractivatesthetracesessionagain.
Trace data reporting
Onlinetracereportingandfile-basedreportingaresupported:

onlinereporting:theiOMSreceivestracereportsfromtheeNBviaasocket
connectionasaTCPstream.TracereportsaresenttotheiOMSperiodically.The
tracereportcontainsallthetracerecordsofthesametracesessioncollectedsince
thelasttracereportcreation.Foronlinetracereporting,thetracedataaresentto
NetActortoanexternalIPaddress.
file-basedreporting:theiOMSreceivestracereportsfromtheeNBviaasocket
connectionasaTCPstream.TracereportsareuploadedtoNetActwheniOMS
informsaboutfinalizedlogfiles.Thetracelogcontainstracereportsofthesame
tracesessioncollectedsincethelastlogfileupload.Forsubscriberandequipment
trace,onetracelogfileisgeneratedforeachtracedsubscriberandtracesession.All
tracerecordsfromthesamesubscriberinthesametracesessionarestoredinthe
sametracelogfile.

ThetraceddatacanbesenttoNetActTraceViewerforevaluationandfromtheretoa
3rdpartyaddress.Thedatacanbealsosenttoa3rdpartyaddressfromtheeNB(inthis
caseonlytheonlinereportingissupported).
NetAct trace data handling
TheNetActTraceViewerdecodesthereceivedmessagestoareadableformat(for
example,XML)andstorestheconvertedmessagestotracelogfiles.

Issue:02M DN0978033 183


Operabilityfeatures LTERL20,FeatureDescriptions

Incaseoffile-basedreporting,theiOMSnotifiesNetActaboutavailabletracedatafiles
usingtheFilesReadyEventNWI3notificationandthenNetActtransfersthesefiles.
Thesamefilenotificationandtransfermechanismisusedforbasicmeasurements.

Figure30 TracefilestransferbetweenNetActandiOMS

NetAct OMS

NWI3FilesReadyEvent

HTTPSGET

Filetransfer

NWI3PIFILETransferred

AcknowledgedTrace
datafiledeletedfrom
thedisk

NetActTraceVieweristheapplicationfortracedatapresentationanditsupportsthe
followingfunctionalities:

sortingthereceivedmessagesperconnection(forexample,usingX2APIDorS1AP
ID)
presentingthemessageflowforeachconnection(theoperatorisabletoselecta
singlemessagetoseethemessagedetails)
presentingthecallprocessingprocedures(forexample,setup,release,HO,andso
on)
presentingabnormalbehaviors(forexample,drops,NACKs,andsoon)
3rd party tracing
ThetracedataaresentdirectlyfromtheeNBtoa3rdpartytoolusinganIPconnection.
Thereisaparameterinthetracecontrolobjectsothattheoperatorcanswitchthis
functionalityon/offforsubscribertraceandforcelltraffictraceseparately.Ifthis
functionalityisswitchedoff,thetracedatawillbesenttoNetActviaOMSregardlessof
whichTraceCollectionEntityIPaddressissetinthetraceparameters.
IftheTCEIPaddress(definedwiththeTraceCollectionEntityIPAddressparameter)is
nottheaddressofNetAct(NetActIPAddressparameter)andthe3rdpartytracingis
enabled,theeNBsendsthetracedatadirectlytothisIPaddress.Whencollectionentity
usingtheTCEIPaddressincludedinthetraceparameters.Messagereportswiththe
followingmessagetypesaresentviathisinterface:
startTrace
stopTrace
traceReport
isAlive
traceFailure

184 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

Theportnumberincludedinthetracecontrolobjectisusedforthissocketconnection.
TheIPconnectionbetweentheeNBandthesecuritygatewayissecuredwithIPsec.The
securityfromthesecuritygatewaytothe3rdpartytooldependsontheoperator
configuration.IftheIPconnectiontothe3rdpartyislostduringanactivecelltrace
session,thetracesessionisautomaticallystoppedintheeNB.TheeNBtriesto
reestablishtheIPconnection.Theoperatorisresponsibleforstoppingthetracesession
intheeNB.Forsubscribertrace,thetracesessioncontinuesuntilallS1connectionsof
thetracedsubscriberarereleased,theoperatorstopsthetracesession,ortheMME
sendsthedeactivationmessagetotheeNB.

g Note: Fortracedatasendingtoa3rdpartytool,onlyonlinereportingmodeis
supported.

4.1.4 System impact


Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.
Impact on network and network element management tools
TheNetActTraceViewerapplicationisusedformanagingthetracereports.

4.1.5 Sales information


Table77 Salesinformation

BSW/ASW License control in network element License control attributes

ASWNetAct NetAct -

4.1.6 User interface


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seetherelevantreferencedocumentation.
Alarms
Table78:Relatedalarmslistsalarmsrelatedtothisfeature.

Table78 Relatedalarms

Alarm ID Alarm name

6261 FailureinconnectionbetweenBTSandiOMSor3rdpartytool.

6263 Failureintracesession

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.
Key performance indicators

Issue:02M DN0978033 185


Operabilityfeatures LTERL20,FeatureDescriptions

Therearenokeyperformanceindicatorsrelatedtothisfeature.
Parameters
Table79:Newparameterslistsparametersintroducedwiththisfeature.

Table79 Newparameters

Full name Abbreviated name Managed Description


object

TraceControlidentifier ctrlTsId CTRLTS ItuniquelyidentifiesaTraceControlinstance.

3rdPartyTraceReporting extTraceReporting CTRLTS Tracereportingsupportfor3rdPartyTool.

MaximumUETrace maxUeTraceSessions CTRLTS ThemaximumnumberofallowedUEtracesessions.


SessionsAllowed

NetActIPAddress netActIpAddr CTRLTS NetActIPaddress.

OMSTracePortNumber omsTracePortNum CTRLTS TheTracePortNumbertobeusedwhileestablishing


traceconnection(TCP)towardsOMS/iOMS.

3rdPartyToolTracePort tceTracePortNum CTRLTS TheTracePortNumbertobeusedwhileestablishing


Number traceconnection(TCP)towards3rdPartyTool.

TraceReportingMode traceRepMode CTRLTS TracereportingmodetobeusedbyOMSforsending


tracereportstoNetAct.

UEActiveTraceSessions ueActiveTrcSessFlag CTRLTS ThisindicatesifthereareanyactiveUEtracesessions


PresentFlag runningwithineNB.

ActivateSubscriberAnd actSubscriberTrace LNBTS ThisisafeatureflagtoenableordisableSubscriberand


EquipmentTrace EquipmentTracefeature.

VendorSpecificExtension vendorSpecTracing CTRLTS Supportforvendorspecificextensiontracing(atpresent


Tracing onlyRLCandMACtracingsupported)

4.2 LTE185: System Upgrade


4.2.1 Introduction to the feature
LTE185:SystemUpgradeenablesasmoothupgradefromRL10toRL20intheoverall
network.RL20isbackwardcompatiblewithRL10.
ThisfeaturecoversusecasesandrequirementsforsystemSWupgradeoftheLTERA
network.eNBupgrade,OMSupgradeandNetActupgradeisinthescopeofthisfeature.

4.2.2 Benefits
ThefeatureensuresasmoothremoteupgradepathfromRL10toRL20.

186 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

4.2.3 Requirements

4.2.3.1 Software requirements

Table80 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

UE

NetAct NAR1.0

4.2.3.2 Hardware requirements

Thisfeaturerequiresnoneworadditionalhardware.

4.2.4 Functional description


ThesystemupgradeisperformedinatopdownapproachstartingwithNetActfollowed
byOMSandfollowedbyaneNBSWupgradeasshownintheFigure31:Topdown
upgradeapproach.Serviceoutagesareminimizedbyusingavailableresiliencyfeatures
andhardwareredundancyasfaraspossible.Itisnotpossibletotakethewholesystem
outofservicetointroducethenewSWrelease.
Asaconsequenceofthisapproach,NetActneedstosupportatleasttwoOMSreleases
andtwoBTSreleases(RL20,RL10).OMSofSWreleaseRL20needstosupporttwo
eNBreleases(RL20,RL10).AlsomixedeNBandOMSconfigurationsneedbesupported
byOMSandNetAct.

Issue:02M DN0978033 187


Operabilityfeatures LTERL20,FeatureDescriptions

Figure31 Topdownupgradeapproach

Step1
NetAct
releasen

Step2
topdown

OMS(1) OMS(2)
releasen releasen-1

Step3

BTS(1) BTS(2) BTS(3) BTS(4)


releasen releasen-1 releasen-1 releasen-1

g Note: FordetailedinstructionsonupgradingFlexiLTEBaseStationsandLTEOMS,
seeLTE_RL20NSNReleaseupgradeinstructions,availableinNOLSatthefollowing
path:Care>SoftwareDelivery>FlexiLTEBaseStation>ReleaseLN2.0>LN2.0
RL20SW>NSN_LTE_RL20_Release_Documentation_ERB_doc.zip.
NetAct
ForinstructionsonupgradingNetAct,seeupgradeinstructionsin
DescriptionoftheCommissioningandUpgradeProcedureintheNetAct
documentation.
OMS
ForinstructionsonupgradingOMSSWfromLTEOMS1.0toLTEOMS2.0,see
UpgradingfromLTEOMS1.0toLTEOMS2.0inNSNLTERadioAccess,Rel.RL20,
OperatingDocumentation.

ThefollowingfunctionalitiesaresupportedwiththeupgradefromRL10toRL20:

1. UpgradefromRL10toRL20ispossibleinonestep.
NointermediateSWversionsarenecessarytobeinstalled.
2. Conversionofconfigurationdata
Alloperatorconfigureddataarestoredandre-loadedagainintothesystem.The
datafromthepreviousreleasecanbere-usedaftertheupgrade.Thisdataincludes:
allconfigurationdataoftheFlexiMultiradioBTS
adaptationsdonebytheoperatorfordifferent(graphical)presentationsinBTS
SiteManagerorNetAct
PerformanceMeasurement(PM)configuration
TheNEconvertsconfigurationdataofanolderversiontotheformatfittingtothe
activatedSWversion.TheconfigurationdataofformerformatofreleaseRL10are
notlostduetoaconversiontothenewformat.RL10configurationdataisavailable
incaseafallbacktotheformerrelease.
3. Savingofsystemdata

188 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

Allsystemdatainformationlikeusersecurity(useraccounts,passwords)and
networksecurityrelatedinformation(certificates,keys)andlicensefilesarestored
beforeasystemupgrade.Thedatawillbeavailableafterthesoftware(SW)upgrade.
4. Fallback
WhileaSWupgradeisongoing,anNEisabletofallbacktotheformerSWloadin
caseofcriticalexceptions.Thisfallbackisautomaticallyinitiatedincaseofstability
problemswiththenewSW.Ifanautomaticfallbackisinitiated,analarmisraised.
TheautomaticfallbackpreventsasituationwhereaNEiscompletelyoutofservice
andservicepersonnelisneededonsiteforrepairaction.
AllNEssupportthemanualfallbacktoaformerSWreleaseandconfigurationdata.It
ispossiblefortheusertotriggerafallbacktoaformerrelease.
5. Upgradepost-conditionandcleanup
AfteranSWupgradebothSWreleases(RL20andRL10)areavailableontheNE.
ThepreviousSWloadincludingitscorrelatedconfigurationisstoredinnon-volatile
memory,oronaredundantdiscorsimilar,inordertoallowafallbackfromtheRL20
totheRL10version.
Bycleanupaction(removalofoldversion)anunwantedfallbacktoformerrelease
canbeexcluded.AnautomaticcleanupbytheNEisnotsupported.
6. Totalupgradeduration
TotalupgradeofalleNBsinthenetworkdoesnotlastlongerthantwohours.
Networksizeisassumedwith500-1000eNB.

4.2.4.1 LTE upgrade use cases

g Note: Thescenarioforupgradedescribedbelowisneededforasystemupgradefrom
RL10toRL20forthefirsttime.

Overall system upgrade scenario


Thisusecaseshowstheoverallhighlevelscenarioofasystemupgradeincluding
NetAct,OMSandeNBs.Thesystemupgradefollowsthetop-downapproachstarting
withhighestlevelelement(NetAct)andfinishingwithlowestlevelNE(eNBs).

g Note: Itishighlyrecommendedtoperformtheupgradeinatimeperiodwithlowtraffic
load(forexampleduringnighttime)asservicedegradationandpartialserviceloss
cannotbefullyavoidedduringanupgrade.

Preconditions

NetworksystemisavailableandactivewithaSWreleaseRL10.
O&MInterfacesbetweenNetActandOMSandbetweenOMSandeNBareworking.
NoHWoutageswhichwouldnotallowaccessingoneormoreNEsthataretobe
upgraded.

Description

1. SWloadsfornewreleasearepreparedandstoredinrepository.
NewNetActSWloadaswellasnewOMSSWloadisstoredonworkstation.The
eNBSWloadsarestoredontheNetActrepository.
2. UserperformsaSWupgradeoftheNetActsystemfromreleaseRL10toRL20.
NetActinternalredundancyisusedtominimizeserviceoutage.OnceNetActgeo-
redundancyfeatureisavailable,theredundantNetActcanbeusedtominimize
serviceoutagetimesduringtheupgrade.

Issue:02M DN0978033 189


Operabilityfeatures LTERL20,FeatureDescriptions

3. UserperformsupgradeofOMS.
OMSupgradeneedsbefinishedbeforetheassociatedeNBsareupgraded.
ItisnotmandatorytoupgradeallOMSsbeforeupgradingthefirsteNB.ButifOMS
resiliencyissupportedinthenetwork,ithelpstoavoidconflictsbetweenupgraded
eNBandnotyetupgradedOMS.
4. UserstartsupgradeofeNBs.
SeveraleNBscan-butneednot-beupgradedinparallel.NetActandOMSneedbe
readytooperatewithamixtureofeNBsinreleaseRL20andRL10.
5. Configurationdataissynchronized.
eNBsendsaconfigurationchangenotificationtotriggerNetActConfiguration
Management(CM)toinitiateconfigurationdataupload.
Assoonasthenewdatasynchronizationfeatureisincludedinthenewrelease,data
synchronizationfollowsthenewapproachwiththeconsequencethatonlythese
objectsareuploadedthathavebeenmodified.
6. Cleanup(optional)
NetActandOMSrepositoriescanbecleanedfromoldNESWandoldNE
configurationdata.Thecleanupisnotanautomaticaction,butneedsbetriggeredby
theuser(forexamplebyoverwritingoldSW).

Postcondition
Aftercompletingallstepssuccessfully:

LTEsystemwithNetAct,OMSandeNBsrunswithaSWversionwhichisreadyto
supportthefeaturesofthenewrelease
LTEsystemissynchronizedandusesnewmigratedconfigurationdata
eNBsarealreadyactive
newfeaturesofnewreleasearenotenabledautomaticallybutparametersare
availableand-whereneeded-suppliedwithdefaultvalues
Upgrade of OMS servers using backup OMS server (without automatic OMS
resiliency feature)
ThisoptionalusecasespecifiestheupgradeprocedureoftheOMSserversfromrelease
RL10toreleaseRL20usingthemanualOMSresiliencyfeature.Byusingbackupserver
theserviceinterruptiontimecanbeminimized.
IfOMSresiliencyisnotavailable,andthebackupserverisnotbeingusedforOMS
upgradeaswell,theconnectedeNBscannotbemonitoredandmanagedremotely
duringanOMSupgrade.
Preconditions

AbackupOMSservermustbeavailable.
NetActandtheelementmanagersmustbealreadyupgraded.

Description

1. ShutdowntheOMSservertobeupgraded.
2. ChangetheOMSsouthboundparameters(IP-address,securitykeys)inbackup
OMSservertothevaluesoftheOMSserver.Ifnecessaryforparameteractivation,a
shutdownandactivationofthebackupOMSserverisapplied.
3. ThebackupOMSservertakesovertheroleoftheformeractiveOMSserver.
TherelatedeNBsautomaticallyreconnectslatestafter2minutes.Alltopology
informationautomaticallyalignedwiththebackupOMSserver.Thesameappliesto
NetAct.

190 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

4. UpgradetheformerservingOMSservertoreleaseRL20.
5. ShutdownthebackupOMSserver.
6. Activatethealreadyupgraded(step4)OMSserver.
7. eNBsreconnectsautomaticallytothenowupgradedformerservingOMSas
specifiedinstep4.Theserviceisagaintemporarilylost.
8. Repeatsteps2to8withallactiveOMSservers.
9. FinallyupgradethebackupOMSserver.

Theupgradecanbeoptimizeddependentonthenetworkconfiguration.Ifpossible,the
OMSserviceneednotbeshiftedbacktotheoriginalserveraftereachupgrade.Instead,
therolesofactiveandbackupOMSservercanbeexchangedduringtheupgradethus
avoidingasecondtemporarylossofO&Mconnection.
Postconditions
AllOMSserversareupgradedtoreleaseRL20.
Upgrade eNB to new SW release including online data conversion
ThisusecasedescribesaremoteeNBupgradefromreleaseRL10toreleaseRL20.
LocalupgradeusingBTSSiteManagerisalsosupported.
TheserviceoftheeNB(s)istemporarilylostduringanupgrade.Aftertheupgrade,the
eNBreconnectstotheOMSandrestartsintoservicewithnewSW.

g Note: thisusecaseisnottobeconfusedwithSWupdate.

Preconditions

TheneweNBSWbuildreleaseRL20ispreparedandstoredinNetActrepository.
NetActisupgradedtothenewreleaseRL20,oratleastcapableofsupportingnew
eNBreleaseRL20.
TheconnectedOMSisupgradedtonewreleaseRL20oratleastcapabletosupport
neweNBreleaseRL20.
TheeNBisactiveandrunningwiththereleaseRL10SWbuild.
BTSO&MinterfaceandNWI3issetupandactive.

Description

1. TheuserdownloadsanewSWloadtotheeNBusingNetActSWManagement.
ExistingNetActSWMapplicationandSWdownloadprotocolwillbeused.
2. TheusersendsanactivationcommandfordownloadedSWusingNetActSW
Management.
ThecurrentSWbuildisnotlost,butkeptbytheeNBinnon-volatilememory(for
fallback).Optionally,theactivationcanbeincludedintheSWdownloadrequestby
settingtheautomaticActivationflag.
3. TheeNBrestartswithnewSWofreleaseRL20.
Beforearestart,theRL10configurationiscopied,sothatitisavailableforthenew
SWversionRL20.
4. Configurationdataisconverted.
OnactivationofanewSWversion,theeNBdetectsthatithasastoredconfiguration
fileofanolderreleaseofRL10only.TheeNBcopiesconfigurationdataandconverts
itintoanewformat.AllconfigurationdataportionsneedbeconvertedbytheeNB:

Issue:02M DN0978033 191


Operabilityfeatures LTERL20,FeatureDescriptions

BTS
TRS
RNWconfiguration
Configurationdataconversionincludesprovisioningofdefaultvaluestonew
parameters.DataconversionrulesneedbepartofanewSWbuild.
eNBkeepsformerconfigurationdatainnon-volatilememory(forfallback).
InsomeexceptionalcaseaBTSrestartmaybenecessaryafterdataconversion.
5. TheeNBestablishesanO&MconnectionusingaConnectionEstablishedIndication
(CEI)message.
TheeNBindicatesthenewSWversionreleaseRL20intheCEI.
OMSstoresreceivedtopologyinformationandsendsatopologyeventtoNetAct.
6. OMSsendsatopologyeventtoNetAct.
Thetopologyeventincludesallrelevanttopologyinformation.
7. NetActtriggersuploadofSWconfiguration.
TheuploadistriggeredbyatimerafterSWactivation.
8. UploadofmodifiedconfigurationdatatoNetAct.
NetActtriggersuploadoftheeNBconfigurationdata.
Ifautomaticuploadofdataisnotsupporteddatauploadmustbetriggeredmanually.
TheusertriggersconfigurationdatauploadfortheCombinedconfigurationfile(BTS,
TRS,RNW).
9. NetActalarmdatabaseisalignedwiththeeNB.
AlignmentisdonebyOMSandalarmdeviationsareforwardedtoNetAct.
10. TheUsercleansupOMSandNetActrepositoriesfromoldNESWandoldNE
configurationdata(optional).

Postcondition
Aftercompletingallstepssuccessfully,theeNB:

isactive
runswithSWLoadofnewrelease
usesconfigurationdataconvertedandvalidatedfornewrelease

OMSandNetAct:

areupdatedwithtopology

NetAct:

isupdatedwithalarminformation
isupdatedwitheNBconfiguration

Newfeaturesofthenewreleasethatneedconfigurationcanbeactivatedmanuallyafter
anupgrade.Licencesfornewfeaturesmayalsobeaddedafterupgrade.
Visualization

192 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

Upgrade of OMS
ThisUseCasedescribestheSWupgradeofOMStotheRL20controlledbyscript.
ThefollowingrestrictionsapplyfortheupgradeprocessRL20:

SWManagementviaNetActisnotavailableforOMS
DCAsupportforOMSSWManagamentisnotavailableinNetActOSS5.3
AsaconsequenceloadingandactivatingnewOMSSWversionmustbeperformed
locally.

Preconditions

NetActhasalreadybeenupgradedtoaSWversioncompatiblewiththeRL20.

Issue:02M DN0978033 193


Operabilityfeatures LTERL20,FeatureDescriptions

OMSisrunningwiththeRL10SWversionatleast
NWI3O&MInterfaceNetAct<=>OMSisestablished
NoHWoutages,whichwouldntallowaccessingOMS.
OMSdisksareavailableinredundantmode.

Description

1. UpgradepreparationsonOMS
a) BackupOMSSWanddatabase
Thisstepisrecommendedtobeabletoperformafallbackeveninthecaseofa
catastrophicfailureduringupgrade.BackupisstoredlocallyonOMSdisk.
b) CheckprerequisitesforOMSUpgradelikeenoughfreediskspace.
c) DownloadtheRL20SWtoOMS

2. OMSSWUpgrade
RemoteNetActSWMmanagementisn'tsupportedforOMS.TheOMSSW
installationandupgradeiscontrolledbyMMLcommandsfromworkstationand
supportedbyscripts.Followingstepsarenecessary:
a) SplittheredundantOMSdisks
Newimagewillbeinstalledononediskonly;theseconddiskremainsavailable
forfallback.
b) InstallupgradeimagetooneoftheOMSdisks.
c) StartOMSdataconversionscripts(LDAPuseraccounts/permissiondata).
d) RestartOMSusingtheupgradeddisk.
e) OMSactivatesthenewRL20SWandestablishesNWI3O&Mconnectionto
NetAct.Thisimpliestopologyandalarmalignment.

3. Performpost-checktestsonOMS
ThisstepisrecommendedsothatcorrectinstallationofSWloadandfunctionalityof
allsystemunitsisverified.
4. CommitupgradeofOMS
Aftercommitting,OMSestablishesnormaldiskredundancy.
Notethataftercommittingrollbackisn'tpossibleanymore.
Temporaryfilescanbedeletedaftercommitting.
GenerationofOMSBackupsofthenewSWandconfigurationisrecommended.

Postconditions

OMSrunningwiththenewRL20SWversion
OMShasre-establishedO&MconnectiontowardsNetAct

Visualization

194 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

OMS NetAct

Preperation

BACKUP OMS

Upgradepre-checks

CopynewOMStarget
SWtoOMSdisks

SplittheOMSdisks;
installnewtargetSWononedisk

StartOMSdata
conversionscripts OMS
Upgrade
ActivatenewSWanddataby
restartfromupgradeddisk

EstablishNWI3 connecttion

Topologydataupdate ; Alarmdataalignment

Post-checks

OMSupgradepost-checks

Commitupgrade

4.2.5 System impacts

4.2.5.1 Impacts on interfaces

ImpactonNEexternalinterfaces:

noimpactonNWI3
noimpactonBTSO&M
availableinterfacesforSWdownloadandSWactivationareusedwhileeNBSW
upgradeaswellasformanualfallback

Issue:02M DN0978033 195


Operabilityfeatures LTERL20,FeatureDescriptions

4.2.5.2 Impact on network elements

TheimpactedNEsaretheFlexiMultiradioBTS,NetActwithallLTErelevantapplications
includingOptimizer,Traffica(whenapplicable),Traceapplication,theNorthbound
interfacesandtheOMS.

4.2.6 Sales information


TheLTE185:SystemUpgradefeaturebelongstobasicsoftware(BSW)features.

4.2.7 User interface

4.2.7.1 Parameters

Notapplicable

4.2.7.2 Alarms

Thefollowingalarmisrelatedtothisfeature:

Table81 AlarmsfortheLTE185:SystemUpgradefeature

Alarm Alarm name Condition


number

7651 BASE STATION OPERATION Amajorfault(orfaults)hasoccurredinthebasestation.Check


DEGRADED thereasonforthefaultfromthesupplementarytextfieldofthe
alarm.

4.2.7.3 Measurements and counters

Notapplicable

4.2.8 System responses to failures


TheNEperformsanautomaticfallbacktotheformerSWversionandformer
configurationdataincaseofacriticalSWupgradeexceptions:

newSWreleasedoesnotstartup
forOMS:establishmentofNWI3isnotsuccessful

TheNEraisesanalarmincaseofanautomaticfallback.Theusermustbeinformedthat
upgradewasnotsuccessful.AfallbacktotheformerreleaseincludesallkindsofSWof
aNEaswellasallkindsofNEconfigurationdata.
Automatic fallback eNB to SW release RL10
ThisusecasedescribesanautomaticeNBfallbackfromreleaseRL20toreleaseRL10.
Precondition

196 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

TheneweNBSWbuildreleaseRL20hasbeendownloadedandactivationhasbeen
startedorfinishedoneNB.Notethatfallbackcanbeinitiatedalsolater,whenSW
upgradeisfinishedalready.
Description

1. eNBdetectsasevereerroranddecidestofallbacktoRL10.
OneexampleofasevereerrorisafailureofnewSWtorestart.
2. eNBrestartsSWbuildRL10.
ThecurrentSWbuildwillnotbelost,butkeptbyeNBinnon-volatilememory(for
fallback).
TheSWbuildRL20includingthenewconvertedconfigurationdataandalready
configuredmodificationsislost.
3. eNBestablishesaconnectiontoOMS.
4. eNBsendsaSWupdaterequestindicatingitsactivatedSWbuildversionRL10.
5. NetActcheckstheSWbuildversionthatiscurrentlymarkedasactivefortheNE.
WhenNEupgradeisdone,NetActsetsthedownloadedandactivatedSWversion
RL20toActivebasedontimerexpiry.Detailedtimeisbeyondscopeofthis
documentbutissupposedtobebetween10-30minutes.
6. NetActsendsSWdownloadrequestwiththecurrentlyactiveSWtargetbuild
descriptor.
TwocasesneedbedistinguisheddependingonwhetherthenewSWisalready
markedasactiveinNetAct:
a) WhileSWupgradestillSWbuildRL10ismarkedasActiveinNetAct:
NetActwillsendSWtargetRL10perSWdownloadrequest.
IfSWfilesofthesameversionalreadyexistintheeNB,eNBchecksthe
checksumandlengthofthesetodecidewhetheradownloadisrequested.
ifnodownloadisnecessary,theSWbuildRL10keepsrunning.

b) IftheNEfallbackisrequestedlater(aftertimerexpiryinNetAct)andnewSW
versionRL20isactive:
NetActwillsendSWtargetRL20perSWdownloadrequest.
eNBwilldownloadrequestedSWfilesfromthefileserver.
eNBrestartsSWbuildversionRL20.

Postcondition
DependingonwhetherafallbackwasstartedwhileSWupgradewasrunning,orlater
aftertheactivationofnewSWonly:

theeNBhasfallenbacktoSWbuildreleaseRL10.Configurationdataareinstate
RL10.
theeNBhasbeendownloadedwithnewSWversionnagainandtheSWupgrade
hasbeenrestarted.

4.2.9 Activating and configuring the feature


Thisfeaturedoesnotrequireactivation.

Issue:02M DN0978033 197


Operabilityfeatures LTERL20,FeatureDescriptions

4.3 LTE433: Cell Trace


Introduction to the feature
Withthisfeatureitispossibletofollowtheconnectionsongoinginacellandverifythe
intendedfunctionalitieswithinacell.Itcanbeusedforadeeperanalysisifproblems
occurandwhenvariousperformancemeasurementsdonotgiveaclearindicationofthe
problem.

4.3.1 Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.
Operator benefits
Thecelltracedatacanbeusedtochecktheradiocoverageinaparticularnetworkarea
andtogetfeedbackonthenetworkqualityandcapacityafteroptimizationoperations
(likeparameterfine-tuning).Thus,itbringsOPEXsavingsastheoperatorcanenhance
thetroubleshootingcapabilitiesandreduceexpensivedrivetests.

4.3.2 Requirements
Software requirements
Table82:Softwarerequirementsliststhesoftwarerequiredforthisfeature.

Table82 Softwarerequirements

System Release eNode B NetAct MME SAE GW

Release RL20 LBTS2.0 OSS5.3CD1 - -

Hardware requirements
Thisfeaturerequiresnoneworadditionalhardware.

4.3.3 Functional description


Functional overview
Withthecelltrace,alltheUEsinatargetcellthatareintheconnectedstatearetraced
simultaneously.
ForeachtracedconnectiontheeNBsupportsthetraceofthefollowinginterfacesand
protocols(theycanbetracedsimultaneously):

S1Interface:S1AP
Thefollowingitemsaretraced:
contextmanagement(forexample:contextsetup,release,andmodification
messages)
handoversignaling(forexample:handoverandpathswitchmessages)

198 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

S1CDMA2000tunneling
UEcapabilityinfoindication
E-RABmanagement(forexample:E-RABsetup,modify,andreleasemessages)
NAStransport
locationreporting
errorindication

X2Interface:X2AP
Thefollowingitemsaretraced:
basicX2mobility(forexample:handoverandUEcontextmessages)
errorindication

UuInterface:RRC
Thefollowingitemsaretraced:
RRCconnectionestablishment/re-establishment
RRCconnectionreconfiguration
RRCconnectionrelease
countercheck
initialsecurityactivation
inter-RATmobility
measurements
UEcapabilityenquiry
UL/DLinformationtransfer
paging

g Note: Theuserplaneisnottraced.

Theoperatorconfigureswhichcellshouldbetracedandselectsthetracedinterfaces.
Additionally,viathevendor-specificextension,TA(TimingAdvance)informationcanbe
selectedtobetraced(ifitisactivatedintheeNB).Withthecelltrace,theIMSI
informationofthetracedconnectionsisnotsupported,buttheNetActTraceViewer
applicationdeliverstheidentifiers(forexample,X2AP-IDorS1AP-ID)ofthetraced
connectionssothatoperatorcanfolloweachtracedconnection.
Onlythemaximumtracedepthissupported.ItmeansthatallL3signalingandcontrol
messagesandmeasurementreportsrelatedtoeachtracedcellonS1AP/X2AP/RRC
protocolsaretraced.
Cell trace administration
Forthecelltraffictrace,themanagement-basedapproachisusedfortracesession
activationanddeactivation.Thecelltraffictracefeatureisoptional(license-based)and
theActivate cell traceparameterisintroducedtocontroltherelevantlicense.
NetActTraceViewerapplicationisusedforactivating/deactivatingthecelltracesand
collectingthetracedata.Theactivation/deactivationcommandsaretransferredtoeNB
asaConfigurationManagement(CM)parameterplanusingthegenericplan
managementoperations.

Issue:02M DN0978033 199


Operabilityfeatures LTERL20,FeatureDescriptions

g Note: IftheactCellTraceparametervalueissettofalseduringanactivetrace
session,allthecell/interfacetracesessionswillbestoppedandMTRACEobjectsare
notdeleted.Inthiscase,theTraceViewermightnotshowthecorrectstatusofthetrace
sessionthathasbeenstopped.Therefore,itisrecommendedtodeletefirstthe
MTRACEobjectsbeforesettingtheactCellTraceparametervaluetofalse.

Figure32 Celltracearchitecture
NetAct

3rdparty TraceViewer TraceData


tool
File

Configurator Datacollectiontool
forinternaltrace
support

NWI3 FileUpload

iOMS

Tracedata
EthernetPort/Backhaul

Securitygateway

IPSec

EthernetPort/Backhaul
CM

Tracedata
Trace
Function

eNB
Administration
TraceData

Thecelltracesessionstartswhenthetracesessioninstance(containingthetrace
parameters)iscreated.Foreachtracedcellonetracesessioninstanceiscreated.
Celltracesessiondetails:
Thetracesessionstartsonlyifthecontrolobjectiscreatedandthelicenseforthis
featureisenabled.
Activeconnectionswithinacellaretraceduntilthemaximumnumberoftraced
connections(definedwiththecellMaxActiveUEsTracedparameterandintroduced
withLTE644:Configurablecelltracecontent)isreached.Foreachtraced
connection,onetracerecordingsessionisstarted.Whentheconnectionisstopped
orwhenthemaximumnumberoftracedconnectionsisreached,theeNBstarts
tracingotheractiveconnectionsuntilthetracesessionsisstopped.

200 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

ThemaximumnumberofsimultaneouscelltracesessionsintheeNBis12.Itis
possible,forexample,tostartacelltracesessionforNetActandatracesessionfor
a3rdpartytool(3rdpartytracing)simultaneouslyinonetracedcell(tracereportsare
generatedforeachtracereference).
Thetracesessionstartswhenthetracesessioninstanceiscreated.

CelltracesessioninstancesarenotdeletedintheeNBaftertheeNBrestart,butthe
tracesarenotrestartedautomatically.
Trace session management during eNB restart
TheactivecelltracesessionsarerestartedautomaticallyaftertheeNBrestart.
Planned restart
WhentheoperatorperformsaplannedeNBrestart,therunningtracesessionsare
deactivatedintheTraceViewer.ThetraceparametersarestoredintheTraceViewerso
thatwhentheoperatorrestartsthepreviouslydeactivatedsessions,thesametrace
settingsareapplied.
Trace data transfer
Onlinetracereportingandfile-basedreportingaresupported:

onlinereporting:theiOMSreceivestracereportsfromtheeNBviaasocket
connectionasaTCPstream.TracereportsaresenttotheiOMSperiodically.The
tracereportcontainsallthetracerecordsofthesametracesessioncollectedsince
thelasttracereportcreation.
file-basedreporting:theiOMSreceivestracereportsfromtheeNBviaasocket
connectionasaTCPstream.TracereportsareuploadedtoNetActwheniOMS
informsaboutfinalizedlogfiles.Thetracelogcontainstracereportsofthesame
tracesessioncollectedsincethelastlogfileupload.

ThetraceddatacanbesenttoNetActTraceViewerandfromtheretoa3rdparty
address.Thedatacanbealsosenttoa3rdpartyaddressfromtheeNB(inthiscase
onlytheonlinereportingissupported).

g Note: Thenumberoftracecollectionentities(TCEs)connectedtoasingleeNBmust
notexceed30.

NetAct trace data handling


TheNetActTraceViewerdecodesthereceivedmessagestoareadableformat(for
example,XML)andstorestheconvertedmessagestotracelogfiles.
Incaseoffile-basedreporting,theiOMSnotifiesNetActaboutavailabletracedatafiles
usingtheFilesReadyEventNWI3notificationandthenNetActtransfersthesefiles.
Thesamefilenotificationandtransfermechanismisusedforbasicmeasurements.

Issue:02M DN0978033 201


Operabilityfeatures LTERL20,FeatureDescriptions

Figure33 TracefilestransferbetweenNetActandiOMS

NetAct OMS

NWI3FilesReadyEvent

HTTPSGET

Filetransfer

NWI3PIFILETransferred

AcknowledgedTrace
datafiledeletedfrom
thedisk

NetActTraceVieweristheapplicationfortracedatapresentationanditsupportsthe
followingfunctionalities:

sortingthereceivedmessagesperconnection(forexample,usingX2APIDorS1AP
ID)
presentingthemessageflowforeachconnection(theoperatorisabletoselecta
singlemessagetoseethemessagedetails)
presentingthecallprocessingprocedures(forexample,setup,release,HO,andso
on)
presentingabnormalbehaviors(forexample,drops,NACKs,andsoon)
3rd party tracing
ThetracedataaresentdirectlyfromtheeNBtoa3rdpartytoolusinganIPconnection.
Thereisaparameterinthetracecontrolobjectsothattheoperatorcanswitchthis
functionalityon/offforsubscribertraceandforcelltraffictraceseparately.Ifthis
functionalityisswitchedoff,thetracedatawillbesenttoNetActviaOMSregardlessof
whichTraceCollectionEntityIPaddressissetinthetraceparameters.
IftheTCEIPaddress(definedwiththeTraceCollectionEntityIPAddressparameter)is
nottheaddressofNetAct(NetActIPAddressparameter)andthe3rdpartytracingis
enabled,theeNBsendsthetracedatadirectlytothisIPaddress.Whencollectionentity
usingtheTCEIPaddressincludedinthetraceparameters.Messagereportswiththe
followingmessagetypesaresentviathisinterface:
startTrace
stopTrace
traceReport
isAlive
traceFailure

Theportnumberincludedinthetracecontrolobjectisusedforthissocketconnection.
TheIPconnectionbetweentheeNBandthesecuritygatewayissecuredwithIPsec.The
securityfromthesecuritygatewaytothe3rdpartytooldependsontheoperator
configuration.IftheIPconnectiontothe3rdpartyislostduringanactivecelltrace

202 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

session,thetracesessionisautomaticallystoppedintheeNB.TheeNBtriesto
reestablishtheIPconnection.Theoperatorisresponsibleforstoppingthetracesession
intheeNB.Forsubscribertrace,thetracesessioncontinuesuntilallS1connectionsof
thetracedsubscriberarereleased,theoperatorstopsthetracesession,ortheMME
sendsthedeactivationmessagetotheeNB.

g Note: Fortracedatasendingtoa3rdpartytool,onlyonlinereportingmodeis
supported.

4.3.4 System impact


Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.
Impact on network and network element management tools
TheNetActTraceViewerapplicationisusedformanagingthetracereports.
Impact on system performance and capacity
Ifalltheavailableinterfacesaretraced,theMCUprocessorloadcanincreaseby20%.
NetActTraceViewersupportsthemaximumof1.5Mbit/stracedatathroughputwhichin
practicemeans:

maximumtwocelltracesessionsperNetActregionwithahighloadscenarioand
maximumtracedepth,or
approximatelyeightcelltracesessionsperNetActregionwitha50%loadscenario
andthetracecontentreducedto50%

4.3.5 Sales information


Table83 Salesinformation

BSW/ASW License control in network element License control attributes

ASW - -

4.3.6 User interface


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seetherelevantreferencedocumentation.
Alarms
Table84:Relatedalarmslistsalarmsrelatedtothisfeature.

Table84 Relatedalarms

Alarm ID Alarm name

6261 FailureinconnectionbetweenBTSandiOMSor3rdpartytool.

Issue:02M DN0978033 203


Operabilityfeatures LTERL20,FeatureDescriptions

Table84 Relatedalarms(Cont.)

Alarm ID Alarm name

6263 Failureintracesession

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.
Key performance indicators
Therearenokeyperformanceindicatorsrelatedtothisfeature.
Parameters
Table85:Newparameterslistsparametersintroducedwiththisfeature.

Table85 Newparameters

Full name Abbreviated name Managed Description


object

ActivateCellTrace actCellTrace LNBTS ThisisafeatureflagtoenableordisableCellTrace


feature.

CellIdentifier cellId MTRACE ThisparameterhastheE-UTRANCellIdentifier


(eutraCelId)oftheCellcorrespondingtothetracedcell.It
issameascontainedintheE-Utrancellglobalidentifier
(ECGI)ofthecell.

CellTraceMode cellTrcMode MTRACE Thisindicatesthestatusofthecelltracesessioni.e.


whetherthecelltracesessionneedstobeenabledor
disabled.

E-UTRANTrace eutranTraceId MTRACE ThisidentifiesanUEtracesession.


Identifier

Celltracesession mTraceId MTRACE ItuniquelyidentifiesaTraceControlinstance.


identifier

3rdPartyToolCell tceCellTracePortNum MTRACE TheTracePortNumbertobeusedforthisCelltrace


TracePortNumber sessionwhileestablishingtraceconnection(TCP)towards
3rdPartyTool.Thiswillbeusedonlyif3rdPartyTracing
forCellTraceisused.

TraceCollection tceIpAddress MTRACE IPaddressofthetracecollectionentityof3rdPartyTool.


EntityIPAddress Thiswillbeusedonlyif3rdPartyTracingforCellTraceis
enabledandtheprovidedIPaddressisdifferentfrom
NetActIPaddress.

InterfacesToTrace tracedInterfaces MTRACE Thisidentifiesthelistofinterfaceprotocolstobetraced.

204 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

4.4 LTE475: Automatic iOMS Resiliency


4.4.1 LTE475: Automatic iOMS Resiliency - introduction
Withthisfeature,itispossibletodefinetwoseparateiOMSs,thatareabletoservea
giveneNB.PrimaryandsecondaryiOMSsareassigneddifferentIPaddresses.By
default,theeNBusestheprimaryiOMS.IftheconnectiontotheprimaryiOMSislost
andcannotbere-establishedafterseveralre-connectionattempts,theiOMSswitches
automaticallytothesecondaryiOMSandtriestosetupanewconnection.Ifconnection
tothesecondaryiOMSisnotpossible,theNetworkElementtriestore-establish
connectivitytotheprimaryiOMS.
OncetheconnectiontothesecondaryiOMSisestablished,theNEidentity,topology
informationandcurrentalarmsareautomaticallytransferredtoit.Next,thesecondary
iOMSautomaticallyinformsNetActthattheNEisnowservedbythesecondaryiOMS
andtransfersautomaticallyalarmsandtopologydatatoNetAct,whichupdatesits
internalreferencesimmediatelysothatallmanagementactionsareroutedviathe
servingiOMS.
SwitchingfromthefailedtothebackupiOMSisdoneautomatically;onlyalarmsand
notificationsresultingfromiOMSfaultarereported.Thatswitchoverworksregardlessif
theservingiOMSwastheprimaryorthesecondaryone.However,noautomatic
switchoverisperformedwhentheoriginalservingiOMSisbroughtbackintoservice.Ifit
istoberestoredastheservingiOMS,theoperatorhastoperformmanualswitchover.
ThiscanbedoneviamassconfigurationdownloadtoallaffectedNEs.
VariousconfigurationsforprimaryandsecondaryiOMSaresupported.
ThefigurebelowshowsaconfigurationinwhichasinglesecondaryiOMSservesasa
backupforseveralprimaryiOMSs.

NetAct

Primary Primary Primary


iOMS iOMS iOMS

primaryBTSOMlink
secondaryBTSOMlink
NWI3link

Issue:02M DN0978033 205


Operabilityfeatures LTERL20,FeatureDescriptions

4.4.2 Benefits
MinimizedinterruptionofO&Mconnectivity,ifiOMSisundergoingroutine
maintenanceorarepair

4.4.3 Functional Description


iOMSresiliencysolutionallowscontinuousoperabilityincaseofaniOMSfailureoriOMS
toNEconnectionfailure.
WithiOMSresiliencyitispossibletouseaback-upiOMS(thesecondaryiOMS)incase
ofthedefaultservingiOMS(theprimaryiOMS)failure.TheiOMSconnectedtotheNEis
calledtheservingiOMS.
IfservingiOMSfailsoriftheconnectionbetweenNEandtheservingiOMSfails,the
AutomaticiOMSresiliencyfeaturemakesallNEsundertheservingiOMSautomatically
connecttothesecondaryiOMS.
TheiOMSswitchoverisdoneautomaticallybytheNE.IfNEisnotabletocommunicate
withtheservingiOMS,itautomaticallyattemptstoestablishcommunicationwitha
secondaryiOMS(providingitisalreadyconfigured).iOMSresiliencysolutionusesthe
O&MprotocolbetweenNEandiOMS(BTSOM).PrimaryandsecondaryiOMSdonot
communicatebetweeneachother.TheNEcanbeconnectedonlytoasingleiOMSata
time.
Incaseofproblemswiththetransportnetwork,itispossibletoworkwithaconfiguration
inwhichpartoftheNEsisservedbytheprimary,andothersareservedbythe
secondaryiOMS.
Automatic iOMS switchover scenarios

failureoftheservingiOMS
connectionbreakbetweenservingiOMSandNEcausedbytransportnetwork
problems

iOMS resiliency solution


ThedatabaseoftheNEcontainsreferencestothetwoiOMSswithdifferentIP
addressesi.e.primaryandsecondary.Bydefault,NEtriestousetheprimaryiOMS.The
iOMStowhichtheNEiscurrentlyconnectediscalledtheservingiOMS.Ifconnectionto
theservingiOMSislost,theNEattemptstoconnecttotheotherone.Ifthisisnot
possible,theNEtriestoconnecttothepreviouslyservingiOMSagain.
WhenservingiOMSswitchesduetoafailure,NEidentityaswellastopologyinformation
(includingstateinformationandcurrentlyactivealarms)areautomaticallytransferredto
thenewiOMS.
TheexistingfunctionalityoftopologyeventsandtopologyuploadinNetActandiOMSis
enhancedinordertoinformNetActaboutthechangeoftheservingiOMS.Afterthe
iOMSswitchover,topologydataandalarmsarealignedbetweenthenewservingiOMS
andNetAct.
DuringanautomaticiOMSswitchover,theNEisnotaccessiblefortheoperatorfora
periodofafewminutes.TelecomfunctionalityoftheNEduringthisintervalisnot
affected.

206 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

ThesameO&Mfeaturesareavailabletotheoperatorregardlessifaconnectionismade
viatheprimaryorsecondaryiOMS(providedbothiOMSssupportthesamefeatureset).
However,aniOMSactinginasecondaryrolemaynotbeabletohandleallNEsthat
attempttoconnecttoit.iOMSrejectsconnectionsifthelimitofNEsthatcanbeservedis
exceeded.
Thisfeaturedoesnotneedactivationordeactivation.However,iOMSresiliencyworks
foraspecificNEonlyifasecondaryiOMSisconfiguredinitsdatabase.Thus,the
featurecanbeeasilydisabledforagroupofNEsbynotconfiguringthesecondaryiOMS
intheirdatabases.Inaddition,theoperatorcanassignanNEoragroupofNEseitherto
theprimaryorthesecondaryiOMSexplicitly;thiscanbeusedduringtheupgrade
procedure.
IftheservingiOMSfailsandcannotcommunicatewithNetAct,anyPMdatathatis
presentonitcannotbeuploadedtoNetActandislostinthiscase.However,ifPMdata
isstillaccessiblewhentheiOMSisactivatedafterrepair,itisautomaticallyuploadedto
NetAct.
Ifamassoperation(e.g.massSWdownload)isongoingwhenaswitchoveroccurs,the
servingiOMScannotcompletetheoperation.Inthiscase,itistypicallynotpossibleto
determineeasilyifallNEshavealreadybeenhandledsuccessfully,anditisnecessary
tore-starttheoperation.Notethatthisisnotanewerrorscenario,itisequivalenttothe
failureofanon-resilientiOMSortoascenarioinwhichanon-resilientiOMSlosesO&M
connectivitytosomeorallofitsservedNEs.
ThePMdatathatwasalreadyloadedintotheprimaryiOMSbutwasnottransferredto
NetActislostincaseofanentireiOMSfailure.IfiOMSreceivesPMdatafromanetwork
element,itstartstotransferitimmediatelytoNetActandnodataislost.IfiOMSis
restoredafterafailure,thependingPMdata(infixediOMS)isautomaticallyuploadedto
NetAct.
Operator-controlled switchover
OperatorhasalsothepossibilitytorequestaniOMSswitchoverexplicitly.Thisis
achievedbyaplandownload.Intheplan,aspecificparametermustbesetwhich
requeststheeNBtoperformtheswitchover.
Noautomaticswitchoverisperformed,iftheoriginallyservingiOMSisbroughtbackinto
serviceafterrepairormaintenance.Therefore,theoperatorhastoperformamanual
switchovertobringtherepairediOMSbackintoservice.Thiscanbedoneviaamass
configurationdownloadtoallaffectedNEs.SincethetargetiOMSisidentifiedbya
symbolicconstant(primary/secondary),theoperatordoesnotneedtoexplicitlyspecify
theidortheIPaddressofthetargetOMSandtherequiredconfigurationchangeisquite
easytohandle.
Multiple configurations
ThesolutionallowsforthecreationofmultipleconfigurationsoftheO&Mnetworkhaving
onesecondaryiOMSformultipleprimaryiOMSs,orhavingprimaryandsecondaryiOMS
groupedinpairs.ItisalsopossiblethattheNEsconnectedtooneprimaryiOMScanuse
differentsecondaryiOMSs.
SinceiOMSsarephysicallyintegratedintoNetAct,theyarealsoequivalentwithrespect
totransporttopology,aslongastheyareassignedtothesamesub-network.Thus,there
arenorestrictionsastowhichiOMScanservewhicheNBs,andthesimplestresiliency
schemecanbeapplied,whereasinglesecondaryiOMSservesagroupofprimary
iOMSs.Sincenotopologydependenciesneedtobeconsidered,assigningabackup
iOMScanbedoneautomaticallyinnetworkplanning.Forsmallnetworks,asingle

Issue:02M DN0978033 207


Operabilityfeatures LTERL20,FeatureDescriptions

secondaryiOMSissufficient,forlargerNetworks,severalsecondaryiOMSsare
required,eachbackingupagroupofotheriOMSs.Also,configurationswithaseparate
secondaryiOMSforeachprimaryiOMSaresupported.
Impact on iOMS performance
ServinganNEbyasecondaryandprimaryiOMSrequiresthesameamountof
processing/memory/non-volatilestoragecapacity.Thus,itisnotpossibletoassignall
availableiOMScapacitytoNEsinprimaryroles,sincethennobackupcapacityis
availableandtheiOMSresiliencyfeaturedoesnotwork.Theactualcapacitytobe
reservedforNEsinasecondaryroledependsontheredundancyschemeapplied.
IfasinglededicatedsecondaryiOMSisdefined,noNEsintheprimaryrolecanbe
assignedtoitbecausecapacitytoserveatleastasingleiOMSfailureisrequired.
IfloadsharingbetweeniOMSsisapplied,thereservedcapacitymustnotexceedthe
minimumcapacityrequiredforhandlingatleastasingleiOMSfailurebythesystemi.e.
inascenariowithtwoiOMSsmonitoringeachothereachiOMScanhaveupto50%of
itscapacityreservedinprimaryrole.
IfthenetworkconsistsofalargenumberofiOMSsandresiliencyofasingleiOMS
failureisnotsufficient,itisnecessarytocreatedisjointedsetsofiOMSsthatare
protectedagainstsingleiOMSfailuresbyoneofthetwoschemesdescribedabove.
Applyingamorecomplexschemeisalsopossible,butitisnotrecommended,sinceit
requiresquitecomplexnetworkplanning.

4.4.4 System Impacts

4.4.4.1 Interdependencies between Features

Thisfeaturedependsonthefollowingfeatures:
LTE654:ConfigurationManagement

4.4.5 Managed Objects

4.4.5.1 Parameters

Table86:ParametersfortheLTE475:AutomaticiOMSResiliencyshowstheparameters
implementedfortheLTE475:AutomaticiOMSResiliencyfeature.
TheparametersbelowrefertotheIPNOobjectwithintheeNB'stransportconfiguration.

Table86 ParametersfortheLTE475:AutomaticiOMSResiliency

Name Short name Object Description Range / Step Default


type value

SecondaryOMSIP secOmsIpAddr string ThisparameterspecifiestheIP validIP 0.0.0.0


address addressoftheOMSservingin address
secondaryrole.Itisusedfor
OMSresiliency.Value0.0.0.0

208 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

Table86 ParametersfortheLTE475:AutomaticiOMSResiliency(Cont.)

Name Short name Object Description Range / Step Default


type value

meanstheparameterisnot
used,asecondaryOMSisnot
defined

ServingOMS servingOms enumer Thisparametershowswhich none(0), -


ation OMS(primaryorsecondary)is primary(1),
thecurrentservingOMS.Thisis secondary(2)
aread-onlyparameter.

ServingOMS servingOmsAdmi enumer Thisparametercanbemodified automatic(0), automatic


administrativesetting nSetting ation toindicatehowtheNEshould primaryForce (0)
selectitsservingOMS. d(1),
Automaticselection(value secondaryFor
"automatic")meansthattheNE ced(2)
autonomouslyselectsitsserving
OMSbasedonavailabilityofthe
configuredprimaryorsecondary
OMS.TheNEmayalsobe
administrativelyassigned/locked
toeithertheconfiguredprimary
ortheconfiguredsecondary
OMS(values"primaryForced"
and"secondaryForced").

ServingOMSSwitchover servingOmsSwoR enumer Thisparameterrequestsan noSwitchover noSwitchove


Request equest ation administrativeswitch-overfrom (0), r(0)
currentservingOMS(primaryor primaryReque
secondary)totheotherOMS. sted(1),
Theparametervaluespecifies secondaryRe
theOMStowhichtheswitch- quested(2)
overisrequested.Theswitch-
overisrejectediftheOMSto
whichswitch-overisrequestedis
notreachable.

4.5 LTE521: Security on Ethernet ports on FCM/FSM2


Introduction to the feature
ThepurposeoftheLTE521:SecurityonEthernetportsonFCM/FSM2featureisto
separatethesensitiveandnon-sensitivetrafficbymeansofapropervirtualLAN(VLAN)
configuration.

4.5.1 Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.
Operator benefits

Issue:02M DN0978033 209


Operabilityfeatures LTERL20,FeatureDescriptions

ThisfeatureincreasesthesecurityofthedatasentintheinternaleNBnetwork.

4.5.2 Requirements
Software requirements
Table87:Softwarerequirementsliststhesoftwarerequiredforthisfeature.

Table87 Softwarerequirements

System eNodeB NetAct MME SAE GW UE


Release

Release RL20 LBTS2.0 OSS5.3 - - -


CD1

Hardware requirements
ThisfeaturerequiresstandardSystemModule(FSM-r2)hardware.

4.5.3 Functional description


ThefollowinglogicaltraffictypesareswitchedbytheEthernetswitchdeviceinside
SystemModule(FSM-r2):

subscriberpayloadandanykindofcontrolandmanagementtrafficbetweentheUE,
theeNBandthecorenetworknodesaccordingto3GPP
Thistypeofdataissensitiveandmustbeproperlyprotected.
internalEthernettraffic,whichisexchangedbetweenmodulesinsideeNB
Thistypeofdataisalsosensitiveandmustbeproperlyprotected.
externalEthernettrafficto/fromsitesupportequipment(forexample,BatteryBackup
Unit(BBU),OvervoltageProtection(OVP)andExternalTransportEquipmentport)
andtrafficto/fromBTSSiteManagerconnectedviaLocalManagementPort(LMP)
Thistypeofdataisassumedtobenon-sensitive.

BecauseofSystemModule(FSM-r2)architecturalconceptalltraffictypessharethe
sameEthernetswitch.TosecuretheinternalEthernettraffic,thefollowingsecurity
requirementsapply:

ThesensitiveinternalEthernettrafficisseparatedfromexternalEthernettrafficby
meansofVLANseparation.
InterceptinginternalEthernettrafficonexternalportsisprevented.
ReroutingofinternalsensitiveEthernettrafficviaexternalportstowardsexternal
equipmentandthewaybackisprevented.
TrafficfromexternalEthernetportsreusesexistingsecuritytunnels.

IngresstrafficvialocalEthernetportisswitchedtotheFTMCPU.ByusingIPfiltering
accordinglytotheinternalaccesscontrollists,theFTMCPUdecideswhethertrafficcan
enterthesensitivepart.
TheVLANseparationsupportcanbeconfiguredlocallyorfromaremotelocationby
userwithproperrights.Forsecurityhardening,thelocalhostCPUisalwaysinvolvedin
theconfigurationprocess.

210 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

g Note: ThisfeatureintroducessecurityforEthernetportsonSystemModule(FSM-r2).
ForinformationonsecurityforEthernetportsonBTS10(FSM-r3),see
LTE593:SecurityforEthernetportsonFCT/FSM3featuredescription.

Feature configuration
TheLTE521:SecurityforEthernetportsonFCM/FSMv2featurecanbeconfiguredtobe
enabledordisabledeitherfromNetActorbytheBTSSiteManager.Thedefault
configurationisenable.

Whenthefeatureisenabled:
Externaltraffic(non-sensitivedata)isseparatedfrominternaltraffic(sensitive
data)viaVLANtagging.
BTSSiteManager(BTS SM)trafficandsitesupportequipment(SSE)trafficis
transmittedthroughthelocalhostCPU.
AnyEthernetframewiththewrongVLANidentifier(VLAN ID)isdiscarded.
Alltheuserdataareseparatedfromanyothertraffictype.
InternalconnectionsandservicescannotbeaccessedbyanylocalEthernetport.

Whenthefeatureisdisabled:
VLANtagisnotsupported,therearenoseparationofsensitiveandnon-sensitive
data.

Deactivating the feature


Deactivatingthefeatureisusuallynotneeded.Iftheoperatorchoosestodeactivatethe
featuremanually,itispossibletodoitusingeitherNetActorBTSSiteManager.To
disableorre-enableLTE521:SecurityforEthernetportsonFCM/FSMv2featureusing
BTSSiteManager,modifytheeNBconfigurationplan.
Allthefeature-relatedsettingsarefoundintheRadio network configurationpage.
SwitchtoRadio network configurationpageandconfiguretheActivate Ethernet
securityoptioninMRBTS-1 Propertiessection.

4.5.4 System impact


Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.
Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.
Impact on network and network element management tools
Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.
Impact on system performance and capacity
Thisfeaturehasnoimpactonsystemperformanceorcapacity.

Issue:02M DN0978033 211


Operabilityfeatures LTERL20,FeatureDescriptions

4.5.5 LTE521: Security for Ethernet ports on FCM/FSM2


management data
Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeFlexiMultiradioBTSLTECommissioning,RNWandTransmissionParametersexcel
inNOLS.
Alarms
Therearenoalarmsrelatedtothisfeature.
Measurements and counters
Therearenomeasurementsorcountersrelatedtothisfeature.
Key performance indicators
Therearenokeyperformanceindicatorsrelatedtothisfeature.
Parameters
Table88:Newparameterslistsparametersintroducedwiththisfeature.

Table88 Newparameters

Full name Abbreviated name Managed object

Activateethernetsecurity actEthernetSec MRBTS

4.5.6 Sales information


Table89 Salesinformation

BSW/ASW License control in network License control attributes


element

BSW - -

4.6 LTE492: ANR


4.6.1 LTE492: ANR
Introduction to the feature
TheLTE492:AutomaticNeighborRelation(ANR)featureisahybridSONprocessfor
ANRfinding.Duringautoconfiguration(seetheLTE720:SONLTEAutoConfiguration
feature)ormanuallytriggeredconfigurationbytheoperatorattheNetAct,theNetAct
preparesfortheseeNBsalook-uptableforresolvingtheneighboreNBX2-IPaddress
fromanewlyfoundPCIvalues.Thelook-uptablekeepsawidernumberofmostsuitable
neighborcellsbasedongeo-locationsforthiseNB.

212 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

TheNetActconsidersallLTEcells(inter-orintra-frequency)knownwithinitsscope.In
addition,theoperatorcanaddexternalLTEcellsinbordersituations.
DuringtheoperationoftheeNB,themobilitymeasurementsareactivitedforeachUE.If
theUEmeasurementreportsshowPCIvalueswithoutexistingconfiguration,theeNB
willsearchthePCIvaluesinthelook-uptable.
Ifthevalueisfound,theeNBitselfgeneratesthisconfigurationdata,whichanoperator
wouldmanuallygeneratefortheLTE724:AutomaticNeighborCellConfigurationfeature.
ThetargeteNBsupportstheLTE492:AutomaticNeighborRelation(ANR)featureas
well,andwillacceptincomingX2linksetupfromtheotherpeer.TheX2linkset-up
happensasfortheLTE724:AutomaticNeighborCellConfigurationfeature.TheLTE492:
AutomaticNeighborRelation(ANR)featureallowsstillmanualneighborconfiguration,or
evenrunningoftheLTE539:CentralANRfeature.

4.6.1.1 Benefits

Theautomateddetectionandconfigurationofunknowncells,respectivelysites,supports
theselfconfigurationoftheneighborcellinformationwithoutoperatorinvolvementand
reducedplanningefforts.
ANRsupportsalluserequipment(UE),alsotheoneswhichdoesnotsupportECGI-
resolution.
TheANRfeatureworksforIntraLTEIntrafrequencyandInterfrequencyusecases.
LTE492:AutomaticNeighborRelation(ANR)doesnotneedcoresupportfortheS1-AP
signalingprocedure"eNB/MMECONFIGURATIONTRANSFER".

4.6.1.2 Requirements

4.6.1.2.1 Software Requirements

Table90 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20
SomeoffunctionalitiesarevalidforRL50andRL60.

OMS GOMS6.0

NetAct OSS5.3CD3
OSS5.5forRL50
NetAct8EP1forRL60

4.6.1.2.2 Hardware Requirements

ThisfeaturedoesnotrequireanyadditionalHardware.

Issue:02M DN0978033 213


Operabilityfeatures LTERL20,FeatureDescriptions

4.6.1.3 LTE492: Automatic Neighbor Relation (ANR)


Figure34 LTE492:ANR
Neighbor Site
Site eNB-A
eNB-B Ue
connected

Newcell
discovered
Look-upIP@
ofneighbor CM
eNB

AddSite&Cell AddSite&Cell
parameterof X2Setup:Ipsec,SCTP,X2-AP[site&cellinfo] parameterof
eNB-A eNB-B

CM CM

NeighborCellTablesinbotheNBupdated

4.6.1.3.1 Prerequisites

Theprerequisitesareasfollows:

Geo-locations
AntennadirectionhastobeconfiguredforallLTEcellsattheNetActConfigurator
non-networkparameters.
TheexternalLTEcellcanbeconfiguredincaseofseveralNetActclusterssupporton
LTEnetwork.
Theoperatorhastoensure,thattheLTEcellblack-lists(blacklistHoL)doesnot
containthePCIsinthePCI/IPaddresstable,thatislearnedbytheLTE782:ANR
feature.
TheneighboringeNBshaveIPconnectivitytoestablishanX2link.
AlltheneighboreNBshavetheLTE492:ANRfeatureortheLTE482:ANR-UE
basedfeatureactivitedtoaccepttheincomingcalls.

4.6.1.3.2 Functional overview/details

InLTEnetworks,theUEmobilityreliesoninformationgivenbyneighborcellrelations
andneighborcellconfigurations.Anautomaticmechanismisimplementedtodiscover
andintegrateunknowncells.Itsupportsandallowstheautomatedconfigurationand
updateofneighborcellinformationwithouttheneedofanoff-lineplanningupdateofthe
neighborcellconfigurations.

214 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

TheneighborcellconfigurationviaX2isinitiatedbytheUE-measurementsofa
connectedUE.OnlytheconnectedUEreportsthismeasurementsduringmobility
procedure.
TheUEreportsalldetected/strongestcellsaboveagiventhreshold.Therefore,itmight
reportstrongcellswhosePCIiscurrentlynotyetknowntotheFlexiBTS.TheeNB
checksintheA3/A5measurementwhentherearemorePCIreported,iftheunknown
PCIistheonlytargettobeselected.Inthiscase,theFlexiBTSlooksuptheC-planeIP-
connectivityinformation(IPaddress)oftherelevantneighboreNB,hostingtheunknown
cell.TheeNBusesonlythestrongestunknownPCIforthisandonlyifthereisnoother
knownPCIthatcouldbeselectedforHOpreparation.
IftheFlexiBTSsuccessfullylooksuptheIP-connectivityinformation,theX2signalling
connectivityissetup,andanIPsectunnelthatisusedforS1trafficisalsousedforthe
X2trafficasconfigured,ifnetworkdomainsecurityisapplied.TheX2UPinterface
(X2_U)issetupduringthefirsthandovereventbetweenapairofeNBs,includingIPsec
tunneloverS1interface,ifnetworkdomainsecurityisapplied.

g Note: TheparameterslimitingofnewneighborsdefinedinANRPRLareappliedalsoto
theLTE492:ANRfeature.

g Note: TheANRsupportsIPsecstartopologyconfigurationswhereanIPsectunnelthat
isusedforS1trafficisalsousedforX2trafficasconfigured.
IPsecmeshedtopologyconfigurationsarenotsupported.

TheresolutionofPCItoIP-connectivityinformationisdonebymeansofaPCI/RF/IP
addresslookuptablestoredattheeNB,providedbyO&M-configuration(NetAct
Optimizer,NetActConfigurator).
ThePCI/RF/IPaddresslook-uptableprovidesamappingofPCIassignedtoaneighbor
cell.Thetableincludesinformationaboutrelationofthecell'sPCIidentificationata
certainRF-carriertotheC-planeIPaddressoftheFlexiBTSservingthatcell.

g Note: ThePCIvaluesofneighborcellsareconfigureduniqueforthegivencenter
frequency(RF-carrier)andthegeo-locationareaofthecells.

TheLTE492:ANRfeaturesupportsfindingoftheneighboronthesame(common)
centerfrequencyastheactualcell.Itisgeneralassumption,thatallcellsareassignedto
thesamecenterfrequency.Therefore,inthePCI/IPaddresstableallPCIvalueshave
usuallythesameRF-carrier.
Inspecialcases,forexamplePLMNborderareasorurban/ruralmultivendorborders,
theoperatormightassigncellsofoneeNBtodifferentcenterfrequencies,thenthe
PCI/IPaddresstableallowsconfigurationofpotentialneighborsforeachcenter
frequency(RF-carrier).
TheselectioninsidetheNetActisbasedonthegeo-dataandcollectsinatypicaltwo
centerfrequencynetworkthepotentialneighborcellsfromeithercenterfrequency.This
allowstheoperatortoassignthecellslaterontodifferentcenterfrequencieswithout
updateoftheeNBPCI/IPaddresstable.

Issue:02M DN0978033 215


Operabilityfeatures LTERL20,FeatureDescriptions

g Note: ItisnotrecommendedtousetheLTE492:ANRfeatureinanetworkdeployment
withthreecenterfrequenciesand/orwithhugedifferenceinthecellsizesoneach
centerfrequency,forexamplefor800and2600MHzbands,asinthosecasessome
RFcarriersmighthavelesspotentialcandidatespreparedthanrequired.

ThegenerationofthePCI/RF/IPaddresslook-uptableispartoftheAuto-connection/
Auto-configurationprocedure.
WithintroductionofthecommonobjectmodelinRL30,thefeatureisadaptedtothenew
modeling.Theneighborrelationandtheneighborcellinformationispersistentlystored.
ThisallowsS1handover,ifX2linkisforanyreasonnotrunning.Theneighborcell
relationisonlygeneratedifthePCIisreportedbyaUEconnectedtothiscell.Thecell-
specificrelationshipallowstoseetherelevantneighborcells,whilestillallknowncellsat
theeNBlevelareavailableforhandover.
ThenewneighborsfoundtheLTE492:ANRfeaturewillbecreatedasLNADJinstance
andsettheparametercPlaneIpAddrCrtl=enbControledandallneighbordata
fromtheX2linkamongthemLNADJL.phyCellId.AftereachX2linkdroponeofthe
persistentconfiguredLNADJL.phyCellIdwillbeusedtolook-uptheIPaddress
again.Thisbehaviorrequirestohaveanup-to-dateIPaddress/PCIlook-uptablein
RL30.ThePCIupdateattheneighborcellisinformedtotheneighborsconnectedvia
X2,butthePCI/IPaddresstableisnotupdated.Theoperatorcandothismanually
triggered.RefertotheLTE468:PCIManagementfeatureandself-healingofPCI
violation.
TheLTE492:ANRandtheLTE782:ANR-UEbasedfeaturescanbeactivated
concurrentlyintheeNB.InthiscaseforresolvingtheIPaddress,thelook-uptablehas
precedencebeforetheMMElook-up.IncaseofX2linkdropthere-connectionoftheX2
linkforenbControledIPaddresswillberesolvedviathelook-uptablefirst,ifnosuitable
PCIvalueisfound,thentheMMEprocedureisapplied.DependentonPCIorIPaddress
changes,itispossible,thatadifferenteNBisfinallyselectedasneighbor,orbefore
establishedX2linkcannotberesolved.AworkaroundistosettheIPaddressto
oamControled,iftheIPaddressisstillthesame,seeiftheeNBsetsuptheX2link
correctly,andthenchangetoenbControledagain.ThiscanhelpupdatingthePCIvalues
inLNADJLsothatthereisavalidresolutionnexttime.

4.6.1.3.2.1 X2 link management

TheeNBsupportstwotypesofX2links:oamControlledX2links(thatisX2linkswhich
areprovidedandcontrolledbyoperator)andenbControlledX2links(thatisX2links
whichtheeNBlearnedviaANRprocedures,respectivelywhichareundercontrolof
ANR).ThetypeoftheX2linkisprovidedintheassociatedLNADJobjectinstance.
oamControlled X2 links
TheoamControlledX2linkshavethefollowingbasicproperties:

TheIP-addresstobeusedfortheestablishmentoftheoamControlledX2linkis
providedbytheoperatorintheLNADJobjectinstance.Itistheresponsibilityofthe
operatortocaterforcorrectconfigurationoftheIP-addressoftheoamControlledX2
link.
TheeNBautomaticallytriggerstheestablishmentoftheoamControlledX2link
configuredbytheoperator(forexampleifstartupoftheeNBoccurs).Nofurther
conditionsarecheckedbytheeNB.

216 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

EstablishmentoftheoamControlledX2linkhaspriorityoverestablishmentofthe
enbControlledX2link.
IftheestablishmentoftheoamControlledX2linkfails,analarmisraisedbytheeNB.

Toavoidinconsistenciesregardingestablishment/re-establishmentbehavior,itis
recommendedtoconfigurethesameX2linktypeatbothsidesoftheX2link(thatisif
theX2linkisconfiguredasoamControlledineNB,thenitshouldbealsoconfiguredas
oamControlledinthepeereNB).
enbControlled X2 links
TheenbControlledX2linkshavethefollowingbasicproperties:

AllX2linkswhichareautomaticallyestablishedbytheANRfunctionsarelabelledas
theenbControlledX2links.ActivationofatleastoneoftheANRfeatures(either
LTE492:AutomaticNeighborRelation(ANR)orLTE782:ANRFullyUEbased)isa
pre-conditionfortheestablishmentoftheenbControlledX2link.
TheANRfunctionsoftheeNBtriggertheautomaticestablishmentofthe
enbControlledX2link,iftheeNBdetectsthathandoverprocedurestocellsofthe
neighboreNBhavetobeperformed.
TheIP-addressneededforX2linkestablishmentisautomaticallydeterminedbythe
eNB(forIP-addressretrievalmechanisms,seealsoLTE782:ANRFullyUEbasedin
AutomaticNeighborRelation(ANR)).
EstablishmentoftheenbControlledX2linktosomeneighboreNBmightbeforbidden
bytheoperatorviaX2linkblacklisting.

Regardingre-establishmentofenbControlledX2links,theeNBbehavesasdescribedin
OutgoingenbControlledX2link(establishmenttriggeredbytheeNB)andIncoming
enbControlledX2link(establishmenttriggeredbyneighboreNB).

g Note: InRL50,theeNBestablishesanenbControlledX2linkonlyifatleastoneofthe
featuresLTE782:ANRFullyUEbasedorLTE492:ANRisactivated(thatis,eitherthe
actUeBasedAnrIntraFreqLteoranrOmExtEnableparameterissettotrue).
FromRL60on,handlingofenbControlledX2linksisabasicfunctionalityandisnot
guardedbyanyfeatureflag.SettingthemaxNumX2LinksInandthe
maxNumX2LinksOutparameters'valuesto0istheonlywaytodisable
accepting/establishingofenbControlledX2linksfromRL60on.
Outgoing enbControlled X2 link (establishment triggered by the eNB)
TheeNBwilltrigger(re-)establishmentoftheenbControlledX2linkifallofthefollowing
conditionsaremet:

TheeNBhasseenthatcellsoftheneighboreNBarenecessaryastargetsfor
handover(inthiscaseLNREL/LNADJLobjectpairsareavailableassociatedwiththe
neighboreNB).
TheoperatorhasnotforbiddenestablishmentoftheenbControlledX2linkviaX2link
blacklisting(seetheNewparameterstableintheLTE782:ANRFullyUEbased
feature).
ThenumberofX2linksisstillsmallerthanthemaxNumX2LinksOutparameter.
ThemaximumnumberofX2links,whichcanbeestablishedbytheeNB,isnot
reachedyet.
Incoming enbControlled X2 link (establishment triggered by neighbor eNB)
TheeNBwillacceptestablishmentrequestoftheenbControlledX2fromtheneighbor
eNBifallofthefollowingconditionsaremet:

Issue:02M DN0978033 217


Operabilityfeatures LTERL20,FeatureDescriptions

TheoperatorhasnotforbiddenestablishmentoftheenbControlledX2linkviaX2link
blacklisting.
ThenumberofX2linksisstillsmallerthanthemaxNumX2LinksInparameter.
ThemaximumnumberofX2linkswhichcanbeestablishedbytheeNBisnot
reachedyet.

g Note: TheeNBwillattempttoretrieveIP-addressviaS1interface,iftheLTE492:ANR
featureisdeactivated,oriftheIP-addresscannotbefoundinthePCI/IPaddress
mappingtable.

g Note: ItisrecommendedtorunwholenetworkorsubclustersincommonANRmode
(ANRONorOFF).

g Note: Inordertoavoidconflicts,PCIplanninghastoensurethatforagivencarrier,
eachneighborcelllearnedbyeNBusesadifferentPCIvalue.(Thisincludesall
neighborcellswhichmightbelearnedbyeNBviaX2.)

4.6.1.3.2.2 NetAct Optimizer: Neighbor evaluation procedure

Triggeredduringtheauto-configurationprocedureforanewlydeployedeNB,theNetAct
Optimizercalculatesthedistancetoothercellsandcreatesalistoffoundneighborcell
relations.Then,theeNBselectstheclosestcellsandaddsthemalltothelist.Theresult
isgiventotheNetActConfiguratortocompletetheconfigurationplanfileforthenew
eNB.Thesearenotfoundneighborcellrelationsbutsimplyalargerlistof
geographicallyclosestneighborsitesasalook-uptablefortheeNB.Withtheintention,
theeNBcanestablishanX2link,onlytothose,thatareactuallyvisibleandreportedby
theconnectedUEs.Therefore,thelook-uptablehasmanymoreentriesthantheX2
linkscanestablishinasinglecenterfrequencydeployment.Inatwo-centerfrequency
deployment,and/oreveninonewithunequalcellsizes,itisstillsufficientwiththecurrent
limitof200entries.

TheNetActsupportsoperator'spreferencestocontrolthecontentofthelook-uptablein
thefollowingway:

searchthedistancetobelimitedsothatthefarawaycellsarenotconsidered;
otherwise,anup-to-100-kilometerdistanceisused
limitofPCIperfrequencycarriersplitforconfiguresLNCEL-EARFCNoftheeNBand
unknownones

TheNetActdropsallPCIvaluesthatwouldduplicatePCIssothatonlytheclosestPCIis
keptonthelist.

g Note: FromRL70on,alltheheterogeneousnetwork(HetNet)-relatedfunctionsare
perfomedintheiSONManager,notintheNetActOptimizer.Formoreinformationon
HetNetfeatures,see:
theLTE1821:NeighborDetectionOptimizationforHetNetfeature
theLTE1822:PCIAssignmentOptimizationforHetNetfeature
theLTE1823:NeighborPrioritizationOptimizationforHetNetfeature

External LTE cell support for the LTE492: ANR in NetAct

218 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

TheNetActOptimizersANRalgorithmfortheLTE492:AutomaticNeighborRelation
(ANR)featureconsiderstheexternalLTEobjectsascandidatesforneighborobjects.If
anexternaleNBorexternalcellsatisfiestheconditionsoftheANRalgorithm,the
Optimizeraddstheexternalcelltothemappingtable(PCI,frequency,IPaddress)ofa
correspondingeNB.
TheANRfunctionineNBdetectsnewneighborcellsandtheeNBcreatescorresponding
LNADJandLNADJLobjects.TheNetActcreatessuitableexternalLTEobjectsforthose.
TheNetActsynchronizestheparameterupdatesfromtheLNADJandLNADJLobjects
forwardtheexternalcellobjects.
Thegeo-locationdataneedstobemaintainedbytheoperator.TheLTE492:ANRfeature
ignoresexternalobjectsiftheydonothavegeo-locationinformationassigned.This
behaviorisdifferenttotheown-managedcells,formoreinformationondistributessites
seetheLTE1045:FullSONSupportforDistributedSitesfeature.

4.6.1.3.2.3 NetAct Configurator: automated neighbor site IP connectivity configuration


completion

AssoonastheNetActOptimizercompletestheneighborevaluation,ithandsoverthe
resulttotheNetActConfiguratorthatstartslookingintotheconfigurationfilesofthe
neighboreNB.
ForeachneweNB,theConfiguratoropenstheconfigurationplanfileandcopiesfrom
theneighboreNBthePCIs,RFs,andIPaddressconnectivityinformationrelevantforX2
establismenttogeneratethelook-uptable.
TheoperatorcanmanuallytriggerforasetofoperationaleNBtheConfigurator
generationthelook-uptablebasedonthecurrentcelldeploymentforeacheNB.
Theupdatedconfigurationplanfile(includingthePCI/RF/IPaddresslook-uptable)is
nowreadytobedownloadedautomaticallyaspartoftheauto-configurationprocess.
Afterthenewneighborsitesaresuccessfullyincludedintothelocalconfigurationdata,
theFlexiBTSsendsaconfigurationchangenotificationtotheNetworkManagement
System(NetAct)tosynchronizethelocalconfigurationchanges.
Assoonasaself-learnedX2connectionhasbeensuccessfullyestablished,itsIP
addressbecomesapartofthenormalconfigurationdataandtherebythisX2connection
becomespersistent(thatisnotneededtobedetectedbytheUEmeasurements
anymore;BTSrestartissafe).
IfanoperatorhasnotlicensedordoesnotwanttoutilizetheANR-feature,theoperator
isstillabletopre-configureX2-connectivityinformation(IP-addresses)byO&M-
configuration(planfile).TheotherpossibilityisthecentralizedSONfunctions-the
LTE539:CentralANRfeature.

Issue:02M DN0978033 219


Operabilityfeatures LTERL20,FeatureDescriptions

g Note: Operator hint


TheLTE492:ANRfeatureworksincoverage-limitednetworkdeploymentsverysimilar
astheLTE782:ANR-UEbasedfeatureinpassiveANRmode.Inadditionitisrequired
tohaveup-to-datePCI/IPaddresstablesinalleNBs,foranychangeofaPCIvalue,
thisisautomaticallydonebytheNetAct.ItisproposedtoswitchofftheLTE492:ANR
featurewhentheLTE782:ANR-UEbasedfeatureisactivated,orusePCI/IPaddress
tablesratherforinter-frequencyHOsupport.
Incapacity-limitednetworkdeploymentstheLTE492:ANRandthe
LTE782:ANR-UEbasedfeaturesinpassiveANRmodeworkquitesimilaraswell.
Similarlytheoperatorwatchestheneighborrelation(NR)fromaperformancepointof
view.DuringtheupgradetheoperatorshouldhavechangedalltheexistingIP
addressestorunintheeNB-controlledmodebysettingtheLNADJ-parameter
cPlaneIpAddrCtrl = enbControlled (1).

4.6.1.3.2.4 Use cases

Theusecasesareasfollows:

IntegrationanddeploymentofaneweNBwithinaninstalledbaseofothereNBs
TheestablishmentofanX2connectionandthecreationoftheneighborrelationsis
alwaystriggeredbythenewlydeployedeNB,thathasthelatestPCI/RF/IPaddress
look-uptableavailablethatisrelevantforitsenvironment.Theinstalledbaseofthe
eNBshastoacceptanX2-setuprequest,withprecedingSCTPconnection
establishmentandaprecedingIPsectunnelestablishmentifnetworkdomain
securityisapplied.
ManuallytriggeredneighborsiteevaluationandIP/RF/PCIupdate
Theoperatorcanstarttheneighborsiteevaluationandconfigurationplanfile
completionmanuallyorwithinascriptforselectedeNBs.Thishelpstosolvepossible
inconsistenciesif,forexample,somethingwentwrongduringautoconfigurationorto
facilitatethemanualplanfileconfiguration.Themanualplanningcompletionresults
inanupdatedconfigurationplanfilebutnotinanautomateddownload.Thisneeds
tobeinitiatedseparately.

4.6.1.4 System Impacts

4.6.1.4.1 Interdependencies between Features

Table91 Interdependenciesbetweenfeatures
LTE720 SONLTEBTSAutoConfiguration

LTE55 Inter-frequencyhandover(optional)
ANRmechanismsofLTE492:ANRmightbeusedtoautomaticallylearn
LTEinter-frequencyneighborcells.

LTE570 PeriodicUEMeasurements
TheRSCmeasurementdoesnotfeedinnewneighbors,asonlytargetsfor
HOareaddedasneighborrelations.

220 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

Table91 Interdependenciesbetweenfeatures(Cont.)
LTE492 Automatedneighborrelation(ANR)LTE492:ANRrequiresX2connectivityto
learntheneighborcellconfiguration.Thelearnedconfigurationdataare
storedpersistentinLNADJandLNADJL.ThissupportsincaseofX2
outagemobilityviaS1HO.

LTE468 PCImanagementThePCI/IPaddresstableofneighboreNBsareupdated
incaseofPCIchangesdoneatNetActwithaconfigurationplan.

LTE782 ANRUEbasedLTE782:ANRUEbasedandLTE492:ANRareworking
similar,thereforebothwillsupporttheresolutionofunknownPCIvaluesand
createtheLNRELinstances,incaseofanHOattempt,withequaldefault
settings(HOallowed,NRautomatic).Ifbothfeaturesareactivated,then
bothfeaturesworkincompetitivemode.ThePCIresolutionviaLTE492:
ANRmightbefaster,andwillset-uptheX2connection.

LTE539 CentralANR
LTE539:CentralANRinauto-configurationconfiguresonlythenewinstalled
eNB.ThiseNBwilltrytoestablishaX2linktoalltheotherpeersthatshall
becomeneighboreNBs.TheoperatorshalltemporaryenableLTE782:ANR
UEbasedorLTE492:ANRatallneighboreNBstoletthemacceptthe
incomingX2link.LTE539:CentralANRinauto-configurationcanrun
concurrentlywithoperationaleNBsthathaveLTE782:ANRUEbasedor
LTE492:ANRenabled.
LTE539:CentralANR,triggeredmanuallyforasetofoperationaleNBs,
requires,thatthoseeNBshavefeatureLTE782:ANRUEbasedand
LTE492:ANRdisabled,asallowingincomingX2linkswillendupina
commissioningalarmandtheplanfilewillbeabort.Theoperatorshall
disableLTE782:ANRUEbased(LNBTS-actUeBasedAnrIntraFreqLte==
False)andLTE492:ANR(LNBTS-anrOmExtEnable==False)manuallyas
NetActcannotdothisautomatically.

Issue:02M DN0978033 221


Operabilityfeatures LTERL20,FeatureDescriptions

g Note: Iftheoperatorconfiguresmanuallytheinter-frequencyLTEmeasurements,and
NetActhastheconfigurationdataforbothLTEfrequencies,NetActgeneratesa
PCI/RF/IPaddresslookuptableforbothfrequencies.ThentheeNBfindsinter-
frequencyneighborsautomatically.ThatmeansLTE492:ANRateNBisnotrestrictedto
intra-frequencywithrespecttotheservingcell,whentheoperatorhasconfiguredin
additionthemeasurementsaccordingtothefeatureLTE55:Inter-frequencyhandover.
IftheeNBdecidesforanUEonanHOattempttoaninter-frequencyneighborcell,then
acorrespondingLNRELinstanceiscreatedsimilarasforintra-frequencycases.
ThisprocedurecanbeappliedforfurtherLTEcarrierfrequenciesaswell.
Anyinter-frequencyUEmeasurementsareaburdenforalltheUEsandreducetheir
throughput.
Ontheotherhand,ifthereareRLFsbecauseofmissingcoverage,thismightbea
triggerfortheoperatortoscanforneighborsonotherLTEcarrierfrequencies.Thenthe
operatorcandecidetoset-up(a)newLNHOIFinstance(s).
EspeciallyformultipleLTEcarrierfrequenciestheindividualLNHOIFsettingofthe
measurementthresholdsandbetter/coveragecellsettingsarecrucialandrequire
furtherconsiderationoftheoperatorforboththeLTE492:ANRlearningandtheregular
HOset-up.
Theoperatorshouldcheckforeachcell,iftheadditionalinter-frequencymeasurements
resultedinanyfindingsofneighborcellsonthecertainLTEcarrierfrequency.Itis
recommendedtodeleteuselessUEmeasurementrequirementsbydeletionofthe
correspondingLNHOIFinstance.Long-termanalysisoftheHOperformancetowards
thecertainLTEfrequencycarriersmightshow,thatnooronlyafewinter-frequencyHO
tothiscertaincarrierapplyandadditionalANRsearchingandUEmeasurementscan
beavoided.

4.6.1.5 Sales Information

Table92 Salesinformation

BSW/ASW License control in network element License control attributes

ASW SWAssetMonitoring -

4.6.1.6 User Interface

4.6.1.6.1 Parameters

Table93 ParametersforLTE492:AutomaticNeighborRelation

Short name Description Range/step Default

anrOmExtEnable Optionalfeatureflagfor enabled/disabled enabled


featureLTE492ANRsupport
forLTEwithO&Mextension

222 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

Table93 ParametersforLTE492:AutomaticNeighborRelation(Cont.)

Short name Description Range/step Default

pciIpAdrMap Thistabledefinesthe 0..maxEARFCN 0


mappingfrom{dlEarfcn,pci}
to{ipAdr}
Parametersincludedinthis
structure:dlEarfcn,
enbId,ipAdr,mcc,mnc,
mncLength,pci

dlEarfcn DownlinkEARFCNofthe 0..65535,step1 -


neighborcell,includedinthe
pciIpAdrMap

pci PhysicalCellIdentityofthe 0...503 0


neighborcell,includedinthe
pciIpAdrMap

ipAdr C-planeIPaddressofeNB 1.2.3.4upto -


whichisservingPhysical
123.456.789.abc
Cell,includedinthe
pciIpAdrMap

mcc MobileCountryCode 0..999,step1 -


includedinthePrimary
PLMNIDoftheneighbor
eNBservingthecell
providedinthePCI-IPMap
entry

mnc MobileNetworkCode 0..999,step1 -


includedinthePrimary
PLMNIDoftheneighbor
eNBservingthecell
providedinthePCI-IPMap
entry

enbId UniquemacroeNBIDofthe 0..1048575,step1 -


neighboreNBwithinthe
PrimaryPLMNservingthe
neighborcellindicatedinthe
PCI-IPMapentry

mncLength LengthofMobileNetwork 2..3,step1 -


CodeincludedinthePrimary
PLMNIDoftheneighbor
eNBservingthecell
providedinthePCI-IPMap
entry

maxNumX2LinksIn IfthenumberofeNB- 0..256,step1 64


controlledX2-linksreaches
themaxNumX2LinksIn,

Issue:02M DN0978033 223


Operabilityfeatures LTERL20,FeatureDescriptions

Table93 ParametersforLTE492:AutomaticNeighborRelation(Cont.)

Short name Description Range/step Default

thentheeNBstops
acceptingestablishment
requestsforneweNB-
controlledX2-linksfrom
neighboureNBs

maxNumX2LinksOu IfthenumberofeNB- 0..256,step1 60


t controlledX2-linksreaches
themaxNumX2LinksOut,
thentheeNBstopsthe
automaticestablishmentof
neweNB-controlledX2-links

g Note: TheANRcontrolparametersarenewlymodeled,asdefinedinthe
LTE1383:Cell-specificNeighborRelation/PCIHandlingfeature.Formoredetails,see
LTE1383:Cell-specificNeighborRelation/PCIHandlingin
AutomaticNeighborRelation(ANR).

g Note: Operator hint


TheparameterLNCEL-threshold1andANRPRL-anrThresRSRPNbCellshall
besetaccordingtothedeploymentofthecell.
Whilethreshold1(s-measure)definestheRSRPthresholdtostartneighbor
measurements,anrThresRSRPNbCellgivesaminimumpowerleveltotriggerthe
CGIresolutionforanewneighborcell.
Inruralcoveragelimiteddeploymentsthosevaluesaresettolowervalues,forexample
70/40(threshold1:-70dBm/-100dBm).
Inurbancapacitylimiteddeploymentsthosevaluesaresettohighervalues,e.g.90/60
(threshold1:-50dBm/-80dBm).

g Note: Operator hint


Overallcarriersatotalof200PCIentriesmightbeincludedinpciIPAdrMap.PCI
planninghastoensurethatthislimitisnotexceededbytheneighbourhoodoftheeNB.
Itisrecommendedfortheoperatortoconfigureabout50/100PCIvaluespercarrierfor
mostly3*12-sectorized/distributedeNBsites.Theoperatormustrunthe
LTE468PCIManagementfeature.

4.6.1.6.2 Alarms

Therearenoalarmsrelatedtothisfeature.

4.6.1.6.3 Measurements and Counters

Therearenomeasurementsandcountersrelatedtothisfeature.

224 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

4.6.1.7 Activating and Configuring the Feature

NetActOptimizerisrequiredfortheLTE492:ANRfeatureaspre-requisite,asthisisa
hybridSONfunction(eNBandNetAct).

ThisfeatureisactivatediftheO&MparameteranrOmExtEnableissetto
enabled.Thefeatureflagisthesettingforlicence.
ThisfeatureisdeactivatediftheO&MparameteranrOmExtEnableissetto
disabled.

4.7 LTE550: Radio Parameter Online Changeable


Introduction to the feature
Withthisfeature,parameterchangescanbemanagedwhentheFlexiMultiradioBTSis
operating.Celllockingandunlockingisnotneeded.Anetworkelement(NE)restartis
avoided.

4.7.1 Benefits
End-user benefits
Thisfeaturebenefitstheend-userasfollows:

Enduserexperienceisimprovedwithprovidingconstantlyhighserviceavailability.
Operator benefits
Thisfeaturebenefitstheoperatorasfollows:

Thenumberofstepsforparametermodificationisreduced,allowingmoreefficient
changemanagement.

4.7.2 Requirements
Software requirements
Table94:Softwarerequirementsliststhesoftwarerequiredforthisfeature.

Table94 Softwarerequirements

System eNB NetAct MME SAE GW UE


release

Release RL20 LBTS2.0 OSS6.0 - - -

Hardware requirements
Thisfeaturerequiresnoneworadditionalhardware.

4.7.3 System impact


Interdependencies between features

Issue:02M DN0978033 225


Operabilityfeatures LTERL20,FeatureDescriptions

Therearenointerdependenciesbetweenthisandanyotherfeature.
Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.
Impact on MML commands
TherearenoMMLcommandsrelatedtothisfeature.
Impact on network and network element management tools
Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.
Impact on system performance and capacity
Thisfeaturehasnoimpactonsystemperformanceorcapacity.

4.7.4 LTE550: Radio Parameter Online Changeable management


data
Formoreinformationonparametersandparametermodificationtype,seeLTERNW
parameters,TransmissionparametersandFlexiMultiradioBTSLTEcommissioning
parameters.
Alarms
Therearenoalarmsrelatedtothisfeature.
Measurements and counters
Therearenomeasurementsorcountersrelatedtothisfeature.
Key performance indicators
Therearenokeyperformanceindicatorsrelatedtothisfeature.
Parameters
Therearenoparametersrelatedtothisfeature.

4.7.5 Sales information


Table95 Salesinformation

BSW/ASW License control in network License control attributes


element

BSW - -

226 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

4.8 LTE559: SW Monitoring Module for LTE


4.8.1 Introduction to the feature
ThisfeatureenablesmonitoringofConfigurationManagement(CM)basedsoftware
features.
Itisintendedforautomatedmonitoringofsoftwareproductusage.

4.8.2 Benefits

4.8.2.1 End user benefits

Thisfeaturedoesnotaffecttheend-userexperience.

4.8.2.2 Operator benefits

Thisfeaturebenefitstheoperatorasfollows:

itenablessimplesupervisionoffeaturesusedinanetwork
itoffersfeatureusagemonitoringwhichcanaccompanywithFeatureManagement
orworkindependently
itbringsintheeasyexecutionofmonitoring-basedcontracts
itpreventsnetworkoutageduetomissinglicenses
iteliminatestheneedforunnecessarypre-investmentscomparedtolicense
managementmethod
itoffersafastsoftwareactivationmethodwithinthenetworkby-passingthepre-
activationprocurementprocess.
itintroducesactivationperformedbytheoperator(withoutbeinginvolved)

4.8.3 Requirements

4.8.3.1 Software requirements

Table96 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB

MME

SAEGW

UE 3GPPrelease8

Issue:02M DN0978033 227


Operabilityfeatures LTERL20,FeatureDescriptions

Table96 Softwarerequirementsfordifferentnetworkelements(Cont.)

Network element Required software release

NetAct OSS5.3CD1

4.8.3.2 Hardware requirements

ThisfeaturedoesnotrequireanyadditionalHardware.

4.8.4 Functional description


Monitoring-basedAssetProtectionframeworkmanagesconfigurationdatatoidentifythe
usageofLTEapplicationsSWinoperatorsnetworks.Theconfigurationdataconsistsof
ConfigurationManagement(CM)parameters.ThedataisretrievedfromtheCM
database.
Datacollectionandreportgenerationcanbecustomized.Reportingofsinglefeatures
canbeenabledordisableddependingonthecustomercontract.

4.8.4.1 Functional overview/details

Monitoring-basedAssetProtectionframeworkusesexistingNetActdata.
TheSWAMClientcollectsandprocessestheconfigurationdatabasedoncustomer-
specificsettings.Itgeneratesareportonthefeatureusageandforwardstheformatted
monitoringdatatothecustomerandCustomerTeamviaencryptedemail.The
encryptedemailcanbereadandvalidatedbyCustomerandCustomerTeamonly.The
reportonthefeatureusagewillbeusedtogenerateaninvoice.

Figure35 FeaturemonitoringforLTE

CustomerNetwork

Customer

Encrypted
Email

SWAM Client

Nokia NetAct

CustomerTeam

TheNetActSWAMClientconsistsoftwomaincomponents

thecommonClientFramework

228 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

theProductspecificMonitoringModule

Monitoring-basedAssetProtectionFrameworkisbasedonSWAMClient2.Itsupports
theLTEMonitoringModuleMRL20.
ThemoduleMRL20isdesignedtocoveralleNB-basedconfigurationbasedApplications
SWFeature(ASWfeatures)whichareavailableintheLTESystemReleaseRL20.

4.8.5 System impacts

4.8.5.1 Interdependencies between features

Therearenointerdepenciesbetweenfeatures.

4.8.5.2 Impacts on interfaces

Thisfeaturehasnoimpactoninterfaces.

4.8.5.3 Impacts on network and network element management tools

Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

4.8.5.4 Impacts on system performance and capacity

Thisfeaturehasnoimpactonsystemperformanceorcapacity.

4.8.6 Sales information


Thisfeatureisabasicsoftwarefeature.

4.8.7 User interface

4.8.7.1 Parameters

Therearenoparametersrelatedtothisfeature.

4.8.8 Activating and configuring the feature


Thisfeaturedoesnotrequireactivation.

4.9 LTE667: LTE User Event Log Management


4.9.1 Introduction to the feature
ThisfeatureisusedforauditinguseractionsintheevolvednodeB(eNB)andtheiOMS.
Theconfigurationchangesaremonitored.Thissupportspossiblecorrectiveactions.

Issue:02M DN0978033 229


Operabilityfeatures LTERL20,FeatureDescriptions

4.9.2 Benefits
Thecentralizeduserauditincreasesthesystemsecurity.Theoperatorcansupervise
security-relateduseractions,thatis:

dateandtimeoftheuseraction
theuseractionitself

4.9.3 Requirements
Software requirements
Table97 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

UE

OMS OMS0.5

NetAct OSS5.3CD1

Hardware requirements
Thisfeaturedoesnotrequireanyneworadditionalhardware.

4.9 Functional description for LTE User Event Log


Management
4.9.4 System impact
FullfunctionalityofLTE667LTEUserEventLogManagementfeatureisonlyobtainedif
LTE666:LTEUserAccountManagementfeatureisactivated.

4.9.5 Sales information


TheLTE667:LTEUserEventLogManagementfeatureisNetActapplicationsoftware.
ThelicensecontrolisinNetAct.TheNetActAuditTrailtoolhandlestheusereventlog
data.

4.9.6 LTE667: LTE User Event Log Management management


data
Alarms

230 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

Therearenoalarmsrelatedtothisfeature.
Measurements and counters
Therearenomeasurementsorcountersrelatedtothisfeature.
Key performance indicators
Therearenokeyperformanceindicatorsrelatedtothisfeature.
Parameters
Therearenoparametersrelatedtothisfeature.

4.9.7 Activating the feature


Thisfeaturedoesnotrequireactivation.AuditTrailisNetActapplicationsoftware.

4.10 LTE796: iOMS Connectivity Increase


4.10.1 Introduction to the Feature
Withthisfeature,iOMSactiveconnectioncapabilityisincreasedupto2000eNBs.
ImprovediOMSarchitecturedoesnothaveSWbasedlimitationsforthenumberofBTSs
connectedtoiOMS.OnlyHWcomputingcapabilitylimitsthenumberofnetwork
elementsconnectedtotheiOMS.

4.10.2 Benefits
BetterscalabilitymeansmorebenefitfromiOMSpowerfulHW.Also,itbringsCAPEX
andOPEXsavingsduetoadecreasednumberofmanagediOMSelements.

4.10.3 Requirements

4.10.3.1 Software Requirements

Table98:Softwarerequirementsliststhesoftwarerequiredforthisfeature.

Table98 Softwarerequirements

System Release eNB NetAct MME SAE GW

Release RL20 LBTS2.0 OSS5.3CD1 - -

4.10.4 Functional Description


iOMSproxyconnectivitytowardsnetworkelementsisincreased.

4.10.5 System Impacts

Issue:02M DN0978033 231


Operabilityfeatures LTERL20,FeatureDescriptions

4.10.5.1 Interdependencies between Features

Thisfeaturehasnorelatedorinterworkingfeatures.

4.10.6 Sales Information


Product Structure Class:ASWNetAct
License Control in Network Element:NetAct

4.11 LTE830: LTE Automatic Lock


4.11.1 Introduction to the Feature
Withthisfeature,celllockingandunlockingisperformedautomaticallydependingonthe
parametertype.Theautomaticlockingisusedwithparameterswhichmodificationtype
isdefinedas"Requiresobjectlocking"or"Cellshutdownneeded".Applyingchangesfor
suchparametersrequireslockingthecorrespondingobjectorrestartingtheBTS.The
operatorcanchooseimmediatelockingorgracefulshutdownprocedure.

4.11.2 Benefits
Theconfigurationmanagementissimplified.Timeneededformodifyingparametersthat
requirecelllockingisdecreasedbecauselockingandunlockingisdoneautomatically.
Onlyparametermodificationisdonebytheoperatormanually.Downloadandactivation
ofseparatelockingplanfiles(beforeparametermodifications)isnotneeded.

4.11.3 Requirements

4.11.3.1 Software Requirements

Table99:Softwarerequirementsliststhesoftwarerequiredforthisfeature.

Table99 Softwarerequirements

System Release eNB NetAct MME SAE GW

Release RL20 LBTS2.0 OSS5.3CD1 - -

4.11.4 Functional Description


Theoperatorcanapplythegracefulcellshutdownofhavinglessserviceimpactorthe
hardshutdownresultinginimmediatecelllocking.Forparameterchangesofthecell
objectswithgracefulcellshutdownenabled,thetrafficofthecellistransferredtoother
cellsbeforethecellserviceisterminated.Ifseveralparametersarechangedforthe
sameobject,alltheseparametersarechangedinthesamelocking/unlockingprocedure.
Theautomaticexecutionofthelocking/unlockingorshutdownisdoneintheFlexi
MultiradioBTS.Celllockingresultsinanimmediateshutdownoftheimpactedcell

232 DN0978033 Issue:02M


LTERL20,FeatureDescriptions Operabilityfeatures

object.Theactiveconnectionsinthatcellarelost.Oncetheparameterchangesare
done,thecellisrestoredtothestatebeforethemodification.eNBrecognizeswhich
parameterchangesrequirerestartingtheBTS,andwhichrequireonlyobjectlockingand
unlocking.Ifobjectlockingisneeded,itisautomaticallyrequestedbyeNB.Parameter
valuesarethenmodifiedandunlockingofobjectistriggeredautomaticallybytheeNB.
OperatortakesautomaticlockinginusebysettingtheappropriateeNBglobalparameter
EnableAutomaticLockingtoenabled.Aftertheparameterchangesaredone,thecellis
restoredtothestatebeforethemodification.TheoperatorcanselectaBTSforwhichthe
featureisapplied.Thisfeatureworkswithplanbasedactivation.Oncethefeatureis
enabled,itappliesforallsubsequentlyactivateddeltaplanfiles.Featureenablingand
parametermodificationcanbedonewithinthesamedeltaplanfile,i.e.thefeature
configurationalreadyappliesforparametersinthesameplanfile.Ifadeltaplanmodifies
aparameterwhichrequires"BTSrestart",therestartisperformedindependentfrom
enablingordisablingAutomaticlocking.
Delta plan activation with automatic locking (immediate locking)
Pre-conditions

eNBisconfiguredandinservice
NetActandOMSareinservice
TheDCNconnectionbetweentheNetActandeNBviaOMSisestablished
TheeNBparameterEnableAutomaticLockingissettoenabled
TheeNBparameterenableGrflShdnissettodisabled

Deltaplanfilecontainsparametermodificationswhichrequireobjectlocking/cell
shutdownbutnoparameterswhichrequireaBTSrestart.Theoperatordownloadsand
activatesthedeltaplanfile.TheeNBevaluatesandprocessestheplanfile.It
automaticallylocksallaffectedobjectsimmediatelyandsendsStateChangeEvent
ReportstoNetActandBTSSiteManagerwithnewOperationalStatevalue
Disabled.NotethatS1Resetisperformedduringcelldeactivation.Thisaffectsall
cellsoftheeNB.eNBmodifiesvaluesofaffectedparametersandsendsConfiguration
ChangeNotifications(CCN)toNetActandBTSSiteManager.eNBautomaticallyunlocks
allaffectedobjectsandsendsStateChangeEventReportstoNetActandBTSSite
ManagerwithnewOperationalStatevalueenabled,unlesstheobjectshavebeen
alreadylocked.Thisensuresthatobjectswhichhavebeenintentionallysettolockedby
theoperatorremaininlockedstate.
Theparametervalueshavebeenmodifiedandallaffectedobjectsareinunlockedstate
again(exceptforobjectsintentionallysettolockedbytheoperator).
Delta Plan activation with automatic locking disabled
Pre-conditions

eNBisconfiguredandinservice
NetActandOMSareinservice
TheDCNconnectionbetweentheNetActandeNBviaOMSisestablished
TheeNBparameterEnableAutomaticLockingissettodisabled

Deltaplanfilecontainsparametermodificationswhichrequireobjectlocking/cell
shutdown.Theplanfilecanalsocontainonlinemodifiableparametersbutdoesnot
containparameterswhichrequireBTSrestart.Operatordownloadsandactivatesthe
deltaplanfile.enBevaluatesandrejectsthedeltaplanfileactivationbecauseservice
affectingobjectlocking/cellshutdownisrequired.

Issue:02M DN0978033 233


Operabilityfeatures LTERL20,FeatureDescriptions

TheeNBconfigurationisunchanged.
Delta Plan activation autolock enabled (parameter requires BTS restart)
Pre-conditions

eNBisconfiguredandinservice
NetActandOMSareinservice
TheDCNconnectionbetweentheNetActandeNBviaOMSisestablished.

DeltaplanfilecontainsparametermodificationswhichrequireBTSrestart.Theplanfile
canalsocontainonlinemodifiableparametersand/orparameterswhichrequireobject
locking/cellshutdown.Operatordownloadsandactivatesthedeltaplanfile.eNB
evaluatesthedeltaplanfileandperformsaBTSrestart.Serviceiscompletely
unavailableduringthattime.Aftercompletionoftherestartallmodifiedvaluesare
applied.NotethatBTSrestartisperformedindependentofthecurrentvalueofthe
parameterEnableAutomaticLocking.
AllparametervaluesaremodifiedandtheeNBisinserviceagain.

4.11.5 Parameters
Table100:ParametersfortheLTE830:LTEAutomaticLockfeatureshowsthe
parametersimplementedfortheLTE830:LTEAutomaticLockfeature.

Table100 ParametersfortheLTE830:LTEAutomaticLockfeature

Name Short name Object Description Range / Step Default


value

EnableAutomatic enableAutoLock LNBTS Theparameterenablesthefeature Disabled(0), Enabled


Locking "Automaticlocking"Ifthefeatureis Enabled(1)
enabled,objectsareautomatically
lockedandunlockedbyeNBifa
parameterwhichrequiresobject
lockingismodifiedviadeltaplanfile.If
gracefulshutdownisenabledby
settingenableGrflShdntoenabled,
theserviceisimpactedlessbut
slowergracefulcellshutdown
procedureisperformedinsteadof
immediatelocking.

EnableGracefulCell enableGrflShdn LNBTS Theparameterenablesthefeature Disabled(0), Enabled


Shutdown GracefulCellShutdown.Ifthefeature Enabled(1)
isactivatedanadditional
administrativestate"shuttingdown"is
supported.Itallowsalessservice
impactingcelllocking.

234 DN0978033 Issue:02M


LTERL20,FeatureDescriptions PerformanceMonitoringFeaturesinRL20

5 Performance Monitoring Features in RL20

5.1 LTE805: PM Counter Capacity I


Introduction to the feature
Thisfeatureintroducesnewcounterstoenhancetheairinterfaceresourceutilizationand
throughputmonitoringcapabilities.

5.1.1 Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.
Operator benefits
Theoperatorgainsadditionalinsightintotheairinterfaceresourceutilizationand
throughputfortroubleshootingandoptimizationpurposes.

5.1.2 Requirements
Software requirements
Table101:Softwarerequirementsliststhesoftwarerequiredforthisfeature.

Table101 Softwarerequirements

System Release eNode B NetAct MME SAE GW

Release RL20 LBTS2.0 NAR1.0 - -

Hardware requirements
ThisfeaturerequireseitherFlexiSystemModule(FSM)R2orFSMR3.

5.1.3 Functional description


Thefollowingcountergroupsareintroduced:

RANradioload-UEquantity:
numberofRRC-connectedUEs
downlinktransmissionqueuelength(signalingradiobearer/dataradiobearer)

RANradioload-channelutilization:
utilizationofPDCCH(fordifferentaggregationgroups)

RANradiothroughput-trafficchannelthroughput:
PRButilizationperchannel(UL/DL)
Itmonitorstheradiointerfaceload.Theloaddistributionoverthephysical
channelsshowsthetrafficrate.

Issue:02M DN0978033 235


PerformanceMonitoringFeaturesinRL20 LTERL20,FeatureDescriptions

NumberofUEsperTTI(UL/DL)
Itmonitorsthecellloadandhelpswithnetworkcapacityplanningandload
balancing.

NAStransport:
NASsignalingdatavolume(UL/DL)
ItmonitorstheS1ApplicationProtocoldownlink/uplinkNAStransportprocedure
usedfortheUE-MMEmessagetransfer.

Forthedetailedlistofcounters,see.

5.1.4 System impact


Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.
Impact on network and network element management tools
Newcountersaddedtotheperformancemonitoringtools.

5.1.5 Sales information


Table102 Salesinformation

BSW/ASW License control in network element License control attributes

ASW

5.1.6 User interface


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seetherelevantreferencedocumentation.
Alarms
Therearenoalarmsrelatedtothisfeature.
Measurements and counters
Table103:Newcounterslistscountersintroducedwiththisfeature.

Table103 Newcounters

Counter ID Counter name Measurement

M8000C29 NumberofUplinkNASTransportmessages 8000-LTES1AP

M8000C30 NumberofDownlinkNASTransport 8000-LTES1AP


messages

M8001C199 RRCConnectedUEsAvg 8001-LTECellLoad

236 DN0978033 Issue:02M


LTERL20,FeatureDescriptions PerformanceMonitoringFeaturesinRL20

Table103 Newcounters(Cont.)

Counter ID Counter name Measurement

M8001C200 RRCConnectedUEsMax 8001-LTECellLoad

M8001C210 MinimumqueuelengthDLSRB 8001-LTECellLoad

M8001C211 AveragequeuelengthDLSRB 8001-LTECellLoad

M8001C212 MaximumqueuelengthDLSRB 8001-LTECellLoad

M8001C213 MinimumqueuelengthDLDRB 8001-LTECellLoad

M8001C214 AveragequeuelengthDLDRB 8001-LTECellLoad

M8001C215 MaximumqueuelengthDLDRB 8001-LTECellLoad

M8011C38 CCEsavailablePDCCHscheduling 8011-LTECellResource

M8011C39 AGG1usedPDCCH 8011-LTECellResource

M8011C40 AGG2usedPDCCH 8011-LTECellResource

M8011C41 AGG4usedPDCCH 8011-LTECellResource

M8011C42 AGG8usedPDCCH 8011-LTECellResource

M8011C43 AGG1blockedPDCCH 8011-LTECellResource

M8011C44 AGG2blockedPDCCH 8011-LTECellResource

M8011C45 AGG4blockedPDCCH 8011-LTECellResource

M8011C46 AGG8blockedPDCCH 8011-LTECellResource

M8011C47 PRBusedULtotal 8011-LTECellResource

M8011C48 PRBusedPRACH 8011-LTECellResource

M8011C49 PRBusedPUCCH 8011-LTECellResource

M8011C50 PRBusedPUSCH 8011-LTECellResource

M8011C51 PRBusedDLtotal 8011-LTECellResource

M8011C52 PRBusedPBCH 8011-LTECellResource

M8011C53 PRBusedPDCCH 8011-LTECellResource

M8011C54 PRBusedPDSCH 8011-LTECellResource

Issue:02M DN0978033 237


PerformanceMonitoringFeaturesinRL20 LTERL20,FeatureDescriptions

Table103 Newcounters(Cont.)

Counter ID Counter name Measurement

M8011C55 AverageUEsperULTTI 8011-LTECellResource

M8011C56 MaxUEsperULTTI 8011-LTECellResource

M8011C57 AverageUEsperDLTTI 8011-LTECellResource

M8011C58 MaxUEsperDLTTI 8011-LTECellResource

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.
Parameters
Therearenoparametersrelatedtothisfeature.

238 DN0978033 Issue:02M


LTERL20,FeatureDescriptions FlexiMultiradioBTSLTESiteSolutionfeatures

6 Flexi Multiradio BTS LTE Site Solution


features

6.1 LTE87: Flexi 3-sector RF Module 850


6.1.1 Introduction to the feature
ThisfeatureintrocucesFlexiMultiradioRFModule(FXCA)for850MHzoperatingatthe
3GPPband5with15MHzRFbandwidth.ItprovidesalsoHWsupportfor3GPPbands
5,18and19

6.1.2 Benefits
TheFXCA3-sectorRFModuleoffersthefollowingbenefits:

themostcost,size,andweightoptimizedthree-sectorBTSsite,easierinstallation,
lessvisualimpact
industry-leadingRFintegrationlevel
software-configurableradio:thesameRFModuleforLTE,HSPA+,WCDMAand
GSM
canbeconfiguredtosupportone,twoorthreesectors,oronesectorwith2TXMIMO
HWsupportfor3GPPbands5,18and19
thewidestambienttemperaturerange:-35...+55C
thesmallestpowerconsumptionandOPEX
canbeusedasfeederlesssitewithoneDCand1-2opticalcables
canbeusedaspowerfulone-sectorRemoteRadioHeads(RRH):60+60W2TX
MIMOwithHWpreparedfor4RX.Athree-sectormoduleismorecost-effectivethan
threeseparateRFHeadsbecauseitislighterandcauseslesswindloadandvisual
impact,whilerequiringonlyonethirdoftheDCandopticalcabling.

6.1.3 Requirements

6.1.3.1 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

Table104 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

Issue:02M DN0978033 239


FlexiMultiradioBTSLTESiteSolutionfeatures LTERL20,FeatureDescriptions

Table104 Softwarerequirementsfordifferentnetworkelements(Cont.)

Network element Required software release

SAEGW

UE

NetAct

6.1.4 Functional description


FlexiMultiradioRFModuleHWsupportsGSM,WCDMAandLTEindedicatedor
concurrentmode.FlexiMultiradioRFModuledesignincludes3x60WoutputRFsignal
interfaces.
ThefollowingLTEconfigurationsaresupportedbyFXCA:

1,1+1or1+1+1LTEcellsatmaximum10MHzLTEbandwithand1TX/2RX
LTEbandwidthsupportislimitedto10MHzat3GPPband5duetothelimitedUE
capability.
8,20,40or60Wmodepersector(controlledbySWlicenses)
1sectorconfigurarionwithmaximum60W+60W2TX/2RXMIMO
HWreadytosupport1sectorconfigurarionwithmaximum60W+60W2TX/4RX
MIMO

FXCAcanbealsousedinfeederlesssite(opticalandDCcableupto200m).

6.1.5 Sales information


Table105 Salesinformation

BSW/ASW License control in network License control attributes


element

BSW

6.1.6 Activating the feature


Thisfeaturedoesnotrequireactivation.

6.2 LTE101: Flexi 3-sector RF Module 1800

240 DN0978033 Issue:02M


LTERL20,FeatureDescriptions FlexiMultiradioBTSLTESiteSolutionfeatures

6.2.1 Introduction to the feature


ThisfeatureintrocucesFlexiMultiradioRFModule(FXEA)for1800MHzoperatingatthe
3GPPbandsIIIandIX.

6.2.2 Benefits
TheFXEA3-sectorRFModuleoffersthefollowingbenefits:

themostcost,size,andweightoptimizedthree-sectorBTSsite,easierinstallation,
lessvisualimpact
industry-leadingRFintegrationlevel
software-configurableradio:thesameRFModuleforLTE,HSPA+,WCDMAand
GSM
canbeconfiguredtosupportone,twoorthreesectors,oronesectorwith2TXMIMO
HWsupportfor4-wayuplinkdiversity
thewidestambienttemperaturerange:-35...+55C
thesmallestpowerconsumptionandOPEX
canbeusedasfeederlesssitewithoneDCand1-2opticalcables
canbeusedaspowerfulone-sectorRemoteRadioHeads(RRH):60+60W2TX
MIMOwithHWpreparedfor4RX.Athree-sectormoduleismorecost-effectivethan
threeseparateRFHeadsbecauseitislighterandcauseslesswindloadandvisual
impact,whilerequiringonlyonethirdoftheDCandopticalcabling.

6.2.3 Requirements

6.2.3.1 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

Table106 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

UE

NetAct

Issue:02M DN0978033 241


FlexiMultiradioBTSLTESiteSolutionfeatures LTERL20,FeatureDescriptions

6.2.4 Functional description


FlexiMultiradioRFModuleHWsupportsGSM,WCDMAandLTEindedicatedor
concurrentmode.FlexiMultiradioRFModuledesignincludes3x60WoutputRFsignal
interfaces.
ThefollowingLTEconfigurationsaresupportedbyFXEA:

1,1+1or1+1+1LTEcellsatmaximum20MHzLTEbandwithand1TX/2RX
8,20,40or60Wmodepersector(controlledbySWlicenses)
1sectorconfigurarionwithmaximum60W+60W2TX/2RXMIMO
HWcapableofsupporting1sectorconfigurarionwithmaximum60W+60W
2TX/4RXMIMO

TheFlexiMultiradioRFModule(FXEA)supports:

3GPPBandIII
UL:1710-1785MHz
DL:1805-1880MHz

3GPPBandIX
UL:1749.9-1784.9MHz
DL:1844.9-1879.9MHz

FXEAcanbealsousedinfeederlesssite(opticalandDCcableupto200m).

6.2.5 Sales information


Table107 Salesinformation

BSW/ASW License control in network License control attributes


element

BSW

6.2.6 Activating the feature


Thisfeaturedoesnotrequireactivation.

6.3 LTE103: Flexi RRH 2TX 730


6.3.1 Introduction to the feature
ThisfeatureintrocucesFlexiMultiradioRemoteRFHead(RRH)with2TXfor3GPP
bands12and17.ItoperatesatNorthAmericanlower700MHz(730MHz)frequency
band.

242 DN0978033 Issue:02M


LTERL20,FeatureDescriptions FlexiMultiradioBTSLTESiteSolutionfeatures

6.3.2 Benefits
Theone-sectorFlexiMultiradioBTSRemoteRFHeadsareabletosupport2TXMIMO
withhighoutputpower.ThemodulesareIP65-protected,sotheycanbeinstalled
outdoorsclosetotheantennas,maximizingtheBTSsitecapacityandcoverageforone
sector.

6.3.3 Requirements

6.3.3.1 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

Table108 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

UE

NetAct

6.3.4 Functional description


TheFlexiRRHModuleoffersthefollowingmainfeatures:

30W+30Wwithtwopoweramplifiers
oneLTEcellwith2TXMIMOupto15.5MHzpersector
optimizedforsinglesectordeploymentwith2TXMIMO
opticalchainingsupportedbytheHW(twoopticalconnectors)
operatingtemperaturerange:-35to+50Cwithconvectioncooling
twoexternalalarmoutputs
AISG2.0AntennaTiltSupportwithanexternalconnector(RS485)
MHAsupportedbybothRXbrancheswithadjustable0...30dBLNAs
theotherTX/RXbranchwithintegratedBias-TtosupportAISG2.0MHA
MHASWsupportviaintegratedBias-T
VSWRmonitoringonbothTXbranches.

Issue:02M DN0978033 243


FlexiMultiradioBTSLTESiteSolutionfeatures LTERL20,FeatureDescriptions

6.3.5 Sales information


Table109 Salesinformation

BSW/ASW License control in network License control attributes


element

BSW

6.3.6 Activating the feature


Thisfeaturedoesnotrequireactivation.

6.4 LTE104: Flexi RRH 2TX 1800


6.4.1 Introduction to the feature
ThisfeatureintrocucesFlexiMultiradioRemoteRFHead(RRH)with2TXforLTE,
WCDMA/HSPAandGSM/EDGEtechnologiesoperatingat1800MHz3GPPband3.

6.4.2 Benefits
Theone-sectorFlexiMultiradioBTSRemoteRFHeadsareabletosupport2TXMIMO
withhighoutputpower.ThemodulesareIP65-protected,sotheycanbeinstalled
outdoorsclosetotheantennas,maximizingtheBTSsitecapacityandcoverageforone
sector.

6.4.3 Requirements

6.4.3.1 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

Table110 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

244 DN0978033 Issue:02M


LTERL20,FeatureDescriptions FlexiMultiradioBTSLTESiteSolutionfeatures

Table110 Softwarerequirementsfordifferentnetworkelements(Cont.)

Network element Required software release

UE

NetAct

6.4.4 Functional description


TheFlexiRRHModuleoffersthefollowingmainfeatures:

40W+40Wwithtwopoweramplifiers
defaultpowerlevelof20W+20WwithtwolicensestouseBranchActivationand
MIMO
40W+40Wwithtwolicensestouse40W
optimizedforsinglesectordeploymentwith2TXMIMO
opticalchainingsupportedbytheHW(twoopticalconnectors)
operatingtemperaturerange:-35to+50Cwithconvectioncooling
4externalalarmoutputs
AISG2.0AntennaTiltSupportwithanexternalconnector(RS485)
MHAsupportedbybothRXbrancheswithadjustable0...30dBLNAs
otherTX/RXbranchwithintegratedBias-TtosupportAISG2.0MHA
MHASWsupportviaintegratedBias-T
VSWRmonitoringonbothTXbranches.

6.4.5 Sales information


Table111 Salesinformation

BSW/ASW License control in network License control attributes


element

BSW

6.4.6 Activating the feature


Thisfeaturedoesnotrequireactivation.

6.5 LTE113: Cell Bandwidth - 15 MHz

Issue:02M DN0978033 245


FlexiMultiradioBTSLTESiteSolutionfeatures LTERL20,FeatureDescriptions

6.5.1 Introduction to the feature


Thisfeatureintroduces15MHzLTEcellRFbandwidthaccordingto3GPPspecifiedbit
ratesandsupportedUEcapability.

6.5.2 Benefits
TheoperatorcandeployLTEcellswith15MHzbandwidth.

6.5.3 Requirements

6.5.3.1 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

Table112 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

UE 3GPPRel.8

NetAct

6.5.3.2 Hardware requirements

ThisfeaturerequiresLTE82:HighCapacityFlexiSystemModuleFSMEandthe
respectiveRFmoduleorRRH.

6.5.4 Functional description


TheFlexiMultiradioBTSLTEsupports15MHzcellbandwidth.The15MHzbandwidth
forFDDisdefinedby3GPPforthefollowingbands:

I-IV
VII
IX-X
XVIII-XXI

g Note: NotethatonlythebandXXissupportedinRL20.

246 DN0978033 Issue:02M


LTERL20,FeatureDescriptions FlexiMultiradioBTSLTESiteSolutionfeatures

TheLTEcell/carrierbandwidthforeachbandwidthoptionissetusingasoftware
configurationparameter.TheRFhardwareispreparedtosupportbandwidthsupto
20MHz,dependingonthe3GPPbandand3GPPspecification.

6.5.5 Sales information


Table113 Salesinformation

BSW/ASW License control in network License control attributes


element

ASW

6.5.6 Activating the feature


Thisfeaturerequiresactivation.

6.6 LTE447: SW support for RF sharing GSM-LTE


6.6.1 Introduction to the feature
ThisfeatureallowsFlexiMultiradioBTSRFModule(FRM)tooperateinconcurrent
modewithGSMandLTE.ThismeansthatoneFRMistransmittingbothGSM/EDGERF
carrier(s)andLTERFcarriersignalsatthesame3GPPfrequencyband.
IntheconcurrentmodeFlexiMultiradioEDGESystemModuleoperatesinGSM/EDGE
modeandFlexiMultimodeSystemModuleinLTEmoderespectively.Bothare
connectedtothesameFRM.

6.6.2 Benefits
Thisfeaturegivesthefollowingbenefits:

EasymigrationtoLTEforGSMoperatorswithFlexiMultiradioBTSincludingFlexi
MultiradioRFModules.
FutureproofBTSsiteevolutionwherethesameFlexiMultiradioRFModulescanbe
usedeitherinGSM/EDGEdedicatedmode,orinconcurrentGSM-LTEmodeorin
LTEdedicatedmode.
FlexiMultiradioBTSbringsgeneralOPEXsavingsonsparepartstock,logisticsand
maintenance.

6.6.3 Requirements

6.6.3.1 Software requirements

Thefollowingsoftwareisrequiredforthisfeature.

Issue:02M DN0978033 247


FlexiMultiradioBTSLTESiteSolutionfeatures LTERL20,FeatureDescriptions

Table114 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

eNodeB LBTS2.0

MME

SAEGW

UE

GSM/EDGE EX4.1

NetAct OSS5.3CDSet2

6.6.3.2 Hardware requirements

ThisfeaturerequiresthefollowingFlexiMultiradioBTSSystemModules:

FlexiMultiradioBTSLTESystemModule(FSME)and
FlexiMultiradioBTSGSM/EDGESystemModule(ESMB/C)

ThisfeaturerequiresFlexiMultiradioRFModulethatsupportGSM/EDGEandLTE:

Flexi3-sectorRFModule1800(FXEA)or
Flexi3-sectorRFModule18003x80W(FXEB)

6.6.4 Functional description


FlexiMultiradioRFModuleoperatesinconcurrentGSM/EDGEandLTEmodeonone
3GPPband.IntheconcurrentGSM-LTEmodethefollowing3GPPbandsaresupported:

1800MHz(3GPPband3and9)

ThemaximumTXRFbandwidthcurrentlysupportedbytheFlexiMultiradioRFModuleis
25MHz.

Figure36 ConceptofGSMandLTEconcurrentmode

248 DN0978033 Issue:02M


LTERL20,FeatureDescriptions FlexiMultiradioBTSLTESiteSolutionfeatures

g Note: Themax.supporteddistancebetweenSMandRF-unitsforclassicalRF-sharing
is10km.

Thefollowingconfigurationsaresupported:

FlexiMultiradio3-sectorRFModulesupportsthreeLTEcellconfiguration.
One,twoandthreesectorconcurrentRFconfigurationsaresupportedwith1TX
SIMOwithoneRFModule.
TwoandthreesectorRFconfigurationswith2TXMIMOaredonewithtwoRF
Modules.Onesector2TXMIMOissupportedbyoneRFModule.

For1TXSIMOconcurrentRFGSM-LTEbasicconfigurations(withone3-sectorFlexi
MultiradioRFModuleforeachthreesectorsandmaximum60Wpereachsector)the
followingnumberofcarriersareallowed:

maximum5GSMcarriers+maximumone5MHzLTEcarrier
maximum4GSMcarriers+maximumone10MHzLTEcarrier
maximum2GSMcarriers+maximumone15MHzLTEcarrierforoneortwosectors
withoneRFModuleat1800MHz

g Note: NotethatthreesectorRFsharingwith15MHzLTEcarrierat1800MHzrequires
2TXMIMO,thatis,twoRFModules.

For2TXMIMOconcurrentRFGSM-LTEbasicconfigurations(withtwo3-sectorRF
Modulesforeachthreesectorsandmaximum80W+80Wpereachsector)

maximum10GSMcarriers+maximumone5MHzLTEcarrierwith2TXMIMO
maximum8GSMcarriers+maximumone10MHzLTEcarrierwith2TXMIMO
maximum4GSMcarriers+maximumone15MHzLTEcarrierwith2TXMIMOat
1800MHz

g Note: BTSalarmhandlingmayshowactivealarmdifferenciesinthepeertechnology
sidewhenRFSharingisactive.

g Note: WhenrunningaTRXtestinGSMside,theRFModuleisconfiguredintest
mode.IftheRFModuleisalsocommissionedtoRFSharing,itwillcausecalldropsin
thepeertechnologyside.

6.6.5 Sales information


Table115 Salesinformation

BSW/ASW License control in network element License control attributes

ASW - -

6.6.6 Activating the feature


Thisfeaturerequiresactivation.SeeConfiguringGSM-LTERFSharingforinstructions.

Issue:02M DN0978033 249


FlexiMultiradioBTSLTESiteSolutionfeatures LTERL20,FeatureDescriptions

6.7 LTE1102: FFCC TRS External Filter for FXCA


Introduction to the feature
ThisfeaturedefinestheexternalfilterFFCCthatisusedtogetherwithFXCA.

6.7.1 Benefits
Operator benefits
TheFFCCallowstofulfilldemandingcositingrequirementsonlocalKoreanradio
systems.

6.7.2 Requirements
Software requirements
Table116:Softwarerequirementslistssoftwarerequiredforthisfeature.

Table116 Softwarerequirements

System release eNode B NetAct MME SAE GW

RL20 LN2.0 - - -

Hardware requirements
FlexiBTSMultimodeSystemModule(FSMD,FSME)
FlexiMultiradioBTSRFModuleFXCA

6.7.3 Functional description


Functional overview
LTE1102:FFCCTRSExternalFilterforFXCAprovidesfollowingfeatures:

Four7/16antennaconnectors(onepairtowardsthesystemmoduleandone
towardsRRH)
Wantedfrequencyband:
RX:839-849MHz
TX:884-894MHz

Twooutputports(SMA,female)forpowermonitoring
Dimensionsare324mmx145mmx120mmwithoutconnectorsandmounting
brackets
Weightlessthan9kg
Operatingtemperaturerange:-40C...+55C
Ingressprotection:IP65

250 DN0978033 Issue:02M


LTERL20,FeatureDescriptions FlexiMultiradioBTSLTESiteSolutionfeatures

Figure37 IsometricviewoftheFFCC

Issue:02M DN0978033 251


FlexiMultiradioBTSLTESiteSolutionfeatures LTERL20,FeatureDescriptions

Figure38 FrontviewoftheFFCC

6.7.4 System impacts


Interdependencies between features
Thisfeaturehasnorelatedorinterworkingfeatures.
Impacts on interfaces
Thisfeaturehasnoimpactoninterfaces.
Impacts on network and network element management tools
Thisfeaturehasnoimpactonnetworkmanagementandnetworkelementmanagement
tools.
Impacts on system performance and capacity
Newconfigurationsareavailable.

6.7.5 LTE1102: FFCC TRS External Filter for FXCA management


data
Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.
Alarms
Therearenoalarmsrelatedtothisfeature.
Measurements and counters
Therearenomeasurementsorcountersrelatedtothisfeature.

252 DN0978033 Issue:02M


LTERL20,FeatureDescriptions FlexiMultiradioBTSLTESiteSolutionfeatures

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.
Parameters
Therearenoparametersrelatedtothisfeature.

6.7.6 Sales information


ThismodulehassamepowerandMulticarrierlicensesasotherearliermodules.It
requiresBranchlicense.

Table117 Salesinformation

BSW/ASW License control in network element License control attributes

BSW

Issue:02M DN0978033 253