network reconfiguration recommendations ed30.pdf

78
Alcatel BSS Network Reconfiguration Recommendations BSS Document Reconfiguration Method Release B9 3BK 17422 0004 PCZZA Ed.30P02

Upload: vu-anh-tuan

Post on 30-Sep-2015

232 views

Category:

Documents


1 download

TRANSCRIPT

  • Alcatel BSS

    Network Reconfiguration

    Recommendations

    BSS Document

    Reconfiguration Method

    Release B9

    3BK 17422 0004 PCZZA Ed.30P02

  • Status IN PREPARATION

    Short title Network Reconfiguration Recommendations

    All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel/Evolium.

    BLANK PAGE BREAK

    2 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • Contents

    ContentsPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Network Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

    1.1 Network Modification Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2 Reverse Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3 Procedural Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

    1.3.1 Reporting Telecom Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.3.2 Ensuring Service Interface (V.11) (Qmux) Continuity . . . . . . . . . . . . . . . . . . . . . . . 141.3.3 Qmux Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.3.4 TCUC Overload Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.3.5 Mapping Improvements in B9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

    1.4 Choose Abis Transmission Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.4.1 Position of the Qmux Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.4.2 Abis Link Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

    1.5 Check for Sufficient Resources on Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.5.1 Display Time Slot Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.5.2 Check the Submultiplexing Scheme of the RSL/OML . . . . . . . . . . . . . . . . . . . . . . 211.5.3 Attempt to Add the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

    1.6 Activate New B9 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261.6.1 Abis Dynamic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261.6.2 M_EGCH Statistical Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261.6.3 Enhanced Transmission Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . 271.6.4 Counter Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.6.5 Electro Magnetic Environment (EME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281.6.6 Support of GPRS QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.6.7 Enhanced Packet Cell Reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.6.8 Extended UL TBF mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311.6.9 Autonomous Packet Resource Allocation (RAE4) . . . . . . . . . . . . . . . . . . . . . . . . . . 311.6.10 E-GSM: Support of GPRS and Signalling in G1 Band . . . . . . . . . . . . . . . . . . . . . . 321.6.11 Improved 2G 3G Cell Reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.6.12 Load Based 3G HO Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.6.13 2G-to-3G HO preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.6.14 Enhanced Support of EGPRS in Uplink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341.6.15 RMS Improvment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341.6.16 SNMP Manager in OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341.6.17 Unbalancing TRX Output Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

    2 Scenario Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.1 Add G1/G2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

    2.1.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.1.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

    2.2 Add Evolium A9110/A9110-E and A9100 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.2.1 A9110/A9110-E Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.2.2 A9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

    2.3 Delete G1/G2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.3.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.3.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

    2.4 Delete Evolium A9110/A9110-E and A9100 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412.4.1 A9110/A9110-E Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412.4.2 A9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

    2.5 G1/G2 BTS: Add TRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422.5.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422.5.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

    2.6 Evolium A9110/A9110-E and A9100 BTS: Add TRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422.6.1 A9110/A9110-E Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 3 / 78

  • Contents

    2.6.2 A9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422.7 G1/G2 BTS: Delete TRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

    2.7.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432.7.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

    2.8 Evolium A9110 /A9110-Eand A9100 BTS: Delete TRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432.8.1 A9110/A9110-E Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432.8.2 A9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

    2.9 Evolium A9110/A9110-E and A9100 BTS: Add Sector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442.9.1 A9110/A9110-E Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442.9.2 A9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

    2.10 Evolium A9110/A9110-E and A9100 BTS: Remove Sector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442.10.1 A9110/A9110-E Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442.10.2 A9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

    2.11 Evolium A9110/A9110-E BTS and A9100: Reconfigure BTS TREs/Sectors . . . . . . . . . . . . . 452.11.1 A9110/A9110-E Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452.11.2 A9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

    2.12 Evolium A9110/A9110-E and A9100 BTS: Create/Reconfigure Multi-band . . . . . . . . . . . . . . 462.12.1 A9110/A9110-E Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462.12.2 A9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

    2.13 Evolium A9100 BTS: Upgrade with New Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462.14 G2 and Evolium A9100 BTS: Synchronize BTS Site Master/Slave . . . . . . . . . . . . . . . . . . . . . . 46

    2.14.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462.14.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

    2.15 G2 and Evolium A9100 BTS: Desynchronize BTS Site Master/Slave . . . . . . . . . . . . . . . . . . . . 472.16 G1/G2 BTS: Replace BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

    2.16.1 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472.16.2 Master/Slave Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482.16.3 Shared Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

    2.17 Evolium A9110/A9110-E and A9100 BTS: Replace BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482.17.1 A9110/A9110-E Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482.17.2 A9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

    2.18 Abis: Move BTS/Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.18.1 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.18.2 Rule Specific to Move BTS within Same BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.18.3 Rules Specific to Move BTS from One BSC to Another . . . . . . . . . . . . . . . . . . . . . 51

    2.19 Add BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512.20 Add A9130 BSS Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522.21 A9120/A9130 BSC Evolution: Replace BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532.22 Move BSS: Different SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532.23 Move A9130 BSS Evolution: Different SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532.24 Introduce GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

    2.24.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542.24.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

    2.25 Delete GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552.25.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552.25.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

    2.26 Extend/Reduce or Modify GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562.26.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562.26.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

    2.27 Extend BSC and Ater-Mux Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572.28 Extend A9130 BSC and Ater-Mux Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582.29 Reduce BSC and Ater-Mux Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582.30 Add/Delete PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

    2.30.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592.30.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

    2.31 Move Ater PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602.31.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

    4 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • Contents

    2.31.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602.32 Add/Delete GPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

    2.32.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612.32.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

    2.33 Add/Delete GP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622.33.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622.33.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

    2.34 Move BSS, Same OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632.34.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632.34.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

    2.35 Move A9130 BSS Evolution, Same OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.35.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.35.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

    2.36 Move BSS, Different OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662.36.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662.36.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

    2.37 Move A9130 BSS Evolution, Different OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672.37.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672.37.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

    2.38 Move BSS, Different A9125 TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692.39 Move A9130 BSS Evolution, Different A9125 TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692.40 Merge TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692.41 Activate Ater Satellite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

    2.41.1 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702.41.2 Satellite Link Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

    2.42 Deactivate Ater Satellite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702.43 Activate Abis Satellite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

    2.43.1 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702.43.2 Satellite Link Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

    2.44 Abis Satellite De-Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702.45 X.25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712.46 IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712.47 Modify Logical Parameters Using MLU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722.48 Introduce LCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732.49 Delete LCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732.50 Introduce E-GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732.51 Deactivate E-GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732.52 Attach Secondary Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732.53 Detach Secondary Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

    3 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.1 Personnel Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 5 / 78

  • Contents

    6 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • Preface

    PrefacePurpose This Network Reconfiguration Recommendations document presents overview

    information and guidelines for persons who carry out network modificationtasks.

    Whats New In Edition 30Improvements due to system evolution.

    In Edition 07Edition created for introduction of A9130 BSC Evolution in B9.Restriction regarding NACC feature activation was removed from NACC(Section 1.6.7.2 )Improvements in Unbalancing TRX Output Power (Section 1.6.17)Update of section Abis Link Capacity (Section 1.4.2) for A9130 BSC Evolution.Update of the method due to new equipment impact in the following sections:

    Editorial update of section Introduce E-GPRS (Section 2.50).Add A9130 BSS Evolution (Section 2.20)A9120/A9130 BSC Evolution: Replace BSC (Section 2.21)Move A9130 BSS Evolution: Different SGSN (Section 2.23)Introduce GPRS (Section 2.24)Delete GPRS (Section 2.25)Extend/Reduce or Modify GPRS (Section 2.26)Extend A9130 BSC and Ater-Mux Interface (Section 2.28)

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 7 / 78

  • Preface

    Add/Delete PCM (Section 2.30)Move Ater PCM (Section 2.31)Add/Delete GPU (Section 2.32)Add/Delete GP (Section 2.33)Move BSS, Same OMC-R (Section 2.34)Move A9130 BSS Evolution, Same OMC-R (Section 2.35)Move BSS, Different OMC-R (Section 2.36)Move A9130 BSS Evolution, Different OMC-R (Section 2.37)Move A9130 BSS Evolution, Different A9125 TC (Section 2.39)IP (Section 2.46)

    In Edition 05Restriction regarding NACC feature activation was inserted in NACC (Section1.6.7.2 )

    In Edition 04Overall document quality was improved following an editorial review in NetworkModifications (Section 1).

    In Edition 03Restriction on LCS introduced in Abis: Move BTS/Abis (Section 2.18), MoveBSS, Different A9125 TC (Section 2.38), Move A9130 BSS Evolution, DifferentA9125 TC (Section 2.39).

    In Edition 02Update due to "Abis Dynamic Allocation" feature in Abis Dynamic (Section1.6.1)Update due to "M_EGCH Statistical Multiplexing" feature in M_EGCH StatisticalMultiplexing (Section 1.6.2)Update for "Electro Magnetic Environment (EME)" in Electro MagneticEnvironment (EME) (Section 1.6.5)Update for "Support of GPRS QoS" in Support of GPRS QoS (Section 1.6.6)Update due to "Cell Ranking With Load Criteria" in NC2 Improvement: CellRanking With Load Criteria (Section 1.6.7.1 )Update due to "NACC" feature in NACC (Section 1.6.7.2 )Update due to feature "Packet (P)SI Status" in Packet (P)SI status (Section1.6.7.3 )Update due to feature "Extended UL TBF Mode" in Extended UL TBF mode(Section 1.6.8)Update due to feature "Autonomous Packet Resource Allocation (RAE4)" inAutonomous Packet Resource Allocation (RAE4) (Section 1.6.9)Update due to feature "Support of GPRS and Signalling in G1 Band (E-GSM)"in E-GSM: Support of GPRS and Signalling in G1 Band (Section 1.6.10)

    8 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • Preface

    Update due to feature "Improved 2G 3G Cell Reselection" in Improved 2G 3GCell Reselection (Section 1.6.11)Update due to feature "Load Based 3G HO Filtering" in Load Based 3G HOFiltering (Section 1.6.12)Update due to feature "Enhanced Support of EGPRS in Uplink" in EnhancedSupport of EGPRS in Uplink (Section 1.6.14)Update due to feature "SNMP Manager in OMC" in SNMP Manager in OMC(Section 1.6.16)

    In Edition 01Update due to TRX/RSL mapping improvement in Mapping Improvements inB9 (Section 1.3.5)Update due to TRE/TCU mapping improvement in Mapping Improvements inB9 (Section 1.3.5)

    Audience This manual is intended for:

    Network Modification Planners

    Operations and Maintenance technicians and systems designers

    Operators who are responsible for carrying out the following O&M functionson assigned BSSs:

    ConfigurationPerformanceFault Management.

    Assumed Knowledge You must have a basic understanding of the following:

    The operation of a Mobile Telecommunications Network

    Alcatel O&M concepts for the BSS, as described in Operations andMaintenance Principles

    The organization of the telecommunications network you are responsiblefor operating.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 9 / 78

  • Preface

    10 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 1 Network Modifications

    1 Network Modifications

    This section provides:

    An overview of the network modification process

    An overview of the reverse procedure

    Procedural guidelines

    Choosing Abis Transmission Settings

    Evolium Network Configuration Hints

    Checking for Sufficient Resources on Abis

    New B9 Features Activation.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 11 / 78

  • 1 Network Modifications

    1.1 Network Modification ProcessThe following figure describes the five major steps to modify the network.

    Note: Step 2 and step 3 can also be performed in reverse order. The HardwareModification step can also be performed after the Activation step.

    1. Start Process

    Perform initial checks on your system, such as alarm state audits. Create a PRC touse as a backup, filling it with the network elements you are going to modify. Do notperform any modifications on this PRC. Close the PRC. Use it in case you mustreturn to the initial state of your system before the modification.

    2. Logical Configuration

    Create and open another PRC which you modify.

    3. Hardware Modification

    Make any necessary hardware modifications.

    4. Activation

    Activate the modified PRC for the changes to be propagated and activated in thenetwork.

    5. End Process

    Perform final checks on your system, making sure that traffic is established on the modified part of the network.

    Figure 1: Network Modification Process

    12 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 1 Network Modifications

    1.2 Reverse Procedure

    In case of problems detected during a scenario, the time interval neededto detect and correct the fault must take into account the necessary timeto reach a stable position.

    The investigations must be led with the support of the manufacturer"s supporttechnicians who must be called a maximum of 30 minutes after the faultdetection. In all cases the rollback decision or the investigation continuationdecision responsibility belongs to the customer, but the manufacturer mustsupply all the elements necessary to take this decision.The customer must inform the manufacturer of the effective hour to reach astable state (for example: 6 AM).The manufacturer must inform the customer of:

    The presence of a problem with its gravity and impact

    The first results of investigations

    The time necessary to reach a stable state after fault correction

    The time interval needed for the rollback procedure.

    The following figure describes the three major steps involved in a reverseprocedure.

    Note: Step 1 and step 2 can also be performed in reverse order, or in parallel.

    1. Hardware Modification

    Return hardware to its previous state.

    2. Activate Backup PRC

    Activate the PRC you made before you started your modifications.

    3. End Process

    Perform final checks on your system, making sure that traffic is reestablishedon the modified part of the network.

    Figure 2: Reverse Procedure

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 13 / 78

  • 1 Network Modifications

    1.3 Procedural GuidelinesThis section provides guidelines on several important aspects of networkmodification:

    Reporting telecom impact

    Ensuring Service Interface (V.11) (Qmux) continuityQmux addressing.

    1.3.1 Reporting Telecom ImpactSome network modification procedures have a telecom impact on the system(traffic lost or reduced). In these cases, operators must warn all the areasof their organization that could be affected by this operation, for example:Supervision, Operations and Maintenance, Customer Care, Quality, etc.

    1.3.2 Ensuring Service Interface (V.11) (Qmux) ContinuityFor some procedures (e.g. adding a BTS to an existing Abis link), several BIEof the BTS on the Abis link must be reprogrammed. In these cases, Qmux buscontinuity and unique addressing must be guaranteed across the network.If these Qmux conditions are not respected, site access to the BTS ismandatory each time the network is reconfigured.

    1.3.3 Qmux AddressingThe OMC-R operator controls the Qmux address. For an existing BSS, theQmux address entered at the OMC-R must match the address installed inthe equipment.At migration, the Qmux address known in the BTS might not always be in linewith the Qmux address known in the BSC. The Qmux address known in theBTS is automatically set (by OML auto-detection) to the BSC address.For new BTSs, the OMC-R operator must allocate a unique Qmux addressfor each BTS.If Qmux address is unique at network level, Qmux address can be kept whenmoving BTS from one BSC to another. Otherwise, it is necessary to changethe Qmux address.

    14 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 1 Network Modifications

    1.3.4 TCUC Overload HandlingTCUCs are BSC processors in charge of handling the TRX/TRE of the BTS.Their load depends greatly on the channels that they have to handle and on thetraffic carried by these channels (for example, whether a cell is at a locationarea border or not).A TCUC can manage up to two dual-rate TRX/TRE, or up to four full-rateTRX/TRE. All TRE/TRX for which the RSL are multiplexed together aremanaged by the same TCUC.The mapping of TRX/TRE is influenced by two types of processes:

    Hardware configuration processThis process allocates TRE/RSL (Frame Unit/Carrier Unit) to the TCUC.To perform this allocation, the following parameters are taken into account:

    Full-rate/dual-rate TREMultiplexing scheme (no multiplexing, static, statistical 64k, statistical16k)Signaling load: high/low (applicable for statistical 64k submultiplexing, tolimit multiplexing up to two full-rate TRX/TRE or one dual-rate TRX/TRE)Multiplexing per BTS or per sector.

    Mapping of TRX to TREThis process maps the TRX (logical channels) on the available TRE. Themain constraint is to map TRX on TRE of the same frequency band.

    The mapping of TRX/TRE to TCU is triggered by a number of circumstances:

    Extensions

    Modification of logical configurations

    Failure recovery

    Reshuffling.

    Most of the processes tend to spread the load, i.e. spread TRX handlingSDCCH. However, in the case of partial evolution of the configuration(e.g. modification of one TRX), to avoid releasing calls no action isperformed to spread the load. This may lead to overload situations forthe TCUC. In this case, the BSC sends the following alarm "ProcessorAlarm[33];SDCCH-OVRL-BSC[9]" (begin/end alarm). The operator can seeoverload TCUC alarms by looking at the TCU_Load_Report window. For eachTCUC in overload situation (the alarm begin has been received), the OMC-Rdisplays the corresponding alarm identifier.The following sections provides some actions and some configuration rules thatthe operator can follow to either prevent, or correct overload situations.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 15 / 78

  • 1 Network Modifications

    1.3.4.1 Preventive Actions

    In Hardware

    Configuration Area

    Beginning with release B7, the BSS supports cells shared by two BTS. EachBTS can be connected to any TSU of the BSC. If the shared cell is a multi-bandcell, all SDCCH are concentrated on only one BTS (e.g. the 900 one) and theother BTS does not support any SDCCH. Grouping all the 900 BTS on the sameTSU will lead to an accumulation of SDCCH on the same subset of processors.It is recommended to mix BTS 900 and BTS 1800 on the same TSU.

    In Logical Configuration

    Area

    When defining the channels of the TRX, the operator should always spreadthe SDCCH as much as possible.

    1.3.4.2 Corrective ActionsThere are a number of possible actions, which are more or less efficientdepending on the configuration.

    Remap Logical

    Channels (RNUSM - TRX

    Management)

    This facility reconsiders the complete mapping of TRX/TRE for a certain cell.It does not modify the used TCUC; it only remaps the logical channels onthese TCUC.This is:

    Efficient for mono-band cells mapped on several TCU

    Efficient for multi-band cells if the TRE of the outer band are carriedby several TCUC

    Not efficient if all the TRX manage the same number of SDCCH.

    RSL Remapping

    - Balanced Load

    (BSSUSM)

    From release B8 the Extra Abis time slots concept must be considered whenperforming an RSL remapping. The BSC tries to free/find space on TCUs bymoving the Extra time slots of the BTS declared on that TSU. This may leadto telecom outage.The operator has a choice of three levels of remapping:

    Compact RSL/TCU remapping

    Balanced load (with possible impact on other TCU)Balanced load (with no impact on other TCU).

    This facility spreads the TRE (and their attached TRX) on the TCU (hardwareconfiguration action).It is not efficient when RSL are multiplexed together by groups of four:

    BTS with more than four TRE

    Static multiplexing

    Statistical multiplexing with low signaling load

    Multiplexing per BTS.

    16 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 1 Network Modifications

    Modify Multiplexing

    Conditions

    This is a prerequisite for an efficient flat hot spot. Note, however, that thisaction increases the Abis occupancy and so may be refused due to lackof time slots on the Abis.Several modifications are possible, for example:

    Go to statistical multiplexing, with a high signaling load

    Statistical multiplexing, with multiplexing per sector (this is not recommendedif the number of TRE per sector is three or seven).

    Note: The above hints do not cover temporary degraded situations due to hardwarefailures. In these situations, the first action to be performed is a repair.Installing dual-rate TRE has a positive effect on the SDCCH load, because itleads to using more TCUC but it is not considered as a way to solve theoverload situation.

    1.3.5 Mapping Improvements in B91.3.5.1 TRX/RSL Mapping Improvement

    Beginning with B9, when mapping TRX to RSL, the RSL speech rate istaken into account. The functional requirement is to map in priority TRXwith signaling on FR TRE.In order to handle both the speech rate and the load constraints, the algorithmallocates TRX with SDCCH in the following order:

    Allocation is done in priority on FR TCU below the limit of 32 SDCCHper TCU.

    When all FR TCU have reached this threshold, the allocation is done on theTCU with the lowest signaling load (BCCH, static and dynamic SDCCH).The allocation is done in second priority on the DR TCU until the signalingload is well-balanced between DR and FR TCU. The allocation is done onany DR or FR TCU by keeping as much as possible a good balancingbetween all TCU.

    1.3.5.2 TRE/TCU Mapping ImprovementA new B9 improvement brings to an optimal use the available TCU resourcesin terms of TRE connectivity/capacity, but it does not impact internal orexternal messages:

    For BTS configuration change, the flag "Reshuffling allowed" allows or notthe BSC to find a more efficient RSL/TCU mapping and to use it includingthe case of TRE extension

    Compact RSL/TCU re-mapping efficiency.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 17 / 78

  • 1 Network Modifications

    1.4 Choose Abis Transmission SettingsUse the following sections to choose the Abis transmission settings:

    Position of the Qmux Bus

    Abis Link Capacity.

    1.4.1 Position of the Qmux BusFor Evolium BTS, the transmission configuration is managed using the OMLlink.For G2 and G1 BTS, the transmission configuration via Qmux is mandatory.For this, free mapping of the Qmux bus is used, which means the Qmux buscan use any time slot. Moving the position of the Qmux bus in the Abis frameimplies an on-site reconfiguration of the BIE module.

    1.4.2 Abis Link CapacityWhen no multplexing apply, there is:

    One OML per BTS which takes one 64 kbit/s time slot

    One RSL per TRE which takes one 64 kbit/s time slot

    Eight TCHs for each TRE, using two contiguous time slots fornon-A9100/A9110/A9110-E BTS. A9100/A9110/A9110-E BTS also use twotime slots, but they do not have to be contiguous.

    The capacity of an Abis link, in terms of the number of BTS and the numberof TRE depends on:

    The multiplexing of control channels

    The type full-rate/dual-rate of the TRE.

    Following possibilities for Abis multiplexing apply:

    Static multiplexing

    Statistical submultiplexing (64 kbit/s)Statistical submultiplexing (16 kbit/s).

    To modify the submultiplexing, use Modify OML and RSL Submultiplexing.

    18 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 1 Network Modifications

    1.4.2.1 Static MultiplexingStatic multiplexing enables you to multiplex up to four RSL channels of the sameBTS on one single time slot of the Abis frame. It allocates 16 kbit/s per RSL.It is supported by the following hardware:

    A9120 BSC, A9130 BSC Evolution

    G2 BTS with Dual Rate Frame Unit (DRFU), A9100/A9110 BTS.

    1.4.2.2 Statistical Submultiplexing (64 kbit/s)This enables you to multiplex one OML and up to four RSL of the same BTSonto a single 64 kbit/s Abis time slot. It dynamically allocates the bandwidthamong the RSLs. RSLs with more traffic get more bandwidth (up to thecomplete 64 kbit/s) than RSLs with less traffic. If dual rate TREs are defined,only two RSL will be multiplexed together with one OML on the same Abistime slot.

    1.4.2.3 Statistical Submultiplexing (16 kbit/s)This enables you to multiplex one OML and one RSL of the same BTS into asingle 16 kbit/s time slot nibble (in time slot 0 of a TRX) available on theAbis in full-rate mode. Statistical Submultiplexing (16 kbit/s) can be used forsmall capacity BTS.

    Note: Intermediate transmission networks can be used on the Abis Interface -External Submultiplexers. These can cause some specific constraints, suchas difficulty in reconfiguring the 64 kbit/s cross-connects.The following table describes the number of time slots available in one Abis linkfor use by the TCH and control channels.

    By QmuxSupervision

    Time Slot 0Transparency(not used byQmux)

    Time Slot 0 Use(used by Qmux)

    By OML

    Chain 30 31 31

    Ring 29 30 29

    Table 1: Abis Link Capacity

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 19 / 78

  • 1 Network Modifications

    The following table describes the number of time slots needed per number ofTRX for each type of submultiplexing in one Abis link.

    Number of Time Slots NeededNo. of TRX

    No Multiplexing Static Multiplexing StatisticalSubmultiplexing(64 kbit/s)

    StatisticalSubmultiplexing(16 kbit/s)

    1 4 4 3 2

    2 7 6 5 4

    3 10 8 8 6

    4 13 10 9 8

    5 16 13 12 10

    6 19 15 14 12

    7 22 17 17 14

    8 25 19 18 16

    9 28 22 21 18

    10 31 24 23 20

    11 Not possible 26 26 22

    12 Not possible 28 27 24

    13 Not possible Not possible 30 26

    14 Not possible Not possible Not possible 28

    15 Not possible Not possible Not possible 30

    Table 2: Time Slots Needed Per Number of TRX for Each Type of Submultiplexing

    20 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 1 Network Modifications

    1.5 Check for Sufficient Resources on AbisSufficient resources must exist on the Abis links when you perform a networkmodification. For example when you add a BTS, you must have enough freetime slots for the TCHs, RSLs, OML and extra Abis TS.To find out if sufficient resources exist, you can:

    Display time slot allocation

    Check the submultiplexing scheme of the RSL

    Attempt to add the BTS.

    1.5.1 Display Time Slot AllocationTo find free time slots on the Abis, use Display Abis Time Slot Allocation andnote down which time slots are not being used.

    1.5.2 Check the Submultiplexing Scheme of the RSL/OMLThe amount of resources that the signaling links use depends on whethermultiplexing (static or statistical) is used. The following table describes thenumber of RSL/OML per time slot:

    Type of Multiplexing OML perTime Slot

    RSL per TimeSlot

    One Time SlotShared BetweenOML & RSLs

    TRX-Time Slot 0bits 1-2 used (noother Time Slotneeded for RSL,OML)

    No Multiplexing 1 1 - -

    Static Multiplexing(Dual-rate not allowed)

    1 4 (16 kbit/s perRSL)

    - -

    Statistical Submultiplexing(64 kbit/s)

    - - 1 OML+ 1 RSL1 OML+ 2 RSL1 OML+ 4 RSL

    -

    Statistical Submultiplexing(16 kbit/s) (Dual-rate notallowed)

    - - - 1RSL+ 1 OML,both at 16 kbit/s atTRX-Time Slot 0 bits1-2

    Table 3: Number of RSL/OML per Time Slot

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 21 / 78

  • 1 Network Modifications

    1.5.3 Attempt to Add the BTSAttempt to add the BTS, using the scenario Add BTS, New Cell(s) .In case of a secondary Abis:

    The allocation for OML, RSL and basic time slots is done only on the firstAbis in limit of the available space

    MAX_EXTRA_TS_PRIMARY seting is taken into account only if the BTShas a secondary Abis link

    Extra Abis time slots allocation is done on the primary Abis, ifMAX_EXTRA_TS_PRIMARY>0, after allocating all the signaling linksand basic time slots. If the secondary Abis is present, only Extra Abistime slots can be allocated on it.

    In example, when MAX_EXTRA_TS_PRIMARY set to 6 you will have thefollowing allocation:

    graphics/tsallocation1.gif

    If MAX_EXTRA_TS_PRIMARY is set to 31, the primary Abis will be filledcompletely:

    graphics/tsallocation2.gif

    If MAX_EXTRA_TS_PRIMARY is set to 0, the primary Abis and the first TSUis preserved for future extension:

    graphics/tsallocation3.gif

    22 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 1 Network Modifications

    For defining the full-rate TCU occupancy the Eq-FR (equivalent full-rate) isused.For computing the needed Eq-FR for add BTS operation, the operator shalltake into account the following:

    1 TCU supports 4 Eq-FR

    1 TCU supports 2 Eq-DR

    1 Extra Abis time slot = 0.5 Eq-FR

    Extra Abis time slots are mapped only on TCUs supporting TRE full-rateand not on TCUs supporting dual-rate TRE

    Full-rate and dual-rate TREs cannot be combined on the same TCU.

    For correctly adding a BTS on the Abis the operator should check first:

    If the number of available Eq-FR on TSU allows him to add the BTS

    Number of Eq-FR needed for the operation

    Number of resources on primary and secondary Abis links.

    For TSU connectivity the following must be taken into account:

    1 dual-rate TRX is equivalent to 2 full-rate TRX

    One extra Abis TS used for PS traffic is equivalent with 0.5 full-rate TRX.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 23 / 78

  • 1 Network Modifications

    If during the scenario no error messages are displayed, the BTS is successfullyadded. If not, follow the solutions in the table to solve the resource problems onthe Abis.

    When... The following error messageappears:

    Perform the following...

    There is lack of TSUspace for RSL, OMLand TCH

    Lack of primary TSU Eq-FRfor RSL,OML and TCH:requested: xxx, available:yyy or Lack of primary TSUEq-FR for Extra Abis TS:requested: xxx, available:yyy, where:

    xxx is the number of Eq-FRneeded for TCH/Extra Abistime slots for this TCU

    yyy is the is the Eq-FR beforethe command for this TSU.

    Reshuffle TSU using Remap RSLRSL remapping is possible at three levels:

    Compact RSL/TCU remapping

    Balanced load (with possible impact onother TCU

    Balanced load (with no impact on otherTCU).

    There is lack of TSUspace for Extra Abistime slots on thesecondary TSU

    Lack of secondary TSUspace: requested Eq-FR:xxx, available Eq-FR: yyy,where:

    xxx is the number of Eq-FRneeded for TCH/Extra Abistime slots for this TCU

    yyy is the is the Eq-FR beforethe command for this TSU.

    Reshuffle TSU using Remap RSLRSL remapping is possible at three levels:

    Compact RSL/TCU remapping

    Balanced load (with possible impact onother TCU

    Balanced load (with no impact on otherTCU).

    24 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 1 Network Modifications

    When... The following error messageappears:

    Perform the following...

    There is no space onAbis for RSL, OML andbasic time slots

    Lack of Abis TS for RSL,OML and TCH: Requested xxx,available: yyy, where:

    xxx is the total number of timeslots required to be allocatedfor RSL, OML and TCH

    yyy is the number of freeuseable time slots before theexecution of this command .

    Defragment Abis Chain/RingFill-Up Primary Abis Chain in case the BTSmust be declared on the secondary Abisof abnother BTS.Delete Extra time slots (pools) or TREIncrease/DecreaseMAX_EXTRA_TS_PRIMARY.

    There is lack of spacefor Extra Abis time slots

    Lack of Abis TS for ExtraAbis TS: requested: xx,available (1st/2nd Abis):yy/zz, where:

    xx is the total number oftimeslots required to beallocated for Extra Abis timeslots

    yy/zz is the number offree useable time slots onprimary/secondary Abis for thisBTS, after the execution of theRSL, OML and TCH mapping.MAX_EXTRA_TS_PRIMARYis not taken into account forthis computation.

    Defragment Abis Chain/RingFill-Up Primary Abis ChainDelete Extra time slots (pools) or TREIncrease/DecreaseMAX_EXTRA_TS_PRIMARY

    Table 4: Error Messages for Add BTS

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 25 / 78

  • 1 Network Modifications

    1.6 Activate New B9 FeaturesMechanismsFeature activation is the last step of the migration of an ALCATEL BSS.The parameters concerning the B9 features activation will be set via twodifferent modes:

    With a PRC activated in Message Mode for modifying BSC parameters

    With a PRC activated in Massive Logical Update, for activation of a globalfeature. MLU activation mode is only applicable on cell parameters

    Some features require hardware modifications to work properly.

    1.6.1 Abis DynamicThis feature is an internal system improvement. There is no specific operatoractivation.The transition from B8 HSDS to B9 HSDS with Dynamic Abis is managed bysome specific actions in the migration steps.Main O&M impacts brought by the Dynamic Abis allocation feature compared tothe HSDS feature in B8 from migration or user point of view:

    The number of extra Abis timeslots is defined per BTS. It replaces the B8notion of TRX pool type

    To simplify the rules to share basic nibbles inside a given cell, a new B9O&M constraint is introduced which guarantees that "in a cell shared overtwo BTSs, only one sector can support PS traffic"

    In B9, the pool of Extra TSs of the BTS can have the following states:"available", "unavailable" (default case when no Extra TSs configured forBTS, or when all Extra TSs are broken), "partly available" (when someExtra TSs are broken, and others not). That state is got by OMC throughthe HSDS-Synthesis view. Those states replace the B8 states "available","truncated", "unavailable", (B8 states per TRX pool). As those informationare nor persistent in the OMC and displayed by means of BSC get, there isno need to migrate this pools status information

    New cell to GPU mapping algorithm that leads to New reshuffling situationsin the MFS

    Due to the better usage of Abis resources, depending on the load of the packettraffic, the operator would be able to reduce the number of Extra TSs.

    1.6.2 M_EGCH Statistical MultiplexingNo new logical parameters are necessary for this feature that cannot beactivated.

    26 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 1 Network Modifications

    1.6.3 Enhanced Transmission Resource Management"Enhanced transmission resource management" is a feature that cannotbe activated.This feature is a system internal improvement. There is no specific operatoractivation.Impacted Parameters

    BSS Parameters Cell Parameters

    T_GCH_Inactivity GCH_THRESHOLD_EGPRS

    T_GCH_Inactivity_Last GCH_THRESHOLD_GPRS

    Impacted parameters can be tuned from both PRC and SC.

    1.6.4 Counter Improvements"Counter improvements" is a feature that cannot be activated.This feature is a system internal improvement. There is no specific operatoractivation.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 27 / 78

  • 1 Network Modifications

    1.6.5 Electro Magnetic Environment (EME)EME feature is activated/deactivated when the operator adds/removes theEME type (type 33) in a/from the standard PMC list.Parameters linked to the feature are specific to the cell. They shall be tuned toallow the use of the feature when activated.The associated parameters do not impact the measurement. They arethresholds used by RNO to monitor the emitted powers per cell. In case thosethresholds are exceeded, RNO includes those cells in a report.These parameters can be manually initialized by the user from both PRCand SC or via a Java script.Impacted Cell Parameters

    EME_PWR_MAX_GSM

    EME_PWR_MAX_DCS

    Activation ScenarioThe feature is activated when the Type 33 is added in the permanent campaign.As a permanent campaign is defined for a complete OMC, EME will be runningin all B9 cells defined in the OMC. The following scenario considers alsothe tuning of the parameter EME_PWR_MAX_GSM/DCS using the EMEjava-script facility on a set of cells on which the operator can choose thesame coefficient as input of the script.

    In the PRC, for cell parameters modificationSelect the set of cells on which the EME script has to be launchedwith the same coefficientApply the Java script on the selected cells.

    PM ActivationAdd the Type 33 in the PMC.

    28 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 1 Network Modifications

    1.6.6 Support of GPRS QoS"Support of GPRS QoS parameters" is a feature that can be activated, and ismanaged via the EN_PFC_FEATURE parameter. Additionally, the sub feature"Support of streaming flow" is managed via the EN_STREAMING parameter.Rules: RMIN_GMSK

  • 1 Network Modifications

    1.6.7 Enhanced Packet Cell Reselection1.6.7.1 NC2 Improvement: Cell Ranking With Load Criteria

    "NC2 improvement: Cell ranking with load criteria" is a feature that can beactivated, and is managed through the THR_NC2_LOAD_RANKING parameter.All parameters can be modified from both PRC and SC.

    Impacted Cell ParametersTHR_NC2_LOAD_RANKING

    Activation scenarioSet cell parameters, using Edit n cells . (THR_NC2_LOAD_RANKINGset to "1")

    1.6.7.2 NACC

    This feature is blocked at OMC in case of satellite used on Abis or on Ater.

    "NACC" features is a feature that can be activated, and is managed throughthe, EN_NACC parameter.All parameters can be modified from both PRC and SC.Rules:

    The cell is mapped on Evolium BTSs

    ROUND_TRIP_DELAY < 500 msec (i.e. terrestrial links)

    Impacted Cell ParametersEN_NACC

    Activation scenarioSet cell parameters, using Edit n cells . (EN_NACC set to true)

    1.6.7.3 Packet (P)SI statusThis feature is blocked at OMC in case of satellite used on Abis or on Ater.

    "Packet (P)SI status" feature is a feature that can be activated, and is managedthrough the EN_PSI_STATUS parameter.All parameters can be modified from both PRC and SC.Rules:

    The cell is mapped on Evolium BTSs

    ROUND_TRIP_DELAY < 500 msec (i.e. terrestrial links)

    Impacted Cell ParametersEN_PSI_STATUS

    Activation scenarioSet cell parameters, using Edit n cells . (EN_PSI_STATUS set to true)

    30 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 1 Network Modifications

    1.6.8 Extended UL TBF modeExtended UL TBF mode is a feature that can be activated, and is managed viathe EN_EXTENDED_UL_TBF parameter.All parameters can be modified from both PRC and SC.Rules:

    T3192 + T_MAX_EXTENDED_UL + ROUND_TRIP_DELAY< 5 s

    Due to the fact that for T3192 and ROUND_TRIP_DELAY the OMC usesdifferent coding rules than those given in the BSS Telecom Paramaters,special attention must be payed when checking the above rule, as all theinvolved values must be expressed in the same measurement unit

    EN_ EXTENDED_UL_TBF can be set to true for a cell mapped upon anon Evolium BTSs

    Impacted Parameters

    BSS Parameters Cell Parameters

    EN_FAST_USF_UL_EXTENDED T_MAX_EXTENDED_UL

    EN_RA_CAP_UPDATE EN_EXTENDED_UL_TBF

    Activation scenarioSet cell parameters, using Edit n cells . (EN_EXTENDED_UL_TBF set totrue)

    1.6.9 Autonomous Packet Resource Allocation (RAE4)Autonomous packet resource allocation is a feature that cannot be activated.This feature is a system internal improvement.There is no specific operator activation.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 31 / 78

  • 1 Network Modifications

    1.6.10 E-GSM: Support of GPRS and Signalling in G1 Band"E-GSM: support of GPRS and signaling in G1 band" can be activated in themeaning that the radio configuration of a cell using G1 frequencies can bemodified to take benefits of the feature.The parameter EGSM_RR_Alloc_Strategy defines the radio resource allocationstrategy used in E-GSM cells. Two allocation strategies can be applied in thesystem depending on the value of the parameter that is:

    EGSM_RR_Alloc_Strategy = 0 means that not all GSM900 mobile stationsin the network are assumed to be E-GSM capable. G1 and PGSM TRXare not managed by the same way

    EGSM_RR_Alloc_Strategy = 1 means that all GSM900 mobile stations inthe network are assumed to be E-GSM capable. No difference madebetween a G1 TRX and a PGSM TRX.

    The parameter EGSM_RR_Alloc_Strategy is defined in the BSC CDE table,and has to be set at migration time.

    1.6.10.1 Activation in Case of EGSM_RR_Alloc_Strategy=0GPRS can be used on G1 TRX.

    Impacted TRX ParametersTRX_PREFERENCE_MARK

    Activation scenarioFor a selected E-GSM cell, set TRX parameters (TPM=0) on G1 TRX

    1.6.10.2 Activation in Case of EGSM_RR_Alloc_Strategy=1In a cell already defined with frequency band E-GSM, the operator can:

    mix G1 and GSM900 frequencies in a FHS

    define a SDCCH TS on the G1 TRX. This second action is obvious fromthe first one.

    Impacted TRX ParametersFHS

    Activation scenarioFor a selected E-GSM hopping cell, modify the definition of the FHS,including G1 frequencies.

    32 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 1 Network Modifications

    1.6.11 Improved 2G 3G Cell ReselectionThis feature is a system internal improvement. The feature 2G to 3G cellreselection is a B8 feature.Same as in B8:

    Impacted BSS ParametersEN_2G_TO_3G_Cell_Reselection

    Activation ScenarioSet BSS parameters (one parameter to modify:EN_2G_TO_3G_Cell_Reselection to Enable with 3G search deactivation).

    1.6.12 Load Based 3G HO Filtering"Load based 3G HO filtering " is a feature that can be activated, and ismanaged via the THR_CELL_LOAD_3G_REJECT parameter.All parameters can be modified from both PRC and SC.Rules:

    The feature is deactivated by setting THR_CELL_LOAD_3G_REJECT toits maximum value 100%

    THR_CELL_LOAD_3G_REJECT shall be lower than the 2G load thresholds(HIGH_TRAFFIC_LOAD) or equal to 100%

    Impacted Cell ParametersTHR_CELL_LOAD_3G_REJECTCell_Capacity_Class

    Activation scenarioSet cell parameters, using Edit n cells . (THR_CELL_LOAD_3G_REJECTto 70)

    1.6.13 2G-to-3G HO preparationFor 2G-to-3G HO the UE/MS must support FDD and EN_3G_HO=Yes.The folowing functions are performed:

    Handover detection functionEach time the UE/MS reports measurements the process reevaluatesthe Ec/No averages for all 3G cells measurements reported.For each cell, if AV_ECNO >=THR_ECNO, the cell shall be added inthe list of candidate cells, ranked according to AV_ECNO and 3G cellson top of the list.

    Handover candidate cell evaluationAs 3G cells are on the top of the candidate cells, handover to 3G isprioritized regarding handover to 2G.The candidate cell with the highest rank is the first cell that is selectedto trigger the handover.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 33 / 78

  • 1 Network Modifications

    1.6.14 Enhanced Support of EGPRS in Uplink1.6.14.1 Support of 8PSK Modulation in Uplink

    "Support of 8PSK modulation in uplink" is a feature that cannot be activated.Rules:

    TBF_UL_INIT_MCS

  • 1 Network Modifications

    In the Function menu, select Modify, then select Enable collection, set thevalue of community string, in accordance with what we have on A 9130 BSCEvolution or on the MFS side, and then press [ OK ]Launch the MRGT application.

    1.6.17 Unbalancing TRX Output PowerThe principle of the feature is to define a specific concentric cell in whichthe output power balancing is performed on a zone basis instead of on thesector basis.The feature can be activated or de-activated at cell level.The feature can be activated on a cell having the following characteristics:

    Concentric monoband / concentric umbrella monoband

    Not shared

    Mapped on an Evolium BTS.

    Impacted Cell ParameterEn-Unbalanced-Output-Power

    Activation scenarioSelect a set of concentric cells with the correct characteristics forthis featureSet cell parameters, using Edit n cells .(En-Unbalanced-Output-Power=1).

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 35 / 78

  • 1 Network Modifications

    36 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 2 Scenario Applicability

    2 Scenario Applicability

    The section provides details of the applicability of the scenarios.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 37 / 78

  • 2 Scenario Applicability

    2.1 Add G1/G2 BTS

    2.1.1 Hardware CoverageThis scenario applies to the following BTS:

    G1 BTSs MKII BIUMD with DRFU.G1 BTSs are not supported any more by A9130 BSC Evolution.

    G2 BTSs with DRFU.

    2.1.2 ApplicabilityThis scenario applies to the following cases:

    BTS is installed on a new Abis

    BTS is installed on an existing Abis with downstream BTSs

    BTS is installed at the end of an Abis chain (no downstream BTSs)It is possible to add more than one new BTS and more than one cell

    BTS site master/slave synchronization is supported by G2 BTS

    The BTS is created as the master BTS. The configuration can be changedin a second step from master to slave using BTS Site Master/SlaveSynchronization (G2 and Evolium A9100 BTS: Synchronize BTS SiteMaster/Slave (Section 2.14)).Shared cell is not possible for G1/G2 BTSs.

    38 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 2 Scenario Applicability

    2.2 Add Evolium A9110/A9110-E and A9100 BTS

    2.2.1 A9110/A9110-E ApplicabilityThis scenario applies to the following cases:

    BTS is installed on a new Abis

    BTS is installed on an existing Abis with downstream BTSs

    BTS is installed at the end of an Abis chain (no downstream BTSs)It is possible to add more than one new BTS and more than one cell

    BTS master/slave synchronization is possible for A9110 BTS, but onlywith another A9110

    BTS master/slave synchronization is possible for A9110-E BTS, but onlywith another A9110/A9110-E BTS. The master is always A9110-E BTS.

    Abis via satellite is covered.

    2.2.2 A9100 ApplicabilityPossible scenarios are:

    BTS is installed on a new Abis

    BTS is installed on an existing Abis with downstream BTSs

    BTS is installed at the end of an Abis chain (no downstream BTSs)It is possible to add more than one new BTS and more than one cell

    It is possible to add a BTS with 2 Abis links

    It is possible to add a BTS to extend existing cells using shared cell, withoutreconfiguring BTSs that are already installed. BTSs already on site must beA9100 BTSs

    It is possible to add a BTS to extend existing cells with reconfiguration ofBTSs already installed. Some sectors from the BTSs already on site aredeleted and recreated in the new BTS. This case is part of the Add TRE onA9100 BTS procedure (refer to Evolium A9110/A9110-E and A9100 BTS:Add TRE (Section 2.6) for more information).

    2.2.2.1 Master/Slave ConfigurationThe following apply:

    When the added BTS does not have sectors in shared cell, it is configuredas master. The configuration can be changed in a second step frommaster to slave (refer to G2 and Evolium A9100 BTS: Synchronize BTSSite Master/Slave (Section 2.14)BTS added with sectors in shared cell are in slave configuration.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 39 / 78

  • 2 Scenario Applicability

    2.2.2.2 Abis via SatelliteAbis via satellite is covered when adding a BTS to support new cells.The following prerequisites must be respected:

    The BTS is not synchronized with another BTS, which also excludes thecase of BTS in shared cell

    The configuration required for satellite has already been prepared.

    2.3 Delete G1/G2 BTS

    2.3.1 Hardware CoverageThe scenario applies to the following BTS:

    G1 BTSs MKII BIUMD with DRFU

    G2 BTSs with DRFU.

    2.3.2 ApplicabilityThis following scenarios are possible:

    The deletion of several BTSs at the same time is allowed

    The case of downstream BTSs is covered.

    Master/Slave

    Configuration

    For synchronized G2 BTSs, the deletion of both master and slave is allowed. Ifonly the master BTS must be deleted, first apply the BTS site master/slavedesynchronization method to avoid slave BTSs enter into free running mode.

    40 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 2 Scenario Applicability

    2.4 Delete Evolium A9110/A9110-E and A9100 BTS

    2.4.1 A9110/A9110-E ApplicabilityThis following scenarios are possible:

    The deletion of several BTSs at the same time is allowed

    The case of downstream BTSs is covered.

    2.4.2 A9100 ApplicabilityThis following scenarios are possible:

    The deletion of several BTSs at the same time is allowed

    The case of downstream BTSs is covered.

    2.4.2.1 Master/Slave ConfigurationFor synchronized BTSs, the deletion of both master and slave is allowed.If only the master BTS must be deleted, first apply the BTS site master/slavedesynchronization method to avoid slave BTSs entering into free running mode.If two slave BTSs support a shared cell, they must remain synchronized. Thereare two possibilities: to find another master BTS to synchronize them or one ofthe slave BTSs must become a master BTS.

    2.4.2.2 Shared CellBTSs in shared cell are covered in the following cases:

    BTSs supporting main and secondary sectors are deleted in one shot. Theassociated cells are also deleted

    The BTS supports only secondary sectors. It is deleted and the associatedTRXs are removed from the cell. The BTS supporting the main sectors iskept.

    If a BTS supports both secondary sectors linked to a shared cell and sectorsmapped on dedicated cells, one must first delete the secondary sectors using amethod from the Reconfigure TREs/Sectors on A9100 BTS (refer to EvoliumA9110/A9110-E BTS and A9100: Reconfigure BTS TREs/Sectors (Section2.11)) before deleting the BTS.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 41 / 78

  • 2 Scenario Applicability

    2.5 G1/G2 BTS: Add TRE

    2.5.1 Hardware CoverageThis scenario applies to the following hardware:

    G1 MKII BIUMD with DRFU

    G2 all DRFU.

    2.5.2 ApplicabilityThis following scenarios are possible:

    It is possible for pre-equipped BTSs

    Add TRE is allowed as a individual action (change TRE from half-rate tofull-rate, modify FHS must be performed afterwards).

    2.6 Evolium A9110/A9110-E and A9100 BTS: Add TRE

    2.6.1 A9110/A9110-E ApplicabilityAdd TRE is allowed as a individual action (change TRE from half-rate tofull-rate; modify FHS must be performed afterwards).When adding a A9110-E module to a A9110, then the A9110-E will take theplace of the master.

    2.6.2 A9100 ApplicabilityThese following scenarios are possible:Add TRE is possible on equipped or not-equipped BTS.It is possible to add more than one TRE.Add TRE is allowed as a individual action (change TRE from half-rate tofull-rate, modify FHS must be performed afterwards).If there is no place to insert TREs in the BTS, or a lack of time slots on the Abis,there are two possibilities:

    A BTS is added to extend existing cells using shared cell, withoutreconfiguring the BTSs already installed. If all sectors of the new BTS areconfigured in shared cell, a part of the Add BTS method is applicable (referto Add Evolium A9110/A9110-E and A9100 BTS (Section 2.2))A BTS can be added to extend existing cells with reconfiguration of a BTSalready installed:

    Some sectors from the BTSs already on site are deleted and recreated inthe new BTSSome sectors of the new BTS can be configured in shared cellSome cells might be changed from mono-band to multi-band.

    42 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 2 Scenario Applicability

    2.7 G1/G2 BTS: Delete TRE

    2.7.1 Hardware CoverageThis scenario applies to the following hardware:

    G1 MKII BIUMD with DRFU

    G2 all DRFU.

    2.7.2 ApplicabilityThis following scenarios are possible:

    It is applicable to configuration other than low-loss configuration whichimplies antenna reconfiguration

    Delete TRE is allowed as a individual action (change TRE from half-rate tofull-rate, modify FHS must be performed afterwards).

    2.8 Evolium A9110 /A9110-Eand A9100 BTS: Delete TRE

    2.8.1 A9110/A9110-E ApplicabilityThis following scenarios are possible:

    Delete TRE is allowed as a individual action (change TRE from half-rate tofull-rate, modify FHS must be performed afterwards)When deleting all TREs from the cabinet, apply the method Delete BTS.Refer to Delete Evolium A9110/A9110-E and A9100 BTS (Section 2.4).

    2.8.2 A9100 ApplicabilityThis following scenarios are possible:

    It is possible to delete only TREs or TREs + RA

    Delete TRE is allowed as a individual action (change TRE from half-rate tofull-rate, modify FHS must be performed afterwards).

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 43 / 78

  • 2 Scenario Applicability

    2.9 Evolium A9110/A9110-E and A9100 BTS: Add Sector

    2.9.1 A9110/A9110-E ApplicabilityThis following scenarios are possible:

    A BTS is extended with a new sector and a cell is created and mapped on it

    It is possible to change existing cells from mono-band to multi-band

    Sector on-line commissioning is used.

    2.9.2 A9100 ApplicabilityThis following scenarios are possible:

    New sector added on an existing BTS. A cell is created and mapped on it, oran existing cell is linked to it to create a shared cell

    It is possible to change existing cells from mono-band to multi-band

    Sector on-line commissioning is used.

    2.10 Evolium A9110/A9110-E and A9100 BTS: Remove Sector

    2.10.1 A9110/A9110-E ApplicabilityThis following scenarios are possible:

    If a sector is deleted, the associated cell is deleted too

    Sector on-line commissioning is used.

    2.10.2 A9100 ApplicabilityThis following scenarios are possible:

    If a sector is deleted, the associated cell is either deleted or unmapped,if planned to be reused for another sector. It can also be unlinked if thesector to remove is a secondary one

    It is possible to delete a main sector from a cell after unlink and delete thesecondary sector

    Changing the cell band from multi-band to mono-band not requested

    Sector on-line commissioning is used.

    44 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 2 Scenario Applicability

    2.11 Evolium A9110/A9110-E BTS and A9100: Reconfigure BTSTREs/Sectors

    2.11.1 A9110/A9110-E ApplicabilityIt is possible to combine Add/Delete TREs and Add/Remove Sectors onA9110 BTS.For mixed A9110/A9110-E configuration the following rules apply:

    Maximum three hierarchy levels are allowed: Master, upper and lower Slave

    Each A9110/A9110-E as upper Slave terminates the Master-Slave link

    A9110 not possible in lower Slave position

    A9110-E must be set as Master in A9110/A9110-E mixed configuration.

    2.11.2 A9100 ApplicabilityIt is possible to combine Add/Delete TREs and Add/Remove Sectors onA9100 BTS.For example:

    Three cells, each with four TREs mapped on one BTS are reconfigured tothree cells, each with six TREs mapped on two BTSs

    Three cells, each with six TREs mapped on two BTS are reconfigured tothree cells, each with eight TREs, and one of the cells is shared betweenthe two BTSs.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 45 / 78

  • 2 Scenario Applicability

    2.12 Evolium A9110/A9110-E and A9100 BTS:Create/Reconfigure Multi-band

    2.12.1 A9110/A9110-E ApplicabilityThree scenarios are possible:

    A 900 cell is changed into a 1800 cell

    A 900 cell is changed into a 900-1800 cell

    One 900 cell and one 1800 cell supported by sectors of the same BTS aremerged into one 900-1800 cell.

    2.12.2 A9100 ApplicabilityThe following scenarios are possible:

    A 900 cell is changed into a 1800cell

    A 850 cell is changed into a 1900cell

    A 900 cell is changed into a 900-1800 cell

    A 850 cell is changed into a 850-1900 cell

    One 900 cell and one 1800 cell supported by sectors of the same BTSare merged into one 900-1800 cell

    One 850 cell and one 1900 cell supported by sectors of the same BTSare merged into one 850-1900 cell

    One 900 cell and one 1800 cell supported by sectors of two different BTSsare merged into one 900-1800 cell.

    One 850 cell and one 1900 cell supported by sectors of two different BTSsare merged into one 850-1900 cell.

    Note: The 850/1900 frequency bands are not available for Micro BTS.

    2.13 Evolium A9100 BTS: Upgrade with New ModulesApplicabilityAN, SUM, and TRE Evolium modules are replaced with Evolution modules.The Evolution modules also include GAN and TWIN TRA modules.

    2.14 G2 and Evolium A9100 BTS: Synchronize BTS SiteMaster/Slave

    2.14.1 Hardware CoverageG2 BTSs and A9100 BTSs are covered.

    46 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 2 Scenario Applicability

    2.14.2 ApplicabilityThis scenario applies to the following cases:

    Up to three G2 or A9100 slave BTSs can be synchronized on a masterG2 BTS

    Up to three A9100 slave BTSs can be synchronized on a master A9100 BTS

    Only one G2 slave BTS can be synchronized on a master A9100 BTS.

    2.15 G2 and Evolium A9100 BTS: Desynchronize BTS SiteMaster/Slave

    Hardware CoverageG2 BTSs and A9100 BTSs are covered.

    2.16 G1/G2 BTS: Replace BTS

    2.16.1 ApplicabilityThe G1/G2 BTSs can be replaced with BTSs of any generation.G1 BTS is not supported any more by A9130 BSC Evolution.It is allowable to replace X BTSs with Y BTSs at the same time:

    X can be equal to Y

    X and Y can be equal to 1

    The BTSs can be on different Abis links.

    BSC with or without free Abis ports are covered:

    If the number of free Abis ports is higher or equal to the number of Abislinks needed for the new BTSs, use the Replace X BTS with Y BTS, FreeAbis Port method

    If the number of free Abis ports is smaller than the number of Abis linksneeded for the new BTSs, use the Replace X BTS with Y BTS, SameAbis Port method.

    The new BTSs can have more/fewer sectors/TREs than the replaced BTSs.Cell creation/deletion is allowed.Abis characteristics remain unchanged.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 47 / 78

  • 2 Scenario Applicability

    2.16.2 Master/Slave ConfigurationIt is assumed that synchronized G2 BTSs are all replaced at the same time.Otherwise, the operator must change the synchronization before performingthe BTS replacement. Refer to G2 and Evolium A9100 BTS: SynchronizeBTS Site Master/Slave (Section 2.14) and G2 and Evolium A9100 BTS:Desynchronize BTS Site Master/Slave (Section 2.15) for more informationThe new BTSs can also be synchronized, but it is a prerequisite that thehardware configuration for synchronization has already been done.

    2.16.3 Shared CellShared cell applies to new BTSs if they are A9100 BTSs.

    2.17 Evolium A9110/A9110-E and A9100 BTS: Replace BTS

    2.17.1 A9110/A9110-E ApplicabilityA9110/A9110-E BTSs can be replaced with BTSs of any generation.It is allowable to replace X BTSs with Y BTSs at the same time:

    X can be equal to Y

    X and Y can be equal to 1

    The BTSs can be on different Abis links.

    BSC with or without free Abis ports are covered:

    If replaced BTSs are on several Abis links and enough Abis ports areavailable to support the new BTSs, use the Replace X BTS with Y BTS,Free Abis Port method

    If the new BTSs will be placed on the same Abis link as the replaced ones,use the Replace X BTS with Y BTS, Same Abis Port method.

    The new BTSs can have more/fewer sectors/TREs than the replaced BTSs.Cell creation/deletion is allowed.Abis via satellite is allowed and is kept for the new BTSs with the followingprerequisites:

    All new BTSs are Evolium

    The new BTSs are not in Master/Slave configuration.

    2.17.1.1 Master/Slave ConfigurationConfiguration:

    The new BTSs can also be synchronized, but it is a prerequisite that thehardware configuration for synchronization has already been done

    Master/slave configuration is not possible between A9110/A9110-E andA9100 BTSs.

    48 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 2 Scenario Applicability

    2.17.1.2 Shared CellShared cell is not possible between A9110/A9110-E BTSs and A9100 BTSs.

    2.17.2 A9100 ApplicabilityA9100 BTSs can be replaced with BTSs of any generation. Here, the casewhere BTSs to be replaced and new BTSs are not all the same generationis also applicable.It is permisible to replace X BTSs with Y BTSs at the same time:

    X can be equal to Y

    X and Y can be equal to 1

    The BTSs can be on different Abis links.

    BSC with or without free Abis ports are covered:

    If the number of free Abis ports is higher or equal to the number of Abislinks needed for the new BTSs, use the Replace X BTS with Y BTS, FreeAbis Port method

    If the number of free Abis ports is smaller than the number of Abis linksneeded for the new BTSs, use the Replace X BTS with Y BTS, SameAbis Port method.

    The new BTSs can have more/fewer sectors/TREs than the replaced BTSs.Cell creation/deletion is allowed.

    2.17.2.1 Master/Slave ConfigurationConfiguration:

    It is assumed that synchronized BTSs are all replaced at the same time.Otherwise, the operator must change the synchronization before performingthe BTSs replacement. Refer to G2 and Evolium A9100 BTS: SynchronizeBTS Site Master/Slave (Section 2.14) and G2 and Evolium A9100 BTS:Desynchronize BTS Site Master/Slave (Section 2.15) for more informationThe new BTSs can also be synchronized, but it is a prerequisite that thehardware configuration for synchronization has already been done.

    2.17.2.2 Shared CellIt is assumed that all BTSs in shared cell are replaced at the same time

    The new BTSs can also be in shared cell, but it is a prerequisite that thehardware configuration for synchronization has already been done

    Abis via satellite is allowed and is kept for the new BTSs with the followingprerequisites:

    All new BTSs are Evolium

    The new BTSs are not in Master/Slave configuration.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 49 / 78

  • 2 Scenario Applicability

    2.18 Abis: Move BTS/Abis

    2.18.1 ApplicabilityThe following applies to this scenario:

    BTS configuration is unchanged

    Qmux address conflict is covered

    TRE auto-allocation mode is used

    G1 BTS cannot be moved to a BSC with A9130 BSC Evolution

    If LCS is activated on the moved cells and the target BSC has not thefeature activated, the operator must first activate LCS on the target BSC

    Both satellite or terrestrial Abis connection types are coveredIf a BTS is moved from a terrestrial Abis to a satellite Abis, the followingprerequisites must be respected:

    The BTS is an Evolium BTSThe BTS is not synchronized with another BTS.

    RESTRICTION LCS feature is on hold. It will be available only after decision at project level.

    2.18.2 Rule Specific to Move BTS within Same BSCOne or several BTSs can be moved at the same time

    Note: A G2 BTS in rack sharing is considered as a single BTS.

    50 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 2 Scenario Applicability

    2.18.3 Rules Specific to Move BTS from One BSC to Another2.18.3.1 Master/Slave Configuration:

    The following rules apply:

    A slave BTS must be on the same BSC as its master BTS

    It is possible to move either one BTS or all the synchronized BTSs.If only one BTS is moved, the BTS must be desynchronized beforeperforming the move. Refer to G2 and Evolium A9100 BTS: DesynchronizeBTS Site Master/Slave (Section 2.15) for more information.

    2.18.3.2 Shared CellBecause a shared cell cannot be split over two BSCs, two BTSs sharing a cellmust be moved at the same time when moved from one BSC to another.The following two cases are possible for synchronization:

    One of the BTSs is the slave of the other oneThe two BTSs part of the shared cell are moved. If the master BTS hasanother slave, this slave BTS can be moved or left on the same BSC. Ifit is left on the BSC, it must be changed from a slave configuration into amaster configuration before performing the move

    Both BTSs are slaves of a third BTS associated with another cell.The master BTS is moved at the same time as the BTSs in shared cell.

    2.19 Add BSSApplicabilityIt is possible to introduce a BSS at the OMC-R from an already prepared build(with GPRS pre-populated or not).Actions such as Add/Remove/Move BTS have to be performed after the AddBSS.The GPRS activation has to be performed after the Add BSS.

    Note: The cabling takes into account the GPRS part. If it exists (MFS already cabledor not), the cabling will be in its definitive version.Different X.25 connection modes are supported:

    Connection via PSDN (BSC)Connection via A interface (MSC), through or not the MFS.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 51 / 78

  • 2 Scenario Applicability

    2.20 Add A9130 BSS EvolutionApplicabilityIt is possible to introduce a BSS at the OMC-R from an already prepared build(with GPRS pre-populated or not).Actions such as Add/Remove/Move BTS have to be performed after the AddBSS.The GPRS activation has to be performed after the Add BSS.

    Note: The cabling takes into account the GPRS part. If it exists (MFS already cabledor not), the cabling will be in its definitive version.Different IP connection modes are supported:

    Connection via Ethernet LAN (BSC)Connection via A interface (MSC), through or not the MFS.

    52 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 2 Scenario Applicability

    2.21 A9120/A9130 BSC Evolution: Replace BSCApplicabilityThe method installs, cables and commissions the new A9130 BSC Evolutionwithout disturbing the A9120 BSC.The same procedure could be applied for rack shared configurations (twoA9130 BSC Evolution in the same rack or one A9130 BSC Evolution and oneA9130 MFS Evolution in the same rack).The following steps are performed:

    Backup software package on A9120 BSC

    New BSS package production and A9130 BSC Evolution functionality test

    Removal of A9120 BSC

    Cabling the new A9130 BSC Evolution

    OMC-R configuration upgrade

    2.22 Move BSS: Different SGSNApplicabilityThis scenario is used to physically move a BSS from one SGSN to another,with the same BSS configuration.The connection between the MFS and the Source or Target SGSN canbe either:

    Direct

    Through Frame Relay.

    2.23 Move A9130 BSS Evolution: Different SGSNApplicabilityThis scenario is used to physically move a BSS from one SGSN to another,with the same BSS configuration.The connection between the MFS and the Source or Target SGSN canbe either:

    Direct

    Through Frame Relay.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 53 / 78

  • 2 Scenario Applicability

    2.24 Introduce GPRS

    2.24.1 Hardware CoverageSupported MFS types:

    The three types of A9135 MFS:

    MFS with AS800MFS with DS10 RC23MFS with DS10 RC40

    A9130 MFS Evolution

    2.24.2 ApplicabilityThe following are covered:

    BSS with GPRS, pre-populated or not, are covered

    Existing MFS or new MFS are covered

    The connection via satellite is supposed to be between the BSC and the firstBTS of the Abis, i.e., all BTS on this Abis will use parameters adapted tosatellite connection (also valid for terrestrial connection).Different synchronization modes are supported:For A9135 MFS:

    central clock modeautonomous modeGPU cascading.

    For A9130 MFS Evolution:central clock modeautonomous mode

    Note: For new installed MFS, use only central clock mode or autonomous mode.

    Physical TC extension must already be performedIn case of A9120 BSC the following X.25 connection modes are supported:

    Connection via PSDN (BSC)Connection via A interface (MSC), through the MFS or not.

    In case of A9130 BSC Evolution the following IP connection modes aresupported:

    Connection via Ethernet LAN (BSC)Connection via A interface (MSC), through the MFS or not.

    54 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 2 Scenario Applicability

    2.25 Delete GPRS

    2.25.1 Hardware CoverageSupported MFS types:

    The three types of A9135 MFS:

    MFS with AS800MFS with DS10 RC23MFS with DS10 RC40

    A9130 MFS Evolution

    2.25.2 ApplicabilityDifferent synchronization modes are supported:For A9135 MFS:

    central clock mode

    autonomous mode

    GPU cascading.

    For A9130 MFS Evolution:

    central clock mode

    autonomous mode

    In case of A9120 BSC the following X.25 connection modes are supported:

    Connection via PSDN (BSC)Connection via A interface (MSC), through the MFS or not.

    In case of A9130 BSC Evolution the following IP connection modes aresupported:

    Connection via Ethernet LAN (BSC)Connection via A interface (MSC), through the MFS or not.

    In case of rack shared with split of O&M link, the connection of the A9130 MFSEvolution to OMCr is made through A9130 BSC Evolution on the Ater-Mux.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 55 / 78

  • 2 Scenario Applicability

    2.26 Extend/Reduce or Modify GPRS

    2.26.1 Hardware CoverageSupported MFS types:

    The three types of A9135 MFS:

    MFS with AS800MFS with DS10 RC23MFS with DS10 RC40

    A9130 MFS Evolution

    2.26.2 ApplicabilityBoth the BSS and the MFS are in service.The scenario is applicable for BSS which already have GPRS configuration andExtension/Reduction can be made for:Logical:

    radio interface

    Ater Mux

    Gb

    Hardware:

    add/remove GPU board

    extend MFS subrack (in both cases: A9135 MFS or A9130 MFS Evolution)Different synchronization modes are supported:For A9135 MFS:

    central clock mode

    autonomous mode

    GPU cascading.

    For A9130 MFS Evolution:

    central clock mode

    autonomous mode

    In case of A9120 BSC the following X.25 connection modes are supported:

    Connection via PSDN (BSC)Connection via A interface (MSC), through the MFS or not.

    In case of A9130 BSC Evolution the following IP connection modes aresupported:

    56 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 2 Scenario Applicability

    Connection via Ethernet LAN (BSC)Connection via A interface (MSC), through the MFS or not.

    2.27 Extend BSC and Ater-Mux InterfaceApplicabilityThe following applies:

    Extend BSC and Ater-Mux Interface is performed to increase the resourcesof the CS and PS

    GPRS and MFS configuration remain the same

    TC Extension with ASMC/ATBX/DT16 is covered

    TC Extension with MT120 is covered

    Satellite feature is covered.

    All Ater links of a BSS must have the same connection type, terrestrial orsatellite.

    Note: For Satellite feature introduction, please refer to section Activate Ater Satellite(Section 2.41).

    To extend the Ater-Mux Interface, the BSC must have enough Ater-Mux tosupport the TC extension

    Each BSC rack has to be connected to one (and only one) A9125 TC rack.Note: If, for a BSC rack extension, the extended part of the BSC rack cannot be

    connected to the same A9125 TC rack, a Move BSS, Different A9125 TC ( seesection Move BSS, Different A9125 TC (Section 2.38)) has to be applied.

    Three different Ater-Mux extensions are supported:Logical extension onlyPhysical extension onlyLogical and physical extension.

    3BK 17422 0004 PCZZA Ed.30P02 IN PREPARATION 57 / 78

  • 2 Scenario Applicability

    2.28 Extend A9130 BSC and Ater-Mux InterfaceApplicabilityThe following applies:

    Extend A9130 BSC Evolution and Ater-Mux Interface is performed toincrease the resources of the CS and PS

    The extension is made through an Ater-Mux extension for the TC andthrough the insertion of boards (CCP and possibly LIUs) for the A9130BSC Evolution.

    GPRS and MFS configuration remain the same

    TC Extension with ASMC/ATBX/DT16 is covered

    TC Extension with MT120 is covered

    Satellite feature is covered.

    All Ater links of a BSS must have the same connection type, terrestrial orsatellite.

    Note: For Satellite feature introduction, please refer to section Activate Ater Satellite(Section 2.41).

    To extend the Ater-Mux Interface, the BSC must have enough Ater-Mux tosupport the TC extension

    The TC hardware has to be upgraded to a configuration compatible withthe target A9130 BSC Evolution.

    Three different Ater-Mux extensions are supported:

    Logical extension only

    Physical extension only

    Logical and physical extension.

    2.29 Reduce BSC and Ater-Mux InterfaceApplicabilityGPRS and MFS configuration remain the same. This must be performedbefore this scenario.Reduce TC is covered.

    58 / 78 IN PREPARATION 3BK 17422 0004 PCZZA Ed.30P02

  • 2 Scenario Applicability

    2.30 Add/Delete PCM

    2.30.1 Hardware CoverageBoth MFS types are supported:

    The three types of A9135 MFS:

    MFS with AS800MFS with DS10 RC23MFS with DS10 RC40

    A9130 MFS Evolution

    2.30.2 ApplicabilityBoth the BSS and the MFS are in service.Different synchronization modes are supported:For A9135 MFS:

    central clock mode

    autonomous mode

    GPU cascading.

    For A9130 MFS Evolution:

    central clock mode

    autonomous mode

    In case of A9120 BSC the following X.25 connection modes are supported:

    Connection via PSDN (BSC)Connection via A interface (MSC), through the MF