3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Circuit Switched V11.2.

0 (CS) fall (2012-09) ac! in "volved Pac!et System ("PS); Technical Specification Sta#e $ (%elease &&)

3GPP TS 23.272

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.

%elease &&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

%eywords
LTE, circuit mode, UMTS, GSM

3GPP Postal address 3GPP support office address

6 0 !oute de" Lucio#e" - So$%i& '(ti$o#i" V&#)o((e - *!'+,E Te#.- .33 / 92 9/ /2 00 *&0- .33 / 93 6 /7 16

&nternet
%tt$-11222.33$$.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.
) *+,*- 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"& currently bein 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

%elease &&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

,o(te(t"
1ontents....................................................................................................................................................3 7oreword...................................................................................................................................................8 , "cope......................................................................................................................................................9 * /eferences..............................................................................................................................................9 3 :efinitions and abbreviations.................................................................................................................;
3., :efinitions..............................................................................................................................................................; 3.* .bbreviations.........................................................................................................................................................;

< Overall :escription................................................................................................................................;

<., General 1onsiderations..........................................................................................................................................; <.* /eference .rchitecture.........................................................................................................................................,+ <.*., /eference points................................................................................................................................................,+ <.3 7unctional entities................................................................................................................................................,, <.3., 32 ,, <.3.* MM2 ,, <.3.3 M"1 ,* <.3.< 2=3T/.'.........................................................................................................................................................,* <.3.> "G"' ,3 <.3.8 0"" ,3 <.3.9 /'" ,3 <.< 1ontrol plane........................................................................................................................................................,3 <.<., MM2 = M"1 "erver..........................................................................................................................................,3 <.> 1o=e(istence with &M" services...........................................................................................................................,< <.8 2mer ency 1alls..................................................................................................................................................,< <.9 1"70 Priority 1all ?andlin ...............................................................................................................................,< <.@ 1" services handlin in specific cases.................................................................................................................,< <.@., "Gs pa in without 5.&...................................................................................................................................,< <.@.* ?andlin of "Gs pa in when MM2 cannot retrieve the "=TM"&...................................................................,>

> Mobility Mana ement..........................................................................................................................,>

>., General.................................................................................................................................................................,> >.,. T.& list and 5.& allocation...............................................................................................................................,> >.* .ttach procedure..................................................................................................................................................,> >.3 :etach procedure.................................................................................................................................................,9 >.3., 32=initiated :etach procedure..........................................................................................................................,9 >.3.,. 32=initiated :etach procedure for G2/.'A3T/.' with &"/ activated.....................................................,@ >.3.* MM2=initiated :etach procedure.....................................................................................................................,; >.3.*. "G"'=initiated :etach procedure with &"/ activated...................................................................................,; >.3.3 ?""=initiated :etach procedure........................................................................................................................*+ >.3.< .dministration of the MM2 = M"1AB5/ .ssociation.....................................................................................*+ >.< T.A5. 3pdate procedure....................................................................................................................................*, >.<.+ General *, >.<., 1ombined T.A5. 3pdate Procedure................................................................................................................*, >.<.* Periodic T. and 5. 3pdate Procedure............................................................................................................*3 >.<.3 'on=2P" .lert procedure.................................................................................................................................*3 >.<.< Boid *3 >.> &dle Mode "i nallin /eduction..........................................................................................................................*3 >.8 Mobility Mana ement for "M" over "Gs only 32s...........................................................................................*<

8 Mobile Ori inatin 1all.......................................................................................................................*>

8., General.................................................................................................................................................................*> 8.* Mobile Ori inatin call in .ctive Mode = P" ?O supported...............................................................................*> 8.3 Mobile Ori inatin call in .ctive Mode C 'o P" ?O support............................................................................*9 8.< Mobile Ori inatin call in &dle Mode..................................................................................................................3, 8.> /eturnin bac# to 2=3T/.'...............................................................................................................................3,

3GPP

%elease &&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

8.8 Mobile Ori inated or Mobile terminated call rejected by the MM2...................................................................3*

9 Mobile Terminatin 1all......................................................................................................................3<

9., General.................................................................................................................................................................3< 9.* Mobile Terminatin call in idle mode..................................................................................................................3< 9.3 Mobile Terminatin call in .ctive Mode = P" ?O supported.............................................................................38 9.< Mobile Terminatin call in .ctive Mode = 'o P" ?O support...........................................................................3; 9.> /oamin /etry for 1" fallbac#............................................................................................................................<3 9.>a /oamin 7orwardin for 1" fallbac#................................................................................................................<< 9.>b 1oe(istence of /oamin /etry and /oamin 7orwardin for 1" fallbac#.......................................................<9 9.8 /eturnin bac# to 2=3T/.'...............................................................................................................................<9 9.9 &nteraction with &"/.............................................................................................................................................<9 9.9., Boid <9 9.9.* Mobile Terminatin 1all when &"/ is active and "Gs is active between M"1AB5/ and MM2.....................<@ 9.9.3 Boid <; 9.@ Mobile Terminatin 1all when "Gs is not active................................................................................................<;

@ Other 1" "ervices................................................................................................................................<;

@., General.................................................................................................................................................................<; @.* "hort Messa e "ervice ("M").............................................................................................................................<; @.*., General <; @.*.* Mobile ori inatin "M" in &dle Mode..............................................................................................................<; @.*.3 Mobile ori inatin "M" in .ctive Mode..........................................................................................................>, @.*.3a Multiple Mobile ori inatin "M"s..................................................................................................................>, @.*.< Mobile terminatin "M" in idle mode..............................................................................................................>, @.*.> Mobile terminatin "M" in .ctive Mode.........................................................................................................>* @.*.>a Multiple Mobile terminatin "M"s.................................................................................................................>* @.*.>b "imultaneous Mobile terminatin and Mobile ori inatin "M"s...................................................................>* @.*.>c 3nsuccessful Mobile terminatin "M" delivery attempt................................................................................>* @.*.>d 'on="M" Mobile terminatin activity durin "M" delivery.........................................................................>3 @.*.>e 'on="M" Mobile ori inatin activity durin "M" delivery..........................................................................>3 @.*.>f Mobile Terminatin "M" when &"/ is active and "Gs is active between M"1AB5/ and MM2..................>3 @.*.8 1o=2(istence with "M" over eneric 3GPP &P access.....................................................................................>3 @.3 5ocation "ervices (51")......................................................................................................................................>< @.3., MO=5/ procedure.............................................................................................................................................>< @.3.,., General >< @.3.,.* MO=5/ in .ctive Mode with &M" Bo&P session = P" ?O supported...........................................................>> @.3.,.3 MO=5/ in .ctive Mode with &M" Bo&P session = 'o P" ?O supported.....................................................>> @.3.* MT=5/ procedure.............................................................................................................................................>8 @.3.*., MT=5/ procedure if 32 is not in &M" Bo&P session.....................................................................................>8 @.3.*.* MT=5/ procedure while 32 is in &M" Bo&P session....................................................................................>9 @.3.3 '&=5/ procedure...............................................................................................................................................>@ @.3.< /eturnin bac# to 2=3T/.'............................................................................................................................>@ @.3.> 1o=2(istence with Other 5ocation "ervices.....................................................................................................>@ @.3.>., 1o=2(istence with "3P5...............................................................................................................................>@ @.< Other 1" "ervices................................................................................................................................................>@ @.<.+ General >@ @.<., Mobile=&nitiated 1" "ervices............................................................................................................................>@ @.<.* 'D=&nitiated 1" "ervices.................................................................................................................................>; @.<.3 /eturnin bac# to 2=3T/.'............................................................................................................................>;

Annex A: Void...............................................................................................................................60 Annex B (normative): CS Fallback to 1xRTT..........................................................................61 0., Overall :escription..........................................................................................................................8,

0.,., General 1onsiderations....................................................................................................................................8, 0.,.* /eference .rchitecture.....................................................................................................................................8, 0.,.*., /eference points............................................................................................................................................8* 0.,.3 7unctional entities............................................................................................................................................8* 0.,.3., 32 8*

3GPP

%elease &&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

0.,.3.* MM2 8* 0.,.3.3 2=3T/.'......................................................................................................................................................83 0.,.< 1o=e(istence with &M" services.......................................................................................................................83 0.,.> 1"70 Priority 1all ?andlin ............................................................................................................................83

0.* Procedures........................................................................................................................................8<
0.*., Mobility Mana ement......................................................................................................................................8< 0.*.,., ,( /TT 1" Pre=/e istration over 2P" Procedure........................................................................................8< 0.*.,.* ",+* Tunnel /edirection...............................................................................................................................8> 0.*.,.3 32=initiated :etach Procedure......................................................................................................................88 0.*.* Mobile Ori inatin 1all in .ctive Mode.........................................................................................................88 0.*.*a Mobile Ori inatin call in &dle Mode.............................................................................................................8@ 0.*.3 Mobile Terminatin 1all..................................................................................................................................8@ 0.*.3a 2nhanced 1" fallbac# to ,(/TT Procedure...................................................................................................9+ 0.*.3a., General 9+ 0.*.3a.* Mobile Ori inatin 1all without concurrent P" handover- or with concurrent non=optimised P" handover or optimised idle=mode P" handover.............................................................................................9, 0.*.3a.3 Mobile Ori inatin 1all with concurrent optimised P" handover..............................................................93 0.*.3a.< Mobile Terminatin 1all without P" handover- or with concurrent non=optimised P" handover or optimised idle=mode P" handover.................................................................................................9> 0.*.3a.> Mobile Terminatin 1all with concurrent optimised P" handover.............................................................98 0.*.3a.8 &nteraction between enhanced 1" 7allbac# to ,(/TT and optimised P" handover...................................99 0.*.3b Mobile Ori inated or Mobile terminated call rejected by the MM2..............................................................99 0.*.< "hort Messa e "ervice ("M")..........................................................................................................................9; 0.*.<., General..........................................................................................................................................................9; 0.*.<.* Mobile ori inatin "M"................................................................................................................................9; 0.*.<.3 Mobile terminatin "M"...............................................................................................................................@+ 0.*.> 2mer ency 1alls...............................................................................................................................................@,

0.3 1" 7allbac# for 32s with dual /( confi uration..............................................................................@,

0.3., General 1onsiderations....................................................................................................................................@, 0.3.* Procedures for leavin 2=3T/.'...................................................................................................................@* 0.3.3 Procedures for returnin to 2=3T/.'............................................................................................................@3

Annex C ( ormative): S!S in !!".........................................................................................#$ 1., General.............................................................................................................................................@3 1.* .rchitecture......................................................................................................................................@3 1.3 /eference Points...............................................................................................................................@<
1.3., General.............................................................................................................................................................@< 1.3.* "8a @< 1.3.3 "8c @< 1.3.< "Gd@>

1.< 'etwor# 2ntities...............................................................................................................................@>

1.<., General.............................................................................................................................................................@> 1.<.* MM2.................................................................................................................................................................@> 1.<.3 ?""@8

1.> /oamin considerations....................................................................................................................@8 1.8 3nsuccessful Mobile=Terminated "M" Transfer..............................................................................@9 1.9 &nformation stora e..........................................................................................................................@9
1.9., ?""@9 1.9.* MM2.................................................................................................................................................................@9

Annex % (in&ormative): C'an(e 'i)tor*......................................................................................+0

3GPP

%elease &&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

*ore2ord
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 followsE Bersion (.y.! whereE ( the first di itE , presented to T"G for informationF * presented to T"G for approvalF 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

%elease &&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

Sco$e

This document defines the "ta e * architecture and specification for the 1" 7allbac# and for "M" over "Gs for 2P" or 1" 7allbac# and "M" over ",+*. The scope of this document includes the architecture enhancements for functionality to enable fallbac# from 2=3T/.' access to 3T/.'AG2/.' 1" domain access and to 1:M. ,( /TT 1" domain access- and functionality to reuse of voice and other 1"=domain services (e. . 1" 3:& video A 51" A 3"":) by reuse of the 1" domain. The functionality specified to support "M" over "Gs does not tri er any 1" 7allbac# to 3T/.'AG2/.'. The functionality specified to support "M" over ",+* does not tri er any 1" 7allbac# to 1:M. ,(/TT 1" domain. &n addition this specification includes an "M" in MM2 architecture option for "M" services only. This functionality does not tri er any 1" 7allbac# and does not reGuire "Gs. The architecture enhancements to support 1" fallbac# to 1:M. ,( /TT 1" domain access for 32s with sin le and dual receiver confi urations are specified in .nne( 0. &n this /elease of the specification no mechanisms are specified to support 1" 7allbac# to both 3T/.'AG2/.' and 1:M. ,(/TT in the same P5M'. "o- even when a 32 has the capability to support both 1" 7allbac# to 3T/.'AG2/.' 1" domain and 1" 7allbac# to 1:M. ,(/TT 1" domain in a iven P5M'- the P5M' implements only one of the two.

!e4ere(ce"
/eferences are either specific (identified by date of publication- edition number- version number- etc.) or non=specific. 7or a specific reference- subseGuent revisions do not apply. 7or a non=specific reference- the latest version applies. &n the case of a reference to a 3GPP document (includin a G"M document)- a non=specific reference implicitly refers to the latest version of that document in the same Release as the present document. H,I H*I H3I H<I H>I H8I H9I H@I H;I H,+I H,,I H,*I 3GPP T/ *,.;+>E JBocabulary for 3GPP "pecificationsJ. 3GPP T" *3.<+,E JGP/" 2nhancements for 2=3T/.' .ccessJ. 3GPP T" *3.+8+E JGeneral Pac#et /adio "ervice (GP/")F "ervice descriptionF "ta e *J. 3GPP T" <<.+,@E JMobile radio interface layer 3 specification /adio /esource 1ontrol (//1) protocolJ. 3GPP T" *3.+,@E J0asic call handlin F Technical reali!ationJ. 3GPP T" <@.++@E JM"1=0"" interface layer 3 specificationF Protocol specificationJ. 3GPP T" *>.33,E J/adio /esource 1ontrol (//1)F Protocol specificationJ. 3GPP T" *3.*9,E J7unctional sta e * description of 5ocation "ervices (51")J. Open Mobile .lliance- OM. .: "3P5E J"ecure 3ser Plane 5ocation .rchitectureJhttpEAAwww.openmobilealliance.or . 3GPP T" *3.+;+E J3nstructured "upplementary "ervice :ata (3"":)F "ta e *J. Boid. 3GPP T" <<.+8+E JM"=0"" interfaceF /51AM.1 protocol J.

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

3GPP

%elease &&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

H,3I

3GPP T" *<.+,+E J"upplementary services specificationF General aspectsJ. H,<I 3GPP T" *3.+<+E JTechnical reali!ation of the "hort Messa e "ervice ("M")J.

H,>I 3GPP T" *3.*+<E J"hort Messa e "ervice ("M") over eneric 3GPP &nternet Protocol (&P) accessJ. H,8I H,9I H,@I H,;I H*+I H*,I H**I H*3I H*<I H*>I H*8I H*9I H*@I H*;I H3+I H3,I H3*I H33I H3<I H3>I H38I H39I H3@I H3;I 3GPP* .."+++@=1E J&nteroperability "pecification (&O") for ?i h /ate Pac#et :ata (?/P:) /adio .ccess 'etwor# &nterfaces with "ession 1ontrol in the .ccess 'etwor#J. 3GPP* .."+++;=1E J&nteroperability "pecification (&O") for ?i h /ate Pac#et :ata (?/P:) /adio .ccess 'etwor# &nterfaces with "ession 1ontrol in the Pac#et 1ontrol 7unctionJ. 3GPP* .."++,3=1E J&nteroperability "pecification (&O") for cdma*+++ .ccess 'etwor# &nterfaces C part 3 7eaturesJ. 3GPP T/ 38.;3@E J&mproved 'etwor# 1ontrolled Mobility between 2=3T/.' and 3GPP*AMobile DiM.K /adio Technolo iesJ. 3GPP T" *3.*,8E J"in le /adio Boice 1all 1ontinuity ("/B11)F "ta e *J. 3GPP T" *<.++@E JMobile radio interface 5ayer 3 specificationF 1ore networ# protocolsF "ta e 3J. 3GPP* K."++<*=+E JBoice 1all 1ontinuity between &M" and 1ircuit "witched "ystemJ. 3GPP T" *3.*38E J&ntra=domain connection of /adio .ccess 'etwor# (/.') nodes to multiple 1ore 'etwor# (1') nodesJ. 3GPP T" <3.+>>E J/adio .ccess 'etwor#F :ual Transfer Mode (:TM)F "ta e *J. 3GPP T" *3.*;*E J&M" 1entralised "ervices (&1")F "ta e *J. 3GPP T" *3.**,E J.rchitectural /eGuirementsJ. 3GPP T" *3.<+*E J.rchitecture enhancements for non=3GPP accessesJ. 3GPP T" *<.+,,E JPoint=to=Point (PP) "hort Messa e "ervice ("M") support on mobile radio interfaceJ. 3GPP T" *>.<,3E J3T/.' &u interface /adio .ccess 'etwor# .pplication Part (/.'.P) si nallin J. 3GPP T" <@.+,@E JGeneral Pac#et /adio "ervice (GP/")F 0"" GP/" Protocol (0""GP)J. 3GPP T" *3.+@*E J1all 7orwardin (17) supplementary servicesF "ta e *J. 3GPP* 1."+++>=.E J3pper 5ayer (5ayer 3) "i nalin "tandard for cdma*+++ "pread "pectrum "ystems = /elease .- .ddendum *J. 3GPP T" 38.33,E J2volved 3niversal Terrestrial /adio .ccess (2=3T/.) /adio /esource 1ontrol (//1)J 3GPP T" *<.3+,E J'on=.ccess="tratum ('.") protocol for 2volved Pac#et "ystem (2P")F "ta e 3J. 3GPP T" 38.<,3E J", .pplication Protocol (",.P)J. 3GPP T" **.,>3E JMultimedia Priority "ervicesJ. 3GPP T" **.+89E Jenhanced Multi 5evel Precedence and Pre emption service (eM5PP) = "ta e ,J. 3GPP T" **.+,,E J"ervice accessibilityJ. 3GPP* .."+++@=1EE J&nteroperability "pecification (&O") for ?i h /ate Pac#et :ata (?/P:) /adio .ccess 'etwor# &nterfaces with "ession 1ontrol in the .ccess 'etwor#J.

3GPP

%elease &&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

H<+I H<,I H<*I

3GPP* .."+++;=1E J&nteroperability "pecification (&O") for ?i h /ate Pac#et :ata (?/P:) /adio .ccess 'etwor# &nterfaces with "ession 1ontrol in the Pac#et 1ontrol 7unctionJ. 3GPP T" *3.,<8E JTechnical reali!ation of facsimile roup 3 non=transparentJ. 3GPP T" *3.*>,E J'etwor# sharin F .rchitecture and functional descriptionJ.

5e4i(itio(" &(d &))re6i&tio("

3.1 5e4i(itio("
7or the purposes of the present document- the terms and definitions iven in T/ *,.;+> H,I apply. . term defined in the present document ta#es precedence over the definition of the same term- if any- in T/ *,.;+> H,I. 1xCS: The 3GPP* le acy circuit "witched si nallin system as defined in 3GPP* K."++<*=+ H**I. CS!T &la(: . fla in 5. update reGuest messa e used in 1" fallbac# for MT call to avoid missin pa in in roamin retry. CS!, &la(: . fla in 1M "ervice /eGuest and 5. 3pdate reGuest messa e used in 1" fallbac# for MO calls. Service -)er: "ee T" **.,>3 H38I.

3.2 '))re6i&tio("
7or the purposes of the present document- the abbreviations iven in T/ *,.;+> H,I apply. .n abbreviation defined in the present document ta#es precedence over the definition of the same abbreviation- if any- in T/ *,.;+> H,I. ,(1" &D" 1"MT 1"MO eM5PP &1" M'/7 M'/7=MM2 MP" MT/7 MD: '.M '2.7 "/B11 1ircuit "witched fallbac# &nterwor#in solution 7unction for 3GPP* ,(1". 1ircuit "witched fallbac# Mobile Terminated call. 1ircuit "witched fallbac# Mobile Ori inated call. enhanced Multi 5evel Precedence and Pre emption &M" 1entralised "ervices Mobile "tation 'ot /eachable 7la Mobile 'ot /eachable 7la in MM2 for "M" Multimedia Priority "ervice Mobile Terminatin /oamin 7orwardin Messa e Daitin :ata 'etwor# .ccess Mode 'on=2P" .lert 7la . "in le /adio Boice 1all 1ontinuity

76er&## 5e"cri$tio(

/.1 Ge(er&# ,o("ider&tio("

The 1" fallbac# in 2P" enables the provisionin of voice and other 1"=domain services (e. . 1" 3:& videoA 51"A 3"":) by reuse of 1" infrastructure when the 32 is served by 2=3T/.'. . 1" fallbac# enabled terminal- connected to 2=3T/.' may use G2/.' or 3T/.' to connect to the 1"=domain. This function is only available in case 2=3T/.' covera e is overlapped by either G2/.' covera e or 3T/.' covera e. 1" 7allbac# and &M"=based services shall be able to co=e(ist in the same operatorLs networ#. The &1" architecture as defined in T" *3.*;* H*>I shall be able to co=e(ist with utilisin 1" 7allbac# as the 1" domain in the same operator$s networ#.

3GPP

%elease &&

&*

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

This specification also specifies the architecture reGuired for "M" over "Gs. The MO "M" and MT "M" are si nalled over "Gs and do not cause any 1" 7allbac# to G2/.'A3T/.' /.Ts- and conseGuently does not reGuire any overlapped G2/.'A3T/.' covera e. .dditionally this specification specifies the "M" in MM2 architecture option as described in .nne( 1. The support of "M" over "Gs is mandatory for 32 and MM2 and M"1 supportin 1" fallbac#- whereas 32 and MM2 and M"1 supportin "M" over "Gs are not reGuired to support 1" fallbac#. 'OT2E .n MM2 supportin only "M" over "Gs (i.e. not supportin 1" fallbac#) will either reply with J"M"= onlyJ or reject an &M"& attach.

The support of 1" fallbac# (and to a lesser e(tent "M" over "Gs) can impose some operational constraints on Trac#in .rea boundary plannin and the use of the Jtrac#in area list conceptJ (see T" *3.<+, H*I).

/.2 !e4ere(ce 'rc%itecture

The 1" fallbac# and "M" over "Gs in 2P" function is reali!ed by usin the "Gs interface mechanism between the M"1 "erver and the MM2. The "Gs interface functionality is based on the mechanisms specified for the Gs interface- T" *3.+8+ H3I.

1i#ure -'$+&2 "PS architecture for CS fall ac! and S3S over SGs 'OT2 ,E The MGD is not shown in the fi ure <.*=, since neither 1" fallbac# in 2P" nor "M" over "Gs has any impacts on the 3=plane handlin . 'OT2 *E "G"' and "3 have additional functionality related to &"/ and 1" fallbac#A"M" over "Gs. &f &"/ is not used- this functionality is not reGuired.

/.2.1 !e4ere(ce $oi(t"

S.)E &t is the reference point between the MM2 and M"1 server. The "Gs reference point is used for the mobility mana ement and pa in procedures between 2P" and 1" domain- and is based on the Gs interface procedures. The "Gs reference point is also used for the delivery of both mobile ori inatin and mobile terminatin "M". .dditional procedures for ali nment with the Gs reference point are not precluded. &t is defined in T" *3.<+, H*I with the additional functionality to support &"/ for 1" fallbac#A"M" over "Gs as defined in this specification.

S$E

3GPP

%elease &&

&&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

/.3 *u(ctio(&# e(titie"

/.3.1 UE
The 1" fallbac# capable 32 supports access to 2=3T/.'A2P1 as well as access to the 1" domain over G2/.' andAor 3T/.'. The "M" over "Gs capable 32 supports access to 2=3T/.'A2P1 and may support access to the 1" domain over G2/.' andAor 3T/.'. The support of "M" over "Gs is mandatory for a 32 that supports 1" fallbac#- whereas a 32 that supports "M" over "Gs is not reGuired to support 1" fallbac#. These 32s support the followin additional functionsE = = 1ombined procedures specified in this document for 2P"A&M"& attach- update and detach. 1" fallbac# andAor "M" over "Gs procedures specified in this document for usin 1" domain services.

7rom the 32$s perspective there is no difference whether the MM2 provides "M" via "Gs or by J"M" in MM2J. . 32 usin 1" fallbac# andAor "M" over "Gs supports &"/ accordin to T" *3.<+, H*I. &n particular a 32 deactivates &"/ at reception of 5.3 accept or at reception of combined /.3A5.3 accept response with no &"/ indication. The coe(istence with &M" services for voiceA"M" is defined in clause <.>. There are no other 1" fallbac#A"M" over "Gs &"/=specifics for the 32 compared to &"/ description in T" *3.<+, H*Ii.e. if &"/ is active the 32 can chan e between all re istered areas and /.Ts without performin update si nallin . The 32 listens for pa in on the /.T it is currently camped on. &f the 32 is service user with subscription to 1" domain priority service- the 32$s 3"&M belon s to one of .ccess 1lass that indicates the priority is needed and the 32 shall sets the //1 establishment cause to J?i hPriority.ccessJ as specified in T" 38.33, H33I.

/.3.2 MME
The 1" fallbac# andAor "M" over "Gs enabled MM2 supports the followin additional functionsE = = = = = Multiple P5M's selection for the 1" domain. /.T selection for the 1" domain. :erivin a B5/ number and 5.& from the T.& of the current cell and based on the selected P5M' or the selected /.T for 1" domain- or usin a default B5/ number and 5.&. :eliver the re istered P5M' &: for 1" domain (included in the 5.&) to the e'ode0. 7or 1" fallbac#- eneratin a T.& list such that the 32 has a low chance of Jfallin bac#J to a cell in a 5. different to the derived 5.& (e. . the T.& list boundary should not cross the 5. boundary). .li nment of the T.& list boundary with a 5. boundary can prevent the MM2 from ma#in effective use of the Jtrac#in area listJ concept. To compensate for this- appropriate cell reselection hysteresis may need to be used within the 2=3T/.'.

'OT2E

= = = = =

Maintainin of "Gs association towards M"1AB5/ for 2P"A&M"& attached 32. &nitiatin &M"& or 2P" detach. &nitiatin pa in procedure specified in this document towards e'ode0 when M"1 pa es the 32 for 1" services. "upportin "M" procedures defined in this document. /ejectin 1" 7allbac# call reGuest (e. . due to OMM reasons)

3GPP

%elease &&

&$

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

.n MM2 that supports J"M" in MM2J shall support additional functions specified in .nne( 1- clause 1.<.*. .n MM2 that supports 1" 7allbac# uses the 5.& and the TM"& based '/& as provided by the 32 or the 5.& and a hash value from the &M"& to determine the B5/ number as defined in T" *3.*38 H*3I when multiple M"1AB5/s serve the same 5.&. The '/& distribution or &M"& ?ash table shall have a consistent confi uration in all MM2s in the pool. The same '/& valueAhash valueAfunction is used by "G"' to determine the B5/ number. .n MM2 that supports "M" over "Gs may use the same procedure as for 1" 7allbac#. &n some networ#s- the MM2 may be confi ured to select the M"1AB5/ for J32s confi ured for MT1J with a different load balance to that used for M"1AB5/ selection for other 32s. &n this case the MM2 maintains a separate hashAvalue function for J32s confi ured for MT1J. &f the networ# supports 1"70 priority call handlin - the MM2 supports the followin additional functionsE = 7or pa in messa e received on the "Gs interface with priority indication- the MM2 provides preferential treatment to this messa e and also the subseGuent 1" fallbac# procedure compared to other normal procedures. &f 32 needs to be pa ed- the MM2 sets priority indication on the pa in reGuest to e'ode0. The MM2 also sets priority indication- i.e. J1"70 ?i h PriorityJ- in ",.P messa e to the e'ode0- so that e'ode0 can initiate the 1"70 procedure with priority- as specified in T" 38.<,3 H3>I. 7or a 1"70 reGuest from a service user- the MM2 determines that the 1"70 reGuest needs priority handlin based on the MP" 1" Priority stored in 32$s 2P" subscription. The MM2 provides preferential treatment to this reGuest and also sets priority indication- i.e. J1"70 ?i h PriorityJ- in ",.P messa e to e'ode0 to initiate 1"70 procedure with priority- as specified in T" 38.<,3 H3>I.

/.3.3 MS,
The 1" fallbac# andAor "M" over "Gs enabled M"1 supports the followin additional functionsE = = Maintainin "Gs association towards MM2 for 2P"A&M"& attached 32. "upportin "M" procedures defined in this document.

'OT2 ,E The 1" 7allbac# enabled M"1 can also be enhanced to support &1" as defined in T" *3.*;* H*>I andAor "/B11 as defined in T" *3.*,8 H*+I. 'OT2 *E &n order to speed up the potential 5.3 procedure durin 1" fallbac# the M"1 may be confi ured to lower the freGuency of .uthentication- TM"& reallocation and &dentity chec# for 32s that are 2P"A&M"& attached via the "Gs interface. 'OT2 3E The M"1AB5/ uses the 1"MO fla in 5.3 and 1M service reGuest messa e for 1" 7allbac# statistics. &f the networ# supports a priority call handlin - the M"1 maps priority indication of the &.M messa e to a priority indication of the pa in messa e sent over the "Gs interface.

/.3./ E-UT!'+
The 1" fallbac# enabled 2=3T/.' supports the followin additional functionsE = = = = = 7orwardin pa in reGuest for 1" domain to the 32. :irectin the 32 to the tar et 1" capable cell considerin the re istered P5M' &: and possibly the 5.1 for 1" domain received from the MM2. The confi uration of appropriate cell reselection hysteresis at 5ocation .rea boundaries (or across the whole 2= 3T/.') to reduce Trac#in .rea 3pdate traffic. To facilitate the confi uration of T. boundaries with 5. boundaries- the 2=3T/.' can ather statistics (from the inbound inter=/.T mobility events of all 32s) of the most common 5.s indicated in the //1 si nallin . 1onfi uration to permit the operator to choose the tar et $fallbac#$ /.T and freGuency.

7or "M" over "Gs- no specific 2=3T/.' functionality is reGuired. &f the networ# supports 1"70 priority call handlin - the 2=3T/.' supports the followin additional functionsE

3GPP

%elease &&

&3

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

= =

7or pa in messa e received on ",.P with priority indication- the 2=3T/.' should provide preferential treatment to this reGuest compared to other normal pa in reGuests. 7or 1" fallbac# ",.P messa e with priority indication- i.e. J1"70 ?i h PriorityJ- if 32 is in &:52 mode- the e'ode0 should provide preferential treatment- in allocatin 2=3T/.' radio bearer resources compared to other normal resource reGuests. Dhen 1"70 based on P" handover is employed- the e'ode0 may forward priority indication to the tar et G2/.'A3T/.'.

/.3. SGS+
&f the "G"' supports &"/- "G"' shall follow the rules and procedures described in T" *3.<+, H*I and T" *3.+8+ H3I with the followin additions and clarificationsE = The "G"' shall not send the &"/ activated indication at combined /.3A5.3 procedure.

.n "G"' that supports Gs uses 5.& and the TM"& based '/& as provided by the 32 or 5.& and a hash value from the &M"& to determine the B5/ number as defined in T" *3.*38 H*3I when multiple M"1AB5/s serve the same 5.&. The same '/& valueAhash valueAfunction is used by MM2 to determine the B5/ number.

/.3.6 8SS
&f the 0"" receives indication from the M"1 that the 1" service (1all- 1&"" or 51") was established as a result of 1" fallbac# the 0"" may e. . select to use // 1onnection /elease with /edirect to send the 32 bac# to 2=3T/.' at release of the 1" service. &f the networ# supports &"/- the 1" fallbac# enabled 0"" e(hibits the followin behaviourE = 2ven if the networ# is operatin in 'MO && the 0"" shall forward Gb interface pa in messa es onto the radio interface. The 0"" in a networ# operatin in 'MO && shall not be confi ured to use P011?.

/.3.7 !+S
&f the /'" receives indication from the M"1 that the 1" service (1all- 1&"" or 51") was established as a result of 1" fallbac# the /'" may e. . select to use //1 1onnection /elease with /edirect to send the 32 bac# to 2=3T/.' at release of the 1" service.

/./ ,o(tro# $#&(e

/./.1 MME - MS, Ser6er
SG"'P S,TP 9P L2 L1 MME SG" SG"'P S,TP 9P L2 L1 MS, Ser6er

4e#end2 SGsAP2 T%i" $rotoco# i" u"ed to co((ect &( MME to &( MS, Ser6er )&"ed o( t%e 8SS'P.. Stream Control Transmission Protocol (SCTP)2 T%i" $rotoco# tr&("4er" "i3(&##i(3 me""&3e". 1i#ure -'-'&+&2 SGs 5nterface

3GPP

%elease &&

&-

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

/. ,o-e0i"te(ce 2it% 9MS "er6ice"

. 1" 7allbac# and &M" capable 32 shall follow the procedures for domain selection for 32 ori inatin sessionAcalls accordin to T" *3.**, H*8I $:omain selection for 32 ori inatin sessions A calls$. .n &M" capable 32 which supports "M" over &P networ#s shall follow the procedures for domain selection for 32 ori inatin "M" accordin to T" *3.**, H*8I $:omain selection for 32 ori inatin "M"$.

/.6 Emer3e(c: ,&##"

Dhen 32 is performin 1" fallbac# procedure for Mobile Ori inatin 1all for the purpose of emer ency call- it shall indicate to the MM2 that this 1" fallbac# reGuest is for emer ency purpose. MM2 also indicates to the 2=3T/.' via the appropriate ",=.P messa e that this 1" fallbac# procedure is for emer ency purpose. &f P" handover is initiated2=3T/.' may indicate priority level of the 1" fallbac# to the tar et /.T- as specified in T" *>.<,3 H*;I- in order to prepare radio resource at tar et /.T in appropriate way- e. . priority allocation of the /.0 resource. 'OT2E 2=3T/.' may use the emer ency indication for selectin a particular radio access networ# (*G or 3G) for 1" emer ency handlin .

/.7 ,S*8 Priorit: ,&## ;&(d#i(3

1"70 Priority call handlin ensures that- when G2/.'A3T/.' supports eM5PP service (T" **.+89 H39I)- end=to=end priority handlin is provided for both mobile ori inated 1"70 calls by a service user in 2=3T/.' and for mobile terminated 1"70 call from a service user to a normal or service user in 2=3T/.'. . service user$s 2P" subscription contains an indication of the users 1" domain priority status- i.e. MP" 1" Priority. &f the 32 is subscribed to 1" domain priority- the 32$s 3"&M shall belon to one of .ccess 1lass ,, to ,>. 7or mobile terminated 1" fallbac# calls from a service user- the M"1 provides a priority indication to the MM2 alon with a pa in messa e. The MM2 shall set a priority indication to the e'ode0 when reGuestin the e'ode0 to pa e the 32 if the 32 is idle. 7or mobile ori inated 1" fallbac# calls from a service user in 2=3T/.'- the MM2 determines that the 1"70 reGuest reGuires priority handlin based on the 32$s MP" 1" Priority. 7or both mobile ori inated and mobile terminated 1"70- the MM2 shall also provide priority indication- i.e. J1"70 ?i h PriorityJ- when reGuestin the e'ode0 to e(ecute the 1"70 priority procedure as specified in T" 38.<,3 H3>I. The e'ode0 should handle the pa in messa e with priority and also prioriti!e the subseGuent 1" fallbac# procedure to G2/.'A3T/.' or ,(/TT. &f P" handover to G2/.' or 3T/.' is initiated- 2=3T/.' may forward 1" fallbac# priority indicator to the tar et /.T- as specified in T" *>.<,3 H*;I- in order to prepare radio resource at tar et /.T in appropriate way- e. . priority allocation of the /.0 resource 'OT2 ,E 7or a Mobile Terminatin 1all from a normal user to a service user- no special handlin is reGuired.

/.< ,S "er6ice" %&(d#i(3 i( "$eci4ic c&"e"

/.<.1 SG" $&3i(3 2it%out L'9
&f the "Gs Pa in /eGuest does not contain the 5.&- and if the MM2 can retrieve the "=TM"& associated to the &M"&the MM2 shall temporarily store this M"1AB5/ number and force the 32 to re=attach to the non=2P" services based onE = = &f the 32 is in connected mode- the MM2 shall send a :etach /eGuest (&M"& :etach) to the 32 as described in clause >.3.*F &f the 32 is in idle mode- the MM2 shall send :etach &ndication (5ocal :etach) messa e to the "G"' via "3 interface if &"/ is active. &f the mobile reachable timer is still runnin the MM2 shall pa e the 32 with &M"& and the 1" indicator (for 1"70) or with "=TM"& and the P" indicator (for "M"). .t the reception of 2(tended "ervice /eGuest (for 1"70) or "ervice /eGuest (for "M") from the 32- the MM2 shall not send a "Gs "ervice /eGuest to the M"1AB5/ as it normally would- but instead shall send a :etach /eGuest (&M"& :etach) to the 32 as described in clause >.3.*.

The MM2 shall not send &M"& :etach &ndication messa e to the M"1AB5/ in the above scenarios.

3GPP

%elease &&

&.

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

MM2 shall then wait for the 32 to re=attach to non=2P" services via a Trac#in .rea 3pdate /eGuestF the MM2 shall &M"& attach the 32 to the M"1AB5/ usin the stored M"1AB5/ number. .fter successful &M"& attach- if the pa in timer has not e(pired- the M"1AB5/ shall pa e the 32 a ain usin "Gs Pa in /eGuest with 5.&.

/.<.2 ;&(d#i(3 o4 SG" $&3i(3 2%e( MME c&((ot retrie6e t%e S-TMS9
3pon receivin "Gs Pa in /eGuest- if the MM2 cannot retrieve the "=TM"& associated with &M"&- the MM2 shall pa e the 32 with &M"& and P" indicator to force the 32 to re=attach to 2P" and non=2P" services.

Mo)i#it: M&(&3eme(t
.1 Ge(er&#
The 1" fallbac# and "M" over "Gs in 2P" is reali!ed by usin the "Gs interface mechanism between the M"1 "erver and the MM2. The "M" over "Gs '." procedures are also used for the "M" in MM2 option. The use of the Jpool=areaJ concept as specified in T" *3.*38 H*3I allows to minimi!e the occurrence of M"1 chan e at 1" fallbac#.

.1' T'9 #i"t &(d L'9 &##oc&tio(

7or 1" fallbac#- the fallbac# procedure is li#ely to be faster if the networ# can allocate a 5ocation .rea to the 32 that is the 5. of the overlappin tar et /.T$s covera e. 7or this situation- the MM2 should avoid allocatin T.& lists that span multiple 5ocation .reas of the tar et /.T (which may be contrary to the normal usa e of the Jtrac#in area listJ concept described in T" *3.<+, H*I). This can be achieved byE = = = confi urin the 2=3T/.' cell$s T.& to ta#e into account the 5. boundary of the tar et /.TF the MM2 bein confi ured to #now which T.&s are within which 5.F and the MM2 usin the T.& of the current 2=3T/.' cell to derive the 5.&.

The operator should be able to confi ure the MM2 as to whether it eitherE = = provides normal usa e of the Jtrac#in area listJ concept- orthe T.& list allocation is adjusted- for 1" fallbac# mobiles- to provide JT.& lists that do not span multiple 5.sJ.

The MM2 may use alternative approaches for 5.& and T.& list allocation. &n particular- this is appropriate forE = = the case of "M" over "Gs without overlappin G2/.'A3T/.' covera eF and the case when not all M"1s in the BP5M' support the "Gs interface.

&n these situations- one approach is to confi ure the MM2 to allocate a default (e. . non=broadcast) 5.& which is associated with a B5/ that supports the "Gs interface. &f J"M" in MM2J is used for a 32- then the MM2 shall allocate a non=broadcasted 5.& (not associated with any B5/) and a reserved TM"&- if needed- for that 32.

.2 'tt&c% $rocedure
The attach procedure for the 1" fallbac# and "M" over "Gs in 2P" is reali!ed based on the combined GP/"A&M"& .ttach procedure specified in T" *3.+8+ H3I.

3GPP

%elease &&

&/

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

6"

33" 1. 'tt&c% !e=ue"t

3SC8)4%

7SS

2. Ste$ 3 to "te$ 16 o4 t%e 'tt&c% $rocedure "$eci4ied i( TS 23./01 3. 5eri6e VL! (um)er /. Loc&tio( U$d&te !e=ue"t . ,re&te SG" &""oci&tio( 6. Loc&tio( u$d&te i( ,S dom&i( 7. Loc&tio( U$d&te 'cce$t <. Ste$ 17 to "te$ 26 o4 t%e 'tt&c% $rocedure "$eci4ied i( TS 23./01 9. P&3i(3 !e=ue"t

1i#ure .'$+&2 Attach Procedure ,) The 32 initiates the attach procedure by the transmission of an .ttach /eGuest (parameters as specified in T" *3.<+, H*I includin the .ttach Type- old 5.& and Mobile "tation 1lassmar# *) messa e to the MM2. The .ttach Type indicates that the 32 reGuests a combined 2P"A&M"& attach and informs the networ# that the 32 is capable and confi ured to use 1" fallbac# andAor "M" over "Gs. &f the 32 needs "M" service but not 1"70the 32 shall include an J"M"=onlyJ indication in the combined 2P"A&M"& .ttach /eGuest. "ee clause >.8. *) "tep 3 to step ,8 of the 2P" .ttach procedure are performed as specified in T" *3.<+, H*I. :urin initial re istration with an ?""- if the MM2 is enabled to use J"M" in MM2J- the MM2 indicates to the ?"" that it supports the "M" in MM2 capability and includes the MM2 identity to be used for MT="M" delivery. 'OT2 ,E Dhether there is a need for indicatin the MM2$s capability to the ?"" is to be determined by sta e 3. &f the MM2 is re istered with an ?"" for P" services but has no valid "M" subscriber data and decides to use J"M" in MM2J for that 32 then the MM2 re=re isters with ?"" to obtain "M" subscriber data and to provide the ?"" with the MM2 identity to be used for MT="M" delivery. The MM2 may decide based on stored subscriber data whether it is possible to provide J"M" in MM2J for the 32 and therefore useful to initiate re= re istration with ?"" for J"M" in MM2J. "uch stored subscriber data are J"M" in MM2 "upportJ and "M" subscriber data that are not updated with ?"". &f the ?"" accepts to re ister the MM2 identity as an M"1 identity for terminatin "M" services then the ?"" cancels any re istered M"1. &f the 32 subscribes the eM5PP (T" **.+89 H39I) service in the 1" domain- the 32 2P" subscription received from ?"" contains MP" 1" Priority which indicates the 32$s 1" domain priority status. 3) &f the .ttach /eGuest messa e includes an .ttach Type indicatin that the 32 reGuests a combined 2P"A&M"& attach- the MM2 allocates a new 5.& for the 32 as described in clause >.,.. The MM2 does not perform any re istrations with a B5/- i.e. it s#ips steps < to 9 and no "Gs association is created. = &f the subscriber data indicate by the 'etwor# .ccess Mode information that the subscription has no 1" subscriber dataF or if the MM2 provides J"M" in MM2J for the 32 as described in clause 1.<.*. &f the re istration with a B5/ is reGuired and multiple P5M's are available for the 1" domain- the MM2 performs selection of the P5M' for 1" domain based on the P5M' &: contained in the current T.&- old 5.& and operator selection policies on preferred /.T for 1" domain. &f the tar et networ# is a shared G2/.'- the

3GPP

%elease &&

&(

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

MM2 shall also ta#e into account the 32 capability of support or non=support of G2/.' networ# sharin when selectin the P5M' for the 1" domain as specified in T" *3.*>, H<*I. The P5M' selected for 1" should be the same that is used for this 32 as a tar et P5M' for P" handovers or for any other mobility procedures related to 1"70. The MM2 may ta#e any access restrictions provided by the ?"" into account- if the networ# is usin separate location areas for G2/.' and 3T/.' cells. The selected P5M' &: is included in the newly allocated 5.& which is sent to M"1AB5/ in step < and in .ttach .ccept to the 32. The MM2 derives a B5/ number based on the newly allocated 5.& and the TM"& based '/& as provided by the 32 or on the newly allocated 5.& and an &M"& hash function defined in T" *3.*38 H*3I. The MM2 starts the location update procedure towards the new M"1AB5/ upon receipt of the subscriber data from the ?"" in step *). This operation mar#s the M" as 2P"=attached in the B5/. <) The MM2 sends a 5ocation 3pdate /eGuest (new 5.&- &M"&- MM2 name- 5ocation 3pdate Type) messa e to the B5/. MM2 name is a 7N:' strin . >) The B5/ creates an association with the MM2 by storin MM2 name. 8) The B5/ performs the normal subscription chec#s for 1" and if all chec#s are successful performs 5ocation 3pdatin procedure in 1" domain. 9) The B5/ responds with 5ocation 3pdate .ccept (B5/ TM"&) to the MM2. @) The 2P" .ttach procedure is completed by performin step ,9 to step *8 as specified in T" *3.<+, H*I. .ttach .ccept messa e includes the parameters as specified in T" *3.<+, H*IE B5/ TM"& and 5.& as allocated in step 3 above. The e(istence of 5.& and B5/ TM"& indicates successful attach to 1" domain. &f the 32 reGuests combined 2P"A&M"& .ttach /eGuest without the J"M"=onlyJ indication- and if the networ# supports "Gs procedures only for "M" or the networ# decided to provide J"M" in MM2J for the 32- the MM2 shall indicate in the .ttach .ccept messa e that the &M"& attach is for J"M"=onlyJ. Dhen the networ# accepts a combined 2P"A&M"& attach without limitin to J"M"=onlyJ- the networ# may provide a J1"70 'ot PreferredJ indication to the 32. &f the 32 reGuests combined 2P"A&M"& .ttach /eGuest with the J"M"=onlyJ indication- and if the networ# supports "Gs procedures only for "M" or if it supports 1"70 and "M" over "Gs or the networ# decided to provide J"M" in MM2J for the 32- the MM2 shall indicate in the .ttach .ccept messa e that the &M"& attach is for J"M"=onlyJ. &f the MM2 provides J"M" in MM2J for the 32- then the TM"& and 5.& are provided as specified in clause 1.<.*. The networ# provides the J"M"=onlyJ or J1"70 'ot PreferredJ indications based on locally confi ured operator policies based on e. . roamin a reement. The 32 behaviour upon receivin such indications is described in T" *3.**, H*8I. ;) &f the B5/ has updated the "Gs association and if a pa in timer is still runnin for a MT service for this 32the B5/ shall repeat "Gs Pa in /eGuest towards the updated "Gs association. 'OT2 *E The case of unsuccessful attach to 1" domain is documented in sta e 3 specifications- ta#in into account reachability for 1" services of 32s that have the user preference to prioriti!e voice over data services and are not confi uredAsupportin to use &M" voice services.

.3 5et&c% $rocedure
.3.1 UE-i(iti&ted 5et&c% $rocedure
The 32=initiated :etach procedure for the 1" fallbac# and "M" over "Gs in 2P" is reali!ed based on the M"=&nitiated :etach Procedure specified in T" *3.+8+ H3I.

3GPP

%elease && 33"

&0

3GPP TS $3'$($ )&&'$'* ($*&$+*,) 7SS

6" 1. 5et&c% !e=ue"t

3SC8)4%

2. Ste$ 2 to "te$ 10 o4 t%e UE-i(iti&ted 5et&c% $rocedure 4or E-UT!'+ &" "$eci4ied i( TS 23./01 3&. 9MS9 5et&c% 9(dic&tio( 3). EPS 5et&c% 9(dic&tio( . 5et&c% 'cce$t /. !emo6e SG" &""oci&tio(

6. Ste$ 12 to "te$ 1/ o4 t%e UE-i(iti&ted 5et&c% $rocedure 4or E-UT!'+ &" "$eci4ied i( TS 23./01

1i#ure .'3'&+&2 6"+initiated 9etach Procedure ,) The 32 initiates the detach procedure by the transmission of a :etach /eGuest (parameters as specified in T" *3.<+, H*I- :etach Type) messa e to the MM2. :etach Type indicates which type of detach is to be performed- i.e.- &M"& :etach only- 2P" :etach only or combined 2P" and &M"& :etach. *) The 32=initiated :etach procedure for 2=3T/.' is continued as specified in T" *3.<+, H*I. 3a) &f the detach type indicates J&M"& :etach onlyJ or Jcombined 2P" and &M"& :etachJ- the MM2 sends an &M"& :etach &ndication (&M"&) messa e to the M"1AB5/. 3b)&f the detach type indicates J2P" :etach onlyJ- the MM2 sends an 2P" :etach &ndication (&M"&) messa e to the M"1AB5/. <) The M"1AB5/ removes the association with the MM2. >) The MM2 sends a :etach .ccept messa e to the 32 as specified in T" *3.<+, H*I. Dhen the 32 receives the :etach .ccept messa e and the :etach Type indicated J2P" :etach onlyJ in step ,- the 32 disables 2=3T/.'selects an appropriate G2/.' or 3T/.' cell. 8) The 32=initiated :etach procedure for 2=3T/.' is completed with step ,* to step ,< as specified in T" *3.<+, H*I. &f no "Gs association e(ists for the 32 steps 3a=< are not e(ecuted.

.3.1' UE-i(iti&ted 5et&c% $rocedure 4or GE!'+1UT!'+ 2it% 9S! &cti6&ted

Dhen &"/ is activated- 32 initiates detach procedure as specified in T" *3.<+, H*I- clause >.3.@.*.*. The procedure is performed with the e(ception as followsE = &n step <- the "G"' sends :etach 'otification (1ause- :etach type) messa e to the associated MM2. 1ause indicates J&M"& :etach onlyJ when 32 performs &M"& :etach only procedure. Otherwise- 1ause indicates Jcomplete detachJ- and :etach type indicates JP" detachJ in case of 32=initiated G/P" :etach only procedureor indicates Jcombined P"A1" detachJ in case of 32=initiated combined GP/"A&M"& detach procedure. &f Gs association e(ists- the "G"' also sends an &M"& :etach &ndication (&M"&) messa e or a GP/" :etach &ndication (&M"&) messa e to the B5/ dependin on the detach type sent by the 32 as specified in T" *3.+8+ H3Iclause 8.8.,. Dhen the MM2 receives the :etach 'otification messa e- it sends an &M"& :etach &ndication (&M"&) messa e to the M"1AB5/ if the cause indicates J&M"& :etach onlyJ or the detach type indicates Jcombined P"A1" detachJ- or sends an 2P" :etach &ndication (&M"&) messa e to the M"1AB5/ if the detach type indicates JP" detachJ.

3GPP

%elease &&

&,

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

&f 1ause indicates J&M"& :etach onlyJ- the MM2 shall not deactivate &"/ and steps > to ; shall be s#ipped.

.3.2 MME-i(iti&ted 5et&c% $rocedure

The MM2=initiated detach procedure for the 1" fallbac# and "M" over "Gs in 2P" is reali!ed based on the "G"'= &nitiated :etach Procedure specified in T" *3.+8+ H3I.
6" SGS: 33" 3SC8)4% 7SS

1. Ste$ 1 to "te$ 10 o4 MME-i(iti&ted det&c% &" "$eci4ied i( TS 23./01 2&. EPS 5et&c% 9(dic&tio( 2). 9MS9 5et&c% 9(dic&tio( 3. !emo6e SG" &""oci&tio( /. Ste$ 11 to "te$1/ o4 MME-i(iti&ted det&c% &" "$eci4ied i( TS 23./01 . 5et&c% !e=ue"t

1i#ure .'3'$+&2 33"+initiated 9etach Procedure ,) The MM2=initiated :etach procedure is performed as specified in T" *3.<+, H*I. *a) &f 2P" service is not allowed for the 32 the MM2 sends an 2P" :etach &ndication (&M"& detach from 2P" service) messa e to the M"1AB5/. *b) If the UE is required to be IMSI detached, the MM2 sends an &M"& :etach &ndication (&M"&) messa e to the M"1AB5/. 3) The M"1AB5/ removes the association with the MM2. <) The MM2=initiated :etach procedure is completed with step ,, to step ,< as specified in T" *3.<+, H*I. >) &f &"/ is activated in "G"' and the 32 is 2MM combined procedures capable- when "G"' receives :etach &ndication messa e sent from MM2 with J:etach TypeJ &2 that indicates J5ocal :etachJ or :elete 0earer /eGuest messa e from "GD for last P:P 1onte(t- then the "G"' shall send :etach /eGuest (&M"& :etach) to the 32. The "G"' turns on J2MM 1ombined 32 Daitin 7la J. Dhen "G"' may have the capability to use this fla and how the "G"' uses this fla is described in clause >.>. &f no "Gs association e(ists for the 32 steps *a=3 are not e(ecuted.

.3.2' SGS+-i(iti&ted 5et&c% $rocedure 2it% 9S! &cti6&ted

Dhen &"/ is activated- "G"' initiates detach procedure as specified in T" *3.<+, H*I- clause >.3.@.3.. The procedure is performed with the e(ception as followsE = &n step <- the "G"' sends :etach 'otification (1ause- :etach type) messa e to the associated MM2. &f this detach is local to the "G"' (e. . implicit detach)- 1ause indicates local detach. Otherwise- 1ause indicates complete detach- and :etach type indicates JP" detachJ. &f Gs association e(ists- the "G"' also sends a GP/" :etach &ndication (&M"&) messa e to the B5/ as specified in T" *3.+8+ H3I- clause 8.8.*.,.. Dhen the MM2 receives the :etach 'otification messa e- it sends an 2P" :etach &ndication (&M"&) messa e to the M"1AB5/ if the detach type indicates JP" detachJ. &f the cause indicates local detach- the MM2 shall not remove "Gs association.

3GPP

%elease &&

$*

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

&f 1ause indicates local detach- the MM2 deactivates &"/ and steps > to ; shall be s#ipped.

.3.3 ;SS-i(iti&ted 5et&c% $rocedure

The ?""=initiated detach procedure for the 1" fallbac# and "M" over "Gs in 2P" is reali!ed based on the ?5/= &nitiated :etach Procedure specified in T" *3.+8+ H3I.
6" 33" 3SC8)4% 7SS

1. Ste$ 1& to "te$ 7) o4 ;SS-i(iti&ted det&c% &" "$eci4ied i( TS 23./01 2. EPS 5et&c% 9(dic&tio( 3. !emo6e SG" &""oci&tio( /. Ste$ <& to "te$ 10& o4 ;SS-i(iti&ted det&c% &" "$eci4ied i( TS 23./01

1i#ure .'3'3+&2 7SS+initiated 9etach Procedure ,) The ?""=initiated :etach procedure is performed as specified in T" *3.<+, H*I. *) The MM2 sends an 2P" :etach &ndication (&M"&) messa e to the M"1AB5/. 3) The M"1AB5/ removes the association with the MM2. <) The ?""=initiated :etach procedure is completed with step @a to step ,+a as specified in T" *3.<+, H*I. &f no "Gs association e(ists for the 32 steps *=3 are not e(ecuted.

.3./ 'dmi(i"tr&tio( o4 t%e MME - MS,1VL! '""oci&tio(

The MM2 = M"1AB5/ association is created at the followin occasionsE = = 1ombined 2P"A &M"& attach in clause >.*. 1ombined T.A5. 3pdate in clause >.<.

The association is updated on the followin occasionsE = Dhen an 32 chan es MM2.

The MM2 = M"1AB5/ association is removed at the followin occasionsE = = = = = 32=initiated :etach in clause >.3.,. MM2 initiated :etach in clause >.3.*. ?"" initiated :etach in clause >.3.3. Gs association establishment in *A3G- see T" *3.+8+ H3I. M"1AB5/ receives a 5. update via the . or &u interface.

3GPP

%elease &&

$&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

./ T'1L' U$d&te $rocedure

./.0 Ge(er&#
Dhen a 1" fallbac# andAor "M" over "Gs capable 32 is 2P"A&M"& attached- it initiates the combined T.A5. procedure based on the tri ers specified in T" *3.<+, H*I. Dhen a 1" fallbac# andAor "M" over "Gs capable 32 is not 2P"A&M"& attached- it may initiate a combined T.A5. procedure in order to use 1" 7allbac# or "M" over "Gs services.

./.1 ,om)i(ed T'1L' U$d&te Procedure

'OT2 ,E The combined T.A5. 3pdate procedure for the 1" fallbac# and "M" over "Gs in 2P" is reali!ed based on the combined /.A5. 3pdate procedure specified in T" *3.+8+ H3I.
6" 1. UE determi(e" to $er4orm T'U new 33" old 33" 3SC8)4% 7SS

2. T'U !e=ue"t 3. Ste$ / to "te$ 19 o4 T'U $rocedure &" "$eci4ied i( TS 23./01 /. Loc&tio( U$d&te !e=ue"t

. Loc&tio( u$d&te i( ,S dom&i( 6. Loc&tio( U$d&te 'cce$t 7. T'U 'cce$t <. T'U ,om$#ete 9. P&3i(3 !e=ue"t

1i#ure .'-'&+&2 Com ined TA 8 4A 6pdate Procedure ,) The 32 detects a chan e to a new T. by discoverin that its current T.& is not in the list of T.&s that the 32 re istered with the networ# or the 32$s T&' indicates the need for a T.3 when re=selectin to 2=3T/.'. The combined T.A5. 3pdate Procedure is also performed in order to re=establish the "Gs association. *) The 32 initiates the T.3 procedure by sendin a T.3 /eGuest (parameters as specified in T" *3.<+, H*I includin the 3pdate Type- old 5.& and Mobile "tation 1lassmar# *) messa e to the MM2. The 3pdate Type indicates that this is a combined Trac#in .reaA5ocation .rea 3pdate /eGuest or a combined Trac#in .reaA5ocation .rea 3pdate with &M"& attach /eGuest. &f the 32 needs "M" service but not 1"70- the 32 shall include an J"M"=onlyJ indication in the combined T.A5. 3pdate procedure- see clause >.8. 3) "tep < to step ,; of the 2P" T.3 procedure are performed as specified in T" *3.<+, H*I. :urin initial re istration with an ?""- if the MM2 is enabled to use J"M" in MM2J- the MM2 indicates to the ?"" that it supports the "M" in MM2 capability and includes the MM2 identity to be used for MT="M" delivery. 'OT2 *E Dhether there is a need for indicatin the MM2$s capability to the ?"" is to be determined by sta e 3. &f the MM2 is re istered with an ?"" for P" services but has no valid "M" subscriber data and decides to use J"M" in MM2J for that 32 then the MM2 re=re isters with ?"" to obtain "M" subscriber data and to provide the ?"" with the MM2 identity to be used for MT="M" delivery. The MM2 may decide based on stored

3GPP

%elease &&

$$

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

subscriber data whether it is possible to provide J"M" in MM2J for the 32 and therefore useful to initiate re= re istration with ?"" for J"M" in MM2J. "uch stored subscriber data are J"M" in MM2 "upportJ and "M" subscriber data that are not updated with ?"". &f the ?"" accepts to re ister the MM2 identity as an M"1 identity for terminatin "M" services then the ?"" cancels any re istered M"1. The MM2 does not perform any re istrations with a B5/- i.e. it s#ips steps < to 8 and no "Gs association is created- if the subscriber data indicate by the 'etwor# .ccess Mode information that the subscription has no 1" subscriber data or if the MM2 provides J"M" in MM2J for the 32 as described in clause 1.<.*. <) &f multiple P5M's are available for 1" domain- the MM2 performs selection of the P5M' for 1" domain based on current T.&- old 5.& and operator selection policies on preferred /.T for 1" domain. &f the tar et networ# is a shared G2/.'- the MM2 shall also ta#e into account the 32 capability of support or non=support of G2/.' networ# sharin when selectin the P5M' for the 1" domain as specified in T" *3.*>, H<*I. The P5M' selected for 1" should be the same that is used for this 32 as a tar et P5M' for P" handovers or for any other mobility procedures related to 1"70. The MM2 may ta#e any access restrictions provided by the ?"" into account- if the networ# is usin separate location areas for G2/.' and 3T/.' cells. The selected P5M' &: is included in the newly allocated 5.&. &f the association has to be established or if the 5. chan ed- the new MM2 sends a 5ocation 3pdate /eGuest (new 5.&- &M"&- MM2 name- 5ocation 3pdate Type) messa e to the B5/. The MM2 retrieves the correspondin B5/ number from the determined 5.&. &f multiple M"1AB5/s serve this 5.&- the TM"& based '/& as provided by the 32 or an &M"& hash function is used to retrieve the B5/ number for the 5.& as defined in T" *3.*38 H*3I. The 5ocation 3pdate Type shall indicate normal location update. The MM2 name is a 7N:' strin . >) The B5/ performs the normal subscription chec#s for 1" and if all chec#s are successful performs 5ocation 3pdate procedure in 1" domain. 8) The B5/ responds with 5ocation 3pdate .ccept (B5/ TM"&) to the MM2. 9) The MM2 sends a T.3 .ccept (parameters as specified in T" *3.<+, H*I- 5.&- B5/ TM"&) messa e to the 32. The B5/ TM"& is optional if the B5/ has not chan ed. 5.& is determined in step < above. The presence of the 5.& indicates to the 32 that it is &M"& attached. &f the 32 reGuests combined T.A5. 3pdate /eGuest without the J"M"=onlyJ indication- and if the networ# supports "Gs for "M" only- the networ# shall perform the &M"& attach and the MM2 shall indicate in the T.3 .ccept messa e that the &M"& attach is for J"M"=onlyJ. &f the 32 reGuests combined T.A5. 3pdate (or combined T.A5. 3pdate with &M"& attach) without the J"M"= onlyJ indication- and if the networ# supports "Gs procedures only for "M" or the networ# decided to provide J"M" in MM2J for the 32- the MM2 shall indicate J"M"=onlyJ in the T.3 .ccept messa e. ?owever- if the networ# supports 1"70 and "M" over "Gs and accepts a combined T.A5. 3pdate procedure but does not indicate J"M"=onlyJ- the MM2 may provide a J1"70 'ot PreferredJ indication to the 32. &f the 32 reGuests combined T.A5. 3pdate (or combined T.A5. 3pdate with &M"& attach) with the J"M"= onlyJ indication- and if the networ# only supports "Gs procedures for "M" or if it supports 1"70 and "M" over "Gs or if the networ# decided to provide J"M" in MM2J for the 32- the MM2 shall indicate in the T.3 .ccept messa e that the combined T.A5. 3pdate procedure is for J"M"=onlyJ. &f the MM2 provides J"M" in MM2J for the 32- then the TM"& and 5.& are provided as specified in clause 1.<.*. The networ# provides the J"M"=onlyJ or J1"70 'ot PreferredJ indications based on locally confi ured operator policies based on e. . roamin a reement. The 32 behaviour upon receivin such indications is described in T" *3.**, H*8I. @) The 32 may send a T.3 complete messa e as specified in T" *3.<+, H*I for the T.3 procedure. ;) &f the B5/ has updated the "Gs association and if a pa in timer is still runnin for a MT service for this 32the B5/ shall repeat "Gs Pa in /eGuest towards the updated "Gs association.

3GPP

%elease &&

$3

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

./.2 Periodic T' &(d L' U$d&te Procedure

Dhen the 32 is camped on 2=3T/.'- periodic 5. updates shall not be performed- but periodic T. updates shall be performed. &n this case- an "Gs association is established and the M"1AB5/ shall disable implicit detach for 2P"= attached 32s and instead rely on the MM2 to receive periodic T. updates. Dhen a periodic T. update is not received in the MM2- the MM2 clears the PP7. The lac# of periodic T. update may be caused by reselection or handover to G2/.'A3T/.' when &"/ is active. To ensure 1" pa in can reach the 2P"A&M"& attached 32- the 32 shall perform combined /.A5. update in 'MO & or 5.3 in 'MO && when the periodic T.3 timer e(pires and the 32 is in G2/.'A3T/.' (or ne(t returns to covera e in G2/.'A3T/.') and &"/ is active. &n addition- when a periodic T. update is not received in the MM2- the MM2 may implicitly detach the 32 as specified in T" *3.<+, H*I. This MM2 implicit detach does not affect any "G"' attach status. .t an implicit detach- the MM2 also releases the "Gs association with the M"1AB5/. The M"1 continues to maintain the re istered 5. for the 32. The M"1 chan es to supervise 5. updates and pa es in the still re istered 5. when mobile terminated services arrive. Dhen the 32 camps on G2/.'A3T/.' it may perform combined /.A5. updates. The combined /.A5. update procedures and the conditions for their usa e are described in T" *3.+8+ H3I.

./.3 +o(-EPS '#ert $rocedure

The M"1AB5/ may reGuest an MM2 to report activity from a specific 32. &n this case- the M"1AB5/ shall send a "Gs.P .lert /eGuest (&M"&) messa e to the MM2 where the 32 is currently 2P"=attached. 3pon reception of the "Gs.P .lert /eGuest (&M"&) messa e- the MM2 shall set '2.7 ('on=2P" .lert 7la ). &f '2.7 is set for an 32- the MM2 shall inform the M"1AB5/ when the ne(t activity from that 32 (and the 32 is both &M"&= and 2P" attached) is detected- and shall clear '2.7. &f the activity detected by the MM2 leads to a procedure towards the M"1AB5/- the MM2 shall just follow this procedure. &f the activity detected by the MM2 does not lead to any procedure towards the M"1AB5/- the MM2 shall send an 32 .ctivity &ndication (&M"&) messa e towards the M"1AB5/.

././ Void

. 9d#e Mode Si3(&##i(3 !eductio(

&n relation with 1"70 andAor "M" over "Gs- when &"/ is activated- the 32 follows re ular &"/ behaviour. &t may reselect between 2=3T/.' and G2/.'A3T/.' without a need to update the 1'. Dhen a mobile terminated service arrives- the M"1AB5/ sends a pa in messa e via "Gs to the MM2. The MM2 pa es in the T.(s) re istered for the 32- and- the MM2 uses the "3 interface to reGuest the "G"' (i.e. the "G"' that has an &"/ relation with the MM2 for that 32) to pa e the 32 in the re istered /.. Dhen the 32 is already connected with the MM2- the MM2 forwards the pa in reGuest only to the 32 via the established si nallin connection. Dhen the 32 is &M" re istered for voice service- even if the 32 is confi ured for 1"70 or "M" over "Gs- it may need to i nore &"/ activation based on the conditions for &"/ activationAde=activation for 32s re istered for &M" voice service as defined in T" *3.<+, H*I. . 32 that supports 1"70 andAor "M" over "Gs includes the J2MM combined procedures capabilityJ indication as part of the JM" 'etwor# 1apabilityJ in the .ttach- /.3 or combined /.3A5.3 /eGuest messa e- if the 32 supports 1"70 service or "M" over "Gs. "G"' stores the J2MM combined procedures capabilityJ indication for &"/ operation as part of the stored JM" 'etwor# 1apabilityJ. &f the 32 does not support 1"70 or "M" over "Gs- it shall not include the J2MM combined procedures capabilityJ indication in the .ttach- /.3 or combined /.3A5.3 /eGuest messa e to "G"'. &"/ remains activated until the 32 performs a combined /.3A5.3 procedure (e. . a 32 in 'MO & moves to a new /. or 5. or the periodic T.3 timer e(pires while the 32 is in 'MO & of G2/.'A3T/.') or separate 5.3 procedure (e. . a 32 moves to a different 5. in 'MO && or the periodic T.3 timer e(pires while the 32 is in 'MO &&

3GPP

%elease &&

$-

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

of G2/.'A3T/.'). 'ormal re=selection between re istered /.AT.(s) does not cause &"/ deactivated condition. Dhen the 32 needs to perform a combined /.3A5.3- the "G"' chec#s the J2MM combined procedures capabilityJ bit in M" 'etwor# 1apability and if it indicates that 1"70 andAor "M" over "Gs is supported then the "G"' deactivates &"/ by not indicatin &"/ activated in the combined /.3 .ccept messa e- which is a re ular &"/ functionality as specified in T" *3.<+, H*I. "o an "G"' in a 1"70A"M" over "Gs confi uration never indicates &"/ activated in combined /.3 procedures for a 32 that supports 1"70A"M" over "Gs. .n "G"' with &"/ capability in a 1"70A"M" over "Gs confi uration shall always maintain &"/ by indicatin &"/ .ctivated in Periodic /.3 .ccept for a 32 that supports 1"70A"M" over "Gs if the "G"' has the status that &"/ is activated for the 32. .fter a combined /.A5. update procedure- the M"1 pa es via Gs for mobile terminated services. Dhen Gs is not used- the M"1AB5/ pa es in the 5. via &uA. for mobile terminated services. &f &"/ is deactivated and the 32 re=selects to 2=3T/.' with the T&' indicatin JP=TM"&J- it initiates a T.3 procedure- which is a re ular &"/ functionality as specified in T" *3.<+, H*I- and &"/ can be activated a ain. The 32 that supports 1" fallbac#A"M" over "Gs shall perform this T.3 procedure as a combined T.A5. 3pdate Procedure. &n case of the detach procedure for 2=3T/.' when &"/ is activated- the MM2 notifies the associated "G"' with indicatin detach cause (i.e. local detach or complete detach) as specified in clause >.3.,- >.3.*- >.3.3 and T" *3.<+, H*I e(cept 32=initiated &M"& detach only procedure. &n case of the detach procedure for G2/.'A3T/.' when &"/ is activated- the "G"' sends an &M"& or G/P" :etach indication messa e to the B5/ dependin on the detach type sent by the 32 as specified in T" *3.+8+ H3I- clause 8.8.,and notifies the associated MM2 with indicatin detach cause (i.e. local detach- complete detach or &M"& detach only) and detach type (i.e. P" detach or combined P"A1" detach) in case of complete detach- and the MM2 sends &M"& :etach &ndication or 2P" :etach &ndication messa e to the M"1AB5/ accordin ly- which is specified in clause >.3.,. and >.3.*.. Dhen the MM2 receives a "Gs pa in for 1" service- if &"/ is activated and the mobile reachable timer has e(pired but the &mplicit :etach timer has not e(pired- the MM2 shall not notify the M"1AB5/ that the 32 is unreachable via "Gs and instead shall pa e the 32 via "3 interface. Dhen implicit detach timer e(pires in the MM2- the MM2 shall send 2P" :etach &ndication messa e. . The "G"' in 'MO & confi uration with &"/ capability shall support the J2MM combined 32 Daitin 7la J. The J2MM 1ombined 32 Daitin 7la J shall be turned on if "G"' sends :etach /eGuest (&M"& :etach) to the 32 as specified in clause >.3.*. &f J2MM 1ombined 32 Daitin 7la J is turned on in the "G"'- then the "G"' shall behave as followsE = = = = &f the "G"' receives Periodic /.3 from the 32- the "G"' shall send :etach /eGuest (&M"& :etach) to the 32. &f the "G"' receives 1ombined /.3 from the 32- the "G"' shall continue the procedure as specified in T" *3.+8+ H3I. &f the "G"' receives "ervice /eGuest from the 32- the "G"' handles the "ervice /eGuest normally and shall send :etach /eGuest (&M"& :etach) to the 32. The "G"' shall turn off the J2MM 1ombined 32 Daitin 7la J if the "G"' receives 1ombined /.3 from the 32.

The MM2 should not activate &"/ if J"M" in MM2J for the 32 is used.

.6 Mo)i#it: M&(&3eme(t 4or SMS o6er SG" o(#: UE"

32s that need "M" service but not 1"70 indicate this specific condition with the J"M"=onlyJ indication in the 2P"A&M"& .ttach /eGuest and combined T.A5. update procedures. This allows an operator to deploy the "Gs for "M" delivery over 5T2 only without the need for 1"70 support. &n addition- this allows the MM2 to use a dedicated al orithm for the selection of the M"1 that supports those 32s. .n MM2 that supports J"M" in MM2J may directly handle "M" services for the 32 under the conditions described in clause 1.<.*.

3GPP

%elease &&

$.

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

'OT2E

"M" delivery via "Gs does not cause the terminal to fallbac# to the 1"=capable networ#. &t is possible that only certain M"1s in the networ# (one in minimum) are confi ured to support "Gs when the networ# only supports "M" and no other (1") services via "Gs. ?owever such a minimal confi uration can cause inter=M"1 location updates to be performed at every movement intoAout of 2=3T/.' covera e.

Mo)i#e 7ri3i(&ti(3 ,&##

6.1 Ge(er&#
This clause describes the mobile ori inatin call procedures for the 1" 7allbac# in 2P".

6.2 Mo)i#e 7ri3i(&ti(3 c&## i( 'cti6e Mode - PS ;7 "u$$orted

This flow may be e(ecuted when the e'ode0 #nows that both the 32 and the networ# support P" ?O- in the normal case. 1lause 8.8 describes the procedure when the procedure is rejected by the MM2.
UE1MS e+ode8 8SS1!+S MME MS, SGS+ Ser6i(3 G> P-G>1 GGS+

1&. E0te(ded Ser6ice !e=ue"t 1). S1-'P !e=ue"t me""&3e 2it% ,S *&##)&cB i(dic&tor 1c. S1-'P !e"$o("e me""&3e 2. 7$tio(&# Me&"ureme(t !e$ort So#icit&tio( 3&. PS ;7 &" "$eci4ied i( 23./01 @2A ($re$&r&tio( $%&"e &(d "t&rt o4 e0ecutio( $%&"e) 3). Su"$e(d 3c. U$d&te 8e&rer(")

/&. Loc&tio( 're& U$d&te /). ,M Ser6ice !e=ue"t /). '19u-c" me""&3e (2it% ,M Ser6ice !e=ue"t) . ,M Ser6ice !e?ect . ,M Ser6ice !e?ect
If the MSC is changed

Loc&tio( 're& U$d&te or ,om)i(ed !'1L' U$d&te

6. ,S c&## e"t&)#i"%me(t $rocedure 7. PS ;7 &" "$eci4ied i( 23./01 @2A (co(ti(u&tio( o4 e0ecutio( $%&"e)

1i#ure /'$+&2 CS Call %e;uest in "+6T%A:< Call in G"%A:86T%A: 'OT2 ,E :TM is not mandatory for 1" 7allbac# to wor# and is not lin#ed to P" ?O. ,a. The 32 sends an 2(tended "ervice /eGuest for mobile ori inatin 1" fallbac# to MM2. 2(tended "ervice /eGuest messa e is encapsulated in //1 and ",=.P messa es. The 32 only transmits this reGuest if it is attached to 1" domain (with a combined 2P"A&M"& .ttach) and can not initiate an &M" voice session (because

3GPP

%elease &&

$/

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

e. . the 32 is not &M" re istered or &M" voice services are not supported by the servin &P=1.'- home P5M' or 32). ,b. The MM2 sends an ",=.P 32 1onte(t Modification /eGuest (1" 7allbac# &ndicator- 5.&) messa e to e'ode0. This messa e indicates to the e'ode0 that the 32 should be moved to 3T/.'AG2/.'. The re istered P5M' for 1" domain is identified by the P5M' &: included in the 5.&- which is allocated by the MM2. &f MM2 determines the 1" 7allbac# procedure needs priority handlin based on MP" 1" Priority in the 32$s 2P" subscription- it also sets priority indication- i.e. J1"70 ?i h PriorityJ- in the ",.P messa e to the e'ode0 as specified in T" 38.<,3 H3>I. ,c. The e'ode0 shall reply with ",=.P 32 1onte(t Modification /esponse messa e. *. The e'ode0 may optionally solicit a measurement report from the 32 to determine the tar et G2/.'A3T/.' cell to which P" handover will be performed. 'OT2E 0ased on operator policy- the priority indicator received in step,b may be used by e'ode0 to decide whether to continue 1" 7allbac# procedures with P" ?O- i.e. step3a- or to initiate radio release procedure to redirect the 32 to *GA3G 1ircuit "witch as specified in clause 8.3.

3a. The e'ode0 tri ers P" handover to a G2/.'A3T/.' nei hbour cell by sendin a ?andover /eGuired messa e to the MM2. The e'ode0 selects the tar et P" handover cell considerin the P5M' &: and possibly the 5.1 for 1" domain provided by the MM2 in step ,b. &f the e'0 is a ?e'0- the ?e'0 should perform step 3 throu h step 8 of clause 8.3 instead of P" ?O if the ?e'0 detects that the 32 has only 5&P. P:' 1onnections. 1"70 will not be completed successfully when P" ?O is performed if the 32 has only 5&P. P:' 1onnections as P" ?O would result in the MM2 detachin the 32. 'OT2 *E 7or details how the ?e'ode0 determines whether a P:' connection is a 5&P. P:' connection see T" *3.<+, H*I- clause <.3.,8. &n the followin an inter=/.T handover from 2=3T/.' to 3T/.' or G2/.' as specified in T" *3.<+, H*I be ins. The e'ode0 indicates in the "ource /'1 to Tar et /'1 Transparent container that P" handover was tri ered due to 1"70. The e'ode0 also indicates whether 1"70 was tri ered for emer ency or priority call handlin purpose. &f the networ# supports a priority call handlin - the e'ode0 may forward the priority indication to the tar et G2/.'A3T/.' in the "ource to Tar et Transparent 1ontainer- and the tar et G2/.'A3T/.' allocates radio bearer resources ta#in received priority indication ta#e into account. .s part of this handover- the 32 receives a ?O from 2=3T/.' 1ommand and tries to connect to a cell in the tar et /.T. The ?O from 2=3T/.' 1ommand may contain a 1" 7allbac# &ndicator which indicates to 32 that the handover is tri ered due to a 1" fallbac# reGuest. &f the ?O from 2=3T/.' 1ommand contains a 1" 7allbac# &ndicator and the 32 fails to establish connection to the tar et /.T- then the 32 considers that 1" fallbac# has failed. "ervice /eGuest procedure is considered to be successfully completed when P" ?andover procedure is completed successfully. 'OT2 3E :urin the P" ?O the "G"' does not create a Gs association with the M"1AB5/. 'OT2 <E "ervice /eGuest procedure supervision timer shall be sufficiently lon considerin the optional measurement reportin at step *. Dhen the 32 arrives at the tar et cell- if the tar et /.T is 3T/.'- the 32 establishes the radio si nallin connection by sendin an //1 &nitial :irect Transfer messa e as specified in T" *>.33, H9I that contains a '." messa e. The 1' :omain &ndicator is set to J1"J in the &nitial :irect Transfer messa e. &f the tar et /.T is G2/.' .AGb modeE The 32 establishes a radio si nallin connection by usin the procedures specified in T" <<.+,@ H<I (i.e. 32 reGuests and is assi ned a dedicated channel where it sends a ".0M containin a '." messa e to the 0"" and the 0"" responds by sendin a 3.). 3pon receivin the ".0M (containin the '." messa e) the 0"" sends a 1OMP52T2 5.O2/ 3 &'7O/M.T&O' messa e (containin the '." messa e) to the M"1 which indicates 1" resources have been allocated in the G2/.' cell. &f both the 32 and the tar et cell support enhanced 1" establishment in :TM (indicated by G2/.' system information included within the ?O from 2=3T/.' 1ommand) a // connection may be established while in pac#et transfer mode without release of the pac#et resources- see T" <3.+>> H*<I. .fter the establishment of the main si nallin lin# as described in T" <<.+,@ H<I the 32 enters either :ual Transfer Mode or :edicated Mode.

3GPP

%elease &&

$(

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

3b. &f the tar et /.T is G2/.' and the 32 has entered :edicated Mode- the 32 starts the "uspend procedure (see T" <<.+,@ H<I) unless both the 32 and the Tar et cell support :TM in which case T07 re=establishment may be performed. 3c. . GnAGp="G"' that receives the "uspend messa e from the 32 follows the "uspend procedure specified in T" *3.+8+ H3I- clause ,8.*.,.,.,. .n "<="G"' that receives the "uspend messa e from the 32 follows the "uspend procedure specified in T" *3.+8+ H3I. The "<="G"' deactivates G0/ bearers towards "=GD and P=GD(s) by initiatin M"=and "G"' &nitiated 0earer :eactivation procedure as specified in T" *3.+8+ H3I- and starts the preservation and suspension of non=G0/ bearers by sendin "uspend 'otification messa e to the "=GD. The "=GD releases all /'1 related information (address and T2&:s) for the 32 if :irect Tunnel is established- and sends "uspend 'otification messa e to the P=GD(s). The "G"' stores in the 32 conte(t that 32 is in suspended status. .ll the preserved non=G0/ bearers are mar#ed as suspended status in the "=GD and P=GD(s). The P=GD should discard pac#ets if received for the suspended 32. <a. &f the 5. of the new cell is different from the one stored in the 32 (which is received as part of 1ombined .ttachAT.3 procedure in 2=3T/.')- the 32 shall initiate a 5ocation .rea 3pdate procedure as followsE = if the networ# is operatin in 'MO=& ('etwor# Modes of Operation)- the 32 shall initiate a separate 5ocation .rea 3pdate before initiatin the /.3 procedure instead of a 1ombined /.A5. 3pdate procedure (to speed up the 1"70 procedure)F or if the networ# is operatin in 'MO=&&- the 32 shall initiate a 5ocation .rea 3pdate before initiatin the /.3 procedure reGuired for P" handover.

Dhen the 32 initiates a 5ocation .rea 3pdate the 32 shall set the Jfollow=on reGuestJ fla in the 5.3 /eGuest in order to indicate to the M"1 not to release the &uA. connection after the 5.3 procedure completion. The 32 shall indicate to the tar et M"1 that this is an ori inatin call establishment as a result of 1"70 by includin the J1"MOJ fla . 7urther the 32 performs any /outin .rea 3pdate procedure as specified by T" *3.+8+ H3I. The 32 may initiate a 5ocation .rea 3pdate procedure immediately when the 32 is handed over to the tar et cell i.e. before the 32 receives e. . 5.& or 'MO information as part of the /.' Mobility &nformation. <b. The 32 sends a 1M "ervice /eGuest to the M"1. The 32 shall indicate to the M"1 that this is an ori inatin call establishment as a result of 1"70 by includin the J1"MOJ fla . >. &f the 32 is not re istered in the M"1 servin the *GA3G tar et cell or the 32 is not allowed in the 5.- the M"1 shall reject the 1M service reGuest- if implicit location update is not performed. The 1M "ervice /eject shall tri er the 32 to perform a 5ocation .rea 3pdate or a 1ombined /.A5. 3pdate procedure as specified in T" *3.+8+ H3I for the different 'etwor# Modes of Operation ('MO). 8. The 32 initiates the 1" call establishment procedure and the 32 shall include the 1"MO fla in the 1M "ervice /eGuest to the M"1. 9. The 32 performs any remainin steps of the inter=/.T handover from 2=3T/.' to 3T/.' or G2/.' as specified in T" *3.<+, H*I. &f the 32 remains on 3T/.'AG2/.' after the 1" voice call is terminated the 32 performs normal mobility mana ement procedures as defined in T" *3.+8+ H3I and T" *<.++@ H*,I.

6.3 Mo)i#e 7ri3i(&ti(3 c&## i( 'cti6e Mode C +o PS ;7 "u$$ort

This procedure is e(ecuted when P" ?O is not supported- in the normal case. 1lause 8.8 describes the procedure when the procedure is rejected by the MM2.

3GPP

%elease &&

$0

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

UE1 MS

e+ode8

8SS1!+S

MME

MS,

SG>1PG>

SGS+

1&. +'S E0te(ded Ser6ice !e=ue"t 1). S1-'P UE ,o(te0t Modi4ic&tio( !e=ue"t 2it% ,S *&##)&cB i(dic&tor 1c. S1-'P UE ,o(te0t Modi4ic&tio( !e"$o("e me""&3e 2. 7$tio(&# Me&"ureme(t !e$ort So#icit&tio( 3&. +',,, . 3), 3c !!, co((ectio( re#e&"e /. S1-'P- S1 UE ,o(te0t !e#e&"e !e=ue"t . S1 UE ,o(te0t !e#e&"e 6. UE c%&(3e" !'T t%e( L' U$d&te or !' U$d&te or L'U &(d !'U 7&. Su"$e(d ("ee 23.060) 7). Su"$e(d !e=ue"t 1 !e"$o("e <. U$d&te )e&rer(") 9. ,M Ser6ice !e=ue"t 10&. Ser6ice !e?ect 10). Loc&tio( 're& U$d&te 10c. ,S M7 c&##
If the MSC is changed

9. '19u-c" me""&3e (2it% ,M Ser6ice !e=ue"t)

11. !outi(3 're& U$d&te or ,om)i(ed !'1L' U$d&te

1i#ure /'3+&2 CS Call %e;uest in "+6T%A:< Call in G"%A:86T%A: without PS 7= ,a. The 32 sends an 2(tended "ervice /eGuest for mobile ori inatin 1" fallbac# to the MM2. 2(tended "ervice /eGuest messa e is encapsulated in //1 and ",=.P messa es. The 32 only transmits this reGuest if it is attached to 1" domain (with a combined 2P"A&M"& .ttach) and can not initiate an &M" voice session (because e. . the 32 is not &M" re istered or &M" voice services are not supported by the servin &P=1.'- home P5M' or 32). ,b. The MM2 sends an ",=.P 32 1onte(t Modification /eGuest (1" 7allbac# &ndicator- 5.&) messa e to e'ode0. This messa e indicates to the e'ode0 that the 32 should be moved to 3T/.'AG2/.'. The re istered P5M' for 1" domain is identified by the P5M' &: included in the 5.&- which is allocated by the MM2. &f MM2 determines the 1" 7allbac# procedure needs priority handlin based on MP" 1" Priority in the 32$s 2P" subscription- it sets priority indication- i.e. J1"70 ?i h PriorityJ- in the ",.P messa e to the e'ode0 as specified in T" 38.<,3 H3>I. ,c. The e'ode0 shall reply with ",=.P 32 1onte(t Modification /esponse messa e. *. The e'ode0 may optionally solicit a measurement report from the 32 to determine the tar et G2/.'A3T/.' cell to which the redirection procedure will be performed. T'e net/ork 0er&orm) one o& )te0) $a or $b or $c. 3a. &f the 32 and networ# support inter=/.T cell chan e order to G2/.' and the tar et cell is G2/.'E The e'ode0 can tri er an inter=/.T cell chan e order (optionally with '.11) to a G2/.' nei hbour cell by sendin an //1 messa e to the 32. The inter=/.T cell chan e order may contain a 1" 7allbac# &ndicator which indicates to 32 that the cell chan e order is tri ered due to a 1" fallbac# reGuest. &f the inter=/.T cell chan e order contains a 1" 7allbac# &ndicator and the 32 fails to establish connection to the tar et /.T- then

3GPP

%elease &&

$,

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

the 32 considers that 1" fallbac# has failed. "ervice /eGuest procedure is considered to be successfully completed when cell chan e order procedure is completed successfully. The e'ode0 selects the tar et cell considerin the P5M' &: and possibly the 5.1 for 1" domain provided by the MM2 in step ,b for 11OA'.11 purpose. 3b. &f the 32 or the networ# does not support inter=/.T P" handover from 2=3T/.' to G2/.'A3T/.' nor inter=/.T cell chan e order to G2/.' or the networ# does not wish to use these proceduresE The e'ode0 can tri er //1 connection release with redirection to G2/.' or 3T/.'. 'OT2 ,E Dhen performin 1" 7allbac# to 3T/.'- the //1 connection release with redirection can be optimi!ed if both the 32 and 3T/.' support the optional J:eferred measurement control readin J feature specified in T" *>.33, H9I. 3c. &f the 32 and networ# support J//1 connection release with redirection and Multi 1ell "ystem &nformation to G2/.'A3T/.'JE The e'ode0 can tri er //1 connection release with redirection to G2/.' or 3T/.' and include one or more physical cell identities and their associated "ystem &nformation. &n step 3b or step 3c- the e'ode0 includes the redirection control information into the //1 1onnection /elease messa e based on the P5M' &: for 1" domain and the /.TAfreGuency priority confi ured in the e'ode0- so that the 32 re istered P5M' for 1" domain can be preferably selected. 'OT2 *E "ervice /eGuest procedure supervision timer shall be sufficiently lon considerin the optional measurement reportin at step *. <. The e'ode0 sends an ",=.P 32 1onte(t /elease /eGuest messa e to the MM2. &f the tar et cell is G2/.' and either the tar et cell or the 32 does not support :TM the messa e includes an indication that the 32 is not available for the P" service. >. The MM2 releases the 32 1onte(t in the e'ode0 as well as all e'ode0 related information in the "=GD as specified in T" *3.<+, H*I. &n case the 1ause indicates that //1 was released due to abnormal conditions- e. . radio lin# failure- the MM2 suspends the 2P" bearers ("tep @). T'e -" 0er&orm) one o& )te0) 6a or 6b or 6c and T1" 0er&orm) )te0 6d. 8a. ("tep 8a is performed if step 3a- 1ell 1han e Order to G2/.'- was performed) The 32 moves to the new cell in G2/.'. The 32 uses the '.11 information andAor the broadcast "ystem &nformation and when it has all of the necessary information to access the G2/.' cell- establishes a radio si nallin connection. 8b. ("tep 8b is performed if step 3b- //1 release with redirection- was performed). The 32 moves to the tar et /.T- identifies a suitable cell preferably of the same P5M' as received in 5.& &2 of combined 2P"A&M"& .ttachAT.3 .ccept messa e- receives the broadcast "ystem &nformation and when it has the necessary information to access G2/.'A3T/.'- establishes a radio si nallin connection. 8c. ("tep 8c is performed if step 3c- //1 connection release with redirection and Multi 1ell "ystem &nformationwas performed). The 32 moves to the tar et /.T and identifies a suitable cell preferably of the same P5M' as received in 5.& &2 of combined 2P"A&M"& .ttachAT.3 .ccept messa e. The 32 uses the Multi 1ell "ystem &nformation andAor the broadcast "ystem &nformation and when it has all of the necessary information to access G2/.'A3T/.'the 32 establishes the radio si nallin connection. 8d. Dhen the 32 arrives at the tar et cell- if tar et /.T is 3T/.'E The 32 establishes the radio si nallin connection by sendin an //1 &nitial :irect Transfer messa e as specified in T" *>.33, H9I that contains a '." messa e. The 1' :omain &ndicator is set to J1"J in the &nitial :irect Transfer messa e. &f the e'ode0 indicated 32 to o to G2/.' in step 3 but the 32 finally camps on an 3T/.' cell of the same /. that the 32 is re istered with and &"/ active- the 32 shall locally deactivate &"/.

3GPP

%elease &&

3*

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

&f tar et /.T is G2/.' .AGb modeE The 32 establishes a radio si nallin connection by usin the procedures specified in T" <<.+,@ H<I (i.e. 32 reGuests and is assi ned a dedicated channel where it sends a ".0M containin a '." messa e to the 0"" and the 0"" responds by sendin a 3.). 3pon receivin the ".0M (containin the '." messa e) the 0"" sends a 1OMP52T2 5.O2/ 3 &'7O/M.T&O' messa e (containin the '." messa e) to the M"1 which indicates 1" resources have been allocated in the G2/.' cell. .fter the establishment of the main si nallin lin# as described in T" <<.+,@ H<I the 32 enters either :ual Transfer Mode or :edicated Mode. &f the 5. of the new cell is different from the one stored in the 32- the 32 (which is received as part of 1ombined .ttachAT.3 procedure in 2=3T/.') shall initiate a 5ocation .rea 3pdate re ardless of the different 'etwor# Modes of Operation ('MO). The 32 shall set the Jfollow=on reGuestJ fla in the 5.3 /eGuest in order to indicate to the M"1 not to release the &uA. connection after the 5.3 procedure is complete. The 32 shall indicate to the tar et M"1 that this is an ori inatin call establishment as a result of 1"70 by includin the 1"MO fla . 7urther the 32 performs any /outin .rea 3pdate procedure as specified by T" *3.+8+ H3I. &n 'MO & a 1"70 32 shall perform separate 5.3 with Jfollow=on reGuestJ fla and J1"MOJ fla - and /.3 procedures instead of a 1ombined /.A5. 3pdate procedure to speed up the 1"70 procedure. 9. &f the tar et /.T is G2/.' and :TM is not supported or the 32 does not support :TM- the 32 starts the "uspend procedure specified in T" *3.+8+ H3I. This tri ers the (servin ) "G"' to send a "uspend /eGuest (T55&- /.&) messa e to the old 1' node identified by the /.& and T55&. &f &"/ is not active- the /.& and T55& refer to an MM2. The MM2 returns a "uspend /esponse to the "G"' even thou h the G3T& cannot be derived from the P=TM"& and /.& pair. &f &"/ is active- the /.& and T55& refer to the old "<="G"'- &n this case- if the servin "G"' is different from the old "G"' which has &"/ association with MM2- the old "G"' returns a "uspend /esponse to the servin "G"'. 'OT2 3E 7or step 9b and @- the inter="G"' suspendin procedure of &"/ active case are not shown in the fi ure. @. &f the ",=.P 32 1onte(t /elease /eGuest messa e- received from the e'ode0 in step <- indicates that the 32 is not available for the P" service in the tar et cell- the MM2 deactivates G0/ bearers towards "=GD and P= GD(s) by initiatin MM2=initiated :edicated 0earer :eactivation procedure as specified in T" *3.<+, H*I- and starts the preservation and suspension of non=G0/ bearers by sendin "uspend 'otification messa e to the "= GD. &f &"/ is active- the (old) "<="G"' deactivates G0/ bearers towards "=GD and P=GD(s) by initiatin M"=and "G"' initiated 0earer :eactivation procedure as specified in T" *3.+8+ H3I- and starts the preservation and suspension of non=G0/ bearers by sendin the "uspend 'otification messa e to the "=GD- which is all tri ered by the "uspend procedure in step 9. The "=GD sends "uspend 'otification messa e to the P=GD(s) when it receives the "uspend 'otification messa e from MM2 or "<="G"'. &f the "=GD receives two "uspend 'otification messa es for the same 32- it i nores the second one e(cept for sendin response. The MM2 stores in the 32 conte(t that 32 is suspended status. &f &"/ is active- the (old) "<="G"' stores in the 32 conte(t that 32 is in suspended status. .ll the preserved non=G0/ bearers are mar#ed as suspended status in the "=GD and P=GD(s). The P=GD should discard pac#ets if received for the suspended 32. 'OT2 <E "tep @ can not be tri ered by the "uspend procedure since the full G3T& can not be derived from the P= TM"& and /.& included in the "uspend /eGuest messa e. ;. The 32 continues with the MO call setup procedure with sendin 1M "ervice /eGuest. The 32 shall indicate to the M"1 that this is an ori inatin call establishment as a result of 1"70 by includin the J1"MOJ fla . ,+a. &f the 32 is not re istered in the M"1 servin the *GA3G cell or the 32 is not allowed in the 5.- the M"1 shall reject the service reGuest- if implicit location update is not performed. ,+b. . 32 detectin that the M"1 rejected the service reGuest shall perform the 5ocation .rea 3pdate or a 1ombined /.A5. procedure accordin to e(istin G2/.' or 3T/.' procedures as specified in T" *3.+8+ H3I for the different 'etwor# Modes of Operation ('MO). ,+c. The 32 initiates the 1" call establishment procedure and the 32 shall include the 1"MO fla in the 1M "ervice /eGuest to the M"1. ,,. .fter the 1" voice call is terminated and if the 32 is in G2/.' and P" services are suspended- then the 32 shall resume P" services as specified in T" *3.+8+ H3I. . GnAGp ="G"' will follow T" *3.+8+ H3I to resume the P:P 1onte(t(s)F in addition- the GnAGp "G"' sends a 3pdate P:P 1onte(t /eGuest messa e to the GG"'AP=GD- the GG"'AP=GD resumes the P:P 1onte(t(s). .n "< "G"' will follow T" *3.+8+ H3I to resume the bearers- and informs the "=GD and P=GD(s) to resume the suspended bearers. &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.

3GPP

%elease &&

3&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

The MM2 will in addition inform "=GD and P=GD(s) to resume the suspended bearers. /esumin the suspended bearers in the "=GD and in the P=GD should be done by implicit resume usin the Modify 0earer reGuest messa e if it is tri ered by the procedure in operation- e. . /.3- T.3 or "ervice /eGuest. The "=GD is aware of the suspend state of the bearers and will forward the Modify 0earer reGuest to the P=GD. 2(plicit resume usin the /esume 'otification messa e should be used in cases when Modify 0earer /eGuest is not tri ered by the procedure in operation. &f the 32 remains on 3T/.'AG2/.' after the 1" voice call is terminated the 32 performs normal mobility mana ement procedures as defined in T" *3.+8+ H3I and T" *<.++@ H*,I.

6./ Mo)i#e 7ri3i(&ti(3 c&## i( 9d#e Mode

Mobile Ori inatin call in &dle Mode procedure is specified by reusin the Mobile Ori inatin 1all in .ctive mode procedures as specified in clauses 8.* and 8.3 with 2(tended "ervice /eGuest for mobile ori inatin 1" fallbac# to the MM2 where the messa es ",=.P 32 1onte(t Modification /eGuest and /esponse are replaced by ",=.P &nitial 32 1onte(t /eGuest and /esponse. The 5.& is included in the ",=.P &nitial 32 1onte(t /eGuest messa e and sent to the e'ode0. The 32 is transited to 21M=1O''21T2: mode by followin the applicable procedures specified in T" *3.<+, H*I. 'OT2E 2ven in case both the 32 and the networ# support P" ?O- the e'ode0 may choose to use a different inter=/.T mobility procedure.

&f 32 has only 5&P. P:' connection and the cell accessed by the 32 does not lin# to the 5=GD where the 32 had the 5&P. P:' 1onnection- the MM2 shall reject the 2(tended "ervice /eGuest with a reason code which results in the 32 selectin G2/.' or 3T/.' as specified in T" *<.3+, H3<I. &f the 32 is service user with subscription to 1" domain priority service- the 32 will set the //1 establishment cause to J?i hPriority.ccessJ based on the access class as specified in T" 38.33, H33I. &f the networ# supports a priority call handlin - the MM2 determines that the 2(tended "ervice /eGuest reGuires priority handlin of 1" 7allbac# based on the J?i hPriority.ccessJ establishment cause forwarded by e'ode0 to the MM2 andAor MP" 1" Priority in the 32$s 2P" subscription. .ccordin to operator policy- the MM2 may use MP" 1" Priority in the 32$s 2P" subscription to verify the priority handlin of the 1" 7allbac# procedure. &f MM2 decides to perform 1" 7allbac# with priority- it sets priority indication- i.e. J1"70 ?i h PriorityJ- in the ",= .P &nitial 32 1onte(t /eGuest messa e to the e'ode0 as specified in T" 38.<,3 H3>I. The e'ode0 allocates radio bearer resources to the 32 preferentially compared to other normal calls.

6. !etur(i(3 )&cB to E-UT!'+

Once 1" service ends in 1" domain- e(istin mechanisms can be used to move the 32 to 2=3T/.'- no specific 1" 7allbac# mechanisms are needed. :urin the release of an // connection the M"1 should indicate to G2/.'A3T/.' that the // connection (for call or 1&"" or 51") was established as a result of 1" fallbac#. G2/.' and 3T/.' may use the indication to determine which of the e(istin mechanisms that should be used to move the 32 to 2=3T/.'. Dhen the 32 moves to 2=3T/.'- if the 2P" service was suspended durin the 1" service- it is resumed accordin to the procedure shown in the fi ure 8.>=, below.

3GPP

%elease &&

3$

3GPP TS $3'$($ )&&'$'* ($*&$+*,) S-G>1 P-G>

UE1MS

e+ode8

MME

1. T'U !e=ue"t me""&3e 2. !e"ume1Modi4: 8e&rer"

3. ;&(d#i(3 T'U !e=ue"t me""&3e

1i#ure /'.+&2 %esume Procedure returnin# from CS fall ac! no PS 7= ,. The 32 sends a T.3 /eGuest messa e- to the MM2. *. &f the 32 conte(t in the MM2 indicates that 32 is in suspended status- the MM2 informs the "=GD and P= GD(s) to re=activate the 2P" bearers for the 32. &f the procedure tri ered by the '." messa e in step , activates Modify 0earer /eGuest messa e to the "=GDthis messa e should be used as an implicit resume. The "=GD is aware of the suspend state of the bearers and shall forward the Modify 0earer reGuest to the P=GD. The P=GD and "=GD shall clear the suspend state and confirm with Modify 0earer response to the MM2. 3. The '." messa e is processed accordin ly.

6.6 Mo)i#e 7ri3i(&ted or Mo)i#e termi(&ted c&## re?ected ): t%e MME

The MM2 may reject an 2(tended "ervice /eGuest either for mobile ori inated or mobile terminated 1"70. The followin procedure covers this scenario.

3GPP

%elease &&

33

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

UE 1MS

EUT!'+

MME

8SS 1 !+S

MS,

S -G> 1 P -G>

1. UE i" com)i(ed EPS19MS9 'tt&c%ed 2 . UE deci"io( to $er4orm M7 ,S*8 c&## or &cce$t & ,S dom&i( $&3e me""&3e 3. E0te(ded Ser6ice !e=ue"t

/. Ser6ice !e?ect . UE . Se#ect" GE!'+1UT!'+ ,S 5om&i(

6. S1 UE ,o(te0t !e#e&"e ,omm&(d

7. E-UT!'+ tri33er" !!, co((ectio( re#e&"e <. S1 UE ,o(te0t !e#e&"e ,om$#ete

1i#ure /'/+&2 CS1> 3= or 3T call< rejected y 33" ,. 32 is combined 2P"A&M"& attached. *. 32 ma#es a decision to perform a mobile ori inated 1" call or accepts 1" pa in for the 1" 7allbac# to G2/.'A3T/.'. 3. 32 sends an 2(tended "ervice /eGuest for mobile ori inatin Amobile terminatin 1" fallbac# to the MM2. <. &f the MM2 decides to reject the 2(tended "ervice /eGuest- the MM2 sends a "ervice /eject messa e to the 32. "teps > C @ are e(ecuted when "ervice /eject is sent with a reason code which results in the 32 selectin G2/.' or 3T/.'- as specified in T" *<.3+, H3<I. >. The 32 selects G2/.' or 3T/.' 1" :omain without waitin for //1 /elease. 8. The MM2 releases ", by sendin the ", 32 1onte(t /elease 1ommand (1ause) messa e to the e'ode0. 1ause value indicates that release is tri ered due to 1" 7allbac# procedure. 9. &f the //1 connection is not already released- the 2=3T/.' sends a //1 1onnection /elease messa e to the 32. @. The 2=3T/.' confirms the ", /elease by returnin an ", 32 1onte(t /elease 1omplete messa e to the MM2.

3GPP

%elease &&

3-

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

Mo)i#e Termi(&ti(3 ,&##

7.1 Ge(er&#
This clause describes the mobile terminatin call procedures for the 1" 7allbac# in 2P". The M"1 handles the timers- Gueuin and retransmission for sendin the "Gs.P=P.G&'G=/2N32"T messa e on the "Gs interface in the same way that it handles the sendin of a P.G&'G messa e on the . or &u interface. .s a conseGuence- the MM2 and (if &"/ is active) the "G"' shall not implement local retransmission schemes for this pa in .

7.2 Mo)i#e Termi(&ti(3 c&## i( id#e mode

The procedure for Mobile Terminatin 1all in idle mode is illustrated in fi ure 9.*=,- in the normal case. 1lause 8.8 describes the procedure when the procedure is rejected by the MM2.
6" e:ode> 33" %:C8>SC 3SC )4% 7SS G+3SC 1. 9'M

2. S!9 $rocedure i( TS 23.01< 3. 9'M /. P&3i(3 !e=ue"t 6. P&3i(3 . P&3i(3

7&. E0te(ded Ser6ice !e=ue"t

7&. Ser6ice !e=ue"t

7). 9(iti&# UE ,o(te0t Setu$

<. '4ter t%e UE co(te0t "etu$ t%e $rocedure co(ti(ue" &" de"cri)ed t%e &cti6e mode mo)i#e termi(&ted c&## $rocedure" de"cri)ed i( ,#&u"e 7.3 &(d 7./. 94 t%e e+ode8 B(o2" t%&t PS ;7 i" "u$$orted t%e $rocedure i( c#&u"e 7.3 DMo)i#e Termi(&ti(3 c&## i( 'cti6e Mode - PS ;7 "u$$ortedE m&: )e &$$#ied 4rom "te$ 2, i( ,#&u"e 7.3, &(d o(2&rd" 94 t%e e+ode8 B(o2" t%&t PS ;7 i" (ot "u$$orted t%e $rocedure i( c#&u"e 7./ DMo)i#e Termi(&ti(3 c&## i( 'cti6e Mode C +o PS ;7 "u$$ortE "%&## )e &$$#ied 4rom "te$ 2 i( ,#&u"e 7./, &(d o(2&rd"

1i#ure ('$+&2 3o ile Terminatin# Call in idle mode ,. G=M"1 receives &.M. *. G=M"1 retrieves routin information of the terminatin 32 by "end /outin &nfo procedures as specified in T" *3.+,@ H>I. 3. G=M"1 sends &.M to the M"1 on the terminatin side as specified in T" *3.+,@ H>I. <. The MM2 receives a Pa in /eGuest (&M"&- B5/ TM"&- 5ocation &nformation- priority indication) messa e from the M"1 over a "Gs interface. &M"& is used by the MM2 to find the "=TM"&. &f the TM"& and the 5.& are received from the M"1AB5/- the "=TM"& is used as the pa in address on the radio interface. &f the TM"& is not received from the M"1AB5/- the &M"& shall be used as the pa in address on the radio interface. &f location information is reliably #nown by MM2 (i.e. MM2 stores the list of T.s)- the MM2 shall pa e the 32 in all the

3GPP

%elease &&

3.

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

T.s. &f the MM2 does not have a stored T. list for the 32- the MM2 may use the location information received from the M"1 to pa e the 32. 'OT2 ,E The case when 5.& is not received from M"1AB5/ and the case when "=TM"& is not available are further described in clause <.@. 'OT2 *E This procedure ta#es place before step 3- immediately after M"1 receives M.PPP/' from ?""- if pre= pa in is deployed. &f the MM2 receives a Pa in /eGuest messa e for an 32 which is considered as detach for 2P" services- the MM2 sends the Pa in reject messa e to the M"1 with an appropriate cause value. This rejection tri ers the M"1 to pa e the 32 over . or &u=cs interface. 'OT2 3E &n case of a 1" fallbac# capable 32 in 'MO &&- there is a case where- for e(ample- the MM2 releases the "Gs association due to the 32 idle mode mobility while the B5/ still maintains the "Gs association. &f the MM2 receives Pa in /eGuest with priority indication- e. . eM5PP priority- from the M"1- then the MM2 processes this messa e and also the subseGuent 1" 7allbac# procedure preferentially compared to other normal procedures. >. &f the MM2 did not return an J"M"=onlyJ indication to the 32 durin .ttach or 1ombined T.A5. 3pdate procedures- the MM2 sends a Pa in (as specified in T" *3.<+, H*I) messa e to each e'ode0. The Pa in messa e includes a suitable 32 &dentity (i.e. "=TM"& or &M"&) and a 1' :omain &ndicator that indicates which domain (1" or P") initiated the pa in messa e. &n this case it shall be set to J1"J by the MM2. &f the MM2 returned the J"M"=onlyJ indication to the 32 durin .ttach or 1ombined T.A5. 3pdate procedures- the MM2 shall not send the pa in to the e'ode0s and sends Pa in /eject towards M"1 to stop 1" Pa in procedure and this 1"70 procedure stops. &f the MM2 received Pa in /eGuest with priority indication in step<- the Pa in messa e also includes priority indication. 8. The radio resource part of the pa in procedure ta#es place. The messa e contains a suitable 32 &dentity (i.e. "=TM"& or &M"&) and a 1' :omain indicator. &f e'ode0 received Pa in with Priority &ndication in step >- it performs the pa in procedure preferentially compared to other normal pa in . 9a. The 32 establishes an //1 connection and sends an 2(tended "ervice /eGuest for mobile terminatin 1" fallbac# to MM2. The 32 indicates its "=TM"& in the //1 si nallin . The 2(tended "ervice /eGuest messa e is encapsulated in //1 and ",=.P messa es. The MM2 sends the "Gs "ervice /eGuest messa e to the M"1 containin an indication that the 32 was in idle mode (and hence- for e(ample- that the 32 has not received any 1allin 5ine &dentification information). /eceipt of the "Gs "ervice /eGuest messa e stops the M"1 retransmittin the "Gs interface Pa in messa e. 'OT2 <E &n order to avoid the callin party e(periencin a potentially lon period of silence- the M"1 may use the "Gs "ervice /eGuest messa e containin the idle mode indication as a tri er to inform the callin party that the call is pro ressin . &f the MM2 had received pa in reGuest with Priority &ndication in step< and receives subseGuent 2(tended "ervice /eGuest in "tep 9a- it detects this messa e is the response to the priority 1" 7allbac# procedure initiated in step>. &n this case- the MM2 processes this messa e with priority and set the priority indication- i.e. J1"70 ?i h PriorityJ- in step9b as specified in T" 38.<,3 H3>I. &f 32 has only 5&P. P:' connection and the cell accessed by the 32 does not lin# to the 5=GD where the 32 had the 5&P. P:' 1onnection- the MM2 shall reject the 2(tended "ervice /eGuest with a reason code which results in the 32 selectin G2/.' or 3T/.' as specified in T" *<.3+, H3<I. 9b. MM2 sends ",=.PE &nitial 32 1onte(t "etup (32 capabilities- 1" 7allbac# &ndicator- 5.& and other parameters specified in T" *3.<+, H*I) to indicate the e'ode0 to move the 32 to 3T/.'AG2/.'. The re istered P5M' for 1" domain is identified by the P5M' &: included in the 5.&- which is allocated by the MM2. 9c. The e'ode0 shall reply with ",=.PE &nitial 32 1onte(t "etup /esponse messa e. @a. &f the e'ode0 #nows that both the 32 and the networ# support P" handoverE The information flow may continue as described in clause 9.3 JMobile Terminatin call in .ctive Mode = P" ?O supportedJ from step *- in clause 9.3- and onwards.

3GPP

%elease &&

3/

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

&f the e'ode0 #nows that either the 32 or the networ# does not support P" handoverE The information flow shall continue as described in clause 9.< JMobile Terminatin call in .ctive Mode C 'o P" ?O supportJ from step *- in clause 9.<- and onwards.

'OT2 >E 2ven in case both the 32 and the networ# support P" ?O- the e'ode0 may choose to use a different inter=/.T mobility procedure.

7.3 Mo)i#e Termi(&ti(3 c&## i( 'cti6e Mode - PS ;7 "u$$orted

This flow may be e(ecuted when the e'ode0 #nows that both the 32 and the networ# support P" ?O in the normal case. 1lause 8.8 describes the procedure when the procedure is rejected by the MM2.
UE1MS e+ode8 8SS1!+S MME MS, 1&. P&3i(3 !e=ue"t 1&. Ser6ice !e=ue"t 1c. ,S P&3i(3 !e?ect SGS+ Ser6i(3 G> P-G>1 GGS+

1&. ,S P&3i(3 +oti4ic&tio( 1). +'S E0te(ded Ser6ice !e=ue"t

1d. S1-'P UE ,o(te0t Modi4ic&tio( !e=ue"t 2it% ,S *&##)&cB i(dic&tor

1e. S1-'P UE ,o(te0t Modi4ic&tio( !e"$o("e me""&3e 2. 7$tio(&# Me&"ureme(t !e$ort So#icit&tio( 3&. PS ;7 &" "$eci4ied i( 23./01 @2A ($re$&r&tio( $%&"e &(d "t&rt o4 e0ecutio( $%&"e) 3). Su"$e(d 3c. U$d&te 8e&rer(")

/&. Loc&tio( 're& U$d&te /). P&3i(3 !e"$o("e /). '19u-c" me""&3e (2it% P&3i(3 !e"$o("e) &. E"t&)#i"% ,S co((ectio( ). ,o((ectio( !e?ect

Option 1: MSC is not changed

). Si3(&##i(3 ,o((ectio( !e#e&"e

). Loc&tio( 're& U$d&te or ,om)i(ed !'1L' U$d&te c. ,S c&## e"t&)#i"%me(t $rocedure

If the MSC is changed

6. PS ;7 &" "$eci4ied i( 23./01 @2A (co(ti(u&tio( o4 e0ecutio( $%&"e)

1i#ure ('3+&2 CS Pa#e in "+6T%A:< Call in G"%A:86T%A: ,a. The M"1 receives an incomin voice call and responds by sendin a Pa in /eGuest (&M"& or TM"&- optional 1aller 5ine &dentification and 1onnection Mana ement information- 1" call indicator- priority indication) to the MM2 over a "Gs interface. The M"1 only sends a 1" Pa e for an 32 that provides location update information usin the "Gs interface. &n active mode the MM2 has an established ", connection and if the MM2 did not return the J"M"=onlyJ indication to the 32 durin .ttach or 1ombined T.A5. 3pdate procedures- the MM2 reuses the e(istin connection to relay the 1" Pa e to the 32. &f the MM2 returned the J"M"=onlyJ indication to the 32 durin .ttach or 1ombined T.A5. 3pdate procedures- the MM2 shall not send the 1" "ervice 'otification to the 32 and shall send Pa in /eject towards M"1 to stop 1" Pa in procedure- and this 1"70 procedure stops. The e'ode0 forwards the pa in messa e to the 32. The messa e contains 1' :omain indicator and- if received from the M"1- the 1aller 5ine &dentification.

3GPP

%elease &&

3(

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

The MM2 immediately sends the "Gs "ervice /eGuest messa e to the M"1 containin an indication that the 32 was in connected mode. The M"1 uses this connected mode indication to start the 1all 7orwardin on 'o /eply timer for that 32 and the M"1 should send an indication of user alertin to the callin party. /eceipt of the "Gs "ervice /eGuest messa e stops the M"1 retransmittin the "Gs interface Pa in messa e. 'OT2 ,E The pre=confi ured policy may be used by 32 to avoid bein disturbed without 1aller 5ine &dentification display and the detailed handlin is to be decided by 1T, and 1T8. 'OT2 *E This procedure can also ta#e place immediately after M"1 receives M.PPP/' from ?""- if pre=pa in is deployed. 1aller 5ine &dentification and 1" call indicator are also provided in the case of pre=pa in . 'OT2 3E &n order to avoid the callin party e(periencin a potentially lon period of silence- the M"1 may use the "Gs "ervice /eGuest messa e as a tri er to inform the callin party that the call is pro ressin . &f the MM2 receives pa in reGuest messa e with priority indication- e. . eM5PP priority- from the M"1- then the MM2 processes this messa e and also the subseGuent 1" fallbac# procedure preferentially compared to other normal procedures. ,b. 32 sends an 2(tended "ervice /eGuest (/eject or .ccept) messa e to the MM2 for mobile terminatin 1" fallbac#. The 2(tended "ervice /eGuest messa e is encapsulated in //1 and ",=.P messa es. The 32 may decide to reject 1"70 based on 1aller 5ine &dentification. ,c. 3pon receivin the 2(tended "ervice /eGuest (/eject) for mobile terminatin 1" fallbac#- the MM2 sends Pa in /eject towards M"1 to stop 1" Pa in procedure and this 1"70 procedure stops. ,d. MM2 sends an ",=.P 32 1onte(t Modification /eGuest (1" 7allbac# &ndicator- 5.&) messa e to e'ode0. This messa eE indicates to the e'ode0 that the 32 should be moved to 3T/.'AG2/.'. The re istered P5M' for 1" domain is identified by the P5M' &: included in the 5.&- which is allocated by the MM2. &f MM2 received priority indication in "tep ,a- the MM2 sends ",=.P 32 1onte(t Modification /eGuest messa e to the e'ode0 with priority indication- i.e. J1"70 ?i h PriorityJ- as specified in T" 38.<,3 H3>I. ,e. The e'ode0 shall reply with ",=.P 32 1onte(t Modification /esponse messa e. *. The e'ode0 may optionally solicit a measurement report from the 32 to determine the tar et G2/.'A3T/.' cell to which P" handover will be performed. 'OT2 <E 0ased on operator policy- the priority indicator received in step,b may be used by e'ode0 to decide whether to continue 1" 7allbac# procedures with P" ?O- i.e. step3a- or to initiate radio release procedure to redirect the 32 to *GA3G 1ircuit "witch. 3a. The e'ode0 tri ers P" handover to a G2/.'A3T/.' nei hbour cell by sendin a ?andover /eGuired messa e to MM2. The e'ode0 selects the tar et P" handover cell considerin the P5M' &: and possibly the 5.1 for 1" domain provided by the MM2 in step ,d. &f the e'0 is a ?e'0- the ?e'0 should perform step 3 throu h step 8 of clause 9.< instead of P" ?O if the ?e'0 detects that the 32 has only 5&P. P:' 1onnections. 1"70 will not be completed successfully when P" ?O is performed if the 32 has only 5&P. P:' 1onnections as P" ?O would result in the MM2 detachin the 32. 'OT2 >E 7or details how the ?e'ode0 determines whether a P:' connection is a 5&P. P:' connection see T" *3.<+, H*I- clause <.3.,8. &n the followin an inter=/.T handover from 2=3T/.' to 3T/.' or G2/.' as specified in T" *3.<+, H*I be ins. The e'ode0 indicates in the "ource /'1 to Tar et /'1 Transparent container that P" handover was tri ered due to 1"70. The e'ode0 also indicates whether 1"70 was tri ered for emer ency or priority call handlin purpose. &f the networ# supports a priority call handlin - the e'ode0 may forward the priority indication to the tar et G2/.'A3T/.' in the "ource to Tar et Transparent 1ontainer- and the tar et G2/.'A3T/.' allocates radio bearer resources ta#in received priority indication ta#e into account. .s part of this handover- the 32 receives a ?O from 2=3T/.' 1ommand and tries to connect to a cell in the tar et /.T. The ?O from 2=3T/.' 1ommand may contain a 1" 7allbac# &ndicator which indicates to 32 that the handover was tri ered due to a 1" fallbac# reGuest. &f the ?O from 2=3T/.' 1ommand contains a 1" 7allbac# &ndicator and the 32 fails to establish connection to the tar et /.T- then the 32 considers that 1" fallbac# has failed.

3GPP

%elease &&

30

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

The 32 establishes the si nallin connection as described in step <b. 'OT2 8E :urin the P" ?O the "G"' does not create a Gs association with the M"1AB5/. 3b. &f the tar et /.T is G2/.' and the 32 has entered :edicated Mode- the 32 starts the "uspend procedure (see T" <<.+,@ H<I) unless both the 32 and the Tar et cell support :TM in which case T07 re=establishment may be performed. 3c. . GnAGp="G"' that receives the "uspend messa e from the 32 follows the "uspend procedure specified in T" *3.+8+ H3I- clause ,8.*.,.,.,. .n "<="G"' that receives the "uspend messa e from the 32 follows the "uspend procedure specified in T" *3.+8+ H3I. The "<="G"' deactivates G0/ bearers towards "=GD and P=GD(s) by initiatin M"=and "G"' &nitiated 0earer :eactivation procedure as specified in T" *3.+8+ H3I- and starts the preservation and suspension of non=G0/ bearers by sendin "uspend 'otification messa e to the "=GD. The "=GD releases all /'1 related information (address and T2&:s) for the 32 if :irect Tunnel is established- and sends "uspend 'otification messa e to the P=GD(s). The "G"' stores in the 32 conte(t that 32 is in suspended status. .ll the preserved non=G0/ bearers are mar#ed as suspended status in the "=GD and P=GD(s). The P=GD should discard pac#ets if received for the suspended 32. <a. &f the 5. of the new cell is different from the one stored in the 32- the 32 shall initiate a 5ocation .rea 3pdate procedure as followsE = &f the networ# is operatin in 'MO=& ('etwor# Modes of Operation)- the 32 shall initiate a separate 5ocation .rea 3pdate before initiatin the /.3 procedure instead of a 1ombined /.A5. 3pdate procedure (to speed up the 1"70 procedure)F or if the networ# is operatin in 'MO=&& the 32 shall initiate a 5ocation .rea 3pdate procedure before initiatin the /.3 procedure reGuired for P" handover.

The 32 shall set the J1"MTJ fla in the 5.3 /eGuest. The J1"MTJ fla is used to avoid missin MT call in roamin retry case. 7urther the 32 performs any /outin .rea 3pdate procedure as specified in T" *3.+8+ H3I. The 32 may initiate a 5ocation .rea 3pdate procedure immediately when the 32 is handed over to the tar et cell i.e. before the 32 receives e. . 5.& or 'MO information as part of the /.' Mobility &nformation. Dhen the M"1 receives a 5. 3pdate /eGuest- it shall chec# for pendin terminatin 1" calls and- if the J1"MTJ fla is set- maintain the 1" si nallin connection after the 5ocation .rea 3pdate procedure for pendin terminatin 1" calls. <b. &f the 32 does not initiate a 5.3 procedure- it shall respond with a Pa in /esponse messa e to the M"1 as followsE = &f the Tar et /.T is 3T/.' or G2/.' &u modeE The 32 establishes a radio si nallin connection and responds to the pa in by sendin an //1 Pa in /esponse as specified in T" *>.33, H9I. The 1' :omain &ndicator is set to J1"J in the &nitial :irect Transfer messa e. &f the Tar et /.T is G2/.' .AGb modeE The 32 establishes a radio si nallin connection and responds to pa in by usin the procedures specified in T" <<.+,@ H<I (i.e. 32 reGuests and is assi ned a dedicated channel where it sends a ".0M containin a Pa in /esponse to the 0"" and the 0"" responds by sendin a 3.). 3pon receivin the ".0M (containin a Pa in /esponse messa e) the 0"" sends a 1OMP52T2 5.O2/ 3 &'7O/M.T&O' messa e (containin a Pa in /esponse messa e) to the M"1 which indicates 1" resources have been allocated in the G2/.' cell. &f both the 32 and the tar et cell support enhanced 1" establishment in :TM (indicated by G2/.' system information included within the ?O from 2=3T/.' 1ommand) an // connection may be established while in pac#et transfer mode without release of the pac#et resources- see T" <3.+>> H*<I. .fter the establishment of the main si nallin lin# as described in T" <<.+,@ H<I the 32 enters either :ual Transfer Mode or :edicated Mode and the 1" call establishment procedure completes.

'OT2 9E The 0"" should be prepared to receive a Pa in /esponse even when the correspondin Pa in /eGuest has not been sent by this 0"". >a. .fter performin the 5.3 procedure or after receivin the Pa in /esponse the M"1 shall establish the 1" call if the 32 is allowed in the 5..

3GPP

%elease &&

3,

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

>b. &f the 32 is not re istered in the M"1 that receives the Pa in /esponse or the 32 is not allowed in the 5.- the M"1 shall reject the Pa in /esponse messa e by releasin the .A&u=1". The 0"1A/'1 in turn releases the si nallin connection for 3T/.' or G2/.' 1" domain. The si nallin connection release shall tri er the 32 to obtain the 5.&- which causes the initiation of a 5ocation .rea 3pdate or a 1ombined /.A5. procedure as specified in T" *3.+8+ H3I for the different 'etwor# Modes of Operation ('MO). The 5ocation .rea 3pdate tri ers the /oamin /etry for 1" 7allbac# procedure as defined in clause 9.>. >c. .fter performin the 5.3 procedure the M"1 shall establish the 1" call if the 32 is allowed in the 5.. 8. The 32 performs any remainin steps of the inter=/.T handover from 2=3T/.' to 3T/.' or G2/.' as specified in T" *3.<+, H*I Dith the e(ception of steps ,a and ,c- above- 1all 7orwardin (see T" *3.+@* H3,I) is performed on the basis of the T" *<.++@ H*,I si nallin received on the G2/.'A3T/.' cell. &f the 32 remains on 3T/.'AG2/.' after the 1" voice call is terminated the 32 performs normal mobility mana ement procedures as defined in T" *3.+8+ H3I and T" *<.++@ H*,I.

7./ Mo)i#e Termi(&ti(3 c&## i( 'cti6e Mode - +o PS ;7 "u$$ort

This procedure is e(ecuted when P" ?O is not supported- in the normal case. 1lause 8.8 describes the procedure when the procedure is rejected by the MM2.
UE1MS e+ode8 8SS1!+S MME MS, S-G>1PG> SGS+

1'. ,S SE!V9,E +7T9*9,'T97+ 1). +'S E0te(ded Ser6ice !e=ue"t

1'. P'G9+G !EGUEST 1'. SE!V9,E !EGUEST 1c. ,S P&3i(3 !e?ect

1d. S1-'P UE ,o(te0t Modi4ic&tio( !e=ue"t 2it% ,S *&##)&cB i(dic&tor 1e. S1-'P UE ,o(te0t Modi4ic&tio( !e"$o("e me""&3e 2. 7$tio(&# Me&"ureme(t !e$ort 3&. ,,71+',,, 3), 3c. Si3(&##i(3 co((ectio( re#e&"e /. S1-'P- S1 UE ,7+TEHT !ELE'SE !EGUEST . S1 UE ,7+TEHT !ELE'SE
6.UE c%&(3e" !'T t%e(, L'U 7! !' UP5'TE 7! L'U '+5 !'U

7&. Su"$e(d ("ee TS 23.060) 7). Su"$e(d !e=ue"t 1 !e"$o("e <. U$d&te )e&rer(") 9. P&3i(3 !e"$o("e 9&. E"t&)#i"% ,S co((ectio( 9). Si3(&##i(3 ,o((ectio( !e#e&"e 9). ,7++E,T97+ !EFE,T
9* T;E MS, 9S ,;'+GE5

9c. Loc&tio( 're& U$d&te or ,om)i(ed !'1L' U$d&te

1i#ure ('-+&2 CS Pa#e in "+6T%A:< Call in G"%A:86T%A: without PS 7= ,a. The M"1 receives an incomin voice call and responds by sendin a Pa in /eGuest (&M"& or TM"&- optional 1aller 5ine &dentification and 1onnection Mana ement information- priority indication) to the MM2 over a "Gs interface. The M"1 only sends a 1" Pa e for an 32 that provides location update information usin the "Gs interface. &n active mode the MM2 has an established ", connection and if the MM2 did not return the J"M"= onlyJ indication to the 32 durin .ttach or 1ombined T.A5. 3pdate procedures- the MM2 reuses the e(istin connection to relay the 1" "ervice 'otification to the 32.

3GPP

%elease &&

-*

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

&f the MM2 returned the J"M"=onlyJ indication to the 32 durin .ttach or 1ombined T.A5. 3pdate procedures- the MM2 shall not send the 1" Pa e to the 32 and sends 1" Pa in /eject towards M"1 to stop 1" Pa in procedure- and this 1"70 procedure stops. The e'ode0 forwards the pa in messa e to the 32. The messa e contains 1' :omain indicator and- if received from the M"1- the 1aller 5ine &dentification. The MM2 immediately sends the "Gs "ervice /eGuest messa e to the M"1 containin an indication that the 32 was in connected mode. The M"1 uses this connected mode indication to start the 1all 7orwardin on 'o /eply timer for that 32 and the M"1 should send an indication of user alertin to the callin party. /eceipt of the "Gs "ervice /eGuest messa e stops the M"1 retransmittin the "Gs interface Pa in messa e. 'OT2 ,E The pre=confi ured policy may be used by 32 to avoid bein disturbed without 1aller 5ine &dentification display and the detailed handlin is to be decided by 1T DG, and 1T DG8. 'OT2 *E This procedure can also ta#e place immediately after M"1 receives M.PPP/' from ?""- if pre=pa in is deployed. 1aller 5ine &dentification is also provided in the case of pre=pa in . &f the MM2 receives pa in reGuest messa e with priority indication- e. . eM5PP priority- from the M"1- then the MM2 processes this messa e and also the subseGuent 1" fallbac# procedure preferentially compared to other normal procedures. ,b. 32 sends an 2(tended "ervice /eGuest (/eject or .ccept) messa e to the MM2 for mobile terminatin 1" fallbac#. 2(tended "ervice /eGuest messa e is encapsulated in //1 and ",=.P messa es. The 32 may decide to reject 1"70 based on 1aller 5ine &dentification. ,c. 3pon receivin the 2(tended "ervice /eGuest (/eject) for mobile terminatin 1" fallbac#- the MM2 sends Pa in /eject towards M"1 to stop 1" Pa in procedure and this 1"70 procedure stops. ,d. The MM2 sends an ",=.P 32 1onte(t Modification /eGuest (1" 7allbac# &ndicator- 5.&) messa e to e'ode0. This messa e indicates to the e'ode0 that the 32 should be moved to 3T/.'AG2/.'. The re istered P5M' for 1" domain is identified by the P5M' &: included in the 5.&- which is allocated by the MM2. &f MM2 received priority indication in "tep ,a- the MM2 sends ",=.P 32 1onte(t Modification /eGuest messa e to the e'ode0 with priority indication- i.e. J1"70 ?i h PriorityJ- as specified in T" 38.<,3 H3>I. ,e. The e'ode0 shall reply with ",=.P 32 1onte(t Modification /esponse messa e. *. The e'ode0 may optionally solicit a measurement report from the 32 to determine the tar et G2/.'A3T/.' cell to which the redirection procedure will be performed. T'e net/ork 0er&orm) one o& )te0) $a or $b or $c. 3a. &f the 32 and networ# support inter=/.T cell chan e order to G2/.' and the tar et cell is G2/.'E The e'ode0 can tri er an inter=/.T cell chan e order (optionally with '.11) to a G2/.' nei hbour cell by sendin an //1 messa e to the 32. The inter=/.T cell chan e order may contain a 1" 7allbac# &ndicator which indicates to 32 that the cell chan e order is tri ered due to a 1" fallbac# reGuest. &f the inter=/.T cell chan e order contains a 1" 7allbac# &ndicator and the 32 fails to establish connection to the tar et /.T- then the 32 considers that 1" fallbac# has failed. "ervice /eGuest procedure is considered to be successfully completed when cell chan e order procedure is completed successfully. The e'ode0 selects the tar et cell considerin the P5M' &: and possibly the 5.1 for 1" domain provided by the MM2 in step ,d for 11OA'.11 purpose. 3b. &f the 32 or the networ# does not support inter=/.T P" handover from 2=3T/.' to G2/.'A3T/.' nor inter=/.T cell chan e order to G2/.'E The e'ode0 can tri er //1 connection release with redirection to G2/.' or 3T/.' instead of P" ?O or '.11. 'OT2 3E Dhen performin 1" 7allbac# to 3T/.'- the //1 connection release with redirection can be optimi!ed if both the 32 and 3T/.' support the optional J:eferred measurement control readin J feature specified in T" *>.33, H9I.

3GPP

%elease &&

-&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

3c. &f the 32 and networ# support J//1 connection release with redirection and Multi 1ell "ystem &nformation to G2/.'A3T/.'JE The e'ode0 can tri er //1 connection release with redirection to G2/.' or 3T/.' and include one or more physical cell identities and their associated "ystem &nformation. &n step 3b or step 3c- the e'ode0 includes the redirection control information into the //1 1onnection /elease messa e based on the P5M' &: for 1" domain and the /.TAfreGuency priority confi ured in the e'ode0- so that the 32 re istered P5M' for 1" domain can be preferably selected. .lso in "teps 3b or 3c- the e'0 sets the J1" 7allbac# ?i h PriorityJ indication in the //1 /elease messa e- if the ",.P messa e in "tep ,d contains the J1"70 ?i h PriorityJ indication. 'OT2 <E "ervice /eGuest procedure supervision timer shall be sufficiently lon considerin the optional measurement reportin at step *. <. The e'ode0 sends an ",=.P 32 1onte(t /elease /eGuest messa e to the MM2. &f the tar et cell is G2/.' and either the tar et cell or the 32 does not support :TM the messa e includes an indication that the 32 is not available for P" service. >. The MM2 releases the 32 1onte(t in the e'ode0 as well as all e'ode0 related information in the "=GD as specified in T" *3.<+, H*I. &n case the 1ause indicates that //1 was released due to abnormal conditions- e. . radio lin# failure- the MM2 suspends the 2P" bearers ("tep @). T'e -" 0er&orm) one o& )te0) 6a or 6b or 6c and T1" 0er&orm) )te0 6d. 8a. ("tep 8a is performed if step 3a- 1ell 1han e Order to G2/.'- was performed). The 32 moves to the new cell in G2/.'. The 32 uses the '.11 information andAor the broadcast "ystem &nformation and when it has the necessary information to access the G2/.' cell- establishes a radio si nallin connection. 8b. ("tep 8b is performed if step 3b- //1 release with redirection- was performed). The 32 moves to the tar et /.T- identifies a suitable cell preferably of the same P5M' as received in 5.& &2 of combined 2P"A&M"& .ttachAT.3 .ccept messa e-- receives the broadcast "ystem &nformation and when it has the necessary information to access G2/.'A3T/.'- establishes a radio si nallin connection. 8c. ("tep 8c is performed if step 3c- //1 connection release with redirection and Multi 1ell "ystem &nformationwas performed) The 32 moves to the tar et /.T and identifies a suitable cell preferably of the same P5M' as received in 5.& &2 of combined 2P"A&M"& .ttachAT.3 .ccept messa e. The 32 uses the Multi 1ell "ystem &nformation andAor the broadcast "ystem &nformation and when it has the necessary information to access G2/.'A3T/.'- the 32 establishes the radio si nallin connection. &f the 32 receives the J1" 7allbac# ?i h PriorityJ indication in the //1 /elease messa e in "tep 3b or 3c and the tar et is 3T/.'- the 32 sets the establishment cause value to JTerminatin ?i h Priority "i nallin J in the //1 1onnection /eGuest in "teps 8b and 8c. &f the tar et is G2/.'- no special establishment cause value is set by the 32. 8d. &f the 5. of the new cell is different from the one stored in the 32- the 32 shall initiate a 5ocation .rea 3pdate re ardless of the different 'etwor# Modes of Operation ('MO). The 32 shall set the J1"MTJ fla in the 5.3 /eGuest. The J1"MTJ fla is used to avoid missin MT call in roamin retry case. &n 'MO &- the 32 in G2/.' may perform 5. update over the // connection instead of combined /.A5. update over the pac#et access as defined in T" *<.++@ H*,I- clause <.9.>.*.>- unless enhanced 1" establishment in :TM is supported. 7urther the 32 performs any /outin .rea 3pdate procedure as specified in T" *3.+8+ H3I. &n 'MO & a 1"70 32 shall perform 5.3 (and if it does so- shall set the J1"MTJ fla ) and /.3 procedures instead of a 1ombined /.A5. 3pdate procedure to speed up the 1"70 procedure.

3GPP

%elease &&

-$

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

Dhen the M"1 receives a 5. 3pdate /eGuest- it shall chec# for pendin terminatin 1" calls and- if the J1"MTJ fla is set- maintain the 1" si nallin connection after the 5ocation .rea 3pdate procedure for pendin terminatin 1" calls. &f the e'ode0 indicated 32 to o to G2/.' in step 3 but the 32 finally camps on an 3T/.' cell of the same /. that the 32 is re istered with and &"/ active- the 32 shall locally deactivate &"/. 9. &f the tar et /.T is G2/.' and :TM is not supported or the 32 does not support :TM- the 32 starts the "uspend procedure specified in T" *3.+8+ H3I. This tri ers the (servin ) "G"' to send a "uspend /eGuest (T55&- /.&) messa e to the old 1' node identified by the /.& and T55&. &f &"/ is not active- the /.& and T55& refer to an MM2. The MM2 returns a "uspend /esponse to the "G"' even thou h G3T& cannot be derived from the P=TM"& and /.& pair. &f &"/ is active- the /.& and T55& refer to the old "<="G"'- &n this case- if the servin "G"' is different from the old "G"' which has &"/ association with MM2- the old "G"' returns a "uspend /esponse to the servin "G"'. 'OT2 >E 7or step 9b and @- the inter="G"' suspendin procedure of &"/ active case are not shown in the fi ure. @. &f the ",=.P 32 1onte(t /elease /eGuest messa e- received from the e'ode0 in step <- indicates that the 32 is not available for the P" services in the tar et cell- the MM2 deactivates G0/ bearers towards "=GD and P= GD(s) by initiatin MM2=initiated :edicated 0earer :eactivation procedure as specified in T" *3.<+, H*I- and starts the preservation and suspension of non=G0/ bearers by sendin "uspend 'otification messa e to the "= GD. &f &"/ is active- the (old) "<="G"' deactivates G0/ bearers towards "=GD and P=GD(s) by initiatin M"=and "G"' initiated 0earer :eactivation procedure as specified in T" *3.+8+ H3I- and starts the preservation and suspension of non=G0/ bearers by sendin the "uspend 'otification messa e to the "=GD- which is all tri ered by the "uspend procedure in step 9. The "=GD sends "uspend 'otification messa e to the P=GD(s) when it receives the "uspend 'otification messa e from MM2 or "<="G"'. &f the "=GD receives two "uspend 'otification messa es for the same 32- it i nores the second one e(cept for sendin response. The MM2 stores in the 32 conte(t that the 32 is in suspended status. &f &"/ is active- the (old) "<="G"' stores in the 32 conte(t that 32 is in suspended status. .ll the preserved non=G0/ bearers are mar#ed as suspended status in the "=GD and P=GD(s). The P=GD should discard pac#ets if received for the suspended 32. 'OT2 8E "tep @ can not be tri ered by the "uspend procedure since the full G3T& can not be derived from the P=TM"& and /.& included in the "uspend /eGuest messa e. ;. &f the 32 does not initiate a 5.3 procedure- the 32 responds to the pa in by sendin a Pa in /esponse messa e as specified in T" <<.+,@ H<I or T" *>.33, H9I. Dhen received at the 0""A/'"- the Pa in /esponse is forwarded to the M"1. 'OT2 9E The M"1 should be prepared to receive a Pa in /esponse after a relatively lon time from when the 1" Pa in /eGuest was sent (step ,a). ;a. &f 32 is re istered in the M"1 servin the *GA3G cell and the 32 is allowed in the 5. the M"1 shall establish the 1" call. ;b. &f the 32 is not re istered in the M"1 that receives the Pa in /esponse or the 32 is not allowed in the 5.- the M"1 shall reject the Pa in /esponse by releasin the .A&u=cs connection. The 0""A/'" in turn releases the si nallin connection for 1" domain. ;c. The si nallin connection release shall tri er the 32 to obtain the 5.&- which causes the initiation of a 5ocation .rea 3pdate or a 1ombined /.A5. procedure as specified in T" *3.+8+ H3I for the different 'etwor# Modes of Operation ('MO). The 5ocation .rea 3pdate tri ers the /oamin /etry for 1" 7allbac# procedure as defined in clause 9.>. .fter performin the 5.3 procedure the M"1 shall establish the 1" call if the 32 is allowed in the 5.. Dith the e(ception of steps ,a and ,c- above- 1all 7orwardin (see T" *3.+@* H3,I) is performed on the basis of the T" *<.++@ H*,I si nallin received on the G2/.'A3T/.' cell. .fter the 1" voice call is terminated and if the 32 is still in G2/.' and P" services are suspended- then the 32 shall resume P" services as specified in T" *3.+8+ H3I. . GnAGp= "G"' will follow T" *3.+8+ H3I to resume the P:P 1onte(t(s)- which is done by the /outin .rea 3pdate procedure. :urin the /outin .rea 3pdate procedure in which the GnAGp "G"' sends a 3pdate P:P 1onte(t /eGuest messa e to the GG"'AP=GD- the GG"'AP=GD resumes the P:P 1onte(t(s). .n "< "G"' will follow T" *3.+8+ H3I to resume the bearers- and informs the "=GD and P=GD(s) to

3GPP

%elease &&

-3

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

resume the suspended bearers. &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 "=GD and P=GD(s) to resume the suspended bearers. /esumin the suspended bearers in the "=GD and in the P=GD should be done by implicit resume usin the Modify 0earer reGuest messa e if it is tri ered by the procedure in operation e. . /.3- T.3 or "ervice /eGuest. The "=GD is aware of the suspend state of the bearers and shall forward the Modify 0earer reGuest to the P= GD. 2(plicit resume usin the /esume 'otification messa e should be used in cases when Modify 0earer /eGuest is not tri ered by the procedure in operation. &f the 32 remains on 3T/.'AG2/.' after the 1" voice call is terminated the 32 performs normal mobility mana ement procedures as defined in T" *3.+8+ H3I and T" *<.++@ H*,I.

7. !o&mi(3 !etr: 4or ,S 4&##)&cB

The procedure in this section may be applied for mobile terminated calls where the M"1- to which the 32 sends the 5.3- is different from the M"1 that sent the pa in messa e to the 32. The procedure is based on the QMobile Terminatin /oamin /etry 1allR procedure defined in T" *3.+,@ H>I and there is an only minor adaptation of the procedure to support 1" fallbac#.

3GPP

%elease &&

--

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

GMS,

;L!

VMS,1VL!
1

7#d

+e2
VMS,1VL!
2

SA"84T"

MS

S!9 (8, GMS,I,c&## !e4.,!o&mi(3retr:) P!+ (c&## re4.,GMS,I, !o&mi(3 retr:) P!+ ',J (MS!+) S!9 ',J P&3i(3 9'M (MS!+)

CS1all ac!
LocU$d&te 'ut%e(tic&tio( Procedure U$d&te Loc&tio( 3 ,&(ce# Loc&tio( 7#d MS, "to$" $&3i(3 timer ,&(ce# Loc&tio( 'cB &(d i(4orm GMS, 9("ert Su)"cri)er 5&t& (mu#ti$#e) !,; (c&## re4ere(ce, ro&mi(3 retr:) !EL !L,"
/

',J

2(d S!9 (8, )&"ic c&## i(terro3&tio() ;L! de#&:" t%e "e(di(3 o4 P!+ u(ti# #oc&tio( u$d&te 6 $rocedure 4i(i"%e" 9("ert Su)"cri)er 5&t& (co(ti(ued) U$d&te Loc&tio( 'cB P!+ P!+ ',J (MS!+) 2(d S!9 ',J (MS!+)
7 7

*urt%er $rocedure" re#&ted to #oc&tio( u$d&te. e.3. ci$%eri(3, TMS9 re&##oc&tio(.

9'M (MS!+) +e2 VMS,1VL! m&: de#&: "etu$ u(ti# < #oc&tio( u$d&te $rocedure 4i(i"%e" LocU$d&te 'cce$t TMS9 !e&##oc&tio( ,om$#ete Setu$ ,&## ,o(4irmed +orm&# MT c&## $rocedure 4o##o2"

1i#ure ('.+&2 %oamin# %etry for CS fall ac! There are only * differences in this procedure compared to the QMobile Terminatin /oamin /etry 1allR procedure defined in T" *3.+,@ H>I. = The first difference is that the pa in messa e in 2=3T/.' tri ers the 1" fallbac# which is followed by a location update in the new /.T. This functionality is already supported in the 1" fallbac# flows for terminatin calls and no additional functionality is needed. The second difference is that the 32 includes the J1"MTJ fla in the location update reGuest messa e so that the si nallin lin# is maintained for lon er in case the &.M is delayed by the ?5/.

7. & !o&mi(3 *or2&rdi(3 4or ,S 4&##)&cB

The procedure in this clause may be applied for mobile terminated calls where the M"1AB5/- to which the 32 sends the 5.3- is different from the M"1AB5/ that sent the pa in messa e to the 32. The procedure is based on the JMobile Terminatin /oamin 7orwardin J procedure defined in T" *3.+,@ H>IF the specific behaviour for 1"70 is

3GPP

%elease &&

-.

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

described in this section. This procedure avoids impactin all GM"1 nodes and can coe(ist with Mobile Terminatin /oamin /etry procedure described in clause 9.>. 'OT2 ,E &n order to support Mobile Terminatin /oamin 7orwardin both the M"1 controllin the tar et cellthe M"1 that sent the pa in messa e to the 32 and the ?5/ need to support the feature. 'OT2 *E This procedure has smaller call setup delay than Mobile Terminatin /oamin /etry procedure especially in roamin cases. 'OT2 3E &f the networ# does not support this procedure- the Mobile Terminatin /oamin /etry procedure specified in clause 9.> can be used. &n order to ensure roamin forwardin can be offered in all scenarios (e. . in case of &M"& in the 5.3 /eGuest from 32)- ?5/s should be updated to support MT/7. &n order to permit Mobile Terminatin /oamin 7orwardin from the old B5/ if the ?5/ is not updated to support MT/7 but the visited networ# does support MT/7- the new B5/ may include MT/7 supported fla in "end &dentification when it receives a 5ocation 3pdatin /eGuest containin the J1"MTJ fla .

3GPP

%elease &&

-/

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

GMS, S!9 (8)

;L! P!+

7#d MS,1VL!

+e2 MS,1VL!

MS

P!+ ',J (MS!+) S!9 ',J 9'M (MS!+)

P&3i(3 CS1> Loc&tio( U$d&te 1. Se(d 9de(ti4ic&tio( (MT!* "u$$orted, +e2 MS,1VL! (um)er")

2. U$d&te Loc&tio( (MT!* "u$$orted)1 3. ,&(ce# Loc&tio( (MT!* Su$$orted '(d 'ut%oriKed, +e2 MS,1VL! (um)er") ,&(ce# Loc&tio( 'cB /. 7#d MS, "to$" $&3i(3 timer 9("ert Su)"cri)er 5&t& (mu#ti$#e) . 94 ;L! &ut%ori"e" MT!* t%e( u"e (e2 MS,1VL! (um)er" to tri33er "e(di(3 o4 P!+ !e= 6. P!+ (MT!* i(dic&tio(, 7#d MS, (um)er) 9("ert Su)"cri)er 5&t& (co(ti(ued) U$d&te Loc&tio( 'cB 7. '4ter U$d&te Loc&tio( 'cB i" recei6ed, t%e (e2 VL! retur(" MS!+L to t%e o#d VL!. <. P!+ !e"$ (MS!+L) 9. 9'M (MS!+L) *urt%er $rocedure" re#&ted to #oc&tio( u$d&te. E.3. ci$%eri(3, 9ME9 c%ecBi(3, TMS9 re&##oc&tio(.

10. +e2 VMS,1VL! de#&:" "etu$ u(ti# #oc&tio( u$d&te $rocedure 4i(i"%e". Loc&tio( U$d&te 'cce$t TMS9 !e&##oc ,om$#ete Setu$ ,&## ,o(4irmed +orm&# MT c&## $rocedure 4o##o2". 1i#ure ('.a+&2 %oamin# 1orwardin# for CS1> The main differences compared to the JMobile Terminatin /oamin 7orwardin J procedure defined in T" *3.+,@ H>I are described belowE = The pa in messa e in 2=3T/.' tri ers the 1" fallbac# which is followed by a location update in the new /.T.

'OT2 <E This functionality is already supported in the 1" fallbac# flows for terminatin calls and no additional functionality is needed.

3GPP

%elease &&

-(

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

= =

The 32 includes the J1"MTJ fla in the location update reGuest messa e so that the si nallin lin# is maintained for lon er in case the &.M is delayed by the old M"1AB5/. &f the 5ocation 3pdate /eGuest contains the J1"MTJ fla set and a valid TM"&Aold 5.&- the new M"1AB5/ may indicate to the old M"1AB5/ that it supports MT/7 in the "end &dentification messa e. The new B5/ then performs authentication to the 5ocation update and updates the ?"". &f the 5ocation 3pdate /eGuest contains the &M"&- only ?5/=based MT/7 procedure can be used. .fter 1ancel 5ocation is received from ?""- if the ?5/ authorised the MT/7 call between the old and the new terminatin M"1s or if the ?5/ did not disallow the MT/7 call between the old and the new terminatin M"1s but the new M"1AB5/ indicated its MT/7 support earlier in "end &dentification messa e- the old M"1AB5/ stops pa in timer and chec#s roamin and char in pre=confi ured a reements with re ards to call routein to the new M"1AB5/. &f these chec#s are successful- the old M"1AB5/ sends a Provide /oamin 'umber reGuest (MT/7 &ndicator- parameters received from the ?5/) to the new M"1AB5/.

7. ) ,oe0i"te(ce o4 !o&mi(3 !etr: &(d !o&mi(3 *or2&rdi(3 4or ,S 4&##)&cB

&f an M"1AB5/ supports both the procedures as specified in clause 9.> and 9.>a- and the GM"1 has indicated support roamin retry as specified in clause 9.>- the old M"1AB5/ which sends the initial pa in reGuest can decide based on operator policy whether to follow the procedure specified in clause 9.> or clause 9.>a.

7.6 !etur(i(3 )&cB to E-UT!'+

Once 1" service ends in 1" domain- e(istin mechanisms can be used to move the 32 to 2=3T/.'- no specific 1" 7allbac# mechanisms are needed. :urin the release of an // connection the M"1 should indicate to G2/.'A3T/.' that the // connection (for call or 1&"" or 51") was established as a result of 1" fallbac#. G2/.' and 3T/.' may use the indication to determine which of the e(istin mechanisms that should be used to move the 32 to 2=3T/.'. Dhen the 32 moves to 2=3T/.'- if the 2P" service was suspended durin the 1" service- it is resumed as specified in clause 8.>.

7.7 9(ter&ctio( 2it% 9S!

7.7.1 Void

3GPP

%elease &&

-0

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

7.7.2 Mo)i#e Termi(&ti(3 ,&## 2%e( 9S! i" &cti6e &(d SG" i" &cti6e )et2ee( MS,1VL! &(d MME

1i#ure ('('$+&2 3o ile Terminatin# Call when 5S% is active and SGs is active etween 3SC8)4% and 33" ,) G=M"1 receives &.M. *) G=M"1 retrieves routin information of the terminatin 32 by "end /outin &nfo procedures as specified in T" *3.+,@ H>I. 3) G=M"1 sends &.M to the M"1AB5/ on the terminatin side as specified in T" *3.+,@ H>I. <) The M"1AB5/ sends a Pa e messa e to the MM2 via "Gs (details on the Pa e messa e can be found in clauses 9.* or 9.3). >a) The MM2 receives the Pa e messa e from the M"1AB5/. &f the 32 is in 21M=&:52 state- the MM2 sends a Pa in (as specified in T" *3.<+, H*I- and 1' :omain &ndicator) messa e to each e'ode0 servin the T. list the 32 is re istered to as specified in clause 9.*. &f the 32 is in 21M=1O''21T2:- the MM2 relays the 1" Pa e messa e to the servin e'ode0 over the ", interface as specified in clause 9.3. >b)The e'ode0s receive 1" pa in messa es from the MM2- and the procedures ta#e place as specified in clause 9.*. 8a .s &"/ is active and the 32 is in 21MP&:52 state- the MM2 forwards the 1" pa in messa e received from the M"1AB5/ to the associated "G"'. The MM2 ets the "G"' information in the re ular &"/ activation process. &f MM2 received the priority mar#in in step<- it forwards 1" pa in messa e with priority mar#in e. . eM5PP priority- to the "G"'. 8b)The "G"' receives the 1" pa in messa e from the MM2- the "G"' sends pa in messa es to /'"A0""swhich is described in detail in T" *3.+8+ H3I. The "G"' shall not implement a local retransmission scheme for the &uAGb pa in messa es. 8c) Dhen /'"A0"" nodes receive pa in messa e from the "G"'- pa in is initiated as described in detail in T" *3.+8+ H3I. 'OT2E &f &"/ is not active or the 32 is in 21M=1O''21T2: state- the MM2 does not send the 1" pa in messa e to the "G"'. That means- the steps of 8a- 8b- 8c are not needed in the MT call procedure.

9) 3pon receipt of a Pa in /eGuest messa e for a circuit=switched service- the 1" 7allbac# (as defined in this specification) or 1ell /eselection (as defined in T" *3.+8+ H3I) ta#e place- and the 32 accesses 1" domain from 3MT"AG"M. @) Dhen the 1" 7allbac# or 1ell /eselection completes- the 32 responds to the 1" pa in reGuest and returns the 1" pa in response as described in detail in this specification and T" *3.+8+ H3I to the /'"A0"".

3GPP

%elease &&

-,

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

;) Dhen received at the /'"A0""- the 1" Pa in /esponse messa e is sent to the M"1AB5/ as described in detail in T" *3.+8+ H3I. The M"1AB5/ receives 1" pa in response contained in correspondin messa e which shall then stop the pa in response timer and establish the 1" connection- then the MT call process as described in detail in T" *3.+,@ H>I.

7.7.3 Void

7.< Mo)i#e Termi(&ti(3 ,&## 2%e( SG" i" (ot &cti6e

/e ular pre=/elease @ M"1 procedures are performed without any &"/ or "Gs specifics.

<

7t%er ,S Ser6ice"

<.1 Ge(er&#
The M"1 handles the timers- Gueuin and retransmission for sendin the "Gs.P=P.G&'G=/2N32"T messa e on the "Gs interface in the same way that it handles the sendin of a P.G&'G messa e on the . or &u interface. .s a conseGuence- the MM2 and (if &"/ is active) the "G"' shall not implement local retransmission schemes for this pa in .

<.2 S%ort Me""&3e Ser6ice (SMS)

<.2.1 Ge(er&#
The procedures for "M" in this specification apply only if the 32 is 2P"A&M"& attached and the 'on .ccess "tratum si nallin based "M" transfer is chosen by the 32 andAor the home P5M' for deliverin short messa es. This clause describes both the mobile ori inatin and mobile terminatin "M" over "Gs procedures in 2P". "M" support is based on the connectionless "Gs reference point between the MM2 and the M"1 "erver and use of '." si nallin between the 32 and the MM2- i.e. no 1" 7allbac# is performed for "M". This clause also describes the "M" procedures between the 32 and the MM2 for 32s that use only P" and "M" services but no 1" 7allbac# via G2/.' andAor 3T/.'. The "M" protocol entities are reused from the e(istin M"A32 and M"1 implementations. This means that the "M" over "Gs procedures reuse the different protocol layers as defined in T" *3.+<+ H,<I. 'OT2. Dith "M" over "Gs- the M"1AB5/ produces the 1all :etail /ecord. The sta e 3 chan es to the 1:/ for "M" over "Gs were made in a manner that should permit an unmodified /elease 9 entity to receive the 1:/. ?owever- for correct operation of- e. . customer care services- when usin an unmodified /elease 9 entity to receive the 1:/- the BP5M' should ensure that the T.1 values do not overlap with the 5.1 values.

<.2.2 Mo)i#e ori3i(&ti(3 SMS i( 9d#e Mode

The followin seGuence flow shows the delivery of mobile ori inatin "M" in idle mode. The messa e flows between the M2A32 and M"1AB5/ are also broadly applicable to the Memory .vailable 'otification.

3GPP

%elease &&

.*

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

MS1UE

MME

MS,1VL!

;L!1;SS

SMS9>MS,

S,

1. EPS19MS9 &tt&c% $rocedure 2. UE tri33ered Ser6ice !e=ue"t 3. U$#i(B +'S Tr&("$ort /. U$#i(B U(itd&t& . *or2&rd S%ort Me""&3e /&. 5o2(#i(B U(itd&t& /&. 5o2(#i(B +'S Tr&("$ort <. 5e#i6er: re$ort 9. 5o2(#i(B U(itd&t& 10. 5o2(#i(B +'S Tr&("$ort 11. U$#i(B +'S Tr&("$ort 12. U$#i(B U(itd&t& 13. !e#e&"e !e=ue"t 6. Me""&3e tr&("4er 7. 5e#i6er: re$ort

1i#ure 0'$'$+&2 3o ile ori#inatin# S3S in idle mode ,. The combined 2P"A&M"& attach procedure as described in clause >.* has been performed earlier. *. . mobile ori inatin "M" is tri ered and the M"A32 is in idle mode. The M"A32 initiates the 32 tri ered "ervice /eGuest procedure- which is defined in T" *3.<+, H*I. The 32 indicates its "=TM"& in the //1 si nallin . 3. The M"A32 builds the "M" messa e to be sent as defined in T" *3.+<+ H,<I (i.e. the "M" messa e consists of 1P=:.T.A/P=:.T.ATP:3A"M"="30M&T parts). 7ollowin the activation of the /adio 0earers- the "M" messa e is encapsulated in an '." messa e and sent to the MM2. <. The MM2 forwards the "M" messa e to the M"1AB5/ in an 3plin# 3nitdata messa e. &n order to permit the M"1 to create an accurate char in record- the MM2 adds the &M2&"B- the local time !one- the Mobile "tation 1lassmar# *- and the 32$s current T.& and 2=1G&. <a. The M"1AB5/ ac#nowled es receipt of the "M" to the 32. >.=@. These steps are performed as defined in T" *3.+<+ H,<I. The "M" messa e is forwarded to the "1 that returns a delivery report messa e. ;. The M"1AB5/ forwards the received delivery report to the MM2 associated with the M"A32 in a :ownlin# 3nitdata messa e. ,+. The MM2 encapsulates the received delivery report in an '." messa e and sends the messa e to the M"A32. ,,- ,*.The 32 ac#nowled es receipt of the delivery report to the M"1AB5/. ,3. The M"1AB5/ indicates to the MM2 that no more '." messa es need to be tunnelled. The MM2 should not use the "Gs /elease /eGuest messa e as a tri er for the release of ", resources. 'OT2E This is because the MM2 does not #now whether the "ervice /eGuest performed in step * was solely for the purpose of "M"- or- was for "M" and user plane data- or- whether or not the mobile has additional "M"s to send.

3GPP

%elease &&

.&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

<.2.3 Mo)i#e ori3i(&ti(3 SMS i( 'cti6e Mode

Mobile Ori inatin "M" in active Mode procedure is specified by reusin the Mobile Ori inatin "M" in &dle Mode with the followin modificationE = The established si nallin connection between the M"A32 and the MM2 is reused for the transport of the "M" messa e and the delivery report (i.e. the 32 tri ered "ervice /eGuest procedure defined in step * is s#ipped).

<.2.3& Mu#ti$#e Mo)i#e ori3i(&ti(3 SMS"

&n clause 3.* of T" *<.+,, H*@I- the simultaneous transmission of more than one MO "M"Anotification per domain is prohibited. &f the 32 has more than one "M"Anotification to send- the subseGuent "M"Anotification is sent at step ,, of clause @.*.* and the ac#nowled ement of the delivery report for the previous "M"Anotification is not sent.

<.2./ Mo)i#e termi(&ti(3 SMS i( id#e mode

The followin seGuence flow shows the delivery of mobile terminatin "M" in idle mode.

MS1UE

e+ode8

MME

MS,1VL!

;L!1;SS

SMSSMS1 GMS,

S,

1. EPS19MS9 &tt&c% $rocedure

2. Me""&3e tr&("4er 3. Se(d !outei(3 9(4o *or S%ort Me""&3e /. *or2&rd S%ort Me""&3e

7. P&3i(3

6. P&3i(3

. P&3i(3

<. Ser6ice !e=ue"t 9). 5o2(#i(B +'S Tr&("$ort 9c. U$#i(B +'S Tr&("$ort 10. U$#i(B +'S Tr&("$ort

<&. Ser6ice !e=ue"t 9&. 5o2(#i(B U(itd&t& 9d. U$#i(B U(itd&t& 11. U$#i(B U(itd&t& 12. 5e#i6er: re$ort 13. 5e#i6er: re$ort

1 . 5o2(#i(B +'S Tr&("$ort

1/. 5o2(#i(B U(itd&t& 16. !e#e&"e !e=ue"t

1i#ure 0'$'-+&2 3o ile terminatin# S3S in idle mode ,. The combined 2P"A&M"& attach procedure as described in clause >.* has been performed. *=<. The "1 initiates transfer of mobile terminatin "M". The ?5/ is reGuested for routin number for "M" services and the "M" messa e is forwarded to the M"1AB5/ where the M"A32 is 1" attached. >. The M"1AB5/ sends a Pa in (&M"&- B5/ TM"&- 5ocation &nformation- "M" indicator) messa e to the MM2. 8. The MM2 initiates the pa in procedure by sendin the Pa in (as specified in T" *3.<+, H*I) messa e to each e'ode0 with cells belon in to the trac#in area(s) in which the 32 is re istered. The 32 is pa ed with its "=TM"&. 9. The M"A32 is pa ed by the e'ode0s. @. The 32 sends a "ervice /eGuest messa e to the MM2. The 32 indicates its "=TM"& in the //1 si nallin . The MM2 sends the ",=.P &nitial 1onte(t "etup /eGuest messa e to the e'ode0 and the e'ode0 establishes the /adio 0earers.

3GPP

%elease &&

.$

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

@a. The MM2 sends a "ervice /eGuest messa e to the M"1. &n order to permit the M"1 to create an accurate char in record- the MM2 adds the &M2&"B- the local time !one- the Mobile "tation 1lassmar# *- and the 32$s current T.& and 2=1G&. ;a. The M"1AB5/ builds the "M" messa e to be sent as defined in T" *3.+<+ H,<I (i.e. the "M" messa e consists of 1P=:.T.A/P=:.T.ATP:3A"M"=:25&B2/ parts). The M"1AB5/ forwards the "M" messa e to the MM2 in a :ownlin# 3nitdata messa e. ;b. The MM2 encapsulates the "M" messa e in a '." messa e and sends the messa e to the M"A32. ;c- ;d. The M"A32 ac#nowled es receipt of the "M" messa e to the M"1AB5/. ,+. The M"A32 returns a delivery report as defined in T" *3.+<+ H,<I. The delivery report is encapsulated in an '." messa e and sent to the MM2. ,,. The MM2 forwards the delivery report to the M"1AB5/ in an 3plin# 3nitdata messa e. ,*=,3. These steps are performed as defined in T" *3.+<+ H,<I. The delivery report is forwarded to the "1. ,<=,>. &n parallel to steps ,*=,3- the M"1AB5/ ac#nowled es receipt of the delivery report to the M"A32. ,8. The M"1AB5/ indicates to the MM2 that no more '." messa es need to be tunnelled. The MM2 should not use the "Gs /elease /eGuest messa e as a tri er for the release of ", resources. 'OT2E .lthou h the MM2 could use the //1 establishment cause (set to mt=.ccess) sent in the ",=.P &nitial 32 Messa e in step @ to deduce that the M"A32 sent the "ervice /eGuest solely for receivin the "M")the MM2 does not #now whether the MT="M" mi ht cause the initiation of user plane traffic or an MO "M". "o- for simplicity of MM2 implementation- the normal e'ode0 procedures should be used to initiate the release of ", resources.

<.2. Mo)i#e termi(&ti(3 SMS i( 'cti6e Mode

Mobile terminatin "M" in .ctive Mode procedure is specified by reusin the Mobile Terminatin "M" in &dle Mode with the followin modificationE = = There is no need for the MM2 to perform Pa in of the M"A32 after step >. MM2 continues with step @a (i.e. steps 8 to @ are s#ipped). The MM2 immediately sends a :ownlin# 3nitdata to the 32. The MM2 also includes the 2=1G& and T.& in step ;d.

<.2. & Mu#ti$#e Mo)i#e termi(&ti(3 SMS"

&n clause 3.* of T" *<.+,, H*@I- the simultaneous transmission of more than one MT "M" per domain is prohibited. &f the M"1AB5/ has more than one "M" to send- the subseGuent "M" is sent in a :ownlin# 3nitdata messa e after step ,< and instead of the /elease /eGuest in step ,8 of clause @.*.<. i.e. the M"1AB5/ does not need to send another "Gs Pa in messa e.

<.2. ) Simu#t&(eou" Mo)i#e termi(&ti(3 &(d Mo)i#e ori3i(&ti(3 SMS"

The above sections on mobile ori inatin and mobile terminatin "M" handlin in active and idle mode can be reused such that no special treatment is needed for this case.

<.2. c U("ucce""4u# Mo)i#e termi(&ti(3 SMS de#i6er: &ttem$t

.s specified in clause 3.*.@ of T" *3.+<+ H,<I- settin the Mobile "tation 'ot /eachable 7la (M'/7) in the M"1AB5/ is mandatory. ?owever- when usin the "Gs interface- the M"1AB5/ has dele ated the $implicit detach$ functionality to the MM2 (andAor- if 'etwor# Mode of Operation , is in use in G2/.'A3T/.'- to the "G"'). &f an "Gs based MT "M" delivery attempt fails- the M"1AB5/ shall set its M'/7 and send an "Gs interface .lert /eGuest messa e to the MM2. 3pon receipt of .lert /eGuest messa e- MM2 shall set its 'on=2P" .lert 7la ('2.7)

3GPP

%elease &&

.3

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

and if &"/ is activated- the MM2 shall then send an "3 interface .lert=MM2=/eGuest messa e to the "G"'. "G"' shall set the "3 "M" .lert 7la ("".7). &f the MM2 operator #nows (e. . because it is in the ?P5M') that the receivin 32$s ?P5M' deploys "M"=/outerand if the receivin 32$s ?P5M' uses both "M" via M"1 and "M" via "G"'- then the MM2 need not send the .lert= MM2=/eGuest messa e to the "G"' for that 32. 'OT2E The receivin 32$s ?P5M' should ensure that the "M"=/outer in the receivin 32$s ?P5M' only returns "M"=/outer address to the "M"=GM"1 of the sender 32$s P5M'.

"ubseGuently- if the 32 ma#es radio contact with the "G"' and "".7 is set- the "G"' informs the MM2 with an "3 interface 32=.ctivity=&ndication. 3pon receipt of the "3 interface 32=.ctivity=&ndication- or- if the 32 ma#es radio contact with the MM2- the MM2 sends an "Gs .P 32=.ctivity=&ndication messa e to the M"1AB5/. 3pon receipt of an "Gs .P 32=.ctivity=&ndication messa e- or si nallin on the .- &u=cs or Gs interface for that 32- the M"1AB5/ shall inform the ?5/.

<.2. d +o(-SMS Mo)i#e termi(&ti(3 &cti6it: duri(3 SMS de#i6er:

Dhile one or more "M" is bein transferred- other mobile terminatin reGuests (e. . an MT voice call) may arrive in the M"1AB5/. &f this happens the M"1AB5/ continues the "M" activities but shall also send the "Gs Pa in messa e for the non="M" activity to the MM2. The MM2 shall handle this "Gs Pa in messa e as if no "M" transfers are on oin . Typically this should lead to the MM2 invo#in the handoverAcall redirection to G2/.'A3T/.' features and it may lead to disruption of the "M" delivery. The M"1AB5/ and 32 shall recover from any such "M" disruption usin the normal /P and 1P layer retransmission timersAmechanisms.

<.2. e +o(-SMS Mo)i#e ori3i(&ti(3 &cti6it: duri(3 SMS de#i6er:

Dhile one or more "M" is bein transferred- other mobile ori inatin reGuests (e. . an MO voice call or 3"":) may be reGuested by the user. &f this happens the M"A32 continues the "M" activities but shall also send the 2(tended "ervice /eGuest messa e for the non="M" activity to the MM2. The MM2 shall handle this 2(tended "ervice /eGuest messa e as if no "M" transfers are on oin . Typically this should lead to the MM2 invo#in the handoverAcall redirection to G2/.'A3T/.' features and it may lead to disruption of the "M" delivery. The M"1AB5/ and 32 shall recover from any such "M" disruption usin the normal /P and 1P layer retransmission timersAmechanisms.

<.2. 4Mo)i#e Termi(&ti(3 SMS 2%e( 9S! i" &cti6e &(d SG" i" &cti6e )et2ee( MS,1VL! &(d MME
Dhen the MM2 receives the "Gs Pa in messa e for "M"- and &"/ is active- and the 32 is in idle mode- the MM2 sends the ", interface pa in messa e to the 2=3T/.' (usin the "=TM"& as temporary identity) and sends a 1" pa in messa e ("M" indicator) to the "G"' usin the M"1 TM"& as temporary identity (unless the M"1 did not allocate a TM"&- in which case the &M"& is used for pa in ). The 32 is pa ed on 2=3T/.' and by the "G"' on G2/.' andAor 3T/.'. 7or G2/.' .AGb mode- the "G"' sends a P.G&'G 1" messa e to the 0"" (see T" <@.+,@ H3+I). 7or 3T/.'- the "G"' sends a P.G&'G messa e to the 3T/.' (see T" *>.<,3 H*;I) with the 1' :omain &ndicator set to $1" domain$ and the Pa in 1ause set to $Terminatin 5ow Priority "i nallin $. The 32 responds on the cell on which it is camped. Dhen camped on 2= 3T/.'- the 32 responds to the MM2. Dhen camped on G2/.' or 3T/.'- the 32 responds to the M"1.

<.2.6 ,o-E0i"te(ce 2it% SMS o6er 3e(eric 3GPP 9P &cce""

&f the home operator has deployed "M" over eneric 3GPP &P access andAor "M"=&nstant Messa in &nterwor#in as defined in T" *3.*+< H,>I- and has confi ured the networ# and the 32 for usin "M" over &P or "M"=&nstant Messa in &nterwor#in - then an "M" or &M will be delivered over 2P" in any visited networ# whether or not the visited networ# supports "M" over eneric 3GPP &P access. &f the home operator has not deployed "M" over eneric 3GPP &P access and the 32 fails to successfully complete the combined 2P"A&M"& attach procedure in the visited networ# (i.e. the visited networ# supports "M" over eneric 3GPP &P access and does not support "Gs for "M" capability)- then the 32 cannot e(ecute MT or MO "M" procedures in the visited networ#.

3GPP

%elease &&

.-

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

<.3 Loc&tio( Ser6ice" (L,S)

<.3.1 M7-L! $rocedure
<.3.1.1 Ge(er&#

MO=5/ procedure in the 1" fallbac# in 2P" is performed as specified in T" *3.*9, H@I. Dhen the MO=5/ procedure is tri ered by the 32$s application- 32 will chec# the 51" "upport &ndication provided by the .ttach and T.3 procedures as specified in T" *3.<+, H*IE = = &f the 51" "upport &ndication indicates 2P1=MO=5/ is supported- and if the 32 supports 2P1=MO=5/- the 32 stays in 5T2 and initiates the 2P1=MO=5/ procedure. &f 2P1=MO=5/ is not supported by either the networ# or the 32 and if the 51" "upport &ndication indicates 1"= MO=5/ is supported- and the 32 supports 1"=MO=5/- the 32 assumes 1"=MO=5/ is provided. .lso- if 2P1= MO=5/ is not supported by either the networ# or the 32 and if networ# does not provide information on whether 1"=MO=5/ is supported- then 32 assumes 1"=MO=5/ may be provided. &n these cases- if the previous combined 2P"A&M"& .ttach or 1ombined T.A5. 3pdate is accepted with no J"M" onlyJ indication- then the 32 initiates 1" 7allbac# to perform 1"=MO=5/. 0ased on 32 implementation- 32 may avoid initiatin 1"=MO=5/ when an &M" Bo&P session is active.

'OT2E =

Otherwise- the 32 shall not attempt the 2P1=MO=5/ procedure- i.e. neither 2P1=MO=5/ nor 1"=MO=5/ with 1" 7allbac#.

&f the 32 decided to initiate the 1" 7allbac# for the 51" based on 51" "upport &ndication chec#- then- the followin appliesE = Dhen the 32 is in active mode without an &M" Bo&P session- the 32 and the networ# follow the procedure in clause 8.* JMobile Ori inatin 1all in .ctive Mode = P" ?O supportedJ or clause 8.3 JMobile Ori inatin call in .ctive Mode = 'o P" ?O supportedJ. .fter the 32 chan es its /.T from 2=3T/.' to 3T/.'AG2/.'- it performs 1"=MO=5/ procedures as specified in T" *3.*9, H@I. Dhen the 32 is in active mode with an &M" Bo&P session and if the 32 supports "/B11 procedures- the 32 and the networ# follow the procedure in clause @.3.,.* JMO=5/ in .ctive Mode with &M" Bo&P session = P" ?O supportedJ. Dhen the 32 is in active mode without an &M" Bo&P session but the networ# decides not to perform P"= ?andover- then the 32 and the networ# follow the procedure in clause 8.3 JMobile Ori inatin 1all in .ctive Mode = 'o P" ?O "upportJ. .fter the 32 chan es its /.T from 2=3T/.' to 3T/.'AG2/.'- it performs 1"=MO=5/ procedure as specified in T" *3.*9, H@I. Dhen the 32 is in active mode with an &M" Bo&P session and if the 32 supports "/B11 procedures but the networ# decides not to perform P"=?andover- then the 32 and the networ# follow the procedure in clause @.3.,.3 JMO=5/ in .ctive Mode with &M" Bo&P session C 'o P" ?O supportedJ. Dhen 32 is in idle mode- 32 follows the procedure in clause 8.< JMobile Ori inatin 1all in &dle ModeJ. .fter 32 chan es its /.T from 2=3T/.' to 3T/.'AG2/.'- it performs 1"=MO=5/ procedure as specified in T" *3.*9, H@I.

3GPP

%elease &&

..

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

<.3.1.2
UE1MS

M7-L! i( 'cti6e Mode 2it% 9MS Vo9P "e""io( - PS ;7 "u$$orted

e+ode8 8SS1!+S MME MS, SGS+ Ser6i(3 G> P-G>1 GGS+

9MS Vo9P Se""io( 1&. E0te(dedSer6ice !e=ue"t 1). S1-'P !e=ue"t me""&3e 2it% ,S *&##)&cB i(dic&tor 1c. S1-'P !e"$o("e me""&3e 2. 7$tio(&# Me&"ureme(t !e$ort So#icit&tio(

3. S!V,, $rocedure i( 23.216 @20A c#&u"e 6.2.2.2 /&. +'S ,M Ser6ice !e=ue"t /). +'S ,M Ser6ice 'cce$t /c. +'S M7 - L! !e=ue"t . M7-L! $rocedure 4rom Ste$3 i( 23.271 @<A (co(ti(u&tio( o4 M7 L! $rocedure) -

1i#ure 0'3'&'$+&2 3=+4% %e;uest in "+6T%A: while 6" is in 53S )o5P session ,a.=*. These steps are performed as defined in clause 8.*. 3. 0ased on 32 measurement reports and 1" 7allbac# &ndicator in step ,b- the source 2=3T/.' decides to tri er an "/B11 handover to 3T/.'AG2/.'. 1ontinuous "/B11 procedures are continued as specified in T" *3.*,8 H*+I- clause 8.*.*.*. <. .fter sendin a ?andover 1omplete messa e via the /'"A0"" to the M"1 in step 3- the 32 sends a 1M "ervice /eGuest to the M"1 indicatin a reGuest for location services. .fter the ?5/ is updated and the subscriber data are downloaded from the ?5/- the M"1 sends a 1M "ervice .ccept to the 32. Then the 32 sends a '." MO= 5/ /eGuest to the M"1. >. 1ontinuation of MO=5/ procedures as specified in T" *3.*9, H@I- clause ;.*.8. 'OT2E Dhen "/B11 capable 32 is in active mode with an &M" Bo&P session but the networ# does not support "/B11- MM2 sends 2(tended "ervice /eject in response to step ,a based on 2P" bearer informationi.e. MM2 rejects the reGuest if 32 has 2P" bearer with N1&S,- i.e. &M" Bo&P session.

<.3.1.3

M7-L! i( 'cti6e Mode 2it% 9MS Vo9P "e""io( - +o PS ;7 "u$$orted

The same procedure as described in clause @.3.,.* applies for JMO=5/ in .ctive Mode with &M" Bo&P session = 'o P" ?O supportedJ case e(cept that the "/B11 procedure in step 3 follows T" *3.*,8 H*+I- clause 8.*.*.,a.

3GPP

%elease &&

./

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

<.3.2 MT-L! $rocedure

<.3.2.1 MT-L! $rocedure i4 UE i" (ot i( 9MS Vo9P "e""io(

1i#ure 0'3'$'&+&2 3T+4% procedure if 6" is not in 53S )o5P session ,. M"1 receives a P/OB&:2P"30"1/&02/P5O1.T&O' messa e due to 1"=MT=5/ (T" *3.*9, H@Iclause ;.,.*). *. M"1 sends Pa in (51" 1lient &dentity- 51" indicator) messa e to MM2. 3. &f the MM2 did not return the J"M"=onlyJ indication to the 32 durin .ttach or 1ombined T.A5. 3pdate procedures- the MM2 sends Pa in (parameters as specified in T" *3.<+, H*I- 1' :omain &ndicator- 51" 1lient &dentity- 51" indicator) messa e to 32. 51" indicator is used to inform the 32 that this pa in if for MT=5/ reGuest. 51" 1lient &dentity and 51" indicator are only included in 1" Pa e if 32 is in active mode. &f the MM2 returned the J"M"=onlyJ indication to the 32 durin .ttach or 1ombined T.A5. 3pdate procedures- the MM2 shall not send Pa in to the 32- and the MM2 sends 1" Pa in /eject towards M"1 to stop 1" Pa in procedure and this 1"70 procedure stops. <. 32 responds with Pa in P/esp messa e in 3MT"AG2/.'. "ervice based redirectionAreselection or P" ?andover may ta#e place as specified in clause 9. >. M"1 continues with the 1"=MT=5/ procedure as defined in T" *3.*9, H@I- clause ;.,.*.

3GPP

%elease &&

.(

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

<.3.2.2

MT-L! $rocedure 2%i#e UE i" i( 9MS Vo9P "e""io(

1i#ure 0'3'$'$+&2 3T+4% procedure while 6" is in 53S )o5P session ,. M"1 receives a P/OB&:2P"30"1/&02/P5O1.T&O' messa e due to 1" MT 5/ (T" *3.*9, H@Iclause ;.,.*). ,a. The M"1 responds by sendin a Pa in /eGuest (51" 1lient &dentity- 51" indicator) to the MM2 over a "Gs interface. The M"1 only sends a 1" Pa e for an 32 that provides location update information usin the "Gs interface. The MM2 has an established ", connection for &M" Bo&P session. &f the MM2 did not return the J"M"=onlyJ indication to the 32 durin .ttach or 1ombined T.A5. 3pdate procedures- the MM2 sends Pa in (parameters as specified in T" *3.<+, H*I- 1' :omain &ndicator- 51" 1lient &dentity- 51" indicator) messa e to 32. 51" indicator is used to inform the 32 that this pa in is for MT=5/ reGuest. &f the MM2 returned the J"M"=onlyJ indication to the 32 durin .ttach or 1ombined T.A5. 3pdate procedures- the MM2 shall not send Pa in to the 32- and the MM2 sends 1" Pa in /eject towards M"1 to stop 1" Pa in procedure and this 1"70 procedure stops. The e'ode0 forwards the pa in messa e to the 32. ,b. 32 sends an 2(tended "ervice /eGuest (/eject or .ccept) messa e to the MM2 for mobile terminatin 1" 7allbac#. The 2(tended "ervice /eGuest messa e is encapsulated in //1 and ",=.P messa es. The 32 may decide to reject 1"70 based on 51" 1lient &dentity. ,c. 3pon receivin the 2(tended "ervice /eGuest (/eject) for mobile terminatin 1" 7allbac#- the MM2 sends Pa in /eject towards M"1 to stop 1" Pa in procedure and this 1"70 procedure stops. 1orrespondin error handlin is returned to the GM51 as specified in T" *3.*9, H@I. ,d. MM2 sends an ",=.P /eGuest messa e to e'ode0 that includes the 32 /adio 1apabilities and a 1" 7allbac# &ndicator. This messa eE indicates to the e'ode0 that the 32 should be moved to 3T/.'AG2/.'. ,e. The e'ode0 shall reply with ",=.P /esponse messa e. *. These steps are performed as defined in clause 9.3 for P" handover supported case and clause 9.< for 'o P" handover supported case. 3. 0ased on 32 measurement reports and 1" 7allbac# &ndicator in step ,d- the source 2=3T/.' decides to tri er an "/B11 handover to 3T/.'AG2/.'. 1ontinuous "/B11 procedures as specified in T" *3.*,8 H*+Iclause 8.*.*.* for P" handover supported case and clause 8.*.*.,a for 'o P" ?O supported case are performed.

3GPP

%elease &&

.0

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

<. .fter receivin /elocationA?andover 1omplete messa e from the /'"A0"" in step 3- M"1 sends 51" 5ocation 'otification &nvo#e to the 32. >. 1ontinuation of 1"=MT=5/ procedures as specified in T" *3.*9, H@I- clause ;.,.*. 'OT2E Dhen "/B11 capable 32 is in active mode with an &M" Bo&P session but the networ# does not support "/B11- MM2 sends Pa in /eject towards M"1 and this 1"70 procedure stops. This is based on the bearer information at MM2 indicatin 32 has &M" Bo&P session- i.e. 2P" bearer with N1&S,.1orrespondin error handlin is returned to the GM51 as specified in T" *3.*9, H@I.

<.3.3 +9-L! $rocedure

'&=5/ procedure ta#es place durin emer ency calls- and is thus performed in G2/.'A3T/.' durin the Mobile Ori inatin call procedure.

<.3./ !etur(i(3 )&cB to E-UT!'+

Once 1" service ends in 1" domain- e(istin mechanisms as specified in T" *3.<+, H*I can be used to move the 32 to 2=3T/.'- no specific 1" 7allbac# mechanisms are needed. :urin the release of an // connection the M"1 should indicate to G2/.'A3T/.' that the // connection (for call or 1&"" or 51") was established as a result of 1" fallbac#. G2/.' and 3T/.' may use the indication to determine which of the e(istin mechanisms that should be used to move the 32 to 2=3T/.'.

<.3. ,o-E0i"te(ce 2it% 7t%er Loc&tio( Ser6ice"

<.3. .1 ,o-E0i"te(ce 2it% SUPL

There is no race condition between OM. .: "3P5 H;I and 1" 7allbac# for 51". Dhen networ# initiated "3P5 procedure ta#es place- the pa in messa e does not contain 1' :omain &ndicator by default. This prevents 1" 7allbac# for 51" to ta#e place. 7or "2T initiated "3P5 procedure- chan in of /.T does not ta#e place.

<./ 7t%er ,S Ser6ice"

<./.0 Ge(er&#
The procedures specified in this clause apply when the 32 is 2P"A&M"& attached and the 1" domain is chosen by the 32 andAor the home P5M' to deliver other types of 1" services- i.e. services not covered e(plicitly in previous sections- such as 1all &ndependent "upplementary "ervices- real time end=to=end facsimile roup 3 servicesT" *3.,<8 H<,I- etc.

<./.1 Mo)i#e-9(iti&ted ,S Ser6ice"

Dhen 32 is in active mode- 32 and the networ# follow the procedure in clause 8.* JMobile Ori inatin 1all in .ctive=ModeJ. .fter 32 chan es its /.T from 2=3T/.' to 3T/.'AG2/.'- it performs Mobile=&nitiated 1" procedures relevant to the initiated 1" service- e. . 1all &ndependent "upplementary "ervice procedure as specified in T" *<.+,+ H,3I- real time end=to=end facsimile roup 3 procedure as specified in T" *3.,<8 H<,I- etc. Dhen 32 is in active mode and networ# initiates '.11 procedure- then 32 and the networ# follow the procedure in clause 8.3 JMobile Ori inatin 1all in .ctive Mode = 'o P" ?O "upport in G2/.'J. .fter 32 chan es its /.T from 2=3T/.' to 3T/.'AG2/.'- it performs Mobile=&nitiated 1" procedures relevant to the initiated 1" service- e. . "upplementary "ervice procedure as specified in T" *<.+,+ H,3I- real time end=to=end facsimile roup 3 procedure as specified in T" *3.,<8 H<,I- etc. Dhen 32 is in idle mode- 32 and the networ# follows the procedure in clause 8.<. .fter 32 chan es its /.T from 2=3T/.' to 3T/.'AG2/.'- it performs Mobile=&nitiated 1" procedures relevant to the initiated 1" service- e. . "upplementary "ervices procedure as specified in specifications such as T" *3.+;+ H,+I- real time end=to=end facsimile roup 3 procedure as specified in T" *3.,<8 H<,I- etc.

3GPP

%elease &&

.,

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

<./.2 +>-9(iti&ted ,S Ser6ice"

MS,1VL! 1. Tri33er 2. P&3i(3 3. P&3i(3 MME UE

/. Procedure" 5e4i(ed i( ,#&u"e MMo)i#e Termi(&ti(3 ,&##M . P&3i(3 !e"$o("e ,S Ser6ice $rocedure co(ti(ue"
1i#ure 0'-'$+&2 :?+5nitiated CS Service procedure ,. M"1AB5/ receives a tri er for a 'D=&nitiated 1" procedure. *. M"1AB5/ sends Pa in messa e to MM2. 7or call independent supplementary service- the Pa in messa e may include the "" service &:. 3. &f the MM2 did not return the J"M"=onlyJ indication to the 32 durin .ttach or 1ombined T.A5. 3pdate procedures- the MM2 sends Pa in (parameters as specified in T" *3.<+, H*I- 1' :omain &ndicator) messa e to 32. 7or call independent supplementary service the Pa in messa e may include the "" service &:. "" service &: is used to indicate the type of the supplementary service (e. . 3"":) to the 32. The "" service &: is only included in 1" Pa e if 32 is in active mode. &f the MM2 returned the J"M"=onlyJ indication to the 32 durin .ttach or 1ombined T.A5. 3pdate procedures- the MM2 shall not send the Pa in to the 32- and the MM2 sends 1" Pa in /eject towards M"1 to stop 1" Pa in procedure and this 1"70 procedure stops. <. The mobile terminatin call procedure then ta#es place as specified in clause 9 JMobile Terminatin 1all ProcedureJ. >. Once the pa in is successfully returned to M"1- the applicable 1" procedures continues- e. . for "upplementary "ervice as specified in specifications such as T" *3.+;+ H,+I.

<./.3 !etur(i(3 )&cB to E-UT!'+

Once 1" service ends in 1" domain- e(istin mechanisms as specified in T" *3.<+, H*I can be used to move the 32 to 2=3T/.'- no specific 1" 7allbac# mechanisms are needed. :urin the release of an // connection the M"1 should indicate to G2/.'A3T/.' that the // connection (for call or 1&"" or 51") was established as a result of 1" fallbac#. G2/.' and 3T/.' may use the indication to determine which of the e(istin mechanisms that should be used to move the 32 to 2=3T/.'.

3GPP

%elease &&

/*

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

'((e0 'Void

3GPP

%elease &&

/&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

'((e0 8 ((orm&ti6e),S *&##)&cB to 10!TT

This anne( describes a 1" 7allbac# to ,(/TT and an "M" solution for dual mode ,(/TTA2=3T/.' terminals. 1" 7allbac# to ,(/TT is supported for 32s with both sin le /( and dual /( confi uration (see T" 38.33, H33I). 32s with sin le /( confi uration are not able to camp in ,(/TT when they are active in 2=3T/.'. The networ# therefore provides mechanisms for the 32 to perform re istration to ,(/TT- receive ,(/TT pa in - "M" etc. while the 32 is in 2=3T/.'. 32s with dual /( confi uration can camp in ,(/TT while they are active in 2=3T/.'- they may however not be able to stay in 2=3T/.' when they handle a 1" call andAor perform re istration si nallin - andAor sendin or receivin "M" in ,(/TT. 1lause 0., and 0.* describes the architecture and procedures for 1" 7allbac# (and enhanced 1" 7allbac#) to ,(/TT when the 32 has sin le /(- dual /(- or dual /(AT( confi uration. &n this scenario the networ# need to support the ",+* interface between the MM2 and ,(1" system in order to support 1" 7allbac# (this is indicated by the presence of 1"70 re istration parameters on 2=3T/.' broadcast channel- T" 38.33, H33I). 1lause 0.3 describes the procedures for 1" 7allbac# when the 32 has dual /( confi uration. &n this scenario the networ# needs to support the 2(tended "ervice /eGuest procedure in order to support 1" 7allbac# (this is indicated by either the presence of 1"70 re istration parameters or indication of support for dual r( 1"70 on 2=3T/.' broadcast channel- T" 38.33, H33I). &f the 32 has a dual /( confi uration and indicates support for enhanced 1" fallbac# to ,(/TT in the 32 radio capabilities- the principles and procedures in clauses 0., and 0.* are followed when the networ# indicates support for ",+*.

8.1

76er&## 5e"cri$tio(

8.1.1 Ge(er&# ,o("ider&tio("

The 1" fallbac# for ,(/TT in 2P" enables the delivery of 1"=domain services (e. . 1" voice) by reuse of the ,(1" infrastructure when the 32 is served by 2=3T/.'. . 1" fallbac# enabled terminal- while connected to 2=3T/.' may re ister in the ,( /TT 1" domain in order to be able to use ,(/TT access to establish one or more 1" services in the 1" domain. The 1" 7allbac# function is only available where 2=3T/.' covera e overlaps with ,(/TT covera e. This specification also specifies the architecture reGuired for "M" over ",+* in 2P". The MO "M" and MT "M" are tunnelled in 2P" and over ",+* and do not cause any 1" 7allbac# to 1:M. ,(/TT- and conseGuently does not reGuire any overlapped 1:M. ,(/TT covera e. 1" 7allbac# to ,(/TT and &M"=based services shall be able to co=e(ist in the same operator$s networ#. 1" 7allbac# to ,(/TT with P" ?andover procedure to ?/P: access for Optimised ?O- non=Optimised ?O- and Optimised &dle mode mobility as defined in T" *3.<+* H*9I shall be able to co=e(ist in the same operator$s networ#.

8.1.2 !e4ere(ce 'rc%itecture

The 1" fallbac# to ,(/TT and "M" over ",+* in 2P" function is realised by reusin the ",+* reference point between the MM2 and the ,(1" &D". The reference architecture described in fi ure 0.,.*=, is similar to the "/B11 architecture for 2=3T/.' to 3GPP* ,(1" described in T" *3.*,8 H*+I- with the additional aspect that the ",+* session is lon =lived (similar to pre=re istration for ",+,).

3GPP

%elease &&

/$

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

10,S ,S*8 UE

10!TT ,S 'cce""

'1 '1 10,S 9>S S102 MME

10!TT MS,

S1-MME 10,S ,S*8 UE E-UT!'+ S1-U

S11 Ser6i(31P5+ G> SGi

Tu((e##ed 10!TT me""&3e"

1i#ure >'&'$+&2 %eference architecture for CS fall ac! to &@%TT CS /eference architecture for P" handover procedure between 2=3T/.' and ?/P: access is defined in T" *3.<+* H*9I.

8.1.2.1 !e4ere(ce $oi(t"

S102E &t is the reference point between the MM2 and the ,(1" &D". The ",+* reference point provides a tunnel between MM2 and 3GPP* ,(1" &D" 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 H,8I and 3GPP* .."+++; H,9I.

8.1.3 *u(ctio(&# e(titie"

8.1.3.1 UE
The 32 capable of 1" fallbac# to ,(/TT and "M" over ",+* supports access to 2=3T/.'A2P1 as well as access to the ,(1" domain over ,(/TT. &t supports the followin additional functionsE = = = = = = ,(/TT 1" re istration over the 2P" after the 32 has completed the 2=3T/.' attachmentF ,(/TT 1" re=re istration due to mobilityF 1" fallbac# procedures specified for ,(/TT 1" domain voice serviceF Procedures for mobile ori inated and mobile terminated "M" tunnelled over 2P" and ",+*F &ncludes enhanced 1" fallbac# to ,(/TT capability indication as part of the 32 radio capabilitiesF &ncludes concurrent ,(/TT and ?/P: capability indication as part of the 32 radio capabilities if supported by the enhanced 1" fallbac# to ,(/TT capable 32.

&f the 32 is service user with subscription to 1" domain priority service- the 32$s 3"&M belon s to one of the special .ccess 1lasses as specified in T" **.+,, H3@I and the 32 shall set the //1 establishment cause to J?i hPriority.ccessJ as specified in T" 38.33, H33I.

8.1.3.2 MME
The MM2 enabled for 1" fallbac# to ,(/TT supports the followin additional functionsE

3GPP

%elease &&

/3

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

&t serves as a si nallin tunnellin end point towards the 3GPP* ,(1" &D" via ",+* interface for sendin Areceivin encapsulated 3GPP* ,(1" si nallin messa es toAfrom the 32- which are encapsulated in ",= MM2 ", &nformation Transfer messa es- as defined in T/ 38.;3@ H,;IF ,(1"=&D" (terminatin ",+* reference point) selection for 1"70 proceduresF ?andlin of ",+* tunnel redirection in case of MM2 relocationF 0ufferin of messa es received via ",+* for 32s in idle state.

= = =

&f the networ# supports 1"70 priority call handlin - the MM2 supports the followin additional functionsE = 7or pa e messa e received on the ",+* interface with priority indication- the MM2 provides preferential treatment to this messa e and also the subseGuent 1" fallbac# procedure compared to other normal transactions. &f 32 needs to be pa ed- the MM2 sets priority indication on the pa in reGuest to e'ode0. The MM2 also sets priority indication- i.e. J1"70 ?i h PriorityJ- in ",.P messa e to the e'ode0- so that e'ode0 may initiate the 1"70 procedure with priority- as specified in T" 38.<,3 H3>I. 7or a 1"70 reGuest from service user- the MM2 determines that the 1"70 reGuest need priority handlin based on the 32$s 2P" subscription information. The MM2 in con estion situation provides preferential treatment to this reGuest and also sets priority indication- i.e. J1"70 ?i h PriorityJ- in ",.P messa e to e'ode0 to initiate 1"70 procedure- as specified in T" 38.<,3 H3>I.

8.1.3.3 E-UT!'+
The 2=3T/.' enabled for 1" fallbac# to ,(/TT supports the followin additional functionsE = = = = = Provision of control information that causes the 32 to tri er ,(1" re istrationF 7orwardin ,( /TT 1" pa in reGuest to the 32F 7orwardin ,( /TT 1" related messa es between MM2 and 32F /elease of 2=3T/.' resources after 32 leaves 2=3T/.' covera e subseGuent to a pa e for 1" fallbac# to ,(/TT 1" if P" handover procedure is not performed in conjunction with ,(1" fallbac#F &nvo#in the optimised or non=optimised P" handover procedure concurrently with enhanced ,(1" fallbac# procedure when supported by the networ# and 32- and based on networ# confi uration.

&f the networ# supports 1"70 priority call handlin - the 2=3T/.' supports the followin additional functionsE = = 7or pa e messa e received on ",.P with priority indication- the 2=3T/.' should provide preferential treatment to this reGuest compared to other normal pa in reGuests. 7or 1" fallbac# ",.P messa e with priority indication and if the 32 is idle- the 2=3T/.' should provide preferential treatment in allocatin 2=3T/.' radio bearer resources compared to other normal resource reGuests. .lso- 2=3T/.' shall not tri er enhanced ,(1"70 with concurrent optimi!ed P" handover to ?/P: access.

8.1./ ,o-e0i"te(ce 2it% 9MS "er6ice"

1lause <.< of this specification also applies here.

8.1. ,S*8 Priorit: ,&## ;&(d#i(3

Priority call handlin support for 1"70 ensures that end=to=end priority handlin is provided for both mobile ori inated 1"70 calls by a service user in 2=3T/.' and for mobile terminated 1"70 call from a service user to a normal or service user in 2=3T/.'. . service user$s 2P" subscription information contains an indication of the users ,(/TT 1" domain priority status- i.e. a MP" 1" priority. &f the 32 is subscribed to 1" domain priority- the 32$s 3"&M shall belon to one of special .ccess 1lasses as specified in T" **.+,, H3@I.

3GPP

%elease &&

/-

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

7or mobile terminated 1" fallbac# calls from a service user- the ,( M"1 via the ,(1" &D" provides a priority indication to the MM2 alon with a pa e messa e. The MM2 shall set a priority indication to the e'ode0 when reGuestin the e'ode0 to pa e the 32 if the 32 is idle. 7or mobile ori inated 1" fallbac# calls from a service user in 2=3T/.'- the MM2 determines that the 1"70 reGuires priority handlin based on the MP" 1" priority in the 32$s 2P" subscription. 7or both mobile ori inated and mobile terminated 1"70- the MM2 shall also provide priority indication- i.e. J1"70 ?i h PriorityJ- when reGuestin the e'ode0 to e(ecute the 1"70 priority procedure. The e'ode0 should handle the pa e messa e with priority and also prioriti!e the subseGuent 1" fallbac# procedure to ,(/TT as specified in T" 38.<,3 H3>I.

8.2

Procedure"

8.2.1 Mo)i#it: M&(&3eme(t

8.2.1.1 10 !TT ,S Pre-!e3i"tr&tio( o6er EPS Procedure
This clause describes how the 32 in an 2=3T/.' system establishes and maintains pre=re istration in the ,(1" system.

1i#ure >'$'&'&+&2 &@%TT CS re#istration procedure ,. The 32 attaches to 2=3T/.' as specified in T" *3.<+, H*I. The 32 includes an indication of enhanced 1" fallbac# to ,(/TT and may also include concurrent ,(/TT and ?/P: P" session handlin capabilities as part of the 32 radio capabilities. &f the 32 is a service user with subscription to ,( priority service in the ,(/TT 1" domain- the 32$s 2P" subscription contains MP" 1" priority.

3GPP

%elease &&

/.

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

*. 0ased on a radio layer tri er (e. . an indication from the 2=3T/.' when the 32 is in connected state or an indication over the broadcast channel)- the 32 decides to re ister with the ,(/TT 1" domain. 3. &f the 32 is in idle state- in order to create a si nallin connection with the MM2- it performs the "ervice /eGuest procedure. <. The 32 enerates a ,(/TT 1" re istration reGuest. <a. The ,(/TT 1" messa e is transferred from the 32 to 2=3T/.'. <b. 2=3T/.' forwards the ,(/TT 1" messa e to the MM2 includin the 1:M.*+++ /eference 1ell &:. <c. The MM2 selects a ,(1" &D" node based on the 1:M.*+++ /eference 1ell &:. The &M"& is used to distin uish ",+* si nallin transactions belon in to different 32s. The MM2 sends a ",+* :irect Transfer messa e (&M"&- ,(1" messa e) to the ,(1" &D" node. >. ,(/TT 1" re istration is then performed by the ,(1" &D" node based on 3GPP* .."+++@ H,8I. 8a. ,(/TT 1" re istration response is tunnelled bac# to the MM2 in a ",+* :irect Transfer messa e (&M"&- ,(1" messa e). 8b. The MM2 forwards the ,(/TT 1" messa e to the 2=3T/.'. 8c. The 2=3T/.' forwards the ,(/TT 1" messa e to the 32. &f the tri ers for ,(1" re istration chan e over time- the 32 (both in idle or connected state)- uses this information to update the ,(1" re istration via the tunnel.

8.2.1.2 S102 Tu((e# !edirectio(

",+* Tunnel /edirection Procedure is used when the 32 perform Trac#in .rea 3pdate with MM2 chan e while the 32 is re istered with the ,(/TT 1" domain as described in clause 0.*.,., and the ",+* session e(ists between the MM2 and the ,(1" &D". The detail procedure for the idle case is depicted as fi ure 0.*.,.*=,.

1i#ure >'$'&'$+&2 S&*$ tunnel redirection durin# TA6 with 33" chan#e ,. 32 performs ,(=re istration over the source MM2 while in 21M=1O''21T2: state- followed by transition to 21M=&:52 state. The ",+* tunnel e(ists between the source MM2 and the ,(1" &D". *. T.3 procedure with MM2 chan e as described in T" *3.<+, H*I- fi ure >.3.3.,=,- up to and includin the step where the tar et MM2 receives 3pdate 5ocation .c# from the ?""- is e(ecuted. The ,(1" &D" &: is transferred to the tar et MM2 via the 1onte(t /esponse messa e. 3. The tar et MM2 sends ",+* /edirection 1ommand messa e to the ,(1" &D". .fter receivin this messa e- the ,(1" &D" associates the ",+* tunnel for this specific 32 with the tar et MM2. Then the ,(1" &D" releases any conte(t associated with the source MM2.

3GPP

%elease &&

//

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

<. &n response to the ",+* /edirection 1ommand messa e- the ,(1" &D" sends a ",+* /edirection .c# messa e to the tar et MM2. >. The T.3 procedure is completed. The detailed procedure for the active case is depicted as fi ure 0.*.,.*=*.

1i#ure >'$'&'$+$2 S&*$ tunnel redirection durin# inter+e:ode> handover with 33" relocation ,. 32 performs ,(=re istration over the source MM2 while in 21M=1O''21T2: state. The ",+* tunnel e(ists between the source MM2 and the ,(1" &D". *. &nter=e'ode0 handover with MM2 relocation procedure as described in T" *3.<+, H*I- fi ure >.>.,.*.*=,- steps prior to T.3- is e(ecuted. The ,(1" &D" &: is transferred to the tar et MM2 via the 7orward /elocation /eGuest messa e. 3. The tar et MM2 sends ",+* /edirection 1ommand messa e to the ,(1" &D". .fter receivin this messa e- the ,(1" &D" associates the ",+* tunnel with the tar et MM2. Then the ,(1" &D" releases any conte(t associated with the source MM2. <. &n response to the ",+* /edirection 1ommand messa e- the ,(1" &D" sends a ",+* /edirection .c# messa e to the tar et MM2. >. The T.3 procedure occurs.

8.2.1.3 UE-i(iti&ted 5et&c% Procedure

&f a ,(/TT 1" 7allbac# 32- pre=re istered to the ,(/TT 1" system- initiates the detach procedure in 2=3T/.' access due to switch off and the 32 is reGuired to perform a Jpower=down re istrationJ in the ,(/TT 1" system (see 1."+++>=. H3*I)- the 32 shall first perform the Jpower=down re istrationJ procedure with the ,(/TT 1" system via the ",+* tunnel- before initiatin the detach procedure in 2=3T/.' access as specified in T" *3.<+, H*I. . ,(1"7 32- pre=re istered to the ,(1" system- performin detach due to reasons other than switch off is not reGuired to perform Jpower=down re istrationJ with the ,(1" system prior to performin the detach procedure in 2=3T/.'.

8.2.2 Mo)i#e 7ri3i(&ti(3 ,&## i( 'cti6e Mode

This clause describes the mobile ori inatin call procedures for the 1" 7allbac# to ,(/TT in the normal case. 7or enhanced 1" fallbac# to ,(/TT procedure- see clause 0.*.3a. 1lause 0.*.3b describes the procedure when the procedure is rejected by the MM2.

3GPP

%elease &&

/(

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

1 0,S ,S*8 UE

EUT!'+

MME

1 0,S 9>S

1 0!TT MS,

S -G> 1 P -G>

1. UE i" E -UT!'+ &tt&c%ed &(d re3i"tered 2it% 2. UE deci"io( to $er4orm M7 c&## i( 1 0,S 3. E0te(ded Ser6ice !e=ue"t /. UE ,o(te0t Modi4ic&tio( !e=ue"t /. UE ,o(te0t Modi4ic&tio( !e"$o("e

1 0!TT ,S

. 7$tio(&# me&"ureme(t re$ort "o#icit&tio( 6 . E -UT!'+ tri33er" !!, co((ectio( re#e&"e 2it% redirectio( 7. S1 UE ,o(te0t !e#e&"e !e=ue"t <. Su"$e(d +oti4ic&tio( 9. Su"$e(d 'cB(o2#ed3e

10. UE ,o(te0t !e#e&"e

11 . 10 M7 c&## e"t&)#i"%me(t $er

3GPP 2 "$eci4ic&tio("

1i#ure >'$'$+&2 CS 3= call usin# fall ac! to C93A &@ %TT networ! ,. 32 is 2=3T/.' attached and re istered with ,(/TT 1" as defined in clause 0.*.,.,. *. 32 ma#es a decision to perform a mobile ori inated 1" call. 3. 32 sends an 2(tended "ervice /eGuest for mobile ori inatin ,(1" fallbac# to the MM2. <. MM2 sends 32 1onte(t Modification /eGuest (1" 7allbac# &ndicator- priority indicator) to 2=3T/.'. 1" 7allbac# &ndicator indicates to the 2=3T/.' to move the 32 to ,(/TT. &f MM2 determines the 1" 7allbac# procedure needs priority handlin based on the MP" 1" priority in the 32$s 2P" subscription- it sets priority indication in the ",.P messa e to the 2=3T/.'. 2=3T/.' responds with 32 1onte(t Modification /esponse >. 2=3T/.' may optionally solicit a ,(/TT measurement report from the 32 to determine the tar et ,(/TT cell to which the 1" 7allbac# will be performed. 8a. The 2=3T/.' tri ers //1 connection release with redirection to ,(1" and continue with step 9. 9. 2=3T/.' sends an ", 32 1onte(t /elease /eGuest (1ause) messa e to the MM2. 1ause indicates that the ", 32 1onte(t /elease was caused by 1" fallbac# to ,(/TT. &n case the 1ause indicates that //1 was released due to abnormal conditions- e. . radio lin# failure- the MM2 should continue with steps @ =,+. @. The MM2 deactivates G0/ bearers towards "=GD and P=GD(s) by initiatin MM2=initiated :edicated 0earer :eactivation procedure as specified in T" *3.<+, H*I- and starts the preservation and suspension of non=G0/

3GPP

%elease &&

/0

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

bearers by sendin "uspend 'otification messa e to the "=GD. The "=GD releases all e'ode0 related information (address and T2&:s) for the 32- and sends "uspend 'otification messa e to the P=GD(s). ;. "=GD and P=GD(s) ac#nowled es the bearer updates by respondin with "uspend .c#nowled e. The MM2 stores in the 32 conte(t that 32 is in suspended status. .ll the preserved non=G0/ bearers are mar#ed as suspended status in "=GD and P=GD. The P=GD discards downlin# data if the 32 is mar#ed as suspended. ,+. ", 32 1onte(t in the 2=3T/.' is released as specified in T" *3.<+, H*I. ,,. 32 moves to ,(/TT and performs the procedure for mobile ori inatin call as specified in 3GPP* .."++,3 H,@I. Once 1" service ends in the ,(1" domain- the 32 returns to 2=3T/.' by performin reselection. The 2P" service is resumed as described in clause 8.>.

8.2.2& Mo)i#e 7ri3i(&ti(3 c&## i( 9d#e Mode

Mobile Ori inatin call in &dle Mode procedure is specified by reusin the Mobile Ori inatin 1all in .ctive mode procedure with 2(tended "ervice /eGuest for mobile ori inatin ,(1" fallbac# to the MM2 where the messa es ",=.P 32 conte(t Modification /eGuest and /esponse are replaced by ",=.P &nitial 32 1onte(t /eGuest and /esponse. 32 is transited to 21M=1O''21T2: mode by followin the applicable procedures specified in T" *3.<+, H*I. &f 32 has only 5&P. P:' connection and the cell accessed by the 32 does not lin# to the 5=GD where the 32 had the 5&P. P:' 1onnection- the MM2 shall reject the 2(tended "ervice /eGuest with a reason code which results in the 32 selectin ,(/TT access as specified in T" *<.3+, H3<I. &f the 32 is a service user with subscription to 1" domain priority service- the 32$s 3"&M shall belon to one of special .ccess 1lasses as specified in T" **.+,, H3@I and sets the //1 establishment cause to J?i hPriority.ccessJ as specified in T" 38.33, H33I. &f the networ# supports a priority call handlin - the MM2 determines that the 2(tended "ervice /eGuest reGuires priority handlin of 1" 7allbac# based on the J?i hPriority.ccessJ establishment cause forwarded by e'ode0 to the MM2 andAor MP" 1" priority in the 32$s 2P" subscription. .ccordin to operator policythe MM2 may use MP" 1" priority to verify the priority handlin of the 1" 7allbac# procedure. &f MM2 decides to perform 1" 7allbac# with priority- it sets priority indication in the ",=.P &nitial 32 1onte(t /eGuest messa e to the e'ode0. The e'ode0 should allocate radio bearer resources to the 32 preferentially compared to other normal calls.

8.2.3 Mo)i#e Termi(&ti(3 ,&##

This clause describes the mobile terminatin call procedures when the 32 accepts or rejects 1" pa in for the 1" 7allbac# to ,(/TT- in the normal case. 1lause 0.*.3b describes the procedure when the procedure is rejected by the MM2. Dhen the ,( M"1 receives a re istration from a 32- it ma#es note of the /.' eGuipment from which it received the re istration. "ubseGuent pa in activities may thus be directed toward that /.' eGuipment. ?owever- pa in activities by the ,(M"1 are not limited to the sin le /.' eGuipment from which the re istration was received. The M"1 may choose to pa e a wider area- includin inter=system pa in . &f the ,(M"1 has direct interfaces to ,(1" &D"- as well as to ,(/TT access- the M"1 may choose to do direct pa in activities to both 2=3T/.' and ,( /.' eGuipments in its attempts to contact the 32. The ,( pa in reGuest sent by the ,(M"1 to the ,(1" &D" is delivered to the 32 via the tunnel. The 32 tunes to ,(/TT access- ac#nowled es the ,( pa e and performs the ,(1" procedures for mobile terminated call. The detailed procedure usin //1 connection release with redirection to ,(1" is described in fi ure 0.*.3=,. 7or enhanced ,(/TT 1" 7all 0ac# procedure- see clause 0.*.3a.

3GPP

%elease &&

/,

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

/ ' "@tended Service %e;uest

1i#ure >'$'3+&2 CS 3T call usin# fall ac! to C93A &@ %TT networ! ,. 32 is 2=3T/.' attached and pre=re istered with ,(/TT 1" as defined in clause 0.*.,.,. *. ,(M"1 sends a pa in reGuest to the ,(1" &D" node with 1aller 5ine &dentification if available. &f the call is ori inated by a priority user or an emer ency callbac# from P".P- the pa in reGuest messa e from the ,(/TT M"1 to the &D" contains a priority value or an emer ency indicator- respectively- as specified in 3GPP* specification .."+++@=1 v3.+ H3;I A .."+++;=1 v3.+ H<+I. 3. ,(1" &D" node forwards the ,( /TT 1" pa in reGuest via the ",+* tunnel to the MM2. &f a priority value or emer ency indication was received in the previous step- the ",+* messa e also reflects the same. <. &f the 32 is in idle state- the MM2 performs the networ# initiated "ervice /eGuest procedure in order to brin the 32 to active state prior to tunnellin of the ,( /TT 1" pa in reGuest toward the 32. &f the ",+* messa e contains a priority value or emer ency indication- the MM2 also sets priority indication in the ",.P pa in reGuest messa e to the 2=3T/.'. The 2=3T/.' handles the pa in process with priority.

3GPP

%elease &&

(*

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

Dhen the MM2 receives subseGuent 2(tended "ervice /eGuest from the 32- it detects this messa e is the response to the priority 1" 7allbac# procedure initiated in step 3. The MM2 also sets the priority indication in the ",.P 32 1onte(t "etup messa e to the 2=3T/.'. >. MM2 forwards the ,(/TT 1" pa in reGuest to the 32. 8a. Boid. 8b. &f the 32 accepts 1" pa in for the 1" 7allbac# to ,(/TT- the 32 sends an 2(tended "ervice /eGuest for mobile terminatin ,(1" fallbac# to the MM2 and proceeds with step 9 to step ,> below. 9. MM2 sends 32 1onte(t Modification /eGuest (1" 7allbac# &ndicator) to indicate the 2=3T/.' to move the 32 to ,(/TT. &f priority value or emer ency indication was received in "tep 3- the MM2 also sets priority indication to the 2= 3T/.'. The 2=3T/.' provides preferential treatment to this call in the subseGuent steps. 2=3T/.' responds with 32 1onte(t Modification /esponse. @. 2=3T/.' may optionally solicit a ,(/TT measurement report from the 32 to determine the tar et ,(/TT cell to which the 1" 7allbac# will be performed. ;. 2=3T/.' tri ers //1 connection release with redirection to ,(1". ,+. 2=3T/.' sends an ", 32 1onte(t /elease /eGuest (1ause) messa e to the MM2. 1ause indicates that the ", 32 1onte(t /elease was caused by 1" fallbac# to ,(/TT. ,,. The MM2 deactivates G0/ bearers towards "=GD and P=GD(s) by initiatin MM2=initiated :edicated 0earer :eactivation procedure as specified in T" *3.<+, H*I- and starts the preservation and suspension of non=G0/ bearers by sendin "uspend 'otification messa e to the "=GD. The "=GD releases all e'ode0 related information (address and T2&:s) for the 32- and sends "uspend 'otification messa e to the P=GD(s). ,*. "=GD and P=GD(s) ac#nowled es the bearer updates by respondin with "uspend .c#nowled e. The MM2 stores in the 32 conte(t that 32 is in suspended status. .ll the preserved non=G0/ bearers are mar#ed as suspended status in "=GD and P=GD. The P=GD discards downlin# data if the 32 is mar#ed as suspended. ,3. ", 32 1onte(t in the 2=3T/.' is released as specified in T" *3.<+, H*I. ,<. 32 tunes to ,(/TT and ac#nowled es the pa e by transmittin a ,(/TT Pa in /esponse messa e over the ,( .ccess 1hannel. ,>. "ubseGuently 32 performs the procedure for mobile terminated call establishment as specified in 3GPP* .."++,3 H,@I. Once 1" service ends in the ,(1" domain the 32 returns to 2=3T/.' by performin reselection. The 2P" service is resumed as described in clause 8.>.

8.2.3& E(%&(ced ,S 4&##)&cB to 10!TT Procedure

8.2.3&.1 Ge(er&#
2nhanced 1" fallbac# to ,(/TT procedure may be used when the 32 indicates its support of this capability to the networ#. &f in addition- the 32 also indicates its support of concurrent ,(/TT and ?/P: P" session handlin - this indication also allows the networ# to invo#e optimised or non=optimised P" handover procedure concurrently with the enhanced 1" fallbac# to ,(/TT procedure. . networ# that advertises support for enhanced 1" fallbac# to ,(/TT may also advertise support for 32s with dual ,(/TT and 2=3T/.' receiverAtransmitter confi uration. &n such networ#s- 32s that support enhanced 1" fallbac# to ,(/TT for dual receiverAtransmitter confi uration may switch off their ,(/TT receiverAtransmitter while camped in 2= 3T/.' and re ister in the ,(/TT domain via the ",+* tunnel. . networ# advertisin these capabilities does not suspend the 2P" bearers for mobile ori inated or mobile terminated ,( 1" calls for such 32s. 1oncurrent enhanced 1" fallbac# to ,(/TT and P" handover to ?/P: is not performed for 32s that support enhanced 1" fallbac# to ,(/TT for dual receiverAtransmitter confi uration.

3GPP

%elease &&

(&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

&f enhanced 1" fallbac# to ,(/TT procedure is not used by the networ# (i.e.- not supported or not confi ured)- the networ# uses //1 connection release with redirection as specified in clauses 0.*.* and 0.*.3. 'OT2 ,. Other 3GPP* specific procedure (e. . how 32 performs concurrent operation in 3GPP* networ#) is outside the scope of this specification. 'OT2 *. 2=3T/.' may invo#e concurrent optimised active=mode P" handover procedure or non=optimised P" handover procedure when it receives ",=.PE 32 1onte(t Modification with 1"70 indication- based on 32 capability and operator confi uration.

8.2.3&.2

Mo)i#e 7ri3i(&ti(3 ,&## 2it%out co(curre(t PS %&(do6er, or 2it% co(curre(t (o(-o$timi"ed PS %&(do6er or o$timi"ed id#e-mode PS %&(do6er

The followin fi ure describes the mobile ori inatin call procedures for the enhanced 1" 7allbac# to ,(/TT with concurrent non=optimised P" handover or optimised idle=mode P" handover- or without concurrent P" handover- in the normal case. 1lause 0.*.3b describes the procedure when the procedure is rejected by the MM2.
1 0,S ,S*8 UE

EUT!'+

MME

1 0,S 9>S

1 0!TT MS,

S- G> 1 P -G>

1 . UE i" E- UT!'+ &tt&c%ed &(d re3i"tered 2it% 10!TT ,S UE i(dic&te" t%&t it "u$$ort" e(%&(ced 10,S*8 $rocedure
2. UE deci"io( to $er4orm M7 c&## i( 1 0,S

3. E0te(ded Ser6ice !e=ue"t /. UE ,o(te0t Modi4ic&tio( !e=ue"t 1 9(iti&# UE ,o(te0t !e=ue"t /. UE ,o(te0t Modi4ic&tio( !e"$o("e 1 9(iti&# UE ,o(te0t !e"$o("e . 7$tio(&# me&"ureme(t re$ort "o#icit&tio(
6 . ;74romEUT!'Pre$ . !e=ue"t ( 3 G1 0 $&r&meter , !'+5 , co( - ;!P5 ;7 i(dic&tio( ) 7. UL ;7 $re$H4er (ME95 , 1 0 Me""&3e ) < UL S 1 cdm& 2000 tu((e#i(3 (N ) 5L S 1 cdm& 2000 tu((e#i(3 (N ) 9& . Mo)iiit:*romEUT!' (e 10,S*8 i(d ,1 0!TT $&r&meter" , %r$d redirectio( i(4o ) 9). 5L 9(4o Tr&("4er (10 Me""&3e) 10 &. S 1 UE co(te0t !e#e&"e !e=ue"t

S 102 5irect Tr&("4er , &(d 10MS, i(ter2orBi(3

10) Su"$e(d +oti4ic&tio( 1 'cB(o2#ed3e

10c. S1 UE ,o(te0t !e#e&"e 11. UE tu(e" to 10!TT &(d re"ume" 2it% 3GPP2 "$eci4ic $rocedure.

;!P5
12 . ;!P5 PS ;7 &" $er TS 23./02 .

1i#ure >'$'3a'$+&2 "nhanced CS fall ac! to &@%TT 3= Call with no PS handover< or with concurrent non+optimised PS handover or optimised idle+mode PS handover

3GPP

%elease &&

($

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

,. 32 is 2 3T/.' attached and re istered with ,(/TT 1" as defined in clause 0.*.,., with enhanced 1" fallbac# to ,(/TT capability indication to 2=3T/.'. The 32 may also indicate that it supports concurrent ,(/TT and ?/P: capability. The 32 may also be pre=re istered with ?/P: access usin procedures defined in T" *3.<+* H*9I- clause ;.3.,. The 32 may also indicate support of enhanced 1" 7allbac# to ,(/TT for dual receiverAtransmitter confi uration to 2=3T/.'. *. 32 ma#es a decision to perform a mobile ori inated 1" call. 3. 32 sends an 2(tended "ervice /eGuest for mobile ori inatin ,(1" fallbac# to the MM2. <. 7or a 32 in active mode- MM2 sends 32 1onte(t Modification /eGuest (1" 7allbac# &ndicator) to 2=3T/.'. 1" 7allbac# &ndicator indicates to the 2 3T/.' to move the 32 to ,(/TT. 2=3T/.' responds with 32 1onte(t Modification /esponse. 7or a 32 in idle mode- MM2 sends &nitial 32 1onte(t /eGuest (1" 7allbac# &ndicator) to 2=3T/.'. 1" 7allbac# &ndicator indicates to the 2=3T/.' to move the 32 to ,(/TT. 2=3T/.' responds with &nitial 32 1onte(t /esponse. &f MM2 determines the 1" 7allbac# procedure needs priority handlin based on MP" 1" priority in the 32$s 2P" subscription andAor the hi h priority access indication that the e'ode0 includes in the ",.P messa e in step 3- it sets priority indication as well as 1" 7allbac# indicator in the ",.P messa e to the e'ode0. .ccordin to operator policy the MM2 may use 1" priority indicator to verify the priority handlin of the 1" 7allbac# procedure- in the case hi h priority access indication is received in the ",=.P messa e. The 2=3T/.'- in con estion conditions- provides preferential treatment for this call in the subseGuent steps. .lso- the 2=3T/.' shall not tri er enhanced ,(1"70 with concurrent optimi!ed P" handover to ?/P: access. >. 2=3T/.' may optionally solicit a ,(/TT measurement report from the 32 to determine the tar et ,(/TT cell to which the 1" 7allbac# will be performed. &f the networ# supports P" handover procedure to ?/P: then 2=3T/.' may optionally solicit an ?/P: measurement report from the 32 to determine whether the tar et ?/P: candidates e(ist or not. 8. 2=3T/.' sends a ?andover7rom2=3T/.Preparation /eGuest messa e to the 32 to start the enhanced ,(1" fallbac# procedure. &t includes 3G,( Overhead Parameters and /.': value. This messa e also includes an indication that concurrent ?/P: handover preparation is not reGuired. Dhen both the networ# and the 32 support enhanced 1" 7allbac# to ,(/TT for dual receiverAtransmitter confi uration- the 2=3T/.' may after "tep < decide- e. . due to /7 conditions- to direct the 32 to turn on its second radio to ,(/TT and retry the ,(1" call directly on the ,(/TT access networ#. 7or this case- the 2= 3T/.' in the ?andover7rom2=3T/.Preparation /eGuest messa e includes a redirection indicator alon with optional redirection information. The procedure stops after this step and the 32 tunes its ,( radio and retries its ,( call in ,(/TT while still receivin Atransmittin data on 2=3T/.'. 9. The 32 initiates si nallin for establishment of the 1" access le by sendin 35 ?andoverPreparation Transfer messa e which contains the ,(/TT Ori ination messa e with called party number. @. Messa es between MM2 and ,(&D" are tunnelled usin the ",+* interface. The ,(/TT M"1 initiates the call with the called party number carried in the ,(/TT Ori ination messa e. ;. The 2=3T/.' performs either "tep ;a or "tep ;b. "tep ;b is only performed when both the 2=3T/.' and 32 support enhanced ,( 1" fallbac# to ,(/TT for dual receiverAtransmitter confi uration. ;a. The 2 3T/.' sends Mobility from 23T/. 1ommand to the 32 with indication that this is for enhanced ,( 1" 7allbac# operation- ,(/TT related information- and optionally the ?/P: redirection information. The ,(/TT information contains ,(/TT messa es related to ,( channel assi nment and cause the 32 to tune to and acGuire this ,( channel. This is perceived by the 32 as a ?andover 1ommand messa e to ,(/TT. &f ,(/TT 1" networ# cannot support this 1"70 reGuest (for e(ample due to resource availability)- the :5 information transfer messa e is sent instead- with an embedded ,( messa e that indicates failure to the 32. = &f the networ# does not support P" handover procedure to ?/P: or if no tar et ?/P: candidates e(ist then 2=3T/.' shall release the ", 32 conte(t (see step ,+aAb) after e(ecutin the enhanced 1" fallbac# to ,(/TT procedure.

3GPP

%elease &&

(3

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

7or either concurrent non=optimised P" handover procedure or optimised idle=mode P" handover procedure alon with enhanced 1" fallbac# to ,(/TT- 2=3T/.' may also redirect the 32 to ?/P: as part of this procedure. This is indicated by the ?/P: redirection information in the Mobility from 23T/. 1ommand.

;b. The 2=3T/.' sends :5 information transfer messa e- with the embedded ,( messa e indicatin ,(/TT preparation success to the 32. "teps ,+ and ,* are not performed in this case. ,+aAbAc. &f P" handover procedure is not performed then 2=3T/.' sends an ", 32 1onte(t /elease /eGuest (1ause) messa e to the MM2. 1ause indicates that the ", 32 1onte(t /elease was caused by 1" fallbac# to ,(/TT. The ",=3 bearers are released and the MM2 starts the preservation and suspension of non=G0/ bearers and the deactivation of G0/ bearers towards "=GD and P=GD(s). The MM2 sets the 32 conte(t to suspended status. ,,. 32 tunes to the ,(/TT radio access networ# and performs ,(channel acGuisition with the ,(/TT 1" access (e. . ,(/TT 0""). . 32 supportin enhanced ,(1"70 to ,(/TT for dual receiverAtransmitter confi uration continues to receiveAtransmit data on 2=3T/.'. ,*.32 and 'etwor# follow the appropriate procedure for handlin non=optimised P" handover procedure or optimised idle=mode P" handover as defined in T" *3.<+* H*9I if performed. ", 32 1onte(t release procedure is as specified in T" *3.<+* H*9I for non=optimised P" handover (clause @.*.*) or optimised idle=mode P" handover (clause ;.<). This step occurs in parallel with step ,,.

8.2.3&.3

Mo)i#e 7ri3i(&ti(3 ,&## 2it% co(curre(t o$timi"ed PS %&(do6er

The followin fi ure describes the mobile ori inatin call procedures for the enhanced 1" 7allbac# procedure to ,(/TT with concurrent optimised P" handover- in the normal case. 1lause 0.*.3b describes the procedure when the procedure is rejected by the MM2. This procedure is not e(ecuted for mobile ori inated priority ,( 1" 7allbac#. This procedure is not performed when both the networ# and the 32 support enhanced 1" 7allbac# to ,(/TT for dual receiverAtransmitter confi uration.

3GPP

%elease &&

(-

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

1i#ure >'$'3a'3+&2 "nhanced CS fall ac! to &@%TT 3= Call with concurrent optimised PS handover ,=>. "ame as steps ,=> in fi ure 0.*.3a.*=,. The 32 indicates that it supports enhanced 1" fallbac# to ,(/TT procedure and concurrent ,(/TT and ?/P: capability. 8. 2=3T/.' sends an ?andover 7rom 2=3T/. Preparation /eGuest messa e to the 32 to start the enhanced ,(1" fallbac# procedure. &t includes 3G,( Overhead Parameters and /.': value. This messa e also includes an indication that concurrent ?/P: handover preparation is reGuired. 9. 32 starts the enhanced ,(1" fallbac# and optimised P" handover messa es (9a- 9b) in a seGuential manner. "tep 9a contains the ,(/TT Ori ination messa e with called party number. @a- ;a- ,+a- and @b- ;b- ,+b. MM2 treats the enhanced ,(1" fallbac# and ?/P: P" handover procedure independently (i.e. MM2 does not lin# the ?/P: messa e and ,(1" fallbac# messa e to ether). @a- ;a- ,+a is same as shown in step @ in fi ure 0.*.3a.*=, @b- ;b- ,+b are messa esAprocedure for optimised 2=3T/.' to ?/P: handover procedure as defined in T" *3.<+* H*9I- clause ;.3.*.

3GPP

%elease &&

(.

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

,,. The 2=3T/.' sends Mobility from 23T/. 1ommand to the 32 with indication that this is for enhanced ,( 1" 7allbac# operation includin the ,(/TT messa e and the ?/P: messa e received over the ",+* and ",+, tunnels. &f handover preparation to ?/P: is successful but preparation failure messa e in received from the ,(/TT 1" networ# via the ",+* tunnel- the messa e for ,(/TT preparation failure indication is sent to the 32 as part of the Mobility from 23T/. 1ommand. &f handover to ?/P: is successful and the e'ode0 times out waitin for preparation completion messa e from ,(/TT- the 2=3T/.' sends a Mobility from 23T/. command with only the ?P/: messa e included. &n the case that the preparation to ?/P: failed but ,(/TT is successful2=3T/.' may optionally include ?/P: redirection info as part of the Mobility from 23T/. 1ommand. &n case preparation on ,(/TT and ?/P: failed with e(plicit failure messa es received on ",+* and "+, tunnels- the 2=3T/.' forwards the received failure messa es as :5 &nformation transfers ,*. 32 retunes to the ,(/TT radio access networ# and performs ,( channel acGuisition with the ,(/TT 1" access (e. . ,(/TT 0"")- see T" *3.*,8 H*+I- clause 8.,.3. ,3. 32 and networ# follow the optimised 2=3T/.' to ?/P: handover procedure. 32 conte(t release procedure follows the optimised 2=3T/.' to ?/P: handover procedure as defined in T" *3.<+* H*9I- clause ;.3.*. This step occurs in parallel with step ,*.

8.2.3&./

Mo)i#e Termi(&ti(3 ,&## 2it%out PS %&(do6er, or 2it% co(curre(t (o(o$timi"ed PS %&(do6er or o$timi"ed id#e-mode PS %&(do6er

The followin fi ure describes the mobile terminatin call procedures for the enhanced 1" 7allbac# to ,(/TT with concurrent non=optimised P" handover or optimised idle=mode P" handover- or without P" handover- in the normal case. 1lause 0.*.3b describes the procedure when the procedure is rejected by the MM2.

3GPP

%elease &&

(/

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

1 0,S ,S*8 UE

EUT!'+

MME

1 0,S 9>S

1 0!TT MS,

S -G> 1 P -G>

1. UE i" E -UT!'+ &tt&c%ed &(d re3i"tered 2it% 1 0!TT ,S UE i(dic&te" t%&t it "u$$ort" e(%&(ced 1 0,S*8 $rocedure Ste$ 2-7 , "&me &" i( *i3ure *i3ure 8 . 2. 3 -1. <. 7$tio(&# me&"ureme(t re$ort "o#icit&tio(
9 . ;74romEUT!'Pre$ . !e=ue"t (3 G 1 0 $&r&meter , !'+5 , co( -;!P5 ;7 i(dic&tio( ) 10 . UL ;7 $re$H4er (ME95 , 1 0P&3e!e"$o("e ) 11 . UL S 1 cdm& 2000 tu((e#i(3

(N)

12 . S102 5irect Tr&("4er , &(d 10MS, i(ter2orBi(3

13 . 5L S 1 cdm& 2000 tu((e#i(3 ( N) 1/&. Mo)iiit:*romEUT!' ( e 1 0,S*8 i(d ,1 0!TT $&r&meter" , %r$d redirectio( i(4o ) 1 & . S 1 UE co(te0t !e#e&"e !e=ue"t

1/). 5L 9(4o Tr&("4er (10 M"3)

1 ) Su"$e(d +oti4ic&tio( 1 'cB(o2#ed3e 1 c. S1 UE ,o(te0t !e#e&"e 16 . UE tu(e" to 10!TT &(d re"ume" 2it% 3GPP 2 "$eci4ic $rocedure .

;!P5
1 7. ;!P5 PS ;7 &" $er TS 23 ./02.

1i#ure >'$'3a'-+&2 "nhanced CS fall ac! to &@%TT 3T call without PS handover< or with concurrent non+optimised PS handover or optimised idle+mode PS handover ,. 32 is 2=3T/.' attached and pre=re istered with ,(/TT 1" as defined in clause 0.*.,., with enhanced 1" fallbac# to ,(/TT capability indication to 2=3T/.'. The 32 may also indicate that it supports concurrent ,(/TT and ?/P: capability The 32 may also be pre=re ister with ?/P: access usin procedures defined in T" *3.<+* H*9I- clause ;.3.,. The 32 may also indicate support of enhanced 1" fallbac# to ,(/TT for dual receiverAtransmitter confi uration to 2=3T/.'. *=9. "ame as step *=9 in fi ure 0.*.3=,.

&f priority indication in included in the ",.P 32 1onte(t "etup or modification messa e from the MM2 to the 2=3T/.'- the 2=3T/.' shall not initiate enhanced ,(1"70 with concurrent optimi!ed P" handover to ?/P: access. @=,9. "ame as steps > C ,* of 7i ure 0.*.3a.*=,- with the modifications that the ,( messa e in step 9 of 7i ure 0.*.3a.*=, provided by the 32 to the 2=3T/.' is a ,(Pa e /esponse messa e and ,( messa es in step ;a of 7i ure 0.*.3.a.*=, (step ,<a of 7i ure 0.*.3a.<=,) provided by the 2=3T/.' to 32 may also contain .lert Dith &nformation messa e to provide caller line &dentification and alertin tri er with ,( channel assi nment messa e.

8.2.3&.

Mo)i#e Termi(&ti(3 ,&## 2it% co(curre(t o$timi"ed PS %&(do6er

The followin fi ure describes the mobile terminatin call procedures for the enhanced 1" 7allbac# to ,(/TT with concurrent optimised P" handover- in the normal case. 1lause 0.*.3b describes the procedure when the procedure is rejected by the MM2. This procedure is not e(ecuted for mobile terminated priority ,( 1" 7allbac#. This procedure is not performed when both the networ# and the 32 support enhanced 1" 7allbac# to ,(/TT for dual receiverAtransmitter confi uration.

3GPP

%elease &&

((

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

1i#ure >'$'3a'.+&2 "nhanced CS fall ac! to &@%TT 3T Call with concurrent optimised PS handover ,=@. "ame as steps ,=@ in fi ure 0.*.3a.<=,. The 32 indicates that it supports enhanced 1" fallbac# to ,(/TT procedures and concurrent ,(/TT and ?/P: capability. The 32 may also be pre=re ister with ?/P: access usin procedures defined in T" *3.<+* H*9I- clause ;.3.,. ;=,8. "ame as steps 8 C ,3 of 7i ure 0.*.3a.3=,- with the modifications that the ,( messa e in step 9 of 7i ure 0.*.3a.*=, provided by the 32 to the 2=3T/.' is a ,(Pa e /esponse messa e and ,( messa es in step ;a of 7i ure 0.*.3.a.*=, (step ,< of 7i ure 0.*.3a.>=,) provided by the 2=3T/.' to 32 may also contain .lert Dith &nformation messa e to provide caller line &dentification and alertin tri er with ,( channel assi nment messa e.

8.2.3&.6

9(ter&ctio( )et2ee( e(%&(ced ,S *&##)&cB to 10!TT &(d o$timi"ed PS %&(do6er

7or re ular optimi!ed P" handover procedure- it is possible that the 32 receives ,(/TT 1" pa in from 2P" while optimised P" handover to ?/P: is in pro ress. &n this case- 32 shall i nore the ,(/TT 1" pa in locally.

8.2.3) Mo)i#e 7ri3i(&ted or Mo)i#e termi(&ted c&## re?ected ): t%e MME

The MM2 may reject an 2(tended "ervice /eGuest either for mobile ori inated or mobile terminated 1"70. &n this case- the followin procedure is e(ecuted.

3GPP

%elease &&

(0

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

10,S ,S*8 UE

EUT!'+

MME

1 0,S 9>S

1 0!TT MS,

S -G> 1 P -G>

1. UE i" E-UT!'+ &tt&c%ed &(d re3i"tered 2it% 1 0!TT ,S 2 . UE deci"io( to $er4orm M7 c&## i( 1 0,S or &cce$t & 10,S $&3e me""&3e 3. E0te(ded Ser6ice !e=ue"t

/. Ser6ice !e?ect

. UE Se#ect" 10!TT &cce"" 6. S1 UE ,o(te0t !e#e&"e ,omm&(d

7. E-UT!'+ tri33er" !!, co((ectio( re#e&"e <. S1 UE ,o(te0t !e#e&"e ,om$#ete

9. U$d&te 8e&rer( ") 10. . U$d&te 8e&rer(") !e"$o("e

1i#ure >'$'3 +&2 &@CS1> 3= or 3T call< rejected y 33" ,. 32 is 2=3T/.' attached and pre=re istered with ,(/TT 1" as defined in clause 0.*.,.,. *. 32 ma#es a decision to perform a mobile ori inated 1" call or accepts 1" pa in for the 1" 7allbac# to ,(/TT ("tep 8a- 1lause >.*.3). 3. 32 sends an 2(tended "ervice /eGuest for mobile ori inatin Amobile terminatin ,(1" fallbac# to the MM2. <. &f the MM2 decides to reject the 2(tended "ervice /eGuest- the MM2 sends a "ervice /eject messa e to the 32. "teps > C ,+ are e(ecuted when "ervice /eject is sent with a reason code which results in the 32 selectin ,(/TT access- as specified in T" *<.3+, H3<I. >. The 32 selects ,(/TT access without waitin for //1 /elease. 8. The MM2 releases ", by sendin the ", 32 1onte(t /elease 1ommand (1ause) messa e to the e'ode0. 1ause value indicates that the release is tri ered by 1" 7allbac# procedure. 9. &f the //1 connection is not already released- the 2=3T/.' sends a //1 1onnection /elease messa e to the 32. @. The 2=3T/.' confirms the ", /elease by returnin an ", 32 1onte(t /elease 1omplete messa e to the MM2. ;=,+. :ependin on the reason for rejection- MM2 may start "uspend 'otificationE = = "uspend 'otificationE The ",=3 bearers are released and the MM2 starts the preservation and suspension of non=G0/ bearers and the deactivation of G0/ bearers towards "=GD and P=GD(s). "=GD and P=GD(s) ac#nowled es the bearer updates "uspend 'otification and mar#s the 32 as suspended. The P=GD discards downlin# data if the 32 is mar#ed as suspended.

3GPP

%elease &&

(,

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

8.2./ S%ort Me""&3e Ser6ice (SMS)

8.2./.1 Ge(er&#
The procedures for "M" in this anne( apply only if the 32 is ,(/TT 1" /e istered and the 1" access domain is chosen by the 32 andAor the home P5M' for deliverin short messa es. This clause describes both the mobile ori inatin and mobile terminatin "M" over ",+* which uses ,(1" procedures in 2P". "M" support is based on the ",+* reference point between the MM2 and the ,(1" &D"- use of //1 &nformation Transfer messa e between the 32 and the 2=3T/.'- and use of ", cdma*+++ Tunnellin messa e between the 2=3T/.' and the MM2.

8.2./.2 Mo)i#e ori3i(&ti(3 SMS

The followin seGuence flow shows the delivery of mobile ori inatin "M" sent via the ,(M"1 while in 2=3T/.'.

1i#ure >'$'-'$+&2 3o ile ori#inatin# S3S sent via the &@3SC while in "+6T%A: ,. The ,(/TT 1" /e istration procedure as described in clause 0.*.,., has been performed earlier. *. . mobile ori inatin short messa e is tri ered. &f the 32 is in idle state- the 32 performs the 32 tri ered "ervice /eGuest procedure- which is defined in T" *3.<+, H*I.

3GPP

%elease &&

0*

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

3. The 32 builds the "M" messa e to be sent as defined in 3GPP* .."+++@ H,8I and 3GPP* .."+++; H,9I. 3a. The ,(/TT "M" messa e is transferred from the 32 to the 2=3T/.'. 3b. The 2=3T/.' forwards the "M" messa e to the MM2. <. The MM2 forwards the "M" messa e to the ,(1" &D" in an ",+* :irect Transfer messa e. >. The ,(1" &D" ac#nowled es the messa e. 8. The ,(1" &D" sends an .::" Transfer messa e to the ,(M"1 containin the "M" messa e as defined in 3GPP* .."+++@ H,8I and 3GPP* .."+++; H,9I. 9. The ,(M"1 forwards the "M" messa e to the Messa e 1entre (M1). &f an ac#nowled ement was reGuested by the 32- the M1 responds with an ac#nowled ement. @. The ,(M"1 forwards the "M" ac#nowled ement to the ,(1" &D" in an .::" Pa e messa e. ;. The ,(1" &D" forwards the "M" ac#nowled ement to the MM2 in an ",+* :irect Transfer messa e. ,+. The MM2 forwards the "M" ac#nowled ement to the 32. ,,. The MM2 sends an ",+* .c# messa e to the ,(1" &D". This occurs immediately after step ; if the M"1 has not reGuested an ac#nowled ement from the ,(1" &D". ,*. &f the M"1 reGuested an ac#nowled ement- the ,(1" &D" sends an .::" Pa e .c# messa e to the ,(M"1.

8.2./.3 Mo)i#e termi(&ti(3 SMS

The followin seGuence flow shows the delivery of mobile terminatin "M" sent via the ,(M"1 while in 2=3T/.'.

1i#ure >'$'-'3+&2 3o ile terminatin# S3S sent via the &@3SC while in "+6T%A:

3GPP

%elease &&

0&

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

,. The 32 is 2=3T/.' attached and re istered with ,(/TT 1" as defined in clause 0.*.,.,. *. The ,(M"1 receives the "M" messa e from the M1 and sends an .::" Pa e messa e to the ,(1" as defined in 3GPP* .."+++@ H,8I and 3GPP* .."+++; H,9I. The .::" Pa e contains the "M" messa e. 3. The ,(1" &D" sends the "M" messa e in an ",+* :irect Transfer messa e. <. &f the 32 is in idle state- the MM2 performs the networ# initiated "ervice /eGuest procedure to brin the 32 to active state prior to tunnellin of the "M" messa e toward the 32. >. The MM2 forwards the "M" messa e to the 32. 8. The MM2 sends an ",+* .c# messa e to the ,(1" &D". This occurs immediately after step 3 if the M"1 has not reGuested an ac#nowled ement from the ,(1" &D". 9. &f the M"1 reGuested an ac#nowled ement- the ,(1" &D" sends an .::" Pa e .c# messa e to the ,(M"1. @. .fter receivin the "M" messa e at step >- the 32 sends an "M" ac#nowled ement toward the M1. ;. The MM2 forwards the "M" ac#nowled ement in an ",+* :irect Transfer messa e to the ,(1" &D". ,+. The ,(1" &D" sends an ",+* .c# messa e to the MM2. ,,. The ,(1" &D" forwards the "M" ac#nowled ement to the ,(M"1. The ,(M"1 then forwards the "M" ac#nowled ement to the M1. 'OT2E &n addition to above MT "M" procedure (1ommon 1hannel "M")- 3GPP* also defines Traffic 1hannel "M" deliverin method in 3GPP* .."+++@H,8I and .."+++; H,9I that can be used in 2=3T/.'=,( interwor#in architecture. &n this method- the messa es between ,(/TT &D" and ,(M"1 are different from those messa es specified in this section. There is no additional functional reGuirement to 2P".

8.2. Emer3e(c: ,&##"

Dhen 32 is performin 1" fallbac# procedure to ,(/TT for the purpose of emer ency call- it shall indicate to the MM2 that this 1" fallbac# reGuest is for emer ency purpose. MM2 also indicates to the 2=3T/.' via the appropriate ",=.P messa e that this 1" fallbac# procedure is for emer ency purpose. 2mer ency call with enhanced ,(/TT 1" fallbac# procedure shall be e(ecuted without the concurrent P" handover procedure.

8.3

,S *&##)&cB 4or UE" 2it% du&# !0 co(4i3ur&tio(

8.3.1 Ge(er&# ,o("ider&tio("

The followin principles are used for supportin 1" 7allbac# for dual receiver 32sE = The 32 with dual /( confi uration attaches separately to each /.T (2=3T/.'- ,(/TT) and maintains separate re istration and mobility procedure handlin to each /.T. 'o coordination is reGuired between the 2=3T/.' and ,(/TT networ#. The 32 with dual /( confi uration is able to camp in ,(/TT at the same time as it is active or idle in 2=3T/.'. 1ampin in ,(/TT includes performin ,(/TT cell re=selection- readin broadcast channelsmonitorin pa in - performin location updates- etc. accordin to 3GPP* specifications. The 32 with dual /( confi uration is allowed to leave 2=3T/.' in order to handle a 1" call andAor perform re istration si nallin - andAor sendin or receivin "M" in ,(/TT. The procedures for leavin 2=3T/.' is described in clause 0.3.* and are only allowed if the networ# indicates that it supports them (this is indicated by either the presence of 1"70 re istration parameters or indication of support for dual /( 1"70 on 2=3T/.' broadcast channel- T" 38.33, H33I). The 32 that reports dual /( confi uration to 2=3T/.' does not reGuire redirection information.

3GPP

%elease &&

0$

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

'OT2E

7urther clarification to the 32 behaviour may be needed if the procedure in clause 0.3.*- i.e. time between transmission of 2(tended "ervice /eGuest (3) and reception of //1 1onnection /elease (>) ta#es too lon .

8.3.2 Procedure" 4or #e&6i(3 E-UT!'+

The 32 with dual /( confi uration is allowed to leave 2=3T/.' in order to handle a 1" call andAor perform re istration si nallin - andAor perform location mana ement si nallin - andAor sendin or receivin "M" in ,(/TT. Dhen the 32 needs to leave 2=3T/.' it indicates this to 2=3T/.' by usin the 2(tended "ervice /eGuest procedure similar to how MTAMO calls are handed in clauses 0.*.*- 0.*.*a and 0.*.3. The procedure is the same re ardless what activity is performed in the ,(/TT system (e. . if it is a pa e response- MO call- re=re istration). The procedure is shown in 7i ure 0.3.*=,.
1 0,S ,S*8 UE

EUT!'+

MME

1 0!TT MS,

S -G> 1 P - G>

1 . UE i" E -UT!'+ &tt&c%ed 2 . UE deci"io( to $er4orm 1 0!TT &cti6it:

3. E0te(ded Ser6ice !e=ue"t /. UE ,o(te0t Modi4ic&tio( !e=ue"t /. UE ,o(te0t Modi4ic&tio( !e"$o("e

. E-UT!'+ tri33er" !!, co((ectio( re#e&" e 6. S1 UE ,o(te0t !e#e&"e !e=ue"t

7. Su"$e(d +oti4ic&tio( <. Su"$e(d 'cB(o2#ed3e

9. S1 UE ,o(te0t !e#e&"e

10. 10!TT &cti6it: &ccordi(3 to 3GPP2 "$eci4ic&tio("

1i#ure >'3'$+&2 Performin# &@%TT related activity for dual receiver 6"s ,. 32 is 2=3T/.' attached the 32 may also be re istered in ,(/TT 1". *. 32 ma#es a decision that it needs to perform some ,(/TT activity (e. . in order to respond to an incomin ,(/TT pa e- setup a MO call- perform location mana ement si nallin - or perform re=re istration). 3. 32 sends an 2(tended "ervice /eGuest for mobile ori inatin Amobile terminatin ,(1" fallbac# to the MM2. The fi ure shows the case the 32 is in active state in 2=3T/.' but the same principles applies if the 32 is in idle state- T" *3.<+, H*I. <. MM2 sends 32 1onte(t modification /eGuest (1" 7allbac# &ndicator) to 2=3T/.'. 1" 7allbac# &ndicator indicates to the 2=3T/.' to move the 32 to ,(/TT. 2=3T/.' responds with 32 1onte(t Modification /esponse.

3GPP

%elease &&

03

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

>. The 2=3T/.' tri ers //1 connection release and continues with step 8. This step may include re=direction information if the 2=3T/.' indicates support for ",+*. 2=3T/.' that indicates support for dual /( 1"70 shall not include any redirection information towards the 32 that indicates dual /( confi uration but no support for enhanced 1" fallbac# to ,(/TT. 8. 2=3T/.' sends an ", 32 1onte(t /elease /eGuest (1ause) messa e to the MM2. 1ause indicates that the ", 32 1onte(t /elease was caused by 1" fallbac# to ,(/TT. 9. The ",=3 bearers are released and the MM2 starts the preservation and suspension of non=G0/ bearers and the deactivation of G0/ bearers towards "=GD and P=GD(s). by sendin "uspend 'otification to "=GD and P=GD The MM2 sets the 32 conte(t to suspended status. @. The "=GD and P=GD(s) ac#nowled es the bearer updates by respondin with "uspend .c#nowled e and mar#s the 32 as suspended in "=GD and P=GD. Dhen a downlin# data arrives at the P=GD- the P=GD should not send downlin# data if the 32 is mar#ed as suspended. ;. ", 32 1onte(t in the 2=3T/.' is released as specified in T" *3.<+, H*I.

8.3.3 Procedure" 4or retur(i(3 to E-UT!'+

The procedure for returnin to 2=3T/.' is the same as specified in clause 8.>.

'((e0 , (+orm&ti6e)SMS i( MME ,.1 Ge(er&#

"M" in MM2 is an architecture option primarily intended for networ#s that do not deploy G2/.' or 3T/.'. "M" in MM2 delivers "M" services over 2P" '." si nallin for 32$s reGuirin "M" services. "M" in MM2 architecture option enables support of "M" in the 2P" via 2=3T/.' without reGuirin deployment of 3GPP M"1s. 7or "M" in MM2 the "M" service control is performed by the MM2. The MM2 receives "M" subscriber data and the MM2 verifies whether the subscriber is permitted to obtain "M" services. The "M" subscriber data received and used by the MM2 may be P" subscriber data (the MM2 directly obtains from ?"") or 1" subscriber data (the MM2 obtains via an interwor#in function as described in clause 1.>). 'OT2E The use of "M" in MM2 by an operator that also deploys 1" service on G2/.' or 3T/.' may lead to increased si nallin traffic to the ?"".

,.2

'rc%itecture

.s outlined in the architecture fi ure below "M" in MM2 reGuires support of "M" functionality in the MM2 and the MM2 also needs to receive "M" subscription information from the ?"". The "M" subscription information may be received throu h the "8a interface.

3GPP

%elease &&

0-

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

;SS
S6& S6c1,

Uu

UE

E-UT!'+

S1-MME

SGd

MME

SMS-GMS,1 9>MS,1 SMS !outer

1i#ure C'$+&2 S3S in 33" Architecture

;SS
S6c1, S6&

9>*
SGd

, E

Uu

S1-MME

UE

E-UT!'+

MME

9>*

SMS-GMS,1 9>MS,1 SMS !outer

1i#ure C'$+$2 S3S in 33" architecture usin# 5?1 There is no impact on the 32 and 2=3T/.'. The "M" entities (includin "M" router etc) functionality to support "M" in MM2 is the same as defined for reference point * and 3 in T" *3.+<+ H,<I e(cept the "Gd and "8c interfaces use :iameter protocols. 'OT2 ,E The ?"" may support both a :iameter "8c and a M.P 1 interface to "M" entities that have not evolved to "8c- or the "M" entities may support both interfaces to obtain routin information from ?""$s that have not evolved to "8c. 'OT2 *E .ccordin to T" *3.+<+ H,<I- the "M"=/outer is optional and only reGuired for MT "M".

,.3

!e4ere(ce Poi(t"

,.3.1 Ge(er&#
The followin reference points specifically enable support of "M" in MM2.

,.3.2 S6&
&n order to support J"M" in MM2J the "8a shall allow the MM2 to reGuest "M" subscription information and to re ister as a servin node for "M". &f the ?"" supports this and has "M" subscription information available- it sends "M" subscription data to the MM2. The "M" subscription data include for e(ample the barrin status of MO="M" and MT="M" and the M"&":'.

,.3.3 S6c
&n order to support J"M" in MM2J the :iameter based "8c shall allow the "M" central functions to reGuest routin information from the ?"".

3GPP

%elease &&

0.

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

,.3./ SGd
&n order to support J"M" in MM2J the :iameter based "Gd shall provide the "hort Messa e /elay 5ayer ("M=/5) between MM2 servin the 32 and "M" central functions.

,./

+et2orB E(titie"

,./.1 Ge(er&#
The followin networ# entities specifically enable support of "M" in MM2

,./.2 MME
The MM2 needs to support the followin featuresE = = = = = = "M"o"Gs 32=MM2 '." procedures. "8a functionality as described above. "M" procedures between 32 and MM2 includin support for the "hort Messa e 1ontrol ("M1) and "hort Messa e /elay ("M=/5) functions defined in T" *<.+,, H*@I. /eportin 32$s availability for receivin MT "M" to the ?"". "M" functions includin char in and 5&. "upport combined 2P"A&M"& procedures for J"M"=onlyJ and in theseE = = = = = provide a non=broadcasted 5.& (not associated with any B5/)F and if needed provide a reserved TM"& that cannot cause any ambi uities with other TM"&s (e. . when the 32 chan es to an area where it needs to derive "M" services from a G2/.'A3T/.' M"1)F and indicate in the .ttachAT.3 .ccept messa e that the &M"& attach is for J"M"=onlyJF and notify the ?"" it is capable of "M" transfer without the need of establishin an "Gs association with an M"1F and obtain "M"=related subscription information.

The MM2 shall provide "M" in MM2 for a 32 if the subscriber data allow for "M" services and the subscriber data indicate J"M" in MM2 "upportJ and one or more of followin conditions are fulfilledE = = the subscriber data indicate by the 'etwor# .ccess Mode information that the subscription has no 1" subscriber dataF or the MM2 supports only J"M" in MM2J but no "Gs is supported or deployed.

Dhen the MM2 also supports "Gs- the MM2 may decide to provide "M" in MM2 for a 32 if the subscriber data allow for "M" services and the ?"" indicates J"M" in MM2 "upportJ and the 32 indicates "M" only. 'OT2 ,E Dhen the MM2 also supports "Gs- dependin on 32 capability (e. . no G2/.'A3T/.' support) andAor or networ# confi uration (e. . whether "M" is preferentially provided via 1" or P" G2/.'A3T/.') andAor subscription is JP" and "M" onlyJ- the MM2 should provide "M" in MM2 for a 32 if the subscriber data allow "M" services and the ?"" indicates J"M" in MM2 "upportJ. 'OT2 *E J"M" in MM2J is not visible to the ?"" when an &D7 for "8a combines P" subscriber data and "M" subscriber data from 1" subscriber data into a sin le set of subscriber data. 7or the MM2 it is not visible whether combined subscriber data are comin from an &D7 for "8a or directly from an ?"".

3GPP

%elease &&

0/

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

Dhen the MM2 receives a cancellation only for the "M" subscriber data- the MM2 mar#s the stored "M" subscriber data as not updated with ?""- which invalidates the stored "M" subscriber data. &f the 32 performs combined attachAT.3 with J"M"=onlyJ indication- the MM2 forwards the J"M"=onlyJ indication in the 5ocation 3pdate procedure to the ?"".

,./.3 ;SS
Dhen an MM2 reGuest "M" subscription information via the "8a and indicates its support of J"M" in MM2J- an ?"" that supports "M" in MM2 re isters the MM2 as an M"1 for MT "M" (i.e. in response to "/& for "M the MM2 identity is passed bac# to the "M"1A"M" router). This re istration as an M"1 for MT "M" causes the ?"" to cancel any old re istered M"1. &f the ?"" receives an "end /outin &nformation for other 1" "ervices than "M" it shall treat the 32 as if it was detached from the 1" domain. &f the 32 subseGuently re isters with an M"1 for 1" services- the ?"" needs to replace the MM2 with the new M"1 as the destination for "M" (but this is not a reason to cancel the MM2s re istration for 2P" "ervices). 'OT2 ,E That an ?"" that supports "M" in MM2 re isters the MM2 as an M"1 for MT "M" does not affect how the information is stored in the ?""- however the ?"" reuses the M'/7 fla intended for the controllin "M delivery via the M"1- for controllin the "M delivery via MM2. &t only affects what servin node identities are returned in response to "/& for "M. &n such cases the MM2 identity is passed bac# to the "M"1A"M" router where usually the M"1 identity is sent. 'OT2 *E 7or the P" and "M" only service to wor# also for outbound roamers- the 3GPP 5T2=only operator may need to confi ure 1" subscription data for "M" services in its ?"" as a visited P5M' may deploy "M" over "Gs. &t may also use an &D7 for M.P and :iameter translation. The 3GPP *GA3GA5T2 operator may need to up rade its ?"" to ensure that its outbound roamers et "M" services as a BP5M' may deploy only "M" in MM2. .n ?"" should allow an operator to confi ure a subscription- which is limited to only P" services and "M" services. This limitation is indicated in the P" subscription data as JP" and "M" onlyJ. 'OT2 3E The limitation of a subscription to only P" and "M" services can for e(ample be based on an operator a reement with an MT1 service provider- that only P" resources shall be used whenever possible. Dhen an ?"" supports J"M" in MM2J- i.e. provides all ?"" functionality described for J"M" in MM2J- and the operator confi ured the ?"" to apply that functionality- the ?"" indicates J"M" in MM2 "upportJ in the subscriber data provided to an MM2. Dhen an ?"" has an "8a re istration for J"M" in MM2J- i.e. the ?"" has re istered an MM2 as servin M"1 for MT "M"- and an M"1 re isters with the ?"" then the ?"" cancels the old MM2 partially- i.e. the ?"" cancels the subscriber data in MM2 that allow for J"M" in MM2J. .nd- the ?"" re isters the M"1 as servin M"1 for MT "M". 'OT2 <E This separate handlin of "M" subscriber data in the MM2 is also for ali nin with the deployment option of an &D7 for "8a that combines P" subscriber data with "M" subscriber data from 1" subscriber data- where the data part that stems from 1" subscriber data may be cancelled in MM2 independently from P" subscriber data. Dhen the P" subscriber data are cancelled then any 32 related subscriber data are cancelled in the MM2.

,.

!o&mi(3 co("ider&tio("

The "M" in MM2 architecture is an optional architecture enhancement for operators that wish to avoid to the use of M"1 and "Gs and do not provide 7allbac# to 3GPP 1" services over G2/.' or 3T/.'. To support inbound roamers from networ#s that do not support the provision of "M" subscription information over "8a there are different options to provide interwor#in - e. .E = = "M" over "Gs. 3se of an interwor#in function to convert between the "8a with "M" subscription data and "8a without "M" subscription data and : for "M" subscription. Dhen the MM2 sends /eady for "M messa e to ?"" for 32

3GPP

%elease &&

0(

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

reachability notification- the interwor#in function also needs to convert the /eady for "M messa e transferred via the "8a interface to /eady for "M messa e transferred via the : interface. Operators that do not deploy the "M" in MM2 architecture option are not reGuired to support the "8a enhancements in the ?"" or the MM2.

,.6

U("ucce""4u# Mo)i#e-Termi(&ted SMS Tr&("4er

The MM2 or the ?"" may not be able to deliver the "M to the 32. This can for e(ample happen when the 32 is not attached to 2P"- when the 32$s "M" memory capacity is e(ceeded- or when the Mobile=terminated "M" is barred. Dhen the MM2 cannot deliver the "M to the 32- the MM2 shall return a failure report to the "M" GM"1A"M" router. The "M"=GM"1A"M" routerA?"" procedures for handlin the failure report are specified in T" *3.+<+ H,<I. .dditionally- if the "M failed due to the 32 not bein reachable- the MM2 shall set the Mobile='ot=/eachable=7la =in= MM2=for="M" (M'/7=MM2) indication in the MM2. &f the 32 subseGuently becomes reachable and M'/7=MM2 indication is set- the MM2 shall send a /eady for "M (&M"&- 32=Present) messa e to the ?"" and the MM2 shall clear the correspondin M'/7=MM2 indication for that 32. 'OT2E &n the case that MM2 receives an indication from "=GD that the 32 has handover to non=3GPP covera e- it will not tri er this activity notification.

&f the 32 subseGuently notifies the MM2 that "M" memory is available- the MM2 shall send a /eady for "M (&M"&32=Memory=.vailable) messa e to the ?"". /eception of a /eady for "M messa e or an 3pdate 5ocation /eGuest messa e by the ?"" when M'/7 is set- shall tri er the "M" alert procedure as defined in T" *3.+<+ H,<I.

,.7

9(4orm&tio( "tor&3e

,.7.1 ;SS
The followin table specifies the ?"" data defined per 32 to support "M" in MM2. Ta le C'('&+&2 7SS data
1ield SMS P&r&meter" +et2orB 'cce"" Mode (+'M) 9escription SMS-re#&ted $&r&meter", e.3. SMS te#e"er6ice, SMS )&rri(3 #i"t. 9(dic&te" 2%et%er t%e "u)"cri$tio( i(c#ude" "u)"cri)er d&t& &##o2i(3 4or &cce""i(3 PS &(d or ,S dom&i(.

'OT2E

Dhen the 32 is not reachable in the MM2- the ?"" sets the M'/7 in the Messa e Daitin :ata (MD:) since the MM2 is re istered as an M"1.

Dhen the ?"" functionality for J"M" in the MM2J is activated- the ?"" will include an J"M" in MM2 "upportJ indication alon with the 32 subscription information to the MM2.

,.7.2 MME
The followin table specifies the MM2 data defined per 32 to support "M" in MM2.

3GPP

%elease &&

00

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

Ta le C'('$+&2 33" Conte@t for S3S

1ield SMS P&r&meter" SMS P&r&meter" U$d&ted SMS i( MME Su$$ort M+!*-MME +et2orB 'cce"" Mode (+'M) 9escription SMS-re#&ted $&r&meter", e.3. SMS te#e"er6ice, SMS )&rri(3 #i"t. 9(dic&te" 2%et%er &(: "tored SMS P&r&meter" &re u$d&ted ): t%e ;SS 9(dic&te" t%&t SMS i( MME i" &cti6&ted i( t%e ;SS 9(dic&te" 2%et%er &cti6it: 4rom t%e UE "%&## )e re$orted to t%e ;SS. 9(dic&te" 2%et%er t%e "u)"cri$tio( i(c#ude" "u)"cri)er d&t& &##o2i(3 4or &cce"" to PS &(d or ,S dom&i(.

3GPP

%elease &&

0,

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

3GPP

%elease &&

,*

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

'((e0 5 (i(4orm&ti6e),%&(3e %i"tor:

3GPP

%elease &&

,& Chan#e history

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

9ate 2010-06 2010-09 2010-09 2010-09 2010-09 2010-09 2010-09 2010-09 2010-09 2010-09 2010-09 2010-09 2010-09 2010-09 2010-12 2010-12 2010-12 2010-12 2010-12 2010-12 2010-12 2010-12 2010-12 2011-01 2011-03 2011-03 2011-03 2011-03 2011-03 2011-03 2011-03 2011-03 2011-03 2011-03 2011-03 2011-0/ 2011-06 2011-06 2011-06 2011-06 2011-06 2011-06 2011-06 2011-06 2011-09 2011-12 2011-12 2011-12 2011-12 2011-12 2012-03 2012-03 2012-03 2012-03 2012-03 2012-03

TSG A SP-/< SP-/9 SP-/9 SP-/9 SP-/9 SP-/9 SP-/9 SP-/9 SP-/9 SP-/9 SP-/9 SP-/9 SP-/9 SP-/9 SP- 0 SP- 0 SP- 0 SPSPSPSPSPSP0 0 0 0 0 0

TSG 9oc' SP-100/// SP-100 31 SP-100 31 SP-100 SP-100 SP-100 SP-100 SP-100 SP-100 SP-100 SP-100 /1 /1 /1 // // // // //

C% 021< 0 96 0609 0 0 0 0 0 0 0 0 7 77 < <0 <1 <2 <3 97

%ev / 1 1 1 3 2 2 2 1 1 2 2 7 2 2 6 1 2 1 2 1 2 3 1 1 1 3 2 3 -

Cat 8 ' ' ' ' ' 8 8 8 8 8 8 * , ' * * , ' ' * ' ' ' ' * ' ' * ' * ' ' 8 * * * * * * ' ' ' * * * ' ' ' ' ' * * *

SP-100 // SP-100 < SP-100 < SP-1006<1 SP-100691 SP-100691 SP-100691 SP-1006<1 SP-1006<1 SP-100709 SP-1006<1 SP-1006<1 SP-1100 9 SP-11006/ SP-110076 SP-11006/ SP-11006/ SP-110076 SP-11006/ SP-110076 SP-11006/ SP-11006/ SP-110076 SP-110330 SP-11033 SP-11033 SP-110327 SP-110330 SP-11033 SP-11032/ SP-11032/ SP-110/ 6 SP-11073< SP-11073< SP-11073< SP-110733 SP-110733 SP-12006< SP-120066 SP-120066 SP-12007 SP-12007 SP-1200<<

0 9< 0 <9 0 99 0 <7 0 91 061/ 061< 0620 0622 0629 0636 06/2 06/3 06/6 06/< 06 1 06 6 0660 0663 066 0671 0673 067/ 06 < 0666 06<1 06</ 06<6 06<9 0691 069/ 0702 0706 0709 0710 071/ 0717 072 0722 07 0 0703 0736 070

SP- 1 SP- 1 SP- 1 SP- 1 SP- 1 SP- 1 SPSPSPSPSPSP1 1 1 1 1 2

SP- 2 SPSPSPSPSPSPSPSPSPSPSPSPSPSPSPSPSPSP2 2 2 2 2 2 3 / / / / /

3 2 / 3 1 2 / 2 3 1 2 2 1 1 3 1 2

Su ject8Comment ,S*8 tri33ered ): L,S 2%i#e UE i" i( &cti6e Vo9P "e""io( !emo6i(3 UE re?ectio( o( ,L9 4or 10 MT c&## ,orrectio( to t%e $&3i(3 i""ue 4or ,S 4&##)&cB c&$&)#e UE" i( +M7 99 or 999 ,orrectio( to P&3i(3 i( MT ,S*8 ,S dom&i( &cce"" ri3%t" %&(d#i(3 i( ,S*8 Su"$e(d c#&ri4ic&tio( 4or ,S*8 eMPS ,! 4or ,S*8 (re4ere(ce, de4i(itio( &(d o6er&## de"cri$tio() eMPS ,! 4or ,S*8 (&tt&c% $rocedure) eMPS ,! 4or ,S*8 (Mo)i#e 7ri3i(&ti(3 ,&##) eMPS ,! 4or ,S*8 (Mo)i#e Termi(&ti(3 ,&##) MPS Su$$ort 4or 10,S*8 C 9(tro &(d im$&ct" to +et2orB E#eme(t" MPS 10,S*8 im$&ct" o( M7 &(d MT c&##" MS, re"e#ectio( i( c&"e o4 ro&mi(3 re"trictio( 'ddi(3 e10,S*8 "u$$ort 4or du&# !01T0 UE Mu#ti$#e PLM+" "e#ectio( i( e+ode8 ,#&ri4ic&tio( o4 ,S*8 i(dic&tio( i( E0te(ded Ser6ice !e=ue"t UE )e%&6iour 2it% 9S! &cti6e &4ter ,S*8 2it% "u"$e(ded PS )e&rer" ,orrectio( to ,S*8 M7 4#o2 ,#&ri4ic&tio( o( ,S*8 i( id#e mode ,#&ri4ic&tio( o( PLM+ "e#ectio( 4or ,S*8 MT, re#&ted ++S* i( MME 4or SMS o6er SG" ,orrectio( to ')(orm&# Ser6ice !e?ect Procedure ,S*8 2it% !e#e&"e 2it% !edirectio( to UMTS &(d Ode4erred S98 re&di(3O U$d&te o4 LTE #o3o to LTE-'d6&(ced #o3o ,orrectio( o( ,L9 i( $&3e me""&3e 4or 10 MT c&## S102 !edirectio( Timi(3 ,S PLM+ re"e#ectio( re=uireme(t 4or ,S*8 &(d !'T1L' c%ecBi(3 PS Su"$e(di(3 ,#&ri4ic&tio( SMS-,S*8 ce## 95 re$orti(3 correctio( ,orrectio( &)out t%e $&3i(3 &re& i( c&"e o4 (o &6&i#&)#e "tored T'9 #i"t i( MME 3GPP2 &#i3(me(t 4or 10,S*8 MT 3GPP2 &#i3(me(t 4or 10,S*8 SMS MT ,S*8 $rocedure" 4or ot%er t:$e" o4 ,S "er6ice" ,orrectio( to ,S*8 +',,1,,7 9(troductio( o4 MT !o&mi(3 *or2&rdi(3 4or ,S*8 M,, ,orrectio( to ;i"tor: t&)#e 6er"io( (um)er" ,orrectio( to ,S*8 $rocedure 4or UE" 2it% L9P' P5+ co((ectio(" o(#: U$d&ti(3 du&# r01t0 e10,S*8 to u"e e0$#icit UE "u$$ort i(dic&tor !!, re#e&"e 2it% ":"tem i(4orm&tio( c#&ri4ic&tio( Priorit: 4or termi(&ti(3 ,S*8 "e""io(" 4or eMPS 9(ter&ctio( )et2ee( L9P' &(d ,S*8 "er6ice ,orrect det&c% $rocedure 2it% 9S! &cti6&ted ,orrectio( o4 PS "u"$e("io( $rocedure i( ,S*8 to GE!'+ '1G) mode ,orrectio( o4 ,S*8 P&3i(3 to &6oid t%e u"e o4 TMS9 ,#&ri4ic&tio( &)out "u"$e(d &(d re"ume %&(d#i(3 ;&(d#i(3 o4 SG" $&3i(3 i( VL! &(d MME 4&i#ure c&"e" VL! SG" $&3i(3 retr: *&"t !etur( &4ter ,S*8 ,orrectio( o4 ,S*8 P&3i(3 $rocedure i( MME Se$&r&te L'U &(d !'U $rocedure" i( ,S 4&##)&cB $rocedure ,#&ri4ic&tio( o4 L'U1!'U tri33er 4or ,S*8 UE 2%e( 9S! i" &cti6&ted ,#&ri4ic&tio( o4 9S! &cti6&tio( co(ditio( 4or +M7 99 !'U &(d Periodic !'U ,orrectio( o4 ":"tem )e%&6iour u$o( MME im$#icit det&c% timer e0$ir: 2%e( SG" i" &""oci&ted &(d 9S! i" &cti6&ted ,M Ser6ice !e=ue"t duri(3 M7-L! $rocedure ,orrectio(" to SG" $&3i(3 4or ,S*8 ,#&ri4ic&tio( &)out 9S! m&i(te(&(ce 4or ,S*8

=ld 9./.0 10.0.0 10.0.0 10.0.0 10.0.0 10.0.0 10.0.0 10.0.0 10.0.0 10.0.0 10.0.0 10.0.0 10.0.0 10.0.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.2.0 10.2.1 10.2.1 10.2.1

:ew 10.0.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.1 10.3.0 10.3.0 10.3.0

10.2.1 10.3.0 10.2.1 10.3.0 10.2.1 10.3.0 10.2.1 10.2.1 10.2.1 10.2.1 10.2.1 10.3.0 10.3.1 10.3.0 10.3.0 10.3.0 10.3.0 10.3.0 10.3.1 10./.0

10.3.1 10./.0 10.3.1 10.3.1 10.3.1 10.3.1 10.3.1 10.3.1 10./.0 10. .0 10. .0 10. .0 10. .0 10. .0 10.6.0 10./.0 10./.0 10./.0 10./.0 10./.0 10./.0 10. .0 10.6.0 10.6.0 10.6.0 10.6.0 10.6.0 10.7.0

10.6.0 10.7.0 10.6.0 10.7.0 10.6.0 10.7.0 10.6.0 10.7.0 10.7.0 &&'*'*

3GPP

%elease &&

,$ Chan#e history

3GPP TS $3'$($ )&&'$'* ($*&$+*,)

9ate 2012-03 2012-03 2012-03 2012-03 2012-03 2012-06 2012-06 2012-06 2012-06 2012-06 2012-06 2012-06 2012-06 2012-06 2012-06 2012-09 2012-09 2012-09 2012-09 2012-09

TSG A SPSPSPSPSPSPSPSPSPSPSP6 6 6 6 6 6

TSG 9oc' SP-1200<< SP-1200<< SP-1200<< SP-1200<6 SP-1200<6 SP-120239 SP-120239 SP-1202/0 SP-120237 SP-120237 SP-120232 SP-120237 SP-1202/6 SP-1202/0 SP-1202 1 SP-120/<6 SP-120/<2 SP-120/<2 SP-120/<2 SP-120/<

C% 0727 0729 073 07/3 07/6 0760 0761 076/ 0766 0772 0793 079 0797 0<01 0<22 0726 0<09 0<30 0<3/ 0<36

%ev 1 1 1 3 2 7 6 1 2 2 / 1 1 1 / 3 / 1 -

Cat * * * 8 8 * * * ' ' ' ' 8 * * * * * * ,

SP- 6 SP- 6 SP- 6 SP- 6 SPSPSPSPSP7 7 7 7 7

Su ject8Comment ,#&ri4ic&tio( o4 det&c% $rocedure 2%e( 9S! i" &cti6&ted ,orrectio( o4 re4ere(ce ,#&ri4ic&tio( &)out PLM+ "e#ectio( 4or ,S dom&i( 9S! de&cti6&tio( e0ce$tio( 4or PS o(#: SMS SMS o6er SG" u"&3e to "u$$ort +'S $rocedure" 4or PS o(#: SMS ,#&ri4:i(3 t%e 4e&ture de4i(itio( 4or SMS i( MME ,orrectio( o4 SMS i( MME re#&ted ,&(ce##&tio( Proce""e" UE '6&i#&)i#it: 4or SMS ;&(d#i(3 o4 SMS o6er SG" i( c&"e o4 &)"e(t L'9 ,orrectio( 4or do2(#i(B u(re&c%&)#e due to 2ro(3 "u"$e(di(3 ,orrectio( o4 ":"tem )e%&6iour u$o( PG> i(iti&ted #&"t P5P ,o(te0t 5e&cti6&tio( 2%e( SG" i" &""oci&ted &(d 9S! i" &cti6&ted P&rti&# VL! 4&i#ure or VL! re"t&rt 2it% ,S*8 &(d 9S! T&Bi(3 UE "u$$ort1(o(-"u$$ort o4 GE!'+ (et2orB "%&ri(3 i(to &ccou(t i( ,S*8 U$d&te to SMS i( MME 'rc%itecture re4ere(ce $oi(t" '#i3(me(t 2it% "t&3e 3 4or t%e co(ditio( to de&cti6&te 9S! ): t%e SGS+ SG" Su$$ort 4or MS, i( Poo# to &6oid du&# VL! re3i"tr&tio(. ,#&ri4ic&tio( o( 9S! &(d OSMS i( MMEO ,orrectio( o4 PS-o(#: *e&ture 5e"cri$tio( SMS i( MME co("o#id&ted de"cri$tio( &(d u$d&ted "co$e !emo6i(3 +M7-999

=ld 10.7.0 10.7.0 10.7.0 10.7.0 10.7.0 11.0.0 11.0.0 11.0.0 11.0.0 11.0.0 11.0.0

:ew 11.0.0 11.0.0 11.0.0 11.0.0 11.0.0 11.1.0 11.1.0 11.1.0 11.1.0 11.1.0 11.1.0

11.0.0 11.1.0 11.0.0 11.1.0 11.0.0 11.1.0 11.0.0 11.1.0 11.1.0 11.1.0 11.1.0 11.1.0 11.1.0 11.2.0 11.2.0 11.2.0 11.2.0 11.2.0

3GPP