LTE Ran Lucent

Title page

Alcatel-Lucent 9400

LTE Radio Access Network | Release LA4.0

RAN Overview

418-000-012

Issue 1 | March 2012

Alcatel-Lucent Proprietary

Use pursuant to applicable agreements


Legal notice

Legal notice

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective

owners.

The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.

Copyright 2012 Alcatel-Lucent. All rights reserved.

Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by anyone outside

Alcatel-Lucent without its written authorization.

Not to be used or disclosed except in accordance with applicable agreements.




Contents

About this document

Purpose ............................................................................................................................................................................................. ixix

Intended audience ......................................................................................................................................................................... ixix

Supported systems ........................................................................................................................................................................ ixix

How to use this document ......................................................................................................................................................... ixix

Conventions used ........................................................................................................................................................................... xx

Related information ....................................................................................................................................................................... xx

Document support .......................................................................................................................................................................... xx

Technical support ........................................................................................................................................................................... xx

How to order .................................................................................................................................................................................... xx

How to comment ........................................................................................................................................................................... xixi

1 Long Term Evolution System Overview

Overview ...................................................................................................................................................................................... 1-11-1

Long Term Evolution .............................................................................................................................................................. 1-11-1

LTE functions ............................................................................................................................................................................. 1-31-3

LTE network components ..................................................................................................................................................... 1-41-4

LTE interfaces ............................................................................................................................................................................ 1-61-6

LTE protocol stacks .................................................................................................................................................................. 1-71-7

2 LTE Radio Access Network

Overview ...................................................................................................................................................................................... 2-12-1

LTE RAN ..................................................................................................................................................................................... 2-12-1

LTE RAN interfaces ................................................................................................................................................................ 2-22-2

....................................................................................................................................................................................................................................

Alcatel-Lucent 9400 RAN

418-000-012 Release LA4.0

Issue 1 March 2012



iii

3 Architecture

Overview ...................................................................................................................................................................................... 3-13-1

5620 Service Aware Manager (SAM) ............................................................................................................................... 3-13-1

Network Performance Optimizer (NPO) .......................................................................................................................... 3-33-3

eNodeB ......................................................................................................................................................................................... 3-53-5

Network Element Manager (NEM) .................................................................................................................................... 3-73-7

Wireless Trace Analyzer (WTA) ........................................................................................................................................ 3-73-7

Wireless Provisioning System (WPS) ............................................................................................................................... 3-73-7

4 LTE RAN OAM functions

Overview ...................................................................................................................................................................................... 4-14-1

Fault management ..................................................................................................................................................................... 4-14-1

Configuration management ................................................................................................................................................ 4-154-15

Performance management ................................................................................................................................................... 4-294-29

Security ...................................................................................................................................................................................... 4-464-46

Call Trace .................................................................................................................................................................................. 4-464-46

Self Optimizing Network (SON) ...................................................................................................................................... 4-474-47

Transport call admission control ....................................................................................................................................... 4-484-48

5 LTE Services

Overview ...................................................................................................................................................................................... 5-15-1

Synchronization ......................................................................................................................................................................... 5-15-1

Quality of Services (QoS) ...................................................................................................................................................... 5-35-3

A Abbreviations

Overview .....................................................................................................................................................................................A-1A-1

Initialisms ...................................................................................................................................................................................A-1A-1

Acronyms ....................................................................................................................................................................................A-5A-5

Index

Contents

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

iv Alcatel-Lucent Proprietary



418-000-012 Release LA4.0

Issue 1 March 2012

List of tables

1-1 LTE interfaces ............................................................................................................................................................. 1-61-6

4-1 Fault types .................................................................................................................................................................... 4-24-2

4-2 State types .................................................................................................................................................................... 4-54-5

4-3 Alarm termination ..................................................................................................................................................... 4-84-8

4-4 AvailabilityStatus values and default states ................................................................................................... 4-194-19

4-5 Parent-child object .................................................................................................................................................. 4-204-20

4-6 eNodeB XML file naming convention ............................................................................................................ 4-424-42

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



v

List of tables

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

vi Alcatel-Lucent Proprietary



418-000-012 Release LA4.0

Issue 1 March 2012

List of figures

1-1 LTE network components ..................................................................................................................................... 1-41-4

1-2 User-plane protocol stack ....................................................................................................................................... 1-81-8

1-3 Control plane protocol stack .................................................................................................................................. 1-91-9

2-1 LTE RAN interfaces ................................................................................................................................................. 2-22-2

2-2 S1 interface .................................................................................................................................................................. 2-32-3

2-3 X2 interface ................................................................................................................................................................. 2-42-4

2-4 LTE air interface ........................................................................................................................................................ 2-52-5

3-1 Standalone 5620 SAM system .............................................................................................................................. 3-23-2

3-2 NPO with auxiliary server ...................................................................................................................................... 3-43-4

3-3 NPO with PCMD support (48K configuration) .............................................................................................. 3-43-4

3-4 eNodeB architecture ................................................................................................................................................. 3-53-5

4-1 Configuration extract view .................................................................................................................................. 4-234-23

4-2 Configuration import view .................................................................................................................................. 4-234-23

4-3 Offline configuration activation view .............................................................................................................. 4-244-24

4-4 cmXML interface overview ................................................................................................................................ 4-254-25

4-5 9452 WPS positioning within OAM ................................................................................................................ 4-284-28

4-6 Measurement scheduling and reporting .......................................................................................................... 4-314-31

4-7 Functional view of the counter observation domain .................................................................................. 4-364-36

4-8 Measurement files - schedule ............................................................................................................................. 4-394-39

4-9 SAM Call Trace Architecture ............................................................................................................................. 4-474-47

5-1 Synchronization distribution ................................................................................................................................. 5-35-3

5-2 QoS ................................................................................................................................................................................. 5-45-4

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



vii

List of figures

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

viii Alcatel-Lucent Proprietary



418-000-012 Release LA4.0

Issue 1 March 2012

About this documentAbout this document

Purpose

This document provides an overview of Long Term Evolution Radio Access Network

(LTE RAN) system. The document can be used to understand the different aspects of

LTE, LTE RAN, architecture, interfaces, OAM functions and services.

Intended audience

This document provides an overview of the LTE technology and introduces the

Alcatel-Lucent solution to operations and maintenance personnel and to other users who

want to know more about the LTE RAN for LTE network management.

Supported systems

This document applies to the System Release LTE RAN LA4.0 (frequency division

duplex - FDD) and TLA4.0 (time division duplex - TDD).

How to use this document

The following table describes how to use this document.

Document organization When to use

Chapter 1, Long Term Evolution

System Overview

To know about Long Term Evolution.

Chapter 2, LTE Radio Access Network To know about Long Term Evolution Radio Access

Network.

Chapter 3, Architecture To know about different architecture and various

components involved in the Long Term Evolution

Radio Access Network solution.

Chapter 4, LTE RAN OAM functions To know about LTE RAN OAM functions.

Chapter 5, LTE Services To know about Long Term Evolution services.

...................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



ix

Conventions used

The following typographical conventions are used in this guide:

Appearance Description

italicized text Used for:

File and directory names

Emphasized information

Titles of publications

A value that the user supplies

graphical user interface text or key name Used for:

Text that is displayed in a graphical user

interface or in a hardware label

The name of a key on the keyboard

input text Command names and text that the user types

or selects as input to a system

output text Text that a system displays or prints

Related information

The following document is referenced in this document or includes additional information

relevant to this document. Refer to Alcatel-Lucent 9400 LTE Radio Access Network

Customer Documentation Overview, 418-000-010 for the purpose of the listed document.

Alcatel-Lucent 9400 LTE Radio Access Network Terminology Overview, 418-000-011

Document support

For support in using this or any other Alcatel-Lucent document, contact Alcatel-Lucent at

one of the following telephone numbers:

1-888-582-3688 (for the United States)

1-630-224-2485 (for all other countries)

Technical support

For technical support, contact your local Alcatel-Lucent customer support team. See the

Alcatel-Lucent Support web site (http://www.alcatel-lucent.com/support/) for contact

information.

How to order

To order Alcatel-Lucent documents, contact your local sales representative or use Online

Customer Support (OLCS) (http://support.alcatel-lucent.com).

About this document

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

x Alcatel-Lucent Proprietary



418-000-012 Release LA4.0

Issue 1 March 2012

How to comment

To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-

lucent.com/comments/) or e-mail your comments to the Comments Hotline

([email protected]).

About this document

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



xi

About this document

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

xii Alcatel-Lucent Proprietary



418-000-012 Release LA4.0

Issue 1 March 2012

1 1Long Term Evolution

System Overview

Overview

Purpose

This chapter provides an overview of the Long Term Evolution (LTE).

Contents

Long Term Evolution 1-1

LTE functions 1-3

LTE network components 1-4

LTE interfaces 1-6

LTE protocol stacks 1-7

Long Term Evolution

Introduction

Long Term Evolution (LTE) is the next generation broadband wireless technology for

3GPP and 3GPP2 networks with the support of up to 20 MHz of bandwidth. LTE is

predominantly associated with the radio access network (RAN). The system architecture

evolution (SAE) specifications defines the core network which is termed as evolved

packet core (EPC) including all Internet Protocol (IP) networking architecture.

LTE provides high data rate by combining four important mechanisms:

Orthogonal Frequency Division Multiple Access (OFDMA) on the downlink to

achieve high peak data rates in high spectrum bandwidth.

Single Carrier Frequency Division Multiple Access (SC-FDMA), a technology that

proves advantageous in terms of power efficiency on the uplink.

...................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



1-1

Use of 64-Quadrature Amplitude Modulation (QAM).

Advanced Antenna techniques such as Multiple Input Multiple Output (MIMO).

LTE features

The following are the features of LTE:

Spectral efficiency (5 bps/Hz DL, 2.5 bps/Hz UL), user throughput (up to 100 Mbps),

latency (10 ms UE-eNodeB), cell edge bit rate

Simplification of the radio network with flexible spectrum allocation (1.4 20 MHz)

Support of efficient packet-based services such as Multimedia Broadcast Multicast

Service (MBMS) and IP Multimedia Subsystem (IMS)

Converged baseband and Software-Defined Radio (SDR) modules

Self-Organizing Network (SON) capabilities

Inter-working with GSM, W-CDMA, and CDMA networks

Radio resource management and fair scheduler

IP transport

Interoperability with networks such as UTRAN, GERAN, and EV-DO

Benefits of LTE

LTE provides global mobility with a wide range of services that includes voice, data, and

video in a mobile environment with lower deployment costs.

The following are the benefits of LTE:

Support for higher user data rates

Reduced packet latency and rich multimedia user experience

Increased spectral efficiency. Offer new services and adapt to available spectrum

Improved system capacity and coverage as well as variable bandwidth operation

Lower deployment costs

Excellent performance for outstanding quality of experience

Wide spectrum and bandwidth range

Cost effective with a flat IP architecture

Smooth integration and mobility with the networks

Optimized usage of radio resource management and fair scheduler

Long Term Evolution System Overview Long Term Evolution

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

1-2 Alcatel-Lucent Proprietary



418-000-012 Release LA4.0

Issue 1 March 2012

LTE functions

Overview

This section describes the LTE functions hosted by eNodeB from 3GPP standard

perspective.

eNodeB functions

The eNodeB performs the following functions:

Radio Resource Management, Radio Bearer Control, Radio Admission Control,

Connection Mobility Control, Dynamic allocation of resources to UEs in both Uplink

and Downlink (scheduling)

IP header compression and encryption of user data stream

Selection of MME at UE attachment

Routing User Plane data to SAE Gateway

Scheduling and transmission of paging messages (originated from the MME)

Scheduling and transmission of broadcast information (originated from the MME or

Operations, Administration and Maintenance (OAM)

Measurement and measurement reporting configuration for mobility and scheduling

Mobile Management Entity (MME) functions

The MME performs the following functions:

Distribution of paging messages to the eNodeBs

Security control

Idle state mobility control

SAE bearer control

Ciphering and integrity protection of NAS signaling

System Architecture Evolution (SAE) functions

The SAE Gateway performs the following functions:

Termination of U-plane packets for paging reasons

Switching of U-plane for supporting UE mobility

QoS handling and tunnel management

Long Term Evolution System Overview LTE functions

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



1-3

LTE network components

Overview

Figure 1-1, LTE network components (p. 1-4) describes the LTE network components

and interfaces.

User equipment

The User Equipment (UE) is a combination of Mobile Equipment (ME) and Subscriber

Identity Module / Universal Mobile Telecommunications System Subscriber Identity

Module (UMTS SIM/USIM) with LTE capabilities.

LTE RAN

LTE RAN provides the physical radio link between the User Equipment (UE) and the

Evolved Packet Core (EPC) network. LTE RAN comprises eNodeBs. The eNodeB

contains Transmit Receive Duplex Units (TRDUs) or Remote Radio Heads (RRHs) and

communicates with the UEs. The eNodeB supports Multiple Input Multiple Output

(MIMO).

The eNodeB provides:

Radio resource management: Radio Bearer Control, Radio Admission Control,

Connection Mobility Control, and Dynamic allocation of resources to UEs in uplink

and downlink (scheduling)

S1-MME interface to Mobility Management Entity (MME)

Figure 1-1 LTE network components

Long Term Evolution System Overview LTE network components

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

S1-U interface to Serving Gateway (S-GW)

IP header compression and encryption of user data stream

Routing of user plane data towards S-GW

Scheduling and transmission of paging messages (originated from MME)

Scheduling and transmission of broadcast information (originated from MME or

Operations, Administration, and Maintenance (OAM))

Bearer level rate enforcement and bearer level admission control

Handover support

Evolved Packet Core

The LTE related core network evolution is referred to as Evolved Packet Core (EPC).

LTE architecture is based on the system architecture evolution (SAE) model defined by

the 3G Partnership Project (3GPP). EPC consists of the following network elements:

Mobility Management Entity

The Mobility Management Entity (MME) is the LTE mobility management and session

management entity of the evolved packet core. MME is responsible for selection of the

P-GW, triggering and enabling authentication, and saving the subscriber profile

downloaded from the HSS.

The MME handles signaling traffic from the UE/eNodeB through any of the following:

S1-MME interface

MME talks to other MMEs through the S10 interface

In the evolved packet core, the MME terminates the control plane with the mobile device.

MME is responsible for terminating Non Access Stratum (NAS) signaling such as

Mobility Management (MM) and Session Management (SM) information as well as

coordinating Idle Mode procedures. The MME also includes the gateway selection inter

MME Mobility and authentication of the mobile device.

Serving Gateway

The Serving Gateway (S-GW) is responsible for anchoring the user plane for

inter-eNodeB handover and inter-3GPP mobility. S-GW in LTE terminates the LTE RAN

and a UE that has only one S-GW at any instance. S-GW handles the user data

functionality and is involved in routing and forwarding the data packets to P-GW through

S5 interface.

Packet Data Network Gateway

The Packet Data Network Gateway (PDN-GW) is responsible for IP address allocation to

the UE. The PDN-GW is also the policy enforcement point to enforce Quality of Service

(QOS) specific rules on traffic packets. The PDN-GW terminates the signaling gateway

(SG) interface in evolved packet core network. PDN-GW is responsible for functions


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



1-5

such as policy enforcement based on the traffic monitoring characteristics on a subscriber

by subscriber basis and ensures the appropriate traffic policy. The PDN-GW connects the

UE to external PDNs (Packet Data Networks) and acts as the UE's default router.

Policy Control and Charging Rules Function

The Policy Charging Rules Function (PCRF) is a functional entity of the 3GPP PCC

(Policy and Charging Control) architecture. The PCRF plays a vital role and makes

Quality of Service (QOS) and charging policy decisions. The Home PCRF (HPCRF)

interfaces with the CSCF, it retrieves IMS layer QOS and makes policy decisions. These

policies are passed down to the P-GW, S-GW, and H-SGW for policy enforcement

through the visited PCRF in the regional center.

LTE interfaces

Overview

The Table 1-1, LTE interfaces (p. 1-6) describes the LTE interfaces and communication

between the network elements.

Table 1-1 LTE interfaces

Interface Description

LTE-Uu The LTE-Uu point is between the UE and E-UTRAN. OFDM - based

LTE air interface protocol is used across this interface.

S1-UP The GTP-U protocol interface is between the E-UTRAN and the

Serving Gateway. This interface supports bearer user plane tunneling

and inter-eNodeB path switching during handover.

S1-MME The S1-MME point for control plane protocol interface is between the

LTE RAN and the MME. All signaling between the eNodeB and the

Serving Gateway (S-GW) is carried over this interface.

S3 The S3 interface carries mobility/handover signaling between 2G /3G

and LTE systems. S3 reference points between the SGSN and the

MME.

S6a The S6a interface is between the MME and the HSS. It enables

transfer of subscription and authentication data for authenticating/

authorizing user access to the evolved system between MME and

HSS.

S4 S4 is the user plane counter part of S3. This interface enables user and

bearer information exchange for inter-3GPP access system mobility.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

Table 1-1 LTE interfaces (continued)

Interface Description

S11 The S11 interface is between the MME and the serving gateway. All

control information between the MME and Serving Gateway is carried

over this interface.

S12 The S12 interface introduced in 3GPP Rel-8 supports direct user plane

tunneling between the UMTS RNC and the SGW of the LTE network.

S5 The S5 interface is between the Serving Gateway and the PDN

Gateway. S5 interface is used to move traffic between the two

Gateways.

S7 The S7 interface is between the Evolved Packet Core and the Policy

Charging and Rule Function (PCRF). S7 interface transfers QOS

policy and charging rules from the PCRF to the policy and charging

enforcement function in the PDN gateway.

X2 The X2 interface is the interface between the eNodeBs.

X2-CP The X2-CP traffic supports mobility signaling traffic between two

eNodeBs.

X2-UP The X2-UP supports data forwarded between eNodeBs during the hard

handover procedures.

LTE protocol stacks

Introduction

Protocol stacks have a conceptual model of the layered architecture of communication

protocols in which layers within a station are represented in hierarchical order. Each layer

in the protocol stack is defined in generic terms describing functionality and mode of

operation. The LTE protocol stacks are divided into user plane and control plane.

User plane protocol stacks

The user plane includes the data streams and the data bearers for the data streams. The

data streams are characterized by one or more frame protocols specified for that interface.

Figure 1-2, User-plane protocol stack (p. 1-8) comprises MediumAccess Control

(MAC), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC) and

Physical (PHY) sub layers. Apart from the serving gateway protocols, all radio interface

protocols terminate in the eNodeB on the network side.

Long Term Evolution System Overview LTE interfaces

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



1-7

The LTE user plane protocol performs the following functions:

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.

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, flow

control and concatenation or re-assembly of packets.

Packet Data Convergence Protocol (PDCP) Sublayer : For the user plane, the

PDCP sublayer performs header compression and ciphering.

Control plane protocol stacks

The control plane includes the application protocol. It also includes the signaling bearers

for transporting the application protocol messages. The application protocol is used for

setting up bearers in the radio network layer. For example, radio access bearers or radio

links.

Figure 1-2 User-plane protocol stack

Long Term Evolution System Overview LTE protocol stacks

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

Figure 1-3, Control plane protocol stack (p. 1-9) comprises Radio Resource Control

(RRC), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Medium

Access Control (MAC), Physical (PHY) and Non Access Stratum (NAS) sub layers.

Apart from the non access stratum (NAS) protocols, all radio interface protocols

terminate in the eNodeB on the network side.

The LTE control plane protocol functions are:

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. Along with scheduling, it 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 or demultiplexing of

different RLC radio bearers from the physical layer on transport channels.

Figure 1-3 Control plane protocol stack


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



1-9

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, flow

control and concatenation or re-assembly of packets.

Packet Data Convergence Protocol (PDCP) Sublayer : The PDCP sublayer is

included in the control plane and is used for ciphering and integrity protection. In

addition, PDCP sublayer is used for control plane data transmission. The PDCP

receives PDCP SDUs from the RRC and forwards them to the RLC layer.

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, UE measurement

reporting and control.

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


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

2 2LTE Radio Access Network

Overview

Purpose

This chapter provides information on Long Term Evolution Radio Access Network (LTE

RAN).

Contents

LTE RAN 2-1

LTE RAN interfaces 2-2

LTE RAN

Overview

The eNodeB communicates with the Evolved Packet Core (EPC) using the S1 interface,

specifically with the MME (Mobility Management Entity) and S-GW (Serving Gateway)

using S1 interface. The MME and S-GW are implemented as separate network nodes to

facilitate independent scaling of the control and user plane.

The eNodeB communicates to each other through the X2 interface. For example, support

of handover of UEs in LTE_ACTIVE.

...................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



2-1

LTE RAN interfaces

Overview

LTE contains a radio interface and access network to deliver higher data rates and faster

connection.

S1 interface

The S1 interface is the interface between the LTE RAN and evolved packet core. S1

interface protocol stack is described in Figure 2-2, S1 interface (p. 2-3)

S1 performs the following functions:

S1-UP (user plane)

S1-CP (control plane)

Figure 2-1 LTE RAN interfaces

LTE Radio Access Network LTE RAN interfaces

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

S1-UP (user plane)

The S1 user plane external interface (S1-U) is defined between the eNodeB and the

S-GW. The S1-U interface provides non guaranteed data delivery of user plane Protocol

Data Units (PDUs) between the eNodeB and the S-GW. Transport network layer is built

on IP transport and GTP-U. UDP/IP carries the user plane PDUs between the eNodeB and

the S-GW. AGTP tunnel per radio bearer carries user traffic.

The S1-UP interface is responsible for delivering user data between the eNodeB and the

S-GW. The IP Differentiated Service Code Point (DSCP) marking is supported for QoS

per radio bearer.

S1-MME (control plane)

The S1-MME interface is responsible for delivering a signaling protocols between the

eNodeB and the MME. S1-MME interface consists of a Stream Control Transmission

Protocol (SCTP) over IP and supports multiple UEs through a single SCTP association. It

also provides guaranteed data delivery. The application signaling protocol is an S1-AP

(Application Protocol). The S1-MME is responsible for Evolved Packet System (EPS)

bearer setup/release procedures, the handover signaling procedure, the paging procedure

and the NAS transport procedure. Transport network layer is built on IP transport, similar

to the user plane but for the reliable transport of signaling messages SCTP is added on top

of the Internet Protocol.

X2 interface

The X2 interface is the interface between the eNodeBs. X2 interface protocol stack is

described in Figure 2-3, X2 interface (p. 2-4).

Figure 2-2 S1 interface


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



2-3

X2 performs the following functions:

X2-UP (User Plane)

X2-CP (Control Plane)

X2-UP (User Plane)

The X2-UP protocol tunnels end-user packets between the eNodeBs. The tunneling

function supports the identification of packets with the tunnels and packet loss

management. X2-UP uses GTP-U over UDP or IP as the transport layer protocol similar

to S1-UP protocol. S1-UP and X2-UP use the same U-plane protocol to minimize

protocol processing for the eNodeB at the time of data forwarding. The X2 user plane

external interface (X2-U) is defined between eNodeBs. The X2-U interface provides non

guaranteed delivery of user plane PDUs. The transport network layer is built on IP

transport and GTP-U is used on top of the UDP or IP to carry the user plane PDUs. The

X2-UP interface protocol stack is identical to the S1-UP protocol stack.

X2-CP (Control Plane)

X2-CP has SCTP as the transport layer protocol which is similar to the S1-CP protocol.

The load management function allows exchange of overload and traffic load information

between eNodeBs to handle traffic load effectively. The handover function enables one

eNodeB to handover the UE to another eNodeB. A handover operation requires transfer of

information necessary to maintain the LTE RAN services at the new eNodeB. It also

requires the establishment and release of the tunnels between source and target eNodeB to

allow data forwarding and informs the already prepared target eNodeB for handover

cancellations.

Figure 2-3 X2 interface


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

X2-CP protocol functions include:

intra LTE-Access-System mobility support for the UE

context transfer from source eNodeB to target eNodeB

control of user plane tunnels between source eNodeB and target eNodeB

handover cancellation

uplink load management

general X2 management

error handling

The X2 control plane external interface (X2-CP) is defined between two-neighbor

eNodeBs. The transport network layer is built on SCTP on top of IP. The application layer

signaling protocol is referred to as X2-AP (X2 Application Protocol).

Air Interface

The air interface is the radio-based communication link between the mobile station and

the active base station. LTE air interface supports high data rates. LTE uses Orthogonal

Frequency Division Multiple Access (OFDMA) for downlink transmission to achieve

high peak data rates in high spectrum bandwidth. LTE uses Single Carrier Frequency

Division Multiple Access (SC-FDMA) for uplink transmission, a technology that

provides advantages in power efficiency.

Figure 2-4 LTE air interface


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



2-5

LTE air interface characteristics

LTE air interface characteristics are:

Downlink (DL) based on OFDMA. OFDMA offers improved spectral efficiency

capacity using OFDMA technology.

Uplink (UL) based on SC-FDMA. SC-FDMA is similar to OFDMA for uplink from

hand-held devices such as mobile phones which requires better battery power

conservation.

Supports both FDD and TDD modes:

Provides deployment flexibility in spectrum allocation.

With FDD, DL and UL transmissions are performed simultaneously in two

different frequency bands.

With TDD, DL and UL transmissions are performed at different time intervals

within the same frequency band.

Significant reduction in delay over air interface and idle to active mode transition.

Suitable for real-time applications, for example, VoIP, PoC, gaming, and so on.

Large improvement in uplink spectral efficiency.

Advanced adaptive MIMO support. Balance average/peak throughput,

coverage/cell-edge bit rate.

LTE channel

Channels are used to transport and segregate different types of data across the LTE radio

access network interface.

The various data channels are grouped into three categories:

Physical channels - The physical channels are transmission channels that carry user

data and control messages.

Transport channels - The physical layer transport channels offer information transfer

to MediumAccess Control (MAC) and higher layers.

Logical channels - The logical channels provide services for the MediumAccess

Control (MAC) layer within the LTE protocol stack.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

3 3Architecture

Overview

Purpose

This chapter describes the various components involved in the LTE RAN solution and

their architecture.

Contents

5620 Service Aware Manager (SAM) 3-1

Network Performance Optimizer (NPO) 3-3

eNodeB 3-5

Network Element Manager (NEM) 3-7

Wireless Trace Analyzer (WTA) 3-7

Wireless Provisioning System (WPS) 3-7

5620 Service Aware Manager (SAM)

Overview

The 5620 SAM system is designed to manage Alcatel-Lucent network elements (NEs).

The 5620 SAM manages the following devices in the Alcatel-Lucent portfolio:

IP/MPLS routers and switches

9471 MME, 7750 SR-MG, and 5780 DSC in the LTE ePC space

9412 eNodeB in the LTE RAN space

The 5620 SAM system also supports few telecom devices and provides limited

management of other third-party devices. The third-party devices are know as generic

NEs.

...................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



3-1

5620 SAM system components

The 5620 SAM system has client, server, and database components that are deployed in a

standalone or redundant configuration. Figure 3-1, Standalone 5620 SAM system

(p. 3-2) shows a block diagram of a standalone 5620 SAM system and the network. The

management network contains the 5620 SAM components and connects to the managed

network of NEs from one or more points, depending on the complexity of the

deployment.

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.

The 5620 SAM uses a Java-based technology that provides distributed, secure, and

scalable processing. For more information about the 5620 SAM, see the complete product

documentation available at (http://www.alcatel-lucent.com/myaccess).

Note: If you are a new user and require access to this service, contact your

Alcatel-Lucent sales representative.

Figure 3-1 Standalone 5620 SAM system

Architecture 5620 Service Aware Manager (SAM)

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

Network Performance Optimizer (NPO)

Overview

The 9459 Network Performance Optimizer (9459 NPO) is the main solution for wireless

network optimization provided by Alcatel-Lucent. 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 which supports 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.

NPO without Per Call Measurement Data (PCMD)

NPO without Per Call Measurement Data (PCMD) comprises:

Amain server: This server supports the oracle database and the reporting functions.

An optional QoS auxiliary server: This server hosts the loading process that converts

the 3GPP PM file into a format that can be directly loaded into NPO Oracle tables.

The main server stores the data. The auxiliary server stores the file while they are

being loaded. Backup and restore procedure only applies to the main server. NPO

client are either Windows PC or Windows server running Citrix.

Architecture Network Performance Optimizer (NPO)

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



3-3

Note:

A number of concurrent users can use the analysis desktop application. Usage of

external export interface is not considered in the count of concurrent users.

In case SAM has an auxiliary server, then NPO retrieves PM from the SAM

auxiliary server and CM from the SAM main server.

NPO with Per Call Measurement Data (PCMD)

NPO with Per Call Measurement Data (PCMD) requires:

A connection to MME from both NPO main server and NPO auxiliary servers.

For 12K cells and above, dedicated NPO auxiliary server(s) are required for PCMD.

Figure 3-2 NPO with auxiliary server

Figure 3-3 NPO with PCMD support (48K configuration)

Architecture Network Performance Optimizer (NPO)

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

eNodeB

eNodeB architecture

The eNodeB is an integrated system, composed of a cabinet, a Base Band Unit (BBU),

Transmit/Receive Duplex Units (TRDUs) and Remote Radio Heads (RRHs). Figure 3-4,

eNodeB architecture (p. 3-5) shows the block diagram of a general eNodeB.

From the architecture point of view, two types of eNodeBs are available:

Compact eNodeB

Distributed eNodeB

Figure 3-4 eNodeB architecture

Architecture eNodeB

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



3-5

Compact eNodeB is based on Transmit/Receive Duplex Units (TRDUs), and distributed

eNodeB is based on Remote Radio Heads (RRHs). In both types, the separation between

digital and RF processing is ensured through the CPRI interface. Digital processing is

ensured by the Base Band Unit (BBU), the BBU architecture being the same for compact

and distributed eNodeBs.

Hardware equipments for eNodeB

This topic provides a short description on hardware equipments for eNodeB involved in

LTE RAN solution.

9926 Base Band Unit (BBU)

The 9926 Base Band Unit (BBU) is the Alcatel-Lucent converged product for W-CDMA,

LTE-FDD and LTE-TDD BBU. There are two BBU versions which are known as 9926

BBU V1 (d2U V3) and 9926 BBU V2 (d2U V5). For all common characteristics between

the two versions they are referred to as 9926 BBU.

The 9926 BBU is a digital NodeB with four types of hardware boards:

eCCM-U (with MDAE1/T1 or GE or T3) (1 module only)

eCEM-U (up to 3 modules)

RBP

RUC

9442 Remote Radio Head (RRH)

The Remote Radio Head (RRH) is a platform asset that can support both 3G (WCDMA

and CDMA) and 4G (LTE and WIMAX-FDD) technologies. This unit can also operate as

a single Tx unit for both single and dual sector configurations. The unit has 2 RF

transceivers to enable 2x2 MIMO applications.

9412 Compact

The 9412 eNodeB is an integrated system. However, logically it is the same as a

distributed eNodeB with a separation of the digital and RF processing by a CPRI

interface. There are two types of 9412 eNodeB compact systems; indoor and outdoor. The

9412 eNodeB Compact indoor system is designed to support LTE service in the 700 MHz

spectrum. This system is housed as an integrated system, all in one cabinet, serving 5 or

10 MHz LTE bandwidth carriers in the 700 MHz spectrum.

The standard 9412 eNodeB Compact outdoor comprises of the following two cabinets.

These cabinets are physically identical, but provide different functionality.

BB (Baseband) cabinet

RF (Radio Frequency) cabinet

Architecture eNodeB

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

Network Element Manager (NEM)

Overview

The Network Element Manager (NEM) application is instantiated in the Local

Maintenance Terminal (LMT) of the related eNodeB and in the 5620 SAM. The LMT is

connected locally to the eNodeB. For example, a portable PC connected directly to the

eNodeB using a 10/100 Base-TX Ethernet interface.

The NEM is used for monitoring, maintaining and commissioning the eNodeB. NEM

uses SNMP v3 for communication with eNodeB. NEM also supports NETCONF as NEM

supports modifying the eNodeB Netconf parameters.

Wireless Trace Analyzer (WTA)

Overview

9958 Wireless 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.

9958 WTA is used to analyze call trace data for the following NEs:

eNodeB (eNB)

9471 MME

Wireless Provisioning System (WPS)

Overview

The 9452 Wireless Provisioning System (9452 WPS) is a powerful tool suite that

simplifies the provisioning and 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 towards further plug-and-play, self- organizing, self-optimizing networks

associated with the 9452 WPS delivers much more simplified operational system.

For information on WPS software installation procedures, see Alcatel-Lucent 9952

Wireless Provisioning System Software Installation Procedure, 418-000-200.

Architecture Network Element Manager (NEM)

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



3-7

Architecture Wireless Provisioning System (WPS)

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

4 4LTE RAN OAM functions

Overview

Purpose

This chapter provides information on OAM functions.

Contents

Fault management 4-1

Configuration management 4-15

Performance management 4-29

Security 4-46

Call Trace 4-46

Self Optimizing Network (SON) 4-47

Transport call admission control 4-48

Fault management

Overview

The Fault management tasks are monitoring tasks that detect and analyze hardware,

software and network problems to execute corrective maintenance procedures according

to the type of alarm. The FM tasks detect failures as soon as they occur and limit their

impact on the network Quality of Service (QoS).

The monitoring levels available in the LTE RAN are:

Network-level monitoring

Element-level monitoring

Service-level monitoring

...................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



4-1

Fault Management concepts

The functions of Fault Management are:

Alarm surveillance (p. 4-2)

Fault localization (p. 4-2)

Fault correction (p. 4-2)

Testing (p. 4-3)

Alarm surveillance

Alarm surveillance function detects faults in a network. It monitors and interrogates

Network Elements (NE) about events or conditions. Event data is generated by an NE

when an abnormal condition is detected.

Table 4-1, Fault types (p. 4-2) lists the different types of faults that occur in a network.

Table 4-1 Fault types

Type Description

Hardware faults Malfunction of physical resource within the

network element.

Software faults Malfunction of software component (software

bug or database inconsistency).

Functional faults Failure of a functional resource in the NE and

no hardware component has been detected as

faulty.

Overload conditions Loss of some or all of the specified

capabilities of an NE due to overload.

Quality of service failures Failure to meet the given threshold values.

Communication failures Communication failure between NEs, between

the NE and the operating system (OS), or

between operating systems.

Fault localization

Fault localization function determines the root cause of a fault. Additional failure

localization routines provide information which must be added when the initial failure

information is insufficient for fault localization. The routines can employ internal or

external test systems and can be controlled by a Network Element Manager (NEM).

Fault correction

Fault correction function takes the appropriate action to correct a fault once the root cause

is identified. It transfers data concerning the repair of a fault. This function also controls

procedures that use redundant resources to replace equipment or facilities that have failed.

LTE RAN OAM functions Fault management

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

Testing

Testing conducts tests to determine the root cause of a fault. To analyze the problem,

access the relevant functionality of the NE using the Network Element Manager to

conduct tests.

General problem solving model

The general problem solving model provides a general approach for troubleshooting

situations. The stages for the general problem solving workflow are:

...................................................................................................................................................................................................

1 Define the problem.

When analyzing a network problem:

Make a clear problem statement.

Define the problem in terms of a set of symptoms and potential causes.

To analyze the problem, identify the general symptoms and ascertain what kinds of

problems (causes) could result in these symptoms.

...................................................................................................................................................................................................

2 Gather the facts.

Gathering facts involves:

Collecting information from affected users, network administrators, managers and

other key people.

Collecting information from sources such as network management systems, protocol

analyzer traces, serial line traces, stack dumps or software release notes.

...................................................................................................................................................................................................

3 Consider the possibilities.

This stage involves:

Eliminating problems in the network.

Narrowing the number of potential problems.

...................................................................................................................................................................................................

4 Create an action plan.

The action plan is based on the remaining potential problems.

...................................................................................................................................................................................................

5 Implement the action plan.

...................................................................................................................................................................................................

6 Observe the results.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



4-3

...................................................................................................................................................................................................

7 If the problem remains unsolved then return to Stage 2.

Fault management process

The Fault management stages in 5620 SAM are:

...................................................................................................................................................................................................

1 Receive notification from eNodeBs in the network.

The eNodeBs in a network generate the following types of notifications:

Events inform the operator of a non-continuing occurrence of interest. An event is

never cleared by the NE.

Alarms are used by the NE to raise or clear alarms on logical or hardware

components.

State changes are used by the NE to notify the change of states on a Managed Object

(MO). For more information on state changes, see Table 4-2, State types (p. 4-5).

The 5620 SAM gathers these notifications using SNMPV3 traps. Each alarm/event has a

unique ID. Each MO class is assigned a range of alarm IDs so that two different MOs do

not raise the same alarm.

...................................................................................................................................................................................................

2 Sort notifications.

The Node Manager layer of the 5620 SAM sorts the following notifications:

Alarms are stored in the 5620 SAM database and include the following information:

alarm ID, alarm name, alarm severity, alarm type, probable cause, timestamp,

managed object and additional text. A visual display of object alarm status is done in

equipment tree and network map.

Events are stored in the 5620 SAM database and include the following information:

alarm ID, alarm name, alarm type, probable cause, timestamp, managed object and

additional text.

State changes are stored in the 5620 SAM database. The new state is displayed in the

equipment management and in the supervision view beside the corresponding

managed object.

...................................................................................................................................................................................................

3 Display the Alarms and State changes in the Supervision windows.

Maintenance states

This topic defines the maintenance states that apply to LTE RAN managed objects (MO)

and resources and the valid values for those maintenance states.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

Table 4-2, State types (p. 4-5) lists the different states of MO that occur in a network.

Table 4-2 State types

State type Description States Meaning

Administrative

state

Administrative state

indicates whether the

use of an MO by the

NE is allowed or not.

This state is set by the

operator either from

SAM or NEM.

Unlocked Use of MO is permitted.

Locked Use of MO is prohibited.

Indetermi-

nate

NEM/SAM is unable to compute the

state.

Operational

state

Operational state

indicates whether an

MO is installed and is

working or not. This

state is determined by

the eNodeB and cannot

be changed by the

operator.

Enabled MO is either fully or partially

operational.

Disabled MO is inoperable.

Availability

state

Availability state

qualifies the

operational state. This

state is determined by

the eNodeB based on

the operational state

and cannot be changed

by the operator.

Empty (0) None of the available states or

combination of states are present.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



4-5

Table 4-2 State types (continued)


Powered

off (1)

The resource is powered off. The

operational state is disabled.

In test (2) The resource is undergoing a test

procedure. The operational state can

be either enabled or disabled.

Faulty (4) The resource has an internal fault but

is able to operate. The operational

state is enabled.

Degraded

(8)

The service available from the

resource is degraded. The operational

state is enabled.

Depen-

dency (16)

The resource cannot operate because

another resource, on which it depends,

is not available. The operational state

is disabled.

LogFull

(21)

This indicates a log full condition, the

semantics of which are defined in

CCITT Rec. X.735.

NotIn-

stalled (22)

The resource represented by the MO

is not present, or is incomplete. For

example, a plug-in module is missing,

a cable is disconnected or a software

module is not loaded. The operational

state is disabled.

OffLine

(23)

The resource requires a routine

operation to be performed to place it

online and make it available for use.

The operation may be manual or

automatic, or both. The operational

state is disabled.

OffDuty

(24)

The resource has been made inactive

by an internal control process in

accordance with a predetermined time

schedule. Under normal conditions

the control process can be expected to

reactivate the resource at some

scheduled time, and it is therefore

considered to be optional. The



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




418-000-012 Release LA4.0

Issue 1 March 2012

Table 4-2 State types (continued)


Failed (32) The resource has an internal fault that

prevents operation. The operational

state is disabled.

Initializing

(64)

The resource is initializing. The


x Combination of errors. For example,

33 means powered off and failed. The

operational state depends on status.

Communica-

tion state

Communication state

indicates which

manager (SAM or

NEM) can modify the

eNodeB configuration.

This state is set only

by the operator

through the NEM.

Reachable Indicates that the SAM/NEM can

reach the NE. Configuration changes

are possible from the SAM and NEM.

Unreach-

able

Indicates that the SAM/NEM cannot

reach the NE. Configuration changes

are possible only from NEM. Changes

from the SAM are rejected by

eNodeB.

Indetermi-

nate

NEM/SAM is unable to compute the

state.

Network resource and service supervision

The following functions are available from the 5620 SAM GUI for supervision of LTE

RAN resources and services:

A visual display of object alarm status is available in equipment tree and network

map.

Alarms can be viewed in the Alarm window.

Details of a specific alarm can be viewed.

The managed object state can be viewed in the equipment management view and in

the network map view beside the corresponding managed object.

Detailed information about network elements can be viewed in the equipment

management view.

eNodeB equipment problems can be troubleshot with the integrated Network Element

Manager (NEM).


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................


418-000-012 Release LA4.0

Issue 1 March 2012



4-7

Alarm management

In the 5620 Service Aware Manager (SAM), fault management is based on the retrieval

and analysis of unsolicited messages sent by the NEs or OAM applications. An

unsolicited message is a message that the NEs or the OAM applications issue

spontaneously concerning software or hardware faults and state and attribute value

changes. The resulting notifications and alarms warn users of NE malfunctions and

inform them about internal system operating changes. OAM maintenance tasks are based

on notifications

Date post:	17-Sep-2015
Category:	Documents
Upload:	amber-wilkerson
View:	77 times
Download:	19 times

LTE Ran Lucent

Documents