Bts Fuctional Description

Alcatel-Lucent GSM
BTS Functional Description
BTS Document
Sub-System Description
Release B10
3BK 21227 AAAA TQZZA Ed.03

BLANK PAGE BREAK
Status RELEASED
Short title BTS Functional Descr.

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 / 184 3BK 21227 AAAA TQZZA Ed.03

Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1 BTS Role in a GSM Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.1.1 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.1.2 Functional Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.1.3 Channel Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2 BTS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2.1 Transmission Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2.2 Telecommunication Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2.3 O&M Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.2.4 Support Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.3 External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3.1 Air Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3.2 Abis Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3.3 Clock Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3.4 MMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3.5 External Alarm Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.3.6 Power Supply Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.4 Signal and Data Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.4.1 Downlink Signal Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.4.2 Uplink Signal Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.4.3 O&M Data Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2 Channel Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.1 Introduction to Channel Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2 Radio Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.1 Radio Transmission Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.2 Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.3 Modulation Technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.3 Channel Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.3.1 Signalling Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.3.2 Broadcast Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.3.3 Common Control Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.3.4 Dedicated Control Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.3.5 Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.3.6 Packet Switched Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.4 Channel Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.4.1 26-Multiframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.4.2 51-Multiframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.4.3 Superframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4.4 Hyperframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4.5 Transmit/Receive Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.5 Radio Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.5.1 Layer 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.5.2 Layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.5.3 Layer 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3 Transmission Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.1 Introduction to Transmission Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.2 Multiplexing Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.2.1 Abis Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.2.2 Transmission O&M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.2.3 Signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.2.4 Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.2.5 Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3BK 21227 AAAA TQZZA Ed.03 3 / 184

Contents
3.2.6 Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.3 Abis Interface Physical Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.4 GPRS Transmission Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4 Telecommunication Functions - Baseband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.1 Introduction to Telecommunication Functions - Baseband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.2 Baseband Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.2.1 Speech Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.2.2 Rate Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.2.3 Channel Encoding and Decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.2.4 Interleaving/De-interleaving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.2.5 Encryption/Decryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.2.6 Demodulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.3 Call Management Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.3.1 Radio Link Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.3.2 Radio Resource Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.3.3 Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.3.4 Discontinuous Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.3.5 Discontinuous Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.3.6 Quality Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.3.7 Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.4 Supervisory and Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.4.1 Clock Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.4.2 Protocol Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.4.3 Radio Channel Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.4.4 Transcoder Time Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5 Telecommunication Functions - RF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.1 Introduction to Telecommunication Functions - RF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.2 RF Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.2.1 RF Carrier Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.2.2 Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.2.3 GMSK Modulation and Up-conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5.2.4 Power Amplification and Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5.2.5 Channel Selection and Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5.2.6 Signal Amplification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.2.7 A-D Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.2.8 Digital Pre-processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.3 Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.3.1 RF Hardware Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.3.2 Frequency Hopping Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.3.3 Clock Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.3.4 Frequency Synthesizer Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.3.5 Alarm Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.3.6 High/Low Gain Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.4 Coupling Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.4.1 Isolating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.4.2 Combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.4.3 Duplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.4.4 Power Coupling and Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
5.4.5 Antenna Pre-amplification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
5.4.6 Receiver Front-end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6 O&M and Support Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.1 O&M Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.1.1 O&M Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.1.2 O&M Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.1.3 RF Self-test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.1.4 Recovery Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4 / 184 3BK 21227 AAAA TQZZA Ed.03

Contents
6.2 Support Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

6.2.1 Internal Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.2.2 Timing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.2.3 Internal Temperature Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
7 BTS Functional Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
7.1 Introduction to BTS Functional Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
7.2 G1/G2 BTS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
7.2.1 Functional Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
7.2.2 Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
7.2.3 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
7.3 Mapping of Functional Blocks to Functional Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
7.3.1 Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
7.3.2 Telecommunication Baseband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
7.3.3 Telecommunication RF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
7.3.4 O&M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7.3.5 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
8 G1/G2 BTS Functional Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8.1 G1/G2 BTS Functional Units Breakdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
8.2 G1/G2 BTS Frame Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
8.2.1 G1/G2 BTS Frame Unit Functional Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
8.2.2 G1/G2 BTS Frame Unit External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8.2.3 G1/G2 BTS Frame Unit Submodules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
8.2.4 G1/G2 BTS Frame Unit Submodule Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
8.2.5 G1/G2 BTS Frame Unit Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
8.3 G1/G2 BTS Station Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.3.1 G1/G2 BTS Station Unit Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.3.2 G1/G2 BTS Station Unit External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
8.3.3 G1/G2 BTS Station Unit Submodules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.3.4 G1/G2 BTS Station Unit Submodule Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.3.5 G1/G2 BTS Station Unit Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.4 Carrier Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.4.1 G1/G2 BTS Carrier Unit Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.4.2 G1/G2 BTS Carrier Unit External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
8.4.3 G1/G2 BTS Carrier Unit Submodules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
8.4.4 G1/G2 BTS Carrier Unit Submodule Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.4.5 G1/G2 BTS Carrier Unit Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.5 G1/G2 BTS Coupling Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
8.5.1 G1/G2 BTS Coupling Unit Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.5.2 G1/G2 BTS Coupling Unit External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
8.5.3 G1/G2 BTS Coupling Unit Submodules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
8.5.4 G1/G2 BTS Coupling Unit Submodule Functions . . . . . . . . . . . . . . . . . . . . . . . . . 117
8.5.5 G1/G2 BTS Coupling Unit Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
9 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
9.1 Overview on Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
9.2 Software and Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.2.1 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.2.2 Downloaded Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.2.3 Software/Firmware Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.3 Software Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
9.4 BTS Start-up and Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
9.4.1 Start-up Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
9.4.2 BTS Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
9.4.3 BTS Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
9.5 O&M Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
9.5.1 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
9.5.2 Software Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
3BK 21227 AAAA TQZZA Ed.03 5 / 184

Contents
9.6 Frame Unit Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

9.6.1 SCP Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
9.6.2 MFP Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
9.6.3 Software States of the Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
9.6.4 Encoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
9.6.5 Demodulator and Channel Decoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
9.7 Carrier Unit Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
9.7.1 Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
9.7.2 Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
10 BTS Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
10.1 Managed Objects and SBL Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
10.2 BTS SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
10.3 BTS Managed Object (SBL) Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
10.4 Allowed Managed Object and SBL States of the G1 BTS Mark 2 and G2 BTS . . . . . . . . . . 164
10.4.1 Allowed States of Managed Object Abis_PCM (SBL Abis-HWAY-TP) . . . . . . . 164
10.4.2 Allowed States of Managed Object (SBL) BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
10.4.3 Allowed States of Managed Object (SBL) CCF . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
10.4.4 Allowed States of Managed Object (SBL) CLLK . . . . . . . . . . . . . . . . . . . . . . . . . . 165
10.4.5 Allowed States of Managed Object (SBL) CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
10.4.6 Allowed States of Managed Object (SBL) EACB . . . . . . . . . . . . . . . . . . . . . . . . . . 166
10.4.7 Allowed States of Managed Object (SBL) FHU . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
10.4.8 Allowed States of Managed Object (SBL) FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
10.4.9 Allowed States of SBL FU_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
10.4.10 Allowed States of Managed Object (SBL) OMU . . . . . . . . . . . . . . . . . . . . . . . . . . 168
10.4.11 Allowed States of Managed Object (SBL) RA . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
10.4.12 Allowed States of SBL RTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
10.5 Allowed Managed Object and SBL Actions for the G1 BTS Mark 2 and G2 BTS . . . . . . . . 170
10.6 G1 BTS Mark 2 RITs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
10.7 G1 BTS Mark 2 SBLs and RITs Reported to the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
10.8 G2 BTS RITs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
10.9 G2 BTS SBLs and RITs Reported to the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
10.10 BTS RBLs and Local Fault Indication via LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
10.10.1 G1 BTS Mark 2 RITs with Corresponding RBL and LED Indications . . . . . . . . 179
10.10.2 G2 BTS (GSM 900/1800/1900) RITs with Corresponding RBLs and LED
Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
10.10.3 RITs Specific to G2 BTS GSM 900 with Corresponding RBLs and LED
Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
10.10.4 RITs Specific to G2 BTS GSM 1800/1900 with Corresponding RBLs and LED
Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
6 / 184 3BK 21227 AAAA TQZZA Ed.03

Figures
Figures
Figure 1: Logical Position of BTS in BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 2: Logical Position of BTS in BSS with GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 3: BTS Functional Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 4: BTS-BSC Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 5: GPRS Transmission and Signalling Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 6: Baseband Telecommunication Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 7: Speech Transcoding for Speech Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 8: Rate Adaptation for Data Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 9: RF Telecommunication Functions for BTSs with Frequency Hopping using Constant Carrier
Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 10: RF Telecommunication Functions for BTSs with Frequency Hopping using Programmable Carrier
Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 11: G1/G2 BTS Functional Units Breakdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 12: G1/G2 BTS, Frame Unit Functional Entities and Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 13: G1 BTS, Mark2 Multi-board Frame Unit (Without Antenna Diversity) . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 14: G1 BTS Mark2 Single-board Frame Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 15: G2 BTS Three-board Frame Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 16: G2 BTS Single-board Frame Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 17: G1/G2 BTS, Station Unit Logical Functions and Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Figure 18: G1 BTS Station Unit (Master) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 19: G2 BTS Single-carrier Station Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Figure 20: G2 BTS Multi-carrier Station Unit with Redundant Timing and Switching Functions . . . . . . . . . 102
Figure 21: G1/G2 BTS, Non-diversity Carrier Unit Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 22: G1 BTS Carrier Unit (Antenna Diversity) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 23: G2 BTS Carrier Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 24: G1/G2 BTS, Downlink Coupling Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Figure 25: G1/G2 BTS, Uplink Coupling Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Figure 26: G1/G2 BTS, Antenna Pre-amplifier Simplified Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Figure 27: G1 BTS Mark2 Two-carrier Downlink Coupling Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Figure 28: G1 BTS Mark2 Four-carrier Downlink Coupling Unit Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Figure 29: G1 BTS Mark2 Six-carrier Downlink Coupling Unit Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Figure 30: G1 BTS Mark2 Eight-carrier Downlink Coupling Unit Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 31: G2 BTS Single-carrier Downlink Coupling Unit Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Figure 32: G2 BTS Two-carrier Downlink Coupling Unit Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Figure 33: G2 BTS Three to Four-carrier Downlink Coupling Unit Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 34: G2 BTS Single to Four-carrier Downlink Coupling Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 35: G2 BTS Single to Eight-carrier Downlink Coupling Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 36: G1 BTS Mark2 Two to Four-carrier Uplink Coupling Unit Variants . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 37: G1 BTS Mark2 Two to Four-carrier Diversity Uplink Coupling Unit Variants . . . . . . . . . . . . . . . . . 129
3BK 21227 AAAA TQZZA Ed.03 7 / 184

Figures
Figure 38: G1 BTS Six to Eight-carrier Uplink Coupling Unit Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 39: G1 BTS Mark2 Six to Eight-carrier Diversity Uplink Coupling Unit Variants . . . . . . . . . . . . . . . . . 131
Figure 40: G2 BTS Single/Two-carrier Uplink Coupling Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 41: G2 BTS Single to Four-carrier Uplink Coupling Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 42: G2 BTS Single to Eight-carrier Uplink Coupling Unit Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 43: BTS Start-Up Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 44: G1 BTS and G2 BTS Managed Object (SBL) Hierarchy Reported by the OMU/SUM to the
OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
8 / 184 3BK 21227 AAAA TQZZA Ed.03

Tables
Tables
Table 1: GSM 900 and GSM 1800 Frequency Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 2: TCH/F and TCH/H Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 3: Possible Channel Combinations for Single Time Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Table 4: Correspondence Table of Speech Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 5: Correspondence Table of Rate Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Table 6: O&M External Connections - Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Table 7: O&M Configuration Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Table 8: O&M Fault Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Table 9: Principal G1/G2 BTS Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Table 10: Functional Block to Functional Unit Mapping - Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Table 11: Functional Block to Functional Unit Mapping - Telecommunication Baseband . . . . . . . . . . . . . . . . 79
Table 12: Functional Block to Functional Unit Mapping - Telecommunication RF . . . . . . . . . . . . . . . . . . . . . . . 80
Table 13: Functional Block to Functional Unit Mapping - O&M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Table 14: Functional Block to Functional Unit Mapping - Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Table 15: G1/G2 BTS, Distribution of Frame Unit Functions between Frame Unit Functional Entities . . . . . 86
Table 16: G1/G2 BTS, Frame Unit, External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Table 17: G1/G2 BTS, Frame Unit Functional Entities and Submodules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Table 18: G1/G2 BTS, Station Unit, External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table 19: G1/G2 BTS, Station Unit Functions and Submodules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Table 20: G1/G2 BTS, Carrier Unit Control Function Submodules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Table 21: G1/G2 BTS, Carrier Unit Downlink Function Submodules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Table 22: G1/G2 BTS, Carrier Unit Uplink Function Submodules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Table 23: G1/G2 BTS, Coupling Unit Downlink Function Submodules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Table 24: G1/G2 BTS, Coupling Unit Uplink Function Submodules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Table 25: G1 BTS, Coupling Unit Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Table 26: G2 BTS Coupling Unit Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Table 27: BTS Firmware/Software Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Table 28: Software and Data Held by BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Table 29: BTS Initialization, Units and Functions to be Initialized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Table 30: O&M Software, Application Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Table 31: O&M Software, Interface Handlers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Table 32: SCP and MFP Functions, States of the FSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Table 33: Digital Receiver, Functional Sub-Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Table 34: BTS Managed Object and SBL Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Table 35: G1 BTS and G2 BTS Managed Objects and SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Table 36: Allowed States of Managed Object Abis_PCM (SBL Abis-HWAY-TP) . . . . . . . . . . . . . . . . . . . . . . . 164
Table 37: Allowed States of Managed Object (SBL) BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Table 38: Allowed States of Managed Object (SBL) CCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Table 39: Allowed States of Managed Object (SBL) CLLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
3BK 21227 AAAA TQZZA Ed.03 9 / 184

Tables
Table 40: Allowed States of Managed Object (SBL) CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Table 41: Allowed States of Managed Object (SBL) EACB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Table 42: Allowed States of Managed Object (SBL) FHU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Table 43: Allowed States of Managed Object (SBL) FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Table 44: Allowed States of SBL FU_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Table 45: Allowed States of Managed Object (SBL) OMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Table 46: Allowed States of Managed Object (SBL) RA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Table 47: Allowed States of SBL RTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Table 48: Allowed Managed Object and SBL Commands for the G1 BTS and G2 BTS . . . . . . . . . . . . . . . . 170
Table 49: G1 BTS Mark 2 RITs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Table 50: G1 BTS MARK 2 SBLs and RITs Reported to the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Table 51: G2 BTS RITs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Table 52: G2 BTS SBLs and RITs Reported to the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Table 53: G1 BTS Mark 2 RITs with Corresponding RBL and LED Indications . . . . . . . . . . . . . . . . . . . . . . . . 180
Table 54: G2 BTS (GSM 900/1800/1900) RITs with Corresponding RBLs and LED Indications . . . . . . . . . 181
Table 55: RITs Specific to G2 BTS GSM 900 with Corresponding RBLs and LED Indications . . . . . . . . . . 182
Table 56: RITs Specific to G2 BTS GSM 1800/1900 with Corresponding RBLs and LED Indications . . . . 183
10 / 184 3BK 21227 AAAA TQZZA Ed.03

Preface
Preface
Purpose This document provides a functional description of the GSM BTS.
The information provided applies to G1 BTS Mark2 and G2 BTS.
All features and functions described in this document may not be available
on your system.
The purpose of this document is to explain the role of the BTS in a GSM
network. This includes a description of:
The logical position of the BTS in the BSS

The functional architecture of the BTS
The way in which the BTS interfaces the land-based telephone system
with Mobile Stations.
What’s New In Edition 03

Update with the new equipment naming.
In Edition 02
Update of system title.
In Edition 01
First release of the document.
Audience This document is intended for:

Telecommunications technicians responsible for installation, configuration,
maintenance and troubleshooting operations on the BTS
Engineers responsible for network and configuration planning

Training departments.
Assumed Knowledge The reader must possess a:
General knowledge of telecommunications systems and terminology
3BK 21227 AAAA TQZZA Ed.03 11 / 184

Preface
Good understanding of GSM concepts

Familiarity with BSS functions and architecture.
12 / 184 3BK 21227 AAAA TQZZA Ed.03

1 Overview
1 Overview
This Overview provides a simplified overview of the BTS and its 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.
3BK 21227 AAAA TQZZA Ed.03 13 / 184

1 Overview
1.1 BTS Role in a GSM Network

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 via the TC. The BTS
thus interfaces 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.
14 / 184 3BK 21227 AAAA TQZZA Ed.03

1 Overview
1.1.1 Environment
The following figure shows the logical position of the 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 BSC BSS

Traffic and Other BTS
Signaling
Downlink via Abis
Interface Transcoder PSTN
Mobile Station Rest of

Uplink PLMN
Mobile Station
Figure 1: Logical Position of BTS in BSS
For systems incorporating GPRS some additional components are required as

shown in the following figure. An 9135 MFS is placed in the system between
the BSC and the SGSN The 9135 MFS contains a number of PCUs, one of
which controls all the GPRS activity for one cell.
Cell Area
SGSN
Radio Frequency Signals

via Air Interface A935
MFS
Mobile Station
BTS BSC BSS
Traffic and Gb
Signaling PCU Interface
Downlink via Abis
Interface
TC
Mobile
StationC
Uplink
Mobile Station
Mobile Station
Figure 2: Logical Position of BTS in BSS with GPRS
The SGSN (see previous figure) 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.
3BK 21227 AAAA TQZZA Ed.03 15 / 184

1 Overview
1.1.2 Functional Architecture

The following figure shows the functional architecture of the BTS.
Support Functions
To all Functions
Receive Telecommunication Functions

Antenna *
Abis Interface
RF Functions Baseband Functions Transmission
Transmit/Receive Functions
Antenna
* Diversity configuration only

Part of the Telecommunications
functions are duplicated for
Antenna Diversity. O&M Functions
Dataflow through the BTS in the downlink direction
Dataflow through the BTS in the uplink direction

Figure 3: BTS Functional Architecture
1.1.3 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 Chapter Channel Organization (Section 2) .
Channel Organization and Radio Resource Management are described in
Chapter Channel Organization (Section 2) .
16 / 184 3BK 21227 AAAA TQZZA Ed.03

1 Overview
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 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 OS 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 Chapter Transmission

Functions (Section 3) .
1.2.2 Telecommunication Functions

There are two primary telecommunication functions:
Baseband Functions
RF Functions.
1.2.2.1 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 Chapter Telecommunication Functions -
Baseband (Section 4) .
3BK 21227 AAAA TQZZA Ed.03 17 / 184

1 Overview
1.2.2.2 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 Chapter Telecommunication Functions - RF (Section 5) .
For Antenna Diversity, the telecommunications functions uplink path is
duplicated. The duplicated functions extend from the antenna, through the
RF functions, and up to the output of the Channel 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 BSC.
The BSC provides overall control.
The O&M functions use Layer 2 links for BTS internal communications. A
terminal connected via a 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 Chapter 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 Chapter O&M and Support
Functions (Section 6) .
18 / 184 3BK 21227 AAAA TQZZA Ed.03

1 Overview
1.3 External Interfaces

The BTS uses a number of external interfaces to provide the following
interfaces and connections:
Air Interface
Abis Interface
Clock Interface
MMI
External Alarm Connection
Power Supply Connection.
1.3.1 Air Interface

The Air Interface is the radio link between the BSS and the Mobile Station.
Different frequency ranges are allocated to the GSM 900 and GSM 1800
systems. 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 Chapter Channel Organization
(Section 2) .
1.3.2 Abis Interface

Uplink, 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
Transmission Functions (Section 3) .
1.3.3 Clock Interface

The Clock Interface enables the BTS to synchronize with other BTSs in either
master or slave mode.
Timing functions are described in Chapter O&M and Support Functions
(Section 6) .
1.3.4 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 BTS.
3BK 21227 AAAA TQZZA Ed.03 19 / 184

1 Overview
1.3.5 External Alarm Connection

The external alarm connection function enables the 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 Chapter O&M and Support Functions
(Section 6) .
1.3.6 Power Supply Connection

The mains supply voltage for a BTS is determined by the internal power supply
modules fitted. The requirement can be:
DC (-48/-60 VDC nominal)
AC (230 VAC).
The main power connection is filtered and provided with one or more protection
breakers. Lightning protection is provided for AC power lines.
Refer to the G2 BTS Hardware Description for more information about the
BTS power supplies.
20 / 184 3BK 21227 AAAA TQZZA Ed.03

1 Overview
1.4 Signal and Data Processing

Downlink data flows through the BTS from the Abis Interface to the transmit
antenna. Uplink data flows from the receive antenna(s) to the Abis Interface.
The following signal and data processing functions are performed:
Downlink Signal Processing
Uplink Signal Processing

O&M Data Processing.
1.4.1 Downlink Signal Processing

Downlink signal processing consists of the following functions and processes:
Transmission Functions
Baseband Processing
Channel Organization
Frequency Hopping
Coupling Functions.
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 up to eight

discrete datastreams, depending on the hardware configuration. These are
passed to the baseband functions for processing.
1.4.1.2 Baseband Processing

The baseband functions encode each datastream 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.
3BK 21227 AAAA TQZZA Ed.03 21 / 184

1 Overview
1.4.1.3 Channel Organization

Within a BTS, a single datastream 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 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.
1.4.1.4 Frequency Hopping

Successive TDMA bursts from each datastream 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 TCH 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 antenna. The coupling functions also enable the BTS
transmitters and receivers to share a single antenna.
22 / 184 3BK 21227 AAAA TQZZA Ed.03

1 Overview
1.4.2 Uplink Signal Processing

Uplink signal processing is essentially the reverse of the downlink processing
described in Section Downlink Signal Processing (Section 1.4.1) . The following
functions and processes are used:
Channel Decoding
Frequency Hopping
Signal Processing.
1.4.2.1 Channel Decoding

Radio signals received from Mobile Stations are routed from the antenna to the
RF functions. If antenna diversity is configured, signals from a second antenna
provide the BTS with a choice of two signals. Both signals are combined in the
Channel Decoder using the maximum radio combining algorithm.
The RF functions also include a duplexing function, which enables the BTS
receivers to share the transmit antenna.
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.
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 Chapter O&M and Support Functions
(Section 6) .
3BK 21227 AAAA TQZZA Ed.03 23 / 184

1 Overview
24 / 184 3BK 21227 AAAA TQZZA Ed.03

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 Usage
Channel Types
Channel Structure
Radio Resource Management.
The chapter breaks down each category into individual functions, and explains
how each type of channel is used.
3BK 21227 AAAA TQZZA Ed.03 25 / 184

2.1 Introduction to Channel Organization

The Air Interface is the radio link between the BSS and the Mobile Station.
The Air Interface utilizes 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 Usage

Two frequency ranges are allocated to the GSM 900 system and GSM 1800
variant. 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 including:
Radio Transmission Channels
Frequencies
Modulation Technique.
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.
All BTSs use up to eight uplink frequency channels, and up to eight downlink
frequency channels, according to the desired cell capacity.
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 900 935 - 960 890 - 915 124
GSM 1800 1805 - 1880 1710 - 1785 374
Table 1: GSM 900 and GSM 1800 Frequency Ranges
2.2.3 Modulation Technique

GSM systems use GMSK modulation, which provides a good compromise
between spectral efficiency and ease of demodulation.
26 / 184 3BK 21227 AAAA TQZZA Ed.03

2.3 Channel Types

The allocated uplink and downlink frequency bands are utilized using 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/Control Channels
TCHs
Packet Switched Channels.
2.3.1 Signalling Channels

Signalling channels are divided into three groups, each containing a number of
channel types:
BCH
CCCH
DCCH.
2.3.2 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).
Synchronization Channel
The SCH provides the Mobile Station with precise information about the
timing of the BTS time slot boundaries. 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 Section 2.5.1 , under the heading
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.
3BK 21227 AAAA TQZZA Ed.03 27 / 184

2.3.3 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 an Mobile Station to access the network. When an 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 MS
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 MS, following an Access Request. The message allocates an SDCCH
to the MS, 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 an Mobile Station that there is an
incoming call. The Mobile Station responds on the RACH.
28 / 184 3BK 21227 AAAA TQZZA Ed.03

2.3.4 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 of 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.5 Traffic Channels

There are four TCH/F types, four Enhanced TCH/F types, and one TCH/H type.
These types are shown in the following table.
Enhanced
Channel Type TCH/F TCH/F TCH/H
Encoded speech X X X
14.4 kbit/s data X - -
Table 2: 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.
2.3.6 Packet Switched Channels

For GPRS the packet data blocks CS-1 and CS-2 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.
3BK 21227 AAAA TQZZA Ed.03 29 / 184

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. Half-rate and enhanced full-rate channel combinations are
available only in dual-rate hardware configurations.
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 3: 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:
26-Multiframe
51-Multiframe
Superframe
Hyperframe
Transmit/Receive Timing.
2.4.1 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.
2.4.2 51-Multiframe
A second cycle, the 51-multiframe, is used for non-traffic channel 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.
30 / 184 3BK 21227 AAAA TQZZA Ed.03

2.4.3 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.
2.4.4 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[frac12] hours. All the frames are synchronized to
the same timing schedule.
2.4.5 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 Stations need only transmit or receive.
For further details of the Air Interface channel structure, refer to GSM rec. 05.01.
3BK 21227 AAAA TQZZA Ed.03 31 / 184

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. These are:
Layer 3 (Network)
Layer 2 (Data Link)
Layer 1 (Physical)
MAC layer.
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. These processes are:
Radio channel selection
Channel establishment
Handover preparation
Dedicated channel management
Common channel management

Flow control.
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 reallocate 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.
32 / 184 3BK 21227 AAAA TQZZA Ed.03

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 a GPRS system 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 9135 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.
For GPRS systems the timing advance is transmitted from the BTS to the
Mobile Station every 26th TDMA frame. This is achieved via the PTCCH.
The BTS also controls the timing between the BTS and 9135 MFS.
Timing Advance - extended cell
The maximum timing advance permitted with GSM networks is equivalent
to 63 bits. This restricts the Mobile Station to BTS distance to a radius of
approximately 35 km. For GSM 900 networks only, this distance can be
increased by using an extended cell configuration.
Extended cell operation inserts an additional 60 bit timing correction to both
received and transmitted signals. With this mechanism in place, the bursts
are realigned with the scheduled time slot boundaries so that processing
can properly take place.
3BK 21227 AAAA TQZZA Ed.03 33 / 184

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.
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
re -transmission 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. The Layer 1 functions are:
Modulation/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.
Multiframe Scheduling
Signalling and traffic data is time interleaved. Each channel uses a single
time slot in successive or periodic TDMA frames.
34 / 184 3BK 21227 AAAA TQZZA Ed.03

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
up to two, eight-channel BTSs. The chapter includes a list of different options
for implementing the Abis Interface at the physical layer.
Clock recovery is outlined, the alternative network configurations, and the
GPRS transmission plane are described.
3BK 21227 AAAA TQZZA Ed.03 35 / 184

3.1 Introduction to Transmission Functions

All uplink/downlink traffic and control data between the BTS and BSC is carried
on the Abis Interface. This interface is supervised by transmission functions at
the BTS and BSC.
Within the BTS, the transmission functions use the following links to handle
the transfer of traffic and control data between the Abis Interface and the
BTS components:
Data
LAPD RSL
LAPD OML.
The following figure shows a simplified block diagram of these interfaces

and links.
BTS BSC
LAPD RSL
BTS LAPD OML Transmission Abis Interface Transmission

Components Functions Functions
Data
Figure 4: BTS-BSC Transmission
36 / 184 3BK 21227 AAAA TQZZA Ed.03

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 64 kbit/s.
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.
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.
The following sections describe how the multiplexing allows all BTS - BSC
communications to be carried on a single Abis Interface. The way in which the
bandwidth is utilized is discussed under the following headings:
Abis Interface
Transmission O&M
Signalling
Traffic
Clock
Network Configuration.
3.2.1 Abis Interface

The 2 Mbit/s bandwidth of the Abis Interface is multiplexed to provide 32 time
slots, each of 64 kbit/s. These 32 time slots comprise one CCITT G703/704
frame.
Control data on the Abis Interface uses the following Layer 2 protocols at
submultiplex levels:
LAPD RSL
LAPD OML
Q1.
The first time slot in each frame is reserved for G703/704 management.
3.2.2 Transmission O&M

The TSC regularly polls the BSS transmission equipment, including that at
the BTS. A Q1 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 64 kbit/s time slot. Configuration rules exist to ensure that room for the Q1
bus is always available, even when a number of BTSs are connected to the
Abis Interface - e.g., in a chain or ring configuration. The remaining 31 time
slots in each frame are used as described in the rest of this section.
3BK 21227 AAAA TQZZA Ed.03 37 / 184

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 time slot is allocated to the OML.
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 onto one 64 kbit/s
time slot. This allows up to 12 carriers to be supported.
For details on GPRS signalling variation refer to Section 3.4 .
3.2.4 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 and Enhanced 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 64 kbit/s time slots for its full capacity of eight TCH/F, or Enhanced 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
64 kbit/s time slots.
For details on GPRS traffic variation refer to Section 3.4 .
3.2.5 Clock
Signals on the Abis Interface are 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.
3.2.6 Network Configuration

BTSs can be connected to the BSC via star or multidrop (chain or ring)
configurations. Star connection is always used for high capacity BTSs which
require all or most of the Abis interface bandwidth. Chain or ring architecture
enables low-capacity BTSs to share the bandwidth of an Abis connection.
In multidrop configurations, the Abis signal is routed through each BTS, where
it is regenerated before being sent to the next BTS. If the BTS is removed, the
vacant Abis connector must be bridged to maintain Abis continuity.
If the BTS is not powered, the routing of the Abis signal is dependent on the
type of BTS in the configuration. In some cases an internal relay connects the
input line to the output line. This passive connection allows the Abis signal to
be routed to the next BTS. For other types of BTS, the Abis connector must be
unplugged and bridged as though the BTS had been removed.
38 / 184 3BK 21227 AAAA TQZZA Ed.03

3.3 Abis Interface Physical Connection

For indoor BTS, the BTS and BSC multiplexing equipment is normally
connected using dedicated cabling.
Other methods of Abis Interface connection can be used for outdoor BTS,
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.
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.
3BK 21227 AAAA TQZZA Ed.03 39 / 184

The following figure shows the functional layout of the protocol layer. This 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 kbits/s channels
L2-RSL; a LAPD protocol between the BSC the BTS.
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 9135 MFS and BTS which uses
the synchronous mode of transmission.
L2-GCH - a simple proprietary protocol between the 9135 MFS and the
BTS for synchronization and channel activation.
S G
N M
D M
C /
P S
M RR BSSGP
LLC
RRM L2−RSL L2−GSL RRM
L1−RSL L1−GSL B BSSGP

S
S
RLC BSC G
MAC RLC
P MAC
Abis Ater
NS
L2−GCH L2−GCH
GSM RF GSM RF L2−RSL L2−GSL
L1−GCH L1−RSL L1−GSL L1−GCH FR
to SGSN
MSTS BTS Abis/Ater A935 MFS
Figure 5: GPRS Transmission and Signalling Planes
40 / 184 3BK 21227 AAAA TQZZA Ed.03

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.
3BK 21227 AAAA TQZZA Ed.03 41 / 184

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.
There are three categories of baseband telecommunication function which are
described in the following sections.
4.2 Baseband Processing

Baseband processing consists of:
Speech Transcoding
Rate Adaptation
Channel Encoding and Decoding
Interleaving/De-interleaving
Encryption/Decryption
Demodulation.
These functions are shown in the following figure and are described below.
RF Functions Baseband Functions Terrestrial Traffic
Downlink Direction
Speech
RF Transcoding
Encryption Interleaving Channel
Transmission Encoding Rate
Adaptation
To/From
Transmission MSC
Duplexing and
Uplink Direction * Transcoder
Functions
Speech
RF De− Channel Transcoding
De− Decryption
Reception modulation interleaving Decoding
Rate
Adaptation
Figure 6: Baseband Telecommunication Functions
42 / 184 3BK 21227 AAAA TQZZA Ed.03

4.2.1 Speech Transcoding

Transcoder functions are logically assigned to the BTS. The Transcoder is
physically located between the MSC and the BSC. It is connected to the
BTS, via the BSC using the Abis Interface. The Transcoder 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 can
be described in terms of:
Speech Traffic
Correspondence between Traffic and Channel Types
Bit-reordering.
4.2.1.1 Speech Traffic

For downlink speech traffic, two separate processes are carried out on full-rate,
enhanced 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 GSM rec. 06.10 TCH/F
GSM rec. 06.20 TCH/H
GSM rec. 06.60 Enhanced TCH/F
Encoding Transcoder
Function Function
6.5 kbit/s
12.2 kbit/s 8 kbit/s
Channel 13 kbit/s 16 kbit/s Speech 64 kbit/s
RAS Transcoding
Encoding Abis Channel
RAS is a GSM−specified rate adaptation

Figure 7: 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, Enhanced 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
Enhanced Full-rate Speech 12.2 Enhanced TCH/F Speech
Half-rate Speech 6.5 TCH/H Speech
Table 4: Correspondence Table of Speech Transcoding
* TCH/H and Enhanced TCH/F channels are not supported in some versions of
the BSS.
3BK 21227 AAAA TQZZA Ed.03 43 / 184

4.2.1.3 Bit-reordering
In addition to speech transcoding, another process is performed on speech
traffic. This is the process of bit-reordering. Bit-reordering is necessary because
individual bits in the encoded speech can make an unequal contribution to the
subjective speech quality. Reordering enables bits to be given the protection of
parity and/or convolutional encoding, according to their importance.
Bit-reordering can be performed by the Transcoder or the baseband functions.
The remote location of the Transcoder 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-reordering is carried out by the baseband
functions. This enables the Transcoder to start sending partly coded data on
the downlink, before finishing the coding of a speech frame. Bit-reordering
can therefore start in the BTS without waiting for the Transcoder to finish
processing the complete frame.
On the uplink, the processes of speech transcoding and bit-reordering are
effectively reversed. This recovers the original bitstream from the Mobile
Station’s transmission.
4.2.2 Rate Adaptation

The rate adaptation function adapts the Transcoder 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 Transcoder and the Air Interface (or vice-versa). This
mechanism forms an essential part of the Layer 1 interface between the two
different baseband coding schemes 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 Transcoder.
The process of rate adaptation can be described in terms of:
Data Traffic
Correspondence between data rates.
44 / 184 3BK 21227 AAAA TQZZA Ed.03

4.2.2.1 Data Traffic

In the downlink direction, V.110 data frames received by the Transcoder 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 GSM rec. 08.60 GSM rec. 04.21 GSM rec. 08.54
Transcoder
Encoding Function Function
3.6 kbit/s
6 kbit/s 16 kbit/s
12 kbit/s 8 kbit/s 16 kbit/s RAA 64 kbit/s
Channel RA1/RA1’ RAA
Encoding
RA2
RA2, RAA and RA1/RA1’ are GSM−specified rate adaptations

Figure 8: 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 and Enhanced TCH/F, the Air Interface rates of 12, 6 or 3.6 kbit/s
support user data rates of:
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 has only to support three user data rates:
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.
3BK 21227 AAAA TQZZA Ed.03 45 / 184

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 and Enhanced TCH/F.
User Data Rate Intermediate Data Air Interface Rate

(bit/s) Rate (kbit/s) (kbit/s) Possible Channel Types *
300 8 3.6 TCH/F2.4 or Enhanced TCH/F2.4
4800 8 6 TCH/F4.8 or Enhanced TCH/F4.8
9600 16 12 TCH/F9.6 or Enhanced TCH/F9.6
Table 5: Correspondence Table of Rate Adaptation
* Enhanced TCH/F channels are not supported in some versions of the BSS.
46 / 184 3BK 21227 AAAA TQZZA Ed.03

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 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 bursts 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 antennas 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
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.
3BK 21227 AAAA TQZZA Ed.03 47 / 184

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 three 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.
4.2.4.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 below.
4.2.4.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.
4.2.4.3 Intra-burst Interleaving

Intra-burst interleaving is achieved by distributing the interleaved sub-blocks
over a number of bursts.
48 / 184 3BK 21227 AAAA TQZZA Ed.03

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.
Three processes are used for message confidentiality:
Encryption
Decryption
TDMA multiframe building.
4.2.5.1 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 hardware dependent. For BTSs that

support dual-rate channels, the A5/1 and A5/2 cipher key must be downloaded
to the BTS, from the BSC, before Encryption can start.
For other non dual-rate BTSs, the cipher key is held in EPROM in the BTS
hardware. There are three different hardware types, with the EPROM
containing either the A5/1, A5/2, or A5/0 algorithm.
4.2.5.2 Decryption
Decryption uses the same algorithms as those used for Encryption. Decryption
is the reverse of Encryption.
4.2.5.3 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.
3BK 21227 AAAA TQZZA Ed.03 49 / 184

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
Adaptive Frame Alignment
Soft Decision Bits.
4.2.6.1 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.
4.2.6.2 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 an 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.
4.2.6.3 Soft Decision Bits

The Viterbi algorithm is used within 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.
50 / 184 3BK 21227 AAAA TQZZA Ed.03

4.3 Call Management Functions

The baseband telecommunications functions participate in a number of Call
Management functions:
Radio Link Recovery
Radio Resource Indication
Paging
DTX
DRX
Quality Measurement
Power Control.
4.3.1 Radio Link Recovery

The Radio Channel Management function detects the need for radio link
recovery when communication with an 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
the 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 an MS. 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.
3BK 21227 AAAA TQZZA Ed.03 51 / 184

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 the
Mobile Stations.
On the downlink TCH, a VAD algorithm in the Transcoder analyzes input
speech. If more than four successive speech frames are detected without
speech activity, the Transcoder can perform DTX.
If DTX is performed, it is controlled by the BSC. During DTX, a 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 prevent 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 the Mobile Stations. These measurements are
made by the Mobile Station during the associated paging block duration.
52 / 184 3BK 21227 AAAA TQZZA Ed.03

4.3.6 Quality Measurement

To exercise Power Control and Handover functions, the BSC uses information
about the signal quality and received signal strength 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 Channel Decoder constructs the received signal quality for every
block, then averages the values. These values are utilized 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.
3BK 21227 AAAA TQZZA Ed.03 53 / 184

4.4 Supervisory and Control Functions

The Supervisory and Control functions consist of:
Clock Distribution
Protocol Management
Radio Channel Management
Transcoder Time Alignment.
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 reallocated by the BSC depending on the
current measurement results. Radio Channel Management is required for
both dedicated channels and CCCH.
For GPRS systems channel management is carried out from the 9135 MFS via
the master PDCH.
54 / 184 3BK 21227 AAAA TQZZA Ed.03

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 Transcoder 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 and Enhanced 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 Transcoder, 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
Transcoder, which adjusts its schedule accordingly.
For each datastream, the baseband functions provide control and baseband
data processing for the eight time slots that comprise one TDMA frame.
3BK 21227 AAAA TQZZA Ed.03 55 / 184

56 / 184 3BK 21227 AAAA TQZZA Ed.03

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.
3BK 21227 AAAA TQZZA Ed.03 57 / 184

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 RF Telecommunication functions are described in three categories:
RF processing
Control functions
Coupling functions.
The following figure shows these functions for BTSs with frequency hopping
using constant carrier frequencies.
RF Functions Baseband Functions

Downlink Direction
Power Power Up− GMSK

Coupling Amplification conversion Modulation
and Detection
Frequency
Generator
Baseband
Downlink
Processing
Control Frequency
Coupling Hopping
Baseband
Uplink
* Processing
Frequency Frequency
Generator Generator
Down− Signal A−D Digital

conversion Amplification Conversion Pre−processing
Uplink Direction
* Antenna Diversity − some uplink functions are duplicated for Antenna Diversity.
Figure 9: RF Telecommunication Functions for BTSs with Frequency Hopping using Constant Carrier
Frequencies
For BTSs using constant carrier frequencies, frequency hopping is achieved by

switching successive TCH time slots between different transmitters. Refer to
Section Frequency Hopping (Section 5.2.2) for more information.
58 / 184 3BK 21227 AAAA TQZZA Ed.03

The following figure shows these functions for BTSs with frequency hopping
using programmable carrier frequencies.
Downlink Direction RF Functions Baseband Functions
Power Power Up− GMSK Baseband

Coupling Amplification conversion Modulation Downlink
and Detection Processing
Frequency
Generator
Control Frequency
Hopping
Coupling
Frequency
Generator
*
Frequency
Generator
Down− Signal A−D Digital Baseband

conversion Amplification Conversion Pre−processing Uplink
Processing
Uplink Direction
* Antenna Diversity − some uplink functions are duplicated for Antenna Diversity.
Figure 10: RF Telecommunication Functions for BTSs with Frequency Hopping using Programmable Carrier
Frequencies
For BTSs using programmable carrier frequencies, 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 Section Frequency Hopping (Section 5.2.2) for more information.
3BK 21227 AAAA TQZZA Ed.03 59 / 184

5.2 RF Processing
RF processing consists of the following functions:
RF Carrier Generation
Frequency Hopping
GMSK Modulation and Up-conversion

Power Amplification and Power Control
Channel Selection and Conversion
Signal Amplification
A-D Conversion
Digital Pre-processing
5.2.1 RF Carrier Generation

A BTS can be configured for up to eight discrete RF carriers. Each carrier
supports up to eight full-rate or 16 half-rate GSM channels. Depending on the
hardware 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. Where a

frequency synthesizer is used, it 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 a 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 direction
Uplink direction.
60 / 184 3BK 21227 AAAA TQZZA Ed.03

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 way a BTS processes the TCHs and
SDCCH varies depending how the hardware is used.
The BTS transmitters are tuned by frequency synthesizers. These synthesizers
can be programmed to produce different frequencies or they can be set to a
constant frequency.
The frequency synthesizer operation determines how the BTS processes
the traffic that is to be transmitted:
Constant carrier frequency

Frequency hopping is achieved by switching successive TCH time slots
between different transmitters. When frequency hopping is switched off,
each datastream remains connected to the same transmitter. The BCCH is
always connected to a single, dedicated transmitter.
Programmable carrier frequency
Frequency hopping is achieved by programming the synthesizers to
a different frequency for successive TCH time slots. 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.
5.2.2.2 Uplink Direction

When frequency hopping is in use, traffic from Mobile Stations is frequency
hopped. The way a BTS processes received frequency hopped TCHs varies
depending how the hardware is used.
The BTS receivers are tuned by frequency synthesizers. These synthesizers
can be programmed to produce different frequencies or they can be set to a
constant frequency.
The frequency synthesizer operation determines how 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.
3BK 21227 AAAA TQZZA Ed.03 61 / 184

5.2.3 GMSK Modulation and Up-conversion

Downlink data is received by the RF telecom functions in the form of encoded
bursts. The GMSK Modulation function converts the downlink data into two
baseband signals I and Q. The data is then 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.
5.2.4 Power Amplification and Power Control

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 PA 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.
5.2.5 Channel Selection and Conversion

A BTS can be configured with up to eight receivers, depending on the type of
hardware used. Each receiver can process up to eight full-rate or 16 half-rate
GSM channels.
Incoming signals are received via the antenna and coupling functions. The
receivers can be configured for diversity or non-diversity reception.
Each receiver is tuned by a frequency synthesizer. This is either set to produce
a constant frequency output or is programmable. The method used depends
on the BTS hardware. When the synthesizer is programmable, it re-tunes 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
frequency oscillator/synthesizer signal. This down-converts 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.
62 / 184 3BK 21227 AAAA TQZZA Ed.03

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
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 to the telecommunications baseband functions for

demodulation.
3BK 21227 AAAA TQZZA Ed.03 63 / 184

5.3 Control Functions

The principal control functions are:
RF Hardware Status
Frequency Hopping Control
Clock Management
Frequency Synthesizer Programming
Alarm Processing
High/Low Gain Selection.
5.3.1 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.
5.3.2 Frequency Hopping Control

Control of the frequency hopping function is performed for hardware
configurations that implement frequency hopping as part of the RF functions.
5.3.3 Clock Management

Clock selection and supervision is performed for hardware configurations
that provide redundant clock buses.
5.3.4 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.
5.3.5 Alarm Processing

Alarms originating in the RF functions are supervised, collected and passed to
the O&M functions.
5.3.6 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.
64 / 184 3BK 21227 AAAA TQZZA Ed.03

5.4 Coupling Functions

The BTS coupling functions interface the RF signal paths to the BTS antenna(s).
The principal coupling functions on the downlink and uplink are:
Isolating (downlink)
Combining (downlink)
Duplexing (optional for downlink and uplink)
Power Coupling and Detection (downlink)

Antenna Pre-amplification (uplink)
Receiver Front-end (uplink).
5.4.1 Isolating
The isolating function prevents the generation of additional intermodulation
products, by improving the isolation between the transmitters.
5.4.2 Combining
The combining function sums the RF signals from the BTS transmitters, to
enable them to share a single antenna. This function is not configured for
single transmitter BTS.
5.4.3 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 receiver’s 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.
3BK 21227 AAAA TQZZA Ed.03 65 / 184

5.4.4 Power Coupling and Detection

The Power Coupling and Detection function is not configured in all hardware
configurations. The function protects the 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 will exceed
a specified threshold. The function immediately diverts the RF power to a
matched termination.
5.4.5 Antenna Pre-amplification

The Antenna Pre-amplification function is realized in close proximity to the
antenna, to ensure optimum signal-to-noise ratio. It provides fault-tolerant,
low -noise pre-amplification of the received signal, ahead of the main receiver
function. The Pre-amplification function also provides an additional level of
co-channel rejection.
The Antenna Pre-amplification function delivers the uplink signal to the BTS
receivers via a Power Splitting function, which can provide an uplink signal to
up to eight receivers.
5.4.6 Receiver Front-end

The Receiver Front-end function provides low-noise pre-amplification of the
received signal, ahead of the main receiver function. The Receiver Front-end
function also provides an additional level of co-channel rejection.
The Receiver Front-end function delivers the uplink signal to the BTS receivers
via a Power Splitting function. This Power Splitting can provide an uplink signal
to up to eight receivers, depending on the hardware in use.
The Receiver Front-end function is realized as part of the main BTS cabinet
hardware configuration.
66 / 184 3BK 21227 AAAA TQZZA Ed.03

6 O&M and Support Functions
This chapter describes the O&M and the Support functions.

The chapter first describes the O&M functions in detail followed by the detailed
description of the Support functions.
3BK 21227 AAAA TQZZA Ed.03 67 / 184

6.1 O&M Functions

The O&M functions monitor and control the operation of the BTS. These
responsibilities are shared with the BSC. The description of these functions is
provided by the following sections:
O&M Connections
O&M Processing
RF Self-test
Recovery Strategy.
6.1.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 Connections
External Connections.
6.1.1.1 Internal Connections

Internally the O&M functions are connected to all processor controlled BTS
functions. This is achieved by the internal Layer 2 links which:
Provide high-speed transfer of downloadable software, operational

parameters and alarms to processor controlled functions.
Handle parameter and alarm transfer to all other intelligent functions

(including RF functions).
The non-intelligent BTS functions, for example, power supplies, fans, etc., are
connected to the O&M functions via dedicated alarm and control lines.
6.1.1.2 External Connections

Two interfaces provide the external connections shown in the following table.
Interface Description
LAPD OML The O&M function is connected to the BSC via the
LAPD OML Interface. This 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 operator’s actions.
Table 6: O&M External Connections - Interfaces
68 / 184 3BK 21227 AAAA TQZZA Ed.03

6.1.2 O&M Processing

O&M processing uses four categories of functions:
Fault Management

External Alarm Handling.
6.1.2.1 Configuration Management

The Configuration Management functions handle a number of tasks as shown
in the following table.
Task Description
Central Command Control GSM function-level configuration commands from the BSC or operator are
translated to low-level commands for the relevant BTS submodule(s).
Configuration/ Initialization Software initially downloaded from the BSC to the OMU is subsequently
downloaded from the OMU to other BTS modules. The O&M functions
configure each BTS module, and report start -up test results to the BSC.
Software Replacement This function enables changeover to newly downloaded software to be

performed, while retaining the configuration.
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.
Table 7: O&M Configuration Management Tasks
6.1.2.2 Fault Management

The Fault Management functions perform a range of tasks as shown in the
following table.
Task Description
Testing The Fault Management functions initiate BTS self-tests. These include RF
self-tests, dedicated alarm line testing and submodule diagnostic tests.
Continuous checks are made on the alarm inputs and, if a change occurs,
the database is updated. The BTS sends the test results to the BSC at
GSM function level.
Alarm Detection and Detects and filters alarms to prevent the generation of multiple fault reports
Filtering from a single source of failure.
Alarm Forwarding Forwards alarms to the BSC for processing.
3BK 21227 AAAA TQZZA Ed.03 69 / 184

Task Description
Alarm Translation Translates alarms to a GSM function-level format, independent of hardware

and software versions.
Command Translation Translates alarms to a GSM function-level format, independent of hardware

and software versions.
Table 8: O&M Fault Management Tasks
70 / 184 3BK 21227 AAAA TQZZA Ed.03

6.1.2.3 Dedicated Alarm and Control Handling

The Dedicated Alarm and Control Handling function provides simple control
and alarm signalling for non-intelligent BTS submodules. Examples of
non-intelligent BTS submodules include power supplies, fans, etc. The function
makes continuous checks on the alarm inputs and updates the database if a
change occurs. Alarms are reported on request.
6.1.2.4 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. Examples of BTS external alarm sources include cabinet
door switches, smoke detectors, etc.
6.1.3 RF Self-test
The optional RF self-test function enables the BTS baseband and radio paths
to be tested. The test is implemented by routing the BTS transmitter output to
the uplink path, in a simple loopback arrangement.
When the test is completed, a report is sent to the O&M functions. This shows
the status of the hardware in the loop, together with key performance figures.
6.1.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.
3BK 21227 AAAA TQZZA Ed.03 71 / 184

6.2 Support Functions

The principal BTS support functions are described in the following sections:
Internal Power Supplies
Timing Functions
Internal Temperature Control.
6.2.1 Internal Power Supplies

All BTS configurations are equipped with internal power supplies. These
convert the mains supply voltage to the DC voltages required by individual
BTS modules. Power supply units are available for DC only input and for
AC/DC mains input.
Additional features provided are:
Output Monitoring
Battery Backup.
6.2.1.1 Output Monitoring

All power supply outputs are monitored for output voltage. If an overvoltage
or undervoltage condition is detected, an alarm is raised and sent to the
O&M functions.
6.2.1.2 Battery Backup

Optional backup batteries maintain operation in the event of mains supply
failure. Backup batteries can be permanently connected in-circuit, or switched
automatically when needed.
6.2.2 Timing Functions

The Timing functions are:
Master frequency generation
Timing signal generation
Clock distribution.
6.2.2.1 Master Frequency Generation

All BTS clocks are derived from a 13 MHz master reference frequency. The
master frequency is generated in the master frequency generator. This is a
high stability oscillator. It can operate in free-running mode, or synchronized
mode to the PCM clock on the Abis Interface.
Most BTS configurations can be run in slave mode. In this arrangement, the
BTS is synchronized as slave to the master clock of another BTS.
72 / 184 3BK 21227 AAAA TQZZA Ed.03

6.2.2.2 Timing Signal Generation

From the 13 MHz reference signal, the following slower synchronization clocks
are derived by a process of frequency division:
2.16 MHz OBCLK
216.7 Hz FCLK
38.4 kBaud FN
1.733 kHz TSCLK.
6.2.2.3 Clock Distribution

The Clock Distribution function distributes the synchronization clocks as follows:
TSCLK, OBCLK, FCLK and FN to the Baseband Telecommunication

functions
OBCLK, FCLK and 13 MHz reference signal to the RF Telecommunication

functions.
6.2.3 Internal Temperature Control

With the exception of hardware types that are hermetically sealed, all BTSs
are equipped with an internal temperature control function. This consists
of heating elements 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
BTS operation. It switches the fans or heaters on and off, to maintain the
specified temperature range.
3BK 21227 AAAA TQZZA Ed.03 73 / 184

74 / 184 3BK 21227 AAAA TQZZA Ed.03

7 BTS Functional Architecture
This chapter describes how the primary functions of a G1/G2 BTS are mapped
onto a functional architecture.
3BK 21227 AAAA TQZZA Ed.03 75 / 184

7.1 Introduction to BTS Functional Architecture

The hardware required to implement the functions of the functional blocks
depend on the hardware variants and the functional units architecture.
There are two hardware variants; G1 BTS Mark2 and G2 BTS. One type of
functional unit architecture exists, G1/G2 BTS architecture.
7.2 G1/G2 BTS Architecture

The G1 BTS Mark2 and the G2 BTS have the same functional architecture.
The G1 BTS Mark2 covers only GSM 900, the G2 BTS covers GSM 900
and GSM 1800.
7.2.1 Functional Units

The G1/G2 BTS contains the following functional units:
BIE
Frame Unit
Station Unit
Carrier Unit
Coupling Unit.
Each functional unit can use a number of different submodule types, depending
upon hardware variant and BTS configuration.
The BIE is not described in an individual section, it is included in the Frame Unit
description and is also mentioned in the Station Unit description.
76 / 184 3BK 21227 AAAA TQZZA Ed.03

7.2.2 Functional Block Diagram

The functional units and their interfaces are shown in the following figure.
Mobile Stations BTS
Terminal
MMI
FHI FHI
RF Carrier Frame BSI
Unit 1 Unit 1
Clocks Clocks
Coupling
Unit
FHI FHI
RF Carrier Frame BSI
Unit n * Station BIE Base
Clocks Unit Clocks Unit n * Station
Antennae Controller
DCL1
DCL2 BSI
* n <= 8 * n <= 8
Transmission
Air Interface
Interface Coupling Unit Carrier Unit Station Unit Frame Unit Equipment
Figure 11: G1/G2 BTS Functional Units Breakdown
7.2.3 Interfaces
The following table describes the interfaces shown in the previous figure.
DCL1 Connects the FU to the OMU. DCL1 provides high-speed transfer of

downloaded software, operational parameters and alarms.
DCL2 (V.11 Q1) Connects the OMU to all other intelligent equipment. This equipment
(for example, CUs) requires only the transfer of parameters and alarm
signals.
Clock links Provides the clock distribution.
FHI Provides internal data transfer.
BSI Provides external communication with the BSC via the BIE.
MMI Provides control via a local BTS Terminal.
Table 9: Principal G1/G2 BTS Interfaces
3BK 21227 AAAA TQZZA Ed.03 77 / 184

7.3 Mapping of Functional Blocks to Functional Units

The BTS functional blocks are mapped onto the G1/G2 BTS functional units as
shown in the following tables:
Table 10 - Transmission
Table 11 - Telecommunication Baseband
Table 12 - Telecommunication RF
Table 13 - O&M
Table 14 - Support.
7.3.1 Transmission
Functional Block G1 BTS G2 BTS
Multiplexing Nokia * SMBI *
Transmission of Signalling Nokia * SMBI *
Transmission of O&M Data Nokia * SMBI *
Transmission of Traffic Nokia * SMBI *
Clock Synchronization Nokia * SMBI *
Table 10: Functional Block to Functional Unit Mapping - Transmission
* These functional units are not described in this document.
78 / 184 3BK 21227 AAAA TQZZA Ed.03

7.3.2 Telecommunication Baseband
Functional Block G1/G2 BTS
Rate Adaptation Frame Unit
Channel Encoding and Decoding Frame Unit
Interleaving/De-interleaving Frame Unit
Encryption/Decryption Frame Unit
Demodulation Frame Unit
Antenna Diversity Carrier Unit,

Frame Unit
Radio Link Recovery Frame Unit
Radio Resource Indication Frame Unit
Paging Frame Unit
DTX Frame Unit
DRX Frame Unit
Quality Measurement Frame Unit
Power Control Frame Unit
Clock Distribution Frame Unit
Protocol Management Frame Unit
Radio Channel Management Frame Unit
Transcoder Time Alignment Frame Unit
Table 11: Functional Block to Functional Unit Mapping - Telecommunication Baseband
3BK 21227 AAAA TQZZA Ed.03 79 / 184

7.3.3 Telecommunication RF
RF Carrier Generation Carrier Unit
Frequency Hopping - Realized by Station Unit
Frequency Hopping - Performed by Station Unit
Frequency Hopping - Controlled by Station Unit
GMSK Modulation Carrier Unit
Up-conversion Carrier Unit
Power Amplification and Power Control Carrier Unit
Power Coupling and Detection Carrier Unit
Channel Selection and Conversion Carrier Unit
Signal Amplification Carrier Unit
A-D Conversion Carrier Unit
Digital Pre-processing Carrier Unit
Control the Status of the RF Hardware Carrier Unit
Clock Selection and Supervision Station Unit
Program the Local Oscillators/Frequency Synthesizers Carrier Unit
Handle Control and Alarm Processing Carrier Unit
Select the High or Low Gain Path on the Uplink Carrier Unit
Downlink Isolating Coupling Unit
Downlink Combining Coupling Unit
Downlink Duplexing Coupling Unit
Downlink Power Coupling and Detection Coupling Unit
Uplink Antenna Pre-amplification Coupling Unit
Uplink Low Noise Pre-amplification (RFE function) Coupling Unit
Uplink Signal Splitting (Duplexing) Coupling Unit
Table 12: Functional Block to Functional Unit Mapping - Telecommunication RF
80 / 184 3BK 21227 AAAA TQZZA Ed.03

7.3.4 O&M
Configuration Management Station Unit,

Frame Unit
Fault Management Station Unit,

Frame Unit
Dedicated Alarm Handling Station Unit
External Alarm Handling Station Unit
Central Command Control Station Unit,

Frame Unit
Configuration/Initialization Station Unit,

Frame Unit
Software Replacement Station Unit,

Frame Unit
Configuration Parameter File Management Station Unit
Testing Station Unit
Alarm Detection, Filtering and Correlation Station Unit
Alarm Forwarding Station Unit
Alarm Translation Station Unit
Command Translation Station Unit
Table 13: Functional Block to Functional Unit Mapping - O&M
7.3.5 Support
Clock Generation and Distribution Station Unit
External Alarm Collection Station Unit
Internal Self-tests Station Unit,

Frame Unit,
Carrier Unit
Table 14: Functional Block to Functional Unit Mapping - Support
3BK 21227 AAAA TQZZA Ed.03 81 / 184

82 / 184 3BK 21227 AAAA TQZZA Ed.03

8 G1/G2 BTS Functional Units
This chapter describes the breakdown of the G1 BTS Mark2 and G2 BTS
into their functional units:
Frame Unit
Station Unit
Carrier Unit
Coupling Unit.
The following information is provided for each functional unit:
Short functional description of each unit’s functions
List of external interfaces

List of hardware modules on which the functions are realized
Mapping of hardware modules against functions
Possible configurations.
3BK 21227 AAAA TQZZA Ed.03 83 / 184

8.1 G1/G2 BTS Functional Units Breakdown

The G1/G2 BTS contains the following functional units:
Frame Unit
Station Unit
Carrier Unit
Coupling Unit.
Each functional unit can use a number of different submodule types, depending
upon hardware variant and BTS configuration.
The functional units and submodules are described in the subsequent sections.
8.2 G1/G2 BTS Frame Unit

The Frame Unit performs baseband processing on traffic and signalling
between the BTS Air Interface and the Abis Interface. It also provides a range
of O&M functions.
The Frame Unit:
Adapts downlink traffic and signalling to a format suitable for transmission

over the Air Interface.
Under control of the BSC, maps the logical channels onto physical channels
for the downlink.
Processes uplink samples delivered by the Carrier Unit, to recover the

baseband data.
Monitors its own status, and the status of its external interfaces.
84 / 184 3BK 21227 AAAA TQZZA Ed.03

8.2.1 G1/G2 BTS Frame Unit Functional Entities

The principal functional entities in a Frame Unit are shown in the following figure.
DCL1
OMU
(located
in Station
Unit) Traffic Traffic
Encoder
Clock Links
Frame Clock Frame Unit
Station Unit Controller
Unit
BSI
Frequency Control
FHI Base Station Abis
Station Hopping Clocks Interface
Links Interface Interface
Unit LAPD Adaptater
Channel
Demodulator Decoder
Traffic Traffic Traffic
Figure 12: G1/G2 BTS, Frame Unit Functional Entities and Interfaces
The figure shows the non-diversity case. When Antenna Diversity is used, the
uplink path for both traffic and signalling is duplicated. This duplication starts
at the antenna and continues up to the output of the Channel Decoder. The
functions of the duplicated path are identical to those of the non-diversity case
described in the following sections.
The principal functional entities in a Frame Unit are:
Frame Unit Controller

Encoder
Channel Decoder
Demodulator
FHI
FCLU
BSIA.
3BK 21227 AAAA TQZZA Ed.03 85 / 184

The following table shows how the Frame Unit functions map on to the Frame
Unit functional entities. In some cases, a single functions can be split between
more than one entity.
Base
Frame Frequency Frame Station
Unit Channel Hopping Clock Interface
Functions Controller Encoder Decoder Demodulator Interface Unit Adapter
Rate Adaptation - X X - - - -
Channel Encoding/ - X X - - - -
Decoding
Interleaving/ - X X - - - -
De-interleaving
Encryption/ Decryption X X - X - - -
Demodulation - - - X - - -
Antenna Diversity X - X X - - -
Discontinuous X X X - - - -
Transmission
Protocol Handling X X X X - - -
Radio Channel X X X X - - -
Management
Radio Resource X - X - - - -
Indication
Paging X - - - - - -
Transcoder Time X X X X - - -
Alignment
Quality Measurements X - X - - - -
Power Control X X X - - - -
Frame Unit X X X X - - -
Downloading
Frame Unit X X X X X X X
Configuration
Frame Unit Control X (X) (X) (X) (X) (X) (X)
Fault Management X X X X X X X
RF Self-test X X X X - - -
Performance X - X X - - -
Measurements
Trace and Debug X - - - - - -
Off-line Tests X X X X X X X
- (X) = Self-control- - - - -
Table 15: G1/G2 BTS, Distribution of Frame Unit Functions between Frame Unit Functional Entities
86 / 184 3BK 21227 AAAA TQZZA Ed.03

8.2.1.1 Frame Unit Controller

The Frame Unit Controller handles the protocol management for Layers 2
and 3, which implement the following telecommunications and O&M functions:
Radio Channel Management
Power Control
Quality Measurements
Paging
Maintenance
Time Synchronization.
The Frame Unit Controller manages the following protocols:
Layer 2 - LAPDm
The LAPDm protocol operates over the BTS -Mobile Station link. It is
responsible for ensuring error free, point-to-point communications 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 3 entities, via the Air Interface.
Layer 2 - LAPD
The LAPD 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 Frame Unit and the BSC. It also carries
information between Layer 3 entities via the subscriber network interface.
8.2.1.2 Encoder
The Encoder processes baseband data for the downlink. It provides the
following functions:
Rate Adaptation
Transcoder Synchronization
Baseband functions, depending on logical channel type:

Channel Encoding
Interleaving
Encryption
Burst Building and TDMA Multiframe Building.
Power Control
DTX functions.
3BK 21227 AAAA TQZZA Ed.03 87 / 184

8.2.1.3 Channel Decoder

The Channel Decoder processes uplink information carried by one time slot
of the TDMA frame. The Decoder performs complex processing on the
demodulated and decrypted data, which involves the following stages:
Antenna diversity combining
Quality estimation for link control
De-interleaving
Convolutional decoding
Block decoding
FACCH detection
Signalling packet extraction
Silence Indication frame detection
Rate Adaptation
Inband control of Transcoder

Processing of test data
Filtering of TOA
Filtering of received signal level
Carrier Unit monitoring
Access burst decoding

Filtering of RF self-test parameters.
The Channel Decoder produces two parameters for signal quality. These relate
to measurements made during a SACCH multi-frame, over a full set of TDMA
frames, and a subset of TDMA frames, respectively. The Channel Decoder
sends these parameters to the Frame Unit Controller.
88 / 184 3BK 21227 AAAA TQZZA Ed.03

8.2.1.4 Demodulator
The Demodulator processes the complex samples of the digital baseband
corresponding to one time slot within a TDMA frame. It performs the following
functions:
Buffering of the digitized samples
Decryption
GMSK demodulation
Estimation of the channel impulse response
TOA estimation
Estimation and correction of the carrier frequency offset
Equalization based on the estimated channel impulse response
Soft decision output
SNR measurement
Frame Unit and Carrier Unit RF self-tests.
8.2.1.5 Frequency Hopping Interface

The FHI connects the Frame Unit to the Frequency Hopping function in the
Station Unit, via high-speed serial links. In this way the Frame Unit is interfaced
to the Carrier Unit via the Station Unit.
8.2.1.6 Frame Clock Unit

The FCLU provides timing for all functions in the Frame Unit. It is locked to the
Station Unit, where the master time reference in the BTS is generated. The
FCLU generates the time slot clock, and distributes these signals.
8.2.1.7 Base Station Interface Adaptor
The BSIA controls:
Selection and supervision of up to two incoming BSIs.
Parallel to serial conversion between the Channel Decoder and the BSI
for the TCH.
Electrical adaptation to the Channel Encoder for TCH, and to/from the
Frame Unit Controller for signalling channels.
3BK 21227 AAAA TQZZA Ed.03 89 / 184

8.2.2 G1/G2 BTS Frame Unit External Interfaces

As shown in Figure 12 , the Frame Unit exchanges data with external entities
through four different types of interface. These are described in the following
table.
BSI Links 0 & 1 These provide links with the BSC (LAPD management)
and the Transcoder (TRAU) frame management).
Only one link is used at a time; BSI Link 1 is used
only if BSI Link 0 is down.These links exchange
telecommunications parameters with the BSC.
Clock Links 0 & 1 These links provide clocks to the BTS units. During
normal operation, both clock links are used to carry the
same information, providing a level of redundancy.The
links provide the Frame Unit with two clock signals and
the Frame Number.
FHI Links 0 & 1 These links enable the Frame Unit to communicate
with the Station Unit’s Frequency Hopping function:
FHI link 0 allows the Frame Unit to communicate

with Frequency Hopping function 1
FHI link 1 allows the Frame Unit to communicate

with Frequency Hopping function 2.
During normal operation, both FHI links are used. In
the case of no antenna diversity they carry the same
information, thus providing an element of redundancy.
DCL1 The DCL1 allows communication with the Station Unit.

It is managed using the Token Passing Bus Access
Method. This interface receives O&M commands,
configuration data and downloaded software, and
sends alarms and commands to the Station Unit.
Note that communication between Frame Units is not
possible via this interface.
Table 16: G1/G2 BTS, Frame Unit, External Interfaces
90 / 184 3BK 21227 AAAA TQZZA Ed.03

8.2.3 G1/G2 BTS Frame Unit Submodules

Depending upon the configuration, the Frame Unit contains a specific set of
submodules that is dependent on the following BTS hardware configurations:
G1 BTS Mark2
G2 BTS.
8.2.3.1 G1 BTS Mark2

The G1 BTS Mark2 BTS Frame Unit contains:
FUCO
CECC
DMAD
DMOD
CDEC
FUIF
DRFU
DRFE.
8.2.3.2 G2 BTS
The G2 BTS Frame Unit contains either a single-board or or a three-board
Frame Unit:
The single-board Frame Unit:

DRFU
The three-board Frame Unit (only if the GPRS feature is not implemented on
the network) with:
FUCO
FICE
DADE.
3BK 21227 AAAA TQZZA Ed.03 91 / 184

8.2.4 G1/G2 BTS Frame Unit Submodule Functions

The following table lists the functional entities against the Frame Unit
submodules that physically contain those entities.
Functional Entity G1/Mark2 G2

1) 1)
Frame Unit Controller FUCO FUCO
DRFU DRFU
Encoder CECC FICE

DRFU DRFU
Channel Decoder CDEC DADE

DRFU DRFU
Demodulator DMOD DADE

DMAD DRFU
DRFU
Frequency Hopping Interface FUIF FICE

DRFU DRFU
Frame Clock Unit FUIF FICE

DRFU DRFU
Base Station Interface Adapter FUIF FICE

DRFU DRFU
DRFE
Table 17: G1/G2 BTS, Frame Unit Functional Entities and Submodules
1)
(Only if the GPRS feature is not implemented on the network.)
92 / 184 3BK 21227 AAAA TQZZA Ed.03

8.2.5 G1/G2 BTS Frame Unit Configurations

8.2.5.1 G1 BTS Frame Unit
There are two G1 BTS Frame Unit configurations:
Mark2 multi-board (Only if the GPRS feature is not implemented on the

network.)
Mark2 single-board.
Both following figures show the possible configurations.

The following figure shows the G1 BTS Mark2 multi-board Frame Unit, without
antenna diversity.
Data
CECC
Clocks Clocks
MCLU or
MCLR
Data
FHIs DMOD
FQHU Clocks
FUIF
Data Control
Data
CDEC
BSIs Clocks
BSC
Clocks
DCL1 FUCO
OMUA
Figure 13: G1 BTS, Mark2 Multi-board Frame Unit (Without Antenna Diversity)
Note: If antenna diversity is used, the DMAD replaces the DMOD.

The single-board DRFU and the DRFE can replace the Mark2 multi -board
Frame Unit for half-rate and enhanced full-rate channels.
The following figure shows the G1 BTS Mark2 single-board Frame Unit DRFU
with the DRFE.
MCLU or Clocks
MCLR
FHIs
FQHU
DRFU
BSIs
BSC
DCL1 DCL1
OMUA DRFE
Figure 14: G1 BTS Mark2 Single-board Frame Unit
3BK 21227 AAAA TQZZA Ed.03 93 / 184

8.2.5.2 G2 BTS Frame Unit

There are two G2 BTS Frame Unit configurations:
Three-board (Only if the GPRS feature is not implemented on the network.)
Single-board.
Both following figures show the possible configurations.

The following figure shows the G2 BTS three-board Frame Unit, with or without
diversity.
Data
Clocks
STSE or STSR or STSP
Data
DADE
FHIs
FICE Clocks
BSIs
BSC Control
Clock
DCL1 FUCO
SCFE
Figure 15: G2 BTS Three-board Frame Unit
The G2 BTS single-board Frame Unit DRFU can replace the G2 BTS
three-board Frame Unit. For reasons of physical size, high power BTSs must
use the single-board Frame Unit. For half-rate and enhanced full-rate channels,
the DRFU must be used.
The following figure shows the G2 BTS single-board Frame Unit.
Clocks
FHIs
DRFU
BSIs
BSC
DCL1
SCFE
Figure 16: G2 BTS Single-board Frame Unit
94 / 184 3BK 21227 AAAA TQZZA Ed.03

8.3 G1/G2 BTS Station Unit

The Station Unit interfaces the Frame Unit to the Carrier Unit, and provides the
main O&M functions for the BTS. These O&M functions are:
Download the BTS software from the BSC
Continuously monitor the operation of the BTS
Generate the main clocks for the BTS

Provide switching for the frequency hopping function.
8.3.1 G1/G2 BTS Station Unit Functions

The Station Unit contains the following functions:
Master Clock Generation
Master Clock Selection and Supervision

Timing Signal Generation
Clock Distribution
Master Clock Control
Message Control
Frequency Hopping
O&M
External Alarm Connection
RF Self-test.
3BK 21227 AAAA TQZZA Ed.03 95 / 184

The following figure shows the logical functions of the Station Unit together
with its internal interfaces.
DCL2 Master
Message Clock
Control Control
Clocks (duplicated links)

Carrier
Units
FHI links Timing Master Master

Carrier Clock Signal Clock Clock
Units Distribution Generation Selection & Generation
Supervision
Frequency DLC2
Hopping
FHI links
Frame Units
Frequency
Number Clocks (duplicated links) Frame Units
Timing and switching (& Slave BTS)
(duplicated)
Coupling
Unit RF Self−test DLC2
RF self−test
Control DCL2 Other Intelligent
BTS Submodules
Dedicated
Alarms/
Control DCL1
Frame Units
Non− Dedicated DLC2
intelligent Alarm and
BTS Cotrol
Components Handling DLC2 BSI
O&M BIE BSC (via Abis
Interface)
External MMI
Alarm External
Sources Alarm BTS
Connection Terminal
Figure 17: G1/G2 BTS, Station Unit Logical Functions and Interfaces
96 / 184 3BK 21227 AAAA TQZZA Ed.03

8.3.2 G1/G2 BTS Station Unit External Interfaces

As shown in the previous figure, there are seven types of Station Unit interface
described in the following table.
BSI The BSI connects the OMU to the BSC via the Abis
Interface using the BIE.
FHI The FHI link carries traffic and control data from the Frame
Units to the Station Unit, and from the Station Unit to the
Carrier Units (and vice-versa).
Clock Links These duplicated links distribute the clocks to the Carrier
Units, Frame Units, RF self-test function and collocated
slave BTSs.
DCL1 DCL1 is a high-speed link between the OMU and Frame

Units. As well as carrying alarm and status information,
the DCL1 is used for software downloading to the Frame
Units.
DCL2 DCL2 is a slower link connecting to all other intelligent

equipment (for example, Carrier Units) that only require
parameter and alarm transfer.
Dedicated Non-intelligent BTS submodules are connected via

Alarm and dedicated, simple alarm and control lines.
Control
MMI The MMI allows the connection of an operator’s terminal,

through which the BTS can be locally controlled.
Table 18: G1/G2 BTS, Station Unit, External Interfaces
3BK 21227 AAAA TQZZA Ed.03 97 / 184

8.3.3 G1/G2 BTS Station Unit Submodules

Depending upon the configuration, the Station Unit contains a specific set of
G1 BTS Mark2
G2 BTS (GSM 900, GSM 900 Extended Cell, and GSM 1800).
8.3.3.1 G1 BTS
The G1 BTS Station Unit contains:
MFGE
MFPG (PCM)
MCLU (for master BTSs)
MCLR (for slave BTSs)

FQHU
OMUA
EACB
EAIB
RTEM.
8.3.3.2 G2 BTS
The G2 BTS Station Unit contains:
SCFE
SACE
SRSE (for master BTSs)
STSP (for master BTSs)

STSR (for slave BTSs)
ESTS (for master BTSs)
ESTR (for slave BTSs)
RTEG or RTED.
98 / 184 3BK 21227 AAAA TQZZA Ed.03

8.3.4 G1/G2 BTS Station Unit Submodule Functions

The following table indicates the functions performed by the Station Unit
submodules.
G2/GSM 900
Function G1 G2/GSM 900 Extended Cell G2/GSM 1800
Master Clock Generation MFGE STSE ESTS STSE

MFGP STSP STSP
Master Clock Selection and MCLU STSE ESTS STSE

Supervision
STSP STSP
Timing Signal Generation MCLU STSE ESTS STSE

MCLR STSP ESTR STSP
STSR STSR
Clock Distribution MCLU STSE ESTS STSE

MCLR STSP ESTR STSP
STSR STSR
Master Clock Control MCLU STSE ESTS STSE

MCLR STSP ESTR STSP
STSR STSR
Message Control MCLU STSE ESTS STSE

MCLR STSP ESTR STSP
STSR STSR
Frequency Hopping FQHU STSE ESTS STSE

STSP ESTR STSP
STSR STSR
Operations and Maintenance OMUA SCFE SCFE SCFE
Dedicated Alarm and Control EACB SCFE/SACE SCFE/SACE SCFE/SACE

Handling
External Alarm Connection EAIB SCFE/SACE SCFE/SACE SCFE/SACE
RF Self-test RTEM RTEG RTEG RTED
Table 19: G1/G2 BTS, Station Unit Functions and Submodules
3BK 21227 AAAA TQZZA Ed.03 99 / 184

8.3.5 G1/G2 BTS Station Unit Configurations

8.3.5.1 G1 BTS Station Unit
The following figure shows the G1 BTS Station Unit used in a master BTS.
MCLRs in Slave BTS
(for synchronization)
Carrier Units 1...16

Frame Units 1...16
Clocks Clocks
FHI
Frame Units 1...16
FQHU
FHI
Carrier Units 1...16
MFGE
or MCLU
MFGP
Combiner
RTEM
Receiver Front−End
External Alarm Inputs

DCL 2
EAIB
Control Outputs
BSIs "Non−Intelligent"
OMUA EACB 1 Units within the
Station Cabinet
MMI DCL 1 DCL2
DCL2
BSC BTS Frame Carrier Units (1...4)
Terminal Units
EACB 2
"Non−intelligent" Units
DCL2
DCL2 Carrier Units (5..16)
EACB n
"Non−intelligent" Units
Figure 18: G1 BTS Station Unit (Master)
100 / 184 3BK 21227 AAAA TQZZA Ed.03

The configuration of the G1 BTS Station Unit equipment depends on the type of
master clock generation. That is, whether the BTS is a:
Free-running master
PCM synchronized master
Slave.
In slave BTSs (which repeat their timing signals from a local master), the
duplicated MFGEs/MFGPs are not used. The MCLRs replace the duplicated
MCLUs.
8.3.5.2 G2 BTS Station Unit

The configuration of G2 BTS Station Unit equipment depends on the type of
master clock generation. That is whether the BTS is a:
Free-running master
PCM synchronized master
Slave.
Both following figures show the possible G2 BTS Station Unit configurations.
The following figure shows a G2 BTS single-carrier (master/slave) Station Unit.
STSE Clocks/Data
Master/ Clocks 1) or Carrier Unit
Slave BTS STSP
or Clocks/Data
ESTS Frame Unit
DCL2
Carrier Units, and
other "Intelligent"
Units
External Alarms Alarm DCL1
Frame Units
BSC BSIs
SCFE Alarms/
MMI Control
BTS Terminal "Non−intelligent" Units
1) to slave BTS in case of a master Station Unit

from Master BTS in case of a slave Station Unit
Figure 19: G2 BTS Single-carrier Station Unit
3BK 21227 AAAA TQZZA Ed.03 101 / 184

The following figure shows a G2 BTS multi-carrier (master/slave) Station

Unit, with redundancy.
Clock/Data Carrier Units

Master/ Clocks 1) STSE Clock/Data
Slave BTS or Frame Units
STSP Clocks
RTEG/RTED
Alarms DCL1
External Alarm Frame Units
BSIs DCL2
BSC SCFE Carrier Units, RTEG/RTED
Alarms/ and other "Intelligent" Units
MMI Control
BTS Terminal "Non−intelligent" Units
Alarms/
Alarms Control
External Alarms SACE "Non−intelligent" Unit
1) to slave BTS in case of a master Station Unit

from Master BTS in case of a slave Station Unit
Figure 20: G2 BTS Multi-carrier Station Unit with Redundant Timing and
Switching Functions
102 / 184 3BK 21227 AAAA TQZZA Ed.03

8.4 Carrier Unit

The Carrier Unit interfaces the digital baseband signals present in the Frame
Unit, to the RF signals used on the Air Interface.
To achieve this, the Carrier Unit:
Generates and modulates the RF carrier for the downlink
Dynamically regulates power on the downlink for each time slot

Receives RF signals transmitted by the Mobile Station on the uplink
Delivers a preprocessed uplink signal to the Frame Unit, ready for

demodulation.
The Carrier Unit is described in the following sections:
Functions
External Interfaces
Submodules
Submodule Functions.
8.4.1 G1/G2 BTS Carrier Unit Functions

The Carrier Unit performs the following functions:
Control
Downlink:
GMSK Modulation
Up-conversion
Power Amplification
Power Coupling and Detection.
Uplink:
Down-conversion
A-D Conversion
Digital Pre-processing.
3BK 21227 AAAA TQZZA Ed.03 103 / 184

A block diagram of a non-diversity Carrier Unit is shown in the following figure.

Downlink Direction
RF out Power I
Coupling Power Up− Q GMSK
and Detection Amplification conversion Modulation
Clocks
Oscillator
DCL2
Station
Unit
FHI1
Frequency
Control Hopping *
Interface FHI2
Oscillator Osillator
RF in I
Down− Signal Q A−D Digital
conversion Amplification Conversion Pre−processing
* FHI Links
Uplink Direction
Figure 21: G1/G2 BTS, Non-diversity Carrier Unit Functions
When Antenna Diversity is used, the uplink path for both traffic and signalling
is duplicated. This duplication starts at the antenna and continues up to
the output of the Channel Decoder in the Frame Unit. The functions of the
duplicated path are identical to those of the non-diversity case described in the
following sections.
104 / 184 3BK 21227 AAAA TQZZA Ed.03

8.4.2 G1/G2 BTS Carrier Unit External Interfaces

The interfaces that link the Carrier Unit with other BTS units are shown in the
previous figure and can be split into two types:
Interfaces to the Coupling Unit

Interfaces to the Station Unit.
8.4.2.1 Interfaces to the Coupling Unit

There are two interfaces from the Carrier Unit to the Coupling Unit in a
non-diversity configuration. A diversity configuration includes an additional
uplink RF input.
The interfaces are:
RF output
The downlink RF signal is output to the Coupling Unit for transmission via
the antenna.
RF input.
The uplink RF signal from the receive antenna is input to the Carrier Unit
from the Coupling Unit. In the case of antenna diversity there are two
RF inputs.
8.4.2.2 Interfaces to the Station Unit

There are three interfaces from the Carrier Unit to the Station Unit:
FHI
The FHI connects the Carrier Unit to a link switch in the Station Unit. This
routes each time slot to the appropriate Frame Unit. The data sent over
this link comprises the receive data, transmit data and test data. Two FHI
links operate in parallel, which meets the requirement either for antenna
diversity or redundancy.
Clock interface
The Clock interface includes the following clock signals from the Station Unit:
REFCLK (13 MHz)
OBCLK (2.16 MHz)
FCLK (216 Hz)
Two links provide redundancy.
DCL2.
The DCL2 Interface is the bidirectional link between the Carrier Unit and
OMU in the Station Unit. Via this interface the Station Unit handles the
Carrier Unit configuration and fault management.
3BK 21227 AAAA TQZZA Ed.03 105 / 184

8.4.3 G1/G2 BTS Carrier Unit Submodules

Depending upon the configuration, the Carrier Unit contains a specific set of
G1 BTS Mark2
G2 BTS GSM 900
G2 BTS GSM 1800.

The G1 BTS Mark2 Carrier Unit contains:
TXUA
TXAL
TXAH
RXUA
RXAS.
8.4.3.2 G2 BTS GSM 900

The G2 BTS GSM 900 BTS Carrier Unit contains:
TXGM
TXGH
TEGM
RXGD.
8.4.3.3 G2 BTS GSM 1800

The G2 BTS GSM 1800 BTS Carrier Unit contains:
TXDH
RXDD.
106 / 184 3BK 21227 AAAA TQZZA Ed.03

8.4.4 G1/G2 BTS Carrier Unit Submodule Functions

The next three tables indicate the functions which the Carrier Unit submodules
perform:
Control function submodules

Downlink function submodules
Uplink function submodules.
8.4.4.1 Control Function Submodules

The following table shows the Carrier Unit control function submodules.
G2/ G2/
Function G1 GS M900 GSM 1800
Control Functions TXUA TXGM TXDH

TXAL TXGH
TXAH TEGM
Table 20: G1/G2 BTS, Carrier Unit Control Function Submodules
8.4.4.2 Downlink Function Submodules

The following table shows the Carrier Unit downlink function submodules.
G2/ G2/
Function G1 GSM 900 GSM 1800
GMSK Modulation TXUA TXGM TXDH

TXAL TXGH
TXAH TEGM
Up-conversion TXUA TXGM TXDH

TXAL TXGH
TXAH TEGM
Power Amplification TXUA TXGM TXDH

TXAL TXGH
TXAH TEGM
Power Coupling and Detection TXUA TXGM TXDH

TXAL TXGH
TXAH TEGM
Table 21: G1/G2 BTS, Carrier Unit Downlink Function Submodules
3BK 21227 AAAA TQZZA Ed.03 107 / 184

8.4.4.3 Uplink Function Submodules

The following table shows the Carrier Unit uplink function submodules.
G2/ G2/
Function G1 GSM 900 GSM 1800
Down-conversion RXUA RXGD RXDD

RXAS
Signal Amplification RXUA RXGD RXDD

RXAS
A-D Conversion RXUA RXGD RXDD

RXAS
Digital Pre-processing RXUA RXGD RXDD

RXAS
Table 22: G1/G2 BTS, Carrier Unit Uplink Function Submodules
108 / 184 3BK 21227 AAAA TQZZA Ed.03

8.4.5 G1/G2 BTS Carrier Unit Configurations

8.4.5.1 G1 BTS Carrier Unit
The following figure shows the G1 BTS Carrier Unit, with antenna diversity.
RF in
(Diversity) Receiver
(Diversity)
Coupling Unit
RF in
Receiver
Control Data
RF out
Coupling Unit Transmitter
FHIs DCL2 Clocks
SU
Figure 22: G1 BTS Carrier Unit (Antenna Diversity)
Note: Where antenna diversity is not used, only one receiver is employed.
The various G1 BTS receiver/transmitter types can only be used in the
combinations TXUA/RXUA, TXAL/RXAS, TXAH/RXAS. Within any one BTS,
the transmitter/receiver types cannot be mixed. Antenna diversity operation
requires the use of two receivers per Carrier Unit.
3BK 21227 AAAA TQZZA Ed.03 109 / 184

8.4.5.2 G2 BTS Carrier Unit

The following figure shows the G2 BTS Carrier Unit.
RF in
(Diversity)
Coupling Receiver
Unit RF in
Control Data
RF out
Coupling Transmitter
Unit
FHIs DCL2 Clocks
SU
Figure 23: G2 BTS Carrier Unit
110 / 184 3BK 21227 AAAA TQZZA Ed.03

8.5 G1/G2 BTS Coupling Unit

The Coupling Unit interfaces the Carrier Unit with the transmit and receive
antennas. The Coupling Unit:
Ensures the efficient transfer of RF power to the transmit antenna
Enables all BTS transmitters to share a single antenna
Protects the Carrier Unit from damage by reflected RF power

Allows BCCH recovery in the event of Carrier Unit failure
Isolates the transmit frequencies from the receiver
Enables the receiver to share the transmit antenna
Provides pre-amplification of the received uplink signal.
The Coupling Unit functions are:
Downlink functions (BTS to Mobile Station)

Uplink functions (Mobile Station to BTS).
The Coupling Unit is described in the following sections:

Functions
External Interfaces
Submodules
Submodule Functions.
3BK 21227 AAAA TQZZA Ed.03 111 / 184

8.5.1 G1/G2 BTS Coupling Unit Functions

The Coupling Unit functions are divided into two types:
Downlink
Uplink.
8.5.1.1 Downlink Functions

The Coupling Unit downlink functions performed by combiners are:
Isolation and Reflected Power Load

Summing
Transmit Filter
Antenna Directional Coupling
Antenna VSWR Alarm Unit

RTC Control
BCCH-Carrier Recovery.
The following figure shows a simplified block diagram of the downlink coupling
functions and interfaces.
Isolation
with Load Transmitter 1
Transmit
Antenna
Transmit
Filter Isolation Transmitter 2
with Load
Antenna
RF Self−test Directional Summing
Coupling
Antenna
Station Unit VSWR
Alarm Unit
Isolation Transmitter n
with Load
Figure 24: G1/G2 BTS, Downlink Coupling Functional Block Diagram
Note: Single-carrier combiners contain no summing function, but provide fault

protection functions.
112 / 184 3BK 21227 AAAA TQZZA Ed.03

8.5.1.2 Uplink Functions

The Coupling Unit uplink functions performed by RFEs are:
Bandpass Filter
Directional Coupling to Test Interface
Power Splitting
Control
Additional Antenna Pre-Amplifier.
The following figure shows the uplink coupling functions and interfaces.
RF Self−test
Antenna
Receiver 1
Directional
Bandpass Coupling Signal Power
Filter to Test Amplification Splitting
Interface Receiver n
Control Station Unit
Figure 25: G1/G2 BTS, Uplink Coupling Functional Block Diagram
The figure shows the non-diversity case. When Antenna Diversity is used, the
uplink path is duplicated. All of the coupling functions are duplicated. These
functions are identical to those of the non-diversity case described in the
following sections.
The Antenna Pre-amplifier’s RFE replaces the normal RFE in BTSs with long,
lossy (2 dB to 8 dB) antenna cables. It consists of two separate sub-modules:
Tower Mounted Amplifier

The Tower Mounted Amplifier is located at the base of the antenna and
provides filtration and initial amplification of the received signal.
Antenna Pre-amplifier RFE

The Antenna Pre-amplifier RFE replaces the usual RFE. It further amplifies
the RF signal from the Tower Mounted Amplifier before dividing it between
the receivers. Fault -tolerant Signal Amplification pairs are employed
whether antenna diversity is used or not.
3BK 21227 AAAA TQZZA Ed.03 113 / 184

The following figure shows a simplified diagram of the Antenna Pre-amplifier.

Receive
Antenna
Tower Mounted Amplifier
Pilot Signal
Filter Tone Amplification
Injection
Long RF Cable
Antenna Pre−amplifier’s RFE

Receiver 1
Pilot Test Signal Pilot Power
Tone Loop Amplification Tone Splitter
Detection Coupling Detection 1 8
Receiver n
Control
Figure 26: G1/G2 BTS, Antenna Pre-amplifier Simplified Block Diagram
114 / 184 3BK 21227 AAAA TQZZA Ed.03

8.5.2 G1/G2 BTS Coupling Unit External Interfaces

The Coupling Unit uses two types of interface:
External interfaces used by the Coupling Unit
External interfaces used by the RFE.
8.5.2.1 External Interfaces used by the Coupling Unit

There are four interfaces used by the Coupling Unit as shown in Figure 24 :
Transmitter RF inputs, where one RF input is provided for each transmitter

output
Antenna RF output, which connects the Coupling Unit output to the transmit
antenna
RF Self-test output, which provides a low power RF output for use in RF

Self-tests
Station Unit Interface, which connects control and alarm signals to and
from the Station Unit.
8.5.2.2 External Interfaces used by the RFE

The RFE has a set of four interfaces as shown in Figure 25 :
Antenna RF input, where a single input allows connection of a receive

antenna
RF Self-test input, which provides the RF input from the RF Self-test function
RF outputs, where a separate RF output is provided for each receiver

in the Carrier Unit
Station Unit Interface, which connects control and alarm signals to/from the
Station Unit.
As shown in Figure 26 , the Antenna Pre-amplifier has an additional

intermediate interface. This carries the pre-amplified received RF signal from
the Tower Mounted Amplifier to the RFE; and a DC power feed from the
RFE to the Tower Mounted Amplifier.
3BK 21227 AAAA TQZZA Ed.03 115 / 184

8.5.3 G1/G2 BTS Coupling Unit Submodules

Depending upon the configuration, the Coupling Unit contains a specific set of
G1 BTS Mark2
G2 BTS GSM 900
G2 BTS GSM 1800.

The G1 BTS Mark2 contains:
CBC2
CBC4
CEC2
CEC4
FBC2
FEC2
FCAV
RXFE
RXDE
RTDE
RTSE
CRFE
CRDE
MCEX
RTMA.
116 / 184 3BK 21227 AAAA TQZZA Ed.03

8.5.3.2 G2 BTS GSM 900

The G2 BTS GSM 900 BTS Coupling Unit contains:
WB1G
WB2G
DUPG
FRBG
FREG
CRBG
CREG
FEG2
FEG8
RMCG
TMAG.
8.5.3.3 G2 BTS GSM 1800

The G2 BTS GSM 1800 BTS contains:
WB2D
DUPD
DUD2
RC4D
RC8D
FED2
FED8
RMCD
TMAD.
8.5.4 G1/G2 BTS Coupling Unit Submodule Functions

The Coupling Unit submodules perform two types of functions:
Downlink
Uplink.
3BK 21227 AAAA TQZZA Ed.03 117 / 184

8.5.4.1 G1/G2 BTS, Coupling Unit Downlink Function Submodules

The following table indicates the Coupling Unit downlink function submodules.
Function G1/Mark2 G2/GSM 900 G2/GSM 1800
Isolation with Power Load FBC2/FCAV/FEC2 WB1G WB2D

CBC2 WB2G DUPD
CBC4/CEC2 DUPG DUD2
CBC4/CEC4 CRBG/CREG RC4D
FRBG/FREG RC8D
Summing FBC2/FCAV/FEC2 WB1G WB2D

CBC2 WB2G DUPD
CBC4/CEC2 DUPG RC4D
CBC4/CEC4 CRBG/CREG RC8D
FRBG/FREG
Transmit Filter FBC2 WB1G WB2D

CBC2 WB2G DUPD
CBC4 DUPG DUD2
CRBG RC4D
FRBG RC8D
Antenna Directional Coupling FBC2 WB1G WB2D

CBC2 WB2G DUPD
CBC4 DUPG DUD2
CRBG RC4D
FRBG RC8D
Antenna VSWR Alarm Unit FBC2 WB1G WB2D

CBC2 WB2G DUPD
CBC4 DUPG DUD2
CRBG RC4D
FRBG RC8D
RTC Control FBC2 CRBG RC4D

CBC2 FRBG RC8D
CBC4
118 / 184 3BK 21227 AAAA TQZZA Ed.03

BCCH-carrier Recovery FBC2 WB1G WB2D

CBC2 WB2G DUPD
CBC4 DUPG DUD2
CRBG RC4D
FRBG RC8D
Integrated Duplexing – DUPG DUPD

DUD2
Table 23: G1/G2 BTS, Coupling Unit Downlink Function Submodules
3BK 21227 AAAA TQZZA Ed.03 119 / 184

8.5.4.2 G1/G2 BTS, Coupling Unit Uplink Function Submodules

The following table indicates the Coupling Unit uplink function submodules.
Bandpass Filter RXFE FEG2 FED2

RXDE FEG8 FED8
RTSE TMAG TMAD
RTDE
CRFE
CRDE
Directional Coupling to Test Interface RXFE FEG2 FED2

RXDE FEG8 FED8
RTSE RMCG RMCD
RTDE
CRFE
CRDE
Signal Amplification RXFE FEG2 FED2

RXDE FEG8 FED8
RTSE RMCG RMCD
RTDE TMAG TMAD
CRFE
CRDE
RTMA
Power Splitting RXFE/MCEX FEG2 FED2

RXDE/MCEX FEG8 FED8
RTSE/MCEX RMCG RMCD
RTDE/MCEX
CRFE
CRDE
Control RXFE FEG2 FED2

RXDE FEG8 FED8
RTSE RMCG RMCD
RTDE
CRFE
CRDE
Additional Antenna Pre-amplifier RTMA/RTSE TMAG/RMCG TMAD/RMCD

RTMA/RTDE
Table 24: G1/G2 BTS, Coupling Unit Uplink Function Submodules
120 / 184 3BK 21227 AAAA TQZZA Ed.03

8.5.5 G1/G2 BTS Coupling Unit Configurations

The configuration of Coupling Unit equipment depends on the number of
transmitters and receivers that are served. The configuration also depends
on the support of antenna diversity.
8.5.5.1 G1 BTS Coupling Unit

The following table shows the possible G1 BTS Coupling Unit configurations,
for various numbers of carriers.
No. of
Carriers Coupling Function Mark2
2 Downlink FBC2 or CBC2
Uplink (non-diversity) CRFE or RXFE/MCEX or

RTMA/RTSE/MCEX
Uplink (diversity) CRDE or RXDE/2 x MCEX or 2 x

RTMA/RTDE/2 x MCEX
4 Downlink FBC2/FCAV or CBC4
Uplink (non-diversity) CRFE or RXFE/MCEX or

RTMA/RTSE/MCEX

RTMA/RTDE/2 x MCEX
6 Downlink FBC2/FCAV/FEC2 or
Uplink (non-diversity) CRFE or RXFE/2 x MCEX or

RTMA/RTSE/2 x MCEX

RTMA/RTDE/4 x MCEX
8 Downlink FBC2/FCAV/2 x FEC2 or

CBC4/CEC4
Uplink (non-diversity) CRFE or RXFE/2 x MCEX or

RTMA/RTSE/2 x MCEX

RTMA/RTDE/4 x MCEX
Table 25: G1 BTS, Coupling Unit Combinations
3BK 21227 AAAA TQZZA Ed.03 121 / 184


The following table shows the possible G2 BTS Coupling Unit configurations for
various numbers of carriers.
No. of
Carriers Coupling Function GSM 900 GSM 1800
1 Downlink WB1G WB2D

WB2G DUPD
DUPG DUD2
Uplink 2 x FEG2 2 x FED2
- 2 x TMAG/RMCG 2 x TMAD/RMCD
2 Downlink WB2G WB2D

DUPG DUPD
DUD2
4 Downlink FRBG RC4D

CRBG RC8D
2 x DUPG 2 x DUPD
2 x DUD2
8 Downlink FRBG/FREG RC8D

CRBG/CREG
Table 26: G2 BTS Coupling Unit Combinations
122 / 184 3BK 21227 AAAA TQZZA Ed.03

8.5.5.3 Downlink Configurations

G1 BTS Coupling Unit The following four figures show the possible G1 BTS
Mark2 Coupling Unit downlink configurations. These show the maximum
number of carriers that each configuration can use.
The following figure shows a G1 BTS Mark2 two-carrier downlink Coupling Unit.
Transmit
Antenna
Transmitter 1 FBC2
or
Transmitter 2 CBC2 RF Self−test
Figure 27: G1 BTS Mark2 Two-carrier Downlink Coupling Unit
The following figure shows the possible G1 BTS Mark2 four-carrier downlink
coupling unit variants.
Transmit
Antenna
Transmitter 1
FBC2
Transmitter 2 RF Self−test
Transmitter 3
FCAV
Transmitter 4
Transmit
Antenna
Transmitter 1
Transmitter 2
Transmitter 3 CBC4
RF Self−test
Transmitter 4
Figure 28: G1 BTS Mark2 Four-carrier Downlink Coupling Unit Variants
3BK 21227 AAAA TQZZA Ed.03 123 / 184

The following figure shows the two possible G1 BTS Mark2 six-carrier downlink
Transmit
Antenna
Transmitter 1
FBC2
Transmitter 3
FCAV
Transmitter 4
Transmitter 5
FEC2
Transmitter 6
Transmit
Antenna
Transmitter 1

Transmitter 3
Transmitter 4
Transmitter 5
CEC2
Transmitter 6
Figure 29: G1 BTS Mark2 Six-carrier Downlink Coupling Unit Variants
124 / 184 3BK 21227 AAAA TQZZA Ed.03

The following figure shows the two possible G1 BTS Mark2 eight-carrier
downlink coupling unit variant.
Transmit
Antenna
Transmitter 1
FBC2
Transmitter 3
FCAV
Transmitter 4
Transmitter 5
FEC2
Transmitter 6
Transmitter 7
FEC2
Transmitter 8
Transmit
Antenna
Transmitter 1
Transmitter 2
Transmitter 4
Transmitter 5
Transmitter 6 CEC4
Transmitter 7
Transmitter 8
Figure 30: G1 BTS Mark2 Eight-carrier Downlink Coupling Unit Variants
3BK 21227 AAAA TQZZA Ed.03 125 / 184

G2 BTS Coupling Unit The following five figures show the possible G2 BTS
Coupling Unit downlink configurations.
The following figure shows the two possible G2 BTS single-carrier downlink
Transmit
Antenna
WB1G
or
Transmitter WB2G
or RF Self−test
WB2D
Transmit
Antenna
DUPG
Transmitter or
Front−End orDUPD RF Self−test
DUD2
Figure 31: G2 BTS Single-carrier Downlink Coupling Unit Variants
The following figure shows the three possible G2 BTS two-carrier downlink
Transmit
Antenna
Transmitter 1 WB2G
or
WB2D RF Self−test
Transmitter 2
Transmit
Antenna
Transmitter 1 DUPG
Transmitter 2 or
DUPD RF Self−test
Front−End
Transmit Transmit
Antenna Antenna
Transmitter 1
Transmitter 2 DUD2
Front−End RF Self−test
Figure 32: G2 BTS Two-carrier Downlink Coupling Unit Variants
The following figure shows the two possible G2 BTS three- to four-carrier
downlink coupling unit variants.
126 / 184 3BK 21227 AAAA TQZZA Ed.03

Transmit
Antenna
Transmit
Transmitter 1 DUPG Antenna
Transmitter 2 or
DUPD RF Self−test
Front−End
Transmitter 3 DUPG
Transmitter 4 or
DUPD RF Self−test
Front−End
(Diversity)
Transmit Transmit
Antenna Antenna
Transmit Transmit
Transmitter 1 Antenna Antenna
Transmitter 2 DUD2
Transmitter 3
Transmitter 4 DUD2
(Diversity)
Figure 33: G2 BTS Three to Four-carrier Downlink Coupling Unit Variants
The following figure shows the G2 BTS single to four-carrier downlink coupling
unit.
Transmit
Antenna
Transmitter 1 FRBG
or
Transmitter 2 CRBG
or
Transmitter 3 RC4D RF Self−test
or
Transmitter 4 RC8D
Figure 34: G2 BTS Single to Four-carrier Downlink Coupling Unit
The following figure shows the G2 BTS single to eight-carrier downlink coupling
unit.
Transmit
Antenna
Transmitter 1
Transmitter 2
FRBG/FREG
or
CRBG/CREG RF Self−test
or
RC8D
Transmitter 8
Figure 35: G2 BTS Single to Eight-carrier Downlink Coupling Unit
3BK 21227 AAAA TQZZA Ed.03 127 / 184

8.5.5.4 Uplink Configurations

G1 BTS Coupling Unit The following four figures show the possible G1 BTS
Mark2 Coupling Unit uplink configurations.
The following figure shows the three possible G1 BTS Mark2 non-diversity, two
to four-carrier uplink coupling unit variants.
Receive
Antenna
Receiver 1
RF Self−test RXFE MCEX
Receiver 4
Receive
Antenna RF Self−test
Receiver 1
RTSE MCEX
RTMA
Long RF Receiver 4
Cable
Receive
Antenna
Receiver 1
CRFE
RF Self−test
Receiver 4
Figure 36: G1 BTS Mark2 Two to Four-carrier Uplink Coupling Unit Variants
128 / 184 3BK 21227 AAAA TQZZA Ed.03

The following figure shows the three possible G1 BTS Mark2 diversity, two to
four-carrier uplink coupling unit variants.
Receive
Antenna
Receiver 1
4−way
Splitter MCEX
RF Self−test
Receiver 4
RXDE Receiver 1
(Diversity)
MCEX
4−way
Receive Splitter
Antenna Receiver 4
(Diversity) (Diversity)
RF Self−test
Receive
Antenna
Receiver 1
RTMA 4−way
Splitter MCEX
Long RF
Receive Cable Receiver 4
Antenna RTDE Receiver 1
(Diversity) (diversity)
4−way MCEX
Splitter
RTMA
Receiver 4
(Diversity)
Long RF
Cable
Receive
Antenna
Receiver 1
4−way
Splitter
RF Self−test Receiver 4
CRDE
Receiver 1
4−way
Receive Splitter
Antenna Receiver 4
(Diversity)
Figure 37: G1 BTS Mark2 Two to Four-carrier Diversity Uplink Coupling Unit
Variants
3BK 21227 AAAA TQZZA Ed.03 129 / 184

The following figure shows the three possible G1 BTS Mark2 non-diversity,
six to eight-carrier uplink Coupling Unit variants.
Receive
Antenna
Receiver 1
MCEX
RF Self−test RXFE
MCEX
Receiver 8
Receive
Antenna
Receiver 1
RF Self−test CRFE
Receiver 8
Receive
Receiver 1
MCEX
RTSE
RTMA
Long RF MCEX
Cable Receiver 8
Figure 38: G1 BTS Six to Eight-carrier Uplink Coupling Unit Variants
130 / 184 3BK 21227 AAAA TQZZA Ed.03

The following figure shows the possible G1 BTS Mark2 diversity, six to
eight-carrier uplink Coupling Unit variants.
Receive Receiver 1
Antenna MCEX
4−way
Splitter
RF Self−test
MCEX
Receiver 8
RXDE
Receiver 1
MCEX
Receive 4−way
Antenna Splitter
(Diversity)
MCEX
Receiver 8
Receive
Antenna
Receiver 1
8−way
Splitter
RF Self−test
Receiver 8
CRDE
Receiver 1
8−way
Receive Splitter
Antenna
(Diversity) Receiver 8
Receive
Receiver 1
MCEX
RTMA 4−way
Splitter
Long RF
Cable MCEX
Receiver 8
Receive
Antenna RTDE
MCEX
4−way
Splitter
RTMA
MCEX
Long RF Receiver 8
Cable
Figure 39: G1 BTS Mark2 Six to Eight-carrier Diversity Uplink Coupling Unit
Variants
3BK 21227 AAAA TQZZA Ed.03 131 / 184


The following three figures show the possible G2 BTS Coupling Unit uplink
funcitons.
The following figure shows the G2 BTS single/two-carrier uplink coupling unit.
Receive
Antenna
or Receiver 1
Duplexer FEG2
or
FED2 Receiver 2
RF Self−test
Receive
Antenna FEG2 Receiver 1
(Diversity) or
FED2 Receiver 2
Figure 40: G2 BTS Single/Two-carrier Uplink Coupling Unit
The following figure shows the G2 BTS single to four-carrier uplink coupling unit.
Receive
Antenna Receiver 1
or
Duplexer FEG8 Receiver 2
or
FED8 Receiver 3
Receive Receiver 1
Antenna
(Diversity) FEG8 Receiver 2
or or
Duplexer FED8 Receiver 3
Receiver 4
Figure 41: G2 BTS Single to Four-carrier Uplink Coupling Unit
132 / 184 3BK 21227 AAAA TQZZA Ed.03

The following figure shows the two possible G2 BTS single to eight-carrier
uplink coupling unit variants.
Receive Receiver 1
Antenna
Receiver 2
FEG8
or
FED8
Receiver 8
Receive Receiver 2
Antenna
(Diversity) FEG8
or
FED8
Receiver 8
RF Self−test
Receive
Antenna
Receiver 1
Receiver 2
TMAG
or RMCG
TMAD or
RMCD
Long RF
Cable
Receiver 8
Receive
Antenna
Receiver 2
RMCG
TMAG or
or RMCD
TMAD
Long RF Receiver 8
Cable
Figure 42: G2 BTS Single to Eight-carrier Uplink Coupling Unit Variants
3BK 21227 AAAA TQZZA Ed.03 133 / 184

134 / 184 3BK 21227 AAAA TQZZA Ed.03

9 Software
9 Software
This chapter describes the BTS software. After providing a general overview, it
describes the:
Definition of firmware and software

Software configuration data
BTS Start-up and initialization
O&M Software
Frame Unit Software
Carrier Unit Software.
3BK 21227 AAAA TQZZA Ed.03 135 / 184

9 Software
9.1 Overview on Software

Many BTS functions are realized or controlled by microprocessors using
associated code. This code is the BTS software.
The BTS software provides services to Layers 1 - 5 in the ISO OSI reference
model.
The BTS software is responsible for:
Initializing, configuring andsupervising the BTS
Software for this purpose comes under the general categoryof O&M. O&M
functions monitor and control the correct operation of the BTS and its
external interfaces. O&M software therefore supports functions for:
Configuration management
Fault management
Performance management.
Realizing the BTS operational functions

The operational software supports a reliable two-way communications path
between the land-based network and Mobile Stations. This path is ’open’
to traffic and signalling meeting GSM standards. For the purpose of this
description, operational software falls into two primary categories:
Telecommunications functions
Transmission functions.
136 / 184 3BK 21227 AAAA TQZZA Ed.03

9 Software
9.2 Software and Firmware

The BTS uses code permanently resident in the units concerned, and code
downloaded after reset or startup. To distinguish between these categories,
resident software is referred to as firmware.
9.2.1 Firmware
Firmware is held in a non-volatile ROM on the unit. It is typically associated
with low-level functions such as self-testing or communication control. As
resident software, it also includes the bootstrap software that performs the initial
boot-up sequence. This establishes input -output mechanisms which allows
access to downloadable software.
9.2.2 Downloaded Software

The BTS downloads software from the BSC, under firmware control.
Downloaded software typically provides high-level functions such as traffic
management or database maintenance.
9.2.3 Software/Firmware Usage

The following table shows the split between firmware and software.
BTS Firmware Only Software and Firmware
G1/G2 BTS Station Unit (External Station Unit (OMU)

Alarm Connection, Timing
and Switching)
- Frame Unit
Carrier Unit -
Coupling Unit Remotely -

Tunable Combiner
Table 27: BTS Firmware/Software Split
3BK 21227 AAAA TQZZA Ed.03 137 / 184

9 Software
9.3 Software Configuration Data

To define the way in which the BTS functions and system control are
implemented, the microprocessor code is supplied with software configuration
data. This data is held in configuration files that are downloaded at start-up or
reset.
The configuration data can therefore be changed only when restarting the
associated function.
The relationship between the software and data files downloaded to the BTS is
shown in the following table.
Bootstrap Operational Loadable Loadable Data

BTS Unit Software Firmware Software Software Files
G1/G2 Station Unit NONVOL NONVOL VOL OMU-SW BTS-MF

BTS Operations &
FU-SCP-SW OMU-CPF
Maintenance
Unit (OMU) FU-MFP-SW OMU-SPF
FUE-SW FU-CPF
Staion Unit NONVOL NONVOL - - -

Timing
Generation
Station Unit NONVOL NONVOL - - -

External Alarm
Frame Unit NONVOL NONVOL VOL FU-SCP-SW FU-CPF

Multi-board
FU-MFP-SW
FUE-SW
Frame Unit NONVOL NONVOL VOL DR-LD-FW FU-CPF

Single-board
DR-SCP-SW
DRFU
DR-MFP-SW
DR-TMUX-SW
DR-BED-SW
DR-ENC-SW
DR-DEC-SW
DR-DEM-SW
Carrier Unit NONVOL NONVOL - - -
Coupling Unit NONVOL NONVOL - - -

RTC
Table 28: Software and Data Held by BTS
Abbreviations used in this table: NONVOL - Non Volatile VOL - Volatile
138 / 184 3BK 21227 AAAA TQZZA Ed.03

9 Software
9.4 BTS Start-up and Initialization

When the BTS is powered-up or reset, a fixed sequence of events occurs.
1. Start-up firmware is executed, including self-tests.
2. Software is downloaded from the BSC.
3. Functions are initialized and software is activated.
The following sections describe these events.
9.4.1 Start-up Firmware

After power-up or reset, the OMU, Frame Unit and all units connected via the
DCL2 (for the G1/G2 BTS) start their firmware. This executes self-test functions
in each unit. The OMU then runs boot procedures to start the operating
system and interface control code.
The following figure shows the sequence of events.
BSC OMU Frame Unit DCL2/ECPL Units
Time
Micro−BTS Power−up
Execute Execute Execute

Self−tests Self−tests Self−tests
Configure Units
Collect Start−up Results
Start
Boot Fimware
* LAPD Link Established
Report OMU Started
Acknowledge
Software and Database

Download
Load Frame Unit
Software
Load Carrier Unit
Software**
Activate Software/Firmware of Each Unit
Report Start−up Results to BSC
* LAPD Link Access Procedure on the D Channel

** Only for Micro−BTS
Figure 43: BTS Start-Up Sequence
3BK 21227 AAAA TQZZA Ed.03 139 / 184

9 Software
9.4.2 BTS Download

When the OMU self-tests are successfully completed, the BSC establishes the
OML between the BSC and the OMU. This uses the LAPD protocol.
Once the OML is running, the OMU sends an ’OMU Started’ message to
the BSC. The BSC then begins the software download to the OMU over the
LAPD connection.
The software download comprises:
Software for the OMU (including database)

Software for the Frame Unit functions
Hardware and software configuration files.
The BSC transfers the BTS software package to the OMU as a set of files.
First, the BSC sends a list of all the files needed by the BTS concerned. The
OMU then requests these files from the BSC.
The first file transferred in the main download is the OMU software, followed by
the OMU software configuration parameter files. The OMU software is then
executed, and the Frame Unit software files are downloaded.
The Frame Unit files contain the Frame Unit operational software and
configuration files. The files are temporarily stored in the OMU RAM. The
download ends with the transfer of O&M configuration parameter files.
140 / 184 3BK 21227 AAAA TQZZA Ed.03

9 Software
9.4.3 BTS Initialization

When the BTS download is complete, the OMU collects all unit start-up test
results. The OMU then configures each of the units and functions as shown in
the following table.
Units and functions

to be initialized G1/G2 BTS
Frame Unit Each Frame Unit is configured by downloading operational software and a
configuration data file from the OMU to the Frame Unit. The OMU initiates the
download by sending a ’Load Frame Unit Software’ message. This instructs the
Frame Unit to handle the transfer. The Frame Unit software is then downloaded.
The Carrier Unit software is stored in the Frame Unit RAM, and is passed to the
Carrier Unit later, via the DCL2/ECPL.
Files are sent to the Frame Unit in fixed-length packets. The Frame Unit calculates
checksums to verify the integrity of the data received. When the operational
software has been loaded, the OMU sends an ’End Frame Unit Download’
message. This is followed by the Frame Unit Configuration Parameter file. The
Frame Unit is then initialized.
After Frame Unit initialization, the RSL is established between the Frame Unit
and the BSC, using the LAPD protocol. Telecommunication function messages
are exchanged over the RSL.
Master Clock Control In a master BTS, the redundant Master Clocks are initialized independently. Both
are subsequently synchronized, then designated as main and standby.
Slave BTSs are provided with clock signals from the master BTS, to which the
repeater functions of the slave BTS are synchronized. The OMU is informed of
the success/failure of the initilaization.
Carrier Unit Initialization of the Carrier Unit is supervised by the OMU, which applies a number
of checks to verify that the start-up sequence has been successful.
The OMU then queries the type of Carrier Unit in use, since this can affect the
configuration parameters which are subsequently downloaded.
External Alarm The OMU sends the External Alarm Connection function a list of settings for the
Connection Function Input/Output ports. Port registers are initialized accordingly and then checked
against the configuration file. A timeout is applied for the completion of the start-up
procedures.
Frequency Hopping Initialization of the Frequency Hopping function is monitored by the OMU to ensure
Function that the start-up sequence has been successful. The Frequency Hopping function
then identifies the type of hardware in use, and the OMU sends an oppropriate
configuration message. This defines the Freuqency Hopping behavior required.
BCCH-Carrier Switch The OMU ensures that the BCCH-Carrier Switch is set to the correct position for
the configuration.
RTC The RTC is initialized by the OMU. The OMU checks if retuning is required to
match the input frequencies to the outputs of the associated Carrier Units. If tuning
is required, the Carrier Units are switched off and the RTC inputs are retuned
using stepper motors. When tuning is complete, the Carrier Units are switched on.
Receiver Front-end The Receiver Front-end function may, or may not, require initialization. This
Function depends on type, and whether or not antenna diversity is used. Redundancy
configuration is initialized where appropriate. In all cases a status check is
performed.
Table 29: BTS Initialization, Units and Functions to be Initialized
3BK 21227 AAAA TQZZA Ed.03 141 / 184

9 Software
9.5 O&M Software

The O&M software manages the BTS O&M procedures. These procedures
can be described as:
Functions
Software Modules.
9.5.1 Functions
The O&M software performs the following functions:
BTS equipment configuration
Frame Unit software download and initialization
Cyclic equipment supervision
Status reporting to the BSC

BTS alarm processing
Local failure recovery handling.
With the exception of one communication handler (for the Q1 Node), all O&M
software runs on the OMU.
At power-up or reset, the following sequence occurs:
1. The BSC downloads the O&M operational software.
2. The BTS hardware is initialized and software is downloaded to the Frame
Unit.
3. The BTS functions are started.
4. When the BTS is operational, the OMU collects alarms from the Frame Unit
and the ECPL Layer 1 entities. The OMU filters the alarms and tries to
implement recovery actions. If no recovery is possible, the OMU sends
appropriate alarms to the BSC.
The SCP provides the Q1 Node function. This supervises the Layer 1 entities,
and indicates any problems to the OMU.
142 / 184 3BK 21227 AAAA TQZZA Ed.03

9 Software
9.5.2 Software Modules

The O&M software is split into a number of modules:
Root System
Application Functions
Support Functions
Interface Handlers
Q1 Node Handler.
Each module contains one or more tasks, the scheduling of which is managed
by a pre-emptive operating system.
9.5.2.1 Root System

The Root System is executed once software downloading is complete. It
performs the following procedures:
Creation and initialization of operating system resources.
Initiation of all tasks for execution under operating system control.
Download of data files.

Initialization of data areas (using BSC configuration data).
Once the execution of root software is complete, the other software modules
start.
3BK 21227 AAAA TQZZA Ed.03 143 / 184

9 Software
9.5.2.2 Application Functions

The application functions shown in the following table perform the primary
OMU processing.
Fuction Description
Initialize BTS The Initialize BTS module initializes and configures each individual BTS unit.
Module
Command The Command Handler provides unit-based handling of BTS O&M procedures.
Handler
The Command Handler processes commands from the Initialize BTS, Configuration
Handler and Central Command Controller modules. It translates the commands from a
function-related form, into a sequence of unit-based O&M actions. The associated units
then initiate these actions.
Central The Central Command Controller handles function-related operations.

Command
Whenever an operational command is entered or an alarm is received, the Central
Controller
Command Controller triggers appropriate actions. The OMU sends messages to the
Command Handler to perform any actions required. Function-related information in the
database is updated accordingly.
Configuration The Configuration Handler manages reconfiguration operations.

Handler
Whenever a reconfiguration command is received, the Configuration Handler generates
a sequence of function-related messages. These are sent to the Command Handler to
perform the required reconfiguration actions. The database is updated accordingly.
Alarm Alarm messages from the BTS units (in unit-based format) are passed to the Alarm
Translator Translator module via DCL1 or DCL2 and the SCP Q1 Node.
Each alarm is translated to a ’raw alarm message’ and then stored in the OMU database.
All alarms are sent to the Alarm Handler for processing.
Alarm The Alarm Handler is responsible for alarm filtering, alarms correlation and BTS fault
Handler localization.
Certain fault conditions can cause false alarms to be reported by indirectly affected units.
Alarms which can be provoked in this way must be correlated to determine the true cause
of the fault, before any action is taken.
Alarms that pass the filtering and correlation process are reported to the BSC. The
appropriate maintenance actions are then initiated via the Central Command Controller.
144 / 184 3BK 21227 AAAA TQZZA Ed.03

9 Software
Fuction Description
Status The Status Reporting Module supplies database information to the BSC and operator.
Reporting
On request, the module scans the OMU database and formats the required information,
Module
before forwarding it to the BSC or BTS Terminal.
Audit n addition to the databases held by each BTS OMU, the controlling BSC also holds a
Manager backup database. This contains function-related information for all of its BTSs.
In order to provide effective backup, the contents of the BSC database must be consistent
with the OMU databases. The OMU can itself request an audit following configuration
failure, recovery failure, or if an OMU fault occurs. At the OMU, this checking procedure is
handled by the Audit Manager.
If differences are found, the database(s) are corrected and fault recovery is initiated if
necessary/possible.
Table 30: O&M Software, Application Functions
3BK 21227 AAAA TQZZA Ed.03 145 / 184

9 Software
9.5.2.3 Support Functions

Support functions provide general facilities that are used by more than one
task. There are many groups of these including:
Database manipulation
Function-related data manipulation

Unit-related data manipulation
Message assembly, format checking, etc.
Time supervision.
Of particular importance are the:
OMU database
It contains information on the whole BTS including its Hardware/software
inventory, Configuration and Status.
Information in the database is held in both function-related (hardware
generation independent), and unit-related (hardware specific) forms. The
hierarchical relationships between the functions/units are also held.
The OMU database does not run as a task. Access is provided through a
suite of functions that can be called by any of the OMU tasks.
Message Route functions

The Message Router provides a flexible mechanism for the internal
distribution of messages. This avoids the need for hard-coded message
distribution in each task.
Each task sends a ’message table’ to the Message Router. This contains
a distribution list for each message type the task issues, and a reception
list detailing the message types the task wants to receive.
When a task wants to send a message to another task, it sends the
message to the Message Router. The Router distributes the message to
tasks in the appropriate distribution list, if they are flagged to receive
that message type.
146 / 184 3BK 21227 AAAA TQZZA Ed.03

9 Software
9.5.2.4 Interface Handlers

A number of Interface Handler modules as shown in the following table manage
the communication between BTS entities.
DCL1 The DCL1 communication code is divided into OSI Layers 2, 3

and 4. Layer 2 is sub-divided into two sub-layers:
MAC packet-level transfer sub-layer
LLC acknowledged connectionless service (LLC type 3)

sub-layer.
DCL1 Layer 3 code performs message format and translation
functions. It is also responsible for the periodic status polling
of the Frame Unit. Layer 4 code handles software download
to the Frame Unit.
DCL2 DCL2 communication is organized in a half-duplex master-slave

arrangement. The master sends command messages to
numbered slave(s), which reply when a command is received. A
slave cannot begin transmission without receiving a command.
DCL2 participates in exchanges at Layers 2, 3 and 4. These
layers are all handled by a single module. This interfaces the
upper layers and the single byte frames used on the physical
connection. DCL2 responsibilities include status polling carried
out for the OMU. The physical layer monitors for reception errors
and operates timeout checking.
OML The OML communication operates in two modes. These are for:
Software Download
Alarm and message transfer between the BSC and the OMU.
OML Layer 2 code employs LAPD signalling. Layer 3 code
converts data between the OMU internal format and the GSM
frame format used on the OML.
MMI The MMI enables a local BTS Terminal to be connected to the

OMU. This allows test results, status and alarm information to be
accessed by the operator. In addition, service commands can
be issued such as ’Initialize’ or ’Disable’ particular equipment.
The MMI uses a full-duplex RS-232 link. The BTS Terminal is
a personal computer which runs special application software to
communicate with the OMU.
Table 31: O&M Software, Interface Handlers
3BK 21227 AAAA TQZZA Ed.03 147 / 184

9 Software
9.6 Frame Unit Software

The Frame Unit software provides control and baseband data processing,
corresponding to Layers 1 to 3 in the OSI 7-Layer communications model.
The software is split into the following components:
SCP Control Functions
MFP Control Functions

Encoder
Demodulator and Channel Decoder.
Further control software supervises the generation of timing signals.
9.6.1 SCP Control Functions

The SCP software handles O&M and telecommunications procedures. These
procedures can be described as:
Functions
Software modules.
9.6.1.1 Functions
The SCP functions are:
O&M functions:
Frame Unit tests
SCP software downloading
Frame Unit and Carrier Unit software downloading
Management of configuration parameters
Management of reconfiguration parameters
Software integrity verification
Control of Frame Unit mode of operation
Supervision and fault management
LAPD link supervision
Processor overload supervision
RACH load measurements.
Telecommunications functions:
LAPD protocol handling
LAPDm protocol handling
Layer 3 protocol handling
Telecommunication configuration message processing
Radio Channel management
Error handling of telecommunications software.
148 / 184 3BK 21227 AAAA TQZZA Ed.03

9 Software
9.6.1.2 Software Modules

The SCP software is split into a number of modules:
Root System
Interface Handlers.
Each module contains one or more tasks. The scheduling of these tasks is
managed by a pre-emptive operating system.
9.6.2 MFP Control Functions

The MFP is the physical interface between the SCP and the Layer 1 entities.
The MFP software handles the low-level O&M and telecommunications
procedures under control of the SCP. These procedures are:
Functions
Software modules.
9.6.2.1 Functions
The MFP functions are:
O&M functions:
Managing the initialization and configuration of the Layer 1 entities.
Supervising the external interfaces (fault management).
Supervising the Layer 1 entities (hardware and software failure).
Managing the exchange of messages between the SCP and Frame Unit
and Carrier Unit entities.
Telecommunications functions:
Managing the synchronization (frame number).
Managing the multiframe configuration.
Routing the telecommunications messages.
9.6.2.2 Software Modules

The MFP software is split into a number of modules:
Root System
Interface Handlers.
Each module contains one or more tasks. The scheduling of these tasks is
managed by a pre-emptive operating system.
3BK 21227 AAAA TQZZA Ed.03 149 / 184

9 Software
9.6.3 Software States of the Control Functions

The SCP and MFP functions are implemented as a FSM, with six primary
states described in the following table.
State Description
Power Off In the Power Off state no internal functions are available.
Initialization The SCP operates under control of the OMU. During Initialization, which follows power-up
or reset, the SCP performs self-tests and attempts to communicate with the OMU. If this is
successful, it then initializes the MFP which performs its own self-tests and communicates
the results to the SCP.
When both subsystems are initialized, the SCP determines the status of the Frame Unit,
including all entities.
Initialization is completed when the SCP configures the MFP and all the Layer 1 Entities.
The Frame Unit is now ready to begin operational processing.
150 / 184 3BK 21227 AAAA TQZZA Ed.03

9 Software
State Description
Operational The SCP and MFP enter their Operational states following successful initialization.
In this state the principal task of the SCP is to activate, manage and deactivate the
channels. These functions are performed under BSC control.
SCP operational tasks also involve exchanges of information with the OMU that relate to:
Alarm reports
Configuration/reconfiguration
MFP debugging interface
Supervision of the Frame Unit status.

Frame Unit supervision detects faults in the Frame Unit itself, or in other BTS equipment
that has an impact on the Frame Unit.
In the Operational state, the MFP is primarily responsible for managing the multiframes for
different configurations of the radio channels. This task consists of:
Obtaining configuration details from the SCP
Sending this information to the Encoder or Channel Decoder, and to the Demodulator.
This must be done early enough to allow these entities to perform the right action at
the right time.
Other MFP functions include message routing between the SCP and the Layer 1 Entities.
These messages form an essential part of the following functions:
Routing transcoder alignment message from the Encoder to the Channel Decoder
Handling channel configuration messages during handover procedures

Synchronizing the MFP and Layer 1 Entities
Monitoring the interface.

Abnormal behavior in the Operational state triggers alarms that can be classified as follows:
Fatal alarms; the Frame Unit cannot handle BTS to Mobile Station communications
Non-Fatal alarms; the Frame Unit can handle BTS to Mobile Station communications in
a degraded mode.
The MFP warns the SCP of all detected alarms.
3BK 21227 AAAA TQZZA Ed.03 151 / 184

9 Software
State Description
Fault The Fault Localization state is entered from the Operational state following the detection of
Localization a fatal incident and from any state after a reset.
Non-fatal alarms are reported by a message to the OMU.
In the case of a fatal alarm (i.e., due to hardware), the MFP stops its own processing and
waits to be restarted by the SCP.
In the case of a fatal error (i.e., due to software or protocol), the MFP stops its processing
and stores the cause of the error.
For both hardware and software errors, when the MFP is restarted by the SCP it indicates
the cause of the problem. Localization is therefore always reported at the level of BTS, and
a limited recovery strategy is available. First, a restart is attempted. If this is unsuccessful,
the OMU commands a reset. If this fails, the RA SBL is set to FOS. The OMU then
activates an Frame Unit reset.
Out of Order The Out of Order state is entered if a fatal failure is detected or when a software download
or reconfiguration fails.
No supervision is performed in this state, so the Frame Unit can exit the state only as the
result of an external event. The SCP therefore requests a reset from the OMU.
Standby The Standby state is entered from the Fault Localization state if fatal external link failures
are detected. On removal of the fault, the Frame Unit initiates its own recovery and
informs the OMU.
Table 32: SCP and MFP Functions, States of the FSM
9.6.4 Encoder
The Encoder implements the following primary funcitons:
BSI time slot management
Rate Adaptation for the data and speech traffic channels

Transcoder time alignment
FACCH bit stealing
Channel encoding and burst building
Burst control
Transmitter power control

Encryption.
152 / 184 3BK 21227 AAAA TQZZA Ed.03

9 Software
9.6.5 Demodulator and Channel Decoder

The Demodulator and Channel Decoder each require dedicated software.
9.6.5.1 Demodulator
The Demodulator processes the physical channels received from the BBI on
the uplink, and passess the processed data to the Channel Decoder. The datat
is recieved from the FHI as complex samples produced by the Carrier Unit.
The Demodulator performs the following functions for each channel:
GMSK demodulation
Carrier frequencies offset compensation, estimation, filtering

Channel impulse response estimation
TOA estimation
Matched filtering
Equalization
Soft decision
Testing.
There is also a Decryption function, which occurs just before the data is
passed to the Channel Decoder. This is performed in the BED, configured by
the Demodulator software.
The MFP uses the ID_CHC messages to send the uplink decryption keys,
the decryption flag and the algorithm type flag to the Demodulator. The
Demodulator extract this information, adds the fram number, and sends the
combined data to the BED. Only nomal bursts are decrypted.
3BK 21227 AAAA TQZZA Ed.03 153 / 184

9 Software
9.6.5.2 Channel Decoder

The Channel Decoder reassembles logical channels from the bursts of data
received from the Demodulator.
The Channel Decoder identifies bursts using channel configuration messages
received from the MFP. The burst process is therefore controlled in real-time,
using a special operating system.
During burst processing, the Channel Decoder performs the following functions:
De-interleaving
Burst processing control

Carrier Unit monitoring
TOA filtering
Received signal level filtering
RACH load measurements.
The reassembled blocks are then processed. Block processing involves the
following functions:
Convolutional decoding
Block decoding
Bit reordering
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.
154 / 184 3BK 21227 AAAA TQZZA Ed.03

9 Software
9.7 Carrier Unit Software

The Carrier Unit provides an interface between the BTS baseband data and the
radio signals used by Mobile Stations. On the downlink, this is achieved by
the transmitter(s), on the uplink by the receiver(s).
9.7.1 Transmitter
The transmitter transforms the digital baseband data sent from the Encoder
(transmit data), into a GSM radio signal for the downlink.
G1/G2 BTS The principal tasks of the transmitter firmware are to monitor and
control the flow of this data through the various stages used to procedure
the GSM signal.
These functions are sub-divided into:
CUC firmware tasks, including:

Data transfer between Carrier Unit and FHIs
DCL2 communication
Receiver supervision and transfer of received data.
Power Control and Alarms (PCA) firmware tasks, include:

Supervision of transmit data-transfers
Output power control
Status monitoring and alarm generation
Data validity checking.
A watch-dog function resets the transmitter in the event of a firmware crash.
9.7.2 Receiver
The receiver transforms radio signals received via the Air Interface, to an analog
baseband signal. This is then sampled to produce a digital representation that
is sent to the Frame Unit for demodulation and further processing.
These tasks are logically and physically divided into two parts:
Analog receiver
Digital receiver.
9.7.2.1 Analog Receiver

The analog part of the receiver operates under control of the transmitter
processor and digital receiver part. It performs the following functions:
Low noise amplification
Down conversion
IF filtering
IQ GMSK demodulation and baseband filtering
A-D conversion.
3BK 21227 AAAA TQZZA Ed.03 155 / 184

9 Software
9.7.2.2 Digital Receiver

The digital part of the receiver monitors and controls the signal processing. In
addition, it optimizes the performance of the analog part of the receiver.
From the A-D converter, the uplink data stream is divided into blocks, each
block corresponding to a time slot. The Data Input and Data Processing
functions, to which the blocks are subjected, run as a continuous loop operating
on one data block per loop, as shown in the following table.
Function Description
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 vonverter to an internal memory
buffer.
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. Each sample is taken from a buffer and processed as follows:
DC Offset A DC offset is calculated to counteract DC variations in the D-A

Calculation converter and other analog hardware. This value is subtracted from
all samples in each time slot.
Power The receiver provides the alternatives of high and low gain signal
Calculation path. This allows wide variations in received signal strength to be
and Path accommodated. The signal power of the I and Q components at
Selection the output of each signal path is calculated. This is done for each
individual time slot. The results are used to select the output from the
high or low gain reicever path for further processing.
RSSI RSSI is based on the power input level measured at the antenna
connector. The RSSI value is used by the BSC to calculate the
optimum RF power level for the Mobile Station.
Scaling Factor The receiver A-D converter produces 12-bit data. From this, only
Calculation 8-bits representing the most significant part of the signal are required.
These are calculated by multiplying samples from the selected signal
path by a coefficient. The coefficient is inversely proportional to the
received signal strength. This ensures that the samples passed to
the demodulator represent similar amplitudes, regardless of received
signal strength.
Frequency To simplify the demodulation in the Frame Unit, the Frequency

Translation Translation funciton performes initial pre-processing of the signal.
This involves multiplying the samples by a complex coefficient.
Fault Checking Ongoing checks are performed for each time slot during operation. These checks
verify that data is sent to the uplink Baseband Interface 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 MFP.
Table 33: Digital Receiver, Functional Sub-Entities
156 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
10 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 Object/SBL to RIT relationships.
3BK 21227 AAAA TQZZA Ed.03 157 / 184

10 BTS Objects
10.1 Managed Objects and SBL Description

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

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

Mapping
CCF CCF Telecom None.
O&M Cools down the BTS boards to maintain them within their
environmental temperature range.
Hardware BTS cooling fans equipment.

Mapping
CLLK CLLK 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.
Hardware Frequency generator and clock distribution units.

Mapping
CU CU 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 Carrier Units (transmitter/receiver boards and power sources).

Mapping
A transmitter/receiver board contains the GSM/DCS modulator,
UHF up/down converter and amplifiers.
158 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
Managed
EACB EACB Telecom None.
O&M Performs the following actions:

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.
Hardware EACB equipment.

Mapping
FHU FHU 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 FHU
Mapping
FU FU 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 signaling 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.).
Hardware FU boards
Mapping
FU_TS Telecom None.
3BK 21227 AAAA TQZZA Ed.03 159 / 184

10 BTS Objects
Managed
O&M Addresses a particular baseband channel of the FU particularly for

configuration purposes.
Performs RTE loop test on addressed baseband channels.
Hardware None.
Mapping
OMU OMU 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.
Hardware OMU/SUM board

Mapping
RA RA 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.
160 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
Managed
Hardware Receiver Front-End

Mapping
FU power supplies
CU power supplies
Transmission combiners rack (cavities + cabling)
BCCH switch.
RTE Telecom None.
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 RTE
Mapping
Table 34: BTS Managed Object and SBL Descriptions
3BK 21227 AAAA TQZZA Ed.03 161 / 184

10 BTS Objects
10.2 BTS SBLs

The following tables list the Managed Objects and SBLs for the G1 BTS Mark 2,
and G2 BTS.
Managed Object SBL Type Description
BTS BTS Base Transceiver Station
CCF CCF Cabinet Cooling Fan
CLLK CLLK Clock Link
CU CU Carrier Unit
EACB EACB External Alarm Collection Board
FHU FHU Frequency Hopping Unit
FU FU Frame Unit
- FU_TS Frame Unit Time Slot
OMU OMU Operations and Maintenance Unit
RA RA Radio Access
- RTE Radio Test Equipment
Table 35: G1 BTS and G2 BTS Managed Objects and SBLs
162 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
10.3 BTS Managed Object (SBL) Hierarchy

The Managed Object (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 Object (SBL) hierarchy within the BTS, the
OMU/SUM also reports to the OMC-R the following information:
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 (G1 BTS Mark 2 and G2 BTS).
Note: The following SBL hierarchies show only those SBLs reported to the OMC-R.
BTS
1234 123456 123456
1234 123456 123456
1234 123456 123456
CCF* EACB* OMU CLLK1 CLLK2
123456OR 123456
123456 1234567
123456 1234567
123456
FHU 1
1234567
FHU 2
1234561234567 OR
RTE RA
FU* CU*
FU−TS*
*: means that the box represents several instances of the SBL.

Figure 44: G1 BTS and G2 BTS Managed Object (SBL) Hierarchy Reported by
the OMU/SUM to the OMC-R
3BK 21227 AAAA TQZZA Ed.03 163 / 184

10 BTS Objects
10.4 Allowed Managed Object and SBL States of the G1 BTS

Mark 2 and G2 BTS
The allowed states for Managed Objects and SBLs of the G1 BTS and G2 BTS
are shown in the following tables.
There is no Managed Object eqivalent to the SBL state NEQ.
10.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 36: Allowed States of Managed Object Abis_PCM (SBL Abis-HWAY-TP)
10.4.2 Allowed States of Managed Object (SBL) BTS
MSD Unlocked No change - Suspended
Table 37: Allowed States of Managed Object (SBL) BTS
164 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
10.4.3 Allowed States of Managed Object (SBL) CCF
OPR Locked No change - -
NEQ - - - -
Table 38: Allowed States of Managed Object (SBL) CCF
10.4.4 Allowed States of Managed Object (SBL) CLLK
FOS Unlocked Disabled Off-Line/Disabled -
NEQ (1) - - - -
Table 39: Allowed States of Managed Object (SBL) CLLK
(1) The NEQ state is only allowed for the FHU and CLLK SBLs for specific
G2 BTS configurations, where non-redundancy is implemented. The state is
not permitted for G1 BTS Mark 2 configurations.
3BK 21227 AAAA TQZZA Ed.03 165 / 184

10 BTS Objects
10.4.5 Allowed States of Managed Object (SBL) CU
SOS Unlocked Disabled Dependency -
NEQ - - - -
Table 40: Allowed States of Managed Object (SBL) CU
10.4.6 Allowed States of Managed Object (SBL) EACB
NEQ - - - -
Table 41: Allowed States of Managed Object (SBL) EACB
166 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
10.4.7 Allowed States of Managed Object (SBL) FHU
NEQ (1) - - - -
Table 42: Allowed States of Managed Object (SBL) FHU
(1) The NEQ state is only allowed for the FHU and CLLK SBLs for specific
G2 BTS configurations, where non-redundancy is implemented. The state is
not permitted for G1 BTS Mark 2 configurations.
10.4.8 Allowed States of Managed Object (SBL) FU
NEQ - - - -
Table 43: Allowed States of Managed Object (SBL) FU
3BK 21227 AAAA TQZZA Ed.03 167 / 184

10 BTS Objects
10.4.9 Allowed States of SBL FU_TS
IT - - - -
SOS - - - -
MSD - - - -
MSA - - - -
UT - - - -
NEQ - - - -
Table 44: Allowed States of SBL FU_TS
10.4.10 Allowed States of Managed Object (SBL) OMU
MSA (2) Unlocked No change - Suspended
Table 45: Allowed States of Managed Object (SBL) OMU
(2) The OMU SBL can only have the state MSA when performing an
Auto-Restart or Auto-Reset. Since no commands are handled by the OMU
until it is completely operational, its MSA state is never seen by the operator
except from the BTS terminal.
168 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
10.4.11 Allowed States of Managed Object (SBL) RA
Table 46: Allowed States of Managed Object (SBL) RA
10.4.12 Allowed States of SBL RTE
IT - - - -
FIT - - - -
FLT - - - -
SOS - - - -
OPR - - - -
MSD - - - -
MSA - - - -
NEQ - - - -
Table 47: Allowed States of SBL RTE
3BK 21227 AAAA TQZZA Ed.03 169 / 184

10 BTS Objects
10.5 Allowed Managed Object and SBL Actions for the G1 BTS
Mark 2 and G2 BTS
The Managed Object and SBL commands which are allowed for the Managed
Objects and SBLs of the G1 BTS and G2 BTS are indicated by a checkmark
(X) in the following table.
Managed
Object
Command Unlock Lock Restart Reset Shutdown
Read
SBL Command Status Initialize Disable Restart Reset
Managed
Object/SBL
Type
BTS X - - X X -
CCF X X X - - X
CLLK X X X - - X
CU X X X - - X
EACB X - - - - -
FHU X X X - - X
FU X X X X X X
FU_TS X - - - - -
OMU X - - X X -
RA X X X - - X
RTE (1) X X X - - -
Table 48: Allowed Managed Object and SBL Commands for the G1 BTS and G2 BTS
(1) The OMC-R does not furnish the RTE-loop-test operations.
170 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
10.6 G1 BTS Mark 2 RITs

G1 BTS Mark 2 RITs are listed in the following table.
G1 BTS Mark O&M

RIT Name RIT Function 2 RITs Controlled
BPSU Booster Power Supply Unit X X
CBC2 Celwave Basic Combiner for Two Carriers X X
CBC4 Celwave Basic Combiner for Four Carriers X X
CDEC Channel Decoder X X
CEC2 Celwave Extension Combiner for Two Carriers X X
CEC4 Celwave Extension Combiner for Four Carriers X X
CECC Channel Encoder Encryption X X
CFSR Cooling Fan Subrack X X
CFSU Cooling Fan Subunit X X
CFT1 Cooling Fan Type 1 X X
CFT2 Cooling Fan Type 2 X X
CLDB Clock Distribution Board X X
CPDB Cabinet Power Distribution Board X -
CRDE Celwave Receiver Front-End with Antenna Diversity X X
CRFE Celwave Receiver Front-End without Antenna Diversity X X
DMAD Demodulator with Antenna Diversity X X
DMOD Demodulator without Antenna Diversity X X
DRFE Dual Rate Frame Unit Extension X X
DRFU Dual Rate Frame Unit X X
EACB External Alarm Collection Board X X
EAIB External Alarm Interconnection Board X -
ECF2 Forem Extension Combiner for Two High-Power Carriers X -
FBC2 Forem Basic Combiner for Two Carriers X X
FCAV Forem Supplementary Combiner for Two Carriers X X
FEC2 Forem Extension Combiner for Two Carriers X X
FQHU Frequency Hopping Unit X X
FUCO Frame Unit Controller X X
3BK 21227 AAAA TQZZA Ed.03 171 / 184

10 BTS Objects
G1 BTS Mark O&M

RIT Name RIT Function 2 RITs Controlled
FUIF Frame Unit Interface X X
MCEX Multicoupler Extension X -
MCLR Master Clock Repeater X X
MCLU Master Clock Unit X X
MFGE Master Frequency Generator X X
MFGP Master Frequency Generator PCM X X
OMUA Operations and Maintenance Unit Type A X X
RTDE Receiver Front-End with Antenna Diversity (Tower mounted) X X
RTEM Radio Test Equipment Mark 1/Mark 2 X X
RTMA Receiver Tower Mounted Amplifier X X
RTSE Receiver Front-End without Antenna Diversity (Tower X X

Mounted)
RXAS Receiver (Mark 2) X X
RXDE Receiver Front-End with Antenna Diversity X X
RXFE Receiver Front-End without Antenna Diversity X X
SUPS Station Unit Power Supply X X
TAMF Forem Transmit Antenna Measuring Unit X X
TBCF Booster Cooling Fan X X
TBPS Transceiver Booster Power Supply X X
TCFB Top Cooling Fan Board X X
TCFU Top Cooling Fan Unit X X
TCPS Transceiver Power Supply X X
TXAH Transmitter Amplifier High Power X X
TXAL Transmitter Amplifier Low Power X X
TXBM Transmitter Booster Module X X
TXUA Transmitter Unit Type A X X
Table 49: G1 BTS Mark 2 RITs
172 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
10.7 G1 BTS Mark 2 SBLs and RITs Reported to the OMC-R

The G1 BTS SBLs and RITs reported to the OMC-R are listed in the following
table.
SBL G1 BTS Mark 2 RITs
BTS OMUA, SUPS
CCF CFSU, TBCF, TCFB, TCFU
CLLK CLDB, MCLR, MCLU, MFGE, MFGP
RA CBC2, CBC4, CEC2, CEC4,CRDE, CRFE, FBC2, FCAV,

FEC2, RTDE, RTMA, RTSE, RXDE, RXFE, TAMF
CU BPSU, RXAS, TBPS, TCPS, TXAH, TXAL, TXBM, TXUA
EACB EACB
FHU FQHU
FU CDEC, CECC, DMAD, DMOD, DRFE, DRFU, FUCO,

FUIF, TCPS
FU_TS None
OMU OMUA
RTE RTEM
Table 50: G1 BTS MARK 2 SBLs and RITs Reported to the OMC-R
3BK 21227 AAAA TQZZA Ed.03 173 / 184

10 BTS Objects
10.8 G2 BTS RITs

G2 BTS RITs are listed in the following table.
RIT RIT GSM O&M

Name Function 900 GSM 1800 GSM 1900 Controlled
ADPS AC/DC Power Supply X X X X
BBU2 Battery Backup Unit 12 Ah X X X -
BCU1 Battery Control Unit 1 X X X -
BHPS Battery and Heat Power Supply X X X -
BU60 Battery Unit 60 Ah X X X -
CFU1 Cooling Fan Unit 1 U X X X X
CFUA Cooling Fan Unit Additional X X X X
CFUT Cooling Fan Unit Top X X X X
COB1 Connection Box 1 (Power) X X X -
COB2 Connection Box 2 (Data) X X X -
CRBG Celwave Remotely Tunable Combiner X - - X

Basic GSM
CREG Celwave Remotely Tunable Combiner X - - X

Extension GSM
CUDP Carrier Unit Dummy Panel X X X -
DADE Demodulator and Channel Decoder with X X X X

Antenna Diversity
DCDB Device Control Distribution Board X X X -
DRFU Dual Rate Frame Unit X X X X
DUD2 Duplexer DCS for Two Transmitters - X - X
DUPD Wideband Combiner Two Carrier with - X - X

Integrated Duplexer
DUPG Receiver Duplex GSM X - - X
DUPP Wideband Combiner Two Carrier with - - X X

Integrated Duplexer
EADB External Alarm Distribution Board X X X -
FCPS Frame/Carrier Power Supply X X X X
FED2 Receiver Front-End D800 for Two Carriers - X - X
174 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
RIT RIT GSM O&M

FED8 Receiver Front-End DCS 1800 for Eight - X - X

Carriers
FEG2 Receiver Front-End GSM for Two Carriers X - - X
FEG8 Receiver Front-End GSM for Eight X - - X

Carriers
FEP8 Receiver Front-End DCS 1900 for Eight - - X X

Carriers
FICE Frame Unit Interface and Channel X X X X

Encoder
FRBG Forem Remotely Tunable Combiner Basic X - - X

GSM
FREG Forem Remotely Tunable Combiner X - - X

Extension GSM
FUCO Frame Unit Controller X X X X
FUDP Frame Unit Dummy Panel X X X -
HEAT Heating Unit X X X -
HEX1 Heat Exchanger 1 X X X -
HEXU Heat Exchanger Unit X X X -
LPQG Lightning Protector Quarter Wave GSM X X X -
LPSG Lightning Protector Spark Gap X X X -
MBPS Mini-BTS Power Supply X X X X
MCIB Mini-BTS Cabinet Indoor Connection Box X X X -
MDSW Mini-BTS Door Switch X X X -
PM06 Power Module 0.6 kW X X X -
PM08 Power Module 0.8 kW X X X -
PSI1 Power Supply Interface Type 1 X X X -
PSI2 Power Supply Interface Type 2 X X X -
RC4D Remotely Tunable Combiner for Four - X - X

Carriers DCS
RC8D Remotely Tunable Combiner for Eight - X - X

Carriers DCS
3BK 21227 AAAA TQZZA Ed.03 175 / 184

10 BTS Objects
RIT RIT GSM O&M

RMCD Receiver Multicoupler DCS - X - X
RMCG Receiver Multicoupler GSM X - - X
RTED Radio Test Equipment Unit for DCS - X - X
RTEG Radio Test Equipment Unit GSM X - - X
RXDD Receiver DCS 1800 with Antenna - X - X

Diversity
RXGD Receiver GSM with Antenna Diversity X - - X
RXPD Receiver DCS 1900 with Antenna - - X X

Diversity
SACE Station Unit Alarm Collection Entity X X X X
SCFE Station Unit Control Function Entity X X X X
STSE Station Unit Timing and Switching Entity X X X X

Master
STSP Station Unit Timing and Switching Entity X X X X

PCM Master
STSR Station Unit Timing and Switching Entity X X X X

Repeater
TMAD Tower Mounted Amplifier DCS - X - X
TMAG Tower Mounted Amplifier GSM X - - X
TXDH Transmitter DCS1800 25 W - X - X
TXDM Transmitter DCS 1800 15 W - X - X
TXGH Transmitter GSM 50 W X - - X
TXGM Transmitter GSM 30 W X - - X
TXPH Transmitter DCS 1900 25 W - - X X
WB2D Wideband Combiner DCS for Two - X - X

Carriers
WB2G Wideband Combiner GSM for Two X - - X

Carriers
Table 51: G2 BTS RITs
176 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
10.9 G2 BTS SBLs and RITs Reported to the OMC-R

The G2 BTS SBLs and RITs reported to the OMC-R are listed in the following
table.
SBL RITs for GSM 900 RITs for GSM 1800 RITs for GSM 1900
BTS ADPS, MBPS, SCFE ADPS, MBPS, SCFE ADPS, MBPS, SCFE
CCF CFU1, CFUA, CFUT CFU1, CFUA, CFUT CFU1, CFUA, CFUT
CLLK STSE/STSP/STSR STSE/STSP/STSR STSE/STSP/STSR
RA CRBG, CREG, DUPG, DUD2, DUPD, FED2, DUPP, FEP8

FEG2, FEG8, FRBG, FED8, RC4D, RC8D,
FREG, RMCG, TMAG, RMCD, TMAD, WB2D
WB2G
CU FCPS, MBPS, RXGD, FCPS, MBPS, RXDD, RXPD, TXPH

TXGM, TXGH TXDM, TXDH
EACB SCFE/SACE SCFE/SACE SCFE/SACE
FHU STSE/STSR/STSP STSE/STSR/STSP STSE/STSR/STSP
FU DRFU DRFU DRFU

For FU3: DADE, FCPS, For FU3: DADE, FCPS, For FU3: DADE, FCPS,
FICE, FUCO, MBPS FICE, FUCO, MBPS FICE, FUCO, MBPS
For FU2: FCPS, MBPS For FU2: FCPS, MBPS For FU2: FCPS, MBPS
FU_TS None None None
OMU SCFE SCFE SCFE
RTE RTEG RTED -
Table 52: G2 BTS SBLs and RITs Reported to the OMC-R
3BK 21227 AAAA TQZZA Ed.03 177 / 184

10 BTS Objects
10.10 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 (X). A dash (-)
indicates that no LED is present. 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 t the G2 BTS Hardware Description .
178 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
10.10.1 G1 BTS Mark 2 RITs with Corresponding RBL and LED

Indications
RIT Name RBL Green LED Red LED Yellow LED
BPSU CUi X - -
CBC2 RA X X -
CBC4 RA X X -
CDEC FUi X X -
CEC2 RA - - -
CEC4 RA - - -
CECC FUi X X -
CFSR CCF X X -
CFSU CCF - - -
CLDB CLLK X - -
CRDE RA - - -
CRFE RA - - -
DMAD FUi X X -
DMOD FUi X X -
DRFE FUi X X -
DRFU FUi X X X
EACB N/A - X -
FBC2 RA X X -
FCAV RA - - -
FEC2 RA X - -
FQHU RA X X X
FUCO FUi X X X
FUIF FUi X X -
MCLR CLLK X X -
MCLU CLLK X X -
MFGE CLLK - - -
3BK 21227 AAAA TQZZA Ed.03 179 / 184

10 BTS Objects
MFGP CLLK X X -
OMUA N/A X X X
RTDE RA Yellow for this RIT X X
RTEM RTE - - -
RTMA RA - - -
RTSE RA X X X
RXDE RA Yellow for this RIT X -
RXFE RA Yellow for this RIT X -
RXAS CUi - - -
SUPS N/A X X -
TAMF RA - - -
TBCF CCF X X -
TBPS RA - - -
TCFB CCF - - -
TCFU CCF X X -
TCPS CUi/FUi - - -
TXAL CUi - - -
TXAH CUi - - -
TXBM X X -
TXUA CUi X X -
Table 53: G1 BTS Mark 2 RITs with Corresponding RBL and LED Indications
180 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
10.10.2 G2 BTS (GSM 900/1800/1900) RITs with Corresponding RBLs

and LED Indications
ADPS N/A X - -
BCU1 N/A X X X
BHPS N/A X X -
CFU1 CCF X X -
CFUA CCF - - -
CFUT CCF - - -
DEDE FUi X X -
DRFU FUi X X X
FCPS FUi, CUi X - -
FICE FUi X X X
FUCO FUi X X X
MBPS FUi, CUi X - -
MSPS FUi, CUi X - -
PM06 N/A X X -
PM08 N/A X - -
PSI1 N/A - - -
PSI2 N/A - - -
SACE EACB X X X
SCFE EACB, X X X
OMU
STSE FHU, X X -
CLLK
STSP FHU, X X -
CLLK
STSR FHU, X X -
CLLK
Table 54: G2 BTS (GSM 900/1800/1900) RITs with Corresponding RBLs and LED Indications
3BK 21227 AAAA TQZZA Ed.03 181 / 184

10 BTS Objects
10.10.3 RITs Specific to G2 BTS GSM 900 with Corresponding RBLs

and LED Indications
CRBG RA X X -
CREG RA - - -
DUPG RA - X -
FEG2 RA X X X
FEG8 RA X X X
FRBG RA X X -
FREG RA X - -
RMCG RA X X X
RTEG RTE - - -
RXGD CUi - - -
TMAG RA - - -
TXGH CUi - Red LED 7 segment -

display
TXGM CUi - Red LED 7 segment -

display
WB2G RA - X -
Table 55: RITs Specific to G2 BTS GSM 900 with Corresponding RBLs and LED Indications
182 / 184 3BK 21227 AAAA TQZZA Ed.03

10 BTS Objects
10.10.4 RITs Specific to G2 BTS GSM 1800/1900 with Corresponding

RBLs and LED Indications
DUD2 RA - X -
DUPD RA - X -
DUPP RA - X -
FED2 RA X X X
FED8 RA X X X
FEP8 RA X X X
RC4D RA X X -
RC8D RA X X X
RMCD RA X X X
RTED RTE - - -
RXDD CUi - - -
RXPD CUi - - -
TMAD RA - - -
TXDH CUi - - -
TXDM CUi - X -
TXPH CUi - - -
WB2D RA - X -
Table 56: RITs Specific to G2 BTS GSM 1800/1900 with Corresponding RBLs and LED Indications
3BK 21227 AAAA TQZZA Ed.03 183 / 184

10 BTS Objects
BLANK PAGE BREAK
184 / 184 3BK 21227 AAAA TQZZA Ed.03

Bts Fuctional Description

Uploaded by

Document Information

Original Description:

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

Bts Fuctional Description

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent GSM

BTS Functional Description

3BK 21227 AAAA TQZZA Ed.03

Short title BTS Functional Descr.

2 / 184 3BK 21227 AAAA TQZZA Ed.03

3BK 21227 AAAA TQZZA Ed.03 3 / 184

3.2.6 Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4 / 184 3BK 21227 AAAA TQZZA Ed.03

6.2 Support Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3BK 21227 AAAA TQZZA Ed.03 5 / 184

9.6 Frame Unit Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

6 / 184 3BK 21227 AAAA TQZZA Ed.03

3BK 21227 AAAA TQZZA Ed.03 7 / 184

8 / 184 3BK 21227 AAAA TQZZA Ed.03

3BK 21227 AAAA TQZZA Ed.03 9 / 184

Table 40: Allowed States of Managed Object (SBL) CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

10 / 184 3BK 21227 AAAA TQZZA Ed.03

The logical position of the BTS in the BSS

What’s New In Edition 03

Audience This document is intended for:

Engineers responsible for network and configuration planning

Assumed Knowledge The reader must possess a:

General knowledge of telecommunications systems and terminology

3BK 21227 AAAA TQZZA Ed.03 11 / 184

Good understanding of GSM concepts

12 / 184 3BK 21227 AAAA TQZZA Ed.03

3BK 21227 AAAA TQZZA Ed.03 13 / 184

1.1 BTS Role in a GSM Network

Facilities to transmit and receive appropriate radio signals

Cell-specific O&M functions

Low-level local control, including radio resource management.

14 / 184 3BK 21227 AAAA TQZZA Ed.03

Radio Frequency Signals

Mobile Station BTS BSC BSS

Mobile Station Rest of

Figure 1: Logical Position of BTS in BSS

For systems incorporating GPRS some additional components are required as

Radio Frequency Signals

Figure 2: Logical Position of BTS in BSS with GPRS

3BK 21227 AAAA TQZZA Ed.03 15 / 184

1.1.2 Functional Architecture

Receive Telecommunication Functions

* Diversity configuration only

Dataflow through the BTS in the downlink direction

Dataflow through the BTS in the uplink direction

1.1.3 Channel Organization

16 / 184 3BK 21227 AAAA TQZZA Ed.03

1.2 BTS Functions

Transmission functions, which manage the transfer of traffic and control

O&M functions, which supervise the operation of the BTS.

Communication between the transmission, telecommunications, and O&M

1.2.1 Transmission Functions

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

1.2.2 Telecommunication Functions

1.2.2.1 Baseband Functions

3BK 21227 AAAA TQZZA Ed.03 17 / 184

1.2.3 O&M Functions

Dedicated Alarm and Control Handling

1.2.4 Support Functions