You are on page 1of 59

VoLTE Solution

eSRVCC Function

Issue 1.0
www.huawei.com

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.


References

3GPP TS 23.216 Single Radio Voice Call Continuity (SRVCC)

3GPP TS 23.237 IP Multimedia Subsystem (IMS) Service


Continuity; Stage 2

3GPP TS 24.237 IP Multimedia Subsystem (IMS) Service


Continuity; Stage 3

GSMA IR.92 IMS Profile for Voice and SMS

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 2
Objectives
After completing this course, you will be able to understand:

Understand eSRVCC principles and objectives

Understand eSRVCC networking and deployment

Understand eSRVCC processes

Understand eSRVCC-related configuration

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 3
Contents
1. eSRVCC Principles and Networking

2. Typical eSRVCC Processes

3. eSRVCC Deployment

4. eSRVCC Configuration and Maintenance

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 4
Contents

1. eSRVCC Principles and Networking

1.1 SRVCC Necessity

1.2 SRVCC Networking and Processes

1.3 eSRVCC Principles and Networking

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 5
LTE Voice Evolution
Phase1: Phase 2: Phase 3:
LTE hotspot coverage Continuous LTE coverage Full LTE coverage

LTE LTE
LTE
LTE
UMTS
Hot
UMTS UMTS
spot

LTE hotspot coverage Full LTE coverage


Continuous LTE coverage
2G/3G full coverage (mainstream)
SRVCC (IMS)
CSFB Supporting VoHSPA, the
CS network shrinks
Applications:
Applications: Supporting IMS roaming
Smart phone supporting
Smart phone supporting CSFB Applications:
SRVCC
Data card, CPE Smart phone
Data card, CPE
Data card, CPE

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 6
SRVCC Solution Source
MME

IMS CN
SAE-GW Voice media flows

LTE 2G/3G

Key issues:
1. The LTE or IMS provides voice services for users in the LTE coverage. How can
the voice service continuity be guaranteed for users moving from the LTE hotspot
coverage to the 2G/3G coverage?
2. Voice services are real-time services. How can the service interruption duration
be minimized when users move from one network to another network?
3. How can a voice continuity solution be deployed?
4. How can voice services be guaranteed for users during inter-carrier roaming?

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 7
Contents
1. eSRVCC Principles and Networking

1.1 SRVCC Necessity

1.2 SRVCC Networking and Processes

1.3 eSRVCC Principles and Networking

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 8
SRVCC Architecture and Interfaces
Message Type Message
EMSC
Um/Uu Iu-cs/A 1 Echo Request

2 Echo Response
BS SGSN Sv 3 Version Not Supported Indication
Iu/Gb HSS
Gn/S3 S6a 25 SRVCC PS to CS Request

26 SRVCC PS to CS Response
IMS CN 27 SRVCC PS to CS Complete Notification
S1-C S11
28 SRVCC PS to CS Complete Acknowledge
Uu S1-U SGi 29 SRVCC PS to CS Cancel Notification

30 SRVCC PS to CS Cancel Acknowledge


eNB SAE-GW
31 For future Sv interface use

Interface Description Protocol


Sv The Sv interface is located between the SRVCC-IWF and the MME or SGSN. It supports inter-system handover 3GPP
from VoIP/IMS voice calls over EPS to voice calls over 2G/3G CS networks. The Sv interface is used to transmit TS29.280
information such as the STN-SR, IMSI, and C-MSISDN. The interface complies with the GTPv2 protocol.
S6a The S6a interface is located between the HSS and the MME. It is used for the HSS to transmit the STN-SR and C- 3GPP
MSISDN required by the SRVCC to the MME. Then, the MME transmits these information to the SRVCC-IWF TS29.272
through the Sv interface during handover.
eNB/UE A UE supporting SRVCC needs to show its SRVCC capability to the network, report measurement reports of other 3GPP
systems, and receive handover commands from the network. TS36.300

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 9
SRVCC Handover Process
Target
UE E-UTRAN MME MSC Server UTRAN/ SRVCC AS
GERAN
3. The MME separates the voice bearer
1.Measurement according to the QCI and initiates a
Reports handover process to the E-MSC for the
bearer.
2.Handover to UTRAN/GERAN
required
5. The target MSC and the target RAN
3.Initiates SRVCC for voice establish session resources and start
component the handover process. Subsequently,
4.Handles PS-PS HO 5.CS handover preparation the IMS SCC AS starts session transfer
for non-voice if
6.IMS Service Continuity Procedure on the core side.
needed

4. Non-voice component handover or


8.To eUTRAN
Coordinates SRVCC
7.PS HO response to MME suspension
(CS resources)
9.Handover CMD and PS HO response

10.Handover 8. The MME instructs the LTE eNodeB


execution
and UE to start handover.

Call signalling anchor


1. The SCC-AS serves as the signaling anchor point in
LTE
Media Leg1 VoIP calls. The caller/callee and the caller after
Calling Leg1 handover anchor signaling to the SCC-AS.
SRVCC AS Called Called Leg3
Access 2. Before handover, a VoIP session is established
Calling Leg2
GERAN between Leg1 and Leg3; after handover, a VoIP
UMTS Media Leg2 session is established between Leg2 and Leg3.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 10
SCC AS Functions
Ensures session continuity during the handover from
Access Transfer one access network to another access network.
Associates new access legs to the original session.

Combines or separates media flows on one or VCC


Handling of multiple multiple access legs.
media flows As required by the UE, combines or separates
media flows on one or multiple access legs.

Terminating Access Completes access network selection to deliver an


Domain Selection incoming session.
Determines that the UE receives an incoming
session.

Represents the UE to provide the SIP UA function in


ICS User Agent the ICS architecture.
Associates service control signaling with bearer
ICS
descriptions (SDP).

CS Access Adapts the service control signaling transparently


Adaptation transmitted between the UE and the SCC AS, and
interworks with other IMS NEs.

Inter-UE Transfer Transfers sessions between UEs.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 11
SRVCC Handover Process (Continuation)
(1-3): The source E-UTRAN determines to initiate SRVCC handover according to the
measurement reports of the UE. The source E-UTRAN sends a handover request to the
MME and indicates SRVCC handover in the handover request message.
(4-5): The MME separates the voice bearer (QCI=1) according to the SRVCC indication
in a message. At the same time, the MME selects an SRVCC IWF according to the
target ID in the handover request message and initiates a PS-CS handover request
carrying mandatory SRVCC handover information (including the STN-SR, MSISDN, and
MM context) to the SRVCC IWF. (The MM context contains the CS key exported by the
MME.)
(6-7): Upon receiving a PS-CS handover request message, the SRVCC IWF selects a
target MSC according to the target ID in the message and sends a Prepare Handover
Request message to the target MSC. The handover process is similar to handover
between traditional MSC offices. The target MSC sends an HO Request message to the
target RNS or BSS to assign air interface resources in the CS domain, and the
handover process is similar to handover between traditional MSC offices.
(8-9): After the assignment of air interface resources is complete, the target RNS or
BSS returns a response message to the target MSC. Then, the target MSC returns a
Prepare Handover Response message to the SRVCC IWF. Upon receiving the Prepare
Handover Response message, the SRVCC IWF establishes a circuit connection (ISUP
IAM, ACM) with the target MSC.
(10-12): The SRVCC IWF initiates an initiate session transfer (IST) process to the IMS
Core. The called number is the STN-SR, the calling number is the MSISDN, and the
signaling can be ISUP signaling. (ISUP signaling must pass through the MGCF.) The
SCC AS completes session handover and updates the media information on the remote
UE.
(13-15): The SRVCC IWF forwards the PS-CS handover response message to the
source MME, indicating that the target air interface resources are complete. Upon
receiving the PS-CS handover response message, the MME or E-UTRAN sends a
Handover Command message to the UE, instructing the UE to start handover.
(16-17): The UE switches to the UTRAN or GERAN. The target RNS or BSS completes
handover detection report.
(19-22): The target RNS or BSS sends an HO Complete message to the target MSC,
indicating that the UE has completed handover. The target MSC sends an SES (HO
completed) and an ISUP ANM message to the SRVCC IWF. Upon receiving the
messages, the SRVCC IWF sends an HO Complete message to the source MME.
(23): The SRVCC IWF initiates implicit location update to the HLR, enabling the HLR to
serve as the controlling MSC during handover in the traditional CS domain.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 12
SRVCC Handover Interruption Duration
To ensure user experience, the interruption duration of the
SRVCC handover from the EUTRAN to the UTRAN should 1. Tb3 is the hard handover duration of the UE.
Generally, Tb3 is less than 300 ms. In TS 36.133,
be less than or equal to 300 ms. Tb3 is generally defined as 100 ms.
2. Ta1+Ta2+Ta3+Ta4 represents the transmission
IMS Bearer before HO
duration required for remote SDP update and the
processing delays of CN nodes.
b3.Tune to CS 3. Assume that the inter-NE transmission delay is 50 ms
b2.HO CMD MME b1.HO CMD MS a1.Invite SCC a2.Offer and the processing delay of each NE is 20 ms.
UE Remote 4. Based on a preliminary estimation, Ta1+Ta2+Ta3+Ta4
/eNodB C a4.200 OK AS a3.Answer
= 940 ms.
k
Uplin Uplin
k
CS Bearer after HO IMS Bearer after HO
Dow MGW
nlink n link
Dow

Optimization scheme:
The reason for the interruption duration caused
by Session Transfer(Remote Update) is that the
Item Interruption Duration SCC AS only implements signaling anchoring,
without media anchoring.
Interruption duration of Td = MAX(Ta1+Ta2+Ta3+Ta4-Tb1-Tb2, Tb3) -> In 3GPP Release 10 (TR23856), the following
downlink voice media flows Td = MAX(Ta1+Ta2+Ta3+Ta4, Tb3) alternative schemes are provided:
Interruption duration of uplink Tu = MAX(Ta1+Ta2+Ta3+Ta4-Tb1-Tb2, Tb3) -> Delay prediction scheme (based on the MSC
voice media flows Tu = MAX(Ta1+Ta2+Ta3+Ta4, Tb3) or SCC AS)
Serial handover scheme
Media anchoring to the SGW
Assumption: Tb1 and Tb2 are very small and can be ignored, ...
because b1 and b2 occur in the visited network of the UE. The final scheme is an enhanced scheme,
namely anchoring to the ATCF or ATGW in the
visited location.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 13
Contents
1. eSRVCC Principles and Networking

1.1 SRVCC Necessity

1.2 SRVCC Networking and Processes

1.3 eSRVCC Principles and Networking

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 14
Enhanced SRVCC
EMSC
Um/Uu Iu-cs/A Objective: In all scenarios (even in
roaming or carrier interworking
BS scenarios), ensure that the handover

The major optimization point is the IMS


SGSN Sv
Iu/Gb HSS interruption duration is less than 300 ms.
Gn/S3 S6a
Policy: Optimize the remote session

Session Transfer process.


IMS CN update process (IMS Session Transfer).
S1-C S11
Uu S1-U
Method: Implement signaling and media
SGi
anchoring on the ATCF or ATGW to
eNB SAE-GW avoid the IMS Session Transfer process.

ATCF: Access Transfer Control Function


ATGW: Access Transfer MGW

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 15
Differences Between SRVCC Signaling before HO
Bearer before HO
Signaling after HO
and eSRVCC Bearer after HO

SRVCC (3GPP R8) CS

IMS session handover (remote


HO Remote
SDP update) causes long IMS end
interruption duration.

EPC SBC

Local leg: < 300 ms Uncertain, maybe > 1s

eSRVCC (3GPP R10) CS

Avoid remote update based on


ATCF/ATGW anchoring, reducing HO IMS Remote
the interruption duration. end
ATCF
EPC SBC
ATGW

Re-establish as SRVCC Keep same with before HO

HISILICON
Copyright SEMICONDUCTOR
2011 Huawei Technologies Co., Ltd. All rights reserved. Page 16
Differences Between SRVCC and
eSRVCC (Continuation)
Entity eSRVCC Requirement
UE Same as SRVCC.
PS(MME/S-PGW) Same as SRVCC.

e-Node B Same as SRVCC.


SRVCC IWF(MSC Server) Same as SRVCC.

SCC AS Receives the STN-SR assigned by the ATCF and writes the STN-SR in the HSS.
Completes ATU-STI assignment and transmission, and C-MSISDN transmission.
After receiving a new session from the ATCF, associates the new session with the original session,
and controls the release of the original session.

ATCF/ATGW (new functional entity in Completes STN-SR assignment and transmission. Receives information such as the ATU-STI and
the visited network) C-MSISDN from the SCC AS.
Implements signaling and media anchoring according to the policy.
After receiving a session from the SRVCC IWF, associates the session with the original session,
and modifies the media to avoid remote SDP update.
After completing session association, initiates session handover to the SCC AS.

Proxy call session control function (P- Completes the routing and configuration to the ATCF. (The P-CSCF, ATCF, and ATGW are
CSCF) integrated on the SBC.)

System architecture evolution - home Receives the STN-SR modified by the SCC AS, and sends the modified STN-SR to the MME.
subscriber server (SAE-HSS)

In Huawei solution, the P-CSCF, ATCF, and ATGW are integrated on the SBC.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 17
Contents
1. eSRVCC Principles and Networking

2. Typical eSRVCC Processes

3. eSRVCC Deployment

4. eSRVCC Configuration and Maintenance

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 18
Key Parameters in the Handover Process
Handover
Subscription Registration Process Handover Process
Type
1. The MME sends a PS to CS Request message (carrying the
STN-SR and C-MSISDN) to the MSC.
2. The SRVCC MSC initiates a Session Transfer process and
STN-SR and C- sends an IAM or INVITE message to the IMS. (In the
MSISDN The HSS sends the STN-SR and C- message, the calling number is the C-MSISDN, and the
SRVCC subscription is MSISDN to the MME through the Update called number is the STN-SR, serving as a session transfer
implemented on Location Ack message. number for SRVCC.)
the SAE-HSS. 3. Upon receiving an INVITE message, the SCC AS checks that
the Request-URI is the STN-SR (configured on the SCC AS),
indicating that the call is a handover call. Then, the SCC AS
performs the session transfer process.
1. The SBC, functioning as the ATCF, 1. The MME sends a PS to CS Request message (carrying the
assigns an STN-SR. The STN-SR, STN-SR and C-MSISDN) to the MSC.
contained in g.3gpp.atcf, is used to 2. The SRVCC MSC initiates a Session Transfer process. The
identify the SBC. (The STN-SR is an MSC sends an INVITE message to the SBC according to the
E.164 number statically configured STN-SR. In the message, the Request-URI is the STN-SR,
on the SBC.) and the P-Asserted-Identity header field contains the C-
2. After completing third-party MSISDN.
registration, the TAS obtains the C- 3. Upon receiving the INVITE message, the SBC checks that
STN-SR and C- MSISDN and STN-SR of the user the Request-URI is the STN-SR, indicating that the call is a
MSISDN from the HSS and sends a Message handover call. Then, the SBC performs the session transfer
eSRVCC subscription is message carrying the ATU-STI (a process.
implemented on URI configured by the TAS used for 4. The SBC sends an INVITE message to the TAS according to
the SAE-HSS. ATCF addressing) and C-MSISDN to the ATU-STI.
the SBC or ATCF. 5. Upon receiving the INVITE message, the TAS detects that
3. Upon receiving a response for the the Route header field contains the orig and atu-sti
Message message, the TAS writes parameters, and therefore it determines that the INVITE
the STN-SR received from the ATCF message is sent by the ATCF and used to identify session
or SBC in the HSS. handover. When the SDP remains unchanged, the TAS
4. After detecting that the STN-SR is modifies only the access domain of the current session,
changed, the convergent HSS needs indicating that the current session has accessed the CS
to send the STN-SR to the MME. domain and facilitating subsequent domain selection.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 19
Registration Process
The registration request message passes
through the SBC.
P1: The SBC determines whether to anchor
a session based on carriers' policies and
configuration. In the registration process,
the SBC assigns an STN-SR to set itself in
the signaling path and transmits the STN-
SR through the Register message.
P2/P5/P6/P7: The STN-SR is a routable
number used to identify the ATCF. The
STN-SR is assigned by the ATCF, and its
transmission path is ATCF -> CSCF -> SCC
AS -> HSS -> MME. During SRVCC
handover, the MME sends the STN-SR to
the SRVCC IWF (MSC) through the Sv
interface. Then, the SRVCC IWF (MSC)
can anchor the handover call to the SBC.
P3/P4: The ATU-STI is assigned by the
SCC AS and returned to the ATCF. After
handover is complete, the ATCF can use
the ATU-STI to locate the correct SCC AS.
P3/P4: The C-MSISDN is a subscription
attribute. The ATCF uses the C-MSISDN to
associate the session before handover with
the session after handover.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 20
Originating Process

The INVITE message passes through the ATCF.


P1: The ATCF determines to anchor the session on the media plane and assigns ATGW resources for the session to
establish a media anchoring point. In addition, the session is bound with the ATU-STI and C-MSISDN.
P2: Upon receiving a response message, the TAS records the information that the session has been anchored by the SCC
AS, if the user has mobility and has subscribed to the STN-SR and C-MSISDN attributes.
P3: The SBC implements media proxy. The SDP in the returned 183 message is replaced. The subsequent process is the
same with that of common calls.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 21
Terminating Process

The INVITE message passes through the ATCF.


P1: Upon receiving a request message, the TAS records the information that the session has been anchored by the
SCC AS, if the user has mobility and has subscribed to the STN-SR and C-MSISDN attributes.
P2: The ATCF determines to anchor the session on the media plane and assigns ATGW resources for the session
to establish a media anchoring point. In addition, the session is bound with the ATU-STI and C-MSISDN.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 22
Handover Process Active Session

1. An Active call is established between UE A and UE B. Media is anchored to the SBC.

2. The UE interworks with the


eNodeB/BSC, MME/SGSN,
and MSC based on TS23.216
to initiate SRVCC handover.

P1: Upon receiving a handover request (carrying information elements such as the IMSI, Target ID, STN-SR, and C-MSISDN)
from the MME, the MSC prepares handover resources on the CS side and sends an INVITE message to the SBC according to the
STN-SR. The Request-URI is the STN-SR, and the P-Asserted-Identity header field contains the C-MSISDN.
P2: Upon receiving the INVITE message, the SBC detects that the Request-URI is the STN-SR and therefore determines that
session transfer is performed during handover. Then, the SBC obtains the C-MSISDN from the INVITE message and determines
the session to be handed over.
P3: Upon receiving an ACK message from the MSC, the SBC initiates session transfer to the TAS or SCC AS based on the ATU-
STI associated with the session to be handed over.
P4: Upon receiving the INVITE message, the TAS detects that the Route header field contains the orig and atu-sti parameters,
and therefore it determines that the INVITE message is sent by the ATCF and used to identify session handover. The TAS only
modifies the access domain of the current session, indicating that the current session has accessed the CS domain and facilitating
subsequent domain selection. The TAS does not update the remote SDP.
P5: The TAS starts the release process for the original access leg.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 23
Handover Process Alerting Session

1. An Alerting call is established between UE A and UE B.

2. The UE interworks with the


eNodeB/BSC, MME/SGSN,
and MSC based on TS23.216
to initiate SRVCC handover.

Note: In VoLTE 1.0, handover of alerting sessions is not supported, and alerting sessions are released.
In VoLTE 1.1, handover of alerting sessions is supported.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 24
Handover Process Active
and Alerting Sessions
V-PLMN H-PLMN

UE MSC SBC CSCF TAS Remote UE B Remote UE C

1. An Active call is established between UE A and UE B, and media is anchored to the SBC. A Waiting Alerting call is established between UE A and UE C.

Media Path of PS bearer Media Path of PS bearer

2. The UE interworks with the


eNodeB/BSC, MME/SGSN, and
MSC based on TS23.216 to
initiate SRVCC handover.
P1
3. SIP INVITE
(STN-SR, C-MSISDN)
P2
4. SIP 200 (OK)
5. SIP ACK

New Media Path of New Media Path of


Media Path of PS bearer
CS bearer PS bearer
P3
6. SIP INVITE
(ATU-STI, C-MSISDN)
7. SIP INVITE
(ATU-STI, C-MSISDN)
P4
8. SIP 200 (OK)
9. SIP 200 (OK)

10. SIP ACK 11. SIP ACK

P5: Release the source call leg and remote leg between UE A and UE C.

13a. 487 12a. 487 12b. Cancel


14a. 487

15a. SIP 200 OK 13b. SIP 200 OK


16a. SIP 200 OK 17a. SIP 200 OK
P6: Release the source call leg between UE A and UE B (timeout).

19. SIP BYE 18. SIP BYE


20. SIP BYE

21. SIP 200 OK


22. SIP 200 OK 23. SIP 200 OK

Note: Active sessions are handed over to the CS domain. In VoLTE 1.0, handover of alerting sessions is not
supported, and alerting sessions are released. In VoLTE 1.1, handover of alerting sessions is supported.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 25
Handover Process Held
and Alerting Sessions
V-PLMN H-PLMN

UE MSC SBC CSCF TAS Remote UE B Remote UE C

1. A Held call is established between UE A and UE B, and an Alerting call is established between UE A and UE C.

Media Path of PS bearer Media Path of PS bearer

2. The UE interworks with the


eNodeB/BSC, MME/SGSN, and
MSC based on TS23.216 to
initiate SRVCC handover.
P1
3. SIP INVITE
(STN-SR, C-MSISDN)
P2
4. SIP INVITE
(ATU-STI, C-MSISDN) 5. SIP INVITE
(ATU-STI, C-MSISDN)
P3

6. 480
7. 480
8. 480
P4
9. Release P5: Release the source call leg and remote leg between UE A and UE C.

11a.487 10a. 487 10b. Cancel


12a. 487

13a. SIP 200 OK 11b. SIP 200 OK


14a. SIP 200 OK 15a. SIP 200 OK

P6: Release the source call leg and remote leg between UE A and UE B.

10c. SIP BYE


11c. SIP BYE 10d. SIP BYE
12c. SIP BYE

13c. SIP 200 OK 11d. SIP 200 OK


14c. SIP 200 OK
15c. SIP 200 OK

Note: In VoLTE 1.0, handover of held and alerting sessions is not supported, and the two types of
sessions are released. In VoLTE 1.1, handover of held and alerting sessions is supported.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 26
Handover Process Handover Exception 1

12. Process abnormal


release during inter-
MSC handover based
on TS23.009.

Description:
1. In this scenario, the source eNodeB initiates handover cancel before the SRVCC MSC initiates session transfer. The
source eNodeB can initiate handover cancel after delivering a handover required or relocation required. The cancel cause
is not specified in 3GPP TS36.413. (Generally, the source eNodeB can initiate handover cancel due to internal resource
causes when the signal strength becomes stronger.)
2. When the source eNodeB initiates handover cancel, the source MME or SGSN sends an SRVCC PS to CS cancel
notification to the SRVCC MSC, as specified in 3GPP TS29.280. The SRVCC MSC must comply with the inter-MSC
handover process specified in 3GPP TS23.009. To be specific, the MSC must release the MAP signaling on the handover
destination side and the inter-MSC call control signaling.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 27
Handover Process Handover Exception 2
1. The UE interworks with the eNodeB/BSC, MME/SGSN, and MSC based on TS23.216 to initiate SRVCC handover.

Description:
1. In this scenario, a handover command has been delivered to the UE, and the UE fails to access the CS domain. (The
failure cause may be that the UTRAN/GERAN radio resources become poor. For example, the user enters a tunnel or
elevator.) At this moment, session transfer has been performed.
2. The UE attempts to return the session to the E-UTRAN, and it re-establishes an air interface channel to the eNodeB. After
channel re-establishment is successful, the eNodeB detects that a handover request is not processed. In this case, the
eNodeB needs to initiate handover cancel. Then, the source MME or SGSN sends an SRVCC PS to CS cancel notification
to the SRVCC MSC, as specified in 3GPP TS29.280. The SRVCC MSC must comply with the inter-MSC handover process
specified in 3GPP TS23.009. To be specific, the MSC must release the MAP signaling on the handover destination side and
the inter-MSC call control signaling. In addition, the MSC needs to carry an identifier indicating that session transfer has
been initiated in an SRVCC PS to CS Cancel Acknowledge message. The MME forwards the SRVCC PS to CS Cancel
Acknowledge message to the UE, and the UE re-establishes a session.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 28
Service Processing After Handover
SCC AS
IMS Core

Service logic LU HSS/HLR SRVCC IWF working in non-ICS mode


MGCF
ISD
All service operations are terminated by the
SRVCC IWF.
LTE/SAE SRVCC IWF CS
MME MSC

Service logic
SCC AS/TAS
SRVCC IWF working in ICS mode
IMS Core

Service logics are processed by the IMS. The HSS/HLR


Invite/Re-Invite
SRVCC IWF, similar to the mAGCF, completes
CS and SIP signaling conversion only.
LTE/SAE SRVCC IWF CS
MME MSC

To support handover of sessions of multiple types (for example, active and held
sessions), the SRVCC IWF must work in ICS mode.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 29
Charging and CDRs
Principle: Prevent the CS and IMS to simultaneously implement charging.
Therefore, charging is implemented in the IMS domain.

Charging, consisting of online charging and offline charging, is implemented in


the IMS domain.

During handover, the SCC AS does not add special identifiers in CDRs. It
charges handover calls as basic calls and does not generate event CDRs for
handover.

The MSC does not generate CDRs for handover calls. (This function is
supported in CS9.0 and IMS8.2.)

If gateways are configured between the MSC and the target MSC or IMS Core,
the MSC needs to generate gateway CDRs.

If the MSC does not work in ICS mode after handover is complete, the MSC
needs to complete subsequent service processing. If the user originates a new
call, the MSC needs to generate CDRs.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 30
Handover Performance Analysis
Interruption Duration

T1a+T2a+T3a is the message transmission duration, which is about 50 ms.


T1b+T2b+T3b is the SDP media negotiation duration, which is about 150 ms.
T4 is the hard handover duration, which is about 100 ms.
Session interruption occurs at T4 or T2b. To be specific, interruption occurs when the UE starts
handover or after the SBC modifies media. The handover interruption duration can be
calculated using the following formula:
Max(T1b+T2b+T3b-T1a-T2a-T3a, T4)
The handover interruption duration greatly depends on T4, namely the hard handover duration
of the UE. The handover voice interruption duration is less than 150 ms.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 31
Contents
1. eSRVCC Principles and Networking

2. Typical eSRVCC Processes

3. eSRVCC Deployment

4. eSRVCC Configuration and Maintenance

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 32
eSRVCC Deployment Typical Networking
SMSC

Single SDB
Key points:
O&M Service layer
1. Newly build IMS core
CTAS & service layer (TAS)
(MMTel AS/SCC AS/IP-SM-GW) Gov.
IMS- ATS9900 2. Overlaid EMSC to
EMS
HSS/ENUM/DNS/ reduce impact on CS
iManager
IMS-HSS9820 IMS Core domain if required
M2000 Legacy
Existing BSS/OSS

MGCF/CCTF network
3. Overlaid SBC &
UGC3200
SAE-HSS I/E/S- PCRF on top of EPC
2G/3G MRFP CSCF/MRFC to support required
SAE-HSS9820
Provisioning HLR MRP6600 IM-MGW
CSC3300 function
GW UMG8900
SPG2800

CS Access PS Access
CCF
EMSC
iCG9815 SBC NGN
(SRVCC IWF/CSFB Proxy/
SCP IM-SSF/Anchor Server) PCRF (P-CSCF/A-SBC/ATCF/
MSoftX3000 ATGW/IBCF/IBGW/IWF)
SE2600

MGW
2G/3G MSC UMG8900 MME S/P-GW
New Deployed
LTE LTE
2G/3G 2G/3G
Existing NE
LTE data-card
Terminal LTE CPE + soft client LTE Handset

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 33
eSRVCC Deployment Typical NEs
Layer Logical nodes name Product name Physical nodes
I/E/S-CSCF/MRFC/BGCF CSC3300
SRVCC IWF/CSFB Proxy/IM-
MSOFTX3000
Control Layer SSF/mAGCF/Anchor AS
MGCF/CCTF UGC3200
DNS/ENUM ENS
MMTel AS/SCC AS/IP-SM-GW ATS9900 ATCA
Service Layer
CCF iCG9815
IMS-HSS IMS-HSS9820
Data Layer
SAE-HSS SAE-HSS9820
Provisioning layer SPG (Provisioning GW) SPG2800
MRFP MRP6600
Media Layer
IM-MGW/IGW/MGW UMG8900 UMG
A-SBC&I-SBC
Border Control
(I-BCF/P-CSCF SE2600 PGP
Layer /ATCF/ATGW/TrGW)

OMS Layer EMS M2000 ATCA

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 34
eSRVCC Deployment
Networking Descriptions
Networking Type Deployment Description
An EMSC is deployed as the SRVCC IWF in centralized
Centralized EMSC deployment
deployment mode, avoiding reconstruction and upgrade of the
(preferred)
live network.
EMSC
The MSC on the CS network is upgraded to support
deployment
eSRVCC/SRVCC or CSFB.
MSC upgrade
If the MSC POOL networking is adopted, one or two MSCs in
the MSC POOL need to be upgraded.
IMS NEs are configured in redundancy mode. For details about
IMS Core
the redundancy configuration, see the IMS Core Redundancy.
Redundancy
A pair of EMSCs are deployed to support redundancy. For
EMSC
details, see the EMSC Redundancy.

Note:
Difference between SRVCC and eSRVCC: The physical NEs are the same. Among the
logical NEs, the SBC does not implement media anchoring. To be specific, the SBC
does not need to enable the ATCF, ATGW, or P-CSCF.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 35
Contents
1. eSRVCC Principles and Networking

2. Typical eSRVCC Processes

3. eSRVCC Deployment

4. eSRVCC Configuration and Maintenance

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 36
Contents
4. eSRVCC Configuration and Maintenance

4.1 eSRVCC License

4.2 eSRVCC Configuration (CS, IMS/TAS, PS, eNodeB, and SBC)

4.3 eSRVCC Performance Measurement

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 37
eSRVCC License

License License Control Mode Version NE Effective Range


SRVCC/eSRVCC license
Function control item PS9.2 MME SRVCC & eSRVCC
control on the MME
eSRVCC (SRVCC-IWF) (per k users)
SRVCC/eSRVCC license Resource control item: Controls the number
CS9.2 MSC SRVCC & eSRVCC
control on the MSC of users that can be simultaneously
implemented with handover.

Note: During handover, the number of users increases by 1. After a handover call is released,
the number of users decreases by 1.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 38
Contents
4. eSRVCC Configuration and Maintenance

4.1 eSRVCC License

4.2 eSRVCC Configuration (HSS, IMS/TAS, SBC, MSC, and EPC)

4.3 eSRVCC Performance Measurement

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 39
eSRVCC Typical Networking and
Configuration Process
Start

Configure MME data

Configure MSC data

Configure SBC data

Configure TAS data

Configure HSS data

End

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 40
HSS Configuration

Category Parameter Example Value Remarks


International mobile subscriber
IMSI 460000009123456
identity (IMSI) of a user.
MOD STN-SR Mobile station international ISDN
MSISDN 8613900001234
number (MSISDN) of a user.
STNSR 8613988889999 None.
PISI 8613955556666 ATU-STI number.
ADD HTPLPSI SCC AS address mapping an ATU-
PUSI sip:sccas1@home1.com
STI number.
PISI 8613988889999 STN-SR number.
ADD HTPLPSI sip:termsdgfdfwe@actf.visited2. ATCF address mapping an STN-SR
PUSI
net number.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 41
IMS/ATS9900 Configuration

Category Parameter Example Value Remarks

Session transfer number for Default SRVCC session transfer


8613988889999
MOD SRVCC number (STN-SR) of an AS.
SRVCCCFG
Session transfer identifier sip:sccas1@home1.com PSI address of an SCC AS.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 42
SBC Configuration
Category Parameter Example Value Remarks
ATCF signaling transmission interface.
interface
slot-id/cpu-id/vcpu-id 3/0/0 It must be configured on the
Signal-if
distribution unit.
IP address of an ATCF signaling
ip-address 202.10.0.20 transmission interface. It must be a
ip address signaling IP address on the core side.
Address mask of an ATCF signaling
mask 255.255.255.0
transmission interface.
Same as the ATCF signaling
sbc atcf ip ipv4-address 202.10.0.20
transmission interface address.
Port mapping the ATCF signaling
port 5060
transmission interface address.
sbc atcf ip domain atcf.visited.net ATCF domain name.
Calling number after eSRVCC
sbc atcf ip stn-sr 8.61399E+12
handover.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 43
MSC Configuration

Category Parameter Example Value Remarks


Used to inform the BSC of the information that
ADD GTPPE Default SAI 4600100010002
the handover source side is the E-UTRAN.
IP address of the eMSC used to communicate
Local IP address 49.49.49.205
ADD GTPPATH with the MME.
Remote IP address 147.2.33.1 IP address of the MME.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 44
EPC Configuration
Category Parameter Example Value Remarks
Type of an MME board address used
IP address type IPV4
to send IP packets.
ADD MME board address used to send IP
BINDGTPCIP packets.
IPv4 address 147.2.33.1
This parameter is valid only when IP
address type is set to IPV4.
Destination IP
49.49.49.205 IPv4 address of the eMSC.
Address
IP Mask 255.255.255.255 Address mask of the eMSC.
ADD IPRT
Next-hop gateway address through
Gateway 136.5.4.253 which IP packets pass before the
packets are routed to the eMSC.
LAC5101.LAC.EPC.MNC001.MC
ADD Host Name Host name of the eMSC.
C308.3GPPNETWORK.ORG
IPV4DNSH
IP Address 49.49.49.205 IPv4 address of the eMSC.
LAC5101.LAC.EPC.MNC001.MC
ADD DNSN FQDN Host name of the eMSC.
C308.3GPPNETWORK.ORG

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 45
eSRVCC Configuration Process MME

MME data configuration:


Run ADD BINDGTPCIP to configure the binding relationship between the
board address and the GTPC IP address.
Run ADD IPRT to configure a static IP route for IP packets from the EPU
board to the destination NE, such as the S-GW or ADMF.
Run ADD IPV4DNSH to configure the mapping relationship between the
eMSC host name and IP address.
Run ADD DNSN to configure the location area (LA) covered by the eMSC.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 46
eSRVCC Configuration Process eMSC

eMSC data configuration:


Configure data for interconnection between the eMSC and MME.
Run ADD GTPPE to configure a GTP peer entity.
Run ADD GTPPATH to configure a GTP path.
After a GTP path is configured, run DSP GTPPATH to check the GTP path status. If
GTP path status in the command output is Normal, the link configuration is successful.
Configure data for interconnection between the eMSC and SCC AS.
Run ADD OFC to configure an office direction.
Run ADD SRT to configure a subroute.
Run ADD RT to configure a route.
Run ADD RTANA to configure route analysis data.
Run ADD SIPTG to configure a SIP trunk group.
Run ADD OFCMGW to configure an MGW for the SIP office direction.
Run ADD CNACLD to configure STN-SR number analysis data.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 47
eSRVCC Configuration Process SBC
Run system-view to enter the system view.
Configure an ATCF transmission interface.
Run the following command to enter the signaling interface view.
interface Signal-if slot-id/cpu-id/vcpu-id
Run the following command to configure an ATCF transmission interface address.
ip address ip-address { mask | mask-length } [ sub ]
Note: The address must be a core-side signaling address of the distribution unit. It is recommended that the address be in the same
network segment with other core-side signaling addresses on the distribution unit.
Run the following command to exit the signaling interface view.
quit
Configure ATCF information.
Run the following command to enter the function entity view.
sbc function-entity function-entity-index
Run the following command to configure an ATCF signaling address and port number.
sbc atcf { [ vpn-instance vpn-instance-index ] ip ipv4-address port | ip ipv6-address port }
Run the following command to configure an ATCF domain name.
sbc atcf domain domain
Run the following command to configure an ATCF number.
sbc atcf stn-sr stn-sr
(Optional): Run the following command to enable the ATCF to support the g.3gpp.srvcc parameter processing.
sbc atcf compatible g.3gpp.srvcc
Run the following command to exit the function entity view.
quit
Enable the ATCF function.
Run the following command to enter the proxy mapping group view.
sbc mapgroup proxy index
Run the following command to enable the ATCF function.
sbc atcf enable
Run the following command to return to the user view.
return
Run the following command to save the current configuration information.
save

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 48
eSRVCC Configuration Process TAS

TAS data configuration:


Run MOD SRVCCCFG to enable the TAS to support the eSRVCC function.
Run MOD SPCFG to enable the TAS to download the STN-SR, C-MSISDN, and
UE-SRVCC-Capability information from the HSS.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 49
eSRVCC Configuration Process HSS

HSS data configuration:


Run MOD STN-SR to configure the STN-SR of the user.
Run ADD HTPLPSI to configure a PSI for the SCC AS.
Run ADD HTPLPSI to configure a PSI for the ATCF.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 50
Contents
4. eSRVCC Configuration and Maintenance

4.1 eSRVCC License

4.2 eSRVCC Configuration (CS, IMS/TAS, PS, eNodeB, and SBC)

4.3 eSRVCC Performance Measurement

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 51
IMS/ATS9900 Performance Measurement
Measurement Measurement
Measurement Entity Function Description
Unit Object
ATS SIP All This measurement unit consists of seven SRVCC process
Message measurement entities: measurement. This
Measurement Number of Single Radio Voice Call measurement unit is used
Continuity to implement performance
Number of Enhanced Single Radio measurement and O&M.
Voice Call Continuity
Number of Total Session Transfer
Number of Successful Single Radio
Voice Call Continuity
Number of Successful Enhanced Single
Radio Voice Call Continuity
Number of Total Successful Session
Transfer
Number of Total Switch Back From
Session Transfer

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 52
MSC Performance Measurement
Measurement Measurement Function
Measurement Entity
Unit Object Description
The handover target side mapping this measurement is a 2G network. This measurement
unit consists of the following measurement entities:
This measurement
Number of Requested 2G Intra-MSC eSRVCC Handovers
unit is aimed at
Number of Successful Radio Access Times During 2G Intra-MSC eSRVCC Handovers
collecting statistics
Number of Requested 2G Inter-MSC eSRVCC Handovers
on handover from
Number of Successful Radio Access Times During 2G Inter-MSC eSRVCC Handovers
the LTE network to
2G eSRVCC Number of Cancelled 2G eSRVCC Services Before SRVCC IWF Sends SRVCC PS to
GTP Peer Entity CS Response Messages
the 2G access side
Service
Name of the CS network.
Measurement Number of Cancelled 2G eSRVCC Services After SRVCC IWF Sends SRVCC PS to
The statistics
CS Response Messages
provide references
Number of 2G eSRVCC Service Failures Due to Radio Resource Allocate Failures of
to network
the BSC
maintenance and
Number of 2G eSRVCC Service Failures Due to Inter MSC Bearer Operation Failures
management.
Number of 2G eSRVCC Service Failures Due to IST Failures
Number of 2G eSRVCC Services with Successful Radio Handovers and ISTs
The handover target side mapping this measurement is a 3G network.
This measurement unit consists of the following measurement entities:
This measurement
Number of Requested 3G Intra-MSC eSRVCC Handovers
unit is aimed at
Number of Successful Radio Access Times During 3G Intra-MSC eSRVCC Handovers
collecting statistics
Number of Requested 3G Inter-MSC eSRVCC Handovers
on handover from
Number of Successful Radio Access Times During 3G Inter-MSC eSRVCC Handovers
the LTE network to
3G eSRVCC Number of Cancelled 3G eSRVCC Services Before SRVCC IWF Sends SRVCC PS to
GTP Peer Entity CS Response Messages
the 3G access side
Service
Name of the CS network.
Measurement Number of Cancelled 3G eSRVCC Services After SRVCC IWF Sends SRVCC PS to
The statistics
CS Response Messages
provide references
Number of 3G eSRVCC Service Failures Due to Radio Resource Allocate Failure of
to network
the RNC
maintenance and
Number of 3G eSRVCC Service Failures Due to Inter MSC Bearer Operation Failures
management.
Number of 3G eSRVCC Service Failures Due to IST Failures
Number of 3G eSRVCC Services with Successful Radio Handovers and ISTs

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 53
EPC/MME Performance Measurement
Measurement Measurement
Measurement Entity Function Description
Unit Object
This measurement unit is aimed at SRVCC process
collecting statistics on SRVCC process measurement. This
S1 mode times of the MME. It consists of the measurement unit is
Whole System
SRVCC following measurement entities: used to implement
S1 mode SRVCC request times performance
S1 mode SRVCC success times measurement and O&M.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 54
SBC Performance Measurement

In IMS9.0, only SBC performance test is supported, and SBC


performance measurement is not developed.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 55
Questions
What are the eSRVCC principles and objectives?

How about the eSRVCC networking and deployment?

What are the eSRVCC processes?

How about eSRVCC configurations?

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 56
Summary
This document describes the eSRVCC and SRVCC solutions.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 57
Acronyms and Abbreviations
SRVCC: Single Radio Voice Call Continuity

eSRVCC: enhanced SRVCC

STN-SR: Session Transfer Number for SR-VCC

ATU-STI: Access Transfer Update - Session Transfer Identifier

QCI: QoS Class Identifier

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 58
Thank You!
www.huawei.com