iManager U2000-CME

Northbound Interface Scenario

Description (GSM)

Issue 01

Date 2014-01-20

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: http://www.huawei.com

Email: support@huawei.com

Issue 01 (2014-01-20) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) About This Document

About This Document

Keywords
CME, Northbound, XML

Abstract
This document describes the technical specifications of the configuration scenarios that the
U2000 CM NBI supports on a GSM network. CM is short for configuration management and
NBI is short for northbound interface. It provides information about interface control and
serves as a reference for users to integrate and interconnect umbrella operations support
system (OSS) tools and Huawei's U2000 system.

Issue 01 (2014-01-20) Huawei Proprietary and Confidential ii

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) Contents

Contents

About This Document....................................................................................................................ii

1 Introduction....................................................................................................................................1
2 Features............................................................................................................................................2
2.1 Network Resource Model..................................................................................................................................2
2.2 Northbound Parameter List................................................................................................................................2
2.3 Radio Parameters...............................................................................................................................................3
2.3.1 Neighbor Relationship Adjustment..........................................................................................................3
2.3.2 Frequency Adjustment..............................................................................................................................7
2.3.3 GSM BA Information...............................................................................................................................9
2.4 Transmission Parameters.................................................................................................................................12
2.4.1 Creating Non-logical BTSs....................................................................................................................12
2.4.2 Creating Logical BTSs...........................................................................................................................19
2.4.3 Deleting BTSs.........................................................................................................................................20
2.4.4 Creating Cells Under a Non-logical BTS...............................................................................................20
2.4.5 Creating Cells Under Logical BTSs.......................................................................................................21
2.4.6 Deleting Cells.........................................................................................................................................22
2.4.7 Creating Non-logical TRXs....................................................................................................................23
2.4.8 Creating Logical TRXs...........................................................................................................................24
2.4.9 Deleting TRXs........................................................................................................................................24
2.4.10 Adjusting BTS Transmission Parameters.............................................................................................25
2.5 Supplementary Information.............................................................................................................................27
2.5.1 Common Objects Under the Radio and Transmission Nodes................................................................27
2.5.2 BTSBRD.................................................................................................................................................27
2.6 Important Notes...............................................................................................................................................28

A Acronyms and Abbreviations....................................................................................................29

Issue 01 (2014-01-20) Huawei Proprietary and Confidential iii

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) IntroductionIntroduction

1 Introduction

The U2000 CM NBI provides configuration management based on configuration scenarios.

This document describes how to configure radio and transmission parameters for a GSM
network through the NBI in common configuration scenarios.
These configuration scenarios are achieved based on a network resource model (NRM). For
details, users can see the reference document listed in this document.

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 1

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

2 Features

2.1 Network Resource Model

For details about the NRM, users can see Northbound Interface MOM Reference (MOM for
short). The MOM document provides information, such as managed object classes (MOCs),
relationships, parameters, parameter value ranges, and business rules, about the NRM.

2.2 Northbound Parameter List

Configuration management depends on parameters. Therefore, parameters are key
information about the NRM. In addition to the MOM document, Excel files are provided to
describe the parameters that the NBI supports. These parameter list files contain only
information about MOCs and parameters. They do not contain any information about business
rules and the relationships between MOCs. They serve as subsets for defining managed object
models (MOMs).
The U2000 CM NBI also provides list files that conform to XML schema constraints and
contain parameter definitions. This enables applications to execute basic data check on XML
instance files transferred over the NBI based on XML schema files.

2.3 Radio Parameters

Radio parameters are classified into the following types based on their operation types:
 Primary key parameter
Such a parameter serves as the primary or foreign key that uniquely identifies an object
in the NRM. Therefore, users are not allowed to modify such parameters unless they
delete existing objects and then add new primary key parameters for identifying objects.
 Basic parameter
Such parameters are configured for cells and their external cells. To ensure data
consistency, users need to update the basic parameters of GEXT2GCELL in other
involved BSCs or those of UEXT2GCELL in other involved RNCs synchronously when
they update the basic parameters of a cell through the OSS.

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 2

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

The update is executed by the OSS.

 Common parameter
Most cell parameters are common parameters. Such parameters are configured only for
cells instead of their external cells.

Some common parameters are not allowed to be directly modified. For details, users can see the Access
column in the parameter list file. If the value of a parameter in the Access column is Read Only, users
are not allowed to modify the value of this parameter. If necessary, users can modify the value of such a
parameter only after they delete this parameter's existing owning or parent object and then create a new
owning or parent object.

The following sections describe certain special radio parameters that are usually managed as
independent subsessions.

2.3.1 Neighbor Relationship Adjustment

Neighbor relationships maintained on BSCs are classified into the following types:
 G2GNCELL: GSM-GSM neighbor relationships
 G3GNCELL: GSM-UMTS neighbor relationships
 GLTENCELL: GSM-LTE neighbor relationships

Figure 1.1 Neighbor relationships

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 3

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

GSM-GSM Neighbor Relationship

GSM-GSM neighbor relationships describe neighbor relationships between GSM cells.
G2GNCELL is an MOC that manages GSM-GSM neighbor relationships. GSM-GSM
neighbor relationships are classified into the following types based on whether a cell and its
peer cell are served by the same BSC:
 Intra-BSC GSM-GSM neighbor relationship
A cell and its peer cell are served by the same BSC.
− Creating an intra-BSC GSM-GSM neighbor relationship
Users can directly create such a neighbor relationship, unidirectional or bidirectional,
through the OSS. If users create a bidirectional neighbor relationship between cells A
and B, two neighbor relationships are created, where the source and destination cells
are A and B, and B and A, respectively.
− Modifying an intra-BSC GSM-GSM neighbor relationship
All such neighbor relationships related to a destination cell are automatically
modified if the basic parameters (such as CGI, BCCH, BCC, and NCC) of the
destination cell are modified. Users can directly modify other parameters of the
destination cell.

In this document, CGI is a combination of MCC, MNC, LAC, and CI.

− Deleting an intra-BSC GSM-GSM neighbor relationship
Users can delete such neighbor relationships between cells as required.

When users delete a source or destination GCELL, the CME automatically deletes involved neighbor
relationships maintained on the BSC serving this GCELL.
 Inter-BSC GSM-GSM neighbor relationship
The peer cell of a cell is served by another BSC.
− Creating an inter-BSC GSM-GSM neighbor relationship
If users want to create a neighbor relationship for a cell whose peer cell is served by
another BSC, they need to create a GSM external cell (GEXT2GCELL) on the BSC
serving the cell through the OSS first.
The two operations, creating a GEXT2GCELL and creating a G2GNCELL, in an
XML file imported over the NBI can be included in the same subsession. The CME
generates a script by including the ADD GEXT2GCELL and ADD G2GNCELL
commands in a time sequence.
The inter-BSC GSM-GSM neighbor relationship between a cell and its external cell
can only be unidirectional. If users want to configure a neighbor relationship from the
external cell to the cell, they need to perform operations on the BSC serving the
external cell.
In addition, cells related to a GEXT2GCELL might be served by BSCs from different
vendors, and therefore information about the GEXT2GCELL might exceed the
management scope of the CME.
− Modifying an inter-BSC GSM-GSM neighbor relationship
After the basic parameters (such as CGI, BCCH, BCC, and NCC) of a destination cell
are modified, users must adjust all its GEXT2GCELLs managed by other BSCs
synchronously through the OSS. Otherwise, outgoing neighbor relationships
maintained on these BSCs might be incorrect.
− Deleting an inter-BSC GSM-GSM neighbor relationship
Issue 01 (2014-01-20) Huawei Proprietary and Confidential 4
Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

Users can delete such neighbor relationships between cells as required.

When users delete a GEXT2GCELL, the CME automatically deletes involved neighbor relationships
maintained on the BSC serving this GEXT2GCELL.
When users delete a source GCELL, the CME automatically deletes involved neighbor relationships
maintained on the BSC serving this GCELL.
When all neighbor relationships related to a GEXT2GCELL are deleted, users must delete this
GEXT2GCELL through the OSS. Otherwise, information about this GEXT2GCELL becomes
redundant.
When the destination cell of a GEXT2GCELL is deleted, users must delete this GEXT2GCELL and all
involved neighbor relationships maintained on other BSCs synchronously through the OSS. Otherwise,
outgoing neighbor relationships maintained on these BSCs might be incorrect.

GSM-UMTS Neighbor Relationship

 Creating a GSM-UMTS neighbor relationship
G3GNCELL is used to identify the neighbor relationship from a GSM cell to a UMTS
cell. Before creating a GSM-UMTS neighbor relationship, users need to create a UMTS
cell on an RNC, and then create a GEXT3GCELL on a BSC to represent the UMTS cell.
All created GSM-UMTS neighbor relationships can only be unidirectional.
The two operations, creating a GEXT3GCELL and creating a G3GNCELL, in an XML
file imported over the NBI can be included in the same subsession. The CME generates a
script by including the ADD GEXT3GCELL and ADD G3GNCELL commands in a
time sequence.
In addition, cells related to a GEXT3GCELL might be served by RNCs from different
vendors, and therefore information about the GEXT3GCELL might exceed the
management scope of the CME.
 Modifying a GSM-UMTS neighbor relationship
The configuration of a GEXT3GCELL must be consistent with that of its related UMTS
cell served by an RNC. After the basic parameters of the UMTS cell are modified, users
must update the configuration of the GEXT3GCELL served by a BSC synchronously
through the OSS. The update is executed by the OSS.
 Deleting a GSM-UMTS neighbor relationship

When users delete a GEXT3GCELL, the CME automatically deletes involved neighbor relationships
maintained on the BSC serving this GEXT3GCELL.
When users delete a source GCELL, the CME automatically deletes involved neighbor relationships
maintained on the BSC serving this GCELL.
When all neighbor relationships related to a GEXT3GCELL are deleted, users must delete this
GEXT3GCELL. Otherwise, information about this GEXT3GCELL becomes redundant.
When the destination cell of a GEXT3GCELL is deleted, users must delete this GEXT3GCELL and all
involved neighbor relationships maintained on other BSCs synchronously through the OSS. Otherwise,
outgoing neighbor relationships maintained on these BSCs might be incorrect.

GSM-LTE Neighbor Relationship

 Creating a GSM-LTE neighboring relationship
GLTENCELL is used to identify the neighbor relationship from a GSM cell to an LTE
cell. Before creating a GSM-LTE neighbor relationship, users need to create an LTE cell
on an eNodeB, and then create a GEXTLTECELL on a BSC to represent the LTE cell.
All created GSM-LTE neighbor relationships can only be unidirectional.

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 5

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

The two operations, creating a GEXTLTECELL and creating a GLTENCELL, in an

XML file imported over the NBI can be included in the same subsession. The CME
generates a script by including the ADD GEXTLTECELL and ADD GLTENCELL
commands in a time sequence.
In addition, cells related to a GEXTLTECELL might be served by eNodeBs from
different vendors, and therefore information about the GEXTLTECELL might exceed the
management scope of the CME.
 Modifying a GSM-LTE neighbor relationship
The configuration of a GEXTLTECELL must be consistent with that of its related LTE
cell served by an eNodeB. After the basic parameters of the LTE cell are modified, users
must update the configuration of the GEXTLTECELL served by a BSC synchronously
through the OSS. The update is executed by the OSS.
 Deleting a GSM-LTE neighbor relationship

When users delete a GEXTLTECELL, the CME automatically deletes involved neighbor relationships
maintained on the BSC serving this GEXTLTECELL.
When users delete a source GCELL, the CME automatically deletes involved neighbor relationships
maintained on the BSC serving this GCELL.
When all neighbor relationships related to a GEXTLTECELL are deleted, users must delete this
GEXT3GCELL. Otherwise, information about this GEXT3GCELL becomes redundant.
When the destination cell of a GEXTLTECELL is deleted, users must delete this GEXTLTECELL and
all involved neighbor relationships maintained on other BSCs synchronously through the OSS.
Otherwise, outgoing neighbor relationships maintained on these BSCs might be incorrect.

Following are example files for adjusting neighbor relationship:

 AdjacencyRelationModification\01-Sample_Create_2G.xml
 AdjacencyRelationModification\01-Sample_Delete_2G.xml
 AdjacencyRelationModification\01-Sample_Update_2G.xml
 AdjacencyRelationModification\02-Sample_Create_3G.xml
 AdjacencyRelationModification\02-Sample_Delete_3G.xml
 AdjacencyRelationModification\02-Sample_Update_3G.xml
 AdjacencyRelationModification\03-Sample_Create_LTE.xml
 AdjacencyRelationModification\03-Sample_Delete_LTE.xml
 AdjacencyRelationModification\03-Sample_Update_LTE.xml

2.3.2 Frequency Adjustment

In scenarios such as the network deployment and capacity expansion, users need to allocate
frequencies for newly created TRXs. In addition, with the development of the network, traffic
increases seriously, which may increase the radio interference. The radio interference can be
greatly reduced by using proper frequency optimization algorithms. Therefore, adjusting cell
frequencies becomes an important means to improve the network performance in routine
maintenance. Users are advised to allocate frequencies with caution. Otherwise, the co-
channel interference and adjacent-channel interference may occur, which decrease network
performance.
2. Modifying frequency parameters
The frequency parameters include:
− Cell frequency list (GCELLFREQ)

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 6

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

− TRX frequency (GTRX)

Parameters related to frequency hopping (FH), including the ARFCNs in
GCELLMAGRP, HSN, and TRXMAIO in GTRXCHANHOP

Table 1.1 Objects related to frequency modification

MOC Modifier

GCELLFREQ M
GTRX M
GCELLMAGRP M
GTRXCHANHOP M

In the MML commands provided by the BSC, only the commands of adding and deleting
frequencies are provided for the MOC GCELLFREQ and users are unable to modify
GCELLFREQ directly. In this case, a new function is provided on the NBI for users to
modify GCELLFREQ. This facilitates users' operations. Operations performed on
GCELLFREQ are as follows:
− Create: performs this operation only when users need to add frequencies for a cell.
Only information about new frequencies is provided in the FREQ list. Information
about the existing frequencies is not provided.
− Update: performs this operation for each cell once when users modify frequencies or
add and delete frequencies at the same time. Information about all the frequencies
after the adjustment must be provided in the FREQ list. The CME automatically
separates this operation to frequency addition and deletion operations. In this case,
the frequency addition and deletion operations can be replaced by this operation.
− Delete: performs this operation only when users need to delete some frequencies
from a cell. Only information about the deleted frequencies is provided in the FREQ
list. Information about frequencies you do not need to delete is not provided.

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 7

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

 The update operation can be converted to the ADD and RMV commands, and the ADD command
is executed before the RMV command. However, the number of frequencies in each cell cannot
exceed the MaxFrequencyCount threshold based on the rule set on the BSC. In this case, if users
prepare to adjust the frequency list of a cell through the umbrella OSS, the number of frequencies
before the adjustment is M, the number of frequencies (that do not exist before the adjustment) you
need to add during the adjustment is N, and the sum of M and N is greater than the
MaxFrequencyCount threshold, executing the ADD command before the RMV command may fail
after users import the file. However, the number of frequencies does not exceed the limitation
according to final data. The CME fails to detect errors in the rule by checking final data. Therefore,
users need to comply with the rule when planning frequencies using the umbrella OSS. In this case,
the sum of the original number of frequencies and the number of new frequencies is less than or
equal to the MaxFrequencyCount threshold. The typical MaxFrequencyCount threshold is 64.
 Changing main BCCH TRX from one TRX to another TRX is not supported on the CME. Users can
change main BCCH TRX by running the MOV BCCH command on the BSC.
 Users also need to modify corresponding parameters using the umbrella OSS when modifying the
frequency of a main BCCH TRX on the BSC. This ensures that the modified BCCH parameter is
consistent with BCCH parameters such as GEXT2GCELL on other BSCs and UEXT2GCELL on
other RNCs.
 You can perform operations in the following subsessions for similar situations:
 Subsession1: Delete the neighbor relationship between cell A and cell B.
 Subsession2: Modify AFRCNs of main BCCH TRXs in cell A and cell B.
 Subsession3: Add the neighbor relationship between cell A and cell B.
 In GBSS16.0 and later versions, you can perform the operations in one subsession. For details, see
section 2.6"Important Notes".
3. Adjusting the FH mode
In this scenario, users can switch over the FH mode of a cell without considering adding,
deleting, and modifying TRXs.

Table 1.1 MOCs related to FH mode adjustment

MOC Modifier

GCELLHOPTP M
GTRXHOP M
GTRXCHANHOP M
GCELLMAGRP A/D

Following are example files for adjusting frequencies:

− FrequencyModification\01-Sample_Frequency.xml
− FrequencyModification\02-Sample_Frequency.xml

2.3.3 GSM BA Information

The BA information belongs to radio parameters. Users need to pay great attention when
exporting data.

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 8

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

Table 1.2 MOCs related to the BA

MOC

GCELL2GBA1
GCELLHO2GBA2
GCELLHOFDDBA2
GCELLHOTDDBA2
GCELLIDLEFDDBA1
GCELLIDLETDDBA1

Table 1.3 Information about the GCELL2GBA1 parameter

Cell ID Cell Index

CELL2GBA1BCCH 2G NCELL BCCH

CELL2GBA1TAG 2GBA1 Input Tag
ITEM NCCELL No.
ITEMVALID Item Valid
CELL2GBA1OPTSW 2G BA1 Neighboring Cell Optimization Switch

Table 1.4 Information about the GCELLHO2GBA2 parameter

Cell ID Cell Index

CELL2GBA2BCCH 2G NCELL BCCH

CELL2GBA2TAG 2GBA2 Input Tag
ITEM NCCELL No.
ITEMVALID Item Valid
CELL2GBA2OPTSW 2G BA2 Neighboring Cell Optimization Switch

Table 1.5 Information about the GCELLHOFDDBA2 parameter

Cell ID Cell Index

DF DL UARFCN
SCRAMBLE Scrambling Code or Cell Parameter Id
FDDBA2TAG FDDBA2 Input Tag
ITEM NCCELL No.
ITEMVALID Item Valid
DIVERSITY Diversity

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 9

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

Table 1.6 Information about the GCELLHOTDDBA2 parameter

Cell ID Cell Index

DF DL UARFCN
TDDSCRAMBLE Cell Parameter ID
TDDBA2TAG TDDBA2 Input Tag
ITEM NCCELL No.
ITEMVALID Item Valid
TDDSYNCCASE Sync Case
DIVERSITY Diversity

Table 1.7 Information about the GCELLIDLEFDDBA1 parameter

Cell ID Cell Index

FDDDLUARFAN Downlink Frequency

FDDSCRAMBLE Scrambling Code
FDDBA1TAG FDDBA1 Input Tag
ITEM NCCELL No.
ITEMVALID Item Valid
FDDDIVERSITY Diversity Indication

Table 1.8 Information about the GCELLIDLETDDBA1 parameter

Cell ID Cell Index

TDDDLUARFAN DL UARFAN
TDDSCRAMBLE Cell Parameter ID
TDDBA1TAG TDD BA1 Input Tag
ITEM NCCELL No.
ITEMVALID Item Valid
TDDSYNCCASE Sync Case
TDDDIVERSITY Diversity

Take the configuration of GCELL2GBA1 as the example.

The parameter CELL2GBA1TAG indicates whether the 2G BA1 table is generated
automatically based on neighbor relationships, created manually or automatically based on
neighbor cell ranking priority. The corresponding enumeration values are AUTO(Auto),

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 10

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

MANU(Manu) and AUTO2GNCELLRANKPRI(Auto import based on neighbor cell

ranking priority). In this situation, GCELL2GBA1 in a cell can only set one configuration
mode at the same time.
In versions from GBSS9.0 to GBSS13.0, GCELL2GBA1 data of the cell can be exported only
when CELL2GBA1TAG is set to MANU. Therefore, users need to extract data from their
own neighbor relationships if CELL2GBA1TAG is set to AUTO. From GBSS14.0 onwards,
all valid data (ITEMVALID=TRUE) can be exported without considering whether
CELL2GBA1TAG is set to AUTO or MANU. This helps users analyze data. If all
GCELL2GBA1 data of a cell is invalid, users need to export the first invalid GCELL2GBA1
object (ITEM=1). This helps users identify the value of the CELL2GBA1TAG parameter
and avoids the occurrence of the processing efficiency reduction caused by exporting large
amounts of invalid data.
When users import GCELL2GBA1 data of a cell, if CELL2GBA1TAG is set to AUTO, only
one object needs to be configured. If CELL2GBA1TAG is set to MANU, each object you
want to adjust needs to be configured. If CELL2GBA1TAG is set to
AUTO2GNCELLRANKPRI (in GBSS16.0 and later versions), only one object needs to
be configured. CELL2GBA1TAG cannot be set to AUTO, MANU and
AUTO2GNCELLRANKPRI for the same cell simultaneously.
When users modify GCELL2GBA1 and GCELL2GBA2(in GBSS16.0 and later versions),
CELL2GBA1OPTSW(2G BA1 Neighboring Cell Optimization Switch) needs to be
configured.
Mechanisms for processing other BA-related MOCs are similar.

2.4 Transmission Parameters

2.4.1 Creating Non-logical BTSs
Introduction to the BTS topology
On the live network, different BTSs may connect together to compose different network
topologies, such as the star topology, chain topology, tree topology, and ring topology, based
on different geographic distributions. Therefore, deploying a proper network topology
becomes an important part of project planning.
The following tables describe the BTS network topology.

Table 1.1 Parameters related to the BTS that is connected to the BSC
NBI Parameter ID Parameter Name

BTSID BTS Index

INPN BTS In Port No.
INCN In Port Cabinet No.
INSRN In Port Subrack No.
INSN In Port Slot No.
DESTNODE Dest Node Type

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 11

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

NBI Parameter ID Parameter Name

SRN Subrack No.

SN Slot No.
PN Port No.

Table 1.2 Parameters related to the BTS that is connected to another BTS
NBI Parameter ID Parameter Name

BTSID BTS Index

INPN BTS In Port No.
INCN In Port Cabinet No.
INSRN In Port Subrack No.
INSN In Port Slot No.
DESTNODE Dest Node Type
UPBTSID Dest Father BTS Index
FCN Cabinet No. of Father BTS
FSRN Subrack No. of Father BTS
FSN Slot No. of Father BTS
FPN Dest Father BTS Port No.

Table 1.3 Parameters related to the BTS that is connected to the DXX
NBI Parameter ID Parameter Name

BTSID BTS Index

INPN BTS In Port No.
INCN In Port Cabinet No.
INSRN In Port Subrack No.
INSN In Port Slot No.
DESTNODE Dest Node Type
DXXINDEX Up DXX Index
DXXPN Up DXX Port No.

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 12

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

Each line in the preceding tables describes one physical connection. All the lines put together
can describe a BTS network topology.
Key parameters are described as follows:
 BTS Index: uniquely identifies a BTS managed by the BSC.
 BTS in Port No.: indicates the BTS port number that is used to set a physical connection
link with the peer device.
 Dest Node Type: indicates the type of the peer device you want to connect when setting
the physical connection link.
Following are three types of peer devices that are connected to the BTS:
 The BTS connects to the BSC directly.
 The BTS connects to another BTS.
 The BTS connects to the DXX.
In Port Cabinet No., In Port Subrack No., In Port Slot No.: identifies the position of
GTMU boards, where the output outgoing port of the physical connection link is situated, for
the BTS together.
Subrack No., Slot No., Port No.: identifies the position of the port on the Abis interface
board of the BSC together.
Dest Father BTS Index, Dest Father BTS Port No.: identifies the position of the port that is
used to connect to the upper-level BTS.
Up DXX Index, Up DXX Port No.: identifies the position of the port on the DXX you want
to connect to.
Figure 1.2 shows the definition of each parameter.

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 13

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

Figure 1.2 Parameter definitions

In Figure 1.2, BTS_1 and BTS_2 compose a chain topology, and BTS_3 and BTS_4 compose
a ring topology. For details about parameters, see Table 2.1.

Table 2.1 Parameters related to the BTS that is connected to the BSC
BTS BTS In In Port In Port In Port Dest Subrack Slot Port
Index Port Cabinet Subrack Slot Node No. No. No.
No. No. No. No. Type

1 0 0 0 6 BSC 0 14 0
3 0 0 0 6 BSC 0 15 0
4 1 0 0 6 BSC 0 15 1

Table 2.2 Parameters related to the BTS that is connected to another BTS
BTS BTS In In Port In Port In Port Dest Dest Cabinet Subrack Slot No. Dest Father
Index Port No. Cabinet Subrac Slot Node Father No. of No. of of Father BTS Port
No. k No. No. Type BTS Index Father BTS Father BTS BTS No.

2 0 0 0 6 BTS 1 0 0 6 1

4 0 0 0 6 BTS 3 0 0 6 1

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 14

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

Table 2.3 Parameters related to the BTS that is connected to the DXX
BTS BTS In In Port In Port In Port Dest Node Up DXX Up DXX
Index Port No. Cabinet No. Subrack No. Slot No. Type Index Port No.

5 0 0 0 6 DXX 8 1

In addition to the primary link, the secondary link and reverse link are automatically
determined based on Config Ring and BTS in Port No..

Procedure for creating a BTS

Users need to provide the basic BTS information, BTS template, BTS transmission links, cell
configuration data, and TRX configuration data in the imported XML file before creating a
BTS. For details, see the example file.
Table 1.1 describes the format of BTS data and related MOC data.

Table 1.1 Format of BTS data and related MOC data

Category Child Category Format

Basic BTS information NA XML

BTS device NA BTS template
Transmission links on the TDM XML
BTS side
IP over E1 XML
IP over FE/GE XML
Cell NA Cell template
TRX NA XML

The process of creating a BTS is complicated. To solve this problem, the CME introduces
templates. Templates imported over the NBI can be classified into the BTS template and cell
template. This section describes the BTS template. For details about the cell template, see
sections 2.4.4"Creating Cells Under a Non-logical BTS" and 2.4.5"Creating Cells Under
Logical BTSs."
Generally, configurations of hardware parameters are the same for the same type of BTSs of a
telecom operator or can be classified into a few types. Therefore, users can pack these data
into a BTS template and use only the specified BTS template when creating a BTS. In this
way, the management for the specific device parameters is not required.
A series of default BTS templates are provided with the release of a CME version. In addition,
users can create or delete user-defined templates. For details about how to manage user-
defined templates, see the CME online help.
Users export all the available BTS templates when exporting files. The name of the XML
element in a BTS template is BTSTEMPLATERSC, and it is the sub element of
Transmission. BTSTEMPLATERSC contains only one attribute, TEMPLATENAME. It is
recommended that the template name contain basic information such as the BTS type and

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 15

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

transmission type so that the template can be easily identified. For example,
defaultOfBTS3900AGSM_SRAN_IPFE_BTS3012II indicates that it is a default template
provided by the CME, the BTS type is BTS3900AGSM that belongs to an SRAN base
station, the transmission type is IPFE, and the cabinet type is BTS3012 II.
BTSTEMPLATE (include parameters BTSID and TEMPLATENAME) is used to
describe the BTS template used by the corresponding BTS when users import files.
BTSTEMPLATE is required when users create non-logical BTSs and not required when
users modify or delete BTSs.

Restrictions on creating a BTS

When both the BTS template and the XML file contain the object instance MOI, the MOI
object in the BTS template will be ignored and that in the XML file will be used. Following
are some examples.

Table 1.1 BTSRXUBRD in a BTS template

RXU Chain No. Cabinet No. Subrack No. Slot No.

1 0 3 0
1 0 3 1
1 0 3 2

Table 1.2 BTSRXUBRD in an XML file

RXU Chain No. Cabinet No. Subrack No. Slot No.

1 0 3 2
1 0 3 3
1 0 3 4

Table 1.3 lists the imported result data.

Table 1.3 Imported result data

RXU Chain No. Cabinet No. Subrack No. Slot No.

1 0 3 0
1 0 3 1
1 0 3 2
1 0 3 3
1 0 3 4

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 16

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

Data in the cell template is processed in the way similar to the preceding.
Users use the template only to manage BTS and cell data during the creation. No records
related to the use of the template are left after BTSs and cells are created, and template
information used in creating a BTS and a cell is not contained in the exported northbound file.
Users need to put transmission parameters and related radio parameters in the network
resource model over the Abis interface to the same subsession for import when creating a
BTS. However, external cells and neighbor relationships can be created in another subsession.
For details about cells and TRXs, see the following sections.

Classification of the BTS transmission type

MOCs you need to configure vary based on transmission types of BTSs. Configurations are
mandatory for some MOCs but optional for some others when BTSs need to be activated.
Table 1.1 describes the involved transmission MOCs when the transmission mode of the BTS
is set to TDM.

Table 1.1 Involved transmission MOCs

MOC Mandatory or Optional

BTSCONNECT Mandatory
BTSMONITORTS Optional
BTSIDLETS Optional

Table 1.2 describes the involved transmission MOCs when the transmission mode of the BTS
is set to IP over E1.

Table 1.2 Involved transmission MOCs

MOC Mandatory or Optional

BTSCONNECT Mandatory
IPRT Optional
PPPLNK Optional
MPRGP Optional
MPLNK Optional
BTSIP Mandatory
BTSIPRT Optional
BTSIPRTBIND Optional
BTSBFD Optional
BTSPPPLNK Mandatory (if use PPPLNK)
BTSMPGRP Mandatory (if use MPLNK)

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 17

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

MOC Mandatory or Optional

BTSMPLNK Mandatory (if use MPLNK)

BTSMONITORTS Optional
BTSIDLETS Optional
BTSESN Mandatory
G_ADJNODE Mandatory
G_ADJMAP Optional
G_IPPATH Optional

Table 1.3 describes the involved transmission MOCs when the transmission mode of the BTS
is set to IP over FE/GE.

Table 1.3 Involved transmission MOCs

MOC Mandatory or Optional

IPRT Optional
ETHIP Optional
BTSIP Mandatory
BTSIPRT Optional
BTSIPRTBIND Optional
BTSBFD Optional
BTSETHPORT Mandatory (For V900R011)
Optional (For V900R012 and later)
BTSDEVIP Mandatory (For V900R012 and later)
BTSESN Mandatory
BTSIPCLKPARA Optional
G_ADJNODE Mandatory
G_ADJMAP Optional
G_IPPATH Optional

Following are XML example files for creating BTSs:

 BTS\01-Sample_Create_TDM.xml
 BTS\02-Sample_Create_IPOE.xml
 BTS\03-Sample_Create_IPFE.xml

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 18

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

Technical Suggestions
Many aspects need to be concerned when users create BTSs. Some operations are time-
consuming. To avoid waiting for a long time, users are advised to import a maximum of 20 to
50 BTSs each time. No restrictions are required when users modify BTSs.

2.4.2 Creating Logical BTSs

For base stations in SingleRAN8.0 and later versions, physical BTSs are managed through co-
MPT BTSs. BSCs are only used to create logical BTSs. No templates are required when users
create logical BTSs because data such as BTS device data is reparented to physical BTSs for
configuration. Most cell data is managed by BSCs. Therefore, cell templates are mandatory
when users create cells.
The following describes how to create a logical BTS.
To create a logical BTS, provide basic BTS information, transmission links on the BSC side,
and cell and TRX information in the imported XML file. For details, see the example file.
Table 1.1 describes the bearer format of related information.

Table 1.1 Bearer format of related information

Category Child Category Format

Basic BTS information NA XML

Transmission links on the BSC side IP over E1 XML
IP over FE/GE XML
Cell NA Cell template
TRX NA XML

Currently, the logical BTS supports only IP transmission mode.

Table 1.2 lists transmission MOCs on the BSC side.

Table 1.2 Transmission MOCs on the BSC side

MOC Mandatory or Optional

IPRT Optional
PPPLNK Optional
MPRGP Optional
MPLNK Optional
ETHIP Optional
SCTPLNK Mandatory
ABISCP Mandatory
BTSOAMIP Mandatory

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 19

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

MOC Mandatory or Optional

G_ADJNODE Mandatory
G_ADJMAP Optional
G_IPPATH Optional

For details about how to create a logical cell and TRX, see the following related sections.

Following is an example file for creating BTSs:

BTS\04_Sample_Create_Logical_BTS.xml

2.4.3 Deleting BTSs

Deleting BTSs, which is a routine operation on the network, includes deleting non-logical
BTSs and logical BTSs from the BSC. Users need to provide the primary key information
about BTSs (BTSID) in the imported XML file through the umbrella OSS during the deletion.
If the file is imported successfully, BTSs and sub objects of the BTSs such as cells, TRXs, and
neighbor relationships will be deleted.
Following are example files for deleting BTSs:
BTS\01-Sample_Delete_TDM.xml
BTS\04_Sample_Delete_Logical_BTS.xml

2.4.4 Creating Cells Under a Non-logical BTS

This section describes how to create cells under an existing non-logical BTS.
Table 1.3 describes configuration data involved in cell creation.

Table 1.3 Configuration data involved in cell creation

Category Child Category Format MOCs Modifier

Basic BTS NA XML BTSRXUCHAIN A

information
BTSRXUBRD A
BTSRXUBP M
BTSTRXBRD A
Cell Cell parameter Cell GCELLTEMPLAT
template E
Basic cell XML GCELL A
information
CELLBIND2BTS A
GCELLOSPMAP A

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 20

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

Category Child Category Format MOCs Modifier

GCELLFREQ A
PTPBVC A
TRX NA XML GTRX A
TRXBIND2PHYB A
RD

CELLBIND2BTS describes the BTS that is bound with GCELL.

Users need to configure PTPBVC when GPRS features are enabled for the cell.
To simplify settings of cell parameters during cell creation, cell templates are introduced to
encapsulate all network optimization parameters except for basic cell parameters (such as
CellName, CGI, NCC, BCC, and BCCH).
The CME provides a default cell template for each NE version. The template is delivered with
the release of the NE version. Users can create or delete user-defined templates. For details
about how to manage user-defined cell templates, see the CME online help.
Users export all the available cell templates when exporting the XML file. The name of the
XML element in a cell template is GCELLTEMPLATERSC, and it is the sub element of
Transmission. GCELLTEMPLATERSC contains only one attribute, TEMPLATENAME.
It is recommended that the template name contains the brief description of the template. For
example, default 2G Cell Template, which indicates that it is a default cell template provided
by the CME.
GCELLTEMPLATE (include parameters CELLID and TEMPLATENAME) is used to
describe the cell template used by the corresponding GCELL when users import the XML
file.
GCELLTEMPLATE must be provided when users create GCELL. However, it is not
required when users modify or delete GCELL.
Following is an example file for creating cells:
GCELL\01-Sample_Create_GCELL.xml

2.4.5 Creating Cells Under Logical BTSs

This section describes how to create cells under an existing logical BTS.
This section only describes how to create logical cells on the BSC side and does not describe
how to configure local and physical cells. Users need to configure them on the BTS side.
Table 1.4 describes configuration data involved in cell creation.

Table 1.4 Configuration data involved in cell creation

Category Child Category Format MOCs Modifier

Cell Cell parameter Cell GCELLTEMPLATE

template

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 21

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

Category Child Category Format MOCs Modifier

Basic cell XML GCELL A

information
CELLBIND2BTS A
GCELLOSPMAP A
GCELLFREQ A
PTPBVC A
TRX NA XML GTRX A

CELLBIND2BTS describes the BTS that is bound with GCELL.

Users need to configure PTPBVC when GPRS features are enabled for the cell.
Compared with creating cells under a non-logical BTS, creating cells under a logical BTS
requires users to:
 Configure local cell ID (GLOCELLID) in GCELL
 Configure GTRXGROUPID in GTRX when creating TRXs without adding the
TRXBIND2PHYBRD object
 Reparent BTSTRXBRD or BTSRXUBRD and related data to physical BTSs for
configuration
Following is an XML example file for creating logical cells:
GCELL\01-Sample_Create_Logical_GCELL_BSC.xml

2.4.6 Deleting Cells

Deleting cells, which is a routine operation on the network, includes deleting non-logical cells
and logical cells from the BSC. Users need to provide the key parameter of cells (CELLID)
in the imported file through the umbrella OSS during the deletion. If the file is imported
successfully, related cells and sub objects of the cells such as TRXs, and neighbor
relationships will be deleted.
Restrictions on deleting cells
Users cannot delete the last cell on an activated BTS. That is, the activated BTS must contain
at least one activated GCELL.
Users need to delete local cells on the physical BTS side when deleting logical cells from a
co-MPT BTS using the umbrella OSS.
Following is an example file for deleting a cell:
GCELL\02-Sample_Delete_GCELL.xml

2.4.7 Creating Non-logical TRXs

A non-logical TRX indicates the TRX on a non-logical BTS.
Users need to create TRXs on the existing BTSs or in the existing cells when performing BTS
capacity expansion and add some hardware during the creation.

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 22

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

Table 1.5 Data involved in non-logical TRX creation

Category Child Category Format MOCs Modifier

Basic BTS NA XML BTSRXUCHAIN A

information
BTSRXUBRD A
BTSRXUBP M
BTSTRXBRD A
Cell Basic cell XML GCELLFREQ A/M
information
TRX NA XML GTRX A
TRXBIND2PHYBRD A
GTRX sub object A/M

Following is an example file for creating TRXs:

GTRX\01-Sample_Create_GTRX.xml

If the RF FH or hybrid FH has been set for the cell before users import the file and the frequency for the
new TRX has been used by the FH group, users can perform the following operations:

If IBCA is disabled for the cell, users can import the file by performing operations in the
following subsessions:
 Subsession1: Shut down the TRX for the cell.
 Subsession2: Create and activate the TRX and configure final FH data.
If IBCA is enabled for the cell and the TRX cannot be shut down for the activated cell, users
can import the file by performing operations in the following subsessions:
 Subsession1: Deactivate cells. Users need to deactivate the BTS if all the cells on the
BTS are deactivated.
 Subsession2: Create but do not activate the TRX and configure final FH data.
 Subsession3: Recover or set the active state.
The second method also applies to the scenario where IBCA is disabled for the cell. In this
case, users need to deactivate associated BTSs.
In GBSS16.0 and later versions, users can perform the operations in one subsession. For
details, see section 2.6"Important Notes".

2.4.8 Creating Logical TRXs

This section only describes how to create logical TRXs on the BSC side. A logical TRX
indicates the TRX configured on the logical BTS. The OSS needs to create the new
GTRXGROUP on the physical BTS before creating the logical TRX.
Table 1.6 describes data involved in logical TRX creation.

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 23

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

Table 1.6 Data involved in logical TRX creation

Category Child Category Format MOCs Modifier

Cell Basic cell information XML GCELLFREQ A/M

TRX NA XML GTRX A
GTRX sub object A/M

Compared with creating non-logical TRXs, creating logical TRXs requires users to:
Configure GTRXGROUPID in GTRX when creating TRXs without adding the
TRXBIND2PHYBRD object
Reparent BTSTRXBRD or BTSRXUBRD and related data to physical BTSs for
configuration

For details about the precautions for creating TRXs in cells of the RF FH mode, see section
2.4.7"Creating Non-logical TRXs."

2.4.9 Deleting TRXs

Deleting TRXs, which is a routine operation on the network, includes deleting non-logical
TRXs and logical TRXs from the BSC. If physical TRXs on base stations in SingleRAN8.0
and later versions need to be deleted, users need to perform another deletion operation
through the umbrella OSS that is not described in this section.
Users need to provide the primary key parameter of the TRX (TRXID) in the imported file
using the umbrella OSS when deleting a TRX. If the file is imported successfully, the TRX
and sub objects of the TRX will be deleted.
Restrictions on deleting TRXs
BCCH TRXs can be deleted only from deactivated cells.
If a cell has not been configured with a BCCH TRX, FH configuration for the cell may cause
unexpected results. Therefore, you are advised to create BCCH TRXs immediately when they
are deleted.
Delete the TRX involved in FH, users can perform the following operations:
If IBCA is disabled for the cell, users can import the file by performing operations in the
following subsessions:
 Subsession1: Disable FH for the cell.
 Subsession2: Delete the TRX and configure final FH data.
If IBCA is enabled for the cell and the TRX cannot be shut down for the activated cell, users
can import the file by performing operations in the following subsessions:
 Subsession1: Deactivate cells. Users need to deactivate the BTS if all the cells on the
BTS are deactivated.
 Subsession2: Delete the TRX and configure final FH data.
 Subsession3: Recover or set the active state.

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 24

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

In GBSS16.0 and later versions, users can perform the operations in one subsession. For
details, see section 2.6"Important Notes".

Following is an example file for deleting TRXs:

GTRX\01-Sample_Delete_GTRX.xml

2.4.10 Adjusting BTS Transmission Parameters

This section only describes transmission parameters of non-logical BTSs.
Users need to deactivate BTSs before performing some of the following operations over
interfaces on the BSC. To reduce risks brought by automatic BTS deactivation, users must
deactivate BTSs using the umbrella OSS unless BTSs are required to be automatically
deactivated by the CME in a specified situation.
2. Modifying basic BTS parameters
Users can adjust basic parameters of the BTS by using the umbrella OSS in this scenario,
including ABISBYPASSMODE, BTSDESC, BTSNAME, FLEXABISMODE, and
MPMODE.
Users need to provide the primary key information and new parameter values in the
imported file through the umbrella OSS when modifying parameters.
The CME performs the following operations to modify ABISBYPASSMODE,
FLEXABISMODE, or MPMODE:
− Automatically deactivate BTSs whose parameters you want to modify and BTSs
displayed in sub trees of these BTSs.
− Update ABISBYPASSMODE, FLEXABISMODE, or MPMODE.
− Recover the active state for each BTS.
Modifying BTSNAME and BTSDESC does not deactivate BTSs.
3. Adjusting BTS transmission parameters in TDM mode
Users can add, delete, and modify the secondary link (slave BTSCONNECT) by using
the umbrella OSS in this scenario. However, the primary link cannot be deleted or
modified individually over the NBI. It can be added when users create BTSs using the
umbrella OSS. All the links are deleted automatically when users delete BTSs using the
umbrella OSS.
Users need to provide BTSCONNECT data in the imported XML file through the
umbrella OSS when adjusting the secondary link. The CME automatically reallocates
information about a timeslot during the import.
4. Adjusting BTS transmission parameters in IP over E1 mode
Table 1.1 describes MOCs that users can adjust through the umbrella OSS in the scenario
of adjusting BTS transmission parameters in IP over E1 mode.

Table 1.1 MOCs adjusted by users

MOC Modifier

IPPATH A/D
IPRT A/D
PPPLNK A/D

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 25

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

MOC Modifier

MPRGP A/D
MPLNK A/D
BTSIP M
BTSIPRT A/D
BTSIPRTBIND A/M/D
BTSBFD A/D
BTSPPPLNK A/D
BTSMPGRP A/D
BTSMPLNK A/D
BTSCONNECT(slave) A/M/D

Do not import the file in this scenario if modifying the current bearer link leads to the disconnection
between BTSs and the BSC. The NMS does not support the automatic link setup over the NBI.
5. Adjusting the BTS transmission parameters in IP over FE/GE mode
Table 1.1 describes MOCs that users can adjust through the umbrella OSS in the scenario
of adjusting BTS transmission parameters in IP over FE/GE mode.

Table 1.1 MOCs adjusted by users

MOC Modifier

IPPATH A/D
IPRT A/D
ETHIP A/D
BTSIP M
BTSIPRT A/D
BTSIPRTBIND A/M/D
BTSBFD A/D
BTSETHPORT M
BTSESN A/M/D
BTSIPCLKPARA M

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 26

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

Do not import the file in this scenario if modifying the current bearer link leads to the disconnection
between BTSs and the BSC. The NMS does not support the automatic link setup over the NBI.
6. Adjusting MOCs related to timeslot data of BTSs
Users can manage timeslot data of BTSs through the umbrella OSS in this scenario,
including adding, deleting, and modifying BTSMONITORTS and setting
BTSIDLETS. The CME automatically reallocates the affected timeslot data.
Following are example files for adjusting transmission parameters:
− TransmissionModification\01-Sample_Update_BTS Basic.xml
− TransmissionModification\02-Sample_Update_TDM.xml
− TransmissionModification\03-Sample_Update_IPOE.xml
− TransmissionModification\04-Sample_Update_IPFE.xml
− TransmissionModification\05-Sample_Update_Timeslot.xml

2.5 Supplementary Information

2.5.1 Common Objects Under the Radio and Transmission Nodes
Both the Radio and Transmission nodes contain objects such as BTS, GCELL,
GCELLFREQ, and GTRX in the NRM. Users are expected to perform the following
operations under the Transmission node:
 Add, delete, and modify BTSs.
 Add and delete GCELL.
 Add, delete, and modify GCELLFREQ.
 Add and delete GTRX.
Creating BTSs, cells, and TRXs involves allocating and managing resources on the
transmission and device sides. Therefore, users are expected to create or delete BTSs, cells,
and TRXs under the Transmission node and perform the following operations under the
Radio node through the umbrella OSS:
 Modify GCELL.
 Add, delete, and modify GCELLFREQ.
 Modify GTRX.
Network optimization and planning for cells and TRXs belong to the radio domain. Therefore,
users need to adjust radio parameters under the Radio node through the umbrella OSS.

2.5.2 BTSBRD
The MOC BTSBRD on the BSC side is available only for non-logical BTSs.
BTSBRD that contains BTSAPMUBP, BTSDHEUBP, BTSDPMUBP, BTSFMUABP, or
sub object BTSDATUBP cannot be added or deleted on the NMS although the modifier of
BTSBRD is A/D. The board type (BT) includes 67:DATM_DATU, 72:DPMU, 74:DHEU,
93:FMU, 94:FMUA, 95:DTCU, 98:GATM, 114:PMU, 115:TCU, and 133:PMU_APMU.
Considering the complexity of correlations between parent and child objects, users need to
perform related operations on the device panel of the CME or use BTS templates to add
BTSBRD when creating BTSs.

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 27

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

2.6 Important Notes

In GBSS16.0 and later versions, BSC provides XML script interface and checks rule based on
the final data. Script execution sequence in MML script interface no longer exists. So in some
scenarios, NBI needs to operate the data through several subsessions, no longer exists. The
configuration can finish in one subsession.

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 28

Copyright © Huawei Technologies Co.,
Ltd.
iManager U2000-CME Northbound Interface Scenario
Description (GSM) FeaturesFeatures

A Acronyms and Abbreviations

C
CM configuration management
CME Configuration Management Express

G
GBSS GSM BSS

M
MO managed object
MOC managed object class
MOI managed object instance

N
NBI northbound interface
NRM network resource model

O
OSS operations support system

X
XML Extensible Markup Language

Issue 01 (2014-01-20) Huawei Proprietary and Confidential 29

Copyright © Huawei Technologies Co.,
Ltd.