23707-d00

7/26/2019 23707-d00

1/41

3GPP TR 23.707 V13.0.0 (2014-12)Technical Report

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

Architecture Enhancements for Dedicated Core Netor!s;Sta"e #

$%elease &3'

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 Orani!ational Partners and shall not be implemented.

This "eport is provided for future development wor# within 3GPPonly. The Orani!ational Partners accept no liability for any use of this $pecification.

$pecifications and "eports for implementation of the 3GPPTMsystem should be obtained via the 3GPP Orani!ational Partners% Publications Offices.

7/26/2019 23707-d00

2/413GPP

&eywords3GPP, Architecture, Dedicated Core Netor!

3GPP

Postal address

3GPP support office address

"#0 Route de$ %ucio&e$ - 'ohia Atio&i$Va&*oe - +RANC

Te&. 33 4 /2 /4 42 00 +a 33 4 /3 "# 47 1"

'nternet

htt.3.or

Copyright Notification

o part may be reproduced ecept as authori!ed by written permission.The copyriht and the foreoin restriction etend to reproduction in all media.

* +,-/ 3GPP Orani!ational Partners (0"'1/ 0T'$/ 22$0/ T$'/ TT0/ TT2).

0ll rihts reserved.

4MT$5 is a Trade Mar# of T$' reistered for the benefit of its members

3GPP5 is a Trade Mar# of T$' reistered for the benefit of its Members and of the 3GPP Orani!ational Partners

6T5 is a Trade Mar# of T$' reistered for the benefit of its Members and of the 3GPP Orani!ational PartnersG$M7 and the G$M loo are reistered and owned by the G$M 0ssociation

3GPP T% #3()*) +&3(*(* $#*&,-'#%elease &3

7/26/2019 23707-d00

3/41

Cotet$

8oreword..........................................................................................................................................................

- $cope......................................................................................................................................................

+ "eferences..............................................................................................................................................

3 9efinitions and abbreviations.................................................................................................................3.- 9efinitions...........................................................................................................................................................3.+ 0bbreviations.......................................................................................................................................................

0ssumptions and 0rchitecture "e:uirements..........................................................................................- General..................................................................................................................................................................+ 0ssumptions.........................................................................................................................................................3 0rchitecture "e:uirements..................................................................................................................................

; lementary 8unctions.............................................................................................................................

;.- 8unctions 2ommon to both P$ and 2$ 9omain.................................................................................................;.-.- 'dentification of association with dedicated 2 nodes..................................................................................

;.-.-., 9escription...............................................................................................................................................;.-.-.- $olutions...................................................................................................................................................;.-.-.-.- ew $ubscription 'nformation...........................................................................................................;.-.-.+ valuations and 2onclusions...................................................................................................................;.-.+ 2onsiderations for "oamin..........................................................................................................................;.-.3 2onsiderations for etwor# $harin..............................................................................................................

;.+ P$ 9omain $pecific 8unctions............................................................................................................................;.+.- 0ssinment of dedicated MM

7/26/2019 23707-d00

4/41

;.+..+.- $olution -> 2ombination of $-

7/26/2019 23707-d00

5/41

+oreord

This Technical "eport has been produced by the 3rdGeneration Partnership Project (3GPP).

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 follows>

Bersion .y.!

where>

the first diit>

- presented to T$G for informationC

+ presented to T$G for approvalC

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

D 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 T% #3()*) +&3(*(* $#*&,-'.%elease &3

7/26/2019 23707-d00

6/41

1 'coe

0n operator may choose to deploy one (or more) dedicated core networ#s within a P6M with each core networ#dedicated for specific type(s) of subscriber. The present document studies and evaluates architectural enhancements

re:uired to support dedicated core networ#s. The specific dedicated core networ# that serves a 4 is selected based onsubscription information and operator confiuration/ without re:uirin the 4s to be modified.

The technical report covers both assinment of dedicated core networ# nodes and maintainin the association durinmobility. "oamin and networ# sharin aspects of dedicated core networ#/ and impacts on procedures such as 2$81/$"B22 and r$"B22 will be studied.

9edicated core networ#s may be in the P$ domain or 2$ domain or both.

2 Reerece$

The followin documents contain provisions which/ throuh reference in this tet/ constitute provisions of the present

document.

= "eferences are either specific (identified by date of publication/ edition number/ version number/ etc.) ornon=specific.

= 8or a specific reference/ subse:uent revisions do not apply.

= 8or 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.

E-F 3GPP T" +-.,;> HBocabulary for 3GPP $pecificationsH.

E+F Boid.

E3F 3GPP T" +- -+ (B3.-.,)> Hample +/ usin fied tetH.

EF 3GPP T$ +3.,-> HGeneral Pac#et "adio $ervice (GP"$) enhancements for volved 4niversalTerrestrial "adio 0ccess etwor# (=4T"0) accessH.

E;F 3GPP T$ +3.,A,> HGeneral Pac#et "adio $ervice (GP"$)C $ervice descriptionC $tae +H.

EAF 3GPP T$ +3.+I+> H2ircuit $witched (2$) fallbac# in volved Pac#et $ystem (P$)C $tae +H.

EIF 3GPP T$ +3.+3A> H'ntra=domain connection of "adio 0ccess etwor# ("0) nodes to multiple2ore etwor# (2) nodesH.

EJF 3GPP T$ +3.+;-> Hetwor# $harinC 0rchitecture and functional descriptionH.

EF 3GPP T$ +.3,-> Hon=0ccess=$tratum (0$) protocol for volved Pac#et $ystem (P$)C$tae 3H.

3 Deiitio$ ad a**reiatio$

3.1 Deiitio$

8or the purposes of the present document/ the terms and definitions iven in T" +-.,; E-F apply.

3GPP

3GPP T% #3()*) +&3(*(* $#*&,-'/%elease &3

7/26/2019 23707-d00

7/41

3.2 A**reiatio$

8or the purposes of the present document/ the abbreviations iven in T" +-.,; E-F apply.

4 A$$u5tio$ ad Architecture Re6uire5et$

4.1 Geera&

ditor%s note> This clause contains eneral definition if needed.

4.2 A$$u5tio$

= 0 dedicated core networ# is assumed to serve only specific subscriber(s). 0 dedicated core networ# comprises

one or more MM

7/26/2019 23707-d00

8/41

# &e5etar +uctio$

ditor%s note> This clause contains the detail of each solution alternative.

#.1 +uctio$ Co55o to *oth P' ad C' Do5aiditor%s note> This clause contains the common functions between P$ and 2$ domains.

#.1.1 8detiicatio o a$$ociatio ith dedicated CN ode$

#.1.1.0 De$critio

$ome identification is needed/ which enables the servin networ# to determine which of its 2s shall serve the 4. 't isassumed that the identification is a parameter of the subscriber data.

#.1.1.1 'o&utio$

#.1.1.1.1 Ne 'u*$critio 8or5atio

0 new optional subscription information parameter (H4 4sae TypeH) stored in the ?$$ is used by the servinnetwor# to select which of its 2s shall serve the 4. The operator confiures which of his 2s serves which 44sae Type(s). Multiple 4 4sae Types can be served by the same 2. The ?$$ provides the H4 4sae TypeH valuein the subscription information of the 4 to the MM This clause contains the specific function of P$ domain.

3GPP

3GPP T% #3()*) +&3(*(* $#*&,-'0%elease &3

7/26/2019 23707-d00

9/41

#.2.1 A$$i5et o dedicated 99'G'N

#.2.1.1 A$$i5et duri Attach ad TA:RA:

#.2.1.1.1 -:TRAN Attach ad TA:

#.2.1.1.1.1 'ceario De$critio

8or initial MM

= 0ttach with 'M$'.

= 0ttach and T04 with G4T' from old MM

7/26/2019 23707-d00

10/41

information from the old MM. The MM may provide G4MM' ta#en from the previously receivedadditional G4T'/ if the MMG' of the taret core networ# matches the MMG' part of the additional G4T' inattach messae.

+. The eode1 =4T"0 0ttach or T04 procedure is performed as specified in T$ +3.,- EF.

3GPP

3GPP T% #3()*) +&3(*(* $#*&,-'&*%elease &3

7/26/2019 23707-d00

11/41

3. 'f the 4 identifies itself with G4T' and the MM has chaned/ the identity response messae (for 0ttach) or2ontet "esponse (for T04) contains the 4 4sae Type information/ if available.

'f dedicated core networ#s are supported and the new MM supports 4s of the 4 4sae Type value containedin the 'dentification "esponse

7/26/2019 23707-d00

12/41

1i"ure .(#(&(&(&(#(#-&2 %e-routin" 7efore NAS security setup

1i"ure .(#(&(&(&(#(#-#2 8nitial assi"nment of DEC9% at E-5T%AN Attach:TA5

. 'f the 4 identifies itself with G4T' and the MM has chaned/ the 'dentification "esponse messae (for0ttach) or 2ontet "esponse (for T04) contains the 4 4sae Type information/ if available.

'f dedicated core networ#s are supported and the new MM supports 4s of the 4 4sae Type value containedin the 'dentification "esponse

7/26/2019 23707-d00

13/41

'f dedicated core networ#s are supported and no 4 4sae Type value contained in the 'dentification"esponse 9etails are for further study. The 0$ re=route procedure specified for solution H"edirection afterupdate location procedureH may apply (the redirection without G4T' case).

9ependin on operator policies/ a decision to re=route or not to re=route may also be ta#en based on availableinformation after step +/ or A.

0t inter=P6M contet transfer specific handlin applies/ which may involve selection of 4 4sae Type based on thevisited networ# policy/ roamin areements and based on different subscription parameters includin the ?P6M 44sae Type.

#.2.1.1.1.2.3 'o&utio 3 ;u&&-NR8;;u&&-99G8; *a$ed redirectio duri Attach ad TA:

The overall sinallin flow of attach or T04 for Hnull=MMG'H based redirection is illustrated in 8iure ;.+.-.-.-.+.3=-.Only the steps that are needed to eplain the specifics of the overall approach are shown.

@hen multiple dedicated 2s are deployed/ the initial allocation of a 4 by the eode1 when comin into an area thatsupports 92O" may be to an arbitrary

7/26/2019 23707-d00

14/41

1i"ure .(#(&(&(&(#(3-&2 9verall si"nallin" flo of attach:TA5 for null-EG8 7ased redirection

-. The 4 initiates the normal =4T"0 initial 0ttach or T04 procedure.

+. 'f the eode1 has no route info for the 4 provided G4MM'/ the initial 0ttach "e:uest messae is routed to arandomly selected or a default first MM.

3. The first MM tries to et the 4%s contet from old MM

7/26/2019 23707-d00

15/41

OT> The flow shows the se:uence for 0ttach. 8or T04 the ?$$ interaction ta#es place after $-- procedure.

I. ?$$ cancels the old 2 node.

J. The ?$$ ac#nowledes the 4pdate 6ocation messae by sendin an 4pdate 6ocation 0c# ('M$'/ $ubscriptiondata) messae to the servin MM.

. 'f the procedure started with 0ttach "e:uest/ the first MM needs to establish new P9 connection(s). The firstMM selects the P=G@ and also the $=G@/ preferably accordin to the re:uired dedicated 2 so that there is no

P=G@ chane needed when in later steps transferrin that 4 to an MM of the appropriate dedicated 2. Thefirst MM establishes the P9 connection(s). 'f the procedure started with T04 "e:uest/ the first MM updatesthe P9 connection(s)/ if those can be maintained.

-,. 'f the first MM needs to redirect the 4/ the first MM allocates a new G4T' includin a null=MMG'

indicatin the taret dedicated 2 and its own MM 2ode and includes that G4T' in the 0ttach

7/26/2019 23707-d00

16/41

1i"ure .(#(&(&(&(#(3-#2 Allocation of Null

7/26/2019 23707-d00

17/41

The handover can then continue normally/ old MM selects a new MM for the 4 but the 4 stays in the current celland is served by the same eode1 as before. 8iure ;.+.-.-.-.+. =- shows the sinallin procedure.

'n order to minimise the number of procedures rejected by the eode1/ the MM shall pause non=handover related $-=interface procedures while a handover to dedicated MM is onoin (in this case/ collision of functionality betweenMM and the $G@ is the same as for reular $- handover today).

9urin the handover/ servin (old) MM sends a 8orward "elocation "e:uest to the dedicated (new) MM and thisincludes the 4 MM 2ontet. The MM 4 2ontet includes 'M$'/ M 'dentity/ 4 $ecurity 2ontet/ 4 etwor#

2apability/ 0M1"/ $elected 2 operator '9/ 0P "estriction/ $ervin G@ address and T'9 for control sinallin/and P$ 1earer 2ontet(s). 4 $ecurity 2ontet includes the P$ security contet which contains the used 0$cipherin #eys. $o/ the new MM can use this information to perform G4T' "eallocation 2ommand with cipherintowards the 4.

@hile the MM triered handover to dedicated MM is onoin/ 0$ messaes from 4 are not handled. $ervin

(old) MM inores all 4 0$ messaes after handover is triered and dedicated (new) MM start handle 4 0$messaes after G4T' reallocation is complete.

'f the first MM cannot allocate a PG@ from the dedicated 2/ the dedicated MM initiates deactivation ofcorrespondin P9 connection with Hreactivation re:uestedH or 9etach with Hre=attach re:uiredH after the handover

procedure is complete.

3GPP

3GPP T% #3()*) +&3(*(* $#*&,-'&)%elease &3

7/26/2019 23707-d00

18/41

1i"ure .(#(&(&(&(#(,-&2 E tri""ered S& handover after successful Attach or TA5 completion

-a. 4 performs normal 0ttach or T04 procedure. 9efault P9 connection is established.

1ased on subscription information received from ?$$ the servin MM determines that a dedicated (new)MM need be selected.

OT -> This functionality is common to all solutions and needs be concluded separately.

-b. @hen 4 is moved to a dedicated MM/ the servin MM does not release $- connection after 0ttach completeor T04 2omplete is received from 4. 0fter the T04 "e:uest is received/ the MM re=establishes radio and $-bearers for all active P$ bearer contets.

+. The servin MM sends ?andover Trier to the eode1.

OT +> This is a new $- procedure.

3. The eode1 initiates a handover to itself into the current servin cell and sends ?andover "e:uired (with a new

cause value ?O triered by 2).

MM triered handover preparation and eecution is done without 4 involvement/ 4 stays in the currentcell and is served by the same eode1 actin towards P2 as both taret and source.

3GPP

3GPP T% #3()*) +&3(*(* $#*&,-'&0%elease &3

7/26/2019 23707-d00

19/41

Throuhout the procedure user plane is not impacted and stays active/ the ="01s are not modified and theaddress(es) of user plane tunnel(s) between eode1 and $=G@ don%t chane.

. The servin MM selects a dedicated MM and sends a 8orward "elocation "e:uest (with a new cause value ?O triered by 2 and Heode1 4 $-0P '9H) to the dedicated MM.

The dedicated MM verifies whether the $ervin G@ can continue to serve the 4. 'f not/ it selects a new$ervin G@. 8or simplicity the session creation towards a new $ervin G@ is not shown in this fiure and therest of procedure show the case when $ervin G@ does not chane.

;. The dedicated MM sends ?andover "e:uest to the eode1 (with a new cause value ?O triered by 2 andHeode1 4 $-0P '9H). The eode1 4 $- 0P '9 is the one used on $- interface between eode1 and$ervin MMC eode1 uses this '9 to identify the eistin 4 contet. o sinallin towards 4 follows as the4 is served by the same eode1 as before.

8rom this step onwards eode1 maintains two MM $-0P '9(s) for the same eode1 $- 0P '9/ one for theservin (old) MM and one for the dedicated (new) MM assined for the 4. The eode1 maintains twoMM $- 0P '9(s) until servin (old) MM releases the $- connection at step -3. @ith the eistin handoverprocedures/ eode1 needs to maintain only one MM $- 0P '9 durin this time.

8rom this step onwards the eode1 sends 0$ messaes comin from the 4 to the dedicated MM via thenewly established $- connection.

'n order to minimise the number of procedures rejected by the eode1/ the old MM shall pause non=handoverrelated $-=interface procedures while a handover to the dedicated MM is onoin.

A. The eode1 sends ?andover 0c#nowlede to dedicated MM.

I. The dedicated MM performs G4T' re=allocation/ after this point 0$ messaes from 4 are handled bydedicated MM.

J. The dedicated MM sends 8orward "elocation "esponse to the servin (old) MM and continues with step -,.

. The servin (old) MM sends ?andover command to the eode1. o sinallin towards 4 follows as the 4

is served by the same eode1 as before.

. These procedures that are part of a normal handover are not performed. $ince there is no chane of eode1/eistin ""2 connection and 0$ security contet will be re=used/ thus no sinallin towards the 4 is needed tore=establish ""2 connection.

-,. The dedicated MM updates location to ?$$.

--. The ?$$ sends 2ancel 6ocation to the servin (old) MM.

-+. The dedicated MM adopts the bearer contets received from the servin (old) MM and sends Modify 1earer"e:uest to $ervin G@ for each P9 connection to update new MM address and T'9 for control planesinallin.

-3. The servin (old) MM releases old $- connection.

-. 'f the first MM cannot allocate the re:uired P9 connection for the dedicated 2 (0ttach case) or the eistinP9 connection(s) cannot be maintained (T04 case)/ the dedicated MM initiates either the re=establishment of

the particular P9 connection with Hreactivation re:uestedH (in case not all P9s need to be re=established) or9etach with Hre=attach re:uiredH (in case all P9s need to be re=established) after the handover procedurecompletes.

#.2.1.1.1.2.# 'o&utio 4* 99 triered re-directio to dedicated 99 ater Attach

This procedure is shown below.

3GPP

3GPP T% #3()*) +&3(*(* $#*&,-'&4%elease &3

7/26/2019 23707-d00

20/41

1i"ure .(#(&(&(&(#(.-&2 E tri""ered re-direction to dedicated E after Attach

,. This step shows completion of attach procedure as per T$ +3.,- EF/ clause ;.3.+.-. MM re=direction mayimmediately follow the 0ttach procedure or may happen at later period after attach. The re=direction decisionmay be ta#en durin the 0ttach procedure by servin MM based on H4 4sae TypeH received from ?$$ and

the subse:uent steps are eecuted after the completion of the 0ttach procedure. 'n some cases re=direction may

be ta#en after attach for eample ONM triers servin MM to off=loadin the 4 in connected mode towardsa dedicated 2ore etwor# (i.e. a dedicated MM that is more appropriate for the 4 type).

-. $ource MM ($=MM) sends a 8orward "elocation "e:uest messae to taret MM (T=MM) over the $-,interface. The messae indicates the reason of re=direction e.. usin new 'ndication 8las inside forward

relocation messae or by other means. 4%s contet stored in $=MM (includin security #eys) is transferred toT=MM with this messae. $=MM also sends Global eode1 '9 and eode1 $-0P '9 to identify 4 contetin the eode1 to T=MM.

+. T=MM decides to accept the re:uest and assins a G4T' that will be used by 4 after completion of the

procedure. T=MM initiates the sendin of 0$ messae towards the 4 usin a new E$-=0PF MM"6O20T'O "L4$T messae. T=MM also enerate E0$F G4T' "066O20T'O "L4$Tmessae which is included in E$-=0PF MM "6O20T'O "L4$T. T=MM inores the transparentcontainer sent by $=MM.

3. 4pon reception of the E$-=0PF MM "6O20T'O "L4$T messae the eode1 retrieves the 4 contet

and forwards the 0$ messae to 4.

. 4 ta#es note of the newly assined G4T' and responds with E0$F G4T' "066O20T'O 2OMP6Tmessae.

;. eode1 receives the uplin# 0$ messae and forwards it to T=MM usin a new E$-=0PF MM"6O20T'O "$PO$ messae.

8rom this step onwards the eode1 sends 0$ messaes comin from the 4 to the dedicated MM via thenewly established $- connection.

'n order to minimise the number of procedures rejected by the eode1/ the $=MM pauses non=handover related$-=interface procedures while a handover to the dedicated MM is onoin.

3GPP

3GPP T% #3()*) +&3(*(* $#*&,-'#*%elease &3

7/26/2019 23707-d00

21/41

A. 4pon reception of the E0$F G4T' "066O20T'O 2OMP6T messae the T=MM sends 8orward"elocation "esponse to $=MM indicatin that 4 contet has been successfully transferred to T=MM.

I. $=MM sends 8orwards "elocation 2omplete 0c# to T=MM.

J. $=MM initiates 4 contet release procedure towards e=1. ote that steps Ja=Jb for 4 2ontet release maynot be needed if it can be assumed that step ; (MM "elocation otify) effectively cancels the $-=MMassociation with the $=MM.

=-,. T=MM creates association with the $=G@ for this 4.

--=-. T=MM informs the ?$$ that it will serve as the new contact point for this 4. $=MM may delete the 4contet at this point.

#.2.1.1.2 :TRAN GPR' Attach ad RA:


8or initial $G$ assinment durin GP"$ 0ttach the followin scenarios are covered>

= 'u GP"$ 0ttach with 'M$'.

= 'u GP"$ 0ttach and "04 with P=TM$' from old MM 9etailed differences from the =4T"0 attach procedure are for further study.

#.2.1.1.2.2.3 'o&utio 3 ;u&&-NR8;;u&&-99G8;*a$ed redirectio duri Attach

The approach is comparable on a hih level to that described under ;.+.-.-.-.+.3 H$olution 3> Hnull="'H

7/26/2019 23707-d00

22/41

determined 2 accepts the 4 and services it. ach $G$ is confiured with a uni:ue non=broadcast "0' so that thenew $G$ can resolve the old $G$ based on it.

'f the $G$ handlin the 0ttach receives subse:uently a re:uest to activate a P9 connection and this $G$ cannotactivate a P9 connection from the determined dedicated 2 the $G$ initiates 9etach with Hreattach re:uestedH/which causes another 0ttach "e:uest that the "2 routes directly to the determined dedicated 2 based on the ull=

"'."edirection durin "04 wor#s as redirect durin 0ttach with followin differences. 0fter acceptin the "04 "e:uest

with parameters as described above for the 0ttach the $G$ verifies whether the 4%s P9 connections can bemaintained. 'f not/ the $G$ initiates 9etach with Hreattach re:uestedH/ which causes another 0ttach "e:uest that the"2 routes directly to the determined dedicated 2 based on the ull="'.

'f the P9 connection can be maintained/ the "2 routes the 4%s net "04 "e:uest to an $G$ from the determineddedicated 2 based on the ull="'. The new $G$ from the determined 2 accepts the 4 and services it.

#.2.1.1.3 GRAN GPR' Attach ad RA:


8or initial $G$ assinment durin GP"$ 0ttach the followin scenarios are covered>

= Gb GP"$ 0ttach with 'M$'.

= Gb GP"$ 0ttach and "04 with P=TM$' from old MM 9etailed differences from the =4T"0 attach procedure are for further study.

#.2.1.1.3.2.3 'o&utio 3 ;u&&-NR8;;u&&-99G8; *a$ed redirectio duri Attach

The solution is the same as under ;.+.-.-.+.+.3 $olution 3> Hnull="'H

= 'nter MM

7/26/2019 23707-d00

23/41

#.2.1.2.2 'o&utio$

#.2.1.2.2.1 'o&utio 1 ad 'o&utio 2 Redirectio ater :date %ocatio Procedure ad Re-routi *eore NA' $ecurit $etu

9urin handover/ if the source MM @hile it is stronly recommended for an operator deployin 92O" toupdate their $8 procedure to enable idle=mode T04 This case happens when load (re=)balancin is needed amon the MMs

7/26/2019 23707-d00

24/41

Ta7le .(#(&(3(&-&2 Comparison of Solutions

3GPP

3GPP T% #3()*) +&3(*(* $#*&,-'#,%elease &3

7/26/2019 23707-d00

25/41

Evaluationcriteria

Solution&2%edirection after5pdate 6ocation

Procedure

Solution # 2 %e-routin" 7efore NAS

security setup

Solution 32 null-N%8:null-EG87ased redirection

Solution(,2 ETri""ered =andover

1. Node$85acted

eNode=RNC,'G'N99

eNode=RNC,'G'N99, ?@c&au$e 7.1.4.1 toic&ude 99G8NR8ad reroute to $eciic99'G'N oo&A&$o i5act G*rocedure.

NN'+ rocedure

eed$ to *e 5odiiedto had&e u&&-99G8u&&-NR8 (oeor each air o $ourcead taret CN oo&$).

Add$ a e CN

triered

7/26/2019 23707-d00

26/41

ne node than othersolutions(6ess si"nallin" thanSolution 3 or ,(

compared toSolution & and #?unless the 5E is !eptin default CN untilne@t re"ular TA5( 8nthat case the defaultCN needs to deploy

the capacity for thededicated CN 5Es inthe 7order TA:%A(

%euires additionalradio si"nallin" tosetup D%Bs( oresi"nallin" comparedto Solution & and #(

3GPP

3GPP T% #3()*) +&3(*(* $#*&,-'#/%elease &3

7/26/2019 23707-d00

27/41

'2.

7/26/2019 23707-d00

28/41

Ne load$re-'7alancin"procedure neededfor ,G(

OT> The above table does not capture $8 confiuration supported in "0 to maintain 4 in dedicated 2networ#. This confiuration is common to all solutions.

1ased on the above table/ $olution=- is selected since it provides efficient procedure to redirect a 4 to dedicatednetwor#.

#.2.1.3.2 Coc&u$io

H$olution -> "edirection after 4pdate 6ocation ProcedureH is selected for 0ssinment of dedicated MM

= T04

7/26/2019 23707-d00

29/41

0 hih level flow showin 2 node selection based on "'

7/26/2019 23707-d00

30/41

1i"ure .(#(#(&(#(.-&2 TA5:%A5 procedure ith 5E 5sa"e Type associated ith EG8:N%8 values

-=+. T04

3GPP

3GPP T% #3()*) +&3(*(* $#*&,-'3*%elease &3

7/26/2019 23707-d00

31/41

HThe RRC parameter "old GUMMEI" takes its value from the identifier that is signalled as the old GUTI according tothe rules above. or a combined MME!G# the e#ode$ is configured to route the MME%code&s' of this combined

node to the same combined node. This e#ode$ is also configured to route MME%code&s' of GUTIs that are generated

b( the UE)s mapping of the *% TMIs allocated b( the combined node. uch an e#ode$ configuration ma( also be used

for separate nodes to avoid changing nodes in the pool caused b( inter R+T mobilit(.H

0 92O" with combined $G$

7/26/2019 23707-d00

32/41

8ollowin functionalities are re:uired to be supported>

= The 9$ should be confiured to handle :ueries from non=92O" supportin MM

7/26/2019 23707-d00

33/41

#.2.3.2.2 'o&utio$

#.2.3.2.2.1 DN' =a$ed PGB 'e&ectio

The 9$ based solution should meet the followin re:uirements>

= nable the MM

7/26/2019 23707-d00

34/41

1i"ure .(#(,(#(&-&2 =SS 8nitiated CN Node Chan"e

-. The ?$$ sends an 'nsert $ubscriber 9ata "e:uest ('M$'/ $ubscription 9ata) messae to the MM. The$ubscription 9ata includes 4 4sae Type information.

+. The MM updates the stored $ubscription 9ata and ac#nowledes the 'nsert $ubscriber 9ata "e:uest messae

by returnin an 'nsert $ubscriber 9ata 0nswer ('M$') messae to the ?$$.

3. The MM determines that 4 4sae Type has chaned for the 4. The MM determines if PG@ needs tochane.

$teps a or b are eecuted if the 4 is in 2M=2O2T9 mode.

a. 'f the PG@ needs to be relocated/ the MM performs detach with re=attach re:uired for the 4. @hen the 4performs re=attach the procedure for $oluiton- in assinment of MM

7/26/2019 23707-d00

35/41

OT> The MM should not release all $- connections which are selected to be released immediately whenredirection is initiated. The MM may wait until the $- "elease is performed due to inactivity. @hen allthe 4s are to be redirected completely the MM can enforce an $- "elease for all remainin 4s thatwere not offloaded by normal T04 procedures or by $- releases caused by inactivity.

$teps c or c are eecuted if the 4 is in 2M='96 mode.

c. 'f the PG@ needs to be chaned/ either (i) the MM will pae the 4 and when the 4 performs a $ervice"e:uest procedure/ the MM sends a $ervice "eject with MM cause H'mplicitly 9etachedH as specified in

T$ +.3,- EF/ or (ii) the 4 performs T04 and the MM will reject T04 with MM 2ause H'mplicitly9etachedH. 'n both cases/ when the 4 reattaches/ the 4 ets redirected to the appropriate core networ#.

d. 'f the PG@ does not need to be chaned/ the MM waits for the 4 to perform (i) $ervice "e:uest procedure.0t the end of the procedure the MM initiates the $- "elease procedure with release cause Hload balancin T04re:uiredH as in $tep b or (ii) normal or periodic T04

7/26/2019 23707-d00

36/41

3. @hen the 4 is in 2M='96 mode and unreachable e.. due to P$M/ etc/ the MM

7/26/2019 23707-d00

37/41

-. 'n case the procedure is used to transfer the 4 to another dedicated 2 due chane of subscriber data/ the ?$$sends an 'nsert $ubscriber 9ata "e:uest ('M$'/ $ubscription 9ata) messae to the MM. The $ubscriber 9ataindicate a need for chanin the 2.

+. The MM updates its stored $ubscriber 9ata and ac#nowledes the 'nsert $ubscriber 9ata "e:uest messae byreturnin an 'nsert $ubscriber 9ata 0c# messae.

3. 'f the MM decides to transfer the 4 immediately to another 2/ the MM paes the 4 if it is in idle mode.0lternatively the MM waits until the 4 becomes active.

. ither triered by the pain or by uplin# data the 4 initiates 0$ connection establishment by sendin a$ervice "e:uest. 0lternatively the 4 initiates connection establishment by sendin a T04 "e:uest.

;a. This step applies when a 0$ connection already eists at the point in time when the MM receives new

$ubscription 9ata for the 4 or when a 0$ connection is established with the $ervice "e:uest procedure. TheMM determines the new 2 and reallocates the G4T' with a new G4T' that contains the null=MMG' of thenew 2 and its own MM2. The MM also allocates a non=broadcast T0' to the 4.

;b. This step applies when the 0$ connection is established with a T04 "e:uest. The MM determines the new2 and returns a T04 0ccept with a new G4T' containin the null=MMG' of the new 2 and its own MM2

and a non=broadcast T0'.

A. 'f the PG@ needs to be chaned/ i.e. when the P9 connection cannot be maintained under the new dedicated2/ the MM performs networ# initiated detach procedure with Hre=attach re:uiredH.

I. The MM re:uests release of the $-

7/26/2019 23707-d00

38/41

#.3.1 A$$i5et o dedicated 9'C

#.3.1.1 A$$i5et duri Attach

#.3.1.1.1 -:TRAN Attach


ditor%s note> $hould cover the followin scenarios> (i) 0ttach with 'M$'

7/26/2019 23707-d00

39/41

#.3.2.1.2 'o&utio$

#.3.2.1.3 a&uatio$ ad Coc&u$io$

#.3.2.2 CN ode chae * hadoer

#.3.2.2.1 'ceario De$critio

ditor%s note> $hould cover the followin scenarios> handover with from an old M$2 supportin 92O" to a newM$2 supportin 92O".

#.3.2.2.2 'o&utio$

#.3.2.2.3 a&uatio$ ad Coc&u$io$

#.3.3

7/26/2019 23707-d00

40/41

8or the 2$ domain/ the solution similar to the selected solution for P$ domain will be captured directly in normativespecifications.

Overview of the feature for supportin dedicated core=networ#s will be captured in T$ +3.,- EF for =4T"0 andT$ +3.,A, E;F for 4T"0 with the details captured in T$ +3.+3A EIF.

3GPP

3GPP T% #3()*) +&3(*(* $#*&,-',*%elease &3

7/26/2019 23707-d00

41/41

Ae AChae hi$tor

Chan"e history

Date TSG TSG Doc( C% %ev Cat Su7ject:Comment 9ld Ne

2014-12 'PF"" 'P-140"/" - - - 9CC ditoria& udate or re$etatio to T'G 'A or aroa& 0.4.0 1.0.0

2014-12 'PF"" - - - - 9CC :date to er$io 13.0.0 ater T'G 'A aroa& 1.0.0 &3(*(*

3GPP T% #3()*) +&3(*(* $#*&,-',&%elease &3

23707-d00

Documents