3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; V12.0.

0 (2013-12) Single Radio Voice Call Continuity SRVCC!; Technical Specification Stage " Release #"!

3GPP TS 23.216

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Or ani!ational Partners and shall not be implemented. This "pecification is provided for future development wor# within 3GPP only. The Or ani!ational Partners accept no liability for any use of this "pecification. "pecifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Or ani!ational Partners$ Publications Offices.

Release #"

"

3GPP TS "3$"#% V#"$&$& "&#3'#"!

%eywords
LTE, UMTS, GSM, Circuit mode, IP, mu timedi!, IMS, "oice

3GPP Postal address 3GPP support office address

6#0 $oute de% Lucio e% - So&'i! ()ti&o i% V! *o))e - +$(,CE Te .- .33 / 02 0/ /2 00 +!1- .33 / 03 6# /2 16 &nt&&.or3

Copyright Notification 'o part may be reproduced e(cept as authori!ed by written permission. The copyri ht and the fore oin restriction e(tend to reproduction in all media.
) *+,3- 3GPP Or ani!ational Partners (./&0- .T&"- 11".- 2T"&- TT.- TT1). .ll ri hts reserved. 3MT"4 is a Trade Mar# of 2T"& re istered for the benefit of its members 3GPP4 is a Trade Mar# of 2T"& re istered for the benefit of its Members and of the 3GPP Or ani!ational Partners 5T24 is a Trade Mar# of 2T"& re istered for the benefit of its Members and of the 3GPP Or ani!ational Partners G"M6 and the G"M lo o are re istered and owned by the G"M .ssociation

3GPP

Release #"

3GPP TS "3$"#% V#"$&$& "&#3'#"!

Co)te)t%
1ontents....................................................................................................................................................3 7oreword...................................................................................................................................................8 , "cope......................................................................................................................................................9 * /eferences..............................................................................................................................................9 3 :efinitions and abbreviations.................................................................................................................;
3., :efinitions..............................................................................................................................................................; 3.* .bbreviations.........................................................................................................................................................<

8 =i h level Principles and 1oncepts........................................................................................................<

8., =i h level .rchitectural Principles for 3GPP* ,(1" "/>11..............................................................................< 8.* 1oncepts? 2?3T/.' to 3GPP* ,(1" "/>11.....................................................................................................< 8.*., 2?3T/.' to 3GPP* ,(1".................................................................................................................................@ 8.*.* "/>11 in 5imited "ervice Mode.......................................................................................................................A

9 .rchitecture model and reference points................................................................................................A

9., General...................................................................................................................................................................A 9.* /eference architecture? 2?3T/.' to 3GPP* ,(1" "/>11 architecture.........................................................,+ 9.3 7unctional 2ntities...............................................................................................................................................,+ 9.3., 3GPP* ,( 1" "/>11 interwor#in solution function (,(1" &B")................................................................,+ 9.3.* M"1 "erver enhanced for 2?3T/.'C3T/.' (="P.) to 3GPP 3T/.'CG2/.' "/>11........................,, 9.3.3 MM2? &nterwor#in with 3GPP* ,(1" &B"...................................................................................................,, 9.3.8 32 enhanced for "/>11..................................................................................................................................,, 9.3.9 "ervin CP:' GB..............................................................................................................................................,, 9.3.; 2?3T/.'.........................................................................................................................................................,, 9.3.< ="" ,, 9.3.@ P11 ,, 9.8 /eference points...................................................................................................................................................,* 9.8., MM2 D 3GPP* ,(1" &B" (",+*)....................................................................................................................,* 9.8.* MM2C"G"' D M"1 "erver ("v)......................................................................................................................,* 9.8.3 2?3T/.' D MM2 (",?MM2).........................................................................................................................,* 9.8.8 ="" D MM2 (";a)............................................................................................................................................,* 9.8.9 ="" D "G"' (Gr- ";d).....................................................................................................................................,* 9.8.; ="" ? M"1 (M.P :).......................................................................................................................................,*

; Procedures and flows...........................................................................................................................,*

;., "/>11 from 2?3T/.' to 3GPP* ,Ecs ? 2?3T/.' .ttach procedure for "/>11......................................,* ;.,., "ervice /eFuest procedures for "/>11...........................................................................................................,* ;.,.* P" =andover procedures for "/>11...............................................................................................................,3 ;.,.3 1all flows for "/>11 from 2?3T/.'...........................................................................................................,3

Annex A (informative): Determination of Neighbour Cell List.................................................15 .., "/>11 from 2?3T/.' to 3GPP* ,(1"........................................................................................,9 ,9

3GPP

Release #"

3GPP TS "3$"#% V#"$&$& "&#3'#"!

+ore4ord
This Technical "pecification has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuin wor# within the T"G and may chan e followin formal T"G approval. "hould the T"G modify the contents of the present document- it will be re?released by the T"G with an identifyin chan e of release date and an increase in version number as followsG >ersion (.y.! whereG ( the first di itG , presented to T"G for informationH * presented to T"G for approvalH 3 or reater indicates T"G approved document under chan e control. y the second di it is incremented for all chan es of substance- i.e. technical enhancements- correctionsupdates- etc. ! the third di it is incremented when editorial only chan es have been incorporated in the document.

3GPP

Release #"

3GPP TS "3$"#% V#"$&$& "&#3'#"!

1
?

Sco&e
from 2?3T/.' to 3GPP* ,(1"H

This document specifies the architecture enhancements for "in le /adio >oice 1all 1ontinuity ("/>11) between the followin access systems for voice calls that are anchored in the &M"G

This document will not describe 3GPP* functional entities. =owever- interfaces between both 3GPP and 3GPP* functional entities are described in this specification. "/>11 from 2?3T/.' access to 3GPP* ,(1" is covered in this specification- includin the handlin of &M" emer ency call continuity. =andlin of non?voice component and "/>11 from 3GPP* ,(1" to 2?3T/.' direction is not specified in this release.

2
I,J I*J I3J I8J I<J I@J IAJ I,+J I,,J I,*J I,3J I,8J I,9J I,;J I,<J I,@J I,AJ I*+J I*,J I**J

$e5ere)ce%
3GPP T/ *,.A+9G K>ocabulary for 3GPP "pecificationsK. 3GPP T" *3.8+,G KGP/" enhancements for 2?3T/.' accessK. 3GPP T" *3.8+* K.rchitecture enhancements for non?3GPP accessesK. 3GPP* E."++8*?+G K>oice 1all 1ontinuity between &M" and 1ircuit "witched "ystemK. 3GPP T/ 3;.A3@G K&mproved 'etwor# 1ontrolled Mobility between 2?3T/.' and 3GPP*CMobile BiM.E /adio Technolo iesK. 3GPP* .."+++@?1G K&nteroperability "pecification (&O") for =i h /ate Pac#et :ata (=/P:) /adio .ccess 'etwor# &nterfaces with "ession 1ontrol in the .ccess 'etwor#K. 3GPP T" **.*<@G K"ervice reFuirements for the 2volved Pac#et "ystem (2P")K. 3GPP T" *3.+;+G KGeneral Pac#et /adio "ervice (GP/")H "ervice descriptionH "ta e *K. 3GPP T" *9.8,3G K3T/.' &u interface /adio .ccess 'etwor# .pplication Part (/.'.P) si nallin K. 3GPP T" 83.,*AG KPac#et?switched handover for G2/.' .CGb modeH "ta e *K. 3GPP T" *3.*A*G K&P Multimedia "ubsystem (&M") 1entrali!ed "ervicesG "ta e *K. 3GPP T" *3.*3<G K&P Multimedia "ubsystem (&M") "ervice 1ontinuityG "ta e *K. 3GPP T" *3.++*G K'etwor# .rchitectureK. 3GPP T" 3;.3++G K2volved 3niversal Terrestrial /adio .ccess (2?3T/.) and 2volved 3niversal Terrestrial /adio .ccess 'etwor# (2?3T/.')H Overall descriptionH "ta e *K. >oid. 3GPP T" *3.++AG K=andover proceduresK. 3GPP T" *9.33,G K/adio /esource 1ontrol (//1) protocol specificationK. 3GPP* .."++,8G K&nteroperability "pecification (&O") for cdma*+++ .ccess 'etwor# &nterfacesK. 3GPP T" 33.*,+G K3G "ecurityH 'etwor# :omain "ecurityH &P networ# layer securityK. 3GPP T" 33.8+,G K3GPP "ystem .rchitecture 2volution (".2)G "ecurity architectureK.

The followin documents contain provisions which- throu h reference in this te(t- constitute provisions of the present document.

3GPP

Release #"

3GPP TS "3$"#% V#"$&$& "&#3'#"!

I*3J I*8J I*9J I*;J I*<J I*@J I*AJ I3+J I3,J I3*J I33J I38J I39J I3;J I3<J I3@J I3AJ I8+J I8,J I8*J

3GPP T" 8@.++@G KMobile "witchin 1entre ? 0ase "tation "ystem (M"1?0"") interfaceH 5ayer 3 specificationK. 3GPP T" 8@.+,@G KGeneral Pac#et /adio "ervice (GP/")H 0ase "tation "ystem (0"") ? "ervin GP/" "upport 'ode ("G"')H 0"" GP/" Protocol (0""GP)K. 3GPP T" 33.,+*G K3G "ecurityH "ecurity architectureK. 3GPP T" **.,<3G K&P Multimedia 1ore 'etwor# "ubsystem (&M") Multimedia Telephony "ervice and supplementary servicesK. 3GPP T" *3.++3G K'umberin - addressin and identificationK. 3GPP T" *3.,;<G K&P Multimedia 1ore 'etwor# "ubsystem (&M") emer ency sessionsK. 3GPP T" *3.*<,G K7unctional sta e * description of 5ocation "ervices (51")K. 3GPP T" 3;.8,3G K2volved 3niversal Terrestrial /adio .ccess 'etwor# (2?3T/.')H ", .pplication Protocol (",.P)K. 3GPP T" **.,+,G K"ervice aspectsH "ervice principlesK. 3GPP T" *3.*+3G KPolicy and char in control architectureK. &T3?T /ecommendation =.3*8 .nne( %G KMedia oriented ne otiation acceleration procedureK and associated chan es to .nne( LK. 3GPP T" *;.,,,G K1odec for circuit switched multimedia telephony serviceH Modifications to =.3*8K. 3GPP T/ *;.A,,G K1odec(s) for 1ircuit?"witched (1") multimedia telephony serviceH Terminal implementor$s uideK. 3GPP T" 3;.8*3G K2volved 3niversal Terrestrial /adio .ccess 'etwor# (2?3T/.')H E* .pplication Protocol (E*.P)K. 3GPP T" *A.3+3G K:omain 'ame "ystem ProceduresH "ta e 3K. 3GPP T" **.++*G K1ircuit 0earer "ervices (0") supported by a Public 5and Mobile 'etwor# (P5M')K. 3GPP T" **.++3G K1ircuit Teleservices supported by a Public 5and Mobile 'etwor# (P5M')K. 3GPP T" *3.*9,G K'etwor# sharin H .rchitecture and functional descriptionK. 3GPP T" *A.++*G KMobile .pplication Part (M.P) specificationK. 3GPP T" *3.*<*G K1ircuit "witched (1") fallbac# in 2volved Pac#et "ystem (2P")K.

6e5i)itio)% !)d !**re"i!tio)%

3.1 6e5i)itio)%
7or the purposes of the present document- the terms and definitions iven in T/ *,.A+9 I,J and the followin apply. . term defined in the present document ta#es precedence over the definition of the same term- if any- in T/ *,.A+9 I,J. 1xCS: The 3GPP* le acy circuit switched si nallin system as defined in 3GPP* E."++8*?+ I8J. 3 !! S"#CC $%G . 3GPP "/>11 32 is a 32 enhanced for &M" "ervice 1ontinuity with the additional 32 capabilities described in this specification for "/>11 between 2?3T/.' and 3GPP 3T/.' and C or between 2? 3T/.' and 3GPP G2/.' and C or between 3T/.' (="P.) and 3GPP 3T/.' and 3GPP G2/.'. &'S(base) '!S Session: see T" *3.8+, I*J.

3GPP

Release #"

3GPP TS "3$"#% V#"$&$& "&#3'#"!

Session *ransfer Number for S"#CC (S*N(S"): see T" *3.*3< I,8J. Single "a)io #oi+e Call Continuit, (S"#CC): >oice call continuity between &M" over P" access and 1" access for calls that are anchored in &M" when the 32 is capable of transmittin Creceivin on only one of those access networ#s at a iven time.

3.2 (**re"i!tio)%
7or the purposes of the present document- the abbreviations iven in T/ *,.A+9 I,J and the followin apply. .n abbreviation defined in the present document ta#es precedence over the definition of the same abbreviation- if any- in T/ *,.A+9 I,J. ,(1" &B" ./P 1?M"&":' MP" ".& "/>11 v"/>11 "in le /adio >oice 1all 1ontinuity &nterwor#in solution 7unction for 3GPP* ,(1" .llocation and /etention Priority 1orrelation M"&":' Multimedia Priority "ervice "ervice .rea &dentifier as defined in T" *9.8,3 I,,J and T" *3.++3 I*<J "in le /adio >oice 1all 1ontinuity "in le /adio >ideo 1all 1ontinuity

/
/.1

7i3' e"e Pri)ci& e% !)d Co)ce&t%

7i3' e"e (rc'itectur! Pri)ci& e% 5or 3GPP2 11CS S$VCC

The solution for "/>11 fulfils the reFuirements of T" **.*<@ IAJ and the followin architectural principlesG ,. The solution shall allow coe(istence and be compatible with the ,(1" procedures specified in the 3GPP* >11 specification- E."++8* I8J. *. The solution shall not reFuire 32 with multiple /.Ts capability to simultaneously si nal on two different /.Ts. 3. The solution shall be transparent to 2?3T/. only terminal or networ#. 8. The solution shall minimi!e the couplin between the 2?3T/.' and the 3GPP* access. &n particular- the solution shall allow the cdma*+++ ,(/TT specification to evolve without necessitatin a modification to the 2? 3T/.' specifications. 9. /.T chan e and domain selection should be under networ# control. ;. &n roamin cases- the >isited P5M' should control the /.T chan e andCor domain selection while ta#in into account any related =P5M' policies. <. The solution shall not impact cdma*+++ /.T. @. The solution shall not impact cdma*+++ 1" 1'. A .ll &M" sessions that may be subject to "/>11 shall be anchored in the &M" (>11 .pplication). ,+. Bhen "/>11 is deployed- M1&N,G ? ? shall not be used for &M" sessions that are not anchored in the &M" (>11 .pplication)H and shall only be used for the voice bearer.

/.2 Co)ce&t%- E-UT$(, to 3GPP2 11CS S$VCC

7or "/>11?capable 32s- the call is always anchored at the >11 ." in the 3GPP*$s &M". The 3GPP* ,(1" &B" enables a sin le radio 32 to communicate in parallel both with the source system and the tar et system. 7rom >11 perspective- this mechanism minimi!es the voice ap by supportin the transport of si nallin for establishment of the tar et 1" access le while the terminal is connected to the source P" access networ#.

3GPP

Release #"

3GPP TS "3$"#% V#"$&$& "&#3'#"!

+igure ($"$#'#, Transport of 3GPP" #-CS signalling messages for preparation of the CS access leg in the target system The ",+* reference point is used to convey 3GPP* ,(1" si nallin messa es between the MM2 and 3GPP* ,(1" &B". These ,( 1" si nallin messa es are actually e(chan ed between the 32 and the 3GPP* ,(1" &B"- and ",+* is only one lin# in the overall 32?,(1" &B" tunnellin path. On the remainin portion of the tunnellin path- the 3GPP* ,(1" si nallin messa es are encapsulated in 2?3T/.'C2P" tunnellin messa es (32?MM2).

/.2.1

E-UT$(, to 3GPP2 11CS

The 32 initiates emer ency session over 2?3T/.' as specified in T" *3.,;< I*@J- T" *3.8+, I*J- upon detectin handover is reFuired from 2?3T/.' to 1:M. ,(- the "/>11 emer ency procedure apply. To support handover of emer ency session the networ# is aware that the 32 and core networ# support "/>11 and has information to identify 2mer ency session. Bhen handover of the emer ency session has been completed- the MM2 or the ,(/TT side may initiate location continuity procedures for the 32 as defined in T" *3.*<, I*AJ.

3GPP

Release #"

3GPP TS "3$"#% V#"$&$& "&#3'#"!

+igure ($"$($"'#, /'0TRA1 to 3GPP" #-CS

/.2.2

S$VCC i) Limited Ser"ice Mode

&n order to support "/>11 emer ency session domain transfer for 32s in 5imited "ervice Mode (e. . 3&11?less)- the MM2 shall support 5imited "ervice Mode 32 emer ency attach defined in T" *3.8+, I*J usin unauthenticated &M"& or eFuipment identifier. Bhen 2?3T/.' determines that "/>11 is needed- the MM2 invo#es "/>11 procedures to the ,(1" &B" includin the 32$s eFuipment identifier.

(rc'itecture mode !)d re5ere)ce &oi)t%

#.1 Ge)er!
The "/>11 .rchitecture for 3GPP* ,(1" reuses many e(istin elements in 3GPP* E."++8* I8J for 3GPP* ,(1". The "/>11 and v"/>11 .rchitectures for 3GPP 2?3T/.' C 3T/.'(="P.) to 3GPP 3T/.'CG2/.' reuses the session transfer function defined for &M" in T" *3.*3< I,8J for &M" service continuity. The M"1 "erver that is enhanced for "/>11 and v"/>11 may also be enhanced for &1" as defined in T" *3.*A* I,3J.

3GPP

Release #"

#&

3GPP TS "3$"#% V#"$&$& "&#3'#"!

The "/>11 .rchitecture for 1" to P" reuses the session transfer function defined for &M" in T" *3.*3< I,8J for &M" service continuity. The M"1 "erver that is enhanced for 1" to P" "/>11 is also enhanced for &1" as defined in T" *3.*A* I,3J. The overall model and impacts to the various elements is provided in the followin clauses.

#.2 $e5ere)ce !rc'itecture- E-UT$(, to 3GPP2 11CS S$VCC !rc'itecture

This specification introduces an additional functional entity to those defined in the 2?3T/.' architecture T" *3.8+* I3J- called ,( 1" "/>11 interwor#in solution function (3GPP* ,(1" &B")- see fi ure 9.*.,?,. 'OT2G
11CS S$VCC UE

The fi ure only shows the necessary components related to 3GPP* ,(1" &B".

11$TT CS (cce%%

(1 (1 11CS I9S S102 MME

11$TT MSC IMS

S1-MME 11CS S$VC C UE E-UT$(, S1-U SIP %i3)! i)3 :e!rer *e5ore 7; :e!rer !5ter 7;

S11 Ser"i)38P6, G9 SGi

Tu))e ed 11$TT me%%!3e%

+igure )$"$#'#, SRVCC architecture for /'0TRA1 to 3GPP" #-CS

#.3 +u)ctio)! E)titie%

'OT2 ,G 3GPP* components are not described here. Please refer to 3GPP* E."++8* I8J. 'OT2 *G &M" components are not described here. Please refer to T" *3.*3< I,8J and T" *3.*A* I,3J.

#.3.1 3GPP2 11 CS S$VCC i)ter4or<i)3 %o utio) 5u)ctio) (11CS I9S)

3GPP* ,(1" &B" uses the ",+* reference point to communicate with the MM2 and to transport 3GPP* ,(1" si nallin messa es to the "/>11 32. The role of the 3GPP* ,(1" &B" isG ? ? To be a si nallin tunnellin end point towards the MM2 for receivin Csendin encapsulated 3GPP* ,(1" si nallin messa es toCfrom the 32H and To emulate a ,(/TT 0"" towards the ,(/TT M"1 (reference point ., as defined in 3GPP* .."++,8 I*+J between ,(0" and M"1).

3GPP

Release #"

##

3GPP TS "3$"#% V#"$&$& "&#3'#"!

#.3.2 MSC Ser"er e)'!)ced 5or E-UT$(,8UT$(, (7SP() to 3GPP UT$(,8GE$(, S$VCC #.3.3 MME- I)ter4or<i)3 4it' 3GPP2 11CS I9S
&f the MM2 (operator) supports interwor#in to 3GPP* ,(1"- the MM2 shall follow the rules and procedures described in T" *3.8+* I3J with the followin additions and clarificationsG ? To be a si nallin tunnellin end point towards the 3GPP* ,(1" &B" for sendin Creceivin encapsulated 3GPP* ,(1" si nallin messa es toCfrom the 32- which are encapsulated in ",?MM2 ", &nformation Transfer messa es (T" 3;.8,3 I3+J). release of the 2?3T/.' resources after "/>11 to the 3GPP* ,(1" is completed. include information to enable 3GPP* networ# to determine emer ency session. insert the eFuipment identifier durin the handover procedure of an emer ency session.

? ? ?

"election of 3 pp* ,(cs &B" ? The 3GPP* ,(1" &B" can be selected based on the local confi uration in the MM2 ta#in into account the /eference 1ell&: received in the 3plin# ", cdma*+++ Tunnellin messa e.

#.3./ UE e)'!)ced 5or S$VCC

&f the 32 supports 3GPP* ,(1" access- the ,(1" "/>11 32 is a 32 that is capable to perform "/>11 to the 3GPP* ,(1" system. The interaction between 32 and 2?3T/.' is described in T" 3;.3++ I,;J. The interaction with the 3GPP* ,(1" system is described in this specification.

#.3.# Ser"i)38P6, G9
The P:' GB shall support the P"?to?1" handover indicator as notified by the MM2C"G"' (see detailed procedures in clause ;.*.*). 'OT2G &f "/>11 is deployed and P11 is not used then the P:' GB is not able to enforce the architecture principle to use M1&N,- see clauses 8.,., and 8.,.*.

#.3.6 E-UT$(,
&f the 2?3T/.' (operator) supports interwor#in to 3GPP* ,(1"- the 2?3T/.' performs the =O tri er- tunnellin of the 3GPP* ,(1" si nallin messa es toward the MM2- and interactin with the "/>11 32 as described in T" 3;.3++ I,;J. 2?3T/.' may be capable of determinin the nei hbour cell list based on the K"/>11 operation possibleK indication andCor presence of an established M1&N, bearer for a specific 32. .n e(ample al orithm is provided in clause ..,. 'OT2G &f 2?3T/.' does not update the nei hbour cell list dynamically- if 2?3T/.' tri ers handover to ,( when either the K"/>11 operation possibleK indication is set to KfalseK or there is no established M1&N, bearer for a specific 32- this will result in an error case.

#.3.2 7SS #.3.= PCC

The P1/7 enforces the architecture principle to use M1&N, (and traffic?class conversational with source statistics descriptor NKspeechK) for voice bearer with &M" sessions anchored in the "11 ."- based on the service the session relates to. This may be achieved by deployin "A reference point- or confi uration and roamin a reements. The P127 should enforce to multiple( the media streams from multiple concurrent normal voice sessions. 'OT2G &n this /elease the 32 initiated P:P conte(t for voice bearer is not supported.

3GPP

Release #"

#"

3GPP TS "3$"#% V#"$&$& "&#3'#"!

7or v"/>11- the P1/7 enforces that the video bearer of &M" sessions anchored in the "11 ."- is mar#ed with the KP" to 1" session continuity indicatorK- see T" *3.*+3 I3*J- and hence can be identified as v"/>11 mar#ed video P" bearer in clause 9.3.3.*.*.

#./ $e5ere)ce &oi)t%

#./.1 MME > 3GPP2 11CS I9S (S102)
The ",+* reference point provides a tunnel between MM2 and 3GPP* ,(1" &B" to relay 3GPP* ,(1" si nallin messa es. ,( 1" si nallin messa es are those messa es that are defined for .*, interface as described in 3GPP* .."+++@?1 I@J. 'OT2. &t is up to sta e 3 to determine whether the tunnellin protocol for ",+* can be defined as e(actly as in .*,. &f so- ",+* is then eFuivalent to .*,.

#./.2 MME8SGS, > MSC Ser"er (S") #./.3 E-UT$(, > MME (S1-MME)
7or 3GPP* ,(1" "/>11- the ",?MM2 reference point provides ", &nformation Transfer messa e (T" 3;.8,3 I3+J) between 32 and MM2 to relay the 3GPP* ,(1" si nallin messa es. 7or 3GPP (v)"/>11- the ",?MM2 reference point allows handover si nallin between 2?3T/.' and MM2. &t is defined in T" 3;.3++ I,;J

#././ 7SS > MME (S6!) #./.# 7SS > SGS, (Gr, S6d) #./.6 7SS - MSC (M(P 6)

Procedure% !)d 5 o4%

6.1 S$VCC 5rom E-UT$(, to 3GPP2 1?c% - E-UT$(, (tt!c' &rocedure 5or S$VCC
2?3T/.' attach or emer ency attach procedure for 3GPP* "/>11 32 is performed as defined in T" *3.8+, I*J with the followin additionsG ? ? "/>11 32 includes the "/>11 capability indication as part of the K32 'etwor# 1apabilityK in the .ttach /eFuest messa e. MM2 stores this information for "/>11 operation. "/>11 32 capable for &M" emer ency calls shall include the "/>11 capability indication as part of the 32 networ# capability in the 2mer ency .ttach /eFuest messa e. MM2 stores this information for emer ency "/>11 operation. MM2 includes a K"/>11 operation possibleK indication in the ", .P &nitial 1onte(t "etup /eFuest- meanin that both 32 and MM2 are "/>11?capable.

6.1.1 Ser"ice $e@ue%t &rocedure% 5or S$VCC

"ervice /eFuest procedures for 3GPP* "/>11 32 are performed as defined in T" *3.8+, I*J with the followin additionsG

3GPP

Release #"

#3

3GPP TS "3$"#% V#"$&$& "&#3'#"!

MM2 includes a K"/>11 operation possibleK indication in the ", .P &nitial 1onte(t "etup /eFuest- meanin that both 32 and MM2 are "/>11?capable.

6.1.2 PS 7!)do"er &rocedure% 5or S$VCC

&ntra?2?3T/.' ",?based handover procedures for 3GPP* "/>11 32 are performed as defined in T" *3.8+, I*J with the followin additionsG ? The tar et MM2 includes a K"/>11 operation possibleK indication in the ",?.P =andover /eFuest messa emeanin that both 32 and the tar et MM2 are "/>11?capable.

7or E*?based handover- the source e'ode0 includes a K"/>11 operation possibleK indication in the E*?.P =andover /eFuest messa e to the tar et e'ode0 as specified in T" 3;.8*3 I3;J.

6.1.3 C! 5 o4% 5or S$VCC 5rom E-UT$(,

7i ure ;.,.3?, illustrates a hi h?level call flow for the 2?3T/.'?to?,( voice service continuity procedure.

+igure %$#$3'#, 3T/ Vo4P'to'#- CS voice service continuity ,. On oin >o&P session over the &M" access le established over 2P"C2?3T/.' access. *. ,(1" "/>11 32 sends measurement reports to e'ode0. 3. The 2?3T/.' (e. .- based on some tri er- measurement reports) ma#es a determination to initiate an inter?technolo y handover to cdma*+++ ,(/TT.

3GPP

Release #"

#(

3GPP TS "3$"#% V#"$&$& "&#3'#"!

8. The 2?3T/.' si nals the 32 to perform an inter?technolo y handover by sendin a =andover from 23T/. Preparation /eFuest (3G,( Overhead Parameters- /.': value) messa e. 9. The 32 initiates si nallin for establishment of the 1" access le by sendin a 35 handover preparation Transfer messa e containin the ,(/TT Ori ination messa e. 7or the case of emer ency voice service continuity- the reFuest includes a /eFuest?Type N Kemer ency handoverK and the M2&: (e. . &M2&) is included. ;. The 2?3T/.' sends an 3plin# ", cdma*+++ Tunnellin (M2&:- /.':- ,( Ori ination- /eference 1ell&:) messa e to the MM2. The e'ode0 will also include 1:M.*+++ =O /eFuired &ndication &2 to 3plin# ", 1:M.*+++ Tunnellin messa e- which indicates to the MM2 that the handover preparation has started. <. 3pon reception of the 3plin# ", cdma*+++ Tunnellin messa e- the MM2 selects a 3GPP* ,(1" &B" as specified in clause 9.3.3.,.* and encapsulates the ,( Ori ination Messa e alon with the M2&: and /.': in a ",+* :irect Transfer messa e (as K,( .ir &nterface "i nallin K). @. The traffic channel resources are established in the ,( /TT system and 3GPP* ,(1" procedures for initiation of "ession Transfer are performed as per 3GPP* E."++8* I8J. 'OT2 ,G "tep A and 3GPP* ,(1" procedures in step @ are independent of each other. 'OT2 *G 7or non?emer ency session transfers- the K>:'K parameter referred to in 3GPP* E."++8* I8J corresponds to the "T'?"/ parameter defined in T" *3.*3< I,8J. 'OT2 3G The emer ency session transfer procedures and procedures for the ,( 1" "/>11 32 obtainin the local emer ency "T'?"/ will be specified by 3GPP*. A. The 3GPP* ,(1" &B" creates a ,( messa e and encapsulates it in a ",+* :irect Transfer messa e (,( messa e=andover indicator). &f the 3GPP* access was able to allocate resources successfully- the ,( messa e is a ,( =andover :irection messa e and the handover indicator indicates successful resource allocation. Otherwise- the handover indicator indicates to the MM2 that handover preparation failed and the embedded ,( messa e indicates the failure to the 32. ,+. The MM2 sends the ,( messa e and 1:M.*+++ =O "tatus &2 in a :ownlin# ", cdma*+++ Tunnellin messa e to the 2?3T/.'. The 1:M.*+++ =O "tatus &2 is set accordin to the handover indicator received over the ",+* tunnel. ,,. &f the 1:M.*+++ =O "tatus &2 indicates successful handover preparation- the 2?3T/.' forwards the ,( =andoff :irection messa e embedded in a Mobility from 23T/. 1ommand messa e to the 32. This is perceived by the 32 as a =andover 1ommand messa e. &f handover preparation failed- :5 &nformation transfer messa e will be sent instead- with the embedded ,(/TT messa e that indicates the failure to the 32. ,*. Once the 32 receives the traffic channel information from the cdma*+++ ,(/TT system- the 32 retunes to the ,(/TT radio access networ# and performs traffic channel acFuisition with the ,(/TT 1" access (e. .- ,(/TT 0""). ,3. The 32 sends a ,(/TT handoff completion messa e to the ,(/TT 1" access (e. .- ,(/TT 0""). ,8. The ,(/TT 1" .ccess sends messa e to ,(/TT M"1 to indicate of handoff done. The resources between ,( 1" &B" and ,(/TT M"1 may be released at this step. ,9. On oin voice call over the 1" access le established over ,(/TT access. The 2?3T/.'C2P" conte(t may be released based on the normal 2?3T/.'C2P" procedure. ,;. The e'ode0 sends an ", 32 1onte(t /elease /eFuest (1ause) messa e to the MM2. 1ause indicates the ", release procedure is caused by handover from 2?3T/.' to ,(/TT. ,<. The MM2 deactivates G0/ bearers towards "?GB and P?GB(s) by initiatin MM2?initiated :edicated 0earer :eactivation procedure as specified in T" *3.8+, I*J. P"?to?1" handover indicator is notified to P?GB for voice bearer durin the bearer deactivation procedure. The MM2 starts preservation and suspension of non?G0/ bearers by sendin "uspend 'otification messa e towards "?GB. The "?GB releases ",?3 bearers for the 32 and sends "uspend 'otification messa e to the P?GB(s). The MM2 stores in the 32 conte(t that the 32 is in suspended status. .ll the preserved non?G0/ bearers are mar#ed as suspended status in the "?GB and P?GB. The P?GB should discard pac#ets if received for the suspended 32. ,@. ", 32 1onte(t in the e'ode0 is released as specified in T" *3.8+, I*J.

3GPP

Release #"

#)

3GPP TS "3$"#% V#"$&$& "&#3'#"!

,A. 7or an emer ency services session after handover is complete- if the control plane location solution is used on the source side- the source MM2 shall send a "ubscriber 5ocation /eport carryin an indication of the ,(/TT M"1 (e. . reference cell &:) to the GM51 associated with the source side as defined in T" *3.*<, I*AJ to support location continuity. This enables location continuity for the ,(/TT side. .lternatively- if the control plane solution is not used on the source side- location continuity procedures shall be insti ated on the ,(/TT side. 'OT2 8G 5ocation continuity on the ,(/TT side will be specified by 3GPP*. &f the 32 has returned to 2?3T/.' after the 1" voice call was terminated- then the 32 shall resume P" service by sendin T.3 to MM2. The MM2 will in addition inform "?GB and P?GB(s) to resume the suspended bearers. /esumin the suspended bearers in the "?GB and in the P?GB should be done by implicit resume usin the Modify 0earer /eFuest messa e if it is tri ered by the procedure in operation- e. . T.3 or "ervice /eFuest. The "?GB is aware of the suspend state of the bearers and will forward the Modify 0earer /eFuest to the P?GB. 2(plicit resume usin the /esume 'otification messa e should be used in cases when Modify 0earer /eFuest is not tri ered by the procedure in operation.

())e1 ( (i)5orm!ti"e)6etermi)!tio) o5 ,ei3'*our Ce Li%t

This anne( describes e(ample al orithms for determination of 'ei hbour 1ell 5ist ('15) for "/>11 operation. &n case of "/>11 to G2/.'C3T/.' it is also clarified when the 2?3T/.' includes a "/>11 indication in the =andover /eFuired messa e.

(.1
?

S$VCC 5rom E-UT$(, to 3GPP2 11CS

&f the K"/>11 operation possibleK indication is set to KtrueK (i.e. both 2P1 and 32 are "/>11 capable)- thenG ? ? if there is an established M1&N, bearer for this 32- then ,( cells may be included as candidate tar et cells in the '15H if there is no established M1&N, bearer for this 32- then ,( cells are not included in the '15.

2?3T/.' may determine the '15 as followsG

&f the K"/>11 operation possibleK indication is set to KfalseK (i.e. either 2P1 or 32 is not "/>11 capable)then ,( cells are not included in the '15.

3GPP