23009-b20

8/9/2019 23009-b20

1/302

3GPP TS 23.009 V11.2.0(2012-12)3rd Generation Partnership Project;

Technical Specification Group Core Network and Terminals;Handover procedures

(elease !!"

The present document has been developed within the 3rdGeneration Partnership Project (3GPPTM) and may be further elaborated for the purposes of 3GPP.

The present document has not been subject to any approval process by the 3GPP Oranisational Partners and shall not be implemented.

This !pecification is provided for future development wor" within 3GPPonly. The Oranisational Partners accept no liability for any use of this

!pecification.!pecifications and reports for implementation of the 3GPPTMsystem should be obtained via the 3GPP Oranisational Partners# Publications Offices.

8/9/2019 23009-b20

2/302

8/9/2019 23009-b20

3/302

*ontent

7oreword..........................................................................................................................................................

, !cope......................................................................................................................................................

* /eferences..............................................................................................................................................

3 bbreviations and definitions...............................................................................................................3., bbreviations.....................................................................................................................................................

3.* 8efinitions.........................................................................................................................................................

9 /ole- functional composition of M!1s and interfaces for handover.....................................................9., M!1:...............................................................................................................................................................

9.,., /ole of M!1:............................................................................................................................................9.,.* 7unctional composition of M!1: and its interfaces for handover............................................................9.* M!1:0...............................................................................................................................................................9.*., /ole of M!1:0............................................................................................................................................

9.*.* 7unctional composition of M!1:0 and its interfaces for handover............................................................9.3 3G;M!1:........................................................................................................................................................

9.3., /ole of 3G;M!1:.....................................................................................................................................9.3.* 7unctional composition of 3G;M!1: and its interfaces for handover11 M!1..................................................................................................................................9.=.* 7unctional composition of !/>11 M!1 and its interfaces for handover11 M!1................................................................................................................................9.=.9 7unctional composition of v!/>11 M!1 and its interfaces for handover

8/9/2019 23009-b20

4/302

E General 8escription of the procedures for inter : 3G;M!1 handovers................................................E., ?andover MT! to G!M..................................................................................................................................E.,., 0asic ?andover procedure reCuirin a circuit connection between 3G;M!1 : and M!1:0...................E.,.,., Aith one circuit connection....................................................................................................................

E.,.,.* Aith multiple circuit connections (Optional functionality)...................................................................E.,.* 0asic MT! to G!M ?andover procedure not reCuirin the establishment of a circuit connection

between 3G;M!1: and M!1:0................................................................................................................E.,.3 Procedure for subseCuent MT! to G!M handover reCuirin a circuit connection...................................E.,.3., 8escription of subseCuent MT! to G!M handover procedure i)D 3G;M!1:0 to M!1:.................E.,.3.,., Aith one circuit connection..............................................................................................................

E.,.3.,.* Aith multiple circuit connections (Optional functionality)..............................................................E.,.3.* 8escription of subseCuent MT! to G!M handover procedure ii)D 3G;M!1:0 to M!1:0#...............E.,.3.*., Aith one circuit connection....................................................................................................................E.,.3.*.* Aith multiple circuit connections (Optional functionality)..............................................................E.,.9 Procedure for subseCuent MT! to G!M handover not reCuirin a circuit connection.............................E.,.9., 8escription of subseCuent MT! to G!M handover procedure i)D 3G;M!1:0 to M!1:.................

E.,.9.* 8escription of the subseCuent MT! to G!M handover procedure without circuit connection ii)D3G;M!1:0 to M!1:0#..........................................................................................................................

E.* ?andover G!M to MT!..................................................................................................................................

E.*., 0asic ?andover procedure reCuirin a circuit connection between M!1: and 3G;M!1:0....................E.*.* 0asic G!M to MT! ?andover procedure not reCuirin the establishment of a circuit connection

between M!1: and 3G;M!1:0................................................................................................................

E.*.3 Procedure for subseCuent G!M to MT! handover reCuirin a circuit connection...................................E.*.3., 8escription of subseCuent G!M to MT! handover procedure i)D M!1:0 to 3G;M!1:.................E.*.3.* 8escription of subseCuent G!M to MT! handover procedure ii)D M!1:0 to 3G;M!1:0#...............E.*.9 Procedure for subseCuent G!M to MT! handover not reCuirin a circuit connection.............................E.*.9., 8escription of subseCuent G!M to MT! handover procedure without circuit connection i)D

M!1:0 to 3G;M!1:...........................................................................................................................

E.*.9.* 8escription of subseCuent G!M to MT! handover procedure without circuit connection ii)DM!1:0 to 3G;M!1:0#..........................................................................................................................

E.3 !/&! /elocation...............................................................................................................................................E.3., 0asic relocation procedure reCuirin a circuit connection between 3G;M!1: and 3G;M!1:0.............

E.3.,., Aith one circuit connection....................................................................................................................E.3.,.* Aith multiple circuit connections (Optional functionality)...................................................................

E.3.,.*., 3G;M!1:0 does not support multiple bearers.................................................................................E.3.,.*.* 3G;M!1:0 supports multiple bearers.............................................................................................E.3.* 0asic relocation procedure not reCuirin the establishment of a circuit connection between

3G;M!1: and 3G;M!1:0...................................................................................................................... .E.3.3 Procedure for subseCuent relocation reCuirin a circuit connection............................................................E.3.3., 8escription of subseCuent relocation procedure i)D 3G;M!1:0 to 3G;M!1:...................................

E.3.3.,., Aith one circuit connection..............................................................................................................E.3.3.,.* Aith multiple circuit connections (Optional functionality)..............................................................E.3.3.* 8escription of subseCuent relocation procedure ii)D 3G;M!1:0 to 3G;M!1:0#.................................E.3.3.*., Aith one circuit connection..............................................................................................................E.3.3.*.* Aith multiple circuit connections (Optional functionality)..............................................................

E.3.9 Procedure for subseCuent relocation not reCuirin a circuit connection......................................................E.3.9., 8escription of subseCuent relocation procedure i)D 3G;M!1:0 to 3G;M!1:...................................E.3.9.* 8escription of subseCuent relocation procedure ii)D 3G;M!1:0 to 3G;M!1:0##................................

F 8etailed procedures in M!1:.............................................................................................................F., 0!!

8/9/2019 23009-b20

5/302

,+.9 MP procedures M!1:0 (functional unit 9).....................................................................................................,+.= %nterwor"in between ?andover control procedures and MP procedures in M!1:0....................................,+.@ 1ompatibility with G!M Phase ,......................................................................................................................

,, 8etailed procedures in 3G;M!1:......................................................................................................,,., /&1

8/9/2019 23009-b20

6/302

oreord

This Technical !pecification (T!) has been produced by the 3 rdGeneration Partnership Project (3GPP).

The present document provides a mechanism ivin reliable transfer of sinallin messaes within the 3GPP system.

The contents of the present document are subject to continuin wor" within the T!G and may chane followin formalT!G approval. !hould the T!G modify the contents of the present document- it will be re:released by the T!G with anidentifyin chane of release date and an increase in version number as followsD

>ersion '.y.

whereD

' the first diitD

, presented to T!G for information

* presented to T!G for approval

3 or reater indicates T!G approved document under chane control.

y the second diit is incremented for all chanes of substance- i.e. technical enhancements- corrections-updates- etc.

the third diit is incremented when editorial only chanes have been incorporated in the document.

3GPP

+ 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

7/302

1 S"o%e

The present document contains a detailed description of the handover procedures to be used in P5M&s. The purpose ofthe handover procedures- as described in the present document- are to ensure that the connection to the Mobile !tation

(M!) or ser 2Cuipment (2) is maintained as it moves from one cell or radio networ" to another. The documentdefines the circuit switched handover functionality based on the service reCuirements in 3GPP T! **.,*F HFI. 7or the

circuit switched handover functionality related to !/>11 and v!/>11- it is based on the service reCuirements in3GPP T! *3.*,@ H*@I.

The present document considers the followin five handover casesD

i) handover between 0ase !tation !ubsystems (0!!) connected to the same M!1- this is termed an %ntra:M!1handover

ii) handover between /adio &etwor" !ubsystems (/&!) connected to the same 3G;M!1- this is termed an %ntra:3G;M!1 handover

8/9/2019 23009-b20

8/302

%n case iv) the handover procedures shall transport the :interface messaes between 3G;M!1 and M!1 described inthe Mobile pplication Part (MP)- 3GPP T! *F.++* H,*I.

%n case iv) the relocation procedure shall transport the %u:interface messaes between 3G;M!1: and 3G;M!1:0described in the Mobile pplication Part (MP)- 3GPP T! *F.++* H,*I.

The interwor"in between the 3GPP T! *F.++* H,*I protocol and the 3GPP T! 9E.++E H=I protocol is described in the3GPP T! *F.+,+ HEI.

Multicall supplementary service is not applicable in G2/& %u mode and relocation of Multicalls is therefore only

possible within T/&.

2nhanced !/&! relocation is possible only within T/& between two /&!s conntected to the same 3G;M!1- i.e. incase ii).

?andovers- which ta"e place on the same M!1 are termed %ntra:M!1 handovers this includes both %nter:0!! and%ntra:0!! handovers.

?andovers- which ta"e place on the same 3G;M!1 are termed %ntra:3G;M!1 handovers this includes %nter:/&!handovers and optionally /&! to 0!! and 0!! to /&! handovers.

%n the conte't of this specification the term %nter!ystem handover can also refer to a handover which ta"es placebetween a 0ase !tation servin a mobile station in %u mode and a 0ase !tation servin a mobile in

8/9/2019 23009-b20

9/302

&OT2 ,D The messae primitive names used in the !85 diarams and messae flows in the present document donot represent the actual messaes specified in the G!M or 3GPP stae 3 technical specifications. Theprimitive names are only intended to be indicative of their use in the present document.

The M!1 server enhanced for !/>11 and the M!1 server enhanced for v!/>11 as specified in 3GPP T! *3.*,@ H*@I

follows the procedures defined for 3G;M!1: in the present specification with the e'ceptions and additions as

specified in subclause 9.=.

2 Re4eren"e

The followin documents contain provisions which- throuh reference in this te't- constitute provisions of the present

document.

/eferences are either specific (identified by date of publication- edition number- version number- etc.) or

non:specific.

7or a specific reference- subseCuent revisions do not apply.

7or a non:specific reference- the latest version applies. %n the case of a reference to a 3GPP document (includina 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 %T:T /ecommendation K.,,ED Jbnormal conditions : !pecial release arranementsJ.

H*I >oid.

H*aI 3GPP T/ *,.F+=D J3G >ocabularyJ.

H3I 3GPP T! 93.+@ED J>oice Group 1all !ervice (>G1!) !tae *J.

H9I 3GPP T! 9=.++ED J/adio !ubsystem 5in" 1ontrolJ.

H=I 3GPP T! 9E.++ED JMobile !witchin 1entre : 0ase !tation !ystem (M!1:0!!) %nterface 5ayer 3specificationJ.

H@I 3GPP T! 9E.+=ED J0ase !tation 1ontroler : 0ase Transceiver !tation (0!1:0T!) %nterface 5ayer3 specificationJ.

HBI 3GPP T! 9F.++ED Jpplication of the 0ase !tation !ystem pplication Part (0!!P) on the2:interfaceJ.

HEI 3GPP T! *F.+,+D J%nformation 2lement Mappin between Mobile !tation : 0ase !tation !ystem(M!:0!!) and 0ase !tation !ystem : Mobile:services !witchin 1entre (0!!:M!1) !inallinprocedures and the Mobile pplication Part (MP)J.

HFI 3GPP T! **.,*FD J?andover /eCuirements between MT! and G!M or other /adio !ystemsJ.

H,+I 3GPP T! *9.++ED JMobile /adio %nterface 5ayer 3 specification 1ore &etwor" Protocols!tae 3J.

H,,I 3GPP T! *=.9,3D JT/& %u interface /&P sinallinJ.

H,*I 3GPP T! *F.++*D JMobile pplication Part (MP) specificationJ.

H,3I 3GPP T! *=.3+3D J2 functions and inter:layer procedures in connected modeJ.

H,9I 3GPP T! *=.33,D J/adio /esource 1ontrol (//1) Protocol !pecificationJ.

H,=I 3GPP T! *F.,+ED Jpplication of the /adio ccess &etwor" pplication Part (/&P) on the 2:interfaceJ.

H,@I %T:T /ecommendation G.B,,D JPulse code modulation (P1M) of voice freCuenciesJ.

H,BI 3GPP T! *3.,3=D JMulticall supplementary service !tae *J.

3GPP

& 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

10/302

8/9/2019 23009-b20

11/302

!/&! !ervin /&!!T&:!/ !ession Transfer &umber for !/:>112 ser 2Cuipment is a terminal that supports !%M and the MT! u interface2

8/9/2019 23009-b20

12/302

* S#eifi +ehavio"r Information - I" (*S+I-I")D information that is sent from the M!1 to the /& and that canbe used to derive specific information about the 2#s capabilities.

7or the purposes of the present document- the followin terms and definitions iven in 3GPP T! *3.*,@ H*@I applyD

S'CC

vS'CC

7or the purposes of the present document- the followin terms and definitions iven in 3GPP T! *3.*3B H3,I applyD

SCC AS

7or the purposes of the present document- the followin terms and definitions iven in 3GPP T! *9.++E H,+I applyD

CSG ell

CSG I&

Ro$e, 4un"t#ona$ "o%o#t#on o4 MS* and #nter4a"e

4or handover

.1 MS*-&

.1.1 Ro$e o4 MS*-&

%n the %ntra:M!1 handover case (includin J0!! %nternal ?andover with M!1 !upportJ with o%P)- the M!1:(simply termed M!1) controls the call- the mobility manaement and the radio resources before- durin and after an%ntra:M!1 handover. Ahen 0!!P procedures have to be performed- they are initiated and driven by M!1:.

%f o%P is supported by M!1: and 0!!- then the 0!! or the M!1: may initiate a J0!! %nternal ?andover with M!1

!upportJ as described in detail in subclause @.3.

%n the %nter:M!1 handover case- M!1: is the M!1 which controls the call and the mobility manaement of theMobile durin the call- before- durin and after a basic or subseCuent handover. Ahen 0!!P procedures related todedicated resources have to be performed towards the M!- they are initiated and driven by M!1:. The M!1: :M!1:0 interface wor"s as a M!1 : 0!! interface for a subset of 0!!MP procedures. These 0!!MP procedures-

described in 3GPP T! 9F.++E HBI are only those related to dedicated resources. The 8TP sinallin is relayedtransparently by M!1:0 between M!1: and the M!.

8urin a basic handover- M!1: initiates and controls all the handover procedure- from its initiation (reception of?andover /eCuired from 0!!: on :interface) until its completion (reception of ?andover 1omplete from M!1:0 on

2:interface).

7or handover to an area where J%ntra 8omain 1onnection of /& &odes to Multiple 1& &odesJ is applied- M!1:

can have multiple taret 1& nodes for each handover taret in a pool:area as specified in 3GPP T! *3.*3@ H,EI.

8urin a subseCuent handover bac" to M!1:- M!1: acts as a 0!! towards M!1:0- which controls the handover

procedure until the termination in M!1: of the handover radio resources allocation (sendin of the ?andover /eCuestc"nowlede to M!1:0 from M!1:). Then all handover related messaes shall terminate at M!1: (e.. ?andover8etect

8/9/2019 23009-b20

13/302

8urin a basic inter:system handover- M!1: initiates and controls all the handover procedure- from its initiation(reception of ?andover /eCuired from 0!!: on :interface) until its completion (reception of ?andover 1ompletefrom 3G;M!1:0 on 2:interface).

8urin a subseCuent inter:system handover bac" to M!1:- M!1: acts as a 0!! towards 3G;M!1:0- which controls

the handover procedure until the termination in M!1: of the handover radio resources allocation (sendin of the

?andover /eCuest c"nowlede to 3G;M!1:0 from M!1:). Then all handover related messaes shall terminate atM!1: (e.. ?andover 8etect

8/9/2019 23009-b20

14/302

.1.2 un"t#ona$ "o%o#t#on o4 MS*-& and #t #nter4a"e 4or handover

%n order to simplify the description of the handover procedures the controllin M!1 (M!1:) can be considered to becomposed of five functional units- as shown in fiure ,.

!inallin functionsD

,) 0!1

8/9/2019 23009-b20

15/302

0!1

8/9/2019 23009-b20

16/302

0LL

LL

a) %ntra:M!1 ?andover case.

0LL

0LL

b) 0asic ?andover case and handover of M! to M! call in the same M!1.

0L

0LLL

0LL

c) !ubseCuent ?andover case

T+ :n a) and ') &; # re$eaed a4ter handover11 M!1 as described in subclause 9.=., with the followin modifications for av!/>11 handoverD

: 8urin a v!/>11 handover- v!/>11 M!1 initiates and controls all the 1ircuit !witch handover procedure-from its initiation (i.e.- reception of !/>11 P! to 1! /eCuest via the !v:interface as defined in3GPP T! *F.*E+ H*BI from MM2) until its completion (i.e.- reception of /elocation

8/9/2019 23009-b20

29/302

%n order to determine if a handover is reCuired- due to /7 criteria- it is typically the M! that shall ta"e radiomeasurements from neihbourin cells. These measurements are reported to the servin cell on an event driven orreular basis. Ahen a networ" determines a need for e'ecutin a handover the procedures iven in 3GPP T! 9E.++E H=I-3GPP T! *=.3+3 H,3I- 3GPP T! *=.33, H,9I are followed.

The decision process used to determine when to perform soft handover or hard handover will typically differ.

8ependin on the support for soft or hard handover the %ntra:M!1 and %nter:M!1 handover may differ.

%n the case of an onoin G!M voice roup call (see 3GPP T! 93.+@E H3I) the criteria described above shall only applyto the mobile station currently assined the uplin" and other users with a dedicated connection- no actions shall be ta"en

for the listenin users.

6 Genera$ de"r#%t#on o4 the %ro"edure 4or #ntra - MS*handover

This clause ives a brief overview of the procedures that shall be followed when performin %ntra:M!1 handovers.8etailed e'planation of these procedures can be found in 3GPP T! 9E.++E H=I and 3GPP T! *9.++E H,+I.

There are three types of G!M handover that involve a sinle 0!! and a sinle M!1. These are J%nternal ?andoverJ-J0!! %nternal ?andover with M!1 !upportJ andJ 2'ternal ?andoverJ.

n J%nternal ?andoverJ ta"es place between channels on a cell or cells controlled by a sinle 0!!- without reference tothe M!1- althouh the M!1 maybe informed of its occurrence after completion. This typical case can be used by the0!! e.. if the :%nterface ser Plane is not to be modified. This J%nternal ?andoverJ may ta"e place with oT8M or

with o%P and is not considered in the present document.

J0!! %nternal ?andover with M!1 !upportJ shall only be used if o%P is supported by both M!1 and 0!! and if the:%nterface ser Plane has to be modified. %n that case the 0!! or the M!1 may initiate a J0!! %nternal ?andover withM!1 !upportJ procedure as described in detail in subclause @.3 in this document.

&OT2D 7rom 1ore &etwor" perspective this J0!! %nternal ?andover with M!1 !upportJ is an J2'ternal

?andoverJ- because the M!1 is actively involved- althouh it is called J%nternal ?andoverJ in 3GPP T!9E.++E- because the call stays within one 0!!.

?andovers between channels on the same cell or between cells on the same 0!! which are controlled by the M!1 (as

defined prior to the introduction of o%P) are termed J2'ternal ?andoversJ and use identical procedures to those for%nter:0!!:%ntra:M!1 handovers. J2'ternal ?andoversJ are also specified with o%P ser Plane transport- for e'amplethe handover from speech to data services.?andovers from a 0!! to an /&! controlled by the same 3G;M!1 are intra:3G;M!1 G!M to MT! handovers. ?andovers from an /&! to a 0!! controlled by the same 3G;M!1 are intra:3G;M!1 MT! to G!M handovers.

There are two types of handover in MT!D soft handover and hard handover. The first one is fully performed withinT/&- without involvin the core networ". The second one may be also performed within T/& or G2/&- orbetween G2/& and T/&- or the core networ" may be involved if the %ur or %ur: interface between /&!s does

not e'ist. This case of hard handover involvin the core networ" is covered in the present document- toether with!/&! relocation with %ur or %ur: interface.

6.1 Pro"edure 4or :ntra-MS* >andover

The procedure for a successful 2'ternal %ntra:M!1 handover is shown in fiure B. %t is assumed that selection of acandidate M! has already ta"en place within the 0!! based upon the criteria presented in clause =. The e'act alorithm-in the 0!!- for determinin a candidate M! is not addressed in the present document. The procedures discussed do notma"e use of the Mobile pplication Part (MP)- represented by sinallin function 9 in fiure * and fiure 3. Theprocedure described in this clause covers case i).

3GPP

#& 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

30/302

M! M!

0!!: M!1: 0!!:0

:?andover:/eCuired

:?andover:/eCuest

:?andover:/eCuest:c"

:?andover:1ommand

/%:?O:1ommand/%:?O:ccess

:?andover:8etect/%:?O:1omplete

:?andover:1omplete

:1lear:1ommand

:1lear:1omplete

.i/ure ,0 6asic 9:ternal 4ntra1SC Handover Procedure

The successful operation of the procedure is as follows. Ahen the 0!! (0!!:)- currently supportin the M!-determines that the M! reCuires to be handed over it will send an :?&8O>2/:/2K%/28 messae to the M!1(M!1:). The :?&8O>2/:/2K%/28 messae shall contain a list of cells- or a sinle cell- to which the M! canbe handed over. The list of cells shall be iven in order of preference based upon operator determined criteria (Thesecriteria are not addressed within the present document and are operator dependent). Ahen the M!1: receives the :?&8O>2/:/2K%/28 messae it shall bein the process of handin over the M! to a new 0!! (0!!:0). (&OT2D

0!!: and 0!!:0 maybe the same 0!!). The M!1: shall enerate an :?&8O>2/:/2K2!T messae to theselected 0!! (0!!:0). Ahen 0!!:0 receives the :?&8O>2/:/2K2!T messae it shall ta"e the necessaryaction to allow the M! to access the radio resource of 0!!:0- this is detailed in 3GPP T! 9E.+=E H@I and in

3GPP T! 9=.++E H9I. The switchin of the radio resource throuh the necessary terrestrial resources is detailed in3GPP T! *9.++E H,+I and 3GPP T! 9E.++E H=I.

Once resource allocation has been completed by 0!!:0 it shall return an :?&8O>2/:/2K2!T:1$. to M!1:.Ahen this messae is received by M!1: it shall bein the process of instructin the M! to tune to a new dedicatedradio resource. n :?&8O>2/:1OMM&8 will be sent by the M!1: to 0!!:. On receipt of the :?&8O>2/:1OMM&8 messae 0!!: will send the radio interface messae /%:?&8O>2/:1OMM&8-containin a ?andover /eference number previously allocated by 0!!:0- to the M!. The M! will then access the newradio resource usin the ?andover /eference number contained in the /%:?&8O>2/:112!! messae. The

number will be chec"ed by 0!!:0 to ensure it is as e'pected and the correct M! has been captured. %f this is the correctM! then the 0!!:0 shall send an :?&8O>2/:82T21T to M!1:. Ahen the M! is successfully communicatinwith the 0!!:0 a /%:?&8O>2/:1OMP52T2 messae will be sent by the M! to 0!!:0. The 0!!:0 will then sendan :?&8O>2/:1OMP52T2 messae to M!1:.

&OT2D The :?&8O>2/:/2K2!T:1$ from 0!!:0 contains the complete /adio %nterface messae thatshall be sent by 0!!: to the M! in the /%:?&8O>2/:1OMM&8- M!1: transparently passes thisradio interface messae onto 0!!:.

fter M!1: has received the :?&8O>2/:1OMP52T2 messae from 0!!:0 it shall bein to release theresources allocated on 0!!:. %n fiure B the resource is released by usin the :152/:1OMM&8 seCuence.

%n the case of onoin G!M voice roup calls the clearin of resources on 0!!: shall not be used if the resources arestill be used on the down lin".

%f a failure occurs durin the handover attempt- for e'ample :?&8O>2/:7%5/2 returned from 0!!: or 0!!:

0- then M!1: will terminate the handover to 0!!:0. nder these conditions M!1: may optionally ta"e one of anumber of actionsD

i) retry the handover to the same cell

3GPP

3% 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

31/302

ii) select the ne't cell from the list contained in the :?&8O>2/:/2K%/28 messae and attempt a handoverto the new cell

iii) await the ne't :?&8O>2/:/2K%/28 messae

iv) send an :?&8O>2/:/2K%/28:/2N21T to 0!!:- if an :?&8O>2/:1OMM&8 has not alreadybeen sent.

The e'act action ta"en is dependent on whether the failure occurs before or after the :?&8O>2/:1OMM&8 hasbeen sent.

%n all cases the e'istin connection to the M! shall not be cleared e'cept in the case of e'piry of the timer for receipt of:?&8O>2/:1OMP52T2.

8urin the period that the M! is not in communication with the networ" M!1: shall Cueue all appropriate messaes.

ll messaes shall be delivered to the M! once communication is resumed . %n the case of an %ntra:M!1 handover onM!1:0 then the messaes shall be Cueued by M!1:0.

%n the case of onoin G!M voice roup calls if a failure occurs when handin over a user on a dedicated channel thenthe procedures described above may optionally be applied.

7or the case of subseCuent %nter:0!! %ntra:M!1:0 or %nter:0!! %ntra:3G;M!1:0 handover the followin appliesD

%f handover to an over %P capable 0!!:0 is performed- M!1:02/:/2K2!T messae to 0!!:0. M!1:0

8/9/2019 23009-b20

32/302

2

8/9/2019 23009-b20

33/302

8urin the period that the 2andover

The procedure for a successful %ntra:3G;M!1 handover is shown in fiure F. %t is assumed that selection of a candidate2

8/9/2019 23009-b20

34/302

2

0!!: 3G M!1: /&!:0

:?andover:/eCuired%u:/elocation:/eCuest

%u:/elocation:/eCuest:c"

:?andover:1ommand

/%:?O:1ommand

%u:/elocation:8etect//1:?O:1omplete

%u:/elocation:1omplete

:1lear:1ommand

:1lear:1omplete

22/:/2K%/28 messae tothe 3G;M!1 (3G;M!1:). The :?&8O>2/:/2K%/28 messae shall contain a sinle cell- to which the 2 canbe handed over. Ahen the 3G;M!1: receives the :?&8O>2/:/2K%/28 messae it shall bein the process ofhandin over the 2 to a new /&! (/&!:0). The 3G;M!1: shall enerate an %u:/25O1T%O&:/2K2!Tmessae to the selected /&! (/&!:0). 7or handover of a speech call to T/& %u mode- 3G;M!1: shall include a

&! !ynch %ndicator in the %u:/25O1T%O&:/2K2!T messae.

%f 3G;M!1: supports inter:system handover to a 1!G cell and 0!!: includes a 1!G %8 for the taret cell in the :

?&8O>2/:/2K%/28 messae- then 3G;M!1: shall chec" the 1!G membership of the 2 for the taret cell asdescribed in subclause 9.3., before eneratin the %u:/25O1T%O&:/2K2!T messae. %f the 2 fails the 1!Gmembership chec" and the taret cell is a 1!G cell- 3G;M!1: shall send an :?&8O>2/:/2K%/28:/2N21T

to 0!!:.

Ahen /&!:0 receives the %u:/25O1T%O&:/2K2!T messae it shall ta"e the necessary action to allow the 2 toaccess the radio resource of /&!:0- this is detailed in the 3GPP T! *=.3++ series and the 3GPP T! *=.*++ series of3GPP Technical !pecifications. The switchin of the radio resource throuh the necessary terrestrial resources is

detailed in the 3GPP T! *=.93+ series and 3GPP T! *=.9,3 H,,I.

Once resource allocation has been completed by /&!:0- it shall return an %u:/25O1T%O&:/2K2!T:1$. to3G;M!1:. Ahen this messae is received by 3G;M!1: it shall bein the process of instructin the 2 to tune to anew dedicated radio resource. n :?&8O>2/:1OMM&8 will be sent by the 3G;M!1: to 0!!:. On receipt

of the :?&8O>2/:1OMM&8 messae 0!!: will send the radio interface messae /%:?&8O>2/:1OMM&8. The 2 will then access the new radio resource. On detection of the 2- the /&!:0 shall send an %u:/25O1T%O&:82T21T to 3G;M!1:. Ahen the 2 is successfully communicatin with the /&!:0 an //1:?&8O>2/:1OMP52T2 messae will be sent by the 2 to /&!:0. The /&!:0 will then send an %u:/25O1T%O&:1OMP52T2 messae to 3G;M!1:.

&OT2D The %u:/25O1T%O&:/2K2!T:1$ from /&!:0 contains the complete //1 messae that shall besent by 0!!: to the M! in the /%:?&8O>2/:1OMM&8- 3G;M!1: transparently passes thisradio interface messae onto 0!!:.

fter 3G;M!1: has received the %u:/25O1T%O&:1OMP52T2 messae from /&!:0- it shall bein to release theresources allocated on 0!!:. %n fiure F the resource is released by usin the :152/:1OMM&8 seCuence.

%f a failure occurs durin the handover attempt- for e'ample- :?&8O>2/:7%5/2 returned from 0!!: or%u:/25O1T%O& 7%5/2 returned from /&!:0- then 3G;M!1: will terminate the handover to /&!:0. nderthese conditions 3G;M!1: may optionally ta"e one of a number of actionsD

i) await the ne't :?&8O>2/:/2K%/28 messae

3GPP

3) 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

35/302

ii) send an :?&8O>2/:/2K%/28:/2N21T to 0!!:- if an :?&8O>2/:1OMM&8 has not alreadybeen sent.

The e'act action ta"en is dependent on whether the failure occurs before or after the :?&8O>2/:1OMM&8 hasbeen sent.

%n all cases the e'istin connection to the 2 shall not be cleared e'cept in the case of e'piry of the timer for receipt of%u:/25O1T%O&:1OMP52T2.

8urin the period that the 2 is not in communication with the networ" 3G;M!1: shall Cueue all appropriate

messaes. ll messaes shall be delivered to the 2 once communication is resumed. %n the case of an %ntra:3G;M!1G!M to MT! handover on 3G;M!1:0 then the messaes shall be Cueued by 3G;M!1:0.

6.2.3 Pro"edure 4or :ntra-3G=MS* SRS Re$o"at#on

The procedure for a successful %ntra:3G;M!1 !/&! /elocation is shown in fiures ,+ and ,,. 7or a successful %ntra:3G;M!1 2nhanced !/&! /elocation the procedure is shown in fiures ,,a and ,,b. !/&! /elocation and 2nhanced!/&! /elocation are used to relocate the servin /&! functionality from one /&! to another. The procedures may ormay not involve chane of the radio resources assined for the correspondin 2. Ahether or not the /elocation

includes chane of radio resources assined for the 2 does not affect the !/&! /elocation procedure or 2nhanced!/&! /elocation procedure in the 1ore &etwor".

%n case of subseCuent %ntra:3G;M!1:0 !/&! relocation or %ntra:3G;M!1:0 2nhanced !/&! relocation the followinappliesD

: %f 3G;M!1:0 has previously received an order to perform location reportin at chane of !ervice rea from3G;M!1: and if 3G;M!1:0 also supports 5ocation /eportin 1ontrol- it shall issue the %u:5O1T%O&:/2PO/T%&G:1O&T/O5 messae towards the taret /&! immediately after successful completion ofrelocation. pon receipt of %u:5O1T%O&:/2PO/T- 3G;M!1:0 shall forward it towards 3G;M!1: via 2interface.

%f 3G;M!1:0 supports location reportin at chane of !ervice rea and if encapsulated 0!!P sinallin isused on the 2:interface- 3G;M!1:0 shall always initiate the 5ocation /eportin 1ontrol procedure at chane of

!ervice rea towards the taret /&!- since no reCuest for 5ocation /eportin can be received from M!1:. %nthat case- if an !/&! relocation is used- the 5ocation /eportin 1ontrol procedure shall be initiated by3G;M!1:0 after the /elocation /esource llocation procedure has been e'ecuted successfully otherwise

3G;M!1:0 shall initiate the 5ocation /eportin 1ontrol procedure when the completion of the 2nhanced !/&!/elocation has been confirmed by the taret /&!. The chane of !ervice rea shall be reported to M!1:within an :?&8O>2/:P2/7O/M28 messae.

%t is assumed that selection of a candidate 2 has already ta"en place within /&! based upon the criteria presentin inclause =. The e'act alorithm- in /&!- for determinin a candidate 2 is not addressed in the present document. The

procedure discussed does not ma"e use of the Mobile pplication Part (MP)- represented by sinallin function 9 infiures 9 and @. The procedure described in this clause covers case ii).

3GPP

3* 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

36/302

2 2

/&!: 3G;M!1: /&!:0

%u:/elocation:/eCuired

%u:/elocation:/eCuest

%u:/elocation:/eCuest:c"%u:/elocation:1ommand

%u:/elocation:8etect


%u: /elease:1ommand

%u: /elease:1omplete

%ur:!/&1:/elocation:1ommit

.i/ure !%0 6asic intra3G71SC SNS elocation Procedure

2 2

/&!: 3G;M!1: /&!:0

%u:/elocation:/eCuired

%u:/elocation:/eCuest

%u:/elocation:/eCuest:c"

%u:/elocation:1ommand

//:?O:1ommand

%u:/elocation:8etect //:?O:1omplete


%u: /elease:1ommand


8etection of 2 in

taret /&!

.i/ure !!0 6asic intra3G71SC SNS elocation Procedure comined with hard chan/eof radio resources (Hard Handover with switch in the Core Network"

3GPP

3+ 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

37/302

2 2

/&!: 3G;M!1: /&!:0

%u:2nhanced /elocation

1omplete /eCuest

%u: /elease:1ommand


%ur:2nhanced /elocation /eCuest

%ur:2nhanced /elocation /esponse


1omplete /esponse

%u:2nhanced /elocation1omplete 1onfirm

.i/ure !!a0 6asic intra3G71SC 9nhanced SNS elocation Procedure

2 2

/&!: 3G;M!1: /&!:0


1omplete /eCuest

%u: /elease:1ommand


%ur:2nhanced /elocation /eCuest

%ur:2nhanced /elocation /esponse


1omplete /esponse


1omplete 1onfirm

//:?O:1ommand

//:?O:1omplete

.i/ure !!0 6asic intra3G71SC 9nhanced SNS elocation Procedure comined with hard chan/eof radio resources (Hard Handover with switch in the Core Network"

6.2.3.1 ?#th no 'earer or one 'earer

6.2.3.1.1 SRS Re$o"at#on

The successful operation of the !/&! /elocation procedure is as follows. Ahen the !ervin /&! (/&!:) ma"es thedecision to perform the !/&! /elocation procedure it will send an %:/25O1T%O&:/2K%/28 messae to the

3G;M!1 (3G;M!1:). The %:/25O1T%O&:/2K%/28 messae shall contain the identifier of the taret /&! towhich the /elocation is to be performed. Ahen the 3G;M!1: receives the %:/25O1T%O&:/2K%/28 messaeit shall bein the process of relocatin the servin /&! functionality to the new /&! (/&!:0). The 3G;M!1: shallenerate an %:/25O1T%O&:/2K2!T messae to the selected /&! (/&!:0). 7or the relocation of a speech call toT/& %u mode- 3G;M!1: shall include the &! !ynch %ndicator in the %u:/25O1T%O&:/2K2!T- if the %u!elected codec to be used after the relocation is different from the %u 1urrently used codec.

%f 3G;M!1: supports !/&! /elocation to a 1!G cell and /&!: includes a 1!G %8 for the taret cell in the %:/25O1T%O&:/2K%/28 messae- then 3G;M!1: shall chec" the 1!G membership of the 2 for the taret cell

as described in subclause 9.3., before eneratin the %u:/25O1T%O&:/2K2!T messae. %f the 2 fails the 1!Gmembership chec" and the taret cell is a 1!G cell- 3G;M!1: shall send an %:/25O1T%O&:P/2P/T%O&:7%5/2 to /&!:.

3GPP

3, 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

38/302

Ahen /&!:0 receives the %:/25O1T%O&:/2K2!T messae it shall ta"e the necessary action to establish thenew %u transport bearers for each /adio ccess 0earer related to 3G;M!1: for the 2 in Cuestion- this is detailed inthe 3GPP T! *=.93+ series and 3GPP T! *=.9,3 H,,I.

Once resource allocation has been completed by /&!:0 it shall return an %:/25O1T%O&:/2K2!T:

1$&OA528G2 to 3G;M!1:. Ahen this messae is received by 3G;M!1:- and 3G;M!1: is ready for the

move in !ervin /&! functionality- it shall indicate the completion of the preparation phase on the core networ" sidefor the !/&! /elocation. n %:/25O1T%O&:1OMM&8 messae is sent by 3G;M!1: to /&!:. /&!: actsas followsD

i) if the procedure is a !/&! /elocation without chane of radio resources- which means that the %ur interfacebetween /&!: and /&!:0 can be used for the procedure- the /&!: shall send %/:!/&!:/25O1T%O&:1OMM%T messae to the /&!:0 to trier the /elocation e'ecution. !ee fiure ,+.

ii) if the procedure is a !/&! /elocation with chane of radio resources- which means that the %ur interfacebetween /&!: and /&!:0 is not used for the procedure- the /&!: shall trier the handover procedure on

the air interface by sendin the //1:?&8O>2/:1OMM&8 to the 2. The 2 will then access the newradio resources. !ee fiure ,,.

&OT2D The %:/25O1T%O&:/2K2!T:1$&OA528G2 from /&!:0 may optionally contain a

transparent container- which is transferred by 3G;M!1: to the /&!: usin the %:/25O1T%O&:1OMM&8 messae.

Ahen the relocation e'ecution trier is received- /&!:0 shall then ta"e the necessary action to assume the role of!ervin /&! and shall send an %:/25O1T%O&:82T21T messae to 3G;M!1:. Ahen the 2 is successfully incommunication with the /&!:0- then /&!:0 shall send an %:/25O1T%O&:1OMP52T2 messae to 3G;M!1:.

fter 3G;M!1: has received the %:/25O1T%O&:1OMP52T2 messae from /&!:0- it shall bein to release theresources associated to the /&!:. %n fiures ,+ and ,,- the resources are released by usin the%:/252!2:1OMM&8 seCuence.

%f a failure occurs durin the !/&! /elocation attempt- then 3G;M!1: will terminate the relocation to /&!:0. 7ore'ample- if %:/25O1T%O&:7%5/2 is returned from /&!:0 then 3G;M!1: will terminate the relocation to

/&!:0 and send %:/25O1T%O&:P/2P/T%O&:7%5/2 to /&!:. %f %:/25O1T%O&:1&125 isreturned from /&!:- then 3G;M!1: will terminate the relocation to /&!:0 and send %:/25O1T%O&:1&125:1$&OA528G2 to /&!:.

%n all cases the e'istin connection to the 2 shall not be cleared e'cept in the case of e'piry of the timer for receipt of

%u:/25O1T%O&:1OMP52T2.

8urin the period that the 2 is not in communication with the networ"- 3G;M!1: shall Cueue all appropriatemessaes. ll messaes shall be delivered to the 2 once communication is resumed. %n the case of an %ntra:3G;M!1!/&! /elocation (with or without chane of radio resources) on 3G;M!1:0- then the messaes shall be Cueued by3G;M!1:0.

6.2.3.1.2 +nhan"ed SRS Re$o"at#on

The successful operation of the 2nhanced !/&! /elocation procedure is as follows. Ahen the !ervin /&! (/&!:)ma"es the decision to perform the 2nhanced !/&! /elocation procedure it will send an %/:2&?&128:/25O1T%O&:/2K2!T messae to the new /&! (/&!:0). The %/:2&?&128 /25O1T%O&:/2K2!Tmessae shall contain the necessary information to set up a 1! /adio ccess 0earer in /&!:0.

Ahen /&!:0 receives the %/:2&?&128:/25O1T%O&:/2K2!T messae it shall ta"e the necessary actions toestablish the new %u transport bearers for the /adio ccess 0earer related to 3G;M!1: for the 2 in Cuestion- asdescribed in detail in the 3GPP T! *=.93+ series and 3GPP T! *=.9,3 H,,I- and the new transport bearers for the /adioccess 0earer related to /&!:. to enable data forwardin. /&!:0 shall initialie the %u P towards /&! - ifnecessary.

3GPP

3- 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

39/302

Once resource allocation has been completed by /&!:0 it shall return an %/:2&?&128:/25O1T%O&:/2!PO&!2 messae to /&1:. %f the resources cannot be allocated- /&!:0 returns an %/:2&?&128:/25O1T%O&:7%5/2 messae to /&!:- and /&!: terminates the procedure.

fter transmission of the %/:2&?&128:/25O1T%O&:/2!PO&!2 messae /&!:0 and /&!: act as followsD

i) %f the procedure is an 2nhanced !/&! /elocation without chane of radio resources- /&!:0 shall send an %:2&?&128 /25O1T%O&:1OMP52T2:/2K2!T messae to 3G;M!1: and start data fowardintowards /&!: for 5 data. fter receipt of the %/:2&?&128:/25O1T%O&:/2!PO&!2 messae /&!: shall start data forwardin towards /&!:0 for 85 data. !ee fiure ,,a.

ii) %f the procedure is an 2nhanced !/&! /elocation with chane of radio resources- when /&!: receives the%/:2&?&128:/25O1T%O&:/2!PO&!2 messaeit shall trier the handover procedure on the airinterface by sendin the //1:?&8O>2/:1OMM&8 to the 2 and start data forwardin towards /&!:0for 85 data. The 2 will then access the new radio resources. Ahen the 2 is successfully in communicationwith the /&!:0- then /&!:0 shall start data forwardin towards /&!: for 5 data and send an %:

2&?&128 /25O1T%O&:1OMP52T2:/2K2!T messae to 3G;M!1:. !ee fiure ,,b.

fter 3G;M!1: has received the %:2&?&128:/25O1T%O&:1OMP52T2:/2K2!T messae from /&!:0- itshall start to confiure the necessary %u resources for the /&!:0 and send the %:2&?&128:/25O1T%O&:

1OMP52T2:/2!PO&!2 messae to /&!:0. %f the necessary resources cannot be allocated or a failure occurs in3G;M!1:- it shall send an %:2&?&128:/25O1T%O&:1OMP52T2:7%5/2 messae to /&!:0.

fter /&1:0 has received the %:2&?&128:/25O1T%O&:1OMP52T2:/2!PO&!2 messaeit shall start toconfiure the %u transport bearer for each /adio ccess 0earer between the M!1: and /&1:0 and perform %u Pinitialiation- if necessary. fter the completion of the %u P initialiation- /&!:0 shall send an %:2&?&128:/25O1T%O&:1OMP52T2:1O&7%/M messae to 3G;M!1:.

fter 3G;M!1: has received the %:2&?&128:/25O1T%O&:1OMP52T2:1O&7%/M messae from /&!:0-it shall bein to release the resources associated to the /&!:. %n fiures ,,a and ,,b- the resources are released byusin the %:/252!2:1OMM&8 seCuence.

6.2.3.2 ?#th u$t#%$e 'earer (%t#ona$ 4un"t#ona$#t@)

%f 3G;M!1: supports the optional supplementary service Multicall (!ee 3GPP T! *3.,3= H,BI)- 3G;M!1: shallhave the followin functionality additionally to the description in subclause @.*.3.,.

7or !/&! /elocation- upon receipt of the %:/25O1T%O&:/2K%/28 from /&!:- 3G;M!1: enerates an %:/25O1T%O&:/2K2!T messae- which may include multiple bearers- to /&!:0.

Ahen an %:/25O1T%O&:/2K2!T:1$ is received from /&!:0- 3G;M!1: sends %:/25O1T%O&:1OMM&8- which indicates the bearers failed to set up in /&!:0 as bearers to be released- to /&!:.

fter 3G;M!1: receives a %:/25O1T%O&:1OMP52T2 messae from /&!:0- 3G;M!1: shall release the calls

via /&!:0- which have been carried by the bearers failed to set up in /&!:0- and then sends %:/252!2:1OMM&8 to /&!:.

7or 2nhanced !/&! /elocation- /&1: enerates an %/:2&?&128:/25O1T%O&:/2K2!T messae- whichmay include multiple bearers- to /&!:0. %f resources for at least one bearer are reserved in /&!:0- /&!:0 shall returnan %/:2&?&128:/25O1T%O&:/2!PO&!2 messae- which indicates the bearers failed to set up in /&!:0 as

bearers to be released- to /&1:.

Ahen the 2 is successfully in communication with the /&!:0- then /&!:0 shall send an %:2&?&128:/25O1T%O&:1OMP52T2:/2K2!T messae- which indicates the bearers failed to set up in /&!:0 as bearers tobe released- to 3G;M!1:.

fter 3G;M!1: receives the %:2&?&128:/25O1T%O&:1OMP52T2:/2K2!T messae from /&!:0-3G;M!1: shall release the calls via /&!:0- which have been carried by the bearers failed to set up in /&!:0- andthen sends %:/252!2:1OMM&8 to /&!:.

3GPP

3& 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

40/302

6.3 :nterna$ >andover #th MS* Su%%ort 4or :ntra-7SS handover#th &o:P

6.3.1 Genera$ e"r#%t#on o4 :nterna$ >andover #th MS* Su%%ort

%f the :%nterface ser Plane is carried over %P (or shall be handed over to %P) and one or more of the :%nterface serPlane parameters need to be modified- for e'ample the 1odec Type- or the 1odec 1onfiuration (0!! determines thatno compatible 1odec Type or 1odec 1onfiuration e'ists for the taret cell)- or the %P Transport 5ayer ddress- or the8P Port- or the 1!8ata /edundancy 5evel- or the :%nterface Type itself (e.. from T8M to %P or vice versa)- then aJ0!! %nternal ?andover with M!1 supportJ shall be performed (see 3GPP T! 9E.++E H=I subclause 3.,.=c.,).

The J0!! %nternal ?andover with M!1 supportJ for o%P is performed by the M!1 that is currently servin theconnected 0!! (in the followin just termed Jservin M!1J) it may be either M!1:- M!1:0- 3G;M!1: or3G;M!1:0.

&OT2D The J0!! %nternal ?andover with M!1 supportJ involves the servin M!1 actively in the handover. %t is

therefore in averae slower and more resource demandin than the 0!! %nternal ?andover without M!1support. %n order to uarantee a hih radio networ" performance the M!1 needs to react Cuic"ly and

handle this handover with hih priority.

The J0!! %nternal ?andover with M!1 supportJ applies only if both 0!! and 1ore &etwor" support the o%Pprocedures and messaes- and an :%nterface ser Plane connection has been established beforehand. The procedures

and messaes for this J0!! %nternal ?andover with M!1 supportJ are described in 3GPP T! 9E.++E H=I.

The J0!! %nternal ?andover with M!1 !upportJ can be initiated eitherD

a) by the 0!!- by sendin the :%&T2/&5:?&8O>2/:/2K%/28 messae orD

b) by the servin M!1- by sendin the :%&T2/&5:?&8O>2/:2&K%/ messae.

6.3.2 7SS-#n#t#ated :nterna$ >andover #th MS* Su%%ort

The 0!!:initiated J0!! %nternal ?andover with M!1 !upportJ starts with an :%&T2/&5:?&8O>2/:/2K%/28 messae from the 0!! to the servin M!1- for further details see 3GPP T! 9E.++E H=I- subclause 3.,.=c.n e'ample seCuence is shown in fiure @.3.*.,

0!!: !ervin M!1

:%&T2/&5:?&8O>2/ /2K%/28

:%&T2/&5:?&8O>2/:1OMM&8

:?&8O>2/:82T21T

:?&8O>2/:1OMP52T2

/%:?O:1ommand

M!

/%:?O:ccess

/%:?O:1omplete

.i/ure +$3$#$!0 6SS4nitiated 4nternal Handover 9:ecution

The :%&T2/&5:?&8O>2/:/2K%/28 messae contains a reason for the reCuired handover and the currentlyvalid 1odec 5ist (0!! !upported). %t shall also contain an o%P Transport 5ayer ddress and 8P Port- if the 0!!

3GPP

)% 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

41/302

reCuires an %P:based taret ser Plane. The 1odec 5ist (0!! supported) contains the "ey reCuirements from the 0!!-li"e taret 1odec Type(s)- taret 1odec 1onfiuration(s) and taret :interface Type(s) (T8M and2/:/2K%/28 messae the 0!! starts a timer JT*=J

(3GPP T! 9E.++E H=I) and it e'pects an answer from the servin M!1 within that timer period. %f JT*=J

(3GPP T! 9E.++E H=I) e'pires before the M!1 has answered- then the 0!! inores any subseCuent (late) answer fromthe servin M!1 after e'piry of timer JT*=J (3GPP T! 9E.++E H=I). The 0!! will not send any new :%&T2/&5:?&8O>2/:/2K%/28 messae before timer JT*=J (3GPP T! 9E.++E H=I) has e'pired or before the %nternal?andover Preparation is terminated by other reasons.

Ahen the servin M!1 receives the :%&T2/&5:?&8O>2/:/2K%/28 messae it shall start timer T,+= (seesubclause F.3). The servin M!1 shall not send any answer to the 0!! after timer T,+= has e'pired. 0oth timers(JT*=J 3GPP T! 9E.++E H=I and T,+=) shall be confiured (by OM) to minimise the li"elihood that the answer fromservin M!1 to 0!! crosses with a new or repeated :%&T2/&5:?&8O>2/:/2K%/28 messae from the 0!!to the servin M!1- i.e. the timer T,+= shall always e'pire before JT*=J (3GPP T! 9E.++E H=I) e'pires.

%f the servin M!1 is able to fulfil the reCuired J0!! %nternal ?andover with M!1 !upportJ- then it shall enerate andsend an :%&T2/&5:?&8O>2/:1OMM&8 messae to the 0!! and stop timer T,+=. This answer shall containthe e'act new :%nterface ser Plane parameters- e.. 1odec Type- 1odec 1onfiuration- :%nterface Type- either T8M

1ircuit %dentity 1ode or %P Transport 5ayer ddress and 8P Port (see 3GPP T! 9E.++E H=I). Ahile T*= is still runninthe 0!! can either accept or reject the :%&T2/&5:?&8O>2/:1OMM&8.

Ahen the 0!! receives the :%&T2/&5:?&8O>2/:1OMM&8 messae it ta"es the necessary action to allowthe M! to access the radio resource of the new cell in 0!!- this is detailed in 3GPP T! 9E.+=E H@I and in3GPP T! 9=.++E H9I. The switchin of the radio resource throuh the necessary terrestrial resources is detailed in3GPP T! 99.+,E H*EI and 3GPP T! 9E.++E H=I. On receipt of the :%&T2/&5:?&8O>2/:1OMM&8 messaethe 0!! will send e.. the radio interface messae /%:?&8O>2/:1OMM&8- containin a ?andover /eference

number previously allocated to the M!. The M! will then access the new radio resource usin the ?andover /eferencenumber contained in the /%:?&8O>2/:112!! messae. The number will be chec"ed by 0!! to ensure it is ase'pected and the correct M! has been captured.

s 0!! and M! proceed with the handover the 0!! may send an :?&8O>2/:82T21T messae to the servin

M!1 to enable fast ser Plane switchin on the 1ore &etwor" side. s soon as the M! and 0!! have completed thehandover the 0!! send an :?&8O>2/:1OMP52T2 messae to servin M!1. 0oth 0!! and servin M!1 willthen release the no loner needed 0!! and 1ore &etwor" resources.

%f the servin M!1 is unable to support the reCuired %nternal ?andover due to whatever reason then it shall send an :%&T2/&5:?&8O>2/:/2K%/28:/2N21T messae to the 0!! (if T,+= has not e'pired already). The servin

M!1 shall not send an :%&T2/&5:?&8O>2/:/2K%/28:/2N21T messae after an :%&T2/&5:?&8O>2/:1OMM&8 has been sent to the 0!!.

%f a failure occurs durin the handover attempt and the 0!! sends an :?&8O>2/:7%5/2 messae- then theservin M!1 shall terminate the handover and shall revert bac" to usin the resources used before the handover attemptwas made.

The servin M!1 shall supervise the J0!! %nternal ?andover with M!1 !upportJ procedure after sendin the :

%&T2/&5:?&8O>2/:1OMM&8 usin the same timer (T,+*) as used for %ntra:M!1 handover- seesubclauses F.3 and ,,.3.

%n all cases the e'istin connection to the M! shall not be cleared- e'cept in the case of e'piry of the timer T,+* beforereceipt of :?&8O>2/:1OMP52T2.

Ahilst the M! is not in communication with the 1ore &etwor" (i.e. in the time span between sendin of :%&T2/&5:?&8O>2/:1OMM&8 and the reception of :?&8O>2/:1OMP52T2 or an :?&8O>2/7%5/2) the servin M!1 shall Cueue all appropriate messaes towards the M!. ll these messaes shall be

delivered to the M! once the communication is resumed.

7or the case of subseCuent %ntra:0!! handover with support from M!1:0 or 3G;M!1:0 the followin appliesD

fter successful completion of the %ntra:0!! handover- if M!1:0

8/9/2019 23009-b20

42/302

5ist (M!1 preferred) from the o%P:!upported 1odecs 5ist (nchor) received from M!1:andover #th MS* Su%%ort

8urin a call the M!1 may reCuest to modify the :%nterface ser Plane- for e'ample to chane the 1odec Type or

1odec 1onfiuration on the :%nterface to optimise end:to:end speech Cuality by avoidin transcodin.

The servin M!1 may initiate a J0!! %nternal ?andover with M!1 !upportJ by sendin an :%&T2/&5:?&8O>2/:2&K%/ messae to the 0!! containin- within the !peech 1odec (M!1 1hosen) %2- the servinM!1#s preferred speech 1odec Type and 1odec 1onfiuration and :%nterface Type.

%f accepted by the 0!!- the 0!! responds with an :%&T2/&5:?&8O>2/:/2K%/28 messae- as described insubclause @.3.*- with reason J/esponse to an %&T2/&5 ?&8O>2/ 2&K%/J. Then the J0!! %nternal ?andover

with M!1 !upportJ may start.

%f the 0!! does not accept the :%&T2/&5:?&8O>2/:2&K%/ messae- then it returns an :?&8O>2/:7%5/2 messae to the servin M!1.

Genera$ de"r#%t#on o4 the %ro"edure 4or #nter - MS*handover

The followin clauses describe two options for the 0asic and !ubseCuent ?andover procedures. The first- as describedin subclauses B., and B.3 respectively- provides for a circuit connection between M!1: and M!1:0. The second- asdescribed in subclauses B.* and B.9 respectively- provides for a 0asic and !ubseCuent ?andover without the provisionof a circuit connection between M!1: and M!1:0.

%n all the above mentioned clauses- the followin principles applyD

a) durin the handover resource allocation- e'cept for the messaes e'plicitly indicated in b and c below- only the

handover related messaes that are part of the applicable 0!!P subset : as defined in 3GPP T! 9F.++E HBI :shall be transferred on the 2:interface

b) the trace related messaes that are part of the applicable 0!!P subset : as defined in 3GPP T! 9F.++E HBI : canbe sent by the M!1: on the 2:interface after successful handover resource allocation. %nsubclauses B., and B.*- it is however allowed at basic handover initiation on the 2:%nterface to transfer one tracerelated messae that is part of the applicable 0!!P subset : as defined in 3GPP T! 9F.++E HBI : toether withthe applicable handover related messae. The applicable handover related messae shall always appear as the

first messae

c) durin the handover resource allocation for subseCuent inter:M!1 handover accordin to subclauses B.3 and B.9-it is allowed to transfer either 8TP or /&P 8irect Transfer messaes on the 2:%nterface between M!1:and M!1:0. /&P 8irect Transfer messaes shall be used for this purpose if and only if the basic handover

procedure was an inter M!1 !/&! relocation

d) durin the handover e'ecution- ie while the M! is not in communication with the networ"- the M!1: shallCueue all outoin 0!!P or /&P messaes until the communication with the M! is resumed

e) durin the e'ecution of a basic inter:M!1 handover to M!1:0 or a subseCuent inter:M!1 handover to a third

M!1:0L- only the handover related messaes and the :1lear:/eCuest messae that are part of the applicable0!!P subset : as defined in 3GPP T! 9F.++E HBI may be sent by the taret M!1 on the 2:interface

f) durin a subseCuent inter:M!1 handover bac" to M!1: or to a third M!1:0L- M!1:0 may initiate either an%u:/elease:/eCuest procedure or an :1lear:/eCuest procedure on the 2:interface. n %u:/elease:/eCuestprocedure shall be initiated only if the basic handover procedure was an inter:M!1 !/&! relocation

) finally- durin supervision- ie while the M! is not in the area of M!1: after a successful %nter:M!1 handover-

the subset of 0!!P procedures and their related messaes : as defined in 3GPP T! 9F.++E HBI : shall apply onthe 2:%nterface. s the only e'ception to this rule- in case of a subseCuent inter:M!1 !/&! relocation bac" to3G;M!1: or to a third 3G;M!1:0L- durin the relocation resource allocation- the relocation and trace related

3GPP

)# 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

43/302

messaes that are part of the applicable /&P subset : as defined in 3GPP T! *F.,+E H,=I : shall betransferred on the 2:interface (see subclause E.3- a and b).

%f a subseCuent inter:M!1 handover2/ reCuest to M!1:0

includin a complete :?O:/2K2!T messae.

&OT2D M!1: shall not send further MP:P/2P/2:?&8O>2/ reCuests while a MP:P/2P/2:?&8O>2/ response is pendin or before any timeouts.

3GPP

)3 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

44/302

The MP:P/2P/2:?&8O>2/ reCuest shall carry in the :?O:/2K2!T all information needed by M!1:0 forallocatin a radio channel- see 3GPP T! 9E.++E H=I. 7or compatibility reasons- the MP:P/2P/2:?&8O>2/reCuest will also identify the cell to which the call is to be handed over. 7or speech calls- M!1: shall also include the%u !upported 1odecs 5ist to be used by M!1:0 for subseCuent intra:M!1:0 intersystem handover to MT! and intra:M!1:0 !/&! relocation.

%f M!1: supports interface over %P- then for speech calls M!1: may include the o%P:!upported 1odecs 5ist(nchor) in the MP:P/2P/2:?&8O>2/ reCuest. %f handover to an over %P capable 0!!:0 is performed-M!1:0 shall include a 1odec 5ist (M!1 preferred) in the :?O:/2K2!T messae to 0!!:0. M!1:0 may select thecodecs for the 1odec 5ist (M!1 preferred) from the channel type information and the o%P:!upported 1odecs 5ist(nchor)- if this list was provided by M!1: in the MP:P/2P/2:?&8O>2/ reCuest. 7or a detailed description

of the handlin of these codec lists by M!1: and M!1:0 see 3GPP T! *3.,=3 H*=I. %f the o%P:!upported 1odecs5ist was not provided or M!1:0 does not support the selection of codecs from the o%P:!upported 1odecs 5ist(nchor)- then M!1:0 shall create the 1odec 5ist (M!1 preferred) usin the channel type information received fromM!1: in the :?O:/2K2!T messae included in the MP:P/2P/2:?&8O>2/ reCuest.

%f M!1: supports handover to a 1!G cell- the taret cell belons to the reistered P5M& or an eCuivalent P5M&- andthe ?5/ or the 1!! provided 1!G subscription data- M!1: shall include the 1!G subscription data for the reisteredP5M& and- if available- for the eCuivalent P5M&s in the MP:P/2P/2:?&8O>2/ reCuest.

M!1:0 will return the MP:P/2P/2:?&8O>2/ response after havin retrieved a ?andover &umber from itsassociated >5/ (e'chane of the messaes MP:allocate:handover:number reCuest and MP:send:handover:report

reCuest). The ?andover &umber shall be used for routin the connection of the call from M!1: to M!1:0. %f a trafficchannel is available in M!1:0 the MP:P/2P/2:?&8O>2/ response- sent to M!1: will contain the complete:?O:/2K2!T:1$&OA528G2 messae received from 0!!:0- containin the radio resources definition to besent by 0!!: to the M! and possible e'tra 0!!MP information- amended by M!1:0 due to the possibleinterwor"in between the 0!!MP protocol carried on the 2:interface and the 0!!MP protocol used on the:interface. %f the traffic channel allocation is Cueued by 0!!:0- the :K2%&G:%&8%1T%O& may optionaly be

sent bac" to M!1:. The further traffic channel allocation result (:?O:/2K2!T:1$ or :?O:7%5/2) will betransferred to M!1: usin the MP:P/O12!!:112!!:!%G&55%&G reCuest. %f the traffic channel allocation isnot possible- the MP:P/2P/2:?&8O>2/ response containin an :?O:7%5/2 will be sent to M!1:.M!1:0 will do the same if a fault is detected on the identity of the cell where the call has to be handed over. M!1:0simply reports the events related to the dialoue. %t is up to M!1: to decide the action to perform if it receives

neative responses or the operation fails due to the e'piry of the MP:P/2P/2:?&8O>2/ timer.

%f interface over %P is supported- then for speech calls via an over %P capable 0!!:0 the selection of the speechcodec shall be as described in 3GPP T! 9E.++E H=I- and if no transcoder is inserted in the 0!!:0 then M!1:0 shallinsert a transcoder.

%f M!1: provided an o%P:!upported 1odecs 5ist (nchor) in the MP:P/2P/2:?&8O>2/ reCuest andM!1:0 selected the codecs for the 1odec 5ist (M!1 preferred) from the o%P:!upported 1odecs 5ist (nchor)-M!1:0 may send the o%P:!elected 1odec (Taret) and o%P:vailable 1odecs 5ist (MP) to M!1: in the MP:P/2P/2:?&8O>2/ response.

%f 0!!:0 does not support interface over %P or M!1: did not include the o%P:!upported 1odecs 5ist (nchor) in

the MP:P/2P/2 ?&8O>2/ reCuest- then M!1:0 shall not include the o%P:!elected 1odec (Taret) and

o%P:vailable 1odecs 5ist (MP) in the MP:P/2P/2:?&8O>2/ response. /eception of o%P:!elected 1odec(Taret) and o%P vailable 1odecs 5ist (MP) from M!1:0 with the MP:P/2P/2:?&8O>2/ responseindicates to M!1: that the taret access supports interface over %P.

%f an error related to the T1P dialoue or to the MP:P/2P/2:?&8O>2/ reCuest is returned from M!1:0- this

will be indicated to M!1: and M!1: will terminate the handover attempt. M!1: may retry the handover attemptusin the cell identity list- if provided- or may reject the handover attempt towards 0!!:. The e'istin connection tothe M! shall not be cleared.

3GPP

)) 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

45/302

Ahen the :?O:/2K2!T:1$&OA528G2 has been received- M!1: shall establish a circuit between M!1:and M!1:0 by sinallin procedures supported by the networ". %n fiure ,* this is illustrated by the messaes %M(%nitial ddress Messae) and 1M (ddress 1omplete Messae) of !inallin !ystem no B. M!1:0 awaits thecapturin of the M! (subclause @.,) on the radio path when the 1M is sent and M!1: initiates the handovere'ecution when 1M is received (illustrated by the :?O:1OMM&8 and described in the subclause @.,.

%f the 0!!: was connected via an interface over %P and no transcodin performed in the 0!! then M!1: shallremove the transcoder between the M!1 and the other party.

M!1:0 transfers to M!1: the ac"nowledement received from the correct M! (:?O:82T21T2/:!1122828 messae shall be sent.

%n the case of basic handover- M!1: shall specify to M!1:0 that no ?andover &umber is reCuired in the MP:P/2P/2:?&8O>2/ reCuest (see 3GPP T! *F.++* H,*I). s for the basic handover usin a circuit connection- the:?O:/2K2!T is transmitted at the same time. ny subseCuent ?andover &umber allocation procedure will not beinvo"ed until the completion of the basic handover procedure (see clauseD !ubseCuent 1hannel ssinment usin acircuit connection). M!1:0 shall then perform the radio resources allocation as described in subclause B.,. The

MP:P/2P/2:?&8O>2/ response shall be returned to M!1: includin either the response of the radioresources allocation reCuest received from 0!!:0 (:?O:/2K2!T:1$&OA528G2

8/9/2019 23009-b20

46/302

The relevant case for the basic handover without circuit connection is shown in fiure ,3. s can be seen the majordifferences to the eCuivalent fiure ,* is the omission of any circuit establishment messain and the omission ofhandover number allocation sinallin.

M!

8/9/2019 23009-b20

47/302

.3.1 e"r#%t#on o4 u'eAuent handover %ro"edure #) MS*-7 to MS*-&

The procedure for successful handover from M!1:0 bac" to M!1: is shown in fiure ,9.

M!

8/9/2019 23009-b20

48/302

.3.2 e"r#%t#on o4 the u'eAuent handover %ro"edure ##) MS*-7 toMS*-78

The procedure for successful handover from M!1:0 to M!1:0# is shown in fiure ,=.

The procedure consists of two partsD

: a subseCuent handover from M!1:0 bac" to M!1: as described in subclause B.3., (the same procedures applyif M!1: is replaced by 3G;M!1:) and

: a basic handover from M!1: to M!1:0# as described in subclause B.,.

M!1:0 sends the MP:P/2P/2:!0!2K2&T:?&8O>2/ reCuest to M!1: indicatin a new M!1 number(which is the identity of M!1:0#)- indicatin also the taret cell identity and includin a complete :?O:/2K2!T-M!1: then starts a basic handover procedure towards M!1:0#.

%f M!1: supports interface over %P- then for speech calls M!1: may include the o%P:!upported 1odecs 5ist

(nchor) in the MP:P/2P/2:?&8O>2/ reCuest towards M!1:0#. 7or a detailed description of the handlin ofthis codec list by M!1: and M!1:0# see 3GPP T! *3.,=3 H*=I.

Ahen M!1: receives the 1M from M!1:0#- M!1: informs M!1:0 that M!1:0# has successfully allocated theradio resources on 0!!:0# side by sendin the MP:P/2P/2:!0!2K2&T:?&8O>2/ response containin the

complete :?O:/2K2!T:1$&OA528G2 received from 0!!:0# and possible e'tra 0!!MP information-amended by M!1: due to the possible interwor"in between the 0!!MP protocol carried on the 2:interface betweenM!1: and M!1:0# and the 0!!MP protocol carried on the 2:interface between M!1: and M!1:0. &ow M!1:0can start the procedure on the radio path.

7or M!1: the handover is completed when it has received the MP:!2&8:2&8:!%G&5 /2K2!T from M!1:0#

containin the :?O:1OMP52T2 received from the 0!!:0#. The circuit between M!1: and M!1:0 is released.M!1: also sends the MP:!2&8:2&8:!%G&5 response to M!1:0 in order to terminate the oriinal MP dialouebetween M!1: and M!1:0. M!1:0 releases the radio resources when it receives this messae.

%f the traffic channel allocation is Cueued by the 0!!:0#- the :K2%&G:%&8%1T%O& may optionally be sent bac"

to M!1:0. %f no radio channel can be allocated by M!1:0# or no circuit between M!1: and M!1:0# can beestablished or a fault is detected on the taret cell identity or the taret cell identity in the :?O:/2K2!T is notconsistent with the taret M!1 number- M!1: informs M!1:0 by usin the :?O:7%5/2 messae included in theMP:P/2P/2:!0!2K2&T:?&8O>2/ response. M!1:0 shall maintain the e'istin connection with the M!.

Ahen the subseCuent handover is completed- M!1:0# is considered as M!1:0. ny further inter:M!1 handover is

handled as described above for a subseCuent handover.

3GPP

)- 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

49/302

M!1:0

:?O:/2K%/28

>5/:0

:?O:1OMM&8

MP:Prep:!ub:?andover reC.

:?O:82T21T

:?O:1OMP52T2

M!1:

M!5/:0L

MP:Prepare:?andover reC.

MP:Prepare:?andover resp.

MP:llocate:?andover:&umber reC.

MP:!end:?andover:/eport reC.

%M

MP:!end:?andover:/ep. resp. (,)

MP:Prep:!ub:?o resp.

MP:Process:ccess:!inallin reC.

MP:!end:2nd:!inal reC.

1M

nswer

/elease

MP:!end:2nd:!inal resp.


/elease

(end of call)

:15/:1M8

8/9/2019 23009-b20

50/302

..1 e"r#%t#on o4 the u'eAuent handover %ro"edure #thout "#r"u#t"onne"t#on #) MS*-7 to MS*-&

The procedure for successful handover from M!1:0 bac" to M!1: without circuit connection is shown in fiure ,@.The only difference with the fiure ,9- is that no circuit release is needed between M!1: and M!1:0.

M!

8/9/2019 23009-b20

51/302

M!1:0

:?O:/2K%/28

>5/:0

:?O:1OMM&8


:?O:82T21T

:?O:1OMP52T2

M!1:

M!5/:0L






(end of lin")



:15/:1M8

8/9/2019 23009-b20

52/302

c) durin the handover resource allocation for subseCuent inter:M!1 inter:system handover accordin tosubclauses E.,.3 and E.,.9- it is allowed to transfer either 8TP or /&P 8irect Transfer messaes on the 2:%nterface between 3G;M!1: and 3G;M!1:0. /&P 8irect Transfer messaes shall be used for this purposeif and only if the basic handover procedure was an inter M!1 !/&! relocation

d) durin the handover e'ecution- i.e. while the 2

8/9/2019 23009-b20

53/302

3G M!1: M!1:0

MP:Prep:?andover reC. MP:llocate:?andover:&umber reC.

:?O:/2K2!T

%u:/25O1T%O&:/2K%/28

0!!:0

8/9/2019 23009-b20

54/302

M!1:0 will return the MP:P/2P/2:?&8O>2/ response after havin retrieved a ?andover &umber from itsassociated >5/ (e'chane of the messaes MP:allocate:handover:number reCuest and MP:send:handover:reportreCuest). The ?andover &umber shall be used for routin the connection of the call from 3G;M!1: to M!1:0. %f atraffic channel is available in M!1:0 the MP:P/2P/2:?&8O>2/ response- sent to 3G;M!1: will contain thecomplete :?O:/2K2!T:1$&OA528G2 messae received from 0!!:0- containin the radio resources

definition to be sent by /&!: to the 22/ timer.

%f interface over %P is supported- then for speech calls via an over %P capable 0!!:0 the selection of the speechcodec shall be as described in 3GPP T! 9E.++E H=I- and if no transcoder is inserted in the 0!!:0 then M!1:0 shall

insert a transcoder.

%f 3G;M!1: provided an o%P:!upported 1odecs 5ist (nchor) in the MP:P/2P/2:?&8O>2/ reCuest andM!1:0 selected the codecs for the 1odec 5ist (M!1 preferred) from the o%P:!upported 1odecs 5ist (nchor)-M!1:0 may send the o%P:!elected 1odec (Taret) and o%P:vailable 1odecs 5ist (MP) to 3G;M!1: in the

MP:P/2P/2:?&8O>2/ response.

%f 0!!:0 does not support interface over %P or 3G;M!1: did not include the o%P:!upported 1odecs 5ist (nchor)in the MP:P/2P/2 ?&8O>2/ reCuest- then M!1:0 shall not include the o%P:!elected 1odec (Taret) ando%P:vailable 1odecs 5ist (MP) in the MP:P/2P/2:?&8O>2/ response. /eception of the o%P:!elected1odec (Taret) and o%P vailable 1odecs 5ist (MP) from M!1:0 with the MP:P/2P/2:?&8O>2/ response

indicates to 3G;M!1: that the taret access supports interface over %P.

%f an error related to the T1P dialoue or to the MP:P/2P/2:?&8O>2/ reCuest is returned from M!1:0- thiswill be indicated to 3G;M!1: and 3G;M!1: will terminate the handover attempt. 3G;M!1: rejects the handoverattempt towards /&!:. The e'istin connection to the 2

8/9/2019 23009-b20

55/302

3G;M!1: may terminate the procedure at any time by sendin an appropriate MP messae to M!1:0. %festablishment of the circuit between 3G;M!1: and M!1:0 has been initiated- the circuit must also be cleared.

The MT! to G!M handover will be aborted by 3G;M!1: if it detects clearin or interruption of the radio pathbefore the call has been established on M!1:0.

B.1.1.2 ?#th u$t#%$e "#r"u#t "onne"t#on (%t#ona$ 4un"t#ona$#t@)

%f 3G;M!1: supports the optional supplementary service Multicall (!ee 3GPP T! *3.,3= H,BI)- 3G;M!1: shallhave the followin functionality additionally to the description in subclause E.,.,.,.

pon receipt of the %:/25O1T%O&:/2K%/28 from /&!: 3G;M!1: shall select one bearer to be handed overif the 2 is enaed with multiple bearers. fter that- the 3G;M!1: enerates an :?O:/2K2!T messae for theselected bearer and sends it to M!1:0 over MP:P/2P/2:?&8O>2/ reCuest.

Ahen MP:P/2P/2:?&8O>2/ response includin an :?O:/2K2!T:1$ is received from M!1:0-

3G;M!1: sends %:/25O1T%O&:1OMM&8- which indicates the bearers not to be handed over as bearers to bereleased- to /&!:.

fter 3G;M!1: receives MP:!2&8:2&8:!%G&5 reCuest from M!1:0- 3G;M!1: shall release calls via M!1:

0- which has been carried by the bearers not to be handed over- and then 3G;M!1: sends %:/252!2:1OMM&8 to /&!:.

B.1.2 7a#" UMTS to GSM >andover %ro"edure not reAu#r#n theeta'$#hent o4 a "#r"u#t "onne"t#on 'eteen 3G=MS*-& and MS*-7

The basic MT! to G!M handover procedures to be used when no circuit connection is reCuired by 3G;M!1: aresimilar to those described in clause E.,., for circuit switched calls. The main differences to the procedures described inclause E.,., relate to the establishment of circuits between the networ" entities and the ?andover &umber allocation.

%n the case of basic MT! to G!M handover- 3G;M!1: shall specify to M!1:0 that no ?andover &umber is

reCuired in the MP:P/2P/2:?&8O>2/ reCuest (see 3GPP T! *F.++* H,*I). s for the basic MT! to G!M

handover usin a circuit connection- the :?O:/2K2!T is transmitted at the same time. ny subseCuent ?andover&umber allocation procedure will not be invo"ed until the completion of the basic MT! to G!M handover procedure(see clauseD !ubseCuent 1hannel ssinment usin a circuit connection). M!1:0 shall then perform the radio resourcesallocation as described in subclause E.,.,. The MP:P/2P/2:?&8O>2/ response shall be returned to3G;M!1: includin either the response of the radio resources allocation reCuest received from 0!!:0 (:?O:

/2K2!T:1$&OA528G2

8/9/2019 23009-b20

56/302

3G;M!1: M!1:0

MP:Prep:?andover reC.

:?O:/2K2!T

%u:/25O1T%O&:

/2K%/28

0!!:0

8/9/2019 23009-b20

57/302

B.1.3.1 e"r#%t#on o4 u'eAuent UMTS to GSM handover %ro"edure #) 3G=MS*-7to MS*-&

The procedure for successful MT! to G!M handover from M!1:0 bac" to 3G;M!1: is shown in fiure *+.

2

8/9/2019 23009-b20

58/302

pon receipt of the %:/25O1T%O&:/2K%/28 from /&!: which indicates the taret is 0!!- 3G;M!1:0 shallselect one bearer to be handed over if the 2 is enaed with multiple bearers. fter that- the 3G;M!1:0 enerates an:?O:/2K2!T messae for the selected bearer and sends it to 3G;M!1: over MP:P/2P/2:!0!2K2&T:?&8O>2/ reCuest with indication of /0 %8 of the selected bearer.

Ahen MP:P/2P/2:!0!2K2&T:?&8O>2/ response includin an :?O:/2K2!T:1$ is received from

the 3G;M!1:- 3G;M!1:0 sends %:/25O1T%O&:1OMM&8- which indicates the bearers not to be handed overas bearers to be released- to /&!:.

fter 3G;M!1: receives :?O:1OMP52T2 messae from 0!!:0- 3G;M!1: shall release calls via 0!!:0- which

has been carried by the bearers not to be handed over- and then 3G;M!1: sends MP:!2&8:2&8:!%G&5 responseto 3G;M!1:0.

B.1.3.2 e"r#%t#on o4 u'eAuent UMTS to GSM handover %ro"edure ##)3G=MS*-7 to MS*-78

The procedure for successful MT! to G!M handover from 3G;M!1:0 to M!1:0# is shown in fiure *,.

The procedure consists of two partsD

: a subseCuent MT! to G!M handover from 3G;M!1:0 bac" to 3G;M!1: as described in subclause E.,.3.,(the same procedures apply if 3G;M!1: is replaced by M!1:) and

: a basic handover from 3G;M!1: to M!1:0# as described in subclause B.,.

B.1.3.2.1 ?#th one "#r"u#t "onne"t#on

3G;M!1:0 sends the MP:P/2P/2:!0!2K2&T:?&8O>2/ reCuest to 3G;M!1: indicatin a new M!1number (which is the identity of M!1:0#)- indicatin also the taret cell identity and includin a complete:?O:/2K2!T- 3G;M!1: then starts a basic handover procedure towards M!1:0#.

%f 3G;M!1: supports interface over %P- then for speech calls 3G;M!1: may include the o%P:!upported 1odecs5ist (nchor) in the MP:P/2P/2:?&8O>2/ reCuest towards M!1:0#. 7or a detailed description of the handlinof this codec list by 3G;M!1: and M!1:0# see 3GPP T! *3.,=3 H*=I.

Ahen 3G;M!1: receives the 1M from M!1:0#- 3G;M!1: informs 3G;M!1:0 that M!1:0# has successfully

allocated the radio resources on 0!!:0# side by sendin the MP:P/2P/2:!0!2K2&T:?&8O>2/ responsecontainin the complete :?O:/2K2!T:1$&OA528G2 received from 0!!:0# and possible e'tra 0!!MPinformation- amended by 3G;M!1: due to the possible interwor"in between the 0!!MP protocol carried on the2:interface between 3G;M!1: and M!1:0# and the 0!!MP protocol carried on the 2:interface between3G;M!1: and 3G;M!1:0. &ow 3G;M!1:0 can start the procedure on the radio path.

7or 3G;M!1: the MT! to G!M handover is completed when it has received the MP:!2&8:2&8:!%G&5/2K2!T from M!1:0# containin the :?O:1OMP52T2 received from the 0!!:0#. The circuit between3G;M!1: and 3G;M!1:0 is released. 3G;M!1: also sends the MP:!2&8:2&8:!%G&5 response to3G;M!1:0 in order to terminate the oriinal MP dialoue between 3G;M!1: and 3G;M!1:0. 3G;M!1:0

releases the radio resources when it receives this messae.

%f the traffic channel allocation is Cueued by the 0!!:0#- the :K2%&G:%&8%1T%O& may optionally be sent bac"to 3G;M!1:0. %f no radio channel can be allocated by M!1:0# or no circuit between 3G;M!1: and M!1:0# can beestablished or a fault is detected on the taret cell identity or the taret cell identity in the :?O:/2K2!T is notconsistent with the taret M!1 number- 3G;M!1: informs 3G;M!1:0 by usin the :?O:7%5/2 messaeincluded in the MP:P/2P/2:!0!2K2&T:?&8O>2/ response. 3G;M!1:0 shall maintain the e'istin

connection with the 2

8/9/2019 23009-b20

59/302

pon receipt of the %:/25O1T%O&:/2K%/28 from /&!:0 3G;M!1:0 shall select one bearer to be handed overif the 2 is enaed with multiple bearers. fter that- the 3G;M!1:0 enerates an :?O:/2K2!T messae for theselected bearer and sends it to 3G;M!1: over MP:P/2P/2:!0!2K2&T:?&8O>2/ reCuest withindication of /0 %8 of the selected bearer.

pon receipt of the MP:P/2P/2:!0!2K2&T:?&8O>2/ reCuest from 3G;M!1:0- 3G;M!1: starts a

basic handover procedure towards M!1:0#.

Ahen 3G;M!1: receives the 1M from M!1:0#- 3G;M!1: informs 3G;M!1:0 that M!1:0# has successfullyallocated the radio resources on 0!!:0# side by sendin the MP:P/2P/2:!0!2K2&T:?&8O>2/ response

containin the complete :?O:/2K2!T:1$ received from 0!!:0# and possible e'tra 0!!P information-amended by 3G;M!1: due to the possible interwor"in between the 0!!MP protocol carried on the 2:interfacebetween 3G;M!1: and M!1:0# and the 0!!MP protocol carried on the 2:interface between 3G;M!1: and3G;M!1:0.

Ahen MP:P/2P/2:!0!2K2&T:?&8O>2/ response includin an :?O:/2K2!T:1$ is received from

3G;M!1:- 3G;M!1:0 sends %:/25O1T%O&:1OMM&8- which indicates the bearers not to be handed over asbearers to be released- to /&!:.

fter 3G;M!1: receives MP:!2&8:2&8:!%G&5 reCuest from M!1:0#- 3G;M!1: shall release calls via M!1:

0#- which has been carried by the bearers not to be handed over- and then 3G;M!1: sends MP:!2&8:2&8:!%G&5 response to 3G;M!1:0.

3GPP

*& 3GPP TS #3$%%& '!!$#$% (#%!#!#"elease !!

8/9/2019 23009-b20

60/302

%u:/25O1T%O&:

/2K%/28

>5/:0

%u:/25O1T%O&:1M8


:?O:82T21T

:?O:1OMP52T2

2

8/9/2019 23009-b20

61/302

B.1..1 e"r#%t#on o4 u'eAuent UMTS to GSM handover %ro"edure #) 3G=MS*-7 toMS*-&

The procedure for successful MT! to G!M handover from 3G;M!1:0 bac" to M!1: without circuit connection isshown in fiure **. The only difference with the fiure *+- is that no circuit release is needed between M!1: and3G;M!1:0.

M!1: 3G M!1:0

MP:Prep:!ub:?andover reC.%u:/25O1T%O&:

/2K%/28

/&!:

8/9/2019 23009-b20

62/302

%u:/25O1T%O&:/2K%/28

>5/:0

%u:/25O1T%O&:1M8


:?O:82T21T

:?O:1OMP52T2

M!1:0L >5/:0L






(end of lin")



3G;M!1:

2

8/9/2019 23009-b20

63/302

since no reCuest for 5ocation /eportin can be received from M!1:. %n that case- the 5ocation /eportin1ontrol procedure shall be initiated by 3G;M!1:0 or 3G:M!1:0L after the /elocation /esource llocationprocedure has been e'ecuted successfully. The chane of !ervice rea shall be reported to M!1: within an :?&8O>2/:P2/7O/M28 messae

e) durin the handover e'ecution- i.e. while the 2

8/9/2019 23009-b20

64/302

2

8/9/2019 23009-b20

65/302

transcoder. %f the %u !upported 1odecs 5ist was not received or 3G;M!1:0 does not support the selection of codecbased on the %u:!upported 1odecs 5ist- 3G;M!1:0 shall select the appropriate default speech codec.

7or handover to T/& %u mode- 3G;M!1:0 shall also enerate a &! !ynch %ndicator for the %u:/25O1T%O&:/2K2!T messae. %f the %u !upported 1odecs 5ist was received by 3G;M!1:0 and 3G;M!1:0 supports the

selection of codec based on the %u:!upported 1odecs 5ist- then the %u !elected codec shall be indicated in the MP:

P/2P/2:?&8O>2/ response- sent from 3G;M!1:0 to M!1:.

%f over %P is supported by M!1:- then for speech calls M!1: may include the o%P:!upported 1odecs 5ist(nchor) in the MP:P/2P/2:?&8O>2/ reCuest to be used by 3G;M!1:0 for subseCuent intra:M!1:0

intersystem handover to over %P capable 0!1. 7or a detailed description of the handlin of this codec list by M!1:and 3G;M!1:0 see 3GPP T! *3.,=3 H*=I.

%f radio resources are available in /&!:0 the MP:P/2P/2:?&8O>2/ response will contain the complete :?O:/2K2!T:1$ messae enerated from the %u:/25O1T%O&:/2K2!T:1$ received from /&!:0- containinthe radio resources definition to be sent by 0!!: to the 22/ response containin an :?O:7%5/2 will be sent to M!1:. 3G;M!1:0 will dothe same if a fault is detected on the identity of the cell where the call has to be handed over. 3G;M!1:0 simply reportsthe events related to the dialoue. %t is up to M!1: to decide the action to perform if it receives neative responses orthe operation fails due to the e'piry of the MP:P/2P/2:?&8O>2/ timer.

%f an error related to the T1P dialoue or to the MP:P/2P/2:?&8O>2/ reCuest is returned from 3G;M!1:0-

this will be indicated to M!1: and M!1: will terminate the handover attempt. M!1: shall reject the handoverattempt towards 0!!:. The e'istin connection to the 2

8/9/2019 23009-b20

66/302

B.2.2 7a#" GSM to UMTS >andover %ro"edure not reAu#r#n theeta'$#hent o4 a "#r"u#t "onne"t#on 'eteen MS*-& and 3G=MS*-7

The basic G!M to MT! handover procedures to be used when no circuit connection is reCuired by M!1: are similarto those described in subclause E.*., for circuit switched calls. The main differences to the procedures described insubclause E.*., relate to the establishment of circuits between the networ" entities and the ?andover &umber allocation.

%n the case of basic G!M to MT! handover- M!1: shall specify to 3G;M!1:0 that no ?andover &umber isreCuired in the MP:P/2P/2:?&8O>2/ reCuest (see 3GPP T! *F.++* H,*I). s for the basic G!M to MT!handover usin a circuit connection- the :?O:/2K2!T is transmitted at the same time. ny subseCuent ?andover&umber allocation procedure will not be invo"ed until the completion of the basic G!M to MT! handover procedure(see clauseD !ubseCuent 1hannel ssinment usin a circuit connection). 3G;M!1:0 shall then perform the radio

resources allocation as described in subclause E.*.,. The MP:P/2P/2:?&8O>2/ response shall be returned toM!1: includin either the translated response of the radio resources allocation reCuest received from /&!:0 (:?O:/2K2!T:1$

8/9/2019 23009-b20

67/302

B.2.3.1 e"r#%t#on o4 u'eAuent GSM to UMTS handover %ro"edure #) MS*-7 to3G=MS*-&

The procedure for successful G!M to MT! handover from M!1:0 bac" to 3G;M!1: is shown in fiure *@.

22/ reCuest. %f the 2 fails the 1!G membership chec" andthe taret cell is a 1!G cell- M!1:0 shall send an :?&8O>2/:/2K%/28:/2N21T to 0!!:.

M!1:0 sends the MP:P/2P/2:!0!2K2&T:?&8O&

23009-b20

Documents