Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
TMO18213_V4.0-SG Edition 10
Course outline
4. Topic/Section is Positioned Here
1. RAN TLA3.0-LA4.0 Technical Overview
Welcome
to 9400Overview
LTE
1.
LTE eUTRAN
5. Topic/Section is Positioned Here
2.
LTETLA3.0-LA4.0
Transport overview
RAN
Technical Overview
3. LTE eNodeB Hardware Description
6. Topic/Section is Positioned Here
4. LTE RAN OAM description
1. RAN TLA3.0-LA4.0 Technical Overview
1. LTE eUTRAN Overview
3
9400 LTE
RAN TLA3.0-LA4.0 Technical Overview
Course objectives
RAN
TLA3.0-LA4.0
Technical
Overview
Describe
the IP transport
layer in the radio
Access Network
z
z
z
z
Describe
Describe
Describe
Describe
4
9400 LTE
RAN TLA3.0-LA4.0 Technical Overview
11
Section 1
RAN TLA3.0-LA4.0 Technical
Overview
Module 1
LTE eUTRAN Overview
9400 LTE
RAN TLA3.0-LA4.0 Technical Overview
TMO18213_V4.0-SG Edition 10
Blank page
112
Document History
Edition
Date
Author
Remarks
10
2012-02-01
Vincent, Cecile
Edition 10
Module objectives
Upon completion of this module, you should be able to:
Describe the eUTRAN architecture
List Network Elements and their functions
Describe interface names
Describe the protocol stack for User and Control Planes
Explain FDD and TDD transmission principles, OFDMA (Orthogonal FrequencyDivision Multiple Access) modulation scheme and MIMO (Multiple Input Multiple
Output) antenna technic.
List supported Mobility features
Describe eNodeB advanced features, (common to FDD et TDD, dedicated to
FDD or to TDD)
113
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
114
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Table of Contents
Switch to notes view!
1 EnodeB functions and protocols
1.1 eNodeB functions
1.2 LTE-Uu Radio interface
1.3 S1 interface
1.4 MME Overload Indication support
2 Air Interface Basics
2.1 FDD and TDD introduction
2.2 LTE frequency bands
2.3 OFDMA
2.4 MIMO
2.5 One antenna/single antenna transmit mode
3 Mobility in LTE
3.1 UE in Active or Idle mode
3.2 X2 interface
3.3 Intra-LTE mobility
3.4 Intra-LTE Inter-Frequency Mobility
3.5 supported IRAT Mobility in FDD
3.6 supported IRAT Mobility in TDD
4 FDD advanced features
4.1 Public Warning Systems in LTE network
4.1.1 CMAS principles
5 TDD advanced features
5.1 Beamforming
1 1 5 5.2 eMBMS
COPYRIGHT ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.
RAN TLA3.0-LA4.0
Technical eMBMS
Overview LTE eUTRAN
Overview
5.2.1
interfaces
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
5.2.2 eMBMS Alcatel-Lucent solution, phase 1
Page
7
8
9
11
13
18
19
21
22
23
24
26
27
28
29
31
32
34
36
37
38
39
40
42
43
44
116
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
117
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
eUTRAN
MME
eNodeB
Dynamic Resource
Allocation
(Scheduler)
NAS Security
Idle State Mobility
Handling
RB Control
RRC Connection
Admission control
Mobility
Anchoring
Measurement
Configuration
Packet
Filtering
eNodeB Functions
118
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
UE IP address
allocation
eNB Functions:
It schedules the user traffic each 1 ms in DL and UL and it takes in account the QoS parameters
MME Functions :
NAS (Non Access Stratum) signaling and NAS signaling security,
NAS Security control,
Inter Core Network node signaling for mobility between 3GPP access networks,
Idle mode UE reachability (including control and execution of paging retransmission) and Tracking Area
PDN GW and Serving GW selection, MME selection for handovers with MME change, SGSN selection for
Roaming,
Authentication,
Bearer management functions including dedicated bearer establishment,
Control Plane
User Plane
Control Plane
NAS
NAS
RRC
Radio Signaling
RRC
PDCP
PDCP
Radio Bearer
RLC
RLC
Logical Channel
MAC Layer
MAC Layer
Transport Channel
Physical Layer
Physical Layer
Physical Channel
119
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Physical (PHY) Sublayer : The physical layer is between the UE and the eNodeB. The physical layer in
LTE supports the Hybrid ARQ with soft combining, uplink power control and multi-stream transmission and
reception (MIMO).
Media Access Control (MAC) Sublayer : The MAC sublayer is between the UE and the eNodeB. MAC
sublayer performs error correction through HARQ, priority handling across UEs as well as across different
logical channels of a UE, traffic volume measurement reporting, and multiplexing/demultiplexing of different
RLC Sublayer. For the user plane, the PDCP sublayer performs header compression and ciphering.
Radio Link Control (RLC) Sublayer : The RLC sublayer is between the UE and the eNodeB. Along with
transferring upper layer PDUs. The RLC does error correction through ARQ, in-sequence delivery of upper
layer PDUs, duplicate detection, and flow control and concatenation/re-assembly of packets.
Packet Data Convergence Protocol (PDCP) Sublayer : For the user plane, the PDCP sublayer
performs header compression and ciphering.
Radio Resource Control (RRC) Sublayer : The RRC sublayer is between the UE and the eNodeB. The
RRC sublayer in essence performs broadcasting, paging, connection management, radio bearer control,
mobility functions, and UE measurement reporting and control.
Non Access Stratum (NAS) Sublayer : The NAS sublayer is between the UE and the MME. It performs
authentication, security control, idle mode mobility handling, and idle mode paging origination.
Transport Channels:
Logical channels:
On RRC level, System information is divided into the MasterInformationBlock (MIB) and a number of
SystemInformationBlocks (SIBs). The MIB includes a limited number of most essential and most frequently
transmitted parameters and is transmitted on BCH.
SIB are transmitted over DL-SCH.
1.3 S1 interface
eNodeB
SGW
IP (user)
IP (user)
GTP - U
GTP - U
PDCP
PDCP
Uu L2
RLC
RLC
MAC
MAC
Phy (L1)
Phy (L1)
UDP
UDP
IP (path)
IP (path)
Phy
Phy
LTE Uu
1 1 11
S1-U
When the UE send in UL an IP packet, it is treated by the LTE radio protocol before being transmitted
over the air interface. After the reception, the eNodeB send this data on the GTP tunnel (S1 bearer) to
the SGW.
S1-U (user plane)
The S1 user plane external interface (S1-U) is defined between the eNodeB and the S-GW. The S1-U
interface provides non guaranteed data delivery of user plane Protocol Data Units (PDUs) between the
eNodeB and the S-GW. Transport network layer is built on IP transport and GTP-U. UDP/IP carries the
user plane PDUs between the eNodeB and the S-GW. A GTP tunnel per radio bearer carries user traffic.
The S1-UP interface is responsible for delivering user data between the eNodeB and the S-GW. The IP
Differentiated Service Code Point (DSCP) marking is supported for QoS per radio bearer.
UE
User Apps
MME
eNodeB
NAS
NAS
RRC
RRC
S1 - AP-
S1 - AP
PDCP
PDCP
Uu L2
RLC
RLC
MAC
MAC
Phy (L1)
Phy (L1)
SCTP
SCTP
IP
IP
Phy
Phy
LTE Uu
1 1 12
S1-MME
UE
load
Over
st art
MME 2
1 1 13
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The purpose of the Overload Start / Stop procedures (3GPP TS 36.413 release 9) is to inform an eNodeB
to reduce the signaling load towards the MME.
The eNB realizes MME Selection : new entering calls, should not be established towards an overloaded MME.
The eNodeB that receives an OVERLOAD START message assumes the MME is in an overloaded state.
The message contains indication on signaling traffic (permitted RRC connections) the eNodeB is permitted
to send to the MME :
reject all RRC connection establishments for non-emergency mobile originated data transfer
reject all RRC connection establishments for signaling
only permit RRC connection establishments for emergency sessions and mobile terminated services
When receiving a RRC establishment request for an overloaded MME, the eNB checks the establishment
cause value included in the request and determines if it should accept or reject the RRC Connection.
In case of reject, the eNB sends back to the UE aRRCConnectionReject message with a waitTime set to
parameter UeTimers:tOverload value.
The eNB receiving the OVERLOAD STOP message assumes that the overload situation at the MME has
ended and the eNodeB resumes normal operation towards this MME.
Handovers are not impacted by Overload procedure: any S1 or X2 Handover related to an overloaded MME
are handled normally.
Copyright 2012 Alcatel-Lucent. All Rights Reserved.
TMO18213_V4.0-SG-Ed10 Module 1.1 Edition NA
Section 1 Module 1 Page 13
MME
Tracking Area Update request
including GUTI
Overload stop
1 1 14
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Following mapping is performed between Overload Action and RRCConnection Establishment Cause
(EC)values:
RRC
accepted
rejected
accepted
rejected
MO
rejected
rejected
rejected
There is a mapping defined between NAS procedures and establishment causes. The relationship is
specified in 3GPP TS 24.301 Annex D.
For example :
Attach, Detach and Tracking Area Update procedures EC = MO Signalling
Service request for Paging response or mobile terminating call CSFB EC = MT Access
Service request for Mobile originating services EC = MO Data
Copyright 2012 Alcatel-Lucent. All Rights Reserved.
TMO18213_V4.0-SG-Ed10 Module 1.1 Edition NA
Section 1 Module 1 Page 14
Data
Name of the
interface
S1-U
Between
NAS
LTE-Uu
UE and eNodeB
GTP-U
RRC
S1-MME
Name of the
interface
S1-U
Between
NAS
LTE-Uu
UE and eNodeB
GTP-U
RRC
S1-MME
SCTP
1 1 15
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
S1-MME ?
IPv4
IPv6
TCP
UDP
SCTP
IPv4
IPv6
TCP
UDP
SCTP
In the TCP/IP suite, what is (are) the layer 3 protocol(s) used for
interfaces :
S1-U?
S1-MME ?
IPv4
IPv6
TCP
UDP
SCTP
IPv4
IPv6
TCP
UDP
SCTP
1 1 16
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
To
To
To
To
1 1 17
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
1 1 18
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
DL
UL
DL
UL
time
DL
UL
DL
frequency
UL
1 1 19
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
time
With FDD, DL and UL transmissions are performed simultaneously in two different frequency bands.
With TDD, DL and UL transmissions are performed at different time intervals within the same
frequency band.
3GPP TS 36.xxx
TDD-LTE
(set of LTE specs)
ePC
Channel BW
Sub-frame duration
1 ms
Frame duration
Ratio (DL:UL)
10ms
5ms, 10ms
1:1
This table illustrates the LTE TDD and FDD bands defined by 3GPP . The 3GPP has defined all these
frequencies, but all these bands are not available for LTE in each country.
LA4.0 modulation schemes : QPSK, 16QAM, 64QAM (UL & DL)
For TDD, 3GPP has defined 7 uplink-downlink allocation configurations (config 0 to 2 for 5 ms frame and
3 to 6 for 10ms frame). TLA3.0 supports configuration 1 (2:2) and configuration 2 (3:1).
1900Mhz
PCS
1GHz
2GHz
2.3 GHz 2.6 GHz
New band for LTE only
TDD
FDD and TDD
700 MHz
US DD
FDD
800 MHz
EDD
AWS
DCS
1800 Mhz
LA4.0
FDD
TLA3.0
1 1 21
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
DD means Digital Dividend, it refers to the frequency band frees by the end of the analogical TV.
700Mhz frequency band on band 17/12 and 13 are available in LA3.0.
The AWS bands are for 1710-1755 MHz and 2110-2155 MHz.
2.3 OFDMA
In TDMA, the UE communications are separated in
time.
Example: GSM
User 1
1 1 22
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
User 2
User 3
2.4 MIMO
1 1 23
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Transmissions from each antenna must be uniquely identifiable so that each receiver can determine what
combination of transmissions has been received.
The UE needs to know the spatial signature of each transmission path : this identification is usually done
with pilot signals, which use orthogonal patterns for each antenna.
In TDD, the RRH (Remote Radio Head) module provides the RF part of the eNodeB. Depending on the
RRH, the eNodeB includes two or eight RF transmitters to enable 2x2 MIMO application.
Sector 1
FDD
only
RF
module
BBU
1 1 24
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
This feature supports single antenna mode (one transmit path only) as an official configuration on eNB.
Single antenna mode configuration allows:
- deployment scenarios that require single antenna operation for cost reason.
- degraded mode operation even when two antenna mode is configured in the case of one transmit path
failure by continuing to support users at maximum capacity.
When there is transmit path failure, eNB shall automatically transition to the pseudo single antenna
transmission mode without operator intervention via DCI change. The eNB shall operate in the pseudo
SIMO mode (Transmit diversity) after the transition.
Performance degradation (including call drops) is expected during this transition, especially for cell edge
users. Operator could decide whether to continue operating in the pseudo SIMO mode or switch to the
true SIMO mode by cell reconfiguration
1 1 25
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
3 Mobility in LTE
1 1 26
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
3 Mobility in LTE
DRB
S1 Bearer
UE is in RRC-CONNECTED state
PDN
S5 Bearers
PGW
SGW
PDN
S5 Bearers
SGW
PGW
UE is in RRC-IDLE state
1 1 27
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
In idle mode,
no UE context information is stored in E-UTRAN : no S1_MME, no S1_U connection for the UE.
The UE is known in EPC and has IP address
The UE location is known on a per Tracking Area level and UE can be reached after beeing paged by
the ePC.
3 Mobility in LTE
3.2 X2 interface
eUTRAN
X2-C interface
X2-U interface
X2-AP
GTP-U
SCTP
UDP
IP
IP
Physical layer
Physical layer
eNodeB
X2-C
X2-U
X2
eNodeB
Alcatel-Lucent
ENodeB
User
Control
Third party
eNodeB
1 1 28
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
z context
z control
z
handover cancellation
z uplink
load management
z general
z error
X2 management
handling
LA3.0 and TLA3.0 eNodeB offer True open X2 interface to Third party eNodeBs.
3 Mobility in LTE
Serving MME
Serving eNB
MME
1 Measurement
Direct forwarding
Target MME
2 HO preparation
3 HO Execution
Direct forwarding
4 HO Completion
Serving eNB
User
Control
SGW
Target eNB
SGW
Target eNB
SGW
indirect forwarding
SGW
A handover operation requires transfer of information necessary to maintain the LTE RAN services at
the new eNodeB. It also requires establishment and release of tunnels between source and target
eNodeB to allow data forwarding and inform the already prepared target eNodeB for handover
cancellations.
ALU solution supports lossless Intra-LTE Mobility with buffered PDCP packet forwarding over X2 interface.
There is no need to indicate neighbouring cell in the serving cell system information, E-UTRAN
relies on the UE to detect the neighbouring cells.
For the search and measurement of inter-frequency neighbouring cells, only the carrier
frequencies need to be indicated.
Cell reselection identifies the cell that the UE should camp on. It is based on cell reselection criteria :
3 Mobility in LTE
SGW
Measurement Control
Radio bearers
S1 Bearers
Packet data exchanged
Measurement Report
RSRP
Serving Cell
HO
decision
Cell1
UE triggers intra-frequency
measurements
1 1 30
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Timer
Cell 1 is Reselected
For each carrier frequency measurement, one or several reporting configurations can be defined. This
reporting configuration defines the reporting criteria : event triggered reporting, periodic reporting.
Two basic UE measurement quantities shall be supported: Reference symbol received power (RSRP) and
E-UTRA carrier received signal strength indicator (RSSI).
Events correspond to UE measurement quantities that matches criterias based on defined thresholds.
Example : the Neighbour RSRP becomes better than the serving cell ones.
Measurement commands are used by eNB to order the UE to start measurements, modify measurements
or stop measurements. The measurements for intra/inter-frequency mobility can be controlled by eNB,
using broadcast or dedicated control.
In RRC_IDLE state, a UE shall follow the measurement parameters defined for cell reselection specified
by the E-UTRAN broadcast.
In RRC_CONNECTED state, a UE shall follow the measurement configurations specified by RRC directed
from the eNB.
They are Intra-frequency neighbour (cell) measurements and inter-frequency neighbour (cell)
measurements (The UE should not be assumed to be able to carry out such measurements without
measurement gaps.)
3 Mobility in LTE
800 MHZ
2,6GHZ
2,6GHZ
Inter eNodeB
Intra band
Inter freq HO
Inter eNodeB
inter band
Inter freq
HO
2,6GHZ
1 1 31
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The Intra-LTE Inter-Frequency Mobility is supported on FDD and on TDD systems (respectively
FDD<>FDD and TDD<>TDD).
It concerns mobility of multi-frequency/band UE (in RRC IDLE or RRC-CONNECTED state) moving
from a cell operating at a LTE frequency to another cell operating at a different LTE frequency within or
in a different frequency band.
The two LTE cells operating at different carrier frequency can be either collocated or adjacent (intra or
inter-eNodeB).
This feature in LA3.0/TLA3 covers :
z Intra-eNB inter- FDD frequency, same band handover
Inter-eNB inter- FDD band handover
z Intra-eNB
3 Mobility in LTE
UE connected
LTE coverage lost
No PS HO support
LA4.0
W or w/o NACC
LTE
GSM
LTE
GSM
Cell reselection
LTE UMTS
LTE
LTE UMTS
LTE
CDMA
LTE UMTS
Cell redirection
PS HO
CSFB
CDMA
Data continuity
Mobility in idle
1 1 32
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
LA3.0
EUTRAN-to-UTRAN Cell reselection and Redirection and PS Handover
EUTRA-to-GERAN Cell Reselection and Redirection
EUTRA-to-GERAN PS mobility via Network Assisted Cell Change (NACC) procedure.
CS Fallback to GERAN for Voice Calls
HRPD to LTE mobility, UE in idle state
LTE to HRPD mobility : cell reselection and redirection
LA4.0
CS Fallback to 1XRTT for Voice Calls : Dual receiver UE Standard based solution. The Dual-receiver
solution includes a UE that is capable to camp on both LTE and CDMA 1X RTT mode simultaneously. The
UE autonomously selects LTE for data services and CDMA 1XRTT circuit domain for voice
LTE and 1xRTT cell reselection
3 Mobility in LTE
LTE
GSM
LTE
LTE
CDMA
CSFB
UMTS
Voice continuity
1 1 33
Cell reselection
Cell redirection
PS HO
LA4.0
3 Mobility in LTE
UE is idle
UE connected
LTE coverage lost
No PS HO support
Cell reselection
Cell redirection
PS HO
CSFB
W or w/o NACC
TD-LTE
TD-LTE
GSM
UMTS
TD-LTE
GSM
TD-LTE
Mobility in idle
LTE
UMTS
TD-LTE
UMTS
UMTS
Voice continuity
Data continuity
1 1 34
LTE
GSM
D t
ti
it
This slide shows eUTRAN (TDD) to UTRAN (TDD) mobility only. UMTS in TDD is also called TD-SCDMA.
TLA2.0 :
eUTRAN to GERAN Inter-RAT Mobility Cell Reselection and redirection LA2.0
LTE to TD-SCDMA PS HO
TLA3.0 :
CS Fallback to UTRA for Voice Calls
CS Fallback to GERAN for Voice Calls
EUTRA-to-GERAN Inter-RAT Mobility NACC
LTE to TD-SCDMA cell reselection and redirection
TDSCDMA to eUTRAN IRAT PS Handover
1 1 35
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
1 1 36
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
LTE-Uu
UE
SBc
S1-MME
eNodeB
Gouvernent
MME
CBC
CMSP GW
Alert GW
1 1 37
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
CMAS messages are transmitted using control plane signaling only, no user plane
bearer is required.
y Write-replace Warning Req./resp. messages and Stop Warning req/resp. messages
are used between the CBC and the MME
y Write-replace Warning Req./resp. and Kill req./resp. are used between the CBC
and the MME.
On CMAS indication reception
the UE acquires SIB12
3
CMAS indication
On Paging Control channel
Write-replace req.
Write-replace req.
2
CMAS Notification
On SIB12
Write-replace resp.
eNodeB
Write-replace resp.
MME
CBC
1 1 38
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The purpose of the Kill procedure is to cancel an already ongoing broadcast of warning
message.
E-UTRAN initiates the paging procedure : The PAGING message is used to inform CMAS (Commercial
Mobile Alert System) capable UEs (RRC_IDLE or RRC_CONNECTED UE) about presence of CMAS
notifications : cmas-Indication is included in the PAGING message transmitted on PCCH PCH
PDSCH channels.
Paging is realized on Logical Channel PCCH & Transport Channel DL-SCH. CMAS-indication is transmitted
in every Paging Occasion at the start of the CMAS transmission.
The UE reads SIB1 to know when SIB12 is scheduled (silent SIB1 update).
The UE re-acquires SIB12 immediately to retrieve CMAS-notification (SIB12 BCCH DL-SCH
PDSCH), that contains a CMAS message (or message segment).
1 1 39
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
5.1 Beamforming
Multiple transmit antennas are used to form a beam towards one user. This realized
by controlling the phase and the amplitude of the antenna dipoles separately.
Beamforming is performed only on the eNodeB side (DL).
RF
module
BBU
1 1 40
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Multiple transmit antennas can be used to shape the overall antenna beam in the direction of a target
receiver. In general, such beamforming can increase the signal-strength at the receiver in proportion to the
number of transmit antennas.
The overall transmission beam can be adjusted in different directions by applying different phase shifts to
the signals to be transmitted on the different antennas. The adjustments are generally based on estimates
of the direction to the target mobile terminal derived from feedback measurements.
In general, the different multi-antenna techniques are beneficial in different scenarios. As an example, at
relatively low SINR, such as at high load or at the cell edge, spatial multiplexing provides relatively limited
benefits. Instead, in such scenarios, multiple antennas at the transmitter side should be used to raise the
SINR by means of beam-forming. On the other hand, in scenarios where there already is a relatively high
SINR, raising the signal quality further provides relatively minor gains. In such scenarios, spatial
multiplexing should be used instead in order to fully exploit the good channel conditions and increase the
rate. The multi-antenna scheme used is under control of the eNB, which therefore can select a suitable
scheme for each transmission
RF module RRH
1 1 41
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
TD-LTE 2.6GHZ eNodeB Configuration needs a d2UV5 for the 8-antenna beamforming application:
1eCCM-U + 2 bCEMs for 3x15MHz sectors with 8-antenna Beamforming;
1eCCM-U + 3 bCEM for 3x10MHz sectors with 8-antenna Beamforming;
1eCCM-U + 1 bCEM for 3x5MHz sectors with 8-antenna Beamforming
1eCCM-U + 1 bCEM for 6x5MHz sectors with 8-antenna Beamforming;
5.2 eMBMS
Tight synchronization
needeed on
eNodeB
BM-SC
MBMS GW
eNodeB
MCE
UE
Allocates radio
ressources
1 1 42
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
e-MBMS provides Broadcast and multicast transport services, ie. unidirectional point-to-multi-point
transmissions of multimedia data. One of the main benefits of eMBMS is the resource savings in the
network as a single stream of data may serve multiple users (all for broadcast services, a set of
subscribers for multicast services).
eMBMS transmissions can be :
z
zA
multi-cell transmission. The terminal can combine multiple signals from multiple synchronized cells
as multi-path transmissions. This transmission scheme is called Multimedia Broadcast multicast
service over a Single Frequency Network (MBSFN). A MBSFN requires content-synchronized and
time-synchronized set of cells, they compose a MBSFN area. An MBMS service area can be
composed of several MBSFN areas.
The BM-SC (Broadcast Multicast Service Centre) provides the MBMS service to the end user. It is the
entry point for content provider, it assumes authentication/authorization of requesting users and
manages sessions and data functions.
Multi-cell/multicast Coordination Entity (MCE) is a logical entity that allocates the radio resources used by
all eNodeBs in the MBSFN area for multi-cell MBMS transmissions and decides the modulation and coding
scheme.
E-MBMS Gateway (MBMS GW) is a logical entity that :
z sends
content provider data to each eNodeB transmitting the service, using IP Multicast.
z performs
5.2 eMBMS
MME
M3
Sm
BM-SC
SGmb
M2
M1
MBMS GW
SGi-mb
Service
announcement
1
UE
eNodeB
Session
start/stop
2 Service joining
4 Service leaving
1 1 43
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
M3 Interface between the MCE and the MME is used for eMBMS Session Control Signalling on E-RAB
level including eMBMS Session Start and Stop. M3 is SCTP based.
M2 Interface between MCE and eNB: is used to convey radio configuration data for the multi-cell
transmission and Session Control Signalling. M2 iq SCTP based.
M1 Interface between MBMS GW and eNodeB is a user plane interface used to transport user IP
Multicast flows.
The Subscription phase, for multicast service, links the end-user to the service or content provider to
allow the end-user to receive the multicast service.
The end-users are informed about the available MBMS services during the Service announcement
phase.
They then need to join multicast service (they can then be charged for the multicast data).
Then MBMS session starts : the MBMS bearers are then reserved and established and the data are
transferred to the UE.
The users are then informed, during the the MBMS notification phase, of the upcoming MBMS
sessions.
At Session stop, ressources are released by the network. The user indicates that he no longer wants to
subscribe to the session in the leaving phase.
5.2 eMBMS
5620 SAM
Operator
command to
start MBMS
service
MCE
M2
TLA3.0
BM-SC
SGmb
M1
SGi-mb
UE
eNodeB
User
MBMS GW
Control
5910 MiTV
1 1 44
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Then, the session is stopped first on MiTV EMS and after on 5620 SAM.
All the necessary information for the eMBMS service is pre-provisionned in the eNodeB and MiTV. For
example, the multicast IP flow is characterized by a GTP-U C-TEID and an multicast destination IP
address. The MBMS-GW marks the M1 Ip traffic with provisonned DSCP value.
A MBSFN area is composed of a group of cells. All enodeB involved in the MBSFN area use the same
radio frequency and have the same MBMS radio ressource allocation. This radio ressource allocation is
statically configured in phase 1.
MTCH and MCH channels are used for radio transmissions.
Layer 1 timing synchronization on the different cells is realized thanks to GPS in TLA3.0. BM-SC should
also be synchronized to a GPS source to provide timing accuracy for content synchronization for multi-cell
transmissions.
End of module
LTE eUTRAN Overview
1 1 45
RAN TLA3.0-LA4.0 Technical Overview LTE eUTRAN Overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
12
Section 1
RAN TLA3.0-LA4.0 Technical
Overview
Module 2
LTE Transport overview
9400 LTE
RAN TLA3.0-LA4.0 Technical Overview
TMO18213_V4.0-SG Edition 10
Blank page
122
Document History
Edition
Date
Author
10
2012-02-01
Vincent, Cecile
Remarks
Module objectives
Upon completion of this module, you should be able to:
Describe the eUTRAN transport architecture,
Explain the Ethernet and IP eNodeB transport configuration (i.e., VLAN, IP
addressing and IP Security (IPSEC),
Explain the eNodeB SCTP configuration and timers,
Describe IP Quality of Service (QoS) mechanisms used on LTE transport
network,
Describe synchronization solution for eUTRAN.
123
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
124
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Table of Contents
Switch to notes view!
1 Transport Network Requirements
1.1 End-to-End IP
2 Traffic Aggregation
2.1 Aggregation with 7705 SAR-F
2.2 7705 SAR-F
3 VLANs
3.1 eNodeB VLAN overview
3.2 Third VLAN in TDD configuration
4 IP addressing
4.1 IPv4 Addressing
4.2 IPv6 addressing
4.3 IPv6 configurations
4.4 DHCP process
5 IPSec
5.1 UE Security
5.2 IPSec LTE configurations
5.3 IPSec LTE Policies
6 SCTP Protocol
6.1 STP associations
6.2 SCTP Multi-homing
6.3 SCTP Timers
6.4 SCTP Failover Time Tuning
7 QoS
1 2 5 7.1 Introduction
COPYRIGHT ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.
RAN TLA3.0-LA4.0
LTE QoS
Transport parameters
overview
7.2 Technical
EPS Overview
bearer
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
7.3 QoS mapping on transport network
7.4 eNodeB traffic Management
7.5 eNodeB UL traffic Shaping
7.6 eNodeB Call Admission
8 Synchronization
8.1 Synchronization overview
8.2 Synchronization need for Handover
8.3 Synchronization need for TDD systems
8.4 Possible solutions
8.5 SyncE Principles
8.6 PTP principles
Page
7
8
9
10
11
13
14
16
20
21
22
23
26
28
29
32
34
38
39
40
41
42
45
46
47
48
50
51
53
55
56
57
58
59
61
62
126
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Page
127
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
1.1 End-to-End IP
EUTRAN + EPC + Backhaul + Backbone = All-IP service delivery
Real-time, multiservice, high-bandwidth, end-to-end QoS
Traffic segregation
VLAN
QoS Management
DiffServ
IP Communications
(VoIP, Video)
Messaging SMS/MMS
Internet, Web 2.0
Advanced Location-based
Services
Mobile TV, IP Multimedia
Mobile office
IP channel
SGW
eNode B
Synchronization
IP Backhaul
Aggregation of sites
traffic
128
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
MME
PCRF
PDN GW
Security
Traffic Encryption and
authentication
LTE network is based natively on IP : all services are carried over IP from the mobile to the service
network.
LTE requires high data rates and offers a larger number of services that requires different QoS treatments
(real time services with low delay, guaranteed bit rate, low error rate ): as a consequence the transport
network needs to support high capacity and QoS management capabilities.
The transport network carries telecom traffic (signaling and user data), OAM traffic and Debug traffic. All
these types of traffic has to be separated in the transport network using VLANs.
The different natures of data (control plane traffic like signaling, or userplane data like internet, voice, video
traffic) have different constraints in terms of delay, error rate and bit rate. The transport network takes
them into account to ensure the services.
The eNodeB need to be synchronized (air interface requirement). This synchronization can be received from
the GPS or from the transport network. In this last case, the tranport network needs to be able to carry
synchronization data.
2G, WCDMA or CDMA BTS can be collocated to LTE eNodeB on site. The transport network is then used to
aggregate and backhaul the traffic to the core networks.
For security reasons, one or several eNodeB interfaces should be protected: eNodeB traffic could be
authenticated and even encrypted using IPSEC.
2 Traffic Aggregation
129
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
2 Traffic Aggregation
3G
NodeB
nxE1
(ATM)
LTE
eNodeB
SGW
GE
MME
PCRF
PDN GW
7705 SAR-F
IP Backhaul
CSA
RNC
UTRAN
1 2 10
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
3G and LTE can share the same site to provide 3G and LTE coverage on an given area. 3G and LTE traffic
can be aggregated on the same transport network using a 7705 SAR called a CSA (Cell Site Aggregator).
3G traffic can be ATM or IP traffic depending on the 3G release.
2 Traffic Aggregation
1 2 11
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
In the Alcatel-Lucent implementation the 7705 SAR-F is integrated in LTE solution as Cell Site Aggregator
(CSA). It allows to multiplex the different types of traffic (ATM & IP) over the IP Mobile Backhauling
network.
z The
7705 SAR is MPLS capable, so it can be connected to a MPLS transport network. In this case, the
Ethernet eNodeB traffic is carried over MPLS, in a so called Ethernet pseudowire or epipe.
z The
Alcatel-Lucent 7705 Service Aggregation Router (SAR) is optimized for multiservice adaptation,
aggregation and routing, especially onto a modern, economical Ethernet and IP/MPLS infrastructure.
Leveraging the powerful Service Router Operating System (SR OS) and 5620 Service Aware Manager
(SAM), it is available in compact, low power consumption platforms delivering highly available services
over resilient and flexible network topologies. Strong Quality of Service (QoS) capabilities ensure
service-level awareness and the management of multiple traffic streams. The 7705 SAR is well suited
to the aggregation, backhaul and routing of 2G, 3G and LTE mobile traffic providing cost-effective
scaling and the transformation to IP/MPLS networking
1 2 12
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
3 VLANs
1 2 13
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
3 VLANs
GigE
S1
X2
OAM
GigE
VLAN
S1
X2
OAM
z increased
security
Broadcast traffic increases in direct proportion to the number of stations in the LAN. VLANS are used to
create isolated of groups of devices so broadcast traffic of one group does not impact another group.
VLANs also provides a basic security function, separating the network into distinct logical networks. Traffic
in one VLAN is separated from another VLAN as if they were physically separate networks. If traffic is to
pass from one VLAN to another, it must be routed.
The IEEE 802.1Q standard defines tagging for Ethernet frames, additional bytes (called tag) contain implicit
VLAN membership information.
When Ethernet frames are tagged with VLAN membership, the frame header that contains the additonal
bytes also contains a3-bit field for Ethernet user priority. This field determines the packet network
treatment priority (802.1p) and may be used to implement the transport QoS in the case of an L2-switched
backbone network.
At Integration and commisionning,the eNodeB is pre-configured with a default OAM VLAN ID value of 400.
3 VLANs
Telecom
VLAN
X2
OAM
VLAN
OAM
OAM VLAN
GigE
1588 VLAN
CP VLAN
UP VLAN
1 2 15
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
No IPSEC is supported in the 3 vlans configuation with S1, X2 and OAM VLans.
LA4.0
3 VLANs
TLA3.0
Or
y OAM VLAN, S1 VLAN and X2 VLAN
OAM VLAN
S1 VLAN
GigE
OAM VLAN
GigE
X2 VLAN
1 2 16
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
S1 VLAN
M1-U VLAN
IEEE 1588v2 dedicated IP address cannot be used in conjunction with eMBMS traffic (M1-U interface).
M1-U must be mapped on a dedicated eNodeB VLAN and not in 1 and 2 vlans config.
eMBMS is a donwlink multicast traffic, no uplink eMBMS traffic originates from eNodeB.
3 VLANs
IPv4
TLA3.0
MME
5620 SAM
IPv4
OAM VLAN
GigE
Telecom VLAN
M1-U VLAN
SGW
MBMS-GW
1 2 17
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
IEEE 1588v2 dedicated IP address cannot be used in conjunction with eMBMS traffic (M1-U interface).
M1-U must be mapped on a dedicated eNodeB VLAN and not in 1 and 2 vlans config.
eMBMS is a donwlink multicast traffic, no uplink eMBMS traffic originates from eNodeB.
1 2 18
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
1 2 19
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
4 IP addressing
1 2 20
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
4 IP addressing
Possible IP configuration
No VLAN
1 VLAN
2 VLANs
1 IPv4@ For X2
Telecom traffic
no IP @ for M1-U
traffic
4 VLANS
1 2 21
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
4 IP addressing
Vlan
configuration
Possible IP configuration
1 VLAN
2 VLANs
2 VLANs
1 IPv6@ For S1
Telecom traffic
1 IPv6@ For X2
Telecom traffic
1 IPv6@ For S1
Telecom traffic
1 IPv6@ For X2
Telecom traffic
1 2 22
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
4 IP addressing
IPv4
O&M network
MME
UE
GigE
IPv4
OAM VLAN
Telecom VLAN
Backhauling
network for
Telecom
1 2 23
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
IPv6
SGW
Either IPv4 addresses or IPv6 addresses are supported in a VLAN. It is not possible to have simultaneously
IPv4 and IPv6 addresses in a VLAN.
The eNodeB will be able to transmit IPv4 and IPv6 packets on one Ethernet port using 2 VLANs : one for
Telecom traffic and one for OAM traffic.
Configuration with IPv6 OAM IP address and IPv4 Telecom IP address is not supported.
4 IP addressing
5620 SAM
IPv6
GigE
MME
VLAN
SGW
IPv6
MME
5620 SAM
IPv6
GigE
OAM VLAN
Telecom VLAN
SGW
1 2 24
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
4 IP addressing
IPv6 or
IPv4
MME
5620 SAM
IPv6
OAM VLAN
GigE
S1 VLAN
X2 VLAN
SGW
OAM VLAN
GigE
S1 VLAN
IPv6
X2 VLAN
1 2 25
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
4 IP addressing
eNodeB broadcasts
DHCP
1
messages to
request an IP
configuration
5620 SAM
NM sends config.
including IP
3
configuration
DHCP Server
At next restart,
eNodeB uses
stored IP
4
configuration :
DHCP process no
more used
1 2 26
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
When the eNodeB first starts, if no OAM IP address has been set at Integration and configuration step,
the eNodeB triggers a DHCP procedure to get an IP address.
The DHCP server has a static database that associates eNodeB identification received in the request
(eNodeB serial number associated with LTE keyword) with its static reserved IP address.
In the same time, eNodeB has been provisionned in 5620 SAM database and so 5620 SAM polls the IP
address of the eNodeB. So, once the eNodeB is up, the OAM connection with the eNodeB is setup. The
5620 SAM sends its configuration to the eNodeB, including the OAM IP address (that should be the same
that the one retrieved by the DHCP server). At next restart, the eNodeB will use the NM configuration and
will not use anymore DHCP process.
The eNodeB identifier is the eNodeB serial number, the serial number is linked to the cabinet serial
number in the FAN tray.
eNodeB requests for an infinite DHCP lease.
If VLAN tagging is enabled then the DHCP messages are transported within the OAM VLAN.
DHCPv4 and DHCPv6 are supported.
One 1588v2 IPv6 address + one OAM IPv6 address on OAM VLAN,
One IPv4 OAM address + one IPv6 Telecom @ on one VLAN,
One IPv4 OAM address + one IPv6 Telecom @ on two VLANs,
One IP address for S1 traffic + one IP address for X2 traffic + one IP address
for OAM + one IP address for 1588v2 using a 4 vlan configuration
1 2 27
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
5 IPSec
1 2 28
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
5 IPSec
5.1 UE Security
After UE authentication, the UE communications are secured on air interface :
Signaling Radio bearer are authenticated and encrypted
Data Radio Bearer are encrypted
S1 MME
MME
RB
S1-U
SRB
UE
SGW
Secured
unsecured network
or unsecured eNodeB location
Use IPSEC
1 2 29
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Security Requirements :
Flat architecture:
z
z eNodeB
z
z Additional
NEW IP header
Sce IP C | dst IP D
Sce IP C | dst IP D
Sce IP C | dst IP D
Tunnel 2
Tunnel 1
nel
3
5 IPSec
LA4.0
S1 MME
MME
Security Gateway
(SEG)
S1 MME
RB
UE
S1-U
S1-U
SRB
Secured
Secure
IPSEC tunnel
Secure
IPSEC tunnel
SGW
1 2 31
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
To activate the eNB to SEG IPsec feature the customer need to purchase a Software License. Licensing is
offered in a per eNodeB basis.
Spokes are eNodeB, MME and SGW. Hubs are the SEGs that terminate all the IPsec tunnels. Spokes can
connect via IPsec tunnels only with hubs, while hubs can connect with spokes and other hubs.
In this Hub and Spoke architecture, the X2 traffic from an eNodeB to another eNodeB must enter the IPsec
tunnel to the SEG from eNodeB to SEG and then from SEG to destination eNodeB.
5 IPSec
O&M network
MME
OAM traffic
ePC
Telecom traffic in
IPSEC tunnel
SEG
SGW
1 2 32
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
5 IPSec
SEG
GigE
VLAN
SEG
GigE
Telecom
VLAN
1 2 33
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
GigE
OAM
VLAN
SEG
5 IPSec
S1-U + X2-U
S1-C + X2-C
GigE
Example
OAM
VLAN
1 2 34
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
OAM
SEG
IPSEC policies can be defined to fine tune the protection depending on the trafffic flows : 2 different IPSEC
policies can be applied for Telecom traffic using the 2 VLANS configuration:
z One
z One
All telecom traffic (S1 and X2) inbound and outbound bypass IPsec.
S1-C traffic is integrity protected and encrypted, but S1-U and X2 traffic bypass IPsec.
All telecom traffic (S1 and X2)is integrity protected and encrypted by IPsec.
X2
eNodeB application
generates IP
packets
S1-C
X2
OAM
S1-C
X2
S1-U
S1-U
OAM IP@
TEL IP@
IPSEC policies
S1-U
OAM IP@
TEL IP@
OAM IP@
TEL IP@
Outer
IPSEC policies
IP@
OAM
TEL
OAM
TEL
vlan
vlan
vlan
vlan
Outer
IPSEC policies
IP@
OAM
TEL
vlan
vlan
5 IPSec
Inner IP :IPv4
SEG
Inner IP :IPv6
SEG
OR
Outer IP :IPv6
Outer IP :IPv4
1 2 36
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Multiple IPsec tunnels can be deployed between one eNodeB and the Security Gateway (SEG). One IPSEC tunnel is
characterized by one pair of IP addresses (eNodeB outer IP@+ SEG IP@).
The inner IP address is the eNodeB Telecom IP address (initially provisioned during commissioning) while the outer IP
address is new and is provisioned together with an outer IP address subnet mask via NM. In addition, NM also
provide the SEG IP address (destination of the tunnel).
The IKE protocol version is IKEv2.
IKEv2 use the following encryption and integrity protection algorithms :
1. 3DES CBC for encryption
2. AES CBC 128 for encryption
3. HMAC-SHA1-96 for integrity protection and authentication
IKE authentication between the eNodeB and the SEG is performed using pre-shared secret keys. These secret is
provisioned in the eNodeB (via NM) and in the SEG.
The SEG can be any IPsec gateway supporting IPSEC IKEv2 standard protocols.
IPSEC is supported on various VLAN topologies, using IPv4 or IPv6 addresses format :
z
OAM and Telecom have the same IPv4 address.
z
OAM and Telecom interfaces have different IPv4 addresses, in the same or different VLANS
z
OAM and Telecom interfaces have different IPv6 addresses, in the same or different VLANS
z
OAM (IPv4) and Telecom (IPv6) interfaces have different address schemes (in different VLANS)
IPSEC is not supported on the 3 VLANS configuration (OAM, S1 and X2 vlans).
The
The
The
The
serving Gateway,
PDN Gateway
MME
Security Gateway
1 2 37
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
6 SCTP Protocol
1 2 38
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
6 SCTP Protocol
X2-AP
2
ort 3642
tion on p
ia
oc
ss
a
SCTP
IP@1
IP@2
IP@3
MME
S1-MME
6 SCTP Protocol
S1-MME
ONE SCTP association on port
36412
IP@1
MME
IP@3
IP@4
6 SCTP Protocol
MME
SCTP data
SCTP data ACK
SACK timer
Min, Max and Init RTO values can be configured to improve the global behavior of
SCTP. These values are limit values for the calculated RTO value.
1 2 41
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Whenever a retransmission timer expires, all non-acknowledged data chunks are retransmitted and the
RTO timer is started again doubling its initial duration (like in TCP). In normal operation, the RTO
value is constantly alculated based on experimented network delay.
The following parameters are introduced in LA4.0:
z sctpSACKTimer - Selective Acknowledgment Timer defines the time to wait before transmitting
Acknowledgement. This parameter tuning helps to save bandwidth as it reduces the number of SACK
messages sent.
sctpRTOMin - Retransmission TimeOut Minimum && sctpRTOMax - Retransmission TimeOut
maximum
These timers defines respectively the minimum/maximum time limit for the Retransmission timer on the
eNodeB. This is used to trigger the retransmission of a Data chunk in response to a lack of receipt of a
SACK acknowledgement from the peer SCTP entity.
The RTO Min parameter has a range of [0...10000] msecs and a default recommended of 1000msecs.
The RTO Max parameter has a range of [0...60000] msecs and a default recommended of 30 seconds.
z
RFC2960/RFC4960 details the algorithm for calculating the RTO within an SCTP end-point. If the
calculated RTO is lower than the RTOmin configuration parameter, the SCTP end-point rounds-up the
value it uses to the configured value. If the SCTP RTO algorithm calculates an RTO which is greater
than the RTOMax configured parameter, then the RTO is truncated to the configured value.
6 SCTP Protocol
T1 T2
T3
T4
T5
T6
The section discusses the impacts of certain settings for RTOmin, RTOmax and
sctpAccessPathMaxRetransmits.
Example 1
Consider the RFC2960/4960 defaults:
z RTOmin = 1 sec
z RTOmax = 60 secs
z PathMaxRetransmits = 5
z
SCTP Link Failure detection occurs after 5 retries. If the link has settled at RTOmin prior to fault, the
following time is required to detect the link break= 1+2+4+8+16+32 = 63 seconds
The first packet transmission failure has RTO = RTOmin = 1 sec, the first RE-transmission has RTO = 2
secs, the fith RE-transmission has RTO = 32 secs. This aggregate time is a considerable time to detect
a failure of a path and invoke a switchover to an alternate path in a multi-homed environment.
Potentially, the association could be torn-down before a switchover is invoked.
6 SCTP Protocol
T1 T2
T3
T4
T5
T6
T1 = T0 + RTO (with RTO = RTOMin) = T0 + 120 msec.
T2 = T1 + RTO (2 x 120 msec.) = T0 + 360 msec.
T3 = T2 + RTO (2 x 240 msec.) = T0 + 840 msec.
T4 = T3 + 500 msec. (as RTO = 2 x 480 msec > RTOMax) = T0 + 1,34 sec.
T5 = T4 + 500 msec = T0 + 1,84 sec.
T6 = T5 + 500 msec.= T0 + 2,34 sec.
Failure detection occurs after 5 retries, which requires the following time if the link is at minimum RTO.
The first failed transmission will have a RTO=RTOmin=0.12sec, the first RE-transmit will be offered
RTO of 0.24 secs for a reply. Due to RTOmax limit, the 3rd, 4th & 5th: RE-transmissions will be given
a RTO=RTOmax = 0.5 secs
total time = 0.12+0.24+0.48+0.5+0.5+0.5 = 2.34 seconds
This is a considerably quicker response to detecting a link break and invoking a switchover.
For MMEs which are multihomed the eNodeB must detect a link failure and switch to the alternate path
sufficiently quickly to prevent the MME tearing down the link.
The
The
The
The
SCTP
SCTP
SCTP
SCTP
1 2 44
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
7 QoS
1 2 45
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
7 QoS
7.1 Introduction
Based on its associated E2E services, an EPS bearer is associated to a set of QoS
parameters, mainly :
QCI,
ARP,
Maximum and Guaranteed bit rate in UL and DL.
ePC
eUTRAN
PGW
1 2 46
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
EPS network (eUTRAN + EPC) provides EPS bearer between the UE and the PGW.
An EPS bearer/E-RAB is the level of granularity for bearer level QoS control in the EPC/E-UTRAN.
The initial bearer level QoS parameter values of the default bearer are assigned by the network, based on
subscription data.
An EPS bearer/E-RAB is referred to as a GBR (Guaranteed Bit Rate) if dedicated network resources are
permanently allocated by an admission control function in the eNodeB, at bearer
establishment/modification.
Otherwise, an EPS bearer/E-RAB is referred to as a Non-GBR bearer.
A dedicated bearer can either be a GBR or a Non-GBR bearer while a default bearer shall be a Non-GBR
bearer.
The bearer QoS parameters are QCI, ARP, GBR, and AMBR.
7 QoS
Resource
Type
Priority
Packet Delay
Budget
100 ms
10-2
Conversational Voice
150 ms
10-3
50 ms
10-3
300 ms
10-6
100 ms
10-6
IMS Signalling
300 ms
10-6
100 ms
10-3
300 ms
10-6
1
2
GBR
Non-GBR
Example Services
1 2 47
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The QoS Class Identifier (QCI) is a index that identifies a pre-defined packet forwarding treatment
(scheduling, admission control, queuing, link layer protocol configuration (ARQ and HARQ), etc.).
The standardized QCI label characteristics describe the packet forwarding treatment through the network
based on the following parameters:
Priority (= ARP)
Allocation and Retention Priority (ARP) is used to determine whether a bearer establishment or modification
request should be accepted or rejected in case of eNodeB resource limitations.
In addition, the ARP can be used by the eNodeB to decide which bearer(s) to drop during exceptional
resource limitations.
In addtion a GBR bearer is allocated Guaranteed Bit Rate value (one in UL and one in DL)that the eNodeB is
expected to provide to the bearer.
7 QoS
MME
RB
UE
S5 Bearer
S1 Bearer
SGW
eNodeB
Radio bearer Qos
PGW
1 2 48
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The end to end QOS functions are performed at four levels : UE , eNodeB , ePC and the transport network
levels.
The EPC bearer QoS parameters are mapped to each corresponding QoS parameters :
-Radio QoS parameters on LTE-Uu interface
-Transport network QoS parameters on S1 and S5 interfaces.
In addition, the transport network also ensure control plane traffic prioritization using the same Layer 3 and
Layer 2 mechanisms.
7 QoS
DSCP
p-bit
Service Example
1 (GBR)
EF (46)
Conversational Voice
2 (GBR)
EF (46)
3 (GBR)
EF (46)
4 (GBR)
AF42 (36)
IMS Signalling
Tunnel header
L2
L3
ETH
IP
L4
..TEid..
IP@(PGW/SGW),DSCP [BE, EF, AF]
P-bit [0,,7]
Diffserv packet marking (DSCP) is used to propagate QoS information on the mobile
backhauling network. It is Implemented in PGW for DL packets and eNodeB for UL
packets
1 2 49
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
7 QoS
5620 SAM
UE
OAM
GigE
SGW
eNodeB
High priority
flow
PGW
1 2 50
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The eNodeB implements UL QoS class based queuing to provide the priority in UL transmission based on
QoS needs.
In addition, depending on backhauling network capacity, the UL traffic needs to support rate limit according
to the backhaul bandwidth provided. The UL traffic shaping applies on the aggregated traffic which
egresses the Ethernet port.
In LA2.0, the initial feature Uplink traffic shaping goal was to support an UL basic traffic shaping only. The
basic requirement is when the eNB transport bandwidth is capped ie limited. In this case the EnodeB
supports UL rate limiting on the total aggregated traffic flow and yet still maintains the QoS needs for
individual flows in the UL.
Backhauling network
capacity limited
GigE
UL shaping used to
adapt UL rate to
backkaul capacity
7 QoS
EIR
bandwidth
CIR
Backhauling network
time
UL eNB traffic between CIR
and EIR may be dropped
by the network in case of
congestion
1 2 51
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
For a flow, the Committed Information Rate ( CIR) is the average bandwidth guaranteed by a backhauling
provider to work under normal conditions. At any time, the bandwidth should not fall below this
committed figure. The CIR is guaranteed on a period of time T. If T is high enough, traffic can exceed
CIR during some time and can be lower than CIR the remaining time. To respect the average value CIR,
the maximum quantuty of data that can be sent during T is determined by : T CIR = CBS (Committed
Burst Size).
Above the CIR, an allowance of extra bandwidth is often given, known as the Excess Information Rate
(EIR). The provider guarantees that the connection will always support the CIR rate, and sometimes the
EIR rate provided that there is adequate bandwidth. The CIR plus excess burst rate (EIR) is either equal
or less than the speed of the access port into the network.
Extra data that exceed EIR are dropped. On the period of time T, the extra traffic can reach a value of EBS
(Excess Burst Size), equal to T (EIR CIR) = EBS.
7 QoS
EIR
CIR
GigE
per VLAN
EIR
CIR
Telecom
VLAN
EIR
OAM
VLAN
1 2 52
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
CIR
average rate shaping limits the transmission rate to the CIR (Committed Information Rate).
Excess Information (EIR) shaping allows to send more traffic than the CIR. However, the traffic sent
above the CIR (the delta) could be dropped if the network becomes congested. If the network has
additional bandwidth available (over the provisioned CIR) and the application or class can tolerate
occasional packet loss, that extra bandwidth can be exploited through the use of EIR shaping.
However, there may be occasional packet drops when network congestion occurs.
The UL traffic shaping can be defined on a per VLAN basis or on a per physical port basis (available from
LA3.0). Bandwidth profiles need to be defined with following parameters: CIR/CBS, EIR/EBS.
Per VLAN configuration: as much set of parameters as VLAN number
Per Physical Port configuration: 1 set of parameters
CIR
CIR and EIR
No shaping
7 QoS
1 2 53
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The Call Admission Evolutions feature provides an evolution of the Admission Control from a token-based to
a measured-based solution. (LA2.0 Static CAC no longer used).
The Radio CAC solution allows admitting or rejecting new entrant bearers on a per QCI basis.
The Admission Control function on a per cell basis has to experience the average cost/impact onto both the
eNodeB and the Air Interface resources of the different types of services/applications. Based on the
experienced average costs versus the maximum eNodeB and Air Interface resources, the admission
decisions are the most in line with the on-per-cell basis live impact of an application depending on the local
radio conditions in the cell.
The Admission Control or admission decisions is also considering the ongoing average situation on served
QoS for existing bearers, and the impacts on the new entrant bearer onto the UL backhaul resources.
The solution allows the operator to control the admission on new entrant bearer on a per service type
basis. The operator/customer may then favor or restrict the admission of certain applications toward their
impact/cost on the LTE network resources.
In addition, from LA4.0, pre emption of existing bearer can be performed. The proper pre-emption action is
configurable by the operator (on a per QCI basis) and may be either:
z offloaded
z Released:
Trigger lower ARP bearer release. Careful analyses of the bearers are performed and
decision taken to release a bearer with minimum impact to end-user services and experience.
1 2 54
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
8 Synchronization
1 2 55
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
8 Synchronization
Technology
Freq.
ToD
GSM
50 ppb
UMTS FDD
50 ppb
UMTS TDD
50 ppb
LTE FDD
50 ppb
LTE TDD
50 ppb
1.5 s
WiMAX TDD
2 ppm
3 s
WiMAX FDD
2 ppm
CDMA
50 ppm
2.5 s
-
10 s
1 2 56
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The eNodeB has an internal clock to synchronize the air interface (time and frequency). But it can drift
slowly and disturbs the cells. It is why the eNodeB must receive an external synchronization.
The modulated carrier frequency of the BS shall be accurate to within 0.05 ppm observed over a period of
one subframe (1ms). The requirement applies on the radio interface.
3GPP TS36.104 [R6] specifies that LTE networks require stability of transmitted radio signal better than
50 ppb.
Phase synchronization is the process by which two or more cyclic signals tend to oscillate with a repeating
sequence of relative phase angles.
Problem of synchronization has not the same impact in FDD or in TDD systems.
z In FDD, the frequency synchronization is required to avoid the drift of the frequency center as this
z In TDD, the time synchronization is also required for the radio frame synchronization.
8 Synchronization
Frequency
eNodeB drifts ouside 50ppb window
F2
F2
+/- 50ppb
+/- 50ppb
UE can not lock to the
target eNodeB.
HO is unsuccessful
Handover
F1
F1
Time
Time
frequency synchronization is
required
1 2 57
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
z in
8 Synchronization
eNB1
eNB2
UE1
UE2
time
UE1 TX
Overlap
Overlap
UE2 RX
1 2 58
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
time
eNB1 TX
eNB2 RX
TDD mode often requires synchronization between various transmitters and receivers in different cells.
Two non-synchronized close UEs jam each other in a nearfar context. The strong signal from the UE1
(transmitter) destined to eNB1 (receiver) can jam the UE2 if the UE1/UE2 ranges overlap.
A nearly same issue can appear between eNodeBs.
Phase Synchronization (same frame start-time among eNodeB) is reaquired :
In TDD mode
8 Synchronization
Sync Ethernet
clock master
Synchronous Ethernet
GPS
1588v2
server
1588v2
client
1 2 59
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
z There is a GPS receiver embedded in the eNB, an RS422 is available to connect GPS antenna. There is
also an External timing port to connect an external GPS receiver. GPS supports phase and frequency
reference.
z IEEE1588v2 is the recommended clock delivery over IP networks.
Note : IEEE 1588v2 is used for frequency reference from LA3.0.
z SyncE can only be used for frequency reference, so syncE cant be used in TDD systems.
Two reference sources can be combined in other to have a primary reference source and a backup
reference source, but syncE and IEEE 1588v2 cant be combined in LA3.0.
The eNodeB can run in free running for 72 hours for Frequency and 1 hour for phase (standard).
8 Synchronization
TDD solution supports GPS and 1588v2 solutions for frequency and phase
synchronization. If both are used, GPS is the ToP priority solution,
1588v2 is the backup reference source.
FDD solution supports GPS, SyncE and 1588v2 solutions for frequency
synchronization.
multiple reference source
Top priority
GPS
GPS
SyncE
GPS
2nd priority
1588v2
SyncE
1588v2
SyncE
3rd priority
1588v2
Flywheel
Holdover
1 2 60
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Holdover
Holdover
Holdover
If no more reference clocks are available the eNB enters holdover, relying on the flywheeling function of
the internal oscillator. While the oscillator flywheels, the clock drifts from the optimum frequency and
phase. The eNB generates alarms when the drift reaches certain thresholds.
GPS is this only available solution for phase synchronization in LA4.0, only TDD TLA3.0 release supports
phase synchronization using PTP 1588v2.
8 Synchronization
Ethernet
Sync Ethernet
clock master
LA3.0
1 2 61
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
A physical layer clock is delivered to the eNodeB over the Ethernet network from the Ethernet switch. This
is the same technique as using recovered E1 or T1 clock to derive the master clock on a Base Station for 2G
/3G /CDMA.
The Ethernet switch connected to the eNodeB must derive its reference clock from a signal traceable to a
Primary Reference Clock (PRC). This may be via a dedicated port, or it may be by using the recovered clock
from an ingress port.
There may be a number of Ethernet switches involved in the distribution of the reference timing signal : all
adjacent switches are running syncE.
Synchronous Ethernet uses synchronization status message (SSM) used in SDH networks. These messages
contain an indication of the quality level of the clock that is driving the synchronization chain. SSM is carried
over Channel ESMC, using the Ethernet OSSP Organization Specific Slow Protocol.
If the eNB is informed that the upstream equipment has lost its clock reference, it can decide what action
to take from a number of option, like for example holdover and ignore incoming reference or Ignore the
message and remain locked to reference. The configuration parameter syncEssmEnable must be set
to Enable to actiavte SSM support on eNodeB.
http://www.explania.com/fr/chaines/alcatel-lucent/detail/synchronous-ethernet
8 Synchronization
PTP server
grandmaster
PTP client
T1
T1
RTT = ((T2-T1)+(T4-T3)):2
mean delay = RTT/2
DL delay = T2-T1
UL delay = T4-T3
T2, local
reception time
T3
Delay request
T4
Delay response T4
1 2 62
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
8 Synchronization
Several messages
are used to
negociate PTP
exchanges rate.
1 2 63
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
logmessage interval
Duration
The messages exchanged are Request unicast transmission messages (sent by the eNodeB) and Grant
unicast transmission messages (sent by the server). These Messages contains different messages types
used to convey synchronization information : Announce, Sync, Delay response.
These information are sent at a regular period called interMessagePeriod over during a defined period.
This sending rate (pps) is negociated at the beginning of PTP messages transmission using sync type
messages.
The receiver records the time when packets are received after which the local interval between two
received packets is compared to the difference between the timestamps. The time stamps inside the
consecutive packets are compared with local arrival times.
Theorically one can determine the frequency error of the local clock compared to the reference by sending
two packets. In reality it is more complex due to Packet Delay Variation in the network, thats why the
number of hops must be limited between Server and eNodeBs.
The eNodeB supports the 1588 v2 server redundancy. In case of primary server lost the eNodeB fallbacks
to a secondary PTP server or another clock reference source. Fallback from primary to secondary is non
revertive.
List the available solution(s) for frequency and phase synchronization on TDD system :
y GPS
y 1588v2 PTP
y SyncE
1 2 64
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
End of module
LTE Transport overview
1 2 65
RAN TLA3.0-LA4.0 Technical Overview LTE Transport overview
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
13
Section 1
RAN TLA3.0-LA4.0 Technical
Overview
Module 3
LTE eNodeB Hardware Description
TMO18213_V4.0-SG-Ed10 Module 1.3 Edition NA
9400 LTE
RAN TLA3.0-LA4.0 Technical Overview
TMO18213_V4.0-SG Edition 10
Blank page
132
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Document History
Edition
Date
Author
Remarks
01
YYYY-MM-DD
First edition
Module objectives
Upon completion of this module, you should be able to:
Describe the eNodeB architecture
Describe the eNodeB Base Band Unit and Radio modules
Describe some eNodeB special configurations
133
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
134
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Table of Contents
Switch to notes view!
1 eNodeB description
1.1 General Architecture
1.2 RF Modules
1.3 Standard configuration
2 9926 BBU (Base Band Unit)
2.1 BBU design
2.2 BBU Shelf and Rack Backplane
2.3 RUC description
2.4 Controller Board Description
2.4.1 Controller Board backhauling interfaces
2.4.2 Controller Board CPRI interfaces
2.5 Modem Board Description : eCEM-U
2.6 Modem Board Description bCEM-U
2.7 External Alarm
2.8 eNodeB R-OCM configuration
3 TRDU Macro modules
3.1 eNodeB configurations with Macro Modules
3.2 TRDU2X overview
4 MC-TRX module
4.1 MC-TRX principles
4.2 eNodeB enclosures with MC-TRX
4.3 MC-TRX overview
5 Distributed eNodeB with RRH modules
RF
1 3 5 5.1 eNodeB configurations with RRH
COPYRIGHT ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.
RAN TLA3.0-LA4.0
Technical
Overview
LTE eNodeB Hardware Description
5.2
9442
RRH
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
5.3 9442 TD-RRH
5.4 antenna cross connect configuration
5.5 RDEM
5.6 Fiber Delay Compensation
5.7 Distributed solution RRH benefits
6 eNodeB advanced capabilities
6.1 Capacity
6.2 eNB Reliability
7 Appendix A : RF modules description
8 Appendix B : eNodeB enclosures
Page
7
8
9
10
11
12
13
15
16
18
20
22
23
24
25
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
44
45
46
47
51
136
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
1 eNodeB description
137
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
1 eNodeB description
eNode B
RF module
CPRI
Base Band Unit
S1 & X2
The antenna represented on the diagram is not considered as being part of the eNodeB.
1 eNodeB description
1.2 RF Modules
The eNodeB is an integrated system composed of a cabinet, a BBU and RF
modules that can be :
Macro modules in compact eNodeB
RRHs in distributed eNodeB
MC-TRX Modules in compact eNodeB
RF module : macro
modules
CPRI
Base Band Unit
eNodeB cabinet
139
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
RF module :
RF module : RRH
MC-TRX
CPRI
CPRI
eNodeB cabinet
eNodeB cabinet
1 eNodeB description
x2
x2
x2
TRDU
TRDU
Or
Or
Or
RRH
RRH
RRH
Or
Or
Or
MC-TRX x2
MC-TRX x2
MC-TRX x2
CPRI
TRDU
CPRI
CPRI
1 3 10
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
In LA4.0 the RF part is ensured by either TRDU or RRHs or MC-TRX only (no mix).
The 2x2 MIMO is the normal base station transmit scheme for all eNodeB variants. In addition, the eNodeB
supports :
Single Antenna Transmit Scheme
The 4-way Receive Diversity (4br Rx Diversity) on RRH equiped with a RDEM module.
TLA3.0 eNodeB supports 8x antenna Beam Forming.
Using cross-polar antennas, each TRDU and/or RRH has two TX/RX paths that are connected to the two RF
connectors of the antenna.
In case of TRDU usage, and depending of the distance between the TRDUs (eNodeB cabinet) and the
cross-polarized antennas, TMAs may be needed,
1 3 11
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
eNode B
RF module
CPRI
1 3 12
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
CEM
CEM Slot 3
CEM
CEM Slot 2
CEM
CCM Slot 1
CCM
fan tray / RUC
Fan Rack Unit
d2U v3 RBP
1 3 13
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
d2Uv5 RBP
Copyright 2012 Alcatel-Lucent. All Rights Reserved.
TMO18213_V4.0-SG-Ed10 Module 1.3 Edition NA
Section 1 Module 3 Page 13
Air flow
1 3 14
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The 9926 BBU can be installed in a standalone indoor mode or in an existing indoor or outdoor AlcatelLucent Base Station cabinet for Multi-Standard configuration.
The 9926 BBU rack has the following characteristics:
width (W): 482.6 mm
depth (D): 300 mm
height (H): 88.1 mm
weight (fully equipped): from 9.8 kg up to 10.5 kg (depending on the number of CEM(s) in the
digital shelf).
Unused CEM slots on a powered BBU rack must be equipped with filler modules. The filler modules maintain
ElectroMagnetic Interference (EMI) integrity, as well as shelf airflow patterns to ensure proper cooling.
The Fan tray includes two fans. The air enters on the right side of the shelf, drawn through the shelf to cool
the boards, and exhausted on the left side of the shelf.
To CCM ext.
alarm port.
-48VDC
RUC
Front View
FAN
-24VDC
RUC
Front View
1 3 15
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Note
Important note : TDD BBU will only operate under -48VDC.
a main mother board (MB) providing Internal interfaces to CEM boards and to
RF modules (CPRI connectivity)
A Gigabit Ethernet (GE) MDA (Media dependant Adaptor) daughter board that
provides backhauling network connectivity
eNodeB synchronization
O&M functions
Collection of BBU alarms, inventory and commissioning data,
1 3 16
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
In LE3.0 The 9926 BBU houses one eCCM-U. The eCCM-U is a controller in charge of part of :
call processing,
OA&M management,
internal/external data flow switching/combining,
external/internal alarm connectivity, and an external synchronization reference interface.
CPRI interfaces to the RRHs.
Collection of BBU alarms, inventory and commissioning data,
Collection of own 9926 BBU alarms, inventory and commissioning data,
Collection of external user alarms from optional alarm module (eAM),
OIM (Optical Interface Module) features to support up to six optical links,
Integrated GPS receiver
High stability OCXO (Oven-Controlled Crystal Oscillator) for frequency stability.
The eCCM-U supports multiple wireless access technologies (one at a time), providing the foundation for
converged RAN.Configuration of the technology is done at commissioning time via a HW technology
switch located on the main mother board.
There is eCCM Controller board convergence between FDD and TDD in LA3.0/TLA3.0 concerning SW design,
this ensures common MIM model, common internal eNB interfaces (CCM CEM interfaces), common
OMC, NPO and WPS for TDD and FDD but still there is different FDD and TDD eCCM-U Hardware used
in LA3.0 and in TLA3.0 : TLA3.0 uses eCCM-U high CPRI rate GE modules whereas LA3.0 used eCCM-U
P2 boards (and previously eCCM-U P0bis version).
The MDA is not a field replaceable unit.
Copyright 2012 Alcatel-Lucent. All Rights Reserved.
TMO18213_V4.0-SG-Ed10 Module 1.3 Edition NA
Section 1 Module 3 Page 16
GE Ethernet MDA
6 SFP cages
for links to
radio modules
1 3 17
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The face plate of the eCCM-U provides the following connectors (please refer to figure below):
LEDs providing the current status of the module,
One port for connection to external GPS antenna (in case of integrated GPS receiver) via a SMB
connector,
One RJ45 connector used for PPS input from an external GPS receiver; this connector also can
provide one RS232 port for control of external equipment,
One block of 6 SFP connectors for connectivity to the radios (RRH, TRDU); each SFP connector is
equipped with two light indicators; they support 6 CPRI links or 3 CPRI + 3 HHSL links,
One RJ45 connector used for a 1-wire interface (connectivity to external alarm module,
commissioning...),
One dual SMP connector providing input for 10MHz/15MHz input and 15MHz output,
Two RJ45 connectors used for debug (RS232) (debug/NEM port refered as Eth2) and Ethernet
(SiteLAN port, used for RETA); each connector is equipped with two LEDs (a yellow one showing
Ethernet activity status and a green one for Ethernet link status),
One J20 connector (not used in LA3.0).
RJ45 Debug interfaces must not be used during normal operation of the BBU.
MDA Geth port is refered as Eth0.
LA4.0 release supports eCCM-U GE modules eCCM-U P0bis or eCCM-U P2 modules.
SFP transceiver
Optical port
RJ45
Ethernet port
Backhauling
network to EPC and
other eNodeB
1 3 18
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Optical or
electrical
The LTE digital does not support traffic backhaul over PCM links but only over Ethernet links, the J20
connector for 4 E1/T1 connections is not used in LTE case.
The face plate of the GE MDA provides:
One RJ45 connector for GE electrical backhaul
Two SFP (Small Form-Factor Pluggable) connectors for GE optical backhaul
On MDA, ports are named SFP1, SFP2 and RJ45, from left to right.
Only SFP-2 or RJ45 connector shall be used : if both connected, then SFP-2 port is used a,d RJ45 port is
disable.
In LA4.0 release, only one single GE Interface is supported for the backhaul. In case of optical link, only
the SFP-2 port is enabled.
RJ45 connexion
The physical length of the channel (fixed horizontal cable & patch cords + cross-connect jumpers) shall not
exceed 100 m (Ethernet standard) so that means that horizontal cable physical length shall not exceed
90 m (+ 10m for patch).
Cables should be F/UTP minimum constructed cables, Category 5e, compliant with IEC11801 & TIA/EIA568 standards.
Fast Ethernet on the embedded RJ45 port can also be used, but not recommended.
EPC
850 nm
850 nm
UL
EPC
DL
1310 nm
1310 nm
1 3 19
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
On optical connections, one fiber carries the downlink signal and a second one the uplink signal.
The multimode fiber is used for a maximum distance of 220 meters using 1000BaseSX SFP (850 nm
wavelength) 62,5 micron fibers or 550 using 850nm and 50 micron multimode fibers.
The monomode fiber is used for a maximum distance of 10km meters using 1000BaseLX SFP (1310 nm
wavelength) / 62,5 micron fibers or 550 using 850nm and 9 micron multimode fibers.
RF
module
RF
module
RF
module
Star configuration
CPRI uses optical links and possibly electrical links for short distance
(compact eNodeB). SFP are used to adapt connectors.
1 3 20
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
CPRI connections are based on V4.0 and V4.1 CPRI standard. CPRI standard plans to cover UMTS + LTE
mixity and CDMA + LTE mixity.
The Alcatel-Lucent BBU supports the following topology:
Star configuration (up to 6 ports on 4G BBU)
Daisy chain configuration will be supported in future release.
Various bits rates are supported :
614.4 Mbit/s (Rate 1), TDD
1228.8 Mbit/s (Rate 2), FDD&TDD
2457.6 Mbit/s (Rate 3) FDD&TDD
3072.0 Mbit/s (Rate 4),
4915.2 Mbit/s (Rate 5). TDD
Secondary port can also be used in case of Antenna cross-connection configuration (described later in this
module).
RF
module
BBU
LC connector
1 3 21
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
SFP
Depending on customer optical link choice (Multi or Single mode), the SFP cage of the eCCM-U board will be
equipped with CPRI optical SFP transceivers to support the connection to the Radio Module.
Various SFP are used to adapt to bit rate and transmission mode (wavelenghth, one or two fibers).
Multi Mode (MM) dual fiber: One fiber carries the downlink signal and a second one the uplink signal.
The MM fiber is used for short distance (<= 500 m). The SFP module in Multimode uses a transmitter 850
nm wavelength.
Single Mode (SM) Dual Fiber: one fiber carries the downlink signal and a second one the uplink signal.
The SM is used for high distance (up to 20 Km). The same Single Mode SFP transmitter is used on both
ends of the fiber, 1310 nm wavelength transmitters.
Single Mode single fiber: one single fiber carries both downlink and uplink signal. The SM must be used
for high distance up to 15 Km. The SFP module on BBU uses a 1550 nm wavelength transmitter. On the
RRH the SFP module uses a 1310 nm wavelength transmitter.
FDD
only
1 3 22
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Peak throughput/
eCEM-U
Nb sector eCEM-U
The eCEM-U performs digital signal processing for both the Tx and Rx paths. The eCEM supports the
following functions:
- Board level OA&M functions,
- Call processing,
- L2 processing (Radio Link Control function (RLC), Media Access Control function (MAC),Downlink
Scheduler, Uplink Schedule).
- L1 processing
The eCEM-U provides two debug ports that should not be used during normal eNodeB operation.
Each eCEM-U modem supports one sector. Up to a maximum of three eCEM-U modules can be inserted in
the 9926 BBU so a maximum 3 sectors can be handled by one eNodeB.
Modem (CEM)
Bandwidth/
bCEM-U
Nb sector /
bCEM-U
1 3 23
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The bCEM-U performs digital signal processing for both the Tx and Rx paths. The bCEM-U supports the
following functions:
- Board level OA&M functions,
- Call processing,
- L2 processing (Radio Link Control function (RLC), Media Access Control function (MAC),Downlink
Scheduler, Uplink Schedule).
- L1 processing
The bCEM-U provides three debug ports that should not be used during normal eNodeB operation.
In TLA3.0 release, a bCEM-U modem can support up to 3 sectors in 2X2 MIMO 10 or 20 Mhz configuration.
First bCEM is installed in slot bCEM-U1, the second in slot bCEM-U2, the third in slot bCEM-U3.
Two different HW version of bCEM-U exists : P0.1 and P1 they must not be mixed inside one BBU shelf.
P0.1 bCEM are used in d2Uv4 BBU and P1 bCEM in d2Uv5 BBU.
Connected to RUC
Ext. port alarm
1 3 24
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The 9926 BBU can be equipped with an external alarm module that provides an extension to support up to
32 external user alarms.
These alarms include power systems and battery backup alarms, cell site door alarms, external alarms
provided by other cell site equipment such as backhaul modems.
Alarms :
10 Frame/Cabinet Alarms
4 Power Alarms
Secondary protection on all alarm inputs
Primary protection on user and power alarms (eAMo)
Future support for I2C controller interface
Powered from eCCM-U controller
The eAMi, as well as the eAMo, are 19 modules, U high for rack mount enclosure.
FDD
only
Reverse OCM
circuit pack
1 3 25
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The eNodeB R-OCM (Remote OneBTS CPRI Module ) is used in 9228 or 9226 Digital Shelf. It enables the
reuse of RF assets in a CDMA Modular Cell BTS.
The CDMA RF resources are shared between the eNodeB and the CDMA BTS. The eNodeB BBU
communicates via the CPRI links with the R-OCM located in the CDMA BTS. The R-OCM creates Virtual
Remote RF Heads (VRRHs) that are seen by the eNodeB as a new type of Remote RF Heads (RRHs).
Using this RF path sharing instead of an external RF combining solution (antenna sharing), the combiner
guard band is not necessary
more available BW for additional CDMA carrier.
The feature is focused on LTE cells with 5 Mhz bandwidths, in the 3GPP Band Class 4-AWS, which
corresponds to Band Class 15 in CDMA standard.
Considering eNodeB capacity in LA4.0, the following RF configurations are supported:
1 to 3 sectors 2T2R shared radios (two TX and two RX paths)
1 to 3 sectors 2T2R stand alone radios
The eNodeB R-OCM configurations are supported in Modular Cell 4.0B and Compact Modular Cell 4.0B
cabinets.
In Indoor Modular Cell 4.0B cabinet, the LTE BBU shares the same cabinet with CDMA equipment.
In the case of Compact Modular Cell 4.0B outdoor cabinet, the LTE BBU is located in a separated
weatherized cabinet
1 3 26
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
1 3 27
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Digital module
Outdoor Cabinets
MBO2 GSM cabinet
or
Baseband and RF cabinet
RF Macro Module
Indoor Cabinets
MBI5 GSM cabinet
or
9926 BBU
CPRI
Ethernet cable
TRDU 2X
Transceiver
Duplexer Unit
FDD
only
1 3 28
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Cube Indoor
Cabinet
Compact
indoor Rackmount shelf
Using TRDU, TMA could be needed depending on the distance between antenna and TRDU.
The 9412 eNodeB is a compact eNodeB in the Alcatel-Lucent Solution. The 9412 eNodeB is a self-contained
solution, often called the LTE cube or the 9412 eNodeB Compact smart.
Compact eNodeB can be located in indoor or outdoor environments :
Indoor cabinet, also called Cube Indoor Cabinet, designed to support LTE service in the 700 MHz
spectrum in a all in one cabinet.
Compact Indoor Rack-mount shelf
Outdoor cabinets (Baseband cabinet and RF cabinet)
The 9412 eNodeB is an integrated system. However, it is the same as a distributed eNodeB with a
separation of the digital and RF processing by a CPRI interface.
Electrical SFP are used to connect CPRI interface between the BBU and the macro module. In outdoor
configurations, Multi Mode Dual Fiber can also be recommended.
Functions:
RF converters
Tx amplifier
Features:
cell
Rx LNA
One TRDU supports 2X2 MIMO.
RF Filter
2 Tx path
EAC
RF jumpers
TRDU2X
TRDU Naming
BW
Frequency Band
Output
RF Power
TRDU2x40-07U
10 Mhz
2 x 40W
TRDU-2x40-07PS
5 Mhz
2 x 40W
TRDU2x40-08U
5 & 10 Mhz
2 x 40W
TRDU2x40-08L
5 & 10 Mhz
2 x 40W
1 3 29
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
CPRI
Base Band
Unit
Compact eNodeB
The TRDU (TRansceiver Duplexer Unit) has two RF transmitters (two Tx paths with 40W per path), two
receivers (Low Noise Amplifier) and a double duplex filter, packaged in a single shelf-mounted module.
It is MIMO capable and there is one TRDU2X per cell.
The nominal transmit power of the TRDU is 2 x 45 Watts at the duplexer ports : this is to support 40W at
the external antenna connector (EAC), (up to 0.5dB of loss in the jumper cable between the TRDU and top
of cabinet).
4 MC-TRX module
1 3 30
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
4 MC-TRX module
4G
Multistandard
1 3 31
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Multimode
Thanks to SDR, the module is able to handle simultaneously several carriers from different technologies and
offers the possibility to evolve smoothly from GSM to W-CDMA and LTE for a dedicated frequency band.
4 MC-TRX module
Digital module
9926 BBU
MC-TRX Module
CPRI
Ethernet cable
MC-TRX
FDD
only
1 3 32
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
MBI5 Cabinet
MBO2 Cabinet
The MC-TRX is a multi carrier transceiver which can operate in LTE technology only, but it is mainly
intended to be used in dual technology: LTE+GSM.
The MC-TRX is located in MBI5 and/or MBO2 GSM cabinets.
The MC-TRX takes place in subracks (called STASR) installed in indoor (MBI5) and outdoor (MBO2) GSM
cabinets.
The solution based on 9926 BBU + MC-TRX module in MBI/MBO cabinet is also called a 9412 Compact
enodeB.
4 MC-TRX module
2 LTE Tx path
AN
TRDU Naming
BW
Frequency Band
Total
Output
RF Power
MC-TRX
10,20
Mhz
1 x 60w
MC-TRX
CPRI
Base
Base Band
Band
Unit
Unit
GSM
GSM SUM-X
SUM-X
Backplane
Evolution Cabinet
1 3 33
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
60 watts are provided at RF module. 40 watts maximum for LTE carrier at top of Cabinet.
GSM SUM-X board is the controller board, the GSM modem is included in the MC-TRX module. MC-TRX and
BBU connection is ensured by the backplane.
The MC-TRX is connected to an Antenna Network (AN) before interfacing the antenna. The AN playing the
Duplexer role.
Following carriers/power configurations are available :
1 3 34
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Digital module
RF Module
9926 BBU
CPRI
optical
1 3 35
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
9442 RRH
Remote Radio
Head
The RRH (Remote Radio Head) module provides the RF part of the eNodeB. It includes :
At least two RF transmitters to enable 2x2 MIMO applications
Two Multi Carrier Power Amplifiers (MCPA)
Four 20MHz Receivers to support 4-way Receive Diversity
The RRH can be on the same site where the BBU is located, or on a remote site. In any case, the BBU and
the RRH are linked by optical fibers (CPRI). One optical link is used between the BBU and the RRH for both
UL and DL based band signals (and OAM info).
The HW is capable of supporting a single or multiple LTE carriers over up to 20 MHz of spectrum of
bandwidth.
The RRH includes :
Its own energy system
Its own cooling system
AISG interface (allowing remote control and monitoring capabilities of the antennas)
The outdoor PSU cabinets provide DC power supply to LTE equipments (BBU and RRHs).
They include AC/DC rectifiers, batteries, but also free space for other RAN equipments (GSM, W-CDMA,
CDMA).
Md4 outdoor cabinet, offering 14U user space can be used:
Frequency Band
Output RF Power
BW
2 x 40W
5, 10, 20 Mhz
RRH2x40-07L
2 x 40W
5,10 Mhz
RRH2x40-07U
2 x 40W
10 Mhz
RRH2x40-08
2 x 40W
5, 10 Mhz
RRH2x40-26
2 x 40W
10,20 Mhz
4 x 40W
(1.4, 3, 5, 10 ,15
or 20 Mhz)
1 3 36
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
RRH2x40-AWS
FDD
only
The RRH has 2 RF transmitters to enable 2x2 MIMO applications and 4 Receivers to support 4-way Receive
Diversity.
RRH delivers 40W output power per antenna connector when the RRH is configured with 2 independent RF
Paths (2x40W combined).
RRH4x40-19 supports simultaneoulsy CDMA and LTE signals over a 65Mhz band. Various configurations
are possible :
-from 0 up to 2 CDMA carriers
-from 0 up to 2 LTE carriers depending on chosen bandwidth
-LTE 2x2 MIMO or 4x4 MIMO
TD-RRH2x20
RRH Naming
Frequency Band
Output RF Power
TD-RRH2x20-23
2 x 20W
10, 20 Mhz
TD-RRH2x20-26
2 x 20W
10,20 Mhz
TD-RRH8x5-26
8x5W
10,20 Mhz
1 3 37
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
BW
TLA3.0
Sector 2
RRH 1
RRH 2
1 3 38
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Sector 3
RRH
FDD
only
LA3.0 eNodeB supports the deployment of RRHs with antennas in cross connect configuration.
This provides redundancy in the case of RRH failures as the eNodeB reverts to a SISO configuration on
detection of failure of an RRH.
In the Antenna Cross Connect configuration, each RRH serves one TX/RX path for two sectors. In case of
RRH failure, the eNodeB defense will change the diversity path of a remaining RRH into main path for the
affected sector.
CPRI fiber cable length to RRH shall be as much as possible the same for all RRHs (max.? Difference of
2meters) This fulfillment is mandatory to be in the 11ns maximum delay acceptable between TX Main and
TX Diversity paths of a RF sector.
5.5 RDEM
BBU
BBU
CPRI
RRH
RDEM
1 3 39
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Rx Only
FDD
only
9442 RRH2x40-26 can be equipped (factory configuration) with RDEM (Receive Diversity Expansion Module)
to provide 4-Way Rx Diversity.
Extension of a RRH with RDEM is not allowed on site as the configuration requires calibration at factory
level so if 4Rx Diversity shall be supported, the good RRH variant shall be ordered.
CPRI
RRH
L3
L1
UE
L2
CPRI
DAS
RRH
1 3 40
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
A Distributed Antenna System, or DAS, is a network of spatially separated antenna nodes connected to
a common source. The transmitted power is spit among several antennas, separated in space so as to
provide coverage over the same area as a single antenna but with reduced total power and improved
reliability.
A downlink broadcast signal can be sent to the users in order to allow a preliminary timing and frequency
estimation by the mobile.
The eNodeB has also to perform fine timing estimation when the signals coming from users are detected :
PRACH is used to obtain ne time synchronization by informing the mobile users how to compensate for the
round trip delay. After a successful random access procedure, the eNodeB and the UE are synchronized
within a fraction of the uplink cyclic pre x, and so, the uplink signals can be correctly decoded and does not
interfere with other users connected to the network.
The fiber connection between LTE modem and radio (RRH/TRDU) adds delay to eNodeB timing. This delay
impacts PRACH processing due to the round trip delay which skews the RACH preamble arrival time
at the eNodeB.
The eNodeB must adjust the center of its search window so that the search window range of the eNodeB
can be used fully for cell range.
From LA4.0, the eNodeB can compensate for BBU-RRH delay. The feature supports :
- a total distance from BBU to Antenna tip of up to 15 km without impacting the max cell radius (L3).
- a BBU-Radio distance up to 15 km
- A Radio to DAS antenna distance up to 400 m
TLA3.0 system supports a 10km fiber delay between BBU and RRH.
19W
44W
33W
0,3dB
TMA
Jumpers
0,5 dB
7/8" feeders
30m 2dB
Jumpers
0,4 dB
Jumpers
0,8 dB
(5m)
no more RF losses
66% more power @ antenna !
40W
Optical fiber
1 3 41
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
RRHs are designed for close connection to the antennas (3 to 5 meters maximum), therefore the usage of
TMAs between RRHs and antennas is not recommended.
Antenna
RF Feeder
Antenna
RF Jumper
RRH
Before
Radio
Optical Link
Digital
Digital
Backhaul
1 3 42
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Backhaul
After
On physical characteristic aspects, the RRH is a zero footprint solution, very light, which doesnt require
any craning for installation.
With a reduced power consumption and noise-free solution (no fan used), the RRH doesnt require any
maintenance.
1 3 43
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
1 3 44
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
6.1 Capacity
DRB
SRB
UE
S1-U
SGW
Assuming :
One 5MHZ cell/modem (or 10MHZ cell/modem)
4,5 data radio bearers/user in average
8 bearers/user at maximum
The SRB, Signaling Radio Bearer, is a bearer on the air interface used to carry the radio signaling (radio
bearer addition request or HO command for example) and the NAS signaling, i.e. the signaling between
the UE and the MME. The DRB, Data Radio Bearer, is used to carry the user traffic. Depending on the
service established for the user, it possible to have several radio bearers for the user traffic.
The eNodeB allocates dynamically the radio resources in UL and DL to all the DRB and SRB depending on
the amount of data, the QoS and the radio conditions.
up to 8 concurrent data radio bearers [that is, DRB(s)] per user are supoorted, as defined by 3GPP as
upper multi-bearer capability for UE categories 1 to 5.
The given eNodeB Software Capacity Configurations corresponds to the maximum number of Active
User(s) supported by an eNodeB from a software standpoint regardless of throughput constraints per
users that may be observed over the air interface.
LA3.0 supports for up to 167 Active Users assuming:
One 5 MHz-cell/modem or one 10MHz-cell / modem
Up to 4.5 concurrent data radio bearers/user in average. For example:
1 Default non-GBR DRB, plus
1 Dedicated non-GBR DRB (for example, SIP)
1 Dedicated GBR DRB (for example, VoIP)
1 Dedicated GBR DRB
0.5 Dedicated non-GBR DRB.
Up to 8 concurrent bearer/user at maximum regardless of the DRB type (that is, GBR or non-GBR).
In TLA3.0, the eNodeB software capacity is 100 active users per cell (with MIMO).
Copyright 2012 Alcatel-Lucent. All Rights Reserved.
TMO18213_V4.0-SG-Ed10 Module 1.3 Edition NA
Section 1 Module 3 Page 45
SW Reset
< 230
5620 SAM
SW
Software Download
Software Activation (eNodeB reboot)
Software Accept
1 3 46
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
FDD
only
1 3 47
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
TRDU 2X overview
CPRI ports
PRI & SEC
TX/RX Antenna ports
Power entry
1 3 48
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
AISG port
(Antenna Line Device)
MC-TRX overview
RX connectors
On/off switch
CPRI ports
PRI & SEC
1 3 49
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
TX connector
RRH 2X Overview
Top View
Power supply
Links to BBU (optic fiber)
Alarms
Bottom View
1 3 50
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The Alcatel-Lucent Remote Radio Head (RRH) specified here is a platform asset that can support LTE in
2.6GHz FDD frequency band. The unit has 2 RF transmitters to enable 2x2 MIMO applications. The RRH
specified is for 3GPP Band VII (2600MHz) and supports 2x40W..
1 3 51
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Fan Tray
Power
Distribution
Panel
3 TRDU2X
(3 cells)
1 3 52
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The eNodeB Indoor cabinet is optimized for small size and small footprint, with a size of 599mm in
width, 575mm in depth, and 675mm in height. It is a riveted cabinet, made of galvanized steel with
exterior powder coat. Assets are mounted along a horizontal upper and lower support shelf. Assets and
rack are EIA-310D compliant (19 standard rack).
From connectivity point of view, only the RF and GPS connectors are present and fixed to the cabinet:
6 ANT TX/RX (7/16 DIN coaxial female connector)
One GPS RX (N coaxial female connector)
The optical and alarm cables enter the cabinet through the top-left side and are directly connected to the
BBU and to the eAM board. The DC power cables enter the cabinet through the top-right side, and are
directly connected to the PDP.
1 3 53
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
In addition, there is also a cabinet called Compact Indoor Rack-mount shelf, designed for easy
integration in 19 or 23 standard racks.
eNodeB
Power
Distribution
Panel
TRDUs
BBU
Power
Distribution
Panel
Fan Tray
Fan Tray
BaseBand Cabinet
1 3 54
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
RF Cabinet
1 3 55
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
FDD
only
1 3 56
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The outdoor PSU cabinets provide DC power supply to LTE equipments (BBU and RRHs).
They include AC/DC rectifiers, batteries, but also free space for other RAN equipments (GSM, W-CDMA,
CDMA).
Two different PSU cabinets can be used:
Md4 outdoor cabinet, offering 14U user space
S3 outdoor cabinet, offering 11U user space
The cabinet can power several telco equipments (Installed inside):
LTE BBU or other technology Controllers (W-CDMA BBU or GSM SUMX)
Transport network elements like 9600 MPR or 7705 SAR
Up to 6 external RRHs.
9228 Macro
Reverse OCM
+
BBU
The eNodeB R-OCM configurations are supported in Modular Cell 4.0B and Compact Modular Cell 4.0B
cabinets. In Indoor Modular Cell 4.0B cabinet, the LTE BBU shares the same cabinet with CDMA
equipment.
In the case of Compact Modular Cell 4.0B outdoor cabinet, the LTE BBU is located in a separated
weatherized cabinet.
In both cases the R-OCM board is inserted in the CDMA Digital Module (CDM), in one free CCU slot (CDMA
Channel Unit).
End of module
LTE eNodeB Hardware Description
1 3 58
RAN TLA3.0-LA4.0 Technical Overview LTE eNodeB Hardware Description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
14
Section 1
RAN TLA3.0-LA4.0 Technical
Overview
Module 4
LTE RAN OAM description
9400 LTE
RAN TLA3.0-LA4.0 Technical Overview
TMO18213_V4.0-SG Edition 10
Blank page
142
Document History
Edition
Date
Author
Remarks
01
YYYY-MM-DD
First edition
Module objectives
Upon completion of this module, you should be able to:
Describe the main 5620 SAM features for the RAN
Describe WPS and NPO functions
Explain SON features
143
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
144
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Table of Contents
Switch to notes view!
1 eUTRAN management via 5620 SAM
1.1 5620 SAM System overview
1.2 configuration Management
1.3 5620 SAM eNodeB Self Configuration
1.4 5620 SAM support of eNodeB upgrade
1.5 Offline configuration
1.6 eNodeB Licensing
1.7 eNodeB Performance management
1.8 eNodeB Troubleshooting and Supervision
2 9952 Wireless provisioning System
2.1 Overview
2.2 5620 SAM and 9952 WPS : Offline configuration
3 9958 Wireless Trace Analyzer
3.1 WTA overview
4 9959 Network Performance Optimizer
4.1 Introduction to 9959 NPO
4.2 NPO Web client
4.3 PCMD
4.4 PCMD Real Time Monitoring Dashboard
5 Self Optimization Process
5.1 Self Organizing/Optimization Opportunities
5.2 eNB Self Establishment/Configuration
5.3 Intra-LTE ANR Configuration and Optimization
1 4 5 5.4 Inter RAT ANR
COPYRIGHT ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.
RAN TLA3.0-LA4.0
Overview LTE
RAN OAM description
5.5 Technical
Automatic
Configuration
of Physical Cell ID
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
5.6 Cell outage detection
Page
7
8
9
11
12
13
14
15
16
18
19
20
22
23
24
25
26
27
28
29
30
31
32
33
34
35
146
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
147
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Server + Database
Standby
Collocated
Distributed
Primary
Redundant solution
Standalone solution
Auxiliary
Managed Network
LA2.0
LA3.0
TLA3.0
148
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
eUTRAN
Reserved
Preferred
Backhaul
ePC
The 5620 SAM (Service Aware Manager) is a system that is designed to manage Alcatel-Lucent network
elements, or NEs, such as routers and switches.
A 5620 SAM system has client, server, and database components that are deployed in a standalone or
redundant configuration.
A 5620 SAM operator performs network management or system administration tasks using a GUI or OSS
client that connects to a main server. The main server sends and receives NE management traffic, and
directs optional auxiliary servers to perform intensive tasks such as NE statistics collection. Main and
auxiliary servers store information in the same 5620 SAM database.
5620 SAM runs on Solaris 10 on various SUN architecture (Intel, AMD, Sparc). As illustrated above, the
servers can be Co-located, Distributed and Georedundancy can be provided.
The 5620 SAM client runs on Windows-based PCs and Solaris-based platforms.
Citrix is supported.
Set/Get
SNMPv3
Trap
5620 SAM
Netconf
MIB
149
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Network Element
View
eNodeB Logical
View
1 4 10
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
5620 SAM
eNodeB and pre-provisioned NE
match during eNodeB
discovery
Pre-Provisionned
NE
Activation
Manager
DB
Configuration data is
pushed to the
template
1 4 11
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
WO
This feature describes the capability of the 5620 SAM to pre-provision eNodeB equipment, activate
discovery rules, and automatically configure and upgrade the software of managed NEs.
The user is able to create a pre-provisioned configuration either offline through the WPS, or online through
the 5620 SAM pre-provisioning capabilities. The goal of the first task is to provide users with a way to
create a starting configuration in terms of release, SW load state, and configuration parameters that will be
applied on the node when it appears in the network.
The user can specify which policy needs to be applied for discovery of the node. The process flow consists
of 4 main steps:
eNodeB auto-start
SW download
configuration deployment
This allows the user to control which steps are performed automatically, and which steps require manual
intervention from the user.
5620 SAM
SW
SW upgrade
policy
1 4 12
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
SW upgrade in 3 steps:
Software Download
Software Activation
(eNodeB reboot)
Software Accept
A framework for eNodeB SW upgrade is provided by the 5620 SAM through a policy-based mechanism. The
policy supports the following options:
z select
z schedule
z immediate
By default, there are pre-created policies that represent different families of nodes or technology areas. The
eNodeB policy is represented by the RAN Policy (ID 5). The user may create new policies, or modify those
that are already present by clicking on the Create or Properties buttons (respectively).
WO
Managed node
Activation
Manager
Logical object
manager
Online
configuration
Offline
configuration
5620 SAM
1 4 13
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
1 4 14
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The goal of this feature is to introduce a licensing mechanism for function and capacity, which are licensed
separately from the main eNodeB functionality set.
The license set that a customer purchases is produced by the LKDI and defined in a digitally signed file.
This file contains licenses that are applicable to the portion of the network that is covered by the
management scope of a single 5620 SAM platform.
This license file is placed on the 5620 SAM server and the file contents are used to control the online/offline
configuration of eNodeB features and capacities.
A licences can have an expiration date (feature license can no longer be configured).
Alarms are generated for event related to licence issues (invalid, usage expiratio, thresholds crossed,
license violations)
5620 SAM
SNMP
Local repository
9459 NPO
2
1 4 15
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The eNodeB automatically starts recording performance management statistics. Counters are stored in
eNodeB memory and the writen to a file at the end of the collect interval.
The user can create 5620 SAM RAN performance management policies with different granularities for
dedicated subsets of eNodeBs to retrieve collected data on the 5620 SAM servers. The collection policies
specify:
counters to collect
the length of time that the 5620 SAM database retains the collected Statistics
The 5620 SAM retrieves the statistics file from the eNodeB via SNMP at the end of the collection interval
that is defined in the policy. The default collection interval for statistics files is 15 min. Statistics are
collected and sent even when no counter changes are occurring on an eNodeB.
The 5620 SAM and managed eNodeBs must use a common time-synchronization server that runs a
protocol such as NTP. The retrieval of eNodeB PM statistics files by the 5620 SAM will fail when the
eNodeB and 5620 SAM real-time clocks are not synchronized.
Operators can view RAN performance management statistics using the statistics plotting framework of the
5620 SAM.
The counters can also be exported to OSS applications using the 5620 SAM-O interface (data converted to
3GPP XML format). An external system can retreive the collection via SFTP on northband interface to
integrate the results into 9459 NPO for performance monitoring and optimization.
1 4 16
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
5620 SAM provides states and statuses repotting for the underlying Managed Objects of the eNodeB:
z Administrative
(configurable): Operational,
Status : gives info on Communication status (read-only field) and Managed state
(declared in GUI but not connected).
z Availability
z Connection
z Alignment
{
Status :
softwareAlignmentStatus: used to indicate if requested SW version is running on eNodeB.
When not aligned, configuration operations are inhibited.
confAlignmentStatus: used to indicate the logical configuration alignment.
The 5620 SAM framework has been enhanced to support eNodeB-generated alarms and display them
within the alarm view in order to have one single point of alarming towards all NEs supported by the 5620
SAM (such as MME, eNodeB, SGw, and PGW). In addition, all functionalities of the 5620 SAM framework are
applicable to the alarms generated by the eNodeB (acknowledge, delete, filter, and view history).
5620 SAM
Ca
2
ll t
r
ac
e
CT Aux Server
9459 NPO/PCMD
Local repository
The 5620 SAM supports call trace on eNodeB NEs. Call trace is a function that collects call-level data on an
interface. . This data can be transferred to an external system for processing and analysis, and the
resulting information can help a network operator do troubleshoot performance issues, troubleshoot device
malfunctions, monitor resource usage for capacity management or validate end-to-end network
transmission.
Call traces sessions can be activated through 5620 SAM interface and are retreived from the eNodeB to the
5620 SAM. This feature requires dedicated HW called a Call Trace Auxilliary server to be added to the
existing 5620 SAM architecture.
The activation mechanisms are schedulable, and the system allows the retrieval of data in binary format via
UDP streaming and conversion into 3GPP format for external analysis.
The 5620 SAM supports the following call-trace session types:
cell-baseda trace that the 5620 SAM initiates at operator request or as a scheduled task
event-baseda trace that begins when a specified threshold value is reached
signaling-baseda trace that the 9471 MME initiates
debuga troubleshooting trace performed by Alcatel-Lucent technical support
Call trace requires SAM-A, SAM-E and SAM-P modules.
The 5620 SAM raises an alarm when it detects a call-trace condition.
5620 SAM supports integration with Wireless Trace Analyzer in LE3.0.
1 4 18
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
2.1 Overview
Planning tools
Other WPS
Initial snapshot
import and
resynchronization
Work-order export
for activation
Main NM server
1 4 19
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The 9452Wireless Provisioning System (9452 WPS) is a powerful tool suite that simplifies the provisioning,
reverse engineering or auditing of the network. WPS can be installed on any PC.
The 9452 WPS uses the rule sets, template and task-based wizards to hide the complexity of system
provisioning from the user while taking care of the vendor-specific and technology engineering guidelines.
Alcatel-Lucent's wireless network evolution toward further plug-and-play, self- organizing, self-optimizing
networks associated with the 9452 WPS delivers a much simplified operational system.
The Alcatel-Lucent 9452 WPS is a high-performance kernel that provides support to design and configure
Alcatel-Lucent LTE networks based on specific network recommendations. The Alcatel-Lucent 9452 WPS
offers a centralized view and configuration of all LTE RAN network elements (NEs) and parameters.
The Alcatel-Lucent 9452 WPS can be used for configuration at every stage of LTE RAN management
including:
z Data
z Data
z Data
The Alcatel-Lucent 9452 WPS manages configuration data coming from various sources and the file format
used is CM XML.
Very large networks are supported with workable and acceptable performance. TheAlcatel-Lucent 9452
WPS supports multiple Alcatel-Lucent 5620 Service Aware Manager(SAM) servers within a Regional
Operating Center (ROC).
WO
WO
5620 SAM
Operator
Local repository
On demand snapshot creation
or scheduled export
1 4 20
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
WO activation
Snapshot export
The snapshot is the current configuration of NE exported by the 5620 SAM. It can be a full configuration or
only a subset of managed objects. The snapshot data file for the eNodeB includes the following
identifications:
Hardware frame of the target eNodeB
Management information model version used to prepare the snapshot file
Specific build identity of the snapshot file
Workorder imports
The workorder is a list of configuration changes, for example, create, delete, and modify.
WPS loads a cmXML snapshot and creates workorders that contain actions/commands. The follow-up of
these configuration changes is done only in 5620 SAM. No status report is sent to WPS.
This feature provides enhancements to the area of Configuration Management by supporting the
configuration of 9412 eNodeB equipment.
In terms of off-line configuration, the 5620 SAM is able to interact with the WPS in order to exchange
configuration snapshots and workorders for bulk configuration changes.
In order to activate workorders produced by the WPS, the 5620 SAM provides a dedicated activation
manager that allows the user to manage the different sessions, import workorders, launch a wide set of
checks, and activate the changes in the network. In addition, the system provides a one-shot fallback
mechanism that allows users to revert the changes (reverse Work-order) that have been caused by
workorder activation.
Copyright 2012 Alcatel-Lucent. All Rights Reserved.
TMO18213_V4.0-SG-Ed10 Module 1.4 Edition NA
Section 1 Module 4 Page 20
Exercise
Does the SAM client an be installed on a laptop ?
yes, checking the prerequisites
no, SAM client requires Solaris based platform
What does the best describe the interaction between SAM and WPS?
NEs (eNodeBs) snapshots are done by the SAM and then exported to the WPS. The WPS
uses them to compute work orders that are transmitted to the SAM and then applied to
the NEs
WPS is used to provision the NEs, the result of this provisioning is called a snapshot
which is transmitted to the SAM which applies them to the NE
1 4 21
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
1 4 22
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Call traces
activation
request
Ca
ll
tr
ac
e
Call trace
5620 SAM
CT Aux Server
1 4 23
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
9958Wireless Trace Analyzer (WTA) is a post-processing and analysis tool for Call Trace data. The WTA
provides a quick way of analyzing end-to-end call scenarios that exist within any given set of traces.
The 9358 RFO used for W-CDMA optimization has evolved to the 9958 WTA (Wireless trace Analyzer), a
product used for both W-CDMA and LTE.
9958 WTA correlates trace data and provides per call trace analysis. Trace data is generated by the eNB,
9471 MME and S&P GW and analyzed by WTA (limited post-processing of S&P GW traces).
WTA supports tracing multiple UE sessions at the same time, can copy traces that match the category
that is wanted for future reuse, provides analysis reports in the form of call flow diagrams and detailed
message view.
The following interfaces are supported:
9471 MME: S1-MME, S11, S6a, S3, S10
eNB: S1MME, Uu, X2
S&P GW: S11, S5/S8
1 4 24
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
QoS analysis
GSM
WCDMA
LTE
Hardware inventory
management
Geographical analysis
1 4 25
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Diagnostic
The 9459 Network Performance Optimizer (9459 NPO) is the Alcatel-Lucent main solution for wireless
network optimization.
The 9459 NPO toolset enables QoS diagnostics, correlation of performance and configuration, QoS tuning is
based on network performance collection across multi-standard wireless networks (2G/3G/LTE).
The 9459 NPO includes advanced reporting functions and is intended for deployment at a regional level to
complement the capabilities of national network optimization solutions.
NPO is a GUI driven Alcatel-Lucent application with the flexibility for reporting (drag and drop, markers, and
so on) and creation of indicators. It offers the following multi-standard QoS monitoring and radio network
optimization facilities:
Powerful GUI supporting all the efficient use of the MS-PO functions
QoS analysis
Customizing
This product includes a powerful Oracle database containing performance measurements and calculated
indicators.
QoS analysis
Cartography
Radio tuning
1 4 26
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
The NPO client represents a PC machine running on Windows XP Professional SP2 or Windows Vista
operating system.Java 1.6 (JRE and JDK) and the Flash Player software must be installed on the NPO
Client.
The web client application allows the operator to browse the NPO topology and functions, and to execute
classical views and reports for a quick analysis of daily checks without running the NPO Analysis Desktop.
The main operations available with the web client application are:
z In
a web navigator, the operator can browse the topology and functions to set a double selection, and
then the operator can execute an interactive view, as in the Analysis Desktop
z Added
z The
operator can store selections as favorites. The web client provides a selection cart, which is a
preset of topology elements and function elements, in order to facilitate the use of selection lists.
4.3 PCMD
B counters
statistical EN
UE activity
PC
MD
UE activity
PC
MD
(E
NB
)
t
sta
(E
NB
)
l
i ca
ist
Ec
MM
rs
nte
ou
cla
ssi
ca
lP
M
file
PCMD (MME+ENB)
MME
PCMD (MME+ENB)
NPO
animated slide
1 4 27
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Based on
last 60
values
rate)
1 line
per MME
Highlight
based on
Threshold
MME 1
One or
more
charts
FCA%
CDR%
: last 10 mn
One or
more MME
per chart
Chart
area can
be hidden
MME 2
MME 3
FCA%
CDR%
: last 40 mn
Zoom
(Nice to have
Step 2)
1 4 28
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
1 4 29
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
1 4 30
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Overview
Self Optimizing Network (SON) feature introduced in 3GPP Release 8 reduces the operating expenditure.
The objective is to minimize pre-provisioning, manual network planning and human intervention during LTE
network deployments.
The SON features are implemented using the centralized solution technique. Centralized SON is a SON
solution, wherein SON algorithms are executed in the OAM system. In such solutions, the SON functionality
resides in a small number of locations, at a high level in the architecture.
In the Alcatel-Lucent LTE solution, all the mechanisms and SON algorithms are implemented either in
eNodeB, SAM, WPS, NPO or other OAM tools. Centralized automatic allocation of PCI is one of the features
of SON. It automatically allocates a PCI value for each cell from the OAM system, and ensures the
uniqueness within the area of the neighbor cells and the neighbors neighbor cells.
There are 504 unique physical-layer cell identities. A physical-layer cell identity is uniquely defined by a
number in the list of 0 to 167, representing the physical-layer cell-identity group, and a number in the list of
0 to 2, representing the physical-layer identity within the physical-layer cell-identity group.
The physical cell identity is used in the generation of the cell-specific reference signal, as well as the
primary and secondary synchronization signals. The physical cell identity must be unique within a given
region, as it is used to identify a cell in the UE eNodeB interactions.
MME
5620 SAM
eNodeB Discovery :
connection established.
Authentication with SNMPV3
eNOdeB
1
preparation
DHCP
Server
Security
Gateway
9
eNB is establishing an IPsec
tunnel to the security gateway
and connect to MME
IP Network
2
6
7
1 4 31
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
eNodeB power up
eNB is rebooting
z This
feature describes a range of requirements for the automatic self-configuration of the eNB during
initial deployment or subsequent upgrades. It includes a number of distinct functions:
eNB Self-Test
Plug-and-play eNB
Automatic inventory
Auto SW Download
z Driving
towards zero-touch comissioning LTE eNB, this feature reduces the planning&deploymentrelated CAPEX and OPEX of the operator by automating the currently manually intensive tasks of
deploying, initial configuration and subsequent configuration updates of a deployed eNB. In addition it
will further speed up the time between the eNB switch on and the eNB becoming operational. Rollout
Time To Market shall be reduced allowing faster profitability.
2 check
UE reports that
PCI 5 has strong
Signal
FDD
only
5620 SAM
Check operator preferences
before NRT table
3 update
X2
MME
Cell B : PCI 5 , Cell
Global ID 19
1 4 32
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
FDD
only
UE reports
strongest cell for
given UTRAN freq
2 check
5620 SAM
NodeB
1 4 33
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
EUTRAN can automatically generate and manage neighbor relation tables that include UMTS neighbours
(L108084.1) : inter-RAT automated neighbor list information are obtained only from UE measurements
since there is no X2 interface to IRAT neighbors.
In order to discover unknown UTRAN neighbors, the eNB must provide UEs with a measurement
configuration to report the strongest cells for a given UTRAN frequency. One of the main difference
between inter-RAT and LTE ANR is the fact that event-triggered measurement reports cannot apply to
inter-RAT. Inter-RAT ANR measurements need to be re-configured periodically to ensure efficiency of the
ANR function.
When a new UTRAN neighbor (FDD only) is discovered (meaning Primary Scrambling Code received in the
measurement report is unknown to the eNB), the eNB will ask the UE to perform the CGI reporting
procedure.
LAC and RAC are present in the measurement report received from the UE, they are used to characterize
an UTRAN neighbor relation. The new neighbor will automatically be added as an
UtraFddNeighboringCellRelation object in the NetConf MIB. As soon as an UTRAN neighbor has been added
in the NetConf MIB, it can be used for inclusion in UTRAN inter-RAT mobility measurements configured to
the UEs. This is exactly same behavior as if the neighbor relation would have been created online by the
operator through the OMC.
Each time an UTRAN neighbor relation has been discovered, it needs to be associated to the RNC serving
the target cell in order to make possible outgoing mobility towards UTRAN. The ANR function will support
retrieving RNC id from cell id.
Copyright 2012 Alcatel-Lucent. All Rights Reserved.
TMO18213_V4.0-SG-Ed10 Module 1.4 Edition NA
Section 1 Module 4 Page 33
PCI algo
UE reports measurement
but Source eNodeB is
confused with provided
PCI
Collision Free:
CellID unique to immediate neighbours
1 4 34
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
PCI algo
Confusion Free:
CellID unique to neighbours neighbours
COPYRIGHT ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.
A physical-layer cell identity must be allocated to each cell, it is defined by a physical cell-identity group and
physical identity within the group (from 0 to 2). There are 504 PCIs available per network. This identity is
the cell identity on radio side. For PCI allocation, there are constraints related to not reusing the same
value among a given cell and its neighbours.
The PCI SON feature is used to select and configure a PCI value for each cell, taking into account
constraints, detect potential conflicts and solve these conflicts autonomously.
The eNB shall use a list of allowed PCI values received from the OAM and use any incoming information
(from connected UEs and neighbor eNodeBs) to eliminate values that would already be in use by neighbor
cells and choose randomly one of the values that remain free to use.
This highlights the dependency between this function, dynamic X2 configuration and ANR.
PCI collision: two cells that are neighbors share the same PCI. Consequence: At best, a UE will be able to
access one of the cells but will be highly interfered.
PCI Confusion : when a cell has two neighbors sharing the same PCI, the eNB knows of only one cell and
could trigger a UE handover to that cell, whereas the UE may have been reporting the other cell. This may
lead to a high number of handover failures and ultimately, call drops
No RRC connected UE :
sleepingCellInactivityTimer
timer is triggered
Last UE leaves
coverage area
Expiracy
5620 SAM
Sleeping cell
alarm raised
UE back in cell
covergae (RRC
connection)
5620 SAM
Sleeping cell
alarm cleared
In the future, the sleeping cell information will be used by the SON
compensation mechanism to realize self-healing.
1 4 35
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
FDD
only
Unplanned Outages can be hardware/software failures, external failures (such as power failure, S1
failure). This kind of outage is accompanied by alarms, but for Sleeping Cells, there is no standard failure
indication.
If the cell is enabled and is not locked (no planned outage), barred, or reserved and the last call ends (no
more RRC connected UEs) a specific timer set to sleepingCellInactivityTimer starts :
If a UE successfully connects with the cell, then stop the timer
If the timer expires, raise a MAJOR alarm that is visible at 5620 SAM
If a UE successfully connects with the cell while the sleeping cell alarm is set, then clear the alarm
If the value of parameter sleepingCellInactivityTimer is 0, then the feature is disabled.The value must be
tuned for each cell, depending on the expected traffic levels, to avoid excessive alarms.
In the future, the sleeping cell information will be used by the SON compensation mechanism to reconfigure
the network to reduce the outage impact.
End of module
LTE RAN OAM description
1 4 36
RAN TLA3.0-LA4.0 Technical Overview LTE RAN OAM description
9400 LTE RAN TLA3.0-LA4.0 Technical Overview
Congratulations
You have finished the training
Your feedback is appreciated!
Please feel free to Email your comments to:
training.feedback@alcatel-lucent.com
Please include the training reference in your email (see cover page)
Thank you!
@@PRODUCT
@@COURSENAME