SRLTE Optimization (ERAN11.1 0d1)

SingleRAN
Configuration Management Feature

Parameter Description
Issue 01
Date 2016-02-29
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2016. 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 (2016-02-29) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
SingleRAN
Configuration Management Feature Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
1.4 Differences Between Base Station Types....................................................................................................................... 2
2 Overview......................................................................................................................................... 3
3 Structure.......................................................................................................................................... 4
3.1 NE Configuration Management......................................................................................................................................6
3.1.1 Southbound Interface Overview.................................................................................................................................. 6
3.1.2 EMS Layer Description............................................................................................................................................... 7
3.2 Subnet Configuration Management................................................................................................................................7
3.2.1 Software System Structure.......................................................................................................................................... 7
3.2.2 Functions..................................................................................................................................................................... 8
3.2.3 Configuration Data Flow............................................................................................................................................. 9
3.2.4 Northbound Interface.................................................................................................................................................11
3.2.5 Typical Application Scenarios...................................................................................................................................12
3.2.6 Configuration Flow Example.................................................................................................................................... 16
4 Configuration Security............................................................................................................... 18
5 Related Feature.............................................................................................................................19
6 Network Impact........................................................................................................................... 20
7 Parameters..................................................................................................................................... 21
8 Counters........................................................................................................................................ 22
9 Glossary......................................................................................................................................... 23
10 Reference Documents............................................................................................................... 24
Issue 01 (2016-02-29) Huawei Proprietary and Confidential ii

SingleRAN
Configuration Management Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes configuration management, including its implementation principles
and basic architecture.
This document covers the following features:
l MRFD-210301 Configuration Management

l LBFD-004007 Configuration Management
l TDLBFD-004007 Configuration Management
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
and "eNodeB" refers to LTE FDD eNodeB.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein

l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes
Issue 01 (2016-02-29) Huawei Proprietary and Confidential 1

SingleRAN
Configuration Management Feature Parameter Description 1 About This Document
SRAN11.1 01 (2016-02-29)
This issue does not include any changes.
1.4 Differences Between Base Station Types

The features described in this document are implemented in the same way on macro, micro,
and LampSite base stations.

SingleRAN
Configuration Management Feature Parameter Description 2 Overview
2 Overview
Configuration management allows you to configure network resources by using configuration

data in network devices. This controls the running status of network devices. You can
configure network resources, and monitor and control configuration parameters for network
devices. This is to ensure that telecom operators can provide effective network operation and
maintenance (O&M).
Configuration management is required on the entire network O&M cycle.
l During network deployment, configuration management allows you to initialize
configuration data, and install and set up network devices.
l During network adjustment and optimization, configuration management allows you to
configure parameters for new features, and modify parameter settings for scenarios such
as network capacity expansion, transmission adjustment, and wireless network
performance optimization.
For example, add, delete, or modify network parameters to maintain the quality of
service (QoS) of a network during network optimization. You can modify parameters for
an NE or for the entire network.
l During routine O&M, configuration management allows you to monitor and modify
network parameters.
Before you add, delete, or modify a parameter, ensure that your operation will have minimal
impact on services. To achieve this, configuration management provides the following
capabilities:
l Security management
Configuration management allows you to control access permission to network
resources.
l Data validity check
Configuration management allows you to add, delete or modify a parameter under
constraints on logical data, to ensure that the parameter is correct and valid. In an end-to-
end configuration data scheme, ensure data integrity and consistency when you modify
network parameters.

SingleRAN
Configuration Management Feature Parameter Description 3 Structure
3 Structure
Radio access networks (RANs) are divided into three layers:

l NE layer (NEL)
l Element management layer (EML)
l Network management layer (NML)
Accordingly, the configuration management architecture consists of three layers: NE
configuration, subnet configuration management, and network configuration management.
l NE configuration
Huawei provides various clients that support man-machine language (MML) interfaces,
including the web-based LMT (Web LMT) and MML command-line interface integrated
with the U2000. Such clients allow you to run MML scripts to fine-tune NE
configuration parameters. You can also modify NE configuration parameters on the
Configuration Management Express (CME) through the southbound interface.
l Subnet configuration management
Huawei provides the CME, a professional configuration solution, to perform EMS-layer
configuration management. The CME helps you centrally manage a SingleRAN
network. The CME provides scenario-based templates and foolproof wizards, which
allow you to efficiently migrate base stations, adjust networks, and check for consistency
between parameter settings. The CME also provides the northbound interface (Itf-N) for
integration with upper-layer NEs. The CME is recommended for configuration
operations, rather than the Web LMT.
l Network configuration management
NMS-layer configuration management is a configuration solution for the entire network.
The northbound interface allows EMSs from different vendors to be connected to the
telecom operator's NMS. Huawei CME is connected to the NMS through the northbound
interface. The telecom operator usually has a comprehensive evaluation system in the
NMS for parameter planning. After the planning system determines the parameters to be
optimized, you can send the modified parameter information to the CME through the
northbound interface. The CME then modifies the parameters for NEs. This significantly
improves end-to-end O&M efficiency and reduces the operating expense (OPEX).
Figure 3-1 shows the configuration management architecture.

SingleRAN
Figure 3-1 Configuration management architecture

SingleRAN
3.1 NE Configuration Management
3.1.1 Southbound Interface Overview

The CME is connected to NEs through a southbound interface, which is a private interface.
After generating configuration scripts, the CME sends these configuration scripts to NEs
through the southbound interface. Configuration scripts take effect on NEs and configuration
data is modified. The southbound interface supports two configuration script formats: MML
and XML.
The configuration capability of the southbound interface is determined by that of NEs. Figure
3-2 shows how an NE processes a configuration script.
Figure 3-2 NE processing a configuration script
1. The script parser in the configuration management module parses the script and performs
database operations according to the instructions in the script, as shown in steps 1 and 2
of Figure 3-2.
2. The configuration management module starts the data validity check, as shown in step 3
of Figure 3-2.
– If the data validity check fails, the configuration management module rolls the data
back by using the database transaction control mechanism and stops data
processing.
– If the data validity check succeeds, the configuration management module instructs
the application module, such as the NodeB Application Part (NBAP) or Radio
Resources (RR), to change the data. The application module adjusts services

SingleRAN
according to data changes. Then, the application module sends the processed result
to the configuration management module, as shown in steps 4 and 5 of Figure 3-2.
3. The configuration management module creates a script execution report according to the
processed result sent by the application module and sends the report to the EMS layer
through the southbound interface, as shown in step 6 of Figure 3-2.
NOTE
In normal cases, an NE processing system is designed on a module basis. Therefore, the

configuration management module and application processing module may be located in different
boards or modules. These two modules interact with each other by using the lower-layer
communication mechanism.
3.1.2 EMS Layer Description

The EMS layer includes the Web LMT, U2000, and CME. Their configuration capabilities are
as follows:
l The Web LMT is a configuration tool for a single NE. Users can issue a single or
multiple MML commands on the Web LMT to configure the NE.
l The U2000 client integrates the Web LMT functions.
l The CME allows users to concurrently configure multiple NEs. As a configuration tool
on the EMS layer, the CME configures NE data through the southbound interface.
Configuration parameters on NEs can be modified at the same time. You are advised to
use the CME to configure data.
NOTE
MML interfaces are located on the NE layer. Therefore, the configuration commands sent by a client
(Web LMT, U2000, or CME) that supports MML interfaces take effect only on an NE. The
configuration parameters for another NE cannot be modified at the same time. When modifying NE
parameters by using such a client, you need to manually modify the parameters on all related NEs.
3.2 Subnet Configuration Management

The EMS-layer configuration solution CME is a standalone service that is set up on the
U2000 platform. The CME performs the following:
l Configures network-level parameters and ensures the integrity and consistency of
network-level parameters on NEs.
l Manages products working in multiple modes, including Global System for Mobile
Communications (GSM), Universal Mobile Telecommunication System (UMTS), and
Long Term Evolution (LTE). Data can be interchanged between these products (NEs).
l Supports concurrent operations of multiple users.
l Connects to the telecom operator's operations support system (OSS) through the
northbound interface.
3.2.1 Software System Structure

Figure 3-3 shows the CME software structure.

SingleRAN
Figure 3-3 CME software structure
The CME has a client/server (C/S) architecture. You can use the CME client to perform O&M
tasks related to configuration on a graphical user interface (GUI). The CME provides wizards
to guide you step by step through complex operations in special scenarios, for example, base
station deployment or migration.
The CME server allows you to manage configuration data for all NEs on the entire network.
Complex logical computation is performed based on these NE data to process configuration
data. The CME server is set up on the U2000 platform. In actual application, the CME has
independent logical database space in the U2000 database where it stores and computes data.
3.2.2 Functions
Data Shared Between NEs of Different RATs
The database design allows different types of NEs to have their own logical database space.
NEs of different radio access technologies (RATs), however, can share data. The CME
processes data for the entire network, therefore maintaining data consistency network-wide.

SingleRAN
Highly Reliable O&M

To facilitate concurrent operations by multiple users and provide highly reliable O&M, the
CME provides current and planned data areas.
The current data area mirrors the configuration data of all NEs. When the configuration data
changes, the CME synchronizes the changed data to the current data area by using the
attribute value change (AVC) notification mechanism. This ensures that the configuration data
in the current data is synchronized with the NE data in the network. The configuration data in
the current data area is read-only. If you need to modify the data, you must create the
corresponding planned data area. When you create a planned data area, the CME copies the
data from the current data area to the planned data area to protect data integrity. Therefore, the
O&M tasks are carried out by performing configuration operations based on the planned data
area.
Planned data areas are isolated from each other. Different users can concurrently perform
operations for different configuration tasks based on different planned data areas. In addition,
the configuration operations in the planned areas do not affect the live network as the planned
areas are "offline".
Data Validation Mechanism

Correct and consistent configuration data is the basis for high performance of network
devices. The CME provides the data validation mechanism for configuration operations
(including adding, deleting and modifying data) based on the planned area. This ensures that
data is logically correct. When you complete configuration operations, the CME generates
incremental scripts according to your operations. The CME also provides the script executor,
which controls script activation on NEs. The script executor supports multiple activation
methods based on configuration application scenarios, such as break on failure and best effort
activation, helping monitor and manage activation processes.
The CME can manage NEs that are of the same type but running different versions. The
multi-version scheduling module loads NE versions and locates the version that you need.
The CME server provides the XML-oriented bulk CM interface that is based on Common
Object Request Broker Architecture (CORBA) to support multiple client access. The standard
CORBA-related protocol messages specified in 3GPP are terminated at the CME server.
3.2.3 Configuration Data Flow

Uplink and downlink data interchange in the EMS configuration solution is a closed-loop data
flow. The data flow in the CME-based EMS configuration solution is shown in Figure 3-4.

SingleRAN
Figure 3-4 Data flow in the CME-based EMS configuration solution
The data flow in Figure 3-4 is as follows:

1. The CME uses the data synchronization function to extract the NE data from the live
network to the current data area. The mirrored NE configuration data is generated.
2. The CME creates multiple planned data areas based on the current data area. Different
users can concurrently perform configuration operations based on different planned data
areas. These planned data areas are isolated and do not affect each other.
3. Users perform configuration operations based on planned data areas. The configuration
data can be imported from an Excel file, or imported from an XML file through the
northbound interface, or configured by using the GUI. After the configuration is
complete, users can extract a data modification report and verify that the data has been
modified.
NOTE
The modified data is highlighted in the CME GUI based on the data modification report.
4. CME provides the script generation mechanism. CME generates incremental
configuration scripts and fallback scripts according to user operations.
5. When the scripts are activated on an NE, modified configuration data takes effect on the
NE.
6. The NE reports an AVC notification to the CME. The CME updates the data in the
current data area according to a preset policy. This ensures that the data in the current
data area is synchronized with the data on the live network.

SingleRAN
NOTE
Scripts from different planned data areas can enable an NE to send an AVC notification. If you use
the Web LMT or U2000 to perform operations on the NE, the NE can also send an AVC
notification.
3.2.4 Northbound Interface

The CME supports batch configuration management of the northbound interface based on
XML files. Through the northbound interface, the CME is integrated to the telecom operator's
NMS. This increases end-to-end configuration efficiency.
The telecom operator's NMS has its own planning system that consists of transmission and
wireless parameter planning systems. During routine O&M, the planning system determines
the network configuration parameters to be optimized based on the monitoring and analysis of
network performance. The planning system sends a request to the CME to modify parameters
through the northbound interface. The CME analyzes XML files for batch configuration
management based on the planned data areas, modifies the data, performs the data validity
check, and generates incremental configuration scripts. After the configuration scripts are
activated on an NE, the modified parameters take effect on the NE. The NE performance is
optimized.
Figure 3-5 shows the configuration process through the northbound interface.
Figure 3-5 Configuration process through the northbound interface
The northbound interface design is in accordance with the following rules:

SingleRAN
l The uplink and downlink data uses the XML file interface to support batch data
configuration through the northbound interface.
l The northbound interface can be automatically controlled based on CORBA. This
complies with 3GPP Release 6.
l XML files can be manually imported by using the CME client.
l The northbound interface supports all configuration scenarios, including deploying base
stations, adjusting transmission, optimizing radio parameters, adjusting neighbor
relationship, and migrating base stations.
l The CME provides only basic functions for modifying parameters in batches, but it
cannot provide intelligent and combined service operations. For example, neighbor
relationship is dynamically adjusted by the configuration inventory management system
of the NMS during migration.
l The northbound interface supports concurrent operations for multiple northbound
interface managers. In RAN sharing scenarios, the northbound interface also supports
permission control by telecom operators.
l The northbound interface of the earlier version also allows new NEs to be managed by
the NMS.
NOTE
Interconnection modes over the northbound interface depend on the telecom operator's NMS. Therefore,
the CME must be adaptable to the telecom operator's NMS.
Northbound data models are modified based on the northbound parameter disuse mechanism,
as shown in Figure 3-6.
Figure 3-6 also shows the status of parameters to be disused in different versions.
Figure 3-6 Northbound parameter disuse mechanism
3.2.5 Typical Application Scenarios
Network Planning
You need to plan for a network before you deploy, adjust, or optimize the network. The CME
supports data imported from the following two sources:
l Data calculated by using a network planning tool
l Data negotiated with the telecom operator
After obtaining planned data, save the data in XLS summary data files provided by the CME
for future configuration.

SingleRAN
Network Deployment
In this scenario, configure data for newly deployed NEs (base station controllers or base
stations) for a new site. The CME provides flexible data configuration methods for a new site.
Choose one of the following methods based on site requirements:
l Configuring data by using the GUI
This method is applicable to a new NE (base station controller or base station), or
adjustment to some data that is configured for NEs in batches. To improve efficiency in
configuring data for base stations, the CME provides default templates for different base
station types and cells. You can customize these templates to quickly create base stations.
l Importing data from data planning files
This method is applicable when configuring data for base stations that are created in
batches and for different interfaces on controllers. When creating base stations in
batches, you can also use default or user-defined templates to simplify the process of
configuring the same data for base stations or cells. If the base stations or cells have
different configuration data, the CME provides a customization tool for XLS summary
data files. You can customize the planning summary data files based on site
requirements, and import these data files to create base stations in batches.
l Importing data from XML files through the northbound interface
This method is applicable after the CME is connected to the 3GPP Release 6-compliant
northbound interface of the telecom operator's NMS. After the planning system of the
NMS completes network planning, the planning system generates incremental
configuration scripts in XML format. The CME imports the XML files to complete data
configuration.
After data configuration is completed, the CME exports configuration data files (in MML or
XML format) for each NE. You can use the script executor provided by the CME to remotely
send the configuration data files to each NE through the U2000 and activate them to remotely
perform centralized data configuration for network deployment. You can also use the
northbound interface to send a request to the CME to activate configuration data scripts for
NEs.
Network Adjustment
You need to adjust hardware resources if services are not distributed evenly in a network.
Unevenly distributed services are caused by unevenly distributed resources. The network
adjustment function addresses this problem. Network adjustment involves increasing or
decreasing network capacity and reconstructing networks. Typical scenarios are as follows:
l Device capacity expansion: For example, add a service processing board or interface
board for an existing controller or base station.
l Transmission capacity expansion: For example, add an inverse multiplexing over ATM
(IMA) link to an IMA group for an existing base station, or adjust the bandwidth of a
transmission link.
l Cell or carrier capacity expansion: For example, change the configuration of NodeB
from 3 x 1 to 3 x 2.
l Transmission reconstruction or adjustment: For example, change ATM to ATM/IP dual
stack for an Iub interface and reconfigure NodeB in an RNC pool from dual homing to
single homing.
The CME provides multiple configuration wizards or one-click configuration for the
preceding typical scenarios. Prepare the data of planning that you have adjusted in an Excel

SingleRAN
template and import the data to the planned data area by using the CME configuration wizard.
The CME can export incremental configuration scripts in appropriate format for NEs.
NOTE
Some scripts take effect only when services in the live network are interrupted or a base station is reset.
When this occurs, the CME displays a message before sending scripts. If scripts take effect only when a
base station is reset, the CME automatically triggers a base station reset after sending the scripts
successfully.
Base Station Migration

During site network operation, you need to migrate base stations in the case of network
planning, load balancing, and capacity expansion. Base station migration is a complex
network adjustment task.
The typical scenario for reparenting base station between controllers is as follows: If areas
managed by controllers are unevenly planned or the load is unbalanced, you need to replan
base stations managed by each controller and reparent some base stations managed by a
controller to another controller. By using this method, the network load is balanced. The CME
supports the ability to reparent base stations between two controllers that support the same
version.
To ensure that configuration data is smoothly migrated with a base station and that the
network performance remains unchanged, perform the following operations during migration:
1. Data planning
Plan the transmission configuration data for migration. Prepare cell-related data if you
reparent base stations between controllers and fill in a data planning file according to
planned data.
2. Script preparation
Import the data planning file that you have finished by using the CME migration wizard.
This wizard is used to perform the following operations:
l Smoothly migrate the data for base stations from source controllers to destination
controllers.
l Recreate the transmission-layer data for destination controllers. The data comes from
planned data.
l Smoothly migrate the cell data from source controllers to destination controllers. Some
data comes from planned data based on site requirements, for example, location area
adjustment.
l Smoothly migrate neighbor relationships. The neighbor relationship data before
migration must be inherited. This is a complex operation that must be performed on the
entire network. The network sometimes consists of 2G and 3G devices.
After the data is configured, the CME exports configuration data files (in MML or XML
format) for each NE. You can use the script executor provided by the CME to remotely send
and activate the configuration data files to each NE through the U2000.
NOTE
You are advised to activate the reparenting scripts on the destination controller first. After the
commissioning is successful, activate the reparenting scripts on the source controller. This ensures that
the data is restored quickly when a fault occurs during the reparenting.

SingleRAN
Network Optimization
You need to adjust and optimize the current network parameters so that the network can
provide better network services. Network optimization is applicable to radio-layer parameter
adjustment. This is the difference between network optimization and network adjustment. The
CME supports the following typical tasks related to network optimization:
l Adjust frequencies or scrambling codes for cells in batches.
l Adjust data for neighboring cells or their booster amplifiers (BAs) in batches.
l Adjust algorithm parameters for cells, carriers, and channels in batches.
l Change configurations for some features. For example, reconstruct a cell that uses high
speed packet access (HSPA), and change telecom operators of cells from exclusive to
multioperator core network (MOCN).
The CME provides the following methods to configure data in batches:
l Importing data from data planning files
Export a summary data file from the CME, reconfigure the data in the file, and import
the file into the CME to quickly adjust data in batches. This method is applicable when
you need to configure different values for multiple objects. The CME provides multiple
data planning files for different network optimization tasks.
l Modifying data in batches by using the wizard
Select some or all of the configuration parameters for an object as a reference and apply
these parameters to another object. This method is applicable when you need to
configure parameters to the same values for a single type of objects.
l Configuring data by using templates
Select some or all of the configuration parameters in a template as reference and apply
these parameters to the NEs on the CME. This improves data reconfiguration efficiency.
This method is applicable when you need to configure different values for different types
of objects.
l Reconfiguring data for some service features
The CME provides a configuration wizard that supports one-click configuration for an
object.
l Importing data from XML files through the northbound interface
This method is applicable after the CME is connected to the 3GPP R9-compliant NBI of
the telecom operator's NMS.
After the data is configured, the CME exports configuration data files (in MML or XML
format) for each NE. You can use the script executor provided by the CME to remotely send
and activate the configuration data files to each NE through the U2000.
Configuration Parameter Management

Configuration parameter management allows you to browse, check, and analyze configuration
data on the CME. For example, compare data and create a data report. This function does not
affect ongoing services because it does not modify data and apply configuration settings to
NEs. Configuration parameter management supports the following functions:
l Global data check
The network has a large amount of data and the correlations between configuration
objects are complex. The CME checks the integrity, redundancy, and consistency of

SingleRAN
configuration data on the CME. If there is an error, an error report is generated. In

addition, the CME automatically recovers certain data according to check results to
ensure valid data configuration.
l Radio-layer algorithm parameter comparison
During the initial phase of network construction, algorithm parameters use the default
baseline data of the system. During network maintenance and optimization, you can
modify certain algorithm parameters according to network performance. You can
compare the actual values of the algorithm parameters for the current controller or cell
with the default values or configuration baseline data through the CME. The CME
highlights the added, modified, and deleted configuration data. This facilitates
subsequent optimization and reconfiguration.
To help you quickly select the parameters to be compared, the CME provides default
parameter sets (parameter filters) according to different NEs and versions. Select the
filter and you can quickly filter out your required parameter list. You can also customize
parameter filters.
l Panoramic data browsing
The data browsing and searching functions help you effectively locate required
information and prepare for the next step in planning and adjustment. The CME allows
you to browse panoramic data and search for data. You can browse the configuration
information for different objects. For example, the port usage of each interface board, or
the number of neighbor relationships configured for each cell. You can also define search
criteria to search for required objects.
l Parameter auditing
The CME allows you to compare NE configuration parameters at different time to learn
configuration data changes during this period. It also allows you to export NE
configuration parameters at a specified time.
l Report configuration
The CME provides configuration reports for various scenarios during network
maintenance. You can view data of multiple NEs of different versions on the live
network by using configuration reports. You can also use configuration reports to collect
statistics on the entire network. Configuration reports can be saved in multiple formats.
3.2.6 Configuration Flow Example

Figure 3-7 shows an example using the configuration flow for creating a base station.

SingleRAN
Figure 3-7 Configuration flow for creating a base station
Step 1 The CME synchronizes data with the live network, as shown in steps 1 through 4 of Figure
3-7.
The CME synchronizes NE configuration data through the southbound interface and the NMS
synchronizes the configuration data in the CME through the northbound interface.
Step 2 The NMS planning system starts configuration data planning, as shown in step 5 of Figure
3-7.
Step 3 The NMS delivers planned configuration data through the northbound interface for the
configuration data to take effect on the live network, as shown in steps 6 through 13 of Figure
3-7.
----End

SingleRAN
Configuration Management Feature Parameter Description 4 Configuration Security
4 Configuration Security
In configuration management, a series of security measures are provided to protect

configuration data. For details, see OM Security Feature Parameter Description.

SingleRAN
Configuration Management Feature Parameter Description 5 Related Feature
5 Related Feature
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None

SingleRAN
Configuration Management Feature Parameter Description 6 Network Impact
6 Network Impact
Network Performance
No impact.
System Capacity
No impact.

SingleRAN
Configuration Management Feature Parameter Description 7 Parameters
7 Parameters
There are no specific parameters associated with this feature.

SingleRAN
Configuration Management Feature Parameter Description 8 Counters
8 Counters
There are no specific counters associated with this feature.

SingleRAN
Configuration Management Feature Parameter Description 9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

SingleRAN
Configuration Management Feature Parameter Description 10 Reference Documents
10 Reference Documents
None


SRLTE Optimization (ERAN11.1 0d1)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SRLTE Optimization (ERAN11.1 0d1)

Uploaded by

Copyright:

Available Formats

SingleRAN

Configuration Management Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2016-02-29) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

Issue 01 (2016-02-29) Huawei Proprietary and Confidential ii

1 About This Document

This document covers the following features:

l MRFD-210301 Configuration Management

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 1

1.4 Differences Between Base Station Types

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 2

Configuration management allows you to configure network resources by using configuration

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 3

Radio access networks (RANs) are divided into three layers:

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 4

Figure 3-1 Configuration management architecture

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 5

3.1 NE Configuration Management

3.1.1 Southbound Interface Overview

Figure 3-2 NE processing a configuration script

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 6

In normal cases, an NE processing system is designed on a module basis. Therefore, the

3.1.2 EMS Layer Description

3.2 Subnet Configuration Management

3.2.1 Software System Structure

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 7

Figure 3-3 CME software structure

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 8

Highly Reliable O&M

Data Validation Mechanism

3.2.3 Configuration Data Flow

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 9

Figure 3-4 Data flow in the CME-based EMS configuration solution

The data flow in Figure 3-4 is as follows:

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 10

3.2.4 Northbound Interface

Figure 3-5 Configuration process through the northbound interface

The northbound interface design is in accordance with the following rules:

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 11

Figure 3-6 Northbound parameter disuse mechanism

3.2.5 Typical Application Scenarios

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 12

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 13

Base Station Migration

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 14

Configuration Parameter Management

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 15

configuration data on the CME. If there is an error, an error report is generated. In

3.2.6 Configuration Flow Example

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 16

Figure 3-7 Configuration flow for creating a base station

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 17

In configuration management, a series of security measures are provided to protect

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 18

Mutually Exclusive Features

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 19

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 20