Config PDF

eNodeB LTE V100R006 Initial
Configuration
eNodeB LTE
V100R006
Initial Configuration
www.huawei.com
Copyright 2013 Huawei Technologies Co., Ltd. All rights reserved.
Objectives
Upon completion of this course, you will be able to:

Describe LTE product networking
Outline functions of Summary data file
Outline the meaning of the common, equipment, transport data
Preparing eNodeB data
Configure eNodeB data
Check and export eNodeB data
Confidential Information of Huawei. No

Spreading Without Permission
Page1

Configuration
Contents
1. eNodeB Data Configuration Introduction
2. Preparing eNodeB Data
3. Creating eNodeB Data
4. Checking eNodeB Data
5. Exporting eNodeB Data
Page2
Contents
1.1 Introduction to Structures of LTE Network
1.2 Flow Chart of Data Configuration
1.3 Introduction to Summary Data File

Page3

Configuration
LTE Transport Structure
Page4
Layer 1 Network

Page5

Configuration
Layer 2 Network
Page6
Layer 3 Network

Page7

Configuration
Overview of Transport Security
Page8
Contents

Page9

Configuration
Process of Configuring a Single

eNodeB
start
Prepare for configuration
Create a workspace
create an eNodeB(GUI mode)
configure the eNodeB data

Check and export the eNodeB configuration
end
Page10
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
Page11

Configuration
Contents
Page12
Summary Data File-Introduction

Currently, when creating eNodeBs in batches, users must fill in data

planning templates with a large number of planning parameters, which
decreases the efficiency. The CME provides a summary data file to
improve efficiency in creating eNodeBs.
Basic elements of the summary data file
MO
parameter
values
MOC
information
groups
MO
parameters
index

Page13

Configuration
Templates Introduction
LLD
tranform
Start here
Summary data file
Initial configuration
of eNodeB
link
eNode
B
radio/
cell
template
eNodeB
customized
template
Adjust
configuration
Radio
Cell
custo- custmized omized
templ- template
ate
export
import
export
export
Commissioning
eNodeB
import
Deployment list
RNP
eNodeB bulk
configuration
template
Customize eNodeB
configuration
Configuration data
Contents
4. Checking eNodeB Data
5. Exporting eNodeB Data

Page15

Configuration
Contents
2.1 Global Data
2.2 Device Data
2.3 Transport Data
2.4 Radio Data
Page16
Global Data Configuration Procedure

Start
Basic information about global data
Operator info
MME info
IP-Sec information(Optional)
S-GW info
Time and clock Info
End

Page17

Configuration
Operator info
Operator ID: Index of operator, one eNodeB can be shared by

maximum 6 operators
Operator name: The name of operator
Operator type: Indicates the type of the operator. The operator can
be the primary operator or a secondary operator.
MCC: Mobile Country Code
MNC: Mobile Network Code
Page18
MME Info
S-GW Info

Page19
10

Configuration
Time Source
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
Page20
Clock Info Clock Source

Page21
11

Configuration
Clock Info
Page22
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.

Page23
12

Configuration
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.
Page24
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.

Page25
13

Configuration
Security Globe Data (Optional)

If Security GW is deployed, relative info should be

configured in eNodeB, such as following info which should
be negotiated with peer security gateway
IKE Proposal
IKE Peer
IP-sec proposal
Page26
IP-Sec Configuration Overview

IP sec
proposal
IKE propose
IKE peer
ACL group
ACL rule
IP-sec policy

IP-sec Bind
Page27
14

Configuration
IP-sec Proposal
AH is a header authentication protocol. It mainly provides the

functions of data source authentication, data integrity check, and
replay protection. AH, however, does not implement encryption on
the protected data packets.
ESP is the packet security encapsulation protocol. In addition to

all functions provided by AH (its integrity check is not effective to
IP headers), ESP can provide encryption for IP packets.
Page28
IKE Proposal
The IKE protocol is based on the framework defined by the

Internet Security Association and Key Management Protocol
(ISAKMP). The IKE protocol provides IPSec with automatic
negotiation and cipher key exchange to simplify the use and
management of IPSec. The IKE negotiation process is the
process of establishing the security association.

Page29
15

Configuration
IKE Peer
IKEPeer: Indicates the name of the IKE peer.
ExchangeMode: Indicates the IKE exchange mode.
LocalIDType: Indicates the type of the identification payload that the

local end transmits. The authentication can be performed based on IP
or fully qualified domain name (FQDN).
DPD Mode: Indicates whether to enable the dead peer detection (DPD)
function.
Page30
ACL
ACL group configuration
The Access Control List (ACL) is an

instruction list for ports on routers and
switches, which is used to control packets
received on or transmitted from the port.
Applied to all router protocols, an ACL
contains matching relations, conditions,
and query commands. The ACL framework
ACL Pattern configuration is aimed at access control.

Page31
16

Configuration
IP-sec Policy
IP-sec Bind
Page32
Contents
2.1 Common Data (Global Data)
2.2 Equipment Data
2.3 Transport Data
2.4 Radio Data

Page33
17

Configuration
Basic eNodeB information
eNodeB Name, eNodeB Id

The data is planned by Telecom operators.
Page34
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.

Page35
18

Configuration
Contents
2.2 Equipment Data
2.3 Transport Data
2.4 Radio Data
Page36
S1 Interface

Page37
19

Configuration
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
Page38
Transport Data Configuration Procedure

Start
Link Layer Data
(Optional) VLAN information

VLANMAP
Network Layer Data
VLANCLASS
Transport Layer Data
End

Page39
20

Configuration
VLAN Introduction
VLAN1
VLAN2
VLAN3
VLAN4
VLAN has the following advantages:

Suppresses broadcast storm
Improves transmission security
Provides differentiated services
Page40
VLAN Solution
S1MME
VLAN1
S1-U
VLAN2
MME
VLAN1
VLAN2
MME
IP
Network
SGW
VLAN3
Solution 1 : VLAN is
OM
VLANn
S1MME
VLAN1
S1-U
VLAN2
OM
VLANn
IP
Network
Solution 2 : VLAN is
designed based on
designed based on traffic
eNodeB
type

SGW
Page41
21

Configuration

Start
Starte
Link Layer Data
d
IP configuration
Network Layer Data
IP Route configuration
End
Page42
Device IP Configuration
Device IP
LMPT/UMPT
Ethernet
link
Ethernet
trunk
LOO
PINT
UTRP
SUB
IF
PPP
link
MPGRP
link
LOO
PINT
Loopint ( Loopback interface) is a logic IP address used for

IP-sec inner IP address.

Page43
22

Configuration
Configuration Case
Page44
IP Route
Destination IP
LMPT
Next hop route
Destination Mask
Next hop IP
UMPT
Destination IP
Destination Mask
Exit Interface
Port Type
Port No.

Page45
23

Configuration
IP Route
Destination IP
Destination Mask
Next hop route
Next hop IP
UTRP
Destination IP
Destination Mask
Exit Interface
Port Type
Port No.
Page46

Start
Starte
Link Layer Data
d
Network Layer Data

S1 and X2 link info
OM channel Info
IP clock link info
End

Page47
24

Configuration
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
Page48
Template Based Configuration

Local node
information
Peer node
information

Page49
25

Configuration
MML Based Configuration Link

Mode
Page50
MML Based Configuration End Points

Mode

Page51
26

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

channel with the M2000
OMCH Mask
Local Maintenance
Remote Maintenance
LMT
M2000
Client
M2000 Server
Local OM IP
eNodeB
LMT
Remote OM IP
or
Page52
IP Clock Link

Page53
27

Configuration
Contents
2.2 Equipment Data
2.3 Transport Data
2.4 Radio Data
Page54
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
..

Page55
28

Configuration
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
Page56
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
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

20750-21449
Page57
29

Configuration
Carrier Frequency EARFCN

Calculation
Page58
Example
100kHz Raster
Uplink
Downlink
1937.4MHz
2127.4MHz
Frequency
FDL = FDL_low + 0.1(NDL - NOffs-DL)

NDL =
NDL =
(FDL - FDL_low)
0.1
+ NOffs-DL
(2127.4 - 2110)
+ 0 = 174
0.1

Page59
30

Configuration
RF Engineering parameters
Start
Started

Cell basic parameters
RF engineering parameters
Longitude
Latitude
Azimuth
Down title
TxRx Mode
Customized cell template
End
Page60
Neighbor Cell Data Configuration

Procedure
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

Page61
31

Configuration
Contents
4. Checking Data
5. Exporting Data
Page62
Contents
3. 1 Create a single eNodeB
3. 2 Create eNodeB in Batches

Page63
32

Configuration
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.
Page64
Creating a Planned Data Area

Set name
Set user group
Set access rights

Page65
33

Configuration
Opening a Planned Data Area
Page66
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


Page67
34

Configuration
Creating Initial Data of single

eNodeB(cont.)
Page68
Configuring eNodeB Equipment Data

Page69
35

Configuration
Configuring eNodeB Transport Data
Page70
Configuring eNodeB Radio Data

Page71
36

Configuration
Contents
3. 1 Create a single eNodeB
3. 2 Create eNodeB in Batches
Page72
Opening a Summary Data File
Select default or custom on required
Set path
See next page

Page73
37

Configuration
Customize Summary Data File

Create
empty sheet
Modify group
name
Check
rule
Deleted
selected
row
Sort by group
Set summary<->LLD
Page74
Creating Base Station Using

Summary
Select summary
data file
See next page

Page75
38

Configuration
Creating Base Station Using

Summary(cont.)
Select the
base station
Page76
Contents
4. Checking Data
5. Exporting Data

Page77
39

Configuration
Description of Checking the data Correctness,

Integrity, and Consistency
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.
Page78
Description of Checking the data

Correctness, Integrity, and
Consistency(cont.)
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.

Page79
40

Configuration
Checking the data Correctness and

Integrity
Page80
Checking the data Consistency
See next
page

Page81
41

Configuration
Checking the data Consistency(cont.)
Set rules
See next
page
Page82
Checking the data Consistency(cont.)

Page83
42

Configuration
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.
Page84
Contents
4. Checking Data
5. Exporting Data

Page85
43

Configuration
Exporting Auto Deployment Data
Select NE
See next page
Page86
Exporting Auto Deployment Data(cont.)
Set export
path
Set data
check

Page87
44

Configuration
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?
Page88
Thank you
www.huawei.com

45

Config PDF

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Config PDF

Enviado por

Direitos autorais:

Formatos disponíveis

eNodeB LTE V100R006 Initial

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

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

Describe LTE product networking

Outline functions of Summary data file

Outline the meaning of the common, equipment, transport data

Preparing eNodeB data

Configure eNodeB data

Check and export eNodeB data

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

Confidential Information of Huawei. No

eNodeB LTE V100R006 Initial

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

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

Confidential Information of Huawei. No

eNodeB LTE V100R006 Initial

LTE Transport Structure

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

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

Confidential Information of Huawei. No

eNodeB LTE V100R006 Initial

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

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

Confidential Information of Huawei. No

eNodeB LTE V100R006 Initial

Overview of Transport Security

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

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

Confidential Information of Huawei. No

eNodeB LTE V100R006 Initial

Process of Configuring a Single

Prepare for configuration

create an eNodeB(GUI mode)

configure the eNodeB data

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

Process of Configure Batch eNodeBs

Check and export eNodeB configuration

Edit the Summary/LLD

Import the radio data planning template

Edit the radio data planning template

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

Confidential Information of Huawei. No

eNodeB LTE V100R006 Initial

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

Summary Data File-Introduction

Currently, when creating eNodeBs in batches, users must fill in data

Basic elements of the summary data file

Confidential Information of Huawei. No

eNodeB LTE V100R006 Initial

Summary data file

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

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

Confidential Information of Huawei. No

eNodeB LTE V100R006 Initial

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

Global Data Configuration Procedure

Basic information about global data

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

Confidential Information of Huawei. No

eNodeB LTE V100R006 Initial

Operator ID: Index of operator, one eNodeB can be shared by

Operator name: The name of operator