ENB Hands-On Training for Trial (RL15TD)

RA4155-02A RL15TD eNB HOT LTE/EPC overview1 Nokia Siemens Networks

LTE/EPC OvervieweNB Hands-on Training for Trial (RL15TD)


Nokia Siemens Networks Academy

Legal notice

Intellectual Property Rights

All copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session for development of groups without the prior written agreement of Nokia Siemens Networks.


Content


data rates

< 1 Gbps

mobility

GSM/IS95

AMPS

WCDMA/cdma2000HSPA LTE

802.11a/b/g802.11a/b/g

< 100 Mbps< 50 Mbps< 10 Mbps< 1 Mbps< 200 kbps

time

2010200520001990

HIGH

LOW

History and Future of Wireless

1G

2G

3G 3G Enhacements 3G Evolution

802.11 802.11nWLAN Family

WiMAX Family

802.16e

Mobile WiMAX

802.16e

Mobile WiMAX802.16a/d

Fixed WiMAX

802.16a/d

Fixed WiMAX


NSN Network Architecture Evolution

Node B RNC SGSN GGSN

Internet

3GPP Rel 6 / HSPA

Direct tunnel

3GPP Rel 7 / HSPA

Internet

Node B RNC

SGSN

GGSN

Direct tunnel

3GPP Rel 7 / Internet HSPA

Internet

Node B

SGSN

GGSN

Node B

(RNC Funct.)

Direct tunnel

3GPP Rel 8 / LTE

Internet

Evolved Node B

MME

SAE GW


LTE/EPS Network Architecture Subsystems

LTE/EPS architecture is driven by the goal to optimize the system for packet data transfer.

No circuit switched components

New approach in the inter-connection between radio access network and core network (S1 interface)

The EPS architecture is made up of an

EPC (Packet Core Network, also referred

as SAE) and an eUTRAN Radio Access

Network (also referred as LTE)

The EPC provides access to external

packet IP networks and performs a number

of CN related functions (e.g. QoS, security,

mobility and terminal context management)

for idle (camped) and active terminals

The eUTRAN performs all radio interface

related functions

IMS/PDN

EPC

eUTRAN

LTE-UE

EPS


Basic Network Architecture

MME

SGW

IMS

Internet

Companyintranet

SAE-GW

LTE-UE eNB

eNB

HSS

PCRF

PGW

X2 S1-MME

S1-U S5/S8

S11Gx

Rx+

SGi

S6a

Uu

eUTRAN EPC

Control plane path

User data path


LTE/EPS Mobility Areas

Two areas are defined for handling of mobility in LTE/EPS:


Tracking Areas

S-eNBTAI3

TAI3TAI3

TAI3

TAI3TAI3

TAI3

MME

HSS

eNB

TAI2

TAI2TAI2

TAI2

TAI2

TAI2

TAI2

TAI2

TAI1

TAI1TAI1

TAI1

TAI1eNB 1 2

MME

3

Cell Identity

Tracking Area


LTE Mobility & Connection States


LTE/EPS Bearer: Identity & Architecture

cell

S1-ULTE-Uu S5/S8

PDN

SGieNB Serving

GatewayPDN

Gateway

E-UTRAN EPC PDN

An EPS bearer identity uniquely identifies an EPS bearer for one UE. The EPS Bearer Identity

is allocated by the MME.

LTE/EPS Bearer spans the complete network, from UE over EUTRAN and EPC up to the

connector of the external PDN.

The SAE bearer is associated with a quality of service (QoS) usually expressed by a label or

QoS Class Identifier (QCI)

LTE-UE

End-to-End Service

EPS Bearer External Bearer

Radio Bearer S1 Bearer S5/S8 Bearer


The Default Bearer Concept

Each UE that is attached to the LTE network has at least one bearer available, that is called the default bearer.

Its goal is to provide continuous IP connectivity towards the EPC (always-on concept)

From the QoS point of view, the default bearer is normally a quite basic bearer

If an specific service requires more stringent QoS attributes, then a dedicated bearer should be established.

cell

S1-U

UE

S5PDN

Sgi

eNB

Serving

Gateway

PDN

Gateway

Default EPS Bearer

MME

S1-MME

S11


EPS Bearer QoS Attributes

EPS Bearer QoS Parameters

(To be defined per Bearer)

Default Bearer/Dedicated Bearer

GBR/N-GBR

MBR

UL/DL-TFT

QCI

ARP

EPS Bearer QoS Parameters

(To be defined per User) AMBR


QoS Class Identifier (QCI) Table in 3GPP

GBR1

Guarantee Delay budget Loss rate ApplicationQCI

GBR

100 ms 1e-2 VoIP

2

GBR

150 ms 1e-3 Video call

3

GBR

300 ms 1e-6 Streaming

4

Non-GBR 100 ms 1e-6 IMS signalling5

Non-GBR 100 ms 1e-3 Interactive gaming6

Non-GBR 300 ms 1e-6TCP protocols : browsing, email, file download

7

Non-GBR 300 ms 1e-68

Non-GBR 300 ms 1e-69

Priority

2

4

5

1

7

6

8

9

50 ms 1e-3 Real time gaming3


EMM & ECM States Transitions

EMM_Deregistered

ECM_Idle

Power On

Registration (Attach)

EMM_Registered

ECM_Connected

Allocate C-RNTI, S_TMSI

Allocate IP addresses

Authentication

Establish security context

Release RRC connection

Release C-RNTI

Configure DRX for paging

EMM_Registered

ECM_Idle

Release due to

Inactivity

Establish RRC Connection

Allocate C-RNTI

New TrafficDeregistration (Detach)

Change PLMN

Release C-RNTI, S-TMSI

Release IP addresses

Timeout of Periodic TA

Update

Release S-TMSI

Release IP addresses


E-UTRAN Functionalities 3GPP TS 36.401

Evolved

Node B

(eNB)cell

LTE-Uu

LTE-UE


NSN LTE / EPC Portfolio


Flexi Multiradio BTS LTE

Remote RF Head Solution for RL15TD:

System module

RRH for RF function, one per sector/cell

Feederless & distributedRemote RF Module

System Module

OBSAI RP3-01 optical

Antenna

GPS Receiver


FlexiBTS Product Differences between FDD&TDD

Remote Radio Head2 Path or8 path (beamforming)

System Module


Antenna

GPS Receiver

FCMDTransport Block

FSPC BB cardFSPC BB cardFSPC BB card

RF feeder

Antenna

GPS Receiver

System Module

RF Module

FDD/RL25TD: RF Module Solution

Near the System Module

TDD: Remote Radio Head Solution

Near the Antenna (RL05/15)


Flexi Network Server


Flexi Network Gateway

1 Nokia Siemens Networks RA4155-02A RL15TD eNB HOT TD-LTE FlexiBTS Hardware

TD-LTE Flexi BTS HardwareeNB Hands-on Training for Trial (RL15TD)



Legal notice




Contents

Introduction to the FlexiBTS architecture

FlexiBTS installation options

Description of TD-LTE FlexiBTS modules and sub-modules


Evolved Packet Core (EPC)

PCRFHSS

User planeControl plane

TD-LTE Radio Access Network

MME

Serving

GW

PDN

GW

IMS

Services in Packet Data Network

Internet

Operatorservices

Companyintranets

eNodeB

3GPP Rel 8 network architecture

SAE-GW


NSN TD-LTE Flexi BTS structure overview

Flexi BTS introduces a new platform

The modular design doesnt use any backplanes

Modules are interconnected through front panel cabling

Modules can be installed separate from each other (Feederless / Distributed Sites)

A TD-LTE Flexi BTS consists of one System Module and

1 optional Extension System Module

up to three Remote Radio Heads or a Radio Module

Radio Module is available with 3 Power Amplifiers (PAs)

each PA contains one up to 20 MHz carrier

Remote Radio Heads are optimized for 1 sector with

2 PAs with up to 20 MHz bandwidth

BTS configurations

up to 1+1+1 with 20 MHz

Module weight: 19-25 kg per Module

The Base Station can be installed by one person


Generic FlexiBTS Product Description

Remote RF Module

System Module


Antenna

GPS Receiver

FCMDTransport Block

FSPC BB cardFSPC BB cardFSPC BB card

RF Feeder

Antenna

GPS Receiver

System Module

RF Module

#2. RF Module Solution

Near the FSM

#1. Remote RF Head Solution

#3. RF Module Solution

Near the antenna is not showed!!


BTS SystemModule

Remote RF Head

Flexi BTS Build Up by Modules

OptionalExtension System

Module

AC-> DC BBU

AC (Optional)

SYSTEM MODULE:- C-plane processing + centralised timing- U-plane processing + multiplexing & summing- Ethernet switching- Transport processing- External interfaces- Power Distribution

Remote RF Head:- Modulator- Channelizer- Analog RF processig- Power Amplifier (integr.)- Antenna filter (integr.)

Optical interfaces betweenthe modules

BBU=Battery Backup Unit

Near the antenna, outdoor

Installed in stack or in cabinet, indoor

Remote RF Head

Remote RF Head


Optional

TMA/MHA Optional TMA/MHAs

Optional AC/DC + Battery

Multimode System Module

Two 3-sector RF Modules

Example TD-LTE Flexi BTS Site(RF Module Solution) System Module

Two 3-sector RF Modules for 3 sectors

1+1+1 @ 3 x 120 W 2TX MIMO

Optional 4 way UL diversity

Ultimate capacity with 3x120 W MIMO 2TX

Sector 1

Sector 3

Sector 2

Tx1/RX1

Tx2/RX2

RX3

RX4


Installation options: Pole installation of Remote Radio Heads (RRH)

up to 3 RRHs fit around one pair of FPKA pole mounting brackets.


Installation options: Stack installation

BTS modules are placed in a stack (e.g. floor or shelves)

Outdoor & indoor installations

Modules in casings with back and front covers

Plinth needed (same plinth for all cabinet less installations stack, pole and wall)

Max 22 Height Units (HU) per plinth for zone 2 earthquake zones, max 15 HU for zone 4 earthquake zones


Installation options: Wall installation

BTS modules installed on a wall



Plinth needed

Up to 2 modules per plinth

Modules installed covers sideways

100 mm space recommended between plinths to enable cabling (see picture)

Standard Flexi BTS clearances apply


Installation options: Pole installation of Modules

BTS modules installed on a pole



Plinth and pole mounting bracket needed

Up to 2 modules per plinth and 4 per pair of brackets

Modules installed covers sideways

Standard Flexi clearances apply


Installation options: Flexi Cabinet installation

Cabinet can simultaneously house LTE, GSM/EDGE, LTE/HSPA and BBU modules

There are no limitations on how to mix LTE, GSM and WCDMA in one cabinet

Optional Flexi Cabinets for indoor and outdoor installations

Open 19 mechanics with 1 HU fixing steps for flexible module installations

No motherboards or electronics (fans etc)

Not part of EMC shielding

Only front cabling

Module casings and covers are not used

Cooling fans remain in modules

Modules are grounded via rack

Same footprint and cabinet fixing points as with UltraSite and Talk Family

Outdoor: 1550 x 770 x 770 (H x W x D), space for 38HU

Indoor: 1800 x 600 x 600 (H x W x D), space for 36HU

Flexi BTS Outdoor CabinetFCOA

Flexi BTS Indoor CabinetFCIA


133 mm

3 HU

422 mm

without covers

560 mm

with covers447 mm

for 19 inch rack installation

Weight: 19-25 kg

NSN Flexi LTE BTS Modules


NSN Flexi BTS System Module

The Flexi System Module hosts the

telecom control

system operation and maintenance

baseband application

transmission

power distribution functionality.

The following versions of the System Module are available:

Multi-Mode System Module versions supporting LTE (TDD/FDD) and WCDMA

operation:

Multimode System Module FSMD

Multimode System Module FSME


Flexi Multimode System Module FSME

High Capacity with FSME

FSME

HW Capacities with 2 TX MIMO and 2 RX

Bandwidth MHz 5 (or less) 10 20 (or 15)

Capacity with FSME 12 cells 6 cells 3 cells

Peak L1 DL Throughput per cell 37 Mbit/s 75 Mbit/s 150 Mbit/s

Peak L1 UL Throughput per cell 12 Mbit/s 25 Mbit/s 50 Mbit/s

FSME

HW Capacities with 2 TX MIMO and 2 RX

Bandwidth MHz 5 (or less) 10 20 (or 15)

Capacity with 2 x FSME 24 cells 12 cells 6 cells

Peak L1 DL Throughput per cell 37 Mbit/s 75 Mbit/s 150 Mbit/s

Peak L1 UL Throughput per cell 12 Mbit/s 25 Mbit/s 50 Mbit/sFSME

Capacity Enhancement with extension FSME

FSME

* FTLB transport sub-module required if transport dimensioned according to peak data rates


Interfaces and alarms

Description (For LTE)

Bandwidth: Up to 20 MHz/sector

RF units supported: 3

Can be connected to LTE and 3G

For outdoor pole/wall mounting (IP 65)

Weight = 48.5 lbs (22 kg)

Volume = 25 liters(h x w x d) [mm] (133x447x422)

Temp. Range -31 +131 F

Power consumption 150 W (typical)

Power supply DC -48 V

Overview Optical OBSAI RP3-01 interfaces to RRH

(RF Modules)

Integrated BB and BTS Control

Integrated Transport: FTLB Module

2 Electrical, 1 Optical GE Ports

For trial electrical interface is planned

BTS site external alarms and controls

Ext Synchronization out and input

Redundant integrated fans

Flexi Multimode System Module (FSME)

Multi-standard System Module for LTE and 3G

FTLB Transport Module


Exploded view of System Module delivery items


FSMC/D/E SYSTEM MODULE INTERFACES 1/2


Variable transmission interfaces8 x RJ-48/16 x SMB/2 x TNC/1 x duplex LC connector

2 x RJ-45 connector

1x GE via SFP transceiver

Transmission interfaces

GroundingScrew M5Grounding

Power feedTX25 screw terminals for 8 25 mm2cableDC input

System and baseband extension interfacesDuplex LC connectorOPT-EXT 2

System and baseband extension interfacesDuplex LC connectorOPT-EXT 1

Interface for RF Module 3Duplex LC connectorOPT-RF 3



BTS synchronization input interface (for external sources)MDR26 connectorSync in

BTS synchronization output interfaceMDR14 connectorSync out

External alarms and controlsMDR36 connectorEAC

External transport equipment interface (for I-HSPA Adapter)RJ-45 connector1000 Eth ETP

Control and location data transferRJ-45 connector10/100/ (1000 for Rel. 2) Eth OVP1)

Site support control over IP/site support hard-wired alarmsRJ-45 connector10/100/ (1000 for Rel. 2) Eth FPMA

For local management toolRJ-45 connector10/100/ (1000 for Rel. 2) Eth LMP

Power delivery to System Extension Module operating in BB-ext

mode and to the main fuse for System Modules. Fuse rating

25A. Can be used for I-HSPA and GPS mediator (FSEG).

Multi-beam XL power supply connectorPower supply System Extension Module

operating in BB-ext mode

Power delivery to RF3. Fuse rating 20A.

Recommended for I-HSPA use. Can be used for GPS mediator

(FSEG).

Multi-beam XL power supply connectorPower supply RF module 3

Power delivery to RF2. Fuse rating 20A.Multi-beam XL power supply connectorPower supply RF module 2

Power delivery to RF1. Fuse rating 20A.Multi-beam XL power supply connectorPower supply RF module 1

PurposeTypeConnector

SYSTEM MODULE INTERFACES 2/2


FSMD/E Functional Block

FSPC 1 FSPC 2 FSPC 3

FCMD

FSME only


FCMD Functionalities

FCMD -- Flexi Control and Multiplexing Sub-Assembly, version D

Takes care of controlling of System Module O&M features for FTM and FSPCs

intelligence temperature control,

clock distribution to the BTS

baseband- and RF-synchronization

power distribution

Platform for user plane resource manager, optical interfaces to/from another modules and summing&multiplexing for baseband pooling


FSPC Functionalities

FSPC Flexi Signal Processor, version C

User plane signal processing including L1 and part of L2

Frame protocol termination

Radio link signalling

Local O&M

Boot SW download fail recovery


FSPC 3

FSPC 2

FSPC Functional Block

CPU

1

CPU

2

CPU

3

Faraday

DSP 1

CPU

1

CPU

2

CPU

3

Faraday

DSP 2

CPU

1

CPU

2

CPU

3

Faraday

DSP 3

CPU

1

CPU

2

CPU

3

Faraday

DSP 4

CPU

1

CPU

2

CPU

3

Faraday

DSP 5

CPU

1

CPU

2

CPU

3

Faraday

DSP 6

CPU

1

CPU

2

CPU

3

Faraday

DSP 7

FSPC 1

FSPC Flexi Signal Processor version C

DSP Digital Signal Processor

Faraday Manufacturer name


Power Distribution and Fuses module (FPFB)

Type label

FPFB

DC Input Connector


FPFB Interfaces


FPFB functionality

Remote controlled, output disabledYellow, blinking

Fault, output disabledRed

Normal operation, output enabledGreen

Stand-by, output disabled manuallyYellow

IndicationLED colour

FPFB LED indication:

The FPFB does not have any circuit breakers but instead electrical fuses and a dedicated power switch for the System Module.

There are five membrane switches on the FPFB front panel for the outputs. The switches control power control circuits and have two states: On and Stand-by.

This allows to individually connect or disconnect the power supply from each of the max 5 modules:

System Module

RF Module / RRH 1

RF Module / RRH 2

RF Module / RRH 3

Extension System Module

The fuse rates for the FPFB are RF1-3 31.0A (+/-2A), EXT 25.0A (+/- 4.5A)


Flexi System Module + Transport sub-module

FTM is the integrated transmission

module of the FlexiBTS

It is mechanically and electrically

connected to the System Module of

the FlexiBTS


FTLB - PDH / Ethernet

LTE - is ready for LTE by software upgrade

Interfaces

2 x electrical Gigabit Ethernet, RJ45 (10/100/1000Base-T)

1 x optical Gigabit Ethernet, via optional SFP (e.g. for 1000Base-SX/LX)

4 x E1/T1/JT1 symmetrical, RJ48 (coaxial E1 supported via baluns)

Data throughput

2 Gbit/s UL+DL

Connector types

E1: 1 x RJ 48 per IF

Ethernet: RJ 45

opt. Ethernet: SFP with LC connector

SFP slot


FTIB - PDH / Ethernet

LTE - is ready for LTE by software upgrade

Interfaces

2 x electrical Gigabit Ethernet, RJ45 (10/100/1000Base-T)

1 x optical Gigabit Ethernet, via optional SFP (e.g. for 1000Base-SX/LX)

4 x E1/T1/JT1 symmetrical, RJ48 (coaxial E1 supported via baluns)

Data throughput

160 Mbit/s UL +DL

Connector types

E1: 1 x RJ 48 per IF

Ethernet: RJ 45

opt. Ethernet: SFP with LC connector

SFP slot


Remote Radio Head

with cover

and

mounting kit

AXIS

FZNB/FZHB

naked


Remote Radio Head Functional Blocks (FZNB/FZHB)

FZNB: 2300 2TX 20+20W

FZHB: 2600 2TX 20+20W


Interfaces


Bandwidth: 20 MHz

Output power 20W+20W

2 Rx and 2 Tx paths

For outdoor use/ pole and wall mounting (IP 65)

Weight = 36.3 lbs

Volume < 20 liters



Temp. Range -35 +55 C

Mechanical target design (Typical)

Interface: OBSAI

RET support (AISG & 3GPP)

External equipment alarm & control

MIMO Remote Radio Head (20 W+20 W)

Best MIMO RF performance with one RF Head per sector

MIMO Remote Radio Head

20 W TX2& Div RX

20 W TX1& RX

ANT


Remote Radio Head Interfaces (FZNB/FZHB)


Several kinds of RRH/RF module used in TD-LTE

Limited customer trials (China)

RL15TD8x582570-262010/20FZHD

Limited customer trials (China)

RL25TD8x1082600FZHA

RL25TD4x1062300-2400Up to 40

FZNC

Limited customer trials (Japan)

RL25TD42545-2575FZOB

RL15TD

RL15TD

RL15TD

RL15TD

RL05TD

Release

ALL MARKETS20+2022545-263010/20FZHB

Limited customer trials (Japan)

8x582545-257510/20FZOA

Limited customer trials

8x582496-269010/20FZHC

20+20

10+10

Tx Power (W)

10/20

10/20

BW (MHz)

ALL MARKETS22300-2400FZNB

-22300-2400FYRN

MarketsNo. of TX

Band (MHz)Type


Interfaces


Bandwidth Up to 20 MHz

Output power 40 W @ antenna conn. for trial version, 60 W for commercial version

2 Rx and 1 Tx paths per Carrier

For outdoor use/ pole and wall mounting (IP 65)

Weight = 51.3 lbs (23,3 kg)

Volume = 25 liters(h x w x d) [mm] (133x447x422)



Temp. Range -31 +131 F

Mechanical design (Typical)

Interface: OBSAI

RET support (AISG & 3GPP)

External equipment alarm & control

Flexi 3-Sector RF Module

The most cost and size optimized 3-sector configuration

Sector 3

Div Rx Tx/RxSector 2

Div Rx Tx/RxSector 1

Div Rx Tx/Rx


Flexi Power Module FPMA

Example configuration with:

1 x Flexi Power Module FPMA

3 Flexi Power AC/DC sub-modules FPAA (230VAC -> 48VDC)

1 Flexi Power Battery FPBA

+

-

48VDC

output to

BTS

AC input

cabling to

FPMA

AC feed to

FPAA

(3pcs)


Flexi Power Module FPRA

High power alternative to FPMA

Up to 3 rectifiers

Output power 2 kW per rectifier, 6 kW total DC output power

External batteries supported


Converts nominal 24 V DC input voltage 53-55 V DC output voltage

A maximum of two FPDA modules can be connected in parallel

Integrated self-controlled fan

Maximum DC output power is 2 kw

Flexi Power DC/DC Module (FPDA)


GPS for Flexi eNB (FYGA)

Trimble Acutime Gold: GPS antenna with inbuilt receiver

Available with Flexi LTE BTS, Flexi WCDMA BTS, Flexi I-HSPA BTS

Flexi BTS System Module

Flexi BTS RF Modules /

power supply Module

connected to Synch In


Flexi mounting kit for floor, wall and pole (FMFA)

Plinth FMFA 101...103

Fixing adapters

Plinth FMFA 104


Flexi External Alarm Box (FSEB)

Extending the Flexi BTS alarm connector to

support up to 24 alarm interfaces.

12 alarms are supported for Flexi LTE BTS.

Support for the fire detector

IP55 protection

11 Nokia Siemens Networks RA4155-02A RL15TD eNB HOT Commissioning and Integration

Flexi Multiradio LTE BTSCommissioning and IntegrationeNB Hands-on Training for Trial (RL15TD)



Legal notice




Module Contents

BTS SiteManager Installation

Manual BTS SW update

Manual BTS Commissioning

Integration


Flexi Multiradio LTE BTS Commissioning

Start

Power On

Autoconnection

Enabled

Autoconfiguration

Enabled

SW Update

Commissioning file

download from

iOMS

Site reset

Commisisoning

tests (optional)

Integration

Local Connect

Remote

Connect

SW Update

Commissioning

File?

Planned Template Manual

Enter site-specific

parameters

Enter all

parameters

Site reset

Commissioning

Report

Done

Yes

Yes

No

No

Autoconfiguration

Report

Complete Template None

Commisisoning

tests (optional)

4


LTE BTS Site Manager Requirements

Item Specification

Processor Minimum: 1 GHz

Recommended: 1.7 GHz

Memory Minimum: 512 MB

Recommended: 1 GB

Hard disk space 260 MB

Ethernet connection 10/100/1000 Mbit/s Ethernet card

Communication cable (10baseT Ethernet

cable with RJ-45 connector)

Display 1024x768

Pointing device Mouse, touch pad, track ball or equivalent

with 2 click buttons

CD-ROM drive (for installation) optional

Printer optional

Operating syste Microsoft Windows 2000/XP/Vista/7

Windows Server 2003

Red Hat Enterprise Linux 4 ES GNOME

desktop.

5


LTE BTS Site Manager Installation

6

Normally we recommend to

keep the older versions

when installing a new BTS

Site Manager. The more

BTS Site Manager versions

are installed the less likely is

an incompatibility issue with

BTSs running on various

SW levels.


Launching BTS Site Manager

PC Setting for Local Connection

7


Launching BTS Site Manager

If connecting remotely,

enter Management Plane

IP address of the BTS.

Remote connection to an

un-commissioned BTS will

not be available, because

no MP IP address has

been configured yet.

8


If there is no any signed certificate installed on the BTS it is required

during the Authentication phase to accept self-signed BTS certificate.

Accept self-signed Certificate

9


Verify BTS Software Level

active SW

running in the

FSMx

active SW

running in the

RRH

active SW

running in the

FTM


Software Update via BTS Site Manager

11

File selected was

LNT1.0_ENB_1010_066_07_release

_BTSSM_downloadable.zip, BTSSM

decompresses and selects the

TargetBD file which points to

necessary binaries for this release.

SW update takes

approximately 20 minutes,

depending on number of

files updated and bandwidth

of DCN connection


Manual Commissioning


Commissioning Options

13


Site Commissioning File (SCF)

14


Site Commissioning File Creation

15


HW Selection

Select

correspondent

FSMx, FTM and

RRH HW


E-UTRAN Cell Identifier

EUTRAN-CGI

20 bits correspond to eNB ID (parameter LNBTS-id) 8 bits lcrId

28 bits

17


Site Properties

iOMS IP

address

18

The BTS can act as a DHCP server, providing an IP

address to external SSE (Site Support Equipment).

1. Provide a single (example above) or range of IP

addresses to the connected devices without further

specification on which device will get which IP

address.

2. HW ID provides a certain IP address to the specified

MAC address (ID).

3. Client ID provides a certain IP address to the specified

client ID.Up to 3 NTP

servers can be

configured

10


Security

The Authentication Lightweight

Directory Access Protocol server

is required for the optional

Remote User Account

Management.

The Certificate Management

Protocol / Certificate Authority

server optionally handles the

automatic installation and

renewal of certificates in the

BTS. Certificates are needed to

support the features Transport

Layer Security and IP Security.

The optional Transport Layer Security for OAM

interface can be Forced on, forced OFF or

Probing (on if supported by certificates,

otherwise off).

For security reasons the operator may want to

block the BTS from replying to Ping and

Traceroute messages by removing the tick.The FTP server function may

be required to transfer files

to/from the eNodeB without the

use of the BTSSite Manager.


Physical Layer Configuration - Transport

20

In LTE, an E1/T1 IF can only be used

for one purpose: Synchronization.

Up to 3 Ethernet interfaces can be used

(with FTIB only 2, EIF1&3 or 2&3). The

Ethernet switching function is configured

on the next page.

11


Ethernet Switching in DSCP Mode with FTLB

The QoS aware Ethernet switching

function supports 6 queues in

FTLB. The queue weight is

configurable in the range 1...8.

If the Ethernet network allows the

operator to temporarily

oversubscript the leased

bandwidth, then an increasing of

the egress data rate to max. 106%

may help to avoid congestion and

buffer overflow.

Note: This option is not available

with FTIB.

The criteria for queue mapping can

be Differentiated Services Code

Point or the DSCP or VLAN priority

code point VLAN-PCP.


Ethernet Switching in DSCP Mode with FTIB

The QoS aware Ethernet switching

function supports 4 queues in FTIB.

The queue weight is configurable in

the range 1...8.

The criteria for queue mapping can

be Differentiated Services Code

Point or the DSCP or VLAN priority

code point VLAN-PCP.

The Shaper allows to limit the

switched bandwidth per interface in

Egress and Ingress direction

individually.

12


Ethernet Switching capabilities FTIB vs. FTLB

EIF 1

EIF 2

EIF 3

EIF 1

EIF 2

EIF 3

FTIB FTLB


Recommended Differentiated Services Code Points (DSCP)

1001010011

1200110021

0000000Best Efford

46011101Expedited Forwarding

1401110031

1801001012

2000101022

2201101032

2601011013

2800111023

3001111033

3401000114

3600100124

3801100134

DSCPDrop Precedence

Per Hop BehaviourAssured forwardingclass

decimalDrop Precedence

PHB binarybinary

13


Ethernet Switching in VLAN-PCP mode

In VLAN-PCP Mode, the mapping to

a queue is based on the VLAN

priority.

The switch mode can be based on

the MAC address only or on both

VLAN ID and MAC address. If kept,

then VLAN Id of untagged frames is

set to 1. The user defined VLAN ID

list can contain up to 16 entries

(single or range).


IP Interfaces

Is the individual TRS Eth / Vlan

shaper (Path) or the overall shaper

(WFQ) used

Weight for the overall WFQ

scheduler.

Enables QoS of the WFQ scheduler (pg.

9/31). Only 1 Eth IF or VLAN can have

QoS enabled.

BFD is an option to monitor IP

connectivity to a far end Router. Two

different routers (session 1 and 2) can be

monitored. If IP connectivity gets lost, an

BFD alarm is generated.

14


Transport Ethernet / VLAN QoS

all SIR/SBSVLAN w

SIR/SBS

Overall

WFQegress

WFQ

SP

all

all

all

Overall

Shaper

TRS Eth IF / VLAN v weight

TRS Eth IF / VLAN w Weight

SIR/SBS

SIR/SBS

SIR/SBS

Standard IP routingon IP destination

User

Ctrl

Mgmt

Sync

a

b

c

d

f

g

h

i

j

VLAN v

VLAN x

VLAN y

VLAN z

Applications

ApplicationIP

Addresses

Interface IP Addresses

Expedited Forwarding

Assured Forwarding 4




Best Effort

User-definedweights

WeightedFair

QueuingScheduler

QoS Enabled

QoS Disabled

QoS Disabled

QoS Disabled

QoS Disabled

individual Shaping

Traffic ShapingType: Path

overall VLAN Shaping

Traffic ShapingType: WFQ

Shaper Information Rate

Shaper Burst Size

Total Shaper

Information

Rate

Total Shaper

Burst Size

TRS Eth IF / VLAN x Weight

TRS Eth IF / VLAN y Weight

TRS Eth IF / VLAN z Weight


Quality of Service

The Quality Of Service definitions on this page are applied

to only that Transport Ethernet interface or VLAN for which

QoS is enabled.

The Weight definitions specify how the WFQ

scheduler proiritizes between the 5 queues.

This table defines the

mapping of a Traffic

type to a DSCP.

This table defines the mapping of a DSCP to

the PHB (defaults according to

http://tools.ietf.org/html/rfc2597

recommendations) and VLAN priority.

NOTE: Radio Network Parameters (LNBTS MO) contain

mapping of LTE QCI indices to transport DSCP and radio

bearer parameters (loss, delay, RLC mode).

Control Plane

Management Plane

Internet Control Message Protocol

Synchronization Plane

Internet Key Exchange

Bi-directional Forwarding Detection

Site Support Equipment

15


Timing over Packet

Activating the Timing over Packet in use

field makes it available as a synchronization

source when defining the Timing Sources on

the Synchronization page of the wizard.

The Master Clock IP address must be

reachable through the Def. GW / Static

Route(s)

The Message rate should be set as high as

necessary for a stable synchronization. The

higher the message rate, the better is the

stability and the higher is the required

bandwidth.

8 times/second: ~7 kbps

16 times/second: ~ 13 kbps

32 times/second: ~ 25 kbps


Application Addresses

16


Activate IPsec and choose a profile

Check the IPSec in use fileld to configure IP Security

processing.

IPSec can be individually configured per traffic type. The pull-

down menu under New Policy lets you select from a list of

Policy templates with pre-filled traffic type specific port numbers

and protcol IDs. Site specific settings still need to be filled in.


IPSec tunnel

IPSec tunnel

IPSec

Gateway

Local IP address

For own IP networks, this can either be the (physical) Transport Ethernet IP address or

VLAN IP address or, in leased or public (VPN) connections this adress can be virtual*.

Local IPSec tunnel IP adress

This can either be the Transport Ethernet or VLAN IP address.

Note: In RL15TD there can be a maximum of only 1 virtual address and only the Ethernet Transport IP or 1 VLAN IP address are allowed to exist then.

* a virtual address is different from Ethernet interface or VLAN IP address.

Local IP

addressLocal IPSec

tunnel IP address

Remote IPSec

tunnel IP

address

Remote IP

address

eNodeB

17


Ipsec settings 1/4 The smaller the Policy order number is the more highly valued is the policy. The applicable Policy/ies with the lowest order

number(s) will be applied.

Bypass-setting does not process any

packets, Discarded-setting does not forward

any packets. Protected-setting follows the

IPsec process.

In case a physical address is used, it can be selected from the

pull-down menu. A virtual address has to be entered manually.

The field is to be left blank, if the same policy is to be applied to all

(VLAN) IP addresses.

The port number has to be specified according to the traffic type

this policy is applied for.

If a policy is to be used for all types of traffic, then the Local port

field is to be left blank.


Ipsec settings 2/4

The Local Ipsec tunnel endpoint IP address can be selected

from the pull-down menu. It is either the previously configured

Transport Ethernet IP adress or a VLAN IP address.

The Protocol is to be selected according to the traffic type this

policy applies for. For all protocol types, the field is to be left blank.

The Remote IP address, Remote port and Remote Ipsec

tunnel endpoint IP address are set according the configuration

on the Security gateway side of the Ipsec tunnel.

18


Ipsec settings 3/4The IKE Internet Key Exchange is a protocol to

exchange the keys used for IPSec encryption in

a secure way and to detect if the far end peer is

still alive (DPD-Dead Peer Detection). There are

2 versions V1 and V2. The version has to be

selected according to the far end configuration at

the Security Gateway

This is the encryption

method used for the Key

exchange.

This is the Encapsulated

Security Payload

encryption method used

for IPSec.


Ipsec settings 4/4

The Dead peer detection delay is the time

between sending R-U-there messages in IKEv1

or Information Request Messgages in IKEv2.

The Dead peer detection

timeout is the time after which a

R-U-there Acknowledge message

must be received. Otherwise a

DPD alarm is raised.

In IKEv2 the Dead peer detection

timeout is not adjustable, but

fixed to 165 seconds

(T1...T6 = 4+7+13+24+42+75

sec.).

The Security associated lifetime is the time

after which the key used for ESP encryption is

automatically renewed.

Anti replay is a method to protect the transport interface from replay attacks where formerly recorded data

packages are send to the receiver in order to authenticate the (non-authorized) sender, even the encryption

key is not known by him.

Anti replay is based on a consecutive numbering of data packages with a sequence number. A replayed

package would have the same sequence number like the original package and the receiver (here FTLB)

would then discard the (faked) package. Also packages with a delay of more than one Anti replay window

size would be rejected.

19


Synchronization

Maximum 2 Timing Sources can be configured. First Prority 1

must exist before selecting Priority 2.

Avalable Types

1. E1 interface, if previously set in use.

2. Synchronous Ethernet

3. Timing over Packet, if previously configured.

Priority 3 is always Internal clock.


Routing

20


IP Filtering

There a are 3 ways to configure IP Filtering.

1. Exception Rules allow the access to the Site

Support equipment for certain IP

addresses. Several rules can be

configured for single or ranges of far end

IP addresses.

2. Restricted mode ON -> Remote Access to

Site Support IP addresses totally blocked.

3. Restricted mode OFF -> Remote Access to

Site Support IP addresses allowed for any

far end IP address.

1.

2.

3.


BTS Settings

43

21


Cell Resource

lcrId

MIMO mode:

SingleTx

TxDiv

Static Open Loop MIMO

Dynamic Open Loop MIMO

Closed Loop MIMO

Single Stream Beamforming


3GPP Frequency Bands for TDD

20 361991920 360001900 361991920 360001900 33

15 363492025 362002010 363492025 362002010 34

60 369491910 363501850 369491910 363501850 35

60 375491990 369501930 375491990 369501930 36

20 377491930 375501910 377491930 375501910 37

50 382492620 377502570 382492620 377502570 38

40 386491920 382501880 386491920 382501880 39

100 396492400 386502300 396492400 386502300 40

eUARFCN

DLhigh

eUARFCN

DLlow

eUARFCN

ULhigh

eUARFCN

ULlow

BW /

MHz

F Downlink

high

F Downlink

low

F Uplink

high

F Uplink

low

Band

NDL andNUL are earfcn which is attribute of LNCEL.

Earfcn = 38000

FDL = FUL = FDL_low + 0.1 (eUARFCNDL eUARFCNDLlow) = 2570 + 0.1 (38000 37750) =2570 + 25 = 2595 MHz

FDL[MHz] = FDL_low + 0.1 (eUARFCNDL eUARFCNDLlow)

FUL[MHz] = FUL_low + 0.1 (eUARFCNUL eUARFCNULlow)

Example from band 38 (2600 MHz)

Calculation of UL & DL Frequencies:

As for TDD, DL=UL

22


LTE Carriers

46


Antenna Line Management

47

TDD uses RRH (Remote Radio

Head), which installed as close as

the antenna, therefore MHA is not

necessary for compensating the

feeder loss

23


AISG Line Settings

48


Siemens Proprietary AISG1.1 TMARET and RET Settings

49

24


RET Settings

50


System Module External Fault and Control Settings

51

25


Radio Network Configuration handling introduction

RNW parameters are

formatted in a hierarchy, click

arrows to see subordinate

objects.

Parameters can be listed

in two orders:

Alpahbetically lets you

easily find a parameter

known by name.

Related Functions uses

the same order as in the

SCF xml-file.

Hover mouse over parameter

name to see description and

short name (as appears in SCF

file).

A validation check is performed by the BTS

Manager. A missing or invalid parameter leads to

an Error indication and description (table

below).


LNBTS MO Key Parameters

Must be unique in

PLMN. Same value

as MRBTS ID and

eNB ID

Values currently can

only be changed by

manually editing SCF

file.

53

26


ADIPNO MO Key Parameters

54


GTPU MO Key Parameters

User plane

supervision

27


SCTP MO Key Parameters

Control plane supervision

Note The S1 and X2 SCTP ports are not configurable anymore from

RL15TD onwards. It is now hard-coded to the 3GPP specified values 36412

for S1 and 36422 for X2.


LNCEL MO Key Parameters

57

28



tddFrameConf: TDD UL-DL configuration (06)

DUUSDUUUSD5 ms6

DDDDDDDUSD10 ms5

DDDDDDUUSD10 ms4

DDDDDUUUSD10 ms3

DDUSDDDUSD5 ms2

DUUSDDUUSD5 ms1

UUUSDUUUSD5 ms0

9876543210

Subframe numberDownlink-to-Uplink

Switch-point

periodicity

Uplink-downlink

configuration



tddSpecSubfConf: TDD special subframe configuration (08)

---1118No

---2107Yes

19396No

28

2

935Yes 2

731124No

1102113No

293102No

38491No1

83

1

1030No

UpPTSGPDwPTSUpPTSGPDwPTS

Extended CP (DL and UL)Normal CP (DL and UL)Format

RL15TD

29


Send Parameters Online Mode

60

Send Parameters will update the

BTS with the new configuration and

restart the BTS (if required) to

enable the changes.


BTS Commissioning: Send Parameters

Initial BTS State

All relevant commissioning

parameters are set -> Send

Parameters to the BTS.

Expected final BTS State

Transfer status

61

30


Verify Commissioning

62


Integration

31


BTS Startup Overview

BTS Initialising

BTS Uncommissioned

BTS Commissioned

BTS Configured

BTS Integrated to RAN

BTS Test Dedicated State

BTS On Air

CDM (SCF file does not exist/

SCF file invalid/ BTS re-hosted)

SCF and RNW

configuration file download

and reset

STUP (SCF exists in BTS,

SCF parsed)

STUP (Ready check done,

FD enabled)

STUP (S1 link connected)

STUP (at least one cell has

operational state Enabled)STUP (none of the

cells is enabled)

STUP (TD state

requested)

BTS can return to normal

operation only after reset

Power ON / reset

64


Test IP Connectivity

65

Choose All configured hosts and make

sure OAM, NTP Server, and Default

gateway are connected.

Choose User-defined address and enter

the IP address for MME, S-GW, adjacent

eNB. (assuming no firewall restrictions

block ICMP).

Select source address appropriate for

interface you are testing.

32


SCTP Association Establishment

eNB (Power On / Reset) MMESCTP: INIT

SCTP: INIT_ACK

SCTP: COOKIE_ECHO

SCTP: COOKIE_ACK

SCTP: HEARTBEAT

SCTP: HEARTBEAT_ACK

SCTP: HEARTBEAT

SCTP: HEARTBEAT_ACK

...

SCTP

establishment

SCTP link

supervision

66


S1 Setup Procedure

eNB MME

S1AP: S1 SETUP REQUEST

SCTP: SACK

S1AP: S1 SETUP RESPONSE

SCTP: SACK

eNB global ID, eNB name, supported TAs and Paging DRX configuration

ServedGUMMEI, Relative MME capacity

GUMMEI: Globally Unique MME Identity

TA: Tracking Area

DRX: Discontinue Reception

67

33


Verify Integration

68

1 Nokia Siemens Networks RA4155-02A RL15TD eNB HOT Transport

LTE Transport OvervieweNB Hands-on Training for Trial (RL15TD)

2 Nokia Siemens Networks RA4155-02A RL15TD eNB HOT transport


Legal notice




Contents


EUTRAN Interfaces


Transport Security New Threats

NB Server

Internet OperatorServices

UE

3G

RNC

3GPP U-plane security

Core

eNBServer


UE

LTE

U-plane security

Core

Core nodes and

adjacent eNBs

can be attacked!

User traffic

can be

compromised!

Location of base station changes

Traditionally in secure, locked sites

In future increasingly in public places or homes

Attack methods evolve

Better attack tools are widely available

Higher processing power to break algorithms

More sophisticated attacks, done by professionals


IPSec with PKI is the Standardized Solution

Relevant 3GPP standards

TS 33.210 Network Domain Security

TS 33.310 Authentication Framework

TS 33.401 Security Architecture

eNBServer


UE

Core

Security

Gateway

(SEG)

Security

Gateway

(SEG)

integrated in

Flexi BTS

IPSec tunnelCert Cert

Authentication

Confidentiality

Integrity protection

PKI: Public Key Infrastructure


Asymmetric Cryptography:Public & Private Keys

Document

Clear Text

BPUBLIC

KEYPRIVATE

KEY

B

Document

Clear Text

PRIVATE

KEY

BDocument

Clear Text

Document

Clear Text

BPUBLIC

KEY

Document

Clear Text

BPUBLIC

KEY FAILS !

Document

Clear Text

Interceptor

BPUBLIC

KEY

A B

Source: Raimund Kausl


Digital Certificate Concept

It includes no secrets

It is issued by a trusted authority which states I guarantee that this particular public key is associated with this particular user, trust me!

It binds the entitys identity to the public key

It contains at least the

Name of the user respectively subject certificate owner

A copy of the users public key

Name of the trusted Authority respectively issuer Certificate Authority (CA)

Digital signature of the Certificate Authority

A subject could be any end entity that has an unique identity like

People

Executable programs / SW

Network elements like Web servers,a LTE Flexi Multiradio BTS ,

Certificate for User A

I officially notarize the

association between this

particular user and particular

public key

APUBLIC

KEY

Subjects Name: A

YourCertification Authority

Source: Raimund Kausl


User Plane Protocol Stack


Transport Overhead

GTP-U (without header extension) 8 bytes

UDP 8 bytes

IPv4 (transport) 20 bytes

IPSec ESP Header (SPI/Sequence Number) 8 bytes

AES Initialisation Vector 16 bytes

ESP Trailer (2-17 bytes, incl. 0-15 padding bytes, average 8

bytes) 10 bytes

IPSec Authentication (HMAC-SHA-1-96) 12 bytes

IPSec Tunnel mode IP header 20 bytes

Ethernet higher layer (incl. 4 bytes for VLAN) 22 bytes

Eth. Inter Frame Gap, Preamble/SFD 20 bytes

Total transport overhead 144 bytes


Dimensioning Based on Air Interface CapacityC

ell

pe

ak

Cell average

eN

B

tra

nsp

ort

All-AverageAll-Average/

Single-Peak

Peak

Rate!

All-Peak

Overb

ookin

g


Dimensioning Example: All-Average/Single-Peak Throughput 1+1+1/10MHz

Notes:

Dimensioning: Max (3 x average rate, peak rate)

M-plane (~1Mbit/s), C-plane (~0.3Mbit/s), X2 U-plane (~30ms bursts) not included

Air

Interface

eNB

92

29

Ethernet layer, with IPSec

Transport

Interface

3 cells, 10MHz, 2x2 MIMO

DL 18 Mbit/s net PHY average rate per cell

UL 7 Mbit/s net PHY average rate per cell

DL 77 Mbit/s net PHY peak rate per cell

UL 24 Mbit/s net PHY peak rate per cell

77

24

+20%

Transport to support the aggregated average capacity of all cells, while at least supporting the peak capacity of one cell


Dimensioning Example:All-Peak S1 Throughput 2+2+2/20MHz

Notes:

Dimensioning: 6 x peak rate

M-plane (~1Mbit/s), C-plane (~0.3Mbit/s), X2 U-plane (~30ms bursts) not included

Air

Interface

eNB

1100

340

918

282

Ethernet layer, with IPSec6 cells, 20MHz, 2x2 MIMO

DL 153 Mbit/s net PHY peak rate per cell

UL 47 Mbit/s net PHY peak rate per cell

Transport

Interface

Transport to support the aggregated peak capacity of all cells (non-blocking)

+20%


Quality of Service Requirements

QCI Resource Type Priority

Packet Delay

Budget

Packet Loss

Rate Example Services

1 GBR 2 100 ms 10-2 Conversational Voice

2 GBR 4 150 ms 10-3 Conversational Video (Live Streaming)

3 GBR 5 300 ms 10-6

Non-Conversational Video (Buffered

Streaming)

4 GBR 3 50 ms 10-3 Real Time Gaming

5 Non-GBR 1 100 ms 10-6 IMS Signaling

6 Non-GBR 7 100 ms 10-3

Voice, Video (Live Streaming) Interactive

Gaming

7 Non-GBR 6 Video (Buffered Streaming)

8 Non-GBR 8 300 ms 10-6

TCP-based (e.g., www, e-mail, chat, ftp, p2p

file sharing, progressive video, etc.)

9 Non-GBR 9

LTE User Plane QoS Requirements


Synchronization via Transport Network


LTE Radio to Transport QoS Mapping


Packet Scheduling


Traffic Prioritization


Flexi Multiradio BTS IP Address Model (1/2)

S1/X2 U-plane application

S1/X2 C-plane application

S-plane application

M-plane application

eNB

internal

routing

U

C

M

S

Binding to virtual address

Binding to interface address

eNB applications may be bound to

interface address(es) or virtual address(es)

Interface IP address

Virtual IP address

eNB

The eNB can be configured with separate IP addresses for User, Control,Management and Synchronization Plane applications.


IP Addressing Examples

eNB applications may be bound to

interface address(es) or virtual address(es)

M

S

U

C

U

C

M

S

M

S

U

C

Application(s) bound to interface address(es) Application(s) bound to virtual address(es)

Address sharing, i.e. configuration with the same IP address, is possible. In the simplest configuration, the eNB features a single IP address.

eNB

internal

routing

Virtual addressInterface address

Multiple interface addresses

Address sharing(Single address)


Flexi Multiradio BTS IP Address Model (2/2)

Interface address(es) may be assigned to

physical interface(s) or logical interface(s)

Possible data link layer interface types are Ethernet (physical interface) or VLAN (logical interface)

RL15TD supports one physical interface and max 4 logical interfaces

Different interfaces belong to different IP subnets.

VLAN

(optional)

eNB

internal

routing

Interface address assigned to physical

interfaces

eNB

Physical interface

(Ethernet)

VLAN2

VLAN3

VLAN4

VLAN1

eNB

internal

routing

Interface addresses assigned to logical

interfaces

eNBPhysical interface

(Ethernet)

Logical interface (VLAN)


IP Addressing with IPSec Tunnel Mode

If IPSec Tunnel Mode is enabled, IPSec tunnel termination

is bound to an interface address

Application(s) bound to interface address

Collapsed "inner" and "outer" address

Application(s) bound to virtual address(es) ("inner) address)

Tunnel terminated at the interface address ("outer address)

Tunnel3

Tunnel4

Tunnel2

Tunnel1

M

S

U

C

Multiple tunnels per eNB

IPSec

tunnel

U

C

M

S

Single tunnel per eNB

VLAN optional

Tunnel


U

C

M

S

eNB

internal

routing

VLAN optional


Recommendation

IP Addressing Example with VLAN and IPSec

U/C/M-plane bound to virtual addresses

forwarded via IPSec tunnel

assigned to VLAN

S-plane bound to interface address

bypassing the IPSec tunnel

assigned to the same VLAN

IPSec Tunnel

U

C

M

eNB

internal

routing

SVLAN

Separate interface IP address for IPSec tunnel termination,IP addresses per functional plane for traffic separation

Interface

IP address

Application

IP address

U C MUser plane Control plane Management

planeS Synchronization

plane


MME

SAE-GW

O&M

X2 Star Architecture

X2 traffic routed through (central) Security Gateway (SEG)

No direct IPSec tunnels between eNBs

Can be implemented with E-Line or E-Tree (both recommended)

eNB

eNB

X2-u/c

SEG

IPSec

tunnel

U

C

M

S


VLAN optional

Simplest configuration with single IP address


MME

SAE-GW

O&M

X2 Star Use Case: IP VPN

IP

eNB

Separate IP addresses for IPSec tunnel terminationand applications

X2-u/c

SEG

IP VPN

Eth

ern

et

IPSEc tunnel: outer IP layer

IPSEc tunnel: inner IP layer

Tunnel


U

C

M

S

eNB

internal

routing

VLAN optional


MME

SAE-GW

O&M

X2 Mesh Architecture(Not recommended)

X2 traffic switched or routed in mobile backhaul network

Direct IPSec tunnels between eNBs

Requires E-LAN (not recommended)

eNB

X2-u/c

SEG


U

C

M

S

eNB

internal

routing

VLAN optional

X2 TunnelsS1 Tunnel


Architecture Comparison

X2 Mesh with E-LAN

Higher complexity

Perceived advantages are questionable

Marginal backhaul traffic savings X2 traffic

11 Nokia Siemens Networks RA4155-02A RL15TD eNB HOT TD-LTE FlexiBTS software and tools

TD-LTE Flexi BTS software and toolseNB Hands-on Training for Trial (RL15TD)



Legal notice




Contents

eNB related interfaces and protocol stack

Introduction to the TDD eNB software architecture

Description of each TDD eNB SC (System Component)

Tools


LTE-UE

LTE/EPS Network Interfaces

Evolved UTRAN (E-UTRAN)

MME S10

S6a

Serving

Gateway

S1-U

S11

Evolved Packet Core (EPC)

S1-MME

PDN

Gateway

PDN

PCRF

GxRx

SGiS5/S8

Evolved

Node B

(eNB)

cell

X2

LTE-Uu

HSS

MME: Mobility Management Entity

SAE

Gateway

User plane

Control Plane

Control Plane + User plane

Gxc


TS 36.421

LTE Radio Interface and the X2 Interface

LTE-Uu

Air interface of EUTRAN

Based on OFDMA in downlink and SC-FDMA in uplink

FDD and TDD duplex methods

Scalable bandwidth: from 1.4 up to 20 MHz

Data rates up to 100 Mbps(DL), 50Mbps (UL)

MIMO (Multiple Input Multiple Output) is a

major component although optional.

X2

Inter eNB interface

Handover coordination without involving the EPC

X2AP: special signalling protocol

During HO, Source eNB can use the X2 interface to forward downlink packets still buffered or arriving from the serving gateway to the target eNB.

This will avoid loss of a huge amount of packets during inter-eNB handover.

(E)-RRC(E)-RRCUser PDUsUser PDUs

PDCPPDCP

RLCRLC

MACMAC

LTE-L1 (FDD/TDD-OFDMA/SC-FDMA)LTE-L1 (FDD/TDD-OFDMA/SC-FDMA)

TS 36.300

eNBLTE-Uu

eNB

X2

User PDUsUser PDUs

GTP-UGTP-U

UDPUDP

IPIP

L1/L2L1/L2

TS 36.424

X2-UP

(User Plane)

X2-CP

(Control Plane)

X2-APX2-AP

SCTPSCTP

IPIP

L1/L2L1/L2TS 36.421

TS 36.422

TS 36.423

TS 36.420[X2 general aspects & principles)

NAS ProtocolsNAS Protocols

Control Plane User Plane

TS 36.323

TS 36.322

TS 36.321

TS 36.331

TS 29.281

TS 24.301


S1-MME & S1-U Interfaces

S1-MME

Control interface between eNB and MME

MME and UE will exchange non-access stratum signaling via eNB through this interface.

E.g.: if a UE performs a tracking area update the TRACKING AREA UPDATE REQUEST message will be sent from UE to eNB and the eNB will forward the message via S1-MME to the MME.

S1AP:S1 Application Protocol

S1flex 1 eNB to connect to several MME

S1-U

User plane interface between eNB and serving gateway.

It is a pure user data interface (U=User plane).

S1flex-U also supported: a single eNB can connect to several Serving GWs.

Which Serving GW a users SAE bearer will have to use is signaled from the MME of this user.

MME

Serving

Gateway

S1-MME

(Control Plane)

S1-U

(User Plane)

NAS ProtocolsNAS Protocols

S1-APS1-AP

SCTPSCTP

IPIP

L1/L2L1/L2

User PDUsUser PDUs

GTP-UGTP-U

UDPUDP

IPIP

L1/L2L1/L2

TS 36.411

TS 36.411

TS 36.412

TS 36.413

TS 36.414

TS 36.410[S1 general aspects & principles]

eNB

TS 29.281

TS 36.410[S1 general aspects & principles]

TS 24.301


Flexi TD-LTE BTS SW Architecture

BTS Common

Platform SW

BTS Common

Application SW

WCDMA

SW

ALD

RAT specific

Application

CP and UP SW

BTS

Site

Mgr

GPS

Receiver

3rd party

RF HWSW

SW

SW

Flexi BTS System Module HW

UM

RFSW

BTSOMDFT

3rd party

HW

Common Application SW

Common Platform Services SW

HWAPI DSP HWAPI

LTE

SW

GSM

SW

OS

FR/AAS

Module

HW

PC/

Workstation

CC&S

I-HSPA ADA SW

BTS Common SW

TRSW

Shown in next slide


LTE specific Application SW


SC (System Component) Responsibilities

L2 air interface protocols (Packet Scheduling, AMC, UL/DL configuration)LTE MAC

GTPu protocol, PDCP protocol, Integrity protection, (Air interface) Ciphering, forwarding of data during handover

LTE TUPu

Provides common utility functions to LTE specific System Components: ASN.1 codecs, State machine framework

LTE COMMON

Local O&M. CPU local interfaces for Performance measurements, Fault/Alarm handling, interface for debugging and trace tools

LTE LOM

Cell related RRM functionality, Admission control, Paging control, System information broadcast

LTE CELLC

Baseband L1 (PHY) processing, UL&DL Transport channel processingLTE PHY

Termination of SCTP based external control interfaces (S1 + X2) and internal message distribution

LTE TUPc

User Equipment control, UE state management, UE bearer management, Handover control, termination of UE related RRC, S1 & X2 signalling

LTE UEC

Central control functions, central Id allocation, S1/X2 common procedures, eNBwide RRM functions

LTE ENBC

Allocation of BB resources for cells. Distribution of configuration parameters. Control of cells and common channels

LTE RROM

Function DescriptionSC


SC (System Component) Responsibilities (cont)

Hides physical devices and buses behind a message and function interface from

the application SW (MCU environment)BTS Site Manager

Mast head Amplifier, Remote Electrical Steering, SW tuneable FiltersMHA, RES, Filter

Transport sub module SW, forwarding external IP packet to correct internal SC, IPSec handling

TRSW

Radio Module SW, SW in the RF MCU controlling the RX, TX and PA and their interfaces. LTE RFSW is also responsible to manage Radio Module level functionality (e.g. temperature control etc.)

RFSW

Design For Testability, to offer testability features via the WEB interfaceDFT

Faraday start-up and DSP application start. Hiding DSP HW environment for the

SW applicationsDSP HWAPI

Startup handling on MCU. Hiding MCU HW environment for the SW applicationsHWAPI

Common Computer & Support, basic local computing services and system servicesfor applications, provides interfaces for supporting application testability

CC&S

Unit management, runtime SW entity that represents a HW resource (module or

unit), startup, recovery UM

BTS level Operation & MaintenanceBTSOM

Function DescriptionSC


Deployment Model


Tools

Pinger

Wireshark

BTSLog


Pinger

Pinger is a .bat or .exe file used to ping all modules in eNB: FCMD, FSPs, Faradays on FSPs, FTM and FR. Once started ping to the modules is sent periodically.

In order to get Pinger working following steps need to be performed:

Double click PING_Fararays_all_FSPs.BAT or PingerGui.exe in your folder

New version of Pinger


Local IP addresses in Flexi Multiradio BTS

Direct connection with PC:192.168.12.1

IP addressModule

192.168.255.126/255.255.254.0PC

192.168.254.129

192.168.254.137

192.168.254.145AXIS RRH

192.168.255.129FTM

192.168.255.33 (FSP1)

192.168.255.34 (FSP2)

192.168.255.35 (FSP3)

FSPC

192.168.255.1FCMD


LTE tracing methods- Wireshark

Traces all IP traffic in monitored IP address

Decodes protocols interface protocols, but has no access to radio protocols

No possibility to decode ciphered protocols

Useless with IPSec

Suitable for single BTS monitoring, mobility and multiple users may be difficult to separate from trace

NSN version available -> No additional license fees

Runs in any Windows PC, with firewall limitations


LTE tracing methods- Wireshark


BTSLog

BTSLog tool is used to collect different log files from eNB like:

BTS Tracing Log : BTSLOG_TRACE_.bin

System log files : SYSLOG_.txt

RealTime log files


Tools->Setup

BTS Log: Tracing Setup

Check if this value is set

correctly.

Value to be used is:

51003

10


BTS Log: BTSLog File Settings

Tools->Setup

Log file size and number of files can

be set here.

Binary and UDP

trace are stored on

the location specified

here.


Set Task to 0x060c

BTS Log: R&D Parameter Setup

1

2

BTSLog->Nodes

3

ALL three FSPx_MCU

need to do this

modification!!!

11


BTSLog and Firewall Settings

In case only Ping failed messages are visible in RealTime log and all

necessary settings are correct check the Firewall settings on PC/laptop.

E.g. Control Panel --> Admin Tools --> Services and disable OfficeScanNT Firewall

If OfficeScan NT Firewall is started: Just Ping failed logged

If OfficeScan NT Firewall is stopped: All real time information is logged


Nodes which can be set in BTSLog (which nodes can be configured

depends on nodes.ini file used).

If some Nodes are configured but not accessible because they are e.g.

not installed, they cause ping-not-ok in the BTSLog main window.

BTS Log: Configure Nodes

12


Current Syslog has index 21. The file SYSLOG_021.LOG is stored on predefined location.

Start UDP Log creates Syslog file on pre-defined location

BTS Log: Start UDP Tracing

If View button is pressed the current SYSLOG file will be opened with the predefined editor.


Click on this button to start Real Time Log on configured Nodes

BTS Log: Start Tracing and Real Time Views

Up to 4 Real Time Logs can run in parallel (e.g. with different filters).

13


BTS Log: Configure Binary Tracing

In order to collect binary traces appropriate file with extension bts need to be loaded to

the BTSLog application (Nodes -> BTS Filters)


BTSLog Filter

Note: String entered as a filter is case sensitive. Press Apply button to apply

the new/modified filter.

Filtered RealTime Log

Filter can be applied on RealTime logs. Only those messages will then be displayed which

contain one or more strings set in the filter. Another example for usage of the filter: Set

OnAir string as filter in order to check if the eNB is going into OnAir state after startup.

14


BTS Log: Disable Authorization

Click Nodes in main window, then R&D Parameters Tab and than Get Current.

Double-click on parameter 244 and change the value.

Note: The change made via BTSLog will be lost by the next reset. In order to disable

authorization permanently, swconfig.txt with appropriate settings need to be copied to FCMD in

/rom directory (username:pa

ENB Hands-On Training for Trial (RL15TD)

Documents

Transcript of ENB Hands-On Training for Trial (RL15TD)