Microsoft PowerPoint - 03 OEB304700 eNodeB LTE V100R006 Initial Configuration ISSUE 1

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
Page1
Confidential Information of Huawei. No Spreading Without Permission
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. eNodeB Data Configuration Introduction
1.1 Introduction to Structures of LTE Network 1.2 Flow Chart of Data Configuration 1.3 Introduction to Summary Data File
Page3
LTE Transport Structure
Page4
Layer 1 Network
Page5
Layer 2 Network
Page6
Layer 3 Network
Page7
Overview of Transport Security
Page8
Contents
Page9
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
Page10
Process of Configure Batch eNodeBs

start Create a workspace Prepare a template Customize the Summary/LLD Edit the Summary/LLD
Edit the radio data planning template
end
Check and export eNodeB configuration Import the radio data planning template
Import Summary/LLD
Page11
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
MO parameters
MOC information groups
index
Copyright 2013 Huawei Technologies Co., Ltd. All rights reserved. Page13
Templates Introduction
LLD
Start here
tranform
Summary data file

link
eNode B eNodeB
Initial configuration of eNodeB

Adjust configuration import export import export export
radio/ cell template
customized template
Radio Cell custo- custmized omized templ- template ate
RNP
eNodeB bulk configuration template
Commissioning eNodeB
Deployment list Configuration data
Customize eNodeB configuration
Contents
1. eNodeB Data Configuration Introduction 2. Preparing eNodeB Data 3. Creating eNodeB Data 4. Checking eNodeB Data 5. Exporting eNodeB Data
Page15
Contents
2. Preparing eNodeB Data
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
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
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
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.
12
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.
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
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
IP-sec policy
IP-sec Bind
ACL group
ACL rule
Page27
14
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.
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
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
The Access Control List (ACL) is an
ACL group configuration
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
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
Basic eNodeB information
eNodeB Name, eNodeB Id

The data is planned by Telecom operators.
Page34
eNodeB Template
Site Type
Currently, DBS3900_LTE,BTS3900_LTE,BTS3900A_LTE, BTS3900L_LTE and BTS3900AL_LTE are supported.
Version
Define the product version.
eNodeB Template
Define the template of eNodeB.
Base Station Configuration

Indicates Base Station Configuration specifies radio frequency (RF) cable connections.
Page35
18
Contents
Page36
S1 Interface
Page37
19
X2 Interface
X2 Control plane
X2-AP
X2 User plane
User plane PDUs
GTP-U SCTP IP Data link layer Physical layer UDP IP Data link 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
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 MME VLAN2
VLAN1
S1-U
MME
OM VLANn IP Network SGW
VLAN2
IP Network
SGW
S1MME S1-U
VLAN1 VLAN2
VLAN3
OM
VLANn
Solution 1 : VLAN is designed based on eNodeB
Solution 2 : VLAN is designed based on traffic type
Page41
21

Start Starte Link Layer Data d
Network Layer Data
IP configuration IP Route configuration
End
Page42
Device IP Configuration
Device IP
LMPT/UMPT
UTRP
Ethernet link
Ethernet trunk
LOO PINT
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 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
IP Route
Destination IP Next hop route Destination Mask 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
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
MML Based Configuration Link Mode
Page50
MML Based Configuration End Points Mode
Page51
26
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
or LMT
eNodeB
Remote OM IP
Page52
IP Clock Link
Page53
27
Contents
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
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
LTE Release 9 Bands

Band Duplex FDL_low (MHz) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD 2110 1930 1805 2110 869 875 2620 925 1844.9 2110 1475.9 728 746 758 FDL_high (MHz) 2170 1990 1880 2155 894 885 2690 960 1879.9 2170 1500.9 746 756 768 0 600 1200 1950 2400 2650 2750 3450 3800 4150 4750 5000 5180 5280 0-599 600-1199 1200-1949 1950-2399 2400-2649 2650-2749 2750-3449 3450-3799 3800-4149 4150-4749 4750-4999 5000-5179 5180-5279 5280-5379 NOffs-DL NDL FUL_low (MHz) 1920 1850 1710 1710 824 830 2500 880 1749.9 1710 1427.9 698 777 788 FUL_high (MHz) 1980 1910 1785 1755 849 840 2570 915 1784.9 1770 1452.9 716 787 798 18000 18600 19200 19950 20400 20650 20750 21450 21800 22150 22750 23000 23180 23280 18000-18599 18600-19199 19200-19949 19950-20399 20400-20649 20650-20749 20750-21449 21450-21799 21800-22149 22150-22749 22750-22999 23000-23179 23180-23279 23280-23379 NOffs-UL NUL
17
FDD
734
746
5730
5730-5849
704
716
23730
23730-23849
33 34 35 36 37 38 39 40
TDD TDD TDD TDD TDD TDD TDD TDD
1900 2010 1850 1930 1910 2570 1880 2300
1920 2025 1910 1990 1930 2620 1920 2400
26000 26200 26350 26950 27550 27750 28250 28650
36000-36199 1900 36200-36349 2010 36350-36949 1850 36950-37549 1930 37550-37749 1910 37750-38249 2570 38250-38649 1880 38650-39649 2300
1920 2025 1910 1990 1930 2620 1920 2400
36000 36200 36350 36950 37550 37750 38250 38650
36000-36199 36200-36349 36350-36949 36950-37549 37550-37749 37750-38249 38250-38649 38650-39649
Page57
29
Carrier Frequency EARFCN Calculation
Page58
Example
100kHz Raster Uplink Downlink
1937.4MHz
2127.4MHz FDL = FDL_low + 0.1(NDL - NOffs-DL) NDL = (FDL - FDL_low) 0.1 + NOffs-DL
Frequency
NDL =
(2127.4 - 2110) + 0 = 174 0.1
Page59
30
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
Contents
1. eNodeB Data Configuration Introduction 2. Preparing eNodeB Data 3. Creating eNodeB Data 4. Checking Data 5. Exporting Data
Page62
Contents
3. Creating eNodeB Data
3. 1 Create a single eNodeB 3. 2 Create eNodeB in Batches
Page63
32
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.
Creating a Planned Data Area

Set name Set user group
Set access rights
Page65
33
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

34
Creating Initial Data of single eNodeB(cont.)
Page68
Configuring eNodeB Equipment Data
Page69
35
Configuring eNodeB Transport Data
Page70
Configuring eNodeB Radio Data
Page71
36
Contents
3. Creating eNodeB Data
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
Customize Summary Data File

Create empty sheet Check rule Modify group name
Deleted selected row
Sort by group
Set summary<->LLD
Page74
Creating Base Station Using Summary
Select summary data file
See next page
Page75
38
Creating Base Station Using Summary(cont.)
Select the base station
Page76
Contents
Page77
39
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
Checking the data Correctness and Integrity
Page80
Checking the data Consistency
See next page
Page81
41
Checking the data Consistency(cont.)
Set rules See next page

Checking the data Consistency(cont.)
Page83
42
Recovering Data Based on the Consistency Check Results

Recovery types: AutoFix: Double-click a data record. > Select the recovery type. > Select AutoFix. If Operation is set to AutoFix, the CME automatically recovers data. You do not need to specify any information. Refresh: 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
Page85
43
Exporting Auto Deployment Data
Select NE
See next page
Page86
Exporting Auto Deployment Data(cont.)
Set export path Set data check
Page87
44
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

Microsoft PowerPoint - 03 OEB304700 eNodeB LTE V100R006 Initial Configuration ISSUE 1

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Microsoft PowerPoint - 03 OEB304700 eNodeB LTE V100R006 Initial Configuration ISSUE 1

Caricato da

Copyright:

Formati disponibili

eNodeB LTE V100R006 Initial Configuration

eNodeB LTE V100R006 Initial Configuration

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

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

Confidential Information of Huawei. No Spreading Without Permission

eNodeB LTE V100R006 Initial Configuration

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

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

Confidential Information of Huawei. No Spreading Without Permission

eNodeB LTE V100R006 Initial Configuration

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 Spreading Without Permission

eNodeB LTE V100R006 Initial Configuration

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

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

Confidential Information of Huawei. No Spreading Without Permission

eNodeB LTE V100R006 Initial Configuration

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 Spreading Without Permission

eNodeB LTE V100R006 Initial Configuration

Process of Configuring a Single eNodeB

create an eNodeB(GUI mode)

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

Process of Configure Batch eNodeBs

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

Confidential Information of Huawei. No Spreading Without Permission

eNodeB LTE V100R006 Initial Configuration

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

Summary Data File-Introduction

MOC information groups

Confidential Information of Huawei. No Spreading Without Permission

eNodeB LTE V100R006 Initial Configuration

Summary data file

Initial configuration of eNodeB

radio/ cell template

Radio Cell custo- custmized omized templ- template ate

Deployment list Configuration data

Customize eNodeB configuration

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

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

Confidential Information of Huawei. No Spreading Without Permission

eNodeB LTE V100R006 Initial Configuration

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

Global Data Configuration Procedure

Basic information about global data

Operator info MME info

S-GW info Time and clock Info

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

Confidential Information of Huawei. No Spreading Without Permission

eNodeB LTE V100R006 Initial Configuration

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

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

Confidential Information of Huawei. No Spreading Without Permission

eNodeB LTE V100R006 Initial Configuration

Time Source Time Source

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

Clock Info Clock Source

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

Confidential Information of Huawei. No Spreading Without Permission