Training Document IManager M2000 CME V200R011 Introduction To LTE Summary Data File 20110823 B 1 0

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.
:32-35pt
: R153 G0 B0
:
FrutigerNext LT Medium
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
FrutigerNext LT Regular
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Training Objectives
After learning this course, you will be able to:
Know about functions related to the Summary data file.
Know about the method for filling in the Summary data file.
Use the Summary data file to deploy eNodeBs on the CME.
Use the customization tools provided in the Summary data file to
customize a data file.
Use the Summary data file to collect the low-level design (LLD) data.
Use the data export function provided in the Summary data file to
modify data and deploy eNodeBs.
www.huawei.com
:40-47pt
:26-30pt
:
:
: Arial

:35-47pt
:
:24-28pt
:
:

Security Level: Internal Only
Wireless Product Rollout Dept.WiTL Team

M2000-CME V200R011C01
Introduction to LTE
Summary Data File
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Contents
Summary Solution
Background of the Summary Data File
Introduction to the Summary Data File
eNodeB Deployment by Using the Summary Data File in Different
Scenarios (Security/Non-Security/TDD/MOCN)
Customization Tools Provided in the Summary Data File
Example of Using the Summary Data File
Solution Integrating the LLD and the Summary Data Files
Data Modification and eNodeB Deployment by Using the Data Export
Function Provided in the Summary Data File

:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Background of the Summary Data File
eNodeB Deployment by Using an eNodeB Data Export Template eNodeB Deployment by Using the Summary Data File
Expansion
Changing an eNodeB data export template involves changing the mapping
relationship between the eNodeB data export template and the CME version. As a
result, the changes can be incorporated only in the later mapping version or a new
patch.
Customization tools are provided in the Summary data file so
that GTS engineers can customize a Summary data file
according to the actual situation of an eNodeB.
Involved files
Three files are involved:
LLD data file
Summary data file
eNodeB data export template
Only the Summary data file is involved during the eNodeB
deployment.
Data conversion
Two mapping processes are involved:
LLD data file > Summary data file
Summary data file > eNodeB data export template
In addition, mapping relationships of the three files need to be maintained manually.
The mapping s relationships are automatically maintained by a
tool. In addition, the Summary data file provides the macro
function so that the LLD data file and the Summary data file can
be automatically converted.

Data filling
All data, except for common data, is filled in List mode. In this case, GTS engineers
need to fill in a lot of data.
Data can be filled in Pattern, List, or Common mode. As a result,
the workload of filling in data by GTS engineers is decreased.
When deploying LTE eNodeBs by using an eNodeB data export template, GTS engineers have to spend a lot of time in
the connection sections for preparing data used for eNodeB deployment, instead of data configuration and eNodeB
deployment due to the following reasons:
The expansion is poor.
There are a lot of data files, mapping relationships of which need to be maintained manually.
Two mapping processes are involved.
All data, except for common data, is filled in List mode.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Contents
Concept of the Summary Data File
Structure of the Summary Data File

:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Contents
Concept of the Summary Data File
Reference
Pattern
List
Comparison Between Pattern and List

:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Customize a
Summary data file
and set LLD
parameters.
Operators fill in the
LLD data file.
Switch to the
Summary data file.
Switch to the LLD
data file.
Whether
operators are
involved?
Yes
GTS engineers fill in
eNodeB deployment
data.
No
Import eNodeB
deployment data to
the CME to deploy
eNodeBs in batches.
Export eNodeB
deployment data
after the data check
is successful.
Commission an
eNodeB.
End
Create eNodeB
in GUI
Modify eNodeB
Configration Data
Save As eNodeB
Template
Page7
eNodeB Deployment Process Using the Solution Integrating the LLD and
the Summary Data File
Switch between the
LLD data file and
the Summary data
file
1
3
Customize
Summary Data
File using the
Summary data
file
4
eNodeB
Deployment
Using Summary
Data File
Create
eNodeB
Template
2
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Page8
Build eNodeB Data
Summary
table
(excel file)
Default or
customized
eNodeB Template
associated
necessary
Radio
Template
associated
optional
Cell
Template
Associated
optional
build
eNodeB data
(xml)
Build eNodeB Data
When summary being imported into CME,
CME will use the correct template build
eNodeB data:

Data prioritySummary data has the
highest priority, Radio and cell has lower
priority, and eNodeB has the lowest
priority.:
Summary data> template data;
Cell template>eNodeB template
Radio template>eNodeB template
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Summary Data File Reference 1
The Pattern-type sheets support the reference of parameters on the Common Data and eNodeB Transport Data
sheets.

The format of parameter reference is as follows:
sheet name\name of the MOC group\parameter name [n]
In this format, [n] indicates the sequence number of the record. The sequence number of records begins from 0.
Currently, cases are distinguished by adding the sequence number to the case name in the Common Data sheet.
Reference
Reference of parameters in the Common Data sheet:
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Summary Data File Reference 2
Reference of
parameters
or new
parameter
values
Reference
Reference of parameters in the eNodeB Transport Data sheet:
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Summary Data File Pattern
Two features:
1. The quantity of data configured for each eNodeB is the same in the Summary
data file.
2. Parameter values of eNodeBs are the same or parameter reference sources
are the same.
Feature 2:
Parameter
reference
sources are
the same.
Feature 2:
Parameter
values are
the same.
Feature 1: Each eNodeB
has five pieces of DevIP
data.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Summary Data File List
1
2
Data of
different NEs
is
distinguished
by eNodeB
name.
Data in the eNodeB Transport Data sheet is redundant when
the number of NEs and the number of parameters are large. To
prevent the data from becoming redundant, you can list some
parameters of NEs in an independent sheet.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Summary Data File Comparison Between Pattern and List (1)
DevIP
eNodeB Name CabinetNo SubrackNo *SlotNo *SubboardType *PortType *PortNo *IP *Mask
eNodeB0 0 0 7 BASE_BOARD LOOPINT 0 10.141.142.1 255.255.255.255
eNodeB0 0 0 7 BASE_BOARD ETH 0 10.141.142.5 255.255.255.255
List:
Pattern:
The workload of filling in data in List mode is twice compared with that
in Pattern mode.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Summary Data File Comparison Between Pattern and List (2)
Pattern:
In the case that the same data source is referred by different Pattern-
type sheets, you can only change the data in the data source instead of
updating the reference when the data is changed.
eNodeB Data BFD
*eNodeB Name BFD SourceIP BFD Mask BFD DstIP
eNodeB0 10.2.96.122 255.255.255.248 10.2.96.121
eNodeB1 10.2.96.90 255.255.255.248 10.2.96.89

Reference 2
Reference 1
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Contents
Concept to the Summary Data File
Common Data
eNodeB Transport Data
eNodeB Radio Data
Pattern-Type Sheet
List-Type Sheet
Other: Cover, Help, USB Parameter for Site

:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Summary Data File Common Data
The Common Data sheet has the following features:
1. The data needs to be negotiated with customers.
2. The data refers to the common planning data of eNodeBs in the Summary data file.
3. When deploying eNodeBs in batches, the data is applicable to all eNodeBs in the Summary
data file.

This sheet cannot be deleted but the parameter description information can be modified.
Separating different
MOC information
groups by a blank
row
One MOC group can
correspond to only one
configuration object.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Summary Data File eNodeB Transport Data
Items in the table
head show the basic
eNodeB deployment
information and
cannot be changed.
eNodeB parameters and parameters related to transmission
planning are defined. Then, other parameters about eNodeBs
are specified by correlating to the eNodeB template.

This sheet cannot be deleted. Items in the table heading,
except for the marked ones, can be changed.

The customized template can be added or deleted by using the
macro function provided in the Summary data file.

1
2
Site template
5
Radio
template
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Summary Data File eNodeB Radio Data
1
2
Distinguish
eNodeBs of
different cells.
List parameters
related to
sectors and
RET objects.
3
Cell
template
The eNodeB Radio Data sheet has the following features:
1. Planning parameters of cells and sectors are defined.
2. This sheet cannot be deleted but contents in this sheet can be changed.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Summary Data File Pattern-Type Sheet
Currently, the default Pattern-type sheets are the OMChPattern, DevIPPattern, and IPRoutePattern sheets.
The three sheets must be filled. Other Pattern-type sheets can be customized based on networking and planning
of each site.
Reference
The eNodeB Transport Data sheet provides the route information of ten groups by default. You can customize the
parameters related to routes, such as IP address, Mask, NextHopIP by referring to parameters in the
IPRoutePattern sheet.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Page 20
Summary Data File List-Type Sheet
You can refer to the contents in the "
Summary Data
File List
" page.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Summary Data File Other Sheets
Cover
Version number of the eNodeB
Precautions for filling in the Summary data file
Descriptions of each sheet in the Summary data file
Change history of the Summary data file

Help
Help for the Summary data file

USB Parameter for Sites
USB parameters for site deployment

Help for USB Parameter
Help for filling in USB parameters for site deployment
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Summary Data File Selection of Data Filling Format
1. Which data is filled in Common-type sheets?
You need to negotiate the data with customers. The parameter values are fixed and do not vary with eNodeBs.

2. Which data is filled in the eNodeB Transport Data sheet?
You need to negotiate the data with customers. The parameter values vary with eNodeBs.
You need to fill in the eNodeB Transport Data sheet with the data related to eNodeBs and transport-related data (and some data related
to the IP address).

3. Which data is filled in Pattern-type sheets?
In the Summary data file, the number of data configured for eNodeBs is the same. In addition, parameter values are the same and the
parameter reference sources are the same.
The Omch, DevIp, and IpRoute sheets are in Pattern-type sheets by default. This solves the rule-check problem after eNodeBs are
deployed by using the Summary data file. You are advised not to delete the three sheets.

4. Which data is filled in the customized template?
You do not need to negotiate the data with customers. Configuration data of each eNodeB is the same. You are advised to fill in the
customized template with parameters such as hardware parameters and radio algorithm parameters.

5. What is the difference between the data in the customized templates and the data in the Common-type sheets?
The data in the Common-type sheets can be saved in the customized templates after negotiation. The data in the customized templates,
however, must be subject to the Summary data file.

6. Which data is filled in List-type Sheets?
The data is filled in List-type sheets when the data cannot be filled in the Common-type sheets, Pattern-type sheets, or customized
templates.

7. Why is not method for filling in List-type data in the eNodeB Transport Data sheet not recommended?
The List-type data can be filled in the eNodeB Transport Data sheet. This data filling method, however, is not recommended. This is
because the data in the eNodeB Transport Data sheet may be redundant and the Summary data file may be changed multiple times
due to the large amount of data.

:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Contents
eNodeB Deployment by Using the Summary Data File in
Different Scenarios (Security/Non-Security/TDD/MOCN)
Overview
eNodeB Deployment by Using the Summary Data File in Non-Security Scenario
eNodeB Deployment by Using the Summary Data File in Security Scenario
eNodeB Deployment by Using the Summary Data File in TDD Scenario
eNodeB Deployment by Using the Summary Data File and Template Selection in
MOCN Scenario

:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Overview
The processes for eNodeB deployment in scenarios such as
non-security, security, TDD, and MOCN scenarios are the same.
However, data filled in the Summary data file are different.

The differences of filling in the Summary data file are compared
based on the eNodeB deployment in non-security FDD scenario.

:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

eNodeB Deployment by Using the Summary Data File in Non-Security
Scenario
You need to fill in the necessary information, such as eNodeB, operator,
clock, time zone, OMCh channel, route, and core network.

:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

eNodeB Deployment by Using the Summary Data File in Security Scenario
Compared to the non-security scenario, objects related to the security scenario are as follows:
In the Common Data sheet: IPSECPROPOSAL, IKEPEER, IPSECPOLICY, IKECFG, IPSECBIND,
PACKETFILTER, ACL, ACLRULE, and security certificate
In the eNodeB Transport Data sheet: physical IP address and PreShareKey of IKEPeer
In the ACLPattern sheet: All parameters in the ACLPattern sheet
You can directly select the security template that is released by default. Or, you can add a security scenario by
using the customization tools provided in the Summary data file.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

eNodeB Deployment by Using the Summary Data File in TDD
Scenario
TDD and FDD scenarios: The main differences lie in the parameter values in the
customized template or Summary data file, and parameters in cell sheets.

The differences in filling in the Summary data file are as follows:
In the eNodeB Transport Data sheet: FDD/TDD Mode and Site Template.
In the eNodeB Radio Data sheet: FddTddInd and ARFCN
Differences in FDD and TDD scenarios
Differences in FDD and TDD
scenarios
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

eNodeB Deployment by Using the Summary Data File in MOCN
Scenario
The differences in filling in the Summary data file in MOCN and single-
operator scenarios are as follows:
1. The following parameters are added in the Common sheet:
eNodeB Info: Add MCC and MNC of an eNodeB
ENodeBSharingMode: Select
eNodeB Sharing Mode
.
LicenseSharingPolicy: Select License-Sharing Policy of an eNodeB.
2. The CellOp and CnOperatorTa sheets are changed from radio sheets to
List-type sheets.
3. RAN Sharing Mode Switch of CellAlgSwitch is added in the Radio sheet:
RAN-sharing mode switch
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

eNodeB Deployment by Using the Summary Data File in MOCN
Scenario Data File Selection
Data file selection in Endpoint and Link mode:
1. The EndPoint mode is recommended. That is, the values of IPPath and SctpLink, and
interface configuration are automatically generated after you fill in MME, SGW, S1SigIP,
S1ServerIP, X2SigIP, and X2ServerIP.
2. Currently, the EndPoint mode supports the scenario of one S1SigIP and S1SigIP port.
3. If more than one S1SigIP or S1SigIP port are configured at the site, you are advised to
deploy the eNodeB in Link mode. That is, the values of IPPath and SctpLink, and
interface configuration are manually configured.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Contents
Customization Tools Provided in the Summary
Data File
Introduction
Function Introduction
Scenario-Based Summary Data File
Introduction Background
Supported Scenarios
Example

:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

On the CME, customization tools are provided in the Summary data file so
that contents in the Summary data file can be modified and maintained.
User model NE model
Summary data file
Right table of
customization tools
Mapping Mapping
Conversion
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Customization Tools Provided in the Summary Data File Function
Introduction
Open a
template
Check a
template
Search
from the
right table
Add a
sheet
Add a scenario-
based Summary
data file
Generate the
mapping directly
from the left
navigation tree

Search for the NE
on the left
navigation tree
from the right table
Add a row
Delete a row
Set the
LLD
Modify
Summary Data
Group Name
The Summary data file supports the following functions:
Open/close/save the data file
Add scenario-based data file
Check the validity of the data file
Add a sheet
Query information
The left navigation tree supports the following functions:
Search
Sequence
Display/close the left navigation tree
The sheet supports the following functions:
Adding/changing mapping on the left navigation tree
Adding/deleting a blank row
Sequence
Filter
Search for NEs on the left navigation tree from the right table
Set the LLD/reference
Define the data in the Pattern-type sheet

:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Customization Tools Provided in the Summary Data File Scenario-
Based Background
The CME provides the functions of customizing the scenario-based
Summary data file to simplify the procedure for customizing the scenario-
based Summary data file and reducing the difficulties.

Customizing the scenario-based Summary data file refers to defining some
typical scenarios by NE feature. The CME provides a window for selecting
different scenarios. Based on the selected scenario, the CME adds the
objects and parameters to the existing Summary data file so that the
Summary data file for typical scenarios can be quickly customized.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Scenario-Based Type

Based on usage of onsite features and network reconstruction requirements, the
CME provides three types of scenarios:
VLAN
Security
QoS

Based on different usage methods, the three types of scenarios can be further
divided into eight sub-scenarios:
VLANGROUP
SINGLEVLAN
SINGLEVLAN_AND_VLANGROUP
IPsecAuthMethByPSK
IPsecAuthMethByPSK_AND_PacketFilter
IPsecAuthMethByRSASIG_AND_PKI_CMPv2
IPsecAuthMethByRSASIG_AND_PKI_CMPv2_AND_PacketFilter
Overbooking_AND_DifferentiatedTrafficFlowControl
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Scenario-Based Example
Add the VLANGROUP feature to the existing Summary data file and customize the
scenario-based Summary data file containing the VLANGROUP feature.
2
1
3
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Contents

Customizing the Summary Data File

:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Example of Using the Summary Data File Customizing a Data
Collection File
The following is a typical example about how to customize the Summary data file.
Case Changing the Summary data file not supporting the security scenario to the
Summary data file supporting the security scenario
Add the ACLPattern and BFDSessionPattern sheets.
Add the SCTPLNKList sheet. This change is only used to describe how to add a List-
type sheet, which is not mandatory in security scenario.
Modify the Common Data sheet: Add parameters such as IPSECPROPOSAL,
IKEPEER, IPSECPOLICY, IKECFG, IPSECBIND, PACKETFILTER, ACL, and the
security certificate.
Add the eNodeB Transport Data sheet.
Add the OuterIP group, and add the PhysicalIP, PhysicalIP Mask, PhysicalIP
PortType, and VlanID parameters under the group.
Add the BFD group, and add the BFD SourceIP, BFD Mask, and BFD DstIP parameters
under the group.
Add the CAserver group, and add the CA server IP parameter under the group.
Add the information about a default route group. Add the IPRoute IP11, IPRoute Mask11,
IPRoute NextHopIp11, VlanID11, and VLANPri11 parameters to the existing IPRoute
group. This change describes only how to add a column to the existing group.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

For the operation procedure, see the Customization Tool of a
Summary Data File in CME online help hdx file ( press F1 in
software)/
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Contents
Solution Integrating the LLD and the Summary Data Files

Background
eNodeB Deployment Process by using the Solution Integrating the LLD and
the Summary Data Files
Setting LLD Parameters by Using the Customization Tools in the Summary
Data File
Converting the Summary Data File to the LLD Data File
Delivery of Existing LTE 2.0 eNodeBs

:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Background
LTE 2.0 has the following problems:
Three data files are required:
LLD data file
Summary data file
eNodeB data export template

Two mapping processes are required:
LLD data file > Summary data file
Summary data file > eNodeB data export template
The process is
complicated.
When will the
entire process
ends?
LLD data file Summary data file
eNodeB data export
template
Mapping
Mapping
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

eNodeB Deployment Process by Using the Solution Integrating the LLD
and the Summary Data Files
Switch between the
LLD data file and
the Summary data
file
1
2
Customize
LLD
parameters by
using the
Summary data
file
3
These
steps do
not change
after the
LLD data
file is
integrated.
4
5
Switch to the LLD
data file.
Switch to the
Summary
data file.
Customize a
Summary data file
and set LLD
parameters.
Operators fill in the
LLD data file.
Switch to the
Summary data file.
Switch to the LLD
data file.
Whether
operators are
involved?
Yes
GTS engineers fill in
eNodeB deployment
data.
Import eNodeB
deployment data to
the CME to deploy
eNodeBs in batches.
Export eNodeB
deployment data
after the data check
is successful.
Commission an
eNodeB.
End
Automatically generated
the Common Data
sheet based on settings
of LLD parameters.
Automatically add the
QoS information in the
Common Data sheet.
Automatically process
common data except for
the OoS information.
Automatically map the
QoS information to
DIFPRI and VlanClass
columns.
Switch to the Summary data file.
Automatically unhide
sheets and parameters.
Automatically hide
sheets and parameters.
Switch to the LLD data file.
Rule
Rule
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Setting LLD Parameters by Using the Customization Tools in the
Summary Data File
2
1
3
The Summary data file supports the setting of LLD parameters in the Common Data, eNodeB
Transport Data, eNodeB Radio Data, and List-type sheets.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Converting the Summary Data File to the LLD Data File
The Summary data file provides the macro function so that the LLD data file and the Summary
data file can be automatically converted.
Summary data file
LLD data file
Perform the
mapping based on
setting of LLD
parameters.
Hide
redundant
sheets.
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

RNP
Page44
Scenario
RNP is applicable to cell expansion and neighboring cell relation
adjustment.
Manage the neighboring cell relation for ERAN in the entire
network.
Automatically create bi-directional neighboring cells.
Automatically create X2 links.
Automatically add external cells according to the intra-frequency
neighboring cell and inter-frequency neighboring cell.

:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

RNP
Page45
1
2
3
Export RNP
Data FIle
Modify RNP
Data FIle
Import RNP
Data FIle
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

RNP
Page46
Operation procedure: Export RNP data
1
2
3
4
5
6
7
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Page47
RNP
Operation procedure: Export RNP data

9
8
10
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Page48
RNP
Operation procedure: Import RNP data

1
2
3
4
:32-35pt
: R153 G0 B0
:
: Arial

:30-32pt
: R153 G0 B0
:

:20-22pt
(2-5) :18pt
:
:
: Arial

:18-20pt
(2-5):18pt
:
:

13
.

Page49
RNP
Operation procedure: Import RNP data

6
5
7
www.huawei.com
Thank you!

Training Document IManager M2000 CME V200R011 Introduction To LTE Summary Data File 20110823 B 1 0

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

Training Document IManager M2000 CME V200R011 Introduction To LTE Summary Data File 20110823 B 1 0

Uploaded by

Copyright:

Available Formats

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

You might also like