OEB305800 ENodeB LTE V100R007 Initial Configuration by CME ISSUE 1.00

eNodeB LTE V100R007
Initial Configuration by
CME
www.huawei.com
Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.
Learning Guide
Before learn this course, you should have:
Studied eNodeB LTE FDD V100R007 Product Description courses.
Studied eNodeB LTE V100R007 Operation course
Studied eNodeB LTE FDD V100R007 Data Introduction for Initial

Configuration courses.
Page2
References
3900 Series Base Station Product Documentation (Product

Version: V100R009C00)
Page3
Objectives
Upon completion of this course, you will be able to:
Outline the concept and structure of the summary data file
Select the summary scenario template according to the specific
situation
Create bulk eNodeBs with summary data file
Outline the usage and type of the CME rule check function
Implement initial configuration by CME
Page4
Contents
1. Flow Chart of eNodeB Data Configuration by CME
2. Summary Introduction
3. Implementation of Initial Configuration by CME
Page5
Process of Configuring a Single eNodeB

Prepare for configuration
start
Create a workspace
create an eNodeB(GUI mode)
configure the eNodeB data
Check and export the eNodeB configuration
end
Page6
Process of Configure Batch eNodeBs

start
Create a workspace
end
Prepare a template
Customize the Summary/LLD
Check and export eNodeB configuration
Edit the Summary/LLD
Import the radio data planning template
Edit the radio data planning template
Import Summary/LLD
Page7
Contents
Page8
Contents
2.1 Introduction to Summary Data File
2.2 Summary Customization Tools

3.3 Template Management
Page9
Get to Know Summary Data File
The summary data file provided by CME is useful to improve efficiency

in creating eNodeB.
Macro functions
Parameter Group
Parameter
Parameter value
Example of summary data file template
Page10
Common Data
Separating different
parameter groups by a
blank row
One parameter group can

correspond to only one
configuration object.
The Common Data sheet has the following features:
The data needs to be negotiated with customers and is consistent on the entire
network.
The data values are fixed, not vary with eNodeBs, such as the operator information
and OSS OM IP address.
When deploying eNodeBs in batches, the data is applicable to all eNodeBs in the
Summary data file.
This sheet cannot be deleted.

Page11
eNodeB Transport Data

Items in the table head show the basic eNodeB
deployment information and cannot be changed.
Basic information about a base station is
Radio
template
Site
template
given in this sheet, such as name and

template, and planned transport data.
Each row in this sheet corresponds to the
planned data of one base station.
The customized template can be added or
deleted by using the macro function

provided in the Summary data file.
Page12
eNodeB Radio Data

List parameters related to
sectors and RET objects
Distinguish eNodeB of different cells.
Cell template
Basic information about a cell, such as the cell ID, name, and template,
is given in this sheet. You need to fill in the sheet row by row. Each row
corresponds to the planned data of one cell.
Page13
Pattern
Default Pattern-type sheets are DevIPPattern, and IPRoutePattern sheets.

These two sheets are mandatory to be filled.
Feature 2: Parameter values are

the same.
Feature 2: Parameter reference

sources are the same.
Two features of pattern :

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 1: Each eNodeB has

the same number of device IP
record.
Page14
Reference in Pattern
Pattern sheet supports the data to refer to the data value in the
sheet of Common Data and Base Station Transport Data.
Reference
Page15
List
Data of different NEs is
distinguished by eNodeB name.
Data in the Base Station 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.
Page16
Comparison Between Pattern and List

Example of the same data in Pattern and List
DevIP
eNodeB Name CabinetNo SubrackNo SlotNo
eNodeB0
eNodeB0
eNodeB0
eNodeB1
eNodeB1
eNodeB1
eNodeB2
eNodeB2
eNodeB2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
7
7
7
7
7
7
7
7
7
SubboardType
PortType *PortNo
BASE_BOARD
BASE_BOARD
BASE_BOARD
BASE_BOARD
BASE_BOARD
BASE_BOARD
BASE_BOARD
BASE_BOARD
BASE_BOARD
LOOPINT
ETH
ETH
LOOPINT
ETH
ETH
LOOPINT
ETH
ETH
0
0
0
0
0
0
0
0
0
VRF
Index
0
0
0
0
0
0
0
0
0
*IP
10.141.142.4
10.141.142.5
10.141.142.6
10.141.142.10
10.141.142.11
10.141.142.12
10.141.142.16
10.141.142.17
10.141.142.18
*Mask
255.255.255.255
255.255.255.255
255.255.255.255
255.255.255.255
255.255.255.255
255.255.255.255
255.255.255.255
255.255.255.255
255.255.255.255
3 eNodeBs device IP in list

DEVIP
Cabinet Subrack Slot

No.
No.
No.
Subboard Type
Port Port
VRF Index
Type No.
BASE_BOARD
ETH
BASE_BOARD
ETH
BASE_BOARD
ETH
IP Address
Mask
Base Station Transport Data\OM Base Station Transport Data\OM

Plane\*eNodeB OM IP
Plane\*eNodeB OM IP Mask
Base Station Transport
Base Station Transport Data\S1\*S1 Sig
Data\S1\*S1 Sig LogicIP
LogicMask
Base Station Transport Data\X2\X2 Base Station Transport Data\X2\X2 Sig
Sig LogicIP
LogicMask
3 eNodeBs device IP in Pattern
The records to be filled in List is N times of that in Pattern. (N = the number

of eNodeBs)
Page17
Comparison Between Pattern and List

(Cont.)
Ethernet Port
*Port No.0
*Port Attribute0
OM Plane
Port No.1
Port Attribute1
*eNodeB OM IP
*eNodeB OM IP Mask
COPPER
FIBER
10.20.9.11
255.255.255.0
COPPER
FIBER
10.20.9.12
255.255.255.0
Pattern:
Reference 2
Reference 1
DEVIP
Cabin Subrack Slot

Port
Subboard Type
et No. No. No.
Type
Port VRF
No. Index
IP Address
Mask
BASE_BOARD ETH
Base Station Transport Data\OM Plane\*eNodeB OM IP
BASE_BOARD ETH
Base Station Transport Data\S1\*S1 Sig LogicIP
Base Station Transport Data\OM Plane\*eNodeB OM IP

Mask
Base Station Transport Data\S1\*S1 Sig LogicMask
BASE_BOARD ETH
Base Station Transport Data\X2\X2 Sig LogicIP
Base Station Transport Data\X2\X2 Sig LogicMask
If multiple pattern sheets refer to the same data source, you only need to change
the data in the data source without modifying the data in pattern sheets when the
data is changed.
Page18
PnP Data
Provides NMS data for base station
automatic deployment
Mandatory parameters for NMS to

establish an PnP task
Only the summary data files for creating base stations or introducing
RATs to base stations contain this sheet.
Page19
Other Sheets
Cover
Version number of the eNodeB
Precautions for filling in the Summary data
Change history of the Summary data file
Help
Procedure for collecting data in the Summary data file
Descriptions of each sheet in the Summary data
Page20
Contents

Page21
Get to Know Customization Tools
On CME, customization tools are provided to modify and maintain the

content of Summary data file.
Summary data file
Mapping
Mapping
Right table of
customization tools
User model
Conversion
Page22
NE model
Window for Customization Tools
Operations
to the
summary
data file
Operations for
customizing parameters
in the summary data file
Choose LLD parameters
To open the tool, enter CME > Advanced > Customize
Summary Data File in U2000 client.

Page23
Setting LLD Parameters
The Summary data file supports the setting of LLD parameters in the
Common Data, Base Station Transport Data, LTE Cell, and List-type
sheets.
Page25
Converting between Summary Data File

and LLD Data File
The macro function
provided to perform the
converting based on setting
of LLD parameters
LLD data file
Hide parameters
and sheets not set
Page26
Contents

Page27
Templates for Initial Configuration

LLD data file
transform
Default summary data file
Parameters
customization
Customized summary data file
link
Radio
Cell
eNodeB
default/
default/
default/
customized customized customized
template
template
template
Fill in
&
export
Legend:
: template with data
Deployment list
Configuration File
: template without data
Commissioning eNodeB
Template Management Window

Operations
buttons
Navigation tree
of template
types
To open the tool, enter CME > Advanced > Template Management
in U2000 client.
Page29
Add a Template by Customization
By saving existing data of one eNodeB
Add an
Add a
eNodeB
cell
or radio
template
template
By exporting from other CME tool
Export a customized template from one CME
Import a customized template to another CME
Page30
Edit a Template
In the Template Management window, select a cell template, a radio

template, or an eNodeB template.
Click edit .
Modify the data to be adjusted.
Conduct the integrity check and correctness check on the data.
Save the data as a template.

Save as a template
Page31
Convert a Template
This function is used when the cabinet numbers and subrack numbers
for boards in a base station in the network is different from default value.
Procedure:
In the Template Management window, select the corresponding eNodeB

template.
Click
Set Destination Cabinet No. and Destination Subrack No..
Click OK.
Page32
Contents
Page33
Contents
3.1 Preparing eNodeB Data
3.2 Creating eNodeB Data

3.3 Checking eNodeB Data
3.4 Exporting eNodeB Data
Page34
Contents
3.1.1 Common Data Sheet Configuration
3.1.2 Base Station Transport Data Sheet Configuration
3.1.3 LTE Cell Data Sheet Configuration
Page35
Common Data Sheet Configuration

Start
Basic information about global data
Operator info
MME info
IP-Sec information(Optional)
S-GW info
Time and clock Info
End
Page36
Basic Data
*Operator ID
CnOperator
*Operator name *Operator type
*Mcc
*Mnc
Second Signalling IP
Second Signalling
IP Mask
MME Info
*Port
*First Signalling IP
*First Service IP
First Signalling IP Mask
S-GW Info
First Service IP Mask Second Service IP Second Service IP Mask
Page37
Time Info
The network need a time source to
provide time synchronization to each

eNodeB
The time source types supported by
eNodeBs are NTP, GPS or None

Time Source
Time Source
*NTP IP
NTP IP
Mask
Port
Network Time Protocol

Authentication Authentication
*SyncCycle
Mode
Key
Page38
Authentication Key
Index
Master
Flag
Clock Info
Working Mode
ClkSource No
System Clock
Clock Synchronization
ClkSource Type
Mode
Page39
Quality Level
IP Clock Info
IP clock No: Indicate the link number of IP clock, it supports 2 links

maximum
Protocol
HW_Defined: Huawei private protocol
PTP(Precision Time Protocol): The 1588v2 protocol
Domain: Indicates the domain to which the IP clock link belongs. The
setting of this parameter must be the same as the setting of the clock
server.
Priority: Indicates the priority of the reference clock, in which 1 is the
highest priority and 4 is the lowest priority.
Page41
GPS Info
WorkMode
Indicates the working mode of the satellite card, including

GPS/GLONASS/COMPASS
Priority
Indicates the priority of the clock source. The value 1 indicates the
current clock source has the highest priority, and the value 4
indicates the current clock source has the lowest priority.
Page42
Transport Network Basic Info
Ethernet MTU : Indicates the Maximum Transfer Unit (MTU),

that is, the largest IP packet size (including the IP header) of the
Ethernet port. This parameter is negotiated with transport
network devices , the default value is 1,500 bytes.
Page43
Common Data Sheet Configuration

Start
Basic information about global data
IP-Sec information(Optional)
IPSec info
IKE info
End
ACL info
Page44
Contents
Page45
Base Station Transport Data Sheet

Configuration Procedure
Start
Device Data
Basic eNodeB information
Link Layer Data
about device
Network Layer Data

Transport Layer Data
End
Page46
Basic eNodeB information
eNodeB Name, eNodeB Id
The data is planned by Telecom operators.
Page47
eNodeB Template
Site Type
Version
Define the product version.
eNodeB Template
Currently, DBS3900_LTE,BTS3900_LTE,BTS3900A_LTE, BTS3900L_LTE and

BTS3900AL_LTE are supported.
Define the template of eNodeB.
Base Station Configuration
Indicates Base Station Configuration specifies radio frequency (RF) cable

connections.
Page48
Base Station Transport Data Sheet

Configuration Procedure
Start
Device Data
Link Layer Data
Network Layer Data
eNodeB transport information
End
Page49
S1 Interface
S1 Control plane
S1 User plane
S1-AP
User plane PDUs
GTP-U
SCTP
UDP
IP
IP
Data link layer
Data link layer
Physical layer
Physical layer
Page50
X2 Interface
X2 Control plane
X2 User plane
X2-AP
User plane PDUs
GTP-U
SCTP
UDP
IP
IP
Data link layer
Data link layer
Physical layer
Physical layer
Page51
Transport Data Configuration Procedure

Start
Link Layer Data
(Optional) VLAN information

VLANMAP
Network Layer Data
VLANCLASS
End
Page52
VLAN Introduction
VLAN1
VLAN2
VLAN3
VLAN4
VLAN has the following advantages:
Suppresses broadcast storm
Improves transmission security
Provides differentiated services
Page53
VLAN Solution
VLAN1
VLAN2
VLAN1
S1-U
VLAN2
MME
MME
IP
Network
Solution 1 : VLAN is
designed based on eNodeB
OM
VLANn
S1MME
VLAN1
SGW
VLAN3
S1MME
S1-U
VLAN2
OM
VLANn
IP
Network
Solution 2 : VLAN is
designed based on traffic
type
Page54
SGW

Start
Starte
Link Layer Data
d
Network Layer Data
IP configuration
IP Route configuration
End
Page55
Device IP Configuration
Device IP
UTRP
LMPT/UMPT
Ethernet
link
Ethernet
trunk
LOO
PINT
SUB
IF
PPP
link
MPGRP
link
LOO
PINT
Loopint ( Loopback interface) is a logic IP address used for IPsec inner IP address.
Page56
IP Route
Destination IP
LMPT
Next hop route
Destination Mask
Next hop IP
UMPT
Destination IP
Destination Mask
Exit Interface
Port Type
Port No.
Page57
IP Route
Destination IP
Next hop route
Destination Mask
Next hop IP
UTRP
Destination IP
Destination Mask
Exit Interface
Port Type
Port No.
Page58

Start
Starte
Link Layer Data
d
Network Layer Data

S1 and X2 link info
OM channel Info
IP clock link info
End
Page59
S1 and X2 Interface
There are two modes for configuring S1 and X2 links: link and
EndPoint.
Both link and EndPoint modes meet the requirements in most

configuration scenarios.
If a large number of MMEs/SGWs exist in the MME/SGW pool, the

EndPoint configuration mode is recommended, which reduces
configuration workload.
If the PATHTYPE type used by the IPPATH between the S1 and X2 is set
to QoS, the link configuration mode is mandatory.
The external template only support end point method
Page60
Template Based Configuration
Local node
information
Peer node
information
Page61
MML Based Configuration Link

Mode
Page62
MML Based Configuration End Points

Mode
Page63
OM Channel
OMCH IP: The local IP address of the remote maintenance

channel with the U2000
OMCH Mask
Local Maintenance
Remote Maintenance
LMT
U2000
Client
U2000 Server
Local OM IP
eNodeB
LMT
Remote OM IP
or
Page64
IP Clock Link
Page65
Contents
Page66
Radio Data Configuration Procedure

Start
Started
Cell basic parameters
RF engineering parameters
End
Cell ID
TA Code
Sector ID
System Bandwidth
Frequency number
CP type
PCI
Preamble format
Root sequence
index
..
Page67
Cell Basic Parameters
LocalCellID, CellName, CellID(Logical Cell ID)
TAC: Tracking area code
SectorId
DlEarfcn, UlEarfcn: Cell downlink/uplink frequency.
DlBandwidth, ULBandwidth: Cell Downlink/bandwidth
PCI : Physical cell identity (PCI). The value range is 0 to 503,

which can be used in sequence. The CME Automatically
generates a PCI in an external template.
ReferenceSignalPw : Indicates the reference signal power of the
cell
Page68
LTE Release 9 Bands

Band
Duplex
FDL_low
FDL_high
(MHz)
(MHz)
NOffs-DL
NDL
FUL_low
FUL_high
(MHz)
(MHz)
NOffs-UL
NUL
FDD
2110
2170
0-599
1920
1980
18000
18000-18599
FDD
1930
1990
600
600-1199
1850
1910
18600
18600-19199
FDD
1805
1880
1200
1200-1949
1710
1785
19200
19200-19949
FDD
2110
2155
1950
1950-2399
1710
1755
19950
19950-20399
FDD
869
894
2400
2400-2649
824
849
20400
20400-20649
FDD
875
885
2650
2650-2749
830
840
20650
20650-20749
FDD
2620
2690
2750
2750-3449
2500
2570
20750
20750-21449
FDD
925
960
3450
3450-3799
880
915
21450
21450-21799
FDD
1844.9
1879.9
3800
3800-4149
1749.9
1784.9
21800
21800-22149
10
FDD
2110
2170
4150
4150-4749
1710
1770
22150
22150-22749
11
FDD
1475.9
1500.9
4750
4750-4999
1427.9
1452.9
22750
22750-22999
12
FDD
728
746
5000
5000-5179
698
716
23000
23000-23179
13
FDD
746
756
5180
5180-5279
777
787
23180
23180-23279
14
FDD
758
768
5280
5280-5379
788
798
23280
23280-23379
17
FDD
734
746
5730
5730-5849
704
716
23730
23730-23849
33
TDD
1900
1920
26000
36000-36199
1900
1920
36000
36000-36199
34
TDD
2010
2025
26200
36200-36349
2010
2025
36200
36200-36349
35
TDD
1850
1910
26350
36350-36949
1850
1910
36350
36350-36949
36
TDD
1930
1990
26950
36950-37549
1930
1990
36950
36950-37549
37
TDD
1910
1930
27550
37550-37749
1910
1930
37550
37550-37749
38
TDD
2570
2620
27750
37750-38249
2570
2620
37750
37750-38249
39
TDD
1880
1920
28250
38250-38649
1880
1920
38250
38250-38649
40
TDD
2300
2400
28650
38650-39649
2300
2400
38650
38650-39649
Page69
Carrier Frequency EARFCN Calculation
FDL = FDL_low + 0.1(NDL - NOffs-DL)
eNB
UE
FUL = FUL_low + 0.1(NUL - NOffs-UL)
Page70
Example
100kHz Raster
Uplink
Downlink
1937.4MHz
2127.4MHz
FDL = FDL_low + 0.1(NDL - NOffs-DL)
NDL =
NDL =
(FDL - FDL_low)
0.1
+ NOffs-DL
(2127.4 - 2110)
+ 0 = 174
0.1
Page71
Frequency
RF Engineering parameters
Start
Started
Cell basic parameters
RF engineering parameters
Longitude
Latitude
Azimuth
Down title
TxRx Mode
Customized cell template
End
Page72

Start
Started
Cell basic information
LTE->LTE intra-feq(Optional)
LTE->LTE inter-feq)(Optional)
LTE->UMTS (Optional)
(Optional)Neighbor Cell List
LTE->CDMA2000(Optional)
LTE->GERAN(Optional)
End
Page73
Contents

Page74
Contents
3.2.1 Create a single eNodeB
3.2.2 Create eNodeBs in Batches
Page75
Basic Knowledge About the CME Data

Areas
The CME provides a current data
area and multiple planned data

areas. Multi-area management
improves data configuration
efficiency and enables several
users to configure the same NE at
the same time.
Current data area: stores the

configuration data on the live
network. The data can only be
viewed.
Planned data area: allows users
to plan and configure data. Users
can create multiple planned data
areas based on the data in the
current data area to perform
different configuration tasks.
Page76
Creating a Planned Data Area

Set name
Set user group
Set access rights
Page77
Opening a Planned Data Area
Page78
Creating Initial Data of single eNodeB
To create a single eNodeB, you need to open a planned area

then start the wizard on the CME, fill the eNodeB basic data, and
select the corresponding template to finish the creation.
Set product type
Set NE basic information
See next page

Page79
Creating Initial Data of single

eNodeB(cont.)
Page80
Configuring eNodeB Equipment Data
Page81
Configuring eNodeB Transport Data
Page82
Configuring eNodeB Radio Data
Page83
Contents
3.2.1 Create a single eNodeB
3.2.2 Create eNodeBs in Batches
Page84
Opening a Summary Data File
Select default or custom on required
Set path
See next page
Page85
Customize Summary Data File (Opt.)

Create
empty sheet
Check
rule
Deleted
selected
row
Modify group
name
Sort by group
Set summary<->LLD
Page86
Creating Base Station Using Summary
Select summary
data file
See next page
Page87
Creating Base Station Using Summary (cont.)
Select the
base station
Page88
Contents

Page89
Description of Data Correctness and Integrity

Check
Data correctness check:
Correctness is the basic rule for data of a single NE. If data that violates the
rule is delivered to the eNodeB, activation of the data fails.
The basic rule in the CME is consistent with that on NEs. The incorrect data
detected by the CME cannot be delivered to NEs.
Data integrity check:
Integrity is an enhanced rule supported by only the CME for data of a single
NE. This rule enables the CME to analyze the indispensable MOCs from the
service perspective.
Integrity is not a forcible constraint rule. Users determine whether to forcibly
deliver the data that violates the rule.
Page90
Description of Data Consistency Check
Data consistency check:
Consistency is an enhanced rule supported by only the CME for data

of multiple NEs. This rule enables the CME to check the consistency
of data among multiple NEs from the service perspective.
Consistency is not a forcible constraint rule. Users determine whether

to forcibly deliver the data that violates the rule.
The prerequisite of the data consistency check is that data of each
single NE is correct.
Page91
Checking the data Correctness and

Integrity
Page92
Checking the data Consistency
Page93
Checking the data Consistency(cont.)
Page94
Recovering Data Based on the Consistency

Check Results
Recovery types:
AutoFix: Double-click a data record. > Select the recovery type. > Select AutoFix.
Refresh:
If Operation is set to AutoFix, the CME automatically recovers data. You do not
need to specify any information.
Specify the required information and enable the CME to recover data
Edit: Double-click a data record and modify data in the displayed MOC configuration
table.
None: The CME cannot automatically recover data. Manual data modification is required.
Page95
Contents

Page96
Exporting Auto Deployment Data

Select NE
See next page
Page97
Exporting Auto Deployment Data(cont.)
Set export path
Set data check
Page98
Questions
Describe the main process of configuring eNodeB in batch.
Describe the main type of the template.
How to create single eNodeB in GUI?
what type of summary template contains the data that need to

be negotiated with customer?
How to check and export the configuration data?
Page99
Summary
The structure of the summary data file
The type of the summary scenario template
How to customize a summary data file?
What is correctness check and integrity check, how to do these

two types of check?
Page100
Thank you
www.huawei.com

OEB305800 ENodeB LTE V100R007 Initial Configuration by CME ISSUE 1.00

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

OEB305800 ENodeB LTE V100R007 Initial Configuration by CME ISSUE 1.00

Încărcat de

Drepturi de autor:

Formate disponibile

eNodeB LTE V100R007

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

Before learn this course, you should have:

Studied eNodeB LTE FDD V100R007 Product Description courses.

Studied eNodeB LTE V100R007 Operation course

Studied eNodeB LTE FDD V100R007 Data Introduction for Initial

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

3900 Series Base Station Product Documentation (Product

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

Upon completion of this course, you will be able to:

Outline the concept and structure of the summary data file

Select the summary scenario template according to the specific

Create bulk eNodeBs with summary data file

Implement initial configuration by CME

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

3. Implementation of Initial Configuration by CME

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

Process of Configuring a Single eNodeB

create an eNodeB(GUI mode)

configure the eNodeB data

Check and export the eNodeB configuration

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

Process of Configure Batch eNodeBs

Customize the Summary/LLD

Check and export eNodeB configuration

Edit the Summary/LLD

Import the radio data planning template

Edit the radio data planning template

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

3. Implementation of Initial Configuration by CME

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

2.2 Summary Customization Tools

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

Get to Know Summary Data File

The summary data file provided by CME is useful to improve efficiency

Example of summary data file template

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

One parameter group can

The Common Data sheet has the following features:

This sheet cannot be deleted.

eNodeB Transport Data

Basic information about a base station is

given in this sheet, such as name and

The customized template can be added or

deleted by using the macro function

eNodeB Radio Data

Distinguish eNodeB of different cells.

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

Default Pattern-type sheets are DevIPPattern, and IPRoutePattern sheets.

Feature 2: Parameter values are

Feature 2: Parameter reference

Two features of pattern :

The quantity of data configured for each eNodeB is

Parameter values of eNodeBs are the same or

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

Feature 1: Each eNodeB has

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

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

Comparison Between Pattern and List

3 eNodeBs device IP in list

Cabinet Subrack Slot

Base Station Transport Data\OM Base Station Transport Data\OM

3 eNodeBs device IP in Pattern

The records to be filled in List is N times of that in Pattern. (N = the number