GSM/DCS/PCS: Reference: PE/BSC/DD/0317 Date

GSM/DCS/PCS
Reference: PE/BSC/DD/0317
Version: 04.01/EN
Date: 16/01/04
BSC 12000 CUSTOMER PRODUCT OVERVIEW
This confidential document is the property of NORTEL NETWORKS and may not be copied or circulated without permission
Ce document confidentiel est la propriété de NORTEL NETWORKS et ne peut être reproduit ou communiqué sans autorisation
TABLE OF CONTENTS
1. INTRODUCTION ...........................................................................................................................6
2. HIGHLIGHTS.................................................................................................................................7
2.1. Characteristics............................................................................................................................................................. 7
2.2. Product Configurations .............................................................................................................................................. 7
3. GENERAL DESCRIPTION ............................................................................................................8
3.1. Functional Overview................................................................................................................................................... 8
3.2. Architecture ............................................................................................................................................................... 10
4. PHYSICAL LAYOUT ...................................................................................................................12
5. CAPACITY AND CONFIGURATION...........................................................................................14
5.1. Configurations ........................................................................................................................................................... 14

5.1.1. BSC 1201 ............................................................................................................................................................... 15
5.1.2. BSC 1202 ............................................................................................................................................................... 16
5.1.3. BSC 1203 ............................................................................................................................................................... 17
5.1.4. BSC 1204 ............................................................................................................................................................... 18
5.1.5. BSC 1205 ............................................................................................................................................................... 19
5.2. Options ....................................................................................................................................................................... 19

5.2.1. BSCB Boards ......................................................................................................................................................... 19
5.2.2. Flexible DDTI ........................................................................................................................................................ 20
5.2.3. HC100 kit and CPU133 boards ............................................................................................................................. 21
5.2.3.1. New Hardware.............................................................................................................................................. 21
5.2.3.2. Supported BSC 12000 Configurations in V12 ............................................................................................ 22
5.2.3.3. Supported BSC 12000 Configurations in V15 ............................................................................................ 23
5.3. Capacity...................................................................................................................................................................... 23
5.3.1. Traffic Profiles ....................................................................................................................................................... 25
5.3.2. Capacity for V12 BSC 12000 equipped “OLD” hardware ................................................................................... 26
5.3.3. Capacity for V12 BSC 12000 equipped with HC100 & CPU133........................................................................ 26
5.3.4. Capacity impact of GPRS on BSC12000 .............................................................................................................. 27
5.4. Shipping and Installation ......................................................................................................................................... 28
5.5. Physical Characteristics ........................................................................................................................................... 28

5.5.1. Weight .................................................................................................................................................................... 28
5.5.2. Access..................................................................................................................................................................... 29
5.6. Floor Space ................................................................................................................................................................ 30

5.6.1. Cabinet Dimensions ............................................................................................................................................... 30
5.6.2. Clearance ................................................................................................................................................................ 31
BSC 12000 Customer Product Overview Page 2

PE/BSC/DD/0317 04.01/EN 16/01/04
5.7. External Cabling ....................................................................................................................................................... 33
5.7.1. Connectors.............................................................................................................................................................. 33
5.8. Protection ................................................................................................................................................................... 33
5.9. Environment .............................................................................................................................................................. 33

5.9.1. Electrical Environment .......................................................................................................................................... 33
5.9.2. Electromagnetic – Static Environment .................................................................................................................. 34
5.9.3. Climatic Environment............................................................................................................................................ 34
5.9.4. Mechanical Environment....................................................................................................................................... 34
5.9.5. Acoustic Noise ....................................................................................................................................................... 34
6. OPERATION & MAINTENANCE.................................................................................................35
6.1. Configuration Management..................................................................................................................................... 35

6.1.1. Initialization ........................................................................................................................................................... 35
6.1.2. Operation ................................................................................................................................................................ 35
6.2. Performance Management....................................................................................................................................... 35

6.2.1. Permanent Observations ........................................................................................................................................ 35
6.2.2. Temporary Observations........................................................................................................................................ 36
6.2.3. Instrument Panel Observations ........................................................................................................................ 36
6.2.4. V11 new Observation Mechanism............................................................................................................... 36
6.2.5. Call Monitoring Management ............................................................................................................................... 37
6.3. Fault Management .................................................................................................................................................... 37
6.4. Software Management.............................................................................................................................................. 37
6.5. Local Maintenance.................................................................................................................................................... 37
7. TECHNICAL DESCRIPTION.......................................................................................................38
7.1. Hardware Description .............................................................................................................................................. 38

7.1.1. BSC Cabinet Layouts............................................................................................................................................. 38
7.1.2. V10 Hardware ........................................................................................................................................................ 40
7.1.2.1. Control Cabinet ............................................................................................................................................ 40
7.1.2.2. Equipment Cabinet....................................................................................................................................... 43
7.1.2.2.1. Switching Shelf (SWG) .......................................................................................................................... 43
7.1.2.2.2. Mixed Shelf (EQPI)................................................................................................................................ 45
7.1.2.2.3. PCM Shelves (EQPD) ............................................................................................................................ 46
7.1.2.2.4. BSCB Shelf (EQPT) ............................................................................................................................... 47
7.1.2.3. MTBF ........................................................................................................................................................... 47
7.1.3. V11 new Hardware ................................................................................................................................................ 48
7.1.3.1. Control Cabinet ............................................................................................................................................ 48
7.1.3.2. Equipment Cabinet....................................................................................................................................... 50
7.1.3.3. MTBF ........................................................................................................................................................... 50
7.2. Software Description ................................................................................................................................................ 51

7.2.1. OMC Access (AOMC)........................................................................................................................................... 51
7.2.2. Administration (ADM) .......................................................................................................................................... 51
7.2.3. BSC Observation (OBS) ........................................................................................................................................ 51
7.2.4. Radio Observation (OBR) ..................................................................................................................................... 51

PE/BSC/DD/0317 04.01/EN 16/01/04
7.2.5. Traffic Management (TMG).................................................................................................................................. 51
7.2.6. SS7 Protocol Management (SS7) .......................................................................................................................... 51
7.2.7. LAPD Protocol Management................................................................................................................................. 51
7.2.8. Supervision (SUP).................................................................................................................................................. 52
7.3. Duplex Mode.............................................................................................................................................................. 52

7.3.1. Introduction ............................................................................................................................................................ 52
7.3.2. Duplex Operations ................................................................................................................................................. 53
7.3.3. Standby Chain Operation....................................................................................................................................... 54
7.3.4. Data protection ....................................................................................................................................................... 54
7.3.5. Mirroring ................................................................................................................................................................ 54
7.3.6. Switchover Conditions........................................................................................................................................... 54
7.4. Overload Protection.................................................................................................................................................. 54

7.4.1. General description ................................................................................................................................................ 55
7.4.2. Monitored boards ................................................................................................................................................... 56
7.4.3. Overload thresholds and traffic filtering ............................................................................................................... 56
7.4.4. OA&M load control on OMU ............................................................................................................................... 57
7.4.5. Observation counters and overload notification ................................................................................................... 57
7.5. Upgrade ...................................................................................................................................................................... 58

7.5.1. Upgrade of Software Version ................................................................................................................................ 58
7.5.2. Upgrade of a BSC 6000 into a BSC 12000 or BSC 12000HC ............................................................................. 58
7.5.3. Upgrade of a BSC 12000 to a BSC 12000HC ...................................................................................................... 58
7.5.4. Upgrade from one Type to Another ...................................................................................................................... 59
7.5.5. Upgrade with BSCB boards................................................................................................................................... 59
7.6. Interfaces.................................................................................................................................................................... 60
7.6.1. Physical Interface ................................................................................................................................................... 60
7.6.2. Abis Interface ......................................................................................................................................................... 60
7.6.2.1. Configurations .............................................................................................................................................. 60
7.6.2.2. Signaling....................................................................................................................................................... 61
7.6.2.3. Traffic ........................................................................................................................................................... 61
7.6.2.4. Dimensioning ............................................................................................................................................... 61
7.6.2.5. Fault Protection ............................................................................................................................................ 61
7.6.3. Ater Interface.......................................................................................................................................................... 62
7.6.3.1. Configurations .............................................................................................................................................. 62
7.6.3.2. Signaling....................................................................................................................................................... 62
7.6.3.3. Traffic ........................................................................................................................................................... 62
7.6.3.4. Dimensioning ............................................................................................................................................... 62
7.6.3.5. Fault Protection ............................................................................................................................................ 63
7.6.4. BSC-OMC Interface .............................................................................................................................................. 63
8. APPENDIX...................................................................................................................................64
8.1. References .................................................................................................................................................................. 64
8.2. Abbreviations ............................................................................................................................................................ 64

PE/BSC/DD/0317 04.01/EN 16/01/04
Figure 1: BSC 12000

PE/BSC/DD/0317 04.01/EN 16/01/04
1. INTRODUCTION
The BSC 12000 is an extension of the previous Nortel Matra Cellular product named
BSC 6000. Thanks to a larger processing capability while keeping its modularity, it is
suitable for various network configurations. A BSC 6000 is upgradable into a BSC
12000 on site.
This document is applicable to the BSC 12000 until software release V15.
Figure 2: System Overview

PE/BSC/DD/0317 04.01/EN 16/01/04
2. HIGHLIGHTS
2.1. CHARACTERISTICS
The Nortel Matra Cellular BSC 12000 has been designed for indoor installation and
may be seen as a cost effective solution for a fast roll out of a GSM, DCS or PCS
network. The BSC 12000 can be located either as a standalone equipment or
colocated with the MSC or the BTS. This location flexibility allows to optimize the costs
of the BSS transmission network. The BSC 12000 can be used as an intermediate
concentration node by locating the transcoders at the MSC site and the BSC at a
remote location. The transmission cost is then reduced by using sub-rate channel
multiplexing in the interface between the MSC and the BSC. This results in four times
the standard PCM capacity in terms of traffic channels.
Advanced solutions have also been developed for the BTS transmission network.
Indeed in order to save on transmission cost, sub-rate channel multiplexing and
signaling concentration is supported on the Abis interface. Furthermore, a complete
range of network topologies such as star, chain and loop are available.
2.2. PRODUCT CONFIGURATIONS

The BSC 12000 product portfolio consists in five BSC configurations which are
indicated below:
1201 1202 1203 1204 1205
Maximum number of sites 28 60 92 124 138
Maximum number of TRX 64 128 192 256 320
Figure 3: BSC 12000 configurations

PE/BSC/DD/0317 04.01/EN 16/01/04
3. GENERAL DESCRIPTION
The BSC 12000 plays an active role in the Base Station Subsystem (BSS)
operations. In addition to linking the Mobile Stations with the MSC, the BSC
12000 ensures the supervision and the defense of the Base Stations and the
Transcoders. The BSC also participates actively in the Operation and
Maintenance of the BSS.
3.1. FUNCTIONAL OVERVIEW

The BSC performs the following functions:
- BTS supervision
- Radio channel allocation
- Radio channel monitoring
- Call processing
- TCU management
- OMC-R link management
- Measurement processing
- Power control procedures
- Handover procedures
- Operation and maintenance request from the OMC-R processing
- BSS configuration data and software storage
- Failure detection and processing

PE/BSC/DD/0317 04.01/EN 16/01/04
These functions are divided into the following classes:
• AOMC Access to the OMC-R via the X25 network
• ADM Configuration and operational management of the radio

subsystem
• OBS BSC observations - BSS performance management
• OBR Call monitoring and radio observations
• TMG Traffic Management - call handling procedures
• SS7 CCITT #7 protocol management - MSC access
• LAPD LAPD protocol management - BTS and TCU access
• SUP Supervision - defense and reconfiguration
Figure 4: BSC classes of functional units

PE/BSC/DD/0317 04.01/EN 16/01/04
3.2. ARCHITECTURE
The BSC 12000 equipment holds in two cabinets, the control and the
equipment cabinet.
For high reliability the BSC 12000 has a duplicated core processing module
which operates in active/standby mode. Each of these two modules contains a
switching matrix and a control unit. Peripheral modules are partnered with the
two processing modules or chains but are controlled by the active chain.
CONTROL CABINET
ACTIVE CHAIN STANDBY CHAIN

OMU MPU BIFP/SICD OMU MPU BIFP/SICD
AOMC TMG TMG AOMC TMG TMG
ADM ADM
SUP SUP SUP SUP
OBS OBS
OBR SS7 LAPD OBR SS7 LAPD
OMC MSC BTS
SWITCHING SWITCHING
MATRIX EQUIPMENT CABINET MATRIX
Figure 5: Duplicated core structure
The software architecture can be tailored to fit into different hardware

structures and is divided into logical processing units. A series of boards and
processors provide each logical unit with the processing power that is needed.
The BSC 12000 main processing boards are :
• The Main Processing Unit (MPU)
• The Base Interface Front-end Processor (BIFP)

• The Operation and Maintenance Unit (OMU)
• LAPD Signalling interface controller (SICD)

PE/BSC/DD/0317 04.01/EN 16/01/04
The control cabinet contains the processing core that directs the overall BSC
operations, including the equipment cabinet operations and insures the
communication with the Radio Operation and Maintenance Center (OMC-R).
The control cabinet contains two identical processing cores which operate in
duplex mode (active/standby).
The equipment cabinet contains the switching matrix, different interface
modules and the equipment for the management of the PCM links. Duplication
or redundancy of the boards ensures service continuity in the event of a failure.

PE/BSC/DD/0317 04.01/EN 16/01/04
4. PHYSICAL LAYOUT
Power
supply
Power
PCM Shelf supply EQPD
MPU - A Power
PCM Shelf supply
Shelf
Mixed
Power
equipment
Shelf supply EQPI
Power
supply
Matrix A Matrix B Power

MPU - B supply SWG
Shelf
Power
BSCB Shelf EQPT
supply
Control Cabinet Equipment Cabinet

Figure 6: BSC 12000 physical layout
The BSC 12000 equipment is divided into several shelves which are the two
Main Processing Unit shelves (MPU), three Equipment cabinet shelves (EQPD,
EQPI and EQPT) and the Switching Unit shelf (SWG).
The MPU processing chain is duplicated for reliability and operates in matched
pairs (MPU-A and MPU-B). Each of these units includes:
• CPU - MPU/BIFP central management units
• CPU - OMU central management unit
• Mass Memory unit (MMU)
• X25 interface controller (SICX)
• LAPD interface controllers (SICD8V)
• CCITT SS7 interface controller(s) (CCS7)

PE/BSC/DD/0317 04.01/EN 16/01/04
• Supervision board (SUP)
• Serial Link Switching unit (SLS)
The equipment cabinet shelves contains:
• a duplicated equipment cabinet interface unit (ECI)
• an external ALArm regrouping board (ALA)
• Dual Digital Trunk Interfaces boards (DDTI)
• duplicated Rate Converter Boards (RCB)
• TCU Signaling link Concentration Boards (TSCB)
• BTS Signaling link Concentration Boards (BSCB)
The switching module SWG is duplicated for reliability and accommodates:
• a SWitching Control Board (SWC)
• two Master SWitching boards (MSW)
• two extension boards controlling 16 additional links (SWE)

PE/BSC/DD/0317 04.01/EN 16/01/04
5. CAPACITY AND CONFIGURATION
The maximum capability of the BSC 12000 has to be considered with two
lights:
− the maximum physical connectivity which is described in the chapter
"Configurations"
− the maximum processing power available for handling the various signaling
procedures which is described in the chapter "Capacity"
The two parameters are linked to the traffic model, but there are a lot of traffic
models giving the same traffic with various processing loads in particular due to
the network configurations. So, several typical traffic models are given as
examples to show a possible use of the BSC 12000.
5.1. CONFIGURATIONS
The BSC 12000 exists in five different basic configurations which all hold in two
cabinets. The different configurations are named BSC 1201, 1202, 1203, 1204
and 1205.
In V9, only the hardware of the BSC 12000 is available.
In V10, the BSC 12000 reaches its full capacity (in terms of the number of
configured TRXs and in terms of traffic which can be supported).
In V11, some new boards are available for the BSC 12000 : CPU133 and
HC100 kit. These boards will allow the BSC 12000 to reach its full erlang
capacity for most of traffic profiles.
From V15, only the BSC12000 with HC100 kit and with CPUE boards (BIFP &
MPU) with 32 MB of RAM is supported (see details in HC100 kit chapter
below).

PE/BSC/DD/0317 04.01/EN 16/01/04
5.1.1. BSC 1201
BSC 1201 Dimensioning V10-V12

number of PCM 48
number of LAPD port 8
number of TEI per LAPD port 15
number of TRX per SICD 64
maximum number of LAPD connections with BSCB 28

option*
maximum number of CELLs 120
number of TDMA (configured TRX) 64
number of TRX (configured & non configured) 200
number of TCU (E1 PCM) 12
number of TCU (T1 PCM) 14
number of terrestrial circuits (E1 PCM) 1440
number of terrestrial circuits (T1 PCM) 1288
number of SS7 links 2
* The number of LAPD connections can be equal to the number of sites in case of
S111 sites for instance, because only one LAPD is necessary for this kind of site. But
if a site requires multiple LAPD, the number of sites supported by the BSC is lower
than the number of LAPD connections.

PE/BSC/DD/0317 04.01/EN 16/01/04
5.1.2. BSC 1202

number of PCM 48

option*

PE/BSC/DD/0317 04.01/EN 16/01/04
5.1.3. BSC 1203

number of PCM 48
option*
number of TDMA 192

PE/BSC/DD/0317 04.01/EN 16/01/04
5.1.4. BSC 1204

number of PCM 48
option*

PE/BSC/DD/0317 04.01/EN 16/01/04
5.1.5. BSC 1205

number of PCM 48
option*
5.2. OPTIONS
5.2.1. BSCB BOARDS
The maximum number of sites of a BSC 12000 can be increased by the use of
additional BSCB boards. These boards will concentrate LAPD signaling coming from
multiple BTS sites onto a single LAPD link.
These additional BSCB boards will be particularly useful for microcellular configurations
where a lot of sites are necessary to use the whole erlang capacity of the BSC. The
usage of these additional BSCB boards is optional and the operator has the possibility
to add them when required.
A shelf is reserved in the equipment cabinet of the BSC 12000 for up to 12 BSCB
boards.

PE/BSC/DD/0317 04.01/EN 16/01/04
The table below gives the number of LAPD links that the BSC can support in
relation to its type and the number of BSCB boards. The figures are given
considering that one board is needed for redundancy purpose (n+1
redundancy).
Nb of BSCB BSC 1201 BSC 1202 BSC 1203 BSC 1204 BSC 1205
0 7 15 23 31 39
2 16 24 32 40 48
3 25 33 41 54 57
4 28 42 50 58 66
5 51 59 67 75
6 60 68 76 84
7 77 85 93
8 86 94 102
9 92 103 111
10 112 120
11 121 129
12 124 138
Figure 7: Maximum number of LAPD connections with optional BSCB

concentration boards (one BSCB is redundant).
5.2.2. FLEXIBLE DDTI

The number of external PCM links is the total number of PCM links on the Abis and the
Ater interface together. This number is scaleable for all the BSC types in a range of 20
to 48 to be suited to the specific Abis configuration (star, drop/insert).

PE/BSC/DD/0317 04.01/EN 16/01/04
5.2.3. HC100 KIT AND CPU133 BOARDS
5.2.3.1. New Hardware

With V11, new boards are available to equip the BSC 12000: HC100 kit and CPU133
boards. These boards are mandatory from V15.
The HC100 kit is made of:
• a new CPU-OMU board called CPU133IE
• a new MMU board called MMU-IDE
• a new SLS board called SLS2
• a new SUP board called SUP2
The BSC 12000 equipped with the HC100 kit is called BSC 12000HC which is the only
one configuration supported from V15.
The CPU133 board is the new board used as CPU-BIFP and CPU-MPU boards. It
replaces the CPU120 board for obsolescence reason.
Important note : Starting in January 2000, the CPU133 boards are
introduced as well in V10 BSC12000 (without the HC100 kit), in order to
cope with a shortage of CPU120. This new variant of BSC12000 will be
supported exactely like the BSC12000 with CPU120 in V10 and from V12
on.
Those new boards address two requirements :

• increased capacity and robustness for tough traffic profiles
• extension of BSC12000 life-cycle : RAM extension allowing the delivery of
software releases in the years 2000’.
Capacity and Robustness

The HC100 kit together with the CPU133 BIFP&MPU boards allow to improve the BSC
12000 capacity in case of hard traffic profiles and to improve the BSC 12000
robustness and defense. The traffic capacity of the BSC 12000HC equipped with
CPU133 is increased by up to 30% for tough traffic profiles (e.g. short calls or high
mobility profiles) compared to the standard BSC 12000.
Note : The BSC12000HC/CPU133 capacity increase applies when the traffic
profile is tough and pushes the BSC to either the BIFP/MPU processor limit or
the OMU/SUP limit : it is the case for Nortel “short call” and “high mobility”
profiles. See §5.3.

PE/BSC/DD/0317 04.01/EN 16/01/04
The OMU CPU133IE and SUP2 boards provide the BSC with an increased traffic
handling and OA&M processing capabilities. The new OMU is 3 times more
powerful than the previous CPU66SE board. The OMU manages both the OA&M
(software downloading, observations, traces, fault supervision & notification...), and the
connections with the switching matrix via the SUP board (OMU-SUP-SWC link). It is
therefore important to increase simultaneously the processing of both OMU and SUP
boards, and make it consistent with the processing level of MPU/BIFP and SICD8V
boards.
The CPU133 is about 20% more powerful than the CPU120 and hence provide more
traffic handling capacity to the BIFP&MPU boards.
SLS2 board along with SUP2 board allows the automatic testing of the BSC/OMC-R
link and the enhanced defense of the BSC in case of a communication failure with the
OMC-R.
BSC12000 life-cycle extension
The CPU133 (BIFP/MPU) and CPU133IE (OMU) boards are equipped with 32 Mb of
RAM. The 16 Mb of RAM on old CPU66 and CPU120 processors will be exhausted
with V14 BSS release. Hence those new processors will extend the life-cycle of
BSC12000, allowing new software releases to be delivered after V14.
From V11 release, the BSC 12000 is equipped with an homogeneous set of main
processors, all based on CPU133 mother board (OMU, MPU, BIFP, SICD), giving
to the BSC a well balanced processing capability able to cope with tough traffic
profiles, and ensuring the delivery, software evolution and sustaining of the BSC
12000 well into the years 2000’.
5.2.3.2. Supported BSC 12000 Configurations in V12

The HC100 kit and the CPU133 equip newly shipped BSC 12000.
The BSC 12000 already installed in the field can be upgraded with the HC100 kit as an
option, for capacity and robustness reasons. The CPU120 can either be kept or
replaced by CPU133 in order to get the latest and most powerful processor in the BSC.
If the CPU120 are kept, then those boards have to be upgraded with RAM from 16 Mb
to 32 Mb. The BSC12000HC with CPU133 offers about 30% higher capacity for tough
traffic profiles, compared to BSC12000 with CPU120.
A BSC6000 can be upgraded to BSC 12000 or BSC 12000HC.

The following configurations of BSC12000 are supported in V12 :
V12 BSC12000 BSC12000 BSC12000HC

OMU/MMU CPU66SE/SCSI disk CPU133IE/IDE disk
BIFP/MPU CPU120 or CPU133 CPU120 (32 Mb) or CPU133
SICD SICD8V SICD8V
SUP/SLS SUP/SLS SUP2/SLS2
Note: Old (CPU66SE & CPU120) and new hardware (HC100&CPU133) cannot be mixed in
the two chains of a same BSC.

PE/BSC/DD/0317 04.01/EN 16/01/04
5.2.3.3.Supported BSC 12000 Configurations in V15
From V15, the only one supported BSC configuration is the BSC12000 HC.
Note: V15.0 supports only the BSCe3. The BSC2G will be supported from V15.1.
The following boards are mandatory in V15:
• CPU-OMU board called CPU133IE is mandatory
This CPU-OMU board handles mainly the Observations, BSC Supervision, BSC
Administration functionalities...
The RAM size of the old CPU-OMU66SE (16MB RAM) is a limiting factor. The
introduction in V15 of new features as maximum BSC counter list, …imposes to extend
the RAM size of the CPU-OMU to 32MB.
From V15, the only one supported CPU-OMU board is the CPU133IE.
• MMU board called MMU-IDE is mandatory

The introduction of the CPU133IE (IDE + Ethernet) imposes to replace the Hard disk
technology from SCSI to IDE.
From V15, the only one supported MMU board is the MMU-IDE Quantum Fireball.
• SLS board called SLS2 and a new SUP board called SUP2 are mandatory
SLS2 board along with SUP2 board, allows an automatic testing of the BSC/OMC-R
link and an enhanced defense of the BSC in case of communication failure with the
OMC-R.
• CPUE boards (BIFP & MPU) with 32 MB of RAM are mandatory

As per the CPU-OMU, the RAM size of the CPUE boards is the bottleneck for the
software evolution. The introduction of new Traffic Management and Radio Supervision
features (WPS, GSM-R features, BTS Background Downloading, ...) imposes to
extend the RAM size of the BIFP and MPU to 32 MB.
From V15, the only one supported BIFP-MPU boards are the CPU133 or the CPU120
32MB.
The CPU120 16MB needs to be upgraded to 32MB RAM.
5.3. CAPACITY
WARNING: The customer detailed traffic model and all engineering parameters
are necessary to compute the exact erlang capacity of the BSC 12000. The
capacity figures given in this section are computed for a “model network” (not
real and not including all engineering parameters) and for the 3 Nortel traffic

PE/BSC/DD/0317 04.01/EN 16/01/04
profiles. These figures shall not be used in any case to dimension the BSCs for a
real network.
The engineering documents written for each specific network are the reference
for BSC capacity in that network.
Several parameters are highly impacting this Erlang capacity:

- location updates
- paging
- handovers
- short messages
- average call holding time
This is due to the fact that the required processing level in the different BSC
processors for a given carried traffic level is dependant on the characteristics of the
traffic.
Moreover, in order to take into account the instantaneous traffic load variations, some
additional margins are to be considered for the following boards:
- CPU-BIFP and CPU-MPU: These board loads have to remain under 70% in
order to avoid the overload phenomenon which appears at this level.
- SICD8V: An overload mechanism has been implemented in these SICD8V
boards. The overload threshold is 100% during a few seconds. Standard
engineering rule is to use 70% of the maximum load on these boards. This
allows to compensate for the variation around the mean profile and the load
differences between the boards.
- OMU-SUP-SWC: The performance level of this processors’ chain defines the
number of switching matrix connections per second that the BSC can handle.
Engineering thresholds (number of processed messages per seconds) are used
to dimension the BSC capacity according to the processing capability of the
OMU and SUP boards. The OMU CPU133IE and SUP2 boards increase the
BSC capacity because they can process a higher number of messages per
second than the OMU CPU66SE and SUP boards.
These thresholds are the typical thresholds used for network engineering. However,
depending on the network and customer requirements, lower thresholds can be taken
into account for BSC dimensioning. These thresholds are defined to take into account
the traffic profile, the expected variation around this traffic profile and the expected
quality of service (amount of traffic filtered for overload reason)...
So even for the same traffic profile, the BSC capacity can be different, depending on
the network and on the real behavior of the subscribers using the network.
The following tables show the computed capacity figures for 3 Nortel traffic profiles for
the different types of BSC 12000.

PE/BSC/DD/0317 04.01/EN 16/01/04
5.3.1. TRAFFIC PROFILES
The following table describes the 3 Nortel traffic profiles used to calculate the BSC
12000 erlang capacity. The High mobility and Short call traffic profiles are tougher
respectively in mobility parameters and call duration parameters, than what is
encountered in most of Nortel customer networks.
Short
Nortel High
call
standard mobility
duration
traffic traffic
traffic
model model
model
Traffic per customer 0,025 0,025 0,025
Number of BHCA per customer 1 1 2,25
Blocking rate on TCH 5% 5% 5%
Number of active subscriber in the LAC (paging load) 40000 40000 40000
Number of cells managed by the BSC 50 50 50
Average call holding time 120s 120s 45s
Average call duration 90s 90s 36s
Land to mobile traffic ratio 33% 33% 33%
Mobile to land traffic ratio 65% 65% 65%
Mobile to mobile traffic ratio 2% 2% 2%
Intra BSC Handovers per call 0,65 2,5 0,65
Inter BSC Handovers per call 0,25 0,7 0,25
Inter MSC Handovers per call 0,05 0,1 0,05
Periodic location updates per active subs in BH 0,2 1 0,2
Inter Location Area updates per active subs in BH 0.8 2,5 0.8
IMSI detach per inactive subscriber in BH 0,35 0,45 0,35
IMSI attach per active subscriber in BH 0,35 0,45 0,35
SMSC to mobile short message per subscriber in BH 0,02 0,02 0,02

PE/BSC/DD/0317 04.01/EN 16/01/04
5.3.2. CAPACITY FOR V12 BSC 12000 EQUIPPED “OLD” HARDWARE
The following table show the estimated erlang capacity of BSC 12000 types 1 to 5
equipped with “old” hardware.
BSC12000 V12 Standard High Mobility Short Call

capacity Profile Profile Profile
(1) (1)
BSC1201 Erlang 500 250 150
BHCA 20 000 10 000 15 000
(2) (2)
BSC1202 Erlang 750 500 350
BHCA 30 000 20 000 35 000
(3) (3)
BSC1203 Erlang 1 200 750 650
BHCA 48 000 30 000 65 000
(3) (3)
BSC1204 Erlang 1 200 750 650
BHCA 48 000 30 000 65 000
(3) (3)
BSC1205 Erlang 1 200 750 650
BHCA 48 000 30 000 65 000
(1) The SICD processor is the limiting factor for the BSC capacity
(2) The BIFP processor is the limiting factor for the BSC capacity
(3) The OMU-SUP-SWC processor chain is the limiting factor for the BSC capacity
5.3.3. CAPACITY FOR V12 BSC 12000 EQUIPPED WITH HC100 & CPU133
The following tables show the estimated erlang capacity of BSC 12000 types 1 to 5
equipped with HC100 and CPU133.
BSC12000HC V12 (CPU133) Standard High Mobility Short Call

capacity Profile Profile Profile
(1) (1)
BSC1201 Erlang 500 250 150
BHCA 20 000 10 000 15 000
(2) (2)
BSC1202 Erlang 750 650 450
BHCA 30 000 26 000 45 000
(1)
BSC1203 Erlang 1 200 1 200 950
BHCA 48 000 48 000 95 000
BSC1204 Erlang 1 200 1 200 1 200
BHCA 48 000 48 000 120 000
BSC1205 Erlang 1 200 1 200 1 200
BHCA 48 000 48 000 120 000
(1) The SICD processor is the limiting factor for the BSC capacity
(2) The BIFP processor is the limiting factor for the BSC capacity

PE/BSC/DD/0317 04.01/EN 16/01/04
5.3.4. CAPACITY IMPACT OF GPRS ON BSC12000
The signalling between the BSC and the PCU requires some additional processing (in
addition to GSM voice & circuit data call processing) on the SICD8V boards : +10%
with 5% GPRS subscribers. Since the SICD8V boards have enough processing margin
and are not limiting even for tough voice traffic profiles, they shall absorb this additional
processing, without impacting significantly the BSC capacity in terms of GSM voice
traffic.
When a GSM voice call need to preempt a radio resource allocated to GPRS (shared
resource), this call will cost about 10% more in terms of BSC processing. So according
to the GSM/GPRS network engineering and the ratio of pre-empting calls, GPRS can
impact the BSC traffic capacity from 0% to 10%. If there is no pre-emption of GSM
over GPRS (ie. GSM & GPRS have their own radio resource statically pre-defined),
then GPRS entails no voice traffic capacity impact on the BSC.
Since some PCM links need to be assigned to Agprs interface, as well as 1 non-
concentrated LAPD per Agprs, the BSC engineering may be impacted with GPRS
introduction : the Abis, Ater and Agprs interfaces and LAPD need to be dimensioned
within the constraint of 48 maximum PCM links of the BSC and 39 LAPD (non-
concentrated).

PE/BSC/DD/0317 04.01/EN 16/01/04
Installation
5.4. SHIPPING AND INSTALLATION

The BSC is fully assembled in standard delivery conditions, except for the 5V-100A
converter and the MMU board which are shipped separately. The cabinets are shipped
on wooden pallets which allow handling by means of a fork-lift truck.
The local testing is the first step of the BSC commissioning operation. This procedure
is carried out between the physical installation of the product on site and the on-line
tests of the BSC and its assigned TCU.
The local test is designed to check that the equipment has not been damaged during
transportation, on-site installation and connection, and hence that the installation
complies with specifications.
The tests validate the hardware configuration of BSC cabinets, the physical paths
inside the BSC and inter-operability of the different boards that activate the lower levels
protocols.
5.5. PHYSICAL CHARACTERISTICS

5.5.1. WEIGHT
Each cabinet weights about 220 kg (485 lb.). The site floor should withstand
the load of 700 kg/m2 (145 lb./sq. ft).

PE/BSC/DD/0317 04.01/EN 16/01/04
5.5.2. ACCESS
The cabinets can be placed side by side or back-to-back. Each cabinet is

equipped with a swing-out frame for ease of access to the rear cabinet back
panel, the inside cabinet cables and the external connections. These cables
can come out either through the top or the bottom panels of the cabinet.
This arrangement is very useful for installation and configuration purposes and
in addition makes on site interventions much easier. The cabinets must be
bolted down to the floor.
120 cm
(3'11")
Control Control
cabinet cabinet 100 cm (3'3")
40 cm
(1'3")
Control Control
cabinet cabinet 60 cm (1'11")
120 cm
(3'11")
Figure 8: Back to back installation

PE/BSC/DD/0317 04.01/EN 16/01/04
5.6. FLOOR SPACE
5.6.1. CABINET DIMENSIONS
2000 mm
(6'6")
600 mm 780 mm
(1'11") (2'6")
Side view Front view
Figure 9: BSC 12000 (closed door)

PE/BSC/DD/0317 04.01/EN 16/01/04
The BSC 12000 consists of two cabinets (control and equipment). The dimensions of
each cabinet are:
Height: 2000 mm (6 '7'')
Width: 780 mm (2'7'')
Depth: 600 mm (2')
Figure 10: BSC 12000 cabinet dimension
5.6.2. CLEARANCE
The minimum free space distances and free surfaces to take into account for BSC
installation are given in the following table. Note that a minimum of 300 mm/1' false
flooring is required if the cable connections are made through the bottom panel of the
BSC cabinets. The cabinets require an unobstructed space of 400 mm/1'4" above the
cabinet if the cable connections are made through the top panel.
Floor space for one BSC (1560 mm/5'2'' x1800 mm/5'11'') 2.8 m2 (30 sq.ft)
Minimum required height (including 400 mm/1'4'' clearance) 2.4 m (7'3'')
Recommended height 3.5 m (11'6'')
Front access clearance 1200 mm (3'11'')
Left side clearance, from the cabinet closest to the wall 400 mm (1'4'')

PE/BSC/DD/0317 04.01/EN 16/01/04
48V distribution 48V + ground
panel 48V filters cable
Cable
path
REAR
Connector SIDE
strips
Connector strip
labels
Frame Swing-
fixtures for out frame
transport catch
Swing-out
frame Ground
bar
FRONT
SIDE
Right side Shelves Door
Figure 11: BSC 12000 (swing out frame opened)

PE/BSC/DD/0317 04.01/EN 16/01/04
5.7. EXTERNAL CABLING
5.7.1. CONNECTORS
Connectors Type
PCM Connectors E1: 75 ohms, coaxial, asymmetric, female

120 ohms, HE5, 15 pins, symmetric, female
T1: 100 ohms, HE5, 15 pins, symmetric, female
48V and 0V Locking screw, wire > 10 mm2
Ground Locking screw, wire > 10 mm2
X25 HE5, 25 pins, female
Alarms HE5, 25 pins, female
5.8. PROTECTION
The BSC conforms to EN 60950 for GSM and DCS, UL 1950 for PCS
5.9. ENVIRONMENT
5.9.1. ELECTRICAL ENVIRONMENT

The cabinets have to be supplied with –48 V (–40 to –56 V) or –60 V (–48 to
-72V). The control cabinet is protected by four 25 A fuses and consumes at
maximum 1000 W. The equipment cabinet is protected by five 15 A fuses and
consumes at maximum 600 W.
The following table shows the typical power consumption for the different BSC
12000 types:
Control cabinet Equipment cabinet Equipment cabinet

(CPU120 or CPU133) (without BSCB) (with BSCB)
Type 1 674 435 463
Type 2 754 440 486
Type 3 860 448 516
Type 4 920 455 547
Type 5 1000 463 555

PE/BSC/DD/0317 04.01/EN 16/01/04
5.9.2. ELECTROMAGNETIC – STATIC ENVIRONMENT
In DCS and GSM, the BSC complies with ETS 300 342-2 and EN55022 class A
relating to the electromagnetic and electrostatic environment.
In PCS 1900, the BSC complies with CFR 47 part 15 subpart B class A relating
to the electromagnetic environment.
5.9.3. CLIMATIC ENVIRONMENT

In PCS, DCS and GSM, the BSC complies with the following climatic
environment standards:
• ETS 300-019 1-3/2-3 class 3.1 for Operating, Weather protected locations
• ETS 300-019 1-1/2-1 class 1.1 for weather protected, partly temperature
controlled storage location.
• ETS 300-019 1-2/2-2 class 2.2 for “careful” transportation.
The BSC operates between –5°C and +45°C. However, the starting of a BSC can only
be performed between +5°C and +45°C.
5.9.4. MECHANICAL ENVIRONMENT

In PCS, DCS and GSM, the BSC complies with CSEI 13-10.
5.9.5. ACOUSTIC NOISE

The acoustic noise is characterized using the two following parameters:
- the acoustic pressure
- the acoustic power
The method used to measure the acoustic pressure and power conforms to NF EN
27779 and ISO 3743/3744.
The acoustic pressure measured value is 60 dBA.
The acoustic power measured value is 70 dBA (referenced to 1pW).

PE/BSC/DD/0317 04.01/EN 16/01/04
6. OPERATION & MAINTENANCE
The BSC 12000 offers an object oriented interface to the OMC-R which hides
the actual implementation of the various BSC entities and functions. All the
information coming from the BSC or going to the OMC-R relate to these
operator specific objects.
The BSC 12000 sends the following information to the OMC-R:
• Observation counters, i.e. the counters defined in the GSM 12.04
specifications, and some additional Nortel specific counters
• Event reports: these event reports mainly refer to physical or logical
entity failures
• Call tracing information: in conformance with GSM 12.08 specifications
6.1. CONFIGURATION MANAGEMENT

6.1.1. INITIALIZATION
The OMC-R is in charge of managing the connections with the BSC, the BSC
initialization.
6.1.2. OPERATION
The BSS configuration set of commands allows an OMC-R user to create a BSS
network, to update it by creating new elements, modifying or deleting the existing ones,
and to get all useful information about all elements in the BSS network managed by the
OMC-R (equipment and links between them). Hardware configuration requests and
BSC Q3 object actions are performed from the OMC-R.
6.2. PERFORMANCE MANAGEMENT

6.2.1. PERMANENT OBSERVATIONS
The BSC general permanent observation are allowing a continuous collection of
measurement data with a view to deferred statistical processing. The general
permanent observations are activated and stopped on the operator’s request.

PE/BSC/DD/0317 04.01/EN 16/01/04
6.2.2. TEMPORARY OBSERVATIONS
The temporary observations are allowing the measurement data to be collected over a
limited period of time:
- interference (channel idle level) temporary observations,
- handover temporary observations
- pair of cells temporary observations
- signaling link temporary observations
- Abis interface temporary observations
- PCM link temporary observations
The user can list the available messages for a temporary observation for which the
data are available in the OMC-R disk.
The user can consult a temporary observation report by giving the observation type
and a date which is the start time of the backward search for the message.
6.2.3. INSTRUMENT PANEL OBSERVATIONS

The instrument panel observations of the OMC-R collect a small number of highly
significant measurement data which are displayed in almost real time.
6.2.4. V11 NEW OBSERVATION MECHANISM

This new mechanism will provide 4 types of permanent observations:
• Real Time Observations: a small set of counters can be displayed in real time
for network supervision.
• Diagnostic Observations: allows launching observations on a small set of cells
(2 diagnostic observations per OMC-R, and 4 cells per BSC) with a large set of
counters.
• Fast Statistic Observations: allows making statistics on a one-hour basis.
• General Statistic Observations: allows making statistics on a per-day basis.
This new mechanism allows to increase the efficiency of observation counters flow
from the BSC to the OMC-R (number of counters reported every period vs their
usefulness for the operator). It improves as well the BSC and OMC-R robustness by
reducing the X25 link load between the BSC and the OMC-R.
Moreover, the operator will be able to configure its own set of counters in each of the 4
family types in the following releases. Counters not used by the operator will not load
the BSC, the OMC-R or the X25 link between the BSC and the OMC-R.

PE/BSC/DD/0317 04.01/EN 16/01/04
6.2.5. CALL MONITORING MANAGEMENT
The Call Trace function is the GSM 12.08 trace facility of the BSC. It enables to trace
the activities associated with specific communications in a BSC (in fact to trace specific
subscribers (IMSI) or specific equipment (IMEI)), and to transfer these data to the
associated OMC-R. This function is initiated at OMC-S level, through MMI-commands
to allow a trace record to be produced for a particular IMSI or IMEI. When a trace is
invoked in a BSS, BSSMAP MSC INVOKE TRACE message is sent by the MSC to the
BSC. On receipt of this message, the BSC starts tracing the specified call.
The Call Path Trace function allows tracing of communications which take place on
specific resources of the BSS ( CICs, TRXs or Cells).
A session of Call Path Trace is initiated in the BSC by the OMC-R.
6.3. FAULT MANAGEMENT

The Fault Management (FM) function of the OMC-R translates the events reports
coming from the BSC into understandable user notifications. Some notifications,
according to predefined criteria, will trigger alarms at the OMC-R.
All events received by the OMC-R are translated into user-notifications and some
information are added to them.
The OMC-R converts the logical identifiers of the sub-system into identifiers
understandable by the user. The location of the faulty element is created thanks to the
knowledge of the type of the BSS which gives the characteristics of its hardware
configuration.
For each type of BSS, the location (equipment, cabinet, rack, slot) of each element of
this BSS using the equipment type and number (respectively, chain identity, processor
type and number) is given.
6.4. SOFTWARE MANAGEMENT

Software management is done from the OMC-R. The OMC-R is able to download and
trigger the replacement of software and to notify which software releases are running.
Only the files not already present on the BSC disk are transferred. This mechanism
reduces the global downloading time.
6.5. LOCAL MAINTENANCE

Maintenance is performed through the OMC-R. Moreover, a local maintenance
terminal can also be connected to CPU-OMU boards of the BSC for on-site trouble
shooting.

PE/BSC/DD/0317 04.01/EN 16/01/04
7. TECHNICAL DESCRIPTION
7.1. HARDWARE DESCRIPTION
7.1.1. BSC CABINET LAYOUTS
PSUC MPUA power

supply
Power supply
fans
MC C C SC SS S SC S C SC S
MC C P I P I UL I PI P I C I
USSU CU CP S CU C U CS C
77- D- D X- D- D7 D
S 8M 8 B8B 8 8 MPUA shelf
E VP V I VI V V
U F F
P P
U U
MPUA fans
PSUC MPUB power

supply
Power supply
fans
MCC C SC SS SSCSC SC S
MCC P I P I UL I PI P I C I
USSU CU CP S CU CU CS C
77- D- D X - D- D7 D
S 8M 8 B8B 8 8
E VP V I VI V V MPUB shelf
U F F
P P
U U
MPUB fans
Ethernet
shelf
Figure 12: BSC 12000 Control cabinet board layout

PE/BSC/DD/0317 04.01/EN 16/01/04
P P
S S
U U
E E
P
EQPD1 shelf
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
S
U
E
P P
S S
U U
E E
EQPD0 shelf
P
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
DDTI
S
U
E
P P
S S
U U
E E
EQPI shelf
P
TSCB
TSCB
RCB
RCB
RCB
RCB
RCB
RCB
RCB
RCB
RCB
RCB
ALA
S
U
E
3 front-facing fans
P P
S S
U U
E E
P P
SWG shelf
MSW
MSW
MSW
MSW
SWE
SWE
SWC
SWE
SWE
SWC
S S
ECI
ECI
U U
E E
P P
S S
U U
E E
EQPT shelf
P
BSCB
BSCB
BSCB
BSCB
BSCB
BSCB
BSCB
BSCB
BSCB
BSCB
BSCB
BSCB
S
U
E
3 front-facing fans
Filling plate
Figure 13: BSC 12000 Equipment cabinet board layout

PE/BSC/DD/0317 04.01/EN 16/01/04
7.1.2. V10 HARDWARE
7.1.2.1. Control Cabinet
The control cabinet has two identical shelves. The boards for one MPU
processing shelf according to the 1201 to 1205 configurations are as follows:
Board 1201 1202 1203 1204 1205
CPU-OMU 1 1 1 1 1
CPU-MPU 1 1 1 1 1
CPU-BIFP 1 1 2 2 2
SICX 1 1 1 1 1
SICD8V 1 2 3 4 5
CCS7 1 2 2 2 3
SUP 1 1 1 1 1
MMU 1 1 1 1 1
SLS 1 1 1 1 1
z CPUM (CPU-OMU) management unit
Processor: Intel 486 DX2 66MHz internal clock

Clock frequency (MHz): 66
RAM: 16 Mb
ROM: 1 Mb
Functions:
- Ensures the supervision and the defense of the BSC and the Transcoding
units (TCUs).
- Manages the communication with the OMC-R.
- Controls the BSC hard disk (built-in controller).

PE/BSC/DD/0317 04.01/EN 16/01/04
z CPUE (CPU-MPU and CPU-BIFP) central management unit
Processor: Intel Pentium 120 or 133 (from Jan 00)

Clock frequency (MHz): 120 or 133
RAM: 16 Mb or 32 Mb for BSC 12000HC
ROM (flash): 1 Mb
Functions:
MPU:
- Manages calls and BSC operations
- Handles the messaging with the MSC
BIFP:
- Traffic Management (TMG) for the radio connections
- Manages radio channels and connections with the BTS
- Takes care of the BTS supervision
- Handles the messaging with the BTSs
Other information: A high speed bus connects the CPUE processing unit to
other boards of the processing core.
z Supervisor unit (SUP)
Processor: Intel 80C188

RAM: 512 Kb
ROM: 512 Kb
Functions:
- Manages the inter-processing chain link, also called the inter MPU link.
- Monitors its mate chain so as to detect malfunctions and designate an
active chain.
- Transfers inter-chain data
Other information: The SUP also manages a serial link controlling the
switching unit provisioning the switching unit with connection commands.
z The Mass Memory Unit (MMU)
Disk types and capacities:

- SCSI-2
- variable capacity according to the software release
Functions: Stores all BSC operating parameters, it accommodates:
- BSC and BTS software
- the BSC application data base (BDA) that contains BSC and BTS
configuration data
- temporary files to be sent to the OMC-R (observation data files, radio
measurement data files, system message files, ...)

PE/BSC/DD/0317 04.01/EN 16/01/04
z The Serial Link Switch (SLS)
Functions: Switches the V28 link from the SICX board onto two outgoing
OMC-R links. In normal conditions, one link supports all the communications
with the OMC-R, while the other one is idle.
z X25 interface controller (SICX)
Processor: Intel 386SX

RAM: 4 Mb
ROM: 512 Kb
Functions: It controls four links running the X25 protocol (two V28 and two
V11 links)
- A V28 link at 19.2 kbps connects the SICX board to the OMC-R via the
serial link switch (SLS).
- The SLS board manages link redundancy in the event of breakdown.
z LAPD interface controller (SICD8V)
Processor: Intel Pentium 75

RAM: 16Mb
ROM (flash): 1 Mb
Functions: The SICD8V boards handle messages issued by both the BTS
and the MS
- Receive messages and run the LAPD protocol
- Handle the signaling messages between the BTS and the BSC
- Send and receive protocol messages matching LAPD protocol standards
- Transfer message to/from user applications
z CCITT SS7 interface controller (CCS7)

RAM: 256 Kb
ROM: 256 Kb
Functions: The CCS7 board runs the CCITT SS7 level-2 layer signaling
protocol. The CPU-MPU unit runs the remaining layers.
Other information: The set of V11 board links works on load sharing
arrangements. If any link fails, the other links of the linkset handle the entire
signaling load.

PE/BSC/DD/0317 04.01/EN 16/01/04
7.1.2.2. Equipment Cabinet
The equipment cabinet has five shelves, from which two are identical and one
optional is reserved for enhancements of the BSC 12000 connectivity.
Board 1201 1202 1203 1204 1205
SWC 2 2 2 2 2
MSW 4 4 4 4 4
SWE 4 4 4 4 4
ECI 2 2 2 2 2
RCB 2 4 6 8 10
TSCB 2 2 2 2 2
ALA 1 1 1 1 1
DDTI 10-24 10-24 10-24 10-24 10-24
BSCB 0-4 0-6 0-9 0-12 0-12
7.1.2.2.1. Switching Shelf (SWG)
The switching matrix is duplicated. Each of the two chains has the following
boards:
Type of board Number of boards

SWC 1
MSW 2
SWE 2
ECI 1
Total: 6

PE/BSC/DD/0317 04.01/EN 16/01/04
The BSC 12000 has a 64 PCM x 64 PCM non blocking switching matrix that
can switch at 64 kbps for the signaling linkset 16 kbps for GSM full rate and
enhanced full rate.
z Switching module control board (SWC)
Processor: Intel 386 SX

RAM: 1 Mb
ROM: 1 Mb
Functions: The Control board SWC reads and writes to the switching matrix
boards (MSW-SWE) via a synchronous bus.
z Switching Matrix (MSW-SWE)
Functions: The MSW runs several basic switching functions and controls 16
links directly.
Other information:
- The master and extension (MSW-SWE) boards form the BSC switching
matrix support 32 PCM links
- The SWE is an extension board (slave) controlling 16 PCM links
- Eight time slots are extracted by the matrix and serve as 64 kbps V11 links.
Six of them are used to carry CCITT SS7 signaling to the CCS7 board. One
is used to carry the X25 link to the SICX board when the OMC-R is
connected to the BSC through the A interface. The last one is unused.
z Equipment Cabinet Interface Unit (ECI)

RAM: 256 Kb
ROM: 256 Kb
Functions: The ECI board monitors equipment units and feeds back
information to the MPU via the SICX board. The ECI monitors the following:
- the processor driven DDTI and ALA boards
- the RCB boards, power supply and cooling circuit converters by controlling
alarm loops for failure detection purposes
The ECI board can handle up to 24 alarm loops.
Other information:
A supervisor circuit tests the signals received from four external PCM links
(via DDTI boards) and selects a clock to control the local oscillator.

PE/BSC/DD/0317 04.01/EN 16/01/04
7.1.2.2.2. Mixed Shelf (EQPI)
The mixed shelf contains the following boards:
Type of board Number of boards

RCB 10 *
TSCB 2
ALA 1
Total: 13
* depends on the type of the BSC (twice the number of SICD8V)
z Rate converter boards (RCB)
Functions: The RCBs convert signals to and from the main switching board
(SWM)
Other information: An RCB board supplies eight 64 kbps time slots
whereas the SWM board delivers 2 Mbps signals from internal PCM links.
The time slots serve as 64 kbps V11 links for one related SICD8V board.
z Transcoding Signaling Concentration board (TSCB)
Processor: Intel 80186

RAM: 256 Kb
ROM: 256 Kb
Functions: The TSCB concentrates LAPD signaling coming from the
Transcoding Unit (TCU) before going to the SICD8V boards via an RCB
board.

PE/BSC/DD/0317 04.01/EN 16/01/04
z Alarm regrouping board (ALA)
Controller: Motorola 68HC11

RAM: 16 Kb
ROM: 40 Kb
Functions: ALA board monitors alarm loops and manages control loops.
The ALA board accommodates
- 24 internal alarm detectors (unused)
- 8 internal power converters (unused)
- 8 external alarm operator-controlled detectors, coupled with a circuit
ensuring high-level protection against overloads
- 4 external relay controls (buzzer, lamps, etc.), coupled with a circuit
ensuring high-level protection against overloads
7.1.2.2.3. PCM Shelves (EQPD)
Two shelves with twelve DDTI boards each are necessary for a fully equipped
BSC 12000 to interconnect with the BTSs and the Transcoding Unit. These 24
DDTI boards allow to connect up to 48 E1 or T1 PCM links to the BSC.
z Dual Digital Trunk Interface (DDTI)
Controller: Motorola 68HC11

RAM: 16 Kb
ROM: 40 Kb
Functions: The DDTI boards are in charge of the following operations:
- convert external E1 HDB3 PCM format or T1 B8ZS PCM format (Abis and
Ater interfaces) into the internal NRZ-binary format
- manage PCM alarms in full compliance with CCITT specifications. The use
of the CRC4/6 codes for transmission error detection is optional.
- match 75 or 120 Ω impedance for E1 and 100 Ω for T1 PCMs
Other information: One DDTI board manages two external PCM links.

PE/BSC/DD/0317 04.01/EN 16/01/04
7.1.2.2.4. BSCB Shelf (EQPT)
This shelf is used for extending the maximum number of connected sites from
39 to 138. It can contain up to twelve boards (BSC 1205).
z BTS Signaling Concentration Board (BSCB)
Processor: Intel 80186

RAM: 256 Kb
ROM: 256 Kb
Functions: concentrates LAPD signaling coming from low capacity BTSs
before going to the SICD8V boards via the RCB boards.
Other information: The software is able to manage a N+1 redundancy. All
the dimensioning of BSCB boards is done using this facility. If one of the
BSCB boards fails, the signaling traffic is automatically reconfigured on the
standby one.
7.1.2.3. MTBF
The MTBF (Mean Time Between Failures) of the BSC has been determined from a
"state-space" system reliability modeling using a Markov probability model. The
reliability prediction method used for the individual hardware component of the BSC is
the RDF93 model from the CNET (French Telecommunication institute).
The MTBF given below takes into account the equipment redundancy within the BSC.
It is assumed that the PCM links to the BTS are not redundant. The MTTR (Mean Time
To Repair) is assumed to be 1 hour.
MTBF BSC 12000 = 56100 hours
Downtime = 9 minutes / year

PE/BSC/DD/0317 04.01/EN 16/01/04
7.1.3. V11 NEW HARDWARE
7.1.3.1. Control Cabinet
The control cabinet has two identical shelves. The boards for one MPU
processing shelf according to the 1201 to 1205 configurations are as follows:
Board 1201 1202 1203 1204 1205

CPU-OMU 1 1 1 1 1
CPU-MPU 1 1 1 1 1
CPU-BIFP 1 1 2 2 2
SICX 1 1 1 1 1
SICD8V 1 2 3 4 5
CCS7 1 2 2 2 3
SUP 1 1 1 1 1
MMU 1 1 1 1 1
SLS 1 1 1 1 1
z CPUM (CPU-OMU) management unit (CPU133IE)

RAM: 32 Mb
ROM: 1 Mb
Functions:
- Ensures the supervision and the defense of the BSC and the Transcoding
units (TCUs)
- Manages the communication with the OMC-R
- Controls the BSC IDE hard disk (built-in controller)
- Controls the Ethernet link

PE/BSC/DD/0317 04.01/EN 16/01/04
z CPUE (CPU-MPU and CPU-BIFP) central management unit (CPU133)

RAM: 32 Mb
ROM (flash): 1 Mb
Functions:
MPU:
- Manages calls and BSC operations
- Handles the messaging with the MSC
BIFP:
- Traffic Management (TMG) for the radio connections
- Manages radio channels and connections with the BTS
- Takes care of the BTS supervision
- Handles the messaging with the BTSs
Other information: A high speed bus connects the CPUE processing unit to
other boards in the processing core.
z Supervisor unit (SUP2)
Processor: Intel 80C186XL

RAM: 512 Kb
ROM: 512 Kb
Functions:
- Manages the inter-processing chain link, also called the inter MPU link.
- Monitors its mate chain so as to detect malfunctions and designate an
active chain
- Transfers inter-chain data
Other information: The SUP also manages a serial link controlling the
switching unit provisioning the switching unit with connection commands.
A debug link is available on the front panel.
No battery for time storage backup in case of power shutdown

PE/BSC/DD/0317 04.01/EN 16/01/04
z The Mass Memory Unit (MMU-IDE)
Disk types and capacities:

- IDE
- variable capacity according to the software release
Functions: The MMU stores all BSC operating parameters, and
accommodates:
- BSC and BTS software
- the BSC application data base (BDA) that contains BSC and BTS
configuration data
- the temporary files to be sent to the OMC-R (observation data files, radio
measurement data files, system message files, ...)
z The Serial Link Switch (SLS2)
Functions: The SLS2 witches the V28 link from the SICX board onto two
outgoing OMC-R links. In normal conditions, one link supports all the
communications with the OMC-R, while the other one is idle.
An internal loopback of the OMC-R link is available.
z X25 interface controller (SICX)

Identical to V10 one
z LAPD interface controller (SICD8V)
z CCITT SS7 interface controller (CCS7)
7.1.3.2. Equipment Cabinet

Identical to the V10 one
7.1.3.3. MTBF
The MTBF (Mean Time Between Failures) of the BSC has been determined from a
"state-space" system reliability modeling using a Markov probability model. The
reliability prediction method used for the individual hardware component of the BSC is
the RDF93 model from the CNET (French Telecommunication institute).
The MTBF given below takes into account the equipment redundancy within the BSC.
It is assumed that the PCM links to the BTS are not redundant. The MTTR (Mean Time
To Repair) is assumed to be 1 hour.
MTBF BSC 12000 = 56100 hours
Downtime = 9 minutes / year

PE/BSC/DD/0317 04.01/EN 16/01/04
7.2. SOFTWARE DESCRIPTION
7.2.1. OMC ACCESS (AOMC)
The AOMC function of the BSC 12000 handles the OMC-R link and access protocol
including the following elements:
- unsolicited messages management
- OSI layer management
- File Transfer Management
- FTAM function management
7.2.2. ADMINISTRATION (ADM)

The administration function of the BSC 12000 manages the data related to application
objects, the database stored on the disk and the transactions between the OMC-R and
the BSC.
7.2.3. BSC OBSERVATION (OBS)

The BSC observation function collects all the information issued by the system entities
and forwards them to the OMC-R.
7.2.4. RADIO OBSERVATION (OBR)

The BSC radio observation function builds the database from raw and average
measurements. The observation result are transferred to the OMC-R using file transfer
facilities.
7.2.5. TRAFFIC MANAGEMENT (TMG)

The Traffic Management (TMG) function of the BSC 12000 establishes the links
between the MSs and the MSC. Each logical link comprising one radio resource (RR)
and one SS7 connection the TMG uses a radio resource and a terrestrial circuit
allocator. Once the logical links are established transparent DTAP (Direct Transfer
Application Part) messages can be transferred between the MS and the MSC.
7.2.6. SS7 PROTOCOL MANAGEMENT (SS7)

The SS7 protocol management facility handles the following items:
- handles the SS7 protocol (MTP1, MTP2, MTP3, SCCP)
- distributes incoming messages to user entities
- shares the signaling load over the links of the combined linkset that connects the BSC
and the MSC
- handles the SS7 configuration
7.2.7. LAPD PROTOCOL MANAGEMENT

The LAPD protocol management facility for TCU or RADIO Sites supervision handles
the following items:

PE/BSC/DD/0317 04.01/EN 16/01/04
- handles the LAPD protocol (Layer 2 and HDLC access)
- distributes incoming messages to user entities
- enables BTS and TCU link access
- handles LAPD configuration, supervision and observation
7.2.8. SUPERVISION (SUP)

The Supervision function's (SUP) main role is to supply the other BSC functions with
the necessary resources. It is therefore responsible for the initialization, the availability
and the supervision of the various resources. The SUP function covers the supervision
of the BSC, the BTS sites with the radio resources and the PCM links.
In case of failure, the SUP function will send an indication to the OMC-R and will
automatically and autonomously trigger defense mechanisms that will focus on
keeping the maximum possible resources available.
The design of the BSC 12000 allows the system to keep on running even in case of a
connection failure between the OMC-R and the BSC. A queuing mechanism allows the
OMC-R to recover any information sent by the BSC during the link failure.
7.3. DUPLEX MODE

7.3.1. INTRODUCTION
In the duplex operating mode, the software and data are loaded onto both
processing chains. The active processor chain directs the BSC activities and
the passive processor chain is updated by the active one.
Furthermore, the hard disks of the two BSC processing chains are mirrored.

PE/BSC/DD/0317 04.01/EN 16/01/04
OMC
2 x V24/V28 2 x V24/V28
MMU SLS SLS MMU

MPU A MPU B
Ethernet link
Panel Panel
CPU- CPU- CPU-
CPU- SUP
MPU/ SUP MPU/ OMU
OMU
BIFP BIFP
MTBII MTBII
SICX CCS7 SICD SICD CCS7 SICX
64 kbps
64 kbps 64 kbps
V11 64 kbps
64 kbps V11 V11
V11 64 kbps
V11 V11
ECI A ECI B
RCB A RCB B
Switching Switching
Matrix SYNC. SYNC. Matrix
A B
PCM Bus
2 Mbps
V11
PCM Bus
2 Mbps
V11
MPU Status MPU Status
TSCB ALA DDTI

BSCB
O&M Bus
9600 bps
RS 485
External Loops G.703 PCM
Figure 14: Duplex Architecture of the BSC 12000
7.3.2. DUPLEX OPERATIONS

In the duplex operating mode, the software and data are loaded onto both processing
chains. Only the “active side” directs the BSC activity:
- Traffic management
- Communication with the BTS
- Communication with the OMC-R

PE/BSC/DD/0317 04.01/EN 16/01/04
The passive processor chain is updated by the active one each time a call reaches or
leaves a stable state. Stable calls are recovered when there is a failure on the active
processor chain, and the passive processor chain turns active. The hard disks of the
two BSC processing chains are mirrored, the various load counters are updated onto
both chains, and the supervision information of the equipment are transferred to the
passive chain at each equipment status change.
The design of the BSC 12000 allows the system to keep on running even in case of a
connection failure between the OMC-R and the BSC. A queuing mechanism allows the
OMC-R to recover any information sent by the BSC during the link failure.
7.3.3. STANDBY CHAIN OPERATION

The standby chain performs the operations needed to ensure the lowest impact on
traffic handling in case of switchover:
- maintaining active/standby data integrity on its disk
- running test to detect standby components faults
- sending its operational status to the active chain to determine which of the two
chains is in the best working condition
Moreover, the standby Traffic Management unit receives from the active chain all the
information needed to sustain calls in case of switchover (radio channel information,
terrestrial and SCCP circuit used, ...)
Besides, the standby Supervision unit receives the radio configuration information from
the active chain at start up time and when it is configured.
It should be noted that the BTS dialogue is unaffected in case of switchover.
7.3.4. DATA PROTECTION

An audit is performed upon operator request on both chains to ensure disk data
integrity. The audit is performed on the active chain and the data consistency on the
passive chain is ensured by the mirror mechanism.
7.3.5. MIRRORING
The mirroring mechanism is performed at the applicative layer level. The data are
written on both chains and not copied from one chain to the other.
7.3.6. SWITCHOVER CONDITIONS

A switchover is performed in case of major H/W or S/W anomaly. The switchover
condition is detected by the supervision entity and initiated by the SUP board after
comparison with the other chain.
7.4. OVERLOAD PROTECTION

The BSC is a core processing and switching element in the BSS network. As such, it is
essential to ensure the BSC robustness and stability in order to maintain a good level
of service quality.

PE/BSC/DD/0317 04.01/EN 16/01/04
Nortel Networks GSM BSC robustness is ensured by a global and optimal overload
control mechanism. This new mecanism is introduced in BSS release V12 and
replaces the previous mechanism that was based on a local overload control on the
main BSC processors.
7.4.1. GENERAL DESCRIPTION

The overload control mechanism is global in the sense that all main processing
boards and all critical resources (CPU, memory, timers, buffers) of those boards are
monitored. Each board computes every second its “synthetic” load, which is the result
of a combination of CPU load, memory occupancy and other resources. In this
computation, the variation trend in the past 3 seconds is taken into account, for
anticipation purpose. According to the value of this “synthetic” load, each board
reports to the OMU board (which is the master board for overload control) its overload
level, if the latter has changed from previous situation. The load information is
centralized in the OMU board, that controls globally the load state of each processor of
the BSC and triggers the appropriate actions in order to maintain an acceptable level
of load.
Figure : The OMU collects, computes and distributes load information
MPU
OMU
BIFPs
OMU-SUP-SWC OMU
SICDs
The mechanism is optimal because it is based on real-time processor load, modulated

with the variation of the past 3 seconds. The processing of a request is started only if
all involved boards can process it. Hence, in overload conditions, the BSC avoids
unnecessary processing. When communications need to be filtered to reduce the load
of the BSC, it is done only in the cells that induce the load. In any case, all established
communications are maintained. Only new traffic requests are filtered.
Counters giving the processor synthetic loads and the number of filtered operations by
type are provided. Those counters give the operator a detailed view of the filtered

PE/BSC/DD/0317 04.01/EN 16/01/04
traffic and processor loads during overload conditions, allowing him to plan the BSC
capacity evolution in its network.
With this global and optimized overload control, Nortel Networks GSM BSC can cope
with overload situations, ensuring both the robustness of the equipment and a
nominal level of carried traffic. The BSC remains stable in very high levels of traffic.
All established communications are maintained. By filtering new traffic requests that
the BSC cannot satisfy because of lack of resources, it protects itself against loss of
messages and thus dropped calls.
7.4.2. MONITORED BOARDS

The BSC is made up of some processing boards and some connectivity & switching
boards. The boards that are impacted by high peaks of traffic are all monitored in order
to prevent overload and instable situations. Those boards are :
• OMU : board performing the OA&M tasks in the BSC. It manages also the
switching connections for GSM traffic together with the SUP board.
• BIFP : board managing the GSM traffic towards the BTS
• MPU : board managing the GSM traffic towards the MSC
• SICD : manages the LAPD protocol and signalling
The boards that ensures the connectivity & switching (CCS7, BSCB, TSCB, DDTI,
SWC… ) shall not reach their limit because of GSM traffic variations. They are
dimensioned according to the maximum connectivity they have to provide and won’t
reach overload state. So they are not included in the global overload control
mechanism.
7.4.3. OVERLOAD THRESHOLDS AND TRAFFIC FILTERING

The overload threshold are determined by the “ processorLoadSupConf” parameter, as
in the old mechanism. However, since the new mechanism is based on real processor
values, it is in most extent independant of the type of processor. So only one nominal
value will be used for this parameter. To the value of this parameter is associated the
sets of overload thresholds for each monitored processing board. The platform tests
have shown that this nominal value ensures the robustness of the BSC in all simulated
traffic patterns. There are other possible values for the “ processorLoadSupConf”
parameter that are reserved for future possible use, for eg. in case where some
unexpected traffic pattern and BSC behaviour occurs in real networks.
Three overload levels are defined in the BSC. Each level corresponds to the load level
of the BSC processors. According to the overload level , some amount of new traffic
requests are filtered :
• overLoad level 1 (80% of processor load) : traffic reduction around 33% by filtering 1
request out of 3 of the following messages:
- Paging Request,

PE/BSC/DD/0317 04.01/EN 16/01/04
- Channel Request with cause different from “Emergency call”,
- All First Layer 3 messages with cause different from “Emergency call” ,
- HandOver for traffic reason,
- HandOver for O&M reason,
- directed retry.
• overLoad level 2 (90% of processor load): traffic reduction around 66% by filtering 2
requests out of 3 of the above messages.
• overLoad level 3 (100% of processor load): no new traffic is accepted by filtering all
previous and following messages :
- All First Layer 3 messages,
- All Channel Request (including causefor “Emergency Call”),
- All Handover Indication,
- All Handover Request.
7.4.4. OA&M LOAD CONTROL ON OMU

Since the OMU board performs many OA&M tasks (fault events processing,
observation/call traces, mirroring/duplex management, BTS downloading) in addition to
handling GSM switching connections messages, GSM traffic message filtering may not
be enough to keep the OMU load at an acceptable level. In OMU overload conditions,
a flow control on the BTS fault events notifications is implemented, since this task is
the most impacting on OMU (the fault events flow can be very bursty and can reach
high peak). At level 2 OMU overload, all BTS events without service impact will be
filtered. At level 3 OMU overload, all BTS events including those with service impact,
will be filtered. However the BTS will resend those events, since the BSC did not
acknowledge them. The BSC will take them into account when the OMU load
decreases.
This feature is available from V12.4 release.
7.4.5. OBSERVATION COUNTERS AND OVERLOAD NOTIFICATION

Counters giving the processor synthetic loads and the number of filtered operations by
type are provided. Those counters give the operator a detailed view of the filtered
traffic and processor load during overload conditions :
- Number of rejected paging requests
- Number of rejected First Layer 3 messages
- Number of rejected Channel Request
- Number of rejected Handover Indication
- Number of rejected Handover Request
- Average and maximum processor synthetic load

PE/BSC/DD/0317 04.01/EN 16/01/04
Those information allows the operator to plan the BSC capacity evolution in its
network.
When the BSC is in overload situation, an alarm notification is sent to the operator on
the OMC-R. The end of overload situation is also notified.
7.5. UPGRADE
7.5.1. UPGRADE OF SOFTWARE VERSION
The software version is upgraded without change of the BSC architecture either by
downloading the new software from the OMC-R or by replacing the disks with new
master disks. Then, on-line BDA building is required. At the end of the BDA building,
each BTS controlled by the BSC is re-initialized without BTS software downloading.
This implies a short interruption of service of 2 to 3 minutes depending on the number
of connected BTSs.
7.5.2. UPGRADE OF A BSC 6000 INTO A BSC 12000 OR BSC 12000HC

The BSC software must be upgraded first to V11 or V12.
Thus, the two chains must be separated and the passive chain (Chain B) hardware
must be upgraded:
∗ SICD boards are replaced with SICD8V boards.
∗ CCS7 boards are added (if applicable).
∗ CPU66 boards are replaced with CPU120 boards or CPU133 (if applicable).
Note: If the BSC6000 is already equipped with CPU120, these boards can be
kept or replaced by CPU133 – see the detail below in §7.5.3.
∗ Installation of HC100 kit if upgrade to BSC 12000HC (see §7.5.3)
∗ Some boards positions must be modified.
The BSC software must be updated.
The BSC architecture must be updated too with TML.
A BDA build must be done on the passive chain.
A chain switchover needs then to be performed.
Chain B becomes the active chain.
Chain A hardware is then upgraded (see above for chain B).
This operation requires a quite long duplex break and a short service interruption of 2
to 3 minutes depending on the number of connected BTSs.
7.5.3. UPGRADE OF A BSC 12000 TO A BSC 12000HC

The BSC software must be first upgraded to V11.

PE/BSC/DD/0317 04.01/EN 16/01/04
Thus, the two chains must be separated and the passive chain (Chain B) hardware
must be upgraded:
∗ CPU-OMU board must be replaced with CPU133IE board.
∗ MMU board must be replaced with MMU-IDE board.
∗ SUP board must be replaced with SUP2 board.
∗ SLS board must be replaced with SLS2 board.
∗ Option: CPU120 can be replaced by CPU133 in order to get the latest and most
powerful processor in the BSC. The CPU133 for BSC12000HC provides 10 to
20% more capacity for tough traffic profiles compared to CPU120. If the CPU120
are kept then the RAM of these boards must be extended from 16 Mb to 32 Mb.
The BSC software must be updated.
The BSC architecture must be updated too with TML.
A BDA build must be done on the passive chain.
A chain switchover needs then to be performed.
Chain B becomes the active chain.
Chain A hardware is then upgraded (see above for chain B).
This operation requires a quite long duplex break and a short service interruption of 2
to 3 minutes depending on the number of connected BTS.
7.5.4. UPGRADE FROM ONE TYPE TO ANOTHER

First, the BSC must be equipped with the required additional hardware for the
new type:
- BIFP (from type 1 or 2 to type 3, 4 or 5)
- SICD8V and RCB
- CCS7 ( from type 1 to type 2, 3, 4 or 5 and
from type 2, 3 or 4 to type 5 )
- DDTI boards (if required)
This operation is done first in the passive chain (power off) and then in the active chain
(power off). It entails a short duplex break and a chain switchover.
In a second step, the change of the BSC type (via TML) requires a BDA building, that
can be done on-line. At the end of the BDA building, each BTS controlled by the BSC
is re-initialized without BTS software downloading. This implies a short interruption of
service.
7.5.5. UPGRADE WITH BSCB BOARDS

The BSCB boards (and the power supply units, if not already there) can be
added in the EQPT shelf. Then, the number of BSCB boards must be updated
in the BDA. This requires a BDA building, that can be done on-line. At the end
of the BDA building, each BTS controlled by the BSC is re-initialized without

PE/BSC/DD/0317 04.01/EN 16/01/04
BTS software downloading. This implies a short interruption of service of a few
minutes.
7.6. INTERFACES
BTS BSC TCU MSC
Ater A
Abis
Figure 15: Interface Overview
7.6.1. PHYSICAL INTERFACE

The BSC 12000 can support both E1 HDB3 format (75 or 120 Ω) and T1 B8ZS format
(100 Ω) PCMs according to the ITU-T white book recommendations (G703 and G823).
The BSC 12000 synchronizes itself on four Ater PCMs. The recommended accuracy
is:
• 2,048 MHz ± 10-9
• 1,544 MHz ± 10-9
7.6.2. ABIS INTERFACE

The Abis interface links the BTSs to the BSC that manages them. Traffic is
carried over E1 or T1 PCM links divided into 32 (E1) or 24 (T1) time slots, each
carrying 64 kbps. Some time slots are set aside for signaling purposes while
others convey speech and data traffic.
7.6.2.1. Configurations
The following standard configurations are possible on the interface between

the BSC 12000 and the BTSs:
• Star configuration
• Chain configuration
• Loop configuration

PE/BSC/DD/0317 04.01/EN 16/01/04
BTS
BTS BSC BTS BTS BTS
BTS Loop
BTS
Star BTS
PCM
Chain BTS Redundant PCM (optional)
Figure 16: Abis Configurations
7.6.2.2. Signaling
Two types of signaling are transported over the Abis interface; the signaling
related to the Operation and Maintenance and the signaling related to the
Traffic Management.
One 64 kbps LAPD Abis link can support the signaling of 8 TRXs using the TEI
of the LAPD protocol for Layer 2 addressing.
7.6.2.3. Traffic
On the Abis interface both speech and data traffic are carried at 8/16 kbps
following the format specified in the GSM recommendation 08.60.
7.6.2.4. Dimensioning
On the Abis interface two time slots per TRX must be reserved for the traffic
data and one 64 kbps LAPD time slot per 8 TRXs for signaling. Redundancy
can be used by adding PCM links.
7.6.2.5. Fault Protection

In case of layer 1 or 2 fault, all the LAPD and traffic channels will be mapped onto the
redundant PCM if available. The radio site will thus come back to its initial operation
mode.
In case of a layer 3 communication loss, the BSC notifies the operator, isolates the
concerned entities and tries to re-establish the layer 3 communication.

PE/BSC/DD/0317 04.01/EN 16/01/04
7.6.3. ATER INTERFACE
7.6.3.1. Configurations
TCU
BSC A-ter A MSC
TCU
figure 17: PCM links on the Ater and A interfaces
One Transcoding Unit (TCU) has one Ater interface PCM and four A interface
PCMs.
7.6.3.2. Signaling
Three types of signaling can be transported on the Ater interface; the LAPD
signaling for the control of the transcoders by the BSC, the SS7 signaling going
to the MSC and the X25 signaling going to the OMC-R (optional). The signaling
traffic is carried on 64 kbps PCM time slots.
7.6.3.3. Traffic
On the Ater interface both speech and data traffic are carried at a rate of
16 kbps following the format specified in the GSM 08.60 recommendation.
7.6.3.4. Dimensioning
It is considered that the load of one SS7 time slot should not exceed 40% of its
capacity in nominal working conditions (each link of the linkset is working). With
this figure, one SS7 interface PCM time slot can support the signaling for
approximately 200/250E of traffic. This gives six SS7 time slots for a fully
equipped BSC 12000 with an N+1 redundancy. Note that each SS7 time slot
should be on a different PCM.
One LAPD TCU signaling time slot is needed on each Ater PCM.
The number of Ater PCM links and thus the number of TCU shelves depends
on the maximum capacity of the BSC and the accepted blocking rate. For a
1200 erlang BSC with a maximum blocking rate of 0.1 %, we obtain 11 + 1 Ater
E1 PCMs or 13 + 1 T1 PCMs. The redundant PCM is used in load sharing
mode, which means that under normal conditions the links are all under
loaded.

PE/BSC/DD/0317 04.01/EN 16/01/04
For synchronization reasons a minimum of four PCMs have to be dedicated to
the Ater interface.
7.6.3.5. Fault Protection

In case of PCM fault, the BSC clears the LAPD connections of the lost PCM and all the
communications established on the faulty PCM. Furthermore, the associated A
interface resources will be set as unavailable. If a LAPD failure occurs, the BSC will try
to re-establish the layer 2 connection with the TCU. If the link is re-established and the
TCU has not reset itself, the BSC will check the TCU configuration before setting the
TCU resource as being available.
7.6.4. BSC-OMC INTERFACE
The BSC 12000 can be connected to the Radio Operation and Maintenance
Center (OMC-R) through an X25 packet data network (1) or through the A
interface (2).
To OMC-R Servers
RS 449 (48 kbps)
Black Box
V35
1 X25 Modem
To OMC- R Servers
X.25 Network V35 (48 kbps)
2
X25 Modem X.25
V24/V28 Switch
(19.2 kbps)
G703
BSC TCU
MSC
BSC TCU
Figure 18: BSC 12000 Connection to the OMC-R
An X25 packet switch with multiple PCM and RS 449 ports must be used when
connecting the BSC to the OMC-R via the A interface. For both types of
connections the X25 connection with the OMC-R is duplicated for redundancy.

PE/BSC/DD/0317 04.01/EN 16/01/04
8. APPENDIX
8.1. REFERENCES
BSC/TCU engineering information IRC/APP/0015

BSC 6000 site specifications PE/ICM/DD/004
BSC I&C general specification PE/ICM/DD/0003
BSC 2G reference manual PE/DCL/DD/0022
8.2. ABBREVIATIONS
BDA Application DataBase

BIFP Base Interface Front-end Processor
BSC Base Station Controller
BSCB BTS Signaling Concentration Board
BSS Base Station SubSystem
BTS Base Transceiver Station
CIC Terrestrial Circuit Identification Code
CCS7 CCITT SS7 Interface Controller
CPU Central Processing Unit
DCS Digital Cellular System
DDTI Dual Digital Trunk Interface
ECI Equipment Cabinet Interface
EFR Enhanced Full Rate
GSM Global System for Mobile communications
HMI Human Machine Interface
H/W Hardware
LAPD Link Access Protocol on D channel
MPU Main Processing Unit
MS Mobile Station
MSC Mobile services Switching Center
O&M Operation and Maintenance
OMC-R Operation and Maintenance Center-Radio
OMU Operation and Maintenance Unit (in BSC)
NMC Nortel Matra Cellular
NSS Network Sub-System
PCM Pulse Code Modulation
PCS Personal Communication System

PE/BSC/DD/0317 04.01/EN 16/01/04
RCB Rate Converter Board
SCSI Small Computer System Interface
SUP SUPervision unit
S/W Software
SWM Master SWitching Matrix
TCB TransCoder Board
TCU TransCoder Unit
TDMA Time Division Multiple Access
TMG Traffic ManaGement
TML Local maintenance terminal
TRAU Transcoder/Rate Adapter Unit
TRC TeRrestrial Circuit
TRX BTS Transceiver entity
TS Time Slot
TSCB Transcoder Signaling Concentration Board
<End of DOCUMENT>

PE/BSC/DD/0317 04.01/EN 16/01/04

GSM/DCS/PCS: Reference: PE/BSC/DD/0317 Date

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

GSM/DCS/PCS: Reference: PE/BSC/DD/0317 Date

Hochgeladen von

Copyright:

Verfügbare Formate

GSM/DCS/PCS

BSC 12000 CUSTOMER PRODUCT OVERVIEW

2.2. Product Configurations .............................................................................................................................................. 7

3. GENERAL DESCRIPTION ............................................................................................................8

3.1. Functional Overview................................................................................................................................................... 8

3.2. Architecture ............................................................................................................................................................... 10

4. PHYSICAL LAYOUT ...................................................................................................................12

5. CAPACITY AND CONFIGURATION...........................................................................................14

5.1. Configurations ........................................................................................................................................................... 14

5.2. Options ....................................................................................................................................................................... 19

5.4. Shipping and Installation ......................................................................................................................................... 28

5.5. Physical Characteristics ........................................................................................................................................... 28

5.6. Floor Space ................................................................................................................................................................ 30

BSC 12000 Customer Product Overview Page 2

5.8. Protection ................................................................................................................................................................... 33

5.9. Environment .............................................................................................................................................................. 33

6. OPERATION & MAINTENANCE.................................................................................................35

6.1. Configuration Management..................................................................................................................................... 35

6.2. Performance Management....................................................................................................................................... 35

6.3. Fault Management .................................................................................................................................................... 37

6.4. Software Management.............................................................................................................................................. 37

6.5. Local Maintenance.................................................................................................................................................... 37

7.1. Hardware Description .............................................................................................................................................. 38

7.2. Software Description ................................................................................................................................................ 51

BSC 12000 Customer Product Overview Page 3

7.3. Duplex Mode.............................................................................................................................................................. 52

7.4. Overload Protection.................................................................................................................................................. 54

7.5. Upgrade ...................................................................................................................................................................... 58

8.1. References .................................................................................................................................................................. 64

8.2. Abbreviations ............................................................................................................................................................ 64

BSC 12000 Customer Product Overview Page 4

BSC 12000 Customer Product Overview Page 5

Figure 2: System Overview

BSC 12000 Customer Product Overview Page 6

2.2. PRODUCT CONFIGURATIONS

Figure 3: BSC 12000 configurations

BSC 12000 Customer Product Overview Page 7

3.1. FUNCTIONAL OVERVIEW

BSC 12000 Customer Product Overview Page 8

• AOMC Access to the OMC-R via the X25 network

• ADM Configuration and operational management of the radio

• OBS BSC observations - BSS performance management

• OBR Call monitoring and radio observations

• TMG Traffic Management - call handling procedures

• SS7 CCITT #7 protocol management - MSC access

• LAPD LAPD protocol management - BTS and TCU access

• SUP Supervision - defense and reconfiguration

Figure 4: BSC classes of functional units

BSC 12000 Customer Product Overview Page 9

ACTIVE CHAIN STANDBY CHAIN

OMC MSC BTS

Figure 5: Duplicated core structure

The software architecture can be tailored to fit into different hardware

• The Main Processing Unit (MPU)

• The Base Interface Front-end Processor (BIFP)

BSC 12000 Customer Product Overview Page 10

BSC 12000 Customer Product Overview Page 11

Matrix A Matrix B Power

Control Cabinet Equipment Cabinet

• CPU - MPU/BIFP central management units

• CPU - OMU central management unit

• Mass Memory unit (MMU)

• X25 interface controller (SICX)