Chichi chacha

System Architecture

Academy course:
I-HSPA Operation and Maintenance
Release 2.0
System Architecture

1 © Nokia Siemens Networks RA34051EN02GLA0

RA34051EN02GLA0 1

System Architecture

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.


RA34051EN02GLA0 2

System Architecture

Document change history

Date Version Name Change comment

12 Nov 2009 1.0 R. Benson Initial version


RA34051EN02GLA0 3

System Architecture

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 4

System Architecture

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-BTS
Network 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/Gn
interfaces

 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 5

System Architecture

I-HSPA Network Architecture
An Evolutionary Step towards LTE

MGW PSTN
NodeB RNC MSC-S

Radio Network SGSN GGSN Internet
Core Network

I-HSPA
For R99 services
SGSN
I-BTS
GGSN Internet
Radio Network Core Network

LTE
eGSN-c
eNodeB
eGSN-u Internet
Radio Network Core Network

RA34051EN02GLA0 6

System Architecture

I-HSPA Rel-2
• HSDPA calls supported by I-BTS
• CS calls served in I-BTS also
NetAct
– I-BTS acts as Drift RNC
MSS
– RNC acts as Serving RNC
• IuPS cp
• Timing Over Packet support • IuPS up (Gn) Eth IuCS cp
• IuCS cp DCN
I-BTS • Iur to other I-BTS’s Network
• Iur to RNC I-OMS
Eth • ToP
Eth SGSN
2+2+2 • I-OMS

Eth IuPS cp
IuPS up
IP /
Iur IP / Ethernet Eth GGSN
Eth
IuPS up
I-BTS
Iur is used for CS
and CS+PS calls RNC
Eth IuCS cp
2+2+2 IuCS up
ToP Master Eth
IuPS cp
Iur is used for soft IuPS up
handover between VPN GW
I-BTS’s


RA34051EN02GLA0 7

System Architecture

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) RN4.0 CD2.0
And RN4.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; SG6 CD9;
SG7 CD2 SG7 CD2
Flexi ISN (GGSN) FI3.2 PCD2.2 FI4.0

• SIGTRAN activated in CS and PS core


RA34051EN02GLA0 8

System Architecture

Outline
examples


RA34051EN02GLA0 9

System Architecture

I-BTS Flexi Mechanics
External
transport
network
I-HSPA Adapter

10/100/1000 BaseT Ethernet
Fans and casing are missing from figure
• 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

I-BTS Flexi

Naming convention in this slide set:
IADA + FlexiBTS = I-BTS Flexi,
IADA + UltraBTS = I-BTS Ultra


RA34051EN02GLA0 10

System Architecture

System Module Interfaces FTM
transmission
Connection to sub-module
IADA (here: 8x E1/T1)

Input for
external sync


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 11

System Architecture

IADA HW architecture

DC/DC
Pentium
1.8GHz
1GB DDR2
1MB boot
Flash
Intel Temp sensor
DMX FPGA chipset

USB 2.0
Pentium board
1000Base-T/BX RJ-45
1 GB
SGMII Local management Port
Flash drive L2
256MB
DDR2 Switch GbE BTS interface
PHY
Iub/Gn
SGMII RJ-45
DSP SGMII Ethernet
transport interface
SERDES (electrical or optical)
SFP
(Optional)
Gn
DC/DC
-48V DC Main DC/DC Unit status
Temp. control
Converter LED


RA34051EN02GLA0 12

System Architecture

IADA logical SW architecture

I-HSPA Adapter
DSP Module Pentium Module

DSP application SW “RNC” application SW

DSP platform SW IPA platform SW

OSEck DMX
Operating System Operating System

Intel Pentium processor
Faraday DSP

To external
transport network
to BTS
VLAN4
VLAN2 VLAN3
VLAN2

VLAN3
Ethernet L2 switch

NOTE: VLANs
supported only
internally, not for
external traffic

RA34051EN02GLA0 13

System Architecture

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

OMU
-Load control
-RRM RNC OMU (Operation and Management Unit)
-Signalling link control -RNC HW configuration mgmt
-Common channels control -Alarm system &Recovery functions
-Alarm system -Performance mgmt
-Performance mgmt -RNW parameter database & management
-RNW mgmt
-RNW database RNC RRMU (Radio Resources Mgmt Unit)
-RNC centralized RRM tasks, e.g. RC3
-Adapter unit mgmt
-FlexiBTS Iub RNC RSMU (Resource and Switch
-Capa Licence key Management Unit)
-SW mgmt
Adapter Unit O&M CCH SW (Mac-C) - RNC centralized resources management
-IPSec
U-plane SW
RNC DMCU (Data and Macro Diversity
Combining Unit)

DSP
-Macro diversity hand-overs
Pentium Computer SW DSP Computer SW
-Packet data processing
DMX OSEck -Radio interface L2 (PDCP, RLC..)

Pentium DSP RNC GTPU (GTP unit)


RA34051EN02GLA0 14

System Architecture

I-HSPA Adapter Hardware
Ethernet Switch Module: Marvell 88E6131
 Only Ports #0, #1, #2, #4 and #5 are used
I-HSPA Adapter
 Interfaces OMU
- 3 x Base-Tx interfaces connected to RJ45 connectors: Intel CPU Pentium
• One interface is Iub interface (towards 3G BTS) [Port#0] (LS8MAN)
• One interface is Transport interface [Port#1]
• One interface is Local management interface [Port#2]; Port #5
Port #1 Transport
Port#2 cannot be used as a redundant link connected to Site Local MGMT
Iub Port #0 L2 Switch Port #2
router
Port #6 SERDES
- SGMII/SERDES interface to DSP [Port#4] Port #4

- Base-BX/SERDES interface to Pentium module (to Intel 82572EI)
[Port#5] DSP
- SERDES interface to optical SFP module (optional transport (LS8DSP)
interface) [Port#6] is not used

 Configuration for switch is loaded from EEPROM Iub Port to Iub interface
- EEPROM is connected to switch with SPI-interface Transport Port to Transport interface
- EEPROM image can be loaded from Pentium (through chip set Local MGMT Port to Local Management
GPIO-pins) SERDES Port to SFP module optical Ethernet
• Switch needs to be reset before a new configuration is
loaded to switch
Message transportation protocols between OMU and DSP
 Messaging between OMU and DSP unit is based on DMX messages
transferred via EMB (Ethernet based Message Bus). There are switch Message
management DMX processes running in OMU (LS8MAN) and DSP
(LSDSP). EMB messaging uses Nokia proprietary protocol DMX Message protocol

Ethernet


RA34051EN02GLA0 15

System Architecture

I-HSPA Adapter LAN architecture
DSP Switch
OMU
eth1 LMP
EL0
eth1.1 VLAN 1 tag 1
eth 1.2 VLAN 2 tag 2
Iub
eth0
VLAN 3 tag 3
eth 0.3
Iu-PS/CS

ext2 ext3 Iub

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 16

System Architecture

I-BTS Flexi: FTM Hardware
Flexi WCDMA BTS Flexi Transport (FTM Sub-modules) Core Interface
FTPB
FTCC + FIPB

FTEB
FTCC + FIEB

FTFA FTCC + FIFA
PDU Flexi Transport
FTOA FTCD + FIOA

Flexi BTS System Module Core FTHA FTCC + FIHA

FTIA FTCC + FIIA

FTJA FTCC + FIHA

FTIB FTCC + FIIB
FTM
FTPB FTOA FTFA FTEB

IH1 IH1 IH1 IH1
1. System Module with integrated BB.
FTJA FTIA FTHA FTIB
2. System Module with embedded
separate transport sub-module.
3. BTS O&M and Transport distributed
IH1 IH1 IH1 IH2
to 2 boards with 2 HW/SW systems.
FTM2.0 Release FTM2.1 Release FTM5.0 Release


RA34051EN02GLA0 17

System Architecture

I-BTS Flexi: FTM Hardware (2)
Transport Sub-Module Interface Number of Notes
Type Type Interfaces
FTPB E1/T1/JT1, symmetrical 8 ATM over PDH with IMA
(8xRJ48)
FTEB E1, coaxial 8 ATM over PDH with IMA
(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 ATM over 16xE1 with IMA
(2xTNC)
FTIA E1/T1/JT1, Symmetrical 10/100Base- 4 PDH (4xRJ48) ATM over PDH with IMA
TX, (GE1) 2(31) Ethernet (RJ45)
FTIB E1/T1/JT1, Symmetrical 10/100Base- 4 PDH (4xRJ48) ATM over PDH with IMA, ToP
TX, (GE1) 2(31) Ethernet (RJ45)
FTJA E1, Coaxial 10/100Base-TX, (GE1) 4 PDH (8xSMB) ATM over PDH with IMA CES
2(31) Ethernet (RJ45) (ATM over Ethernet)

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

• 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 18

System Architecture

Outline
examples


RA34051EN02GLA0 19

System Architecture

I-HSPA Adapter
Internal VLANs and Flows ADA L2 Switch

Port#5 - OMU
ADA L2 Switch supports in IP stack of OMU and DSP the Port Based VLAN PVID=1
mechanism according to VLAN 802.1Q standard. Port based VLAN is used for PVID=2
PVID=3
security reasons and it shall ensure that there is no direct connection between Iub PVID=4
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 Port#1-Transport
system is up-and-running and is fully capable of processing traffic: untagged
Iub CN/OMS
 Internal VLAN grants traffic separation between external traffic (Network L2 Port#0
VLAN3
domain) and internal traffic (I-BTS L2 domain) VLAN2 PVID=2
VLAN4
 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;
Local MGMT
 only Ethernet ports of the C-plane and U-plane processors are in the same
Port#2 - LMT VLAN1
VLAN as the external Ethernet ports
untagged
 It shall be possible to configure static MAC addresses to support MAC-based
VLANs; Port #4 - DSP
PVID=1
 External VLAN are not supported; PVID=2
 Packets are forwarded only to the Ports inside the VLAN that is defined in the PVID=3
VID tag PVID=4

 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

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


RA34051EN02GLA0 20

System Architecture

Internal VLANs

EXT 2 EXT 3 BTS IUB
VLAN VLAN VLAN
1 3 2

For Local For Core For Internal
Management Network Iub

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


RA34051EN02GLA0 21

System Architecture

I-HSPA Adapter
IP Addressing
I-HSPA Adapter
3G BTS Ultra
192.168.255.143 OMU
3G BTS Flexi MAC: 0E-00-00-01-06-12
IP1 Public OMU
IP2 Public IADA BTS O&M
Into ADA are configured two IP subnets to separate traffic physically by the
Transport Port # 1:
#5
1) Private subnet is used for 3G BTS and intra-ADA traffic: this subnet, #1 Transport
which comprises a set of private fixed IP addresses (i.e. OMU, DSP, Iub #0 L2 Switch #2 LGM
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* #4
and O&M flows

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

IP3 Public
I-BTS

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) IP public address and configurable MAC provide connection for:
IP2 (Public) 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 Not Applicable It supports Port Based VLAN mechanism which grants traffic separation between external traffic (Network L2
Switch domain) and internal traffic (I-BTS L2 domain)


RA34051EN02GLA0 22

System Architecture

IP addressing example, one I-BTS

Flexi BTS with I-HSPA
I-HSPA
Adapter
FCM (”BTS”) OMU
192.168.255.1 192.168.255.143
10.10.10.2/29 10.1.1.1/29 OMU
10.10.10.3/29 (IADA BTS O&M)
FSP
192.168.255.33

Iub, O&M Trans
FSP
192.168.255.34 L2 Switch Iub L2 Switch LGM

SERDES
FSP
192.168.255.35

FTM (”TRS”) DSP
192.168.255.129 192.168.255.142
10.10.10.1/29 10.1.1.2/29

Iub :Port to Iub interface LGM :Port to local management

Trans :Port to transport interface SERDES :Port to SFP module, optical ethernet

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

• 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


RA34051EN02GLA0 23

System Architecture

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 24

System Architecture

BTS O&M IP flow
Flexi BTS I-HSPA Adapter

FCM: 192.168.255.1 OMU: 192.168.255.143
public IP Address 2 public IP Addresses
L2 L2
switc Public IP switc
h address in BTS h
O&M subnet

UP: 192.168.255.xxx DSP: 192.168.255.142
Public IP
{FSP private IP} public IP Address address in
external
transport subnet

FTM
FTM routes BTS O&M to
OMU using OMU MAC address.
192.168.255.129
public IP Address
OMU routes BTS O&M to FTM. - BTSOM routing
- SMA


SMA = Site Management Agent

RA34051EN02GLA0 25

System Architecture

Outline
examples


RA34051EN02GLA0 26

System Architecture

I-HSPA BTS Reference Configurations (IPoE, Flexi)

Option 1: IPoE using IADA Ethernet port, Flexi

Iub
Flexi I-HSPA
BTS Adapter to/from external transport network

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

Flexi Iub
to/from external transport network
I-HSPA
BTS + FTIB
Adapter
(except FIIB)

FTIB
ToP
modul
e L2 switch
FIIB

FTIB FTCC + FIIB


RA34051EN02GLA0 27

System Architecture

I-HSPA BTS Reference Configurations (IPoE, Ultra)

Option 1: IPoE using IADA Ethernet port, Ultra

Iub I-HSPA to/from external
Ultra BTS AXC + IFUH
Adapter transport network


RA34051EN02GLA0 28

System Architecture

Configurations when L2 is Ethernet (IPoE)
• 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

I-BTS Flexi ADA OMU I-BTS Flexi ADA OMU

Configuration Option 1 Configuration Option 2
Eth Eth Eth
Eth
Port#0 Port#1 Port#0 Port#1
(Iub) (Transport) (Iub) (Transport)
DSP DSP
Iub’ Iub’

3G BTS Flexi 3G BTS Flexi
FTIB
FSP FSP Eth
FSP FTxx FSP Eth
FSP BTS FSP BTS Switch
Switch FTM (any Ftxx module) ToPA
System Module System Module

• I-BTS Flexi: the I-HSPA Adapter (ADA) is I-BTS Ultra
connected to the WCDMA BTS, i.e. FTM sub- 3G BTS Ultra ADA
module L2 Switch via ADA L2 Switch. Two AXC IFUH OMU
configuration options are available. AXU
I Iub’
W
• I-BTS Ultra: the I-HSPA Adapter (ADA) is F Eth Eth Eth
Port#0 Port#1
connected to IFUH unit via ADA. Only one WAM
ToPA
(Iub) DSP (Transport)
configuration option is available.


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

RA34051EN02GLA0 29

System Architecture

IPoE Transport Ref Config #1

I uC

M
SC

O&
P

Gn
UP

RA34051EN02GLA0 30

System Architecture

I-BTS Flexi IPoE Configuration Option 1

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.

U/C/M Plane frames ADA OMU OMS
DL ToP frames
Eth MSC
UL ToP frames Eth
Port#0 (Iub) Port#1
Internal Iub’ frames (Transport) SGSN
DSP
GGSN
Internal Iub’
3G BTS Flexi SAS
FTxx
L3 router RNC
???
IP/Eth I-BTS
BTS Switch

FSP System Module
ToP Master


RA34051EN02GLA0 31

System Architecture

IPoE Transport Ref Config #2

Access site Public network Core site

MGW
MSS OMS

I-BTS 1

Flexi BTS Adapter
C
FCM OMU IuP
VPN GW SAS
IP/Ethernet Operators Core
FTM with
DSP
Network
ToP slave
Core site
router
With/without
IPSec
ToP Master
I-BTS 2
FCM OMU
FTM with GGSN
DSP
ToP slave
.
RNC SGSN
.
.


RA34051EN02GLA0 32

System Architecture

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 ADA OMU OMS
DL ToP frames
Eth MSC
UL ToP frames Eth
Port#0 Port#1
Internal Iub’ frames (Transport) SGSN
(Iub)
DSP
GGSN
Internal Iub’
3G BTS Flexi SAS
FTIB
L3 router
RNC

EIF3
IP/Eth I-BTS
BTS Switch EIF1/2
ToPA L2 switch
FSP System Module
ToP Master

FTIB functions
as a L2 switch
only!

RA34051EN02GLA0 33

System Architecture

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

TRS_CLK
LIU OVP
. .
SPI IF4
IDT82V2084
• 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
I2C I2CMUX EEPROM
EMB the same time
PCA 9544 T°C
• 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
SFP EIF1
FE changes to the input masks are needed compared
receptacle
to non I-HSPA mode
GE SGMII Ethernet
• The I-HSPA transport interface should be connected
Switch EIF2
XFR to EIF3. The operator can choose either to use the
88E6097
OVP EIF3 optical interface or an electrical interface to connect
the transport network; the operator should not use
MII
VLAN 1108 and 1109 for I-HSPA traffic or ToP
traffic on the transport network. For outdoor
ToP
connection the same cable type used to connect
ACS/9550SRAM ADA to FCM should be used to connect ADA to
EIF3

3.3 V
NOTE: only Eth • “ToP” has to be allowed to be used as Sync source
switch, no IP
routing!


RA34051EN02GLA0 34

System Architecture

I-BTS Ultra IPoE Configuration
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

3G BTS Ultra ADA
OMU No NAT required

AXC DCN NAT required
Public IP
IFUH
Iub
AXC Iu
IP/Eth

WAM
WAM
WAM Top
Client Top Master
DSP sends packets
to OMU’s public
IP Top
Master
WAM DCN All these must use the same source
private IP 192.168.254.140
Public IP
Top traffic, IP forwarding & NAT in OMU in both directions
DCN traffic terminated in AXC & WAM, IP forwarding in OMU in both directions, no NAT
Control & management planes terminated in OMU
User plane terminated in DSP

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

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 IFUH
implementation 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 35

System Architecture

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 Shared
Antenna
– IP QoS Shared
Mast Head
Amplifiers

Shared
feeders
RNC
Iur

Iub/Native IP
I-HSPA Adapter
GGSN

Gn


RA34051EN02GLA0 36

System Architecture

IFUH Unit

• Applicable with
– AXUA / AXUB with all BTS cabinet types
– AXCC / AXCD with exception of Metrosite / Metrosite50
cabinet 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 37

System Architecture

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

I-BTS Flexi # 1 I-BTS Flexi # 2 I-BTS Flexi # 3

WCDMA Flexi BTS WCDMA Flexi BTS WCDMA Flexi BTS
WBTS #1 WBTS #2 WBTS #3

Subnet Subnet Subnet
10.10.1.0/28 10.10.1.16/28 10.10.1.32/28
TRS IP TRS IP TRS IP
10.10.1.1 10.10.1.17 10.10.1.33
NOTE: BTS IP BTS IP BTS IP
IADA BTSOM IP 10.10.1.2 10.10.1.18 10.10.1.34
address is IADA BTSOM IP IADA BTSOM IP IADA BTSOM IP
„physically“ in OMU. 10.10.1.3 10.10.1.19 10.10.1.35

IADA-1 IADA-2 IADA-3

OMU: .1 SIGTRAN IP OMU: .3 SIGTRAN IP OMU: .5 SIGTRAN IP
DSP: .2 10.20.1.1 DSP: .4 10.20.1.3 DSP: .6 10.20.1.5

IADA subnet
10.20.1.0/28

L2 switch L2 switch

.14

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

external transport network


RA34051EN02GLA0 38

System Architecture

Outline
examples


RA34051EN02GLA0 39

System Architecture

I-HSPA BTS Reference Configuration (IPoA)
IP over ATM (IPoA)
ATM over
PDH/SDH in FTM

Flexi Iub I-HSPA FTM
to/from external
transport network
BTS Adapter

This connection
uses the same
GigEth connection
as Iub between
IADA and System
Module


RA34051EN02GLA0 40

System Architecture

IPoA Transport Ref Config


RA34051EN02GLA0 41

System Architecture

I-BTS Flexi IPoA Configuration

ATM transport option is via FTM sub-module: ADA Eth
• Iub‘ internal interface is via ADA L2 Switch Port#0 ADA L2 Switch Port#1
ADA L2 Switch Port#0
• External interfaces (e.g. Iu/Iur) are via FTM module port;
Iub’
Ethernet transport option is via ADA (IHSW-33):
• Iub‘ internal interface is via ADA L2 Switch Port#0 SDH/PDH
• External interfaces (e.g. Iu/Iur) are via ADA L2 FTM Port
BTS
Switch Port#1. Switch
FTM Module (e.g. FTPB)
• ToP feature is not supported. FSP System Module
ATM data flow

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

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

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

RA34051EN02GLA0 42

System Architecture

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

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

SCCP SCCP

M3UA M3UA

SCTP SCTP
ADA – ADA connection
IP IP

UDP Transport module 1 Transport module 2 UDP
IP UDP AAL5 AAL5 UDP IP
ADA – FTM ADA – FTM
internal IP ATM ATM IP internal
Ethernet connection connection
Ethernet
Ethernet L1 L1 Ethernet

L2 L2 L2 L2
switch switch Iur over switch switch
43 © Nokia Siemens Networks RA34051EN02GLA0 ATM

Note: not possible for ultra

RA34051EN02GLA0 43

System Architecture

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

OMU [RNC Application]
FTM Public: 130.1.0.101
130.2.0.101 over UDP port#1002 to 192.168.255.129 MAC connection to CN (i.e. Iu-
Iu-PS CP PS CP, Iu-CS CP, Iur/Iur*
DEST: 130.2.0.101 FTM
Iu-CS CP CP, DCN)
Iur/Iur* CP
UDP port#1002
DCN
Private: 192.168.255.143
BTS internal network
including ADA

Port#5 (L2 Switch)
DEST: 130.2.0.201
Iu-PS UP
UDP port#1011 Port#4 (L2 Switch)
DSP
DEST: 130.2.0.201
Iur/Iur* UP 130.2.0.201 over UDP port#1011 to 192.168.255.129 MAC Public: 130.1.0.201
UDP port#1010 FTM connection to CN (i.e. Iu-
FTM is not IP PS UP, Iur/Iur* UP)
router, it just Private: Private: 192.168.255.142
130.2.0.201 over UDP port#1010 to 192.168.255.129 MAC
forwards IP 192.168.255.129
FTM BTS internal network
packets from including ADA
VCC to L2
switch and adds
OMU AA0 Iu-PS/Iu-CS/Iur/Iur* CP, DCN UDP Port: 1002 VP=xx/VC=yyy
UDP/IP layer

ADA (i.e. DSP/OMU [RNC
FTM
Appl] selects the correct UDP ATM0 Iu-PS UP UDP Port: 1011 VP=xx/VC=yyy
port so that traffic will be DSP
forwarded to the correct VCC ATM1 Iur/Iur* UP UDP Port: 1010 VP=xx/VC=yy


RA34051EN02GLA0 44

Chichi chacha

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Chichi chacha

Similar to Chichi chacha (20)

Chichi chacha