BSC Basic Operations

Module 3

This chapter is designed to provide the student with the basic

abilities to operate a BSC.

OBJECTIVES:
Upon completion of this chapter the student will be able to:

• Understand the main function of a BSC.

• Recognize BSC specific data.

• Describe BSC specific hardware.

• Solve a Managed Object (MO) Fault upon alarm.

• Reconfigure MOs and BTSs using the OSS applications
Cellular Network Administration and BTS SW management.
• Load RBS software using BTS SW management in OSS.
GSM Operation Handling in MSC/BSC

Intentionally Blank

2 3-EN/LZM 112 318 R2A

 3 BSC Basic Operations

3 BSC Basic Operations

Table of Contents

Topic Page

12. BSC HANDLING 169

INTRODUCTION........................................................................................................ 169
CELL DATA................................................................................................................ 169
MANAGED OBJECTS ............................................................................................... 170
TRANSCODER AND RATE ADAPTER UNIT ........................................................... 172
TRANSCEIVER HANDLER ....................................................................................... 172
SUBRATE SWITCH ................................................................................................... 173

3-EN/LZM 112 318 R2A i

GSM Operation Handling in MSC/BSC

Intentionally Blank

ii 3-EN/LZM 112 318 R2A

 3 BSC Basic Operations

12. BSC HANDLING

INTRODUCTION
In the GSM network the AXE-based Base Station Controller
(BSC) controls and supervises a number of Radio Base Stations
(RBSs) and radio connections in the system. It handles the
administration of cell data, the locating algorithm, and orders
handovers.

The BSC manages the functions to set up, supervise and

disconnect circuit-switched and packet-switched connections.

A number of BSCs can be handled by one MSC. The connection

between the BSC and the MSC is the A-interface. The ETC
devices on the PCM link to the MSC are called RALT devices.
The connection between the BSC and an RBS is called the Abis-
Interface. The ETC devices in the BSC for the PCM link to the
RBS are called RBLT (RTS Abis- Interface Line Terminal). An
RBLT device is a 64 kbps channel containing max. 4 calls (Full
Rate, FR / Enhanced Full Rate, EFR) or 8 calls (Half Rate, HR).

In order to perform the tasks that the BSC is responsible for, the
administration of the Cell Data and Managed Objects (MOs) is
done in the BSC. The BSC is equipped with three types of
unique hardware: the Transcoder and Rate Adapter Unit
(TRAU), the Transceiver Handler (TRH) and the SubRate
Switch (SRS).

CELL DATA
For every cell in the network, cell data is defined in the BSC. In
the BSC cell data contains the name and the size of the cell, the
used frequencies and the transmitting power. Also information
about neighboring cells is available for handovers. Up to 200
parameters can be described for one cell.

The cell data can be divided into:

• Cell Definition data

A cell can be defined as an internal or external cell. Internal
means, that the cell is fully controlled by the own BSC. A
cell can be defined as an internal or external cell. Internal
means, that the cell is fully controlled by the BSC, where it
is defined as internal. Command: RLDEI.
• Cell Description Data

3-EN/LZM 112 318 R2A

GSM Operation Handling in MSC/BSC

In the Cell Description Data the details about the cell are
specified: the Cell Global Identity (CGI), which also
contains the Location Area Identity (LAI). The Location
Area Identity is important for locating the Mobile Station.
The Base Station Identity Code (BSIC) is used for
distinguishing between the different Base Stations with the
same carrier frequency, or to distinguish cells between
different operators or countries. Also the Radio Frequency
(RF) channel number is included in the cell description data
as an indication for the BCCH (Broadcast Control Channel).
Command used for the Cell Description Data: RLDEC.

• Subcell Definitions
If a cell is configured with at least two frequencies, it can be
split into two subcells - an overlaid subcell and an underlaid
subcell. More than one frequency can be assigned to a
subcell. Command: RLDSI.
• Configuration of frequency and power data
If more frequencies than the BCCHNO are added to the cell,
these frequencies should be defined separately. Command:
RLCFI. For transmitting power specifications: RLCPC.
• Locating Data
There are various commands to specify locating data.
Examples are the BSC and Cell Locating Data command
(RLLBC and RLLOC) for the specification of handover
decisions.

MANAGED OBJECTS
A Managed Object (MO) is a logical representation of a
hardware and/or software unit in the RBS. MOs are defined in
different classes. The Transceiver Group (TG) is normally equal
to one RBS. The Central Function (CF), Digital Path (DP),
Concentrator (CON), Interface Switch (IS) and Timing Function
(TF) are Managed Objects within one Transceiver Group.

The Transceiver Controller (TRX) is equal to one Transceiver

Unit (TRU, the transmitting and receiving hardware for one
carrier frequency). The Transmitter (TX) and Receiver (RX) are
common MOs within the TRX. Per TRX 8 Time Slots (TS) are
defined.

– 170 – 3-EN/LZM 112 318 R2A

 3 BSC Basic Operations

DP

CF TF

RX

TRXC
0 TX

TS
0 TS 8 TS
7
IS ( UP TO 16 TRXCs)

RX

TRXC
15 TX

TS
0 TS 8 TS
7
CON

Figure 2-12.1 Managed Object Block Diagram

Handle Managed Objects

If Managed Objects in more than one Transceiver Group are
defined, it is recommended that all Managed Objects are defined
in one TG before defining the Managed Objects in the next TG
(command RXMOI).

The TG Managed Object must always be defined first before

any of its subordinates.

The recommended order for defining the object classes is: TG,
CF, IS, CON, DP, TRXC, TF, TX, RX, and finally TS.

3-EN/LZM 112 318 R2A

GSM Operation Handling in MSC/BSC

It is recommended to use the same order for bringing the MOs

into service (command RXESI) and operation (command
RXBLE).

For deleting MOs use the opposite order.

TRANSCODER AND RATE ADAPTER UNIT

The Transcoder and Rate Adapter Unit (TRAU) is the hardware
of the transcoder devices. It is connected to the Group Switch
and is controlled by the Regional Processors (RPs).

The transcoding and rate adaption is performed by a set of

transcoder devices consisting of one Multiplexor (MUX) device
and 4*n Demultiplexor (DEMUX) devices. The DEMUX
devices are connected to the MSC and each can handle one
speech/data channel of 64 kbps. The MUX devices are
connected to the RBS and each can handle 4 speech/data
channels (FR/EFR) or 8 speech/data channels (HR).

Transcoder and Rate Adapter devices can be defined in a

transcoder pool. From a transcoder pool, transcoders are
initialized on a per call basis leading to better utilization of the
installed transcoder hardware.

TRANSCEIVER HANDLER
The main function of the Transceiver handler (TRH) is to
implement LAPD-signalling from the BSC to the RBS. It
processes signaling information and handles the measurement
data required to perform the handover function. The TRH is
connected to the Group Switch and is RP controlled.

– 172 – 3-EN/LZM 112 318 R2A

 3 BSC Basic Operations

BSC RBS
MSC
RALT RBLT
ETC ETC ETC
GS
ETC ETC ETC

TRAU

ST
S7-ST

TRH
SRS

RP RP RP RPD
RPD RP RP

CP-A SP-A

Figure 2-12.2. Connections of TRAU, TRH and SRS

SUBRATE SWITCH
In a former module the Group Switch was described. It switches
8000 times per second an 8-bit sample. Therefore it can switch
64 kbps channels only. On the Abis-Interface each connection
uses 16 kbps (FR/EFR) or 8 kbps (HR). The Subrate Switch
(SRS) makes it possible to switch 4 or 8 individual connections
within the physical 64 kbps Time Slots. This enables more
efficient usage of the Abis-interface.

3-EN/LZM 112 318 R2A

GSM Operation Handling in MSC/BSC

Intentionally Blank

– 174 – 3-EN/LZM 112 318 R2A