ISSUE1.1
HUAWEI Confidential
www.huawei.com
HUAWEI Confidential
Page 2
HUAWEI Confidential
Page 3
HUAWEI Confidential
Page 4
HUAWEI Confidential
Page 5
Quality Assurance
Scenario/workflow optimization
Planning in advance
Concurrent operation
Frequency replanning
workflow
Swapping workflow
Page 6
HUAWEI Confidential
Software Platform
Supporting Sun mini-server +
Solaris + Sybase
Supporting HP/ATAE miniserver + Linux + Oracle
Sharing the platform with the
M2000
Providing a single-server
version
Providing a Chinese version
Distributed mode
High availability (HA)
Security
Reliability
Component-based release
Value-Added Service
MBTS integrated configuration
RRU resource allocation
BTS swapping crossing NEs
and versions
Frequency replanning on the
entire network
Site deployment in batches
Adjustment of neighboring cell
relations
Modification of algorithm
parameters in batches
3GPP northbound
configuration
Consistency check
Panoramic view
NE Access
RAN 13.0/12.0/11.0 / 11.1
GBSS 13.0/12.0/9.0/8.x
LTE 2.0/ LTE 2.1
Page 7
HUAWEI Confidential
GUI Enhancement
The TOPO site deployment, BTS networking, TRXs of each cell, and timeslot allocation can be viewed in GUI mode on the LMT of the BSC6000.
Therefore, the BTS configuration and resource allocation can be displayed clearly.
Cascade,
multi-link
Traditional site deployment wizard
HUAWEI Confidential
Page 8
Ring topology
Security
The CME provides the function of data check on the entire network before data is activated, including the
check for completeness, redundancy, and consistency.
The CME supports the data rollback in key scenarios.
The CME supports the parameter comparison. That is, the CME compares the data that has taken effect and
the template to check whether data configuration is correct.
HUAWEI Confidential
Page 9
HUAWEI Confidential
Page 10
HUAWEI Confidential
Page 11
GBTS
NodeB
HUAWEI Confidential
Page 12
Hardware platform
Sun
HP
ATAE
Page 13
HUAWEI Confidential
Citrix networking
solution
Page 14
HUAWEI Confidential
CME Client
MBSC/MBTS
Business
GBSS
Business
WRAN
Business
LTE
Business
Client Framework
Corba
N-Itf(Corba)
CME Adapter
iMAP Platform
M2K Mediation
DB Link
M2000
Delivering configuration data
through channels of the M2000 by
DB
M2K Master Server
M 2K Slave Server
NE
Page 15
HUAWEI Confidential
GBSS
Business
WRAN
Business
LTE
Business
Client Framework
other NEs.
The CME is used in the pure offline scenario.
Data is exchanged in the following modes:
Corba
DB Link
SQL Server
CME Server
Page 16
HUAWEI Confidential
Triple Area
Triple area: current area, planned area, and fallback area
Current area
Current area is a network data mirroring area used to save the configuration data of the live network.
Data in the current area is read-only and cannot be modified directly to ensure the security of the
network.
Only one current area is available for a network system.
Through the CME, the data of the live network can be periodically or automatically synchronized to the
current area. Alternatively, users can manually synchronize the data of the live network to the current
area.
Planned area
Planned area is a data planning area that is created with the data of a certain NE system.
Users can perform data planning in the planned area. Different users can create their respective
planned areas. The planned areas are independent of each other.
After implementing data planning in the planned area, users can export the generated data scripts.
After executing the data scripts to the NE, users can make the data take effect.
Fallback area
The rollback command scripts are generated in the fallback area to perform rollback.
When configuration adjustment effects are not ideal, the CME can quickly roll back to the original
configuration status.
Currently, the CME supports the rollback on the GSM side in only three scenarios: RNP import,
modification of radio algorithm parameters in batches, ARFCN import. In addition, the CME supports
the rollback in all adjustment scenarios on the UMTS side in versions later than BSC6900
V900R012C01 (UMTS only). For LTE, CME supports the rollback in all adjustment scenarios..
HUAWEI Confidential
Page 17
Standalone Version
Recommended
scenario
License
Configuration
area
One current area, multiple planned areas and multiple fallback areas.
Function
1. Configuration functions, such as site deployment and site swapping, are the same.
2. In the standalone version, current area-based functions, such as AVC, are unavailable. The script executor is unavailable.
Obtaining data of
the live network
Synchronize data on the BSC, NodeB, and eNodeB (through the data
channel between the M2000 and NEs).
Activating the
script
Script executor
Database
Documentation
HUAWEI Confidential
Page 18
Software Structure
CME client software, which is used to display the GUI
In the integrated version, the CME client software is installed on the maintenance terminal where the M2000 client is installed.
In the standalone version, the CME client software is installed on the PC.
CME server software, which is used to control the traffic flow and execute configuration operations by communicating
with the CME client
In the integrated version, the CME server software is installed on the M2000 server and communicates with applications on
the M2000 to obtain the NE information.
In the standalone version, the CME server software is installed on the PC.
Database
In the integrated version, the CME and the M2000 share one database, which is used to store NE configuration data.
In the standalone version, the MSDE database is used and is installed on the PC.
HUAWEI Confidential
Page 19
Version Compatibility
M2000
The recommended matching version is M2000 V200R011.
BSC
The recommended matching version is BSC6900 V900R013, BSC6900 V900R012, and BSC6900 V900R011, which can
provide configuration capability on transmission, device, and radio parameters.
The matching BSC6000 only provides the capability for radio layer and BTS swapping that works with the GBSS CME
V100R005.
The matching BSC6800 and BSC6810 are used only for the BTS swapping crossing specified versions.
GBTS
The GBTS does not directly match the CME. In this case, the CME matches the GBTS versions that are supported by the
BSC6900 versions that match the CME.
NodeB
The NodeB versions that work with the CME are the NodeB versions that work with the BSC6900/RNC.
The CME only matches the baseline versions of the NodeB, such as SPC100, SPC 200, and SPC 300 and their non-baseline
versions. The interface configured for NodeB products remains unchanged. For example, if the CME works with SPC 100,
then the CME works with versions such as SPC1XX or SPH1XX.
The following are principles of the CME to release the NodeB components.
For NodeB versions released after a CME version is released, the matching components are required and are released
with the NodeB version. When the component is used, refer to the Release Notes of the component to confirm the CME
version working with the component.
The preceding components will be contained in the following CME version.
LTE
The eRAN 2.1/eRAN 2.0 is recommended.
MBTS
The MBTS versions working with the CME depend on the versions of LTE, NodeB, and GBTS working with the MBTS.
HUAWEI Confidential
Page 20
List of objects
with the selected
level
HUAWEI Confidential
Page 21
HUAWEI Confidential
Page 22
Configuration objects
under one or several
NEs can be modified
in batches.
Parameter values
of several objects
can be modified to
the same value.
Right-click the
configuration NE to
display the GUI for
batch data
modification.
HUAWEI Confidential
Page 23
HUAWEI Confidential
Page 24
HUAWEI Confidential
Page 25
HUAWEI Confidential
Page 26
HUAWEI Confidential
Page 27
HUAWEI Confidential
Page 28
Data Flow
Three areas: live network, current area, and
planned area.
Interaction of data flow
Planned area
Current area: Data
modification in the planned area does not
Generating and
affect data in the current area.
activating scripts
Planned area
live network: Data
modification in the planned area takes
Live
effect on the live network by generating
network
and activating data scripts. Before the
changed data is delivered, data on the live
network is not affected.
Live network
current area/planned area:
Data modification on the live network will
be updated in the current area but cannot
be updated in the planned area.
Current area planned area: By
creating/synchronizing data in the planned
area, some data in the current area is
synchronized to the planned area.
Current area live network: Data in the
current area is read-only and does not
affect the live network.
Planned
area
Creating,
synchronization
Current area
Synchronization
HUAWEI Confidential
Page 29
Synchronization method
The data synchronization can be performed periodically, automatically,
or manually. The data synchronization of the current area is performed
in firm real time.
The data synchronization is performed automatically in the following
cases:
The CME receives the AVC message reported by the NE and
receives no other messages within two minutes.
A BSC is created on the M2000 and data synchronization has
been complete.
Data synchronization has been performed on the NodeB or TGW
on the M2000.
The script data has been successfully activated.
HUAWEI Confidential
Page 30
when the data in the planned areas takes effect on the live network.
If the data conflicts between the planned areas occur, the data in the
planned areas fails to take effect and are mutually overwritten. As a
result, the operation of the NE is affected.
To prevent the data conflicts between the planned areas, data
M2000
Planning area
...
Planning area
areas (such as cell index or TRX index) to ensure that the data in the
planned areas is not mutually overlapped.
Creating a planned area: copy the data of NEs from the current
Current Area
HUAWEI Confidential
Page 31
ObjectTree
Network topology
Device panel
HUAWEI Confidential
Page 32
Hint: Data conflict of this type occurs because a user modifies data in the planned area but the data has
been modified by another user and has been updated to the current area. Whether activation failures occur
depends on configuration rules on the live network.
During the data configuration, users can check the data modification on the live network
through the AVC message and adjust data configuration in time.
After the data configuration is complete, users need to check whether data is conflicted.
Compare user configuration data in the planned area with configuration data of the live network in the
current area to locate conflicted data.
Users can adjust configuration data in the planned area based on the check result to ensure that the
subsequent activation is successful.
HUAWEI Confidential
Page 33
Generation of Scripts
The CME supports two types of MML/XML file: differentiated data MML/XML file and full data
MML/XML file.
BSC and BTS: MML commands will be generated; NodeB and eNodeB: XML file will be generated.
Differentiated data MML/XML scripts: MML/XML configuration scripts are generated based on
modified contents.
This type of command is generated during the configuration of the planned area and is related to the
configuration process.
This type of command supports the exporting of modified contents separately by exporting multiple
differentiated scripts in the same planned area.
This type of command supports all configuration operations and is applicable to the scenarios such as
parameter modification, radio network planning, and optimization.
Full data MML/XML scripts: MML configuration scripts are generated based on objects.
This type of command supports the exporting of all configuration scripts based on the object selected
by users
The exported objects include:
BSC data, including data on the BSC, equipment, transmission, and radio network
BTS data, including data on the BTS equipment, transmission, and radio network
NodeB and eNodeB data, including all data of site.
This type of command is generated according to the data in the planned area and is not related to the
configuration process.
This type of command is applicable to special scenarios such as initial network deployment or site
deployment.
HUAWEI Confidential
Page 34
Activation of Scripts
Activation Type
START
Manual start
Upload
Active data
Auto start
Modify MML
MML has
errors
Browse task
Activation Methods
End
Timed activation: The configuration script is activated at the time specified by the user.
Stopped once an error occurs: The script activation is stopped immediately after an error occurs during a
command execution. In this case, the script activation resumes after the command is modified or skipped.
Skipping the error command: When error occurs during a command execution for activating the script, the
error command is skipped and the script activation resumes from the next command.
Pre-activation: The NE creates a simulative digital environment for the M2000 to perform the pre-activation
function. In this case, the M2000 can confirm whether data in the configuration files to be activated takes
effect.
HUAWEI Confidential
Page 35
Network Expansion
and Adjustment
Obtaining data from
the live network
Description
Network expansion and adjustment scenarios: Users export the current
configuration data (BSC: .ZIP file, by using the Web LMT (EXP CFGSYNFILE; eNodeB:
export from M2000). The exported data will be imported to the CME.
Users start the client software before using the CME to configure data.
Adding NEs
Adding NEs
Configuring data
Configuring data
Site deployment scenario: GU: The CME provides the basic unit of data configuration
files (ZIP files) based on NEs. Users can import a ZIP file to create an NE. They can
also reconfigure an NE based on this file. LTE: create site using GUI or sumary.
Network expansion and adjustment: Users create an NE on the CME and import the
corresponding NE data obtained from the live network.
Users reconfigure the data of an NE by using the CME client. The procedure is the
same as that by using the integrated CME.
Users check the correctness of data through the consistency check function provided
by the CME.
Checking data
Checking data
After data configuration and data check are complete, users export the MML/XML
scripts for activating data on the live network.
Exporting MML/XML
Activating MML/XML
Activating MML/XML
HUAWEI Confidential
Page 36
NodeB Data
Configuration Data
Source
BSC: 1. Users can export the BSC data by running the EXP
CFGSYNFILE command after logging in to the BSC6900 through
the Web LMT.
2. An example of minimal data is provided in the installation
directory of the CME.
LTE: export using LMT or M2000
Content
Default name
BSC: CMECfgSyncView.zip
eNodeB: LMT.xml or M2000.xml
NodeBCfg.xml
NEData.zip
Entrance
NE is selected
based on each
BSC/eNdeB.
HUAWEI Confidential
Page 37
HUAWEI Confidential
Page 38
Frequency refarming scenario: The verification of commands are different from batch commands.
When exporting incremental scripts, if scripts are service affected, the CME will pop out
messages for user to confirm the operations.
Operation steps on integrated CME:
HUAWEI Confidential
Page 39
Batch Configuration
Scripts are delivered in batches by running the RUN BATCHFILE
command on the WEB LMT.
The efficiency for delivering scripts to take effect is high.
Script Executor
Scripts are uploaded to the script executor provided by the integrated
CME.
The script executor is used in the frequency replanning scenario and
the method for checking commands in the scripts is different from that
in the batch configuration and batch processing.
Mode
Batch Configuration
647
Batch Processing
1767
HUAWEI Confidential
Page 40
Thank You
www.huawei.com