Sie sind auf Seite 1von 131

LTE Radio Access, Rel.

RL60,
Operating Documentation,
Issue 03

Feature Descriptions RL10


DN0978045
Issue 02B
Approval Date 2012-09-30

FeatureDescriptionsRL10

Theinformationinthisdocumentissubjecttochangewithoutnoticeanddescribesonlytheproduct
defined in the introduction of this documentation. This documentation is intended for the use of
NokiaSolutionsandNetworkscustomersonlyforthepurposesoftheagreementunderwhichthe
documentissubmitted,andnopartofitmaybeused,reproduced,modifiedortransmittedinany
formormeanswithoutthepriorwrittenpermissionofNokiaSolutionsandNetworks.Thedocumen-
tationhasbeenpreparedtobeusedbyprofessionalandproperlytrainedpersonnel,andthecus-
tomerassumesfullresponsibilitywhenusingit.NokiaSolutionsandNetworkswelcomescustomer
commentsaspartoftheprocessofcontinuousdevelopmentandimprovementofthedocumenta-
tion.

The information or statements given in this documentation concerning the suitability, capacity, or
performanceofthementionedhardwareorsoftwareproductsaregiven"asis"andallliabilityaris-
inginconnectionwithsuchhardwareorsoftwareproductsshallbedefinedconclusivelyandfinally
in a separate agreement between Nokia Solutions and Networks and the customer. However,
NokiaSolutionsandNetworkshasmadeallreasonableeffortstoensurethattheinstructionscon-
tained in the document are adequate and free of material errors and omissions. Nokia Solutions
and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which
maynotbecoveredbythedocument.

NokiaSolutionsandNetworkswillcorrecterrorsinthisdocumentationassoonaspossible.INNO
EVENT WILL Nokia Solutions and Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-
TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-
RECT,INCIDENTALORCONSEQUENTIALORANYLOSSES,SUCHASBUTNOTLIMITEDTO
LOSSOFPROFIT,REVENUE,BUSINESSINTERRUPTION,BUSINESSOPPORTUNITYORDA-
TA,THATMAYARISEFROMTHEUSEOFTHISDOCUMENTORTHEINFORMATIONINIT.

Thisdocumentationandtheproductitdescribesareconsideredprotectedbycopyrightsandother
intellectualpropertyrightsaccordingtotheapplicablelaws.

NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia
Corporation.Otherproductnamesmentionedinthisdocumentmaybetrademarksoftheirrespec-
tiveowners,andtheyarementionedforidentificationpurposesonly.

CopyrightNokiaSolutionsandNetworks2012.Allrightsreserved

f Important Notice on Product Safety


Thisproductmaypresentsafetyrisksduetolaser,electricity,heat,andothersourcesof
danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.

ThesafetyinformationisprovidedintheSafetyInformationsectionintheLegal,Safety
andEnvironmentalInformationpartofthisdocumentordocumentationset.

NokiaSolutionsandNetworksiscontinuallystrivingtoreducetheadverseenvironmentaleffectsof
itsproductsandservices.Wewouldliketoencourageyouasourcustomersanduserstojoinusin
working towards a cleaner, safer environment. Please recycle product packaging and follow the
recommendationsforpoweruseandproperdisposalofourproductsandtheircomponents.

IfyoushouldhavequestionsregardingourEnvironmentalPolicyoranyoftheenvironmentalser-
vicesweoffer,pleasecontactusatNokiaSolutionsandNetworksforanyadditionalinformation.

2 DN0978045 Issue:02B
FeatureDescriptionsRL10

Table of Contents
Thisdocumenthas131pages

SummaryofChanges.................................................................. 15

1 FeatureDescriptionsRL10.......................................................... 16
1.1 Radioresourcemanagementandtelecomfeaturesfromprevious
releasesforRL20.........................................................................16
1.1.1 LTE28:ClosedloopULpowercontrol..........................................16
1.1.1.1 Introductiontothefeature............................................................ 16
1.1.1.2 Benefits........................................................................................ 16
1.1.1.2.1 Enduserbenefits......................................................................... 16
1.1.1.2.2 Operatorbenefits......................................................................... 16
1.1.1.3 Requirements...............................................................................17
1.1.1.3.1 Softwarerequirements................................................................. 17
1.1.1.3.2 Hardwarerequirements................................................................17
1.1.1.4 Functionaldescription.................................................................. 17
1.1.1.4.1 Functionaldetails......................................................................... 17
1.1.1.4.1.1 Messagesandinformationelements........................................... 19
1.1.1.5 Systemimpacts............................................................................ 20
1.1.1.5.1 Interdependenciesbetweenfeatures........................................... 20
1.1.1.5.2 Impactsoninterfaces................................................................... 20
1.1.1.5.3 Impactsonperformanceandcapacity......................................... 20
1.1.1.6 Userinterface...............................................................................20
1.1.1.6.1 Parameters...................................................................................20
1.1.1.6.2 Measurementsandcounters........................................................23
1.1.1.7 ActivatingTheFeature................................................................. 24
1.1.1.8 Abbreviations............................................................................... 24
1.1.1.8.1 0Z............................................................................................. 24
1.1.2 LTE30:CQIadaption(DL)............................................................24
1.1.2.1 Introductiontothefeature............................................................ 24
1.1.2.2 Benefits........................................................................................ 25
1.1.2.3 Requirements...............................................................................25
1.1.2.3.1 Softwarerequirements................................................................. 25
1.1.2.3.2 Hardwarerequirements................................................................25
1.1.2.4 Functionaldescription.................................................................. 25
1.1.2.4.1 Functionaldetails......................................................................... 25
1.1.2.5 Systemimpacts............................................................................ 26
1.1.2.5.1 Interdependenciesbetweenfeatures........................................... 26
1.1.2.6 Userinterface...............................................................................26
1.1.2.6.1 Parameters...................................................................................26
1.1.2.7 ActivatingTheFeature................................................................. 27
1.1.3 LTE37:CipheringandLTE38:Integrityprotection........................27
1.1.3.1 Introductiontothefeature............................................................ 27
1.1.3.2 Benefits........................................................................................ 28

Issue:02B DN0978045 3
FeatureDescriptionsRL10

1.1.3.3 Requirements...............................................................................28
1.1.3.3.1 Softwarerequirements................................................................. 28
1.1.3.3.2 Hardwarerequirements................................................................28
1.1.3.4 Functionaldescription.................................................................. 29
1.1.3.4.1 Functionaloverview..................................................................... 29
1.1.3.4.2 Securitykeys................................................................................30
1.1.3.4.3 Messagesandinformationelements........................................... 33
1.1.3.5 Systemimpacts............................................................................ 35
1.1.3.5.1 Interdependenciesbetweenfeatures........................................... 35
1.1.3.5.2 Impactsonnetworkelements...................................................... 35
1.1.3.5.3 Impactsonsystemperformanceandcapacity.............................35
1.1.3.6 Userinterface...............................................................................35
1.1.3.6.1 Parameters...................................................................................35
1.1.3.7 ActivatingTheFeature................................................................. 36
1.1.4 LTE43:Supportof64QAMinDL,LTE788:Supportof16QAM
(UL),LTE793:Supportof16QAM(DL)....................................... 36
1.1.4.1 Introductiontothefeature............................................................ 36
1.1.4.2 Benefits........................................................................................ 36
1.1.4.3 Requirements...............................................................................37
1.1.4.3.1 Softwarerequirements................................................................. 37
1.1.4.3.2 Hardwarerequirements................................................................37
1.1.4.4 Functionaldescription.................................................................. 38
1.1.4.4.1 Functionaldetails......................................................................... 38
1.1.4.5 Systemimpacts............................................................................ 38
1.1.4.5.1 Interdependenciesbetweenfeatures........................................... 38
1.1.4.6 Salesinformation......................................................................... 38
1.1.4.7 Userinterface...............................................................................39
1.1.4.7.1 Managedobjects..........................................................................39
1.1.4.7.2 Parameters...................................................................................39
1.1.4.7.3 Measurementsandcounters........................................................39
1.1.4.8 ActivatingTheFeatures............................................................... 41
1.1.4.9 Abbreviations............................................................................... 41
1.1.4.9.1 0Z............................................................................................. 41
1.1.5 LTE69:TransmitdiversityfortwoantennasandLTE70:Downlink
adaptiveopenloopMIMOfortwoantennas................................ 43
1.1.5.1 Introductiontothefeature............................................................ 43
1.1.5.2 Benefits........................................................................................ 43
1.1.5.2.1 Enduserbenefits......................................................................... 43
1.1.5.2.2 Operatorbenefits......................................................................... 43
1.1.5.3 Requirements...............................................................................43
1.1.5.3.1 Softwarerequirements................................................................. 44
1.1.5.3.2 Hardwarerequirements................................................................44
1.1.5.4 Functionaldescription.................................................................. 44
1.1.5.4.1 Functionaloverview..................................................................... 44
1.1.5.4.2 DownlinkadaptiveopenloopMIMOfortwoantennas.................44
1.1.5.4.2.1 Receivediversity.......................................................................... 46

4 DN0978045 Issue:02B
FeatureDescriptionsRL10

1.1.5.4.2.2 Transmitdiversity......................................................................... 46
1.1.5.4.2.3 DownlinkopenloopMIMO........................................................... 47
1.1.5.4.3 Transmitdiversityfortwoantennas..............................................48
1.1.5.4.4 Openloopspatialmultiplexing..................................................... 48
1.1.5.5 Systemimpacts............................................................................ 49
1.1.5.5.1 Interdependenciesbetweenfeatures........................................... 49
1.1.5.5.2 Impactsoninterfaces................................................................... 49
1.1.5.5.3 Impactsonnetworkandnetworkelementmanagementtools..... 49
1.1.5.5.4 Impactsonsystemperformanceandcapacity.............................49
1.1.5.6 Salesinformation......................................................................... 49
1.1.5.7 Userinterface...............................................................................49
1.1.5.7.1 ManagedObjects......................................................................... 50
1.1.5.7.2 Parameters...................................................................................50
1.1.5.7.3 Alarms.......................................................................................... 51
1.1.5.7.4 Measurementsandcounters........................................................51
1.1.5.8 ActivatingtheFeature.................................................................. 51
1.2 Transportandtransmissionfeaturesfrompreviousreleasesfor
RL20.............................................................................................51
1.2.1 LTE713:SynchronousEthernet................................................... 51
1.2.1.1 IntroductiontotheFeature........................................................... 51
1.2.1.2 Benefits........................................................................................ 51
1.2.1.3 Requirements...............................................................................51
1.2.1.3.1 SoftwareRequirements................................................................51
1.2.1.3.2 HardwareRequirements.............................................................. 52
1.2.1.4 FunctionalDescription..................................................................52
1.2.1.4.1 SynchronizationStatusMessages(SSM)....................................52
1.2.1.5 SalesInformation......................................................................... 53
1.2.1.6 UserInterface...............................................................................53
1.2.1.6.1 Parameters...................................................................................53
1.2.1.6.2 Alarms.......................................................................................... 54
1.2.1.6.3 MeasurementsandCounters.......................................................54
1.2.1.7 ActivatingandConfiguringtheFeature........................................54
1.2.2 LTE132:VLANbasedtrafficdifferentiation................................. 54
1.2.2.1 IntroductiontotheFeature........................................................... 54
1.2.2.2 Benefits........................................................................................ 54
1.2.2.3 Requirements...............................................................................55
1.2.2.3.1 SoftwareRequirements................................................................55
1.2.2.3.2 HardwareRequirements.............................................................. 55
1.2.2.4 FunctionalDescription..................................................................55
1.2.2.4.1 NetworkScenarioswithVLANbasedTrafficDifferentiation.........56
1.2.2.4.1.1 X2interfaceviaIPsecStarConfiguration.................................... 57
1.2.2.4.2 VLANbasedTrafficDifferentiation:MappingofDLPacketsinthe
SecurityGateway......................................................................... 58
1.2.2.4.3 VLANbasedTrafficDifferentiation:MappingofDLPacketsinthe
VLANGateway.............................................................................59
1.2.2.5 SalesInformation......................................................................... 59

Issue:02B DN0978045 5
FeatureDescriptionsRL10

1.2.2.6 UserInterface...............................................................................59
1.2.2.6.1 Parameters...................................................................................59
1.2.2.6.2 Alarms.......................................................................................... 60
1.2.2.6.3 MeasurementsandCounters.......................................................60
1.2.2.7 ActivatingandConfiguringtheFeature........................................61
1.2.3 LTE134:Timingoverpacket.........................................................61
1.2.3.1 LTE134:TimingoverPacket........................................................ 61
1.2.3.1.1 Benefits........................................................................................ 61
1.2.3.1.2 Requirements...............................................................................61
1.2.3.1.3 FunctionalDescription..................................................................62
1.2.3.1.3.1 ToPMaster................................................................................... 62
1.2.3.1.3.2 ToPSlave..................................................................................... 62
1.2.3.1.3.3 SupportofIEEE1588EventMessages.......................................63
1.2.3.1.4 Managementdata........................................................................ 64
1.2.3.1.5 Salesinformation......................................................................... 65
1.2.3.1.6 Activatingandconfiguringthefeature..........................................65
1.3 OperabilityfeaturesfrompreviousreleasesforRL20..................65
1.3.1 LTE150:LTEOAMTransportLayerSecurity(TLS)Support........65
1.3.1.1 Introductiontothefeature............................................................ 65
1.3.1.2 Benefits........................................................................................ 65
1.3.1.3 Requirements...............................................................................66
1.3.1.3.1 Softwarerequirements................................................................. 66
1.3.1.3.2 Hardwarerequirements................................................................66
1.3.1.4 FunctionaldescriptionforLTEOAMTransportLayerSecurity
(TLS)Support...............................................................................66
1.3.1.4.1 SecureBTSSiteManagerconnection......................................... 69
1.3.1.5 Systemimpact..............................................................................69
1.3.1.5.1 Interdependenciesbetweenfeatures........................................... 69
1.3.1.5.2 Impactoninterfaces.....................................................................69
1.3.1.5.3 Impactonnetworkandnetworkelementmanagementtools.......69
1.3.1.5.4 Impactonsystemperformanceandcapacity...............................69
1.3.1.6 Salesinformation......................................................................... 69
1.3.1.7 ParametersforLTE150:LTEOAMTransportLayerSecurity(TLS)
Support.........................................................................................70
1.3.1.8 AlarmsforLTE150:LTEOAMTransportLayerSecurity(TLS)
Support.........................................................................................70
1.3.2 LTE432:CellOutageDetection....................................................71
1.3.2.1 Introduction.................................................................................. 71
1.3.2.2 Benefits........................................................................................ 71
1.3.2.3 Requirements...............................................................................71
1.3.2.3.1 SoftwareRequirementsforLTE432............................................. 71
1.3.2.3.2 SoftwareRequirementsforLTE502............................................. 71
1.3.2.3.3 HardwareRequirements.............................................................. 71
1.3.2.4 FunctionalDescription..................................................................72
1.3.2.4.1 LTE432:CellOutageDetection....................................................72
1.3.2.4.1.1 FailureScenarios......................................................................... 72

6 DN0978045 Issue:02B
FeatureDescriptionsRL10

1.3.2.4.1.2 AlarmGeneration......................................................................... 73
1.3.2.4.2 LTE502:Celloutagetriggeredreset.............................................73
1.3.2.5 SystemImpacts............................................................................74
1.3.2.5.1 InterdependenciesbetweenFeatures..........................................74
1.3.2.6 SalesInformation......................................................................... 74
1.3.2.7 UserInterface...............................................................................74
1.3.2.7.1 ParametersforLTE432:Celloutagedetection............................ 74
1.3.2.7.1.1 LTE502:Celloutagetriggeredreset.............................................75
1.3.2.7.2 AlarmsforLTE432:Celloutagedetection....................................75
1.3.2.7.2.1 AlarmsforLTE502:Celloutagetriggeredreset........................... 76
1.3.2.7.3 MeasurementsandCountersforLTE432:Celloutagedetection....
76
1.3.2.8 SystemResponsestoFailures.................................................... 77
1.3.2.9 ActivatingtheFeature.................................................................. 77
1.3.2.10 Abbreviations............................................................................... 77
1.3.2.10.1 0Z............................................................................................. 77
1.3.3 LTE539:CentralANR...................................................................78
1.3.3.1 Introduction.................................................................................. 78
1.3.3.2 Benefits........................................................................................ 78
1.3.3.2.1 OperatorBenefits......................................................................... 78
1.3.3.3 Requirements...............................................................................78
1.3.3.3.1 SoftwareRequirements................................................................78
1.3.3.3.2 HardwareRequirements.............................................................. 79
1.3.3.4 LTE539:CentralANR...................................................................79
1.3.3.4.1 FunctionalOverview/Details.........................................................79
1.3.3.4.1.1 NetActOptimizer.......................................................................... 79
1.3.3.4.1.2 NetActConfigurator......................................................................83
1.3.3.4.1.3 IntegrationintheAutoconfigurationWorkflow.............................84
1.3.3.5 SystemImpacts............................................................................84
1.3.3.5.1 InterdependenciesBetweenFeatures......................................... 84
1.3.3.6 SalesInformation......................................................................... 85
1.3.3.7 ActivatingandConfiguringtheFeature........................................85
1.3.3.8 Abbreviations............................................................................... 85
1.3.3.8.1 0Z............................................................................................. 85
1.3.4 LTE665:CertificateManagementandLTE685:Infrastructuresfor
CertificationAuthority(CA)andRegistrationAuthority(RA)........86
1.3.4.1 Introductiontothefeature............................................................ 86
1.3.4.1.1 LTE665:LTECertificateManagement......................................... 86
1.3.4.1.2 LTE685:InfrastructuresforCertificationAuthority(CA)and
RegistrationAuthority(RA)......................................................... 86
1.3.4.2 Benefits........................................................................................ 86
1.3.4.2.1 LTE665:LTECertificateManagement......................................... 86
1.3.4.2.2 LTE685:InfrastructuresforCertificationAuthority(CA)and
RegistrationAuthority(RA).......................................................... 86
1.3.4.3 Requirements...............................................................................86
1.3.4.3.1 Softwarerequirements................................................................. 86

Issue:02B DN0978045 7
FeatureDescriptionsRL10

1.3.4.3.2 Hardwarerequirements................................................................87
1.3.4.4 Functionaldescriptionforcertificatemanagement.......................87
1.3.4.4.1 LTE665:LTECertificateManagement......................................... 87
1.3.4.4.2 LTE685:InfrastructuresforCertificationAuthority(CA)and
RegistrationAuthority(RA).......................................................... 91
1.3.4.5 Systemimpacts............................................................................ 93
1.3.4.6 Salesinformation......................................................................... 93
1.3.4.7 Userinterface...............................................................................93
1.3.4.7.1 ParametersforLTE665:LTECertificateManagement.................93
1.3.4.7.2 AlarmsforLTE665:LTECertificateManagement........................ 94
1.3.4.8 Activatingandconfiguringthefeature..........................................95
1.3.5 LTE666:LTEUserAccountManagement.................................... 95
1.3.5.1 Introductiontothefeature............................................................ 95
1.3.5.2 Benefits........................................................................................ 95
1.3.5.3 Requirements...............................................................................96
1.3.5.3.1 SoftwareRequirements................................................................96
1.3.5.3.2 HardwareRequirements.............................................................. 96
1.3.5.4 Functionaldescriptionforusersecurity........................................96
1.3.5.4.1 Authenticationandauthorization..................................................96
1.3.5.4.2 DisablinguseraccountsinNetAct............................................... 97
1.3.5.4.3 Usermanagement........................................................................97
1.3.5.4.3.1 MassupdatingofeNBlocaluseraccounts.................................. 97
1.3.5.4.4 Audittrail...................................................................................... 97
1.3.5.5 Systemimpacts............................................................................ 98
1.3.5.6 Salesinformation......................................................................... 98
1.3.5.7 Userinterface...............................................................................99
1.3.5.7.1 ParametersforLTE666:LTEUserAccountManagement........... 99
1.3.5.7.2 AlarmsforLTE666:LTEUserAccountManagement...................99
1.3.5.8 Activatingandconfiguringthefeature........................................100
1.3.6 LTE679:LTELocalUserAccountManagement........................ 100
1.3.6.1 Introductiontothefeature.......................................................... 100
1.3.6.2 Benefits...................................................................................... 100
1.3.6.3 Requirements.............................................................................100
1.3.6.3.1 Softwarerequirements............................................................... 100
1.3.6.3.2 Hardwarerequirements..............................................................101
1.3.6.4 FunctionaldescriptionforLTELocalUserAccountManagement...
101
1.3.6.5 Systemimpacts..........................................................................101
1.3.6.6 Salesinformation....................................................................... 101
1.3.6.7 Userinterface.............................................................................101
1.3.6.7.1 ParametersforLTE679:LTELocalUserAccountManagement......
101
1.3.6.8 Activatingthefeature................................................................. 101
1.3.7 LTE689:LTEIPsecSupport....................................................... 101
1.3.7.1 Introductiontothefeature.......................................................... 101
1.3.7.2 Benefits...................................................................................... 102

8 DN0978045 Issue:02B
FeatureDescriptionsRL10

1.3.7.3 Requirements.............................................................................102
1.3.7.3.1 Softwarerequirements............................................................... 102
1.3.7.3.2 Hardwarerequirements..............................................................102
1.3.7.4 FunctionaldescriptionforIPsecSupport................................... 103
1.3.7.4.1 Transportsecurity.......................................................................104
1.3.7.5 Systemimpacts..........................................................................104
1.3.7.6 Salesinformation....................................................................... 104
1.3.7.7 Userinterface.............................................................................105
1.3.7.7.1 ParametersforLTE689:LTEIPsecSupport.............................. 105
1.3.7.7.2 AlarmsforLTE689:LTEIPsecSupport......................................108
1.3.7.7.3 CountersforLTE689:LTEIPsecSupport.................................. 109
1.3.7.8 Activatingandconfiguringthefeature........................................109
1.3.8 LTE692:LTEFirewallSupport....................................................110
1.3.8.1 Introductiontothefeature...........................................................110
1.3.8.2 Benefits.......................................................................................110
1.3.8.3 Requirements............................................................................. 110
1.3.8.3.1 Softwarerequirements............................................................... 110
1.3.8.3.2 Hardwarerequirements.............................................................. 110
1.3.8.4 FunctionaldescriptionforLTEFirewallSupport......................... 110
1.3.8.4.1 Firewallfunctionality................................................................... 111
1.3.8.4.2 Firewallfilter............................................................................... 113
1.3.8.4.3 Logging.......................................................................................113
1.3.8.5 Systemimpacts.......................................................................... 114
1.3.8.6 Salesinformation........................................................................114
1.3.8.7 Userinterface............................................................................. 114
1.3.8.7.1 ParametersforLTE692:LTEFirewallSupport........................... 114
1.3.8.7.2 CountersforLTE692:LTEFirewallSupport............................... 114
1.3.8.8 Activatingandconfiguringthefeature........................................ 115
1.3.9 LTE746:IPbasedfilteringforBTSSiteSupportEquipment...... 115
1.3.9.1 Introductiontothefeature...........................................................115
1.3.9.2 Benefits.......................................................................................115
1.3.9.3 Requirements............................................................................. 115
1.3.9.3.1 Softwarerequirements............................................................... 115
1.3.9.3.2 Hardwarerequirements.............................................................. 116
1.3.9.4 FunctionaldescriptionforIPbasedfilteringforBTSSiteSupport
Equipment.................................................................................. 116
1.3.9.5 Systemimpacts.......................................................................... 116
1.3.9.6 Salesinformation........................................................................116
1.3.9.7 Userinterface............................................................................. 116
1.3.9.7.1 ParametersforLTE746:IPbasedfilteringforBTSSiteSupport
Equipment.................................................................................. 116
1.3.9.8 Activatingthefeature..................................................................118
1.3.10 LTE913:LTENEBScompliantOMS.......................................... 118
1.3.10.1 IntroductiontotheFeature......................................................... 118
1.3.10.2 Benefits.......................................................................................118
1.3.10.3 FunctionalDescription................................................................ 118

Issue:02B DN0978045 9
FeatureDescriptionsRL10

1.3.10.4 Requirements............................................................................. 119


1.4 FlexiMultiradioBTSLTESiteSolutionfeaturesfromprevious
releasesforRL20....................................................................... 119
1.4.1 IntroductiontotheFlexiMultiradioBTSSiteSolutionfeatures.. 119
1.4.2 Cell-relatedfeatures...................................................................120
1.4.2.1 LTEcellbandwidthfeatures:LTE112,LTE114,andLTE115....... 120
1.4.2.1.1 Introduction................................................................................ 120
1.4.2.1.2 Functionaldescription................................................................ 120
1.4.2.1.3 Benefits...................................................................................... 120
1.4.2.1.4 Activatingthefeature................................................................. 120
1.4.2.2 LTE97:Cellradiusmax77km................................................... 120
1.4.2.2.1 Introduction................................................................................ 120
1.4.2.2.2 Benefits...................................................................................... 120
1.4.2.2.3 Functionaldescription................................................................ 120
1.4.2.2.4 Activatingthefeature................................................................. 121
1.4.3 Antennalinefeatures................................................................. 121
1.4.3.1 LTE71:2-wayRXdiversity(MRC)..............................................121
1.4.3.1.1 Introduction................................................................................ 121
1.4.3.1.2 Benefits...................................................................................... 121
1.4.3.1.3 Functionaldescription................................................................ 121
1.4.3.2 LTE160:FlexiMultiradioBTS3GPPantennatiltsupport.......... 121
1.4.3.2.1 Introduction................................................................................ 121
1.4.3.2.2 Benefits...................................................................................... 121
1.4.3.2.3 Functionaldescription................................................................ 122
1.4.3.2.4 Managementdata...................................................................... 122
1.4.3.2.5 Activatingthefeature................................................................. 123
1.4.3.3 LTE94:Feederlesssite...............................................................123
1.4.3.3.1 Introduction................................................................................ 123
1.4.3.3.2 Benefits...................................................................................... 123
1.4.3.3.3 Functionaldescription................................................................ 123
1.4.4 FlexiMultiradioBTSRFModules...............................................124
1.4.4.1 Introduction................................................................................ 124
1.4.4.2 Benefits...................................................................................... 124
1.4.4.3 LTE85:Flexi3-sectorRFModule2600(FRHA).........................124
1.4.4.4 LTE99:Flexi3-sectorRFModule1.7/2.1(FRIE)....................... 124
1.4.4.5 LTE437:Flexi3-sectorRFModule800EU.................................124
1.4.4.6 LTE96:MIMO2TXconfigurationwith3-sectorRFModule........ 125
1.4.4.6.1 Introduction................................................................................ 125
1.4.4.6.2 Benefits...................................................................................... 125
1.4.4.6.3 Functionaldescription................................................................ 125
1.4.5 FlexiMultiradioBTSRemoteRadioHeads................................125
1.4.5.1 Benefits...................................................................................... 125
1.4.6 CabinetsandotherFlexiMultiradioBTShardware....................125
1.4.6.1 LTE79:FlexiIndoor(FCIA)andOutdoor(FCOA)Cabinets....... 125
1.4.6.1.1 Introduction................................................................................ 125
1.4.6.1.2 Benefits...................................................................................... 125

10 DN0978045 Issue:02B
FeatureDescriptionsRL10

1.4.6.1.3 Functionaldescription................................................................ 126


1.4.6.2 LTE78:FlexiAC/DCwithBatteryPowerModule(FPMA).......... 127
1.4.6.2.1 Introduction................................................................................ 127
1.4.6.2.2 Benefits...................................................................................... 127
1.4.6.2.3 Functionaldescription................................................................ 127
1.4.6.3 LTE82:High-capacityFlexiSystemModule(FSME)................. 127
1.4.6.3.1 Introduction................................................................................ 127
1.4.6.3.2 Benefits...................................................................................... 128
1.4.6.3.3 Functionaldescription................................................................ 128
1.4.7 LTE80:GPSsynchronization..................................................... 128
1.4.7.1 Introduction................................................................................ 128
1.4.7.2 Benefits...................................................................................... 128
1.4.7.3 Functionaldescription................................................................ 128
1.4.8 Powersupportfeatures.............................................................. 129
1.4.8.1 LTE900:FlexiMultiradioBTS40Wpowersupport....................129
1.4.8.1.1 Introduction................................................................................ 129
1.4.8.1.2 Benefits...................................................................................... 129
1.4.8.1.3 Functionaldescription................................................................ 129
1.4.8.2 LTE901:FlexiMultiradioBTS8Wpowersupport......................129
1.4.8.2.1 Introduction................................................................................ 129
1.4.8.2.2 Benefits...................................................................................... 129
1.4.8.2.3 Functionaldescription................................................................ 130
1.4.8.3 LTE903:FlexiMultiradioBTS60Wpowersupport....................130
1.4.8.3.1 Introduction................................................................................ 130
1.4.8.3.2 Benefits...................................................................................... 130
1.4.8.3.3 Functionaldescription................................................................ 130
1.4.8.4 LTE904:FlexiLTEBTSBranchActivation................................. 131
1.4.8.4.1 Introduction................................................................................ 131
1.4.8.4.2 Benefits...................................................................................... 131
1.4.8.4.3 Functionaldescription................................................................ 131

Issue:02B DN0978045 11
FeatureDescriptionsRL10

List of Figures
Figure1 Powercontroldecisionmatrix.............................................................18
Figure2 PrincipleofCQIadaptation.................................................................26
Figure3 C-planesecurity..................................................................................29
Figure4 U-planesecurity..................................................................................29
Figure5 Securitykeyhierarchy........................................................................ 31
Figure6 Throughputfordifferentmodulationschemes.................................... 37
Figure7 QAMmodulation.................................................................................38
Figure8 2x2MIMOconfiguration..................................................................... 47
Figure9 Multipoint-to-multipointVLAN............................................................. 56
Figure10 Point-to-PointVLAN........................................................................... 57
Figure11 IPsecstarconfiguration...................................................................... 58
Figure12 LTE432ThresholderandProfilerinNetAct......................................72
Figure13 Transportprotocolstackoverview.................................................... 104

12 DN0978045 Issue:02B
FeatureDescriptionsRL10

List of Tables
Table1 Softwarerequirementsfordifferentnetworkelements....................... 17
Table2 ParametersforclosedloopULpowercontrol.................................... 21
Table3 ParameterscommonforopenandclosedloopULpowercontrol......22
Table4 Newandmodifiedcounters................................................................ 23
Table5 Softwarerequirementsfordifferentnetworkelements....................... 25
Table6 Softwarerequirementsfordifferentnetworkelements....................... 28
Table7 Securityrelatedmessagesandinformationelements........................33
Table8 Parametersforcipheringandintegrityprotection...............................35
Table9 Softwarerequirementsfordifferentnetworkelements....................... 37
Table10 ParametersforLTE43:Supportof64QAMinDL............................... 39
Table11 CountersforLTE43............................................................................ 39
Table12 MultiantennaoptionsinLTE.............................................................. 46
Table13 ParametersforLTE70:DownlinkadaptiveopenloopMIMOfortwo
antennas............................................................................................50
Table14 Softwarerequirementsfordifferentnetworkelements....................... 52
Table15 ParametersrelatedtotheLTE713:SynchronousEthernetfeature....53
Table16 Softwarerequirementsfordifferentnetworkelements....................... 55
Table17 SupportednumbersofVLANs............................................................55
Table18 SalesInformation................................................................................59
Table19 ParametersrelatedtotheLTE132:VLANbasedtrafficdifferentiation...
59
Table20 CountersfortheLTE132:VLANbasedtrafficdifferentiation.............. 60
Table21 Softwarerequirementsfordifferentnetworkelements....................... 62
Table22 ParametersrelatedtotheLTE134:Timingoverpacketfeature......... 64
Table23 Salesinformation................................................................................65
Table24 Softwarerequirementsfordifferentnetworkelements....................... 66
Table25 ParametersforLTE150:LTEOAMTransportLayerSecurity(TLS)
Support............................................................................................... 70
Table26 AlarmsforLTE150:LTEOAMTransportLayerSecurity(TLS)Support
............................................................................................................70
Table27 Softwarerequirementsfordifferentnetworkelements....................... 71
Table28 Interdependenciesbetweenfeatures................................................. 74
Table29 ParametersfortheLTE432:CellOutageDetection........................... 74
Table30 AlarmsfortheLTE432:Celloutagedetection.................................... 75
Table31 AlarmsfortheLTE502:Celloutagetriggeredreset........................... 76
Table32 CountersfortheLTE432:Celloutagedetection.................................76
Table33 Errorcodes......................................................................................... 77
Table34 Softwarerequirementsfordifferentnetworkelements....................... 78
Table35 Interdependenciesbetweenfeatures................................................. 84
Table36 Softwarerequirementsfordifferentnetworkelements....................... 86

Issue:02B DN0978045 13
FeatureDescriptionsRL10

Table37 ParametersforLTE665:LTECertificateManagement....................... 94
Table38 AlarmsforLTE665:LTEcertificatemanagement............................... 94
Table39 Softwarerequirementsfordifferentnetworkelements....................... 96
Table40 ParametersforLTE666:LTEUserAccountManagement..................99
Table41 ParametersforLTE666:LTEUserAccountManagement-BTSSM.. 99
Table42 AlarmsforLTE666:LTEUserAccountManagement......................... 99
Table43 Softwarerequirementsfordifferentnetworkelements..................... 100
Table44 ParametersforLTE679:LTELocalUserAccountManagement...... 101
Table45 Softwarerequirementsfordifferentnetworkelements..................... 102
Table46 Hardwarerequirementsfordifferentnetworkelements....................102
Table47 Salesinformation..............................................................................104
Table48 ParametersforLTE689:LTEIPsecSupport.....................................105
Table49 AlarmsforLTE689:LTEIPsecSupport............................................ 108
Table50 CountersforLTE689:LTEIPsecSupport.........................................109
Table51 Softwarerequirementsfordifferentnetworkelements..................... 110
Table52 Messages..........................................................................................111
Table53 ParametersforLTE692:LTEFirewallSupport................................. 114
Table54 CountersforLTE692:LTEFirewallSupport..................................... 115
Table55 Softwarerequirementsfordifferentnetworkelements..................... 115
Table56 ParametersforLTE746:IPbasedfilteringforBTSSiteSupport
Equipment.........................................................................................117
Table57 ParameterforconfiguringMTUsize................................................. 118
Table58 TheparametersrelatedtoLTE160:FlexiMultiradioBTS3GPP
antennatiltsupport........................................................................... 122

14 DN0978045 Issue:02B

FeatureDescriptionsRL10 SummaryofChanges

Summary of Changes
Changes between version 02B (2012-09-30, RL30) and 02C (2013-07-22, RL30)
Thefollowingfeaturedescriptionhasbeenupdated:

LTE665:CertificateManagement

Thefollowingfeatureactivationhasbeenupdated:

ActivatingLTE665:CertificateManagement

Changes between version 02A (2012-04-26, RL30) and 02B (2012-09-30, RL30)
Thefollowingfeaturedescriptionshavebeenupdated:

LTE665:CertificateManagementandLTE685:InfrastructuresforCertification
Authority(CA)andRegistrationAuthority(RA)

Changes between version 02 (2011-09-26, RL20) and 02A (2012-04-10, RL30)


Thefollowingfeaturedescriptionshavebeenupdated:

LTE97:CellRadiusMax77km
LTE432:CellOutageDetection
LTE746:IPBasedFilteringforBTSSiteSupportEquipment

Changes between version 01B (2011-03-24, RL20) and 02 (2011-09-26, RL30)


Thefollowingfeaturedescriptionshavebeenupdated:

LTE665:CertificateManagementandLTE685:InfrastructuresforCertification
Authority(CA)andRegistrationAuthority(RA)::Functionaldescriptionsectionhas
beenupdated.

Changes between version 01A (2010-12-17, RL20) and 01B (2011-03-24,RL20)


Thefollowingfeaturedescriptionshavebeenupdated:

LTE870:IdleModeMobilityFromLTEToCDMA/eHRPD:Parameterssectionhas
beenupdated.

Changes between version 01A (2010-12-17, RL20) and 01 (2010-10-29, RL20)


LTE665:CertificateManagementandLTE685:InfrastructuresforCertificationAuthority
(CA)andRegistrationAuthority(RA)

VendorCertificaterevocationsectionhasbeenadded
Identitymanagementserversolutionsectionhasbeenupdated
Factorytrustanchorsectionhasbeenupdated.

Issue:02B DN0978045 15

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1 Feature Descriptions RL10

1.1 Radio resource management and telecom features


from previous releases for RL20
1.1.1 LTE28: Closed loop UL power control
1.1.1.1 Introduction to the feature

ClosedloopULpowercontrolcomplementsthebasicopenloopULpowercontrol(see
chapterPowercontrolintheLinkcontrolfunctionalareadescription;UL:uplink).Itis
basedoneNodeBsmeasurementsofULsignallevelandquality.Ofthemeasurement
datatheeNodeBdeterminesanULpowerincreaseordecreasestepandcommandsthe
UE(userequipment)toincreaseordecreasethecurrentULtransmitpowerbythisstep.
OpenlooppowercontrolisbasedonpathlossestimationsoftheUEandmainlystatic
systemandO&Mparameters;itcompensateslong-termvariationsoftheradio
conditions,buttypicallysuffersfromerrorsinpathlossestimations.Theclosedloop
powercontrolstronglyimprovesthepathlossestimationsandallowsoptimizedULpower
adaption.Hence,theUEisenabledtooperatewithoptimumpowerlevelsundervarying
propagationandinterferenceconditions.
Actually,openloopULpowercontrolandclosedloopULpowercontrolarecombined
andoneformulaisusedtocalculatetheUEstransmitpowertakingintoaccountboth
openandclosedlooppowercontrolcomponents.SeparateULpoweradjustmentsare
calculatedfordifferentPUCCHformats,SRSs(soundingreferencesymbols)and
specificULallocationsonPUSCH.ClosedloopULpowercommandsaresenton
PDCCH.
Theoperatorenables/disablesandconfiguresclosedlooppowercontrolbyO&Msetting.
Thegeneralcellspecificparametersaredeliveredviasysteminformationbroadcasting
andtheUEspecificparametersaredeliveredviaRRCsignalling.
TheFlexiMultiradioBTSsupportsslowclosedloopuplinkpowercontrol.

1.1.1.2 Benefits
1.1.1.2.1 End user benefits

TheUEpowerconsumptionisreduced.
ThereductionofinterferencebyoperationwithclosedloopULpowercontroloptimizes
thetransmissionconditionswithinthecellintermsofspeechqualityand/ordatarates.

1.1.1.2.2 Operator benefits

ClosedloopULpowercontrolreducesintra-cell,inter-cellandinter-systeminterference.
Theresultsareimprovedcelledgebehaviorandarelaxationofrequirementsonintra-
cellorthogonality.

16 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.1.1.3 Requirements
1.1.1.3.1 Software requirements

Table1 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL10

eNodeB LBTS1.0

MME

SAEGW

UE 3GPPrelease8

NetAct

1.1.1.3.2 Hardware requirements

Thisfeaturedoesnotrequireanyadditionalhardware.

1.1.1.4 Functional description


1.1.1.4.1 Functional details

ClosedloopULpowercontrolisdoneasfollows:

1. TheeNodeBmeasureseveryTTI(transmissiontimeinterval)foreveryPRB
(physicalresourceblock)andforallUEs,whosesignalsarereceived,thesignal
level(RSSI,receivedsignalstrengthindicator)andquality(SINR,signal-to-
interferenceplusnoiseratio)fromPUCCHand/orPUSCHdependingontheO&M
configuration.
2. TheeNodeBprocessesthemeasurementdataby
transformingitintoatransportformatindependentformat,
clippingthemeasurementdata(alimitationofeachvalueinacertainrange
betweenaO&Mdefinedminimumandmaximumthreshold),
weightingthemeasurementdata,
filteringthemeasurementdata(averagingfilters).

3. Afterthat,theeNodeBmakesadecisionaboutPUCCHand/orPUSCHcommands
byusingadecisionmatrixwithatargetwindowforsignalqualityandlevelconfigured
byanoperator.Forexample,ifthesignalqualityandlevelisbelowthelower
thresholds,apowerincreaseisinitiated.
4. ThenewULpoweriscalculated.
5. PUCCH/PUSCH/SRSpowercommandsarethensignalledtotheUEviaPDCCH.
Thecommandcontainsthepoweradjustments(e.g.+3dBforPUSCH).

Issue:02B DN0978045 17

FeatureDescriptionsRL10 FeatureDescriptionsRL10

TheUEusestheclosedlooppowercorrectionvaluesasadditivetermtotheopenloop
componentforthecalculationofitstotaluplinktransmitpower.
ThedescribedULpowercontrolschemeisappliedseparatelyforthephysicaluplink
sharedchannel(PUSCH),physicaluplinkcontrolchannel(PUCCH)andsounding
referencesymbols(SRSs)withdifferentparametersets.TheULpowercontrolis
performedindependentlyforeachparticularUEinacell.

Measurements
TheeNodeBmeasures:

RSSI(receivedsignalstrengthindicator)ofreceivedsignalsforeveryUE
transmittingonPUCCHorPUSCHortransmittingSRS
InterferenceforeveryreceivedPUCCH/PUSCH/SRSphysicalresourceblock(PRB)
InterferenceforeveryUEtransmittingviaPUCCHorPUSCH

TheeNodeBthencalculatestherelatedSINRvaluesforthecellandforeachUE.

Power adjustment decision and determination of the power


adjustment value
SeparateULpowercontrolwindowsforthepoweradjustmentdecisionaredefinedfor
thePUSCH,SRSandPUCCHcomponents.TheULpowercontrolwindowisdefinedby
upperandlowerqualityandlevelthresholds(inatwo-dimensionalquality-levelspace
thethresholdsdefinethefieldsofadecisionmatrix).Figure1:Powercontroldecision
matrixschematicallyshowstheULpowercontroldecisionmatrixforPUSCHandfor
PUCCH.
TherequiredpoweradjustmentsteptobesenttotheUEisgiveninthefieldsofthe
matrixandiscalledPUSCHorPUCCH.

Figure1 Powercontroldecisionmatrix

SINR
good

+1dBor
-1dB -1dB
+3dB
high_qual_thresh
medium

+1dBor
0dB -1dB
+3dB

low_qual_thresh
poor

+1dBor +1dBor +1dBor


+3dB +3dB +3dB

RSSI
low medium high

low_lev_thresh high_lev_thresh

18 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

IntheformulafortheUEscalculationoftheULtransmissionpower,PUSCHisan
additivecomponent.TheULtransmissionpowerforsubframei,PPUSCH(i),usesthe
poweradaptionvaluePUSCH(i4)whichwassignalledviaPDCCH4subframesbefore
(accordingto3GPP36.213:PUSCH(iKPUSCH),andforFDDmode:KPUSCH=4).

isgivenasthecurrentcontributiontoanaccumulatedpowercorrectionsummand.In
thiscasethesummandisgivenbyf(i)=f(i1)+PUSCH/PUCCH(i4).Anotherpossibility
(describedin3GPP36.213)wouldbetogiveasanabsolute(standalone)power
correctionvalue.TheeNodeBtakescarethatsuccessivepoweruporpowerdown
commandsdonotexceedanupperandalowerabsolutepowerlimit.
SinceclosedloopULpowercontroltakesintoaccounttheSINRconditions,SINRisnot
consideredinopenloopULpowercontrol.

Transmit power control commands


TheULpoweradjustmentvaluePUSCHforPUSCHiscarriedwithinthetransmitpower
control(TPC)commandwhichissenttotheUEincombinationwiththeuplink
schedulinggrant:WheneveraUEisscheduled,itgetsaTPCcommandtogetherwith
beinginformedwhichresourcesandtransportformatisassigned.TheTPCcommandis
includedinthePDCCHwithDCIformat0.AnotherpossibilityofconveyingtheTPC
informationnotimplementedinthecurrentsolutionwouldbetousetheTPC-PUSCH
format,whichisaspecialPDCCHpayloadandcontainsjointlycodedULTPC
commandsforasetofuptoNusers.InthiscaseDCIformat3/3Awouldbeusedwhose
CRCparitybitsarescrambledwithTPC-PUSCH-RNTI.
Correspondingly,theULpoweradjustmentvaluePUCCHforPUCCHiscarriedwithinthe
transmitpowercontrol(TPC)commandwhichisalsosenttotheUEincombinationwith
theuplinkschedulinggrant.
PossiblevaluesforPUSCH/PUCCHintheaccumulationcaseare-1dB,0dB,1dB,3dB.

TheUEattemptstodecodeaPDCCHofDCIformat0withtheUE'sC-RNTIorSPSC-
RNTIandaPDCCHofDCIformat3/3AwiththisUE'sTPC-PUSCH-RNTIinevery
subframeexceptwheninDRXmode.IfDCIformat0andDCIformat3/3Aareboth
detectedinthesamesubframe,thentheUEusesthepowervalueprovidedinDCI
format0.

1.1.1.4.1.1 Messages and information elements

Messages
ULUEspecificpowercontrolparametersareincludedintheRRC:CONNECTION
RECONFIGURATIONmessage.Itcontainsinformationelementsdescribedbelow.

Information elements
TheIEUplinkPowerControlCommonandIEUplinkPowerControlDedicatedareused
tospecifyparametersforuplinkpowercontrolinthesysteminformationandinthe
dedicatedsignalling,respectively;see3GPPTS36.331.
Forexample,theIEUplinkPowerControlDedicatedisincludedinthe
physicalConfigDedicatedIEwhichisincludedintheradioResourceConfigDedicated
IE.ThelastoneisapartoftheRRC:CONNECTIONRECONFIGURATIONmessage.

Issue:02B DN0978045 19

FeatureDescriptionsRL10 FeatureDescriptionsRL10

ThephysicalConfigDedicatedIEalsocontainstheTPC-PDCCH-ConfigIEwhichis
usedtospecifytheRNTIsandindexesforPUCCHandPUSCHpowercontrol.The
powercontrolfunctioncaneitherbesetuporreleasedwiththeIE.

1.1.1.5 System impacts


1.1.1.5.1 Interdependencies between features

ClosedloopULpowercontrolcomplementsthefeatureOpenloopULpowercontrol
andDLpowersetting,seechapterPowercontrolintheLinkcontrolfunctionalarea
description.
ClosedloopULpowercontrolhaseffectsonthepacketscheduler(seethePacket
schedulerfunctionalareadescription):Thecombiningofpowercontrolandresource
allocationallowsinterferencecoordinationtofurtherenhancecelledgeperformanceand
allowshigheroverallspectralefficiency.Forexample,UEswithcomparablepathlossin
adjacentcellscanbedirectedtotransmitinthesametime-frequencyresource.On
average,suchagroupingofUEswithasimilarchannelqualityinadjacentcellsresultsin
thebestcelledgeperformance,becauseitavoidsstronginterferencefromUEscloseto
theeNodeBinadjacentcells.Viceversa,aligningUEswithdifferentchannelquality
betweencellsresultsinagoodchannelqualityfortheseUEs,hencethepeakdatarates
andtheaveragecellthroughputcanbeincreased.

1.1.1.5.2 Impacts on interfaces

Regardingtheradiointerface,thecommunicationbetweeneNodeBandUEisdonevia
RRCsignalling.CellspecificULpowercontrolparametersareincludedinthesystem
informationblocktype1(SIB1).GeneralpowercontrolparametersaresenttotheUE
duringtheInitialContextSetupRequestprocedure.ULUEspecificpowercontrol
parametersareincludedintheRRC:CONNECTIONRECONFIGURATIONmessage
(includestheradioResourceConfigDedicatedIEwhichincludesthe
physicalConfigDedicatedIE;thelastoneincludestheuplinkPowerControlDedicated
IE).

1.1.1.5.3 Impacts on performance and capacity

SinceClosedloopULpowercontrolisrelatedtointerference,thefeaturecombined
withallocationofresources(bythepacketscheduler)improvestheperformanceatcell
edgeandallowsahigheroverallspectralefficiency.

1.1.1.6 User interface


1.1.1.6.1 Parameters

Thefollowingtableshowstheparametersimplementedforthefeature.Parameters
commonforclosedloopandopenloopuplinkpowercontrolareshowninthesecond
table.

20 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table2 ParametersforclosedloopULpowercontrol

Name Object Description Range Default value

EnableClosedLoopUplink LNCEL Thisparameterallowstoenable/disable 0(false) 0


PowerControl closedloopuplinkpowercontrol.
1(true)
(ulpcEnable)

IncludePUCCH LNCEL IncludingorexcludingofRSSIandSINR 0(false) 1


MeasurementsInCLPower measurementsfromPUCCHintheclosed
1(true)
Control loopPCcomponent.
(ulpcPucchEn)

IncludePUSCH LNCEL IncludingorexcludingofRSSIandSINR 0(false) 1


MeasurementsInCLPower measurementsfromPUSCHintheclosed
1(true)
Control loopPCcomponent.
(ulpcPuschEn)

LowerRSSIThresholdFor LNCEL Lowerthresholdofthepowercontrolwindow -127...0dBm -103dBM


PUCCHPowerCommand fortheRSSI(signallevel)forPUCCH
step1dBm
Decision component.
(ulpcLowlevCch)

LowerRSSIThresholdFor LNCEL Lowerthresholdofthepowercontrolwindow -127...0dBm -103dBM


PUSCHPowerCommand fortheRSSI(signallevel)forPUSCH/SRS
step1dBm
Decision component.
(ulpcLowlevSch)

LowerSINRThresholdFor LNCEL Lowerthresholdofthepowercontrolwindow -47...80dB 1dB


PUCCHPowerCommand fortheSINR(signalquality)forPUCCH
step1dB
Decision component.
(ulpcLowqualCch)

LowerSINRThresholdFor LNCEL Lowerthresholdofthepowercontrolwindow -47...80dB 8dB


PUSCHPowerCommand fortheSINR(signalquality)forPUSCH/SRS
step1dB
Decision component.
(ulpcLowqualSch)

UpperRSSIThresholdFor LNCEL Upperthresholdofthepowercontrolwindow -127...0dBm -98dBM


PUCCHPowerCommand fortheRSSI(signallevel)forPUCCH
step1dBm
Decision component.
(ulpcUplevCch)

UpperRSSIThresholdFor LNCEL Upperthresholdofthepowercontrolwindow -127...0dBm -98dBm


PUSCHPowerCommand fortheRSSI(signallevel)forPUSCH/SRS
step1dBm
Decision component.
(ulpcUplevSch)

Issue:02B DN0978045 21

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table2 ParametersforclosedloopULpowercontrol(Cont.)

Name Object Description Range Default value

UpperSINRThresholdFor LNCEL Upperthresholdofthepowercontrolwindow -47...80dB 4dB


PUCCHPowerCommand fortheSINR(signalquality)forPUCCH
step1dB
Decision component.
(ulpcUpqualCch)

UpperSINRThresholdFor LNCEL Upperthresholdofthepowercontrolwindow -47...80dB 11dB


PUSCHPowerCommand fortheSINR(signalquality)forPUSCH/SRS
step1dB
Decision component.
(ulpcUpqualSch)

TimeIntervalForPower LNCEL TimeintervalforsendingaveragedRSSIand 10...2000ms 50ms


CommandDecisions SINRvaluestothedecisionmatrixto
step10ms
determinepowercorrectionsinclosedloop
(ulpcReadPeriod)
uplinkpowercontrol.

Table3 ParameterscommonforopenandclosedloopULpowercontrol

Name Object Description Range Default value

EnabledTBSizeImpactTo LNCEL Thisparameterenables/disablesatransport 0(false), 1


UEPUSCHPower formatdependentoffsetonaperUEbasis.In
1(true)
Calculation casethatthisparameterisenabled,PUSCH
powercalculationinUEuplinkpowercontrol
(deltaTfEnabled)
equation(P1)takesthetransportblocksizein
accountduringpowercalculation.

DeltaFPUCCHFormat1 LNCEL ThisparameterparameterdefinesthedeltaF 0(-2), 1


PUCCHFormat1.
(dFpucchF1) 1(0),
2(2)

DeltaFPUCCHFormat1b LNCEL ThisparameterparameterdefinesthedeltaF 0(1), 0


PUCCHFormat1b.
(dFpucchF1b) 1(3),
2(5)

DeltaFPUCCHFormat2 LNCEL ThisparameterparameterdefinesthedeltaF 0(-2), 1


PUCCHFormat2.
(dFpucchF2) 1(0),
2(1),
3(2)

DeltaFPUCCHFormat2a LNCEL ThisparameterparameterdefinesthedeltaF 0(-2), 1


PUCCHFormat2a.
(dFpucchF2a) 1(0),
2(2)

22 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table3 ParameterscommonforopenandclosedloopULpowercontrol(Cont.)

Name Object Description Range Default value

DeltaFPUCCHFormat2b LNCEL ThisparameterparameterdefinesthedeltaF 0(-2), 1


PUCCHFormat2b.
(dFpucchF2b) 1(0),
2(2)

FilterCoefficient LNCEL Thisparameterspecifiesthefiltering 0(fc0), 4


coefficientusedforRSRP(3GPP:TS36.331)
(filterCoeff) 1(fc1),
2(fc2),
3(fc3),
4(fc4),
5(fc5),
6(fc6),
7(fc7),
8(fc8),
9(fc9),
10(fc11),
11(fc13),
12(fc15),
13(fc17),
14(fc19)

1.1.1.6.2 Measurements and counters

Counters for: LTE CELL LOAD MEASUREMENT

Table4 Newandmodifiedcounters

Counter Number Description

TPC-1dBforPUCCH M8001CR NumberofsentTPC-1dBvaluesforPUCCH.


D900
UpdatedwhenClosedLoopULpowercommandforPUCCHwithvalue-1dBis
sentonPDCCHtoUE.

TPC-0dBforPUCCH M8001CR NumberofsentTPC0dBvaluesforPUCCH.


D901
UpdatedwhenClosedLoopULpowercommandforPUCCHwithvalue0dBis
sentonPDCCHtoUE.

TPC+1dBforPUCCH M8001CR NumberofsentTPC+1dBvaluesforPUCCH.


D902

Issue:02B DN0978045 23

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table4 Newandmodifiedcounters(Cont.)

Counter Number Description

UpdatedwhenClosedLoopULpowercommandforPUCCHwithvalue+1dBis
sentonPDCCHtoUE.

TPC+3dBforPUCCH M8001CR NumberofsentTPC+3dBvaluesforPUCCH.


D903
UpdatedwhenClosedLoopULpowercommandforPUCCHwithvalue+3dBis
sentonPDCCHtoUE.

TPC-1dBforPUSCH M8001CR NumberofsentTPC-1dBvaluesforPUSCH.


D904
UpdatedwhenClosedLoopULpowercommandforPUSCHwithvalue-1dBis
sentonPDCCHtoUE.

TPC-0dBforPUSCH M8001CR NumberofsentTPC0dBvaluesforPUSCH.


D905
UpdatedwhenClosedLoopULpowercommandforPUSCHwithvalue0dBis
sentonPDCCHtoUE.

TPC+1dBforPUSCH M8001CR NumberofsentTPC+1dBvaluesforPUSCH.


D906
UpdatedwhenClosedLoopULpowercommandforPUSCHwithvalue+1dBis
sentonPDCCHtoUE.

TPC+3dBforPUSCH M8001CR NumberofsentTPC+3dBvaluesforPUSCH.


D907
UpdatedwhenClosedLoopULpowercommandforPUSCHwithvalue+3dBis
sentonPDCCHtoUE.

1.1.1.7 Activating The Feature

Thisfeatureneedsactivation.ForinstructionsseeActivatingtheLTE28:ClosedloopUL
powercontrol.

1.1.1.8 Abbreviations
1.1.1.8.1 0Z

xxx

1.1.2 LTE30: CQI adaption (DL)


1.1.2.1 Introduction to the feature

CQI(channelqualityindicator)isanindicatorofthecurrentdownlinkchannelconditions
asseenbytheUE.InLTE,theuserequipment(UE)reportsCQIstoassisttheeNodeB
inselectinganappropriatemodulationandcodingscheme(MCS)tobeusedforthe
downlinktransmission.AhighCQIvalueisindicativeofachannelwithhighquality.The
UEdeterminestheCQIvaluefromthedownlinkreceivedsignalquality,typicallybased
onmeasurementsofthedownlinkreferencesignals.

24 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

ACQIvaluereportedfromtheUEmaynotbereliableenoughfortheeNodeBselecting
amodulationandcodingschemetoachieveacertain(low)blockerrorrate(BLER)for
downlinkdatatransmission.ThereforetheeNodeBadjuststhereportedCQIvalueby
takingintoaccountACK/NACK(acknowledged/notacknowledged)reportsfromtheUE
forreceiveddownlinkdatablocks(e.g.NACKissentiftheUEcouldnotsuccessfully
decodeareceiveddatablock).ThisprocessiscalledCQIadaptation.TheadjustedCQI
valueisusedbytheAMC(adaptivemodulationandcoding)algorithm,whichisa
componentofthelinkadaptationfunctionalitywithintheeNodeB,toselecttheoptimum
MCSforthefollowingdownlinkdatatransmission.

1.1.2.2 Benefits

CQIadaptationcompensatesuserequipmentmeasurementerrors(yieldingto
suboptimalCQIvaluesreportedtotheeNodeB)andallowstoachieveaconfigurableDL
targetblockerrorrate(BLER).

1.1.2.3 Requirements
1.1.2.3.1 Software requirements

Table5 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL09

eNodeB LBTS0.5

MME

SAEGW

UE 3GPPrelease8

NetAct

1.1.2.3.2 Hardware requirements

Thisfeaturedoesnotrequireanyadditionalhardware.

1.1.2.4 Functional description


1.1.2.4.1 Functional details

CQIadaptationistheadjustmentofthereportedCQIvalueintheeNodeBwithan
adaptedoffsetbeforelinkadaptationbyAMC(adaptivemodulationandcoding)is
appliedindownlinkdirection.
Figure2:PrincipleofCQIadaptationshowshowtheoffsetvalueCQIiscalculatedand
applied.CQIadaptationisalsocalledouterloopqualitycontrol(OLQC):AnUL
ACK/NACKreportandthefollowingDLtransmission,whoseMCSisinfluencedbythe
previousACK/NACKreportandwhichdeterminesthenextULACK/NACKreport,forma
loop.

Issue:02B DN0978045 25

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Figure2 PrincipleofCQIadaptation

Datablocks
Packetscheduler DLlinkadaptation:SelectMCS
(PDSCH)
Evaluate
reference CQIadaptation
signals CQIreport
CQIreported CQIreported+CQI=CQIcorrected
(PUCCH/PUSCH)

Decode ACK
transport CQI(t-1)+CQIstepup=CQI(t)
blocks ACK/NACK 1stDL Additionally:
transportblock CQIbetween
(PUCCH/PUSCH) transmissions CQImaxandCQImin
CQI(t-1)+CQIstepdown=CQI(t)
UE NACK eNodeB

TheCQIoffsetisdeterminedintheeNodeBwiththehelpoftheincomingACK/NACK
responsesfromtheUE(viaL1/L2controlsignaling)fortheinitialtransmissionofeach
transportblockinDLdirection.Foracorrectreceivedtransportblocktheoffsetvalue
CQIisincreasedbyastepCQIstepupwhereasforanincorrecttransportblockthevalue
isdecreasedbyCQIstepdown.NochangeisdonewhennoACK/NACKisavailableorin
caseofaretransmissionofthecorrespondingtransportblock(therearesomeother
specificconditionswhereCQIisnotchanged).
TheparametersCQIstepupandCQIstepdownarechoseninawaythatacertainblockerror
ratetargetvalue(BLERtarget)isreached.TheoffsetvalueCQIliesbetweenamaximum
andminimumvalue.

1.1.2.5 System impacts


1.1.2.5.1 Interdependencies between features

CQIadaptationiscloselyrelatedtothefeatureLTE31LinkadaptationbyAMC(UL/DL):
TheselectionoftheappropriatemodulationandcodingschemeforDLtransmissionby
theAMC(adaptivemodulationandcoding)algorithmisbasedontheadjustedCQI
value.Formoreinformation,seethefunctionalareadescriptionLinkcontrol.

1.1.2.6 User interface


1.1.2.6.1 Parameters

ThefollowingtableshowstheparametersimplementedforthefeatureLTE30:CQI
adaption(DL).

26 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Name Object Description Range Default


value

dlOlqcEnable LNCEL Thisparameterallowstoenable/disableCQI false(0) true(1)


adaption(i.e.downlinkouterlooplinkquality
control).

Otherparametersforthisfeatureareinternalorvendor-specific.

1.1.2.7 Activating The Feature

Thisfeaturerequiresactivation.ForinstructionsseeActivatingtheLTE30:CQIAdaption.

1.1.3 LTE37: Ciphering and LTE38: Integrity protection


1.1.3.1 Introduction to the feature

SecurityfortheeNodeB(asanetworkelement)isatfirsttimespecifiedby3GPPfor
LTE.Thismeans:LTEisheretheleadingradiostandard.Itisneededtoprotectthe
confidentialityoftheuserandmitigatetheeffectsofattacksonthenetwork.Inthis
document,thesecurityfortheradioaccessnetworkisdescribed(inotherwords:Theair
linksecurity).ThisfeaturedescriptionLTE37:CipheringandLTE38:Integrityprotection
consistsuserdatasecuritybetweenUEandeNodeBforradiolayer2(u-planedata)and
radiolayer3(RRC,controlplanedata).
Twofunctionsareprovidedforthemaintenanceofsecurity:Cipheringandintegrity
protection.

Cipheringisappliedonbothcontrolplanedata(RRCsignalling)anduserplanedata
anditisusedinordertoprotectthedatastreamsfrombeingeavesdroppedbya
thirdparty.PartofCipheringisalsothekeyderivationfunction(SHA-256inRL3
protocol)
Integrityprotectionisappliedoncontrolplanedataonlyandallowsthereceiverto
detectpacketinsertionorreplacement.

CipheringandintegrityprotectionwithintheaccessstratumisperformedinthePDCP
layer.TheFlexiMultiradioBTSsupportscipheringfortheuserplanePDUsandtheRRC
PDUsaccordingtothe3GPPspecificationsTS36.300,TS36.323,TS36.331and
TS36.401.
Thekeysusedforcipheringandintegrityprotectionoftraffic(data/controlsignalling)
areestablishedwhenaconnectionbetweenUEandtheeNodeB/networkisbuiltupand
theyarediscardedafterasessionhasbeenclosed(sometimeskeyscanchangewithin
asession);UEandeNodeBestablishthesamekeys.Thekeyshave128bitslengthand
arederivedfromsuperiorkeyswhichareorganizedinahierarchicalstructure.Thelast
jointkeyKASMEusedforderivationofASkeysiscalculatedintheHomeSubscriber
Server(HSS)andstoredandusedintheMMEandinasecurepartoftheUniversal
SubscriberIdentityModule(USIM)intheUE.
TheeNodesupportsthefollowingciphering/integrityprotectionalgorithms(EEA:EPS
encryptionalgorithm;EIA:EPSintegrityalgorithm):

Nullalgorithm(EEA0/EIA0providingnosecurity)

Issue:02B DN0978045 27

FeatureDescriptionsRL10 FeatureDescriptionsRL10

SNOW3G(EEA1/EIA1)
AES(EEA2/EIA2)

Acipheringalgorithmusesacipheringkey(andotherparameters)asinputtocreatea
keystreamwhichiscombinedwiththeplaintextstream.Theresultingciphereddata
streamistransmittedandthereceivergetstheplaintextbackbyapplyingthesamekey
streamontheciphereddatastreaminthesamewayasdoneduringciphering.Ciphering
isanoptionalfeature.Ifacustomerdecidesnottobuyalicenseforthisfeature,hecan
useaNULL-algorithminstead.
Anintegrityprotectionalgorithmusesanintegrityprotectionkey(andotherparameters)
asinputtocreateamessageauthenticationcodeaddedtothemessagetobesent.The
integrityprotectionisamandatoryfeature.From3GPPviewnointegrityprotectionNULL-
algorithmisavailable.Butinextensionto3GPP-completelyexplainedbytheLTSI-forum
thereaIP-NULL-algorithmisimplemented.ThisextensioncanonlybeusediftheMME
isconfiguredtodoso,suchitcannotbeusedbyaccident.

1.1.3.2 Benefits

Cipheringandintegrityprotectionintheaccessstratum(AS)providessecurityoftheair
interfaceandprotectsagainstattacksandeavesdropper.

1.1.3.3 Requirements
1.1.3.3.1 Software requirements

Table6 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL10

eNodeB LBTS1.0

MME NS10CD2

SAEGW

UE 3GPPrelease8

NetAct

1.1.3.3.2 Hardware requirements

Thisfeaturedoesnotrequireanyadditionalhardware.

28 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.1.3.4 Functional description


1.1.3.4.1 Functional overview

Figure3:C-planesecurityandFigure4:U-planesecurityshowtheoverallsecurity
conceptwithinLTE.Thesecurityarchitectureisdifferentforuserplanetrafficandcontrol
planetraffic.Hereandinfollowingsections,securityaspectsforthenon-accessstratum
(NAS)arealsoincludedinordertoshowrelationsbetweenNASandASsecurityandfor
comprehensibility.

Figure3 C-planesecurity

integrityprotected,ciphered
NAS NAS

integrityprotected integrityprotected
RRC RRC S1AP/X2AP S1AP
ciphered L3 AP ciphered

PDCP PDCP SCTP SCTP


L2 L4
... ...
IPv4/IPsec IPv4/IPsec
L3
... ...
UE eNB MME

integrity
protected,
ciphered

RRC X2AP
... ... AP:ApplicationLayer
eNB L2,L3,...:Layer2,Layer3,...

Figure4 U-planesecurity

Datastream Datastream

integrity integrity
ciphered protected protected
PDCP PDCP GTP-U GTP-U GTP-U
L2 AP ciphered ciphered
... ...
UDP UDP UDP
L4

IPv4/IPsec IPv4/IPsec IPv4/IPsec


L3 ... ...
...
UE eNB S-GW P-GW

integrity
protected,
ciphered

PDCP GTP-U
... ... AP:ApplicationLayer
eNB L2,L3,...:Layer2,Layer3,...

C-planesecurityincludesthefollowingcharacteristics:

NASsignallingprotectionistransparentfortheeNodeB.
NASsignallingiscipheredandintegrityprotectedbetweenUEandMME.
RRCintegrityprotectionandcipheringisappliedtoNASmessagescarriedbyRRC
messagesinadditiontotheNASsignallingsecuritybetweenMMEandUE.This
resultsindoubleprotectionofNASsignalling.
RRCsignallingisalwaysintegrityprotectedbyPDCPintheeNodeBandintheUE.
RRCsignallingiscipheredbetweenUEandeNodeBbyPDCP.

Issue:02B DN0978045 29

FeatureDescriptionsRL10 FeatureDescriptionsRL10

S1APsignallingiscipheredandintegrityprotectedbetweeneNodeBandMMEbyan
underlyingtransportsecuritymechanism.Thisisanseperatefeature(LTE689)and
describedtintoFAD:IPsecoperation.Itisanoptionalfeature.
X2APsignallingisprotectedinthesamewayasS1APsignalling.

ThesecuritydescribedbyLTE:37/LTE38isalwaysbetweenUEandeNodeB.Ifthereis
dataforwardingfromansource-eNodeBtoatargeteNodeBtherewillbetransport
securityactivated.

1.1.3.4.2 Security keys

Varioussecuritykeysareusedforcipheringandintegrityprotectionoftrafficdepending
onthetypeoftraffic(userdata/controlsignalling)andtherelatedstratum(NAS/AS).
FortheNAS(nonaccessstratum)theseare:

KNASencforencryptionofNASmessagesbetweenUEandMME
KNASintforintegrityprotectionofNASmessagesbetweenUEandMME

FortheAS(accessstratum;transmissionbetweenUEandeNodeB)thefollowing
securitykeysareused:

KUPencforencryptionofuserplanetraffic
KRRCencforencryptionofcontrolplanetraffic(whichisRRCsignalling)
KRRCintforintegrityprotectionofcontrolplanetraffic

Thekeysarederivedfromsuperiorkeysorganizedinahierarchicalstructure.TheAS
keysKUPenc,KRRCencandKRRCintarederivedfromKeNBwhichisrelatedtoacertain
eNodeBandwhichitselfisderivedfromthesuperiorkeyKASME.TheNASkeysKNASenc
andKNASintarealsoderivedfromKASME.Figure5:SecuritykeyhierarchyshowstheLTE
securitykeyhierarchyandkeydistributionconcept.
KASMEisavailableintheAuthenticationCenter(AuC)whichresidesintheHome
SubscriberServer(HSS)andinasecurepartoftheUniversalSubscriberIdentity
Module(USIM)intheUE;UEandeNodeBusethesameKASMEforderivingtheir
securitykeys.ASMEistheAccessSecurityManagementEntityoftheEPS(evolved
packetsystem)andislocatedintheMME.
ThekeyKwhichistheoriginofallotherkeysandthekeysCK(cipherkey)andIK
(integritykey)havenodirecteffectonRRMandarementionenedjustforcompleteness.
Otherkeysorstructuresforciphering/integrityprotectionsuchasKeNB*andNHare
describedintherelatedchapters.

30 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Figure5 Securitykeyhierarchy

UE HSS

K K

CK IK CK IK
MME
KASME KASME KASME

KNASint KeysforNASsignalling KNASint


KNASenc KNASenc
NASarea
ASarea
KeNB KeNB KeNB

eNB
KUPenc KUPenc
ASkeysfor
KRRCint KRRCint
KRRCenc C-planeand KRRCenc
U-planetraffic

Lifetime of security keys


TheexistenceofakeydependsontheEMM/RRCstateofaUEinrespectofconnection
establishment(EMM:EPSmobilitymanagement;ECM:EPSconnectionmanagement):

Kexistsalways;itistheonlypermanentkey.
TheNASkeysKASME,KNASenc,KNASintandCK,IKexistwhiletheEMM-
REGISTEREDstateisongoing.
TheASkeysKeNB,KUPenc,KRRCint,andKRRCencarecreatedonRRC-IDLEtoRRC-
CONNECTEDtransitions(correlatedwithECM-IDLEtoECM-CONNECTED
transitions)wheninEMM-REGISTEREDstate(astheUEisinEMM-REGISTERED
state,anEPSsecuritycontextalreadyexistsintheUEandtheMME)andtheyexist
duringRRC-CONNECTEDstate.
TheeNodeBdeletesthekeysafterreceivingtheS1AP:UECONTEXTRELEASE
COMMANDmessage.

Key establishment and key distribution


Thedifferentsecuritykeysareestablishedduringspecifickeyestablishmentprocedures:

AuthenticationandKeyAgreement(AKA):ThisprocedureisperformedwhenaUE
initiallyattachestothenetwork.TheMMEauthenticatesthesubscriber,andthekeys
CK,IK,andKASMEareestablished,onceintheUSIM/UE,andinthesamewayinthe
AuC/HSS.KASMEisderivedfromCK,IKandthePLMNID;theHSStransfersKASME
totheMME.AKAisaNASprocedureanddoesnothaveanyprerequisitebesides
thepermanentkeyK.

Issue:02B DN0978045 31

FeatureDescriptionsRL10 FeatureDescriptionsRL10

NASSecurityModeCommand(NASSMC)procedure:Thisprocedureisperformed
whentheUEhassuccessfullybeenauthenticated.MMEandUEgeneratetheNAS
keysKNASencandKNASintforNASsignallingsecurity.NASSMCneedsavalidKASME
asprerequisite.Inaddition,NASSMCactivatestheNASsecuritymechanisms.
KeNBestablishment:Theprocedureappliedisspecificfordifferentcases:

ForachangeofstatetoRRC-CONNECTED,KeNBisderivedintheUEandinthe
MMEfromKASMEandtheeNodeBID.TheMMEtransmitsKeNBtotheeNodeB
bytheS1AP:INITIALCONTEXTSETUPREQUESTmessage.
MMEandUEalsoderivethenexthop(NH)parameterfromtheKASME.
Foranintra-LTEintra-frequencyhandover,thesourceeNodeBcreatesKeNB*,a
transportsecuritykey,whichistransferredviaX2interfacetothetargeteNodeB
wheretheKeNBtobeusedisderivedfromtheKeNB*(formoreinformation,see
below).

ASSecurityModeCommand(ASSMC)procedure:
TheeNodeBselectsthesecurityparametersrequiredforderivingtheASsecurity
keys.TheseparametersaretransferredtotheUEviatheSECURITYMODE
COMMANDmessage.ThentheUEandeNodeBderivetheASkeysKUPenc,KRRCint,
andKRRCencfromKeNB.ThesekeysareneededforuserplaneencryptionandRRC
integrityprotectionandencryption.ASSMCneedsavalidKeNBasprerequisite.In
addition,ASSMCactivatestheASsecuritymechanisms.

Key set identifier and key change indicator


AtinitialcontextsetupASandNASsecuritystartwithacommonKASMEkey.Later,
severalKASMEmaybeknownbynetworkandUE.Forexample,whiletheRRC-
CONNECTEDstateisstillongoing,NASmayapplyanewKASME(byexecutinganother
NASsecuritymodecommand).InthiscasethereistheoldKASME,fromwhichNASand
ASkeysarestillderived,andthenewKASME,fromwhichfreshNASandASkeysshall
bederived.Therefore,aspecificparameteridentifiesaparticularKASME.Subsequentlyto
aNASchangeofKASME(whiletheASKASMEisstillused),ASfollowstheNASchange
whichincludesahandover.
TheparameteridentifyingaparticularKASMEisKSI(keysetidentifier).KSIisgenerated
togetherwithKASMEduringtheAuthenticationandKeyAgreementprocedure.Allkeys
derivedfromaKASMEinheritthisKSI(thisiswhyKSIiscalleda"set"identifier).

TheKSIissignalledatNASlevelonly,i.e.duringtheAuthenticationandKeyAgreement
procedureandNASsecuritymodecommandprocedure.AtASleveltheKSIisnot
signalled.Instead,implicitdependenciesbetweenNASandASprocedureskeeptheAS
keyssynchronousinthenetworkandtheUE:AtbeginningofASproceduresforanRRC
connection,theASusesthesameKASMEastheNAS,andASdoesnotchangethis
KASMEduringusualASkeychanges.Onlyincombinationofanintra-cellhandoverAS
maychangetheKASME.InthiscasetheKASMEchangeissignalledbyaflagcalledKCI
(keychangeindicator).

32 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Key handling in case of handover


ThetargeteNodeBgetsitsKeNBtobeusedforgeneratingitsU-planeandC-planekeys
asfollows:ThesourceeNodeBdeterminesatransportsecuritykeyKeNB*andtransmits
thiskeyviaX2interfacetothetargeteNodeB.ThenthetargeteNodeBderivesK eNBfrom
KeNB*.

OnepossibilitytodetermineKeNB*istohaveitderiveddirectlyfromthecurrentlyactive
KeNB.ThisdirectderivationofKeNB*usesacryptographichashfunction,soitisnot
feasibletoreconstructthesourceKeNBfromthenewtargetKeNB.Thereforeatarget
eNodeBdoesnotexposethesecurityofthesourceeNodeB;inotherwords:backward
securityisguaranteed.However,thereisnoforwardsecuritywhichmeansthatthetarget
eNodeBkeysarenosecretforthesourceeNodeB.
ThesecondpossibilitytodetermineKeNB*istohaveitderivedfromtheNH(nexthop)
parameterwhichwascalculatedfromtheKASME.SincethesourceeNodeBcannotre-
calculateKeNB*fromKeNB,forwardsecurityisachieved.IncaseofaS1handover,NHis
transportedfromtheMMEbytheS1AP:HANDOVERREQUESTmessageandis
immediatelyavailableforthehandover(forwardsecurityafteronehop).IncaseofX2
handover,NHistransportedbytheS1AP:PATHSWITCHACKNOWLEDGEMENT
messageandisnotavailabeforthecurrenthandover(becausethenewkeysare
alreadydeterminedatthispointintime)butforthenextone.Therefore,forwardsecurity
isreachedatnexthandover(forwardsecurityaftertwohops).
SubsequenthandoverswitheachtransportKeNB*deriveddirectlyfromthepreviousKeNB
formachainwithbackwardsecurityonly.AhandoverwherethetransportKeNB*is
derivedviaNHisthestartingpointforanotherchainwithbackwardsecurityonly.These
chainsarecountedandidentifiedwiththeNCC(nexthopchainingcounter)parameter
signalledbytheMME;NCChasthevalue0attheinitialsecuritycontextsetup.

1.1.3.4.3 Messages and information elements

Thefollowingtableshowsthemessageswhichincluderelevantsecurityinformationand
theirsecurityrelatedcontent:

Table7 Securityrelatedmessagesandinformationelements

Message Information element IE includes

RRCmessages

SECURITYMODECOMMAND securityConfigSMC securityAlgorithmConfigIE


(cipheringAlgorithmand
integrityProtAlgorithm)

RRCCONNECTIONREESTABLISHMENT ue-Identity shortMAC-I


REQUEST

RRCCONNECTIONRECONFIGURATION securityConfigHO keyChangeIndicator(notprocessedby


theeNodeB)
nextHopChainingCount

Issue:02B DN0978045 33

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table7 Securityrelatedmessagesandinformationelements(Cont.)

Message Information element IE includes

securityAlgorithmConfig
(cipheringAlgorithmand
integrityProtAlgorithm;onlynecessary
incaseofalgorithmchanges)

RRCMOBILITYFROMEUTRACOMMAND nas-
SecurityParamFromEUTR
A

S1APmessages

INITIALCONTEXTSETUPREQUEST UESecurityCapabilities HandoverPreparationinformationIE


suchascipheringandintegrity
SecurityKey
protectioninformationoftheservingcell
andthetargetCellShortMAC-I
InitialsecuritykeyKeNB

HANDOVERREQUIRED RRCContext HandoverPreparationinformationIE


suchascipheringandintegrity
protectioninformationoftheservingcell
andthetargetCellShortMAC-I

HANDOVERREQUEST RRCContext (seeabove)


UESecurityCapabilities (seebelow)
SecurityContext NHparameter
NCCrelatedtoNH.

HANDOVERCOMMAND NASSecurityParameters HandoverPreparationinformationsuch


fromE-UTRAN ascipheringandintegrityprotection
informationoftheservingcellandthe
targetCellShortMAC-I

PATHSWITCHREQUEST UESecurityCapabilities Supportedencryptionandintegrity


protectionalgorithmsintwo2-bit
representations.

PATHSWITCHREQUEST SecurityContext NHparameter


ACKNOWLEDGEMENT
NCCrelatedtoNH.

X2APmessages

HANDOVERREQUEST UEContextInformation RRCContext


UESecurityCapabilities
ASSecurityInformation(transitionkey
KeNB*andNCC)

34 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.1.3.5 System impacts


1.1.3.5.1 Interdependencies between features

AnadditionalsecurityfeatureistheoptionalLTE689LTEIPsecsupportwhichallows
secureeNodeBcontrolandsecurebulkdatacommunicationbetweeneNodeBsaswell
asbetweeneNodeBsandcorenodes.IPsecisrelatedtotransportandapplication
protocols.SupportedIPseccapabilitiesaredataintegrityprotection,originauthentication
andanti-replayprotection.

1.1.3.5.2 Impacts on network elements

Asecureenvironmentisrequiredinthenetworkelementsstoringsecuritykeys.The
FlexiMultiradioBTSprovidessuchasecureenvironment.

1.1.3.5.3 Impacts on system performance and capacity

Securitymechanismsareassociatedwithprocessingeffortandadditionalcontroldata
accordingtocommonlaws.

1.1.3.6 User interface


1.1.3.6.1 Parameters

Table8 Parametersforcipheringandintegrityprotection

Full name (Short name) Object Description Range / Step Default value

CipheringAlgorithmActivation LNBTS Thisparameterallowsto false(0),true true(1)


enable/disabletheoptional (1)
(actCiphering)
cipheringalgorithms.

CipheringAlgorithmPreferenceList LNBTS AlistofsupportedASciphering


algorithms.Thealgorithmis
(cipherPrefL)
identifiedbytheparameter
name,andtheassignedvalue
determinesthealgorithm
preference.

IntegrityProtectionAlgorithmPreference LNBTS AlistofsupportedASintegrity


List protectionalgorithms.The
algorithmisidentifiedbythe
(integrityPrefL)
parametername,andthe
assignedvaluedeterminesthe
algorithmpreference.

KeyRefreshMargin LNBTS Thisparameterdefinesa 0...429496 50000


thresholdforPDCPCOUNT 7295,
(keyRefrMarg)
supervision.Iftheremaining
step1
COUNTspacebecomesless
thanthisthreshold,theeNodeB
keyhierarchywillberefreshed.

Issue:02B DN0978045 35

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table8 Parametersforcipheringandintegrityprotection(Cont.)

Full name (Short name) Object Description Range / Step Default value

NullCipheringAlgorithmFallback LNBTS Thisparameterdeterminesifa false(0),true true(1)


fallbacktoNullcipheringcaused (1)
(nullFallback)
byeNodeBlimitationsis
accepted(true)ornot(false).

1.1.3.7 Activating The Feature

ThefeatureLTE37:cipheringrequiresactivation.ForinstructionsseeActivatingthe
LTE37:Ciphering.

1.1.4 LTE43: Support of 64 QAM in DL, LTE788: Support of 16


QAM (UL), LTE793: Support of 16 QAM (DL)
1.1.4.1 Introduction to the feature

TheoriginalbitstreamsintheeNodeBandintheUEaredigital.Tosendthemviaradio
antennatheymustbeconvertedtoanalogouswaveform.Thisisdonebymodulation.
ThebasicmodulationmethodisQPSKforrobusttransmissiononPUSCHandPDSCH.
OntoptherearehigherordermodulationswithQAM(quadratureamplitudemodulation)
-whicharethecontentofthisfeaturedescription.
Thisfeaturedescriptioncomprisesthefollowingfeatures:

LTE793:Supportof16QAM(DL)
LTE788:Supportof16QAM(UL)
LTE43:Supportof64QAMinDL

1.1.4.2 Benefits

Thebenefitsofthefeaturesare:
16QAM:Increaseofthepeakrateby100%comparedtoQSPK,around70%increased
spectralefficiency.
64QAM(DL):IncreaseoftheDLpeakrateby50%ascomparedto16QAMscenario.

Figure6:Throughputfordifferentmodulationschemesgivesashortoverviewofthe
throughputofdifferentmodulationschemes.Thefigureisvalidforabandwidthof
20Mhz.

36 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Figure6 Throughputfordifferentmodulationschemes

1.1.4.3 Requirements
1.1.4.3.1 Software requirements

Thefollowingsoftwareisrequiredforthesefeatures:

Table9 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL09

eNodeB 64QAM:LBTS0.5,16QAM:

UE 3GPPrelease8

1.1.4.3.2 Hardware requirements

Thisfeaturedoesnotrequireanyneworadditionalhardware.

Issue:02B DN0978045 37

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.1.4.4 Functional description


1.1.4.4.1 Functional details

Quadratureamplitudemodulation(QAM)isoneofthewidelyusedmodulationschemes,
whichchanges(modulates)theamplitudeoftwoothogonalsinusoidalcarrierwaves
dependingontheinputbitsasfollows

whereI(t)andQ(t)arethemodulatingsignalamplitudes,fisthecarrierfrequency.
Inagraphicalrepresentation(I-Q-plane)theI-andQ-amplitudesarearrangedina
squaregridwithequalverticalandhorizontalspacing.
16QAMconsistsofa4x4gridof(I,Q)-points,64QAMconsistsofa8x8grid.

Figure7 QAMmodulation

16QAM 64QAM
4bits/symbol 6bits/symbol
Q Q

I I

IncaseofdownlinkdirectiontheQAM(both16QAMand64QAM)isusedbylink
adaptionandcodingforPDSCH(physicaldownlinksharedchannel),incaseofuplink
directionthe16QAMisusedbyadaptivemodulationforPUSCH(physicaluplinkshared
channel).

1.1.4.5 System impacts


1.1.4.5.1 Interdependencies between features

LTE31:LinkadaptationbyAMCdescribeshowQAMisdeployedbylinkadaption.

1.1.4.6 Sales information

Thesefeaturesareoptional.

38 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.1.4.7 User interface


1.1.4.7.1 Managed objects

ThemanagedobjectclassLNCELisused.Attributeofitistheparameter
dl64QamEnable.ParentofLNCELisLNBTS.

1.1.4.7.2 Parameters

Table10 ParametersforLTE43:Supportof64QAMinDL

Name Object Description Range Default value

dl64QamEnable LNCEL Enables/disablesdownlink64QAM false,true


modulationforlinkadaptationuseinPDSCH.

1.1.4.7.3 Measurements and counters

ThefollowingcountersaredefinedforthefeatureLTE43:Supportof64QAMinDL

Table11 CountersforLTE43

Network element name Database ID Description

HarqAck16QAM_Dl 47244 DownlinkHARQAcksreceived.

HarqOkRetr1_16QAM_Dl 47247 DL-SCHTBsacknowledgedatthe1st


retransmission.

HarqOkRetr2_16QAM_Dl 47251 DL-SCHTBsacknowledgedatthe2nd


retransmission.

HarqOkRetr3_16QAM_Dl 47255 DL-SCHTBsacknowledgedatthe3rd


retransmissionorlater.

HarqSizeOrig16QAM_Dl 47261 TotalsizeoforiginaltransmissionsofDL-


SCHTBs.

HarqSizeRetr16QAM_Dl 47264 TotalsizeofretransmissionsofDL-SCH


TBs.

HarqSizeOk16QAM_Dl 47258 TotalsizeofacknowledgedDL-SCHTBs.

TbSchOrig16QAM_Dl 47270 NumberoforiginalHARQtransmissions


oftransportblocksonDL-SCH.

TbSchRetr16QAM_Dl 47273 NumberofHARQretransmissionsof


transportblocksonDL-SCH.

Issue:02B DN0978045 39

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table11 CountersforLTE43(Cont.)

Network element name Database ID Description

TbSchNoHarq16QAM_Dl 47267 Numberoftransmittedtransportblockson


DL-SCHwithoutHARQ.Fortheseblocks,
theHARQcountersshallnotbeupdated.

HarqAck64QAM_Dl 47245 DownlinkHARQAcksreceived.

HarqOkRetr1_64QAM_Dl 47248 DL-SCHTBsacknowledgedatthe1st


retransmission.

HarqOkRetr2_64QAM_Dl 47250 DL-SCHTBsacknowledgedatthe2nd


retransmission.

HarqOkRetr3_64QAM_Dl 47253 DL-SCHTBsacknowledgedatthe3rd


retransmissionorlater.

HarqSizeOrig64QAM_Dl 47259 TotalsizeoforiginaltransmissionsofDL-


SCHTBs.

HarqSizeRetr64QAM_Dl 47262 TotalsizeofretransmissionsofDL-SCH


TBs.

HarqSizeOk64QAM_Dl 47256 TotalsizeofacknowledgedDL-SCHTBs.

TbSchOrig64QAM_Dl 47268 NumberoforiginalHARQtransmissions


oftransportblocksonDL-SCH.

TbSchRetr64QAM_Dl 47271 NumberofHARQretransmissionsof


transportblocksonDL-SCH.

TbSchNoHarq64QAM_Dl 47265 Numberoftransmittedtransportblockson


DL-SCHwithoutHARQ.Fortheseblocks,
theHARQcountersshallnotbeupdated.

HarqAckQPSK_Dl 47246 DownlinkHARQAcksreceived.

HarqOkRetr1QPSK_Dl 47249 DL-SCHTBsacknowledgedatthe1st


retransmission.

HarqOkRetr2QPSK_Dl 47252 DL-SCHTBsacknowledgedatthe2nd


retransmission.

HarqOkRetr3QPSK_Dl 47254 DL-SCHTBsacknowledgedatthe3rd


retransmissionorlater.

HarqSizeOrigQPSK_Dl 47260 TotalsizeoforiginaltransmissionsofDL-


SCHTBs.

HarqSizeRetrQPSK_Dl 47263 TotalsizeofretransmissionsofDL-SCH


TBs.

40 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table11 CountersforLTE43(Cont.)

Network element name Database ID Description

HarqSizeOkQPSK_Dl 47257 TotalsizeofacknowledgedDL-SCHTBs.

TbSchOrigQPSK_Dl 47269 NumberoforiginalHARQtransmissions


oftransportblocksonDL-SCH.

TbSchRetrQPSK_Dl 47272 NumberofHARQretransmissionsof


transportblocksonDL-SCH.

TbSchNoHarqQPSK_Dl 47266 Numberoftransmittedtransportblockson


DL-SCHwithoutHARQ.Fortheseblocks,
theHARQcountersshallnotbeupdated.

1.1.4.8 Activating The Features

Thessfeaturesrequireactivation.ForinstructionsseeActivatingtheLTE793:Supportof
16QAM(DL),ActivatingtheLTE788:Supportof16QAM(UL),ActivatingtheLTE43:
Supportof64QAMinDL.

1.1.4.9 Abbreviations
1.1.4.9.1 0Z

3GPP

thirdgenerationpartnershipproject

AMC

adaptivemodulationandcoding

CQI

channelqualityindicator

DL

downlink

HARQ

hybridautomaticrepeatrequest

LBTS

landbasedtestside

Issue:02B DN0978045 41

FeatureDescriptionsRL10 FeatureDescriptionsRL10

LTE

longtermevolution

MCS

modulationandcodingscheme

MIMO

multipleinputmultipleoutput

PDSCH

physicaldownlinksharedchannel

PUSCH

physicaluplinksharedchannel

QAM

quadratureamplitudemodulation

QPSK

quadraturephaseshiftkeying

Rc

Ratecodeforchannelcoding

UE

userequipment

UL

uplink

SCH

synchronizationchannel

SNIR

signaltonoiseandinterferenceratio

TB

transportblock

42 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

TTI

transmissiontimeinterval

1.1.5 LTE69: Transmit diversity for two antennas and LTE70:


Downlink adaptive open loop MIMO for two antennas
1.1.5.1 Introduction to the feature

Thefollowingfeaturesoffersolutionsrelatedtomulti-pathdownlinktransmissions.As
MIMO(MultipleInputsMultipleOutputs)isoneofthekeyfeaturesofLTE,techniquesfor
downlinkadaptiveopenloopMIMOandtransmissiondiversityarepresented.
ByapplyingthefeatureLTE70:DownlinkadaptiveopenloopMIMOfortwoantennas,the
eNodeBselectsdynamicallybetweenSpaceFrequencyBlockCoding(SFBC)transmit
diversityandOpenLoopSpatialMultiplexingwithLarge-delayCyclic Delay
Diversity(Large-delayCDD).
WhenusingthefeatureLTE69:Transmitdiversityfortwoantennas,theeNodeB
transmitseachdatastreamvia2TXdiversitypaths,andtheSpaceFrequencyBlock
Codemodeisapplied.DiversitymethodsarecomplementingthebasicfeatureLTE187:
SingleTXpathmode,wheretheTXsignalistransmittedviaasingleTXantennaper
cell,eitherduetoHWconfigurationorinsemi-staticmodeselectedbyO&MforHW
configurationswithtwoTXpathspercell.

1.1.5.2 Benefits

Inthefollowingsection,benefitsforoperatorsandendusersaresummarizedwith
regardtothefollowingfeatures:

LTE69:Transmitdiversityfortwoantennas
LTE70:DownlinkadaptiveopenloopMIMOfortwoantennas

1.1.5.2.1 End user benefits

Thementionedfeaturessupportradiolinks,offeringhighdataratesandsignalquality.

1.1.5.2.2 Operator benefits

BythefeatureLTE69:Transmitdiversityfortwoantenna,cellcoverageandcapacityare
enhancedbythetransmitdiversityoftwoantennas.
ThefeatureLTE70:DownlinkadaptiveopenloopMIMOfortwoantennasprovideshigh
peakrates(usingtwocodewords)andgoodcelledgeperformance(usingasinglecode
word)bytheadaptivealgorithm.
Furthermore,doublestream2x2MIMOspatialmultiplexing(openloop)canbeusedfor
smallcellswithlowloadiftheUEcapabilitiesaresufficient.

1.1.5.3 Requirements

ForthefeaturesLTE70:DownlinkadaptiveopenloopMIMOfortwoantennasand
LTE69:Transmitdiversityfortwoantennas,thefollowinghardwareandsoftware
requirementshavetobemet.

Issue:02B DN0978045 43

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.1.5.3.1 Software requirements

ThefeaturesLTE69andLTE70requireRL09software.

1.1.5.3.2 Hardware requirements

ThefeaturesLTE70andLTE69requireparticularhardwaretosupportradiodiversity
techniques:

ForLTE70:DownlinkadaptiveopenloopMIMOfortwoantennas,theeNodeBand
theUEsupportMIMO.UEswhicharenotMIMOcapableshallusedlMimoMode=1.
ForLTE69:Transmitdiversityfortwoantennas,theeNodeBhastobeequippedwith
twoantennasatleast.

UEsasdefinedin3GPPrelease8complywiththeserequirements.

1.1.5.4 Functional description


1.1.5.4.1 Functional overview

BymeansofthefeatureLTE70:DownlinkadaptiveopenloopMIMOfortwoantennas,
theeNodeBisabletoselectdynamicallybetweenSpaceFrequencyBlockCoding
(SFBC)TransmitDiversityandOpenLoopSpatialMultiplexingwithLarge-delay
CyclicDelayDiversity(Large-delayCDD).Openloopspatialmultiplexingisoffered
withtwocodewordswithLarge-delayCDDforthePDSCH(PhysicalDownlinkShared
Channel)onUEbasis.
UsingthefeatureLTE69:Transmitdiversityfortwoantennas,theeNodeBtransmits
singledatastreamsvia2TXdiversitypaths.Furthermore,eachdatastreamis
transmittedbytwodiversityantennaspersector,andSpaceFrequencyBlockCoding
(SFBC)TransmitDiversityisapplied.Diversitymethodscomplementthebasicfeature
LTE187:SingleTXpathmode.

1.1.5.4.2 Downlink adaptive open loop MIMO for two antennas

BymeansofthefeatureLTE70:DownlinkadaptiveopenloopMIMOfortwoantennas,
theeNodeBisabletoselectdynamicallybetweenSpaceFrequencyBlockCoding
(SFBC)TransmitDiversityandOpenLoopSpatialMultiplexingwithLarge-delay
CyclicDelayDiversity(Large-delayCDD).Openloopspatialmultiplexingisoffered
withtwocodewordswithLarge-delayCDDforthePDSCHonUEbasis.Theopenloop
dynamicMIMOswitchfunctionalitycanbeenabledanddisabledoncelllevelbymeans
ofO&M.WhenthedynamicMIMOswitchisdisabled,eitherstaticmultiplexingorstatic
transmitdiversitycanbeselectedforthewholecell(allUEs).Thedynamicswitchtakes
intoaccounttheUEsspecificlinkqualityandrankinformation.Furthermore,theUE
radiocapabilitiesareconsideredandadditionaloffsetsforCQIreportingcompensation
areprovidedwithregardtothedynamicMIMOswitchingfunctionality.
MIMOisakeytechnologyinachievingtheambitiousrequirementsforthroughputand
spectralefficiencyfortheLTEairinterface.MIMOreferstotheuseofmultipleantennas
atthetransmitterandatthereceiver.FortheLTEdownlink,a2x2configurationfor
MIMOisassumedasbaselineconfiguration,i.e.twotransmitantennasatthebase
stationandtworeceiveantennasattheterminalside.Configurationswithfourtransmit
orreceiveantennasarealsosupportedbyLTERel-8.Differentgainscanbeachieved
dependingontheMIMOmodethatisused.

44 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table12:MultiantennaoptionsinLTEgivesanoverviewonthetypicalLTEmulti
antennaconfigurations:

Issue:02B DN0978045 45

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table12 MultiantennaoptionsinLTE

DL UL Configuration type

BS UE Gain to smaller UE BS Gain to smaller


configuration configuration
TX RX TX RX

1x2 1 2 1x2 1 2 minimum

2x2 2 2 +4..5dBDLlinkbudget 1x2 1 2 standard


+100%peakdatarate
+userexperience
+10%spectrumefficiency

ThestandardconfigurationoftheLTEbasestationprovidesinadditionto2RX
antennas(RXdiversity)2TXchains,whichhastheadvantageinthatnoextraantenna
andfeedercostisnecessarycomparedtotheminimum1TXchain.Inahigh
performancescenario,4RXantennasattheLTEbasestationsubstantiallyenhancethe
LTEuplinkpathbutrequireadditionalantennaandfeedereffortandcosts.Typically,the
LTEUEisequippedwith2RXantennasand1TXchain.

1.1.5.4.2.1 Receive diversity

NSNsupports2-branchandplanstosupport4-branchreceivediversitybasedonMRC
(MaximumRatioCombining).MRCaimsatcombiningthe2(or4)receivesignalsinsuch
awaythatthewantedsignal'spowerismaximizedcomparedtotheinterferenceandthe
noisepower,i.e.theSINR(SignaltoInterfererandNoiseRatio)isenhanced.
Comparedtoasinglereceivebranch,2-branchreceivediversityallowsfor:

coherencelinkbudgetgainof3dB
additionaldiversitylinkbudgetgainofsomedBdependingonmanyconditions
includingvelocity,fadingchannelandcarrierbandwidth
linkbudgetgainfromMRCatabout10%BlockErrorRate(BLER)mayreachupto6
dB(asshowninsimulations)

Correspondingly,4-branchreceivediversitywillshowacoherencelinkbudgetgainof6
dBplussomedBadditionaldiversitylinkbudgetgain.
Receivediversitywithtworeceivebranchesrequirestwouncorrelatedreceiveantennas
usingasinglecross-polarantennaortwoverticallypolarizedspatiallyseparated
antennas;4-branchreceivediversityrequiresfouruncorrelatedreceiveantennasusing
e.g.2spatiallyseparatedcross-polarantennas.
ReceivediversitycomplieswithLTERel-8terminalsandissupportedonalluplink
channels.

1.1.5.4.2.2 Transmit diversity

NSNsupports2-branchandplanstosupport4-branchtransmitdiversity.

46 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

IfthetotaleNodeBtransmitpowerkeepsthetransmitpowerpertransmitbranchashigh
asforthesingletransmitantennacase,thelinkbudgetisincreasedby3dBfortwo
branchesandby6dBforfourbranches.Thisimpliescoverageandcapacity
enhancements.
IfthetotaleNodeBtransmitpowerisconstant(comparedtothesingletransmitbranch
case),transmitdiversityleadstomorerobustlinksatthecelledgewhileslightlyreducing
cellcapacity.However,forDRX(DiscontinuousReception)VoIPusers,transmitdiversity
slightlyenhancescellcapacitybyapproximately5%fortwotransmitbranches.
Transmitdiversitymaybesemi-staticallyconfiguredpercell,whilefornon-MIMOUEs,
dlMimoMode=1forPDSCHisautomaticallyselected.

1.1.5.4.2.3 Downlink open loop MIMO

ThetypicalMIMOconfigurationencompassingdualcodeword2x2DLSU(Single-User)
MIMOSpatialMultiplexingisillustratedinthefigurebelow.ThisMIMOschemetargetsa
duplicationofthedownlinkpeakuserdataratebymeansoftwoindependentparallel
datastreamstoasingleUE.ThisisalsocalledSpatialMultiplexing.Thetwobase
stationtransmitsignals,twoUEreceivesignals,andfourchannelsform(foreach
subcarrier)asystemoftwoequationswithtwounknowntransmitsignals.Thetwo
unknowntransmitsignalscanbeachievedbychannelestimation,possibletransmit
alphabet(s),andthetworeceivesignals.

Figure8 2x2MIMOconfiguration

Transmissionof2independentdatastreamstransmittedatthesametimedependson
thechannelssignalqualityandthedecorrelationofbothchannels.Correlationofthe
channelsisdeterminedbytheantennacharacteristics.
Forexampleantennasareuncorrelatedifthey:

arespatiallyseparatedbyabout10ormorewavelengths,or
useorthogonalpolarizationplanes(cross-polarity),or
arelocatedinadiffuseenvironment.

Byuncorrelatedantennasdiversityandspatialmultiplexinggainscanbeachieved,and
coherencegainstosomeextent.
Forexampleantennaelementsarecorrelatedifthey:

arephasedbywavelengthspacing,
havealowangularspread,and
arelocatedinanon-diffuseenvironment(e.g.ontherooftop).

Issue:02B DN0978045 47

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Correlatedantennaseasilyproviderobustcoherencegains(theclassicalbeamforming
gain),butnospatialmultiplexingordiversitygain.
ForOpen Loop SU-MIMO Spatial Multiplexing, UEfeedback,likePMIandRIis
required.Mappingofdatatothetransmitantennaportsisfixedandthesystemcannot
beinfluenced.IftheconditionsforSpatialMultiplexingnotgoodenough,however,the
UEmayrequesttolowerthetransmissionrankandultimatelyfallsbackto
dlMimoMode=1.
Forinteroperabilityreasons,theOpenLoopSU-MIMOschemehastobebasedonthe
Large-delayCyclicDelayDiversity(Large-delayCDD)precoding.Theoptimum
unitaryprecodingmatrixisselectedbymeansofapredefinedcodebookwhichisknown
ateNodeBandUEside,andbytheUEsradiochannelestimate.Operatorsmay
(statically)configurewhetheracellsupportsTransmitDiversity,orMIMOSpatial
Multiplexing,orallowsforanadaptivemode.Intheadaptivemode,theOpenLoop2x2
SU-MIMOfallbackisSpaceFrequencyBlockCoding(SFBC)TransmitDiversity.
Inidealsituations,2x2SU-MIMOduplicatesthepeakuserdatarate.Forrealistic
conditions,2x2SU-MIMOenhancescellcapacityby10%formacro-cellularandby40%
formicro-cellulardeploymentscenarios.
ThecurrenteNodeBhardwaremeetsthephasenoiseortheminimumjitterrequirements
(<60ns)betweenLTEbasebandprocessingandantennaconnectorsrequiredforMIMO
schemeswithuncorrelatedantennas.

1.1.5.4.3 Transmit diversity for two antennas

UsingthefeatureLTE69:Transmitdiversityfortwoantennas,theeNodeBtransmitseach
datastreamvia2TXdiversitypaths.Eachdatastreamistransmittedbytwodiversity
antennaspersector,andSpaceFrequencyBlockCoding(SFBC)TransmitDiversityis
applied.Thetransmitdiversitymodecanbeusedformostphysicaldownlinkchannels,
exceptforthesynchronizationsignals,whicharetransmittedonlyviathefirstTX
antenna,andexceptwhentheeNodeBsenddifferentcell-specificreferencesignalsper
antenna.Theoperatorcanenablethesemi-statictransmitdiversitymodeoncellbasis.
DiversitymethodscomplementthebasicfeatureLTE187:SingleTXpathmode,where
theTXsignalistransmittedviaasingleTXantennapercell.Here,thesingleTXpath
modecanbeappliedfortwoscenariosdependentontheHWconfigurationofthe
eNodeB:EitherforHWconfigurationswithonlyoneTXpathpercellorforHW
configurationswithtwoTXpathspercellwherethesecondTXpathisdisabledbyO&M.
Thelatterscenarioisprimarilyintendedfortrialingpurpose.Inthiscase,thesame2-
pathHWconfigurationsupportsenhancedoperationalmodesofTXdiversityorMIMO.
TheoperatorcanselecttheTXmodesemi-staticallyoncellbasisbytheO&M
configuration.ThesingleTXpathpercellmodeisthebasictransmitsolutionwithout
spatialdiversityintheeNodeB.Asinglepatternofsymbolsforcell-specificreference
signalsissentindownlinkdirection.Inuplinkdirection,2RXpathspercellarealways
supportedbytheeNodeB.

1.1.5.4.4 Open loop spatial multiplexing

Forsmallcellswithlowload,doublestream2x2MIMOspatialmultiplexing(openloop)
canbeusediftheUEcapabilitiesaresufficient.Otherwise,dlMimoMode=1hastobe
selected.

48 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.1.5.5 System impacts

ByintroductionofthefeaturesLTE70:DownlinkadaptiveopenloopMIMOfortwo
antennasandLTE69:Transmitdiversityfortwoantennas,thefollowing
interdependenciesandimpactsarerelevant:

1.1.5.5.1 Interdependencies between features

ThefollowingfeaturesarerequiredforLTE70:DownlinkadaptiveopenloopMIMOfor
twoantennas:

LTE30:CQIadaptation
LTE899:Antennalinesupervision
LTE69:Transmitdiversityfortwoantennas.

ForLTE69:Transmitdiversityfortwoantennas,theTXpathactivationordeactivation
canbeperformedonlyifMIMOorTXfeaturesareenabled.
ThefeaturesLTE187:SingleTXpathmode,LTE69:Transmitdiversityfortwoantennas,
LTE70:DownlinkadaptiveopenloopMIMOfortwoantennas,andLTE703:Downlink
adaptiveclosedloopMIMOfortwoantennasarerelatedtoeachotherastheyare
configuredbythesamemanagementparameterdlMimoMode.

1.1.5.5.2 Impacts on interfaces

C-plane,U-planeandotherRRMfunctionshavetocontaindatafortheMIMOmodeor
fortheantennaconfigurationandsettings.

1.1.5.5.3 Impacts on network and network element management tools

TheeNodeBantennaconfigurationhastocompriseatleasttwoantennasifMIMOis
applied.
OpenloopMIMOhastotakeintoaccounttheUEcapabilities.UEswhicharenot
capabletosupportMIMOshallusedlMimoMode=1,i.e.diversity,inMIMO
configurations.

1.1.5.5.4 Impacts on system performance and capacity

Bydiversitymethods,thechannelcapacityisenhanced,evenformorerestrictiveradio
channelconstraintswithregardtoBLERandSINRforinstance.

1.1.5.6 Sales information

ThefeatureLTE70:DownlinkadaptiveopenloopMIMOfortwoantennasisaessential
partforLTE,release8functionality.DiversitytechniquesareprovidedalsobyLTE69:
Transmitdiversityfortwoantennas.

1.1.5.7 User interface

ByintroductionofthefeatureLTE70:DownlinkadaptiveopenloopMIMOfortwo
antennas,newparametersandcountersareavailable.

Issue:02B DN0978045 49

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.1.5.7.1 Managed Objects

Thischapterisnotrelevantforthefeature.

1.1.5.7.2 Parameters

ThefollowingtabledisplaystheparametersimplementedforthefeatureLTE70:
DownlinkadaptiveopenloopMIMOfortwoantennas.BydlMimoMode,diversitymodes
canbeselected.Fordynamiccontroloftherespectivemode,thresholdswithregardto
theCQIandthecodingmatrixrankareintroduced,bothcomprisingvaluesfora
hysteresisloop.

Table13 ParametersforLTE70:DownlinkadaptiveopenloopMIMOfortwo
antennas

Name Object Description Range Default


value

dlMimoMode LNCEL "TheusedDLmimomodeforeach SingleTX(0),TXDiv


physicalchannelisthefollowing:0:Single (1),StaticOpenLoop
StreamDownlink:Alldownlinkphysical MIMO(2),Dynamic
channelsaretransmittedusingthismode; OpenLoopMIMO(3)
1:SingleStreamDownlinkTransmit
Diversity:Alldownlinkphysicalchannels
aretransmittedusingthismode;2:Dual
StreamMIMOSpatialMultiplexing:SRB1
(DCCH)andRBs(DTCH)onPDSCHare
transmittedusingDualStreamMIMOwith
spatialmultiplexing;SRB0(CCCH),
BCCHandPCCHonPDSCHandall
otherphysicalchannelsaretransmitted
usingSingleStreamDownlinkTransmit
Diversity;3:DynamicOpenLoopMIMO:
SRB1(DCCH)andRBs(DTCH)on
PDSCHaretransmittedusingeither
SingleStreamDownlinkTransmit
DiversityorDualStreamMIMOwith
spatialmultiplexingdependingonradio
conditions;SRB0(CCCH),BCCHand
PCCHonPDSCHandallotherphysical
channelsaretransmittedusingSingle
StreamDownlinkTransmitDiversity;"

mimoOlCqiThD LNCEL CQIthresholdforfallbacktoOpenLoop 0...16,step0.1


MIMOdiversity.

mimoOlCqiThU LNCEL CQIthresholdforactivationofOpenLoop 0...16,step0.1


MIMOSpatialMultiplexing.

mimoOlRiThD LNCEL RankthresholdforfallbacktoOpenLoop 1...2,step0.05 1.4


MIMOdiversity.

mimoOlRiThU LNCEL RankthresholdforactivationofOpen 1...2,step0.05 1.6


LoopMIMOSpatialMultiplexing.

50 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Note:Theparametersaresubjecttochange.

1.1.5.7.3 Alarms

Therearenorelevantalarmsforthisfeaturedefinedinthisrelease.

1.1.5.7.4 Measurements and counters

NorfortheLTE70:DownlinkadaptiveopenloopMIMOfortwoantennasneitherfor
LTE69:TransmitDiversityforTwoAntennas,thereareadditionalcounters.

1.1.5.8 Activating the Feature

Thisfeaturerequiresactivation.ForinstructionsseeActivatingtheLTE69:Transmit
diversityfortwoantennasandLTE70:DownlinkadaptiveopenloopMIMOfortwo
antennas.
Thisfeaturerequiresdeactivation.ForinstructionsseeDeactivatingtheLTE69:Transmit
diversityfortwoantennasandLTE70:DownlinkadaptiveopenloopMIMOfortwo
antennas.

1.2 Transport and transmission features from previous


releases for RL20
1.2.1 LTE713: Synchronous Ethernet
1.2.1.1 Introduction to the Feature

TheLTE713:SynchronousEthernetdifferentiationfeatureprovidesbasestation
frequencysynchronizationfromtheEthernetinterfaceasperG.8261.Synchronizationis
extractedfromanEthernetsignalwhichisprovidedtotheFlexiTransportsub-module.
ThisrequiresthatallnodesinthedistributionchainsupportstheSynchronousEthernet
featureasperG.8261.SynchronizationthroughtheLTE713:SynchronousEthernet
featureisapplicableonlyforFDDsystems.

1.2.1.2 Benefits

SynchronizationfromtheEthernetinterfaceeliminatestheneedforaGPSreceiverat
theeNBsiteifTDMbasedsynchronizationorothersynchronizationmethodsarenot
available.SynchronousEthernetprovidessynchronizationinaTDM-likedeterministic
manner.

1.2.1.3 Requirements
1.2.1.3.1 Software Requirements

Thefollowingsoftwareisrequiredforthisfeature:

Issue:02B DN0978045 51

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table14 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL10

eNB LBTS1.0

MME -

SAEGW -

1.2.1.3.2 Hardware Requirements

ThisfeaturerequiresFlexiTransportsub-moduleswhichsupportLTE.

1.2.1.4 Functional Description

SynchronousEthernetisoneofthepossiblefrequencyreferencesourcesforaneNB.
WiththeLTE713:SynchronousEthernetfeatureactivated,SynchronousEthernetas
specifiedinITU-TRecommendationsG.8261,G.8262andG.8264canbeusedfor
distributingahighqualitysynchronizationreferenceintheEthernettransport
environment.
WithSynchronousEthernet,thetimingreferenceistraceabletoaPrimaryReference
Clock(PRC).
TheFlexiMultiradioBTSLTEisHW-preparedforlaterupgradewhichallowstogenerate
theclockfortheradiointerfacecardsfromanEthernetinterface,usingSynchronous
EthernetaccordingtoITU-TG.8261.ThisupgrademightrequireadditionalHWtobe
installedeventhoughitisintendedtore-useexistingHW.
ThewanderofthetimingreferenceshallbeinlimitsspecifiedfortrafficinterfacesinITU-
TRecommendationG.823.ForNorthAmericandigitalhierarchy,thewandershallbein
limitsspecifiedfortrafficinterfacesinITU-TRecommendationG.824.
InadditiontosynchronizationinterfacesmentionedinITU-TRecommendationsG.823
andG.824,anEECinterfacecanbeusedasreferenceforSynchronousEthernet.Inthis
case,thewandershallbeinthelimitsspecifiedforEECinterfacenetworklimitsinITU-T
RecommendationG.8261,chapter9.2.1.

1.2.1.4.1 Synchronization Status Messages (SSM)

Synchronizationstatusmessagescarrytheinformationaboutthequalityofincoming
SyncEreferencesignal.
TheFlexiMultiradioBTSLTEsupportsthereceptionofSSMsasspecifiedinITU-T
RecommendationG.8264section10.SinceaneNBalwaysrepresentsthelastnodein
synchronizationdistributionchain,itisnotrequiredforittosendSSMs.
TheeNBconsidertheEthernetsignalasavalidsynchronizationsourceiftheQuality
Level(QL)containedinthereceivedSSMmessagesisoneofthefollowing:

PRC(PrimaryReferenceClock),

52 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

SSU(SynchronizationSupplyUnit)
PRS(PrimaryReferenceSource).

AnidealsituationoccurswhenthereferenceprovidesPRC/PRStraceableclockand
indicatesthiswithSSMcontainingQL=PRC/PRStraceable.
ThecustomerneedstomakesurethatthelowerqualityofSyncEreferencesignal(SSU-
AorSSU-B)isgoodenoughforfrequencysynchronization.
Infaultconditions,someoftheclocksinthesynchronizationdistributionchainmayenter
hold-overmodeorfree-runmodeandtheeNBreceivesSSMQLDoNotUse(DNU)or
DonotUseforSync(DUS).Consequentlythereferencesignalisnotusedas
synchronizationsourcesignalanymoreandtheeNBtriestoswitchtoanalternative
synchronicationsource.TheeNBraisesanalarm.
TheoperationmodeforSynchronousEthernetcanbeswitchedbetweenoperationwith
andwithoutSSMsupport.ThedefaultsettingisoperationwithSSMsupport:

Inoperation with SSM support,validSSMsarecontinuouslyreceivedthroughthe


SynchronousEthernetcapableEthernetinterface.ThepurefactthatanSSMis
receivedataSynchronousEthernetcapableinterfacealreadytellsthattheincoming
signalisSynchronousEthernetsignal.AnalarmisgeneratedifnovalidSSMis
receivedwithinacertaintimeinterval(ssmTimeoutparameter),orwhenforexample
theeNBreceivesQLDoNotUse(DNU).Inthiscase,theSyncEreferencesignalis
nolongerusedassynchronizationsourcesignal.
Inoperation without SSM support,theEthernetsignalisstillsynchronizedtothe
networkreference(PRC)anditispossibletorecovertimingfromanEthernet
interfacethatistraceabletothePRC.Analarmisgeneratedwhenthesignalatthe
Ethernetinterfaceislost.
WithoutSSMsupport,thenetworkplanningandtheconfigurationofthenetwork
mustbedoneverycarefully.ThereisahighriskofmisconfigurationandtheEthernet
signalmaynotcarrytimingreferencetraceabletothePRC.
WithoutSSMsupport,itisalsoimpossibletosignalthehold-overmodeorfree-run
modeofintermediatenodesinasynchronizationdistributionchain.

1.2.1.5 Sales Information

ThisfeaturebelongstoASW.

1.2.1.6 User Interface


1.2.1.6.1 Parameters

Table15:ParametersrelatedtotheLTE713:SynchronousEthernetfeatureshowsthe
parametersrelatedtotheLTE713:SynchronousEthernetfeature.

Table15 ParametersrelatedtotheLTE713:SynchronousEthernetfeature

Name Object Description Range Default


value

synchroSourceList STPG Thisisthelistofsynchronizationsourcesof - -


theeNB.

Issue:02B DN0978045 53

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table15 ParametersrelatedtotheLTE713:SynchronousEthernetfeature(Cont.)

Name Object Description Range Default


value

ssmEnabled STPG ThisparameterenablesSSMsupport Boolean true


(SynchronizationStatusMessage)for
SynchronuousEthernet.

ssmTimeout STPG Thisisthemaximumdurationinsecondsfor 2...10seconds,step1 5s


whichtheactualSSMvaluemaybelessthan seconds
acceptableclockqualityorforwhichSSMs
arenotreceivedatall.Ifthedurationis
surpassed,analarmwillberaised.

1.2.1.6.2 Alarms

ThissectionlistsalarmsrelatedtotheLTE713:SynchronousEthernetfeature.
TherearenoalarmsfortheLTE713:SynchronousEthernetfeature.

1.2.1.6.3 Measurements and Counters

ThissectionlistsmeasurementsandcountersrelatedtotheLTE713:Synchronous
Ethernetfeature.
TherearenomeasurementsandcountersfortheLTE713:SynchronousEthernet
feature.

1.2.1.7 Activating and Configuring the Feature

Foractivatingandconfiguringthefeature,seeFeatureActivationDocumentation.

1.2.2 LTE132: VLAN based traffic differentiation


1.2.2.1 Introduction to the Feature

TheLTE132:VLANbasedtrafficdifferentiationfeatureprovidesthesupportoftraffic
differentiationonlayer2.TheFlexiMultiradioBTSLTEinsertsVLANIDs(IEEE802.1q)
intopacketheadersofegresstraffic,basedontheirtraffictype(U/C/M/S-plane).The
traffic-type-to-VLANmappingtableisconfigurable.EachVLANisassociatedwitha
dedicatedIPaddressattheevolvednodeB.

1.2.2.2 Benefits

ThisfeaturesupportsvirtuallyseparatenetworksforUser,Control,Managementand
SynchronizationPlane.DifferenttypesoftrafficcanberoutedthroughdifferentL2
networkpaths,withdifferentQoScapabilities.

54 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.2.2.3 Requirements
1.2.2.3.1 Software Requirements

Thefollowingsoftwareisrequiredforthisfeature:

Table16 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL10

eNB LBTS1.0

MME -

NetAct OSS5.2CD3

SAEGW -

1.2.2.3.2 Hardware Requirements

ThisfeaturerequiresFlexiTransportsub-moduleswhichsupportLTE.

1.2.2.4 Functional Description

Trafficdifferentiationcaninprinciplebeperformedonseverallayers:

L3:UsingdifferentIPsubnets
L2:UsingdifferentVLANs
EachVLANisterminatedwithadedicatedIPaddressattheeNB.
L1:Usingdifferentphysicalpaths
L1trafficdifferentiationrequiresmultiplephysicalinterfacesofanNE.Thisisnot
supportedinthecurrentrelease.

VLANbasedtrafficdifferentiationisanoptionalfeature.TheeNBsupports1,2,3,or4
VLANsifthefeatureisenabled,andonesingleVLANifthefeatureisdisabled.ULand
DLtrafficarealwayscarriedinthesameVLAN.Thefollowingmaximumnumbersof
VLANsaresupportedpereNB:

Table17 SupportednumbersofVLANs

VLAN Main usage Number of PHB Associated IP network


queues interface

VLAN#1 mainlyforU-plane;optionally 6 IPnetworkinterface#1


alsoforC-,M-andS-plane

VLAN#2 C-plane 1 IPnetworkinterface#2

Issue:02B DN0978045 55

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table17 SupportednumbersofVLANs(Cont.)

VLAN Main usage Number of PHB Associated IP network


queues interface

VLAN#3 M-plane 1 IPnetworkinterface#3

VLAN#4 S-plane(TimingoverPacket) 1 IPnetworkinterface#4

VLANbasedtrafficdifferentiationcanbeusedforvariouspurposes.First,theremaybea
needtoseparatetrafficofdifferentplanes(eNBapplications)fromeachotherfornetwork
planningreasons.Forexample,M-planetrafficmayneedtobeseparatedfromU/C/S-
planetraffic.Or,trafficmaybesplitintomultiplepathswhichhavedifferentQoS
capabilities(pathselection).
TheFlexiMultiradioBTSLTEinsertsVLANIDs(IEEE802.1q)intopacketheadersof
egresstraffic,basedonthetraffictype(U/C/M/S-plane).Themappingtableis
configurable.EachVLANisassociatedwithadedicatedIPaddressattheevolvednode
B.

1.2.2.4.1 Network Scenarios with VLAN based Traffic Differentiation

ThefollowingnetworkscenariosforVLANbasedtrafficdifferentiationaresupported:

Multipoint-to-multipoint VLANs
Inthisscenario,theVLANsareoperatedinamultipoint-to-multipointconfiguration.In
termsoftheMetroEthernetForum,theVLANprovidesan"E-LANservice".Eachofthe
VLANs(uptofour)isidentifiedbyasingleVLANidentifier(VLANID)whichisconfigured
identicallyinalleNBsandalsointheVLANGW.DependingontheX2configuration,the
X2trafficcanbeswitchedbetweendifferenteNBsdirectlyintheEthernetnetwork,or
routed(intheIPlayer)intheVLANGWorintheSEG.IfIPsecisemployed,X2
interfaceshavetobeset-upasanIPsecstar,seeX2interfaceviaIPsecStar
Configuration.

Figure9 Multipoint-to-multipointVLAN

56 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Point-to-point VLAN
InthisscenariotheVLANsareoperatedinapoint-to-pointconfiguration.Intermsofthe
MetroEthernetForum,theVLANprovidesan"E-LINEservice".EachVLANisidentified
byanindividualVLANIDwhichisconfiguredataeNBsandattheVLANGW.Point-to-
pointVLANrequiresmoreconfigurationeffortthanmultipoint-to-multipointVLANbut
allowsmorefine-grainedtrafficmanagementonaper-linkbasis.

Figure10 Point-to-PointVLAN

Toavoidexcessiveconfigurationeffort,separate(direct)Point-to-PointVLANsbetween
individualeNBsfortheX2interfaceshavebeenprecluded.
DependingontheX2configuration,X2trafficcanberoutedintheVLANGWorthe
SEG.IfIPsecisemployed,X2interfaceshavetobeset-upasanIPsecstar,seeX2
interfaceviaIPsecStarConfiguration.Inbothscenarios,theendpointsoftheVLANsat
theeNBareidentifiedbyseparateIPaddresses.

1.2.2.4.1.1 X2 interface via IPsec Star Configuration

TheeNBsupportsX2interfacestowardsupto32adjacenteNBnodes.AnX2interface
comprisesanX2_Cinterface(signaling)andanX2_Uinterface(userdata).
InscenarioswithoutIPsec,thetrafficbetweenapairofeNBscanbeswitched/routed
directlybytheswitches/routersofthetransportnetwork.IfIPsecisusedontheX2
interfaces,allX2trafficiscarriedviatheSecurityGateway(SEG).Figure11:IPsecstar
configurationshowstheprincipleofthisIPsecstarconfigurationforX2:

Issue:02B DN0978045 57

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Figure11 IPsecstarconfiguration

TheeNBtransportsubsystemusesasingleIPsectunnelpairtowardstheSEGforall
X2_Ctrafficto/fromitsadjacenteNBs,andasingleIPsectunnelpairtowardstheSEG
forallX2_Utrafficto/fromitsadjacenteNBs.IfaneNBusesacommonaddressforC-
andU-plane,thetransportsystemcombinestheX2_CandX2_UtrafficinasingleIPsec
tunnelpairwhichisdedicatedtoallX2interfaces.
TheX2packetsaremappedintooneoftheoutgoingX2IPsectunnelsbasedontheir
destinationIPaddress.ApacketismappedtoanIPsectunnelifitsdestinationaddress
(thatis,eithertheC-orU-planeaddressofanadjacenteNB)matchesapreconfigured
subnetaddress.YoucanconfigureonesubnetaddressfortheCPaddressesofalleNBs
andonesubnetfortheUPaddressesofalleNBs.Thesubnetaddressesmustbe
preconfiguredwhentakinganeNBintoservice.TheaddressrangeoftheCPsubnet
(AdjeNBCPSubnetAddress)mustincludetheCPaddressesofalleNBswhichmight
becomeadjacenteNBs.Similarly,theaddressrangeoftheUPsubnet(AdjeNBUP
SubnetAddress)mustincludetheUPaddressesofalleNBswhichmightbecome
adjacenteNBs.
TheX2packetsaresenttotheSEGthrough(oneof)thededicatedX2IPsectunnel(s).
IntheSEG,thereceivedX2packetsaredecrypted.Theapplicationlevelpacketsare
thenforwardedtotheappropriateDLIPsectunnelbasedontheirdestinationIPaddress
(theSEGhasdedicatedX2IPsectunnelpairstoalleNBs,andthusitalsohasthe
CP/UPaddressesofalleNBs).TheX2packetsareIPsecencryptedandsenttothe
addressedeNB.

1.2.2.4.2 VLAN based Traffic Differentiation: Mapping of DL Packets in the Security


Gateway

WhenusingVLANbasedtrafficdifferentiation,theSecurityGatewaysupportsmapping
oftheDLpacketsintouptofourIPsectunnelstowardseacheNB.OneseparateIPsec
tunnelisneededperVLAN.

58 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.2.2.4.3 VLAN based Traffic Differentiation: Mapping of DL Packets in the VLAN


Gateway

TheVLANGateway(attheborderoftheL3andL2networks)supportsterminationofthe
layer2,includingVLANfunctionality.TheVLANGatewaysupportsterminationofupto
fourVLANstowardseacheNB.TheDLpacketsaredistributedovertheVLANsbased
ontheDestinationAddresscontainedintheIPheader.

1.2.2.5 Sales Information

Table18 SalesInformation

BSW/ASW Licensecontrol in network element License control attributes

ASW - -

1.2.2.6 User Interface


1.2.2.6.1 Parameters

Table19:ParametersrelatedtotheLTE132:VLANbasedtrafficdifferentiationshowsthe
parametersrelatedtotheLTE132:VLANbasedtrafficdifferentiationfeature.

Table19 ParametersrelatedtotheLTE132:VLANbasedtrafficdifferentiation

Name Object Description Range/step Default value

vlanIfNetId IVIF ThisparameteridentifiestheVLAN 1...5 1


interfaceobject.Valueis1to5.Upto
step:1
5VLANsmayexistontheBTS.The5th
VLANisusedbyLTE491:FlexiPacket
RadioConnectivity.

localIpAddr IVIF ThisparameterspecifiestheIPaddressof 7...15characters -


theVLANnetworkinterfacetowardsthe
externaltransportnetwork.Itis
accompaniedwithasubnetmask.
Tobeenteredindotteddecimalformat.

netmask IVIF Thisparameterspecifiesthenetworkmask 7...15characters -


fortheIPaddressoftheVLANnetwork
interfaceintheexternaltransportnetwork.
Tobeenteredindotteddecimalformat.

vlanId IVIF ThisparameterspecifiestheVLAN 0...4094 -


identifiernumberoftheVLANnetwork
step:1
interface.

sir IVIF Thisparameterholdstheshaper 100...1.000.000kbps, 1.000.000kbps


informationrateforaspecificvlaninterface.
step:100kbps

Issue:02B DN0978045 59

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table19 ParametersrelatedtotheLTE132:VLANbasedtrafficdifferentiation
(Cont.)

Name Object Description Range/step Default value

sbs IVIF Thisparameterholdstheshaperburstsize 1522...2.000.000octets, 1522octets


foraspecificvlaninterface. step:1octet

qosEnabled IVIF ThisparameterspecifiesifmultiplePHB 0(false),1(true) false


queuesareusedoverthisVLANinterface
oronlyasingleone.MultiplePHBqueues
allowDSCPbasedtrafficpriorisation.

wfqSchedQueu IVIF Thisistheweightvaluetobeusedinthe 1..10000 1000


eWeight WFQaggregationschedulerforthisVLAN
step:1
interface.

wfqSchedQueue IEIF Thisistheweightvaluetobeusedinthe 1..10000 1000


Weight WFQaggregationschedulerforthisVLAN
step:1
interface.

vlanMapId IVMP IdentifieroftheVLANMap 1 1

vlanMap IVMP Structureof"vlanMap" - -

ulTrafficPath IVMP NumberoftheUL-trafficpaths 1...4 -

vlanPtr IVMP ReferencetothecorrespondingVLANi.e. - -


MOI IVIF

1.2.2.6.2 Alarms

ThissectionlistsalarmsrelatedtotheLTE132:VLANbasedtrafficdifferentiationfeature.
TherearenoalarmsfortheLTE132:VLANbasedtrafficdifferentiationfeature.

1.2.2.6.3 Measurements and Counters

Table20:CountersfortheLTE132:VLANbasedtrafficdifferentiationshowsthe
measurementsandcountersrelatedtotheLTE132:VLANbasedtrafficdifferentiation
feature.

Table20 CountersfortheLTE132:VLANbasedtrafficdifferentiation

Counter Number Description

ifInPackets15 M51127C0 ThenumberofIPpacketsreceivedonthe


VLANinterfacethatweredeliveredtohigher-
layerprotocols.

ifInOctets15 M51127C1 Thetotalnumberofkilo-octetsreceivedonthe


VLANinterface,includingframingcharacters.

60 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table20 CountersfortheLTE132:VLANbasedtrafficdifferentiation(Cont.)

Counter Number Description

ifOutPackets15 M51127C2 ThenumberofIPpacketsthatwere


successfullytransmittedovertheVLAN
interface.

ifOutOctets15 M51127C3 Thetotalnumberofkilo-octetstransmittedover


theVLANinterface,includingframing
characters.

ifInErrors15 M51127C4 Thenumberofinboundpacketsthatcontained


errorspreventingthemfrombeingdeliverableto
ahigher-layerprotocol.

ifOutDroppedPackets M51127C5 Thenumberoftotaloutboundpacketsthatwere


droppedintheIPschedulerduetocongestion.

ifOutDroppedOctets M51127C6 Thenumberoftotaloutboundkilo-octetsthat


weredroppedintheIPschedulerdueto
congestion.

1.2.2.7 Activating and Configuring the Feature

Foractivatingandconfiguringthefeature,seeFeatureActivationInstruction

1.2.3 LTE134: Timing over packet


1.2.3.1 LTE134: Timing over Packet
Introduction to the feature
TheTimingoverPacket(ToP)solutionconsistsofaTimingMaster(ToPMaster)atthe
coresite,andTimingSlaves(ToPSlaves)implementedintheeNBs.Themasterandthe
slavescommunicatethroughtheIEEE1588v2protocol.TheToPMastersends
synchronizationmessagesviatheEthernet/packetnetworktotheslaves.TheToP
Slavesrecoverthesynchronizationreferencefromthesemessages.

1.2.3.1.1 Benefits

TheLTE134:TimingoverPacket(ToP)featureprovidesCAPEX/OPEXsavings,as
separateTDMlinksorGPSreceptionarenolongerneededforprovidingafrequency
synchronizationreferencefortheeNBs.ThefeaturerequiressufficientEthernet/packet
networkqualityintermsoflowframe/packetdelayvariation.

1.2.3.1.2 Requirements

Software requirements
Thefollowingsoftwareisrequiredforthisfeature:

Issue:02B DN0978045 61

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table21 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL10

eNB LBTS1.0

MME -

SAEGW -

Hardware requirements
ThisfeaturerequiresFlexiTransportsub-moduleswhichsupportLTE.

1.2.3.1.3 Functional Description

Timing-over-Packet(ToP)isoneoftheavailablemethodstosupportsynchronizationifa
FlexiMultiradioBTSLTEisconnectedthroughIP/Ethernetbackhaul.TheToPsolution
consistsofaMasterClock(ToPMaster)atthecoresiteandSlaveClocks(ToPSlave)
implementedintheeNBs.Masterandtheslavescommunicatethroughsynchronization
messagesviatheEthernet/IPnetwork.Theslavesrecoverthesynchronizationreference
fromthesemessages.Thissynchronizationisrequiredtomaintainastablefrequencyof
theeNBsairinterface.
TheTimingoverPacketsolutionisbasedontheIEEE1588-2008standard.All
supportedIEEE1588-2008functionsandfeaturesarecompliantwiththisstandard.

1.2.3.1.3.1 ToP Master

ThecurrentToPsolutionsupportsonesingleTPMasterwhichmaybesupplementedby
aredundantelement.
TheeNBToPSlavesareconfiguredwiththeIPaddressoftheToPMaster(Unicast
discoveryasspecifiedinclause17.5ofIEEE1588-2008).

ToP Master Redundancy


Formorereliability,theToPMastermaysupportredundancy.IftheprimaryToPMaster
fails,theredundantToPMasteristakenintoserviceandtakesovertheIPaddressthat
waspreviouslyused.Atanygiventime,onlyoneToPMaster,eithertheprimaryorthe
redundantone,maybeactive.
SeenfromtheeNBToPslave,thereisonesingleIPaddressunderwhichitfindsthe
(oneandonly)ToPMasterthatisactiveinthesystem.Afteraswitch-overfromprimary
toredundantToPMaster,theeNBToPSlavehastoresolvetheMACaddressofthe
activeToPMaster.

1.2.3.1.3.2 ToP Slave

TheeNBToPSlaverecoversthetimingreferencebasedonthemessagingbetweenit
andtheToPMaster.TheToPSlavegeneratesanindicationwhenitisoutoflock.The
maximumvaluefortheToPSlavelockingtimeis15min.

62 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

ThelockingtimeachievedwithacertainSYNCpacketratedependsonthepacketdelay
variationinthenetworkbetweenMasterandSlave.Highpacketdelayvariationmaylead
tolongerlockingtimes.

1.2.3.1.3.3 Support of IEEE 1588 Event Messages

IEEE1588-2008specifiesasetofmessagesofvarioustypes.Forfrequency
synchronization,onlytheSYNCeventmessageisrequired.IEEE1588eventmessages
aretimedmessages,thatis,atimestampisgeneratedbothattransmissionandreceipt
ofthemessage.SYNCeventmessagesareusedtogenerateandcommunicatethe
timinginformationneededtosynchronizetheToPSlaves.
ApartfromtheSYNCeventmessage,masterandToPSlavesalsosupportthefollowing
IEEE1588generalmessages:

Signalingmessage
SignalingmessagesareusedforunicastnegotiationbetweenToPMasterandToP
Slaves.
ANNOUNCEmessage
ANNOUNCEmessagesareusedtoestablishthesynchronizationhierarchy.Another
purposeofthismessageistofindthebestmasterclockunderuseoftheBest
masterclockalgorithm,whichintheLTEsystemisirrelevantsincethereisonlyone
ToPMaster.

ThemessagesareexchangedusingthePTP(PrecisionTimeProtocol)protocol,which
iscarriedinaprotocolstackthathasPTPoverUDPoverIP.TheUDPsourceand
destinationportsare

319foreventmessages
320forunicastgeneralmessages

OntheIPlayer,thetime-to-livefieldofIPpacketsusedforToPmessagesissetto255.
TheQoSmechanismimplementedintheLTEsystemalsosupportsDiffServforToP
traffic.Bydefault,theDSCPvalueforpacketswithToPtrafficissetto46,whichis
mappedtothehighestper-hop-behavior,EF(ExpeditedForwarding).
1.2.3.1.3.3.1 UnicastNegotiation
UnicastnegotiationservestoinitiateandmaintainaunicastconnectionbetweenToP
MasterandaToPSlave.Throughunicastnegotiation,aToPSlaverequeststheToP
MastertotransmitunicastSYNCandANNOUNCEmessagestoit.Thisisdoneby
exchangingRequest_Unicast_TransmissionandGrant_Unicast_TransmissionTLVs
(type,length,valuemessages):

1. TheToPSlavesendsasignalingmessagecontainingthe
Request_Unicast_TranmissionTLVwhichincludestherequestedmessagetype
(SYNCorANNOUNCE),rateandtherequesteddurationofunicasttransmission:
TheSYNCmessageratecanbechosenbetween8/s,16/sand32/s,witha
defaultof16/s.Inhigh-qualitynetworks,lowermessageratescanbeused.
TheRL10eNBusesafixedvalueof300sasthedurationofUnicast
transmissionintheRequest_Unicast_TransmissionTLV.
TheANNOUNCEmessagerateissettoafixedvalueof0.5/s(thatis,onceper2
s).

Issue:02B DN0978045 63

FeatureDescriptionsRL10 FeatureDescriptionsRL10

2. TheToPMasterconfirmstherequestedunicasttransmissionwitha
Grant_Unicast_TransmissionTLVwhichcontainsthegrantedmessagerateandthe
grantedduration.Iftherequestedmessageratecannotbeprovided,theToPMaster
rejectstherequestbysettingthedurationfieldto0.

Onceaunicasttransmissionisset-up,theToPSlavereceivesmessagesuntilthegrant
durationexpires.TheToPSlaverequestsanewUnicastgrantwellbeforethecurrent
grantdurationhasexpired.IfnoUnicastgrantisreceived(forexamplebecauseof
transportfailures),theToPSlaverepeatsitsrequestafteratimeoutof5s.Itrepeatsthe
requesttwomoretimesifnograntisreceived.Ifstillnograntisreceived,theToPSlave
raisesanalarm.

1.2.3.1.4 Management data

Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table22:ParametersrelatedtotheLTE134:Timingoverpacketfeatureshowsthe
parametersrelatedtotheLTE134:Timingoverpacketfeature.

Table22 ParametersrelatedtotheLTE134:Timingoverpacketfeature

Name Object Description Range Default

administrativeState TOPIK UsedtolockandunlocktheTOPobjectinstance. locked(0), -


Lockingtheobjectdeactivatesitandsupresses unlocked(1)
allitsalarms.

logMeanSyncValue TOPIK ThisindicateshowoftenaToPsyncmessage -5...-3,step1 -4


shallbesendbytheToPmasterwithinthe
transmissiondurationrequestperiod.(The
transmissiondurationrequestperiodiscurrently
fixedto300seconds.)Thefollowingvaluesare
defined:

-3:8persecond
-4:16persecond
-5:32persecond

64 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table22 ParametersrelatedtotheLTE134:Timingoverpacketfeature(Cont.)

Name Object Description Range Default

masterIpAddr TOPIK IPaddressoftheToPmaster.Format:thisisan 7...15characters -


IPv4IPaddressindotteddecimalform.
Examples:
IPv4:10.12.11.0

topId TOPIK ThisparameteridentifiestheTimingOverPacket 1...1,step1 -


configurationoftheFTM.Thevalueisalways1.

1.2.3.1.5 Sales information

Table23 Salesinformation

BSW/ASW License control in network element License control attributes

ASW - -

1.2.3.1.6 Activating and configuring the feature

Foractivatingandconfiguringthefeature,seeFeatureActivationDocumentation.

1.3 Operability features from previous releases for


RL20
1.3.1 LTE150: LTE OAM Transport Layer Security (TLS) Support
1.3.1.1 Introduction to the feature

ThisfeatureenablessecureO&McontrolandbulkdatacommunicationbetweenEvolved
NodeB(eNB)andBTSSiteManager,NetAct,orothermanagementsystem.The
featureincludesaPKIinfrastructurebyutilizingsecureprotocolssuchasTransport
LayerSecurity(TLS).ThefeaturealsobringsCAPEXsavings,asthereisnoneedto
investinanyexternalHW.AppliedtogetherwithLDAP,TLStakescareofconfidential
usercredentialexchange.

1.3.1.2 Benefits

ThisfeatureoffersenhancedriskmanagementbecauseofimprovedRANnetwork
security.ItalsooffersCAPEXsavingsbynotrequiringinvestmentintoanyexternalHW.

Issue:02B DN0978045 65

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.3.1.3 Requirements
1.3.1.3.1 Software requirements

Thefollowingsoftwareisrequiredforthisfeature:

Table24 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL10

eNB LBTS1.0

MME -

SAEGW -

NetAct OSS5.2CD3

1.3.1.3.2 Hardware requirements

Thisfeaturehasnoparticularhardwarerequirements.

1.3.1.4 Functional description for LTE OAM Transport Layer Security (TLS)
Support

ThisfeatureincreasesthesecurityoftheinterfacesoftheEvolvedNodeB(eNB)
towardstheBTSSiteManagerinterfaceandiOMSbyencryption,integrityprotectionand
serverauthentication,whichareprovidedbytheTransportLayerSecurityProtocol(TLS)
andfurtherprotocolssuchasHTTPorLightweightDirectoryAccessProtocol(LDAP)
runningontopofit.UnsecureprotocolssuchasFTParenolongerused.TLSisa
securecommunicationmethodforprotectingtheconfidentialityandintegrityof,for
example,Java,HTTPandLDAPbasedO&Mtraffic.TLSisalsousedforauthenticating
theseservicesandthehostsandtheserversthatprovideaservice.eNBandiOMS
supportTLSversion1.0[RFC2246].
Indetail,thefeatureintroducesthefollowingfunctions:

DigitalcertificatesaccordingtoX.509v3formatareusedtomutuallyauthenticatethe
eNB,theBTSSiteManager,andnetworkserverssuchasNetAct.
Dataencryptionisusedtoprohibitbothinternalandexternalhostileattacks.iOMS
andeNBencryptalltrafficthatissentviaBTSO&M.
SecureO&Minterfaces
O&MmessagesandcommandsareencryptedandintegrityprotectedbyTLS.Data
suchasusernamesandpasswordsisnottransferredasplaintext.
BulkdatatransferisencryptedandintegrityprotectedbyHTTPS.
TheLDAPinterfaceforuserauthenticationandprovisionofpermissioninformation
forauserissecuredbyTLS.

TLS(similartoSecureSocketLayerProtocol,SSL)providesencryptionand
authenticationmechanisms,andconsistsoftwolayers:

66 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

TheTLSrecordprotocolprovidesencryptionandintegrityprotectionofthemessage
exchange.
TheTLShandshakeprotocolprovidesmutualauthenticationofthecommunication
peersbymeansofdigitalcertificates.Inthisprocess,thecertificatesCAsignature
andlifetimearevalidated.Thismutualauthenticationpreventsman-in-the-middle
andmasqueradeattacks.

LDAP secured with TLS


TheNetActcentralizeduserauthenticationandauthorization(CUAA)applicationand
otherservicesusetheLDAPinterfacetoauthenticateauserandtofetchpermission
informationforauser.InsecureconnectionsontheLDAPlinkbetweentheBTSandthe
LDAPserversleadtoasituationwhereauser'susernameandpasswordaretransferred
inplaintextacrosstheO&Mnetwork.ThisisnolongerthecasewiththesecureLDAP
feature,wherebytheLDAPinterfaceissecuredbymeansofTLS,usingAES-128
encryptionandtherelatedintegrityprotectionaccordingtoLDAPv3asspecifiedinRFC
4513.

LDAP operation modes


UsingtheldapConnectionTypeparameter,theeNBcanbeconfiguredtoallow
towardsLDAPservers:

onlysecuredLDAPconnections,or
bothsecuredandunsecuredLDAPconnections.

Ifbothsecureandinsecureconnectionsareallowed,theeNBattemptstoestablisha
securedLDAPconnectionfirst.IftheLDAPserverdeniesthesecureconnection,the
eNBtriestoestablishaninsecureconnection.

TLS operation mode in the eNB


TransportLayerSecurityintheeNB(omsTLSparameter)canbeconfiguredas:

Probing (Secure/Unsecure)
BothsecureandunsecureO&MconnectionsareallowedbetweentheiOMSandthe
eNB.Iftheconnectionsetuptobothsecureandinsecureportsfails,theeNBstarts
theconnectionprocedurefromthebeginning,thatis,ittriestoestablishsecure
connectionfirst.Thissettingshouldbeusedforonlyfortransitionfrominsecureto
secureBTSO&Minterfacewithoutlimitingtheconnectivity.Fromthesecuritypointof
view,itisrecommendednottousethissettingpermanently.
Forced
OnlysecureO&MconnectionsareestablishedbetweeniOMSandeNB.
Off
OnlyunsecureO&MconnectionsareestablishedbetweeniOMSandeNB.Thisis
thedefaultsetting.

g Makesuretohavetheconfigurationmatchedbetweentheoperationmode
settingsintheeNBandtheiOMS.Ifthesettingsdiffer,theeNBmightnotbe
abletoconnect,butwillcontinuetryingtoconnecteventhoughtheiOMS
connectionportisclosed.

InsecureandsecureO&MconnectionsareestablishedonseparateTCPports.By
enablingordisabling(openingorclosing)theseports,secureandinsecureconnections
canbeactivatedanddeactivated.

Issue:02B DN0978045 67

FeatureDescriptionsRL10 FeatureDescriptionsRL10

BTS O&M protocol (OM) security mode in iOMS


TheTLSModeOMparameteriniOMScanbeconfiguredas:

Forced
OnlysecureO&Mprotocolconnectionareestablished.TheiOMSandtheeNBuse
theTLS_RSA_WITH_AES_128_CBC_SHAciphersuite.Theinsecureport(8002)is
closed.
Probing (Secure/Unsecure)
BothsecureandunsecureO&Mprotocolconnectionsareallowed.Bothsecureand
insecureportsareopen.WhentheparametervalueischangedfromOffto
Probing,theiOMSresetstheport8002totriggertheeNBchangefrominsecureto
secureconnection.
Off
OnlyunsecureO&Mprotocolconnectionsareallowed.Thesecureport(8003)is
closed.

File Transfer (FT) security mode in iOMS


ForfiletransferbetweeniOMSandeNBthereisaseparateparameter(TLSModeFT)
whichcanbeconfiguredas:

Forced
Onlysecurefiletransfersareallowed.
TheiOMSandtheeNBusetheTLS_RSA_WITH_RC4_128_SHAciphersuite.
Thesecureport(443)isopen.Insecureportsareclosed(FTP20,HTTP80).
Thisisthedefaultvalue.

Probing
BothsecureandinsecurefiletransfersareallowedbetweeniOMSandeNB.
Securefiletransferistriedfirst.FiletransfersbetweeniOMSandNetActarein
securemodeonly.
Bothsecureandinsecureportsareopen.

Off
Onlyinsecurefiletransfersareallowed.
Bothsecureandinsecureportsareopen.

ThefiletransfersbetweeneNBandiOMSdependsontheBTSO&Minterfacestate.If
theinterfacestateissecure,thenthefiletransferisalsosecure.
Ifthenegotiatedfiletransferprotocolsallowbothinsecureandsecurefiletransfers,and
thefiletransferattemptsfrombothsecureandinsecureportsfails,theclientdoesnot
retry,butabortstheprocedure.

Authentication and encryption of TLS connections


TheeNBauthenticatespeerapplicationswithdigitalcertificatesaccordingtoX.509v3
andencryptsalltrafficthatissentviaTLSlinks.
ThesameeNBdevicecertificateisusedtoauthenticatetowardsIPSecandTLSpeers.

68 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Parallel usage of TLS and other secure transport protocols


Dependingonthetransportnetworkconfigurationandthenumberofnetwork
managementlocationsandapplicationstobeaddressed,TLS(oneormoreinstances)
aloneortogetherwithothersecuretransportprotocolslikeIPseccanbeusedand
configuredinparallel.Forinstance,itispossibletorunTLSwithinacommonIPsec
tunnel.

1.3.1.4.1 Secure BTS Site Manager connection

TheBTSSiteManager(BTSSM)triestoestablishonlysecureconnectiontoaneNB.
TheBTSSM(actingasTLSclient)authenticatestheeNB(actingasTLSserver)with
eNBscertificate;theeNBauthenticatestheBTSSMuserwithusernameandpassword.
BoththeBTSSMandtheeNBusetheTLS_RSA_WITH_AES_128_CBC_SHAcipher
suiteforsecureconnection.
IftheeNBcertificatevalidationfailsinBTSSM,theBTSSMasksfortheuserpermission
tocontinueestablishingasecureconnection(eveniftheeNBcertificateisunknownto
BTSSM).Theunknowncertificateis:

anoperatorendentitycertificatethatcannotbevalidatedbyBTSSM(forexample,
becausetheoperatorrootCAcertificateisnotconfiguredinBTSSM),
anNSNvendorcertificate(whichcannotbevalidatedbyBTSSM),
aneNBself-signedcertificate(whichcannotbevalidatedbyBTSSM).

Iftheuseraccepts,asecureconnectionisestablished.Iftheuserdeclines,the
connectionisclosed(noinsecureconnectionsbetweenBTSSiteMangerandeNBare
possible).

1.3.1.5 System impact


1.3.1.5.1 Interdependencies between features

LTE665:LTECertifcateManagementprovisioningofacommoncertificatehandling.

1.3.1.5.2 Impact on interfaces

Thisfeaturehasnoimpactoninterfaces.

1.3.1.5.3 Impact on network and network element management tools

Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

1.3.1.5.4 Impact on system performance and capacity

Thisfeaturehasnoimpactonsystemperformanceorcapacity.

1.3.1.6 Sales information

ThisfeaturebelongstoBSW.

Issue:02B DN0978045 69

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.3.1.7 Parameters for LTE150: LTE OAM Transport Layer Security (TLS)
Support

Table25:ParametersforLTE150:LTEOAMTransportLayerSecurity(TLS)Support
showsparametersrelatedtoLTE150:LTEOAMTransportLayerSecurity(TLS)Support.

g AfterchangingparametersaBTSrestartisnecessary.

Table25 ParametersforLTE150:LTEOAMTransportLayerSecurity(TLS)Support

Full name Object Description Range / Default


Step value
(Short name)

LDAPServerTLS AMGR ThisparameterholdstheTLS TLS(0),


accessmode accessmodefortheLDAP TLS_OR_PL
server(s)oftheBTS.Thepossible AIN_TEXT
(
valuesare:secured(allowonly (1)
ldapConnectionT
securedconnections)andboth
ype)
(allowbothunsecuredandsecured
connections).

TLSusagetowards IPNO DefinestheusageofTLSbetween off(0),forced probing


theiOMSsystem theeNBandtheiOMSsystem.The (1),probing (2)
usageofTLSrequiresthatvalid (2)
(omsTls)
certificatesareinstalledtothe
eNB.

1.3.1.8 Alarms for LTE150: LTE OAM Transport Layer Security (TLS) Support

ThissectionlistsalarmsrelatedtoRANO&Msecurityperfeature.

Table26 AlarmsforLTE150:LTEOAMTransportLayerSecurity(TLS)Support

Alarm Alarm name Condition


number

71058 NEO&M ThisalarmisraisedwhentheBTSO&Mconnection


connectionfailure betweentheiOMSandanetworkelementfails.The
managednetworkelementisnotreachablebythe
centralizedO&Msystem.

71052 OMSfiletransfer Startingofanewfiletransferconnectionhasfailed.File


connectioncould transferbetweentheiOMSandatargetnetworkelementis
notbeopened notworking.

71107 InsecureO&M iOMSisinprobingmodeandaneNBattemptstoconnect


connectionattempt withaninsecureBTSO&Mconnection.Inprobingmode
inOMS secureconnectionsarepreferred,thatis,thealarmmaybe
anindicationofafailureinsettingupasecureconnection.

70 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.3.2 LTE432: Cell Outage Detection


1.3.2.1 Introduction

Cells,identifiedasprobablynotprovidingservicewillbeindicatedwithaqualityof
servicealarm.
ThedetectionmechanismofthefeatureLTE432:CellOutageDetectionwillraise
dedicatedqualityofservicealarmforacellincaseithasbeendetectedassleepycell.
BasedonthisspecificalarmthefeatureLTE502:Celloutagetriggeredresettriggersan
actionautomaticallytogetthecellbackintoservice.

1.3.2.2 Benefits

ThefeatureLTE432:CellOutageDetectiondetectssleepingcellsinthenetworkand
executesautomaticcorrectiveactionstoputthecellinserviceagain(celloutage
correction).Theoperatorbenefitsfromacompletelymonitorednetworkperformance.

Improvedfaultmanagementincaseofcelloutages/sleepingcells.
Highercellandserviceavailability.
Automaticcorrectionofserviceoutages(self-healing).

Thenetworkoperationissimplifiedandexperiencesin"traditional"networksshowed
goodresultsincaseofresetexecution.
WiththefeatureLTE502:Celloutagetriggeredresettheoperatorcanselecttoapply
theseautomaticcorrectiveactionsperFlexiMultiradioBTS.

1.3.2.3 Requirements
1.3.2.3.1 Software Requirements for LTE432

1.3.2.3.2 Software Requirements for LTE502

Table27 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL20

NetAct OSS5.3CD3

1.3.2.3.3 Hardware Requirements

ThisfeaturedoesnotrequireanyadditionalHardware.

Issue:02B DN0978045 71

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.3.2.4 Functional Description


1.3.2.4.1 LTE432: Cell Outage Detection

KeyPerformanceindicators,whichindicatethesuccessofcriticalproceduresontheair
interface(suchasUEattemptstoattachtotheNetworkorestablishmentofaRadio
Bearer)areevaluatedtodetermineiftheremaybeaprobleminthecell.Inaddition,the
currenttrafficinthecelliscomparedtohistoricaldata-encounteringnotrafficatanhour
wherethereisusuallyamoderateorhighloadonthecell,isalsoaverylikelyproblem
indicator.
ThetoolsoftheNetActReporter,ThresholderandProfilerapplicationsareusedfor
providingthecorrelationandalarmgeneration.
Thisfeatureraisesanindicationthattheremaybeaproblem,sotheoperatormuststill
checkthesituationinthecellanddecide,whichactionsaretobetriggered.
ThisfeaturecanbeswitchedonoroffintheRadioAccessNetworkinThresholder&
ProfilerinNetAct.
Figure12:LTE432ThresholderandProfilerinNetActgivesanoverviewofthescenario.

Figure12 LTE432ThresholderandProfilerinNetAct

1.3.2.4.1.1 Failure Scenarios

Thefollowingfailurescenariosaretakenintoaccount:

72 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

FailedRACH(RandomAccessChannel)access
FailedRRC(RadioResourceController)connectionsetup
FailedDRB(DataRadioBearer)setup
NoRACHaccess
NoRRCconnectionsetup
NoDRBsetup
Notraffic

1.3.2.4.1.2 Alarm Generation

QualityofServicealarmsaregeneratedinNetactGlobalReporterThreshold&Profiler.
Forthegenerationofthesealarms,eNBPerformanceManagementCounters(uploaded
automatically)andotherO&Minformatione.g.alarms,statesetc.aretakenintoaccount.
Topreventfalsealarms,KPIsarecomparedagainsthistoricalKPIresultvalues.Ifthere
isnotrafficinatimeinterval,wherethereisusuallytraffic(thresholdexceeded),an
alarm/notificationisgenerated.

ThefollowingPMcountersaretakenintoaccount:

Cellavailability
RACHfailurerate
RRCconnectionsetupfailurerate
Dataradiobearersetupfailurerate
PDCPcellthroughput
Uplinkpowermeasurements

1.3.2.4.2 LTE502: Cell outage triggered reset

ThedetectionmechanismoftheexistingfeatureLTE432:Celloutagedetectionwillbe
usedasthebasis.Theraisedqualityofservicealarmisthetriggerfortheautomatic
alarmreactioninNetAct.
Onlythoseconditionsareevaluated,whichindicateaproblemwithnearlyabsolute
certainty:

FailedRACHAccess
FailedRRCConnectionSetup
FailedDRBSetup

Therelatedalarmsareraisedonlyifwehave,duringonePMdatauploadinterval,a
100%failurerateoftheassociatedtelecomprocedures.ABTSresetisattemptedto
correctthecondition.Aslongasthealarmstaysactive,nofurtherresetsareinitiated.

Logging of Automatic Cell Recoveries


Theoperatorcangetinformationaboutthecurrentperformedrecoveriesbyviewinga
logfileinNetAct.

Use Case: Cell Outage Triggered Reset


ThisusecasedescribestherecoveryactionsafteraCellOutagehasbeendetected.
Actors:NetAct,NE,OMSasmediator

Issue:02B DN0978045 73

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Preconditions:

NEisonAir
FeatureLTE432:Celloutagedetectionisenabled
FeatureLTE502:Celloutagetriggeredresetisenabled
ManagementconnectionbetweenNEandNetActisup

Trigger:
NetActMonitoringdetectsaCellOutageAlarmwithasuitabletriggercondition.
Description:

1. NetActcreatestheDelta-PlanwiththechangedBTSResetRequestparameter
2. NetActdownloadstheDelta-PlantotheaffectedBTS
3. NetActactivatestheDelta-Plan
4. TheBTSperformstheresetinordertoactivatetheDelta-Plan.

Postconditions:
TheBTShasbeenreset.

1.3.2.5 System Impacts


1.3.2.5.1 Interdependencies between Features

Table28 Interdependenciesbetweenfeatures
LTE432 CellOutageDetection
Sub-feature:
LTE502:Celloutagetriggeredreset

1.3.2.6 Sales Information

ThisfeaturebelongstoApplicationSoftware(ASW)productstructureclass.

g ForfeatureLTE432:Celloutagedetectionalicenseisnecessary.Feature
LTE502:Celloutagetriggeredresetdoesnotrequireaseparatelicense.

1.3.2.7 User Interface


1.3.2.7.1 Parameters for LTE432: Cell outage detection

Table29:ParametersfortheLTE432:CellOutageDetectionshowstheparameters
implementedforthefeatureLTE432:CellOutageDetection.

Table29 ParametersfortheLTE432:CellOutageDetection

Name Description Default value

MIN_RACH_Threshold Thresholdfor"MINRACH" 100

74 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table29 ParametersfortheLTE432:CellOutageDetection(Cont.)

Name Description Default value

MIN_RRC_Threshold Thresholdfor"FailedRRCConnection 50
Setup"and"NoRRCConnectionSetup"
evaluation

MIN_DRB_Threshold Thresholdfor"FailedDRBSetup"and 50
"NoDRBSetup"evaluation

MIN_PDCP_Threshold Thresholdfor"NoTraffic"evaluation 5kBit/s

MIN_RSSI_Threshold Thresholdfor"DegradedUplinkPower" -100dbm)


evaluation

History_Evaluation AttributeforhistoricalKPIevaluation
methodusedfor"NoRACHAccess",
"NoRRCConnectionSetup","NoDRB
Setup"and"NoTraffic"evaluation.
7days:
historicalKPIresultvalueof
correspondingtimeofday
Min7days:
minimumhistoricalKPIresultvaluefor
sametime

1.3.2.7.1.1 LTE502: Cell outage triggered reset

TheuserhasthepossibilitytocontroltheenablingofthefeatureLTE502:Celloutage
triggeredresetbyeditinganexclusionlist,whichisavailableonNetAct.

1.3.2.7.2 Alarms for LTE432: Cell outage detection

Thefollowingalarmsarerelatedtothisfeature:

Table30 AlarmsfortheLTE432:Celloutagedetection

Alarm number Alarm name

69301 FailedRACHaccess

69302 FailedRRCconnectionsetup

69303 FailedDRBsetup

69304 NoRACHaccess

69305 NoRRCconnectionsetup

Issue:02B DN0978045 75

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table30 AlarmsfortheLTE432:Celloutagedetection(Cont.)

Alarm number Alarm name

69306 NoDRBsetup

69307 Notraffic

1.3.2.7.2.1 Alarms for LTE502: Cell outage triggered reset

Thefollowingalarmsarerelatedtothisfeature:

Table31 AlarmsfortheLTE502:Celloutagetriggeredreset

Alarm number Alarm name

69301 FailedRACHaccess

69302 FailedRRCconnectionsetup

69303 FailedDRBsetup

1.3.2.7.3 Measurements and Counters for LTE432: Cell outage detection

ThefollowingtableshowsthecountersforLTE432:Celloutagedetection.

g ThesecountersdonotservejustfeatureLTE432/502.Theyarecollectedalso
forotherevaluationpurposesandarejustre-usedforthefeature.

Table32 CountersfortheLTE432:Celloutagedetection

Counter long name (short name) Description

CellAvailability(CellAvail) ThisKPIprovidestheCellAvailabilitymainlyforpermanentsupervisionofthe
eNBqualityandforevaluationofCellOutagedetectionscenarios.

RACHFailureRate(RACHFailRate) ThisKPIprovidestheRACHFailureRatebydividingthefailedRACH
accessesthroughthenumberofreceivedRACHpreambles.

RRCConnectionSetupFailureRate ThisKPIprovidestheRRCConnectionSetupFailureRatebydividingthe
(RRCConnSetupFailRate) failedRRCconnectionestablishmentsthroughtheRRCConnectionSetup
attempts.

DRBSetupFailureRate ThisKPIprovidestheDataRadioBearerSetupFailureRatebydividingthe
(DRBSetupFailRate) DRBSetupsFailuresthroughtheDRBSetupattempts.

a)PDCPDataRateuplink ThisKPIprovidestheCellThroughputonPDCPlayerinuplinkanddownlink
direction.
b)PDCPDataRatedownlink

76 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table32 CountersfortheLTE432:Celloutagedetection(Cont.)

Counter long name (short name) Description

Shortname:
a)PDCP_DATARATE_MEAN_UL
b)PDCP_DATARATE_MEAN_DL

a)MeanRSSIonPUCCH ThisKPIprovidestheMeanRSSIinuplinkdirectiononPUCCHaswellason
PUSCH.ThisKPIcanbeusedtomonitorthecorrectfunctionalityofthe
b)MeanRSSIonPUSCH
radio/airinterface.Incaseuplinkpowermeasurementsshowlowvalues,a
c)MeanRSSI malfunctionoftheeNB(i.e.poweramplifier)couldbeongoing.

Shortname:
a)Mean_RSSI_PUCCH
b)Mean_RSSI_PUSCH
c)Mean_RSSI

1.3.2.8 System Responses to Failures

ThisfeatureintroducestheerrorcodesshowninTable33:Errorcodes.

Table33 Errorcodes

Output Name Number Description

DLDC feature option_dldc_not_in_use_ec 000B4H TheDLDCfeaturecannotbeenabledduetothe


is not in use factthatthereisnolicenseinstalledintheBSC,or
in BSC thelicenseinusehasexpired.

DLDC cannot be dldc_without_egprs_ec 000B6H Self-explanatory


enabled
without EGPRS
enabled in BTS

1.3.2.9 Activating the Feature

ToactivatethefeatureseetheNetActFeatureActivationManualinOSS5.2.

g ForfeatureLTE432:Celloutagedetectionalicenseisnecessary.Feature
LTE502:Celloutagetriggeredresetdoesnotrequireaseparatelicense.

1.3.2.10 Abbreviations
1.3.2.10.1 0Z

DRB

DataRadioBearer

Issue:02B DN0978045 77

FeatureDescriptionsRL10 FeatureDescriptionsRL10

eNB

evolvedNodeB

RACH

RandomAccessChannel

RRC

RadioResourceController

SCH

SignallingChannel

1.3.3 LTE539: Central ANR


1.3.3.1 Introduction

Thisfeaturerepresentsthefirstimplementationofautomatedneighborrelation(ANR)for
Intra-frequency,Intra-LTEANR,enablingfortheautomaticcreationandestablishmentof
neighborrelationsbetweenFlexiMultiradioBTSs.ThecentralANR,asthenamestates,
isacentralsolutionbasedonNetActConfiguratorandOptimizer,notconsideringanyUE
measurements.

1.3.3.2 Benefits
1.3.3.2.1 Operator Benefits

Theautomateddetectionandconfigurationofunknowncellsorsitessupportstheself-
configurationoftheneighborcellinformationwithoutoperatorinvolvementandwith
reducedplanningefforts.

Theoperatorcanpresetthepolicyoftheservicetogeneratetheneighborlist.
Theoperatorcanpre-configurethelowertargetandtheuppernumberofneighbor
eNBsforeachnewlyconfiguredeNB.
Theoperatorcanconfigurethethresholdoftheprioritycriterion(forexample
maximumdistance,maximumdifferenceinrelativeantennamainlobes).

1.3.3.3 Requirements
1.3.3.3.1 Software Requirements

Table34 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL10

OMS GOMS6.0

78 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table34 Softwarerequirementsfordifferentnetworkelements(Cont.)

Network element Required software release

NetAct OSS5.2CD3

1.3.3.3.2 Hardware Requirements

ThisfeaturedoesnotrequireanyadditionalHardware.

1.3.3.4 LTE539: Central ANR


1.3.3.4.1 Functional Overview/Details

Feature scope
LTE539:CentralANRrequestsNetActConfiguratorandOptimizertoautomatically
generateLTEintra-frequencyneighborrelationsforaneweNBofanLTEnetworkduring
autoconfiguration,whilethecorrespondingoperationalneighboreNBsarenot
configured.Itisassumed,thatthosewillaccepttheX2setupbasedonfeatureLTE492:
ANRorLTE782:ANRFullyUEbased.LTE539:CentralANRisafeaturepurelyof
NetActOptimizerandConfigurator.TheBTSwillnotbeimpactedbythisfeature.

NetActOptimizergeneratesadjacencyinformationasrequiredforPCImanagement.
Dependingontheprofilethefoundadjacenciesareenteredasneighborcellrelation
informationforconfigurationdata.
NetActConfiguratorwillincludeneighborcellrelationinformationintheCMdatabase
foreNBautoconfiguration.
FortheeNBtheneighborcellrelationinformationisincludedintheparameter
database.OneNeighborRelationisalwaysaffectingtwoeNBDB.

1.3.3.4.1.1 NetAct Optimizer

TosupportCentralANR,Optimizercreatesforeach(newly)plannedeNBalistof
neighboringeNBsbasedonapriorityfunctioncomposedofdistanceandantenna
directionsofhostedLTEcells.Optimizeradds/modifiestheglobaleNBIDintheattribute
adjEnbIPAddressMapoftheobjectADIPNO.

OptimizerpasseslistsofneighboringeNBstoConfigurator.
OptimizerwillpassoneneighborlistforeachgiveneNBoftheplantoConfigurator.
OptimizerandConfiguratorusetheglobaleNBIDtoidentifyeNBs.

Optimizerranksthelistofcellneighborsaccordingtoaprioritycriterionandenforcesthe
numberofneighborcellstobeinanoperator-definablerangebetweenalowerand
upperlimit.Thelowerlimitwillonlybeenforcedincasethereareenoughneighborcells
fulfillingtheprioritycriterion.

Issue:02B DN0978045 79

FeatureDescriptionsRL10 FeatureDescriptionsRL10

g TargetofthefeatureLTE539:CentralANRistoprovidearankedlistofneighbor
eNBstoagiveneNB.InordertoreservefreeentriesintheobjectADIPNOfor
notyetplannedneighboringeNBs,itispossibletorestrictthenumberofentries
bylimitingthenumberofneighborcells.
Thepolicies,loweranduppernumberofneighborcellsandtheprioritycriterion
areexistingmechanismforGSMandWCDMAneighborcellconfigurations.

Manual execution of Central ANR in Optimizer


ManualexecutionofthefeatureLTE539:CentralANRallowstodetermineneighbor
eNBsaccordingtoanoperatorselectedscopeofeNBsbasedongeo-locations.Usually
theeNBisinoperationalstateandhasexistingneighboreNBs.Themanualexecutionof
centralizedANRenforcesthecurrentpolicy.Thismeans,thattheneighborshipsforthe
selectedeNBsareadaptedtothelatestfindingsofthisworkflow.AsthoseeNBsrunina
newNRT(NeighborRelationTable)setup,thecurrentlyappliedneighborrelation
settings(forexampleblacklistingsandCIOsettings)fordeletedneighboreNBsare
expectedtobeuseless.Toavoidraceconditionswiththecurrentconfigurationofthe
eNBs,theoperatorneedstodisableexistingdecentralizedANRfunctions(LTE782:ANR
-UEbasedandLTE492:Automatedneighborrelation(ANR))inthescopeofthe
selectedeNBs.Accordingtothedescribedusecases,itisrequired,thatLTE782:ANR-
UEbasedandLTE492:Automatedneighborrelation(ANR)aredisabledduringplan
provisioning.Ofcoursetheoperatorcanenablethetwofeaturesaftertheexecutionof
themanualtriggeredLTE539:CentralANR.
The uses cases for manual execution of centralized ANR are:

SomeeNBshavebeeninstalledwithoutauto-configuration,noneighborsexist.
TheoperatorcreateseNBsandmanuallycreatesplanfilestobeactivatedby
installationpersonal.
SomeeNBsfailedduringauto-configurationandneedtobeconfiguredinapost
process.
TheoperatorrunsthenetworkwithoutLTE492:ANRorLTE782:ANRUEbased.
SomeeNBshaveachangedHWandcelldeploymentandrequirere-configuration.
SomeeNBshavetoomuchuselessneighborsandneedtoobtainanewNRT.

Theoperatorcanselectascopeofplannedand/oroperationaleNBsandexecutein
NetActOptimizerthetoolforcentralizedANR.Thistooldeterminesforeachofthe
selectedeNBalistofneighboringeNBsbasedonapriorityfunctiondescribedbelow.
TheselectedneighboreNBmightbe

apartoftheselectedset,
othereNBsthatarecontrolledbythesameNetActcluster
externalcells,whicharecontrolledbyanotherelementmanager,evenfromanother
vendor.

Duringauto-configurationCentralizedANRignorsalreadyplannedneighborrelations,
sinceitoperatesonanewlyinstalledeNB.
Incontrast,iftheusermanuallystartsCentralizedANR,thealgorithmneedstoapplya
certainreplacementstrategytoconsiderexistingneighbors,thathavebeencreated
manuallyorbyANR.Existingneighborcellsmightbewhitelistedorblacklisted,neighbor
eNBmightbeblacklistedforhandoverviaX2.Existingneighborsmighthavebeen
optimizedwithrespectto-forexample-timetotriggerorcellindividualoffset.

80 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

ManualexecutionofcentralizedANRsupportsdistributedsites.
Theoperatorcanconfiguretheexecutionoftheneighborfindingalgorithmwith
preferencesettings:

MinimumrequirednumberofneighboreNBs(irrespectiveofdistance).
MaximumallowednumberofneighboreNBs(uptoRL40/RL25TD:32oamControlled
LNADJ).
Maximumalloweddistancebetweenanycell-pairofsourceandneighboringeNBs.

TheneighborfindingalgorithmranksforeachservedcelloftheselectedeNBsthe
potentialneighborcells.ThealgorithmconsidersallmanagedcellsoftheNetActcluster
aswellasallexternalLTEcells.ForeachfoundneighboreNB,Optimizercreatesthe
respectiveLNADJinstancestothesourceeNBasrequiredforeacheNB.
NetActOptimizercreatestheconfigurationplanfileforfurtherprocessinginConfigurator.

OptimizerdeletesallnotrequiredactualLNADJsandConfiguratordeletestheir
LNADJLs.
OptimizercreatesallrequiredLNADJsthatarenotyetexistingandfreeinstances
areavailable.
OptimizerreconfiguresallexistingandrequiredLNADJstooamControlled
ConfiguratoralsodeletesallLNRELsrelatedtodeletedLNADJLs-nomatterifthose
areblacklisted,haveCIOsettingsdifferentfromdefault(0)ortheirnrControl
propertyissetequaltomanual.

NetActOptimizercreatesnewneighboreNBs.Theconfiguratorprovidesallfurther
requiredinformationfortheeNBtoexecuteLTE724:LTEAutomaticNeighborCell
ConfigurationfunctionstoconnecttheX2link.

Issue:02B DN0978045 81

FeatureDescriptionsRL10 FeatureDescriptionsRL10

g DuringtheexecutionofmanualtriggeredcentralizedANRtheUEbased
ANRfeaturesneedtobedisabledtoavoidacommissioningalarmand
abortoftheplanactivation.
TheeNBsoutsidethescopeoftheselectedeNBswillneverbeconfigured.
ThefeaturepreparesthenewLNADJsfortheeNBfeature
LTE724:LTEAutomaticNeighborCellConfigurationasoamControlled
LNADJswiththeIPaddress.TheIPaddressisnotnecessarilyconfigured
atbothpeers.Thereforetheoperatorshouldtemporaryenablethefeature
LTE782:ANRUEbasedorLTE492:ANRafterwardstoenablethe
acceptanceofincomingX2linksattheotherpeer.
Thework-flowdoesnotconsiderthecapabilityoftheeNBstosupportANR,
intra-orinter-frequencyLTEHO.IfthefeatureLTE782:ANRUEbasedor
LTE492:ANRisconfiguredattheotherpeerafterwards,thenthepeerwill
acceptincomingX2links.
IfthetargetglobaleNBIDisX2-black-listed,thisisignoredfor
LTE539:CentralizedANR,asstillS1HOissupported.The
LTE539:CentralizedANRdoesnotmodifyanyX2-black-listingsetting.
ThefeatureLTE539:CentralizedANRdoesnotconsiderthePCI
configuration.Itislefttotheoperatorwhetherornotheruns
LTE468:PCImanagementtoclean-upthePCIconfiguration
ThemanualexecutionofcentralANRdoesnotsupportformerADIPNOLTE
neighbormodelingassupporteduptoRL20/RL15TD.
Theoperatorhastorunandprovisionthemanualexecuted
LTE539:CentralANRtwice,iftherearenotsufficientfreeLNADJinstances
available.NetActOptimizergivesahinttotheoperatorontheneedforthe
secondexecution.

Use Case: manual execution of centralized ANR


ThisproceduredescribestheconfigurationofoneormoreplannedoroperationaleNB(s)
withLTEneighboreNBs.ThisSONfunctionistriggeredbytheoperatorforascopeof
eNBs.NetActOptimizerhastoconsiderallplannedandoperationaleNBsaspossible
neighborsandselectsthebestrankedonesforeacheNB.
Actors
TheoperatormanuallytriggersthefunctionalityforoneormoreeNBs.
Preconditions
Thegeo-locationdataforthecells(respectivethelinkedsitesand/orantennas)inthe
selectedscopeofeNBsandthepotentialneighboreNBsexist.Themainlobedirections
oftheantennasexistorwillbeassumedtobeomni-directional.
NetActOptimizerhasrefreshedallrelevantCMdata,likeglobaleNBID,CGIandPCI.
LTE492:ANRandLTE782:ANRUEbasedaredisabledforalleNBintheselected
scopeofeNBsduringprovisioning.
Description
ThefollowingstepsaresupportedbyNetActOptimizerinamanualtriggeredexecution:

1. NetActOptimizerallowstheoperatortoselectconfigurationdatafortheneighbor
findingalgorithm.
2. TheoperatorselectsascopeofeNBs.

82 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

3. TheoperatortriggerstheCentralizedANRtoolofNetActOptimizertoexecutean
algorithmthatgeneratesintra-orinter-frequencyLTEneighboreNBs.
4. NetActOptimizerexecutestheneighborfindingalgorithmforeacheNBofthe
selectedscope.ExistingneighboreNBs(LNADJs)thatarenotfulfillingtheuser-
givencriteriaanymoreorarelowerrankedcomparedtothenewLNADJsaredeleted
byOptimizer/Configurator.Theirchildelements(LNADJLs)andtherelatedLNRELs
aredeletedaswell.ThehighestrankedfoundneighboreNBs(LNADJs)fullfillingthe
operatordefinedcriteriaareaddedtotheneighborlistofeacheNB.
5. Aftercheckingandpossiblemanualcorrectionbytheoperator,hesavestheresults
toanewplanormergestheresultsbacktothecurrentlyopenplanandexchangesit
toConfiguratorforfurtherprocessing.
6. TheConfiguratorcomplementstheconfigurationoftheneighboreNBsand
configuresthemandatoryparameteroftheoamControlledLNADJs,liketheIP
address.
7. Theoperatortriggerstodownloadandactivatetheplan.NetActConfiguratortriggers
theconsistencychecksandforwardstheplanviaiOMStotheeNB.
8. TheeNBsreconfigureonline(withoutresetorcelllock)theeNBneighbortable.For
alldeletedLNADJtherespectiveX2linkisterminated.ForallconfiguredLNADJs
therespectiveX2linkismaintainedandsettooamControlledorisnewlyset-up.
AccordingtotheexecutionoftheX2proceduresandANRsettingsthenewneighbor
informationfromX2isobtainedandismadeavailableforcallprocessing.NetActwill
beinformedwithCCNand/orcreatenotificationsaccordingly.

Exceptions
IftheneighboreNBdoesnotacceptincomingX2links,thenthesourceeNBcannot
updateitsneighborcellinformationwithrespecttothatneighboreNB.
Post-conditions
TheselectedscopeofeNBshasaconfigurationofvalidneighboreNBs,thatcontains
neighborsthatcomplytothecriteriaandpoliciesassetinOptimizer.Theformer
neighborinformationisdeleted,ifnotrequiredanymore.TheeNBsoperateonthenew
neighboreNBsasitisconfiguredforANRandmobilityfunctions(forexampleLTE724:
LTEAutomaticNeighborCellConfiguration,LTE782:ANR-UEbased,...)andwill
populatetheNRTaccordingly.
ConfigurationsofsurroundingeNBsmightbechangedbyterminatedX2linksor
incomingX2set-upprocedurestriggeredbyeNBsintheselectedscope.

1.3.3.4.1.2 NetAct Configurator

ConfiguratorinturnfindsforeachglobaleNBIDthecorrespondingIPaddress,
completestheentryintheattributeadjEnbIPAddressMapoftheobjectADIPNO
(RL30:objectLNADJparametercPlaneIpAddrCtrl) andwritesthisintoaplan.In
additionNetActConfiguratorupdatestheotherpeer'splanfilestohaveasymmetricalX2
configuration.AteachneighboreNB,identifiedbytheglobaleNBID,theattribute
adjEnbIPAddressMapoftheobjectADIPNOisupdatedwiththeIPaddressandglobal
eNBIDoftheneweNB.WithintroductionofthecommonobjectmodelinRL30,the
ConfiguratorcreatesanLNADJinstanceandsetstheparametercPlaneIpAddr,
cPlaneIpAddressCtrl=oamControlled.
Afterdownloadingandactivatingtheplan,theaffectedeNBproceedsasdefinedbythe
featureLTE724:LTEAutomaticNeighborCellConfiguration:

Issue:02B DN0978045 83

FeatureDescriptionsRL10 FeatureDescriptionsRL10

TheeNBstartsX2setuptoanothereNB(orothereNBs)andexchangesdataaboutthe
cellithosts.

1.3.3.4.1.3 Integration in the Auto configuration Workflow

TheoperatorinfrontoftheConfiguratormanuallycreates/importsaplanwithnewly
plannedeNBs.TheplancontainstheglobaleNBId,thegeo-locationanddirectionof
cellsandmaybealsothelocationofsites.TheIPaddressesoftheeNBsareeither
pre-planned,manuallyconfiguredbytheoperator.Inaddition,theConfigurator
knowsthecurrentconfigurationofthealreadyrunningnetwork.
TheautoconfigurationworkflowtriggersOptimizer.
OptimizerretrievesalistofneweNBsinthemasterplantobehandled.Optimizer
hasalreadyaccesstothecurrentconfiguration.
Optimizerplansintra-LTEneighborsfortheeNBsinthelist.
OptimizerallocatescollisionandconfusionfreecompliantPCIvalues(LTE468:PCI
management)
OptimizertransfersinformationaboutPCIsandintra-LTEneighborstoConfigurator.
Configuratorthenusesneighborinformationtocompletepre-planningfornew
eNBs.
ConfiguratorcreatesentriesinADIPNO.adjEnbIPAddressMaponlyforthe
neighboringeNBthatarealreadyrunning.
ConfiguratoraddstheneweNBtoADIPNO.adjEnbIPAddressMapoftherunning
neighboringeNB.ThisupdateoftherunningeNBisnecessarybecausetheIP
addressoftheneweNBhasnotbeenavailablebeforeautoconfigurationofthe
neweNB.

Configuratordownloadsandactivatestheplantonetwork.Thiswillresultin
AutoconfigurationoftheneweNBand
UpdateofADIPNO.adjEnbIPAddressMapinthealreadyrunningeNB.

1.3.3.5 System Impacts


1.3.3.5.1 Interdependencies Between Features

Table35 Interdependenciesbetweenfeatures
LTE724 LTEAutomaticNeighborCellConfiguration
LTE724enablestheeNBtoexchangecelldataviatheX2interface.

g ThefeaturedoesnotenableeNBtoacceptincomingX2setuprequests
fromunknownIPaddresses,inotherwordseNBisnotabletolearnIP
addressesfromincomingX2setup.

LTE654 LTEConfigurationManagement

LTE720 SONLTEAutoConfigurationAutoconfigurationworkflowusesLTE539:Central
ANRinordertoautomaticallyprovidebi-directionalneighborrelationsbetween
eNBswithouttheneedforexplicitplanning.

LTE492 ANR

84 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table35 Interdependenciesbetweenfeatures(Cont.)
LTE539:CentralANRinauto-configurationconfiguresonlythenewinstalledeNB.
ThiseNBwilltrytoestablishaX2linktoalltheotherpeersthatshallbecome
neighboreNBs.TheoperatorshalltemporaryenableLTE492:ANRatall
neighboreNBstoletthemaccepttheincomingX2link.LTE539:CentralANR
triggeredmanuallyforasetofoperationaleNBs,requires,thatthoseeNBshave
featureLTE492:ANRdisabled,asallowingincomingX2linkswillendupina
commissioningalarmandtheplanfilewillbeabort.Theoperatorshalldisable
LTE492:ANR(LNBTS-anrOmExtEnable==False)manuallyasNetActcannot
dothisautomatically.

LTE782 ANR-fullyUEbased
LTE539:CentralANRinauto-configurationconfiguresonlythenewinstalledeNB.
ThiseNBwilltrytoestablishaX2linktoalltheotherpeersthatshallbecome
neighboreNBs.TheoperatorshalltemporaryenableLTE782:ANR-fullyUE
basedatallneighboreNBstoletthemaccepttheincomingX2link.
LTE539:CentralANR,triggeredmanuallyforasetofoperationaleNBs,requires,
thatthoseeNBshavefeatureLTE782:ANRUEbaseddisabled,asallowing
incomingX2linkswillendupinacommissioningalarmandtheplanfilewillbe
abort.TheoperatorshalldisableLTE782:ANRUEbasedbased(LNBTS-
actUeBasedAnrIntraFreqLte==False)manuallyasNetActcannotdothis
automatically."

1.3.3.6 Sales Information

ForFeatureActivationseeFeatureActivationManualinNetActoperating
documentationOSS5.2.

1.3.3.7 Activating and Configuring the Feature

ToactivatethefeatureseetheNetActFeatureActivationManualinOSS5.2.

1.3.3.8 Abbreviations
1.3.3.8.1 0Z

ANR

AutomatedNeighborRelation

eNB

evolvedNodeB

Issue:02B DN0978045 85

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.3.4 LTE665:Certificate Management and


LTE685:Infrastructures for Certification Authority (CA) and
Registration Authority (RA)
1.3.4.1 Introduction to the feature
1.3.4.1.1 LTE665: LTE Certificate Management

TheeNBcertificatemanagementfeatureprovideshandlingoftheprivateandpublickey
aswellasdigitalcertificatesinX.509v3format.Keysandcertificatesareusedformutual
authenticationbetweenIPsecand/orTLSprotocolpeers.Thisfeaturerepresentsthe
eNBlocal/peerpartoftheNSNidentitymanagementsystem(IDM)ora3rdpartyPKI
solution.

1.3.4.1.2 LTE685: Infrastructures for Certification Authority (CA) and Registration


Authority (RA)

Toenablepublickeycertificationbasedauthenticationandauthorizationwithinthe
accessnetworkandmanagementnetwork,provisioningofapublickeyinfrastructureon
bothNSNasvendorandtheoperatorsideisaprerequisite.TheNSNidentity
managementsolutionintegratestheNSNPKImanufacturinganddeliverychainwiththe
operatorsPKIinfrastructure.

1.3.4.2 Benefits
1.3.4.2.1 LTE665: LTE Certificate Management

Thecertificatemanagementfeatureprovidescentralizedandscalablekeyandcertificate
managementforoperatornetworks.
Itenables:

Securecommunicationbasedonapublickeyinfrastructure
Mutualauthenticationbasedondigitalpubliccertificates

1.3.4.2.2 LTE685: Infrastructures for Certification Authority (CA) and Registration


Authority (RA)

Publickeyandcertificatemanagementprovideacentralizedandfullscalableidentity
andsecuritymanagementforthenetworknodesandtransmissionfortheeNB.

1.3.4.3 Requirements
1.3.4.3.1 Software requirements

Table36 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL10

eNodeB LBTS1.0

86 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table36 Softwarerequirementsfordifferentnetworkelements(Cont.)

Network element Required software release

MME

SAEGW

UE

NetAct OSS5.3CD1

1.3.4.3.2 Hardware requirements

Thisfeaturedoesnotrequireanyneworadditionalhardware.

1.3.4.4 Functional description for certificate management


1.3.4.4.1 LTE665: LTE Certificate Management

Thecertificatemanagementisimplementedbythesystemfeatures:
Thecertificatemanagementfeatureisneededforenrollments,update,andrevocationof
operatorcertificateswhenpublicoperatorcertificatesareusedinthenetwork.
Thisfeaturecomprisesthefollowingcharacteristics:

factoryprovisioningofvendorkeysandcertificate
remoteoperatorcertificateenrollment
localoperatorcertificateenrollment
vendorcertificateauthentication
PSK/RefNumauthentication
eNBself-signedcertificateauthentication
certificaterevocation
certificaterenewal/keyupdate

Factory provisioning of vendor keys and certificate


TocomplywiththeNSNsecuredeviceidentity(SDI)conceptandthe3GPPTS33.310
AuthenticationFrameworkforinitialcertificateenrollment,themanufacturingprocessof
aneNBisextendedbykeypairandcertificatecreationsteps:

1. WhenaneweNBismanufacturedatacertainpointintheprocessqueue,aunique
publicandprivatekeyisgeneratedandstoredwithintheeNB.Thepublickey
portionisgiventothefactoryRA/CAforsigning.
2. TheNSNfactorycertificationauthority(Factory-CA)togetherwiththefactory
registrationauthority(Factory-RA)createsandsignsaNSNdevicecertificatefor
eachindividualeNB,wherethesubjectofthecertificateislinkedtotheeNBserial
number.

g TheNSNFactoryCAisasubordinateCAoftheNokiaRootCA.

Issue:02B DN0978045 87

FeatureDescriptionsRL10 FeatureDescriptionsRL10

3. ThepublicNSNdevicecertificateisstoredtogetherwiththefactoryCAcertificatein
aNSNrepository,andintheFTMinsideeNB,beforemodulesareshippedto
warehousesand/orcustomers.Thisdevicecertificateorvendorcertificateisusedto
authenticateagainsttheoperatorRA/CAduringautomatedenrolment(compliant
with3GPPTS33.310).
4. WhenaneweNBisdeliveredtotheoperator,theoperatoralsogetstheserial
numbersoftheshippedmodulesonrequestviatheNSNWebinterface(NOLS).The
eNBsserialnumbercanbeusedasawhitelisttoverifyorcross-checkiftheeNB
belongstothehardwarethathasbeenordered,bycomparingtheserialnumberof
thecertificatefromtheeNBwiththeorderdeliveries.NSNprovideswiththeIdentity
ManagementServer(IDM)acompletePKIsolutionwhichisabletoexecutethis
serialnumbercheckautomatically.

CertificateenrollmentisdoneforeacheNB.Thenetworkelementgeneratesakeypair
andsendstheinitializationrequesttothecertificationauthority.Thisprocedureincludes
theregistration,theinitialization,andthecertificationprocesses.Afterthis,thecertificate
isdeliveredtothenetworkelementandispublishedtotheCAscertificaterepository.

Supported certificates
TheeNBsupportthefollowingcertificatesinthex.509v3format:

PEM:usedforuserinterface
DER:usedfortransferringcertificatesovercertificatemanagementprotocol(CMP)
PKCS#12:usedfortransferringcertificatesandkeysbetweeneNBandBTSSite
Manager(usedforinjectingthecertificateandprivate/publickeypairintheBTSin
exceptionalcasewherenoonlinePKIisavailable)

ThesamecertificateisusedforbothIPSecandTransportLayerSecurityProtocol(TLS)
authenticationneeds.

Remote operator certificate enrollment


WhenanewlydeployedeNBconnectstothetransportnetwork,itisprovidedwiththe
addressoftheoperator'sIDMserver(asavendor/operator-specificattributeduringplug-
and-playfromtheDHCPserverormanuallyconfigured)oritsthird-partyPKIsecurity
server(RA/CA)asthefirstpointofcontact.
TheeNBcreatesanewkeypairandestablishesaCMPconnectiontogetthepublickey
portionsignedbyanewoperatordevicecertificateforthiseNBandtodownloadthe
operator'spublicsigningCAcertificateastrustanchor.
IfaNSNIDMserverisinplace,theserverknowstheeNBalready(becauseitsserial
numberhasalreadybeenreceivedandstored)andtheservercanverifyoptionallyifthe
eNBbelongstothepoolofordereddevices.
OncetheeNBknowsthefinaloperatornodecertificatetobeused,itcanestablish
secureconnectionstoallofitscommunicationpartnersviaIPsecorTLSwiththecorrect
operatornodeidentity,forexample,toconnectwithNetActtocontinuewithauto-
configuration.

88 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Local certificate enrollment


LocalcertificateenrollmentisusediftheoperatorrunsnoonlinePKIinfrastructure.The
operatorcertificatesandtrustanchorsarethenintroducedbyamanualprocedureinto
thesecurekeystorageoftheeNBwiththeBTSSiteManager.Certificateandkey
interchangeaccordingtoPKCS#12issupportedbetweeneNBandBTSSiteManagerto
injectbothoperatorcertificateandkeypair.

g Theoperatorneedstocomputetheprivateandthepublickeypairoff-linetoget
thepublickeysignedbytheoperator'sCAandtocreatethePKCS#12
containerfile.Thisfilecontainstheoperatorcertificateandthekeypairanditis
entirelyciphered.Fordecryptionpurposes,thefieldinstallerneedstoknowthe
rightpassphrase.

Asimilarprocedurecanbeusedtoinjectothercertificateslikethetrustanchors.

eNB authentication
DuringeNBrolloutandinexceptionalcases,novalidoperatorcertificatemaybe
availablewithintheeNB.TheeNBthentriesthefollowingalternativestoauthenticate
againsttheoperatorsCAorcertificateservertoobtaintheoperatorcertificate:

1. IfaPSK/RefNumisconfigured,theeNBtriestoauthenticateusingthesecredentials.
2. IfPSK/RefNumisnotconfigured,andaNSNdevicecertificate(vendorcertificate)is
available,theeNBtriestoauthenticatewithitsvendorcertificate.
3. IfneitheraPSK/RefNumnoraNSNvendorcertificateisavailable,theeNBusesa
self-signedcertificate.

Incaseofafactoryreset,theoperatorcertificateandtheoperatorCAcertificateare
removedfromthenetworkelementandifavendorcertificateisavailableitisusedto
authenticatethenetworkelementagainsttheoperatorsCAtoobtainanewoperator
certificate.

PSK/RefNum authentication
ThePSKandRefNumcanbeconfiguredbytheBTSSiteManagerorviaNetAct(NetAct
massupdatetool).
ThePSK/RefNumisusedonlyifthePSKandRefNumvaluesaredifferentthatthe
defaultvalues.
TheoperatorneedstoactivateanexceptionpolicyfortheCAtoallowacceptanceof
PSK/RefNum.

eNB self-signed certificate


Adefaultself-signedcertificateisavailableforexceptionalcasesifnoNSNdevice
certificate(vendorcertificate),nooperatordevicecertificate,orPSK/RefNumisavailable
intheeNBtoauthenticatetheCMPconnectiontotheoperator'sIDMsystemor
certificateauthority.
TheoperatorneedstoactivateanexceptionpolicyfortheCAtoallowacceptanceofthe
self-signedcertificate.

Issue:02B DN0978045 89

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Operator certificate revocation


Certificaterevocationisdonewhenpropertiesofendentitieschange.Suchchangesare:
privatekeycompromise,changeinaffiliation,andnamechange.Whencertificatesare
identifiedforrevocation,theyarelistedinthecertificaterevocationlist(CRL)inthe
operator'sIDM/CA.TheCRLisdownloadedfromtheCRLrepositorytotheeNBeither
periodically,orcommand-basetriggeredfromNetAct.
TheeNBfetchestheCRLfromaCLRdistributionpoint.ThereferencetoCRL
distributionpointistakenfromeNBownoperatorcertificateorCAcertificate.With
LTE482:DNSSupportforCertificaterevocationfeature,thisreferencecanbeeitheran
IPaddressorfullyqualifieddomainname(FQDN).

Operator certificate renewal/key update


OperatorcertificaterenewalintheeNBandiOMSisdoneautomaticallybeforea
certificateslifetimeendsandneedstoberenewedforanotherperiodoftime.
Simultaneously,akeyupdateismadetothestill-validcurrentkeypair.Ifthenew
certificateisreceived,thecurrentkeypairissubstitutedbythenewone.This
functionalityistriggeredfromtheeNBautonomouslyaccordingtocontroltimersettings
orcommandbasetriggeredfromNetAct.TheupdateoftheoperatorcertificateforeNB
canbealsodonebytriggeringCMPinitializationprocedureusingBTSSiteManager.

g BeforetriggeringCMPinitializationprocedureofupdatingeNBoperator
certificate,makesuretheCMP/CAserverpolicyisconfiguredtoallowa
repeatingCMPinitializationrequestsforacertaineNB.

WhenCMPinitializationprocedurefinishes(triggeredeitherautomaticallyormanually),
thecurrentlyestablishedIPsecconnectionsareterminatedandre-establishedusingnew
certificates.ThiscausestemporaryinterruptionintheeNBoperation.TheCMP
initializationproceduredoesnotaffectsecureconnectionsthatuseTLSprotocol.

Operator certification authority (CA) certificate renewal/key update


Theoperatorcertificationauthority(CA)certificateisusuallyvalidfor10-20years.Ifthe
operatorCAcertificatelifetimeisgoingtoexpire,iftherehasbeenaleakageofthe
certificate,oramajorchangeinthePKIhierarchyofthecustomernetworkhastaken
placetheoperatorCAcertificatemustberenewed.TheupdateoftheoperatorCA
certificateisdoneviamanualprocedureusingtheCMPinitializationprocedure.
Aswiththeoperatorcertificateupdate,theCMP/CAserverpolicymustbeconfiguredto
allowarepeatingCMPinitializationrequestsforacertaineNB.Thecurrentlyestablished
IPsecconnectionsareterminatedandre-establishedusingnewcertificates.
ForthenewIPsecconnectionstowork,theoperatorCAcertificatemustbeupdatedalso
inallpeernetworkelements(forexample,securitygateways,iOMS).Itisrecommended
toupdatetheoperatorCAcertificateinallnetworkelementsintheorderspecifiedinLTE
RANO&MSecurity.FormoreinformationoftheoperatorCAcertificateupdate,see
ManualoperatorCAcertificateupdate,inOperatingtaskrelatedtoLTERANO&M
Security.

Certificate management protocol (CMP)


CMPv2accordingtoRFC4210issupported.
HTTP1.1accordingtoRFC2585isusedasthetransportprotocolfortheCMP.

90 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

ThefollowingCMPmessagesaresupported:

ir(initializationrequest)
ip(initializationresponse)
kur(keyupdaterequest)
kup(keyupdateresponse)
pkiconf(PKIconfirmation)
certConf(certificateconfirm)

VendorcertificatesareprovidedintheCMPmessageExtraCertsfield.

1.3.4.4.2 LTE685: Infrastructures for Certification Authority (CA) and Registration


Authority (RA)

Toenablethepublic-key-certification-basedauthenticationandauthorizationwithinthe
accessnetworkandmanagementnetwork,provisioningofapublickeyinfrastructureon
boththeNSNsideasvendor,andontheoperatorsideisaprerequisite.TheNSN
securedeviceidentity(SDI)conceptlinkstheNSNPKImanufacturinganddeliverychain
withtheoperatorsPKIinfrastructure.
Ontheoperatorside,theNSNidentitymanagement(IDM)solutionprovidesall
componentstorealizeanoperatorPKI.Thissolutionprovidestherequiredinfrastructure
includingcomputersystemsandapplicationsforhandlingcertificaterequestsand
alignedprocessesforcertificateimplementation.
Thisfeatureislicensed(trustbasedlicense).
SDI concept on NSN side
TosupporttheNSNIDMoranotherthirdpartyPKI,themanufacturingprocessofaneNB
isextendedbytheintroductionofaNSNfactorycertificationauthority(Factory-CA)and
factoryregistrationauthority(Factory-RA),whichcreatesandsignsavendorcertificate
foreachindividualeNB.
TheprivateandpublickeypairsarecreatedduringtheeNBsystemmoduleassembly.
TheNSNfactory-CAtogetherwiththefactory-RAcreatesandsignsaNSNvendor
devicecertificateforeachindividualeNB.
IDM solution on operator side
Ontheoperatorside,theIDMprovidestheidentitymanagement,whichcomprises:

aregistrationandcertificationauthorityfor
creationandmanagementofthepublicoperatordevicecertificates
additionalauthorizationmodulesforautomatedchecksofNSNpublicdevice
certificatesagainstdeployedeNBhardware

deploymentofoperatordevicecertificatestotheeNB
renewalandrevocationofoperatorcertificates,ifnecessary.

Theinfrastructureismulti-vendorcapableaslongasotherRA/CAproductssupportthe
certificateexchangeproceduresandtherelatedprotocols,suchasthecertificate
managementprotocol(CMPv2)withtherequiredprotocoloptions.TheCMPv2protocol
isusedtoderivetheoperatorcertificatefromtheoperator'sIDMorthirdpartyCA.

Issue:02B DN0978045 91

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Identity management server solution


Theidentitymanagementserversolutionconsistsofthefollowingcomponents:

eNB
Intheinitialenrollmentphase,whichusesCMP,theeNBvendorcertificate,theserial
number,andanewlycreatedpublickeyaresenttotheoperatorCA/RA.The
operatorCA/RAauthenticatestheeNB,createsanewoperatorcertificate,signsthe
newoperatorcertificatewiththeoperatorCAcertificate,andsendsitbacktothe
networkelement.

g Intheinitialenrollmentthevendorcertificateisusedtoauthenticatethe
request.WhentheeNBupdatestheoperatorcertificate,itusesthealready-
enrolledoperatorcertificateforauthentication.

DHCPserver(tosupportautomatedcertificateenrolmentifeNBplugandplayis
applied)
TheDHCPserveristheoperatorsnormalDHCPserver(usedforeNBplugandplay
rollout),whichdeliversIPaddressestoeNBs.AstheeNBsisnotawareoftheIP
addressoftheoperatorsIDMserver,itreceivestheaddressintheinitialDHCP
exchange.AstandardDHCPservercanbeusedbutitmustbeconfigurableto
supporttheconfigurationofvendorspecificattributes.
IDMserver
TheIDMserverrepresentstheNSNRA/CAsolutiontomanageanddeliveroperator
certificatestotheeNBsintheoperatornetwork.TheIDMserverisownedandrunby
theoperator.Themaincomponentsoftheidentitymanagementserverare:
securityserver
Thesecurityserveristhefront-endoftheoperatorPKIterminatingtheCMP
protocoltowardstheeNB.ItmayhosttheRAfunction,too,andisoftenlocated
inademilitarizedzone(DMZ),separatedfromtheCAbyafirewall.Thesecurity
serverisusedbytheeNBtoenrollandrenewtheoperatorcertificate.TheIP
addressofthesecurityserverispassedtotheeNBduringtheplug-and-play
DHCPsequenceorbymanualconfiguration.
operatorCA
TheoperatorCAsignstheeNBpublicRSAkeyreceivedfromthesecurityserver,
createstheoperatorcertificate,returnsthemtotherequestorandstoresthe
publiccertificatesinrepositories.
serialnumberdatabase(optional)
TheNSNserialnumberdatabaseisanabstractentitycontainingalistofallNE
serialnumbersthattheoperatorhaspurchased.
certificatedeliverysoftwaremodule(optional)
TheNSNspecificcertificatedeliverysoftwaremoduleisruneverytimethe
customerordersasetoftransportmodules.Thesoftwarereceivesasinputalist
ofserialnumbersofthedeliveredmodules.Itvalidates(compares)theserial
numberofanewenrolledeNBaskingforanoperatorcertificatewiththeserial
numbersreceivedfromthedeliverychain.Iftheentriesmatch,theeNBis
authorizedtoreceiveanoperatorcertificate.
customizedRA(optional)
ThecustomizedRAdeliverseachcertificatesigningrequesttotheoperatorCA
forsigning.Therehavetobepre-settrustrelationsbetweentheCAandtheRA.

Deployment of operator certificates without IDM/online PKI

92 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

IftheoperatorrunsnoonlineIDMorsimilarPKIinfrastructure,thenitispossibleto
introducetheoperatorcertificatesbyamanualprocedureintothesecurekeystorageof
theeNBeitherlocallyorremotelywiththeBTSSiteManager.
Factory trust anchor
ThefactoryCAbelongstothePKIofNSN.ThefactoryCAcertificateitselfissignedby
theNokiaRootCA.Thesefactorytrustanchorsarerequiredbytheidentitymanagement
server(oranotherthirdpartyRA/CAusedbytheoperator).Duringtheinitialoperator
certificateenrollment,theCAvalidatesandauthenticatestheCMPInitializationmessage
usingthefactoryCAsignedvendorcertificate.Forthisvalidation,theCAneedstheNSN
trustanchors.Thefactorytrustanchors(NokiaRootCAcertificateandNSNfactoryCA
certificate)aredeliveredtotheoperatorviatheNSNWebinterface(NOLS).
Operator trust anchor
Theoperatortrust-anchorisprotectedbyasecurekeyandsecurefilestorage
mechanismintheeNB.TheeNBauthenticatesitselftoapeernetworkelementusingits
operatorcertificate,whichissignedbytheoperatortrustanchor.Thistrustanchoris
usedbythenetworkelementstovalidatethepeercertificatewhenexecutingTLSsetup.
Thetrustanchorisdeliveredbytheidentitymanagementservertothenetworkelement
duringtheinitialoperatorcertificateenrollmentintheCMPinitializationresponse
message.
Operator trust anchor and operator/vendor certificate installation
TheeNBsupports:

operatortrustanchorviaCMP
operatorcertificateviaCMP
transferfromBTSSiteManager(manualdeploymentwithBTSSiteManager).

1.3.4.5 System impacts

LTE665:LTECertificateManagementfeatureisrelatedtofollowingfeatures:

LTE150:LTEOAMTransportLayerSecurity(TLS)Support
LTE689:LTEIPsecSupport
LTE154:SONLTEBTSAutoConnectivity

1.3.4.6 Sales information

LTE665:LTECertificateManagementandLTE685:InfrastructuresforCertification
Authority(CA)andRegistrationAuthority(RA)arebothadditionalsoftwarefeaturesand
theirlicenseistrust-based.
ThefeaturesareactiveforthewholeeNB.
TheyareindicatedasactiveifthecmpServerIpAddressparameterisnotempty.

1.3.4.7 User interface


1.3.4.7.1 Parameters for LTE665: LTE Certificate Management

Table37:ParametersforLTE665:LTECertificateManagementshowstheparameters
relatedtofeatureLTE665LTECertificateManagement.

Issue:02B DN0978045 93

FeatureDescriptionsRL10 FeatureDescriptionsRL10

AllparametersarelocatedinobjectCERTH.

Table37 ParametersforLTE665:LTECertificateManagement

Name Description Range Default


value

btsCertificateUpdateTim NumberofdaysbeforeaBTScertificate 1...4999 365days


e expiresandaCMPupdatesequenceis days,step1
triggeredautonomouslyfromtheBTS. day

caCertificateUpdateTim NumberofdaysbeforeaCAortrust 1...4999 1825


e anchorcertificateexpiresandaCMP days,step1 days
updatesequenceistriggered day
autonomouslyfromtheBTS.

caSubjectName NameofCMPserver 0...128


characters

certhId Certificatehandlerconfiguration 1...1,step1 1


Valueisalways1,notmodifiable

cmpServerIpAddress IPaddressofCMPserver,enteredin 7...15


dotteddecimalformat characters

cmpServerPort PortnumberforaddressingCMPserver 1...65535,


step1

crlUpdatePeriod Periodforexecutingaperiodicalupdate 0...8760 0


ofCRL hours,step
1hour
Value0meansnoperiodicalupdate

1.3.4.7.2 Alarms for LTE665: LTE Certificate Management

Table38 AlarmsforLTE665:LTEcertificatemanagement

Alarm Alarm name Condition


number

61074 CRLUpdatefailure ThisalarmisraisediftheBTScannotupdatethe


CertificateRevocationList(CRL)foroneofthe
followingreasons:

theLDAPbindingfails
theLDAPsearchisempty(noCRLfound)/
theLDAPsearchcontainsmorethanone
entry
theCRLsignaturevalidationfails
theCRLfileexceedstheBTSstoragelimit
theBTScertificateispartoftheCRL

94 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table38 AlarmsforLTE665:LTEcertificatemanagement(Cont.)

Alarm Alarm name Condition


number

61510 NO_CERTIFICATE Arequestedcertificatecouldnotberetrievedfromthe


CertificateAuthority(CA).

7665 BASESTATION ThisalarmisraisedifanyofthebelowBTSfaults


TRANSMISSION occurs:
ALARM
CRL Update failure (61074)
Thefaultisreportedwhen:
theLDAPbindingfails
theLDAPsearchisempty(noCRLfound)
/theLDAPsearchcontainsmorethan
oneentry
theCRLsignaturevalidationfails
theCRLfileexceedstheBTSstorage
limit
theBTScertificateispartoftheCRL

Automatic BTS Operator Certificate


retrieval unsuccessful (61510)
Thefaultisreportedwhentherequested
certificatecouldnotberetrievedfromthe
CertificateAuthority(CA).

1.3.4.8 Activating and configuring the feature

ForanactivationinstructionrefertoFeatureActivationDocument.

1.3.5 LTE666: LTE User Account Management


1.3.5.1 Introduction to the feature

ThisfeatureenablescentralizeduseraccountmanagementfortheeNBandintegrated
operationandmediationfunctionfromNetAct.Italsoprovidesamassupdatingfunction
oflocaluserpasswordsforeNB.

1.3.5.2 Benefits

EnhancedriskmanagementandOPEXsavingsareachievedbecauseofcentralized
LTEradioaccesssystemsecurityandafastnetworkwidemanagementoflocaleNB
useraccounts.

Issue:02B DN0978045 95

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.3.5.3 Requirements
1.3.5.3.1 Software Requirements

Table39 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL10

eNodeB LBTS1.0

MME

SAEGW

UE

NetAct OSS5.2CD3

1.3.5.3.2 Hardware Requirements

Thisfeaturedoesnotrequireanyneworadditionalhardware.

1.3.5.4 Functional description for user security

CentralizeduseraccountsofnetworkelementsaremanagedwithNetAct.(Formore
information,seeNetActdocumentation:Centralizeduserauthentication&authorization).
Itallowsuserstologintodifferentnetworkelementswithinthecustomernetworkwiththe
sameuserIDandpassword.
Duringlogin,usersareauthenticatedandauthorizedusingalocaluserrepositoryora
centralizedauthenticationserver.Iflocalauthenticationfails,thecentralized
authenticationisattempted.Userauthorizationprofilescanbecustomizedaccordingto
differentroles.Rolesarebasedondifferenttypesofusageneedsandcanbedefinedby
thenetworkadministrator.

1.3.5.4.1 Authentication and authorization

Centralizeduserauthenticationandauthorizationisdonebytheauthenticationserver,
whichislocatedinNetAct,andbyLDAPclientsoftwarelocatedineachnetwork
element.TheoperatingmodeofLDAPinterfacebetweentheserverandtheclientis
configurable(secure/insecuremode).
Networkelementshavetheirownaccountsthatprovidecommunicationwiththe
centralizeduserrepository.TheiOMShavetwotypesofaccounts:registrationaccount
andNEaccount.Theregistrationaccountisusedonlyfortheregistrationpurposes,
whentheiOMSconnectstotheNWI3registrationserviceinNetActandfurthertothe
centralizeduserrepositoryserver(LDAPserver)forthefirsttime.Afterregistrationofa
newnetworkelement,theregistrationaccountisdisabledandonlytheNEaccountisin
use.IftheregistrationaccountofaniOMScouldnotbeused,theNEaccountisusedas
aback-upaccountforregisteringtheiOMSintheCUAArepository.

96 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

NEaccountsprovidecommunicationwiththecentralizeduserrepository,enable
attachmentoftheroledataforaparticularuserwhentheuserlogsintothesystem,and
itistheonlyaccounttypethatisusedforobtainingauthenticationandauthorizationdata.
Authenticationwiththelocaluserrepositorycanbeusedifthereisnoconnectiontothe
centralizedauthenticationserverorduringthenetworkelementcommissioning.
Thenetworkelementuserauthenticationorderisthefirstlocaluserrepository,then
centraluserrepository.

1.3.5.4.2 Disabling user accounts in NetAct

Itispossibletodisablecentralizedenduseraccountsforeachcombinationofnetwork
elementtypeandversion.Ifcentralizedenduseraccountsaredisabled,NetActusesthe
networkelementlocalaccounttoconnecttothenetworkelementinsteadofthe
centralizedaccount.Internally,NetActalwaysusesthecentralizedauthenticationand
authorizationrepository.Networkelementscancontinueusingtheirnetworkelement
accounteventhoughcentralizedenduseraccountsaredisabledinNetActforthat
networkelementtypeandversion.
Itisalsopossibletodisablenetworkelementaccounts.

1.3.5.4.3 User management

Withcentralizeduseraccountsandpermissionmanagementfunctionalitythenetwork
administratorcansetupuseraccountsanddefinedifferentaccessclassesfordifferent
usergroupsandnetworkelements.TheeNBsupportsonlyoneaccessclass.Auserthat
isconnectedandsuccessfullyauthenticatedtotheeNBcanperformanyavailable
action.
Itispossibletodefineandsetmultipleprofilesforonecentralizeduseraccount.Inthis
case,accessrightsfortheuserarethecombinationofthoseprofiles.
Managementoperationsusinglocaluseraccountcanbeperformedinaddition
especiallywhenthecentralizedmanagementsystemisnotavailable.

1.3.5.4.3.1 Mass updating of eNB local user accounts

WiththemasschangefunctionalityimplementedinNetAct,itispossibletochangeeNB
localuseraccounts.TheeNBlocaluseraccountscanbechangedformultiplenetwork
elementsatthesametime.
TolimitsimultaneousNWI3sessionopeningstothesameiOMS,theNetActmass
updatingtoolhasbeenenhancedtosendnewuseraccountandpasswordinformationin
alistmode.ThismeansthatasinglemessagecancontainseveraleNBstowhichthe
changeoperationistargeted.TheiOMSmediationfunctiondisassemblesthetarget
networkelementidlistandforwardstheseparatemessagesindividuallytoeacheNB.
ToavoidtheoverloadsituationintheiOMS,NetActwillnotsendanynewmassupdate
requeststowardsthesameiOMS,andtheiOMSwillnotacceptanynewrequestsuntil
thepreviousmassupdaterequesthandlingiscomplete.

1.3.5.4.4 Audit trail

TheAuditTrailapplicationisadditionalNetActsoftware.Withthisapplicationcentralized
userauditingisenabled.LTE667LTEUserEventLogManagementfeatureisavailable
fromiOMSandeNB.

Issue:02B DN0978045 97

FeatureDescriptionsRL10 FeatureDescriptionsRL10

LogfileuploadfromtheeNBandiOMStoNetActisusuallyascheduledevent.Both
eNBandiOMScanalsotriggertheuploadbysendingthelogfilefulleventtoNetAct.
FilescanbetracedandprocessedwithNetActtoolsafterthesuccessfulupload.

LTE user event log management


UsereventlogmanagementisimplementedfortheiOMSandtheeNB(whereauser
canestablishinteractivesessions).Bothsupportcentralizedeventlogmanagement.The
iOMScollectstheeventlogsfromtheeNBandtransfersthelogstotheNetAct.
Thefollowingsecurity-relateduseractionsarecollectedintheusereventlog:

unsuccessfulloginattempts
successfullogins
logouts
configurationchanges

Logfileuploadmaybeinitiatedby:

NetActoperator:TheoperatormanuallyentersthereferringNetActcommand.
NetActscheduler:Theoperatorschedulestheuploadperiodically.
alogfilefullevent:TheiOMSandtheeNBinitiatetheuploadifalogfilereaches
maximumcapacitybeforeNetActinitiatestheuploadagain.

TolimitsimultaneousNWI3sessionopeningstothesameiOMS,theNetActAuditTrail
applicationsendseNBlogfilerequestsinalistmode.Thismeansthatinthelog
collectionsequencesasinglemessagecancontainseveraleNBstowhichtherequestis
targeted.TheiOMSmediationfunctiondisassemblesthetargeteNBIDlistandforwards
themessagestoeachindividualeNBs.
TheeNBcompressesthelogfilesbeforeupload.TheeNBlogfilesaretransferred
directlytoNetAct.TheeNBlogfilesarefirsttransferredtotheiOMSandthensenttothe
NetAct.Duringlogfileupload,thenewlogeventsarebufferedandstoredafterwardsin
thenewlogfile.AftersuccessfuluploadtoNetAct,thelogfilesaredeletediniOMSand
eNB.

g BecauseoftheeNBtwo-stepfiletransfermodeviatheiOMS,theTLS
configurationmustbeconsistentinallnetworkelementstakingpartinthefile
transfer.IfTLSistobeenabled,itmustbeenabledbetweentheeNBandthe
iOMS,andalsobetweentheiOMSandtheNetAct.Theconfigurationinwhich
onlyoneconnectionissecuredwithTLS(eitherbetweentheeNBandtheiOMS
orbetweentheiOMSandtheNetAct)blocksthefiletransfer.

IfalogfilehasreacheditsmaximumsizeandisnotuploadedtoNetAct,thelogfileis
overwrittenandtheoperatorisinformedbyamessageinthelogfile.

1.3.5.5 System impacts

Thisfeaturehasnoimpactonsystemperformanceorcapacity.

1.3.5.6 Sales information

TheLTEUserAccountManagementfeatureisanadditionalsoftwarefeature.

98 DN0978045 Issue:02B

FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.3.5.7 User interface


1.3.5.7.1 Parameters for LTE666: LTE User Account Management

Table40:ParametersforLTE666:LTEUserAccountManagementshowsthe
parametersrelatedtoLTE666LTEUserAccountManagement.
AllparametersarelocatedinobjectAMGR.

Table40 ParametersforLTE666:LTEUserAccountManagement

Name Description Range Default


value

amgrID Thisparameteridentifiestheaccount 1...1,


manager
step1
Valueisalways1,notmodifiable

primaryLdapPort PortnumberoftheprimaryLDAPserver 1...65535, 389


step1

primaryLdapServer IPaddressoftheprimaryLDAPserver, 7..15


enteredindotteddecimalformat characters

Table41:ParametersforLTE666:LTEUserAccountManagement-BTSSMshowsthe
waitingtimefortheautomaticdisconnectparameterrelatedtoLTE666.Itissetinthe
BTSSMapplicationandislocatedinFilePreferences.

Table41 ParametersforLTE666:LTEUserAccountManagement-BTSSM

Description Range Default value

itemAutomatic disconnection from BTS site,check 10..120minutes, 30minutes


Disconnect if no user activity step1

1.3.5.7.2 Alarms for LTE666: LTE User Account Management

Table42 AlarmsforLTE666:LTEUserAccountManagement

Alarm number Alarm name Condition

61500 Fivefailedloginsto FiveconsecutivefailedloginattemptstotheFTM


FTMduetowrong havebeenperformed.
usernameor
password

Issue:02B DN0978045 99

FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table42 AlarmsforLTE666:LTEUserAccountManagement(Cont.)

Alarm number Alarm name Condition

70025 POSSIBLE Five(defaultvalue)consecutivefailedlogin


SECURITYTHREAT attemptstoiOMS
INNETWORK
ELEMENT

7665 BASESTATION ThisalarmisraisedifthebelowBTSfaultoccurs:


TRANSMISSION
ALARM Five failed logins to FTM due to wrong
user name or password(61500)
Thefaultisreportedwhenfiveconsecutive
failedloginattemptstotheFTMhavebeen
performed.

1.3.5.8 Activating and configuring the feature

ForanactivationinstructionrefertoFeatureActivationDocument

1.3.6 LTE679: LTE Local User Account Management


1.3.6.1 Introduction to the feature

ThisfeatureintroducesalocaluseraccountmanagementfortheeNB.

1.3.6.2 Benefits

Enhancedriskmanagementisachievedbyimprovedaccesssecurity.

1.3.6.3 Requirements
1.3.6.3.1 Software requirements

Table43 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL09

eNodeB LBTS0.5

MME

SAEGW

UE

NetAct

100 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.3.6.3.2 Hardware requirements

Thisfeaturedoesnotrequireanyneworadditionalhardware.

1.3.6.4 Functional description for LTE Local User Account Management

TheBTSSiteManageraccesstoaneNBisprotectedwithaconfigurablepassword.The
userauthenticationisdonelocallyintheeNB.Theusercanchangethelocalcredentials
(userpasswordandaccountname)withtheBTSSiteManager.

1.3.6.5 System impacts

Thefeaturehasnoadditionalimpactsonthesystem.

1.3.6.6 Sales information

TheLTE679:LTELocalUserAccountManagementfeatureisabasicsoftwarefeature.

1.3.6.7 User interface


1.3.6.7.1 Parameters for LTE679: LTE Local User Account Management

Table44:ParametersforLTE679:LTELocalUserAccountManagementshowsthe
parametersrelatedtoLTE679LTELocalUserAccountManagement.

Table44 ParametersforLTE679:LTELocalUserAccountManagement

Name Length

Useraccountname 4-16characters

Useraccountpassword 8-14characters

1.3.6.8 Activating the feature

Thisfeaturedoesnotrequireactivation.

1.3.7 LTE689: LTE IPsec Support


1.3.7.1 Introduction to the feature

TheIPsecsupportenablessecureeNBcontrolandbulkdatacommunicationbetween
eNBsandbetweeneNBsandcorenodesbyutilizingsecuretransportandapplication
protocols.IPsecsupportstheseparationbetweendifferenttypesoftraffic,likecontrol
planetrafficanduserplanetrafficfrommanagementtraffic,bydedicatedtransport
tunnels.
ThesecurityofeNBcontrol,user,synchronization,andmanagementplaneinterfacesis
increasedbyprovidingencryption,integrityprotectionandcommunicationpeer
authenticationwithIPsecaccordingRFC4301.

Issue:02B DN0978045 101


FeatureDescriptionsRL10 FeatureDescriptionsRL10

Itispossibletoenable/disableIPsecperconnection,forexampleperneighboreNB,or
percoresecuritygatewayandtoconfigureeachconnectionindependentlyintermsof
securitysettingsforeachremoteIPsecpeer.
ThesupportedIPseccapabilitiesfollow3GPPTS33.210forinterworkingpurposesand
furtherappliancerulesgivenbyTS33.401andTR33.821.SinceIPsecstandards
includeahighnumberofselectablesecurityparametersoptions,3GPPhas
recommendedtocutdownthenumberoftheseoptionsinordertoguarantee
interoperabilitybetweendifferentsecuritydomains.

1.3.7.2 Benefits

EnhancedriskmanagementisachievedbecauseofimprovedRANsystemsecurity.Itis
notnecessarytoinvestintoanyadditionalexternalHWtouseIPsecsupport.

1.3.7.3 Requirements
1.3.7.3.1 Software requirements

Table45 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL10

eNodeB LBTS1.0

MME

SAEGW

UE

NetAct OSS5.2CD3

1.3.7.3.2 Hardware requirements

Table46 Hardwarerequirementsfordifferentnetworkelements

Network element Required hardware

MME -

eNodeB

UE -

102 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.3.7.4 Functional description for IPsec Support


Supported IPsec capabilities
Services:Dataintegrityprotection,originauthentication,anti-replayprotection,and
confidentiality.ForFlexiBTS10,alsoIPpacketsreassembly(beforeIPsec
decryption).
Protocol:ESP(RFC4303)
IPsecmode:Tunnelmode
Encryption/cipheringalgorithms:
AES-128-CBC
3DES-192-CBC
NULL

Integrityprotectionalgorithm:HMAC-SHA-1-96
Identificationwith
IPaddresses
fullyqualifieddomainnames(FQDN)
distinguishednameID_DER_ASN1_DN

Authentication:DigitalcertificatesinX.509v3format
Keyexchange:
dualstackIKEv1andIKEv2
Diffie-Hellman:Group2(1024-bitMODP)

Suggestions for IPsec configuration


IPsecimplementationisoptimizedtoprovidebestthroughputandstrongestsecurity
levelwhenusingESPencapsulationwithAES-128-CBCencryptionalgorithmalongwith
theHMAC-SHA1-96integrityprotectionalgorithm.

IPsec for traffic separation


Controlplanetraffic,userplanetraffic,andmanagementtrafficcanbeseparatedwith
separateIPsectunnelsfromeachotherandfromanyotheroperator'strafficifanypartof
thetransportnetworkisshared.Theseparationalsoensuresthatfloodingattacksatthe
control/signalingnetworkwillhavenoimpacttotheseparateddatapaths.Fortraffic
separationinLTEIPSecVPNtunnelsasper3GPPNDS/IParesupported.

Parallel usage of IPsec and other secure transport protocols


Dependingonthetransportnetworkconfigurationandthenumberofnetwork
managementlocationsandapplicationstobeaddressed,IPsec(oneormorededicated
connections)aloneortogetherwithothersecuretransportprotocolscanbeusedand
configuredinparallel.

Properties of LTE689: IPsec Support


TheIPsecfeatureisoptional.Ifthelicenseisnotavailable,theeNBactslikeIPsecis
disabledwithanactivelicenseinplace.
TheeNBsupportsIPsecfunctionsontheinterfacestopeer-entities.

Issue:02B DN0978045 103


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.3.7.4.1 Transport security

Thissectioncoversthetransportsecurityfunctionsforthefollowinglogicalinterfaces:

S1-U:Userdatatransport(U-plane)betweeneNBandS-GW(GTP-Utunneling)
X2-U:Userdatatransport(U-plane)betweeneNBnodesduringhandover(GTP-U
tunneling)
S1-MME:Signalingtransport(C-plane)betweeneNBandMME(S1-APprotocol)
X2-C:Signalingtransport(C-plane)betweeneNBnodes(X2-APprotocol)
O&Mi/f:TransportofO&Mdata(M-plane)betweeneNBandO&MSystem

IETFSecurityArchitecturefortheInternetProtocolincludingIPsecandIKEisusedto
providetransportsecurityontheeNBfortheabovementionedinterfaces.
Figure13:TransportprotocolstackoverviewgivesonoverviewontheeNBprotocol
stacksandtheembeddedIPseclayer.

Figure13 Transportprotocolstackoverview

AteNBside,theIPsecfunctionisintegratedintotheeNB.Therefore,theeNBrepresents
asecuritydomainofitsownandcanactasSEGaccordingto3GPPTS33.210

1.3.7.5 System impacts

TheLTE689:IPsecSupportfeatureisrelatedtofollowingfeatures:

LTE665:LTEcertificatemanagement
LTE875:DifferentIPaddressesforU/C/M/S-plane

FTLBorFTIBarerequiredforthisfeature.

1.3.7.6 Sales information

Table47 Salesinformation

BSW/ASW License control in network element License control attributes

ASW SWAssetMonitoring -

ThefeatureisactiveforthewholeeNB.
ItisindicatedasactiveiftheipSecEnabledparameteristrue.

104 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.3.7.7 User interface


1.3.7.7.1 Parameters for LTE689: LTE IPsec Support

Table48:ParametersforLTE689:LTEIPsecSupportshowstheparametersrelatedto
featureLTE689LTEIPsecSupport.
AllparametersarelocatedinobjectIPSECC.

Table48 ParametersforLTE689:LTEIPsecSupport

Name Description Range Default value

ipSecEnabled Activation(TRUE)/deactivation FALSE,TRUE FALSE


(FALSE)ofIPsec

ipSeccId IdentificationofIPsecconfiguration 1...1,step1 1


Valueisalways1,notmodifiable

securityPolicies Listofsecuritypolicies Structure,


comprisingbelow-
mentioned
components

antiReplayEnable Activation(TRUE)/deactivation FALSE,TRUE TRUE


d (FALSE)ofanti-replay

antiReplayWindo Sizeofanti-replaywindow,only 64,128,256 256


wSize relevant,ifantiReplayEnabled
parameterisTRUE

authentication Determination,ifapresharedkey certificate(1),psk(2) certificate


oraceritificateisused
Inthisreleaseonlycertificateis
used

dpddelay Timedelaywithnomessages 10360sec, 10sec


receivedfromremotepeernode
step1sec
atexpiryDPDalivecheck
messageissent

dpdtimeout Timedelaywithnomessages 603600sec,step 120sec


receivedfrompeernodeonDPD 1sec
alivecheckmessagesatexpiry
DPDalarmisraised

encryptionMethod ESPencryptionalgorithm NULL, AES_128_CB


AES_128_CBC, C_OR_3DES_
AES_128_CBC_OR_3DES_192_C
3DES_192_CBC, 192_CBC(prior
BC(defaultvalue)means:
AES_128_CBC_OR ity1:
1. AES_128_CBCtriedfirst _3DES_192_CBC(p AES_128_CB
riority1:
2. 3DES_192_CBCtried
second

Issue:02B DN0978045 105


FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table48 ParametersforLTE689:LTEIPsecSupport(Cont.)

Name Description Range Default value

AES_128_CBC, C,priority2:
priority2: 3DES_192_C
3DES_192_CBC) BC)

IKEencryptionMet IKEencryptionalgorithm AES_128_CBC, AES_128_CB


hod 3DES_192_CBC, C_OR_3DES_
AES_128_CBC_OR_3DES_192_C
AES_128_CBC_OR 192_CBC(prior
BC(defaultvalue)means:
_3DES_192_CBC(p ity1:
1. AES_128_CBCtriedfirst riority1: AES_128_CB
AES_128_CBC, C,priority2:
2. 3DES_192_CBCtried priority2: 3DES_192_C
second 3DES_192_CBC) BC)

IKEprotocol IKEprotocolversion IKE_V1,IKE_V2 IKE_V2

ipSecStatus Treatmentoftrafficdatapackets PROTECT, BYPASS


matchingtheselectioncriteriaof DISCARD,BYPASS
theIPsecpolicy.
PROTECT:packetissubjecttothe
securityassociationssettings
DISCARD:packetisdiscarded
withoutanyfurtheractionor
notification,thatisitisnotpassed
toitsdestination
BYPASS:packetisdeliveredtoits
destinationwithoutanyfurther
IPsecrelatedprocessing

localIpAddress LocalIPaddressofthedatatraffic 7...15characters


packet,enteredindotteddecimal
format
ItcancontainasingleIPaddress
ortheIPaddressofasubnet.
Value0.0.0.0meansthatallIP
addressesareallowed

localIpPort PortnumberoflocalIPaddress -1...65535, -1


Ifvalue-1isconfigured,theIPsec step1
policyisvalidforallportsoflocal
IPaddress

localNetmask NetmaskoflocalIPaddress 7...15characters

localTunnelEndpoi LocalendpointofIPsectunnel,IP 7...15characters


nt addressenteredindotteddecimal
format

106 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table48 ParametersforLTE689:LTEIPsecSupport(Cont.)

Name Description Range Default value

remoteIpAddress RemoteIPaddressofthedata 7...15characters


trafficpacket,enteredindotted
decimalformat
ItcancontainasingleIPaddress
ortheIPaddressofasubnet.
Value0.0.0.0meansthatallIP
addressesareallowed

remoteIpPort PortnumberofremoteIPaddress -1...65535, -1


Ifvalue-1isconfigured,theIPsec step1
policyisvalidforallportsofremote
IPaddress

remoteNetmask NetmaskofremoteIPaddress 7...15characters

remoteTunnelEnd RemoteendpointofIPsectunnel, 7...15characters


point IPaddressindotteddecimal
format

policyNumber Securitypolicyordernumber-only 0...65535,step1


thelowestnumberofseveral
equallymatchingpoliciesisapplied

protocol Protocolinformationofthetraffic -1...254,step1 -1


datapacket
Ifvalue-1isconfigured,theIPsec
policyisvalidforallprotocols

saMaxLifeTime LifetimeofCHILDSAs(security 30086400sec, 86400sec


associations).Afterthetimerhas step1sec
expiredforthesecurity
association,anewsecurity
associationisnegotiated.

ikeAssociations ListofIKEassociations Structure,


comprisingbelow-
mentioned
components

peerState StateofIKEpeer 0...1000characters

remoteTunnelEnd RemoteIPsectunnelendpointIP 7...45characters


point address

ikeId IdentificationofIKEassociation 1...1,step1 1


databasevalueisalways1

Issue:02B DN0978045 107


FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table48 ParametersforLTE689:LTEIPsecSupport(Cont.)

Name Description Range Default value

operationalState OperationalstateofIKE DISABLED, ENABLED


associationsobject-summarizes ENABLED
operationalstatesofindividualIKE
associations

associationList InformationrelatedtoIPsec 1...4000characters


associations

sadbId IdentificationofIPsecassociation 1...1,step1


database-valueisalways1

g Incaseanexistingsecuritypolicyischangedordeleted,orthereisanew
policyadded,consequentlytheeNBIPsecapplicationisrestartedandthe
securityassociationsresultingfromtheconfiguredsecuritypoliciesarere-
established.Thiscausesatemporarytransmissionbreak.
TheeNBIKEv1applicationislimitedregardingusageofthe'remoteIpAddress'
parameterfortheconfigurationofmultiplesecuritypolicies.ForapropereNB
IKEv1operationitmustbeensuredthatthe'remoteIpAddress'parametersofall
policiesdonotoverlapinthecoveredranges.Asanexceptiontothat,one
policywith'remoteIpAddress=0.0.0.0'meaningallIPaddressesareallowedfor
theremotepeer,canbeconfigured.
IncaseofinterworkingwithCiscoWSGassecuritygatewayandintendedeNB
initiatedre-keyingofIKEsecurityassociationsinIKEv2,theeNBdefault
configurationforIKEencryptionmustbechangedbecauseofnotstandard
compliantbehaviorofCiscoWSGinthisregard.Forsuchconfigurations,the
'IKEencryptionMethod'parametermustbeeithersetto'AES_128_CBC'or
'3DES_192_CBC',butmustnotbesetto
'AES_128_CBC_OR_3DES_192_CBC'.

1.3.7.7.2 Alarms for LTE689: LTE IPsec Support

Table49 AlarmsforLTE689:LTEIPsecSupport

Alarm Alarm name Condition


number

61030 DeadPeer AdeadpeerwasdetectedinoneoftheIPsecassociationsofthe


Detected FTM.
Possibly

acableiscutorthereisnocableconnectedtothe
interface
thesignalisexcessivelyattenuated
theportattheconnectedfarendnodeisswitchedoff

108 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table49 AlarmsforLTE689:LTEIPsecSupport(Cont.)

Alarm Alarm name Condition


number

7665 BASE ThisalarmisraisedifthebelowBTSfaultoccurs:


STATION
TRANSMISS Dead Peer Detected (61030)
IONALARM Thefaultisreportedwhenadeadpeerwasdetectedin
oneoftheIPsecassociationsoftheFTM.
Possibly:
acableiscutorthereisnocableconnectedtothe
interface
thesignalisexcessivelyattenuated
theportattheconnectedfarendnodeisswitchedoff

1.3.7.7.3 Counters for LTE689: LTE IPsec Support

Table50:CountersforLTE689:LTEIPsecSupportshowscountersrelatedtoLTE689:
LTEIPsecSupport.

Table50 CountersforLTE689:LTEIPsecSupport

PI ID Counter name Description

M51125C0 Protected_ESPFramesTx NumberofsuccessfullyencryptedESPpackets


inegressdirection

M51125C1 Protected_ESPFramesRx NumberofsuccessfullydecryptedESPpackets


iningressdirection

M51125C2 Discarded_ESPFramesTx NumberofdroppedESPpacketsinegress


directionbecauseoffailedencryption

M51125C3 Discarded_ESPFramesRx NumberofdroppedESPpacketsiningress


directionbecauseoffaileddecryption

M51125C4 Bypassed_FramesTx NumberofbypassedESPpacketsinegress


direction

M51125C5 Bypassed_FramesRx NumberofbypassedESPpacketsiningress


direction

1.3.7.8 Activating and configuring the feature

Foractivatingandconfiguringthefeature,seeFeatureActivationDocumentation.

Issue:02B DN0978045 109


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.3.8 LTE692: LTE Firewall Support


1.3.8.1 Introduction to the feature

ThisfeatureprovidesaninternalfirewalltoprotecttheeNB.

1.3.8.2 Benefits

EnhancedriskmanagementisachievedbecauseofimprovedRANsystemsecurity.
CAPEXsavingsareachievedbecauseitisnotnecessarytoinvestintoanyadditional
externalHWtousethisfeature.

1.3.8.3 Requirements
1.3.8.3.1 Software requirements

Table51 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL10

eNodeB LBTS1.0

MME

SAEGW

UE

NetAct

1.3.8.3.2 Hardware requirements

Thisfeaturedoesnotrequireanyneworadditionalhardware.

1.3.8.4 Functional description for LTE Firewall Support

TheeNBsupportsintegratedfirewallfunctionality.Accesscontrolaimstopreventthe
eNBfromhandlingtraffic,servicesandapplicationto/fromunauthorizedhosts.
IPpacketfilterrulesarebasedonsourceanddestinationaddresses,sourceand
destinationportnumbersandprotocols.
IngressratelimitingreducesoverloadsituationsontheeNB,whereasegressrate
limitingprotectsothernetworknodesfromunwantedtrafficgeneratedbytheeNB.
ProtectionagainstDenialofServiceisappliedontheeNB.
Statisticisimprovedbyimplementingappropriatecountersandtrafficlogging.

110 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

Protected interfaces
TheeNBfirewallfunctionalityappliestoallexternalinterfaces,forexampleS1-MME,S1-
U,X2-C,X2-UandO&M.
Incasetheratelimitisexceeded,theexceedingtrafficwillbedropped.Theratelimitis
definedaccordingtotheresourcecapacityoftheeNB.

Firewall characteristics
Thefirewallfunctionalityisenabledonprinciple,thatisitcannotbeswitchedoff.
Furthermore,thefirewallfilterrulesarefixed,thatistheycannotbeconfigured.
ThefixedfirewallrulesarederivedfromtheLTEIPtopologysuchthattheyare
appropriateforeachplane,forexampleforC-planetheeNBacceptsallSCTPtraffic
senttotheeNBC-planeIPaddress.StaticrulesallowtoautomaticallycoverrelevantIP
addresses,ports,protocols,etc.andthusconfigurationerrorsareavoided.

ICMPv4
ICMPv4issupportedwiththefollowingmessages:

Table52 Messages

message receive direction (Rx) transmit direction (Tx)

DestinationUnreachable x x

TimeExceeded x

ParameterProblem x

EchoRequest x x

EchoReply x x

ItispossibletodisableeNBresponsestoICMPPing(EchoRequest)messagesand
traceroutemessagesreceivedovertheexternalinterfaces.

1.3.8.4.1 Firewall functionality

Thefollowingfirewallfunctionalitiesareprovided:

ingress IPpacketfiltering
ingressratelimiting
egressratelimiting
DoScountermeasures

Ingress IP packet filtering


TheingressIPpacketfilterfiltersingressIPtrafficbasedonsourceanddestinationIP
addresses(includingIPsubnets),sourceanddestinationportnumbers,andprotocol.
Filtercriteria/rulesarefixed.IngressIPpacketswhichdonotmatchanyofthedefined
ruleswillbedropped.ComparedtothegeneralstatelessoperationofIPpacketfiltering,

Issue:02B DN0978045 111


FeatureDescriptionsRL10 FeatureDescriptionsRL10

thereisanexceptionforhandlingofICMPoneNBside.ICMPishandledinastateful,for
exampleanegressICMPmessageisevaluatedregardingtheincludedtargetaddressin
ordertoacceptthecorrespondingingressICMPmessagefromthisaddress.

Ingress rate limiting


InordertoavoidanoverloadoftheeNBinternalsubsystemsandtolimittheeffectof
DenialofServiceattacks,theingresspacketratecanbelimited.Supportedmessages
areICMPandARP.
InordertoavoidanoverloadoftheNEinternalsubsystemsandtolimittheeffectofa
DenialofServiceattack,theingresspacketratecanbelimitedseparatelyforeachofthe
followingtrafficaggregates:

U-plane
C- plane
M-plane
S-plane(ToP)
ICMPEchoRequest
ICMPEchoReply
ARPRequestandReply

Trafficexceedingthedefinedratelimitswillbedropped.Trafficexceedingoneaggregate
willnotaffectthetrafficforotheraggregates.Theratelimitsaredefinedaccordingtothe
capacityoftheeNBinternalsubsystemsandtheshareoftheinternalresourcesthatthe
trafficisallowedtouse.

Egress rate limiting


TheegresspacketrateofthefollowingICMPmessagesislimited:

EchoRequest
EchoReply
TimeExceeded
DestinationUnreachable

DoS countermeasures
TheeNBisprotectedagainstthefollowingDoSattacks:

Smurf attack:
Inthesmurfattack,attackersareusingICMPechorequestpacketsdirectedtoIP
broadcastaddressesfromremotelocationstogenerateDoSattacks.
Teardrop attack:
SomeimplementationsoftheTCP/IPfragmentationreassemblycodedonotproperly
handleoverlappingIPfragments.ThisattackwouldaffectonlytoO&Msince
reassemblyisnotsupportedbyU-plane/C-plane.
Land attack:
ALandattackinvolvessendingaspoofedSYNpacketwiththetargethost'sIP
addressandanopenportasboththesourceandthedestination.Thisattackwould
affectonlyO&MsinceTCPisnotusedbyU-plane/C-plane.
TCP SYN attack:

112 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

ForTCPprotocol,SYNmessagesaresenttothetargetwithnonexistentsource
addresses,causingtheresourcestobereserveduntilatime-outhappens.This
attackwouldaffectonlytoO&MsinceTCPisnotusedbyU-plane/C-plane.
Ping of Death attack:
AnICMPEchoRequestmessageissenttothetargetwithsizeover65535bytes.
Thisisnotalegalpacketsizeanditcouldcausetheoperatingsystemtocrash.

1.3.8.4.2 Firewall filter

Filterrulesarefixed.

Predefined packet filter rules


Thepacketfilterisautomaticallyconfiguredtoallowthefollowingapplicationsand
protocolsfortheapplicableaddressesandports,basedonthepredefinedconfiguration:

Controlplane(SCTP)
IKE(UDP)
TimingoverPacket(UDP)
PW(MPLS)
LDAP(TCP)
CMP(TCP)

Ifanyoftheapplicationsaboveisnotenabled,therespectivefilterconfigurationwillnot
beperformed.RulesincludesourceanddestinationIPaddresses,sourceand
destinationportnumbersandprotocol.

icmpResponseEnable parameter
TheicmpResponseEnableparametercontrolstheeNBresponsetoICMPand
tracerouterequests.Thefunctionalityisperdefaultenabled.Thisparametercanbe
configuredbyNetActorBTSSiteManager.

1.3.8.4.3 Logging

Thefirewallallowstologdiscardedanddroppedpackets.

Discarded packets statistic


NumberofpacketdiscardedbyeNBfirewallismeasured.Countersareimplementedfor:

1. IngressIPpacketfiltering:
DiscardofIPpacketsreceivedwhichdonotmatchthedefinedfilteringrules.
2. Ingressratelimiting
DiscardofIPpacketsreceivedanddroppedinordertoavoidanoverloadoftheeNB
internalsubsystems.

ThisreportisusefultodetectattacksonIPlayer.Itshouldbementionedthatalso
misconfigurationsattheIPlayer,forexampleaconfigurationofwrongIPaddressesmay
causeIPpacketstobediscardedaccordingtothefilteringrules.

Traffic logging
Itispossibletologthetrafficwhichisdroppeddueto:

Issue:02B DN0978045 113


FeatureDescriptionsRL10 FeatureDescriptionsRL10

filteringrules
ratelimiting

Loggingstopsautomaticallywhenthereisnomorestoragespaceavailable.Itispossible
tostartandstopthetrafficloggingmanually.Thefollowingistraced:

destinationandsourceaddresses
protocoltype
destinationandsourceport(ifpresent)
messagetypeandcode(forICMP)
cause(filteringrule,ratelimitexceeded)
timestamp

Trafficlogginghelpstodetermineaproblemintheconfigurationofthefilteringrules,and
tomonitorwhichtypeoftrafficisusedforDoS.TrafficlogsareavailableonlytotheSite
Manager.

1.3.8.5 System impacts

Therearenoimpactsrelatedtothefeature.

1.3.8.6 Sales information

TheLTE692:LTEFirewallSupportfeatureisanadditionalsoftwarefeatureandthe
licenseistrust-based(SWAssetMonitoring).
ThefeatureisactivatedforthewholeeNB.Nospecialactivationisnecessary.

1.3.8.7 User interface


1.3.8.7.1 Parameters for LTE692: LTE Firewall Support

Table53:ParametersforLTE692:LTEFirewallSupportshowsparametersrelatedto
LTE692:LTEFirewallSupport.
AllparametersarelocatedinobjectIPNO.

Table53 ParametersforLTE692:LTEFirewallSupport

Name Description Range Default


value

icmpResponseEnabled ThisparametercontrolsiftheBTS TRUE, TRUE


respondstoICMPandtraceroute FALSE
requests

1.3.8.7.2 Counters for LTE692: LTE Firewall Support

Table54:CountersforLTE692:LTEFirewallSupportshowscountersrelatedtoLTE692:
LTEFirewallSupport.

114 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table54 CountersforLTE692:LTEFirewallSupport

PI ID Counter name Description

M51126C0 ipRmDroppedPacketsRateLimiting Numberofdroppedpacketsdueto


ingressratelimiting

M51126C1 ipRmDroppedPacketsFiltering Numberofpacketsdiscardeddueto


ingresspacketfilteringviolations

1.3.8.8 Activating and configuring the feature

Thisfeatureneedsnospecialactivationprocedure.

1.3.9 LTE746: IP based filtering for BTS Site Support Equipment


1.3.9.1 Introduction to the feature

ThisfeatureallowsselectiveaccessoftheIPdatacommunicationnetwork(DCN)
towardssitesupportequipmentandviceversa.
FilteringisdonebasedonIPaddressesandthesizeofmaximumtransmissionunit
(MTU).Itimprovestheprotectionof:

sitesupportequipmentfromharmfulIPDCNtraffic
IPDCNfromharmfulIPtrafficoriginatedfromsitesupportequipment

1.3.9.2 Benefits

Theprotectionagainstharmfulmanipulationofthesitesupportequipmentconfiguration
viaIPDCNisimproved.

1.3.9.3 Requirements
1.3.9.3.1 Software requirements

Table55 Softwarerequirementsfordifferentnetworkelements

Network element Required software release

Systemrelease RL10

eNodeB LBTS1.0

MME

SAEGW

UE

Issue:02B DN0978045 115


FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table55 Softwarerequirementsfordifferentnetworkelements(Cont.)

Network element Required software release

NetAct OSS5.2CD3

1.3.9.3.2 Hardware requirements

Thisfeaturedoesnotrequireanyneworadditionalhardware.

1.3.9.4 Functional description for IP based filtering for BTS Site Support
Equipment

TheeNBprovidesaccesstositesupportequipment(forexamplebatterybackupunits
etc.)viaadditionalethernetinterfaces.Typically,thistypeofIP-basedequipmentdoes
notprovideanownIPpacketfilterorafirewall.Thus,thesitesupportequipmentis
directlyaccessibleifthereisnopacketfilterateNBside.Therefore,theeNBprovidesan
IPpacketfilterservicethatprotectsthesitesupportequipmentfromharmfulnetwork
traffic,butalsoprotectsthenetworkfromunintendedtrafficfromthisinterface.
ItispossibletodefineIPaddressesorIPsubnetsthathaveaccesstoanysitesupport
equipment.IPpacketsfrom/toanysitesupportequipmentwhichdonotmatchanyofthe
configuredIPaddresses/subnetsaredropped.
Themaximumtransmissionunit(MTU)oftheeNBinterfacetowardsbackhaulnetworkis
alsoconfigurable.TheoperatormustsettheMTUsizetoavaluelargeenoughto
accommodateIPpacketsfromSSE.Theconfiguredsizemustincludethesizeofa
possibleoverhead(upto73bytesifIPsecisappliedtoSSEtraffic).

g MakesuretoconfiguretheMTUcorrectly.Ifpacketsarrivingfrom/goingtoSSE
havesizelargerthantheconfiguredMTU,thepacketsaredropped.Formore
informationontheconfigurationofMTU,seeLTETransportfunctionalarea
description.

TheconfigurationofthefeatureisdoneusingBTSSiteManagerfromalocalorremote
site,orbyNetAct.

1.3.9.5 System impacts

Thefeaturehasnoadditionalimpactonthesystem.

1.3.9.6 Sales information

TheLTE746:IPbasedfilteringforBTSSiteSupportEquipmentfeatureisabasic
softwarefeature.

1.3.9.7 User interface


1.3.9.7.1 Parameters for LTE746: IP based filtering for BTS Site Support Equipment

Table56:ParametersforLTE746:IPbasedfilteringforBTSSiteSupportEquipment
showsparametersrelatedtoLTE746:IPbasedfilteringforBTSSiteSupportEquipment.

116 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

AllparametersarelocatedinobjectIPRM.

Table56 ParametersforLTE746:IPbasedfilteringforBTSSiteSupportEquipment

Full name Description Range / Step Default


value
(Short name)

RmExceptions Filterrulesdefinedfortrafficfrom/to Structure,


attachedsitesupportequipment(SSE) comprising
trafficfrom/toSSEto/fromremote below-
peersisonlyallowediftheremote mentioned
peersIPaddressisconfiguredinthe components
filterrule.BydefaultSSEcannotbe
accessed,i.e.aconfiguredremote
peersIPaddressisanexceptiontothe
defaultbehavior.

sourceTwoDiscr Descriptionofremotepeerasdedicated SINGLE,


RANGE,
SINGLE:asingleIPaddress WILDCARD
RANGE:rangeofIPaddresses
(IPaddressandsubnetmask)
WILDCARD:anyIPaddress
allowed

sourceTwoIpAddr MeaningfulonlyifsourceTwoDiscris 715 0.0.0.0


definedasSINGLEorRANGE characters

SINGLE:IPaddress
from/towardstrafficisallowed
RANGE:upperlimitoftheIP
addressrangefrom/towards
whichtrafficisallowed,entered
indotteddecimalformat
Value0.0.0.0meansaddressnotused.

sourceTwoNetMask RelevantonlyifsourceTwoDiscris 715 0.0.0.0


definedasRANGE;whenappliedto characters
sourceTwoIpAddr,theallowedrangeof
IPaddressesisderived.Enteredin
dotteddecimalformat.
Value0.0.0.0meansnetmasknotused.

userLabel UserdefinedidentificationoftheSSE 140


specificfilterrule characters

iprmId Identificationofuniqueinstanceofclass 1...1,step1


IPRM
Valueisalways1,notmodifiable

Issue:02B DN0978045 117


FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table57:ParameterforconfiguringMTUsize.showsparameterfortheconfigurationof
theEthernetinterfaceMTUsize.TheparameterisapartoftheLTE664:LTETransport
ProtocolStack.ForthecompletelistofparametersrelatedtoLTE664,seeParameters
forLTEtransport.

Table57 ParameterforconfiguringMTUsize.

Full name Description Range / Step Default


value
(Short name)

Maximum transfer Thesizeofthemaximumtransferunitof 576...1608 1500bytes


unit (MTU) theEthernetinterface. bytes

1.3.9.8 Activating the feature

Thisfeaturedoesnotrequireactivation.

1.3.10 LTE913: LTE NEBS compliant OMS


1.3.10.1 Introduction to the Feature

OMS(OperationandManagementServer)hardwareisavailableaspre-certifiedNEBS
(NetworkElementBuildingStandard)complianthardware.NEBScomplianthardware
fullfillsverystrictrequirementsonreliability,productsafety,electromagneticcompatibility
andenvironmentalrequirements,andmeetsthehigheststandardsfor
telecommunicationnetworks.

1.3.10.2 Benefits

OperatorshaveacceptedtheNetworkEquipmentBuildingStandard(NEBS)which
ensurescommoncriteriafornetworkintegrity,inparticularinenvironmentswhere
equipmentfrommultiplevendorsisinvolved.
NEBScomplianceallowsoperatorstodeliverreliablenetworkperformancewith
uninterruptedserviceevenduringcatastrophicevents.NEBScompliancealsoprovides
energysavings.Additionally,operatorscanrelyontheNEBScompliantequipment
withouthavingtotestthereliabilityaspectscoveredunderNEBS.Asaresult,itiseasier
tointroducenewequipmenttoanetwork,toloweronesOPEX,andtoreducetimeto
marketfornewnetworkroll-outs.

1.3.10.3 Functional Description

OMShardwareisavailableaspre-certifiedNEBScomplianthardware.
NEBSisnotalegalorregulatoryrequirementbutarequirementbymajorNorthAmerica
operatorsforequipmentthatgoesintheCentralOffice.SinceinmostcasesOMSis
suchCentralOfficeequipment,NEBScomplianceisonerequirement.
NEBScomplianthardwarefullfillsverystrictrequirementsonreliability,productsafety,
electromagneticcompatibilityandenvironmentalrequirements,andmeetsthehighest
standardsfortelecommunicationnetworks.NEBScomplianthardwarecanbeblade-

118 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

basedorrack-based.SoftwarechangesonNEBScomplianthardwarearenotexpected
tocauseretestforNEBS.However,hardwareandplatform/configurationchangesmade
toNEBShardwaremaycreatetherequirementtoretesttheequipment.
NEBScomplianceisdividedintothreelevels.Thehighestlevel(3)istheminimumto
assureoperabilitywithinnetworkfacilityenvironmentunderextremeconditions.
NEBSenvironmentalcriteriaincludeElectromagneticCompatibility(EMC)andSafety
requirements,including:

ElectrostaticDischarge(ESD)
ElectromagneticInterference(EMI)
RadiatedEmissions-ElectricFields
RadiatedEmissions-MagneticFields
ConductedEmission(ACPowerLeads-Voltage)
ConductedEmission(ACandDCPowerandSignalLeads-Current)
ConductedEmission(AnalogVoicebandLeads)

LightningandACPowerFault
Bondingandgrounding
DCPotentialDifference
ElectricalSafety
AmbientTemperatureandHumidity
AirborneContaminant(outdoorlevel)
FireResistance
Corrosion

Furthermore,NEBScomplianceguaranteeshighestreliabilityofthenetworkequipment
inEarthquake4zones.

1.3.10.4 Requirements

Notapplicable.

1.4 Flexi Multiradio BTS LTE Site Solution features


from previous releases for RL20
1.4.1 Introduction to the Flexi Multiradio BTS Site Solution
features
ThissectionintroducestheFlexiMultiradioBTSSiteSolutionfeaturesforLTERL10.
Furtherinformationonthefeatures,includinginstallationinstructions,willeventuallybe
availableinPIC.

Issue:02B DN0978045 119


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.4.2 Cell-related features


1.4.2.1 LTE cell bandwidth features: LTE112,LTE114, and LTE115
1.4.2.1.1 Introduction

Thesefeaturesareofferedaccordingto3GPP-specifiedbitratesandsupportedUE
capability.

LTE112:Cellbandwidth-20MHzoffersfullLTEcapacitywith20MHzLTE
cellbandwidth
LTE114:Cellbandwidth-10MHzofferssupportforthe10MHzLTEcellbandwidth
LTE115:Cellbandwidth-5MHzofferssupportforthe5MHzLTEcellbandwidth

1.4.2.1.2 Functional description

TheLTEcell/carrierbandwidthforeachbandwidthoptionissetusingasoftware
configurationparameter.TheRFhardwareispreparedtosupportbandwidthsupto20
MHz,dependingonthe3GPPbandand3GPPspecification.

1.4.2.1.3 Benefits

LTEcanoperateinanumberofdifferentfrequencybands.HighLTEBTSandcell
averageandpeakdataratesareofferedaccordingto3GPPspecificationsandUE
capability.
offersthefollowingcellbandwidthfeatures:

1.4.2.1.4 Activating the feature

Thisfeatureislicense-based.

1.4.2.2 LTE97: Cell radius max 77 km


1.4.2.2.1 Introduction

TheFlexiMultiradioBTScellradiusissupporteduptothemaximumof77kmbyusing
cellparametersettingsdefinedin3GPP.

1.4.2.2.2 Benefits

Thisfeatureoffersextendedcellcoverageforruralandcoastalareasusinghighantenna
towersandhighmountainsitelocations,coveringthesamecellareaastheGSM
extendedcell.NonewLTEsitesareneededforruralcoverage.

1.4.2.2.3 Functional description

ThisfeatureenablesthesupportofLTEcellsofupto77kmaccordingto3GPPBTScell
parametersettings.Theactualobtainedcoveragedependsonmanypractical
parameters,forexampletheRFbandinuse,BTSandUEantennaheight,networktraffic
loadconditions,andradioconditions.Detailednetworkplanningtoolsareneededto
estimatetheobtainablecoverageprobabilityforaspecificBTSsiteandterrain.

120 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.4.2.2.4 Activating the feature

Thefeatureisactivatedbyspecialsoftwareparameters,usingstandardFlexiMultiradio
BTSSystemandRFModules.

1.4.3 Antenna line features


1.4.3.1 LTE71: 2-way RX diversity (MRC)
1.4.3.1.1 Introduction

Thisfeatureprovidestwo-wayreceivediversityforenhanceduplinkcoverage.

1.4.3.1.2 Benefits

Receiverdiversityisawell-known,robustmethodforincreasingthereceivedsignal
strengthandqualitybyeffectivelydoublingthereceivedsignalpowerandthusimproving
theperformanceagainstnoise.Itcancelsthesignaldropoutscausedbymultipath
fading.

1.4.3.1.3 Functional description

ReceiverdiversityisastandardfeatureforFlexiMultiradioBTSconfigurations.The
signalsfromthetworeceiverantennasareseparatelyamplifiedanddownconvertedand
finallycombinedinbasebandprocessingusingMaximumRatioCombining(MRC).The
FlexiMultiradioBTSisabletooperatewithlimiteduplinkperformance(ULcoverage)
withjustoneRXreceiverincaseoneofthetwoRXsignalsismissing.

1.4.3.2 LTE160: Flexi Multiradio BTS 3GPP antenna tilt support


1.4.3.2.1 Introduction

TheFlexiMultiradioBTShasintegratedantennatiltcontrolhardwareintheradiomodule
tocontrolthe3GPPtiltantennas.

1.4.3.2.2 Benefits

Themainbenefitsofremoteelectrictiltmanagementare:

itsimplifiesandspeedsupthenetworkoptimizationprocess,allowingthenetworkto
beoptimizedregularlyandindependentlyofengineeringresources,siteaccessor
weatherconditions
itcreatesthecapabilitytoreacttochangingloadpatternsandtotunethenetwork,
ensuringoptimalnetworkperformanceforallservices
iteliminatestheneedforsitevisitstotiltantennasandhencetheneedtoturnoff
sites.Thisleadstoconsiderablesavingsinoperationalcostsandavoidsthelossof
revenueduetositedowntime.
itreducestheoverallantennastockholdingandimproveslogisticsbecauseofa
radicalreductionofantennavariants,thankstotheuseofantennaswith
continuouslyvariabledowntilt.

Inshort,theantennatiltfeaturedeliverssavingsbecauselesseffortontiltingisrequired
andbetterradioRFperformanceisachieved.

Issue:02B DN0978045 121


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.4.3.2.3 Functional description

AntennatiltisintegratedintotheRFModuleoftheFlexiMultiradioBTS.ItfeedsDC
powertotheantennaandcontrolstheantennatilting.This3GPP-specifiedantenna
tiltingfunctionalitydoesnotrequireadditionalhardware.

1.4.3.2.4 Management data

ThissectionsliststheparametersrelatedtoLTE160:FlexiMultiradioBTS3GPPantenna
tiltsupport.

Table58 TheparametersrelatedtoLTE160:FlexiMultiradioBTS3GPPantennatilt
support.

Parameter name MO class Description

ALDCVoltageEnabled ANTL DefinesifDCpoweris


enabled/disabledforan
antennaline.

Communication3gpp ANTL Definesifdevicescan


Enabled functionalityis
enabled/disabledforan
capable3GPPantennaline.

Angle RET Definestheelevationangle.

Calibrate RET Definestheusageof


calibration.

CalibrationDone RET Definesifcalibrationisdone.

ConfigurationFileDLNeeded RET DefinesifConfigurationFile


DLisneeded.

ConfigurationDone RET Definesifconfigurationis


done.

ConfigurationFile RET Thisparameterisusedto


storeandtransferdevice-
specificconfigurationdatato
theBTS.

Manufacturer RET Definesthemanufacturerof


thedevice.

MaxAngle RET Definestheminimum


allowedelectricaltiltvalue.

MechanicalAngle RET Definesthemechanicaltilt


fixedbythegeometryofthe
installation.

122 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

Table58 TheparametersrelatedtoLTE160:FlexiMultiradioBTS3GPPantennatilt
support.(Cont.)

Parameter name MO class Description

MinAngle RET Definestheminimum


allowedelectricaltiltvalue.

SWVersion RET DefinestheRETFirmware


SWVersion.

1.4.3.2.5 Activating the feature

Thisfeatureislicense-based.

1.4.3.3 LTE94: Feederless site


1.4.3.3.1 Introduction

ThefeederlessLTEBTSsiteisasitewheretheFlexiMultiradioBTSRFModuleis
locatedclosetoantennas,sotraditionallongantennafeedersarenotneeded.

1.4.3.3.2 Benefits

ThefeederlesssitesolutionusingstandardFlexiMultiradioBTSIP65RFandSystem
ModulesoffersaflexiblewaytooptimizeBTSsiteperformance.BTSsitelevelsavings
areachievedbecause:

itiseasiertoacquirenewsites
co-sitingwithexisting2Gand3Gbasestations,feedersandantennasiseasier
noneedoflongandthickantennafeedersinstallations
optimizedDLandULRFperformance-coverageandcapacity-isachieved
noMHAsareneeded
standardRFModulesareusedinthefeederlessinstallationoption,whichsimplifies
logisticsaswellastheinstallationworkitself.

OneFlexiMultiradioBTSRFModulecansupportmax60Wforuptothreesectorsand
cells.TwoFlexiMultiradioBTSRFModulescansupportmax60W+60W2TXMIMO
foruptothreesectorsandcells.ThreeFlexiMultiradioBTSRFModulescansupport
max60W+60W2TXMIMOforonesectorwithHWcapabletosupport4RXdiversity.

1.4.3.3.3 Functional description

AtafeederlessBTSsite,theFlexiMultiradioBTSRFModuleislocatedclosetothe
antenna.ThedistancebetweentheRFModuleandtheantennaisonlyafewmeters,so
notraditionalfeedercablesarerequired.TheSystemModulecanbefreelylocatedbyan
opticalinterfaceupto200metersawayfromtheRFModule.Typically,theSystem
Moduleisinstalledclosertothetransmissionterminationpointandothersitesupport
equipment,suchasanexistingBTSshelter,orinsideaBTSorSiteSupportcabinet,ata
locationwitheasieraccess.TheSystemandRFModulescanbeinstalledindoorsand
outdoors.

Issue:02B DN0978045 123


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.4.4 Flexi Multiradio BTS RF Modules


1.4.4.1 Introduction

ThehardwareoftheFlexiMultiradioBTS3-sectorRFModulesforLTEisidenticaltothe
existingDualandSingleFlexiWCDMABTSRFModules.Theenvironmentalprotection
classofthemodulesisIP65.Themodulesare3UhighwithFlexiMultiradioBTS
platformmechanics.TheRFModulesareabletosupportone,twoorthreesectorswith
upto60WoutputpowerattheBTSantennaconnector.Theycanbeusedasapowerful
one-sectorRemoteRadioHead(RRH)withthemaximumof60W+60W2TXMIMOfor
onecell.ThebasicLTEconfigurations-1omni,1+1,1+1+1withthemaximumof20
MHzLTEbandwidthand1TX/2RXfortwoormorecells-areoffered.Softwarelicenses
enablethe8,20,40or60Wmodepersector.TheFlexiMultiradioBTSRFModulescan
beusedinfeederlessanddistributedBTSsites.

1.4.4.2 Benefits

TheFlexiMultiradioBTS3-sectorRFModulesofferthefollowingbenefits:

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

1.4.4.3 LTE85: Flexi 3-sector RF Module 2600 (FRHA)

TheFlexiMultiradioBTSRFModulefor2600MHz(FRHA)offers3X60Woutputforthe
3GPPband7.

1.4.4.4 LTE99: Flexi 3-sector RF Module 1.7/2.1 (FRIE)

TheFlexiMultiradioBTSRFModulefor1.7/2.1GHz(FRIE)provides1.7GHzULand
2.1GHzDL.The3GPPbands4and10aresupportedandtheRFbandwidthrangeis60
MHz.

1.4.4.5 LTE437: Flexi 3-sector RF Module 800EU

TheFlexiMultiradioBTSRFModulefor800MHz(FRMA)supportsthe3GPPband20.

124 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.4.4.6 LTE96: MIMO 2TX configuration with 3-sector RF Module


1.4.4.6.1 Introduction

Downlink2TXMIMOuptothreesectorsissupportedwithtwothree-sectorRadio
Moduleswithupto60W+60WRFpowerpercellorsector.

1.4.4.6.2 Benefits

JusttwoFlexiMultiradioBTSRFModulesareneededtobuildahighperformancethree-
sectorsitesupporting2TXdownlinkMIMO.Themaximumoutputpoweris60W+60W
percellorsector.Theothersoftware-configurableRFTXoutputleveloptionsare20W+
20Wand40W+40W.

1.4.4.6.3 Functional description

TwoRFModulescanbeconfiguredtooperateasparallel,sothateachmoduleprovides
onebranchofthe2TXMIMOuptoathree-sectorsiteconfiguration.ThemaximumTX
poweroneach3GPPRFbanddependsontheRFModuleversion.

1.4.5 Flexi Multiradio BTS Remote Radio Heads


1.4.5.1 Benefits

Theone-sectorFlexiMultiradioBTSRemoteRadioHeads(RRHs)areabletosupport
2TXMIMOwithhighoutputpower.ThemodulesareIP65-protected,sotheycanbe
installedoutdoorsclosetotheantennas,maximizingtheBTSsitecapacityandcoverage
foronesector.

1.4.6 Cabinets and other Flexi Multiradio BTS hardware


1.4.6.1 LTE79: Flexi Indoor (FCIA) and Outdoor (FCOA) Cabinets
1.4.6.1.1 Introduction

OptionalIndoor(FCIA)andOutdoor(FCOA)CabinetsareavailableforFlexiMultiradio
BTSinstallationswhereadditionalprotectionisneededorwherethelargenumberof
modulespreventsthestackedinstallation.Thecabinetsareintroducedhereonlybriefly;
furtherinformation,forexampleinstallationinstructions,isavailableinPICaspartofthe
LTERadioAccess,Rel.RL,OperatingDocumentation.

1.4.6.1.2 Benefits

TheFlexiMultiradioBTSIndoorCabinet(FCIA)providesadditionalinstallationsupport
forlargeconfigurationswherethestackedinstallationisnotpossible.TheFlexiMultiradio
BTSOutdoorCabinet(FCOA)providesadditionalshieldingfortheBTSsiteandprovides
spaceforauxiliarydevices,suchasahigh-capacitybatterybackupunit(BBU).

Issue:02B DN0978045 125


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.4.6.1.3 Functional description

The Flexi Multiradio BTS Indoor Cabinet (FCIA)


TheFlexiMultiradioBTSmultipurposeIndoorCabinet(FCIA)isanoptionforindoorsites
whereacabinetisneeded.Itprovides36UspacefortheFlexiMultiradioBTSmodules
andforoptionalsitesupport.Themainapplicationsare:

thefuture-proofmultipurposecabinetcanhousetwoorthreeseparateBTSs,for
exampleWCDMAand/orEDGE,and/orWimax,and/orLTE
severalhoursofsharedbatterybackupforasinglecabinetwithoneortwoBTSs
(WCDMA,EDGE,WiMaxorLTE)
spacefortheoperator'sown19-inchunits
earthquakeprotectionforFlexiMultiradioBTSconfigurationshavingmorethansix
modules(WCDMA,EDGE,WiMaxorLTE).

TheoptionalIndoorCabinet(FCIA)canincludethefollowingoptionalitems:

Indoorlong-termBatteryBackupsolution(MIBBU),62Ahor92Ahbatterywiththe
indoorinstallationcablekit(FMBB).Formoreinformation,seesectionLTE78:Flexi
AC/DCwithBatteryPowerModule.
FireDetector(FCDA)
EACIP55connectionbox(FSEB),neededtoconnectFCDA,FSECandMIBBU
alarms.
OVPIP55box(FSEC)
cabinetdimensions:1800x600x600mm(HxWxD).

The Flexi Multiradio BTS Outdoor Cabinet (FCOA)


TheFlexiMultiradioBTSSystemandRFModulesareIP65weather-protected.TheFlexi
MultiradioBTSmultipurposeOutdoorCabinet(FCOA)isanoptionforsiteswherefurther
protectionisneeded.Themainapplicationsare:

moduleandcableprotectionagainstvandalismandwind-drivenrain
thefuture-proofmultipurposecabinetcanhousetwoorthreeseparateBTSs,for
exampleWCDMAand/orEDGE,and/orWiMax,and/orLTE
severalhoursofsharedbatterybackupforasinglecabinetwithoneortwoBTSs
(WCDMA,EDGE,WiMaxorLTE)
space(4U)fortheoperator'sownindoorIP20classunits
anoptionalairfilterforharshenvironmentalconditions,forexamplesaltycoastal
areas
earthquakeprotectionforFlexiMultiradioBTSconfigurationshavingmorethansix
modules(WCDMA,EDGE,WiMaxorLTE).

Theoptionaloutdoorcabinet(FCOA)canincludethefollowingoptionalitems:

OutdoorSiteSupportModule(FCSAwithoptionalindoorMIBBU):62Ahor92Ah
longtermbatterywithoutdoorinstallationcablekit(FMBA).Formoreinformation,
seesectionLTE78:FlexiAC/DCwithBatteryPowerModule.
Airfilter(FCFA)
Firedetector(FCDA)

126 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

EACIP55connectionbox(FSEB),neededtoconnecttheFCDA,FCFA,FSECand
FCSAalarms.FCOAincludesalockandadooralarmswitchthatisconnectedto
FSEB.
OVPIP55connectionbox(FSEC)
cabinetdimensions:1550x770x770mm(HxWxD).Withoptionalairfilter
(FCFA):1550x770x930mm(HxWxD).Withairfilter(FCFA)andwindbreaker:
1550x770x1020mm(HxWxD).

1.4.6.2 LTE78: Flexi AC/DC with Battery Power Module (FPMA)


1.4.6.2.1 Introduction

TheFlexiMultiradioBTSPowerModule(FPMA)offersanIP55-protectedFlexiMultiradio
BTSAC/DCrectifierwithanoptionalBatteryModulewithmultipleinstallationoptions:
outdoorsorindoors,onawall,pole,thefloororacabinet.

1.4.6.2.2 Benefits

TheFlexiMultiradioBTSPowerModule(FPMA)isaslim3Uhighflexiblegeneral
purposeFlexiMultiradioBTSPowerModulethatcanbeinstalledinvirtuallyanycabinet.
TheAC/DCandBatteryModulecanbeinstalledinthesameinstallationconditionsas
theotherFlexiMultiradioBTSModules.Noseparateequipmentroomisneededfor
protectingtheinstalledsiteagainstmainsfailures.

1.4.6.2.3 Functional description

TheFlexiMultiradioBTSAC/DCandbatterymoduleconsistsofthefollowingmain
elements:theFlexiMultiradioBTSPowerModule(FPMA),whichisthecasingfortheAC
inputandDCoutputcableconnectorboxandasupportframefortheactualpowersub-
modules,theFlexiMultiradioBTSPowerBatterySub-Module(FPAA)andtheoptional
battery(FPBA).ThemainfunctionoftheFPAAistoprovidetheBTSmoduleswith48V
DCpowerfromanACcurrent.TheFPBA,amaintenancefreeLithium-Ionbattery,brings
significantOPEXsavingsoveritsten-yearbatterylifetime.ThefunctionoftheFPDA,a
standalone2kWDC/DCmodulewith2Uheight,istogenerateBTSinternal48VDC
powerfromtheexternal24VDC.TheFPMAcanhouseuptothreeAC/DCrectifiers,
eachofwhichhasanoutputpowerof1kW48VDCpower.TheFPMAcanhouseupto
threebatterysub-modules,whichcanprovideuptoonehourofbatteryback-uptime
whentheACpowermainsisdownonatypical1+1+1FlexiMultiradioBTSsite.Two
HardwareAlarmscanbeconnectedfromtheFPMAdirectlytotheFlexiMultiradioBTS
SystemModuleusinganEthernetRJ45cable.

1.4.6.3 LTE82: High-capacity Flexi System Module (FSME)


1.4.6.3.1 Introduction

TheFlexiMultiradioBTSSystemModule(FSME)providesallthecommonand
basebandprocessingfunctionsattheBTSsite.Thehigh-capacityFlexiMultiradioBTS
SystemModule(FSME)cansupportatypicalthree-sectorFlexiMultiradioLTEBTSwith
upto20MHzcellbandwidth.

Issue:02B DN0978045 127


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.4.6.3.2 Benefits

Thehigh-capacityFlexiMultiradioBTSSystemModule(FSME)isthemostcost-
optimizedandfuture-proofmultimodeSystemModuleforhigh-capacity
WCDMA/HSPA/LTEsitesofferingmaximumcapacitywithminimumrequiredsitespace.
FSMEissoftware-configurable.AllthecommonfunctionsataBTSsite-baseband
processing,transport,powerdistributionandfans-areprovidedinacompactIP65
weather-proof3Umodule.Themodulecanoperateinambienttemperaturesranging
from-35Cto+55C.Nocabinetisneeded,asthemodulecanbeinstalledtoawallor
poleoranexistingthird-partyBTSorsitesupportcabinet.

1.4.6.3.3 Functional description

ThearchitectureofFSMEallowsforproductcapacityvariantsofone,twoorthree
basebandprocessingunitsperoneSystemModule.FSMEisabletosupportthreeLTE
cellswiththemaximumof20MHzcarrierbandwidthwith2TXMIMO,orsixLTEcells
withthemaximumof10MHzcarrierbandwidthwith2TXMIMO.
TheFSMEModuleprovidesthefollowingfunctionality:

BTSandsite-levelO&Mprocessing
LTEeNBtelecomandRRMfunctionality
transportinterfacewithtransportsub-module
externalalarmsandcontrols(EACs)
timingandsynchronization
site48VDCinputpowerinterfaceand48VDCdistributiontoothermoduleswith
fuses
EthernetSwitchwith1Gand100MEthernetinterfaces
5opticalinterfaces,usedtoconnectRadioModulesandthesecondSystemModule
intheextensionmode
RP3summing/distributionfunction
2redundantfans
IP65mechanicswith-35to+55Cambienttemperature.

1.4.7 LTE80: GPS synchronization


1.4.7.1 Introduction

ExternalGPSsynchronizationcanbeusedforfrequencysynchronizationonsites
utilizingEthernettransport.

1.4.7.2 Benefits

Areliablefrequencyreferencecanbeprovidedforsitesusingasynchronoustransport
mediaunabletoprovideafrequencyreferencefortheFlexiMultiradioBTS.

1.4.7.3 Functional description

TheGPSantennawithintegratedreceiver(FYGA)needstobeinstalledoutsidefor
satellitevisibilityandcanbedirectlyconnectedtothesynchronizationinputoftheFlexi
MultiradioBTSSystemModule.DCpowerfortheGPSreceiverissuppliedthroughthe
combinedpowerandcontrolcableconnectedtotheMDR-26SyncinterfaceoftheFlexi

128 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

MultiradioBTSSystemModule.TheFlexiMultiradioBTSSystemModuleprovidesa
powerfeedingof12Vwhichallowsforcablelengthsofmorethan200m.ForFDDLTE,
GPSsynhronizationataBTSsiteisanoptionalfeatureifTimingOverPacket(ToP)or
SynchronousEthernetarenotusedinthetransportnetwork.

1.4.8 Power support features


1.4.8.1 LTE900: Flexi Multiradio BTS 40 W power support
1.4.8.1.1 Introduction

FlexiMultiradioBTS40WRFPowerlicenceactivates40WpowermodetooneTX
PowerAmplifierofFlexiMultiradioBTSRFModuleinLTEmode.

1.4.8.1.2 Benefits

TheoneandthesameFlexiRFModulehardwarecansupport8,20,40and60WRF
powermodeswithSWlicences.ThereforethereisnoneedforseparateRFModule
Powervariants.NositevisitsareneededbecauseRFcapacityincreaseispossible'Pay
asyougrow'-theno-site-visitprinciple.
60WinLTEisneededespeciallyathigherRFbandwidths,e.g.at15MHzor20MHz
bandwidthinordertokeepcoveragewithhighcapacity.
OneRFModulehardwaremodelbringssavingsinsparepartstock,logistics,and
maintenance.

1.4.8.1.3 Functional description

ThisfeatureisneededforFlexiMultiradio3-sectorRFModuleforallRFbandvariants
when60WRFmodeperTXpathisrequired.
InSIMO(Single1TX)BTSconfigurationone60WPowerlicenceisneededpersector.
In2TXMIMO(twoactiveTXpaths)BTSconfigurationtwo60WPowerlicencesare
neededpersector.
Requiredhardware:

FlexiMultiradio3-sectorRFModuleforallRFbandvariants.
Tentatively,60WpowermodenotneededforanyRemoteRadioHead(RRH)2TX
(30+30W)MIMOproduct.

1.4.8.2 LTE901: Flexi Multiradio BTS 8 W power support


1.4.8.2.1 Introduction

FlexiMultiradioBTS8WRFPowerlicenceenables8WRFpowermodeoperationwith
FlexiMultiradioBTSRFModuleinLTEmode.

1.4.8.2.2 Benefits

TheoneandthesameFlexiMultiradioBTShardwarevariantcanbeusedatmacroand
micro/picosites.Logisticsandsparepartcostsarelower.Hotspotindoorandoutdoor
capacityandcoveragecanbebuiltcost-efficientlyusingsmallFlexiModuleswithout
cabinetsornewcostlymacroBTSsites.

Issue:02B DN0978045 129


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.4.8.2.3 Functional description

ThisfeaturemakesitpossibletolimittheFlexiBTSRFpowerto8Wwiththe60WRF
Module,andlimitthemaximumallowedRFexposurefromtheBTSespeciallyatmicro
sites.TheRFexposurelimitsdependonnationalorlocallegislationineachcoutry.
Theoperatorcanselectteh8WmoduleinthecommissioningphaseofFlexiBTS.The
FlexiBTSRFModuleinternallylimitstheoutputpowerto8Wwithacontrolcycleofless
than1ms.
Configurations:

1,1+1,1+1+1@8W1TXand2RXwith3-sectorRFModule.
1sector8+8W2TX/2RXMIMOwith3-sectorRFModule.

1.4.8.3 LTE903: Flexi Multiradio BTS 60 W power support


1.4.8.3.1 Introduction

FlexiMultiradioBTS60WRFPowerlicenceactivatesthe60WRFpowermodetoone
TXpathofFlexiBTSRFModuleinLTEmode.60WTXpowerisattheantenna
connectorofFlexiBTS,thatis,RFModuleTX/RXport.Supportformaximum60WTX
powermodeoneach3GPPRFbanddependsonRFModuleversion.

1.4.8.3.2 Benefits

TheoneandthesameFlexiRFModuleHWcansupport8,20,40and60WRFpower
modeswithSWlicences.Therefore,thereisnoneedforseparateRFModulePower
variants.NositevisitsareneededbecauseRFcapacityincreaseispossible'Payasyou
grow'-theno-site-visitsprinciple.
60WinLTEisneededespeciallyathigherRFbandwidths,e.g.at15MHzor20MHz
bandwidtinordertokeepcoveragewithhighcapacity.
OneRFModulehardwaremodelbringssavingsinsparepartstock,logistics,and
maintenance.

1.4.8.3.3 Functional description

ThisfeatureisneededforFlexiMultiradio3-sectorRFModuleforallRFbandvariants
when60WRFmodeperTXpathisrequired.
InSIMO(Single1TX)BTSconfigurationone60WPowerlicenceisneededpersector.
In2TXMIMO(twoactiveTXpaths)BTSconfiguration,two60WPowerlicencesare
neededpersector.
Requiredhardware:

FlexiMultiradio3-sectorRFModuleforallRFbandvariants.
Tentatively,60WpowermodenotneededforanyRemoteRadioHead(RRH)2TX
(30+30W)MIMOproduct.

130 DN0978045 Issue:02B


FeatureDescriptionsRL10 FeatureDescriptionsRL10

1.4.8.4 LTE904: Flexi LTE BTS Branch Activation


1.4.8.4.1 Introduction

TheDownlinkTXBranchActivation(BA)licenceisneededtoactivateoneTXofthe
Flexi3-sectorRFModule.OnebranchactivationlicenceactivatesoneTXPower
Amplifierinthedefault20WRFpowermode.Thedefault20WTXpowerisatthe
antennaconnectoroftheFlexiMultiradioBTS,attheTX/RXportoftheRFModule.
ThreebranchactivationlicensesareneededtoactivateallthreeTXpathsofthe3-sector
RFModule.

1.4.8.4.2 Benefits

AsingleFlexiRFModulecanbeusedflexiblyforone,twoorthreesectorconfigurations
bysoftwarelicenseactivation.ThesameRFModulecanalsobeconfiguredandusedas
onesectorremote2TXMIMORFModule(60+60W).Becausethereisnoneedfor
separateone,twoandthreesectorRFModules,savingsareachievedinlogistics,spare
partsandmaintenance.

1.4.8.4.3 Functional description

InordertoactivateanyLTEcellsinaFlexi3-sectorRFModule,atleastoneBranch
Activationlicenceisneededforeachsector.InaSIMO(Single1TX)BTSconfiguration,
oneBranchActivationlicenceisneededperactivesector.Ina2TXMIMO(twoactive
TXs)BTSconfiguration,twoBranchActivationlicencesareneededpersector.This
licenseisneededforallfrequencyvariantsoftheFlexiMultiradio3-sectorRFModule.
TheRemoteRFHead(RRH)2TXMIMOproductrequiresoneBranchActivationlicence
foreachactiveTXbranch,i.e.twoBranchActivationlicencesareneededforthe20W+
20W2TXMIMOoperationmodepersectorandpereachRRH.

Issue:02B DN0978045 131