85962275-Alcatel-LTE RAN LA2.0 Technical

9400 LTE RAN LA2.0 Technical Overview - Page 1

All Rights Reserved © Alcatel-Lucent 2010


9400 LTE RAN LA2.0 Technical Overview

STUDENT GUIDE

TMO18213 D0 SG DEN Issue 6

All rights reserved © Alcatel-Lucent 2010Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent





2

Empty page

Switch to notes view!

This page is left blank intentionally





3

Terms of Use and Legal Notices

Switch to notes view!1. Safety Warning

Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to

wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the

equipment alone.

The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.

2. Trade Marks

Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.

All other trademarks, service marks and logos (“Marks”) are the property of their respective holders, including Alcatel-

Lucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning

the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.

Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to

change without notice.

3. Copyright

This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No

other use or transmission of all or any part of this document is permitted without Alcatel-Lucent’s written permission, and

must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may

be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from

Alcatel-Lucent.

Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly

prohibited.

User obtains no rights in the information or in any product, process, technology or trademark which it includes or

describes, and is expressly prohibited from modifying the information or creating derivative works without the express

written consent of Alcatel-Lucent.

All rights reserved © Alcatel-Lucent @@YEAR

4. Disclaimer

In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including

lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not Alcatel-

Lucent has been advised of the possibility of such damages.

Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an

endorsement, nor a recommendation.

This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The

information contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some

cases, due to contractual limitations, certain compromises have been made and therefore some features are not entirely

accurate.

Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment

and its operation, or contact your nearest Alcatel-Lucent representative for more information.

The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. Alcatel-

Lucent disclaims any warranties in connection with the products as used and described in the courses or the related

documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties,

including warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of

dealing, usage or trade practice.

Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed

internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in

nature

5. Governing Law

The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are

governed by the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal

Notices, or the application thereof to any person or circumstances, is held invalid for any reason, unenforceable including,

but not limited to, the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a

valid, enforceable provision that matches, as closely as possible, the original provision, and the other provisions of these

Terms of Use and Legal Notices shall remain in full force and effect.





4

Blank Page







5

Course Outline

About This CourseCourse outline

Technical support

Course objectives

1. Topic/Section is Positioned HereXxx

Xxx

Xxx

2. Topic/Section is Positioned Here






1. eUTRAN Overview

1 eUTRAN Architecture

2 eNode B Functions

4 Protocol Stack

4 Air Interface Basics

5 LTE spectrum deployment strategy

2. LTE Transport Network

1 eNodeB Requirements

2 Traffic aggregation

3 VLAN

4 IPSec

5 QOS

6 META

7 Synchronization

3. LTE eNodeB Hardware Description

1 eNodeB description

2 9926 BBU

3 Compact EnodeB with TRDU2X

4 Distributed eNodeB with RRH2x

4. LTE RAN OAM Solution Description

1 XMS Introduction

2 Fault Management

3 Configuration Management

4 Interfaces

5 Performance Management

6 Self Optimization Process





6

Course Outline [cont.]







7

Course Objectives


Welcome to 9400 LTE RAN LA2.0 Technical Overview

Upon completion of this course, participants will be able to describe the:

- Functions and the architecture of a LTE Access network

- LTE IP transport layer in the Radio Access Network

- Portfolio of the Alcatel-Lucent LTE Radio equipment

- LTE e-Node B operation and maintenance principles.





8

Course Objectives [cont.]







9

About this Student Guide

� Switch to notes view!Conventions used in this guide

Where you can get further information

If you want further information you can refer to the following:

� Technical Practices for the specific product

� Technical support page on the Alcatel website: http://www.alcatel-lucent.com

Note

Provides you with additional information about the topic being discussed.

Although this information is not required knowledge, you might find it useful

or interesting.

Technical Reference (1) 24.348.98 – Points you to the exact section of Alcatel-Lucent Technical

Practices where you can find more information on the topic being discussed.

WarningAlerts you to instances where non-compliance could result in equipment

damage or personal injury.





10

About this Student Guide [cont.]

� Switch to notes view!


Section 1 � Pager 1


Do not delete this graphic elements in here:

1All Rights Reserved © Alcatel-Lucent 2010

Section 1LTE eUTRAN Overview







1 � 2

Blank Page


First editionBoiteux, Nicolas2010-09-1201

RemarksAuthorDateEdition

Document History





1 � 3

Module Objectives

Upon completion of this module, you should be able to:

� Describe the eUTRAN architecture

� List NEs and their function

� Describe interfaces names

� Describe the protocol stack for User plane and Control Plane





1 � 4

Module Objectives [cont.]






1 � 5

Table of Contents

Switch to notes view! Page

1 eUTRAN Architecture 71.1 LTE Network Architecture 81.2 LTE RAN Architecture 91.3 Architecture Comparison 10

2 eNode B Functions 112.1 eNode B Functions 122.1 eNode B Functions [cont] 132.3 LTE vs UMTS Functions 15

3 Protocol Stack 163.1 eUTRAN Bearer 173.2 Global of the radio interface 183.3 S1-U interface supported 193.4 S1-MME interface supported 20

4 Air Interface Basics 214.1 Introduction 224.2 OFDMA 234.3 MIMO 244.4 eNodeB Handover 25

5 LTE spectrum deployment strategy 275.1 LTE TDD and FDD bands defined by 3GPP 285.2 LTE frequency bands 29





1 � 6

Table of Contents [cont.]







1 � 7






1 � 8


1.1 LTE Network Architecture

� All IP

eUTRAN

User and control

Control only

eNodeB

PGWSGW

ePC

HSS

PDN

PCRF

MME

The eUTRAN (for evolved UMTS Terrestrial Radio Access Network) is the LTE Radio Access Network defined by the

3GPP R8. It is made of the eNodeB. They are connected to the ePC to provide connectivity to the UE.

ENodeB can handle several cells to provide a LTE coverage to the LTE UEs.

MME (Mobility Management Entity) provides mobility and session control management and authenticates UEs.

The 7750 SR - SGW routes and forwards user packets, and acts as the mobility anchor for the user plane for LTE

handovers and inter-RAT handovers

The 7750 SR - PGW provides UE session connectivity to external packet data networks. The UE may have more

than one session active with a PGW for accessing multiple PDNs. The PGW also acts as the anchor point for non-

3GPP networks (e.g., CDMA 1X/EVDO, or UMTS).

PCRF supports service data flow detection, policy enforcement, and flow-based charging.





1 � 9


1.2 LTE RAN Architecture

�eUTRAN

MME

X2

SGW

X2

X2

S1-MME

E-UTRAN

EPC

S1-U

S1-MME S1-U

S1-MME

S1-U

The interface between eNodeB and the ePC is called the S1 interface. It is made of:

- S1-U interface between eNodeB and SGW. It carries the user plane (internet traffic, VoIP, …)

- S1-MME interface between the eNodeB and the MME. It carries the signaling between the UE and the ePC (ex

Authentication messages)

In addition to the S1 interface, there is the X2 interface between the eNodeB. It carries user and control plane

and it is used to manage the handover.

All these interfaces are based on IP.





1 � 10


1.3 Architecture Comparison

eNode B

Node BBTS

data plane

control plane

data plane

control plane

SGSN

PDSN

RNC

BSCGGSN

HA

MME S/P GW

PGWSGW

In LTE, compared to existing 2G or 3G technologies, there is one network element less for the user plan between

the UE and the external network. When a 2G/3G UE sends a packet in UL, it passes through 4 Network Element

before reaching the PDN. In LTE like there is not equivalent to the BSC/RNC, there are only 3 network

elements. That means lower latency.





1 � 11

2 eNode B Functions





1 � 12

2 eNode B Functions

2.1 Introduction

�For each connected UE, the eNodeBmaintains:

� SRB for the signaling

� Radio Bearer (RB) for the user traffic. The RB is mapped on the S1 bearer (GTP tunnel) on the S1-U interface.

eNodeB

MME

P-GWUE

S-GW

RB S1 Bearer S5 Bearer

SRB

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 RB, 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 RB and SRB depending on the

amount of data, the QoS and the radio conditions.





1 � 13

2 eNode B Functions

2.2 eNodeB Functions [cont]

Logical Nodes

Control Plane Entities

Radio Protocol layers

Ref 3GPP TS 36.300eNodeB

PDCP

PHY

MME

S-GW

MAC

RLC

E-UTRAN EPC

RRC

MobilityAnchoring

EPS Bearer Control

Idle State MobilityHandling

NAS Security

P-GW

UE IP addressallocation

Packet Filtering

Dynamic Resource Allocation

(Scheduler)

RB Control

RRC Connection

Admission control

Measurement Configuration

S1

eNodeBFunctions

eNB Functions:

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 radio bearers.

It handles the RRC 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.





1 � 14

2 eNode B Functions

2.2 MME Functions [cont]

Logical Nodes

Control Plane Entities

Radio Protocol layers

Ref 3GPP TS 36.300eNB

RB Control

Connection Mobility Cont.

eNB MeasurementConfiguration & Provision

Dynamic Resource Allocation (Scheduler)

PDCP

PHY

MME

S-GW

S1MAC

Inter Cell RRM

Radio Admission Control

RLC

E-UTRAN EPC

RRC

Mobility Anchoring

EPS Bearer Control

Idle State Mobility Handling

NAS Security

P-GW

UE IP address allocation

Packet Filtering

MME Functions

NAS (Non Access Stratum) signaling;

NAS signaling security;

NAS Security control;

Inter CN node signaling for mobility between 3GPP access networks;

Idle mode UE Reachability (including control and execution of paging retransmission);

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;

Support for ETWS message transmission





1 � 15

2 eNode B Functions

2.3 LTE vs UMTS Functions

Radio intelligence moving to eNodeB

1 2 4

Node B

SGSN

Backhaul (TDM/ATM)

Backhaul transition

to IP/Ethernet

Backhaul (IP/Ethernet)

MCS voice and SGSN packet mobility

evolves into the SGW

SGSN control evolves into the MME

Service and mobile aware all-IP network

MME

eNodeB

WCDMAWCDMA

LTELTE

Core Network

SGW

RNC

RNC bearer mobility evolves to the SGW

3

RNC control distributed

into the MME/eNB

1. The Radio intelligence is moving to eNodeB, like the nodeB. But as there is no RNC, the eNodeB is more

independent (for the Handover management for example)

2. Backhaul transition to IP/Ethernet, the LTE is natively based on IP. Note that if the 3G network carry traffic

over IP, they can share the same transport network.

3. The RNC functions are split between the MME, the eNodeB and the SGW.

� RNC bearer mobility evolves to the SGW.

� RNC control distributed into the MME/eNB.

4. The SGSN functions are split between the MME and the SGSN.

� MCS voice and SGSN packet mobility evolves into the SGW.

� SGSN control evolves into the MME





1 � 16

3 Protocol Stack





1 � 17

3 Protocol Stack

3.1 Global of the radio interface

PDCP

Physical Layer

MAC Layer

RLC

RRC

NAS

Control PlaneUser Plane

PDCP

Physical Layer

MAC Layer

RLC

RRC

NAS

Control PlaneUser Plane

Transport Channel

Logical Channel

Radio Bearer

Physical Channel

Non Access StratumSignaling between Core Network and UE

Radio Signaling

The user plane, IP packets, is treated by the radio protocols to send it over the air interface. By this treatment,

the radio bearer is mapped on the logical channel, the transport channel and finally the physical channel. The

structure of the air interface with the channel is covered in the LTE Radio Principles training.

The PDCP protocol is in charge of the ciphering.

The RLC is in charge of the segmentation of the RLC SDU (IP Packets) and the retransmission (ARQ).

The scheduler and H-ARQ processes are running in the MAC layer (only in the eNodeB).

The signaling is managed by the RRC protocol. There is a distinction between the radio signaling (RRC) and the

NAS signaling between the UE and the MME.





1 � 18

3 Protocol Stack

3.2 S1-U interface supported

� User Plane (eNB - S-GW)

Phy (L1)

MAC

RLC

PDCP

IP (user)

TCP, UDP, ICMP

User Apps

Phy (L1)

MAC

RLC

PDCP

IP (user)

GTP - U

UDP

IP (path)

Phy

GTP - U

UDP

IP (path)

Phy

IP (user)

UE

eNodeB SGW

LTE Uu S1 - U

Uu L2

S1 -U Transport

When the UE send in UL an IP packet, it is treated by the LTE radio protocol before being transmitted over the air

interface. After the reception, the eNodeB send this data on the GTP tunnel (S1 bearer) to the SGW.





1 � 19

3 Protocol Stack

3.3 S1-MME interface supported

� Control plane (eNB – MME)

Phy (L1)

MAC

RLC

PDCP

RRC

NAS

User Apps

Phy (L1)

MAC

RLC

PDCP

S1 - AP-

SCTP

IP

Phy

S1 - AP

SCTP

IP

Phy

NAS

UE

eNodeBMME

LTE Uu S1 - U

Uu L2

S1 -MME Control

RRC

The NAS signaling is encapsulated by the RRC protocol over the air interface. But it is then transmitted to the

MME with the S1-AP protocol and not to the SGW.





1 � 20






1 � 21


4.1 Introduction

OFDMA MIMO Flat IP

Robust modulation in dense

environmentsOFDMA (DL) / SC-FDMA (UL) Increased spectral efficiency. Simplified Rx design cheaper UE Scalable - go beyond 5 MHz

limitation

Increased link capacity

Multiple-input, multiple-output UL& DL.

Collaborative MIMO (UL). Overcome multi-path

interference

Flat, scalableShort TTI: 1 ms (2 ms for HSPA). Backhaul based on IP / MPLS transport. Fits

with IMS, VoIP, SIP

1.4MHz 3MHz 20MHz10MHz5MHz

LTE bandwidths options

The LTE air interface key features are:

- The OFDMA (Orthogonal Frequency Division Multiple Access)

- The MIMO which is a multiple antennas techniques to improve the air interface performance

- The Flat IP, in every Network element including UE and eNodeB, the layer 3 is the IP layer.

In addition the bandwidth assigned to each cell is between the 1.4 MHz and 20 MHz. That provides more

flexibility in the spectrum allocation and re-farming. The bandwidth has a direct impact on the cell capacity.





1 � 22


4.2 OFDMA

� In TDMA, the UE are separated by the time.

� Example: GSM

� In FDMA, the UE are separated by the frequency

� Several users can receive data on the same time but not on the same frequencies.

� The OFDMA, for Orthogonal FDMA, allows a high density of sub-carrier, and so boost the performance

5, 10 or 20 MHz

15kHz Sub-Carrier

User 1 User 2 User 3

TDMA = Time Division Multiple Access.

The Sub-Carrier can carry only one symbol at each time. The number of Sub-Carrier depends on the bandwidth.

The scheduler allocated dynamically groups of sub-carrier to the UEs.





1 � 23


4.3 MIMO

DL

freq

time

� MIMO is a multiple antenna technique to boost the performance

� 2 antennas on the enodeB side

� 2 antennas on the UE side

� It transmits 2 streams in parallel when the radio condition are enough good.

Transmissions from each antenna must be uniquely identifiable so that each receiver can determine what combination of transmissions has been received.

The UE needs to know the spatial signature of each transmission path

� This identification is usually done with pilot signals, which use orthogonal patterns for each antenna.





1 � 24

4 Flat IP and Mobility Management

4.4 eNodeB Handover

� The Handover:

� The radio link is released from the eNodeB 1 and re-established on the eNodeB 2

� The Control plane is switched to the eNodeB 2 and the MME

� The User plane is switched to the eNodeB 2 and the S-GW

eNodeB 1

MME

Serving GW

eNodeB 2

x2

S1-MME

S1-U

S11

User data

The Handover is based on preliminary radio measurements on serving and neighbour cells

Handover procedures are controlled by UE and the eNB

eNB coordinates active mode handovers using the X2 interface

� Data is forwarded from Original eNB to Target eNB during handover

� eNB signals to MME (Path Switch Request) via the S1-MME interface for handover

� MME signals to the S-GW (User Plane Update Request) via the S-11 interface to switch the downlink bearer

tunnel to the target eNB





1 � 25

4 Flat IP and Mobility Management

4.4 eNodeB Handover

� The number of X2 interface maintains by an eNodeB depends on the neighborhood.

� Typically an eNodeB is tri-sectorized, i.e 3 cells.

eNB with 3 cells - 6 X2s

eNB with 3 cells - 6 X2s

eNB

eNB

eNB

eNB

eNB

eNB

eNB

eNB

eNB

eNB

eNB

eNB

The number of X2 interfaces depends on the topology of the network. They are declared in the eNodeB (max 32).

If the X2 interface is not available between 2 eNodeB, the handover can be S1 based.





1 � 26






1 � 27


5.1 FDD and TDD

� TDD = Time Division Duplex

� The Uplink and the downlink transmissions are separated by the time.

� Only one bandwidth is used.

� Example: WiMAX

frequency DLtime

UL DL UL

� FDD = Frequency Division Duplex

� The Uplink and the downlink transmissions are separated by the frequency.

� 2 bandwidths are used.

� Example: WCDMA, CDMA2000

frequency

DL

UL DL timeUL

frequency





1 � 28


5.1 FDD and TDD [cont.]

� The LA (LTE Access) release is the FDD solution

� The TLA (TDD LTE Access) release is the TDD solution

LTE-FDD TD-LTE

One standard 3GPP TS 36.xxx (set of LTE specs)

One access Scheme OFDMA for DL and SC-FDMA for UL

One Core Network ePC

Channel BW 1.4MHz, 3MHz, 5MHz, 10MHz, 15MHz, 20MHz

Sub-frame duration 1 ms

Frame duration 10ms 5ms, 10ms

Ratio (DL:UL) 1:1

5ms (1:3), (2:2), (3:1)

10 ms (6:3), (7:2), (8:1), (3:5)

One technology, One standard – 2 access options





1 � 29


5.2 LTE TDD and FDD bands defined by 3GPP

� This table illustrates the LTE TDD and FDD bands defined by 3GPP

The 3GPP is able to use all the frequency above. But all these bands will be not availabe for LTE in each country.





1 � 30


5.2 LTE frequency bands

� The first frequency bands usable by the operators are the DD bands and the 2.6 GHz bands.

� It will also possible to reuse 2G, 3G or CDMA bands for LTE (refarming)

700 MHzUS DDFDD

800 MHzEurope DDFDD

1GHz 2GHz

2.6 GHzNew band for LTE onlyFDD and TDD

2.3 GHzTDD

DD means Digital Dividend, it refers to the frequency band frees by the end of the analogical TV.





1 � 31

End of ModuleLTE eUTRAN Overview





Section 2LTE Transport

9400 LTE RAN LA2.0 Technical Overview TMO18213 D0 SG DEN Issue 6





2 � 2

Blank Page


First editionLast name, first nameYYYY-MM-DD01


Document History





2 � 3

Module Objectives


� Describe the eUTRAN transport architecture

� List transport NEs and describe their function

� Describe synchronization solution for eUTRAN





2 � 4







2 � 5

Table of Contents


1 Transport Network Requirements 71.1 LTE End-to-End IP Approach 81.2 Transport Network Requirement overview 91.3 List of requirements at the eNodeB 10

2 Traffic aggregation 112.1 Aggregation with 7705 SAR-F 122.2 7705 SAR-F 13

3 VLAN 143.1 VLAN 153.2 IPv6 16

4 IPSec 174.1 Security Requirements 184.2 UE Security 194.3 Transport Network Security requirements 204.4 Services Offered by IPSEC 214.5 Introduction of the Security Gateway for IPSec 224.6 Security Gateway collocated to core network 24

5 QOS 255.1 Introduction 265.2 EPS QoS parameters 275.3 QoS parameters mapping on the transport network 28

6 Synchronization 326.1 Why Synchronization? 336.2 Handover example 346.3 Frequency and Time-of-Day synchronization 356.4 LTE Synchronization Solution 366.5 Candidate LTE synchronization Implementations 37

7 META 387.1 Presentation 39





2 � 6








2 � 7

1 Transport Network Requirements





2 � 8

1 eUTRAN Transport Requirement

1.1 LTE End-to-End IP Approach

EUTRAN + EPC + Backhaul + Backbone = All-IP service deliveryReal-time, multiservice, high-bandwidth, end-to-end QoS

eNode B

IP channel

High performance, highly reliable IP backhaul network is critical to LTE success

� IP Communications(VoIP, Video)�Messaging SMS/MMS� Internet, Web 2.0

� Advanced Location-based Services

�Mobile TV, IP Multimedia

�Mobile office

IP BackhaulEvolved Packet Core

(IP)

MME PCRFPDN GWSGW

Service Delivery Platforms

LTE network is based natively on IP. So the IP transport network between the ePC and the eNodeB need to carry

all the services over IP. Due to the high data rate reachable by LTE and due to the diversity of the services and

so the diversity in terms of QoS (real time, delay, guaranteed bit rate, error rate …) the transport network has

high capacity and QoS management capabilities





2 � 9


1.2 Transport Network Requirement overview

eNode B

IP channel

IP BackhaulEvolved Packet Core

(IP)

MME PCRFPDN GWSGW

Service Delivery Platforms

Traffic separationVLAN

SecurityTraffic Encryption

QoS ManagementDiffServ

SynchronizationGPS, PTP … Aggregate all the site

traffic

The transport network carries basically telecom traffic (signaling and user data), OAM traffic and Debug traffic.

All these types of traffic has to be separated in the transport network. It is ensure by VLANs.

The different natures of data (signaling, internet traffic, voice, streaming …) have different constraints in terms

of delay, error rate and bit rate. The transport network takes them in account to ensure the services.

The eNodeB need to be synchronized for air interface reason. This synchronization can be received from the GPS

or without GPQ from the transport network which need to be able to transport this synchronization.

On site, collocated with the LTE eNodeB there will be eventually 2G, WCDMA or CDMA BTS. The IP transport

nature has to be able the aggregate and to transport all the traffic.

For security reason, the traffic need to be encrypted on the different interfaces.





2 � 10


1.3 List of requirements at the eNodeB

QoS: DiffservIPv4/IPv6

IP header compression

IP

VLANP-bit

Ethernet

3GPP compliance

GigaEthernetOptic Fiber

eNodeB connectivity

IPSec

SecurityGPS (Satellite)SyncE1588v2

Synchronization/Timing

GTP-US1-AP and X2-AP

The eNodeB requirements linked to the transport network are:

- The synchronization. Like there is no E1, its synchronization is lost and so the eNodeB must be synchronized by

another way.

- The security to secure traffic towards the ePC

- The connectivity depends on the site

- The compliancy with the 3GPP (S1AP and GTP-U)

- IP and its QoS mechanisms

- VLAN





2 � 11

2 Traffic aggregation





2 � 12

ePCePC

2 Chaining and traffic aggregation

2.1 Aggregation with 7705 SAR-F

nxE1(ATM)

7705 SAR-F

LTE eNodeB

3G/LTE NodeB Cabinet

CSA

IP Backhaul

MME

SGW

3G NodeB

GE

UTRANUTRAN

RNC

3G and LTE can share the same site to provide on the area a 3G and LTE coverage. 3G and LTE traffic are

aggregated on the IP transport network.

3G traffic is over ATM or maybe over IP depending on the release.

The 7705 SAR is called the CSA: Cell Site Aggregator.





2 � 13

2 eUTRAN Backhauling Solution

2.2 7705 SAR-F

� The 7705 SAR-F is integrated in LTE solution as Cell Site Aggregator (CSA).

� It multiplexes the different types of traffic (ATM & IP) over the IP Mobile Backhauling.

� It can be connected to a MPLS transport network.

� 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.

� The 7705 SAR can be connected to a MPLS transport network like it has MPLS capabilities. It is not the case of

the eNodeB. When Ethernet is carried over MPLS, it is called an Ethernet pseudowire or epipe.

� 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





2 � 14

3 VLAN





2 � 15

3 VLAN

3.1 VLAN

� VLAN are used to separate different nature of traffic.

� The eNodeB supports 2 VLAN:

� OAM VLAN for the OAM elements (XMS, NPO …)

� Telecom VLAN for the user plane and control plane on the S1 and X2 interface.

� The enodeB has 2 IP address, one in each VLAN

GigE

Telecom VLAN

OAM VLAN

S1

X2

XMS

MME eNodeB

SGW

The IEEE 802.1q standard contains specifications for tagging Ethernet frames with VLAN membership information.

It defines the operation of VLAN bridges that permit the definition, operation and administration of virtual LAN

topologies within a bridged LAN infrastructure.

Note that when Ethernet frames are tagged with VLAN membership, the frame header has a 3-bit field for

Ethernet user priority. This field determines the packet network treatment priority and may be used to

implement the transport QoS in the case of an L2-switched backbone network





2 � 16

3 VLAN

3.2 IPv6

� At IP level there are 2 options:

� IPv4 in both VLAN

� IPV4 in OAM VLAN and IPv6 in Telecom VLAN

GigE

Telecom VLAN

OAM VLAN

S1

X2

XMS

MME eNodeB

SGW

IPv4 only

IPv4 or IPv6

It is possible to activate IPv6 in VLAN Telecom. In this configuration, the eNodeB has:

- 1 IPv4 address for OAM traffic

- 1 IPv6 address for S1 and X2 traffic





2 � 17

4 IPSec





2 � 18

4 IPSec

4.1 Security Requirements

� Flat architecture:

� All radio access protocols terminate in one node: eNB

� IP protocols also visible in eNB

� Security implications due to� Architectural design decisions

� Interworking with legacy and non-3GPP networks

� Allowing eNB placement in untrusted locations

� New business environments with less trusted networks involved

� Trying to keep security breaches as local as possible

� As a result (when compared to UTRAN/GERAN):

� Extended Authentication and Key Agreement

� More complex key hierarchy

� Additional security for eNB (compared to NB/BTS/RNC)





2 � 19

4 IPSec

4.2 UE Security

� From Challenge-response authentication and key agreement procedure between MME and UE, the air interface is secured.

� Signaling Radio bearer are authenticated and encrypted

� Data Radio Bearer are encrypted

� The S1 interface requires also security but it is not UE-specific

� IPSec

eNodeB

MME

P-GWUE

S1-U

S-GW

RB

SRB

S1 MME

Secured





2 � 20

4 IPSec

4.3 Transport Network Security requirements

� Due to:

� eNB placement in untrusted locations

� New business environments with less trusted networks involved

� S1 and X2 interfaces need to be secured by IPSec tunnel

eNodeB

MME

P-GWUE

S-GW

RB

SRB

Unsecured Link

IP Sec





2 � 21

4 IPSEC

4.4 Services Offered by IPSEC

� IPsec provides the following services:

• Integrity check

• Authentication of data

• Confidentiality

• Protection against replay

@eNB @SGW

IP Sec

x→→→→y

IPsec

@NB→→→→@SGW @NB→→→→@SGW

Not entirely protected

Entirely protected

The IP Security Protocol (IPsec) is a set of mechanisms intended to protect the traffic at the IP level (IPv4 or IPv6).

In tunnel mode, the IP header is also protected (authentication, integrity and/or confidentiality). All of it isencapsulated in a new packet. The purpose of the header of this new packet is to transport the initial packet up to

the end of the tunnel, where the packet is de-encapsulated. Therefore, the tunnel mode can be used by both

terminal devices and security gateways.

The original IP packet is encapsulated in another IP packet.

The entire packet can be authenticated and/or encrypted.





2 � 22

Evolved Packet Core (IP)

MME

SGW

XMS

EMS SAM-5620

MLS 7750-SR

LTE

Base Station

IP Sec VPN Tunnel

MGW

SGSN

OAM backbone

SecurityGateway function

4 IPSec

4.5 Introduction of the Security Gateway for IPSec

The ALU solution to bring security over the transport network is to create IPSec VPN for Ethernet Backhaul with

an IP Device: MLS 7750-SR.

In order to avoid single point of failure, the implementation recommends to have a second MLS 7750-SR, for

redundancy purpose.

The Service Router will be supervise by the EMS SAM 5620.





2 � 23

4 IPSec

4.5 Introduction of the Security Gateway for IPSec [cont.]

LTE-Uu

LTE-Uu

S1-MME

S1U

UE

UE

eNB

eNBeNB

MME

ServingGateway

IP Transport Network (IP Cloud)

eUTRAN EPC

AP

AP

AP AP

AP

Ipsec Tunnel:Ipsec Tunnel:

SecurityGateway OAM

Ipsec Tunnel

Ipsec Tunnel

S1+X2

S1+X2

S1+X2

This diagram above shows a LTE network architecture with the introduction of the Security Gateway

This example indicates where Ipsec tunnel are used in a classic transport configuration with S1 and X2 interfaces

going through the Security Gateway





2 � 24

4 IPSec

4.6 Security Gateway collocated to core network

LTE-Uu

LTE-Uu

S1-MME

S1U

UE

UE

eNB

eNBeNB

MME

ServingGateway

IP Transport Network (IP Cloud)AP

AP

AP AP

AP

Ipsec Tunnel:Ipsec Tunnel:

SecurityGateway

OAM

(Ipsec Tunnel)

(Ipsec Tunnel)

X2

X2

X2S1

S1

S1

eUTRAN EPC

When the Security Gateway is collocated with the core network then it could important to have the X2 Ipsec

tunnel directly connected to the collocated eNB





2 � 25

5 QOS





2 � 26

5 QOS

5.1 Introduction

� ESP network (eUTRAN+ePC) provides EPS bearer between the UE and the PGW.

� A EPS bearer is associated to a set of QoS parameters which depends on the E2E services (streaming, VoIP, Access to internet)

� The main parameters are QCI, Maximum and Guaranteed bit rate in UL and DL

MME

P-GWS-GW

VoIP (real time)

Internet access (BE)

Streaming (Guaranteed bit rate))





2 � 27

5 QOS

5.2 EPS QoS parameters

sharing, progressive video, etc.99

Video (Buffered Streaming)TCP-based (e.g., www, e-mail, chat, ftp, p2p file

10-6300 ms88

Video (Live Streaming)Interactive Gaming10-3100 ms7

Non-GBR7

Video (Buffered Streaming)TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing)10-6300 ms6

6

IMS Signalling10-6100 ms15

Non-Conversational Video (Buffered Streaming)10-6300 ms54

Real Time Gaming10-350 ms33

Conversational Video (Live Streaming)10-3150 ms4GBR2

Conversational Voice10-2100 ms21

Example ServicesPacket Error Loss

RatePacket Delay

BudgetPriorityResource

TypeQCI

� The Maximum Bit Rate (MBR) and GBR are defined per EPS bearer :� The MBR defines the bit rate that the traffic on the bearer may not exceed

� The GBR defines the bit rate that the network guarantees (e.g. through the use of an admission control function)

Each bearer is assigned one and only one QoS Class Identifier (QCI).

QCI is used within the access network as a reference to node-specific parameters that control packet-forwarding

treatment (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol

configuration such as ARQ and HARQ parameters, etc.)

The standardized QCI label characteristics describe the packet forwarding treatment through the network based

on the following parameters:

� Resource Type (GBR or non-GBR)

� Priority

� Packet Delay Budget (PDB)

� Packet Error Loss Rate (PLR)

A label is applicable only locally. In LTE, eNB and LTE-Uu link label is a key element for LTE QoS control.





2 � 28

5 QOS

5.3 QoS parameters mapping on the transport network

� EPS bearer parameters are mapped on:

� Radio bearer with the scheduling type, retransmission, priority

� S1 and S5 bearers which are carried over GTP tunnel

� The QoS mechanism on S1 and S5 bearer are:

� Diffserv at L3

� p-bit at Ethernet level

eNodeB

MME

P-GWUE

S-GW

RB S1 Bearer S5 Bearer





2 � 29

5.3 QoS parameters mapping on the transport network

5.3.2 QoS parameters mapping

� Packet marking is required to ensure traffic separation and QoS transport in the mobile backhauling network

� It makes the translation from the bearer-level QoS (QCI) to L3 and L2 transport-level QoS (DSCP at L3 and p-bit at L2)

� Implemented in S/P-GW for DL/UL packets and eNB for UL packets

E2E IP packetIP header Bearer IDMAC header

P-bit [0,…,7]

DSCP [BE, EF, AF]

Tunnel header

Video (Buffered Streaming),

TCP-based (e.g., www, e-mail,

chat, ftp, p2p file sharing,

progressive video, etc.)

3AF21 (18)8 (non-

GBR)

Voice, Video (Live Streaming),

Interactive Gaming

3AF22 (20)7 (non-

GBR)

Video (Buffered Streaming),

TCP-based (e.g., www, e-mail,

chat, ftp, p2p file sharing,

progressive video, etc.)

5AF42 (36)6 (non-

GBR)

IMS Signalling6AF41 (34)5 (non-

GBR)

Non-Conversational Video

(Buffered Streaming)

5AF42 (36)4 (GBR)

Real Time Gaming7EF (46)3 (GBR)

Conversational Video (Live

Streaming)

7EF (46)2 (GBR)

Conversational Voice7EF (46)1 (GBR)

Service Examplep-bit

L2-transport-level QoS

DSCP

L3-transport-level QoS

QCI

Bearer-level QoS

Packet marking needs to be consistent from an end-to-end perspective





2 � 30

6 Synchronization





2 � 31

6 Synchronization

6.1 Why Synchronization?

� Synchronization is vital across many elements in the mobile network

� In the RAN, the need is focused in 2 principal areas:

� Radio Framing accuracy in TDD systems

� Handover control

Handover

UDLULDL

Radio Framing accuracy in TDD systems

UDLULDL X2X2

The eNodeB has an internal clock to synchronize the air interface (time and frequency). But it can drift slowly

and disturbs the cells. It is why the eNodeB must receive an external synchronization. It is not the same impact

in FDD and in TDD.

In FDD, the frequency synchronization is required to avoid the drift of the frequency center. It disturbs the

handover

In TDD, the time synchronization is also required for the radio frame synchronization.





2 � 32

6 Synchronization

6.2 Handover example

� The UE expects to see the target cell carrier at F2

� If F2>50ppb from nominal, the UE can not find it and call drops

F1

F2

Frequency

Time

+/- 50ppb

Handover

F1

F2

Frequency

Time

+/- 50ppb

UE can not lock to the target eNodeB.HO is unsuccessful

eNodeB drifts ouside 50ppb window

Parts-per-billion is a unit of concentration

In FDD, the system must be synchronized on the frequency to avoid bad HO success rate. Actually, if the

frequency center of the target cell drifts, the UE can have difficulties to re-establish the RRC connection.





2 � 33

6 Synchronization

6.3 Frequency and Time-of-Day synchronization

�Frequency Division Duplex (FDD) systems require only frequency synchronization

�Time Division Duplex (TDD) require both frequency and time-of-day (ToD) synchronization.

F1 F2 F3

+/- 50ppb

Frequency

Time

Time

+/- 2.5 µs





2 � 34

6 Synchronization

6.4 LTE Synchronization Solution

There different solutions are:

•IEEE1588v2 (PTP)

•GPS

•Synchronous Ethernet

Access NetworkAccess Network

Ethernet

GPS

1588v2 server

Synchronous EtherNet

1588v2 client

eNB

eNB

eNB IEEE1588v2 Precision Time Protocol

Sync Ethernet clock master

Holdover: 72 hours for Frequency and 1 hour for phase (standard)

Frequency Synchronization:

� Always required

� Single value so far for LTE: Max 50 ppb

Phase Synchronization (same frame start-time among eNodeB):

� TDD mode, whatever the eNodeB type

� FDD mode, in case one of the following features are used

eMBMS

HO CDMA/LTE

� Accuracy: Requirement is +/- 1.5 µsec phase accuracy

IEEE1588v2:

� 1588 Master server could be co-located with the MME.

� Recommended clock delivery over IP networks

GPS:

� Receiver inside the eNB.

� interface RS422

External timing port

Synchronous Ethernet

� Requires Layer 1 clock tree through all Ethernet devices between clock master and eNB’s.

� Synchronous Ethernet supporting intermediate nodes

High stability internal clock: optional





2 � 35

6 Synchronization

6.5 Candidate LTE synchronization Implementations

Applicable only for DSL access case

Requires DSL modem to provide

external clock to base station, or base

station integrates DSL termination

Established protocolNetwork Timing Reference

(NTR)

New technology, but similar in concept

to SDH/SONET

Requires continuous path of SyncE

capable nodes & links

Currently no way to distribute phase or

time

Not affected by network trafficSynchronous Ethernet

SyncE

)

New technology, but similar in concept

to NTP

More accurate distribution than NTP; allows lower

precision oscillator in base station

Provides frequency, phase, and time

Operable over any backhaul technology

IEEE 1588v2 Precision Timing

Protocol (PTP)

Requires high precision oscillator in

base station

Established protocol

Operable over any backhaul technology.

Network Time Protocol (NTP)

Requires outdoor/rooftop accessSimplifies requirements on backhaul network

PRC accuracy; provides frequency, phase, and time

Already deployed in some CDMA & WiMAX networks

Global Navigation Satellite

System (GNSS) e.g. GPS,

Galileo

SyncE

Not affected by network traffic)

DisadvantagesAdvantagesMethods

Provides frequency only





2 � 36

7 META





2 � 37

7 META

7.1 Presentation

OPEX ReductionLL vs MW/DSL/MEth/GPON

Bandwidth Optimization

ATM/ETH Aggregation

Resiliency

ScalabilityMW ETH / MEth / GPON

QoS & Traffic Engineering

IP traffic + Legacy traffic (Pseudo-wire) + Synchronization

Alcatel-Lucent's Mobile Evolution Transport Architecture (META) is the industry's first and most

comprehensive framework for mobile transport evolution to all-IP.

ETA integrates multiple mobile transport technologies including IP/MPLS, Optical, Microwave, DSL, and

GPON, into an end-to-end network architecture.

Profitable Evolution to Next Generation Mobile Services

META delivers increased and scalable bandwidth at lower cost.

TDM to Packet Evolution

META provides flexible evolution paths for any last mile access.

Network Simplification and Improved Performance

META provides industry leading integrated end-to-end management across multiple technology domains

wireless and wireline for simplified & reduced OPEX.

Global Network Transformation Expertise

META is backed by comprehensive professional services.

We discuss the drivers for META and Alcatel Lucent’s META portfolio offering for mobile backhaul transport.





2 � 38

End of ModuleLTE Transport





Section 3LTE eNodeB HW description

9400 LTE RAN LA2.0 Technical Overview TMO18213 D0 SG DEN Issue 6





3 � 2

Blank Page


Le Petit François2010-02-2203


Document History





3 � 3

Module Objectives


� Describe the eNodeB architecture

� Describe the eNodeB modules

� Describe the eNodeB Configuration





3 � 4

Table of Contents

Switch to notes view!Page

1 eNodeB Description 51.1 General Architecture 61.2 Cabinet Solution – Macro module 71.3 Distributed Solution – RRH Module 82. 9926 BBU 112.1 BBU Presentation 122.2 e-CCM-U Board Description 152.3 eCEM-U Board Description 172.4 BBU to backhaul Configuration 18

3 Compact EnodeB with TRDU2X 193.1 Macro Module - TRDU 2X 203.2 The Cube 213.3 External Alarm 22

4 Distributed eNodeB with RRH2x 234.1 9442 RRH 2X 244.2 Distributed eNodeB 264.3 BBU to RRH connection 274.4 Mounting Frame





3 � 5

1 eNodeB Description





3 � 6

CPRI

RF module

Digital <-> Radio

� S1 and X2 interface to ePC and other eNode Bs through

Gigabit Ethernet port

�Processing capabilities

�Send/Receive signal to/from radio through CPRI link

Base Band

eNode B brain and link to the network

EPC OthereNode Bs

eNode B

•X2•S1

�Receives and sends digital signal to/from Base Band

�Receives and sends radio signal to/from antennas

�Includes Power Amplifier, Duplexers, Receivers


1.1 General Architecture

An eNodeB is made of 2 main parts:

-The Baseband unit is charge of the interfaces with the ePC (MME and SGW) and the other eNodes and

also all the baseband processing (LTE Radio protocols).

-The RF module is charge of the RF conversion, the amplifier to send the RF signal on the feeder (RF

cable) up to the antennas





3 � 7


1.2 Cabinet Solution – Macro module

CabinetDigital module RF Macro Module

9926 BBUCPRI

TRDU 2X

MC-TRX

9412 Cube

A9100 BTS

The RF module in the cabinet is the TRDU2X. It is MIMO capable and there is one TRDU2X per cell. In future

release, MC-TRX will be introduced.





3 � 8

1 eNodeB Description

1.3 Distributed Solution – RRH Module

CPRI

9442 RRH 2X MC-RRH

The RF module for the distributed solution is the RRH2X. Like the TRDU2X, it is MIMO capable. In future

release, MC-RRH (based on the MC-TRX) will be introduced.





3 � 9

Jumpers0,5 dB

7/8" feeders30m ≈ 2dB

Jumpers0,4 dB

TMA

Optical fiber

no more RF losses ��66% more power @ antenna !

0,3dB

Jumpers0,8 dB(5m)

44W19W �� 33W ☺☺☺☺


1.4 Distributed solution – RRH benefits

40W

Great RF performance thanks to the capability of installing RRH close to the antenna: No RF feeders are

needed, only jumpers from the RRH to the antenna. This reduces the

feeder loss in UL/DL, having several consequences:

� The feeder cost and installation costs are reduced.

� In the UL, there is no need for a TMA, as the losses introduced by the RF feeder are greatly

reduced.

� In the DL, no RF power is dissipated in the feeder runs. The PA power can be reduced while

maintaining the same RF power at the antenna. This results in the power consumption of the

equipment being reduced. Compared to a conventional eNode B (equipped with MCPA 60W) that

delivers about 20W at the antenna level (assuming 3dB feeder+TMA losses), RRH40-21 (assuming

0.8 dB jumper loss) delivers 65% more RF power while consuming half the power.

The main purpose of the Tower Mounted Amplifier (TMA) is to decrease the overall noise of the system

by amplifying the received signal.

The TMA is a Low Noise Amplifier designed to be mounted as close as possible to the antenna system. The

TMA compensates the feeder loss on the receiving path by amplifying the received signal at the top of

the mast head equipment. The TMA has a gain of 12dB. The advantages of placing an amplifier on the

tower are an increase in uplink budget (at BTS level), a better coverage in rural areas at cell level and an

increased battery life at UE level.





3 � 10

After ☺☺☺☺

Radio

Digital

RRH

Backhaul Backhaul

Antenna Antenna

Optical Link

RF JumperRF Feeder

Before ��

Digital


1.4 Distributed solution – RRH benefits

Remote co-location of radio module with the antenna resolves capacity and coverage needs whilst

reducing operational and capital expenditure.

The advantages of using an RRH to replace a traditional eNode B are most evident in rooftop

installations. In fact, the limited space available in some sites may either prevent the installation of

traditional Macro eNode B equipment or require costly cranes to be employed, thus coverage holes may

appear. These sites can however host an RRH installation providing more flexible site selection and

therefore improved network quality. In addition installation times and costs are greatly reduced.





3 � 11

2 9926 BBU (BaseBand Unit)D2U-v3





3 � 12

2 9926 BBU

2.1 BBU Presentation

RBP

The 9926 BBU consists of four types of hardware boards:

• CCM which controls OAM management, part of call processing and internal/external data flow

switching/combining, supporting external/internal alarm connectivity and external synchronisation

reference interface. Only one of this module can be inserted in 9926 BBU. The 9926 BBU uses the latest

generation of core controller module: eCCM-U.

• CEM, controls part of call processing and base band transmit/receive digital signal processing. One, up to

a maximum three, of these modules can be inserted in the 9926 BBU. The 9926 BBU uses the latest

generation of channel element module: eCEM-U.

�RBP (Rack Back Plane), supports all internal links between CCM-U and CEM-U modules.

• RUC (Rack User Commissioning), which supports all commissioning of non-volatile memories, and fan

alarms. Note it exists in two different variants; one designed for -48V DC power supply and the other

designed for +24V DC power supply. The 9926 BBU can be added in the user space of any Node B or in a

standard 19 inch indoor rack, when the environmental conditions are compliant with the requirements

detailed in the Site Specification document

Unused eCEM slots on a powered 9926 d2U-V3 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.





3 � 13

2 9926 BBU


AIR FLOW

9926 d2U-V3 digital shelf layout

eCCM-U Slot 1

eCEM-U Slot 2

eCEM-U Slot 3

eCEM-U Slot 4

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.

The Alcatel-Lucent 9926 BBU solution is compliant with the Common Packet Radio Interface (CPRI).

The 9926 BBU rack has the following characteristics:

• width (W): 482.6 mm

• depth (D): 300 mm

• height (H): 88.1 mm

• weight (fully equipped): from 9.8 kg up to 10.5 kg (depending on the number of xCEM(s)-U in the digital

shelf).





3 � 14

2 9926 BBU


Backplane (RBP)

RUC

FAN

The Rack Back Plane (RBP)

The 9926 BBU houses one eCCM-U up to three eCEM-Us. The Rack Back Plane (RBP) is part of the 9926 BBU

and allows the signaling interconnections between the CCM-U and the CEM-U modules inserted within the

digital shelf. The backplane board also gives a power supply to the CCM-U and CEM-U modules.

The Fan Rack (also referred to as Rack User Commissioning -RUC) manages the

following functionalities::

• Power filtering

• Current limitation

• Commissioning

• Inventory

• Fan alarms report and power supply

• DC power supply connectivity.

The Fan Rack exists in two versions to meet different deployment requirements:

• -48V DC power version

• +24V DC power version





3 � 15

2 9926 BBU

2.2 e-CCM-U Board Description

� The main functionality provided by the eCCM-U GE module are the following:

� Internal interfaces to CEM-U boards

� Interfaces with RF modules and ePC

� IP plane support

� eNodeB synchronization � Integrated GPS receiver

� High stability OCXO

� O&M functions

� Collection of own 9926 BBU alarms, commissioning data

Extended Core Controller Module Unit (eCCM-U)

The 9926 BBU houses one eCCM-U.

The eCCM-U is a controller in charge of part of call processing, OA&M management, internal/external data

flow switching/combining, external/internal alarm connectivity, and an external synchronization reference

interface. The eCCM-U also contains CPRI interfaces to the RRHs.

Port 1= Eth2 = debug/NEM

Port 2 = RETA

MDA Geth = Eth0





3 � 16

2 9926 BBU

2.2 e-CCM-U Board Description

6 SFP cages for links to

radio modules

GE Ethernet MDA for S1 and X2 interfaces

Not used in LTE

The face plate of the eCCM-U provides the following connectors (please refer to figure below):

LEDs providing the current status of the module,

One port for connection to external GPS antenna (in case of integrated GPS receiver) via a SMB connector,

One RJ45 connector used for PPS input from an external GPS receiver; this connector also can provide one

RS232 port for control of external equipment,

One block of 6 SFP format connectors for connectivity to the radios (RRH, TRDU); each SFP connector is

equipped with two light indicators; they support 6 CPRI links or 3 CPRI + 3 HHSL links,

One RJ45 connector used for a 1-wire interface (connectivity to external alarm module, commissioning...),

One dual SMP connector providing input for 10MHz/15MHz input and 15MHz output,

One double RJ45 connector used for debug (RS232) and Ethernet (SiteLAN); each connector is equipped

with two LEDs (a yellow one showing Ethernet activity status and a green one for Ethernet link status),

One J20 connector (not used in LA2.0).

Extended Core Controller Module Unit (eCCM-U)

The 9926 BBU houses one eCCM-U.

The eCCM-U is a controller in charge of part of call processing, OA&M management, internal/external data

flow switching/combining, external/internal alarm connectivity, and an external synchronization reference

interface. The eCCM-U also contains CPRI interfaces to the RRHs.

Port 1= Eth2 = debug/NEM

Port 2 = RETA

MDA Geth = Eth0





3 � 17

2 9926 BBU

2.3 eCEM-U Board Description

The e-CEM-U (enhanced Channel Element Module) provides base-band signal processing for the eNodeB. It also supports data, control and timing interfaces to the eNodeB

1Nb sector eCEM-U

Peak L1: 172 Mbps DLPeak throughput/

eCEM-U

2X2 MIMO 1X20 MHz

2X2 MIMO 1X10 MHz

2X2 MIMO 1X5 MHz

Bandwidth/eCEM-U

Modem (CEM)

The xCEM-U performs digital signal processing for both the Tx and Rx paths. The xCEM-U processes all types

of LTE physical channels in both UL and DL directions.

It implements the LTE radio protocols including:

� UL Scheduler

� DL Scheduler





3 � 18

2 9926 BBU

2.4 BBU to backhaul Configuration

� To connect the eNodeB to the backhaul network, the MDA used in LTE provides:

� RJ45 connector for GE electrical backhaul� Category 5e Ethernet cable

� Shall not exceed 100m

� Two SFP connectors for GE optical backhaul� Single Mode Dual Fiber or Multi Mode Dual Fiber

Backhaul network

?

GE Ethernet MDA for S1 and X2 interfaces

MDA = Media Device Adaptator

The LTE digital does not support traffic backhaul over PCM links but only over Ethernet links.





3 � 19

2 9926 BBU

2.4 BBU to backhaul Configuration [cont.]

1. Ethernet Cabling :• Category 5e Ethernet cable,• RJ45 cabling shall comply with IEC11801 & TIA/EIA-568 standards.

2. Optical Cabling :• Multi Mode Dual Fiber: one fiber carries the downlink signal and a second one

the uplink signal. The MM fiber is used for short distance (15 m)

• Single Mode Dual Fiber: two fibers are used; one fiber carrying the downlink signal and a second one the uplink signal. The same Single Mode SFP transceiver is used on both ends of the fiber.

DLUL

20 Km1310 nm 1310 nm

EPC

ULDL

15 m850 nm 850 nm

EPC

• The physical length of the channel (fixed horizontal cable & patch cords / cross-connect jumpers) shall

not exceed 100 m,

• Patch cords / cross-connect jumpers:

� Length of patch cords/jumper cables should not exceed 10 m in total. In case longer

connection is required, the installation should be made of a horizontal cable plus the

required patch cords/jumper cables,

� F/UTP minimum constructed cable, using 26 AWG minimum conductors,

� Male-Male connectorised cable.

• Horizontal Cable:

� Its physical length shall not exceed 90 m,

� F/UTP minimum constructed cable, using 24 AWG minimum insulated solid conductors,

� Female-Female connectorised cable.

• Foil screens should be connected to ground for each cable of the Ethernet channel.





3 � 20

3 Compact EnodeB with TRDU2X





3 � 21

3 Compact eNodeB with TRDU2X

3.1 Macro Module - TRDU 2X

Radio technology : LTE

5, 10 or 20 MHz LTE bandwidth

Features:

� MIMO capability (2X2)

� 2x40 W

Functions:

� RF converters

� Tx amplifier

� Rx LNA

� RF Filter

The TRDU is an RF unit that comprises the radio, Tx amplifier, Rx LNA, and RF filter in a single module. The

TRDU supports two Tx paths with 40W per path. In addition to the pair of CPRI ports to connect to BBU(s)

and the RF ports connected to antennas, there are several other interfaces to connect to an external RF

filter, typically to be used for antenna-sharing configurations.





3 � 22


3.1 Macro Module - TRDU 2X [cont.]

2 x 40WEDD Band (800 MHz Lower)TRDU2x40-08L

2 x 40WBand XIII (700 MHz Upper)TRDU2x40-07U

Output RF Power Frequency BandTRDU Naming

√√√√TRDU2x40-08L

√√√√√√√√TRDU2x40-07U

-48 VDC+24 VDCTRDU type

< 15kgWeight

355 mm (h) x 110 mm (w) x 360 mm (d)

(Height including guide rail: 367 mm)Size HxWxD

Gigabit Ethernet cable (Special cable for SFP cage).

Multi Mode Dual Fiber (and associated SFP) may be used in

some special cases. (Refer to chapter 9.2 for more detailed

information)

CPRI interface

Star configurationNetwork topology

≈ 415 WPower consumption

(typical at 40W RF)

Two variants: -48VDC, and +24VDCPower supply

40W nominal RF power, on each Transmit antenna connectors

(applies for both 16 and 64 QAM)

RF output power @

antenna port

10MHzCarrier bandwiths

supported

1 LTE carrierNb of carriers

Dl: 746-756 MHz

Ul: 777-787 MHzTx/Rx Band

Band XIII3GPP Band





3 � 23


3.2 The Cube

d2Uv3 BBU

3 TRDU2X(3 cells)

Fan TrayPower DistributionPanel

Enhanced Alarm ModuleeAM

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. That envelope includes all elements of the eNodeB except the

7705 unit, and (for the 9926 BBU equipped eNodeBs) the eAM. Therefore in the 9926 BBU case, the

cabinet contains the three TRDUs, the TRDU fan tray and the 9926 BBU.





3 � 24


3.3 External Alarm

� The 9926 BBU can be equipped with an external alarm module.

The 9926 BBU can be equipped with an external alarm module.

The eAM provides an extension to support up to 32 external user alarms Support of external user alarms

allows the BTS and OAM to become the centre for monitoring of many cell site functions in addition to

those directly related to the BTS. These include items such as power systems and battery backup, cell

site door alarms, external alarms provided by other cell site equipment such as backhaul modems, etc.





3 � 25






3 � 26


4.1 9442 RRH 2X

Radio technology: LTE

•2.6 GHz• 5, 10 or 20 MHz

Features :

•MIMO capability (2X2)•2x30W

Functions:

• RF converters• Tx amplifier• Rx LNA• RF Filter

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 and 4

Receivers to support 4-way Receive Diversity. The RRH specified is for 3GPP Band VII (2600MHz) and

supports 2x30W over a 20MHz bandwidth. The official product name is RRH2x30-26.





3 � 27


4.1 9442 RRH 2X [cont.]

� 2 RF transmitters to enable 2x2 MIMO

� 4 Receiver to support 4-way Receive Diversity

Top View

Bottom View

� Power supply

� Links to BBU (optic fiber)

� Alarms

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 and 4

Receivers to support 4-way Receive Diversity. The RRH specified is for 3GPP Band VII (2600MHz) and

supports 2x30W over a 20MHz bandwidth. The official product name is RRH2x30-26.

These two equipments are linked by optical fibers, carrying LTE downlink and uplink (main and diversity)

base band digital signals along with OAM information.





3 � 28

4.1 9442 RRH 2X

4.1.1 TD-RRH

� For TDD solution, The RRH is called TD-RRH.

� The official naming will be Alcatel-Lucent TD-RRH2x20-XY, where XY represents the supported frequency band:

� TD-RRH2x20-2300 (2x20W at 2300 MHz – 3GPP band 38)

� TD-RRH2x20-2600 (2x20W at 2600 MHz – 3GPP band 40)





3 � 29


4.2 Distributed eNodeB

� 1 RRH per sector

� Star configuration (not daisy chain)

CPRI links (optical fiber)Digital Signal

2 Antennas per cell

FeedersRF Signal

In downlink, the RRH receives the optical signal from the BTS. The signal is converted into an electrical

digital baseband signal, which is then digital to analogue converted and up converted to an RF signal. The

RF signal is amplified through power amplifiers and sent to duplexers.

In uplink, two signals are received from the main and diversity antenna (1&2). They are amplified through

low noise amplification chains and down-converted before being converted into digital signals, then

multiplexed according to I/Q radio signal format and converted into optical signals that are sent to the

digital BTS (e.g. eNodeB). RRH can also process 2 additional RX signals in order to manage 4 ways RX

diversity.





3 � 30


4.3 BBU to RRH connection

� The CPRI interface supports:

� Multi Mode dual fiber

� Single Mode single fiber

SFPSFP

CPRI Link

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 Remote Radio Heads.

Multi Mode dual fiber: One fiber carries the downlink signal and a second one the uplink signal. The MM

fiber is used for short distance (<= 500 m). The SFP module in Multimode uses a transmitter 850 nm

wavelength.

Single Mode single fiber: The 9926 BBU supports Single mode transceiver, Single fiber (one single fiber

carries both downlink and uplink signal). The SM must be used for high distance up to 15 Km. The SFP

module used on the 9926 BBU uses a 1550 nm wavelength transmitter. On the RRH the SFP module uses a

1310 nm wavelength transmitter.





3 � 31


4.4 Mounting Frame

� Depending on the hardware installation, there are different mounting kit.

Wall mounting kit Pole mounting kit Stand Floor mounting kit





3 � 32

End of ModuleLTE eNodeB HW description





Section 4LTE RAN OAM description







4 � 2

Blank Page


First editionLast name, first nameYYYY-MM-DD01


Document History





4 � 3

Module Objectives


� To be able to describe the OMC-B Architecture

� To be able to describe the OMC-B HW & SW ArchitectureTo be able to describe the OMC products for configuration management

� To be able to describe the OMC products for Fault management

� To be able to describe the OMC products for Performance management

� To be able to describe Self Optimization/Organizing Network cases





4 � 4







4 � 5

Table of Contents


1 XMS Introduction 71.1 OAM Architecture 81.2 XMS Unified Management System for Wireless 91.3 LTE XMS Hardware Portfolio 101.4 Main Functions 111.5 GUI 12

2 Fault Management 132.1 Fault Management 142.2 Alarm Surveillance 15

3 Configuration Management 163.1 RAN Configuration Principles 17

4 Performance Management 194.1 LTE XMS Performance tool Portfolio 204.2 Network Performance Optimizer (NPO) 214.3 RF Optimizer & Wireless Quality Analyser 22

5 Self Optimization Process 235.1 Self Organizing/Optimization Opportunities 245.2 eNB Self Establishment/Configuration 255.3 ANR Configuration and Optimization 265.4 Automatic Configuration of Physical Cell ID 27





4 � 6








4 � 7

1 XMS Introduction





4 � 8

1 XMS Introduction

1.1 OAM Architecture

eUTRAN

eNodeB

PGWSGW

ePCHSS

PCRF

MME

UE PDN

OAM applications:

)) 5620 SAM )) 9453 XMS 5620 SAM

9453 XMS

XMS = LTE eNode B Manager

The 9453 XMS is the Management System for LTE RAN, it is main system which is efficient, Robust and scalable, it

ensures:

� Network service fulfillment and service Assurance.

� Plug and play deployment of the eNB,

� Provisioning activation, service Assurance (fault,

� correlation, state management, services overviews

� at a glance, troubleshooting)

� Inventory and resource management.

� Performance management and security.

XMS also leverages the Self-Organizing and the Self-Optimizing Networks (SON) concepts.





4 � 9

1 XMS Introduction

1.3 LTE XMS Hardware Portfolio

LTE XMS Solution Scalability on state of the art SUN™ Servers

Small-scale system Medium-scale system Large-scale system

150 eNode Bs

5 concurrent

user sessions

Supported on:

SUN Sparc Enterprise

T5220

700** eNode Bs

35 concurrent user

sessions

Integration* of up to

700** BTS of GSM,

WCDMA, CDMA

technology

Supported on:

SUN Netra T5440

Up to 3000** eNode Bs

50 concurrent user

sessions

Integration* of up to

3000** BTS of GSM,

WCDMA, CDMA

technology

Supported on:

SUN Sparc Enterprise

M5000 with a pair of

ST2540 disk arrays

* Cf integration roadmap, through integrated EMSs – assumes EMSs servers separate

** scalability target subject to change depending on technology & specific engineering – please consult our

engineering team

The distributed architecture of the Software Application allows a large variety of deployment fitting operator’s

operational need.





4 � 10

1 XMS Introduction

1.4 Main Functions

9453 XMS

Configuration Management

• NE creation/deletion in XMS • eNodeb Supervision• Link Monitoring• Plug&Play for enodeB• Reconfiguration • Lock&Unlock of Objects • Online parameters browsing

and setting.

Fault Management

• Alarm display• Alarm Acknowledgement• Alarm Clear• Alarm Help Online • Notification Management

Performance Management

• eNodeB counters retrieval• Call Trace management

Software replacement Mngt

• Automated software activation• Software download • Software Activate• Software Acceptance or Abort





4 � 11

1 XMS Introduction

1.5 GUI

XMS client is based on Java Web Start application.





4 � 12

2 Fault Management





4 � 13

2 Fault Management

2.1 Fault Management

The supervision view displays all radio resources and their states. For each network object (EnodeB, LteCell, S1

and X2 interfaces) the status is clearly visible. That means their administrative, operational and alarm status.

By this way, it is easy to identify an object in trouble. The contents of this table can be exported to a printer

or into an HTML file. Attributes (columns) can be customized by the user.





4 � 14

2 Fault Management

2.2 Alarm Surveillance

� The CFMA application can be opened directly from the Iconbox or from the Supervision view by selecting the menu Display Related Alarms for a given object.

The FM GUI provides an alarm browser window which is accessible from the desktop menu and from the main FM

frame menu.

� The browser displays a high level view of the alarms in the network element for which the user has

permission. The alarm browser may be filtered according to the displayed attributes and the operator’s

permissions.





4 � 15






4 � 16


3.1 RAN Configuration Principles

eUtran

Snapshot

Workorder

9453 XMS

Import Snapshot

Open wps

Save as

Local directory

Workspace

Workorder

WSP is an offline tool to configure eUTRAN. The configuration file is called a “workorder”. This workorder can be

activated by the XMS to apply the configuration on the eUTRAN network.

XMS can also provide to WPS “snapshot” to modify by WPS the current configuration.

XMS also offers on-line configuration capabilities to support network operations: object editors for

parameter tuning, CCL (Common Command Language) for various purposes. “Smart Activation” mechanism

guarantees that the activation of a new configuration on the managed NEs is done with a minimum impact

on service, while reducing the complexity of the activation procedure.





4 � 17

3.1 Configuration Management

Session Manager

The Session manager offers the possibility to activate several work-orders in a session. In case of a multi

work-orders session, all the previous steps are based on the merge of the work-orders.

The activation of a work-order is controlled and monitored within an activation session. This is a step-by-

step assistant where the user can consecutively:

� Load a work-order to create a session while splitting WO content in NE activation units with syntactic

checks and application of provisioning changes on OAM objects.

� Validate a Session work-order to perform Semantic checks& Analyze all service impact if NE activation

units are downloaded.

� Pre-activate a NE activation unit which downloads the configuration changes to the NE .

� Activate a NE activation unit which applies/activates configuration changes.

� Resume: The activation operation may be interrupted due to communication problems with NE and

because the activation process requires several activate commands to be completed.

� Abort: This operation enables to abort an ongoing activation process.

� Fallback mechanism is also provided by the Activation Manager.





4 � 18






4 � 19


4.1 LTE XMS Performance tool Portfolio

Counters

CallTraces

eUTRAN

eXtended

Management

System

XMS

BASE PRODUCT

NPO

Network

Performance

Optimizer

WTA

Wireless Trace

Analyser

Counters

CallTraces

Network Performance Optimizer :

� Counter Based

� Performance Reporting

� Added value modules

Radio Frequency Optimizer :

� CallTrace Based

� Per Call Analysis

� Graphs / KPI

Wireless Quality Analyzer :

� CallTrace Based

� Mobility Optimization

� Call Failure Optimization





4 � 20


4.2 Network Performance Optimizer (NPO)

DiagnosticRules & CM Tuning

Geographical analysis

QoS Alerter & Warning

Web AccessPerf Reporting

Network Performance Optimizer (NPO): Reporting and optimizing multi-standard network performance

Embedded Alcatel-Lucent Engineers Know-How :

Large set of specific release independent Indicators

Covering all aspects for performance reporting, Optimization & Troubleshooting

� Accessibility / Retainability

� Congestion / Traffic

� Call profile

� Capacity/load

� Mobility

� Specific Feature Monitoring

� Quality

Additional Extended Set of Indicator for network optimization, network evolution and business planning

Supported Devices:

LTE eNB

LTE MME, S&P GTW

WCDMA NB, RNC

GSM BTS, BSC





4 � 21






4 � 22


5.1 Self Organizing/Optimization Opportunities

Different SON use cases will be relevant at different times of network operation, e.g. during initial roll-out, early

phases of operation, or operation of a mature network with high load

Self Organizing Network (SON) is a 3GPP-standardized initiative which drives the building of intelligence and

automation into the network itself to help operators solve those challenges

SON provides Operators with a path to maximize their network performance with lower effort (and thus lower

cost).





4 � 23


5.2 eNB Self Establishment/Configuration

IP Network

mobile core network

SecurityGateway

1 DHCP procedure

2 DHCP provides: Public Ip for

eNB, OAM & 1st hop

MME

3

XMS Polling until eNBconnection established.

Authentication with SNMPV3

4 OAM authentication of the eNB

5 OAM checks the SW version on the eNB if an upgrade is needed then send the SW to

the eNB

6 eNB is rebooting

7 eNB is making a self test

8 eNB is retrieving the configuration

9

eNB is establishing an IPsectunnel to the security gateway

and connect to MME

DHCP Server

LTE Management

System (XMS)

SecurityGateway

DHCP Server

XMSMME

- IP@

- connection- authentication- software download- configuration download

- Self test- inventory

- connection

Self Configuration

Network Deployment Phase

Self Configuration


� This feature describes a range of requirements for the automatic self-configuration of the eNB during initial

deployment or subsequent upgrades. It includes a number of distinct functions:

� eNB Self-Test

� Plug-and-play eNB

� Auto eNB Authentication

� Automatic download of eNB Parameters from OMC

� Automatic inventory

� Auto SW Download

� Driving towards “zero-touch” comissioning LTE eNB, this feature reduces the planning&deployment-related

CAPEX and OPEX of the operator by automating the currently manually intensive tasks of deploying, initial

configuration and subsequent configuration updates of a deployed eNB. In addition it will further speed up

the time between the eNB switch on and the eNB becoming operational. Rollout Time To Market shall be

reduced allowing faster profitability.





4 � 24


5.3 ANR Configuration and Optimization

* PCI: Physical Cell identifier / CGI: Cell Global Identifier

eNB

Cell B

PCI = 5

CGI = 19

Table

XMS

Cell B

PCI = 5

CGI = 19

Operator Check

Neighour infos

via X2

UE Report PCI =5

Strong Signal

NeighboureNB

X2

SON NCLalgorithm

Neighbour Relationship Table

(NRT) per cell

NeighboureNB

Operator Preferences:- white list, - black list

Self Configuration


Self Configuration


Automatic Neighbor Relationship

� The eNB is able to autonomously generate and manage its own intra-frequency neighbor relation tables (NRTs)

by requesting Ues 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 XMS. 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.





4 � 25


5.4 Automatic Configuration of Physical Cell ID

Collision Free: CellID unique to immediate neighbours

Confusion Free: CellID unique to neighbours’ neighbours

New integration

PCI algo

Self Configuration


Self Configuration


Physical CellID shall be allocated out of the pool of 504 possible IDs available as specified in 3GPP.

eNB assigns a PCI to one of its cells which has been allocated by the O&M system. The XMS determines

automatically the allocation of PCI to the cells within the eNBs, ensuring that they are assigned in a collision

and confusion free manner

Decentralized feature: Investigating the ability of the eNB to automatically configure the Physical CellIDs.

Currently assessing the feasibility and challenges of such approach.

This feature automates the configuration of the Physical CellIDs within the eNB. The objective for the algorithm

is to avoid PCI collisions and confusions, knowing that the eNB will profite from the ANR functionality to learn

about their neighbours PCIs. Therefore, for instance, when a new cell is integrated, it chooses an initial PCI

value. Then, after learning from its neighbours’ configuration, it might detect a collision or confusion and

decide to change its PCI value.

Benefits the operator by reducing the amount of pre-planning and manual provisioning he has to do for an LTE

network, and also reducing the re-planning needed as additional eNBs are deployed. Significant reduction of

deployment-related CAPEX and OPEX, as part of the global SON effort.

PCI collision:

is to say that 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. Consequence: In the worst case, the eNB knows of only one

cell and will trigger a 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





4 � 26

End of ModuleLTE RAN OAM description

@@COURSENAME - Page 1All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

@@COURSENAME@@PRODUCT

1

Last But One Page



@@COURSENAME - Page 2All Rights Reserved © Alcatel-Lucent @@YEAR

All rights reserved © Alcatel-Lucent 2010Passing on and copying of this document, use and communication of its

contents not permitted without written authorization from Alcatel-Lucent

Documents

85962275-Alcatel-LTE RAN LA2.0 Technical