Академический Документы
Профессиональный Документы
Культура Документы
BSS Document
Reference Guide
Release B11
Status RELEASED
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.1 BSS Equipment Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.2 Supported Hardware Platforms, Restrictions and Retrofits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.3 Platform Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.4 Release Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.5 BSS Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.6 New B11 Features and Impacted Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2 BSS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2 Transmission Architecture with CS Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3 Transmission Architecture with CS and PS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.4 PLMN Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3 BTS Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.1 Introduction to the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.1.1 BTS in BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.1.2 BTS IP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.1.3 BTS Generation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.2 9100 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.2.1 9100 BTS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.2.2 MC TRE Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.2.3 9100 BTS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.3 Distributed BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.3.1 MC-RRH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.3.2 Distributed BTS Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.4 BTS Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.5 Physical Channel Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.5.1 GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.5.2 GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.5.3 Dual Transfer Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.5.4 Extended Dynamic Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.6 Frequency Band Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.6.2 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.6.3 Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.7 Speech Call Traffic Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.8 Adaptive Multi-Rate Speech Codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.8.2 Rules and Dimensioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.8.3 Thresholds and Hysteresis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.9 TRE Packet Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.10 BTS Power Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.11 OML and RSL Submultiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.12 Cell Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.12.1 Cell Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.12.2 Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.12.3 Shared Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.13 TRX Dynamic Power Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.14 AC/DC Converters Capacity in MBO/MBOE Cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.15 Antenna Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4 BSC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.1 BSC in the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figures
Figure 1: BSS with GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 2: Transmission Architecture with CS and PS (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 3: Transmission Architecture with CS and PS (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 4: BTS in the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 5: Network Topology for IP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 6: GSM MC TRE Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 7: Multistandard MC TRE Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 8: Distributed BTS Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 9: BSC in the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 10: 9120 BSC Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 11: 9130 BSC Evolution Hardware Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 12: 1000 TRX LIU Shelf Connections Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 13: ABIS-HWAY-TP and ATER-HWAY-TP Mapped on VC12 Container . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 14: Functional Diagram TPGSMv3 with LIU-E1 and VC12 Cross-connections . . . . . . . . . . . . . . . . . . 80
Figure 15: TC in the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 16: MFS in the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 17: 9135 MFS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 18: BSC Connection for Multi-GPU per BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Figure 19: Generic LCS Logical Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Figure 20: Chain Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 21: Ring or Loop Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 22: Example of Cross-Connect Use on Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Figure 23: Gb Link Directly to SGSN, over Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 24: Gb Link through the TC and MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 25: Gb Link through the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Figure 26: Gb Link Directly to SGSN, over IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Figure 27: Gb Logical Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Figure 28: CBC-BSC Interconnection via PSDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Figure 29: CBC-BSCs Interconnection via the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Tables
Table 1: 9100 BTS Minimum and Maximum Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 2: Typical GSM 900 and GSM 1800/1900 Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 3: Typical Multiband Configuration G3 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 4: Frequency Band Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Table 5: AMR Codec List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Table 6: AMR-WB Codec List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Table 7: Software Version versus Hardware Board/Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Table 8: Thresholds and Hysteresis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Table 9: Data Call Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Table 10: Maximum Supported Capacities and Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Table 11: 9120 BSC Globally Applicable Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Table 12: BSC Configuration Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Table 13: B11 9120 BSC Capacity per Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table 14: TSL / TCU Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table 15: Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Table 16: DTC Configuration and SBL Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 17: G2 TC/9125 TC Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Table 18: G2 TC Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table 19: 9125 TC Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Table 20: TS 16 configuration for MT120 - xB board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Table 21: TS 16 Configuration for TC Boards Older than MT120 - xB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Table 22: MFS Capacity for DS10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Table 23: Maximum MFS Configurations on MX Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Table 24: GPRS General Dimensioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Table 25: GPRS Coding Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Table 26: (E)GPRS Modulation and Coding Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Table 27: GMSK and 8-PSK Transmission Power Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Table 28: Multiplexed Channel Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Table 29: TS Mapping Table for Corresponding Abis Chain or Ring Configurations . . . . . . . . . . . . . . . . . . . . 140
Table 30: Number of TS Available in One Abis Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Table 31: Number of Required TS versus TRX Number and Sub-Multiplexing Type . . . . . . . . . . . . . . . . . . . 143
Table 32: SS7, Ater Mux, DTC and Ater Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Preface
Purpose This document describes the configuration rules for Release B11 of the
Alcatel-Lucent BSS.
It describes the possible BSS configurations supported in Release B11, and
the new equipment in this release, as well as the corresponding impact on
the various interfaces. Note that the OMC-R and NPO products are beyond
the scope of this document. Refer to the appropriate documentation for more
information about these products.
In Edition 27
Frequency Hopping (Section 3.12.2) was updated.
In Edition 26
The following sections were updated:
In Edition 25
Multiple CCCH (Section 4.4.2) was updated.
In Edition 24
In Edition 23
The following sections were updated:
In Edition 22
The following sections were updated:
In Edition 21
The following sections were updated:
In Edition 20
The following sections were updated:
In Edition 19
Gb flex rules (Section 12.3) was updated.
In Edition 18
The following sections were updated:
In Edition 17
The document is updated to specify that IP transport in the BSS is available
from Release B12.
In Edition 16
Description improvement due to MC-RRH 900 - 2G/3G - Different PA - Separate
2G and 3G carriers in same module in MC TRE Module (Section 3.2.2).
Section Lb Interface (Section 10) was added due to the implementation of the
Support of the Lb Interface by BSC feature.
The following MC TRE Module (Section 3.2.2) and Distributed BTS (Section
3.3)are added due to MC/MC RRH module introduction.
The section Antenna Hopping (Section 3.15)has been added due to introduction
of the Antenna Hopping feature.
Updates are done in the following:
In Edition 15
Description improvement in BTS IP Security (Section 3.1.2).
In Edition 14
Release name was changed in Document pertinence.
Description improvement due to MC-RRH 900 - 2G/3G - Different PA - Separate
2G and 3G carriers in same module in MC TRE Module (Section 3.2.2).
In Edition 13
Description improvement is made in GPRS General Dimensioning and Rules
(Section 6.4.1.2).
In Edition 12
Updates are done in the following:
In Edition 11
GB Interface (Section 12) was updated.
In Edition 10
Improvement done in SS7 Signaling Link Code (Section 8.5.2).
In Edition 09
Editorial improvement in:
In Edition 08
Description improvement in:
In Edition 07
Restrictions concerning LSL/HSL have been removed from SS7 Links (Section
8.5.3).
Editorial improvements in RSL and OML (Section 7.4.1).
In Edition 06
Descriptive improvement in Document Pertinence.
In Edition 05
Description improvement in MFS Clock Synchronization (Section 6.3.4).
In Edition 04
Editorial improvements in RSL and OML (Section 7.4.1).
In Edition 03
The following sections were improved:
Hardware Coverage (Section 9.2)
9130 MFS Evolution and 9130 BSC Evolution Rack Shared Configurations
(Section 6.3.3)
In Edition 02
The MFS Clock Synchronization (Section 6.2.3) was improved.
The section Extended Cell Configuration (Section 3.2.3.4)was improved due to
3 extended cells allowance on BTS.
In Edition 01
First official release of the document.
This document contains information about the following new features:
Operations and support staff who need to know how the system operates in
normal conditions, including:
Operators
Support engineers
Maintenance staff
Client Help Desk personnel.
GSM
GPRS
Mobile telecommunications.
1 Introduction
9125 TC 9125 TC
BSC
TC
G2 TC Yes
9125 TC Yes
BTS
MFS
TRX Dynamic Power Saving TRX Dynamic Power Saving (Section 3.13)
2 BSS Overview
2.1 Introduction
The GSM Radio System (GRS) is a set of hardware and software equipment
provided by Alcatel-Lucent to support the radio part of the GSM network. The
GRS comprises one OMC-R and one or more BSS. The OMC-R supervises
one or more BSS.
The BSS provides radio access for Mobile Stations (MS) to the PLMN. There
are one or more GRS per PLMN.
The following figure shows a BSS with GPRS. All BSS operating over the
field are with/without data service.
BSS
GRS
Um Abis Interface
A Interface
Ater mux Interface
BTS
MS BSC TC MSC
BTS
BTS
Gs
Gb Interface
SGSN
MFS
MFS
OMCR
GPRS
BTS
MS BTS MSC
BSC TC
A Interface
BTS
Abis
Um Interface
Atermux Interface
BSS
The Gb interface, used to connect the MFS to the SGSN (directly, or through
the TC and the MSC).
Note: This document does not describe the Gb interface, between the MSC
and the SGSN, as it is not considered to be part of the BSS. For more
information about this interface, refer to the BSS Overview.
For specific information about the LCS dedicated interfaces, refer to LCS
in BSS (Section 6.4.2).
Given that the transmission architecture depends on GPRS, there are two
possible transmission architectures:
BSC TC
BTS A Interface
MSC
The Abis interface, between the BIE BTS and the BIE BSC
The Ater interface, between the SM and the DTC inside the BSC, and
between the SM and the TRCU inside the TC
The Ater Mux interface, between the BSC-SM and the TC-SM
The A interface, between the TRCU and the MSC.
The Abis, Ater, Ater Mux and A are E1 interfaces structured in 32 timeslots (TS).
The TS are numbered from TS0 to TS31.
Note: Microwave equipment is external to and independent of Alcatel-Lucent
transmission equipment, however, in some cases, the microwave can be
housed in the transmission equipment rack and in the BTS.
For 9130 BSC Evolution, the SM no longer exists.
BSC MFS CS TS TC
Mixed CS/GPRS MFSTC Interface
GPRS TS
Conversion
of Protocol
Gb A
Interface Frame Relay Interface
BTS
SGSN MSC
Conversion
GPRS TS of Protocol
Gb
Interface
BTS
SGSN MSC
Frame Relay
The MFS-BSC interface, which is the Ater Mux interface (a 2Mbit/s PCM
link carrying 32 TS at 64Kbit/s). The Ater Mux interface can be fully
dedicated to GPRS (only PS conveyed), or mixed CS/GPRS. In this case,
the CS channels (called CICs) coexist with GPRS channels (called GICs)
on the same link.
The MFS-TC interface, which is also a 2Mbit/s PCM link carrying CS only,
GPRS only, or mixed CS/GPRS channels. The Gb interface can be routed
through the TC for SGSN connection. While GSL is used between the
BSC and MFS for signaling and not for traffic, the GCH is used between
the BTS and MFS.
Note: The MFS can connect directly to the MSC (that is, without crossing the
TC) for cabling facilities, however this still results in an MFS-SGSN
interface, because the MSC only cross-connects the GPRS traffic.
Outgoing 2G to 3G handovers
Multi-PLMN
The Multi-PLMN feature allows operators to define several primary PLMN,
in order to support network sharing. Inter-PLMN handovers and cell
reselections between two different primary PLMN are supported.
The Alcatel-Lucent BSS supports several primary PLMN (at least one, up to
four). An OMC-R therefore manages at least one (primary) PLMN and up
to eight PLMN (four primary and four foreign).
The OMC-R (and the Tool Chain) is by definition of the feature itself always
shared between the different primary PLMN, however:
The MFS can be shared
The BSC cannot be shared
The Abis transmission part can be shared
The transcoder part can be shared.
It is not allowed to modify the PLMN friendly name of a cell, even if the
Multi-PLMN feature is active and several PLMN are defined on the OMC-R side.
The primary PLMN cannot be added, removed or modified online.
Customers no longer need to ensure CI (or LAC/CI) unicity over all PLMN
involved in their network.
With regard to clock synchronization, the only constraint is that when the MFS
is connected to different SGSN, these SGSN are not necessarily synchronized.
If they are not synchronized, central clocking and cascade clocking cannot
be used on the MFS side.
3 BTS Configurations
OMCR
IMT
SGSN
MFS Gb
Gb
Abis (PCU)
BTS Abis MSC
BSC TC A
Atermux
Trusted
A trusted network is either the operator network, in particular on central
sites, or the ISP network when protected.
Untrusted.
An untrusted network is a non-protected ISP network.
Basics for the address definition when a tunnel (between a BTS and an IPsec
GW) is used are the following:
OMC, MFS, BSC NE are part of the customer network, the trusted network
BTS are most often connected to a provider network, the untrusted network.
BTS
G3 BTS
Evolution
G4 BTS (*)
G5 MC TRE
Distributed
MC RRH
Note: *: G3.8 and G4.2 are the TD names used respectively for Evolution Step
1 and Evolution Step 2.
The BTS are grouped into the following families:
The 9110 BTS (which corresponds to the BTS 9110 Micro BTS and the
9110-E Micro BTS)
The 9100 BTS, which includes all BTS, but not the micro BTS.
The antenna coupling level, which consists of ANX, ANY, ANC, AGX,
AGY, AGC and ANB
Note: The above-mentioned architecture does not include the micro BTS.
MC TRE Module
MCPA technology performing power Amplifier for several carriers
Is an extension of the TWIN-module in term of TRX capacity. A TWIN
module has a capacity of up to 2 TRE, when a MC-module has a
capacity of up to 6 GSM TRE (up to 6 because fewer than 6 TRE can
be configured in a MC-module)
Is multi-standard capable
Is hosted in 9100 Evolium BTS equipped with all BTS modules (SUM,
AN, Single Carrier TRE, TWIN)
MC RRH
Is an outdoor box with up to 2 MC-modules/MC-TRE inside, full capacity
(we can have a MC-RRH with only a single MC-module inside)
Distributed BTS
Is one central box (new SUMX) and one or several MC-RRH
A Mono-standard MC-TRX is, from the point of view of a 2G system, a
TRE module
MC TRE types:
MC TRX 900 MHz TDM
The G3.5 BTS, which is a G3 BTS with new power supply modules
The G4 BTS Step 1 (also referred to within TD as the G3.8), which is a G3.5
BTS in which the following modules are redesigned:
SUMA, which is the new SUM board
SUM-X, which integrates the Transmission function, the OMU function
and the Master Clock function. SUM-X provides the BTS with the
Ethernet interfaces
ANC, which is a new antenna network combining a duplexer and
a wide band combiner
New power supply modules which are compatible with BTS subracks.
The 9100 BTS family also includes the following micro BTS:
9110 Micro BTS
G3 TRE
EDGE TRA
Physical Logical
* : TWIN modules are required in order to attain 24 TRE. In this case, the minimum for the physical extension step is 1
TWIN module (2 TRE).
Table 1: 9100 BTS Minimum and Maximum Capacity
Number of TRE 1 sectors 1x2 to 1x4 1x2 to 1x12 1x2 to 1x4 1x2 to 1x12
MBI3 3*2 TRA HP /4 RX low loss /2 G5 ANC 3*2 TRA HP / 4 RX low loss
3*4 TRA TWIN / 2 RX
MBI5 3*4 TRA HP / 4 RX low loss /2 G5 ANC 3*4 TRA HP / 4 RX low loss
3*8 TRA TWIN / 2 RX w. ANY2
MBO1, MBO1E 3*2 TRA HP / 4 RX low loss /2 G5 ANC 3*2 TRA HP / 4 RX low loss
3*4 TRA TWIN / 2 RX
MBO2, MBO2E 3*4 TRA HP / 4 RX low loss /2 G5 ANC 3*4 TRA HP / 4 RX low loss
3*8 TRA TWIN / 2 RX w. ANY2
CBO AC 2*1 TRA HP / 4 RX low loss /2 G5 ANC 2*1 TRA HP / 4 RX low loss /2 G5 ANC
2*2 TRA TWIN / 2 RX
CBO DC 3*1 TRA HP / 4 RX low loss /2 G5 ANC 3*1 TRA HP / 4 RX low loss /2 G5 ANC
3*2 TRA TWIN / 2 RX
The following table shows the TWIN operation modes supported by the different
BTS hardware generations.
TWIN TRA 2TRX Mode 2TRX Mode 1TRX Mode 1TRX Mode
both on same both on diff. with TX Div. w/o TX Div.
sector sectors
Note: 1): Given that the cell planning is done for these network elements, the
TX Div. feature is not supported.
2): The ordered configuration for TX Div. will be delivered from the
factory by default with the 2TRX Mode cabled in different sectors and
must be configured onsite for TX Div.
6 sectors 3x2 GSM 900 & 3x2 GSM 1800 (outdoor only)
A second Abis is necessary for EDGE and for more than 12 TRX, except for
small and medium BTS
The BTS must not contain any G3 TREs for a configuration with more
than 12 TREs
IP transport mode
Each 9110 Micro BTS upper slave terminates the master-slave link, which is
the Inter Entity Bus (IEB)
The following figure shows a mixed 9110 Micro BTS/9110-E Micro BTS
standard configuration.
Master
M5M
If GPS synchronization is used the master BTS must be equipped with a SUMX
board and a GPS receiver. On the slave BTSs there are no requirements on
the type of the SUM board to benefit of this synchronization mode.
Where:
BCCH transports broadcast system information
SDCCH transports signalling outside a call. It can be static (fixed position
on the TS), or dynamic (variable existence in time).
Note: It is possible to define two CBCH channels for cells used for SMS-CB:
3.5.2 GPRS
GPRS radio timeslots (PDCH) are dynamically allocated according to the
following, customer-defined parameters:
These parameters allow the operator to prioritize CS traffic versus GPRS traffic
in order, for example, to avoid a QoS drop while introducing GPRS.
The following quality parameters can also be used:
N_TBF_PER_SPDCH defines the number of mobile stations that can share the
same PDCH
DTM is supported:
For both GPRS and (E)GPRS
Rules:
Only multislot classes 1-12 are supported
EDA operations are not supported in the case of RT TBF and RT PFC
As the shifted-USF operation is not supported, EDA will not be handled for
mobile stations whose multislot class is 7 (1+3 configuration).
For multislot class 3: EDA is used in UL for the 1+2 configuration (i.e. 1
TS in DL, 2 TSs in UL), and DA is used for all the other configurations
(2+1 and 1+1)
For multislot class 11: EDA is used in UL for the 2+3 and 1+3 configurations,
and DA is used for all the other configurations (4+1, 3+2, 3+1, 2+2, 2+1,
1+2 and 1+1)
For multislot class 12: EDA is used in UL for the 1+4, 2+3 and 1+3
configurations, and DA is used for all the other configurations (4+1, 3+2,
3+1, 2+2, 2+1, 1+2 and 1+1).
In the TS configuration for which EDA is used in UL, a PDCH on a given TRX
must verify the following conditions in order to be included in a candidate
timeslot allocation:
The PDCH does not support any (GPRS or (E)GPRS) Best-Effort UL TBFs
of other mobile stations
The PDCH does not support any resources allocated to (GPRS or (E)GPRS)
RT PFCs in the UL direction for other mobile stations
P-GSM band 1.. 124 890.2 to 915.0 MHz 935.2 to 960.0 MHz
GSM850 band 128... 251 824.2 MHz to 848.8 MHz 869.2 MHz to 893.8 MHz
DCS1800 band 512.. 885 1710.2 to 1784.8 MHz 1805.2 to 1879.8 MHz
DCS1900 band 512.. 810 1850.2 to 1909.8 MHz 1930.2 to 1989.8 MHz
3.6.2 Compatibility
The following table shows TRE generation equipment and the corresponding
radio bands.
G3/G4 Yes (*) E-GSM Yes Yes Yes Yes Yes Yes
9110 Micro N.A P-GSM Yes N.A N.A N.A Yes N.A
BTS
3.6.3 Rules
From functional point of view, there are two types of multiband behavior:
Multiband BTS
The frequency bands (850/1800, or 850/1900, or 900/1800) are used in
different sectors of the BTS. There are two BCCH carriers, one in the sector
with frequency band 1, and another one in the sector with frequency band 2.
Multiband cell
The sector (cell) is configured with TRX in band 1, and TRX in band 2. Only
one BCCH carrier is configured for the sector.
Only CS is supported by the G1 band TRX and by the inner zone TRXs of a
concentric or a multiband cell
The following table shows the different rates available over different generations
of equipment.
The FR_AMR-WB codec type uses the following codec modes: 12,65
kbit/s, 8,85 kbit/s, 6,60 kbit/s.
The codec mode HR_AMR 7,95 Kbit/s is not supported by the Alcatel BSS
12.2 Kbit/s X
10.2 Kbit/s X
7.40 Kbit/s X X
6.70 Kbit/s X X
5.90 Kbit/s X X
5.15 Kbit/s X X
4.75 Kbit/s X X
23.85 kbit/s x x
15.85 kbit/s x x
12.65 kbit/s x x
x x
x x
8.85 kbit/s x x
x x
x x
6.60 kbit/s x x
x x
x x
The lowest bit rate providing excellent speech quality in a clean environment is
12.65 kbit/s. Higher bit rates are useful in background noise conditions and in
the case of music. Also, lower bit rates of 6.60 and 8.85 provide reasonable
quality, especially if compared to narrow band codecs.
On the AMR-WB Air interface, only GMSK is used for FR TCH.
The AMR-WB interface is used with the MT120 WB board and the AMR-NB
interface is used with the MT120 NB board.
Supported channel types:
All TCH/WFS: supported
RATSCCH: supported
Only one AMR configuration per AMR-NB codec type is active in the BSS
The AMR configurations with Optimization Mode allowed are not supported.
AMR_WB_ GMSK_ HYST_1 Hysteresis for AMR wideband Number min=0 max=7.5
FR in GMSK codec mode default=to be defined
adaptation for transition between by simulation
lowest codec mode and second
lowest codec mode.
AMR_WB_ GMSK _HYST_2 Hysteresis for AMR wideband Number min=0 max=7.5
FR in GMSK codec mode default=to be defined
adaptation for transition between by simulation
highest codec mode and second
lowest codec mode
Mandatory rules:
AMR_WB_GMSK_THR_1<=AMR_WB_GMSK_THR_2
AMR_WB_GMSK_THR_1+AMR_WB_GMSK_HYST_1<=AMR_WB_GMSK_THR_2+AM
Note: The OMC-R implements the first mandatory rule and it does not allow
AMR_WB_GMSK_THR_2 to be bigger than AMR_WB_GMSK_THR_1.
However, if the second one is not implemented, it could lead
to situations like the following: AMR_WB_GMSK_THR_1 +
AMR_WB_GMSK_HYST_1 > AMR_WB_GMSK_THR_2 or even
- AMR_WB_GMSK_THR_1 + AMR_WB_GMSK_HYST_1 >
AMR_WB_GMSK_HYST_2,
BS_TXPWR_ATTENUATION
T3106-F
PWR_ADJUSTMENT.
The first 3 parameters on one side and the last one on other side are computed
separately. If one or the other is changed by the operator, the left one is
changed by the OMC.
At migration time, the following values must be respected:
T3106-D
Max (( old value T3106-D AND 11111111000), (1104))
T3106-F
old value T3106-F AND 1111111100.
Where:
The number of RSL or OML that can be mapped to one HDLC channel is
as follows:
Cell dimension
Macro up to 35 Km but up to 70 km with extended cells. Micro up to 300
meters.
Cell Coverage
There are four types of coverage: single, lower (overlaid), upper (umbrella),
and indoor.
Cell Partition
There are two types of frequency partition: normal or concentric.
Cell Range
The cell range can be either normal or extended.
Cell Band Type
A cell belongs to 850, 900, 1800 or 1900 bands, or to two frequency bands
in the case of a multiband cell.
The following table lists the Alcatel-Lucent BSS cell types for multiband cells.
Non extended, non concentric mono-band cells of any type can be converted to
multiband cells by adding TRXs of a different band.
The micro concentric, mini concentric, indoor concentric cells must be
multiband (the allowed FREQUENCY_RANGE is PGSM-DCS1800 or
EGSM-DCS1800). This restriction does not apply to external cells.
The Unbalancing TRX Output Power per BTS sector allows unbalanced
configurations. The level of the output power is no more adapted to the lower
TRE output in the sector. One group of transceivers is configured to transmit
with high output power, the other group is configured to transmit with low output
power. This configuration is available in a concentric cell, where the output
power balancing is performed on a zone basis instead of on the sector basis.
When is activated, it is recommended to the operator to set the TRX Preference
Mark parameter to 0 for all TRX of the outer zone.
For the extended cell, the following rules apply:
(E)GPRS is supported
The extended inner cell is not declared in the neighbor cells reselection
adjacencies, because it is barred
Up to 12 TRX CS+PS capable, including the BCCH TRX can be offered in
each cell (inner + outer)
The extended inner and outer cells are in the same Routing Area
No frequency hopping is allowed neither in the extended inner cell nor in the
extended outer cell for (E)GPRS TRX
* : This hopping mode works only with M1M, M2M that are obsolete.
The FHSy including the same frequencies as FHSx except the BCCH
ARFCN has to be assigned to TS0 of all TRX except the TRX supporting
BCCH ( all Non BCCH TRX)
The TS0 from the BCCH TRX is configured with the BCCH ARFCN (non
hopping). This is the basic BBH configuration
In case the Multiple CCCH feature is activated with three or four CCCH, the
following limitations apply:
The CCCH slots from the BCCH TRX are not hopping
On all the other TRX, the TS number corresponding to a CCCH slot must
not contain the BCCH frequency in their hopping sequence
With 4 CCCH, multiple PDCH allocation is not possible on these TRX.
With 3 CCCH, the maximum PDCH allocation would be 3 TS per PDCH
group. In order to avoid this situation, either change cell configuration to
NH/RH or, on cells with 3 TRX or more, create two groups of TRX. One
group must contain at least 2 TRX (BCCH TRX + another TRX) with 2
FHS, the other group will contain the GPRS TRX. Another option is to
add an SDD channel on each TRX.
The linked BTS can still be connected on the Abis side, by the same or a
different Abis link, the same or different Abis TSU, or by same or different
multiplexing schemes.
The shared cell requires a specific attribute that must be defined by the
operator (either primary or secondary) at the TRX level.
3.12.3.2 Rules
The following rules apply:
Clock synchronization
The BTS in a shared cell must be synchronized.
Hardware coverage
For G3 BTS and beyond, generations can be mixed as long as master/slave
configurations are possible. Cell sharing is not supported on 9110-E Micro
BTS and 9110 Micro BTS, because they cannot be clock synchronized.
Output Power.
When a certain sector is extended with another sector, transmission output
powers can be different. In this case, a software adjustment of the output
power is performed. There is a separate power adjustment for 900MHz and
1800 MHz. In all cases, if there is a power discrepancy, only an alarm is
sent, without any further consequences, and sectors continue to transmit
traffic. In a cell shared over two BTS, only one sector (main or secondary)
can support GPRS traffic (not both).
The unbalancing TRX output power also applies on shared cells.
MC TRE 3
Multistandard MBO2E: 3
MBO2: 4
1) : Combined sum of all options: battery charging, MW, TMA, TNL, modems.
2) : Only if usage of TRAP, in case of TRPM as for MP 1800
3) : Depending on type of options and the required redundancy
The two TRE of a twin module are connected to different antennas of the
same sector (cell)
2 TRE
1 TRE without TxDiv usage
Antenna hopping is activated only on BTS configured with all TRE full rate
or all TRE dual rate.
To avoid the loss of a complete sector in case of Twin module failure, it is
recommended for small BTS configuration to configure each TRE of a Twin
in different sector.
4 BSC Configuration
This section describes the 9120 and 9130 BSC Evolution, and corresponding
features and configurations.
OMCR
IMT
SGSN
MFS Gb
Gb
Abis (PCU)
BTS Abis MSC
BSC TC A
Atermux
The Ater TSU, which sets the capacity the BSC can handle
Group Switch
Abis TSU 8 Planes Ater TSU
TCUC
2 Stages DTCC
TCUC DTCC
6x TCUC DTCC 2x
G.703 TCUC DTCC ASMB G.703
Abis TCUC DTCC Ater
I/F TCUC DTCC muxed
BIUA
TCUC DTCC I/F
TCUC AS AS DTCC ASMB
TSL Q1 bus
AS
Broadcast bus
Common Functions TSU
4.2.1.1 Capabilities
The following table lists the maximum theoretical capacities versus
configurations supported by the Mobile Networks Division. Capacities greater
than this cannot be guaranteed and must not be offered to customers.
The following table below lists the parameters that are applicable to all
configurations across all releases.
CPRC-SYS 2 2 2 2 2
CPRC-OSI 2 2 2 2 2
CPRC-BC 2 2 2 2 2
LAPD / TCU 6 6 6 6 6
TRX / Cell 16 16 16 16 16
Max Nb SCCP cnx / BSSAP proc. 128 128 128 128 128
Extension / Reduction
The following data shows the different steps required to go from a minimum
9120 BSC configuration to the maximum configuration. The granularity of
extension/reduction is provided by a Terminal Unit (TU). A TU is a set of four
TSU sharing an access switch through stage 1.
There are six TU: Maximum Configuration (6):
1 1 2 1 4 1 32 6/4
2 4 3 2 4 1 128 24/6
3 6 5 3 8 2 192 36/10
4 9 6 4 8 2 288 54/12
5 11 8 5 8 3 352 66/16
6 14 9 6 8 3 448 84/18
The following table describes the 9120 BSC capacity for each configuration.
Configuration 1 2 3 4 5 6
Access Switch 8 16 24 32 40 48
DC-DC Converters 13 17 30 34 42 47
Abis TSU 1 4 6 9 11 14
Abis interfaces 6 24 36 54 66 84
ATER TSU 2 3 5 6 8 9
No.7 DTCC 4 6 10 12 16 16
BSSAP DTCCs 8 14 22 28 36 44
Full/ Dual Rate TRX or RSLs 32/14(1) 128/62(1) 192/92(2) 288/140(2) 352/170(3) 448/218(3)
Configuration 1 2 3 4 5 6
Ater circuits (assuming X.25 on Ater) 454 686 1148 1380 1842 2074
* : The value does not take into account that this maximum cannot be reached due to SDCCH and BCCH configuration.
** : Maximum number of BTS = (#TCU * #max_OML per TCU) - #TSL link
1 : + 4FR
2 : + 8FR
3 : + 12FR
Table 13: B11 9120 BSC Capacity per Configuration
* : The BS interface is the interface between the BIUA and the TCU.
Table 14: TSL / TCU Mapping
When present, the TSL uses one of the six LapD controllers of the G2 TCU.
4 FR 2
4 FR 1 1
3 FR 3
2 FR 2 1
2 DR 2 1
Each TCUC can handle eight extra Abis timeslots, which reduces the
number of TRE per TCUC
The operator can choose the multiplexing scheme of the BTS and the
rate type of the TRX.
Each Abis TSU (BIUA) can handle six Abis links, which allows:
A maximum three ring configuration (looped multidrop)
A maximum six chain configuration (open multidrop or star configuration).
First Abis TSU for the first rack and the second Abis TSU of second and
third rack can only support up to 14 DR TRE if first TCU of the TSU is
presently configured as FR TCU.
First Abis TSU for the first rack and the second Abis TSU of second and
third rack can only support up to 28 FR TRE if first TCU of the TSU is
presently configured as DR TCU.
Modification of the configuration FR/DR of the first TCU is not supported
from the OMC.
Abis TSU
TCU
Abis
Abis TCU
TCU
Abis
TCU
Abis BIU
switch
TCU
Abis
TCU
Abis
TCU
TCU
4.2.2.3 HR Flexibility
Currently, GSM network operators see the HR as a way of extending the
capacity of the network without any additional hardware deployment (i.e.
without any extra significant cost).
The gradual introduction of HR allows the operator to define each individual
TRE as full rate or dual rate. This allows control of the HR ratio on a per cell
basis. Due to the TRE/TCU mapping algorithm where TRE and TCU must be
of the same type (full rate, dual rate), mapping is not possible when there is
no TCU at all or when the TCU which can be available is already mapped to
TRE whose type is different.
The TCUs of a TSU are allocated, by the 9120 BSC, to support FR or DR TREs
according to the mapping algorithm:
The two types of TRE are mapped on compatible TCUs with a maximum of
four FR TREs per FR TCU and two DR TREs per DR TCU
The BSC allocates free TCUs as FR or DR TCU, according to requirements
In each rack, the TCUC which carries the TSL link cannot be modified
from full rate to half rate, or vice versa, depending on the TCUC original
configuration.
The BSC is responsible for selecting the multiplexing scheme compatible with
the signaling load and the TRE type.
Eight DTCC
Any of the first DTCs in each group of four supporting an Ater Mux interface
(among the 16 first Ater Mux) can terminate an SS7 signaling link if the
Ater Mux is CS
There are six potential BSC synchronization sources (one from each Ater
Mux in the first rack). If the Ater Mux is used, then the first DTC attached
to that ASMB recovers a synchronization reference signal and sends this
to the BSC central clock
DTCC can be dedicated for SS7-MTP (supporting a physical SS7 link), GSL
(supporting a physical GSL), BSSAP/GPRSAP (higher layers of SS7 and
GSL) or TCHRM (TCH allocation)
One DTCC TCH-RM pair can handle up to 60 cells and the number of
TRX per TCH-RM is limited to 90.
BSSAP/GPRSAP
GSL
MTP-SS7.
The following table shows the default mapping on the DTC SBL number.
BSC Configuration
1 2 3 4 5 6
BSSAP/ GPRSAP 2, 6-8, 10, 18-20, 26, 30-32, 42-44, 50, 54-56, 65-72
14-16 22-24 34, 38-40 46-48 58, 62-64
For GPRS, the second DTC in each group of four (e.g. DTCs 2, 6 etc.) can
be configured to handle GSLs on TS28
The second DTC on the first 2 Ater Mux can support X.25 on TS31.
r : Redundancy
W : Working
N and y : Network Element capacity
Figure 11: 9130 BSC Evolution Hardware Architecture
The following table describes the 9130 BSC Evolution functional blocks and
boards.
SSW: Gigabit Ethernet Allows exchanges between all the OMC-R physical interface
switch (in ATCA shelf) elements of the platform and external
CBC physical interface
IP/Ethernet equipment:
Monitoring
Performs Gigabit Ethernet switching
NEM terminal connection
at the shelf level
OMCP: O&M Control Is based on ATCA technology O&M logical interface to the Operation
Processing board (in equipped with a permanent storage and Maintenance Center (OMC-R)
ATCA shelf) device. It manages the platform as
VCPR: S-CPR & O-CPR software +
system manager, and manages O&M
TCH/RM
applications.
TSC software
OMCP boards operate in active-standby
mode following the 1+1 redundancy
model.
CCP: Control Is based on ATCA technology used for VTCU: TCU software
Processing board call control functions. Identical to the
VDTC: DTC software
(in ATCA shelf) OMCP board but without a hard disk.
CCP boards operate in an N + 1
redundancy model. N is the number
of active boards ready to handle traffic
and one standby CCP board is always
available to take over the traffic of failed
board.
TDM switch
8 kbit/s synchronous switching with
a total bandwidth of 284 * 2 Mbits
(252 external links + 32 internal links
toward HDLC, SS7, Q1 and R/W
bits controllers).
LIU boards (in LIU Interface for E1 links These links correspond to the user
shelf) plane interfaces.
4.3.2 Configurations
With the STM1 introduction in B11 Release, the 9130 BSC Evolution can be:
Mixed, with E1 links mapped on the LIU shelf and STM1 interface.
As there are 16 E1 per LIU board (i.e. 256 E1 with configuration type 3):
Note that TP-GSM board can only manage 252 E1 so 4 E1 cannot be used.
Ater can be:
Ater CS, supporting CS, direct link BSC-TC and supporting CS and PS
(mixed, passing through TC), supporting PS (dedicated link, not passing
through TC)
Ater PS, supporting only PS (dedicated, not passing through TC).
The following figure shows the 600 TRX LIU Shelf connections assignment.
200 TRX 400 TRX 600 TRX 800 TRX 1000 TRX
ATCA Shelf 1
TPGSM 2
OMCP 2
SSW 2
LIU Shelf 1
MUX 2
LIU 8 16
Note: Note that the quantity of TPGSM, OMCP, SSW and MUX boards must be
considered to be 1 active + 1 standby to allow redundancy in the shelf.
K=1..3
L=1..7
M=1..3
E1X-1
This is the first cross-connect added to the TPGSM board, manage
cross-connection of up to 252 input E1 links and it is located on the NE1oE.
It maps an input E1 from the LIU shelf to a given E1 framer of the UMA.
UMA
This is the ultra-mapper of TPGSMv3 and contains the E1 framers
consists of 252 inputs.
Each input can be programmed to select an input from the LIU shelf or from
the STM1 network (exclusive choice). Each input handles an E1 frame and
forwards the payload to the same input number of the E1X-2.
E1X-2
This is the second E1 cross-connect added to the TPGSMv3 board. This
cross-connect can manage cross-connection of up to 252 input E1 links, it is
located on the TBS3 and maps an input framer to the TBS2.
TBS2
This is the TPGSM bitswitch managing, amongst other functions, the
cross-connections for call handling (8kbit/s switch). This is the same entity
both on TPv1 and v3 (same functions).
Numbering:
LIU-Port-Number
This is the port number used by a given E1 on the LIU shelf; the port
number is in the range [1, 256].
The numbering scheme is continuous from LIU board 1, port 1 to LIU board
16, port 16. Four LIU port numbers cannot be equipped due to the internal
TPGSM hardware constraint (only 252 framers equipped). In order to
avoid a change in the NE1oE configuration, the same four positions of LIU
board 12 are reserved and cannot be equipped as in previous releases.
All other LIU shelf positions are associated to a fixed SBL as in previous
releases (rigid mapping).
VC12-Number
This is the key identification of a VC12-E1 on the STM1 interface. It is
derived from the STM1 configuration file where the STM1 Number and K,
L, M triplet is specified. The numbering scheme is in range [0...255] and
follows the following rule: VC12-Number = 63* [(STM1-Number) -1] +
21* (K-1) + 3*(L-1) + (M-1)
E1-Number
This is the key identification of an E1 on the interface between the BSC
Application and the TPGSM.
In TPGSMv1 (previous release), the E1 number is the TP board internal
framer number. This is known in all BSC internal specifications also as
the TP-PORT-NUMBER.
In TPGSMv3 (new release), the E1 number is no longer the TP board
framer number. It is the E1X-2 output port number (i.e. the TBS2 port
number). The E1 number in both TPGSMv1 and TPGSMv3 has a physical
significance: each SBL in the BSC is mapped to a UNIQUE E1-Number.
The E1-Number reflects an SBL and does not depend on the transport
mode (LIU-E1 or VC12-E1)
Framer-Number (same as X2-Input-Port-Number)
This is the framer number (from 0 to 251) selected for a given E1.
In TPGSMv3 (new release), the association of a VC12-E1 (identified by
a VC12-Number) to a framer number is fixed, but the association of a
LIU-E1 (identified by a LIU-Port-Number) to a framer number can no longer
be fixed and must take into account the possible conflict if the framer
number is actually used by a VC12-E1.
For all these files, the extension of the file can be .csv or .xls.
The transmission termination points configuration must contain the
configuration of all equipped Abis/Ater HwayTP.
The following table lists the parameters and structures.
LinkNumber This column gives the logical link number. It 1 to 176 for ABIS-HWAY-TP
is the ABIS/ATER-HWAY-TP SBL number.
1 to 76 for ATER-HWAY-TP
Physical Transport This column gives the used transport 0: No Resource configured
LIU-E1 or STM1 VC12-E1 or none if the TP
1: LIUE1 - default value
is not configured.
2: STM1 VC12-E1
LiuPortNumber This column gives the LIU E1 port number Case no configuration: 0 Case
on which the ABIS/ATER-HWAY-TP is E1:
mapped. Dummy value 0 is used if the
1 to 256 LIUPortNumber =
ABIS/ATER-HWAY-TP is mapped on a
f(Linknumber, LinkType)
STM1 tributary
Refer to Figure 12 for the exact
mapping between the LIU port
number and Linknumber.
Case STM1: 0
STM1 Interface This column gives the STM1 interface Case no configuration: 0
on which the ABIS/ATER-HWAY-TP is
Case LIU-E1: 0
mapped. Dummy value 0 is used if the
ABIS/ATER-HWAY-TP is mapped on a LIU Case STM1 VC12-E1: 1 to 4
port.
STM1-K This column gives the TUG-3 number of the Case no configuration: 0
TU-12 on which the ABIS/ATER-HWAY-TP
Case LIU-E1: 0
is mapped. Dummy value 0 is used if the
ABIS/ATER-HWAY-TP is mapped on a LIU Case STM1 VC12-E1: 1 to 3
port.
STM1-L This column gives the TUG-2 number of the Case no configuration: 0
TU-12 on which the ABIS/ATER-HWAY-TP
Case LIU-E1: 0
is mapped. Dummy value 0 is used if the
ABIS/ATER-HWAY-TP is mapped on a LIU Case STM1 VC12-E1: 1 to 7
port.
STM1-M This column gives the TU12 number of the Case no configuration: 0
TU-12 on which the ABIS/ATER-HWAY-TP
Case LIU-E1: 0
is mapped. Dummy value 0 is used if the
ABIS/ATER-HWAY-TP is mapped on a LIU Case STM1 VC12-E1: 1 to 3
port.
All Abis and Ater Mux are mapped on STM1 Template PureSTM1.cnf
VC12-E1.
Configuration 1 2 3 4 5
Type
Nb SS7 8 16 16 16 16
links
Ater CS 10 20 30 38 46
Ater PS 6 12 18 26 30
Nb DTC 24 48 72 96 112
PS
Nb VCE Nb 1 1 1 1 1
OMCP TCH-RM
pairs
Nb CPR 2 2 2 2 2
pairs
Nb TSC 8 8 8 8 8
pairs
Nb 11 11 11 11 11
VCE/OMCP
* : The Nb CICs depends on the type of TC, MT120 boards and on the number of SS7/HSL.
The capacity of the 9130 BSC Evolution is extended to 1000 TRX by adding
two CCP boards in the ATCA shelf
The TP GSM board supports the traffic of 1000 TRXs, depending on the
generation
It is possible to map up to four TREs per VTCU, i.e. up to 200 TREs per CCP
The maximum number of active TCHs per CCP board in order to reach
900 Erlang per CCP with a blocking probability of 0.1% and a margin of
3% (call mix with 3HO/call) is 1000
The capacity is extended to 500 cells for the 9130 BSC Evolution
The increase of TRX capacity also impacts the number of extra Abis
timeslots that are supported by the 9130 BSC Evolution, in that it is
increased up to 2000. This increase leads to two extra Abis timeslots
available per TRX.
The external alarms can be collected by an External Alarm Box (EAB); refer
to the External Alarm Box Installation and Commissioning Manual for
more information.
4.4.1.2 Terminology
A static SDCCH/x TS refers to one physical TS on the Air interface containing x
SDCCH sub-channels (x = 3, or 4, or 7, or 8, depending whether the TS is
SDCCH/3, or SDCCH/4, or SDCCH/7, or SDCCH/8).
Dynamic SDCCH allocation only deals with SDCCH/8 TS. It is not necessary
to add or suppress a SDCCH/3, or a SDCCH/4, or a SDCCH/7 TS
The maximum number of SDCCH per cell must be verified to ensure that
the number of configured SDCCH, dynamic and static, for a cell must not
exceed the defined maximum of 88.
In terms of usage:
A dynamic SDCCH TS can carry only CS traffic
In multiband and concentric cells, only the TRX, which belong to the outer
zone, can support dynamic and static SDCCH
Static SDCCH/8 TS cannot be used as TCH
Dynamic SDCCH/8 TS are allocated for SDCCH only if all the static
SDCCH/8 TS are busy (i.e. all its sub-channels are busy)
With MC module must avoid SDCCH loss: to spread SDCCH over FHS in
case of base band hopping with several FHS.
It is not allowed to activeate a second CCCH when the CCCH in the cell
is combined with SDCCH
It is assumed that one CCCH equals to SDCCH/8 in terms of RSL load and
processor load imposed by the signalling by a CCCH
To activate multiple CCCH using three or four time slots, there must be
at least two TRX per cell.
To activate multiple CCCH using three or four time slots in concentric cells, it
is necessary that the outer zone of the concentric cell has at least two TRX.
It is not allowed to configure more than four signaling time slots per TRX
(including dynamic SDCCH)
When BCCH is combined with SDCCH, CCH cannot be configured
In BCCH TRX, when BCC and CCH are configured on TS0 and TS2, only
one Static SDCCH is allowed to config on the others TS
In BCCH TRX, when CCH is configured on TS0, TS2 or TS4, only one Static
SDCCH is allowed. The CBCH and SDCCH channels will not be located on
the beacon TRX when four CCCH are configured
CBC and CBH are forbidden when mCCCH is configured on BCCH TRX
DYN SDCCH is forbidden on BCCH TRX when mCCCH is configured
on BCCH TRX
With the additional CCCH on TS2 aTRX (G3, G4 and G5) must support:
SDCCH on TS1/TS3/TS4/TS5/TS6/TS7
No changes in PM mechanisms
TSU is removed
Support of HSL
Remove HR impact
The 9130 BSC Evolution can be used as a clock synchronization source
for DS10 or 9130 MFS Evolution
Free allocation of any RSL/OML to any TCU, thus allowing the full TRE
capacity and avoiding any internal BSC moves
No need of TCU capacity to support the extra Abis TS. Edge traffic can be
supported even when the BSC has the maximum of TRE
For IPoEth : the TP v3 with TPIP board (and the LIU shelf) are no more
used and can be removed.
TS15/TS16 can support PS traffic on CS/PS Mixed Ater Mux
For 9120 BSC the Ater Mux 1,2,7,8,13,14 cannot be dedicated GPRS
TCU
BIE
BTS ADAPT
TCU
BIE
The following figure shows the different kinds of SBLs (with their hardware
module mapping) shown at the interface between the 9130 BSC Evolution and
the BTSs and at the interface between the BTSs. For the 9130 BSC Evolution,
the SBL BSC-ADAPT is removed.
ABIS HWAY TP ABIS HWAY TP
(Unit type=BTS) (Unit type=BTS)
BIE
SSW MUX LIU ABIS HWAY TP
(Unit type=BSC) BTS ADAP T
TP
GS M ABIS HWAY TP
SSW HW ECU ETU ABIS HWAY TP
(Unit type=BTS)
(Unit type=BTS)
(Unit type=BSC)
BIE
BTS ADAPT
TP HW
(Unit type=BSC)
5 TC Configuration
5.1 Introduction
The following figure shows the location of the transcoder (TC) inside the BSS.
OMCR
IMT
SGSN
MFS Gb
Gb
Abis (PCU)
BTS Abis MSC
BSC A
TC
Atermux
In the case of a 9125 TC transcoder, these units are combined on one single
board, the MT120, which offers an Ater Mux connection to a BSC and up to
4 A-trunk connections to the MSC.
The MT120 can also be installed in the place of the ASMC in the G2 TC, and
replaces 1 ASMC, 4 ATBX and 8 DT16 boards.
The following table provides a summary of the technical data for the different
generations of TC.
G2 TC (with / 9125 TC
without MT120)
A interfaces 24 192
* : From the total number of CIC, it must decrease the channels carrying the
O&M traffic: 2 for 9120 BSC (X25 links) and up to 16 for 9130 BSC Evolution
(MLPPP links).
Table 17: G2 TC/9125 TC Capabilities
5.2 G2 TC
5.2.1 Architecture
There are two types of G2 TC:
The G2 TC architecture is linked to the 9120 BSC architecture (that is, the
Ater TSU). A G2 TC rack is compounded by six Submultiplexing Units (SU)
with a granularity of 1 SU = 1 ASMC + 4 TRCU.
One G2-TC Full Rack can be installed in front of the 9120 BSC (one full
G2-TC rack means Conf 2: 6 Ater Mux. as two SU are required in front
of one Ater TSU)
Taking into account the above rules for G2 TC equipped with MT120, the
configuration rules described in the following table apply for this rack.
Physical/Logical
SU 2 6 1
ASMC 2 6 1
TRCU SM 4:1 4 24 4
MT120 - 4 1
Rules:
When creating one logical Ater Mux, the new granularity of hardware added
is: n or one ASMC + 4xATBX + (4x2 DT16)
Before introducing MT120 in a G2 TC, the ASMC must be completed with all
required DT16 (to remove holes in the ASMC).
5.3 9125 TC
5.3.1 Architecture
The 9125 TC can be used to extend the G2 TC (by mixing a G2 TC and 9125
TC within a BSS), for G2 TC replacements and for new BSS.
For G2 TC replacements, one 9125 TC can replace several G2 TC racks.
The 9125 TC can be equipped with up to 48 sub-units (referred to as MT120
boards). Each MT120 offers an Ater Mux connection to a BSC and up to four
Atrunk connections to the MSC, so that the 9125 TC offers up to 192 Atrunk
connections to the MSC.
The 9125 TC can be shared between several 9120 BSC. One MT120 board in
any slot of any subrack can be allocated to any Ater Mux of a 9120 BSC. These
BSC can belong to several OMC-R.
The following table describes the 9125 TC configurations.
Physical Logical
MT120 2 48 1 1
The AMR-WB introduces two types of MT120 board, besides the legacy MT120:
MT120 WB
MT120 NB.
The 9125 TC can have two 9125 TC STM1 boards (active and standby). They
are inserted in a dedicated 9125 TC STM1 subrack, which is located in the
bottom part of the TC rack. Each TC MT120 board is connected to both TC
9125 STM1 boards (dual star). The link between MT120 and 9125 TC STM1
boards is a high speed link (using HSI).
The A and Ater Mux interfaces can use the E1 support or/and the STM1
support. The TC 9125 has the SDH interfaces (STM1) on a daughter board on
9125 TC STM1, referred to as JATC4S1, dedicated to STM1.
The 9125 TC STM1 boards provide:
HSI mode, when TC is equipped with TCIF boards with two sub modes:
HSI2a mode, when TCIF board is used only for O&M action on TC. In
this mode the Atermux and A interface are configured with E1
HSI2b mode, when TCIF board is used for O&M actions and telecom
traffic on STM-1/IP. In this case one or both interface (Atermux and A)
can have STM-1/IP configuration.
Note: From cluster point of view all MT120 boards must be in the same mode,
TCIL or HSI mode.
Six BSCs with eight Ater Mux can be connected to a 9125 TC rack.
Extension
A Qmux cluster is a group of up to six MT120 which ensure the Qmux
supervision of the boards with the TSC/VTSC of the related BSC. These MT120
boards must be always in the same 9125 TC rack.
A Qmux cluster corresponds to one 9120 BSC rack, or to group of six Ater Mux
in 9130 BSC Evolution (1..6, 7..12,.).
The notion of Qmux clusters is important during the extension of Ater Mux in a
BSC rack, as it can induce modification of the initial configuration.
The maximum number of MT120 boards is equal to 48.
In case of 9130 BSC Evolution:
Atermux 1 to 30 are CS
G2 TC extension
Once the G2 TC rack maximum capacity (six Ater) is reached, the BSC
extension requires TC capacity. In this case, the 9125 TC rack is required
as the G2 TC rack extension (G2 TC rack is kept). The 9125 TC rack
can be shared afterwards between different BSC extensions. A 9125 TC
rack can also be added even if the G2 TC rack is not completely filled (in
the case of GPRS holes).
New BSC
Depending on the free slot capacity in the 9125 TC, a new 9125 TC may
be required.
STM1 interfaces
BTS
To introduce the interface to the TC 9125 STM1 board, the MT120 software
has to be upgraded.
Note: If the A Interface is over IP, the Ater Mux TS16 is used for traffic
regardless of the BSS Transport Mode.
TS16 N7 Not Not used Not used Not used Not used
configuration
(GCH) used (GCH) (GCH) (GCH) (GCH)
(GCH)
6 MFS Configuration
This section describes the MFS, and corresponding features and functions.
OMCR
IMT
SGSN
MFS Gb
Gb
Abis (PCU)
BTS Abis MSC
BSC A
TC
Atermux
Ethernet LAN
/HUB
From / to BSC
and TC
Atermux Gb Interface
Interfaces GPU
From / to
Atermux GPU Gb Interface
SGSN
Interfaces
Atermux Gb Interface
GPU
Interfaces
There are a maximum of 16 PCM links per GPU board. The use of these PCM
links is not dedicated, and each interface can be connected to BSS or NSS
entities. The supported interfaces are:
Mixed Ater transport TCH from the BTS to existing the TC on the BSC
side and TC side
Gb connects the MFS directly to SGSN, through the Frame Relay Network
or through the MSC. The capacity required depends on GCH in Ater Mux.
In terms of the BSC connection, the BSC is transparent to this behavior and
ignores the mapping of cells per GPU. The BSC is only impacted by a greater
number of LAPD or TCP links.
For inter-GPU links, there are two 100Mbs Ethernet links, which interconnect
the GPU and the Control Station. These links are used to exchange information
between GPU.
Standard
The MFS includes one telecom subrack with a minimum two GPU (1+1)
and can be extended up to 16 (15+1) GPU. The second telecom subrack is
only wired and is not equipped.
Standard pre-equipped
The MFS includes two equipped and wired telecom subracks. The maximum
capacity is 32 GPU (2 * (15+1)).
Maximum BSS 15 22
Centralized
The BSC (dedicated GPRS Ater Mux) and SGSN (Gb) ports (0 to 7) are
configured as usual for traffic
The last eight GPU ports (8 to 15) are configured as SGSN (Gb) ports
but with no data paths assigned.
From a hardware point of view, the GPU ports (8 to 15) are linked at the DDF
to create the synchronization distribution scheme.
To prevent alarm reports towards the OMC-R, all unused ports (from 8 to 15) of
each GPU are looped at the DDF side (TX path looped on RX path).
This synchronization type is used only in old field equipment which does
not support the centralized mode.
SSW GP
(duplicated)
Mux
Radio Network Links
E1 LIU 1
OMCPw
OMCPr
LIU n
LIU Shelf
(21 slots) ATCA Shelf (14 Slots)
One or two shelves: single without BSC Evolution. When the MFS is single
the type of BSC has no importance.
GP 9*+1 21+1
or
16+1
LIU boards 8 16
For other objects (PDCH group, FrBR, PVC, etc.), the same values are
maintained.
6.3.3 9130 MFS Evolution and 9130 BSC Evolution Rack Shared
Configurations
A rack shared configuration for a 9130 MFS Evolution and a 9130 BSC
Evolution consists of:
In both cases:
In the case of the BSC and MFS, they are not considered as a standalone
node, and the MFS NE can be used by the rack shared BSC, but also by
other nearby BSCs (9130 BSC Evolution based or 9120 BSC). (MFS NE is
not fully or only dedicated to BSC traffic located in the same rack)
ATCA Shelf 1 1
TPGSM 2 NA
GP NA 1 to 9
SPARE GP NA 1
OMCP 2 2
SSW 2 2
LIU Shelf 1 1
MUX 2 2
LIU 8 16 8
The autonomous mode, whereby each GPU receives the clock signal on
dedicated E1s (at least two links for redundancy)
The centralized mode, whereby two dedicated GP receive the clock signal
on dedicated E1s and transmit it to the other GPs.
The 9130 MFS Evolution allows 12 E1 per GP with centralized clock.
When defining the synchronizing PCM-TTPs, it is recommended to:
Select two PCM-TTPs that are not connected to the same LIU board
Select two PCM-TTPs that are not connected to the same BSC.
With the following priorities: TC then 9130 BSC Evolution, then SGSN.
During the MFS installation with a centralized clock, the operator must first
configure the E1 that is physically connected first.
The control plane. The following two signaling interfaces are used:
The GPRS Signaling Link (GSL) between the MFS and BSC. This link is
used for coordination between the BSC and the PCU, mainly for GPRS
capacity on demand, and for GPRS paging, access request and access
grant when the CCCH is used for GPRS.
The Radio Signaling Link (RSL) between the BTS and the BSC. The
RSL is mainly used for GPRS paging, access request and access grant,
when the CCCH is used for GPRS.
The Gb interface can be routed via the G2 TC and 9125 TC to the SGSN
across the MSC
PVC per BC S 1 1
O : Operator Choice
S : System Check
* : GPU concerns the logical unit, and GP is expressed for 9130 MFS Evolution.
Table 24: GPRS General Dimensioning
Maximum 1 GSL per Ater Mux. The GSL is located on TS28 of the 2nd
tributary
The DS10 MFS supports 8 BSC/MFS links (and 32 gicGroup instances per
GPU). The 9130 MFS Evolution supports up to 16 BSC/9130 MFS Evolution
links (and up to 52 gicGroup instances per GP).
LCS provides the position of the target mobile station. Depending on the
positioning techniques.
GMLC
BTS
A Interface
Lg
Lh
MS BTS
BSC MSC
HLR
Lb
Interface Gs
Interface Lg
SMLC
SGSN
MFS
LSN1 LSN2
Gb Interface
Router AGPS
Server
SAGI
Figure 19: Generic LCS Logical Architecture
As shown:
The GMLC is the first NE serving external Location Application (LA) access
in a GSM PLMN. The GMLC requests routing information from the Home
Location Register (HLR) via the Lh interface. After performing registration
authorization, it sends positioning requests to the MSC and receives final
location estimates from the MSC or the SGSN via the Lg interface.
The SMLC is the NE which serves the client. The SMLC manages the
overall coordination and scheduling of the resources required to performing
mobile station positioning. The SMLC calculates the final location estimate
and accuracy to obtain the radio interface measurements required to locate
the mobile station in the area it serves. The SMLC is connected to the
BSS (via the Lb interface).
Activate GPRS for the cell (i.e. set the MAX_PDCH to > 0, so that the cell is
locked for GPRS if the operator does not want to have GPRS running on
this cell)
Activate LCS (by setting the EN_LCS flag, the common BSC/MFS
parameter, to true ) on the BSS handling the cell
6.4.2.4 Rules
The following rules apply:
LCS is supported in the CS domain
A-GPS positioning methods can be used if the new SAGI interface has
been installed
An MFS with a router in front presents one IP address to the GPS server.
Reciprocally, the GPS server presents one IP address to a router in front of
the MFS
The router is external to the MFS, which implies that it is not supervised by
the MFS. The declaration of SAGI interface is supported by a EN_SAGI
flag defined on a per BSS basis.
A basic service to offer CS3 and CS4 for GPRS and MCS1 to MCS9 for
(E)GPRS (two optional features)
CS-3
CS-4.
The following table lists the coding schemes and the corresponding modulation
types and maximum transmission rates.
CS-4 GMSK 20
CS-2 GMSK 12
CS-1 GMSK 8
HSDS
HSDS provides support for GPRS with CS1 to CS4, and for (E)GPRS with
MCS1 to MCS9.
There are 3 families of modulation and coding schemes:
37 bytes: family A
28 bytes: family B
22 bytes: family C.
The different code rates within a family are achieved by transmitting a different
number of payload units within one radio block.
When four payload units are transmitted, these are split into two separate RLC
blocks (i.e. with separate sequence numbers).
When a block has been retransmitted with a given MCS, it can be retransmitted
(if needed) with a more robust MCS of the same family.
The following figure shows the choice of modulation schemes.
GMSK 8PSK
MCS1 MCS2 MCS3 MCS4 MCS5 MCS6 MCS7 MCS8 MCS9
Family
C 22 22 22
28 28 28 28 28
Family
B
28 28
37 37 37 37 37
Family
A
37 37
Ater Interface
In order to handle a throughput higher than 16Kb/s on the Ater interface,
several Ater nibbles are dynamically allocated by the MFS Telecom.
Abis Interface
On the Abis interface, to handle a throughput higher than 16Kb/s, several
Abis nibbles are also used. The configuration is dynamic for TRX inside
the same BTS.
A number of 64k EXTS (Extra TS) are defined for each BTS by O&M. This
group of TS replaces the number of transmission pool types used previously.
Due to the increase in Abis resource requirements, a single Abis link may not
be enough to introduce HSDS into a large BTS configuration. In this case, a
second Abis link is required (see Two Abis Links per BTS (Section 7.9) ).
M-EGCH
This term is used to refer to a link established between the MFS and the BTS.
One M-EGCH is defined per TRX.
Enhanced Transmission Resource Management
A dedicated manager sequences the GCH establishment, release, redistribution
or pre-emption procedures.
The transmission resource manager is on the MFS/GPU level. It handles both
Abis and Ater resources (GCH level).
It is in charge of:
The following table shows the output power values for GERAN TRA.
GSM900 GTT09 2*45 W / 46,5 dBm 2*30 W / 44,8 dBm - 116 dBm Twin TRA
GTH09 90W / 49,5 dBm 40W / 46,0 dBm - 119 dBm HP / 4 RX TRA
DCS1800 GTT18 2*35 W / 45,4 dBm 2*30 W / 44,8 dBm - 116 dBm Twin TRA
GTH18 70W / 48,5 dBm 30W / 44,8 dBm - 119 dBm HP / 4 RX TRA
60W 40W
60W 30W
The (E)GPRS TBF can be allocated on the BCCH TRX, and the BCCH
frequency must have a quite stable radio transmission power.
The Modulation Delta Power is the difference between the GMSK output power
of the sector for the TRE band, and the 8-PSK output power of the TRE.
According to the 8-PSK delta power value, a TRE is called "High Power" or
6.4.3.3 Rules
The following rules apply:
TCU Allocation:
Extra Abis TS are allocated only on the FR TCU
RSL, OML and TCH are mapped on a TCU, regardless of extra Abis TS
Extra Abis TS are moved automatically from one TCU to another
BTS configuration
Only 9100 BTS (including 9100 Micro-BTS) support the HSDS
A mix of the G4 TRE medium power and G4 TRE high power (that
offers a higher output power useful for 8-PSK modulation) in the same
9100 BTS is allowed
To support MCS1 to MCS9, an 9100 BTS must be upgraded with some
G4 TREs
TWIN TRA is supported only with SUMA, not with SUMP.
For BSC connectivity, two A-bis extra timeslots are equivalent to one Full
Rate TRX
For example, for a 9135 MFS, the maximum throughput for a DSP, in one
direction, is about 800 kbit/s for pure GPRS and 1 Mbit/s with (E)GPRS
(with some assumptions regarding MCS and CS distribution)
6.4.4 Gb over IP
With the introduction of GBoIP, telecom traffic towards/from the SGSN goes
through the router from/in the MFS.
The following table lists the Gb over IP connectivity mains output.
9130 MFS O&M One LAN O&M Two LAN Telecom One
Evolution LAN
(No RIP) (RIP)
B9 Supported Supported -
9135 MFS O&M One LAN O&M Two LAN Telecom One
LAN
(No RIP) (RIP)
Where:
And:
Assumptions:
When GboIP is activated, there must be one IP address per active GPU
The support of GBoIP needs a B11 MFS but also a B11 version of the BSS
associated with the concerned GPU
Some boards of 9130 MFS Evolution are common with 9130 BSC Evolution:
OMCP, switch, LIU, MUX, shelf manager.
If the MFS single secured Gb feature is used, the GPU synchronization in
autonomous mode can be used through the BSC links or through the TC links if
the Gb and the synchronization from the TC do not share the same Ater Mux.
Configurations for 4, 9, and 21 GPUs Colors shown affectation of LIU per GPU
GPU 1, 5, 9, 13, 17, 21
The following figure shows Ater Allocation on LIU boards for MFS with only
one subrack.
8 x GPU
4 x GPU
LIU 1 LIU 2 LIU 3 LIU 4 LIU 5 LIU 6 LIU 7 LIU 8 LIU 9 LIU 10 LIU 11 LIU 12 LIU 13 LIU 14 LIU 15 LIU 16
1 1 17 33 49 65 81 97 113 129 145 161 177 193 209 225 241
2 2 18 34 50 66 82 98 114 130 145 162 178 194 210 226 242
3 3 19 35 51 67 83 99 115 131 147 163 179 195 211 227 243
4 4 20 36 52 68 84 100 116 132 148 164 180 196 212 228 244
5 5 21 37 53 69 85 101 117 133 149 165 181 197 213 229 245
6 6 22 38 54 70 86 102 118 134 150 166 182 198 214 230 246
7 7 23 39 55 71 87 103 119 135 151 167 183 199 215 231 247
8 8 24 40 56 72 88 104 120 136 152 168 184 200 216 232 248
9 9 25 41 57 73 89 105 121 137 153 169 185 201 217 233 249
10 10 26 42 58 74 90 106 122 138 154 170 186 202 218 234 250
11 11 27 43 59 75 91 107 123 139 155 171 187 203 219 235 251
12 12 28 44 60 76 92 108 124 140 156 172 188 204 220 236 252
13 13 29 45 61 77 93 109 125 141 157 173 189 205 221 237 253
14 14 30 46 62 78 94 110 126 142 158 174 190 206 222 238 254
15 15 31 47 63 79 95 111 127 143 159 175 191 207 223 239 255
16 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256
GPU 2, 6
GPU 3, 7
GPU 4, 8
The following figure shows Ater Allocation on LIU boards for MFS which are
rack shared with the BSC.
8 x GPU
4 x GPU
LIU 1 LIU 2 LIU 3 LIU 4 LIU 5 LIU 6 LIU 7 LIU 8 LIU 9 LIU 10 LIU 11 LIU 12 LIU 13 LIU 14 LIU 15 LIU 16
1 1 17 33 49 65 81 97 113 129 145 161 177 193 209 225 241
2 2 18 34 50 66 82 98 114 130 145 162 178 194 210 226 242
3 3 19 35 51 67 83 99 115 131 147 163 179 195 211 227 243
4 4 20 36 52 68 84 100 116 132 148 164 180 196 212 228 244
5 5 21 37 53 69 85 101 117 133 149 165 181 197 213 229 245
6 6 22 38 54 70 86 102 118 134 150 166 182 198 214 230 246
7 7 23 39 55 71 87 103 119 135 151 167 183 199 215 231 247
8 8 24 40 56 72 88 104 120 136 152 168 184 200 216 232 248
9 9 25 41 57 73 89 105 121 137 153 169 185 201 217 233 249
10 10 26 42 58 74 90 106 122 138 154 170 186 202 218 234 250
11 11 27 43 59 75 91 107 123 139 155 171 187 203 219 235 251
12 12 28 44 60 76 92 108 124 140 156 172 188 204 220 236 252
13 13 29 45 61 77 93 109 125 141 157 173 189 205 221 237 253
14 14 30 46 62 78 94 110 126 142 158 174 190 206 222 238 254
15 15 31 47 63 79 95 111 127 143 159 175 191 207 223 239 255
16 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256
Configurations with 4 and 8 GPUs in rack shared with option 16 E1 /GP Colors shown affectation of LIU per GPU
GPU 1, 5
GPU 2, 6
GPU 3, 7
GPU 4, 8
Because the spare GP is not fixed, the mapping changes after switchover.
The 9130 MFS Evolution differs from the standard MFS as follows:
The GP replaces the current GPU
In the 9130 MFS Evolution, there are only 12/14/16 ports per GP
The fixed synchronization mode does not exist. The clock synchronization is
transmitted over Ethernet (nE1oE) from the E1 board. It is received on the
specific virtual E1 links of the GP and can be configured, as is the case
in the autonomous mode or centralized mode.
In IP transport mode, the BSS bases the IPGSL, TCSL and the IPGCH
control link on a TCP connection:
Between the 9130 MFS Evolution GP and the 9130 BSC Evolution
CCP for the IPGSL
Between the 9130 MFS Evolution GP and the BTS TRE for IPGCH
Between the 9130 BSC Evolution OMCP and the TC TCIF for the TCSL
For more information about configurations with O&M connection via the 9130
BSC Evolution, refer to BSS Routing Configurations document.
7 Abis Interface
This section describes the Abis interface, and corresponding features and
functions.
The Abis interface is standard ITU-T G.703 / G.704 interface. It is based on a
frame structure. The frame length is 256 bits grouped in 32 TS, numbered from
0 to 31. The rate of each TS is 64 Kbit/s.
BSC
BTS BTS BTS
BTS BTS
BSC
BTS
A terrestrial link referred to as the PCM 2Mbit/s link (64 Kbit/s * 32 Timeslots
= 2048 Kbit/s)
A satellite link.
7.2 Impedance
There are two types of impedance which define the access to the transmission
network:
TS0 Transparency
The Qmux is carried by any other TS from TS1 to TS31 (TS0 does not
carry Qmux).
TS0 transparency is strongly recommended.
The Radio Signaling Link (RSL) is used for supporting traffic management
procedures (mobile station to network communication)
The Operation and Maintenance Link (OML) is used for supporting network
management procedures.
Signaling for GPRS traffic is carried over the RSL and/or GCH.
No multiplexing
If the multiplexing mode is "Per sector" and the signalling load is "normal"
for the first sector, "normal" for the second sector and "high" for the third
sector, then the following distribution of the OML and the RSLs over the Abis
timeslots applies:
First TS = OML + RSL1/1 + RSL1/2
Second TS = RSL 2/1 + RSL2/2
Third TS = RSL 3/1 + RSL 3/2
Fourth TS = RSL 3/3 + RSL 3/4
For 16k statistical submultiplexing, the TS0 of each TRX must carry a static
signaling channel (BCCH, static SDCCH).
The operator can reserve Abis TS per Abis (range of TS from Tsi to TSj)
(i and j from 0 to 31 and j>i). The operator can define (per BTS) the
usable TS inside the range defined on the Abis. The operator defines, TS
per TS, which one correspond to which BTS. This is necessary in the
case of cross connects.
For 9100 BTS, the two TS required to carry the traffic channels over Abis do
not need to be contiguous, but the first set of four traffic channels (TRX-TS
0..3) must always be on a lower Abis-TS than the second set (TRX-TS 4..7)
The Qmux, Rbits and Sbits can be mapped onto any usable TS from
TS0 to TS31
Note: For the 9130 BSC Evolution Qmux, Rbits and Sbits must not be
mapped on TS0.
The OML channels can be slotted anywhere by the operator
The RSL and TCH channels are slotted in any available TS by the BSC
RSL and traffic channels of one MCB must be on the same PCM link
The parameters which allow to control the Abis allocation are:
Max_PS_TS primary
Max_FR_TRE_primary
Max_DR_TRE_primary.
Note: For an HSDS-configured BTS, refer to the mapping rules (extra Abis
nibbles; OML mandatory on first Abis) described in HSDS in BSS
(Section 6.4.3).
An empty TCU (without any MCB and extra Abis TS) can be set to FR or DR.
The sequence for remapping RSL/TRX and for programming the BIUA is
reversed to reduce telecom outage. The scenario is as follows:
1. Construct a new RSL/TRX mapping and save this mapping in the DLS.
2. Reprogram the BIUA based on this new mapping.
3. Activate the new RSL/TRX mapping in the BSC.
Each of these blocks are secured against take over, etc... Point (1) and (3) are
protected with a rollback mechanism.
With HR flexibility, the reshuffling algorithm is kept but the reshuffling process is
to be conducted independently for each TCU type.
BTS 2 TS 2 to 6
BTS2
Branch 1
Branch 2
BSC BTS1
Branch 3
BTS 1 TS 2 to 4
BTS 2 TS 11 to 15
BTS 3 TS 21 to 24
BTS 3 TS 2 to 5 BTS3
The following table lists the possible TS mapping tables for the corresponding
Abis chain or ring in the BSC.
2 to 10 2 to 10
11 to 20 2 to 11
21 to 31 2 to 12
When BTS 1 is created, according to the usable TS, the TS allocated for the
BSC connector are 10-9-8, and according to the TS mapping table, the TS
allocated for the BTS-BIE are 10-9-8.
When BTS 2 is created, according to the usable TS, the TS allocated for the
BSC connector are 15-14-13-12-1, and according to the TS mapping table,
the TS allocated for the BTS-BIE are 6-5-4-3-2.
When BTS 1 is created, according to the usable TS, the TS allocated for the
BSC connector are 24-23-22-21, and according to the TS mapping table, the
TS allocated for the BTS-BIE are 5-4-3-2.
When a TRE is added to BTS 3, according to the usable TS, the TS allocated
for the BSC connector are 27-26-25, and according to the TS mapping table,
the TS allocated for the BTS-BIE are 8-7-6.
7.6.4.2 Cross-Connect Use on Abis Rules
Cross-connect usage on Abis is supported only if the following rules are applied:
One BTS uses (for itself and for the forwarded Abis link) only PCM TS, which
come from a single BSC connector
If Qmux is used, the BTS must be connected to the Qmux TS. The other
branch must use OML if possible (9100 BTS)
Note that the following rules for TCU allocation still apply:
The TCU can handle maximum of four FR TREs (four RSLs) or two FR +
one DR TRE (three RSLs) or two DR TREs (two RSLs). Therefore, the
TCU can handle a maximum of four Eq. FR RSLs
Open Chain MD 30 31 31
Closed Loop MD 29 30 29
The following table lists the number of required TS versus TRE number and
sub-multiplexing type in one Abis Link with FR TRE. The assumption is that
there are no extra TS for PS traffic in this example.
Signaling Multiplex
1 4 4 3 2
2 7 6 5 4
3 10 8 8 6
4 13 10 9 8
5 16 13 12 10
6 19 15 14 12
7 22 17 17 14
8 25 19 18 16
9 28 22 20 18
10 31 24 22 20
11 Impossible 26 26 22
12 Impossible 28 27 24
13 Impossible Impossible 30 26
Signaling Multiplex
The following table provides example FR/DR ratios according to Abis size.
* : These numbers result from the need to split any group of three TREs as 2+1 to
facilitate the mapping. Some other choices are possible, as shown by the table.
Via satellite.
When the link is via satellite, the system applies different parameters to wait for
an acknowledgement, in order to repeat frames.
Satellite links cannot be used at the same time on the Abis interface and on the
Ater interface (see Ater Satellite Links (Section 8.7) ).
This feature is only available for 9100 BTSs and later versions.
The following configuration rules apply:
On Abis, the satellite link is considered to be installed between the BSC and
the first BTS of the multidrop. If this is not the case, the drawback is that
timers applied on the first BTS will be unnecessarily lengthened and this
does not support high traffic with poor quality links.
Usually, only a part of the TS is routed via the satellite. The customer must
take care to route the required TS.
For BTS where the satellite link is installed, the following features are not
available:
The BTS must be configured as a free run (no PCM synchronized) (OCXO
synchronization).
Support of fax and data (in CS mode, transparent and not transparent) depends
on timers managed by the NSS part.
GPRS connections are supported over satellite links (Abis or Ater). If GPRS is
activated, there are a number of parameters to be modified.
For OML autodetection via satellite, a timer has been designed to be able
to manage the transmission delay. In that context, OML autodetection via
satellite is possible.
LCS is supported with Abis satellites.
The primary Abis and the secondary Abis of a BTS can be on different TSU of
different racks.
There are no restrictions concerning cross-connection on the primary Abis.
The system does not check for a cross-connect on the secondary Abis.
Cross-connection is not supported on the secondary Abis.
7.9.2 Rules
The following rules apply:
The second Abis per BTS is used for more than 12 TRX feature in one BTS
OML and basic TS are always mapped to the first link and the extra TS for
the TRX
Only an 9100 BTS with SUMA boards or 9110-E Micro BTS supports
the second Abis link
An 9100 BTS with a SUMP board has to be upgraded. An 9100 BTS can
only manage two termination points
Change the Abis from chain to ring if there is a BTS with 2 Abis
Attach a second Abis to a BTS that is not at the end of an Abis chain
Only BTS with G4 TRE or upper are able to support second Abis Link.
It is not possible to have the primary Abis via satellite and the secondary link
by terrestrial means.
8 Ater Interface
This section describes the Ater interface, and corresponding features and
functions.
A terrestrial link referred to as the PCM 2Mbit/s link (64 Kbit/s * 32 Timeslots
= 2048 Kbit/s)
A satellite link.
8.2 Impedance
There are two types of impedance which define access to the transmission
network:
5-8 2 2 2 5-8
9-12 3 3 3 9-12
13-16 4 4 4 13-16
17-20 5 5 5 17-20
21-24 6 6 6 21-24
29-32 8 8 8 29-32
33-36 9 9 9 33-36
37-40 10 10 10 37-40
41-44 11 11 11 41-44
45-48 12 12 12 45-48
53-56 14 14 14 53-56
57-60 15 15 15 57-60
61-64 16 16 16 61-64
65-68 17 17 17 65-68
69-72 18 18 18 69-72
DT16 DT16
ATERHWAYTP ATERHWAYTP
MSC (Unit type=TC) (Unit type=BSC)
ATBX BSC
Site ASMB
DT16 DT16
ASMC
Site
ATBX
DT16 DT16
ATBX
Ater Mux from 31 to 58 that can be connected only to the MFS: E1 Ater
PS (Packet Switch).
The ATER-HWAY-TP 59 and 60 can be used for HSL or PS.
This is why the number of Ater-Hway-TP is not the same on the TC side and on
the 9130 BSC Evolution side. The Ater-Hway-TP from 31 to 58 can only be
used for GPRS dedicated Ater Mux.
For a detailed view of the numbering scheme for the 9130 BSC Evolution -
Ater Mux, refer to Figure 12.
* : DTC: [1..322] [4 x (48 DTC Ater CS + 28 DTC Ater PS + 4 E1 not used)] (CCP) +
2 DTCTCH-RM (OMCP: SBLs 305, 306)
DT16 DT16
APCMTP
ATBX
DT16 DT16
LIU MUX SSW
ATERHWAYTP
ATBX (Unit type=BSC)
X.25
An X.25 link is set between the 9120 BSC and the OMC_R. Depending
on the BSC position related to the OMC_R, this link can be directly
established from the 9120 BSC to the OMC_R via an X.25 network, or
carried up to the TRCU site or the MSC site on the A trunk and then via
an X.25 Network (TS31).
IP
The connection of 9130 BSC Evolution with the OMC-R is based on the
IP protocol on both two routes, namely over direct IP network, or over
Ater and IP network.
GSL
The GSL handles signaling for GPRS paging and for all synchronization
between the BSC and the MFS (TS28).
Qmux
Qmux is always carried in the first nibble of TS 14.
The BSC ensures that all SS7 links use different SLC values
For each added SS7, its SLC equals the highest SLC which is not already
associated with an equipped SS7. This algorithm is performed for newly
added SS7 in the increasing order of SS7 SBL numbering (i.e. the new SS7
with the lowest SBL number must be processed first, and so on).
Such an algorithm is flexible enough to be compatible with any already
installed configuration. Furthermore, in the case of an MSC which does not
handle SLCs equal to "0", it guarantees that the SS7 which is associated
with the SLC "0" will be always the 16th (this SS7 must remain "OPR").
The following table shows SS7, Ater Mux, DTC and Ater numbering. The
Network Location (NAD) is the DTC location in the BSS.
1 1
5 2
9 3
13 4
17 5
21 6
25 7
29 8
33 9
37 10
41 11
45 12
49 13
53 14
57 15
61 16
LSL/HSL
The total number of LSL+HSL is a maximum of 48
The transmission network between the 9130 BSC Evolution and the MSC
ensures the frame integrity for timeslots 1 to 3. HSL links are between the
BSC and MSC.
The mixed mode (LSL+HSL) is not allowed.
Any Ater Mux defined in the BSC configuration can be used to support HSL, but
the BSC checks that these two Ater Mux:
A signalling over IP
The BSC and MSC server are in peer-to-peer mode. The MSC server
terminates the SS7 signalling instead of forwarding it to other SS7 signalling
point. And there is no other SS7 signalling point between BSC and MSC
server
The A Signalling over IP does not work with the other A signalling transfer
modes at the same time
Only the SS7 point code is used as the routing key for M3UA for both MSC
and BSC. The routing key is configured statically instead of being configured
by the routing key registration scenario
8.6 GPRS and GSM Traffic on Ater Mux versus 9120 BSC
8.6.1 Overview
There are two types of Ater Mux links to the MFS:
Dedicated
Mixed.
First state:
Ater Mux is used for GSM traffic
G2 TC rack filled with 4 Ater Mux.
This situation is not applicable to 9125 TC, because the operator configures the
MT120 to Ater Mux mapping with 9125 TC terminal.
X is the number of Ater Mux between the BSC and the GPU
Y is the number of Ater Mux between the GPU and the TC (mixed Ater Mux)
There are a maximum 12/14/16 PCM links at the GPU for traffic. For 9135
MFS, in the case of Fixed Synchronization Sources feature use, only 8 PCM
links can be used for traffic.
The minimum number of GPU-TC and GPU-SGSN links (Y+Z) is 1. The
maximum number of BSC-GPU links is 13, and the maximum number of
BSC-MFS links depends on the BSC configuration. It is also possible to have
one complete PCM (X) with GPRS and a direct connection to SGSN (then
Y can be null). Z also can be null.
A full Ater Mux carries 112 GCH (32 TS - TS0, alarm octet, SS7, GSL)
CS TCH PS GCH*
3/4 84 1/4 32
1/2 56 1/2 60
1/4 28 3/4 88
The TS numbers are a maximum value and depend on the presence (or
not) of signaling links.
The use of GSL on a given Ater Mux takes the place of 4GCH nibbles on
this link.
TS 16 is always occupied for N7, even if it is not used.
On the Ater interface, all the links are handled in the same way. The satellite
link can be installed either on the Ater (between the BSC and the TC), or
on the A interface (between the TC and the MSC). As the latter case is
comparatively rare, the process is referred to as Ater. In the case where
the satellite link is on the A interface, the modification of the transmission
supervision timer is not useful but is implemented.
In the case where only a part of the TS are routed via the satellite, at least
Qmux, X25/MLPPP (if via A interface) must be routed. Non-routed channels
must be blocked either from the MSC or from the OMC-R.
When A interfaces or Ater interfaces are routed via satellite, the SS7 are
configured to use Preventive Cyclic Retransmission (PCR).
0< <= 32 1
32< <=64 2
64< <=96 3
96< <=128 4
128< <=192 3
192< <=256 4
9 A Interface
When A-Flex is applied, one or more MSC serve a CS pool-area, but only
one out of these MSC serves each individual MS
A-Flex feature does not work with core network sharing
One and only one MSC server always controls an interface circuit
10 Lb Interface
The Lb interface is used to connect the 9130 BSC Evolution to the SMLC.
The Support of Lb interface by the BSC with SMLC in IP feature allows a 9130
BSC Evolution to connect to one SMLC.
EN_Lb can be set on Disabled only if all the Lb endpoints of the SMLC
are locked.
11 Iur-g Interface
The Iur-g interface is used to connect the 9130 BSC Evolution with the RNC.
The Iur-g Interface with Enhanced Control Plane feature allows a 9130 BSC
Evolution to be connected with up to 16 neighbour RNCs.
The feature is optional, is activated from OMC-R and the operator can
declare up to 16 neighbor RNCs for one BSC
A new precondition for modifying the BSC SPC is that, if the Iur-g interface
is activated, all Iur-g signaling links of all RNCs must be locked.
12 GB Interface
12.1 Gb Topology
The interface between the MFS and the SGSN is referred to as the Gb
interface. It is supported by 2Mbit/s PCM links of 32 TS at 64Kbit/s.
There are four possible ways to connect the MFS to SGSN:
BSC SM MFS CS TS TC
Mixed CS/GPRS MFSTC Interface
GPRS TS
Conversion
of Protocol
Gb A
Frame Relay Interface Interface
OMC
SGSN MSC
Via Ater Mux links and Gb links through the TC and the MSC, therefore CS
TS are routed transparently to the MSC across the MFS. GPRS TS are
transparent in the TC. GPRS TS are converted to Gb TS in the MFS. The
TC transmission is updated in this case, so that TC is ready when Gb goes
to SGSN through the TC (this is known as TC transparency).
Conversion
GPRS TS of Protocol
Gb
Interface
OMC
SGSN MSC
Frame Relay
Via Gb links from the MFS to SGSN through the MSC, whereby a PCM is
dedicated to Gb interface and GPRS TS are converted to Gb TS in the MFS.
Atermux Interface Atermux Interface
BSC SM MFS CS TS TC
Mixed CS/GPRS MFSTC Interface
GPRS TS
Conversion
of Protocol
A
Interface
OMC Gb
SGSN Interface MSC
Frame Relay
BSC SM MFS CS TS TC
Mixed CS/GPRS MFSTC Interface
GPRS TS
Conversion
of Protocol
Gb A
IP Network Interface Interface
OMC
MSC
SGSN
12.2 Gb Configuration
The BSSGP, Network Service (NS) and physical layer protocols define the Gb
interface. The BSSGP manages GB Interface and Virtual Connections (BVC)
identified by their BVCI.
There are three types of BVC:
BVC-PTP
Virtual circuit Point to Point assigned for the GPRS traffic of one cell: BVCI>1
BVC-PTM
Virtual circuit Point to Multi-point (not used in the BSS): BVCI=1
BVC-SIG
Signaling of all BVC-TTP: BVCI=0.
Only one NSE is declared per GPU board (in the case of multi-GPU per
BSS), so that adding a new GPU for a BSS implies the following on the SGSN
side for the Gb interface:
The definition of a new NSE (the NSE identifier is unique, is an O&M static
information and is given by SGSN)
The definition and declaration on the SGSN side of the PVCs and NS-VCs
of this NSE (NS-VCI are O&M static information) in the case of GboFR
The definition and declaration on the SGSN side of the MFS IpEndpoint, in
the case of GboIP.
The Bearer Channel (in the case of Gb over FR) can be a minimum 64 Kbit/s
TS or a bulk of adjacent 64 Kbit/s TS or a maximum 31 of 64 Kbit/s TS of E1
Digital Hierarchy Transmission Network.
The following figure shows the logical context for the Gb Interface.
The secured single Gb (in the case of Gb over FR) allows the installation
of twice as few GB links (only one E1) than with the former recommended
configuration rules, which required two PCM-TTP and 2 NS-VC per FR-BC
for redundancy. In the case of a GB failure on a given GPU board, re-routing
is done for the whole GB stack (at BSSGP level) of other GPUs of the same
BSS, which have Gb available. There is no impact on the current cell mapping;
that is, cells remain mapped on their related GPUs.
MFS Frame Relay SGSN
NSEi=1 NSEi=1
BSC1 Load Sharing Load Sharing
BVCi=0 Bearer Bearer BVCi=0
Channel=1 Channel=3
DLCi=34 NSVC3
NSVC1
PVC BVCi=2
Callid8 (DLCi=16)
BVCi=2
GPU number 21
As the link between the NSE and GPU is not direct (but through SGSN IP
endpoint or NsVc) the control can be done only when a SGSN IP endpoint
or a NsVc is created in the NSE.
OMC-R should refuse to set the BSS transport mode to FR when Gb flex
feature is enabled.
The NSE can exist without the BSS. But once an NSE is associated to a
BSS, we cant delete the NSE before to remove the association with the
BSS. In the other case, the BSS will try to access to an NSE which does
not exist any more. With Gb-flex, the NSE can be deleted only if it is not
associated to a BSS.
If BSS Gb Transport Mode is IP, all NSEs belonging to the same SGSN,
associated with the same (new) BSS function, holding at least one SGSN
IP endpoint, have the same Configuration type.
This section describes the GSM Short Message Service Cell Broadcast
(SMSCB) features and functions.
13.1 Overview
The GSM SMSCB feature allows the distribution of messages from an SMSCB
centre (CBC) to a mobile station listening in idle mode to a general broadcast
channel called the CBCH.
Applications where the operator offers the Cell Broadcast facility for use
by entities external to the GSM Network. Applications such as road traffic
information, public safety, and advertisements can be a source of additional
revenue for the operator.
13.3 Solutions
13.3.1 9120 BSC Solutions
For the X25 CBC-BSC connection (which differs from the OMC-R connection,
but which must be configured in the same way), several alternative solutions
exist:
PSDN
The secondary link is optional. This redundant link, if it exists, is only used if the
communication with the CBC cannot be achieved using the primary link.
The following figure shows a CBC-BSC interconnection via PSDN.
SM SM TRCU
BTS3
BSC3 MSC3
PSDN
SMCB Path
OMC CBC
Switchovers
BTS1 BSC1
MSC1
SM SM TRCU
BTS2
BSC2 MSC2
Router