• No results found

Prm Set Migrating Btsplus

N/A
N/A
Protected

Academic year: 2021

Share "Prm Set Migrating Btsplus"

Copied!
378
0
0

Loading.... (view fulltext now)

Full text

(1)

GSM/EDGE BSS, rel.

RG20(BSS), operating

documentation, issue 02

Reference

Parameter/attribute mapping for

migrating BTSplus to the

Flexi BSC product family

DN0933393

Approval Date 2010-08-05

(2)

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2010. All rights reserved

f Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system. The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

(3)

Table of contents

This document has 378 pages.

Summary of changes . . . 12

1 Introduction . . . 15

1.1 Abis mediation of BTSplus parameters towards Flexi BSC . . . 15

2 ControlFile format . . . 16

2.1 Common info (not class-specific) for the migration procedure. . . 16

2.2 BTSM selection and migration (BCF and O&M LAPD creation) . . . 16

2.3 TRX selection and migration (LAPD creation only) . . . 17

3 Create LAPD . . . 19 3.1 abisSigChannelSubSlot . . . 20 3.2 abisSigChannelTimeSlotPcm . . . 21 3.3 abisSigChannelTimeSlotTsl. . . 22 3.4 adminState. . . 23 3.5 bitRate . . . 24 3.6 Id . . . 24 3.7 name . . . 25 3.8 parentBSCId . . . 26 3.9 relatedLapdLinkName . . . 26 3.10 sapi . . . 27 3.11 tei . . . 28 3.12 dChannelType . . . 29 3.13 parameterSetNumber . . . 30 4 Create BCF . . . 31 4.1 adminState. . . 32 4.2 batteryBackupProcedure . . . 33 4.3 bcchTrxBatbuTimer . . . 34 4.4 bcfType . . . 35 4.5 lapdLinkName . . . 36 4.6 normTrxBatbuTimer . . . 36 4.7 normTrxBatbuTimer2 . . . 37 4.8 normTrxBatbuTimer3 . . . 38 4.9 btsSiteSubtype. . . 39 4.10 pcmPortId0 . . . 40 4.11 pcmPortId1 . . . 41 4.12 pcmPortId2 . . . 42 4.13 pcmPortId3 . . . 43 4.14 pcmPortId4 . . . 44 4.15 pcmPortId5 . . . 45 4.16 pcmPortId6 . . . 46 4.17 pcmPortId7 . . . 47 5 Create BTS . . . 48

5.1 Migration of BR product line complex cells . . . 49

(4)

5.1.2 Example for dual band standard cell. . . 51 5.2 Packet migration . . . 53 5.2.1 Example . . . 55 5.3 Frequency hopping . . . 55 5.4 acDIMinCiRatioEst . . . 56 5.5 adaptiveLaAlgorithm . . . 56 5.6 adminState . . . 57 5.7 amrHoFrInHoThrDlRxQual . . . 58 5.8 amrHoFrThrDlRxQual . . . 59 5.9 amrHoFrThrUlRxQual . . . 60 5.10 amrHoHrInHoThrDlRxQual . . . 61 5.11 amrHoHrThrDlRxQual. . . 62 5.12 amrHoHrThrUlRxQual. . . 63 5.13 amrPocFrPcLThrDlRxQual . . . 64 5.14 amrPocFrPcLThrUlRxQual . . . 65 5.15 amrPocFrPcUThrDlRxQual. . . 66 5.16 amrPocFrPcUThrUlRxQual. . . 67 5.17 amrPocHrPcLThrDlRxQual. . . 68 5.18 amrPocHrPcLThrUlRxQual. . . 69 5.19 amrPocHrPcUThrDlRxQual . . . 70 5.20 amrPocHrPcUThrUlRxQual . . . 71 5.21 antennaHopping . . . 72 5.22 bcchGSM900Band . . . 72 5.23 bsIdentityCodeBCC . . . 73 5.24 bsIdentityCodeNCC . . . 73 5.25 cellId . . . 74 5.26 cellNumberInBtsHW . . . 75 5.27 directGPRSAccessBts . . . 76 5.28 egprsInitMcsAckMode. . . 77 5.29 egprsInitMcsUnAckMode . . . 77 5.30 egprsLinkAdaptEnabled . . . 78 5.31 egprsMaxBlerAckMode. . . 79 5.32 egprsMaxBlerUnAckMode . . . 80 5.33 egprsMeanBepOffset8psk . . . 80 5.34 egprsMeanBepOffsetGmsk. . . 81 5.35 frequencyBandInUse . . . 82 5.36 gprsMsTxPwrMaxCCH1x00 . . . 83 5.37 gprsMsTxpwrMaxCCH . . . 84 5.38 gprsNonBCCHRxlevLower . . . 84 5.39 gprsNonBCCHRxlevUpper . . . 85 5.40 gprsRxlevAccessMin. . . 85 5.41 hcsPriorityClass . . . 86 5.42 hcsThreshold . . . 86 5.43 hoppingMode . . . 87 5.44 hoppingSequenceNumber1 . . . 88 5.45 hoppingSequenceNumber2 . . . 89

(5)

5.47 inactEndTimeMinute . . . 90 5.48 inactStartTimeHour . . . 91 5.49 inactStartTimeMinute . . . 91 5.50 inactWeekDays . . . 92 5.51 csAckDl . . . 93 5.52 csAckUl . . . 94 5.53 csExtAckDl. . . 95 5.54 csExtAckUl. . . 96 5.55 csExtUnackDl . . . 97 5.56 csExtUnackUl . . . 98 5.57 csUnackDl . . . 99 5.58 csUnackUl . . . 100 5.59 initMcsExtAckMode . . . 101 5.60 initMcsExtUnackMode . . . 102 5.61 interferenceAveragingProcessAverPeriod . . . 103 5.62 interferenceAveragingProcessBoundary0 . . . 104 5.63 interferenceAveragingProcessBoundary1 . . . 105 5.64 interferenceAveragingProcessBoundary2 . . . 106 5.65 interferenceAveragingProcessBoundary3 . . . 107 5.66 interferenceAveragingProcessBoundary4 . . . 108 5.67 interferenceAveragingProcessBoundary5 . . . 109 5.68 locationAreaIdLAC. . . 109 5.69 locationAreaIdMCC . . . 110 5.70 locationAreaIdMNC . . . 110 5.71 maxNumberOfRepetition . . . 111 5.72 msMaxDistInCallSetup. . . 112 5.73 msTxPwrMaxCCH . . . 113 5.74 msTxPwrMaxCCH1x00 . . . 115 5.75 msTxPwrMaxGSM . . . 117 5.76 msTxPwrMaxGSM1x00 . . . 118 5.77 noOfMFramesBetweenPaging. . . 119 5.78 nbrOfSlotsSpreadTrans . . . 120 5.79 noOfBlocksForAccessGrant. . . 121 5.80 nonBCCHLayerOffset . . . 122 5.81 pcuCsHopping . . . 123 5.82 pcuCsNonHopping. . . 123 5.83 pcuDlBlerCpHopping . . . 124 5.84 pcuDlBlerCpNonHop . . . 125 5.85 pcuDlLaRiskLevel . . . 126 5.86 pcuUlBlerCpHopping . . . 127 5.87 pcuUlBlerCpNonHop . . . 128 5.88 pcuUlLaRiskLevel . . . 129 5.89 qSearchP . . . 130 5.90 raReselectHysteresis . . . 131 5.91 rac . . . 132 5.92 radiusExtension . . . 133 5.93 segmentId . . . 133

(6)

5.94 segmentName. . . 134 5.95 superRadiusExtension . . . 135 5.96 throughputFactor_cs1cs4dlcs . . . 136 5.97 throughputFactor_cs1cs4ulcs . . . 137 5.98 throughputFactor_mcs1mcs4ulcs . . . 138 5.99 throughputFactor_mcs1mcs9dlcs . . . 139 5.100 throughputFactor_mcs1mcs9ulcs . . . 140 5.101 gprsEnabled . . . 141 5.102 egprsEnabled . . . 142 5.103 cellBarred . . . 143 5.104 cellReselectHysteresis . . . 144 5.105 cellReselectOffset . . . 145 5.106 cellReselectParamInd . . . 146 5.107 temporaryOffset . . . 147 5.108 penaltyTime . . . 148 5.109 callReestablishmentAllowed . . . 149 5.110 dtxMode . . . 150 5.111 amrWbFrCodecModeSet . . . 151 5.112 earlySendingIndication . . . 152 5.113 emergencyCallRestricted . . . 153 5.114 fddQMin . . . 154 5.115 fddQMinOffset. . . 155 5.116 fddQOffset. . . 156 5.117 fddRscpMin . . . 157 5.118 allowIMSIAttachDetach. . . 158 5.119 notAllowedAccessClasses . . . 159 5.120 multiBandCellReporting . . . 160 5.121 plmnPermitted. . . 161 5.122 powerOffset. . . 162 5.123 qSearchI . . . 163 5.124 radioLinkTimeout . . . 165 5.125 radioLinkTimeoutAmr . . . 166 5.126 radioLinkTimeoutAmrHr . . . 167 5.127 rxLevAccessMin . . . 168 5.128 smsCbUsed . . . 169 5.129 maxNumberRetransmission . . . 170 5.130 carrierUnitConfiguration . . . 171 5.131 timerPeriodicUpdateMs. . . 172 5.132 amhUpperLoadThreshold . . . 173 5.133 amhMaxLoadOfTgtCell . . . 174 5.134 btsSpLoadDepTchRateLower. . . 175 5.135 btsSpLoadDepTchRateUpper. . . 176 5.136 amrSegLoadDepTchRateLower . . . 177 5.137 amrSegLoadDepTchRateUpper . . . 178 6 Create TRX . . . 179 6.1 bbUnitSupportsEdge. . . 181

(7)

6.3 channel0Pcm . . . 183 6.4 channel0Subslot . . . 184 6.5 channel0Tsl . . . 185 6.6 channel0Type . . . 186 6.7 channel1Maio . . . 187 6.8 channel1Pcm . . . 188 6.9 channel1Subslot . . . 189 6.10 channel1Tsl . . . 190 6.11 channel1Type . . . 191 6.12 channel2Maio . . . 192 6.13 channel2Pcm . . . 193 6.14 channel2Subslot . . . 194 6.15 channel2Tsl . . . 195 6.16 channel2Type . . . 196 6.17 channel3Maio . . . 197 6.18 channel3Pcm . . . 198 6.19 channel3Subslot . . . 199 6.20 channel3Tsl . . . 200 6.21 channel3Type . . . 201 6.22 channel4Maio . . . 202 6.23 channel4Pcm . . . 203 6.24 channel4Subslot . . . 204 6.25 channel4Tsl . . . 205 6.26 channel4Type . . . 206 6.27 channel5Maio . . . 207 6.28 channel5Pcm . . . 208 6.29 channel5Subslot . . . 209 6.30 channel5Tsl . . . 210 6.31 channel5Type . . . 211 6.32 channel6Maio . . . 212 6.33 channel6Pcm . . . 213 6.34 channel6Subslot . . . 214 6.35 channel6Tsl . . . 215 6.36 channel6Type . . . 216 6.37 channel7Maio . . . 217 6.38 channel7Pcm . . . 218 6.39 channel7Subslot . . . 219 6.40 channel7Tsl . . . 220 6.41 channel7Type . . . 221 6.42 circuitTelecom . . . 222 6.43 eTrxInd. . . 223 6.44 initialFrequency . . . 224 6.45 lapdLinkName . . . 225 6.46 trxFrequencyType . . . 226 6.47 tsc . . . 227 6.48 gprsEnabledTrx . . . 228 6.49 daPool_ID . . . 229

(8)

6.50 preferredBcchMark . . . 230 6.51 adminState . . . 231 7 Create MAL. . . 232 7.1 frequency . . . 232 7.2 frequencyBandInUse . . . 233 8 Create BAL . . . 234 8.1 frequency . . . 235 8.2 frequencyBandInUse . . . 236 9 Create POC . . . 237 9.1 alpha . . . 237 9.2 bepPeriod . . . 238 9.3 bsTxPwrMax . . . 239 9.4 bsTxPwrMax1x00 . . . 241 9.5 bsTxPwrMin . . . 242 9.6 bsTxPwrOffset . . . 243 9.7 enableAla . . . 244 9.8 minIntBetweenAla . . . 245 9.9 pcALDlWeighting . . . 246 9.10 pcALDlWindowSize. . . 247 9.11 pcALUlWeighting . . . 248 9.12 pcALUlWindowSize. . . 249 9.13 pcAQLDlWeighting . . . 250 9.14 pcAQLDlWindowSize . . . 251 9.15 pcAQLUlWeighting . . . 252 9.16 pcAQLUlWindowSize . . . 253 9.17 pcControlInterval. . . 254 9.18 pcIncrStepSize . . . 255 9.19 pcLTQual144RxQual . . . 256 9.20 pcLTQualDlRxQual . . . 257 9.21 pcLTQualUlRxQual . . . 258 9.22 pcLowerThresholdsLevDLRxLevel . . . 259 9.23 pcLowerThresholsLevULRxLevel . . . 260 9.24 pcRedStepSize . . . 261 9.25 pcUTQualDlRxQual . . . 262 9.26 pcUTQualUlRxQual . . . 263 9.27 pcUpperThresholdsLevDLRxLevel . . . 264 9.28 pcUpperThresholdsLevULRxLevel . . . 265 9.29 pcControlEnabled . . . 266 9.30 powerDecrQualFactor. . . 267 10 Create HOC . . . 268 10.1 amhTrhoPbgtMargin . . . 269 10.2 averagingWindowSizeAdjCell . . . 270 10.3 ddeThresholdsLevRxLevel . . . 271 10.4 enaFastAveHo . . . 272

(9)

10.6 enableIntraHoUl . . . 274 10.7 enableMsDistance . . . 275 10.8 enablePowerBudgetHo . . . 276 10.9 enableSddchHandover . . . 277 10.10 enableUmbrellaHo . . . 278 10.11 hoAvaragingLevDLWeighting . . . 279 10.12 hoAvaragingLevDlWindowSize . . . 280 10.13 hoAveragingLevUlWeighting . . . 281 10.14 hoAveragingLevUlWindowSize . . . 282 10.15 hoAveragingQualDlWeighting . . . 283 10.16 hoAveragingQualDlWindowSize . . . 284 10.17 hoAveragingQualUlWeighting . . . 285 10.18 hoAveragingQualUlWindowSize . . . 286 10.19 hoPeriodPbgt . . . 287 10.20 hoTLDlPx . . . 288 10.21 hoTLDlRxLevel . . . 289 10.22 hoTLUlNx. . . 290 10.23 hoTLUlPx . . . 291 10.24 hoTLUlRxLevel . . . 292 10.25 hoTQDlNx . . . 293 10.26 hoTQDlPx . . . 294 10.27 hoTQDlRxQual . . . 295 10.28 hoTQUlNx . . . 296 10.29 hoTQUlPx . . . 297 10.30 hoTQUlRxQual . . . 298 10.31 hoThresholdsInterferenceDlRxLevel . . . 299 10.32 hoThresholdsInterferenceULRxLevel . . . 300 10.33 hoThresholdsLevDLNx . . . 301 10.34 intraHoLoRxLevLimAmrHr. . . 302 10.35 maxMsDistanceHoThreshold. . . 303 10.36 minIntBetweenHoReq . . . 304 10.37 minIntBetweenUnsuccHoAttempt . . . 305 10.38 minIntUnsuccIsHo . . . 306 10.39 minMsDistanceHoThreshold . . . 307 10.40 modifiedAveWinNCell . . . 308 10.41 msDistanceAveragingParamHreqave . . . 309 10.42 msDistHoParamMsRngMax. . . 310 10.43 msSpeedDetectionState . . . 311 10.44 smaxMsDistanceHoThreshold . . . 312 10.45 sminMsDistanceHoThreshold . . . 313 10.46 superReuseBadCiThresholdCiRatio . . . 314 10.47 superReuseBadRxLevThresholdRxLevel . . . 315 10.48 superReuseGoodCiThresholdCiRatio . . . 316 10.49 superReuseGoodRxLevThresholdRxLevel . . . 317 10.50 interSystemDa . . . 318 10.51 intraHoUpRxLevLimAmrHr . . . 319 10.52 msSpeedThresholdNx . . . 320

(10)

10.53 msSpeedThresholdPx. . . 321 10.54 reportingOffsetFdd . . . 322 10.55 reportingThresholdFdd . . . 323 10.56 fddRepThr2 . . . 324 10.57 qSearchC . . . 325 11 Create ADCE . . . 326 11.1 adjCellBsicBcc . . . 327 11.2 adjCellBsicNcc . . . 327 11.3 adjacentCellIdCI . . . 328 11.4 adjacentCellIdLac . . . 328 11.5 adjacentCellIdMCC . . . 329 11.6 adjacentCellIdMNC . . . 330 11.7 bcchFrequency . . . 331 11.8 chainedAdjacentCell . . . 332 11.9 dtmPowerBudgetMargin . . . 333 11.10 enableHoMarginLevQual . . . 334 11.11 fastMovingThreshold. . . 335 11.12 gprsEnabled . . . 336 11.13 gprsMsTxPwrMaxCCH1x00 . . . 337 11.14 gprsMsTxpwrMaxCCH . . . 338 11.15 gprsPenaltyTime . . . 339 11.16 gprsRxlevAccessMin. . . 340 11.17 gprsTemporaryOffset . . . 341 11.18 hcsPriorityClass . . . 342 11.19 hcsThreshold . . . 343 11.20 hoMarginLev . . . 344 11.21 hoMarginPbgt . . . 345 11.22 hoMarginQual . . . 346 11.23 hoPriorityLevel . . . 347 11.24 msTxPwrMaxGSM . . . 348 11.25 msTxPwrMaxGSM1x00 . . . 349 11.26 nccrEgprsPbgtMargin . . . 350 11.27 nccrEgprsQualityMargin . . . 351 11.28 nccrGprsPbgtMargin . . . 352 11.29 nccrGprsQualityMargin . . . 353 11.30 rac . . . 354 11.31 levelAdj . . . 355 11.32 reportingPriority. . . 356 11.33 rxLevMinCell . . . 357 11.34 trhoTargetLevel. . . 358 12 Create ADJW . . . 359 12.1 AdjwCId. . . 359 12.2 cellParameter . . . 360 12.3 fddReportingPriority . . . 361 12.4 isnccrFddQualityThr . . . 362

(11)

12.6 mcc . . . 364 12.7 minEcnoThreshold. . . 365 12.8 mnc . . . 366 12.9 rncId . . . 367 12.10 scramblingCode . . . 368 12.11 syncCase . . . 369 12.12 txDiversityInd . . . 370 12.13 uarfcn . . . 371 13 Create DAP . . . 372 13.1 id . . . 372 13.2 firstTSL . . . 373 13.3 lastTSL. . . 374 13.4 pcmCircuit_ID . . . 375 13.5 bcsuID . . . 376 13.6 pcuID . . . 377 13.7 psei . . . 378

(12)

Summary of changes

Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Issue Date Summary

01 10/2009 First issue for RG10(BSS)

02 04/2010 Updated chapters: 3.12 dChannelType 4.11 btsSiteSubtype 5.93 rac 6.48 gprsEnabledTRX 6.50 preferredBcchMark 6.51 adminState 9.19 pcLTQual144RXQual 9.20 pcLTQualDIRxQual 9.21 pcLTQualUIRxQual 9.25 pcUTQualDIRxQual 9.26 pcUTQualUIRxQual New chapter: 13 Create DAP

(13)

03 09/2010 Updated chapters: 3.13 parameter 4.13 pcmPortId0 4.14 pcmPortId1 4.15 pcmPortId2 4.16 pcmPortId3 4.17 pcmPortId4 4.18 pcmPortId5 4.19 pcmPortId6 4.20 pcmPortId7 5.7 amrHoFrInHoThrDlRxQual 5.21 antennaHopping 5.43 hoppingMode 5.73 msTxPwrMaxCCH 5.74 msTxPwrMaxCCH1x00 5.103 cellBarred 5.104 cellReselectHysteresis 5.105 cellReselectOffset 5.106 cellReselectParamInd 5.107 temporaryOffset 5.108 penaltyTime 5.109 callReestablishmentAllowed 5.110 dtxMode 5.111 amrWbFrCodecModeSet 5.112 earlySendingIndication 5.113 emergencyCallRestricted 5.114 fddQMin 5.115 fddQMinOffset 5.116 fddQOffset 5.117 fddRscpMin 5.118 allowIMSIAttachDetach 5.119 notAllowedAccessClasses 5.120 multiBandCellReporting 5.121 plmnPermitted 5.122 powerOffset 5.123 qSearchI 5.124 radioLinkTimeout 5.125 radioLinkTimeoutAmr

(14)

Issue 03 for release RG10(BSS) 03 09/2010 Updated chapters: 5.126 radioLinkTimeoutAmrHr 5.127 rxLevAccessMin 5.128 smsCbUsed 5.129 maxNumberRetransmission 5.130 carrierUnitConfiguration 5.131 timerPeriodicUpdateMs 5.132 amhUpperLoadThreshold 5.133 amhMaxLoadOfTgtCell 5.134 btsSpLoadDepTchRateLower 5.135 btsSpLoadDepTchRateUpper 5.136 amrSegLoadDepTchRateLower 5.137 amrSegLoadDepTchRateUpper 10.54 reportingOffsetFdd 10.55 reportingThresholdFdd 10.56 fddRepThr2 10.57 qSearchC

(15)

1 Introduction

This document considers in detail all the configuration parameters in the BSS managed object hierarchy that need to be configured for operating the BTSplus with the Flexi BSC

product family.

When migrating a BTSplus base station to the Flexi BSC product family, a related “BCF” managed object instance needs to be created in the Flexi BSC configuration plan. The underlying hierarchy of the BCF managed object (such as the “BTS”, “TRX” and “POC” managed objects) also needs to be created. The new BTSplus base station type is rep-resented by the value 7 being assigned to the “site type (TYPE)” parameter.

The BTSplus is migrated using the exporter offline migration tool. In particular, this tool automatically creates all the BSS managed objects necessary for operating the BTSplus with the Flexi BSC product family. It maps BTSplus-related configuration parameters from the BR info model to the equivalent parameters in the BSS managed object hierarchy. Parameters that are required by the Flexi BSC, but that cannot be found in the eBSC/BSC1 configuration plan, are provided by means of a control file that is manually edited by the user during the migration process and used as input to the exporter tool.

Management of the BTSplus base station site type by the Flexi BSC product family is also supported by a number of new parameters in the BSS managed object hierarchy. For example, a new BCF parameter “BTS site subtype (-)” distinguishes between the three different types of BTSplus base station site: basic, mainline and eMicro.

The migration of the BTSplus to a Flexi BSC requires an OAM network that is already operational, including NetAct and the Flexi BSC. It is possible to have other BTS types (for example the Flexi EDGE BTS) being managed by the same Flexi BSC together with the BTSplus. For more information on the BTSplus migration procedures and the exporter migration tool, refer to the “Migrating BTSplus to the Flexi BSC product family” functional area description. For a description of the control file, refer to “Control File format”.

For an overall description of operating the BTSplus with the Flexi BSC product family, refer to the “BSS21469: BSxx@Flexi BSC product family” feature description.

1.1 Abis mediation of BTSplus parameters towards Flexi BSC

Besides the migration of BTSplus-related configuration parameters to the BSS

managed object hierarchy, as described in “Introduction”, the parameters and attributes required by the BTSplus for its operation also need to be translated in real time from BR format to Flexi BSC format and vice versa. This translation is done by an Abis interface mediation function on the BTSplus. A detailed description of this mediation can be found in “Abis mediation of BTSplus parameters/attributes towards the Flexi BSC product family”.

Furthermore, a listing of the BTSplus-related parameters and attributes in BR format can be found in the respective command manuals:

• “BTSplus basic commands at Flexi BSC product family” • “BTSplus mainline commands at Flexi BSC product family” • “BTSplus eMicro commands at Flexi BSC product family”

(16)

2 ControlFile format

When using the exporter migration tool to automatically rehost BTSplus base stations from an eBSC/BSC1 to the Flexi BSC product family, you need to provide additional information to assist the migration process. For example, you need to specify which BTSM objects need to be migrated, and which ID they will be assigned. For this purpose, an XML-based control file is used as input for the exporter tool, together with the eBSC/BSC1 configuration file.

For more information, refer to “Data export and migration” in the “Migrating BTSplus to the Flexi BSC product family” functional area description.

2.1 Common info (not class-specific) for the migration

proce-dure

2.2 BTSM selection and migration (BCF and O&M LAPD

cre-ation)

<commonData>

<p name=“cmDataName”>…</p> name attribute of the cmData tag in the resulting script; takes the value of NAME<bscid>, where bscid is the value given by the --bscid input parameter to the exporter migration tool <p name=“cmDataId”>…</p> id attribute of the cmData tag in the resulting

script; takes the value of ID<bscid>, where bscid is as described above

<p name=“bscId”>…</p> identifier of the target BSC; takes the value of <bscid>, where bscid is as described above <p name=“bscDistName”>…</p> distinguishing name of the target BSC; takes the

value of PLMN-PLMN/BSC-<bscid>, where bscid is as described above

</commonData>

<sourceObject mmlName=“…” BTSM to be migrated

<p name=“distNamePart”>…</p> BCF-level part of distName of the created BCF; takes the value of BCF-<btsmn>, where btsmn is the source BTSM index <p name=“lapdLinkName”>…</p> name given to the OAM LAPD link of the

BCF and used as the lapdLinkName param-eter of the created BCF and as the name parameter of the related OAM LAPD; takes the value of L<lapdn>, where lapdn is a unique index of LAPDs being migrated and starts from 1, unless otherwise specified by the --first_lapd input parameter to the exporter tool

(17)

2.3 TRX selection and migration (LAPD creation only)

<p name=“LAPD_distNamePart”>…</p> LAPD-level part of the distName of the created OAM LAPD; takes the value of LAPD-<lapdn>, where lapdn is as described above

<p name=“MISC_pcmCon0”>…</p> the PCM in the new configuration to be asso-ciated with the existing PCM specified in PCMCON0; takes the value of <pcmbn>, where pcmbn is the source PCMB index, and is possibly added to the value specified by the --first_pcmb input parameter to the exporter tool

<p name=“MISC_pcmCon1”>…</p> the PCM in the new configuration to be asso-ciated with the existing PCM specified in PCMCON1

<p name=“MISC_pcmCon2”>…</p> the PCM in the new configuration to be asso-ciated with the existing PCM specified in PCMCON2

<p name=“MISC_pcmCon3”>…</p> the PCM in the new configuration to be asso-ciated with the existing PCM specified in PCMCON3

<p name=“MISC_pcmCon4”>…</p> the PCM in the new configuration to be asso-ciated with the existing PCM specified in PCMCON4

<p name=“MISC_pcmCon5”>…</p> the PCM in the new configuration to be asso-ciated with the existing PCM specified in PCMCON5

<p name=“MISC_pcmCon6”>…</p> the PCM in the new configuration to be asso-ciated with the existing PCM specified in PCMCON6

<p name=“MISC_pcmCon7”>…</p> the PCM in the new configuration to be asso-ciated with the existing PCM specified in PCMCON7

</sourceObject>

<sourceObject mmlName=“…”> TRX to be migrated

<p name=“lapdLinkName”>…</p > lapdLinkName of the created TRX and name of the related radio signaling LAPD; takes the value of L<lapdn>, where lapdn is a unique index of LAPDs being migrated and starts from 1, unless otherwise speci-fied by the --first_lapd input parameter to the exporter migration tool

(18)

<p name=“LAPD_distNamePart”>…</p > LAPD-level part of distName of created sig-naling LAPD; takes the value of LAPD-<lapdn>, where lapdn is as described above

<p name=“LAPD_tei”>…</p > TEI of LAPD; takes the value of <trxn>, where trxn is as described above </sourceObject>

(19)

3 Create LAPD

The CREATE LAPD instances are derived as : • One OAMLAPD for the related BCF

(derived from the first LPDLM configured on the BTSplus PORT_0)

• NUM_TRX: one radio signaling link LAPD created for each TRX subordinated to the related BCF

g

The BR LAPD allocation on the PCM line (the related timeslot number) is not changed in the migrated configuration

Create LAPD Example from Real NetAct Configuration script

<managedObject class="LAPD" operation="create" version="S14.1">

<p name="adminState">1</p> <p name="abisSigChannelTimeSlotPcm">133</p> <p name="abisSigChannelTimeSlotTsl">30</p> <p name="abisSigChannelSubSlot">2</p> <p name="bitRate">32</p> <p name=" dChannelType ">0</p> <p name=" parameterSetNumber">2</p> <p name="parentBSCId">85703</p> <p name="relatedLapdLinkName">T45</p> <p name="name">EXS12</p> <p name="sapi">0</p> <p name="tei">2</p> </managedObject>

(20)

3.1 abisSigChannelSubSlot

Obj LAPD

M,O,N,internal mapped

<p name=“abisSigChannelSubSlot">Val</p>

Full name Sub TSL

Type Number

Range 0...7, step 1

Internal value gui_value

Default

Description SubTimeslot of the PCM where the LAPD will be created.

BitRate 8 kBit/s, Sub TSL = 0..7. BitRate 16 kBit/s, Sub TSL = 0,2,4,6. BitRate 32 kBit/s, Sub TSL = 0,2,4. BitRate 64 kBit/s, Sub TSL = Not Defined

3GPP

Multip 1

Modification Not modifiable

Modified

onCreate mandatory

Val info derived from [LAPD] LPDLMN and from control file for PCM

mapping (related BTSM sourceObject)

(21)

3.2 abisSigChannelTimeSlotPcm

Obj LAPD M,O,N,internal mapped <p name=“abisSigChannelTimeSlot-Pcm">Val</p> Full name PCM Type Number Range 0...3391, step 1

Internal value gui_value

Default

Description PCM where the LAPD link has been created

3GPP

Multip 1

Modification Not modifiable

Modified

onCreate mandatory

Val info derived from [LAPD] LPDLMN and from control file for PCM

(22)

3.3 abisSigChannelTimeSlotTsl

Obj LAPD M,O,N,internal mapped <p name=“abisSigChan-nelTimeSlotTsl">Val</p> Full name TSL Type Number Range 1...31, step 1

Internal value gui_value

Default

Description Timeslot of the PCM where the LAPD link has been created

3GPP

Multip 1

Modification Not modifiable

Modified

onCreate mandatory

Val info derived from [LAPD] LPDLMN and from control file for PCM

(23)

3.4 adminState

Obj LAPD

M,O,N,internal M

<p name=“adminState">Val</p>

Full name Administrative State

Type Enumeration

Range Unlocked (1), Locked (3)

Internal value gui_value

Default

Description Administrative State of the object. Note that, when using file

based activation method in plan provisioning, LAPD will be always automatically unlocked after creation regardless of the planned value. 3GPP Multip 1 Modification Online Modified onCreate optional Val 1

(24)

3.5 bitRate

3.6 Id

NetAct does not define the final ID for the LAPD, but the BSC does. So NetAct only creates a temporary ID for the LAPD. This temporary ID is created automatically and does not need to be present as part of distName in the RAML file. During plan provision-ing to the Flexi BSC, the BSC will reserve the actual ID for the LAPD. That info will be provided to NetAct as a LAPD creation event.

Obj LAPD

M,O,N,internal M

<p name=“bitRate">Val</p> gui_value

Full name Bit Rate

Type Enumeration

Range 8 kbit/s (8), 16 kbit/s (16), 32 kbit/s (32), 64 kbit/s (64)

Internal value Default

Description LAPD Link Bit Rate

3GPP

Multip 1

Modification Not modifiable

Modified

onCreate mandatory

Val For the O&M LAPD: is derived from the BR [LPDLM] ABISCH

(25)

3.7 name

Obj LAPD

M,O,N,internal M

<p name=“name">Val</p>

Full name Name

Type String

Range 1...5 characters

Internal value gui_value

Default

Description NW Name and Name of LAPD object. Enter with capital letters.

3GPP

Multip 1

Modification Not modifiable

Modified

onCreate mandatory

Val For the O&M LAPD: “lapdLinkName" info in control file (related

BTSM sourceObject)

For the TRX LAPD: “lapdLinkName" info in control file (related TRX sourceObject)

(26)

3.8 parentBSCId

3.9 relatedLapdLinkName

RelatedLapdLinkName is set only in special cases. Therefore, it is not considered for migration.

Obj LAPD

M,O,N,internal Internal

<p name=“ parentBSCId">Val</p>

Full name /* not visible to the Operator: it is assigned by NetAct

Config-urator automatically */

Type Number

Range

Internal value /* not visible to the Operator: it is assigned by NetAct

Config-urator automatically */ Default

Description /* not visible to the Operator: it is assigned by NetAct

Config-urator automatically */ 3GPP

Multip

Modification /* not visible to the Operator: it is assigned by NetAct

Config-urator automatically */ Modified

onCreate /* not visible to the Operator: it is assigned by NetAct

Config-urator automatically */

Val For all LAPD (O&M and signalling): “bscId" info in control file

(27)

3.10 sapi

Obj LAPD

M,O,N,internal M

<p name=“sapi">Val</p>

Full name SAPI

Type Enumeration

Range Signalling LAPD (0), AcPool LAPD (61), O&M LAPD (62)

Internal value gui_value

Default Signalling LAPD (0)

Description Service access point identifier that corresponds to the LAPD

Link object. 3GPP

Multip 1

Modification Not modifiable

Modified

onCreate mandatory

Val For the O&M LAPD: 62

(28)

3.11 tei

Obj LAPD

M,O,N,internal M

<p name=“tei">Val</p>

Full name TEI

Type Number

Range 0...126, step 1

Internal value gui_value

Default 0

Description Terminal end point identifier TEI = 1 for O&M LAPD and for

Signalling LAPD it is the TRX ID. 3GPP

Multip 1

Modification Not modifiable

Modified

onCreate mandatory

Val For the O&M LAPD: 1

For the TRX LAPD: assigned to “id” of the related TRX (derived as unique number within BTSM)

(29)

3.12 dChannelType

Obj LAPD

M,O,N,internal

<p name=“ dChannelType ">Val</p>

Full name D-Channel Type

Type Number

Range normal (0), combi (1), multi (2)

Internal value gui_value

Default 0

Description With this parameter you define whether or not the O&M and

telecom LAPD links are allocated to the same Abis PCM time slot or there is multiplexed singnalling link. Parameter is used instead of the combinedSignalling parameter from S14.1 onwards. NOTE: Platform MML interface NOTE: Use value ‘multi’ for BTSplus.

3GPP

Multip 1

Modification Not modifiable

Modified

onCreate mandatory

(30)

3.13 parameterSetNumber

Obj LAPD

M,O,N,internal

<p name=“ parameterSetNumber ">Val</p>

Full name Parameter Set Number

Type Enum

Range Standard Abis setup (0), Satellite Abis setup (1), BTSplus Abis

setup (2), BTSplus Satellite Abis setup (3), IP Abis setup 1 (4), IP Abis setup 2 (for long delays) (5), IP Abis setup 3 (for low quality lines) (6), Enhanced Satellite Abis Setup (7), Standard Abis setup (8)

Internal value gui_value

Default 0

Description With this parameter you define the used predefined parameter

set of LAPD in LAPD creation for BTSplus site type.

NOTE: Platform MML interface NOTE: Parameter is manda-tory if site type is BTSplus.

3GPP

Multip 0

Modification Not modifiable

Modified

onCreate mandatory

Val parameterSetNumber = BTSplus Abis setup (2) if

[BTSM]LPDLMSAT is set to FALSE

parameterSetNumber = BTSplus Satellite Abis setup (3) if [BTSM]LPDLMSAT is set to TRUE

Note: the BTSM parameter LPDLMSAT indicates whether the LAPD link on the Abis interface is satellited or terrestrial.

(31)

4 Create BCF

Create BCF Example from Real NetAct Configuration script

<managedObject class="BCF" operation="create" version="S14.1" distName="BSC-12345/BCF-45"> <defaults name="ESTemplate"/> <p name="name">ExampleSite</p> <p name="bcfType">5</p> <p name="longitude">269367786</p> <p name="latitude">605064855</p> <p name="siteId">ExampleSite</p> <p name="lapdLinkName">EXSOM</p> <p name="adminState">3</p> <p name=" btsSiteSubtype ">3</p> <p name=" pcmPortId0">3</p> <p name=" pcmPortId1">4</p> <p name=" pcmPortId2">5</p> <p name=" pcmPortId3">6</p> <p name=" pcmPortId4">7</p> <p name=" pcmPortId5">8</p> <p name=" pcmPortId6">9</p> <p name=" pcmPortId7">10</p> </managedObject>

(32)

4.1 adminState

Obj BCF

M,O,N,internal M

<p name=“adminState">Val</p>

Full name Administrative State

Type Enumeration

Range Unlocked (1), Locked (3)

Internal value gui_value

Default Locked (3)

Description Administrative State of the object in the NW after object creation

or modification. 3GPP Multip 1 Modification online Modified onCreate optional Val 1

(33)

4.2 batteryBackupProcedure

Obj BCF

M,O,N,internal M

<p name=”batteryBackupProcedure”>Val</p>

Full name BTS Battery Backup Procedure

Type Enumeration

Range All Alive (0), Transmission and BCCH Alive (1), Transmission

Alive (2)

Internal value gui value

Default All Alive

Description With this parameter you define what type of BTS battery

backup procedure is used. The procedure is executed when the mains power goes down at the BTS site and there is a battery backup unit.

3GPP Multip 1 Modification online Modified onCreate optional Val 0

(34)

4.3 bcchTrxBatbuTimer

Obj BCF

M,O,N,internal mapped

<p name=“bcchTrxBatbuTimer">Val</p>

Full name BCCH TRX Shutdown Timer

Type Number

Range 0...600 min, step 1 min

Internal value gui_value * 6000

Default 0 min

Description With this parameter you define the time period after which

shutdown group 0 TRXs are powered down. The time begins after the TRX Shutdown Timer1 has expired.

3GPP

Multip 1

Modification online

Modified

onCreate optional

(35)

4.4 bcfType

Obj BCF

M,O,N,internal M

<p name=“bcfType">Val</p>

Full name Site Type

Type Enumeration

Range Nokia 2nd Generation (0), Nokia Talk-family (1), Nokia

PrimeS-ite (2), Nokia MetroSPrimeS-ite (3), Nokia InSPrimeS-ite (4), Nokia UltraSPrimeS-ite (5), Nokia Flexi EDGE (6)

Internal value gui_value

Default

Description Identifies the type of the BTS site. Modifiable when provisioning

plan with CM Operations Manager or command line interface and not having Use File Based Activation Method for S12 BSC -option selected in GSM Options.

3GPP

Multip 1

Modification Requires object locking

Modified When BCF is locked. The OMU link of the BCF cannot be in

working state when the BTS site type is modified to Nokia Ultra-Site.

onCreate mandatory

(36)

4.5 lapdLinkName

4.6 normTrxBatbuTimer

Obj BCF

M,O,N,internal M

<p name=“lapdLinkName">Val</p>

Full name LAPD Link Name

Type String

Range 1...5 characters

Internal value gui_value

Default

Description LAPD link name of the BTS Site O&M Link

3GPP

Multip 1

Modification online

Modified

onCreate mandatory

Val “lapdLinkName” info in control file

Obj BCF

M,O,N,internal mapped

<p name=“normTrxBatbuTimer">Val</p>

Full name TRX Shutdown Timer

Type Number

Range 0...600 min, step 1 min

Internal value gui_value * 6000

Default 0 min

Description With this parameter you define the time period after which

shutdown group 1 TRXs are powered down. The time begins after the TRX Shutdown Timer 2 has expired.

3GPP

Multip 1

Modification online

Modified

onCreate optional

(37)

4.7 normTrxBatbuTimer2

Obj BCF

M,O,N,internal mapped

<p name=“normTrxBatbuTimer2">Val</p>

Full name TRX Shutdown Timer 2

Type Number

Range 0...600 min, step 1 min

Internal value gui_value * 6000

Default 0 min

Description With this parameter you define the time period after which

shutdown group 2 TRXs are powered down. The time begins after the TRX Shutdown Timer 3 has expired.

3GPP

Multip 1

Modification online

Modified

onCreate optional

Val MAX (50, MIN (INT ([BTSM]EMT2(emergencyTimer2) / 2), 550))

(38)

4.8 normTrxBatbuTimer3

Obj BCF

M,O,N,internal mapped

<p name=“normTrxBatbuTimer3">Val</p>

Full name TRX Shutdown Timer 3

Type Number

Range 0...600 min, step 1 min

Internal value gui_value

Default 0 min

Description With this parameter you define the time period after which

shutdown group 3 TRXs are powered down. Parameter is valid only when BTS Battery Backup Procedure parameter has value ”Transmission and BCCH Alive (1)” or ”Transmission Alive (2)" 3GPP

Multip 1

Modification online

Modified

onCreate optional

(39)

4.9 btsSiteSubtype

Obj BCF

M,O,N,internal mapped

<p name=“ btsSiteSubtype ">Val</p>

Full Name BTS Site Subtype

Type Enum

Range Mainline (M) (0), eMicro (E) (1), Basic (B) (2), No BTS sub site

(255)

Internal Value gui_value

Default No BTS sub site (255)

Description With this parameter you identify the subtype of the BTS site.

Parameter is not modifiable. NOTE: Parameter is mandatory if site type is BTSplus. NOTE: Parameter is valid only for BTSplus site type. 3Gpp Multip 1 Modification unmodifiable Modified onCreate optional

Val The parameter btsSiteSubtype is mapped starting from BTSM

EXPSWV value.

Taking into consideration that the parameter EXPSWV is composed by the sub-fields SS-VV-RR-PR-LL-CL_YY-MM-DD, the btsSiteSubtype is assigned using the following mapping rule:

btsSiteSubtype = Mainline if VV = 04 and PR = 01 btsSiteSubtype = EMicro if VV = 04 and PR = 05 btsSiteSubtype = BasicI if VV = 04 and PR = 06

(40)

4.10 pcmPortId0

Obj BCF

M,O,N,internal mapped

<p name=“ pcmPortId0 ">Val</p>

Full name PCM Port ID 0

Type Number

Range 0..3391 step 1

Internal value gui_value

Default

-Description With this parameter you identify the BSC PCM used in BTS Abis

Port 0 in BTSplus side. PCM of TRX is defined in TRX creation. 3GPP

Multip 1

Modification Requires BCF object locking

Modified

onCreate Mandatory

Val pcmPortId<x>shall be mapped on the [BTSM] PCMCON<n> (n

= 0..7):

pcmPortId0 is equal to the ‘PcmbNumber’ sub-attribute of PCM-CON<n> having PortNumber = PORT_0

(41)

4.11 pcmPortId1

Obj BCF

M,O,N,internal mapped

<p name=“ pcmPortId1 ">Val</p>

Full name PCM Port ID 1

Type Number

Range 0..3391 step 1

Internal value gui_value

Default

-Description With this parameter you identify the BSC PCM used in BTS

Abis Port 1 in BTSplus side. PCM of TRX is defined in TRX cre-ation.

3GPP

Multip 1

Modification Requires BCF object locking

Modified

onCreate Mandatory

Val pcmPortId<x>shall be mapped on the [BTSM] PCMCON<n> (n

= 0..7):

pcmPortId1 is equal to the ‘PcmbNumber’ sub-attribute of PCMCON<n> having PortNumber = PORT_1

(42)

4.12 pcmPortId2

Obj BCF

M,O,N,internal mapped

<p name=“ pcmPortId2 ">Val</p>

Full name PCM Port ID 2

Type Number

Range 0..3391 step 1

Internal value gui_value

Default

-Description With this parameter you identify the BSC PCM used in BTS

Abis Port 2 in BTSplus side. PCM of TRX is defined in TRX cre-ation.

3GPP

Multip 1

Modification Requires BCF object locking

Modified

onCreate Mandatory

Val pcmPortId<x>shall be mapped on the [BTSM] PCMCON<n> (n

= 0..7):

pcmPortId2 is equal to the ‘PcmbNumber’ sub-attribute of PCMCON<n> having PortNumber = PORT_2

(43)

4.13 pcmPortId3

Obj BCF

M,O,N,internal mapped

<p name=“ pcmPortId3 ">Val</p>

Full name PCM Port ID 3

Type Number

Range 0..3391 step 1

Internal value gui_value

Default

-Description With this parameter you identify the BSC PCM used in BTS

Abis Port 3 in BTSplus side. PCM of TRX is defined in TRX cre-ation.

3GPP

Multip 1

Modification Requires BCF object locking

Modified

onCreate Mandatory

Val pcmPortId<x>shall be mapped on the [BTSM] PCMCON<n> (n

= 0..7):

pcmPortId3 is equal to the ‘PcmbNumber’ sub-attribute of PCMCON<n> having PortNumber = PORT_3

(44)

4.14 pcmPortId4

Obj BCF

M,O,N,internal mapped

<p name=“ pcmPortId4 ">Val</p>

Full name PCM Port ID 4

Type Number

Range 0..3391 step 1

Internal value gui_value

Default

-Description With this parameter you identify the BSC PCM used in BTS Abis

Port 4 in BTSplus side. PCM of TRX is defined in TRX creation. 3GPP

Multip 1

Modification Requires BCF object locking

Modified

onCreate Mandatory

Val pcmPortId<x>shall be mapped on the [BTSM] PCMCON<n> (n

= 0..7):

pcmPortId4 is equal to the ‘PcmbNumber’ sub-attribute of PCM-CON<n> having PortNumber = PORT_4

(45)

4.15 pcmPortId5

Obj BCF

M,O,N,internal mapped

<p name=“ pcmPortId5 ">Val</p>

Full name PCM Port ID 5

Type Number

Range 0..3391 step 1

Internal value gui_value

Default

-Description With this parameter you identify the BSC PCM used in BTS Abis

Port 5 in BTSplus side. PCM of TRX is defined in TRX creation. 3GPP

Multip 1

Modification Requires BCF object locking

Modified

onCreate Mandatory

Val pcmPortId<x>shall be mapped on the [BTSM] PCMCON<n> (n

= 0..7):pcmPortId5 is equal to the 'PcmbNumber' sub-attribute of PCMCON<n> having PortNumber = PORT_5

(46)

4.16 pcmPortId6

Obj BCF

M,O,N,internal mapped

<p name=“ pcmPortId6 ">Val</p>

Full name PCM Port ID 6

Type Number

Range 0..3391 step 1

Internal value gui_value

Default

-Description With this parameter you identify the BSC PCM used in BTS Abis

Port 6 in BTSplus side. PCM of TRX is defined in TRX creation. 3GPP

Multip 1

Modification Requires BCF object locking

Modified

onCreate Mandatory

Val pcmPortId<x>shall be mapped on the [BTSM] PCMCON<n> (n

= 0..7):

pcmPortId6 is equal to the ‘PcmbNumber’ sub-attribute of PCM-CON<n> having PortNumber = PORT_6

(47)

4.17 pcmPortId7

Obj BCF

M,O,N,internal mapped

<p name=“ pcmPortId7 ">Val</p>

Full name PCM Port ID 7

Type Number

Range 0..3391 step 1

Internal value gui_value

Default

-Description With this parameter you identify the BSC PCM used in BTS

Abis Port 7 in BTSplus side. PCM of TRX is defined in TRX cre-ation.

3GPP

Multip 1

Modification Requires BCF object locking

Modified

onCreate Mandatory

Val pcmPortId<x>shall be mapped on the [BTSM] PCMCON<n> (n

= 0..7):

pcmPortId7 is equal to the ‘PcmbNumber’ sub-attribute of PCMCON<n> having PortNumber = PORT_7

(48)

5 Create BTS

Create BTS Example from Real NetAct Configuration script

<managedObject class="BTS" operation="create" version="S14.1" distName="BSC-12345/BCF-45/BTS-198"> <defaults name="ESTemplate"/> <p name="name">57113</p> <p name="cellId">57113</p> <p name="locationAreaIdLAC">5210</p> <p name="masterBcf">1</p> <p name="bsIdentityCodeBCC">2</p> <p name="bsIdentityCodeNCC">5</p> <p name="locationAreaIdMCC">244</p> <p name="locationAreaIdMNC">05</p> <p name="rac">23</p> <p name="frequencyBandInUse">0</p> <p name="gprsEnabled">1</p> <p name="egprsEnabled">1</p> <p name="diversityUsed">1</p> <p name="nwName">EXAMPLESITEG1</p> <p name="defaultGPRScapacity">1</p> <p name="upperLimitCellLoadHSCSD">80</p> <p name="lowerLimitCellLoadHSCSD">80</p> <p name="smsCbUsed">1</p> <p name="cellBarred">1</p> <p name="cellReselectHysteresis">1</p> <p name="cellReselectOffset">1</p> <p name="cellReselectParamInd">1</p> <p name="temporaryOffset">1</p> <p name="penaltyTime">1</p> <p name="callReestablishmentAllowed">1</p> <p name="dtxMode">1</p> <p name="amrWbFrCodecModeSet">1</p> <p name="earlySendingIndication">1</p> <p name="emergencyCallRestricted">1</p> <p name="fddQMin">1</p> <p name="fddQMinOffset">1</p>

(49)

5.1 Migration of BR product line complex cells

Besides standard cells, the BTSplus administered by the eBSC/BSC1 can also be used to create complex overlay cell structures. When migrating these cell structure types to the Flexi BSC, special considerations have to be taken into account.

The following cell types are considered: • Standard cells

• Extended cells • Concentric cells

• Dual band standard cells

Standard cells

The most common situation during migration is the direct mapping of a standard BTSplus cell to a standard cell managed by the Flexi BSC. This mapping is done auto-matically by the exporter migration tool. Refer to “Example for standard cell” for an example of a migrated standard cell.

<p name="fddRscpMin">1</p> <p name="allowIMSIAttachDetach">1</p> <p name="notAllowedAccessClasses">1</p> <p name="multiBandCellReporting">1</p> <p name="plmnPermitted">1</p> <p name="powerOffset">1</p> <p name="qSearchI">1</p> <p name="radioLinkTimeout">1</p> <p name="radioLinkTimeoutAmr">1</p> <p name="radioLinkTimeoutAmrHr">1</p> <p name="rxLevAccessMin">1</p> <p name="smsCbUsed">1</p> <p name="maxNumberRetransmission ">1</p> <p name="carrierUnitConfiguration ">1</p> <p name="timerPeriodicUpdateMs ">1</p> <p name="amhUpperLoadThreshold ">1</p> <p name="amhMaxLoadOfTgtCell">1</p> <p name="btsSpLoadDepTchRateLower">1</p> <p name="btsSpLoadDepTchRateUpper">1</p> <p name="amrSegLoadDepTchRateLower">1</p> <p name="amrSegLoadDepTchRateUpper">1</p> </managedObject>

(50)

Extended cells

Extended cells managed by the eBSC/BSC1 are not migrated to the Flexi BSC. Refer to “Extended cells” for more information.

Concentric cells

When administering the BTSplus with the Flexi BSC product family, concentric cells are managed as standard cells if they are not dual band. If the TRX of the INNER and COMPLETE area belong to different frequency bands, the cells are managed as dual band standard cells. Therefore, a pair of Flexi BSC cells is generated from the original cell. Refer to “Concentric cells” for more information.

Dual band standard cells

Refer to “Dual band cells” for more information on the migration of dual band standard cells. Refer to “Example for a dual band standard cell” for an example of a migrated dual band standard cell.

5.1.1

Example for standard cell

Migration steps:

1. Input (eBSC/BSC database text file)

First of two inputs requested by the offline migration tool for migration of the standard cell:

2. Further mapping info

Second of two inputs requested by the offline migration tool for migration of the standard cell: NAME BTSM:2/BTS:2 BSIC 5-3 CELLGLID "555"-"01"-10183-10188 CELLTYP STDCELL BCCHFREQ 4 CALLF01=34, CALLF02=44, CALLF03=104 SYSID BB900 CONCELL FALSE

REQUESTED INFO SOURCE WHERE EXPECTED COMMENT

<sourceObject mmlName="BTSM:2/BTS:2"> CONTROL FILE

(USED BY THE OFFLINE MIGRATION TOOL)

The values (i.e. the BTS num-bering) are picked up from the free instances numbers avail-able in the GEMINI network to migrate.

(51)

3. Output:

5.1.2

Example for dual band standard cell

Migration steps:

1. Input (eBSC/BSC1 database text file)

First of two inputs requested by the offline migration tool for migration of the standard cell:

REQUESTED INFO SOURCE WHERE EXPECTED COMMENT

<p name=" distNamePart">BTS-198</p> CONTROL FILE (USED BY THE OFFLINE MIGRATION TOOL)

The values (i.e. the BTS num-bering) are picked up from the free instances numbers avail-able in the GEMINI network to migrate.

<p name="segmentId">143</p> CONTROL FILE (USED BY THE OFFLINE MIGRATION TOOL)

The BSS segment.

<p name="segment-Name">3000BRCN02</p>

CONTROL FILE (USED BY THE OFFLINE MIGRATION TOOL)

Example considering the agreed solution C.

INFO SOURCE WHERE EXPECTED COMMENT

<managedObject class="BTS" version="S14" operation="create"

distName="PLMN-PLMN/BSC-33333/BCF-222/BTS-198">

NetAct script (common RAML format)

<p name="segmentId">143</p> NetAct script (common RAML format) <p name="">3000BRCN02</p> NetAct script (common RAML format)

BTS ID Added by BSC3i Assigned at creation.

cellNumber (HMO id) Built by Mediation on the BTS

side

Derived from SegmentName.

NAME BTSM:0/BTS:11 BSIC 5-3 CELLGLID "555"-"01"-10183-10182 CELLTYP DBSTDCELL BCCHFREQ 94 CALLF01=614, CALLF02=624, CALLF03=114, CALLF04=113, CALLF05=112 SYSID GSMDCS CONCELL FALSE

(52)

2. Further mapping info

Second of two inputs requested by the offline migration tool for migration of the standard cell:

3. Output:

If an eBSC/BSC1 BTS object has to be split into a pair of Flexi BSC BTS objects, all the segment level parameters (except the segmentId parameter) are allocated only for the first one. The complete list is grouped in the following table:

REQUESTED INFO SOURCE WHERE EXPECTED COMMENT

<sourceObject mmlName="BTSM:0/BTS:11"> CONTROL FILE (USED BY THE OFFLINE MIGRATION TOOL)

The values (i.e. the BTS num-bering) are picked up from the free instances numbers avail-able in the GEMINI network to migrate.

REQUESTED INFO SOURCE WHERE EXPECTED COMMENT

<p name=" distNamePart">BTS-199</p> <p name=" distNamePartAux">BTS-200</p>

CONTROL FILE (USED BY THE OFFLINE MIGRATION TOOL)

1) The first BTS of the new splitted pair (e.g. 199) is the BTS with the BCCH TRX band2) and HOC/PWRC must be consid-ered only associated to the 1st BTS of the pair.

<p name="segmentId">145</p> CONTROL FILE (USED BY THE OFFLINE MIGRATION TOOL)

The BSS segment

<p name="segment-Name">3000BRCN02</p>

CONTROL FILE (USED BY THE OFFLINE MIGRATION TOOL)

Example considering the agreed solution C.

INFO SOURCE WHERE EXPECTED COMMENT

<managedObject class="BTS" version="S14" operation="create"

distName="PLMN- PLMN/BSC-33333/BCF-222/BTS-199"><managedObject class="BTS" ver-sion="S14" operation="create" dist- Name="PLMN-PLMN/BSC-33333/BCF-222/BTS-200">

NetAct script (common RAML format)

<p name="segmentId">145</p> NetAct script (common RAML format) <p

name="segment-Name">3000BRCN11</p>

NetAct script (common RAML format)

BTS ID Added by BSC3i. Assigned at creation.

cellNumber (HMO id) Built by Mediation on the BTS

side.

(53)

5.2 Packet migration

The migration tool simply migrates the BTSM object to an equivalent BCF object, includ-ing the complete underlyinclud-ing hierarchy. This means that any kind of external required

1 bsIdentityCodeBCC 31 noOfBlocksForAccess-Grant 61 plmnPermitted 2 bsIdentityCodeNCC 32 noOfMFramesBetween-Paging 62 powerOffset

3 cellId 33 pcuCsHopping 63 qSearchI

4 directGPRSAccessBts 34 pcuCsNonHopping 64 radioLinkTimeout

4 egprsInitMcsAckMode 35 pcuDlBlerCpHopping 65 radioLinkTimeoutAmr

6 egprsInitMcsUnAckMode 36 pcuDlBlerCpNonHop 66 radioLinkTimeoutAmrHr

7 egprsLinkAdaptEnabled 37 pcuDlLaRiskLevel 67 rxLevAccessMin

8 egprsMaxBlerAckMode 38 pcuUlBlerCpHopping 68 smsCbUsed

9 egprsMaxBlerUnAckMode 39 pcuUlBlerCpNonHop 69 maxNumberRetransmission

10 egprsMeanBepOffset8psk 40 pcuUlLaRiskLevel 70 carrierUnitConfiguration

11 egprsMeanBepOffsetGmsk 41 qSearchP 71 timerPeriodicUpdateMs

12 gprsEnabled 42 rac 72 amhUpperLoadThreshold

13 gprsMsTxpwrMaxCCH 43 raReselectHysteresis 73 amhMaxLoadOfTgtCell

14 gprsMsTxPwrMaxCCH1x00 44 cellBarred 74 btsSpLoadDepTchRateLowe

15 gprsRxlevAccessMin 45 cellReselectHysteresis 75 btsSpLoadDepTchRateLower

16 hcsPriorityClass 46 cellReselectOffset 76 amrSegLoadDepTchRateLower

17 hcsThreshold 47 cellReselectParamInd 77 amrSegLoadDepTchRateUpper

18 initMcsExtAckMode 48 temporaryOffset 78 19 initMcsExtUnackMode 49 penaltyTime 79 20 interferenceAveragingPro-cessAverPeriod 50 callReestablishmentAl-lowed 80 21 locationAreaIdLAC 51 dtxMode 81 22 locationAreaIdMCC 52 earlySendingIndication 82 23 locationAreaIdMNC 53 emergencyCallRestricted 83 24 maxNumberOfRepetition 54 fddQMin 84 25 msMaxDistInCallSetup 55 fddQMinOffset 85 26 msTxPwrMaxCCH 56 fddQOffset 86 27 msTxPwrMaxCCH1x00 57 fddRscpMin 87 28 msTxPwrMaxGSM 58 allowIMSIAttachDetach 88 29 msTxPwrMaxGSM1x00 59 notAllowedAccessClasses 89 30 nbrOfSlotsSpreadTrans 60 multiBandCellReporting 90

(54)

managed objects (e.g. PCM resources, “NSVC” or “NSE” objects) have to be consid-ered independently and must be previously equipped in the network managed by the Flexi BSC. The BTSplus product line configuration is heavily dependent on this. More-over, the PTPPKF object is not a BR Abis managed object, and the main key features are implemented in the eBSC.

The EDAP configuration on the Abis interface connecting the BTSplus with the Flexi BSC requires information that cannot be provided by the packet configuration as described in the eBSC/BSC1 configuration script. Furthermore, the allocation of packet resources could demand more capacity on the new Abis interface.

Therefore, the migration tool implements a best-effort strategy. TCH timeslots are always preferred to packet timeslots. This means that the tool first attempts to migrate all the voice channels and to allocate them on the PCM line of the BSS Abis.

Then it starts the migration of packet timeslot, with the creation of the related EDAP pool, if the resources available are sufficient for the migration.In case there are no sufficient free subslots after the migration, the PS channels are mapped until resource exhausta-tion and the remaining PS channels are not mapped.

Remaining timeslots can then be used to manually add the EDAP configuration to the

RAML script. For this purpose, the exporter tool provides an inline list of all the idle timeslots for each LAPD, as shown in the example below.

In order to implement this strategy, the exporter tool first identifies the proper Abis PCM and LAPD primary positions and extracts the related equipped subslots. From this available pool of resources, it then starts to map each TRX, allocating two consecutive 64 kbit/s timeslots per TRX. In doing so, the LAPD timeslots used on the BR Abis are preserved. This means that some configurations can result in an LAPD timeslot breaking up a sequence of two consecutive 64 kbit/s timslots that could otherwise be allocated to a TRX. In such a case, the unused timeslots are lost.

The remaining (and consecutive) subslots can therefore be allocated to EDAPs.

g

The migration of real configurations can present an empty list of idle timelots. This

means that, in real cases, not all the timeslots of the TCH pool can be migrated. However, preprocessing activities done when still using the eBSC/BSC1 (e.g. reconfiguration and leasing of new PCM lines when capacity is not sufficient) are not within the scope of this document.

For general guidelines on dimensioning EDAPs on the Abis interface, refer to “Abis EDGE dimensioning”. For an example PCM allocation, refer to “Example PCM alloca-tion”.

<!-- Available PCM subslots (for EDAP) from BTSM:4/LPDLM:0 on PCM:445 : timeslot 3 - 1 1 1 1 from BTSM:4/LPDLM:1 on PCM:445 : timeslot 1 - 1 1 1 1 from BTSM:4/LPDLM:4 on PCM:445 : timeslot 2 - 1 1 1 1 -->

(55)

5.2.1

Example

The "firstTSL" and ="lastTSL" parameters are filled automatically by the tool, since these are respectively the first and the last free timeslot found by the tool.

The attribute "pcmCircuit_ID" is filled considering the PCM line id the TSs belong to. The parameters "bcsuID", "pcuID" and "psei" are not known to the Exporter Tool: "bcsuID", "pcuID" are set to fixed value 0 and "psei" is not filled at all.

After creating the DAP pool, the tool assigns the GPRS/EDGE TRXs by the TRX attri-bute DAP ID.

The GPRS/EDGE TRXs are identified checking first if the related BTS supports the GPRS/EDGE (attributes EGPRS and EEDGE of the object PTPPKF). Then it is checked if the TRX is associated to a layer supporting GPRS/EDGE services.

5.3 Frequency hopping

The exporter tool cannot have clear and unique criteria according to which it can decide whether to drop frequency hopping laws or not. Therefore, you have to reconfig-ure frequency hopping laws according to the guidelines described for other BTS types in the Nokia Siemens Networks GSM/EDGE BSS product line. Refer to “BSS7005: Fre-quency hopping” for more information.

Create EDAP Example from Real NetAct Configuration script

<managedObject class="DAP" version="S12" distName="PLMN-PLMN/BSC-205283/DAP-1" id="60881001"> <p name="bcsuID">2</p> <p name="firstTSL">25</p> <p name="lastTSL">26</p> <p name="pcmCircuit_ID">596</p> <p name="pcuID">3</p> <p name="psei">4</p> </managedObject>

Attribute Range Description

<p name="bcsuID"> 0-8 The BSCU associated to the PCU serving the DAP pool <p name="firstTSL"> 0-31 The 1st 64 Kbps-timeslot of the PCM

<p name="lastTSL"> 0-31 The last 64 Kbps-timeslot (of the consecutive series started at firstTSL ) of the PCM

<p name="pcmCircuit_ID"> 0-254 Identifier for the PCM (e.g. 2048 Kbps line for PCM30) <p name="pcuID"> 0-254 id for the PCU

<p name="psei"> 0-99 Packet Service Entity Identifier: This parameter identifies the PSE object in the BSC.

(56)

5.4 acDIMinCiRatioEst

Parameters related to enhanced quality of service (Eqos) are not supported.

5.5 adaptiveLaAlgorithm

Obj BTS

M,O,N,internal M

<p name=“adaptiveLaAlgorithm">Val</p>

Full name Adaptive LA Algorithm

Type Enumeration

Range Adaptive LA algorithm is enabled (Y) (0), Adaptive LA

algo-rithm is disabled (N) (1)

Internal value gui_value

Default Adaptive LA algorithm is enabled (Y) (0)

Description With this parameter the operator can define if the used GPRS

Link Adaptation algorithm is adaptive or not. 3GPP Multip 1 Modification Online Modified onCreate optional Val 0

(57)

5.6 adminState

Obj BTS

M,O,N,internal M

<p name=“adminState">Val</p>

Full name Administrative State

Type Enumeration

Range Unlocked (1), Locked (3)

Default Locked (3)

Description Administrative State of the object in the NW after object

creation or modification. 3GPP Multip 1 Modification Online Modified onCreate Optional Val 1

(58)

5.7 amrHoFrInHoThrDlRxQual

Obj BTS

M,O,N,internal mapped

<p name=“amrHoFrInHoThrDlRx-Qual">Val</p>

Full name Intra HO Threshold Rx Qual AMR FR

Type Enumeration

Range < 0.2% (0), 0.2% - 0.4% (1), 0.4% - 0.8% (2), 0.8% - 1.6% (3),

1.6% - 3.2% (4), 3.2% - 6.4% (5), 6.4% - 12.8% (6), > 12.8% (7)

Internal value gui_value

Default < 0.2% (0)

Description AMR Handover Intra Threshold Dl Rx Qual for Full Rate.

3GPP

Multip 1

Modification Online

Modified

onCreate optional

Val amrHoFrInHoThrDlRxQual is equal to the mean value of

HOTHCDL and HOTHCUL fields extracted from Handover Service Groups for AMR FR speech calls (Service Group-11, Service Group-12)

Exporter uses the value related to Service Group-11: if the parameters for Service Group-11 are not defined, it uses the Service Group-12 values.

In case both Handover Service Groups are not defined, the parameter is set equal to mean value of HOTHCDL and HOTHCUL (BR object HAND).

In case the BR value is not defined at all, amrHoFrInHoThrDl-RxQual is set equal to default(0).

refer to mapping Threshold Table: Table 3 - 0-20 BR range to 0-7 BSS range Threshold mapping

(59)

5.8 amrHoFrThrDlRxQual

Obj BTS

M,O,N,internal M

<p name=“amrHoFrThrDlRxQual">Val</p>

Full name Threshold Dl Rx Qual For AMR FR

Type Enumeration

Range < 0.2% (0), 0.2% - 0.4% (1), 0.4% - 0.8% (2), 0.8% - 1.6% (3),

1.6% - 3.2% (4), 3.2% - 6.4% (5), 6.4% - 12.8% (6), > 12.8% (7)

Internal value gui_value

Default 1.6% - 3.2% (4)

Description Amr Handover Dl Rx Qual for Full Rate.

3GPP

Multip 1

Modification Online

Modified

onCreate optional

Val Extract from Service Group, in case it is used

Handover Service Groups for AMR FR speech calls (Service Group-11, Service Group-12)

SGxxHOPAR(x=11..12

= <field 1>-<field 2>..<field 10>)

= HOLTHLVDL-HOLTHLVUL-HOTDLINT-HOTULINT-HORX-LVDLI-HORXLVDLO-HOLTHQUDL-HOLTHQUUL

-HOTHCDL-HOTHCUL

otherwise set it equal to HOLTHQUDL [0-20] otherwise set it equal to default.(4)

refer to mapping Threshold Table: Table 3 - 0-20 BR range to 0-7 BSS range Threshold mapping

(60)

5.9 amrHoFrThrUlRxQual

Obj BTS

M,O,N,internal M

<p name=“amrHoFrThrUlRxQual">Val</p>

Full name Threshold Ul Rx Qual AMR FR

Type Enumeration

Range < 0.2% (0), 0.2% - 0.4% (1), 0.4% - 0.8% (2), 0.8% - 1.6% (3),

1.6% - 3.2% (4), 3.2% - 6.4% (5), 6.4% - 12.8% (6), > 12.8% (7)

Internal value gui_value

Default 1.6% - 3.2% (4)

Description AMR Handover Threshold Ul Rx Qual for Full Rate.

3GPP

Multip 1

Modification Online

Modified

onCreate optional

Val Extract from Service Group, in case it is used

Handover Service Groups for AMR FR speech calls (Service Group-11, Service Group-12)

SGxxHOPAR(x=11..12) = <field 1>-<field 2>..<field 10>

= HOLTHLVDL-HOLTHLVUL-HOTDLINT-HOTULINT-HORX-LVDLI-HORXLVDLO-HOLTHQUDL-HOLTHQUUL

-HOTHCDL-HOTHCUL

otherwise set it equal to HOLTHQUUL [0-20] otherwise set it equal to default.(4)

refer to mapping Threshold Table: Table 3 - 0-20 BR range to 0-7 BSS range Threshold mapping

(61)

5.10 amrHoHrInHoThrDlRxQual

Obj BTS

M,O,N,internal mapped

<p name=“amrHoHrInHoThrDlRx-Qual">Val</p>

Full name AMR Handover HR Intra Threshold DL Rx Qual

Type Enumeration

Range < 0.2% (0), 0.2% - 0.4% (1), 0.4% - 0.8% (2), 0.8% - 1.6% (3),

1.6% - 3.2% (4), 3.2% - 6.4% (5), 6.4% - 12.8% (6), > 12.8% (7)

Internal value gui_value

Default 1.6% - 3.2% (4)

Description AMR Handover Intra Threshold Dl Rx Qual for Half Rate.

3GPP

Multip 1

Modification Online

Modified

onCreate optional

Val [HAND] HOTHDDL.

refer to mapping Threshold Table: Table 3 - 0-20 BR range to 0-7 BSS range Threshold mapping

(62)

5.11 amrHoHrThrDlRxQual

Obj BTS

M,O,N,internal M

<p name=“amrHoHrThrDlRxQual">Val</p>

Full name Threshold Dl Rx Qual AMR HR

Type Enumeration

Range < 0.2% (0), 0.2% - 0.4% (1), 0.4% - 0.8% (2), 0.8% - 1.6% (3),

1.6% - 3.2% (4), 3.2% - 6.4% (5), 6.4% - 12.8% (6), > 12.8% (7)

Internal value gui_value

Default 1.6% - 3.2% (4)

Description AMR Handover Threshold Dl Rx Qual for Half Rate.

3GPP

Multip 1

Modification Online

Modified

onCreate optional

Val Extract from Service Group, in case it is used

Handover Service Groups for AMR HR speech calls (Service Group-13, Service Group-14)

SGxxHOPAR(x=13..14) = <field 1>-<field 2>..<field 10>

= HOLTHLVDL-HOLTHLVUL-HOTDLINT-HOTULINT-HORX-LVDLI-HORXLVDLO-HOLTHQUDL-HOLTHQUUL

-HOTHDDL-HOTHDUL

otherwise set it equal to HOLTHQUDL [0-20] otherwise set it equal to default.(4)

refer to mapping Threshold Table: Table 3 - 0-20 BR range to 0-7 BSS range Threshold mapping

References

Related documents

Presence of such trends in field of international students mobility within Ukrainian universities indicates at two major problems: (1) existence of information gap among

In memory of Harold Taub, beloved husband of Paula Taub by: Karen &amp; Charles Rosen.. Honouring Maria Belenkova-Buford on her marriage by: Karen &amp;

In this study, the monthly Currency sale rates (DS) and Export (X) series are considered to investigate whether the X and DS series were affected by each other in the turning

Long years of service for the students practice job of the Faculty for Tou- rism and Business Logistics from University “Goce Delcev”-Shtip, Republic of North Macedonia (further

The table below provides a comparison of the cost per square foot for Menlo Park Fire District Station 2, located in East Palo Alto, bid and rebuilt starting in 2013, and Station

“Workforce Development Board” or “WDB” shall mean the Board established by the City as a non-profit, public benefit corporation and certified by the Governor of the State

Extensive experience in managing a team, handling direct clients, handling escalations, team building and placing qualified candidates on IT&amp; Non-IT projects