Sie sind auf Seite 1von 69

SRVCC Single Radio Voice Call Continuity

FN 2008
1. VoLTE and NSN Implementation
2. SRVCC

For public use IPR applies


1
Nokia Siemens Networks

CN60022EN50GLA0

VoLTE and NSN Implementation

For public use IPR applies


2
Nokia Siemens Networks

CN60022EN50GLA0

LTE Implementation
More than 100 operators have
invested in LTE networks
LTE is answer for increased voice
and data capacity demand - coming
from growing smart phone segment providing at a significantly lower
cost per bit.
Voice ARPU being driven down by
low cost VoIP services offered by
internet players
VoLTE is mandatory service to
maintain the current voice business
model in LTE
New services opportunity on a
common service architecture
For public use IPR applies
3
Nokia Siemens Networks

CN60022EN50GLA0

When to offer Voice over LTE ?

Drivers for LTE


10x faster

100
Mbps

42

Demand for higher bandwidth


Lower latency
Better spectral efficiency
New spectrum
E2E All-IP flat architecture

Mbps
HSPA+

~10

HSPA

Latency Latency
(Round
trip delay)
(Rountripdelay) **

GSM/EDGE
GSM/EDGE
HSPA
Rel6
HSPA
Rel6
HSPAevo
HSPAevo
(Rel 8)

LTELTE
0

capacity bands: carriers up to 20MHz


Bandwidth
LTE 2.6GHz

New and large bands:


2x70MHz paired
1x 50MHz unpaired

1900/2100 MHz
1800 MHz/AWS
Refarming

850/900 MHz
LTE 700/800MHz (Digital Dividend)
Coverage
For public use IPR applies
4
Nokia Siemens Networks

CN60022EN50GLA0

20

40

60

80

100

120

140

160

180

DSL (~20- 50 ms, depending on operator)

200

ms

LTE

Voice over LTE - why and how


Voice over LTE is mandatory
to preserve the operators services business model in LTE
Method
IMS-VoLTE
Voice over LTE

CSFB
CS Fall Back

VoLGA
V. o. LTE Gateway

Fast Track
Fast Track to IMS

OTT
Over the top
For public use IPR applies
5
Nokia Siemens Networks

Comments

3GPP standard solution using IMS


Standard devices, inter-working and roaming procedures
Open to deploy more multimedia services (RCS)
LTE for data only (not really a VoLTE solution)
For voice calls the device connection falls back to 2G/3G
Data session is interrupted during voice call
Tunnels CS calls to LTE devices specific devices
Not a standard, did not find acceptance in the industry

Works on top of NSNs mobile switching system MSS


Provides voice and SMS only standard LTE devices
Uses Internet services over the data link (e.g. Skype)
Operator maintains the bit pipe

CN60022EN50GLA0

VoLTE evolution
SMS over LTE connection, LTE Broadband VoIP
Over the air configuration, prepaid information

Dual radio terminals for CDMA /LTE operators


Voice over CDMA and data over LTE

CS FallBack to 2G/3G

MSS SR
4.1

Voice over 2G/3G and data over 2G/3G or LTE

LTE voice technology take-off


times

VoLTE with QoS

Terminal and network


requirements meet each
other

Secured voice quality

MSS
IMS SR
5.0
2010

For public use IPR applies


6
Nokia Siemens Networks

CN60022EN50GLA0

2011

Dept. / Author / Date

VoLTE with SRVCC


Seamless voice continuity

2012

2013

LTE Features of MSS IMS System SR5.0 release


NSN introduces 3GPP IR.92 VoLTE capability

LTE SRVCC
SCC AS
VoLTE IMS - CS Interworking
Co-located multiple applications
VoLTE with QoS
GSMA VoLTE (IR.92)
IP-SM-GW for SMS over IP
Ut interface
HD video over LTE (IR.94)
Media Resource Function (MRF) for broadband voice
CS Fullback Support (already in SR4.1)

For public use IPR applies


7
Nokia Siemens Networks

* MSS VLR BU Solution General Availability (GA) granted for DX MSS M14.6 GCD10.3,
M15.0 MP1.3, M15.1 MP2.3, Open MSS M16.0 EP1 MP2.0
CN60022EN50GLA0

LTE Target Architecture


and product portfolio
NVS as TAS
Open to add more services

CMS-8200 with OneNDS for HSS


Subscriber data management

Applications
Applications
Applications

TAS

CMS-8200
+OneNDS

Sh
ISC
S6a

Cx

MME

CFX-5000 for IMS core control


CSCF, TRCF, MCF,

CFX-5000
S11

Gx

SIP

H.248

PCS-5000
eNb
LTE

S/P-GW

IP
Network
BGF

PCS-5000 for all Policy control


PCRF, SPDF,

LTE and an all-IP transport network simplifies the core


For public use IPR applies
8
Nokia Siemens Networks

CN60022EN50GLA0

VoLTE Evolution,
MSS and MGW reused
VoLTE Features

Drivers

1. CSFB
2. VoLTE with QoS and SMSHLR
GSMA VoLTE (IR.92) and video
(IR.94)

SDM

SCC AS SMSC
NVS TAS
MSS

3. SRVCC mobility
Voice

Voice core
HSS

IMS

SBC
MAG

Fixed
users

Seamless
2G/3G/LTE voice
experience
Fixed mobile
convergence
support

RCS
IMS VAS

HD video for LTE

2G/3G radio network

QoS for VoIP


BSS/NB

BSC /
RNC

Sv/SGs
MGW

PSTN
PCRF

CSFBSRVCC
MME
eNB
SMS Voice LTE radio network

For public use IPR applies


9
Nokia Siemens Networks

CN60022EN50GLA0

SGW
PGW
LTE Packet core

Intern
et

VoIP/RCS to
compete the OTT
VoIP threat
Single control point of
signaling and media
plane
Long term all-IP
network architecture

MSS IMS SR5.0 functional contents


MSS IMS SR 5.0 Products and Functions

RNC

SRVCC

MSC-S

CSFB

SCP

MGCF

BSC

MSS
TAS/MMTel

Ut

SMS-C

SCCAS

MRFC

MSS/NVS

IP-SMGW

HLR
DX HLR/NT HLR

IM-SSF

Gm
H.24
8

ISC
PCSCF

I/S-CSCF

Rx
SGs,S
v

Flexi NS

BGCF
ENUM

CFX-5000

eNodeB

MME

S6a

iNUM

Cx
PCRF

PCS-5000

CMS-8200

SR5.0 Function
H.24
8

MRFP

P-GW

Legend

HSS FE

Gx
S-GW

One NDS

Mg,
Mj

IMS-MGW

SR 5.0 Product

R4 MGW
Function

MGW

Flexi NG

Counterpart product

For public use IPR applies


10
Nokia Siemens Networks

CN60022EN50GLA0

Dept. / Author / Date

The Open Core System example: VoLTE


Co-Located Multiple Application
VoLTE functionality in two
cabinets
Software upgrade from
MSS to NVS with re-use
of existing blades and
network integration

MSS / NVS
CSFB,
MGCF, SCC-AS

12 3 45 6 78 9

common
Hub blades

Re-balance resources
from CS voice to the
VoLTE when traffic
requirements change

HLR

S-GW
P-GW
12 3 45 6 78 9

Introduce IMS
blades/shelf according to
traffic needs

11 11 1 11
1 111 1 11
1 2 345 6 7 89
01 23 4 56
0 123 4 56

CSCF / HSS-FE
PCRF
ENUM

11 1 1 1 1 1
01 2 3 4 5 6

12 3 45 6 78 9

11 1 1 1 1 1
01 2 3 4 5 6

MME
MGW
1 2 34 5 6 7 89

1 1 11 111
11 1 1 1 1 1
0 1 23 456 12 3 45 6 78 9
01 2 3 4 5 6

* for approx 600k subscribers with NSN traffic profile


For public use IPR applies
11
Nokia Siemens Networks

CN60022EN50GLA0

VoLTE key products and programs

MSC Server System Program (MSS SR) IMS and LTE


CSCF/
HSS /
(IMS)

MSS/
NVS/
MGW/
HLR
(M,U)

PCRF
(PCS)

NVS,
MSS,
MGW

PCS5000

EPC
(NS,NG)

Radio
(RL)

CFX5000
CMS8200

IMS VoLTE

For public use IPR applies


12
Nokia Siemens Networks

CN60022EN50GLA0

Flexi NS
Flexi NG

Flexi BS

MSS IMS SR5.0 Main Product Component


Releases

Product

Release

CFX-5000 (IMS) (Atca)

IMS9.1

CMS-8200 (HSS) (Atca)

IMS9.1

MGW (Atca)

Ui5.0EP1

MGW (IPA)

U5.0EP2

MSS/NVS (Atca)

Ma16.1

MSS/NVS (DX)

Md16.1

PCS-5000 (Atca)

6.3

For public use IPR applies


13
Nokia Siemens Networks

CN60022EN50GLA0

LTE Deployment Options


Exploring the differences between
CSFB, VoLGA, IMS VoLTE (Fast Track and Full IMS)

For public use IPR applies


14
Nokia Siemens Networks

CN60022EN50GLA0

VoLTE Deployment Options (1)

Contents:
CS Fallback (CSFB)
for Voice and SMS
VoLGA
IMS VoLTE (FastTrack and Full
IMS)

For public use IPR applies


15
Nokia Siemens Networks

CN60022EN50GLA0

VoLTE Deployment Options


Introduction

the LTE radio and EPC are IP only:

there is no CS domain anymore; therefore


Voice must also be carried over IP.

UEs may fall back into the existing 2G/3G CS network (CSFB),
but this is less efficient from a radio resource point of view.

Single Radio:

SRVCC

2G/3G
coverage

most UEs will only be capable to have one active radio,


LTE or GSM/UMTS, but not both. Active radio means
being able to send and receive via this radio technology.

Initially, there will only be Hot Spot Coverage:

Voice over LTE coverage will be in hot-spots only, thus Voice over LTE
and CS Voice needs to be supported for the same user
The same user experience is desired in 2G/3G CS and VoLTE.
A solution for Voice Call Continuity (handover) between
LTE and CS is required.

For public use IPR applies


16
Nokia Siemens Networks

CN60022EN50GLA0

LTE
cell

VoLTE Deployment Options


Solutions

1. IMS based Voice over LTE

includes the NSN IMS solution and the NSN FastTrack solution.

both solutions are compliant to the One Voice VoLTE profile


defined in GSMA VoLTE IR.92.
the NSN FastTrack is an initial step targeting a simple/easy
deployment solution, but only partially 3GPP IMS compliant.

IMS is the main stream 3GPP solution for LTE/VoIP

2. No VoIP/LTE, but fallback to 2G/3G CS:

3GPP Interim Solution. IMS is not needed at


all for voice and SMS when CSFB is used.

for voice: UE leaves LTE and uses 2G/3G CS to send/receive calls


for SMS: SMS can be sent and received while staying in LTE
it is all about timing: eventually LTE/IMS for VoIP and SMS
will substitute CSFB ... the question is when.

3. VoLGA formerly known as CS over PS (dead):

this is not accepted in the standards-/operator communities.

proprietary approach: CS and mobility signaling (Iu-CS)


is tunneled via IP/LTE access to the MSC.

For public use IPR applies


17
Nokia Siemens Networks

CN60022EN50GLA0

VoLTE Deployment Options


CS Fallback (CSFB) Solution

Motivation:

CSFB enables LTE introduction as a data-only type of network


in the beginning and makes the initial LTE investments smaller.
IMS roaming agreements are not in place yet.

Standards:

3GPP TS 23.272 describes CSFB


3GPP TS 29.118 describes the SGs-interface between the MSC and the MME

Support in NSN MSC Server:

SMS over SGs/LTE is supported in the M14.6 product release (MSS SR4.0)
CSFB for Voice is supported in the M15.0 product release (MSS SR4.1)

Voice calls

SMS
the terminal can stay in
LTE to send/receive SMS

the terminal switches to


3G or 2G for voice

LTE
For public use IPR applies
18
Nokia Siemens Networks

3G

2G

CN60022EN50GLA0

LTE

VoLTE Deployment Options


CS Fallback (CSFB) Solution

CSFB Procedure Overview:

UE performes a combined attach (EPS/CS)


Terminating Call: the MSC sends a paging request to the MME which is
then paging the terminal via eNB and request it to move to 2G/3G.
Ongoing Data Sessions may remain active in 2G/3G PS,
possibly at a lower bit rate, or are interrupted.

6. the CS Voice Call is delivered


to the UE via 3G/3G access

4. When receiving the Paging


Request, the UE returns the
CSFB Indicator to the
MME/MSC and performs
the Handover to 2G/3G

2G/3G coverage

5. The UE sends a
Paging Response via the
2G/3G access to the MSC

BSS
Handover
to 2G/3G

LTE Cell

MSC / VLR

eNB

- includes Location Update from the MSC to the HLR/HSS


CN60022EN50GLA0

3. MSC initiates Paging via MME/eNB

HSS /
HLR

1. UE performs Combined Attach (EPS/CS)


For public use IPR applies
19
Nokia Siemens Networks

2. Incoming Terminating CS Voice Call

MME

PDN-GW

VoLTE Deployment Options (2)

Contents:
CS Fallback (CSFB)
for Voice and SMS
VoLGA (dead)
IMS VoLTE (FastTrack and Full
IMS)

For public use IPR applies


20
Nokia Siemens Networks

CN60022EN50GLA0

IMS based VoLTE: Deployment Options


Voice over LTE via Generic Access (VoLGA)

What is VoLGA:

2G/3G CS and mobility signaling are tunneled via IP/LTE access


to keep the mobile core stable (but be able to exploit LTE for voice).

Based on Unlicensed Mobile

For public use IPR applies


21
Nokia Siemens Networks

CN60022EN50GLA0

Access (UMA) Concept


for Mobility over WLAN.
VAN Controller (VANC)
acts as interworking function.
No impact on the MSC (that
just sees the A/Iu interface).
supports CS voice and SMS.
Proprietary solution.
Kineto holds all relevant IPRs.

VoLTE Deployment Options (3)

Contents:
CS Fallback (CSFB)
for Voice and SMS
VoLGA
IMS VoLTE (FastTrack and Full
IMS)

For public use IPR applies


22
Nokia Siemens Networks

CN60022EN50GLA0

IMS based VoLTE: Deployment Options


NSN FastTrack

Motivation:

enable the operator to use VoIP/LTE with standard IMS Phones;


but without that the operator has to deploy a full IMS.
enable a stepwise deployment.

Provide Unchanged interfaces


to the old CS world

Provide standard interfaces


to the new LTE/IMS world

IMS Gm
UE

OAM, Charging

Sv, SGs

FastTrack
Solution
(MSS, NVS,
CFX5000)

MME

Nc
MSC-S

Gx
Mb

Nb

SAE-GW
For public use IPR applies
23
Nokia Siemens Networks

MGW
HLR
CN60022EN50GLA0

IMS based VoLTE: Deployment Options


NSN FastTrack

Architecture:

LTE functionality expansion to the existing NSN MSS


NVS VoIP Server upgrade on the MSS
deployment of the CFX5000/P-CSCF/PCRF

3GPP interfaces supported:

the Sv interface enables SRVCC support


the SGs interface enables CSFB
the Gx interface enables
standard QoS Control.
the Gm interface allows the
support of standard IMS Phones.

FastTrack
HLR
CFX-5000

SIP MSS/NVS

(P-CSCF/PCRF)

Sv,
SGs

(MSC-Server)

H.248

Gm,
Gx

Mobile Broadband Access


S11
S1-MME

Gm (SIP)

S1-U

eNB
For public use IPR applies
24
Nokia Siemens Networks

MME

CN60022EN50GLA0

SAE GW

MGW
RTP
RTCP

IPA 2800

IMS based VoLTE: Deployment Options


GSMA PRD IR.92 IMS Profile for Voice and SMS

Specification Scope:
the current 3GPP standards for Voice over LTE give
multiple alternatives for the Voice implementation and services
NSN fine tunes / defines a clear profile for voice
and SMS and takes into account both:
requests from network and terminal vendors.
While the technical profile is focused on LTE, the IMS/SIP
aspects of the profile are applicable to all cellular access types.

IMS VoLTE
profile

Terminal
For public use IPR applies
25
Nokia Siemens Networks

CN60022EN50GLA0

Network

IMS based VoLTE: Deployment Options


Summary
1. IMS based Voice over LTE

The NSN IMS solution


SRVCC for 2G/3G handover

2. No VoIP/LTE, but fallback to 2G/3G CS:

3GPP Interim Solution.


IMS is not needed for this.

3. VoLGA formerly known as CS over PS:

this is not accepted in the


standards-/operator communities.

For public use IPR applies


26
Nokia Siemens Networks

CN60022EN50GLA0

SRVCC Single Radio Voice Call Continuity


FN 2008

For public use IPR applies


27
Nokia Siemens Networks

CN60022EN50GLA0

SRVCC Single Radio Voice Call Continuity


SRVCC FN2008 is available for
MSS DX200 in Md16.1 (SR5.0) and for
MSS ATCA in Ma16.1 EP1 (SR5.0)
Feature code of license
3729 On/Off SRVCC Support in MSS
3284 On/Off Dynamic Payload Type restriction

For public use IPR applies


28
Nokia Siemens Networks

CN60022EN50GLA0

Introduction SRVCC
(Single Radio Voice Call Continuity)

E-UTRAN (4G) access together with EPC will provide Packet


Switched services for Mobile subscribers, and is able to provide
sufficient QoS for VoIP calls as well.
However, 4G access might be available only in spotted areas in the
first phases of introduction, which means that VoIP calls cannot be
maintained outside 4G coverage. In order to enable seamless voice
service from 4G access (VoIP) to 3G/2G (UTRAN/GERAN) access
(CS voice) the MSC Server SRVCC functionality has been specified
by 3GPP.

For public use IPR applies


29
Nokia Siemens Networks

CN60022EN50GLA0

Introduction SRVCC
(Single Radio Voice Call Continuity)

With SRVCC procedure the Mobile subscribers are able to


roam outside 4G coverage without the call being disconnected.
The SRVCC functionality will cause challenges for the MSS enhanced
with SRVCC, called as MSS(SRVCC).The UE shall move in SRVCC
from 4G to 3G/2G with limited amount of information, no signaling
connection and not attached to any CS services. The SRVCC
procedure shall be also done in very short period of time during which
also user plane, charging and statistics shall be fixed.

For public use IPR applies


30
Nokia Siemens Networks

CN60022EN50GLA0

Architecture SRVCC
(Single Radio Voice Call Continuity)

2G/3G

UE

MSS(SRVCC)

IMS = IP Multimedia Subsystem


NVS = VoIP Server
IMS or NVS

Handover/Relocation

Sv
SCC AS

SCC AS = Service Centralization and


Continuity Application Server
(Provides IMS-based mechanisms for
enabling service continuity of
multimedia sessions)

4G (LTE)
UE

For public use IPR applies


31
Nokia Siemens Networks

MME

CN60022EN50GLA0

LTE voice options


LTE used for data service only
Recommended
Step1: CSFB via
existing MSS

Recommended Step2:
VoLTE via NVS upgrade

For public use IPR applies


32
Nokia Siemens Networks

Voice via 3G/2G based on


standardized CS Fallback

VoLTE compliancy to
Multimedia IMS-based VoLTE.
NVS as IMS TAS

CN60022EN50GLA0

Sv

ISC

SRVCC Configuration at network level


SMSC
MAP

IMS

MSS
(SRVCC) SIP
SIP-I
BICC..

MGCF
SIP

HLR
H.248

SRVCC enhanced MSC


Server {called as
MSS(SRVCC)} function is
always in MSC/MSS

H.248

MGW

MGW

SCC AS functionality is co-

SIP/Gm

located in NVS or in
CFX5000 / CMS8200
(MCF)

Sv

All interfaces according to

RTP
RTCP

3GPP TS 23.216 (Single


Voice Call Continuity)
S11

S1-MME

VoLTE
UE

SIP/Gm

For public use IPR applies


33
Nokia Siemens Networks

x-CSCF
SCC AS
NVS or
CFX5000/
CMS8200

eNb
CN60022EN50GLA0

MME
S1-U

SAE GW

Note. MGCF function is


needed with
MSS(SRVCC)
only if ISUP/BICC
signaling
is used as outgoing
signaling from
MSS(SRVCC). If using
SIP signaling as outgoing
signaling from
MSS(SRVCC), the MGCF
function is not needed at
all.

LTE SRVCC

SR5.0
SCC AS

Challenge

LTE coverage will be limited by the time VoLTE is launched and therefore handover from
LTE to 2G/3G is necessary for keeping calls alive when people move during calls
IMS will eventually handle VoIP in LTE and 2G and 3G remain circuit switched and this
brings SIP / CS change request in addition to change of used radio technology
LTE terminals have only one radio active at the time => handover between LTE and
2G/3G are time critical functionality

Solution
MSS implements the 3GPP release 8 standardized Single Radio Voice Call Continuity
(SRVCC) functionality, which enables call continuity from the LTE VoIP towards the
2G/3G CS core network

Operator benefits
SRVCC makes it possible to introduce primary voice service in LTE so that
both operator voice and wideband data services are simultaneously available
When moving from LTE coverage area to 2G/3G area voice and data calls
continues without interruption
SRVCC secures high quality user experience, especially in the LTE
introduction phase when LTE access coverage is still sparse and limited

For public use IPR applies


34
Nokia Siemens Networks

CN60022EN50GLA0

LTE SRVCC

SR5.0

Functionality:

SCC AS

Voice over CS for


MGW
Sv-interface between MME and MSS is introduced
2G/3G access
for SRVCC purpose.
Terminal measures neighboring cells signal
BSC
MSS
strengths. When the intersystem access change
PSTN/
(SRVC
criteria from LTE to 2/3G are met, Node B initiates
PLMN
C)
handover toward MME. Based on subscription
information MME knows whether SRVCC can be
NVS with colocated
HLR
applied to a terminal. While the intersystem change
MAP
is needed and there exist a real-time bearer, MME
SCC AS/T-ADS and
initiates a SRVCC toward the MSS.
M
g
TAS is the
S
MSS reserves the target cell resources from 2G/3G
v
access from same MSS, or through inter MSS
anchoring point
handover. MSS also utilizes embedded MGCF
MME
functionality (Mg) to makes a call towards the VCC
Cx
IP
anchoring point (SCC AS) based on received
S1
Session Transfer Number (STN-SR).
IMS/
HSS services
1
Gx
The anchoring point is responsible for the session
CFX-5000
continuity from PS to CS bearer. After these actions
MSS sends a response to MME and the terminal is
SAE-GW
eNb
commanded to handover to the target cell.
Support required (e2e viewpoint): Voice over IP for LTE access

The VoLTE call prior the SRVCC has been established with dedicated bearers (P-CSCF, PCRF)
LTE-Node-B, MME and MSS need to be upgraded for supporting SRVCC
LTE terminal supporting the SRVCC
HSS/HLR is provisioned with STN-SR.
No new functionality introduced to MGW but existing functionality is reused by SRVCC MSS
The SRVCC is planned to be enhanced in SR5.0 PT-2 to support in addition to the transfer of
single active call also one inactive/held call (enhancement to MSS with SRVCC, SCC AS).

For public use IPR applies


35
Nokia Siemens Networks

CN60022EN50GLA0

SCC AS for SRVCC

SR VCC

Challenge:

SR5.0

LTE coverage will be limited by the time VoLTE is launched and therefore handover from LTE to
2G/3G is necessary for keeping calls alive when people move during calls
IMS will eventually handle VoIP in LTE and 2G and 3G remain circuit switched and this brings SIP
/ CS change request in addition to change of used radio technology
LTE terminals have only one radio active at the time => handover between LTE and 2G/3G are
time critical functionality
New dedicated network elements to be avoided

Solution:

NVS functionality of MSS implements the Service Centralization and Continuity Application
Server (SCC AS) role including Terminating Access Domain Selection (T-ADS) functionality
to support the 3GPP release 8 standardized Single Radio Voice Call Continuity (SRVCC)
solution, needed to enable call continuity from the LTE VoIP towards the 2G/3G CS core network

Operator benefits
Existing elements upgraded by software upgrade only
Scalable and integrated cost effective SCC AS/T-ADS functionality
Optimized architecture for interfaces, signaling loads and service
interruption times
Seamless interworking with existing O&M and statistical tools
Geo redundancy supported

For public use IPR applies


36
Nokia Siemens Networks

CN60022EN50GLA0

SCC AS for SRVCC


Functionality:
In order to support SRVCC requirements, the NVS TAS
is enhanced with call anchoring and session transfer
functionality
When VoLTE subscriber registers in IMS, the
corresponding NVS is triggered to provide it TAS/MRFC,
IP-SM-GW and SCC AS/T-ADS functionalities. NVS can
co-locate with the MSS implementing the SRVCC
The anchoring functionality is triggered when a user
initiates/receives a call and if the user has a Session
Continuity subscription in the HSS and NVS
The MSS initiates the session transfer call towards the
IMS using the session transfer number for single
radio (STN-SR)
The S-SCSF triggers the call to the corresponding
NVS/SCC AS via ISC interface and NVS performs the
session transfer taking into account the possible need
for MGW resource.
The SRVCC is planned to be enhanced in SR5.0 PT-2 to
support in addition to the transfer of single active call
also one inactive/held call (impact to MSS with SRVCC,
SCC AS).

SR5.0
SR VCC

Voice over CS for

MGW

2G/3G access

PSTN/
PLMN
MSS (SRVCC)

BSC

HLR
MAP

NVS
S
v

MME
Cx

S1
1

eNb

Gx

IMS/
HSS
CFX-5000

SAE-GW

Support required (e2e viewpoint):


Voice over IP for LTE access
LTE-Node-B, MME and MSS upgraded for supporting SRVCC
MSS is upgraded with SRVCC and NVS TAS upgraded with SCC AS/T-ADS functionality
HSS/HLR supporting the SRVCC related information
LTE terminal supporting the SRVCC
For public use IPR applies
37
Nokia Siemens Networks

CN60022EN50GLA0

IP
services

Overview SRVCC
(Single Radio Voice Call Continuity)

The MSS(SRVCC) (=MSC Server Enhanced for SRVCC) shall


support the following additional functionalities for SRVCC:
The Sv interface support between the MME/SGSN and the
MSS(SRVCC)
Handling the relocation/handover request for the voice component
Coordinating the CS relocation/handover and SIP session transfer
Interworking with SIP session transfer procedure to CS
Handling the Location Update instead of the terminal

The feature shall be optional and shall be controlled with an


ON/OFF license and shall be applicable for both DX and
Open (ATCA) MSS.

For public use IPR applies


38
Nokia Siemens Networks

CN60022EN50GLA0

Sv interface
New interface Sv between MME and MSS with SRVCC function.
The Sv interface is defined for SRVCC functionality by 3GPP TS 23.216
and 3GPP TS 29.280.
Two nodes communicate with GTP tunnels over a GTP based interface. A
GTP tunnel is identified in each node with a Tunnel Endpoint Identifier
(TEID), an IP address and a UDP port number.
The Sv interface establishes connection between the MSS and the
MME/SGSN to enable the SRVCC specific procedures.
The MSS acts as a server and the MME/SGSN as a client.

For public use IPR applies


39
Nokia Siemens Networks

CN60022EN50GLA0

Sv interface
The receiving end side of a GTP tunnel locally assigns the transmitting side the TEID value to
use. The same tunnel is shared for the control messages related to the same UE operation.
GTP tunnels separate traffic into different communication flows. GTPv2-C messages are sent
per UE over the Sv interface.
GTP tunnel with unique TEID value is SRVCC procedure specific !!! On top UDP/IP link,
there can be multiple GTP tunnels simultaneously for SRVCC procedures per
subscribers (limiting factor is SRVCC specific hand count in SV0PRB 1000
simultaneous SRVCC sessions per xSU)

For public use IPR applies


40
Nokia Siemens Networks

CN60022EN50GLA0

Sv interface connectivity
There can be max. 100 MME/SGSNs configured to one MSS/VLR. Every
MME/SGSN can have max. 32 UDP link address per one MSS/VLR. UDP
links from one MME cannot be configured to same signaling unit (BSU or
GISU)
Links can be used equally within one SRVCC procedure
MME/SGSN configuration file controlled by EJ MML command group, has
main MME/SGSN address data, link state, logical address of MSS signalling
unit(s), FQDN, MSS restart counter and index to parameter file.
MME/SGSN parameter file controlled by EJ MML command group, has
common configuration data of one physical MME/SGSN. Record 0 is
reserved for default values. Data includes default SAI, echo handling
configuration, timers, retransmission timer and amount, control information.
Note: There can be max 100 SGs MME IP addresses configures and additional max
100 Sv MME IP addresses.

For public use IPR applies


41
Nokia Siemens Networks

CN60022EN50GLA0

Sv interface connectivity model, example 1


MME/SGSN

MSS
xSU-0
SV0

AIF

Centralized unit

VLR

xSU-1
SV0

AIF

xSU-2
SV0

AIF

SVEFIL config (EJ MML):


MME_SGSN_index=0
(Unit-0)
UDP_link=0: xSU-0
UDP_link=1: xSU-1
UDP_link=2: xSU-2
UDP_link=3: xSU-n
For public use IPR applies
42
Nokia Siemens Networks

CN60022EN50GLA0

xSU-n
SV0

AIF

Sv interface connectivity model, example 2


MME/SGSN

MSS

SVEFIL config (EJ MML):

xSU-0

Unit-0

UDP link 0

SV0

AIF

xSU-1

Unit-1

SV0

VLR
AIF

UDP link 1
xSU-2
Unit-2

UDP link 0

SV0

AIF

xSU-n

Unit-n

SV0

UDP link 1

For public use IPR applies


43
Nokia Siemens Networks

CN60022EN50GLA0

AIF

MME_SGSN_index=0 (Unit-0)
UDP_link=0: xSU-0
UDP_link=1: xSU-1
MME_SGSN_index=1 (Unit-1)
UDP_link=0: xSU-0
UDP_link=1: xSU-1
MME_SGSN_index=2 (Unit-2)
UDP_link=0: xSU-2
UDP_link=1: xSU-n
MME_SGSN_index=n (Unit-n)
UDP_link=0: xSU-2
UDP_link=1: xSU-n

Create Sv interface configuration with the EJB


command.
ZEJB:TYPE=SV,NAME=MME1:ADDR="10.85.17.31",IND=0,PIND=0,
ASTATE=ACTIVE,FQDN="mmec12.mmecgi23.mme.epc.mnc03.mcc262.3g":;
TYPE interface type
NAME MME/SGSN name
NBR MME/SGSN number
ADDR MME/SGSN primary IP address
IND unit index in the MSS
PIND MME/SGSN parameter set index
ASTATE administrative state of the UDP link
FQDN MME/SGSN fully qualified domain name

For public use IPR applies


44
Nokia Siemens Networks

CN60022EN50GLA0

Interrogate Sv interface configuration with the EJJ


command.
ZEJJ:TYPE=SV,NAME=MME1;
OUTPUT SV INTERFACE CONFIGURATION
SGSN/MME NAME .................(NAME).. :MME1
SGSN/MME NUMBER ...............(NBR)... :0
FULLY QUALIFIED DOMAIN NAME ...(FQDN).. :mmec12.mmecgi23.mme.epc.mnc03.mcc262.3g
PARAMETER SET INDEX ...........(PIND).. :0
RESTART COUNTER FOR UDP LINKS..(RECNT). :0
SV INTERFACE CONNECTIONS
========================
SGSN/MME IPV4 ADDRESSES
----------------------10.85.17.31
SGSN/MME IPV6 ADDRESSES
----------------------NONE
For public use IPR applies
45
Nokia Siemens Networks

CN60022EN50GLA0

UNIT INDEX
---- ----BSU 0

ASTATE OSTATE
----------ACTIVE
DOWN

UNIT INDEX
---- -----

ASTATE OSTATE
-----------

Sv interface messages
SRVCC procedure specific messages:
SRVCC PS to CS Request
SRVCC PS to CS Response
SRVCC PS to CS Complete Notification
SRVCC PS to CS Complete Acknowledge
SRVCC PS to CS Cancel Notification
SRVCC PS to CS Cancel Acknowledge

GTP protocol specific messages:


Echo Request
Echo Request Acknowledgement
Version Not Support

For public use IPR applies


46
Nokia Siemens Networks

CN60022EN50GLA0

High level concepts for SRVCC


from E-UTRAN to UTRAN/GERAN

For public use IPR applies


47
Nokia Siemens Networks

CN60022EN50GLA0

SRVCC Function
When the subscriber moves from LTE to 2G/3G, the SRVCC capable terminal
measures the signal strength of the neighboring cells and sends measurement
reports to E-UTRAN.
When the inter-system access change criteria from LTE to 2G/3G are met, the
eNodeB initiates PS to CS handover request to the MME.
Based on the Session Transfer Number for SRVCC (STN-SR), that is, SRVCCspecific subscription information stored in the HSS and the HLR, the MME knows
whether the SRVCC procedure can be applied to the terminal and hence to the
subscriber.
If the subscriber is entitled for SRVCC based on STN-SR information, radio access
change is required based on the measurement reports, and also a real-time bearer
exists, the MME triggers the SRVCC procedure for the voice component with
the MSS enhanced for SRVCC over the Sv interface.

For public use IPR applies


48
Nokia Siemens Networks

CN60022EN50GLA0

SRVCC Function
The MSS enhanced for SRVCC coordinates the SRVCC procedure with the CS
handover procedure.
The MSS enhanced for SRVCC can reserve the target cell resources from 2G/3G
access in the same MSS or with an inter-MSS handover from a target MSS.
The MSS enhanced for SRVCC also initiates the session transfer procedure to
the Voice Call Continuity anchoring point. The anchoring point is responsible for
the session continuity from PS to CS bearer. For facilitating session transfer of the
voice component to the CS domain, IMS multimedia telephony sessions need to be
anchored in the IMS and in the Service Centralization and Continuity Application
Server (SCC AS).
In the Nokia Siemens Networks VoLTE solution, the SCC AS function resides in the
NVS.
The MSS enhanced for SRVCC then sends PS to CS handover response to the
MME, which includes the necessary CS handover command information for the UE
to access UTRAN/GERAN.

For public use IPR applies


49
Nokia Siemens Networks

CN60022EN50GLA0

SRVCC Function
Handling of any non-voice PS bearer is managed by the PS bearer
splitting function in the MME.
The MME starts the handover of non-voice PS bearer during the SRVCC
procedure based on the information received from E-UTRAN.
The handover of non-voice PS bearers, if performed, is done according to
Inter RAT handover procedure as defined in 3GPP TS 23.401.
The MME is responsible for coordinating the Forward Relocation Response
from SRVCC and PS handover procedure.

For public use IPR applies


50
Nokia Siemens Networks

CN60022EN50GLA0

PS to CS SRVCC relocation/handover to MSS(SRVCC) UTRAN/GERAN

(1) User Plane termination reserved from target MGW


for A/Iu resource towards target BSC/RNC
(2) User Plane
termination reserved
from anchor MGW for
outgoing Call Control
leg towards IMS (this
is anchor termination
for whole SRVCC
call).

(3) User Plane through connection for speech path !

For public use IPR applies


51
Nokia Siemens Networks

CN60022EN50GLA0

PS to CS SRVCC relocation/handover to target MSS UTRAN/ GERAN


(1) User Plane termination reserved
from target MGW for A/Iu resource
towards target BSC/RNC

(2) User Plane


termination reserved
from anchor MGW for
outgoing resource
towards Target MSS
(this is target leg
termination)
(4) User Plane
termination reserved
from anchor MGW for
outgoing Call Control
leg towards IMS (this
is anchor termination
for whole SRVCC
call).

(3) User Plane termination reserved


from target MGW reserved for incoming
Call Control leg.

Note1. Steps (1), (2) and (3) are


always repeated if the UE
continues the movement to next
target MSS with subsequent
Inter-MSS handovers/relocations.

(5) User Plane through connection


for speech path !

For public use IPR applies


52
Nokia Siemens Networks

CN60022EN50GLA0

Note2. In case of SIP between


MSS(SRVCC)
and Target MSS(CC call leg), the SIP
messages (INVITE/200 OK/ACK) are
used instead of ISUP/BICC messages
(IAM/ACM/ANSWER).

Failure before SRVCC PS to CS Response

For public use IPR applies


53
Nokia Siemens Networks

CN60022EN50GLA0

Failure after SRVCC PS to CS Response

For public use IPR applies


54
Nokia Siemens Networks

CN60022EN50GLA0

Location update rejected after successful SRVCC handover

(or call is continued, see below)

Procedure:
1.The MSS (SRVCC) starts a Location Update procedure.
2.The Location Update is rejected.
3.As a result, depending on the operator settings, the call is either cleared (DISCONNECT to UE)
or the call will be continued (CALLINT parameter setting):
Modify the Sv parameter set with EJN command to the required value if needed.
ZEJN:MODIFY:TYPE=SV,PNAME=<parameter set name>:CALLINT=<YES/NO>;

Note. If the call is not cleared, the supplementary services (for example, call waiting) can
not be supported by the MSS (SRVCC).
For public use IPR applies
55
Nokia Siemens Networks

CN60022EN50GLA0

SRVCC handover using TFO/WB-AMR

For public use IPR applies


56
Nokia Siemens Networks

CN60022EN50GLA0

SRVCC handover using TrFO/WB-AMR

For public use IPR applies


57
Nokia Siemens Networks

CN60022EN50GLA0

Other supported procedures with SRVCC


TMSI reallocation with SRVCC
1. The SRVCC handover procedure is successful.
2. The MSS enhanced with SRVCC performs a location update procedure.
The IMSI is unknown to the MSS/VLR.
The MSS(SRVCC) performs a TMSI reallocation procedure toward the UE
using a nonbroadcast LAI and its own NRI if the MSS(SRVCC) and other
MSS/VLRs serve the same (target) LAI.
MAP Update Location is sent to the HLR after the TMSI reallocation procedure.

Signalling unit reset


1.
2.

The Sv interface UDP/IP control plane connection is established between the EMSS
and the MME.
Spontaneous reset of the signalling unit can happen in the MSS(SRVCC) in the
following scenarios:
while the Sv interface is established between the MSS(SRVCC) and the MME
during an ongoing SRVCC handover procedure
Note 1: All ongoing active procedures/dialogs are aborted in the unit under reset.
Note 2: After the reset, the Sv interface connection is established between the MSS(SRVCC) and the MME.

For public use IPR applies


58
Nokia Siemens Networks

CN60022EN50GLA0

Other supported procedures with SRVCC


Signalling unit switchover
1. The Sv interface UDP/IP control plane connection is established between
the EMSS and the MME.
2. Switchover of the signalling unit in the MSS(SRVCC) can happen in the
following scenarios:
while the Sv interface is established between the MSS(SRVCC) and the MME
during an ongoing SRVCC handover procedure
Note 1: The new active signalling unit takes over all ongoing active procedures/dialogs after the switchover.
Note 2: The new active signalling unit takes over the Sv interface connection between the EMSS
and the MME after the switchover.

For public use IPR applies


59
Nokia Siemens Networks

CN60022EN50GLA0

Other supported procedures with SRVCC


Supplementary Services with SRVCC

All traditional 2G/3G related Supplementary Services are


supported but those are applicaple only after the successful
SRVCC procedure (after successful LU procedure generated by
MSS in the end of SRVCC procedure completion).

For public use IPR applies


60
Nokia Siemens Networks

CN60022EN50GLA0

SRVCC in Pool concept


Location update and TMSI reallocation in MSS configurations
LAI of SRVCC default SAI is configurable with the EJN command.
Non-broadcast LAI is configurable with the E3E command.
Both LAI part of SRVCC default SAI and non-broadcast LAI must be defined
in the MSS radio network configuration but cannot be identical to any real
radio network LAI.

For public use IPR applies


61
Nokia Siemens Networks

CN60022EN50GLA0

Statistics with SRVCC


Traffic category measurement report (20/14H)
Traffic category SRVCC originating calls is included in the measurement.
Handover measurement report, part 1 (81/51H)
The SRVCC procedures and their success ratio are included in the handover measurement
report.
VLR measurement report (82/52H)
The SRVCC Location update procedure initiated in the MSS(SRVCC) is included separately in
the VLR measurement. The following two counters are introduced:

Number of attempted SRVCC Location Update procedures


Number of successful SRVCC Location Update procedures

Destination measurement reports (17/11H, 24/18H, 25/19H, 385/181H)


The reports display STN-SR number as destination number in the MSS(SRVCC). The layout of these
measurements is unchanged.
MSC observation report (96/60H)
The MSC Observation report can indicate if the call is coming from LTE to GSM/UMTS
access using SRVCC. The MME IP address initiating the SRVCC procedure is also
available in the MSC Observation report.

For public use IPR applies


62
Nokia Siemens Networks

CN60022EN50GLA0

Statistics with SRVCC


Handover observation report (97/61H)
The Handover observation report includes:
SRVCC-related values in Handover Type field:
SRVCC TO MSS(SRVCC) GSM/UMTS
SRVCC TO TARGET MSS GSM/UMTS
MME address
The report includes the IP address of the MME initiating the SRVCC procedure.

Location update observation report (90/5AH)


The Location update observation report (90/5AH) includes
SRVCC-related value SRVCC LOCATION UPDATE in location update type field
The MME IP ADDRESS field displays the address of MME initiating the SRVCC procedure.
For more information on statistical reports, see NSS Statistics, Reports.

For more information on counters, consult the Reference Information Services portal of
Product Information Center (PIC).

For public use IPR applies


63
Nokia Siemens Networks

CN60022EN50GLA0

Charging with SRVCC


MGW

SCP

RNC
MSS
(SRVCC)
BSC

MGCF

CDR

CDR

HLR

CDR

P/I/SCSCF

eNB
MME
PCRF

HSS

NVS/SCCAS
CDR

SAE-GW

Orinating/
Terminating
network

SCP
TDM

IP MGW
MGW

TDM/IP

SR-VCC signalling in LTE (before SRVCC)


SR-VCC signaling in CS (after SRVCC)
User plane before SRVCC
User plane after SRVCC
For public use IPR applies
64
Nokia Siemens Networks

CN60022EN50GLA0

Charging with SRVCC


TO BE NOTE: The main control of charging is in IMS side (in where the voice call was
anchored) !! The following describes only the SRVCC related charging actions in MSS side with
SRVCC.
The following CDR fields have been modified to increment SRVCC functionality:

CALL_TYPE
The field contains the type of the call.
The field has been extended with the following value:
14 Voice Call Continuity
The field is available in MOC, MTC, FORW, ROAM, SMMO, SMMT, POC, PTC, PBXO, PBXT, DOC,
RCC, SMMF, SOC, STC, SOM, and STM CDRs.

LOC_UP_INDICATOR
The field indicates the type of location update.
The field has been extended with the following values:
00H Location update
01H GPRS location update (Note. This value is valid only in CDRs generated by the HLR.)
02H Location update due to Voice Call Continuity . (Note. This value is valid only in CDRs generated by the
MSS/VLR, and is only available if Feature 2008:
SRVCC Support in MSS is activated.)

The field is available in LOCA and SIPR CDRs

For public use IPR applies


65
Nokia Siemens Networks

CN60022EN50GLA0

Charging with SRVCC


MME_IP_ADDRESS
The field contains the IP address of the Serving MME.

If the CDR is generated due to Tracking Area Update, the field


contains the IP address of the target MME.
If the CDR is generated due to SRVCC, the field contains the IP
address of the MME which initiating the SRVCC procedure.
The field is available in LOCA CDR.
For more information on CDRs and charging, see CDR Field Descriptions in
M16.1 and Charging, Functional Area Description.

For public use IPR applies


66
Nokia Siemens Networks

CN60022EN50GLA0

3GPP SRVCC specifications


(Relevant for MSS)

TS 23.216 Rel 8
Single Radio Voice Call Continuity (SRVCC); Stage 2

TS 29.280 Rel 8
Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and
SGSN to MSC) for SRVCC

TS 29.274 Rel 8
3GPP Evolved Packet System (EPS); Evolved General Packet Radio
Service (GPRS) Tunneling Protocol for Control plane (GTPv2-C);
Stage 3

For public use IPR applies


67
Nokia Siemens Networks

CN60022EN50GLA0

Standardization steps with SRVCC

Rel-8 Officially part of GSMA IR.92 current baseline

Rel-9 Commercial pressure increasing to have this as soon as possible similarly as with CSFB

All basic SRVCC functionality (PS->CS domain transfer) for single active call
Support for PS->CS domain transfer for active and held calls in stable state
Calls in alerting phase are discontinued
Mid-call assisted call transfer

MSC Server assisted mid-call feature can only be triggered if UE, MSC Server, and SCC AS support the MSC Server
assisted mid-call feature
Requires M-AGCF/ICS enhanced MSC server functionality in network element that performs SRVCC role

Rel-10

Enhancement for SR-VCC performance by implementation of media anchoring in serving network with Visited Access
Transfer Functionality (VATF)
Co-located in visited/home P-CSCF to anchor media plane with GW functionality
Support for video telephony PS->CS->PS domain transfer (vSR-VCC)
Support for alerting phase domain transfers

Rel-11

Support for CS->PS domain transfer (rSR-VCC)

Rel-10 functionality is the first release to meet the existing functionality of mobile CS networks!

SRVCC defined also for VoIP/HSPA->CS (Rel8) and vice versa (Rel10) but that business need for that
functionality is unclear

For public use IPR applies


68
Nokia Siemens Networks

CN60022EN50GLA0

Changes with Sv interface connectivity in M17.0


Sv interface using IPDU Load Balancer

EMB

xSU-0

UDP/IP link 1
IPDU-0

xSU-1
xSU-2

UDP/IP link 2
xSU-3

UDP/IP
link 3
IPDU-1

UDP/IP link n

xSU-4

xSU-n

IPDU is N+1
redundant LinDX
based unit.
For public use IPR applies
69
Nokia Siemens Networks

CN60022EN50GLA0

Ethernet port (EL4 / EL5)