New Features in Release B11 216090000e29

Alcatel-Lucent GSM
New Features
in Release B11
BSS Document
Concept Guide
Release B11
3BK 21609 AAAA TQZZA Ed.29

BLANK PAGE BREAK
Status RELEASED
Short title Concept Guide

All rights reserved. Passing on and copying of this document, use
and communication of its contents not permitted without written
authorization from Alcatel-Lucent.
2 / 344 3BK 21609 AAAA TQZZA Ed.29

Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1 B11 Features Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.1 Document Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.2 B11 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2 AMR Signalling Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.2 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.3 Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.5 Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.6 LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.7 Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3 Improved Packet Connection Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4 Avoid Ping-Pong between CS and PS Zones for DTM MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5 CS Paging Coordination in the BSS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6 Migration and Software Replacement Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3BK 21609 AAAA TQZZA Ed.29 3 / 344

Contents
6.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

6.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7 BSS Software Management Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
8 Lock Configuration Actions during SW Replacement Procedure in the OMC-R . . . . . . . . . . . . . . 57
8.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
9 AS 800 MFS not Supported in B11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
9.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
9.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
9.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
9.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
10 Removal of the Support of BTS with DRFU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
10.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
10.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
10.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
10.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
11 A5/3 Ciphering Algorithm Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
11.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
11.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
11.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
11.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
12 Edit n Adjacencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4 / 344 3BK 21609 AAAA TQZZA Ed.29

Contents
12.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
12.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
12.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
12.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
13 Copy&Paste of Data in OMC-R Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
13.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
13.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
13.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
13.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
14 Customization of BTS External Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
14.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
14.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
14.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
14.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
15 Change Granularity for Customization of BTS External Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
15.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
15.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
15.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
15.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
16 Clean Management of Reselection Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
16.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
16.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
16.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
16.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
17 New GSL Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
17.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
17.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3BK 21609 AAAA TQZZA Ed.29 5 / 344

Contents

17.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
17.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
18 SEC Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
18.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
18.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
18.6 LMT / OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
18.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
18.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
19 Load Indicators for OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
19.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
19.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
19.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
19.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
20 Centralized Licence Server and Time Validity for Optional Features . . . . . . . . . . . . . . . . . . . . . . . . . 89
20.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
20.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
20.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
20.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
21 TRX Dynamic Power Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
21.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
21.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
21.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
21.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
22 Adjust of BTS Power Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
22.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
22.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
22.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
22.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
6 / 344 3BK 21609 AAAA TQZZA Ed.29

Contents
23 Support of Windows Vista for PC LMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

23.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
23.2 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
23.3 Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
23.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
23.5 Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
23.6 LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
23.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
23.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
23.7 Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
24 Support of TFO on NB-AMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
24.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
24.2 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
24.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
24.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
24.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
25 A-Flex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
25.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
25.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
25.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
25.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
26 A Signalling over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
26.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
26.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
26.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
26.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
27 New ALMAP FM Module Replacing AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
27.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
27.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
27.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
27.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
28 Inter-BSS NACC/ Inter-RAT NACC (3G- ->2G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
28.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
3BK 21609 AAAA TQZZA Ed.29 7 / 344

Contents
28.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

28.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
28.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
29 New SUN HW Platform for OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
29.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
29.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
29.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
29.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
30 OMC-R Compatible with SAN Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
30.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
30.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
30.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
30.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
31 New OMC-R Restore Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
31.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
31.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
31.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
31.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
32 STM1 on 9130 BSC Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
32.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
32.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
32.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
32.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
33 Full Gb over IP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
33.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
33.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
33.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
33.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
8 / 344 3BK 21609 AAAA TQZZA Ed.29

Contents

34 Lock of Additional Optional Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
34.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
34.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
34.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
34.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
35 Broadcast Other Value than CI in SYSINFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
35.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
35.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
35.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
35.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
36 Enhanced 2G to 3G FDD/TDD Cell Re-selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
36.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
36.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
36.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
36.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
37 Investigation Based on Permanent Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
37.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
37.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
37.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
37.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
38 Antenna Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
38.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
38.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
38.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
38.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
39 Randomisation of Fill Bits in L2 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
39.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
3BK 21609 AAAA TQZZA Ed.29 9 / 344

Contents

39.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
39.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
39.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
40 Introduction of CF F8 LMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
40.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
40.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
40.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
40.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
41 MC-TRX 900Mhz TDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
41.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
41.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
41.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
41.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
42 RMS Improvement: Increase of the 42 BCCH-BSIC Pairs Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
42.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
42.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
42.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
42.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
43 2 BTS Configuration within 2 Integrated SUMA Boards in 1 BTS Cabinet . . . . . . . . . . . . . . . . . . . 173
43.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
43.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
43.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
43.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
44 Support of MC-TRX 900 Multistandard: Separate 2G and 3G carriers in same cabinet TDM . 175
44.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
44.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
44.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
10 / 344 3BK 21609 AAAA TQZZA Ed.29

Contents
44.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

45 Dynamic Power Voltage Adjustment (DPVA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
45.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
45.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
45.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
45.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
46 Network Synchronization of Radio TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
46.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
46.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
46.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
46.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
47 IP Transport in the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
47.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
47.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
47.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
47.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
48 Remote BTS NEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
48.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
48.2 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
48.3 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
48.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
48.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
49 Layer 2 Network Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
49.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
49.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
49.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
49.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
50 Security Enhancements for IP Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
50.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
3BK 21609 AAAA TQZZA Ed.29 11 / 344

Contents

50.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
50.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
50.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
51 Logging of BTS Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
51.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
51.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
51.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
51.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
52 Ethernet Installation Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
52.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
52.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
52.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
52.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
53 3G Search Prio Wrong in PMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
53.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
53.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
53.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
53.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
54 Support of Sftp in the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
54.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
54.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
54.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
54.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
55 IP Flow Separation at Physical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
55.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
55.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
55.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
12 / 344 3BK 21609 AAAA TQZZA Ed.29

Contents
55.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

56 AMR WB Cell Load Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
56.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
56.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
56.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
56.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
57 Interworking with LTE in the Packet Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
57.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
57.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
57.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
57.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
58 2G to LTE (TDD) Cell Re-selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
58.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
58.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
58.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
58.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
59 Remove Mx Firmware from Hardware Status for BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
59.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
59.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
59.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
59.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
60 Remove Mx Firmware from Hardware Status for MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
60.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
60.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
60.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
60.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
61 Bidirectional Forwarding Detection (BFD) Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
61.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
3BK 21609 AAAA TQZZA Ed.29 13 / 344

Contents

61.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
61.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
61.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
62 MC-RRH 900Mhz 2PA TDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
62.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
62.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
62.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
62.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
63 MC-RRH 900 - 2G/3G - Different PA - Separate 2G and 3G carriers in same module . . . . . . . . . 263
63.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
63.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
63.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
63.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
64 9130 BSC Evolution Availability Improvement. Weekly Standby Reset. . . . . . . . . . . . . . . . . . . . . . 267
64.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
64.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
64.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
64.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
65 Gb flex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
65.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
65.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
65.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
65.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
66 STM1 Bidirectional on 9125 TC Equipped with TC STM1-IP Subrack . . . . . . . . . . . . . . . . . . . . . . . . 275
66.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
66.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
14 / 344 3BK 21609 AAAA TQZZA Ed.29

Contents
66.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

66.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
67 BTS Synchronization Through NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
67.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
67.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
67.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
67.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
68 CS/PS Outage Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
68.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
68.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
68.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
68.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
69 OMCP-OMC Supervision Link Defense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
69.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
69.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
69.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
69.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
70 TP Init Auto Test Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
70.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
70.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
70.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
70.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
71 Management of BSC patches (Step 1: BSC Term only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
71.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
71.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
71.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
71.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
72 MC-Modules hardware capacity licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
3BK 21609 AAAA TQZZA Ed.29 15 / 344

Contents
72.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

72.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
72.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
72.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
73 Improved Multi-GPU Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
73.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
73.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
73.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
73.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
74 Iur-g Interface with Enhanced Control Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
74.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
74.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
74.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
74.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
75 Support of Lb Interface by the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
75.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
75.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
75.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
75.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
76 MC-TRX 1800Mhz TDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
76.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
76.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
76.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
76.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
77 Customization of IconBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
77.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
77.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
16 / 344 3BK 21609 AAAA TQZZA Ed.29

Contents

77.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
77.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
78 15 BSSUSM Windows per BSSUSM Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
78.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
78.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
78.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
78.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
79 MC-TRX 900 - 2G - IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
79.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
79.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
79.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
79.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
80 MC-TRX 900 - 3G - IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
80.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
80.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
80.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
80.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
81 MC-TRX 1800 - 2G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
81.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
81.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
81.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
81.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
82 MC-RRH 1800 - 2G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
82.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
82.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
82.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
82.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
3BK 21609 AAAA TQZZA Ed.29 17 / 344

Contents
83 MC-RRH 900 - 2G - 1 PA - TDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

83.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
83.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
83.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
83.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
84 MC-RRH 900 - 2G -1 PA - IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
84.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
84.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
84.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
84.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
85 MC-RRH 900 - 2G/3G - Different PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
85.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
85.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
85.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
85.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
86 Stop Supporting Sun V880 as OMC-R Hardware in B11 MR3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
86.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
86.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
86.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
86.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
87 Management of BSC patches (Step 2: full) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
87.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
87.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
87.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
87.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
88 Additional QoS basic alerters delivered by default (circuit part) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
88.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
18 / 344 3BK 21609 AAAA TQZZA Ed.29

Contents
88.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

88.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
88.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
89 Support of MC-TRX 900 Multistandard: Separate 2G and 3G Modules in Same Cabinet IP . . . 341
89.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
89.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
89.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
89.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
90 Provide E1 Clock Out from BTS for NodeB Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
90.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
90.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
90.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
90.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
3BK 21609 AAAA TQZZA Ed.29 19 / 344

Contents
20 / 344 3BK 21609 AAAA TQZZA Ed.29

Preface
Preface
Purpose 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.
Document Pertinence 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 28

Provide E1 Clock Out from BTS for NodeB Synchronization (Section 90)
was added.
Additional QoS basic alerters delivered by default (circuit part) (Section 88)
was added.
Support of MC-TRX 900 Multistandard: Separate 2G and 3G Modules in Same
Cabinet IP (Section 89) was added.
Management of BSC patches (Step 2: full) (Section 87) was added.
2G to LTE (TDD) Cell Re-selection (Section 58) was added.
Description improvement in Security Enhancements for IP Introduction (Section
50).
In Edition 27
The section MC-TRX 900 - 2G - IP (Section 79) was added.
The section MC-TRX 900 - 3G - IP (Section 80) was added.
The section MC-TRX 1800 - 2G (Section 81) was added.
The section MC-RRH 1800 - 2G (Section 82) was added.
The section MC-RRH 900 - 2G - 1 PA - TDM (Section 83) was added.
The section MC-RRH 900 - 2G -1 PA - IP (Section 84) was added.
3BK 21609 AAAA TQZZA Ed.29 21 / 344

Preface
The section MC-RRH 900 - 2G/3G - Different PA (Section 85) was added.
Description improvement in Feature Activation (Section 57.3).
The section Customization of IconBox (Section 77) was added.
The section 15 BSSUSM Windows per BSSUSM Controller (Section 78)
was added.
The section Stop Supporting Sun V880 as OMC-R Hardware in B11 MR3
(Section 86) was added.
In Edition 26
Updates performed in Improved Multi-GPU Performance (Section 73) .
Updates performed in Iur-g Interface with Enhanced Control Plane (Section 74).
In Edition 25
Description introduction in MC-TRX 1800Mhz TDM (Section 76).
Description improvement due to MC-TRX 900MHz TDM (Power Supply Voltage
Switching) in Dynamic Power Voltage Adjustment (DPVA) (Section 45).
Support of Lb Interface by the BSC (Section 75) was added.
Description improvement done in Remove Mx Firmware from Hardware Status
for MFS (Section 60).
In Edition 24
Description improvement in Support of MC-TRX 900 Multistandard: Separate
2G and 3G carriers in same cabinet TDM (Section 44).
The following MC-RRH 900Mhz 2PA TDM (Section 62) is improved due to
MC RRH new information.
Improvement performed in Iur-g Interface with Enhanced Control Plane
(Section 74).
In Edition 23
Iur-g Interface with Enhanced Control Plane (Section 74) 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 Firmware from Hardware Status for
MFS (Section 60).
In Edition 20
Description improvement in MC-RRH 900 - 2G/3G - Different PA - Separate
2G and 3G carriers in same module (Section 63).
In Edition 19
Description improvements in IP Flow Separation at Physical Level (Section 55).
22 / 344 3BK 21609 AAAA TQZZA Ed.29

Preface
In Edition 18
Section Improved Multi-GPU Performance (Section 73) was added.
Description improvements in MC-RRH 900Mhz 2PA TDM (Section 62).
In Edition 17
Description improvement in 2 BTS Configuration within 2 Integrated SUMA
Boards in 1 BTS Cabinet (Section 43) and Remove Mx Firmware from
Hardware Status for MFS (Section 60).
MC-Modules hardware capacity licensing (Section 72) was added.
In Edition 16
Description improvement in RMS Improvement: Increase of the 42 BCCH-BSIC
Pairs Limit (Section 42).
In Edition 15
Description improvement in Remove Mx Firmware from Hardware Status for
MFS (Section 60).
In Edition 14
Description improvement performed in Interworking with LTE in the Packet
Domain (Section 57)
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 Bidirectional on 9125 TC Equipped with
TC STM1-IP Subrack (Section 66).
In Edition 12
Description improvement.
In Edition 11
Improvements were done in:
AMR WB Cell Load Handling (Section 56)
B11 Features (Section 1.2)
Hardware Coverage (Section 53.2)
IP Flow Separation at Physical Level (Section 55)
In Edition 10
Improvement done in Support of TFO on NB-AMR (Section 24).
The following MC-TRX 900Mhz TDM (Section 41) was updated due to MC
TRE module introduction.
In Edition 09
New section Management of BSC patches (Step 1: BSC Term only) (Section
71) was created.
3BK 21609 AAAA TQZZA Ed.29 23 / 344

Preface
Improvement done in 3G Search Prio Wrong in PMO (Section 53).

Updates performed in Interworking with LTE in the Packet Domain (Section 57).
In Edition 08
The following section were added:
Gb flex (Section 65)
STM1 Bidirectional on 9125 TC Equipped with TC STM1-IP Subrack

(Section 66)
BTS Synchronization Through NTP (Section 67).
In Edition 07
The Network Synchronization of Radio TS (Section 46) section was added.
Description improvement in Description (Section 61.1).
In Edition 06
The section 9130 BSC Evolution Availability Improvement. Weekly Standby
Reset. (Section 64) 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 57.4)
New features for B11 MR3:
Remove Mx Firmware from Hardware Status for BSC (Section 59),
Remove Mx Firmware from Hardware Status for MFS (Section 60)
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 55)
Customization of BTS External Alarms (Section 14)
In Edition 02
Improvements were done in the following section Counters and Indicators
(Section 17.5)
This document contains information about the following new feature 3G Search
Prio wrong in PMO in 3G Search Prio Wrong in PMO (Section 53).
24 / 344 3BK 21609 AAAA TQZZA Ed.29

Preface
In Edition 01
First official release of the document.
3BK 21609 AAAA TQZZA Ed.29 25 / 344

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.
26 / 344 3BK 21609 AAAA TQZZA Ed.29

1 B11 Features Overview
This section presents:
The document structure
An overview of the Release B11 features.
3BK 21609 AAAA TQZZA Ed.29 27 / 344

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.
28 / 344 3BK 21609 AAAA TQZZA Ed.29

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 Configuration Actions during SW Replacement Procedure in MR1

the OMC-R (Section 8)
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 MR1
(Section 20)
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
3BK 21609 AAAA TQZZA Ed.29 29 / 344

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 MR1

parameter modifications
Additional operational information in GCD feature descriptions (***) MR1
GCD Counter and Indicator Dictionary: Additional information for MR1

each counter and indicator on the related feature
Documentation of all system, feature and procedure changes in the MR1

new release (***)
Ethernet Installation Kit MR1
CMCC Q3 interface (*) MR1
Ilog 5.1 introduction due to 5.0 EOL (*) MR1
30 / 344 3BK 21609 AAAA TQZZA Ed.29

SUMx remote firmware upgrade (*) MR1
Support of Sftp in the OMC (Section 54) 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 55) 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-TRX 900Mhz TDM (Section 41) MR1Ed2
RMS Improvement: Increase of the 42 BCCH-BSIC Pairs Limit MR1Ed2

(Section 42)
2 BTS Configuration within 2 Integrated SUMA Boards in 1 BTS MR1Ed2

Cabinet (Section 43)
Support of MC-TRX 900 Multistandard: Separate 2G and 3G carriers MR1Ed3

in same cabinet TDM (Section 44)
Dynamic Power Voltage Adjustment (DPVA) (Section 45) MR1Ed3
Gb flex (Section 65) MR3
BTS Synchronization Through NTP (Section 67) MR3
IP over Ethernet on Abis and Ater in IP Transport in the BSS (Section MR3
47)
Remote BTS NEM (Section 48) MR3
Layer 2 Network Access (Section 49) MR3
Security Enhancements for IP Introduction (Section 50) MR3
Logging of BTS Temperature (Section 51) MR3
Remote switching BTS Abis connection MR3
PM differentiation Packet User Traffic/Signalling, GPRS/EDGE MR3
3G Search Prio Wrong in PMO (Section 53) MR3/MR1Ed2
3BK 21609 AAAA TQZZA Ed.29 31 / 344

AMR WB Cell Load Handling (Section 56) MR3
Interworking with LTE in the Packet Domain (Section 57) MR1Ed2/MR3
2G to LTE (TDD) Cell Re-selection (Section 58) MR3Ed2
Remove Mx Firmware from Hardware Status for BSC (Section 59) MR1Ed2/MR3
Remove Mx Firmware from Hardware Status for MFS (Section 60) MR1Ed2/MR3
Change Granularity for Customization of BTS External Alarms MR3

(Section 15)
Bidirectional Forwarding Detection (BFD) Protocol (Section 61) MR3
MC-RRH 900Mhz 2PA TDM (Section 62) MR3Ed1
MC-RRH 900 - 2G/3G - Different PA - Separate 2G and 3G carriers MR3Ed2.0

in same module (Section 63)
Management of BSC patches (Step 1: BSC Term only) (Section 71) MR1Ed2
9130 BSC Evolution Availability Improvement. Weekly Standby MR1Ed2

Reset. (Section 64)
STM1 Bidirectional on 9125 TC Equipped with TC STM1-IP Subrack MR1Ed2

(Section 66)
CS/PS Outage Detection (Section 68) MR1Ed2
OMCP-OMC Supervision Link Defense (Section 69) MR1Ed2
TP Init Auto Test Improvements (Section 70) MR1Ed2/MR3
Introduction of CF F8 LMT (Section 40) MR1Ed2
MC-Modules hardware capacity licensing (Section 72) MR1Ed2.1
Iur-g Interface with Enhanced Control Plane (Section 74) MR1Ed2.2
MC-TRX 1800Mhz TDM (Section 76) MR3Ed1.1
Customization of IconBox (Section 77) MR3Ed2
15 BSSUSM Windows per BSSUSM Controller (Section 78) MR3Ed2
MC-TRX 900 - 2G - IP (Section 79) MR3Ed2
MC-TRX 900 - 3G - IP (Section 80) MR3Ed2
MC-TRX 1800 - 2G (Section 81) MR3Ed2
MC-RRH 1800 - 2G (Section 82) MR3Ed2
MC-RRH 900 - 2G - 1 PA - TDM (Section 83) MR3Ed2
32 / 344 3BK 21609 AAAA TQZZA Ed.29

MC-RRH 900 - 2G -1 PA - IP (Section 84) MR3Ed2
MC-RRH 900 - 2G/3G - Different PA (Section 85) MR3Ed2
Stop Supporting Sun V880 as OMC-R Hardware in B11 MR3 MR3Ed2

(Section 86)
Support of MC-TRX 900 Multistandard: Separate 2G and 3G MR3Ed2

Modules in Same Cabinet IP (Section 89)
Provide E1 Clock Out from BTS for NodeB Synchronization (Section MR3Ed2
90)
(*) : 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
3BK 21609 AAAA TQZZA Ed.29 33 / 344

34 / 344 3BK 21609 AAAA TQZZA Ed.29

2 AMR Signalling Modifications
3BK 21609 AAAA TQZZA Ed.29 35 / 344

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.
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
36 / 344 3BK 21609 AAAA TQZZA Ed.29

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.
3BK 21609 AAAA TQZZA Ed.29 37 / 344

38 / 344 3BK 21609 AAAA TQZZA Ed.29

3 Improved Packet Connection Configurations
3BK 21609 AAAA TQZZA Ed.29 39 / 344

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

The feature is not NE dependent.

For specific information about the feature activation, refer to Network
Reconfiguration Recommendations, to Improved Packet Connection
Configurations.
3.4 Parameters
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).
40 / 344 3BK 21609 AAAA TQZZA Ed.29

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.

There are no counter and indicator modifications.

3.6.1 LMT Updates

Functional and Graphical Evolutions, to:
RNUSM: Edit BSS Telecom Parameters - Radio Res. Mngt. View
RNUSM: Edit Cell Window - Radio Res. Ctrl View.


3BK 21609 AAAA TQZZA Ed.29 41 / 344

42 / 344 3BK 21609 AAAA TQZZA Ed.29

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

MS
3BK 21609 AAAA TQZZA Ed.29 43 / 344

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.

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

The feature is not optional.
Reconfiguration Recommendations, to Avoid Ping Pong between CS and
PS Zone.
4.4 Parameters
deployment.
Name New
N_DELAYED_HO_CAUSE30 New
MC482 NB_TCH_HO_REQ_30_ABORTED

4.6.1 LMT Updates

Functional and Graphical Evolutions, to "GENERAL HO CONTROL" Window.
44 / 344 3BK 21609 AAAA TQZZA Ed.29


3BK 21609 AAAA TQZZA Ed.29 45 / 344

46 / 344 3BK 21609 AAAA TQZZA Ed.29

5 CS Paging Coordination in the BSS Support
3BK 21609 AAAA TQZZA Ed.29 47 / 344

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.


Reconfiguration Recommendations, to Support of Paging Coordination in
the BSS.
5.4 Parameters
deployment.
Name New
EN_BSS_PAGING_COORDINATION (BSC) New
EN_BSS_PAGING_COORDINATION (MFS) New

P390a NB_BSS_CS_PAGING_REQ_GPU
P390b NB_CS_PAGING_REQ_PACCH

5.6.1 LMT Updates

Functional and Graphical Evolutions, to "GPRS GENERAL" Window.
48 / 344 3BK 21609 AAAA TQZZA Ed.29


3BK 21609 AAAA TQZZA Ed.29 49 / 344

50 / 344 3BK 21609 AAAA TQZZA Ed.29

6 Migration and Software Replacement Modifications
3BK 21609 AAAA TQZZA Ed.29 51 / 344

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.

The features are partially dependent on the 9130 BSC Evolution.

The features are not optional.
6.4 Parameters
There are no parameter modifications.


6.6.1 LMT Updates

There are no OMC HMI modifications.

B10/B11 MFS/TC/BSS Software Migration
B11/B11 MFS/TC/BSS Software Replacement.
52 / 344 3BK 21609 AAAA TQZZA Ed.29

7 BSS Software Management Modifications
3BK 21609 AAAA TQZZA Ed.29 53 / 344

7.1 Description
This feature brings the following modifications:
A single command for launching a series of previously selected actions

required for the BSS 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 in progress
An automatic report at end of the migration that offers a quick and easy
view of the BSS state after the software change in comparison with its initial
state (before the software change).

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

The features are not optional.
7.4 Parameters


7.6.1 LMT Updates

For specific information about the OMC HMI, refer to 9153 OMC-R Functional
and Graphical Evolutions, to BSSUSM : Software Management.
54 / 344 3BK 21609 AAAA TQZZA Ed.29



BSS Configuration Handbook
Operations & Maintenance Principles.
3BK 21609 AAAA TQZZA Ed.29 55 / 344

56 / 344 3BK 21609 AAAA TQZZA Ed.29

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

Procedure in the OMC-R
3BK 21609 AAAA TQZZA Ed.29 57 / 344

8 Lock Configuration Actions during SW Replacement Procedure in the OMC-R
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.

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

8.4 Parameters


8.6.1 LMT Updates


58 / 344 3BK 21609 AAAA TQZZA Ed.29

9 AS 800 MFS not Supported in B11
3BK 21609 AAAA TQZZA Ed.29 59 / 344

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.

Not applicable.

The feature is mandatory in Release B11, therefore there is no activation
scenario.
9.4 Parameters
There are no new or modified parameters.


9.6.1 LMT Updates


9135 MFS Maintenance Handbook
9135 MFS Software Installation
Network Reconfiguration Recommendations
9135 MFS Description
BSS Configuration Rules

9130 MFS Evolution Commissioning Manual.
60 / 344 3BK 21609 AAAA TQZZA Ed.29

10 Removal of the Support of BTS with DRFU
3BK 21609 AAAA TQZZA Ed.29 61 / 344

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.

Not applicable.

There is no activation scenario for this feature.
10.4 Parameters


10.6.1 LMT Updates


The following GCD documents are impacted by the feature:
BSS Preventive Maintenance Handbook

Engineering Rules for LMT
Operations & Maintenance Principles
BSS Overview
BSS Methods Handbook
BTS Alarm Dictionary
62 / 344 3BK 21609 AAAA TQZZA Ed.29

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.
3BK 21609 AAAA TQZZA Ed.29 63 / 344

64 / 344 3BK 21609 AAAA TQZZA Ed.29

11 A5/3 Ciphering Algorithm Support
3BK 21609 AAAA TQZZA Ed.29 65 / 344

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.

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.

Reconfiguration Recommendations, to Support of A5/3 Ciphering Algorithm.
11.4 Parameters
deployment.
Name New
CELL_CIPH_SET New
TRX_CIPH_CAP New
TRE_CIPH_CAP New

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
66 / 344 3BK 21609 AAAA TQZZA Ed.29


11.6.1 LMT Updates

Functional and Graphical Evolutions. The following sections are updated:
RNUSM: Network Information Window
RNUSM: Edit Cell Window
BSSUSM: Modify BTS Characteristics Window.


BSS Overview.
3BK 21609 AAAA TQZZA Ed.29 67 / 344

68 / 344 3BK 21609 AAAA TQZZA Ed.29

12 Edit n Adjacencies
3BK 21609 AAAA TQZZA Ed.29 69 / 344

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.4 Parameters


12.6.1 LMT Updates

Functional and Graphical Evolutions, toRNUSM Edit N Adjs Window.

BSS Configuration Handbook.
70 / 344 3BK 21609 AAAA TQZZA Ed.29

13 Copy&Paste of Data in OMC-R Forms
3BK 21609 AAAA TQZZA Ed.29 71 / 344

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.4 Parameters

There are no counters and indicators improvements.

13.6.1 LMT Updates
There are no LMT HMI improvements

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

The impacted document by the feature is 9153 OMC-R Functional and
Graphical Evolutions
72 / 344 3BK 21609 AAAA TQZZA Ed.29

14 Customization of BTS External Alarms
3BK 21609 AAAA TQZZA Ed.29 73 / 344

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.


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.1 LMT Updates
There are no LMT modifications

Functional and Graphical Evolutions.

BSS Surveillance Handbook

9153 OMC-R Getting Started.
74 / 344 3BK 21609 AAAA TQZZA Ed.29

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.
3BK 21609 AAAA TQZZA Ed.29 75 / 344

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.


The feature is optional. For specific information about the feature functionality,
refer to the BSS Surveillance Handbook.
15.4 Parameters

There are no new or modified counters and indicators

15.6.1 LMT Updates

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

BSS Surveillance Handbook.
76 / 344 3BK 21609 AAAA TQZZA Ed.29

16 Clean Management of Reselection Links
3BK 21609 AAAA TQZZA Ed.29 77 / 344

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


The feature activation is made virtually in the OMC-R.
16.4 Parameters
deployment.
Name New
Link-Type-2G New


16.6.1 LMT Updates


The BSS Overview is impacted by the feature.
78 / 344 3BK 21609 AAAA TQZZA Ed.29

17 New GSL Counters
17 New GSL Counters
3BK 21609 AAAA TQZZA Ed.29 79 / 344

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.

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.

The feature is optional.
17.4 Parameters

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.
80 / 344 3BK 21609 AAAA TQZZA Ed.29

17 New GSL Counters
The following table presents the new GSL counters for a BSC in TDM or
IP mode.

for BSC in TDM/IP Mode
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:
P7a NB_BSCGP_MSG_SENT
P7b NB_BSCGP_MSG_DISCARDED
3BK 21609 AAAA TQZZA Ed.29 81 / 344

17 New GSL Counters
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:
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
82 / 344 3BK 21609 AAAA TQZZA Ed.29

17 New GSL Counters
P509a NB_DTM_CS_DL_TBF_RELEASE_EGPRS
P510a NB_DTM_CS_UL_TBF_RELEASE_EGPRS
Table 5: PS couters for MR3
3BK 21609 AAAA TQZZA Ed.29 83 / 344

17 New GSL Counters

17.6.1 LMT Updates


The document impacted by the feature is Quality of Service Alerters User Guide.
84 / 344 3BK 21609 AAAA TQZZA Ed.29

18 SEC Command Line Interface
3BK 21609 AAAA TQZZA Ed.29 85 / 344

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.4 Parameters

18.6 LMT / OMC HMI Updates

18.6.1 LMT Updates

There are not OMC HMI updates.

9153 OMC-R Getting Started
9153 OMC-R Command Mode.
86 / 344 3BK 21609 AAAA TQZZA Ed.29

19 Load Indicators for OMC-R
3BK 21609 AAAA TQZZA Ed.29 87 / 344

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.4 Parameters


19.6.1 LMT Updates

Functional and Graphical Evolutions, to OMC-R Load Indicators Window.

9153 OMC-R Network Administration Handbook
9153 OMC-R Functional and Graphical Evolutions.
88 / 344 3BK 21609 AAAA TQZZA Ed.29

20 Centralized Licence Server and Time Validity for Optional Features
20 Centralized Licence Server and Time Validity for

Optional Features
3BK 21609 AAAA TQZZA Ed.29 89 / 344

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.1 LMT Updates

Functional and Graphical Evolutions, to DSMUSM Window.
90 / 344 3BK 21609 AAAA TQZZA Ed.29


B11/B11 9153 OMC-R Software Replacement
B10/B11 9153 OMC-R Software Migration

9153 OMC-R Methods Handbook
Optional Features Activation on Running 9153 OMC-R
9153 OMC-R Installation
Site Preparation Sheet.
3BK 21609 AAAA TQZZA Ed.29 91 / 344

92 / 344 3BK 21609 AAAA TQZZA Ed.29

21 TRX Dynamic Power Saving
3BK 21609 AAAA TQZZA Ed.29 93 / 344

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.

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

Reconfiguration Recommendations, to TRX Dynamic Power Saving.
21.4 Parameters
deployment.
Name New
EN_POWER_SAVING New
MC957 TIME_TS_BUSY
MC958 TIME_PA_BIAS_ON

21.6.1 LMT Updates

Functional and Graphical Evolutions, to RNUSM: Edit Cell View.
94 / 344 3BK 21609 AAAA TQZZA Ed.29



BSS Overview
BSS Configuration Rules.
3BK 21609 AAAA TQZZA Ed.29 95 / 344

96 / 344 3BK 21609 AAAA TQZZA Ed.29

22 Adjust of BTS Power Level
3BK 21609 AAAA TQZZA Ed.29 97 / 344

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.1 LMT Updates

Functional and Graphical Evolutions, to RNUSM: Edit Cell View.

BSS Overview
Replace Non Alcatel-Lucent BTS with Alcatel-Lucent BTS.
98 / 344 3BK 21609 AAAA TQZZA Ed.29

23 Support of Windows Vista for PC LMT
3BK 21609 AAAA TQZZA Ed.29 99 / 344

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

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.4 Parameters


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

100 / 344 3BK 21609 AAAA TQZZA Ed.29


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

Move BTS/Abis in Same BSC.
3BK 21609 AAAA TQZZA Ed.29 101 / 344

102 / 344 3BK 21609 AAAA TQZZA Ed.29

24 Support of TFO on NB-AMR
3BK 21609 AAAA TQZZA Ed.29 103 / 344

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.

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.

To activate TFO on NB-AMR, refer to the Network Reconfiguration
Recommendations , to Support of TFO on NB-AMR.
24.4 Parameters
deployment.
Name New
PREF_CONFIG_FR_AMR_NB New
PREF_CONFIG_HR_AMR_NB New
EN_TFO_AMR_NB New
EN_TFO_MATCH Modified

The TFO for AMR-NB introduces the following BSC counters.
MC938 NB_CALL_TFO_AMR_WB
MC939 NB_HO_INTER_TFO_AMR_WB
MC950 NB_HO_EXT_TFO_AMR_WB
104 / 344 3BK 21609 AAAA TQZZA Ed.29


24.6.1 LMT 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.


BSS Overview.
3BK 21609 AAAA TQZZA Ed.29 105 / 344

106 / 344 3BK 21609 AAAA TQZZA Ed.29

25 A-Flex
25 A-Flex
3BK 21609 AAAA TQZZA Ed.29 107 / 344

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.

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

To activate A-Flex, refer to the Reconfigure BSC/MSC.
25.4 Parameters
deployment.
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
108 / 344 3BK 21609 AAAA TQZZA Ed.29

25 A-Flex
Name New
OFFLOADED New
NULL_NRI New

A-Flex introduces the following BSC counters.
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.
P53d NB_CS_PAGING_WITH_GLOBAL_CN_ID_PCH
3BK 21609 AAAA TQZZA Ed.29 109 / 344

25 A-Flex

25.6.1 LMT Updates

Functional and Graphical Evolutions, to BSSUSM: BSS Parameters.


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.
110 / 344 3BK 21609 AAAA TQZZA Ed.29

26 A Signalling over IP
3BK 21609 AAAA TQZZA Ed.29 111 / 344

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.

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

To activate A Signalling over IP, refer to Modify N7 Transport Mode for 9130
BSC Evolution.
26.4 Parameters
deployment.
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
112 / 344 3BK 21609 AAAA TQZZA Ed.29

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

A-Flex introduces the following BSC counters.
MC1101 NB_ASPUP_TX
MC1102 NB_ASPUP_RX
MC1103 NB_ASPDOWN_TX
MC1104 NB_ASPDOWN_RX
MC1105 NB_ASPACTIVE_TX
3BK 21609 AAAA TQZZA Ed.29 113 / 344

MC1106 NB_ASPACTIVE_RX
MC1107 NB_ASPINACTIVE_TX
MC1108 NB_ASPINACTIVE_RX
A Signalling over IP does not introduce any MFS counter.

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.



BSS Overview
Which Scenario to Use.
Modify N7 Transport Mode for BSC Evolution


Move 9130 BSC Evolution, Different MFS, Same MSC, Same 9153 OMC-R.
114 / 344 3BK 21609 AAAA TQZZA Ed.29

27 New ALMAP FM Module Replacing AS
3BK 21609 AAAA TQZZA Ed.29 115 / 344

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.


The feature is not optional. There is no activation scenario for this feature.
27.4 Parameters


27.6.1 LMT Updates

Functional and Graphical Evolutions, to:
FM Current Alarms Window
FM Historical Alarms Management Window.
116 / 344 3BK 21609 AAAA TQZZA Ed.29


Alarm Call Out User Guide

BSS Overview
BSC & TC Alarm Dictionary

MFS Alarm Dictionary
Quality of Service Alerters User Guide
9125 Transcoder Alarm Dictionary.
3BK 21609 AAAA TQZZA Ed.29 117 / 344

118 / 344 3BK 21609 AAAA TQZZA Ed.29

28 Inter-BSS NACC/ Inter-RAT NACC (3G- ->2G)
3BK 21609 AAAA TQZZA Ed.29 119 / 344

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.


Reconfiguration Recommendations , to Inter-BSS NACC/ Inter-RAT NACC
(3G- ->2G).
28.4 Parameters
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
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
120 / 344 3BK 21609 AAAA TQZZA Ed.29


28.6.1 LMT Updates

Functional and Graphical Evolutions, to RNUSM: RIM-NACC View.


BSS Overview
9153 OMC-R Online Help.
3BK 21609 AAAA TQZZA Ed.29 121 / 344

122 / 344 3BK 21609 AAAA TQZZA Ed.29

29 New SUN HW Platform for OMC-R
3BK 21609 AAAA TQZZA Ed.29 123 / 344

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.

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

For M4000 configuration and OMC-R installation on the M4000 machine,
refer to 9153 OMC-R Installation.
29.4 Parameters


29.6.1 LMT Updates
No updates.

No updates.
124 / 344 3BK 21609 AAAA TQZZA Ed.29


Cabling Description for SUN Servers
LEGATO Installation and User Guide

9153 OMC-R Reconfigure Platform

9153 OMC-R Acceptance Tests.
3BK 21609 AAAA TQZZA Ed.29 125 / 344

126 / 344 3BK 21609 AAAA TQZZA Ed.29

30 OMC-R Compatible with SAN Architecture
3BK 21609 AAAA TQZZA Ed.29 127 / 344

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.

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.

The methods 9153 OMC-R Installation and 9153 OMC-R Network
Administration Handbook contain information about SAN compatibility with
9153 OMC-R.
30.4 Parameters
128 / 344 3BK 21609 AAAA TQZZA Ed.29



30.6.1 LMT Updates
No updates.

No updates.

3BK 21609 AAAA TQZZA Ed.29 129 / 344

130 / 344 3BK 21609 AAAA TQZZA Ed.29

31 New OMC-R Restore Strategy
3BK 21609 AAAA TQZZA Ed.29 131 / 344

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.

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.

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.4 Parameters


31.6.1 LMT Updates
No updates.

No updates.

LEGATO Installation and User Guide.
132 / 344 3BK 21609 AAAA TQZZA Ed.29

32 STM1 on 9130 BSC Evolution
3BK 21609 AAAA TQZZA Ed.29 133 / 344

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.

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

For specific information, refer to Activate/Deactivate STM1 Interface for 9130
BSC Evolution.
134 / 344 3BK 21609 AAAA TQZZA Ed.29

32.4 Parameters
deployment.
Name 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.1 LMT Updates
The LMT modifications are in the 9130 BSC Evolution Terminal User Guide.

The OMC HMI Updates are in the 9153 OMC-R Functional and Graphical
Evolution .
3BK 21609 AAAA TQZZA Ed.29 135 / 344


BSS Overview
9130 BSC Evolution Hardware Description

9130 BSC Evolution Functional Description
Network Reconfiguration Recommendation

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 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
9130 MFS/BSC Evolution Installation Manual
BSS O&M Routing Configurations
STM1 on 9130 BSC Evolution.
136 / 344 3BK 21609 AAAA TQZZA Ed.29

33 Full Gb over IP Option
3BK 21609 AAAA TQZZA Ed.29 137 / 344

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.4 Parameters


33.6.1 LMT Updates
No updates.

No updates.

138 / 344 3BK 21609 AAAA TQZZA Ed.29

34 Lock of Additional Optional Features
3BK 21609 AAAA TQZZA Ed.29 139 / 344

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.4 Parameters


34.6.1 LMT Updates
No updates.

The OMC HMI Updates are in the 9153 OMC-R Functional and Graphical
Evolution document, section RNUSM: Network Information Window
140 / 344 3BK 21609 AAAA TQZZA Ed.29


3BK 21609 AAAA TQZZA Ed.29 141 / 344

142 / 344 3BK 21609 AAAA TQZZA Ed.29

35 Broadcast Other Value than CI in SYSINFO
3BK 21609 AAAA TQZZA Ed.29 143 / 344

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.


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.
35.4 Parameters
deployment.
Name New
CI_SI New


35.6.1 LMT Updates

Functional and Graphical Evolutions, to RNUSM: Edit Cell Window.
144 / 344 3BK 21609 AAAA TQZZA Ed.29


BSS Overview
Add BTS, New Cell(s).
3BK 21609 AAAA TQZZA Ed.29 145 / 344

146 / 344 3BK 21609 AAAA TQZZA Ed.29

36 Enhanced 2G to 3G FDD/TDD Cell Re-selection
3BK 21609 AAAA TQZZA Ed.29 147 / 344

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

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.

36.4 Parameters
deployment.
Name 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

148 / 344 3BK 21609 AAAA TQZZA Ed.29


36.6.1 LMT Updates


BSS Overview

3BK 21609 AAAA TQZZA Ed.29 149 / 344

150 / 344 3BK 21609 AAAA TQZZA Ed.29

37 Investigation Based on Permanent Measurements
3BK 21609 AAAA TQZZA Ed.29 151 / 344

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

The feature is supported only by the 9130 BSC Evolution.

37.4 Parameters
deployment.
Name New
BSS identifier New
Reduced Accumulation Period New


37.6.1 LMT Updates

152 / 344 3BK 21609 AAAA TQZZA Ed.29


3BK 21609 AAAA TQZZA Ed.29 153 / 344

154 / 344 3BK 21609 AAAA TQZZA Ed.29

38 Antenna Hopping
38 Antenna Hopping
Note: This feature is available starting with MR1Ed2.
3BK 21609 AAAA TQZZA Ed.29 155 / 344

38 Antenna Hopping
38.1 Description
Antenna hopping means that the sequence of bursts comprising a radio block
are transmitted over more than one antenna. The purpose is to get 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 hopping.
The feature is intended to be provided by the twin module, and thus the number
of antennas for antenna hopping is two.

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

The feature is optional and can be activated at cell level.
For specific information, refer to Network Reconfiguration Recommendations,
section Antenna Hopping.
38.4 Parameters
deployment.
Name New
EN_ANTENNA_HOPPING New
TXDIV_CAPABILITY Modified


38.6.1 LMT Updates

156 / 344 3BK 21609 AAAA TQZZA Ed.29

38 Antenna Hopping


9100 BTS/9110 Micro BTS Functional Description
BSS Overview

Add TRE to Equipped 9100 BTS.
3BK 21609 AAAA TQZZA Ed.29 157 / 344

38 Antenna Hopping
158 / 344 3BK 21609 AAAA TQZZA Ed.29

39 Randomisation of Fill Bits in L2 Messages

3BK 21609 AAAA TQZZA Ed.29 159 / 344

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.

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

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.1 LMT Updates

Functional and Graphical Evolutions, to RNUSM: Ded. Radio Res 1/2.
160 / 344 3BK 21609 AAAA TQZZA Ed.29


3BK 21609 AAAA TQZZA Ed.29 161 / 344

162 / 344 3BK 21609 AAAA TQZZA Ed.29

40 Introduction of CF F8 LMT
3BK 21609 AAAA TQZZA Ed.29 163 / 344

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


40.4 Parameters


40.6.1 LMT Updates


The following document is impacted by the feature: Engineering Rules for LMT.
164 / 344 3BK 21609 AAAA TQZZA Ed.29

41 MC-TRX 900Mhz TDM

Note: This feature is available in MR1Ed2.
3BK 21609 AAAA TQZZA Ed.29 165 / 344

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.

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.

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:
Name New
Dynamic_Power_Allocation New
Additional_Power_Tables New
166 / 344 3BK 21609 AAAA TQZZA Ed.29


This section contains the new counters involved in feature deployment:
BSC Counters
MC1208 TIME_PWR_RED_8PSK_1
MC1212 TIME_PWR_RED_GMSK_1
MC1216 TIME_PWR_RED_DEFENSE_1
MC1220 TIME_8PSK_BURST_TRANSMISSION
MC1221 TIME_GMSK_BURST_TRANSMISSION
MC1222 TIME_DEFENSE_BURST_TRANSMISSION

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

Functional and Graphical Evolutions .

3BK 21609 AAAA TQZZA Ed.29 167 / 344


BTS NEM User Guide
Reconfigure TRE/Sectors, 9100 BTS

Upgrade 9100 BTS with AN/SUM/TRE Evolution Modules
Move BTS/Abis, Different BSC, Same OMC-R

Move BTS/Abis in same BSC
Add TRE to Equipped 9100 BTS
Delete TRE from Equipped 9100 BTS

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
168 / 344 3BK 21609 AAAA TQZZA Ed.29

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

Pairs Limit
3BK 21609 AAAA TQZZA Ed.29 169 / 344

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.

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

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.6.1 LMT Updates

Functional and Graphical Evolutions .

170 / 344 3BK 21609 AAAA TQZZA Ed.29


Network Reconfiguration Recommendations .
3BK 21609 AAAA TQZZA Ed.29 171 / 344

172 / 344 3BK 21609 AAAA TQZZA Ed.29

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
3BK 21609 AAAA TQZZA Ed.29 173 / 344

43 2 BTS Configuration within 2 Integrated SUMA Boards in 1 BTS Cabinet
43.1 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.

The feature is supported for: MBI5 shared BTS.

43.4 Parameters
There are no parameters modifications.


43.6.1 LMT Updates


Reconfigure TRE/Sectors, Monoband to Multiband Cell.

Extend Existing Cell(s) to Shared Cell(s) by 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.
174 / 344 3BK 21609 AAAA TQZZA Ed.29

44 Support of MC-TRX 900 Multistandard: Separate 2G and 3G carriers in same cabinet TDM
44 Support of MC-TRX 900 Multistandard: Separate 2G

and 3G carriers in same cabinet TDM
Note: This feature is available starting with B11 MR1ED3.
3BK 21609 AAAA TQZZA Ed.29 175 / 344

44.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.
The number of other standard modules in a given sector and in the band GSM
is entered by the operator at OMC-R.

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

The feature is activated as soon as the MC module is plugged in.
44.4 Parameters
deployment.
Name New
Nb other standard modules 900 MHz New
Nb other standard modules 1800 MHz New
Multi-PA TRE Load Sharing Mode New
PAR table New
176 / 344 3BK 21609 AAAA TQZZA Ed.29



44.6.1 LMT Updates
For specific information about the LMT modifications, refer to BTS NEM User
Guide.

Functional and Graphical Evolutions, sections BSSUSM: Modify BTS Remote
Settings and RNUSM: Network Information Window.

BTS NEM User Guide

CI 08 - Site Equipment Inventory



3BK 21609 AAAA TQZZA Ed.29 177 / 344


9100 BTS Acceptance Manual.
178 / 344 3BK 21609 AAAA TQZZA Ed.29

45 Dynamic Power Voltage Adjustment (DPVA)

Note: This feature is available starting with B11 MR3ED1.1.
3BK 21609 AAAA TQZZA Ed.29 179 / 344

45.1 Description
With the Multi Carrier Modules Alcatel-Lucent introduces a new technique to
further reduce the power consumption.
Normally a power amplifier is designed for the highest output power requested.
The amplifier gets here a certain supply voltage where it is by design most
efficient. A standard amplifier design provides only one supply voltage.
But in most of the cases the amplifier is used in partly or even low load
conditions where the amplifier is visibly less efficient and consumes more
power than necessary.
Alcatel-Lucent provides therefore a new innovative technique to enhance the
amplifier efficiency also in low traffic situations.
The power supply for the amplifier is switchable and provides the best supply
voltage for the PA depending on the load conditions in the specific timeslot.
From one GSM timeslot to the next this voltage is adapted and keeps the
amplifier always in the best efficiency range and therefore reduces the power
consumption of the amplifier.

There are no specific HW support restrictions.

There is no specific activation procedure.
45.4 Parameters


45.6.1 LMT Updates
There are no specific LMT updates.

There are no specific OMC HMI updates.

The following document is impacted by the feature: 9100 BTS/9110 Micro
BTS Functional Description.
180 / 344 3BK 21609 AAAA TQZZA Ed.29

46 Network Synchronization of Radio TS

3BK 21609 AAAA TQZZA Ed.29 181 / 344

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

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.

The feature is commercially optional. For specific information about the feature
activation, refer to Network Reconfiguration Recommendations, to Network
Synchronization of Radio TS.
46.4 Parameters
This section contains the new parameter involved in feature deployment:
Name New
GPS-Synchronised New
FN_OFFSET_TIME_SYNCHRO New


46.6.1 LMT Updates

Functional and Graphical Evolutions, sections BSSUSM: Modify BTS
Characteristics Window and BSSUSM: Effective Synch Mode Panel.

182 / 344 3BK 21609 AAAA TQZZA Ed.29


3BK 21609 AAAA TQZZA Ed.29 183 / 344

184 / 344 3BK 21609 AAAA TQZZA Ed.29

47 IP Transport in the BSS

Note: This feature is available starting with MR3.
3BK 21609 AAAA TQZZA Ed.29 185 / 344

47.1 Description
IP transport is introduced to support the diversity of existing network
environments.
The BSC, TC, MFS are connected to an IP network through Ethernet links.
The BTS is connected to an IP network over Ethernet links, or 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”

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

For specific information about the feature activation, refer to Change IP
Extraction Mode for 9130 BSC Evolution.
47.4 Parameters
deployment.
186 / 344 3BK 21609 AAAA TQZZA Ed.29

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 (BSC)
REACHABILITY_TEST_ADDR_TELECOM (BSC)
ROUTING_TABLE (BSC)
3BK 21609 AAAA TQZZA Ed.29 187 / 344

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)
188 / 344 3BK 21609 AAAA TQZZA Ed.29

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)
3BK 21609 AAAA TQZZA Ed.29 189 / 344

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
190 / 344 3BK 21609 AAAA TQZZA Ed.29

Name New
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
3BK 21609 AAAA TQZZA Ed.29 191 / 344

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)
192 / 344 3BK 21609 AAAA TQZZA Ed.29

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
P0_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)
3BK 21609 AAAA TQZZA Ed.29 193 / 344

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
194 / 344 3BK 21609 AAAA TQZZA Ed.29

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)
3BK 21609 AAAA TQZZA Ed.29 195 / 344

Counter Counter Name

ID
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
196 / 344 3BK 21609 AAAA TQZZA Ed.29


ID
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 NB_BTS_DROPPED_IP_PACKETS_PRIORITY1
IP31e NB_BTS_DROPPED_IP_PACKETS_PRIORITY2
IP31f NB_BTS_DROPPED_IP_PACKETS_PRIORITY3
IP32a NB_BSC_SENT_ALL_FLOWS_BYTES
IP32b NB_BSC_RCVD_ALL_FLOWS_BYTES
IP32c NB_BSC_DROPPED_IP_PACKETS_PRIORITY0
IP32d NB_BSC_DROPPED_IP_PACKETS_PRIORITY1
IP32e NB_BSC_DROPPED_IP_PACKETS_PRIORITY2
IP32f NB_BSC_DROPPED_IP_PACKETS_PRIORITY3
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
3BK 21609 AAAA TQZZA Ed.29 197 / 344


ID
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

47.6.1 LMT Updates
Tbc.
198 / 344 3BK 21609 AAAA TQZZA Ed.29


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.

BSS Overview


BSS Methods handbook
BTS NEM User Guide
9130 BSC Evolution NEM User Guide

9100 MBS Outdoor Installation Manual
CI 08 – Site Equipment Inventory
BSS Telecom Routing Configurations

BSS configuration rules
MFS Alarm Dictionary
9130 BSC Evolution Functional Description

9125 Compact TC Description
3BK 21609 AAAA TQZZA Ed.29 199 / 344


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 in same BSC

Move Several Abis Links from a BSC to Another, Same OMC-R
Move BSS from One 9125 Compact TC to Another

Merge 900 and 1800 Cells into Multiband Cells on 9100 BTS

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 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
200 / 344 3BK 21609 AAAA TQZZA Ed.29

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.
3BK 21609 AAAA TQZZA Ed.29 201 / 344

202 / 344 3BK 21609 AAAA TQZZA Ed.29

48 Remote BTS NEM
48 Remote BTS NEM

3BK 21609 AAAA TQZZA Ed.29 203 / 344

48 Remote BTS NEM
48.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 BTS 1, BTS 2, BTS X View
Local PC−NEM Remote PC_NEM
via IP or RS232
BTS X
BTS 1 BTS 2
Ethernet or PPP/E1
IP
NEM−IP−Forwarding−inside−BTS = TRUE
BTS 1, BTS 2, BTS X View

NEM−IP−Forwarding−inside−BTS = FALSE
Remote PC−NEM
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
204 / 344 3BK 21609 AAAA TQZZA Ed.29

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

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.
48.3 Parameters
A new parameter, ’NEM-IP-Forwarding-inside-BTS (True/False)’, exists to
enable/disable routing to the NEM in each BTS.


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

48.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.
3BK 21609 AAAA TQZZA Ed.29 205 / 344

48 Remote BTS NEM


BTS NEM User Guide

9100 BTS Acceptance Manual

CI 08 - Site Equipment Inventory.
206 / 344 3BK 21609 AAAA TQZZA Ed.29

49 Layer 2 Network Access

3BK 21609 AAAA TQZZA Ed.29 207 / 344

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

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

For specific information about the feature activation, refer to the BSS Telecom
Routing Configuration document.
49.4 Parameters


49.6.1 LMT Updates

208 / 344 3BK 21609 AAAA TQZZA Ed.29


BSS Telecom Routing Configuration
BSS Overview.
3BK 21609 AAAA TQZZA Ed.29 209 / 344

210 / 344 3BK 21609 AAAA TQZZA Ed.29

50 Security Enhancements for IP Introduction

This feature is available starting with MR3.
Enhanced security with IPSEC is available from Release B11MR3 Ed2.0
3BK 21609 AAAA TQZZA Ed.29 211 / 344

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


Reconfiguration Recommendations.
50.4 Parameters
deployment.
Name New
BSS_PAGING_COORDINATION (BSC) New
BSS_PAGING_COORDINATION (MFS) New
EN_BTS_PASSWORD_ RENEWAL (OMC local, BSC New

level, default is FALSE)
EXCLUDE_BTS_FROM_ PASSWORD_RENEWAL New

(OMC local, BTS level, default is FALSE)
212 / 344 3BK 21609 AAAA TQZZA Ed.29

Name New
SNMP_KEY_PERIOD_ TOWARD_BTS (OMC local, New

BSC level)
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


50.6.1 LMT Updates

3BK 21609 AAAA TQZZA Ed.29 213 / 344

214 / 344 3BK 21609 AAAA TQZZA Ed.29

51 Logging of BTS Temperature

Note: This feature is available starting with MR1 ED3 and MR3.
3BK 21609 AAAA TQZZA Ed.29 215 / 344

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


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.
51.4 Parameters

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.
MC1200 TRX_MAX_TEMPERATURE

51.6.1 LMT Updates


There are no applicable documents.
216 / 344 3BK 21609 AAAA TQZZA Ed.29

52 Ethernet Installation Kit
3BK 21609 AAAA TQZZA Ed.29 217 / 344

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

The Ethernet Adapter Board is introduced in the MBI3/MBI5 cabinets.
External Alarm Input Board Multistandard Multistandard Connection Area Power Supply and
XIBM MSCA Circuit Breaker Area
DCBR3
Equipment Labels External Interface DC Output External Clock Equipment DC Filter DC Output
Connectors Interface Group Abis Interface Group Labels Connectors −48 V/500 W max
GND −48V 0V
XCLK1 Out
DC OUT
XCLK1 In
+12 V Abis 3 Abis 1 500 W max
Abis 4 Abis 2
Abis 4 I Abis 3 I Abis 2 I Abis1
XCLK2 In/Out
I I I I
XBCB
0 0 0 0
INT & SR1 SR2 SR3
DC OUT
XRT RS232
Krone Strip Abis Relays Ethernet Adapter Circuit

Board Breakers
Figure 2: MBI3 Interconnection Panels with Ethernet Adapter Board
External Alarm Input Board Multistandard Multistandard Connection Area Power Supply and
XIBM MSCA Circuit Breaker Area
DCBR5
Equipment Labels External Interface Connectors External Clock Equipment DC Filter DC Output
DC Output Interface Group Abis Interface Group Labels Connectors −48 V/500 W max
GND −48V 0V DC OUT

XCLK1 Out
XCLK1 In
+12 V Abis 3 Abis 1 500 W max
Abis 4 Abis 2
Abis 4 I Abis 3 I Abis 2 I Abis1
XCLK2 In/Out
I I I I I I
XBCB
0 0 0 0 0 0
INT & SR1 SR2 SR3 SR4 SR5
DC OUT
XRT RS232
Krone Strip Abis Relays Ethernet Adapter Circuit Breakers

Board
Figure 3: MBI5 Interconnection Panels with Ethernet Adapter Board
218 / 344 3BK 21609 AAAA TQZZA Ed.29


The feature is commercially optional and there is no new parameter at the
OMC/BSC/BTS level.
52.4 Parameters

There are no new or modified counters and indicators.

52.6.1 LMT Updates



3BK 21609 AAAA TQZZA Ed.29 219 / 344

220 / 344 3BK 21609 AAAA TQZZA Ed.29

53 3G Search Prio Wrong in PMO

Note: This feature is available starting with MR1Ed.2 and MR3.
3BK 21609 AAAA TQZZA Ed.29 221 / 344

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


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


53.6.1 LMT Updates

222 / 344 3BK 21609 AAAA TQZZA Ed.29


BSS Overview.
3BK 21609 AAAA TQZZA Ed.29 223 / 344

224 / 344 3BK 21609 AAAA TQZZA Ed.29

54 Support of Sftp in the OMC
3BK 21609 AAAA TQZZA Ed.29 225 / 344

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


54.4 Parameters


54.6.1 LMT Updates


9153 OMC-R Methods Handbook.
226 / 344 3BK 21609 AAAA TQZZA Ed.29

55 IP Flow Separation at Physical Level

Note: This feature is available starting with B11 MR1 and MR3.
3BK 21609 AAAA TQZZA Ed.29 227 / 344

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

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

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,
transport in 9130 MFS Evolution.
9125 Transcoder To activate the feature for 9125 Transcoder (for B11 MR3 only):
228 / 344 3BK 21609 AAAA TQZZA Ed.29

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,
transport in 9125 TC.
55.4 Parameters
This section contains the modified parameters involved in feature deployment:
Name New
VLAN_CONF_INDEX New


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


Modify N7 Transport Mode for 9130 BSC Evolution
9130 BSC Evolution Acceptance Manual
Install 9130 MFS/BSC Evolution

9130 BSC Evolution Commissioning
3BK 21609 AAAA TQZZA Ed.29 229 / 344

Configure OS6850 for GB/BSS Traffic.

230 / 344 3BK 21609 AAAA TQZZA Ed.29

56 AMR WB Cell Load Handling

3BK 21609 AAAA TQZZA Ed.29 231 / 344

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


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’.
56.4 Parameters
deployment.
Name New
EN_HR_FOR_AMR_WB_GMSK New
ADD_HR_IN_TFO_LIST New
232 / 344 3BK 21609 AAAA TQZZA Ed.29



56.6.1 LMT Updates

Functional and Graphical Evolutions, to RNUSM: TFO Window and RNUSM:
AMR WB Window.


3BK 21609 AAAA TQZZA Ed.29 233 / 344

234 / 344 3BK 21609 AAAA TQZZA Ed.29

57 Interworking with LTE in the Packet Domain

Note: This feature is available starting with B11 MR1Ed2 / MR3.
3BK 21609 AAAA TQZZA Ed.29 235 / 344

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

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

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.
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.
236 / 344 3BK 21609 AAAA TQZZA Ed.29

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.
57.4 Parameters
deployment.
Name New
RAT_LTE New
MCC_LTE New
MNC_LTE New
CI_LTE New
EUARFCN New
PRIORITY_LTE New
THRESH_LTE_HIGH New
3BK 21609 AAAA TQZZA Ed.29 237 / 344

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 New
_RESELECTION
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_ Modified
RESELECTION
EN_2G_TO_3GTDD_ Modified
CELL_RESELECTION
238 / 344 3BK 21609 AAAA TQZZA Ed.29

Name New
CELL_RIM_NACC_CAPABILITY Modified

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

57.6.1 LMT Updates



BSS Overview
3BK 21609 AAAA TQZZA Ed.29 239 / 344

240 / 344 3BK 21609 AAAA TQZZA Ed.29

58 2G to LTE (TDD) Cell Re-selection

Note: This feature is available starting with B11 MR3Ed2.
3BK 21609 AAAA TQZZA Ed.29 241 / 344

58.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 2G to LTE (TDD) Cell Re-selection 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-TDD 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.

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

The feature is optional and can be activated at cell level through
EN_2G_TO_LTETDD_CELL_RESELECTION parameter.
1. Open RNUSM Main Window, create a PRC containing the cells on which the
LTE reselection to be activated.
4. Select LTE.
5. In order to activate the feature, set the
’EN_2G_TO_LTETDD_CELL_RESELECTION’ parameter to enabled.The
following rules apply when using this feature:
For a given BSS, we cannot have at the same time
TDD_ARFCN_LIST defined at BSS level and, at least, one 2G
cell where both ’EN_2G_TO_3GTDD_CELL_RESELECTION’ and
’EN_2G_TO_LTETDD_CELL_RESELECTION’ are enabled.
242 / 344 3BK 21609 AAAA TQZZA Ed.29

’EN_2G_TO_LTEFDD_CELL_RESELECTION’ and
’EN_2G_TO_LTETDD_CELL_RESELECTION’ cannot be enabled
at the same time.
If both ’EN_2G_TO_3G_CELL_RESELECTION’ and
’EN_2G_TO_LTETDD_CELL_RESELECTION’ are enabled, they must
If both ’EN_2G_TO_3GTDD_CELL_RESELECTION’ and
’EN_2G_TO_LTETDD_CELL_RESELECTION’ are enabled, they must
’EN_FAST_3G_CELL_RESELECTION’ can be set on 3 only if

’EN_2G_TO_3G_CELL_RESELECTION’ and
’EN_2G_TO_LTEFDD_CELL_RESELECTION’ are enabled or
’EN_2G_TO_3G_CELL_RESELECTION’ and
’EN_2G_TO_LTETDD_CELL_RESELECTION’ are enabled or
’EN_2G_TO_3GTDD_CELL_RESELECTION’ and
’EN_2G_TO_LTETDD_CELL_RESELECTION’ are enabled.
’EN_FAST_3G_CELL_RESELECTION’ cannot be set on

2 if ’EN_2G_TO_LTEFDD_CELL_RESELECTION’ = 0 and
’EN_2G_TO_LTETDD_CELL_RESELECTION’ = 0.
The allowed value ranges for ARFCN_LTE (TDD) are: [36000.. 39649].
For any given serving cell, no more than n distinct values of

ARFCN_LTE(TDD) are allowed in the neighbor LTE cells having
RAT_LTE =TDD and targeted by 2g-LTE reselection links,
where n is:
4, if ’EN_2G_TO_3GTDD_CELL_RESELECTION’ and
’EN_2G_TO_LTETDD_CELL_RESELECTION’ are enabled on the
aim serving cell and ’FAKE_FDD_MANAGEMENT’ = 1 on the aim
serving BSC
8, otherwise.
For any given serving cell, no more than 20 outgoing 2g-LTE adjacencies
are allowed.
3BK 21609 AAAA TQZZA Ed.29 243 / 344

58.4 Parameters
deployment.
Name New
EN_2G_TO_LTETDD_CELL _RESELECTION New
FAKE_FDD_MANAGEMENT New
EUARFCN (ARFCN_LTE(TDD)) New
RAT_LTE Modified
MNC_LTE Modified
PRIORITY_LTE Modified
THRESH_LTE_HIGH Modified
THRESH_LTE_LOW Modified
QRXLEVMIN_LTE Modified
MEASUREMENT_BANDWIDTH Modified
EN_2G_TO_LTEFDD_CELL_RESELECTION Modified
EN_2G_TO_3G_CELL_ RESELECTION Modified
EN_2G_TO_3GTDD_ CELL_RESELECTION Modified
Qsearch_C_LTE_INITIAL Modified
TDD_ARFCN_LIST Modified

This section contains the counters involved in feature deployment.
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
244 / 344 3BK 21609 AAAA TQZZA Ed.29


58.6.1 LMT Updates


BSS Overview

3BK 21609 AAAA TQZZA Ed.29 245 / 344

246 / 344 3BK 21609 AAAA TQZZA Ed.29

59 Remove Mx Firmware from Hardware Status for BSC

Note: This feature is available starting with MR1Ed.2 and MR3.
3BK 21609 AAAA TQZZA Ed.29 247 / 344

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

This feature is available only for 9130 BSC Evolution.

59.4 Parameters
248 / 344 3BK 21609 AAAA TQZZA Ed.29



59.6.1 LMT Updates


B11/B11 MFS/TC/BSS Software Replacement
9130 BSC Evolution Commissioning
9130 BSC Evolution Software Installation.
3BK 21609 AAAA TQZZA Ed.29 249 / 344

250 / 344 3BK 21609 AAAA TQZZA Ed.29

60 Remove Mx Firmware from Hardware Status for MFS

Note: This feature is available starting with MR1Ed3 and MR3.
3BK 21609 AAAA TQZZA Ed.29 251 / 344

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

This feature is available only for 9130 MFS Evolution.

60.4 Parameters
252 / 344 3BK 21609 AAAA TQZZA Ed.29



60.6.1 LMT Updates
For specific information about the LMT updates, refer to 9130 MFS Evolution
IMT User Guide, sections Firmware Upgrade and Check Firmware Status.


9130 MFS Evolution Maintenance Handbook

9130 MFS Evolution Software Installation.
3BK 21609 AAAA TQZZA Ed.29 253 / 344

254 / 344 3BK 21609 AAAA TQZZA Ed.29

61 Bidirectional Forwarding Detection (BFD) Protocol

Note: This feature is available starting with B11 MR3.
3BK 21609 AAAA TQZZA Ed.29 255 / 344

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


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.
61.4 Parameters
deployment.
Name New
BFD_IP_ADDRESS_BTS New

256 / 344 3BK 21609 AAAA TQZZA Ed.29


61.6.1 LMT Updates
Guide, section 4.9.5 BFD IP Address.

Functional and Graphical Evolutions, section 1.4 BSSUSM: View BTS Window.

BTS NEM User Guide

Install CISCO Routers
BSS Telecom Routing Configuration.
3BK 21609 AAAA TQZZA Ed.29 257 / 344

258 / 344 3BK 21609 AAAA TQZZA Ed.29

62 MC-RRH 900Mhz 2PA TDM

3BK 21609 AAAA TQZZA Ed.29 259 / 344

62.1 Description
The MC TRE can be hosted in:
Standard 9100 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
An MC-RH is a module, which has two power amplifiers, each able to

transmit simultaneously several carriers, and a dual receiver, able to
receive simultaneoulsy several carriers. A carrier is a GSM and or an 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.
Ring and chain configurations, exclusive or mixed are supported.
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 with 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.

MC-RRH is supported with SUMX.
MC-RRH is supported with 9130 BSC Evolution.

260 / 344 3BK 21609 AAAA TQZZA Ed.29

62.4 Parameters
deployment.
Name New
RRH-ID New
Number of MC-RRH for which the 1PA/2G-1PA/3G New

configuration is activated in the sector and in the
band 900 Mhz


62.6.1 LMT Updates
Guide.

Functional and Graphical Evolutions, sections BSSUSM: View BTS Window
and BSSUSM Main Window.

BTS NEM User Guide

Distributed BTS Technical Description
BSS Overview

BSS Preventive Maintenance Handbook
Reconfigure RRH/Sectors on Distributed BTS

Distributed BTS Dismantling Manual
3BK 21609 AAAA TQZZA Ed.29 261 / 344

Distributed BTS Installation Manual

Distributed/9100 BTS Commissioning Manual
Distributed BTS Additional Tests
Distributed BTS Acceptance Manual
262 / 344 3BK 21609 AAAA TQZZA Ed.29

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

3G carriers in same module
Note: This feature is available starting with B11 MR3ED2.0.
To be completed.
3BK 21609 AAAA TQZZA Ed.29 263 / 344

63.1 Description

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

63.4 Parameters
deployment.
Name New


63.6.1 LMT Updates
Guide.

Functional and Graphical Evolutions, sections BSSUSM: Modify BTS Remote
Settings and RNUSM: Network Information Window.

BTS NEM User Guide

264 / 344 3BK 21609 AAAA TQZZA Ed.29






9100 BTS Acceptance Manual.
3BK 21609 AAAA TQZZA Ed.29 265 / 344

266 / 344 3BK 21609 AAAA TQZZA Ed.29

64 9130 BSC Evolution Availability Improvement. Weekly Standby Reset.
64 9130 BSC Evolution Availability Improvement. Weekly

Standby Reset.
Note: This feature is available starting with B11 MR1Ed. 2.
3BK 21609 AAAA TQZZA Ed.29 267 / 344

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

The feature is available only for 9130 BSC Evolution.

The feature is not optional. For specific information about the feature
functionality, refer to the Network Reconfiguration Recommendations.
64.4 Parameters

268 / 344 3BK 21609 AAAA TQZZA Ed.29


64.6.1 LMT Updates

There are no OMC HMI updates.

3BK 21609 AAAA TQZZA Ed.29 269 / 344

270 / 344 3BK 21609 AAAA TQZZA Ed.29

65 Gb flex
65 Gb flex
Note: This feature is available starting with B11 MR3 release.
3BK 21609 AAAA TQZZA Ed.29 271 / 344

65 Gb flex
65.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


refer to the Configure GPRS.
65.4 Parameters
deployment.
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
272 / 344 3BK 21609 AAAA TQZZA Ed.29

65 Gb flex
Name New
MAX_NB_SGSN New
CELL_GPU New
BSS_GPU New
SGSNR New
P180a NB_SGSN_SELECTION_NSF
P180b NB_SGSN_SELECTION_RIM

65.6.1 LMT Updates



Configure GPRS
BSS Overview

3BK 21609 AAAA TQZZA Ed.29 273 / 344

65 Gb flex
274 / 344 3BK 21609 AAAA TQZZA Ed.29

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

STM1-IP Subrack
3BK 21609 AAAA TQZZA Ed.29 275 / 344

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

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

For specific information, refer to 9125 Transcoder NEM User Guide.
276 / 344 3BK 21609 AAAA TQZZA Ed.29

66.4 Parameters
deployment.
Name New
APS_MODE New


66.6.1 LMT Updates
No updates.

No updates.

9125 Transcoder Alarm Dictionary
Activate/Deactivate STM1 Interface for 9130 BSC Evolution/9125 TC.
3BK 21609 AAAA TQZZA Ed.29 277 / 344

278 / 344 3BK 21609 AAAA TQZZA Ed.29

67 BTS Synchronization Through NTP

Note: This feature is available starting with B11 MR3 release.
3BK 21609 AAAA TQZZA Ed.29 279 / 344

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


refer to the Synchronize BTS with a NTP Server.
67.4 Parameters
deployment.
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
280 / 344 3BK 21609 AAAA TQZZA Ed.29

Name New
NTP-SYNCHRONISED New
PCM-SYNCHRONISED New


67.6.1 LMT Updates


BTS NEM User Guide

3BK 21609 AAAA TQZZA Ed.29 281 / 344

282 / 344 3BK 21609 AAAA TQZZA Ed.29

68 CS/PS Outage Detection

3BK 21609 AAAA TQZZA Ed.29 283 / 344

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


The feature is activated from the 9130 BSC Evolution Terminal.
For specific information, refer to Network Reconfiguration Recommendations.
68.4 Parameters
deployment.
Name New
EN_Tel_Outage_DET New

284 / 344 3BK 21609 AAAA TQZZA Ed.29


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

No updates.

BSC & TC Alarm Dictionary
3BK 21609 AAAA TQZZA Ed.29 285 / 344

286 / 344 3BK 21609 AAAA TQZZA Ed.29

69 OMCP-OMC Supervision Link Defense

3BK 21609 AAAA TQZZA Ed.29 287 / 344

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


The feature is activated from the 9130 BSC Evolution Terminal.
For specific information, refer to Network Reconfiguration Recommendations.
69.4 Parameters
deployment.
Name New
EN-OMCR-Conn-DET New


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

No updates.
288 / 344 3BK 21609 AAAA TQZZA Ed.29


3BK 21609 AAAA TQZZA Ed.29 289 / 344

290 / 344 3BK 21609 AAAA TQZZA Ed.29

70 TP Init Auto Test Improvements

3BK 21609 AAAA TQZZA Ed.29 291 / 344

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


70.4 Parameters


70.6.1 LMT Updates

No updates.

The BSC & TC Alarm Dictionarydocument is impacted by the feature.
292 / 344 3BK 21609 AAAA TQZZA Ed.29

71 Management of BSC patches (Step 1: BSC Term only)

Note: This feature is available starting with B11 MR1Ed.2.
3BK 21609 AAAA TQZZA Ed.29 293 / 344

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


71.4 Parameters


71.6.1 LMT Updates
294 / 344 3BK 21609 AAAA TQZZA Ed.29


No updates.

The documents impacted by this feature are:
B10/B11 MFS/TC/BSS Software Migration.
3BK 21609 AAAA TQZZA Ed.29 295 / 344

296 / 344 3BK 21609 AAAA TQZZA Ed.29

72 MC-Modules hardware capacity licensing

Note: This feature is available starting with B11 MR1Ed.2.1
3BK 21609 AAAA TQZZA Ed.29 297 / 344

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

The feature is only for MC-Modules.

72.4 Parameters


72.6.1 LMT Updates

Functional and Graphical Evolutions, section RNUSM: License server synchro
and RNUSM: Network Information Window.
298 / 344 3BK 21609 AAAA TQZZA Ed.29



Site Preparation Sheet
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.
3BK 21609 AAAA TQZZA Ed.29 299 / 344

300 / 344 3BK 21609 AAAA TQZZA Ed.29

73 Improved Multi-GPU Performance

3BK 21609 AAAA TQZZA Ed.29 301 / 344

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


73.4 Parameters


73.6.1 LMT Updates

No updates.

The BSS Overview document is impacted by the feature.
302 / 344 3BK 21609 AAAA TQZZA Ed.29

74 Iur-g Interface with Enhanced Control Plane

Note: This feature is available starting with B11 MR1Ed.2.2
3BK 21609 AAAA TQZZA Ed.29 303 / 344

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

This feature is only for 9130 BSC Evolution.

The feature is optional, has one BSC-level activation parameter and is
controlled per TRX quantity.
For B11 MR1, the feature is activated from the 9130 BSC Evolution Terminal.
For B11 MR3, the feature is activated from OMC-R.
For specific information about feature activation and usage, refer to BSS
Methods Handbook, IURG section.
304 / 344 3BK 21609 AAAA TQZZA Ed.29

74.4 Parameters
deployment.
Name 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
3BK 21609 AAAA TQZZA Ed.29 305 / 344

MC1301 NB_BSC_SENT_SS7_IP_BYTES_IURG
MC1302 NB_BSC_SENT_SS7_IP_PACKETS_IURG
MC1303 NB_BSC_RESENT_SS7_IP_PACKETS_IURG
MC1304 NB_BSC_SENT_SS7_IP_BYTES_MAX_MN_IURG
MC1305 NB_N7_CON_REQ_REC_IURG
MC1306 NB_N7_CON_CONF_SENT_IURG
MC1307 NB_ENH_RELOC_REQ_IURG
MC1308 NB_ENH_RELOC_RESP_IURG
MC1309 NB_ENH_RELOC_FAIL_IURG

74.6.1 LMT Updates
The 9130 BSC Terminal was updated with IURG corresponding menus. For
details see 9130 BSC Evolution Terminal User Guide.

For B11 MR1 Ed3, the OMC-R was updated to display RNCs and the
corresponding IURGSL(s).
For B11 MR3, the OMC-R was updated to enable IURG, create RNC, display
RNCs and the corresponding IURGSL(s).
For details see 9153 OMC-R Functional and Graphical Evolutions.

For B11 MR1Ed.2.2, the following documents are impacted by the feature:

9130 BSC Evolution Terminal User Guide.
For B11 MR1Ed.3, the following documents are impacted by the feature:
306 / 344 3BK 21609 AAAA TQZZA Ed.29

BSC and TC Alarm Dictionary.
For B11 MR3Ed.1, the following documents are impacted by the feature:

BSS Overview
3BK 21609 AAAA TQZZA Ed.29 307 / 344

308 / 344 3BK 21609 AAAA TQZZA Ed.29

75 Support of Lb Interface by the BSC

Note: The feature is available in IP starting with B11 MR3Ed1.
Starting with B11 MR3Ed2 the feature is also supported in TDM.
3BK 21609 AAAA TQZZA Ed.29 309 / 344

75.1 Description
The Lb interface is a 3GPP standard interface between BSC and SMLC for
location service. SMLC is abbreviation of “Service Mobile Location Centre”,
who is the network element to handle the location service.
The feature is only supported by 9130 BSC Evolution.
The Lb interface is managed through IP (but the use of a Signaling Gateway
allows managing the Lb interface over TDM).
A given BSC can be connected to one SMLC at the most.
Two location methods are supported on Lb interface:
Timing Advance positioning (also called Cell Id + TA method)
TA positioning + NMR.

This feature is only for 9130 BSC Evolution.

The feature is optional, is activated at BSS level and is controlled per TRX
quantity.
Reconfiguration Recommendations.
75.4 Parameters
deployment.
Name New
EN_LB New
EN_LB_NMR New
LB_IP_SUBNET_MASK_BSC New
LB_SCTP_ENDPOINT_IP_ADDRESS_1 New
LB_SCTP_ENDPOINT_IP_ADDRESS_2 New
LB_SCTP_ENDPOINT_LIST New
LB_SCTP_ENDPOINT_PORT New
LOCAL_LB_SCTP_ENDPOINT_IP_ADDRESS_1 New
LOCAL_LB_SCTP_ENDPOINT_PORT New
LB_MIN_NB_ACTIVE_IPSP New
310 / 344 3BK 21609 AAAA TQZZA Ed.29

Name New
START_LB_IP_ADDRESS_BSC New
SMLC_SPC New
SMLC_TRAFFIC_MODE New
SMLC_Name New
T_SCON New
LB_PRIORITY New
MAX_NB_LB_SCTP_ENDPOINT New
EN_RESET_LB New
T_WAIT_SMLC_RESET_ACK New
NB_WAIT_SMLC_RESET_ACK New
T_Location_Lb New
T_Loc_abort_Lb New
SGW_INTERWORKING_LB New
REACHABILITY_TEST_ADDR_LB New
VLAN_CONF_INDEX (BSC) Modified
EN_CONV_GPS Modified
EN_MS_BASED_AGPS Modified
EN_MS_ASSISTED_AGPS Modified
EN_SAGI Modified
EN_LCS(MFS) Modified
EN_LCS(BSC) Modified
ASIG_IP_SUBNET_MASK_BSC Modified
BSS_IP_SUBNET_MASK_BSC Modified
START_ASIG_IP_ADDRESS_BSC Modified
START_BSS_IP_ADDRESS_BSC Modified
START_IURG_IP_ADDRESS_BSC Modified
IURG_IP_SUBNET_MASK_BSC Modified
3BK 21609 AAAA TQZZA Ed.29 311 / 344

MC923a NB_LCS_REQ
MC923b NB_LCS_SUCC
MC923c NB_LCS_FAIL_LB
MC923d NB_LCS_ABORT
MC942 NB_LCS_RESET_TX
MC943 NB_LCS_RESET_RX
MC965 NB_LCS_INTERRUPTED_INTRA_BSC_HO
MC966 NB_LCS_INTERRUPTED_INTER_BSC_HO

75.6.1 LMT Updates

The OMC-R was updated to display SMLC and the corresponding LBSL. For
details see 9153 OMC-R Functional and Graphical Evolutions.


BSC and TC Alarm Dictionary.
312 / 344 3BK 21609 AAAA TQZZA Ed.29


Note: This feature is available in MR3Ed1.1.
3BK 21609 AAAA TQZZA Ed.29 313 / 344

76.1 Description
The feature is similar with MC-TRX 900Mhz TDM, only the frequency range is
changed, with only internal telecom updates.

No impact versus MC-TRX 900Mhz TDM.

76.4 Parameters


76.6.1 LMT Updates


314 / 344 3BK 21609 AAAA TQZZA Ed.29

77 Customization of IconBox
Note: This feature is available starting with B11 MR3Ed.2
3BK 21609 AAAA TQZZA Ed.29 315 / 344

77.1 Description
The purpose of the feature is to offer a flexible way to integrate in 9153
OMC-R several applications allowing the access to specific 3PPs ncessary to
the customer.
The feature allow the 9153 OMC-R operator to customize the 9153 OMC-R
IconBox in order to add icons, link icons with applications and start applications
by clicking on user specific icons.
The user defined icons can be created, modified and removed from the 9153
OMC-R IconBox.
The user defind icons appear inside a separate frame below the
Alcatel-Lucent’s icons frame in the 9153 OMC-R IconBox.

No impact.

The feature is not optional. For specific information regarding the feature usage
refer to 9153 OMC-R Getting Started document.
77.4 Parameters

No impact.

77.6.1 LMT Updates
No impact.

The OMC-R was updated to display the 9153 OMC-R IconBox with a separate
frame for user defined icons and an additional menu in the 9153 OMC-R
IconBox menu bar.

316 / 344 3BK 21609 AAAA TQZZA Ed.29

78 15 BSSUSM Windows per BSSUSM Controller

Note: This feature is available starting with B11 MR3Ed.2
3BK 21609 AAAA TQZZA Ed.29 317 / 344

78.1 Description
For BSSUSM the number of main views was improved from 5 to 15 per
BSSUSM controller. The main views are considered as counting units to
express the oflcf.in limits, not controllers even though the limit per controller is
set to 15.
Each time a BSSUSM main view must be opened, the BSSUSM calls a specific
counting script and depending on the script result and on the limit per controller
the request will be accepted or denied.
BSSUSM will keep a file containing in its name, at each moment, the current
number of opened BSSUSM main views. The file is created when the first main
BSSUSM view is opened and deleted when the last main view is closed.

No impact.

78.4 Parameters
The NUMBER_BSSUSMCTRL_VIEWS_* variable is replaced by
NUMBER_BSSUSM_VIEWS_* in oflcf.in file.
Name New
NUMBER_BSSUSM_VIEWS_* New

No impact.

78.6.1 LMT Updates
No impact.

No impact.

Refer to 9153 OMC-R Network Administration Handbook document.
318 / 344 3BK 21609 AAAA TQZZA Ed.29

79 MC-TRX 900 - 2G - IP
79 MC-TRX 900 - 2G - IP
3BK 21609 AAAA TQZZA Ed.29 319 / 344

79 MC-TRX 900 - 2G - IP
79.1 Description
The feature is similar with MC-TRX 900Mhz TDM.


79.4 Parameters
deployment.
Name New
MAX_PDCH_PTU_IP_MC New
MAX_RLC_blks_PTU_MC_IP New
MAX_TBF_PTU_MC_IP New
MAX_TRX_PTU_IP_MC New
MAX_TRX_PTU_IP_MC New


79.6.1 LMT Updates


320 / 344 3BK 21609 AAAA TQZZA Ed.29

80 MC-TRX 900 - 3G - IP
80 MC-TRX 900 - 3G - IP
3BK 21609 AAAA TQZZA Ed.29 321 / 344

80 MC-TRX 900 - 3G - IP
80.1 Description
The feature is similar with MC-TRX 900Mhz TDM.


80.4 Parameters


80.6.1 LMT Updates


322 / 344 3BK 21609 AAAA TQZZA Ed.29

81 MC-TRX 1800 - 2G
81 MC-TRX 1800 - 2G
3BK 21609 AAAA TQZZA Ed.29 323 / 344

81 MC-TRX 1800 - 2G
81.1 Description
The feature is similar with MC-TRX 900Mhz TDM, only the frequency range is
changed, with only internal telecom updates.


81.4 Parameters


81.6.1 LMT Updates


324 / 344 3BK 21609 AAAA TQZZA Ed.29

82 MC-RRH 1800 - 2G
82 MC-RRH 1800 - 2G
3BK 21609 AAAA TQZZA Ed.29 325 / 344

82 MC-RRH 1800 - 2G
82.1 Description
The feature is similar with MC-RRH 900Mhz 2PA TDM, only the frequency
range is changed, with only internal telecom updates.

No impact versus MC-RRH 900Mhz 2PA TDM.

82.4 Parameters
deployment.
Name New
Number of MC-RRH for which the 1PA/2G-1PA/3G configuration New

is activated in the sector and in the band 1800 Mhz


82.6.1 LMT Updates


326 / 344 3BK 21609 AAAA TQZZA Ed.29

83 MC-RRH 900 - 2G - 1 PA - TDM
83 MC-RRH 900 - 2G - 1 PA - TDM

3BK 21609 AAAA TQZZA Ed.29 327 / 344

83 MC-RRH 900 - 2G - 1 PA - TDM
83.1 Description
The feature is similar with MC-RRH 900Mhz 2PA TDM. There is only one
Power Amplificator.


83.4 Parameters


83.6.1 LMT Updates


328 / 344 3BK 21609 AAAA TQZZA Ed.29

84 MC-RRH 900 - 2G -1 PA - IP
84 MC-RRH 900 - 2G -1 PA - IP
3BK 21609 AAAA TQZZA Ed.29 329 / 344

84 MC-RRH 900 - 2G -1 PA - IP
84.1 Description
The feature is similar with MC-RRH 900Mhz 2PA TDM.


84.4 Parameters


84.6.1 LMT Updates


330 / 344 3BK 21609 AAAA TQZZA Ed.29

85 MC-RRH 900 - 2G/3G - Different PA

3BK 21609 AAAA TQZZA Ed.29 331 / 344

85.1 Description
The feature is similar with MC-RRH 900Mhz 2PA TDM.


85.4 Parameters
deployment.
Name New
other-Standard-ratio-PA1 New
other-Standard-ratio-PA2 New
Pooling-over-2-PA (for 2G only MC-RRH with 2 PA) New


85.6.1 LMT Updates


332 / 344 3BK 21609 AAAA TQZZA Ed.29

86 Stop Supporting Sun V880 as OMC-R Hardware in B11 MR3
86 Stop Supporting Sun V880 as OMC-R Hardware in

B11 MR3
Note: SF V880 is no longer supported as OMC-R hardware starting with
B11 MR3Ed.2
3BK 21609 AAAA TQZZA Ed.29 333 / 344

86 Stop Supporting Sun V880 as OMC-R Hardware in B11 MR3
86.1 Description
The SF V880 machine is no longer supported as OMC-R hardware starting
with B11 MR3Ed.2. The impacted documents were updated accordingly.

No impact.

86.4 Parameters
No impact.

No impact.

86.6.1 LMT Updates
No impact.

No impact.

The following documents were updated:
9153 OMC-R Software Migration

9153 OMC-R Software Replacement
Legato Installation and User Guide

9153 OMC-R Reconfigure Platform
9153 OMC-R Acceptance Tests.
334 / 344 3BK 21609 AAAA TQZZA Ed.29

87 Management of BSC patches (Step 2: full)

3BK 21609 AAAA TQZZA Ed.29 335 / 344

87.1 Description
The aim af this feature is to help operators to patch MX BSC’s and to gather
information about patch status across all MX BSC supervised by an OMC.
The feature offers the following use cases:
Download patches
Install patches
Uninstall patch
Patch audit
ACIE export of BSC patch information
HTML export of the patch status information.
The patching process of BSC’s consist in:

the operator copies the patches and add-on matrix from delivered media to
OMC patch repository (/alcatel/var/share/patch/BSC)
Note: The Add On Matrix is extra information about patches that is delivered
together with the every patch. The Add On Matrix together with BSC
patch report helps operators in taking decisions. The Add On Matrix
file is defined per main release.
An example of Add On Matrix name is
BSC.PATCH_MX.11_3_02.001A.csv
where:
BSC is the type of equipment
PATCH_MX is the patch indicator
11_3_02 is B11MR3 edition 02
001A is patch ID
the operator, using OMC dedicated tools, can download a number of

patches to a number of BSCs repository
the operator decides to install a number of patches from BSC repository,

again using OMC dedicated tools.
the operator elects to uninstall some patches from some BSCs.


87.4 Parameters
336 / 344 3BK 21609 AAAA TQZZA Ed.29



87.6.1 LMT Updates

Functional and Graphical Evolutions, section BSSUSM: Patch Management
Window.


B10/B11 MFS/TC/BSS Software Migration.
3BK 21609 AAAA TQZZA Ed.29 337 / 344

338 / 344 3BK 21609 AAAA TQZZA Ed.29

88 Additional QoS basic alerters delivered by default (circuit part)
88 Additional QoS basic alerters delivered by default

(circuit part)
3BK 21609 AAAA TQZZA Ed.29 339 / 344

88 Additional QoS basic alerters delivered by default (circuit part)
88.1 Description
Based on counters/indicators, alerters are dedicated to speed up the reactivity
of the operational team to detect and to solve any Quality of Service (QoS)
degradation so as to restore telecom resources as fast as possible and to
improve network availability seen by the end user.
Five additional QoS basic alerters are delivered by default.

No impact.

88.4 Parameters
No impact.

No impact.

88.6.1 LMT Updates
No impact.

No impact.

The document impacted by this feature is:
Quality of Service Alerters User Guide.
340 / 344 3BK 21609 AAAA TQZZA Ed.29

89 Support of MC-TRX 900 Multistandard: Separate 2G and 3G Modules in Same Cabinet IP
89 Support of MC-TRX 900 Multistandard: Separate 2G

and 3G Modules in Same Cabinet IP
3BK 21609 AAAA TQZZA Ed.29 341 / 344

89 Support of MC-TRX 900 Multistandard: Separate 2G and 3G Modules in Same Cabinet IP
89.1 Description
The feature is similar with Support of MC-TRX 900 Multistandard: Separate 2G
and 3G carriers in same cabinet TDM.

No impact versus Support of MC-TRX 900 Multistandard: Separate 2G and
3G carriers in same cabinet TDM.

89.4 Parameters
deployment.
Name New


89.6.1 LMT Updates


342 / 344 3BK 21609 AAAA TQZZA Ed.29

90 Provide E1 Clock Out from BTS for NodeB Synchronization
90 Provide E1 Clock Out from BTS for NodeB

Synchronization
3BK 21609 AAAA TQZZA Ed.29 343 / 344

90 Provide E1 Clock Out from BTS for NodeB Synchronization
90.1 Description
The NodeB does not have an accurate autonomous clock system, especially in
IP mode, where the it uses PDP (Packet Data Protocol) and IEEE 1588v2 to
obtain the required frequency accuracy. That is why, in the case of collocated
BTSs and IP NodeBs, the BTS will provide a G704 E1 signal synchronized
from the local oscillator on the secondary Abis port that will be connected
to the NodeB.
BSC BTS Synchro Line NodeB
Abis HW TP E1 G704
Port 1 Port 2
Figure 4: The NodeB synchronization principle
The NodeB will be in charge of supervising the new synchronization line.

This feature is available for all types of 9100 BTSs, both IP and TDM modes,
that have the second Abis unused.

90.4 Parameters
No impact.

No impact.

90.6.1 LMT Updates
No impact.

No impact.

IO 148 - Provide E1 Clock Out of BTS for NodeB Synchronization.
344 / 344 3BK 21609 AAAA TQZZA Ed.29

New Features in Release B11 216090000e29

Uploaded by

Copyright:

Available Formats

You might also like

New Features in Release B11 216090000e29

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

New Features in Release B11 216090000e29

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent GSM

3BK 21609 AAAA TQZZA Ed.29

Short title Concept Guide

2 / 344 3BK 21609 AAAA TQZZA Ed.29

3BK 21609 AAAA TQZZA Ed.29 3 / 344

6.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4 / 344 3BK 21609 AAAA TQZZA Ed.29

3BK 21609 AAAA TQZZA Ed.29 5 / 344

17.6 LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6 / 344 3BK 21609 AAAA TQZZA Ed.29

23 Support of Windows Vista for PC LMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

3BK 21609 AAAA TQZZA Ed.29 7 / 344

28.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

8 / 344 3BK 21609 AAAA TQZZA Ed.29

33.7 Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

3BK 21609 AAAA TQZZA Ed.29 9 / 344

39.3 Feature Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

10 / 344 3BK 21609 AAAA TQZZA Ed.29

44.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

3BK 21609 AAAA TQZZA Ed.29 11 / 344

50.2 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

12 / 344 3BK 21609 AAAA TQZZA Ed.29

55.6.2 OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

3BK 21609 AAAA TQZZA Ed.29 13 / 344

61.2 Hardware Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

14 / 344 3BK 21609 AAAA TQZZA Ed.29

66.6.1 LMT Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

3BK 21609 AAAA TQZZA Ed.29 15 / 344

72.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

16 / 344 3BK 21609 AAAA TQZZA Ed.29

77.6 LMT/OMC HMI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

3BK 21609 AAAA TQZZA Ed.29 17 / 344

83 MC-RRH 900 - 2G - 1 PA - TDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

18 / 344 3BK 21609 AAAA TQZZA Ed.29

88.4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

3BK 21609 AAAA TQZZA Ed.29 19 / 344

20 / 344 3BK 21609 AAAA TQZZA Ed.29

Document Pertinence This document applies to Release B11 of the BSS.

TC STM1 interface board is also referred as TCIF

TC STM1 IP interface board is also referred as TCIFI.

What’s New In Edition 28

3BK 21609 AAAA TQZZA Ed.29 21 / 344

Hardware Coverage (Section 21.2)

22 / 344 3BK 21609 AAAA TQZZA Ed.29

AMR WB Cell Load Handling (Section 56)

B11 Features (Section 1.2)

Hardware Coverage (Section 53.2)

IP Flow Separation at Physical Level (Section 55)

3BK 21609 AAAA TQZZA Ed.29 23 / 344

Improvement done in 3G Search Prio Wrong in PMO (Section 53).

Gb flex (Section 65)

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

BTS Synchronization Through NTP (Section 67).

Remove Mx Firmware from Hardware Status for BSC (Section 59),

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

Customization of BTS External Alarms (Section 14)

OMC HMI Updates (Section 19.6.2).

Customization of BTS External Alarms (Section 14)

24 / 344 3BK 21609 AAAA TQZZA Ed.29