Documente Academic
Documente Profesional
Documente Cultură
Base Station
MOM User Guide
Version:V4.13.10.20
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
II
For example, the rack, which is a physical entity, is abstracted to a manageable MO (Rack)
in the MOM. Rack encapsulates manageable characteristics, such as RackId, rackNo, and
cabinetPosition. They are the attribute parameters of Rack. By setting these parameters,
you can configure the rack.
MO's DN
Each MO has a Distinguished Name (DN), which is the MO category name plus Id. For
example, the DN of the SubRack category is SubRackId. The MO category name and the
DN value form a Relative Distinguished Name (RDN), with a equal mark but without space
between them. For example, SubRack=1. Under the same upper-layer managed object,
each MO can have one and only RDN. It means that you can use the RDN of a subnode
to locate only one subnode.
1-1
The RDNs of all MOs on an MO tree form a Local Distinguished Name (LDN), with a comma
between two RDNs. For example, ManagedElement=1, Equipment=1,Rack=1. By using
an LDN, you can locate only one MO.
Creating An MO
An MO can be created by the system or the user, or created dynamically.
l Created by the system: In this case, the MO is not configured by the user. Instead,
it will be created automatically by the system after its parent MO is created. The MO
cannot be deleted separately. It will be deleted automatically after its parent MO is
deleted.
l Created dynamically: In this case, all attributes of the MO are reported dynamically
by the NE. The user do not need to configure the MO.
l Created by the user: This is the default way to create an MO. In this case, the user
can set MO parameters to create MOs. Such MOs can be modified or deleted by the
user.
MO Attributes
l Data Types of MO Attributes
The data types of MO attributes are classified into basic data types and compound
data types. The basic data types are listed in the table below.
l General MO Attributes
Different MOs have some same attributes, which are called general attributes.
1-2
2:disabled
4:Powered-down
65536:Block Smoothly
524288:Test
1048576:Powered-down
8388608:Power-saving
16777216:Synchronous
33554432:MMC Fault
67108864:License state-
constrained
1-3
instance may contain 0-2 MO_Y instances. If MO_X does not exist, MO_Y cannot be
created. Similarly, an MO_X cannot be deleted if it has MO_Y child nodes. The only
exception is that, if all child nodes of an MO_X are created automatically by the system,
the MO_X can be deleted and these child nodes will be deleted automatically.
Association relation: the association relation is a relation of resource usage, that is, a
quoting-quoted relation. One MO can quote, or be quoted by, multiple MOs of the same
kind or different kinds.
As shown in Figure 1-3, MO_X quotes MO_Y and MO_Y is quoted by MO_X. One MO_X
instance can quote 0-2 MO_Y instances while one MO_Y instance can be quoted by 0-3
MO_X instances. MO_X has the refMO_Y attribute, which indicates the LDN of the quoted
MO_Y instance. MO_Y has the reservedByMO_X attribute, which indicates the LDN of the
quoting MO_X instance.
1-4
MO Meaning
Operator Operator
Table of Contents
2-1
Equipment..................................................................................................................2-2
TransportNetwork.......................................................................................................2-5
Ir ................................................................................................................................2-8
BtsFunction ................................................................................................................2-8
NodeBFunction ..........................................................................................................2-9
Operator...................................................................................................................2-10
VsOam.....................................................................................................................2-10
2.1 Equipment
The base station equipment resources MO takes Equipment as the root node. The base
station management objects include rack, shelf, slot, card, feeder cable, fiber, mechanical
antenna, electric tilt antenna, and tower amplifier. The equipment resources are divided
into two parts. One part contains the BBU and RRU units (base band digital unit and
radio frequency unit). This part consists of the rack, shelf, slot, and card. The other part
contains the peripheral equipment of the base station, such as the antenna and feeder
system, external power, microwave equipment, or other three-party devices. This part
takes AuxUnit as the root unit.
The card is a basic functional unit of the base station. To adapt to various market
demands, a variety of functions can be combined together on one card. The card
is regarded as a physical entity and a functional set. This physical entity is defined
as PlugInUnit, standing for a physical card in a slot. The functional set is defined as
SdrDeviceGroup, standing for the functions and operations which the card supports. The
SdrDeviceGroup includes a group of Device MO of these functions and operations, such
as clock, base band processing, receiving/transmitting signal, power amplifier, and optical
interface.
Figure 2-2 shows the equipment resource MO model.
2-2
MO Meaning
Equipment Device
Cabinet Cabinet
Rack Rack
SubRack Sub-Rack
Slot Slot
2-3
MO Meaning
Pa PA
TxChannel Tx Device
RxChannel Rx Device
E1DeviceSet E1 Set
E1Device E1
T1DeviceSet T1 Set
T1Device T1
Stm1Device STM-1
2-4
MO Meaning
RfCable RF Cable
2.2 TransportNetwork
The transport resource MO takes TransportNetwork as the root node. The
TransportNetwork model is established according to the Iub and Abis interface
transmission protocol stack between the base station and the upper-layer NE RNC/BSC
(In LTE, the base station interconnects to CN.). From the physical layer to the application
layer, the resources such as Ethernet interface, E1/T1 interface, IP, ATM, NBAP, and
BTSM are abstracted.
2-5
MO Meaning
Aal2 AAL2
SaalUni SaalUni
Alcap ALCAP
2-6
MO Meaning
Sctp SCTP
Udp UDP
Rtp RTP
Tcp TCP
Dot1x DOT1X
2-7
MO Meaning
2.3 Ir
The Ir model is an abstract of the interfaces between BBU and RRU. The root node is Ir.
At present, the Ir model is not used.
Table 2-4 describes the Ir model MO meanings.
MO Meaning
2.4 BtsFunction
BtsFunction is the root node of GSM wireless service model. Figure 2-4 shows the
BtsFunction model.
MO Meaning
BtsFunction GSM
2-8
MO Meaning
2.5 NodeBFunction
NodeBFunction is the root node of UMTS wireless service model. Figure 2-5 shows the
NodeBFunction model.
MO Meaning
2-9
MO Meaning
2.6 Operator
Operator is an abstract of operators. This MO is used when the transport resources and
wireless resources are occupied or shared.
2.7 VsOam
VsOam is the root node of the specified MO of the vendor. VsOam MO includes ItfUniBts
which stands for OMA operation and maintenance interface. In 3GPP, ItfUniBts is called
as Itf-B. Figure 2-6 shows the VsOam model.
MO Meaning
2-10