Chichi chacha

RA34051EN02GLA0

System Architecture

1

1 © Nokia Siemens Networks RA34051EN02GLA0

Academy course:I-HSPA Operation and MaintenanceRelease 2.0System Architecture

RA34051EN02GLA0

System Architecture

2


Nokia Siemens Networks AcademyLegal notice

Intellectual Property RightsAll 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.

RA34051EN02GLA0

System Architecture

3


Document change history

Date Version Name Change comment

12 Nov 2009 1.0 R. Benson Initial version

RA34051EN02GLA0

System Architecture

4


Outline

• I-HSPA Network architecture

• I-BTS hw/sw and physical connections

• Internal VLANs and IP addressing principles

• Transport reference configurations and IP addressing examples

– IP over Ethernet (IPoE)

– IP over ATM (IPoA)

• Synchronization configurations

• Interfaces and Protocols

RA34051EN02GLA0

System Architecture

5


I-HSPA Network Architecture

I-HSPA is a simplified network architecture based on innovative 3GPP standards. I-HSPA system solution, handling HSPA services, enables high capacity and high bitrates optimizing for

the 3GPP operators both the network response times and the costs of Packet Switched (PS) network

From a technical perspective I-HSPA is a flat architecture: the I-HSPA RAN consists of the I-BTSNetwork Element, derived from a Nokia Wideband Code Division Multiple Access (WCDMA) BTS plus an I-HSPA Adapter implementing the RNC functionality. Relevant WCDMA BTS generations are Flexi and Ultrasite

The I-HSPA radio access architecture which supports standard compliant terminals offers the operators an optimised radio interface for HSPA service

I-BTS network element is connected to the 3GPP Core Network (CN) via the 3GPP standard Iu-PS/Gninterfaces

I-HSPA flat architecture, an evolutionary step towards LTE, utilizes the Direct Tunnel solution to bypass the SGSN in the User plane with performance benefits (e.g. lower user plane latency)

I-HSPA uses Serving GPRS Support Node (SGSN) and Gateway GPRS Support Node (GGSN) network elements to handle mobility

The complete solution is centrally managed and operated via OMS and the Nokia Siemens Networks NetAct Framework which provides the operator with a suite of tools to perform network monitoring, configuration, fine tuning, accounting and optimization functions

RA34051EN02GLA0

System Architecture

6


I-HSPA Network ArchitectureAn Evolutionary Step towards LTE

NodeB RNC

Radio Network

I-BTS

Radio Network Core Network

Internet

SGSN

GGSN

For R99 services

eNodeB

Radio Network Core Network

Internet

eGSN-c

eGSN-u

I-HSPA

LTE

SGSN GGSN

MGW

MSC-S

Core Network

Internet

PSTN

RA34051EN02GLA0

System Architecture

7


I-HSPA Rel-2

RNC

I-BTS

IP / Ethernet

I-BTS

SGSN

Eth

GGSN

Eth

MSS

Eth

IP /Eth

Eth

• HSDPA calls supported by I-BTS

• CS calls served in I-BTS also– I-BTS acts as Drift RNC

– RNC acts as Serving RNC

• Timing Over Packet supportIuCS cp

IuPS cp

IuPS up

IuPS up

Iur

Eth

Iur is used for CS and CS+PS calls

IuPS cpIuPS up

IuCS cpIuCS up

VPN GW

ToP Master

I-OMS

NetAct

DCN Network

• IuPS cp

• IuPS up (Gn)

• IuCS cp

• Iur to other I-BTS’s

• Iur to RNC

• ToP

• I-OMS

Iur is used for soft handover between

I-BTS’s

Eth

Eth

2+2+2

2+2+2

RA34051EN02GLA0

System Architecture

8


I-HSPA Release Compatibility

Network Element I-HSPA Rel-1 I-HSPA Rel-2

I-HSPA Adapter ADA1.0 ADA2.0

RNC RN3.0 (CD2.2)

And RN4.0

RN4.0 CD2.0

Flexi WCDMA BTS WBTS4.0 WBTS5.0 CD1.4

OMS I-OMS1.0 I-OMS2.0

NetAct OSS5.1 OSS5.1 CD2 priority CD

MSC Server M14.2 M14.2

Combi SGSN SG6 CD6;

SG7 CD2

SG6 CD9;

SG7 CD2

Flexi ISN (GGSN) FI3.2 PCD2.2 FI4.0

• SIGTRAN activated in CS and PS core

RA34051EN02GLA0

System Architecture

9


Outline









RA34051EN02GLA0

System Architecture

10


I-BTS Flexi Mechanics

Fans and casing are missing from figure

I-BTS Flexi

I-HSPA Adapter

10/100/1000 BaseT Ethernet

• Transport interface Ext3 can be configured to auto negotiate or 10/100/1000 Mbit/s mode• Can be configured to half or full duplex• IADA MML Command ZQIS• Default: auto negotiate speed / full duplex

External transport network

Naming convention in this slide set:

IADA + FlexiBTS = I-BTS Flexi,

IADA + UltraBTS = I-BTS Ultra

RA34051EN02GLA0

System Architecture

11


System Module Interfaces

Input for external sync

Connection to IADA

FTM transmission sub-module

(here: 8x E1/T1)

Note, Power Supply for BB-EXT Module has a main switch for System Module Power feed. By pulling out the switch, power in System Module and FTM is disconnected.

When connecting locally to I-BTS, plug in to LMP port of system module. Computer settings:

Static IP address configuration (DHCP not used)

IP Address 192.168.255.130

Subnet Mask 255.255.255.0

check with ping 192.168.255.143 (OMU IP Address) or 192.168.255.142 (DSP IP)

Gateway address not needed (all units in the same L2 domain).

RA34051EN02GLA0

System Architecture

12


IADA HW architecture

DSP

1 GB

Flash drive

-48V DC

1GB DDR2

L2 Switch

SGMII

1000Base-T/BX

DC/DC

Intel

chipset

256MB DDR2 GbE

PHY

USB 2.0

1MB boot

Flash

SGMII

SGMII

Unit status

LED

Temp sensor

Temp. control

Pentium board

Pentium

1.8GHz

RJ-45

SERDES

BTS interface

Iub/GnEthernettransport interface(electrical or optical)Gn

RJ-45

SFP(Optional)

DMX FPGA

Main DC/DCConverter

DC/DC

Local management Port

RA34051EN02GLA0

System Architecture

13


IADA logical SW architecture

DSP application SW

DSP platform SW

OSEck

Operating System

Faraday DSP

“RNC” application SW

IPA platform SW

DMXOperating System

Intel Pentium processor

Ethernet L2 switch

To external transport network

to BTS

I-HSPA Adapter

DSP Module Pentium Module

VLAN3

VLAN3

VLAN2

VLAN2VLAN4

NOTE: VLANs supported only

internally, not for external traffic

RA34051EN02GLA0

System Architecture

14


I-HSPA Adapter Unit tasks

I-HSPA Adapter

Adapter Unit O&M

RNC HSPA Applications

OSEck

Pentium Computer SW

DMX

RNC ICSU (Interface Control and Signalling Unit)-Signalling protocols for Iu, Iub, Iur-Call admission control-Hand-over control & Load control-RRM-Rel99 Packet scheduler-Signalling link control

RNC OMU (Operation and Management Unit)-RNC HW configuration mgmt-Alarm system &Recovery functions-Performance mgmt-RNW parameter database & management

RNC RRMU (Radio Resources Mgmt Unit)

-RNC centralized RRM tasks, e.g. RC3

RNC RSMU (Resource and Switch Management Unit)- RNC centralized resources management

RNC DMCU (Data and Macro Diversity Combining Unit)-Macro diversity hand-overs-Packet data processing-Radio interface L2 (PDCP, RLC..)

RNC GTPU (GTP unit)

-Signalling protocols-HSPA CAC-Hand-over control-Load control-RRM-Signalling link control-Common channels control-Alarm system-Performance mgmt-RNW mgmt-RNW database

-Adapter unit mgmt-FlexiBTS Iub-Capa Licence key-SW mgmt-IPSec CCH SW (Mac-C)

U-plane SW

DSP Computer SW

DSP Pentium

OM

UD

SP

RA34051EN02GLA0

System Architecture

15


I-HSPA Adapter HardwareEthernet Switch Module: Marvell 88E6131

Only Ports #0, #1, #2, #4 and #5 are used

Interfaces- 3 x Base-Tx interfaces connected to RJ45 connectors:

• One interface is Iub interface (towards 3G BTS) [Port#0]• One interface is Transport interface [Port#1]• One interface is Local management interface [Port#2];

Port#2 cannot be used as a redundant link connected to Site router

- SGMII/SERDES interface to DSP [Port#4]- Base-BX/SERDES interface to Pentium module (to Intel 82572EI)

[Port#5]- SERDES interface to optical SFP module (optional transport

interface) [Port#6] is not used

Configuration for switch is loaded from EEPROM- EEPROM is connected to switch with SPI-interface- EEPROM image can be loaded from Pentium (through chip set

GPIO-pins)• Switch needs to be reset before a new configuration is

loaded to switch

Messaging between OMU and DSP unit is based on DMX messages transferred via EMB (Ethernet based Message Bus). There are switch management DMX processes running in OMU (LS8MAN) and DSP (LSDSP). EMB messaging uses Nokia proprietary protocol

Transport

Local MGMT

SERDES

Iub

I-HSPA Adapter

OMU Intel CPU Pentium

(LS8MAN)

DSP(LS8DSP)

L2 SwitchPort #0

Port #5

Port #4

Port #1

Port #2

Port #6

Message transportation protocols between OMU and DSP

DMX Message protocol

Ethernet

Message

Iub

Transport

Local MGMT

SERDES

Port to Iub interface

Port to Transport interface

Port to Local Management

Port to SFP module optical Ethernet

RA34051EN02GLA0

System Architecture

16


I-HSPA Adapter LAN architecture

ext2 ext3 Iub

LMP

Iu-PS/CS

Iub

EL0

OMUDSP

VLAN 1 tag 1

VLAN 2 tag 2

VLAN 3 tag 3

eth1

eth1.1

eth 1.2

eth0

eth 0.3

Switch

BTS subnet: 192.168.255.0/24 (private Iub)

LMP Subnet 192.168.254.0/24 (private ext2 only)

Iub and Iu-PS/CS: Site dependent (public addresses)

The internal connections through the Ethernet SW are listed in the slide

The VLAN Tagging is only used internally there is no external VLAN support

The LMP subnet on EXT2 is tagged VLAN1. this subnet is preconfigured

The WBTS Iub subnet is tagged VLAN2 and is also preconfigured however it will need a Public IP address for BTS O&M.

The external connections have to be configured with external routable IP address

All Public IP address are configured during the commissioning phase using the site commissioning file/Macro

RA34051EN02GLA0

System Architecture

17


I-BTS Flexi: FTM Hardware

Flexi BTS System Module Core

Flexi TransportPDU

FTEB

FTOA

FTHA

+

Flexi WCDMA BTS Flexi Transport (FTM Sub-modules) Core Interface

FTFA

FTPB

1. System Module with integrated BB.

2. System Module with embedded separate transport sub-module.

3. BTS O&M and Transport distributed to 2 boards with 2 HW/SW systems.

FTIB

FTCC FIPB

FIEB

FIFA

FIOA

FTCC +

FTCC +

FTCD +

FIHAFTCC +

FIIBFTCC +

FTIB

IH2

FTPB

IH1

FTHA

IH1

FTOA

IH1

FTEB

IH1

FTFA

IH1

FTM5.0 ReleaseFTM2.1 ReleaseFTM2.0 Release

FTIA

IH1

FTJA

IH1

FTJA

FTIA FIIAFTCC +

FIHAFTCC +

FTM

RA34051EN02GLA0

System Architecture

18


Transport Sub-Module Type

InterfaceType

Number ofInterfaces

Notes

FTPB E1/T1/JT1, symmetrical 8(8xRJ48)

ATM over PDH with IMA

FTEB E1, coaxial 8(16xSMB)


FTHA E1/T1 (FTCP cable) 16 ATM over PDH with IMA

FTOA STM-1 / OC-3, Fibre 1 x STM-1 S1.1 (LC) ATM over SDH (VC-4 mapping)

FTFA Nokia FlexBus, Cable Interface 2(2xTNC)

ATM over 16xE1 with IMA

FTIA E1/T1/JT1, Symmetrical 10/100Base-TX, (GE1)

4 PDH (4xRJ48)2(31) Ethernet (RJ45)


FTIB E1/T1/JT1, Symmetrical 10/100Base-TX, (GE1)

4 PDH (4xRJ48)2(31) Ethernet (RJ45)

ATM over PDH with IMA, ToP

FTJA E1, Coaxial 10/100Base-TX, (GE1) 4 PDH (8xSMB)2(31) Ethernet (RJ45)

ATM over PDH with IMA CES (ATM over Ethernet)

Note 1: There is an optional Gigabit Ethernet Interface available to support1000Base-SX/LX optical fibre applications (SFP)

I-BTS Flexi: FTM Hardware (2)

• All the interfaces above can be used in IP over ATM transport configuration (ATM over PDH/SDH with IMA)

• FTIB, FTIA and FTJA can be used with IP over Ethernet. In practice only FTIB is worth considering because it supports ToP. If ToP is not needed, then one can use IADA Ethernet transport port directly ( no need for FTIB)

RA34051EN02GLA0

System Architecture

19


Outline









RA34051EN02GLA0

System Architecture

20


I-HSPA Adapter Internal VLANs and Flows

ADA L2 Switch supports in IP stack of OMU and DSP the Port Based VLAN mechanism according to VLAN 802.1Q standard. Port based VLAN is used for security reasons and it shall ensure that there is no direct connection between Iub port and other external ports (transport port, local management port). Therefore the switch maintains two separate Port based VLAN mapping rules: initial configuration rule: the system is not ready for traffic processing; and final configuration rule: the system is up-and-running and is fully capable of processing traffic: Internal VLAN grants traffic separation between external traffic (Network L2

domain) and internal traffic (I-BTS L2 domain) IP packets destined/sent to/from 3G BTS internal IP addresses do not go

directly to the Core Network (CN) to guarantee that MAC addresses of 3G BTS are not exposed to the unprotected network for security reasons; only Ethernet ports of the C-plane and U-plane processors are in the same

VLAN as the external Ethernet ports It shall be possible to configure static MAC addresses to support MAC-based

VLANs; External VLAN are not supported; Packets are forwarded only to the Ports inside the VLAN that is defined in the

VID tag The packets are tagged by ADA L2 switch; VID tag is then stripped from the

packets when these are sent to the ADA L2 Switch egress port The media connecting the L2 Switch do not receive any tagged packets

CN/OMSIub

Port#2 - LMT

untagged

Local MGMTVLAN1

VLAN3VLAN2

Port #4 - DSP

Port#5 - OMU

Port#1-Transport

untagged

Port#0

PVID=2

PVID=1PVID=2PVID=3PVID=4

PVID=1PVID=2PVID=3PVID=4

ADA L2 Switch

VID VLAN Switch Port# Description

1 VLAN1 2, 4, 5 It is used for Local Management

2 VLAN2 0, 4, 5 It is used for Iub interface

3 VLAN3 1, 4, 5 It is used for external logical interfaces (Iu-CS CP; Iu-PS, Iur/Iur*) and OMS flows

4 VLAN4 4, 5 It is reserved for messages transferred via EMB (Ethernet based Message Bus): DMX messages, BOOTP packet

VLAN4

RA34051EN02GLA0

System Architecture

21


Internal VLANs

VLAN

1

VLAN

3

VLAN

2

For Local Management

For Core Network

For Internal Iub

EXT 3 BTS IUBEXT 2

NOTE: Ethernet frames in “VLANs” are untagged (no .1Q header)

RA34051EN02GLA0

System Architecture

22


I-HSPA Adapter IP Addressing

Host IP Address (Dec) Description

OMU 192.168.255.143 (Private) IP private address is used:

1) to terminate Iub C-Plane (NBAP) between ADA and 3G BTS

2) to forward IP packets towards ToP, BTSOM (3G BTS Flexi), AXC&OM (3G BTS Ultra)

Static MAC is for connection with 3G BTS Flexi and 3G BTS Ultra (i.e. IFUH) respectively

IP1 (Public)

IP2 (Public)

IP public address and configurable MAC provide connection for:

1) C-Plane of external transport interface (i.e. Iu-CS, Iu-PS, Iur)

2) Routing of BTSOM traffic

DSP 192.168.255.142 (Private) IP private address and static MAC terminate Iub U-Plane with 3G BTS Flexi and 3G BTS Ultra (i.e. IFUH) respectively

IP3 (Public) IP public address and configurable MAC terminate U-Plane of external transport interface (Iu-PS, Iur/Iur*)

L2 Switch

Not Applicable It supports Port Based VLAN mechanism which grants traffic separation between external traffic (Network L2 domain) and internal traffic (I-BTS L2 domain)

Into ADA are configured two IP subnets to separate traffic physically by the Transport Port # 1:

1) Private subnet is used for 3G BTS and intra-ADA traffic: this subnet, which comprises a set of private fixed IP addresses (i.e. OMU, DSP, 3G BTS: FTM, IFUH), is not exposed to external CN subnets;

2) Public subnet is used for external traffic: Iu-CS (CP), Iu-PS, Iur/Iur* and O&M flows

192.168.255.143MAC: 0E-00-00-01-06-12IP1 Public OMU IP2 Public IADA BTS O&M

L2 Switch

I-HSPA Adapter

OMU

192.168.255.142MAC: 0E-00-00-01-06-11

IP3 Public

DSP

#4

#5#1

#2#0

I-BTS

LGM

Transport

3G BTS Ultra

Iub

3G BTS Flexi

RA34051EN02GLA0

System Architecture

23


IP addressing example, one I-BTS

• Two publically reachable subnets: IADA subnet and BTS O&M subnets• OMU has two public addresses:

– one IP address towards external transport network– one IP address in BTS O&M address

Flexi BTS with I-HSPA

L2 Switch L2 Switch

I-HSPAAdapter

Iub, O&M Trans

FCM (”BTS”) OMU

192.168.255.1

192.168.255.129

192.168.255.143

192.168.255.142

10.1.1.1/29 OMU10.10.10.3/29 (IADA BTS O&M)

FTM (”TRS”)

10.10.10.2/29

FSP192.168.255.33

FSP192.168.255.34

FSP192.168.255.35

DSP

10.1.1.2/29

LGMIub

SERDES

Iub

Trans

LGM

SERDES

:Port to Iub interface

:Port to transport interface

:Port to local management

:Port to SFP module, optical ethernet

xxx.yyy.zzz.www: private address xxx.yyy.zzz.www: public address that needs to be planned

10.10.10.1/29

RA34051EN02GLA0

System Architecture

24


BTS O&M IP interfaces in IADA (IPoE)< ZQRI;

LOADING PROGRAM VERSION 12.9-0

I-HSPA IPA2800 2009-06-04 13:40:13

INTERROGATING NETWORK INTERFACE DATA

IF ADM IF ADDR

UNIT NAME STATE MTU PRIORITY TYPE TYPE IP ADDRESS

--------- --------- ------ ---- --------- ---- ---- -----------------------

OMU-0 EL0 UP 1500 - P 192.168.254.143/24

VLAN1 UP 1496 - P 192.168.1.143/24

VLAN2 UP 1496 - P 192.168.255.143/24

P 10.10.10.3/29

VLAN3 UP 1496 - P 10.1.1.1/29

DSP-0 ETH0.3 UP 1496 - P (10.1.1.2)/29

ETH1.1 UP 1496 - P (192.168.1.142)/24

ETH1.2 UP 1496 - P (192.168.255.142)/24

IADA BTS O&M address in IADA

Iub VLAN

RA34051EN02GLA0

System Architecture

25


L2switc

h

OMU: 192.168.255.143

2 public IP Addresses

L2switc

h

FCM: 192.168.255.1public IP Address

UP: 192.168.255.xxx{FSP private IP}

Flexi BTS I-HSPA Adapter

FTM

192.168.255.129public IP Address

- BTSOM routing- SMA

FTM routes BTS O&M to OMU using OMU MAC address.

OMU routes BTS O&M to FTM.

DSP: 192.168.255.142

public IP Address

Public IP address in BTS

O&M subnet

Public IP address in external

transport subnet

BTS O&M IP flow

SMA = Site Management Agent

RA34051EN02GLA0

System Architecture

26


Outline









RA34051EN02GLA0

System Architecture

27


I-HSPA BTS Reference Configurations (IPoE, Flexi)

I-HSPAAdapter

FlexiBTS

Option 1: IPoE using IADA Ethernet port, Flexi

to/from external transport networkIub

I-HSPAAdapter

FlexiBTS + FTIB

(except FIIB)

Option 2: IPoE via FTM Ethernet port (FTIB), Flexi

to/from external transport networkIub

ToP modul

e L2 switchFIIB

FTIB

FTIB FIIBFTCC +

RA34051EN02GLA0

System Architecture

28


I-HSPA BTS Reference Configurations (IPoE, Ultra)

AXC + IFUHUltra BTS

Option 1: IPoE using IADA Ethernet port, Ultra

to/from external transport network

Iub I-HSPAAdapter

RA34051EN02GLA0

System Architecture

29


Iub’IFUH

ADAOMUAXC

Eth Eth

WAM

AXUIWF

3G BTS Ultra

Port#0 (Iub)

I-BTS Ultra

Port#1 (Transport)

ToPA

DSP

Configurations when L2 is Ethernet (IPoE)

• I-BTS Flexi: the I-HSPA Adapter (ADA) is connected to the WCDMA BTS, i.e. FTM sub-module L2 Switch via ADA L2 Switch. Two configuration options are available.

• I-BTS Ultra: the I-HSPA Adapter (ADA) is connected to IFUH unit via ADA. Only one configuration option is available.

• L3 is always IP with I-BTS, but L2 towards external transport network can be either Ethernet or ATM

• Ethernet transport configuration options shown below

ADA OMU

Eth

Port#0 (Iub)

Port#1 (Transport)

I-BTS Flexi

Configuration Option 1

DSPIub’

System Module

BTS Switch

FSP

3G BTS Flexi

FSP

FSP

FTM (any Ftxx module)

FTxx

Eth

Eth

Port#1 (Transport)

ADA OMU

Port#0 (Iub)

DSPIub’

System Module

BTS Switch

FTIB

FSP

Eth

3G BTS Flexi

FSP

FSP

ToPA

Eth

Eth

I-BTS Flexi

Configuration Option 2Eth

FTM Module required for O&M functionality, even if IADA Ethernet port is used for external transport.

RA34051EN02GLA0

System Architecture

30


IPoE Transport Ref Config #1

IuCS

CP O

&M

Gn U

P

RA34051EN02GLA0

System Architecture

31


Ethernet transport Option 1 is via ADA (IHSW-33):• Iub‘ internal interface is via ADA L2 Switch Port#0• External interfaces (e.g. Iu/Iur) are via ADA L2

Switch Port#1.• Timing over Packet feature is not supported.

I-BTS Flexi IPoE Configuration Option 1

U/C/M Plane frames

DL ToP frames

Internal Iub’ frames

UL ToP frames

Internal Iub’

System Module

BTS Switch

FTxx

FSP

ADA

Port#0 (Iub) Port#1 (Transport)

3G BTS Flexi

MSC

SGSN

GGSN

SAS

RNC

I-BTS

ToP Master

OMSOMU

L3 router

DSP

Eth Eth

IP/Eth???

RA34051EN02GLA0

System Architecture

32


IPoE Transport Ref Config #2

Operators CoreNetwork

.

.

.

I-BTS 1

Adapter

DSP

MSS OMS

GGSN

SGSNRNC

SASIuPCOMU

I-BTS 2

OMU

DSP

Access site Core site

Core site router

With/without IPSec

Public network

Flexi BTS

FCM

FCM

IP/EthernetVPN GW

MGW

ToP Master

FTM with ToP slave

FTM with ToP slave

RA34051EN02GLA0

System Architecture

33


I-BTS Flexi IPoE Configuration Option 2

Ethernet transport Option 2 is via FTM FTIB sub-module only (ARAN1155):

• FTIB (Hybrid unit – 4 x E1/T1/JT1 symmetrical + Ethernet (FE+GE) + ToP + Sync Ethernet):– 4 X E1/T1/JT1 are not enabled.

• External interfaces are via FTM Ethernet Port.

• ToP feature is supported with ToPA module embedded in FTIB card

• FTIB functions as a L2 switch, forwarding U/C/M traffic to/from ADA

U/C/M Plane frames

DL ToP frames


UL ToP frames

Internal Iub’

System Module

BTS Switch

FTIB

FSP

ADA

ToPA

Port#0 (Iub)

Port#1 (Transport)

3G BTS Flexi

MSC

SGSN

GGSN

SAS

RNC

I-BTS

ToP Master

OMSOMU

L3 router

L2 switch

DSP

Eth Eth

EIF1/2

EIF3 IP/Eth

FTIB functions as a L2 switch

only!

RA34051EN02GLA0

System Architecture

34


FIIB Card in I-HSPA mode (from Sys Arch slides, edited)Features:• 2 FE (10/100Base-TX)• 1 GE (SFP)• 4 E1/T1 supported in I-HSPA ATM transport mode• IEEE 1588 (ToP) • 1.1 Gbps System Interface

• Only in I-HSPA mode EM must support the enabling of EIF3 and additionally one of EIF1or EIF2; it is not possible to support both EIF1 and EIF2 at the same time

• EM has to allow to configure “Transport Address and QoS”, “ToP”, “BTS Routing” and “DCN Routing”as well as “IP Filtering” in I-HSPA mode. No changes to the input masks are needed compared to non I-HSPA mode

• The I-HSPA transport interface should be connected to EIF3. The operator can choose either to use the optical interface or an electrical interface to connect the transport network; the operator should not use VLAN 1108 and 1109 for I-HSPA traffic or ToP traffic on the transport network. For outdoor connection the same cable type used to connect ADA to FCM should be used to connect ADA to EIF3

• “ToP” has to be allowed to be used as Sync source

IF1

IF4

.

.

.

.

.

.QuadLIU

XFRMOVP

Clock

3.3 V

EEPROMT°C

EMB

SPI

L In (1..4)

TRS_CLK

IDT82V2084

INT

EthernetSwitch

FE

88E6097

I2CMUX

XFROVP

PCA 9544

ToP

SFP receptacle

EIF1

EIF2

EIF3

GE

ACS/9550SRAM

MII

SGMII

I2C

NOTE: only Eth switch, no IP

routing!

RA34051EN02GLA0

System Architecture

35


Ethernet transport option is via “IFUH” unit which provides native IP support :

• ToP feature is supported with ToPA module which is mandatory in IFUH unit– OMU functions as an IP router with Network Address Translation (NAT) for ToP packets

No embedded support for ATM transport with I-BTS Ultra is provided.

IP/Eth

3G BTS Ultra ADA

OMU

DSP

IuIub

Top Master

IFUH

Top Client

AXC

Control & management planes terminated in OMU

Top traffic, IP forwarding & NAT in OMU in both directions

User plane terminated in DSP

WAMWAMWAM

DCN traffic terminated in AXC & WAM, IP forwarding in OMU in both directions, no NAT

NAT required

All these must use the same source private IP 192.168.254.140

Top Master sends packets to OMU’s public IP

AXC DCNPublic IP

No NAT required

WAM DCNPublic IP

I-BTS Ultra IPoE Configuration

ToP implementation details for IADA + IFUH:

NAT (Network Address Translation) required for ToP traffic to translate ToP client’s private IP address to OMU’s public Iu address and vice versa.

IP forwarding & NAT only for ToP traffic because ToP client must use the same IFUH’s private IP address 192.168.254.140 as U/C/M planes due to IFUHimplementation restrictions.

ToP synchronization packets use always UDP port 319 and other ToP packets port 320 in both directions

Hard coded NAT rules can be used on external ports:

•in UL translate all traffic from 192.168.254.140 with destination port 319/320 to OMU’s public IP (192.168.254.140 OMU’s IP in IP packet source address field)

•in DL map all traffic to UDP port 319/320 with destination IP 192.168.254.140 (OMU’s IP 192.168.254.140 in IP packet destination address field)

IADA commissioning phase is as with I-BTS Flexi.

RA34051EN02GLA0

System Architecture

36


I-BTS Ultra support (I-HSPA516)

In I-HSPA Release 2 the Ultra Support feature extends the scope of the I-HSPA offer to cover the cases where the I-BTS solution is based on Ultrasite WCDMA BTS allowing operator to deploy I-HSPA solution with existing Ultrasite WCDMA BTSs; in I-HSPA Release 1 the relevant NodeB generation is FlexiBTS only

The IP and the Ethernet transport options at the Iub interface for Ultrasite WCDMA BTS are according to the requirements inherited from WCDMA RU10 program (see RAN1634 “IP Based Iub for Ultrasite WCDMA BTS”)

Some functionalities implemented in Ultrasite WCDMA BTS are not required in I-HSPA Adapter as Iub is a local interface:

– ATM transport option– IP CAC– IP QoS

Shared Mast Head Amplifiers

Shared Antenna

Shared feeders

Iub/Native IP

GGSN

Gn

RNC

Iur

I-HSPA Adapter

RA34051EN02GLA0

System Architecture

37


IFUH Unit

• Applicable with– AXUA / AXUB with all BTS cabinet types

– AXCC / AXCD with exception of Metrosite / Metrosite50cabinet types

• Not applicable with Standalone AXC

• Interfaces– 2 x Fast Ethernet (FE)

– 1 x Gigabit Ethernet (GE)▪ SFP is optional

• Interface capabilities– One interface, either the first FE or the GE, is used for

trunk connectivity using “ATM over Ethernet” technology

– Remaining interfaces can be used to e.g. aggregate Ethernet traffic from other 3G BTS or 2G BTS [RU10 study item]

RA34051EN02GLA0

System Architecture

38


IP addressing example, three BTSs in the same L2 domain (IPoE)

WCDMA Flexi BTSWBTS #1

Subnet10.10.1.0/28

TRS IP10.10.1.1

BTS IP10.10.1.2

IADA-1

OMU: .1DSP: .2

IADA BTSOM IP10.10.1.3

.14

IADA subnet10.20.1.0/28

I-BTS Flexi # 1


Subnet

10.10.1.16/28

TRS IP10.10.1.17

BTS IP10.10.1.18

IADA-2


I-BTS Flexi # 2

OMU: .3DSP: .4

external transport network

SIGTRAN IP10.20.1.3

SIGTRAN IP10.20.1.1

ROUTING TABLE (downlink)to 10.10.1.0/28 via 10.20.1.1to 10.10.1.16/28 via 10.20.1.3to 10.10.1.32/28 via 10.20.1.5…

L2 switchL2 switch

NOTE: IADA BTSOM IP

address is „physically“ in OMU.


Subnet

10.10.1.32/28

TRS IP10.10.1.33

BTS IP10.10.1.34

IADA-3


I-BTS Flexi # 3

OMU: .5DSP: .6

SIGTRAN IP10.20.1.5

RA34051EN02GLA0

System Architecture

39


Outline









RA34051EN02GLA0

System Architecture

40


I-HSPA BTS Reference Configuration (IPoA)

IP over ATM (IPoA)

I-HSPAAdapter

FlexiBTS

FTMIub to/from external transport network

This connection uses the same

GigEth connection as Iub between

IADA and System Module

ATM over PDH/SDH in FTM

RA34051EN02GLA0

System Architecture

41


IPoA Transport Ref Config

RA34051EN02GLA0

System Architecture

42


Ethernet transport option is via ADA (IHSW-33):• Iub‘ internal interface is via ADA L2 Switch Port#0• External interfaces (e.g. Iu/Iur) are via ADA L2

Switch Port#1.• ToP feature is not supported.

I-BTS Flexi IPoA Configuration

ATM transport option is via FTM sub-module:• Iub‘ internal interface is via ADA L2 Switch Port#0• External interfaces (e.g. Iu/Iur) are via FTM module port;

System Module

BTS Switch

FTM Module (e.g. FTPB)FSP

ADA

ADA L2 Switch Port#0

FTM Port

SDH/PDH

Iub’

ADA L2 Switch Port#1

ATM data flow

Eth

IP/ATM and IP/Ethernet transport options cannot be simultaneously active!

FTM sub-modules supported for ATM and Ethernet transport options are:• FTPB: 8xE1/T1/JT1 symmetrical (IMA) ARAN940/ARAN946/ARAN941).

• FTEB: 8xE1 coaxial (IMA) (ARAN940).

• FTOA: 1xSTM-1/VC-4 (No IMA) (ARAN942).

• FTFA: 2xFlexBus (IMA) (ARAN939).

• FTHA: 16xE1/T1 (ARAN1324).

• FTFA: 16xE1 (Add/Drop Capability for FTFA) (ARAN1325).

• FTIA: 4xE1/T1/JT1 2xFE, 1GEo.

• FTJA: 4xE1/T1/JT1 coax 2xFE, 1GEo.

• FTIB: 4xE1/T1/JT1 2xFE, 1GEo +ToP

In earlier versions of documents FTIB was not allowed with IPoA. However, FTIB has been since tested out successfully in lab with IPoA.

RA34051EN02GLA0

System Architecture

43


IP

SCTP

SCCP

RNSAP’

M3UA

Ethernet

IP

UDP

L2 switch

L2 switch

L2 switch

Example: Iur control plane over IP/Ethernet over ATM between Adapters

L2 switch

Adapter 1OMU

Ethernet

IP

UDP

L1

ATM

AAL5

Ethernet

IP

UDP

L1

ATM

AAL5

IP

SCTP

SCCP

RNSAP’

M3UA

Ethernet

IP

UDP Transport module 1 Transport module 2

ADA – FTMinternalconnection

ADA – FTMinternalconnection

ADA – ADA connection

Iur over ATM

In all Adapter external interfaces,except toward BTS, also ATM transportis available, but then BTS’s “FTM” moduleis used for this. Method is same for all interfaces (as presented within this case).

Adapter 2OMU

Note: not possible for ultra

RA34051EN02GLA0

System Architecture

44


I-BTS Flexi: 3VCCs for Iu, Iur/Iur* and DCN (UL direction)

OMU [RNC Application]

Public: 130.1.0.101 connection to CN (i.e. Iu-PS CP, Iu-CS CP, Iur/Iur* CP, DCN)

Private: 192.168.255.143BTS internal network including ADA

Port#5 (L2 Switch)

Port#4 (L2 Switch)

DSP

Public: 130.1.0.201 connection to CN (i.e. Iu-PS UP, Iur/Iur* UP)

Private: 192.168.255.142BTS internal network including ADA

FTM

Private: 192.168.255.129

DEST: 130.2.0.101

DEST: 130.2.0.201

DEST: 130.2.0.201

Iu-PS CPIu-CS CPIur/Iur* CPDCN

Iur/Iur* UP

Iu-PS UP

UDP port#1002

UDP port#1011

UDP port#1010

130.2.0.201 over UDP port#1010 to 192.168.255.129 MAC FTM



ATM0 Iu-PS UP UDP Port: 1011 VP=xx/VC=yyy

ATM1 Iur/Iur* UP UDP Port: 1010 VP=xx/VC=yy

OMU AA0 Iu-PS/Iu-CS/Iur/Iur* CP, DCN UDP Port: 1002 VP=xx/VC=yyy

DSP

FTM

FTM is not IP router, it just forwards IP packets from VCC to L2 switch and adds UDP/IP layer

ADA (i.e. DSP/OMU [RNC Appl] selects the correct UDP port so that traffic will be forwarded to the correct VCC

RA34051EN02GLA0

System Architecture

45


I-BTS Flexi: 3VCCs for Iu, Iur/Iur* and DCN (DL direction)

OMU [RNC Application]

Public: 130.1.0.101connection to CN (i.e. Iu-PS CP, Iu-CS CP, Iur/Iur* CP, DCN)

Private: 192.168.255.143

BTS internal network including ADA

Port#5 (L2 Switch)

Port#4 (L2 Switch)

DSPPublic: 130.1.0.201connection to CN (i.e. Iu-PS UP, Iur/Iur* UP)

Private: 192.168.255.142 BTS internal network including ADA

FTM

Private: 192.168.255.129

DEST: 130.2.0.101

DEST: 130.2.0.201

DEST: 130.2.0.201

Iu-PS CPIu-CS CPIur/Iur* CP

DCN

Iur/Iur* UP

Iu-PS UP

UDP port#1002

UDP port#1011

UDP port#1010

130.2.0.201 over UDP port#1010 to 192.168.255.142

130.2.0.201 over UDP port#1011 to 192.168.255.142

130.2.0.101 over UDP port#1002 to 192.168.255.143

FTM is not IP router, it just forwards IP packets from VCC to L2 switch and adds UDP/IP layer

Static mapping in FTM defines

VCC ↔ UDP/IP/MAC

ATM0 Iu-PS UP UDP Port: 1011 VP=xx/VC=yyy

ATM1 Iur/Iur* UP UDP Port: 1010 VP=xx/VC=yy

OMU AA0 Iu-PS/Iu-CS/Iur/Iur* CP, DCN UDP Port: 1002 VP=xx/VC=yyy

DSP

FTM

RA34051EN02GLA0

System Architecture

46


IP addressing (IPoA)

For IP over ATM • One IP over ATM interface for OMU (AA0). This is for Iur/Iur* CP, Iu-PS CP, Iu-CS CP, O&M DCN traffic

• One IP over ATM interface for DSP (ATM0). This is for Iu-PS UP

• One IP over ATM interface for DSP (ATM1). This is for Iur/Iur* UP.

• Addresses are created as numbered interfaces in OMU and DSP (every IPoA interface has its own IP address)

• Far-end address needed at the multiservice router (can be numbered or unnumbered)

• BTS O&M addressing is as in the IPoE case

RA34051EN02GLA0

System Architecture

47


IP addressing example (IPoA)

• Numbered IPoA interfaces used at the router in this example

RA34051EN02GLA0

System Architecture

48


IP addressing (IPoA, ZQRI output)

< ZQRI;LOADING PROGRAM VERSION 12.9-0I-HSPA IPA2800 2009-06-04 13:40:13INTERROGATING NETWORK INTERFACE DATA

IF ADM IF ADDRUNIT NAME STATE MTU PRIORITY TYPE TYPE IP ADDRESS--------- --------- ------ ---- --------- ---- ---- -----------------------OMU-0 AA0 UP 1464 - N P 10.10.1.1/30

->10.10.1.2 EL0 UP 1500 - P 192.168.254.143/24 VLAN1 UP 1496 - P 192.168.1.143/24 VLAN2 UP 1496 - P 192.168.255.143/24

P 10.16.71.51/29 DSP-0 ATM0 UP 1464 - N P (10.10.2.1)/30

-> 10.10.2.2 ATM1 UP 1464 - N P (10.10.3.1)/24

-> 10.10.3.2 ETH1.1 UP 1496 - P (192.168.1.142)/24 ETH1.2 UP 1496 - P (192.168.255.142)/24

COMMAND EXECUTED

• NOTE: VLAN3 not needed with IPoA

• HINT: one can define one Iur* subnet and create the ATM1 interface to that subnet all Iur* user plane is sent via this interface because IP stack sees all Iur* addresses as directly connected no need for route configuration for every neighbour I-BTS. (Parameter: ADASC/DSPATM1NetMask)

RA34051EN02GLA0

System Architecture

49


Outline









RA34051EN02GLA0

System Architecture

50


UL

• ToP traffic is terminated at Top Master;

• ToP frames are directly forwarded to the ToP Master;

DL

• ToP traffic is switched by the FTIB/FIIB L2 switch towards the ToPA module;

• Incoming ToP frames are a subset of the overall data flowing through the CN connection;

• ToP frames are directly forwarded (switched) to the ToPA module embedded in the FTIB module; all remaining traffic having ADA as destination is switched to the FTIB Ethernet Port “EIF3” connected to the ADA L2 Switch Port#1

• ToPA module IP address has to be in the same subnet with OMU and DSP

Timing over Packet feature (ARAN1254)

U/C/M Plane frames

DL ToP frames


UL ToP frames

Internal Iub’

System Module

BTS Switch

FTIB

FSP

ADA

ToPA

Port#0 (Iub) Port#1 (Transport)

3G BTS Flexi

MSC

SGSN

GGSN

SAS

RNC

I-BTS

ToP Master

OMSOMU

Intel Westport

Transport Switch

DSP

Eth Eth

EIF1/2

EIF3 IP/Eth

RA34051EN02GLA0

System Architecture

51


Synchronization from TDM Traffic Interfaces

• Synchronization is achieved using Flexi Transport sub-module available for:– E1/T1/JT1– STM-1– FlexBus

• This solution applies in case of ATM transport option via the following FTM sub-module:– FTPB: 8xE1/T1/JT1 symmetrical [IMA] ARAN940/ARAN946/ARAN941) – FTEB: 8xE1 coaxial [IMA] (ARAN940)– FTOA: 1xSTM-1/VC-4 [No IMA] (ARAN942)– FTFA: 2xFlexBus [IMA] (ARAN939)– FTHA: 16xE1/T1 (ARAN1324)– FTFA: 16xE1-Add/Drop Capability for FTFA (ARAN1325)– FTIA: (ARAN940/ARAN946/ARAN941) – FTJA: (ARAN940/ARAN946/ARAN941)– FTIB

• Sync from TDM can also be used with IPoE• With IPoE the TDM interface carries no traffic (only sync), see next slide

I-BTS Flexi

TDM TDM

RA34051EN02GLA0

System Architecture

52


Synchronization from 2.048MHz G.703 signal

• 2.048MHz G.703 signal• SYNC input is used at the System Module• I-HSPA traffic is via Ethernet port on ADA (IHSW-33)

I-BTS Flexi

BTSE1/T1

IP / Ethernet

TDM

Eth

SYNC

SYNC

2.048MHz

G.703

RA34051EN02GLA0

System Architecture

53


Synchronization from GPS

Flexi BTS System Module

Flexi BTS RF Modules

-48VDCPPS

FSEG Mediator

FPF Power Distribution assembly FTM Transmission assembly (FTPA in this figure)

FCM Con trol and Multiplexing assembly / FSP Signal processing assembly

MDR14 MDR26MDR36

LMP5 x Optical (duplex LC)

connectors

8 x RJ- 48C (in this case FTPA)4 pcs Multi-beam

connectors

F F F F

FSEG

SYNC port(995098_) 2.4m

48VDC BB extension(995083)

GPS Port(471606 30m, 47xxxx 100m)

Grounding

FYGA

(471442_)

Solution includes:

• GPS antenna with integrated receiver

• In I-HSPA Release 2 the Mediator (FSEG) between FlexiBTS System Module and GPS receiver is no more required!

RA34051EN02GLA0

System Architecture

54


Outline








• I-OMS Overview


RA34051EN02GLA0

System Architecture

55


OMS

• One OMS can control several I-BTSs

• NTP server for I-BTSs can run in OMS

• NTP server IP address is OMS IP address

• Runs NTP client for NTP server in NetAct, to derive master time

RA34051EN02GLA0

System Architecture

56


OMS HW

For the I-HSPA G5 OMS:• HP ProLiant DL360 G5 1U rack-mount server• 8 GB memory• two 146 GB Serial Attached SCSI (SAS) hard drives• an external monitor (with VGA cable) and external keyboard (with PS/2 or

USBcable) connected to the HP ProLiant server• 19-inch rack

For the I-HSPA G6 OMS:• HP ProLiant DL360 G6 1U rack-mount server• 12 GB memory• two 146 GB 2,5" SFF SAS Hot Plug hard drives• an external monitor (with VGA cable) and external keyboard (with PS/2 or

USBcable) connected to the HP ProLiant server• 19-inch rack

RA34051EN02GLA0

System Architecture

57


IP Planning requirements for OMS

• OMS has two Ethernet interfaces

• Two IP addresses are needed for OMS, they should be allocated from the same subnet

• The “southbound” IP address of OMS is configured in IADA during commissioning (parameter: ADASC/OMSIpAddress)

• Northbound address is for NetAct

• ADASC/NTPServerIPAddress is the same as ADASC/OMSIpAddress, when OMS is the NTP server for I-BTSs

RA34051EN02GLA0

System Architecture

58


Plan Creation/editing Overview

• I-BTS parameters can be browsed and edited in OMS using Network Element Parameter Editor

• Plans can be downloaded to I-BTS and activated

• Plans can be uploaded from I-BTS as an XML file

• The XML file can be loaded to Plan Editor

• Mass creation/editing of plans takes place in Plan Editor and/or Excel

• NOTE: also signalling parameters can be downloaded to I-BTS using an xml file (no MML needed)

• The same functionality is available from NetAct in which case OMS is a mediator (NetAct does not access I-BTS directly, but via OMS)

RA34051EN02GLA0

System Architecture

59


CM from NetAct versus CM from OMS

RA34051EN02GLA0

System Architecture

60


InterfacesProtocols

I-BTS logical interfaces according to the 3G reference model are:

• Iu-CS-c: it is between I-BTS and the MSC

• Iu-PS interface which is logically divided into two parts:

– Iu-PS-c: it is between I-BTS and SGSN handling control data

– Iu-PS-u: it is between I-BTS and SGSN/GGSN handling user data

• Iur* interface: it is between I-BTS and I-BTS and up to 32 instances can be supported

• Iur: it is between I-BTS and 3G RNC; only 1 instance; it is due to I-BTS Sharing feature→ Iur+Iur* = up to 32 instances as maximum

• Gn-u: it is between I-BTS and GGSN, handling user plane data; it is due to direct tunnel functionality (also standardized in 3GPP)

• O&M: it is between I-BTS and OMS/NetAct

• Iu-PC: it is between I-BTS and SAS for LCS services

RA34051EN02GLA0

System Architecture

61


Outline








• I-OMS Overview


RA34051EN02GLA0

System Architecture

62


I-BTS Flexi

ProtocolsIu-CS: Control Plane

IP/Ethernet option IP/AAL5/ATM option

The main task of the Radio Access Network Application Part (RANAP) is to set up and release dedicated connections, with defined capacity and QoS performance, between the UE and the CN. Such a dedicated connection is called Radio Access Bearer (RAB)

The Signalling Connection Control Part (SCCP) offers direct signalling connections for each active UE: SCCP connections are used for differentiating the signalling transactions intended for different subscribers

The Stream Control Transmission Protocol (SCTP) is an alternative to the unreliable UDP and the reliable but slow TCP protocol. SCTP is described in IETF RFC 3286

IP shall be supported according to IP version 4 [RFC791] even though 3GPP specification requires IPv6 for IP option

The MTP3 User Adaptation Layer (M3UA) supports the transport of SCCP messages over IP using the services of SCTP. M3UA is described in RFC 3332

MSS

IPv4

SCCP

ATM

AAL5

PDH/SDH

RANAP

Iu-CS

I-BTS Flexi MSS

Iu-CS

Ethernet-PHY

Ethernet-MAC

IPv4

SCTP

M3UA

SCCP

RANAP

M3UA

SCTP

RA34051EN02GLA0

System Architecture

63


I-BTS Flexi

ProtocolsIu-PS: Control Plane


The main task of the Radio Access Network Application Part (RANAP) is to set up and release dedicated connections, with defined capacity and QoS performance, between the UE and the CN. Such a dedicated connection is called Radio Access Bearer (RAB)

The Signalling Connection Control Part (SCCP) offers direct signalling connections for each active UE: SCCP connections are used for differentiating the signalling transactions intended for different subscribers

The Stream Control Transmission Protocol (SCTP) is an alternative to the unreliable UDP and the reliable but slow TCP protocol. SCTP is described in IETF RFC 3286

IP shall be supported according to IP version 4 [RFC791] even though 3GPP specification requires IPv6 for IP option

The MTP3 User Adaptation Layer (M3UA) supports the transport of SCCP messages over IP using the services of SCTP. M3UA is described in RFC 3332

SGSN

IPv4

SCCP

ATM

AAL5

PDH/SDH

RANAP

Iu-PS

I-BTS Flexi SGSN

Iu-PS

Ethernet-PHY

Ethernet-MAC

IPv4

SCTP

M3UA

SCCP

RANAP

M3UA

SCTP

RA34051EN02GLA0

System Architecture

64


ProtocolsIu-PS: User Plane / Gn “One Tunnel Solution”:

IP/Ethernet option IP/AAL5/ATM optionGPRS Tunnelling Protocol (GTP). At the Iu-PS interface, a connection-oriented data bearer is obtained by forming a ”tunnel” between the I-BTS and the SGSN. This tunnel is then extended from the SGSN to the GGSN

ATM

AAL5

IPv4

UDP

GTP-U

Iu-PS User Plane Protocol

PDH/SDH

Ethernet-PHY

Ethernet-MAC

IPv4

UDP

GTP-U

Iu-PS User Plane Protocol

One tunnel solution: I-BTS is directly connected to GGSN

UDP shall be supported according to IETF RFC768. UDP protocol will be used for the transport of data in the User plane. On Iub interface BTS ignores UDP checksum of DL packets. On UL packets BTS fills checksum 0 to mark that checksum is not used. The UDP checksum generation and verification shall be supported on Iu and Iur interfaces

I-BTS

RA34051EN02GLA0

System Architecture

65


ProtocolsIur*/Iur: Control and User Plane

Iur Control Plane


Iur User Plane

Iur User Plane

Ethernet-PHY

Ethernet-MAC

IPv4

SCTP

RNSAP

SCCP

Iur Control Plane

IPv4

SCTP

M3UA

RNSAP

SCCP

ATM

AAL5

PDH/SDH

ATM

AAL5

IPv4

UDP

PDH/SDH

PCH

FP

FACH

FP

DCH

FP

Ethernet-PHY

Ethernet-MAC

IPv4

UDP

PCH

FP

FACH

FP

DCH

FP

M3UA

RA34051EN02GLA0

System Architecture

66


1

2

Blue boxes indicate “IP over Ethernet” option

Green boxes indicate “IP over ATM” option

ProtocolsO&M and Iu-PC interfaces

The O&M interfaces or the IuPC interface towards the Stand-alone A-GPS Serving mobile location centre (SAS) are based either on IP over Ethernet or IP over ATM (IPoA) transport

• IP over Ethernet transport is supported via the I-HSPA Adapter

• IP over ATM transport is supported via the FlexiBTS transmission module

BTS & AdapterO&M protocolsBTS & AdapterO&M protocols

IPIP

AAL5AAL5

ATMATM

PHYPHY

IPIP

EthernetEthernet

PCAP (Position Calculation Application Part)

PCAP (Position Calculation Application Part)

SCCPSCCP

M3UAM3UA

SCTPSCTP

O&M Interfaces Iu-PC Interface

TCP/FTPTCP/FTP

IPIP

PHYPHY

ATMATM

AAL5AAL5 IPIP

EthernetEthernet

TCP/FTPTCP/FTP

RA34051EN02GLA0

System Architecture

67


Transport Network ScenariosI-BTS Flexi (ADA+FTxx): ATM over E1/T1/JT1/STM-1 Transport

GGSN

SGSN

AAL5

(IMA)

TDM PHY

(IMA)

TDM PHY

AAL5

ATM ATM

L4

(Carrier) IP

Eth PHY

Eth MAC

Eth PHY

I-HSPA Adapter

L4

IP

LLC/SNAP LLC/SNAP

Eth MAC

IP

IP Router

TDM

System Module with FTM

Sub-Modules

RNC

IPEth

I-BTS Flexi

The FTM Sub-modules supported are the following:

FTPB: 8 x E1/T1/JT1 symmetrical (IMA) (ARAN940/ARAN946/ARAN941)

FTEB: 8 x E1 coaxial (IMA) (ARAN940)

FTOA: 1 x STM-1/VC-4 (No IMA) (ARAN942)

FTFA: 2 x FlexBus (IMA) (ARAN939)

FTHA: 16 x E1/T1 (ARAN1324)

FTFA: 16 x E1 (Add/Drop Capability for FTFA) (ARAN1325)

NO FTIB

External interfaces

I-BTS Flexi ATM I-BTS Ultra IP

I-BTS Flexi IP

I-BTS Flexi CNRouterIP over AAL5 IP over Ethernet

RA34051EN02GLA0

System Architecture

68


Transport Network ScenariosFlexbus Transport

AAL5

(IMA)

TDM PHY

(IMA)

TDM PHY

AAL5

ATM ATM

L4

(Carrier) IP

Eth PHY

Eth MAC

Eth PHY

L4

IP

LLC/SNAP LLC/SNAP

Eth MAC

IP

I-BTS Flexi

M x E1/T1MWR-IU MWR-IU

M x E1/T1M x E1/T1

IP Router orEthernet Switch

GGSN

SGSN

RNC

I-BTS Ultra

I-BTS Flexi with IP

RA34051EN02GLA0

System Architecture

69


Transport Network ScenariosI-BTS Flexi (ADA+FTIB): IP/Ethernet Transport

I-HSPA Adapter


System Module + FTIB

IP/Ethernet

I-BTS Flexi

Eth MAC

L4

Eth PHY

IP

Eth MAC

Eth PHY

IP

Eth PHY

Eth MAC

L4

Eth PHY

(Carrier) IPEth MAC

External interfaces

GGSN

SGSN

RNC

I-BTS Ultra

I-BTS Flexi with IP

RA34051EN02GLA0

System Architecture

70


Transport Network ScenariosI-BTS Ultra: IP/Ethernet Transport

I-HSPA Adapter

IFUH card

IP/Ethernet

I-BTS Ultra

Eth MAC

L4

Eth PHY

IP

Eth MAC

Eth PHY

IP

Eth PHY

Eth MAC

L4

Eth PHY

(Carrier) IPEth MAC

External interfaces

GGSN

SGSN

RNC

I-BTS Ultra

I-BTS Flexi with IP


RA34051EN02GLA0

System Architecture

71


I-BTS Flexi - IP/AAL5/ATM TransportATM Service Categories

• ATM Service Categories “CBR”, “UBR” and “UBR+” shall be implemented according to AF-TM-0121.000 version 4.1 and AF-TM-0150.000

• The ATM service category UBR has been extended by ATM Forum standard to support an additional parameter Minimum Desired Cell Rate (MDCR). An UBR implementation that supports the MDCR parameter is commonly denoted as UBR+

• The “UBR+” service category is specified if the “MDCR” (Minimum Desired Cell Rate) parameter value is set to more than “0”. The “UBR+” service category includes the “UBR” service category as well

The following ATM service categories shall be supported:

ATM Layer Service Category User configurable parameters

Constant Bit Rate (CBR) PCR, CDVT (1)

Unspecified Bit Rate (UBR) PCR, MDCR=0

Unspecified Bit Rate+ (UBR+) PCR, MDCR>0 (2)

Table: Service categories and traffic parameters

(1) CDVT parameter is mandatory(2) MDCR ≤ PCR for an UBR+ connection

RA34051EN02GLA0

System Architecture

72


I-BTS Flexi - IP/AAL5/ATM TransportUBR+ for Control/User/Management Plane (ARAN1192)

• This feature applies to I-BTS Flexi only; I-BTS Flexi can use ATM as transport layer towards other ATM network elements (e.g. other I-BTSs or Core Network Elements); Transmission paths are provided by PDH/SDH

• ATM service category UBR+ is introduced for Iu-CS (C-Plane), Iu-PS, Iur and DCN interfaces• UBR+ service category increases transport efficiency and enables to benefit from statistical multiplexing

gain in RAN transport• MDCR is a VCC parameter that represents the minimum ATM cell rate that should be granted to a VCC.

Cell rates above the MDCR share a common bandwidth among the VCCs configured as UBR/UBR+ under control of UBRshare parameters

• UBR+ solution provides the parameter called UBRshare to favour individual UBR+ connections. How much BW a UBR+ connection will get above its MDCR guarantee depends on the current traffic conditions and on the ratio of that connection's UBRshare attribute to the sum of all UBRshare attributes of all UBR+ connections

VCC1 CBR (always guaranteed)

MDCR for VCC3 UBR+ (guaranteed)

MDCR for VCC2 UBR+ (guaranteed) Physical link

capacity

Could takephysical link

capacity, if noother traffic

present

Could takephysical link

capacity, if noother traffic

present

VCC1 (CBR)

VCC2 (UBR+)

VCC3 (UBR+)

RA34051EN02GLA0

System Architecture

73


AAL5

(IMA)

PDH/SDH PHY

(IMA)

PDH/SDH PHY

AAL5

ATM ATM

L4

(Carrier) IP

Eth PHY

Eth MAC

Eth PHY

I-HSPA Adapter

L4

IP

LLC/SNAP LLC/SNAP

Eth MAC

IP

TDM

System Module with FTM

Sub-Modules

RNC

IP/Ethernet

Transport Network ScenarioI-BTS Flexi IP/AAL5/ATM Transport with I-BTS Sharing feature

I-BTS Flexi

I-BTS Flexi RNCRouterIP/AAL5/ATM IP/Ethernet

Iur


RA34051EN02GLA0

System Architecture

74


I-HSPA O&M Architecture

I-HSPA O&M architecture

I-HSPA OMS

AdapterI-HSPA BTS

NetAct

NWI3 (Same services provided as in RNC)

IPSec pipe

BTS O&M interface (from WiMAX)

BTS O&M interfaceIub over IP (Fixed configuration) RNW

DB Iu-ps over IP (over ethernet) SGSN/GGSN(Direct Tunnel to GGSN)

Optional: ATM connectionby FTM Iu-ps over IP over ATM

LCS/SMLCIu-pc over IP (over ethernet)

I-HSPA BTSIur over IP (over ethernet)

External IP ROUTERas WiMAX

FTP

Optional: External ATM-IP ROUTER

BTS Master O&M

BOIMED

PMFMSWmng

HWmng

Planmng

LicenMng

Secmng

Topology

EM

ParameterEditor

Topology

SWmng

FM

LicenMng

PM

From WiMAX OMS

From WiMAX OMS

From RNC OMS

Iu-pc over IP over ATM

AAL5ATML1

UDPIP

Ethernet

AAL5ATML1

UDPIP

Ethernet

Iur over IP over ATM

BTS EMsBTS EMs

TelnetMML interface (locally) IPSec pipe

IPSec pipe

IPSec pipe

RA34051EN02GLA0

System Architecture

75


I-BTS FlexiTermination of BTSOM and role of FTM

FTM, which is in charge to terminate TLS, terminates all management connections: it means that all O&M traffic is going via FTM even in case the content is sometimes transparent (e.g. file transfers towards FCM)

Related features implemented in FTM are:• Secure BTS O&M• Secure File Transfer• User Management• Log Management• Certificate Management• Secure Element Manager

The functionality is implemented in the “Site Management Agent” (SMA)

Agent

SiteAgent

OMS

NetAct

FTMFCM

Agent

BTSOMMaster

I-BTS Flexi

RA34051EN02GLA0

System Architecture

76


Site Management Agent (SMA)Site Management Agent (SMA) (WBTS4.0; I-HSPA-Adapter [RAS07])

• RUIM (Remote User Information Management) for authentication only:– Remote User Accounts on LDAP server– Local User Accounts on NE, only one per NE– Authentication (username and password) and Authorization (permissions)

• FTP Interface: FTM and FCM maintain own public IP address for FTP

Site Management Agent (SMA) Evolution (WBTS5.0)• Transport Layer Security (TLS / SSL) for the BTSOM/ASN.1 management connection• Secure File Transfer between NMS and BTS based on HTTPs• RUEM (Remote User Event Log Management): all management operations are logged for off-line evaluation• Certificate Management Protocol (CMPv2 support)

NWI3

XoH

/

TRS BTSRUIM RUEMSOAP

BTSOM/ASN1

XoH

ASN.1 Gateway

XoH Gateway BTSOM

TLS

TRSOM

RNS Split

SMA

NWI3

XoH

TRS BTSRUIM RUEM

BTSOM/ASN.1

XoH

ASN.1 Gateway

XoH Gateway

TLS

RNS Split

File Manager

http

httpTFTP

Cert

MgmtCMPv2 SMA

BTSOM/ASN.1

WBTS4.0 WBTS5.0

BTSOM/ASN.1

BTSOM

Documents

Chichi chacha