This is MO

1 Introduction
MO is a terminological which is fully named Managed Object and used in RBS/BTS area.
Then, what does MO mean exactly?

Strictly speaking, MO is introduced and mentioned firstly by a conception – BTS Logical

Model. There’re two versions of BTS Logical Model for Ericsson’s implementation, G01
and G12 where G01 is for RBS200, G12 is for RBS 2000. MO is a logical conception
based on functionality – oriented method. It is used for dividing RBS HW and SW into
different parts (MOs) with different functionality to simplify the operation and maintenance
of a RBS. All O&M related communication on the Abis interface is directed to MOs. In this
article, I’ll help you look into managed objects! The following contents are mainly based on
BTS Logical Model G12.

2 BTS Logical Model G12

2.1 Brief Introduction

Based on functionality – oriented method, a RBS is mainly divided into MOs such as TG,
CF, CON, IS, TF, DP, TRXC, TX, RX, TS. Then, what do they mean? Maybe you can
firstly learn something from their full name. See below.

1. TG: Transceiver Group

2. CF: Central Functions

3. CON: Concentrator

4. IS: Interface Switch

5. TF: Timing Function

6. DP: Digital Paths

7. TRXC: Transceiver Controllers

8. RX: Receivers

9. TX: Transmitters

10. TS: Time Slots

 Each one of them also stands for a MO class, See Figure 1.

Superior

Subordinate

Figure 1 MO class

2.2 Functionalities of Managed Objects

2.2.1 Categories of Managed Objects

2.2.1.1 Control Managed Objects

Control MOs also called Service Objects (SOs). An SO carries service functions
for a set of MO instances, including itself. The service functions include Layer 2
termination and Layer 3 distribution. They may further include SW loading,
forwarding of loaded SW to other MOs and supervision of Hardware (HW) and
Software (SW). The following MOs are SOs:

• Central Functions, CF
• Transceiver, TRXC

2.2.1.2 Traffic Managed Objects

Traffic MOs also called AOs (Application Objects).

An AO provides a part of the functionality in a base transceiver site. An AO instance has

O&M communication with a BSC on Layer 3, via a specific SO instance. The following
MOs are AOs:

• TX, Transmitter
• RX, Receiver
• TS, Timeslot
• IS, Interface Switch
• DP, Digital Path
• CON, Concentrator
• TF, Timing Function

2.2.2 Transceiver Group

Before TG, there’s a concept of BTS – Base Transceiver Station. A BTS is, by Global
System for Mobile Communication (GSM) definition, the base station equipment required
to support a cell. The implementation of BTS functionality in G12 Model is termed a
Transceiver Group (TG). However, a TG can support part of a cell, a single cell, or any
number of cells up to a maximum of 16.
A TG consists of a set of MOs and is a MO in itself. An MO is a logical representation of
one or more hardware units and their software at a base station site.

One or more TGs are connected to one or more cell via Channel Group (CHGR). The
relationship between TGs and cells is shown in Figure 2.
Cell Cell
…

CHG CHG CHG CHG

R … R R …
R
0 1 N 0

TG TG

Figure 2 The relationship between TG, CHGR and cell

Followings are the verbal descriptions of the relationship between TG, CHGR and cell.

1) A transceiver group is connected to one or many cells via one or many channel
groups.
2) Each cell may have many channel groups connected to it. A channel group shall
only be connected to one cell.
3) Each channel group shall only be connected to a single transceiver group.
4) A number of channel groups may be connected to a single transceiver group.

Maybe you are itching to ask me how a CHGR is connected to a cell. OK, the following
figure (Figure 3) can give you a visual and direct presentation.

CHG
R

BPC BPC … BPC

BCC SDCC TCH/ … TCH/

H H/4 F or F or
2xTC 2xTC
H/H H/H

Figure 3 The relationship between CHGR, BPC and LCH

• Two New Conceptions:

BPC: A BPC is one timeslot occurring on every TDMA frame. With frequency
hopping the frequency will change between every frame; without frequency
hopping it will not. A BPC may be used to carry different channel combinations.
 LCH: The logical channel(s) (LCH) are mapped from specific BPC according to the
TDM timing structure of GSM.

• General Limitations for Frequency Hopping:

The maximum number of frequencies per cell is 128. Note that the number of
frequencies per channel group is however limited to 32, thus limits the number of
frequencies to hop on per BPC to 32.

In addition, the MO TG cannot be communicated with over the Abis interface for operation
and maintenance. Thus, it cannot be tested, configured etc. However, if the MO TG is
allowed in a command, it may refer to all MOs within that TG. For example, program load
of a TG means program load of all MOs belonging to that TG.

In some models of RBS 2000 series, the TG can contain up to 12 TRXs (theoretically up to
16), 1 CF, 1 TF, 1 IS, 1 CON and 2 DPs (theoretically up to 4).

2.2.3 Central Functions

Managed object - Central Functions (CF) are generally considered as the main processing
ability or Central Processing Unit of Distribution Switch Unit (DXU).

It models all equipments in a base station infrastructure that are not part of other objects,
for example climate control. It provides communication for the AOs IS, CON, DP and TF. It
also handles the maintenance of the CF itself.

The CF is addressed by a Terminal Endpoint Identifier (TEI) in layer 2 signalling. TEI is

usually set to 62 in a single cabinet site.

What is a DXU? See Figure 4.

Figure 4 RBS2206 with DXU21

Provides the RBS with an interface to the transport network through four E1/T1
transmission ports

Handles incoming traffic, controls and supervises information and sends it to its
destination within the RBS

Provides frequency reference signals and timing signals for circuits within the RBS

Stores and executes RBS SW stored on a removable flash card

Controls climate and power systems in non-ECU equipped cabinets

Handles external alarms

Managed objects, such as CF, CON, IS, TF, DPs are separately abstracted in a DXU
based on a functionality – oriented method.

2.2.4 LAPD Concentrator

An AO, it provides the functionality for the distribution of signalling information from
concentrated links sharing Abis paths on to un-concentrated links, each terminated by a
TRXC.

The maximum concentration factor, or number of signalling links that can be concentrated
on to the same 64 kbps Abis path, is 16.

Up to 8 concentrated 64 kbps Abis paths can be routed to a maximum of 16 TRXCs.

2.2.5 Interface Switch

An AO, it provides switching capability within the TG by setting up connections between

DCPs.

The IS is capable of switching on a combination of 16kbit/s, 32kbit/s, and 64kbit/s at any

given time.

2.2.6 Timing Function

An AO, it provides timing necessary in a TG.

2.2.7 Digital Path

An AO, Layer 1 reception and transmission are not part of the BTS Logical Model.
However, each of the PCM systems terminating in a TG has an associated supervision
object, the DP.

Reports on transmission faults and supervision of transmission quality are carried over the
Abis O&M interface. That signalling is described using the BTS MO DP.

A DP instance contains all parameter settings and counters to monitor the PCM link. It also
performs procedures to report detected alarm conditions and quality values to BSC.

2.2.8 Transceiver Controller

An SO, it provides communication for other MO instances. It handles the communication to

the dedicated RX, TX and TSs. It also handles the maintenance of the TRXC itself. Or you
can approximately say a TRXC is the CPU of a TRU. A TRXC is also addressed by a TEI
when a LAPD cell arrives. Available TEIs for TRXC are usually 0 to 11 per cabinet and
related to its installation slot.
What is a TRU? See Figure 5, Figure 6.

Figure 5 RBS2206 with dTRU EDGE

Figure 6 Block Diagram of dTRU

The TRU consists of the following main blocks:

CPU system

DSP system

Radio Control (RC) system

Radio system
 TRXC, TX, RX, TS are MOs in a TRU1.

2.2.9 Transmitter

An AO, it provides the RF transmission functionality on a time slot basis for eight TSs
using different time slot numbers. Although communicated with via the TRXC, it can be
used by any TS in the same TG.

2.2.10 Receiver

An AO, it provides the Radio Frequency (RF) reception functionality for a transceiver.

2.2.11 Time Slot

An AO, it provides the functionality for controlling, signalling and processing for one time
slot of a TDMA frame.

2.3 Module Areas of Managed Objects

Since MOs are classified based on functionality – oriented method, the functionalities of
HW and SW module(s) are divided into different function areas by different MOs. See
Figure 7.
BS TG
DX

C
D TR
A- I LB T
S T CD
Y- TR
CO RX
TS

TIB
TF

Figure 7 BTS Logical Model G12 (RBS 2000)

2.4 Addressing of Managed Object Instances

An operator can identify an MO instance by its Managed Object Type (MOTY) and one or
more indices depending on MO class.

The basis for addressing MOs is the TG, which has an instance number as index.

The Central Functions (CF), Interface Switch (IS), Concentrator (CON), and Timing
Function (TF) are addressed by the same instance number as their TG.

1
TRU is standing for TRU, sTRU, dTRU or dTRU EDGE
 The Digital Paths (DPs) are addressed by using the same instance number as their TG,
and a local index within the TG.

The Transceiver Controllers (TRXCs), Receivers (RXs) and Transmitters (TXs) are
addressed by using the same instance number as their TG and a local index within the TG.
The TRXC and its dedicated RX and TX are related by using the identical local indices.

The Time Slots (TSs) are addressed by the same instance number as the TG, a local
index for the TRXC (within the TG) and a local index within the TRXC.

The addressing scheme is shown in Table 1.

Table 1 Addressing Scheme

MO Identification
MO class Limits
(MOTY-indices)
TG RXOTG-tg 0 <= tg <= 511
CF RXOCF-tg 0 <= tg <= 511
CON RXOCON-tg 0 <= tg <= 511
IS RXOIS-tg 0 <= tg <= 511
TF RXOTF-tg 0 <= tg <= 511
DP RXODP-tg-ldp 0 <= tg <= 511
0 <= ldp <= 3
TRXC RXOTRX-tg-ltrxc 0 <= tg <= 511
0 <= ltrxc <= 15
TX RXOTX-tg-ltrxc 0 <= tg <= 511
0 <= ltrxc <= 15
RX RXORX-tg-ltrxc 0 <= tg <= 511
0 <= ltrxc <= 15
TS RXOTS-tg-ltrxc-lts 0 <= tg <= 511
0 <= ltrxc <= 15
0 <= lts <= 7

Where:

tg: TG instance within MOTY RXOTG

ldp: Local DP index within its TG

ltrxc: Local TRXC index within its TG

lts: Local TS index within its TRXC

2.5 Managed Objects States

2.5.1 Global States

The global state of an MO in the BSC represents its operational state.

The following descriptions can be used to describe one or a set of global states:
 NOOPER PREOPER
Global States: DEF COM OPER
FAIL
Descriptions: Defined
Out of service or in
Service State In service
prepost service
Block State Manually blocked Manually deblocked
Operation In operation or
Out of operation
State operational
Application Automatically Not automatically
Not applicable
State blocked blocked

An MO cannot perform any traffic function if it is not operational. Some objects depend on
other objects to be able to be operational - they are automatically deblocked from superior
object. In a BTS logical model G12 TG the following relationships are valid:

TG (Superior)
| |
V |
CF |
| |
V |
/-------------------\ |
V V V V V |
TRXC IS CON TF DP |
| |
V |
/-------\ |
V V V |
RX TX TSs (Subordinate)

If an MO is out of operation then its subordinate MOs will also be taken out of operation.

To be used for its traffic function an Application Object (AO) must be configured. Whether
an AO is configured or not is reflected by its configuration state.

An MO can be defined, taken into service and manually deblocked.

The MO TG must be defined before any of its corresponding MOs.

The order for bringing MO instances into service is TG first, followed by CF, before its
corresponding IS, CON, DPs, TRXCs and TF; and TRXC before its corresponding TX, RX
and TS. The manual deblocking will start the process of bringing an MO into operation.
The MO will then, automatically, be available to carry traffic.

Similarly, an MO can be manually blocked to bring it out of operation, taken out of service
and removed. The order for taking MO instances out of service is TS, TX and RX before
the corresponding TRXC; TRXC, IS, CON, DPs and TF before the corresponding CF; and
CF before the corresponding TG.

All of an MO TG's corresponding MOs must have been removed before the TG MO itself
can be removed.
 Figure 8 MO Global State Transfer

2.5.2 BTS Operational States

This state indicates whether an MO is able to be used to its full capabilities. There are two
BTS operational states, 'Operational' and 'Not Operational'. To be 'Operational' the MO
must be in global state OPER and, in case of an AO it must also be configured and
enabled i.e. it is able to be used for traffic.

2.5.3 BTS States

For SOs, the following states are defined:

RESET

All variable parameters are cleared or initiated to their default values. Loading is handled,
with possible transfer of files allowed. Some supervision in the SO may not be active. The
reduced functionality means that services to its AOs are absent.

STARTED

All functions and hardware belonging to the SO are supervised. Loading is handled, with
possible transfer of files allowed. Once the loading is finished, all AOs belonging to the SO
may be connected.

For AOs, the following states are defined:

RESET

All variable parameters are cleared or initiated to their default values. Some supervision of
the AO may not be active. Connection on Layer 3 is allowed if the SO to which the AO
belongs is started and loaded.

DISABLED
All supervision is active. All O&M procedures are possible. No traffic management is
possible.

ENABLED

All supervision is active. Traffic management is started. Some configuration data may be
changed.