Sei sulla pagina 1di 15

SRVCC Overview

Prepare
Handover
Access
transfer
GERAN ATCF &
UTRAN MSS B
SCC AS
GSM / WCDMA
Sv
MMTel
SRVCC IMS
A
handover
LTE EPC
LTE Moving UE

LTE SRVCC handover


CS coverage

IMS Telephony Voice to CS handover


– Handover triggered by LTE RAN.
Handover signalling from MME in EPC to MSC
(via the Sv reference point)
– MSC prepares handover and connects CS leg to IMS
– ATCF and SCC AS executes access transfer
SRVCC procedures
6. Media is
3b. The MSS set up a call leg to the
established
ATCF using the STN-SR number.
towards UE
And performs HO towards
Access network
BTS BSC
NodeB RNC MSS
GSM / WCDMA 4. The ATCF finds the
anchored call and
executes session
SCC AS MMTel
transfer
3a. The MSS and RAN
prepares to receive a MTAS
handover
SRVCC B
handover MME P-CSCF I-/S-
ATCF CSCF
1. The eNodeB
decides to do
SRVCC HO

HO request

S&P
Signaling
eNodeB GW ATGw
Voice media
A LTE
2. The MME handles Serving Network Home isNetwork
5. The ATGW updated
the SRVCC HO via
with new media
the Sv interface
destination for
transferred party
SRVCC in different releases
• Single Radio VCC introduced in 3GPP Rel-8
• 3GPP Rel-9 enhancements
– SRVCC for emergency calls
• 3GPP Rel-10 enhancements
– Performance Enhancements using ATCF (no UE impact)
– Support for transfer of calls in alerting and mid-call state
– Support for Video Call
• 3GPP Rel-11 enhancements
– SRVCC for Multimedia Priority Calls
– SRVCC from CS to PS
• 3GPP Rel-12 enhancements
– SRVCC for calls in pre-alerting state
Main Drivers For
Rel-10 SRVCC
• Secure speech interruption time below 300ms.

• Scalability

• Allow local breakout for roaming

• Rel-9 architecture broken (requires proprietary


hacks)
SRVCC and other media than voice
• In case the IMS session on LTE (or HSPA) includes besides voice also other
media, then during transfer those other media are handled as follows:
– If the target access is GERAN non Dual Transfer Mode (DTM), then all non
voice media are removed from the session by the SCC AS.
– If the target access is UTRAN or GERAN with DTM (and the UE supports
GERAN with DTM), then
• The UE informs the SCC AS about which non-voice media to keep on PS
access, i.e., speech media component is always removed.
• In case of IMS session that includes synchronised video media, then the
UE must remove both the voice media and the video media component
from the session on Gm, hence the video media from the video call is
discontinued after the session transfer.
SRVCC HO Interruption
LTE UTRAN EPC MSS ATCF/
ATGW
RTP Media over LTE

SRVCC triggered
PS CS resp
PS CS HO Cmd INVITE
PS CS HO Cmd

200 OK
RTP media
HO Detect HO Detect

CS Voice Media CS Voice Media


RTP media

HO Complete

CS Voice Media CS Voice Media RTP media


SRVCC Call-flow
SRVCC HO Interruption
• The 3GPP requirement for speech interruption due to
SRVCC is to be below 300ms.
• Packet Handover Interruption can be measured easily
in the network or UE based on last observed packet
over LTE until first packet over CS.
• Observed speech Interruption time (SIT) is more tricky
to measure without special tools.
• SIT is dependent on:
– The Packet Handover Interruption time
– Media buffers in the device (and network).
– Due to the buffers, the SIT may in some cases be smaller
than the Packet HO interruption.
Alerting and Mid call
• Specific procedures are required in the MSC Server and IMS
to handle mid-call and alerting calls correctly.
• If not supported, the behavior will be as follows
– If a call is in alerting state where a QCI-1 bearer has been
established, SRVCC will be triggered by MSC Server. No active
call will be found in IMS, hence, the SRVCC procedures will fail
and the alerting call will be lost.
– Only one active call will be transferred during SRVCC. Any held
calls will be released by IMS as a result of the SRVCC transfer.
– Conference calls will be transferred, but the conference control
will be lost. Any conference events by the UE after the transfer
will trigger the CS conference services and not the IMS
conference service.
Bearer release due to SRVCC

IMS APN

• As part of SRVCC, the voice bearer IMS Signaling Bearer (Default) , QCI=5 SIP (SDP)

will be released. Voice Bearer (GBR) , QCI=1 Voice (RTP)

Video Bearer (GBR) , QCI=2 Video (RTP)


• Depending on target access, other
Global Text Tel (non-GBR) , QCI=9 GTT (RTP)
bearers will be treated slightly
differently.

GBR bearers Non-GBR bearers


SRVCC to GSM without MME deactivates all MME suspends any
DTM GBR bearers. non-GBR bearers.
SRVCC to GSM DTM/ MME deactivates the UE performs RAU to re-
UTRAN no PSHO GBR bearers. establish bearers.
SRVCC to UTRAN with All non voice bearers All non voice bearers
PSHO are moved if supported are moved
SRVCC for CDMA 1x
SRVCC

A1
Um / Uu
1xRTT 1xRTT SRVCC
SRVCC
MSS
CDMA Access
A 1x CS MMTel
IWS VCCAS
1x CS MTAS
EPC ISC
Mw /
SRVCC
Mg /
S102 Mw Mx B
I-/S-
RAT MME P-CSCF
CSCF
change
S11 Gm
Mb
SRVCC S1-MME

e-Uu
SRVCC
eNodeB S1-U S&P
SRVCC GW
A
phone LTE
SGi

SRVCC
New functionality
SRVCC for CDMA 1x
Handover Procedures
3. MSS prepares resources in
4. UE tunes to target based target network and initiates
on HO information transfer towards IMS.
received. SRVCC

A1
Um / Uu
1xRTT 1xRTT SRVCC
SRVCC
MSS
CDMA Access
A 1x CS MMTel
IWS VCCAS
1x CS MTAS
EPC ISC
Mw /
SRVCC
1. Based on measurement S102 Mw
Mg /
Mx B
reports, eNB decides to
trigger HO by informing UE. I-/S-
RAT MME P-CSCF
CSCF
change
S11 Gm
Mb
SRVCC S1-MME

e-Uu
SRVCC
eNodeB S1-U S&P
SRVCC GW
A
phone LTE
SGi

2. UE initiates SRVCC procedures by sending HO


preparation request to MSS tunneled over MME, SRVCC
New functionality
including address to VCC AS.
SRVCC 1x vs SRVCC 2G/3G

SRVCC to 2G/3G SRVCC to 1x


• Transfer number to anchor • Transfer number to anchor
function dynamic. function provisioned in UE.
• UE not aware of HO until • UE initiates resources
target resources allocated. reservation in target.
• MME central role in SRVCC • MME mainly “relay” node
procedures. for UE to MSS messages.
• Speech interruption and • Uses Rel-7 VCC architecture
scalability improvements without improvements.
for Rel-10. • Needs to be “patched” to
• Rel-10 architecture handles handle SDP miss-match.
SDP miss-match.
SRVCC Summary
• IMS is introduced as service engine
• CS coverage will Initially be larger than LTE coverage
• SRVCC provide an efficient mean to provide voice
continuity when leaving LTE access.
• SRVCC according 3GPP Release 10 will reduce voice
interruption delay during the access transfer.

• Internal E2e Documentation


– SRVCC SISR
– SRVCC Method of Procedures (MoP)
– SRVCC White paper