212690000 e 10

8/13/2019 212690000 e 10

http://slidepdf.com/reader/full/212690000-e-10 1/86

Alcatel-Lucent GSM

Network Reconfiguration

Recommendations

BSS Document

Reconfiguration Method

Release B10

3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10


Status RELEASED

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

BLANK PAGE BREAK

2 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10


Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

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

1.5 Check for Sufficient Resources on Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.5.1 Display Timeslot Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.5.2 Check Submultiplexing Scheme of RSL/OML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

1.5.3 Attempt to Add BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.6 Optional Features Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261.7 Activate New B10 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

1.7.1 STM1 in 9125 TC Equipped with TC STM1 - IP Subrack . . . . . . . . . . . . . . . . . . . 271.7.2 Gb over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281.7.3 Mx Capacity Improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.7.4 Multiple CCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.7.5 Ping Time Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.7.6 Improved Delayed UL TBF release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.7.7 Dual Transfer Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.7.8 Extended Dynamic Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.7.9 Adaptive Multiple Rate - Wideband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

1.7.10 2G to 3G/TDSCDMA Cell Reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321.7.11 Fast 3G Re-selection at 2G CS call release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.7.12 Alarm management of external equipments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.7.13 Enable Multislot Classes 30-33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

1.8 Activate New B9 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341.8.1 Abis Dynamic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341.8.2 M_EGCH Statistical Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351.8.3 Enhanced Transmission Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . 361.8.4 Counter Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361.8.5 Electro Magnetic Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371.8.6 Support of GPRS QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381.8.7 Enhanced Packet Cell Reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391.8.8 Extended UL TBF mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

1.8.9 Autonomous Packet Resource Allocation (RAE4) . . . . . . . . . . . . . . . . . . . . . . . . . . 401.8.10 E-GSM: Support of GPRS and Signalling in G1 Band . . . . . . . . . . . . . . . . . . . . . . 411.8.11 Improved 2G 3G Cell Reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421.8.12 Load Based 3G HO Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421.8.13 2G-to-3G HO preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421.8.14 Enhanced Support of EGPRS in Uplink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431.8.15 RMS Improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431.8.16 SNMP Manager in OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431.8.17 Unbalancing TRX Output Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

2 Scenario Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

2.1 Add G1/G2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462.1.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

2.1.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3BK 21269 AAAA PCZZA Ed.10 3 / 86

8/13/2019 212690000 e 10


Contents

2.2 Add Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100 BTS . . . . . . . . . . . . . . . . . 472.2.1 9110 Micro BTS/9110-E Micro BTS Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . 472.2.2 9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

2.3 Delete G1/G2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492.3.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492.3.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

2.3.3 Master/Slave Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492.4 Delete Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100 BTS . . . . . . . . . . . . . . . 50

2.4.1 9110 Micro BTS/9110-E Micro BTS Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.4.2 9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

2.5 G1/G2 BTS: Add TRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512.5.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512.5.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

2.6 Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100 BTS: Add TRE . . . . . . . . . . . . 512.6.1 9110 Micro BTS Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512.6.2 9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

2.7 G1/G2 BTS: Delete TRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532.7.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

2.7.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532.8 Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100 BTS: Delete TRE . . . . . . . . . . 532.8.1 9110 Micro BTS/9110-E Micro BTS Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . 532.8.2 9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

2.9 Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100 BTS: Add Sector . . . . . . . . . . 542.9.1 9110 Micro BTS/9110-E Micro BTS Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . 542.9.2 9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

2.10 Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100 BTS: Remove Sector . . . . . . 542.10.1 9110 Micro BTS/9110-E Micro BTS Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . 542.10.2 9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

2.11 Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100: Reconfigure BTST R E s / S e c t o r s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552.11.1 9110 / 9110-E Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

2.11.2 9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552.12 Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100 BTS: Create/Reconfigure

Multiband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562.12.1 9110 Micro BTS/9110-E Micro BTS Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . 562.12.2 9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

2.13 Alcatel-Lucent 9100 BTS: Upgrade with New Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562.14 G2 and Alcatel-Lucent 9100 BTS: Synchronize BTS Site Master/Slave . . . . . . . . . . . . . . . . . 56

2.14.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562.14.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

2.15 G2 and Alcatel-Lucent 9100 BTS: Desynchronize BTS Site Master/Slave . . . . . . . . . . . . . . . 572.16 G1/G2 BTS: Replace BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

2.16.1 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

2.16.2 Master/Slave Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582.16.3 Shared Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

2.17 Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100 BTS: Replace BTS . . . . . . . . 592.17.1 9110 Micro BTS/9110-E Micro BTS Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . 592.17.2 9100 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

2.18 Abis: Move BTS/Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612.18.1 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612.18.2 Rule Specific to Move BTS within Same BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612.18.3 Rules Specific to Move BTS from One BSC to Another . . . . . . . . . . . . . . . . . . . . . 61

2.19 Add BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622.20 9120/9130 BSC Evolution: Replace BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632.21 Move BSS: Different SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632.22 Introduce GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

2.22.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

4 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10


Contents

2.22.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.23 Delete GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65


2.24 Extend/Reduce or Modify GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662.24.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

2.24.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662.25 Extend 9120 BSC and Ater Mux Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672.26 Extend 9130 BSC Evolution and Ater Mux Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682.27 Reduce 9130 BSC Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692.28 Reduce 9120 BSC and Ater Mux Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692.29 Add/Delete PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69


2.30 Move Ater PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712.30.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712.30.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

2.31 Add/Delete GPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

2.31.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722.31.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722.32 Add/Delete GP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72


2.33 Move 9120 BSC, Same OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732.33.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732.33.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732.33.3 Satellite Link Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

2.34 Move 9130 BSC Evolution, Same OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742.34.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742.34.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742.34.3 Satellite Link Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

2.35 Move 9120 BSC, Different OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752.35.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752.35.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762.35.3 Satellite Link Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

2.36 Move 9130 BSC Evolution, Different OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772.36.1 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772.36.2 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772.36.3 Satellite Link Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

2.37 Move BSS, Different 9125 TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782.38 Merge TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782.39 Activate Ater Satellite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

2.39.1 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

2.39.2 Satellite Link Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792.40 Deactivate Ater Satellite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792.41 Activate Abis Satellite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

2.41.1 Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792.41.2 Satellite Link Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

2.42 Abis Satellite De-Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792.43 X.25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802.44 IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802.45 Modify Logical Parameters Using MLU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802.46 Introduce LCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812.47 Delete LCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812.48 Introduce E-GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822.49 Deactivate E-GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822.50 Attach Secondary Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

3BK 21269 AAAA PCZZA Ed.10 5 / 86

8/13/2019 212690000 e 10


Contents

2.51 Detach Secondary Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

3 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

3.1 Personnel Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10


Preface

Preface

Purpose This document provides an overview and offers guidelines for persons whocarry out network modification tasks.

What’s New In Edition 10

Section Mx Capacity Improvement (Section 1.7.3) was updated.

In Edition 09

Update with the new equipment naming.

In Edition 08

Section Optional Features Limitation (Section 1.6) was updated.

In Edition 07

Update of system title.

In Edition 06

Section Add BSS (Section 2.19) was updated.

In Edition 05Updates were made in sections:

Applicability (Section 2.18.1)

Introduce LCS (Section 2.46)

Delete LCS (Section 2.47)

Sections Extended Dynamic Allocation (Section 1.7.8) and Dual Transfer Mode (Section 1.7.7) was updated.

In Edition 04

Delivered in release.

Overall document quality was improved following an editorial review.

Gb over IP (Section 1.7.2) was updated.

3BK 21269 AAAA PCZZA Ed.10 7 / 86

8/13/2019 212690000 e 10


Preface

Reduce 9130 BSC Evolution (Section 2.27) was introduced.The following sections were updated:

Optional Features Limitation (Section 1.6)

Enable Multislot Classes 30-33 (Section 1.7.13).The following sections were updated due to system evolution changes:

STM1 in 9125 TC Equipped with TC STM1 - IP Subrack (Section 1.7.1)

Gb over IP (Section 1.7.2)

Move BSS: Different SGSN (Section 2.21)

Extended Dynamic Allocation (Section 1.7.8)

Adaptive Multiple Rate - Wideband (Section 1.7.9)

2G to 3G/TDSCDMA Cell Reselection (Section 1.7.10)

Optional Features Limitation (Section 1.6).

First official release of the document for B10 MR2.

8 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10


Preface

In Edition 03

A new section 2G to 3G/TDSCDMA Cell Reselection (Section 1.7.10) wasadded.

In Edition 02

Optional Features Limitation (Section 1.6) was updated.

In Edition 01The following sections were updated:

TCUC Overload Handling (Section 1.3.4)

Static Multiplexing ( Section 1.4.2.1 )

Activate New B10 Features (Section 1.7)

Statistical Submultiplexing (64 kbit/s) ( Section 1.4.2.2 ).The following sections were updated due to system evolution:

Optional Features Limitation (Section 1.6)

Abis: Move BTS/Abis (Section 2.18)

9120/9130 BSC Evolution: Replace BSC (Section 2.20).

Optional Features Limitation (Section 1.6) was added.3BKA80CBR197035

- The HSL restriction was removed from Activate New B10 Features (Section 1.7).

First official release of the document for B10.

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 functions

on assigned BSSs:

Configuration

Performance

Fault Management.

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

The operation of a Mobile Telecommunications Network

Alcatel-Lucent O&M concepts for the BSS, as described in Operations and

Maintenance Principles

The organization of the telecommunications network you are responsible

for operating.

3BK 21269 AAAA PCZZA Ed.10 9 / 86

8/13/2019 212690000 e 10


Preface

10 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10


1 Network Modifications


This section provides:

An overview of the network modification process

An overview of the reverse procedure

Procedural guidelines

Information about choosing Abis transmission settings

Network configuration hints

Information about checking for sufficient resources on Abis

Information about new B10 feature activation.

3BK 21269 AAAA PCZZA Ed.10 11 / 86

8/13/2019 212690000 e 10



1.1 Network Modification Process

The following figure shows the five major steps to modify the network.

Note: Steps 2 and 3 can be performed in reverse order.

The Hardware Modification 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 not perform 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 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



1.2 Reverse Procedure

In case of problems detected during a scenario, the time interval needed todetect and correct the fault must take into account the time required to reach astable position.

Any investigations must be supported by 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 make this decision.

The customer must inform the manufacturer of the projected time required toreach a stable state (for example: 6:00 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 required 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: Steps 1 and 2 can 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 re−established on the modified part of the network.

Figure 2: Reverse Procedure

3BK 21269 AAAA PCZZA Ed.10 13 / 86

8/13/2019 212690000 e 10



1.3 Procedural Guidelines

This section provides guidelines concerning several important aspects ofnetwork modification:

Reporting telecom impact

Ensuring Service Interface (V.11) (Qmux) continuity

Qmux addressing.

1.3.1 Reporting Telecom Impact

Some network modification procedures have a telecom impact on the system(traffic lost or reduced).

In these cases, operators must warn all the areas of their organization thatcould be affected by this operation:

Supervision

Operations and Maintenance

Customer Care

Quality, etc.

1.3.2 Ensuring Service Interface (V.11) (Qmux) Continuity

For 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 Addressing

The 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 the Qmux address is unique at the network level, the Qmux address can bekept when moving BTS from one BSC to another. Otherwise, it is necessary tochange the Qmux address.

14 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



1.3.4 TCUC Overload Handling

TCUCs are BSC processors in charge of handling the TRX/TRE of the BTS.Their load depends 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 must be taken intoaccount:

Full-rate/dual-rate TRE

Multiplexing scheme (no multiplexing, static, statistical 64k, statistical16k)

Signaling load: high/normal (applicable for statistical 64k submultiplexing,

to limit 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 (for example, spread TRXhandling SDCCH). However, in the case of partial evolution of the configuration(e.g. modification of one TRX), to avoid releasing calls, no action is performed tospread the load. This may lead to overload situations for the TCUC. In this case,

the BSC sends the Processor Alarm[33];SDCCH-OVRL-BSC[9 (begin/endalarm) alarm. The operator can see overload TCUC alarms by looking at the"TCU_Load_Report" window. For each TCUC in overload situation (the alarmbegin is received), the OMC-R displays the corresponding alarm identifier.

The following sections provide some actions and configuration rules that theoperator can follow to either prevent or correct overload situations.

3BK 21269 AAAA PCZZA Ed.10 15 / 86

8/13/2019 212690000 e 10



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 multibandcell, 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 same

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

1.3.4.2 Preventive Actions in Logical Configuration Area

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

1.3.4.3 Corrective Actions

There 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 monoband cells mapped on several TCU

Efficient for multiband cells if the TRE of the outer band are carried by

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 timeslots concept must be considered whenperforming an RSL remapping. The BSC tries to free/find space on TCUs bymoving the Extra timeslots 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 (hardware

configuration 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 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



Modify Multiplexing Conditions

This is a prerequisite for an efficient flat hotspot. Note, however, that thisaction increases the Abis occupancy and so may be refused due to lack oftimeslots 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 recommended

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

3BK 21269 AAAA PCZZA Ed.10 17 / 86

8/13/2019 212690000 e 10



1.4 Choose Abis Transmission Settings

Use the following sections to choose the Abis transmission settings:

Position of the Qmux Bus

Abis Link Capacity.

1.4.1 Position of Qmux Bus

For an Alcatel-Lucent BTS, the transmission configuration is managed usingthe OML link.

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 timeslot. Moving the position of the Qmux bus in the Abis frameimplies an onsite reconfiguration of the BIE module.

1.4.2 Abis Link Capacity

When no multiplexing applies, there is:

One OML per BTS which takes one 64 kbit/s timeslot

One RSL per TRE which takes one 64 kbit/s timeslot

Eight TCHs for each TRE, using two contiguous timeslots for non-9100

and 9110 Micro BTS/9110-E Micro BTS. Note that 9100 and 9110 Micro

BTS/9110-E Micro BTS also use two timeslots, but they do not have

to be contiguous.

The capacity of an Abis link, in terms of the number of BTS and the number

of TRE depends on:

The multiplexing of control channels

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

The 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 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



1.4.2.1 Static Multiplexing

Static multiplexing enables you to multiplex up to four RSL channels of the sameBTS on one single timeslot of the Abis frame. It allocates 16 kbit/s per RSL.

Note: Three RSLs cannot be multiplexed on one Abis timeslot.

It is supported by the following hardware:

9120 BSC, 9130 BSC Evolution

G2 BTS with Dual Rate Frame Unit (DRFU), 9100/9110 Micro 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 BTS ontoa single 64 kbit/s Abis timeslot. It dynamically allocates the bandwidth amongthe RSLs. RSLs with more traffic get more bandwidth (up to the complete 64kbit/s) than RSLs with less traffic. If dual rate TREs are defined, only two RSLwill be multiplexed together with one OML on the same Abis timeslot.

Note: Three RSLs cannot be multiplexed on one Abis timeslot.

1.4.2.3 Statistical Submultiplexing (16 kbit/s)

This enables you to multiplex one OML and one RSL of the same BTS intoa single 16 kbit/s timeslot nibble (in timeslot 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 timeslots available in one Abis link

for use by the TCH and control channels.

By QmuxSupervision

Timeslot 0Transparency(not used byQmux)

Timeslot 0 Use(used by Qmux)

By OML

Chain 30 31 31

Ring 29 30 29

Table 1: Abis Link Capacity

3BK 21269 AAAA PCZZA Ed.10 19 / 86

8/13/2019 212690000 e 10



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

Number of Timeslots NeededNo. of TRX

No Multiplexing Static Multiplexing Statistical

Submultiplexing

(64 kbit/s)

Statistical

Submultiplexing

(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: Timeslots Needed Per Number of TRX for Each Type of Submultiplexing

20 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



1.5 Check for Sufficient Resources on Abis

Sufficient resources must exist on the Abis links when you perform a networkmodification. For example, when you add a BTS, you must have enough freetimeslots for the TCHs, RSLs, OML and extra Abis TS.

To find out if sufficient resources exist, you can:Display timeslot allocation

Check the submultiplexing scheme of the RSL

Attempt to add the BTS.

1.5.1 Display Timeslot Allocation

To find free timeslots on the Abis, use Display Abis Timeslot Allocation and notedown which timeslots are not being used.

1.5.2 Check Submultiplexing Scheme of 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 timeslot.

Type ofMultiplexing

OMLperTimeslot

RSL perTimeslot

OneTimeslotSharedBetweenOML & RSLs

TRX-Timeslot0 bits1-2 used(no otherTimeslotneeded for

RSL, OML)

No Multiplexing 1 1 - -

Static Multiplexing(Dual-rate notallowed)

1 4 (16 kbit/sper RSL)

- -

StatisticalSubmultiplexing(64 kbit/s)

- - 1 OML+ 1RSL

1 OML+ 2RSL

1 OML+ 4RSL

-

StatisticalSubmultiplexing(16 kbit/s)(Dual-rate notallowed)

- - - 1RSL+ 1OML, both at16 kbit/s atTRX-Timeslot0 bits 1-2

Table 3: Number of RSL/OML per Timeslot

3BK 21269 AAAA PCZZA Ed.10 21 / 86

8/13/2019 212690000 e 10



1.5.3 Attempt to Add BTS

Attempt to add the BTS, using the Add BTS, New Cell(s) scenario.

In the case of a secondary Abis:

The allocation for OML, RSL and basic timeslots is done only on the first

Abis in limit of the available space

The MAX_EXTRA_TS_PRIMARY setting is taken into account only if

the BTS has a secondary Abis link

Extra Abis timeslots allocation is done on the primary Abis, if

MAX_EXTRA_TS_PRIMARY>0, after allocating all the signaling links

and basic timeslots. If the secondary Abis is present, only Extra Abis

timeslots can be allocated on it.

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

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

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

22 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



When 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 musttake into account the following:

1 TCU supports 4 Eq-FR

1 TCU supports 2 Eq-DR

1 Extra Abis timeslot = 0.5 Eq-FR

Extra Abis timeslots are mapped only on TCUs supporting TRE full-rate and

not on TCUs supporting dual-rate TRE

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

In order to add a BTS on the Abis, the operator should first check:

If the number of available Eq-FR on TSU allows the addition of the BTS

Number of Eq-FR needed for the operation

Number of resources on primary and secondary Abis links.

For TSU connectivity, the operator must take the following information intoaccount:

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 21269 AAAA PCZZA Ed.10 23 / 86

8/13/2019 212690000 e 10



During the scenario, if no error messages are displayed, the BTS is successfullyadded. If not, use the solutions provided in the following table to solve theresource problems on the Abis.

When ... The following errormessage appears:

Perform the following ...

There is a lack of TSUspace for RSL, OMLand TCH

Lack of primary

TSU Eq-FR for

RSL,OML and TCH:

requested: xxx,

available: yyy orLack of primary

TSU Eq-FR for

Extra Abis TS:

requested: xxx,

available: yyy ,where:

xxx is the number

of Eq-FR needed

for TCH/Extra Abis

timeslots for this

TCU

yyy is the is the

Eq-FR before the

command for this

TSU.

Reshuffle TSU using Remap RSL.

RSL remapping is possibleat three levels:

Compact RSL/TCU

remapping

Balanced load (with

possible impact on other

TCU

Balanced load (with no

impact on other TCU).

There is a lack ofTSU space for ExtraAbis timeslots on thesecondary TSU

Lack of secondary

TSU space:

requested Eq-FR:

xxx, available

Eq-FR: yyy , where:

xxx is the number

of Eq-FR needed

for TCH/Extra Abis

timeslots for this

TCU

yyy is the is theEq-FR before the

command for this

TSU.

Reshuffle TSU using Remap RSL.

RSL remapping is possibleat three levels:

Compact RSL/TCU

remapping

Balanced load (with

possible impact on other

TCU

Balanced load (with noimpact on other TCU).

24 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



When ... The following errormessage appears:

Perform the following ...

There is no space onAbis for RSL, OML

and basic timeslots

Lack of Abis TS

for RSL, OML and

TCH: Requestedxxx, available:

yyy , where:

xxx is the

total number of

timeslots required

to be allocated for

RSL, OML and

TCH

yyy is the number

of free useabletimeslots before

the execution of

this command.

Defragment Abis Chain/Ring .

Fill-Up Primary Abis Chain if the BTS must be declaredon the secondary Abis ofanother BTS.

Delete Extra timeslots(pools) or TRE.

Increase/decreaseMAX_EXTRA_TS_PRIMARY.

There is a lack ofspace for Extra Abistimeslots

Lack of Abis TS

for Extra Abis TS:

requested: xx,

available (1st/2nd

Abis): yy/zz ,where:

xx is the totalnumber of

timeslots required

to be allocated

for Extra Abis

timeslots

yy/zz is the

number of

free usable

timeslots on

primary/secondaryAbis for this BTS,

after the execution

of the RSL, OML

and TCH mapping.

MAX_EXTRA_TS_PRIMARY

is not taken into

account for this

computation.

Defragment Abis Chain/Ring .

Fill-Up Primary Abis Chain .

Delete Extra timeslots(pools) or TRE.

Increase/DecreaseMAX_EXTRA_TS_PRIMARY

Table 4: Error Messages for Add BTS

3BK 21269 AAAA PCZZA Ed.10 25 / 86

8/13/2019 212690000 e 10



1.6 Optional Features Limitation

A checking mechanism is implemented at OMC level, in order to limit thenumber of units when that optional feature is activated. Only the TRX is usedas a unit for the counting and inside computation algorithms.

There is a configurable threshold with the default value set to 95%. When thenumber of objects configured with any of the locked features is close to thethreshold value, the user receives a warning message.

The following features are locked according to a number of TRX:

EDGE(*)

CS3–CS4(*)

AMR_FR

AMR_HR(*)

Logical TRX

DR TRE

TxDiv TRE

E-GSM Cells

CS1–CS2( *)

2G-3G HO

2G-3G Interoperability

Streaming QoS(*)

2G-3G TDSCDMA

Multi CCCH

DTM( *)

EDA( *)

EN_MULTISLOT_CLASS_30_33

( *) For these features, there are possible two computation modes for thecounting of used TRX:

Mode 1: The sum of all TRXs belonging to the cells where the feature

parameter is set to “enabled”.

Mode 2: For all cells having the feature parameter set to “enabled” and

where GPRS is activated, integer part of (sum MAX_PDCH for all cells)/8.

Note: Only one of the two modes is considered as “activated” at a time. The totalquantities for the GPRS related features are computed for both computationmodes, but the limit checking is done according to the active mode selected bythe customer.

Note: All the optional features are sold according to a number of TRX. If the operatorexceeds the number of TRX allocated by contract, the creation and applicationof a new configuration is refused at the next PRC activation.

26 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



1.7 Activate New B10 Features

1.7.1 STM1 in 9125 TC Equipped with TC STM1 - IP Subrack

STM1 is only available in an 9125 TC with a TC STM1-IP subrack.

STM1 is a 155 Mbit/s interface, defined within the SDH family of interfaces(others are STM4, STM1 and so on). In GSM, SDH is used only for thetransport of E1 links.

Each E1 link is transported transparently (using asynchronous mapping) in oneVC12 container. One STM1 link can contain up to 63 VC12 containers. A VC12container is also called VC12 tributary.

Prerequisites

The 9125 TC is already equipped with a TC STM1-IP subrack

A “working” STM1 configuration file is ready to be downloaded from

TC-NEM.

In order to activate STM1, several major steps must be performed:

9125 TC declaration at the OMC-R

STM1 interface declaration

Transmission terminal points configuration

Activation of the required configuration.

The following Activation Scenario applies:

1. 9125 TC declaration at the OMC-R.

If the 9125 TC with a TC STM1 board was not previously declared on theOMC-R, perform the Declare an 9125 TC task.

2. STM1 interface declaration.

If the STM1 interface was not previously declared on the OMC-R, declarethe requested STM1 interface from the OMC-R (STM1 interfaces andassociated STM1-TTPs are created in the TC).

3. Transmission terminal points configuration.

Unlock the associated pair of STM1-TTPs, if required.

4. Activation of the required configuration:

Start the TC-NEM application. See also Local Connection and Remote

Connection , depending on the type of connection to the TC-NEM.The "TC-NEM Communication" window opens.

To connect, from the menu bar, select Serial -> Connect.The TCIF panel opens.

Select the "STM1 Configuration" tab.

Open the default configuration file in a text editor or from the TC-NEM

application.In the "STM1 Configuration" tab, in the "Get" frame, click on [ Current ].The current configuration file opens.

Import the file in the Configuration folder in order to change it.

3BK 21269 AAAA PCZZA Ed.10 27 / 86

8/13/2019 212690000 e 10



In the "STM1 Configuration" tab, click on [ Import ].

Modify the current configuration file.

To do so:

In the first ’Browse’ section, find the saved file in the Configuration

folderOnce the file is selected in the ’Browse’ field, click on [ View ].

The "STM1 View" window opens.

Make the necessary changes in the configuration file

In the ’ File Name’ field, type a name for the modified file and click on

[ Save ]

Click on [ OK ] to confirm the changes

Check the file.Click on [ Check ]. If the check result is not OK, correct the errors and

then save the file again.

5. Download the configuration file from the TC-NEM to the TC STM1-IPsubrack.

In the "Set" frame, click on [ Candidate ].

Note: Once it is downloaded, the STM1 configuration is identified as the candidateconfiguration.

6. If a candidate configuration is applied for the first time, unlock and verifySTM1_TTPs.

7. Apply the candidate configuration.

Click on [ Apply ].

1.7.2 Gb over IP

Gb over IP is an optional feature.

The user is not allowed to set Gb_Transport_Mode parameter on IP mode ifthe feature has not been bought.

The GboIP is an alternative to the GboFR (Frame Relay), in order to decreasethe transmission costs in BSS network. The MFS can support, at the sametime, Gb over Frame Relay and Gb over IP, and the granularity of the Gbtransport mode is the BSS.

The feature is completely independent of BTS connection type (TDMA or IP)or the Ater connection type (TDMA or IP), so it is possible to implement theGboIP feature with a BSS not in IP.

Prerequisites

For an 9135 MFS, replace existing hubs/switches with a 1Gigabit /VLAN

capable switch (Alcatel-Lucent Omniswitch 6224)

For an 9130 MFS Evolution, if necessary, move from 2 LANS O&M to

1 LAN O&M

If necessary, install and configure a new router to be used for telecom.

Connect the new router to the MFS & IP network

28 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



Gb over IP is supported on:

9130 MFS Evolution

9135 MFS with DS10 control station equipped with Alcatel-Lucent

OmniStack LS 6224 switches.

For the Move GboFR to GboIP Scenario , refer to Configure GPRS .

1.7.3 Mx Capacity Improvement

The following sub-features apply:

1000 TRX 9130 BSC Evolution capacity

Removal of HR impact on BSC connectivity

Up to 500 cells per BSC.

In order to have 1000 TRX in one 9130 BSC Evolution, the following

modifications are necessary:

Introduction of a High Speed Signaling Link (HSL)

Addition of 2 more CCP boards

A new type of TPGSM board will be used.

To implement the removal of the HR impact on BSC connectivity, a newOMC-R command, Remap BTS on CCP, is introduced. The maximum numberof TREs mapped to a CCP is not related to whether the TREs are FR orDR. It is always possible to map up to four TREs (FR and/or DR) per VTCU(that is, up to 200 TREs per CCP).

The capacity is extended to 500 cells for the 9130 BSC Evolution . Thenumber of 2G adjacencies to be supported per 9130 BSC Evolution in B10 is10300. The maximum number of 3G external cells supported per 9130 BSCEvolution is 850, and the maximum number of 3G cells adjacencies is 1850.

Activation scenario

1. Up to 1000 TRX per 9130 BSC Evolution, up to 500 cells per 9130BSC Evolution.

Except for the HSL activation scenario described in Extend Ater Mux Interface , there is no specific activation required for this feature other thanthe hardware requirements. The 9130 BSC Evolution must be equippedwith a number of CCP(s), in line with the awaited capacity. Moreover, the

9130 BSC Evolution must be equipped with a new type of TPGSM board.

2. Removal of HR impact on BSC connectivity:

In RNUSM, select the required BSC

Right click and select Edit

Select Procedures -> Resource Management

Set the parameter EN_4_DR_TRE_PER_TCU to ’Dynamic’.

3BK 21269 AAAA PCZZA Ed.10 29 / 86

8/13/2019 212690000 e 10



1.7.4 Multiple CCCH

This feature increases CCCH capacity by allowing the operator to configuremore than one CCCH timeslot.

Activation scenario

Create a PRC containing the cells to be configured with Multiple CCCH.

In the PRC, select the required cells


Select Radio Channel Configuration -> Timeslot Configuration

Modify the radio TS2 from BCCH TRX to CCCH

1.7.5 Ping Time Reduction

No specific action is required to activate this feature.

1.7.6 Improved Delayed UL TBF release

No specific action is required to activate this feature.

1.7.7 Dual Transfer Mode

This feature allows a dual transfer mode capable MS to use a radio resource forCS traffic and simultaneously one or several radio resources for PS traffic.

Activation scenario

Create a PRC containing the cells to be configured with DTM


Right click and select Edit n Cell

Select GPRS -> General Groups->EN_DTM

Set parameter EN_DTM to ’Enabled’.

1.7.8 Extended Dynamic Allocation

The Extended Dynamic Allocation is an extension of the basic DynamicAllocation (E)GPRS MAC mode to allow higher throughput in uplink for type 1

mobile stations (supporting the feature) through the support of more than tworadio transmission timeslots.

The feature is useful only whenever the mobile station does not share itsresources.

Activation scenario

Create a PRC containing the cells to be configured with EDA


Right click and select Edit n Cell

Select GPRS -> General Groups->EN_EDA

Set parameter EN_EDA to ’EDA activated’.

30 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



Set one BSS parameter:

In the PRC, select the required BSS


Select GPRS -> Radio Res.Mngt.

Set one BSS parameter (ALLOW_DTM_EDA_COMBINATION) to ’EDA

usage in DTM mode allowed’.

The other parameters can be used with their default value.

1.7.9 Adaptive Multiple Rate - Wideband

This feature allows the use of AMR-WB (Adaptive Multiple Rate - Wideband)FR in the cell.

AMR-WB is an optional feature, and is sold based on the number of TRX

This feature is not compatible with TFO (Tandem Free Operation)The cell must be an Alcatel-Lucent cell (no G2 BTS)

The TC must be equipped with MT120-WB boards, however it is not checkedby the OMC-R and the feature can be enabled even if there is no MT120-WB

The AMR Wideband (AMR-WB) codec is developed as a multi-rate codecwith several codec modes like the AMR codec. As in AMR, the codec modeis chosen based on the radio conditions. This feature is available for bothTDM and IP configurations.

Impacted Cell Parameters

EN_AMR_WB_GMSK

AMR_WB_GMSK_THR_1

AMR_WB_GMSK_THR_2

AMR_WB_GMSK _HYST_1

AMR_WB_GMSK _HYST_2

DL_DTX_AMR_WB_GMSK

DTX_INDICATOR_SACCH_AMR_WB_GMSK

EN_INTRA_DL_AMR_WB_GMSK

EN_INTRA_UL_AMR_WB_GMSK

L_RXQUAL_DL_H_AMR_WB_GMSK

In order to activate the feature, set the EN_AMR_WB_GMSK parameterto Enable.

3BK 21269 AAAA PCZZA Ed.10 31 / 86

8/13/2019 212690000 e 10



Activation scenario

Task Nr. Task Description Site To Do

1 Perform a BSC SW change OMC-R 1h30 min. for9120 BSC

1h11min. forBSC Evolution

2a A new MT120-WB board is introduced and declaredin the TC.

TCNEM or TCTerminal andBSC Terminal

5 min.

2b Or: A legacy MT120 board is replaced by aMT120-WB

TCNEM or TCTerminal

5 min.

3 Check the configuration. The new board is nowvisible in the MT120 configuration view

TCNEM or TCTerminal

1 min.

4 Perform a MT120 SW change on the new board. TCNEM or TCTerminal

5 min.

5 Activate the SW change on the new board. TCNEM or TCTerminal

2 min.

6 The BSC discovers the MT120-WB on the QMUXinterface.

OMC-R 1 min.

7 Check the configuration at the OMC-R in theHardware view.

OMC-R 1 min.

1.7.10 2G to 3G/TDSCDMA Cell Reselection

The 2G to 3G/TDSCDMA (Time Division-Synchronous Code Division MultipleAccess) cell reselection feature is available and optional, lockable at theOMC-R. As it is a time division duplexing, no TX-RX frequency separation isrequired, and UARFCN can be used for any of uplink or downlink transmission.3G TDD coverage is allowed in the area of a given 2G cell.

Activation scenario

Create a PRC containing the cells to be configured with 3G/TDSCDMA

Reselection



Select UMTS -> Reselection

Modify, using Edit n cell 2, the (EN_2G_TO_3GTDD_CELL_RESELECTION,

TDD_Qoffset) parameters for the selected cells.

Set one BSS parameter:

In the PRC, select the required BSS

32 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10




Select UMTS

Set the BSS parameters from the box (TDD_FREQUENCY_LIST).

1.7.11 Fast 3G Re-selection at 2G CS call releaseThis feature introduces a new information element defined in the CHANNELRELEASE message: cell selection indicator after release of all

TCHs and SDCCH, indicating the MS where camping can be tried after channel(TCH/SDCCH) release.

The IE indicates the frequency and optionally the scrambling code (in the caseof an UTRAN frequency) on which the MS will start a cell selection. If this IEis absent, the MS will try to camp on the cell on which the TCHs or SDCCHwas released as specified, if suitable.

Activation scenario

Create a PRC containing the cells to be configured with Fast 3G Reselection



Select UMTS -> Reselection

Modify, using Edit n cells , one parameter (EN_FAST_3G_RESELECTION)

for the selected cells.

1.7.12 Alarm management of external equipments

This section refers to two sub-features:

An optional feature that allows the OMC-R to manage alarms originated on

equipment outside the BSS

A basic feature that allows the management of the OMC-R alarms.

Both types of alarms are visible from the AS and the management mechanismuses the SNMP manager-agent principle.

Activation scenario

You can activate this feature through a new OMC-R component.

Select UFM -> ExNE ManagementThe following parameters must be set in order to activate the feature:

SNMPNE-Friendly-Name

SNMPNE-IP-Address

SNMPNE-Port (default value is OK)

SNMPNE-Sup-Start-Flag

3BK 21269 AAAA PCZZA Ed.10 33 / 86

8/13/2019 212690000 e 10



1.7.13 Enable Multislot Classes 30-33

This feature is optional and lockable at OMC-R level, taking into account themaximum number of TRX on which the feature can be activated. It takes intoaccount the multislot classes 30-33 for GPRS and EGPRS.

Activation scenario

Create a PRC containing the cells to be configured with

EN_MULTISLOT_CLASS_30_33



Select GPRS -> Cnct Ctrl 2/2

In order to activate the feature, set the EN_MULTISLOT_CLASS_30_33

parameter to enable.

1.8 Activate New B9 Features

Mechanisms

Feature activation is the last step of the migration of an Alcatel-Lucent BSS.

The parameters concerning the B9 features activation are set via two differentmodes:

With a PRC activated in Message Mode for modifying BSC parameters

With a PRC activated in Massive Logical Update, for activation of a global

feature. MLU activation mode is only applicable on cell parameters.

Some features require hardware modifications to work properly.

1.8.1 Abis Dynamic

This feature is an internal system improvement. There is no specific operatoractivation.

The transition from B8 HSDS to B9 HSDS with Dynamic Abis is managed byspecific actions in the migration steps.

The main O&M impacts resulting from the Dynamic Abis allocation feature,as compared to the HSDS feature in B8, from the migration or user point of

view, are as follows:The number of extra Abis timeslots is defined per BTS. It replaces the B8

notion of TRX pool type.

To simplify the rules to share basic nibbles inside a given cell, a new B9

O&M constraint is introduced which guarantees that, in a cell shared over

two 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 are configured for the BTS,

or when all Extra TSs are broken)

34 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



partly available (when some Extra TSs are broken, and others not)This state is obtained by the OMC-R through the HSDS-Synthesis view.

These states replace the B8 states "available", "truncated", "unavailable"(B8 states per TRX pool). As this information are not persistent in theOMC-R and are displayed by means of BSC get, there is no need to migrate

this pool status information.New cell to GPU mapping algorithm that leads to new reshuffling situations

in the MFS.

Due to the improved usage of Abis resources, depending on the load of thepacket traffic, the operator is able to reduce the number of Extra TSs.

1.8.2 M_EGCH Statistical Multiplexing

No new logical parameters are necessary for this feature that cannot beactivated.

3BK 21269 AAAA PCZZA Ed.10 35 / 86

8/13/2019 212690000 e 10



1.8.3 Enhanced Transmission Resource Management

Enhanced transmission resource management is a feature that cannot beactivated.

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 the PRC and SC.

1.8.4 Counter Improvements

Counter improvements is a feature that cannot be activated.

This feature is a system internal improvement. There is no specific operatoractivation.

36 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10


8/13/2019 212690000 e 10



1.8.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, support ofstreaming flow sub-feature is managed via the EN_STREAMING parameter.

Rules: RMIN_GMSK <= RMIN_EGPRS

All parameters can be modified from both the PRC and SC.

Impacted Parameters


EN_PFC_FEATURE EN_STREAMING

BEST_EFFORT _PRIORITY QOS_SAFETY_MARGIN

SIGNALLING _PRIORITY RMIN_EGPRS

HIGH_PRECEDENCE_ BACKGROUND_PRIORITY RMIN_GPRS

HIGH_PRECEDENCE_ THP1_PRIORITY R_AVERAGE_EGPRS

HIGH_PRECEDENCE_ THP2_PRIORITY R_AVERAGE_GPRS

HIGH_PRECEDENCE_ THP3_PRIORITY RMIN_GMSK

LOW_PRECEDENCE_ BACKGROUND_PRIORITY -

LOW_PRECEDENCE_ THP1_PRIORITY -



NORMAL_PRECEDENCE_ BACKGROUND_PRIORITY -

NORMAL_PRECEDENCE_ THP1_PRIORITY -



PFC_T6 -

PFC_T8 -

SMS_PRIORITY -

T_MAX_STREAMING_BUFFERING -

Activation scenario

Set the BSS parameters (EN_PFC_FEATURE set to True)

Set cell parameters, using Edit n cells (EN_STREAMING parameter).

38 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



1.8.7 Enhanced Packet Cell Reselection

1.8.7.1 NC2 Improvement: Cell Ranking With Load Criteria

This feature can be activated, and is managed through theTHR_NC2_LOAD_RANKING parameter.


Impacted Cell ParametersTHR_NC2_LOAD_RANKING

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

1.8.7.2 NACC

This feature is blocked at the OMC-R in the case of a satellite used on theAbis or Ater.

This feature can be activated, and is managed through the EN_NACCparameter.


Rules:

The cell is mapped on Alcatel-Lucent BTSs

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


EN_NACC

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

1.8.7.3 Packet (P)SI status

This feature is blocked at the OMC-R in the case of a satellite used on theAbis or Ater.

This feature can be activated, and is managed through the EN_PSI_STATUSparameter.


Rules:

The cell is mapped on Alcatel-Lucent 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).

3BK 21269 AAAA PCZZA Ed.10 39 / 86

8/13/2019 212690000 e 10



1.8.8 Extended UL TBF mode

This feature can be activated, and is managed via the EN_EXTENDED_UL_TBFparameter.

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-R uses

different coding rules than those given in the BSS Telecom Parameters, pay

special attention when checking the above rule, as all the involved values

must be expressed in the same measurement unit

EN_ EXTENDED_UL_TBF can be set to True for a cell mapped upon a

non Alcatel-Lucent BTS

Impacted 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 setto True).

1.8.9 Autonomous Packet Resource Allocation (RAE4)

This feature cannot be activated.

This feature is a system internal improvement.

There is no specific operator activation.

40 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



1.8.10 E-GSM: Support of GPRS and Signalling in G1 Band

This feature can be activated, in the sense that the radio configuration of a cellusing G1 frequencies can be modified to take advantage of the feature.

The EGSM_RR_Alloc_Strategy parameter 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:

EGSM_RR_Alloc_Strategy = 0 means that not all GSM900 mobile stations

in the network are assumed to be E-GSM capable. G1 and PGSM TRX

are not managed in the same way.

EGSM_RR_Alloc_Strategy = 1 means that all GSM900 mobile stations in

the network are assumed to be E-GSM capable. No difference made

between a G1 TRX and a PGSM TRX.

The EGSM_RR_Alloc_Strategy parameter is defined in the BSC CDE table,and must be set during the migration.

1.8.10.1 Activation in Case of EGSM_RR_Alloc_Strategy=0

GPRS 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.8.10.2 Activation in Case of EGSM_RR_Alloc_Strategy=1

In a cell already defined with the E-GSM frequency band, the operator can:

Mix G1 and GSM900 frequencies in a FHS

Define a SDCCH TS on the G1 TRX. This second action is a direct result

of the first action.

Impacted TRX ParametersFHS

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

3BK 21269 AAAA PCZZA Ed.10 41 / 86

8/13/2019 212690000 e 10



1.8.11 Improved 2G 3G Cell Reselection

This feature is a system internal improvement. The 2G to 3G cell reselectionfeature 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.8.12 Load Based 3G HO Filtering

This feature can be activated, and is managed via theTHR_CELL_LOAD_3G_REJECT parameter.


Rules:

The feature is deactivated by setting THR_CELL_LOAD_3G_REJECT to its

maximum value of 100%

THR_CELL_LOAD_3G_REJECT must be lower than the 2G load thresholds

(HIGH_TRAFFIC_LOAD) or equal to 100%


THR_CELL_LOAD_3G_REJECT

Cell_Capacity_Class

Activation scenarioSet cell parameters, using Edit n cells (THR_CELL_LOAD_3G_REJECT to70).

1.8.13 2G-to-3G HO preparation

For 2G-to-3G HO, the UE/MS must support FDD and EN_3G_HO=Yes.

Perform the following functions:

Handover detection function

Each time the UE/MS reports measurements, the process reevaluatesthe Ec/No averages for all reported 3G cells measurements

For each cell, if AV_ECNO >=THR_ECNO, the cell must be added in

the list of candidate cells, ranked according to AV_ECNO and 3G cells

on top of the list.

Handover candidate cell evaluation

As 3G cells are on the top of the candidate cells, handover to 3G is

prioritized regarding handover to 2G

The candidate cell with the highest rank is the first cell that is selected

to trigger the handover.

42 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



1.8.14 Enhanced Support of EGPRS in Uplink

1.8.14.1 Support of 8PSK Modulation in Uplink

This feature cannot be activated.

Rules:

TBF_UL_INIT_MCS <= MAX_EGPRS_MCS

TBF_DL_INIT_MCS <= MAX_EGPRS_MCS

Migration rules:

TBF_UL_INIT_MCS(B9) = Min(TBF_UL_INIT_MCS(B8),

MAX_EGPRS_MCS)

TBF_DL_INIT_MCS(B9) = Min(TBF_DL_INIT_MCS(B8),

MAX_EGPRS_MCS)

1.8.14.2 Support of Incremental Redundancy in UplinkThis feature can be activated, and is managed via the EN_IR_UL parameter.


Impacted BSC Parameters

EN_IR_UL

EN_RESEGMENTATION_UL

Activation scenarioSet BSS parameters EN_IR_UL to True.

1.8.15 RMS Improvement

This featurecannot be activated.

The new parameters are set to their default values and can be modified fromthe PRC only. As they are not considered as critical values, the operator doesnot have to change them during migration.

1.8.16 SNMP Manager in OMC

This feature is not optional but must be enabled after the migration.

The purpose of the feature is to collect, in the 9130 BSC Evolution or the MFS,

data using SNMP and to retrieve this data at the OMC-R level.

The retrieved data comprises:

CPU, memory and swap

Network activity

Disk usage.

Activation scenario

In DCN, open the BSS or the MFS window, and select the required 9130

BSC Evolution or MFS

3BK 21269 AAAA PCZZA Ed.10 43 / 86

8/13/2019 212690000 e 10



In the Function menu, select Modify, then select ’Enable collection’ , and

set the value of community string, in accordance with what exists on the

9130 BSC Evolution or on the MFS side, and then press [ OK ]

Launch the MRGT application.

1.8.17 Unbalancing TRX Output Power

This feature defines a specific concentric cell in which the output powerbalancing is performed on a zone basis instead of on a sector basis.

The feature can be activated or de-activated at cell level.

The feature can be activated on a cell with the following characteristics:

Concentric monoband / concentric umbrella monoband

Not shared

Mapped on an Alcatel-Lucent BTS.

Impacted Cell ParameterEn-Unbalanced-Output-Power

Activation scenario

Select a set of concentric cells with the correct characteristics for

this feature

Set cell parameters, using Edit n cells (En-Unbalanced-Output-Power=1).

44 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10


2 Scenario Applicability


The section provides information about the applicability of the scenarios.

3BK 21269 AAAA PCZZA Ed.10 45 / 86

8/13/2019 212690000 e 10



2.1 Add G1/G2 BTS

2.1.1 Hardware Coverage

This scenario applies to the following BTS:

G1 BTSs MKII BIUMD with DRFU.G1 BTSs are no longer supported by the 9130 BSC Evolution.

G2 BTSs with DRFU.

2.1.2 Applicability

This 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 BTSThe configuration can be changed in a second step from master to slaveusing BTS Site Master/Slave Synchronization (G2 and Alcatel-Lucent 9100 BTS: Synchronize BTS Site Master/Slave (Section 2.14)).

Shared cell is not possible for G1/G2 BTSs.

46 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



2.2 Add Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and9100 BTS

2.2.1 9110 Micro BTS/9110-E Micro BTS Applicability






BTS master/slave synchronization is possible for 9110 Micro BTS, but

only with another 9110 Micro BTS

BTS master/slave synchronization is possible for 9110-E Micro BTS, but

only with another 9110 Micro BTS/9110-E Micro BTS. The master is always

9110-E Micro BTS.

Abis via satellite is covered.

2.2.2 9100 Applicability

Possible scenarios are:





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, without

reconfiguring BTSs that are already installed. BTSs already onsite must

be 9100 BTSs.

It is possible to add a BTS to extend existing cells with reconfiguration of

BTSs already installed. Some sectors from the BTSs already onsite are

deleted and recreated in the new BTS.This case is part of the Add TRE on 9100 BTS procedure (refer toAlcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100 BTS: Add TRE ( Section 2.6) for more information).

2.2.2.1 Master/Slave Configuration

The following rules apply:

When the added BTS does not have sectors in the shared cell, it is

configured as the master.The configuration can be changed in a second step from master toslave (refer to G2 and Alcatel-Lucent 9100 BTS: Synchronize BTS Site Master/Slave (Section 2.14).

3BK 21269 AAAA PCZZA Ed.10 47 / 86

8/13/2019 212690000 e 10



BTS added with sectors in shared cell are in a slave configuration.

48 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



2.2.2.2 Abis via Satellite

Abis 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 the

case of a BTS in a shared cell

The configuration required for satellite is already prepared.

2.3 Delete G1/G2 BTS


The scenario applies to the following BTS:

G1 BTSs MKII BIUMD with DRFU

G2 BTSs with DRFU.

2.3.2 Applicability

The following scenarios are possible:

The deletion of several BTSs at the same time is allowed

The case of downstream BTSs is covered.

2.3.3 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 entering free running mode.

3BK 21269 AAAA PCZZA Ed.10 49 / 86

8/13/2019 212690000 e 10


8/13/2019 212690000 e 10



Some cells can be changed from monoband to multiband.

52 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



2.7 G1/G2 BTS: Delete TRE


This scenario applies to the following hardware:

G1 MKII BIUMD with DRFU

G2 all DRFU.

2.7.2 Applicability


It is applicable to configurations other than the low-loss configuration, which

implies antenna reconfiguration

Delete TRE is allowed as an individual action (change TRE from half-rate to

full-rate, modify FHS must be performed afterwards).

2.8 Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100BTS: Delete TRE



Delete TRE is allowed as a individual action (change TRE from half-rate to

full-rate, modify FHS must be performed afterwards)When deleting all TREs from the cabinet, apply the ’Delete BTS’ method.

Refer to Delete Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and

9100 BTS (Section 2.4).



It is possible to delete only TREs or TREs + RA

Delete TRE is allowed as a individual action (change TRE from half-rate to

full-rate, modify FHS must be performed afterwards).

3BK 21269 AAAA PCZZA Ed.10 53 / 86

8/13/2019 212690000 e 10



2.9 Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100BTS: Add Sector



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 monoband to multiband

Sector online commissioning is used.



New sector added on an existing BTS. A cell is created and mapped on it, or

an existing cell is linked to it to create a shared cell.

It is possible to change existing cells from monoband to multiband


2.10 Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100BTS: Remove Sector



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




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 the

sector to remove is a secondary one.

It is possible to delete a main sector from a cell after unlinking and deleting

the secondary sector

Changing the cell band from multiband to monoband is not requested


54 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



2.11 Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and9100: Reconfigure BTS TREs/Sectors

2.11.1 9110 / 9110-E Applicability

It is possible to combine Add/Delete TREs and Add/Remove Sectors on9110/9110-E BTS.

For mixed 9110/9110-E configurations, the following rules apply:

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

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

9110 not possible in lower Slave position

9110-E must be set as Master in 9110/9110-E mixed configurations.

2.11.2 9100 ApplicabilityIt is possible to combine Add/Delete TREs and Add/Remove Sectors onan 9100 BTS.

For example:

Three cells, each with four TREs mapped on one BTS are reconfigured to

three cells, each with six TREs mapped on two BTSs

Three cells, each with six TREs mapped on two BTS are reconfigured to

three cells, each with eight TREs, and one of the cells is shared between

the two BTSs.

3BK 21269 AAAA PCZZA Ed.10 55 / 86

8/13/2019 212690000 e 10



2.12 Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100BTS: Create/Reconfigure Multiband


Three 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 are

merged into one 900-1800 cell.







One 900 cell and one 1800 cell supported by sectors of the same BTS

are merged into one 900-1800 cell

One 850 cell and one 1900 cell supported by sectors of the same BTS

are merged into one 850-1900 cell

One 900 cell and one 1800 cell supported by sectors of two different BTSs

are merged into one 900-1800 cell.

One 850 cell and one 1900 cell supported by sectors of two different BTSs

are merged into one 850-1900 cell.

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

2.13 Alcatel-Lucent 9100 BTS: Upgrade with New Modules

Applicability

AN, SUM, and TRE Alcatel-Lucent modules are replaced with Evolutionmodules.

2.14 G2 and Alcatel-Lucent 9100 BTS: Synchronize BTS SiteMaster/Slave


G2 BTSs and 9100 BTSs are covered.

56 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



2.14.2 Applicability


Up to three G2 or 9100 slave BTSs can be synchronized on a master

G2 BTS

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

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

2.15 G2 and Alcatel-Lucent 9100 BTS: Desynchronize BTS SiteMaster/Slave

Hardware Coverage

G2 BTSs and 9100 BTSs are covered.

2.16 G1/G2 BTS: Replace BTS


The G1/G2 BTSs can be replaced with BTSs of any generation.

G1 BTS is no longer supported by the 9130 BSC Evolution.

It is possible 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 than or equal to the number of Abis

links needed for the new BTSs, use the ’Replace X BTS with Y BTS, Free

Abis Port’ method

If the number of free Abis ports is smaller than the number of Abis links

needed for the new BTSs, 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 characteristics remain unchanged.

3BK 21269 AAAA PCZZA Ed.10 57 / 86

8/13/2019 212690000 e 10



2.16.2 Master/Slave Configuration

For a master/slave configuration:

It is assumed that synchronized G2 BTSs are all replaced at the same

time. Otherwise, the operator must change the synchronization before

performing the BTS replacement. Refer to G2 and Alcatel- Lucent 9100 BTS: Synchronize BTS Site Master/Slave (Section 2.14) and G2 and

Alcatel-Lucent 9100 BTS: Desynchronize BTS Site Master/Slave (Section

2.15) for more information

The new BTSs can also be synchronized, but it is a prerequisite that the

hardware configuration for synchronization is already done.

2.16.3 Shared Cell

Shared cell applies to new BTSs if they are 9100 BTSs.

58 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



2.17 Alcatel-Lucent 9110 Micro BTS/9110-E Micro BTS and 9100BTS: Replace BTS


9110 Micro BTS/9110-E Micro BTSs can be replaced with BTSs of anygeneration.

It is allowable to replace X BTSs with Y BTSs at the same time:

X can be equal to Y




If replaced BTSs are on several Abis links and enough Abis ports are

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


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

All new BTSs are Alcatel-Lucent

The new BTSs are not in Master/Slave configuration.


Configuration:


hardware configuration for synchronization has already been done

Master/slave configuration is not possible between 9110 Micro BTS/9110-E

Micro BTS and 9100 BTSs.

2.17.1.2 Shared CellShared cell is not possible between 9110 Micro BTS/9110-E Micro BTSsand 9100 BTSs.

3BK 21269 AAAA PCZZA Ed.10 59 / 86

8/13/2019 212690000 e 10




9100 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 permissible to replace X BTSs with Y BTSs at the same time:

X can be equal to Y




If the number of free Abis ports is higher or equal to the number of Abis

links needed for the new BTSs, use the ’Replace X BTS with Y BTS, Free

Abis 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, Same

Abis Port’ method.



Configuration:

It is assumed that synchronized BTSs are all replaced at the same

time. Otherwise, the operator must change the synchronization before

performing the BTSs replacement. Refer to G2 and Alcatel-Lucent 9100 BTS: Synchronize BTS Site Master/Slave (Section 2.14) and G2 and

Alcatel-Lucent 9100 BTS: Desynchronize BTS Site Master/Slave (Section

2.15) for more information


hardware configuration for synchronization has already been done.

2.17.2.2 Shared Cell

Rules:

It 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 the

hardware 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 Alcatel-Lucent

The new BTSs are not in Master/Slave configuration.

60 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10


8/13/2019 212690000 e 10



2.20 9120/9130 BSC Evolution: Replace BSC

Applicability

The method installs, cables and commissions the new 9130 BSC Evolutionwithout disturbing the 9120 BSC.

The same procedure can be applied for rack shared configurations (two 9130BSC Evolution in the same rack or one 9130 BSC Evolution and one 9130MFS Evolution in the same rack).

No G1 BTSs must be connected to the 9120 BSC and no Qmux or R/S TS seton TS0 before replacement.

The following steps apply:

Backup software package on the 9120 BSC

New BSS package production and 9130 BSC Evolution functionality test

Removal of 9120 BSC

Cabling the new 9130 BSC Evolution

OMC-R configuration upgrade.

2.21 Move BSS: Different SGSN

Applicability

This 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

Through IP.

3BK 21269 AAAA PCZZA Ed.10 63 / 86

8/13/2019 212690000 e 10



2.22 Introduce GPRS


Supported MFS types:

The three types of 9135 MFS:

MFS with AS800

MFS with DS10 RC23

MFS with DS10 RC40.

9130 MFS Evolution


The 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 first

BTS of the Abis, i.e., all BTS on this Abis will use parameters adapted to

satellite connection (also valid for terrestrial connection).Different synchronization modes are supported:

For an 9135 MFS:

Central clock mode

Autonomous mode

GPU cascading.

For an 9130 MFS Evolution:

Central clock mode

Autonomous mode.

Note: For new installed MFS, only use the Central clock mode or Autonomous mode.

Physical TC extension must already be performed

In the case of an 9120 BSC, the following X.25 connection modes aresupported:

Connection via PSDN (BSC)

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

In the case of an 9130 BSC Evolution, the following IP connection modesare supported:

Connection via Ethernet LAN (BSC)


64 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



2.23 Delete GPRS




MFS with AS800

MFS with DS10 RC23

MFS with DS10 RC40.

9130 MFS Evolution.


Different synchronization modes are supported:

For an 9135 MFS:

Central clock mode

Autonomous mode

GPU cascading.


Central clock mode

Autonomous mode





Connection via an Ethernet LAN (BSC)

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

In the case of a shared rack with a split O&M link, the connection of the 9130MFS Evolution to the OMC-R is made through an 9130 BSC Evolution onthe Ater Mux.

3BK 21269 AAAA PCZZA Ed.10 65 / 86

8/13/2019 212690000 e 10



2.24 Extend/Reduce or Modify GPRS




MFS with AS800

MFS with DS10 RC23

MFS with DS10 RC40.

9130 MFS Evolution.


Both 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: 9135 MFS or 9130 MFS Evolution)


For an 9135 MFS:

Central clock mode

Autonomous mode

GPU cascading.


Central clock mode

Autonomous mode




66 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10






2.25 Extend 9120 BSC and Ater Mux Interface

Applicability


Extend 9120 BSC and Ater Mux Interface is performed to increase the

resources of 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, either terrestrialor satellite.

Note: For more information about introducing the Satellite feature, refer to Activate Ater Satellite (Section 2.39).

To extend the Ater Mux Interface, the BSC must have enough Ater Mux to

support the TC extension

Each BSC rack has to be connected to one (and only one) 9125 TC rack.

Note: If, for a BSC rack extension, the extended part of the BSC rack cannot beconnected to the same 9125 TC rack, perform a Move BSS, Different 9125 TC ( Section 2.37) procedure.

Three different Ater Mux extensions are supported:

Logical extension only

Physical extension only

Logical and physical extension.

3BK 21269 AAAA PCZZA Ed.10 67 / 86

8/13/2019 212690000 e 10



2.26 Extend 9130 BSC Evolution and Ater Mux Interface

Applicability


Extend 9130 BSC Evolution and Ater Mux Interface is performed to increase

the resources of the CS and PS

The extension is made through an Ater Mux extension for the TC and

through the insertion of boards (CCP and possibly LIUs) for the 9130

BSC 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, either terrestrialor satellite.

Note: For more information about introducing the Satellite feature, refer to Activate Ater Satellite (Section 2.39).

To extend the Ater Mux Interface, the BSC must have enough Ater Mux to

support the TC extension

The TC hardware has to be upgraded to a configuration compatible with the

target 9130 BSC Evolution

In the case where an 9130 BSC Evolution and an 9125 TC with TC

STM1-IP subrack are used, it is possible to transport E1 links on STM1.

See E1 to STM1 Configuration .

Three different Ater Mux extensions are supported:

Logical extension only

Physical extension only

Logical and physical extension.

68 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



2.27 Reduce 9130 BSC Evolution

Applicability

The reduction is made through the BTS (or TRE) move; these are mapped fromthe TCU of a CP-LOG to be removed to the TCU of CP-LOG that remains. Then

all the SBL(s) which are not in scope of the target configuration are removed.Note: The 9130 BSC to be reduced must be able to carry the traffic (a CCP is not able

to carry more than 900 erlangs). Also, the Abis-Hway-TP and Ater-Hway-TPto be removed must not be used.

2.28 Reduce 9120 BSC and Ater Mux Interface

Applicability

GPRS and MFS configuration remain the same. Ensure that this is the casebefore performing this scenario.

Reduce TC is covered.

2.29 Add/Delete PCM


Both MFS types are supported:

The two types of 9135 MFS:

MFS with AS800

MFS with DS10.

9130 MFS Evolution.




For an 9135 MFS:

Central clock mode

Autonomous mode

GPU cascading.


Central clock mode

Autonomous mode




3BK 21269 AAAA PCZZA Ed.10 69 / 86

8/13/2019 212690000 e 10






The following Ater Mux types are supported:

Direct

Mixed

Dedicated

Note: The "Delete PCM" scenario can be applied only if the PCM does not carrythe last GSL/GPU or the last N7.

70 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



2.30 Move Ater PCM


Both MFS types are supported:


MFS with AS800

MFS with DS10 RC23

MFS with DS10 RC40.

9130 MFS Evolution.



Both the BSS and the MFS are in service

If the PCM to move is the last PCM link of the last GPU/GP, use the ’Delete

GPU’ or ’Delete GP’ method

If the PCM to be moved is the first PCM link through the MFS, use one of

the following scenarios:

Add Logically a BSS to an MFS

Add a BSS by Moving Existing Links Through an MFS .

Different synchronization modes are supported:For an 9135 MFS:

Central clock mode

Autonomous mode

GPU cascading.


Central clock mode

Autonomous mode

Note: For new installed MFS, only use Central clock mode or Autonomous modes.

In the case of an 9120 BSC, different X.25 connection modes are supported:


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




3BK 21269 AAAA PCZZA Ed.10 71 / 86

8/13/2019 212690000 e 10



2.31 Add/Delete GPU


The three MFS types are supported:

MFS with AS800

MFS with DS10 RC23

MFS with DS10 RC40.




Central clock mode

Autonomous mode

GPU cascading.


In the case of an 9120 BSC, different X.25 connection modes are supported:



In the case of an 9130 BSC Evolution, the following IP connection modes

are supported:



2.32 Add/Delete GP


Supported MFS type: 9130 MFS Evolution.



For the MFS, different synchronization modes are supported:

Central clock mode

Autonomous mode.

72 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10




In the case of an 9120 BSC different X.25 connection modes are supported:






2.33 Move 9120 BSC, Same OMC-R




MFS with AS800

MFS with DS10 RC23

MFS with DS10 RC40.

9130 MFS Evolution.

MFS type change is covered.


Move BSS is an individual action (extension, reduction, and reconfiguration onGPRS, Network Element, or Transmission Links must be performed afterwards).


For an 9135 MFS:

Central clock mode

Autonomous mode

GPU cascading.


Central clock mode

Autonomous mode

Different X.25 extraction modes are supported:



3BK 21269 AAAA PCZZA Ed.10 73 / 86

8/13/2019 212690000 e 10



The following changes apply when Moving BSS from One MSC to Another:

Change the CRC

Change the SPC

Change the TC.

The target TC can be either:

G2 TC with ASMC/ATBX/DT16

G2 TC with MT120

9125 TC in a new rack

9125 TC in an existing rack.

Note: Moving a BSS from One MSC to Another can lead to introducing or removingsatellite links on the Ater Interface.

2.33.3 Satellite Link RulesRegarding satellite links, the following rules apply:

If there is a satellite link on the Abis, there cannot be a satellite link on

the Ater

In the BSC, the connection type attribute has to be modified (to terrestrial or

satellite) according to the link. This must be done before the Move BSS.

2.34 Move 9130 BSC Evolution, Same OMC-R




MFS with AS800

MFS with DS10 RC23

MFS with DS10 RC40.

9130 MFS Evolution.





For an 9135 MFS:

Central clock mode

Autonomous mode

GPU cascading.

74 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10




Central clock mode

Autonomous mode

Different IP extraction modes are supported:




Change the CRC

Change the SPC

Change the TC.



G2 TC with MT120




2.34.3 Satellite Link Rules

Regarding satellite links, the following rules apply:

If there is a satellite link on the Abis, there can be no satellite link on the Ater



2.35 Move 9120 BSC, Different OMC-R




MFS with AS800

MFS with DS10 RC23

MFS with DS10 RC40.

9130 MFS Evolution.


3BK 21269 AAAA PCZZA Ed.10 75 / 86

8/13/2019 212690000 e 10





The X.25 extraction mode remains the same as in the source OMC-R.


For an 9135 MFS:

Central clock mode

Autonomous mode

GPU cascading.


Central clock mode

Autonomous mode.

Different X.25 extraction modes are supported:




Change the CRC

Change the SPC

Change the TC.



G2 TC with MT120






the Ater



76 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



2.36 Move 9130 BSC Evolution, Different OMC-R




MFS with AS800

MFS with DS10 RC23

MFS with DS10 RC40.

9130 MFS Evolution.





For an 9135 MFS:

Central clock mode

Autonomous mode

GPU cascading.


Central clock mode

Autonomous mode

Different IP extraction modes are supported:




Change the CRC

Change the SPC

Change the TC.



G2 TC with MT120



3BK 21269 AAAA PCZZA Ed.10 77 / 86

8/13/2019 212690000 e 10



9125 TC with TC STM1-IP subrack




the Ater



2.37 Move BSS, Different 9125 TC

Applicability


For an 9120 BSC, different X.25 extraction modes are supported:



For an 9130 BSC Evolution, different IP extraction modes are supported:


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

Each BSC rack has to be connected to one (and only one) 9125 TC rack (notethat the 9125 TC has only one rack). When a BSC extension is needed andits dedicated Ater Mux cannot be plugged in the same 9125 TC rack, it isnecessary to first perform a move BSS from one 9125 TC to another, due to thefact that the 9125 TC is multi-BSS.

In case of an 9130 BSC Evolution, the associated TC can also be an 9125 TCequipped with TC STM1-IP subrack.

2.38 Merge TC

Applicability

The initial state can be either:

G2 TC

G2 TC and 9125 TC.

The final state will be 9125 TC/ 9125 TC equipped with TC STM1-IP subrack.

78 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



2.39 Activate Ater Satellite


BSS with or without GPRS support satellite links on the Ater side.




the Ater

All Ater links must have the same connection type (either terrestrial or

satellite).

2.40 Deactivate Ater Satellite

Applicability

No restriction.

2.41 Activate Abis Satellite


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

PCM-synchronized BTSs cannot support Abis Satellite Link.



If there is a satellite link on the Ater, there cannot be a satellite link on

the Abis

All Abis links do not need to have the same connection type.

2.42 Abis Satellite De-ActivationApplicability

No restriction.

3BK 21269 AAAA PCZZA Ed.10 79 / 86

8/13/2019 212690000 e 10



2.43 X.25

Applicability

X.25 extraction mode change:

Initial state: X.25 connection via PSDN (BSC)

Final state: X.25 connection via A Interface (MSC), through the MFS or not

G2 TC and 9125 TC are covered.

2.44 IP

Applicability

IP extraction mode change:

From Direct to Ater Mux

Initial state: IP connection via Ethernet LAN (BSC)Final state: IP connection via A Interface (MSC), through the MFS or not

From Ater-mux to Direct

Initial state: IP connection via A Interface (MSC), through the MFS or not

Final state: IP connection via Ethernet LAN (BSC)

G2 TC and 9125 TC are covered

The modification of the number of Ater links carrying IP is also covered

(increase or decrease number of TS used for O&M).

2.45 Modify Logical Parameters Using MLU

Applicability

The following can be modified in the network using massive logical update:

Frequency plan

Hopping mode

Logical parameters

Creation/deletion of adjacenciesCreation/deletion of external cells.

These modifications can be done in two ways:

By the OMC-R itself, according to Modify Logical Parameters with OMC-R

using MLU to modify a small number of parameters.

With an external tool, according to Modify Logical Parameters with External

Tool using MLU in the case of major frequency planning and modification,

when several cells or the whole (sub-)network are impacted. This type of

tool is also used to build the initial frequency plan. The tool must be able

to read the ACIE format.

80 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



When an external cell is impacted (i.e., BCCH modification), you must contactthe OMC-R controlling the external cell so that the appropriate changes arealso made.

9156 RNO is used to modify a small number of frequencies or logicalparameters. If the modification impacts cells that have handover relationships

with cells controlled by different OMC-Rs, 9156 RNO creates informationspecific for each OMC-R.

When the Massive Logical Update involves an MFS, the operator, by PRCactivation:

1. Must ask the MFS to process the radio configuration file downloaded bythe OMC-R after the successful download of the MLU packages sent tothe impacted BSCs.

2. Activate these MLU packages once the MFS has reported the successfulactivation of its radio configuration file.

2.46 Introduce LCS

Applicability

A minimum GPRS configuration is required for LCS activation on a BSS.

2.47 Delete LCS

Applicability

3BK 21269 AAAA PCZZA Ed.10 81 / 86

8/13/2019 212690000 e 10



2.48 Introduce E-GPRS

Applicability

The HSDS is the support of GPRS with coding schema CS1 to CS4 andE-GPRS with coding schema MCS1 to MCS9.

The followings describe the supported configuration:

E-GPRS cell is mapped on homogenous BTS with Evolution TRE (TRA),

CS3/CS4 cell is mapped on homogenous Alcatel-Lucent 9100 and Evolution

TRE (TRA)

Pseudo non hopping TRX are supported by BSC but not by the OMC-R

Single cell (and not concentric or multiband cell)

Full-Rate TRE.

2.49 Deactivate E-GPRSApplicability

No restriction.

2.50 Attach Secondary Abis

Applicability

The added BTS must be alone on primary Abis, in the end of chain position.

The restrictions are:

Cannot use SUMP

The G3 TRE cannot access the second Abis.

2.51 Detach Secondary Abis

Applicability

No restriction.

82 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10


3 Additional Information


This section provides information on the type of personnel who are expectedto perform network configuration tasks. It also provides an explanation ofthe terms that are used in the tasks.

3BK 21269 AAAA PCZZA Ed.10 83 / 86

8/13/2019 212690000 e 10



3.1 Personnel Profiles

Personnel with the profiles listed in the following table perform networkconfiguration tasks during a network modification scenario.

Personnel Profile Abbreviation

Network Modification Planner Schedules the networkmodification.

-

OMC-R operator Uses the OMC-R to definethe logical configuration to beapplied to a given BSS.

ope.

Commissioning technician Commissions the hardware,software and troubleshoots.

Com.

Installation technician Cables the BSS site. M/C

Table 5: Personnel Profiles for Network Modification

3.2 Terminology

The following terms are used in the network configuration tasks:

min. Duration of an operation in minutes.

sec. Duration of an operation in seconds.

Grouped Task Must be performed without stopping. Otherwise,the system is in an unstable state. Containsdetailed tasks.

Grouped TaskSequence

Provides a graphical representation of:

The sequence in which tasks are performed

Tasks that must be performed without stopping

(grouped tasks)

The site where tasks are performed

The synchronization points between sites.

Operation andMaintenance Outage(OM Out)

O&M outage in minutes. Besides telecomoutage and supervision outage, certain networkfunctionalities are not available. For example, it isnot possible to run a performance management

job.

Prerequisites Describes what the network must be equippedwith before you do the network modification.You cannot program the scenario unless theseoperations are executed. This includes PCM links,and so on.

84 / 86 3BK 21269 AAAA PCZZA Ed.10

8/13/2019 212690000 e 10



Restrictions Describes actions or configurations that are notallowed during the scenario.

Scenario A sequence of tasks that must be performed in aspecific order when the network is being modified.

Each scenario provides a high-level view of thetasks required for a given network modification.Tasks in a scenario are nested as macro anddetailed tasks.

Scheduling Describes the personnel, duration and site(s)needed to perform the modification.

Site-specific Information Describes the site-specific information you needto complete the scenario. This includes specificparameter values, such as Signaling Point Code(SPC), X.25 addresses, and so on.

Supervision Outage(Sup Out)

Supervision outage in minutes. Supervision of theimpacted part of the network is not possible.

Supplies Describe all the supplies needed for the networkmodification. Supplies are materials that areinstalled or left onsite.

Telecom Reduction (TelRed)

Describes the telecom reduction. The capacity ofthe system is reduced, but mobiles can still accessthe services.

Telecom Outage (Tel

Out)

Describes the site, nature and duration of the

telecom outage. Mobiles cannot access theservices.

Tools Describe all the tools needed for the networkmodification. Tools are materials that are used forthe modification but are not left onsite.

3BK 21269 AAAA PCZZA Ed.10 85 / 86

8/13/2019 212690000 e 10



BLANK PAGE BREAK

212690000 e 10

Documents