You are on page 1of 273

RU50 Feature Descriptions

and Instructions
DN09146788
Issue 01A DRAFT
Approval Date 2014-04-08

RU50FeatureDescriptionsandInstructions

Theinformationinthisdocumentissubjecttochangewithoutnoticeanddescribesonlytheproduct
defined in the introduction of this documentation. This documentation is intended for the use of
NokiaSolutionsandNetworkscustomersonlyforthepurposesoftheagreementunderwhichthe
documentissubmitted,andnopartofitmaybeused,reproduced,modifiedortransmittedinany
formormeanswithoutthepriorwrittenpermissionofNokiaSolutionsandNetworks.Thedocumentationhasbeenpreparedtobeusedbyprofessionalandproperlytrainedpersonnel,andthecustomerassumesfullresponsibilitywhenusingit.NokiaSolutionsandNetworkswelcomescustomer
commentsaspartoftheprocessofcontinuousdevelopmentandimprovementofthedocumentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performanceofthementionedhardwareorsoftwareproductsaregiven"asis"andallliabilityarisinginconnectionwithsuchhardwareorsoftwareproductsshallbedefinedconclusivelyandfinally
in a separate agreement between Nokia Solutions and Networks and the customer. However,
NokiaSolutionsandNetworkshasmadeallreasonableeffortstoensurethattheinstructionscontained 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 DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,INCIDENTALORCONSEQUENTIALORANYLOSSES,SUCHASBUTNOTLIMITEDTO
LOSSOFPROFIT,REVENUE,BUSINESSINTERRUPTION,BUSINESSOPPORTUNITYORDATA,THATMAYARISEFROMTHEUSEOFTHISDOCUMENTORTHEINFORMATIONINIT.
Thisdocumentationandtheproductitdescribesareconsideredprotectedbycopyrightsandother
intellectualpropertyrightsaccordingtotheapplicablelaws.
NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia
Corporation.Otherproductnamesmentionedinthisdocumentmaybetrademarksoftheirrespectiveowners,andtheyarementionedforidentificationpurposesonly.
CopyrightNokiaSolutionsandNetworks2014.Allrightsreserved

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.
IfyoushouldhavequestionsregardingourEnvironmentalPolicyoranyoftheenvironmentalservicesweoffer,pleasecontactusatNokiaSolutionsandNetworksforanyadditionalinformation.

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table of Contents
Thisdocumenthas273pages

Summaryofchanges................................................................... 19

Issue:01ADRAFT

1
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9

IntroductiontoRU50features...................................................... 23
RU50radioresourcemanagementfeatures................................ 23
RU50telecomfeatures................................................................ 24
RU50transmissionandtransportfeatures...................................25
RU50operabilityfeatures.............................................................25
RU50performancemonitoringfeatures....................................... 26
RU50RNCsolutionfeatures........................................................27
RU50BTSsolutionfeatures.........................................................27
Licensing...................................................................................... 28
Referencedocumentation............................................................ 29

2
2.1
2.1.1
2.1.1.1
2.1.1.2
2.1.1.3
2.1.1.4
2.1.1.5
2.1.1.6
2.2
2.2.1
2.2.1.1
2.2.1.2
2.2.1.3
2.2.1.4
2.2.1.5
2.2.1.6
2.3
2.3.1
2.3.1.1
2.3.1.2
2.3.1.3
2.3.1.4
2.3.1.5
2.3.1.6
2.3.2
2.3.3
2.3.4
2.4

Radioresourcemanagementfeatures.........................................31
RAN2578:AMRCodecSetfor2G-3GTrFO................................31
DescriptionofRAN2578:AMRCodecSetfor2G-3GTrFO.........31
Benefits........................................................................................ 31
Requirements...............................................................................31
Functionaldescription.................................................................. 32
Systemimpact..............................................................................32
RAN2578:AMRCodecSetfor2G-3GTrFOmanagementdata..32
Salesinformation......................................................................... 34
RAN3018:BTSLoadBasedAACR............................................. 34
DescriptionofRAN3018:BTSLoadBasedAACR...................... 34
Benefits........................................................................................ 34
Requirements...............................................................................35
Functionaldescription.................................................................. 35
Systemimpact..............................................................................36
RAN3018:BTSLoadBasedAACRmanagementdata............... 36
Salesinformation......................................................................... 38
RAN2963:DataSessionProfiling................................................ 38
DescriptionofRAN2963:DataSessionProfiling......................... 38
Benefits........................................................................................ 38
Requirements...............................................................................39
Functionaldescription.................................................................. 39
Systemimpact..............................................................................40
RAN2963:DataSessionProfilingmanagementdata.................. 40
Salesinformation......................................................................... 42
ActivatingRAN2963:DataSessionProfiling................................42
VerifyingRAN2963:DataSessionProfiling................................. 44
DeactivatingRAN2963:DataSessionProfiling........................... 45
RAN1905:DC-HSUPA................................................................. 45

DN09146788

RU50FeatureDescriptionsandInstructions

2.4.1
2.4.1.1
2.4.1.2
2.4.1.3
2.4.1.4
2.4.1.5
2.4.1.6
2.5
2.5.1
2.5.1.1
2.5.1.2
2.5.1.3
2.5.1.4
2.5.1.5
2.5.1.6
2.5.2
2.5.3
2.5.4
2.6
2.6.1
2.6.1.1
2.6.1.2
2.6.1.3
2.6.1.4
2.6.1.5
2.6.1.6
2.7
2.7.1
2.7.1.1
2.7.1.2
2.7.1.3
2.7.1.4
2.7.1.5
2.7.1.6
2.7.2
2.7.3
2.7.4
2.8
2.8.1
2.8.1.1
2.8.1.2
2.8.1.3
2.8.1.4

DescriptionofRAN1905:DC-HSUPA.......................................... 45
Benefits........................................................................................ 45
Requirements...............................................................................46
Functionaldescription.................................................................. 46
Systemimpact..............................................................................48
RAN1905:DC-HSUPAmanagementdata................................... 50
Salesinformation......................................................................... 52
RAN2179:DualBandHSDPA42Mbps....................................... 52
DescriptionofRAN2179:DualBandHSDPA42Mbps................ 52
Benefits........................................................................................ 52
Requirements...............................................................................53
Functionaldescription.................................................................. 53
Systemimpact..............................................................................55
RAN2179:Dual-BandHSDPA42Mbpsmanagementdata..........55
Salesinformation......................................................................... 57
ActivatingRAN2179:DualBandHSDPA42Mbps...................... 58
VerifyingRAN2179:DualBandHSDPA42Mbps........................ 59
DeactivatingRAN2179:DualBandHSDPA42Mbps.................. 60
RAN2250:EnhancedHSUPAIC..................................................61
DescriptionofRAN2250:EnhancedHSUPAIC...........................61
Benefits........................................................................................ 62
Requirements...............................................................................62
Functionaldescription.................................................................. 62
Systemimpact..............................................................................64
RAN2250:EnhancedHSUPAICmanagementdata....................64
Salesinformation......................................................................... 65
RAN2482:EnhancedVirtualAntennaMapping........................... 65
DescriptionofRAN2482:EnhancedVirtualAntennaMapping... 65
Benefits........................................................................................ 65
Requirements...............................................................................66
Functionaldescription.................................................................. 66
Systemimpact..............................................................................67
RAN2482:EnhancedVirtualAntennaMappingmanagementdata.
67
Salesinformation......................................................................... 68
ActivatingRAN2482:EnhancedVirtualAntennaMapping.......... 68
VerifyingRAN2482:EnhancedVirtualAntennaMapping............ 71
DeactivatingRAN2482:EnhancedVirtualAntennaMapping...... 71
RAN1668:HSUPACompressedModeforLTEandInterfrequencyHandover.....................................................................72
DescriptionofRAN1668:HSUPACompressedModeforLTEand
Inter-frequencyHandover............................................................ 72
Benefits........................................................................................ 72
Requirements...............................................................................72
Functionaldescription.................................................................. 73
Systemimpact..............................................................................74

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

2.8.1.5
2.8.1.6
2.8.2
2.8.3
2.8.4
2.9
2.9.1
2.9.1.1
2.9.1.2
2.9.1.3
2.9.1.4
2.9.1.5
2.9.1.6
2.9.2
2.9.3
2.9.4
2.10
2.10.1
2.10.1.1
2.10.1.2
2.10.1.3
2.10.1.4
2.10.1.5
2.10.1.6
2.10.2
2.10.2.1
2.10.2.2
2.10.3
2.10.3.1
2.10.3.2
2.10.4
2.10.4.1
2.10.4.2
2.11
2.11.1
2.11.1.1

Issue:01ADRAFT

RAN1668:HSUPACompressedModeforLTEandInterfrequencyHandovermanagementdata.......................................75
Salesinformation......................................................................... 78
ActivatingRAN1668:HSUPACompressedModeforLTEand
Inter-frequencyHandover............................................................ 78
VerifyingRAN1668:HSUPACompressedModeforLTEandInterfrequencyHandover.....................................................................81
DeactivatingRAN1668HSUPACompressedModeforLTEand
Inter-frequencyHandover............................................................ 83
RAN2980:MeasurementBasedLTELayering............................ 84
DescriptionofRAN2980:MeasurementBasedLTELayering..... 84
Benefits........................................................................................ 84
Requirements...............................................................................84
Functionaldescription.................................................................. 85
Systemimpact..............................................................................86
RAN2980:MeasurementBasedLTELayeringmanagementdata..
86
Salesinformation......................................................................... 89
ActivatingRAN2980:MeasurementBasedLTELayering............89
VerifyingRAN2980:MeasurementBasedLTELayering............ 92
DeactivatingRAN2980:MeasurementBasedLTELayering....... 93
RAN147:RRCConnectionSetupRedirection............................. 93
DescriptionofRAN147:RRCConnectionSetupRedirection...... 93
Benefits........................................................................................ 93
Requirements...............................................................................93
Functionaldescription.................................................................. 94
Systemimpact..............................................................................96
RAN147:RRCConnectionSetupRedirectionmanagementdata...
97
Salesinformation......................................................................... 99
ActivatingRAN147:RRCConnectionSetupRedirection............ 99
ActivatingRAN147:RRCConnectionSetupRedirectiondueto
admissioncontrolreasons........................................................... 99
ActivatingRAN147:RRCConnectionSetupRedirectiondueto
signalingunitoverload............................................................... 100
VerifyingRAN147:RRCConnectionSetupRedirection............ 102
VerifyingRAN147:RRCConnectionSetupRedirectiondueto
admissioncontrolreasons......................................................... 102
VerifyingRAN147:RRCConnectionSetupRedirectiondueto
signalingunitoverloadreasons..................................................102
DeactivatingRAN147:RRCConnectionSetupRedirection...... 103
DeactivatingRAN147:RRCConnectionSetupRedirectiondueto
admissioncontrolreasons......................................................... 103
DeactivatingRAN147:RRCConnectionSetupRedirectiondueto
signalingunitoverloadreasons..................................................104
RAN3069:RSRQ-basedLTEReselection................................. 105
DescriptionofRAN3069:RSRQ-basedLTEReselection.......... 105
Benefits...................................................................................... 105

DN09146788

RU50FeatureDescriptionsandInstructions

2.11.1.2
2.11.1.3
2.11.1.4
2.11.1.5
2.11.1.6
2.11.2
2.11.3
2.11.4
2.12
2.12.1
2.12.1.1
2.12.1.2
2.12.1.3
2.12.1.4
2.12.1.5
2.12.1.6
2.12.2
2.12.3
2.12.4
2.13
2.13.1
2.13.1.1
2.13.1.2
2.13.1.3
2.13.1.4
2.13.1.5

2.14.1.6
2.14.2
2.14.3
2.14.4

Requirements.............................................................................106
Functionaldescription................................................................ 106
Systemimpact............................................................................106
RAN3069:RSRQ-basedLTEReselectionmanagementdata... 107
Salesinformation....................................................................... 108
ActivatingRAN3069:RSRQ-basedLTEReselection.................108
VerifyingRAN3069:RSRQ-basedLTEReselection.................. 109
DeactivatingRAN3069:RSRQ-basedLTEReselection.............110
RAN2264:SmartLTEHandover.................................................111
DescriptionofRAN2264:SmartLTEHandover..........................111
Benefits.......................................................................................111
Requirements............................................................................. 111
Functionaldescription.................................................................112
Systemimpact............................................................................ 113
RAN2264:SmartLTEHandovermanagementdata.................. 113
Salesinformation........................................................................118
ActivatingRAN2264:SmartLTEHandover................................118
VerifyingRAN2264:SmartLTEHandover................................. 122
DeactivatingRAN2264:SmartLTEHandover........................... 123
RAN2546:VHSReceiverforHighspeedTrain..........................124
DescriptionofRAN2546:VHSReceiverforHighSpeedTrain.. 124
Benefits...................................................................................... 124
Requirements.............................................................................125
Functionaldescription................................................................ 125
Systemimpact............................................................................125
RAN2546:VHSReceiverforHighSpeedTrainmanagementdata.
126
Salesinformation....................................................................... 126
RAN2881:WCDMAandGSMLayerPriorities.......................... 126
DescriptionofRAN2881:WCDMAandGSMLayerPriorities... 126
Benefits...................................................................................... 126
Requirements.............................................................................127
Functionaldescription................................................................ 127
Systemimpact............................................................................128
RAN2881:WCDMAandGSMLayerPrioritiesmanagementdata..
128
Salesinformation....................................................................... 131
ActivatingRAN2881:WCDMAandGSMLayerPriorities..........131
VerifyingRAN2881:WCDMAandGSMLayerPriorities............133
DeactivatingRAN2881:WCDMAandGSMLayerPriorities......133

Telecomfeatures........................................................................134

4
4.1
4.1.1

Transmissionandtransportfeatures..........................................139
RAN2913:LocalandRemoteIPTrafficCapturing.....................139
DescriptionofRAN2913:LocalandRemoteIPTrafficCapturing....
139

2.13.1.6
2.14
2.14.1
2.14.1.1
2.14.1.2
2.14.1.3
2.14.1.4
2.14.1.5

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

4.1.1.1
4.1.1.2
4.1.1.3
4.1.1.4
4.1.1.5

4.2.4.1
4.2.4.2
4.2.4.3

Benefits...................................................................................... 139
Requirements.............................................................................139
Functionaldescription................................................................ 140
Systemimpact............................................................................142
RAN2913:LocalandRemoteIPTrafficCapturingmanagement
data............................................................................................ 143
Salesinformation....................................................................... 144
RAN2243:PerformanceMonitoringBasedonETHServiceOAM...
144
DescriptionofRAN2243:PerformanceMonitoringBasedonETH
ServiceOAM.............................................................................. 144
Benefits...................................................................................... 144
Requirements.............................................................................144
Functionaldescription................................................................ 145
Systemimpact............................................................................146
RAN2243:PerformanceMonitoringBasedonETHServiceOAM
managementdata...................................................................... 147
Salesinformation....................................................................... 150
ActivatingRAN2243:PerformanceMonitoringBasedonETH
ServiceOAM.............................................................................. 150
ActivatingEthernetServiceOAMPM........................................ 151
ActivatingFrameLossMeasurementsession........................... 152
ActivatingFrameDelayMeasurementsession..........................154
VerifyingRAN2243:PerformanceMonitoringBasedonETH
ServiceOAM.............................................................................. 156
DeactivatingRAN2243:PerformanceMonitoringBasedonETH
ServiceOAM.............................................................................. 160
DeactivatingEthernetServiceOAMPM.................................... 161
DeactivatingFrameLossMeasurementsession....................... 162
DeactivatingFrameDelayMeasurementsession......................163

5
5.1
5.1.1

Operabilityfeatures.................................................................... 166
RAN2199:BTSEventTriggeredSymptomDataCollection.......166
DescriptionofRAN2199:BTSEventTriggeredSymptomData
Collection................................................................................... 166
Benefits...................................................................................... 166
Requirements.............................................................................166
Functionaldescription................................................................ 167
Systemimpact............................................................................169
RAN2199:BTSEventTriggeredSymptomDataCollection
managementdata...................................................................... 169
Salesinformation....................................................................... 171
ActivatingRAN2199:BTSEventTriggeredSymptomData
Collection................................................................................... 171
DeactivatingRAN2199:BTSEventTriggeredSymptomData
Collection................................................................................... 172
RAN2919:OMSCertificateUpdateandRevocationSupport.... 173

4.1.1.6
4.2
4.2.1
4.2.1.1
4.2.1.2
4.2.1.3
4.2.1.4
4.2.1.5
4.2.1.6
4.2.2
4.2.2.1
4.2.2.2
4.2.2.3
4.2.3
4.2.4

5.1.1.1
5.1.1.2
5.1.1.3
5.1.1.4
5.1.1.5
5.1.1.6
5.1.2
5.1.3
5.2

Issue:01ADRAFT

DN09146788

RU50FeatureDescriptionsandInstructions

5.2.1
5.2.1.1
5.2.1.2
5.2.1.3
5.2.1.4
5.2.1.5
5.2.1.6
5.3
5.3.1
5.3.1.1
5.3.1.2
5.3.1.3
5.3.1.4
5.3.1.5
5.3.1.6
5.4
5.4.1
5.4.1.1
5.4.1.2
5.4.1.3
5.4.1.4
5.4.1.5
5.4.1.6
5.5
5.5.1
5.5.1.1
5.5.1.2
5.5.1.3
5.5.1.4
5.5.1.5
5.5.1.6
5.6
5.6.1
5.6.1.1
5.6.1.2
5.6.1.3
5.6.1.4
5.6.1.5
5.6.1.6
5.6.2
5.6.2.1

DescriptionofRAN2919:OMSCertificateUpdateandRevocation
Support.......................................................................................173
Benefits...................................................................................... 173
Requirements.............................................................................173
Functionaldescription................................................................ 174
Systemimpact............................................................................175
RAN2919:OMSCertificateUpdateandRevocationSupport
managementdata...................................................................... 176
Salesinformation....................................................................... 177
RAN2699:OMSSystemStatusView.........................................177
DescriptionofRAN2699:OMSSystemStatusView..................177
Benefits...................................................................................... 177
Requirements.............................................................................178
Functionaldescription................................................................ 178
Systemimpact............................................................................180
RAN2699:OMSSystemStatusViewmanagementdata.......... 181
Salesinformation....................................................................... 181
RAN3004:ParameterCategorization.........................................182
DescriptionofRAN3004:ParameterCategorization..................182
Benefits...................................................................................... 182
Requirements.............................................................................182
Functionaldescription................................................................ 182
Systemimpact............................................................................183
RAN3004:ParameterCategorizationmanagementdata...........184
Salesinformation....................................................................... 184
RAN2507:RNWPlanProgressIndicatorandAbort.................. 184
DescriptionofRAN2507:RNWPlanProgressIndicatorandAbort.
184
Benefits...................................................................................... 184
Requirements.............................................................................185
Functionaldescription................................................................ 185
Systemimpact............................................................................189
RAN2507:RNWPlanProgressIndicatorandAbortmanagement
data............................................................................................ 190
Salesinformation....................................................................... 191
RAN2554:TransportConfigurationFall-back............................ 191
DescriptionofRAN2554:TransportConfigurationFall-back..... 191
Benefits...................................................................................... 191
Requirements.............................................................................191
Functionaldescription................................................................ 192
Systemimpact............................................................................193
RAN2554:TransportConfigurationFallbackmanagementdata......
194
Salesinformation....................................................................... 194
ActivatingRAN2554:TransportConfigurationFallback............. 194
ActivatingRAN2554:TransportConfigurationFallbackusingBTS
SiteManager..............................................................................195

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

5.6.2.2

5.7.1.6

ActivatingRAN2554:TransportConfigurationFallbackfrom
NetActCMEditor....................................................................... 195
VerifyingRAN2554:TransportConfigurationFallback............... 195
DeactivatingRAN2554:TransportConfigurationFallback......... 195
DeactivatingRAN2554:TransportConfigurationFallbackusing
BTSSiteManager......................................................................196
DeactivatingRAN2554:TransportConfigurationFallbackfrom
NetActCMEditor....................................................................... 196
RAN2229:TroubleshootingDataManagementbyNetAct.........196
DescriptionofRAN2229:TroubleshootingDataManagementby
NetAct........................................................................................ 196
Benefits...................................................................................... 197
Requirements.............................................................................197
Functionaldescription................................................................ 197
Systemimpact............................................................................197
RAN2229:TroubleshootingDataManagementbyNetAct
managementdata...................................................................... 198
Salesinformation....................................................................... 199

6
6.1
6.1.1
6.1.1.1
6.1.1.2
6.1.1.3
6.1.1.4
6.1.1.5

Performancemonitoringfeatures...............................................200
RAN2496:3GPPMinimizationofDriveTests............................ 200
DescriptionofRAN2496:3GPPMinimizationofDriveTests..... 200
Benefits...................................................................................... 200
Requirements.............................................................................200
Functionaldescription................................................................ 201
Systemimpact............................................................................202
RAN2496:3GPPMinimizationofDriveTestsmanagementdata....
202
Salesinformation....................................................................... 203
RAN2443:BTSResourceUtilizationMonitoring........................203
DescriptionofRAN2443:BTSResourceUtilizationMonitoring.203
Benefits...................................................................................... 203
Requirements.............................................................................204
Functionaldescription................................................................ 204
Systemimpact............................................................................205
RAN2443:BTSResourceUtilizationMonitoringmanagementdata
................................................................................................... 206
Salesinformation....................................................................... 212
RAN2555:ConfigurableRangesforUserThroughputCounters.....
212
DescriptionofRAN2555:ConfigurableRangesforUser
ThroughputCounters................................................................. 212
Benefits...................................................................................... 212
Requirements.............................................................................212
Functionaldescription................................................................ 213
Systemimpact............................................................................214
RAN2555:ConfigurableRangesforUserThroughputCounters
managementdata...................................................................... 214

5.6.3
5.6.4
5.6.4.1
5.6.4.2
5.7
5.7.1
5.7.1.1
5.7.1.2
5.7.1.3
5.7.1.4
5.7.1.5

6.1.1.6
6.2
6.2.1
6.2.1.1
6.2.1.2
6.2.1.3
6.2.1.4
6.2.1.5
6.2.1.6
6.3
6.3.1
6.3.1.1
6.3.1.2
6.3.1.3
6.3.1.4
6.3.1.5

Issue:01ADRAFT

DN09146788

RU50FeatureDescriptionsandInstructions

6.3.1.6
6.4
6.4.1
6.4.1.1
6.4.1.2
6.4.1.3
6.4.1.4
6.4.1.5
6.4.1.6
6.5

6.5.1.6

Salesinformation....................................................................... 217
RAN2930:IMSI-basedCallMonitoring...................................... 217
DescriptionofRAN2930:IMSI-basedCallMonitoring............... 217
Benefits...................................................................................... 218
Requirements.............................................................................218
Functionaldescription................................................................ 218
Systemimpact............................................................................220
RAN2930:IMSI-basedCallMonitoringmanagementdata........ 220
Salesinformation....................................................................... 221
RAN2870:TrafficaIPReportsatmcRNCforRTTandPacketLoss
Ratio...........................................................................................221
DescriptionofRAN2870:TrafficaIPReportsatmcRNCforRTT
andPacketLossRatio............................................................... 221
Benefits...................................................................................... 221
Requirements.............................................................................221
Functionaldescription................................................................ 222
Systemimpact............................................................................223
RAN2870:TrafficaIPReportsatmcRNCforRTTandPacketLoss
Ratiomanagementdata.............................................................224
Salesinformation....................................................................... 225

7
7.1
7.1.1

RNCsolutionfeatures................................................................ 226
RAN2251:AutomaticmcRNCResourceOptimization...............226
DescriptionofRAN2251:AutomaticmcRNCResource
Optimization............................................................................... 226
RAN2251benefits...................................................................... 226
RAN2251requirements..............................................................226
RAN2251functionaldescription.................................................227
RAN2251systemimpact............................................................228
RAN2251:AutomaticmcRNCResourceOptimization
managementdata...................................................................... 228
RAN2251salesinformation....................................................... 229
RAN2928:DSPPoolInformationinMeasurements.................. 229
DescriptionofRAN2928:DSPPoolInformationinMeasurements.
229
RAN2928benefits...................................................................... 230
RAN2928requirements..............................................................230
RAN2928functionaldescription.................................................230
RAN2928systemimpact............................................................232
RAN2928:DSPPoolInformationinMeasurementsmanagement
data............................................................................................ 232
RAN2928salesinformation....................................................... 233
Testing[FeatureID]:[FeatureName].........................................233
RAN2959:mcRNCStep7Support............................................ 233
DescriptionofRAN2959:mcRNCStep7Support..................... 233
RAN2959benefits...................................................................... 233
RAN2959requirements..............................................................234

6.5.1
6.5.1.1
6.5.1.2
6.5.1.3
6.5.1.4
6.5.1.5

7.1.1.1
7.1.1.2
7.1.1.3
7.1.1.4
7.1.1.5
7.1.1.6
7.2
7.2.1
7.2.1.1
7.2.1.2
7.2.1.3
7.2.1.4
7.2.1.5
7.2.1.6
7.2.2
7.3
7.3.1
7.3.1.1
7.3.1.2

10

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

7.3.1.3
7.3.1.4
7.3.1.5
7.3.1.6
7.4
7.4.1
7.4.1.1
7.4.1.2
7.4.1.3
7.4.1.4
7.4.1.5
7.4.1.6
7.5
7.5.1

7.5.1.6
7.6
7.6.1
7.6.1.1
7.6.1.2
7.6.1.3
7.6.1.4
7.6.1.5
7.6.1.6

RAN2959functionaldescription.................................................234
RAN2959systemimpact............................................................235
RAN2959:mcRNCStep7Supportmanagementdata.............. 236
RAN2959salesinformation....................................................... 236
RAN2512:RNCResiliencyforRNC2600.................................. 236
DescriptionofRAN2512:RNCResiliencyforRNC2600........... 236
Benefits...................................................................................... 236
Requirements.............................................................................237
Functionaldescription................................................................ 237
Systemimpact............................................................................239
RAN2512:RNCResiliencyforRNC2600managementdata.... 239
Salesinformation....................................................................... 241
RAN3047:RTTImprovementtoEnhanceUserExperience...... 242
DescriptionofRAN3047:RTTImprovementtoenhanceuser
experience..................................................................................242
Benefits...................................................................................... 242
Requirements.............................................................................242
Functionaldescription................................................................ 243
Systemimpact............................................................................243
RAN3047:RTTImprovementtoenhanceuserexperience
managementdata...................................................................... 243
Salesinformation....................................................................... 244
RAN2671:UpgradingofmcBSCtomcRNC.............................. 244
DescriptionofRAN2671:UpgradingofmcBSCtomcRNC....... 244
Benefits...................................................................................... 244
Requirements.............................................................................244
Functionaldescription................................................................ 246
Systemimpact............................................................................254
RAN2671:UpgradingofmcBSCtomcRNCmanagementdata. 255
Salesinformation....................................................................... 255

8
8.1

BTSsolutionfeatures.................................................................256
RAN3010:24CellSupportwithFlexiFSMF+FSMD/ESystem
Modules......................................................................................256
DescriptionofRAN3010:24CellSupportwithFlexiFSMF+
FSMD/ESystemModules.......................................................... 256
Benefits...................................................................................... 256
Requirements.............................................................................256
Functionaldescription................................................................ 256
Systemimpact............................................................................257
Salesinformation....................................................................... 257
RAN3017:Additional6WCDMACellActivation........................ 258
DescriptionofRAN3017:Additional6WCDMACellActivation. 258
Benefits...................................................................................... 258
Requirements.............................................................................258
Functionaldescription................................................................ 259
Systemimpact............................................................................259

7.5.1.1
7.5.1.2
7.5.1.3
7.5.1.4
7.5.1.5

8.1.1
8.1.1.1
8.1.1.2
8.1.1.3
8.1.1.4
8.1.1.5
8.2
8.2.1
8.2.1.1
8.2.1.2
8.2.1.3
8.2.1.4

Issue:01ADRAFT

DN09146788

11

RU50FeatureDescriptionsandInstructions

8.2.1.5
8.2.1.6
8.2.2
8.2.3
8.2.4
8.3
8.3.1
8.3.1.1
8.3.1.2
8.3.1.3
8.3.1.4
8.3.1.5
8.3.1.6
8.4
8.4.1
8.4.1.1
8.4.1.2
8.4.1.3
8.4.1.4
8.4.1.5
8.4.1.6
8.5
8.5.1
8.5.1.1
8.5.1.2
8.5.1.3
8.5.1.4
8.5.1.5
8.5.1.6
8.6
8.6.1
8.6.1.1
8.6.1.2
8.6.1.3
8.6.1.4
8.6.1.5
8.6.1.6

12

RAN3017:Additional6WCDMACellActivationmanagementdata
................................................................................................... 259
Salesinformation....................................................................... 260
ActivatingRAN3017:Additional6WCDMACellActivation....... 260
VerifyingRAN3017:Additional6WCDMACellActivation......... 262
DeactivatingRAN3017:Additional6WCDMACellActivation... 262
RAN2826:FlexiCompactasRFModule................................... 263
DescriptionofRAN2826:FlexiCompactasRFModule............ 263
Benefits...................................................................................... 263
Requirements.............................................................................263
Functionaldescription................................................................ 263
Systemimpact............................................................................264
RAN2826:FlexiCompactasRFModulemanagementdata..... 264
Salesinformation....................................................................... 264
RAN2784:FlexiLiteBTS1900MHz..........................................265
DescriptionofRAN2784:FlexiLiteBTS1900MHz...................265
Benefits...................................................................................... 265
Requirements.............................................................................266
Functionaldescription................................................................ 266
Systemimpact............................................................................267
RAN2784:FlexiLiteBTS1900MHzmanagementdata............267
Salesinformation....................................................................... 268
RAN2732:FlexiSystemModuleExtension,FSMF+FSMD/E.. 268
DescriptionofRAN2732:FlexiSystemModuleExtension,FSMF+
FSMD/E......................................................................................268
Benefits...................................................................................... 268
Requirements.............................................................................268
Functionaldescription................................................................ 269
Systemimpact............................................................................270
RAN2732:FlexiSystemModuleExtension,FSMF+FSMD/E
managementdata...................................................................... 270
Salesinformation....................................................................... 271
RAN2393:OpticalFiber:RX/TXLevelMonitoring..................... 271
DescriptionofRAN2393:OpticalFiber:RX/TXLevelMonitoring....
271
Benefits...................................................................................... 271
Requirements.............................................................................272
Functionaldescription................................................................ 272
Systemimpact............................................................................273
RAN2393Opticalfiber:RX/TXlevelmonitoringmanagementdata.
273
Salesinformation....................................................................... 273

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

List of Figures

Issue:01ADRAFT

Figure1

DC-HSUPAphysicalchannelstructure.Physicalchannelsdistribution.
47

Figure2

TwoHSDPAcarrierslocatedintwodifferentfrequencybands.......... 54

Figure3

TheEnhancedInterferenceCancellationprocedure.......................... 63

Figure4

Theresidualsignalstreamrelationship.............................................. 64

Figure5

RRCconnectionsetupredirection......................................................95

Figure6

Selectionprocessofredirectioninformation.......................................96

Figure7

WCDMAandGSMcellreselectionbasedonlayerpriorities........... 128

Figure8

IPtrafficcapturingsetup................................................................... 140

Figure9

CapturepointsinBTS...................................................................... 141

Figure10

Capturingmechanism.......................................................................142

Figure11

PerformancemonitoringusingEthernetServiceOAMframes.........146

Figure12

SymptomdatacollectionfromtheBTS............................................ 167

Figure13

OMSSystemStatusViewapplicationstructurediagram................. 179

Figure14

CMEditor-BasicandAdvancedparametersviews........................ 183

Figure15

RAN2554:TransportConfigurationFallback.................................... 193

Figure16

MDTmeasurements......................................................................... 201

Figure17

ConfigurableRangesforUserThroughputCounters....................... 213

Figure18

OverviewofRAN2930:IMSI-basedCallMonitoring.........................219

Figure19

MeasuringRTTandPLRwithTWAMP............................................ 223

Figure20

Automaticresourceoptimizationbetweenprocessingplanes.........227

Figure21

DSPloadmeasurementbeforethefeatureactivation......................231

Figure22

DSPloadmeasurementafterthefeatureactivation........................232

Figure23

RNC2600resiliencytransportnetworklayout.................................. 238

Figure24

MulticontrollerBSCcapacitysteps................................................... 246

Figure25

MulticontrollerRNCcapacitysteps...................................................248

Figure26

UpgradingmcBSCtomcRNC.......................................................... 249

Figure27

mcBSCPSextensionmodulenecessarychanges.......................... 251

Figure28

mcBSCTRXextensionmodulenecessarychanges........................ 252

Figure29

mcBSCSparemodulenecessarychanges...................................... 253

Figure30

mcBSCmainmodulenecessarychanges........................................254

Figure31

ActivatingRAN3017:Additional6WCDMACellActivation..............261

Figure32

FlexiLiteBTS1900.......................................................................... 265

DN09146788

13

RU50FeatureDescriptionsandInstructions

List of Tables

14

Table1

RU50radioresourcemanagementfeatures...................................... 23

Table2

RU50EP1radioresourcemanagementfeatures...............................24

Table3

RU50EP1Telecomfeatures.............................................................. 24

Table4

RU50transmissionandtransportfeatures......................................... 25

Table5

RU50EP1transmissionandtransportfeatures................................. 25

Table6

RU50operabilityfeatures................................................................... 25

Table7

RU50EP1operabilityfeatures........................................................... 26

Table8

RU50EP1performancemonitoringfeatures......................................26

Table9

RU50RNCsolutionfeatures.............................................................. 27

Table10

RU50EP1RNCsolutionfeatures...................................................... 27

Table11

RU50BTSsolutionfeatures............................................................... 27

Table12

RU50EP1BTSsolutionfeatures....................................................... 28

Table13

Softwarerequirements....................................................................... 31

Table14

Newcounters......................................................................................33

Table15

Newparameters................................................................................. 33

Table16

Modifiedparameters...........................................................................33

Table17

Salesinformation................................................................................34

Table18

Softwarerequirements....................................................................... 35

Table19

Newcounters......................................................................................36

Table20

Relatedcounters................................................................................ 37

Table21

Newparameters................................................................................. 37

Table22

Modifiedparameters...........................................................................38

Table23

Salesinformation................................................................................38

Table24

Softwarerequirements....................................................................... 39

Table25

Newcounters......................................................................................41

Table26

Relatedexistingcounters................................................................... 41

Table27

Newparameters................................................................................. 41

Table28

Modifiedparameters...........................................................................42

Table29

Salesinformation................................................................................42

Table30

Softwarerequirements....................................................................... 46

Table31

NewAlarms........................................................................................ 50

Table32

Newcounters......................................................................................50

Table33

Newparameters................................................................................. 51

Table34

Modifiedparameters...........................................................................52

Table35

Salesinformation................................................................................52

Table36

Softwarerequirements....................................................................... 53

Table37

Supportedbandcombinations............................................................54

Table38

Existingalarms................................................................................... 56

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Issue:01ADRAFT

Table39

Newcounters......................................................................................56

Table40

Newparameters................................................................................. 56

Table41

Modifiedparameters...........................................................................57

Table42

Salesinformation................................................................................57

Table43

AllowedbandcombinationsforDualCellandDualBandHSDPA..... 58

Table44

SoftwareRequirements...................................................................... 62

Table45

ModifiedParameters.......................................................................... 65

Table46

SalesInformation................................................................................65

Table47

Softwarerequirements....................................................................... 66

Table48

Newparameters................................................................................. 68

Table49

Salesinformation................................................................................68

Table50

Softwarerequirements....................................................................... 72

Table51

Newcounters......................................................................................75

Table52

Relatedexistingcounters................................................................... 76

Table53

Newkeyperformanceindicators........................................................ 76

Table54

Newparameters................................................................................. 77

Table55

Modifiedparameters...........................................................................77

Table56

Relatedexistingparameters...............................................................77

Table57

Salesinformation................................................................................78

Table58

Softwarerequirements....................................................................... 84

Table59

Newcounters......................................................................................87

Table60

Newparameters................................................................................. 87

Table61

Modifiedparameters...........................................................................88

Table62

Salesinformation................................................................................89

Table63

Softwarerequirements....................................................................... 94

Table64

Newcounters......................................................................................97

Table65

Relatedexistingcounters................................................................... 97

Table66

Newparameters................................................................................. 97

Table67

Modifiedparameters...........................................................................99

Table68

Salesinformation................................................................................99

Table69

Countersverification.........................................................................102

Table70

Countersverification.........................................................................103

Table71

Softwarerequirements..................................................................... 106

Table72

Newparameters............................................................................... 107

Table73

Salesinformation..............................................................................108

Table74

Softwarerequirements...................................................................... 111

Table75

Newcounters.................................................................................... 114

Table76

Relatedexistingcounters................................................................. 116

Table77

Newparameters............................................................................... 116

Table78

Modifiedparameters......................................................................... 117

DN09146788

15

RU50FeatureDescriptionsandInstructions

16

Table79

Salesinformation.............................................................................. 118

Table80

Softwarerequirements..................................................................... 125

Table81

Salesinformation..............................................................................126

Table82

Softwarerequirements..................................................................... 127

Table83

Newparameters............................................................................... 129

Table84

Modifiedparameters.........................................................................130

Table85

Relatedexistingparameters.............................................................130

Table86

Salesinformation..............................................................................131

Table87

..........................................................................................................136

Table88

Newparameters............................................................................... 137

Table89

Modifiedparameters.........................................................................138

Table90

Salesinformation..............................................................................138

Table91

Softwarerequirements..................................................................... 139

Table92

..........................................................................................................139

Table93

Relatedexistingalarms.................................................................... 143

Table94

Salesinformation..............................................................................144

Table95

Softwarerequirements..................................................................... 145

Table96

Newfaults.........................................................................................148

Table97

Newcounters....................................................................................148

Table98

Newparameters............................................................................... 149

Table99

Salesinformation..............................................................................150

Table100

Relatedexistingalarms.................................................................... 170

Table101

Newparameters............................................................................... 170

Table102

NewOMSLDAPparameters............................................................170

Table103

RelatedexistingOMSLDAPparameters......................................... 170

Table104

Salesinformation..............................................................................171

Table105

Softwarerequirements..................................................................... 173

Table106

Newalarms.......................................................................................176

Table107

NewOMSLDAPparameters............................................................177

Table108

Salesinformation..............................................................................177

Table109

Softwarerequirements..................................................................... 178

Table110

FunctionalscopeofOMSSystemStatusViewcomponents............179

Table111

NewAlarms...................................................................................... 181

Table112

Salesinformation..............................................................................181

Table113

Softwarerequirements..................................................................... 182

Table114

Salesinformation..............................................................................184

Table115

Softwarerequirements..................................................................... 185

Table116

TasksinmonitoringandabortingRNWconfigurationmanagement
operations.........................................................................................186

Table117

Alarms.............................................................................................. 190

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Issue:01ADRAFT

Table118

Parameters....................................................................................... 191

Table119

Softwarerequirements..................................................................... 192

Table120

Newfault...........................................................................................194

Table121

Newparameter................................................................................. 194

Table122

Salesinformation..............................................................................194

Table123

Softwarerequirements..................................................................... 197

Table124

Relatedexistingalarms.................................................................... 198

Table125

NewOMSLDAPparameters............................................................198

Table126

Salesinformation..............................................................................199

Table127

Softwarerequirements..................................................................... 200

Table128

Newparameters............................................................................... 202

Table129

Modifiedparameters.........................................................................203

Table130

Salesinformation..............................................................................203

Table131

Softwarerequirements..................................................................... 204

Table132

Newcounters....................................................................................206

Table133

Modifiedcounters............................................................................. 209

Table134

Salesinformation..............................................................................212

Table135

Relatedexistingcounters................................................................. 215

Table136

Newparameters............................................................................... 216

Table137

Salesinformation..............................................................................217

Table138

Softwarerequirements..................................................................... 218

Table139

Salesinformation..............................................................................221

Table140

Softwarerequirements..................................................................... 221

Table141

Parameters....................................................................................... 224

Table142

Salesinformation..............................................................................225

Table143

Softwarerequirements..................................................................... 226

Table144

Newalarms.......................................................................................228

Table145

Modifiedcounters............................................................................. 229

Table146

Salesinformation..............................................................................229

Table147

Softwarerequirements..................................................................... 230

Table148

Newcounters....................................................................................233

Table149

Salesinformation..............................................................................233

Table150

Softwarerequirements..................................................................... 234

Table151

Softwarerequirements..................................................................... 234

Table152

mcRNCstep7capacity.................................................................... 235

Table153

Salesinformation..............................................................................236

Table154

Softwarerequirements..................................................................... 237

Table155

Newparameters............................................................................... 240

Table156

Modifiedparameters.........................................................................241

Table157

Salesinformation..............................................................................241

DN09146788

17

RU50FeatureDescriptionsandInstructions

18

Table158

Softwarerequirements..................................................................... 242

Table159

Salesinformation..............................................................................244

Table160

Softwarerequirements..................................................................... 245

Table161

Softwarerequirements..................................................................... 245

Table162

NewhardwarerequiredaccordingtomcBSCmoduletypes............ 245

Table163

mcBSCmodulecardchangesrequirements.................................... 250

Table164

Softwarerequirements..................................................................... 255

Table165

Softwarerequirements..................................................................... 256

Table166

Salesinformation..............................................................................257

Table167

Softwarerequirements..................................................................... 258

Table168

Numberofneededlicensekeys...................................................... 259

Table169

Existingalarms................................................................................. 260

Table170

Modifiedparameters.........................................................................260

Table171

Salesinformation..............................................................................260

Table172

Softwarerequirements..................................................................... 263

Table173

Salesinformation..............................................................................264

Table174

Softwarerequirements..................................................................... 266

Table175

Salesinformation..............................................................................268

Table176

Softwarerequirements..................................................................... 269

Table177

Relatedexistingalarms.................................................................... 270

Table178

Modifiedparameters.........................................................................271

Table179

Salesinformation..............................................................................271

Table180

Softwarerequirements..................................................................... 272

Table181

Salesinformation..............................................................................273

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Summaryofchanges

Summary of changes
Changesbetweendocumentissuesarecumulative.Therefore,thelatestdocument
issuecontainsallchangesmadetopreviousissues.

Changes between issues 01 (2014-02-28, RU50) and 01A DRAFT


(2014-04-08, RU50 EP1)
RequirementshavebeenupdatedinallRU50mainfeatures.
New feature descriptions
Thefollowingfeaturedescriptionsarenew:

Radioresourcemanagementfeatures

Telecomfeatures

RAN2496:3GPPMinimizationofDriveTests
RAN2443:BTSResourceUtilizationMonitoring
RAN2555:ConfigurableRangesforUserThroughputCounters
RAN2930:IMSI-basedCallMonitoring
RAN2870:TrafficaIPReportsmcRNCforRTTandPacketLossRatio

RNCsolutionfeatures

Issue:01ADRAFT

RAN2919:OMSCertificateUpdateandRevocationSupport
RAN2699:OMSSystemStatusView
RAN3004:ParameterCategorization
RAN2507:RNWPlanProgressIndicatorandAbort
RAN2229:TroubleshootingDataManagementbyNetAct

Performancemonitoringfeatures

RAN2913:LocalandRemoteIPTrafficCapturing

Operabilityfeatures

RAN2211:Multi-CellHSDPA(HSDPA168Mbps)

Transmissionandtransportfeatures

RAN2578:AMRCodecSetfor2G-3GTrFO
RAN3018:BTSLoadBasedAACR
RAN1905:DC-HSUPA23Mbps
RAN2250:EnhancedHSUPAIC
RAN2546:VHSReceiverforHighSpeedTrain

RAN2251:AutomaticmcRNCResourceOptimization
RAN2928:DSPPoolInformationinMeasurements

DN09146788

19

Summaryofchanges

RU50FeatureDescriptionsandInstructions

RAN2959:mcRNCStep7Support
RAN2512:RNCResiliencyforRNC2600
RAN2671:UpgradingofmcBSCtomcRNC

BTSsolutionfeatures

RAN3010:24CellSupportwithFlexiRel3+Rel2
RAN2826:FlexiCompactasRFModule
RAN2784:FlexiLiteBTS1900MHz
RAN2732:FlexiSystemModuleextension,FSM3+FSM2
RAN2393:OpticalFiber:RX/TXLevelMonitoring

Changes between issues 01 DRAFT (2013-12-13, RU50) and 01 (201402-28, RU50)


Description of RAN3017: Additional 6 WCDMA Cell Activation

Managementdatahasbeenupdated.

Description of RAN2264: Smart LTE Handover

Functionaldescriptionhasbeenupdated.
Systemimpacthasbeenupdated.
Managementdatahasbeenupdated.

Description of RAN2963: Data Session Profiling

TheBenefitshavebeenupdated.

Activating RAN3069: RSRQ-based LTE Reselection

Theinstructionshavebeenadded.

Activating RAN147: RRC Connection Setup Redirection

Theinstructionshavebeenupdated.

Description of RAN147: RRC Connection Setup Redirection

Benefitshasbeenupdated.
Functionaldescriptionhasbeenupdated.
Managementdatahasbeenupdated.
Requirementshasbeenupdated.

Verifying RAN147: RRC Connection Setup Redirection

Theinstructionshavebeenupdated.

Deactivating RAN147: RRC Connection Setup Redirection

Theinstructionshavebeenupdated.

New feature descriptions


Thefollowingfeaturedescriptionsarenew:

20

Radioresourcemanagementfeatures

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Summaryofchanges

RAN2482:EnhancedVirtualAntennaMapping

RNCsolutionfeatures

RAN3047:RTTImprovementtoenhanceuserexperience

New feature activation instructions


Featureactivationinstructionshavebeenaddedforthefollowingfeatures:

Radioresourcemanagementfeatures

Transmissionandtransportfeatures

RAN2243:PerformanceMonitoringBasedonETHServiceOAM

Operabilityfeatures

RAN2963:DataSessionProfiling
RAN2179:DualBandHSDPA42Mbps
RAN2482:EnhancedVirtualAntennaMapping
RAN1668:HSUPACompressedModeforLTEandInter-frequencyHandover
RAN2980:MeasurementBasedLTELayering
RAN147:RRCConnectionSetupRedirection
RAN3069:RSRQ-basedLTEReselection
RAN2264:SmartLTEHandover
RAN2881:WCDMAandGSMLayerPriorities-nottested

RAN2199:BTSEvenTriggeredSymptomDataCollection
RAN2554:TransportConfigurationFall-back

BTSsolutionfeatures

RAN3017:Additional6WCDMACellActivation

Changes between issues 00 DRAFT (2013-11-12, RU50) and 01


DRAFT (2013-12-13, RU50)
Updated features
Thefollowingfeaturedescriptionshavebeenupdated:

Radioresourcemanagementfeatures

Issue:01ADRAFT

RAN2963:DataSessionProfiling
RAN2179:DualBandHSDPA42Mbps
RAN1668:HSUPACompressedModeforLTEandInter-frequencyHandover
RAN2980:MeasurementBasedLTELayering
RAN147:RRCConnectionSetupRedirection
RAN3069:RSRQ-basedLTEReselection

DN09146788

21

Summaryofchanges

RU50FeatureDescriptionsandInstructions

Transmissionandtransportfeatures

RAN2199:BTSEventTriggeredSymptomDataCollection
RAN2554:TransportConfigurationFall-back

BTSsolutionfeatures

22

RAN2243:PerformanceMonitoringBasedonETHServiceOAM

Operabilityfeatures

RAN2264:SmartLTEHandover
RAN2881:WCDMAandGSMLayerPriorities

RAN3017:Additional6WCDMACellActivation

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

IntroductiontoRU50features

1 Introduction to RU50 features


1.1 RU50 radio resource management features
SeethefollowingtableformoredetailedinformationonWCDMARANfunctionsand
featureactivation:
RU50 features
Table1

RU50radioresourcemanagementfeatures

Feature

Other related descriptions

Related instructions

RAN2963:DataSessionProfiling

WCDMARANRRMPacketScheduler

ActivatingRAN2963:DataSession
Profiling

WCDMARANPacketDataTransfer
States
RAN2179:DualBandHSDPA42Mbps

WCDMARANHSDPAinBTS
WCDMARANRRMHandoverControl

ActivatingRAN2179:DualBand
HSDPA42Mbps

WCDMARANRRMHSDPA
WCDMARANRRMHSUPA
RAN2482:EnhancedVirtualAntenna
Mapping

Thisinformationwillbeprovidedin
futuredeliveries.

ActivatingRAN2482:EnhancedVirtual
AntennaMapping

RAN1668:HSUPACompressedMode
forLTEandInter-frequencyHandover

WCDMARANRRMHandoverControl

ActivatingRAN1668:HSUPA
CompressedModeforLTEandInterfrequencyHandover

WCDMARANRRMHSUPA
WCDMARANSRNSRelocation

RAN2980:MeasurementBasedLTE
Layering

WCDMARANRRMHSUPA

ActivatingRAN2980:Measurement
BasedLTELayering

RAN147:RRCConnectionSetup
Redirection

WCDMARANRRMAdmissionControl

ActivatingRAN147:RRCConnection
SetupRedirection

WCDMARANRRMHandoverControl
WCDMARANRRMHSDPA
WCDMARANRRMHSUPA
RNCOverloadControl
WCDMARANCallSetupandRelease

RAN3069:RSRQ-basedLTE
Reselection

WCDMARANRRMHandoverControl

RAN2264:SmartLTEHandover

WCDMARANRRMHandoverControl

WCDMARANCallSetupandRelease

WCDMARANRRMHSUPA

Issue:01ADRAFT

DN09146788

ActivatingRAN3069:RSRQ-basedLTE
Reselection
ActivatingRAN2264:SmartLTE
Handover

23

IntroductiontoRU50features

Table1

RU50FeatureDescriptionsandInstructions

RU50radioresourcemanagementfeatures(Cont.)

Feature

Other related descriptions

Related instructions

WCDMARANSRNSRelocation
RAN2881:WCDMAandGSMLayer
Priorities

WCDMARANRRMHandoverControl
WCDMARANCallSetupandRelease

ActivatingRAN2881:WCDMAand
GSMLayerPriorities

RU50 EP1 features


Table2

RU50EP1radioresourcemanagementfeatures

Feature

Other related descriptions

Related instructions

RAN2578:AMRCodecSetfor2G-3G
TrFO

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN3018:BTSLoadBasedAACR

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN1905:DC-HSUPA

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2250:EnhancedHSUPAIC

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2546:VHSReceiverforHigh
SpeedTrain

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

1.2 RU50 telecom features


TherearenoRU50featuresintheTelecomarea.
RU50 EP1 features
Table3

RU50EP1Telecomfeatures

Feature

Other related descriptions

Related instructions

RAN2211:Multi-CellHSDPA(trial)

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

24

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

IntroductiontoRU50features

1.3 RU50 transmission and transport features


SeethefollowingtableformoredetailedinformationonWCDMARANfunctionsand
featureactivation:
RU50 features
Table4

RU50transmissionandtransportfeatures

Feature
RAN2243:PerformanceMonitoring
BasedonETHServiceOAM

Other related descriptions


WCDMARANIPTransport

Related instructions
ActivatingRAN2243:Performance
MonitoringBasedonETHServiceOAM

RU50 EP1 features


Table5

RU50EP1transmissionandtransportfeatures

Feature
RAN2913:LocalandRemoteIPTraffic
Capturing

Other related descriptions


Thisinformationwillbeprovidedin
futuredeliveries.

Related instructions
Thisinformationwillbeprovidedin
futuredeliveries.

1.4 RU50 operability features


SeethefollowingtablesformoredetailedinformationonWCDMARANfunctionsand
featureactivation:
RU50 features
Table6

RU50operabilityfeatures

Feature

Other related descriptions

Related instructions

RAN2199:BTSEventTriggered
SymptomDataCollection

Thisfeaturedoesnothaveanyrelated
descriptions.

ActivatingRAN2199:BTSEvent
TriggeredSymptomDataCollection

RAN2554:TransportConfigurationFall- Thisfeaturedoesnothaveanyrelated
back
descriptions.

ActivatingRAN2554:Transport
ConfigurationFall-back

RU50 EP1 features

Issue:01ADRAFT

DN09146788

25

IntroductiontoRU50features

Table7

RU50FeatureDescriptionsandInstructions

RU50EP1operabilityfeatures

Feature

Other related descriptions

Related instructions

RAN2919:OMSCertificateUpdateand Thisinformationwillbeprovidedin
RevocationSupport
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2699:OMSSystemStatusView

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN3004:ParameterCategorization

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2507:RNWPlanProgress
IndicatorandAbort

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2229:TroubleshootingData
ManagementbyNetAct

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

1.5 RU50 performance monitoring features


TherearenoRU50featuresintheperformancemonitoringarea.
SeethefollowingtableformoredetailedinformationonWCDMARANfunctionsand
featureactivation:
RU50 EP1 features
Table8

RU50EP1performancemonitoringfeatures

Feature

Other related descriptions

Related instructions

RAN2496:3GPPMinimizationofDrive
Tests

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2443:BTSResourceUtilization
Monitoring

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2555:ConfigurableRangesfor
UserThroughputCounters

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2930:IMSI-basedCallMonitoring

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2870:TrafficaIPReportsmcRNC
forRTTandPacketLossRatio

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

26

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

IntroductiontoRU50features

1.6 RU50 RNC solution features


SeethefollowingtableformoredetailedinformationonWCDMARANfunctionsand
featureactivation:

RU50 features
Table9

RU50RNCsolutionfeatures

Feature
RAN3047:RTTImprovementto
enhanceuserexperience

Table10

Other related descriptions


Thisfeaturedoesnothaverelated
descriptions.

Related instructions
Thisfeaturedoesnothaverelated
instructions.

RU50EP1RNCsolutionfeatures

Feature

Other related descriptions

Related instructions

RAN2251:AutomaticmcRNC
ResourceOptimization

Thisfeaturedoesnothaverelated
descriptions.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2928:DSPPoolInformationin
Measurements

Thisfeaturedoesnothaverelated
descriptions.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2959:mcRNCStep7Support

RAN2874:mcRNCHWCapacity
ExpansionSupport

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2512:RNCResiliencyfor
RNC2600

Thisfeaturedoesnothaverelated
descriptions.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2671:UpgradingofmcBSCto
mcRNC

RAN2874:mcRNCHWCapacity
ExpansionSupport

Thisinformationwillbeprovidedin
futuredeliveries.

1.7 RU50 BTS solution features


SeethefollowingtablesformoredetailedinformationonWCDMARANfunctionsand
featureactivation:
RU50 features
Table11

RU50BTSsolutionfeatures

Feature
RAN3017:Additional6WCDMACell
Activation

Other related descriptions


Thisfeaturedoesnothaveanyrelated
descriptions.

Related instructions
ActivatingRAN3017:Additional6
WCDMACellActivation

RU50 EP1 features

Issue:01ADRAFT

DN09146788

27

IntroductiontoRU50features

Table12

RU50FeatureDescriptionsandInstructions

RU50EP1BTSsolutionfeatures

Feature

Other related descriptions

Related instructions

RAN3010:24CellSupportwithFlexi
FSMF+FSMD/ESystemModules

Thisinformationwillbeprovidedin
futuredeliveries.

Thisinformationwillbeprovidedin
futuredeliveries.

RAN2826:FlexiCompactasRF
Module

Thisinformationwillbeprovidedin
futuredeliveries.

Thisfeaturedoesnothaverelated
instructions.

RAN2784:FlexiLiteBTS1900MHz

Thisinformationwillbeprovidedin
futuredeliveries.

Thisfeaturedoesnothaverelated
instructions.

RAN2732:FlexiSystemModule
extension,FSMF+FSMD/E

Thisinformationwillbeprovidedin
futuredeliveries.

Thisfeaturedoesnothaverelated
instructions.

RAN2393:OpticalFiber:RX/TXLevel
Monitoring

Thisinformationwillbeprovidedin
futuredeliveries.

Thisfeaturedoesnothaverelated
instructions.

1.8 Licensing
Theapplicationsoftwarefeatures(ASW)areunderlicensekeymanagement.Alicense
isafilethatincludesthefeatureinformation.Beforealicensedfeaturecanbeactivated,
thelicensefileneedstobetransferredtoandinstalledintheIPA-RNC.Forinformation
ontransferringthelicense,seeLicensemanagementoperationsinRNCinWCDMA
RANLicenseOperation.Forinformationoninstallingthelicense,seeInstallinglicenses
inthenetworkelementinManagingLicense-basedFeaturesinIPA-RNCandManaging
License-basedFeaturesinMulticontrollerRNC.

g
g

SomeRNC-controlledfeaturesareactivatedusinganRNCgeneralparameter
file(PRFILE)orafeatureinformationcontrolfile(FIFILE).Fordetails,see
Parameter-basedoptionmanagementinWCDMARANLicenseOperation.
TherearenolicensesintheFlexiDirectRNC.
AlicensecanbeinstalledusingNetActoralocalMML(IPA-RNC)orSCLI(mcRNC)
interface.IfitisinstalledusingNetAct,thelicensedfeaturestateisautomaticallysetto
ONstate.IftheMML/SCLIinterfaceisused,thedefaultvalueisOFF,andyouneedto
setthefeaturetoONstatemanually.Forinformationonfeaturestates,seeFeature
StatesinWCDMARANLicenseOperation.Thelicense-relatedMMLcommandsare
describedinW7-LicenseandFeatureHandling.

License management in mcRNC


FordetailsonthemcRNC-specificlicensemanagement,seeLicensemanagementin
RNCinWCDMARANLicenseOperationandManagingLicense-basedFeaturesin
MulticontrollerRNC.

License management in WBTS


LicensemanagementinWBTSisbasedonapoolconcept.Eachlicensecontainsa
specificamountofcapacitythatcanbedistributedamongtheselectedWBTSs.
Distributinglicensesfromthepoollicensedecreasestheamountoffreecapacityinthe

28

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

IntroductiontoRU50features

pool.ManagingpoollicensesanddistributingtoWBTSsisdoneviaNetActLicence
Manager.Somebasiclicenseoperations(forexample,licenseinstallationordeletion)
arealsopossiblewithBTSSiteManager.
FordetailsontheWBTS-specificlicensemanagement,seeLicensemanagementin
WBTSinWCDMARANLicenseOperation.

1.9 Reference documentation


Forinformationontheparameters,countersandalarmsrelatedtoeachfeature,seethe
Managementdatasectionofthefeaturedescriptions.
Forparameterdescriptions,see:

WCDMARadioNetworkConfigurationParametersExcelinWCDMARANOperating
Documentation,ParametersinNOLSPIC
IPConfigurationPlanInterfaceParametersforMulticontrollerRNCExcelinWCDMA
RANOperatingDocumentation,ParametersinNOLSPIC
OMSLDAPparameters
FlexiTransportModuleParametersExcelinWCDMARANOperating
Documentation,ParametersinNOLSPIC
FlexiMultiradioBTSWCDMAParametersExcelinWCDMARANOperating
Documentation,ParametersinNOLSPIC
MulticontrollerRadioNetworkConfigurationParametersExcelinWCDMARAN
OperatingDocumentation,ParametersinNOLSPIC
ATMConfigurationPlanInterfaceParametersExcelinWCDMARANOperating
Documentation,ParametersinNOLSPIC
FrequentlyUsedParametersforSS7signallingoverIP
IPConfigurationPlanInterfaceParametersforFlexiDirectRNCExcelinWCDMA
RANOperatingDocumentation,ParametersinNOLSPIC
RadioNetworkParametersinFlexiDirectExcelinWCDMARANOperating
Documentation,ParametersinNOLSPIC
ReferenceInformationServiceinNOLSforRNCparameters

Forcounterdescriptions,see:

RNCCounters-RNWPart
RNCCountersTransportandHWPart
WBTSCounters
FlexiLiteBTSCounters
ReferenceInformationServiceinNOLS

Foralarmdescriptions,see:

Issue:01ADRAFT

IPA-RNCNotices(0-999)
IPA-RNCDisturbances(1000-1999)
IPA-RNCFailurePrintouts(2000-3999)
IPA-RNCDiagnosisReports(3700-3999)
MulticontrollerRNC,IPA-RNCandFlexiDirectRNCBaseStationAlarms(70009000)
FlexiWCDMABaseStationFaults

DN09146788

29

IntroductiontoRU50features

RU50FeatureDescriptionsandInstructions

FlexiLiteBTSFaults
mcRNCAlarms
OMSAlarms

Forkeyperformanceindicatordescriptions,see:

30

WCDMARANKeyPerformanceIndicators

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

2 Radio resource management features


2.1 RAN2578: AMR Codec Set for 2G-3G TrFO
2.1.1 Description of RAN2578: AMR Codec Set for 2G-3G TrFO
Introduction to the feature
InadditiontoexistingAMRcodecmodesets(12.2),(12.2,7.95,5.9,4.75)and(5.9,
4.75),AMRcodecmodeset(12.2,7.4,5.9,4.75)shallbesupportedforenhancingTrFO
callqualitybetween2Gand3G.AMRcodecmodeset(12.2,7.4,5.9,4.75)isalso
supportedbetween3Gcalls.

2.1.1.1

Benefits
End-user benefits
TranscoderfreeoperationandGSMhalfratecanbeusedsimultaneouslyin2G-3Gcalls.

Operator benefits
IncaseofGSMthepreferredAMRhalfratecodecmodeis7.4kbps.Addingittothe
existingcodecratesin3Genables2G-3GTrFOcalls,wherethepreferredAMRhalfrate
codecmodecanbeused.Thisenhancesthevoicequalityifhalf-rateneedstobeused
onGSMside.Otherwiseonlythelowermodes5.9kbpsor4.75kbpswouldneedtobe
usedinTrFOcalls.

2.1.1.2

Requirements
Software requirements
Table13:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
Table13

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

OMS

BTS Flexi

Flexi Lite

RU50
EP1

Notplanned RN8.1

mcRNC4.1

OMS3.1

WN9.1

WL9.1

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

WN9.1

NetAct8EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradio
SystemModuleFSMForFlexiLiteBTSWCDMA.

Issue:01ADRAFT

DN09146788

31

Radioresourcemanagementfeatures

2.1.1.3

RU50FeatureDescriptionsandInstructions

Functional description
Functional overview
NarrowbandAMRcodecmodeset(12.2,7.4,5.9,4.75)isaddedamongtheother
supportedNarrowbandAMRcodecmodesets,whichcanbeselectedbytheoperatorto
beinuse.Thisiscontrolledbyacellbasedradionetworkconfigurationparameter
controllingalsotheusageoftheotherAMRcodecmodesets.AMRcodecmodeset
(12.2,7.4,5.9,4.75)isaddedasanewsupportedset.Itdoesnotreplaceanyexisting
AMRcodecmodeset.
ThenewcodecmodesetisusedwhenCoreNetworkasksittobeused,mainlyincase
of2G-3GTrFOcalls.Thenewcodecmodesetcanbeusedalsobetween3G3Gcalls,
basedonCoreNetworkrequest.
TheAMRcodecmodeset(12.2,7.4,5.9,4.75)canbedeterminedtobeappliedinCS
AMRcallsetup,inSRNCrelocationUEinvolved(HardHandover),inSRNCrelocation
UEnotinvolvedandinInter-RAThandover(from2Gto3G).TheAMRcodecmodeset
(12.2,7.4,5.9,4.75)issupportedoverIurinmobilitycasesi.e.branchadditiontoDRNC
andinanchoringcases.
TheAMRcodecmodeset(12.2,7.4,5.9,4.75)isappliedinLoadBasedAMRcodec
modeselectionforlowloadedcells.
ThedeploymenttonetworkrequiresCoreNetworksupport,RNCsupportandalsoBTS
supportto7.4kbpscodecmode(preferablyinallBTSsunderoneRNC).

2.1.1.4

System impact
Interdependencies between features
TheRAN830:AMRCodecSets(12.2,7.95,5.90,4.75)and(5.90,4.75)featureis
required.

Impact on interfaces
ThisinformationwillbeprovidedInfuturereleases.

Impact on commands
Therearenocommandsrelatedtothisfeature.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

2.1.1.5

RAN2578: AMR Codec Set for 2G-3G TrFO management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

32

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Table14:Newcounterslistscountersintroducedwiththisfeature.
Table14

Newcounters

Counter ID

Counter name

Measurement

M1002C694

AMRCODECSET(12.2,7.4,5.9,4.75)
ALLOCATION

M1002Traffic

M1004C175

AMRCODECSET(12.2,7.4,5.9,4.75)
IURFAIL

M1004L3signallingatIuR

M1006C316

AMRCODECSET(12.2,7.4,5.9,4.75)UE M1006RRCsignalling
FAIL

Related existing counters


Therearenoexistingcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table15:Newparameterslistsparametersintroducedwiththisfeature.
Table15

Newparameters

Full name

Abbreviated name

Managed object

AMRcodecmodeset7.4enabled

AMRCodecSet74Enabled

RNFC

AMRcodecmodesetenabled

AMRCodecSetEnabled

RNFC

WBAMRcodecmodesetenabled

WBAMRCodecSetEnabled

RNFC

Table16:Modifiedparameterslistsparametersmodifiedbythisfeature.
Table16

Issue:01ADRAFT

Modifiedparameters

Full name

Abbreviated name

Managed object

RNCOptions

RncOptions

RNC

DN09146788

33

Radioresourcemanagementfeatures

Table16

2.1.1.6

RU50FeatureDescriptionsandInstructions

Modifiedparameters(Cont.)

Full name

Abbreviated name

Managed object

ConfiguredCSAMRmodesets

CSAMRModeSET

VCEL

ConfiguredCSAMRmodesets

CSAMRModeSET

WCEL

ConfiguredCSWBAMRmodesets

CSAMRModeSETWB

VCEL

ConfiguredCSWBAMRmodesets

CSAMRModeSETWB

WCEL

Sales information
Table17

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCLK

2.2 RAN3018: BTS Load Based AACR


2.2.1 Description of RAN3018: BTS Load Based AACR
Introduction to the feature
Inthecurrentsystemimplementation,BTSoverloaddoesnottriggeraccessclass
restrictionprovidedbytheRAN2480:AutomaticAccessClassRestriction(AACR)
feature.AACRisusedtotemporarilypreventnetworkaccessforUEswithdefined
accessclassthatisSIM-specificrandomnumber(0,1,9).TheRNCcontrolsthe
limitationleveldynamicallybasedonthenetworkload.
TheRAN3018:BTSLoadBasedAACRfeaturetriggerstheAACRwhentheBTSisin
theprocessingoverloadduetocongestionofRLprocedures.

2.2.1.1

Benefits
End-user benefits
ThisfeatureprovidessmoothrecoverytothenormalsystemstatewhenthereisaBTS
overload.Underoverloadconditions,thisfeatureallowsmoresubscriberstobeserved,
evenifsomeusersaretemporarilyrestricted.

Operator benefits
ThisfeatureprovidessmoothrecoveryfromhighBTScontrolplaneprocessingoverload.

34

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

2.2.1.2

Radioresourcemanagementfeatures

Requirements
Software requirements
Table18:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
Table18

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi Direct OMS


RNC

Flexi BTS

RU50EP1

Notplanned RN8.1

mcRNC4.1

Notplanned OMS3.1

WN9.1

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

SGSN

UE

NetAct8
EP2

Supportnot Supportnot Supportnot


required
required
required

Notplanned WN9.1

MGW

Support
not
required

Hardware requirements
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradio
SystemModuleFSMF.

2.2.1.3

Functional description
Functional overview
ThisfeaturehelpstheBTStorecoverfromthenetworkoverloadconditionsbytriggering
theAutomaticAccessClassRestriction(AACR),providedbytheRAN2480:Automatic
AccessClassRestrictionfeature,whentheBTSprocessingloadishigh.
TheRAN3018:BTSLoadBasedAACRfeatureprovides:

overloadprotectionfortheBTSsbasedonthenewandimprovedBTSnotification
aboutBTSprocessingload
theabilitytosetNBAPsignaling/BTSprocessingloadasatriggerforAACR
apossiblitytorestrictCell_PCHtoCell_FACH/Cell_DCHstatetransitionsinacell
duetohighAACRlevelinthecell(AACRtriggeredbytheRAN2480:Automatic
AccessClassRestrictionfeatureortheRAN3018:BTSLoadBasedAACRfeature)

TheBTS'scapacityforhandlingNBAPsignalingislimited.TheNBAPentityinthe
RNCcontinuouslyfollowsthenumberofsimultaneouslyongoingNBAPsignaling
procedurestowardstheBTS.Incurrentsystemimplementation,whenthenumberof
parallelNBAPproceduresietstoohigh,thesystemlimitstheamountofincomingRRC
ConnectionRequestsandRadioLinkSetupprocedurestowardstheloadedBTS.
WhentheRAN3018:BTSLoadBasedAACRfeatureisactivated,theRNCstartsthe
automaticaccessclassrestrictionprocedureinthecellsoftheloadedBTSbasedonthe
informationfromtheBTSoverloadprotectionprocedure.Withtheaccessclass

Issue:01ADRAFT

DN09146788

35

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

restrictionproceduretheBTSandtheRNCcanbeprotected,astheUEsaretemporarily
bannedfromenteringthenetwork.Thisisdonebysendingtheaccessclassbarredlistin
systeminformationblock3(SIB3).
TherestrictionactionsintroducedwiththeRAN3018:BTSLoadBasedAACRfeature
startoncetheRNCdetectsthattheBTScannothandlealltherequests.IftheNBAP
signalingoverloadcontinueslongenough,AACR-basedrestrictionisstarted.Levelof
AACRrestrictionisthenupdateddynamicallyaccordingtodetectedNBAPsignaling
load.
WhentheAACRlevelinthecellexceedsthethresholdAACRleveldefinedbythe
AutoACResFromCellPCHparameter,theRNClimitsthenumberofCell_PCHto
Cell_DCHstatetransitionsinthecellinthefollowingway:

anumberofUEsismovedtoIDLEstateinsteadofCell_PCHtoCell_DCHstate
transition
anumberofUEsiskeptinCell_PCHstate

TheselectionoftheUEsisbasedontherestrictedaccessclassesinthecellatthat
momentandtheregulationactiondependsonhowlongtheaccessclassoftheUEis
assumedtoberestricted.

2.2.1.4

System impact
Interdependencies between features
ThisfeaturerequirestheRAN2480:AutomaticAccessClassRestrictionfeature.

Impact on network and network element management tools


Informationonthisfeaturesimpactoninterfaceswillbeprovidedinfurtherdeliveries.

Impact on system performance and capacity


ThisfeatureprovidessmoothrecoveryfromBTSoverload.

2.2.1.5

RAN3018: BTS Load Based AACR management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Table19:Newcounterslistscountersintroducedwiththisfeature.
Table19

36

Newcounters

Counter ID

Counter name

Measurement

M1000C408

ACCESSCLASSRESTRICTIONACTIVEBTS
SAMPLES

CellResource

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table19

Radioresourcemanagementfeatures

Newcounters(Cont.)

Counter ID

Counter name

Measurement

M1005C255

RLSETUPREJECTDUETOOVERLOAD

L3signallingatIub

M1005C256

RLADDITIONREJECTDUETOOVERLOAD

L3signallingatIub

M1005C257

RLRECONFIGURATIONREJECTDUETO
OVERLOAD

L3signallingatIub

M1005C258

RLSETUPFAILDUETOBTSOVERLOAD

L3signallingatIub

Table20:Relatedcounterslistscountersrelatedtothisfeature.
Table20

Relatedcounters

Counter ID

Counter name

Measurement

M1000C404

ACCESSCLASSRESTRICTIONACTIVE
SAMPLES

CellResource

M1000C405

ACCESSCLASSESBLOCKEDAMOUNT

CellResource

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table21:Newparameterslistsparametersintroducedwiththisfeature.
Table21

Newparameters

Full name

Abbreviated name

Managed
object

AutomaticAccessClassRestriction
basedonBTSloadEnabled

AutoACResBTSEnabled

RNFC

BTSloadindicationselection

BTSLoadIndSel

RNFC

AccessClassRestrictionforUEs
transferringfromCell_PCHstateto
Cell_FACH/Cell_DCH

AutoACResFromCellPCH

RNAC

Table22:Modifiedparameterslistsparametersmodifiedbythisfeature.

Issue:01ADRAFT

DN09146788

37

Radioresourcemanagementfeatures

Table22

2.2.1.6

RU50FeatureDescriptionsandInstructions

Modifiedparameters

Full name

Abbreviated name

Managed
object

RNCOptions

RncOptions

RNC

AutomaticAccessClassRestriction
Enabled

AutoACResEnabled

RNFC

AutomaticAccessClassRestriction
TriggerofRNCLoad

AutoACRTrigRNCLoad

RNAC

AccessRestrictionforCell_PCHstate
UE

AutoACRestForCellPCH

RNAC

Accessclassrestrictionguardtime

RNARDSACGuardTime

RNAC

Sales information
Table23

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCLK

2.3 RAN2963: Data Session Profiling


2.3.1 Description of RAN2963: Data Session Profiling
Introduction to the feature
TheRAN2963:DataSessionProfilingfeatureprovidesafasterweb-browsingsessionfor
theend-user.

2.3.1.1

Benefits
End-user benefits
Thisfeatureenablestheend-userhavingfastweb-browsingsessions.

Operator benefits
Thisfeaturebenefitstheoperatorasfollows:

38

Itallowstheoperatortousehigherthresholdsforthecommonchannels.Keep-alivetypesignalingismovedtocommonchannelsandmoreHSPAresourcesare
availablefordata.Thatimpactstheend-userexperienceandincreasesthe
satisfaction.

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

2.3.1.2

Radioresourcemanagementfeatures

ItallowstheusageoftheshorterCell_DCHstateinactivitytimers,resultinginthe
fasterdirectCell_PCHtoCell_DCHallocation.ThisimprovesHSPAefficiency.
ThelargeamountsofdatasentinshorttimeperiodareallocatedtotheHSPA
directly.InthiscaseCell_FACHstateisskipped,andstatechangefromCell_PCHto
Cell_DCHisapproximatelyonesecondfaster.

Requirements
Software requirements
Table24:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
Table24

Softwarerequirements

RAS

Flexi
Direct

IPA-RNC

mcRNC

Flexi Direct
RNC

OMS

BTS Flexi

RU50

FlexiDirect
RU50

RN8.0

mcRNC4.1

ADA6.0

OMS3.01)

Supportnot
required

OMS3.12)
IHO6.03)

Flexi Lite
BTS

BTS Flexi
10

NetAct

MSC

SGSN

MGW

UE

Supportnot
required

Supportnot
required

NetAct8
EP11)

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

NetAct8
EP22)3)

1)forRU50
2)forRU50EP1
3)forFlexiDirectRU50

Hardware requirements
Thisfeaturerequiresnoneworadditionalhardware.

2.3.1.3

Functional description
Functional overview
TheRAN2963:DataSessionProfilingfeatureaimstoprovidefasterwebbrowsing.This
isachievedbymovingtheterminaldirectlytotheCell_DCH,eventhoughtheinitialdata
amountsuggestsallocationtotheCell_FACH-theamountofdataisbelowtheRNPS TrafVolThresholdULLowparameter.
Whenthelargedataamountisidentifiedinthesession(theLargeDataThrparameter
valueisexceeded),aftertheendofthesession(whentheUEismovedtothe
Cell/URA_PCHstate),thetimerdefinedbytheLargeDataTimeparameterisstarted.
TheUE,beingintheCell/URA_PCHstate,startsnextdatasessionbysendingtheRRC:
CELLUPDATEmessagewithcellupdatecausesetasuplinkdatatransmission.When
thetimedefinedbytheLargeDataTimeparameterisnotexceeded,theUEismoved

Issue:01ADRAFT

DN09146788

39

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

directlytotheCell_DCHstate,withtheRRC:CELLUPDATECONFIRMmessage.After
successfulprocedure,whentheRRC:RADIOBEARERRECONFIGURATION
COMPLETEmessageissuccessfullyreceivedfromUE,theRNCupdatesthe
M1006C309:SUCCESSFULPCHTODCHTRANSDUETODATASESSION
PROFILINGcounter,ifTVIisnotsetasTRUEinRRC:CELLUPDATEmessage.
Theamountofdata(LargeDataThr)andthetimeperiod(LargeDataTime)arethe
parametersdefinedbytheoperator.
Thefaststatechangeisperformedbothforsendingandreceivingdata.
FortheUEscapableofusingtheHS-RACH,anRNPS- HSChaPrefInDataSesProf
parameterisused.ItallowseitheradirecttransfertheCell_DCHstateorstayinginthe
Cell_FACHstateandusingHS-RACH/FACHchannelsprovidedthedatasession
profilingconditions.
ForproperfunctioningoftheRAN2963feature,pleasemindthefollowingparameter
configuration:

2.3.1.4

RNFC-DCHtoPCHEnabledshouldbesettoitsdefaultvalue-enabled.
RNFC-CUCforPCHtoDCHallowedshouldbesettoitsdefaultvalue-true.
WAC-MSActivitySupervisionshouldbesettothevalue> 0.

System impact
Interdependencies between feature

RAN1913:HighSpeedCell_FACH
ThefeatureenablesaspecialhandlingforHS-RACH-capableUE.Ifpreferred,the
featurecanbedisabledforHS-RACH-capableUEsusing
HSChaPrefInDataSesProfparameter.
RAN2494:FastCell_PCHSwitching
ThisfeatureisrecommendedtobeusedwiththeDataSessionProfilingfeature.It
helpsinachievingfasterstatechangestotheCell_DCHstate.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on commands
Therearenocommandsrelatedtothisfeature.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


ThestatechangefromtheCell_PCHtoCell_DCHisapproximatelyonesecondfaster.

2.3.1.5

RAN2963: Data Session Profiling management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

40

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Table25:Newcounterslistscountersintroducedwiththisfeature.
Table25

Newcounters

Counter ID

Counter name

Measurement

M1006C309

SUCCESSFULPCHTODCHTRANSDUE
TODATASESSIONPROFILING

RRCsignalling(RNC)

Table26:Relatedexistingcounterslistsexistingcountersrelatedtothisfeature.
Table26

Relatedexistingcounters

Counter ID

Counter name

Measurement

M1006C174

STATETRANSITIONTIMEPCHTODCH

RRCsignalling(RNC)

M1006C175

DENOMINATORFORSTATETRANSITION RRCsignalling(RNC)
TIMEPCHTODCH

M1006C196

ATTEMPTEDPCHTODCHTRANSITIONS RRCsignalling(RNC)
USINGUM-RLC

M1006C197

SUCCESSFULPCHTODCH
TRANSITIONSUSINGUM-RLC

RRCsignalling(RNC)

M1006C198

CELLRESELECTIONSDURINGPCHTO
DCHTRANSITIONSUSINGUM-RLC

RRCsignalling(RNC)

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table27:Newparameterslistsparametersintroducedwiththisfeature.
Table27

Issue:01ADRAFT

Newparameters

Full name

Abbreviated name

Managed object

DataSessionProfilingEnabled

DataSessionProfEnabled

RNFC

LargeDataThreshold

LargeDataThr

RNPS

DN09146788

41

Radioresourcemanagementfeatures

Table27

RU50FeatureDescriptionsandInstructions

Newparameters(Cont.)

Full name

Abbreviated name

Managed object

LargeDataTime

LargeDataTime

RNPS

HS-RACH/FACHPreferredinData
SessionProfiling

HSChaPrefInDataSesProf

RNPS

Table28:Modifiedparameterslistsparametersmodifiedbythisfeature.
Table28

2.3.1.6

Modifiedparameters

Full name

Abbreviated name

Managed object

RNCOptions

RncOptions

RNC

Uplinktrafficvolumemeasurementlow
threshold

TrafVolThresholdULLow

RNPS

ULtrafficvolumethresholdfor
Smartphone

SmartTrafVolThrUL

WCEL

Downlinktrafficvolumemeasurement
lowthreshold

TrafVolThresholdDLLow

WCEL

DLtrafficvolumethresholdfor
Smartphone

SmartTrafVolThrDL

WCEL

DownlinkNASsignallingvolume
threshold

NASsignVolThrDL

WCEL

Sales information
Table29

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCLK

2.3.2 Activating RAN2963: Data Session Profiling


Purpose
Followthisproceduretoactivatethisfeature.
Formoreinformationonthefeature,seetheRAN2963:DataSessionProfilingfeature
description.

42

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Before you start

RestartoftheRNCisnotrequiredaftertheactivationofthisfeature.
Thisproceduredoesnotrequirecell-locking.
Thisproceduredoesnotcausedowntime,anditcanbeactivatedatanytimeof
theday.
Makesureyouhaveaccesstothefollowingapplications:

OMSElementManager
ApplicationLauncher

Thisfeatureiscontrolledbyalicense.Forinformationonmanaginglicenses,see
Licensing.
TosetthefeaturestatetoON,usethefollowingcommand:

forIPA-RNC:
ZW7M: FEA=4654:ON;

Thefollowingfeaturesarerecommendedtobeactivated/configuredbeforeactivationof
theRAN2963:DataSessionProfilingfeature:

RAN2494:FastCell_PCHSwitching
RAN1232:FastCallSetupfromCell_PCHState

Thefollowingparametersneedtobesetasfollows:

TheWAC-MSActivitySupervisionmustbesettonon-zerovalue,toallowthe
Cell_PCHDataSessionProfilingtofunction.
TheRNFC-CUCforPCHtoDCHallowedparametermustbesettoitsdefaultvaluetrue-toallowtheDataSessionProfilingtofunction.

TheRNFC-DCHtoPCHEnabledissuggestedtobesettothevalue1(Enabled).

Open the OMS Element Manager.

Go to the Topology Tree View.


Select:Network ManagementTopology Tree View

Issue:01ADRAFT

DN09146788

43

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

Expand the RNFC object.

Configure the RNFC object.


a) From the drop-down menu select Edit Parameters.
b) Set the DataSessionProfEnabled parameter value to Enabled.

Save the changes.


a) Click the Apply button.

2.3.3 Verifying RAN2963: Data Session Profiling


Purpose
Followthisproceduretoverifythatthisfeatureworksproperlyinthenetwork.

Activate measurement M1006.


IntheApplicationLauncher,activatethemeasurementM1006andsetthe
measurementintervalto15minutes.

Start the PS session with the smartphone.


Itcanbeinternet-browsing,mailboxchecking.Thetransmitteddataamountmustbe
higherthanthevaluespecifiedwiththeLargeDataThrparameter.

During the session make pauses.


Duringthedatasessionmakepauses,butkeeptheRRCconnection.Thepauses
mustnotbelongerthanthetimevaluedefinedintheLargeDataTimeparameter.

Resume the user-data transmission.


Afterthepause,whentheUEwasmovedfromtheCell_DCHtoCell_PCH,renew
theuser-datatransmission.Evenalittledataamountissufficientforthepurposesof
thevenerationprocess.Thedatatransmissionmustnotbelongerthanthetime
valuedefinedbytheLargeDataTimeparameter.

Open the Application Launcher.

Use the RNW measurement management application to start measurements of


the Cell_PCH to Cell_DCH transitions due to data session profiling counter.
ThevalueoftheM1006C309(SUCCESSFULPCHTODCHTRANSDUETODATA
SESSIONPROFILING)countershouldbelargerthan0.Thatimpliesthatthedirect
transmissionfromtheCell_PCHtoCell_DCHstatehasoccurred.

44

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

2.3.4 Deactivating RAN2963: Data Session Profiling


Purpose
Followthisproceduretodeactivatethisfeature.

Open the OMS Element Manager.

Go to the Topology Tree View.


Select:Network ManagementTopology Tree View

Expand the RNFC object.

Configure the RNFC object.


a) From the drop-down menu select Edit Parameters.
b) Set the DataSessionProfEnabled parameter value to Disable.

Save the changes.


a) Click the Apply button.

2.4 RAN1905: DC-HSUPA


2.4.1 Description of RAN1905: DC-HSUPA
Introduction to the feature
ThefeatureallowsusageoftwoadjacentWCDMAcarrierssimultaneouslyinULfora
singleUE.

2.4.1.1

Benefits
End-user benefits
ThisfeatureimprovestheusageoftheNRTservices,likee-mailsendingandreceiving,
webbrowsing,chatting,videofileuploading,photouploading.

Operator benefits
Thisfeaturebenefitstheoperatorasfollows:

Issue:01ADRAFT

IncreasestheULpeakbitrateto11,5Mbps.
IncreasestheaverageUEULdataratebyupto100%inburstytraffic.
ProvidesperfectloadbalancingacrossULcarriers,utilisingtheunusedairinterface
resources.

DN09146788

45

Radioresourcemanagementfeatures

2.4.1.2

RU50FeatureDescriptionsandInstructions

Requirements
Software requirements
Table30:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
RAS

Flexi
Direct

IPA-RNC

mcRNC

Flexi
Direct
RNC

OMS

Flexi
BTS

Flexi Lite
BTS

RU50
EP1

Not
planned

RN8.1

mcRNC4.1

Not
planned

OMS3.1

WN9.1

WL9.1

Table30

Softwarerequirements

Flexi 10 BTS NetAct


WN9.1

MSC

SGSN MGW

UE

NetAct8EP2 Supportnotrequired SG7.0 Supportnotrequired 3GPPRel-9

Hardware requirements
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/E,orFlexiMultiradio
SystemModuleFSMForFlexiLiteBTSWCDMA.

2.4.1.3

Functional description
Functional overview
TheRAN1905featureallowstheuserequipmenttotransmitsimultaneouslyontwo
adjacentULcarriers.
Duringthedualcarrieroperationmode,theUEsendsdataovertwoparallelE-DCHs,
onepereachcarrier.EachofthedualE-DCHistransmittedoveritsownActiveSet,
consistingofservingandnon-servingRadioLinksets.
CombiningofthedatastreamsfromthetwocarriersisdoneonMAC-islayerinthe
SRNC.TheDCHSUPAisdefinedonlywithE-DCH2msTTIandF-DPCH.Scheduling
grantsforUEsaregivenindependentlyonbothcarriers,basedontheavailablepower
andservinggrantvalueforeachcarrier.TheSRBsareontheprimarycarrier.
Thedistributionofchannelsbetweenthetwocarriers(primarycarrierandsecondary
carrier)ispresentedinthefollowingpicture.

46

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Figure1

Radioresourcemanagementfeatures

DC-HSUPAphysicalchannelstructure.Physicalchannelsdistribution
DC-HSUPA physicalchannelstructure

Pripary
carrier

E-DPDCHs
E-DPCCH
HS-DPCCH

UL

Of1DCHSUPA UE

DPCCH
HS-SCCH
HS-PDSCH

E-AGCH
E-RGCH
E-HICH

DL

E-DPCH

E-DPDCHs
E-DPCCH
UL
DPCCH
HS-SCCH
HS-PDSCH

E-AGCH
E-RGCH

DL

E-HICH
E-DPCH

Secondary
carrier

ItispossibletoallowtheDC-HSUPAoperationfortheUEonlyintheCell_DCHstate.
TheSRNCallocatesDC-HSUPAalwayswhenitispossible.Thefollowingconditions
mustbemetbeforeitispossibletoallocateDC-HSUPA:

Issue:01ADRAFT

TheUEhasinformedthatitsupportsDC-HSUPA.
TheDC-HSUPAisallowedforusedservicecombination,thatis,uptothree
InteractiveorBackgroundPSNRTRABs.TheDC-HSUPAisnotsupported,when
ConversationalorStreamingserviceisconfigured
ThereisnoradiolinkoverIurintheactiveset
TheDC-HSUPAisenabledinallthecellsofthecurrentDCHactivesetandintheir
possibleDC-HSDPA/DC-HSUPAcellpairsinthesamesector.Furthermorethe
primary/possiblesecondaryE-DCHactivesetontheprimary/secondaryUL
frequencyisequaltotheDCHactivesetontheprimary/possiblesecondaryUL
frequency
ItispossibletoallocatetheDC-HSDPAfortheUEintheprimaryandsecondary
servingHS-DSCHcell
ItispossibletoallocatetheF-DPCHfortheUEinallprimaryandsecondaryE-DCH
activesetcells
ItispossibletoallocatetheHSUPA2msTTIinallprimaryandsecondaryE-DCH
activesetcells
ItispossibletoallocatetheFlexibleRLCfortheUEinuplink

DN09146788

47

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

ItispossibletoallocatetheDC-HSUPAinallprimaryandsecondaryE-DCHactive
setcells

ThesetupofthefirstRT(ConversationalorStreaming)RABcauseschanneltypeswitch
toHSPA.ThereleaseofthelastRT(ConversationalorStreaming)RABmakesDCHSUPAallocationpossible.

2.4.1.4

System impact
Interdependencies between features
Thefollowingfeaturesmustbeactivated,inordertoactivatetheRAN1905:DC-HSUPA
feature:

RAN1016:FlexiBTSMultimodeSystemModule,RAN1848:FlexiBTSMultimode
SystemModule-FSME,orRAN2262:FlexiMultiradioSystemModules
RAN1201:FractionalDPCH
RAN1470:HSUPA2msTTI
RAN1906:DC-HSDPA:Dual-CellHSDPA42Mbps
RAN1910:FlexibleRLCinUL

ThefollowingfeaturesareaffectedbytheRAN1905:DC-HSUPAfeature:

RAN971:HSUPADownlinkPhysicalChannelPowerControl
RAN2124:HSPA128UsersperCell

TheRAN1905:DC-HSUPAfeatureisrelatedtothefollowingfeatures:

RAN1668:HSUPACompressedModeforLTEandInter-frequencyHandover
RAN2211:Multi-CellHSDPA
RAN2509:ApplicationAwareRAN
RAN2886:FasterOLPC
ByshorteningtheOLPCSIRtargetmodulationinterval,thisfeaturereducesnumber
ofretransmissionsandimprovestheHSUPAcellcapacity.
RAN2302:DynamicHSUPABLER
ThisfeatureincreasestheCellPeakthroughput,optimizesburstytraffic,improves
thecelledgedata-rate,andimprovesacellcoverage.

Impact on interfaces
Thisfeatureimpactsinterfaces(andprotocols)asfollows:

interfacesbetweenBTSandRNC(Iub,NBAP)

48

NBAP:AUDITRESPONSEandNBAP:RESOURCESTATUSINDICATION
CellCapabilityContainerIEisenhancedtoindicateBTSsDC-HSUPAcapability
toRNC.
NBAP:RADIOLINKSETUPREQUEST
AnadditionalE-DCHCellInformationRLSetupReqIEisintroducedforRL
configurationonuplinksecondarycell.
Theprocedureofestablishingtheradiolinkisasfollows:
RADIOLINKSETUPREQUEST>AdditionalE-DCHCellInformationRLSetup
Req>AdditionalE-DCHCellInformationSetup>AdditionalE-DCHFDDSetup
Information>AdditionalE-DCHFDDInformation>E-DCHMaximumBitrateIE

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

TheE-DCHMaximumBitrateIEspecifiesthemaximumbitratesupportedper
carrier
NBAP:RADIOLINKSETUPRESPONSEandNBAP:RADIOLINKSETUP
FAILURE
AnadditionalE-DCHCellInformationResponseIEisintroducedforsecondary
cellRLconfigurationresponse.
NBAP:RADIOLINKADDITIONREQUEST
AnadditionalE-DCHCellInformationRLAddReqIEisintroducedforRLaddition
duringsofterhandoveronsecondaryE-DCH.
NBAP:RADIOLINKADDITIONRESPONSEandNBAP:RADIOLINK
ADDITIONFAILURE
AnadditionalE-DCHCellChangeInformationResponseIEisintroducedforRL
additionresponseduringsofterhandoveronsecondaryE-DCH.
NBAP:RADIOLINKRECONFIGURATIONPREPARE
AnadditionalE-DCHCellInformationRLReconfPrepIEisintroducedforRL
reconfigurationofsecondaryE-DCH.
NBAP:RADIOLINKRECONFIGURATIONREADY
AnadditionalE-DCHCellInformationResponseRLReconfIEisintroducedforRL
reconfigurationresponseofsecondaryE-DCH.
NBAP:SECONDARYULFREQUENCYUPDATEINDICATIONandNBAP:
SECONDARYULFREQUENCYREPORT
ThesemessagesarenewlyintroducedforDC-HSUPA.
NBAP:RADIOLINKPARAMETERUPDATEINDICATION
AnadditionalE-DCHCellInformationRLParamUpdIEisintroducedforRL
parameterupdateindicationofsecondaryE-DCH.But,inNSNimplementation
thismessageisnotused.So,nochangesneeded.

FrameProtocolImpacts

TheULMaxInfoIEisintroducedinOuterLoopPCControlframeandE-DCH
TYPE2ULDataframe,todifferentiateprimaryandsecondarycarrierframesin
singleIubtransportbearer.
TheTNLCongestionIndicationcontrolframeisusedtoindicatecongestionin
thetransportbearer.

ThefollowingL3(RRC)messagesareaffectedbythefeatures:

ACTIVESETUPDATE
CELLUPDATECONFIRM
PHYSICALCHANNELRECONFIGURATION
RADIOBEARERRECONFIGURATION
RADIOBEARERRELEASE
RADIOBEARERSETUP
RRCCONNECTIONSETUPCOMPLETE
TRANSPORTCHANNELRECONFIGURATION
MEASUREMENTREPORT

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Issue:01ADRAFT

DN09146788

49

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

Impact on system performance and capacity


Thisfeatureimpactssystemperformanceandcapacityasfollows:

2.4.1.5

increaseinthedataratesofferedtoUEs-11,5Mbps,onL1(withQPSK)
enlargeintheavailablebandwidth,whatallowsthetrunkinggainandhighercell
throughput
accordingtothefeasibilitystudy,thedoublethroughputfortheUEpersectorpercell
canbeexpected(comparingtoSCHSUPA)infullbuffertrafficforoneUE,inbursty
traffic-upto10UEspersectorpercellcangetthedoublethroughput(comparingto
SCHSUPA)

RAN1905: DC-HSUPA management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Table31:NewAlarmspresentsalarmsintroducedwiththefeature.
Table31

NewAlarms

Alarm ID

Alarm name

7795

INCONSISTENCYINHIGHPEAKRATEHSPA
CONFIG

3325

INCONSISTENCYINCONFIGURATION
PARAMETERS

Measurements and counters


Table32:Newcounterslistscountersintroducedwiththisfeature.
Table32

50

Newcounters

Counter ID

Counter name

Measurement

M1001C711

UESUPPORTFORE-DCHCATEGORY8

ServiceLevel(RNC)

M1001C712

UESUPPORTFORE-DCHCATEGORY9

ServiceLevel(RNC)

M1001C743

ACCESSSTRATUMRELEASE
INDICATORRELEASE10

ServiceLevel(RNC)

M1002C691

SC-HSUPASELECTEDDUETOULLOAD

Traffic(RNC)

M1006C303

RADIOBEARERCONFIGURATIONFOR
DC-HSUPASUCCESSFUL

RRCsignalling(RNC)

M1006C304

RADIOBEARERCONFIGURATIONFOR
DC-HSUPAFAILED

RRCsignalling(RNC)

M1022C248

CHANNELSWITCHFROMSC-HSUPATO
DC-HSUPASUCCESSFUL

SUCC_SWI_SCHSUPA_TO_
DCHSUPA

M1022C249

CHANNELSWITCHFROMDC-HSUPATO PacketCall(RNC)
SC-HSUPASUCCESSFUL

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table32

Radioresourcemanagementfeatures

Newcounters(Cont.)

Counter ID

Counter name

Measurement

M5005C36

SUMOFDCHSUPAUSERS

HSPAinWBTSExtension
(WBTS)

M5005C37

MAXNUMBEROFDCHSUPAUSERS

HSPAinWBTSExtension
(WBTS)

M5005C38

SUMOFACTIVEDCHSUPAUSERS
USING2C

HSPAinWBTSExtension
(WBTS)

M5005C39

SUMOFACTIVEDCHSUPAUSERS
USING1C

HSPAinWBTSExtension
(WBTS)

M5005C48

DCHSUPAUSERSDENOMINATOR

HSPAinWBTSExtension
(WBTS)

M5005C49

SUMDC-HSUPAMACIPDUDATAUSING
2CARRIERS

HSPAinWBTSExtension
(WBTS)

M5005C50

SUMDC-HSUPAMACIPDUDATAFOR
PRIMARYCARRIER

HSPAinWBTSExtension
(WBTS)

M5005C51

SUMDC-HSUPAMACIPDUDATAFOR
SECONDARYCARRIER

HSPAinWBTSExtension
(WBTS)

M5005C52

SUMOFMACIPDUFORDC-HSUPA
USERSUSING2CARRIERS

HSPAinWBTSExtension
(WBTS)

M5005C53

SUMOFMACIPDUFORDC-HSUPA
USERSUSINGPRIMARYCARRIER

HSPAinWBTSExtension
(WBTS)

M5005C54

SUMOFMACIPDUFORDC-HSUPA
USERSUSINGSECONDARYCARRIER

HSPAinWBTSExtension
(WBTS)

Key performance indicators


Thisinformationwillbeprovidedinfurtherdeliveries.

Parameters
Table33:Newparameterslistsparametersintroducedwiththisfeature.
Table33

Newparameters

Full name

Abbreviated name

Managed object

DCHSUPAEnabled

DCellHSUPAEnabled

WCEL

DPCCHPoweroffsetforsecondaryUL
frequency

DPCCHPwrOffsetSecULFreq

RNHSPA

MaximumnumberofE-DCHusersper
MAC-i/isscheduler

MaxNumberEDCHS

WCEL

Table34:Modifiedparameterslistsparametersmodifiedbythisfeature.

Issue:01ADRAFT

DN09146788

51

Radioresourcemanagementfeatures

Table34

RU50FeatureDescriptionsandInstructions

Modifiedparameters

Full name

Abbreviated name

Managed object

RNCOptions

RncOptions

RNC

MaximumnumberofE-DCHsinthecell

MaxNumberEDCHCell

WCEL

MaximumnumberofE-DCHsinthe
localcellgroup

MaxNumberEDCHLCG

WBTS

NumberofE-DCHsreservedforSHO
branchadditions

NumberEDCHReservedSHOB WCEL
ranchAdditions

Inactiveusersoverloadpreventivefactor InacUsersOverloadFact

RNHSPA

HSPA128UsersperCell

HSPA128UsersPerCell

WCEL

HSPA72UsersperCell

HSPA72UsersPerCell

WCEL

HSUPAxusersenabled

HSUPAXUsersEnabled

WBTS

TherearenoPRFILEparametersrelatedtothisfeature.

2.4.1.6

Sales information
Table35

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCLK

2.5 RAN2179: Dual Band HSDPA 42 Mbps


2.5.1 Description of RAN2179: Dual Band HSDPA 42 Mbps
Introduction to the feature
WithRAN2179:DualBandHSDPA42Mbps,itispossibletouseDualCellHSDPAwith
twocarrierslocatedindifferentfrequencybands(example:Carrier1inband2110-2170
MHzandCarrier2inband925-960MHz).DualBandHSDPAisthereforeverysimilarto
DualCellHSDPA,theonlydifferenceisatLayer1:thecarriersareindifferentfrequency
bands.FormoreinformationonDualCellHSDPA,seeRAN1906:DualCellHSDPAin
WCDMARAN,Rel.RU20,FeatureDescriptions.

2.5.1.1

Benefits
End-user benefits
Withthisfeature,end-userbenefitsfromincreasedcoverageandthroughput.

52

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Operator benefits
Withthisfeature,DualCellHSDPAbenefitscanbeobtainedevenwhennocontiguous
10MHzfrequencyallocationisavailable.Gainsareobtainedfromadditionalfrequency
band.Lowerbandprovidescoverage,whilehigherbandprovidesincreasedcapacity
andpeakrate.BTSbasedschedulingenablesdynamicresourcesharing,sothatfaraway-UEsmainlyuselowfrequencyband,whileclose-by-UEsmainlyusethehigh
frequency.Thisapproachmaximizesthesectorcoverageandcapacity.

2.5.1.2

Requirements
Software requirements
Table36:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
Table36

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi
OMS
Direct RNC

Flexi BTS

RU50

FlexiDirect
RU50

mcRNC4.1

ADA6.0

WN9.0

RN8.0

OMS3.01)
OMS3.12)
IHO6.03)

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

SGSN

Not
planned

WN9.1

NetAct8
EP11)

Supportnot SG8.0
required

MGW

UE

Supportnot 3GPPRelrequired
9

NetAct8
EP22)3)

1)forRU50
2)forRU50EP1
3)forFlexiDirectRU50

Hardware requirements
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradio
SystemModuleFSMF.

2.5.1.3

Functional description
WiththeRAN2179:DualBandHSDPA42MbpsfeaturedataforcapableUEis
scheduledontwodistinctfrequencybandsinthedownlink.Withthisfeature,the
maximumpeakrateis42Mbpswhen64QAMisenabledand15codesareavailableon
bothfrequencies.

Issue:01ADRAFT

DN09146788

53

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

TheBTSusesproportionalfairschedulingandoptimizesthesectorcoverageand
capacitybyfavoringthelow-frequencybandforcell-edge-UEsandthehigh-frequency
bandforUEs,thatareclosertotheBTS.ThisallowsDualBandHSDPAtocombinethe
gainofnormalDualCellHSDPAschedulingandthebenefitsoflowfrequencybandfor
farawayusers.
ThecarrierselectionisbasedbothontheUEdistanceandcurrentloadonbothuplink
carriers.TheRNCusestheRAN2172:Multi-BandLoadBalancingfeatureforcarrier
selection.
Figure2

TwoHSDPAcarrierslocatedintwodifferentfrequencybands.

Table37:Supportedbandcombinationsshowsthreebandcombinationssupportedby
theRAN2179:DualBandHSDPA42Mbpsfeature.
Table37

Supportedbandcombinations

Dual Band HSDPA


Configuration

54

UL Band

DL Band

IorVIII

IandVIII

IIorIV

IIandIV

IorV

IandV

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

g
2.5.1.4

Radioresourcemanagementfeatures

MixedRFmoduleconfigurations,Rel1+Rel2orRel1+Rel3,cannotbeused
withthisfeature.

System impact
Interdependencies between features

TheRAN1906:DualCellHSDPAfeatureandallitspreconditionsareprerequisites
forthisfeature.
Useof64QAMmodulationrequirestheRAN1643:HSDPA64QAMfeature.
LicensesfortwoseparatefrequencybandsinthesameNodeBandRNCare
required.

Impact on interfaces
RNCandBTSNBAPinterfaceincludingnewIE'sinmessages:
(BTS->RNC)AuditResponse:BTSinformsRNConDualBand-HSDPAcapability
(BTS->RNC)ResourceStatusIndication:BTSinformsRNCwhichcellwillsupport
DualBand-HSDPA.
FollowingNBAPproceduresareunchangedbetweenDC-HSDPAandDB-HSDPA:

RadioLinkSetup
RadioLinkReconfiguration

ChangedNBAPproceduresbetweenDC-HSDPAandDB-HSDPA:AuditResponseand
ResourceStatusIndication.TheseproceduresareenhancedwithnewIEindicatingthat
NodeBhasnewDB-capability

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


TheRAN2179:DualBandHSDPA42Mbpsfeaturecandoublemaximumachievable
peakuserthroughput.Italsoincreasescellcapacity(byupto40%)andcelledge
throughput.

2.5.1.5

RAN2179: Dual-Band HSDPA 42Mbps management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Table38:Existingalarmslistsalarmsrelatedtothisfeature.

Issue:01ADRAFT

DN09146788

55

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

Table38

Existingalarms

Alarm ID

Alarm name

3325

INCONSISTENCYINCONFIGURATIONPARAMETERS

7795

INCONSISTENCYINHIGHPEAKRATEHSPACONFIG

Measurements and counters


Table39:Newcounterslistscountersintroducedwiththisfeature.
Table39

Newcounters

Counter ID

Counter name

Measurement

M1001C728

UESUPPORTFORDB-HSDPABAND
REL9-1

ServiceLevel

M1001C729

UESUPPORTFORDB-HSDPABAND
REL9-2

ServiceLevel

M1001C730

UESUPPORTFORDB-HSDPABAND
REL9-3

ServiceLevel

M1006C293

RBSETUPATTEMPTFORDB-HSDPA

RRCsignalling

M1006C294

SUCCESSFULRBSETUPFORDBHSDPA

RRCsignalling

M1006C295

RBSETUPFAILFORDB-HSDPADUETO
NOREPLY

RRCsignalling

M1006C296

RBSETUPFAILFORDB-HSDPADUETO
UENACK

RRCsignalling

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table40:Newparameterslistsparametersintroducedwiththisfeature.
Table40

56

Newparameters

Full name

Abbreviated name

Managed object

DualBandHSDPAEnabled

DBandHSDPAEnabled

WCEL

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table40

Radioresourcemanagementfeatures

Newparameters(Cont.)

Full name

Abbreviated name

Managed object

PreferredFrequencyLayerforDB-DCHSDPANRT

PFLDBHSDNRT

PFL

PreferredLayerforDB-DC-HSDPANRT PrefLayerDBHSDNRT

PFL

PreferredFrequencyLayerforDB-DCHSDPAStreaming

PFLDBHSDStr

PFL

PreferredLayerforDB-DC-HSDPA
Streaming

PrefLayerDBHSDStr

PFL

PreferredFrequencyLayerforDB-DCHSDPAAMR

PFLDBHSDAMR

PFL

PreferredLayerforDB-DC-HSDPAAMR PrefLayerDBHSDAMR

PFL

PreferredFrequencyLayerforDB-DCHSDPAAMRandNRT

PFL

PFLDBHSDAMRNRT

PreferredLayerforDB-DC-HSDPAAMR PrefLayerDBHSDAMRNRT
andNRT

PFL

Table41:Modifiedparameterslistsparametersmodifiedbythisfeature.
Table41

2.5.1.6

Full name

Abbreviated name

Managed object

DCHSDPAEnabled

DCellHSDPAenabled

WCEL

DualCellversusMIMOpreference

DCellVsMIMOPreference

RNC

Frametimingoffsetofacell

Tcell

WCEL

Sales information
Table42

Issue:01ADRAFT

Modifiedparameters

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCLK

DN09146788

57

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

2.5.2 Activating RAN2179: Dual Band HSDPA 42 Mbps


Purpose
Followthisproceduretoactivatethisfeature.
Before you start
ArestartoftheRNCandtheBTSisnotrequiredaftertheactivationofthisfeature.
Thisprocedurerequirescelllocking.
Makesureyouhaveaccesstothefollowingapplications:

OMSElementManager
ApplicationLauncher
Man-machineinterface(MMI)

Makesurethat:

RAN1906:Dual-CellHSDPA42MbpsfeatureisactivatedintheRNC.
DualCellHSDPAmustbeactivatedtothosecellsthataregoingtobeusedforDual
BandHSDPA.
UsedcellsmustbeconfiguredtothosebandsthataresupportedforDualBand
HSDPA.
Usedfrequencies(intwobands)mustbehandedwiththesameHSDPAscheduler
(similartoDualCellHSDPAusesfrequenciesinonebandthatmustbehandledwith
thesamescheduler).

FortheallowedbandcombinationsforDualBandHSDPA,seeTable43:Allowedband
combinationsforDualCellandDualBandHSDPA.
Table43

AllowedbandcombinationsforDualCellandDualBandHSDPA

Dual Band - Dual Cell


HSDPA Configuration

Uplink band

Downlink
band

IorVIII

IandVIII

IIorIV

IIandIV

IorV

IandV

TheRAN2179:DualBandHSDPA42Mbpsfeatureiscontrolledbythecapacitylicense
key.Formoreinformationonlicensing,seeLicensing.

Thefeaturecodeforthisfeatureis2118.
TosetthethefeaturestatetoON,usethefollowingcommand:

58

forIPA-RNC:
ZW7M:FEA=2118:ON;
NolicenseisrequiredinFlexiDirectRNC.

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Open the OMS Element Manager.

Go to the Topology.

Expand the ROOT.

Expand the RNC object.

Expand the WBTS object.

Lock the WCEL where the RAN2179: Dual Band HSDPA 42 Mbps feature needs
to be activated:
a) Select the WCEL object.
b) Select the cell in the WCell(s) table.
c) From the drop-down menu select "State Change State: Lock".

Configure the WCEL object:


a) Select Edit parameters from the WCEL object.
b) Set the DBandHSDPAEnabled parameter to Enabled.

Unlock the WCEL.

Repeat the steps 6-8 for all the required cells.

2.5.3 Verifying RAN2179: Dual Band HSDPA 42 Mbps


Purpose
FollowtheprocedurebelowtoverifythattheactivationoftheRAN2179:DualBand
HSDPA42Mbpsfeaturehasbeensuccessful.

Issue:01ADRAFT

DN09146788

59

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

Perform the RRC connection setup with UE that supports Dual Band HSDPA
and send some data.

Open the RNW measurement management application from Application


Launcher.

Use the RNW measurement management application to start measurements


M1006 Traffic with 15 minute interval.
AlternativelythemeasurementcanbestartedusingNetActAdministrationof
MeasurementsApplication.
Waituntilthemeasurementintervalstarts.

After the measurement data has been collected, use the RNW Measurement
presentation GUI to check if any of the following counters has value greater
than 0.

M1006C293-RBSETUPATTEMPTFORDB-HSDPA
M1006C294-SUCCESSFULRBSETUPFORDB-HSDPA
M1006C295-RBSETUPFAILFORDB-HSDPADUETONOREPLY
M1006C296-RBSETUPFAILFORDB-HSDPADUETOUENACK
M1001C728-UESUPPORTFORDB-HSDPABANDREL9-1
M1001C729-UESUPPORTFORDB-HSDPABANDREL9-2
M1001C730-UESUPPORTFORDB-HSDPABANDREL9-3

Expected outcome
ValuesofcountersM1006C293andM1006C294areupdatedbyanormalDBcallsetup,
andvalueofcounterM1006C295orM1006C296isupdatedbyrelatedfailureRBsetup
scenarios.Theapproximatethroughputis42Mbit/s.TheRAN2179:DualBandHSDPA
42Mbpsfeaturehasbeenactivatedsuccessfully.

2.5.4 Deactivating RAN2179: Dual Band HSDPA 42 Mbps


Purpose
Followthisproceduretoactivatethisfeature.

60

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Open the OMS Element Manager.

Go to the Topology.

Expand the ROOT.

Expand the RNC object.

Expand the WBTS object.

Lock the WCEL where the RAN2179: Dual Band HSDPA 42 Mbps feature needs
to be activated:
a) Select the WCEL object
b) Select the cell in the WCell(s) table.
c) From the drop-down menu select "Start Change state: Lock".

Configure the WCEL object:


a) Select Edit parameters from the WCEL object.
b) Set the DBandHSDPAEnabled parameter to Disabled

Unlock the WCEL.

Repeat the steps 6-8 for all the required cells.

Further information

ArestartoftheRNCandtheBTSisnotrequiredafterthedeactivationofthis
feature.

2.6 RAN2250: Enhanced HSUPA IC


2.6.1 Description of RAN2250: Enhanced HSUPA IC
Introduction to the feature
TheRAN2250:EnhancedHSUPAICprovidesanimprovedalgorithm,whichcancelsan
interferencefrom2msTTIusersfromother2msTTIusers.Thefeatureistheextension
oftheRAN1308:HSUPAInterferenceCancellationReceiverfeature.TheRAN2250:
EnhancedHSUPAICfeatureprovidesthesupportforcancelinganinterferencecaused
byandhappeningtothe16QAMULusers.

Issue:01ADRAFT

DN09146788

61

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

Formoreinformationon16QAMfeature,see:RAN1645:HSUPA16QAMfeature
description.

2.6.1.1

Benefits
End-user benefits
Thisfeatureprovidestheuserwiththefollowingbenefits::

removingtheinterferencesappearingduringadirectdatatransfer
providingtheservicewithhigherqualitythanwithoutthefeature

Operator benefits
ThisfeaturebenefitstheoperatorbyincreasingtheULdatarateswhenseveral2msTTI
usersarepresentinthesamecell.

2.6.1.2

Requirements
Software requirements
Table44:SoftwareRequirementsliststhesoftwarerequiredforthisfeature.
Table44
RAS

SoftwareRequirements
Flexi Direct IPA-RNC

RU50EP1 Notplanned RN8.1


Flexi Lite
BTS
Not
planned

Flexi 10
BTS
WN9.1

mcRNC
mcRNC4.1

NetAct

MSC

NetAct8
EP2

Supportnot
required

Flexi Direct RNC OMS


Notplanned
SGSN
Supportnot
required

Flexi BTS

OMS3.1 WN9.1
MGW
Supportnot
required

UE
Supportnot
required

Hardware requirements
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/E,orFlexiMultiradio
SystemModuleFSMF.

2.6.1.3

Functional description
Thealgorithmwhichisintroducedwiththisfeatureispresentedonthepicturebelow,and
describedinthefollowingparagraph.

62

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Figure3

Radioresourcemanagementfeatures

TheEnhancedInterferenceCancellationprocedure
Originalstreampower(cell-specific)
Prx_total,orig = Prx_total
non-PIC

r(k)

DEM

Symbolsof
usersinset
non-PIC

Usersinset
PIC

PIC

(0)

(1)

r(k)

r(k)

DEM

REM

RSR

DEM

Secondstage
detected
symbolsof
usersinset
PIC

Firststage
detected
symbolsof
usersinset

Commonresidualstreampower
(cell-specific)
Prx_total,res,common

PIC

Individualresidualstream
powerafterinterference
cancellationandresidual
streamconstruction
(UE/service-specific
Prx_total,res,k

Where:

DEM-thedemodulationstage
REM-theremodulationstage
RSR-theResidualSignalReconstructionstage

Thecell-specificsignalismarkedwithther(k)andthepowerofthisstreamismarked
withthePrx_total,original.
Inthefirstphasepartoftheprocessthealgorithmgeneratesthecommonresidual
signal,bysubtractingthedemodulatedandre-modulatedsignalsofall2msTTIE-DCH
users)fromtheoriginalstream.Onthepicture,thecreatedsignalisnamedas
Prx_total,res,common.
Inthesecondphase,foreach2msTTIE-DCHusers,theindividualsignalforuser
kPrx_total,res,k(wherethekistheindicateduser)iscreated.Thisisachievedbyadding
theowndetectedsignaltothecommonresidualsignalPrx_total,res,common.
Thefollowingpicture(Figure4:Theresidualsignalstreamrelationship)presentsthe
basicACconsiderationwithandwithouttheRAN2250:EnhancedHSUPAICfeature.
ThepowerlevelsonthecommonresidualsignalstreamandtheUE-specificresidual
streamsignificantlydifferwhatshowsthebenefitsofusingtheRAN2250:Enhanced
HSUPAICfeature.

Issue:01ADRAFT

DN09146788

63

Radioresourcemanagementfeatures

Figure4

RU50FeatureDescriptionsandInstructions

Theresidualsignalstreamrelationship
Originalstream

Commonresidual
stream

ExampleUE-specific
residualstreamafter
residualstream
reconstruction

Prx_total =
Prx_total,orig

UE-specificRXpowerfrom
residualstreamreconstruction

Pres,k
Prx_total,res,common

PEDCH,orig =
L EDCH,rx,IC /(1=)...
.Prx_total,res,common

otherHSUPA
(2ms TTIonly)

(1-)
k Pres,k
otherHSUPA
(2ms TTIonly)

PDCH =

DCH

DCH

noise+other
interference

noise+other
interference

PDCH,res

RSR
PEDCH,res,IC =LEDCH,res,IC *
.Prx_total,res,common

PEDCH,res =LDCH *
.Prx_total,res,common

Pres,k

Prx_total,res,common

otherHSUPA
(2ms TTIonly)

PEDCH,res,IC =
.LEDCH,res,IC *...
.Prx_total,res,common

DCH

PEDCH,res
=L
*
DCH
.Prx_total,res,common

noise+other
interference

Interferencereductionfactor(IRF), Totalinterferencereduction: TIR=Prx_total /Prx_total,res,common

2.6.1.4

System impact
Interdependencies between features
Thisfeaturerequiresthefollowingfeatureupandrunning:

RAN1308:HSUPAinterferencecancellationreceiver

Impact on interfaces
ThisfeatureimpactsNBAPinterfaceasfollows:

NBAPCAPABILITYINFORMATION

thePIClevelparameterisenhanced.
Thenewvalue:enhanced-2ms-PICisaddedtothePIClevelfortheRAN2250:
EnhancedHSUPAICfeature.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeatureisbeneficialinnetworkswhere2msTTIisinwideuse.Inthesecases
highercellthroughputanduserdataratescanbeachieved.

2.6.1.5

RAN2250: Enhanced HSUPA IC management data


Alarms
Therearenoalarmsrelatedtothisfeature.

64

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table45:ModifiedParameterslistsparametersmodifiedbythisfeature.
Table45

ModifiedParameters

Full name

Abbreviated name

Management object

PICstate

PICState

WCEL

FilteringCoefficientofPrxTotal
measurement

PrxMeasFilterCoeff

WCEL

Loadmeasurementthresholds

LoadMeasThresholds

RNC

CellassignedtoPICpool

AssignedPICPool

WCEL

Maxtargetreceivedwideband PrxMaxOrigTargetBTS
originalpowerforBTS

2.6.1.6

WCEL

Sales information
Table46

SalesInformation
BSW/ASW

ASW

License control in network


element
RAN

License control in network


element
BTSLK

2.7 RAN2482: Enhanced Virtual Antenna Mapping


2.7.1 Description of RAN2482: Enhanced Virtual Antenna
Mapping
Introduction to the feature
WiththeVirtualAntennaMappingtheWCDMAorHSDPAdownlinksignals,eithernonMIMOorMIMO,areallsentfromtwophysicalantennasusingavirtualantennamapping
matrixbetweenthevirtualantennasandphysicalantennas.TheRAN2482:Enhanced
VirtualAntennaMappingfeaturetunesthephasedifferencebetweenthetwophysical
antennastoobtainthebestsignalqualityforHSDPA.

2.7.1.1

Benefits
End-user benefits
Theenduserbenefitsfromanenhancedapplicationexperiencebecauseofhigher
HSDPADLthroughput.

Issue:01ADRAFT

DN09146788

65

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

Operator benefits
TheoperatorbenefitsfromhigheraverageDLthroughputforHSDPAusers,andthus
higheraveragecellthroughput.

2.7.1.2

Requirements
Software requirements
Table47:Softwarerequirementslistssoftwarerequiredforthisfeature.
Table47

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi Direct OMS


RNC

Flexi BTS

RU50

Notplanned RN8.0

mcRNC4.1

Notplanned OMS3.01)

WN9.0

OMS3.12)

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

WL9.1

WN9.1

NetAct8
EP11)

Supportnot Supportnot Supportnot


required
required
required

NetAct8
EP22)

SGSN

MGW

UE

Support
not
required

1)forRU50
2)forRU50EP1

Hardware requirements
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradio
SystemModuleFSMForFlexiLiteBTSWCDMA.
ThisfeaturealsorequiresdoubleTxanddoubleantennalinespersector.Forsupported
BTSconfigurations,seeFlexiMultiradioBTSWCDMASupportedandPlanned
ConfigurationsExcelinNOLS.

2.7.1.3

Functional description
VirtualAntennaMapping(VAM)wasintroducedwiththefeatureRAN1642:MIMOandit
canbeusedincellswithtwoTxlikeinphysicalMIMOconfiguration.WiththeVAMthe
cellareaiscoveredwithtwophysicalantennasusingvirtualantennamappingbetween
physicalandvirtualantennas.ThemappingcanbeusedforMIMOandnon-MIMO
configurations.However,VAMsolutionprovidesmoreefficientMIMOperformanceby
transmittingtonon-MIMOUEswithouttransmitdiversitybutbyVirtualAntennaMapping

66

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

forpowerbalancing.VAMisbeneficialforaddingpoweroftwopoweramplifiersinstead
ofoneandintroducingpolarizationdiversitywhenthecross-polarizedbasestation
antennasareused.
TheRAN2482:EnhancedVirtualAntennaMapping(E-VAM)featureimprovesthe
performanceofVAMbycontrollingthephasedifferencebetweenthephysicalantennas.
TheRAN2482:EnhancedVirtualAntennaMappingfeaturetunesthephasedifference
betweenthetwophysicalantennastoobtainthebestsignalqualityforHSDPA.The
channelqualityindicatorsofactivenon-MIMOUEsinthecellareusedtoobtainthebest
phasedifferencebetweenthetwophysicalantennas.Tuningofthephaseoffsetis
dynamicandautomatic.ThebestbenefitsareobtainedforUEswithoneRx.
TheE-VAMcanbeactivatedonlyincellswithtwoTx.Cellrestartisrequiredwhenever
theRAN2482:EnhancedVirtualAntennaMappingfeatureisactivatedordeactivated.

2.7.1.4

System impact
Interdependencies between features
Thereisnointerdependencieswithotherfeatures.
VirtualAntennaMapping(VAM)hastobeconfiguredinthecellspriortoE-VAM
activation.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on MML commands


TherearenoMMLcommandsrelatedtothisfeature.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


ThefeatureincreasestheDLcellthroughput.

2.7.1.5

RAN2482: Enhanced Virtual Antenna Mapping management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Therearenomeasurementsandcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Issue:01ADRAFT

DN09146788

67

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

Parameters
Table48:Newparameterslistsparametersintroducedwiththisfeature.
Table48

2.7.1.6

Newparameters

Full name

Abbreviated name

Managed object

EVAMinuse

EVAMInUse

WCEL

Sweeptime

EvamTSweep

WCEL

Keeptime

EvamTKeep

WCEL

Phaseoffsetamount

EvamNumPhaseOffset

WCEL

InitialPhaseOffset

EvamDInit

WCEL

EVAMCapability

EVAMCapability

WCEL

Sales information
Table49

Salesinformation

BSW/ASW

RAS SW component

License control in network


element

ASW

RAN

RNCLK

2.7.2 Activating RAN2482: Enhanced Virtual Antenna Mapping


Purpose
FollowthisproceduretoactivateRAN2482:EnhancedVirtualAntennaMappingfeature.

Configuring Virtual Antenna Mapping


Before you start
BeforeactivatingtheRAN2482:EnhancedVirtualAntennaMappingfeature,Virtual
AntennaMapping(VAM)needstobeconfiguredfirst.TheVAMisconfiguredviaBTS
SiteManageronlyinMIMO-capableBTSs.AfterVAMconfiguration,BTSrestartis
required.
AlthoughVAMwasintroducedwiththeRAN1642:MIMOfeature,itdoesnotrequirea
licensetobeconfigured.
MakesureyouhaveaccesstotheBTSSiteManager.

68

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Start the WCDMA BTS Site Manager application and establish the connection
to the BTS.
FlexiMultiradioBTSWCDMAisabletoautonomouslyrequestformissinglicense
file(s)fromtheNetActLicenseManagerduringtheRAN2131:AutomaticLicence
DistributiontoFlexiBTSfeatureactivation.
MakesurethatyouhaveselectedAutomaticlicensinginusecheckboxinthe
AutomaticLicenseDistributionSettingspage.

IftheRAN2131:AutomaticLicenceDistributiontoFlexiBTSfeatureisnot
activated,therelevantlicensemustbeuploadedmanually.

Upload the configuration plan file from the BTS.


WhenBTSSMisconnectedtotheBTS,itautomaticallyuploadsthecurrent
configurationplanfilefromtheBTS.

SelectViewCommissioningorclickCommissioningontheViewbar.

Configure Virtual Antenna Mapping in a cell.


a) InCommissioning,gotoLocalCellResourcespageandassigntwoTxoutputs
forasinglecelltomakeMIMOsettingssectionappear.
b) InMIMOsettingssection,selecttheVirtualantennamappinginusecheckbox
andchooseMIMOtypefromthedrop-downlist.

Pleasenote,thatfollowingthisstepallowstoconfigureVAMonlyinone
specificcell.ToconfigureVAMinmultiplecells,runthissteponeachcell
separately.

Send the commissioning plan file to the BTS.


ClickSend Parametersbutton.
Youmaysavetheparametersatthispoint.

The new commissioning plan file is automatically activated in the BTS.


BTSSMautomaticallysendsanactivationcommandafterfinishingthefiledownload.

Select Next to complete the commissioning.


Youcansavethecommissioningreport,ifrequired.

Backup commissioning files (if applicable).


SelectFile Backup commissioning files
Savethecompletebackupcommissioningfileforfurtheruse.

Expected outcome
VAMisconfiguredinchosencells.RestarttheBTStomakechangesvalid.

Issue:01ADRAFT

DN09146788

69

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

Activating Enhanced Virtual Antenna Mapping


Before you start
TheRAN2482:EnhancedVirtualAntennaMappingfeatureactivatingproceduredoes
notcausedowntimeandthefeaturecanbeactivatedatanytimeoftheday.
Makesureyouhaveaccesstothefollowingapplications:

OMSElementManager
ApplicationLauncher
Man-machineinterface(MMI)

TheRAN2482:EnhancedVirtualAntennaMappingfeatureiscontrolledbythelong-term
capacityEnhancedVirtualAntennamappinglicensekey.Capacitylicensereferstothe
numberofcells.Formoreinformationonlicensing,seeLicensing.

Numberofactivatedcellsmustnotexceedthecapacityofthe
EnhancedVirtualAntennamappinglicense.

Thefeaturecodeforthisfeatureis3732.
TosetthefeaturestatetoON,usethefollowingcommand:

forIPA-RNC:
ZW7M:FEA=3732:ON;

NotethatinFlexiDirectRNCthereisnoneedtoconfigurethelicense.

Open the OMS Element Manager.

Go to the Topology.

Expand the ROOT.

Go to the WCEL object by following the path:


RNC objectWBTSs folderWBTS objectWCELs folderWCEL object

Configure the WCEL object:


a) Lock the WCEL object.
b) Right-click on the WCEL object and select Edit parameters.
c) Set the EVAM in use (EVAMInUse) parameter to Enabled.
ThechangeoftheparametertoEnabledconsumesthelicenseintermsof
numberofcells.

70

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

d) Unlock the WCEL object.


Expected outcome
TheRAN2482:EnhancedVirtualAntennaMappingfeaturehasbeenactivatedinthe
RNC.Afteractivatingthefeature,thereisnoneedtoresettheRNCortheBTS.

2.7.3 Verifying RAN2482: Enhanced Virtual Antenna Mapping


Purpose
InacellwhichhasMIMOhardwarecapability,E-VAMprovideshigheraverageDL
throughputfornon-MIMOusersandthushigheraveragecellthroughput.When
comparedtoVAM,theenhancedVAMisexpectedtoincreasestationaryone-RxUEs
averagethroughputbyatleast10%.

2.7.4 Deactivating RAN2482: Enhanced Virtual Antenna Mapping


Purpose
Followthisproceduretodeactivatethisfeature.

Open the OMS Element Manager.

Go to the Topology.

Expand the ROOT.

Go to the WCEL object following the path:


RNC objectWBTSs folderWBTS objectWCELs folderWCEL object

Configure the WCEL object:


a) Lock the WCEL object.
b) Right-click on the WCEL object and select Edit parameters.
c) Set the EVAM in use (EVAMInUse) parameter to Disabled.
ThechangeoftheparametertoDisabledfreesthelicenseintermsofnumberof
cells.
d) Unlock the WCEL object.

Further information

Issue:01ADRAFT

ArestartoftheRNCandtheBTSisnotrequiredafterthedeactivationofthe
feature.

DN09146788

71

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

2.8 RAN1668: HSUPA Compressed Mode for LTE and


Inter-frequency Handover
2.8.1 Description of RAN1668: HSUPA Compressed Mode for
LTE and Inter-frequency Handover
Introduction to the feature
TheRAN1668:HSUPACompressedModeforLTEandInter-frequencyHandover
featureintroducescompressedmodemeasurementswithHSPAactivewithoutUL
channeltypeswitchingtoDCH.Thefeaturealsointroducesbasiccompressedmode
supportforperformingmeasurementsrelatedtointer-systemhandovertoLTE.
Withoutthisfeature,duringinter-frequencyhandoverinHSPA,beforecompressedmode
isstarted,switchingtheULtransportchannelfromHSUPAtoDCHisneeded.Aswitch
backtoHSPAisperformed,afterinter-frequencyhandoverusingULDCH.

2.8.1.1

Benefits
End-user benefits
Theend-userbenefitsfromfastHSPAinter-frequencyhandoverandhigherdata
throughputduringcompressedmode.

Operator benefits
Thisfeaturebenefitstheoperatorasfollows:

2.8.1.2

HSPAinter-frequencyhandover(HO)isdonefasterwhenchanneltypeswitchingto
DCHisnotneededfirst
Theinter-systemhandover(ISHO)andredirectionfromHSPAtoLTEbecomesmore
reliablewhenLTEcellsaremeasuredbeforeISHOorredirection.
ThisfeaturereducessignalingforRNC,Iub,BTS,andtheUEaschanneltype
switchingtoDCHisnotneeded.

Requirements
Software requirements
Table50:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
Table50

72

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi
OMS
Direct RNC

RU50

FlexiDirect
RU50

mcRNC4.1

ADA6.0

RN8.0

DN09146788

Flexi BTS

Supportnot WN9.0
required

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

SGSN

MGW

UE

WL9.1

WN9.1

NetAct8
EP11)

Supportnot Supportnot Supportnot 3GPPRelrequired


required
required
6

NetAct8
EP22)

1)forRU50
2)forRU50EP1andFlexiDirectRU50

Hardware requirements
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradio
SystemModuleFSMForFlexiLiteBTSWCDMA.

2.8.1.3

Functional description
TheRAN1668:HSUPACompressedModeforLTEandInter-frequencyHandover
featureintroducesHSUPAcompressedmode(CM)forLTEandinter-frequency
measurements,withoutULchanneltypeswitchingtoDCH.
HSUPACMconfigurationforinter-frequencymeasurementsisachievedusingasingleframemethodwith7(orless)-slottransmissiongappattern(TGP).HSUPACM
configurationforLTEmeasurementsisachievedusingadouble-framemethodwith7(or
more)-slotTGP.InNSNimplementationtheTGPforsingleframemethodisalwaysfixed
to7slotsandfordoubleframemethod,theTGPisfixedto10slots.
CompressedmodeissupportedwhiletheradiobearersaremappedtoE-DCHinuplink
andSRBsaremappedonDCHorE-DCH.ThisalsoincludesthecasewhereDLSRBis
mappedtoDCHorHSDPA.
Avoidingthechannel-typeswitchtoULDCHreducesthetotalhandoverexecutiontime
upto1.5s.Also,thehighHSUPAthroughputcanbeexperiencedduringcompressed
mode.
Forinter-systemhandovertoLTE,onlythebasicHSUPAcompressedmodesupportis
coveredinthisfeature.HSUPAcompressedmodeforLTEisusedbytheRAN2980:
MeasurementbasedLTELayeringfeatureandtheRAN2264:SmartLTEHandover
feature.Allthecontrol,signaling,andRRMdecisionmakingofmeasurement-based
redirectionandPSHOtoLTEareincludedinthosefeatures.

g
g

Issue:01ADRAFT

InNSNimplementationHSUPACMisneverenabledindependently.Itisalways
doneintandemwithHSDPACM,thatisCMisalwaysenabledinboth
directionstogether
NotethatHSUPAcompressedmodeisnotsupportedoverIur.

DN09146788

73

Radioresourcemanagementfeatures

2.8.1.4

RU50FeatureDescriptionsandInstructions

System impact
Interdependencies between features
TheRAN1276:HSDPAInter-frequencyHandoverfeatureisaprerequisiteforusingthis
feature.
TheRAN1276:Inter-frequencyHandoverfeaturecoversthefollowingdirecthandover
cases:

DCH/HSDPAtoDCH/HSDPA
DCH/HSDPAtoHSUPA/HSDPA
DCH/HSDPAtoDCH/DCH
DCH/DCHtoDCH/HSDPA
DCH/DCHtoHSUPA/HSDPA

WiththeRAN1668:HSUPACompressedModeForLTEandInter-frequencyHandover
featurethefollowingdirecthandovercasesaresupportedinaddition:

HSUPA/HSDPAtoDCH/HSDPA
HSUPA/HSDPAtoHSUPA/HSDPA
HSUPA/HSDPAtoDCH/DCH

Impact on interfaces
HSUPACMisconfiguredandactivatedusingthefollowingmessages:

overIub:

NBAP:RadioLinkSetupRequestprocedure
NBAP:RadioLinkRe-configurationProcedure(Synchronized)

overUu:

RRC:TransportChannelRe-configuration
RRC:PhysicalChannelRe-configuration
RRC:MeasurementControl(Setup)

HSUPACMisdeactivatedusingthefollowingmessages:

overIub:

overUu:

74

NBAP:CompressedModeCommand
NBAP:RadioLinkRe-configurationProcedure(Synchronizedonly)

RRC:TransportChannelRe-configuration
RRC:PhysicalChannelRe-configuration
RRC:MeasurementControl(Release)

NotethatonlymessagessupportedbyNSNarelisted.

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeatureimpactssystemperformanceasfollows:

HSPAIFHOisdonefaster,aschanneltypeswitchingtoDCHisnotneededfirst.
ISHOandredirectionfromHSPAtoLTEbecomesmorereliable,astheLTEcellscan
bemeasuredbeforeISHOorredirection.
TheULthroughputisimpactedsinceUEcannottransmitoneachslot.Thereduction
dependsontheconfiguredtransmissiontimeintervalandwhethertheUEis
performingintra-orinter-systemmeasurement.

Thisfeatureimpactssystemcapacityasfollows:

2.8.1.5

SignalingforRNC,Iub,BTS,andUEisreduced,aschanneltypeswitchingtoDCH
isnotneededforenablingCM.
InFSM3,amaximum50%oftheuserswithCMactivecanbesupported,thatis,a
maximum50%oftheuserscanhaveCMactiveatthesametime.

RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency


Handover management data
Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Table51:Newcounterslistscountersintroducedwiththisfeature.
Table51

Issue:01ADRAFT

Newcounters

Counter ID

Counter name

Measurement

M1002C676

ALLOCATIONFORHSUPAIFHO
COMPRESSEDMODE

Traffic(RNC)

M1002C677

ALLOCATIONDURATIONFORHSUPA
IFHOCOMPRESSEDMODE

Traffic(RNC)

M1002C678

REJECTEDHSUPAIFHOCOMPRESSED
MODE

Traffic(RNC)

M1002C692

ALLOFORCOMMODELTE

Traffic(RNC)

M1002C693

ALLODURAFORCOMMODELTE

Traffic(RNC)

DN09146788

75

Radioresourcemanagementfeatures

Table51

RU50FeatureDescriptionsandInstructions

Newcounters(Cont.)

Counter ID

Counter name

Measurement

M1006C312

HSUPAIFHOCOMPRESSEDMODEFAIL
DUETOUE

RRCsignalling

M1006C313

LTECOMPRESSEDMODEFAILDUETO
UE

RRCsignalling

M1008C294

HSUPAIFHOATTEMPTS

IntraSystemHardHandover
(RNC)

M1008C295

SUCCESSFULHSUPAIFHO

IntraSystemHardHandover
(RNC)

Table52:Relatedexistingcounterslistsexistingcountersrelatedtothisfeature.
Table52

Relatedexistingcounters

Counter ID

Counter name

Measurement

M1002C623

ALLOCATIONFORHSDPAIFHO
COMPRESSEDMODE

Traffic(RNC)

M1002C624

ALLOCATIONDURATIONFORHSDPA
IFHOCOMPRESSEDMODE

Traffic(RNC)

M1002C625

REJECTEDHSDPAIFHOCOMPRESSED
MODE

Traffic(RNC)

Key performance indicators


Table53:Newkeyperformanceindicatorslistskeyperformanceindicatorsintroduced
withthisfeature.
Table53

Newkeyperformanceindicators

KPI ID

KPI name

RNC_5301a

HSUPACompressedModeallocationsuccessrate

Therearenomodifiedandexistingkeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table54:Newparameterslistsparametersintroducedwiththisfeature.

76

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table54

Radioresourcemanagementfeatures

Newparameters

Full name

Abbreviated name

Managed object

TGPLforHSPAInterFrequency
Measurement

TGPLHSPAInterFreq

RNHSPA

Table55:Modifiedparameterslistsparametersmodifiedbythisfeature.
Table55

Modifiedparameters

Full name

Abbreviated name

Managed
object

BTSSupportForHSPACM

BTSSupportForHSPACM

WBTS

MaxnumberofUEsinHSDPACMdue
tocriticalHO

MaxNumberUEHSPACmHO

WCEL

MaxnumberofUEsinHSDPACMdue
toNCHO

MaxNumberUEHSPACmNCHO

WCEL

Table56:Relatedexistingparameterslistsexistingparametersrelatedtothisfeature.
Table56

Relatedexistingparameters

Full name

Issue:01ADRAFT

Abbreviated name

Managed
object

ServingHS-DSCHcellchangeandSHO HSDPAMobility
on/offswitch

RNFC

Gappositionsingleframe

GAPPositionSingleFrame

RNC

Gappositionsingleframe

GAPPositionSingleFrame

RNMOBI

RecoveryPeriodPowerinUL
CompressedMode

UplinkRecoveryPeriodPowerMode

RNAC

Initialtransmitpowerinuplink
compressedmode

UplinkInitialTransmitPowerMode

RNC

ULDeltaSIR1incompressedmode

DeltaSIRUplink

RNC

ULDeltaSIR1incompressedmode

DeltaSIRUplink

WRAB

DLDeltaSIR1incompressedmode

DeltaSIRDownlink

RNC

DLDeltaSIR1incompressedmode

DeltaSIRDownlink

WRAB

DN09146788

77

Radioresourcemanagementfeatures

Table56

2.8.1.6

RU50FeatureDescriptionsandInstructions

Relatedexistingparameters(Cont.)

Full name

Abbreviated name

Managed
object

ULDeltaSIRafter1incompressed
mode

DeltaSIRAfterUplink

RNC

ULDeltaSIRafter1incompressed
mode

DeltaSIRAfterUplink

WRAB

DLDeltaSIRafter1incompressed
mode

DeltaSIRAfterDownlink

RNC

DLDeltaSIRafter1incompressed
mode

DeltaSIRAfterDownlink

WRAB

CompressedMode:Alternative
scramblingcode

AltScramblingCodeCM

WCEL

Compressedmodemasterswitch

CmMasterSwitch

RNFC

Sales information
Table57

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

HSPA

RNCLK

2.8.2 Activating RAN1668: HSUPA Compressed Mode for LTE


and Inter-frequency Handover
Purpose
Followthisproceduretoactivatethisfeature.
Formoreinformationonthefeature,seetheDescriptionofRAN1668:HSUPA
CompressedModeforLTEandInter-frequencyHandoverinWCDMARAN,rel.RU50,
featuredescriptions.
Before you start
RestartoftheRNCisnotrequiredaftertheactivationofthisfeature.
Thisproceduredoesnotcausedowntime,andcanbeactivatedatanytimeoftheday.
Makesureyouhaveaccesstothefollowingapplications:

78

OMSElementManager
ApplicationLauncher
Man-machineinterface(MMI)

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Beforeactivatingthisfeature,activatetheRAN1276:HSDPAInter-frequencyHandover
feature(seeActivatingRAN1276:HSDPAInter-frequencyHandover).
BeforeactivatingthisfeaturemakesurethatbasicHSUPAandHSDPAmobilityare
enabled.
Thisfeatureiscontrolledbythelong-termON/OFFlicensekey.Formoreinformationon
licensing,seeLicensing.

Thefeaturecodeforthisfeatureis4783.
TosetthefeaturestatetoON,usethefollowingcommand:

Issue:01ADRAFT

forIPA-RNC:
ZW7M:FEA=4783:ON;

DN09146788

79

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

Open the OMS Element Manager.

Go to the Topology.

Expand the ROOT.

Expand the RNC object.

Expand the RNHSPAs folder.

Configure the RNHSPA object:


a) Select Edit Parameters from the RNHSPA object.
b) In Packet Scheduler tab set the TGPLHSPAInterFreq parameter to 5 if this
feature is used for inter-frequency handovers or/and set the value of the
TGPLForLTEMeas parameter to 6 if this feature is used for LTE handover or
layering. Set the TGPLAMRHSDPAInterFreq parameter and the
TGPLHSDPAInterFreq parameter to default value 4.
c) Navigate back to the RNC object.

Expand the WBTSs folder.

Configure the WBTS object:


a) Select Edit Parameters from the WBTS object.
b) In Packet Scheduler tab set the value of the BTSSupportForHSPACM
parameter to "HSPA CM supported".
c) Navigate back to the RNC object.

Expand the RNFCs folder.

10 Enable compressed mode by configuring the RNFC object:


a) Select Edit Parameters from the RNFC object.
b) In Packet Scheduler tab set the CmMasterSwitch parameter to "Used".
c) Navigate back to the RNC object.

11 Go to the WCEL object by the following path:


RNC objectWBTSs folderWBTS objectWCELs folderWCEL object

80

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

12 Configure the WCEL object.


a) Select Edit Parameters from the WCEL object.
b) In Packet Scheduler tab, set value greater than 0 for the parameter
MaxNumberUEHSPACmHO .
c) In Packet Scheduler tab, set value greater than 0 for the parameter
MaxNumberUEHSPACmNCHO.

2.8.3 Verifying RAN1668: HSUPA Compressed Mode for LTE and


Inter-frequency Handover
Purpose
Followthisproceduretoverifythatthisfeatureworksproperlyinthenetwork.
Before you start
1. MakesurethattheRAN1668:HSUPACompressedModeforLTEandInterfrequencyHandoverfeatureisactivatedintheRNC(seeActivatingRAN1668:
HSUPACompressedModeforLTEandInter-frequencyHandover).
2. SetBTS1CELL2asinter-frequencyadjacentcellofBTS1CELL1.
3. SetthevalueofFMCI-IFHOcauseCPICHEcNoparameterto1('Enabled')in
FMCI_IDassignedtoBTS1CELL1(HsdpaFmciIdentifieror
NrtFmciIdentifierparameter).
4. SetthevalueofFMCS-HHoEcNoTimeHysteresisparameterto6(100ms)in
FMCS_IDassignedtoBTS1CELL1(HspaFmcsIdentifier,
HsdpaFmcsIdentifier,orNrtFmcsIdentifierparameter).
5. SetWCELparameter MaxNumberUECmHOtovaluegreaterthanorequaltothe
valueofWCEL-MaxNumberUEHSPACmHOparameterinBTS1CELL1(fortheaccess
path,seestep11andstep12inActivatingRAN1668:HSUPACompressedModefor
LTEandInter-frequencyHandover).

Issue:01ADRAFT

DN09146788

81

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

Make an NRT interactive call with the UE (Rel-6/Rel-7/Rel-8/Rel-9), RAB on


HSPA in BTS 1 CELL 1 and send data.

Adjust the signal of BTS 1 CELL 1, so that it is lower than the threshold value
of the HHoEcNoThreshold parameter.

Adjust the signal of BTS 1 CELL 2, so that it is stronger than the signal of BTS
1 CELL 1.

Release the call.

Collect the log for "step 1", "step 2", "step 3", and "step 4" and analyze the log.

Verify that:

TheUEsendsoutRRC:MEASUREMENTREPORTwithMeasuredResultsfor
intra-frequencyevent1f.
InNBAPmessageRADIOLINKRECONFIGURATIONPREPAREthevaluesof
IEsinTransmissionGapPatternSequenceInformationareasfollows:
TGPSIdentifierxx
tGSNxx
tGL17
tGDxx
tGPL15
uL/DLmodeUL/DL
DownlinkCompressedModeMethodsf/2
UplinkCompressedModeMethodsf/2
DownlinkFrameTypexx
DeltaSIR1xx
DeltaSIRafter1xx

xxmeansthatthevalueoftheIEisnotrelevantforverifyingthis
feature.

InRRCmessagePHYSICALCHANNELRECONFIGURATIONthevaluesofIEs
areasfollows:
tgp-SequenceList{{
tgpsixx,
tgps-Statusactivate:{
tgcfnxx},
tgps-ConfigurationParams{
tgmpfdd-Measurement,
tgprcxx,
tgsnxx,
tgl17,
tgdxx,
tgpl15,
rppxx,
itpxx,

82

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

ul-DL-Modeul-and-dl:{
ulsf-2,
dlsf-2},
dl-FrameTypedl-FrameTypeA,
deltaSIR1xx,
deltaSIRAfter1xx}}}

xxmeansthatthevalueoftheIEisnotrelevantforverifyingthis
feature.

CountersM1002C676ALLO_CM_HSUPA_IFHOandM1002C623
ALLO_CM_HSDPA_IFHOareupdated:1isaddedtotheirvalue.

Expected outcome
HSUPAcompressedmodestartssuccessfullyandcallreleaseisnormal.Logsdataare
asspecifiedaboveandcountersareupdated.

2.8.4 Deactivating RAN1668HSUPA Compressed Mode for LTE


and Inter-frequency Handover
Purpose
Followthisproceduretodeactivatethisfeature.

Open the OMS Element Manager.

Go to the Topology.

Expand the ROOT.

Expand the RNC object.

Expand the WBTSs folder.

Configure the WBTS object:


a) Select Edit Parameters from the WBTS object.
b) In Packet Scheduler tab set the value of the BTSSupportForHSPACM
parameter to "Only DCH CM supported" or "HSDPA CM supported".

Further information
Afterdeactivatingthefeature,setthefeaturestatetoOFF.

Issue:01ADRAFT

DN09146788

83

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

2.9 RAN2980: Measurement Based LTE Layering


2.9.1 Description of RAN2980: Measurement Based LTE
Layering
Introduction to the feature
Inthecurrentsystemimplementation,theRAN2717:SmartLTELayeringfeature
supportsredirectionfromWCDMAtoLTE.Thisredirectionisperformedblindly,thatis
withoutpriormeasurementsofLTElayer.Itisagoodalternativewhen,forexample,
WCDMAandLTEcellsareco-locatedandhavelargelyoverlappingcoverageareas.
However,UEscouldfaceproblemincellreselectionwhichcancauseunsatisfyingenduserexperience.
TheRAN2980:MeasurementBasedLTELayeringfeaturesupportstheredirectionofUE
toLTElayeronlyifmeasurementresultsindicatethatLTE-capableUEcouldcampon
LTEcellsuccessfully.ThisensuresseamlessLTEcampingeveniftheWCDMAcellhas
onlypartialLTEcoverage.BothFDD-LTEandTDD-LTEaresupported.

2.9.1.1

Benefits
End-user benefits
EnsuringasuccessfulLTEcampingimprovesend-userexperience.

Operator benefits
OperatorbenefitsfromhavingtwotypesofWCDMAtoLTEredirectionsavailable:with
andwithoutameasurement.Operatorcanchooseifthetriggeractivateswith-orwithoutmeasurement-basedredirection.

2.9.1.2

Requirements
Software requirements
Table58:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
Table58

Softwarerequirements

RAS

Flexi Direct

IPA-RNC

mcRNC

Flexi Direct
RNC

OMS

Flexi BTS

RU50

FlexiDirect
RU50

RN8.0

mcRNC4.1

ADA6.0

OMS3.01)

WN9.0

OMS3.12)
IHO6.03)

84

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

SGSN

MGW

WL9.1

WN9.1

NetAct8
EP11)

Supportnot Supportnot Supportnot


required
required
required

UE

3GPP
Rel-8

NetAct8
EP22)3)

1)forRU50
2)forRU50EP1
3)forFlexiDirectRU50

Hardware requirements
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradio
SystemModuleFSMForFlexiLiteBTSWCDMA.

2.9.1.3

Functional description
Functional overview
RRCconnectionreleasewithredirectioncommandtoLTEcanbeusedformovingLTEcapableUEtoLTE,ifcompressedmodemeasurementsindicatethatLTEcoverageis
available.Eachofthefollowingeventstriggerscompressedmodemeasurementsfor
LTE:

RCCstatechangefromCell_DCHtoCell_FACH,Cell_PCH,orURA_PCH
channeltypechangefromHSDPA/HSPAtoDCH/DCHCTS
CScallreleasewhenUEhasCSandPSconnectionactive
periodictriggerwithoperator-definabletimer:
WhenLTE-capableUEenterstheCell_DCHstatehavingonlyPSRAB(s),itstimer
(controlledwithLTEPeriodicTriggerTimerparameter)isset.Attheexpiryof
timer,measurementsforredirectiontoLTEarestartedandtimerissetagain.If
measurementresultsleadtodecisiontoredirectUEtoLTEsystem,UEisthen
redirected.IfthemeasurementresultsdonottriggerUEsredirectiontoLTEandUE
stillcontinuesdataactivity,thenattheexpiryofthetimerthenewtimerissetand
measurementsarestartedagain.

FirstthreeoftheabovementionedtriggersarealsousedintheRAN2717:SmartLTE
Layeringfeature.TheRAN2980:MeasurementBasedLTELayeringfeatureintroduces
thefourthtriggerforUEskeepinglongCell_DCHreservationsforPSservices.Notethat
whentheRAN2980:MeasurementBasedLTELayeringfeatureisactive,allfourtriggers
arevalidandthereisnoneedtohavetheRAN2717:SmartLTELayeringfeature
installedseparately.
Inuplink,DCHisusedduringcompressedmode.HSPAcompressedmode,also
includingHSUPAcompressedmode,issupportedbytheRAN1668:HSUPA
CompressedModeforLTEandInter-frequencyHandoverfeature.IftheRAN1668:
HSUPACompressedModeforLTEandInter-frequencyHandoverfeatureisnot

Issue:01ADRAFT

DN09146788

85

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

implementedinthenetwork,theRAN2980:MeasurementBasedLTELayeringfeature
supportsHSDPA/DCH,andDCH/DCH.IfthereisHSUPA(E-DCH)inuplink,thenitis
reconfiguredtoDCH,beforeinitiatingthecompressedmodemeasurements.
LTE-capableUEsarecheckedfortheirmeasurementcapabilities.UEswithdualreceiver
donotrequirecompressedmodeforcreatinggapstolistentootherfrequencies.For
suchUEs,compressed-mode-relatedinformationisnotrequiredandthusnotsentto
them.
IfWCDMAcellloadisnothighanduserscanbeprovidedgoodenoughexperience
withinWCDMAlayer,measurementsandredirectiontoLTEcanbebypassed.RNCload
levelparametercanbeusedtodefineifloadislowenoughforkeepingUEsinWCDMA.
WiththeRAN2980:MeasurementBasedLTELayeringfeatureoperatorcan:

2.9.1.4

enableLTEredirectionwithoutmeasurementsforthefirstthreeredirectiontriggers
(alsoprovidedwiththeRAN2717:SmartLTELayeringfeature)andmeasurementbasedredirectiontoLTEfortheperiodictrigger
establishmeasurement-basedredirectiontoLTEforallfourredirectiontriggers
selectthefrequenciestowhichUEsinCell_DCHstateareredirectedinLTEsystem
aswellasdefinecampingprioritiesforthosefrequencies
excludesomeLTEcarrierfrequenciesfromLTEtargetcampinglayers
disabletheWCDMAcellloadcheckwhichwillresultinautomaticLTEredirection
everytimetheLTEcoverageisavailable

System impact
Interdependencies between features
TheRAN2067:LTEInterworkingfeatureprovidessupportforLTEcellreselectioninidle
modeCell_PCHandURA_PCHstates.

Impact on interfaces
ThisfeatureaffectsUuandIubinterfacesandusesstandardsignalingprocedures.

Impact on commands
Therearenocommandsrelatedtothisfeature.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

2.9.1.5

RAN2980: Measurement Based LTE Layering management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

86

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Table59:Newcounterslistscountersintroducedwiththisfeature.
Table59

Newcounters

Counter ID

Counter name

Measurement

M1001C747

RRCSETUPATTCSFB

ServiceLevel

M1001C748

RCSETUPACCESSFAILCSFB

ServiceLevel

M1001C749

RRCACCESSRELEASECSFB

ServiceLevel

M1001C750

RRCSETUPATTREPEATCSFB

ServiceLevel

M1006C310

RRCCONNRELEASELTEREDIRINDCH

RRCsignaling

M1010C237

LTECARRIERNOTFOUNDFORREDIRECTION

InterSystemHard
Handover

M1010C238

LTEREDIRECTIONSTARTEDAFTER
MEASUREMENT

InterSystemHard
Handover

M1010C239

DURATIONOFLTECARRIERMEASUREMENT

InterSystemHard
Handover

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table60:Newparameterslistsparametersintroducedwiththisfeature.
Table60

Newparameters

Full name

Abbreviated name

Managed
object

FMCLIdentifier

FMCLId

RNC
FMCL

Issue:01ADRAFT

ChangeoriginforFMCLobject

FMCLChangeOrigin

FMCL

LTEMeasurementAveragingWindow

LTEMeasAveWindow

FMCL

LTEMaximumMeasurementPeriod

LTEMaxMeasPeriod

FMCL

DN09146788

87

Radioresourcemanagementfeatures

Table60

RU50FeatureDescriptionsandInstructions

Newparameters(Cont.)

Full name

Abbreviated name

Managed
object

LTEMinimumMeasurementInterval

LTEMinMeasInterval

FMCL

LTENeighborCarrierFrequencySearch LTENcarrFreqSearchPeriod
Period

FMCL

MeasurementBasedLTELayeringand
HandoverActivation

LTELayeringMeasAndHOActivatio
n

WCEL

LTEPeriodictriggertimer

LTEPeriodicTriggerTimer

RNC

AdjacentLTESelectedFrequency
(EARFCN)

AdjLSelectFreq

ADJL

WCDMACellLoadThreshold

WCDMACellLoadThreshold

WCEL

FMCLIdentifier

FMCLIdentifier

WCEL

AdjacentLTEFrequencyPriority

AdjLFreqPriority

HOPL

LTECarrierfrequencyselection
MinimumRxPowerlevel

AdjLMinRSRPLevel

HOPL

LTECarrierfrequencyselection
MinimumRxquallevel

AdjLMinRSRQLevel

HOPL

TransmissionGapLengthforLTE
Carrierfrequencymeasurements

TGPLForLTEMeas

RNHSPA

Table61:Modifiedparameterslistsparametersmodifiedbythisfeature.
Table61

88

Modifiedparameters

Full name

Abbreviated name

Managed
object

RNCOptions

RncOptions

RNC

SmartLTELayeringEnabled

SmartLTELayeringEnabled

WCEL

SmartLTELayeringRSCPthreshold

SmartLTELayeringRSCP

WCEL

SmartLTELayeringNRTuseramount
threshold

SmartLTELayeringUA

WCEL

SmartLTELayeringservicecontrol

SmartLTELayeringServ

RNMOBI

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table61

2.9.1.6

Radioresourcemanagementfeatures

Modifiedparameters(Cont.)

Full name

Abbreviated name

Managed
object

TimerforSmartLTELayeringPreventio

SmartLTELayeringPrevT

RNMOBI

SmartLTELayeringTargetSystem
Selection

SmartLTELayeringTSysSel

WCEL

Sales information
Table62

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCLK

2.9.2 Activating RAN2980: Measurement Based LTE Layering


Purpose
FollowthisproceduretoactivatetheRAN2980:MeasurementBasedLTELayering
feature.
Before you start
AfteractivatingthisfeaturethereisnoneedtorestartneithertheRNC,northeBTS.
Activatingproceduredoesnotcausedowntimeandthefeaturecanbeactivatedatany
timeoftheday.
ActivatethelicenseoftheRAN2067:LTEInterworkingfeatureusingLTEInterworking
licensekey.Formoreinformation,seeActivatingRAN2067:LTEInterworking.
ActivatethelicenseoftheRAN2980:MeasurementBasedLTELayeringfeatureusing
MeasurementBasedLTELayeringlicensekey.
TosetthefeaturestatetoON,usethefollowingcommand:

forIPA-RNC:
ZW7M:FEA=4839:ON;

Formoreinformationonmanaginglicenses,seeLicensing.
BeforeactivatingtheRAN2980:MeasurementBasedLTELayeringfeature,theLTE
neighborsmustbeconfiguredaccordingtotheRAN2067:LTEInterworkingfeature.
HSDPAcompressedmodemeasurementsforLTErequiressettingthe
BTSSupportForHSPACMWBTSparametervalueto1.IfHSDPACMisnotactivated,
thentheHS-DSCHtoDCHchannelswitchingisneededbeforestartingtheLTE
measurements.NotethatiftheRAN1276:HSDPAInter-frequencyHandoverfeature
licenseisON,HSDPACompressedModemeasurementsforIFHOtotheBTSin
questionisactivated,providedtheBTSSupportForHSPACMparametervalueissetto1.

Issue:01ADRAFT

DN09146788

89

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

TheHSUPAcompressedmodemeasurementsupportforLTEisprovidedwiththe
RAN1668:HSUPACompressedModeforLTEandInter-frequencyHandoverfeature.If
thatfeatureisnotactivated,thentheE-DCHtouplinkDCHchannelswitchingisneeded
beforestartingtheLTEmeasurements.TheHSPA(HSUPA/HSDPA)compressedmode
measurementsforLTErequiresthatthelicenseofRAN1668:HSUPACompressedMode
forLTEandInter-frequencyHandoverfeatureisONandthevalueofthe
BTSSupportForHSPACMparameterissetto2.
ConfigurethefollowingdatabaseobjectsandrelevantparametersfortheRAN2980:
MeasurementBasedLTELayeringfeatureandattachthemtotheWCDMAcell:

FMCLparametersforcontrollinginter-RAT(LTE)measurement:

HOPLparametersforcontrollinginter-RAT(LTE)neighborfrequency:

AdjLEARFCN
AdjLMeasBw

WCELparametersforidentifyingtheMeasurementControlParameterSetand
controllingredirectiontriggers:

AdjLFreqPriority
AdjLMinRSRPLevel
AdjLMinRSRQLevel

ADJLparametersfordefininginter-RAT(LTE)neighborfrequency:

LTEMeasAveWindow
LTEMaxMeasPeriod
LTEMinMeasInterval
LTENcarrFreqSearchPeriod

FMCLIdentifier
LTELayeringMeasActivation

Notethatthelistedparametersareoptionalandhaveadefaultvalue.Onlythe
AdjLEARFCNADJLparameter,fordefiningtheE-UTRAAbsoluteRadio
FrequencyChannelNumberoftheneighboringE-UTRAfrequency,is
mandatory.
RedirectiontoLTEhappensonlywhenthecellhasatleastoneCell_DCH
adjacencydefinedwiththeAdjLSelectFreqRNC/WBTS/WCEL/ADJL
parameter.Operatorcanexcludechosenfrequencyfromredirectiontarget
usingtheAdjLSelectFreqparameter.InordertouseredirectiontoLTE,
value0fortheAdjLSelectFreqparametermustbeusedforatleastoneLTE
frequencyconfiguredinthecell.
EnsurethatRSRPandRSRQthresholdsinbothLTEandWCDMAnetworks
arealigned.Correspondingparametersrelatedtothisfeatureare
AdjLMinRSRPLevelandAdjLMinRSRQLevel.
Additionally,thefollowingparameterscanbeusedfortuningtheRAN2980:
MeasurementBasedLTELayeringfeature:

90

LTEPeriodicTriggerTimerRNCparameter
SmartLTELayeringServRNMOBIparameter
LTETargetFreqCriterionRNMOBIparameter

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

LTELayerCellHSLoadWCELparameter
SmartLTELayeringUAWCELparameter
SmartLTELayeringTSysSelWCELparameter
SmartLTELayeringRSCPWCELparameter

ItiscrucialtoensurethecorrectnessofAdjLEARFCNandAdjLMeasBw
neighboringLTEparameterswhileconfiguring,becauseRNCO&Misnotable
toverifythevaluesoftheseparameters.

Open the OMS Element Manager.

Go to Topology and expand the ROOT directory.

Expand the RNC object and then the WBTS object.

Configure the WCEL object:


a) Right-click on the WCEL object and select Edit parameters.
b) In Handover Control tab, set the value of the SmartLTELayeringEnabled
parameter to Enabled.

In Handover Control tab, set the value LTELayeringMeasActivation


parameter to:

0forsettingT1,T2,T3astriggersforredirectionwithoutmeasurementsandT4
asatriggerforredirectionwithmeasurements
1forsettingT1,T2,T3,T4astriggersforredirectionwithmeasurements

Further information
SmartLTELayeringEnabledWCELparameterenablestriggers(T)fortheRAN2980:
MeasurementBasedLTELayeringfeatureasfollows:

value(0)=T1,T2,T3,andT4disabled
value(1)=T1enabled
value(2)=T1andT2enabled
value(3)=T1andT3enabled
value(4)=T1,T2,andT3enabled
value(5)=T1andT4enabled
value(6)=T1,T2,andT4enabled
value(7)=T1,T3,andT4enabled
value(8)=T1,T2,T3,andT4enabled

wherethetriggersare:

Issue:01ADRAFT

T1:RRCstatechangeCell_DCHtoCCH
T2:HSDPA/HSPAtoDCH/DCHCTS
T3:CSRABrelease

DN09146788

91

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

T4:periodictrigger

Formoreinformationontriggers,seeDescriptionofRAN2980:MeasurementBasedLTE
Layering.
TheRAN2980:MeasurementBasedLTELayeringfeatureissupportedforthefollowing
PSQoSclasses:

interactive(NRT)
background(NRT)
streaming(RT)

2.9.3 Verifying RAN2980: Measurement Based LTE Layering


Purpose
FollowthesetipstoverifythattheRAN2980:MeasurementBasedLTELayeringfeature
worksproperlyinthenetwork.
RedirectiontoLTE,providedwiththeRAN2980:MeasurementBasedLTELayering
feature,isdoneaftersuccessfulLTEmeasurementsandsendingtheUEtheRRC
CONNECTIONRELEASEmessagebytheRNC.Feature'sperformancecanbeverified
withthefollowingcounters:

M1006C310RRCCONNRELEASELTEREDIRINDCH
whichisupdatedwhentheRNCsendsRRCconnectionreleasemessagetotheUE,
becauseofLTEredirectionstartedbyperiodictrigger
M1010C238LTEREDIRECTIONSTARTEDAFTERMEASUREMENT
whichisupdatedwhentheLTEcarriermeasurementperformedbytheUEfindsa
carrierfrequencywiththequalityacceptabletoperformredirectionandtheRNC
initiatestheredirectionprocedure

Notethatforverificationusingcounters,theend-userhastomakeaPScall.
Expected outcome
RedirectiontoLTEissuccessfulandvisibleinthelistedcounters.
Unexpected outcome
RedirectiontoLTEisnotsuccessfulandisvisibleinthefollowingcounter:

M1010C237LTECARRIERNOTFOUNDFORREDIRECTION
whichisupdatedwhentheLTEcarrierfrequencymeasurementperformedbytheUE
doesnotresultinacarrierfrequencywiththequalityacceptabletoperform
redirection

Further information

Thefollowingcountercanbeusedformoredetailedmonitoringthe
RAN2980:MeasurementBasedLTELayeringfeature:

M1010C239DURATIONOFLTECARRIERMEASUREMENT

CountersrelatedtoCSFallback:

92

M1001C747RRCSETUPATTCSFB

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

M1001C748RRCSETUPACCESSFAILCSFB
M1001C749RRCACCESSRELEASECSFB
M1001C750RRCSETUPATTREPEATCSFB

2.9.4 Deactivating RAN2980: Measurement Based LTE Layering


FollowthisproceduretodeactivatetheRAN2980:MeasurementBasedLTELayering
feature.

Open the OMS Element Manager.

Go to Topology and expand the ROOT directory.

Expand the RNC object and then the WBTS object.

Configure the WCEL object:


a) Right-click on the WCEL object and select Edit parameters.
b) In Handover Control tab, set the value of the SmartLTELayeringEnabled
parameter to Disabled.

2.10 RAN147: RRC Connection Setup Redirection


2.10.1 Description of RAN147: RRC Connection Setup
Redirection
Introduction to the feature
IncasetheRRCconnectionisrejectedduetotheadmissioncontrolreasons,theRNC
sendstheUEto2Gor3G,toanewfrequencyforthenexttry.IfRRCconnectionis
rejectedduetothesignalingunitoverloadreason,theRNCsendsUEto2G.

2.10.1.1

Benefits
End-user benefits
Bettersubscriberexperiencebecauseoflesscallsetupdelay.

Operator benefits
Thisfeaturehelpstoreducecallsetupdelayincaseofcongestion.

2.10.1.2

Requirements
Software requirements
Table63:Softwarerequirementsliststhesoftwarerequiredforthisfeature.

Issue:01ADRAFT

DN09146788

93

Radioresourcemanagementfeatures

Table63

RU50FeatureDescriptionsandInstructions

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

OMS

BTS Flexi

Flexi Lite

RU50

Notplanned RN8.0

mcRNC4.1

OMS3.01)

Supportnot
required

Support
not
required

OMS3.12)

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

Supportnot
required

NetAct8EP1

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

1)

NetAct8EP2
2)

1)forRU50
2)forRU50EP1

Hardware requirements
Thisfeaturedoesnotrequireanyneworadditionalhardware.

2.10.1.3

Functional description
Functional overview
TheRAN147:RRCConnectionSetupRedirectionfeatureenablestoredirectanRRC
connectiontoanother3GfrequencyorGSM.Theredirectionhappensifadmission
controlrejectstheRRCconnectionrequest.TheFigure5:RRCconnectionsetup
redirectionillustratesthedescribedsituation.

94

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Figure5

Radioresourcemanagementfeatures

RRCconnectionsetupredirection

TheredirectioninfosentintheRRCmessageRRCCONNECTIONREJECTdependson
thetargetsystem.IfthetargetsystemisGSM,thentheredirectioninfoisalistoftarget
cellsfortheUEwithreleaserel-6ornewer.IftheUEreleaseisolderthanrel-6,thenthe
redirectioninfoisjustthetargetsystem,forexample,GSM.
Ifthetargetsystemis3G,thentheredirectioninfoisatargetfrequency(UTRAAbsolute
RadioFrequencyChannelNumber).Theinter-frequencyneighborcellAdjiUARFCN
parameterdefinesitfordownlink.TheRNCcalculatesitforuplinkinlegacywayfrom
valueoftheAdjiARFCNparameterandduplexdistanceusedintheRFband.
RRCconnectionsetsuponCell_DCHstate,whentheredirectionistriggered.RRC
connectioncanbesetupalsooncommonchannels.Formoreinformation,seeRAN1797
Commonchannelsetup.
ThereisnoAdmissioncontrolincommonchannelsthusitcannotfail,whenRRC
connectionissetuponcommonchannels.
RRMdecidesaboutthetargetsystemonthebasisofestablishmentcauseoftheRRC
ConnectionRequestandthenewmanagementRRCReDirTargetSysparameter.The
RRCReDirTargetSysparameterdefinesthetargetsystemforeachestablishment
cause.Also,iftheRNCtriestoredirecttheRRCconnectionintoGSMbutUEisnotable
tocamptothenewtargetcellinGSM,thentheRNCisallowedtoredirecttheRRC
connectioninto3G.Valueforeachparameterneedtobeplannedbasedonfunctionality
ofactualestablishmentcauseandavailableradioaccesstechnologies.Especiallyneed
tobeconsideredifthiscertainfunctionalitycanbeperformedonGSM.
TheRRCReDirBlockedCellAllowedparameterdefinesifcells,whicharemarkedas
blockedinSLHOorMBLBprocedure,shouldnotbeusedasatargetcellofanRRC
connectionredirection.IfMBLBloadinformationisnotavailable,thenonlySLHO
information(loadedornotloaded)isused.IfbothMBLBandSLHOloadinformationis
notavailable,thenSLHOandMBLBblockedcellsarenotreducedfromthetargetcell
list,althoughtheRRCReDirBlockedCellAllowedparameterindicatesthatthe
blockedcellsshouldnotbeusedasatargetcellofanRRCconnectionredirection.

Issue:01ADRAFT

DN09146788

95

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

TheAdjiPriorityReDirparameterdefinespriorityforeachinter-frequencycellinthe
neighborcelllistifcongestionofIubtransmissionorBTScausestherejection.
TheAdjiPriorityQualityparameterdefinespriorityforcellsintheneighborcelllist
iftheRRCconnectionisrejectedbecauseofdownlinkpower,uplinkinterferenceor
downlinkspreadingcodecongestion.Thefrequencyoffeasibletargetcellwiththe
highestpriorityisselectedasthetargetfrequencyforredirection.
Formoreinformation,seetheFigure6:Selectionprocessofredirectioninformation.
Figure6

Selectionprocessofredirectioninformation

IftheRNCsignalingunitoverloadisthereasontorejecttheRRCConnectionRequest,
UEcanberedirectedtoGSMnetworkwithouttargetcelllist.

2.10.1.4

System impact
Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on commands
Therearenocommandsrelatedtothisfeature.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

96

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

2.10.1.5

Radioresourcemanagementfeatures

RAN147: RRC Connection Setup Redirection management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Table64:Newcounterslistscountersintroducedwiththisfeature.
Table64

Newcounters

Counter ID

Counter name

Measurement

M1006C305

RRC_CONN_REDIR_GSM_FAIL

1006-RRCsignalling(RNC)

Table65:Relatedexistingcounterslistsexistingcountersrelatedtothisfeature.
Table65

Relatedexistingcounters

Counter ID

Counter name

Measurement

M1006C70

RRC_CONN_REJ_DIR_SETUP

1006-RRCsignalling(RNC)

M1001C618

RRCCONNSETUPFAILDUETOICSU
OVERLOAD

1001-RRCsignaling(RNC)

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table66:Newparameterslistsparametersintroducedwiththisfeature.
Table66

Issue:01ADRAFT

Newparameters

Full name

Abbreviated name

Managed object

EnablingRRCconnectionRedirection

RRCReDirEnabled

RNFC

RRCConnectionRedirectionTarget
System

RRCReDirTargetSys

WCEL

RCCConnectionRedirectionTarget
Systemforconversationalcauses

TargetsystemConversationalC
all

WCEL

DN09146788

97

Radioresourcemanagementfeatures

Table66

98

RU50FeatureDescriptionsandInstructions

Newparameters(Cont.)

Full name

Abbreviated name

Managed object

RRCConnectionRedirectionTarget
Systemforstreamingcauses

TargetsystemStreamingCall

WCEL

RCCConnectionRedirectionTarget
Systemforinteractivecauses

TargetsystemInteractiveCall

WCEL

RCCConnectionRedirectionTarget
Systemforbackgroundcauses

TargetsystemBackgroundCall

WCEL

RCCConnectionRedirectionTarget
Systemforsubscribedtrafficcauses

TargetsystemSubscribedTraffi
c

WCEL

RCCConnectionRedirectionTarget
Systemforemergencycallcauses

TargetsystemEmergencyCall

WCEL

RCCConnectionRedirectionTarget
Systemforinter-RATre-selection
causes

TargetsysteminterRATreselecti WCEL
on

RCCConnectionRedirectionTarget
Systemforinter-RATcellchangeorder
causes

TargetsysteminterRATchangeo WCEL
rder

RCCConnectionRedirectionTarget
Systemforregistrationcauses

Targetsystemregistration

WCEL

RCCConnectionRedirectionTarget
Systemfordetachcauses

TargetsystemDetach

WCEL

RCCConnectionRedirectionTarget
Systemforhighprioritysignalling
causes

TargetsystemHighPrioritySign
alling

WCEL

RCCConnectionRedirectionTarget
Systemforlowprioritysignallingcauses

TargetsystemLowPrioritySigna WCEL
lling

RCCConnectionRedirectionTarget
Systemforcallre-establishmentcauses

Targetsystemreestablishment

WCEL

RCCConnectionRedirectionTarget
Systemforunknowncauses

Targetsystemunknown

WCEL

RCCConnectionRedirectionTarget
SystemforMBMSreceptioncauses

TargetsystemMBMSreception

WCEL

RCCConnectionRedirectionTarget
SystemforMBMSptpRBrequest
causes

TargetsystemMBMSrbrequest

WCEL

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table66

Radioresourcemanagementfeatures

Newparameters(Cont.)

Full name

Abbreviated name

Managed object

RRCConnectionRedirectionallows
blockedcells

RRCReDirBlockedCellAllowed RNMOBI

NeighbourcellpriorityforRRC
ConnectionRedirection

AdjiPriorityReDir

HOPI

Table67:Modifiedparameterslistsparametersmodifiedbythisfeature.
Table67

2.10.1.6

Modifiedparameters

Full name

Abbreviated name

Managed object

NcellPriorityforQualityIFHO

AdjiPriorityQuality

HOPI

NcellPriorityforCoverageHO

AdjgPriorityCoverage

HOPG

RNCOptions

RncOptions

IADA

Sales information
Table68

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCLK

2.10.2 Activating RAN147: RRC Connection Setup Redirection


2.10.2.1

Activating RAN147: RRC Connection Setup Redirection due to


admission control reasons
Purpose
Followthisproceduretoactivatethisfeature.
Formoreinformationonthefeature,seetheRAN147:RRCConnectionSetup
RedirectionFeatureDescription.
Before you start
RestartoftheRNCisnotrequiredafteractivationofthisfeature.
Thisproceduredoesnotrequirecelllocking.
Thisproceduredoesnotcausedowntimeanditcanbeactivatedatanytimeoftheday.
Makesureyouhaveaccesstothefollowingapplications:

Issue:01ADRAFT

DN09146788

99

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

OMSElementManager
ApplicationLauncher

Thisfeatureiscontrolledbyalicense.Forinformationonmanaginglicenses,see
Licensing.
TosetthefeaturestatetoON,usethefollowingcommand:

forIPA-RNC:
ZW7M: FEA=4780:ON;

Open the OMS Element Manager.

Go to the Topology Tree View.


Select:Network ManagementTopology Tree View

Expand the RNFC object.

Configure the RNFC object.


a) Fromthedrop-downmenuselectEditEdit Parameters.
b) SettheRRCReDirEnabledparametervaluetoEnabled(AC1or3).
c) Thevalueofthetargetsystemforredirection(bothprimaryandsecondary)
shouldbedefined,anditsvaluedependsonthevalueoftheEstablishment
CausereceivedinthemessageRRC:RRCCONNECTIONREQUEST.
TheRRCReDirTargetSys(underWCELobjects)parametervalueprimary
targetsystemsecondarytargetsystem:

0none,
1GSM3G,
23GGSM,
3GSMnone,
43Gnone.

Save the changes.


a) ClicktheApplybutton.
b) IftheUEshouldberedirectedtoUMTS,thenADJI'sshouldtobecreated.Ifthe
redirectionshouldbedonetoGSM,thenADJG'sshouldbecreatedforWCEL.

2.10.2.2

Activating RAN147: RRC Connection Setup Redirection due to


signaling unit overload
Purpose
Followthisproceduretoactivatethisfeature.
Formoreinformationonthefeature,seetheRAN147:RRCConnectionSetup
RedirectionFeatureDescription.

100

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Before you start


RestartoftheRNCisnotrequiredafteractivationofthisfeature.
Thisproceduredoesnotrequirecelllocking.
Thisproceduredoesnotcausedowntimeanditcanbeactivatedatanytimeoftheday.
Makesureyouhaveaccesstothefollowingapplications:

OMSElementManager
ApplicationLauncher

Thisfeatureiscontrolledbyalicense.Forinformationonmanaginglicenses,see
Licensing.
TosetthefeaturestatetoON,usethefollowingcommand:

forIPA-RNC:
ZW7M: FEA=4780:ON;

Open the OMS Element Manager.

Go to the Topology Tree View.


Select:Network ManagementTopology Tree View

Expand the RNFC object.

Configure the RNFC object.


a) Fromthedrop-downmenuselectEditEdit Parameters.
b) SettheRRCReDirEnabledparametervaluetoEnabled(AC2or3).
c) Thevalueofthetargetsystemforredirection(bothprimaryandsecondary)
shouldbedefined,anditsvaluedependsonthevalueoftheEstablishment
CausereceivedinthemessageRRC:RRCCONNECTIONREQUEST.
TheRRCReDirTargetSys(underWCELobjects)parametervalueprimary
targetsystemsecondarytargetsystem:

0none,
1GSM3G,
23GGSM,
3GSMnone,
43Gnone.

Save the changes.


a) ClicktheApplybutton.
b) IftheUEshouldberedirectedtoUMTS,thenADJI'sshouldtobecreated.Ifthe
redirectionshouldbedonetoGSM,thenADJG'sshouldbecreatedforWCEL.

Issue:01ADRAFT

DN09146788

101

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

2.10.3 Verifying RAN147: RRC Connection Setup Redirection


2.10.3.1

Verifying RAN147: RRC Connection Setup Redirection due to


admission control reasons
Purpose
Followthisproceduretoactivatethisfeature.
Before you start
Makesureyouhaveaccesstothefollowingapplication:

RNWMeasurementManagement

UE1 sends RRC Connection Request with cause


"originatingInteractiveCall" to WBTS1 CELL-1. RRC Connection of UE1
is rejected due to DL Power.
Verify,ifRNCsendsRRC:RRCConnectionRejecttoUEwithredirectioninfo
specifyingfrequencyInfo.SincePrimaryTargetSystem(selectedonthebaseof
HOPI-AdjiPriorityQuality),definedforRRCReDirTargetSysTargetsystemInteractiveCallis3G.ThespecifiedtargetfrequencyofWBTS1
CELL-3hasthehighestprioritydefinedbyHOPI2- AdjiPriorityQuality.

RRC connection setup successfully on WBTS1 CELL-3 with cause


"originatingInteractiveCall" for UE1.

Counters verification.
Thecountersareupdatedasfollows:
Table69

2.10.3.2

Countersverification

ID

Name

Value

Updated objects

M1006C70

RRCCONN
REJECTDUETO
RRC
CONNECTION
SETUP
REDIRECTION

WBTS1CELL-1

Verifying RAN147: RRC Connection Setup Redirection due to


signaling unit overload reasons
Purpose
Followthisproceduretoactivatethisfeature.
Before you start
Makesureyouhaveaccesstothefollowingapplication:

102

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

RNWMeasurementManagement

Make sure that there is very heavy CPU load in signaling unit (ICSU or USCP).

UE1 sends RRC Connection Request.


Verify,iftheRNCsendsRRC: RRC Connection Reject to UE with
redirection info / Inter-RAT info = GSM.

Counters verification.
Thecountersareupdatedasfollows:
Table70

Countersverification

ID

Name

Value

Updated objects

M1001C618

RRCCONN
SETUPFAILDUE
TOICSU
OVERLOAD

WBTS1CELL-1

M1006C70

RRCCONN
REJECTDUETO
RRC
CONNECTION
SETUP
REDIRECTION

WBTS1CELL-1

2.10.4 Deactivating RAN147: RRC Connection Setup Redirection


2.10.4.1

Deactivating RAN147: RRC Connection Setup Redirection due to


admission control reasons
Purpose
Followthisproceduretodeactivatethisfeature.
Before you start
Makesureyouhaveaccesstothefollowingapplications:

ApplicationLauncher

Open the OMS Element Manager.

Go to the Topology Tree View.


Select:Network ManagementTopology Tree View

Issue:01ADRAFT

DN09146788

103

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

Expand the RNFC object.

Configure the RNFC object.


a) Fromthedrop-downmenuselectEditEdit Parameters.
b) SettheRRCReDirEnabledparametervaluetoDisabled(0or2).

Save the changes.


a) ClicktheApplybutton.

Open the MMI session.


OpentheSecureMMIWindowapplicationfromtheApplicationLauncher.
Alternatively,anyotherconfiguredMMIclientcanbeused.

To deactivate the feature execute the follows:

TosetthefeaturestatetoOFF,setthevalueoftheRRCReDirEnabledto0.
Toenablethesignalingunitoverload,setthevalueoftheRRCReDirEnabledto
2.

Formoreinformation,see
DeactivatingRAN147:RRCConnectionSetupRedirectionduetosignaling
unitoverloadreasons
ForIPA-RNC,usethefollowingMMLcommand:
ZW7M: FEA=4780:OFF;

2.10.4.2

Deactivating RAN147: RRC Connection Setup Redirection due to


signaling unit overload reasons
Purpose
Followthisproceduretodeactivatethisfeature.
Before you start
Makesureyouhaveaccesstothefollowingapplications:

ApplicationLauncher

Open the OMS Element Manager.

Go to the Topology Tree View.


Select:Network ManagementTopology Tree View

104

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Expand the RNFC object.

Configure the RNFC object.


a) Fromthedrop-downmenuselectEditEdit Parameters.
b) SettheRRCReDirEnabledparametervaluetoDisabled(0or1).

Save the changes.


a) ClicktheApplybutton.

Open the MMI session.


OpentheSecureMMIWindowapplicationfromtheApplicationLauncher.
Alternatively,anyotherconfiguredMMIclientcanbeused.

To deactivate the feature execute the follows:

TosetthefeaturestatetoOFF,setthevalueoftheRRCReDirEnabledto0.
Toenabletheadmissioncontrolmodifications,setthevalueofthe
RRCReDirEnabledto1.

Formoreinformation,see
DeactivatingRAN147:RRCConnectionSetupRedirectionduetoadmission
controlreasons
ForIPA-RNC,usethefollowingMMLcommand:
ZW7M: FEA=4780:OFF;

2.11 RAN3069: RSRQ-based LTE Reselection


2.11.1 Description of RAN3069: RSRQ-based LTE Reselection
Introduction to the feature
TheRAN3069:RSRQ-basedLTEReselectionfeatureprovidessupportforLTEcell
reselectionbasedonthereferencesignalreceivedquality(RSRQ).

2.11.1.1

Benefits
End-user benefits
Thisfeaturemaximizesend-usersLTEexperience.

Operator benefits
ThisfeatureassuressmoothWCDMA-LTEinterworkingwheninLTEnetworkRSRQ
criteriaareusedforcellreselection.

Issue:01ADRAFT

DN09146788

105

Radioresourcemanagementfeatures

2.11.1.2

RU50FeatureDescriptionsandInstructions

Requirements
Software requirements
Table71:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
Table71

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi Direct OMS


RNC

Flexi BTS

RU50

Notplanned RN8.0

mcRNC4.1

Notplanned OMS3.01)
OMS3.12)

Support
not
required

MGW

UE

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

SGSN

Supportnot
required

Supportnot
required

NetAct8
EP11)

Supportnot Supportnot Supportnot


required
required
required

3GPP
Rel-9

NetAct8
EP22)

1)forRU50
2)forRU50EP1

Hardware requirements
Thisfeaturedoesnotrequireanyneworadditionalhardware.

2.11.1.3

Functional description
Functional overview
IncurrentsystemimplementationtheRAN2067:LTEInterworkingfeaturesupports
referencesymbolreceivedpower(RSRP)-basedLTEreselection.TheRAN3069:RSRQbasedLTEReselectionfeatureintroducesanupgradebyincludingqualitythresholdsfor
LTEpriority-basedcellreselection.Thesequalitythresholdsarespecifiedin3GPPRel-9
andtheyincludetheUTRAservingcellEc/N0thresholdandE-UTRAneighborcell
RSRQqualitythreshold.Thesethresholdsarebroadcastinthesysteminformationblock
type19(SIB19).

2.11.1.4

System impact
Interdependencies between features
ThisfeaturerequirestheRAN2067:LTEInterworkingfeature.

106

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Impact on commands
Therearenocommandsrelatedtothisfeature.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

2.11.1.5

RAN3069: RSRQ-based LTE Reselection management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table72:Newparameterslistsparametersintroducedwiththisfeatureandthe
correspondingSIB19parametersspecifiedin3GPPRel-9.
Table72

Newparameters

Full name

Abbreviated name

SIB19 IE

Managed
object

Threshservinglow2

Threshservlow2

Threshserving,low2

WCEL

QqualminforLTEcellreselection

AdjLQqualminEUTRA

QqualminEUTRA

HOPL

Thresholdhigh2forLTEcellreselection

AdjLThreshigh2

Threshx,high2

HOPL

Thresholdlow2forLTEcellreselection

AdjLThreslow2

Threshx,low2

HOPL

Issue:01ADRAFT

DN09146788

107

Radioresourcemanagementfeatures

2.11.1.6

RU50FeatureDescriptionsandInstructions

Sales information
Table73

Salesinformation

BSW/ASW

SW component

License control in network element

ASW1)

RAN

RNCLK

1)theRAN2067:LTEInterworkingfeaturelicensealsocontrolstheRAN3069:RSRQ-

basedLTEReselectionfeature

2.11.2 Activating RAN3069: RSRQ-based LTE Reselection


Purpose
FollowthisproceduretoactivatetheRAN3069:RSRQ-basedLTEReselectionfeature.
Before you start
AfteractivatingthisfeaturethereisnoneedtorestartneithertheRNC,northeBTS.
Activatingproceduredoesnotcausedowntimeandthefeaturecanbeactivatedatany
timeoftheday.

TheRAN2067:LTEInterworkingfeaturelicensealsocontrolsthe
RAN3069:RSRQ-basedLTEReselectionfeature.Activatethe
RAN2067:LTEInterworkingfeaturecontrolledbythelicensekey
LTEInterworking.Formoreinformation,see
ActivatingRAN2067:LTEInterworking.
Forinformationonmanaginglicenses,seeLicensing.
Toprovideseamlesspriority-basedcellreselectionbetweenGSM,WCDMA,andLTE,
makesuretoadmiteachRadioAccessTechnologyadifferentpriority:

AbsPrioCellReselecWCELparameter,introducedwiththeRAN2067:LTE
Interworkingfeature,definesthepriorityoftheWCDMAservingcell(UTRApriority
infolist/UTRAServingCellIE)
AdjiAbsPrioCellReselecHOPIparameter,introducedwiththeRAN2881:
WCDMAandGSMLayerPrioritiesfeature,definestheWCDMAinter-frequency
priority(UTRApriorityinfolist/UTRANFDDFrequenciesIE)
AdjgAbsPrioCellReselecHOPGparameter,introducedwiththeRAN2881:
WCDMAandGSMLayerPrioritiesfeature,definestheGSMpriority(GSMpriority
infolist/GSMPriorityInfoIE)
AdjLAbsPrioCellReselecHOPLparameter,introducedwiththeRAN2067:LTE
Interworkingfeature,definestheLTEpriority(E-UTRAfrequencyandpriorityinfo
list/E-UTRAfrequencyandpriorityIE)

Priority-basedcell-reselectionbetweenGSMandWCDMAradiotechnologiesis
providedbytheRAN2881:WCDMAandGSMLayerPrioritiesfeature.
WCDMApriorityisbroadcastperUARFCNinSIB19message.Thesamepriorityvalue
shouldbegivenforeachinter-frequencyWCDMAneighbor.Ifmorethanonevalueis
given,thehighestpriorityisbroadcastinSIB19message.

108

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

IfqualitycriteriaarechosentobeusedforLTEabsolute-priority-basedcell
reselection,ensurethatbothThreshx, high2(AdjLThreshigh2HOPL
parameter)andThreshx, low2(AdjLThreslow2HOPLparameter)are
configuredatthesametimeandbroadcastinSIB19.OtherwiseUEisnotusing
theseparameters.Also,ensurethatprioritiesforwhichbothThreshx, high2
andThreshx, low2areprovidedinSIB19arealwaysdifferentfromthe
prioritiesforwhichtheseparametersarenotprovidedinSIB19.Bydefault
Threshx, high2andThreshx, low2arenotbroadcastinSIB19.
Notethattheactivationprocedureforthe
RAN3069:RSRQ-basedLTEReselectionfeatureisthesameasforthe
RAN2067:LTEInterworkingfeature.

Open the OMS Element Manager.

Go to Topology and expand the ROOT directory.

Expand the RNC object and then the WBTS object.

Configure the WCEL object:


a) Right-click on the WCEL object and select Edit parameters.
b) In System Info tab, set the values of LTECellReselection parameter to
Enabled.

Further information

NotethattheUEdoesnotuseHierarchicalCellStructure(HCS)forinterfrequencyorinter-RATreselectionifabsolute-priority-basedcellreselectionis
used.

2.11.3 Verifying RAN3069: RSRQ-based LTE Reselection


Purpose
FollowthesetipstoverifythattheRAN3069:RSRQ-basedLTEReselectionfeature
worksproperlyinthenetwork.
Before you start
ToverifytheusageofthequalitycriteriaforLTEabsolute-priority-basedcellreselection,
youalsoneedtoactivateandverifytheRAN2067:LTEInterworkingfeature.Formore
information,seeActivatingRAN2067:LTEInterworkingandVerifyingRAN2067:LTE
Interworking.

Issue:01ADRAFT

Therearenocountersinvolvedincellreselectionprocess.TheUEreselectsthe
cellaccordingtotheparametersbroadcastbythenetworkinSIB19message.

DN09146788

109

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

WhentheRAN3069:RSRQ-basedLTEReselectionfeatureisactive,itisvisibleinthe
contentofSIB19message.Afteractivatingthisfeatureandascribingvaluestothe
parameterslistedinRAN3069:RSRQ-basedLTEReselectionmanagementdata
section,theE-UTRAfrequencyandpriorityinfolist/E-UTRAfrequencyandpriority
informationelementswillbebroadcastinSIB19message.
ContentofSIB19messagecanbemonitoredbyusingUEandnetworkprotocol
analyzer.
Further information
CampingonadesiredlayerisperformedbytheUEusingSIB19parameters.Cell
reselectionalgorithmisspecifiedin3GPPTS25.304UserEquipment(UE)procedures
inidlemodeandproceduresforcellreselectioninconnectedmode.

2.11.4 Deactivating RAN3069: RSRQ-based LTE Reselection


Purpose
FollowthisproceduretodeactivatetheRAN3069:RSRQ-basedLTEReselection
feature.
Before you start

110

InordertoverifyusageofthequalitycriteriaforLTEabsoluteprioritybasedcell
reselection,activationoftheRAN2067:LTEInterworkingfeaturewasneeded.
Therefore,fordeactivatingtheRAN3069:RSRQ-basedLTEReselection
feature,instructionsontheRAN2067:LTEInterworkingfeaturedeactivationare
alsoincluded.Formoreinformation,see
DeactivatingRAN2067:LTEInterworking.

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Open the OMS Element Manager.

Go to Topology and expand the ROOT directory.

Expand the RNC object and then the WBTS object.

Configure the WCEL object:


a) Right-click on the WCEL object and select Edit parameters.
b) In System Info tab, set the values of LTECellReselection parameter to
Disabled.

2.12 RAN2264: Smart LTE Handover


2.12.1 Description of RAN2264: Smart LTE Handover
Introduction to the feature
TheRAN2264:SmartLTEHandoverfeatureintroducesinter-RATWCDMAtoLTE
handover.ThisfeaturesupportstrafficsteeringtoLTElayers,providingseamless
handoverexperiencefortheend-users.

2.12.1.1

Benefits
End-user benefits
EnduserbenefitsfromseamlessWCDMAtoLTEhandoverexperience.

Operator benefits
ThankstothisfeatureWCDMAtoLTEmobilitybecomesfasterendmorereliable,as
handoverisprecededwithcompressedmodemeasurements.

2.12.1.2

Requirements
Software requirements
Table74:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
Table74

Issue:01ADRAFT

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi
OMS
Direct RNC

Flexi BTS

RU50

FlexiDirect
RU50

mcRNC4.1

ADA6.0

WN9.0

RN8.0

OMS3.01)
OMS3.12)

DN09146788

111

Radioresourcemanagementfeatures

Table74

RAS

RU50FeatureDescriptionsandInstructions

Softwarerequirements(Cont.)

Flexi Direct IPA-RNC

mcRNC

Flexi
OMS
Direct RNC

Flexi BTS

IHO6.03)

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

WL9.1

WN9.1

NetAct8
EP11)

Supportnot Plannedfor Supportnot 3GPPRelrequired


later
required
8(optional)
releases

NetAct8
EP22)3)

SGSN

MGW

UE

1)forRU50
2)forRU50EP1
3)forFlexiDirectRU50

Hardware requirements
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradio
SystemModuleFSMForFlexiLiteBTSWCDMA.

2.12.1.3

Functional description
TheRAN2264:SmartLTEHandoverfeatureintroducesinter-systemhandoverfrom
WCDMAtoLTE.
Inter-RAThandoverfromWCDMAtoLTEcanbestartedifcompressedmode
measurementsindicatethatLTEcoverageisavailable.Thefollowingeventscantrigger
compressedmodemeasurementsforLTEhandover:

T1:Cell_DCHtoCell_FACH,Cell_PCH,orURA_PCHselection
T2:HSDPAreconfigurationtotraditionalDCH,forexamplereconfigurationcausedby
highHSDPAloadandlackofHSDPAcellresources
T3:CScallreleasewithactivePSRAB
T4:Periodictrigger

InuplinkDCHisusedduringcompressedmode.However,ifHSUPAcompressedmode
supportedbytheRAN1668:HSUPACompressedModeforLTEandInter-frequency
Handoverfeatureisactive,thenHSUPAcompressedmodeisusedinuplink.
IncaseswhenWCDMAcellloadisnothighanduserscanbeprovidedwithgood
enoughexperienceinWCDMAlayer,measurementsandhandovertoLTEcanbebypassed.Celllevelloadparameterscanbeusedtodefineifloadislowenoughfor
keepingUEsinWCDMA.

112

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

TheRAN2264:SmartLTEHandoverfeaturesupportsinter-RAThandoverfromWCDMA
tobothFDD-LTEandTDD-LTE.

2.12.1.4

System impact
Interdependencies between features
TheRAN2067:LTEInterworkingfeatureisaprerequisiteforusingthisfeature.
ForHSUPAcompressedmodemeasurements,theRAN1668:HSUPACompressed
ModeforLTEandInter-frequencyHandoverfeatureisrequired.

ThisfeaturerequiresalsosupportfromtheUE,3Gcorenetwork,LTEcore
network,andLTEeNB.

Impact on interfaces
ThisfeaturecausesriseofsignalingtrafficonUu,Iub,Iur,andIuPSinterfaces
(compressedmoderelatedsignaling,LTEneighborreportingoverIur,relocationrelated
signalingbetweenRNCandcorenetwork).

Impact on network and network element management tools

NewManagedObjectClass(MOC):ADJEisintroducedfordefiningE-UTRA(LTE)
neighborcells.
NewcountersformonitoringoutgoingLTEPSHandoverareintroduced.

Impact on system performance and capacity

2.12.1.5

Thisfeaturesupportstrafficsteeringandnetworkloadbalancingscenarios.
OffloadingWCDMAnetworkduringhighloadstatesviaseamlesshandovertoLTE
(resourcesarereservedinadvanceonLTEsideincontrasttolayeringfeatures)
increasesavailableHSDPApowerperuserratioinWCDMAcell.
ThisfeatureimpactsthemaximumnumberofUEsthataresimultaneouslyin
compressedmodeinthecellduetoanon-criticalhandovermeasurementreason
(bothDCHandHSPAcompressedmodes).

RAN2264: Smart LTE Handover management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Table75:Newcounterslistscountersintroducedwiththisfeature.

Issue:01ADRAFT

DN09146788

113

Radioresourcemanagementfeatures

Table75

114

RU50FeatureDescriptionsandInstructions

Newcounters

Counter ID

Counter name

Measurement

M1010C240

LTENRTISHOMEASWITHCMDUETO
DCHTOCCH

InterSystemHardHandover

M1010C241

LTENRTISHOMEASWITHCMDUETO
HSPATODCH

InterSystemHardHandover

M1010C242

LTENRTISHOMEASWITHCMDUETO
CSRABRELEASE

InterSystemHardHandover

M1010C243

LTENRTISHOMEASWITHCMDUETO
PERIODICTRIGGER

InterSystemHardHandover

M1010C244

LTENRTISHOMEASWITHOUTCMDUE
TODCHTOCCH

InterSystemHardHandover

M1010C245

LTENRTISHOMEASWITHOUTCMDUE
TOHSPATODCH

InterSystemHardHandover

M1010C246

LTENRTISHOMEASWITHOUTCMDUE
TOCSRABRELEASE

InterSystemHardHandover

M1010C247

LTENRTISHOMEASWITHOUTCMDUE
TOPERIODICTRIGGER

InterSystemHardHandover

M1010C248

LTENRTISHONOCELLFOUNDDUETO
DCHTOCCH

InterSystemHardHandover

M1010C249

LTENRTISHONOCELLFOUNDDUETO
HSPATODCH

InterSystemHardHandover

M1010C250

LTENRTISHONOCELLFOUNDDUETO
CSRABRELEASE

InterSystemHardHandover

M1010C251

LTENRTISHONOCELLFOUNDDUETO
PERIODICTRIGGER

InterSystemHardHandover

M1010C252

LTENRTISHOATTEMPTSDUETODCH
TOCCH

InterSystemHardHandover

M1010C253

LTENRTISHOATTEMPTSDUETOHSPA InterSystemHardHandover
TODCH

M1010C254

LTENRTISHOATTEMPTSDUETOCS
RABRELEASE

InterSystemHardHandover

M1010C255

LTENRTISHOATTEMPTSDUETO
PERIODICTRIGGER

InterSystemHardHandover

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table75

Issue:01ADRAFT

Radioresourcemanagementfeatures

Newcounters(Cont.)

Counter ID

Counter name

Measurement

M1010C256

LTENRTISHOSUCCESSDUETODCH
TOCCH

InterSystemHardHandover

M1010C257

LTENRTISHOSUCCESSDUETOHSPA
TODCH

InterSystemHardHandover

M1010C258

LTENRTISHOSUCCESSDUETOCS
RABRELEASE

InterSystemHardHandover

M1010C259

LTENRTISHOSUCCESSDUETO
PERIODICTRIGGER

InterSystemHardHandover

M1010C260

LTENRTISHOUENACKDUETODCH
TOCCH

InterSystemHardHandover

M1010C261

LTENRTISHOUENACKDUETOHSPA
TODCH

InterSystemHardHandover

M1010C262

LTENRTISHOUENACKDUETOCS
RABRELEASE

InterSystemHardHandover

M1010C263

LTENRTISHOUENACKDUETO
PERIODICTRIGGER

InterSystemHardHandover

M1010C264

LTENRTISHOUELOSTDUETODCHTO InterSystemHardHandover
CCH

M1010C265

LTENRTISHOUELOSTDUETOHSPA
TODCH

M1010C266

LTENRTISHOUELOSTDUETOCSRAB InterSystemHardHandover
RELEASE

M1010C267

LTENRTISHOUELOSTDUETO
PERIODICTRIGGER

InterSystemHardHandover

M1010C268

LTENRTISHOPREPARATIONFAIL

InterSystemHardHandover

M1019C0

LTEISHOATTEMPTS

AutoDefLTE

M1019C1

LTEISHOSUCCESSFUL

AutoDefLTE

M1036C0

LTEPSISHOOUTPREPREQ

LTERelocation

M1036C1

LTEPSISHOOUTPREPSUCC

LTERelocation

M1036C2

LTEPSISHOOUTPREPFAILDUETO
RNLAYERCAUSE

LTERelocation

DN09146788

InterSystemHardHandover

115

Radioresourcemanagementfeatures

Table75

RU50FeatureDescriptionsandInstructions

Newcounters(Cont.)

Counter ID

Counter name

Measurement

M1036C3

LTEPSISHOOUTPREPFAILDUETOTR LTERelocation
LAYERCAUSE

M1036C4

LTEPSISHOOUTPREPFAILDUETO
NASCAUSE

LTERelocation

M1036C5

LTEPSISHOOUTPREPFAILDUETO
PROTCAUSE

LTERelocation

M1036C6

LTEPSISHOOUTPREPFAILDUETO
MISCCAUSE

LTERelocation

M1036C7

LTEPSISHOOUTPREPFAILDUETO
NONSTANCAUSE

LTERelocation

M1036C8

LTEPSISHOCANCELTOTAL

LTERelocation

M1036C9

LTEPSISHOFAILDUETORELOC
OVERALLTIMEREXPIRY

LTERelocation

M1036C10

LTEPSISHOCANCELDUETORELOC
PREPTIMEREXPIRY

LTERelocation

Table76:Relatedexistingcounterslistsexistingcountersrelatedtothisfeature.
Table76

Relatedexistingcounters

Counter ID

Counter name

Measurement

M1010C239

DURATIONOFLTECARRIER
MEASUREMENT

InterSystemHardHandover

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table77:Newparameterslistsparametersintroducedwiththisfeature.
Table77

116

Newparameters

Full name

Abbreviated name

Managed object

OutgoingLTEHandoverEnabled

LTEHandoverEnabled

RNC/WBTS/WCEL

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table77

Radioresourcemanagementfeatures

Newparameters(Cont.)

Full name

Abbreviated name

Managed object

MinimumIntervalBetweenLTEHOs

LTEMinHoInterval

RNC/FMCL

ADJEIdentifier

ADJEId

RNC/WBTS/WCEL
/ADJE

ChangeoriginforADJEobject

ADJEChangeOrigin

RNC/WBTS/WCEL
/ADJE

Inter-RATLTEadjacentphysicalcell
identifier

AdjePhysicalCellId

RNC/WBTS/WCEL
/ADJE

MobileCountryCode

AdjeMCC

RNC/WBTS/WCEL
/ADJE

MobileNetworkCode

AdjeMNC

RNC/WBTS/WCEL
/ADJE

MobileNetworkCodeLength

AdjeMNCLength

RNC/WBTS/WCEL
/ADJE

MacroeNBID

AdjeENodeBId

RNC/WBTS/WCEL
/ADJE

CellID

AdjeCellId

RNC/WBTS/WCEL
/ADJE

TrackingAreaCode

AdjeTAC

RNC/WBTS/WCEL
/ADJE

ADJLIdentifier

AdjLIdentifier

RNC/WBTS/WCEL
/ADJE

Table78:Modifiedparameterslistsparametersmodifiedbythisfeature.
Table78

Issue:01ADRAFT

Modifiedparameters

Full name

Abbreviated name

Managed object

RNCOptions

RncOptions

RNC

BTSsupportforHSPACM

BTSSupportForHSPACM

RNC/WBTS

MaxnumberofUEsinHSDPACMdue
toNCHO

MaxNumberUEHSPACmNCH
O

RNC/WBTS/WCEL

LTELayerCellHSDPALoad

LTELayerCellHSLoad

WCEL

DN09146788

117

Radioresourcemanagementfeatures

Table78

2.12.1.6

RU50FeatureDescriptionsandInstructions

Modifiedparameters(Cont.)

Full name

Abbreviated name

Managed object

SmartLTELayeringNRTuseramount
threshold

SmartLTELayeringUA

WCEL

SmartLTELayeringservicecontrol

SmartLTELayeringServ

RNMOBI

SmartLTELayeringTargetSystem
Selection

SmartLTELayeringTSysSel

WCEL

LTEPeriodictriggertimer

LTEPeriodicTriggerTimer

RNC

LTEMeasurementAveragingWindow

LTEMeasAveWindow

RNC/FMCL

LTEMaximumMeasurementPeriod

LTEMaxMeasPeriod

RNC/FMCL

LTEMinimumMeasurementInterval

LTEMinMeasInterval

RNC/FMCL

LTENeighborCarrierFrequencySearch LTENcarrFreqSearchPeriod
Period

RNC/FMCL

AdjacentLTEFrequencyPriority

AdjLFreqPriority

RNC/HOPL

LTECarrierfrequencyselection
MinimumRxPowerlevel

AdjLMinRSRPLevel

RNC/HOPL

LTECarrierfrequencyselection
MinimumRxquallevel

AdjLMinRSRQLevel

RNC/HOPL

Identifierofinter-systemadjacencyto
LTE

ADJLId

RNC/WBTS/WCEL
/ADJL

FMCLIdentifier

FMCLIdentifier

RNC/WBTS/WCEL

MaximumnumberofUEsinCMdueto
SLHOmeasurement

MaxNumberUECmSLHO

RNC/WBTS/WCEL

Sales information
Table79

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCLK

2.12.2 Activating RAN2264: Smart LTE Handover


Purpose
Followthisproceduretoactivatethisfeature.

118

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Before you start


RestartoftheRNCandtheBTSisnotrequiredaftertheactivationofthisfeature.
Thisproceduredoesnotcausedowntime,anditcanbeactivatedatanytimeoftheday.
Makesureyouhaveaccesstothefollowingapplications:

OMSElementManager
ApplicationLauncher
Man-machineinterface(MMI)

Beforeactivatingthisfeature,activatethelicenseoftheRAN2067:LTEInterworking
feature(featurecode1755,seeActivatingRAN2067:LTEInterworking).
Thisfeatureiscontrolledbythelong-termON/OFFlicensekey.Forinformationon
managinglicenses,seeLicensing.

Thefeaturecodeforthisfeatureis3414.
TosetthefeaturestatetoON,usethefollowingcommand:

forIPA-RNC:
ZW7M: FEA=3414:ON;

Beforeactivatingthisfeatureconfigurethefollowingdatabaseobjectsandrelevant
parametersandattachthemtoWCDMAcell:

FMCL(Inter-RAT(LTE)measurementcontrolparameterset)

HOPL(Inter-RAT(LTE)neighborfrequencyparameterset)

AdjLEARFCN(mandatory)
HopLIdentifier(mandatory)
AdjLMeasBw(optional,defaultvalueexists)
NotethateventhoughconfiguringAdjLMeasBwparameterisnot
mandatoryforcreatingADJL-object,itisimportantfornetworkplanning.

ADJE(Inter-RAT(LTE)neighborcelldefinitions)

Issue:01ADRAFT

AdjLFreqPriority(optional,defaultvalueexists)
AdjLMinRSRPLevel(optional,seeFurtherinformationsection)
AdjLMinRSRQLevel(optional,seeFurtherinformationsection)

ADJL(Inter-RAT(LTE)neighborfrequencydefinitions)

LTEMinHoInterval(optional,defaultvalueexists)
LTEMeasAveWindow(optional,defaultvalueexists)
LTEMaxMeasPeriod(optional,defaultvalueexists)
LTEMinMeasInterval(optional,defaultvalueexists)
LTENcarrFreqSearchPeriod(optional,defaultvalueexists)

AdjePhysicalCellId(mandatory)
AdjeMCC(mandatory)
AdjeMNC(mandatory)
AdjeMNCLength(optional,defaultvalueexistsforthe2digitMNC)

DN09146788

119

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

AdjeENodeBId(mandatory)
AdjeCellId(mandatory)
AdjeTAC(mandatory)
AdjLIdentifier(mandatory)

Additionally,thefollowingparameterscanbeusedfortuningtheRAN2264:SmartLTE
Handoverfeature:

RNCparameter LTEPeriodicTriggerTimer(optional,defaultvalueexists)
RNMOBIparameterSmartLTELayeringServ(optional,defaultvalueexists)
WCELparameterLTELayerCellHSLoad(optional,defaultvalueexists)
WCELparameterSmartLTELayeringUA(optional,defaultvalueexists)
WCELparameterSmartLTELayeringTSysSel(optional,defaultvalueexists)
RNHSPAparameterTGPLForLTEMeas(optional,defaultvalueexists)

BeforeactivatingthisfeatureensurethecorrectnessofthefollowingneighboringLTE
andCNconfigurationandidentifierparameters:

ADJL-AdjLEARFCN
ADJL-AdjLMeasBw
ADJE-AdjePhysicalCellId
ADJE-AdjeMCC
ADJE-AdjeMNC
ADJE-AdjeMNCLength
ADJE-AdjeENodeBId
ADJE-AdjeCellId
ADJE-AdjeTAC
ADJE-AdjLIdentifier

RNCO&Misnotabletoverifythevaluesoftheseparameters.

120

TheRAN2264:SmartLTEHandoverfeatureisactivatedoncellbasis.

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Open the OMS Element Manager.

Go to Topology.

Expand the ROOT.

Expand the RNC object.

Expand the WBTS object.

Configure the WCEL object:


a) Select Edit Parameters from the WCEL object.
b) Activate the RAN2264: Smart LTE Handover feature with the
LTEHandoverEnabled parameter.

g
g

WCELshouldbeassociatedwithFMCLobject.

Stateofthelicensesmustnotbechangedafteractivatingthefeature.
Further information
WCELparameterLTEHandoverEnabledenablestriggersfortheSmartLTEHandover
asfollows:

value(0)=alltriggersdisabled
value(1)=T1enabled
value(2)=T1andT2enabled
value(3)=T1andT3enabled
value(4)=T1,T2,andT3enabled
value(5)=T1andT4enabled
value(6)=T1,T2,andT4enabled
value(7)=T1,T3,andT4enabled
value(8)=alltriggersenabled(T1,T2,T3,andT4)

where:

T1:RRCstatechangeCell_DCHtoCCH
T2:HSDPA/HSPAtoDCH/DCHCTS
T3:CSRABrelease
T4:Periodictrigger

Formoreinformation,seeDescriptionofRAN2264:SmartLTEHandover.

Issue:01ADRAFT

DN09146788

121

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

TheHSUPAcompressedmodemeasurementsupportforLTEisprovidedbythe
RAN1668:HSUPACompressedModeforLTEandInter-frequencyHandoverfeature.If
thefeatureisnotavailable,E-DCHtoULDCHswitchisneededbeforestartingtheLTE
measurementsforhandover.
ForinstructionsonhowtoactivateandconfigureDCH/DCHcompressedmode(CM)and
HSDPA/DCHCMforLTEhandover,seeActivatingRAN2980:MeasurementBasedLTE
Layering.ForinformationonhowtoactivateandconfigureHSPACMforLTEhandover,
seeActivatingRAN1668HSUPACompressedModeforLTEandInter-frequency
Handover.
TheminimumrequiredRSRP(AdjLMinRSRPLevel)andRSRQ(AdjLMinRSRQLevel)
levelsofthecellunderLTEcarrierfrequencyshouldbealignedwiththecorresponding
thresholdsintheLTEnetwork.
EnsurethattheUEisnotredirectedorhandedoverfromWCDMAtoLTEwiththeRSRP
orRSRQlevels,whicharelowerthanthethresholdsforthecoverage(RSRP)orquality
(RSRQ)-basedhandoverfromLTEtoWCDMA.Forexample,ifthecoverage(RSRP)
basedhandoverfromLTEtoWCDMAisconfiguredtotriggerwithRSRPlevel115
dBm,thentherecommendedminimumRSRPthresholdfortheWCDMAtoLTE
handoveris112dBm(3dBhysteresis)inordertoavoidimmediatehandoverbackto
WCDMA.Correspondingly,ifthequality(RSRQ)-basedhandoverfromLTEtoWCDMA
isconfiguredtotriggerwithRSRQlevel-15dB,thentheminimumRSRQthresholdfor
theWCDMAtoLTEhandovershouldbesetto-12dB(3dBhysteresis).
Inter-RAThandoverfromWCDMAtoLTEissupportedforthefollowingPSQoSclasses:

Interactive(NRT)
Background(NRT)

2.12.3 Verifying RAN2264: Smart LTE Handover


Purpose
Followthisproceduretoverifythatthisfeatureworksproperlyinthenetwork.
ThefunctioningoftheRAN2264:SmartLTEHandoverfeaturecanbeverifiedwiththe
followingcountersfortheinter-RATLTEhandoverattemptsandsuccesses:

M1010C252LTENRTISHOATTEMPTSDUETODCHTOCCH
M1010C253LTENRTISHOATTEMPTSDUETOHSPATODCH
M1010C254LTENRTISHOATTEMPTSDUETOCSRABRELEASE
M1010C255LTENRTISHOATTEMPTSDUETOPERIODICTRIGGER
M1010C256LTENRTISHOSUCCESSDUETODCHTOCCH
M1010C257LTENRTISHOSUCCESSDUETOHSPATODCH
M1010C258LTENRTISHOSUCCESSDUETOCSRABRELEASE
M1010C259LTENRTISHOSUCCESSDUETOPERIODICTRIGGER

Expected outcome
Outgoinginter-RATLTEhandoverissuccessfulandvisibleintheattemptandsuccess
counters.
Further information
MoredetailedmonitoringoftheRAN2264:SmartLTEHandoverfeaturecanbe
performedwiththefollowingcounters:

122

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

M1010C239DURATIONOFLTECARRIERMEASUREMENT
M1010C240LTENRTISHOMEASWITHCMDUETODCHTOCCH
M1010C241LTENRTISHOMEASWITHCMDUETOHSPATODCH
M1010C242LTENRTISHOMEASWITHCMDUETOCSRABRELEASE
M1010C243LTENRTISHOMEASWITHCMDUETOPERIODICTRIGGER
M1010C244LTENRTISHOMEASWITHOUTCMDUETODCHTOCCH
M1010C245LTENRTISHOMEASWITHOUTCMDUETOHSPATODCH
M1010C246LTENRTISHOMEASWITHOUTCMDUETOCSRABRELEASE
M1010C247LTENRTISHOMEASWITHOUTCMDUETOPERIODICTRIGGER
M1010C248LTENRTISHONOCELLFOUNDDUETODCHTOCCH
M1010C249LTENRTISHONOCELLFOUNDDUETOHSPATODCH
M1010C250LTENRTISHONOCELLFOUNDDUETOCSRABRELEASE
M1010C251LTENRTISHONOCELLFOUNDDUETOPERIODICTRIGGER
M1010C260LTENRTISHOUENACKDUETODCHTOCCH
M1010C261LTENRTISHOUENACKDUETOHSPATODCH
M1010C262LTENRTISHOUENACKDUETOCSRABRELEASE
M1010C263LTENRTISHOUENACKDUETOPERIODICTRIGGER
M1010C264LTENRTISHOUELOSTDUETODCHTOCCH
M1010C265LTENRTISHOUELOSTDUETOHSPATODCH
M1010C266LTENRTISHOUELOSTDUETOCSRABRELEASE
M1010C267LTENRTISHOUELOSTDUETOPERIODICTRIGGER
M1010C268LTENRTISHOPREPARATIONFAIL
M1019C0LTEISHOATTEMPTS
M1019C1LTEISHOSUCCESSFUL
M1036C0LTEPSISHOOUTPREPREQ
M1036C1LTEPSISHOOUTPREPSUCC
M1036C2LTEPSISHOOUTPREPFAILDUETORNLAYERCAUSE
M1036C3LTEPSISHOOUTPREPFAILDUETOTRLAYERCAUSE
M1036C4LTEPSISHOOUTPREPFAILDUETONASCAUSE
M1036C5LTEPSISHOOUTPREPFAILDUETOPROTCAUSE
M1036C6LTEPSISHOOUTPREPFAILDUETOMISCCAUSE
M1036C7LTEPSISHOOUTPREPFAILDUETONONSTANCAUSE
M1036C8LTEPSISHOCANCELTOTAL
M1036C9LTEPSISHOFAILDUETORELOCOVERALLTIMEREXPIRY
M1036C10LTEPSISHOCANCELDUETORELOCPREPTIMEREXPIRY

2.12.4 Deactivating RAN2264: Smart LTE Handover


Purpose
Followthisproceduretodeactivatethisfeature.

Issue:01ADRAFT

TheRAN2264:SmartLTEHandoverfeatureisdeactivatedoncellbasis.

DN09146788

123

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

Open the OMS Element Manager.

Go to Topology.

Expand the ROOT.

Expand the RNC object.

Expand the WBTS object.

Configure the WCEL object:


a) Select Edit Parameters from the WCEL object.
b) Deactivate the RAN2264: Smart LTE Handover feature with the
LTEHandoverEnabled parameter.

2.13 RAN2546: VHS Receiver for High speed Train


2.13.1 Description of RAN2546: VHS Receiver for High Speed
Train
Introduction to the feature
ThefeatureintroducesthenewBTSreceiveralgorithm,forservingtheUEsmovingat
thespeedhigherthan250km/h(155mph),uptothe350km/h(217mph).

2.13.1.1

Benefits
End-user benefits
Thisfeatureprovidestheend-userwiththefollowingbenefits::

Thepossibilityofmakingbetter-qualityvoicecalls,forUEsmovingathighspeed(for
exampleintrains).
Experiencingthroughputenhancementwhenmovingatahighspeed.

Operator benefits
Thisfeatureprovidestheoperatorwiththefollowingbenefits(whentheUEismovingat
highspeed):

124

increaseoftheend-usersatisfaction
improvementinthecall-relatedKPIs
improvementinthepowercontrolstability
betterDCHandHSPAthroughputsandcoverage
avoidingtheULinterferencespikesatthebeginningoftheconnection

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

2.13.1.2

Radioresourcemanagementfeatures

Requirements
Software requirements
Thefollowingtablelistssoftwarerequiredforthisfeature.
Table80

Softwarerequirements

RAS

Flexi
Direct

IPA-RNC

mc-RNC

Flexi
Direct
RNC

OMS

Flexi BTS Flexi Lite


BTS

RU50
EP1

Support
not
required

Support
not
required

Support
not
required

Support
not
required

Support
not
required

WN9.1

Not
planned

Flexi 10 BTS

NetAct

MSC

SGSN

MGW

UE

WN9.1

NetAct8EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradio
SystemModuleFSMF.

2.13.1.3

Functional description
ThenewalgorithmintroducedwiththeRAN2546:VHSReceiverforHighSpeedTrain
featureiscalled:VeryHighSpeedapproach(theVHS approach).Thefeatureimproves
thereceiverperformanceintermsofpowerstabilityanddecodingperformanceatahigh
speedupto350km/h(217mph).
ThisfeatureiscontrolledbythelicenseandactivatedontheBTSlevel.

2.13.1.4

System impact
Interdependencies between features
Thisfeatureaffectsthefollowingfeature:

RAN1702:FrequencyDomainEqualizer

Impact on interfaces
Thefeaturedoesnotimpactthesysteminterface.

Impact on network and network element management tools


Thefeaturedoesnotimpactthenetworkandnetworkelementmanagementtools.

Impact on system performance and capacity


Thefeatureimpactsthesystemperformanceandcapacityasfollows:

Issue:01ADRAFT

stabilizingthepowercontrolfunctionbothintheULandDL
improvingtheULchanneldecodingperformance(fortheUEsmovingathighspeed)

DN09146788

125

Radioresourcemanagementfeatures

2.13.1.5

RU50FeatureDescriptionsandInstructions

achievingfrom3to4dBgainindecodingperformancefortheR99CS/PSserviceat
highspeed(350km/h;217mph)
improvingtheHS-DPCCHACK/NACKdecodingperformanceresultinginimproved
theHS-DSCHthroughputatahighspeed
improvingtheE-DCHthroughput
increasingtheCPUcyclesinDSP(Rake)consumption

RAN2546: VHS Receiver for High Speed Train management data


Alarms
Therearenonewalarmsrelatedtothisfeature.

Measurements and counters


Therearenonewmeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenonewkeyperformanceindicatorsrelatedtothisfeature.

Parameters
Therearenonewparametersrelatedtothisfeature.

2.13.1.6

Sales information
Table81

Salesinformation

BSW/ASW

RAS SW component

License control in network


element

ASW

RAN

BTSon/offlicense

2.14 RAN2881: WCDMA and GSM Layer Priorities


2.14.1 Description of RAN2881: WCDMA and GSM Layer Priorities
Introduction to the feature
TheRAN2881:WCDMAandGSMLayerPrioritiesfeatureallowsidlemodetraffic
steeringaccordingtoprioritiesgivenforWCDMAandGSMlayers.

2.14.1.1

Benefits
End-user benefits
Thisfeatureprovidesend-userhigherdataratesandfasterresponsetimes.

Operator benefits
Introducedidle-modetrafficsteeringreducestheneedforhandoversandreselectsthe
bestpossiblelayerfortheend-user.Operatorcontrolstheprioritiesofthelayers.

126

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

2.14.1.2

Radioresourcemanagementfeatures

Requirements
Software requirements
Table82:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
Table82

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi Direct OMS


RNC

Flexi BTS

RU50

Notplanned RN8.0

mcRNC4.1

Notplanned OMS3.01)
OMS3.12)

Support
not
required

MGW

UE

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

SGSN

Supportnot
required

Supportnot
required

NetAct8
EP11)

Supportnot Supportnot Supportnot


required
required
required

3GPP
Rel-8

NetAct8
EP22)

1)forRU50
2)forRU50EP1

Hardware requirements
Thisfeaturedoesnotrequireanyneworadditionalhardware.

2.14.1.3

Functional description
Functional overview
TheRAN2881:WCDMAandGSMLayerPrioritiesfeatureenablesWCDMAandGSM
cellreselectionbasedonlayer/RadioAccessTechnologypriorities.Whenlayer-specific
absolutepriorityinformationisprovidedinthesysteminformationblocktype19(SIB19),
UEperiodicallymeasureshigherprioritylayers.UEmeasurementsareapplicablewhen
theUEisinidlemode,Cell_PCH,orURA_PCHstate.Alsolowerandequalpriority
layersaremeasuredbyUE,ifradioconditionsinthecampedfrequencyfallbelow
criteriadefinedwithsearchthresholds.
Basedonresultsofthesemeasurements,UEperformspriority-basedcellreselection
usingbothcoverageandqualitythresholdsbroadcastinSIB19.ForWCDMAandGSM
priority-basedcellreselectionthesethresholdsarespecifiedin3GPPRel-8.
Inadditiontotheprioritynumberforthelayer,signalstrengthandqualitythresholdsare
providedforcellreselection.Frequencybandprioritizationcanbeadjustedwith
thresholds,forexample,900MHzcanbepreferredforcelledgeUEsand2100MHz-for
closebyUEs.UEsabovecertainthresholdmovetohigherprioritylayer,whereascell

Issue:01ADRAFT

DN09146788

127

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

edgeUEspreferlowprioritylayerastheyarebelowthethreshold.Figure7:WCDMA
andGSMcellreselectionbasedonlayerprioritiesshowsthemechanismofcell
reselection.Theabsoluteprioritymechanismis3GPPRel-8feature.
Figure7

2.14.1.4

WCDMAandGSMcellreselectionbasedonlayerpriorities

System impact
Interdependencies between features
HierarchicalCellStructurecannotbeusedsimultaneouslywithRAN2881:WCDMAand
GSMLayerPrioritiesfeature.

Impact on commands
Therearenocommandsrelatedtothisfeature.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

2.14.1.5

RAN2881: WCDMA and GSM Layer Priorities management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

128

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table83:Newparameterslistsparametersintroducedwiththisfeatureandthe
correspondingSIB19parametersspecifiedin3GPPRel-8.
Table83

Newparameters

Full name

Abbreviated name

SIB19 IE

Managed
object

WCDMACellReselection

WCDMACellReselection

N/A

WCEL

GSMCellReselection

GSMCellReselection

N/A

WCEL

Absolutepriorityforinter-frequencycell
reselection

AdjiAbsPrioCellReselec

priority

HOPI

Thresholdhighforinter-frequencycell
reselection

AdjiThreshigh

Threshx,high

HOPI

Thresholdlowforinter-frequencycell
reselection

AdjiThreslow

Threshx,low

HOPI

QqualminFDDforinter-frequencycell
reselection

AdjiQqualminFDD

QqualminFDD

HOPI

QrxlevminFDDforinter-frequencycell
reselection

AdjiQrxlevminFDD

QrxlevminFDD

HOPI

AbsolutepriorityforGSMcellreselection

AdjgAbsPrioCellReselec

priority

HOPG

ThresholdhighforGSMcellreselection

AdjgThreshigh

Threshx,high

HOPG

ThresholdlowforGSMcellreselection

AdjgThreslow

Threshx,low

HOPG

Threshservinglow2

Threshservlow2

Threshserving,low2

WCEL

SystemInformationBlock19Compmask5

SIB19Compmask5

N/A

WCEL

SystemInformationBlock19Compmask6

SIB19Compmask6

N/A

WCEL

SystemInformationBlock19Compmask7

SIB19Compmask7

N/A

WCEL

Table84:Modifiedparameterslistsparametersmodifiedbythisfeatureandthe
correspondingSIB19parametersspecifiedin3GPPRel-8.

Issue:01ADRAFT

DN09146788

129

Radioresourcemanagementfeatures

Table84

RU50FeatureDescriptionsandInstructions

Modifiedparameters

Full name

Abbreviated name

SIB19 IE

Managed
object

RNCOptions

RncOptions

N/A

RNC

Absoluteprioritylevelforcellreselection

AbsPrioCellReselec

priority

WCEL

Sprioritysearch1

Sprioritysearch1

Sprioritysearch1

WCEL

Sprioritysearch2

Sprioritysearch2

Sprioritysearch2

WCEL

Threshservinglow

Threshservlow

Threshserving,low

WCEL

UTRAAbsoluteRadioFrequencyChannel
Number

AdjiUARFCN

UARFCN

ADJI

RTHOPIIdentifier

RtHopiIdentifier

N/A

ADJI

CellRe-selectionMinimumRXLevel

AdjgQrxlevMin

QrxlevminGSM

HOPG

RTHOPGIdentifier

RtHopgIdentifier

N/A

ADJG

CellReselectionAbsolutePriority

AdjLAbsPrioCellReselec

priority

HOPL

PriorityforSIB19

SIB19Priority

N/A

RNC

ListofCompmasksinSystemInformationBlock
19

SIB19CompmaskInfo

N/A

WCEL

Block19Compmask1

SIB19Compmask1

N/A

WCEL

SystemInformationBlock19Compmask2

SIB19Compmask2

N/A

WCEL

SystemInformationBlock19Compmask3

SIB19Compmask3

N/A

WCEL

SystemInformationBlock19Compmask4

SIB19Compmask4

N/A

WCEL

Table85:Relatedexistingparameterslistsexistingparametersrelatedtothisfeature
andthecorrespondingSIB19parametersspecifiedin3GPPRel-8.
Table85

Relatedexistingparameters

Full name

Abbreviated name

SIB19 IE

Managed
object

BCCHARFCN

AdjgBCCH

GSMcellgroupList/
StartingARFCN

ADJG

130

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table85

Radioresourcemanagementfeatures

Relatedexistingparameters(Cont.)

Full name

Abbreviated name

SIB19 IE

Managed
object

GSMcellgroupList/List
ofARFCNs
BandIndicator

2.14.1.6

AdjgBandIndicator

GSMcellgroupList/
BandIndicator

ADJG

Sales information
Table86

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCLK

2.14.2 Activating RAN2881: WCDMA and GSM Layer Priorities


Purpose
FollowthisproceduretoactivatetheRAN2881:WCDMAandGSMLayerPriorities
feature.
Before you start
AfteractivatingthisfeaturethereisnoneedtorestartneithertheRNC,northeBTS.
Activatingproceduredoesnotcausedowntimeandthefeaturecanbeactivatedatany
timeoftheday.
ActivatethelicenseoftheRAN2881:WCDMAandGSMLayerPrioritiesfeatureusing
WCDMAandGSMLayerPrioritieslicensekey.
TosetthefeaturestatetoON,usethefollowingcommand:

forIPA-RNC:
ZW7M: FEA=4781:ON;

Forinformationonmanaginglicenses,seeLicensing.
Toprovideseamlesspriority-basedcellreselectionbetweenGSM,WCDMA,andLTE,
makesuretoadmiteachRadioAccessTechnologyadifferentpriority:

Issue:01ADRAFT

AbsPrioCellReselecWCELparameter,introducedwiththeRAN2067:LTE
Interworkingfeature,definesthepriorityoftheWCDMAservingcell(UTRApriority
infolist/UTRAServingCellIE)
AdjiAbsPrioCellReselecHOPIparameter,introducedwiththeRAN2881:
WCDMAandGSMLayerPrioritiesfeature,definestheWCDMAinter-frequency
priority(UTRApriorityinfolist/UTRANFDDFrequenciesIE)

DN09146788

131

Radioresourcemanagementfeatures

RU50FeatureDescriptionsandInstructions

AdjgAbsPrioCellReselecHOPGparameter,introducedwiththeRAN2881:
WCDMAandGSMLayerPrioritiesfeature,definestheGSMpriority(GSMpriority
infolist/GSMPriorityInfoIE)
AdjLAbsPrioCellReselecHOPLparameter,introducedwiththeRAN2067:LTE
Interworkingfeature,definestheLTEpriority(E-UTRAfrequencyandpriorityinfo
list/E-UTRAfrequencyandpriorityIE)

Priority-basedcellreselectionbetweenWCDMAandLTEradiotechnologiesis
providedbytheRAN2067:LTEInterworkingfeature.The
RAN3069:RSRQ-basedLTEReselectionfeatureisanextensiontothe
RAN2067:LTEInterworkingfeatureandprovidesqualitythresholdsforLTE
priority-basedcellreselection.
RtHopiIdentifier (RT HOPI Identifier)ADJIparameterisusedfordefining
parametersetforWCDMAinter-frequencyabsoluteprioritycellreselection.
RtHopgIdentifier (RT HOPG Identifier)ADJGparameterisusedfordefining
parametersetforGSMabsoluteprioritycellreselection.
WCDMApriorityisbroadcastperUARFCNinSIB19message.Thesamepriorityvalue
shouldbegivenforeachinter-frequencyWCDMAneighbor.Ifmorethanonevalueis
given,thehighestpriorityisbroadcastinSIB19message.Correspondingly,GSMpriority
isbroadcastperGSMcellgroup(BCCHARFCN+BandIndicator)inSIB19message.
Thus,priorityshouldbedefinedsothatthesamepriorityvalueisgivenforeachGSM
neighborwithinthesamefrequency.Ifmorethanonevalueisgiven,thehighestpriority
isbroadcastinSIB19message.

BeforeenablingtheGSMCellReselectionWCELparameterinthecell,make
surethatGSMpriority(AdjgAbsPrioCellReselecparameter)isdefinedfor
eachGSMneighborcell.IfpriorityinformationisprovidedforanyGSMlayer,
cellsbelongingtoGSMlayerforwhichnopriorityisassignedarenot
consideredforreselection.DefaultvalueofAdjgAbsPrioCellReselec
parametermeansthatGSMpriorityisnotdefined.

Open the OMS Element Manager.

Go to Topology and expand the ROOT directory.

Expand the RNC object and then the WBTS object.

Configure the WCEL object:


a) Right-click on the WCEL object and select Edit parameters.
b) In System Info tab, set the values of WCDMACellReselection and
GSMCellReselection parameter to Enabled.

Further information

132

NotethattheUEdoesnotuseHierarchicalCellStructure(HCS)forinterfrequencyorinter-RATreselectionifabsolute-priority-basedcellreselectionis
used.

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Radioresourcemanagementfeatures

2.14.3 Verifying RAN2881: WCDMA and GSM Layer Priorities


Purpose
FollowthesetipstoverifythattheRAN2881:WCDMAandGSMLayerPrioritiesfeature
worksproperlyinthenetwork.
Before you start

Therearenocountersinvolvedincellreselectionprocess.UEreselectsthecell
accordingtotheparametersbroadcastbythenetworkinSIB19message.
WhentheRAN2881:WCDMAandGSMLayerPrioritiesfeatureisactive,itisvisiblein
thecontentofSIB19message.Afteractivatingthisfeatureandascribingvaluestothe
parameterslistedinRAN2881:WCDMAandGSMLayerPrioritiesmanagementdata
section,thefollowinginformationelementswillbebroadcastedinSIB19message:

UTRApriorityinfolist/UTRAServingCell
UTRApriorityinfolist/UTRANFDDFrequencies
GSMpriorityinfolist/GSMPriorityInfo

ContentofSIB19messagecanbemonitoredbyusingUEandnetworkprotocol
analyzer.
Further information
CampingonadesiredlayerisperfomedbyUEusingSIB19parameters.Cellreselection
algorithmisspecifiedin3GPPTS25.304UserEquipment(UE)proceduresinidlemode
andproceduresforcellreselectioninconnectedmode.

2.14.4 Deactivating RAN2881: WCDMA and GSM Layer Priorities


Purpose
FollowthisproceduretodeactivatetheRAN2881:WCDMAandGSMLayerPriorities
feature.

Open the OMS Element Manager.

Go to Topology and expand the ROOT directory.

Expand the RNC object and then the WBTS object.

Configure the WCEL object:


a) Right-click on the WCEL object and select Edit parameters.
b) In System Info tab, set the values of WCDMACellReselection and
GSMCellReselection parameter to Disabled.

Issue:01ADRAFT

DN09146788

133

Telecomfeatures

RU50FeatureDescriptionsandInstructions

3 Telecom features
3.1 RAN2211: Multi-Cell HSDPA
3.1.1 Description of RAN2211: Multi-Cell HSDPA

TheRAN2211featuredescriptionpresentsthetrialfunctionalitiesofthe
feature.Thefeatureinthisstatecannotbetriedonthelivenetwork.Formore
informationontestingpossibilitiesandlimitations,contacttheNSNdirectly.

Introduction to the feature


Thisfeatureenablesusageofupto3simultaneousHSDPADLfrequencycarriersfor
oneuser.

3.1.1.1

Benefits
End-user benefits
Thisfeatureallowsfortheusageofthreefrequencycarriers,whatincombinationwith
theRAN1643:64QAMfeature,enablestheend-userachievingdownlinkpeakdatarates
upto63Mbps.Thegainstotheend-usercanbenoticedwhenusingtheInternetand
transmittingpacketdata.

Operator benefits
Byimplementingthisfeature,operatorbenefitsfromtheenhancedaverageuserandcell
throughputandenhancedend-usersatisfaction.
Thethroughputinthecellcanbeonaverageeven5%to50%bigger,comparedtothe
DC+64QAMusage(dependingonthenetworkload).

3.1.1.2

Requirements
Software requirements
Formoreinformationonthetrialsoftwarerequirements,contacttheNSNdirectly.

Hardware requirements
Formoreinformationonthetrialhardwarerequirements,contacttheNSNdirectly.

3.1.1.3

Functional description
Thefeaturesupports3C-HSDPAconfigurationforoneUEwithoneNRTserviceinthe
laboratory-conditionstrial.Thetrialsoftwareisnotintendedforfieldorliveoperation.
Thescopeofthetrialistodemonstratethe63Mbpssingleuserpeakrate.Formore
informationonthetrialfeaturefunctionalities,contacttheNSNdirectly.

134

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

3.1.1.4

Telecomfeatures

System impact
Interdependencies between features
Thisfeaturerequiresthefollowingfeatures:

RAN826:BasicHSUPA
RAN1906:DC-HSDPA42Mbps

ThefollowingfeaturesarerelatedtotheRAN2211:Multi-CellHSDPAfeature:

RAN2179:DualBandHSDPA42Mbps
RAN1643:HSDPA64QAM
RAN1645:HSUPA16QAM
RAN981:HSUPA5.8Mbps
RAN1262:QoSAwareHSPAScheduling
RAN1803:L2resourcemanagement
RAN955:PowersavingmodeforBTS
RAN2394:ExtendedBTSSiteCapacity
RAN2398:ChainingofSeveralFlexiRelease2SystemModules(>2)
RAN2879:MassEventHandler
RAN2509:ApplicationawareRAN
RAN1881:RFChaining
RAN2736:18cellsBTS
RAN1644:CPC

TheRAN2211:Multi-CellHSDPAfeaturesupportsthefollowingIubtransportmodes:

RAN74:IPBasedIubforFlexiWCDMABTS
RAN1449:DualIubforFlexiWCDMABTS

Impact on interfaces
TheAdditionalHSCellInformationIEwillbemodifiedforthefollowingNBAPmessages:

RADIOLINKSETUPREQUEST
RADIOLINKRECONFIGURATIONPREPARE
RADIOLINKSETUPRESPONSE
RADIOLINKRECONFIGURATIONREADY

TheOrdinalNumberofFrequencyIEisaddedtoHS-DSCHFDDSecondaryServing
InformationIE.TheRNCassignstotheOrdinalNumberofFrequencyvaluesforeachof
thesecondaryservingHS-DSCHRLsinconsecutiveorder,startingwithvalue1.
ThePhysicalChannelcapabilityIEisaddedtotheRRCCONNECTIONSETUP
COMPLETEmessage.ThisIEcorrespondstotheHS-DSCHcategorysupportedbythe
UEwhenitisconfiguredwithmulticelloperation.Theinformationispreservedforthe
lifetimeoftheRRCConnection.
TheAdditionaldownlinksecondarycellinformationIEisaddedtothefollowing
messages:

Issue:01ADRAFT

DN09146788

135

Telecomfeatures

RU50FeatureDescriptionsandInstructions

RRC:ACTIVESETUPDATE
RRC:CELLUPDATECONFIRM
RRC:PHYSICALCHANNELRECONFIGURAION
RRC:RADIOBEARERRECONFIGURATION
RRC:RADIOBEARERRELEASE
RRC:RADIOBEARERSETUP
RRC:RRCCONNECTIONSETUP
RRC:TRANSPORTCHANNELRECONFIGURATION

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


TheRAN2211:Multi-CellHSDPAfeatureimpactsthesystemperformanceasfollows:

Itincreasesthedatarateupto63Mbps
Intheuplink,about1.5%oftheFTPdownlinkdatarateisneededforTCPACKs(40
ByteACKforeverysecondTCPpacketof~1500Bytes).
Theamountsignallingisincreased:RRCandNBAPmessagescontainmoredata,
whentheMC-HSDPAisused(onenewsecondarycarrier).

TheRAN2211:Multi-CellHSDPAfeatureimpactsthesystemcapacityasfollows:

3.1.1.5

ThefeaturemultipliestheUEthroughputforsinglecarrierinthesectorby
aggregatingthecarriers
Itincreasesthefrequencydiversityinthecells

RAN2211: Multi-Cell HSDPA management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothefeature.

Measurements and counters


TheTable87:presentsthecountersrelatedtothefeature

136

Counter ID

Counter name

Measurement

M1001C743

ACCESSSTRATUMRELEASEINDICATOR
RELEASE10

ServiceLevel(RNC)

M1001C744

ACCESSSTRATUMRELEASEINDICATOR
RELEASE11

ServiceLevel(RNC)

M5000C449

DATAVOLUMEOFMCHSDPAUSERS
SCHEDULEDINONECARRIER

HSPAinWBTS(WBTS)

M5000C450

DATAVOLUMEOFMCHSDPAUSERS
SCHEDULEDINTWOCARRIERS

HSPAinWBTS(WBTS)

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Telecomfeatures

Counter ID

Counter name

Measurement

M5000C451

DATAVOLUMEOFMCHSDPAUSERS
SCHEDULEDINTHREECARRIERS

HSPAinWBTS(WBTS)

M5002C130

ORIGINALHSDPADATA

CellThroughputinWBTS
(WBTS)

M5002C126

ACKNOWLEDGEDMCHSDPADATAFOR
PRIMARYCELL

CellThroughputinWBTS
(WBTS)

M5002C127

ACKNOWLEDGEDMCHSDPADATAFOR
SECONDARYCELL

CellThroughputinWBTS
(WBTS)

M5000C436

MCHSDPADATADISCARDEDINMAC-D
PDUS

HSPAinWBTS(WBTS)

M5000C435

MCHSDPADATARECEIVEDINMAC-DPDUS HSPAinWBTS(WBTS)

M5002C128

INALMCHSDPADATAFORPRIMARYCELL

CellThroughputinWBTS
(WBTS)

M5002C129

ORIGINALMCHSDPADATAFOR
SECONDARYCELL

CellThroughputinWBTS
(WBTS)

M1006C306

RADIOBEARERCONFIGURATIONFORMCHSDPAATTEMPT

RRCsignalling(RNC)

M1006C308

RADIOBEARERCONFIGURATIONFORMCHSDPAFAILED

RRCsignalling(RNC)

M1006C307

RADIOBEARERCONFIGURATIONFORMCHSDPASUCCESSFUL

RRCsignalling(RNC)

M1001C745

UESUPPORTFORHSDSCHCLASS29OR
30

ServiceLevel(RNC)

M1001C746

UESUPPORTFORHSDSCHCLASS31OR
32

ServiceLevel(RNC)

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table88:Newparameterslistsparametersintroducedwiththisfeature.
Table88

Full name

Issue:01ADRAFT

Newparameters

Abbreviated name

Managed
object

AMRLCmaximumbuffer
AMRLCMaximumBufferUE1500
allocationforUEcapability1500

RNRLC

AMRLCmaximumbuffer
AMRLCMaximumBufferUE1800
allocationforUEcapability1800

RNRLC

AMRLCmaximumbuffer
AMRLCMaximumBufferUE2550
allocationforUEcapability2550

RNRLC

AMRLCmaximumbuffer
AMRLCMaximumBufferUE2300
allocationforUEcapability2300

RNRLC

DN09146788

137

Telecomfeatures

RU50FeatureDescriptionsandInstructions

Table89:Modifiedparameterslistsparametersmodifiedbythisfeature.
Table89

3.1.1.6

Modifiedparameters

Full name

Abbreviated name

Managed
object

RNCOptions

RncOptions

RNC

DualBandHSDPAEnabled

DBandHSDPAEnabled

WCEL

DCHSDPAEnabled

DCellHSDPAEnabled

WCEL

SectorIdentifier

SectorID

WCEL

Frametimingoffsetofacell

Tcell

WCEL

DRRCconnectionsetupfor
HSDPAlayerenhancements

DirectedRRCForHSDPALayerEnhanc

RNMOBI

MaximumbitrateofNRT
MAC-dflow

MaxBitRateNRTMACDFlow

RNHSPA

CQIfeedbackcycle

CQIfeedback

RNC

CQIFeedbackCycleforCPC
NRT2msTTI

N2msCQIFeedbackCPC

RNHSPA

CQIFeedbackCycleforCPC
NRT10msTTI

N10msCQIFeedbackCPC

RNHSPA

MAC-hstransmittingwindow
size

MAChstxwindowsize

RNC

T1timer

T1

RNC

AMRLCmaximumbuffer
allocationforUE

AMRLCMaximumBufferUE

RNRLC

Sales information
Table90

Salesinformation

BSW/ASW SW component License control in network element


ASW

138

HSPA

RNCLK

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Transmissionandtransportfeatures

4 Transmission and transport features


4.1 RAN2913: Local and Remote IP Traffic Capturing
4.1.1 Description of RAN2913: Local and Remote IP Traffic
Capturing
Introduction to the feature
RAN2913:LocalandRemoteIPTrafficCapturingfeatureallowsthecaptureofingress
andegressIPtrafficoftheC-plane,U-plane,M-planeorS-planetrafficforpostanalysis.
ItusesaWebinterfaceforconfigurationandcapturefileretrieval.ThroughWeb
interface,itispossibletoselectthelayer3internalmeasurementpoints.Inaddition,the
captureoftheU-planetrafficcanbeexcludedtomaximizecapturingduration.

4.1.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
ThisfeaturebenefitstheoperatorbyreducingtheOPEX.Itallowstheoperatorto
remotelycapturedtheBTStrafficforfastertroubleshootingandavoidingsitevisitsto
retrievetransportcapturefiles,savingtime,cost,andeffort.

4.1.1.2

Requirements
Software requirements
Thefollowingtablelistssoftwarerequiredforthisfeature.
Table91

Softwarerequirements

RAS
release

Flexi Direct IPA-RNC

mcRNC

OMS

Flexi BTS

RU50EP1

Supportnot
required

Supportnot
required

Supportnot
required

Notplanned WL9.1

Supportnot
required

Flexi Lite
BTS

Flexi 10 BTS

NetAct

MSC

SGSN

MGW

UE

WN9.1

NetAct8EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
ThisfeaturerequiresFlexiMultiradioSystemModuleFSMForFlexiLiteBTSWCDMA.

Issue:01ADRAFT

DN09146788

139

Transmissionandtransportfeatures

4.1.1.3

RU50FeatureDescriptionsandInstructions

Functional description
TheRAN2913:LocalandRemoteIPtrafficCapturingfeatureallowsthecapturingof
BTSbackhaulinterfaces'IPpacketinformationatdifferentcapturepointsinsidethe
trafficpathoftheBTS.

ThisfeaturespecifiescapturingonIPlayer,thereforeLayer2informationand
protocol,suchasEthernetheaders,Ethernetslowprotocols,orARParenot
captured.
ItextendsthetroubleshootingcapabilitiesoftheBTSbycapturingtheBTStrafficlocally
onsiteandbycapturingtheBTStrafficremotelybyNetworkOperationCenter,seeIP
trafficcapturingsetup.
Figure8

IPtrafficcapturingsetup
NetAct
Local Access

BTS
RNC
IPsec
GW

Transport Network

IPsec
GW

ThisfeatureusesaWebinterfaceforconfigurationforhighreliabilitytoselect
measurementpoint,configureoutputport(on-site)orinitiatefiletransfer.Thestreaming
outputisavailableonlytoaMACentityinthesameL2broadcastdomainastheselected
BTSEthernetinterface.TheWebinterfaceisrobustcanoperateeveninmanyfaulty
conditionsoftheBTS,inwhichtheremoteconnectiontoSiteElementManagerisnot
operative.ThroughWebinterfaceitispossibletoselecttheLayer3internal
measurementpoints.Additionally,thecaptureoftheU-planetrafficcanbeexcludedto
maximizecapturingduration.
CapturingofIPtrafficissupportedintwodifferentways:

StreamingofthecapturedIPpacketstoaon-siteconnectedlaptoporstorage
device.
Capturingintoalibpcapfilewhichcanbedownloadedvialocalorremote
connection.Thelibpcapfileformatisthemaincapturefileformatusedin
TcpDump/WinDump,Wireshark/TShark,snort,andmanyothernetworkingtools.

ThefeatureallowsthecapturingoftheBTSbackhaulinterfaces'IPpacketinformation
(ingressandegressIPtraffic)atdifferentcapturepointsinsidethetrafficpathoftheBTS.
Thecapturepointsare:

140

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Transmissionandtransportfeatures

AIPtrafficto/fromtheBTS.AtthiscapturepointthetrafficiscapturednonfragmentedandIPsecdecrypted(ifinuse).TLS-encryptedM-planeisstillencrypted.
IfTLSisnotinuse,M-planeiscontainedunencryptedordecrypted(incaseofIPsec
inuse).Atthiscapturepointdownlinktrafficisnotfilteredbythesystemfirewall,
uplinktraffichasalreadypassedit.
BIPtrafficto/fromtheBTSandSSEcapturedatthetransportnetworkinterfaces.At
thiscapturepointthetrafficiscapturedfragmentedandencrypted(ifinuse).

Atallofthesecapturepoints,trafficiscapturedinbothingressandegressdirection.
EspeciallycapturingatpointsAsimplifiesthetroubleshootingsinceitallowsaccessing
thedecryptedtraffic.Thecapturingisindependentoftheusedlayer2protocol(for
exampleEthernet,IP/ML-PPP).
AtcapturepointsAandB,theuser-planepayload(suchasdatabeyondtheUE
TCP/UDPheadersterminatingandoriginatingattheUE)ofunencryptedordecrypted
packetsiscompletelystrippedofffromthecapturedpackets.
AtcapturepointB,theencryptedpartofpacketscipheredwithIPsec("innerpacket")are
strippedofffromthecapturedpackets,theIPheaderofthe"outerpacket"uptotheESP
headeroftheinnerpacketiscaptured.TheESPheaderisstillcapturedtohelpin
identifyingIPseccustomerissues.
Itispossibletocompletelyexcludethecapturingofenduserplanepackets(headers).
AllotherpacketsofIPbasedprotocols(forexampleICMP,TWAMP)arealwayscaptured
ifIPtrafficcapturingisongoing.AtallcapturepointstheoriginalIPpackets(allthe
portionpacketbeforetheIPheaderisstrippedoffbeforethecapturepointandthe
portionpacketfromtheIPheaderonwardsispreserve)areconveyedunmodifiedtotheir
destination.Throughoutacapturingsession,capturingispossibleatoneofthecapture
points.Capturingatmultiplecapturepointsisnotsupported,seeCapturepointsinBTS.
Figure9

CapturepointsinBTS

IP/MLPPP
termination

Fragment
Reassembly

IPsecGateway
Function
Fragment
Reassembly

O&M
Function

SSL/TLS

BaseStation

TDM
Interfaces

Transport
Ethernet
Interface(s)
OtherBaseStation
Functions
(BasebandRadio)

L2Switching
Function
IP LayerCapturePoints

Capturingmechanismsummarizesthecapturingmechanism,theprovisioningofthe
localpacketstreamandthelibpcapfilecreationandprovisioning:

Issue:01ADRAFT

DN09146788

141

Transmissionandtransportfeatures

Figure10

RU50FeatureDescriptionsandInstructions

Capturingmechanism
2.

BTS
captureto
libpcapfile

requestmirroringfile
3.

libpcapfile

file

capturinghistory

RemoteUser

tur

ing

2.

tc
ap

libpcapfile

re

qu

es

Mirroredfullpacketsresp.leadingn
bytes(UP) plustiminginformation
3.

orstreaming

LocalEthernet
Port

BTS
functions
capturepoint

Laptop

capturedfullpacketsresp.
headersonly(UP)

packettiming
information
Packetstream(ingressandegress)

Thefeatureincludesthecapabilitytomirrortrafficintoalibpcapfileandfetchit
compressedandoptionallypasswordprotectedviaremoteconnection.Alternatively,the
trafficcanbemirroredtothelocalmanagementport(LMP)orafreetransportEthernet
port(ifavailableontheBTS).Foralloftheseoutputoptions,mirroringofuserplaneis
limitedtotheheaderinformation.UE-levelpayloadbeyondtheUE-levelTCP/UDP
headersisnevercaptured.Themirroringofuserplanetrafficcanbeenabled/disabled
completelyviatheWebinterface.
Remotetrafficcapturingeasestheactivitiesofmaintenanceengineersandavoidsextra
sitevisitstoretrievetransportcapturefiles,savingtime,costandeffort.Forremotetraffic
capturing,thesizeofthefileisfixedat150MBbeforecompressionand40MBforthe
compressedlibpcapfile.Thisfixedfilesizeensurestheabout2.5minutestocapture
dataforasingleUE(peak-throughput,IPv4,withheaderuptotheUETCPlevel,no
payloadbytes,andnotmorethan100Mbps).
LocaltrafficcapturingcancollectBTStrafficoveraperiodofuptoseveraldaysinorder
toinvestigateunexpectedBTSbehavior,supportbugfixingandcustomertrials.
Thisfeatureprovidesthemeanstocollectthetransportcapturefilesasoftenasneeded
sothattheycanbeincludedtotheticket,contributingtoreducetheticketresolving
times.Thefeatureprovidesarobustandsimpleconfigurationinterfacetoconfigurethe
IPtrafficcapturingeveninfaultorcongestionsituations.
IncaseonlyasingleUEisconnectedtotheBTS,thisfeatureallowsmaintenance
engineerstocapturethetransportIPtrafficrelatedtothatsingleUEataBTSinthefield;
itallowsthemtocalculatetheKPIs,provecorrectBTSbehaviorandevaluateactual
networkperformance.Itenablestheremoteanalysisoffaultsandcontributestoa
quickersolutionofthosefaults.

4.1.1.4

System impact
Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

142

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Transmissionandtransportfeatures

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


System performance
IPtrafficcapturingiscompetingwithnormalBTSservicesforthesameresources.Soit
mighthappenthattherearenotenoughresourcestoconcurrentlyrunIPtrafficcapturing
andnormalBTSservices.Thiscouldhappen

incaseofalackofresourcesinthepacketbufferswhichpreventthecopyoperation
ofthecapturedpacketsincaseoflocalstreaming
incaseofalackofallocatedprocessingtimeforthecapturingprocess
ifthedatarateofstreamedIPtrafficcapturingdataexceedstheavailabledatarate
ontheLocalEthernetPort

Ifeitherofthesecaseshappens,theIPtrafficcapturingmaydropcapturingpackets(for
exampleIPpacketsarenotcapturedorstreamed).TheuserisNOTnotifiedaboutthis.
System capacity
OnFlexiMultiradio10HW,theoutputdatarateoflocalstreamingofIPcapturingdatavia
theNELocalManagementPortislimitedtoFastEthernetsincetheLocalManagement
PortdoesnotsupportGigabitEthernet.

4.1.1.5

RAN2913: Local and Remote IP Traffic Capturing management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Table93

Relatedexistingalarms

Alarm ID

Alarm name

Meaning of the alarm

7665

Basestation
TransmissionAlarm

ThebasestationiscurrentlycapturingIPtraffic
towardsalocalportorintoafileonthebase
station

Measurements and counters


Therearenomeasurementsandcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Therearenoparametersrelatedtothisfeature.

Issue:01ADRAFT

DN09146788

143

Transmissionandtransportfeatures

4.1.1.6

RU50FeatureDescriptionsandInstructions

Sales information
Table94

Salesinformation

BSW/ASW

SW component

License control in network


element

BSW

4.2 RAN2243: Performance Monitoring Based on ETH


Service OAM
4.2.1 Description of RAN2243: Performance Monitoring Based
on ETH Service OAM
Introduction to the feature
ThisfeatureenhancestheRAN1880:EthernetOAMinBTSfeaturetoprovide
performancemonitoringfunctionalityusingEthernetServiceOAMframes.
PerformancemonitoringaccordingtotheITU-TY.1731providesEthernetperformance
measurementbetweenMaintenanceEndPoints(MEPs)thatareplacedattheedgesof
eachmaintenancedomain.TheperformancemonitoringfeaturesupportstheFrame
LossandFrameDelayMeasurements.TheFrameDelayMeasurementsareshowed
withmaximum,minimumandaveragevaluesofthemeasurementperiodoffifteen
minutestoprovidetheinformationabouttheFrameDelayVariation.

4.2.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
Thisfeatureprovidesthemaintenancehierarchystructurewheretheperformance
measurementsareperformedbetweentheMEPsofthesamegradeofhierarchy.
DifferentgradesofhierarchymonitordifferentEthernetnetworksegmentstofindthe
problemsmoreefficiently.

4.2.1.2

Requirements
Software requirements
Table95:Softwarerequirementslistssoftwarerequiredforthisfeature.

144

RAS

Flexi Direct

IPA-RNC

mcRNC

RU50

Notplanned

Supportnot Supportnot Notplanned


required
required

DN09146788

Flexi Direct RNC OMS

Flexi BTS

OMS3.01)

WN9.0

OMS3.12)

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table95

Transmissionandtransportfeatures

Softwarerequirements

Flexi Lite Flexi 10


BTS
BTS

NetAct

WL9.1

NetAct8EP11) Supportnot Supportnot Supportnot Supportnot


required
required
required
required
NetAct8EP22)

WN9.1

MSC

SGSN

MGW

UE

1)RU50
2)RU50EP1

Hardware requirements
ThisfeaturerequiresoneofthefollowingFlexiMultiradioBTSTransportSub-Modules:

FlexiFTIA
FlexiFTJA
FlexiFTIB
FlexiFTLB
FlexiFTFB

ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradio
SystemModuleFSMForFlexiLiteBTSWCDMA.

4.2.1.3

Functional description
Functional overview
ThisfeatureenhancestheRAN1880:EthernetOAMinBTSfeaturetoprovide
performancemonitoring(PM)functionalityusingEthernetServiceOAMframes.The
EthernetOAMperformancemonitoringfunctionsaredefinedbyITU-TY.1731standard.
TheITU-TY.1731standardsetsupanL2networkonhierarchy,whichconforms
maintenancedomains.Differentmaintenancedomainsareassignedtothecustomer,
serviceprovidersoroperators.TheedgesofeachdomainareMaintenanceEndPoints
(MEPs).TheportswithindomainsareMaintenanceIntermediatePoints(MIPs).The
maintenancehierarchyallowstomonitordifferentsegmentsoftheEthernetnetwork,
whichareundertheresponsibilityofdifferenthierarchydepartments.Thesegmentation
ofmaintenancedomainssimplifiesfindingtheproblemsontheL2Ethernetnetwork.
Whentheperformancemonitoringfeatureisnotactivated,theL2(Ethernet)
performancemonitoringfunctionsarenotpossibletobeperformed.

Issue:01ADRAFT

DN09146788

145

Transmissionandtransportfeatures

Figure11

RU50FeatureDescriptionsandInstructions

PerformancemonitoringusingEthernetServiceOAMframes
EthPM
EthPM
EthPM

MEP

MEP

MEP

MEP

BTS

Eth

Ethernet

Ethernet

Theperformancemonitoringfunctionssupportedbytheperformancemonitoringfeature
areFrameLossandFrameDelayMeasurement.Therearedifferentmodesofeach
measurement.Thesemodesarepresentedbeneath:

FrameLossMeasurement

dual-ended(ETH-CCM)
single-ended(ETH-LMM/ETH-LMR)

FrameDelayMeasurement(ETH-DM)

One-wayDelayVariation
Two-wayDelay

ThisfeatureprovidesalsoconfigurablethresholdsfortriggeringalarmsforFrameLoss
MeasurementandFrameDelay/DelayVariationMeasurement.Thresholdsare
configurablepermeasurementsession.
TheFrameLossMeasurementsareobtainedbymeansofcountersforreceivedand
transmitteddataframesbetweenapairofMEPs.Thesecountersareprovidedbythe
performancemonitoringfeature.TheFrameLossMeasurementcanbecalculatedfor
eachdirection.Far-endandnear-endFrameLossMeasurementsaresupported.The
BTSsupportsbothkindsofFrameLossMeasurements.Theoperatorconfiguresthe
measurementnature.

g
4.2.1.4

Notethatmesh,chain,tree,andcircletopologyshouldhavepoint-to-point
EthernetconnectionsbetweenMEPstoperformaccurateFrameLoss
Measurement,whereastherearenosimilarconditionsforFrameDelay/Delay
VariationMeasurement.

System impact
Interdependencies between features
Thisfeaturedoesnotneedaseparatelicense.
Thisfeatureneedsthelicensesoffeatures:

146

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Transmissionandtransportfeatures

RAN1880:EthernetOAMinBTS
RAN1900:IPTransportNetworkMeasurement

Thisfeatureneedstheactivationoffeature:

RAN1880:EthernetOAMinBTS

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on network and network element management tools


Thisfeaturehasanimpactonnetworkelementmanagementtoolsasbeneath:

newalarms/faultssupportedbyNetAct
newcounterssupportedbyNetAct
newparameterssupportedbyNetAct

Impact on system performance and capacity


Thisfeaturehasanimpactonsystemperformanceandcapacityasbeneath:

TheServiceOAMcanconsumesignificantamountofbandwidth,particularlywhen
pro-activefunctions(ETH-CC)areactivatedsimultaneouslyandusinghigh
transmissionrates.However,theServiceOAMperformancemonitoringfunctionsare
notmeanttousehightransmissionrates.Thefeaturestandardrecommends10fps.
Theusageofthesefunctionsmustbeconfinedthen.
ThecapacitydemandsforServiceOAMperformancemonitoringfunctionsisusually
notsignificant.Withdefaultsettings,eachETH-CCMmeasurementconsumesless
than1kbps,whereasETH-LMandETH-DMmeasurements-lessthan0.1kbps.
Thedefaultintervalvaluesformeasurementsaregivenbelow:

4.2.1.5

ETH-CCMmeasurement-1s
ETH-LMmeasurement-10s
ETH-DMmeasurement-10s

Atmaximum(notrecommended),ETH-CCMFrameLossMeasurementcan
consume312kbpsatEthernetlayerwhen3.33msintervalisconfigured.

RAN2243: Performance Monitoring Based on ETH Service OAM


management data
Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Faults
Table96:Newfaultslistsfaultsandreportedalarmsintroducedwiththisfeature.

Issue:01ADRAFT

DN09146788

147

Transmissionandtransportfeatures

RU50FeatureDescriptionsandInstructions

Table96

Newfaults

Fault ID

Fault name

Reported alarms

61635

Framelossthreshold
exceededonmac$m

7665BASESTATIONTRANSMISSIONALARM

61636

Twowaydelay
thresholdexceededon
mac$m

7665BASESTATIONTRANSMISSIONALARM

61637

OneWaydelayvariation
thresholdexceedon
mac$m

7665BASESTATIONTRANSMISSIONALARM

Theperformancemonitoringfaultsarepresentedasalarmsat:

OMS Fault Management


NetAct Monitor

Measurements and counters


Table97:Newcounterslistscountersintroducedwiththisfeature.
Table97

148

Newcounters

Counter ID

Counter name

Measurement

M5141C0

soamIngressFramesLost

M5141(FrameLoss)

M5141C1

soamIngressTotalFrames

M5141(FrameLoss)

M5141C2

soamNearEndFrameLossRatio

M5141(FrameLoss)

M5141C3

soamEgressFramesLost

M5141(FrameLoss)

M5141C4

soamEgressTotalFrames

M5141(FrameLoss)

M5141C5

soamFarEndFrameLossRatio

M5141(FrameLoss)

M5142C0

soamTwowayAverageDelay

M5142(FrameDelay)

M5142C1

soamTwowayMaxDelay

M5142(FrameDelay)

M5142C2

soamTwowayMinDelay

M5142(FrameDelay)

M5143C0

soamOnewayNearEnDelayVariation

M5143(FrameDelay)

M5143C1

soamOnewayFarEndDelayVariation

M5143(FrameDelay)

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Transmissionandtransportfeatures

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table98:Newparameterslistsparametersintroducedwiththisfeature.
Table98

Newparameters

Full name

Abbreviated name

Managed object

EnableserviceOAMperformance
monitoring

enableSoamPm

IPNO

Flagforenabling/disablingSOAM
framelossmeasurement

enableSoamFrameLossMeas

OAMFLM

MACaddressoftheframeloss
measurementremoteMEP

macAddr

OAMFLM

ServiceOAMframelossalarm
threshold

soamFrameLossAlarmThres

OAMFLM

ServiceOAMframeloss
measurementinterval

soamFrameLossMeasInt

OAMFLM

ServiceOAMFrameloss
MeasurementMode

soamFrameLossMeasMode

OAMFLM

EnableserviceOAMdelay
measurement

enableSoamDelayMeasure

OAMDM

MACaddressofthedelay
measurementremoteMEP

macAddr

OAMDM

ServiceOAMonewaydelay
variation15malarmthreshold

soamDelayAlarmThresOneway

OAMDM

ServiceOAMtwo-waydelay1min
alarmthreshold

soamDelayAlarmThresTwoway

OAMDM

Serviceoamdelaymeasurement
PDUlength

soamDmmPduSize

OAMDM

ServiceOAMframedelay
measurementinterval

soamFrameDelayMeasInt

OAMDM

Commands
Therearenocommandsrelatedtothisfeature.

Issue:01ADRAFT

DN09146788

149

Transmissionandtransportfeatures

4.2.1.6

RU50FeatureDescriptionsandInstructions

Sales information
Table99

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

TRSLK

4.2.2 Activating RAN2243: Performance Monitoring Based on


ETH Service OAM
Purpose
Thepurposeofthisprocedureistoactivatetheperformancemonitoring(PM)feature.
Before you start
Theactivatingproceduredoesnotcausedowntime.
Theactivatingprocedurecanbeperformedatanytimeoftheday.
Theactivatingproceduredoesnotneedaseparatelicense.
Theactivatingprocedureneedsthelicensesoffeatures:

RAN1880:EthernetOAMinBTS
RAN1900:IPTransportNetworkMeasurement

Theactivatingprocedureneedstheactivationoffeature:

RAN1880:EthernetOAMinBTS

TheactivatingproceduretoactivatetheEthernetServiceOAMPMontheBTSneeds:

BTS Site Manager


NetAct Configuration Managementsoftware

TheactivatingproceduretoconfigurethePMmeasurementsessionsontheBTSneeds:

BTS Site Manager


NetAct Configuration Managementsoftware

TheactivatingproceduretostartthemeasurementsatOMSneeds:

RNW Measurement Management


NetAct Administration of Measurements

TheactivatingproceduretomonitorthePMmeasurementsessionsdataneeds:

BTS Site Manager


NetAct Performance Manager

Theactivatingprocedureconsistsofthreeprocedures:

150

activatingEthernetServiceOAMPM
activatingFrameLossMeasurementsession

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

4.2.2.1

Transmissionandtransportfeatures

activatingFrameDelayMeasurementsession

Activating Ethernet Service OAM PM


Purpose
ThisprocedureisusedtoactivatetheEthernetServiceOAMPMontheBTS.
Before you start

Thisprocedureneedstheseactionstobeperformed:

DeterminetheMaintenanceDomainandMaintenanceAssociation.
DeterminetheMaintenanceEndPoint(s)withingivenMaintenance
Association.
DeterminetheEthernetServiceOAMperformancemonitoringswitch.

Theseactionshappenwhenthepreconditionsarenotmet:

TheEthernetServiceOAMPMfeaturescanbesetbuttheyarenot
operable.
ThemessagesfromtheremoteMEPsarediscarded.
ThePMmeasurementsarenotgenerated.

Open the BTS Site Manager.

TheNetAct Configuration Managementsoftwarecanbeused


alternatively.

Turn on the Ethernet Service OAM PM feature on the BTS.


Theactionsofcurrentstepare:
a)
b)
c)
d)

OpentheTRS HardwarefromtheView bar.


OpentheEthernet Service OAMmenu.
MarkontheEthernet Service OAM in usecheckbox.
MarkontheEthernet Service OAM performance monitoring in usecheckbox.

TheactivationmustbeconfirmedusingtheSendbuttonwhenusingthe
BTS Site Manager.

Expected outcome
TheEthernetServiceOAMPMhasbeenactivatedsuccessfullyontheBTS.
TheEthernetServiceOAMPMstatisticsarecleared.
TheBTSonlyanswerstotheincomingPMmessagesfromtheremoteMEPs.
ThePMmeasurementsessionsaresupportedontheBTS:

Issue:01ADRAFT

FrameLossMeasurementsession
FrameDelayMeasurementsession

DN09146788

151

Transmissionandtransportfeatures

RU50FeatureDescriptionsandInstructions

ThePMmeasurementsessionswithactivestatusareautomaticallyrestartedonthe
BTS.

ThePMmeasurementsessionshavetobefurtheractivatedseparatelyonthe
BTS.

ThepropermeasurementshavetobestartedatOMS.Themeasurementsare:

g
4.2.2.2

M5141-SoamFrameLossstatistics
M5142-SoamTwoWayDelayStatistics
M5143-SoamOneWayDelayVariationStatistics

TheoperatorcansettheBTSthresholdsfortriggeringalarms.
ThePMthresholdsaresetontheBTSforeachmeasurementseparately.

Activating Frame Loss Measurement session


Purpose
ThisprocedureisusedtoactivatetheFrameLossMeasurementsessionontheBTS.
ThisprocedureconsistsalsoofthesteptostarttheassociatedmeasurementatOMS.
Before you start
ThisprocedureneedstheactivationoftheEthernetServiceOAMPMontheBTS.
TheFrameLossstatisticsarefifteen-minutestatistics.

TheFrameLossMeasurementsessionatsingle-endedmodecannotbe
activatedwhen:

TheFrameLossMeasurementsessionatdual-endedmodecannotbe
activatedwhen:

152

TheMaintenanceAssociationhasmorethanoneremoteMEP.
TheycausethetotalegressofServiceOAMframestosurpass1000fps.
TherearemeasurementsunderthesameMEPwiththesamemeasurement
mode.

TheMaintenanceAssociationhaszeroormorethanoneremoteMEP.
TheMaintenanceAssociationdoesnothavetheETH-CCactivated.
TherearemeasurementsunderthesameMEPwiththesamemeasurement
mode.

Open the BTS Site Manager.


TheNetAct Configuration Managementsoftwarecanbeused
alternatively.

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Transmissionandtransportfeatures

Turn on the Frame Loss Measurement session on the BTS.


Theactionsofcurrentstepare:
a)
b)
c)
d)

OpentheTRS HardwarefromtheView bar.


OpentheEthernet Service OAMmenu.
OpentheNewdrop-downmenuandcreateFrame loss measurement session.
MarkontheFrame loss measurement in usecheckbox.

Determine the Frame Loss Measurement session parameters.


TheFrameLossMeasurementsessionneedstoconfiguretheparameters:

MAC addressofremoteMEP
Frame loss measurement mode
Frame loss transmission interval(forsingle-endedmeasurements)
Frame loss alarm ratio threshold
MEPwithhereditaryVLANIDandPCPfromMaintenanceAssociation

TheactivationmustbeconfirmedusingtheSendbuttonwhenusingthe
BTS Site Manager.

Monitor the measurement session using the BTS Site Manager.


Expected outcome
TheFrameLossMeasurementsessionhasbeenactivatedontheBTS.
WhenFrameLossMeasurementsessionhasbeenactivatedontheBTSthen:

Start the Soam Frame Loss statistics measurement (M5141) at OMS.


Thisstepmustbeperformedusing:

TheBTSpurgesthecurrentFrameLossstatistics.
TheBTSstartstomeasuretheFrameLossstatisticsagain.
TheBTSmeasurestheFrameLossRatioeveryfifteenminutes.
TheBTSsendsthemeasurementdatatotheOMSeveryhour.
TheBTSsendstheCCMmessagestotheremoteMEP(dual-endedmode).
TheBTSsendstheLMMmessagestotheremoteMEP(single-endedmode).
TheLMRmessagesaretransmittedfromtheremoteMEP(single-endedmode).
TheFrameLossalarmoccurswhenthethresholdhasbeenreached.

RNW Measurement Management


NetAct Administration of Measurements

TheOMSdoesnotstorethemeasurementdatatodatabase.
TheOMStransfersthemeasurementdatafromtheBTStotheNetAct.
Expected outcome
TheSoamFrameLossstatisticsmeasurementhasbeenstartedatOMS.

Issue:01ADRAFT

DN09146788

153

Transmissionandtransportfeatures

RU50FeatureDescriptionsandInstructions

TheOMSsendsthemeasurementdatatotheNetActtenminutesaftereveryhour.
6

Monitor the measurement session using the NetAct Performance Manager.


Thisstepmustbeperformedafterthepropertime.
TheBTSsendsthemeasurementdatatotheOMSeveryhour.
Themeasurementdatacomprisesfourfifteen-minutestatistics.
TheOMSsendsthemeasurementdatatotheNetActtenminutesafter.
Themeasurementdatacanbemonitoredthenusing:

NetAct Performance Manager

Expected outcome
TheFrameLossMeasurementsessionhasbeenactivatedontheBTS.

4.2.2.3

Activating Frame Delay Measurement session


Purpose
ThisprocedureisusedtoactivatetheFrameDelayMeasurementsessionontheBTS.
ThisprocedureconsistsalsoofthestepstostarttheassociatedmeasurementatOMS.
Before you start
ThisprocedureneedstheactivationoftheEthernetServiceOAMPMontheBTS.
TheOne-wayFrameDelayVariationstatisticsarefifteen-minutestatistics.
TheTwo-wayFrameDelaystatisticsareone-minuteandfifteen-minutestatistics.

TheFrameDelayMeasurementsessioncannotbeactivatedwhen:

Thereare80FrameDelayMeasurementsessionswhicharealready
created.
TheycausethetotalegressofServiceOAMframestosurpass1000fps.
TheFrameDelayMeasurementsessionwiththesameremoteMACwas
alreadyactivated.

Open the BTS Site Manager.


TheNetAct Configuration Managementsoftwarecanbeused
alternatively.

Turn on the Frame Delay Measurement session on the BTS.


Theactionsofcurrentstepare:
a) OpentheTRS HardwarefromtheView bar.
b) OpentheEthernet Service OAMmenu.

154

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Transmissionandtransportfeatures

c) OpentheNewdrop-downmenuandcreateDelay measurement session.


d) MarkontheDelay measurement in usecheckbox.
3

Determine the Frame Delay Measurement session parameters.


TheFrameDelayMeasurementsessionneedstoconfiguretheparameters:

MAC addressofremoteMEP
Delay measurement transmission interval
Delay measurement message PDU size
One-way delay variation 15 min alarm threshold
Two-way delay measurement 1 min alarm threshold
MEPwithhereditaryVLANIDandPCPfromMaintenanceAssociation

TheactivationmustbeconfirmedusingtheSendbuttonwhenusingthe
BTS Site Manager.

Monitor the measurement session using the BTS Site Manager.


Expected outcome
TheFrameDelayMeasurementsessionhasbeenactivatedontheBTS.
WhenFrameDelayMeasurementsessionhasbeenactivatedontheBTSthen:

Start the Soam Two Way Delay Statistics measurement (M5142) at OMS.
Thisstepmustbeperformedusing:

TheBTSpurgesthecurrentFrameDelaystatistics.
TheBTSstartstomeasuretheFrameDelaystatisticsagain.
TheBTSsendsthemeasurementdatatotheOMSeveryhour.
TheBTSsendstheDMMmessagestotheremoteMEP.
TheDMRmessagesaretransmittedfromtheremoteMEP.
TheFrameDelayalarmsoccurwhenthethresholdshavebeenreached.

RNW Measurement Management


NetAct Administration of Measurements

TheOMSdoesnotstorethemeasurementdatatodatabase.
TheOMStransfersthemeasurementdatafromtheBTStotheNetAct.
Expected outcome
TheSoamTwoWayDelayStatisticsmeasurementhasbeenstartedatOMS.
TheOMSsendsthemeasurementdatatotheNetActtenminutesaftereveryhour.

Issue:01ADRAFT

DN09146788

155

Transmissionandtransportfeatures

RU50FeatureDescriptionsandInstructions

Start the Soam One Way Delay Variation Statistics measurement (M5143) at
OMS.
Thisstepmustbeperformedusing:

RNW Measurement Management


NetAct Administration of Measurements

TheOMSdoesnotstorethemeasurementdatatodatabase.
TheOMStransfersthemeasurementdatafromtheBTStotheNetAct.
Expected outcome
TheSoamOneWayDelayVariationStatisticsmeasurementhasbeenstartedat
OMS.
TheOMSsendsthemeasurementdatatotheNetActtenminutesaftereveryhour.
7

Monitor the measurement session using the NetAct Performance Manager.


Thisstepmustbeperformedafterthepropertime.
TheBTSsendsthemeasurementdatatotheOMSeveryhour.
Themeasurementdatacomprisesfourfifteen-minutestatistics.
TheOMSsendsthemeasurementdatatotheNetActtenminutesafter.
Themeasurementdatacanbemonitoredthenusing:

NetAct Performance Manager

NetActdoesnotsupportone-minutestatistics.
Expected outcome
TheFrameDelayMeasurementsessionhasbeenactivatedontheBTS.

4.2.3 Verifying RAN2243: Performance Monitoring Based on ETH


Service OAM
Purpose
ThepurposeofthisprocedureistoverifyactivationofPMfeature.
Before you start
Theverifyingproceduredoesnotcausedowntime.
Theverifyingprocedurecanbeperformedatanytimeoftheday.
TheverifyingprocedureneedsthePMmeasurementsessionsactivationontheBTS:

FrameLossMeasurementsession(makesurethatthereareanylostframes)
FrameDelayMeasurementsession

TheverifyingproceduretostartthemeasurementsatOMSneeds:

156

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Transmissionandtransportfeatures

RNW Measurement Management


NetAct Administration of Measurements

TheverifyingproceduretomonitorthePMmeasurementsessionsdataneeds:

BTS Site Manager


NetAct Performance Manager

TheverifyingproceduretomonitorthePMalarmsneeds:

BTS Site Manager


NetAct Monitor
OMS Fault Management

TheFrameLossstatisticsarefifteen-minutestatistics.
TheOne-wayFrameDelayVariationstatisticsarefifteen-minutestatistics.
TheTwo-wayFrameDelaystatisticsareone-minuteandfifteen-minutestatistics.

Open the RNW Measurement Management.


TheNetAct Administration of Measurementsapplicationcanbeused
alternatively.

Start the proper measurements at OMS.


TheFrameLossMeasurementisM5141measurement.
TheTwo-wayFrameDelayMeasurementisM5142measurement.
TheOne-wayFrameDelayVariationMeasurementisM5143measurement.

TheOMSdoesnotstorethemeasurementdatatodatabase.
TheOMStransfersthemeasurementdatafromtheBTStotheNetAct.

Open the BTS Site Manager.

After one minute verify that the proper PM counters are greater than zero.
Thisstepmustbeperformedoneminuteaftermeasurementstart.
TheproperPMcountersare(whenperformingthecurrentstep):

Two-wayFrameDelayMeasurementcounters:

Issue:01ADRAFT

M5142C0-soamTwowayAverageDelay
M5142C1-soamTwowayMaxDelay
M5142C2-soamTwowayMinDelay

TheFrameDelaycountersmustbealwaysgreaterthanzeroatthepresent
moment.

DN09146788

157

Transmissionandtransportfeatures

RU50FeatureDescriptionsandInstructions

Themeasurementdataofeachminutecanbemonitoredonlyusing:

BTS Site Manager

Expected outcome
TheTwo-wayFrameDelaycountersaregreaterthanzero.

TheproperPMcountersarepresentedduringtheoneminutemeasurement.
TheproperPMcountersareupdatedafterthecompletionofoneminute
measurement.
5

Verify that the proper alarm has been raised when the threshold was reached.
Thisstepmustbeperformedoneminuteaftermeasurementstart.
Theproperalarmcanoccurfor(whenperformingthecurrentstep):

Two-wayFrameDelayMeasurement

Expected outcome
Theproperalarmhasbeenraisedwhenthethresholdwasreached.

Theproperalarmdoesnotoccurwhenthethresholdhasbeensettozero.
Theproperalarmoccursonlywhenthethresholdhasbeenreachedafter
theoneminutemeasurement.

g
g

TheproperalarmsarepresentedasfaultsattheBTS Site Manager.


TheproperalarmsarereportedfromtheBTStotheOMS/NetActpromptly.
Theproperalarmscanbemonitoredalsousing:

NetAct Monitor
OMS Fault Management

Further information
Theproperalarmsarecanceledwhenthethresholdsarenotreachedafterthenext
oneminutemeasurementfor:

Two-wayFrameDelayMeasurement

After fifteen minutes verify that the proper PM counters are greater than zero.
Thisstepmustbeperformedfifteenminutesaftermeasurementstart.
TheproperPMcountersare(whenperformingthecurrentstep):

FrameLossMeasurementcounters:

158

M5141C0-soamIngressFramesLost
M5141C1-soamIngressTotalFrames
M5141C2-soamNearEndFrameLossRatio

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

M5141C3-soamEgressFramesLost
M5141C4-soamEgressTotalFrames
M5141C5-soamFarEndFrameLossRatio

One-wayFrameDelayVariationMeasurementcounters:

g
g

Transmissionandtransportfeatures

M5143C0-soamOnewayNearEndDelayVariation
M5143C1-soamOnewayFarEndDelayVariation

TheTwo-wayFrameDelayMeasurementcounterscanbeverifiedagain.
TheFrameLosscountersaregreaterthanzeroonlywhenthereareanylost
frames.
TheFrameDelaycountersmustbealwaysgreaterthanzeroatthepresent
moment.

Themeasurementdataofeachminutecanbemonitoredonlyusing:

BTS Site Manager

Expected outcome
TheOne-wayFrameDelayVariationcountersaregreaterthanzero.
TheTwo-wayFrameDelaycountersaregreaterthanzero.
TheFrameLosscountersaregreaterthanzero.

TheproperPMcountersarepresentedduringthefifteenminutes
measurement.
TheproperPMcountersareupdatedafterthecompletionoffifteenminutes
measurement.
7

Verify that the proper alarm has been raised when the threshold was reached.
Thisstepmustbeperformedfifteenminutesaftermeasurementstart.
Theproperalarmcanoccurfor(whenperformingthecurrentstep):

One-wayFrameDelayVariationMeasurement
FrameLossMeasurement

Expected outcome
Theproperalarmhasbeenraisedwhenthethresholdwasreached.

Theproperalarmdoesnotoccurwhenthethresholdhasbeensettozero.

TheproperalarmsarepresentedasfaultsattheBTS Site Manager.

Issue:01ADRAFT

Theproperalarmsoccuronlywhenthethresholdshavebeenreachedafter
thefifteenminutesmeasurement.

DN09146788

159

Transmissionandtransportfeatures

RU50FeatureDescriptionsandInstructions

TheproperalarmsarereportedfromtheBTStotheOMS/NetActpromptly.
Theproperalarmscanbemonitoredalsousing:

NetAct Monitor
OMS Fault Management

Further information
Theproperalarmsarecanceledwhenthethresholdsarenotreachedafterthenext
fifteenminutesmeasurementfor:

One-wayFrameDelayVariationMeasurement
FrameLossMeasurement

Monitor the measurement session using the NetAct Performance Manager.


Thisstepmustbeperformedafterthepropertime.
TheBTSsendsthemeasurementdatatotheOMSeveryhour.
Themeasurementdatacomprisesfourfifteen-minutestatistics.
TheOMSsendsthemeasurementdatatotheNetActtenminutesafter.
Themeasurementdatacanbemonitoredthenusing:

NetAct Performance Manager

NetActdoesnotsupportone-minutestatistics.

Verify that the proper PM counters are greater than zero.


Expected outcome
TheOne-wayFrameDelayVariationcountersaregreaterthanzero.
TheTwo-wayFrameDelaycountersaregreaterthanzero.
TheFrameLosscountersaregreaterthanzero.

Expected outcome
TheFrameLoss/DelayMeasurementsessionshavebeenactivatedsuccessfully.

4.2.4 Deactivating RAN2243: Performance Monitoring Based on


ETH Service OAM
Purpose
Thepurposeofthisprocedureistodeactivatetheperformancemonitoring(PM)feature.
Before you start
Thedeactivatingproceduredoesnotcausedowntime.
Thedeactivatingprocedurecanbeperformedatanytimeoftheday.
Thedeactivatingprocedureneedsthatthefeaturehasbeenactivatedsuccessfully.

160

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Transmissionandtransportfeatures

ThedeactivatingproceduretodeactivatetheEthernetServiceOAMPM(BTS)needs:

BTS Site Manager


NetAct Configuration Managementsoftware

ThedeactivatingproceduretodeactivatethePMmeasurementsessions(BTS)needs:

BTS Site Manager


NetAct Configuration Managementsoftware

ThedeactivatingproceduretostopthemeasurementsatOMSneeds:

RNW Measurement Management


NetAct Administration of Measurements

Thedeactivatingprocedureconsistsofthreeprocedures:

4.2.4.1

deactivatingEthernetServiceOAMPM
deactivatingFrameLossMeasurementsession
deactivatingFrameDelayMeasurementsession

Deactivating Ethernet Service OAM PM


Purpose
ThisprocedureisusedtodeactivatetheEthernetServiceOAMPMontheBTS.
Before you start
ThisprocedureneedstheactivationoftheEthernetServiceOAMPMontheBTS.
Thisprocedurecanbeperformedbydisablethelicenseofoneofthefeatures:

RAN1880:EthernetOAMinBTS
RAN1900:IPTransportNetworkMeasurement

TheEthernetServiceOAMPMfeaturesarestoppedafteroneoftheactions:

TheEthernetServiceOAMPMhasbeendeactivated.
TheEthernetServiceOAMhasbeendeactivated.

Open the BTS Site Manager.

TheNetAct Configuration Managementsoftwarecanbeused


alternatively.

Turn off the Ethernet Service OAM PM feature on the BTS.


Theactionsofcurrentstepare:
a) OpentheTRS HardwarefromtheView bar.
b) OpentheEthernet Service OAMmenu.
c) UnmarktheEthernet Service OAM performance monitoring in usecheckbox.

Issue:01ADRAFT

DN09146788

161

Transmissionandtransportfeatures

RU50FeatureDescriptionsandInstructions

ThedeactivationmustbeconfirmedusingtheSendbuttonwhenusingthe
BTS Site Manager.
Expected outcome
TheEthernetServiceOAMPMhasbeendeactivatedsuccessfullyontheBTS.
TheBTSdiscardstheincomingPMmessagesfromtheremoteMEPs.
ThePMmeasurementsessionsarenotsupportedontheBTS.
ThePMmeasurementsessionsarestoppedontheBTSandPMalarmsarecanceled.
ThePMmeasurementsessionsactivationontheBTSdoesnothaveanyeffect.
TheFrameLoss/Delaystatisticsarenotclearedbuttheyarenotfurtherupdated.

ThepropermeasurementshavetobestoppedatOMS.Themeasurementsare:

g
4.2.4.2

M5141-SoamFrameLossstatistics
M5142-SoamTwoWayDelayStatistics
M5143-SoamOneWayDelayVariationStatistics

TheoperatorcanalsodeactivateasinglePMmeasurementsession.
TheaboveoperationcanbeperformedwithoutfullydeactivationofPMfeature.

Deactivating Frame Loss Measurement session


Purpose
ThisprocedureisusedtodeactivatetheFrameLossMeasurementsessionontheBTS.
ThisprocedureconsistsalsoofthesteptostoptheassociatedmeasurementatOMS.
Before you start
ThisprocedureneedstheactivationoftheFrameLossMeasurementsessiononthe
BTS.
ThisprocedureneedstheactivationoftheassociatedmeasurementatOMS.
Thisprocedurecanbeperformedbydisablethelicenseofoneofthefeatures:

TheFrameLossMeasurementsession(BTS)stopsafteroneoftheactions:

162

RAN1880:EthernetOAMinBTS
RAN1900:IPTransportNetworkMeasurement

TheFrameLossMeasurementsessionhasbeendeactivated.
TheEthernetServiceOAMPMhasbeendeactivated.
TheEthernetServiceOAMhasbeendeactivated.

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Transmissionandtransportfeatures

Open the BTS Site Manager.


TheNetAct Configuration Managementsoftwarecanbeused
alternatively.

Turn off the Frame Loss Measurement session on the BTS.


Theactionsofcurrentstepare:
a) OpentheTRS HardwarefromtheView bar.
b) OpentheEthernet Service OAMmenu.
c) Performoneoftheactions:

UnmarkontheFrame loss measurement in usecheckbox.


DeletetheselectedmeasurementsessionusingDeletebutton.

ThedeactivationmustbeconfirmedusingtheSendbuttonwhenusingthe
BTS Site Manager.
Expected outcome
TheFrameLossMeasurementsessionhasbeenstoppedontheBTS.
WhenFrameLossMeasurementsessionhasbeenstoppedontheBTSthen:

TheBTSstopsmeasuringtheFrameLossstatistics.
TheBTSstopssendingtheFrameLossMeasurementdatatotheOMS.
TheBTSdiscardstheincomingFrameLossmessagesfromtheremoteMEPs.
TheFrameLossmessagesarenottransmittedanymore.
TheFrameLossalarmiscanceled.
TheFrameLossstatisticsarenotclearedbuttheyarenotfurtherupdated.

Stop the Soam Frame Loss statistics measurement (M5141) at OMS.


Thisstepmustbeperformedusing:

RNW Measurement Management


NetAct Administration of Measurements

Expected outcome
TheSoamFrameLossstatisticsmeasurementhasbeenstoppedatOMS.
TheOMSstopssendingtheFrameLossMeasurementdatatotheNetAct.

4.2.4.3

Deactivating Frame Delay Measurement session


Purpose
ThisprocedureisusedtodeactivatetheFrameDelayMeasurementsessionontheBTS.
TheprocedureconsistsalsoofthestepstostoptheassociatedmeasurementatOMS.

Issue:01ADRAFT

DN09146788

163

Transmissionandtransportfeatures

RU50FeatureDescriptionsandInstructions

Before you start


ThisprocedureneedstheactivationoftheFrameDelayMeasurementsessiononthe
BTS.
ThisprocedureneedstheactivationoftheassociatedmeasurementatOMS.
Thisprocedurecanbeperformedbydisablethelicenseofoneofthefeatures:

RAN1880:EthernetOAMinBTS
RAN1900:IPTransportNetworkMeasurement

TheFrameDelayMeasurementsession(BTS)stopsafteroneoftheactions:

TheFrameDelayMeasurementsessionhasbeendeactivated.
TheEthernetServiceOAMPMhasbeendeactivated.
TheEthernetServiceOAMhasbeendeactivated.

Open the BTS Site Manager.

TheNetAct Configuration Managementsoftwarecanbeused


alternatively.

Turn off the Frame Delay Measurement session on the BTS.


Theactionsofcurrentstepare:
a) OpentheTRS HardwarefromtheView bar.
b) OpentheEthernet Service OAMmenu.
c) Performoneoftheactions:

UnmarkontheDelay measurement in usecheckbox.


DeletetheselectedmeasurementsessionusingDeletebutton.

ThedeactivationmustbeconfirmedusingtheSendbuttonwhenusingthe
BTS Site Manager.
Expected outcome
TheFrameDelayMeasurementsessionhasbeenstoppedontheBTS.
WhenFrameDelayMeasurementsessionhasbeenstoppedontheBTSthen:

164

TheBTSstopsmeasuringtheFrameDelaystatistics.
TheBTSstopssendingtheFrameDelayMeasurementdatatotheOMS.
TheBTSdiscardstheincomingFrameDelaymessagesfromtheremoteMEPs.
TheFrameDelaymessagesarenottransmittedanymore.
TheFrameDelayalarmsarecanceled.
TheFrameDelaystatisticsarenotclearedbuttheyarenotfurtherupdated.

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Transmissionandtransportfeatures

Stop the Soam Two Way Delay Statistics measurement (M5142) at OMS.
Thisstepmustbeperformedusing:

RNW Measurement Management


NetAct Administration of Measurements

Expected outcome
TheSoamTwoWayDelayStatisticsmeasurementhasbeenstoppedatOMS.
TheOMSstopssendingtheTwo-wayFrameDelayMeasurementdatatotheNetAct.
4

Stop the Soam One Way Delay Variation Statistics measurement (M5143) at
OMS.
Thisstepmustbeperformedusing:

RNW Measurement Management


NetAct Administration of Measurements

Expected outcome
TheSoamOneWayDelayVariationStatisticsmeasurementhasbeenstoppedat
OMS.
TheOMSstopssendingtheOne-wayFrameDelayVariationMeasurementdatato
theNetAct.

Issue:01ADRAFT

DN09146788

165

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

5 Operability features
5.1 RAN2199: BTS Event Triggered Symptom Data
Collection
5.1.1 Description of RAN2199: BTS Event Triggered Symptom
Data Collection
Introduction to the feature
Thisfeatureintroducesautomaticfault-triggeredBTSsymptomdatacollection.The
triggeringBTSfaultsaredefinedintheSiteConfigurationFile(SCF)usingtheNetAct
Configurator.

5.1.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
Thisfeaturebenefitstheoperatorasfollows:

5.1.1.2

Automaticsymptomdatacollectionreducestheworkload.
Theimmediatedatacollectionfollowingthefaultoccurrenceassiststhe
troubleshootingprocess.Self-triggeredsymptomdatagenerationismoreaccurate
andthusmoreefficientinsolvingfailures.

Requirements
Software requirements
Softwarerequirementsliststhesoftwarerequiredforthisfeature.

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi Direct OMS


RNC

Flexi BTS

RU50

Notplanned RN8.0

mcRNC4.1

Notplanned OMS3.01)

WN9.0

OMS3.12)

166

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

SGSN

MGW

UE

WL9.1

WN9.1

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Operabilityfeatures

1)forRU50
2)forRU50EP1

Hardware requirements
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradio
SystemModuleFSMForFlexiLiteBTSWCDMA.

5.1.1.3

Functional description
Theeventtriggeredsymptomdatacollectioncanbedividedintofollowingsteps:
1.
2.
3.
4.

Selection of the triggering faults


Data collection after the selected faults occur
Data transfer and storage
Viewing the collected data

Figure12:SymptomdatacollectionfromtheBTSillustratesthelogcollection
mechanism.
Figure12

SymptomdatacollectionfromtheBTS

Selection of the triggering faults


TheautomaticsymptomdatacollectionistriggeredbyBTSfaultsselectedbytheuser,
whoshouldcontacttheNSNTechnicalSupportpersonneltogetthelistofrecommended
triggers.ThelistoffaultsisdefinedwiththesymptomDataTriggerLparameter.

ThelistofBTSfaultsisavailableintheFlexiMultiradioBTSWCDMAFaults
document.TheTRSfaults(IDswithinrange61000-61999)arenotconsidered
astriggersforthesymptomdatacollection.
Atriggeringthresholdcanbeset-itdefineshowmanytimesacertainfaultshouldoccur
forthesamefaultsourcetotriggerthedatacollection.Bydefaultnotriggersaredefined.
Data collection after the selected faults occur

Issue:01ADRAFT

DN09146788

167

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

Thelogcollectionhappensonlywhenthefaultoccurs.Thelogconsistsof,forexample:

computerlogwritings
HWconfiguration
alarmhistory
activeSWversion
transportconfiguration
blackboxdata
performancedata
auto-connectionreport

Data transfer and storage


SymptomdataconsistsofoneorseveralfilesthataretransferredseparatelytoOMS
immediatelyafterthedatahasbeencollected.TheOMSisabletoperformsimultaneous
uploadsfromseveralBTSs.TheexistingfiletransfermechanismthroughtheBTSOM
interfaceisusedtotransferthedatatoOMS.Ifthetriggeringfaultleadstoarecovery
resetoftheBTS,theuploadtoOMSisstoppedanditisnotrestartedautomatically.
IntheOMS,thefilesarecombinedintoonepackagefile.Thisfileisnamedinacommon
way:TSUPL_<NE>_<NEid>_BTS_<BTSid>_<TRSHid>.<date-time>.tar
Thenamecontainsthefollowinginformation:

TSUPL:usedbyOMStoidentifythefiletypeasasymptomdatafile
<NE>:identifiesthecontroller(forexample,RNC)
<NEid>:thecontrollerIDnumber
<BTSid>:theBTSIDnumber
<TRSHid>:identifiesthetroubleshootingtaskintheBTS
<date-time>:indicateswhenthefileiscreated(usingtheOMSlocaltime).Thedate
andtimeformatisYYYYMMDDhhmmss.

Thefilesarestoredinthefollowingdirectory:
/var/opt/OMSftproot/NE/TroubleshootingData

The71106 TROUBLESHOOTING DATA RECEIVEDalarmindicatesthatthelog


filehasbeentransferredtoOMS.ThedwAlarmForUploadCompleted
parameterisusedfordisabling/enablingthealarmsettinginOMS.
The71129 TROUBLESHOOTING DATA CREATION OR UPLOAD FAILED
indicatesthatthedatacreationoruploadtoOMShasfailed.
OldsymptomdatafilesaredeletedautomaticallyfromtheBTS(afterbeingtransferredto
OMS).WhenthecleanupprocedurestartsintheOMS,theOMSdeletesfilesolderthan
certainnumberofdays(definedwiththedwNELogDaysSpanparameter).Bydefault,
filesolderthan10daysareremoved.Additionally,theOMSmonitorsthediskspaceuse
andifneeded,performsadditionalcleanupprocedure.
WiththedwBTSUploadEnabledparameter,theautomaticdatatransfertoOMScanbe
enabled/disabled.
Viewing the collected data

168

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Operabilityfeatures

ThefilescanbeviewedusingtheLogViewerintheOMSElementManager.TheLog
ViewerintroducestheTroubleshootingdatafiltercomponenttoallowusertofilter
troubleshootingfilestoshowonlythosefilesnotolderthanadefinedperiodofdays
(usercanspecifyvaluefrom1to30).WhenuserlogsintoOMSElementManager,the
Troubleshootingdatafiltercomponentcontainsthedefaultvaluewhichistakenfromthe
HideTRSFilesOlderThanDaysFilterLDAPparameter(2days)orfromtheweb
browsercookie(ifanyisstored).Whentheusersetsnewvalueinthiscomponent,this
newvalueispreservedwithinthesamesessionandalsorestorednexttimewhenthe
userlogsintoOMSElementManager(webbrowsercookiemechanismisusedto
preservethevaluesetbytheuser).
Thetroubleshootingdatafilescanalsobedownloadedtotheclient'scomputerusingthe
LogViewer.Onlythearchivefilescanbedownloadedandnotthecontentofthearchive.
ThelogfilesaresenttoOMSeveniftheBTSfaultwasfilteredbytheBTSalarmsystem
andtherelatedalarmwasnotdisplayedinOMS.

5.1.1.4

System impact
Interdependencies between features
Thisfeatureisapartofgenerictroubleshootingdatacollectionfunctionthatconsistsof
thefollowingfeatures:

RAN1873:OMSTroubleshootingDataCollection
RAN1805:RNCEventTriggeredSymptomDataCollection
RAN2446:EmergencySymptomDataCollectioninIPA-RNC

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on commands
Therearenocommandsrelatedtothisfeature.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkelementmanagementtools.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

5.1.1.5

RAN2199: BTS Event Triggered Symptom Data Collection


management data
Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
TableRelatedexistingalarmslistsexistingalarmsrelatedtothisfeature.

Issue:01ADRAFT

DN09146788

169

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

Table100

Relatedexistingalarms

Alarm ID

Alarm name

71106

TROUBLESHOOTINGDATARECEIVED

71129

TROUBLESHOOTINGDATACREATIONORUPLOADFAILED

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
TableNewparameterslistsparametersintroducedwiththisfeature.
Table101

Newparameters

Full name

Abbreviated name

Managed object

Symptomdatatriggerlist

symptomDataTriggerL

MRBTS

Table102

NewOMSLDAPparameters

Attribute
ClusterRoot/OMS/OMSPlatform/SS_SpringyUI/HideTRSFilesOlderThanDaysFilter

Tomakethenewvalueeffective,userneedstorestartTomcatPlatusingthefollowing
command:fshascli -rn /TomcatPlat

Table103:RelatedexistingOMSLDAPparameterslistsexistingparametersrelatedto
thisfeature.
Table103

RelatedexistingOMSLDAPparameters

Attribute
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwAlarmForUploadCom
pleted
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwBTSUploadEnabled

170

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table103

Operabilityfeatures

RelatedexistingOMSLDAPparameters(Cont.)

Attribute
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwNELogDaysSpan

g
5.1.1.6

WhentheLDAPparametervalueischanged,thenewvalueimmediatelytakeseffect
(noadditionalactionisnecessary).Itappliestoallparametersinthistable.

Sales information
Table104

Salesinformation

BSW/ASW

SW component

License control in network element

BSW

RAN

5.1.2 Activating RAN2199: BTS Event Triggered Symptom Data


Collection
Purpose
FollowthisproceduretoactivatetheRAN2199:BTSEventTriggeredSymptomData
Collectionfeature.Formoreinformationonthefeature,seetheRAN2199:BTSEvent
TriggeredSymptomDataCollectionfeaturedescriptioninRU50FeatureDescriptions
andInstructions.
Before you start

Thefeatureisactivatedwhentheoperatorenablesautomaticuploadof
symptomdatatoOMSusingthedwBTSUploadEnabledLDAPparameter.By
defaultthefunctionalityisturnedon.
Theactualsymptomdatacollectiontakesplaceifanytriggeringfaultshavebeendefined
duringtheBTScommissioning.ThelistoffaultsisdefinedusingtheSymptom data
trigger list (symptomDataTriggerL)parameterundertheMRBTSobject.
RestartoftheRNC,OMSorBTSisnotrequiredaftertheactivationofthisfeature.This
proceduredoesnotcausedowntime,anditcanbeperformedatanytimeoftheday.
MakesureyouhaveaccesstotheParameterToolintheOMSElementManager.

Log in to OMS Element Manager.

Open the Parameter Tool.


TheParameterToolisavailableintheExternalApplications(intheApplication
Launcherwindowthatisdisplayed).

Issue:01ADRAFT

DN09146788

171

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

Change the dwBTSUploadEnabled LDAP parameter value to 1.


Path:
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwBTSUpload
Enabled

Expected outcome
TheRAN2199:BTSEventTriggeredSymptomDataCollectionfeatureisturnedon.
Further information
Ittakesapproximately10minutestomakethechangeeffectiveintheOMS.

5.1.3 Deactivating RAN2199: BTS Event Triggered Symptom


Data Collection
Purpose
FollowthisproceduretodeactivatetheRAN2199:BTSEventTriggeredSymptomData
Collectionfeature.Formoreinformationonthefeature,seetheRAN2199:BTSEvent
TriggeredSymptomDataCollectionfeaturedescriptioninRU50FeatureDescriptions
andInstructions.
Before you start
RestartoftheRNC,OMSorBTSisnotrequiredafterthedeactivationofthisfeature.
Thisproceduredoesnotcausedowntime,anditcanbeperformedatanytimeofthe
day.
MakesureyouhaveaccesstotheParameterToolintheOMSElementManager.

Log in to OMS Element Manager.

Open the Parameter Tool.


TheParameterToolisavailableintheExternalApplications(intheApplication
Launcherwindowthatisdisplayed).

Change the dwBTSUploadEnabled LDAP parameter value to 0.


Path:
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwBTSUpload
Enabled

Expected outcome
TheRAN2199:BTSEventTriggeredSymptomDataCollectionfeatureisturnedoff.
Further information
Ittakesapproximately10minutestomakethechangeeffectiveintheOMS.

172

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Operabilityfeatures

5.2 RAN2919: OMS Certificate Update and Revocation


Support
5.2.1 Description of RAN2919: OMS Certificate Update and
Revocation Support
Introduction to the feature
TheOMSsupportstheautomatedcertificatelifecyclemanagementbyautonomous
updateoftheoperatorentitycertificate.Thecertificatecanbesignedbyamultilayer
PublicKeyInfrastructure(PKI)systemconsistingofsub-ordinateCertificateAuthorities
(CAs)andtherootCAontop.RevocationlistsprovidedbythesigningCAsareloaded
andregularlyupdated.

5.2.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
Thisfeaturebenefitstheoperatorasfollows:

5.2.1.2

TheoperatorisabletouseausualPublicKeyInfrastructure(PKI)witharootCAon
topandusecase-specificsub-ordinateCAsinchargeforsigningboththeRANand
OMSnodes.
3GPP-compliantlifecyclemanagementallowsflexibilityonPKIvendorselectionand
harmonizedcertificatemanagementforOMSinthesamefashionasforBTSand
SecurityGateways.ThisresultsinsevereOPEXreductions.

Requirements
Software requirements
Thefollowingtableliststhesoftwarerequiredforthisfeature.
Table105

Issue:01ADRAFT

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

OMS

BTS Flexi

Flexi Lite

RU50EP1

supportnot
required

supportnot
required

OMS3.1

supportnot
required

supportnot
required

supportnot
required

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

supportnot
required

NetAct8EP2

supportnot
required

supportnot
required

supportnot
required

supportnot
required

DN09146788

173

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

Hardware requirements
Thisfeaturerequiresnoneworadditionalhardware.

5.2.1.3

Functional description
ThiscertificatemanagementfeaturesupportstheautonomousupdateoftheOMS
operatorcertificateandtheprovisionofrevocationinformationtothesecuretransport
layers,suchasTLSorHTTPS.Withthehelpoftherevocationliststhesecuretransport
layerscheckifitisallowedtoestablishasecureconnectiontoaparticularremote
communicationpeer.

3GPP-compliant life cycle management


TheCertificateManagementProtocol(CMP)protocolandproceduresareimplemented
asspecifiedin3GPPTS33.310.ThisaffectsespeciallytrustanchordeliverytoOMSand
CMPmessagesigningbytheCAoralternativelybytheRegistrationAuthorityclosingthe
CMPprotocolsession.

Multilayer support
TheOMScertificatecanbesignedbyatrustchain,forexample,theOMSendentity
certificateissignedbyasub-ordinateCAwhichitselfissignedbytherootCA.TheOMS
hasthecompletetrustchainforitsownoperatorcertificatestoredandsupportsachain
oftrustoffourlayers,thatismaximumthreesub-ordinateCAsexceptfortherootCA.

Certificate format
OMSsupportsX.509v3certificates.Thefollowingformatshavetobesupported:

PEM:itistheformatusedforuserinterface.
DER:itistheformatusedfortransferringcertificatesoverCMP.
PKCS#12:itistherequiredformatfortransferringcertificatesandkeystoOMS.

Automated OMS operator certificate update


TheCMPv2protocolimplementationisenhancedbythekeyupdateprocedure.The
OMSrenewsitsoperatorcertificateautomaticallybeforethelifetimeexpires.Inaddition,
theoperatorisabletousetheNWI3MediationFragmentConfigurationTooltotrigger
theoperatorcertificateupdateondemandremotely.

Trust anchor deployment and update


Thetrustanchors,rootCAcertificate,andoptionalsub-ordinatesCAcertificatesare
deliveredusingeithertheCMPprotocolexchange(forkeysigningrequestorkey
update)orbythemanualOMSset-upconfiguration(filesinthePKSC#12orPEM
format).WhenthecertificateisclosetoexpirationandOMSisnotabletoupdateitorit
hasalreadyexpired,theOMSsendsanotificationtoNetAct.

Local certificate enrollment


IftheoperatorhasnoonlinePKIinservice,itisthenpossibletoloadtheoperator
certificateandtrustanchorsmanuallyaspartoftheOMSset-upconfiguration
procedureswithfiles.Theoff-linecreatedkey-pairandtherelatedcertificateareincluded
withinapassphraseprotectedPKCS#12file.Inaddition,certificatesandRSAkeysare
acceptedasPEMformattedfiles.

174

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Operabilityfeatures

3GPP algorithms
InadditiontoSHA-1theOMSsupportsSHA_256ashashalgorithmforcertificatesas
requiredby3GPPTS33.310chapter6.1.1Commonrulestoallcertificates.

Certificate Revocation List (CRL) check


CRLsupportcanbeactivated/deactivatedbyoperator'sconfiguration.Ifactivated,the
OMSperformstheCRLhousekeeping.

CRL distribution points (CRLDP) given by certificates of the own PKI


BydefaulttheOMSusesfoundCRLDPreceivedwithinCAcertificatesoftheowntrust
chaintoaddressanddownloadtheCRLsfortheownPKI.TheOMSdownloadsand
updatestheselistsautomaticallyfromtheLDAPservers.Inaddition,theoperatorisable
totriggertheupdatewiththeNetActMNCToolorOMSCLIomscertificatetool.

Configurable CRL distribution points


Alternatively,configurableCRLsourcesareavailable(IPaddresses/FQDNandpath).
TheOMSoffers10additionalCRLdistributionpointswhichcanbeconfiguredwithIP
addresses/FQDNandpathdefinedpercertificate.

5.2.1.4

System impact
Interdependencies between features
ThisfeatureisrelatedtotheRAN2267:CertificateManagementforOMSProducts
feature.

Impact on interfaces
ThisfeaturehasimpactonthefollowingOMSinterfaces:

HTTPS:ServerandClient
RUIM-LDAP:Client
OMSLDAPS:ClientandServer
BTSOM:Server
EMI:Server

Impact on commands
Thisfeatureisrelatedtothefollowingcommands:

Issue:01ADRAFT

omscertificate
omscertificate
omscertificate
omscertificate
omscertificate
omscertificate
omscertificate
omscertificate

configure-crl-client
install-crl
show-crl
update-crl
show-crl-status
delete-crl
add-crl-url
delete-crl-url

DN09146788

175

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

Impact on network and network element management tools


Thisfeaturesimplifiesnetworkmanagementbyautomaticandcentralizedcertificate
managementfunctions.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

5.2.1.5

RAN2919: OMS Certificate Update and Revocation Support


management data
Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Table106:Newalarmslistsalarmsintroducedwiththisfeature.
Table106

Newalarms

Alarm ID

Alarm name and description

71122

CRL UPDATE FAILURE.ThisalarmisraisedwhentheNEfailstoretrieveor


validateaCRLfromtheserver.

71123

CERTIFICATE REVOKED.ThisalarmisraisedwhentheOMSowncertificateis
listedonCRL.

71133

CERTIFICATE CAPACITY REACHED.TheOMSsetsthisalarmwhenitsownCA


certificatestoragecapacityorCRLstoragespaceisabouttobereached.

71134

CERTIFICATE EXPIRED.TheOMSsetsthisalarmwhenitsownEEor
intermediateCAorrootCAcertificateexpires.

70381

CRL DOWNLOAD FAILURE.ThisalarmisraisedwhentheOMSfailstoretrieveor


validateaCRLforpeercertificatefromtheserver.

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table107:NewOMSLDAPparameterslistsparametersintroducedwiththisfeature.

176

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table107

Operabilityfeatures

NewOMSLDAPparameters

Attribute
ClusterRoot/OMS/SW/SS_Nwi3Certificate/Nwi3Certificate/CANECloseCertUpdateTimerAdv
ThisparameterdefineshowmanydaysinadvancetheOMStriggerstheoperatorcertificateupdateprocedureor
fetchesCAcertificatesfromthecertificaterepository(ifCRisconfigured).
ClusterRoot/OMS/SW/SS_Nwi3Certificate/Nwi3Certificate/CANECloserCertUpdateTimerAdv
ThisparameterdefineshowmanydaysinadvancetheOMSraisesthe71125CERTIFICATEEXPIRINGalarmand
triggerstheoperatorcertificateupdateprocedureorfetchesCAcertificatesfromthecertificaterepository(ifCRis
configured).
ClusterRoot/OMS/SW/SS_Nwi3Certificate/Nwi3Certificate/CRLPeriodicDownloadTimer
ThisparameterdefineshowoftentheOMSdownloadsCRLsfromCRLdistributionpoints.

TherearenoPRFILEparametersrelatedtothisfeature.

5.2.1.6

Sales information
Table108

Salesinformation

BSW/ASW

SW component

License control in network element

BSW

RAN

notdefined

5.3 RAN2699: OMS System Status View


5.3.1 Description of RAN2699: OMS System Status View
Introduction to the feature
ThisfeatureintroduceseasytousegeneralOMSSystemStatusViewthatenablesan
instantrealtimeviewofOMSnode'soverallstatus.

5.3.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
Thisfeaturebenefitstheoperatorasfollows:

Issue:01ADRAFT

ItmakesmonitoringandtroubleshootingofOMSeasierandfaster.
ItlowerstheoperatingcostsandimprovesOMSservicelevelinthelongterm.

DN09146788

177

Operabilityfeatures

5.3.1.2

RU50FeatureDescriptionsandInstructions

Requirements
Software requirements
Thefollowingtableliststhesoftwarerequiredforthisfeature.
Table109

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi Direct OMS


RNC

Flexi BTS

RU50EP1

supportnot
required

supportnot
required

supportnot
required

supportnot
required

OMS3.1

supportnot
required

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

SGSN

MGW

UE

supportnot
required

supportnot
required

supportnot
required

supportnot
required

supportnot
required

supportnot
required

supportnot
required

Hardware requirements
Thisfeaturerequiresnoneworadditionalhardware.

5.3.1.3

Functional description
Thisfeatureisdesignedasasetofarea-specificviewsthatdisplaydifferenttypesof
informationhelpingtheoperatortomonitortheOMSsystem.Operatoraccessesstatus
viewandtheprovidedsysteminformationafterselectingappropriateOMSSystem
StatusViewwebpage.
Area-specificviewsaredividedintotwomaingroups:

OMS Resources.Viewsavailablewithinthisgroupinformtheoperatoraboutstatus
ofOMSserveranditsgenericservices.Fromtheinformationpresentedherethe
operatorisabletoverifyifOMSoperatescorrectlyasaserver.Theseviewsfocuson
hardware,software,andnetworkconfiguration.Therearealsoprocessesrunningon
OMSserverpresentedalongwiththeirstates.TheOMSResourcesviewsallowthe
operatortoconcludetheconditionofserverregardlessofitsOSSresponsibilities.
OMS Services.Viewsavailablewithinthisgroupinformtheoperatoraboutthemore
detailedstatusofO&MServicesprovidedbytheOMS.Fromtheinformation
presentedheretheoperatorisabletoverifyifOMSoperatescorrectlyasan
OperationsSupportSystemelement.Coremediationoperationsaretrackedhere
usingtwoperspectives:currenttasksandhistoricalevents.Theoperatorisalso
presentedcountersandalarmsrelatedtoparticularO&Mareas.

TheOMSprovidesOMSSystemStatusViewmainpagewithtriggersallowingtodisplay
thefollowingchildviews:
1. OMS Resources

178

OMSHardware

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Operabilityfeatures

OMSSoftware
Network&Applications
OMSProcesses

2. OMS Services

PerformanceManagement(PM)
FaultManagement(FM)
ConfigurationManagement(CM)
SoftwareManagement(SWM)
SecurityManagement
ConnectionManagement

EachofthechildviewsconsistsofseveralcomponentsthatareshowninFigure13:
OMSSystemStatusViewapplicationstructurediagram.
Figure13

OMSSystemStatusViewapplicationstructurediagram
OMSSystemStatusView

OMSResources

Hardware

Network
and App

OMSServices

OMS
Processes

Software

PM

FM

CM/TOPO

SWM

Secu

Connect.

OMSHW
specification

Net&IP layer
conf. view

OMSHW
specification

Processes
view

Counter
view

Counter
view

Counter
view

Counter
view

Counter
view

Alarms
view

Disk&RAID
monitoring

App.layer
conf. view

Op.history
view

Alarms
view

Alarms
view

Alarms
view

Alarms
view

Processes
view

Alarms
view

Processes
view

Counter
view

Counter
view

Currentop.
view

Op.history
view

Processes
view

Processes
view

Processes
view

Currentop.
view

Processes
view

Op.history
view

Alarms
view

Alarms
view

Alarms
view

Config
view

Currentop.
view

Currentop.
view

Op.history
view

Op.history
view

OMS
connectivity

Config
view

Op.history
view

Op.history
view

Op.history
view

Config
view

Config
view

Config
view

Certificates
view

ThelistofcomponentsviewandtheirshortdescriptionsarepresentedinTable110:
FunctionalscopeofOMSSystemStatusViewcomponents:
Table110

FunctionalscopeofOMSSystemStatusViewcomponents

Component view name Short description

Issue:01ADRAFT

Countersview

Countersviewisacommonviewdisplayingcurrentvaluesand
historicalchartsofcountersimportantforparticulararea.

Alarmsview

Alarmsviewdisplaysactivealarmsrelatedtoparticulararea.

Processesview

ProcessesviewdisplaysstatesofOMSprocessesrelatedtoparticular
area.Thefollowingstatesareprovidedintheviewforeachprocess:
administrativestate,operationalstate,proceduralstate.

DN09146788

179

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

Table110

FunctionalscopeofOMSSystemStatusViewcomponents(Cont.)

Component view name Short description


OperationHistoryview

OperationHistorypresentsdetailsofeventsbeingapartofoperations
whichareperformedwithincertainarea.Thisviewprovidesadvanced
filterfunctionalityallowingtofindanyoperation-relatedinformation.

CurrentOperationsview CurrentOperationspresentscurrentlyprocessesandrecentlyfinished
operationswithincertainarea.Thisviewprovidesadvancedfilter
functionalityallowingtofindanyoperation-relatedinformation.
Configurationview

Configurationviewdisplaysessentialconfigurationparameterswithin
eacharea.

Certificatesview

Certificatesviewdisplayslistofcertificatesstored(installed)onthe
OMS.Thelistcontainswholechainoftrust:EE,rootCAand
intermediateCAcertificates.

OMSconnectivity

OMSConnectivityviewsummarizesthequantitiesofconnected
RNCs,BTSsandcellsandalsopresentsOMSconnectivitylimits.

OMSHWspecification

OMSHWspecificationdisplaysinformationaboutOMShardware
resources:server,CPUs,RAMmemories,disks,networkcards,RAID
controllers,andBIOS.

Disks&RAIDmonitoring

Disks&RAIDmonitoringviewdisplaysinformationaboutHWandSW
RAIDconfigurationandstatus,physicaldrivesandlogicaldisks
informationandhealthstatus.Italsocontainssummaryofpartitions
andtheirusage.

Network&IPlayer
configurationview

Network&IPlayerconfigurationviewdisplaysnetworkconfiguration
forlowerlayers(L2&L3)protocols.

Applicationlayer
configuration&status
view

Applicationlayerconfiguration&statusviewdisplaysnetwork
configurationforapplicationlayerprotocols:northboundand
southboundinterfaces,filetransfers,RUIM,CMP,CRL,NTP,and
DNS.

OMSSWspecification

OMSsoftwarespecificationviewdisplaysinformationaboutcurrent
OMSsoftwarereleaseandversionandsummaryofOMSsoftware
sets.

TheOMSSystemStatusViewisimplementedwithinOMSWebUI.

5.3.1.4

System impact
Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

180

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Operabilityfeatures

Impact on network and network element management tools


Thisfeaturesimplifiesnetworkmanagementbyintroducingeasytouseandinstantreal
timestatusview.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

5.3.1.5

RAN2699: OMS System Status View management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Table111:NewAlarmslistsalarmsintroducedwiththisfeature.
Table111

NewAlarms

Alarm ID Alarm name


70359

HARD DISK DRIVE FAILURE.

70377

SYSTEM CLOCK OUT-OF-SYNC WITH NTP SERVER.

Measurements and counters


Informationonmeasurementsandcountersrelatedtothisfeaturewillbeprovidedin
furtherdeliveries.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Informationonparametersrelatedtothisfeaturewillbeprovidedinfurtherdeliveries.

5.3.1.6

Sales information
Table112

Issue:01ADRAFT

Salesinformation

BSW/ASW

License control in
network element

License control
attributes

Activated by default

ASW

OMSLK

Long-termON/OFF
licence

No

DN09146788

181

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

5.4 RAN3004: Parameter Categorization


5.4.1 Description of RAN3004: Parameter Categorization
Introduction to the feature
TheRAN3004:ParameterCategorizationfeatureintroducesRadioNetwork(RNW)and
IPplanparameterscategorizationinNetAct Configurator.Thegoalistodifferentiate
betweentheparametersforsimplifiedoperations(Basicparameters)andtheparameters
thatareoutofprimaryfocusduringregularnetworkoperation(Advancedparameters).

5.4.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
ThisfeaturefacilitatesthenetworkconfigurationbydividingtheRNWandIPplan
parametersintoBasicandAdvancedcategories.

5.4.1.2

Requirements
Software requirements
Thefollowingtablelistssoftwarerequiredforthisfeature.
Table113

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi Direct OMS


RNC

Flexi BTS

RU50EP1

Notplanned RN8.1

mcRNC4.1

Notplanned Supportnot
required

Supportnot
required

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

SGSN

MGW

UE

Supportnot
required

Supportnot
required

NetAct8
EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
Thisfeaturerequiresnoneworadditionalhardware.

5.4.1.3

Functional description
TheRAN3004:ParameterCategorizationfeatureintroducesRNWandIPplan
parameterscategorizationintotwopre-definedgroupsintheEditor ViewsoftheCM
Editor.Thefirstgroup(Basic parameters)ismeantforparametersusedduringcell
deploymentthatareadjustedtoparticularscenario.Theothergroup(Advanced
parameters)holdsthenetworkoptimizationandfinetuningparameters(includingthose
relatedtoadvancedorcomplexfeatures).
Thefollowinglistshowsthekeycharacteristicsofparametercategories:

182

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Basic

Operabilityfeatures

configurationparameters(forexample,networkelementidentifiers,IP
addresses,andsoon)
planningparameters(forexample,neighbordefinitions,frequencyplan,
scramblingcodeplan,PCIplan,RApreambleplan,andsoon)
parametersrelatedtothedimensioning
parametersthatdefinetheoperatorstrategy(forexample,trafficsteering,
thresholdsforpowercontrol,handovers,cellreselections,highlevelparameters
definingfeaturebehavior,andsoon)

Advanced

networkoptimizationandfinetuningparameters(includingthoserelatedto
advancedorcomplexfeatures)
parametersthatareoutofprimaryfocusduringregularnetworkoperation

InNetactCMEditortherearepre-definedParameterViewscalledBasicparametersand
Advancedparameters.Theygroupparametersaccordingtothecategory.Thesetwo
pre-definedgroupscanbeusedasatemplatetocreatethecustomViews(Editor
Views).
Figure14

5.4.1.4

CMEditor-BasicandAdvancedparametersviews

System impact
Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on network and network element management tools


NetAct Configuratorintroducestwopre-definedViewsfortheRNWandIPplan
parameters(BasicparametersandAdvancedparameters).

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

Issue:01ADRAFT

DN09146788

183

Operabilityfeatures

5.4.1.5

RU50FeatureDescriptionsandInstructions

RAN3004: Parameter Categorization management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Faults and alarms


Therearenofaultsandalarmsrelatedtothisfeature.

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Therearenoparametersrelatedtothisfeature.

5.4.1.6

Sales information
Table114

Salesinformation

BSW/ASW

SW component

License control in network element

BSW

RAN

5.5 RAN2507: RNW Plan Progress Indicator and Abort


5.5.1 Description of RAN2507: RNW Plan Progress Indicator and
Abort
Introduction to the feature
RAN2507:RNWPlanProgressIndicatorandAbortfeatureallowstheusertoabortradio
network(RNW)configurationmanagementoperationsatanypointintheirexecution.
ThisfeatureshowstheNetActConfiguratorOperatortheprogressofRNWconfiguration
managementoperations;thatis,thepercentageoftheoperationthathascompletedand
theestimatedtimeleft.

5.5.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
Thisfeaturebenefitstheoperatorasfollows:

184

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

5.5.1.2

Operabilityfeatures

ItispossibletoaborttheRNWplandownload,activate,rollback,andupload
operationswhenneededwithoutwaitingfortheplannedactiontofinish.
Itispossiblefortheoperatorstoabortlong-runningoperationtoallowthemto
performmorecriticaloperation.
ItprovidesbettervisibilitytoRNWplanoperationprogress,whichiscrucialwhen
activatingbigplans.

Requirements
Software requirements
Thefollowingtableliststhesoftwarethatisrequiredforthisfeature.
Table115

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi Direct OMS


RNC

BTS Flexi

RU50EP1

Notplanned RN8.1

mcRN4.1

Notplanned OMS3.1

Supportnot
required

Flexi Lite

BTS Flexi
10

NetAct

MSC

SGSN

MGW

UE

Supportnot
required

Supportnot
required

NetAct8
EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
Thisfeaturerequiresnoneworadditionalhardware.

5.5.1.3

Functional description
TheRAN2507:RNWPlanProgressIndicatorandAbortfeatureprovidesbetter
monitoringandcontrolforradionetwork(RNW)configurationmanagementoperations.
Thisfeatureisabletoshowprogressinformationfor:

RNWplandownload
RNWplanactivation
RNWplanrollback

TheRNCreportstheinformationabouttheprogressoftheaboveRNWconfiguration
managementoperationsandforwardstheinformationtotheOMS.TheOMSservesasa
mediatorbetweentheRNCandNetAct.
NetActupdatestheNetActConfiguratorOperatortoshowplan
download/activation/rollbackprogressforeachRNCincludedintheplanaswellasfor
theoverallplandownload.
TheNetActConfiguratorOperatordisplaystheprogressindicationwhichshowsthe
percentageofoveralloperationcompletionandtheestimatedtimelefttofinishthe
operation.

Issue:01ADRAFT

DN09146788

185

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

ForconfigurationchangesthatimpacttheBTS,theestimatedtimeleftreported
inprogressindicationsfromtheRNCtakesintoaccountanestimatedlatency
duetomessagesexchangedbetweentheRNCandtheBTS.Unexpected
delaysintheBTSresponsetosuchmessagingmaycauseanoperation'stime
lefttoincreaseastheoperationprogress,ratherthandecrease,asistypically
expected.
ThisfeaturealsointroducestheabilitytoabortRNWconfigurationmanagement
operations:

RNWplandownload
RNWplanactivation
RNWplanrollback
RNWconfigurationupload

TheoperatorisabletoaborttheconfigurationmanagementoperationsforallRNCsor
forasingleRNCwithintheplan.
TheNetActConfiguratorOperatorshowstheresultoftheabortrequest,whichiseither
successful(abortoperationwasinitiated),orafailure(thenetworkelementrejectedthe
abortrequest).
InmonitoringandabortingRNWconfigurationmanagementoperations(download,
activate,rollback,andconfigurationupload),eachelement:NetAct,OMS,RNC,and
systeminterfaceshasitsowntasksasindicatedinTable116:Tasksinmonitoringand
abortingRNWconfigurationmanagementoperations.
Table116

TasksinmonitoringandabortingRNWconfigurationmanagement
operations

Network element Task in monitoring


NetAct

Task in aborting

Receivesandprocessesthe
operationprogressmessage
thatdescribethe
download/activation/rollback
progressforwardedbytheOMS

OMS

186

Servesasmediatorbetween
theRNCandNetAct
Receivestheoperation
progressmessagesfromthe
RNCthatcontainnetwork

DN09146788

UpdatestheNetAct
ConfiguratorOperatorto
facilitatetheuser'srequest
toaborttheplanoperation
forasingleRNCorforall
theRNCswithintheplan
Generatestheoperation
abortmessagetostopthe
plan
activation/download/rollbac
k/configurationupload
operationandsendsthis
operationtotheOMS
Displaysthefeedback
whethertheabortrequestis
acceptedorrejectedbythe
networkelement
Receivesandprocesses
operationabortmessage
Issuesnewoperationabort
messagetotheRNCtobe
aborted,iftheoperationis

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table116

Operabilityfeatures

TasksinmonitoringandabortingRNWconfigurationmanagement
operations(Cont.)

Network element Task in monitoring

element
download/activation/rollback
progressinformation
Convertstheoperation
progressmessageand
forwardedtheconverted
messagetoNetAct

Task in aborting

alreadystartedonthe
networkelement
Cancelsfurtheroperation
processingfortheRNC,if
theoperationhasnot
startedonthenetwork
element
Receivesandprocesses
theresponsetothe
operationabortmessage
fromtheRNC
Receivesandprocessesan
"aborted"resultfromthe:

RNC

Issue:01ADRAFT

Definesthealgorithmfor
calculatingoverallprogress
basedonthenumberofobjects
activated
Facilitatesthereportingofthe
progressasapercentageofthe
totalplaneffort
Definesthealgorithmin
estimationofthetotalamountof
timethatthe
download/activation/rollback
operationwillbecompletedand
reportsperiodicupdatestothe
totaltimeviaprogressmessage
Generatesoperationprogress
messagethatdescribesthe
download/activation/rollback
progressatleastevery60

DN09146788

fileactivation
acknowledgedmessage
(RNWplanactivation)
fileloadcompleted
message(RNW
downloadactivation)
rollbackacknowledged
message(RNW
rollbackactivation)
fileloadprepare
message(RNW
configurationupload)

Generatesanddeliversthe
operationcompleted
responsewithan"aborted"
operationstatustoNetAct
Receivesandprocesses
operationabortmessage
DeterminesiftheRNWplan
operationcanbeaborted
basedonthecurrentstate
oftheoperationand
acknowledgesthe
operationabortrequest
Performstheabortofthe:

activationoperation-by
terminatingthe
activationoperationina
'safe'place,suchas
leavestheRNC
databaseinastate
readyforthe
subsequentdownload
andactivationof

187

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

Table116

TasksinmonitoringandabortingRNWconfigurationmanagement
operations(Cont.)

Network element Task in monitoring

Task in aborting

secondsandforwardsthis
messagetoOMS

Generatesthefollowing
response,whichdepends
onwhattypeofRNW
configurationmanangement
operation,withan"aborted"
causevalueanddeliversit
totheOMS:

188

DN09146788

anotherplanorthe
rollbackofthecurrent
plan
downloadoperation-by
terminatingany
consistencychecking
thatmaybeinprogress
andensuresthatthe
RNCisinastate,
whereitispossibleto
receivesubsequent
downloadattempt
rollbackoperation-by
terminatingtherollback
operationata'safe'
place,suchasleaves
theRNCdatabaseina
statereadyfora
subsequentrollbackor
downloadrequest
uploadoperation-by
terminatingthecreation
oftheconfiguration
uploadfile(ifin
progress),removingthe
configurationuploadfile
(ifcreated),and
ensuringtheRNCisin
astatetoreceivea
subsequentoperation

fileactivation
acknowledged(RNW
planactivation)
fileloadcompleted
(RNWplandownload)
rollbackacknowledged
(RNWplanrollback)
fileloadprepare(RNW
configurationupload)

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table116

Operabilityfeatures

TasksinmonitoringandabortingRNWconfigurationmanagement
operations(Cont.)

Network element Task in monitoring

Task in aborting

Interfaces

Theabortmessagerequestandits
associatedabortacknowledgement
responseisaddedinOMS-RNC
interface.

Thenewmessagethatincludes
progressinformationsuchas
percentagecompletionandestimated
timeleftisaddedinOMS-RNC
interface.
Thenewmessageforoperation
progressreportingpurposesisaddedin
NetAct-OMSinterface.

TheRNCraisesaminoralarm,3173 RNW PLAN ACTIVATION OR ROLLBACK


FAILED,iftheongoingRNWplanactivationorrollbackoperationisaborted.Thealarm
notifiestheoperatoraboutthepossibleinconsistencyinRNWdatabase(RNWDB)
becauseoftheabortoperation.Thesystemwillautomaticallycancelthealarmwhenthe
operatorperformsplanrollbackorplanprovisioningwithparameter
FullConsCheckRequest.

5.5.1.4

System impact
Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.

Impact on interfaces
Thisfeatureimpactsinterfacesasfollows:

NetAct-OMS

NewprogressinoperationmessagetobeusedbyOMSforforwardingtoNetAct
thatindicatesthepercentageofcompletedtasksandtheestimatedtimeleftto
completetheplanmanagementoperation.
NewoperationabortmessagetobeusedbyOMSforrequestingabortofRNW
planmanagementoperationinRNC,whichincludesthetaskidentifierofthe
operationtobeaborted.
NewoperationabortacknowledgementmessagetobeusedbyRNCaresponse
totheoperationabortmessagereceivedfromOMS,whichincludesthetask
identifieroftheoperationtobeaborted,codeindicatingthereasonofthe
rejectionoftheabortrequest(optional)andtextdescribingthereasonofthe
rejectionoftheabortrequest(optional).

OMS-RNC

NewoperationabortmessagetobeusedbyOMSforrequestingabortofRNW
planmanagementoperationinRNC.Thenewmessageincludesthetask
identifieroftheoperationtobeaborted.
NewoperationabortacknowledgemessagetobeusedbyRNCasresponseto
operationabortmessagefromtheOMS.Thismessageincludes:

Issue:01ADRAFT

Taskidentifieroftheoperationtobeaborted

DN09146788

189

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

Notacknowledgedreasoncodethatindicatesthereasonoftheabortrequest
rejection(optional)
Notacknowledgedtextthatdescribesthethereasonoftheabortrequest
rejection(optional)

NewoperationprogressmessagetobeusedbyRNCtoindicatetheprogress
informationoftheongoingplandownload,activation,orrollbackoperationat
RNC.Thenewmessageincludesthepercentageofcompletedtasksandthe
estimatedtimelefttocompletetheplanmanagementoperation.

Impact on network and network element management tools


ThisfeaturehasanimpactonO&Msystemperformance.Theabortfunctionis
consideredasaperformanceimprovementtotheusers,sincetheoperatorsisableto
stoptheprocessingofactivitiesthatarenotcrucialtothem.

Impact on system performance and capacity


Thefuncionalityofthisfeaturewilltypicallybeexecutedonthefollowingsituations:

5.5.1.5

duringthemaintenancewindowwhenthesystemcapacityimpactsarenotlikelyto
occur
duringemergencysituationswhenthesystemcapacityimpactsarelessimportant
thefunctionalitythatthisfeatureprovides

RAN2507: RNW Plan Progress Indicator and Abort management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Table2Alarmslistsexistingalarmsthatarerelatedtothisfeature.
Table117

Alarms

Alarm ID

Alarm name

3173

RNWPLANACTIVATIONORROLLBACKFAILED

Measurements and counters


Therearenonewmeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table118:Parameterslistsnewparametersthatarerelatedtothisfeature.

190

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table118

5.5.1.6

Operabilityfeatures

Parameters

Full name

Abbreviated name

Managed object

FullConsistencyCheck
Request

FullConsCheckRequest

RNC

BSW/ASW

SW component

License control in network


element

ASWNetAct

CMActivationOptions

Sales information

5.6 RAN2554: Transport Configuration Fall-back


5.6.1 Description of RAN2554: Transport Configuration Fall-back
Introduction to the feature
IfafteraconfigurationupdatetheFlexiMultiradioBTSfailstoconnecttoitsmanagement
network,selfhealingmeasuresaretaken.Thisappliesforfailuresduringnormal
operationafteraconfiguration-update.

5.6.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
Thisfeaturebenefitstheoperatorasfollows:

5.6.1.2

Selfhealingreducestheeffortfornetworkmanagementandmaintenanceand
increasestheFlexiMultiradioBTSavailabilityduetolessoutage.
SitevisitscanbeavoidedwhenachangedBTStransmissionconfigurationprohibits
remotemanagementconnections.

Requirements
Software requirements
Table119:Softwarerequirementsliststhesoftwarethatisrequiredforthisfeature.

Issue:01ADRAFT

RAS

Flexi Direct IPA-RNC

RU50

Supportnot
required

mcRNC

OMS

BTS Flexi

Supportnot Supportnot Supportnot WN9.0


required
required
required

DN09146788

Flexi Lite
WL9.1

191

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

Table119

Softwarerequirements

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

WN9.1

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/E,orFlexiMultiradio
SystemModuleFSMForFlexiLiteBTSWCDMA.

5.6.1.3

Functional description
Autonomous fallback to previous configuration
AfallbacktothepreviousconfigurationhappenswhentheBTSfailstosuccessfully
(re)connecttheM-planetotheNetworkManagementSystemafteraremote
configurationupdateandactivation.IftheM-planecanbeestablishedwiththeold
configuration,anotificationissenttotheNetworkManagementSystemindicatingthat
thenewconfigurationwasnotactivated.Iftheoldonefailsaswell,thereceivednewone
isactivatedagainandtheBTScontinueswiththeregularlinkfailuremechanism.
TheselfhealingrecoveryisinitiatedonlyafterTransportNetworkLayer(TNL)
configurationchangesviaBTSSiteConfigurationfile(SCF)activation.TheTNL
configurationreferstotheparametersdefinedintheTransportSystem(TRS)PDDB.

192

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Figure15

g
5.6.1.4

Operabilityfeatures

RAN2554:TransportConfigurationFallback

Self-healingisnotallowedwhenBTSSMisconnectedtotheBTS.

System impact
Interdependencies between features
Therearenointerdependenciesbetweenfeatures.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on commands
Therearenocommandsrelatedtothisfeature.

Impact on network and network element management tools


TheselfhealingfunctionalityandlogicareimplementedintheBTS.Therearenew
parametersintroduced,whichimpactNetActadaptation.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

Issue:01ADRAFT

DN09146788

193

Operabilityfeatures

5.6.1.5

RU50FeatureDescriptionsandInstructions

RAN2554: Transport Configuration Fallback management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Thefollowingtablelistsalarmsandfaults,whicharerelatedtothisfeature.
Table120

Newfault

Alarm ID

Alarm name

7665

Newfaultcomingwith:BASESTATIONTRANSMISSIONALARM.Meaning
ofnewfault:thebasestationhasrecoveredtheM-planeconnectionby
fallingbacktotheoldtransportconfigurationaftertheconfigurationchange

Parameters
Table121

5.6.1.6

Newparameter

Full name

Abbreviated name

Managed object

Enabletransportconfigurationfallback

enableTransportConfigF
allback

IPNO

Sales information
Table122

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

BTSLK

5.6.2 Activating RAN2554: Transport Configuration Fallback


Purpose
FollowthisproceduretoactivateRAN2554:TransportConfigurationFallbackfeature.
Formoreinformationonthisfeature,seeDescriptionofRAN2554:Transport
ConfigurationFallback.ThefeaturecanbeactivatedusingBTSSiteManagerorNetAct
CMEditor.
Before you start
ThisfeaturerequiresthatFSMrel2(excludingFSIAandFSIB),FSMrel3,orFlexiLiteis
present.

194

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

5.6.2.1

Operabilityfeatures

Activating RAN2554: Transport Configuration Fallback using BTS


Site Manager

Open the BTS Site manager.

Download feature license to BTS.


a) In the Configuration menu, choose License Management.
b) A License Managament window opens. Select the appropriate license file
and click Download to BTS.

Enable transport configuration fallback.


a) In the Configuration menu, choose IP Configuration.
b) Choose IP Adresses tab.
OrintheIPview,choosetheIP Addressestab.
c) Check the Enable Transport Configuration Fallback checkbox.

5.6.2.2

Activating RAN2554: Transport Configuration Fallback from NetAct


CM Editor

Open NetAct CM Editor

Configure IPNO/enableTransportConfigFallback to "True".

Activate SCF in BTS from NetAct.


WhenenableTransportConfigFallbackissetto"True"usingSCFthen
correspondinglicenseisautomaticallydownloadedtoBTS.

5.6.3 Verifying RAN2554: Transport Configuration Fallback


Purpose
Followthisproceduretoverifythatthisfeaturehasbeenactivatedsuccessfully.

Activate the transport configuration fallback feature.


Formoreinformationsee,ActivatingRAN2554:TransportConfigurationFallback.

Testing the transport configuration fallback feature.


Formoreinformationsee,TestingRAN2554:TransportConfigurationFallback.

5.6.4 Deactivating RAN2554: Transport Configuration Fallback


Purpose

Issue:01ADRAFT

DN09146788

195

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

FollowthisproceduretodeactivateRAN2554:TransportConfigurationFall-back.For
moreinformation,seeDescriptionofRAN2554:TransportConfigurationFall-back.The
featurecanbeactivatedusingBTSSiteManagerorNetActCMEditor.
Before you start
MakesurethatRAN2554:TransportConfigurationFallbackfeatureisalreadyactivated.

5.6.4.1

Deactivating RAN2554: Transport Configuration Fallback using BTS


Site Manager

Disabling the feature


a) Open BTS Site manager.
b) Choose the IP Addresses tab.
c) Uncheck the Enable Transport Configuration Fallback checkbox.

5.6.4.2

Deactivating RAN2554: Transport Configuration Fallback from


NetAct CM Editor

Disabling the feature


a) Open NetAct CM Editor
b) Configure IPNO/enableTransportConfigFallback to "False".
c) Activate SCF in BTS from NetAct.

5.7 RAN2229: Troubleshooting Data Management by


NetAct
5.7.1 Description of RAN2229: Troubleshooting Data
Management by NetAct
Introduction to the feature
ThisfeatureallowsaNetActusertotriggersymptomdatacollectionfromRNCOMSand
IPA-RNCs,anduploadthecollectedsymptomdatafromthem.
ThisfeaturealsoprovidesthefunctionalityforRNCOMStoautomaticallytransfer
symptomdatageneratedfromit'smanagedRNCsandFlexiBTSstoNetAct,whetherit
wascreatedspontaneouslyduetoaninternaltrigger,orduetoanoperatorrequestfrom
alocalNEuserinterface.
Troubleshootingdatacanbecollectedbasedondifferentprofiles.Thisfeatureprovides
onlythe"Emergency"profilefordatacollectionfromtheRNCs.FeatureRAN2872will
provideadditionalprofilesfortroubleshootingdatacollection.

196

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

5.7.1.1

Operabilityfeatures

Benefits
Operator benefits
ThisfeatureprovidesOPEXsavingsfortheoperatorwhenresolvingproblemsthat
requiretroubleshootingdatatodiagnose.

5.7.1.2

Requirements
Software requirements
Thefollowingtablelistssoftwarerequiredforthisfeature.
Table123

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi Direct OMS


RNC

Flexi BTS

RU50EP1

Notplanned Supportnot
required

Supportnot
required

Notplanned OMS3.1

Supportnot
required

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

SGSN

MGW

UE

Supportnot
required

Supportnot
required

NetAct8
EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
Thisfeaturedoesnothaveanyhardwarerequirements.

5.7.1.3

Functional description
Thisfeatureprovidesacentralizedmechanismtorequestandcollecttroubleshooting
datafromvariousNetworkElements,eliminatingtheneedfortheusertologinto
individualNEsdirectly.TroubleshootingdataistransferredtotheOMS,storedthereand
forwardedtoNetAct,whichprovidesthecentralpointofcontrol.Simultaneouscollection
requestsarepossibleforatleastoneOMSandupto20RNCsmanagedbythatOMS.
RAN2229buildsuponthedatacollectionfunctionalityofRAN2199:BTSEventTriggered
SymptomDataCollection,RAN1805:AlarmtriggeredlogcollectionforRNC,RAN1873:
OMStroubleshootingdatacollectionandRAN2446:RNCsymptomdatacollection.

5.7.1.4

System impact
Interdependencies between features
RAN2229dependsuponthefollowingfeatures:

RAN2199:BTSEventTriggeredSymptomDataCollection
RAN1805:AlarmtriggeredlogcollectionforRNC
RAN1873:OMStroubleshootingdatacollection
RAN2446:RNCsymptomdatacollection

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Issue:01ADRAFT

DN09146788

197

Operabilityfeatures

RU50FeatureDescriptionsandInstructions

Impact on network and network element management tools


ThisfeatureaddsnewfunctionalitytotheNetActnetworkmanagementtool.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceandcapacity.

5.7.1.5

RAN2229: Troubleshooting Data Management by NetAct


management data
Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
TableRelatedexistingalarmslistsexistingalarmsrelatedtothisfeature.
Table124

Relatedexistingalarms

Alarm ID

Alarm name

71106

TROUBLESHOOTINGDATARECEIVED

71129

TROUBLESHOOTINGDATACREATIONORUPLOADFAILED

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
TableNewOMSLDAPparameterslistsparametersintroducedwiththisfeature.
Table125

NewOMSLDAPparameters

Attribute
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/NetActNotifyEnabled
ThisparametercontrolswhethertheOMSwillautomaticallyuploadtroubleshootingdatato
NetActwhenitisavailable.

198

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

5.7.1.6

Sales information
Table126

Issue:01ADRAFT

Operabilityfeatures

Salesinformation

BSW/ASW

SW component

License control in network element

BSW

RAN

DN09146788

199

Performancemonitoringfeatures

RU50FeatureDescriptionsandInstructions

6 Performance monitoring features


6.1 RAN2496: 3GPP Minimization of Drive Tests
6.1.1 Description of RAN2496: 3GPP Minimization of Drive Tests
Introduction to the feature
TheRAN2496:3GPPMinimizationofDriveTestsfeatureprovidesautomaticUser
Equipment(UE)measurementscollectionanddataloggingwhichreplacethemanual
drivetestingthattheoperatorshavetoperformintheirnetworks.MinimizationofDrive
Tests(MTD)allowsalsotoevaluatethenetworkperformanceperphysicallocation.

6.1.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
Thisfeatureminimizesthedrivetests,andthusallowssignificantcostsavingsinthe
coverageoptimizationduringnetworkdeploymentandmaintenance.

6.1.1.2

Requirements
Software requirements
Thefollowingtablelistssoftwarerequiredforthisfeature.
Table127

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi Direct OMS


RNC

Flexi BTS

RU50EP1

Notplanned RN8.1

mcRNC4.1

Notplanned Supportnot
required

WN9.1

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

SGSN

MGW

UE

NetAct8
EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Notplanned WN9.1

Hardware requirements
ThisfeaturerequirestheL3DataCollector(Megamon)connectedtotheRNC.ForL3
DataCollectorproduct-specificinformation,seeCareSoftware Supply Tool
Product Related ToolsL3 Data Collector (Megamon)inNOLSPIC.
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradio
SystemModuleFSMF.

200

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

6.1.1.3

Performancemonitoringfeatures

Functional description
Thegoalofthisfeatureistominimizethedrivetestsbyusingimmediate MDTmode
conceptintroducedin3GPPTS37.320.
TheimmediateMDTfunctionalityappliestoUEsinRRCCELL_DCHstateandsupports
thecollectionofthefollowingmeasurements:
Figure16

MDTmeasurements
MDTMEASUREMENTS

-CPICHRSCP andCPICHEc/No
-Downlinkblockerrorratio
(DL BLER)
-Rx-Txtimedifferencetype1
-GPSlocation

UE
(CELL_DCHstate)

BTS

RNC

L3DataCollector

TraceViewer

CommonPilotChannelreceivedsignalcodepower(CPICHRSCP)and
CommonPilotChannelratioofenergypermodulatingbittothenoisespectral
density(CPICHEc/No)
Downlinkblockerrorratio(DLBLER)
Rx-Txtimedifferencetype1
GPSlocation

Measurements reported by BTS:

NETACT

Measurements reported by UE:

-Signaltointerferenceratio(SIR)
-SIRerror
Datavolumeandactive
-Round-triptime(RTT)for
transfertimeto
R99andHSPA calls
Throughputcalculation
-Propagationdelay

Signaltointerferenceratio(SIR)
SIRerror
Round-triptime(RTT)forR99andHSPAcalls
Propagationdelay

Measurements reported by RNC:

DataVolumemeasurement(reportedseparatelyfordownlinkanduplink,per
QoSclass,andperUE)
Throughputmeasurement(reportedseparatelyfordowlninkanduplink,perRAB
perUE,andperUE)

Measurementscollectioncanbeenabledintwoways:

forallUEswithinthecellwiththeMDTPeriodicMeasEnabledparameterofthe
WCELobject
foraparticularconnection(perIMSI)withtheIMSIMeasMDTEnabledparameterof
theRNFCobjectandrelatedMML/SCLIcommandsinRNC

TheintervalfortheUEperiodicmeasurementreportiscontrolledwiththe
UePeriodicMeasIntervalparameteroftheRNCobject.

Issue:01ADRAFT

DN09146788

201

Performancemonitoringfeatures

6.1.1.4

RU50FeatureDescriptionsandInstructions

System impact
Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on network and network element management tools


L3 Data CollectorgathersthemeasurementdatawhileNetAct TraceViewerisusedto
presentthemeasurementreports.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

6.1.1.5

RAN2496: 3GPP Minimization of Drive Tests management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Faults and alarms


Therearenofaultsandalarmsrelatedtothisfeature.

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Thefollowingtablelistsparametersintroducedwiththisfeature.
Table128

Newparameters

Full name

Abbreviated name

Managed object

PeriodicMeasurementsinUE
andWBTSforMDT

MDTPeriodicMeasEnabled

WCEL

IMSIbasedMDT
Measurements

IMSIMeasMDTEnabled

RNFC

Pre-emptioncapabilityfor
emergencycall

EmeCallPCIValue

RNAC

Pre-emptionvulnerabilityfor
emergencycall

EmeCallPVIValue

RNAC

Prioritylevelforemergency
call

EmeCallLevelValue

RNAC

Thefollowingtablelistsparametersmodifiedbythisfeature.

202

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table129

6.1.1.6

Performancemonitoringfeatures

Modifiedparameters

Full name

Abbreviated name

Managed object

UEPeriodicMeasurement
ReportCPULimit

UePeriodicMeasCpuLimit

RNC(IPA-RNCspecific
parameter)

UEPeriodicMeasurement
ReportMeasurementsInterval

UePeriodicMeasInterval

RNC

Sales information
Table130

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCLK

6.2 RAN2443: BTS Resource Utilization Monitoring


6.2.1 Description of RAN2443: BTS Resource Utilization
Monitoring
Introduction to the feature
TheRAN2443:BTSResourceUtilizationMonitoringfeatureintroducescountersto
monitorresourceutilizationinsideaBTSonthefollowinglevels:

BTSlevel
FlexiSystemModulelevel
HSPASchedulerlevel
LocalCellGroup(LCG)level

ThisisinadditiontoexistingcountersthatenablemonitoringresourceutilizationinBTS
onthelevelofsubunits(SUs),throughput,andusers.

6.2.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
Thefeaturebenefitstheoperatorinthefollowingways:

Issue:01ADRAFT

Improvesmonitoringpossibilitiestoshowhowbasebandresourcescommissioned
ontheBTSandtheLCGlevelareassignedtotheactualBTShardwaremodules,
andthusproactivelyreacttopossiblecongestions.
IntroducestheresourcemonitoringonadditionallevelsperFlexiSystemModules
andperHSDPA/HSUPAScheduler.

DN09146788

203

Performancemonitoringfeatures

6.2.1.2

RU50FeatureDescriptionsandInstructions

Requirements
Software requirements
Table131:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
RAS

Flexi Direct IPA-RNC

mcRNC

Flexi Direct OMS


RNC

BTS
Flexi

Flexi Lite
BTS

RU50
EP1

Supportnot
required

Supportnot
required

Supportnot
required

WN9.1

Not
planned

Table131

Supportnot
required

OMS
3.1

Softwarerequirements

BTS Flexi
10

NetAct

MSC

SGSN

MGW

UE

WN9.1

NetAct8
EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradio
SystemModuleFSMF.

6.2.1.3

Functional description
TheRAN2443:BTSResourceUtilizationMonitoringintroducesthefollowingcounters:

countersinmeasurementM5006forlocalcellgroup(LCG)levelmonitoring:

newandmodifiedcountersinmeasurementM5008forBTSlevelmonitoring:

204

numberofavailableHSDPASUs
average/maximumnumberofHSDPAusers
average/maximumnumberofHSUPAusers
average/maximumHSDPAthroughput
average/maximumHSUPAthroughput
numberofavailableHSDPAusers
numberofavailableHSUPAusers
numberofavailableHSDPAthroughput
numberofavailableHSUPAthroughput
average/maximumHSDPAProcessingSetutilization
average/maximumHSUPAProcessingSetutilization
hardwareresourceutilizationclass1-6(0-100%)
availableoverlappingR99SUs
AverageR99usedfromoverlappingR99andHSUPASUs
AverageHSUPAusedfromoverlappingR99andHSUPASUs

numberoflicensedR99channelelements(R99CEs)
numberofconfiguredPICsubunits(SUs)
numberofconfiguredSUsforHS-FACHinuplink

countersinnewmeasurementM5011forschedulermonitoring:

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Performancemonitoringfeatures

average/maximumnumberofHDSPAusers
average/maximumachievedHSDPAthroughput
average/maximumachievedHSUPAthroughput
availableHSDPAthroughput
availableHSDPAusers
average/maximumnumberofHSUPAusers
availableHSUPAthroughput
availableHSUPAusers

countersinnewmeasurementM5012forFlexiSystemModule(FSM)level
monitoring:

maximumusedR99SUs
maximumusedHSUPASUs
numberofavailableR99SUs
numberofavailableHSUPASUs
numberofconfiguredHSUPASUs
numberofconfiguredPICSUs
numberofconfiguredSUsforHS-FACHinuplink
numberofusedCCCHSUs

CorrectionofthecounterspresentedintheTable133:Modifiedcountersisrelatedto:

6.2.1.4

Incounters:M5006C0toM5006C20
Themodificationisrelatedtothechangeofsamplingperiodfrom5secondsto5,12
seconds.
Incounters:M5006C27toM5006C38
IntheBTSitispossibletolicensemoreHSPAusersthanitissupportedbytheHW
capacity.Thecountersaremodified,bychangingthedenominator.Thesmallervalue
istakentothecounters:eitherthenumberofLicensedHSDPA/HSUPAusers,orthe
HWcapacitylimitofHSDPA/HSUPAusers.
Incounters:M5008C22-M5008C27
IntheBTSitispossibletolicensemoreHSPAusersandmoreHSPAthroughput
thanitissupportedbytheHWcapacity.Thecountersaremodified,bychangingthe
denominator.Thesmallervalueistakentothecounters,eitherthenumberof
LicensedHSDPA/HSUPAthroughput,ortheHWcapacitylimitofHSDPA/HSUPA
throughput.
Alsothechangeincalculatingeachsamplewasmadenowtheaveragevalueof
theusers,throughput,andhardware(onlyintheHSUPAcases)insteadofmaximum
istaken.
Incounters:M5008C40-M5008C41
IntheBTSitispossibletolicensemoreHSPAusersthanitissupportedbytheHW
capacity.Thecountersaremodified,bychangingthedenominator.Thesmallervalue
istakentothecounters:eitherthenumberofLicensedHSDPA/HSUPAusers,orthe
HWcapacitylimitofHSDPA/HSUPAusers.

System impact
Interdependencies between features
ThefollowingfeaturesareneedtobeactivatedbeforeactivationoftheRAN2443:BTS
ResourceUtilizationMonitoringfeature:

Issue:01ADRAFT

DN09146788

205

Performancemonitoringfeatures

RU50FeatureDescriptionsandInstructions

RAN2123:FlexiBTSGigabitBaseband
RAN2626:BasebandLoadMonitoring

ThefollowingfeaturesarerelatedtotheRAN2443:BTSResourceUtilizationMonitoring
feature:

RAN912:LicensebasedBTSchannelcapacity
RAN2262:FlexiMultiradioSystemModules
RAN2887:CCCHProcessingSet

Impact on interfaces
Thisfeatureimpactsthefollowinginterfaces:

BTS-RNC/OMS-NetAct:thetwonewmeasurements(M5011andM5012)withnew
countersaretransferredfromBTStoNetActviaexternalO&Minterface.
BTS-BTSManager:thetwonewmeasurements(M5011andM5012)withnew
countersaretransferredfromBTSOMtoBTSManagerviaO&Minterface.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


TheRAN2443:BTSResourceUtilizationMonitoringfeatureintroduceslargenumberof
newcounters,whichimpacttheOMSserverandNetAct.Thescopeofimpactdepends
onthetotalnumberofBTSsreportingtosingleOMSserver/NetActserver.

6.2.1.5

RAN2443: BTS Resource Utilization Monitoring management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Table132:Newcounterslistscountersintroducedwiththisfeature.
Table132

206

Newcounters

Counter ID

Counter name

Measurement

M5006C45

ALLOCATEDHSDPASUBUNITSINLCG

WBTSR99HWResource
(WBTS)

M5006C46

NUMBEROFR99PLUSHSUPA
OVERLAPPINGSUBUNITSINLCG

WBTSR99HWResource
(WBTS)

M5006C47

AVERAGEUSEDR99FROMOVERLAPPING WBTSR99HWResource
SUBUNITSINLCG
(WBTS)

M5006C48

AVERAGEUSEDHSUPAFROM
OVERLAPPINGSUBUNITSINLCG

DN09146788

WBTSR99HWResource
(WBTS)

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table132

Issue:01ADRAFT

Performancemonitoringfeatures

Newcounters(Cont.)

Counter ID

Counter name

M5006C49

LCGHWRESOURCEUTILIZATIONCLASS1 WBTSR99HWResource
(WBTS)

M5006C50

LCGHWRESOURCEUTILIZATIONCLASS2 WBTSR99HWResource
(WBTS)

M5006C51

LCGHWRESOURCEUTILIZATIONCLASS3 WBTSR99HWResource
(WBTS)

M5006C52

LCGHWRESOURCEUTILIZATIONCLASS4 WBTSR99HWResource
(WBTS)

M5006C53

LCGHWRESOURCEUTILIZATIONCLASS5 WBTSR99HWResource
(WBTS)

M5006C54

LCGHWRESOURCEUTILIZATIONCLASS6 WBTSR99HWResource
(WBTS)

M5006C55

MAXIMUMNUMBEROFHSDPAUSERSIN
LCG

WBTSlevelmonitoring
(WBTS)

M5006C56

AVERAGENUMBEROFHSDPAUSERSIN
LCG

WBTSlevelmonitoring
(WBTS)

M5006C57

AVAILABLENUMBEROFHSDPAUSERSIN
LCG

WBTSR99HWResource
(WBTS)

M5006C58

MAXIMUMNUMBEROFHSUPAUSERSIN
LCG

WBTSlevelmonitoring
(WBTS)

M5006C59

AVERAGENUMBEROFHSUPAUSERSIN
LCG

WBTSlevelmonitoring
(WBTS)

M5006C60

AVAILABLENUMBEROFHSUPAUSERSIN
LCG

WBTSR99HWResource
(WBTS)

M5006C61

MAXIMUMHSDPATHROUGHPUTINLCG

WBTSR99HWResource
(WBTS)

M5006C62

AVERAGEHSDPATHROUGHPUTINLCG

WBTSR99HWResource
(WBTS)

M5006C63

AVAILABLEHSDPATHROUGHPUTINLCG

WBTSR99HWResource
(WBTS)

M5006C64

MAXIMUMHSUPATHROUGHPUTINLCG

WBTSR99HWResource
(WBTS)

M5006C65

AVERAGEHSUPATHROUGHPUTINLCG

WBTSR99HWResource
(WBTS)

M5006C66

AVAILABLEHSUPATHROUGHPUTINLCG

WBTSR99HWResource
(WBTS)

M5006C67

MAXIMUMHSDPAPROCESSINGSETS
UTILIZATIONRATIO

WBTSR99HWResource
(WBTS)

M5006C68

AVERAGEHSDPAPROCESSINGSETS
UTILIZATIONRATIO

WBTSR99HWResource
(WBTS)

M5006C69

MAXIMUMHSUPAPROCESSINGSETS
UTILIZATIONRATIO

WBTSR99HWResource
(WBTS)

M5006C70

AVERAGEHSUPAPROCESSINGSETS
UTILIZATIONRATIO

WBTSR99HWResource
(WBTS)

DN09146788

Measurement

207

Performancemonitoringfeatures

Table132

208

RU50FeatureDescriptionsandInstructions

Newcounters(Cont.)

Counter ID

Counter name

Measurement

M5008C48

LICENSEDR99CESINBTS

WBTSlevelmonitoring
(WBTS)

M5008C49

CONFIGUREDPICSUBUNITSINBTS

WBTSlevelmonitoring
(WBTS)

M5008C50

CONFIGUREDHS-FACHSUBUNITSINBTS

WBTSlevelmonitoring
(WBTS)

M5011C0

MAXIMUMNUMBEROFHSDPAUSERSIN
SCHEDULER

HSPASchedulerMonitoring

M5011C1

AVERAGENUMBEROFHSDPAUSERSIN
SCHEDULER

HSPASchedulerMonitoring

M5011C2

AVAILABLEHSDPAUSERSINSCHEDULER

HSPASchedulerMonitoring

M5011C3

MAXIMUMHSDPATHROUGHPUTIN
SCHEDULER

HSPASchedulerMonitoring

M5011C4

AVERAGEHSDPATHROUGHPUTIN
SCHEDULER

HSPASchedulerMonitoring

M5011C5

AVAILABLEHSDPATHROUGHPUTIN
SCHEDULER

HSPASchedulerMonitoring

M5011C6

MAXIMUMNUMBEROFHSUPAUSERSIN
SCHEDULER

HSPASchedulerMonitoring

M5011C7

AVERAGENUMBEROFHSUPAUSERSIN
SCHEDULER

HSPASchedulerMonitoring

M5011C8

AVAILABLENUMBEROFHSUPAUSERSIN
SCHEDULER

HSPASchedulerMonitoring

M5011C9

MAXIMUMHSUPATHROUGHPUTIN
SCHEDULER

HSPASchedulerMonitoring

M5011C10

AVERAGEHSUPATHROUGHPUTIN
SCHEDULER

HSPASchedulerMonitoring

M5011C11

AVAILABLEHSUPATHROUGHPUTIN
SCHEDULER

HSPASchedulerMonitoring

M5012C0

MAXIMUMUSEDSUBUNITSFORR99IN
FSM

FSMLevelMonitoring
(WBTS)

M5012C1

MAXIMUMUSEDSUBUNITSFORHSUPAIN FSMLevelMonitoring
FSM
(WBTS)

M5012C2

NUMBEROFAVAILABLER99SUBUNITSIN
FSM

M5012C3

NUMBEROFAVAILABLEHSUPASUBUNITS FSMLevelMonitoring
INFSM
(WBTS)

M5012C4

CONFIGUREDHSDPASUBUNITSINFSM

FSMLevelMonitoring
(WBTS)

M5012C5

CONFIGUREDPICSUBUNITSINFSM

FSMLevelMonitoring
(WBTS)

M5012C6

CONFIGUREDHS-FACHSUBUNITSINFSM

FSMLevelMonitoring
(WBTS)

M5012C7

NUMBEROFUSEDCCCHSUBUNITSIN
FSM

FSMLevelMonitoring
(WBTS)

DN09146788

FSMLevelMonitoring
(WBTS)

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Performancemonitoringfeatures

Table133:Modifiedcounterslistscountersmodifiedbythisfeature.
Table133

Issue:01ADRAFT

Modifiedcounters

Counter ID

Counter name

Measurement

M5006C0

MAXIMUMNUMBEROF
AVAILABLER99CHANNEL
ELEMENTS

WBTSR99HWResource
(WBTS)

M5006C1

AVERAGENUMBEROF
AVAILABLER99CHANNEL
ELEMENTS

WBTSR99HWResource
(WBTS)

M5006C2

MINIMUMNUMBEROF
AVAILABLER99CHANNEL
ELEMENTS

WBTSR99HWResource
(WBTS)

M5006C3

MAXIMUMNUMBEROF
USEDR99CEFORDL

WBTSR99HWResource
(WBTS)

M5006C4

AVERAGENUMBEROF
USEDR99CEFORDL

WBTSR99HWResource
(WBTS)

M5006C5

MINIMUMNUMBEROFUSED WBTSR99HWResource
R99CEFORDL
(WBTS)

M5006C6

MAXIMUMNUMBEROF
USEDR99CEFORUL

WBTSR99HWResource
(WBTS)

M5006C7

AVERAGENUMBEROF
USEDR99CEFORUL

WBTSR99HWResource
(WBTS)

M5006C8

MINIMUMNUMBEROFUSED WBTSR99HWResource
R99CEFORUL
(WBTS)

M5006C9

BTSR99CHANNEL
ELEMENTTOTAL
UTILIZATIONINUL-CLASS
1

WBTSR99HWResource
(WBTS)

M5006C10

BTSR99CHANNEL
ELEMENTTOTAL
UTILIZATIONINUL-CLASS
2

WBTSR99HWResource
(WBTS)

M5006C11

BTSR99CHANNEL
ELEMENTTOTAL
UTILIZATIONINUL-CLASS
3

WBTSR99HWResource
(WBTS)

M5006C12

BTSR99CHANNEL
ELEMENTTOTAL
UTILIZATIONINUL-CLASS
4

WBTSR99HWResource
(WBTS)

M5006C13

BTSR99CHANNEL
ELEMENTTOTAL
UTILIZATIONINUL-CLASS
5

WBTSR99HWResource
(WBTS)

M5006C14

BTSR99CHANNEL
ELEMENTTOTAL
UTILIZATIONINUL-CLASS
6

WBTSR99HWResource
(WBTS)

M5006C15

BTSR99CHANNEL
ELEMENTTOTAL

WBTSR99HWResource
(WBTS)

DN09146788

209

Performancemonitoringfeatures

Table133
Counter ID

RU50FeatureDescriptionsandInstructions

Modifiedcounters(Cont.)
Counter name

Measurement

UTILIZATIONINDL-CLASS
1

210

M5006C16

BTSR99CHANNEL
ELEMENTTOTAL
UTILIZATIONINDL-CLASS
2

WBTSR99HWResource
(WBTS)

M5006C17

BTSR99CHANNEL
ELEMENTTOTAL
UTILIZATIONINDL-CLASS
3

WBTSR99HWResource
(WBTS)

M5006C18

BTSR99CHANNEL
ELEMENTTOTAL
UTILIZATIONINDL-CLASS
4

WBTSR99HWResource
(WBTS)

M5006C19

BTSR99CHANNEL
ELEMENTTOTAL
UTILIZATIONINDL-CLASS
5

WBTSR99HWResource
(WBTS)

M5006C20

BTSR99CHANNEL
ELEMENTTOTAL
UTILIZATIONINDL-CLASS
6

WBTSR99HWResource
(WBTS)

M5006C27

BTSHSPAUSERAMOUNT
UTILIZATIONINUL-CLASS
1

WBTSR99HWResource
(WBTS)

M5006C28

BTSHSPAUSERAMOUNT
UTILIZATIONUL-CLASS2

WBTSR99HWResource
(WBTS)

M5006C29

BTSHSPAUSERAMOUNT
UTILIZATIONUL-CLASS3

WBTSR99HWResource
(WBTS)

M5006C30

BTSHSPAUSERAMOUNT
UTILIZATIONUL-CLASS4

WBTSR99HWResource
(WBTS)

M5006C31

BTSHSPAUSERAMOUNT
UTILIZATIONUL-CLASS5

WBTSR99HWResource
(WBTS)

M5006C32

BTSHSPAUSERAMOUNT
UTILIZATIONUL-CLASS6

WBTSR99HWResource
(WBTS)

M5006C33

BTSHSPAUSERAMOUNT
UTILIZATIONDL-CLASS1

WBTSR99HWResource
(WBTS)

M5006C34

BTSHSPAUSERAMOUNT
UTILIZATIONDL-CLASS2

WBTSR99HWResource
(WBTS)

M5006C35

BTSHSPAUSERAMOUNT
UTILIZATIONDL-CLASS3

WBTSR99HWResource
(WBTS)

M5006C36

BTSHSPAUSERAMOUNT
UTILIZATIONDL-CLASS4

WBTSR99HWResource
(WBTS)

M5006C37

BTSHSPAUSERAMOUNT
UTILIZATIONDL-CLASS5

WBTSR99HWResource
(WBTS)

M5006C38

BTSHSPAUSERAMOUNT
UTILIZATIONDL-CLASS6

WBTSR99HWResource
(WBTS)

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table133

Performancemonitoringfeatures

Modifiedcounters(Cont.)

Counter ID

Counter name

Measurement

M5006C39

AVERAGENUMBEROF
WBTSR99HWResource
USEDBASEBANDSUBUNITS (WBTS)
INLCG

M5006C41

NUMBEROFAVAILABLE
BASEBANDSUBUNITSIN
LCG

WBTSR99HWResource
(WBTS)

M5006C43

MAXIMUMNUMBEROF
USEDHSUPASUBUNITSIN
LCG

WBTSR99HWResource
(WBTS)

M5006C44

NUMBEROFAVAILABLE
HSUPASUBUNITSINLCG

WBTSR99HWResource
(WBTS)

M5008C22

MINIMUMHSDPA
PROCESSINGSETS
UTILIZATIONRATIO

WBTSlevelmonitoring(WBT
S

M5008C23

AVERAGEHSDPA
PROCESSINGSETS
UTILIZATIONRATIO

WBTSlevelmonitoring(WBT
S

M5008C24

MAXIMUMHSDPA
PROCESSINGSETS
UTILIZATIONRATIO

WBTSlevelmonitoring(WBT
S

M5008C25

MINIMUMHSUPA
PROCESSINGSETS
UTILIZATIONRATIO

WBTSlevelmonitoring(WBT
S

M5008C26

AVERAGEHSUPA
PROCESSINGSETS
UTILIZATIONRATIO

WBTSlevelmonitoring(WBT
S

M5008C27

MAXIMUMHSUPA
PROCESSINGSETS
UTILIZATIONRATIO

WBTSlevelmonitoring(WBT
S

M5008C40

CONFIGUREDHSDPA
USERS

WBTSlevelmonitoring(WBT
S

M5008C41

CONFIGUREDHSUPA
USERS

WBTSlevelmonitoring(WBT
S

M5008C42

CONFIGUREDHSDPA
THROUGHPUT

WBTSlevelmonitoring(WBT
S

M5008C43

CONFIGUREDHSUPA
THROUGHPUT

WBTSlevelmonitoring(WBT
S

Key performance indicators


Thekeyperformanceindicatorswillbepresentedinthefuturereleases

Parameters
Therearenoparametersrelatedtothisfeature.

Issue:01ADRAFT

DN09146788

211

Performancemonitoringfeatures

6.2.1.6

RU50FeatureDescriptionsandInstructions

Sales information
Table134

Salesinformation

BSW/ASW

SW component

License control in network element

BSW

RAN

6.3 RAN2555: Configurable Ranges for User


Throughput Counters
6.3.1 Description of RAN2555: Configurable Ranges for User
Throughput Counters
Introduction to the feature
ThefeatureRAN2555:ConfigurableRangesforUserThroughputCountersenablesto
overcomecurrenthardcodingofrangesforRCPMthroughputclasscounters(existing
13DLand5ULcounters).
ThefeatureprovidesconfigurabilityoptionforRCPMthroughputcounters:

6.3.1.1

configurablebinsforthe13existingDLClassesand5ULclasses,
aggregationperdatavolumeinadditiontothepersession.

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
Thisfeatureimprovesmonitoringcapabilitiesbyadaptingmeasurementstothe
operatorsneeds.

6.3.1.2

Requirements
Software requirements
Softwarerequirementsliststhesoftwarerequiredforthisfeature.

212

RAS

Flexi Direct IPA-RNC

mcRNC

OMS

BTS Flexi

Flexi Lite

RU50
EP1

Notplanned RN8.1

mcRNC4.1

OMS3.1

Supportnot
required

Support
not
required

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Performancemonitoringfeatures

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

Supportnot
required

NetAct8EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
Thisfeaturedoesnotrequireanyneworadditionalhardware.

6.3.1.3

Functional description
Functional overview
TheRAN2555:ConfigurableRangesforUserThroughputCountersfeatureenablesto
overcomecurrenthardcodingofrangesforRCPMthroughputclasscounters(existing
13DLand5ULcounters).Theillustratesthedescribedsituation.
Figure17

ConfigurableRangesforUserThroughputCounters

nt M
ax
>8

>84

Mb

Mb

ps

8M
bps

4M
bps

4...

2M
bps
1...

2...

... 1
512

ps

Cur
re

s
Mb

ps

kbp

kbp
256

... 5

56
... 2
128

12

bps

8k

64.

.. 1
2

kbp
.. 6
4

32.

kbp
16

.. 3
2
16.

8...

4k
bps

8k
bps
4...

0...

NOW

kbp

Current situation: RCPM t.put counters lose visibility on the high scale of the t.put distribution.

Lost t.put scale, where most of the NEW


devices are located for the 4G concept

RAN2555 allows operators to CUSTOMIZE scale distribution for a full visibility, also for future release,
allowing a more precise throughput and data volume distributions observation

40.

>84

Mb
ps

0M
bps
.. 6

0M
bps
36.

.. 4

6M
bps
30.

.. 3

0M
bps
.. 3
25.

5M
bps
24.

.. 2

4M
bps
23.

.. 2

3M
bps
20.

.. 2

0M
bps
.. 2

.. 1
10.

8...

4...

12.

bps
10
M

bps
8M

bps
4M
0...

AFTER

2M
bps

EXAMPLE 1

Mb
ps
>84

0M
bps
.. 6
40.

0M
bps
.. 4
36.

6M
bps
.. 3
30.

0M
bps
.. 3
26.

5M
bps
.. 2
24.

4M
bps
.. 2
23.

bps

3M
bps
.. 2
20.

20
M
8...

bps
8M
6...

bps
6M
4...

bps
4M
2...

0...

2M

bps

EXAMPLE 2

Itispossibletoconfiguretherangesforthethroughputclasses,andtheprincipleof
counterupdatesfortheparametersaffectingRCPMcountersbehavior.
Configurable parameters to provide ranges for the throughput classes

Issue:01ADRAFT

DN09146788

213

Performancemonitoringfeatures

RU50FeatureDescriptionsandInstructions

UsingtheRAN2555:ConfigurableRangesforUserThroughputCountersfeature,when
the M1026C38 USER_DL_THRP_DIST_CLASS_5_W counterindicatesthePSsession
throughputbetween32...64kbit/s,itispossibletodefinethisrangeto,forexample,
128...256kbit/s.
Thenalsoothercountersrangesmusttobeadjustedcorrespondingly,toavoidthe
overlappingwitheachother.
Configurable parameter to choose the principle of counter updates
WithoutusingoftheRAN2555:ConfigurableRangesforUserThroughputCounters
feature,thecountercorrespondingtoachievedthroughput(withintheRCPMthroughput
classcountersfunctionality)isupdatedbyvalue1,whentheradiobeareris
reconfigured,orreleased,orsomemobilityeventsoccurs.
TheRAN2555:ConfigurableRangesforUserThroughputCountersfeatureenablesto
incrementthebytheamountofPSdatavolumetransferredduringthesessioncounter,
insteadofupdatingbyvalue1.

6.3.1.4

System impact
Interdependencies between features
Thisfeaturerequiresthefollowingfeatures:

RAN953:RadioConnectionPerformanceMeasurementsforRLCAcknowledged
Mode
RAN190:RadioConnectionPerformanceMeasurementsforRLCTMandUMand
OuterLoopPowerControl
RAN1188Pre-AggregationofRCPMDatainRNC

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on commands
Therearenocommandsrelatedtothisfeature.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

6.3.1.5

RAN2555: Configurable Ranges for User Throughput Counters


management data
Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

214

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Performancemonitoringfeatures

Measurements and counters


Therearenonewcountersrelatedtothisfeature.
Relatedexistingcounterslistsexistingcountersrelatedtothisfeature.
Table135

Issue:01ADRAFT

Relatedexistingcounters

Counter ID

Counter name

Measurement

M1017C34

USERDLTHROUGHPUTDISTRIBUTION
-CLASS1

RCPMRLC

M1017C43

USERDLTHROUGHPUTDISTRIBUTION
-CLASS10

RCPMRLC

M1017C50

USERDLTHROUGHPUTDISTRIBUTION
-CLASS11

RCPMRLC

M1017C52

USERDLTHROUGHPUTDISTRIBUTION
-CLASS13

RCPMRLC

M1026C34

USERDLTHROUGHPUTDISTRIBUTION
-CLASS1FORWCEL

RCPMRLCWCEL

M1026C43

USERDLTHROUGHPUTDISTRIBUTION
-CLASS10FORWCEL

RCPMRLCWCEL

M1026C50

USERDLTHROUGHPUTDISTRIBUTION
-CLASS11FORWCEL

RCPMRLCWCEL

M1026C52

USERDLTHROUGHPUTDISTRIBUTION
-CLASS13FORWCEL

RCPMRLCWCEL

M1027C34

USERDLTHROUGHPUTDISTRIBUTION
-CLASS1FORRNC

RCPMRLCRNC

M1027C43

USERDLTHROUGHPUTDISTRIBUTION
-CLASS10FORRNC

RCPMRLCRNC

M1027C50

USERDLTHROUGHPUTDISTRIBUTION
-CLASS11FORRNC

RCPMRLCRNC

M1027C52

USERDLTHROUGHPUTDISTRIBUTION
-CLASS13FORRNC

RCPMRLCRNC

M1017C53

USERULTHROUGHPUTDISTRIBUTION
-CLASS1

RCPMRLC

M1017C57

USERULTHROUGHPUTDISTRIBUTION
-CLASS5

RCPMRLC

M1026C53

USERULTHROUGHPUTDISTRIBUTION
-CLASS1FORWCEL

RCPMRLCWCEL

M1026C57

USERULTHROUGHPUTDISTRIBUTION
-CLASS5FORWCEL

RCPMRLCWCEL

M1027C53

USERULTHROUGHPUTDISTRIBUTION
-CLASS1FORRNC

RCPMRLCRNC

M1027C57

USERULTHROUGHPUTDISTRIBUTION
-CLASS5FORRNC

RCPMRLCRNC

DN09146788

215

Performancemonitoringfeatures

RU50FeatureDescriptionsandInstructions

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Newparameterslistsparametersintroducedwiththisfeature.
Table136

216

Newparameters

Full name

Abbreviated name

ConfigureRangesforRCPMUser
ThroughputCountersenabled

ConfigurableRCPMtputEnable RNFC
d

RCPMthroughputcountersaggregation
Level

RCPMtputAggregationLevel

RNC

RCPMDLthroughputclass01toclass
02rangelimit

RCPMtputDLCl01to02Range

RNC

RCPMDLthroughputclass02toclass
03rangelimit

RCPMtputDLCl02to03Rangel

RNC

RCPMDLthroughputclass03toclass
04rangelimit

RCPMtputDLCl03to04Range

RNC

RCPMDLthroughputclass04toclass
05rangelimit

RCPMtputDLCl04to05Range

RNC

RCPMDLthroughputclass05toclass
06rangelimit

RCPMtputDLCl05to06Range

RNC

RCPMDLthroughputclass06toclass
07rangelimit

RCPMtputDLCl06to07Range

RNC

RCPMDLthroughputclass07toclass
08rangelimit

RCPMtputDLCl07to08Range

RNC

RCPMDLthroughputclass08toclass
09rangelimit

RCPMtputDLCl08to09Range

RNC

RCPMDLthroughputclass09toclass
10rangelimit

RCPMtputDLCl09to10Range

RNC

RCPMDLthroughputclass10toclass
11rangelimit

RCPMtputDLCl10to11Range

RNC

RCPMDLthroughputclass11toclass
12rangelimit

RCPMtputDLCl11to12Rangeg

RNC

RCPMDLthroughputclass12toclass
13rangelimit

RCPMtputDLCl12to13Range

RNC

DN09146788

Managed object

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table136

Performancemonitoringfeatures

Newparameters(Cont.)

Full name

Abbreviated name

Managed object

RCPMULthroughputclass01toclass
02rangelimit

RCPMtputULCl01to02Range

RNC

RCPMULthroughputclass02toclass
03rangelimit

RCPMtputULCl02to03Range

RNC

RCPMULthroughputclass03toclass
04rangelimit

RCPMtputULCl03to04Range

RNC

RCPMULthroughputclass04toclass
05rangelimit

RCPMtputULCl04to05Range

RNC

Modified parameters
Therearenomodifiedparametersrelatedtothisfeature.

6.3.1.6

Sales information
Table137

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCLK

6.4 RAN2930: IMSI-based Call Monitoring


6.4.1 Description of RAN2930: IMSI-based Call Monitoring
Introduction to the feature
Inthecurrentsystemimplementation,itisonlypossibletoperformUEmonitoringwitha
Layer3DataCollector(L3DC)andaLayer3Dataanalyzer(Emil).TheRAN2930:IMSIbasedCallMonitoringfeatureallowstheoperatortostarttheUEmonitoringwithout
Layer3DataCollector(L3DC).
ExtendedRNCdatasetsrelevantforsolvingUEKPIproblemsarecapturedfor
predefinedIMSI,includingmessages,logs,packetheaders,statistics:

Issue:01ADRAFT

ControlPlane
UserPlane
TransportPlane

DN09146788

217

Performancemonitoringfeatures

6.4.1.1

RU50FeatureDescriptionsandInstructions

Benefits
End-user benefits
FasttroubleshootingRNCcallrelatedissues,duetoonetimecollectionofallneeded
datarelatedtocertaincall.

Operator benefits
Operatorcanmonitormultiplecalls(Testmobiles)withoutextrahardware.

6.4.1.2

Requirements
Software requirements
Table138:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
Table138

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

Flexi Direct OMS


RNC

Flexi BTS

RU50EP1

Notplanned RN8.1

mcRNC4.1

Notplanned Supportnot Support


required
not
required

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

SGSN

Supportnot
required

Supportnot
required

Supportnot Supportnot Supportnot Supportnot


required
required
required
required

MGW

UE

Support
not
required

Hardware requirements
Thisfeaturedoesnotrequireadditionalhardware.

6.4.1.3

Functional description
Functional overview
AsthenumberofconnectedusersperRNCandend-userdataratescontinuetogrow,
sodoesthecomplexityinbeingabletotroubleshootproblemsrelatedtoindividualcalls.
Typicalusecasesfortroubleshootingindividualcallsinclude(basedon3GPPTS32.421
Subscriberandequipmenttrace;Traceconceptsandrequirements):

218

MultivendorUEvalidation:checkhowdifferentvendor'sUEsareworking
Subscribercomplaint:checkhowthesubscriber'sservicesareworkinginorderto
findoutthereasonforthecomplaint
MalfunctioningUE:whentheoperatorsuspectsthataUEisnotworkingaccordingto
thespecifications
Checkingradiocoverageonaparticulargeographicalarea

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Performancemonitoringfeatures

Testinganewfeature
Fine-tuningandoptimizationofalgorithms/procedures

Figure18

OverviewofRAN2930:IMSI-basedCallMonitoring

ThisfeatureintroducesacollectionofControl,User,andTransportplanesmonitoring
dataforindividualcallsbasedongivenIMSInumbers.Thedatacapturing,processing,
andanalyzingisdonewiththehelpofanexternalmonitoringtoolhavingagraphicaluser
interface,runningonastandardWindowsPC,andconnectedremotelytothemonitored
RNC.Themainbenefitofthisfeatureisthatitallowsasmallsizeofthemonitoreddata
whileprovidingcomprehensivemonitoreddatacontentforindividualmonitoredcalls.
Notethatneitherend-usercommunicationcontent,thatisend-userspeechanddata,nor
messagesrelatedtoanyothercall(s)(uninterestedcalls)iscollectedbythisfeature.
Monitoreddatacontent
1. ControlPlaneincontrolplaneprocessingunits(ICSUinRNC2600andUSCPin
mcRNC):

DMXmessagesfrommostofcallhandlingprogramfamilies

2. UserPlaneinuserplaneprocessingunits(DMPG/DSPinRNC2600,notsupported
inmcRNCinthisrelease):

Issue:01ADRAFT

DN09146788

219

Performancemonitoringfeatures

RU50FeatureDescriptionsandInstructions

ProtocolheadersonIu-PS:GTP-U
ProtocolheadersonIu-CS:RTP,RTCP(notinRNC2600)andIu-CSUP
ProtocolheadersonIub/Iur:FP,MAC,RLCandPDCP
InternalmessagesrelatedtoL3-L2interfaces
L2internalprotocolinterfaces(suchasRLC-MAC),internaldata(suchas
schedulinginfo),minorandsevereerrors,exceptions

3. TransportPlaneintransportplaneprocessingunits(NPGEinRNC2600,not
supportedinmcRNCinthisrelease):

ProtocolheadersonIu-PS:outerIP,UDP,GTP-U,innerIP,innerTCP/ICMP/UDP
Iu-CS:IP/UDP/RTP/IuUPheaders,IP/UDP/RTCPfullpacket
Iub/Iur:IP/UDP/FPheadersandMAC/RLCheadersofthefirstPDU

Siteconfiguration

6.4.1.4

InRNC2600,themonitoreddatacollectionisperformedviaO&Mconnectionto
RNC.
InmcRNC,it'srequiredtoinstallEthernetswitchonsiteasthemonitoreddata
collectionisdoneviaoneSFPportineachBCNbox.ExistingMegamon/L3Analyzer
installedsolutioncanbere-used.

System impact
Interdependencies between features
Informationonthisfeaturesimpactoninterdependenciesbetweenfeatureswillbe
providedinfurtherdeliveries.

Impact on network and network element management tools


Informationonthisfeaturesimpactoninterfaceswillbeprovidedinfurtherdeliveries.

Impact on system performance and capacity


Informationonthisfeaturesimpactonsystemperformanceandcapacitywillbeprovided
infurtherdeliveries.

6.4.1.5

RAN2930: IMSI-based Call Monitoring management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Therearenomeasurementsandcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

220

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Performancemonitoringfeatures

Parameters
Therearenoparametersrelatedtothisfeature.

6.4.1.6

Sales information
Table139

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCLK

6.5 RAN2870: Traffica IP Reports at mcRNC for RTT


and Packet Loss Ratio
6.5.1 Description of RAN2870: Traffica IP Reports at mcRNC for
RTT and Packet Loss Ratio
Introduction to the feature
RAN2870:TrafficaIPReportsatmcRNCforRTTandPacketLossRatiofeatureenables
mcRNCtohavecountersforround-triptime(RTT)andpacketlossratio(PLR).

6.5.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
Thisfeaturebenefitstheoperatorasfollows:

6.5.1.2

Real-timemonitoringofthenetwork'scondition,whichleadstoaquickreactionto
potentialservicedegradations.
Eliminatestheacquisitionofadditionalhardwareormeasurementequipmentto
monitorthenetwork.

Requirements
Software requirements
Thefollowingtableliststhesoftwarerequiredforthisfeature.
Table140

Issue:01ADRAFT

Softwarerequirements

RAS

IPA-RNC

mcRNC

RU50EP1

Availablein
mcRNC4.1
earlierrelease

DN09146788

Flexi Direct
RNC

OMS

BTS Flexi

Supportnot
required

Notrelevant

Supportnot
required

221

Performancemonitoringfeatures

RU50FeatureDescriptionsandInstructions

Flexi Lite

BTS Flexi
10

NetAct

MSC

SGSN

MGW

UE

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

ThesamefunctionalityisavailableinIPA-RNCwith
RAN2402:TrafficaIPReportsforRTTandPacketLossRatiofeature.

Hardware requirements
ThisfeaturerequiredTrafficatooltobeoperational.

Other requirements
TouseRAN2870:TrafficaIPReportsatmcRNCforRTTandPacketLossRatiofeature,
RAN1900:IPTransportNetworkMeasurementfeaturemustbeactivated.
FormoredetailsonsoftwareandhardwarerequirementsforTraffica,seetherelevant
Trafficadocumentation.

6.5.1.3

Functional description
RAN2870:TrafficaIPReportsatmcRNCforRTTandPacketLossRatioenablesTraffica
tomonitorIub,Iu,andIurIP-basedinterfacesinrealtimetosupportmcRNC.
Withthisfeature,Trafficaprovidesthefollowingmeasurementdatareportsa60-second
interval:

round-triptime(RTT)
packetlossratio(PLR)

RAN2870:TrafficaIPReportsatmcRNCforRTTandPacketLossRatiousestheTwoWayActiveMeasurementProtocol(TWAMP)inmcRNC.TWAMPisusedtomeasure
andmonitorIPnetworkconditionsbetweentwonetworkelements.
TheRNCservesastheTWAMPsender,asshowninFigure1MeasuringRTTandPLR
withTWAMP,whichcollectsIPnetworksqualityofservice(QoS)measurementdata
fromthenetwork.TheTWAMPsendersessiongeneratestesttrafficbasedontheIETF
definedTWAMPprotocolRFC5357.TheRNCdoestheanalysisandtherelated
measurementsdataresultsareprovidedtotheTrafficatool.TheBTSontheotherend
servesasUserDatagramProtocol(UDP)echoserverorTWAMPresponder.

222

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Figure19

Performancemonitoringfeatures

MeasuringRTTandPLRwithTWAMP

BTS UDP
echo server OR
TWAMP responder

RNC
TWAMP sender

Traffica

Router
UDP echo server

SGSN

RNC
UDP echo server

ThemeasurementreportsareonlyvisibleintheTrafficatoolbasedonthereporttype
thattheRNCprovides.Thesemeasurementreportsareusedtoassessthequalityand
performanceoftheIP-basedtransportnetworkforeachQoSclassindependentlyas
indicatedbytheDifferentiatedServicesCodePoint(DSCP).
Formoreinformation,seeRAN1900:IPTransportNetworkMeasurementand
RAN2255:IPTransportMeasurementInitiatedfromRNCandFlexiDirectBTS.

6.5.1.4

System impact
Interdependencies between features
RAN2870:TrafficaIPReportsatmcRNCforRTTandPacketLossRatiodependson
RAN2255:IPTransportNetworkMeasurementInitiatedfromRNCandFlexiDirectBTS
andRAN1900:IPTransportNetworkMeasurementfeatures.

Impact on interfaces
ATrafficareporttypeisintroducedtoindicateRTTandPLRtosupportmcRNC.

Impact on network and network element management tools


ThefeatureenhancestheTrafficatoolfunctionssothatIP-relatedmonitoringcanbe
performedbothoncorenetwork(CN)andradioaccessnetwork(RAN)interfaces.

TheTrafficatoolmustbeupdatedtosupportthenewreport.ThesameTraffica
supportinRAN2402:TrafficaIPReportsforRTTandPacketLossRatiois
needed.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

Issue:01ADRAFT

DN09146788

223

Performancemonitoringfeatures

6.5.1.5

RU50FeatureDescriptionsandInstructions

RAN2870: Traffica IP Reports at mcRNC for RTT and Packet Loss


Ratio management data
Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


ThefollowingarethecountersthatarereportedforeachmonitoredIP-transportpathat
60-secondinterval:

averageround-triptime
minimumround-triptime
maximumround-triptime
numberofsentTWAMPmeasurementrequestpackets
numberoflostTWAMPmeasurementpackets

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table2ParametersliststheparametersthatareintroducedintheIPplaninterfacewith
thisfeature.
Table141

Parameters

Full name

Abbreviated name

Managed object

DestinationIPaddress

destIpAddr

TWAMPS

DestinationUDPport

destIpPort

TWAMPS

DSCPvaluefortesttraffic

dscpVal

TWAMPS

Packetsendingfrequency

freqOfPacket

TWAMPS

IPTWAMPsendersessionID

ipSenderSessId

TWAMPS

Lengthofthetestpacket

lenOfPacket

TWAMPS

SourceIPaddress

srcIpAddr

TWAMPS

Sessionstate

stateOfsession

TWAMPS

Commands
ThefollowingsCLIcommandsareusedtocreateTWAMPsessions:

224

add networking monitoring twamp sendertostartTWAMPmonitoring


delete networking monitoring twamp sendertostopTWAMPmonitoring

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

6.5.1.6

Sales information
Table142

Issue:01ADRAFT

Performancemonitoringfeatures

Salesinformation

BSW/ASW

SW component

License control in network


element

ASWNetAct

Thelicensecontrolof
RAN2870:TrafficaIPReportsatmcRNCforRTTandPacketLossRatiocomes
fromtheTrafficatool.

DN09146788

225

RNCsolutionfeatures

RU50FeatureDescriptionsandInstructions

7 RNC solution features


7.1 RAN2251: Automatic mcRNC Resource
Optimization
7.1.1 Description of RAN2251: Automatic mcRNC Resource
Optimization
Thisfeatureenablestheoptimalusageofuserplaneandcontrolplaneresourcesfor
mcRNC.Switchingtotheoneofthepre-setconfigurationsismademanuallyorthrough
themcRNCinternalfunctionalityaccordingtomcRNCloadanalysisindifferentunits.

7.1.1.1

RAN2251 benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
TheoperatorcanusemcRNCresourcesmostefficientlyandreachthemaximum
mcRNCcapacityforeverykindoftrafficmix.

7.1.1.2

RAN2251 requirements
Software requirements
Thefollowingtablelistssoftwarerequiredforthisfeature.
Table143
RAS

Softwarerequirements
Flexi Direct

RU50EP1 Notrelevant

IPA-RNC

mcRNC

Notrelevant mcRNC4.1

OMS

BTS Flexi

Flexi Lite

OMS3.1

Supportnot
required

Supportnot
required

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

Supportnot
required

NetAct8EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

ThisfeaturerequiresRAN2324:mcRNCresourcemanagementfeatureactivated.

Hardware requirements
ThisfeaturerequiresMulticontrollerRNCRel.2HW.

226

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

7.1.1.3

RNCsolutionfeatures

RAN2251 functional description


Introduction to the feature
InthemcRNC,asingletypeofresourceisusedtohandleallthetrafficintheprocessing
planes.Theresourcesareallocatedinthemulticoreprocessoradd-incardswhichactas
processingunits.Actingrolesarestrictlydefinedbytheinstalledapplicationsoftware.
TheRAN2251:AutomaticmcRNCResourceOptimizationfeatureenablesthe
optimizationoftheresourceallocationwithinacardactingasaUE-specificprocessing
unit(USPU)duringthemcRNCsystemrunningtimeasitisshowninFigure20:
Automaticresourceoptimizationbetweenprocessingplanes.
Figure20

Automaticresourceoptimizationbetweenprocessingplanes

mcRNC

Follow-upand
controlbyCFPU

Processor/USPU

UserPlane
resources

ControlPlane
resources

Whiletheloadofthesystemchangesaccordingtousersbehavior,thefeatureadjusts
resourceallocationbetweenUE-SpecificfunctionsandservicesinControlPlane
(USCP),andUE-SpecificfunctionsandservicesinUserPlane(USUP)handledbyUEspecificProcessingUnit(USPU).TheloadofUSCPandUSUP,whicharecalled
functionalunits(FU),isconstantlymonitoredbyresourcemanagers.Centralized

Issue:01ADRAFT

DN09146788

227

RNCsolutionfeatures

RU50FeatureDescriptionsandInstructions

resourcemanagerreceivesaloadmessage.Itcantriggerlocalresourcemanagerto
movecores,whichhandlespecifiedfunctionsandservicesfromoneFUtoanother.
Whentheresourceassignmentdoesnotfollowsystemloadchangesandother
conditionsarefulfilled,localresourcemanagerdecidestomovecoresbetweenuser
planeandcontrolplane.Thisprocessshiftsresourcesfromless-loadedtomaximumloadedplane.LocalresourcemanagerconstantlytrackstheloadradiobetweenUSCP
andUSUPbycollectingrelevantuserplaneandcontrolplaneloadinformation.
ThemcRNCoptimizestheresourceallocationbasedonmeasurementhistorytomeet
thetrafficprofileinthenetwork.Ifthefillrateisnotbalancedcomparedtothesoftwaredefinedshares,themcRNCautomaticallytriggersamechanismthatwilladaptthetraffic
profileinthenetwork.
ThefeaturefunctionsinternallyinthemcRNCanddoesnotaffectanymcRNCexternal
functions.ThereisnoneedtoreleaseanyUEs,shutdowncells,orcutongoingtrafficto
optimizeresources.
Theoperatordoesnotneedtodoanyadditionalactionsafterthefeatureisactivated.
Thefeaturecanbeusedconstantlyandsimultaneouslywithanyotherfeature.

7.1.1.4

RAN2251 system impact


Interdependencies between features
ThisfeaturerequiresRAN2324.

Impact on interfaces
ThisfeatureenablesControlandUserPlanesloadoptimization.

Impact on commands
ThefollowingSCLIcommandsarerelatedtothisfeature:

show troubleshooting core-reallocate history unit USPU

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkandnetworkelementmanagementtools.

Impact on system performance and capacity


Thisfeatureallowstoreachmaximumcapacityforeverykindoftrafficmix.

7.1.1.5

RAN2251: Automatic mcRNC Resource Optimization management


data
Alarms
Table144:Newalarmslistsalarmsintroducedwiththisfeature.
Table144

Newalarms

Alarm ID Alarm name

228

3560

USERPLANEPROCESSINGRESOURCESHORTAGE

3785

AUTOMATICRESOURCEOPTIMIZATION

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

RNCsolutionfeatures

Measurements and counters


Table145:Modifiedcounterslistscountersmodifiedbythisfeature.
Table145

Modifiedcounters

Counter ID Counter Name

Measurement

M2002C3

MinimumCPUUsage

CPUUsageCoreLevel

M2002C4

MaximumCPUUsage CPUUsageCoreLevel

M2002C5

AverageCPUUsage

CPUUsageCoreLevel

M2007C3

MinimumCPUUsage

CPUUsageNodeLevel

M2007C4

MaximumCPUUsage CPUUsageNodeLevel

M2007C5

AverageCPUUsage

CPUUsageNodeLevel

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

7.1.1.6
Table146

RAN2251 sales information

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCLK

7.2 RAN2928: DSP Pool Information in Measurements


7.2.1 Description of RAN2928: DSP Pool Information in
Measurements
Introduction to the feature
SeveralDSPprocessesareexecutedintheRNCtoensurethattheusageofthedigital
signalprocessor(DSP)isoptimized.ThemainDSPprocessesareDSPservicepooling
andDSPmeasurement.TheformerenablestheoptimaluseoftheDSPs,whilethelatter
providesdataonthe:

numberofcallsbasedontheservicetype
peaknumberofconnections
failedconnectionattempts
numberofrejectedcalls
numberofconnectedannouncements.
CPUload,memoryusageandprocessesnumberofDSPs

TheRAN2928:DSPPoolInformationinMeasurementsfeatureenhancestheaccuracy
oftheDSPmeasurementandimprovesDSPresourcemanagement.Thisgivesthe
operatormorepreciseknowledgeaboutstatisticalinformation,whichishelpfulfor
networkanalysisandoptimization.

Issue:01ADRAFT

DN09146788

229

RNCsolutionfeatures

7.2.1.1

RU50FeatureDescriptionsandInstructions

RAN2928 benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
OperatorhasmoreaccuratevisibilityoftheDSPloadwiththisfeature.Thisallowsto
gainprecisemeasurementdatafornetworkanalysisandoptimization.

7.2.1.2

RAN2928 requirements
Software requirements
Thefollowingtablelistssoftwarerequiredforthisfeature.
Table147

Softwarerequirements

RAS

Flexi Direct

IPA-RNC

mcRNC

OMS

BTS Flexi

Flexi Lite

RU50
EP1

Supportnot
required

RN8.1

Supportnot
required

OMS3.1

Supportnot
required

Supportnot
required

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

Supportnot
required

NetAct8EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
ThisfeaturerequiresRNC2600.

7.2.1.3

RAN2928 functional description


Before the feature is activated
TheDSPLOADMEASUREMENT(M617)countersaredatafromalloftheDSPs
groupedinthedataandmacrodiversityprocessorgroup(DMPG).Themeasureddata
providedbyM617istheaverageDSPloadvaluefromtheDSPsgroupedtooneDMPG.
SeeFigure21:DSPloadmeasurementbeforethefeatureactivationforanoverviewof
themeasurementprocess:

230

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Figure21

RNCsolutionfeatures

DSPloadmeasurementbeforethefeatureactivation

DMPG

DSP1

DSP2

M617

DSP Group
LoadData

After the feature is activated


ByactivatingtheRAN2928:DSPPoolInformationinMeasurementsfeaturetheM617
measurementisupgradedtoprovidesingleDSP-leveldata.SeeFigure22:DSPload
measurementafterthefeatureactivation

Issue:01ADRAFT

DN09146788

231

RNCsolutionfeatures

RU50FeatureDescriptionsandInstructions

Figure22

DSPloadmeasurementafterthefeatureactivation

DMPG

DSP1

DSP2

DSP1
LoadData

DSP2
LoadData

M617

foranoverviewofthemeasurementprocessafterthefeatureactivation.Theupgraded
M617measurementreportcontainsinformationrelatedtotheDSPservicepool.This
upgradegivestheuserevenmoreaccurateloadsituationoverviewindifferentDSP
servicepools.Withthisfeatureactivated,theusercanimprovetheefficiencyofnetwork
analysisandoptimization.

7.2.1.4

RAN2928 system impact


Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkandnetworkelementmanagementtools.

Impact on system performance and capacity


ThisfeaturechangesmeasurementM617objectfromDMPGtoDSP,sothe
measurementobjectsnumberisdoubled.Thisobjectmeasurementincreasedoesnot
impactonsystemperformance.
Thisfeaturehasnoimpactonsystemcapacity.

7.2.1.5

RAN2928: DSP Pool Information in Measurements management data


Formoreinformationonalarm,counter,keyperformanceindicator,andparameter
documents,seeReferencedocumentation.

232

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

RNCsolutionfeatures

Alarms
Therearenoexistingalarmsrelatedtothisfeature.

Measurements and counters


Table148:Newcounterslistscountersintroducedwiththisfeature:
Table148

Newcounters

Counter ID Counter name


M617C20

Measurement

DSP_SERVICE_POOL_TYPE DSPLoad

Key performance indicators


Therearenoexistingkeyperformanceindicatorsrelatedtothisfeature.

Parameters
Therearenoexistingparametersrelatedtothisfeature.

7.2.1.6

RAN2928 sales information


Table149

Salesinformation

BSW/ASW

SW component

License control in network element

BSW

RAN

7.2.2 Testing [Feature ID]: [Feature Name]


Before you start

1
Result

7.3 RAN2959: mcRNC Step 7 Support


7.3.1 Description of RAN2959: mcRNC Step 7 Support
Introduction to the feature
Thisfeatureaddsthecapacitystep7(S7-B2)supporttothemcRNCHWRel.2
configurations.ThemcRNCHWcapacityexpansionfromS3-B2toS7-B2isalso
supported.

7.3.1.1

RAN2959 benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Issue:01ADRAFT

DN09146788

233

RNCsolutionfeatures

RU50FeatureDescriptionsandInstructions

Operator benefits
Thisfeaturebenefitstheoperatorasfollows:

7.3.1.2

highcapacityRNC.
capacityexpansionfromlowercapacitysteptohighercapacitystep

RAN2959 requirements
Software requirements
Thefollowingtablelistssoftwarerequiredforthisfeature.
Table150

Softwarerequirements

RAS

Flexi Direct

IPA-RNC

mcRNC

OMS

BTS Flexi

Flexi Lite

RU50
EP1

Supportnot
required

Supportnot
required

mcRNC4.1

OMS3.1

Supportnot
required

Supportnot
required

Table151

Softwarerequirements

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

Supportnot
required

NetAct8
EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
ThisfeatureissupportedonlyformcRNCRel.2HW(BCN-B2HW).

7.3.1.3

RAN2959 functional description


ThisfeatureoffersmcRNChardwarecapacitystepS7-B2(8BCN-Bmodule
configuration)supporttoincreasemcRNCcapacityandcellconnectivity.ThemcRNC
hardwarecapacityexpansionfromS3-B2(4BCN-Bmoduleconfiguration)toS7-B2is
alsosupportedwiththefeature.
ThemcRNCHWcapacityexpansiondoesnotrequireanyRNCrestart.TheRNCandall
BTS'scellserviceremainsalthoughRNCcapacityisreducedduringtheHWexpansion
period.ThemcRNCHWexpansiontimewithreducedRNCcapacityislessthanfour
hours.
Enablingthisfeaturetakestenhoursintotal.Itisrecommendedtoperformthehardware
expansionwithinamaintenancewindow.PreparationworkfortheHWexpansion,
withoutimpactingtheRNC'scapacityandperformance,isneeded.Thepreparationwork
isdonewithinsixhoursofonenormalday.IncaseofafailedmcRNCHWexpansion,
mcRNCisabletogobacktotheoriginalconfigurationbyrestartingtheRNC.
Havinghardwareexpansiondone,theuserdoesBTSresourcere-balancingtomake
RNCloadsharing.
TheRAN2959:mcRNCStep7SupportincreasesmcRNCcapacity.Seetocheck
mcRNCstep7capacityfigures.

234

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table152

RNCsolutionfeatures

mcRNCstep7capacity

Configuration/capacity

S7-B2

User plane capacity


AMRErlangs

113000

AMRErlangs(includingsofthandover)

158200

Userplanethroughput(IubtotalinMbps)

20000

DLuserplanethroughput(IubtotalinMbps)

14000

ULuserplanethroughput(IubtotalinMbps)

6000

Control plane capacity


RNCsubscribers

4520000

AMRBusyHourCallAttempts

4520000

PSBusyHourCallAttempts1

7920000

PSSessionBusyHourCallAttempts

15800000

SmartphoneBusyHourCallAttempts2

6660000

TotalBusyHourCallAttempts3

25200000

NASBusyHourCallAttempts(ontopofmaximumcallcapacity) 17300000
MaxnumberofRRCconnectedUE's

1000000

Connectivity

7.3.1.4

Maxnumberofcells

10000

MaxnumberofBTSsites

2000

PacketSwitchedRadioAccessBearerBusyHourCallAttempts
(BHCA)assuming2xPSHSPAsessionperRAB

TotalPacketSwitchedandCircuitSwitchedBHCAfortrafficmix
assuming20%basicphones,79%smartphones,1%laptops

PacketSwitchedBHCAandNon-AccessStratum(NAS)BHCA

RAN2959 system impact


Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on network and network element management tools


Therearenocommandsrelatedtothisfeature.

Issue:01ADRAFT

DN09146788

235

RNCsolutionfeatures

RU50FeatureDescriptionsandInstructions

Impact on system performance and capacity


Thisfeatureincreasessystemcapacity.

7.3.1.5

RAN2959: mcRNC Step 7 Support management data


Forinformationonalarm,counter,keyperformanceindicator,andparameter
documentationseeReferencedocumentation.

Alarms
Therearenoexistingalarmsrelatedtothisfeature.

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators.


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Therearenoexistingparametersrelatedtothisfeature.

7.3.1.6

RAN2959 sales information


Table153

Salesinformation

BSW/ASW/HW

SW Component

License in network element

HW

RAN

7.4 RAN2512: RNC Resiliency for RNC2600


7.4.1 Description of RAN2512: RNC Resiliency for RNC2600
Introduction to the feature
TheRAN2512:RNCResiliencyforRNC2600featureimprovesnetworkavailability.This
featureallowsRANnetworkrecoveryfromfatalHWfailureofasingleRNCoranRNC
site.WhenonephysicalRNChasfailed,theoperatorisabletocommandtheearlier
configuredandsynchronizedbackupphysicalRNCtotakeovertheresponsibilityofthe
failedphysicalRNC.ThebackupphysicalRNCtakesovertheresponsibilityaftera
restart.Thisfeaturehelpstoavoidlongoutages,lastingmanyhoursordays.

7.4.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
ThisfeatureshortenstheRNC2600outageintheradionetwork.

236

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

7.4.1.2

RNCsolutionfeatures

Requirements
Software requirements
Table154:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
Table154

Softwarerequirements

RAS

Flexi Direct IPA-RNC

mcRNC

RU50EP1

Supportnot
required

Supportnot OMS3.1
required

RN8.1

OMS

BTS Flexi

Flexi Lite

WN9.1

WL9.1

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

WN9.1

NetAct8EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
Thisfeaturerequiresthefollowinghardware:

RNC2600
FlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradioSystemModuleFSMF
orFlexiLiteBTS

Other requirements
IPtransportisrequiredforRNCresiliency.

7.4.1.3

Functional description
Functional overview
TheRAN2512:RNCResiliencyforRNC2600featureimprovesnetworkavailability
duringsingleRNC2600outagesandRNC2600siteoutages.
WiththeRAN2512:RNCResiliencyforRNC2600feature,theoperatorcanintroducea
BackupPRNC(BkPRNC)inthenetwork.TheBkPRNCdoesnothaveitsownradio
accessnetworkunderitscontrol.ThePRNCthatisprotectedbytheBkPRNCiscalled
theProtectedPRNC(PrPRNC).IncasethePrPRNCfails,theBkPRNCiscommanded
bytheoperatortotakeovertheRANandinterfaces,andtorunthePrPRNC'sservices
withintheacceptabletimeinterval.
RNC2600capacitystep3canbackupRNC2600capacitystep1/step2/step3.One
RNC2600configuredasBkPRNCisabletoprotectupto16RNC2600s,whichare
assignedasPrPRNCs.TheredundancymodeisN+1.OnePrPRNCmighthaveone
BkPRNCconfigured.ThePrPRNCandtheBkPRNCareinthesamephysicalsitesorin
differentsites.Bothintra-siteandinter-siteRNCresiliencyaresupported.
Figure23:RNC2600resiliencytransportnetworklayoutshowsingeneraltheresiliency
ideaandintroducesanexamplenetworklayout.

Issue:01ADRAFT

DN09146788

237

RNCsolutionfeatures

RU50FeatureDescriptionsandInstructions

Figure23
NetAct

RNC2600resiliencytransportnetworklayout
RNC

SGSN

MSS

SASserver

CBCserver
OMS
O&M

Core

Site A

SiteB

Protected Protected
PRNC
PRNC

Backup
PRNC

Protected Protected
PRNC
PRNC

Backup
PRNC

Backhaul

Active
Standby
RNC-clO&M
O&Mnetwork

Theintra-siteresiliencyisusefulwhentheoperatorwantstodoon-sitemaintenanceto
thePrPRNC.ThePrPRNCisshutdownorisolated,andthentheBkPRNCisswitched
onsothattheBkPRNCmighttakeoverthePrPRNC'sresponsibilities.Thebenefitsof
intra-siteresiliencyarethatthenetwork'sparametersdonotdecreaseandthat
scheduledorsuddenmaintenanceworkcanbedone.
Theinter-siteresiliencyisneededincasethereis,forexample,afireoranatural
disasterlikeanearthquakethatcandestroythewholesite.Toimprovenetworkstability
andavailabilityinthiscase,theBkPRNCmustbeplacedinanothersitewithlowerrisk
fromdisasterthanwherethePrPRNCwas.

Operation and maintenance (O&M) area in resilient network


TheO&Mareaprovidestheabilitytoestablishacontrollableandsecuredresiliency
frameworkthatisimplementedbyenhancednetworkinterconnections.Theoperator
managestheresilientnetworkinafastandsimplemannerbecausetheOMSuser
interface,whichistheOMSElementManager,issupported.ThePRNCobject
representingRNCscoveredwiththeresiliencyabilityiscreatedintheOMS.This
solutionallowstheoperatorto:

238

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

RNCsolutionfeatures

remotelymanagethenetwork'sresiliency
managePRNCthatdoesnothostactiveRNCserviceusingthePRNCobject
create,modify,anddeletetheobjectsandparametersinPRNCtopology
checkthestatusofresiliencyassociationbetweenPrPRNCandBkPRNC
checkandmodifyRNWconfigurationofRNCserviceatBkPRNC
downloadanduploadIPPlantoBkPRNC

RAN2512:RNCResiliencyforRNC2600featureintroducesanewRNC-cluster(RNCcl)O&Minterface,whichconnectsPrPRNCwithBkPRNC.Thisnewinterfaceis
responsibleforsynchronizingtheBkPRNCconfigurationwiththePrPRNCs'
configurations.ThefiletransferbetweenPrPRNCandBkPRNCisnecessary.
Transferredfilescontainsomesensitiveinformationthatenablesinsecureandsecurefile
transfers.
SecurityprotectionisalsousedforsecureOMSO&MinterfaceconnectioninBkPRNC,
regardlessiftheRNCserviceiseithernotActive(backup/loadedmode)orActive.Thisis
toreducethethreatsbyprovidingauthentication,confidentiality,andintegritytoO&M
traffic.
InordertoprovideQualityofService,thefeaturesupportsonlytheIPprotocolinthe
transportlayersothatthePrPRNC'slogicalinterfacesareconfiguredaccordingtothis
requirement.

7.4.1.4

System impact
Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on commands
Thisinformationwillbeavailablewhenthenewcommandswillbedeveloped.
ThisfeatureismanagedbytheparameterslistedinParameters.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeatureimpactssystemperformanceandcapacityasfollows:

7.4.1.5

Duringscheduledbackupdatasynchronization,theprotectedPRNCsOMU
performancedecreasestemporarily.

RAN2512: RNC Resiliency for RNC2600 management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Issue:01ADRAFT

DN09146788

239

RNCsolutionfeatures

RU50FeatureDescriptionsandInstructions

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table155:Newparameterslistsparametersintroducedwiththisfeature.
Table155

240

Newparameters

Full name

Abbreviated name

Managed object

PhysicalRNCIdentifier

PRNCId

PRNC

RNCSERVICEIdentifier

RNCSRVId

PRNC

PhysicalRNCcurrentActivityMode

ActivityMode

PRNC

RNCserviceChangeOrigin

RNCSRVChangeOrigin

PRNC

DataSynchronizationidentifier

DATSYNId

PRNC

Stateforcontrollingperiodicdata
synchronization

DataSynchState

PRNC

Schedulingperiodicdata
synchronization

DataSyncSchedule

PRNC

Schedulingperiodicdata
synchronizationindays

DataSyncDays

PRNC

Schedulingperiodicdata
synchronizationinhours

DataSyncHours

PRNC

Schedulingperiodicdata
synchronizationinminutes

DataSyncMinutes

PRNC

RNCclusterO&Minterfacelinkstatus

RNCClusterOMLnkState

PRNC

DatasynchronizationChangeOrigin

DATSYNChangeOrigin

PRNC

BackupPhysicalRNCIdentifier

BKPRNCId

PRNC

BackupRNCIPv4Addressusedfor
establishingRNCclusterO&M

BackUpRNCIP4Address

PRNC

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table155

RNCsolutionfeatures

Newparameters(Cont.)

Full name

Abbreviated name

Managed object

RNCclusterO&Minterfacelinkstatus

RNCClusterOMLnkState

PRNC

BackupPRNCclientTLSModeforRNC BKPRNCTLSClientMode
RlcO&Mlink

PRNC

BKPRNCChangeOrigin

BKPRNCChangeOrigin

PRNC

ActivePhysicalRNC

ActivePRNC

PRNC

DSCPforRNC-clO&Minterface

DSCPRNCCLOM

PRNC

Table156:Modifiedparameterslistsparametersmodifiedbythisfeature.
Table156

Modifiedparameters

Full name

Abbreviated name

Managed object

RNCIdentifier

RncId

PRNC

RNCOptions

RncOptions

PRNC

COSITEIdentifier

COSITEId

PRNC

ConnectionConfigurationIdentifier

COCOId

PRNC

IPbasedrouteidentifier

IPBasedRouteIdIur

PRNC

Therearenoexistingparametersrelatedtothisfeature.

7.4.1.6

Sales information
Table157

Issue:01ADRAFT

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

RNCResiliencyLK

DN09146788

241

RNCsolutionfeatures

RU50FeatureDescriptionsandInstructions

7.5 RAN3047: RTT Improvement to Enhance User


Experience
7.5.1 Description of RAN3047: RTT Improvement to enhance
user experience
Introduction to the feature
ThisfeaturewillreduceRTTRNCdelayinanendtoendenvironment.

7.5.1.1

Benefits
End-user benefits
ThisfeatureprovidesbetterenduserexperienceintermsofRTTdelay.

Operator benefits
Thefeatureprovidesfasterdatatransferforinteractiveapplicationsandbackground
traffic.

7.5.1.2

Requirements
Software requirements
Table158:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
RAS

Flexi Direct IPA-RNC

mcRNC

Flexi Direct OMS


RNC

RU50

FlexiDirect
RU50

mcRNC4.1

ADA6.0

Supportnot Support
required
not
required

SGSN

MGW

Table158

RN8.0

Flexi BTS

Softwarerequirements

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

UE

Supportnot
required

Supportnot
required

NetAct8
EP11)
NetAct8
EP22)

Supportnot Supportnot Supportnot


required
required
required

3GPP
Rel-8

1)forRU50
2)forRU50EP1andFlexiDirectRU50

Hardware requirements
Nohardwarerequirements.Itishardwareindependent.

242

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

7.5.1.3

RNCsolutionfeatures

Functional description
Functional overview
Thisfeatureenablesfasterdatatransferforinteractiveapplicationsandbackground
trafficbyreducingdelayindatahandling,andpushendtoendHSPARTTdelayfora32
BytePingwith2msULTTI.
ImprovementinRoundTripTime(RTT)isachievedbyreducingthedelaycomponentsin
thedatapathbetweenthenetworkandUE.ThefeaturefocusesonreducingRNC
internalprocessingdelayinHS(D)PADownlinkdatapath.
ReductionofRTTimprovestheresponsetimesforinteractiveservicesandfasterdata
transferforbackgroundtraffic,therebyenhancingtheuserexperience.

7.5.1.4

System impact
Interdependencies between features
Thisfeaturehasnofeatureinterdependencies.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on commands
Therearenocommandsrelatedtothisfeature.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

7.5.1.5

RAN3047: RTT Improvement to enhance user experience


management data
Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Therearenokeyperformanceindicatorsrelatedtothisfeatureatthistime.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Issue:01ADRAFT

DN09146788

243

RNCsolutionfeatures

RU50FeatureDescriptionsandInstructions

Parameters
Therearenokeyperformanceindicatorsrelatedtothisfeatureatthistime.

7.5.1.6

Sales information
Table159

Salesinformation

BSW/ASW

SW component

License control in network element

BSW

RAN

RNCLK

7.6 RAN2671: Upgrading of mcBSC to mcRNC


7.6.1 Description of RAN2671:Upgrading of mcBSC to mcRNC
Overview
Thehugegrowthoftrafficexpectedhasbroughtnewchallengestoradionetwork
elements.Tosatisfycurrentandfutureneeds,NSNhasdevelopedanovel,compact,
andhighlyscalableMulticontrollerPlatformwhichenablesoperatorstoprovidethe
neededcapacityinanunrivaledfootprint.BothmcBSCandmcRNChardwarearebased
ontheMulticontrollerhardwarePlatform.TheplatformismadesothatmcBSCand
mcRNCcansharemostofthehardware.Whenthenetworkchangesandmorecapacity
isrequiredformcRNC,themcBSCmodulescanbetransformedtomcRNCmodulesby
makingminorHWchangesinthemoduleand/orbyinstallingthecorrespondingSW.
Thishardwaresolutionprovidesrelativelylow-costandlow-effortpossibilityto:

7.6.1.1

upgradeexisting2Gradionetworkcontrollerto3GradionetworkcontrollermcRNC
transformmcBSCmodulestomcRNCinordertoincreasecapacitystep(s)
useexistingmcBSCmodulesinordertoincreasemcRNCcluster'scapacitystep(s)

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
SecuremcBSCHWinvestimentinGSMbyreuseofmcBSCHWmodule(s)formcRNC
inWCDMAnetwork.

7.6.1.2

Requirements
Software requirements
Table160:Softwarerequirementsliststhesoftwarerequiredforthisfeature

244

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table160

RNCsolutionfeatures

Softwarerequirements

RAS

Flexi Direct IPA-RNC

RU50EP1

Notrelevant Notrelevant mcRNC4.1

Table161
BTS Flexi
10`

mcRNC

OMS

BTS Flexi

Flexi Lite

OMS3.1

Notrelevant Notrelevant

SGSN

MGW

Softwarerequirements
NetAct

Notrelevant Supportnot
required

MSC

OMS

UE

Notrelevant Notrelevant Notrelevant Notrelevant Notrelevant

Hardware requirements
DependingontheactualmcBSCtomcRNCupgradescenario,newhardware,aslisted
intheisrequiredwiththisfeature.FormoredetailsseeUpgradescenarios.Thisfeature
isapplicableonlytomcRNCHWRel2.
Table162

NewhardwarerequiredaccordingtomcBSCmoduletypes

mcBSC module type

New hardware required

MulticontrollerBSCPSextensionmodule

N/A

MulticontrollerBSCTRXextensionmodule

BMPP2-Bprocessoradd-incardswithmemories
required

MulticontrollerBSCbasicmodules

BMPP2-Bprocessoradd-incardswithmemories
required

DependingonrequestedmcRNCconfiguration,additionalmcRNCcablesforinternal
andexternal(withrelatedSFPs)connectionsmightberequired.

Issue:01ADRAFT

DN09146788

245

RNCsolutionfeatures

7.6.1.3

RU50FeatureDescriptionsandInstructions

Functional description
mcBSC introduction
Figure24

MulticontrollerBSCcapacitysteps

ThemcBSCisfullycompliantwithanycorenetworksupportingIPbasedGSMaccess
networkanditisfullyoptimizedtomostmodernandefficientIPonlytransmission
solutions.Dependingonthecapacityneeds,onemcBSCconsistsoftwotoseveral
modules.SevenreferencecapacitystepsareusedincurrentmcBSC.Theydifferinthe
numberofBCNmodulesused,from2(step1)to8(step7).
mcBSCwithRel2hardwareisbuiltwithfourmoduletypes,Typically,thehardware
combinationconsistsofBCN-BboxandBMPP2add-incards.
EachmoduletypeofmcBSCwithRel2hardwareconsistsofbelowadd-incards:
Mainmodule

246

4xBJC-A,JasperForestCard
4xBMPP2-B,OcteonIICard
HDS30-A,300GBHDD

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

RNCsolutionfeatures

optionalBSAC-A,SynchronizationAMCcard

Sparemodule

3xBJC-A,JasperForestCard
5xBMPP2-B,OcteonIICard
HDS30-A,300GBHDD
optionalBSAC-A,SynchronizationAMCcard

TRXextensionmodule

2xBJC-A,JasperForestCard
6xBMPP2-B,OcteonIICard

PSextensionmodule

8xBMPP2-B,OcteonIICard

BasicstandalonemcBSCconfigurationconsistsoftwomodules(mcBSCbasic
modules).AdditionalcapacitystepsareavailablebystepsofonemcBSCTRXextension
moduletoincreaseTRXandPSdataconnectivity.MaximumTRXconnectivitycanbe
reachedwithcapacitystep4containing5modules,andontopofthat,evenhigherPS
dataconnectivitycanbereachedwithadditionalmcBSCPSdataextensionmodules.
MaximumconfigurationwithBCN-Bhardwareconsistsof8modules.
Formoreinformation,pleaseseeMulticontrollerBSCandMulticontrollerTranscoder
ProductDescription.

Issue:01ADRAFT

DN09146788

247

RNCsolutionfeatures

RU50FeatureDescriptionsandInstructions

mcRNC introduction
Figure25

MulticontrollerRNCcapacitysteps

ThemcRNCishighlyoptimizedfortheIPnetworkenvironment.TheMulticontroller
moduleistightlyintegratedandhasonlyafewfield-replaceableparts.Thekeyenablers
ofthisapproachareIP/EthernettechnologyandadvancedCPUtechnology.ThemcRNC
consistsofanumberofsimilarBCNmoduleswhichareconnectedinternallybycables.
Dependingonthecapacityneeds,thelatestmcRNCwithRel2hardwarecanconsistof
two,four,oreightmodules.EverymoduleconsistsofBCN-BboxandBMPP2-Badd-in
cards.
ThepossiblemoduletypesforRel2hardwareareeithermc01Bormc02B.The
differencebetweenmc01Bandmc02Bisthatmc01BhasahardDiskAMCandmc02B
doesnot.
Themaincomponentsofmc01Bare:

8xBMPP2-B,OcteonIICard
HDS30-A,300GBHDD

Themaincomponentsofmc02Bare:

248

8xBMPP2-B,OcteonIICard

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

RNCsolutionfeatures

BasicmcRNCconfigurationwithRel2HWconsistsoftwomc01Bmodules.The
supportedmcRNCRel2hardwarecapacityexpansionistoaddtwomc02Bmodulesto
mc01BbasicmodulesforS3-B2,thenaddfourmoremc02BmodulestoS3-B2forS7B2.
Formoreinformation,pleaseseeMulticontrollerRNCProductDescription.

Upgrade scenarios
ThetargetofreusingmcBSChardwareformcRNCismainlyfortwousescenarios.One
isformcRNChardwareexpansionandtheotheristocommissionanewmcRNCwith
transformedmcBSCmodules.
Figure26

UpgradingmcBSCtomcRNC

3. SpecificworktocommissionanewmcRNCorexpand
existingmcRNChardware

2. Commonworktothemodules
formcRNCapplication

1.Initialwork

Upgrading mcBSCtomcRNC
StripmcBSCspecificconfigurationdata
toreducetheBSCcapacityandconnectivity
toremovethefunctionalunitswithinoneormoremodulesfromthemcBSCconfiguration
toshutdownandphysicallyremoveoneormoremodulesfrommcBSC

1.Hardwaremodifications (ifneeded)

2. Hardwareinstallation

For setupanew mcRNC

3.Embedded SWupdate
forthetransformedmodules

4. Pre-configuring mcRNC modules

FormcRNChardwareexpansion

Startabovecommonwork2

1. ExistingmodulesmcRNCverification.

1. CreatingtheFSetupconfigurationfile

Startabovecommonwork2

2. Creatingcommissioningsession

2. Updatingthenewaddedmodulesto
mcRNCdatabase
UpdatingnewhardwaretoLDAP
database
Refreshingfunlibandaddresstables

3.InstallingmcRNCsoftwarepackage
4.Performing post-configuration

3. Backplane activation
4. CompletingHW expansion
5. Running diagnosticsinnewaddedmodules
6. Sigtran configuration
7. Activating expansion modules
8.RebalancingBTSresourcesafterexpansion

Using mcBSC modules to expand existing mcRNC

Issue:01ADRAFT

DN09146788

249

RNCsolutionfeatures

RU50FeatureDescriptionsandInstructions

mcBSCmodulescanbetransferredintomcRNCusingmebymoduleormultiple
modulesatthesametime
mcBSCPSdataextensionmodulesandmcBSCTRXextensionmoduleshavetobe
transferredfirstintomcRNCuse
lasttwomodulestobetransferredatthesametimeintomcRNCusearemcBSC
basicmodules
maximumnumberofmodulesinamcRNCconfigurationis8

Using mcBSC modules to set up new mcRNC

completemcBSCconfiguration(maximum8modules)canbetransferredinto
mcRNCuseatthesametime
apartofmcBSCcanbetransferredintomcRNCuseatthesametime(minimum
numberofmodulesinanmcRNCconfigurationis2)

Hardware modification from mcBSC module to mcRNC module


AccordingtomcBSChardwarearchitecture,therearesomespecificadd-incardswhich
aresupportedinmcRNC.DuringtheupgradingfrommcBSCtomcRNC,thoseshallbe
replacedorremoved.Table163:mcBSCmodulecardchangesrequirementsshows
overalltheamountofadd-incardstobereplacedorremovedaccordingtomcBSC
moduletype.
Table163

mcBSCmodulecardchangesrequirements

mcBSC module type

Required BMPP2-B add-in cards

mcBSCPSextensionmodule

mcBSCTRXextensionmodule

mcBSCbasicmodules

Fordetailedinformationaboutnecessarychanges,see:

Figure27:mcBSCPSextensionmodulenecessarychanges
Figure28:mcBSCTRXextensionmodulenecessarychanges
Figure29:mcBSCSparemodulenecessarychanges
Figure30:mcBSCmainmodulenecessarychanges

FormcBSCPSextensionmodule-nochangetomcRNCPSextensionmodule

250

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Figure27

Issue:01ADRAFT

RNCsolutionfeatures

mcBSCPSextensionmodulenecessarychanges

FormcBSCTRXextensionmodule-slot1,2add-incardsareremoved,andreplaced
withBMPP2-B

DN09146788

251

RNCsolutionfeatures

RU50FeatureDescriptionsandInstructions

Figure28

252

mcBSCTRXextensionmodulenecessarychanges

FormcBSCSparemodule-slot1,2,and3add-incardsareremovedandreplaced
withBMPP2-B(PTU(BSAC-A)isremoved)

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Figure29

Issue:01ADRAFT

RNCsolutionfeatures

mcBSCSparemodulenecessarychanges

FormcBSCmainmodule-slot1,2,3,and8add-incardsareremovedandreplaced
withBMPP2-B(PTU(BSAC-A)isremoved)

DN09146788

253

RNCsolutionfeatures

RU50FeatureDescriptionsandInstructions

Figure30

mcBSCmainmodulenecessarychanges

Exceptadd-incards,additionalequipment,likemodules,cables,SFPs,mightbe
necessary.TheseneedsdependsonexistingmcBSCconfigurationandrequiredmcRNC
configuration.

7.6.1.4

System impact
Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.

254

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

RNCsolutionfeatures

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on commands
Thisfeaturehasnoimpactoncommands.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

7.6.1.5

RAN2671:Upgrading of mcBSC to mcRNC management data


Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Therearenoexistingparametersrelatedtothisfeature.

7.6.1.6

Sales information
Table164

Issue:01ADRAFT

Softwarerequirements

BSW/ASW

SW component

License control in network element

HW

RAN

DN09146788

255

BTSsolutionfeatures

RU50FeatureDescriptionsandInstructions

8 BTS solution features


8.1 RAN3010: 24 Cell Support with Flexi FSMF +
FSMD/E System Modules
8.1.1 Description of RAN3010: 24 Cell Support with Flexi FSMF +
FSMD/E System Modules
Introduction to the feature
Upto24cellsperBTSissupportedwithFSMF+FSMD/ESystemModules.

8.1.1.1

Benefits
Operator benefits
Evolutionformulticarrier,multibandandmultisectorsiteswithFSMF+FSMD/E.

8.1.1.2

Requirements
Software requirements
Table165:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
Table165

Softwarerequirements

RAS

RNC

IPA-RNC

mcRNC

BTS Flexi

Flexi Lite

RU50EP1

Supportnot
required

Supportnot
required

Supportnot
required

WN9.1

Notrelevant

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

WN9.1

NetAct8EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
FlexiMultiradioSystemModuleFSMFasmasterSystemModuleandFlexiMultimode
SystemModuleFSMD/EasextensionSystemModulearerequired.FlexiWCDMA
SystemModuleFSMBisnotsupported.Thisfeatureisnotsupportedwithsingle-sector
anddual-sectorRadioModules.

8.1.1.3

Functional description
24cellsaresupportedwithFSMFasmasterSystemModuleandFSMD/Easextension
SystemModule.ThemasterSystemModulecanhavezero,oneortwoCapacity
ExtensionSub-Modules(FBBA).

256

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

BTSsolutionfeatures

RFModulesneedstobeconnectedtomasterSystemModule.TwoOBSAIlinks
betweenMasterandextensionSystemModuleisrequired.Maximumamountofcellsper
BTSis24.Morethan12cellsconfigurationsneedadditional6WCDMAcellactivation
licensekey:

13-18cellsconfiguration:oneadditionalLK
19-24cellsconfiguration:twoadditionalLKs

TherequiredtransportmodeisIPIub.
Forsupportedconfigurationspleasesee"FlexiMultiradioBTSWCDMASupportedand
PlannedConfigurations"and"FlexiMultiradioBTSRFSharingReleased
Configurations".

8.1.1.4

System impact
Current Implementation
18cellsperBTSwithFSMF+FSMD/Econfigurationissupported

Interdependencies between features


SupplementaryInternalInformationRequiresRAN2732:FlexiSystemModuleextension,
FSMF+FSMD/E.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on MML commands


TherearenoMMLcommandsrelatedtothisfeature.

Impacts on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementandnetworkelementmanagement
tools.

Impacts on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceandcapacity.

8.1.1.5

Sales information
Table166

Issue:01ADRAFT

Salesinformation

BSW/ASW

SW component

License control in network element

ASW

RAN

Notdefined

DN09146788

257

BTSsolutionfeatures

RU50FeatureDescriptionsandInstructions

8.2 RAN3017: Additional 6 WCDMA Cell Activation


8.2.1 Description of RAN3017: Additional 6 WCDMA Cell
Activation
Introduction to the feature
RAN3017:Additional6WCDMACellActivationlicensekeyincreasesthenumberof
supportedcellsintheBTSconfiguration.Stepsizeofonelicensekeyis6cells.InRU50
thenumberofcellscanbeupto18.

8.2.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
Increasingtraffic,demandformulticarrier,multiband,andmulti-sectorsitesleads
operatorneedstowardslargerBTSsiteconfigurations,especiallyinhotspotareas.This
featureenablestobuildsuchconfigurationswithsimpleSWconfiguration.

8.2.1.2

Requirements
Software requirements
Table167:Softwarerequirementsliststhesoftwarerequiredforthisfeature.
Table167

Softwarerequirements

RAS

Flexi Direct

IPA-RNC

mcRNC

Flexi Direct
RNC

OMS

Flexi BTS

RU50

Notplanned

Supportnot
required

Supportnot
required

Notplanned

Supportnot
required

WN9.0

MGW

UE

Flexi Lite
BTS

Flexi 10
BTS

NetAct

MSC

SGSN

Notrelevant

WN9.1

NetAct8
EP1
(RU50)

Supportnot Supportnot Supportnot Supportnot


required
required
required
required

NetAct8
EP2(RU50
EP1)

Hardware requirements
ThisfeaturerequiresFlexiMultiradioSystemModule(FSMC/D/E)orFlexiMultiradio10
SystemModule(FSMF).

258

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

8.2.1.3

BTSsolutionfeatures

Functional description
Functional overview
Siteconfigurationenablescreationupto12cellswithoutalicensekey.Toactivate
additional6cellsinBTSconfigurationalicensekey(LK)isrequired.
Table168

Numberofneededlicensekeys

Number of cells

License keys

0-12

0xLK

13-18

1xLK

Needforlicensekey(s)ischeckedbasedontheRNCcellsetup.Notethatafter
theSWupgradetoWN9.x,theLKhastobeprovidedwithintwoweeks.
Otherwise,additionalcellsstopworking.
Incaseofasitethathasmorethan12cells,aftertheupgradetoWN9.x,this
featureisautomaticallyswitchedon.IftheextendedBtsSiteCapacity
parameterisoffandadditionalcellsarenotactive,thisfeatureremains
switchedoffalsoinWN9.x.

8.2.1.4

System impact
Interdependencies between features
Currently,RAN2736ExtendedBTSSiteCapacitylicensekeyisneededifBTSsite
configurationhasmorethan12cells.RAN3017:Additional6WCDMACellActivation
replacestheexistingsolution.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeatureenablestheoperatortoenlargesiteconfigurationbyaddingnewcells.

8.2.1.5

RAN3017: Additional 6 WCDMA Cell Activation management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Table169:Existingalarmslistsexistingalarmsrelatedtothisfeature.

Issue:01ADRAFT

DN09146788

259

BTSsolutionfeatures

RU50FeatureDescriptionsandInstructions

Table169

Existingalarms

Alarm ID

Alarm name

7660

BASESTATIONLICENCEEXPIRED
Relatedfault:1885:EFaultId_MissingLicenseAl

7661

BASESTATIONLICENCENOTIFICATION
Relatedfault:1885:EFaultId_MissingLicenseAl

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table170:Modifiedparameterslistsparametersmodifiedbythisfeature.
Table170

8.2.1.6

Modifiedparameters

Full name

Abbreviated name

Managed object

ExtendedBTSsitecapacity
enabled

extendedBtsSiteCapacity

BTSSCW

Sales information
Table171

Salesinformation

BSW/ASW

SW component

License control in network


element

ASW

RAN

BTSLK

8.2.2 Activating RAN3017: Additional 6 WCDMA Cell Activation


Purpose
FollowtheprocedurebelowtoactivatetheRAN3017:Additional6WCDMACell
Activation.
Before you start
MakesureyouhaveaccesstotheBTSSiteManager.

260

Notethatthisfeatureisunderlicensecontrol.Thisfeaturerequiresavalid
licensefile.Thefeaturecodeis0000005171.See
WCDMARANLicenseOperationdocumentfordetails.

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

BTSsolutionfeatures

Start the WCDMA BTS Site Manager application and establish the connection
to the BTS.
FlexiMultiradioBTSWCDMAcanautonomouslyrequestformissinglicensefile(s)
fromNetActLicenceManagerduringfeatureactivation(RAN2131:Automatic
LicenceDistributiontoFlexiBTS).
MakesurethatyouhaveselectedAutomatic licensing in usecheckboxinthe
AutomaticLicenseDistributionSettingspage.

IfRAN2131:AutomaticLicenceDistributiontoFlexiBTSisnotactivated,
relevantlicensemustbeuploadedmanually.

Upload the configuration plan file from the BTS.


WhenBTSSiteManagerisconnectedtotheBTS,itautomaticallyuploadsthe
currentconfigurationplanfilefromtheBTS.

SelectViewCommissioningorclickCommissioningontheViewbar.

Activate RAN3017: Additional 6 WCDMA Cell Activation feature.


GotoLocalCellResourcespageandselecttheExtended BTS site capacity
enabledcheckbox.
Figure31

ActivatingRAN3017:Additional6WCDMACellActivation

Send the commissioning plan file to the BTS.


ClickSend Parametersbutton.
Youmightsavetheparametersatthispoint.

The new commissioning plan file is automatically activated in the BTS.


BTSSiteManagerautomaticallysendsanactivationcommandafterfinishingthefile
download.

Select Next to complete the commissioning.


Youcansavethecommissioningreport,ifrequired.

Issue:01ADRAFT

DN09146788

261

BTSsolutionfeatures

RU50FeatureDescriptionsandInstructions

Backup commissioning files (if applicable).


SelectFileBackup commissioning files
Savethecompletebackupcommissioningfileforfurtheruse.

Result
ThefeatureRAN3017:Additional6WCDMACellActivationisactivated.

8.2.3 Verifying RAN3017: Additional 6 WCDMA Cell Activation


Purpose
FollowstepsbelowtoverifythattheactivationoftheRAN3017:Additional6WCDMA
CellActivationfeaturehasbeensuccessful.
1

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

Upload the configuration plan file from the BTS.


WhenBTSSiteManagerisconnectedtotheBTS,itautomaticallyuploadsthe
currentconfigurationplanfilefromtheBTS.

SelectViewCommissioningorclickCommissioningontheViewbar.

Verify that Extended BTS site capacity enabled checkbox is selected.


ThevalueofBTSSCW extendedBtsSiteCapacityparametershouldbe1/true.
Additionally,verifyonthemainpagethatallcreatedcellsareworking:

localcellstateis"Operational"
operationalstateis"Enabled"
workingstateis"Working"

8.2.4 Deactivating RAN3017: Additional 6 WCDMA Cell


Activation
Purpose
TodeactivateRAN3017:Additional6WCDMACellActivationfeature,followthis
procedure.
Before you start

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

Perform recommissioning procedure.


SelectCommissioning,choosereconfiguration.

262

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

BTSsolutionfeatures

Disable RAN3017: Additional 6 WCDMA Cell Activation feature.


GotoLocalCellResourcespageandremovetheselectionfromtheExtended BTS
site capacity enabledcheckbox.

Complete the recommissioning procedure.

8.3 RAN2826: Flexi Compact as RF Module


8.3.1 Description of RAN2826: Flexi Compact as RF Module
Introduction to the feature
ThefeatureintroducesFlexiCompactBTS(FQDJ,band900J)useasanRFModulefor
WCDMAoperationwithFSMFSystemModule.

8.3.1.1

Benefits
Operator benefits
TheFlexiCompact(FQDJ)modulecanbeusedasaWCDMARFModule.

8.3.1.2

Requirements
Software requirements
Thefollowingtablelistssoftwarerequiredforthisfeature.

RAS

Flexi Direct IPA-RNC

RU50EP1

Supportnot
required

Table172

mcRNC

OMS

BTS Flexi

Flexi Lite

Supportnot Supportnot Supportnot Supportnot Supportnot


required
required
required
required
required

Softwarerequirements

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

WN9.1

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
ThisfeaturerequiresFlexiMultiradio10BaseStationSystemModule(FSMF).

8.3.1.3

Functional description
TheFQDJmoduleisseenintheWCDMAmodeasa3x40W900MHz1TX/2RXRF
Module.TX/RXbandwidthis25MHz.

Issue:01ADRAFT

DN09146788

263

BTSsolutionfeatures

RU50FeatureDescriptionsandInstructions

ThemodulecanbeusedasaWCDMA3-sectorRFModulewithFSMFintwoscenarios:

8.3.1.4

DedicatedforWCDMA
AntennasharingconfigurationwithGSM(GSMsupportisdefinedinGSMroadmap)

System impact
Interdependencies between features
Therearenointerdependenciesbetweenfeatures.

Impact on interfaces
Thereisnoimpactoninterfaces.

Impact on network and network element management tools


Thereisnoimpactonnetworkandnetworkelementmanagementtools.

Impact on system performance and capacity


Thereisnoimpactonsystemperformanceandcapacity.

8.3.1.5

RAN2826: Flexi Compact as RF Module management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Therearenonewormodifiedparametersrelatedtothisfeature.

8.3.1.6

Sales information
Table173

264

Salesinformation

BSW/ASW

SW component

License control in network element

BSW

RAN

Notdefined

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

BTSsolutionfeatures

8.4 RAN2784: Flexi Lite BTS 1900 MHz


8.4.1 Description of RAN2784: Flexi Lite BTS 1900 MHz
Introduction to the feature
FlexiLiteBTS1900(FQFA)isasmall,all-in-onebasestationoptimizedforindoorand
outdoormicrocellenvironment.Theproductdesign,hardwareandsoftwareisbasedon
theawardwinningFlexiMultiradioBTSplatform.
Figure32

8.4.1.1

FlexiLiteBTS1900

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
Thisfeaturebenefitstheoperatorasfollows:

Issue:01ADRAFT

Theproductcanbeusedinpico-andmicrocellularapplicationsandalsoasa
coveragefill-insolution.Themainusecaseisincapacitylimitednetworkswherethe
operatorneedstostartusingsmallercellstobeabletodelivertherequiredsystem
capacity.

DN09146788

265

BTSsolutionfeatures

RU50FeatureDescriptionsandInstructions

8.4.1.2

Outputpowerishighenoughtosupportindoorcoveragebuildingfromoutdoorsites.
Itisalsohighenoughtodrivedistributedantennasystemforindoorcoverage.Italso
supports2TXMIMO.
SupportsWCDMA/HSPAservices.

Requirements
Software requirements
Table174:Softwarerequirementsliststhesoftwarerequiredforthisfeature.

RAS

Flexi Direct IPA-RNC

RU50EP1

Notrelevant Supportnot Supportnot OMS3.1


required
required

Table174

mcRNC

OMS

BTS Flexi

Flexi Lite

Not
relevant

WL9.1

Softwarerequirements

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

Notrelevant

NetAct8EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
Thisfeaturerequiresnoneworadditionalhardware.

8.4.1.3

Functional description
FlexiLiteBTS1900isintegrated,smallinsize,lightweightbasestationwhichcanbe
installedonwallsorpoles(IP65).Theoutputpowerlevelisadjustablefrom5W+5W
downto250mW+250mWin~1dBstepsformicrocells.
FlexiLiteBTSoffersflexibledeploymentsoptionsatwalls,lampposts,utilitypoles,
billboardsorotherstreetfurniture.Typicalmicro-celloutdoorantennadeploymentsare
belowroof-topinheightsofabout5to15metersabovethegroundlevel.
Typicalindoordeploymentsincludeexhibitionhalls,shoppingmalls,largeofficespaces,
airportsetc.Antennaheightinindoorinstallationsistypicallyfrom2to5metersabove
groundlevel.InindoorsFlexiLiteBTSistobemountedeitheronthewallortheceiling
orconnectedtoanexternaldistributedantennasystem.
FlexiLiteBTSconsistsofthefollowingelements:

266

corebasestationmodule
optionalintegratedantenna
optionalvisualcover
optionalpoleandwallinstallationkits

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

BTSsolutionfeatures

FlexiLiteBTScanbemountedonawalloronapolewiththesuppliedhardware.Active
coolingenablesminimuminstallationclearance,soFlexiLiteBTScanbeinstalledin
locationsthatarenotmuchlargerthanBTSitself(~12.5l),forexampleinutilityrooms,
insidecabinets(anypositionpossible).Allcablingisaccessiblewithoutdismountingthe
unit.

Air interface configuration


FlexiLiteBTS1900hastwotransceivers:two5Wtransmittersandtwo-121dBm
(tunabledownto-107dBminsteps)receivers.FlexiLiteBTSoperatesatband2:

UL:1850-1910MHz
DL:1930-1990MHz

Transport
FlexiLiteBTSusesIPasastandardtransportprotocol.Ethernet,bothwirelineandfiber,
isthestandardinterfaceintheFlexiLiteBTS.

8.4.1.4

System impact
Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on network and network element management tools


Thisfeatureisanewbasestationdesignedforpico-andmicrocellularsitesandalsoas
acoveragefill-insolution.Themainusecaseisforcapacity-limitednetworkswherethe
operatorneedstostartusingsmallercellstobeabletodelivertherequiredsystem
capacity.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

8.4.1.5

RAN2784: Flexi Lite BTS 1900 MHz management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
InformationonalarmsandfaultsrelatedtoFlexiLiteBTScanbefoundinFlexiLiteBTS
Faults.

Measurements and counters


InformationonmeasurementsandcountersrelatedtoFlexiLiteBTScanbefoundin
FlexiLiteBTSCounters.

Issue:01ADRAFT

DN09146788

267

BTSsolutionfeatures

RU50FeatureDescriptionsandInstructions

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
InformationonparametersrelatedtoFlexiLiteBTScanbefoundinFlexiLiteBTS
WCDMAParametersandFlexiLiteBTSTransportModuleParameters.

8.4.1.6

Sales information
Table175

Salesinformation

BSW/ASW

SW component

License control in network element

BSW

RAN

8.5 RAN2732: Flexi System Module Extension, FSMF +


FSMD/E
8.5.1 Description of RAN2732: Flexi System Module Extension,
FSMF + FSMD/E
Introduction to the feature
ThisfeatureintroducessupportfornewFlexiBTSconfigurationsthatcanconsistofboth
FlexiMultiradioBTSSystemModule(FSMD/E)andFlexiMultiradio10BTSSystem
Module(FSMF).

8.5.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Operator benefits
Thisfeaturebenefitstheoperatorasfollows:

8.5.1.2

Smoothsiteupgrade
Evolutionpathforexistingsitestoincreasecapacity

Requirements
Software requirements
Table176:Softwarerequirementsliststhesoftwarerequiredforthisfeature.

268

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table176

BTSsolutionfeatures

Softwarerequirements

RAS

Flexi Direct IPA-RNC

RU50EP1

Supportnot
required

Flexi Lite
BTS

Flexi 10
BTS

Notrelevant WN9.1

mcRNC

Flexi Direct
RNC

Supportnot Supportnot Supportnot


required
required
required

OMS

Flexi BTS

OMS3.1

WN9.1

NetAct

MSC

SGSN

MGW

UE

NetAct8
EP2

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
ThisfeaturerequiresFlexiMultiradioSystemModule(FSMD/E)andFlexiMultiradio10
SystemModule(FSMF).

8.5.1.3

Functional description
Functional overview
WiththisfeatureitispossibletouseFSMF(master)togetherwithFSMD/Easan
extensionmodule(slave).
InsuchconfigurationFSMFasamasterisresponsibleforthefollowingtasks:

Iubtransport(onlyIPIubissupported)
synchronizationofothermodules(RFs,extension/slaveunits)
RP3topologydetectionforthewholeBTSunderoneRAT
dynamicRP3allocationforthewholeBTSunderoneRAT
SWdownloadanddistributiontoextensionFSMs

Notethatconfigurationswithmorethan12cellsarenotsupportedwithone-andtwosectorRadioModules.Forsupportedconfigurations,seeFlexiMultiradioBTSWCDMA
SupportedConfigurations.
FSMFcapacitycanbeadditionallyincreasedwithuptotwooptionalCapacityExtension
Sub-Modules(FBBAs).SuchconfigurationallowsconnectinguptofourRF
Modules/RRHs.ThemaximumnumberofchainsisthreewithuptotwoRF
Modules/RRHsperchain.
Notethatinsuchconfigurationthesupportedtypesofbasebandpoolingareonlyfixed
basebandallocations(fixedtoFSMD/EandFSMForFBBA).
ThisalsomeansthattheextensionSMhastobecommissionedbeforeconnectingtothe
masterSM.
Twolocalcellgroups(LCGs)aresupported(oneperFSM).

Issue:01ADRAFT

DN09146788

269

BTSsolutionfeatures

RU50FeatureDescriptionsandInstructions

Configuration
FSMFandFSMD/EareconnectedthroughtwoRP3-01interfaces:

oneforcommunicationpurposes(1GbEthernetmode)
oneforantennadataandsynchronizationinformationexchange

FSMFcanuseanyofitsRP3interfaces.FSMD/EhastouseOptIF1BB-extandOptIF2
BB-ext.FSMsautomaticallyconfigurebothconnections.
Formoreinformation,seeCablingFlexiMultiradio10BaseStation.

8.5.1.4

System impact
Interdependencies between features
ThisfeatureallowstouseRAN2262:FlexiMultiradioSystemModulestogetherwith:

RAN1016:FlexiBTSMultimodeSystemModule-FSMD
RAN1848:FlexiBTSMultimodeSystemModule-FSME

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on commands
Therearenocommandsrelatedtothisfeature.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeatureimpactssystemperformanceandcapacityasfollows:

8.5.1.5

AllowstocreatesitesbasedonFlexiMultiradio10SystemModuletogetherwiththe
legacyFlexiSystemModule.
AllowsconnectinguptofourRFModules/RRHstoFSMFwithtwoFBBAs.The
maximumnumberofchainsisthreewithuptotwoRFModules/RRHsperchain.

RAN2732: Flexi System Module Extension, FSMF + FSMD/E


management data
Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Table177:Relatedexistingalarmslistsexistingalarmsrelatedtothisfeature.
Table177

270

Relatedexistingalarms

Alarm ID

Alarm name

7651

BASESTATIONOPERATIONDEGRADED

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

Table177

BTSsolutionfeatures

Relatedexistingalarms(Cont.)

Alarm ID

Alarm name
Fault4199ExtensionSystemModulecannot
betakenintouse

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Table178:Modifiedparameterslistsexistingparametersrelatedtothisfeature.
Table178

8.5.1.6

Modifiedparameters

Full name

Abbreviated name

Managed object

RP3linkId

linkId

RMOD

LinkId

linkId

SMOD

Sales information
Table179

Salesinformation

BSW/ASW

SW component

License control in network element

BSW

RAN

8.6 RAN2393: Optical Fiber: RX/TX Level Monitoring


8.6.1 Description of RAN2393: Optical Fiber: RX/TX Level
Monitoring
Introduction to the feature
Withthisfeatureitispossibletoobtainopticalinterfacediagnosticsinformationfromthe
SFPconnector.Suchinformationcanbeusedfortroubleshootingpurposes.

8.6.1.1

Benefits
End-user benefits
Thisfeaturedoesnotaffecttheend-userexperience.

Issue:01ADRAFT

DN09146788

271

BTSsolutionfeatures

RU50FeatureDescriptionsandInstructions

Operator benefits
Thefeaturecanbemainlyusedfortroubleshootingpurposesoronanewsiteinstallation
incaseofSFPopticalinterfaceproblembetweentheRFModuleandtheSystem
Module.Thediagnosticsinformationgivesaverygoodindicationofthefiberlinkquality
betweentheRFModuleandtheSystemModule.

8.6.1.2

Requirements
Software requirements
Table180:Softwarerequirementsliststhesoftwarerequiredforthisfeature.

RAS

Flexi Direct IPA-RNC

RU50EP1

Supportnot
required

Table180

mcRNC

OMS

BTS Flexi

Supportnot Supportnot Supportnot WN9.1


required
required
required

Flexi Lite
Not
relevant

Softwarerequirements

BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE

WN9.1

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Supportnot
required

Hardware requirements
Thisfeatureisnotsupportedwithanysingle-sectoranddual-sectorRadioModule,
FRGFthree-sectorRadioModuleandFRGGRRH.
ThisfeaturerequiresFlexiMultimodeSystemModuleFSMC/D/EorFlexiMultiradio
SystemModuleFSMF.

8.6.1.3

Functional description
Functional overview
Theinter-module(RP3)linkconnectivitytroubleshootingfeaturemonitorstheoptical
interfacecondition.Thefeaturesupportson-demandpollingandshowsdatafromboth
endsofthelink-thenearendandthefarend.
TheBTSSiteManagershowstheSFPonlinediagnosticinformation.Thefollowingdata
isshown:

272

SFPVendor
SFPType
Moduletemperature
TransceiverTxsupplyvoltage
TransceiverTxbiascurrent
TransceiverTxpower
TransceiverRxopticalpower

DN09146788

Issue:01ADRAFT

RU50FeatureDescriptionsandInstructions

BTSsolutionfeatures

TheBTSSiteManagerpresentsthestatisticsofthemonitoredindicatorsandallowsto
setthecumulativeLCVcountertozero.

8.6.1.4

System impact
Interdependencies between features
Therearenointerdependenciesbetweenthisandanyotherfeature.

Impact on interfaces
Thisfeaturehasnoimpactoninterfaces.

Impact on network and network element management tools


Thisfeaturehasnoimpactonnetworkmanagementornetworkelementmanagement
tools.

Impact on system performance and capacity


Thisfeaturehasnoimpactonsystemperformanceorcapacity.

8.6.1.5

RAN2393 Optical fiber: RX/TX level monitoring management data


Forinformationonalarm,counter,keyperformanceindicator,andparameterdocuments,
seeReferencedocumentation.

Alarms
Therearenoalarmsrelatedtothisfeature.

Measurements and counters


Therearenomeasurementsorcountersrelatedtothisfeature.

Key performance indicators


Therearenokeyperformanceindicatorsrelatedtothisfeature.

Parameters
Therearenoparametersrelatedtothisfeature.

8.6.1.6

Sales information
Table181

Issue:01ADRAFT

Salesinformation

BSW/ASW

SW component

License control in network element

BSW

RAN

DN09146788

273