ALU B11 Features

Alcatel-Lucent GSM New New Feat Featur ures es in Release B11

BSS Document Concept Guide Release B11

3BK 21609 AAAA TQZZA Ed.23a

BLANK PAGE BREAK

Status

RELEASED

Short hort titl title e

Conc Co ncep eptt Gui Guide All rights reserved. reserved. Passing Passing on and copying copying of this document, document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent.

2 / 288


Contents

Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1

B11 B1 1 Feat Feature ures s Overv Overvie iew w . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 1.1 1.1 1.2

2

AMR Signal Signallin ling g Modific Modificati ations ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 2.1 2.2 2.2 2.3 2.3 2.4 2.5 2.5 2.6

2.7 2.7 3

3.7 3.7

4.7 4.7

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardw ardwar are e Co Cov verag erage e ................................................................ Featu eature re Activ ctivat atiion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Count ounter ers s and and Indi Indica cato tors rs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/O T/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appli pplica cab ble Docum ocumen ents ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

34 34 34 34 35 35 35 35 35


38 38 38 38 38 38 38 38 39

CS Pagin Paging g Coordi Coordinat nation ion in the BS BSS S Support Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 5.1 5.2 5.2 5.3 5.3 5.4 5.5 5.5 5.6

5.7 5.7 6

30 30 30 30 31 31 31 31 31

Avoid void Ping Ping-P -Pong ong betwee between n CS CS and and PS PS Zones Zones for DTM MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 4.1 4.2 4.2 4.3 4.3 4.4 4.5 4.5 4.6

5


Impro Improved ved Pack Packet et Connec Connectio tion n Configu Configurat rations ions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 3.1 3.2 3.2 3.3 3.3 3.4 3.5 3.5 3.6

4

Docum ocumen entt Stru Struc cture ture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 B11 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25


42 42 42 42 42 42 42 42 43

Migrat Migration ion and Softwa Software re Replac Replaceme ement nt Modifi Modificat cation ions s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 6.1 6.2 6.2 6.3 6.3 6.4 6.5 6.5 6.6

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardw ardwar are e Co Cov verag erage e ................................................................ Featu eature re Activ ctivat atiion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Count ounter ers s and and Indi Indica cato tors rs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/O T/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


46 46 46 46 46 46

3 / 288

Contents

6.7 6.7 7

BSS BS S Softwa Software re Manage Management ment Modific Modificati ations ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 7.1 7.2 7.2 7.3 7.3 7.4 7.5 7.5 7.6

7.7 7.7 8

8.7 8.7

9.7 9.7

10.7 10.7

52 52 52 52 52 52 52 52 52


54 54 54 54 54 54 54 54 54

Descrip ription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hard Ha rdwa ware re Co Cov verag erage e ................................................................ Featu eature re Acti Activ vatio ation n ................................................................. Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coun Co unte ters rs and and Indi Indica cato tors rs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/ LM T/OM OMC C HM HMII Up Upda date tes s ............................................................ 10.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.6 10.6..2 OMC OMC HM HMII Updat pdates es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appl Applic icab able le Do Docu cume ment nts s .............................................................

56 56 56 56 56 56 56 56 56

A5/3 A5/ 3 Ciph Cipherin ering g Algo Algorith rithm m Suppo Support rt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 11.1 11.2 11.2 11.3 11.3 11.4 11.5 11.5 11.6 11.6

11.7 11.7 12


Remov Removal al of the Suppo Support rt of BTS BTS with with DRFU DRFU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 10.1 10.2 10.2 10.3 10.3 10.4 10.5 10.5 10.6 10.6

11

48 48 48 48 48 48 48 48 49

AS 800 800 MFS MFS not not Suppo Supporte rted d in B1 B11 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 9.1 9.2 9.2 9.3 9.3 9.4 9.5 9.5 9.6

10


Lock Configuration Configuration Actions Actions during during SW Replacement Replacement Procedure Procedure in the OMC-R . . . . . . . . . . . . . . 51 8.1 8.2 8.2 8.3 8.3 8.4 8.5 8.5 8.6

9

6.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 6.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Appli pplica cab ble Docum ocumen ents ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46


60 60 60 60 60 61 61 61 61

Edit Edit n Adjace Adjacenci ncies es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

4 / 288


Contents

12.1 12.2 12.2 12.3 12.3 12.4 12.5 12.5 12.6 12.6

12.7 12.7 13

13.7 13.7

14.7 14.7

15.7 15.7


68 68 68 68 68 68 68 68 68


70 70 70 70 70 70 70 70 70

Clean Management Management of Reselection Reselection Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 16.1 16.2 16.2 16.3 16.3 16.4 16.5 16.5 16.6 16.6

16.7 16.7 17

66 66 66 66 66 66 66 66 66

Change Granularity Granularity for for Customizat Customization ion of BTS External External Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 15.1 15.2 15.2 15.3 15.3 15.4 15.5 15.5 15.6 15.6

16


Customizatio Customization n of BTS External External Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 14.1 14.2 14.2 14.3 14.3 14.4 14.5 14.5 14.6 14.6

15

64 64 64 64 64 64 64 64 64

Copy&P Copy&Past aste e of Data Data in OMC-R OMC-R Forms Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 13.1 13.2 13.2 13.3 13.3 13.4 13.5 13.5 13.6 13.6

14



72 72 72 72 72 72 72 72 72

New Ne w GSL GSL Count Counter ers s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 17.1 17.2 17.2 17.3 17.3 17.4 17.5 17.5

Descrip ription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hard Ha rdwa ware re Co Cov verag erage e ................................................................ Featu eature re Acti Activ vatio ation n ................................................................. Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coun Co unte ters rs and and Indi Indica cato tors rs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


74 74 74 74 74

5 / 288

Contents

17.6

17.7 18

18.7

19.7

20.7

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

82 82 82 82 82 82 82 82 82


84 84 84 84 84 84 84 84 85

TRX Dynamic Power Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 21.1 21.2 21.3 21.4 21.5 21.6

21.7 22

80 80 80 80 80 80 80 80 80

Centralized Licence Server and Time Validity for Optional Features . . . . . . . . . . . . . . . . . . . . . . . . . 83 20.1 20.2 20.3 20.4 20.5 20.6

21

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT / OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Load Indicators for OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 19.1 19.2 19.3 19.4 19.5 19.6

20

78 78 78 78

SEC Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 18.1 18.2 18.3 18.4 18.5 18.6

19

LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


88 88 88 88 88 88 88 88 89

Adjust of BTS Power Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 22.1 22.2 22.3 22.4 22.5 22.6

22.7

6 / 288


92 92 92 92 92 92 92 92 92


Contents

23

Support of Windows Vista for PC LMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 23.1 23.2 23.3 23.4 23.5 23.6

23.7 24

24.7

25.7

26.7

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

102 102 102 102 103 104 104 104 104


106 106 106 106 107 108 108 108 108

New ALMAP FM Module Replacing AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 27.1 27.2 27.3 27.4 27.5 27.6

27.7 28

98 98 98 98 98 99 99 99 99

A Signalling over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 26.1 26.2 26.3 26.4 26.5 26.6

27

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-Flex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 25.1 25.2 25.3 25.4 25.5 25.6

26

94 94 94 94 94 94 94 94 95

Support of TFO on NB-AMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 24.1 24.2 24.3 24.4 24.5 24.6

25



110 110 110 110 110 110 110 110 111

Inter-BSS NACC/ Inter-RAT NACC (3G- ->2G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 28.1 28.2 28.3

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114


7 / 288

Contents

28.4 28.5 28.6

28.7 29

29.7

30.7

31.7


122 122 122 122 123 123 123 123 123


126 126 126 126 126 126 126 126 126

STM1 on 9130 BSC Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 32.1 32.2 32.3 32.4 32.5 32.6

32.7 33

118 118 118 118 118 118 118 118 119

New OMC-R Restore Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 31.1 31.2 31.3 31.4 31.5 31.6

32


OMC-R Compatible with SAN Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 30.1 30.2 30.3 30.4 30.5 30.6

31

114 114 115 115 115 115

New SUN HW Platform for OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 29.1 29.2 29.3 29.4 29.5 29.6

30

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


128 128 128 129 129 129 129 129 130

Full Gb over IP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 33.1 33.2 33.3 33.4 33.5 33.6

8 / 288

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

132 132 132 132 132 132 132 132


Contents

33.7 34

Lock of Additional Optional Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 34.1 34.2 34.3 34.4 34.5 34.6

34.7 35

35.7

36.7

37.7

138 138 138 138 138 138 138 138 139


142 142 142 142 142 143 143 143 143


146 146 146 146 146 146 146 146 147

Antenna Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 38.1 38.2 38.3 38.4 38.5 38.6

38.7 39


Investigation Based on Permanent Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 37.1 37.2 37.3 37.4 37.5 37.6

38

134 134 134 134 134 134 134 134 135

Enhanced 2G to 3G FDD/TDD Cell Re-selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 36.1 36.2 36.3 36.4 36.5 36.6

37


Broadcast Other Value than CI in SYSINFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 35.1 35.2 35.3 35.4 35.5 35.6

36

Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132


150 150 150 150 150 150 150 150 151

Randomisation of Fill Bits in L2 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 39.1 39.2

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154


9 / 288

Contents

39.3 39.4 39.5 39.6

39.7 40

40.7

41.7

42.7


160 160 160 160 161 161 161 161 161


164 164 164 164 164 164 164 164 164

2 BTS Configuration within 2 Integrated SUMA Boards in 1 BTS Cabinet . . . . . . . . . . . . . . . . . . . 167 43.1 43.2 43.3 43.4 43.5 43.6

43.7 44

158 158 158 158 158 158 158 158 158

RMS Improvement: Increase of the 42 BCCH-BSIC Pairs Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 42.1 42.2 42.3 42.4 42.5 42.6

43


MC TRE Module Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 41.1 41.2 41.3 41.4 41.5 41.6

42

154 154 154 154 154 154 155

Introduction of CF F8 LMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 40.1 40.2 40.3 40.4 40.5 40.6

41

Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


168 168 168 168 168 168 168 168 168

MC-RRH 900 - 2G/3G - Different PA - Separate 2G and 3G carriers in same module . . . . . . . . . 169 44.1 44.2 44.3 44.4 44.5 44.6

10 / 288

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

170 170 170 170 170 171 171


Contents

44.7 45

Network Synchronization of Radio TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 45.1 45.2 45.3 45.4 45.5 45.6

45.7 46

46.7

47.7

48.7

178 178 178 178 188 190 190 191 191

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

196 197 197 197 197 197 197 198 198


200 200 200 200 200 200 200 200 201

Security Enhancements for IP Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 49.1 49.2 49.3 49.4 49.5 49.6

50


Layer 2 Network Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 48.1 48.2 48.3 48.4 48.5 48.6

49

174 174 174 174 174 174 174 174 174

Remote BTS NEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 47.1 47.2 47.3 47.4 47.5 47.6

48


IP Transport in the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 46.1 46.2 46.3 46.4 46.5 46.6

47

44.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

204 204 204 204 205 205 205 205

Logging of BTS Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 50.1 50.2

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208


11 / 288

Contents

50.3 50.4 50.5 50.6

50.7 51

51.7

52.7

53.7


214 214 214 214 214 214 214 214 215


218 218 218 218 218 218 218 218 218

IP Flow Separation at Physical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 54.1 54.2 54.3 54.4 54.5 54.6

54.7 55

210 210 211 211 211 211 211 211 211

Support of Sftp in the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 53.1 53.2 53.3 53.4 53.5 53.6

54


3G Search Prio Wrong in PMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 52.1 52.2 52.3 52.4 52.5 52.6

53

208 208 208 208 208 208 208

Ethernet Installation Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 51.1 51.2 51.3 51.4 51.5 51.6

52

Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


220 220 220 221 221 221 221 221 221

AMR WB Cell Load Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 55.1 55.2 55.3 55.4 55.5 55.6

12 / 288

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

224 224 224 224 225 225 225


Contents

55.7 56

Interworking with LTE in the Packet Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 56.1 56.2 56.3 56.4 56.5 56.6

56.7 57

57.7

58.7

59.7

234 234 234 234 235 235 235 235 235


238 238 238 238 239 239 239 239 239


242 242 242 242 242 243 243 243 243

MC-RRH 900 - 2G -2PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 60.1 60.2 60.3 60.4 60.5 60.6

60.7 61


Bidirectional Forwarding Detection (BFD) Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 59.1 59.2 59.3 59.4 59.5 59.6

60

228 228 228 229 231 231 231 231 231

Remove Mx Firmware from Hardware Status for MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 58.1 58.2 58.3 58.4 58.5 58.6

59


Remove Mx Firmware from Hardware Status for BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 57.1 57.2 57.3 57.4 57.5 57.6

58

55.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225


246 246 246 246 247 247 247 247 247

9130 BSC Evolution Availability Improvement. Weekly Standby Reset. . . . . . . . . . . . . . . . . . . . . . 249 61.1

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250


13 / 288

Contents

61.2 61.3 61.4 61.5 61.6

61.7 62

62.7

63.7

64.7


258 258 258 259 259 259 259 259 259


262 262 262 262 263 263 263 263 263

CS/PS Outage Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 65.1 65.2 65.3 65.4 65.5 65.6

65.7 66

254 254 254 254 255 255 255 255 255

BTS Synchronization Through NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 64.1 64.2 64.3 64.4 64.5 64.6

65


STM1 Bidirectional on 9125 TC Equipped with TC STM1-IP Subrack . . . . . . . . . . . . . . . . . . . . . . . . 257 63.1 63.2 63.3 63.4 63.5 63.6

64

250 250 250 250 251 251 251 251

Gb flex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 62.1 62.2 62.3 62.4 62.5 62.6

63

Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


266 266 266 266 266 267 267 267 267

OMCP-OMC Supervision Link Defense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 66.1 66.2 66.3 66.4 66.5 66.6

14 / 288

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

270 270 270 270 270 270


Contents

66.7 67

TP Init Auto Test Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 67.1 67.2 67.3 67.4 67.5 67.6

67.7 68

68.7

69.7


276 276 276 276 276 276 276 277 277


280 280 280 280 280 280 280 280 281

Improved Multi-GPU Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 70.1 70.2 70.3 70.4 70.5 70.6

70.7 71

274 274 274 274 274 274 274 274 274

MC-Modules hardware capacity licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 69.1 69.2 69.3 69.4 69.5 69.6

70


BSC Patch Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 68.1 68.2 68.3 68.4 68.5 68.6

69

66.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 66.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271


284 284 284 284 284 284 284 284 284

Iur-g interface with enhanced control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 71.1 71.2 71.3 71.4 71.5 71.6

71.7



286 286 286 287 288 288 288 288 288

15 / 288

Contents

16 / 288


Preface

Preface Purpose

Document Pertinence

This document describes the Alcatel-Lucent Release B11 GSM features. Note that some of the features may be unavailable on the system installed at your location. This document applies to Release B11 of the BSS. The following convention applies for a 9125 TC equipped with a TC STM1 IP subrack: TC STM1 interface board is also referred as TCIF TC STM1 IP interface board is also referred as TCIFI.

What’s New

In Edition 23a Description improvement in Feature Activation (Section 56.3).

In Edition 23 Iur-g interface with enhanced control plane (Section 71) was added.

In Edition 22 Descriptions improvement in following chapters: Hardware Coverage (Section 21.2) Hardware Coverage (Section 39.2).

In Edition 21 Description improvement inRemove Mx Firm ware from Hardware Status for MFS (Section 58).

In Edition 20 Description improvement in MC-RRH 900 - 2 G/3G - Different PA - Separate 2G and 3G carriers in same module (Section 44).


17 / 288

Preface

In Edition 19 Description improvements in IP Flow Separation at Physical Level (Section 54).

In Edition 18 Section Improved Multi-GPU Performance (Section 70) was added. Description improvements in MC-RRH 900 - 2G -2PA (Section 60) .

In Edition 17 Description improvement in 2 BTS Configura tion within 2 Integrated SUMA Boards in 1 BTS Cabinet (Section 43) and Remove Mx Firm ware from Hardware Status for MFS (Section 58). MC-Modules hardware capacity licensing (Section 69) was added.

In Edition 16 Description improvement in RMS Improveme nt: Increase of the 42 BCCH-BSIC Pairs Limit (Section 42).

In Edition 15 Description improvement in Remove Mx Firm ware from Hardware Status for MFS (Section 58).

In Edition 14 Description improvement performed in Interworking wit h LTE in the Packet Domain (Section 56)

In Edition 13 The following Introduction of CF F8 LMT (Section 40) was updated due to Introduction of CF F8 LMT introduction. Description improvement in STM1 Bidirectio nal on 9125 TC Equipped with TC STM1-IP Subrack (Section 63).

In Edition 12 Description improvement.

In Edition 11 Improvements were done in: AMR WB Cell Load Handling (Section 55) B11 Features (Section 1.2) Hardware Coverage (Section 52.2) IP Flow Separation at Physical Level (Section 54)

In Edition 10 Improvement done in Support of TFO on NB-AMR (Section 24) . The following MC TRE Module Introduction (Section 41) was updated due to MC TRE module introduction.

18 / 288


Preface

In Edition 09 New section BSC Patch Management (Section 68) was created. Improvement done in 3G Search Prio Wrong in PMO (Section 52) . Updates performed in Interworking with LTE in the Packet Domain (Section 56) .

In Edition 08 The following section were added: Gb flex (Section 62) STM1 Bidirectional on 9125 TC Equipped with TC STM1-IP Subrack ( Section 63) BTS Synchronization Through NTP (Section 64) .

In Edition 07 The Network Synchronization of Radio TS (Section 45) section was added. Description improvement in Description (Section 59.1).

In Edition 06 The section 9130 BSC Evolu tion Availability Improvement. Weekly Standby Reset. (Section 61) was added. The Randomisation of Fill Bits in L2 Messages (Section 39) was added. The Antenna Hopping (Section 38) was added.

In Edition 05 Improvement done in Adjust of BTS Power Level (Section 22) . Description improvement performed in Parameters (Section 56.4) New features for B11 MR3: Remove Mx Firmware from Hardware Status for BSC (Section 57) , Remove Mx Firmware from Hardware Status for MFS (Section 58)

In Edition 04 Description improvements made in: Counters and Indicators (Section 5.5) Customization of BTS External Alarms (Section 14) OMC HMI Updates (Section 19.6.2).

In Edition 03 Improvements were done in the following sections: IP Flow Separation at Physical Level (Section 54) Customization of BTS External Alarms (Section 14)

In Edition 02 Improvements were done in the following section Counters and Indicators ( Section 17.5)


19 / 288

Preface

This document contains information about the following new feature 3G Search Prio wrong in PMO in 3G Search Prio Wrong in PMO (Section 52) .

In Edition 01 First official release of the document.

20 / 288


Preface

Audience

This document is intended for personnel requiring a general overview of the Release B11 features, including: Technical Project Managers Support engineers Operators Client Help Desk personnel.

Assumed Knowledge

You must have a basic understanding of the following: Alcatel-Lucent operations and maintenance (O&M) concepts for GSM Network Management concepts and terminology.


21 / 288

Preface

22 / 288


1 B11 Features Overview

1 B11 Features Overview This section presents: The document structure An overview of the Release B11 features.


23 / 288


1.1 Document Structure For each feature, this document provides: Description A short overview of the feature. Hardware Coverage A description of the supported hardware. Feature Activation Lists the steps required to use the feature. Parameters Counters and Indicators LMT/OMC HMI Updates Lists the new or modified windows in the LMT or OMC-R: LMT Updates OMC-R HMI Updates. Applicable Documents Lists associated documents.

24 / 288



1.2 B11 Features The following table presents the Release B11 feature list and the associated Maintenance Release. B11 Feature List

B11 MR Number

AMR Signalling Modifications (Section 2)

MR1

Improved Packet Connection Configurations (Section 3)

MR1

Avoid Ping-Pong between CS and PS Zones for DTM MS (Section 4)

MR1

CS Paging Coordination in the BSS Support (Section 5)

MR1

Migration and Software Replacement Modifications (Section 6)

MR1

BSS Software Management Modifications (Section 7) :

MR1

Single command for launching SW migration operations, per BSC Single screen for managing all operations for SW replacement (with multiple selections) Automatic report at end of the migration. Lock Configurati on Actions during SW Replacement Procedure in the OMC-R (Section 8)

MR1

AS 800 MFS not Supported in B11 (Section 9)

MR1

Removal of the Support of BTS with DRFU (Section 10)

MR1

A5/3 Ciphering Algorithm Support (Section 11)

MR1

Edit n Adjacencies (Section 12)

MR1

Copy&Paste of Data in OMC-R Forms (Section 13)

MR1

Customization of BTS External Alarms (Section 14)

MR1

Clean Management of Reselection Links (Section 16)

MR1

New GSL Counters (Section 17)

MR1

SEC Command Line Interface (Section 18)

MR1

Load Indicators for OMC-R (Section 19)

MR1

Centralized Licence Server and Time Validity for Optional Features ( Section 20)

MR1

TRX Dynamic Power Saving (Section 21)

MR1

Support of Windows Vista for PC LMT (Section 23)

MR1

Support of TFO on NB-AMR (Section 24)

MR1


25 / 288


B11 Feature List

B11 MR Number

A-Flex (Section 25)

MR1

A Signalling over IP (Section 26)

MR1

New ALMAP FM Module Replacing AS (Section 27)

MR1

Inter-BSS NACC/ Inter-RAT NACC (3G- ->2G) (Section 28)

MR1

New SUN HW Platform for OMC-R (Section 29)

MR1

OMC-R Compatible with SAN Architecture (Section 30)

MR1

New OMC-R Restore Strategy (Section 31)

MR1

STM1 on 9130 BSC Evolution (Section 32)

MR1

Full Gb over IP Option (Section 33)

MR1

Lock of Additional Optional Features (Section 34)

MR1

Broadcast Other Value than CI in SYSINFO (Section 35)

MR1

Enhanced 2G to 3G FDD/TDD Cell Re-selection (Section 36)

MR1

Investigation Based on Permanent Measurements (Section 37)

MR1

Fast Traffic Handover on G1 TRX (*)

MR1

SS7 clear request during establishment phase (*)

MR1

New counters of discarded messages (NE request) (*)

MR1

MFS Defence and Investigation Facilities (P0)

MR1

Export of EML MFS aspects like equipment (GPU) (*)

MR1

Export interface for User Logs (*)

MR1

Parameter Dictionary: Description of operational impacts during parameter modifications

MR1

Additional operational information in GCD feature descriptions (***)

MR1

GCD Counter and Indicator Dictionary: Additional information for each counter and indicator on the related feature

MR1

Documentation of all system, feature and procedure changes in the new release (***)

MR1

Ethernet Installation Kit

MR1

CMCC Q3 interface (*)

MR1

Ilog 5.1 introduction due to 5.0 EOL (*)

MR1

26 / 288



B11 Feature List

B11 MR Number

SUMx remote firmware upgrade (*)

MR1

Support of Sftp in the OMC (Section 53)

MR1

Adaptation of TD/SYT capacity tools for production (*)

MR1

On-Demand loading (**)

MR1

Support of TC redundancy (manual operation)

MR1

IP Flow Separation at Physical Level (Section 54)

MR1

Phase 1: AsigOIP Tel and O&M flow separated on 2 different ports. Investigation based on permanent measurements

MR1

Adjust of BTS Power Level (Section 22)

MR1

Antenna Hopping (Section 38)

MR1Ed2

Randomisation of Fill Bits in L2 Messages (Section 39)

MR1Ed2

MC TRE Module Introduction (Section 41)

MR1Ed2

RMS Improvement: Increase of the 42 BCCH-BSIC Pairs Limit ( Section 42)

MR1Ed2

2 BTS Configura tion within 2 Integrated SUMA Boards in 1 BTS Cabinet (Section 43)

MR1Ed2

MC-RRH 900 - 2 G/3G - Different PA - Separate 2G and 3G carriers in same module (Section 44)

MR1Ed3

Gb flex (Section 62)

MR3

BTS Synchronization Through NTP (Section 64)

MR3

IP over Ethernet on Abis and Ater in IP Transport in the BSS (Section MR3 46) Remote BTS NEM (Section 47)

MR3

Layer 2 Network Access (Section 48)

MR3

Security Enhancements for IP Introduction (Section 49)

MR3

Logging of BTS Temperature (Section 50)

MR3

Remote switching BTS Abis connection

MR3

PM differentiation Packet User Traffic/Signalling, GPRS/EDGE

MR3

3G Search Prio Wrong in PMO (Section 52)

MR3/MR1Ed2

AMR WB Cell Load Handling (Section 55)

MR3


27 / 288


B11 Feature List

B11 MR Number

Interworking with LTE in the Packet Domain (Section 56)

MR1Ed2/MR3

Remove Mx Firmware from Hardware Status for BSC (Section 57)

MR1Ed2/MR3

Remove Mx Firmware from Hardware Status for MFS (Section 58)

MR1Ed2/MR3

Change Granularity for Customization of BTS External Alarms ( Section 15)

MR3

Bidirectional Forwarding Detection (BFD) Protocol (Section 59)

MR3

MC-RRH 900 - 2G -2PA (Section 60)

MR3Ed1

BSC Patch Management (Section 68)

MR1Ed2

9130 BSC Evolu tion Availability Improvement. Weekly Standby Reset. (Section 61)

MR1Ed2

STM1 Bidirectional on 9125 TC Equipped with TC STM1-IP Subrack ( Section 63)

MR1Ed2

CS/PS Outage Detection (Section 65)

MR1Ed2

OMCP-OMC Supervision Link Defense (Section 66)

MR1Ed2

TP Init Auto Test Improvements (Section 67)

MR1Ed2/MR3

Introduction of CF F8 LMT (Section 40)

MR1Ed2

MC-Modules hardware capacity licensing (Section 69)

MR1Ed2.1

Iur-g interface with enhanced control plane (Section 71)

MR1Ed2.2

(*)

: This feature does not impact Customer Documentation.

(**)

: The feature description can be found in MUSE Customer Documentation.

(***)

: This feature’s purpose is the creation of this document.

Table 1: Release B11 Feature List

28 / 288


2 AMR Signalling Modifications



29 / 288


2.1 Description When an AMR (NB or WB) speech codec is used in the TCH, to reduce the ACCH signalling error rate in poor radio conditions, “Repeated Downlink FACCH” and “Repeated SACCH” functionalities are used (FACCH and SACCH are sent twice).

2.2 Hardware Coverage The feature is supported only by the 9130 BSC Evolution.

2.3 Feature Activation For specific information about the feature activation, refer to the Network Reconfiguration Recommendations , to AMR Signalling Modifications .

2.4 Parameters This section contains the new and modified parameters involved in feature deployment.

30 / 288

Name

New

EN_REP_DL_FACCH

New

REP_DL_FACCH_LEGACY_SUPPORT

New

REP_DL_FACCH_THRES_AMR_FR

New

REP_DL_FACCH_THRES_AMR_HR

New

REP_DL_FACCH_THRES_AMR_WB

New

EN_REP_SACCH

New

RADIOLINK_REP_DL_SACCH

New

L_RXQUAL_UL_P_AMR_RXACCH

New

L_RXQUAL_DL_P_AMR_RXACCH

New

REP_DL_SACCH_THRES

New

REP_DL_SACCH_WS

New

REP_UL_SACCH_THRES

New

REP_UL_SACCH_WS

New



2.5 Counters and Indicators This section contains the new counters involved in feature deployment. Counter ID

Counter Name

MC990

NB_MS_REPEATED_ACCH_CAPABLE

MC991

NB_CALLS_RFACCH_ACTIVATED

MC992

NB_CALLS_RSACCH_ACTIVATED

MC993

NB_AMR_TCH_DROP_RLF_TRX

MC994

NB_AMR_TCH_DROP_RLF_TRX_RSACCH

MC995

NB_AMR_TCH_DROP_OUT_HO_TRX

MC996

NB_AMR_TCH_DROP_OUT_HO_TRX_RFACCH

2.6 LMT/OMC HMI Updates 2.6.1 LMT Updates There are no LMT modifications.

2.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , to “REPEATED ACCH” Window .

2.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Online Help 9153 OMC-R Functional and Graphical Evolutions Network Reconfiguration Recommendations .


31 / 288


32 / 288


3 Improved Packet Connection Configurations



33 / 288


3.1 Description This feature improves the current MFS bias mechanism in terms of ping performance and EDA configurations usage.

3.2 Hardware Coverage The feature is not NE dependent.

3.3 Feature Activation For specific information about the feature activation, refer to Network Reconfiguration Recommendations , to Improved Packet Connection Configurations .

3.4 Parameters This section contains the new and modified parameters involved in feature deployment. Name

New

EN_FULL_FAST _USF_UL_EXTENDED

Flag to enable / disable the full fast scheduling mode for uplink TBFs in EUTM. Values can be: 0-disable 1-enable

FULL_FAST_USF_UL_EXTENDED

Duration of the full fast USF scheduling phase for an UL TBF in EUTM, during which the UL TBF in EUTM may be scheduled on all its PDCHs (instead of on only one). It is expressed in number of successive block periods (20 ms).

EN_EXTENDED _UL_TBF

Flag to disable/enable the extended TBF mode feature on the uplink. Values can be: 0 if EUTM mode is not used 1 if EUTM mode is used 2 if I-EUTM is used (improved EUTM mode).

IEUTM_MAX _IDLE_PERIOD

Maximum duration of UL TBF inactivity before MS is polled in EUTM mode when EN_EXTENDED _UL_TBF is set ot 2 (IEUTM enabled).

BIAS_LIMIT

Transfer ratio above which the bias of the transfer is deemed as uplink (otherwise downlink).

34 / 288



Name

New

N_POLLING_EUTM_LIMIT

Maximum number of consecutive polling requests that can be sent to a MS in EUTM state (when EN_EXTENDED _UL_TBF is set on 2 (IEUTM enabled)) without receiving a polling response in a PCA.

T_MAX _EXTENDED_UL

Maximum duration of the extended uplink TBF phase.

3.5 Counters and Indicators There are no counter and indicator modifications.


3.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , to: RNUSM: Edit BSS Telecom Parameters - Radio Res. Mngt. View RNUSM: Edit Cell Window - Radio Res. Ctrl View .



35 / 288


36 / 288


4 Avoid Ping-Pong between CS and PS Zones for DTM MS



37 / 288


4.1 Description When a transition DTM to Dedicated mode occurs (DL/UL TBF release), a Handover cause 30 can be triggered to move the corresponding RTS (which handles CS) from the “PS traffic zone” to the “CS traffic zone”. This way frees the Radio Resources for further PS transactions. The aim of the feature is to delay the handover execution to avoid ping-pong between the CS and PS zone, if the mobile enters DTM again before the delay has expired.

4.2 Hardware Coverage The feature is not supported on 9120 BSC, but only by 9130 BSC.

4.3 Feature Activation The feature is not optional. For specific information about the feature activation, refer to Network Reconfiguration Recommendations , to Avoid Ping Pong between CS and PS Zone .


New

N_DELAYED_HO_CAUSE30

New

4.5 Counters and Indicators Counter ID

Counter Name

MC482

NB_TCH_HO_REQ_30_ABORTED


4.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , to "GENERAL HO CONTROL" Window .

38 / 288





39 / 288


40 / 288


5 CS Paging Coordination in the BSS Support



41 / 288


5.1 Description Without paging coordination, CS Paging messages are always broadcast through the CCCH/PCH channel, even if the MS is in PTM mode. The support of paging coordination improves CS paging performances. It allows to broadcast CS Paging messages through the PDCH/PACCH. It is mandatory to fully support the DTM feature.


5.3 Feature Activation For specific information about the feature activation, refer to Network Reconfiguration Recommendations , to Support of Paging Coordination in the BSS .


New

EN_BSS_PAGING_COORDINATION (BSC)

New

EN_BSS_PAGING_COORDINATION (MFS)

New


Counter Name

P390a

NB_BSS_CS_PAGING_REQ_GPU

P390b

NB_CS_PAGING_REQ_PACCH


5.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , to "GPRS GENERAL" Window .

42 / 288





43 / 288


44 / 288


6 Migration and Software Replacement Modifications



45 / 288


6.1 Description The features deal with the following topics: Performing, during MFS migration operation, the first steps of the BSC migration method, including downloads. The overall migration is better scheduled. Launching PM jobs after launching the activation of the new BSS software and before the audits. The resolution concerns the OMC-R internal software. Downloading software in all 9130 BSCs Evolutions found in one OMC-R in parallel, whatever the OMC-R size. No longer stopping the running PMC on the BSCs during migration or software change.

6.2 Hardware Coverage The features are partially dependent on the 9130 BSC Evolution. Evolution.

6.3 Feature Activation The features are not optional.

6.4 Parameters There are no parameter parameter modifications. modifications.

6.5 Counters and Indicators There are no counter counter and indicator modifications modifications..

6.6 LMT/OMC HMI Updates 6.6.1 LMT Updates There are no LMT modifications. modifications.

6.6.2 OMC HMI Updates There are no OMC HMI modifications.

6.7 Applicable Documents The following documents are impacted by the feature: B10/B11 MFS/TC/BSS Software Migration B11/B11 MFS/TC/BSS Software Replacement.

46 / 288


7 BSS Software Management Modifications



47 / 288


7.1 Description This feature brings the following modifications: A single command command for launching launching a series of previousl previously y selected selected actions required required for the BSS software software change A single screen for managing all operations for the software replacement (with multiple selections) that allows a better view of all the software changes changes in progress progress An automatic report at end of the migration that offers a quick and easy view view of the BSS state after the software change in comparison with its initial state (before the software software change). change).

7.2 Hardware Coverage The features are supported for both 9120 BSC and 9130 BSC Evolution. Evolution.

7.3 Feature Activation The features are not optional.

7.4 Parameters There are no parameter parameter modifications. modifications.



7.6.2 OMC HMI Updates For specific specific information about the OMC HMI, refer to 9153 OMC-R Functional and Graphical Evolutions , to BSSUSM : Software Management .

48 / 288



7.7 Applicable Documents The following documents are impacted by the feature: B10/B11 MFS/TC/BSS Software Migration B11/B11 MFS/TC/BSS Software Replacement. 9153 OMC-R Functional and Graphical Evolutions 9153 OMC-R Online Help BSS Configuration Handbook Operations & Maintenance Principles.


49 / 288


50 / 288


8 Lock Configuration Actions during SW Replacement Procedure in the OMC-R



51 / 288


8.1 Description The feature consists of locking any configuration actions, either from SC or from PRC during the software replacement procedure. This lock begins from the moment when the software package is generated until the end of the audit following the software activation. The lock applies for all BSCs managed by the OMC-R, whether they are involved in the software replacement operation or not.

8.2 Hardware Coverage The feature is supported regardless of the station on which the OMC-R is installed.

8.3 Feature Activation The feature is not optional.

8.4 Parameters There are no parameter modifications.




8.7 Applicable Documents The following documents are impacted by the feature: B10/B11 MFS/TC/BSS Software Migration B11/B11 MFS/TC/BSS Software Replacement.

52 / 288


9 AS 800 MFS not Supported in B11



53 / 288


9.1 Description Starting with B11, the AS800 MFS is no longer supported. All documents that refer to this type of MFS must be updated.

9.2 Hardware Coverage Not applicable.

9.3 Feature Activation The feature is mandatory in Release B11, therefore there is no activation scenario.

9.4 Parameters There are no new or modified parameters.




9.7 Applicable Documents The following documents are impacted by the feature: 9135 MFS Maintenance Handbook 9135 MFS Software Installation Network Reconfiguration Recommendations 9135 MFS Description BSS Configuration Rules 9130 MFS Evolution Commissioning Manual.

54 / 288


10 Removal of the Support of BTS with DRFU



55 / 288


10.1 Description Starting with B11, the G1 and G2 BTSs are no longer supported. All documents that refer to these types of BTS must be updated.

10.2 Hardware Coverage Not applicable.

10.3 Feature Activation There is no activation scenario for this feature.





10.7 Applicable Documents The following GCD documents are impacted by the feature: BSS Preventive Maintenance Handbook Network Reconfiguration Recommendations Engineering Rules for LMT BSS Configuration Rules Operations & Maintenance Principles BSS Overview BSS Methods Handbook BTS Alarm Dictionary 9153 OMC-R Functional and Graphical Evolutions 9153 OMC-R Online Help

56 / 288



The following methods are impacted by the feature: Move BTS/Abis, Different BSC, Different OMC-R Move BTS/Abis in Same BSC Move Several Abis Links from a BSC to Another, Same OMC-R Replace X BTS with Y BTS, Free Abis Port Replace X BTS with Y BTS, Same Abis Port Reconfigure TRE/Sectors, A9100 BTS Reconfigure TRE/Sectors, Monoband to Multiband Cell Delete TRE from Equipped A9100 BTS Synchronize BTS Master / Slave Site Desynchronize BTS Master / Slave Site .


57 / 288


58 / 288


11 A5/3 Ciphering Algorithm Support



59 / 288


11.1 Description A5/3 is a new ciphering algorithm specified first for UMTS, and now also defined for GSM. It is used for circuit switched channels.

11.2 Hardware Coverage The feature is supported only for G4 / G5 TRE (TDM or IP BTS). If the feature is activated for G3 TRE, A5/1ciphering it is used for this TRE.

11.3 Feature Activation For specific information about the feature activation, refer to the Network Reconfiguration Recommendations , to Support of A5/3 Ciphering Algorithm .


New

CELL_CIPH_SET

New

TRX_CIPH_CAP

New

TRE_CIPH_CAP

New

11.5 Counters and Indicators This section contains the new counters involved in feature deployment.

60 / 288

Counter ID

Counter Name

MC951

NB_TCH_A5_3_REQ

MC952

NB_CIPHER_CMD_A5_3

MC953

NB_SUCC_CIPHER_CMD_A5_3

MC954

NB_TCH_A5_3_ASS

MC955

NB_TCH_A5_3_ASS_NO_TRX

MC956

NB_ASS_HO_CMD_A5_3_NO_TRX




11.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions . The following sections are updated: RNUSM: Network Information Window RNUSM: Edit Cell Window BSSUSM: Modify BTS Characteristics Window .

11.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Online Help 9153 OMC-R Functional and Graphical Evolutions Network Reconfiguration Recommendations BSS Overview .


61 / 288


62 / 288


12 Edit n Adjacencies



63 / 288


12.1 Description This feature allows the user to modify one or more adjacency parameters on several adjacencies in one shot (in a similar way as it is currently done with the edit n-cells facility).






12.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , toRNUSM Edit N Adjs Window .

12.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Online Help 9153 OMC-R Functional and Graphical Evolutions BSS Configuration Handbook .

64 / 288


13 Copy&Paste of Data in OMC-R Forms



65 / 288


13.1 Description The aim of this feature is to provide a better mechanism for Copy & Paste in the USM windows, and make all text boxes and objects editable. In the USM windows all text fields, which do not have an interactor attached, are available for highlight. Using this highlight,the copy/paste mechanism is extended to all parameters and field names.




13.5 Counters and Indicators There are no counters and indicators improvements.

13.6 LMT/OMC HMI Updates 13.6.1 LMT Updates There are no LMT HMI improvements

13.6.2 OMC HMI Updates The OMC HMI updates can be followed in 9153 OMC-R Functional and Graphical Evolutions .

13.7 Applicable Documents The impacted document by the feature is 9153 OMC-R Functional and Graphical Evolutions

66 / 288


14 Customization of BTS External Alarms



67 / 288


14.1 Description This feature provides more flexibility to customers to declare the external alarms on BTSs. The solution consists in offering several profiles per BTS type for declaring the external alarms.


14.3 Feature Activation The feature is optional. For specific information about the feature activation, refer to the BSS Configuration Handbook .

14.4 Parameters This section contains the new parameter involved in the feature deployment. Name

New

En_CustExtAlmBts

New


14.6 LMT/OMC HMI Updates 14.6.1 LMT Updates There are no LMT modifications

14.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions .

14.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Functional and Graphical Evolutions 9153 OMC-R Online Help BSS Surveillance Handbook Operations & Maintenance Principles 9153 OMC-R Getting Started .

68 / 288


15 Change Granularity for Customization of BTS External Alarms

15 Change Granularity for Customization of BTS External Alarms Note: This feature is available starting with B11 MR1Ed2 release.


69 / 288

15 Change Granularity for Customization of BTS External Alarms

15.1 Description This feature is alocated per number of BTSs for which external alarm profile is not set to the default profile. This is a limited feature. If the number of BTSs for which the external alarm profile is not the default one, exceeds the limit alocated by contract, the centralized license server rejects any configuration which requests other BTSs to use non-default profiles.


15.3 Feature Activation The feature is optional. For specific information about the feature functionality, refer to the BSS Surveillance Handbook .


15.5 Counters and Indicators There are no new or modified counters and indicators


15.6.2 OMC HMI Updates The OMC HMI updates can be followed in 9153 OMC-R Functional and Graphical Evolutions

15.7 Applicable Documents The following documents are impacted by the feature: Network Reconfiguration Recommendations BSS Surveillance Handbook . 9153 OMC-R Functional and Graphical Evolutions

70 / 288


16 Clean Management of Reselection Links



71 / 288


16.1 Description This feature improves the process of reselection retrieval, as is the case for the HO links.


16.3 Feature Activation The feature activation is made virtually in the OMC-R.


New

Link-Type-2G

New




16.7 Applicable Documents The BSS Overview is impacted by the feature.

72 / 288


17 New GSL Counters

17 New GSL Counters


73 / 288

17 New GSL Counters

17.1 Description This feature provides new counters related to the GSL interface in order to ease the BSCGP protocol dimensioning for both possible configurations: terrestrial and satellite configurations.

17.2 Hardware Coverage Depending on the transport mode: The TDM mode is available on G2/MX BSC and on Legacy/MX MFS The IP mode is available on MX BSC and Legacy/MX MFS.

17.3 Feature Activation The feature is optional.


17.5 Counters and Indicators New counters exist at the BSCGP application level to configure the window size and acknowledgement timer: For BSC: nb_UL_GSL_messages UL_GSL_messages_max UL_GSL_messages_avg. For MFS: nb_DL_GSL_messages DL_GSL_messages_max DL_GSL_messages_avg.

74 / 288


17 New GSL Counters

The following table presents the new GSL counters for a BSC in TDM or IP mode. Counter ID for BSC in TDM/IP Mode

Counter Name

BSC_3_L1.5

NB_LAPD_ RNR_SENT

BSC_3_L1.6

NB_LAPD_ RNR_REC

BSC_3_L1.12

NB_LAPD_ CRC_ERROR

BSC_3_L1.16

TIME_LAPD_UNAVAIL

BSC_3_L1.17

NB_LAPD_EST

BSC_3_L1.18

NB_LAPD_CONG

BSC_IP24l

MAX_NB_MSG_SENT

Table 2: GSL Counters for BSC in TDM/IP Mode The following table presents the new GSL counters for a MFS in TDM or IP mode. Counter ID for MFS in TDM/IP Mode

Counter Name

MFS_1_1

Nb_GSL_msg_sent

MFS_1_2

Nb_GSL_msg_discarded

MFS_1_4

Cumul_full_ongoingA

MFS_1_4bis

Cumul_full_ongoingB

MFS_1_5

Nb_GSL_msg_resent

MFS_2_1

Nb_GSL_msg_received

MFS_2_2

Nb_GSL_channel_req_ received

MFS_5_P547m

Max_Nb_Kb_sent

MFS_5_P547l

Max_Nb_Msg_sent

Table 3: GSL Counters for MFS in TDM/IP Mode The following table presents the new PS counters:


Counter ID

Counter Name

P7a

NB_BSCGP_MSG_SENT

P7b

NB_BSCGP_MSG_DISCARDED

75 / 288

17 New GSL Counters

Counter ID

Counter Name

P7c_1

CUMULATED_TIME_ONGOING_QUEUE_A_FULL

P7c_2

CUMULATED_TIME_ONGOING_QUEUE_B_FULL

P7d

NB_BSCGP_MSG_RESENT

P7e

NB_BSCGP_MSG_RECEIVED

P7f

NB_BSCGP_CHANNEL_REQ_RECEIVED

P7g

NB_BSCGP_BYTES_SENT

P7h

MAX_NB_BSCGP_BYTES_SENT

P7i

MAX_NB_BSCGP_MSG_SENT

P9a

NB_DL_TBF_NORM_REL_EGPRS

P22a

NB_UL_TBF_NORM_REL_EGPRS

P30e

NB_UL_TBF_EST_SUCC_EGPRS_MStransDL

P62e

NB_UL_TBF_EST_REQ_EGPRS_MStransDL

P90h

NB_DL_TBF_EST_SUCC_EGPRS_MS_Transfer_UL

P90i

NB_DL_TBF_EST_SUCC_EGPRS_T3192

P91h

NB_DL_TBF_EST_REQ_EGPRS_MS_Transfer_UL

P91i

NB_DL_TBF_EST_REQ_EGPRS_T3192

P181a

NB_DL_TBF_REL_SIG

P181b

NB_UL_TBF_REL_SIG

Table 4: PS counters Note: The following counters are MR3 only: The following table presents the PS counters for MR3:

76 / 288

Counter ID

Counter Name

P505a

NB_DTM_DL_TBF_EST_REQ_EGPRS

P506a

NB_DTM_DL_TBF_EST_SUCC_EGPRS

P507a

NB_DTM_UL_TBF_EST_REQ_EGPRS

P508a

NB_DTM_UL_TBF_EST_SUCC_EGPRS


17 New GSL Counters

Counter ID

Counter Name

P509a

NB_DTM_CS_DL_TBF_RELEASE_EGPRS

P510a

NB_DTM_CS_UL_TBF_RELEASE_EGPRS

Table 5: PS couters for MR3


77 / 288

17 New GSL Counters



17.7 Applicable Documents The document impacted by the feature is Quality of Service Alerters User Guide .

78 / 288


18 SEC Command Line Interface



79 / 288


18.1 Description This feature allows the users to centralize their user management. SEC provides a Command Line Interface. This interface offers all necessary for access right management (user profiles, OAD, FAD).





18.6 LMT / OMC HMI Updates 18.6.1 LMT Updates There are no LMT modifications.

18.6.2 OMC HMI Updates There are not OMC HMI updates.

18.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Getting Started 9153 OMC-R Command Mode .

80 / 288


19 Load Indicators for OMC-R



81 / 288


19.1 Description This feature is intended as a useful tool for system administrators to help troubleshoot different SOLARIS and applications problems; the tool is also useful to indicate the system load.






19.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , to OMC-R Load Indicators Window .

19.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Network Administration Handbook 9153 OMC-R Functional and Graphical Evolutions .

82 / 288


20 Centralized Licence Server and Time Validity for Optional Features



83 / 288


20.1 Description This component can be installed on every OMC-R, or on another Unix machine. The license server use a limits file (similar to the current oflcf) in order to store the allowed upper limits of the configured units quantities. The server displays the current status of the optional features for the all involved OMC-Rs, like oflcf for a single OMC in RNUSM



20.4 Parameters Name

New

Validity-date

New



20.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , to DSMUSM Window .

84 / 288



20.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Functional and Graphical Evolutions B11/B11 9153 OMC-R Software Replacement B10/B11 9153 OMC-R Software Migration 9153 OMC-R Network Administration Handbook 9153 OMC-R Methods Handbook Optional Features Activation on Running 9153 OMC-R 9153 OMC-R Installation Site Preparation Sheet.


85 / 288


86 / 288


21 TRX Dynamic Power Saving



87 / 288


21.1 Description This feature reduces BTS power consumption. The solution consists in switching off the Power Amplifier (PA) bias of a TRX as soon as several consecutive timeslots are not used in DL on this TRX.

21.2 Hardware Coverage The feature is not supported by MC TRE only by G3, G4 and G5 TRE.

21.3 Feature Activation For specific information about the feature activation, refer to Network Reconfiguration Recommendations , to TRX Dynamic Power Saving .


New

EN_POWER_SAVING

New


Counter Name

MC957

TIME_TS_BUSY

MC958

TIME_PA_BIAS_ON


21.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , to RNUSM: Edit Cell View .

88 / 288



21.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Online Help 9153 OMC-R Functional and Graphical Evolutions Network Reconfiguration Recommendations BSS Overview BSS Configuration Rules .


89 / 288


90 / 288


22 Adjust of BTS Power Level



91 / 288


22.1 Description This feature allows setting the maximum transmission power used at cell level per BTS cabinet.



22.4 Parameters Name

New

BS_TXPWR_ATTENUATION

New

BS_TXPWR_ATTENUATION_INNER

New



22.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , to RNUSM: Edit Cell View .

22.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Online Help 9153 OMC-R Functional and Graphical Evolutions BSS Overview Replace Non Alcatel-Lucent BTS with Alcatel-Lucent BTS .

92 / 288


23 Support of Windows Vista for PC LMT



93 / 288


23.1 Description Windows Vista can be used as the Operating System for the PC LMT.

23.2 Hardware Coverage Windows Vista required more resource then Windows XP / 2000. The minimum resource requirements by Windows Vista are: 1 gigahertz (GHz) 32-bit (x 86) processor or 1 GHz 64-bit (x 64) processor 1 GB of system memory 128 MB of graphics memory (minimum) 40-GB hard disk that has 15 GB of free hard disk space.




23.6 LMT/OMC HMI Updates 23.6.1 LMT Updates Some components of the PC LMT must be updated to support and to work properly with Windows Vista.


94 / 288



23.7 Applicable Documents The following documents are impacted by the feature: 9125 TC Commissioning Manual 9125 TC Acceptance Manual 9130 BSC Evolution Software Installation 9110-E Micro BTS Commissioning Manual 9135 MFS Software Installation 9130 MFS Evolution Commissioning Manual BSS Methods Handbook 9135 MFS Maintenance Handbook BTS NEM User Guide 9130 MFS Evolution IMT User Guide 9135 MFS IMT User Guide 9125 Transcoder NEM User Guide TC Corrective Maintenance Handbook 9130 BSC Evolution Terminal User Guide 9130 BSC Evolution Maintenance Handbook 9130 BSC Evolution NEM User Guide BSS Configuration Rules Engineering Rules for LMT Move BTS/Abis in Same BSC .


95 / 288


96 / 288


24 Support of TFO on NB-AMR



97 / 288


24.1 Description The Tandem Free Operation (TFO) is a call configuration where a transcoder device is physically present in the signal path, but the transcoding functions are bypassed. Adaptive Multiple Rate (AMR) increases the quality of speech during conversations and also increases the offered capacity due to the provision of half-rate channels. To support TFO on NB-AMR, HR_AMR and FR_AMR is a prerequisite.

24.2 Hardware Coverage TRAU G2 MT 120, G2.5 MT 120 supports TFO on NB-AMR if upgraded. TRAU G2.5 MT 120-WB does not support TFO on NB-AMR in Release B11. TFO on NB-AMR is supported only by a 9130 BSC Evolution.

24.3 Feature Activation To activate TFO on NB-AMR, refer to the Network Reconfiguration Recommendations , to Support of TFO on NB-AMR .


New

PREF_CONFIG_FR_AMR_NB

New

PREF_CONFIG_HR_AMR_NB

New

EN_TFO_AMR_NB

New

EN_TFO_MATCH

Modified

24.5 Counters and Indicators The TFO for AMR-NB introduces the following BSC counters.

98 / 288

Counter ID

Counter Name

MC938

NB_CALL_TFO_AMR_WB

MC939

NB_HO_INTER_TFO_AMR_WB

MC950

NB_HO_EXT_TFO_AMR_WB




24.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to the 9153 OMC-R Functional and Graphical Evolutions , to TFO Window and AMR Window .

24.7 Applicable Documents The following documents are impacted by the feature: Network Reconfiguration Recommendations 9153 OMC-R Functional and Graphical Evolutions BSS Configuration Rules 9153 OMC-R Online Help BSS Overview .


99 / 288


100 / 288


25 A-Flex

25 A-Flex


101 / 288

25 A-Flex

25.1 Description The A-Flex feature allows a BSC to connect to more than one MSC. One BSC connects up to 16 MSC servers. When A-Flex is applied, one or more MSC serve a CS pool-area, but only one of these MSC serves each individual MS. The A-Flex feature does not work with core network sharing. One and only one MSC Server always controls an interface circuit. The A-Flex feature requires the A signalling over IP feature.

25.2 Hardware Coverage The feature is implemented only in the case of: 9130 BSC Evolution A non-Legacy MSC.

25.3 Feature Activation To activate A-Flex, refer to the Reconfigure BSC/MSC .


102 / 288

Name

New

EN_A_FLEX

New

MSC SBL number

New

MSC_SPC

New

MSC_CN_ID

New

NRI_LIST

New

NRI_LENGTH

New

PLMN Name

New

MSC_MCC

New

MSC_MNC

New

MIN_NB_ACTIVE_IPSP

New

MSC Name (local to the OMC)

New

MSC_WEIGHT

New


25 A-Flex

Name

New

OFFLOADED

New

NULL_NRI

New

25.5 Counters and Indicators A-Flex introduces the following BSC counters. Counter ID

Counter Name

C8e

NB_CS_PAGING_with_IMSI (TRX)

MC8e

NB_CS_PAGING_with_IMSI (Cell)

MC980

NB_INIT_L3_MSG_PAGING_RESPONSE_NRI

MC981

NB_INIT_L3_MSG_IMSI_DETACH_IND_NRI

MC982

NB_INIT_L3_MSG_CM_RE_ESTABL_REQ_NRI

MC983

NB_INIT_L3_MSG_IMSI_ATTACH_NRI

MC984

NB_INIT_L3_MSG_LOC_UPD_NRI

MC985a

NB_INIT_L3_MSG_CM_SERV_REQ_SMS_NRI

MC985b

NB_INIT_L3_MSG_CM_SERV_REQ_SUP_SERV_NRI

MC985c

NB_INIT_L3_MSG_CM_SERV_REQ_CALL_EST_NRI

MC985d

NB_INIT_L3_MSG_CM_SERV_REQ_LOC_SERV_NRI

MC985e

NB_INIT_L3_MSG_CM_SERV_REQ_OTHERS_NRI

MC986

NB_TIMES_MSC_SELECTION_NRI

MC987

NB_TIMES_MSC_SELECTION_IMSI

MC988

NB_TIMES_MSC_SELECTION_LB

A-Flex introduces the following MFS counter.


Counter ID

Counter Name

P53d

NB_CS_PAGING_WITH_GLOBAL_CN_ID_PCH

103 / 288

25 A-Flex


25.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to the 9153 OMC-R Functional and Graphical Evolutions , to BSSUSM: BSS Parameters .

25.7 Applicable Documents The following GCD documents are impacted by the feature: Network Reconfiguration Recommendations 9153 OMC-R Functional and Graphical Evolutions BSS Configuration Rules 9153 OMC-R Online Help BSS Overview BSC and TC Alarm Dictionary Which Scenario to Use. The following FPD documents are impacted by the feature: Reconfigure BSC/MSC Add a New BSS on OMC-R Replace 9120 BSC with 9130 BSC Evolution Move 9130 BSC Evolution without MFS, Different MSC, Same OMC-R Move 9130 BSC Evolution, Same MFS, Different MSC, Same OMC-R Move 9130 BSC Evolution, Different MFS, Different MSC, Same OMC-R Move 9130 MFS Evolution with Associated BSS, Different OMC-R Move 9130 BSC Evolution Without MFS, Same MSC, Different OMC-R Move 9130 BSC Evolution, Different MFS, Same MSC, Different OMC-R Move 9130 BSC Evolution, Different MFS, Different MSC, Different OMC-R Move 9130 BSC Evolution, Different MFS, Same MSC, Same 9153 OMC-R .

104 / 288


26 A Signalling over IP



105 / 288


26.1 Description This feature is one of the solutions for the BSS to be connected to the NGN network. The purpose of this feature is to transfer the SS7 signaling over the IP network between the BSC and NGN core network. The benefits of this feature are the following: Improvement of the signaling transfer reliability and lower transfer delay Higher signalling transfer bandwidth Simple network configuration and flexible network construction It supports multi remote SS7 end points to be connected to BSC. The feature is an optional feature, and the A-signalling over TDM is still supported. TDM mode and IP mode are exclusive.

26.2 Hardware Coverage The feature is implemented only in the case of: 9130 BSC Evolution A non-Legacy MSC.

26.3 Feature Activation To activate A Signalling over IP, refer to Modify N7 Transport Mode for 9130 BSC Evolution .


106 / 288

Name

New

MSC SBL number

New

MSC_SPC

New

MSC_CN_ID

New

NRI_LIST

New

NRI_LENGTH

New

PLMN Name

New

MSC_MCC

New

MSC_MNC

New

MIN_NB_ACTIVE_IPSP

New



Name

New

MSC Name (local to the OMC)

New

MSC_WEIGHT

New

OFFLOADED

New

NULL_NRI

New

MSC IP Address

New

MSC Secondary IP Address

New

MSC Port Number

New

BSC IP Address

New

EN_ASIG_ OVER_IP

New

BSC Port Number

New

ASIG_SCTP_ENDPOINT_IP_Address_1

New

ASIG_SCTP_ENDPOINT_IP_Address_2

New

ASIG_SCTP_ENDPOINT_LIST

New

ASIG_SCTP_ENDPOINT_PORT

New

START_TELECOM_IP_ADDRESS_BSC

New

TELECOM_IP_SUBNET_MASK_BSC

New

M2UA_TC_IP_ADDRESS

New

M2UA_TC_IP_ADDRESS

New

26.5 Counters and Indicators A-Flex introduces the following BSC counters.


Counter ID

Counter Name

MC1101

NB_ASPUP_TX

MC1102

NB_ASPUP_RX

MC1103

NB_ASPDOWN_TX

MC1104

NB_ASPDOWN_RX

MC1105

NB_ASPACTIVE_TX

107 / 288


Counter ID

Counter Name

MC1106

NB_ASPACTIVE_RX

MC1107

NB_ASPINACTIVE_TX

MC1108

NB_ASPINACTIVE_RX

A Signalling over IP does not introduce any MFS counter.

26.6 LMT/OMC HMI Updates 26.6.1 LMT Updates For specific information about the LMT modifications, refer to Modify IP Parameters , in the 9130 BSC Evolution Terminal User Guide .


26.7 Applicable Documents The following GCD documents are impacted by the feature: Network Reconfiguration Recommendations 9153 OMC-R Functional and Graphical Evolutions BSS Configuration Rules 9153 OMC-R Online Help BSS Overview BSC and TC Alarm Dictionary Which Scenario to Use. The following methods are impacted by the feature: Modify N7 Transport Mode for BSC Evolution Move 9130 BSC Evolution without MFS, Different MSC, Same OMC-R Move 9130 BSC Evolution, Same MFS, Different MSC, Same OMC-R Move 9130 BSC Evolution, Different MFS, Different MSC, Same OMC-R Move 9130 MFS Evolution with Associated BSS, Different OMC-R Move 9130 BSC Evolution Without MFS, Same MSC, Different OMC-R Move 9130 BSC Evolution, Different MFS, Same MSC, Different OMC-R Move 9130 BSC Evolution, Different MFS, Different MSC, Different OMC-R Move 9130 BSC Evolution, Different MFS, Same MSC, Same 9153 OMC-R .

108 / 288


27 New ALMAP FM Module Replacing AS



109 / 288


27.1 Description Starting with Release B11, the ASUSM is replaced by FM. AS (Current Alarms) is replaced by FM (Current Alarms) in the iconbox. AS (Historical Alarms) is replaced by FM (Historical Alarms) in the iconbox. MFSUSM, RNUSM and BSSUSM are updated to invoke FM (Current Alarms) and FM (Historical Alarms) instead of AS.


27.3 Feature Activation The feature is not optional. There is no activation scenario for this feature.




27.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to the 9153 OMC-R Functional and Graphical Evolutions , to: FM Current Alarms Window FM Historical Alarms Management Window .

110 / 288



27.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Getting Started Alarm Call Out User Guide 9153 OMC-R Functional and Graphical Evolutions BSS Surveillance Handbook Operations & Maintenance Principles BTS Alarm Dictionary BSS Overview BSC & TC Alarm Dictionary MFS Alarm Dictionary Quality of Service Alerters User Guide 9125 Transcoder Alarm Dictionary .


111 / 288


112 / 288


28 Inter-BSS NACC/ Inter-RAT NACC (3G- ->2G)



113 / 288


28.1 Description This feature is commercially optional and its activation is managed through the EN_RIM_NACC parameter at BSS level. The feature optionally is managed on by a TRX quantity basis, by considering the feature as PS related.


28.3 Feature Activation The feature is optional. For specific information about the feature activation, refer to the Network Reconfiguration Recommendations , to Inter-BSS NACC/ Inter-RAT NACC (3G- ->2G).

28.4 Parameters This section contains the new and modified parameters involved in feature deployment. This field/button

Lets you

EN_RIM_NACC

Enables inter-BSS NACC and inter-RAT NACC

T_RIM_RIR

Timer supervising reception of RAN Information

T_RIM_RI

Timer supervising reception of RAN information ACK

T_RIM_MULTIPLE_REPORT

Timer supervising reception of following RAN information with multiple report

N_RIM_RETRIES

Number of retries of a RAN procedure is sent before giving up (in case of no answer)

T_RIM_DISABILITY_CELL

Timer supervising the disability of the External Adjacent cell context when information not available

28.5 Counters and Indicators

114 / 288

Counter ID

Counter Name

P182a

NB_SERVING_INTER_BSS_NACC

P182b

NB_SERVING_INTER_RAT_NACC

P182c

NB_CONTROLLING_INTER_BSS_NACC

P182d

NB_RAN_INFO_REQ_INTER_BSS_NACC

P182e

TIME_RIM_NACC_PROC_SUCC




28.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , to RNUSM: RIM-NACC View .

28.7 Applicable Documents The following documents are impacted by the feature: Network Reconfiguration Recommendations 9153 OMC-R Functional and Graphical Evolutions BSS Configuration Rules BSS Overview 9153 OMC-R Online Help .


115 / 288


116 / 288


29 New SUN HW Platform for OMC-R



117 / 288


29.1 Description The OMC-R HW configurations based on SunFire V490 + SE3510 are replaced by M4000 + ST2540. The Sun SPARC Enterprise M4000 server gives two dual-core 2.4 GHz SPARC64 VII processors. M4000 was introduced due to a series of key benefits: Higher single-system performance for very large workloads Increased reliability, availability, serviceability Faster I/O and increased I/O connectivity Safe application portability as it fits into the existing environment. The Sun StorageTek 2540 Array contains disk drives for storing data and controllers that provide the interface between a management and/or data host and the disk drives. The Sun StorageTek 2540 Array provides a Fibre Channel connection from the data host to the controller. There are two key features for ST2540: Fibre Channel (FC) controller tray Two data host connectors per controller that support a fiber-optic interface with 1, 2, or 4 Gb/s data host connection speed.

29.2 Hardware Coverage The Ultra 24 workstation is used for M4000 configuration. The disk bay ST2540 is added for Large, X-Large, and XX-Large configurations.

29.3 Feature Activation For M4000 configuration and OMC-R installation on the M4000 machine, refer to 9153 OMC-R Installation.



29.6 LMT/OMC HMI Updates 29.6.1 LMT Updates No updates.

29.6.2 OMC HMI Updates No updates.

118 / 288



29.7 Applicable Documents The following documents are impacted by the feature: Cabling Description for SUN Servers 9153 OMC-R Installation LEGATO Installation and User Guide 9153 OMC-R Network Administration Handbook 9153 OMC-R Getting Started 9153 OMC-R Methods Handbook 9153 OMC-R Reconfigure Platform B11/B11 9153 OMC-R Software Replacement B10/B11 9153 OMC-R Software Migration 9153 OMC-R Acceptance Tests.


119 / 288


120 / 288


30 OMC-R Compatible with SAN Architecture



121 / 288


30.1 Description Storage Area Networks (SANs) represent the latest stage in the evolution of mass data storage for enterprises and other large institutions. A SAN is a storage networking architecture that enables the more efficient use of storage assets by decoupling server and storage capacities with a dedicated network. This feature can be also used to move the application(s) directory to external FC storage. Key advantages introduced by a SAN architecture: Reduces overall cost of storage management High availability Any-to-any connectivity Frees server capacity Reduces LAN congestion Storage not dedicated to one server Increases data transfer rates Enables server-less and LAN-less backup File sharing.

30.2 Hardware Coverage The client must have the SAN infrastructure which is compatible with Solaris 10: Storage hardware: disk arrays Fiber Channel switch: not mandatory for small configurations Fiber Channel cables SAN management software (usually bundled with the disk array). The OMC-R machine must have one or more FC HBA installed which can be also one of the current HBA used now in configurations with direct attached storage. The following types of storage hardware can be used for SAN architecture: SE 3510 ST 2540.

30.3 Feature Activation The methods 9153 OMC-R Installation and 9153 OMC-R Network Administration Handbook contain information about SAN compatibility with 9153 OMC-R.


122 / 288






30.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Installation 9153 OMC-R Network Administration Handbook B10/B11 9153 OMC-R Software Migration B11/B11 9153 OMC-R Software Replacement Cabling Description for SUN Servers


123 / 288


124 / 288


31 New OMC-R Restore Strategy



125 / 288


31.1 Description This feature improves the backup/restore time and CPU usage. This feature permits to avoid multiple copies of big database files. It is possible to avoid the full backup/restore and to use instead only the incremental facility, based on the fact that the machine is installed from start with DVD1, DVD2 and DVD3 on both backup and restore. Using a central server for backup/restore is used to manage more efficiently the storage implementing a method to delete old files that are no longer needed at restore. Moving data between the server and clients is done using operating system services.

31.2 Hardware Coverage The DVD1 and patches from DVD2 are hardware dependant, 3PP from DVD2 and packages are machine type dependant (master, agent, etc.) and customizations are machine type and hardware dependant.

31.3 Feature Activation To perform a restore, the same installation steps as for the OMC installation must be performed, and at the end, before the OMC start, an incremental restore must be done to obtain the same machine as it was after the last backup. Starting from the end of DVD installation and customization, all the modifications are saved as an incremental backup.





31.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Network Administration Handbook LEGATO Installation and User Guide .

126 / 288


32 STM1 on 9130 BSC Evolution



127 / 288


32.1 Description In order to decrease the cost of the transport in the BSS, Alcatel-Lucent provides an alternative solution to the TDM transport, STM1 (Synchronous Transport Mode level 1) in the SDH (Synchronous Digital Hierarchy) network. STM1 can transport larger amounts of telephone calls and data traffic over the same fiber wire without synchronization problems, using lasers or light-emitting diodes (LED). The basic unit of framing in SDH is the STM1 (Synchronous Transport Module level 1) and operates at 155.52 Mbit/s, used in GSM solely for the transport of E1 links. Each E1 link is transported transparently (using asynchronous mapping) in one VC12 container. One STM1 link can contain up to 63 VC12 containers. So, one STM1 can carry 63 Abis and/or Ater, each E1 of 2048 kbps is transported separately on one VC12 container. Four STM1 interfaces can be connected on the front plate of the new TPGSMv3 board BSC and 63 E1 Abis/Ater per interface make that all 252 E1 links to be transported on STM1. Using STM1, the 9130 BSC Evolution can be configured without a LIU shelf. Mixed configuration, LIU-E1 and VC12-E1 is supported. The benefits offered by this feature are: Reduces the cabling effort Reduces the space needed for cables and distribution frames Simplifies cabling/assignment changes Reduces cost on transmission equipment Increases reliability and availability.

32.2 Hardware Coverage This feature is available only for 9130 BSC Evolution equipped with TPGSMv3 boards.

32.3 Feature Activation The feature is optional. For specific information, refer to Activate/Deactivate STM1 Interface for 9130 BSC Evolution .

128 / 288




New

Max-Number-STM1-Interface

New

BSC-STM1-VC12-Identifier

New

BSC-STM1-Interface-identifier

New

LIU-Shelf-Present

New

BSC-SECTION-TRACE-TYPE

New

BSC-SECTION-TRACE-ONEBYTE-TRANSMITTED

New

BSC-SECTION-TRACE-STRING-TRANSMITTED

New

BSC-SECTION-TRACE-ONEBYTE-RECEIVED

New

BSC-SECTION-TRACE-STRING-RECEIVED

New

BSC-LOW-PATH-TRACE-TRANSMITTED

New

BSC-LOW-PATH-TRACE- RECEIVED

New

BSC-HIGH-PATH-TRACE-TRANSMITTED

New

BSC-HIGH-PATH-TRACE- RECEIVED

New

BSC-CLOCK-PREFERRED

New


32.6 LMT/OMC HMI Updates 32.6.1 LMT Updates The LMT modifications are in the 9130 BSC Evolution Terminal User Guide .

32.6.2 OMC HMI Updates The OMC HMI Updates are in the 9153 OMC-R Functional and Graphical Evolution .


129 / 288


32.7 Applicable Documents The following documents are impacted by the feature: BSS Overview 9130 BSC Evolution Hardware Description 9130 BSC Evolution Maintenance Handbook 9130 BSC Evolution Terminal User Guide 9130 BSC Evolution Functional Description BSS Configuration Handbook Network Reconfiguration Recommendation 9153 OMC-R Functional and Graphical Evolutions BSC and TC Alarm Dictionary Move BSS from One 9125 TC to Another Move 9130 BSC Evolution without MFS, Different MSC, Same 9153 OMC-R Move 9130 BSC Evolution, Same MFS, Different MSC, Same 9153 OMC-R Move 9130 BSC Evolution, Different MFS, Different MSC, Same 9153 OMC-R Move 9130 BSC Evolution, Different MFS, Different MSC, Different 9153 OMC-R Extend 9130 BSC Evolution Reduce 9130 BSC Evolution Add a New BSS on 9153 OMC-R Move BTS/Abis, Different BSC, Same 9153 OMC-R Move BTS/Abis, Different BSC, Different 9153 OMC-R Move BTS/Abis in Same BSC Move Several Abis Links from a BSC to Another, Same 9153 OMC-R Add BTS, New Cell(s) Extend Ater Mux Interface Reduce Ater Mux Interface BSS Configuration Rules 9130 MFS/BSC Evolution Installation Manual BSS O&M Routing Configurations STM1 on 9130 BSC Evolution .

130 / 288


33 Full Gb over IP Option



131 / 288


33.1 Description This feature is sold according to a number of TRX. If the operator exceeds the number of TRX allocated by contract, the creation and application of a new configuration is refused at the next PRC activation. The full Gb over IP option is available, starting with the current release.







33.7 Applicable Documents The following documents are impacted by the feature: Network Reconfiguration Recommendations 9153 OMC-R Functional and Graphical Evolutions .

132 / 288


34 Lock of Additional Optional Features



133 / 288


34.1 Description All the optional features are sold according to a number of TRX. A checking mechanism is implemented at OMC level, in order to limit the number of TRX configured with a certain optional feature. If the operator exceeds the number of TRX configured with a certain optional feature, the creation and application of a new configuration is refused at the next PRC activation. The following features are added in the list of optional features: Multi PLMN Extended Cell A-bis per satellite A-Ter per satellite SMS-CB Basic LCS.






34.6.2 OMC HMI Updates The OMC HMI Updates are in the 9153 OMC-R Functional and Graphical Evolution document, section RNUSM: Network Information Window

134 / 288



34.7 Applicable Documents The following documents are impacted by the feature: Network Reconfiguration Recommendations 9153 OMC-R Functional and Graphical Evolutions


135 / 288


136 / 288


35 Broadcast Other Value than CI in SYSINFO



137 / 288


35.1 Description Some companies build data bases including the association between the cell reference of some PLMN and geographical positioning information. For example, for CI information broadcast on SYSINFO 3 and 6, there are some applications that are able to request the MS position from the centralized data base. In order to limit the impact on their business, operators request that another parameter than the CI is broadcast in SI.


35.3 Feature Activation The feature is NOT commercially optional. The feature is activated by a dedicated parameter at the cell level which contains the CI value to be broadcast on SYSINFO messages. The new parameter is exchanged on the OMC-BSC interface. When set to “0”, it indicates that the feature is deactivated.


New

CI_SI

New



35.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to the 9153 OMC-R Functional and Graphical Evolutions , to RNUSM: Edit Cell Window .

138 / 288



35.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Functional and Graphical Evolutions . 9153 OMC-R Online Help BSS Overview Add BTS, New Cell(s).


139 / 288


140 / 288


36 Enhanced 2G to 3G FDD/TDD Cell Re-selection



141 / 288


36.1 Description This feature allows the user to choose between using 2G to 3G FDD or TDD cell re-selction with: Up to 3 UARFCN defined at BSC level Up to 8 UARFCN defined at cell level (per serving cell).

36.2 Hardware Coverage The feature is supported for serving cells mapped on Evolium ® Alcatel-Lucent BTSs. The following limitations apply: For a G2 BSC, the maximum number of 3G cells which can be defined is 900 and the maximum number of 3G adjacencies is 1960 For a 9130 BSC Evolution, the maximum number of 3G cells which can be defined is 1700 and the maximum number of 3G adjacencies is 3700.



New

RAT_3G

New

UARFCN

New for TDD Modified for FDD

TDD_ARFCN_LIST

Modified

EN_3G_DIVERSITY(FDD)

Modified

Adjacency type

Modified

EN_FAST_3G_RESELECTION

Modified


142 / 288




36.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to the 9153 OMC-R Functional and Graphical Evolutions .

36.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Functional and Graphical Evolutions BSS Overview 9153 OMC-R Online Help BSS Configuration Handbook .


143 / 288


144 / 288


37 Investigation Based on Permanent Measurements



145 / 288


37.1 Description The feature is to reduce the accumulation period of type 110 to 15 minutes for only one BSC at a time during a limited period. It is possible to reduce the accumulation period only for type 110 that is used only in Permanent Measurement Campaign. The feature could not be activated for another type. To limit risk of overload in OMC-R and NPO, for a given network take in consideration the following : only one BSC could have a reduced accumulation period at a time it is also possible to reduce the accumulation period only during two hours. It is not possible to define a reduced accumulation period out of a recording interval (the first one or the second one).

37.2 Hardware Coverage The feature is supported only by the 9130 BSC Evolution.



New

BSS identifier

New

Reduced Accumulation Period

New




146 / 288



37.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Functional and Graphical Evolutions 9153 OMC-R Online Help


147 / 288


148 / 288


38 Antenna Hopping

38 Antenna Hopping Note: This feature is available starting with MR1Ed2.


149 / 288

38 Antenna Hopping

38.1 Description Description Antenna Antenna hopping means that the sequence sequence of bursts bursts comprising a radio block block are transmitted transmitted over more than one antenna. The purpose is to get diversity diversity of the radio path to the mobile. In conjunction with frequency hopping, the number of paths provided by frequency hopping can be multiplied with the number of antennas involved in the antenna antenna hopping. hopping. The feature is intended intended to be provided by the twin module, and thus the number number of antennas for antenna hopping is two.

38.2 Hardware Coverage The feature is available on 9120 BSC and 9130 BSC Evolution only for the BTS equipped with TWIN TRE.

38.3 Feature Activation The feature is optional and can be activated at cell level. For specific information, refer to Network Reconfiguration Recommendations , section Antenna Hopping .


New

EN_ANTENNA_HOPPING

New

TXDIV_CAPABILITY

Modified




150 / 288


38 Antenna Hopping

38.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Functional and Graphical Evolutions BSS Configuration Rules 9153 OMC-R Online Help Network Reconfiguration Recommendations BTS Alarm Dictionary 9100 BTS/9110 Micro BTS Functional Description BSS Overview Add BTS, New Cell(s) Add TRE to Equipped 9100 BTS .


151 / 288

38 Antenna Hopping

152 / 288


39 Randomisation of Fill Bits in L2 Messages

39 Randomisation of Fill Bits in L2 Messages Note: This feature is available starting with MR1Ed2.


153 / 288


39.1 Description The feature decreases the risks of hacking on the Air Interface by replacing fixed sequences of fill bits in L2 messages by random sequences of bits. The feature brings more protection to voice calls using A5/1 encryption algorithm.

39.2 Hardware Coverage The feature is supported from by G3 onwards TRE (including MC TRE).

39.3 Feature Activation The feature is commercially optional. For specific information about the feature activation, refer to Network Reconfiguration Recommendations , to Randomisation of fil bits in L2 messages .

39.4 Parameters This section contains the new parameter involved in feature deployment: Name

New

EN_RANDOMISE_FBL2

New



39.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , to RNUSM: Ded. Radio Res 1/2 .

154 / 288



39.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Online Help 9153 OMC-R Functional and Graphical Evolutions Network Reconfiguration Recommendations


155 / 288


156 / 288


40 Introduction of CF F8 LMT

40 Introduction of CF F8 LMT Note: This feature is available starting with MR1Ed2.


157 / 288

40 Introduction of CF F8 LMT

40.1 Description The feature replace the generic PC Panasonic CF 74 laptop into CF F8.







40.7 Applicable Documents The following document is impacted by the feature: Engineering Rules for LMT .

158 / 288


41 MC TRE Module Introduction

41 MC TRE Module Introduction Note: This feature is available in MR1Ed2.


159 / 288


41.1 Description MC TRE module is an extension of the ‘TWIN-module’ in term of TRX capacity. A TWIN module has a capacity of up to 2 TRE, whether an MC-module has a capacity of up to 6 GSM TRE (an MC-module can be configured with less than 6 TRE). MC RRH is an ‘outdoor box’ with up to 2 MC-modules/MC-TRE inside, full capacity (the MC-RRH can have only a single MC-module inside). Distributed BTS is one central box (new SUMX) and one or several MC-RRH.

41.2 Hardware Coverage The MC TRE module is accepted with: SUMA, SUMX boards 64 kbpsstatistic and nomux multiplexing mode. The MC TRE module is not compatible with: Tx-Diversity, Antenna Hopping TRX Dynamic Power Saving 16kbpsstatistic, 64kbpstatic multiplexing modes. Distributed BTS is suported with the V2 version of SUMX board.

41.3 Feature Activation The following features are optional and can be controled as mentioned: MC-module configuration The control is done depending on the number of the TRE mapped on MC module, the number is agreed with the customer. Dynamic power Multistandard The check is done at OMC. MC-modules configuration in multistandard Similar remark with the first item.

41.4 Parameters This section contains the new parameters involved in feature deployment:

160 / 288

Name

New

Dynamic_Power_Allocation

New

Additional_Power_Tables

New



41.5 Counters and Indicators This section contains the new counters involved in feature deployment: BSC Counters Counter ID

Counter Name

MC1208

TIME_PWR_RED_8PSK_1

MC1209

TIME_PWR_RED_8PSK_2

MC1210

TIME_PWR_RED_8PSK_3

MC1211

TIME_PWR_RED_8PSK_4

MC1212

TIME_PWR_RED_GMSK_1

MC1213

TIME_PWR_RED_GMSK_2

MC1214

TIME_PWR_RED_GMSK_3

MC1215

TIME_PWR_RED_GMSK_4

MC1216

TIME_PWR_RED_DEFENSE_1

MC1217


MC1218


MC1219


MC1220

TIME_8PSK_BURST_TRANSMISSION

MC1221

TIME_GMSK_BURST_TRANSMISSION

MC1222

TIME_DEFENSE_BURST_TRANSMISSION

41.6 LMT/OMC HMI Updates 41.6.1 LMT Updates For specific information about the BTS LMT updates, refer to BTS NEM User Guide .


41.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Online Help


161 / 288


9153 OMC-R Functional and Graphical Evolutions Network Reconfiguration Recommendations BSS Configuration Rules BSS Configuration Handbook BTS NEM User Guide Reconfigure TRE/Sectors, 9100 BTS Reconfigure TRE/Sectors, Monoband to Multiband Cell Upgrade 9100 BTS with AN/SUM/TRE Evolution Modules Move BTS/Abis, Different BSC, Same OMC-R Move BTS/Abis, Different BSC, Different OMC-R Move BTS/Abis in same BSC Add TRE to Equipped 9100 BTS Delete TRE from Equipped 9100 BTS Replace X BTS with Y BTS, Free Abis Port Replace X BTS with Y BTS, Same Abis Port 9100 BTS/9110 Micro BTS Functional Description BTS Alarm Dictionary 9100 BTS/9110 Micro BTS Corrective Maintenance Handbook 9100 BTS Commissioning Manual 9100 BTS Acceptance Manual 9100 BTS Additional Tests CI 08 - Site Equipment Inventory. 9100 BTS Hardware Description General Safety Instructions for Node B / BTS

162 / 288


42 RMS Improvement: Increase of the 42 BCCH-BSIC Pairs Limit

42 RMS Improvement: Increase of the 42 BCCH-BSIC Pairs Limit Note: This feature is available in MR1Ed2.


163 / 288


42.1 Description The BCCH/BSIC pairs limit is increased from 42 to 154. The RMS campaign is designed in a daily basis. The number of pairs is increased to allowed to report more interferers by the mobiles through the referred TRX.

42.2 Hardware Coverage The feature is supported for: 9130 BSC Evolution starting with G3 TRE (in this case the limit is 84).

42.3 Feature Activation The feature is commercially optional. For specific information about the feature activation, refer to Network Reconfiguration Recommendations , to RMS Improvement: Increase of the 42 BCCH-BSIC Pairs Limit .

42.4 Parameters This section contains the new parameters involved in feature deployment: Name

New

EN_MORE_RMS_BCCH_BSIC

New

RMS_BCCH_BSIC_NB

New




42.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Online Help

164 / 288



9153 OMC-R Functional and Graphical Evolutions Network Reconfiguration Recommendations .


165 / 288


166 / 288


43 2 BTS Configuration within 2 Integrated SUMA Boards in 1 BTS Cabinet

43 2 BTS Configuration within 2 Integrated SUMA Boards in 1 BTS Cabinet Note: This feature is available starting with MR1Ed2.


167 / 288

43 2 BTS Configuration within 2 Integrated SUMA Boards in 1 BTS Cabinet

43.1 Description Description In case of MBI5 Shared BTS, the factory cabinet contains two BTS. The upper BTS contains 3 subracks and the below BTS contains 2 subracks. Any configuration or commisioning operations must be done independently on each BTS.

43.2 Hardware Coverage The feature is supported for: MBI5 shared BTS.

43.3 Feature Activation There is no activation activation scenario scenario for this feat feature. ure.

43.4 Parameters There are no parameters modifications.




43.7 Applicable Documents The following documents are impacted by the feature: 9100 BTS Hardware Description Reconfigure TRE/Sectors, 9100 BTS Reconfigure TRE/Sectors, Monoband to Multiband Cell . Upgrade 9100 BTS with AN/SUM/TRE Evolution Modules Extend Extend Existing Cell(s) to Shared Shared Cell(s) Cell(s) by Adding Adding a 9100 BTS Reduce Cell(s) Shared by Deleting the 9100 BTS Supporting the Secondary Sector . 9100 MBS Indoor Installation Manual 9100 BTS Commissioning Manual .

168 / 288


44 MC-RRH 900 - 2G/3G - Different PA - Separate 2G and 3G carriers in same module

44 MC-RRH 900 - 2G/3G - Different PA - Separate 2G and 3G carriers in same module Note: This feature is available starting with B11 MR1ED3. To be completed.


169 / 288


44.1 Description Description The MC TRE can be hosted in: Standard A9100 Evolium BTS, with all BTS modules A new outdoor box called: MC RRH distributed BTS, when the central box contains the SUM board. Where: A Mono-standard MC-TRX is, from the point of view of a 2G system, a TRE module A Multi-standard MC-TRX is a module capable of switching between 2G and 3G software A Multi-mode MC-TRX is a module running 2G+3G software (2G SW embedding 3G SW), thus also Multi-standard An MC module is based on MCPA technology performing Power Amplifier for several carriers The number of other standard modules in a given sector and in the band GSM is entered by the operator at OMC-R.

44.2 Hardware Coverage Because MC-TRE is supported with SUMA and SUMX and MC-RRH is supported with SUMX, the feature is supported accordingly.

44.3 Feature Activation 44.4 Parameters This section contains the new and modified parameters involved in feature deployment. Name

New

Nb other standard modules 900 MHz Nb other standard modules 1800 MHz

44.5 Counters and Indicators This section contains the new and modified counters and indicators involved in feature deployment.

170 / 288



Name

New

44.6 LMT/OMC HMI Updates 44.6.1 LMT Updates For specific information about the LMT modifications, refer to BTS NEM User Guide , section. section.

44.6.2 OMC HMI Updates For specific specific information information about the OMC HMI updates, updates, refer to 9153 OMC-R Functional and Graphical Evolutions , sections BSSUSM: Modify BTS Remote Settings and RNUSM: Network Information Window .

44.7 Applicable Documents The following documents are impacted by the feature: BTS NEM User Guide 9153 OMC-R Functional and Graphical Evolutions Network Reconfiguration Recommendations 9153 OMC-R Online Help 9100 BTS/9110 Micro BTS Functional Description BSS Configuration Rules BSS Surveillance Handbook CI 08 - Site Equipment Inventory 9100 BTS Hardware Description 9100 BTS/9110 Micro BTS Functional Description 9100 BTS/9110 Micro BTS Corrective Maintenance Handbook BTS Alarm Dictionary Add TRE to Equipped 9100 BTS Delete TRE from Equipped 9100 BTS Reconfigure TRE/Sectors, 9100 BTS Reconfigure TRE/Sectors, Monoband to Multiband Cell Upgrade 9100 BTS with AN/SUM/TRE Evolution Modules Replace X BTS with Y BTS, Free Abis Port Replace X BTS with Y BTS, Same Abis Port Move BTS/Abis, Different BSC, Same 9153 OMC-R


171 / 288


Move BTS/Abis, Different BSC, Different 9153 OMC-R Move Move BTS/Abis in Same BSC 9100 BTS Commissioning Manual 9100 BTS Additional Tests General Safety Instructions for Node B / BTS 9100 BTS Acceptance Manual .

172 / 288


45 Network Synchronization of Radio TS

45 Network Synchronization of Radio TS Note: This feature is available starting with MR1Ed2.


173 / 288


45.1 Description The feature reduces the interferences on the cells’ frequencies used by a BTS where this feature is activated.

45.2 Hardware Coverage The BTS must be equipped with a GPS receiver for this feature to be available. On site a GPS antenna must be installed. In a configuration with master/slaves BTS the GPS receiver is mandatory only in the master BTS.

45.3 Feature Activation The feature is commercially optional. For specific information about the feature activation, refer to Network Reconfiguration Recommendations , to Network Synchronization of Radio TS .

45.4 Parameters This section contains the new parameter involved in feature deployment: Name

New

GPS-Synchronised

New

FN_OFFSET_TIME_SYNCHRO

New



45.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , sections BSSUSM: Modify BTS Characteristics Window and BSSUSM: Effective Synch Mode Panel .

45.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Online Help 9153 OMC-R Functional and Graphical Evolutions Network Reconfiguration Recommendations

174 / 288



BSS Configuration Handbook BSS Configuration Rules .


175 / 288


176 / 288


46 IP Transport in the BSS

46 IP Transport in the BSS Note: This feature is available starting with MR3.


177 / 288


46.1 Description Description IP transport is introduced to support the diversity of existing network environments. The BSC, TC, MFS are connected connected to an IP network network through Ethernet links. The BTS is connected to an IP network over Ethernet links, links, or over over E1 links. The BTS is connected to an IP network over Ethernet links. The following figure shows the generic configuration.

Figure 1: BSS “full IPoEth”

46.2 Hardware Coverage The feature is supported only in: 9130 BSC Evolution 9130 MFS Evolution 9125 TC with new TCIF board BTS 9100 (MBI3/MBI5, Outdoor) equipped with SUMX

46.3 Feature Activation For specific information information about the feature activation, activation, refer to Change IP Extraction Mode for 9130 BSC Evolution.


178 / 288



Name

New

BSC Name Atermux Number TC Internal Mode TC Rack Name TCSL ID BscNodeId TcslIpAddressBsc (BSC) TcslIpAddressTc (BSC) TcslPortBsc (BSC) TcslPortTc (BSC) TcslIpAddressBsc (TC) TcslIpAddressTc (TC) TcslPortBsc (TC) TcslPortTc (TC) OML_PRIORITY TCSL_MSS TCSL_PRIORITY GPRS_ACCESS_INTVL GPRS_ACCESS_TEST_CNT GPRS_ACCESS_TEST_DELAY GPRS_ACCESS_TEST_ PERIOD TCP_KEEP_ALIVE_CNT TCP_KEEP_ALIVE_IDLE TCP_KEEP_ALIVE_INTVL REACHABILITY_TEST_ADDR_O&M REACHABILITY_TEST_ADDR_O&M (BSC) REACHABILITY_TEST_ADDR_TELECO REACHABILITY_TEST_ADDR_TELECOM M (BSC) ROUTING_TABLE (BSC)


179 / 288


Name

New

REACHABILITY_TEST_ADDR_O&M (TC) REACHABILITY_TEST_ADDR_TELECOM (TC) ROUTING_TABLE (TC) REACHABILITY_TEST_ADDR_O&M (MFS) REACHABILITY_TEST_ADDR_TELECOM (MFS) ROUTING_TABLE (MFS) T_TCSL_ACK (TC)

New

T_TCSL_ACK (BSC)

New

N_TCSL_RETRY (TC)

New

N_TCSL_RETRY (BSC)

New

TCP_MSL (BTS) TCP_MSL (BSC) used by CCP and OMCP TCP_MSL (MFS) TCP_MSL (TC) IPBSS_SUBNET_MASK_MFS

New

IPGCH_Base_Address_MFS

New

IPGCH_IP_Address_MFS

New

IPGCHC_Base_TCP_MFS

New

IPGCHU_Base_UDP_MFS

New

REACHABILITY_TEST_ADDR_TEL_GB

New

REACHABILITY_TEST_ADDR_TEL_BSS

New

REACHABILITY_TEST_LABEL_O&M

New

REACHABILITY_TEST_LABEL_TEL_GB

New

REACHABILITY_TEST_LABEL_TEL_BSS

New

BSS_TRANSPORT_MODE (BSC) BSS_TRANSPORT_MODE (MFS) GslIpAddressBsc (BSC) GslIpAddressMfs (BSC)

180 / 288



Name

New

GslTcpPortBsc (BSC) GslTcpPortMfs (BSC) GslIpAddressBsc (MFS) GslIpAddressMfs (MFS) GslTcpPortBsc (MFS) GslTcpPortMfs (MFS) tcMuxIpAddress tcMuxPort tcNONMUXIpAddress tcNONMUXPortUL MIN_PDCH (MX BSC) MAX_PDCH (MX BSC) MAX_PDCH_HIGH_LOAD (MX BSC) T_TC_IPTCHM_REPORTING _PERIOD UL_TA_Late_Margin TCP_MAX_RETRANS (BSC) TCP_MAX_RETRANS (MFS) TCP_MAX_RETRANS (BTS) TCP_MAX_RETRANS (TC) TCP_KEEP_ALIVE_CNT (BTS) TCP_KEEP_ALIVE_CNT (BSC) used by CCP and OMCP TCP_KEEP_ALIVE_CNT (MFS) TCP_KEEP_ALIVE_CNT (TC) TCP_KEEP_ALIVE_IDLE (BTS) TCP_KEEP_ALIVE_IDLE (BSC) used by CCP and OMCP TCP_KEEP_ALIVE_IDLE (MFS TCP_KEEP_ALIVE_IDLE (TC) TCP_KEEP_ALIVE_INTVL (BTS)


181 / 288


Name

New

TCP_KEEP_ALIVE_INTVL (BSC) used by CCP and OMCP TCP_KEEP_ALIVE_INTVL (MFS) TCP_KEEP_ALIVE_INTVL (TC) START_TELECOM_IP_ADDRESS_TC

New

TELECOM_IP_SUBNET_MASK_TC

New

IPTCH_UDP_PORT_TC_MUX

New

IPTCH_UDP_PORT_TC_NONMUX

New

MUXTRAUP_SIZE A MUXTRAUP TRAU_CONNECTION_TIMEOUT T_MAX_HOLD_MUXTRAUP

New

E1_MTU

New

IPGSL_PRIORITY (BSC) IPGSL_PRIORITY (MFS) IPGCHC_PRIORITY (MFS) IPGCHC_PRIORITY (BTS) IPGCHU-GBR_PRIORITY (MFS) IPGCHU-GBR_PRIORITY (BTS) IPGCHU-BE_PRIORITY (MFS) IPGCHU-BE_PRIORITY (BTS) OandM_PRIORITY (BSC) OandM_PRIORITY (MFS) P0_MAPPING_LAYER2_BSC P0_MAPPING_LAYER2_MFS P1_MAPPING_LAYER2_BSC P1_MAPPING_LAYER2_MFS P2_MAPPING_LAYER2_BSC P2_MAPPING_LAYER2_MFS

182 / 288



Name

New

P3_MAPPING_LAYER2_BSC P3_MAPPING_LAYER2_MFS P0_MAPPING_LAYER3_BSC P0_MAPPING_LAYER3_MFS P1_MAPPING_LAYER3_BSC P1_MAPPING_LAYER3_MFS P2_MAPPING_LAYER3_BSC P2_MAPPING_LAYER3_MFS P3_MAPPING_LAYER3_BSC P3_MAPPING_LAYER3_MFS T_IPGCH_ACK_DL T_IPGCH_ACK_UL T_IPGCHU_TIMEOUT IPGCHU_ACK_SEND_THRESHOLD IPGCHU_BE_UL_THRES IPGCHU_UDP_MAX_WINDOW_SIZE_G3 IPGCHU_UDP_MAX_WINDOW_SIZE_G4_G5 IPGCHU_UDP_MAX_WINDOW_SIZE_GPU AbisTransportMode AbisTargetTransportMode BTSIPIdentifier BTS-Hostname NTPServerIPAd1 NTPserverIPAd2 SUM-Capability BSC-OML-IP-Address BTS-First-NTP-Server-Address BTS-Second-NTP-Server-Address


183 / 288


Name

New

BTS-TransMode FTPServerAd

New

BSC_OML_TID

New

BSC_OML_PortNumber

New

BTS_OML_PortNumber

New

BTS_OML_TID

New

DHCP-location

New

Abis-Topology

Modified

OCXO-Synch-Mode

Modified

Usable-TSs

Modified

Abis link number

Modified

ABIS_BTS_GROUP_ID ABIS_BTS_GROUP_SECONDARY_ID BTS-Routing-SubGroup

New

Second-BTS-Routing-SubGroup

New

DHCP_SERVER_IP_ADDRESS

New

AbisBtsGroupId BTSmode(MFS) Bandwidth(MFS) Bandwidth(BSC) BTS_IP_Ad TCH_TS_ACTIVITY_FACTOR NB_MAX_ACTIVE_TCH_TS BANDWIDTH_PER_TCH_TS BANDWIDTH_PER_SIG_LINK NRT_GUARANTEED_BANDWIDTH MIN_PDCH (BSC) MAX_PDCH_HIGH_LOAD (BSC)

184 / 288



Name

New

MAX_PDCH (BSC) BSC_RSL_TID

New

RSL_UDP_PORT_BSC

New

BSC_RSL_PortNumber

New

BTS_RSL_PortNumber

New

BTS_RSL_TID

New

IP_CONGESTION_JITTER_THRESHOLD

New

TP_QUEUE3_WEIGHT

New

TP_QUEUE2_WEIGHT

New

TP_QUEUE1_WEIGHT

New

TP_QUEUE0_WEIGHT

New

P0_TPQUEUE_MAPPING

New

P1_TPQUEUE_MAPPING

New

P2_TPQUEUE_MAPPING

New

P3_TPQUEUE_MAPPING

New

IPGCH_PACKET_SIZE IPGSL_MSS (MFS)

New

IPGSL_MSS (BSC)

New

E1_MTU

New

TCSL_MSS (TC)

New

TCSL_MSS (BSC)

New

START_TELECOM_IP_ADDRESS_BSC

New

TELECOM_IP_SUBNET_MASK_BSC

New

IPTCH_UDP_PORT_BTS

New

RSL_UDP_PORT_TRX

New

SIDMO_TCP_PORT_TRE

New

FTP_PRIORITY (BSC) FTP_PRIORITY (BTS)


185 / 288


Name

New

RSL_I_PRIORITY (BSC) RSL_I_PRIORITY (BTS) RSL_UI_PRIORITY SNMP_PRIORITY (BSC) SNMP_PRIORITY (BTS) SNMP_PRIORITY (TC) VARIOUS_IP_PRIORITY (BSC) VARIOUS_IP_PRIORITY (MFS) VARIOUS_IP_PRIORITY (BTS) VARIOUS_IP_PRIORITY (TC) ABIS_BANDWIDTH IPGCHU_Nominal_Abis_BW_Factor IPGCHU_BW_MAX_CONG_DL IPGCHU_BW_MAX_CONG_UL IPGCHU_BW_MIN_CONG_DL IPGCHU_BW_MIN_CONG_UL IPGCH_DL_BW_CONTROL_REPEAT_RATE IPGCH_UL_BW_CONTROL_REPEAT_RATE IPGCHU_DELAY_HIGH_THRES_DL IPGCHU_DELAY_HIGH_THRES_UL IPGCHU_DELAY_LOW_THRES_DL IPGCHU_DELAY_LOW_THRES_UL IPGCHU_MAX_PATTERN_MEAS_THROUGHPUT_DL IPGCHU_PATTERN_LIFETIME_DL Estimated_Speed_CS_FAMILY_0.7 RLC_FC1_BUFFER_SEND_THRES RLC_FC1_THROUGHPUT_CHANGE_THRES RLC_TARGET_BUFFER

186 / 288



Name

New

IPGCHU_ExtraGBR_UL_THRES IPGCHU_GBR_UL_THRES IPGCHU_XOFF_BE_FIFO_DL_THRESHOLD IPGCHU_XOFF_GBR_FIFO_DL_THRESHOLD IPGCHU_XON_BE_FIFO_DL_THRESHOLD IPGCHU_XON_GBR_FIFO_DL_THRESHOLD IP_CONGESTION_FILTER_WS IP_CONGESTION_PREVENTIVE_THRESHOLD IP_CONGESTION_TIMER T_IP_COUNTER_REPORT BSCNodeId_TCSL TCSL_IpAddress_BSCside(BSC) TCSL_IpAddress_BSCside(TC) TCSL_IpAddress_TCside(BSC) TCSL_IpAddress_TCside(TC) Tcsl-port-BSCside(BSC) Tcsl-port-BSCside(TC) Tcsl-port-TCside(BSC) Tcsl-port-TCside(TC) TCSL_MSS (BSC) TCLS_MSS (TC) TRAU_ACTIVITY_TIMER TCSL_ID N_TCSL_RETRY(BSC) N_TCSL_RETRY(TC) T_TCSL_ACK(BSC) T_TCSL_ACK(TC)


187 / 288


46.5 Counters and Indicators

188 / 288

Counter ID

Counter Name

IP21

NB_ATERMUX_NIBBLE_ALLOC_REQ

IP22

NB_ATERMUX_NIBBLE_ALLOC_FAIL_CONG

IP23

TIME_ATERMUX_NIBBLE_CONG

IP24a

NB_BSC_SENT_GSL_IP_BYTES

IP24b

NB_BSC_SENT_GSL_IP_PACKETS

IP24c

MAX_NB_BSC_SENT_GSL_IP_BYTES

IP24m

MAX_NB_BSC_RCVD_GSL_IP_BYTES

IP25a

NB_BSC_SENT_OMLRSL_IP_BYTES

IP25b

NB_BSC_SENT_OMLRSL_IP_PACKETS

IP25c

NB_BSC_SENT_OMLRSL_BYTES_HIGHEST_MIN

IP26a

NB_BTS_SENT_OML_IP_BYTES

IP26b

NB_BTS_SENT_RSL_IP_BYTES

IP26c

NB_BTS_SENT_OML_IP_PACKETS

IP26d

NB_BTS_SENT_RSL_IP_PACKETS

IP26e

NB_BTS_RESENT_RSL-I_LAPD FRAMES

IP27a

NB_BSC_SENT_TCSL_IP_BYTES

IP27b

NB_BSC_SENT_SS7_IP_BYTES

IP27c

NB_BSC_SENT_TCSL_IP_PACKETS

IP27d

NB_BSC_SENT_SS7_IP_PACKETS

IP27e

NB_BSC_RESENT_SS7_IP_PACKETS

IP27h

NB_BSC_SENT_TCSL_IP_BYTES_HIGHEST_MIN

IP27g

NB_BSC_SENT_SS7_IP_BYTES_HIGHEST_MIN

IP28a

NB_TC_SENT_TCSL_IP_BYTES

IP28b

NB_TC_SENT_SS7_IP_BYTES

IP28c

NB_TC_SENT_TCSL_IP_PACKETS

IP28d

NB_TC_SENT_SS7_IP_PACKETS




Counter ID

Counter Name

IP28f

NB_TC_RESENT_SS7_SCTP_SEGMENTS

IP28h

NB_TC_SENT_TCSL_IP_BYTES_HIGHEST_MIN

IP28g

NB_TC_SENT_SS7_IP_BYTES_HIGHEST_MIN

IP29a

NB_BTS_SENT_IPTCH_BYTES

IP29c

NB_BTS_SENT_IPTCH_PACKETS

IP29k

NB_BTS_RCVD_IPTCH_PACKETS_OUT_OF_DELAY

IP29l

NB_BTS_NOT_RCVD_DL_IPTCH_PACKETS

IP30a

NB_TC_SENT_IPTCH_BYTES

IP30c

NB_TC_SENT_IPTCH_PACKETS

IP30g

NB_TC_SENT_IPTCH_BYTES_HIGHEST_MIN

IP30m

NB_TC_NOT_RCVD_UL_IPTCH_PACKETS

IP31a

NB_BTS_SENT_ALL_FLOW_BYTES_HIGHEST_MIN

IP31c

NB_BTS_DROPPED_IP_PACKETS_PRIORITY0

IP31d


IP31e


IP31f


IP32a

NB_BSC_SENT_ALL_FLOWS_BYTES

IP32b

NB_BSC_RCVD_ALL_FLOWS_BYTES

IP32c

NB_BSC_DROPPED_IP_PACKETS_PRIORITY0

IP32d


IP32e


IP32f


IP33a

NB_TC_TO_TC_SENT_IPTCH_PACKETS

IP33c

NB_TC_TO_TC_SENT_IPTCH_BYTES

IP33f

NB_TC_TO_TC_SENT_IPTCH_BYTES_HIGHEST_MIN

IP40a

NB_BTS_SENT_IPGCHU_GBR_IP_PACKETS

IP40b

NB_BTS_RESENT_IPGCHU_GBR_IP_PACKETS

189 / 288


Counter ID

Counter Name

IP40d

NB_BTS_SENT_IPGCHU_GBR_IP_BYTES

IP41a

NB_BTS_SENT_IPGCHU_BE_IP_PACKETS

IP41b

NB_BTS_RESENT_IPGCHU_BE_IP_PACKETS

IP41d

NB_BTS_SENT_IPGCHU_BE_IP_BYTES

IP42a

NB_BTS_SENT_IPGCHC_CTRL_TCP_SEGMENTS

IP42d

NB_BTS_SENT_IPGCHC_CTRL_IP_BYTES

P540a

NB_RCVD_RT_PFC_REQUEST

P540b

NB_REFUSED_RT_PFC_LACK_BW

P540c

NB_REFUSED_RT_PFC_LACK_RADIO

P540d

MAX_DL_GBR_BW_GRANTED

P540e

MAX_UL_GBR_BW_GRANTED

P541a

NB_MFS_SENT_IPGCHU_GBR_IP_PACKETS

P541b

NB_MFS_RESENT_IPGCHU_GBR_IP_PACKETS

P541d

NB_MFS_SENT_IPGCHU_GBR_IP_BYTES

P542a

NB_MFS_SENT_IPGCHU_BE_IP_PACKETS

P542b

NB_MFS_RESENT_IPGCHU_BE_IP_PACKETS

P542d

NB_MFS_SENT_IPGCHU_BE_IP_BYTES

P543a

NB_MFS_SENT_IPGCHC_CTRL_TCP_SEGMENTS

P543d

NB_MFS_SENT_IPGCHC_CTRL_IP_BYTES

P547a

NB_MFS_SENT_GSL_IP_BYTES

P547c

NB_MFS_SENT_GSL_TCP_SEGMENTS

P549a

CUMULATED_TIME_PS_DL_BE_CONGESTED TEMP_TRX

46.6 LMT/OMC HMI Updates 46.6.1 LMT Updates Tbc.

190 / 288



46.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to the following 9153 OMC-R Functional and Graphical Evolutions sections: BSSUSM Transport Mode Window BSSUSM TCSL Parameters Window BSSUSM Bandwidth Window BSSUSM View BTS Window .

46.7 Applicable Documents The following GCD documents are impacted by the feature: BSS Overview 9153 OMC-R Online Help 9130 BSC Evolution Maintenance Handbook 9100 BTS/9110 Micro BTS Functional Description 9100 BTS Hardware Description BTS Alarm Dictionary Operations & Maintenance Principles 9153 OMC-R Functional and Graphical Evolutions BSS Configuration Handbook BSS Methods handbook BTS NEM User Guide 9130 BSC Evolution NEM User Guide Network Reconfiguration Recommendations 9100 MBS Outdoor Installation Manual 9100 MBS Indoor Installation Manual CI 08 – Site Equipment Inventory BSS Telecom Routing Configurations BSS configuration rules Engineering Rules for LMT 9130 MFS Evolution IMT User Guide MFS Alarm Dictionary 9130 BSC Evolution Functional Description 9125 Compact TC Description 9153 OMC-R Online Help


191 / 288


The following methods are impacted by the feature: Change to IP Mode for 9130 BSC Evolution Move full IP BTS different BSS, same/different OMC Move BTS/Abis, Different BSC, Same OMC-R Move BTS/Abis, Different BSC, Different OMC-R Move BTS/Abis in same BSC Move Several Abis Links from a BSC to Another, Same OMC-R Move BSS from One 9125 Compact TC to Another Add TRE to Equipped 9100 BTS Delete TRE from Equipped 9100 BTS Reconfigure TRE/Sectors, 9100 BTS Reconfigure TRE/Sectors, Monoband to Multiband Cell Upgrade 9100 BTS with AN/SUM/TRE Evolution Modules Merge 900 and 1800 Cells into Multiband Cells on 9100 BTS Add BTS, New Cell(s) Delete BTS Extend Existing Cell(s) to Shared Cell(s) by Adding an 9100 BTS Reduce Cell(s) Shared by Deleting the 9100 BTS Supporting the Secondary Sector Create Extended Cells Reconfigure TRE/Sectors on 9110 E-BTS Extend/Replace an 9110 Micro-BTS with an 9110 E-BTS Replace X BTS with Y BTS, Free Abis Port Replace X BTS with Y BTS, Same Abis Port Replace Non Alcatel-Lucent BTS with Alcatel-Lucent BTS Attach Secondary, Third Abis Which Scenario to Use Extend 9130 BSC Evolution Reduce 9130 BSC Evolution Extend Ater Mux Interface Reduce Ater Mux Interface Move 9130 BSC Evolution without MFS, Different MSC, Same OMC-R Move 9130 BSC Evolution, Same MFS, Different MSC, Same OMC-R Move 9130 BSC Evolution, Different MFS, Different MSC, Same OMC-R Move 9130 MFS Evolution with Associated BSS, Different OMC-R

192 / 288



Move 9130 BSC Evolution Without MFS, Same MSC, Different OMC-R Move 9130 BSC Evolution, Different MFS, Same MSC, Different OMC-R Move 9130 BSC Evolution, Different MFS, Different MSC, Different OMC-R Move 9130 BSC Evolution, Different MFS, Same MSC, Same OMC-R Move BSS from One 9125 Compact TC to Another Configure GPRS Move Direct CS Link into Dedicated GPRS Link Move Dedicated GPRS Link into Direct CS Link Add Logically a BSS to an MFS Add a BSS by Moving Existing Links Through an MFS Delete GPRS from Active BSS Add GP in 9130 MFS Evolution for Multi GP BSS Delete GP from 9130 MFS Evolution for a Multi GP BSS Add a New BSS on OMC-R B11/B11 9125 TC Software Replacement .


193 / 288


194 / 288


47 Remote BTS NEM

47 Remote BTS NEM Note: This feature is available starting with MR3.


195 / 288

47 Remote BTS NEM

47.1 Description The Network Element Manager for a BTS (BTS NEM) is a software package used for managing, maintaining and commissioning a BTS. For IP transport, there are two BTS connection types: Local connection Remote connection Local Connection Local connection can be done via front panel NEM connector on the SUM board (which needs to open the NE door with a key). From this point, the PC-NEM is named ”Local PC-NEM”. Remote Connection This is possible from anywhere within the network, as far as the routing / firewall allows. A “remote connection” can also be on a switch port physically located near the BTS, which needs the port to be enabled and physical accessible. In the following figure,the wording “PC-NEM” is used for content relative to the local and the remote PC-NEM. BTS 2 View Local PC−NEM via RS 232

BTS 1 View Local PC−NEM via IP or RS232

BTS 1, BTS 2, BTS X View Remote PC_NEM

BTS X BTS 2

BTS 1

Ethernet or PPP/E1

IP

NEM−IP−Forwarding−inside−BTS = TRUE BTS 1, BTS 2, BTS X View Remote PC−NEM

NEM−IP−Forwarding−inside−BTS = FALSE

Note: A new parameter, ’NEM-IP-Forwarding-inside-BTS (True/False)’, exists in the BSC Terminal in order to enable/disable routing to the NEM in each BTS. Local and remote PC-NEM use IP to connect BTS. There are two ways to connect the PC-NEM: Serial connection to the BTS Ethernet connection. Serial connection to a BTS Local IP connection using IP/PPP over RS232 for SUMA/P only. Ethernet connection

196 / 288


47 Remote BTS NEM

The Ethernet local or remote connection is realized either: Through a point to point Ethernet link to the concerned BTS for the SUMX, or Connecting the PC-NEM on the IP backbone.

47.2 Hardware Coverage Remote connection to the BTS is possible only if the BTS is equipped with SUMX boards. The LMT PC must be equipped with an Ethernet Interface.

47.3 Parameters A new parameter, ’NEM-IP-Forwarding-inside-BTS (True/False)’, exists to enable/disable routing to the NEM in each BTS.


47.5 Feature Activation The Remote BTS-NEM feature is not optional, it is activated by default. Optionally it is possible to enable/disable routing to the NEM in each BTS by activate ’NEM-IP-Forwarding-inside-BTS’ parameter. To enable/disable routing to the NEM in each BTS: 1. Open the BSC Terminal. 2. From the BSC Terminal menu bar, select Commands->BSS Operations->Display BSC Peer Entities. The "Display BSC Peer Entities window" appears. 3. Complete the following fields: In the ’Object Class’, select BSC In the ’Unit Type’, select BSC In the ’Unit Number’, enter 1. Check the “’Get and Modify’” box and click on [ OK ]. The "Modify BSC Peer Entities" window opens. 4. Select "Address - 3" tab. 5. In the ’NEM-IP-Forwarding-inside-BTS’ field select the TRUE value: 6. Click on [ OK ].

47.6 LMT/OMC HMI Updates 47.6.1 LMT Updates For specific information about the LMT modifications, refer to Modify BSC Peer Entities , in the 9130 BSC Evolution Terminal User Guide .


197 / 288

47 Remote BTS NEM


47.7 Applicable Documents The following documents are impacted by the feature: BTS NEM User Guide BSS Configuration Rules 9153 OMC-R Network Administration Handbook 9100 BTS/9110 Micro BTS Corrective Maintenance Handbook 9100 BTS Commissioning Manual 9100 BTS Acceptance Manual 9100 BTS Additional Tests Engineering Rules for LMT CI 08 - Site Equipment Inventory.

198 / 288


48 Layer 2 Network Access

48 Layer 2 Network Access Note: This feature is available starting with MR3.


199 / 288


48.1 Description Using a Layer 2 transport network means that, despite the BSS, network elements (BTS, BSC, TC, MFS) will still exchange IP packets. The underlying functional architecture of the transport network can be seen as a single LAN, in fact, an Ethernet LAN. Taking into account the potential distance between network elements, this is based on "Extended Area LAN" concepts such the MetroEthernet. The primary impact on the IP-based transport is that all IP addresses of the network elements belong to the same IP subnet, and no IP router (Layer 3) is needed between two network elements.

48.2 Hardware Coverage The feature is supported only in: 9130 BSC Evolution: IPoE1 with new TP board TPIP module IPoEth no new upgrade needed IPoEth no new upgrade needed 9130 MFS Evolution 9125 TC with new TCIF board BTS 9100, 9110 IPoE1 with SUMA,SUMP IPoEth with SUMX IPoEth with SUMX

48.3 Feature Activation For specific information about the feature activation, refer to the BSS Telecom Routing Configuration document.





200 / 288



48.7 Applicable Documents The following documents are impacted by the feature: BSS Telecom Routing Configuration BSS Overview.


201 / 288


202 / 288


49 Security Enhancements for IP Introduction

49 Security Enhancements for IP Introduction Note: This feature is available starting with MR3.


203 / 288


49.1 Description The aim of this feature is to distribute the security functions over the BSS subsystems as well as their interactions. The security strategy for the BSS takes into account the following aspects: The need for network element protection A first level of protection is to secure write accesses to telecom and O&M network elements. A second level of protection is to secure read access for sensitive data. A third level of protection would be to secure everything, meaning read accesses whatever the data flow. The need for network protection (data flow sensitivity) Network protection is not to protect the network, but to protect data flows going through the network against dishonest users with network access. The solution is to use secured VPN tunnels, via to the IPsec protocol. The BTS supports such IPsec tunnels. Other network elements rely on customer central site IPsec gateways. The NE location (central or remote sites are differentiated). As opposed to customer central sites, where only customer authorized people are present, remote sites are easily accessible to non authorized people. In the BSS, remote sites are, in most cases, BTS sites. Therefore, the BTS has the support of the IPsec and the 802.1x protocol for Ethernet port access control. The 802.1x protocol forbids unauthorized clients from using the Ethernet ports of a server machine.


49.3 Feature Activation For specific information about the feature activation, refer to Network Reconfiguration Recommendations .


204 / 288

Name

New

BSS_PAGING_COORDINATION (BSC)

New

BSS_PAGING_COORDINATION (MFS)

New

EN_BTS_PASSWORD_ RENEWAL (OMC local, BSC level, default is FALSE)

New

EXCLUDE_BTS_FROM_ PASSWORD_RENEWAL (OMC local, BTS level, default is FALSE)

New



Name

New

SNMP_KEY_PERIOD_ TOWARD_BTS (OMC local, BSC level)

New

SNMP_KEY_PERIOD_ TOWARD_TC (OMC local, TC level) SSH_KEY_PERIOD_ TOWARD_MFS (OMC local, one for every managed MFS). Implemented through a crontab script. EN_IPSEC (BTS)

New

IPsec_GW_ADDRESS

New

EN_SUPPLICANT_802 _1x (BTS)

New

EN_AUTHENTICATOR_802 _1x (BTS)

New

PRIMARY_RADIUS_ SERVER_ADDRESS

New

SECONDARY_RADIUS_ SERVER_ADDRESS

New

RADIUS_SHARED_SECRET

New

NEM-IP-Forwarding-inside -BTS

New

BSC_USE_FTP

New





205 / 288


206 / 288


50 Logging of BTS Temperature

50 Logging of BTS Temperature Note: This feature is available starting with MR1 ED3 and MR3.


207 / 288

50 Logging of BTS Temperature

50.1 Description The feature functionality allows you to log the BTS ambient temperature remotely via the OMC-R without any external equipment. The data is also made available at the established interfaces for external analysis tools (e.g. Metrica). Inside the BTS, the internal temperature, and more precisely, the TRX-module temperature from which the ambient temperature can be derived very easily, is available. This information is made accessible via the normal O&M procedures and the ambient temperature is made visible at the OMC-R.


50.3 Feature Activation The feature is not a commercially optional feature and there is no need for a new parameter at the OMC/BSC/BTS level. The feature is activated as soon as the BSC/BTS/OMC are upgraded.


50.5 Counters and Indicators One counter is needed to monitor the TRX temperature. The level of the new counter is at “TRX” and not at “BTS”, even if future user actions are at the BTS level. Counter ID

Counter Name

MC1200

TRX_MAX_TEMPERATURE



50.7 Applicable Documents There are no applicable documents.

208 / 288


51 Ethernet Installation Kit



209 / 288


51.1 Description The Ethernet connection is introduced in B11 in order to connect the 9100 Evolution Indoor BTS to the IP network. To connect the BTS in IP network, it must be equipped with: SUMX board Ethernet Adapter Board Ethernet cable with RJ-45 connectors (3BK 25970 ABxx) Ethernet Adapter Board consists in 8 double layer ETH ports, inserted in the front panel of the 9100 Indoor BTS (MBI3/MBI5 only), between the MSCA and Power Supply modules. The Ethernet cable with RJ-45 connectors (3BK 25970 ABxx), is used to interconnect the TRANS1 port of the SUMX board and the back panel ETH1 port of the Ethernet Adapter Board. From the front panel ETH1 port of the Ethernet Adapter Board, other Ethernet cable is used to connect the BTS to the external switch/router.

51.2 Hardware Coverage The Ethernet Adapter Board is introduced in the MBI3/MBI5 cabinets. External Alarm Input Board Multistandard XIBM

Equipment Labels

External Interface Connectors

DC Output

GND +12 V

B C B X

Multistandard Connection Area MSCA

External Clock Interface Group

Abis Interface Group

t u O 1 K L C X

n I 1

K L C X

Power Supply and Circuit Breaker Area DCBR3 Equipment Labels

DC Filter Connectors

−48V

Abis 3

Abis 1

Abis 4

Abis 2

DC Output −48 V/500 W max

0V

DC OUT 500 W max

Abis 4 I Abis 3 I Abis 2 I Abis1

t u O / n I 2 K L C X

I

I

I

I

0

0

0

0

INT & SR1 DC OUT

SR2

SR3

RS232

XRT

Krone Strip

Abis Relays

Ethernet Adapter Board

Circuit Breakers

Figure 2: MBI3 Interconnection Panels with Ethernet Adapter Board External Alarm Input Board Multistandard XIBM

Equipment Labels External Interface Connectors DC Output

GND +12 V

B C B X

Multistandard Connection Area MSCA

External Clock Interface Group

Abis Interface Group

t u O 1 K L C X

n I 1 K L C X

Power Supply and Circuit Breaker Area DCBR5 Equipment Labels

DC Filter Connectors

−48V

Abis 3

Abis 1

Abis 4

Abis 2

DC Output −48 V/500 W max

0V

DC OUT 500 W max

Abis 4 I Abis 3 I Abis 2 I Abis1

t u O / n I 2 K L C X

I

I

I

I

I

I

0 0 0 0 0 0 INT & SR1 SR2 SR3 SR4 SR5 DC OUT

XRT

RS232

Krone Strip

Abis Relays

Ethernet Adapter Board

Circuit Breakers

Figure 3: MBI5 Interconnection Panels with Ethernet Adapter Board

210 / 288



51.3 Feature Activation The feature is commercially optional and there is no new parameter at the OMC/BSC/BTS level.


51.5 Counters and Indicators There are no new or modified counters and indicators.



51.7 Applicable Documents 9100 BTS Hardware Description 9100 MBS Indoor Installation Manual 9100 BTS Commissioning Manual


211 / 288


212 / 288


52 3G Search Prio Wrong in PMO

52 3G Search Prio Wrong in PMO Note: This feature is available starting with MR1Ed.2 and MR3.


213 / 288


52.1 Description In the current implementation when the MS enters the PTM, a PMO message is sent, overwriting the GPRS 3G Measurement Parameters broadcasted in SI2Quater to the MS, especially the list of cells and the parameter 3G_SEARCH_PRIO. This implementation is chosen to preserve time processing in the mobile in order not to impact the on-going 2G packet transfer. Otherwise the MS could interrupt its data transfer(s) more frequently to monitor 3G neighbor cells. This feature allows a reselection from GSM to UMTS to be possible in both packet idle and packet transfer modes. The PMO message is not longer sent at the beginning of a packet transfer and the mobile uses instead the broadcasted neighboring cells and reselection parameters for the reselection decision. This is accomplished by using a new value for the following parameters: EN_2G_TO_3G_CELL_RESELECTION and EN_2G_TO_3GTDD_CELL_RESELECTION .


52.3 Feature Activation The feature is not optional. For specific information about the feature functionality, refer to the Network Reconfiguration Recommendations , to 3G Search Prio wrong in PMO .

52.4 Parameters This section contains the modified parameters involved in feature deployment: Name

New

EN_2G_TO_3G_CELL_RESELECTION

Modified

EN_2G_TO_3GTDD_CELL_RESELECTION

Modified




214 / 288



52.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Functional and Graphical Evolutions Network Reconfiguration Recommendations BSS Overview .


215 / 288


216 / 288


53 Support of Sftp in the OMC



217 / 288


53.1 Description SFTP stands for SSH File Transfer Protocol. SFTP based on SSHv2 shall be supported as a alternative to FTP transfers between 9153 OMC-R and 9130 BSC Evolution. Since SFTP also supports the standard ftp commands, it is not required to use the SFTP specific commands.







53.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Network Administration Handbook 9153 OMC-R Methods Handbook .

218 / 288


54 IP Flow Separation at Physical Level

54 IP Flow Separation at Physical Level Note: This feature is available starting with B11 MR1 and MR3.


219 / 288


54.1 Description This feature provides the flow segregation at layer 1 (same or different physical ports for the different flows). The 9130 BSC Evolution has flexible mapping of O&M / A SigoIP flows onto GE ports starting with B11 MR1. The 9130 BSC Evolution has flexible mapping of O&M / A SigoIP / BSSoIP flows onto GE ports starting with B11 MR3. The 9130 MFS Evolution has flexible mapping of O&M / GBoIP flows onto GE ports starting with B11 MR1. The 9130 MFS Evolution has flexible mapping of O&M / GBoIP / IPGSL / IPGCH flows onto GE ports starting with B11 MR3. The 9125 TC has flexible mapping of O&M / Telecom flows onto GE ports starting with B11 MR3.

54.2 Hardware Coverage This feature is available for 9130 BSC Evolution, 9130 MFS Evolution and 9125 TC.

54.3 Feature Activation 9130 BSC Evolution

To activate the feature for 9130 BSC Evolution: 1. From the BSC Terminal menu bar, select Commands -> BSS Operations -> Display IP Parameters. The "Display IP Parameters" window opens 2. Complete the following fields: In ’Object Class’, select BSC In ’Unit Type’, select BSC In ’Unit Number’, enter 1. Check the "Get and Modify" box and click on [OK] The "Modify IP Parameters" window opens 3. From the "Modify IP Parameters" window, select "IP Parameters" tab and select ’DISTINCT TAGGING’ for the ’VLAN Conf Index’ field. For specific information about the feature functionality for 9130 BSC Evolution, refer to BSS Telecom Routing Configuration , section Management of IP transport in 9130 BSC Evolution .

9130 MFS Evolution

To activate the feature for 9130 MFS Evolution: 1. For B11 MR1 refer to BSS Configuration Handbook, section Separate O&M and GBoIP flows 2. For B11 MR3 refer to BSS Configuration Handbook, section Separate MFS IP Telecom flows. For specific information about the feature functionality for 9130 MFS Evolution, refer to BSS Telecom Routing Configuration , section Management of IP transport in 9130 MFS Evolution .

9125 Transcoder

220 / 288

To activate the feature for 9125 Transcoder (for B11 MR3 only):



1. From the TC NEM menu bar, select Window -> TCIF -> IP Conf. The "TCIF" window opens 2. In the "TCIF" window use the "IP Conf" panel to view and modify TC’s IP configuration 3. Check box "VLAN Separation" which allows to select the O&M/Telecom flow separation and click on [Save]. For specific information about the feature functionality for 9125 Transcoder, refer to BSS Telecom Routing Configuration , section Management of IP transport in 9125 TC .

54.4 Parameters This section contains the modified parameters involved in feature deployment: Name

New

VLAN_CONF_INDEX

New


54.6 LMT/OMC HMI Updates 54.6.1 LMT Updates For specific information about the LMT updates, refer to 9130 BSC Evolution Terminal User Guide , section Display/Modify BSC Parameters 9130 MFS Evolution IMT User Guide , section Set VLAN Configuration in MFS 9125 Transcoder NEM User Guide , section IP Conf Panel


54.7 Applicable Documents The following documents are impacted by the feature: Modify N7 Transport Mode for 9130 BSC Evolution BSS Telecom Routing Configuration 9130 BSC Evolution Acceptance Manual Install 9130 MFS/BSC Evolution 9130 BSC Evolution Commissioning


221 / 288


Configure OS6850 for GB/BSS Traffic. 9125 Transcoder NEM User Guide 9130 MFS Evolution IMT User Guide 9130 BSC Evolution Terminal User Guide

222 / 288


55 AMR WB Cell Load Handling

55 AMR WB Cell Load Handling Note: This feature is available starting with MR3.


223 / 288


55.1 Description The AMR WB Cell Load Handling feature allows a call to be established in AMR NB HR (or in HR in case NB-AMR HR would not be possible) in case of high cell load. This is accomplished by using the following new parameters: EN_HR_FOR_AMR_WB_GMSK and . The ADD_HR_IN_TFO_LIST parameter is available only for the 9130 BSC.


55.3 Feature Activation In order to activate the feature: 1. Open RNUSM Main Window, create a PRC containing the cells to be configured. 2. In the PRC, select the required cell. 3. Right click and select Edit. 4. Click on the AMR&TFO tab and next on the AMR WB tab. 5. In order to activate the feature, set the ’EN_HR_FOR_AMR_WB_GMSK’ parameter to ’Enabled’.


224 / 288

Name

New

EN_HR_FOR_AMR_WB_GMSK

New

ADD_HR_IN_TFO_LIST

New





55.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , to RNUSM: TFO Window and RNUSM: AMR WB Window .



225 / 288


226 / 288


56 Interworking with LTE in the Packet Domain

56 Interworking with LTE in the Packet Domain Note: This feature is available starting with B11 MR1Ed2 / MR3.


227 / 288


56.1 Description LTE (Long Term Evolution) is the evolution of 3G UMTS which targets very high throughputs. LTE means: No more CS plane, voice is carried through VoIP A flat IP architecture Use of enhanced radio techniques, including MIMO & OFDM E-UTRAN the equivalent of GERAN (2G) or UTRAN (3G) is a set of eNodeBs connected to the same MME (Mobility Management Entity, part of the Core Network). The purpose of the Inter-working with LTE in the Packet domain feature is to manage 2G versus LTE inter-working (in other words, the GERAN versus E-UTRAN inter-working), with the following requirements: Support of 2G to LTE-FDD reselection GERAN CS User Plane is not managed (no CS Handover to be managed) Inter-RAT NACC is managed for the E-UTRAN to GERAN direction only Manage cell reselection in blind search mode. The management of the reselection algorithm by the MS/UE takes into account additional parameters (the so-called priority parameters ) which are not only related to E-UARFCNs, but also to UARFCNs and 2G serving cells.

56.2 Hardware Coverage The feature is supported only by 9130 MFS Evolution and 9130 BSC Evolution.

56.3 Feature Activation The feature is optional and can be activated at cell level through EN_2G_TO_LTEFDD_CELL_RESELECTION parameter. To activate the feature: 1. Open RNUSM Main Window, create a PRC containing the cells on which the LTE reselection to be activated. 2. In the PRC, select the required cell. 3. Right click and select Edit. 4. Select LTE. 5. In order to activate the feature, set the ’EN_2G_TO_LTEFDD_CELL_RESELECTION’ parameter to enabled.The following rules apply when using this feature: The ’EN_2G_TO_3GTDD_CELL_RESELECTION’ and ’EN_2G_TO_LTEFDD_CELL_RESELECTION’ parameters cannot be enabled at the same time.

228 / 288



For a given BSS, we cannot have at the same time FDD_ARFCN_LIST defined at BSS level and, at least, one 2G cell where both ’EN_2G_TO_3G_CELL_RESELECTION’ and ’EN_2G_TO_LTEFDD_CELL_RESELECTION’ are enabled. If both ’EN_2G_TO_3G_CELL_RESELECTION’ and ’EN_2G_TO_LTEFDD_CELL_RESELECTION’ are enabled, they must have the same value. ’EN_FAST_3G_CELL_RESELECTION’ cannot be set on 3 if any of ’EN_2G_TO_LTEFDD_CELL_RESELECTION’ or ’EN_2G_TO_3G_CELL_ RESELECTION’ is = 0 ’EN_FAST_3G_CELL_RESELECTION’ cannot be set on 2 if ’EN_2G_TO_LTEFDD_CELL_RESELECTION’ = 0 MCC_LTE, MNC_LTE, CI_LTE uniquely identify an LTE cell inside the OMC. This represents the telecom/O&M LTE cell identification, also called ECGI (E-UTRAN Cell Global Identifier). The allowed value ranges for ARFCN_LTE (FDD) are: [0..5379] U [5730..6599]. Note: For 2G-LTE interworking, Alcatel-Lucent recommends configuring ARFCN_LTE (FDD) value compliant with the values recommended by 3GPP release 9, where band 6 (2650 - 2749) is not applicable anymore and band 11 (4750 – 4999) is limited up to 4949. For any given serving cell, no more than 8 distinct values of ARFCN_LTE(FDD) are allowed in the neighbor LTE cells having RAT_LTE =FDD and targeted by 2g-LTE reselection links. For any given serving cell, no more than 20 outgoing 2g-LTE adjacencies are allowed.



Name

New

RAT_LTE

New

MCC_LTE

New

MNC_LTE

New

CI_LTE

New

EUARFCN

New

PRIORITY_LTE

New

THRESH_LTE_HIGH

New

229 / 288


230 / 288

Name

New

THRESH_LTE_LOW

New

QRXLEVMIN_LTE

New

MEASUREMENT_BANDWIDTH

New

T_RESELECTION

New

H_PRIO

New

DEFAULT_PRIORITY_3G

New

DEFAULT_THRESH_3G

New

DEFAULT_QRXLEVMIN_3G

New

EN_2G_TO_LTEFDD_CELL _RESELECTION

New

Qsearch_P_LTE

New

GERAN_PRIORITY

New

THRESH_PRIORITY_SEARCH

New

THRESH_2G_LOW

New

PRIORITY_3G

New

THRESH_3G_HIGH

New

THRESH_3G_LOW

New

QRXLEVMIN_3G

New

Adjacency-type-LTE

New

Adjacency-Name-LTE

New

Cell-LTE-PLMN-Name

New

Cell-Name-LTE

New

Cell-LTE-Location-Name

New

EN_RIM_NACC

Modified

FDD_ARFCN_LIST

Modified

EN_2G_TO_3G_CELL_ RESELECTION

Modified

EN_2G_TO_3GTDD_ CELL_RESELECTION

Modified



Name

New

EN_FAST_3G_RESELECTION

Modified

CELL_RIM_NACC_CAPABILITY

Modified


Counter Name

P450f

NB_E_UTRA_FDD_CAPABLE_MS_CONTEXT_GPU

P450g

NB_UTRA_FDD_CAPABLE_MS_CONTEXT_GPU

P450h

NB_UTRA_TDD_CAPABLE_MS_CONTEXT_GPU

P182f

NB_SERVING_INTER_LTE_NACC



56.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Functional and Graphical Evolutions BSS Overview 9153 OMC-R Online Help Network Reconfiguration Recommendations BSS Configuration Handbook .


231 / 288


232 / 288


57 Remove Mx Firmware from Hardware Status for BSC

57 Remove Mx Firmware from Hardware Status for BSC Note: This feature is available starting with MR1Ed.2 and MR3.


233 / 288


57.1 Description With this feature implemented, firmware upgrade procedure is simple and easy. Firmware upgrade is triggered remote by operator upon reception of alarms. This is possible because the firmware packages are part of the BSS package. The types of boards and the Firmware which should be upgraded are listed below: Firmware on FRU

IPMC FW

Payload

BIOS

(IPMI SW) SMM (M100)

Yes

Yes

No

SSW (F300)

Yes

Yes

No

OMCP/CCP (F715)

Yes

No

Yes

PEM

Yes

No

No

FAN Tray

Yes

No

No

PC (A100)

Yes

No

No

Firmware upgrade action is executed manually by operator, one by one and more than one upgrade action in parallel is forbidden. The standby board is upgraded first, followed by the active one. Firmware upgrade is performed only when the BSC is stable (under IT). Because the whole firmware package is part of the BSS software version, the firmware effective upgrade can only take place in one of these three situations: Commissioning (platform installation) Software replacement Board replacement. These situations are triggering conditions for possible discrepancy reporting, via an alarm and log files. This is when the firmware upgrade is performed. The entire firmware upgrade process is described in Firmware Upgrade section from 9130 BSC Evolution Maintenance Handbook .

57.2 Hardware Coverage This feature is available only for 9130 BSC Evolution.



234 / 288






57.7 Applicable Documents The following documents are impacted by the feature: 9130 BSC Evolution Maintenance Handbook B10/B11 MFS/TC/BSS Software Migration B11/B11 MFS/TC/BSS Software Replacement 9130 BSC Evolution Commissioning 9130 BSC Evolution Software Installation.


235 / 288


236 / 288


58 Remove Mx Firmware from Hardware Status for MFS

58 Remove Mx Firmware from Hardware Status for MFS Note: This feature is available starting with MR3.


237 / 288


58.1 Description With this feature implemented, firmware upgrade procedure is simple and easy. Firmware upgrade is triggered remote by operator upon reception of alarms. This is possible because the firmware packages are part of the MFS package. The boards impacted by firmware upgrade are listed below: Boards

Action

SMM (M100)

Payload + IPMI upgrade

SSW (F300)

Payload + IPMI upgrade

OMCP/(F715)

BIOS + IPMI upgrade

PEM

IPMI upgrade

FAN Tray

IPMI upgrade

PC (A100)

IPMI upgrade

GP

IPMI + NE1oE Firmware upgrade

MUX

NE1oE Firmware upgrade

The Firmware upgrade process is launch exclusively from IMT. The operator is mainly warned via alarms about firmware discrepancies compared to a reference. The whole process concerning firmware upgrade is automatic and consists in: Locate the standby board and upgraded it When the new firmware version is installed and running, reboot it Locate the new standby board and upgrade it When the new firmware version is installed and running, reboot it Wait for return to operational state. The entire firmware upgrade process is described in Firmware Upgrade section from 9130 MFS Evolution Maintenance Handbook .

58.2 Hardware Coverage This feature is available only for 9130 MFS Evolution.



238 / 288






58.7 Applicable Documents The following documents are impacted by the feature: 9130 MFS Evolution Maintenance Handbook 9130 MFS Evolution IMT User Guide B10/B11 MFS/TC/BSS Software Migration B11/B11 MFS/TC/BSS Software Replacement 9130 MFS Evolution Software Installation.


239 / 288


240 / 288


59 Bidirectional Forwarding Detection (BFD) Protocol

59 Bidirectional Forwarding Detection (BFD) Protocol Note: This feature is available starting with B11 MR3.


241 / 288


59.1 Description Bidirectional Forwarding Detection (BFD) is a network protocol used to detect faults between two endpoints over a particular link. In an IP BSS network architecture, IP Abis traffic is often aggregated from BTS sites in several points of concentration (POCs) of an access network, before reaching a central IP gateway, which is the starting point of a secured IP backbone towards TC, BSC, and MFS. The network access can be a layer 2 or a layer 3 access network. In most of the cases, it is not owned by the mobile operator, and Abis is backhauled through leased lines services. BFD is a tool to monitor the transport layer of the Abis through non managed transport network. The BFD IP address is used by the “next hop” router which implement the BFD protocol The address is configured via the BTS NEM and is retrieved by the OMC via through SNMP. If the network access does not provide path resiliency capability , BFD can be used as trigger of path switchover between a primary and a secondary route.


59.3 Feature Activation To activate the feature: From the BTS NEM User Guide window follow the menu path: Configuration —> IP... —> BFD IP Address The "BFD Responder IP Address" window opens. Enter the required BFD IP Address and click on [ OK ]. The default value is 0.0.0.0 and means that BFD is not activated; that value indicates that the operator does not provide any IP address yet and is not displayed on the OMC. The BFD IP address must be different from the BTS IP address.


New

BFD_IP_ADDRESS_BTS

New


242 / 288



59.6 LMT/OMC HMI Updates 59.6.1 LMT Updates For specific information about the LMT modifications, refer to BTS NEM User Guide , section 4.9.5 BFD IP Address.

59.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , section 1.4 BSSUSM: View BTS Window.

59.7 Applicable Documents The following documents are impacted by the feature: BTS NEM User Guide 9153 OMC-R Functional and Graphical Evolutions Install CISCO Routers BSS Telecom Routing Configuration.


243 / 288


244 / 288


60 MC-RRH 900 - 2G -2PA

60 MC-RRH 900 - 2G -2PA Note: This feature is available starting with B11 MR3ED1. To be completed.


245 / 288

60 MC-RRH 900 - 2G -2PA

60.1 Description The MC TRE can be hosted in: Standard A9100 Evolium BTS, with all BTS modules A new outdoor box called: MC RRH distributed BTS, when the central box contains the SUM board. Where: A Mono-standard MC-TRX is, from the point of view of a 2G system, a TRE module A Multi-standard MC-TRX is a module capable of switching between 2G and 3G software A Multi-mode MC-TRX is a module running 2G+3G software (2G SW embedding 3G SW), thus also Multi-standard An MC module is based on MCPA technology performing Power Amplifier for several carriers A MC-RH is a module, which has two power amplifiers, each able to transmit simultaneoulsy several carriers, and a dual receiver, able to receive simultaneoulsy several carriers. A carrier is a GSM carrier and or a LTE (or other system) carrier. A distributed BTS is a BTS, which is composed of one central module (SUM) and one or more MC-RH with the necessary interconnection A remote MC-RH (MC RRH) is a unit which contains all necessary items to provide a full BTS function except the functions of a central module, from DC and central module connection to antenna connection A local MC-RH (MC LRH) is a unit which provides together wit the central module, a cabinet and a power distribution all necessary items for a full macro BTS MC-RRH is an ‘outdoor box’ with to 2 MCPA inside MC-RRH supports up to 12 TRE/GSM carriers.

60.2 Hardware Coverage MC-RRH is supported with SUMX.

60.3 Feature Activation 60.4 Parameters This section contains the new and modified parameters involved in feature deployment.

246 / 288


60 MC-RRH 900 - 2G -2PA

Name

New

60.5 Counters and Indicators This section contains the new and modified counters and indicators involved in feature deployment. Name

New

60.6 LMT/OMC HMI Updates 60.6.1 LMT Updates For specific information about the LMT modifications, refer to BTS NEM User Guide , section.

60.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , section.

60.7 Applicable Documents The following documents are impacted by the feature: BTS NEM User Guide 9153 OMC-R Functional and Graphical Evolutions Network Reconfiguration Recommendations 9153 OMC-R Online Help 9100 BTS/9110 Micro BTS Functional Description BSS Overview BSS Configuration Rules Using BSS IP Ports BSS Surveillance Handbook BSS Preventive Maintenance Handbook CI 08 - Site Equipment Inventory BSS O&M Routing Configurations BSS Telecom Routing Configuration 9100 BTS Hardware Description


247 / 288

60 MC-RRH 900 - 2G -2PA

9100 BTS/9110 Micro BTS Functional Description 9100 BTS/9110 Micro BTS Corrective Maintenance Handbook BTS Alarm Dictionary Add TRE to Equipped 9100 BTS Delete TRE from Equipped 9100 BTS Reconfigure TRE/Sectors, 9100 BTS Reconfigure TRE/Sectors, Monoband to Multiband Cell Upgrade 9100 BTS with AN/SUM/TRE Evolution Modules Reconfigure RRH/Sectors on Distributed BTS Distributed BTS Dismantling Manual Distributed BTS Installation Manual Distributed/9100 BTS Commissioning Manual 9100 / Distributed BTS Additional Tests 9100 / Distributed BTS Acceptance Manual

248 / 288


61 9130 BSC Evolution Availability Improvement. Weekly Standby Reset.

61 9130 BSC Evolution Availability Improvement. Weekly Standby Reset. Note: This feature is available starting with B11 MR1Ed. 2.


249 / 288


61.1 Description The aim of this feature is to avoid the traffic disturbance due to the 9130 BSC Evolution hardware failures. There are 4 cases of outages due to hardware failures: OMCP CCP TPGSM MUX To prevent the above 4 types of outages, the solution is to use a periodic reset of the standby boards of the 9130 BSC Evolution. The periodic reset of the standby boards lead to: initialize again the standby board. This remove the potential software fault and leave the standby board in the clean state launch again the self test on the standby board. This detect an inactif fault covered by the boot self test This daily reset is launched on the following standby boards: OMCP, CCP, TPGSM, MUX An OMC-R script is developed and scheduled in crontab for daily runing. The script manages a list of board types which is circularly parsed, one type being picked up from the list at each run. The script triggers the reset on the standby boards of the chosen type on all or some specified 9130 BSCs Evolution known by the 9153 OMC-R. The reset is triggered only if the concerned standby board is in IT status.

61.2 Hardware Coverage The feature is available only for 9130 BSC Evolution.

61.3 Feature Activation The feature is not optional. For specific information about the feature functionality, refer to the Network Reconfiguration Recommendations .



250 / 288




61.6.2 OMC HMI Updates There are no OMC HMI updates.

61.7 Applicable Documents The following documents are impacted by the feature: Network Reconfiguration Recommendations B11/B11 MFS/TC/BSS Software Replacement .


251 / 288


252 / 288


62 Gb flex

62 Gb flex Note: This feature is available starting with B11 MR3 release.


253 / 288

62 Gb flex

62.1 Description The Gb-Flex feature allows a BSS to connect to more than one SGSN. Up to 8 SGSN can be connected to a BSS. Up to 8 NRI can be defined per SGSN. In Alcatel-Lucent solution Gb-Flex works only with Gb over IP. The benefits of the feature are as following: Load sharing can be done by the BSS for each SGSN where the BSS is connected Possibility of capacity upgrades by additional SGSN in the pool-area Increase the reliability when an SGSN fails thanks to SGSN redundancy To have several SGSN allow to enlarge the served area and the reduction of signalling within the core network Possibility to “off-load” an SGSN to perform maintenance


62.3 Feature Activation The feature is optional. For specific information about the feature functionality, refer to the Configure GPRS .


254 / 288

Name

New

EN_GB_FLEX

New

NRI_LENGTH_PS

New

NRI_PS

New

SGSN_Weight

New

SGSN_OFFLOAD_STATE

New

NULL_NRI_PS

New

CN_ID_PS

New

SLOW_MOVING_FACTOR

New

SGSN_Name

New

NRI_LIST_PS

New


62 Gb flex

Name

New

MAX_NB_SGSN

New

CELL_GPU

New

BSS_GPU

New

SGSNR

New


Counter Name

P180a

NB_SGSN_SELECTION_NSF

P180b

NB_SGSN_SELECTION_RIM



62.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Functional and Graphical Evolutions Configure GPRS BSS Overview BSS Configuration Rules Network Reconfiguration Recommendations BSS Configuration Handbook 9153 OMC-R Online Help.


255 / 288

62 Gb flex

256 / 288


63 STM1 Bidirectional on 9125 TC Equipped with TC STM1-IP Subrack

63 STM1 Bidirectional on 9125 TC Equipped with TC STM1-IP Subrack Note: This feature is available starting with B11 MR1Ed. 2.


257 / 288


63.1 Description STM1 is a 155 Mbit/s interface, defined within the SDH family of interfaces (others are STM-4, STM-16…). SDH is used for GSM solely for the transport of E1 links. The SDH is used in the so-called channelized mode. Each E1 link is transported transparently (using asynchronous mapping) in one VC12 container. One STM-1 link can contain up to 63 VC12 containers. Due to the high traffic per STM1 link, protected access is usually used. Protection is done by automatic protection switching (APS) with one active and one standby link. Automatic protection switching (APS) is used to avoid the loss of a STM1 link in case of a physical link (or termination) failure. The standards have designed two modes: Unidirectional protection In case of unidirectional protection each end of the link transmits on both lines permanently and each end of the link selects only one line for reception of the traffic and monitors the received signal on that line. If the received signal is faulty, then APS in that end will switch the reception to the other line. At a given point in time, thus one end could use one line and the other end the other line for reception Bidirectional protection. In case of bidirectional protection each end of the link transmits and receives always on one and the same selected line. Each end of the link monitors the received signal on that line. If the received signal is faulty, then APS in that end will switch the reception to the other line and will signal the switch to the other end (in-band signaling protocol if possible). At a given point in time, thus both ends use one and the same working line (except during the short transitions). The TC provides APS 1+1 bidirectional non-revertive implementation, with automatic return to the unidirectional mode in case of APS protocol mismatch. The requirement is to provide compatibility in terms of STM1 APS interface with NSN MGW. This feature requires at least two STM1 interfaces to be activated on TC, this is because the Atermux and A interfaces cannot be mapped on the same STM1 interface. Another constraint consists in fact that only 189 A interfaces from 192 maximum possible can be mapped on 3 STM1 interfaces. At TCIF side, the working (protected) lines will be configured on TCIF1 from slot 0 and the protecting lines for TCIF2 from slot 1. This configuration should be synchronized with the one made at ADM/MGW side.

63.2 Hardware Coverage This feature is available only for 9125 TC equipped with TC STM1-IP subrack.

63.3 Feature Activation The feature is optional. For specific information, refer to 9125 Transcoder NEM User Guide .

258 / 288




New

APS_MODE

New




63.7 Applicable Documents The following documents are impacted by the feature: 9125 Transcoder NEM User Guide 9125 Transcoder Alarm Dictionary Activate/Deactivate STM1 Interface for 9130 BSC Evolution/9125 TC .


259 / 288


260 / 288


64 BTS Synchronization Through NTP

64 BTS Synchronization Through NTP Note: This feature is available starting with B11 MR3 release.


261 / 288


64.1 Description With IP BSS, the frequency synchronization of the BTS (i.e. the automatic recalibration of the local oscillator frequency on a high accuracy transmission clock source) can be achieved through NTP: a stratum 1 NTP server delivers NTP messages to the BTS. The key value of the synchronization through NTP is that this method does not induce any requirement on the transmission backbone.


64.3 Feature Activation The feature is optional. For specific information about the feature functionality, refer to the Synchronize BTS with a NTP Server .


262 / 288

Name

New

FREQ_SYNC_POLLING_TIME_INITIAL

New

FREQ_SYNC_POLLING_TIME_SUSTAINED

New

FREQ_SYNC_POLL_PER_EVAL

New

FREQ_SYNC_MIN_NBR_EVAL

New

FREQ_SYNC_MAX_INITIAL_EVAL

New

FREQ_SYNC_GRAD_CONV_THRES

New

FREQ_SYNC_GRAD_CONV_EDGE

New

FREQ_SYNC_SUCCESS_RATIO

New

BTS-First-NTP-Server-Address

New

BTS-Second-NTP-Server-Address

New

EFFECTIVE_SYNCH_MODE

New

NTP_SYNCHRONISED

New

NTP-IP-ADDR

New

GPS-SYNCHRONISED

New



Name

New

NTP-SYNCHRONISED

New

PCM-SYNCHRONISED

New




64.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Functional and Graphical Evolutions BTS NEM User Guide BSS Configuration Handbook 9130 BSC Evolution Terminal User Guide Add BTS, New Cell(s) 9153 OMC-R Online Help.


263 / 288


264 / 288


65 CS/PS Outage Detection

65 CS/PS Outage Detection Note: This feature is available starting with B11 MR1Ed. 2.


265 / 288


65.1 Description The objective of this feature is to improve the availability of the system. This means that under normal conditions, the unavailability of the system is better than 5’15” per year. This feature runs in full IP mode, mixed mode or TDM mode. A new module TOAD (Telecom Outage Detector), is introduced in both active and standby OMCP as a basic LINUX process. The TOAD checks the number of call establishment per minute. When it detects there is no call establishment, the process launches an end to end telecom tests towards Abis and Ater interface. If both tests fails, it attempts to retrieve the traffic by running the take over of the main boards, and finally, if the traffic still does not come up, it runs a BSC reset. The TOAD process runs the BSC outage detection and defense only on the active OMCP board, mainly to avoid double defense. It sends the outage report to the standby TOAD to assure the case of OMCP take over following BSC outage detection. The BSC distinguish the CS and PS outage, but the PS traffic is less stringent. The CS and PS traffic outage is observed in the same time.The activity of the BSC regarding the PS traffic only is very low without impacting the PS traffic. The BSC will not run any defense action in case where only the PS outage is detected. The BSC will not generate additional BSC outage neither in case of bad external transmission network nor in case of others BSS network element dysfunctions (MFS,TC, BTS unavalaibility).


65.3 Feature Activation The feature is activated from the 9130 BSC Evolution Terminal. For specific information, refer to Network Reconfiguration Recommendations .


New

EN_Tel_Outage_DET

New


266 / 288



65.6 LMT/OMC HMI Updates 65.6.1 LMT Updates For specific information about the LMT updates, refer to the 9130 BSC Evolution Terminal User Guide , section Display/Modify BSC Parameters .


65.7 Applicable Documents The following documents are impacted by the feature: Network Reconfiguration Recommendations 9130 BSC Evolution Terminal User Guide BSC & TC Alarm Dictionary


267 / 288


268 / 288


66 OMCP-OMC Supervision Link Defense

66 OMCP-OMC Supervision Link Defense Note: This feature is available starting with B11 MR1Ed. 2.


269 / 288


66.1 Description The connection between 9130 BSC Evolution and OMC-R can be over an IP network or via A interfaces. In case of connection over IP network, the extraction point is on OMCP. This feature is to provide a working connection to OMC-R in case of communication via A interface over MLPPP. The aim of this feature is to improve the 9130 BSC Evolution connection towards the OMC-R, to save the basic requirement regarding the availability time. This requirement is improved by the following mechanisms: limitation of the FLT state (Power OFF) in cases of TPGSM when no configuration is available, applying a default TPGSM configuration by running TPGSM takeover on the PPP link alarm by checking the connection toward the OMCR.


66.3 Feature Activation The feature is activated from the 9130 BSC Evolution Terminal. For specific information, refer to Network Reconfiguration Recommendations .


New

EN-OMCR-Conn-DET

New


66.6 LMT/OMC HMI Updates 66.6.1 LMT Updates For specific information about the LMT updates, refer to the 9130 BSC Evolution Terminal User Guide , section Display/Modify BSC Parameters .


270 / 288



66.7 Applicable Documents The following documents are impacted by the feature: Network Reconfiguration Recommendations 9130 BSC Evolution Terminal User Guide


271 / 288


272 / 288


67 TP Init Auto Test Improvements

67 TP Init Auto Test Improvements Note: This feature is available starting with B11 MR1Ed. 2.


273 / 288

67 TP Init Auto Test Improvements

67.1 Description The aim of this feature is to cover most of the component of theTP board and the datapath between those components. This application is ran right after driver installation, and before the MxPF process startup. When the TP starts-up , the driver load error log file is checked , if there is no error, TP starts-up normally , otherwise , the TP send an alarm to BSC and wait for poweroff. There are two type of diagnosis: diagnosis without SS7, after all drivers installation except the TPGMSK SS7 diagnosis, after all drivers installation and load PQ2 software, and it imply that the drivers are loaded in two stage and the TPGMSK is installed at last.







67.7 Applicable Documents The BSC & TC Alarm Dictionary document is impacted by the feature.

274 / 288


68 BSC Patch Management

68 BSC Patch Management Note: This feature is available starting with B11 MR1Ed.2.


275 / 288


68.1 Description The aim of this feature is to improve the availability and usability of MX BSC patch information Due to the implementation of a Webmin module that: generates a report post-processes its output and displays a report giving BSC patch information, the operator can check: the patch name the patched software provider (the software delivered as a patch may be provided by BSC or the MX platform development teams or it may be provided by a third party) whether the patch archive is present in BSC’s patch repository or not whether errors have been recorded at patch install time the type of ATCA boards concerned by the patch the list of ATCA boards on which the patch is installed and whether the installed software is corrupted or not. However, MX BSC patch installation is not changed. That is, patches are installed manually, one by one, BSC by BSC, remotely from OMC-R, using helper tools delivered with each patch.






276 / 288




68.7 Applicable Documents The documents impacted by this feature are: B11/B11 MFS/TC/BSS Software Replacement B10/B11 MFS/TC/BSS Software Migration .


277 / 288


278 / 288


69 MC-Modules hardware capacity licensing

69 MC-Modules hardware capacity licensing Note: This feature is available starting with B11 MR1Ed.2.1


279 / 288


69.1 Description In B11, it will be possible for customers to dynamically configure up to 6 2G TRXs in a MC-Module. The licensing unit controlled by the Centralized License Manager is the number of TREs effectively mapped to MC-Modules. Considering the pay-as-you-grow model and the shift of MC-Modules from 2G to 3G/LTE over time, the quantity of TREs mapped to MC-Modules is expected to fluctuate, requiring regular updates of the OMC-R licence files for a given customer. To anticipate and optimally manage the licensing of MC-Module hardware capacity, more flexibility is needed in order to automate the license generation. The flexibility of the license generation offered to customers is provided by an Alcatel-Lucent online web tool called LKDI, which tracks all the customer options transactions and provide a quick way for customers to get licenses. In GSM, the following cases are handled: regular license updates initiated by customers or customers representatives, control by Alcatel-Lucent over the options that are transferred back (returned in LKDI) in the case of migration, feature deactivation, or option reshuffling between severs automation of the license generation in LKDI.

69.2 Hardware Coverage The feature is only for MC-Modules.

69.3 Feature Activation The feature is optional.




69.6.2 OMC HMI Updates For specific information about the OMC HMI updates, refer to 9153 OMC-R Functional and Graphical Evolutions , section RNUSM: License server synchro and RNUSM: Network Information Window .

280 / 288



69.7 Applicable Documents The following documents are impacted by the feature: 9153 OMC-R Functional and Graphical Evolutions B11/B11 9153 OMC-R Software Replacement 9153 OMC-R Network Administration Handbook 9153 OMC-R Methods Handbook 9153 OMC-R Installation Site Preparation Sheet Move BTS/Abis, Different BSC, Different 9153 OMC-R Move 9120 BSC, Without MFS, Same MSC, Different 9153 OMC-R Move 9120 BSC, Different MFS, Same MSC, Different 9153 OMC-R Move 9135 MFS with Associated BSS, Different 9153 OMC-R Move 9130 MFS Evolution with Associated BSS, Different 9153 OMC-R Move 9130 BSC Evolution Without MFS, Same MSC, Different 9153 OMC-R Move 9130 BSC Evolution, Different MFS, Same MSC, Different 9153 OMC-R Move 9120 BSC, Different MFS, Different MSC, Different 9153 OMC-R Move 9130 BSC Evolution, Different MFS, Different MSC, Different 9153 OMC-R .


281 / 288


282 / 288


70 Improved Multi-GPU Performance

70 Improved Multi-GPU Performance Note: This feature is available starting with B11 MR3Ed.1.


283 / 288

70 Improved Multi-GPU Performance

70.1 Description In order to be prepared to face a still increasing packet traffic, an improved performance in case of Multi-GPU is needed. Until now the BSC chooses the GPU towards which sending an UL message according only to load sharing considerations among its GPU boards and therefore a part of the GPU processing is wasted in message rerouting. In order to send the UL message directly to the GPU board handling the corresponding cell, the BSC shall maintain a cell/GPU mapping table. From this improvement is expected a higher capacity per GPU board and therefore a reduction of the number of GPU boards for the same packet capacity, at network level.







70.7 Applicable Documents The BSS Configuration Rules document is impacted by the feature.

284 / 288


71 Iur-g interface with enhanced control plane

71 Iur-g interface with enhanced control plane Note: This feature is available starting with B11 MR1Ed.2.2


285 / 288


71.1 Description Iur is the interface defined by 3GPP between RNCs mainly to allow soft handover inside RNS (without involving CN) in case of inter RNC handovers. A first step of similar interface named Iur-g between BSCs and between RNC and BSC has been studied in 3GPP. Only some signalling information exchange between a BSS and a BSC/RNC has been standardized. The Iur-g interface is based on a subset of procedures and messages of the Iur interface of UTRAN, namely the RNSAP. With the current implementation, one BSC supports up to 16 neighbour RNCs. The new messages definition through an Iur-g like interface (Control plane) can optimize 3G to 2G Relocation/HO. Three procedures are defined on Iur-g+: Information exchange procedure: in line with 3GPP Iur-g RNSAP TS 25.423. The RNC obtains GSM cell capacity information from BSC. Common Measurement Procedure: slightly modified procedure against 3GPP Iur-g RNSAP TS 25.423 (more than one GSM cell per messages). The RNC obtains GSM cell load indication from BSC. The availability of GSM target cell capacity and load allows the RNC to trigger a handover toward a GSM cell in which the handover will be probably successful. Radio resource reserve handover procedure: specific procedure not defined in 3GPP, to reduce the handover preparation time and to trigger earlier the intersystem TD-SDCMA -> GSM handover in the UE. This procedure allows the source RNC to request directly the BSC to allocate in advance the radio resource needed in the target BSS for a just triggered external TD -> GSM handover. This anticipation allows the RNC to trigger the handover command toward the UE earlier (before the receipt of RELOCATION COMMAND from CN). Consequently, the handover preparation time is reduced, and consequently the time critical intersystem handover has better probability to succeed.

71.2 Hardware Coverage This feature is only for 9130 BSC Evolution.

71.3 Feature Activation The feature is optional, has one BSC-level activation parameter and is controlled per TRX quantity. The feature is activated from the 9130 BSC Evolution Terminal. For specific information about feature activation and usage, refer to BSS Methods Handbook , IURG section.

286 / 288




New

IURG_IP_SUBNET_MASK_BSC

New

IURG_PRIORITY

New

IURG_SCTP_ENDPOINT_IP_ADDRESS_1

New

IURG_SCTP_ENDPOINT_IP_ADDRESS_2

New

IURG_SCTP_ENDPOINT_LIST

New

IURG_SCTP_ENDPOINT_PORT

New

CELL_CAPACITY_CLASS_SOURCE

New

EN_IURG

New

LOCAL_IURG_SCTP_ENDPOINT_IP_ADDRESS_1 New


LOCAL_IURG_SCTP_ENDPOINT_PORT

New

MAX_NB_IURG_SCTP_ENDPOINT

New

RNC_MIN_NB_ACTIVE_IPSP

New

RNC_SPC

New

START_IURG_IP_ADDRESS_BSC

New

RNC_TRAFFIC_MODE

New

RNC_Name

New

RNC_ID

New

REACHABILITY_TEST_ADDR_IURG (BSC)

New

MAX_NB_RNC

New

ASIG_IP_SUBNET_MASK_BSC

Modified

BSS_IP_SUBNET_MASK_BSC

Modified

START_ASIG_IP_ADDRESS_BSC

Modified

START_BSS_IP_ADDRESS_BSC

Modified

VLAN_CONF_INDEX (BSC)

Modified

287 / 288

ALU B11 Features

Recommend Documents