Mavenir CSFB IWF

LI Overview
September 2012

2011 Mavenir Systems

Standard IP LI
MAP

MSC

HLR
MAP

UDR

X1

LDAP / SOAP

Lawful
Intercept

X2

IN / SCP

Mavenir Converged TAS

CAP / INAP

(MMTEL, gsmSSF, Video, CCF, Conferencing)

Mr
SIP (MSML)

SCC

ISC / Ma
(SIP)

Sh

HSS

Zb (Ut)

Ut

Cx

I-S-CSCF

ISUP

GMSC
BGCF

Mj (SIP)
Mg (SIP)

AG
Zh

Emergency

PSAP

BSF AP (NAF)

Mw
(SIP)

HEP

Le

Ua (Ut) Ut

MGCF

MGW

May be combind
RTP

P-CSCF
Ub

MRF

X1

ADMF

X2

DF1

Call Data Delivery

X3

DF2

Call Content Delivery

Provisioning

E-CSCF
LRF

A-SBC

SIP

LI

Access

SIP Client /UE

2012 Mavenir Systems

Page

VoLTE IWF

2011 Mavenir Systems

Mavenir VoLTE IWF Solution

Easing The Pain for Network Transitions
Only complete VoLTE
Interworking portfolio

Eliminates investment in legacy

components

HLR

SMSC

MSC
Xx
LI

MAP

Common platform that can follow

traffic as services evolve

MAP

MAP E

VoLTE IWF

2
CSFB IWF

SR-VCC IWF

CSFB IWF, SR-VCC IWF and ICS

IWF (common hardware and
software) on a single platform

Mg

Mg/Mw

MGCF
SGs

ICS IWF

i2
P/I/S-CSCF
ATCF

Sv

MME / PGW / SGW

2012 Mavenir Systems

Page

VoLTE IWF Network Architecture

Combined CSFB / SR-VCC / ICS IWF
Um

GERAN/
UTRAN

MAP

MSC/
VLR

A/Iu

MAP

SMSC

ISUP
MAP
UE
LTE-Uu

E-UTRAN

SGs

S1MME

MGCF

Sv

MME
S6a

S1-U

S-11

Sgi
P-CSCF

I2 / Mw / Mg

LI

I2 / Mw

Cx
Sh

Mw

Mj

ATCF /
ATGW

HLR

MAP

CSFB / SRVCC
IWF

HSS

SGW / PGW

MAP

SIP

Lawful
Intercept

CAP
SCP/
gsmSCF

Mw
I/S-CSCF

Mi

BGCF

ISC
TAS / SCC AS

2012 Mavenir Systems

Page

CSFB IWF LI

2011 Mavenir Systems

Mavenir CSFB IWF - Introduction

Mavenirs CSFB IWF enables Mobile Operators to
provide voice and SMS messaging services to LTE/EUTRAN devices without requiring MSC to be upgrade to
support the 3GPP SGs reference point.
MO and MT voice calls are still handled by the VLR/MSC
infrastructure, the device is made to fallback to UTRAN or
GERAN for both mobile originating and mobile
terminating calls as such existing LI procedures can still
be used
However, SMS messages are delivered via the CSFB
IWF to the devices via SGs interface to the MME. As
such existing VLR/MSC are not in the message path for
MO or MT SMS while a UE is attached to E-UTRAN
2012 Mavenir Systems

Page

CSFB IWF Architecture

HLR

SMSC

MAP

MAP

MSC/VLR

CSFB
IWF

LI
Xx

SGs

Iu-cs

SGSN

S3

CSFB IWF Interfaces

SGs to MME
Standard SGs functionality
MME sees the IWF as a VLR

MAP to HLR
Location updating procedures
- MAP Update Location
- MAP Cancel Location
- MAP Insert Subscriber Data

MME

Call routing procecures

Gb

GERAN

Iu-ps

- MAP Provide Roaming Number

- MAP Send Routing Info

S1-MME

UTRAN

E-UTRAN

MAP to SMSC
MO/MT SMS procedures

Um

Uu

LTE-Uu

CSFB UE

- MAP MO Forward Short Message

- MAP MT Forward Short Message

LI
X1
- For provisioning of target
identifiers. Based on TCP/IP

New or modified node

Unchanged node

X3
2012 Mavenir Systems

For reporting SMS related to provisioned

target Identifiers. Based on TCP/IP
|

Page

Mavenir CSFB IWF LI - Introduction

The CSFB IWF includes LI capability and interfaces to
the LI Administration Function (LI ADMF) and LI Delivery
Function (LI DF) as defined in the 3GPP specification
33.107
3GPP LI Architecture defines three interfaces via which
network element for LI capability, ICE Interception
Control Element, interfaces to the LI ADMF and LI DF.
X1 for administration to provision interception rules in ICE,
including activation and deactivation
X2 is used by ICE to deliver signalling and other events,
referred to as Interception Related Information (IRI)
X3 - is used by ICE for delivery of content, referred to as CC
Communication Content. This is also used by IWF to report SMS
LI reports

Mavenirs CSFB IWF is a ICE providing X1, X3

2012 Mavenir Systems

Page

Mavenir CSFB IWF LI General

The 3GPP specifications do not define an implementation
of the X1, X2 and X3 interfaces and often these are
proprietary interfaces of the vendor providing the LI
ADMF and LI DF functions in the network
Target Identifiers -The interception target can be
dentified by any one of the following:
MSISDN
IMSI
IMEI(SV)

Interception by multiple LEAs

CSFB IWF supports multiple interception whereby a single target
is intercepted multiple times, potentially by different LEA
Each intercept is identified by a different Lawful Intercept
Identifier (LIID) and managed separately via X1
2012 Mavenir Systems

Page

Mavenir CSFB IWF LI X1/X3

X1 Administration - Mavenir CSFB IWF supports the following
actions on X1

Activate start the LI of SMS messages for a target

Deactivate end the LI of SMS messages for a target
Interrogate obtain status for either a specific intercept or all active intercepts

X3 SMS events and content - Mavenir CSFB IWF provides the

following information

LI Target MSISDN
LI Target IMSI
LI Target IMEI(SV)
LIID
Reference and sequence number
MO/MT Indicator
Event date and Time
Location (TAI/E-CGI)
SMS message

2012 Mavenir Systems

Page

Mavenirs Reference implementation

Transport - Mavenirs reference implementation of X1 and X3 uses either

TCP or SSL/TLS as the transport mechanism

Message format:

Administration Interface (X1)

The X1 is based on a simple MML syntax. Requests and responses are

encoded in messages described previously
Requests are from the LI ADMF to Mavenir CSFB IWF, responses are
from CSFB IWF to LI ADMF

Request Syntax: <REQUEST_ID>:<ATTR>=<VALUE>,<ATTR2>=<VALUE2>,;

Response Syntax: <STATUS CODE>[:<ADDITIONAL INFO>][:<ADDITIONAL INFO>];
where each ADDITIONAL INFO is a comma separated list of (attribute, attribute-value) pairs

IRI Interface X3 - The X3 interface sends an XML structure in a message. The

structure is can be shared at request

2012 Mavenir Systems

Page

Mavenirs Reference implementation

Transport for X1 and X3 messages
All X1 and X3 messages are encapsulated within PEP (Packet Encapsulation
Protocol) and carried over TCP/IP
The aim of this encapsulation is to provide packetization of X1 and X3 messages
before it is sent over TCP/IP
PEP is unidirectional protocol where the Request or Notification messages are
initiated by the sender and the receiver acknowledges the packets using ACK
or NACK. Only Request messages need to be acknowledged. Notification
messages do not require acknowledgement. NACK is sent in case of transport
errors or unexpected sequence number. At a time only one Request message
can be outstanding
Sequence numbers starts from 0 until 65535. NACK messages do not contain a
sequence number. ACK messages carry the same sequence number as received
in corresponding Request messages.
For X1 interface, the provisioning server is responsible for maintaining sequence
numbers and for X3 interface the CSFB IWF will maintain the sequence numbers.
The provisioning server sends X1 MML commands in Request messages and
the CSFB IWF acknowledge the command using ACK or NACK messages. X3
interface only uses Notification messages initiated by the CSFB IWF.

2012 Mavenir Systems

Page

Backup

2011 Mavenir Systems

SR-VCC Release Comparison

3GPP R10

3GPP R9
Sv interface between MME and
MSC enhanced with SR-VCC
SCC AS in home network
anchors session (signaling)

ATCF and ATGW introduced

Session anchor moved from
SCC AS to serving network
ATCF anchors signaling

No RTP anchor for the session

SCC AS initiates RTP updates at
both endpoints

Transfer of held sessions

ATGW anchors bearer

Advantage is lower handover

time, less voice disruption <300 ms
Transfer of alerting sessions

Interruption time 800-1000 ms

3GPP R11
SR-VCC for video sessions
Reverse SR-VCC (CS to PS)

2012 Mavenir Systems

Page

15

3GPP R9 SR-VCC Architecture

GERAN/
UTRAN

A/Iu

SCC AS anchors the session and initiates the

update of both RTP endpoints upon the access
transfer

MSC

MMTel TAS provides

telephony services

SR-VCC handover

E
GERAN/
UTRAN

A/Iu

MSC
(SR-VCC)

Sv
MME

S1-MME

E-UTRAN

S1-U

MMTel
TAS

SCC AS

Mg/I2
ISC

S11
Serving /
PDN-GW SGi

Gm
P-CSCF

I/S-CSCF

To remote
SIP endpoint

Mw
Mb
To remote
RTP endpoint
CS component
EPS component
IMS component

2012 Mavenir Systems

Page

16

3GPP R10 SR-VCC Architecture

GERAN/
UTRAN

A/Iu

SCC has a more limited role in access

transfer but is still a necessary
component

MSC

MMTel TAS provides

telephony services

SR-VCC handover

E
GERAN/
UTRAN

A/Iu

MSC
(SR-VCC)

Sv
MME

S1-MME

E-UTRAN

S1-U

I2
ISC

S11
Serving /
PDN-GW SGi

Gm

Mw
P-CSCF

Mw
ATCF

Mb
ATGW
CS component
EPS component

MMTel
TAS

SCC AS

ATCF/ATGW provide the session and

RTP anchor and perform the access
transfer function

Serving
Network

Mw

I/S-CSCF

Mb

To remote
SIP endpoint

To remote
RTP endpoint

Home
Network

IMS component

SR-VCC Rel 10 reduces voice interruptions to less than 300ms

2012 Mavenir Systems

Page

17