LTE eUTRAN Technical Overview
LTE eUTRAN Technical Overview
Switch toUSEnotes
TERMS OF view!
AND LEGAL NOTICE
Alcatel-Lucent provides this training course to you subject to these Terms of Use and Legal Notice. Your use of this training
course and/or this site constitutes your acceptance of and agreement to these Terms of Use and Legal Notice. These Terms
of Use and Legal Notice, as well as the contents of this training course, may be updated or amended by Alcatel-Lucent from
time to time without prior notice to you. Your use of the Alcatel-Lucent training materials after such update or amendment
constitutes your acceptance of and agreement to said updated or amended Terms of Use and Legal Notice.
SAFETY WARNING
Alcatel-Lucent training materials can be for products or refer to products that have both lethal and dangerous voltages
present. Always observe all safety precautions and do not work on the equipment alone. The user is strongly advised not to
wear conductive jewelry while working on the products. Equipment referred to or used during this course may be
electrostatic sensitive. Please observe correct anti-static precautions.
exploiting any of the Content, in whole or in part, for uses other than those expressly permitted herein is strictly prohibited
@@COURSENAME
and shall not be made without Alcatel-Lucent’s prior written consent. All characters appearing in this training course are
fictitious. Any resemblance to real persons, living or dead, is purely coincidental.
There may be a number of proprietary logos, marks, trademarks, slogans and product designations found in the
Content. Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logos are trademarks of Alcatel-Lucent. All other trademarks
are the property of their respective owners. Alcatel-Lucent does not grant you a license to use any of the foregoing logos,
marks, trademarks, slogans and product designations in any fashion. Granting of the right to access and use the Content for
training purposes does not confer upon you any license under any of Alcatel-Lucent’s or any third party's IP Rights.
DISCLAIMER
ALCATEL-LUCENT DISCLAIMS ALL WARRANTIES REGARDING THE TRAINING COURSES OR THE CONTENT, EXPRESS OR
IMPLIED, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. THE ALCATEL-LUCENT WILL NOT BE RESPONSIBLE OR LIABLE FOR ANY INJURY, LOSS, CLAIM,
DAMAGE, OR ANY SPECIAL, EXEMPLARY, PUNITIVE, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES OF ANY KIND
(INCLUDING WITHOUT LIMITATION LOSS PROFITS OR LOSS SAVINGS), WHETHER BASED IN CONTRACT, TORT, STRICT
LIABILITY OR OTHERWISE, THAT ARISES OUT OF OR IS IN ANY WAY CONNECTED WITH (A) ANY USE OR MISUSE OF THE
CONTENT OR THE TRAINING COURSES BY YOU, OR (B) ANY FAILURE OR DELAY BY ALCATEL-LUCENT, ITS OFFICERS,
DIRECTORS, AGENTS OR EMPLOYEES IN CONNECTION WITH THE CONTENT OR THE TRAINING COURSES (INCLUDING,
WITHOUT LIMITATION, THE USE OF OR INABILITY TO USE ANY COMPONENT OF THE CONTENT OR TRAINING BY
YOU). SOME JURISDICTIONS LIMIT OR PROHIBIT SUCH EXCLUSION OF WARRANTIES OR LIMITATION OF LIABILITIES
AND SO THE FOREGOING EXCLUSION OF WARRANTIES OR LIMITATION OF LIABILITY MAY NOT APPLY TO YOU.
GOVERNING LAW
These Terms of Use and Legal Notice are governed by the laws of France. The operation and use of the training course is
governed by the laws of the country that governs your employment contract, if applicable. If any provision of these Terms of
Use and Legal Notice, or the application thereto to a person or circumstance, is held invalid or unenforceable by law, statute
or a court of competent jurisdiction, for any reason, then such provision shall be modified and/or superseded by a provision
that reflects the intent of the original provision as closely as possible. All other provisions of these Terms of Use and Legal
Notice shall remain in full force and effect. You may not assign these Terms of Use or any permission granted hereunder
without Alcatel-Lucent’s prior written consent. Nothing herein shall be deemed an employment agreement or an offer of
employment or an alteration in any way of a user’s terms of employment with or within Alcatel-Lucent.
Copyright © 2013 Alcatel-Lucent. All Rights Reserved
z LTE completion
Upon RAN of this course, you should be able to:
LR13.3L
Describe 9400 and
functions LTEthe RAN Technical
architecture of aOverview
LTE Access network
Describe the IP transport layer in the radio Access Network
Describe the portofolio
Upon completion of this of the Alcatel-Lucent
course, LTE to:
you should be able Radio equipment
Describe the eNodeB Operation and Maintenance Principles
[Link]@[Link]
Thank you!
Section 1
eUTRAN Technical Overview
Module 1
LTE eUTRAN Overview
TMO18213_V7.0-SG-LR13.3L-Ed1 Module 1.1 Edition 1
LTE RAN
LR13.3L 9400 LTE RAN Technical Overview
TMO18213_V7.0-SG Edition 1
Document History
1·1·4
This page is left blank intentionally
COPYRIGHT © ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.
eUTRAN Technical Overview · LTE eUTRAN Overview
LTE RAN · LR13.3L 9400 LTE RAN Technical Overview
1·1·6
eUTRAN Technical Overview · LTE eUTRAN Overview
ThisCOPYRIGHT
page© ALCATEL-LUCENT
is left blank2013. ALL intentionally
RIGHTS RESERVED.
GMLC LSC-client
9981CMS
/LRF SLh
SLg
SBc CBC
eNodeB S6a
S1-MME HSS
M3 MME S11
X2
SLs
IP network SeGW PCRF
E-SMLC Sm
M1 MBMS BM-SC
-GW
Gx
eNodeB
S1-Ui S5/S8
SGW PGW SGi
PDN
: User plane
: Control plane
LTE network which is a Packet switched (PS) only system and is all-IP, because every standardized interface is based on a
protocol stack where L3 is IP.
The Evolved Packet System provides IP connectivity between a UE and a PLMN external packet data network and is referred to
as PDN Connectivity Service.
• The E-UTRAN consists of set of eNodeBs connected to the EPC (MME, SGW, PGW, PCRF) through the S1 (S1-U for user plan
and S1-MME for control plan). eNodeBs can be interconnected through the X2. The E-UTRAN is layered into a Radio Network
Layer (RNL) and a Transport Network Layer (TNL).
The LTE architecture can be further described as follow:
● S1-U: Reference point between E-UTRAN and Serving GW for the per bearer user plane tunnelling and inter eNodeB path
switching during handover.
● S1-MME: Reference point for the control plane protocol between E-UTRAN and MME.
● S11: The interfaces between MME and SGW provide control of bearer establishment.
● S5: It provides user plane tunneling and tunnel management between Serving GW and PDN GW. It is used for Serving GW
relocation due to UE mobility and in case the Serving GW needs to connect to a non-collocated PDN GW for the required PDN
connectivity.
● S6a: This interface is defined between MME and HSS for authentication and authorization.
● Gx: It provides transfer of (QoS) policy and charging rules from PCRF to Policy and Charging Enforcement Function (PCEF) in
the PGW.
● GMLC (Gateway Mobile Location Center) and E-SMLC (Evolved Serving Mobile Location Center) are used for example in case
of emergency call to get the position of the UE.
● CBC (Cell Broadcast Center) is used to forward Warning Message via the MME to the appropriate eNodeB(s) (which may
impact a geographical region) and then broadcasted using a paging channel. It’s a signaling message to notify UE’s in an area
(case of earthquake, tsunami, …)
● MBMS GW (Multimedia Broadcast/Multicast service Gateway): MBMS is a broadcast service in which data (multimedia: Film,
Video, …) is transmitted from a single source entity to multiple recipients (mode Broadcast or Multicast). The signaling messages
are send on the interfaces Sm and M3 (Control plane). M1 is used as user plane.
● Alcatel-Lucent 9981CMS (Certificate Management Server) is in charge of delivering online/offline certificates to activate
IpSec tunnel between the Security Gateway and the eNodeB.
eUTRAN ePC
eNodeB MME PCRF
NAS Security
RRC Connection
SGW PGW
Admission control
UE IP address
allocation
Measurement Mobility
Configuration Anchoring
Packet Filtering
eNB :
• It schedules the user traffic each 1 ms in DL and UL and it takes in account the QoS parameters associated to
the data (real time, guaranteed bit rate),
• It controls the creation, modification and release of the (RB) radio bearers,
• It handles the RRC ( Radio Resource control) connection for each UE,
• It performs an admission control to avoid to accept too many users,
• It configures the UE measurements on the adjacent cell to manage the mobility by Handover mechanism.
MME:
• NAS (Non Access Stratum) signaling and NAS signaling security,
• 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 list
management (for UE in idle and active mode),
• PDN GW and Serving GW selection, MME selection for handovers with MME change, SGSN selection for
handovers to 2G or 3G 3GPP access networks,
• Roaming, Authentication, Bearer management functions including dedicated bearer establishment,
PCRF:
• The PCRF (Policy Control and Charging Rules Function) is a functional element that encompasses policy control
decision and flow based charging control functionalities.
SGW:
• The SGW routes and forwards user data packets, while also acting as the mobility anchor for the user plane
during inter-handovers and as the anchor for mobility between LTE and other 3GPP technologies.
PGW:
• The PDN Gateway provides connectivity from the UE to external packet data networks by being the point of
exit and entry of traffic for the UE. A UE may have simultaneous connectivity with more than one PGW for
accessing multiple PDNs. The PGW performs policy enforcement, packet filtering for each user.
GTP-U
SCTP UDP
IP IP
Data link Layer Data link Layer
Physical Layer Physical Layer
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.
GTP-U
UDP SCTP UDP
IP IP IP
Data link Layer Data link Layer Data link Layer
Physical Layer Physical Layer Physical Layer
Other protocols:
● SBcAP is used between MME and CBC
● CMP v2 is used between 9981CMS and SeGW
● M3AP is used between MME and eNB
UE MME 1
ar t
lo ad st
Over
MME 2
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.
Tracking Area Up
request including date Overload start
GUTI
Overload action included
Tracking Area Up
request includin date Overload stop
g GUTI MME
2
S1AP (NAS TAU Req
uest)
Following mapping is performed between Overload Action and RCConnection Establishment Cause (EC)values:
‘MT’ stands for ‘Mobile Terminating’ and ‘MO’ for ‘Mobile Originating’.
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
In the TCP/IP suite, what is (are) the layer 4 protocol(s) used for
interfaces :
S1-U? S1-MME ?
IPv4 IPv4
IPv6 IPv6
TCP TCP
UDP UDP
SCTP SCTP
In the TCP/IP suite, what is (are) the layer 3 protocol(s) used for
interfaces :
S1-U? S1-MME ?
IPv4 IPv4
IPv6 IPv6
TCP TCP
UDP UDP
SCTP SCTP
a)Increase throughput
b)Increase SNR
c)Simplify eNodeB algorithms
a)Rx diversity
b)Tx diversity
c)DL_MiMo Single user
d)UL_Mimo Multiple User
e)DL_MiMo Single user
f)UL_Mimo Multiple User
700MHZ
800MHZ
2,6GHZ
Every handset that has a listening CB channels enabled and is within the coverage area
of cells that are broadcasting a CB message, will receive this message.
PWS
(Public Warning Services)
CB CMAS
(Cell Broadcast) (Commercial Mobile Alert System)
Using Cell Broadcast (CB) technology and the CMAS (Commercial Mobile Alert
System) recommended as standardized network architecture, allows cellular
subscribers to be alerted based on their location at the time of the alert even
when the network is congested.
CMAS system in Japan or US country is deployed to allow federal agencies to accept and
aggregate alerts from first the President, the National Weather Service (NWS) and emergency operations
centers (EOCs), then send the alerts to participating wireless providers who will distribute them to their
subscribers.
Cell Broadcast is location specific; only people in the disaster area, to whom it concerns, are
contacted; enabling real-time crowd control, guiding them to safety.
Alert Origination
CMSP
Gateway
3
1
CMSP
(Commercial Mobile Service Provider )
Federal Agencies
CBC
2
SBc
Alert
Alert Aggregation
Gateway
MME
Local
EOC
Public Warning systems are used to broadcast public warnings and emergency messages during events such as
natural disasters. It exists 2 variant of PWS :
Earthquake and Tsunami Warning system (ETWS) used in Japan, Commercial Mobile Alert System (CMAS),
used in Americas. It is used to send emergency alerts as text messages to CMAS capable handsets.
The CMAS network will allow the Federal Emergency Management Agency (FEMA), to accept and aggregate
alerts (several levels defined : Presidential, Imminent Threats and Child Abduction Emergency / AMBER
Alerts.
The alerts are sent over a secure interface to participating commercial mobile service providers (CMSPs)
that will then distribute the alerts to their users.
The CMSP Gateway interfaces to the Federal Alert Gateway for application-dependent functions, and it interfaces
with the carrier network for technology-dependent functions.
The CBC determines the impacted network elements for CMAS alerts and manages the transmission and
retransmission of the alerts received by the CMSP Gateway.
Cell Broadcast Center (CBC) and CMSP Gateway functions are both supported by ALU 5140 BMC (Broadcast
Message Center) product.
The MME selects the appropriate eNBs based on information provided by the CBC and forwards the messages to
the selected eNBs.
The eNB performs the transmission and re-transmission of CMAS notifications over the air interface.
The eNB uses enhanced RRC Paging to alert CMAS-capable UEs of the presence of CMAS notification broadcast
in the eUTRAN (CMAS messages are broadcasted on SIB12).
The CMAS (Commercial Mobile Alert System) is the principal alert system
CBC that allows broadcasting short messages to UEs present in specific cells of the
network. It relies on SIB12 transmission.
SBc
The MME selects the appropriate eNB(s) based on information provided by the
CBC for the purpose of CMAS message distribution and forwards these messages
MME to the selected eNBs.
The eNB Determines the affected cells from the notification list in the
message.
S1-
MME For each affected cell, it:
• Schedules the transmission of SIB12,
• Indicates the scheduling of the SIB 12 in SIB,
• Prepares SIB12 which contains the CMAS notification message then begins
transmitting SIB12 over the air interface on the schedule indicated.
eNB
The eNB uses RRC Paging to alert CMAS-capable UEs of the presence of CMAS
notification broadcast(s) information.
MME CBC
SBcAP SBcAP
SCTP SCTP
IP IP
Data link Layer Data link Layer
Physical Layer Physical Layer
SBc
The SBc-AP is the application between the MME and the Cell Broadcast Center (CBC) and is used to transport
messages associated with the Warning Message Delivery function.
Transport Rule:
• supports IPv4, IPv6, or IPv4 and IPv6 addressing
• Recommended port for Sbc is the SCTP port 29168 SBcAP is defined in 3GPP TS 29.168.
Optional
Shared MME/ SGW Shared MME/ SGW Shared MME/ SGW
S1 Flex
S1
Two different network sharing architectures are described in 3GPP TS 23.251 recommendation: Multi-
Operator Core Network (MOCN) and Gateway Core Network (GWCN)
In MOCN, only the radio resources are common to 2 or more operators. The ePC elements are not
shared. S1-flex interface allows for a single eNodeB to be connected to several ePCs and/or several MME and
SGW in a given ePC.
In GWCN architecture, some elements of the Core (MME/SGW) might also be shared by several operators
(in addition to radio resources)
Plmn A&B
frequency
f1+f2
Shared Spectrum
The spectrum allocated to operators involved in a RAN sharing agreement might be dedicated or shared.
In dedicated spectrum mode, available spectrums are partitioned with portions dedicated to each
partner operator.
This mode of sharing may lead to denial of service to one operator’s subscribers
when its entire spectrum is in use, while there is still available bandwidth in the partner’s spectrum.
In shared spectrum mode, available spectrums are pooled and accessible to all subscribers of the
partner operators. This mode of sharing provides more efficient use of the radio spectrum. However,
depending on the resources allocation strategy selected, fairness cannot be guaranteed if subscribers of
one operator overload the shared carrier.
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
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
8 ANT TX/RX
RF module RRH
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;
Sm
Allocates radio
BM-SC
resources Content provider data
M3 SGmb
SGi-mb
M1 MBMS GW
1
Service
announcement
MCE
UE Session
3
eNodeB start/stop
2 Service joining
4 Service leaving
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).
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 MBMS Session Control Signaling on EPS bearer level.
The e-MBMS GW has 3 interfaces :
z Sm control plane interface , MBMS Session Control Signaling via MME.
z pure user plane M1 interface to eNodeB used to transport user IP Multicast flows
z SGmb and SGi-mb interfaces to BM-SC
M3 Interface between the MCE and the MME is used for eMBMS Session Control Signaling on E-RAB level including eMBMS Session Start
and Stop. M3 is SCTP based.
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, resources are released by the network. The user indicates that he no longer wants to subscribe to the session in the
leaving phase.
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TMO18213_V7.0-SG-LR13.3L-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 28
2.4 eMBMS
2.4 eMBMS architecture [cont.]
The eMBMS control plane is implemented by introducing an MCE inside the
eNodeB.
M1 Data SGi-mb
eNodeB Core + RAN MBMS BM-SC
M2 transport network M3 Control Sm GW SGmb
MCE
MME
9471 WMM 9774 LMG
MBMS GW: MBMS Gateway: Broadcast services’s contents to eNB using IP multicast and
SYNC prot.
LMG: LTE Multimedia Gateway
This feature enables deployment of eMBMS by providing commercial support of eMBMS for both User Plane and
Control Plane with distributed Multi-cell/Multicast Coordination Entity (MCE).
The feature 158990 implements the eMBMS control plane by introducing an MCE inside the eNodeB.
Capabilities provided include the following:
z M3 Interface for Control Plane
z M2 Interface internal to eNodeB
z IP Multicast: support of Internet Group Management Protocol (IGMP) (used over IP V4) and Multicast
Listener Discovery (MLD) (used over IP V6)
z Feature under License per eNodeB
Note: The MCE can be used via two licences: LTE eNB integrated MCE application and LTE eMBMS support
up to 15 bearers.
MCE distributed and eNodeB integrated coordinates the radio resources in MBSFN area.
The MCE allocates radio resources semi-statically for eMBMS services according to the M3-AP procedures
(session start and session stop).
Resources can be allocated and released as needed by the eMBMS traffic instead of being statically allocated by
OAM (which was the LA5 allocation method).
Nota: This feature is detailed in the training module: TMO18514_V1.0-SG Edition 1 9400 LTE LA6.0-LR13.1L
Telecom Evolution Description
TRUE FALSE
The public warning system cell broadcast enables sending out a short
message to all handsets in a particular cell, group of cells, or the
entire network.
The SBc interface is the reference point which lies the cell broadcast center
(CBC) and the eNodeB for warning delivery and control functions.
a) S1-AP, M1, M3
b) SGmb, M3, Sm
c) Sm, M1, S1mme
d) Sm, M1, SGmb
Section 1
eUTRAN Technical Overview
Module 2
LTE Transport overview
TMO18213_V7.0-SG-LR13.3L-Ed1 Module 1.2 Edition 1
LTE RAN
LR13.3L 9400 LTE RAN Technical Overview
TMO18213_V7.0-SG Edition 1
Document History
1·2·4
This page is left blank intentionally
COPYRIGHT © ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.
eUTRAN Technical Overview · LTE Transport overview
LTE RAN · LR13.3L 9400 LTE RAN Technical Overview
Page
IP Backhaul
PCRF
MME PDN GW
SGW Evolved Packet
Core (IP)
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.
P-GW S-GW
EPC MME PCRF
Applications
IMS
Ethernet HLR/HSS
HLR AAA
ATM
Backhaul
7710/
7705 7750SR
Internet
Aggregator
TDM
RNC
BSC
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
NodeB MME
PCRF
nxE1 eNodeB
(ATM) SGW PGW
7705 SAR-F
Backhaul UTRAN
RNC
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.
Each SFP cage can be equipped with an optical or Gigabit Ethernet (MDA)
electrical TRX. eNodeB only enables one ETH PHY •2 SFP cages for optical GE
device of GE-MDA. •1 RJ45 for electrical GE
eCCM/eCCM2 only supports one Ethernet port that is used for backhaul access.
The GE MDA (eCCM) provides on the face plate three GE ports, two SFP cages and one RJ45.
The choice was done to enable the ETH PHY which handles SFP2 and RJ45. SFP1 can't be used at all.
SFP2 or RJ45 are mutually exclusive:
• The default Ethernet backhaul interface is the electrical RJ45.
MDA: Media dependent adapter
2- Which technique allows to handle ATM, TDM and Frame Relay over Packet
Service Network?
a) Encryption
b) Pseudowire
c) Aggregation
a) The GE MDA provides on the face plate fours GE ports, two SFP cages and
two RJ45.
b) The GE MDA provides on the face plate three GE ports, three SFP cages.
c) The GE MDA provides on the face plate three GE ports, two SFP cages and
one RJ45.
d) The GE MDA provides on the face plate fours GE ports, three SFP cages and
one RJ45.
S1
GigE X2
IPV4 addressing only
OAM
No VLAN
FDD+TDD 1588 OAM S1-U S1-C X2-U X2-C M3 M1-U
Config 1 IPv4@1 IPv4@2
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.
MBMS: Multimedia Broadcast/Multicast Service is a broadcast service (video,…) in which data is transmitted from
a single source entity to multiple recipients. The MME determines which eNode’s are in the MBMS broadcast
services area and transmits session control messages towards the appropriate nodes using the M3 interface. M1
interface is used between MBMS GW (gateway) and eNB’s for data distribution (M1 is pure user plan interface).
The eNodeB is pre-configured with a default OAM VLAN ID value of 400 at factory. At Integration and
commissioning, it’s possible to change the value if needed.
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.
S1
X2 IPV4 addressing only Or
GigE VLAN
OAM IPV6 addressing only
VLAN 1
FDD + TDD
1588 OAM S1 X2
Config 1 IPv4@2 IPv4@1 IPv4@3
Config 2 IPv4@1
Config 3 IPv4@1 IPv4@2
Config 4 IPv4@1 IPv4@2
Config 5 IPv6@1 IPv6@2
1588 OAM S1 X2 M3 M1
Config 1 IPv4@2 IPv4@1 IPv4@3
Config 2 IPv4@1 IPv4@2
Config 3 IPv6@1 IPv6@2
Config 4 IPv4@1 IPv6@2
Config 5 IPv4@2 IPv4@1 IPv6@3
Config 6 IPv6@2 IPv6@1 IPv4@3
IPv6@ IPv6
X2-C + M3
3 @4 IPv6@3
Config 9 IPv6@2 IPv6@1 IPv6@4 No IP @
S1-U S1-C X2-U
MBMS: Multimedia Broadcast/Multicast Service is a broadcast service (video,…) in which data is transmitted from
a single source entity to multiple recipients. The MME determines which eNode’s are in the MBMS broadcast
services area and transmits session control messages towards the appropriate nodes using the M3 interface. M1
interface is used between MBMS GW (gateway) and eNB’s for data distribution (M1 is pure user plan interface).
5620
MME
SAM
OAM VLAN
GigE Telecom VLAN
MBMS-
GW
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 downwlink multicast traffic, no uplink eMBMS traffic originates from eNodeB.
ALU eNodeB supports the Multiple Operators Core Network (MOCN) model where all
operators share the RAN resources (eNodeBs, backhaul) while each operator manages its own
core network (MMEs, SGWs).
The L2 backhaul access is shared between the operators but the telecom traffics of the
operators are logically separated logically with VLANs. This allows each operator to manage its
own policy for QoS.
eUTRAN sharing is supported with up to 4 operators.
The X2-C traffic cannot be
split between operators and
is carried in the telecom SGW PGW
VLAN of the master operator. CN (Operator A)
Backhaul
SGW PGW
Shared
eUTRAN CN (Operator B)
VLAN1 VLAN2
S1-U S1-C X2-U X2-C
1588 OAM All
Master Operator Only
Operators
Config 1 IPv4@2 IPv4@1 IPv4@3
Config 2 IPv4@1 IPv4@2
Config 3 IPv4@1 IPv6@2
Config 4 IPv6@1 IPv6@2
(1) 1588 requires a dedicated IPv4 address. 1588 is not supported over IPv6.
(2) M1-U is not supported with eUTRAN sharing.
(3) OAM must be mapped on the first TrafficDescriptor instance of the first VLAN instance.
VLAN3
S1-U S1-C X2-U
1588 OAM X2-C
Non Master Operator
Config 1 IPv4@n+3
Config 2 IPv4@n+2
Config 3 IPv6@n+2
Config 4 IPv6@n+2
5620SAM
IPv4
O&M network
MME
UE
OAM VLAN
GigE
Telecom VLAN
IPv4
Backhauling
network for
IPv6 SGW
Telecom
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.
5620
SAM
MME
IPv6
GigE VLAN
SGW
5620
SAM
IPv6
MME
IPv6
OAM VLAN
GigE
Telecom VLAN
SGW
IPv6 as specified in IETF RFC 2460 is supported for the Telecom traffic (S1 & X2) and for OAM.
eNodeB does not support IPv6 for 1588v2 traffic.
OAM IP address can be set manually during eNodeB commissioning or can be distributed by a DHCP server.
DHCPv6 is used to retreive OAM IPv6 address.
Telecom address is then provisonned by the NM during commissioning phase.
The no VLAN configuration is not supported in IPv6, IPv6 traffic is carried over tagged Ethernet frames.
IPv6 does not support the 1588v2 can be carried over a dedicated IP address when IPv6 is deployed.
Configuration with one OAM IPv6 address and one IPv4 telecom address is not supported.
IPv6 or 5620
SAM
IPv4 MME
IPv6
OAM VLAN
GigE S1 VLAN
X2 VLAN SGW
OAM VLAN
GigE S1 VLAN IPv6
X2 VLAN
eNodeB broadcasts
DHCP messages to
request an IP 5620
configuration SAM
1
NM sends config. 3
including IP
configuration
eNB
DHCP
Server
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. A parameter “ipConfigMode” defines if eNB OAM IP@ is
configured at Integration & Configuration, or dynamically learned with DHCP procedure.
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.
XXX VLAN
XXX VLAN
GigE
XXX VLAN
XXX VLAN
MME
S1 MME
DRB
SRB S1-U SGW
UE
Secured
Security Requirements :
Flat architecture:
z All radio access protocols terminate in one node: eNodeB
z IP protocols also visible in eNodeB
MME
Security E
Gateway M
M
(SEG) S1
S1 MME
SRB
DRB S1-U S1-U SGW
UE
Secured Secure Secure
IPSEC tunnel IPSEC tunnel
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.
eNB
eNB
Ethernet
eNB Backhaul Intranet
eNB SGW
eNB
Intranet
IPSec Tunnels
MME
eNB
eNB
Ethernet Intranet
eNB Backhaul
eNB SGW
eNB
The Security Gateway (SEG) is the central hub of communications between the eNodeB and other
LTE components (i.e. eNodeB, MME, SGW, MME/SGW from other operator in case of RAN sharing).
The diagram depicts the logical functionality of the SEG within the network. The physical SEG
component can be the same router that would normally aggregate traffic from the eNodeB’s, given
the router supports IPsec functionality. Most larger core routers that aggregate traffic should
support IPsec tunnels. The SEG will usually contain a robust IPsec feature set to allow compatibility
with a wide variety of vendors IPsec implementation.
MME
Ethernet
Backhaul Intranet
eNB
Ethernet
Backhaul Intranet
SGW
eNB
Telecom traffic NM
in IPSEC tunnel O&M
MME
network
OAM traffic
ePC
SGW
SEG
In the release LA5.0, the operator will be able to select digital certificates as a new method for IKEv2
authentication in addition to the existing pre-shared secret key method.
Digital certificate based authentication is adequate for large IPsec deployments like the LTE backhaul because it
is more scalable than pre-shared keys.
Without digital signatures, the operator must either manually exchange public keys or secrets between each
pair of systems that use IPsec to protect communications.
By using digital certificates, the operator can simply register each eNodeB system with a Certificate Authority
(provided by 9981CMS – Certificate Management server) and systems like the SEG needs no modification while
implementing digital certificates.
When a new eNodeB attempts an IPsec connection, IKEv2 automatically exchanges certificates with the peer
SEG and the eNodeB and SEG systems authenticate each other.
Note: The 7750 SR IPsec functionality is implemented in the MS-ISA module. The MS-ISA module is a hot
swappable component that can be inserted into an Input/Ouput Module-2 (IOM-2).
GigE
SEG
GigE SEG
Example
Telecom S1-U + X2-U
VLAN
S1-C + X2-C
GigE SEG
OAM OAM
VLAN
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 policy applied on userplane (S1-U and X2-U)
z One other applied on controlplane (S1-C and X2-C)
IPsec policies are used in the eNodeB for inbound and outbound traffic to determine if a flow should be sent
into the tunnel or not, and what kind of protection should be aplied . Once IPSEC is activated, IPSEC
policies are applied.
IKE rules and IPsec policies in both IPsec peers must match.
Change of IPsec configuration, like change of IPsec policy or the value of some attribute require an eNodeB
reboot.
As an example, following diagram illustrates the 3 possible IPSEC policies options in LA2.0 (outband direction
only).
IP packets are generated and then, based on the kind of traffic the inner IP address is applied (OAM or telecom
IP address).
The chosen IPSEC policy is then applied to the IP packet. Depending on the policy, the IP packet is not
modified (“bypass” policy) or is encapsultated into a new IP packet using the outer IP address.
The final IP packet is then sent on the egress VLAN.
OAM
OAM X2 S1-C OAM S1-C
S1-C
X2 S1-U X2
S1-U
S1-U
Outer Outer
IPSEC policies IPSEC policies
IP@ IPSEC policies IP@
SEG
1588v2
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.
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 can be performed using pre-shared secret keys (or digital
certificate provided by 9981CMS). These secret is provisioned in the eNodeB 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 supported on the 3 VLANS configuration (OAM, S1/X2 User plan and S1/X2 Control plan vlans).
Master Operator
OAM Ipsec Tunnel
Telecom Ipsec Tunnel
Backhaul Backhaul
IPSec Tunnel
IPSec Tunnel
In the eUtran shared architecture the eNodeB will only have one OAM network connection.
The OAM network connection will belong to the master operator. AN IPsec tunnel can be configured for the
OAM or Telecom traffic. Each of the telecom transport commuications will belong to their respective
operator (i.e S1-U, S1-C, X2-U). It is expected that each operator will have their own Security gateway and
LTE transport network components (i.e. MME, SGW). The X2-U traffic will only be transported on the
master operators IPsec communications since this is an eNodeB to eNodeB communications and owned by
the master operator. Each Operator can independently enable/disable IPsec tunnels.
Before After
No IPsec tunnel
Internet
Access (BE)
SGW PGW
Streaming
(GBR)
Transport QOS
Transport QOS
Diffserv Dimensionning
Diffserv Dimensionning
UE QOS
QOS Control
Control IP QOS
IP QOS toto L2
L2 mapping
mapping
UE
SIP/SDP Qos
SIP/SDP Qos signaling
signaling Traffic Management
Traffic Management
App/SDF/RBMapping
App/SDF/RBMapping MPLS
MPLS
UL Rate
UL Rate control
control (PBR
(PBR support)
support)
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.
SGW PGW
The end to end QOS functions are performed at four levels : UE , eNodeB , ePC and the transport network
levels.
The EPS 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.
The “Standardized QCI characteristics” defines packet delay and packet loss rate per QCI at access
side from UE to PCEF (Policy and Charging Enforcement Function, in the PDN GW). Jitter is not
addressed by this 3GPP standard.
The 3GPP assumption is that delay from eNodeB to PDN GW should be in average of 20 ms (with
min=10ms and max=50ms).
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:
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.
Tunnel header
L2 L3 L4
..TEid..
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.
Most QoS mechanisms include some type of classification but only a small number
of mechanisms also include marking capability.
Classification: used for identifying a Behavior Aggregate to which a packet
belongs.
Marking: used for coloring packets by applying a class-identifying Value to
one of the following markers: IP precedence, DSCP, QoS group …..
Traffic shaping: aims to control the rate at which packets are sent out of an
interface, while preventing packet loss.
Traffic policing: aims to control the amount of bandwidth consumed by an
individual microflow, or an aggregate of flows.
Queuing: Queues are created at the interface where congestion is expected.
Scheduling: Determines order in which queues (and then packets) are served.
SAM5620
Lower priority
flow
UE
OAM
VoIP GigE
(real time) SGW PGW
High
priority
flow
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 either
per Ethernet port orper VLAN.
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
EIR
CIR
Backhauling
bandwidth
Network
time
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.
per VLAN
EIR
CIR The eNB performs traffic
Telecom
VLAN shaping for all UL traffic
traffic for each VLAN with
EIR different values of CIR/EIR
OAM
VLAN 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.
“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
Allow the following bandwidth granularity:
100 Kbit/s steps up to 1 Mbit/s
1 Mbit/s step beyond 1 Mbit/s up to 10 Mbit/s
5 Mbit/s step beyond 10 Mbit/s up to 100 Mbit/s
10 Mbit/s step beyond 100 Mbit/s up to 1 Gbit/s
Support 3 modes of shaping per Bandwidth profile to be shaped:
CIR
CIR and EIR
No shaping
MME
2 Attacker
DOS Attack
PDN
SGW PGW
The DOS Attack protection feature is intended to enhance the Intrusion Detection System/Intrusion Protection
System (IDS/IPS) of the eNodeB to avoid Denial of Service (DOS).
It implements the following additional security functionalities in the eNodeB:
z Filtering of ingress packets to control the traffic entering the eNodeB.
z Counting the number of packets dropped by the packet filtering mechanism.
The eNodeB has a list of authorized IP addresses (from eNodeB, MME, SGW, OMC…). Based on this information,
the eNodeB authorizes or rejects each packet.
The eNodeB allow the user to configure Layer 3 filtering rules:
z IP packet filter on ingress traffic
z IP filtering can be done on an IP address or subnet level
z Packet filtering are stateless
z IPv4 and IPv6 are supported
z Compatible with IPsec and Non IPsec interfaces
When the packet filtering capability is activated, the Node will begin to inspect and discriminate traffic against a
well known list of acceptable traffic.
All ingress traffic that doesn’t match the known list of acceptable traffic will be discarded.
1 2 Transport CAC
Radio CAC
(T-CAC)
Number of Number of
PRB consumption
connected users established data Transport
(per Cell, per
(per Cell, per bearers (per Cell, bandwidth
PLMN per cell)
Trigger PLMN per cell) per PLMN per cell)
In LA5.0, enhanced eUTRAN sharing is introduced which enables the eNB to additionally perform admission
control on a per PLMN per cell basis when a cell is shared by multiple operators. Refer to Volume 5 for an
overview of eUTRAN sharing. Per PLMN admission criteria are checked when more than one PLMN is
broadcast in SIB1 in the cell. The resources which are checked per PLMN for admission control fall under the 3
Radio CAC criteria (number of connected users, number of established data bearers, and PRB consumption).
The data parameters used to configure PLMN admission control are associated with object RadioCacCellPerPlmn
and are described in the sub-sections corresponding to their respective criteria type. Parameter
RadioCacCellPerPlmn::plmnId identifies the instance of the PlmnIdentity object that defines MCC and MNC of the
concerned PLMN. See Volume 5 for additional discussion of PlmnIdentity.
Also in LA5.0, PRB licensing is introduced which allows the eNB to additionally perform admission control on a
per band basis across all cells of the eNB if parameter flag isUnlimitedPRBLicenseAllowed = false. Refer to
section 5.3 for an overview of PRB licensing.
If:
isReactiveLoadControlAllowed:: True
The choice of pre-emption action to be taken is based on the data parameter settings described subsequently in
this section. In the case of off-loading, Radio CAC will invoke eMCTA to off-load UEs.
A fallback to UE/bearer release may occur when off-loading may not be processed or fails.
Bearer candidates for reactive load control are selected if they meet the following criteria:
• It is not the only bearer of a UE;
• Its pre-emption vulnerability is pre-emptable, and its Priority Level is not 15;
• Its priority is lower than that of the bearer which triggered reactive load control;
• Its UE is not in an ongoing procedure, including release, handover, CCO and ANR procedure;
• Its UE is not a CSFB call;
• Its UE is not in coverage alarm (event A2 for Entering-Coverage-Alarm has been received);
• Its UE is not the same UE of the bearer which triggered reactive load control;
A UE is a candidate for off-loading if:
• Parameter isOffloadUponLoadControlAllowed is set to “True”
• It has a pre-emption candidate bearer configured and parameter
ReactiveLoadControlActionForBearerAdmission::action (in the instance
of TrafficRadioBearerConf with qCI=incoming bearer QCI) is set to “outgoingMobility”
• All the bearers belonging to the UE are pre-emptable.
• All the bearers belonging to the UE have a lower priority than that of the bearer which triggered reactive load
control.
eNB Call Admission Control (CAC) includes Radio CAC and Transport CAC (T-CAC).
When both T-CAC and Radio CAC are applicable, T-CAC is performed first.
T-CAC may apply in a per port or mode or in a per VLAN mode.
If eUTRAN sharing is activated it is only possible to configure the per VLAN mode.
In case eUTRAN sharing is activated, the number of VLAN and the number of PLMN managed by T-CAC
are the same. There is one VLAN handling S1-U per operator (i.e. per PLMN identified by
VLAN::plmnId). There is one T-CAC runing per VLAN (i.e. per operator).
T-CAC applies separately on uplink (egress) and downlink (ingress) direction.
At RAB set-up (or modify) T-CAC controls if the associated S1-U UL and DL volume of traffic can be
satisfied according to the remaining UL and DL bandwith of the transport link to the backhaul network.
The Call Admission Evolutions feature provides an evolution of the Admission Control from a token-based to a
measured-based solution. (Static CAC no longer used).
A transport link is;
either a physical link, that is an ethernet port, for which T-CAC applies on
the port aggregated traffic (even if some VLANs are defined),
or a VLAN, for which T-CAC applies on the VLAN aggregated traffic.
S1-AP E-RAB MODIFY REQUEST: QCI of eRAB is modified (1) Increased (2) or
Intra-eNB HO involving QCI change Decreased
(1) QCI online modification for existing data bearers is possible for QCI in range [6..9]. This is enabled
by setting ActivationService::isQciArpOnLineModificationAllowed to “true”.
(2) If the transport bandwith is not sufficient, the QoS of existing eRABs is maintained by rejecting
the new eRAB.
• T-CAC does not modify QoS characteristics of existing eRABs nor pre-empt ressources in case of
transport link bandwith exhaustion.
• T-CAC algorithm operates in an open loop mode. T-CAC does not get feedback from the user-plane
transport layer (i.e. WinPath) of UL and DL bandwidth consumption measurement.
• A mechanism is provided to accept some extra emergency eRABs in case of transport link bandwith
reaching exhaustion. Emergency calls correspond to calls set up with an ARP that equals to
PlmnIdentity::arpPriorityEmergency.
• It is based on provisioning a percentage of the transport link bandwidth that is reserved for
emergency calls.
4- From the list, please select the triggers radio CAC algorithms:
An eRAB is rejected if T-CAC fails in both directions (DL or UL). True/ False
An eRAB is accepted if T-CAC succeeds in one direction (DL or UL). True/ False
The master nodes usually have access to a Primary Reference Clock (PRC) traceable reference signal. PRC is a
high accuracy clock of which long-term frequency stability error should be below 1 part per 10 11 as per ITU-T
G.811.
At the receiver of the timing signal a PLL (phase-locked loop) controls the frequency or the phase of the local
oscillator according to the received reference timing signal. The function of PLL is to lock the local clock to the
incoming reference signal. Radio networks require always frequency stability.
Phase and time synchronization are additional requirements in some technologies as in LTE TDD and
LTE MBMS.
The purpose of synchronization is to make sure that equipments send and receive data at the same
rate and possibly also at the same time.
Accurate frequency synchronization is a crucial requirement on radio interface, for instance for
handovers.
Frequency synchronization requirements are expressed in parts-per notation. Parts-per notation is
the ratio between the observed frequency and the reference frequency ( i.e. = (measured frequency
/ reference frequency) – 1)) expressed in parts-per-million (ppm) or parts-per-billion (ppb).
The clock generator within eNodeB generates the bit, basic frame, hyper frame, CPRI-10ms frame
and BS super frame synchronization signals from a timing source input signals (such as local GPS,
syncE, IEEE1588v2…).
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 disturbs
the handover.
z In TDD, the time synchronization is also required for the radio frame synchronization.
F2 F2
F1 F1
Time Time
Sync Ethernet
clock master
Ethernet
Synchronous Ethernet
GPS
1588v2
server
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.
SyncE can only be used for frequency reference, so syncE can’t be used in TDD systems.
The eNodeB can run in free running for 72 hours for Frequency and 1 hour for phase (standard).
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 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.
eNB1 eNB2
UE1 Overlap
UE2
Overlap
UE1 TX eNB1 TX
time time
UE2 RX 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 near–far 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.
Ethernet
Sync Ethernet
clock master
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.
PTP client
T1
T1
T2,
local reception time
RTT = ((T2-T1)+(T4-T3)):2
mean delay = RTT/2
DL delay = T2-T1
UL delay = T4-T3
T3 Delay reques
t
T4
Delay response – T4
PTP is a Timing over Packet Protocol (ToP). The root timing reference is called the grandmaster.
Two PTP transport modes exist : PTP protocol over UDP or PTP protocol directly over Ethernet. UDP mode is
used.
The PTP server can distribute synchronization information using multicat mode (all client receive the multicast
timing messages) or in unicast mode (each client gets its own targeted timing messages). The eNodeB only
support unicast mode.
The network between the master and the slave introduces packet delay, packet delay variation (PDV) and
packet loss.
Several timestamps are used to compute network these delays :
T1: server sends Sync message.
The grandmaster conveys to the slave the timestamp t1 by Embedding the timestamp t1 in the Sync
message. This requires some sort of hardware processing for highest accuracy and precision (one-step
clock), or by embedding the timestamp t1 in a Follow_Up message (two-step clock). (message not shown
on the diagram).
T2: client receives server’s sync message.
T3: client sends Delay request to server. This is optional for frequency synchronization
T4: server receives it and responses Delay response with t4
At the conclusion of this exchange of messages, the slave possesses all four timestamps.
RTT = ((T2-T1)+(T4-T3)):2
mean delay = RTT/2
DL delay = T2-T1
UL delay = T4-T3
The client deduces drift of its clock compared to the server reference .
PTP client
PTP server
grandmaster
Several messages
are used to Request unicast
negociate PTP transmission
exchanges rate.
ansmission
Grant unicast tr
erval, Duration)
(logmessage int
Sync logmessage
interval
Sync Duration
Sync
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, that’s 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 possible general solution for frequency and phase synchronization
solutions :
y GPS
y 1588v2 PTP
y SyncE
List the available solution(s) for frequency and phase synchronization on TDD
system :
y GPS
y 1588v2 PTP
y SyncE
IPsec consists of several protocols to administer the secure tunnel and perform the encryption of user traffic.
IPsec suite of protocols contains three main protocols, Internet Key Exchange (IKE), Authentication Header
(AH), and Encapsulating Security Payload (ESP).
The administrative portion of IPsec is either performed manually or dynamically. The dynamic method of tunnel
negotiation is performed by the IKE protocol. There are two flavors of IKE (IKEv1 and IKEv2) that may be
supported on a SEG. In case of the eNodeB, IKEv2 is the only supported IKE mechanism. For the
remainder of the IPsec discussion, we will only refer to IKEv2.
IKE is the protocol used to set up a SA in the IPsec protocol suite. IKE builds upon the Internet Security
Association and Key Management Protocol (ISAKMP) and uses a Diffie-Hellman Key exchange to set up a shared
session secret, from which crytographic keys are derived.
Public key techniques, certificates, alternatively, a pre-shared key, are used to mutually authenticate the
communicating parties.
The ISAKMP SA should not be confused with the IPsec SA. The ISAKMP SA is meant to secure (encrypt) the
remaining phase 1 and phase 2 negotiations.
.
The original IP packet source and destination address will be referred to as the
Inner Tunnel Address. The new IP headers source and destination IP addresses will
be referred to as the Outer Tunnel Address.
Encrypted
Original Header Originial
New IP Header New IP IP Data
IP Data ESP
Tunnel Mode Header AH
Header
Header Header
Transport mode will reformat the original IP packet by inserting an IPsec header to form a new Ipsec packet for
transmission. The Ipsec header is inserted between the IP header and the payload. The original header remains
unaltered. Tunnel mode will reformat the original IP packet by inserting a new IP header and an Ipsec header in
front of the original IP packet. The Ipsec header is either the AH or ESP format.
SEG
Traffic Selector
Unprotected
Subnet
Protect eNB Inner Subnet
SEG
Traffic Selector
eNodeB
eNodeB
without IPsec
The IP security feature is activated to protect the various traffic types in an eNodeB. If the IP security
feature is not activated, peer entities in the core network or the OAM network reaches the eNodeB through
a Security Gateway (SEG) or router without any protection.
After the IP Security feature is activated, the peer entities reach the eNodeB through the SEG or router
based on some policies. Enabling IP Security feature allows to protect all or a part of the traffic to the
eNodeB.
Protecting the eNodeB traffic is achieved in the IP Security feature by defining a new eNodeB inner subnet.
After activating the IPsec feature, the protected traffic
• can be part of a private eNodeB subnet or the eNodeB inner subnet
• can be the telecom and OAM traffic between eNB and SEG (one VLAN used for OAM and telecom traffic)
• can be the independent OAM traffic or telecom traffic, if two VLANs are used
After IPsec feature activation, a new eNodeB inner subnet is defined for the traffic flow concerned by this
activation. The eNodeB IP address defined in this inner subnet is not routable and this can be a private
address if IPv4 is used.
Note: The customer should purchase a software license offered by Alcatel-Lucent to enable the IPsec
feature. Software licenses are offered on a per eNodeB basis.
1 HDR, SA1,KE,N
IKE_SA_INIT
Message 1:
The initiator sends the IKE Header with possible supported SAs (Crytographic algorithms), KE – Diffe-Hellman
Value, and nonce value.
Message 2: The responder sends the IKE Header with the SA selected from one of the possible Sas provided by
the Initiator from message 1.
Included as well is the responders KE – Diffe-Hellman Value, nonce and optionally the Certificate Request.
Dashed Line: At this stage of the negotiation, the two participants have exchange Diffe-Hellman Values and they
can derive shared secret
keys. From this point on, all information after the IKE Header will be encrypted and provides Integrity Protection.
Message 3: The Initiator sends the IKE Header, Identification, Certificate response if there was a request in
message 2, optional certificate request, optional ID of
responder, Authentication – could contain the pre-shared keys or digital certificate verification. SA and traffic
selectors for traffic flow.
Message 4: The responder sends the IKE Header with an ID, Certificate response if a certificate request was
present in message 3.
Authentication – could contain the pre-shared keys or digital certificate verification. SA and traffic selectors for
traffic flow. Peer Authentication has been
validated after this stage
After the second message, the IKE encryption key is calculated and used to encrypt the remaining
message transfers between the initiator and responder. The Key calculation is dependant on the
negotiated method of authentication. T
The IKE Encryption Key, Authentication and Derivation key are valid for all future communications,
unless otherwise renegotiated in the Phase 2 stage.
Auth: Authentication
HDR, SA, N, [KE], CERT: Certificate
[3GPP TS i, TS] CERTREQ: Certificate Request
5 HDR: IKE Header
Idi: Identification - Initiator
Initiator HDR, SA, N, [KE], Responder Idr: Identification –
[3GPP TS i, TSr] Responder
KE: Key Exchange
6 N: Nonce
SA: Security Association
TS: Traffic Selector
[]: optional parameter
IKE phase 2 negotiation creates the IPsec SA that will determine if any subsequent packet will be
encrypted prior to transmission or reception of pack Dashed Line:All traffic remains encrypted as a result of the
phase 1 negotiation.
Message 5: The Initiator sends the IKE Header, SA offers, a new nonce value different from the phase 1
transmission, optional KE if you want to create a new calculated key, and optional Traffic selection offers.
Message 6: The responder sends the IKE Header with a selected SA from message 5, a new nonce value
different from the phase 1 transmission, optional KE if you
want to create a new calculated key, and optional traffic selector chosen from the offers provided in message 5.
Note: [KE] Diffie-Hellman keys are exchanged if Perfect Forwarding Secrecy is selected.
Note: A Child SA is a unidirectional connection. Therefore a connection to an end point will require a TX and RX
SA for a bidirectional IPsec tunnel.
The phase 2 will be repeated for additional SAs setup.
IKE negotiation is completed at the end of the Phase 2 negotiation. The Agreed upon SA for each direction will
be entered into the Initiator’s and responder’s local SA database. The agreed upon traffic selectors will be
entered into the Initiator’s and responder’s local security policy database.
The agreed upon SA will contain:
• Encryption Algorithms to protect data
• Hash algorithms to reduce data for signing ets.
An authentication method for signing data
• Information about a group over which to do a Diffie-Hellman exchange.
• A pseudo-random function (PRF) to hash certain values during the key exchange.
• Type of protection to use - either ESP or AH.
Stage 1: Out going IP traffic are examined on a packet basis and compared to the Security Policy Database
(SPD) for a corresponding valid entry. If a valid entry is found, the specified action in the SPD is followed. If the
specified action is IPsec, the corresponding SAD lookup is performed to determine the IPsec specifics for
encryption.
Depending on the rules validation the transmitted packet can have several possibilities. The packet can be
dropped, transmitted without IPsec encryption or IPsec encryption is enforced. If the Ipsec encryption is
required, an SADB lookup is performed to retrieve the corresponding SA.
X2-AP
2
ort 3642 IP@2
ocia ti on on p
SCTP ass
A transport address is unique to an SCTP endpoint and is defined by the combination of an IP address and an
SCTP port number (case of single-homed SCTP endpoint) or by the combination of multiple IP addresses and an
SCTP port number (case of multi-homed SCTP endpoint).
The sctpAssocHeartbeatInterval defines the delay between successive Heartbeats transmitted by the SCTP
entity over an association when no Data is transmitted. With the HB Acknowledgement it acts both as a
‘keep-alive’ and as a link–failure detector.
Several remote IP addresses are provisioned in the eNodeB and the peer
advertises its SCTP IP addresses at association setup.
When the eNodeB detects too much retransmissions on the failed path, it
uses another remote IP@ as peer address.
S1-MME
The eNodeB selects one of the multihomed MME or eNB peer IP addresses as ‘Primary’ in this node.
The eNodeB should always transmit to the primary peer address unless specifically commanded to use an
alternative due to
fault conditions.
The sctpAccessPathMaxRetrans parameter defines, in the multi-homed environment, the maximum number
of retransmissions on each path that should be attempted for a Data chunk for which an acknowledgment
has not been received.
Peer SCTP
eNodeB endpoint
Up To MAX
InitRetransmits
Similarly during Initialisation, if the eNodeB receives the INIT-ACK and sends COOKIE, it starts the T1-
cookie timer. If the timer expires the eNodeB resends the COOKIE message a maximum number of times
set also by the parameter “[Link]”.
If the COOKIE-ACK is not forthcoming on the last re-send the eNodeB raises alarm “SCTP ASSOCIATION
FAILURE”.
The eNodeB after it sends INIT message sets the T1-init timer. If the timer expires before an INIT-ACK is
received from the peer, the eNodeB resends the INIT message a maximum number of times set by the
parameter “[Link]”.
If the INIT-ACK is not forthcoming on the last re-send the eNodeB raises alarm “SCTP ASSOCIATION
FAILURE”.
The eNodeB requests the SCTP protocol retry to initialize the association a repeated number of times as
defined by ALU proprietary parameter “sctpAssocEstablishmentMaxRetries”.
The value 255 defines ‘infinite’ number of [Link] during Initialisation, if the eNodeB receives the
INIT-ACK and sends COOKIE, it starts the T1-cookie timer. If the timer expires the eNodeB resends the
COOKIE message a maximum number of times set also by the parameter “[Link]”.
If the COOKIE-ACK is not forthcoming on the last re-send the eNodeB raises alarm “SCTP ASSOCIATION
FAILURE”.
INIT
Start T1-Init timer
Cookie Echo
t + δt State Cookie sent back Start T1-cookie timer
ERROR
If (δt > [Link]) Cause:Stale cookie Error
Data to IP@1
Start T3- rtx
RTO Data and/or SACK Primary path
T3- rtx expiry X (IP@1)
Error_path1=+1
Heartbeat to IP@1
Start HB Timer
HB Timer Heartbeat ACK
HB Timer expiry X
error_path1 >
X Error_path1=+1
Switch to secondary path
sctpAccessPathMaxRetrans
Data to IP@2 Secondary path
Start T3- rtx
T3- rtx expiry RTO Data and/or SACK (IP@2)
X
Error_path2=+1
error_assoc>
sctpAccessPathMaxRetrans X Alarm-SCTP association down
The eNodeB monitors the SCTP associations for failure based on Heartbeat ACK’s and Data ACK’s
monitoring. Data Chunks are retransmitted based on the RTO Retransmission Timer within the SCTP
stack. If the RTO expires before a Data Chunk is acknowledged then the Data Chunk will be
retransmitted.
The only action performed on path failure is the switching of the primary path by the SCTP stack.
No indication is sent to OAM when this occurs.
SCTP also maintains a counter for the total number of retransmissions to the peer over all paths (if
peer is multi-homed). When the counter exceeds the [Link] to the peer the
eNodeB considers the peer unreachable, stops transmitting and raises alarm “SCTP ASSOCIATION
DOWN”.
The eNodeB requests the SCTP protocol retry to initialize the association a repeated number of
times as defined by ALU proprietary parameter “sctpAssocEstablishmentMaxRetries”.
MME
SCTP data
SACK
timer
SCTP data ACK
RTO timer
SCTP data retransm
expiracy ission
Retransmissions
occur till Max
retransmit value SCTP data retransm
is reached issi on
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.
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.
Section 1
eUTRAN Technical Overview
Module 3
LTE eNodeB Hardware description
TMO18213_V7.0-SG-LR13.3L-Ed1 Module 1.3 Edition 1
LTE RAN
LR13.3L 9400 LTE RAN Technical Overview
TMO18213_V7.0-SG Edition 1
Document History
1·3·4
This page is left blank intentionally
COPYRIGHT © ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.
eUTRAN Technical Overview · LTE eNodeB Hardware description
LTE RAN · LR13.3L 9400 LTE RAN Technical Overview
Page
SLg CBC
SBc
S1-MME S6a
HSS
9412 eNodeB M3
MME
S11
X2 S1
SLs
SeGW PCRF
IP network
S1
E-SMLC Sm
MBMS
LTE 9764 MCO S1 M1 -GW BM-SC
or 9763 MCI Gx
S1-Ui
SGW S5/S8 PGW SGi PDN
CPRI
BBU
9768 MRO 9926 d2U eNodeB
Small Cells
: User plane
: Control plane
Alcatel-Lucent offers LTE metro cells for both indoor and outdoor usage.
The 9763 Metro Cell Indoor is for use in indoors spaces. Supporting up to 64 users, these metro cells may be placed
in any indoor spaces, such as in malls, conference halls, subway stations, etc. They can also be used to
coverage heavily populated indoor events, such as conventions.
The 9764 Metro Cell Outdoor is great for covering dense urban hotspots. Its directional antenna can direct
coverage directly to the hotspot, focusing capacity where it is needed. Since an optional Wi-Fi APs may also be
included, the operator may utilize their current Wi-Fi sites also for LTE coverage as this one device allows one
site to be used for 2 technologies. Supporting up to 64 users (for 2x1watts), these metro cells can also be used
to provide additional coverage and capacity for outdoor events, such as concerts, horse races, etc. as well as
coverage holes in the macro network. With directional antennas the 9764 MCO can also be used to provide in-
building coverage from outdoor sites.
The 9764 MCO 2 x 5 supported up to 200 users and is ideal for large public venues and for macro extension. It is
also great for covering larger rural areas and villages.
The 9768 Metro Radios can provide massive capacity, with exact capacity dependant on the eNodeB. These are
what have been referred to as the Stadium metro cells and indeed MROs are great for providing additional
capacity to large sports stadiums as well as other large public venues, such as event centers. The 2x 5W MRO is
powerful enough to cover floors of high rise buildings from an outdoor site.
Antenna
CPRI
eNode B brain and link to the network
S1 and X2 interface to ePC and other eNode Bs
Base Band Unit through Gigabit Ethernet port
Processing capabilities
Send/Receive signal to/from radio through CPRI
link
S1 & X2
TRDU
OR
(Base Band Unit)
BBU (Transmit Receive Duplex)
MRO
(Metro Radio Outdoor)
AA
(Active Antenna)
Frame
Alarms
α β γ
x2 x2 x2
TRDU TRDU TRDU
Or Or Or
RRH RRH RRH
Or Or Or
MC-TRX x2 MC-TRX x2 MC-TRX x2
Or Or Or
MC-TRDU MC-TRDU MC-TRDU
CPRI CPRI CPRI
The RF part is ensured by either TRDU or RRHs or MC-TRX or MC-TRDU only (no mixture is allowed within the
same eNodeB Band. (In case of dualband eNB , 2 bCEM card are used. 1 bCEM card per Band).
The 2x2 MIMO is the normal base station transmit scheme for all eNodeB variants.
However, other transmit schemes are supported since LA4.0 Release, thus to serve in-building systems, and to
provide service where two transmit paths per sector are too costly or infeasible. These transmit schemes are:
• Single Antenna Transmit Scheme
• Low Power eNodeB DAS Support Configuration
3- Antennas 6- Antennas
3- Sectors 6- Sectors
3-Cells 6-Cells
Radio Module
the correct modules names
…………………
…………………
…………………
…………………
GPS
………….
……….
……….
……….
Backhaul
………………
BBU
(Base Band Unit)
DC- PS
…………………………. User
Alarms
SFP SFP
GigE
Fiber Optic Cable
CPRI Links
to 7705 SAR
(Up to 9 units)
The 9926 BBU can be installed in a standalone indoor mode or in an existing indoor or outdoor Alcatel-Lucent
Base Station cabinet for Multi-Standard configuration.
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.
The 9926 BBU has been specifically designed for coverage within
constrained Environments. It can be installed in:
bCEM modems can be equally used for FDD and TDD deployments. The same module (as shipped from the
factory) can therefore be inserted into an FDD eNode or into a TDD eNodeB. However, in LR13.3.L release, once
configured in one mode (FDD or TDD) the bCEM cannot be configured in another mode. Attention must
therefore be paid to management of bCEMs in mixed FDD/TDD network environment.
In LR13.3.L release, there are two different releases for FDD and TDD concerning the cards eCEM-U and eCCM2.
2 variants for eCCM-U and 2 variants for eCCM2 and no compatibility between them.
The d2Uv5 shelf offers a d2U sub-rack (with a RBP) and +24V High Capacity Fan Tray (RUC) or a -48V High
Capacity Fan Tray (RUC).
The RBP (Rack Back Plane) supports all internal links between CCM and CEM modules. It allows the signaling
interconnections between the CCM and the CEM modules inserted within the digital shelf. The backplane board
also gives a power supply to the CCM and CEM modules.
Rack Back Plane (RBP) supports all internal links between the eCCM and bCEM modules. The d2Uv5 backplane
features a flexible slot that can act as a controller slot or a modem slot. Hence, it can support either one
controller plus three modems or two controllers plus two modems in a programmable fashion.
Fan Tray
-48VDC RUC +24VDC RUC
Front View Front View
As previously said, the 9926 BBU can operate either in -48VDC or +24VDC.
The nominal DC voltage ranges are:
• –40,5 VDC to -57 VDC
• +20 VDC to +28.8 VDC
Within these nominal voltage ranges, the BBU operates at full performance.
The BBU will not suffer any irreversible damage when powered within an abnormal voltage within the range -0
VDC to -40.5 VDC.
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.
● Number of sectors
● Backhaul physical interface (Gigabit Ethernet, or Fast Ethernet)
● CPRI Rate
● Power supply (-48VDC or +24VDC)
CCM
Band#1
Carrier#1 RRH
Band#1
Band#1 RRH
Carrier#1 Band#2
Band#2
Carrier#2 RRH
Band#1 Band#1
Carrier#1 Band#1 RRH
RRH Band#2
Carrier#2 Band#1
RRH
Band#2 Band#2
Carrier#2
Band#1 eCCM2
Carrier#1 RRH
Band#1 RRH
Band#1
Band#1 RRH
RRH
Carrier#1 Band#2
Band#2
Band#2 RRH
RRH
Band#1 Carrier#2 Band#3
Band#1
Carrier#1 Band#1
Carrier#2
RRH
Band#2 Band#1 RRH
Carrier#2 Band#1
RRH
Band#2
RRH
Band#3 Band#2
Carrier#3 RRH
Band#3 RRH
Band#3 Band#3
Carrier#3
Band#3
Carrier#3
BBU tri carrier configuration with 3xbCEM is supported from LR13.3.L Release with the use of eCCM2
controller board. Up to 9 sectors or 3 Carriers 3 sectors.
• 1 x BBU shelf
• 1 x eCCM
• 3 x bCEM modem board (each bCEM handles 3 sectors)
• 1 x Fan Tray on the right side, including fans and power entry module
The Tri carrier feature enables operators to co-locate different carriers on different LTE bands within a single
eNB, when spectrum available in one band is not sufficient or redundancy is achieved by covering an area with
more than 1 carrier. Anyway this feature will take into account the configurations implying independent
carriers/bandwidths.
there can be 3 carrier frequencies in 3 bands, or there can be 3 carriers on 2 bands (Dual-Band using a single
carrier on 1 band and Dual-Carrier on the other band).
Aggregation of two or more carriers for obtaining an increased bandwidth is treated by Carrier Aggregation
feature. In the LR13.3L release Carrier aggregation is supported between two carriers in two different bands.
Carrier aggregation is implemented on the bCEM, therefore it requires a dedicated bCEM for each sector. Thus
any three sectors BBU with carrier aggregation will require three bCEMs.
• The eCCM-U MB together with the GE MDA constitutes the eCCM-U GE module.
Not Used
In LTE
GE MDA
for links
6 SFP cages ules
To radio mod
The face plate of the eCCM-U provides the following connectors and LEDs:
• 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 format connectors for connectivity to the radio modules (RRH, TRDU); each SFP connector
is equipped with two light indicators;
they support 6 CPRI links or 3 CPRI + 3 HSSL 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,
• One double RJ45 connector used for debug (RS232) and Ethernet (NEM); each connector is equipped with
two LEDs (a yellow one showing Ethernet activity status and a green one for Ethernet link status),
Note: RJ45 Debug interfaces must not be used during normal operation of the BBU. (Risk of unstable behavior,
crash, …)
The face plate of the GE MDA provides:
• One RJ45 connector for GE electrical backhaul
• Two SFP connectors for GE optical backhaul
Due to the GE MDA hardware design, a total of two connectors (i.e. 2 optical or 1 optical + 1 electrical) can be
used at a given time on the GE MDA.
In case of optical link, only the SFP-2 port is enabled.
Only one single GE Interface is supported for the backhaul. In case of optical
link, only the SFP-2 port is enabled.
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.
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/EIA-568
standards.
Fast Ethernet on the embedded RJ45 port can also be used, but not recommended.
Note: The Backhaul function in eCCM2 is integrated in the main board using WP3: 2 SFP + 2 10/100/1000bT
RJ45.
Optical
Use Wavelenght Functionnalities
Mode
Multi
Short
Mode 850 nm
Distance
Dual Fiber
Single
Long
Mode 1310 nm
Distance
Dual Fiber
The Network Engineer must then take care of the distance between the BBU and the ODF (Ethernet Backhaul
connection point). For both optical modes, LC-LC fiber cables of 15m length are defined for ordering.
Depending on customer optical link choice (Multi mode or Single mode), the SFP cages of the eCCM-U board will
be equipped with corresponding optical SFP transceivers.
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.
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).
BBU
eCCM-U
Or eCCM2 RRH RRH RRH
board
Frame (Option) ● ● ● ● ● ●
1.
Distribution
Optical
2.
3.
4.
CPRI
R2CT weatherized
5. connector
.
.
. LC-LC connectors
9.
CPRI (Common Public Radio Interface) connections are based on V4.0 and V4.1 CPRI standard. CPRI standard
plans to cover UMTS + LTE mixity and CDMA + LTE mixity.
BBU to RRH connections are optical connections whereas BBU to TRDU connections can also be electrical based.
eCCM-U board
The usage of the GPS-RF input port is the recommended Alcatel-Lucent solution, but the usage of the PPS input
port can still be used if the operator has already an external GPS receiver with PPS interface.
eCCM2
eCCM1 RF GPS cable SMB_F-N_F
board
board
Optional Secondary Protection N_F-N_M
The PPS input port can still be used if the operator has already an existing TMU (i.e external GPS receiver) with
PPS interface.
The TMU_RXD_P/N pins can be configured as either input-only for RS422 full duplex or as bidirectional
signals for RS485 half duplex for the RET interface (AISG-compliant) via software control. The termination
is software switchable. The software can then switch out the termination when the Rx pins are used for
transmit (RS-485) or when a termination exists outside the board in a daisy-chained configuration.
The GPS PPS_P/N pins can be configured as either inputs or outputs via software control. The termination
is software switchable. The software can then switch out the termination when these pins are used for
transmit or when a termination exists outside the board in a daisy-chained configuration.
The eCCM2 (model 2)/eCCM2-HR (High Rate) supports 9 CPRI ports that accept SFP/SFP+ optical transceivers
(or cables with SFP connectors). Supported CPRI rates for the eCCM2 are from Rate 2 to Rate 5 (for FDD). The
eCCM2-HR (TDD only) supports Rates 3, 5, and 7. Two green LEDs indicate CPRI link TX and RX status.
The eCCM2/eCCM2-HR supports backhaul Ethernet support using two SFP ports and two RJ-45 ports. The
eCCM2/eCCM2-HR can enable all four ports simultaneously.
The face plate of the bCEM provides triple port RJ45 connector for debug, labelled “Test BBU”, “Test SW” and
“Test ICE”.
Debug ports “Test SW” and “Test ICE” provide a 10/100/1000 Base-T Ethernet interface, and “Test BBU” debug
port provide including an RS232 UART line and Synchronisation.
The bCEM 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 provides three debug ports that should not be used during normal eNodeB operation.
Two different HW version of bCEM exists: bCEM 1.0 (used for TDD version only) and bCEM 1.1 (common
for TDD and FDD BBU versions).
FDD version supports up to two bCEM (one modem for 3 sectors per frequency band).
TDD version supports one bCEM P1.0 or bCEM P1.1 (2 antennas) to three bCEM P1.0 or bCEM P1.1 (for 8
antennas configuration).
The bCEM modem has the ability to be configured for all 3 cells on the eNodeB.
By doing so it allows the eNodeB to have fewer units within its framework. Having fewer units in the eNodeB frees
up existing space for future use, such as redundant modem or redundant controller and allowance for 6 sector
support by using 2 bCEMs.
Note: In release LR13.3L the eCEM board is not supported.
Connected to RUC
Ext. port alarm
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.
The eNodeB collects alarm information using the eAM and the internal one-wire interface. All user alarms and
internal alarm connections, such as the door-intrusion and fan- alarm signals, must use the eAM.
The eNodeB collects frame alarms directly with no external module needed. The remaining d2Uv3 frame alarms
are unassigned. TRDUs will convey all alarm information via the CPRI interfaces to the controller in the BBU.
CDMA_ BTS
3G-1X CDM
MCR-1+
eNB BBU Channel
Tx AMP
& Filer
Card
eCCM-U Channel
• CPRI Card MCR-2+
GPS Tx AMP
10/15Mhz Ref • CPRI & Filer
Backhaul(Gig E) R-OCM
Alarm
• CPRI
MCR-3+
CDMA Tx AMP
eCEM-U eCEM-U eCEM-U & Filer
α β γ Controller
The R-OCM takes baseband signals from the d2u BBU and inserts them onto the backplane of the CDMA base
station in a manner similar to a CDMA modem unit.
The R-OCM appears to the BBU to be three individual RRHs that are connected to three of the BBU’s CPRI ports.
The R-OCM arrangement supports 2Tx/2Rx (refer to table 3) . The RF power is dependent on the CDMA
equipment.
The Reverse-OCM (R-OCM) is the connection between the LTE BBU and the
OneBTS Digital Shelf.
It converts the optical CPRI from the BBU and connects to the OneBTS backplane
to facilitate use of OneBTS RF assets.
The CDMA RF resources are shared between the eNodeB and the CDMA BTS.
Optical CPRI
Connection
Reverse OCM
circuit pack
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.
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
No bCEM support on R-OCM configurations. R-OCM configurations are only supported with eCEM boards.
RET
The maximum AISG cable length depends on the
following parameters:
Output Power supply on AISG connector (pin 6)
AISG
of the RFM (or TMA) Cable
AISG topology (Star, daisy chaining, …) RF
Number of RCUs connected
RCU (RET) power consumptions (standby and
with motor rotating)
Conductor size of AISG cable (typically pin 6)
RRH_1
Note: all RRHs and TRDUs support the AISG feature. But No AISG
on MC-TRX.
AISG protocol uses a 3-layered model comprising a physical layer, a data link layer and an application layer.
RETAs don’t allow AISG daisy chaining.
Each RFM drives the RETA to which it is associated.
RETAs don’t allow AISG daisy chaining. RETAs allow AISG daisy chaining.
Each RFM drives the RETA to which it is All RETAs are driven from the same
associated. RFM (RRH_1 in our case)
The AISG cables have approximately
the same length as the RF feeders.
RET
RET RET
RET RET
RET
1:3 Splitter
AISG
RF RF RF Cable
RRH_1 RRH_2 RRH_3
Note: As most of the new RETs offer the daisy chaining possibility, the AISG splitter is less used.
TMA and Smart Bias-T are installed closed to the RF equipment (≤1m)
RETAs allow AISG daisy chaining.
All RETAs are driven from the same RFM (RRH-1)
ANT-1 ANT-2 ANT-3
AISG
Cable RF RF RF
Smar
t
BIAS
Tee
● At RFM site, a Smart BIAS Tee is used to convey the AISG signal over the RF feeder. The Smart BIAS Tee is
Installed on the Main TX path.
● TMA supports AISG (in our case). AISG signal is detected on the RF and retrieved on the AISG connector.
RFM embeds an internal Smart Bias-T RFM embeds an internal Smart Bias-T
The RRH2x40-26 and TRDU2x60-26 include At antenna site, the TMA retrieves the AISG
a smart bias-T. signal from the RF feeder, on the Main TX path.
ANT
ANT
RET
RET
AISG
Smart Bias-T Cable
TMA
RF
RF
Internal Smart Bias-T
RRH/TRDU RRH/TRDU
MDA
SFP SFP
………..
CPRI Links
(Up to 9 units)
2- Fill in the gaps the interfaces and connectors names of eCCM2 module:
………………..
……..
……………….. ……………….. …………
……………….. ………………..
………………..
……………….. ………………..
………………..
a) CPRI
b) AISG
c) Ethernet
d) HSSL
The TRDU (Transmit Receive Duplex Unit) has two RF transmitters, two receivers
(LNA), and double duplex filter, packaged in a single shelf-mounted module.
TRDUs are not supported for TDD.
Optical
fiber
The TRDU will be located in Compact eNodeB, either in indoor cabinet, or in outdoor cabinet.
The TRDU supports 2-way MIMO. Two TRDU modules can be combined to support 4 x 4 MIMO, or 2-way MIMO
with 4 receive branch.
Taking the case of 2 x 40W TRDU, the nominal transmit power is 2 x 45 Watts at the duplexer ports. This is to
support 40W at the external antenna connectors (EAC), accounting for up to 0.5dB of loss in the jumper cable
between the TRDU and top of cabinet.
The principle is the same for the 2 x 60W TRDU.
The TRDU supports CPRI Rates 2 to 4 (and is hardware ready to support CPRI Rate 1).
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”.
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.
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TMO18213_V7.0-SG-LR13.3L-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 48
3 TRDU Macro modules FDD
3.1 TRDU Description [cont.] Only
The following table lists the different TRDU available for LA6.0 release,
with their related frequency band and output RF power.
Output PS PS
TRDU Naming Frequency Band
RF power (+24VDC) (-48VDC)
Band XIII
TRDU2x40-07U 2 x 40W √ √
(700 MHz Upper)
Band XIV
TRDU2x40-07PS 2 x 40W √
(700 MHz)
EDD Band
TRDU2x40-08L 2 x 40W √
(800 MHz Lower)
Band XII, XVII (700 MHz
TRDU2x60-07L 2 x 60W √
Low)
EDD Band
TRDU2x40-08U 2 x 40W √
(800 MHz Upper)
Band VII
TRDU2x60-26 2 x 60W √
(2600 MHz)
TRDU2x60-AWS Band IV (AWS) 2 x 60W √
Band III
MC-TRDU2x60-18 2x60W √
(1800 MHz)
Rack Mount
TRDU 9412 ID 9412 OD MBI5 MBO2 LRID LROD
ID
TRDU2x40-07U √ √ √
TRDU2x40-07PS √ √
TRDU2x40-08L √(*) √ √
TRDU2x40-08U √(*) √ √
TRDU2x60-07L √
TRDU2x60-26 √(*) √ √
TRDU2x60-AWS √ √ √ √
√ √
MC-TDRU2x60-18
The TRDU will be located in Compact eNodeB, either in indoor cabinet, or in outdoor cabinet.
Indoor Cabinets
6U mounting frame
for 19" equipment
d2U
Battery
MBO1 MBO2
Starting from LA6.0 release, the new LightRadioTM cabinets will be introduced.
Two cabinets (outdoor and indoor) are available: the “Small” and the “Compact”
LA6.0 will introduce the Outdoor versions, with limited configurations:
Configuration #1: Small / DC / Digital (2x LTE BBU + 1x W-CDMA BBU + 1x SUMX GSM)
Configuration #2: Small / DC / Digital (2x LTE BBU + 1x W-CDMA BBU)
Configuration #3: Compact + Small / AC / 2x LTE BBU + 3 Band RF (700L, 700U, AWS)
Configuration #4A: Small + Small / AC / Digital (2x LTE BBU + 1x W-CDMA BBU) / 2x90Ah batteries
Configuration #4B: Small / AC / Digital (2x LTE BBU) / 1x 90Ah battery
1- Please Link the TRDU to eCCM, using the correct connectors and name
the interfaces
……………
……………
……………
……………
The RRH can be on the same site where the BBU is located, or on a remote site.
In both cases, these two equipments are linked by optical fibers supporting CPRI interface, carrying LTE
downlink and uplink (main and diversity) base band digital signals along with OAM information.
Each RRH is equipped with two CPRI interfaces.
The RRH also include :
• Its own energy system
• Its own cooling system
• AISG interface (allowing remote control and monitoring capabilities of the antennas)
On physical characteristic aspects, the RRH is a zero footprint solution, very light, which doesn’t require any
craning for installation.
With a reduced power consumption and noise-free solution (no fan used), the RRH doesn’t require any
maintenance.
Functions
Self contained radio part of distributed solution
Radio Transceiver
Power amplifier
Low Noise Amplifier
Filter front end (Duplexer)
Power system (-48V)
Power consumption ~ 320W
40% amplifier efficiency, 2x 40W EAC Tx + 2x Rx (exc AISG, RET, TTLNA)
Field installable & swappable Optical Transceiver/Fiber options
Multimode to support of to 500m
Single Mode to support up to 20km
Single and dual fiber variants
19W
44W
7/8" feeders
30m ≈ 2dB 0,3dB
Jumpers
TMA 0,4 dB
Jumpers
0,5 dB
33W ☺ Jumpers
0,8 dB
no more RF losses /(5m)
66% more power @ antenna !
40W
Optical fiber
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.
RF Antennas
RDEM Module
RRH with RDEM –Top Connection
All unused connectors shall be closed by a protection cap to prevent any contact and humidity entry. (Protection
caps are provided with the RRH at delivery time)
All unused RF connectors shall be protected with a metal cap.
4-Way Rx Diversity
Supported by use of optional RDEM (Rx Diversity Expansion Module)
Low installation weight
Weight below 13.5kg, using removable solar shield and heat-sink
Wide temperature range
-40 deg C to +50 with 1120W/mk of solar load
-40 deg C to +55 with no solar load.
TMA and RET support with AISG 2.0
The following table lists the different RRH available for LR13.3L release, with their
related frequency band, output RF power, and RDEM option.
The following table lists the different RRH available for TLA6.0 releases,
with their related frequency band and output RF power.
Note: The new TLA6.0 feature allows to converge several physical cells into one logical cell under a single cellId
with multiple RRH connections. Up to 4 RRH 2x20w can be connected to one logical cell.
This feature increases the cell coverage while avoiding the problem of frequent handover (HO) occurrences.
TDD
Only
Star configuration: The star configuration is used when the RRHs are being mounted far from each other, but
nearly equally spaced from the Base Band Unit.
Daisy chain configuration: The daisy chain configuration is used when the RRHs are being mounted close
together but far from the Base Band Unit
Note: Excepted for the RRH4x40-19 which is build of two boxes (daisy chain between the two boxes), the “CPRI
Daisy Chain” feature between two RRHs is not supported in LTE FDD LR13.3L. Therefore only star configuration
between BBU and RRHs is allowed.
Only in TDD: Daisy chain configuration is supported with up to 4 chained TD – RRH in 2.3Ghz. This feature
supports the product RRH2x50-2350.
Calibration Port
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.
Note that the cabling delay does not include the BBU
and/or RFM processing delays
Delay 2
RRH
Delay 3
d2U
Delay 1
The maximum delay (11ns) between TX Main path and TX Diversity paths is not without impacts on the fibers
length (CPRI), as well as on the RF jumpers and feeders.
CPRI fiber cable length to RRH shall be as much as possible the same for all RRHs. However, a maximum of 2m
difference is acceptable between two CPRI fibers serving the same sector. (This fulfillment is mandatory to be in
the 11ns maximum delay acceptable between TX Main and TX Diversity paths of a RF
sector).
Feeder Delay
DAS
Feeder DAS Fiber Remote Unit
CPRI Link (Fiber) RRH (Coaxial Cable) DAS
d2U Optical DAS
Host DAS Fiber Remote Unit
CPRI Delay
Antenna Path Delay
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 fine 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 prefix, 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
3- what does the red cable in the picture below used for?
Sector α
???
TD-RRH1
CPRI CPRI CPRI CPRI
3G
Only the 1800 MHz MC-TRX is available for
LTE.
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.
Receiver Connector
Transmitter Connector
CPRI
The MC-TRX (Multi-carrier transceiver) is used to support LTE + GSM on single RF path.
The connection between MC-TRX and BBU is ensured by CPRI links, and the connection between MC-TRX and
GSM SUM-X is ensured by Ethernet links.
Up to 6 MC-TRXs can be connected to the BBU in a star configuration.
The MC-TRX is connected to an Antenna Network (AN) before interfacing the antenna. The AN playing the
Duplexer role.
Rule: Not more than 2 MC-TRX can be connected per AN.
Note: For LTE MIMO 2x2, 2 x MC-TRX per sector are used.
GSM LTE
1x16 1X40 1X16 + 1X35 / 1X10 + 1X40
1X16 1X30
2X16 1X20 2X16 +1X15 / 2X12 + 1X20
1X33 1X20
2X10 1X30 2X10 + 1X22/ 2X6 + 1X30
α β γ
AN AN AN
GSM SUM-X
Backhaul
9768 MRO
(Distributed BBU)
CPRI
IP Network
9926 BBU or BBU cluster
7750 SGW
USE CASES indoor hotspots Outdoor Hotspots, Macro extension, Large High rise
Indoor hotspots from Large public public buildings
outdoors, venues, venues, from
Coverage Hole-fill Rural areas. outdoors
The 9763 Metro Cell Indoor is for use in indoors spaces. Supporting up to 64 users, these metro cells may be
placed in any indoor spaces, such as in malls, conference halls, subway stations, etc. They can also be used
to coverage heavily populated indoor events, such as conventions.
The 9764 Metro Cell Outdoor is great for covering dense urban hotspots. Its directional antenna can direct
coverage directly to the hotspot, focusing capacity where it is needed.
Since an optional Wi-Fi APs may also be included, the operator may utilize their current Wi-Fi sites also for LTE
coverage as this one device allows one site to be used for 2 technologies. Supporting up to 64 users (for
2x1watts), these metro cells can also be used to provide additional coverage and capacity for outdoor events,
such as concerts, horse races, etc. as well as coverage holes in the macro network.
With directional antennas the 9764 MCO can also be used to provide in-building coverage from outdoor sites.
The 9764 MCO 2 x 5 supported up to 200 users and is ideal for large public venues and for macro extension.
It is also great for covering larger rural areas and villages.
The 9768 Metro Radios can provide massive capacity, with exact capacity dependant on the eNodeB. These
are what have been referred to as the Stadium metro cells and indeed MROs are great for providing
additional capacity to large sports stadiums as well as other large public venues, such as event centers. The
2x 5W MRO is powerful enough to cover floors of high rise buildings from an outdoor site.
Note: See appendix A. 9764 Metro dock is a mechanical support for 9764MCO module. The
Metro Dock has been designed so that different types of 9764MCO module could be
plugged on it.
Following feature or capacity purchase (Purchase Order) for a specific number of eNB or cell optional features or
capacity resources, licenses are created for each feature or capacity unit with the ALU Licensing tool (also called
LKDI). The Licenses are available through an encrypted file, protected by a digital signature.
The license (file) is installed into SAM using an application called RAN License Manager (also referred to as RAN-
LM in this document). This license file creates at SAM a pool of Tokens (RTUs) that are available for all eNBs
managed by SAM.
The operator can then distribute the pool of available optional feature or capacity tokens among all eNB(s) via
specific OAM parameters (also called Licensing Parameters).
These Licensing parameters are checked for each licensed resource by SAM (RAN-LM) anytime a change is made
so that the global license capacity provided by the License file is not exceeded Lixcense file (RTUs) ≥∑(Licensing
parameters)
If the above mentioned SAM check fails for one of the licensed resources, the configuration of that specific
optional feature or capacity element is blocked, the configuration work-order is rejected, and no changes
covered by that work order will be activated for any eNB. No activations of the optional feature or capacity
element will be allowed until the number of available tokens exceeds the number of activations.
The following eNB capacity elements are managed by Capacity Licensing:
• Transmission Power (per cell)
• Number of Active users per eNB
• Allocated Operating Bandwidth (per cell)
S1 MME
DRB
SRB S1-U
UE
SGW
With carrier bandwidth: 5Mhz
Number of Active user per Sector-carrier: 400 users
Number of Connected Users per Sector-carrier: 800 users
With carrier bandwidth: 10Mhz
Number of Active user per Sector-carrier: 250 users
Number of Connected Users per Sector-carrier: 625 users
Note: FDD eNodeB equipped with eCCM2 and bCEM boards.
1 · 3 · 80 COPYRIGHT © ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.
eUTRAN Technical Overview · LTE eNodeB Hardware description
LTE RAN · LR13.3L 9400 LTE RAN Technical Overview
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 supported, 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.
Note:
In case of TDD eNodeB equipped with eCCM2 and bCEM:
For 10 and 20 Mhz:
Number of active and connected users per sector-carrier: 200 users
Software Download
Software Activation (eNodeB reboot)
Software Accept
eNB Software Upgrade Outages should also be less than 2 mn 30 seconds, from the SW Activation of the new
load and parameters in the NM server (SW download and installation already done in background) till the eNB
is ready to accept calls (S1 & X2 are up, The SIB are transmitted, the first cell is ready to accept calls …)
eNB Software upgrade success ratio: 99,9%
The Warm-up time for outdoor systems at the minimum storage temperature to reach operational
temperature shall be at most 60 mn (System Cold Start) .
For indoor systems and outdoor systems already at operating temperature when not powered, start time shall
be no more than 10 minutes.
99% of software trap and firmware failures shall be automatically recoverable. Recovery is defined as
returning to a state wherein the software is able to serve the designed traffic objective. It can range from an
automatic reset to an eNB reboot. Manual recovery shall also be supported in case operator intervention
becomes necessary or is preferred by the service provider.
CPRI ports
PRI & SEC
VSWR (voltage standing wave ratio) measures the size of signal reflections of transmission lines between
transmitters or receivers and antennas.
TRDU daisy chaining not supported.
RX connectors
TX connector
On/off switch
CPRI ports
PRI & SEC
Top View
Power supply
Links to BBU (optic fiber)
Alarms
Bottom View
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..
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..
BBU
Fan Tray
Power
Distribution
Panel
3 TRDU2X
(3 cells)
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.
In addition, there is also a cabinet called Compact Indoor Rack-mount shelf, designed for easy integration in 19”
or 23” standard racks.
Power
Distribution
Panel
TRDUs
BBU
Power
Distribution
Panel
Fan Tray
Fan Tray
A Baseband Cabinet version in -48 VDC with Dual BBU also exists.
Two variants of cabinets are possible : +24VDC variant, and +48VDC variant.
The Baseband and RF cabinets can be mounted a floor-stand mount, on a wall or a pole.
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
FDD
only
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).
lightRadio Small lightRadio Compact 9712 lightRadio Outdoor cabinet (small configuration)
indoor cabinet indoor cabinet
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.
Section 1
eUTRAN Technical Overview
Module 4
LTE eUTRAN OAM Overview
TMO18213_V7.0-SG-LR13.3L-Ed1 Module 1.4 Edition 1
LTE RAN
LR13.3L 9400 LTE RAN Technical Overview
TMO18213_V7.0-SG Edition 1
Document History
1·4·4
This page is left blank intentionally
COPYRIGHT © ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.
eUTRAN Technical Overview · LTE eUTRAN OAM Overview
LTE RAN · LR13.3L 9400 LTE RAN Technical Overview
Server + Database
Primary Standby
Distributed
Collocated
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.
The 5620 SAM 11.0 R5 is used to manage the eUTRAN NE’s LR13.3L.
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
Network Element
View
eNodeB Logical
View
Pre-provision manager
creates an eNodeB
template 1
5620 SAM
Pre-Provisionned
eNodeB and pre-provisioned NE NE
match during eNodeB
discovery
3
Activation WO
Manager
Configuration data is
pushed to the 2
template
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
set administrative state to enable
This allows the user to control which steps are performed automatically, and which steps require manual
intervention from the user.
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 a set of nodes to which SW will be downloaded
z schedule for later or immediate execution
z immediate activation after download
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
Offline Online
configuration configuration
5620 SAM
1 · 4 · 13 COPYRIGHT © ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.
eUTRAN Technical Overview · LTE eUTRAN OAM Overview
LTE RAN · LR13.3L 9400 LTE RAN 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
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:
network or service objects from which to collect statistics
counters to collect
the rate of collection
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.
Aalrm management
in 5620 SAM
Alarm
Windows
5620 SAM provides states and statuses repotting for the underlying Managed Objects of the eNodeB:
z Administrative (configurable): Operational,
z AvailabilityStatus : gives info on Communication status (read-only field) and Managed state (declared in
GUI but not connected).
z Connection State : Offline, Not Connected, Online
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
ll t
rac
e
2 eNodeB sends call trace
messages to Aux server
CT Aux Server
Wireless Trace Analyzer
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.
Initial snapshot
Work-order export import and
for activation resynchronization
Main NM server
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 engineering of a new network.
z Data engineering for network expansion, additional density.
z Data engineering for network optimization.
z Data engineering for upgrade provisioning.
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).
WPS
snapshot WO
snapshot WO
5620 SAM
Local repository Operator
On demand snapshot creation
or scheduled export 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.
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
MME
Ca
Call traces ll
t ra
activation ce
request
Call trace
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 NPO offers a full range of multi-standard QoS Monitoring and radio network
optimization facilities, including:
9959 MS-NPO
QoS analysis
GSM WCDMA LTE
QoS decrease cause diagnosis
Cartographic telecom
management
Performance
Reporting Geographical analysis
Hardware inventory
management QoS Alerter & Warning
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
The NPO client represents a PC machine running on Windows XP Professional SP2 or Windows Vista operating
[Link] 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 Ina 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 search facilities help the operator to perform selections
z Theoperator 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.
animated slide
Focus on
FCA & CD Based on
only (raw + last 60
rate)
values
1 line Highlight
per MME based on
Threshold
MME 1
One or FCA%
more
charts CDR%
: last 10 mn
Chart
area can
MME 2 be hidden
One or
more MME MME 3
per chart
FCA%
CDR%
: last 40 mn
Zoom
(Nice to have
Step 2)
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.
The SON features can be used for self-configuration or self-optimization purpose. These are the SON features
implemented in the Alcatel-Lucent LTE Network Solution:
z X2 Dynamic Configuration
z eNB Self Configuration
z Automatic Neighbor Relation (ANR) configuration and optimization
z Automatic Configuration of Physical Cell Identity (PCI)
z Mobility Robustness Optimization
z Capacity and Coverage Optimization
Plug-N-Play (PnP) is meant for initial deployment for eNB with automatic establishment of IPsec OA&M
Connection only. Plug-N-Play capabilitites are not available for Telecom connections.
The IPsec Plug-N-Play feature allows the eNB to automatically establish an OA&M IPsec channel without
extraneous configurations. Currently the eNB will require the user to configure the IPsec outer and Inner tunnel
addresses before communications to the SAM can be established.
With PNP, the Outer IPsec Tunnel address can be automatically acquired by enabling the Automatic Security
Gateway Discovery capability. The IPsec PNP will enable the automatic discovery of the IPsec Inner Tunnel
address and complete the IPsec tunnel configuration.
1. When the eNB is first deployed in the field, the eNB will first boot and perform a DHCP request for an outer
IPsec tunnel address, SAM IP addresses and SeGW address. The edge device will allocate the IP addresses.
2a. The eNB will initiate an IPsec tunnel connection with the SeGW. The eNB will use the factory certificates as
part of the IKEv2 authentication procedure in order to avoid additional manual provisioning.
2b. The eNB will request the Inner IPsec address via the IKEv2 negotiation (to the Core DHCP server via SeGW).
The eNodeB complete Ipsec negociation with the SeGW and the OAM tunnel is established.
3/4/5. The OAM IP sec tunnel is established between eNodeB and SeGW. The eNodeB initiates contact with
5620SAM. The SAM that is responsible for managing the eNB will reply and complete the eNB registration. Then
the Sam can load the work order to complete the provisioning of the eNB.
6. After the eNB is configured, the eNB will have to reboot in order to substantiate the new MIM parameters.
The eNB will perform its normal start up with a completely populated MIM.
It is expected that the Factory certificates were only used for the initial OA&M connection. Future connection to
the OA&M will be via the operators CMS domain.
7. The eNB will be configured with new operator CMS parameters. A new SeGW can be configured that is
different from the SeGW that established the connection for the bootup IPsec tunnel.
Nota: Optional DNS (1 or 2)can be used if Fully Qualified Domain Names (FQDN) are used instead of IP
addresses.
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TMO18213_V7.0-SG-LR13.3L-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 31
5 Self Optimization Process
5.3 Intra-Freq and Inter-Freq LTE ANR
eNode request UE measurement and UE
sends info on PCI to eNodeB 1
5620 SAM
X2 Check operator preferences
before NRT table
3 update
MME
5
Served Cell information sent eNodeB retrieves neighbor IP address for dynamic X2
over X2 interface configuration, MME acts as relay 4
Automatic Neighbor Relation (ANR) is a capability that enables the eNodeB to create and maintain its
neighbor lists automatically. Features in previous releases provided ANR for intra-frequency LTE neighbors
and for UTRAN FDD neighbors. The LA6.0 feature (L103176) introduces commercial delivery of ANR
capability for LTE inter-frequency FDD and TDD neighbors. It does not support inter-frequency ANR for a
frequency with a different frame structure than the serving frequency.
The eNB is able to autonomously generate and manage its own intra-frequency and inter-frequency
neighbor relation tables (NRTs) by requesting UE to report neighbors identifiers (PCI, CGI) and/or by
sharing infos with another eNB through an X2 connection. The operator can keep full control (in particular
White and Black lists are supported) from the 5620 SAM. Note that the feature requests the ability to setup
S1-AP connections between eNB and ePC to retrieve the IP@ of the neighboring eNB, when x2 connection
is requested.
As a component of Self Organizing Network functionality this feature benefits the operator by reducing the
planning & deployment-related CAPEX (when ANR is played at new site integration), but also OPEX as it will
work as an autonomated Planning Optimization tool on a daily operational basis. Network rollout and
upgrade, plus Time to Market are shortened.
5620 SAM – eNB synchronization ensures that data is consistent between 5620 SAM and eNB. It is triggered
by 5620 SAM after the eNB notifies what is changed on eNB configuration regarding SON configuration to
the 5620 SAM server via a specific event reporting mechanism, at anytime.
The event reporting mechanism is used by eNB only if eNB configuration has been updated by one of the
features ‘IRAT ANR’, ‘intra-LTE ANR’, or ‘PCI Allocation, Conflict Detection and Correction’.
5620 SAM
NodeB
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.
UE reports measurement
PCI algo but Source eNodeB is
confused with provided
PCI PCI algo
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
5620 SAM
Expiracy
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 COPYRIGHT © ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.
eUTRAN Technical Overview · LTE eUTRAN OAM Overview
LTE RAN · LR13.3L 9400 LTE RAN Technical Overview
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 [Link] 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.
CM FM PM
Ssh, sftp 5620 SAM
CT
PCMD
CM FM PM
Ssh, sftp 5620 SAM
CT
PCMD
Hint: use the interfaces names provided to complete the blue boxes.
Congratulations
You have finished the training
[Link]@[Link]
Please include the training reference in your email (see cover page)
Thank you!