Alcatel-Lucent GSM: 9100 BTS/9110 Micro BTS/9110-E Micro BTS Functional Description

Alcatel-Lucent GSM
9100 BTS/9110 Micro BTS/9110-E

Micro BTS Functional Description
BTS Document
Sub-System Description
Release B10
3BK 21244 AAAA TQZZA Ed.08
BLANK PAGE BREAK
Status
RELEASED
Short title
9100 BTS/9110 Micro BTS/9110-E Micro BTS FD

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 / 234
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1
Logical Position of BTS in BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1
Functional Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2
Channel Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2
BTS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1
Transmission Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2
Telecommunication Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.3
O&M Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.4
Support Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3
BTS External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4
Signal and Data Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1
Downlink Signal Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.2
Uplink Signal Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.3
O&M Data Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5
Functional Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.1
9100 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.2
BTS 9110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.3
9110 Micro BTS-E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Channel Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1
Introduction to Channel Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2
Radio Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1
Radio Transmission Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2
Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.3
Modulation Technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3
Channel Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1
Signalling Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2
Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.3
Packet-Switched Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4
Channel Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5
Radio Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.1
Layer 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.2
Layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.3
Layer 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6
SMS-CB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.1
Simplified SMS-CB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.2
Complete SMS-CB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transmission Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1
Introduction to Transmission Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2
Multiplexing Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1
Abis Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2
Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.3
Signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.4
Transmission O&M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.5
Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.6
Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.7
Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3
Abis Interface Physical Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1
Second Abis Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2
No Cross Connect for Second Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4
GPRS Transmission Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Telecommunication Functions - Baseband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
12
13
14
14
14
15
15
15
16
20
20
21
22
23
23
23
24
25
26
26
26
27
27
28
28
30
31
32
33
33
35
35
36
36
37
39
40
40
40
42
42
43
43
43
43
45
46
48
49
51
3 / 234
Contents
4.1
4.2
Introduction to Telecommunication Functions - Baseband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Baseband Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1
Speech Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2
Rate Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3
Channel Encoding and Decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4
Interleaving/De-interleaving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.5
Encryption/Decryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.6
Demodulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3
Call Management Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1
Radio Link Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2
Radio Resource Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3
Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4
Discontinuous Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.5
Discontinuous Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.6
Quality Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.7
Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4
Supervisory and Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1
Clock Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2
Protocol Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3
Radio Channel Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4
Transcoder Time Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Telecommunication Functions - RF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1
Introduction to Telecommunication Functions - RF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2
RF Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1
RF Carrier Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.2
Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.3
Modulation and Up-Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.4
Power Amplification and Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.5
Channel Selection and Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.6
Signal Amplification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.7
A-D Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.8
Digital Pre-processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3
Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4
Coupling Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
O&M and Support Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1
Introduction to O&M and Support Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2
O&M Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1
O&M Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2
O&M Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3
Station Unit Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4
Recovery Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3
Support Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1
HEAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.2
Internal Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.3
Internal Temperature Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.4
External Battery Cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.5
MPS / MPS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.6
Timing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Functional Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1
Introduction to Functional Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2
Functional Units Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.1
9100 BTS Functional Units Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.2
BTS 9110/9110-E Functional Units Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3
Mapping of Functions to Functional Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.1
Functional Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.2
Telecommunication Baseband Functional Mapping . . . . . . . . . . . . . . . . . . . . . . . .
4 / 234
52
52
52
54
58
59
59
60
61
61
61
61
62
62
63
63
64
64
64
64
65
67
68
69
69
69
70
72
74
74
75
75
76
77
79
80
80
80
81
82
82
83
83
83
85
86
87
88
89
90
90
90
92
96
97
98
Contents
10
11
7.3.3
Telecommunication RF Functional Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
7.3.4
O&M Functional Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7.3.5
Support Functional Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.1
Naming Conventions Used for the Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
8.2
9100 BTS Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
8.2.1
Configurations Using TWIN TRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.2.2
9100 BTS Indoor Configurations - DC Powered . . . . . . . . . . . . . . . . . . . . . . . . . . 108
8.2.3
9100 BTS Indoor Configurations - AC Powered . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
8.2.4
9100 BTS Outdoor Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
8.3
BTS 9110 Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
8.4
9110 Micro BTS-E Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Antenna Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9.1
Introduction to Antenna Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
9.1.1
9100 BTS Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
9.1.2
BTS 9110/9110-E Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
9.2
Antenna Network Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
9.2.1
9100 BTS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
9.2.2
9110 Micro BTS/9110-E Micro BTS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
9.3
Antenna Network External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
9.4
Antenna Network Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.4.1
9100 BTS Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.4.2
9110 Micro BTS/9110-E Micro BTS Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
9.5
Antenna Network Software Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
9.5.1
Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
9.5.2
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
9.6
Range Extension Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
9.6.1
Masthead Amplification Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
9.6.2
Power Distribution Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
9.7
Tower Mounted Amplifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
9.7.1
Tower Mounted Amplifier with External Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 143
9.7.2
Tower Mounted Amplifier with AGC Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
9.8
GSM/UMTS Co-siting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Station Unit Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
10.1
Introduction to the Station Unit Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
10.2
Station Unit Module Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
10.3
Station Module External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
10.4
Station Unit Module Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
10.5
Station Unit Module Software Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
10.5.1
O&M Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
10.5.2
Transmission Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
10.5.3
Clock Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Transceiver Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
11.1
Introduction to Transceiver Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
11.2
Transceiver Equipment Functional Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
11.3
Transceiver Equipment External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
11.4
Transceiver Equipment Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
11.5
Transceiver Equipment Software Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
11.5.1
SCP Software Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
11.5.2
ENCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
11.5.3
DEM, RXP and DEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
11.5.4
MBED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
11.5.5
CUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
11.5.6
BCBT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
11.6
Transceiver Equipment Power Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
5 / 234
Contents
12
13
14
15
11.6.1
Transceiver Equipment Power Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6.2
Unbalanced Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS Start Up and Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2
SUM/MSUM Start Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3
Software Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3.1
BTS Master File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3.2
SUM Software Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3.3
Other BTS Software Packages Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3.4
Management of Software Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.4
Software Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.1
BTS Managed Objects and SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2
BTS Managed Objects and SBLs Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3
BTS Managed Objects (SBL) Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4
Allowed Managed Object/SBL States of the 9110 Micro BTS/9110-E Micro BTS . . . . . . . .
13.4.1
Allowed States of Managed Object Abis_PCM (SBL Abis-HWAY-TP) . . . . . . .
13.4.2
Allowed States of Managed Objects (SBL) BTS . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4.3
Allowed States of Managed Objects (SBL) CCF . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4.4
Allowed States of Managed Objects (SBL) CLLK . . . . . . . . . . . . . . . . . . . . . . . . .
13.4.5
Allowed States of Managed Objects (SBL) CU . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4.6
Allowed States of Managed Objects (SBL) EACB . . . . . . . . . . . . . . . . . . . . . . . . .
13.4.7
Allowed States of Managed Objects (SBL) FU . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4.8
Allowed States of Managed Objects (SBL) OMU . . . . . . . . . . . . . . . . . . . . . . . . .
13.4.9
Allowed States of Managed Objects (SBL) RA . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5
Allowed Managed Objects and SBL States of the 9100 BTS . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5.1
Allowed States of Managed Object Abis_PCM (SBL Abis-HWAY-TP) . . . . . . .
13.5.2
Allowed States of Managed Objects (SBL) BTS . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5.3
Allowed States of Managed Objects (SBL) CCF . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5.4
Allowed States of Managed Objects (SBL) CLLK . . . . . . . . . . . . . . . . . . . . . . . . .
13.5.5
Allowed States of Managed Objects (SBL) CU . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5.6
Allowed States of Managed Objects (SBL) EACB . . . . . . . . . . . . . . . . . . . . . . . . .
13.5.7
Allowed States of Managed Objects (SBL) FU . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5.8
Allowed States of Managed Objects (SBL) OMU . . . . . . . . . . . . . . . . . . . . . . . . .
13.5.9
Allowed States of Managed Objects (SBL) RA . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6
Allowed Managed Objects and SBL Actions for 9110 Micro BTS/9110-E Micro BTS . . . . .
13.7
Allowed Managed Objects and SBL Actions for 9100 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.8
BTS 9110/9110-E RITs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.9
BTS 9110/9110-E SBLs and RITs Reported to the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.10
9100 BTS RITs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.11
9100 BTS SBLs and RITs Reported to the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.12
BTS RBLs and Local Fault Indication via LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1
Telecommunication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1.1
Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1.2
Timing Advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1.3
Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1.4
Channel Interference Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1.5
LAPD Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1.6
In-Band Signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.2
Telecommunications Overload Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3
Mobile Station RF Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Interaction Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1
BCCH-TRE Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.2
Interaction Fault Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6 / 234
176
177
179
180
182
183
183
183
183
184
185
187
188
189
193
194
194
194
194
195
195
196
196
197
197
198
198
198
199
199
200
200
201
201
202
203
204
205
206
207
210
211
215
216
216
217
218
218
218
218
219
220
223
224
225
Contents
16
Start-Up Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.1
BTS/SUM/MSUM Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2
Restart SBL BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.3
Restart SBL OMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.4
SBL OMU Auto-Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.5
Reset SBL BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.6
Reset SBL OMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.7
SBL OMU Auto-Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
227
228
229
230
231
232
233
234
7 / 234
Contents
8 / 234
Preface
Preface
Purpose
This document provides a functional description of the GSM 9100 BTS and the
9110 Micro BTS/9110-E Micro BTS.
The purpose of this document is to explain the role of the 9100 BTS and 9110
Micro BTS/9110-E Micro BTS in a GSM network.
All features and functions described in this document may not be available
on your system.
Whats New
In Edition 08
Description improvement in Tower Mounted Amplifier with AGC Support
(Section 9.7.2).
In Edition 07
Update with the new equipment naming.
In Edition 06
Description improvement in:
9100 BTS Modules (Section 9.4.1)
Transceiver Equipment Modules (Section 11.4).
In Edition 05
Section Tower Mounted Amplifier with AGC Support (Section 9.7.2) was added.
In Edition 04
Section Tower Mounted Amplifier with AGC Support (Section 9.7.2) was added.
In Edition 03
Information about AGCL9P was removed.
9 / 234
Preface
In Edition 02
Information about AGX module was removed.
In Edition 01
First release of the document.
Audience
Assumed Knowledge
This document is intended for anyone interested in learning about the

Alcatel-Lucent BTSs.
The reader must possess a:
General knowledge of telecommunications systems and terminology
Good understanding of GSM concepts
Familiarity with BSS functions and architecture
Embedded/real-time software techniques.
10 / 234
1 Overview
1 Overview
This Overview provides a simplified overview of the 9100 BTS and 9110 Micro
BTS/9110-E Micro BTS together with their role in a GSM network.
After explaining the logical position of the BTS in the BSS, the chapter shows
the functional architecture of the BTS. It then outlines how the BTS processes
uplink and downlink data to interface the land-based telephone system with
Mobile Stations.
11 / 234
1 Overview
1.1 Logical Position of BTS in BSS

The BTS provides two-way radio communication between the PSTN, and
Mobile Stations located in a single GSM cell. It also provides a similar link
between the Mobile Stations and the rest of the PLMN. The BTS provides an
interface for the digital baseband signals used by the land-based networks and
the GSM radio signals used by Mobile Stations.
To achieve its overall function, the BTS provides:
Facilities to transmit and receive appropriate radio signals
Management of the protocols used on the BTS - BSC and BTS - Mobile
Station links. This provides a communications path open to GSM standards
Cell-specific O&M functions
Low-level local control, including radio resource management.
Environment The following figures show the logical position of a BTS in the
BSS, between the BSC and Mobile Stations currently located in the cell area.
Cell Area
Radio Frequency Signals

via Air Interface
Mobile Station
BTS
Traffic and
Signaling
via Abis
Interface
Downlink
Mobiles Station
BSS
BSC
Other BTS
TC
MSC
Uplink
Mobile Station
TC = Transcoder
Figure 1: Logical Position of BTS in BSS

For systems incorporating GPRS some additional components are required as
shown in the following figure. An MFS is placed in the system between the BSC
and the SGSN. The MFS contains a number of PCUs, one of which controls
all the GPRS activity for one cell.
12 / 234
1 Overview
PDN
SGSN
Cell Area
Gb
Interface
Radio Frequency Signals

via Air Interface
MFS
Mobile Station
BTS
BSS
BSC
Traffic and
Signaling
via Abis
Interface
Downlink
PCU
MSC
TC
Uplink
Mobile Station
Mobile Station
Figure 2: Logical Position of BTS in BSS with GPRS

The SGSN (see the figure above) keeps track of the location of individual
Mobile Stations. The SGSN also performs both security functions and
access control. GPRS services are not available until the Mobile Station has
established contact with the SGSN.
1.1.1 Functional Architecture

The following figure shows the functional architecture of the BTS.
Support Functions
To all Functions
Telecommunication Functions
RF Functions
Baseband Functions
Transmission
Functions
Abis Interface
Transmit/Receive
Antennas
Part of the Telecommunications

functions are duplicated for
Antenna Diversity.
O&M Functions
Data flows through the BTS in the downlink direction

Data flows through the BTS in the uplink direction
Figure 3: BTS Functional Architecture
13 / 234
1 Overview
1.1.2 Channel Organization

RF signals over the Air Interface carry traffic and signalling/control channels
which are organized according to GSM recommendations. The allocation and
control of these channels are managed by the BTS functions.
Radio Resource Management functions control and organize radio resources to
meet the current operational needs of both the network and individual users.
Systems using GPRS services have additional channel allocation as described
in Channel Organization (Section 2).
Channel Organization and Radio Resource Management are also described in
Channel Organization (Section 2).
1.2 BTS Functions

As the principal interface between the PSTN and Mobile Stations, the BTS
performs four primary functions.
These are:
Transmission functions, which manage the transfer of traffic and control
data between the BTS and BSC
Telecommunications functions, which manage the transfer of traffic and
control data between the BTS and the Mobile Stations
O&M functions, which supervise the operation of the BTS
Support functions, which provide a logical and physical environment in
which the BTS functions can be realized.
Communication between the transmission, telecommunications, and O&M
functions is managed according to the OSI model. The BTS functions are
concerned with Layer 1 (Physical), Layer 2 (Data Link), and Layer 3 (Network)
of this model.
1.2.1 Transmission Functions

To minimize operating costs, all data passed between the BTS and the BSC
is time-division multiplexed onto a single physical interface. This is the Abis
Interface, which carries all the data sent between the BSC and BTS.
Logical links between the BSC and BTS handle the following information:
Signalling data used for control purposes
O&M data for the BTS transmission modules
O&M data for the BTS entities
User data in the form of speech and data traffic.
The Abis Interface is described in greater detail in Transmission Functions
(Section 3).
14 / 234
1 Overview
1.2.2 Telecommunication Functions

There are two primary telecommunication functions:
Baseband functions
Baseband functions modulate and encode traffic and signalling data from
the BSC according to GSM recommendations. This data is then sent to
the Mobile Stations using the RF functions. Traffic and signalling received
from the Mobile Stations is demodulated and decoded to recover the
baseband data. Baseband processing is discussed in Telecommunication
Functions - Baseband (Section 4).
RF functions
RF functions enable traffic and signalling to be sent and received over the
Air Interface as a radio signal. A special link layer protocol ensures the
reliable transfer of signalling data over the Air Interface. The RF functions
are described in Telecommunication Functions - RF (Section 5).
For Antenna Diversity, the telecommunications functions uplink path is
duplicated. The duplicated functions extend from the antennas, through the RF
functions, and up to the output of the Decoder in the baseband functions.
1.2.3 O&M Functions

O&M functions monitor and control the correct operation of the BTS and its
external interfaces. These functions are shared between the BTS and the BSC.
The BSC provides overall control.
The O&M functions use Layer 2 links for BTS internal communications. A
terminal connected via an MMI is used for local operator control of the BTS.
There are four categories of O&M functions:
Configuration Management
Fault Management
Dedicated Alarm and Control Handling
External Alarm Handling.
The O&M functions also control the operation of the RF Self-tests and manage
the actions required by the BTS Recovery Strategy.
The BTS O&M functions are described in O&M and Support Functions
(Section 6).
1.2.4 Support Functions

The support functions provide a number of services relevant to the internal
working of the BTS.
They are:
Clock generation and distribution
External alarm collection
Internal self-tests.
The support functions are also described in O&M and Support Functions
(Section 6).
15 / 234
1 Overview
1.3 BTS External Interfaces

The BTS uses a number of external interfaces. These interfaces are described
in the following table.
Interface
Description
9100
9110
Micro
BTS/
9110-E
Micro
BTS
Air
The Air Interface is the radio link between the BSS and the Mobile
Station. The BTS uses an external RF interface to realize the
Air Interface.
Four frequency ranges are allocated to the GSM 850, GSM 900,
GSM 1800 and GSM 1900 variants. Each range is divided into
two bands. One band is for use by the uplink, the other by the
downlink.
The Air Interface functions are described in Channel Organization
(Section 2).
Abis
Uplink and downlink and control data between the BSC and BTS
is carried by the Abis Interface. This interface is specified as a
G.703/704 2048 kbit/s PCM link (GSM rec. 04.06).
The Abis Interface and transmission functions are described in
Chapter 3.
External Alarm
Connection
The external alarm connection function is implemented as the

External Input Output Interface. The XIO enables the 9100 BTS
external alarm sources to be interfaced to the O&M functions.
The connection is made via the dedicated alarm functions.
The external alarm connection function is used only in
configurations where external alarm sources are present - e.g.,
cabinet door switch, smoke detector.
External alarm handling is described in O&M and Support
Functions (Section 6).
XBAT
The External Battery Connection is used to provide control over

an external battery backup unit.
XCLK
The External Clock Interface enables the BTS to synchronize with

other BTSs in either master or slave mode.
Timing functions are described in O&M and Support Functions

(Section 6).
XBCB
16 / 234
The External BTS Control Bus is used to supervise or control

external events. It can be used to perform external Remote
Inventory on the BTS, but only if the BTS is not powered up and
only at factory level.
1 Overview
Interface
Description
9100
9110
Micro
BTS/
9110-E
Micro
BTS
XGPS
The External Global Positioning System Control Bus provides

control and supervisory functions for an external GPS receiver.
The receiver is used to provide an external clock synchronization
signal for the BTS. Using a GPS module removes the need for the
yearly calibration of the BTS internal clock.
XST_RA
The External Stealth Radio Connection provides the control link

between the MSUM and Stealth Radio equipment.
IEB
The Inter Entity Bus is used to connect a single master 9110

Micro BTS/9110-E Micro BTS to a maximum of five BTSs in slave
mode (refer to Figure 4 ). The identity of the BTS 9110/9110-E
entity is determined by the connections of the IEB cable.
The master BTS 9110/9110-E can have cables connected to

ports S1 and S2. Each of these cables is terminated at the M port
of a slave BTS 9110/9110-E. The units are identified as master,
slave 1 and slave 2 via the Addressing bus. Internal addressing
of the MTRE allows each MTRE to be addressed independently
by the master unit.
17 / 234
1 Overview
Interface
Description
9100
9110
Micro
BTS/
9110-E
Micro
BTS
MMI
A local MMI enables a terminal to be connected for local operator

control of the BTS.
Refer to the BTS Terminal User Guide for more information about
local operator control of the 9100 BTS.
Power Supply
Connection
The mains supply voltage for a 9100 BTS is determined by the

internal power supply modules fitted
The requirement can be:
AC (230 VAC)
DC (-48/-60 VDC nominal).
The 9100 BTS modules are provided with their own DC/DC
converters. Power on/off of these modules is controlled by the
O&M functions via the internal BCB Interface.
For the 9110 Micro BTS, power is supplied to the master 9110
Micro BTS. All other 9110 Micro BTS/9110-E Micro BTS entities
are supplied from cabling from the first entity. For each 9110 Micro
BTS there is only one centralized power supply, the MPS. For the
9110 Micro BTS-E the power supply is the MPS2. These modules
supply the power and different voltages for all the modules.
The input voltage requirements are as follows:
AC 170 VAC through 270 VAC (230 VAC through 240 VAC
Nominal) at 47 Hz through 63 Hz
DC 270 VDC through 358 VDC.
The BTS main power connection is filtered and provided with
one or more protection breakers. Lightning protection is provided
for AC power lines.
In case of 9110 Micro BTS/9110-E Micro BTS together with an
SSC each BTS will be supplied by the SSC (also the slaves).
For more information about power supply connections, refer to the
appropriate hardware documents.
Table 1: BTS External Interfaces
18 / 234
1 Overview
The following figures shows how the IEB is used to connect a single master
9110 Micro BTS/9110-E Micro BTS to up to two 9110 Micro BTS in slave mode,
and up to five 9110 Micro BTS-E in cascading slave mode.
Master
BTS A9110
Slave 2
BTS A9110
Slave 1
BTS A9110
S1
S2
S1 S2
S1
S2
Figure 4: IEB Connections for Pure 9110 Micro BTS

Slave 1
BTS
A9110E
M
S1
S2
Slave 11
Master
Slave 2
BTS
A9110E
BTS
A9110E
BTS
A9110E
BTS
A9110E
S1 S2
S1
S2
S1
S2
Slave 1
Slave 12
Slave 11
Master
BTS
A9110E
BTS
A9110E
BTS
A9110E
BTS
A9110E
S1
S2
Slave 1
BTS
A9110
M
Slave 12
S1
S2
S1 S2
Slave 12
BTS A9110E
S1 S2
S1
S2
Slave 11
BTS A9110E
S1
S2
S1
S2
BTS
A9110
M
S1 S2
Slave 2
BTS
A9110E
S1
S1 S2
Slave 2
Master
S2
BTS
A9110
M
S1 S2
Slave 21
BTS
A9110E
M
S1
S2
Slave 21
BTS A9110E
S1
S2
Slave 21
BTS A9110E
S1
S2
: The 9110 Micro BTS in the configuration does not allow connection of lower slaves. The master must be an 9110-E
Micro BTS.
Figure 5: IEB Connections for Pure 9110-E Micro BTS and Mixed 9110-E Micro BTS + 9110 Micro BTSs
19 / 234
1 Overview
1.4 Signal and Data Processing

Downlink data flows through the BTS from the Abis Interface to the transmit
antennae. Uplink data flows from the receive antennae to the Abis Interface.
1.4.1 Downlink Signal Processing

Downlink signal processing consists of several functions and processes, which
are described in the following sections.
1.4.1.1 Transmission Functions

The transmission functions demultiplex digital baseband data received via
the Abis Interface:
BTS entity O&M data is passed to the O&M functions.
Transmission O&M data is handled locally by the transmission functions.
Traffic and associated control data is demultiplexed to form a number of
discrete data streams. The number of data streams, up to eight full-rate or
16 half-rate, depends on the telecom configuration. The data streams are
passed to the baseband functions for processing.
1.4.1.2 Baseband Processing

The baseband functions encode each data stream as a series of data bursts.
Each burst occupies one TDMA time slot.
The baseband processing assembles the TDMA bursts into the GSM frame
hierarchy in accordance with GSM rec. 05.01. This recommendation specifies
a number of time slot groups, within which individual time slots are allocated
to downlink TDMA channels in a cyclical manner.
1.4.1.3 Channel Organization

Within a cell of a BTS a single data stream is dedicated to carry the mandatory
BCCH. All other time slots are available to carry baseband traffic data and
associated signalling channel data.
The associated signalling channel data is carried on the SDCCH. This channel
is used for call establishment and location update. It is also used with the SMS
and Cell Broadcast features. For more information about channel types,
refer to Channel Types (Section 2.3).
The data bursts are organized into the GSM frame hierarchy, then they are
sent to the RF functions. The RF functions generate one or more carrier
frequencies, which are modulated by the downlink data. This enables the
downlink data to be sent over the Air Interface as a radio signal.
20 / 234
1 Overview
1.4.1.4 Frequency Hopping

Successive TDMA bursts from each data stream can be transmitted on a fixed
carrier frequency. Alternatively, successive bursts can be transmitted on
different carrier frequencies, chosen from the set of frequencies generated by
the RF functions. The process of transmitting successive bursts on different
frequencies is called frequency hopping.
For both methods of burst transmission, the resulting combination of a time
slot and a specific radio frequency creates a GSM channel. This channel is
unique within the cell.
Only TCHs and SDCCHs are frequency hopped. The BCCH is always sent
on a constant carrier frequency. Frequency hopping is implemented under
control of the FHA.
1.4.1.5 Coupling Functions

The RF functions include coupling functions which ensure the efficient
transfer of RF power to the antennae. The coupling functions enable the BTS
transmitters and receivers to use two antennae to maximize RF performance.
1.4.2 Uplink Signal Processing

Uplink signal processing is essentially the reverse of the downlink processing
described in Downlink Signal Processing (Section 1.4.1).
1.4.2.1 Channel Decoding

Radio signals received from Mobile Stations are routed from the antennae
to the RF functions.
When antenna diversity is configured, the signals from the second antenna
provide the BTS with a choice of two signals. Both signals are combined in the
Decoder using the maximum radio combining algorithm.
The RF functions also include a duplexing function, which enables the BTS
receivers to share the transmit antennae.
The RF functions remove the RF carrier and produce samples which represent
the data contained in the incoming signals.
1.4.2.2 Frequency Hopping

Each uplink channel can be on a fixed carrier frequency, or it can be frequency
hopped by the sending Mobile Station. If frequency hopping is configured,
successive databursts associated with an uplink channel are received on
different carrier frequencies. This process is implemented under control of
the FHA.
1.4.2.3 Signal Processing

The RF functions send the representative samples to the baseband functions.
The baseband functions carry out GMSK demodulation and equalization to
recover the baseband data.
The baseband functions send the recovered baseband data to the transmission
functions. From here the uplink data is multiplexed onto the Abis Interface.
21 / 234
1 Overview
1.4.3 O&M Data Processing

The O&M functions are connected to all of the BTS functional entities, and also
(via the Abis Interface), to the BSC.
The BTS is responsible for its own fault detection and localization. The BSC
need not, therefore, know the internal structure of the BTS.
O&M functions are provided for:
Performance Management
Fault Management.
The O&M functions are described in O&M and Support Functions (Section 6).
22 / 234
1 Overview
1.5 Functional Units

The functional units are those elements that implement the BTS functions. The
functional units are described in the following sections.
1.5.1 9100 BTS

The functional units used in the 9100 BTS are:
Transmitter and Receiver Equipment (TRE)
Antenna Network (AN)
Station Unit Module (SUM).
These modules are installed in varied combinations within the 9100 BTS to
provide sectorized and omni-directional configurations. Other, non-intelligent,
modules provide connection and power supply services.
One SUMP can control up to 8 TRE modules in an omni-directional
configuration or 12 TRE modules in a sectorized configuration. In case of
Twin TRE usage one SUMA/SUMX can control up to 16 TRE modules in an
omni-directional configuration or 24 TRE modules in a sectorized configuration.
Each TRE module is connected to the antennae using the AN modules.
Different types of AN are available; their use depends on the number of TREs,
whether or not antenna diversity is used, and the type of configuration.
The 9100 BTS supports multiband BTSs, where different sectors of a
multisector configuration operate in different frequency bands. This allows an
increase in network capacity without installing new sites.
For more information about the functional units refer to Functional Units
(Section 7).
1.5.2 BTS 9110

The functional units used in the BTS 9110 are:
Micro-BTS Transmitter and Receiver Equipment (MTRE)
Micro-BTS Antenna Network (MAN)
Micro-BTS Station Unit Module (MSUM)
Connection Box (COBO).
For the BTS 9110 the MAN changes depending on if the BTS is configured with
one (MAN1) or two antennae (MAN2). All other functional unit configurations
are the same, regardless of whether sectorized or omni-directional
configurations are used. The master and slave BTSs are physically identical.
GSM 900 and GSM 1800 versions differ only in the analog part of the MTRE
and MAN. A single BTS 9110 entity consists of two MTREs and a MAN.
The MTRE can be configured to belong either to the same sector or to be
split into different sectors.
One MSUM (the BTS 9110 master) can control up to six MTRE modules
(that is, one master and two slaves) independent of the configuration
(omni-directional or sectorized configuration). Each MTRE module is connected
to the antennae using the MAN module.
Two different types of MAN are available. Their use depends on the use of
one antenna or two antenna BTS. For BTSs with one antenna, the MTREs are
23 / 234
1 Overview
internally combined in the MAN and therefore no receiver diversity is available.

For BTSs with two antennae, each of the units MTREs has an antenna and
receiver diversity is possible.
The BTS 9110 supports multiband BTSs, where different sectors of a
(Section 7).
There may be an optional SSC located adjacent to the 9110 Micro BTS.
If present, it can contain the network termination, the microwave and other
external equipment.
The SSC can provide power to up to three 9110 Micro BTSs.
1.5.3 9110 Micro BTS-E

The functional units used in the 9110 Micro BTS-E are:
Micro-BTS Transmitter and Receiver Equipment (MTREDA)
Micro-BTS Antenna Network (MAN)
Micro-BTS Station Unit Module (MSUMA)
Connection Box (COBO).
For the 9110 Micro BTS-E the MAN changes depending on if the BTS is
configured with one (MANM) or two antennae (MAND). All other functional
unit configurations are the same, regardless of whether sectorized or
omni-directional configurations are used. The master and slave BTSs are
physically identical. GSM 850, GSM 900 GSM 1800 and GSM 1900 versions
differ only in the analog part of the MTREDA and MAN. A single 9110 Micro
BTS-E entity consists of two MTREDA and a MAN. The MTREDA can be
configured to belong either to the same sector or to be split into different sectors.
One MSUMA (the 9110 Micro BTS-E master) can control up to 12 MTREDA
modules (one master and five cascading slaves), independent of configuration
(omni-directional or sectorized configuration). Each MTREDA module is
connected to the antennae using the MAN module.
Two different types of MAN are available. Their use depends on the use of one
antenna or two antennae BTS. For BTSs with one antenna, the MTREDAs
are internally combined in the MANM and therefore no receiver diversity is
available. For BTSs with two antennae, each of the units MTREDAs has an
antenna and receiver diversity is possible for MAND.
The 9110 Micro BTS-E supports multiband BTSs, where different sectors of a
(Section 7) .
There may be an optional SSC located adjacent to the BTS 9110-E. If present,
it can contain the network termination, the microwave and other external
equipment.
The SSC can provide power to up to three 9110/9110-E BTSs.
24 / 234
2 Channel Organization
This chapter describes the Air Interface channel organization.
The various features associated with these channels are described in the
following sections:
Radio Use
Channel Types
Channel Structure
Radio Resource Management
SMS-CB.
The chapter breaks down each category into individual functions, and explains
how each type of channel is used.
25 / 234
2.1 Introduction to Channel Organization

The Air Interface is the radio link between the BSS and the Mobile Station.
The Air Interface uses several channel types that are organized in combinations
according to GSM recommendations. The transmission of these channels is
managed in a logical manner according to the OSI seven-layer model. The
various features associated with these channels are described in the following
sections.
2.2 Radio Use

Four frequency ranges are supported by the Alcatel-Lucent BSS: GSM 850,
GSM 900, GSM 1800 and GSM 1900. Each range is divided into two bands.
One band is for use by the uplink, the other by the downlink.
The number of channels available depends on a number of factors.
2.2.1 Radio Transmission Channels

Radio transmission channels are spaced at 200 kHz intervals within each band.
A guard space is left at both ends of each band.
The number of uplink and downlink frequency channels used by a BTS is
determined by the desired cell capacity.
A 9100 BTS equipped with SUMP board can use up to 12 uplink frequency
channels, and up to 12 downlink frequency channels, with a sectorized
configuration. For an omni-directional configuration up to 8 channels are
allowed. A BTS 9100 equipped with SUMA/SUMX board and Twin TRE can
use up to 24 uplink frequency channels, and up to 24 downlink frequency
channels, with a sectorized configuration. For an omni-directional configuration
up to 16 channels are allowed.
A 9110 Micro BTS can use up to six uplink and downlink frequency channels in
an omni-directional or sectorized configurations.
A 9110 Micro BTS-E can use up to 12 uplink and downlink frequency channels
in a sectorized configuration.
26 / 234
2.2.2 Frequencies
The following table shows the uplink and downlink frequencies and the number
of transmission channels available.
System
Downlink (MHz)
Uplink (MHz)
Channels
GSM 850
869 - 894
824 - 849
124
GSM 900 (P-GSM)
935 - 960
890 - 915
124
GSM 900 (E-GSM)
925 - 960
880 - 915
174
GSM 1800
1805 - 1880
1710 - 1785
374
GSM 1900
1930 - 1990
1850 - 1910
299
Table 2: GSM 850, GSM 900, GSM 1800 and GSM 1900 Frequency Ranges
The 9100 BTS MINI and MEDI cabinets do not support the GSM 850 band.
GSM 850 is not supported by all BSS software releases. If you are in doubt
please contact the Alcatel-Lucent Customer Services.
The 9110 Micro BTS does not support the GSM 850 band nor the GSM 1900
band.
The analog part and the power amplifier support the E-GSM band, but the MAN
currently only supports the P-GSM band.
The 9110 Micro BTS-E supports the 850, 900, 1800 and the 1900 band.
2.2.3 Modulation Technique

GSM 850, GSM 900, GSM 1800 and GSM 1900 systems use GMSK
modulation, which provides a good compromise between spectral efficiency
and ease of demodulation.
27 / 234
2.3 Channel Types

The allocated uplink and downlink frequency bands use a combination of
FDMA and TDMA.
The use of FDMA and TDMA results in a large number of discrete physical
channels, each of which can carry traffic or signalling information.
The logical channels carried by the FDMA/TDMA time slots are classified
as either:
Signalling Channels
TCHs
Packet Switched Channels.
2.3.1 Signalling Channels

Signalling channels are divided into three groups, each containing a number of
channel types. Each group is described separately.
2.3.1.1 Broadcast Channels

BCHs are used to control Mobile Station RF transmissions. They also update
Mobile Stations on the status of the cells with which they can communicate.
There are three types of BCH:
FCCH
The Mobile Station uses the FCCH to synchronize its RF transmission
frequency to the allotted channel. It is also used by the Mobile Station when
the Mobile Station is first switched on, or otherwise enters a service area.
At this point, the FCCH enables the Mobile Station to obtain an approximate
indication of the boundaries between time slots. This reveals the position of
Time Slot 0, which the FCCH occupies. From this starting point, the Mobile
Station locates the SCH. It can then time its random access burst within
the available window (see below).
SCH
The SCH provides the Mobile Station with precise information about the
timing and frame numbering of the BTS. This enables the Mobile Station
to maintain correct frame alignment with the BTS timing schedule. The
Mobile Station advances its timing schedule to compensate for changes
in Mobile Station - BTS distance. (Refer to Layer 3 (Section 2.5.1), under
Dedicated Channel Management.)
BCCH
The BCCH carries general information. This includes the identity of
neighboring cells, maximum cell transmit power and details of the
configuration of the other signalling channels. In GPRS systems this
channel is known as the PBCCH.
28 / 234
2.3.1.2 Common Control Channels

The CCCH is used for access control and is shared between all Mobile
Stations in a cell.
There are three types of CCCH:
RACH
The RACH allows a Mobile Station to access the network. When a Mobile
Station first detects a BCH carrier, and if a location update is needed, it
tries to access the BTS. It does this by sending a random access burst on
the RACH. Timing of the random access burst is based on information
derived from the FCCH/SCH.
Once the Mobile Station is camped on a cell, it remains in Idle mode until it
needs to communicate with the BTS. For this purpose, it requests access to
dedicated radio resources.
Access can be requested:
To originate a call from the Mobile Station
In response to a Paging message when a call is originated by the network
When a location update becomes necessary.
The Access request is sent on the RACH in the form of an Access Request
message. In GPRS systems this channel is known as the PRACH.
AGCH
The AGCH is used by the BTS to send an Immediate Assignment message
to the Mobile Station, following an Access Request. The message allocates
an SDCCH to the Mobile Station, so that a TCH can be specified for the call.
In GPRS systems this channel is known as the PAGCH.
PCH
The PCH is used by the BTS to notify a Mobile Station that there is an
incoming call. The Mobile Station responds on the RACH.
29 / 234
2.3.1.3 Dedicated Control Channels

DCCHs are allocated to carry control information for a specific Mobile Station.
They can be of two types, associated or stand alone:
ACCH
The ACCH takes two forms, depending on the operational condition of
the Mobile Station:
SACCH
The SACCH is allocated with a SDCCH or TCH, and is present
throughout the duration of a call. It carries non-urgent control information,
including timing advance data.
FACCH
Unlike other channels, the FACCH has no dedicated part in the GSM
multiframe. Instead it steals capacity in the TCH when it is necessary to
send urgent control information. This process is referred to as bit stealing.
In GPRS systems this channel is known as the PACCH.
SDCCH
The SDCCH is allocated dynamically by an Immediate Assignment message
sent on the AGCH. It is used for low-rate control communication during
call establishment. The SDCCH specifies the TCH with an Assignment
command, and handles all signalling until the TCH is set up. The SDCCH is
also invoked during location update and for SMS.
2.3.2 Traffic Channels

There are five Full-Rate Traffic Channel (TCH/F) types and one Half-Rate Traffic
Channel (TCH/H) type. The following table shows the different types of channel.
Channel Type
TCH/F
TCH/H
Encoded speech
14.4 kbit/s data
9.6 kbit/s data
4.8 kbit/s data
2.4 kbit/s data
Table 3: TCH/F and TCH/H Types

In order to maximize the use of available bandwidth, TCHs are allocated to
Mobile Stations only when required. The allocation is therefore made only
when a call is established. An SACCH is always allocated with a TCH,
as described earlier.
30 / 234
2.3.3 Packet-Switched Channels

Just as for traffic (voice) services, different logical channels are defined for
GPRS / EGPRS. These channels are classified into traffic channels and control
channels. Some channels are bi-directional, other channels are uni-directional.
While its function is similar to the logical channels defined for voice service,
the Packet Timing Advance Control Channel (PTCCH) is new. In the uplink,
the mobile transmits a random access burst (one mobile per PTCCH). In the
downlink, the network transmits timing advance information to the mobiles
(several mobiles per PTCCH).
For GPRS the packet data blocks CS-1, CS-2, CS-3 and CS-4 and all packet
control channels are implemented. All channels configured as TCHs can
be dynamically configured for packet switched channels. This dynamic
configuration is handled by the BSC.
Up to eight Packet Data Traffic Channels (PDTCH) (limited to five due to mobile
constraints in the first software releases) on different time-slots but on the same
transceiver can be allocated to one mobile at the same time (depending
on the multi-slot capabilities of the mobile). Several mobiles can share the
same PDCH.
It is possible to mix GPRS and EGPRS on the same Packet Data Channel
(PDCH). Up to 16 users can share a Packet Data Channel (PDCH). The
Alcatel-Lucent implementation allows a maximum of seven users in uplink plus
nine users in downlink for the initial release. In later releases, a maximum of six
users in uplink plus ten users in downlink can share one PDCH.
31 / 234
2.4 Channel Structure

A group of one or more channels can be multiplexed onto a single time slot in
successive TDMA frames, in a cyclical manner.
The following table shows the channel combinations allowed by GSM rec.
05.02 Sec. 6.4. Full-rate and half-rate channel combinations are available in
all BTS hardware configurations. For further details about possible hardware
configurations, refer to Functional Units (Section 7).
Multiframe
Type
Channel Combination
26-multiframe TCH/F + FACCH/F + SACCH/F

TCH/H + SACCH/H + FACCH/H
51-multiframe BCCH + CCCH + SCH + FCCH
FCCH + SCH + BCCH + PCH + RACH + AGCH +
4 x SDCCH/4 + SACCH x 4
BCCH + PCH + RACH + AGCH
8 x SDCCH/8 + SACCH x 8
Table 4: Possible Channel Combinations for Single Time Slot
Channels are multiplexed into the following types of frame with a fixed
relationship between transmit and receive timing.
Frame Type
Description
26-Multiframe
The simplest example is the TCH and SACCH. These are combined into a 4 x 26 TDMA
frame cycle, known as the 26-multiframe. The FACCH has no allocation on the time slot
- it relies on bit stealing.
51-Multiframe
A second cycle, the 51-multiframe, is used for non-TCH combinations, including the
BCCH. Due to their differing lengths, the start of the 51-multiframes becomes offset with
respect to the start of the 26-multiframes. During the resulting time interval, any Mobile
Station that is handling a call also monitors the surrounding cells. The signals that are
monitored from the surrounding cells are the SCH and FCCH signals. The surrounding
cells can be synchronized or unsynchronized. Resulting measurements are sent to the
BTS, then to the BSC, which uses them to assess the need for handover.
Superframe
The 26 and 51-multiframes are themselves framed into superframes. Superframes are
made up of 51 sets of 26-multiframes or 26 sets of 51-multiframes.
Hyperframe
Superframes are framed into hyperframes. A hyperframe consists of 2048 superframes.

This enables every frame to be separately numbered over a period of approximately
3 hours. All the frames are synchronized to the same timing schedule.
Transmit/
Receive
Timing
The Mobile Stations transmit the uplink three time slots later than the BTS transmits the
downlink (minus the transmission delay). Therefore, at any instant the Mobile Station need
only transmit or receive.
For further details of the Air Interface channel structure, refer to GSM rec. 05.01.
32 / 234
2.5 Radio Resource Management

Air Interface communication is managed in OSI-type layers. Although there
are seven layers in the OSI model, the BTS functions are concerned with
only the three lower layers.
2.5.1 Layer 3
Layer 3 radio resource functions provide general management of the Air
Interface channels. The majority of the control processing is performed in the
BSC, the BTS simply acting upon BSC commands.
2.5.1.1 Radio Channel Selection

The BTS carries out free-channel interference measurements. These enable
the BSC to determine which channels are currently the most suitable for
use by both traffic and signalling.
2.5.1.2 Channel Establishment

Radio Link Management and Channel State Control functions establish the Air
Interface channels assigned by the BSC.
2.5.1.3 Handover Preparation

A handover procedure can be initiated by the BSC to maintain or improve call
quality once channels have been assigned. The same mechanism can also
be used to optimize use of the network (e.g., reduce interference, alleviate
local congestion, etc.). The handover procedure is based on measurements
made at the Mobile Station and BTS.
The procedure can re-allocate the Air Interface channels used in the present
cell (intra-cell handover). It can also hand over the Mobile Station to a different
BTS and its associated cell (inter-cell handover). Handover is relevant to both
dedicated and common channels.
33 / 234
2.5.1.4 Dedicated Channel Management

Dedicated Channel Management functions control the radio communication
between the BTS and each Mobile Station. Some control is carried out in the
BTS but overall management of the channels is under control of the BSC. For
this purpose, the BSC makes use of measurements carried out for each
channel in the Mobile Station and in the BTS.
Channel Management is handled as a Layer 3 function, using the RSL between
the BSC and the telecommunication functions. The RSL uses the LAPD.
The dedicated channel management functions are:
Power Control
In order to minimize Mobile Station power consumption and co-channel
interference, the Mobile Station adjusts its transmit power to an acceptable
minimum. The power level is based on uplink signal strength measurements
made in the BTS.
Similar measurements are made in the Mobile Station for the received
signal strength on the downlink. Measurement results are sent to the BTS,
which sets the transmitter power output for each time slot. BCCH time slots
are transmitted at constant power.
In GPRS systems there is no power control on the downlink. Uplink power
control is still performed by the Mobile Station, based on configuration
parameters set by the MFS.
Timing Advance
As the distance between a Mobile Station and the BTS changes, burst
transmissions from the Mobile Station must remain aligned with the allocated
Air Interface time slots. Each Mobile Station therefore advances its burst
transmission time, to compensate for changes in the radio propagation delay.
This advance is made relative to the basic schedule the Mobile Station
derives from received bursts. Timing advance changes for each Mobile
Station are calculated within the BTS, which sends them to the Mobile
Station on the SACCH twice every second.
In GPRS systems the timing advance is transmitted from the BTS to the
Mobile Station every 26th TDMA frame via the PTCCH. The BTS also
controls the timing between the BTS and the MFS.
2.5.1.5 Common Channel Management

Common Channel Management functions use BCHs to handle shared control
communication between the BTS and Mobile Stations.
The common channel management functions are:
Channel Request
When an Mobile Station needs to access the network, it sends a random
access request to the BTS. The BTS sends the request to the BSC together
with reception measurements taken by the BTS.
Channel Scheduling
Channel Scheduling ensures that Mobile Stations not carrying traffic,
need only listen to the Air Interface at pre-determined time intervals. This
minimizes power consumption.
2.5.1.6 Flow Control

The Flow Control function raises an alarm at the BSC in the event of a BTS
processor overload.
34 / 234
2.5.2 Layer 2
The Air Interface Layer 2 functions handle the reliable transmission of speech
and data frames between the BTS and Mobile Stations. The protocol used is a
variant of LAPD known as LAPDm.
LAPDm transparently transfers complete messages, and handles automatic
retransmission in the event of detected errors.
2.5.3 Layer 1
The Layer 1 functions handle the physical transmission of data over the Air
Interface.
2.5.3.1 Modulation and Demodulation

The digital stream of downlink control and traffic data is used to modulate the
RF carrier. The modulated carrier is then transmitted in the GSM RF band.
A separate demodulator converts the uplink radio signals received from the
Mobile Stations back to digital form.
2.5.3.2 Multiframe Scheduling

Signalling and traffic data is time interleaved. Each channel uses a single time
slot in successive or periodic TDMA frames.
2.5.3.3 Encoding and Decoding

These two functions are very similar in the way they process information.
Decoding is essentially the reverse of Encoding.
Speech and data traffic, and data for signalling channels are encoded to
produce a string of TDMA bursts. These encoded bursts are transmitted over
the Air Interface. Encoding is achieved using a combination of convolutional
and block encoding.
The Decoding function processes uplink information and is applied after
demodulation and de-interleaving. It produces a GSM-compliant bitstream by
performing a combination of convolutional and block decoding. Convolutional
decoding is performed on all received channel types. Block decoding is applied
to Control Channels and TCH.
2.5.3.4 Encryption and Decryption

Encryption and Decryption protect the confidentiality of messages sent over the
Air Interface. The baseband functions carry out Encryption and Decryption on
TCHs and dedicated control channels only. Common channels are transmitted
without encryption.
Encryption is implemented using the confidential A5 algorithm. Decryption
uses the same algorithm and is the reverse of Encryption.
2.5.3.5 Signal Strength and Signal Quality Measurements

Information about the signal quality and received signal strength of all channels
is sent to the BSC. The BSC uses this information to exercise Power Control
and Handover functions. Both uplink and downlink channels are monitored for
this purpose.
35 / 234
2.5.3.6 Interleaving and De-interleaving

Interleaving is applied to the encoded sub-blocks, to improve the error
detection rate. The baseband telecommunications functions are responsible
for interleaving data for the downlink, and for de-interleaving data received
on the uplink.
There are three interleaving processes:
Sub-block partitioning
Inter-block interleaving
Intra-burst interleaving.
All the logical channels follow this scheme, except that bursts carried by the
BCCH are not interleaved.
2.6 SMS-CB
There are two mutually exclusive types of SMS-CB, simplified and complete.
Each type is described in detail in the following sections.
2.6.1 Simplified SMS-CB

In the simplified version, the BTS places the broadcast messages in the
TDMA frame structure.
These messages consist of four consecutive blocks.
The BTS uses the repetition frequency of broadcast commands on the Abis
Interface together with some buffering mechanism to guarantee a proper
mapping of the psuedo-synchronous commands received from the BSC
onto the synchronous air interface.
The simplified version allows the continuous broadcast of one single
message on a per cell basis.
Messages are stored in the TCU.
The BSC sends broadcast messages to the BTS at the maximum repetition
rate of approximately once every 1.88 seconds.
The message scheduling is the responsibility of the OMC-R.
36 / 234
2.6.2 Complete SMS-CB

The complete version is more complex. There are two types of CBCH, the
basic channel supported by the simplified SMS-CB, and the extended channel
that is needed to support the additional functions of the complete SMS-CB.
The complete SMS-CB uses both CBCH, basic and extended, to provide
double the channel capacity of the simplified SMS-CB. The basic CBCH is
broadcast within the first four multi-frames of the TDMA frame and the extended
CBCH is sent in the last four multi-frames.
The BTS:
Transmits the SMS-CB messages on the given CBCH under control from the
BSC and transmits null messages when nothing is received from the BSC
Stores up to 150 message pages per cell. Multi-page messages can
be sent, with an assigned message priority. High priority messages are
broadcast in reserved time slots. Normal and background messages
are sent in the next free time slot
Reports CBCH or memory overload when the CBC request cannot be
satisfied
Performs the scheduling broadcast on a per cell or CBCH basis as
requested by the CBC
Provides GSM phase 2 DRX to allow Mobile Station battery saving by
setting a last block bit in the SMS-CB message
Counts the number of broadcast-realized messages on a cell and channel
basis (used for billing purposes)
Reports to the CBC, after a Replace or Kill request, the number of
broadcasts realized for a message on a per cell basis for a given CBCH
channel
Provides a counting function to give the CBC loading information.
There are five SMS-CB cell states, Inactive, Idle, Configured, Operational,
and Failure.
There are two SMS-CB message states:
Active, where the message is being broadcast
Realized, where all requested broadcasts have been performed.
37 / 234
38 / 234
3 Transmission Functions
This chapter describes how BTSs are linked to the BSC via the Abis Interface.
After introducing the general arrangement, the chapter explains how data is
multiplexed to allow a single Abis Interface to service the full traffic capacity of
a BTS. The chapter includes a list of different options for implementing the
Abis Interface at the physical layer.
Clock recovery is outlined, plus the alternative network configurations, and the
GPRS transmission plane are described.
39 / 234
3.1 Introduction to Transmission Functions

To minimize transmission costs, all uplink/downlink traffic and control data
between the BTS and BSC is carried on a single Abis Interface. This interface
is supervised by transmission functions at the BTS and BSC.
Within the BTS the Abis Interface uses the following links to handle the transfer
of traffic and control data between the BTS transmission functions and the
BTS components:
Data
LAPD RSL
LAPD OML.
The following figure shows a simplified block diagram of these interfaces
and links.
BSC
BTS
LAPD RSL
BTS
Components
LAPD OML
Data
Transmission
Functions
Abis Interface
Transmission
Functions
Figure 6: BTS to BSC Transmission
3.2 Multiplexing Scheme

Each baseband datastream through the BTS requires a transmission capacity
on the Abis Interface of 128 kbit/s for traffic, and 64 kbit/s for signalling
purposes. Additionally the O&M function requires a 64 kbit/s channel.
The following sections describe how the multiplexing allows all BTS to BSC
communications to be carried on a single interface.
3.2.1 Abis Interface

The 2 Mbit/s bandwidth of the Abis Interface is used as 32 time slots, each of
64 kbits. These 32 time slots comprise one CCITT G703/704 frame.
Data on the Abis Interface uses the following Layer 2 protocols at submultiplex
levels:
LAPD RSL
LAPD OML
Q1 time slot.
The first time slot in each frame is reserved for G703/704 management
including the Q1 service interface. The remaining 31 time slots in each frame
are used as described in the rest of this section.
40 / 234
3.2.1.1 Second Abis Interface

Without EDGE/EGPRS, the amount of information provided per Air interface
time slot allowed to have the eight time slots of one TRX mapped onto two
64 kbit/s time slots of the Abis interface (adding some time slots for signalling
and O&M). Using this scheme, even a fully equipped BTS cabinet can be
served by one E1-interface (PCM30).
Introducing EGPRS, the amount of information provided by the time slots of
the Air interface increases. If a BTS is fully equipped with TRXs, one E1-link
is no longer sufficient to carry all data between the BTS and BSC. With the
introduction of GPRS step 2 and EGPRS, the possibility to connect two E1-links
between BTS and BSC is added.
Introducing the Twin TRE module and the support of up to 24 TRXs per BTS
the need of resources is also increased so the posibility to connect a second
Abis is necessarry.
To support the second Abis link the Alcatel-Lucent BTS must be equipped
with SUMA/SUMX board.
Using two Abis links, OML and basic time slots are always mapped to the first
link and the extra time slots for the TRX transmission pools are split over
the two Abis links.
Primary Abis Link
BT BT
BT BT ET ET ET ET
OML RSL BT BT RSL BT BT RSL BT BT RSL RSL
BSC
BTS
Secondary Abis Link
ET ET ET ET ET ET ET ET
BT
Basic Timeslot
ET
Extra Timeslot
Figure 7: Second Abis Interface, Time Slot Mapping

RSL with corresponding TCH and extra timeslots can be mapped over the
primary or secondary Abis link. RSL with corresponding TCH must be mapped
on the same Abis link.
For a BTS with two Abis links the operator defines a new parameter:
MAX_EXTRA_TS_PRIMARY, that is, the maximum number of extra time slots
the system is allowed to allocate on the first Abis for this BTS.
To keep the maximum free time slots on the secondary Abis for another BTS,
the allocation of extra time slots is done in priority on the first Abis until this Abis
is full or MAX_EXTRA_TS_PRIMARY is reached.
To help the tuning of this parameter, the TSU occupancy is reported on demand
to the operator and, in case of failed operation, the number of missing TCU
resources is also reported.
41 / 234
3.2.1.2 Second Abis Supervision

As already done today, when the BTS detects a problem on the second Abis,
it reports it to the BSC through the fault indication message. In turn, the
BSC translates this Abis message into an alarm report message towards
the OMC-R.
If the detected alarms on the second Abis link is one of the following:
BER-3
LOS
LFA
LMFA
AIS
RAI.
and it is either a BEGIN or an END (events are ignored), then the BTS informs
the BSC using the existing recovery message, but applied to another SBL. The
recovery message will contain the SBL Abis_HW_TP (N2), corresponding
to the second Abis.
Moreover, the recovery message with this SBL will be sent by the BTS, when
there is an audit and at OMU/BTS reset, restart and init (if the Abis Highway
TP is not in service and the second Abis is used).
3.2.2 Multiplexing
On the downlink, the BSC transmission functions multiplex the data onto the
Abis Interface. At the BTS the data is demultiplexed by the BTS transmission
functions.
The transmission functions for a single BTS provide connections for up to two
Abis Interfaces. This allows multiple BTSs to be connected to a single BSC
using chain or ring configurations.
The 9110 Micro BTS/9110-E Micro BTS has two separate 2 Mbit/s Abis
interfaces to allow for multidrop configurations.
Uplink data is multiplexed onto the Abis Interface by the BTS transmission
functions. The process used is similar to that employed by the BSC for downlink
data. The mapping between the transmission functions and Abis links for both
uplink and downlink is programmable.
3.2.3 Signalling
Signalling frames are sent via the RSL between the BSC and the baseband
functions, and via the OML between the BSC and the O&M functions.
One 64 kbit/s channel is allocated to each BTS baseband datastream for
signalling data. A similar 64 kbit/s channel is provided for the O&M function.
One RSL is required for each BTS carrier. Each RSL can be:
Multiplexed onto a separate 64 kbit/s time slot. This allows up to eight
carriers to be supported.
Static submultiplexed, which combines up to four RSLs into one 64 kbit/s
time slot. This allows up to 12 carriers to be supported.
42 / 234
If up to 24 carriers must be supported in one BTS the static multiplexing

solution must be used.
3.2.4 Transmission O&M

The TSC regularly polls the BSS transmission equipment, including that at
the BTS. A service interface is therefore provided on the Abis Interface to
carry data for this function.
The Q1 service interface consists of a 16 kbit/s nibble, which uses part of the
first time slot or part of one of the other time slots. Configuration rules exist to
ensure that room for the Q1 bus is always available. This applies even when
a number of BTSs are connected to the Abis Interface. The BTSs can be
attached in a chain or ring configuration.
3.2.5 Traffic
Time slots not used for signalling information are available to carry traffic. For
this purpose, each 64 kbit/s time slot is divided into four 16 kbit/s nibbles.
For TCH/F, each nibble is dedicated to a single traffic channel for the duration of
a call. Each time slot is shared between four, full-rate TCHs - i.e., between
four different calls. Each carrier of the BTS thus requires two PCM time slots
for its full capacity of eight TCH/F.
For TCH/H, each nibble can support two different traffic channels. Each time
slot is therefore shared between eight, half-rate TCHs - i.e., between eight
different calls. Each carrier of the BTS can carry sixteen TCH/H by using
two time slots.
3.2.6 Clock
Signals on the Abis Interface are normally synchronized to the PCM master
clock at the MSC. There is no separate line for the clock, which must therefore
be recovered from the signal at each receiver.
If a GPS receiver is installed, alternatively synchronization can be performed by
using the precise GPS clock.
3.2.7 Network Configuration

The network configurations for the 9100 BTS and 9110 Micro BTS/9110-E Micro
BTS are different. These configurations are described in the following sections.
3.2.7.1 9100 BTS Configuration

9100 BTSs can be connected to the BSC via star or multidrop (chain or
ring) configurations. Star connection is always used for high-capacity 9100
BTSs which require all or most of the Abis Interface bandwidth. Since the
introduction of GPRS/EGPRS and the usage of the Twin TRE a second Abis
Interface is supported by the BTS in order to provide better data flow. Chain or
ring architecture enables low-capacity 9100 BTSs to share the bandwidth of
an Abis connection.
In multidrop configurations, the Abis signal is routed through each 9100 BTS,
where it is regenerated before being sent to the next equipment. If the 9100
BTS is removed, the vacant Abis connector must be bridged to maintain
Abis continuity.
43 / 234
If the 9100 BTS is not powered, the routing of the Abis signal is performed by
an internal relay which connects the input line to the output line. This passive
connection allows the Abis signal to be routed to the next equipment.
44 / 234
3.2.7.2 9110 Micro BTS/9110-E Micro BTS Configuration

9110 Micro BTS/9110-E Micro BTSs can be connected to the BSC via a
multidrop configuration. In multidrop configurations, the Abis signal is routed
through the 9110 Micro BTS/9110-E Micro BTS, where it is regenerated before
being sent to the next equipment.
If the 9110 Micro BTS/9110-E Micro BTS is removed, is faulty, or is unpowered,
an internal relay connects the input line to the output line. This passive
connection allows the Abis signal to be routed to the next equipment.
3.3 Abis Interface Physical Connection

For indoor 9100 BTS, the 9100 BTS and BSC multiplexing equipment is
normally connected using dedicated cabling.
Other methods of Abis Interface connection can be used for outdoor BTSs,
where the installation of dedicated cabling is not possible. In this case, control
of the transmission medium is in the hands of a third party.
Examples of this type of connection include:
Microwave Link
Used where a line-of-sight radio path is available.
Leased Line (copper cable or fibre optic)
Used where no line-of-sight link is available, or, where the distance between
the BSC and BTS is too great for microwave.
45 / 234
3.3.1 Second Abis Topologies

The second Abis is interesting when there is not enough space on one
complete Abis for all the BTS time slots. For a second Abis, the primary Abis
must be fully assigned to the BTS. So the secondary Abis cannot be attached
to a BTS if the BTS is not alone on the primary Abis.
Only BTS with SUMA/SUMX boards or 9110-E Micro BTS support the second
Abis link. The BTS with a SUMP board has to be upgraded.
The baby board on the SUMA board that allows the BTS to manage four
Abis termination points is not used.
The SUMX can manage four Abis termination points without any additional
baby board.
Without the baby board on the SUMA, a BTS can manage only two termination
points.
This implies that it is not possible to:
Connect a BTS in chain after a BTS with two Abis
Change the Abis from chain to ring if there is a BTS with two Abis
Attach a second Abis to a BTS that is not at the end of an Abis chain
Attach a second Abis to a BTS that is in an Abis ring.
Consequently, only two added Abis topologies are supported:
Primary Abis
TP1
BSC
Secondary Abis
EVOLIUM
BTS
TP2
Figure 8: Second Abis Interface, Topology 1
Primary Abis
Secondary Abis
BSC
TP1
EVOLIUM
BTS or
G1/G2 BTS
TP2
TP1
EVOLIUM
BTS or
G1/G2 BTS
TP1
EVOLIUM
BTS
TP2
TP2
Figure 9: Second Abis Interface, Topology 2
46 / 234
The primary Abis and the secondary Abis of a BTS can be on different TSU in
different racks.
47 / 234
3.3.2 No Cross Connect for Second Abis

There is no restriction regarding cross-connect on the primary Abis.
But, on the secondary Abis, because there is no RSL on this Abis, the fault
management of the link is based on transmission alarms. And as transmission
alarm propagation through a cross-connect is not assured, cross-connects
are not allowed on the second Abis. It is physically possible, but the system
does not and cannot check it.
Cross
Connect
Primary Abis
TP1
BSC
EVOLIUM
BTS
TP2
Cross
Connect
TP1
EVOLIUM
BTS or
G1/G2 BTS
Cross
Connect
TP2
Secondary Abis
Figure 10: Second Abis Interface, Cross Connect
48 / 234
3.4 GPRS Transmission Plane

The GPRS transmission plane consists of a layered protocol structure. This
structure provides user information transfer, along with associated information
transfer control procedures such as flow control, error detection, error
correction, and error recovery.
The independence of the transmission plane from the underlying Air interface is
preserved via the GB.
The signalling plane consists of protocols for control and support of the
transmission plane functions for controlling:
GPRS network access connections, such as attaching/detaching from
the GPRS network
Attributes of an established network access connection, such as activation
of a PDP address
The routing path of an establish network access connection, in order to
support user mobility
Assignment of network resources to meet changing user demands and
providing supplementary services.
The following figure shows the functional layout of the protocol layer.
G
M
M
/
S
M
S
N
D
C
P
RR
BSSGP
LLC
RRM
RRM
L2RSL L2GSL
L1RSL L1GSL
RLC
MAC
BSC
Abis
B
S
S
G
P
RLC
MAC
BSSGP
Ater
NS
L2GCH
GSM RF
GSM RF
L1GCH
MSTS
BTS
L2RSL
L1RSL
L2GSL
L1GSL
Abis/Ater
L2GCH
L1GCH
FR
to SGSN
MFS
Figure 11: GPRS Transmission and Signalling Planes

This protocol layer is composed of the following elements, in relation to the BTS.
Relay - relays the RLC PDUs between the L1 Ater and Um interfaces
L1-RSL - the physical layer between the BSC and the BTS using 64 or
16 kbit/s channels
L2-RSL - a LAPD protocol between the BSC and the BTS.
49 / 234
For user data traffic and CCCH signalling when the GPRS is present, the BSC
is transparent and lines are replaced with GCH lines as follows:
L1-GCH - the physical layer between the MFS and BTS which uses the
synchronous mode of transmission
L2-GCH - a simple proprietary protocol between the MFS and the BTS for
synchronization and channel activation.
50 / 234
4 Telecommunication Functions - Baseband

This chapter describes the baseband telecommunications functions.
These are divided into the following categories:
Baseband Processing functions
Call Management functions
Supervisory and Control functions.
The chapter breaks down each category into individual functions, and
explains how these work together to prepare the downlink baseband data for
transmission over the Air Interface. The chapter also explains how the process
is reversed for uplink data.
51 / 234
4.1 Introduction to Telecommunication Functions - Baseband

The baseband telecommunication functions adapt the downlink terrestrial
bitstream to the format required for transmission over the Air Interface. On
the uplink, the process is reversed.
The three categories of the baseband telecommunication function are
described in the following sections.
4.2 Baseband Processing

Baseband processing consists of several functions shown in the following figure
and described in the following sections.
Baseband Functions
RF Functions
Terrestrial Traffic
Downlink Direction
RF
Transmission
Encryption
Interleaving
Channel
Encoding
Speech
Transcoding
Rate
Adaptation
Transmission
and
Transcoder
Functions
Duplexing
Uplink Direction *
RF
Reception
De
modulation
Decryption
De
interleaving
Channel
Decoding
To/From
Mobile
services
Switching
Center
Speech
Transcoding
Rate
Adaptation
* Some uplink functions are duplicated for Antenna Diversity.
Figure 12: Baseband Telecommunication Functions
4.2.1 Speech Transcoding

TC functions are logically assigned to the BTS. The TC is physically located
between the MSC and the BSC. It is connected to the BTS, via the BSC using
the Abis Interface. The TC performs speech transcoding and rate adaptation on
the TCHs in both downlink and uplink directions.
Speech transcoding is performed on speech traffic only. The process is
52 / 234
4.2.1.1 Speech Traffic

For downlink speech traffic, two separate processes are carried out on full-rate
and half-rate speech. These processes are, two-stage speech transcoding,
and bit-reordering. The bitstream is then passed to the Channel Encoding
function as a sequence of blocks.
The speech transcoding process is shown in the following figure.
GSM rec. 08.60
GSM rec. 04.21
Encoding
Function
Channel
Encoding
6.5 kbit/s
13 kbit/s
GSM rec. 06.10 TCH/F

GSM rec. 06.20 TCH/H
TC Function
8 kbit/s
16 kbit/s
RAS
Speech
Transcoding
64 kbit/s
Abis Channel
RAS is a GSMspecified rate adaptation
Figure 13: Speech Transcoding for Speech Traffic
4.2.1.2 Correspondence Between Traffic and Channel Types

The following table shows the relationship between the Speech Traffic Type,
the Air Interface Rate and the possible channel types. The table applies to
TCH/F and TCH/H channel types.
Speech Traffic Type
Air Interface Rate (kbit/s)
Possible Channel Types
Full-rate Speech
13
TCH/F Speech
Half-rate Speech
6.5
TCH/H Speech
Table 5: Correspondence Table of Speech Transcoding
4.2.1.3 Bit Re-ordering

In addition to speech transcoding, another process is performed on speech
traffic. This is the process of bit re-ordering. Bit re-ordering is necessary
because individual bits in the encoded speech can make an unequal
contribution to the subjective speech quality. Re-ordering enables bits to
be given the protection of parity and/or convolutional encoding, according
to their importance.
Bit re-ordering can be performed by the TC or the baseband functions. The
remote location of the TC introduces an overhead in transmission time via
the Abis link. This increases the importance of minimizing speech coding
and decoding delays.
To minimize delays, speech bit re-ordering is carried out by the baseband
functions. This enables the TC to start sending partly coded data on the
downlink, before finishing the coding of a speech frame. Bit re-ordering can
therefore start in the BTS without waiting for the TC to finish processing the
complete frame.
On the uplink, the processes of speech transcoding and bit- re-ordering are
effectively reversed. This recovers the original bitstream from the Mobile
Stations transmission.
53 / 234
4.2.2 Rate Adaptation

The rate adaptation function adapts the TC data rate to the speech frame format
used on the Air Interface. Rate adaptation is performed on data traffic only.
Rate adaptation is the process of modifying the bitstream and changing the
data rate between the TC and the Air Interface (or vice-versa). This mechanism
forms an essential part of the Layer 1 interface between the two different
baseband coding schema used by the Air Interface and the terrestrial link. Rate
adaptation is applied only to TCHs carrying data.
The responsibilities for carrying out rate adaptation are shared between the
baseband functions and the TC.
The process of rate adaptation is described in the following sections.
4.2.2.1 Data Traffic

In the downlink direction, V.110 data frames received by the TC are adapted in
a three-stage process to one of three possible Air Interface rates.
The data traffic rate adaptation process is shown in the following figure.
GSM rec. 04.21
3.6 kbit/s
6 kbit/s
12 kbit/s
14.5 kbit/s
GSM rec. 08.60
GSM rec. 04.21
Encoding Function
TC Function
16 kbit/s
8 kbit/s
RA1/RA1
GSM rec. 08.54
16 kbit/s
RAA
64 kbit/s
RAA
Channel
Encoding
RA2
RA2, RAA and RA1/RA1 are GSMspecified rate adaptations
Figure 14: Rate Adaptation for Data Traffic

The Air Interface uses the lowest rate compatible with the current user data
rate. This arrangement allows the maximum level of redundancy to be
introduced into the bitstream.
For TCH/F, the Air Interface rates of 14.5, 12, 6 or 3.6 kbit/s support user
data rates of:
14400 bit/s
9600 bit/s
4800 bit/s
2400 bit/s
1200 bit/s
600 bit/s
300 bit/s.
User rates below 2400 bit/s are rate-adapted to 2400 bits/s by simple bit
repetition. As a result, the Encoder only has to support four user data rates:
14.4, 9.6, 4.8 or 2.4 kbit/s.
Rate adaptation in the uplink direction is essentially a reverse of processing
carried out on data traffic for the downlink.
54 / 234
4.2.2.2 Correspondence Between Data Rates

The following table shows the relationship between the User Data Rate, the
Intermediate Data Rate, the Air Interface Rate and the possible channel types.
The table applies to TCH/F channel types only.
User Data
Rate (bit/s)
Intermediate Data
Rate (kbit/s)
Air Interface
Rate (kbit/s)
Possible
Channel
Types
300
3.6
TCH/F2.4
600
3.6
TCH/F2.4
1200
3.6
TCH/F2.4
2400
3.6
TCH/F2.4
4800
TCH/F4.8
9600
16
12
TCH/F9.6
14400
16
14.5
TCH/F14.4
Table 6: Correspondence Table of Rate Adaptation
55 / 234
4.2.2.3 Packet-switched Traffic

GPRS was implemented in order to enable data transmission at a bit rate
exceeding the capabilities of GSM. Basically, GPRS relies on new coding
schema on the Air interface that allow a higher data throughput.
HSDS supports GPRS with the CS-1 to CS-4 coding schema and EGPRS with
the MCS1 to MCS9 coding schema.
The following table gives the data rates based on the different coding schema.
Scheme
Modulation
Maximum rate [kbps]

per radio TS basis
CS-4
GMSK
21.4
CS-3
GMSK
15.6
CS-2
GMSK
13.4
CS-1
GMSK
9.05
EGPRS was implemented in order to enable data transmission at a bit rate

exceeding the capabilities of GPRS. Basically, EGPRS relies on new modulation
and coding schema on the Air interface allowing for a data throughput optimized
with respect to radio propagation conditions (Link Adaptation).
The basic principle of link adaptation is to change the Modulation and Coding
Schema (MCS) according to the radio conditions. When the radio conditions
worsen, a more protected MCS (more redundancy) is chosen, leading to a lower
throughput. On the contrary, when the radio conditions become better, a less
protected MCS (less redundancy) is chosen, leading to a higher throughput.
Nine modulation and coding schema are proposed for EGPRS, providing
raw RLC data rates ranging from 8.8 kbit/s (minimum value under the worst
radio propagation conditions per time slot) up to 59.2 kbit/s (maximum value
achievable per time slot under the best radio propagation conditions). Data
rates above 17.6 kbit/s require that 8-PSK modulation be used on the Air
interface, instead of the regular GMSK.
56 / 234
The following table shows the data rates based on coding scheme and
modulation type.
Scheme
Modulation
Maximum rate [kbps]

per radio TS basis
MCS-9
8-PSK
59.2
MCS-8
8-PSK
54.4
MCS-7
8-PSK
44.8
MCS-6
8-PSK
29.6
MCS-5
GMSK
22.4
MCS-4
GMSK
17.6
MCS-3
GMSK
14.8
MCS-2
GMSK
11.2
MCS-1
GMSK
8.8
: Note that the maximum data rate given in the above table refers to the RLC
payload (= the throughput offered to the Logical Link Control LLC) layer). The
RLC/MAC header, Block Check Sequence (BCS), Tail bit etc. are already
subtracted.
Table 7: Data Rates for Different Modulation and Coding Schema
57 / 234
4.2.3 Channel Encoding and Decoding

These two functions are very similar in the way they process information.
Channel Decoding is essentially the reverse of Channel Encoding.
4.2.3.1 Channel Encoding

Channel Encoding is the baseband processing implemented by the channel
encoding algorithm, as defined in GSM rec. 05.03, version 5.2.0 or later.
Data for Channel Encoding is received from the Speech Transcoding or Rate
Adaptation function (speech and data traffic), and from the upper OSI layers
(data for signalling channels). From these inputs, the Channel Encoding
function produces a string of encoded TDMA bursts for transmission over the
Air Interface. The resulting bursts can also carry information for internal BTS
control and test purposes.
Channel Encoding is achieved using a combination of convolutional and block
encoding. Convolutional encoding produces a greater number of output bits
than there are input bits. Applying convolutional encoding to reordered
speech bits enables the most important bits to be given the protection of a
high level of redundancy.
Four types of burst are encoded:
Normal Burst (encoded) which is used on the traffic and signalling channels
Synchronization Burst (encoded) which is used on the SCH
Frequency Correction Burst (fixed pattern) which is used on the FCCH
Dummy Burst (fixed pattern) which is used for empty BCCH time slots and
unused TCH time slots.
4.2.3.2 Channel Decoding

The Channel Decoding function processes uplink information. Channel
Decoding is left largely to the system manufacturer, but is essentially the
reverse of encoding.
A BTS configured for antenna diversity provides two receive paths, allowing
uplink signals from two separate antennae to be processed. Each incoming
time slot has two uplink signals which are combined in the Channel Decoder.
For traffic and signalling received in the uplink, Channel Decoding is applied
after demodulation and de-interleaving. Channel Decoding is essentially the
reverse of Channel Encoding. It produces a GSM-compliant bitstream ready for
Speech Transcoding or Rate Adaptation and onward routing to the terrestrial
path. This is done by a combination of convolutional and block decoding.
Convolutional decoding is performed on all received channel types, and is
achieved by applying the Viterbi algorithm.
Block decoding is applied to Control Channels and TCH, both full and half-rate.
It uses a dedicated routine defined in GSM rec. 05.03 for Channel Decoding.
58 / 234
4.2.4 Interleaving/De-interleaving
Interleaving is applied to the channel-encoded sub-blocks, to improve the error
detection rate. The baseband telecommunications functions are responsible
for interleaving data for the downlink, and for de-interleaving data received
on the uplink.
The interleaving process can be divided into the following three processes.
All the logical channels follow this scheme, except that bursts carried by the
BCCH are not interleaved.
1. Sub-block Partitioning
The first stage in the interleaving process is to split the encoded bits of a
speech or data channel into sub-blocks. These can be partitioned into
further sub-blocks depending on the type of channel. Sub-blocks are then
transmitted within the TDMA frame structure as defined by the inter-block
interleaving scheme, summarized in the following description.
2. Inter-block Interleaving
Interleaving of the sub-blocks is diagonal for TCH and FACCH, or rectangular
for signalling channels. The effect of these two types of interleaving is to
enable blocks to be mapped onto bursts according to the channel type.
3. Intra-burst Interleaving
Intra-burst interleaving is achieved by distributing the interleaved sub-blocks
over a number of bursts.
4.2.5 Encryption/Decryption
Encryption and Decryption are optional security functions that protect the
confidentiality of messages sent over the Air Interface. When Encryption
is used, the baseband functions carry out Encryption and Decryption on
traffic channels and dedicated control channels. Common channels must be
transmitted without encryption. This is because a cipher key is dedicated to
each individual call, and this key is not known to the Mobile Station until the
initial stages of call establishment are underway.
The following three processes are used for message confidentiality.
Encryption
Encryption is implemented using the confidential A5 algorithm, specified in

accordance with GSM rec. 03.20.
Three versions of this algorithm are used:
A5/1 which performs the most secure level of encryption
A5/2 which performs a level of encryption effective for normal use, but
which is less secure than that provided by A5/1
A5/0 which performs no encryption.
The implementation of the A5 algorithm is not dependent on the BTS
hardware. The A5/1 and A5/2 (cipher key) must be downloaded to the BTS,
from the BSC, before Encryption can start.
Decryption
Decryption uses the same algorithms as those used for Encryption. Decryption
is the reverse of Encryption.
TDMA Multiframe
Building
On the downlink, the encrypted bursts are finally multiplexed to build the TDMA
multiframes, before being sent to the RF telecommunications functions.
59 / 234
4.2.6 Demodulation
Demodulation recovers the baseband data contained in the radio signal
received in the uplink direction.
The RF telecommunication functions remove the RF carrier and produce
complex samples of the digital baseband. These samples are sent to the
baseband functions, where the GMSK demodulation is performed. At this
stage, the Demodulation function applies frequency correction to compensate
for frequency drift at the Mobile Station.
In addition a number of measurements are made on the uplink signal to provide
information required by the BSC for control purposes.
Signal-to-Noise Ratio
SNR measurements are made by the Demodulation function as part of the

signal processing. The resulting values are also used by the BSC to optimize
channel allocation.
Adaptive Frame
Alignment
TOA estimation measures the propagation delay over the Air Interface, as
Mobile Station to BTS distances change.
Using TOA measurements, the BTS calculates timing advance changes for
each Mobile Station. This is done by measuring the time offset between its
own burst transmission and the reception of Mobile Station bursts.
The timing advance data is sent on the SACCH to the Mobile Station. The
Mobile Station then advances its burst transmissions relative to the bursts
it receives from the BTS. Two such updates per second enable the Mobile
Station to keep its burst transmissions synchronized to the allotted time slots.
The overall process is known as Adaptive Frame Alignment.
When a Mobile Station is switched on or otherwise enters a service area, the
TOA is initially estimated using the Random Access burst. The BTS measures
the position of the received burst within the Burst Period and its Guard Period.
Soft Decision Bits
60 / 234
The Viterbi algorithm is used in the Decoder function. It requires the

information produced by Demodulation of a burst to be supplied in a format
known as soft decision bits. The demodulated bursts are therefore output
in the form of soft decision samples.
4.3 Call Management Functions

The baseband telecommunications functions participate in several Call
Management functions, described in the following sections.
4.3.1 Radio Link Recovery

The Radio Channel Management function detects the need for radio link
recovery when communication with a Mobile Station is lost. Radio link recovery
consists of maximizing the transmitter power at the BTS and Mobile Station.
If the recovery procedure fails, this is recognized by the BSC as a radio link
failure. The situation can then be handled by the network in an orderly manner.
This mechanism is based on signal strength values and quality parameters
provided by the baseband telecommunication functions.
4.3.2 Radio Resource Indication

The quality of a radio channel can change very quickly, due to the movement of
Mobile Stations. For this reason, the best channel currently available cannot be
predicted for more than a few seconds. To ensure that channels are allocated
in the most effective manner at a given moment, idle channels are continuously
monitored by the BTS. The measurements on which this mechanism is based
are performed by the baseband telecommunication functions.
4.3.3 Paging
The Paging function is used to find a Mobile Station. For this purpose the
BSC first determines the Paging Group to be used. This is based on the
International Mobile Subscriber Identity, or Temporary Mobile Subscriber
Identity, of the Mobile Station to be paged. The Paging Group value is then
sent to the BTS with a paging request message.
The baseband telecommunication functions do this by using the Paging Group
information to construct PCH messages.
61 / 234
4.3.4 Discontinuous Transmission

DTX is an option in accordance with GSM rec. 06.31. It is designed to
reduce co-channel interference between cells, and to cut power consumption
in Mobile Stations.
On the downlink TCH, a VAD algorithm in the TC analyzes input speech. If
more than four successive speech frames are detected without speech activity,
the TC can perform DTX.
If DTX is performed, it is controlled by the BSC. During DTX, an SID frame is
sent to the Mobile Station at the start of every speech inactivity period. Further
SID frames are sent at 480 ms intervals thereafter, for as long as the inactivity
period lasts. This compares with 20 ms intervals between normal speech
frames, so the number of bursts transmitted is greatly reduced. This pattern
is modified by constraints to ensure that DTX does not prevent valid signal
measurements being made in the BTS.
During a silent period the frame level functions encode dummy bursts for the
transmitter. This stops TCH radio transmission when there is no useful traffic to
transmit. However, DTX is overridden when FACCH data needs to be sent.
DTX is not applied to TCHs transmitted by the BCCH transmitter, since GSM
protocol requires continuous BCCH transmission. In this case, a dummy burst
is transmitted when the FDMA time slot is on the BCCH frequency. The BTS
applies the transmitter power value of the BCCH carrier to the transmitted
dummy burst.
The SID frames tell the Mobile Station when to listen to the TCH. They also
enable the Mobile Station to generate comfort noise during the silence periods.
This prevents the caller from thinking that the call has been disconnected.
DTX can be used on both uplink and downlink. If it is used on the uplink, the
Channel Decoder distinguishes between speech frames and SIDs on the
basis of the frame content. The Channel Decoder uses SID flags to control
the speech decoding.
4.3.5 Discontinuous Reception

The BTS supports the GSM option of DRX by Mobile Stations. When DRX
is used, the downlink CCCH is divided into a number of PCH sub-channels.
This allows all paging messages for a particular Mobile Station to be sent on
the same sub-channel. Each Mobile Station can determine this channel from
information sent on the CCCH. When idle, the Mobile Station needs listen
only to the relevant sub-channel. Since this contains only a small sub-set of
all the PCH frames, the technique results in a significant saving in power
consumption by the Mobile Station.
When DRX is used, the telecommunication functions continue to receive signal
strength measurements from Mobile Stations. These measurements are made
by the Mobile Station during the associated paging block duration.
62 / 234
4.3.6 Quality Measurement

To exercise Power Control and Handover functions, the BSC uses information
about the signal quality and RSSI for all channels. Both uplink and downlink
channels are monitored for this purpose. This function is supported by the BTS
in accordance with GSM rec. 05.08.
For a given channel, the RF functions measure the received signal strength
on the uplink. These are sent to the baseband functions every TDMA frame.
Here, the Decoder constructs the received signal quality for every block,
then averages the values. These values are used by the Power Control and
Handover functions.
4.3.7 Power Control

The RF power radiated by Mobile Stations and the BTS is controlled by the
BSC. This minimizes co-channel interference and conserves battery power
at the Mobile Station. On the uplink, the BTS measures the signal strength
and signal quality received from the Mobile Station as previously described.
For the downlink, the BTS acquires the equivalent values from the Mobile
Station via the SACCH.
These measurements are processed by the BSC, which sends power control
values to the BTS via Layer 3. The Channel Encoding function routes this data
to the RF telecommunications functions or Mobile Station, as relevant.
63 / 234
4.4 Supervisory and Control Functions

The Supervisory and Control functions are described in the following sections.
4.4.1 Clock Distribution

The Clock Distribution function distributes all clocks required by the baseband
functions. Clocks are derived from the Timing Generation function.
4.4.2 Protocol Management

In order to carry out its telecommunications and O&M functions, the baseband
telecommunications function manages protocols corresponding to OSI
Layers 1, 2 and 3. For each layer it is possible to find more than one protocol
- for example, there are three Layer 2 protocols: LAPD, LAPDm, and the
BTS internal links.
4.4.3 Radio Channel Management

Radio Channel Management is based on decisions made by the BSC. These
decisions are implemented within the BTS, which effectively reacts to BSC
commands. This arrangement requires a constant exchange of signalling
messages between the BSC and the Mobile Station. These messages are
handled using the GSM rec. 08.58 and 04.08 protocols.
Within this mechanism, the baseband function is responsible for routing
transparent messages, and for processing non-transparent messages before
routing them. These activities are handled by the baseband Layer 3 functions,
which play a key role in managing the Air Interface and its channels.
The measurements are preprocessed in the BTS and sent via Layer 3 to the
BSC. Radio channels can then be re-allocated by the BSC depending on the
current measurement results. Radio Channel Management is required for
both dedicated channels and CCCH.
In GPRS systems, channel management is carried out from the MFS via
the master PDCH.
64 / 234
4.4.4 Transcoder Time Alignment

The multiframe organization of TCHs dictates that speech blocks for the Air
Interface can start only at predefined points in time. Since each speech block
corresponds to 20 ms of speech, an asynchronous entity in the downlink
speech path can lead to a delay of up to 20 ms.
To avoid this difficulty, the TC is told the precise points in time to send TRAU
frames to the BTS.
This function, known as Transcoder Time Alignment, is implemented by the
telecommunication functions in accordance with GSM recommendations:
08.60 for TCH/F
08.61 for TCH/H.
The baseband functions measure the shift between the ideal point in time to
receive a frame from the TC, and the actual time of arrival. This involves
measuring the delay between reception of the TRAU frames and the encoding
of a speech block. The resulting value is sent by the BTS to the TC, which
adjusts its schedule accordingly.
For each data stream, the baseband functions provide control and baseband
data processing for the eight time slots that comprise one TDMA frame.
65 / 234
66 / 234
5 Telecommunication Functions - RF
This chapter describes the RF telecommunication functions. Following a brief
introduction, the chapter discusses RF functions under the headings:
RF processing
Control functions
Coupling functions.
67 / 234
5.1 Introduction to Telecommunication Functions - RF

The RF telecommunication functions convert downlink databursts into a
modulated RF carrier, for transmission over the Air Interface.
On the uplink, the functions receive incoming GSM radio signals from the
Air Interface. They then convert them into samples suitable for baseband
processing.
The following figure shows the RF functions for BTSs with frequency hopping
using programmable carrier frequencies.
RF Functions
Downlink Direction
Power
Coupling
and Detection
Power
Amplification
Up
conversion
Baseband
Functions
Baseband
Downlink
Processing
GMSK
Modulation
Frequency
Generator
Frequency
Hopping
Control
Coupling
Frequency
Generator
Down
conversion
Signal
Amplification
AD
Conversion
Digital
Preprocessing
Baseband
Uplink
Processing
Uplink Direction
* Antenna Diversity some uplink functions are duplicated for Antenna Diversity.
Figure 15: RF Telecommunication Functions

Frequency hopping is achieved by controlling the transmitter and receiver
frequency generators. The generators are programmed to a different frequency
for successive TCH time slots. Refer to Frequency Hopping (Section 5.2.2)
for more information.
68 / 234
5.2 RF Processing
RF processing consists of the following functions.
5.2.1 RF Carrier Generation

A 9100 BTS can be configured for up to eight discrete RF carriers for an
omnidirectional configuration and for up to twelve discrete RF carriers in case
of a sectorized configuration. Each carrier supports up to eight full-rate or 16
half-rate GSM channels. A 9110 Micro BTS can be configured for up to six
discrete RF carriers and a 9110 Micro BTS-E can be configured for up to twelve
discrete RF carriers for a sectorized configuration.
Each RF carrier is generated:
At constant frequency - each transmitter sends successive time slots on a
constant carrier frequency. This is produced by a frequency synthesizer.
At a programmed frequency - the synthesizer is reprogrammed for each
time slot.
In both cases, the BCCH is transmitted at a constant frequency. The frequency
synthesizer is reprogrammed at a constant frequency for successive BCCH
time slots.
5.2.2 Frequency Hopping

Frequency hopping is the optional process of transmitting successive time slots
of an GSM channel, on different carrier frequencies. The carrier frequency is
specified by the ARFCN, under control of the FHA.
Frequency hopping reduces the effects of multipath distortion and co-channel
interference between cells. It is applied only to the TCHs and SDCCH, since
the BCCH must be transmitted on a constant carrier frequency.
Frequency Hopping is performed on traffic transmitted over the Air Interface.
The process is described for the downlink and uplink directions.
5.2.2.1 Downlink Direction

When frequency hopping is in use, traffic that is to be transmitted to Mobile
Stations is frequency hopped. The BTS transmitters are tuned by frequency
synthesizers which are programmed to produce different frequencies. When
frequency hopping is not used, the synthesizers are set to a constant frequency.
The frequency synthesizer operation determines the way in which the BTS
processes the traffic to be transmitted:
Programmable frequency synthesizer
Frequency hopping is achieved by programming the synthesizers to a
different frequency for successive TCH time slots. The BCCH synthesizer
is programmed only once, during power up or following a change in the
ARFCN.
Frequency synthesizer set to a constant frequency
When frequency hopping is switched off, the TCH frequency synthesizers
are repeatedly re-programmed for the same ARFCN. The BCCH synthesizer
is programmed only once, during power up or following a change in the
ARFCN.
69 / 234
5.2.2.2 Uplink Direction

When frequency hopping is in use, traffic from Mobile Stations is frequency
hopped. The BTS receivers are tuned by frequency synthesizers which are
programmed to produce different frequencies. When frequency hopping is not
used, the synthesizers are set to a constant frequency.
The frequency synthesizer operation determines the way in which the BTS
processes the received TCH:
Programmable frequency synthesizer
A receiver with a programmable frequency synthesizer is retuned, under
control of the FHA, for each time slot. Each receiver therefore preserves the
original TDMA frame content, and with it the cyclic data that comprises the
associated TCHs. This type of receiver provides a contiguous datastream,
which can be passed directly to the telecommunications baseband functions.
Frequency synthesizer set to a constant frequency
A receiver tuned by a frequency synthesizer set to produce a constant
frequency, receives uplink signals on a single frequency. Successive,
frequency hopped, bursts sent by a single Mobile Station are therefore
received by different receivers. To enable the telecommunications baseband
functions to process the uplink TCHs, the received bursts are switched,
under control of the FHA, to remotely reassemble the original TDMA frames.
5.2.3 Modulation and Up-Conversion

Modulation and up-conversion are described in the following sections.
5.2.3.1 Modulation
Downlink data is received by the RF telecommunication functions in the form
of encoded bursts. Both the GMSK and 8-PSK modulation functions convert
the downlink data into two baseband signals I and Q. The data is differentially
encoded, and digital values are generated from a sine and cosine look-up table.
The digital values are converted to analog signals, amplified and filtered, to
form the baseband signals I and Q.
The I and Q signals are used to modulate the RF carrier. The downlink signal is
then ready for amplification.
The figure below shows the I and Q baseband signals for 8-PSK.
70 / 234
5.2.3.2 Coding Schema
EGPRS
GPRS
Note
Scheme
Modulation
Code rate
Maximum rate
[kbps]
MCS-9
8-PSK
59.2
MCS-8
8-PSK
0.92
54.4
MCS-7
8-PSK
0.76
44.8
MCS-6
8-PSK
0.49
29.6
MCS-5
8-PSK
0.37
22.4
MCS-4
GMSK
17.6
MCS-3
GMSK
0.8
14.8
MCS-2
GMSK
0.66
11.2
MCS-1
GMSK
0.53
8.8
CS-4
GMSK
20
CS-3
GMSK
0.75
14.4
CS-2
GMSK
0.66
12
CS-1
GMSK
0.5
: The maximum data rate given in the above table refers to the RLC payload (=
the throughput offered to the Logical Link Control (LLC) layer). The RLC/MAC
header, Block Check Sequence (BCS), Tail bit etc. are already subtracted.
The choice of the modulation and coding scheme is based on measurements of

the Bit Error Probability (BEP). The highest packet data throughput that can
be achieved for Carrier-to-Interference Ratio (CIR) values is in excess of 20
dB, which corresponds to a clear radio path. (GSM radio network planning
is done with the objective of meeting CIR values at least equal to 9 dB.)
Numerical simulations indicate that, on average, EGPRS would enable a data
throughput twice as large as what can be obtained with GPRS (with all four
coding schema), that is roughly 35 kbit/s/time slot.
71 / 234
5.2.4 Power Amplification and Power Control

Power amplification and power control for GMSK and 8-PSK are described
below.
5.2.4.1 GMSK Output Power

Power Amplification boosts the RF signal in several stages to the required
output power. Output power for each transmitter is constantly monitored,
and set to a level specified for each time slot. The power level is controlled
by the Power Step parameter, which is included in the downlink signalling
from the BSC.
The TCH carrier output power can vary dynamically for each burst, and is
ramped up or down as necessary. The BCCH carrier output power remains
at a constant level, but is nevertheless controlled by the Power Step for each
discrete time slot.
Power Amplification is temperature limited. If the temperature of the RF power
stage exceeds a pre-defined limit, the RF output power is switched OFF and an
alarm is sent to the O&M function.
The Power Step parameter also controls the Power Amplifier switches. These
enable/disable the PA output power for the TCH and BCCH carriers.
During normal operation, each carrier is enabled for the active period of each
time slot. This leaves a guard period between time slots, during which no
carrier is transmitted.
During startup, the TCH and BCCH carriers can be suppressed for individual
time slots. The same suppression is applied while alarms are in force, or
during unused time slots.
TRE output
power
TRE1: Max 8PSK

output power
Transmission
GMSK
output power
of the sector
8PSK delta power

for TRX2
TRE2: Max 8PSK

output power
Figure 16: GMSK Output Power
72 / 234
5.2.4.2 8-PSK Output Power

The nominal output power of the transmitters is specified as the average power
during the active part of the burst. In GMSK, the average power is identical to
the peak power (ignoring imperfections like overshoots and ripples). In 8-PSK,
even though the peak power is the same as in GMSK, the average power is
lower than the GMSK power. This is sometimes called power back off. This
power back off is theoretically about 4.8 dB assuming the same peak power
as for GMSK and a random bit pattern. In reality, transmitters are often not
limited by the ability to deliver instant power peaks, but by thermal constraints.
In that case, it is therefore possible to increase the peak power for 8-PSK
without violating the thermal limits.
For a given TRE, the maximum output power is lower in 8-PSK than in GMSK
because of the 8-PSK modulation envelope which requires a quasi-linear
amplification. The TRE transmit power in 8-PSK cannot exceed the GMSK
transmit power in the sector and in the band. In 8-PSK, the only levelling which
applies aligns, if necessary, the 8-PSK transmit power to the GMSK transmit
power in the sector and in the band. In the figure below, an attenuation is
applied to the 8-PSK output power of TRE1 in order to align it with the GMSK
output power of the sector. No attenuation is necessary for the output power
of TRE2.
TRE output
power
TRE1: Max 8PSK

output power
Transmission
GMSK
output power
of the sector
TRE2: Max 8PSK

output power
Figure 17: 8-PSK Output Power
73 / 234
5.2.4.3 Determination of 8-PSK Delta Power

The 8-PSK delta power informs the system of the difference between the
GMSK output power of the sector and the 8-PSK output power that can be
reached by a given TRE. It takes into account all the attenuations except
the static power reduction.
The figure below shows the 8-PSK delta power for TRE2. For TRE1, the
8-PSK delta power is 0.
TRE output
power
TRE1: Max 8PSK

output power
Transmission
GMSK
output power
of the sector
8PSK delta power

for TRX2
TRE2: Max 8PSK

output power
Figure 18: 8-PSK Delta Power
5.2.5 Channel Selection and Conversion

Incoming signals are received via the antennae and coupling functions. For the
9100 BTS, the receivers are always configured for diversity reception.
Each receiver is tuned by a programmable frequency synthesizer. The
synthesizer is programmable, re-tuning the receiver to the channel frequency
for each discrete time slot.
The incoming GMSK-modulated RF signal is filtered to suppress interference
from outside the selected frequency. The RF signal is then mixed with the
oscillator/synthesizer signal to down-convert the required signal into an
intermediate frequency. The channel number is selected by an O&M command
which is sent to the control function of the transmitter.
A 9100 BTS can be configured with up to eight receivers in an omni-directional
configuration or 12 receivers in a sectorized configuration. Using the Twin
TRE 16 receivers are supported in an omni-directional configuration or 24 in
receivers in a sectorized configuration. Each receiver can process up to eight
full-rate or 16 half-rate GSM channels.
A 9110 Micro BTS can be configured with up to a maximum of 6 receivers and
a 9110 Micro BTS-E can be configured with up to a maximum of 12 receivers in
a sectorized configuration. Each receiver can process up to eight full-rate or
16 half-rate GSM channels.
5.2.6 Signal Amplification

The receiver filters and amplifies the intermediate frequency signal. This signal
is then split into two paths, high and low gain. Using a second local oscillator
signal, I/Q demodulators down-convert the high and low gain intermediate
74 / 234
frequency signals to baseband I and Q components. These are ready for

A-D conversion.
5.2.7 A-D Conversion

The receiver A-D converts the high and low gain I and Q signals into a digital
representation. Either the high gain or the low gain path is selected, depending
on signal strength. This increases the dynamic range of the receiver.
5.2.8 Digital Pre-processing

The receiver carries out the following Digital Pre-processing procedures:
DC offset correction to negate the influence of DC variations in the signal
Power calculation to select one of the two signal paths for further processing;
this depends on the power of the received signal
Frequency translation which supports the demodulation process.
The data is then output via the RFI to the telecommunications baseband
functions for demodulation.
75 / 234
5.3 Control Functions

The principal control functions are described in the following table.
Function
Description
RF Hardware
Status
The status of the RF hardware is dynamically

configured to meet the current requirements of the
BSS.
The control functions therefore manage the RF
hardware according to the changing requirements
during:
Power-up and initialization
Normal operation
Reconfiguration
Failure conditions.
Frequency Hopping
Control
Control of the frequency hopping function is performed

for hardware configurations that implement frequency
hopping as part of the RF functions.
Clock Management
Clock selection and supervision is performed for

hardware configurations that provide redundant clock
buses.
Frequency
Synthesizer
Programming
The frequency synthesizers in the BTS are

programmed under control of the BSC. This function
is implemented by extracting control signals from the
datastream provided by the BSC.
Alarm Processing
Alarms originating in the RF functions are supervised,

collected and passed to the O&M functions.
High/Low Gain
Selection
Selection of the high or low gain path on the uplink is

determined by measuring the received signal power on
the high and low gain paths. If the signal strength for
the low gain path is high enough, then it is selected.
Otherwise the high gain path is used.
Table 8: RF Control Functions
76 / 234
5.4 Coupling Functions

The BTS coupling functions interface the RF signal paths to the BTS antennae.
These functions are described in the following table.
Function
Description
Uplink Downlink
Isolating
The isolating function prevents the generation of additional intermodulation

products by improving the isolation between the transmitters.
Combining The combining function sums the RF signals from a pair of BTS
transmitters, to enable them to share a single antenna. Several pairs
of transmitters can be used in a BTS configurations, each with their
associated antenna.
Duplexing
Duplexing enables the uplink and downlink to share a single antenna.

Duplexing performs the following functions that are common to the
downlink and uplink signal paths:
Suppresses unwanted emissions outside the downlink band,
especially emissions which would fall into the uplink band
Ensures that isolation between the transmitter and receiver in the
duplexing function prevents the downlink signals from blocking the
receiver
Ensures that wide-band noise and spurious emissions present in the
downlink carrier do not cause interference in the receive band.
On the uplink, duplexing also performs the following additional functions:
Rejects the receivers image frequency
Ensures a high degree of isolation from the transmitters.
Duplexing does not deal with the third-order intermodulation components
of the transmitter. Channel frequency allocation must therefore
ensure that these intermodulation components do not fall in a used
receiver channel.
77 / 234
Function
Description
Uplink Downlink
Power
Coupling
and
Detection
For the 9100 BTS only, the Power Coupling and Detection function
protects the 9100 BTS against the effects of reflected RF power by
measuring the reflected power level. For example, if the RF coupling to
the antenna is interrupted, the power measurement exceeds a specified
threshold. The function immediately removes the RF power by switching
off the transmitters.
The power measurement is performed for power steps 0 to 9 only. This is

because of the limited isolation between the transmission and reception
parts of the AN. The measurement is performed for all bursts in this power
range and if more than 25% of measurements exceed the threshold,
then an alarm is raised.
RFE
The Receiver Front-End function provides low-noise pre-amplification

of the received signal, ahead of the main receiver function. The RFE
function delivers the uplink signal to the BTS receivers via a Power
Splitting function.
Table 9: RF Coupling Functions
78 / 234
6 O&M and Support Functions

This chapter describes the:
O&M functions
Support functions.
79 / 234
6.1 Introduction to O&M and Support Functions

The O&M functions monitor and control the operation of the BTS. These
responsibilities are shared with the BSC. The support functions control
non-telecommunications features.
6.2 O&M Functions

The O&M functions are described in the following sections.
6.2.1 O&M Connections

The O&M functions exchange information and command messages with
different parts of the BTS, and with the BSC. This allows the O&M functions to
monitor and control the operation of the BTS. The different types of connection
used for this purpose are grouped into internal and external connections.
6.2.1.1 Internal Connections

Internally the O&M functions are connected from the OMU to the
TRANS/CLOCK, the TRE or MTRE, and to the ANX modules. This is achieved
by the BSII which provides high-speed transfer of downloadable software,
operational parameters and alarms to processor controlled functions. All of the
processors can be loaded or configured via the BSII.
Additionally, the non-intelligent BTS functions, e.g., power supplies, fans, etc.,
are connected to the O&M functions via the BCB.
All BTS functional modules are identified by location within the BTS cabinet
(9100 BTS) or in terms of an inbox and a box address (9110 Micro BTS/9110-E
Micro BTS). This ADR information is carried on either the BSII or the BCB
depending on the presence of a processor on the module.
6.2.1.2 External Connections

The following interfaces provide the external connections shown in the following
table.
Interface
Description
Abis
The O&M function is connected to the BSC via the LAPD

OML logical interface. This is physically implemented on
the BSII. It is multiplexed onto the Abis Interface by the
BTS transmission functions.
MMI
A local MMI is provided for operator control of the BTS.

This control is in the form of local maintenance and
control operations performed by the O&M functions. The
BTS sends a message to the BSC to inform it of the
operators actions.
XBCB (9100
BTS only)
The 9100 BTS can control or supervise external events

using the XBCB Interface. This interface can also be used
by an external source to perform RI on the BTS, but only
if the BTS is not powered up and only at factory level.
Table 10: O&M External Connections - Interfaces
80 / 234
The O&M functions are connected to the Abis Interfaces via the SUM to the
Connection Area Interface (SUMCAI) (9100 BTS) or the MSUM Connection
Box Interface (MSCOI) (9110 Micro BTS/9110-E Micro BTS). This interface is
used to transfer all external digital interfaces from the 9100 BTS SUM to the
9100 BTS Connection Area (CA) or from the 9110 Micro BTS/9110-E Micro
BTS MSUM to the 9110 Micro BTS/9110-E Micro BTS COBO.
6.2.2 O&M Processing

O&M processing uses three categories of functions, which are described below.
6.2.2.1 Configuration Management

The Configuration Management functions handle a number of tasks as shown
Function
Description
Central Command
Control
GSM function-level configuration commands from the

BSC or operator are translated to low-level commands
for the relevant BTS modules.
Configuration/
Initialization
Software initially downloaded from the BSC to the

O&M functions is subsequently downloaded to the
other BTS modules. The O&M functions configure
each BTS module, and report start-up test results to
the BSC.
File Handling
Up to two versions of the downloaded software can

be stored in memory at any one time. This allows
the software to be downloaded without service
interruption.
Database
A database is maintained for use by other O&M

functions and the BSC. It contains complete details
of the BTS including configuration data, alarm and
status information.
Remote Inventory
and RF Cabling
Detection
These O&M functions can interrogate the hardware to

determine which modules are installed and how they
are connected.
Live Insertion and

Removal of Modules
(9100 BTS only)
All modules can be inserted or removed from the 9100

BTS subracks while power is connected. An alarm is
sent to the O&M functions when a module is removed.
Hardware
Additional modules can be added to the existing
Extension/Reduction configuration and then the BTS is reconfigured under
BSC control. Similarly, modules can be removed and
the system reconfigured.
Table 11: O&M Configuration Management Function
81 / 234
6.2.2.2 Fault Management

The Fault Management functions perform a range of tasks as shown in the
following table.
Function
Description
Alarm Detection and

Correlation
Detects and filters alarms to prevent the generation of

multiple fault reports from a single source of failure.
Alarm Reporting
Forwards alarms to the BSC for processing.
Alarm Translation
Translates alarms to a GSM function-level format,

independent of hardware and software versions.
Module Power
Supply Control
Module power on/off is controlled by the O&M

functions via the BCB Interface.
Table 12: O&M Fault Management Tasks
6.2.2.3 External Alarm Handling

External Alarm Connections provide a mechanical/electrical interface between
the Dedicated Alarm and Control Handling functions, and the BTS external
alarm sources. These external alarm sources include the cabinet door switch,
smoke detector, etc.
6.2.3 Station Unit Sharing

The 9100 BTS can share certain functions between different sectors (i.e., cells)
using Station Unit Sharing. The O&M, Transmission and Clock functions can be
shared between sectors that have unique Telecommunications functions.
6.2.4 Recovery Strategy

In addition to monitoring and reporting the status of the BTS, the O&M functions
can implement recovery actions. The recovery strategy varies according
to the type of BTS.
For configurations that include redundant hardware, recovery actions can
include:
Hardware reconfiguration
Selective hardware shutdown
Hardware reset
Software reload and restart.
For BTSs designed as a simple unit, without redundancy, recovery actions are
limited to restart and reset attempts.
82 / 234
6.3 Support Functions

The Support functions are described in the following sections.
Support Function
9100
Indoor
9110
Micro
BTS/
9110-E
9100
Micro
Outdoor BTS
HEAT
Internal Power Supplies
Internal Temperature Control
External Battery Cabinet
MPS/MPS2
Timing Functions
Table 13: Mapping of Support Functions to BTS Variants
6.3.1 HEAT
For the 9100 BTS outdoor and the 9110 Micro BTS/9110-E Micro BTS, the
digital boards must not be operated below -5 C.
6.3.1.1 9110 Micro BTS/9110-E Micro BTS

To combat low temperature conditions, heating elements (resistors) are fitted to
the MPS/MPS2 module. In addition to this, two HEAT modules are also fitted;
one to each digital module. The +26 V supply that is normally used to feed the
power amplifiers is used to warm up the BTS when its internal temperature is in
the range -33 C through 0 C. Once the unit reaches 0 C the power amplifier
becomes operational. As the temperature increases from 0 C to 15 C, the
amount of heating power is reduced linearly from 80 W to 0 W.
6.3.1.2 9100 BTS Outdoor

Heating is provided by electrical air heaters if the internal air temperature is
below 10 C. They are fitted to the floor or on the side wall of each compartment
(except MBO1) in the 9100 BTS outdoor. In the MBO1/MBO1DC cabinet, the
HEAT2/HEATDC module is installed underneath the HEX4 module at the back
of the front door. The HEAT2 version is AC-mains powered, the HEATDC is
DC-voltage powered.
6.3.2 Internal Power Supplies

9100 BTS configurations intended for outdoor use are equipped with internal
power supplies. These convert the mains supply voltage to the nominal 48 VDC
required by individual 9100 BTS modules.
The 9100 BTS MBO can be powered by AC mains or DC supply voltage.
Configurations used indoors are supplied in two variants for either AC or DC
supply voltages. The AC supply variant is equipped with internal power supplies
83 / 234
that are similar to the 9100 BTS outdoor configurations. The DC supply variant
contains DC filters to condition the DC input voltage supply.
For both variants, each module contains a DC/DC converter to produce the
required voltage levels needed by the individual module. Module power on/off
is controlled by the O&M functions via the BCB Interface.
The following additional features are provided.
84 / 234
6.3.2.1 Output Monitoring

All power supply outputs are monitored for output voltage. If an undervoltage
condition is detected, an alarm is raised and sent to the O&M functions.
6.3.2.2 External Load

External loads like pylon lightning, transmission equipment etc., can be
supplied by the internal 48 VDC power supplies of the indoor and outdoor BTS
AC variants. In case of an indoor BTS DC configuration, external loads can be
connected via the BTS to the external BTS DC power supply.
6.3.2.3 Battery Backup

The AC supply variants use optional backup battery to maintain operation in the
event of mains supply failures. Backup batteries are permanently connected
in-circuit. They are disconnected only in case of deep discharge.
After an AC supply failure, TREs can be selectively shut down to extend the
time the BTS operates on battery power. At least one TRE per cell remains
in operation. The TRE that supports the BCCH, SDDCH, and some TCHs
will always be kept operational. Only the TREs exclusively carrying TCHs
are shut down.
When the AC supply fails, a timer starts. After a pre-set period the TCH-only
TREs are shut down. When the AC power supply is restored, another 10
second timer starts. If the power supply is stable and within its operating
tolerances at the end of this period, the TREs are restored to operation.
The pre-set value of the first timer, default 120 seconds, can be read using
the RI.
6.3.3 Internal Temperature Control

All 9100 BTSs are equipped with an internal temperature control function. For
the 9100 BTS, this consists of heating elements (outdoor cabinets only) and
cooling fans, controlled by temperature sensors and supervisory equipment.
Depending on the hardware configuration, the Temperature Control function
can delay power up of the main equipment at switch on. Power is applied when
the internal temperature has been raised or lowered to within specified limits.
The Temperature Control function monitors the internal temperature during
9100 BTS operation. It switches the fans or heaters on and off, to maintain the
specified temperature range.
Note that the heaters and heat exchangers or direct air cooling systems
(HEAT2 and HEX2, HEX3, HEX4, HEX5, HEX8 or HEX9 or DAC 8/DAC9
respectively) used in outdoor configurations are controlled independently
of the BTS OMU functions.
85 / 234
6.3.4 External Battery Cabinets

External battery cabinets are available for indoor and outdoor installation.
Cabinets are used to house a large backup battery to maintain operation
in the event of mains supply failures. In this case it is not allowed to use a
BTS configuration with a parallel internal backup battery. Backup batteries
are permanently connected in-circuit; they are disconnected only in case
of deep discharge.
6.3.4.1 Indoor Battery Cabinet

As required, up to three battery units (48 VDC) can be installed inside the
indoor battery cabinet. These battery units can be connected separately to
supply different BTSs or they can be connected in parallel to supply one BTS.
If battery units are used for different BTSs, each branch can be switched off
separately. If battery units are used for one BTS, all branches can be switched
off commonly.
Each battery unit has a temperature sensor which monitors the battery
temperature. The output of each sensor is connected to separate RIBAT boards
which are installed inside the battery cabinet. RIBAT boards are powered by the
BTS(s). They prepare the sensor information used by the SUMA/SUMX (inside
the BTS) to regulate the charging voltage and thus preventing overheating.
6.3.4.2 Outdoor Battery Cabinet

As required, up to three battery units (48 VDC) can be installed inside the
outdoor battery cabinet. These battery units are connected in parallel to
supply one BTS.
Each branch can be switched off separately. Additionally all branches can be
switched off commonly (main circuit breaker).
Each battery unit has a temperature sensor which monitors the battery
temperature. The output of each sensor is connected to separate RIBAT boards
which are installed inside the battery cabinet. RIBAT boards are powered by
the BTS(s). They prepare the sensor information used by the SUMA/SUMX
(inside BTS) to regulate the charging voltage and thus preventing overheating.
The battery branches are fitted with venting tubes. The venting tubes discharge
the gasses produced during battery charging to the external environment.
The external outdoor battery cabinet has an air conditioner with an integrated
heater. The air conditioner maintains the correct air environment inside the
cabinet. The airflow inside the cabinet is isolated from the outside environment.
The heater switches on automatically if the internal air temperature falls below
a pre-defined temperature (+10 C). An alarm is raised if the air conditioner or
heater fails. Both air conditioner and heater are powered by 230 VAC power.
An optical smoke detector is installed in order to raise an alarm in case of
smoke inside the cabinet. The smoke detector is powered by the BTS.
The cabinet door presses an electronic switch which raises an alarm, if the door
is open. For maintenance and service, the open door alarm can be switched off.
For maintenance and service, a service light and integral 230 VAC power
socket is available.
86 / 234
6.3.5 MPS / MPS2

The MPS for the BTS 9110 is an AC/DC converter and provides the following
voltages:
+26 V
+9 V
+5.1 V
+3.3 V
-9 V.
If the input voltage level falls below the stated minimum (170 V), the MPS
automatically switches off. When the voltage is restored at, or above, the
minimum level, the MPS switches back on again automatically.
The MPS2 is the AC/DC converter for the BTS 9110-E and provides the
following voltages:
+26.1 V
+9.3 V
+5.4 V
-5.1 V
+3.45 V
If the input voltage level falls below the minimum (150 V), the MPS2
automatically switches off. When the voltage is restored at 160 V, the MPS2
switches back on again automatically (hysteresis).
87 / 234
6.3.6 Timing Functions

The Timing functions are described in the following sections.
6.3.6.1 Master Frequency Generation

All BTS clocks are derived from a 13 MHz master reference frequency. The
master frequency is generated by the master frequency generator. This is a
high stability oscillator.
The BTS can operate in master mode or slave mode. In the master mode,
the BTS uses the internal 13 MHz master frequency. This clock can be either
free-running, or synchronized to the PCM clock on the Abis Interface. If the
free-running mode is used, the BTS internal clock requires yearly calibration.
In the slave mode, the BTS is synchronized as a slave to another BTSs master
clock. The synchronization is performed using the XCLK Interface.
Additionally, an external clock synchronization signal for the BTS can be
provided by the XGPS option. This signal can be used to replace the
PCM synchronization from the Abis Interface. The GPS option is a future
enhancement that is not currently available.
Because all 9100 BTS configurations can be run in master or slave mode, the
XCLK Interface can be used for either output or input of the 13 MHz master
frequency.
6.3.6.2 Timing Signal Generation

From the 13 MHz reference signal, the following slower synchronization clocks
are derived by a process of frequency division:
2.167 MHz OBCLK
216.7 Hz FCLK with Frame Number multiplexed.
6.3.6.3 Clock Distribution

The Clock Distribution function distributes the synchronization clocks to the
MTRE/TRE and AN (9100 BTS only). The two synchronization clocks are
referred to as the CLKI.
88 / 234
7 Functional Units
7 Functional Units
This chapter describes the functional units architecture of the 9100 BTS
and 9110 Micro BTS/9110-E Micro BTS. It shows how to map the functions
to functional units.
89 / 234
7 Functional Units
7.1 Introduction to Functional Units

This chapter introduces the functional units and the configurations that are
possible with these units. The functional units are the elements that physically
realize the BTS functions. The BTS functions are described in Transmission
Functions (Section 3), Telecommunication Functions - Baseband (Section
4), Telecommunication Functions - RF (Section 5) and O&M and Support
Functions (Section 6).
7.2 Functional Units Architecture

This section provides a description of the BTS functional architecture in terms
of Functional Units, Functional Block Diagram, and Interfaces for the 9100 BTS
and 9110 Micro BTS/9110-E Micro BTS.
7.2.1 9100 BTS Functional Units Architecture

The 9100 BTS contains the following functional units:
AN
CA
SUM
TRE.
The CA is not described as a separate section. It is included in the SUM
description, see Introduction to the Station Unit Module (Section 10.1).
7.2.1.1 9100 BTS Functional Block Diagram

The following figure shows the relationship between the 9100 BTS functional
units and their interfaces.
CLKI
MMI
BSII
Abis
SUM
BCB
XIO
XBCB
CA
BCB
TRE(s)
ADR
SUMCAI
XCLK
RFI
AN(s)
Air
Interface
XRF
BTS A9100
AN
: Antenna Network
CA
: Cell Allocation
SUM
: Station Unit Module
TRE
: Transmitter and Receiver Equipment
Figure 19: 9100 BTS Functional Units Breakdown
90 / 234
7 Functional Units
7.2.1.2 9100 BTS External Interfaces

The main external interfaces for the 9100 BTS functional units are described in
the following table.
Interface
Description
Abis
Provides a 2 Mbit/s link between the 9100 BTS and the BSC.
The SUM provides two Abis Interfaces to allow connection to
the BSC in ring or chain configuration.
Air
Provides the radio interface with the Mobile Station. It carries

both signalling and traffic information.
MMI
Allows the connection of the BTS Terminal used for O&M

configuration and telecommunications configuration.
XBCB
Supervises or controls external events or, can be used to

perform external RI on the 9100 BTS at factory level.
XCLK
Synchronizes the BTS 9100 to an external clock master.

Alternatively, it is used to provide a clock from the 9100 BTS
for external slave BTSs.
XIO
Provides 24 inputs and eight outputs to allow the connection

of external alarms.
XRF
Provides the link between the AN and the antennae.
Table 14: Principal 9100 BTS External Interfaces
91 / 234
7 Functional Units
7.2.1.3 9100 BTS Internal Interfaces

The main internal interfaces for the 9100 BTS functional units are described in
Interface
Description
ADR
Determines the physical location of a module in the 9100 BTS.

This location information is grouped in terms of subrack address
then slot address.
BCB
Provides a serial interface used for RI and to allow the SUM to

control the module power supplies.
BSII
Handles OML and TCH data and the appropriate RSL data
for each TRE. Internal O&M messages are also exchanged
on this bus.
CLKI
CLKI consists of two lines, the reference clock and the frame
signal which also carries the Frame Number.
RFI
Consists of three lines between the TRE and the AN; one TRE
output and two TRE inputs. Each TRE has its own RFI.
SUMCAI
Transfers all external digital interfaces from the SUM to the

BTS 9100 CA. This interface carries the XCLK, XBCB, XIO,
and Abis Interfaces.
Table 15: Principal 9100 BTS Internal Interfaces
7.2.2 BTS 9110/9110-E Functional Units Architecture

The BTS 9110/9110-E functional units are described in the following sections.
A functional block diagram is provided, as well as a list of the internal and
external interfaces used.
7.2.2.1 Functional Units for the 9110

The BTS 9110 contains the following functional units:
COBO
MAN1, MAN2
MPS
MSUM
MTRE.
92 / 234
7 Functional Units
7.2.2.2 Functional Units for the 9110-E

The BTS 9110-E contains the following functional units:
COBO (this is not the same COBO as used for the 9110)
MANM, MAND
MPS2
MSUMA
MTREDA.
7.2.2.3 Functional Block Diagram

The following figure shows the relationship between the BTS 9110/9110-E
functional units and their interfaces.
CLKI
BSII
MMI
MSCOI /
ABISCOI
Abis
MSUM/
MSUMA
BCB
MTRE /
MTREDA
ADR
Air
Interface
IPS
IAL
RFI
XIN
COBO
MAN
XGPS
XRF
XBAT
RFI
XST_RA
MTRE /
MTREDA
PCIXPS
XPS
MPS / MPS2
BTS A9110 / A9110E
COBO
: Connection Box
MAN
: Micro-BTS Antenna Network
MPS/MPS2
: Micro-BTS Power Supply
MSUM/MSUMA: Micro-BTS Station Unit Module

MTRE/MTREDA: Micro-BTS Transmitter and Receiver Equipment
Figure 20: 9110 Micro BTS/9110-E Micro BTS Functional Units Breakdown
93 / 234
7 Functional Units
7.2.2.4 9110 Micro BTS/9110-E Micro BTS External Interfaces

The external interfaces used in the 9110 Micro BTS/9110-E Micro BTS
functional units are described below.
Interface
Description
Abis
Provides a 2 Mbit/s link between the 9110 Micro

BTS/9110-E Micro BTS and the BSC. The COBO provides
two Abis Interfaces to allow connection to the BSC in a
multidrop configuration.
Air
Provides the radio interface with the Mobile Station. It

carries both signalling and traffic information.
IEB
Connects up to two 9110 Micro BTS/9110-E Micro BTS,

in slave mode, to a 9110 Micro BTS/9110-E Micro BTS in
master mode. The interface comprises three subsections.
When the BTS is used in master mode, two of these
subsections can used to connect the BTS to other BTSs
in slave mode. The third subsection is used if the BTS is
used in slave mode.
MMI
Allows the connection of the BTS Terminal used for O&M

configuration and telecommunications configuration.
OMU_TRACE
Provides an asynchronous serial interface that can be used

for fault tracing and debugging.
TRANS_TRACE Provides an asynchronous serial interface that can be used

for trace and debugging.
XBAT
Provides an asynchronous interface that is used to control

an external battery backup unit.
XGPS
Controls and supervises a GPS receiver which is used to

synchronize the 9110 Micro BTS/9110-E Micro BTS. The
interface also provides a 1 Hz or 10 MHz clock source
that can be used in conjunction with the GPS receiver or
independently.
XIN
Provides eight alarm inputs.
XRF
Provides the link between the MAN/MAN2 and the

antennae.
XST_RA
Provides two serial interfaces that are used as a control link

between the MSUM/MSUMA and Stealth Radio.
XPS
External Power Supply Interface.
Table 16: Principal 9110 Micro BTS/9110-E Micro BTS External Interfaces
94 / 234
7 Functional Units
7.2.2.5 9110 Micro BTS/9110-E Micro BTS Internal Interfaces

The internal interfaces used in the 9110 Micro BTS/9110-E Micro BTS
functional units are described below.
Interface
Description
ADR
Determines the physical location of a module in the 9110

Micro BTS/9110-E Micro BTS. This location information is
grouped in terms of an inbox and then a box address.
BCB
Provides a serial interface used for RI.
BSII
Handles OML and TCH data and the appropriate RSL

data for each MTRE. Internal O&M messages are also
exchanged on this bus. When used in a master/slave
configuration this interface provides an interconnection
between the 9110 Micro BTS or 9110-E Micro BTS entities.
CLKI
Comprises the reference clock and the frame signal. The

frame signal also carries the Frame Number.
Internal Alarm
(IAL)
Provides the LNA failure alarm.
Internal
Power Supply
Interface (IPS)
Provides the internal supply DC power and is distributed

from the MPS / MPS2.
MSCOI /
ABISCOI
Transfers all external digital interfaces from the MSUM

/ MSUMA to the COBO. This interface carries the XIN,
XGPS, XBAT, XST_RA and Abis Interfaces.
Power
Connection
Interface (PCI)
Provides the AC power input to the MPS / MPS2 and is

distributed from the COBO.
RFI
Consists of one TRE output and two TRE input lines

between the MTRE and the MAN, or two lines for the 9110
Micro BTS/9110-E Micro BTS fitted with a MAN1/MANM
and no antenna diversity. Each MTRE has its own RFI.
Table 17: Principal 9110 Micro BTS/9110-E Micro BTS Internal Interfaces
95 / 234
7 Functional Units
7.3 Mapping of Functions to Functional Units

The following figure shows the relationship between the functions and the
functional units.
There are two possible mappings, direct and indirect:
Direct mapping - some of the functions can be mapped directly to functional
units.
Indirect mapping - functions must first be mapped to functional entities. This
is because, in some cases, a single function can be split between more
than one functional entity. These functional entities can then be mapped to
the functional units.
Example of a Direct
Mapping of a Function
Example of an Indirect
Mapping of a Function
Logical Functions
Function is:
Master Clock
Generation
Functions
Function is:
Rate Adaptation
Physical
Functions
Functional
Entities
Functional Unit is:

SUM/MSUM
Functional Units
Functional Entities are:

Encoder, Decoder
Functional Unit is:

TRE/MTRE
Figure 21: Mapping of Functions to Functional Units

The following tables map the functions onto the BTS functional units:
Table 18 - Transmission
Table 19 - Telecommunication Baseband
Table 20 - Telecommunication RF
Table 21 - O&M
Table 22 - Support.
96 / 234
7 Functional Units
7.3.1 Functional Mapping

The functional mapping between the Transmission functions and the BTS
functional units is shown below.
Function
Functional Unit
Multiplexing
SUM/MSUM
Transmission of Signalling
SUM/MSUM
Transmission O&M
SUM/MSUM
Transmission of Traffic
SUM/MSUM
Clock Synchronization
SUM/MSUM
Table 18: Functional Mapping - Transmission
97 / 234
7 Functional Units
7.3.2 Telecommunication Baseband Functional Mapping

The functional mapping between the Telecommunication Baseband functions
and the BTS functional units is shown below.
Function
Functional Unit
Rate Adaptation
TRE/MTRE
Channel Encoding and Decoding
TRE/MTRE
Interleaving/De-interleaving
TRE/MTRE
Encryption/Decryption
TRE/MTRE
Demodulation
TRE/MTRE
Antenna Diversity
TRE/MTRE
Radio Link Recovery
TRE/MTRE
Radio Resource Indication
TRE/MTRE
Paging
TRE/MTRE
DTX
TRE/MTRE
DRX
TRE/MTRE
Quality Measurement
TRE/MTRE
Power Control
TRE/MTRE
Clock Distribution
TRE/MTRE
Protocol Management
TRE/MTRE
Radio Channel Management
TRE/MTRE
Transcoder Time Alignment
TRE/MTRE
Table 19: Functional Mapping - Telecommunication Baseband
98 / 234
7 Functional Units
7.3.3 Telecommunication RF Functional Mapping

The table below maps the Telecommunication RF functions onto the BTS
functional units.
Function
Functional Unit
RF Carrier Generation
TRE/MTRE
Frequency Hopping - Implemented by
TRE/MTRE
Frequency Hopping - Performed by
TRE/MTRE
Frequency Hopping - Controlled by
TRE/MTRE,
SUM/MSUM
GMSK Modulation
TRE/MTRE
Up-Conversion
TRE/MTRE
Power Amplification and Power Control
TRE/MTRE
Power Coupling and Detection
TRE/MTRE
Channel Selection and Conversion
TRE/MTRE
Signal Amplification
TRE/MTRE
A-D Conversion
TRE/MTRE
Digital Pre-processing
TRE/MTRE
Control the Status of the RF Hardware
TRE/MTRE
Clock Selection and Supervision
SUM/MSUM
Program the Frequency Synthesizers
TRE/MTRE
Handle Control and Alarm Processing
TRE/MTRE
Select the High or Low Gain Path on the Uplink
TRE/MTRE
Downlink Isolating
AN/MAN
Downlink Combining
AN/MAN
Downlink Duplexing
AN/MAN
Downlink Power Coupling and Detection
AN
Uplink Antenna Pre-amplification
AN/MAN
Uplink Signal Splitting (Duplexing)
AN/MAN
Table 20: Functional Mapping - Telecommunication RF
99 / 234
7 Functional Units
7.3.4 O&M Functional Mapping

The table below maps the O&M functions onto the BTS functional units.
Function
Functional Unit
SUM/MSUM
Fault Management
SUM/MSUM
Dedicated Alarm Handling
SUM/MSUM
External Alarm Handling
SUM/MSUM
Central Command Control
SUM/MSUM
Configuration/Initialization
SUM/MSUM,
TRE/MTRE, AN
Software Replacement
SUM/MSUM,
TRE/MTRE, AN
Configuration Parameter File Management
SUM/MSUM
Testing
SUM/MSUM
Alarm Detection, Filtering and Correlation
SUM/MSUM
Alarm Forwarding
SUM/MSUM
Alarm Translation
SUM/MSUM
Command Translation
SUM/MSUM
Table 21: Functional Mapping - O&M
7.3.5 Support Functional Mapping

The table below maps the support functions onto the BTS functional units.
Function
Functional Unit
Clock Generation and Distribution
SUM/MSUM
External Alarm Collection
SUM/MSUM
Internal Self-tests
SUM/MSUM
Table 22: Functional Mapping - Support
100 / 234
8 Configurations
8 Configurations
This chapter lists all possible configurations for the following BTS types:
9100 BTS indoor
9100 BTS outdoor
9110 Micro BTS / 9110-E Micro BTS.
101 / 234
8 Configurations
8.1 Naming Conventions Used for the Configurations

In the following sections all possible configurations are listed in tables, sorted
by the different types of BTSs.
The naming conventions used for the BTS configurations are listed in the
following table.
1x1...4
Means 1 sector with up to 4 TREs
3x1...2
Means 3 sectors with up to 2 TREs per sector
1x1...2/1x1...2
Means Multiband configuration, with 1 sector and up to 2

TREs in Band 1, and 1 sector and up to 2 TREs in Band 2
1x(...2/...2)
Means Multiband configuration, with 1 sector and up to

2 TREs in each band
Table 23: Naming Conventions Used for the BTS Configurations
8.2 9100 BTS Configurations

All 9100 BTS configurations use one SUM module. The different configurations
are due to the required number of carriers, and therefore TRE modules. These
TRE modules are connected to the antennae using one or more ANC, ANX
and ANY modules.
Many configurations are possible using the ANC, ANX and ANY modules, but
they all follow the same principles.
For the 9100 BTS six different sizes of cabinets are available:
CBO
MBI3
MBO1
MINI/CPT2
MBO2
MEDI/MBI5.
In addition, there is a distinction made between configurations for Indoor
BTSs and Outdoor BTSs.
102 / 234
8 Configurations
8.2.1 Configurations Using TWIN TRM

8.2.1.1 General Information About TWIN TRM
The TWIN TRM is a transceiver module with new capabilities and multiple
operation modes. The new capabilities are detailed in the following table.
Capability
Description
2 TRE Support
No (One TRE only)

Half Cabled (one TRE only)
Both Parts Cabled (The module has the capability to act
as 2 TREs)
Tx Div Capability
No (Not supported)
Yes
The module, due to the way it is cabled on the antenna
can provide transmission diversity (Same signal sent on
2 diffrent antennas).
For Tx Div and Rx div, it is not enough that all
outputs/inputs be cabled on same sector. They must
additionally be connected on different antennaes
This capability is restricted by cabling and is supported
only in case the TwoTRESupport is Both Parts Cabled on
the same sector and cabled on different AN.
4 Rx Div Support
No (Not supported)
Yes
The module, due to the way it is cabled on the antenna and
due to internal design can process receive signal coming
from 4 antennas. 4RxDiv is automatically activated if
TxDiv is activated and the module is 4RxDiv capable.
This capability is restricted by cabling and is supported
only in case the TwoTRESupport is Both Parts Cabled on
the same sector and cabled on different AN.
Table 24: TWIN TRM Capabilities

The functional modes described in the following table are available for the
TWIN TRM.
4RxDiv
Support
2TRE
Support
TxDiv
Capability
Possible TRE Mode

Configuration
No
Half Cabled
No
1TRE, No TxDiv
103 / 234
8 Configurations
4RxDiv
Support
2TRE
Support
TxDiv
Capability
Possible TRE Mode

Configuration
Yes
Both Paths
Cabled
Yes
1TRE, TxDiv
1TRE, No TxDiv
2TRE, No TxDiv
No
Both Paths
Cabled
Yes
2TRE, No TxDiv
1TRE, No TxDiv
1TRE, TxDiv
No
Both Paths
Cabled
No
2TRE, No TxDiv
1TRE, No TxDiv
Table 25: TWIN TRM Modes

The following constraints must be taken into account:
Configurations with more than 12 TRXs should not contain any G3 TRE
(TRGM, TRDM, TRDH)
Indoor configurations with more than 16 TRXs require the MBI5 cabinet
variant 2BK 25965 ABxx or newer.
8.2.1.2 9100 BTS Indoor Configurations Using TWIN TRM

The following table lists the 9100 BTS indoor configurations using TWIN TRM.
104 / 234
8 Configurations
TWIN
Mode
MBI3
MBI5
Carriers per sector
Carriers per sector
AC with
BU5
AC with
DC
other
(external)
BBU
AC with
BU5
AC with
BU90
AC with
DC
other
(external)
BBU
4/4
4/4
6/6
8/8
8/6
8/8
8/8
2/2/2
2/2/2
4/4/4
4/4/4
4/4/4
8/8/8
8/8/8
2/2/2/2
2/2/2/2
4/4/4/4
4/4/4/4
4/4/4/4
6/6/6/6
10
12
16
16
16
16
3/3
4/4
6/6
10/10
8/8
10/10
12/12
6/6/6
4/4/4
6/6/6
8/8/8
4+4
4+4
6+6
8+*
8+8
8+8
12+12
4/4+4/4
4/4+4/4
4/4+4/4
6/6+6/6
2/2/2+2/2/2 2/2/2+2/2/2 2/2/2+2/2/2 4/4/4+4/4/4
2/2
2/2
2/2
4/4
4/4
4/4
4/4
1/1/1
2/2/2
2/2/2
2/2/2
2/2/2
2/2/2
4/4/4
Coverage
Mode
TxDiv.
2Rx Div.
Low Loss
2/2
2/2
2/2
2/2
2/2
2/2
2/2
2/2/2
2/2/2
2/2/2
2/2/2
Coverage
Mode
TxDiv.
4Rx Div.
Low Loss
2/2
2/2
2/2
2/2
2/2
2/2
2/2
2/2/2
2/2/2
2/2/2
2/2/2
Capacity
Mode
Capacity
Mode
Low Loss
Multiband
& MB Cell
Coverage
Mode
TxDiv.
2Rx Div.
Number
of
sectors
105 / 234
8 Configurations
TWIN
Mode
Number
of
sectors
MBI3
MBI5
Carriers per sector
Carriers per sector
AC with
BU5
AC with
DC
other
(external)
BBU
AC with
BU5
AC with
BU90
AC with
DC
other
(external)
BBU
Extended
Cell
1 In, 1
Out
4+4
4+4
4+4
8+8
8+8
8+8
8+8
Extended
Cell
TxDiv,
4RX Div
for outer
cell
1 In, 1
Out
4+2
4+2
4+2
8+2
8+2
8+2
8+2
106 / 234
8 Configurations
8.2.1.3 9100 BTS Outdoor Configurations Using TWIN TRM

The following table lists the 9100 BTS outdoor configurations using TWIN TRM.
TWIN Mode
Number of sectors
MBO1E
MBO2E
Carriers per sector
Carriers per sector
6/6
8/8
4/4/4
8/8/8
2/2/2/2
6/6/6/6
12
16
6/6
12/12
8/8/8
6+6
12+12
2/2+2/2
6/6+6/6
4/4/4+4/4/4
2/2
4/4
2/2/2
4/4/4
2/2
2/2
2/2/2
2/2
2/2
2/2/2
Extended Cell
1 In, 1 Out
4+4
8+8
Extended Cell TxDiv,

4RX Div for outer cell
1 In, 1 Out
4+2
8+2
Capacity Mode
Capacity Mode Low Loss
Multiband & MB Cell
Coverage Mode TxDiv.

2Rx Div.

2Rx Div. Low Loss

4Rx Div. Low Loss
107 / 234
8 Configurations
8.2.2 9100 BTS Indoor Configurations - DC Powered

The 9100 BTS used for indoor configurations can be powered by DC or AC.
The DC-powered configurations are described in the following sections.
8.2.2.1 9100 BTS Standard Indoor DC-Powered Configurations

The following table lists all possible standard indoor configurations which are
DC powered.
Cabinet Size
Configuration Type
GSM 850
GSM 900
GSM 1800
GSM 1900
Notes
MINI
1x1...4
MINI
2x1...2
MINI
1x1...3 + 1x1
MINI
3x1
MEDI
1x1...8
MBI3
1x1...8
(2)
MBI5
1x1...8
MEDI
1x9...12
(1)(2)
MBI5
1x9...12
(2)
MBI3
2x1...4
(2)
MEDI
2x1...6
(2)
MBI5
2x1...6
(2)
MEDI
1x1...8 + 1x1...4
MBI5
1x1...8 + 1x1...4
MBI3
3x1...2
MEDI
3x1...4
(2)
MBI5
3x1...4
(2)
(1) 1x12 is a 8+4 rack layout.

(2) No restrictions for GSM 1900 configurations based on TRPMs (Medium-power TREs). For
medium-power configurations using the TRAPs (Medium-power TREs, EDGE capable) some temperature
restrictions are possible, as shown in Table 27.
Table 26: 9100 BTS Indoor Standard Configurations, DC Powered
108 / 234
8 Configurations
8.2.2.2 9100 BTS Indoor DC-Powered Configurations with Restrictions

Configurations which do not fulfill the +45 C ambient temperature are listed
in the table below.
Restrictions
Configurations impacted
Comments
+40 C
MEDI 1x1...8 DC, Standard

medium-power configuration GSM
1900 (using TRAP TREs)
+45 C up to 1x6 with 45 W
MBI3 2x1...4 DC, Standard

MEDI 1x9...12 Standard
medium-power configuration
GSM 1900 (using TRAP TREs)
MEDI 1x9...12 Medium-power
low-losses configuration GSM 1900
(using TRAP TREs)
MBI5 1x9...12 AC or DC, Standard
MBI5 1x9...12 AC or DC,
Medium-power low-losses
configuration GSM 1900 (using
TRAP TREs)
MEDI 2x3...6 Medium-power
(using TRAP TREs)
MBI5 2x3...6 DC, Medium-power
(using TRAP TREs)
+45 C up to 1x7...8 with 28 W (or 45 W at +40 C)

+45 C up to 2x4 with 28 W (or 45 W at +40 C)

+45 C up to 2x3...5 with 45 W
+45 C up to 2x3...5 with 45 W
+45 C up to 3x1...3 with 45 W
+45 C up to 3x1...3 with 45 W
Table 27: Indoor Configurations versus Temperature Restrictions
109 / 234
8 Configurations
8.2.2.3 9100 BTS Indoor DC-Powered Low Loss/High-Power Configurations

The low loss and high-power configurations for 9100 BTS Indoor DC-powered
configurations are given in the following table.
Cabinet Size
Configuration Type
Low Losses (1)
High Power GSM

900/1800
Notes
MINI
2x1
MBI3
2x1
MEDI
1x1...4
MBI5
1x1...4
MBI3
1x3...4
MEDI
1x3...8
MBI5
1x3...8
MEDI
1x9...12
(2)
MBI5
1x9...12
(2)
MBI5
2x1...2
MEDI
2x1...4
MBI5
2x1...4
MEDI
2x3...6
(2)
MBI5
2x3...6
(2)
MEDI
3x1...2
MEDI
3x1...3
(3)
MBI5
3x1...3
(1) Configurations valid for GSM 900, GSM 1800 and GSM 1900.
(2) No restrictions for GSM 1900 configurations based on TRPM (Medium-power TRE). For medium-power
configurations using the TRAP (Medium-power TRE, EDGE capable) some temperature restrictions are
possible, as shown in Table 27.
(3) Configuration with mixed high-power TREs and medium-power TREs. For each sector: the two first
TREs are high-power TREs (TADH, TAGH), and the third TRE is a medium-power TRE (TRAD/TRADE).
Table 28: 9100 BTS Indoor Low-losses and High-power Configurations, DC Powered
110 / 234
8 Configurations
8.2.2.4 9100 BTS Indoor Multiband DC-Powered Configurations

The table below lists the 9100 Indoor multiband DC configurations for all
GSM bandwidths.
Cabinet Size
Configuration Type
Single Band
Cells
Multi-Band
Cells (1)
Notes
MINI
1x1...2/1x1...2
MBI3
1x1...4/1x1...4
MINI
1x(...2/...2)
MBI3
1x(...4/...4)
MEDI
1x1...6/1x1...6
MBI5
1x1...6/1x1...6
MEDI
1x(...6/...6)
MBI5
1x(...6/...6)
MEDI
1x1...8/1x1...4
MBI5
1x1...8/1x1...4
MBI5
1x(...8/...4)
MEDI
1x1...4/1x1...8
MBI5
1x1...4/1x1...8
MBI5
1x(...4/...8)
MEDI
1x3...8LL/1X1...4
MBI5
1x3...8LL/1X1...4
MEDI
1x1...4/2x1...4
MBI5
1x1...4/2x1...4
MEDI
2x1...4/1x1...4
MBI5
2x1...4/1x1...4
MEDI
1x1...4/...4,...2,...2
MBI5
1x1...4/...4,...2,...2
MEDI
...4,...2,...2/1x1...4
MBI5
...4,...2,...2/1x1...4
MEDI
2x1...4/2x1...2
111 / 234
8 Configurations
Cabinet Size
Configuration Type
Single Band
Cells
Multi-Band
Cells (1)
Notes
MBI5
2x1...4/2x1...2
MEDI
2x(...4/...2)
MBI5
2x(...4/...2)
MEDI
2x1...2/2x1...4
MBI5
2x1...2/2x1...4
MEDI
2x(...2/...4)
MBI5
2x(...2/...4)
MEDI
1x(...2/...2),1x(...4/...4)
MBI5
1x(...2/...2),1x(...4/...4)
(1)
: Multiband cell configurations are not available for GSM 900/1900
Table 29: 9100 BTS Indoor Multiband (GSM 900/1800 and GSM 900/1900) Configurations, DC Powered
112 / 234
8 Configurations
8.2.3 9100 BTS Indoor Configurations - AC Powered

9100 BTS used for indoor configurations can be powered by DC or AC. All
possible indoor configurations which are AC powered are described in the
following sections.
8.2.3.1 9100 BTS Standard Indoor AC-Powered Configurations

The 9100 BTS standard indoor AC-powered configurations are given in the
following table.
Cabinet Size
Configuration
Type
GSM 850
GSM 900
GSM 1800
GSM 1900
Notes
MBI3
1x1...4
(2)
MEDI
1x2...8
MBI5
1x1...8
(4)
MBI5
1x9...12
(1)(2)(5)
MEDI
2x1...2
MBI3
2x1...2
(2)
MBI5
2x1...4
(3)
MEDI
2x1...6
(2)
MBI5
2x1...6
(2)(5)
MBI5
1x1...8 + 1x1...4
(1)(2)
MBI3
3x1
(2)
MEDI
3x1...2
MBI5
3x1...2
(3)
MEDI
3x1...4
(2)
MBI5
3x1...4
(2)(5)
(1) Configurations with more than 8 TREs: no possibility of having internal batteries.
(2) Configurations without the possibility of having standard internal batteries, but a small battery (BATS)
is possible.
(3) Configurations with the possibility of having standard internal batteries (large BBU).
(4) Configurations with the possibility of having standard internal batteries (large BBU), a small battery
(BATS) is also possible.
Table 30: 9100 BTS Indoor Standard Configurations, AC Powered
113 / 234
8 Configurations
8.2.3.2 9100 BTS Indoor AC-Powered Low Loss/High-Power Configurations

The low loss and high-power configurations for 9100 BTS Indoor AC-powered
configurations are given in the following table.
Cabinet Size
Configuration Type
Low Losses (1)
High Power GSM

1800
Notes
MBI3
1x3...4
(2)
MBI5
1x1...4
(2)
MBI5
1x3....8
(3)
MBI5
1x9...12
(2)(4)
MBI3
2x1
(2)
MBI5
2x1...4
(2)
MBI5
3x1...3
(2)
(1) Configurations valid for GSM 900, GSM 1800 and GSM 1900..
is possible.
(3) Configurations with the possibility of having standard internal batteries (large BBU); but a small battery
(BATS) is also possible.
Table 31: 9100 BTS Indoor Low Losses and High Power Configurations, AC Powered
114 / 234
8 Configurations
8.2.3.3 9100 BTS Indoor Multiband AC-Powered Configurations

The table below lists the 9100 Indoor multiband AC configurations for all
GSM bandwidths.
Cabinet Size
Configuration Type
Single Band
Cells
Multi Band Cells

(3)
Notes
MBI5
1x1...6/1x1...6
(2)
MBI5
1x(...6/...6)
(2)
MEDI
1x1...8/1x1...4
(1)
MBI5
1x1...8/1x1...4
(2)
MBI5
1x(...8/...4)
(2)
MBI5
1x1...4/1x1...8
(2)
MBI5
1x(...4/...8)
(2)
MBI5
1x3...8LL/1x1...4
(2)
MBI5
1x1...4/2x1...4
(2)
MBI5
2x1...4/1x1...4
(2)
(1) Configurations without the possibility of having internal batteries.

is possible.
(3) Multiband cell configurations are not available for GSM 900/1900
Table 32: 9100 BTS Indoor Multiband Configurations (GSM 900/1800 and GSM 900/1900), AC Powered
8.2.3.4 9100 BTS Indoor Extended Cell Configurations

The following table lists all possible indoor extended cell configurations.
Cabinet Size
Configuration Type
AC
DC
GSM 900
Notes
MEDI
1x1...4LL/1x1...4
(1)
MBI5
1x1...4LL/1x1...4
(1)(3)
MEDI
1x1...4/1x1...4
(2)
MBI5
1x1...4/1x1...4
(2)(3)
(1) Configuration based on REK.

(2) Configuration based on TMA.
(3) AC versions: without BBU, with BATS, or with large BBU
Table 33: 9100 BTS Indoor Standard Configurations, Extended Cell
115 / 234
8 Configurations
8.2.4 9100 BTS Outdoor Configurations

The following tables list all possible outdoor configurations.
8.2.4.1 Standard 9100 BTS Outdoor Configurations

The table below shows the standard 9100 BTS outdoor configurations with fulfill
the +45 C ambient temperature requirements. Configurations which do not
fulfil this required are shown in the next section.
Cabinet Size
Configuration Type
GSM 850
GSM 900
GSM 1800
GSM 1900
Notes
CBO
1x1...2
MINI
1x1...8
MBO1
1x1...8
X(7)
CBO
2x1
CBO
2x2
(9)
MINI
2x1...4
MBO1/MBO1E 2x1...4
X(8)
CBO
3x1
(9)
MINI
3x1...2
MBO1/MBO1E 3x1...2
MEDI
1x1...8
(1)
MEDI
1x9...12
X(3)
(2)
MBO2/MBO2E 1x9...12
(2)
CPT2
2x1...6
X(5)
MEDI
2x1...6
X(4)
X(3)
MBO2/MBO2E 2x1...6
MBO2/MBO2E 1x1...8 + 1x1...4
CPT2
3x1...4
X(5)
X(3)
MEDI
3x1...4
X(4)
X(6)
X(3)
MBO2/MBO2E 3x1...4
MBO2/MBO2E 4x1...3
116 / 234
8 Configurations
Cabinet Size
Configuration Type
MBO2/MBO2E 2x4 + 2x2
GSM 850
GSM 900
GSM 1800
GSM 1900
Notes
(1) Configurations replaced by MINI configurations.

(2) 1x12 configuration is a 8+4 rack layout.
possible as shown in Table 35.
(4) Configuration could be replaced by an equivalent CPT2 configuration.
(5) Configuration with some restrictions as shown in Table 35.
(6) Configuration could be replaced by an equivalent CPT2 configuration with some restrictions as shown
in Table 35.
(7) The configuration is limited to 6 TREs.
(8) The configuration is limited to 6 TREs over the two sectors.
(9) The configuration is available only on CBO DC variant.
Table 34: Standard 9100 BTS Outdoor Configurations
117 / 234
8 Configurations
8.2.4.2 9100 BTS Outdoor Configurations with Restrictions

Outdoor configurations which do not fulfill the +45 C ambient temperature
are listed in the table below.
Restrictions
Configurations impacted
Comments
+38 C
MEDI 2x1...4 High-power configuration GSM

1800 (using TADH TREs)
+40 C
CPT2 3x1...2 High-power configuration GSM

1800 (using TADH TREs)
CPT2 2x1...6 Standard medium-power

configuration GSM 1800 (using TRAD/TRADE
TREs)
+45 C up to 2x1...4 with 45 W

configuration GSM 1800 (using TRAD/TRADE
TREs)
+45 C up to 3x1...3 with 45 W
MEDI 1x9...12 Standard medium-power

configuration GSM 1900 (using TRAP TREs)
MEDI 1x9...12 Medium-power low-losses


+45 C up to 2x1...5 with 45 W

+45 C up to 2x3...5 with 45 W

+45 C up to 3x1...3 with 45 W

+45 C up to 3x1...3 with 45 W

+45 C 3x3 with 45 W
+40 C and
power reduced
to 28 W
Table 35: Outdoor Configurations versus Temperature Restrictions
118 / 234
8 Configurations
8.2.4.3 9100 BTS Outdoor Low Losses/ High-Power Configurations

The low loss and high-power configurations of the outdoor 9100 BTS are
described below.
Cabinet
Size
Configuration Type
Low Losses
GSM 900/1800/1900
High Power
GSM 900/1800
Notes
CBO
1x1...2
MINI
1x1...4
MBO1/MBO1E 1x1...4
CBO
2x1
MINI
2x1...2
MBO1/MBO1E 2x1...2
1x3...8
MBO1/MBO1E 1x5...8
(7)
MEDI
MEDI
1x9...12
(1)
MEDI
2x1...2
(2)
MEDI
2x1...4
X (4)
X (3)
2x3...6
(1)
MBO2/MBO2E 2x3...6
MBO2/MBO2E 2x1...4
MEDI
CBO
3x1
(8)
CPT2
3x1...2
(3)
MEDI
3x1...2
(5)
MBO2/MBO2E 3x1...2
3x1...3
(6)
MBO2/MBO2E 3x1...4
(6)
MEDI
MEDI
3x1...4
(1)
MEDI
3x3...4
(3)
119 / 234
8 Configurations
Cabinet
Size
Configuration Type
MBO2/MBO2E 3x3...4
Low Losses
GSM 900/1800/1900
High Power
GSM 900/1800
Notes
possible as shown in Table 35.
(2) Configuration replaced by MINI configuration.
(3) Restriction as shown in Table 35.
(4) The 2x1...4 configuration is now a 2x3...6 low losses, under-equipped configuration.
(5) Configuration could be replaced by equivalent CPT2 with temperature restriction as shown in Table 35.
(6) Configuration with mixed high-power TREs and medium-power TREs.
(7) For GSM 1900, configuration is limited to 6 TREs.
(8) Configuration available only CBO DC variant
Table 36: 9100 BTS Outdoor Low-losses and High-power Configurations
120 / 234
8 Configurations
8.2.4.4 9100 BTS Outdoor Multiband GSM 900/1800 and GSM 900/1900 Configurations
The table below shows the outdoor multiband configurations for both the GSM
900/1800 and GSM 900/1900 configurations.
Cabinet Size
Configuration Type
Single Band
Cells
Multi-Band
Cells (1)
Notes
MINI
1x1...4/1x1...4
MBO1/MBO1E
1x1...4/1x1...4
MINI
1x(...4/...4)
MBO1/MBO1E
1x(...4/...4)
MEDI
1x1...6/1x1...6
MBO2/MBO2E
1x1...6/1x1...6
MEDI
1x(...6/...6)
MBO2/MBO2E
1x(...6/...6)
MBO2/MBO2E
1x1...8/1x1...4
MBO2/MBO2E
1x1...4/1x1...8
MBO2/MBO2E
1x(...8/...4)
MBO2/MBO2E
1x(...4/...8)
MEDI
1x1...4/2x1...4
MBO2/MBO2E
1x1...4/2x1...4
MEDI
2x1...4/1x1...4
MBO2/MBO2E
2x1...4/1x1...4
CPT2
2x1...2/2x1...2
MEDI
1x1...4/...4,...2,...2
MBO2/MBO2E
1x1...4/...4,...2,...2
MEDI
...4,...2,...2/1x1...4
MBO2/MBO2E
...4,...2,...2/1x1...4
MEDI
2x1...4/2x1...2
MBO2/MBO2E
2x1...4/2x1...2
MEDI
2x1...2/2x1...4
MBO2/MBO2E
2x1...2/2x1...4
121 / 234
8 Configurations
Cabinet Size
Configuration Type
Single Band
Cells
Multi-Band
Cells (1)
Notes
MEDI
2x1...3/2x1...3
MBO2/MBO2E
2x1...3/2x1...3
CPT2
2x(...2/...2)
MEDI
2x(...4/...2)
MBO2/MBO2E
2x(...4/...2)
MEDI
2x(...2/...4)
MBO2/MBO2E
2x(...2/...4)
MEDI
2x(...3/...3)
MBO2/MBO2E
2x(...3/...3)
MEDI
1x(...2/...2),1x(...4/...4)
MBO2/MBO2E
1x(...2/...2),1x(...4/...4)
MEDI
3x1...2/3x1...2
MBO2/MBO2E
3x1...2/3x1...2
MEDI
3x(...2/...2)
MBO2/MBO2E
3x(...2/...2)
(1)
: Multiband cell configurations are not available for GSM 900/1900
Table 37: 9100 BTS Outdoor Multiband (GSM 900/1800 and GSM 900/1900) Configurations
122 / 234
8 Configurations
8.2.4.5 9100 BTS Outdoor Multiband (GSM 850/1800) Configurations

The GSM 850/1800 outdoor configurations for the 9100 are listed below.
Cabinet Size
Configuration Type
Single Band
Cells
Multi Band
Cells
Notes
MBO2/MBO2E
3x1/3x1...3
MBO2/MBO2E
3x(1/...3)
Table 38: 9100 BTS Outdoor Multiband (GSM 850/1800) Configurations
8.2.4.6 9100 BTS Outdoor Multiband GSM 850/1900 Configurations

The multiband configurations for GSM 850/1900 9100 BTS outdoor
configurations is shown in the following table.
Cabinet Size
Configuration Type
Single Band
Cells
Multi Band
Cells
Notes
MBO2/MBO2E
3x1/3x1...3
MBO2/MBO2E
3x(1/...3)
Table 39: 9100 BTS Outdoor Multiband (GSM 850/1900) Configurations
123 / 234
8 Configurations
8.3 BTS 9110 Configurations

All BTS 9110 configurations use one MSUM module. The different
configurations are due to the required number of carriers, the number of BTS
9110 slave units and therefore MTRE modules. These MTRE modules are
connected to the antennae using one or more MAN modules.
The following table lists all possible BTS 9110 configurations.
GSM 900
GSM 1800
1x1...2, 2 W Single Antenna
1x1...2, 2 W, Single Antenna
1x1...4 + 1x1...2, 2 W, Single Antenna
1x1...4 + 1x2, 2 W, Single Antenna
1x1...2, 4.5 W, Low Loss (1)
1x1...2, 4.5 W, Low Loss (1)
1x1...4, 4.5 W, Low Loss (1)
1x1...4, 4.5 W, Low Loss (1)
1x1...6, 4.5 W, Low Loss (1)
1x1...6, 4.5 W, Low Loss (1)
2x1...2, 4.5 W, Low Loss (1)
2x1...2, 4.5 W, Low Loss (1)
3x1...2, 4.5 W, Low Loss (1)
3x1...2, 4.5 W, Low Loss (1)
Multiband GSM 900/1800 (2)
1x1...2/1x1...2
1x1...4/1x1...2
1x1...2/1x1...4
(1) Low loss configurations are only possible with antenna network type
2 (MAN2), which means that low loss configurations have two antenna
accesses.
(2) Each band can be configured either in 2 W or in 4.5 W.
Table 40: 9110 Micro BTS Configurations
124 / 234
8 Configurations
8.4 9110 Micro BTS-E Configurations

All 9110 Micro BTS-E configurations use one MSUMA module. The different
configurations are due to the required number of carriers, the number of
9110 Micro BTS/9110-E Micro BTS slave units and therefore MTRE modules.
These MTRE modules are connected to the antennae using one or more
MAN modules.
The following table lists all possible 9110 Micro BTS-E configurations.
GSM 850
GSM 900
GSM 1800
GSM 1900
1x1...2, Single Antenna
1x1...4 + 1x1...2, Single

Antenna
1x1...4 + 1x1...2, Single

Antenna
1x1...4 + 1x1...2, Single

Antenna
1x1...4 + 1x1...2, Single

Antenna
3x1...2+ 1x1...4, Single

Antenna
3x1...2+ 1x1...6, Single

Antenna
3x1...2+ 1x1...6, Single

Antenna
3x1...2+ 1x1...6, Single

Antenna
3x1...2+ 1x1...6, Single

Antenna
3x1...2+ 1x1...6, Single

Antenna
3x1...2+ 1x1...6, Single

Antenna
3x1...2+ 1x1...6, Single

Antenna
1x1...6 + 1x1...2, Single

Antenna
1x1...6 + 1x1...2, Single

Antenna
1x1...6 + 1x1...2, Single

Antenna
1x1...6 + 1x1...2, Single

Antenna
1x1...4+ 1x1...6, Single

Antenna
1x1...4+ 1x1...6, Single

Antenna
1x1...4+ 1x1...6, Single

Antenna
1x1...4+ 1x1...6, Single

Antenna
1x1...4+ 2x1...3, Single

Antenna
1x1...4+ 2x1...3, Single

Antenna
1x1...4+ 2x1...3, Single

Antenna
1x1...4+ 2x1...3, Single

Antenna
2x1...2+ 1x1...6, Single

Antenna
2x1...2+ 1x1...6, Single

Antenna
2x1...2+ 1x1...6, Single

Antenna
2x1...2+ 1x1...6, Single

Antenna
2x1...2+ 2x1...3, Single

Antenna
2x1...2+ 2x1...3, Single

Antenna
2x1...2+ 2x1...3, Single

Antenna
2x1...2+ 2x1...3, Single

Antenna
125 / 234
8 Configurations
GSM 850
GSM 900
GSM 1800
GSM 1900
1x1...2, Low Loss (1)
1x1...2, Low Loss (1)
1x1...4, Low Loss (1)
1x1...4, Low Loss (1)
1x1...6, Low Loss (1)
1x1...6, Low Loss (1)
2x1...2, Low Loss (1)
2x1...2, Low Loss (1)
2x1...4, Low Loss (1)
2x1...4, Low Loss (1)
2x1...6, Low Loss (1)
2x1...6, Low Loss (1)
3x1...2, Low Loss (1)
3x1...2, Low Loss (1)
3x1...4, Low Loss (1)
3x1...4, Low Loss (1)
4x1...2, Low Loss (1)
4x1...2, Low Loss (1)
5x1...2, Low Loss (1)
5x1...2, Low Loss (1)
6x1...2, Low Loss (1)
6x1...2, Low Loss (1)
Multiband GSM
900/1800 (2)
1x1...2/1x1...2
1x1...4/1x1...2
1x1...2/1x1...4
Multiband GSM 900/1800 (2)
126 / 234
8 Configurations
GSM 850
GSM 900
1x1...2/1x1...2
GSM 1800
GSM 1900
1x1...4/1x1...2
1x1...2/1x1...4
1x1...4/1x1...4
1x1...6/1x1...2
1x1...2/1x1...6
1x1...6/1x1...4
1x1...4/1x1...6
1x1...6/1x1...6
(1) Low loss configurations are only possible with antenna network type 2 (MAN2), which means that low
loss configurations have two antenna accesses.
(2) Each band can be configured either in 2 W or in 4.5 W.
Table 41: 9110 Micro BTS-E Configurations
127 / 234
8 Configurations
128 / 234
9 Antenna Network
9 Antenna Network
This chapter describes the AN/MAN functions and software. It provides
information about the AN/MAN:
Functions
External interfaces
Modules
Software implementation.
129 / 234
9 Antenna Network
9.1 Introduction to Antenna Network

The main functions of the AN/MAN are:
Downlink:
Isolation of the transmitters from the receivers
Combining the output of two transmitters to allow them to share a
single antenna
Duplexing to allow transmitters and receivers to share the same antenna
Power Coupling and Detection (9100 BTS only) to sample the VSWR
forward and reflected power.
Uplink:
Pre-amplification to amplify the received signals and control the overall
gain of the antenna network
Splitting to distribute the received signals to a pair of receivers.
The AN modules are part of the 9100 BTS and the MAN modules are part of
the 9110 Micro BTS/9110-E Micro BTS.
9.1.1 9100 BTS Modules

There are five types of AN module, called ANX, ANC, AGC, ANB and ANY. The
purpose of these modules is to connect the TREs to the antennae.
Reduced configurations with antenna diversity and up to two TREs can use
the ANB. Configurations with antenna diversity and two or more TREs always
use at least one ANX or ANC/AGC. More TREs can be connected to the
antenna by first connecting them to an ANY. The ANY is then connected to an
ANX or ANC/AGC. One or more ANY are used depending on the number of
TREs in the BTS 9100 configuration. See Section 9.2 for more information
about possible configurations.
9.1.2 BTS 9110/9110-E Modules

There are two types of MAN module for the BTS 9110/9110-E.
The MAN1/MANM is used to connect two TRX modules to a single antenna.
It comprises a combiner, a duplexer, and a low-noise amplifier with power
splitter. This is shown in Figure 23.
The MAN2/MAND is available in dual form. It is a low loss variant and is
used to connect two TRX modules to two antennae without a combiner. This
variant comprises two duplexers and two low-noise amplifiers, both with power
splitters. This is shown in Figure 24.
130 / 234
9 Antenna Network
9.2 Antenna Network Functions

The functions for the 9100 BTS and the 9110 Micro BTS/9110-E Micro BTS
are described separately.
The principal functional entities contained in the AN/MAN are described in
Functions
Description
9100
9110
Micro
BTS/
9110-E
Micro
BTS
ANCON/ANCC/
AGCC/AGCRI
The Antenna Network Controller controls the configuration

and initialization of the AN software. It also controls the uplink
pre-amplification of the received RF signals.
The ANCON/ANCC/AGCC includes a directional coupler and

VSWR receiver to measure forward and reflected transmitter
power. The measurement is performed for all bursts with output
power less than Power Step 9. This is because of the limited
isolation between the transmission and reception parts of the AN.
If more than 25% of the measurements exceed a pre-defined
threshold, the ANCON/ANCC/AGCC/AGCRI raises an alarm.
This alarm causes the TRE transmitters to be switched off.
The AGCC controlls the power for two TMAs via an overcurrent
protection circuit.
The AGCRI performs only the sector selection, RF cabling
detection, remote power ON/OFF and remote inventory functions.
Combiner
The Combiner concentrates two TRE/MTRE transmitter outputs

into a single RF output, thus reducing the number of antennae
required.
The two Combiners used in the ANY module allow the outputs
from four TREs to be fed into the two inputs of a single ANX
module.
The two Combiners used in the ANC/AGC module allow the
outputs from four TREs to be fed into one ANC/AGC module.
In the ANB module no combiners are used, each TRE output is
fed to one antenna.
The Combiners in the MAN1 allow the outputs from two TRXs
to be fed to a single antenna.
Divider
The Dividers split and distribute the received RF signals from

the antenna. The ANC, AGC and ANX modules provide two
outputs for each antenna input. This process can be continued
by the ANY module to provide four outputs from the received
signal. Each output is connected to a different TRE input, to
provide diversity. The MAN1 provides two outputs and the MAN2
provides four outputs.
131 / 234
9 Antenna Network
Functions
Description
9100
9110
Micro
BTS/
9110-E
Micro
BTS
Duplexer
The Duplexers provide the coupling function for the transmitted

and received RF signals. Each duplexer provides a bi-directional
signal path, allowing a single antenna to be used for the
transmission and reception of uplink and downlink signals.
The Duplexer includes a filter unit to suppress spurious emissions

and transmitter noise that could interfere with the receive
frequency bandwidth.
LNA
The LNA amplifies the received signals. It has a fixed nominal

gain value. The LNA has an extremely low Noise Factor and good
values for VSWR, compression and reliability.
Table 42: AN / MAN Principal Functional Entities
132 / 234
9 Antenna Network
9.2.1 9100 BTS Functions

The ANX and ANY functions and interfaces are shown first, followed by a
mapping of AN functions on its functional entities.
9.2.1.1 ANX/ANY Functions and Interfaces

The following figure shows the ANX and ANY principal functions and their
interfaces.
ANY
RFI
to/
from
TRE
ANX
TX
Combiner
RX
TX
XRF to
ANT A
Duplexer
RX
LNA
RX
RFI
to/
from
TRE
Divider
TX
Divider
RX
RX
Divider
RX
BSII
ANCON
BCB
RFI
to/
from
TRE
TX
RI
CLKI
Divider
RX
RX
Divider
Combiner
RFI
to/
from
TRE
RX
Divider
RI
BCB
RX
LNA
TX
XRF to
ANT B
Duplexer
TX
RX
RX
Figure 22: ANX and ANY Functions and Interfaces

The ANC and AGC are a combination of ANX and ANY in one module.
The ANB is an ANC without the combiner.
133 / 234
9 Antenna Network
9.2.1.2 9100 BTS Functions to Entities Mapping

The following table shows how the 9100 BTS AN functions, described in
Telecommunication Functions - RF (Section 5), map onto the AN functional
entities.
Functions
Combiner
Duplexer
Divider
ANCON/ANCC
/AGCC /AGCRI
Downlink Isolation
Downlink Combining
Downlink Duplexing
Downlink Power
Coupling/Detection**
TMA Power Supply Control*
ANCON
: ANCON board is used in ANX module
ANCC
: ANCC board is used in ANC module
AGCC
: AGCC board is used in AGC module
: Only provided by AGCC
**
: Not provided bythe AGCRI
Table 43: Distribution of AN Functions between AN Functional Entities
134 / 234
9 Antenna Network
9.2.2 9110 Micro BTS/9110-E Micro BTS Functions

The MAN functions are interfaces are described first, followed by a
function-to-functional entity mapping.
9.2.2.1 MAN Functions and Interfaces

The following figures show the MAN principal functions and interfaces, both for
9110 Micro BTS and 9110-E Micro BTS.
Even if these functional descriptions are identical, the MANxx module for
9110-E Micro BTS is not the same that the MANxx module for 9110 Micro BTS.
TX1
Combiner
TX2
Duplexer
RX1
Antenna
XRF
Divider
LNA
RX2
Figure 23: MAN1 / MANM for Two TRXs with One Antenna Without Diversity
TX1
TRE 1
Duplexer
Divider
RX1
Antenna
XRF
LNA
RX2
TRE 2
Duplexer
Divider
RX1
Antenna
XRF
LNA
RX2
TX2
Figure 24: MAN2 / MAND for Two TRXs with Two Antennas With Diversity
9.2.2.2 9110 Micro BTS/9110-E Micro BTS Functions to Entities Mapping

For the 9110 Micro BTS/9110-E Micro BTS, all of the MAN functions map onto
the MAN functional entity.
135 / 234
9 Antenna Network
9.3 Antenna Network External Interfaces

The AN/MAN exchanges data with external entities through the links described
Interface
Description
9100
9110
Micro
BTS/
9110-E
Micro
BTS
BCB
The BCB is used to exchange information and data between

the OMU and the AN. The BCB allows the OMU to perform auto
identification and remote inventory functions.
BSII
The BSII is used to transfer O&M messages from the OMU to

the AN. These IOM messages are used for software download,
transfer of configuration data, error and alarm collection,
etc. The BSII also allows the OMU to broadcast IOM_CONF
information to the AN.
CLKI
The CKLI receives timing from the TRANS/CLOCK for

all functions in the AN. The clocks are supplied by the
TRANS/CLOCK Unit.
RFI
The Radio Frequency Interface connects the TRE/MTREs to

the AN/MAN modules. Each TRE/MTRE has its own RFI which
consists of three lines, one TX and two RX, or two lines for the
9110 Micro BTS/9110-E Micro BTS fitted with a MAN1 and no
antenna diversity.
XRF
The XRF is the interface between the AN/MAN and the

antennae and is functionally identical to the Air Interface.
Table 44: AN/MAN External Interfaces
136 / 234
9 Antenna Network
9.4 Antenna Network Modules

The BTS module variants are described separately.
9.4.1 9100 BTS Modules

The four types of AN module, ANX, ANY, ANC, AGC and ANB are available as
GSM 850, GSM 900, GSM 1800, or GSM 1900 variants, see the following table.
No. of
Antennas
GSM 850
GSM 900
GSM 1800
GSM 1900
ANXG
ANXD
ANXP
ANYL
ANYG
ANYD
ANYP
ANYGH
ANYDH
ANCL
ANCG,
ANCGP*
ANCD
ANCP
AGC08
AGC9E,
AGC9P*
AGC18
ANBG
ANBD
: Availablle only for GSM 900 Primary band
Table 45: AN Module Variants

Not all AN functions are concentrated on each AN module.
The following table lists the AN functions of the 9100 BTS against the AN
modules that physically contain those functions.
Functions
Module
ANX, ANC, AGC, ANB
ANX, ANC, AGC, ANB
Downlink Isolation
ANX, ANC, AGC, ANB
Downlink Combining
ANY, ANC
Downlink Duplexing
ANX, ANC, AGC, ANB
Downlink Power Coupling/Detection
ANX, ANC, AGC, ANB
ANX, ANC, AGC, ANB
ANX, ANY, ANC, AGC, ANB
Table 46: AN Functions and Modules
137 / 234
9 Antenna Network
9.4.2 9110 Micro BTS/9110-E Micro BTS Modules

The MAN module is available as GSM 850, GSM 900, GSM 1800 or GSM
1900 variants, see the following table.
No. of
Antennas
GSM 850
GSM 900
GSM 1800
GSM 1900
MAN1G
MAN1E
MAN1D
MAN2G
MAN2E
MAN2D
Table 47: MAN Module Variants for 9110 Micro BTS
No. of
Antennas
GSM 850
GSM 900
GSM 1800
GSM 1900
MANML
MANME
MANMD
MANMP
MANDL
MANDE
MANDD
MANDP
Table 48: MAN Module Variants for 9110-E Micro BTS

All MAN functions of the 9110 Micro BTS/9110-E Micro BTS are concentrated
on each MAN module.
138 / 234
9 Antenna Network
9.5 Antenna Network Software Implementation

The AN software is described in terms of functions. The AN functions are
implemented in firmware and software.
9.5.1 Firmware
The AN firmware functions are:
AN auto-tests
Retrieving the IOM mapping from the BSII
Establishing a connection with the SUM on the IOM.
Dialog with the SUM for:
Reporting the failure of the auto-tests
Reporting the cause of the AN start up
Downloading the AN files.
Launching the AN software.
The AN firmware uses the BSII for retrieving the IOM_CONF and for the
O&M dialog with the SUM.
9.5.2 Software
The ANCON/ANCC/AGCC software is used to maintain operation of the AN.
It supports the following functions:
Retrieving the IOM mapping from the BSII
Establishing a connection with the SUM on the IOM
Dialog with the SUM for:
Receiving commands (reset, restart, configuration)
Reporting the execution of commands
Reporting faults
Reporting an auto-restart.
Supervising the VSWR and reporting alarms
Supervising the LNA gain and reporting alarms
Self-supervision.
AN software uses the BSII to retrieve the IOM for the O&M dialog.
139 / 234
9 Antenna Network
9.6 Range Extension Kit

The basic advantage of a Range Extension Kit installation is to enhance the
capabilities of the 9100 BTS in terms of coverage. This is done by increasing the
size of the cell which significantly impacts the density of sites to be implemented
over the service area of GSM 900 networks. Other advantages are:
Range extension of road cell
Compensation of RF performance impairment due to antenna feeder
and ANx losses
Compensation of the eventual error of site location by radio network
planning.
The Range Extension Kit can be used with a wide variety of 9100 BTS indoor
and outdoor configurations in GSM 900 with the constraint of coupling only
one TRX/TRE to each antenna. Cross-polarized antennae can still be used
respecting this constraint. For practical reasons, configurations are limited to a
maximum of six TREs per BTS site assuming a 3x2 configuration.
The REK has been designed to minimize BTS and system impacts. The BTS
has no knowledge of the REK presence and is not involved in its configuration.
Configuration of the REK is reduced to manual attenuator setting at installation.
Supervision is minimal. It only involves external alarms to the BTS and there is
no recovery mechanism. The system impact concerns the handling of these
new external alarms at OMC-R level.
The REK is composed of two modules:
A Masthead Amplification Box
A Power Distribution Unit.
140 / 234
9 Antenna Network
9.6.1 Masthead Amplification Box

The Masthead Amplification Box is a bi-directional amplifier for one antenna
port. It is designed for outdoor installation on a tubular mounted support
below the antenna.
The principle functional entities contained in the MAB are described in the
following table.
Functions
Description
Circulator
The circulator routes the TX signal coming from the antenna cable to the TX power
amplifier and the output signal of the LNA to the antenna cable.
Together with the output duplexer it has to prevent the masthead equipment from
self-oscillating.
Another function is to prevent the receive amplifier from generating intermodulation by
reversely injected TX signals.
TX Power
Amplifier
The amplifier is made of one class A and two class AB stages. The output stage is a
quadrature to improve the reliability and manufacturability of the design.
To adapt the amplifier to the different BTS types and antenna cable losses, a variable
attenuator in front of the amplifier is available. The attenuator can be adjusted
manually.
A thermal protection/shut-down circuitry is incorporated in order to prevent the
amplifier from damage in case of too high temperature inside the MAB.
RX Low Noise
Amplifier
The receiver amplifier is a balanced two-stage design, each arm containing two
standard LNAs.
A variable attenuator in front of the amplifier is available. It can be adjusted manually.
Temperature compensation is provided through a passive temperature variable
attenuator on the amplifier output.
Duplexer
The output duplexer is located at the antenna port and has to prevent the RX path
from being interfered with by the own TX signals and to suppress the TX noise in
the RX band.
A further function is the attenuation of TX harmonics if necessary.
BIAS T and
Lightning
Protection
This circuit is located at both ends of each antenna cable, i.e. inside the MAB and
PDU. The bias circuit is used for remote DC feeding and alarm signalling. It includes a
lightning protection.
DC Power
Regulation
A DC regulator is introduced to avoid gain fluctuations of the transmit power amplifier

and the receive LNA. The amplifiers are DC fed via the feeder cable which introduces
up to 3 V of voltage drop (depending on the cable length and DC current).
Alarm Circuitry
Two alarms per TRX function are provided, one fatal and one non-fatal.
The fatal alarm is raised in case of a fatal failure (e.g. power amplifier out of order).
The non-fatal alarm is raised in case of a non-fatal failure (e.g. acceptable
performance degradation).
The signalling from the MAB to the PDU is done via the corresponding antenna cable.
Table 49: MAB, Principal Functional Entities
141 / 234
9 Antenna Network
9.6.2 Power Distribution Unit

The Power Distribution Unit provides the power supply and alarm interface
for two Masthead Amplification Boxes. It is located at the BTS site, either
wall-mounted close to the BTS in case of an indoor site or integrated inside the
BTS cabinet in case of an outdoor BTS.
The principle functional entities contained in the PDU are described in the
following table.
Functions
Description
Power Distribution
Unit
The PDU includes two separate DC/DC converters, each providing one MAB with
DC power.
BIAS T and
Lightning
Protection
There is one BIAS T per feeder cable. It is used to DC feed the corresponding MAB
and to extract the alarms from the MAB. It includes a lightning protection to protect
the BTS.
Supervision and
Alarm Circuitry
One fatal PDU alarm per TRX function is provided, if the power supply and supervision
circuit detects a defective DC/DC converter.
The PDU collects the fatal alarms of the MAB and PDU for TRX1 and TRX2.
Non-fatal MAB alarms of TRX1 and TRX2 are grouped.
LEDs
LEDs are provided on the front panel of the PDU to indicate the DC input status, MAB
alarms (fatal/non-fatal) and PDU alarms (fatal).
Reset Buttons
During the installation process, one or more red LEDs can be activated. In this case,
resetting the PDU is required.
Table 50: PDU, Principal Functional Entities
142 / 234
9 Antenna Network
9.7 Tower Mounted Amplifier

The Tower Mounted Amplifier is used to increase the energy level received
by the 9100 BTS from the mobile.
A significant part of the benefits brought by the outstanding sensitivity of the
9100 BTS can be lost if the losses incurred by signals along the feeder cable
between the receiving antenna and the antenna coupling module (ANxx) are
too high. In fact, the noise factor of the system is degraded by an amount
depending on the feeder loss.
The basic idea of tower-mounted amplification is to implement a low-noise
amplifier as close as possible to the antenna, so as to compensate for all losses
incurred by received signals. The TMA solution can be used in GSM 900, GSM
1800 or GSM 1900 indoor and outdoor configurations.
For TMA usage two solutions are available:
Tower Mounted Amplifier with external solution
Tower Mounted Amplifier with AGC support.
9.7.1 Tower Mounted Amplifier with External Solution

Installation of a Tower Mounted Amplifier with external solution is composed
of three separate modules:
A Tower Mounted Amplifier
A BIAS T module
A Power Distribution Unit.
9.7.1.1 Tower Mounted Amplifier

The Tower Mounted Amplifier is designed for outdoor installation on a tubular
mounted support below the antenna. It is suited for GSM 900. GSM 1800,
and GSM 1900.
As the transmit and receive path are duplexed by the BTS onto the same
feeder, the TMA has two duplexers integrated to separate the transmit and
the receive path. The transmit signal is bypassed to the antenna, while the
receive signal is amplified by a low-noise amplifier. The gain of the low-noise
amplifier depends on the frequency band.
143 / 234
9 Antenna Network
There is no specific supervision and alarm circuit. The TMA is indirectly

monitored at the PDU by supervising the current supply of the TMA.
The principle functional entities contained in the TMA are described in the
following table.
Functions
Description
Input Duplexer
The input duplexer routes the TX signal coming from the antenna cable to a TX
signal filter and the output duplexer. It routes the output signal of the RX LNA
to the antenna cable.
Together with the output duplexer it has to prevent the masthead equipment
from self-oscillating.
Another function is to prevent the receive amplifier from generating
intermodulation by reversely injected TX signals.
RX Low Noise Amplifier
The TMA consists of an LNA for received signals with filters at both ends.
It has an integrated bypass in case of an amplifier failure.
Output Duplexer
The output duplexer is located at the antenna port and has to prevent the RX
path from being interfered by the own TX signals and to suppress the TX noise in
the RX band.
A further function is the attenuation of TX harmonics if necessary.
Integrated BIAS T and

Lightning Protection
This circuit is integrated in the TMA at the BTS connection side. It is the
counterpart of the separate BIAS T module which is placed near the BTS. The
integrated bias circuit is used as a DC separator for the amplifier energy supply. It
includes a lightning protection.
Table 51: TMA, Principal Functional Entities
9.7.1.2 BIAS T
The BIAS T is a separate module used for insertion of the DC voltage in the RF
antenna cable between the BTS and TMA to feed the amplifier of the TMA. It is
the counterpart of the integrated BIAS T inside the TMA. The separate BIAS
T is designed for indoor and outdoor installation. It can be combined with a
surge arrestor to protect the BTS.
144 / 234
9 Antenna Network
9.7.1.3 Power Distribution Unit

The Power Distribution Unit provides the power supply and alarm interface
for up to six tower-mounted amplifiers. It is located at the BTS site, either
wall-mounted close to the BTS in the case of an indoor site or integrated inside
the BTS cabinet in the case of an outdoor BTS.
The principle functional entities contained in the PDU are described in the
following table.
Functions
Description
Power Distribution Unit
The PDU includes three separate DC/DC converters, each providing two TMAs
with DC power.
Supervision and Alarm

Circuitry
An alarm indication informs the BTS if there is a:

Defective DC/DC converter
Malfunction of a tower-mounted amplifier
Connection error of the various cabling parts.
LEDs
There are three kind of LEDs:

Orange (1x), indicates the presence of main power
Green (3x), indicate the presence of secondary power, i.e., the PDU is OK.
Red (6x), indicate a failure of the corresponding tower-mounted amplifier or a
connection error of the various parts of the cabling.
Switches
A main power switch can be used to switch the main power on or off.
Additionally, six output channels can be switched on/off separately.
Reset Buttons
Each channel has a separate reset button to reset the corresponding red LED,
which may have been set during the switching-on procedure. The PDU is also
fitted with a main reset button to reset all channels used in a single action.
Table 52: PDU, Principal Functional Entities
145 / 234
9 Antenna Network
9.7.2 Tower Mounted Amplifier with AGC Support

9.7.2.1 Functions and Features
The TMA is designed to compensate the feeder losses which significantly
impacts the density of sites.
The BTS cabinet sited AGC is the front-end to the TMA. It provides the
intermediate RF stage between the TREs and the antenna.
The hardware (Bias T) for supplying an external TMA for the reception path
is integrated. If a TMA is used, the RF signaling is routed first to the TMA
and then to the antenna.
In the transmit path the bandpass filter to the antenna provides the following
features:
Suppression of spurious and noise signals from the out of band transmitter(s)
Suppression of intermodulation products
Rejection of transmitter harmonics
Isolation to the reception branch.
In the receive path, the incoming signal from the antenna:
Passes the RX ANT filter
Is amplified by the integrated LNA
Is fed to the receivers in the BTS.
The power for the two TMAs, provided by the AGC, can be switched on and off
by variable settings. Between others, the controller of the AGC is in charge of
supervision of the TMA supply power. This current supervision is done with
an Overcurrent Protection Circuit, which includes a current sense amplifier,
a comparator and an internal voltage reference. The current sense circuit
has a comparator with a latched output, it gives an over current alarm if the
current is higher than a pre-set limit.
For more details see the 9100 BTS Hardware Description.
146 / 234
9 Antenna Network
AGC Gain Tuning

The TMA RX Gain and the Feeder Loss setting values are used to tune the RF
input levels via the AGC gain to match the TMA behaviour.
The algorithm is as follows:
AGC Rx Gain = Total Rx Gain - (TMA Rx Gain - Feeder Loss - Jumper Loss)
TMA
TMA
Duplexer
Duplexer
Duplexer
Duplexer
Bias
Bias
Fixed
TMA Rx Gain
BTS
AGC
TRE
Bias
TRE
Bias
Adjustable
AGC Rx Gain
Feeder Cable Loss
AGC Power Supply,

Switching and
Supervision
Figure 25: TMA with AGC, Receive and Power Supply Principle
Settings
The TMA setting values are stored in the Remote Inventory memory of the
XIOB. In case of an outdoor cabinet it is located on the OUTC module, for
indoor it is located on the XIBM module.
If low and high threshold of each DC output setting is > 0 (null), then the
AGC power supply output to the TMA is switched on and the current value is
supervised. If a threshold is 0, the output to the TMA is switched off physically
and logically.
If setting values entered outside the valid range (0255), the LMT rejects
the input and shows this in an error window. There is no consistency check
of the values.
Supervision
The AGCPS measures the both DC currents to the TMA once per second.
The current values are polled periodically approximately each minute from the
147 / 234
9 Antenna Network
SUMA. The values can be seen on the SBL Module State for RA1 and
RA2 on BTS Terminal or OMC-R.
Note:
The current values are not supervised in the first second after TMA connection
and power up. Initial TMA power up causes a short high inrush current, which
is normal but higher than the high threshold.
Short Circuit Portection
As a protection for the AGCPS a short circuit supervision disables the TMA if
the current exceeds 300mA. In case of over-current (Short Circuit Alarm) the
hardware automatically switches off the power supply of the according TMA. If
the short circuit alarm appears, then a TMA recovery action is started. After the
detection of the short circuit alarm, the AGC starts a single shot timer with a
duration of 10 sec. When the timer expires, then the AGC tries permanently to
re-enable the TMA power by resetting the TMA short circuit alarm.
9.7.2.2 Typical Values for TMA Parameters

The value range is principally( 0255) (one byte).
Parameter
Details
TMA (DC) low threshold
(0255) mA
default: 70 mA for unknown TMA data
0 for switch OFF
TMA (DC) high threshold
(0200) mA
default: 200 mA for unknown TMA data
TX loss
default: 0
This value is not used in GSM
RX gain
Should be taken from data sheets.
Feeder loss
Should be taken from data sheets.

In case of jumper cable usage, a 0.5 dB
loss must be added.
The AGC allows an inrush current of 2 A per TMA during initial power ON.
148 / 234
9 Antenna Network
9.8 GSM/UMTS Co-siting

A GSM cabinet and an UMTS cabinet can be installed at the same site.
Normally all antenna feeder cables between antennae (A and B) and BTSs
have to be installed separately for GSM and UMTS.
With the help of external diplexer filters at both ends of the feeder cables, the
GSM (850/900/1800) band and UMTS band can be decoupled in order to use
the same feeder cable for both services.
The base station feeder cable of the GSM part and the UMTS part are
connected to the according BTS ports of the diplexer. Both signals pass
separate bandpath filters of the diplexer. Then they are combined and
commonly available at the antenna connector of the diplexer.
The UMTS branch is additionally equipped with a BIAS circuit. This BIAS circuit
allows the DC power supply (12 VDC) of a TMA using the RF feeder cable. The
appropriate PDU is part of the UMTS ANRU module.
The GSM part of the diplexer is decoupled from the UMTS BIAS circuit part.
If both branches (GSM and UMTS) are equipped with a TMA, this external
diplexer cannot be used. Then all the necessary equipment of a TMA (including
feeders) have to be installed twice.
149 / 234
9 Antenna Network
150 / 234
10 Station Unit Module

This chapter provides a description of the SUM/MSUM. It provides information
about the SUM/MSUM:
Functions
External interfaces
Modules
151 / 234
10.1 Introduction to the Station Unit Module

The main functions of the SUM/MSUM are:
Transmission
Handling the Abis link
Multiplexing TCH data and RSL/OML data between the Abis Interface
and BSII Interface
Supporting the Q1 link to the TSC.
Generation of clocks for all other BTS modules; either
Synchronization to an external clock reference (another BTS or from
the Abis link), or
Internal frequency generation using high precision OCXO.
Generation and distribution of Frame Number
Central OMU control
Provision and handling of internal and external interfaces
BSII Interface handling.
10.2 Station Unit Module Functions

The principal functions of the SUM/MSUM are shown in the following figure.
SUM/MSUM
XCLK
(SUM only)
Clock
Generation
and Synchro
nization
Abis
Trans
mission
MMI
O&M
XBCB
(SUM only)
Timing
RI
CLKI
BSII
BCB
Figure 26: SUM/MSUM Functions and Interfaces
152 / 234
The following table shows how the different SUM/MSUM functions, described
fully in Transmission Functions (Section 3) and O&M and Support Functions
(Section 6), are summarized in functional groups.
Functions
Transmission
Clock
O&M
Configuration Management:
Clock and Frame Number Generation and Synchronization
Frequency Hopping
Transmission - Abis link:
Provision and Handling of internal and External Interfaces
BSII Interface Handling
Central command control and handling

Configuration and initialization of TRE/MTRE and AN
software
Downloaded software replacement
Configuration parameter file management
Database maintenance
Hardware configuration management.
Fault Management:
Filtering of alarms
External alarm collection
Forwarding of alarms to the BSC for processing
Self-testing of the BTS
Translation of alarms to a GSM function-level format
Translation of high-level BSC commands.
Dedicated Alarm Handling
Electrical interface providing a loop-back

Clock recovery from the PCM link
Framer for control and synchronization of frames
64 kbit/s time slot switch maps time slots onto TCH.
Transmission - Multiplexing TCH, and RSL/OML data
Transmission - support of Q1 link
Table 53: Grouping of SUM/MSUM Functions
153 / 234
10.3 Station Module External Interfaces

The SUM/MSUM exchanges data with external entities through the links
described in the following table.
Abis Interfaces
The Abis Interface provides the Transmission function with a 2 MHz reference clock
from the BSC. Abis Interface 1 or 2 is used for TCH, RSL/OML signalling, Q1 and
ring control bits.
BSII
The BSII comprises two physical links at 2 Mbit/s. It is used to:

Route information received on the Abis link to the involved entities. For example,
RSL, TCH and OML routed to TRE/MTRE and O&M.
Internal O&M functions. Communication between O&M and other entities (for
example, TRE/MTRE and AN/MAN using IOM link.
CLKI
The CLKI provides the basic GSM clocks to all of the BTS modules. It consists of
two signals:
CLKI_CLK which is a 2.167 MHz clock
CLKI_FRM which is the GSM frame signal multiplexed with the frame number.
BCB
The BCB is used for:

Auto-identification and remote inventory functions
O&M functions to address entities that are not connected to the BSII or when
entities cannot be addressed on the BSII.
BTS Terminal
The BTS Terminal provides a local MMI for operator control of the BTS. The BTS
Terminal is also used to:
Handle local commands for the BTS
Monitor status and alarms of the BTS
Perform commissioning tests, such as calibrate the OCXO.
Refer to the BTS Terminal User Guide for more information about local operator control
of the 9100 BTS.
XCLK
(SUM only)
XCLK is used to synchronize the BTS with an external master clock. Alternatively, it
can provide a Master Clock to a slave BTS.
XBCB
(SUM only)
The XBCB is an external control bus used to control or supervise events. This bus is an
extension of the BCB. It can be used to perform external RI with a suitable inventory
tool at factory level.
Table 54: SUM / MSUM External Interfaces
10.4 Station Unit Module Boards

The functions of the SUM are all concentrated on the SUMX, SUMA or SUMP.
The MSUM functions are concentrated on the MSUM or MSUMA module.
154 / 234
10.5 Station Unit Module Software Implementation

The SUMP/MSUM use two microprocessors, the SUMA/SUMX/MSUMA only
one to run the software/firmware for the O&M and Transmission modules.
The SUM software is described in terms of functions.
10.5.1 O&M Function

The SUM software is the central node for the BTS O&M.
This means that the SUM software is in charge of the following O&M functions:
Downloading the BTS Master File, the SUM software, and the SUM SPF
Monitoring all modules within the BTS
Controlling all modules within the BTS
Interfacing between the BTS and the operator at the BSC or the BTS
Terminal.
The main functions of the SUM software are:
Dialog with the BSC or BTS Terminal for:
Downloading BTS files
Executing operator commands
Reporting faults detected inside the BTS.
Broadcasting the IOM mapping
Connection to other modules for:
Sending and controlling commands to the modules
Downloading the files to the modules
Retrieving faults.
Calculating and transmitting the BSII configuration to the Transmission
function.
Controlling the BCB as master for:
Managing all components which use the BCB
Detecting the live insertion/extraction of modules
Activating the BCB polling of the low-level alarms from the module
connected to the BCB
Setting the output ports, e.g., power supplies.
Supervision of the BCB and BSII internal busses
Self supervision.
155 / 234
The O&M software uses the following interfaces:

BSII which gives access to:
OML
IOM
IOM_CONF for the periodic IOM configuration broadcast.
BTS MMI for the dialog with the BTS Terminal.
BCB for ISL protocol conversion and physical layer control.
10.5.2 Transmission Function

The Transmission function controls the Abis link by performing management
and supervision, transmission and reception of data:
The Framer monitors conditions on the Abis link. These include frame and
multiframe synchronization, framing, and detection of alarms. The Framer is
polled by the Transmission processor and the Abis link status is stored for
use by other functions. The Framer can be configured to check for cyclic
redundancy check errors on the Abis link.
The Time Slot Switch handles the mapping of the 64 kbit/s time slot.
The main function of the BSII Switch is to choose which of the two BSII
internal interfaces is used for O&M data distribution and for the TCHs.
10.5.3 Clock Function

The Clock function controls the distribution of clocks within the BTS (for the
TRE/MTRE and AN modules):
The Master Frequency Generator synchronizes the output of a voltage
controlled oscillator in the clock function with the external reference supplied
from the Abis link. This output is now used as the system master clock.
The CLKI is responsible for the distribution of the system master clock for
the TRE/MTRE and AN. It also distributes the Frame Clock and the Frame
Number to these modules.
156 / 234
11 Transceiver Equipment
This chapter provides a description of the TRE /MTRE. It provides information
about the TRE/MTRE:
Functional entities
External interfaces
Modules
157 / 234
11.1 Introduction to Transceiver Equipment

The main functions of the TRE/MTRE are:
Telecommunications Management
O&M Management.
11.2 Transceiver Equipment Functional Entities

The following figure shows the principal functional entities of the TRE/MTRE
together with their internal and external interfaces.
MMI
BCB
RI
Frequency
Hopping
SCP
CLKI
CGU
Transmitter
ECPL
CUI
Power
Amplifier
RFI TX
To
AN/MAN
MBED
RF Loop
DEM
DEC
BSII
MUX
BED
CUL
Receiver
RFI RX
From
AN/MAN
TXP
ENC
Frequency
Hopping
ENCT
Figure 27: TRE/MTRE Functional Entities and Interfaces
158 / 234
The following figure shows the principal functional entities of the Twin TRE
together with their internal and external interfaces.
Frequency
Hopping
Modulator/
Filter / Buffer
for GSM, EDGE,
enh. EDGE
Transmitter
FLASH
SDRAM
Level & Bias

CUI
Power
Amplifier
Ramping
CPLD
RFI TX
To AN
SDRAM
Receiver
SCP
RFI RX
From AN
SYS
TX Synth.
Module
TXP
ENC
ECPL
HPI
RX Synth.
Module
DSP1
Frequency
Hopping
DEM
RFI RX
CLKI
Receiver
BSII
HFFI
FHL
To/from LALE
From AN
IQ
MUX
RFI TX
CUI
FPGA
SYS
Power
Amplifier
To AN
DEM
HPI
DSP2
DEM ctrl.
Transmitter
DEC
FPGA
Frequency
Hopping
SDRAM
Figure 28: Twin TRE Functional Entities and Interfaces
159 / 234
The following tables show how the TRE/MTRE functions, described in

Telecommunication Functions - Baseband (Section 4) and Telecommunication
Functions - RF (Section 5) map onto the TRE/MTRE functional entities. In
some cases, a single function can be split between more than one entity.
Functions
SCP
MBED
DEC
DEM
ENCT
CUL
CGU
Configuration
/Initialization
Software
Replacement
Rate Adaptation
Channel Encoding
and Decoding
Interleaving/
De-interleaving
Encryption/
Decryption
Demodulation
Antenna Diversity
Radio Link Recovery
Radio Resource
Indication
Paging
DTX
DRX
Quality
Measurement
Power Control
Clock Distribution
Protocol
Management
Radio Channel
Management
Transcoder Time
Alignment
Frequency Hopping
160 / 234
Functions
SCP
MBED
DEC
DEM
ENCT
CUL
CGU
Channel Selection
and Conversion
Digital Preprocessing
Control the Status of the RF Hardware
Handle Control and

Alarm Processing
Select High/Low
Gain Path on Uplink
Table 55: Distribution of TRE/MTRE Functions between TRE/MTRE Functional Entities (1)
Functions
SCP
DSP1
DSP2
FPGA
CPLD
CGU
Configuration
/Initialization
Rate Adaptation
Channel Encoding and

Decoding
Interleaving/
De-interleaving
Encryption/ Decryption
Demodulation
Antenna Diversity
Radio Link Recovery
Radio Resource
Indication
Paging
DTX
DRX
Quality Measurement
Power Control
161 / 234
Functions
SCP
DSP1
DSP2
FPGA
CPLD
CGU
Clock Distribution
Protocol Management
Radio Channel
Management
Transcoder Time
Alignment
Frequency Hopping
Channel Selection and

Conversion
Digital Pre- processing
Control the Status of

the RF Hardware
Handle Control and

Alarm Processing
Select High/Low Gain

Path on Uplink
Table 56: Distribution of Twin TRE Functions between Twin TRE Functional Entities (1)
Functions
Frequency
Hopping
Transmitter
Receiver
RF Loop
RF Power
Amplifier
Frequency Hopping
RF Carrier
Generation
GMSK Modulation
Up-conversion
Power Amplification
and Power Control
Power Coupling
and Detection
Signal Amplification -
162 / 234
Functions
Frequency
Hopping
Transmitter
Receiver
RF Loop
RF Power
Amplifier
A-D Conversion
Program the
Frequency
Synthesizers
Table 57: Distribution of TRE/MTRE/Twin TRE Functions between TRE/MTRE/Twin TRE Functional Entities
(2)
163 / 234
The principal functional entities contained in the TRE/MTRE are described in

This Entity...
Does this...
SCP
Handles the protocol management for Layers 2 and 3, which are used to implement
O&M functions. See SCP Software Implementation (Section 11.5.1) for detailed
information on the SCP functions.
MBED/DSP1
Multiplexes/demultiplexes. See Transceiver Equipment Software Implementation

(Section 11.5) for detailed information on the MBED functions.
DEC/DSP2
Processes the uplink information carried by one time slot of the TDMA frame. See
DEM, RXP and DEC (Section 11.5.3) for detailed information on the DEC functions.
CUL/CPLD
Interfaces the ENCT to the analog functions. See CUL (Section 11.5.5) for detailed
information on the CUL functions.
DEM/DSP1/DSP2 Processes the complex samples of the digital baseband corresponding to eight
sequential time slots within a TDMA frame. See DEM, RXP and DEC (Section 11.5.3)
for detailed information on the DEM functions.
ENCT/DSP1
Processes baseband data for the downlink. The ENCT includes the ENC and TXP
functions. For detailed information on the ENCT, see
CGU
All BTS clocks are derived from a master reference frequency. The master frequency
is generated in the Clock functions. The Timing functions in the CGU perform the
following operations in the BTS.
Timing Signal Generation: The CGU derives all BTS clocks from the master
frequency generator.
Clock Distribution: The synchronization clocks are distributed to the TRE/MTRE
analog functions.
Frequency
Hopping
Frequency hopping is performed by the hopping synthesizers. These synthesizers

generate the RF frequencies for the transmitter.
Transmitter
The transmitter combines GMSK/8-PSK modulation and Up-conversion functions. The

modulator transforms the incoming digital data stream into two baseband signals: I and
Q. These signals are transformed into the RF band by the Up-converter.
Receiver
The analog receivers perform the following functions:

Low noise amplification
Down-conversion
IF filtering
IQ demodulation
Baseband filtering.
RF Loop
The RF Loop provides an analog test loop between the transmitter and receivers. It
performs analog self-tests, mainly for start-up test purposes.
The RF Loop is not available on TRAGE/TAGHE/TRADE/TADHE/TGTxx.
RF Power
Amplifier
The RF Power Amplifier takes the RF signals from the Transmitter and isolates,
regulates and amplifies them before passing them to the AN/MAN module.
Table 58: Principal Functional Entities of the TRE/MTRE/TWIN TRE
164 / 234
11.3 Transceiver Equipment External Interfaces

The TRE/MTRE/Twin TRE exchanges data with external entities through the
links described in the following table.
Interface
Description
RFI
The Radio Frequency Interface connects the TRE/MTREs to the AN/MAN modules. Each
TRE/MTRE/TWIN TREmodule has its own RFI which consists of three lines, one transmitter
and two receivers, or two lines for the 9110 Micro BTS/9110-E Micro BTS fitted with
a MAN1/MANM and no antenna diversity. The TWIN TRE is considered as 2 x TREs
containing three lines for each module.
CLKI
The CKLI distributes the timing reference for the TRE/MTRE/TWIN TRE. The clocks are
supplied by the TRANS/CLOCK.
BSII
The BSII is used to transfer O&M messages from the SUM to the TRE/MTRE/TWIN TREs.
These IOM messages are used for software download, transfer of configuration data, error
and alarm collection, etc. The BSII also allows the SUM/SUMA to broadcast IOM_CONF
information to the TRE/MTRE/TWIN TREs. For the 9110 Micro BTS/9110-E Micro BTS, it
also provides an interconnection between the 9110 Micro BTS/9110-E Micro BTS entities
when operating in a master/slave configuration with more than two TREs.
BCB
The BCB is used to exchange information and data between the SUM and the TRE/MTREs.
The BCB allows the SUM to perform auto identification and remote inventory functions. For
the 9110 Micro BTS/9110-E Micro BTS only, it also provides an interconnection between the
9110 Micro BTS/9110-E Micro BTS entities when operating in a master/slave configuration
with more than two TREs.
MMI
The MMI provides an interface to the TRE/MTRE/TWIN TRE for factory test purposes only.
Table 59: TRE/MTRE/Twin TRE External Interfaces
165 / 234
11.4 Transceiver Equipment Modules

The TRE/MTRE/TWIN TRE functional units are contained on three boards
located within the TRE/MTRE/TWIN TRE module. There are a number of types
of TRE/MTRE module for GSM 850, GSM 900, GSM 1800 and GSM 1900
operation for the BTS, as shown in the following table.
BTS
GSM 850
9100
TRAL
TGT08
9110 Micro
BTS
9110-E
Micro BTS
MTREDAL
GSM 900
GSM 1800
GSM 1900
TRGM
TRDM
TRPM
TRAG
TRAD
TRAP
TRAGE
TRADE
TAGH
TADH, TRDH
TAGHE
TADHE
TGT09
TGT18
MTRGM
MTRDM
MTREDAG
MTREDAD
MTREDAP
Table 60: TRE/MTRE/TWIN TRE Variants
166 / 234
11.5 Transceiver Equipment Software Implementation

The TRE/MTRE software provides control and baseband data processing,
corresponding to Layers 1 to 3 in the GSM communications model.
The following figure shows the TRE/MTRE logical subsystem.
MMI
BCB
BCBT
Push Button
SCP
ECPL
ENCT
BBI
BBI
TCH
ENC
BBI
TXP
BSII
CUI
BED
MUX
CUL
TCH
BBI
DEC
BBI
BBI
DEM
RXP
MBED
FHL CLKI
Figure 29: TRE/MTRE Logical Subsystem

The TRE/MTRE logical subsystem consists of several modules. Note that
although the BCBT is not a software module, a description of its functions is
included for completeness. Refer to the appropriate section for information
about each module, as well as the BCBT.
167 / 234
11.5.1 SCP Software Implementation

The SCP firmware/software manages the O&M, synchronization and
telecommunication functions of the TRE/MTRE.
The O&M functions perform:
Configuration management
Fault management.
Refer to section 11.5.1.1 for more information on the O&M functions.
The synchronization function controls the Frame Number distribution to the
Layer 1 entities.
The telecommunication functions control the:
Radio protocol between the network and the Mobile Station
Transmission protocol between the TRE/MTRE and BSC.
Refer to section 11.5.1.2 for more information on the telecommunications
functions.
The SCP handles the protocol management for Layers 2 and 3, which are used
to implement the following O&M functions:
Radio channel management
Power control
Quality measurements
Paging
Maintenance
Time synchronization.
The SCP also manages the following:
Layer 2 LAPDm
The LAPDm operates over the BTS-to-Mobile Station link. It is responsible
for providing error-free, point-to-point communication using LAPDm frames
(GSM rec. 04.06).
At Layer 2, LAPDm provides services for the following radio channels:
SDCCH
FACCH
SACCH.
On these channels, LAPDm performs connection establishment, data
transfer and connection release. Services to other radio channels are
handled at Layer 3 to avoid excessive transfers between Layers 2 and 3.
LAPDm thus carries information between Layer entities, via the Air Interface.
Layer 2 LAPD
The LAPD protocol operates over the Abis link between the BTS and BSC
(GSM rec. 04.06). LAPD is responsible for ensuring error-free, point-to-point
communication between the BTS and the BSC. It also carries information
between Layer 3 entities via the subscriber network interface.
168 / 234
11.5.1.1 O&M Functions

The SCP O&M functions are implemented in firmware and software.
The SCP firmware:
Performs TRE/MTRE auto-tests
Retrieves the IOM mapping from the BSII
Establishes the connection with the SUM using the IOM
Dialogs with the SUM to:
Report the TRE/MTRE auto-tests in the case of failure
Report the cause of the TRE/MTRE start up
Download the TRE/MTRE files.
Launches the TRE/MTRE software.
The SCP software:
Manages configuration parameters
Manages reconfiguration parameters
Verifies software integrity
Controls the TRE/MTRE mode of operation
Supervises and manages faults
Supervises the LAPD link
Supervises processor overload
Performs RACH load measurements.
Supervises external interfaces (fault management)
Supervises Layer 1 entities (hardware and software failure)
Manages the exchange of messages between the SCP and other
TRE/MTRE entities.
169 / 234
11.5.1.2 Telecommunications Functions

The SCP telecommunication functions are only implemented in the software.
This software controls the radio protocol between the network and the Mobile
Station. It also controls the transmission protocol between the TRE/MTRE
and the BSC. The telecommunications software:
Handles the LAPD protocol
Handles the LAPDm protocol
Handles the Layer 3 protocol
Processes Telecommunications configuration messages
Manages Radio Channel
Performs the error handling of the telecommunications software
Manages the initialization of the Layer 1 entities
Manages the configuration of the Layer 1 entities
Manages the synchronization (frame number)
Manages the multiframe configuration
Routes the telecommunications messages.
11.5.2 ENCT
The ENCT is in charge of terrestrial link and radio channel functions:
On the terrestrial link side, the ENCT controls:
Rate adaptation
TRAU frames management
Transcoder time alignment.
On the radio channel side, the ENCT controls:
FHL calculation of time slot and link number
Control of the analog part including transmitter and receiver parts
FHL interface management
Encryption control
Forward error correction and encoding.
These functions are implemented in the ENC and the TXP and are described in
more detail in the following sections.
170 / 234
11.5.2.1 ENC
The ENC is in charge of the majority of the BTS downlink baseband functions.
These functions are given below. Downlink baseband functions not mentioned
here are performed by the MBED.
The ENC software performs the following functions:
Control of the TCH interface with the MBED
Rate adaptation
Control of the remote transcoder
Control of the interface with the channel encoding function
Channel encoding
FACCH bit stealing
Burst building
Multiframe building
Burst control
TDMA frame multiplexing.
11.5.2.2 TXP
The functions of the TXP are:
Initialization of the TRE/MTRE analog part:
Synthesizer initialization
Minimization of Amplitude Modulation effects
Control of amplifier offset bias adjustment.
Online control of the TRE/MTRE analog functions, performed on behalf of
the ENC:
Transceiver power ramping
Transceiver power control
VSWR supervision
Temperature supervision
Synthesizer programming and frequency hopping
Synthesizer lock detect supervision
Receiver attenuator setting
RF Loop (not available on TRAGE/TAGHE/TRADE/TADHE).
171 / 234
11.5.3 DEM, RXP and DEC

The DEM, RXP and DEC each require dedicated software. However, as these
blocks are structurally similar, a brief introduction is given for each.
11.5.3.1 DEM Functions

The DEM is in charge of collecting the receiver measurements e.g., TOA
estimation and SNR estimation. It also takes in-band control information from
the DEC and performs pre-processing, channel demodulation and equalization
on the received signal.
Functionally, the application software is separated into two parts:
DEM software
RXP software.
The RXP software is described separately in the next section.
The DEM processes the physical channels received on the uplink, and passes
the processed data to the DEC. The data is received as complex samples
from the ADC in the analog functions.
The DEM performs the following functions for each channel:
GMSK demodulation
Receiver-level calculations
High and low gain path selection
DC offset calculation and correction
Frequency translation
Carrier frequency offset compensation, estimation, filtering
Channel impulse response estimation
TOA estimation
Matched filtering
Equalization based on estimated channel impulse
Soft decision
SNR estimation
Channel state weighting
Testing.
There is also a Decryption function, which occurs just before the data is passed
to the DEC. This is performed in the MBED, configured by the DEM software.
The SCP uses the ID_CHC messages to send the uplink decryption keys, the
decryption flag and the algorithm type flag to the DEM. The DEM extracts this
information, adds the frame number, and sends the combined data to the
MBED. Only normal bursts are decrypted.
172 / 234
11.5.3.2 RXP Functions

The RXP processes the physical channels received on the uplink, and passes
the processed data to the DEM. The data is received from the A-D converter as
complex samples.
The RXP functions are performed for each channel.
This function...
Does this...
RF Data Input
As the A-D converter finishes each conversion, it sends an interrupt to the

processor. The processor then transfers the data from the A-D converter
to an internal memory buffer.
Received Data Processing
The data read from the A-D converter for each time slot is pre-processed
to allow its subsequent demodulation. Data output for each time slot
occurs at the beginning of the next time slot. The data output for each time
slot is checked for inconsistencies that can indicate an error.
Receive Level Computation

and High/Low Gain Selection
Four demodulation paths are provided by the analog functions. Two for
each of the pair of receiver signals obtained through antenna diversity.
Each receiver signal contains a high and a low gain path that are
pre-processed. If the low gain path has a sufficiently high RF power value,
then it is demodulated. Otherwise, if the low gain path is too low, the high
gain path is demodulated.
DC Offset Computation and

Compensation
The RXP controls the application of DC offset to the pre-amplified I and

Q signals. AM measurements from the analog functions are used by the
RXP to calculate the DC of the I and Q signals. These values are passed
to an analog subtraction unit which balances the amplitude of the I and Q
signals.
Frequency Translation
To simplify the demodulation of the received signals, pre-processing

is performed. This involves multiplying the A-D samples by a complex
coefficient before passing them to the DEM.
Fault Checking
Ongoing checks are performed for each time slot during operation. These
tests verify that data is sent to the uplink BSII, and that data is received
from the analog part of the receiver. If these tests fail, or if no interrupts
are detected, an alarm is sent to the SCP.
Table 61: RXP Functions
11.5.3.3 DEC Functions

The DEC is in charge of antenna diversity, speech, data; and signaling, and
the terrestrial link. For the DEM, the DEC performs in-band control and
measurements pre-processing.
The DEC reassembles logical channels from the bursts of data received
from the DEM.
It identifies bursts using channel configuration messages received from the
SCP. The burst process is therefore controlled in real-time, using a special
operating system.
173 / 234
During burst processing, the DEC performs the following functions:

De-interleaving
Burst processing control
TOA filtering
Received signal level filtering
Decryption
Channel observations (interference, RSSI, SNR)
RACH load measurements.
The reassembled blocks are then processed using the following functions:
Convolutional decoding
Block decoding
Bit reordering
Deciphering of soft decision bits
Hard decisions of uncoded bits
Received signal quality estimation
Rate adaptation
Building of output frames
Filtering of Layer 2 fill frames
Ciphering state initialization for signalling frames
Indication of valid traffic frame decoding.
The data is then routed towards the BSC.
In addition, the DEC performs the following functions:
Handover management
Support of RF Loop Test
DEM configuration
BER measurements.
The DEC produces two parameters for signal quality. These relate to
measurements made during a SACCH multiframe over a full set of TDMA
frames, and a subset of TDMA frames, respectively. These two parameters
are sent to the SCP.
174 / 234
11.5.4 MBED
The MBED performs the MUX and BED functions. It multiplexes/demultiplexes
TRAU frames on the BSII. It also performs decryption/encryption key extraction
and generation of the decryption/encryption masks. The MBED interfaces the
uplink and downlink TCH and the LAPD RSL to the Abis Interface. This is done
via the BSII and the SUM/MSUM. Since these are transparent to the MBED,
the MBED effectively provides a direct mapping of the data streams onto
the relevant Abis channels.
The MBED is in charge of the following functions:
CKLI Interface management including Frame Number reception
Multiplexing the ENCT and DEC external interfaces to the BSII
Generation of synchronization signals for the SCP
Timing control generation for the baseband processing
Decryption key extraction and generation of decryption mask
Encryption key extraction and generation of encryption mask.
11.5.5 CUL
The CUL interfaces the ENCT to the analog functions. The CUL, together with
the ENCT, performs supervision and control of the following functions:
Synchronization functions (the timing of all analog functions):
Power ramping control and synchronization
Synthesizer programming and synchronization
Supervision of lock detects, temperature and power
Power Amplifier calibration
Synchronization of the baseband data to the GMSK Modulator.
Synchronization and control functions:
Synchronization and control of Receiver attenuators
Synchronization and control of Receiver DC offset
Synchronization of IQ sampling.
175 / 234
11.5.6 BCBT
The BCBT Communication module handles communication with the SUM via
the BCB.
The BCBT is in charge of handling:
Access to the RI EEPROM and obtaining the TRE/MTREs physical address
TRE/MTRE power supply control
RF cabling detection to determine the RF interconnection between TRE and
ANs. RF supervision is performed when the 9100 BTS is operational. It
detects an interruption in the RF path.
Hardware protection for SCP Flash-EPROM
Routing of low level TRE/MTRE alarms and status to the SUM
JTAG access to SCP processor and memory to allow firmware downloading.
11.6 Transceiver Equipment Power Management

This section describes the transceiver equipment output power management
when power balancing feature is activated and for unbalanced configurations.
11.6.1 Transceiver Equipment Power Balancing

This section describes the transceiver equipment power balancing in a sector.
The TX power attenuation is used to take care of unbalanced hardware
configurations for 9100 BTSs. In case of 9110 Micro BTS and 9110-E Micro
BTSs TX power attenuation is 0 dB so there is no need for power balancing.
A power balancing for the GMSK power of the TREs in the sector is made.
For the 8PSK power of the TREs in the sector a power balancing is made in
a best effort way. Three steps must be made for this and these steps are
11.6.1.1 Determine the Attenuation Between TRE Modules and Antenna Connector
Determine the attenuation between TRE modules and antenna connector by
taking into account the attenuations due to coupling stages and cabling:
As the OMU/SUM can not detect the TRE- ANY connection, the attenuation
to give to a TRE can be deduced using a rule based on the number of ANY
"assumed to be connected to a TRE.
Two types of unbalanced configurations are used:
Mixed configuration normal power TRE and high power TRE. In such
configuration, the normal power and high power do not have the same
power and do not have the same number of ANY stages between TRE and
AN (there is one ANY less in normal power TRE)
Unbalanced configuration with different AN. In such configuration, the TRE
connected to different number of ANY are connected to different AN.
11.6.1.2 Balance the GMSK Power of the TREs in a Sector

The attenuation to be given to the TRE (for GMSK) is based on the following
rules:
176 / 234
Calculate the TX Power of each TRE at antenna output (or AN input) taking
into account the TRX power and the different losses (cables, ANY and AN)
Search for the TRE which has the lowest output power at this reference point
Attenuate all other TRE with the power difference to this TRE.
In order to take into account the case of a cell split over two BTSs, the CDM
indicates per sector and frequency band the Maximum TX power requested
in order to have the same TX power for all TRE belonging to the same cell
among the two BTSs.
There are two cases:
The requested Maximum TX power is lower than the TX power calculated
above, then a supplementary attenuation is added in order that the final TX
power of the TRE is equal to the Maximum TX power
The requested Maximum TX power is equal or higher than the TX power
calculated above, then this requested Maximum TX power is ignored and an
alarm is generated in order to notify the system.
11.6.1.3 Balance the 8PSK Power of the TREs in the Sector

The 8PSK output power of a TRE is generally lower than the GMSK power.
Once the GMSK power in a sector is balanced, the 8PSK power is balanced in
a best effort way. For each TRE, the 8PSK power is reduced to the GMSK
sector power, if the value is higher. For modules with 8PSK power below GMSK
sector power, no attenuation is applied. In order to notify the system, about
possible differences between GMSK and 8PSK power, this value, called delta
power is provided to the TRE that reports it towards the MFS for this purpose.
The BSC determines this delta power internally for its own use.
For splitted cells, the 8PSK power is aligned to the Maximum TX Power if
it is higher, otherwise Maximum TX Power is ignored. The delta power
reporting takes into account the balancing made between the two semi-sectors
of a splitted cell.
11.6.2 Unbalanced Configurations

In order to take benefit of the wide TRE portfolio and capacities a new feature
is implemented to support unbalanced configurations on the same antenna
network. Furthermore for three TRXs per AN configuration to permit the usage
of two TRXs in combining mode on the first antenna path and to connect in
by-pass mode the third TRX, on the second antenna path thus resulting in a
sort of concentric cell configuration.
The principle of the feature is to define a specific concentric cell in which the
output power balancing is performed on a zone basis instead of on the sector
basis. The major benefit of the feature is in rural regions as this will allow
less expensive BTS for a certain coverage. When the feature is activated on
a concentric cell, the BSS system ensures that the more powerful TREs are
mapped on TRX configured on the outer zone, and the less powerful ones, on
the TRX configured on the inner zone.
Activating this feature brings as benefits:
Easier introduction of high power GMSK output power for better indoor
coverage and without need to have the whole sector equipped with TRX
high power
177 / 234
Upgrade of two TRXs / cell in by-pass mode towards three TRXs without
impact on coverage and without need of low loss configuration.
The existing current mechanism described in Transceiver Equipment Power
Balancing (Section 11.6.1) is kept if the feature not activated.
178 / 234
12 BTS Start Up and Initialization

This chapter describes the BTS start-up procedure and the initialization that
follows.
After introducing the sequence of events that occur, it describes the following
processes:
SUM/MSUM Start Up
Software Download
Software Initialization.
179 / 234
12.1 Introduction
When the BTS is powered up, reset or restarted, a fixed sequence of events
occurs.
There are several different scenarios and the one that is chosen depends on:
Whether or not the BTS has been reset or restarted
The reason that this reset/restart has occurred.
The main differences between the various reset/restart scenarios are:
Whether or not the BTS downloads the module software
How the software is activated after it has been downloaded.
The reasons for a reset/restart are:
BTS/SUM/MSUM Power-up
Restart BTS (SBL)
Restart OMU (SBL)
OMU auto-restart with/without OMU CPF replacement
Reset BTS
Reset OMU
OMU auto-reset.
180 / 234
Software Interaction Scenario (Section 15) contains diagrams showing the

sequences for all of the BTS start-up scenarios. The following figure gives
an overview of all BTS start-up scenarios and presents the internal states of
the BTS O&M.
Startup Reason
(1)
SUM bootstrap
BTS/OMU started
Download SUM SW
Start SUM SW
Start Up,
Reset or Restart
Reason
(1), (6), (7), (8)
(2)
Download
BTS files
OMU CPF
Restart
BTS
(3)
(4)
Reconfigure
BTS
SW Activate
(5)
Increment
autorestart
counter
Download
OMU CPF
BTS context
recovery
Reconfigure
BTS
Report Reason for Start Up,

Reset, or Restart
(fault, command)
Reset/Restart Reason
(2), (3), (4), (5)
BTS
OPERATIONAL
Reset/Restart Reason
(6), (7), (8)
Start Up, Reset or Restart Reason
Start Up, Reset or Restart Reason
1
2
3
4
5
6
7
8
BTS/SUM/MSUM Powerup
Restart BTS
Restart OMU
OMU autorestart without OMU CPF replacement
OMU autorestart with OMU CPF replacement

Reset BTS
Reset OMU
OMU autoreset
Figure 30: Overview of all BTS Start-up Scenarios

The different scenarios share a number of common actions. To avoid excessive
duplication, the description is for the BTS power-up sequence as described in
the SUM/MSUM Start Up (Section 12.2). This sequence contains the majority
of the actions performed in any of the scenarios shown in Chapter 15.
181 / 234
12.2 SUM/MSUM Start Up

After power-up or a reset, the following actions are performed on the
SUM/MSUM.
For the 9110 Micro BTS/9110-E Micro BTS, only the MSUM of the master 9110
Micro BTS/9110-E Micro BTS is powered up. The MSUM of the slave 9110
Micro BTS/9110-E Micro BTSs remain deactivated.
1. SUM Auto-test and Bootstrap
The SUM software is activated and performs an auto-test, then bootstrap
procedures are run on the SUM. The bootstrap procedures contain the
operating system and interface control code.
2. Abis Configuration Exchange
The O&M function requests the Abis configuration from the transmission
function in order to establish a connection with the BSC. The information
required by the O&M function is the position of the OML, RSL and TCHs in
the Abis datastream.
The SUM software obtains the Abis configuration and stores it in non-volatile
memory. The configuration is obtained from one of two sources:
The BSC via the Abis Q1 time slot
The BTS Terminal via the MMI.
3. BSII Configuration Exchange
The SUM software calculates the BSII configuration after each auto-reset or
power up. The OML, RSL and TCHs are assigned the same position on the
BSII as they occupy on the Abis.
4. BSC Connection
The SUM is now able to establish the LAPD OML connection with the BSC.
This link is between the BSC and the BIE.
5. BTS/OMU Started Message
The SUM software sends an OMU Started message to the BSC. The
message contains the reason for the BTS reset/restart. The BSC responds
with an acknowledgement message.
The BSC then begins the software download to the SUM over the LAPD
OML connection.
182 / 234
12.3 Software Download

The BTS software download comprises:
BTS Master File
SUM Software Download
Other BTS Software Packages Download
Management of Software Versions.
Each of these is described in the following sections.
12.3.1 BTS Master File

The BTS software is transferred to the SUM in two parts. First, the BSC sends
the BTS Master File, which contains a list of all the files needed by the BTS.
These files are collectively called the BTS Software Package.
Note that the Master File is stored in RAM. Only one version of this file is ever
present in the BTS. Therefore it is not stored in Flash-EPROM.
12.3.2 SUM Software Download

The second part of the software transfer is the transmission of the BTS
Software Package. The SUM software compares the list of files contained in
the BTS Master File with the files contained in the SUM Flash-EPROM. The
result of this comparison is a list of files that need to be downloaded.
The SUM software then requests these files from the BSC. The files that are
downloaded are stored in the Flash-EPROM. These files are required for the
performance of both SUM and module functions.
After the BTS Software Package is downloaded, the LAPD OML connection to
the BSC is dropped and the SUM software starts.
12.3.3 Other BTS Software Packages Download

The downloading of the remaining BTS software is performed under control of
the SUM software. The SUM re-establishes the LAPD SUM connection with the
BSC using the OML time slot position previously stored in memory.
The SUM collects hardware data from the BTS modules to determine which
modules are present and their hardware capabilities.
The SUM inspects the BTS Master file to determine the correct files to be
downloaded for each module that has been identified. These files are then
downloaded from the BSC and stored in Flash-EPROM.
A BTS_DOWNLOAD_REPORT message is sent to the BSC indicating the
result of the software download. The reason for the BTS reset/restart is also
provided.
This has an effect on the level of software activation required, either:
SUM software alone, or
SUM and module software.
183 / 234
12.3.4 Management of Software Versions

The SUM can store up to two versions of the BTS Software Packages in
Flash-EPROM. The SUM requests that a file be downloaded only when a new
file is needed. This is determined by comparing the file version listed in the
Master File against the version currently stored in Flash-EPROM.
A new file is downloaded when:
The correct version is not in Flash-EPROM
The correct version exists but has become corrupted.
When there are two versions of a file currently stored, downloading another
version causes the file with the oldest reference to be removed.
Note that the OMU_CPF is not stored in Flash-EPROM. Only one version of
this file is present in the BTS.
Download files are transferred in packets. The SUM calculates checksums for
each packet and returns an acknowledgement to the BSC after a successful
transfer. Re-transmission is requested for any packets which are corrupted.
184 / 234
12.4 Software Initialization

When the BTS software download is complete, the SUM activates the software
in one of two ways:
OMU-(SBL) level software activation (for SUM software alone), or
BTS-level software activation (for SUM and module software).
The type of software activation depends on the content of the
BTS_DOWNLOAD_REPORT message.
This message was sent to the BSC indicating the reason for the BTS
reset/restart. The SUM first establishes the IOM connection to allow
communication with the modules. It then performs one of the two types of
software activation.
After the software has been activated, the SUM sends two messages to the
BSC. The first message is the BTS_CONF_COMPL message (configuration
completion report) which contains configuration error messages. The second
message is the BTS_SW_ACTIVATE_REPORT. This provides an overall
report of the results of the software initialization, together with a reminder of
the reason for the BTS reset/restart.
The following figure shows the common actions that occur in both SUM-level
and BTS-level software activation.
BSC
SUM SW
Modules
Time
Start of IOM_CONF
Broadcast by SW
BTS_SW_ACTIVATE_REQ
BTS_CONF_REQ
BTS_CONF_DATA
OMU(SBL) Level Software Activation

BTS Context Recovery
BTS Modules Reconfiguration
BTS (SBL) Level Software Activation

BTS Modules Initialization
BTS_CONF_COMPL
BTS_SW_ACTIVATE_REPORT
Figure 31: Software Activation
185 / 234
186 / 234
13 BTS Objects
13 BTS Objects
This chapter describes the managed objects for the BTS. It provides the
allowed states for both managed objects and SBLs. It maps managed objects
and SBLs to the corresponding RIT.
It provides for both Managed Objects and SBLs:
Hierarchy
Allowed states
Allowed actions
RITs
Managed Objects/SBL to RIT relationships.
187 / 234
13 BTS Objects
13.1 BTS Managed Objects and SBLs

The following table lists the Managed Objects and SBLs for the BTS
9110/9110-E and BTS 9100.
Managed Object
SBL Type
Description
BTS
BTS
Base Transceiver Station
CCF
CCF
Cabinet Cooling Fan (always set to NEQ for 9110 Micro

BTS/9110-E Micro BTS because there are no fans)
CLLK
CLLK
Clock Link
EACB
EACB
External Alarm Collection Board
OMU
OMU
Operations and Maintenance Unit
RA
RA
Radio Access
TRE
TRE
Transceiver Equipment (exists externally, maps internally to

CU SBL)
Table 62: 9100 BTS and 9110 Micro BTS/9110-E Micro BTS Managed Objects and SBLs
188 / 234
13 BTS Objects
13.2 BTS Managed Objects and SBLs Description

The following table describes the Managed Objects and SBLs in terms of
the functions:
Telecom
O&M
Hardware mapping.
Managed
Objects SBL
Function
Description
BTS
Telecom
None.
O&M
Supports all configuration management actions performed on BTS

equipment.
BTS
The SBL also collects general BTS alarms (e.g., loss of Q1 or

Token Bus).
CCF
CLLK
CCF
CLLK
Hardware
Mapping
BTS equipment.
Telecom
None.
O&M
Cools down the BTS boards to maintain them within their

environmental temperature range.
Hardware
Mapping
BTS cooling fans equipment.
Telecom
None.
O&M
Provides the whole BTS with four clocks signals derived from the
13 Mhz master frequency. Those signals are delivered via a bus
type link to the frame units, the carrier units and the frequency
hopping units.
The clock signals are the basic timing for TDMA.
CU
CU
Hardware
Mapping
Frequency generator and clock distribution units.
Telecom
Transforms a baseband signal into an UHF signal on the transmitting

side and vice versa on the receiving side. The UHF value is
configured by the OMU/SUM from an OMC-R command.
The SBL also measures the strength of the received signal.
O&M
Measures regularly the VSWR . When the VSWR is too high, it

automatically disconnects the transmitter.
Hardware
Mapping
Carrier Units (transmitter/receiver boards and power sources).

A transmitter/receiver board contains the GSM/DCS modulator,
UHF up/down converter and amplifiers.
189 / 234
13 BTS Objects
Managed
Objects SBL
Function
Description
EACB
Telecom
None.
O&M
Performs the following actions:
EACB
Sends to the OMU/SUM environmental alarms such as fire,

smoke, intrusion, overheating, etc
Commands the shutdown or activation of the BTS power supplies
Switches the BCCH to the spare combiner
Triggers the change-over to the redundant amplifier
Distributes the Q1 bus to the carrier units and to the extension
cabinets of the BTS.
FHU
FU
FHU
FU
Hardware
Mapping
EACB equipment.
Telecom
Switches each time slot of a TDMA frame between the FUs and
the CUs tuned to different frequencies, according to a frequency
hopping algorithm.
O&M
None.
Hardware
Mapping
FHU.
Telecom
Handles the following layers:

Layer 1 - the electrical interface from the CU as well as the 2
Mbps interface from the Abis interface
Layer 2 - the LAPD and LAPDm protocols
Layer 3 - part of the RR signalling from mobile side RSL.
O&M
For a specified time slot it:

Provides configuration parameters
Computes online the results of the FU-CU loop test
Computes (on triggered basis) the results of the radio loop test
Performs measurements (processor load, interference level,
etc.).
FU_TS
Hardware
Mapping
FU boards.
Telecom
None.
O&M
Addresses a particular baseband channel of the FU particularly for

configuration purposes.
Performs RTE loop test on addressed baseband channels.
190 / 234
13 BTS Objects
Managed
Objects SBL
OMU
OMU
Function
Description
Hardware
Mapping
None.
Telecom
None.
O&M
Main functions are:

Initializes and configures the BTS
Collects and reports alarms to the BSC
Transfers SW and data files to the FUs
Triggers the BTS channels configuration in case of a failure
Tests triggering at the other parts of the BTS
Communicates with local terminal.
RA
RA
Hardware
Mapping
OMU/SUM board.
Telecom
Models the up and down interface to the transmit/receive antennae.

Receive:
Filters the signal from the antennae to remove unwanted signals
outside the GSM band
Amplifies the filtered signal
Performs signal splitting by multi-coupling to allow each receiver
to pick up its own signal.
Transmit:
Couples to the transmitting antennae all analog signals coming
from the carrier units.
Optionally, it is also able to switch the BCCH carrier unit to a
spare combiner, on an OMU/SUM command.
O&M
Tunes the cavities if RTCs are used.

Measures the VSWR regularly.
Hardware
Mapping
Receiver Front-End
FU power supplies
CU power supplies
Transmission combiners rack (cavities + cabling)
BCCH switch.
RTE
Telecom
None.
191 / 234
13 BTS Objects
Managed
Objects SBL
Function
Description
O&M
Loops the RF signal of a specified time slot from the transmitting

end to the receiving end.
Activates the connection between the transmitter combiner and the
receiver front end input under the control of the OMU/SUM.
Hardware
Mapping
RTE
Table 63: Managed Objects and SBL Descriptions
192 / 234
13 BTS Objects
13.3 BTS Managed Objects (SBL) Hierarchy

The Managed Objects (SBL) hierarchy reported by the BTS to the OMC-R
is shown in the following figures. All Managed Objects (SBLs) are reported
by the OMU/SUM except the FU_TS, which is not reported in hardware
configuration data.
In addition to the Managed Objects (SBL) hierarchy within the BTS, the
OMU/SUM also reports the following information to the OMC-R:
Relationship between Frame Unit and LAPD - RSL. It indicates the TEI value
used by the Frame Unit
The relationship between OMU and LAPD - OMU, by indicating the
corresponding TEI value (always 1)
RA configuration parameters, such as type of combiners and BTS power
class
BTS configuration (Master BTS/Slave BTS)
BTS hardware family (9110 Micro BTS/9110-E Micro BTS and 9100 BTS).
Note:
The following SBL hierarchies show only those SBLs reported to the OMC-R.
1234567890123456789012345
1234567890123456789012345
BTS
1234567890123456789012345
1234567890123456789012345
1234567890123456789012345
1234
12345
1234
1234
EACB* 1234
CCF*
OMU
1234
12345
CLLK
1234 123451234 1234
1234
12345
12345
RA*
12345
123
12345
RA*
123
123
FU* 123
CU*
123456789
123
123
ABISHWAYTP
123456789 123
TRE*
123456789 123
at OMCR
There can be to 6 sectors, FHU is always IT.

*: means that the box represents several instances of the SBL.
Figure 32: 9110 Micro BTS/9110-E Micro BTS/9100 Managed Objects (SBL)
Hierarchy Reported by the OMU/SUM to the OMC-R
193 / 234
13 BTS Objects
13.4 Allowed Managed Object/SBL States of the 9110 Micro

BTS/9110-E Micro BTS
The allowed states for the Managed Objects and SBLs of the 9110 Micro
BTS/9110-E Micro BTS are shown in the following tables.
13.4.1 Allowed States of Managed Object Abis_PCM (SBL Abis-HWAY-TP)

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
Unlocked
Enabled
Degraded
FLT
Unlocked
Disabled
Failed
EF
Unlocked
Disabled
Dependency/failed
MSA
Unlocked
No change
Suspended
Table 64: Allowed States of Managed Object Abis_PCM (SBL Abis-HWAY-TP)
13.4.2 Allowed States of Managed Objects (SBL) BTS

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
MSD
MSA
Table 65: Allowed States of Managed Objects (SBL) BTS (1)

(1) The OMU does not receive a message that these Managed Objects are
equipped. It sets their state to unlocked/enabled (IT).
13.4.3 Allowed States of Managed Objects (SBL) CCF

SBL
Admin. State
Operat. State
Availab. State
Control State
NEQ (2)
Table 66: Allowed States of Managed Objects (SBL) CCF

(2) The CCF SBL is always in the NEQ state because 9110 Micro BTS/9110-E
Micro BTS do not have any cooling fans.
194 / 234
13 BTS Objects
13.4.4 Allowed States of Managed Objects (SBL) CLLK

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
Unlocked
Enabled
Degraded
FLT (4)
Unlocked
Disabled
Failed
FOS (3)
Unlocked
Disabled
Off-Line/Disabled
MSA
Unlocked
No change
Suspended
Table 67: Allowed States of Managed Objects (SBL) CLLK

(3) After a repair action, CLLK initialization takes place during SUM power up.
(4) The CLLK is put to unlocked/disabled (FLT) state when it is configured in
slave mode but the external clock is not available.
13.4.5 Allowed States of Managed Objects (SBL) CU

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
Unlocked
Enabled
Degraded
FOS
Unlocked
Disabled
Off-Line/ Disabled
SOS
Unlocked
Disabled
Dependency
OPR
Locked
No change
MSD
Unlocked
No change
Suspended
MSA
Unlocked
No change
Suspended
NEQ
Table 68: Allowed States of Managed Objects (SBL) CU
195 / 234
13 BTS Objects
13.4.6 Allowed States of Managed Objects (SBL) EACB

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT (5)
FOS (5)
OPR
Locked
No change
MSD
Unlocked
No change
Suspended
MSA (5)
NEQ
Table 69: Allowed States of Managed Objects (SBL) EACB

(5) No XIOB is provided. Therefore, the EACB cannot get the FOS, FIT and
MSA states.
13.4.7 Allowed States of Managed Objects (SBL) FU

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
Unlocked
Enabled
Degraded
FLT
Unlocked
Disabled
Failed
SOS
Unlocked
Disabled
Dependency
FOS
Unlocked
Disabled
Off-Line/Disabled
OPR
Locked
No change
MSD
Unlocked
No change
Suspended
MSA
Unlocked
No change
Suspended
NEQ
Table 70: Allowed States of Managed Objects (SBL) FU
196 / 234
13 BTS Objects
13.4.8 Allowed States of Managed Objects (SBL) OMU

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
MSD
Unlocked
No change
Suspended
MSA
Unlocked
No change
Suspended
Table 71: Allowed States of Managed Objects (SBL) OMU
13.4.9 Allowed States of Managed Objects (SBL) RA

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
Unlocked
Enabled
Degraded
FOS
Unlocked
Disabled
Off-Line/Disabled
SOS
Unlocked
Disabled
Dependency
OPR
Locked
No change
MSD
Unlocked
No change
Suspended
MSA
Unlocked
No change
Suspended
NEQ
Table 72: Allowed States of Managed Objects (SBL) RA
197 / 234
13 BTS Objects
13.5 Allowed Managed Objects and SBL States of the 9100 BTS
The allowed states for the Managed Objects and SBLs of the 9100 BTS are
shown in the following table.
13.5.1 Allowed States of Managed Object Abis_PCM (SBL Abis-HWAY-TP)

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
Unlocked
Enabled
Degraded
FLT
Unlocked
Disabled
Failed
EF
Unlocked
Disabled
Dependency/failed
MSA
Unlocked
No change
Suspended
Table 73: Allowed States of Managed Object Abis_PCM (SBL Abis-HWAY-TP)
13.5.2 Allowed States of Managed Objects (SBL) BTS

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
MSA
MSD
Table 74: Allowed States of Managed Objects (SBL) BTS (1)

(1) The OMU/SUM does not receive a message that these Managed Objects
are equipped. It sets their state to unlocked/enabled (IT).
198 / 234
13 BTS Objects
13.5.3 Allowed States of Managed Objects (SBL) CCF

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
Unlocked
Enabled
Degraded
FOS
Unlocked
Disabled
Off-Line/Disabled
OPR
Locked
No change
MSA
Unlocked
No change
Suspended
MSD
Unlocked
No change
Suspended
NEQ
Table 75: Allowed States of Managed Objects (SBL) CCF
13.5.4 Allowed States of Managed Objects (SBL) CLLK

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
Unlocked
Enabled
Degraded
FLT (3)
Unlocked
Disabled
Failed
FOS (2)
Unlocked
Disabled
Off-Line/Disabled
MSA
Unlocked
No change
Suspended
Table 76: Allowed States of Managed Objects (SBL) CLLK

(2) After a repair action, CLLK initialization takes place during OMU/SUM
power up.
(3) The CLLK is put to unlocked/disabled (FLT) state when it is configured in
slave mode but the external clock is not available.
199 / 234
13 BTS Objects
13.5.5 Allowed States of Managed Objects (SBL) CU

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
Unlocked
Enabled
Degraded
FOS
Unlocked
Disabled
Off-Line/Disabled
SOS
Unlocked
Disabled
Dependency
OPR
Locked
No change
MSD
Unlocked
No change
Suspended
MSA
Unlocked
No change
Suspended
NEQ
Table 77: Allowed States of Managed Objects (SBL) CU
13.5.6 Allowed States of Managed Objects (SBL) EACB

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
Unlocked
Enabled
Degraded
FOS
Unlocked
Disabled
Off-Line/Disabled
OPR
Locked
No change
MSA
Unlocked
No change
Suspended
MSD
Unlocked
No change
Suspended
NEQ
Table 78: Allowed States of Managed Objects (SBL) EACB
200 / 234
13 BTS Objects
13.5.7 Allowed States of Managed Objects (SBL) FU

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
Unlocked
Enabled
Degraded
FLT
Unlocked
Disabled
Failed
SOS
Unlocked
Disabled
Dependency
FOS
Unlocked
Disabled
Off-Line/Disabled
OPR
Locked
No change
MSD
Unlocked
No change
Suspended
MSA
Unlocked
No change
Suspended
NEQ
Table 79: Allowed States of Managed Objects (SBL) FU
13.5.8 Allowed States of Managed Objects (SBL) OMU

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
MSD
Unlocked
No change
Suspended
MSA
Unlocked
No change
Suspended
Table 80: Allowed States of Managed Objects (SBL) OMU
201 / 234
13 BTS Objects
13.5.9 Allowed States of Managed Objects (SBL) RA

SBL
Admin. State
Operat. State
Availab. State
Control State
IT
Unlocked
Enabled
FIT
Unlocked
Enabled
Degraded
FOS
Unlocked
Disabled
Off-Line/Disabled
SOS
Unlocked
Disabled
Dependency
OPR
Locked
No change
MSD
Unlocked
No change
Suspended
MSA
Unlocked
No change
Suspended
NEQ
Table 81: Allowed States of Managed Objects (SBL) RA
202 / 234
13 BTS Objects
13.6 Allowed Managed Objects and SBL Actions for 9110 Micro
BTS/9110-E Micro BTS
The Managed Objects and SBL commands which are allowed for the internal
Managed Objects and SBLs of the 9110 Micro BTS/9110-E Micro BTS are
indicated by a checkmark ( ) in the following table.
Managed
Objects
Command
Unlock
Lock
Restart
Reset
Initialize
Disable
Restart
Reset
CU
EACB
SBL Command
Read
Status
Shutdown
Managed
Objects/SBL
Type
BTS
CCF
(1)
CLLK
FU
OMU
RA
Table 82: Allowed Managed Objects and SBL Commands for the 9110 Micro BTS/9110-E Micro BTS
(1) The CCF is always in the NEQ state because it does not have any cooling
fans.
203 / 234
13 BTS Objects
13.7 Allowed Managed Objects and SBL Actions for 9100 BTS
The Managed Objects and SBL commands which are allowed for the internal
Managed Objects and SBLs of the 9100 BTS are indicated by a checkmark
( ) in the following table.
Managed
Objects
Command
SBL Command
Read
Status
Unlock
Lock
Restart
Reset
Initialize
Disable
Restart
Reset
Shutdown
Managed
Objects/SBL
Type
BTS
CU
EACB
CCF
CLLK
FU
OMU
Table 83: Allowed Managed Objects and SBL Commands for the 9100 BTS
204 / 234
13 BTS Objects
13.8 BTS 9110/9110-E RITs

BTS 9110/9110-Es are single replaceable units. Implementing fault localization
at a more refined level than the whole equipment is unnecessary. The BTS
9110/9110-E RITs are listed in the following table.
RIT
Name
RIT
Function
GSM
850
ABISCO
Abis Connection Board
ACCO
GSM
900
GSM
1800
GSM
1900
O&M
Controlled
Alternating Current Connection
ANTD
Internal Antenna GSM 1800
ANTG
Internal Antenna GSM 900
DB4D
9110 Micro BTS-S Basic or Extension

BTS unit GSM 1800 with antenna diversity
DB4E

BTS unit Extended GSM Frequency Band
(E-GSM) with antenna diversity
DB4G

BTS unit GSM 900 with antenna diversity
MB4D
9110 Micro BTS-S Basic or Extension BTS

unit GSM 1800 without antenna diversity
MB4E

BTS unit E-GSM without antenna diversity
MB4G
9110 Micro BTS-S Basic or Extension BTS

unit GSM 900 without antenna diversity
MFCC
Micro-BTS Fan
SSCB
Battery for SSC
SSCCF
Connector field for SSC
SSCF
Fan external for SSC
SSCFH
Fan and heater internal for SSC
SSCLP
Lightning protection for SSC (two per SSC) -
SSCPS
AC/DC converter for SSC (three per SSC)
VSWD
VSWR detector GSM 1800
VSWG
VSWR detector GSM 900
Table 84: 9110 Micro BTS/9110-E Micro BTS

SBL/RIT Relationships All 9110 Micro BTS/9110-E Micro BTS SBLs are
related uniquely to their RIT.
205 / 234
13 BTS Objects
13.9 BTS 9110/9110-E SBLs and RITs Reported to the OMC-R

The BTS 9110 SBLs and RITs reported to the OMC-R are listed in the
following table.
SBL
RITs for GSM 900
RITs for GSM 1800
CLLK
DB4E, DB4G, MB4E, MB4G
DB4D, MB4D
RA
DB4D, MB4D
EACB
None.
None.
CU
DB4D, MB4D
FU
DB4D, MB4D
OMU
DB4D, MB4D
Table 85: 9110 Micro BTS SBLs and RITs Reported to the OMC-R
SBL
RITs for GSM 850
RITs for GSM 900
RITs for GSM 1800
RITs for GSM 1900
CLLK
DB5L, MB5L
DB5E, DB5G, MB5E,

MB5G
DB5D, MB5D
DB5P, MB5P
RA
DB5L, MB5L
DB4E, DB4G, MB4E,

MB4G
DB5D, MB5D
DB5P, MB5P
EACB
None.
None.
None.
DB5P, MB5P
CU
DB5L, MB5L
DB4E, DB4G, MB4E,

MB4G
DB5D, MB5D
DB5P, MB5P
FU
DB5L, MB5L
DB4E, DB4G, MB4E,

MB4G
DB5D, MB5D
DB5P, MB5P
OMU
DB5L, MB5L
DB4E, DB4G, MB4E,

MB4G
DB5D, MB5D
DB5P, MB5P
Table 86: 9110-E Micro BTS SBLs and RITs Reported to the OMC-R
206 / 234
13 BTS Objects
13.10 9100 BTS RITs

The 9100 BTS RITs are listed in the following table.
RIT
Name
RIT
Function
GSM
850
GSM
900
GSM
1800
GSM
1900
O&M
Controlled
ABAC
AC Battery Control Unit
ACIB
AC Interface Box
ACRI
AC Remote Inventory
ADAM
Adapter Module
ADAM4
Adapter Module 4
ANCD
Antenna Network Combiner GSM 1800
ANCG
ANCL
ANCP
AC Power Distribution Panel
ANXD
Antenna Network Module - Type X - GSM

1800
ANXG
Antenna Network Module - Type X - GSM

900
ANXP
Antenna Network Module - Type X - Digital

Cellular System at 1900 MHz (GSM 1900)
ANYD
Antenna Network Module - Type Y - GSM

1800
ANYG

900
ANYL

850
ANYP

1900
APOD
AC Power Distribution Panel
BAC2
Battery Connection 2
BACO
Battery Connection
BCU1
Battery Control Unit 1
BCU2
Battery Control Unit 2
BATL
Large Battery Unit
BATLM
Large Multi Battery Unit
BATM
Medium Battery Unit
207 / 234
13 BTS Objects
RIT
Name
RIT
Function
GSM
850
GSM
900
GSM
1800
GSM
1900
O&M
Controlled
BATS
Small Battery Unit
DAC8
Direct Air Cooling
DAC9
Direct Air Cooling
FACB
Fans Control Board
FANU
Fan Unit
HEAT2
Heating Unit
HEX2
Heat Exchanger
HEX3
Heat Exchanger
HEX4
Heat Exchanger
OUTC
Outdoor Control Board
PM08
Power Module 800 W
PM11
Power Module 1100 W
PM12
Power Module 1200 W
SUMA
Station Unit Module
SUMP
Station Unit Module PCM
SUMX
Station Unit Module
TADH
TRE Module - GSM 1800 - High Power
TADHE

GMSK and 8-PSK
TRAD
TRE Module - GSM 1800 - Medium Power
TRADE

Enhanced 8-PSK power
TRAG
TRAGE

Enhanced 8-PSK power
TAGH
TAGHE

GMSK and 8-PSK
TRAL
TRAP
TRDH
TRDM
208 / 234
13 BTS Objects
RIT
Name
RIT
Function
GSM
850
TRGM
TRE Module - GSM 900- Medium Power
TRPM
XIBM
External I/O Board
XIOB
External I/O Board
GSM
900
GSM
1800
GSM
1900
O&M
Controlled
Table 87: 9100 BTS RITs
209 / 234
13 BTS Objects
13.11 9100 BTS SBLs and RITs Reported to the OMC-R

The 9100 BTS SBLs and RITs reported to the OMC-R are listed in the
following table.
SBL
RITs for GSM 850
RITs for GSM 900
RITs for GSM 1800
RITs for GSM 1900
BTS
BATM, BATLM, PM12
BATM, BATL, BATLM, BATM, BATL, BATLM,

BATS, BCU1, BCU2, BATS, BCU1, BCU2,
PM08, PM11, PM12
PM08, PM11, PM12
BATM, BATL, BATLM,

BATS, BCU1, BCU2,
PM08, PM11, PM12
CCF
FACB, FANU
FACB, FANU
FACB, FANU
FACB, FANU
CLLK
SUMA, SUMX
SUMA, SUMP, SUMX
SUMA, SUMP, SUMX
SUMA, SUMP, SUMX
RA
ANCL, ANYL
ANCG, ANXG, ANYG
ANCD, ANXD, ANYD
ANCP, ANXP, ANYP
EACB
XIBM, OUTC
XIBM, XIOB, OUTC
XIBM, XIOB, OUTC
XIBM, XIOB, OUTC
OMU
SUMA, SUMX
SUMA, SUMP, SUMX
SUMA, SUMP, SUMX
SUMA, SUMP, SUMX
CU
TRAL
TAGH, TRAG,
TAGHE, TRAGE,
TRGM
TADH, TRAD,
TADHE, TRADE,
TRDH, TRDM
TRAP, TRPM
FU
TRAL
TAGH, TRAG,
TRAGE, TRGM
TADH, TRAD,
TRADE, TRDH,
TRDM
TRAP, TRPM
Table 88: 9100 BTS SBLs and RITs Reported to the OMC-R
210 / 234
13 BTS Objects
13.12 BTS RBLs and Local Fault Indication via LEDs

Most of the BTS RITs have LEDs mounted on their front panels.
These conform to the following colors and status for maintenance purposes:
Green LED
The RIT is powered when the green LED is ON unless otherwise stated.
There can be more than one green LED.
Red LED
Flashing or continuously ON in the case of permanent failure.
Yellow LEDs
These LEDs indicate software checks. Consult the hardware description of
the particular RIT to obtain more detailed information about the function of
these LEDs.
The following tables list the associated RBL for each RIT. Where more than
one RBL exists, the disable sequence is shown.
The front panel LEDs for each RIT are indicated by a checkmark ( ). A dash (-)
indicates that no LED is present. Only RITs which have LEDs are shown in
these tables. In many cases there is more than one LED of a particular color.
The exact function of each LED is not within the scope of this document. For
more information, refer to the BTS 9110 / 9110-E Hardware Description or
the 9100 BTS Hardware Description
RIT Name
RBL
DB4D
TRE
DB4E
TRE
DB4G
TRE
MB4D
TRE
MB4E
TRE
MB4G
TRE
MFCC
N/A
Green LED
Red LED
Yellow LED
Table 89: 9110 Micro BTS / 9110-E Micro BTS RITs with Corresponding RBLs and LED Indications
211 / 234
13 BTS Objects
RIT Name
RBL
ACRI
N/A
ANCD
RA
ANCG
RA
ANCL
RA
ANCP
RA
ANXD
RA
ANXG
RA
ANXP
RA
ANYD
RA
BCU1
N/A
BCU2
N/A
HEX2
N/A
PM08 (Version BAAA) BTS
Green LED
Red LED
Yellow LED
PM08 (Version BBAA) BTS

PM11
BTS
PM12
BTS
SUMA
RA
SUMP
RA
SUMX
RA
TADH
TRE
TADHE
TRE
TAGH
TRE
TAGHE
TRE
TRAD
TRE
TRADE
TRE
TRAG
TRE
TRAGE
TRE
TRAL
TRE
TRAP
TRE
212 / 234
13 BTS Objects
RIT Name
RBL
TRDH
TRE
TRDM
TRE
TRGM
TRE
TRPM
TRE
Green LED
Red LED
Yellow LED
Table 90: 9100 BTS RITs with Corresponding RBLs and LED Indications
213 / 234
13 BTS Objects
214 / 234
14 Example Functions
This chapter shows how the BTS software works with other parts of the
system, to link Mobile Stations to the land-based network. The examples are
representative only, and illustrate some of the principal GSM system functions.
215 / 234
14.1 Telecommunication
This section provides examples of the operation of telecommunication
functions, which are:
Handover
Timing advance
Paging
Channel interference monitoring
LAPD failure
In-band signalling.
14.1.1 Handover
Handover procedures are primarily managed by Layer 3 software located in
the SCP. All BTS handovers are asynchronous.
In an asynchronous handover the target BTS controls the Mobile Station
access. The target BTS has a channel pre-assigned by the BSC for the Mobile
Station to access when it changes cell. A Physical Information message,
which includes new timing advance information, is sent to the Mobile Station.
To establish a link with the target BTS a Handover Access message is sent
from the Mobile Station. The target BTS then sends a Handover Detection
message to the BSC. When the Mobile Station fully establishes the link, it
reports completion of the procedure to the BSC. This is done using a Handover
Complete message, which is transparently transferred by the target BTS. The
BSC then sends an RF Channel Release message to the original BTS to
release the radio resources.
If the link is not established within a predefined time period, the target BTS
repeats the physical information message. If establishment of the link is still not
confirmed within a predefined period, the target BTS stops the transmission. It
then sends a Handover Access Failure message to the BSC. If the Mobile
Station cannot access the new radio channel, it attempts to re-establish the link
with the original BTS. In this case the Mobile Station also reports the failure to
the BSC with a Handover Failure message.
Note:
216 / 234
In multiband operation, a congestion mechanism, for example, can cause the

Mobile Station to perform a handover between the main and secondary bands.
This is to prevent saturation of the cell. Multiband operation is supported on
Multiband Mobile Stations that are compliant to Phase 2, or later.
BSC
Channel Activation message informs Target BTS

of handover type, and preassigns channel for
Mobile Station to access when it changes cell.
Target BTS
Target BTS sends physical Information
message to Mobile Station. This includes
new timing advance information.
Target BTS
Target BTS sends Handover

Detection message to BSC.
Mobile Station requests access to target BTS

by sending Handover Access message.
Target BTS grants handover access.
BSC
Mobile Station sends Handover

Complete message to BSC via BTS.
Target BTS
Mobile Station continues call in

progress without interruption.
BSC
Previous BTS
BSC sends Channel Release

message to last BTS to release
radio resources.
Radio resources available for

reallocation.
Figure 33: Asynchronous Handover
14.1.2 Timing Advance

Timing Advance is used to compensate for changing transmission delays
between Mobile Stations and the BTS. The TRE/MTRE monitors the arrival
time of bursts from each Mobile Station. These measurements are passed
to the BSC. The BSC calculates a new timing offset to compensate for any
change in BTS-to-Mobile Station distance. Timing advance commands from
the BSC are transparently forwarded to the Mobile Stations.
217 / 234
14.1.3 Paging
The paging algorithm creates Paging Request messages in response to
paging commands sent from the BSC. Each paging command identifies the
paging group of the Mobile Station concerned.
For each paging group, the BTS maintains a paging message queue. When a
paging command is received, the algorithm attempts to include the specified
Mobile Station in the Paging Request message at the end of the queue. If
the message is full, a new message is created and added to the queue. The
queued messages are periodically transmitted and removed from the queue.
Note:
To minimize overhead, the paging algorithm selects one of three types of

paging request message. The type of paging request message depends on the
format of the Mobile Station identification. Depending on its type, the paging
request message identifies between one and four Mobile Stations.
14.1.4 Channel Interference Monitoring

The DEC continuously performs two types of measurements on the data
received from the TRE/MTRE:
Noise (interference) level on the idle time slots
SNR.
The parameters are sent to the SCP in two different messages. These are
subsequently forwarded to the BSC for use when allocating traffic to idle
time slots.
14.1.5 LAPD Failure

Whenever a LAPD failure occurs on the Abis Interface, the error is reported
to the BTS Layer 3 functions. The error is passed back to the BSC, if the
failure permits.
14.1.6 In-Band Signalling

In-band signalling is used where urgent/fast message transfer is required. In
order to provide an instantly available signalling channel, traffic channels are
temporarily borrowed for messaging. This can also be done to increase
signalling channel bandwidth. Typical uses are for handover commands, call
establishment progress messages and fault reports.
218 / 234
14.2 Telecommunications Overload Protection

The following section provides an example of a telecommunications overload
protection function.
Internal BTS overload situations are prevented by informing the BSC of
unacceptably high operational loads in the TRE/MTRE.
SCP-idle time is monitored over a fixed observation period. The percentage of
available TRE/MTRE telecommunication buffers is also monitored. If either
measurement falls below predefined thresholds, actions are taken according
to the degree of overload detected:
1. A timer is used to delay triggering of overload defense actions (to prevent
short load transients causing unnecessary fault reports).
2. Local defense actions are triggered to limit the load of the TRE/MTRE.
3. An Overload Detected message is forwarded towards the BSC. The BSC
then takes steps to reduce the demands on the TRE/MTRE.
Note:
Since a watchdog is included in the SCP, a complete overload results in

a TRE/MTRE reset.
219 / 234
14.3 Mobile Station RF Power Control

The following figure shows how the BTS adjust Mobile Station RF power
according to the uplink signal strength received.
Mobile Station
SACCH bursts
TRE/MTRE
Analog
RXP
BSC
DEC
SCP
I/Q demodulation
AD conversion
H_LRXDATA (high gain)
L_LRXDATA (low gain)
High or low gain
output selected.
RSSI calculated for
each time slot.
RSSI inserted
as inband signaling
RSSI values filtered and
averaged for each time
slot over 104 frames,
to produce RXLEV_AV
Average Bit Error Rate
estimated to produce
EXQUAL quality
parameter
Measurement Result Message
RXLEV_AV and RXQUAL
to BSC via Layer 3
Power Control
threshold
comparison as
shown in Figure 33
MS_POWER_CONTROL
to BTS via Layer 3
ENC
Power Step
extracted
from Power
Control
command
Power Step parameter
SACCH MS Power Command in Layer 1 Header
Power Step from

ENCT inserted into
SACCH
RF power
adjusted
Figure 34: RF Power Control Applied to Mobile Station
220 / 234
The following figure shows the parameters evaluated by the power control and
handover algorithms. It also shows the type of action taken when specified
threshold values are reached. Handover decisions are made by the BSC,
based on measurement result messages from the BTS.
RXQUAL
0
2
LEV
Intercell
H/O
3
1234
1234
1234
1234
1234
1234
1234
1234
1234
1234
1234
1234
1234
1234
1234
123456789012345678901234567
123456789012345678901234567
123456789012345678901234567
123456789012345678901234567
Power Decrease
No Power
Command
Required
Power Increase
QUAL Intercell H/O
Intracell H/O
RXLEV
0
10
20
30
40
50
60
Upper RXLEV threshold for Power Decrease

Lower RXLEV threshold for Intracell Handover
Lower RXLEV threshold for Power Increase
Lower RXLEV threshold for Intercell Handover
Lower RXQUAL threshold for Inter/Intracell Handover, depending on RXLEV

Lower RXQUAL threshold for Power Increase
Upper RXQUAL threshold for Power Decrease
Figure 35: Mobile Station Power Control and Handover Thresholds
221 / 234
222 / 234
15 Software Interaction Scenario

This chapter shows a typical scenario to illustrate the high-level interaction
between principal BTS software entities.
223 / 234
15.1 BCCH-TRE Fault

The scenario details a typical high-level interaction between principal BTS
software entities that follow a fault arising in a TRE/MTRE allocated to the
BCCH.
The order of actions is representative, since it varies according to the exact
nature of the failure.
Interaction sequence:
1. If an abnormal situation is internally detected by the TRE/MTRE, it
autonomously sends an error message to the SUM with a status of Faulty.
2. The TRE/MTRE is marked as maintenance seized in the SUM database
while it is subjected to further checks. Using the data supplied by the
TRE/MTRE, the SUM correlates the detected alarms (including those from
other sources) to eliminate secondary, knock-on effects. This pinpoints
the underlying cause of the failure.
3. If the TRE/MTRE is indeed faulty, a recovery request is sent to the BSC.
The BSC responds with a recovery report and determines the appropriate
recovery action based on the data received from the SUM. The SUM is
notified of the recovery action by a reconfiguration message.
4. Local defense and recovery actions are now run concurrently.
The defense actions power down the faulty TRE/MTRE.
The recovery actions specified by the BSC are used to reconfigure the
BTS. These includes re-allocation of the radio channels to the remaining
TRE/MTREs (to ensure the preservation of the BCCH-Carrier). The
wideband combiner requires no reconfiguration.
The TRE/MTRE, Frequency Hopping function and External Alarm
Connection function are also reconfigured.
5. The TRE/MTRE is marked as faulty/out-of-service in the SUM database. A
report is forwarded to the BSC.
224 / 234
15.2 Interaction Fault Reports

The following figure shows a typical sequence of reports which follow a fault
arising in a TRE/MTRE allocated to the BCCH.
BSC
SUM
TRE/MTRE
Impacted Internal
BTS Entities
Fault Occurs
TRE/MTRE Faulty Report
Mark TRE/MTRE as Maintenance Seized
2
Correlate Alarms and Determine
if TRE/MTRE is indeed Faulty
Request Recovery
Recovery Report
Determine Recovery Action
Reconfiguration Data
Local Defense Actions and Reconfiguration
Mark TRE/MTRE as Faulty/OutofService
Report Fault Status
Figure 36: TRE/MTRE Fault Report Scenario
225 / 234
226 / 234
16 Start-Up Scenario
This Scenario shows the different reset/restart sequence for all BTS start-up
scenarii.
These scenarii are:
BTS/SUM/MSUM Power Up
Restart BTS (SBL)
Restart OMU (SBL)
OMU Auto-restart
Reset BTS
Reset OMU
OMU Auto-reset.
The BTS/SUM/MSUM Power-up scenario is fully described in BTS Start Up
and Initialization (Section 12). The remaining scenarii use actions that are also
described in Chapter 12, but in lesser detail than that used for the first scenario.
The full set of scenarii is included here for completeness. The sequence of
events shown in each scenario is understandable in terms of the detailed
description provided in BTS Start Up and Initialization (Section 12).
227 / 234
16.1 BTS/SUM/MSUM Power Up

The following figure shows the BTS/SUM/MSUM Power-up sequence of events.
BSC
SUM Software
Module
Time
SUM/MSUM Power Up
SUM Autotest
BSC Connection
BTS/OMU Started
BTS Master File,

SUM SW/SPF Download
BSC
SUM Software
Module
Other BTS Sofware Packages Download
Software Activate (SBL BTS or SBL OMU Level)
BTS Fault Indication
Actions after OMU or BTS Power Up,

(Auto) Restart, (Auto) Reset
Figure 37: BTS/SUM/MSUM Power Up Process Diagram
228 / 234
16.2 Restart SBL BTS

The following figure shows the Restart SBL BTS sequence of events.
BSC
SUM
Module
Time
BSC and IOM Disconnection
Restart of SUM Software
BSC Connection
BTS_CONF_REQUEST
BTS_ACK
BTS_CONF_DATA
BTS_ACK
Start of IOM_CONF
Broadcast
BTS Restart:
BTS Module Initialization
BTS_CONF_COMPL
BTS_ACK
Figure 38: Restart SBL BTS Process Diagram
229 / 234
16.3 Restart SBL OMU

The following figure shows the Restart SBL OMU sequence of events.
BSC
SUM
Module
Time
BSC Connection
BTS_CONF_REQUEST
BTS_ACK
BTS_CONF_DATA
BTS_ACK
Start of IOM_CONF
Broadcast
OMU Restart:
BTS Module Reconfiguration
BTS_CONF_COMPL
BTS_ACK
Figure 39: Restart SBL OMU Process Diagram
230 / 234
16.4 SBL OMU Auto-Restart

The following figure shows the SBL OMU auto-restart sequence of events.
BSC
SUM
Module
Time
Save the Origin
of the Autorestart
BSC Connection
Increment
OMU_Autorestart_Count
Start of IOM_CONF
Broadcast
Actions after OMU or BTS

Power Up, (Auto) Restart, (Auto) Reset
Figure 40: SBL OMU Auto-Restart Process Diagram
231 / 234
16.5 Reset SBL BTS

The following figure shows the Reset SBL BTS sequence of events.
BSC
SUM
Module
Time
BTS Reset:
Hardware Reset of the Modules which are not Isolated
BSC
SUM
Module
SUM goes to
Bootstrap
SUM Autotest
BSC Connection
BTS/OMU Started
BTS Master File,

SUM Software/SPF Download
BSC
SUM
Module
Other
BTS Software Packages Download
Software Activate (BTS Level)
Figure 41: Reset SBL BTS Process Diagram
232 / 234
16.6 Reset SBL OMU

The following figure shows the Reset SBL OMU sequence of events.
BSC
SUM
Module
Time
BSC
SUM
Module
SUM goes to
Bootstrap
SUM Autotest
BSC Connection
BTS/OMU Started
BTS Master File,

BSC
SUM
Module
Other
Software Activate (OMU Level)
Figure 42: Reset SBL OMU Process Diagram
233 / 234
16.7 SBL OMU Auto-Reset

The following figure shows the SBL OMU Auto-Reset sequence of events.
BSC
SUM
Module
Time
Save the Origin
of the AutoReset
SUM
SUM goes to
Bootstrap
SUM Autotest
BSC Connection
BTS/OMU Started
BTS Master File,

BSC
SUM
Module
Other
Software Activate (BTS or OMU Level)
Actions after OMU or BTS Power Up,

(Auto) Restart, (Auto) Reset
Figure 43: SBL OMU Auto-Reset Process Diagram
234 / 234

Alcatel-Lucent GSM: 9100 BTS/9110 Micro BTS/9110-E Micro BTS Functional Description

Uploaded by

Document Information

Original Title

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

Alcatel-Lucent GSM: 9100 BTS/9110 Micro BTS/9110-E Micro BTS Functional Description

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent GSM

9100 BTS/9110 Micro BTS/9110-E

3BK 21244 AAAA TQZZA Ed.08

BLANK PAGE BREAK

9100 BTS/9110 Micro BTS/9110-E Micro BTS FD

3BK 21244 AAAA TQZZA Ed.08

3BK 21244 AAAA TQZZA Ed.08

Introduction to Telecommunication Functions - Baseband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3BK 21244 AAAA TQZZA Ed.08

3BK 21244 AAAA TQZZA Ed.08

3BK 21244 AAAA TQZZA Ed.08

3BK 21244 AAAA TQZZA Ed.08

3BK 21244 AAAA TQZZA Ed.08

3BK 21244 AAAA TQZZA Ed.08

This document is intended for anyone interested in learning about the

3BK 21244 AAAA TQZZA Ed.08

3BK 21244 AAAA TQZZA Ed.08

1.1 Logical Position of BTS in BSS

Radio Frequency Signals

Figure 1: Logical Position of BTS in BSS

3BK 21244 AAAA TQZZA Ed.08

Radio Frequency Signals

Figure 2: Logical Position of BTS in BSS with GPRS

1.1.1 Functional Architecture

Part of the Telecommunications

Data flows through the BTS in the downlink direction

Figure 3: BTS Functional Architecture

3BK 21244 AAAA TQZZA Ed.08

1.1.2 Channel Organization

1.2 BTS Functions

1.2.1 Transmission Functions

3BK 21244 AAAA TQZZA Ed.08

1.2.2 Telecommunication Functions

1.2.3 O&M Functions

1.2.4 Support Functions

3BK 21244 AAAA TQZZA Ed.08

1.3 BTS External Interfaces

The external alarm connection function is implemented as the

The External Battery Connection is used to provide control over

The External Clock Interface enables the BTS to synchronize with

Timing functions are described in O&M and Support Functions

The External BTS Control Bus is used to supervise or control

3BK 21244 AAAA TQZZA Ed.08

The External Global Positioning System Control Bus provides

The External Stealth Radio Connection provides the control link

The Inter Entity Bus is used to connect a single master 9110

The master BTS 9110/9110-E can have cables connected to

3BK 21244 AAAA TQZZA Ed.08

A local MMI enables a terminal to be connected for local operator

The mains supply voltage for a 9100 BTS is determined by the

Table 1: BTS External Interfaces

3BK 21244 AAAA TQZZA Ed.08

Figure 4: IEB Connections for Pure 9110 Micro BTS

3BK 21244 AAAA TQZZA Ed.08

1.4 Signal and Data Processing

1.4.1 Downlink Signal Processing

1.4.1.1 Transmission Functions

1.4.1.2 Baseband Processing

1.4.1.3 Channel Organization

3BK 21244 AAAA TQZZA Ed.08

1.4.1.4 Frequency Hopping

1.4.1.5 Coupling Functions

1.4.2 Uplink Signal Processing