Beruflich Dokumente
Kultur Dokumente
Issue
01
Date
2014-01-20
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.
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2014-01-20)
Abstract
This document describes the technical specifications of the configuration scenarios that the
U2000 CM NBI supports on a UMTS 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)
ii
Contents
Contents
About This Document.......................................................................ii
1 Introduction.................................................................................4
2 Features....................................................................................... 5
2.1 Network Resource Model..................................................................................................................................5
2.1.1 Managed Object Model............................................................................................................................5
2.1.2 Parameter List...........................................................................................................................................5
2.2 Radio Parameter Configuration Scenarios.........................................................................................................5
2.2.1 Cell Creation.............................................................................................................................................6
2.2.2 Cell Deletion.............................................................................................................................................9
2.2.3 Cell Data Modification...........................................................................................................................10
2.2.4 Neighbor Relationship Adjustment.........................................................................................................11
2.3 Transmission Parameter Configuration Scenarios...........................................................................................15
2.3.1 NodeB Creation......................................................................................................................................15
2.3.2 NodeB Deletion......................................................................................................................................16
2.3.3 Iub Interface Data Modification.............................................................................................................16
Issue 01 (2014-01-20)
iii
1 Introduction
Introduction
Issue 01 (2014-01-20)
Features
the RNC side and that used on the NodeB side are delivered separately as XML files through
the NBI.
A logical cell (UCELL) contains information about a cell that users want to create and is
served by the current RNC. CELLID uniquely identifies a cell within a radio network system.
During the creation of a logical cell, subobjects, such as channels and algorithm parameters,
of the cell must be provided to support certain services. For example, if users want to create a
cell that supports HSDPA services, they must configure a subobject, UCELLHSDPA, for the
cell.
Issue 01 (2014-01-20)
Users can import data to create a cell and then configure neighbor relationships repeatedly until they
have created all desired cells. Alternatively, they can import data to create all desired cells and then
configure neighbor relationships at a time. For example, if users want to create U2GNCELL,
UINTERFREQNCELL, UINTRAFREQNCELL, and ULTENCELL, they can centrally configure
neighbor relationships through the NBI after they have created all desired cells and external cells.
The cell subobject list varies with NE versions. Users can obtain the latest cell subobject list from
the MOM document.
When users create a cell, they do not need to include all subobjects of the cell in imported files. This
is because subobjects for features that users do not want to use are not required. However, the
following subobjects must be provided so that users can properly activate the cell:
UCELLCAC
UCELLLDB
UCELLPUC
UCELLRLPWR
UCELLALGOSWITCH
UCELLACCESSSTRICT
UCELLSELRESEL
UCELLMEAS
UCHPWROFFSET
UCELLSIBSWITCH
UCELLRLACTTIME
UCELLOLC
UCELLLDM
UCELLLDR
UCELLHCS
UPSCH
USSCH
UPCCPCH
UPCPICH
UBCH
USCCPCH
USCCPCHTFCS
UPCH
UPICH
UFACH
UFACHDYNTFS
UPRACHBASIC
UPRACHTFC
UPRACHSLOTFORMAT
UPRACHASC
UPRACHACTOASCMAP
UAICH
URACH
URACHDYNTFS
UCELLURA
UPCHDYNTFS
Cell Template
A large number of associated MOCs and parameters are used when users create a cell. This
brings challenges to the umbrella OSS.
Such MOCs and parameters are divided into the following categories based on the data
similarities between cells:
Based on the preceding information, the U2000 CM NBI provides a fast copy and
modification function for users to rapidly create a cell using a cell template. Each cell
template represents a type of typical cell configuration data. When users import files to create
a logical cell through the NBI, they only need to provide the planned parameters of the cell
and the used cell template. Then, users can copy cell configuration data from the cell template
and modify the planned parameters based on files imported over the U2000 CM NBI. This
simplifies user operations for creating a cell through the umbrella OSS.
A series of default cell templates are provided along with the release of a Configuration
Management Express (CME) version. Users are not allowed to delete these templates.
However, they can create and delete customized cell templates as required. For details about
the management of customized templates, users can see CME Online Help.
Creating a Cell
The CME allows users to create a cell using either of the following methods:
Issue 01 (2014-01-20)
If users create a logical cell using a cell template through the NBI, they only need to
include basic parameters of the cell in imported files, and the NBI then automatically
inherits all parameters in the template. This simplifies user operations for collecting
files that they want to import and improves work efficiency. Information about the
cell template is provided for the NBI through the CELLTEMPLATE (include
parameters CELLID and NAME) object.
Following is an example file for creating a logical cell by using a cell template:
01_Sample_Create_LogicalCELL_With_Template.xml
The URA information (UCELLURA) of the cell is not included in the cell template. Users need to
configure UCELLURA when they create the cell. This ensures that the cell can be properly activated.
As shown in the preceding example, when creating a cell based on a template, users have to set
Operation for the cell to CreateCellWithTemplate, but do not have to set modifier for all subobjects
of the cell. The CME takes this as a creation scenario by default.
Information about the used cell template is provided to the NBI through the TEMPLATENAME
parameter of the ULOCELL object.
To properly activate a new cell, users must include the minimum object set for the cell in imported files.
Following is an example file for creating a logical cell without using a cell template:
02_Sample_Create_LogicalCELL_Without_Template.xml
Activating a Cell
Only active cells can provide network access services. After users create a logical cell and a
local cell, they need activate the cell by properly setting the ACTSTATUS parameter of its
logical cell.
Issue 01 (2014-01-20)
Following are example files for activating and deactivating a cell, respectively:
03_Sample_ACT_CELL.xml
03_Sample_DEA_CELL.xml
A prerequisite for users to delete external cells is that all neighbor relationships involving the external
cells have been deleted.
Figure 1.1 and Figure 1.2 show the process for users to handle neighbor relationships and
perform operations over the NBI when they delete data about CELL1 as maintained on
RNC1.
Figure 1.1
Issue 01 (2014-01-20)
Figure 1.2
Following is an example file for deleting a logical cell on the RNC side:
03_Sample_Delete_LogicalCELL.xml
Common parameters
Associated parameters
Common Parameter
Common parameters exist only on cells instead of their external cells, and therefore
modification of common parameters affects only cells instead of their external cells. Most cell
parameters are common parameters.
Following is an example file for modifying a common parameter:
Issue 01 (2014-01-20)
10
06_Sample_Update_CELLACINFO.xml
Associated Parameter
Associated parameters exist on cells and their external cells. After users modify an associated
parameter of a cell, they must also modify the related parameters of the cell's external cells to
ensure data consistency.
For example, if users modify the PSCRAMBCODEC parameter of a cell, they must also
modify the related parameters of its external cells (UEXT3GCELL) served by other RNCs; if
they modify the LAC, SAC, or RAC parameter of a cell, they must also modify the related
parameters of its external cells (UEXT3GCELL) served by other RNCs. If users do not
modify parameters of external cells served by other RNCs synchronously after they modify a
parameter of a cell, data of the cell and that of the external cells becomes inconsistent.
Neighbor relationship between a UMTS cell and its external GSM cell
Neighbor relationship between a UMTS cell and its external LTE cell
Issue 01 (2014-01-20)
11
Figure 1.1
Following describes external cells involved in neighbor relationship adjustment and the
methods for configuring different types of neighbor relationships:
Issue 01 (2014-01-20)
12
Issue 01 (2014-01-20)
13
Issue 01 (2014-01-20)
14
On an actual network, NodeB configuration data can be divided into a limited number of
categories, and NodeBs of the same type are featured with similar configuration data.
Based on the preceding information, the U2000 CM NBI provides a fast copy and
modification function for users to rapidly create a NodeB using a template. Each template
represents a type of typical NodeB configuration data. When users import files to create a
NodeB through the NBI, they only need to provide the planned parameters of the NodeB and
the used template. Then, users can copy NodeB configuration data from the template and
modify the planned parameters based on files imported over the U2000 CM NBI. This
simplifies user operations for creating a NodeB through the umbrella OSS.
Configuration of device parameters and that of transmission parameters are closely related,
whereas configuration of radio parameters is decoupled from that of device and transmission
parameters. In addition, radio parameters and device and transmission parameters are usually
planned and configured by engineers from different departments through different umbrella
OSS tools. Therefore, the U2000 CM NBI divides the templates used for NodeB creation into
the following categories:
The U2000 CM NBI allows users to create a NodeB only by using a template. When users
attempt to create a NodeB, they must specify NodeB and radio templates in imported files
through the umbrella OSS.
Issue 01 (2014-01-20)
15
The CME provides a template management function for users to manage NodeB and radio
templates. For details, users can see the CME product documentation.
When users create a NodeB, they must include transmission parameters and related radio
parameters in one XML file. They can include neighbor relationship configuration data in the
same XML file or in a separate XML file.
Following are example files for creating various types of logic NodeBs:
01-Sample_Create_ATM_IMAGRP.xml
02-Sample_Create_ATM_OPT.xml
03-Sample_Create_ATM_ATMLOGICPORT.xml
04-Sample_Create_IP_ETH.xml
05-Sample_Create_IP_IPLOGICPORT.xml
06-Sample_Create_DUAL_OPT_ETH.xml
01-Sample_Create_NODEB.xml
Creation of a physical NodeB through the NBI is complicated because it involves file validity
check, NodeB business rules check, NodeB data integrity check, and the generation of NodeB
configuration data files. To avoid long waiting, users are advised to include data of less than
50 NodeBs in one XML file.
Two fields related to the NE name are involved in example files for creating a NodeB: neid in
the NE and NODEBFUNCTIONNAME in the NODEBFUNCTION. Users are advised to
keep values of these two fields consistent. If they are inconsistent, the NBI uses neid. After a
NodeB is created successfully, the name displayed in the general view is the value of neid.
As shown in the preceding example, when creating a NodeB based on a template, users have
to set Operation for the NodeB to CreateSite, but do not have to set modifier for all
subobjects of the NodeB. The CME takes this as a creation scenario by default.
productversion is the version of a base station, it should be set when creating a base
station. And the parameter NENAME in MOC NE, PRODUCTTYPE in MOC NODE should
be set when creating a base station.
Issue 01 (2014-01-20)
16
B
BPU
C
CM
configuration management
CME
L
LA
location area
M
MOC
MOM
N
NBI
northbound interface
NRM
O
OSS
Issue 01 (2014-01-20)
17
R
RF
radio frequency
X
XML
Issue 01 (2014-01-20)
18