Single Radio Voice Call

Continuity
(SRVCC)
By
Kumar G S
 Core functionality

• Basics about SRVCC

• SRVCC Architecture
• Registration Procedure
• Access transfer Procedures for ATU STI
• Access transfer Procedures for STN-SR
SRVCC Architecture
 SRVCC Architecture

SCC AS

ISC

I /S-CSCF

Mw / Mx

Gm Mw / Iq/ Ix
P- CSCF Mx ATCF * ATGW *

UE
Mw / I 2**

CS Access MSC Server

*: Location of functionality **: Reference point dependent

depends on deployment and on MSC Server capability
.
collocation scenario
 Mobile Switching Centre
(MSC)
• The Mobile-services Switching Centre (MSC) constitutes the
interface between the radio system and the fixed networks.

• The MSC performs all necessary functions in order to handle

the circuit switched services to and from the mobile stations.

• The MSC typically comprises different entities: the MSC

Server (handling the control plane) and the CS-MGW
(handling the user plane).

• It is assumed that the MSC has been upgraded to support

both eSRVCC and IMS Centralised Services and is
responsible for the CS-IMS interworking.
 ATCF/ATGW (Access Transfer Control
Function/Access Transfer Gateway)

• The ATCF is a function in the serving IMS network (visited

network in the roaming case). It enables SRVCC Session
Transfer mechanisms in the serving network for a UE.

• The SCC AS can provide Session Transfer mechanisms in the

serving network, if an ATCF is present in the SIP registration
path of the UE, as defined in 3GPP TS 23.237

• The ATGW is a media function that is used to anchor the media

for enhanced SRVCC procedures as defined in 3GPP TS 23.237
[84]. The ATCF/ATGW may be co-located with the IMS-
ALG/IMS-AGW or IBCF/TrGW elements.
 SCC AS (Service Centralisation and Continuity
Application Server)

• The SCC AS is an IMS Application Server that provides

functionality to enable IMS Centralized Services (ICS)

• It provides IMS-based mechanisms for enabling service

continuity of multimedia sessions as defined in 3GPP TS
23.237 [84].
UE Registration with ATCF is
in Path
 E-UTRAN attach/IMS Registration and Deregistration

UE1 SGW/
MME P-CSCF ATCF/ATGW IMS Core SCC AS HSS
PS CS PGW

EPC attach procedures

IMS bearer establishment
SIP REGISTER REGISTER (Feature-Caps:*;
+g.3gpp.atcf="<tel:+123788
89999>;+g.3gpp.atcf-mgmt-
uri="<sip:actf.xyz.net>";+g.
3gpp.atcf-
path=”sip:termatcf@actf.xy
z.net”
ATCF will include a Feature-Caps
header in the REGSITER
containing
(i) +g.3gpp.atcf feature tag with
value as ATCF’s STN-SR, and
(ii) +g.3gpp.mgmt-uri feature tag
with value containing a URI that will
be used to send SIP MESSAGE to
ATCF
(iii)+g.3gpp.atcf-path feature tag
containing ATCF’s UEI in the Path
header

200 OK
200 OK REGISTER

SCC AS gets UE-SRVCC-Cap and UDR

STN-SR from HSS. If needed
updates STN-SR in HSS. HSS push UDA(STN-SR, UE-
the updated STN-SR to MME SRVCC-Cap)
200 OK
SIP MESSAGE is sent to the ATCF management URI
included in +g.3gpp.mgmt-uri feature tag the in REGISTER SCC AS sends
MESSAGE
by ATCF. This request contains the SRVCC-info xml SRVCC info to
(defined in 3GPP TS 24.237). Example – ATCF. Independent
200 OK of Sh operations
Content-Type: application/vnd.3gpp.SRVCC-info+xml

<?xml version="1.0" encoding="UTF-8"?>

<SRVCC-infos> SCC AS compares STN-SR with the
PUR (STN-SR)
<SRVCC-info ATCF-Path-URI="sip:termatcf@actf.xyz.net"> one sent by ATCF and if differs,
<ATU-STI>sip:sccas.xyz.net</ATU-STI> updates STN-SR in HSS
PUA
<C-MSISDN>tel:+12375551111</C-MSISDN>
</SRVCC-info>
</SRVCC-infos>

UE deregisters
REGISTER (expires=0)

ATCF adds Feature-

Caps header as
mentioned above

200 OK REGISTER
(expires=0)

200 OK
• The ATCF adds its identity into the PATH header and also
includes a Feature Tag header containing the following in
Register message while sending towards ICSCF

Feature-Caps:
*;+g.3gpp.atcf="<tel:+12378889999>";+g.3gpp.atcf-mgmt-uri=
"<sip:atcf.mavenir.net>";+g.3gpp.atcf-
path="<sip:termxyz@atcf.mavenir.net>"
Path: <sip:termxyz@atcf.mavenir.net>,
sip:abc@pcscf.mavenir.net:5070;ob

E.g: without Feature-Caps:

Path: <sip:termxyz@atcf.mavenir.net>;+g.3gpp.atcf="<tel:
+12378889999>";+g.3gpp.atcf-mgmt-
uri="<sip:atcf.mavenir.net>",<
sip:abc@pcscf.mavenir.net:5070;ob>
• After Registration successful at SCCAS, It sends a SIP MESSAGE to the ATCF
containing an XML body (vnd.3gpp.SRVCC-info+xml) containing the ATU-STI
and C-MSISDN. The ATCF responds to the SCC AS with a 200 OK message.
<?xml version="1.0" encoding="UTF-8"?>
<SRVCC-infos>
<SRVCC-info ATCF-Path-
URI="sip:termxyz@atcf.mavenir.net;transport=tcp;lr">
<ATU-STI>sip:sccas1@mavenir.net</ATU-STI>
<C-MSISDN>tel:+12375551111</C-MSISDN>
</SRVCC-info>
</SRVCC-infos>

• The SCC AS notes that the STN-SR associated with the user has changed and
informs the HSS via a DIAMETER PUR message. The HSS stores the new
STN-SR against the user and responds with a DIAMETER PUA message.

• In turn, the HSS informs the MME that the STN-SR has changed via a
DIAMETER IDR message. The MME stores the new STN-SR and responds with
a DIAMETER IDA message.
Access transfer Procedures
for SRVCC
TYPES :
• Access transfer with ATU-STI(eSRVCC)
• Access Transfer with STN-SR (SRVCC)
 Handover Initiation from
EUTRAN to GERAN/UTRAN
 Access transfer Procedures
for SRVCC(cont’d)
Access transfer with ATU-STI(eSRVCC)
FLOW: Configuration :
• Identification of Access-TasSccAsInternal
transfer request AtuSti
• Identification of :sip:09999@domain.com
Transferable session SccAsLocalConfig
• SDP Speech Component transferOnAtuSti(‘TRUE’)
comparison
• Remote leg Update
• Releasing of Source leg
 Access transfer Procedures
for SRVCC(cont’d)
Access transfer with ATU-STI(eSRVCC)

UE1 SRVCC Target

Target
MSC/ Target ATCF/ SCC
E-UTRAN MME HLR MGCF
CS PS IWF MGW
MSC BSS/RNC ATGW AS
IP Bearer IP Bearer

Measuremen SRVCC PS to CS
HO Required Req (Target Cell,
t reports (Target Cell, STN-SR, C-
SRVCC HO MSISDN,
indication) SourceToTargetC
ontainer)

Selects MSC from LAI

to MSC table
MAP PrepareHO Req (Target Cell, HO Request) HO Request
HO Request Ack
MAP PrepareHO Resp (HO Num, HO Request Ack)

Remote leg update is

INVITE (HO Num, 100rel, no SDP) IAM not done if ATGW
SDP is not changed
ACM
183 Progress (SDP-MGW)
INVITE(
INVITE (STN-SR, C-MSISDN, SDP-MGW) ATU-STI,
SDP-ATGW)
200 OK (SDP-ATGW’) 200 OK
(SDP-UE2)
ACK

SRVCC PS to CS ACK
PRACK (SDP-ATGW ’)/200 OK
Resp
(TargetToSource Release old access
container) leg in PS domain
(BYE might not
HO Command
reach UE as it may
have moved to CS)
BYE
200 OK

UE tunes to GERAN
HO detect
MAP-PAS(HO Detect)
HO Complete
MAP-Send End Signal (HO Complete)
200 OK ANM
SRVCC PS to CS
ACK
Complete Notif

SRVCC PS to CS
Complete Ack
CS Bearer

IP Bearer IP Bearer
TMSI Reallocation Cmd/Ack Location Update/
ISD/LU Ack
 Access transfer Procedures
for SRVCC(cont’d)
Access transfer with STN-SR(SRVCC)
FLOW: Configuration :
• Identification of Access-TasSccAsInternal
transfer request StnSr: 09999999988
• Identification of SccAsLocalConfig
Transferable session transferOnStnSr (‘TRUE’)
• Remote leg Update
• Releasing of Source leg
 Access transfer Procedures
for SRVCC(cont’d)
Access transfer with STN-SR(SRVCC)
UE-A SCC AS/
E-UTRAN MME SRVCC MSC I/S-CSCF UE-B
CS PS TAS
Initial Call setup with UE-B
INVITE

200 OK/ACK

IP Bearer

Handover to CS domain
Measureme
HO Required (Target Cell, SRVCC HO
nt reports indication,
SrcToTargetContainer)

INVITE (STN-SR, C-
SRVCC MSC sends the MSISDN, SDP-MGW) I-CSCF does an LIR query.
HO INVITE to the I-CSCF STN-SR is configured as PSI in
HSS against SCC AS
SRVCC PS to CS Resp
INVITE (STN-SR, SDP-
(TargetToSrc
MGW)
HO Command (TargetToSrcContainer) container)
SCC AS initiates a
reINVITE(SDP-MGW) remote leg update

200 OK(SDP-UE2)
200 OK (SDP-UE2)

ACK

Release old access leg (send

BYE to UE on PS access)
BYE
200 OK

UE tunes to GERAN/UTRAN

SRVCC MSC receives HO

complete indication from RAN

PS to CS Complete
Notif
UE Context Release Command
PS to CS Complete
UE Context Release Complete Ack

TMSI Reallocation Command/Complete

SRVCC MSC does Location

Update with HLR
CS Bearer IP Bearer
QUESTION ?
THANK YOU