NokiaEDU

Flexi SRAN BTS Common Transport &

Synchronization
SRAN16.10

RA23323EN04GLA0 © Nokia 2016

 Copyright and confidentiality
The contents of this document are proprietary and
confidential property of Nokia Networks. This document
is provided subject to confidentiality obligations of the
applicable agreement(s).
This document is intended for use of Nokia Networks
customers and collaborators only for the purpose for
which this document is submitted by Nokia Networks.
No part of this document may be reproduced or made
available to the public or to any third party in any form
or means without the prior written permission of Nokia
Networks. This document is to be used by properly
trained professional personnel. Any use of the contents
in this document is limited strictly to the use(s)
specifically created in the applicable agreement(s)
under which the document is submitted. The user of
this document may voluntarily provide suggestions,
comments or other feedback to Nokia Networks in
respect of the contents of this document ("Feedback").
2 RA23323EN04GLA0
Such Feedback may be used in Nokia Networks
products and related specifications or other
documentation. Accordingly, if the user of this
document gives Nokia Networks feedback on the
contents of this document, Nokia Networks may freely
use, disclose, reproduce, license, distribute and
otherwise commercialize the feedback in any Nokia
Networks product, technology, service, specification or
other documentation.
Nokia Networks operates a policy of ongoing
development. Nokia Networks reserves the right to
make changes and improvements to any of the
products and/or services described in this document or
withdraw this document at any time without prior notice.
The contents of this document are provided "as is".
Except as required by applicable law, no warranties of
any kind, either express or implied, including, but not
© Nokia 2016
limited to, the implied warranties of merchantability and
fitness for a particular purpose, are made in relation to
the accuracy, reliability or contents of this document.
NOKIA NETWORKS SHALL NOT BE RESPONSIBLE
IN ANY EVENT FOR ERRORS IN THIS DOCUMENT
or for any loss of data or income or any special,
incidental, consequential, indirect or direct damages
howsoever caused, that might arise from the use of this
document or any contents of this document.
This document and the product(s) it describes are
protected by copyright according to the applicable laws.
Nokia is a registered trademark of Nokia Corporation.
Other product and company names mentioned herein
may be trademarks or trade names of their
respective owners.
Content
- SRAN Common Transport
• Introduction of Common Transport
• FSMF Transport Interface
• SRAN IP Addresses 2
• IPSec
• Transport QoS
3 G
- SRAN Synchronization G LTE
• Synchronization Requirement
• Synchronization Capabilities
• SRAN16.2 Sync Features

4 RA23323EN04GLA0 © Nokia 2016

SRAN Common Transport

5 RA23323EN04GLA0 © Nokia 2016

Introduction – common transport

Before After

3 separate: • One IP transport solution

•Transport solutions • 3 RATs in single box
•Feature sets • One transport feature set and transport parameter set
• One system base station per radio technology (GSM, WCDMA, LTE) • One IPsec engine
• One operability and management

RF RF
RF RF RF
RF

GSM BB WCDMA BB LTE BB

GSM WCDMA LTE
TRS OA TRS OA TRS OA
M M M
TRS OAM System
Module
TRS OSS TRS
backhaul GSM LTE
WCDMA OSS
backhaul

6 RA23323EN04GLA0 © Nokia 2016

 Introduction to common transport
SBTS common transport scheme

shared transport function in SBTS with unified operability

• On Transport Network layer site appears as one IP host
(single physical node supporting IP connectivity)
• Data form specific RAT are processed on FSMF subunits
and transferred between them via Secured internal bus
• Transport processed only on master system module (in
case of module chaining)
• Main focus on IP/ETH - based Transport modes
• One Transport feature set and common implementation
SBTS

Common IP layer

for GSM, WCDMA, LTE

• Flexible IP addressing, QoS and IPsec concepts
• Unified Transport operability and maintenance

7 RA23323EN04GLA0 © Nokia 2016

HW platform
FSMF system module as platform for SBTS

SBTS = FSMF system module + SRAN SW (serving GSM WCDMA LTE)

Flexi MultiRadio 10 – FSMF
•2 x Transport interfaces
(one shared with RP3-01)
•Optional FTIF module
•Optional FBBA/C add-in
cards
Flexi MultiRadio 10
FSMF system module
with Multi-RAT support
• Simultaneously processing of 3RATs on one system module
• Baseband capacity and extension modules allocated to specific
RATs
• Common Transport and O&M on Master module
• Optional TRS extension unit FTIF for TDM interface and
Ethernet interfaces extensions
• Module chaining - up to 2 system modules (capacity
expansion purposes)
• All FSMF HW rel. supported (excluding FSMF A.101)

8 RA23323EN04GLA0 © Nokia 2016

 SW Architecture
System Module Sharing 2-RAT and 3-RAT modes
Opt. PDU Opt.TRS ext GSM/ Opt. PDU Opt.TRS ext

3 HU
TR WCDMA
GSM&WCDMA S FSMF TRS
WCDMA WCDMA FBBA/C FBBA/C
2-RAT Modes

Opt. PDU Opt.TRS ext GSM/LTE Multi-radio capable HW

TR
GSM&LTE S
• “Dedicated mode”: e.g. GSM application
runs on FSMF, (1-RAT mode)
LTE LTE
• “Shared mode”: GSM, WCDMA and LTE can
run simultaneously on a single FSMF
Opt. PDU Opt.TRS ext WCDMA/ with one common backhaul connection
LTE or WCDMA S
TR LTE
• TRS processing on Master FSMF
LTE WCDMA EXAMPLE even in case of chaining of system modules
S
• GSM is always processed on main FSMF
3-RAT Modes

Opt. PDUOpt.TRS ext Single • LTE always processed on Slave system module
GSM&WCDMA S
TR subrack or in case of system module chaining
chained
WCDMA LTE subracks

9 RA23323EN04GLA0 © Nokia 2016

Transport Modes and NW dependency
Supported Transport modes
• LTE: S1/X2 over IP/Ethernet
SRAN BTS • WCDMA: IP Iub over Ethernet
• GSM: Packet Abis over IP/Eth
RAT 1 or Packet Abis over TDM

Transport
Common
Full packet backhaul example Note: In SRAN16.2/16.10 support of Packet Abis over TDM
RAT 2 interfaces is used only in scenario of:
•SBTS in GSM dedicated mode
•TDM as fallback for Packet Abis over IP/Eth
RAT 3

• No ATM IuB support

Network dependency plan • No Dynamic Abis support
• No CES over PSN
MME Flexi NS15, Flexi NS16
SRAN16.2 E16
A, LT S-GW
LTE15 Flexi NG15, Flexi NG16 Transport configuration fully integrated into the Web UI
P-GW
GSM16
BSC BSC16, mcBSC16
SBTS WC NetAct16 SBTS peer node requires corresponding SW
DM
A16
RNC RNC16, mcRNC16 release
OMS16 for
RNC
managing

10 RA23323EN04GLA0 © Nokia 2016

Single RAN BTS - Transport Interfaces
FSMF Transport Interface
2 x Combo Ethernet Ports:
• 2x 1000/100BaseT, or
• 2x optional optical GE SFP, or
• 1x 1000/100BaseT and
1 x optional optical GE SFP
1x optional optical SFP (GE),
available for Transport
only if not used for RP3-01 (RF sharing)
11
• FSMF provides the following Transport interfaces
(without the optional Transport Sub-Module)
- 1x 100/1000 Base-T Ethernet port
- 1x optional optical (if not in use for RP3-01)
8x E1/T1/JT1 (twisted pair):
• Optional FTIF required in case of
4 x RJ48C-style ports with
2 x E1/T1/JT1 each - use of TDM interface for
• Packet Abis over TDM or
• synchronization input via PDH
- use of optical Ethernet (if optical SFP is already used on
FSMF for RF purposes)
- need for multiple Ethernet ports - backhauling
• to extend the TRS capacity beyond 1GE
• to provide redundancy
• Transport chaining
1x 100/1000Base-T • Two FSMF modules can be chained (SRAN16.2, SRAN16.10)
Ethernet port,
dedicated for Transport
RA23323EN04GLA0 © Nokia 2016
Single RAN BTS - Transport Interfaces
FSMF system module chaining • 2 system modules can be chained for baseband
capacity extension
MASTER - Backhaul interfaces and transport processing/functions
located on MASTER
- FTIF not needed on SLAVE
• When chaining FSMFs:
- SRIO interface
• System module connectivity
Ex. OBSAI RP3-01 SRIO
- RP3-01 interface
• RF connectivity purposes
• Synchronization distribution between system
modules
• GSM and WCDMA processed on MASTER
SLAVE • LTE processed on SLAVE

12 RA23323EN04GLA0 © Nokia 2016

Single RAN BTS - IP addresses
Flexible IP addressing concept
• Applications can bind to interface IP addresses, virtual IP addresses or alias IP addresses
• IP addresses can be shared or dedicated across RATs and/or planes
• SBTS M-plane binds to one IP address
• In one extreme a SBTS can be operated with a single IP address for U-/C-/M-/S-plane,
in other extreme it can be operated for U- and C-plane IP addressing same as individual BTSs (except for
M-plane which is always shared)

U/C
VLAN
(optional)
SRAN SRAN VLAN SRAN U/C
VLAN
U/C/S VLAN U/C/S
(optional)
BTS /M BTS (optional) BTS
(optional) VLAN
M VLAN U/C
(optional) (optional)
VLAN
Examples S
(optional)
M VLAN
(optional)

13 RA23323EN04GLA0 © Nokia 2016

Single RAN BTS - IP addresses
SBTS- IP addresses – minimum IP addressing scenario
Migration scenario from 3 separate single RAT BTS to SBTS with the minimum number of IP addresses.
Legacy solutions:
• In GSM and LTE U/C/S/M planes can share one IP address
• In WCDMA U/C/S planes are under one IP address, Management plane has separated IP address

U/C/S
VLAN
(optional)

SRA
M N
SBTS
GSM BTS LTE LTE
BTSBTS (3-RATs)
WCDMA BTS

14 RA23323EN04GLA0 © Nokia 2016

Single RAN BTS - IP addresses
SBTS- IP addresses – separated M-plane scenario
Migration scenario from 3 separate single RAT BTS to SBTS with the minimum number of IP addresses and separate
management plane VLAN
Legacy solutions:
• In GSM and LTE U/C/S/M planes can share one IP address
• In WCDMA U/C/S planes are under one IP address, Management plane has separated IP address

U/C/S VLAN
(optional)
T
VLAN
(optional) SRA
M N

GSM BTS WCDMA BTS LTE BTS SBTS

15 RA23323EN04GLA0 © Nokia 2016

Single RAN BTS - IP addresses SBTS – IPv4/IPv6 Dual Stack
Supported IP versions Common
GS LTE WCDMA
Transport
M
Supported IP versions - SBTS
- On level of the IP interface IPv4 / IPv6 Dual Stack is supported
- IPv6 capabilities of a Single RAN BTS will thus be same as IPv6 capabilities of the individual Radio Access
Technologies (only LTE supports IPv6 for C/U-plane)

Supported IP versions - Interface

table
Application termination – planes termination

Hosted RAT Interface name C U M S TRS

GSM Packet Abis IPv4 IPv4 IPv4 IPv4 IPv4/IPv6 GSM – IPv4

WCDMA IuB over IP IPv4 IPv4 IPv4 IPv4 IPv4/IPv6 WCDMA – IPv4

LTE S1/X2 IPv4/IPv6 IPv4/IPv6 IPv4 IPv4 IPv4/IPv6 LTE – IPv4/IPv6

IPv4 IPv4
SRAN Common transport IPv6 - for LTE IPv6 - for LTE IPv4 IPv4 IPv4/IPv6
from SRAN17 from SRAN17

16 RA23323EN04GLA0 © Nokia 2016

Single RAN BTS - IP Security

GSM IPse
c tunnel
Common IPsec tunnel

Com
tunnel mo n
WCDMA IPsec Bac
k up
IPse
c tu

c t un n
el SBTS n ne
l
IPse
LTE
Backup IPsec tunnel

In Single RAT Base stations: In SBTS solution:

• Each RAT node has own IPsec engine
• Single or multiple tunnels can be established between each
single RAT base station
• IPsec extension features (e.g. backup IPsec tunnel) supported
only by LTE BTS
• Common IPsec engine with unified parameter set per SBTS
• Full flexibility possible with regard to assigning traffic to
tunnels (single or multiple tunnels per SBTS, tunnels per
RAT, per plane, etc.)
• IPsec extension features (backup IPsec tunnel and emergency
bypass) available for all RAT applications

17 RA23323EN04GLA0 © Nokia 2016

 Single RAN BTS - Transport Quality of Service
• Marking RAT traffic class to DSCP - no changes
• Common BTS mapping table for DSCP  PHB and DSCP  p-
bits
• C/U-plane marking done by RAT application – same possibilities
as in legacy solution
R
O
U •M/S-plane marking configurable per SBTS
T
I
N • Two levels of scheduling/shaping are provided
G
• 1st level queuing/scheduler/shaper “per policed or
bandwidth limited connection in the transport network”
Multiple 8-queue (3xSP+5xWFQ) schedulers available per
SBTS (shaping per flow basing on source IP address
In Single RAT Base stations:
• Single or dual 6-queue (1xSP+5xWFQ) scheduler available per BTS - Traffic flows can be freely allocated to 1st level schedulers
(shaping per VLAN and/or per aggregate) allowing to prioritize, shape and limit flows or
• Multiple queues egress scheduler (actual implementation depends on combination of flows according to the preference of the
FTM HW) available per Ethernet port in integrated switch operator
• 2nd level scheduler/shaper “per phys. L2 interface”

18 RA23323EN04GLA0 © Nokia 2016

Transport Admission and Congestion Control

• Radio Access Technology-specific legacy Admission and Congestion Control mechanisms remain
applicable and operate independently in Single RAN BTS
- WCDMA: Connection Admission Control
- LTE: Measurement Based Transport Admission Control
- GSM: Packet Abis Congestion Control

shared
IP / Ethernet Common
Transport GS LTE WCDMA SBTS
M

19 RA23323EN04GLA0 © Nokia 2016

SRAN Synchronization

20 RA23323EN04GLA0 © Nokia 2016

RAN synchronization

Traditional deployments SRAN solution

SRAN BTS
GSM BTS WCDMA BTS LTE BTS GSM WCDMA LTE
System Module ~ System Module ~ System Module ~ System Module ~
sync reference sync reference sync reference
sync reference

Every BTS contains an independent clock SRAN BTS has a single clock
that must be synchronized that feeds all RATs on the BTS
to a reference clock at once

Single RAN = Single Clock

21 RA23323EN04GLA0 © Nokia 2016

RF sharing synchronization

Traditional deployments SRAN solution

SRAN BTS
GSM BTS WCDMA BTS LTE BTS GSM WCDMA LTE
System Module ~ System Module ~ System Module ~ System Module ~

In traditional deployments, RF sharing With SRAN BTS, it is not an issue

requires site level synchronization among
BTS of different RATs

All RATs on a single SBTS are synchronized from a common clock

22 RA23323EN04GLA0 © Nokia 2016

Summary of synchronization requirements

GSM LTE FDD

• Frequency Sync: ±50 ppb • Frequency Sync: ±50 ppb
• Phase Sync: No requirement • Phase sync: No requirement
except as for the DFCA: ±9 μs except as for specific LTE-A features

WCDMA LTE TDD (not supported in SRAN16.10)

• Frequency Sync: ±50 ppb • Frequency Sync: ±50 ppb
• Phase Sync: No requirement • Phase Sync: ±1.5 μs

Single RAN BTS must meet the most stringent sync requirements
among all RATs used on the BTS

23 RA23323EN04GLA0 © Nokia 2016

SRAN16.10 sync capabilities

List of user-defined sources

with configurable priorities Individually controlled outputs
 External GNSS receiver  PDH
 ToP: ToP-F or ToP-P  2.048 MHz
 SyncE  1pps&ToD
 PDH  FCLK/FN signal
 2.048 MHz
SRAN BTS
 1PPS&ToD GSM WCDMA LTE
System Module ~

24 RA23323EN04GLA0 © Nokia 2016

SRAN generic sync features at glance

Generic features
• SR847 BTS Synchronization Mode Support
A generic feature that defines SBTS capability to operate a radio interface
in the frequency or the phase synchronization modes by tuning the local
oscillator to a generic sync input
SRAN BTS
• SR1041 Synchronization Holdover Support GSM WCDMA LTE
Defines period of SBTS operation in holdover mode for specific accuracy
requirements in the frequency and the phase synchronization modes System Module ~
• SR1103 SBTS Flexible Sync Input Priority
Implements single list of synchronization reference sources
with freely defined priorities, regardless of the sync reference type

25 RA23323EN04GLA0 © Nokia 2016

New sync features in SRAN16.10

SRAN BTS
GSM WCDMA LTE
System Module ~
Affected sync functions

Sync input features Sync output features

• SR567 1PPS&ToD Sync from Sync Hub Master • SR554 Sync Hub Direct Forward
Enables SBTS to use ingress 1PPS&ToD signal as a Enables SBTS to operate as a SyncHub Master by generating
synchronization reference egress 1PPS&ToD signal, or as a SyncHub intermediate slave
by directly forwarding the ingress 1PPS&ToD signal to the output

• SR1147 Synchronization Hub with FCLK/FN signal

as output
Enables SBTS to operate as a SyncHub Master in synchronization
chains with legacy ESMA-based GSM BTS

26 For internal use RA23323EN04GLA0 © Nokia 2016

SR567: 1PPS&ToD Sync from Sync Hub Master
Technical Details

The feature SR567 1PPS&ToD With the feature, SBTS operates

Sync from Sync Hub Master as a Slave in SyncHub Direct
enables SBTS to support Forwarding chains
1PPS&ToD signal as a
synchronization reference

GSM, WCDMA, LTE or WCDM

Sync 1PPS&ToD GSM LTE
SBTS A
source ~ System Module
System Module Sync-In
SyncHub Master port SRAN BTS

27 For internal use RA23323EN04GLA0 © Nokia 2016

SR1147 Synchronization Hub with FCLK/FN signal as output
Technical Details

The feature SR554 Sync Hub With the feature, SBTS can
Direct Forward enables SBTS to operate as a Master or an
generate 1PPS&ToD signal at the intermediate Slave in SyncHub
egress Sync-Out interface Direct Forwarding chains

WCDM GSM, WCDMA, LTE or GSM, WCDMA, LTE or

Sync GSM LTE 1PPS&ToD 1PPS&ToD
A SBTS SBTS
source System Module ~
Sync-Out System Module System Module
SRAN BTS port SyncHub Slave SyncHub Slave

GSM, WCDMA, LTE or WCDM GSM, WCDMA, LTE or

Sync 1PPS&ToD GSM LTE 1PPS&ToD
SBTS A SBTS
source System Module
System Module Sync-In Sync-Out System Module
SyncHub Master port SRAN BTS port SyncHub Slave

28 For internal use RA23323EN04GLA0 © Nokia 2016

SR1147: Synchronization Hub with FCLK/FN signal as output
Technical Details
The problem Solution
ESMA does not support The feature SR1147
synchronization from Synchronization Hub with
1PPS&ToD reference FCLK/FN Signal as
Output enables SBTS
to generate FCLK/FN
signal that can be used by
another GSM BTS
as a synchronization
reference
> All GSM BTSs – namely
ESMA, ESMB, ESMC, FSMF
– support synchronization
from FCLK/FN signal
29 For Internal Use RA23323EN04GLA0
Limitations
The feature SR1147
is mutually exclusive with
the feature SR554
> FCLK/FN signal
is transmitted over the same
physical interface
as 1PPS&ToD signal
The feature SR1147
is not suitable for sync
chains with LTE or
WCDMA BTS
> Only GSM BTSs support sync
from FCLK/FN signal
© Nokia 2016
Usage recommendations
It is recommended
to use the feature SR554
Sync Hub Direct Forward
instead of the feature
SR1147 in sync chains
that do not include ESMA
BTS
> All other GSM BTSs (except
those, based on ESMA)
support sync from 1PPS&ToD
signal
RA23323EN04GLA0 © Nokia 2016