3rd Generation Partnership Project; V12.4.

0 (2014-03) Technical Specification Group Services and System Aspects; Technical Specification Network architecture ( elease !"#

3GPP TS 23.002

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

elease !"

"

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

$eywords
LTE, GSM, UMTS, network, architect re

3GPP Postal address

!-0"#21 So$hia %nti$o&i' (e)e* - !+%,(E

Office address
"-0 +o te )e' L cio&e' - So$hia %nti$o&i' Va&.onne - !+%,(E Te&./ 033 4 #2 #4 42 00 !a*/ 033 4 #3 "- 41 1"

%nternet
htt$/22www.33$$.or3

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

3GPP

elease !"

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

(ontent'
2ontents....................................................................................................................................................3 8oreword...................................................................................................................................................9 %ntroduction...............................................................................................................................................9 , !cope....................................................................................................................................................,+ * 0eferences............................................................................................................................................,+ 3 :efinitions and abbreviations...............................................................................................................,;
3., Public 6and Mobile &etwor" (P6M&)................................................................................................................,; 3.* 2ore &etwor" (2&) and /ccess &etwor" (/&)..................................................................................................,; 3.3 2ircuit !witched (2!) and Pac"et !witched (P!) :omains................................................................................,; 3.3., 2! :omain........................................................................................................................................................,; 3.3.* P! :omain........................................................................................................................................................,; 3.3a %P Multimedia subsystem (%M!)........................................................................................................................,< 3.- 6ocation re ister...................................................................................................................................................,< 3.= 2ell ,< 3.; 1ase !tation 2ontroller (1!2) area.....................................................................................................................,> 3.< 0adio &etwor" 2ontroller (0&2) area................................................................................................................,> 3.> 6ocation /rea (6/)..............................................................................................................................................,> 3.9 0outin /rea (0/)...............................................................................................................................................,> 3.9a Trac"in /rea (T/)............................................................................................................................................,> 3.,+ M!2 area............................................................................................................................................................,> 3.,, ?60 area............................................................................................................................................................,> 3.,* !G!& area..........................................................................................................................................................,> 3.,3 @ones for 0e ional !ubscription........................................................................................................................,> 3.,- !ervice area........................................................................................................................................................,9 3.,= Group call area...................................................................................................................................................,9 3.,=a MM3 /rea........................................................................................................................................................,9 3.,; PoolAarea............................................................................................................................................................,9 3.,< !ervin GB !ervice /rea..................................................................................................................................,9

- The basic entities of the mobile system................................................................................................,9

-., The 2ore &etwor" (2&) entities..........................................................................................................................*+ -.,., 3ntities common to the P! and 2! domains.....................................................................................................*+ -.,.* 3ntities of the 2! domain.................................................................................................................................*-.,.3 3ntities of the GP0! P! domain.......................................................................................................................*; -.,.- 3ntities of the 3P2 P! :omain.........................................................................................................................*> -.,.= 1order Gateway (1G)C......................................................................................................................................3* -.* The /ccess &etwor" (/&) entities......................................................................................................................3* -.*., The 1ase !tation !ystem (1!!)........................................................................................................................3* -.*.* The 0adio &etwor" !ystem (0&!)...................................................................................................................33 -.*.3 /ccess &etwor" elements for 3A4T0/&.........................................................................................................33 -.3 The Mobile !tation (M!).....................................................................................................................................33 -.- 4ser 3Duipment (43)...........................................................................................................................................33

-a The specific entities of the 3GPP system............................................................................................3-a., The Group 2all 0e ister (G20) entity...............................................................................................................3-a.* (void)..................................................................................................................................................................3= -a.3 The 6ocation !ervices (62!) entities................................................................................................................3= -a.3., 6ocation !ervices (62!) entities in 0/&.......................................................................................................3= -a.3.* Gateway Mobile 6ocation 2entre (GM62)....................................................................................................3; -a.3.3 6ocation Measurement 4nit (6M4)...............................................................................................................3; -a.3.- 3volved !ervin Mobile 6ocation 2entre (3A!M62)....................................................................................3; -a.- 2/M36 entities.................................................................................................................................................3< -a.-., G!M !ervice 2ontrol 8unction ( sm!28).....................................................................................................3<

3GPP

elease !"

'

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

-a.-.* G!M !ervice !witchin 8unction ( sm!!8)..................................................................................................3< -a.-.3 G!M !pecialised 0esource 8unction ( sm!08).............................................................................................3< -a.-.- GP0! !ervice !witchin 8unction ( prs!!8)................................................................................................3< -a.= 21!Aspecific entities..........................................................................................................................................3< -a.=., 2ell 1roadcast 2entre (212)..........................................................................................................................3< -a.; &umber Portability !pecific entities..................................................................................................................3< -a.;., %&Abased solutionE &umber Portability :atabase (&P:1).............................................................................3< -a.;.* !i nallin 0elayAbased solutionE Mobile &umber PortabilityF!i nallin 0elay function (M&PA!08).........3> -a.< %P Multimedia (%M) 2ore &etwor" (2&) !ubsystem entities............................................................................3> -a.<., 2all !ession 2ontrol 8unction (2!28)...........................................................................................................3> -a.<.* Media Gateway 2ontrol 8unction (MG28)....................................................................................................3> -a.<.3 %P Multimedia !ubsystem A Media Gateway 8unction (%M!AMGB).............................................................3> -a.<.- Multimedia 0esource 8unction 2ontroller (M082).......................................................................................39 -a.<.-a Multimedia 0esource 8unction Processor (M08P).......................................................................................39 -a.<.-b Media 0esource 1ro"er (M01)....................................................................................................................39 -a.<.= ?oid 39 -a.<.; 1rea"out Gateway 2ontrol 8unction (1G28).................................................................................................39 -a.<.< /pplication !erver (/!)..................................................................................................................................-+ -a.<.> %nterconnection 1order 2ontrol 8unction (%128)...........................................................................................-+ -a.<.9 Transition Gateway (TrGB)...........................................................................................................................-+ -a.<.,+ 6ocation 0etrieval 8unction (608)...............................................................................................................-+ -a.<.,, !ervice 2entrali(ation and 2ontinuity /pplication !erver (!22 /!)..........................................................-, -a.<.,,a 3mer ency /ccess Transfer 8unction (3/T8)...........................................................................................-, -a.<.,* /ccess Transfer 2ontrol 8unction (/T28)...................................................................................................-, -a.<.,3 /ccess Transfer Gateway (/TGB)..............................................................................................................-, -a.> !i nallin Gateway 8unction (!GB).................................................................................................................-, -a.9 Global Te't Telephony !pecific entities............................................................................................................-, -a.,+ !ecurity Gateway (!3G)..................................................................................................................................-, -a.,, /pplication 8unction (/8)...............................................................................................................................-* -a.,* ?oid..................................................................................................................................................................-* -a.,3 3GPPFB6/& %nterwor"in entities.................................................................................................................-* -a.,3., B6/& 43.....................................................................................................................................................-* -a.,3.* 3GPP /// Pro'y.........................................................................................................................................-* -a.,3.3 3GPP /// !erver.........................................................................................................................................-* -a.,3.- B6/& /ccess Gateway (B/G)..................................................................................................................-* -a.,3.= Pac"et :ata Gateway (P:G).........................................................................................................................-* -a.,3.; Gome / ent (G/).........................................................................................................................................-* -a.,- Multimedia 1roadcast Multicast !ervice (M1M!) specific entities................................................................-* -a.,-., General..........................................................................................................................................................-* -a.,-.* 1roadcastAMulticast !ervice 2entre (1MA!2)..............................................................................................-3 -a.,-.3 M1M!AGB...................................................................................................................................................-3 -a.,-.- MultiAcellFmulticast 2oordination 3ntity (M23)..........................................................................................-3 -a.,= ?oid..................................................................................................................................................................-3 -a.,; G4P !erver.......................................................................................................................................................-3 -a.,< Policy and 2har in 0ules 8unction (P208)..................................................................................................-3 -a.,> Policy and 2har in 3nforcement 8unction (P238).......................................................................................--a.,9 !upport of !hort Messa e !ervice over eneric 3GPP %nternet Protocol access (!M!%P) specific entities....--a.,9., General..........................................................................................................................................................--a.,9.* %PA!hortAMessa eAGateway (%PA!MAGB)....................................................................................................--a.*+ !ubscription Profile 0epository (!P0).............................................................................................................--a.*, !ervice :ata 8low 1ased 2redit 2ontrol 8unction..........................................................................................--a.** Offline 2har in !ystem (O82!)....................................................................................................................--a.*3 Online 2har in !ystem (O2!).......................................................................................................................--a.*- 1earer 1indin and 3vent 0eportin 8unction (11308)................................................................................--a.*= Gome (e)&ode1 entities...................................................................................................................................-= -a.*=., Gome &ode1 !ubsystem (G&!)...................................................................................................................-= -a.*=.* Gome e&ode1 !ubsystem (Ge&!)...............................................................................................................-= -a.*=.3 2!G 6ist !erver.............................................................................................................................................-= -a.*=.- 2!G !ubscriber !erver (2!!).......................................................................................................................-= -a.*; /pplication 8ront 3nds (/83).........................................................................................................................-; -a.*< 4ser :ata 0epository (4:0)...........................................................................................................................-;

3GPP

elease !"

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

-a.*> Traffic :etection 8unction (T:8)....................................................................................................................-; -a.*9 !pecific entities to facilitate communications with pac"et data networ"s and applications............................-; -a.*9., Machine Type 2ommunicationA%nterBor"in 8unction (MT2A%B8)..........................................................-; -a.*9.* Machine Type 2ommunicationA /uthentication. /uthori(ation and /ccountin (MT2A///)..................-; -a.3+ T2P Pro'y 8unction.........................................................................................................................................-< -a.3, !pecific entities for Pac"et !witched !treamin (P!!) !ervice......................................................................-< -a.3,., Pac"et !witched !treamin !ervice !erver (P!! !erver).............................................................................-<

= 2onfi uration of a Public 6and Mobile &etwor".................................................................................-<

=., 1asic confi uration..............................................................................................................................................-< =.* 2onfi uration of 62! entities..............................................................................................................................=, =.*., 2onfi uration of 62! entities for G30/&.......................................................................................................=, =.*.* 2onfi uration of 62! entities for 4T0/&.......................................................................................................=* =.*.3 2onfi uration of 62! entities for 3A4T0/&...................................................................................................=* =.3 2onfi uration of 2/M36 entities.......................................................................................................................=3 =.- 2onfi uration of 21! entities..............................................................................................................................==.= 2onfi uration of %M 2& !ubsystem entities........................................................................................................==.=., %M 2& !ubsystem functional entities...............................................................................................................==.=.* %M 2& !ubsystem !ervice layer.......................................................................................................................== =.=.3 !ervice 2entrali(ation and 2ontinuity..............................................................................................................=< =.=.- Beb0T2 access to %M!....................................................................................................................................=> =.; 2onfi uration of !i nallin Gateway 8unction...................................................................................................=9 =.< 2onfi uration of 3GPPFB6/& %nterwor"in ......................................................................................................=9 =.> 2onfi uration of Presence service.......................................................................................................................;+ =.9 2onfi uration of M1M! entities.........................................................................................................................;+ =.,+ 2onfi uration of !hort Messa e !ervice over eneric 3GPP %nternet Protocol access (!M!%P) entities.........;* =.,, 2onfi uration of Policy 2ontrol and 2har in entities.....................................................................................;* =.,* 2onfi uration of 2!81(2! 8allbac")................................................................................................................;= =.,3 2onfi uration of !in le 0adio ?oice 2all 2ontinuity (!0?22)......................................................................;; =.,3., 3A4T0/&F4T0/& (G!P/) to 4T0/& or G30/& !0?22 architecture..................................................;; =.,3.* 4T0/&FG30/& to 3A4T0/& or 4T0/& (G!P/) !0?22 architecture..................................................;< =.,- 2onfi uration of !ecurity...................................................................................................................................;9 =.,= 2onfi uration of 6awful %ntercept related entities.............................................................................................;9 =.,; 2onfi uration of 2har in related entities.........................................................................................................<+ =.,< 2onfi uration of Gome (e)&ode1 entities.........................................................................................................<, =.,<., 2onfi uration of the Gome &ode1 !ubsystem...............................................................................................<, =.,<.* 2onfi uration of the Gome e&ode1 !ubsystem.............................................................................................<* =.,> 2onfi uration for facilitatin communications with pac"et data networ"s and applications............................<3 =.,9 2onfi uration of Pac"et !witched !treamin (P!!) !ervice.............................................................................<3

; P6M& basic interfaces and reference points........................................................................................<;., %nterfaces between Mobile !tation and the 8i'ed %nfrastructure.........................................................................<= ;.,., %nterface between Mobile !tation and 1ase !tation !ystem (4mAinterface)....................................................<= ;.,.* %nterface between 4ser 3Duipment and 0adio &etwor" !ystem (4uAinterface)..............................................<= ;.,.3 %nterface between 4ser 3Duipment and 3volved 4T0/& (3A4T0/& 4uAinterface).....................................<= ;.* %nterface between the 2ore &etwor" and the /ccess &etwor"............................................................................<= ;.*., %nterfaces between the 2! domain and the /ccess &etwor"............................................................................<= ;.*.* %nterfaces between the P! domain and the /ccess &etwor"............................................................................<; ;.*.3 %nterfaces between the 3volved Pac"et 2ore and the /ccess &etwor"............................................................<; ;.3 %nterfaces internal to the /ccess &etwor"...........................................................................................................<; ;.3., %nterface between 1!2 and 1T! (/bisAinterface)............................................................................................<; ;.3.* %nterface between 0&2 and &ode 1 (%ubAinterface).........................................................................................<; ;.3.3 %nterface between two 0&2s (%urAinterface).....................................................................................................<< ;.3.- %nterface between two e&1s (H*Ainterface).....................................................................................................<< ;.3.= %nterface between G&1 and G&1AGB(%uhAinterface).....................................................................................<< ;.- %nterfaces internal to the 2ore &etwor"...............................................................................................................<< ;.-., %nterfaces internal to the 2! domain.................................................................................................................<< ;.-.* %nterfaces internal to the P! domain (GP0!)....................................................................................................<9 ;.-.3 %nterfaces used by 2! and P! domains.............................................................................................................>+ ;.-.- %nterfaces internal I related to the 3volved Pac"et 2ore.................................................................................>,

;a P6M& specific interfaces...................................................................................................................>;a., G20Aspecific interface.......................................................................................................................................>-

3GPP

elease !"

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

;a.,., %nterface between the M!2 and its associated G20 (%Ainterface)...................................................................>;a.* (void)..................................................................................................................................................................>;a.3 62!Aspecific interfaces......................................................................................................................................>;a.3., 62! interfaces usin M/P..............................................................................................................................>;a.3.* (void) >= ;a.3.3 (void) >= ;a.3.- (void) >= ;a.3.= %nterface between 1!2 and !M62 (6bAinterface)..........................................................................................>= ;a.3.; %nterface between Peer !M62s (6pAinterface)...............................................................................................>= ;a.3.< %nterface between 1T! and 6M4 (4mAinterface)..........................................................................................>= ;a.3.> %nterface between GM62 and 3'ternal 62! 2lient (6eAinterface)................................................................>= ;a.3.9 %nterface between 0&! and !tandA/lone 6M4. 43 (4uAinterface)...............................................................>= ;a.3.,+ %nterface between !0&2 and !/! (!tandA/lone !M62) (%upcAinterface)..................................................>; ;a.3.,, %nterface between GM62 and GM62 (6rAinterface)....................................................................................>; ;a.3.,* %nterface between GM62 and MM3 (!6 Ainterface)...................................................................................>; ;a.3.,3 %nterface between MM3 and 3A!M62 (!6sAinterface)................................................................................>; ;a.3.,- %nterface between GM62 and G!! (!6hAinterface).....................................................................................>; ;a.3.,= %nterface between GM62 and !G!& (6 dAinterface)..................................................................................>; ;a.- 2/M36Aspecific interfaces................................................................................................................................>; ;a.= 21!Aspecific interfaces......................................................................................................................................>< ;a.=., %nterface between the 212 and 0&! (%uJ12 %nterface)................................................................................>< ;a.=.* %nterface between the 212 and MM3 (!1c %nterface)...................................................................................>< ;a.=.3 %nterface between the 212 and 1!2..............................................................................................................>< ;a.; &umber portability specific interfaces...............................................................................................................>> ;a.;., %&Abased solution............................................................................................................................................>> ;a.;.* !i nallin 0elayAbased solution......................................................................................................................>> ;a.< %M !ubsystem 0eference Points.........................................................................................................................>> ;a.<., 0eference Point G!! K 2!28 (2' 0eference Point)......................................................................................>> ;a.<.* 0eference Point 2!28 K 43 (Gm 0eference Point).......................................................................................>> ;a.<.3 0eference Point MG28 K %M!AMGB (Mn 0eference Point)........................................................................>> ;a.<.- 0eference Point MG28 K 2!28 (M 0eference Point).................................................................................>9 ;a.<.= (void) >9 ;a.<.=a 0eference Point /!AM082 for media control (2r 0eference Point)............................................................>9 ;a.<.=b 0eference Point /!AM082 for session control (MrL 0eference Point)........................................................>9 ;a.<.; 0eference Point 2!28 A M082 (Mr 0eference Point)...................................................................................>9 ;a.<.;a 0eference Point M082 K M08P (Mp 0eference Point)...............................................................................>9 ;a.<.< 0eference Point 2!28 K 2!28 (Mw 0eference Point)..................................................................................9+ ;a.<.> (void) 9+ ;a.<.>a 0eference Point 2!28 K M01 (%!2 0eference Point).................................................................................9+ ;a.<.9 (void) 9+ ;a.<.9a 0eference Point /! K M01 (0c 0eference Point)........................................................................................9+ ;a.<.,+ 0eference Point 2!28 K 1G28 (Mi reference point)...................................................................................9+ ;a.<.,, 0eference Point 1G28 K MG28 (Mj reference point).................................................................................9+ ;a.<.,* 0eference Point 1G28F%128 K 1G28 (M" reference point).......................................................................9+ ;a.<.,3 0eference Point 2!28A !68 (:' 0eference Point)......................................................................................9+ ;a.<.,- 0eference Point to %Pv; networ" services (Mb reference point)..................................................................9, ;a.<.,= 0eference Point !A2!28 K /! (%!2 0eference Point).................................................................................9, ;a.<.,=a 0eference Point 3A2!28 A 3/T8 (%- 0eference Point)..............................................................................9, ;a.<.,=b 0eference Point %A2!28 A 3/T8 (%= 0eference Point)...............................................................................9, ;a.<.,; 0eference Point G!! K !%P /! or O!/ !2! (!h 0eference Point).............................................................9, ;a.<.,< 0eference Point G!! K 2/M36 %MA!!8 (!i 0eference Point)...................................................................9, ;a.<.,> 0eference Point 43 K /! (4t 0eference Point)............................................................................................9, ;a.<.,9 0eference Point /!A !68 (:h 0eference Point)...........................................................................................9, ;a.<.*+ 0eference Point 2!28F1G28 A %128 (M' 0eference Point).......................................................................9* ;a.<.*, 0eference Point %128 A TrGB (%' 0eference Point)....................................................................................9* ;a.<.** 0eference Point %A2!28 K /! (Ma 0eference Point)...................................................................................9* ;a.<.*3 0eference Point PA2!28 K %M! /ccess Gateway (%D 0eference Point).......................................................9* ;a.<.*3a 0eference Point 3A2!28 A 608 (Ml 0eference Point)...............................................................................9* ;a.<.*- 0eference Point %128 A %128 (%ci 0eference Point).....................................................................................9* ;a.<.*= 0eference Point TrGB A TrGB (%(i 0eference Point)..................................................................................9* ;a.<.*; ?oid 9*

3GPP

elease !"

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

;a.<.*< 0eference Point M!2 !erver A 2!28 (%* 0eference Point)..........................................................................9* ;a.<.*> 0eference Point M!2 !erver A T/! (%3 0eference Point)............................................................................93 ;a.<.*9 0eference Point %2! 43 K !22 /! (%, 0eference Point)............................................................................93 ;a.> ?oid 93 ;a.9 0eference Points for 3GPPFB6/& %nterwor"in ..............................................................................................93 ;a.9., 0eference point 3GPP /// !erver A G60 (:#FGr# 0eference Point).............................................................93 ;a.9.* 0eference point B6/& access networ" A 3GPP /// Pro'yF!erver (Ba 0eference Point).........................93 ;a.9.3 0eference point 3GPP /// !erver K 3GPP /// Pro'y (Bd 0eference Point)..........................................93 ;a.9.- 0eference point 3GPP /// !erverFPro'y A B/G (B 0eference Point)....................................................93 ;a.9.= 0eference point P:G A pac"et data networ"s (Bi 0eference Point)..............................................................9;a.9.; 0eference Point 3GPP /// !erverFPro'y A P:G (Bm 0eference Point).....................................................9;a.9.< 0eference Point B/G A B6/& access networ" (Bn 0eference Point)........................................................9;a.9.> 0eference Point B/G A P:G (Bp 0eference Point).....................................................................................9;a.9.9 0eference point B6/& 43 A P:G (Bu 0eference Point).............................................................................9;a.9.,+ 0eference point B6/& 43 A B6/& access networ" (Bw 0eference Point).............................................9;a.9.,, 0eference point 3GPP /// !erver A G!! (B' 0eference Point)...............................................................9;a.9.,* 0eference point 3GPP /// !erver A !68 (:w reference point).................................................................9= ;a.,+ M1M! specific reference points for GP0!.....................................................................................................9= ;a.,+., 0eference point GG!& K 1MA!2 (Gmb 0eference Point)...........................................................................9= ;a.,+.* 0eference point 1MA!2 K 1MA!2 (M( 0eference Point)............................................................................9= ;a.,+.3 0eference point GG!& K 0&! (or 1!! %u mode) (Gmc 0eference Point)..................................................9= ;a.,, M1M! specific reference points for 3P!........................................................................................................9= ;a.,,., 0eference point M1M!AGB K 1MA!2 (!Gmb 0eference Point)................................................................9= ;a.,,.* 0eference point M1M!AGB K 1MA!2 (!GiAmb 0eference Point).............................................................9= ;a.,,.3 0eference point M1M!AGB A MM3 (!m 0eference Point)........................................................................9= ;a.,,.- 0eference point M1M!AGB K !G!& (!n 0eference Point)........................................................................9= ;a.,,.= 0eference point M1M!AGB K 3A4T0/&F4T0/& (M, 0eference Point)................................................9; ;a.,,.; 0eference point MM3 K M23 (M3 0eference Point)..................................................................................9; ;a.,,.< 0eference point M23 A e&ode1 (M* 0eference Point)................................................................................9; ;a.,* 0eference Points for 3GPP Generic 4ser Profile (G4P).................................................................................9; ;a.,*., 0eference Point G4P !erver K /pplications (0 0eference Point).............................................................9; ;a.,*.* 0eference Point G4P !erver K G!! and /pplications K G!! (0p 0eference Point)...................................9; ;a.,3 0eference Points for Policy and 2har in 2ontrol..........................................................................................9; ;a.,3., 0eference Point P238 A P208FGAP208F?AP208 (G' 0eference Point)....................................................9; ;a.,3.* 0eference Point P208 A /pplication 8unction (0' 0eference Point)..........................................................9; ;a.,3.3 0eference Point !P0 K P208 (!p 0eference Point).....................................................................................9< ;a.,3.- 0eference Point O2! K P238 (Gy 0eference Point)....................................................................................9< ;a.,3.= 0eference Point O82! K P238 (G( 0eference Point)..................................................................................9< ;a.,3.; 0eference Point Trusted nonA3GPP %P /ccess and P208F?P208 (G'a 0eference Point).........................9< ;a.,3.< 0eference Point eP:G and P208F?P208 (G'b 0eference Point)..............................................................9< ;a.,3.<a 0eference Point eP:G and P208F?P208 (G'bM 0eference Point)..........................................................9< ;a.,3.> 0eference point between !AGB and P208F?P208 (G'cAinterface)...........................................................9< ;a.,3.9 0eference Point P208F?P208 K 11308 (G'' 0eference Point)...............................................................9< ;a.,3.,+ 0eference Point GP208 A ?P208 (!9A interface).....................................................................................9< ;a.,3.,, 0eference Point 4:0 K P208 (4d 0eference Point).................................................................................9< ;a.,3.,* 0eference Point T:8 A P208FGAP208F?AP208 (!d 0eference Point).....................................................9> ;a.,3.,3 0eference Point O2! A P208FGAP208 (!y 0eference Point)....................................................................9> ;a.,3.,- 0eference Point G&1 GB A P208F?AP208 (!,= 0eference Point).........................................................9> ;a.,3.,= 0eference Point 1P28 A P208FvAP208 (!9a 0eference Point).................................................................9> ;a.,3.,; 0eference Point O2! A T:8 (Gyn 0eference Point)..................................................................................9> ;a.,3.,< 0eference Point O82! A T:8 (G(n 0eference Point)................................................................................9> ;a.,- !M!%P specific reference points......................................................................................................................9> ;a.,-., 0eference point %PA!MAGB K G!! (N 0eference Point)...............................................................................9> ;a.,= 4ser :ata 2onver ence specific reference points............................................................................................9> ;a.,=., 0eference point /pplication 8ront 3nds A 4:0 (4d 0eference Point)........................................................9> ;a.,; !pecific reference points for facilitatin communications with pac"et data networ"s and applications.........99 ;a.,;., 0eference point MT2A%B8 A !2! (Tsp reference point)..............................................................................99 ;a.,;.* 0eference point MT2A%B8 A G!!FG60 (!;m reference point)...................................................................99 ;a.,;.3 0eference point MT2A/// A G!!FG60 (!;n reference point)...................................................................99 ;a.,;.- 0eference point MT2A%B8 A !M!A!2 (T- reference point)........................................................................99

3GPP

elease !"

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

< 0eference points between the P6M& and other networ"s....................................................................99

<., 0eference point fi'ed networ"s A M!2................................................................................................................99 <.* 0eference point GG!& A pac"et data networ"s (Gi reference point).................................................................,++ <.*a 0eference point P:& GB A pac"et data networ"s (!Gi reference point)........................................................,++ <.3 0eference point GM62 A e'ternal 62! 2lient (6e reference point).................................................................,++ <.- 0eference Point 2!28F%128 K Multimedia %P networ"s (Mm 0eference Point).............................................,++ <.= (void) ,++ <.; 0eference point P:G A pac"et data networ"s (Bi reference point)...................................................................,++ <.< 0eference Point B/G K B6/& access networ" (Bn reference point)............................................................,++ <.> 0eference point MT2A%B8 A !2! (Tsp reference point)...................................................................................,++

/., &ormative references.....................................................................................................................,+, /.* :efinitions related to Gateway 6ocation 0e ister (G60)...............................................................,+,
/.*., Gateway 6ocation 0e ister (G60)................................................................................................................,+, /.*.* %ntermediate MobileAservices !witchin 2entre (%MAM!2)..........................................................................,+, /.*.3 %ntermediate GP0! !ervin &ode (%MAG!&)................................................................................................,+,

/.3 The entities of the mobile system...................................................................................................,+,

/.3., Gateway 6ocation 0e ister (G60)................................................................................................................,+, /.3.* %ntermediate MobileAservices !witchin 2entre (%MAM!2)..........................................................................,+* /.3.3 %ntermediate GP0! !ervin &ode (%MAG!&)................................................................................................,+*

/.- 2onfi uration of a Public 6and Mobile &etwor"...........................................................................,+*

/.-., 1asic confi uration with G60 introduction...................................................................................................,+*

/.= P6M& interfaces............................................................................................................................,+3

/.=., %nterface between the G60 and the G60 (G6aAinterface).............................................................................,+3 /.=.* %nterface between the ?60 and the G60 (G6bAinterface)............................................................................,+3 /.=.3 %nterface between the !G!& and the G60 (G6cAinterface)..........................................................................,+3 /.=.- %nterface between the G60 and the %MJM!2 (G6dAinterface).....................................................................,+3 /.=.= %nterface between the G60 and the %MJG!& (G6eAinterface)......................................................................,+3 /.=.; %nterface between the !M!AGM!2 and the G60 (G6fAinterface)................................................................,+/.=.< %nterface between the !M!AGM!2 and the %MJM!2 (G6 Ainterface)........................................................,+/.=.> %nterface between the M!2 and the %MJM!2 (G6hAinterface).....................................................................,+/.=.9 %nterface between the GM62 and the %MJM!2 (G6iAinterface)..................................................................,+/.=.,+ %nterface between the GG!& and the %MJG!& (G6jAinterface)..................................................................,+/.=.,, %nterface between the !G!& and the %MJG!& (G6"Ainterface).................................................................,+-

3GPP

elease !"

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

!orewor)
This Technical !pecification (T!) has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuin wor" within the T!G and may chan e followin formal T!G approval. !hould the T!G modify the contents of the present document. it will be reAreleased by the T!G with an identifyin chan e of release date and an increase in version number as followsE ?ersion '.y.( whereE ' the first di itE , presented to T!G for informationO * presented to T!G for approvalO 3 or reater indicates T!G approved document under chan e control. y the second di it is incremented for all chan es of substance. i.e. technical enhancements. corrections. updates. etc. ( the third di it is incremented when editorial only chan es have been incorporated in the document.

4ntro) ction
This document presents the possible architectures of the 3GPP !ystem coverin both 4T0/& and G30/& radio access technolo ies. %n addition. this document also includes the 3volved Pac"et !ystem providin support for 3A4T0/& radio access technolo y in addition to 4T0/& and G30/& radio access technolo ies. /s well as providin support for 3A4T0/&. 4T0/& and G30/& radio access technolo ies. the 3volved Pac"et !ystem also provides support for nonA 3GPP access technolo ies ma"in it possible for these technolo ies to interwor" with the 3GPP specified 3volved Pac"et 2ore networ". The confi uration of nonA3GPP access networ"s usin 3P! is not within the scope of 3GPP specification. This document also presents the architecture for the %P Multimedia !ubsystem common to 3GPP and other access systems such as 8i'ed 1roadband and those specified by 3GPP* and provide architecture for interwor"in and session continuity between %M! and 2ircuit !witched systems. 2lause 3 of the document contains the definition of the P6M& entities. 2lause - of the document contains the description of the basic entities of the P6M&. and clause -a contains the description of the specific entities of the P6M&. 2lause = of the document contains the confi uration of the P6M&. 2lauses ;. ;a and < of the document contain the P6M&#s basic and specific interfaces and reference points and the P6M&#s interfaces towards other networ"s.

3GPP

elease !"

!%

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

Sco$e

This document offers an overview of the 3GPP P6M& and its architectures and confi uration. The confi uration and the functional entities of the P6M& and the interfaces between them are described on a eneral level in order to cope with possible implementations. These descriptions include interfaces between and within the core networ"s. the access networ"s. the user eDuipment. different service platforms. different domains and subsystems. and functional entities within domains and subsystems. This document covers different architectural aspects with varyin level of detail. %n eneral. other specifications shall be referred to for further detailsO these specifications enable the reader to acDuire the full understandin of a system or service feature. &ote that this document does not cover. or even list. all features of P6M&s.

+e5erence'
0eferences are either specific (identified by date of publication. edition number. version number. etc.) or nonAspecific. 8or a specific reference. subseDuent revisions do not apply. 8or a nonAspecific reference. the latest version applies. %n the case of a reference to a 3GPP document (includin a G!M document). a nonAspecific reference implicitly refers to the latest version of that document in the same Release as the present document. P,C P,aC P*C P*aC P*bC P*cC P3C P-C P=C P;C P<C P>C P9C P9aC P,+C P,+aC PvoidC 3GPP T0 *,.9+=E Q?ocabulary for 3GPP !pecificationsQ. 3GPP T! **.+,;E Q%nternational Mobile station 3Duipment %dentities (%M3%)Q. 3GPP T! **.+;+E QGeneral Pac"et radio !ervice (GP0!)O !ervice descriptionO !ta e ,Q. 3GPP T! **.+<,E Q6ocation !ervices (62!)O !ervice descriptionO !ta e ,Q. 3GPP T! **.+<>E Q2ustomised /pplications for Mobile networ" 3nhanced 6o ic (2/M36)O !ervice description. !ta e ,Q. 3GPP T! *3.++3E Q &umberin . addressin and identificationQ. 3GPP T! **.,*<E QOpen !ervice /ccess (O!/)Q. 3GPP T! *3.++>E QOr ani(ation of subscriber dataQ. 3GPP T! *3.++9E QGandover proceduresQ. 3GPP T! *3.+,*E Q6ocation Mana ement ProceduresQ. 3GPP T! *3.+-,E QTechnical reali(ation of 2ell 1roadcast !ervice (21!)Q. PvoidC 3GPP T! *3.+;+E QGeneral Pac"et 0adio !ervice (GP0!)O !ervice descriptionO !ta e *Q. PvoidC 3GPP T! -3.+;-E Q:i ital cellular telecommunication system (Phase *R)O General Pac"et 0adio service (GP0!)O Overall description of the GP0! radio interfaceO !ta e *Q.

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

3GPP

elease !"

!!

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

P,+bC P,+cC P,+dC P,,C P,,aC P,,bC P,*C P,3C P,-C P,-aC P,=C P,;C P,<C P,>C P,9C P*+C P*,C P**C P*3C P*-C P*=C P*;C P*<C P*>C P*9C P3+C

3GPP T! *=.3+=E Q!ta e * 8unctional !pecification of 43 Positionin in 4T0/&Q. 3GPP T! *3.+<>E Q2ustomised /pplications for Mobile networ" 3nhanced 6o ic (2/M36) Phase 3 A !ta e *Q. 3GPP T! -3.+=9E Q8unctional !ta e * :escription of 6ocation !ervices in G30/&Q. %T4AT 0ecommendation S.,*,- (+=F,99=)E Q:istributed 8unctional Plane for %ntelli ent &etwor" 2!A,Q. 3GPP T! *3.,+,E QGeneral 4MT! /rchitectureQ. 3GPP T! *3.,,+E Q4MT! /ccess !tratum)O !ervices and 8unctionsQ. 3GPP T! *-.++*E QG!M A 4MT! Public 6and Mobile &etwor" (P6M&) access reference confi urationQ. 3GPP T! ->.++,E Q1ase !tation !ystem A MobileAservices !witchin 2entre (1!! A M!2) interfaceO General aspectsQ. 3GPP T! ->.++*E Q1ase !tation !ystem A MobileAservices !witchin 2entre (1!! A M!2) interfaceO %nterface principlesQ. 3GPP T! *=.-,+E Q4T0/& %u %nterfaceE eneral aspects and principlesQ. 3GPP T! ->.++-E Q1ase !tation !ystem A MobileAservices !witchin 2entre (1!! A M!2) interface 6ayer , specificationQ. 3GPP T! ->.++;E Q!i nallin transport mechanism specification for the 1ase !tation !ystem A MobileAservices !witchin 2entre (1!! A M!2) interfaceQ. 3GPP T! ->.++>E QMobileAservices !witchin 2entre A 1ase !tation !ystem (M!2 A 1!!) interfaceO 6ayer 3 specificationQ. PvoidC 3GPP T! ->.+=,E Q1ase !tation 2ontroller A 1ase Transceiver !tation (1!2 A 1T!) interfaceO General aspectsQ. 3GPP T! ->.+=*E Q1ase !tation 2ontroller A 1ase Transceiver !tation (1!2 A 1T!) interfaceO %nterface principlesQ. 3GPP T! ->.+=-E Q1ase !tation 2ontroller A 1ase Transceiver !tation (1!2 A 1T!) interfaceO 6ayer , structure of physical circuitsQ. 3GPP T! ->.+=;E Q1ase !tation 2ontroller A 1ase Transceiver !tation (1!2 A 1T!) interfaceO 6ayer * specificationQ. 3GPP T! ->.+=>E Q1ase !tation 2ontroller A 1ase Transceiver !tation (1!2 A 1T!) interfaceO 6ayer 3 specificationQ. 3GPP T! ->.+;+E Q%nAband control of remote transcoders and rate adaptors for full rate traffic channelsQ. 3GPP T! ->.+;,E Q%nAband control of remote transcoders and rate adaptors for half rate traffic channelsQ. 3GPP T! *9.++*E QMobile /pplication Part (M/P) specificationQ. 3GPP T! **.**>E Q!ervice reDuirements for the %P Multimedia 2ore &etwor" !ubsystemQ. 3GPP T! *3.*+<E Q3ndAtoAend Suality of !ervice (So!) concept and architectureQ. PvoidC. PvoidC.

3GPP

elease !"

!"

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

P3,C

3GPP T! *9.++<E QGeneral reDuirements on interwor"in between the Public 6and Mobile &etwor" (P6M&) and the %nte rated !ervices :i ital &etwor" (%!:&) or Public !witched Telephone &etwor" (P!T&)Q. 3GPP T! *9.+,+E Q%nformation element mappin between Mobile !tation A 1ase !tation !ystem (M! K 1!!) and 1ase !tation !ystem A MobileAservices !witchin 2entre (1!! A M!2)O !i nallin procedures and the Mobile /pplication Part (M/P)Q. 3GPP T! *9.+,,E Q!i nallin interwor"in for supplementary servicesQ. 3GPP T! *3.**>E Q%P Multimedia !ubsystem (%M!)O !ta e *Q. 3GPP T! -,.,+3E QG!M 0elease = specificationsQ. 3GPP T! -3.+=,E QTechnical !pecification Group G!MF3:G3 0adio /ccess &etwor"O Overall description. !ta e *Q. 3GPP T! *3.**;E QGlobal Te't Telephony (GTT)O !ta e *Q. 3GPP T! *;.**;E Q2ellular Te't Telephone ModemO General :escriptionQ. 3GPP T! *3.+,;EQ!ubscriber data mana ementO !ta e *Q. 3GPP T! *3.+;;E Q!upport of Mobile &umber Portability (M&P)O Technical reali(ationO !ta e *Q. 3GPP T! -3.+;>E Q?oice Group 2all !ervice (?G2!)O !ta e *Q. 3GPP T! -3.+;9E Q?oice 1roadcast !ervice (?1!)O !ta e *Q. 3GPP T! *3.*+=E Q1earer independent circuit switched core networ"O !ta e *Q. 3GPP T! ->.+,-E Q1ase !tation !ystem (1!!) K !ervin GP0! !upport &ode (!G!&) interfaceO Gb interface 6ayer ,Q. 3GPP T! ->.+,;E Q1ase !tation !ystem (1!!) K !ervin GP0! !upport &ode (!G!&) interfaceO &etwor" serviceQ. 3GPP T! ->.+,>E Q1ase !tation !ystem (1!!) K !ervin GP0! !upport &ode (!G!&)O 1!! GP0! Protocol (1!!GP)Q. 3GPP T! ->.+3,E Q!ervin Mobile 6ocation 2entre K !ervin Mobile 6ocation 2entre (!M62 K !M62)O !M62PP specificationQ. 3GPP T! *9.+,;E Q!ervin GP0! !upport &ode (!G!&) K ?isitor 6ocation 0e ister (?60)O Gs interface networ" service specificationQ. 3GPP T! *9.+,>E Q!ervin GP0! !upport &ode (!G!&) K ?isitor 6ocation 0e ister (?60)O Gs interface 6ayer 3 specificationQ. 3GPP T! -9.+3,E Q&etwor" 6ocation !ervices (62!)O 1ase !tation !ystem /pplication Part 62! e'tension (1!!/PA63)Q. 3GPP T! *9.+;+E QGP0! Tunnellin Protocol (GTP) across the Gn and Gp %nterfaceQ. %T4AT 0ecommendation G.*->E QGateway 2ontrol ProtocolQ. %T4AT 0ecommendation 3.,;-E QThe %nternational public telecommunication numberin planQ. %T4AT 0ecommendation G.3*3E QPac"etAbased multimedia communications systemsQ. 3GPP T! --.+<,E QMobile radio interface layer 3 6ocation !ervices (62!) specificationQ. 3GPP T! *3.*<,E Q8unctional sta e * description of 62!Q. %T4AT 0ecommendation %.3;3A* EQ1A%!:& /TM /daptation 6ayer (//6) type * specificationQ. %T4AT 0ecommendation G.*-=E Q2ontrol protocol for multimedia communicationQ.

P3*C

P33C P3-C P3=C P3;C P3<C P3>C P39C P-+C P-,C P-*C P-3C P--C P-=C P-;C P-<C P->C P-9C P=+C P=,C P=*C P=3C P=-C P==C P=;C P=<C P=>C

3GPP

elease !"

!3

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

P=9C P;+C P;,C P;*C P;3C P;-C P;=C P;;C P;<C P;>C P;9C P<+C P<,C P<*C P<3C P<-C P<=C P<;C P<<C P<>C P<9C P>+C P>,C P>*C P>3C P>-C P>=C P>;C P><C

%3T8 082 <;>E Q4ser :ata ram ProtocolQ. %3T8 082 ,>>9E Q0TPE / Transport Protocol for 0ealATime /pplicationsQ. %3T8 082 3*;,E Q!%PE !ession %nitiation ProtocolQ. OM/ M6P T!E QMobile 6ocation ProtocolQ. PhttpEFFwww.openmobilealliance.or FC. 3GPP T! *9.,9>E QOpen !ervice /ccess (O!/) /pplication Pro rammin %nterface (/P%)Q. 3GPP T! 33.*,+E Q3G !ecurityO &etwor" :omain !ecurityO %P networ" layer securityQ. 3GPP T! *3.*3;E Q%ntra :omain 2onnection of 0/& &odes to Multiple 2& &odesQ. 3GPP T! *=.-=3E Q4T0/& %upc interface Positionin 2alculation /pplication Part (P2/P) si nallin Q. 3GPP T! *3.*3-E Q3GPP system to Bireless 6ocal /rea &etwor" (B6/&) interwor"in Q. 3GPP T! *3.,-,E QPresence !erviceO /rchitecture and functional descriptionQ. OM/ 06P T!E Q0oamin 6ocation ProtocolQ. PhttpEFFwww.openmobilealliance.or FC. 3GPP T! *3.*-;E QMultimedia 1roadcastFMulticast !ervice (M1M!)O /rchitecture and functional descriptionQ. 3GPP T! *3.*-+E Q3GPP Generic 4ser Profile (G4P)O /rchitecture (!ta e *)Q. 3GPP T! 33.***E QGeneric /uthentication /rchitecture (G//)O /ccess to networ" application functions usin Gyperte't Transfer Protocol over Transport 6ayer !ecurity (GTTP!)Q. 3GPP T! *3.*+3E QPolicy 2ontrol and 2har in /rchitecture (!ta e *)Q. 3GPP T! *3.,;<E Q%P Multimedia !ubsystem (%M!) emer ency sessionsQ. 3GPP T! *3.*+-E Q!upport of !hort Messa e !ervice (!M!) over eneric 3GPP %nternet Protocol (%P) accessQ. 3GPP T! *3.-+,EQGeneral Pac"et 0adio !ervice (GP0!) enhancements for 3volved 4niversal Terrestrial 0adio /ccess &etwor" (3A4T0/&) accessQ. 3GPP T! *3.-+*E Q/rchitecture enhancements for nonA3GPP accessesQ. 3GPP T! 3;.3++E Q3volved 4niversal Terrestrial 0adio /ccess (3A4T0/) and 3volved 4niversal Terrestrial 0adio /ccess &etwor" (3A4T0/&)O Overall descriptionO !ta e *Q. 3GPP T! 3;.-+,E Q3volved 4niversal Terrestrial 0adio /ccess &etwor" (3A4T0/&)O /rchitecture descriptionQ. Open Mobile /lliance. OM/ 30P !4P6 ?*.+E Q!ecure 4ser Plane 6ocation 3nabler 0elease Pac"a eQ. (httpEFFwww.openmobilealliance.or ). 3GPP T! *3.*<*E Q2ircuit !witched 8allbac" in 3volved Pac"et !ystemO !ta e *Q. 3GPP T! *9.,,>E QMobility Mana ement 3ntity (MM3) K ?isitors 6ocation 0e ister (?60) !Gs interface specificationQ. 3GPP T! *3.*,;E Q!in le 0adio ?oice 2all 2ontinuity (!0?22)O !ta e *Q. 3GPP T! 33.,+<E Q3G securityO 6awful interception architecture and functionsQ. 3GPP T! 3*.*-+E QTelecommunication mana ementO 2har in mana ementO 2har in architecture and principlesQ. 3GPP T! *9.*<*E Q3volved Pac"et !ystem (3P!)O Mobility Mana ement 3ntity (MM3) and !ervin GP0! !upport &ode (!G!&) related interfaces based on :iameter protocolQ. 3GPP T! 33.-+,EQ3GPP !ystem /rchitecture 3volution (!/3)O !ecurity architectureQ.

3GPP

elease !"

!'

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

P>>C P>9C P9+C P9,C P9*C P93C P9-C P9=C P9;C P9<C P9>C P99C P,++C P,+,C P,+*C P,+3C P,+-C P,+=C P,+;C P,+<C P,+>C P,+9C P,,+C P,,,C P,,*C P,,3C P,,-C

3GPP T! 33.-+*E Q3GPP !ystem /rchitecture 3volution (!/3)O !ecurity aspects of nonA3GPP accessesQ. 3GPP T! *-.3+,E Q&onA/ccessA!tratum (&/!) protocol for 3volved Pac"et !ystem (3P!)O !ta e 3Q. 3GPP T! *9.*<-E QGeneral Pac"et 0adio !ervice (GP0!)O 3volved GP0! Tunnellin Protocol (eGTP) for 3P!Q. 3GPP T! *9.*>+E Q3volved Pac"et !ystem (3P!)O 3GPP !v interface (MM3 to M!2. and !G!& to M!2) for !0?22Q. 3GPP T! *9.*,3E QP22 !i nallin 8lows and Mappin TablesQ. 3GPP T! *9.*<=E QPro'y Mobile %Pv; (PM%Pv;) based Mobility and Tunnellin protocolsO !ta e 3Q. 3GPP T! *-.3+-E QMobility mana ement based on Mobile %Pv-O 4ser 3Duipment (43) A forei n a ent interfaceO !ta e 3Q. 3GPP T! *-.3+3E QMobility mana ement based on :ualA!tac" Mobile %Pv;O !ta e 3Q. 3GPP T! *9.*<3E Q3volved Pac"et !ystem (3P!)O 3GPP 3P! /// interfacesQ. 3GPP T! *-.3+*E Q/ccess to the 3GPP 3volved Pac"et 2ore (3P2) via nonA3GPP access networ"sQ. 3GPP T! *9.,;>E Q2ell 1roadcast 2entre interfaces with the 3volved Pac"et 2oreO !ta e 3Q. 3GPP T! *9.*,*E QPolicy and 2har in 2ontrol (P22)O 0eference pointsQ. 3GPP T! *9.*,-E QPolicy and 2har in 2ontrol over 0' %nterfaceQ. 3GPP T! 3*.*=,EQTelecommunication mana ementO 2har in mana ementO Pac"et !witched (P!) domain char in Q. %3T8 082 -++;E Q:iameter 2reditA2ontrol /pplicationQ. 3GPP T! *9.*,=E QPolicy and 2har in 2ontrol over !9 %nterfaceQ. 3GPP T! *9.+;,E Q%nterwor"in between P6M& supportin pac"et based services and P:&Q. ?oid. 3GPP* /.!+++>A2E Q%nteroperability !pecification (%O!) for Gi h 0ate Pac"et :ata (G0P:) 0adio /ccess &etwor" %nterfaces with !ession 2ontrol in the /ccess &etwor"Q. 3GPP* 2.!++>< +E Q3A4T0/& A G0P: and 2:M/*+++ ,' 2onnectivity and %nterwor"in E /ir %nterface /spectsQ. 3GPP T! 3*.*9;E QTelecommunication mana ementO 2har in mana ementO Online 2har in !ystem (O2!)E /pplications and interfacesQ. 3GPP T! 3*.*9=E QTelecommunication mana ementO 2har in mana ementO 2har in :ata 0ecord (2:0) transferQ. 3GPP T! *3.*9*E Q%P Multimedia !ubsystem (%M!) 2entrali(ed !ervicesQ. 3GPP T! *3.*3<E Q%P Multimedia !ubsystem (%M!) !ervice 2ontinuityQ. 3GPP T! *3.3*<E QMobility between 3GPPABireless 6ocal /rea &etwor" (B6/&) %nterwor"in and 3GPP !ystemsQ. 3GPP T! *3.*,>E Q%P Multimedia (%M) session handlin O %M call modelO !ta e *Q. 3GPP T! *=.-;<E Q4T0/& architecture for 3G Gome &ode 1 (G&1)O !ta e *Q.

3GPP

elease !"

!)

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

P,,=C P,,;C P,,<C P,,>C P,,9C P,*+C P,*,C P,**C P,*3C

3GPP T! *=.-;>E Q4T0/& %uh %nterface 0/&/P 4ser /daption (04/) si nallin Q. 3GPP T! *=.-;9E Q4T0/& %uh interface Gome &ode 1 (G&1) /pplication Part (G&1/P) si nallin Q. 3GPP T! *-.*>=E Q/llowed 2losed !ubscriber Group (2!G) 6istO Mana ement Object (MO)Q. 3GPP T! 3,.,+*E Q2haracteristics of the 4niversal !ubscriber %dentity Module (4!%M) applicationQ. 3GPP T! ->.+-9E Q1ase !tation 2ontroller A 2ell 1roadcast 2entre (1!2A212) %nterface !pecificationO 2ell 1roadcast !ervice Protocol (21!P)Q. 3GPP T! *3.33=E Q4ser :ata 2onver ence (4:2)O Technical reali(ation and information flowsO !ta e *Q. 3GPP T! *9.33=E Q4ser :ata 2onver ence (4:2)O 4ser :ata 0epository /ccess Protocol over the 4d interfaceO !ta e 3Q. 3GPP T! 3;.3+=E Q3volved 4niversal Terrestrial 0adio /ccess &etwor" (3A4T0/&)O !ta e * functional specification of 4ser 3Duipment (43) positionin in 3A4T0/&Q. 3GPP T! *9.,<*E Q6ocation !ervices (62!)O 3volved Pac"et 2ore (3P2) 62! Protocol (36P) between the Gateway Mobile 6ocation 2entre (GM62) and the Mobile Mana ement 3ntity (MM3)O !6 interfaceQ. 3GPP T! *9.,<,E Q6ocation !ervices (62!)O 62! /pplication Protocol (62!A/P) between the Mobile Mana ement 3ntity (MM3) and 3volved !ervin Mobile 6ocation 2entre (3A!M62)O !6s interfaceQ. 3GPP T! *9.,<3E Q6ocation !ervices (62!)O :iameterAbased !6h interface for 2ontrol Plane 62!Q. 3GPP T! *9.*>,E QGP0! Tunnellin Protocol 4ser Plane (GTPv,A4)Q. 3GPP T! 3;.--3E Q3volved 4niversal Terrestrial 0adio /ccess &etwor" (3A4T0/&)O M* /pplication Protocol (M*/P)Q. 3GPP T! 3;.---E Q3volved 4niversal Terrestrial 0adio /ccess &etwor" (3A4T0/&)O M3 /pplication Protocol (M3/P)Q. 3GPP T! 3;.--=E Q3volved 4niversal Terrestrial 0adio /ccess &etwor" (3A4T0/&)O M, data transportQ. 3GPP T! **.**+E Q!ervice 0eDuirements for Gome &ode1s and Gome e&ode1sQ. 3GPP T! *9.*,9E QPolicy and char in controlE !pendin limit reportin over !y reference pointQ. 3GPP T! *3.;>*E Q/rchitecture enhancements to facilitate communications with pac"et data networ"s and applicationsQ. 3GPP T! *9.33;E QGome !ubscriber !erver (G!!) diameter interfaces for interwor"in with pac"et data networ"s and applicationsQ. 3GPP T! *9.33<E Q:iameter based T- %nterface for communications with pac"et data networ"s and applicationsQ. 3GPP T! *9.33>E Q:iameter based protocols to support of !M! capable MM3sQ. 3GPP T! *9.3;>E QTsp interface protocol between the MT2 %nterwor"in 8unction (MT2A%B8) and !ervice 2apability !erver (!2!)Q. 3GPP T! *3.+-+E QTechnical reali(ation of the !hort Messa e !ervice (!M!)Q. %3T8 082 <93 (,9>,)E QTransmission 2ontrol ProtocolQ (!T: <).

P,*-C

P,*=C P,*;C P,*<C P,*>C P,*9C P,3+C P,3,C P,3*C P,33C P,3-C P,3=C P,3;C P,3<C P,3>C

3GPP

elease !"

!*

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

P,39C

3GPP T! *;.*33E QTransparent endAtoAend Pac"etAswitched !treamin !ervice (P!!)O General :escriptionQ.

6e5inition' an) a..re7iation'

%n addition to the abbreviations iven in the remainder of this clause others are listed in T0 *,.9+= P,aC. The definitions of the entities of the mobile system are iven in the ne't clause.

3.1 P .&ic Lan) Mo.i&e ,etwork (PLM,)

/ Public 6and Mobile &etwor" (P6M&) is established and operated by an administration or 0eco ni(ed Private Operatin / ency (0PO/) for the specific purpose of providin land mobile telecommunications service services to the public. / P6M& may be re arded as an e'tension of networ"s (e. . %!:&. corporate and public P:&s. etc.)O it is a collection of M!2s areas in 2! domain and !G!& areas for GP0! and !G!& or MM3 areas for 3P2 in P! domain within a common numberin plan (e. . same &ational :estination 2ode) and a common routin plan. The M!2s are the functional interfaces between the fi'ed networ"s and a P6M& for call setAup in 2! domain. The GG!& and the !G!& are the functional interfaces between the fi'ed networ"s and a P6M& for pac"et transmission in GP0! P! domain. %n case of 3P2 P! :omain. the P:& GB. !ervin AGB and the !G!& and the MM3 are the functional interfaces between the fi'ed networ"s and a P6M& for pac"et transmission. 8unctionally the P6M&s may be re arded as independent telecommunications entities even thou h different P6M&s may be interconnected throu h the %!:&FP!T& and P:&s for forwardin of calls or networ" information. / similar type of interconnection may e'ist for the interaction between the M!2sF!G!&sFMM3s of one P6M&.

3.2 (ore ,etwork ((,) an) %cce'' ,etwork (%,)

The P6M& infrastructure is lo ically divided into a 2ore &etwor" (2&) and an /ccess &etwor" (/&) infrastructures. as defined in T! *3.,+, P,,aC and T! *3.,,+ P,,bC. The 2& is lo ically divided into a 2! domain. a P! domain and an %M subsystem. as defined in ne't clause. The /& are G30/& (also called 1!! for G!M). 4T0/& (also called 0&!). 3A4T0/&. as defined in clause QThe /ccess &etwor"Q.

3.3 (irc it Switche) ((S) an) Packet Switche) (PS) 6o8ain'

The 2& is constituted of a 2ircuit !witched (2!) domain and a Pac"et !witched (P!) domain (which includes GP0! and 3P2). These two domains differ by the way they support user traffic. as e'plained below. These two domains are overlappin . i.e. they contain some common entities. / P6M& can implement only one domain or both domains.

3.3.1 (S 6o8ain
The 2! domain refers to the set of all the 2& entities offerin Q2! type of connectionQ for user traffic as well as all the entities supportin the related si nallin . / Q2! type of connectionQ is a connection for which dedicated networ" resources are allocated at the connection establishment and released at the connection release. The entities specific to the 2! domain areE M!2. GM!2. ?60. /ll the other 2& entities defined in clause - QThe basic entities of the mobile systemQ and not defined as P! domain specific entities (see followin clause) are common to the 2! and to the P! domains. %n case of 3A4T0/& access. there is no support for 2! :omain.

3.3.2 PS 6o8ain
The P! domain refers to the set of all the 2& entities offerin QP! type of connectionQ for user traffic as well as all the entities supportin the related si nallin . / QP! type of connectionQ transports the user information usin autonomous concatenation of bits called pac"etsE each pac"et can be routed independently from the previous one.

3GPP

elease !"

!+

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

The entities specific to the P! domain are the GP0! specific entities. i.e. !G!& and GG!& and 3P! specific entities. i.e. P:& GB. !AGB. MM3. !G!&. /ll the other 2& entities defined in clause Q- The basic entities of the mobile systemQ and not defined as 2! domain specific entities (see previous clause) are common to the 2! and to the P! domains.

3.3a 4P M &ti8e)ia ' .'9'te8 (4MS)

The %M subsystem comprises all 2& elements for provision of %P multimedia services comprisin audio. video. te't. chat. etc. and a combination of them delivered over the P! domain. The entities related to %M! are 2!28. MG28. M08. etc. as defined in the sta e * of the %M subsystem T! *3.**> P3-C. !ee T! **.**> P*<C for some service e'amples of %M!.

3.4 Location re3i'ter

To enable communication to a mobile station the networ" must "now where this mobile station is located. This information is stored in a function named location re ister. The location re ister is handled by the followin entities. A The Gome 6ocation 0e ister (G60).

The Gome 6ocation 0e ister (G60) is the location re ister to which a mobile subscriber is assi ned for record purposes such as subscriber information. 8or 3P!. the G60 functionality is provided via G!!. A The ?isitor 6ocation 0e ister (?60).

The ?isitor 6ocation 0e ister (?60) is the location re ister for 2ircuit !witched (2!) services. other than the G60. used by an M!2 to retrieve information for. e. . handlin of calls to or from a roamin mobile station currently located in its area. A The !ervin GP0! !upport &ode (!G!&).

The location re ister function in the !G!& stores subscription information and location information for Pac"et !witched (P!) services for each subscriber re istered in the !G!&. The !G!& is needed only in a P6M& which supports P! :omain with G30/& or 4T0/& access. A The Gateway GP0! !upport &ode (GG!&).

The location re ister function in the GG!& stores subscriber information and routein information (needed to tunnel pac"et data traffic destined for a GP0! M! to the !G!& where the M! is re istered) for each subscriber for which the GG!& has at least one P:P conte't active. The GG!& is needed only in a P6M& which supports GP0! with G30/& or 4T0/& access. A The Mobility Mana ement 3ntity (MM3).

The location re ister function in the MM3 stores subscription information and location information for Pac"et !witched (P!) services for each subscriber re istered in the MM3 for 3P!. A The Pac"et :ata &etwor" Gateway (P:& GB).

The location re ister function in the P:& GB stores subscriber information and routein information (needed to tunnel pac"et data traffic destined for an 3P! 43 to the !ervin GB. where the 43 is re istered in the MM3. in the !G!& or in the 3GPP /// server in case of nonA3GPP access) for each subscriber for which the P:& GB has at least one P:& connection active.

3.- (e&&
The cell is an area of radio covera e identified by a 1ase station identification as defined in T! *3.++3 P3C.

3GPP

elease !"

!,

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

3." :a'e Station (ontro&&er (:S() area

The 1ase !tation 2ontroller (1!2) area is an area of radio covera e consistin of one or more cells controlled by one 1!2. The boundaries of a 1!2 area and a location area are independentO a location area may span the boundary between 1!2 area and a 1!2 area may span the boundary between location areas.

3.1 +a)io ,etwork (ontro&&er (+,() area

The 0adio &etwor" 2ontroller (0&2) area is an area of radio covera e consistin of one or more cells controlled by one 0&2. The boundaries of a 0&2 area and a location area are independentO a location area may span the boundary between 0&2 area and a 0&2 area may span the boundary between location areas.

3.; Location %rea (L%)

The 6ocation /rea (6/) is defined as an area in which a mobile station may move freely without updatin the ?60. / location area includes one or several G30/&F4T0/& cells.

3.# +o tin3 %rea (+%)

The 0outin /rea (0/) is defined as an area in which a mobile station. in certain operation modes. may move freely without updatin the !G!&. / routin area includes one or several G30/&F4T0/& cells. / 0/ is always contained within a location area.

3.#a Trackin3 %rea (T%)

/ Trac"in /rea (T/) includes one or several 3A4T0/& cells. The networ" allocates a list with one or more T/s to the 43 . %n certain operation modes. the 43 may move freely in all T/s of the list without updatin the MM3.

3.10 MS( area

The M!2 area is the part of the networ" covered by an M!2. /n M!2 area may consist of one or several location areas. /n M!2 area may also consist of one or several 1!2 areas.

3.11 VL+ area

The ?60 area is the part of the networ" controlled by a ?60. / ?60 area may consist of one or several M!2 areas.

3.12 SGS, area

The !G!& area is the part of the networ" served by an !G!&. /n !G!& area may consist of one or several routin areas. /n !G!& area may also consist of one or several 1!2 areas. There need not be a one to one relationship between !G!& area and M!2F?60 area.

3.13 <one' 5or +e3iona& S .'cri$tion

/ P6M& operator may define a number of re ional subscription areas. each of which is a subset of the service area for an unrestricted mobile subscriber. / re ional subscription area may be contained within the service area of a sin le P6M&. or may lie within the service areas of two or more P6M&s. 3ach re ional subscription area consists of one or more (onesO each (one is contained within the service area of a P6M&. The definition of a mobile subscriber#s re ional subscription area is stored within the G60FG!! per &ational :estination 2ode(s) (&:2) of a P6M& and is transferred to the ?60s andFor !G!&sFMM3s of that P6M&. The ?60 andFor !G!&FMM3 evaluates this information to e'tract the restricted or accessible M!2 andFor !G!&FMM3 areas and

3GPP

elease !"

!-

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

location areas to which the mobile subscriber is allowed to roam. The ?60 andFor !G!&FMM3 inform the G60FG!! if an entire M!2 andFor !G!&FMM3 area is restricted. @ones for 0e ional !ubscription and their handlin are defined in T! *3.++3 P3C. T! *3.++> P=C and T! *9.++* P*;C and T! *9.*<* P>;C for 3P2.

3.14 Ser7ice area

The service area is defined as an area in which a mobile subscriber can be reached by another (mobile or fi'ed) subscriber without the subscriber#s "nowled e of the actual location of the mobile station within the area. / service area may consist of several P6M&s. One service area may consist of one country. be a part of a country or include several countries. The location re istration system associated with each service area must thus contain a list of all mobile stations located within that service area.

3.1- Gro $ ca&& area

The roup call area is a predefined area composed of one or a number of cells to which a particular ?oice Group 2all !ervice (?G2!) or ?oice 1roadcast !ervice (?1!) call is distributed. The composition of a roup call area is predefined in the networ". The roup call area may include cells of more than one M!2 area and cells of more than one P6M&.

3.1-a MME %rea

The MM3 area is the part of the networ" served by an MM3. /n MM3 area consists of one or several Trac"in /reas. /ll cells served by an e&ode1 are included in an MM3 /rea. There is no one to one relationship between an MM3 /rea and an M!2F?60 area. Multiple MM3s may have the same MM3 /rea as described in clause QPoolAareaQ. MM3 /reas may overlap each other.

3.1" Poo&-area
/ pool area is an area where %ntra :omain 2onnection of 0/& &odes to Multiple 2& &odes is applied. Bithin a poolA area an M! may roam without need to chan e the servin 2ore &etwor" (2&) node. / poolAarea is served by one or more 2& nodes in parallel.

3.11 Ser7in3 G= Ser7ice %rea

/ !ervin GB !ervice /rea is the part of the networ" served by sin le !ervin GB. !ervin GB !ervice /reas consist of one or several complete Trac"in /reas. /ll cells served by an e&ode1 are included in an !ervin GB !ervice /rea .!ervin GB !ervice /reas may overlap each other. There is no one to one relationship between an MM3 /rea and a !ervin GB !ervice /rea.

The .a'ic entitie' o5 the 8o.i&e '9'te8

To provide the mobile service as it is defined. it is necessary to introduce some specific functions. These functional entities can be implemented in different eDuipments or athered. %n any case. e'chan es of data occur between these entities. 3ntities in the mobile system can be either implemented in a monolithic way where user data are stored within the entity itself (or in an e'ternal entity via non standard interfaces) or accordin to the 4ser :ata 2onver ence (4:2) concept (see T! *3.33= P,*+C) where the entity becomes a soAcalled userAdataless /pplication 8ront 3nd (/83). /pplication 8ront 3nds access. via the 4d reference point. a 4ser :ata 0epository (4:0). which stores the relevant user data mana ed by the applications. 4nless e'plicitly stated otherwise. this document describes entities in its monolithic form. e. . statin that user data are stored in the G!!. %f however the 4:2 concept applies. user data are actually stored in the 4:0 and mana ed by one or several /pplication 8ront 3nds. so that user data may be shared amon the different

3GPP

elease !"

"%

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

/pplication 8ront 3nds. allowin several /83s of the same application type (e. . G!!) to serve the same user at any iven time.

4.1 The (ore ,etwork ((,) entitie'

4.1.1 Entitie' co88on to the PS an) (S )o8ain'
4.1.1.1 The >o8e S .'cri.er Ser7er (>SS)

The G!! is the master database for a iven user. %t is the entity containin the subscriptionArelated information to support the networ" entities actually handlin callsFsessions. / Gome &etwor" may contain one or several G!!sE it depends on the number of mobile subscribers. on the capacity of the eDuipment and on the or anisation of the networ". /s an e'ample. the G!! provides support to the call control servers in order to complete the routin Froamin procedures by solvin authentication. authorisation. namin Faddressin resolution. location dependencies. etc. The G!! is responsible for holdin the followin user related informationE A A A A 4ser %dentification. &umberin and addressin informationO 4ser !ecurity informationE &etwor" access control information for authentication and authori(ationO 4ser 6ocation information at interAsystem levelE the G!! supports the user re istration. and stores interAsystem location information. etc.O 4ser profile information.

The G!! also enerates 4ser !ecurity information for mutual authentication. communication inte rity chec" and cipherin . 1ased on this information. the G!! also is responsible to support the call control and session mana ement entities of the different :omains and !ubsystems (defined in section 3.3 and 3.3a) of the operator as shown in fi ure +Aa.
>SS

S .'cri$tion in5or8ation Sh

Location in5or8ation

%S

Gr2S") Gc

(*

S"a MME (S(!

MS( Ser7er

GMS( Ser7er

SGS,

GGS,

.i/ure %(a0 12ample of a Generic 3SS structure and 4asic interfaces The G!! may inte rate hetero eneous information. and enable enhanced features in the core networ" to be offered to the application I services domain. at the same time hidin the hetero eneity. The G!! consists of the followin functionalitiesE A %P multimedia functionality to provide support to control functions of the %M subsystem such as the 2!28. %t is needed to enable subscriber usa e of the %M 2& subsystem services. This %P multimedia functionality is independent of the access networ" used to access the %M 2& subsystem.

3GPP

elease !"

"!

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

A A

The subset of the G60F/42 functionality reDuired by the P! :omain (GP0! and 3P2). The subset of the G60F/42 functionality reDuired by the 2! :omain. if it is desired to enable subscriber access to the 2! :omain or to support roamin to le acy G!MF4MT! 2! :omain networ"s.

The or anisation of the subscriber data is outlined in T! *3.++> P=C. %t also indicates which numbers. addresses and identifiers specified in T! *3.++3 P3C are stored in G!!.

4.1.1.1.1

The >o8e Location +e3i'ter (>L+)

The G60 is shown in the 0eference /rchitecture up to and includin 0elA-. The G60 can be considered a subset of the G!! that holds the followin functionalityE A The functionality reDuired to provide support to P! :omain entities such as the !G!&. MM3 and GG!&. throu h the Gr. !;a. !;dand Gc interfaces and the 3GPP /// !erver for 3P! in case of nonA3GPP access via !B' and for the %AB6/& throu h the :#FGr# interface. %t is needed to enable subscriber access to the P! :omain services. The functionality reDuired to provide support to 2! :omain entities such as the M!2FM!2 server and GM!2FGM!2 server. throu h the 2 and : interfaces. %t is needed to enable subscriber access to the 2! :omain services and to support roamin to le acy G!MF4MT! 2! :omain networ"s.

4.1.1.1.2

The % thentication (entre (% ()

The /u2 is shown in the 0eference /rchitecture up to and includin 0elA-. The /u2 can be considered a subset of the G!! that holds the followin functionality for the 2! :omain and P! :omainE A The /u2 is associated with an G60 and stores an identity "ey for each mobile subscriber re istered with the associated G60. This "ey is used to enerate security data for each mobile subscriberE A A A A data which are used for mutual authentication of the %nternational Mobile !ubscriber %dentity (%M!%) and the networ"O a "ey used to chec" the inte rity of the communication over the radio path between the mobile station and the networ"O a "ey used to cipher communication over the radio path between the mobile station and the networ".

The /u2 communicates only with its associated G60 over a nonAstandardised interface denoted the GAinterface. The G60 reDuests the data needed for authentication and cipherin from the /u2 via the GAinterface. stores them and delivers them to the ?60 and !G!& and MM3 which need them to perform the security functions for a mobile station.

4.1.1.1.3

>SS &o3ica& 5 nction'

This section provides a hi h level and not e'haustive description of G!! functionality.

3GPP

elease !"

""

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

3SS
Mo.i&it9 Mana3e8ent U'er 'ec rit9 in5o. 3eneration U'er 'ec rit9 ' $$ort Ser7ice Pro7i'ionin3 ' $$ort (a&& 2 Se''ion e'ta.&i'h8ent ' $$ort GUP 6ata +e$o'itor9 4)enti5ication han)&in3 Ser7ice a thori?ation ' $$ort %cce'' a thori?ation %$$&ication Ser7ice' S $$ort (%MEL Ser7ice' S $$ort

S=*

3'8S(!

Gr

Gc
GGS,

+$

Sh
S7P Application Server

Si

(*

5S 6omain
GMS( MS( 2 VL+

S")
SGS,

GP S

S"a
1P5
SGS, MME %$$&ication'

9SA S5S

78(SS.

(S(!

78 5N su4system
GUP Ser7er

3GPP %%% Ser7er

.i/ure %$40 3SS lo/ical functions A Mobility Mana ement This function supports the user mobility throu h 2! :omain. P! :omain and %M 2& subsystem. A 2all andFor session establishment support The G!! supports the call andFor session establishment procedures in 2! :omain. P! :omain and %M 2& subsystem. 8or terminatin traffic. it provides information on which call andFor session control entity currently hosts the user. A A 4ser security information eneration The G!! enerates user authentication. inte rity and cipherin data for the 2! and P! :omains and for the %M 2& subsystem. 4ser security support The G!! supports the authentication procedures to access 2! :omain. P! :omain and %M 2& subsystem services by storin the enerated data for authentication. inte rity and cipherin and by providin these data to the appropriate entity in the 2& (i.e. M!2F?60. !G!&. MM3. 3GPP /// !erver or 2!28). A 4ser identification handlin The G!! provides the appropriate relations amon all the identifiers uniDuely determinin the user in the systemE 2! :omain. P! :omain and %M 2& subsystem (e. . %M!% and M!%!:&s for 2! :omainO %M!%. M!%!:&s and %P addresses for P! :omain. private identity and public identities for %M 2& subsystem). A /ccess authorisation The G!! authorises the user for mobile access when reDuested by the M!2F?60. !G!&. MM3. 3GPP /// !erver or 2!28. by chec"in that the user is allowed to roam to that visited networ".

3GPP

elease !"

"3

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

!ervice authorisation support The G!! provides basic authorisation for MT callFsession establishment and service invocation. 1esides. the G!! updates the appropriate servin entities (i.e.. M!2F?60. !G!&. MM3. 3GPP /// !erver. 2!28) with the relevant information related to the services to be provided to the user.

A A

!ervice Provisionin !upport The G!! provides access to the service profile data for use within the 2! :omain. P! :omain andFor %M 2& subsystem. /pplication !ervices and 2/M36 !ervices !upport (for G30/& and 4T0/& access). The G!! communicates with the !%P /pplication !erver and the O!/A!2! to support /pplication !ervices in the %M 2& subsystem. %t communicates with the %MA!!8 to support the 2/M36 !ervices related to the %M 2& subsystem. %t communicates with the sm!28 to support 2/M36 !ervices in the 2! :omain and GP0! P! :omain (for G30/& and 4T0/& access).

3ditor#s &oteE 2/M36 support for G30/&F4T0/& via 3P! (i.e. for !- !G!&) is 88!. A G4P :ata 0epository The G!! supports the stora e of %M 2& !ubsystem user related data. and provides access to these data throu h the 0p reference point as described in T! *3.*-+ P<,C.

4.1.1.2

The Vi'itor Location +e3i'ter (VL+)

/ mobile station roamin in an M!2 area or within a G30/&F4T0/& poolAarea is controlled by a ?isitor 6ocation 0e ister. Bhen a Mobile !tation (M!) enters a new location area it starts a re istration procedure. /n M!2 in char e of that area notices this re istration and transfers to a ?isitor 6ocation 0e ister the identity of the location area where the M! is situated. %f this M! is not yet re istered in the ?60. the ?60 and the G60 e'chan e information to allow the proper handlin of 2! calls involvin the M!. / ?60 may be in char e of one or several M!2 areas. The ?60 contains also the information needed to handle the calls setAup or received by the M!s re istered in its data base (for some supplementary services the ?60 may have to obtain additional information from the G60). The followin elements are includedE A A A A A A A A A the %nternational Mobile !ubscriber %dentity (%M!%)O the Mobile !tation %nternational %!:& number (M!%!:&)O the Mobile !tation 0oamin &umber (M!0&). see T! *3.++3 P3C for allocation principlesO the Temporary Mobile !tation %dentity (TM!%). if applicableO the 6ocal Mobile !tation %dentity (6M!%). if usedO the location area where the mobile station has been re isteredO the identity of the !G!& where the M! has been re istered. Only applicable to P6M&s supportin GP0! and which have a Gs interface between M!2F?60 and !G!&O the last "nown location and the initial location of the M!O the identity of the MM3 where the M! has been re istered. Only applicable to P6M&s supportin 3P2 and 2! 8allbac" and which have a !Gs interface between M!2F?60 and MM3.

The ?60 also contains supplementary service parameters attached to the mobile subscriber and received from the G60. The or anisation of the subscriber data is outlined in T! *3.++> P=C.

3GPP

elease !"

"'

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

4.1.1.3 4.1.1.4

(7oi)) The E@ i$8ent 4)entit9 +e3i'ter (E4+)

The 3Duipment %dentity 0e ister (3%0) in the G!M system is the lo ical entity which is responsible for storin in the networ" the %nternational Mobile 3Duipment %dentities (%M3%s). used in the G30/&F4T0/&F3A4T0/& system. The eDuipment is classified as Qwhite listedQ. Q rey listedQ. Qblac" listedQ or it may be un"nown as specified in T! **.+,; P*C and T! *9.++* P*;C. This functional entity contains one or several databases which store(s) the %M3%s used in the system. The mobile eDuipment may be classified as Qwhite listedQ. Q rey listedQ and Qblac" listedQ and therefore may be stored in three separate lists. /n %M3% may also be un"nown to the 3%0. /n 3%0 shall as a minimum contain a Qwhite listQ (3Duipment classified as Qwhite listedQ). !ee also T! **.+,; P*C on %M3%.

4.1.1.-

SMS Gatewa9 MS( (SMS-GMS()

The !M! Gateway M!2 (!M!AGM!2) acts as an interface between a !hort Messa e !ervice 2entre and the P6M&. to allow short messa es to be delivered to mobile stations from the !ervice 2entre (!2). The choice of which M!2s can act as !M! Gateway M!2s is a networ" operator matter (e. . all M!2s or some desi nated M!2s).

4.1.1."

SMS 4nterworkin3 MS( (SMS-4=MS()

The !M! %nterwor"in M!2 acts as an interface between the P6M& and a !hort Messa e !ervice 2entre (!2) to allow short messa es to be submitted from Mobile !tations to the !2. The choice of which M!2s can act as !M! %nterwor"in M!2s is a networ" operator matter (e. . all M!2s or some desi nated M!2s).

4.1.1.1
The !68E A A A A

S .'cri$tion Locator ! nction (SL!)

%s Dueried by the %A2!28 durin the 0e istration and !ession !etup to et the name of the G!! containin the reDuired subscriber specific data. 8urthermore the !68 is also Dueried by the !A2!28 durin the 0e istration. %s Dueried by the /! in conjunction with the !h interface operation to et the name of the G!! containin the reDuired subscriber specific data. %s Dueried by the 3GPP /// server to et the name of the G!! containin the reDuired subscriber specific data. %s accessed via the :' interface by the 2!28. via the :h interface by the /!. and via the :w interface by the 3GPP /// !erver.

The !68 is not reDuired in a sin le G!! environment. /n e'ample for a sin le G!! environment is a server farm architecture. 4se of !68 is not reDuired when /! are confi uredFmana ed to use preAdefined G!!.

4.1.2 Entitie' o5 the (S )o8ain

4.1.2.1 The Mo.i&e-'er7ice' Switchin3 (entre (MS()

The MobileAservices !witchin 2entre (M!2) constitutes the interface between the radio system and the fi'ed networ"s. The M!2 performs all necessary functions in order to handle the circuit switched services to and from the mobile stations.

3GPP

elease !"

")

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

%n order to obtain radio covera e of a iven eo raphical area. a number of 1!! andFor 0&! are normally reDuiredO i.e. each M!2 would thus have to interface to one or more 1!!(s) andFor 0&!(s). %n addition several M!2s may be reDuired to cover a country. Bhen %ntra :omain 2onnection of 0/& &odes to Multiple 2& &odes is applied. all the M!2s servin a poolAarea share the responsibility to serve the M!s located in the poolAarea. /ll these M!2s interface to all the 1!!(s) andFor 0&!(s) formin the poolAarea. The MobileAservices !witchin 2entre is an e'chan e. which performs all the switchin and si nallin functions for mobile stations located in a eo raphical area desi nated as the M!2 area. Bhen %ntra :omain 2onnection of 0/& &odes to Multiple 2& &odes is applied. one or more M!2s serve a poolAarea. but each individual M! is served by only one out of these M!2s. as described in T! *3.*3; P;=C. The main difference between a M!2 and an e'chan e in a fi'ed networ" is that the M!2 has to ta"e into account the impact of the allocation of radio resources and the mobile nature of the subscribers and has to perform in addition. at least the followin proceduresE A A procedures reDuired for the location re istration (see T! *3.+,* P<C)O procedures reDuired for handover (see T! *3.++9 P;C). Bhen this improves the readability (e. . when dealin with interAreleases handover). the term *GAM!2 can be used to refer to an M!2 0elease 9> or prior. and the term 3GAM!2 can be used to refer to an M!2 0elease 99 or later.

&OT3E

Bhen needed. the M!2 can be implemented in two different entitiesE the M!2 !erver. handlin only si nallin . and the 2!AMGB. handlin user#s data. / M!2 !erver and a 2!AMGB ma"e up the full functionality of a M!2. The 2! fallbac" enabled M!2 supports the followin additional functions accordin to T! *3.*<* P>,CE A A Maintainin !Gs association towards MM3 for 3P!F%M!% attached 43O !upportin !M! procedures accordin to 2! 8allbac".

4.1.2.1.1

MS( Ser7er

The M!2 !erver mainly comprises the call control (22) and mobility control parts of a M!2. The M!2 !erver is responsible for the control of mobile ori inated and mobile terminated 22 2! :omain calls. %t terminates the userAnetwor" si nallin and translates it into the relevant networ" K networ" si nallin . The M!2 !erver also contains a ?60 to hold the mobile subscriber#s service data and 2/M36 related data. The M!2 !erver controls the parts of the call state that pertain to connection control for media channels in a 2!AMGB. /n M!2 !erver which has been enhanced for !0?22 provides the followin functions as needed for support of !0?22 accordin to T! *3.*,; P>3CE A A A A Gandlin the 0elocation Preparation procedure reDuested for the voice component from MM3 via !v interfaceO %nvo"in the session transfer procedure from %M! to 2! O 2oordinatin the 2! Gandover and session transfer proceduresO Gandlin the M/PJ4pdateJ6ocation procedure without it bein tri ered from the 43.

%f a M!2 !erver is enhanced for %M! 2entrali(ed !ervices (as defined in T! *3.*9* P,,+C). it is responsible for the 2! to %M! interwor"in . and it terminates the userAnetwor" si nallin received over the 2! access (/F%u and 3 interface) and translates it into !%P si nallin in %M! and vice versa.

4.1.2.1.2
&OT3E

(irc it Switche) - Me)ia Gatewa9 ! nction ((S-MG=)

%n this document the term Media Gateway 8unction (MGB) is used when there is no need to differentiate between the 2! domain entity and the %P Multimedia 2& !ubsystem entity. Bhen referrin specifically to the 2! domain entity the term 2!AMGB is used. Bhen referrin specifically to the %P Multimedia 2& !ubsystem entity. the term %M!AMGB is used.

3GPP

elease !"

"*

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

This component is P!T&FP6M& transport termination point for a defined networ" and interfaces 4T0/& with the core networ" over %u. / 2!AMGB may terminate bearer channels from a switched circuit networ" and media streams from a pac"et networ" (e. . 0TP streams in an %P networ"). Over %u. the 2!AMGB may support media conversion. bearer control and payload processin (e. . codec. echo canceller. conference brid e) for support of different %u options for 2! services (//6*F/TM based as well as 0TPF4:PF%P based). The 2!AMGBE A A A %nteracts with MG28. M!2 server and GM!2 server for resource control. Owns and handles resources such as echo cancellers etc. May need to have 2odecs.

The 2!AMGB will be provisioned with the necessary resources for supportin 4MT!FG!M transport media. 8urther tailorin (i.e. pac"a es) of the G.*-> P=*C may be reDuired to support additional 2odecs and framin protocols. etc. The 2!AMGB bearer control and payload processin capabilities will also need to support mobile specific functions such as !0&! relocationFhandover and anchorin . %t is e'pected that current G.*-> P=*C standard mechanisms can be applied to enable this.

4.1.2.2

The Gatewa9 MS( (GMS()

%f a networ" deliverin a call to the P6M& cannot interro ate the G60. the call is routed to an M!2. This M!2 will interro ate the appropriate G60 and then route the call to the M!2 where the mobile station is located. The M!2 which performs the routin function to the actual location of the M! is called the Gateway M!2 (GM!2). The acceptance of an interro ation to an G60 is the decision of the operator. The choice of which M!2s can act as Gateway M!2s is for the operator to decide (i.e. all M!2s or some desi nated M!2s). %f the call is a voice roupFbroadcast call. it is routed directly from the GM!2 to the ?1!F?G2! /nchor M!2. based on information (?1!F?G2! call reference) contained in the dialled number (see also T! -3.+;> P-,C and T! -3.+;9 P-*C). 3ditor#s noteE There is a need to consider possibilities that call incomin to the P6M& may be routed to entities other than the GM!2. e. .. for networ"s that do not deploy 2! domain. Bhen needed. the GM!2 can be implemented in two different entitiesE the GM!2 !erver. handlin only si nallin . as defined below. and the 2!AMGB. defined above. / GM!2 !erver and a 2!AMGB ma"e up the full functionality of a GM!2.

4.1.2.2.1

Gatewa9 MS( Ser7er (GMS( Ser7er)

The GM!2 server mainly comprises the call control and mobility control parts of a GM!2.

4.1.2.3

The 4nterworkin3 ! nction (4=!)

The %nterwor"in 8unction (%B8) is a functional entity associated with the M!2. The %B8 provides the functionality necessary to allow interwor"in between a P6M& and the fi'ed networ"s (%!:&. P!T& and P:&s). The functions of the %B8 depend on the services and the type of fi'ed networ". The %B8 is reDuired to convert the protocols used in the P6M& to those used in the appropriate fi'ed networ". The %B8 may have no functionality where the service implementation in the P6M& is directly compatible with that at the fi'ed networ". The interwor"in functions are described in T! *9.++< P3,C.

4.1.3 Entitie' o5 the GP+S PS )o8ain

The 4T0/&FG30/& P!Adomain (or GP0!) !upport &odes (G!&) are the Gateway G!& (GG!&) and the !ervin G!& (!G!&). They constitute the interface between the radio system and the fi'ed networ"s for pac"et switched

3GPP

elease !"

"+

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

services. The G!& performs all necessary functions in order to handle the pac"et transmission to and from the mobile stations.

4.1.3.1

Ser7in3 GP+S S $$ort ,o)e (SGS,)

The location re ister function in the !G!& stores two types of subscriber data needed to handle ori inatin and terminatin pac"et data transferE A subscription informationE A A A A the %M!%O one or more temporary identitiesO (ero or more P:P addresses.

location informationE A A A dependin on the operatin mode of the M!. the cell or the routein area where the M! is re isteredO the ?60 number of the associated ?60 (if the Gs interface is implemented)O the GG!& address of each GG!& for which an active P:P conte't e'ists.

The !G!& .provide support for :irect Tunnel functions as specified in T! *3.+;+ P9aC. The or anisation of the subscriber data in the !G!& is defined in T! *3.++> P=C and T! *3.+;+ P9aC. The procedures for information transfer between the !G!&. the GG!&. the ?60 and the G60 are defined in T! *3.+,; P39C and T! *3.+;+ P9aC. &OT3E Bhen this improves the readability (e. . when dealin with interAreleases handover). the term *GA!G!& can be used to refer to a !G!& 0elease 9> or prior. and the term 3GA!G!& can be used to refer to a !G!& 0elease 99 or later.

The !G!& provides support for !0?22 functions as specified in T! *3.*,; P>3C.

4.1.3.2

Gatewa9 GP+S S $$ort ,o)e (GGS,)

The location re ister function in the GG!& stores subscriber data received from the G60 and the !G!&. There are two types of subscriber data needed to handle ori inatin and terminatin pac"et data transferE A subscription informationE A A A the %M!%O (ero or more P:P addresses.

location informationE A the !G!& address for the !G!& where the M! is re istered.

The or anisation of the subscriber data in the GG!& is defined in T! *3.++> P=C and T! *3.+;+ P9aC. The procedures for information transfer between the GG!&. the !G!& and the G60 are defined in T! *3.+,; P39C and T! *3.+;+ P9aC.

4.1.3.3

Voi)

3GPP

elease !"

",

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

4.1.4 Entitie' o5 the EP( PS 6o8ain

4.1.4.1 MME

MM3 is the control plane entity within 3P! supportin functions as listed below. 8or detailed functional role of MM3. see specifications T! *3.-+, P<;C. T! *3.-+* P<<C and T! 3;.3++ P<>C. Mobility Mana ement. A A A A A A A A A &/! si nallin and securityO %nter 2& node si nallin for mobility between 3GPP access networ"sO Trac"in /rea list mana ementO P:& GB and !ervin GB selectionO !G!& selection for handovers to *G or 3G 3GPP access networ"sO 0oamin O /uthenticationO 1earer mana ement functions includin dedicated bearer establishment. 6awful %nterception of si nallin traffic.

%n order to support 3GPP* access. MM3 supportsE A A A G0P: access node selection and maintenance for handovers to G0P:O Transparent transfer of G0P: si nallin messa es and transfer of status information between 3A4T0/& and G0P: accessO Transparent transfer of 0%M si nallin messa es between 3A4T0/& and G0P: accessO

The procedures for information transfer between the !G!&. the MM3 and the G!! are defined in T! *3.-+, P<;C and T! *3.+;+ P9aC. The 2! fallbac" enabled MM3 supports the followin additional functions accordin to T! *3.*<* P>,CE A A A A A A :erivin a ?60 number and 6/% out of the T/% Maintainin of !Gs association towards M!2F?60 for 3P!F%M!% attached 43 %nitiatin %M!% detach at 3P! detach %nitiatin pa in procedure towards e&ode1 when M!2 pa es the 43 for 2! services !upportin !M! procedures for 2! 8allbac". !upport 2! 8allbac" interface and related functions for ,'0TT 2:M/ access.

Bhen the MM3 supports the interwor"in to 3GPP 2!. the MM3 supports the followin functions as specified in T! *3.*,; P>3CE A A A A A Performin the P! bearer splittin function by separatin the voice P! bearer from the nonAvoice P! bearers. Gandlin the nonAvoice P! bearers handover with the tar et cell as accordin to %nter 0/T handover procedure as defined in T! *3.-+, P<;C. %nitiatin the !0?22 handover procedure for handover of the voice component to the tar et cell. 2oordinatin P! handover and !0?22 handover procedures when both procedures are performed. support interwor"in and !0?22 related functions for ,'0TT 2:M/ access.

3GPP

elease !"

"-

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

4.1.4.2
4.1.4.2.1.

Gatewa9'
Ser7in3 G=

The !ervin GB is the ateway which terminates the interface towards 3A4T0/&. 8or each 43 associated with the 3P!. at a iven point of time. there is a sin le !ervin GB. 8or detailed !AGB functions. see T! *3.-+, P<;C and T! *3.-+* P<<C. 2onnectivity to a GG!& is not supported. The functions of the !ervin GB includeE A A A A A A the local Mobility /nchor point for interAe&ode1 handoverO Mobility anchorin for interA3GPP mobilityO 32MA%:63 mode downlin" pac"et bufferin and initiation of networ" tri ered service reDuest procedureO 6awful %nterceptionO Pac"et routein and forwardin O Transport level pac"et mar"in in the uplin" and the downlin"O /ccountin on user and S2% ranularity for interAoperator char in O A A A A A A / local nonA3GPP anchor for the case of roamin when the nonA3GPP %P accesses connected to the ?P6M&O 3vent reportin (chan e of 0/T. etc.) to the P208O 4plin" and downlin" bearer bindin towards 3GPP accesses as defined in T! *3.*+3 P<3CO 4plin" bearer bindin verification with pac"et droppin of Qmisbehavin 46 trafficQO Mobile /ccess Gateway (M/G) functions if PM%PAbased != or !> is usedO !upport necessary functions in order for enablin GTPFPM%P chainin functions.

4.1.4.2.2

P6, G=

The P:& GB is the ateway which terminates the !Gi interface towards the P:&. %f a 43 is accessin multiple P:&s. there may be more than one P:& GB for that 43. however a mi' of !=F!> connectivity and GnFGp connectivity is not supported for that 43 simultaneously. The P:& GB provides P:& connectivity to both G30/&F4T0/& only 43s and 3A4T0/& capable 43s usin any of 3A4T0/&. G30/& or 4T0/&. The P:& GB provides P:& connectivity to 3A4T0/& capable 43s usin 3A4T0/& only over the !=F!> interface. The P:& GB may also provide P:& connectivity to 43s usin nonA3GPP access networ"s with the procedures defined in T! *3.-+* P<<C. 8or detailed P:& GB functions. see T! *3.-+, P<;C and T! *3.-+* P<<C. P:& GB functions includeE A A A A A A PerAuser based pac"et filterin (by e. . deep pac"et inspection)O 6awful %nterceptionO 43 %P address allocationO Transport level pac"et mar"in in the uplin" and downlin". e. . settin the :iff!erv 2ode Point. based on the S2% of the associated 3P! bearerO 46 and :6 service level char in . atin control. rate enforcement as defined in T! *3.*+3 P<3CO 46 and :6 rate enforcement based on /P&A/M10O

3GPP

elease !"

3%

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

A A

:6 rate enforcement based on the accumulated M10s of the a re ate of !:8s with the same G10 S2% (e. . by rate policin Fshapin )O :G2Pv- (server and client) and :G2Pv; (client and server) functionsO

/dditionally the P:& GB includes the followin functions for the GTPAbased !=F!>F!*aF!*bE A A 46 and :6 bearer bindin as defined in T! *3.*+3 P<3CO 46 bearer bindin verificationO

The P:& GB functions also includes user plane anchor for mobility between 3GPP access and nonA3GPP access. %t supportsE A A A A A / 6M/ function for PM%Pv;. if PM%PAbased != or !>. or if PM%P based !*a or PM%P based !*b is usedO / :!M%Pv; Gome / ent. if !*c is usedO /llocation of G03 "ey. which is used to encapsulate uplin" traffic to the P:& GB on the PM%PAbased !=F!>. or PM%P based !*a or PM%P based !*b interfaceO / M%P?- Gome / ent. if !*a with M%Pv- 8/ 2o/ mode is used. GP0! Tunnellin Protocol for the control plane and the user plane to provide P:& connectivity to 43s usin nonA3GPP accesses. if GTP based !*a or GTP based !*b is used.

4.1.4.2.3

Loca& G= (L-G=)

/ 6ocal GB is a ateway towards the %P networ"s (e. . residentialFenterprise networ"s. %nternet). 8or detailed 6ocal GB functions. see T! *3.-+, P<;C and T! *3.+;+ P9aC.

4.1.4.3
A A A

SGS,

%n addition to the functions described for GP0!. for 3P2 !G!& functions includeE %nter 3P2 node si nallin for mobility between *GF3G and 3A4T0/& 3GPP access networ"sO P:& and !ervin GB selectionE the selection of ! GBFP:& GB by the !G!& is as specified for the MM3O MM3 selection for handovers to 3A4T0/& 3GPP access networ".

8or details. see T! *3.-+, P<;C and T! *3.+;+ P9aC.

4.1.4.4

Tr 'te) an) Untr 'te) ,on-3GPP %cce'' ,etwork

Trusted and 4ntrusted &onA3GPP /ccess &etwor"s are %P access networ"s that use access technolo y whose specification is out of the scope of 3GPP. Bhether a &onA3GPP %P access networ" is Trusted or 4ntrusted is not a characteristic of the access networ". %n nonAroamin scenario it is the GP6M&#s operator decision if a &onA3GPP %P access networ" is used as Trusted or 4ntrusted &onA3GPP /ccess &etwor". %n roamin scenario. the G!!F3GPP /// !erver in GP6M& ma"es the final decision of whether a &onA3GPP %P access networ" is used as Trusted or 4ntrusted nonA3GPP /ccess &etwor". The G!!F3GPP /// !erver may ta"e the ?P6M&#s policy and capability returned from the 3GPP /// Pro'y or roamin a reement into account. 8or details. see T! *3.-+* P<<C.

4.1.4.-

eP6G

The functionality of eP:G includes the followin E

3GPP

elease !"

3!

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

A A A

8unctionality defined for the P:G in T! *3.*3- P;<C for the allocation of a remote %P address as an %P address local to the eP:G which is used as 2o/ when !*c is usedO 8unctionality for transportation of a remote %P address as an %P address specific to a P:& when !*b is usedO 0outin of pac"ets fromFto P:& GB (and fromFto !ervin GB if it is used as local anchor in ?P6M&) toFfrom 43O if GTP based !*b is used. this includes routin of uplin" pac"ets based on the uplin" pac"et filters in the T8Ts assi ned to the !*b bearers of the P:& connectionO 0outin of downlin" pac"ets towards the !Bu instance associated to the P:& connectionO :eAcapsulationF3ncapsulation of pac"ets for %P!ec and. if networ" based mobility (!*b) is used. for GTP or PM%P tunnelsO Mobile /ccess Gateway (M/G) for PM%Pv; if PM%P based !*b is usedO Tunnel authentication and authori(ation (termination of %$3v* si nallin and relay via /// messa es)O 6ocal mobility anchor within untrusted nonA3GPP access networ"s usin MO1%$3 (if needed)O Transport level pac"et mar"in in the uplin"O 3nforcement of So! policies based on information received via /// infrastructureO 6awful %nterception.

A A A A A A A A

8or details. see T! *3.-+* P<<C.

4.1.4."

3GPP %%% Ser7er

The 3GPP /// !erver is located at the GP6M& and provides support for nonA3GPP /ccess users with services li"e /uthentication. /uthorisation and location mana ement services in order to et access to 3P!. %t also contains necessary user related information in order to rant access to nonA3GPP access. %t also coordinates the information needed to support mobility between 3GPP and nonA3GPP accesses such as coordination of P:& GB information. %t interacts with G!! to maintain consistent information for users supportin mobility and service continuity between 3GPP and nonA3GPP access. 8or details. see T! *3.-+* P<<C.

4.1.4.1

3GPP %%% Pro*9

The 3GPP /// Pro'y provides support for roamin nonA3GPP /ccess users in the ?P6M& necessary the /uthentication. /uthorisation and location mana ement services in order to et access to 3P!. %t may also provide roamin related information for support of chainin scenarios as described in T! *3.-+* P<<C. %f an !AGB is needed for nonA3GPP access in the visited networ". the 3GPP /// pro'y selects an !AGB for the 43 durin initial attach or handover attach.

4.1.4.;

%,6S!

The /&:!8 (which is an optional element in the architecture) contains data mana ement and control functionality necessary to provide networ" discovery and selection assistance data as per operators# policy. The /&:!8 is able to initiate data transfer to the 43. based on networ" tri ers. and respond to reDuests from the 43. %t provides functions such as interAsystem mobility policy. access networ" discovery information. The /&:!8 in the subscriber#s home operator networ" may interact with other databases such as the G!! user profile information residin in subscriber#s home operator networ". :etails of such interaction with these databases are not described in this 0elease of the specifications. 8or details on /&:!8. see T! *3.-+* P<<C. &OT3E Bhen the 43 is roamin . how it discovers and interacts with the /&:!8 is not specified in the specification of this release.

3GPP

elease !"

3"

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

4.1.- :or)er Gatewa9 (:G)A

The 1order Gateway (1G) is a ateway between a P6M& supportin GP0!F3P2 and an e'ternal interAP6M& bac"bone networ" used to interconnect with other P6M&s also supportin GP0!F3P2. The role of the 1G is to provide the appropriate level of security to protect the P6M& and its subscribers. The 1G is only needed in P6M&s supportin GP0! and 3P2.

4.2 The %cce'' ,etwork (%,) entitie'

Three different types of access networ" are used by the 2&E the /& include G30/& (also called 1!!). 4T0/& (also called 0&!) and 3A4T0/&. The M!2 (resp. !G!&) can connect to one of the followin /ccess &etwor" type or to both of themE 1!!. 0&!. The MM3 connects to the 3A4T0/&. The access technolo ies offered by the 1!! are described in the -=Aseries of 3GPP specifications. The access technolo ies offered by the 0&! (8::. T::) are described in the *=Aseries of 3GPP specifications. The access technolo ies offered by 3A4T0/& (8::. T::) are described in the 3;Aseries of 3GPP specifications.

4.2.1 The :a'e Station S9'te8 (:SS)

The 1ase !tation !ystem (1!!) is the system of base station eDuipments (transceivers. controllers. etc.) which is viewed by the M!2 throu h a sin le / andFor %uA2! interface as bein the entity responsible for communicatin with Mobile !tations in a certain area. !imilarly. in P6M&s supportin GP0!. the 1!! is viewed by the !G!& throu h a sin le Gb or %uAP! interface. Bhen %ntra :omain 2onnection of 0/& &odes to Multiple 2& &odes is applied. a 1!! may connect to several M!2s by several / andFor %uA2! interfaces. and a 1!! may connect to several !G!&s by several Gb andFor %uAP! interfaces. The functionality for the / interface is described in T! ->.++* P,-C and for the Gb interface in T! *3.+;+ P9aC. The functionality for the %uA2! interface is described in T! *=.-,+ P,-aC and for the %uAP! interface in T! *3.+;+ P9aC. The radio eDuipment of a 1!! may support one or more cells. / 1!! may consist of one or more base stations. Bhere an /bisAinterface is implemented. the 1!! consists of one 1ase !tation 2ontroller (1!2) and one or more 1ase Transceiver !tation (1T!). The split of functions between 1!! and 2& for a %u interface is described in the *=Aseries of 4MT! Technical !pecifications. The split of functions between 1!! and 2& for a /FGb interface is described in the ->Aseries of G!M Technical !pecifications. The split of functions between 1!! and 2& for a %u interface is described in the *=Aseries of 4MT! Technical !pecifications. &OT3E The mobile station shall operate usin only the followin modesE

a A / Gb mode. e. . for preA0elease - terminals. or for 0elease - terminals when connected to a 1!! with no %u interface towards the 2ore &etwor". b Iu mode (i.e. %uA2! and %uAP! ). e. . for 0elease - terminals when connected to a 1!! with %u interfaces towards the 2ore &etwor". &o other modes (e. . /F%uAP! or %uA2!FGb) shall be allowed. !ee also T! -3.+=, P3;C.

4.2.1.1

:a'e Station (ontro&&er (:S()

/ 1ase !tation 2ontroller (1!2) is a networ" component in the P6M& with the functions for control of one or more 1T!.

4.2.1.2

:a'e Tran'cei7er Station (:TS)

/ 1ase Transceiver !tation (1T!) is a networ" component which serves one cell.

3GPP

elease !"

33

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

4.2.2 The +a)io ,etwork S9'te8 (+,S)

The 0adio &etwor" !ystem (0&!) is the system of base station eDuipments (transceivers. controllers. etc.) which is viewed by the M!2 throu h a sin le %uAinterface as bein the entity responsible for communicatin with Mobile !tations in a certain area. !imilarly. in P6M&s supportin GP0!. the 0&! is viewed by the !G!& throu h a sin le %uA P! interface. Bhen %ntra :omain 2onnection of 0/& &odes to Multiple 2& &odes is applied. an 0&! may connect to several M!2s by several %uA2! interfaces. and an 0&! may connect to several !G!&s by several %uAP! interfaces. The functionality for the %uA2! interface is described in T! *=.-,+ P,-aC and for the %uAP! interface in T! *3.+;+ P9aC. The radio eDuipment of a 0&! may support one or more cells. / 0&! may consist of one or more base stations. The 0&! consists of one 0adio &etwor" 2ontroller (0&2) and one or more &ode 1. The split of functions between 0&! and 2& is described in the *=Aseries of 4MT! Technical !pecifications.

4.2.2.1

+a)io ,etwork (ontro&&er (+,()

/ 0adio &etwor" 2ontroller (0&2) is a networ" component in the P6M& with the functions for control of one or more &ode 1.

4.2.2.2

,o)e :

/ &ode 1 is a lo ical networ" component which serves one or more 4T0/& cells.

4.2.3 %cce'' ,etwork e&e8ent' 5or E-UT+%,

4.2.3.1 E-UT+%, ,o)e : (e,:)

/n e&1 is a lo ical networ" component which serves one or more 3A4T0/& cells.

4.2.3.2

E7o&7e) UT+%,

The 3volved 4T0/& (3A4T0/&) consists of e&1s. providin the 3A4T0/ user plane (P:2PF062FM/2FPGT) and control plane (002) protocol terminations towards the 43. The e&1s can be interconnected with each other by means of the H* interface. The e&1s are connected by means of the !, interface to the 3P2 (3volved Pac"et 2ore). more specifically to the MM3 (Mobility Mana ement 3ntity) by means of the !,AMM3 and to the !ervin Gateway (!AGB) by means of the !,A4 interface. The !, interface supports a manyAtoAmany relation between MM3s F !ervin Gateways and e&1s. The split of functions between e&1 and 3P2 is described in the specifications T! *3.-+, P<;C. T! 3;.3++ P<>C and T! 3;.-+, P<9C. The architecture defined usin 3A4T0/& can be further described as followsE The 3A4T0/& consists of set of e&1s connected to the 3P2 throu h the !, interface. /n e&1 can support 8:: mode. T:: mode or dual mode operation.

4.3 The Mo.i&e Station (MS)

The mobile station consists of the physical eDuipment used by a P6M& subscriberO it comprises the Mobile 3Duipment (M3) and the !ubscriber %dentity Module (!%M). called 4MT! !ubscriber %dentity Module (4!%M) for 0elease 99 and followin . The M3 comprises the Mobile Termination (MT) which. dependin on the application and services. may support various combinations of Terminal /dapter (T/) and Terminal 3Duipment (T3) functional roups. These functional roups are described in T! *-.++* P,*C.

4.4 U'er E@ i$8ent (UE)

The 4ser 3Duipment /llows a user access to networ" services. 8or the purpose of 3GPP specifications the interface between the 43 and the networ" is the radio interface. / 4ser 3Duipment can be subdivided into a number of domains. the domains bein separated by reference points. 2urrently the 4ser 3Duipment is subdivided into the 4%22 domain

3GPP

elease !"

3'

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

and the M3 :omain. The M3 :omain can further be subdivided into one or more Mobile Termination (MT) and Terminal 3Duipment (T3) components showin the connectivity between multiple functional roups.

4a

The '$eci5ic entitie' o5 the 3GPP '9'te8

The entities presented in this clause are dedicated to the provisionin of a iven (set of) service(s). The fact that they are implemented or not in a iven P6M& should have limited impact on all the other entities of the P6M&. /ll the specific entities defined so far are located in the 2ore &etwor".

4a.1 The Gro $ (a&& +e3i'ter (G(+) entit9

The Group 2all 0e ister (G20) is a re ister holdin information about ?G2! or ?1! calls. the voice roup or broadcast call attributes. respectively. ?oice roup or broadcast call attributes are defined for a specific voice roup or broadcast call reference and include the data reDuired to confi ure the conference brid e for a ?G2! or ?1! call and other call related attributes. The Group 2all 0e ister (G20) shall hold for a related M!2 area for each roup %: and cell from which ?oice Group 2all !ervice (?G2!) or ?oice 1roadcast !ervice (?1!) calls can be established by mobile stations the voice roup call reference or voice broadcast call reference to be used for a ?G2! or ?1! call to be established and an indication whether the ori inatin M!2 is the M!2 responsible for that call. %f the ori inatin M!2 is not responsible for that call. the G20 shall hold the routin information identifyin the M!2 responsible for that call. / G20 may be in char e of one or several M!2. 3ach M!2 involved in a voice roup or broadcast call reDuests its proper voice roup or broadcast call attributes from its related G20 by use of the voice roup or broadcast call reference. The contents of each list related to reDuests of the M!2 responsible for a voice roup or broadcast call is as followsE A A A A A A A A a list of cells inside the M!2 area of the reDuestin M!2 into which the call is to be sent (part of the roup call area)O a list of other M!2s into which the call is to be sentO a list of identities of dispatchers to which a dedicated lin" is to be establishedO a list of identities of dispatchers which are allowed to initiate the voice roup or broadcast callO a list of identities of dispatchers which are allowed to terminate the voice roup or broadcast callO the len th of time over which no activity is detected before the voice roup call is automatically terminatedO the default priority level related to the voice roup or broadcast call if the eM6PP supplementary service appliesO a fla indicatin if ac"nowled ements are reDuired for this voice roup or broadcast call.

The contents of each list related to reDuests of an M!2 not responsible for a voice roup or broadcast call is as followsE A a list of cells inside the M!2 area of the reDuestin M!2 into which the call is to be sent (part of the roup call area).

More information is provided in T! -3.+;> P-,C and T! -3.+;9 P-*C.

3GPP

elease !"

3)

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

4a.2 (7oi)) 4a.3 The Location Ser7ice' (L(S) entitie'

This section describes the 6ocation !ervices entities found in the 2ore &etwor" and 0adio /ccess &etwor" that support positionin methods for the 43FM!. 8or further details on 62! in 3A4T0/&. 4MT! and G!M from system and core networ" point view. see T! *3.*<, P=;C. 8or further details on 62! in 4T0/&. see T! *=.3+= P,+bC. 8or further details on 62! in G30/&. see T! -3.+=9 P,+dC. 8or further details on userAplane 62! in 3A4T0/&. see OM/ !4P6 P>+C. 8or further details on control plane 62! for 3A4T0/& see T! 3;.3+= P,**C.

4a.3.1 Location Ser7ice' (L(S) entitie' in +%,

The 0/& (3A4T0/&. 4T0/& and G30/&) supports one or more 43FM! positionin methods to calculate the eo raphical position of the 43FM! and responds to the 43FM! location reDuest received from the 2&. 8or 4T0/& and G30/&. the 0/& may broadcast 62! assistance data to 43sFM!s under its covera e. %n case this assistance data is ciphered. the cipherin "ey is provided by the 2& to the 43FM!. To support 43 positionin methods. the 0/& is made of several entities li"eE BSC/SRNC: the 1!2 for G30/& and !0&2 for 4T0/& receive authenticated location reDuests from the 2&E A %n 4T0/&. the !0&2 coAordinates the positionin reDuests ta"in into account their priority and it selects the positionin method to fulfil the reDuested accuracy. %t interfaces. when necessary. with the 20&2 which mainly mana es resources allocated to 43 positionin operations and reDuests 43 Positionin related measurements from its associated &ode 1s and 6M4s. %n G30/&. the 1!2 passes the location reDuest to the !M62.

SMLC: A The !ervin Mobile 6ocation 2entre (!M62) function can be part of the 0&2 or be a !/! (!tandA/lone !M62) for 4T0/&. The !M62 function can be part of the 1!2 or be in a separate !M62 server for G30/&. %n 4T0/&. the !M62 function provides assistance data to the 0&2 and acts as a location calculation server if the location estimates are not to be calculated in the 0&2. %n G30/&. the !M62 function coAordinates the positionin reDuest. schedules resources reDuired to perform positionin of a mobile. and calculates the final location estimate and accuracy. The !M62 may control a number of 6M4s.

A A

LMU: The 6ocation Measurement 4nit (6M4) entity ma"es measurements for one or more positionin methods. Node BE &ode 1 is a networ" element of 4T0/& that may provide measurement results for position estimation and ma"es measurements of radio si nals. eNodeB: The e&ode 1 is a networ" element of 3A4T0/& that may provide measurement results for position estimation and ma"es measurements of radio si nals for a tar et 43 and communicates these measurements to an 3A!M62. CBC: The 2ell 1roadcast 2entre. in G30/&. the !M62 function may interface a 212 in order to broadcast assistance data usin e'istin cell broadcast capabilities. 8or detail on 6ocation services. entities and interfaces provided by 3A4T0/&. see T! 3;.3+= P,**C.

3GPP

elease !"

3*

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

8or detail on 6ocation services. entities and interfaces provided by 4T0/&. see T! *=.3+= P,+bC. 8or detail on 6ocation services. entities and interfaces provided by G30/&. see T! -3.+=9 P,+dC.

4a.3.2 Gatewa9 Mo.i&e Location (entre (GML()

The Gateway Mobile 6ocation 2entre (GM62) is the first node an e'ternal 6ocation /pplication accesses in the G!M P6M&. The GM62 performs re istration authori(ation and reDuests routin information from the G60FG!!. There may be more than one GM62 in a P6M&.

4a.3.3 Location Mea' re8ent Unit (LMU)

/n 6M4 ma"es radio measurements to support one or more positionin methods. Two types of 6M4 are definedE A A Type / 6M4E Type 1 6M4E accessed over the normal G!M air interfaceO accessed over the base station to controller interface (/bis in G!M and %ub in 4MT!).

/ type / 6M4 is accessed e'clusively over the G!M air interface (4m interface)E there is no wired connection to any other networ" element. %n G!M. a type / 6M4 has a servin 1T! and 1!2 that provide si nallin access to a controllin !M62. Bith an &!! based !M62. a type / 6M4 also has a servin M!2 and ?60 and a subscription profile in an G60. / type / 6M4 always has a uniDue %M!% and supports all radio resource and mobility mana ement functions of the G!M air interface that are necessary to support si nallin usin an !:22G to the !M62. / type / 6M4 supports those connection mana ement functions necessary to support 62! si nallin transactions with the !M62 and may support certain call control functions of to support si nallin to an !M62 usin a circuit switched data connection. %n 4T0/&. a type / 6M4 has si nallin access to the !0&2. Type / 6M4 is not supported in 4MT! release ,999. %n G!M. a Type 1 6M4 is accessed over the /bis interface from a 1!2. The 6M4 may be either a standalone networ" element addressed usin some pseudoAcell %: or connected to or inte rated in a 1T!. !i nallin to a Type 1 6M4 is by means of messa es routed throu h the controllin 1!2 for a 1!! based !M62 or messa es routed throu h a controllin 1!2 and M!2 for an &!! based !M62. %n 4T0/&. a Type 1 6M4 is accessed over the %ub interface from an 0&2. The 6M4 may be either a standalone networ" element addressed usin some pseudoAcell %: or connected to or inte rated in a &ode 1.

4a.3.4 E7o&7e) Ser7in3 Mo.i&e Location (entre (E-SML()

8or 3A4T0/&. the 3volved !ervin Mobile 6ocation 2entre (3A!M62) is a server in the core networ". The 3A!M62 mana es the support of different location services for tar et 43s. includin positionin of 43s and delivery of assistance data to 43s. The 3A!M62 may interact with the servin e&ode1 for a tar et 43 in order to obtain position measurements for the 43. includin uplin" measurements made by the e&ode1 and downlin" measurements made by the 43 that were provided to the e&ode1 as part of other functions such as for support of handover. The 3A!M62 may interact with a tar et 43 in order to deliver assistance data if reDuested for a particular location service. to obtain a location estimate. or location related measurements. if that was reDuested. 8or positionin of a tar et 43. the 3A!M62 decides on the position methods to be used. based on factors that may include the 62! 2lient type. the reDuired So!. 43 positionin capabilities. and e&ode 1 positionin capabilities. The 3A!M62 then invo"es these positionin methods in the 43 andFor servin e&ode 1. The positionin methods may yield a location estimate for 43Abased position methods andFor positionin measurements for 43Aassisted and networ"A based position methods. The 3A!M62 may combine all the received results and determine a sin le location estimate for the tar et 43 (hybrid positionin ). /dditional information li"e accuracy of the location estimate and velocity may also be determined.

3GPP

elease !"

3+

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

4a.4 (%MEL entitie'

The entities of this clause support the 2/M36 feature (2ustomised /pplications for Mobile networ" 3nhanced 6o ic). This feature provides the mechanisms to support services consistently independently of the servin networ". as described in T! **.+<> P*cC. The followin definitions are e'tracted from T! *3.+<> P,+cC. which completely specifies 2/M36 sta e *.

4a.4.1 GSM Ser7ice (ontro& ! nction (3'8S(!)

/ functional entity that contains the 2/M36 service lo ic to implement Operator !pecific !ervice. %t interfaces with the sm!!8. the sm!08 and the G60.

4a.4.2 GSM Ser7ice Switchin3 ! nction (3'8SS!)

/ functional entity that interfaces the M!2FGM!2 to the sm!28. The concept of the sm!!8 is derived from the %& !!8. but uses different tri erin mechanisms because of the nature of the mobile networ".

4a.4.3 GSM S$ecia&i'e) +e'o rce ! nction (3'8S+!)

/ functional entity which provides various speciali(ed resources. %t interfaces with the sm!28 and with the M!2. This entity is defined in %T4AT S.,*,- P,,C with variations defined in T! *3.+<> P,+cC.

4a.4.4 GP+S Ser7ice Switchin3 ! nction (3$r'SS!)

/ functional entity that interfaces the !G!& to the sm!28. The concept of the prs!!8 is derived from the %& !!8. but uses different tri erin mechanisms because of the nature of the mobile networ".

4a.- (:S-'$eci5ic entitie'

The cell broadcast service (21!) is a Teleservice which enables an %nformation Provider to submit short messa es for broadcastin to a specified area within the P6M&. T! *3.+-, P>C contains the technical reali(ation of the service.

4a.-.1 (e&& :roa)ca't (entre ((:()

The 212 shall be responsible for the mana ement of 21! messa es and for determinin the 21! delivery parameters of the 1!!F0&!. The 212 may be connected to several 1!2sF0&2s. The 212 is re arded to be inte rated as a node into the core networ". &OT3E Bhether it should be possible that an 0&2 is connected to at least two 212s at the same time (the QnormalQ one as in G!M and a second one for 62!) is for further study and depends on the solution ta"en for 62!.

4a." , 8.er Porta.i&it9 S$eci5ic entitie'

Two different solutions are defined to support &umber Portability. The first one is an %& based solution and is described in the ne't clause. The second one is a Q!i nallin 0elayQ based solution described in ne't but one clause. 8or details on M&P see T! *3.+;; P-+C.

4a.".1 4,-.a'e) 'o& tion/ , 8.er Porta.i&it9 6ata.a'e (,P6:)

The &umber Portability :atabase (&P:1) is the central element of the %& based solution for Mobile &umber Portability (M&P). M&P is the ability for a mobile subscriber to chan e the G!M subscription networ" within a portability cluster (e. . a country) whilst retainin hisFher ori inal M!%!:& or M!%!:&s.

3GPP

elease !"

3,

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

The &P:1 stores the table of correspondence between M!%!:&s and !ubscription networ"s. 4pon reDuest of the ( ateway or visited) M!2. the &P:1 retrieves from the M!%!:& the 0outin &umber pointin out the !ubscription networ".

4a.".2 Si3na&&in3 +e&a9-.a'e) 'o& tion/ Mo.i&e , 8.er Porta.i&it92Si3na&&in3 +e&a9 5 nction (M,P-S+!)
The M&PA!i nallin 0elay 8unction (M&PA!08) is the central element of the !i nallin 0elay based solution for Mobile &umber Portability. The M&PA!08 obtains the routin information from a &P database to identify the subscription networ" associated with a particular national M!%!:&. 4pon reDuest from ateway M!2. the M&PA!08 may perform one of the followin actionsE ,. the M&PA!08 will reply bac" to the GM!2 with the necessary routin information to route the callO *. the messa e is relayed to the G60O 3. the messa e is relayed to M&PA!08 in the subscription networ". 8or nonAcall related si nallin (e. . delivery of !M!). only cases * and 3 are applicable.

4a.1 4P M &ti8e)ia (4M) (ore ,etwork ((,) S .'9'te8 entitie'

4a.1.1 (a&& Se''ion (ontro& ! nction ((S(!)
The 2!28 can act as Pro'y 2!28 (PA2!28). !ervin 2!28 (!A2!28). 3mer ency 2!28 (3A2!28). or %nterro atin 2!28 (%A2!28). The PA2!28 is the first contact point for the 43 within the %M subsystem (%M!)O the !A2!28 actually handles the session states in the networ"O the 3A2!28 handles certain aspects of emer ency sessions such as routin an emer ency reDuest to the correct emer ency centre or P!/PO the %A2!28 is mainly the contact point within an operator#s networ" for all %M! connections destined to a subscriber of that networ" operator. or a roamin subscriber currently located within that networ" operator#s service area. 8urther definitions of the PA. !A and %A2!28 are provided in T! *3.**> P3-C. 8urther definitions of the 3A2!28 is provided in T! *3.,;< P<-C.

4a.1.2 Me)ia Gatewa9 (ontro& ! nction (MG(!)

The MG28E A A A A A 2ontrols the parts of the call state that pertain to connection control for media channels in an %M!AMGB. 2ommunicates with 2!28. 1G28. and circuit switched networ" entities. :etermines the ne't hop dependin on the routin number for incomin calls from le acy networ"s. Performs protocol conversion between %!4PFT2/PF!%PA% and the %M subsystem call control protocols. Out of band information received in MG28 may be forwarded to 2!28F%M!AMGB.

4a.1.3 4P M &ti8e)ia S .'9'te8 - Me)ia Gatewa9 ! nction (4MS-MG=)

&oteE %n this document the term Media Gateway 8unction (MGB) is used when there is no need to differentiate between the 2! domain entity and the %P Multimedia 2& !ubsystem entity. Bhen referrin specifically to the 2! domain entity. the term 2!AMGB is used. Bhen referrin specifically to the %P Multimedia 2& !ubsystem entity. the term %M!AMGB is used. / %M!AMGB may terminate bearer channels from a switched circuit networ" and media streams from a pac"et networ" (e. .. 0TP streams in an %P networ"). The %M!AMGB may support media conversion. bearer control and payload processin (e. . codec. echo canceller. conference brid e). itE A %nteracts with the MG28 for resource control.

3GPP

elease !"

3-

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

A A

Owns and handles resources such as echo cancellers etc. May need to have 2odecs.

The %M!AMGB will be provisioned with the necessary resources for supportin 4MT!FG!M transport media. 8urther tailorin (i.e. pac"a es) of the G.*-> P=*C may be reDuired to support additional 2odecs and framin protocols. etc.

4a.1.4 M &ti8e)ia +e'o rce ! nction (ontro&&er (M+!()

The M082E A A A 2ontrols the media stream resources in the M08P. %nterprets information comin from an /! and !A2!28 (e. . session identifier) and control M08P accordin ly. Generates 2:0s .

4a.1.4a M &ti8e)ia +e'o rce ! nction Proce''or (M+!P)

The M08PE A A A A A A 2ontrols bearers on the Mb reference point. Provides resources to be controlled by the M082. Mi'es incomin media streams (e. . for multiple parties). !ources media streams (for multimedia announcements). Processes media streams (e. . audio transcodin . media analysis). 8loor 2ontrol (i.e. mana e access ri hts to shared resources in a conferencin environment).

4a.1.4. Me)ia +e'o rce :roker (M+:)

The M01 supports the sharin of a pool of hetero eneous M08 resources by multiple hetero eneous applications. M01 assi ns (and later releases) specific suitable M08 resources to calls as reDuested by the consumin applications. based on M08 attributes specified by the applications as well as other criteria. The M01 may ta"e the followin "inds of information into account when assi nin M08 resources to an applicationE A A A A A the specific characteristics of the media resources reDuired for the call or callsO the identity of the applicationO rules for allocatin M08 resources across different applicationsO perAapplication or perAsubscriber !6/ or So! criteriaO and capacity models of particular M08 resources.

4a.1.- Voi)

4a.1." :reako t Gatewa9 (ontro& ! nction (:G(!)

The 1rea"out Gateway control function (1G28) determines the ne't hop for routin the !%P messa e. This determination may be based on information received in the si nallin protocol. administrative information. andFor database access. 8or P!T& F2! :omain terminations. the 1G28 determines the networ" in which P!T&F2! :omain brea"out is to occur and A within the networ" where the brea"out is to occur A selects the MG28. :etails are described in T! *3.**> P3-C.

3GPP

elease !"

'%

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

4a.1.1 %$$&ication Ser7er (%S)

/n /pplication !erver (/!) i.e.. !%P /pplication !erver. O!/ /pplication !erver. or 2/M36 %MA!!8. offers value added %M services and resides either in the user#s home networ" or in a third party location. The third party could be a networ" or simply a standAalone /!. &OT3 ,E The O!/ /pplication !erver does not directly interact with the %M! networ" entities but throu h the O!/ !ervice 2apability !ervers (O!/ !2!As). 8urther information on O!/ is provided in T! **.,*< P-C. &OT3 *E / !%P /pplication !erver specified within 3GPP that supports %M! reference points (e. . %!2. !h. 4t). in support of an application. is considered as part of the %M 2& subsystem. 3'amples of such /!s are !22 /! and T/!. The /! (!%P /pplication !erver andFor the O!/ !ervice 2apability !erver andFor %MA!!8) can communicate with the G!!. The !h and !i interfaces are used for this purpose. The !ervin A2!28 to /! interface is used to provide services residin in an /!. Two cases were identifiedE A A !ervin A2!28 to an /! in Gome &etwor". !ervin A2!28 to an /! in a trusted 3'ternal &etwor" (e. .. Third Party or ?isited). The !A2!28 does not provide authentication and security functionality for secure direct third party access to the %M !ubsystem. The O!/ framewor" provides a standardi(ed way for third party access to the %M !ubsystem.

The %nterro atin A2!28 to /! interface is used to forward !%P reDuests destined to a Public !ervice %dentity hosted by the /! directly to that /!. The /! to M082 interfaces areE A A Mr. used for session controlO 2r. used for media control.

The /! to M01 interface (0c) is used by the /! to reDuest that M08 resources with certain characteristics be assi ned to a call. /n /pplication !erver may influence and impact the !%P session on behalf of the services supported by the operator#s networ". /n /! may host and e'ecute services.

4a.1.; 4nterconnection :or)er (ontro& ! nction (4:(!)

/n %128 provides application specific functions at the !%PF!:P protocol layer in order to perform interconnection between two operator domains. %t enables communication between %Pv; and %Pv- !%P applications. networ" topolo y hidin . controllin transport plane functions. screenin of !%P si nallin information. selectin the appropriate si nallin interconnect and eneration of char in data records. :etails are described in T! *3.**> P3-C.

4a.1.# Tran'ition Gatewa9 (TrG=)

/ TrGB is located within the media path and controlled by an %128. %t provides functions li"e networ" addressFport translation and %Pv-F%Pv; protocol translation. :etails are described in T! *3.**> P3-C.

4a.1.10 Location +etrie7a& ! nction (L+!)

The 608 retrieves location information for the 43 includin . where reDuired. interim location information. initial location and updated location information. The 608 may interact with a 0outin :etermination 8unction (0:8) in order to obtain routin information. The 608 may interact with a GM62 or other types of location server functions in order to obtain location information. 8urther definitions of the 608 is provided in T! *3.,;< P<-C.

3GPP

elease !"

'!

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

4a.1.11 Ser7ice (entra&i?ation an) (ontin it9 %$$&ication Ser7er (S(( %S)
The !22 /! is an %M! /pplication that can provide functionality reDuired to enable %M! 2entrali(ed !ervices as defined in T! *3.*9* P,,+C. and can provide %M!Abased mechanisms for enablin service continuity of multimedia sessions as defined in T! *3.*3< P,,,C.

4a.1.11a E8er3enc9 %cce'' Tran'5er ! nction (E%T!)

The 3/T8 provides %M!Abased mechanisms for enablin service continuity of %M! emer ency sessions. %t is a function in the servin (visited if roamin ) %M! networ". providin the procedures for %M! emer ency session anchorin and P! to 2! access transfer as defined in T! *3.*3< P,,,C.

4a.1.12 %cce'' Tran'5er (ontro& ! nction (%T(!)

The /T28 is a function in the servin (visited if roamin ) %M! networ". %t enables !0?22 !ession Transfer mechanisms in the servin networ" for a 43. The !22 /! can provide !ession Transfer mechanisms in the servin networ". if an /T28 is present in the !%P re istration path of the 43. as defined in T! *3.*3< P,,,C.

4a.1.13 %cce'' Tran'5er Gatewa9 (%TG=)

The /TGB is a media function in the servin (visited if roamin ) %M! networ". %t may anchor the media for enhanced !0?22 procedure as defined in T! *3.*3< P,,,C.

4a.; Si3na&&in3 Gatewa9 ! nction (SG=)

The !GB performs the si nallin conversion (both ways) at transport level between the !!< based transport of si nallin used in preA0elA- networ"s. and the %P based transport of si nallin possibly used in postA099 networ"s (i.e. between !i tran !2TPF%P and !!< MTP). The !GB does not interpret the application layer (e. . M/P. 2/P. 1%22. %!4P) messa es but may have to interpret the underlyin !22P or !2TP layer to ensure proper routin of the si nallin .

4a.# G&o.a& Te*t Te&e$hon9 S$eci5ic entitie'

%nterwor"in between cellular te't modem (2TM) and te't telephony standards (e. . ?.,>) used in e'ternal networ"s can be supported by three methodsE A 0outin calls throu h a 2TM !pecial resource function (2TMA!08) in the core networ". The 2TMA!08 is lin"ed in to the call path via 2/M36 procedures. :ependin on operator confi uration the 2TMA!08 may also be lin"ed in to the call path for 3mer ency calls. / 2TM F Te't telephone convertin function included alon the speech call path selected by the networ" after an indication from the terminal that 2TM is reDuired. / 2TM F Te't telephone convertin function included in all speech call paths.

A A

8urther information of the support for te't telephony is found in T! *3.**; P3<C. 8or further details of 2TM. see T! *;.**; P3>C.

4a.10 Sec rit9 Gatewa9 (SEG)

The 3GPP system and its networ" domains shall be lo ically and physically divided into security domains in order to protect %P based control plane si nallin . These security domains typically coincide with operator borders. The interface between different security domains is protected by !ecurity Gateways (!3Gs). The !3Gs are responsible for enforcin the security policy of a %P security domain towards other !3Gs in the destination %P security domain. /ll &:!F%P traffic shall pass throu h a !3G before enterin or leavin a security domain. 8or further details of !3G. see T! 33.*,+ P;-C.

3GPP

elease !"

'"

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

4a.11 %$$&ication ! nction (%!)

The /pplication 8unction (/8) is an element offerin applications that reDuire the control of %P bearer resources or the control of flow based bearer char in . The /8 is capable of communicatin with the P208 to transfer dynamic So!A related service information andFor dynamic char in Arelated service information. One e'ample of an /8 is the PA2!28 of the %M 2& subsystem.

4a.12 Voi) 4a.13 3GPP2=L%, 4nterworkin3 entitie'

4a.13.1 =L%, UE
/ B6/& 43 is the 4ser 3Duipment usin a 4%22 card utili(ed by a 3GPP subscriber to access the B6/& networ" for 3GPP interwor"in purpose.

4a.13.2 3GPP %%% Pro*9

The 3GPP /// Pro'y in case of %AB6/& access as specified in T! *3.*3- P;<C represents a /// pro'yin and filterin function and resides in the visited 3GPP networ". %t is involved in access and service authentication and authori(ation procedures of a B6/& 43.

4a.13.3 3GPP %%% Ser7er

The 3GPP /// server resides in the 3GPP networ" and in case of %AB6/& access as specified in T! *3.*3- P;<C is responsible for access and service authentication and authori(ation of a B6/& 43.

4a.13.4 =L%, %cce'' Gatewa9 (=%G)

The B6/& access ateway is a ateway between B6/& and 3GPP networ". %n the roamin case it resides in the visited 3GPP networ". otherwise in the home 3GPP networ". %t provides filterin . policin and char in functionality for the traffic between B6/& 43 and 3GPP networ".

4a.13.- Packet 6ata Gatewa9 (P6G)

The Pac"et :ata Gateway provides access to P! based services for a B6/& 43. %t resides either in the home (for access to home services) or in the visited 3GPP networ" (for access to local services).

4a.13." >o8e %3ent (>%)

The G/ provides control and mobility function for service continuity between 3GPP B6/& %nterwor"in system and 3GPP !ystems. The G/ terminates the GGi reference point towards the P:& as defined in T! *3.3*< P,,*C.

4a.14 M &ti8e)ia :roa)ca't M &tica't Ser7ice (M:MS) '$eci5ic entitie'

4a.14.1 Genera&
The Multimedia 1roadcast Multicast !ervice (M1M!) is a pointAtoAmultipoint service in which data is transmitted from a sin le source entity to multiple recipients. T! *3.*-; P<+C contains the technical reali(ation of the service.

3GPP

elease !"

'3

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

4a.14.2 :roa)ca't-M &tica't Ser7ice (entre (:M-S()

The 1roadcastAMulticast !ervice 2entre provides functions for M1M! user service provisionin and delivery. %t may serve as an entry point for content provider M1M! transmissions. used to authorise and initiate M1M! 1earer !ervices within the P6M& and can be used to schedule and deliver M1M! transmissions.

4a.14.3 M:MS-G=
The M1M!AGB provides functions in the 3P! for controllin M1M! session initiationFmodificationFtermination by the M1M! 4ser !ervice and for providin delivery of %P Multicast data rams from the !GiAmb reference point to downstream nodes in the M1M! !ervice /rea with a specified Duality of service.

4a.14.4 M &ti-ce&&28 &tica't (oor)ination Entit9 (M(E)

The M23 is a functional entity providin functions for admission control and allocation of radio resources by 3A4T0/& and for M1M! session control. !ee T! 3;.3++ P<>C.

4a.1- Voi) 4a.1" GUP Ser7er

The G4P !erver is a functional entity providin a sin le point of access to the Generic 4ser Profile data of a particular subscriber. The architecture does not specify or limit the physical location of the G4P !erver enablin fle'ibility in the implementations. 8or further details of the G4P !erver. see T! *3.*-+ P<,C.

4a.11 Po&ic9 an) (har3in3 + &e' ! nction (P(+!)

The Policy and 2har in 0ules 8unction (P208) acts as a policy decision point for policy and char in control of service data flowsFapplications and %P bearer resources. The P208 selects and provides the applicable policy and char in control decision to the P238 and. if applicable. application detection and control decision to the T:8 or P238 with application detection and control feature. Bhen the G'' interface applies. the P208 maintains the correlation between the GB control session over G'' interface and the %PA2/& session over G'. The P208 also acts as an information e'chan e relay between 11308 and P238 to forward event tri ers. which can#t be transferred directly. Bhen the !d interface applies. the P208 maintains the correlation between the %PA2/& session and the T:8 session. 3vents subscribed by the T:8 are reported by the P208. Bhen !9a interface applies. the P208 provides to the 1P28 the 43FG(e)&1 local %P address and 4:P port number. the So! rules and P22 rules over !9a interface. P208 maintains the correlation between the GB control session over !9a interface and the %PA2/& session over G' interface (if %PA2/& session over G' interface is available). Bhen !,= interface applies. the P208 provides dynamic So! control policies to the 1P28 for the purpose of allocation of So! resources in the 8i'ed 1roadband /ccess &etwor" for G&1 2! traffic. P208 is the policy and char in control element. P208 functions are described in more detail in T! *3.*+3 P<3C. %n nonAroamin scenario. there is only a sin le P208 in the GP6M& associated with one 43#s %PA2/& session. %n a roamin scenario with local brea"out of traffic andFor when a G'' interface applies there are two P208s associated with one 43#s %PA2/& sessionE A A GAP208 that resides within the GAP6M&O ?AP208 that resides within the ?AP6M&.

/ sin le lo ical P208 entity may be deployed by means of multiple and separately addressable P208s in the P6M&. %n this case. the P208 discovery and selection is enabled by :iameter 0outin / ency (:0/).

3GPP

elease !"

''

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

4a.1; Po&ic9 an) (har3in3 En5orce8ent ! nction (P(E!)

The Policy and 2har in 3nforcement 8unction (P238) acts as a policy enforcement point for policy and char in control of %P bearer resources. This functional entity is located at the Gateway (e. . GG!& in the GP0! case) and in the P:& GB for 3P!). The functionality of P238 is described in T! *3.*+3 P<3C. T! *3.-+, P<;C and T! *3.-+* P<<C.

4a.1# S $$ort o5 Short Me''a3e Ser7ice o7er 3eneric 3GPP 4nternet Protoco& acce'' (SMS4P) '$eci5ic entitie'
4a.1#.1 Genera&
!upport of !hort Messa e !ervice over eneric 3GPP %nternet Protocol access (!M!%P) provide 3GPP !M! messa in services across any form of %P 2onnectivity /ccess &etwor". T! *3.*+- P<=C contains the technical reali(ation of the service.

4a.1#.2 4P-Short-Me''a3e-Gatewa9 (4P-SM-G=)

The %P !hort Messa e Gateway function is used for two functionsE to deliver !M! messa es over the %P networ" and to provide interwor"in between !M! users and %nstant Messa in users. The interwor"in function translates between M/P or :iameter based si nallin and !%P si nallin to convey messa es and responses between the two systems. 1oth functions are described in T! *3.*+- P<=C.

4a.20 S .'cri$tion Pro5i&e +e$o'itor9 (SP+)

The !P0 lo ical entity contains all subscriberFsubscription related information needed for subscriptionAbased policies and char in control by the P208.

4a.21 Ser7ice 6ata !&ow :a'e) (re)it (ontro& ! nction

The !ervice :ata 8low 1ased 2redit 2ontrol 8unction performs online credit control functions. %t is a functional entity embedded in the Online 2har in 8unction (O28) within the Online 2har in !ystem. (O2!) as specified in T! 3*.*9; P,+>C.

4a.22 B55&ine (har3in3 S9'te8 (B!(S)

The Offline 2har in !ystem is lo ically specified in T! 3*.*-+ P>=C.

4a.23 Bn&ine (har3in3 S9'te8 (B(S)

The Online 2har in !ystem is specified in T! 3*.*9; P,+>C.

4a.24 :earer :in)in3 an) E7ent +e$ortin3 ! nction (::E+!)

The 1earer 1indin and 3vent 0eportin 8unction (11308) acts as a policy enforcement point for bearer bindin . uplin" bearer bindin verification and event reportin to the P208 when G'' applies. This function entity is located at a GB (e. . !AGB in the 3GPP access with PM%P based !=F!> case. G!GB in the G0P: case. /AGB in the nonA 3GPP access when PM%P or :!M%Pv; based mobility is used. eP:G with PM%P based !*b or 4ntrusted !*c case if G'bM applies).

3GPP

elease !"

')

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

The 11308 in the eP:G supports only reportin of the 43#s 6ocal %P address and 4:P port number to the P208. 1earer bindin and bearer bindin verification functions are not supported.

4a.2- >o8e (e),o)e: entitie'

4a.2-.1 >o8e ,o)e: S .'9'te8 (>,S)
The Gome &ode1 !ubsystem (G&!) consists of a Gome &ode1 (G&1). a Gome &ode1 Gateway (G&1AGB) and optionally a 6ocal GB (6AGB). The Gome &ode1 !ubsystem appears as an 0&! to the core networ" and is connected by means of the %uA2! interface to the M!2 and by means of the %uAP! interface to the !G!&. / Gome &ode1 is a 2ustomer Premises 3Duipment (2P3) offerin 4T0/& covera e. further details can be found in T! *=.-;< P,,-C. / Gome &ode1 Gateway is the ateway throu h which the Gome &ode1 accesses the core networ". more details can be found in T! *=.-;< P,,-C. / 6ocal GB is a ateway towards the %P networ"s (e. . residentialFenterprise networ"s. %nternet) associated with the Gome &ode1. more details can be found in T! *3.+;+ P9aC. The 6ocal GB can be colocated with the Gome &ode1 or can be a standalone GB (with !ervin GB and 6ocal GB collocated) residin in the 6ocal &etwor".

4a.2-.2 >o8e e,o)e: S .'9'te8 (>e,S)

The Gome e&ode1 !ubsystem (Ge&!) consists of a Gome e&ode1 (Ge&1). optionally a Gome e&ode1 Gateway (Ge&1AGB) and optionally a 6ocal GB (6AGB). The Gome e&ode1 !ubsystem is connected by means of the !, interface to the 3P2 (3volved Pac"et 2ore). more specifically to the MM3 (Mobility Mana ement 3ntity) by means of the !,AMM3 interface and to the !ervin Gateway (!AGB) by means of the !,A4 interface. / Gome e&ode1 is a 2ustomerAPremises 3Duipment (2P3) offerin 3A4T0/& covera e. further details can be found in T! 3;.3++ P<>C. / Gome e&ode1 Gateway is an optional ateway throu h which the Gome e&ode1 accesses the core networ". more details can be found in T! 3;.3++ P<>C. / 6ocal GB is a ateway towards the %P networ"s (e. . residentialFenterprise networ"s. %nternet) associated with the Gome e&ode1. more details can be found in T! *3.-+, P<;C. The 6ocal GB can be colocated with the Gome e&ode1 or can be a standalone GB (with !ervin GB and 6ocal GB collocated) residin in the 6ocal &etwor".

4a.2-.3 (SG Li't Ser7er

The 2!G 6ist !erver provisions the /llowed 2!G list and the Operator 2!G list on the 43 usin the OT/ procedures defined in T! 3,.,+* P,,>C or the OM/ :M procedures defined in T! *-.*>= P,,<C. The /llowed 2!G list and the Operator 2!G list are applicable to both 4T0/& and 3A4T0/& 2!G cells for G&1 and Ge&1 respectively.

4a.2-.4 (SG S .'cri.er Ser7er ((SS)

The 2!! is the entity in the ?P6M& storin and mana in 2!G subscriptionArelated information for roamin 43s to enable ?P6M& /utonomous 2!G 0oamin (see T! **.**+ P,3+C). The 2!! is responsible for holdin the followin user related informationE A A A 4ser %dentificationO 2!G membership ranted to the subscriber durin his stay in the ?P6M&. i.e. list of 2!G %:s and associated e'piration datesO 4ser 6ocation informationE the 2!! stores the location information of the subscriber for subseDuent update of the 2!G subscription information at the MM3. !G!& and ?60 upon subscription chan e.

3GPP

elease !"

'*

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

The 2!! consists of the followin functionalitiesE A download of the 2!G subscription information upon reDuest from the servin MM3. !G!& and ?60. throu h the !<a. !<d. Ghv and Gv interfaces. to enable roamin subscribers to access to the P! and 2! :omain services via 2!G cellsO service provisionin . includin updatin the appropriate servin entities (i.e. MM3. !G!& and ?60) with modifications of the the 2!G membership ranted to the subscriber.

The or anisation of the subscriber data is outlined in T! *3.++> P=C. %t also indicates which numbers and identifiers specified in T! *3.++3 P3C are stored in the 2!!.

4a.2" %$$&ication !ront En)' (%!E)

Bhen the 4ser :ata 2onver ence (4:2) architecture is applied. certain functional entities "eep the application lo ic. but do not locally store user data permanently. 3'amples of such functional entities are G60FG!!F/u2 and /pplication !ervers. These dataAless functional entities are "nown in the 4:2 architecture as /pplication 8ront 3nds. The application that is handled by an /83 determines the type of /83. e. . G60A83 or G!!A83. The reference points between the 8ront 3nds and the core and service layers are not affected by the 4:2 architecture. More information on /pplication 8ront 3nds can be found in T! *3.33= P,*+C.

4a.21 U'er 6ata +e$o'itor9 (U6+)

The 4:0 is a functional entity that acts as a sin le lo ical repository storin user data. The userArelated data traditionally stored in the G!!FG60F/u2. /pplication !ervers. etc.. are now stored in the 4:0. 4:0 facilitates the share and provisionin of userArelated data. The 4:0 provides a uniDue reference point to /pplication 8ront 3nds such as G!!FG60F/u2F/! 8ront 3nds. This reference point is named 4d. More information on the 4:0 can be found in T! *3.33= P,*+C.

4a.2; Tra55ic 6etection ! nction (T6!)

The Traffic :etection 8unction (T:8) is a functional entity that performs application detection and control. The functional description of the T:8 is in T! *3.*+3 P<3C.

4a.2# S$eci5ic entitie' to 5aci&itate co88 nication' with $acket )ata network' an) a$$&ication'
4a.2#.1 Machine T9$e (o88 nication-4nter=orkin3 ! nction (MT(-4=!)
The Machine Type 2ommunicationA%nterBor"in 8unction (MT2A%B8) is a functional entity that acts as an interface between the P6M& and a !ervices 2apability !erver (!2!) to provide specific MT2 functionalities in the P6M& such as device tri erin . The functional description of the MT2A%B8 is in T! *3.;>* P,3*C.

4a.2#.2 Machine T9$e (o88 nication- % thentication, % thori?ation an) %cco ntin3 (MT(-%%%)
The Machine Type 2ommunicationA/uthentication. /uthori(ation and /ccountin (MT2A///) is a functional entity that translates an %M!% to the e'ternal identifier(s) of the user. The functional description of the MT2A/// is in T! *3.;>* P,3*C.

3GPP

elease !"

'+

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

4a.30 T(P Pro*9 ! nction

Bhen T2P is bein used. T2P connection is between a T2P client and a T2P server as defined in 082<93 P,3>C. / T2P Pro'y 8unction splits a T2P connection such that it terminates the T2P connection received from the 43 and establishes a correspondin T2P connection to the other end system in pac"et data networ". &oteE The T2P Pro'y 8unction can be deployed in a GG!&FPGB or as an e'ternal function beyond !GiFGi. The T2P Pro'y is deployed such that it is transparent to the 43 and its mobility. The implementation and necessary protocols to reali(e the functions related to T2P Pro'y 8unction are outside the scope of 3GPP specifications.

4a.31 S$eci5ic entitie' 5or Packet Switche) Strea8in3 (PSS) Ser7ice

4a.31.1 Packet Switche) Strea8in3 Ser7ice Ser7er (PSS Ser7er)
P!! !erver provides the 3GPP pac"et switched streamin service based on the %3T8 0T!PF!:P andFor GTTP standards. with 3GPP e'tensions. The description of the P!! !erver is detailed in T! *;.*33 P,39C.

(on5i3 ration o5 a P .&ic Lan) Mo.i&e ,etwork

-.1 :a'ic con5i3 ration

The basic confi uration of a Public 6and Mobile &etwor" (P6M&) supportin GP0! and the interconnection to the P!T&F%!:& and P:& is presented in fi ure , and fi ure ,a. Bhereas the basic confi uration of a Public 6and Mobile &etwor" (P6M&) supportin P! :omain (both GP0! and 3P2) and the interconnection to the P!T&F%!:& and P:& is presented in fi ure ,b. This confi uration presents si nallin and user traffic interfaces which can be found in a P6M&. %mplementations may be differentE some particular functions may be athered in the same eDuipment and then some interfaces may become internal interfaces. %n the basic confi uration presented in fi ure ,. all the functions are considered implemented in different eDuipments. Therefore. all the interfaces within P6M& are e'ternal. %nterfaces / and /bis are defined in the ->Aseries of Technical !pecifications. %nterfaces %u. %ur and %ub are defined in the *=.-''Aseries of Technical !pecifications. %nterfaces 1. 2. :. 3. 8 and G need the support of the Mobile /pplication Part of the si nallin system &o. < to e'chan e the data necessary to provide the mobile service. &o protocols for the GAinterface and for the %Ainterface are standardi(ed. /ll the GP0!Aspecific interfaces (GA series) are defined in the *3Aseries. *-Aseries and *9Aseries of Technical !pecifications. %nterfaces Mc. &b. and &c are defined in T! *3.*+= P-3C and in the *9Aseries of Technical !pecifications. The specifications for 3A4T0/& interfaces !, and H* are specified in T! 3;.-'' and &/! protocol is specified in T! *-.3+, P>9C series of specifications. The interfaces !;aFdF!,3 are specified in the specifications T! *9.*<* P>;C. The 3P2 specific !,F3F-F=F>F,+F,,F,*F series are specified in T! *9.*<- P9+C for GTP based protocols and for PM%P based !=F> interfaces are specified in T! *9.*<= P93C. 8rom this confi uration. all the possible 3GPP access P6M& or anisations can be deduced. %n the case when some functions are contained in the same eDuipment. the relevant interfaces become internal to that eDuipment. The confi uration possibilities when usin nonA3GPP access technolo ies usin 3P! is not part of the scope of this specification. The architecture and details for nonA3GPP access and mobility and interwor"in with nonA3GPP access are described in T! *3.-+* P<<C and the interfaces and protocols are specified in 3GPP *-Aseries and *9Aseries of specifications..

3GPP

elease !"

',

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

P208

Le3en)/ :o&) &ine'/ inter5ace' ' $$ortin3 'er tra55icC 6a'he) &ine'/ inter5ace' ' $$ortin3 'i3na&&in3. ,BTE 1/ The 5i3 re 'how' )irect interconnection' .etween the entitie'. The act a& &ink' 8a9 .e $ro7i)e) .9 an n)er&9in3 network (e.3. SS1 or 4P)/ thi' nee)' 5 rther 't )ie'. ,BTE 2/ =hen the MS( an) the SGS, are inte3rate) in a 'in3&e $h9'ica& entit9, thi' entit9 i' ca&&e) UMTS MS( (UMS(). ,BTE 3/ % (G)MS( 'er7er an) a''ociate) (S-MG= can .e i8$&e8ente) a' a 'in3&e no)e/ the (G)MS(. ,BTE 4/ The Gn inter5ace (.etween two SGS,') i' a&'o $art o5 the re5erence architect re, . t i' not 'hown 5or &a9o t $ r$o'e' on&9.

.i/ure !0 :asic 5onfi/uration of a P;8N supportin/ 5S and PS services (usin/ GP S# and interfaces

3GPP

elease !"

'-

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

SMS-GMS(2 SMS-4=MS( SG) E MS(Ser7er S"c2( >SS (>L+) G)2G)) SGS, MME

.i/ure !a0 5onfi/uration for Short 8essa/e Service

3GPP

elease !"

)%

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

PSTN PSTN

PSTN

Gi Rx S9

Gp

SGi

CSMGW

Mc

GMSC server
C

PCRF

Gx

GGSN
Gx

PDN-GW

S8 S5 Gc Gn Gr/S6d S13 S11 Gxc S4

Nc PSTN Nb

HSS (HLR, AuC)

D

S-GW

EIR
F Gf Gs

VLR
B

G E Nc

VLR
B

SGSN

S6a S3 S12

MSC server
Mc

MSC server
Mc

MME CS-MGW
Nb A IuCS Gb IuPS IuCS IuPS

CS-MGW CN RNS
Iur

BSS BSC
Abis

RNC
Iub

RNC

BTS Um

BTS

Node B
cell

Node B
S1-MME

Uu ME
SIM-ME i/f or Cu
EUTRANUu

S1-U

eNB
X2

eNB

SIM

USIM
MS

3A4T0/&

,BTE/

The inter5ace' in .& e re$re'ent EPS 5 nction' an) re5erence $oint'.

.i/ure !40 :asic 5onfi/uration of a 3GPP Access P;8N supportin/ 5S and PS services (usin/ GP S and 1PS# and interfaces

3GPP

elease !"

)!

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

-.2 (on5i3 ration o5 L(S entitie'

-.2.1 (on5i3 ration o5 L(S entitie' 5or GE+%,
The confi uration of 62! entities for G30/& is presented in fi ure *. %n the fi ure. all the functions are considered implemented in different lo ical nodes. %f two lo ical nodes are implemented in the same physical eDuipment. the relevant interfaces may become internal to that eDuipment.
3'8S(! :SS 4 -c' 3G 3G MS(2 MS( 2
U8 MS U8 T9$e% LMU MS( Ser7er

< Note "

Pro$rietar9

BS% S(S
Pro$rietar9 GML(

:TS
T9$e : LMU %.i'

:S(

L3 4 -$' 3G SGS, 3 L3 2L3) GML(

%

BS% %P4
E*terna& L(S (&ient

2G MS( MS(L3 2G L32L3)

2G SGS,

Lr

Le

Lh

Lh

SML(

(:(

G.

>SS
< Note !

L. SML(

L. SML(

(:(-:S(

Note !0 >SS inc& )e' .oth 2G->L+ an) 3G->L+ 5 nctiona&it9. Note "0 %' one a&ternati7e the L(S c&ient 8a9 3et &ocation in5or8ation )irect&9 5ro8 GML(, which 8a9 contain BS% Mo.i&it9 S(S with ' $$ort 5or the BS% 'er &ocation inter5ace'.

L$

(:(

G1 AN
,BTE/

SML(-(:(

L3) inter5ace i' a$$&ica.&e on&9 5or an SGS, ' $$ortin3 EPS .a'e) inter5ace' an) $rotoco&'.

.i/ure "0 5onfi/uration of ;5S entities for a G1 AN P;8N

3GPP

elease !"

)"

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

-.2.2 (on5i3 ration o5 L(S entitie' 5or UT+%,

The basic confi uration of 4T0/& 62! is presented in fi ure 3. The !M62 functionality is inte rated in !0&2 or. in case a !tandA/lone !M62 entity (!/!) is present. split between !0&2 and !M62.
3'8S(!
< Note "

NS
Stan)-%&one S8;5 (S%S) 7u ( pc
< Note 3

Pro$rietar9 3G MS(2 MS( 'er7er L3 GML( L3 2L3) 3G SGS, GML( Lr Lh >SS

< Note !

4 - c'

Lc

BS% S(S Pro$rietar9 Le Lh

E*terna& L(S c&ient

+,( +,(

7ur

( (SML( SML( 5 5 nctiona&it9 nctiona&it9 ) )

S+,( S+,(

7u4
%''ociate) LMU ce&&

4 - $'

Node :

=T AN
=1

Note !0 >SS inc& )e' .oth 2G->L+ an) 3G->L+ 5 nctiona&it9. =u =u Note "0 %' one a&ternati7e the L(S c&ient 8a9 3et &ocation in5or8ation )irect&9 5ro8 GML(, which 8a9 contain BS% Mo.i&it9 S(S with ' $$ort 5or the BS% 'er &ocation inter5ace'. Note 30 The SML( 8a9 .e either a 'tan)-a&one network e&e8ent (S%S) or an interna& 5 nction on the +M(.

Stan) %&one LMU

,BTE/

L3) inter5ace i' a$$&ica.&e on&9 5or an SGS, ' $$ortin3 EPS .a'e) inter5ace' an) $rotoco&'.

.i/ure 30 5onfi/uration of ;5S entities for a =T AN P;8N

-.2.3 (on5i3 ration o5 L(S entitie' 5or E-UT+%,

The basic confi uration of 3A4T0/& 62! is presented in fi ure 3a.

3GPP

elease !"

)3

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

SL3 S1 UE LTE-U E-UT+%, MME GML( SL' E-SML( SLh >SS Le

E*terna& L(S
(&ient

.i/ure 3a0 5onfi/uration of ;5S entities for an 1(=T AN P;8N

-.3 (on5i3 ration o5 (%MEL entitie'

The followin fi ure shows the interconnection of the 2/M36Aspecific entities with the rest of the networ". Only the interfaces specifically involved in 2/M36 provisionin are shown. i.e. all the GM!2. M!2. !G!& and G60 interfaces depicted in fi ure , are still supported by these entities even if not shown. 2/M36 is not supported for 3A4T0/& access. &OT3E Most 2/M36Aspecific interfaces have no particular name. They are desi nated by the name of the two entities they lin" to ether. e. . Qthe sm!!8A sm!28 interfaceQ.

GMSC gsmSSF
C

gsmSRF

gsmSCF
Ge

HLR
D Gr

gsmSSF VLR
B

gprsSSF SGSN

MSC

.i/ure '0 confi/uration of 5A81; entities

3GPP

elease !"

)'

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

The bold lines are used for interfaces supportin user data only. the dashed lines are used for interfaces supportin si nallin only.

-.4 (on5i3 ration o5 (:S entitie'

CBC CN
1!2A212 iFf %u12

BSS BSC
/bis

RNS RNC
%ub

BTS

BTS

Node B

Node B

UE

.i/ure )0 5onfi/uration of a P;8N supportin/ 5ell :roadcast Service entities for G1 AN>=T AN

UE

1(=T AN S1-MME

MME S:c

(:(

(:E

E-UT+%,-U

.i/ure '$"$3(!0 ?arnin/ System Architecture for 1(=T AN Access &OT3E The 213 and the interface between 213 and 212 are out of scope of 3GPP specifications.

-.- (on5i3 ration o5 4M (, S .'9'te8 entitie'

-.-.1 4M (, S .'9'te8 5 nctiona& entitie'
The confi uration of %M 2& !ubsystem entities is presented in fi ure ;. %n the fi ure. all the functions are considered implemented in different lo ical nodes. %f two lo ical nodes are implemented in the same physical eDuipment. the relevant interfaces may become internal to that eDuipment. Only the interfaces specifically lin"ed to the %M subsystem are shown. i.e. all the !G!&. GG!& and G!! interfaces depicted in fi ure , are still supported by these entities even if not shown.

3GPP

elease !"

))

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

IP Multimedia Networks
CS Network
Mm Mb Mb CS Mm Ma

Legacy mobile signalling Networks

AS
Sh Mg Mk Mw Mj Cx
C, D, Gc, Gr

LCS Client
Le

BGCF
CS Mk

I-CSCF

LRF

BGCF
Mi Cx Dx Mg Mr Cr Mw ISC S-CSCF Dx MRB

HSS SLF
ISC

Mm

IMSMGW Mn Mb MRFP Mp Mb Mb Mb

MGCF

M& Dh

E-CSCF
Rc

Mw MRFC P-CSCF Mx Rx Gm Mx IBCF Ici, Mm Ix Mx I4 Mi

EATF
Mx

BGCF

TrGW UE

Izi Ut

Le3en)/ :o&) &ine'/ 6a'he) &ine'/

inter5ace' ' $$ortin3 'er tra55icC inter5ace' ' $$ortin3 on&9 'i3na&&in3.

,BTE 1/ The re5erence $oint (S ((irc it Switche)) i' not '$eci5ie) in thi' '$eci5ication. ,BTE 2/ The re5erence $oint 4- i' not 'hown in thi' 5i3 re.

.i/ure *0 5onfi/uration of 78 Su4system entities

-.-.2 4M (, S .'9'te8 Ser7ice &a9er

The fi ure below depicts an overall view of the functional architecture for services.

3GPP

elease !"

)*

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

/!

/!

!%P !%P/pplication /pplication !erver !erver

!2%M

!h G!! G!!

%!2 2' !i ! A2!28 ! A2!28 %!2 %M A!!8 %M A!!8 2/P

2amel 2amel!ervice !ervice 3nvironment 3nvironment

%!2

O!/ O!/service service capability capabilityserver server (!2!) (!2!)

O!/ /P%

O!/ O!/ application application server server

M/P

.i/ure *a0 .unctional architecture for the provision of service in the 78S The purpose of the %M !!8 is to host the 2/M36 networ" features (i.e. tri er detection points. 2/M36 !ervice !witchin 8inite !tate Machine. etc.) and to interwor" with 2/P. The %M !!8 and the 2/P interface support le acy services only. The application server may contain Qservice capability interaction mana erQ (!2%M) functionality and other application servers. The !2%M functionality is an application which performs the role of interaction mana ement. The internal components are represented by the Qdotted bo'esQ inside the !%P application server. The internal structure of the application server is outside the standards. The !h interface shall have sufficient functionality to enable this scenario. The fi ure below depicts an overall view of the functional architecture for enablin the mana ement of the user#s service related information via the 4t interface.
S7P Application Server

Sh >SS (* 4S(

Ut

UE

S-(S(!

.i/ure *40 .unctional architecture for the mana/ement of the user@s service related information The fi ure below depicts an overall view of the functional architecture for routin !%P reDuests between %A2!28 and /pplication !erver.

3GPP

elease !"

)+

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

Application Server

Ma

4-(S(!

.i/ure *c0 .unctional architecture for the routin/ of S7P reAuests 4etween 7(5S5. and AS

-.-.3 Ser7ice (entra&i?ation an) (ontin it9

8i ure ;d depicts an overall view of the functional architecture for %M! services centrali(ation and continuity.

7! 7S5 Gm =1 7" A>7u 5S Access 73

S55 AS

5S5.

8c 8S5 Server 5S(8G?

TAS

.i/ure *d0 .unctional architecture for 78S Service 5entraliBation and 5ontinuity %M! !ervice 2entrali(ation. defined in T! *3.*9* P,,+C provides communication services such that all services. and service control. are based on %M! mechanisms and enablers. %t enables %M! services when usin 2! access as bearer for the media. %M! !ervice 2ontinuity. defined in T! *3.*3< P,,,C provides !ession Transfer mechanisms to maintain service continuity in the event of access transfer for the case when such events are not hidden from the %M! session layer and thus service continuity could not otherwise be maintained. 8i ure ;e provides the reference architecture for !0?22 usin the /T28 enhancements as defined in T! *3.*3< P,,,C. The /T28 enhancements provide !ession Transfer mechanisms in the servin networ" to maintain service continuity in the event of access transfer for !0?22.

3GPP

elease !"

),

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

.i/ure *e0 78S Service 5entraliBation and 5ontinuity eference Architecture when usin/ AT5. enhancements %f neither the M!2 !erver is not enhanced for %2!. the interface between M!2 !erver and /T28 is Mw. &OT3 *E %f the M!2 !erver is enhanced for %2!. the interface between M!2 !erver and /T28 is %*.

-.-.4 =e.+T( acce'' to 4MS

8i ure =.=.-A, depicts an overall view of the functional architecture for Beb0T2 access to %M!.

==S!
=1

=4( , % T UE
=3

=2

4 P ( % ,

eP-(S(!
4MS-%LG +* .1

Mw

42S-(S(!

P ( E !
G*

>2 V-P(+!

e4MS- %G=

,BTE/

The $re'ence o5 )a'he) e&e8ent' in the 5i3 re )e$en)' on the con5i3 ration. P(( 5 nctiona& e&e8ent' are $re'ent on&9 5or EP( acce'' with DoS. The corre'$on)in3 P(( e&e8ent' 5or 5i*e) acce'' are a&'o o$tiona&&9 ' $$orte) . t not 'hown. The ,%T i' 8eant 5or non-ce&& &ar acce'' to 4MS.

.i/ure )$)$'(!0 .unctional architecture for ?e4 T5 access to 78S

3GPP

elease !"

)-

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

The architecture and the procedures to provide communication services to Beb0T2 %M! clients (B%2) are defined in /nne' 4 of T! *3.**> P3-C.

-." (on5i3 ration o5 Si3na&&in3 Gatewa9 ! nction

The !i nallin ateway function is used to interconnect different si nallin networ"s i.e. !2TPF%P based si nallin networ"s and !!< si nallin networ"s. The application layer (e. . %!4P. 1%22. M/P or 2/P) is not affected. The si nallin ateway function may be implemented as a stand alone entity or inside another entity.

4P Si3na&&in3 tran'$ort ,=

!2TPF%P

SGW

MTP

SS1 Si3na&&in3 tran'$ort ,=

.i/ure +0 5onfi/uration of a si/nallin/ /ateway function &OT3E !!< application transport and !2TPF%P adaption protocols are not shown.

-.1 (on5i3 ration o5 3GPP2=L%, 4nterworkin3

The confi uration of the 3GPPFB6/& interwor"in function is presented in fi ure >. The fi ure shows all networ" entities and reference point for the roamin scenario when a B6/& 43 accesses P! based services in the home networ". P! based services in the visited networ" are accessed via a Pac"et :ata Gateway in the visited 3GPP networ". 0eference point Bw between B6/& 43 and B6/& is outside the scope of 3GPP and only shown for completeness.

3GPP

elease !"

*%

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

%ntranet F %nternet

3GPP &isited Network 3GPP %%% Pro*9

=3

?;AN Access Network =L%, =w UE =n =%G

=a

=)

=$
8 =

3GPP %%% Ser7er

=* 6w

>SS

SL!

E2 6 rE G

Packet 6ata Gatewa9

>L+ =i 3GPP 3ome Network

.i/ure ,0 5onfi/uration of a 3GPP>?;AN interworkin/ function

-.; (on5i3 ration o5 Pre'ence 'er7ice

The reference architecture model. the reference points and the functional entities to support the Presence !ervice are described in T! *3.,-, P;>C.

-.# (on5i3 ration o5 M:MS entitie'

The confi uration of the M1M! entities for GP0! and 3P! is represented in fi ures 9 and 9a respectively. M1M! for GP0! supports 4T0/& and G30/&. M1M! for 3P! supports 3A4T0/& and 4T0/&.

3GPP

elease !"

*!

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

P6N ( e $ / $7nternet #

3;

(ontent Pro7i)er 2 M &tica't :roa)ca't So rce

Gr G8. 4 Gn 2 G$ (ontent Pro7i)er 2 M &tica't :roa)ca't So rce

=1

=T AN
4

SGSN

4 2 G. U8 4

GGSN TP.
Gi G8c Gi

:8 ( S5
M?

:8(S5

=1

G1 AN

9ther P;8N

.i/ure -0 5onfi/uration of 8:8S entities for GP S P6, Gatewa9 SGi SG8. :M-S( SGi-8. (ontent Pro7i)er

M3 E-UT+%, U UE E-UT+%, M1 U UE
,BTE/

MME S8 M:MS G= Sn SGS,

4 UT+%,

The M(E (M &ti-ce&&2M &tica't (oor)ination Entit9) i' not 'hown in the 5i3 re. See TS 3".300 F1;A.

.i/ure -a0 5onfi/uration of 8:8S entities for 1volved Packet System

3GPP

elease !"

*"

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

-.10 (on5i3 ration o5 Short Me''a3e Ser7ice o7er 3eneric 3GPP 4nternet Protoco& acce'' (SMS4P) entitie'
The confi uration of the !hort Messa e !ervice over eneric 3GPP %nternet Protocol access (!M!%P) entities are represented in fi ure ,+.

SME

S(

(G!2(6! +5 B(S +o

SMS-GMS(2SMS-4=MS( E 2 G) 2 G)) 2 SG) 4P-SM-G=

( 2 S"c

>SS

Sh G 2 S"c

4S(

(* (S(!

G8 UE

.i/ure !%0 5onfi/uration of S8S7P entities

-.11 (on5i3 ration o5 Po&ic9 (ontro& an) (har3in3 entitie'

The P22 functionality is comprised by the functions of the Policy and 2har in 3nforcement 8unction (P238). the 1earer 1indin and 3vent 0eportin 8unction (11308). the Policy and 2har in 0ules 8unction (P208). the /pplication 8unction (/8). the Online 2har in !ystem (O2!). the Offline 2har in !ystem (O82!). the Traffic :etection 8unction (T:8) and the !ubscription Profile 0epository (!P0) or the 4ser :ata 0epository (4:0). 8i ures =.,,A, throu h to =.,,A- describe the nonAroamin and roamin architecture for P22. The P22 architecture e'tends the architecture of an %PA2/&. where the Policy and 2har in 3nforcement 8unction is a functional entity in the Gateway node implementin the %P access to the P:&. The allocation of the 1earer 1indin and 3vent 0eportin 8unction is specific to each %PA2/& type and specified in the T! *3.*+3 P<3C. P22 function ma"es it possible to apply policy and char in control to any "ind of 3GPP %P 2/& and any nonA3GPP accesses connected via 3P2 complyin with T! *3.-+* P<<C. /pplicability of P22 to other %P 2/& is not restrictedO however. it shall be possible for the P22 architecture to base decisions upon the type of %P 2/& used (e. . GP0!. %A

3GPP

elease !"

*3

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

B6/&. etc.). !upport for policy control and char in when local brea"out and roamin are applied as specified in T! *3.-+, P<;C and T! *3.-+* P<<C is supported.
S$

Su4scription Profile epository (SP # .i2ed :road4and Access N? S#a :P5. S13N:( G? G**

A. 9nline 5har/in/ System (95S#

+*

Policy and 5har/in/ (P5 .#

ules .unction S9

G*

S)

G9 ::1 .

PCEF
T6. G?n G?

G9n 9ffline 5har/in/ System (9.5S#

P6N G?
.i/ure )$!!(!0 9verall P55 lo/ical architecture (non(roamin/# when SP is used

3GPP

elease !"

*'

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

=ser 6ata epository (=6 # .i2ed :road4and Access N? S#a :P5. S13N:( G? G**

U)

A. 9nline 5har/in/ System (95S#

+*

Policy and 5har/in/ (P5 .#

ules .unction S9

G*

S)

G9 ::1 .

PCEF
T6. G?n G?

G9n 9ffline 5har/in/ System (9.5S#

P6N G?
.i/ure )$!!("0 9verall P55 lo/ical architecture (non(roamin/# when =6 is used
Su4scription Profile epository (SP # 3P;8N .i2ed :road4and Access Network S#a :P5.

S$

A. 9nline 5har/in/ System (95S#

+*

&P;8N Policy and 5har/in/ ules .unction (&(P5 .# S13N:( G? G** S#

Policy and 5har/in/ .unction (3(P5 .#

ules S9

G*

S) G9 G9n

PCEF
::1 . T6. G? G?n 9ffline 5har/in/ System (9.5S#

P6N G?

.i/ure )$!!(30 9verall P55 architecture (roamin/ with home routed access# when SP is used

3GPP

elease !"

*)

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

&P;8N

Su4scription Profile epository 3P;8N (SP # S$

A. 9nline 5har/in/ System (95S#

+*

A.

Policy and 5har/in/ ules .unction (3(P5 .#

S9

+* .i2ed :road4and Access Network S#

:P5.

S#a

Policy and 5har/in/ ules .unction (&(P5 .# (&(P5 .#

S13N:( G?

G** G*

S) G9

::1 .

PCEF

G9n T6. G?n G? 9ffline 5har/in/ System (9.5S#

P6N G?

.i/ure )$!!('0 9verall P55 architecture for roamin/ with P51. in visited network (local 4reakout# when SP is used

-.12 (on5i3 ration o5 (S!:((S !a&&.ack)

The 2! fallbac" in 3P! enables the provisionin of voice and other 2!Adomain services (e. . 2! 4:% videoF !M!F 62!F 4!!:) by reuse of 2! infrastructure when the 43 is served by 3A4T0/&. This function is only available in case 3A4T0/& covera e is overlapped by either G30/& covera e or 4T0/& covera e. The confi urations of the 2!81 entities are represented in fi ure =.,*.

3GPP

elease !"

**

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

=T AN U G1 AN U8

4 -(S MS(2VL+ % SG'

UE

1(=T AN E-UT+%,-U S1-MME

MME

.i/ure )$!"0 5onfi/uration of 5S.: &OT3E The MGB is not shown in the fi ure =.,* since the 2! fallbac" in 3P! does not have any impacts to the 4ser plane handlin .

-.13 (on5i3 ration o5 Sin3&e +a)io Voice (a&& (ontin it9 (S+V(()
-.13.1 E-UT+%,2UT+%, (>SP%) to UT+%, or GE+%, S+V(( architect re
!in le 0adio ?oice 2all 2ontinuity (P! to 2!) refers to continuity between %M! over P! access and 2! calls that are anchored in %M! when the 43 is capable of transmittin Freceivin on only one of those access networ"s at a iven time. P! to 2! !0?22 is specified in T! *3.*,; P>3C. The followin fi ures =.,3. =.,3a and =.,3b show the entities involved in P! to 2! !0?22.

.i/ure )$!30 S &55 architecture for 1(=T AN to 3GPP =T AN>G1 AN

3GPP

elease !"

*+

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

UE

U82U

Tar3et UT+%,2GE+%,

4 -c'2%

MS( Ser7er

4 -$'2G. SGS, Gn

S7

SGS,

Gr >SS

3GPP 4MS

4 -$' UT+%, (>SP%)

Gn

UE

GGS,

Gi

.i/ure )$!3a0 S &55 architecture for =T AN (3SPA# to 3GPP =T AN>G1 AN with Gn 4ased SGSN
U82U Tar3et UT+%,2GE+%, 4 -c'2%

UE

MS( Ser7er

4 -$'2G. SGS, S1"

S7

SGS,

Gr >SS

3GPP 4MS

4 -$' UT+%, (>SP%)

S4 S12

UE

Ser7in32P6, G=

SGi

.i/ure )$!340 PS to 5S S &55 architecture for =T AN (3SPA# to 3GPP =T AN>G1 AN with S' 4ased SGSN
,BTE 1/ ,BTE 2/ ,BTE 3/ ,BTE 4/ The a.o7e 5i3 re' on&9 'how the nece''ar9 co8$onent' re&ate) to MS( Ser7er enhance) with S+V((. MS( Ser7er 'hown in the a.o7e 5i3 re' are enhance) 5or S+V((. Thi' architect re a&'o a$$&ie' to roa8in3 'cenario (i.e., S;, S"a are not i8$acte) ) e to S+V((). The MS( Ser7er enhance) with S+V(( 8a9 not .e the 5ina& tar3et MS( which connect' to the tar3et ce&&.

-.13.2 UT+%,2GE+%, to E-UT+%, or UT+%, (>SP%) S+V(( architect re

2! to P! !in le 0adio ?oice 2all 2ontinuity refers to continuity between a 2! call and %M! call over P! access that are anchored in %M! when the 43 is capable of transmittin Freceivin on only one of those access networ"s at a iven time. 2! to P! !0?22 is specified in T! *3.*,; P>3C. The followin fi ures =.,3c. =.,3d and =.,3e show the entities involved in 2! to P! !0?22.

3GPP

elease !"

*,

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

UE

U8 2 U

UT+%, 2 GE+%,

4 - c' 2 %

MS( Ser7er

4 -$' 2 G. SGS, S3 4MS MME S"a >SS S 1 -MME S 11 S7 6

UE

E -UT+%, U

Tar3et E - UT+%,

S 1 -U

Ser7in3 2 P6, G=

SGi

:earer $ath .e5ore >B :earer $ath a5ter >B S4P 'i3na&in3 $ath a5ter >B

,BTE 1/ The a.o7e 5i3 re on&9 'how' the nece''ar9 co8$onent' re&ate) to MS( Ser7er enhance) 5or (S to PS S+V((. ,BTE 2/ MS( Ser7er 'hown in the 5i3 re i' enhance) 5or (S to PS S+V((. ,BTE 3/ Thi' architect re a&'o a$$&ie' to roa8in3 'cenario (i.e. S;, S"a are not i8$acte) ) e to (S to PS S+V(().

.i/ure )$!3c0 5S to PS S &55 architecture for =T AN>G1 AN to 1(=T AN

U82U Tar3et UT+%,2GE+%, 4 -c'2%

UE

MS( Ser7er

4 -$'2G. SGS, Gn

S7

78S
SGS, Gr >SS

4 -$' UT+%, (>SP%)

Gn

UE

GGS,

Gi

.i/ure )$!3d0 5S to PS S &55 architecture for =T AN>G1 AN to =T AN (3SPA# with Gn 4ased SGSN

3GPP

elease !"

*-

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

UE

U82U

Tar3et UT+%,2GE+%,

4 -c'2%

MS( Ser7er

4 -$'2G. SGS, S1"

S7

78S
SGS, S") >SS

4 -$' UT+%, (>SP%)

S4 S12

UE

Ser7in32P6, G=

SGi

,BTE 1/ The a.o7e 5i3 re' on&9 'how the nece''ar9 co8$onent' re&ate) to MS( Ser7er enhance) with (S to PS S+V((. ,BTE 2/ MS( Ser7er 'hown in the a.o7e 5i3 re' are enhance) 5or (S to PS S+V((. ,BTE 3/ Thi' architect re a&'o a$$&ie' to roa8in3 'cenario.

.i/ure )$!3e0 5S to PS S &55 architecture for =T AN>G1 AN to =T AN (3SPA# with S' 4ased SGSN

-.14 (on5i3 ration o5 Sec rit9

The reference architecture model. the reference points and the functional entities to support and provide security related functions to the users. devices and networ" entities when in the 4T0/& access as well as usin %M! are described in T! 33.,'' series and T! 33.*'' series. The reference architecture model. the reference points and the functional entities to support security functions to the users. devices and networ" entities when in the 3P2 are described in T! 33.-+, P><C for 3GPP access and in T! 33.-+* P>>C for nonA3GPP accesses.

-.1- (on5i3 ration o5 Law5 & 4nterce$t re&ate) entitie'

The eneral confi uration for 6awful %nterception is shown in fi ure =.,=. The definition of the 6% functional entities and interfaces is provided in T! 33.,+< P>-C. The reference confi uration is only a lo ical representation of the entities involved in lawful interception and does not mandate separate physical entities. There is one /dministration 8unction (/:M8) in the networ". 3very physical %nterceptin 2ontrol 3lement (%23) is lin"ed by its own H,J,Ainterface to the /:M8. 2onseDuently. every sin le %23 performs interception (activation. deactivation. interro ation as well as invocation) independently from other %23s.

3GPP

elease !"

+%

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

G%,

H,J,

Mediation 8unction

/:M8

H,J* G%*

H,J3 H*

LEMF G%3

Mediation 8unction

:elivery 8unction * %nterceptin 2ontrol 3lement

Mediation 8unction

:elivery 8unction 3

H3

.i/ure )$!)0 General ;awful 7nterception Architecture

-.1" (on5i3 ration o5 (har3in3 re&ate) entitie'

The eneral confi uration for common char in architecture for 3GPP defined entities is shown in fi ure =.,; as defined in T! 3*.*-+ P>=C. This common char in architecture provides a lo ical view and the actual domain F service F subsystem specific char in architecture depends on the domain F service F subsystem in Duestion. The physical mappin of the common lo ical architecture onto each domain. subsystem or service is described in the respective char in specifications. i.e. the T!s 3*.*='. 3*.*;' and 3*.*<' number ran e. 3GPP networ"s provide functions that implement offline andFor online char in mechanisms on the bearer (e. . 3P2). subsystem (e. . %M!) and service (e. . MM!) levels. %n order to support these char in mechanisms. the networ" performs realAtime monitorin of resource usa e on the above three levels in order to detect the relevant char eable events. %n offline char in . the resource usa e is reported from the networ" to the 1illin :omain after the resource usa e has occurred. %n online char in . a subscriber account. located in an Online 2har in !ystem. is Dueried prior to rantin permission to use the reDuested networ" resource(s). Offline and online char in may be performed simultaneously and independently for the same char eable event.

3GPP

elease !"

+!

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

:illin/ 6omain
5S (N1 Service(N1 S7P AS 8 .5 8G5. :G5. 7:5. P(5S5. 7(5S5. S(5S5. ?;AN SGSN eP6G S(G? 881 T6. P(G? P51. 78S( G?.

5G.

56.

95S

P5 .

9..;7N1 53A G7NG

A.

9N;7N1 53A G7NG

.i/ure )$!*0 ;o/ical u4iAuitous char/in/ architecture

-.11 (on5i3 ration o5 >o8e (e),o)e: entitie'

-.11.1 (on5i3 ration o5 the >o8e ,o)e: S .'9'te8
The confi uration of the Gome &ode1 !ubsystem is presented in fi ure =.,<A,. %n the fi ure. all the functions are considered implemented in different lo ical nodes. %f two lo ical nodes are implemented in the same physical eDuipment. the relevant interfaces may become internal to that eDuipment. The Gome &ode1 Gateway may also be used only for the control plane of %uA2! andFor %uAP! interfaces. %n this case. the user plane of %uA2! andFor %uAP! interfaces is directly between the Gome &ode1 and respectively the M!2F?60 and the !G!&F!ervin GBFGG!&. %n case :irect Tunnel is established. the user plane is directly between the Gome &ode1 !ubsystem and the GG!& or !ervin GB nodes.

3GPP

elease !"

+"

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

.i/ure )$!+(!0 5onfi/uration of P;8N supportin/ 3ome Node: Su4system

-.11.2 (on5i3 ration o5 the >o8e e,o)e: S .'9'te8

The confi uration of Gome e&ode1 !ubsystem with a Gome e&ode1 Gateway present is shown in fi ure =.,<A*. %n the fi ure. all the functions are considered implemented in different lo ical nodes. %f two lo ical nodes are implemented in the same physical eDuipment. the relevant interfaces may become internal to that eDuipment. The presence of Gome e&ode1 Gateway in the confi uration of Gome e&ode1 !ubsystem is optional. The Gome e&ode1 Gateway may also be used only for the !,AMM3 interface. %n this case. the !,A4 interface is directly between the Gome e&ode1 and the !AGB.

3GPP

elease !"

+3

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

.i/ure )$!+("0 5onfi/uration of P;8N supportin/ 3ome eNode: Su4system

-.1; (on5i3 ration 5or 5aci&itatin3 co88 nication' with $acket )ata network' an) a$$&ication'
The reference architecture model. the reference points and the functional entities to facilitate communications with pac"et data networ"s and applications are described in T! *3.;>* P,3*C.

-.1# (on5i3 ration o5 Packet Switche) Strea8in3 (PSS) Ser7ice

The confi uration of the P!! entities for GP0! and 3P! is represented in fi ures =.,9A, and =.,9A* respectively. P!! for GP0! supports 4T0/& and G30/&. P!! for 3P! supports 3A4T0/&. 4T0/& and G30/&. 8urther details of the P!! !ervice are described in T! *;.*33 P,39C.

3GPP

elease !"

+'

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

(ontent 'o rce'

G1 AN Core Network

UE PSS (&ient
=T AN

Gi SGS, GGS,

PSS Ser7er

(ontent 'o rce'

U'er an) ter8ina& $ro5i&e'

B$erator ' network

.i/ure )$!-(!0 PSS Service Architecture for GP S

G1 AN

EP(
+*

(ontent 'o rce'

P(+!
SGi

UE PSS (&ient

=T AN

P-G=

PSS Ser7er

(ontent 'o rce'

1(=T AN

U'er an) ter8ina& $ro5i&e'

B$erator ' network

.i/ure )$!-("0 PSS Service Architecture for 1PS

"

PLM, .a'ic inter5ace' an) re5erence $oint'

The implementation of the mobile service with international roamin implies the e'chan e of data between the eDuipment involved in the service. The same &o.< si nallin networ" should be used to transfer these data and the callA related si nallin information. 3ditor#s noteE either the difference between interface and reference point should be clearly provided. or only one of the terms should be used.

3GPP

elease !"

+)

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

".1 4nter5ace' .etween Mo.i&e Station an) the !i*e) 4n5ra'tr ct re

".1.1 4nter5ace .etween Mo.i&e Station an) :a'e Station S9'te8 (U8inter5ace)
The interface between the M! and the 1!! is specified in the --A and -=Aseries of Technical !pecifications.

".1.2 4nter5ace .etween U'er E@ i$8ent an) +a)io ,etwork S9'te8 (U inter5ace)
The interface between the 43 and the 0&! is specified in the *-A and *=Aseries of Technical !pecifications.

".1.3 4nter5ace .etween U'er E@ i$8ent an) E7o&7e) UT+%, (E-UT+%, U inter5ace)
The interface between the 43 and the 3A4T0/& is specified in the 3;Aseries of Technical !pecifications.

".2 4nter5ace .etween the (ore ,etwork an) the %cce'' ,etwork
".2.1 4nter5ace' .etween the (S )o8ain an) the %cce'' ,etwork
".2.1.1 4nter5ace .etween the MS( an) :a'e Station S9'te8 (%-inter5ace)

The interface between the M!2 and its 1!! is specified in the ->Aseries of Technical !pecifications. The 1!!AM!2 interface is used to carry information concernin E A A A 1!! mana ementO call handlin O mobility mana ement.

".2.1.2

4nter5ace .etween the MS( an) :a'e Station S9'te8 (4 H(S inter5ace)

The interface between the M!2 and its 1!! is specified in the *=.-,'Aseries of Technical !pecifications. The 1!!AM!2 interface is used to carry information concernin E A A A 1!! mana ementO call handlin O mobility mana ementO

".2.1.3

4nter5ace .etween the MS( an) +,S (4 H(S inter5ace)

The interface between the M!2 and its 0&! is specified in the *=.-,'Aseries of Technical !pecifications. The 0&!AM!2 interface is used to carry information concernin E A A A 0&! mana ementO call handlin O mobility mana ement.

3GPP

elease !"

+*

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

".2.2 4nter5ace' .etween the PS )o8ain an) the %cce'' ,etwork

".2.2.1
A A

4nter5ace .etween SGS, an) :SS (G.-inter5ace)

The 1!!A!G!& interface is used to carry information concernin E pac"et data transmissionO mobility mana ement.

The Gb interface is defined in T! ->.+,- P--C. T! ->.+,; P-=C and T! ->.+,> P-;C.

".2.2.2
A A

4nter5ace .etween SGS, an) :SS (4 HPS-inter5ace)

The 1!!A!G!& interface is used to carry information concernin E pac"et data transmissionO mobility mana ement.

The %uJP! interface is defined in the *=.-,'Aseries of 3GPP Technical !pecifications.

".2.2.3
A A

4nter5ace .etween SGS, an) +,S (4 HPS-inter5ace)

The 0&!A!G!& interface is used to carry information concernin E pac"et data transmissionO mobility mana ement.

The %uJP! interface is defined in the *=.-,'Aseries of Technical !pecifications.

".2.3 4nter5ace' .etween the E7o&7e) Packet (ore an) the %cce'' ,etwork
".2.3.1 4nter5ace .etween MME an) E-UT+%, (S1-MME-inter5ace)

0eference point for the control plane protocol between 3A4T0/& and MM3. This interface is defined in the T! 3;.-,'Aseries of Technical !pecifications and in T! *-.3+, P>9C.

".2.3.2

4nter5ace .etween S-G= an) E-UT+%, (S1-U-inter5ace)

0eference point between 3A4T0/& and ! GB for the per bearer user plane tunnellin . This interface is defined in T! *9.*>, P,*;C.

".3 4nter5ace' interna& to the %cce'' ,etwork

".3.1 4nter5ace .etween :S( an) :TS (%.i'-inter5ace)
Bhen the 1!! consists of a 1ase !tation 2ontroller (1!2) and one or more 1ase Transceiver !tations (1T!). this interface is used between the 1!2 and 1T! to support the services offered to the G!M users and subscribers. The interface also allows control of the radio eDuipment and radio freDuency allocation in the 1T!. The interface is specified in the ->.='Aseries of Technical !pecifications.

".3.2 4nter5ace .etween +,( an) ,o)e : (4 .-inter5ace)

Bhen the 0&! consists of a 0adio &etwor" 2ontroller (0&2) and one or more &ode 1. this interface is used between the 0&2 and &ode 1 to support the services offered to the 4MT! users and subscribers.

3GPP

elease !"

++

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

The interface also allows control of the radio eDuipment and radio freDuency allocation in the &ode 1. The interface is specified in the *=.-3' series of Technical !pecifications.

".3.3 4nter5ace .etween two +,(' (4 r-inter5ace)

This interface is defined in the *=.-*' series of Technical !pecifications.

".3.4 4nter5ace .etween two e,:' (I2-inter5ace)

This is a lo ical interface between two e&1s. Bhilst lo ically representin a point to point lin" between e&1s. the physical reali(ation need not be a point to point lin". This interface is defined in the T! 3;.-*'Aseries of Technical !pecifications.

".3.- 4nter5ace .etween >,: an) >,:-G=(4 h-inter5ace)

This interface is specified in the T! *=.-;< P,,-C. T! *=.-;> P,,=C and T! *=.-;9 P,,;C.

".4 4nter5ace' interna& to the (ore ,etwork

".4.1 4nter5ace' interna& to the (S )o8ain
".4.1.1 4nter5ace .etween the MS( 'er7er an) it' a''ociate) VL+ (:-inter5ace)

The ?60 is the location and mana ement database for the mobile subscribers roamin in the area controlled by the associated M!2 server(s). Bhenever the M!2 server needs data related to a iven mobile station currently located in its area. it interro ates the ?60. Bhen a mobile station initiates a location updatin procedure with an M!2 server. the M!2 server informs its ?60 which stores the relevant information. This procedure occurs whenever an M! roams to another location area. /lso. when a subscriber activates a specific supplementary service or modifies some data attached to a service. the M!2 server informs (via the ?60) the G60 which stores these modifications and updates the ?60 if reDuired. This interface is internal to the M!2 server F?60O si nallin on it is not standardised.

".4.1.2

4nter5ace .etween the >L+ an) the MS( 'er7er ((-inter5ace)

The Gateway M!2 server must interro ate the G60 of the reDuired subscriber to obtain routin information for a call or a short messa e directed to that subscriber. !i nallin on this interface uses the Mobile /pplication Part (M/P). which in turn uses the services of Transaction 2apabilities (see T! *9.++* P*;C). 8or 2/M36 purposes. this interface is used as described in T! *3.+<> P,+cC. %t is used e. . at terminatin calls to e'chan e routein information. subscriber status. location information. subscription information. etc.

".4.1.3

4nter5ace .etween the >L+ an) the VL+ (6-inter5ace)

This interface is used to e'chan e the data related to the location of the mobile station and to the mana ement of the subscriber. The main service provided to the mobile subscriber is the capability to set up or to receive calls within the whole service area. To support this. the location re isters have to e'chan e data. The ?60 informs the G60 of the location of a mobile station mana ed by the latter and provides it (either at location updatin or at call setAup) with the roamin number of that station. The G60 sends to the ?60 all the data needed to support the service to the mobile subscriber. The G60 then instructs the previous ?60 to cancel the location re istration of this subscriber. 3'chan es of data may occur when the mobile subscriber reDuires a particular service. when he wants to chan e some data attached to his subscription or when some parameters of the subscription are modified by administrative means. !i nallin on this interface uses the Mobile /pplication Part (M/P). which in turn uses the services of Transaction 2apabilities (see T! *9.++* P*;C).

3GPP

elease !"

+,

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

8or 2/M36 purposes. this interface is used to send the 2/M36 related subscriber data to the visited P6M& and for provision of M!0&. The interface is also used for the other purposes described in T! *3.+<> P,+cC. e. . to retrieve subscriber status and location information of the mobile subscriber or to indicate suppression of announcement for a 2/M36 service.

".4.1.4

4nter5ace .etween MS( 'er7er' or MS( 'er7er an) 4P-SM-G= (E-inter5ace)

Bhen a mobile station moves from one M!2 area to another durin a call. a handover procedure has to be performed in order to continue the communication. 8or that purpose the M!2 servers have to e'chan e data to initiate and then to realise the operation. /fter the handover operation has been completed. the M!2 servers will e'chan e information to transfer /A or %uA interface si nallin as defined in T! *3.++9 P;C. Bhen a short messa e is to be transferred between a Mobile !tation and !hort Messa e !ervice 2entre (!2). in either direction. this interface is used to transfer the messa e between the M!2 server servin the Mobile !tation and the M!2 server which acts as the interface to the !2. or between the %PA!MAGB servin the Mobile !tation and the M!2 server which acts as the interface to the !2. !i nallin on this interface uses the Mobile /pplication Part (M/P). which in turn uses the services of Transaction 2apabilities (see T! *9.++* P*;C).

".4.1.-

4nter5ace .etween MS( 'er7er an) E4+ (!-inter5ace)

This interface is used between M!2 server and 3%0 to e'chan e data. in order that the 3%0 can verify the status of the %M3% retrieved from the Mobile !tation. !i nallin on this interface uses the Mobile /pplication Part (M/P). which in turn uses the services of Transaction 2apabilities (see T! *9.++* P*;C).

".4.1."

4nter5ace .etween VL+' (G-inter5ace)

Bhen a mobile subscriber moves from a ?60 area to another 6ocation 0e istration procedure will happen. This procedure may include the retrieval of the %M!% and authentication parameters from the old ?60. !i nallin on this interface uses the Mobile /pplication Part (M/P). which in turn uses the services of Transaction 2apabilities (see T! *9.++* P*;C).

".4.1.1

+e5erence $oint (G)MS( 'er7er J (S-MG= (Mc +e5erence Point)

The Mc reference point describes the interfaces between the M!2 !erver and 2!AMGB. and between the GM!2 !erver and 2!AMGB. %t has the followin propertiesE A A A A A full compliance with the G.*-> P=*C standard. baseline wor" of which is currently carried out in %T4AT !tudy Group ,;. in conjunction with %3T8 M3G/2O BG. fle'ible connection handlin which allows support of different call models and different media processin purposes not restricted to G.3*3 P=-C usa e. open architecture where e'tensionsFPac"a es definition wor" on the interface may be carried out. dynamic sharin of MGB physical node resources. / physical MGB can be partitioned into lo ically separate virtual MGBsFdomains consistin of a set of statically allocated Terminations. dynamic sharin of transmission resources between the domains as the MGB controls bearers and mana e resources accordin to the G.*-> P=*C protocols.

The functionality across the Mc reference point will need to support mobile specific functions such as !0&! relocationFhandover and anchorin . %t is e'pected that current G.*->F%3T8 Me aco P=*C standard mechanisms can be applied to enable this.

3GPP

elease !"

+-

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

".4.1.;

+e5erence Point MS( Ser7er J GMS( Ser7er (,c +e5erence Point)

Over the &c reference point. the &etwor"A&etwor" based call control is performed. 3'amples of this are %!4P or an evolvement of %!4P for bearer independent call control (1%22). :ifferent options for si nallin transport on &c shall be possible includin %P.

".4.1.#

+e5erence Point (S-MG= J (S-MG= (,. +e5erence Point)

Over the &b reference point the bearer control and transport are performed. The transport may be 0TPF4:PF%P P=9C. P;+C or //6* (%.3;3A*) P=<C for transport of user data. :ifferent options for user data transport and bearer control shall be possible on &b. for e'ampleE //6*FS.//6*. !TMFnone. 0TPFG.*-= P=>C. %P12.

".4.1.10

+e5erence Point .etween the (SS an) the VL+ (>7 +e5erence Point)

This reference point is used to transfer to the ?60 the 2!G subscription information stored in the ?P6M& for roamin 43s. !i nallin on this interface uses the Mobile /pplication Part (M/P). which in turn uses the services of Transaction 2apabilities (T2/P) (see T! *9.++* P*;C).

".4.2 4nter5ace' interna& to the PS )o8ain (GP+S)

".4.2.1 4nter5ace .etween SGS, an) >L+ (Gr-inter5ace)

This interface is used to e'chan e the data related to the location of the mobile station and to the mana ement of the subscriber. The main service provided to the mobile subscriber is the capability to transfer pac"et data within the whole service area. The !G!& informs the G60 of the location of a mobile station mana ed by the latter. The G60 sends to the !G!& all the data needed to support the service to the mobile subscriber. 3'chan es of data may occur when the mobile subscriber reDuires a particular service. when he wants to chan e some data attached to his subscription or when some parameters of the subscription are modified by administrative means. !i nallin on this interface uses the Mobile /pplication Part (M/P). which in turn uses the services of Transaction 2apabilities (T2/P) (see T! *9.++* P*;C).

".4.2.2

4nter5ace .etween SGS, an) GGS, (Gn- an) G$-inter5ace)

These interfaces are used to support mobility between the !G!& and GG!&. The Gn interface is used when GG!& and !G!& are located inside one P6M&. The GpAinterface is used if GG!& and !G!& are located in different P6M&s. The GnFGp interface also includes a part which allows !G!&s to communicate subscriber and user data. when chan in !G!&. !i nallin on this interface uses the 4ser :ata ram Protocol. 4:PF%P P=9C. The GnFGp interface is defined in T! *9.+;+ P=,C.

".4.2.3

Si3na&&in3 Path .etween GGS, an) >L+ (Gc-inter5ace)

This optional si nallin path may be used by the GG!& to retrieve information about the location and supported services for the mobile subscriber. to be able to activate a pac"et data networ" address. There are two alternative ways to implement this si nallin pathE A if an !!< interface is implemented in the GG!&. si nallin between the GG!& and the G60 uses the Mobile /pplication Part (M/P). which in turn uses the services of Transaction 2apabilities (T2/P) (see T! *9.++* P*;C)O if there is no !!< interface in the GG!&. any G!& in the same P6M& and which has an !!< interface installed can be used as a GTP to M/P protocol converter. thus formin a si nallin path between the GG!& and the G60.

3GPP

elease !"

,%

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

".4.2.4

4nter5ace .etween SGS, an) E4+ (G5-inter5ace)

This interface is used between !G!& and 3%0 to e'chan e data. in order that the 3%0 can verify the status of the %M3% retrieved from the Mobile !tation. !i nallin on this interface uses the Mobile /pplication Part (M/P). which in turn uses the services of Transaction 2apabilities (T2/P) (see T! *9.++* P*;C).

".4.2.-

+e5erence Point .etween the (SS an) the Gn2G$ SGS, (Gh7 +e5erence Point)

This reference point is used to transfer to the GnFGp !G!& the 2!G subscription information stored in the ?P6M& for roamin 43s. !i nallin on this interface uses the Mobile /pplication Part (M/P). which in turn uses the services of Transaction 2apabilities (T2/P) (see T! *9.++* P*;C).

".4.3 4nter5ace' 'e) .9 (S an) PS )o8ain'

".4.3.1 4nter5ace .etween MS(2VL+ an) SGS, (G'-inter5ace) 5or GP+S

The !G!& may send location information to the M!2F?60 via the optional Gs interface. The !G!& may receive pa in reDuests from the M!2F?60 via the Gs interface. The M!2F?60 may indicate to an !G!&. via the Gs interface. that an M! is en a ed in a service handled by the M!2. !i nallin on this interface uses connectionless !22P (without T2/P). !22P Global Title (GT) is used for addressin . The GsAinterface is defined in T! *9.+,; P->C and T! *9.+,> P-9C.

".4.3.2

4nter5ace .etween >L+2>SS an) % ( (>-4nter5ace)

Bhen an G60FG!! receives a reDuest for authentication and cipherin data for a Mobile !ubscriber and it does not hold the reDuested data. the G60FG!! reDuests the data from the /u2. The protocol used to transfer the data over this interface is not standardised.

".4.3.3

4nter5ace .etween SGS,24P-SM-G= an) SMS-GMS(2SMS-4=MS( (G)2G))-4nter5ace) 5or GP+S

The Gd interface may be used to transfer short messa es between !G!&. %PA!MAGB and !M!AGM!2F!M!A%BM!2 over GP0!. !i nallin on the Gd interface uses the Mobile /pplication Part (M/P) (see T! *9.++* P*;C). The Gdd interface may be used to to transfer short messa es between !G!& supportin 3P! interfaces. %PA!MAGB and !M! GM!2F!M! %BM!2. !i nallin on the Gdd interface uses the :iameter !Gd application (see T! *9.33> P,3=C).

".4.3.4

4nter5ace .etween MS(2VL+ an) MME (SG'-inter5ace) 5or EP(

The !Gs interface is the reference point between the MM3 and M!2F?60 which is used for the mobility mana ement and pa in procedures between 3P! and 2! domain. and it is based on the Gs interface procedures. The !Gs interface is used to provide 8allbac" for 6ocation !ervices (62!) and 2all %ndependent !upplementary !ervices (!!). The !Gs interface is also used for the delivery of both mobile ori inatin and mobile terminatin !M! over 34T0/& in case !M!%P is not used. The si nallin on this interface uses !2TP. The !Gs interface is defined in T! *3.*<* P>,C and T! *9.,,> P>*C.

3GPP

elease !"

,!

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

".4.3.-

4nter5ace .etween 3GPP MS( Ser7er an) MME or SGS, (S7-inter5ace)

The !v reference point provides !0?22 support for functions li"e sendin 8orward 0elocation Messa e between MM3 or !G!& and 3GPP M!2 !erver. This interface is specified in T! *9.*>+ P9,C.

".4.4 4nter5ace' interna& K re&ate) to the E7o&7e) Packet (ore

".4.4.1 4nter5ace .etween MME an) >SS (S"a-inter5ace)

This interface is used to e'chan e the data related to the location of the mobile station and to the mana ement of the subscriber. The main service provided to the mobile subscriber is the capability to transfer pac"et data within the whole service area. The MM3 informs the G!! of the location of a mobile station mana ed by the latter. The G!! sends to the MM3 all the data needed to support the service to the mobile subscriber. 3'chan es of data may occur when the mobile subscriber reDuires a particular service. when he wants to chan e some data attached to his subscription or when some parameters of the subscription are modified by administrative means. !i nallin on this interface uses :iameter !;aF!;d /pplication as specified in T! *9.*<* P>;C.

".4.4.2

4nter5ace .etween SGS, an) >SS (S")-inter5ace)

This interface is used to e'chan e the data related to the location of the mobile station and to the mana ement of the subscriber. The main service provided to the mobile subscriber is the capability to transfer pac"et data within the whole service area. The !G!& informs the G!! of the location of a mobile station mana ed by the latter. The G!! sends to the !G!& all the data needed to support the service to the mobile subscriber. 3'chan es of data may occur when the mobile subscriber reDuires a particular service. when he wants to chan e some data attached to his subscription or when some parameters of the subscription are modified by administrative means. !i nallin on this interface uses :iameter !;aF!;d /pplication as specified in T! *9.*<* P>;C.

".4.4.3

4nter5ace .etween MME an) S-G= (S11-inter5ace)

This interface is used to support mobility and bearer mana ement between the MM3 and !AGB. This interface is specified in T! *9.*<- P9+C.

".4.4.4

4nter5ace .etween MME an) MME (S10-inter5ace)

This interface is used to support user information transfer and MM3 relocation support between the MM3s. This interface is specified in T! *9.*<- P9+C.

".4.4.-

4nter5ace .etween S-G= an) P6, G= (S- an) S;-inter5ace)

These interfaces are between !AGB and P:& GB. provides support for functions for pac"et data services towards end users durin roamin and nonAroamin cases (i.e. !> is the inter P6M& variant of !=). These interfaces are specified in T! *9.*<- P9+C and T! *9.*>, P,*;C for GTP and T! *9.*<= P93C for PM%P.

".4.4."

4nter5ace .etween MME an) E4+ (S13-inter5ace)

This interface is used between MM3 and 3%0 to e'chan e data. in order that the 3%0 can verify the status of the %M3% retrieved from the Mobile !tation. !i nallin on this interface uses the :iameter !,3 /pplication. in T! *9.*<* P>;C.

".4.4.1

4nter5ace .etween MME an) SGS, (S3-inter5ace)

This interface enables user and bearer information e'chan e for inter 3GPP access networ" mobility in idle andFor active state. This interface is specified in T! *9.*<- P9+C.

3GPP

elease !"

,"

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

".4.4.;

4nter5ace .etween S-G= an) SGS, (S4-inter5ace)

This interface provides related control and mobility support between GP0! 2ore and the 3GPP /nchor function of !ervin GB. %n addition. if :irect Tunnel is not established. it provides the user plane tunnellin . This interface is specified in T! *9.*<- P9+C and T! *9.*>, P,*;C.

".4.4.#

4nter5ace .etween S-G= an) UT+%, (S12-inter5ace)

0eference point between 4T0/& and !ervin GB for user plane tunnellin when :irect Tunnel is established. %t is based on the %uAuFGnAu reference point usin the GTPA4 protocol as defined between !G!& and 4T0/& or respectively between !G!& and GG!&. 4sa e of !,* is an operator confi uration option. This interface is specified in T! *9.*>, P,*;C.

".4.4.10

4nter5ace .etween Tr 'te) non-3GPP 4P %cce'' an) S-G=2P6, G= (S2ainter5ace)

%t provides the user plane with related control and mobility support between trusted non 3GPP %P access and the Gateway. This interface is specified in T! *9.*<= P93C and T! *-.3+- P9-C for PM%P and 2lient Mobile %Pv- 8/ mode respectively. Bhen GTP is used in !*a. this interface is specified in T! *9.*<- P9+C for GTP control plane (GTPA2) and in T! *9.*>, P,*;C for GTP user plane (GTPA4).

".4.4.11

4nter5ace .etween P6, G=2S-G= an) eP6G (S2.-inter5ace)

%t provides the user plane with related control and mobility support between eP:G and the Gateway. This interface is specified in T! *9.*<- P9+C and T! *9.*>, P,*;C for GTP and in T! *9.*<= P93C for PM%P.

".4.4.12

4nter5ace .etween P6, G= an) UE (S2c-inter5ace)

%t provides the user plane with related control and mobility support between 43 and the Gateway. This reference point is implemented over trusted andFor untrusted nonA3GPP /ccess andFor 3GPP access. This interface is specified in T! *-.3+3 P9=C.

".4.4.13

4nter5ace .etween P6, G= an) 3GPP %%% Ser7er2$ro*9 (S".-inter5ace)

%t is the reference point between P:& GB and 3GPP /// serverFpro'y for mobility related authentication and authori(ation. This reference point may also be used to retrieve and reDuest stora e of mobility parameters. such as the P:& GB %dentity. This reference point may also be used to retrieve static So! profile for a 43 for nonA3GPP access in case dynamic P22 is not supported. This interface is specified in T! *9.*<3 P9;C.

".4.4.14

4nter5ace .etween Untr 'te) non-3GPP 4P %cce'' an) 3GPP %%% Ser7er2$ro*9 (S=a-inter5ace)

%t enables support for the 4ntrusted nonA3GPP %P /ccess with the 3GPP /// !erverFPro'y and transports access authentication. authori(ation and char in Arelated information in a secure manner. This interface is specified in T! *9.*<3 P9;C.

".4.4.1-

4nter5ace .etween Tr 'te) non-3GPP 4P %cce'' an) 3GPP %%% Ser7er2$ro*9 (STa-inter5ace)

%t connects the Trusted nonA3GPP %P /ccess with the 3GPP /// !erverFPro'y and transports access authentication. authori(ation. mobility parameters and char in Arelated information in a secure manner. This interface is specified in T! *9.*<3 P9;C.

".4.4.1"

4nter5ace .etween 3GPP %%% Ser7er an) 3GPP %%% $ro*9 (S=)-inter5ace)

%t connects the 3GPP /// Pro'y. possibly via intermediate networ"s. to the 3GPP /// !erver. This interface is specified in T! *9.*<3 P9;C.

3GPP

elease !"

,3

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

".4.4.11

4nter5ace .etween eP6G an) 3GPP %%% Ser7er2$ro*9 (S=8-inter5ace)

This reference point is located between 3GPP /// !erverFPro'y and eP:G and is used for /// si nallin (transport of mobility parameters. tunnel authentication and authori(ation data). This reference point also includes the M/GA/// interface functionality and Mobile %Pv; &/!A/// interface functionality. This interface is specified in T! *9.*<3 P9;C.

".4.4.1;

4nter5ace .etween eP6G an) Untr 'te) non-3GPP %cce'' (S=n-inter5ace)

This is the reference point between the 4ntrusted &onA3GPP %P /ccess and the eP:G. Traffic on this interface for a 43Ainitiated tunnel has to be forced towards eP:G. This interface is specified in T! *9.*<3 P9;C.

".4.4.1#

4nter5ace .etween eP6G an) UE (S= -inter5ace)

This is the reference point between the 43 and the eP:G and supports handlin of %P!ec tunnels. The functionality of !Bu includes 43Ainitiated tunnel establishment. user data pac"et transmission within the %P!ec tunnel and tear down of the tunnel and support for fast update of %P!ec tunnels durin handover between two untrusted nonA3GPP %P accesses. This interface is specified in T! *-.3+* P9<C.

".4.4.20

4nter5ace .etween >SS an) 3GPP %%% Ser7er (S=*-inter5ace)

This reference point is located between 3GPP /// !erver and G!! and is used for transport of authentication data. This interface is specified in T! *9.*<3 P9;C.

".4.4.21

4nter5ace .etween UE an) %,6S! (S14-inter5ace)

This reference point is between 43 and /&:!8 for direct Dueries via pull mechanism. %t enables dynamic provision of information to the 43 for &etwor" discovery and selection procedures related to nonA3GPP accesses. Push andFor combination of PullAPush may be supported as well. This interface is specified in T! *-.3+* P9<C.

".4.4.22

+e5erence $oint .etween >+6P %, an) MME (S101-re5erence $oint)

The !,+, interface supports procedures for PreA0e istration. !ession Maintenance and /ctive handovers between 3A4T0/& and G0P: networ"s. This is based on tunnellin over !,+, si nallin of one technolo y while the 43 is in the other technolo y as specified in T! *3.-+* P<<C. The G0P: air interface messa es tunnelled over !,+, in 3A4T0/& to G0P: mobility are defined in 3GPP* 2.!++>< + P,+<C.

".4.4.23

+e5erence $oint .etween 3GPP2 1*(S 4=S an) MME (S102-re5erence $oint)

The !,+* reference point provides a tunnel between MM3 and 3GPP* ,'2! %B! to relay 3GPP* ,'2! si nallin messa es in order to support !0?22 as specified in T! *3.*,; P>3C and 2! 8allbac" as specified in T! *3.*<* P>,C. ,' 2! si nallin messa es are those messa es that are defined for /*, interface as described in 3GPP* /.!+++>A2 P,+;C. %n case of 2! 8allbac" to ,' 2! networ" as specified in T! *3.*<* P>,C. !,+* Tunnel 0edirection Procedure is used when the 43 perform Trac"in /rea 4pdate with MM3 chan e (as specified in T! *3.-+* P<<C in case of !,+, tunnel redirection) while the 43 is re istered with the ,'0TT 2! domain and the !,+* session e'ists between the MM3 and the ,'2! %B!.

".4.4.24

4nter5ace .etween >SG= an) S-G= (S103-inter5ace)

The !,+3 interface between the !ervin GB and G0P: P:!& G!GB supports the forwardin of :6 data durin mobility from 3A4T0/& to G0P: as specified in T! *3.-+* P<<C. !i nallin procedures on the !,+, interface are used to set up tunnels on the !,+3 interface.

".4.4.2-

+e5erence $oint .etween UE an) (SG Li't Ser7er (Uh re5erence $oint)

This reference point is used to provision the /llowed 2!G list and the Operator 2!G list subscription information to the mobile station via OM/ :M or OT/. This interface is specified in T! *-.*>= P,,<C for OM/ :M and in T! 3,.,+* P,,>C for OT/.

3GPP

elease !"

,'

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

".4.4.2"

+e5erence Point .etween the (SS an) the S4-SGS, (S1) +e5erence Point)

This reference point is used to transfer to the !-A!G!& the 2!G subscription information stored in the ?P6M& for roamin 43s. !i nallin on this interface uses :iameter !<d /pplication as specified in T! *9.*<* P>;C.

".4.4.21

+e5erence $oint .etween the (SS an) the MME (S1a re5erence $oint)

This reference point is used to transfer to the MM3 the 2!G subscription information stored in the ?P6M& for roamin 43s. !i nallin on this interface uses :iameter !<a /pplication as specified in T! *9.*<* P>;C.

".4.4.2;

+e5erence $oint .etween the MME an) the SMS-GMS(2SMS-4=MS(2SMS +o ter (SG) re5erence $oint)

This reference point is used to transfer short messa es between the MM3 and !M!AGM!2. !M!A%BM!2 or !M! 0outer. The details for this reference point are described in T! *3.+-+ P,3<C and T! *9.33> P,3=C. !i nallin on this interface uses :iameter !Gd /pplication as specified in T! *9.33> P,3=C.

".4.4.2#

+e5erence $oint .etween the >SS an) the SMS-GMS(2SMS-4=MS(2SMS +o ter (S"c re5erence $oint)

This reference point is used to interro ate the G!! of the reDuired subscriber to obtain routin information for a short messa e directed to that subscriber. The details for this reference point are described in T! *3.+-+ P,3<C and T! *9.33> P,3=C. !i nallin on this interface uses :iameter !;c /pplication as specified in T! *9.33> P,3=C.

".4.4.30

+e5erence $oint .etween >+P6 %, an) MME (S121-inter5ace)

The !,*, interface supports 0%M messa e transfer between e&ode1 and G0P: /& as described in T! *3.-+* P<<C.

"a

PLM, '$eci5ic inter5ace'

"a.1 G(+-'$eci5ic inter5ace

"a.1.1 4nter5ace .etween the MS( an) it' a''ociate) G(+ (4-inter5ace)
The G20 is the mana ement data base for the voice roup or broadcast calls in the area controlled by the associated M!2(s). Bhenever the M!2 needs data related to a reDuested voice roup or broadcast call it interro ates the G20 to obtain the respective voice roup or broadcast call attributes. The protocol used to transfer the data over this interface is not standardi(ed.

"a.2 (7oi)) "a.3 L(S-'$eci5ic inter5ace'

"a.3.1 L(S inter5ace' 'in3 M%P
The followin interfaces are based on M/P in 62!.

3GPP

elease !"

,)

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

A A

Lh inter a!e: interface between GM62 and G60. This interface is used by the GM62 to reDuest the address of the visited M!2 or !G!& for a particular tar et 43 whose location has been reDuested (see T! *9.++* P*;C). L" inter a!e: interface between GM62 A M!2 and GM62 A !G!&. This interface is used by the GM62 to convey a location reDuest to the M!2 or !G!& currently servin a particular tar et 43 whose location was reDuested. The interface is used by the M!2 or !G!& to return location results to the GM62 (see T! *9.++* P*;C). L! inter a!e: between GM62 and sm!28. 2/M36. This interface is used to et location information for 2/M36 based services. (see T! *9.++* P*;C).

"a.3.2 (7oi))

"a.3.3 (7oi))

"a.3.4 (7oi))

"a.3.- 4nter5ace .etween :S( an) SML( (L.-inter5ace)

%n G30/&. a !M62 supports positionin via si nallin on the 6b interface to the 1!2 servin the tar et M!. !i nallin on this interface uses 1!!/PA63. which is specified in T! -9.+3, P=+C %n 4T0/&. the 6b interface is not standardi(ed. the !M62 functionality is included in !0&2.

"a.3." 4nter5ace .etween Peer SML(' (L$-inter5ace)

%n G30/&. a !M62 may support the 6p interface to enable access to information and resources owned by another !M62. !i nallin on this interface uses 1!!/PPA63. which is defined in T! -9.+3, P=+C. and !M62PP. which is specified in T! ->.+3, P-<C. %n 4T0/&. the !M62 functionality is included in !0&2 and the %ur interface shall include the 6p interface type of functionality.

"a.3.1 4nter5ace .etween :TS an) LMU (U8-inter5ace)

The 4mF4u interface specific to 62! is defined in T! --.+<, P==C.

"a.3.; 4nter5ace .etween GML( an) E*terna& L(S (&ient (Le-inter5ace)

The 6e interface is used by the e'ternal 62! client to retrieve location information from the 62! server. !i nallin on this interface may use the OM/ Mobile 6ocation Protocol (M6P) P;*C and Open !ervice /ccess /pplication Pro rammin %nterface (O!/A/P%). T! *9.,9> P;3C.

"a.3.# 4nter5ace .etween +,S an) Stan)-%&one LMU, UE (U -inter5ace)

The 4u interface is used to communicate amon the 43 Positionin entities associated with the !0&2. the 43s and the standAalone 6M4. The 4u interface may pass measurement reDuests and results to and from the 43 or the standAalone 6M4. 43 Positionin operations at the 4u interface are enerally defined in the *-A and *=Aseries of 3GPP Technical !pecifications. 8urthermore. T! *=.3+= P,+bC describes how a standAalone 6M4 may be distin uished from a normal 43.

3GPP

elease !"

,*

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

"a.3.10 4nter5ace .etween S+,( an) S%S (Stan)-%&one SML() (4 $cinter5ace)

The %upc interface defined for 62! is specified in T! *=.-=3 P;;C.

"a.3.11 4nter5ace .etween GML( an) GML( (Lr-inter5ace)

The 6r interface is used by the GM62 to communicate with other GM62s. !i nallin on this interface may use the OM/ 0oamin 6ocation Protocol (06P) P;9C.

"a.3.12 4nter5ace .etween GML( an) MME (SL3-inter5ace)

The !6 interface is used by the GM62 to communicate with MM3s. The !6 interface is defined in T! *9.,<* P,*3C.

"a.3.13 4nter5ace .etween MME an) E-SML( (SL'-inter5ace)

The !6s interface is used to convey 62! messa es between the MM3 and 3A!M62. %t is also used for tunnellin positionin protocol messa es between the 3A!M62 and either 3A4T0/& or 43 which are transparent to the MM3 as described in T! 3;.3+= P,**C. The !6s interface is defined in T! *9.,<, P,*-C.

"a.3.14 4nter5ace .etween GML( an) >SS (SLh-inter5ace)

!6h interface between GM62 and G!!. This interface is used by the GM62 to reDuest the address of the visited MM3 for a particular tar et 43 whose location has been reDuested. The !6h interface is defined in T! *9.,<3 P,*=C.

"a.3.1- 4nter5ace .etween GML( an) SGS, (L3)-inter5ace)

6 d is the interface that is used by the GM62 to convey a location reDuest to the !G!& currently servin a particular tar et 43 whose location was reDuested. The interface is also used by the !G!& to return location results to the GM62. This interface is applicable only for an !G!& supportin 3P! based interfaces and protocols. The 6 d interface is defined in T! *9.,<* P,*3C.

"a.4 (%MEL-'$eci5ic inter5ace'

The 2/M36Aspecific interfaces are detailed in T! *3.+<> P,+cC. These interfaces are.

"a.4.1

GMS( - 3'8SS! inter5ace

This is an internal interface. The interface is described in the specification to ma"e it easier to understand the handlin of :etection Points (armin Fdisarmin of :Ps. :P processin etc.).

"a.4.2

3'8SS! - 3'8S(! inter5ace

This interface is used by the sm!28 to control a call in a certain sm!!8 and to reDuest the sm!!8 to establish a connection with a sm!08. 0elationships on this interface are opened as a result of the sm!!8 sendin a reDuest for instructions to the sm!28.

"a.4.3

MS( - 3'8SS! inter5ace

This is an internal interface. The interface is described in the specification to ma"e it easier to understand the handlin of :Ps (armin Fdisarmin of :Ps. :P processin etc.).

"a.4.4

3'8S(! - >L+ inter5ace

This interface is used by the sm!28 to reDuest information from the G60. /s a networ" operator option the G60 may refuse to provide the information reDuested by the sm!28.

3GPP

elease !"

,+

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

This interface is also used for 4!!: operations. both for sm!28Ainitiated dialo ues and M!Ainitiated dialo ues (relayed via G60). %t is a networ" operator option whether to support or not 4!!: operations on this interface.

"a.4.-

3'8S(! - 3'8S+! inter5ace

This interface is used by the sm!28 to instruct the sm!08 to play tonesFannouncements to the users.

"a.4."

MS( - 3'8S(! inter5ace

This interface is used by the M!2 to send supplementary service invocation notifications to the sm!28.

"a.4.1

SGS, - 3$r'SS! inter5ace

This is an internal interface. The interface is described in the specification to ma"e it easier to understand the handlin of :Ps (armin Fdisarmin of :Ps. :P processin etc.).

"a.4.;

3$r'SS! - 3'8S(! inter5ace (Ge +e5erence Point)

This interface is used by the sm!28 to control a GP0! session or individual P:P 2onte't in a certain prs!!8. 0elationships between the prs!!8 and the sm!28 (GP0! dialo ues) on this interface are opened as a result of the prs!!8 sendin a reDuest for instructions to the sm!28. This interface is also "nown as Ge reference point (see T! *3.+;+ P9aC).

"a.- (:S-'$eci5ic inter5ace'

"a.-.1 4nter5ace .etween the (:( an) +,S (4 H:( 4nter5ace)
The interface between the 212 and the 0&! is specified in the *=.-,'Aseries of Technical !pecifications. The 212A0&! interface is used to carry information concernin E A A the 21! messa es itselfO and 21! delivery parameter.

"a.-.2 4nter5ace .etween the (:( an) MME (S:c 4nter5ace)

0eference point between 212 and MM3 for warnin messa e delivery and control functions. This interface is specified in T! *9.,;> P9>C.

"a.-.3 4nter5ace .etween the (:( an) :S(

The interface between the 212 and the 1!2 is specified in T! ->.+-9 P,,9C. The 212A1!2 interface is used to carry information concernin E A A the 21! messa e and the warnin messa e itselfO and 21! messa e and warnin messa e delivery parameters.

3GPP

elease !"

,,

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

"a." , 8.er $orta.i&it9 '$eci5ic inter5ace'

"a.".1 4,-.a'e) 'o& tion
"a.".1.1 ,P6: to MS( inter5ace

4pon receivin an %!4P %/M. the ( ateway or visited) M!2 send a database Duery to the &P:1 as a result of analysis of the received M!%!:&. The M!%!:& is included in the Duery to the &P:1. The &P:1 determines whether the M!%!:& is ported or not. %f not. it responds bac" to the M!2 to continue the normal call setup procedure for MT calls (optionally providin the 0outin &umber). %f it is ported. the &P:1 responds bac" to the M!2 with a 0outin &umber pointin out the !ubscription networ".

"a.".2 Si3na&&in3 +e&a9-.a'e) 'o& tion

"a.".2.1 GMS( to M,P-S+! inter5ace

4pon receivin an %!4P %/M. the ateway M!2 sends a routin interro ation to the M&PA!08. which in turn will perform one of the actions. described in clause -a.<. dependin on the portability status of the subscriber and the networ" confi uration (see T! *3.+;; P-+C).

"a.".2.2

M,P-S+! to >L+ inter5ace

Bhen the M&PA!08 receives a routin interro ation from the GM!2 or an interro atin networ" entity (nonFcall related si nallin ). and it determines that the subscriber is not ported or it has been ported from another networ". the M&PA!08 relays the messa e to the G60.

"a.1 4M S .'9'te8 +e5erence Point'

"a.1.1 +e5erence Point >SS J (S(! ((* +e5erence Point)
The 2' reference point supports information transfer between 2!28 and G!!. The main procedures that reDuire information transfer between 2!28 and G!! are ,) Procedures related to !ervin 2!28 assi nment *) Procedures related to routin information retrieval from G!! to 2!28 3) Procedures related to authorisation (e. .. chec"in of roamin a reement) -) Procedures related to authenticationE transfer of security parameters of the subscriber between G!! and 2!28 =) Procedures related to filter controlE transfer of filter parameters of the subscriber from G!! to 2!28 8urther information on the 2' reference point is provided in T! *3.**> P3-C.

"a.1.2 +e5erence Point (S(! J UE (G8 +e5erence Point)

The Gm reference point supports the communication between 43 and %M 2& subsystem. e. . related to re istration and session control. The protocol used for the Gm reference point is !%P (as defined by 082 3*;, P;,C. other relevant 082#s. and additional enhancements introduced to support 3GPPUs needs).

"a.1.3 +e5erence Point MG(! J 4MS-MG= (Mn +e5erence Point)

The Mn reference point describes the interfaces between the MG28 and %M!AMGB in the %M!. %t has the followin propertiesE

3GPP

elease !"

,-

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

full compliance with the G.*-> standard functions for %M! K P!T&FP6M& interwor"in .A fle'ible connection handlin which allows support of different call models and different media processin purposes not restricted to G.3*3 P=-C usa e. open architecture where e'tensionsFPac"a es definition wor" on the interface may be carried out. dynamic sharin of %M!AMGB physical node resources. / physical %M!AMGB can be partitioned into lo ically separate virtual MGBsFdomains consistin of a set of statically allocated Terminations. dynamic sharin of transmission resources between the domains as the %M!A MGB controls bearers and mana e resources accordin to the G.*-> P=*C protocols and functions for %M!.

A A A

"a.1.4 +e5erence Point MG(! J (S(! (M3 +e5erence Point)

The M reference point allows the MG28 to forward incomin session si nallin (from the circuit switched networ") to the 2!28 for the purpose of interwor"in with circuit switched networ"s. The protocol used for the M reference point is !%P (as defined by 082 3*;, P;,C. other relevant 082#s. and additional enhancements introduced to support 3GPPUs needs).

"a.1.- (7oi))

"a.1.-a +e5erence Point %S-M+!( 5or 8e)ia contro& ((r +e5erence Point)
The 2r reference point allows interaction between an /pplication !erver and an M082 for media control. The 2r reference point enables the M082 to fetch and cache documents and resources from an /pplication !erver and to return data to an /pplication !erver. The 2r reference point enables media control protocol reDuests. responses and notifications to be sent between the M082 and an /pplication !erver. 8urther information on the 2r reference point is provided in T! *3.*,> P,,3C.

"a.1.-. +e5erence Point %S-M+!( 5or 'e''ion contro& (Mr +e5erence Point)
The Mr# reference point allows interaction between an /pplication !erver and an M082 for session control without passin throu h an !A2!28. 8urther information on the Mr# reference point is provided in T! *3.*,> P,,3C.

"a.1." +e5erence Point (S(! - M+!( (Mr +e5erence Point)

The Mr reference point allows interaction between an !A2!28 and an M082. The protocol used for the Mr reference point is !%P (as defined by 082 3*;, P;,C. other relevant 082#s. and additional enhancements introduced to support 3GPPUs needs).

"a.1."a +e5erence Point M+!( J M+!P (M$ +e5erence Point)

The Mp reference point allows an M082 to control media stream resources provided by an M08. The Mp reference point has the followin propertiesE A A 8ull compliance with the G.*-> P=*C standard. Open architecture where e'tensions (pac"a es) definition wor" on the interface may be carried out.

3GPP

elease !"

-%

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

"a.1.1 +e5erence Point (S(! J (S(! (Mw +e5erence Point)

The Mw reference point allows the communication and forwardin of si nallin messa in between 2!28s. e. . durin re istration and session control.

"a.1.; (7oi))

"a.1.;a +e5erence Point (S(! J M+: (4S( +e5erence Point)

This interface is used with an M01 operatin in %nA6ine mode and is described further in T! *3.*,> P,,3C). The !A2!28 receives a session initiation reDuest from an M01 that ori inated from an /pplication !erver reDuestin M08 resources and whose destination is an M08 resource identified by the M01. The !A2!28 routes the messa e to the identified M082. !ubseDuent messa es in the same session dialo between the /! and M082 traverse the M01 as well as the !A2!28.

"a.1.# (7oi))

"a.1.#a +e5erence Point %S J M+: (+c +e5erence Point)

The 0c reference point is used by the /! to reDuest that media resources be assi ned to a call when utili(in an M01 in both Suery and %nA6ine modes (as described in T! *3.*,> P,,3C).

"a.1.10 +e5erence Point (S(! J :G(! (Mi re5erence $oint)

This reference point allows the !ervin 2!28 to forward the session si nallin to the 1rea"out Gateway 2ontrol 8unction for the purpose of interwor"in to the circuit switched networ"s. The Mi reference point is based on e'ternal specifications i.e. !%P P;,C.

"a.1.11 +e5erence Point :G(! J MG(! (ML re5erence $oint)

This reference point allows the 1rea"out Gateway 2ontrol 8unction to e'chan e session si nallin messa e with the Media Gateway 2ontrol 8unction for the purpose of interwor"in to the circuit switched networ"s. or for transit scenarios. The Mj reference point is based on e'ternal specifications i.e. !%P P;,C.

"a.1.12 +e5erence Point :G(!24:(! J :G(! (Mk re5erence $oint)

This reference point allows the 1rea"out Gateway 2ontrol 8unctionF%128 to forward the session si nallin to another 1rea"out Gateway 2ontrol 8unction. The M" reference point is based on e'ternal specifications i.e. !%P P;,C.

"a.1.13 +e5erence Point (S(!- SL! (6* +e5erence Point)

This interface between 2!28 and !68 is used to retrieve the address of the G!! which holds the subscription for a iven user or information related to a service. This interface is not reDuired in a sin le G!! environment. /n e'ample for a sin le G!! environment is a server farm architecture. :etails are described in T! *3.**> P3-C. clause =.>.,.

3GPP

elease !"

-!

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

"a.1.14 +e5erence Point to 4P7" network 'er7ice' (M. re5erence $oint)

?ia the Mb reference point %Pv; networ" services are accessed. These %Pv; networ" services are used for user data transport. &ote. that GP0! provides %Pv; networ" services to the 43. i.e. the GP0! Gi reference point and the %M! Mb reference point may be the same.

"a.1.1- +e5erence Point S-(S(! J %S (4S( +e5erence Point)

This interface between !ervin 2!28 and the /pplication !ervers (i.e.. !%P /pplication !erver. O!/ !ervice 2apability !erver. or 2/M36 %MA!!8) is used to provide services for the %M!. :etails are described in T! *3.**> P3-C. clause -.*.-.

"a.1.1-a +e5erence Point E-(S(! - E%T! (44 +e5erence Point)

This is the interface between the 3mer ency 2!28 and the 3/T8 in servin networ" (i.e. 3/T8 as defined in T! *3.,;< P<-C). it is used to provide services for emer ency sessions.

"a.1.1-. +e5erence Point 4-(S(! - E%T! (4- +e5erence Point)

This is the interface between the %nterro atin 2!28 and the 3/T8 in servin networ" (i.e. 3/T8 as defined in T! *3.,;< P<-C). it is used to provide services for emer ency sessions.

"a.1.1" +e5erence Point >SS J S4P %S or BS% S(S (Sh +e5erence Point)
The /pplication !erver (!%P /pplication !erver andFor the O!/ !ervice 2apability !erver) may communicate to the G!!. The !h interface is used for this purpose. :etails are described in T! *3.**> P3-C. clause -.*.-. This reference point is also used to e'chan e si nallin between %PA!MAGB and the G!! for !M!%P delivery.

"a.1.11 +e5erence Point >SS J (%MEL 4M-SS! (Si +e5erence Point)

The 2/M36 /pplication !erver (%MA!!8) may communicate to the G!!. The !i interface is used for this purpose. :etails are described in T! *3.**> P3-C. clause -.*.-.

"a.1.1; +e5erence Point UE J %S (Ut +e5erence Point)

The 4t interface resides between the 43 and the !%P /pplication !erver. The 4t interface enables the user to mana e information related to his services. !uch as creation and assi nment of Public !ervice %dentities. mana ement of authori(ation policies that are used e. . by Presence service. conference policy mana ement. etc. The /! may need to e'hibit security related functions for the 4t interface. the details of these security functions are described in T! 33.*** P<*C. 8or the protocol at the 4t reference point GTTP shall be supported.

"a.1.1# +e5erence Point %S- SL! (6h +e5erence Point)

This interface between /! and !68 is used to retrieve the address of the G!! which holds the subscription for a iven user. This interface is not reDuired in a sin le G!! environment. /n e'ample for a sin le G!! environment is a server farm architecture. :etails are described in T! *3.**> P3-C. clause =.>.,.

3GPP

elease !"

-"

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

"a.1.20 +e5erence Point (S(!2:G(! - 4:(! (M* +e5erence Point)

The M' reference point allows the communication and forwardin of si nallin messa es between a 2!28F1G28 and an %128. e. . durin session establishment.

"a.1.21 +e5erence Point 4:(! - TrG= (4* +e5erence Point)

This interface is used by the %128 to control the TrGB. e. . to reDuest networ" address translation bindin .

"a.1.22 +e5erence Point 4-(S(! J %S (Ma +e5erence Point)

This interface between %nterro atin A2!28 and the /pplication !ervers (i.e. !%P /pplication !erver. O!/ !ervice 2apability !erver. or 2/M36 %MA!!8) is used toE A A forward !%P reDuests destined to a Public !ervice %dentity hosted by an /pplication !erver directly to the /pplication !erver. :etails are described in T! *3.**> P3-C. clause =.-.,*O and initiate a reDuest on behalf of a user or Public !ervice %dentity. if the /! has no "nowled e of the servin !A2!28 for that user or Public !ervice %dentity. :etails are described in T! *3.**> P3-C. clause =.;.=.3.

"a.1.23 +e5erence Point P-(S(! J 4MS %cce'' Gatewa9 (4@ +e5erence Point)
The %D reference point is between the Pro'yA2!28 and the %M! /ccess Gateway. %t conveys the necessary information that is needed to allocate and release transport addresses. :etails are described in T! *3.**> P3-C. /nne' G.

"a.1.23a +e5erence Point E-(S(! - L+! (M& +e5erence Point)

The Ml reference point allows the 3A2!28 to reDuest the 608 to validate the location information received from the 43. to determine or Duery the 608 for routin information to emer ency centres. 6ocation information may be received from 608 andFor reference "ey to allow the P!/P to retrieve location at a later sta e.

"a.1.24 +e5erence Point 4:(! - 4:(! (4ci +e5erence Point)

The %ci reference point allows two %128s to communicate with each other in order to provide the communication and forwardin of si nallin messa in between %M 2& subsystem networ"s.

"a.1.2- +e5erence Point TrG= - TrG= (4?i +e5erence Point)

The %(i reference point allows two TrGBs to forward media streams between %M 2& subsystem networ"s.

"a.1.2" Voi)

"a.1.21 +e5erence Point MS( Ser7er - (S(! (42 +e5erence Point)

The %* reference point is used to route session control si nallin between the M!2 !erver and the %M!. as defined in T! *3.*9* P,,+C and in T! *3.*3< P,,,C. This can be a roamin and interAoperator reference point. %* is used to support one or more of the followin featuresE A A /n M!2 !erver enhanced for %2!. as defined in T! *3.*9* P,,+C. /n M!2 !erver enhanced for %2! and !0?22. as defined in T! *3.*9* P,,+C. T! *3.*,; P>3C and T! *3.*3< P,,,C.

3GPP

elease !"

-3

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

A A

/n M!2 !erver enhanced for %2! and !0?22 with the M!2 !erver assisted midAcall feature as defined in T! *3.*3< P,,,C. /n M!2 !erver enhanced for %2! and !0?22 with the !0?22 for call in alertin phase feature as defined in T! *3.*3< P,,,C.

"a.1.2; +e5erence Point MS( Ser7er - T%S (43 +e5erence Point)

The %3 reference point is used between the M!2 !erver enhanced for %2! and the T/! to interwor" 2! si nallin and communication service settin procedures. as defined in T! *3.*9* P,,+C.

"a.1.2# +e5erence Point 4(S UE J S(( %S (41 +e5erence Point)

The %, reference point is used between the %2! 43 and the !22 /! for service control si nallin over 2! access. as defined in T! *3.*9* P,,+C.

"a.; Voi) "a.# +e5erence Point' 5or 3GPP2=L%, 4nterworkin3

&OT3E Bith the introduction of 3volved Pac"et 2ore !ystem. the 3GPP /// server and 3GPP /// Pro'y provide a set of different and additional functions as specified in the 3P2 specific section of this specification.

"a.#.1 +e5erence $oint 3GPP %%% Ser7er - >L+ (6E2GrE +e5erence Point)
This is the reference point between the 3GPP /// server and the G60 up to and includin 0elA- and the G!! in 0elA=. The functionality of this reference point is similar to that of the B' reference point. 8or more information see T! *3.*3- P;<C.

"a.#.2 +e5erence $oint =L%, acce'' network - 3GPP %%% Pro*92Ser7er (=a +e5erence Point)
This is the reference point between the B6/& access networ" and 3GPP /// Pro'y or !erver. The /// protocol on this reference point is used to transport authentication. authori(ation and char in data.

"a.#.3 +e5erence $oint 3GPP %%% Ser7er J 3GPP %%% Pro*9 (=) +e5erence Point)
This is the reference point between the 3GPP /// !erver and Pro'y. the purpose of the protocols crossin this reference point is to transport authentication. authori(ation and related information. 8or more information see T! *3.*3- P;<C.

"a.#.4 +e5erence $oint 3GPP %%% Ser7er2Pro*9 - =%G (=3 +e5erence Point)
This is the reference point between the 3GPP /// serverFpro'y and B/G. %t is used to provide information needed by the B/G to perform policy enforcement functions for authorised users and to transport perAtunnel based char in information from the B/G to the /// Pro'y in roamin scenarios.

3GPP

elease !"

-'

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

"a.#.- +e5erence $oint P6G - $acket )ata network' (=i +e5erence Point)
This is the reference point between the P:G and a pac"et data networ". %t may be an operator e'ternal public or private pac"et data networ" or an intra operator pac"et data networ". e. . for provision of %M! services.

"a.#." +e5erence Point 3GPP %%% Ser7er2Pro*9 - P6G (=8 +e5erence Point)
This is the reference point between the 3GPP /// serverFpro'y and P:G. The functionality of this reference point is to enableE A A A The 3GPP /// !erverFPro'y to retrieve tunnellin attributes and B6/& 43#s %P confi uration parameters fromFvia Pac"et :ata Gateway 2arryin messa es for service authentication and authori(ation 2arryin authentication data for the purpose of tunnel establishment. tunnel data authentication and encryption.

8or more information see T! *3.*3- P;<C.

"a.#.1 +e5erence Point =%G - =L%, acce'' network (=n +e5erence Point)
This is the reference point between the B/G and the B6/& access networ". %t is used to force traffic between a B6/& 43 and P:G to o throu h the B/G.

"a.#.; +e5erence Point =%G - P6G (=$ +e5erence Point)

This is the reference point between B/G and P:G. %t is used to transport the Bu reference point protocol data pac"ets.

"a.#.# +e5erence $oint =L%, UE - P6G (= +e5erence Point)

This is the reference point between the 3GPP B6/& 43 and P:G. The functionality of this reference point is to establish a tunnel between B6/& 43 and P:G and to e'chan e data pac"ets between B6/& 43 and P:G.

"a.#.10 +e5erence $oint =L%, UE - =L%, acce'' network (=w +e5erence Point)
This is the reference point between the 3GPP B6/& 43 and B6/& access networ". The functionality of this reference point is specified by %333 and outside the scope of 3GPP.

"a.#.11 +e5erence $oint 3GPP %%% Ser7er - >SS (=* +e5erence Point)
This is the reference point between the 3GPP /// server and G!!. The functionality of this reference point is to enableE A A A A A A 0etrieval of authentication vectors 0etrieval of B6/& accessArelated subscriber information (profile) 0e istration of the 3GPP /// !erver of an authorised B6/& user in the G!! %ndication of chan e of subscriber profile 0etrieval of online char in F offline char in function addresses from G!!. 0etrieval of service related information

8or more information see T! *3.*3- P;<C.

3GPP

elease !"

-)

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

"a.#.12 +e5erence $oint 3GPP %%% Ser7er - SL! (6w re5erence $oint)
This reference point is between the 3GPP /// !erver and the !68. The prime purpose of the protocol(s) crossin this reference point is to enable the 3GPP /// !erver to find the address of the G!! which holds the subscriber data for a iven user identity in a confi uration with multiple separately addressable G!!s.

"a.10 M:MS '$eci5ic re5erence $oint' 5or GP+S

"a.10.1 +e5erence $oint GGS, J :M-S( (G8. +e5erence Point)
This reference point is used to e'chan e si nallin between GG!& and 1MA!2. This represents the networ" side boundary of the M1M! 1earer !ervice from a control plane perspective. This includes user specific Gmb si nallin and M1M! bearer service specific si nallin . The details for this reference point are described in T! *3.*-; P<+C and T! *9.+;, P,+-C.

"a.10.2 +e5erence $oint :M-S( J :M-S( (M? +e5erence Point)

This reference point is the roamin variant of the Gmb reference point and is used to e'chan e si nallin between a 1MA!2 in the ?P6M& and a 1MA!2 in the GP6M&. The details for this reference point are described in T! *3.*-; P<+C and T! *9.+;, P,+-C.

"a.10.3 +e5erence $oint GGS, J +,S (or :SS 4 8o)e) (G8c +e5erence Point)
This reference point is used between GG!& and 0&! (or 1!! %u mode) for M1M! data delivery usin %P multicast. The details for this reference point are described in T! *3.*-; P<+C and T! *9.*>, P,*;C.

"a.11 M:MS '$eci5ic re5erence $oint' 5or EPS

"a.11.1 +e5erence $oint M:MS-G= J :M-S( (SG8. +e5erence Point)
This reference point is used to e'chan e si nallin between M1M!AGB and 1MA!2. This represents the networ" side boundary of the M1M! 1earer !ervice from a control plane perspective. This includes M1M! bearer service specific si nallin . The details for this reference point are described in T! *3.*-; P<+C and T! *9.+;, P,+-C.

"a.11.2 +e5erence $oint M:MS-G= J :M-S( (SGi-8. +e5erence Point)

This reference point is used between M1M!AGB and 1MA!2 for M1M! data delivery. The details for this reference point are described in T! *3.*-; P<+C and T! *9.+;, P,+-C.

"a.11.3 +e5erence $oint M:MS-G= - MME (S8 +e5erence Point)

This reference point is used to e'chan e si nallin between M1M!AGB and MM3 for M1M! !ession 2ontrol. The details for this reference point are described in T! *3.*-; P<+C and T! *9.*<- P9+C.

"a.11.4 +e5erence $oint M:MS-G= J SGS, (Sn +e5erence Point)

This reference point is used to e'chan e si nallin between M1M!AGB and !-A!G!& for M1M! !ession 2ontrol and for M1M! data delivery in pointAtoApoint mode. The details for this reference point are described in T! *3.*-; P<+C and T! *9.*<- P9+C.

3GPP

elease !"

-*

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

"a.11.- +e5erence $oint M:MS-G= J E-UT+%,2UT+%, (M1 +e5erence Point)

This reference point is used between M1M!AGB and 3A4T0/&F4T0/& for M1M! data delivery usin %P Multicast. The details for this reference point are described in T! *3.*-; P<+C. T! *9.*>, P,*;C and T! 3;.--= P,*9C.

"a.11." +e5erence $oint MME J M(E (M3 +e5erence Point)

This reference point is used to e'chan e si nallin between MM3 and M23 for M1M! !ession 2ontrol. The details for this reference point are described in T! *3.*-; P<+C. T! 3;.3++ P<>C and T! 3;.--- P,*>C.

"a.11.1 +e5erence $oint M(E - e,o)e: (M2 +e5erence Point)

This reference point is used to e'chan e si nallin between M23 and e&ode1 for M1M! !ession 2ontrol. The details for this reference point are described in T! *3.*-; P<+C. T! 3;.3++ P<>C and T! 3;.--3 P,*<C.

"a.12 +e5erence Point' 5or 3GPP Generic U'er Pro5i&e (GUP)

"a.12.1 +e5erence Point GUP Ser7er J %$$&ication' (+3 +e5erence Point)
The 0 reference point resides between the G4P !erver and the /pplications. The 0 reference point allows applications to create. read. modify and delete any user profile data usin the harmoni(ed access interface. The G4P !erver locates the data repositories responsible of the stora e of the reDuested profile component(s). The details of the 0 reference point are described in T! *3.*-+ P<,C.

"a.12.2 +e5erence Point GUP Ser7er J >SS an) %$$&ication' J >SS (+$ +e5erence Point)
The 0p reference point resides between the G4P !erver and the G!!. and between the /pplications and the G!!. The 0p reference point enables the G4P !erver and the /pplications to access G4P :ata 0epositories. The G!! is one of the G4P :ata 0epositories. %t stores the %M 2& !ubsystem user related data. The details of the 0p reference point are described in T! *3.*-+ P<,C.

"a.13 +e5erence Point' 5or Po&ic9 an) (har3in3 (ontro&

"a.13.1 +e5erence Point P(E! - P(+!2>-P(+!2V-P(+! (G* +e5erence Point)
This interface provides transfer of policy and char in rules from P208 to Policy and 2har in 3nforcement 8unction Point (P238) in the GB (e. . GG!&. P:& GB). This interface is specified in T! *9.*,* P99C.

"a.13.2 +e5erence Point P(+! - %$$&ication ! nction (+* +e5erence Point)

This interface allows for dynamic So! and char in Arelated service information to be e'chan ed between the Policy and 2har in 0ules 8unction (P208) and the /pplication 8unction (/8). This information is used by the P208 for the control of service data flows and %P bearer resources. 8or more information see T! *3.*+3 P<3C.

3GPP

elease !"

-+

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

"a.13.3 +e5erence Point SP+ J P(+! (S$ +e5erence Point)

This interface allows for the P208 to reDuest subscription information from the !P0 and the !P0 to notify the P208 when the subscription information has chan ed if the P208 has reDuested such notifications. The details associated with the !p reference point are not specified in this 0elease.

"a.13.4 +e5erence Point B(S J P(E! (G9 +e5erence Point)

This interface allows for the online char in based on the :iameter credit control application between the Online 2har in !ystem (O2!) and the P238. 8or more information see T! 3*.*=, P,+,C and 082 -++; P,+*C.

"a.13.- +e5erence Point B!(S J P(E! (G? +e5erence Point)

This interface allows for the offline char in based on the char in record data transfer between the Offline 2har in !ystem (O82!) and the P238. 8or more information see T! 3*.*9= P,+9C.

"a.13." +e5erence Point Tr 'te) non-3GPP 4P %cce'' an) P(+!2VP(+! (G*a +e5erence Point)
This interface provides transfer of (So!) policy information from P208 to the Trusted &onA3GPP accesses. This interface is specified in T! *9.*,* P99C..

"a.13.1 +e5erence Point eP6G an) P(+!2VP(+! (G*. +e5erence Point)

This interface is not specified within this release of the specification.

"a.13.1a +e5erence Point eP6G an) P(+!2VP(+! (G*.M +e5erence Point)

The reference point transports access information from eP:G to P208FvP208 for B6/& 43s such as the 43 local %P address and the 4:P port number. This interface is specified in T! *9.*,* P99C. G'bM is only applicable to the interwor"in with 8i'ed 1roadband /ccess networ".

"a.13.; +e5erence $oint .etween S-G= an) P(+!2VP(+! (G*c-inter5ace)

This interface provides transfer of (So!) policy information from P208 to the !ervin Gateway. G'c is used only in the case of PM%PAbased !=F!>. This interface is specified in T! *9.*,* P99C..

"a.13.# +e5erence Point P(+!2VP(+! J ::E+! (G** +e5erence Point)

This interface allows for a P208 to have a dynamic control over the 1earer 1indin and 3vent 0eport 8unction (11308) behaviour. 8or more information see T! *3.-+* P<<C and T! *3.*+3 P<3C. This interface is specified in T! *9.*,3 P9*C

"a.13.10

+e5erence Point >P(+! - VP(+! (S#- inter5ace)

This interface provides transfer of policy and char in rules (in case of local brea"out of traffic) andFor (So!) policy information (when G'' interface applies) between the Gome P208 and the ?isited P208 in order to support P22 roamin related functions. This interface is specified in T! *9.*,= P,+3C.

"a.13.11

+e5erence Point U6+ J P(+! (U) +e5erence Point)

This interface allows for the P208. actin as an 4:2 /pplication 8rontend as defined in T! *3.33= P,*+C. to reDuest subscription information from the 4:0 and the 4:0 to notify the P208 when the subscription information has chan ed if the P208 has reDuested such notifications. 8or details re ardin the 4d reference point see T! *3.33= P,*+C and T! *9.33= P,*,C.

3GPP

elease !"

-,

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

"a.13.12

+e5erence Point T6! - P(+!2>-P(+!2V-P(+! (S) +e5erence Point)

The !d 0eference Point enables a P208 to have dynamic control over the application detection and control behaviour at a T:8. The !d 0eference Point is specified in T! *9.*,* P99C.

"a.13.13

+e5erence Point B(S - P(+!2>-P(+! (S9 +e5erence Point)

The !y 0eference Point enables transfer of information relatin to subscriber spendin from O2! to P208. The !y 0eference Point is specified in T! *9.*,9 P,3,C.

"a.13.14

+e5erence Point >,: G= - P(+!2V-P(+! (S1- +e5erence Point)

This reference point supports the initiation. modification and termination of sessions between the G&1 GB and P208 to support 2! sessions. %t tri ers the P208 to reDuest allocation of resources in the 8i'ed 1roadband access networ" for G&1 2! calls. This interface is specified in T! *9.*,* P99C. !,= is only applicable to the interwor"in with 8i'ed 1roadband /ccess networ".

"a.13.1-

+e5erence Point :P(! - P(+!27-P(+! (S#a +e5erence Point)

This interface supports the transfer of (So!) policy information from P208 to 1P28 of broadband access networ". This interface is specified in T! *9.*,= P,+3C. !9a is only applicable to the interwor"in with 8i'ed 1roadband /ccess networ".

"a.13.1"

+e5erence Point B(S - T6! (G9n +e5erence Point)

The Gyn 0eference Point allows for the online char in based on the :iameter credit control application between the Online 2har in !ystem (O2!) and the T:8. 8or more information see T! 3*.*=, P,+,C and 082 -++; P,+*C.

"a.13.11

+e5erence Point B!(S - T6! (G?n +e5erence Point)

The G(n 0eference Point allows for the offline char in based on the char in record data transfer between the Offline 2har in !ystem (O82!) and the T:8. 8or more information see T! 3*.*9= P,+9C.

"a.14 SMS4P '$eci5ic re5erence $oint'

"a.14.1 +e5erence $oint 4P-SM-G= J >SS (G +e5erence Point)
This reference point is used to e'chan e si nallin between %PA!MAGB and the G!! for !M!%P delivery. The details for this reference point are described in T! *3.*+- P<=C.

"a.1- U'er 6ata (on7er3ence '$eci5ic re5erence $oint'

"a.1-.1 +e5erence $oint %$$&ication !ront En)' - U6+ (U) +e5erence Point)
This reference point is used to e'chan e user between /pplication 8ront 3nds and the 4:0. The details for this reference point are described in T! *3.33= P,*+C and T! *9.33= P,*,C.

3GPP

elease !"

--

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

"a.1" S$eci5ic re5erence $oint' 5or 5aci&itatin3 co88 nication' with $acket )ata network' an) a$$&ication'
"a.1".1 +e5erence $oint MT(-4=! - S(S (T'$ re5erence $oint)
This reference point is used between the MT2A%B8 and the !ervices 2apability !erver (!2!) to invo"e specific functionalities in the P6M& such as device tri erin . The details for this reference point are described in T! *3.;>* P,3*C and T! *9.3;> P,3;C. This interface is a P6M& internal interface if the !2! is controlled by the operator. !i nallin on this interface uses :iameter Tsp /pplication as specified in T! *9.3;> P,3;C. &OT3E !ee clause <.> when the !2! is not controlled by the operator.

"a.1".2 +e5erence $oint MT(-4=! - >SS2>L+ (S"8 re5erence $oint)

This reference point is used between the MT2A%B8 and the G!!FG60 to authori(e a certain !2! to reDuest a specific service (e. . device tri erin ). and to retrieve subscription information and routin information (i.e. servin !G!&FMM3FM!2 identities) from the G!!FG60. The details for this reference point are described in T! *3.;>* P,3*C and T! *9.33; P,33C. !i nallin on this interface uses :iameter !;m /pplication as specified in T! *9.33; P,33C.

"a.1".3 +e5erence $oint MT(-%%% - >SS2>L+ (S"n re5erence $oint)

This reference point is used between the MT2A/// and the G!!FG60 to translate an %M!% to e'ternal identifier(s) of the user. The details for this reference point are described in T! *3.;>* P,3*C and T! *9.33; P,33C. !i nallin on this interface uses :iameter !;n /pplication as specified in T! *9.33; P,33C.

"a.1".4 +e5erence $oint MT(-4=! - SMS-S( (T4 re5erence $oint)

This reference point is used between the MT2A%B8 and the !M!A!2 to transfer device tri er to the !M!A!2 inside the GP6M&. The details for this reference point are described in T! *3.;>* P,3*C and T! *9.33< P,3-C. !i nallin on this interface uses :iameter T- /pplication as specified in T! *9.33< P,3-C.

+e5erence $oint' .etween the PLM, an) other network'

The reference points between the P6M& and other networ"s. includin dedicated networ"s. are described in the -9A series of Technical !pecifications and in the *9Aseries of Technical !pecifications.

1.1 +e5erence $oint 5i*e) network' - MS(

The M!2 is based on a normal %!:& e'chan e. %t has. for call control. the same reference points as the fi'ed networ" e'chan es. The si nallin reference point considered in the Technical !pecifications is related to the si nallin system &o. < 4ser Parts T4P and %!4P associated to the circuits used for incomin and out oin calls.

3GPP

elease !"

!%%

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

1.2 +e5erence $oint GGS, - $acket )ata network' (Gi re5erence $oint)
This is the reference point between the GG!& and a pac"et data networ". %t may be an operator e'ternal public or private pac"et data networ" or an intra operator pac"et data networ". e. . for provision of %M! services.

1.2a +e5erence $oint P6, G= - $acket )ata network' (SGi re5erence $oint)
This is the reference point between the P:& GB and a pac"et data networ". %t may be an operator e'ternal public or private pac"et data networ" or an intra operator pac"et data networ". e. . for provision of %M! services. 8or more details see T! *9.+;, P,+-C.

1.3 +e5erence $oint GML( - e*terna& L(S (&ient (Le re5erence $oint)
/t this reference point e'ternal 62! 2lients reDuest services from the P6M&.

1.4 +e5erence Point (S(!24:(! J M &ti8e)ia 4P network' (M8 +e5erence Point)

This is an %P interface between 2!28F%128 and %P networ"s. This interface is used. for e'ample. to receive a session reDuest from another !%P server or terminal.

1.- (7oi)) 1." +e5erence $oint P6G - $acket )ata network' (=i re5erence $oint)
This is the reference point between the P:G and a pac"et data networ". %t may be an operator e'ternal public or private pac"et data networ" or an intra operator pac"et data networ". e. . for provision of %M! services.

1.1 +e5erence Point =%G J =L%, acce'' network (=n re5erence $oint)
This is the reference point between the B/G and the B6/& access networ". %t is used to force traffic between a B6/& 43 and P:G to o throu h the B/G.

1.; +e5erence $oint MT(-4=! - S(S (T'$ re5erence $oint)

!ee clause ;a.,;.,. This interface is an interface between the P6M& and other networ"s if the !2! is not controlled by the operator.

3GPP

elease !"

!%!

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

%nne* % (in5or8ati7e)/ 6e'cri$tion 5or GL+-re&ate) entitie' an) inter5ace'

This anne' describes the G60Arelated entities and the interfaces. This anne' is an informative anne'. The #informative# means just that the G60 is an optional functional entity to optimi(e si nallin traffic between P6M&s. Therefore. this anne' is normative to a P6M& which introduce the G60. The G60 is only applicable for G30/& and 4T0/& access. The G60 is not applicable to the 3P2.

%.1
P/,C

,or8ati7e re5erence'
3GPP T! *3.,,9E Q3rd Generation Partnership ProjectO Technical !pecification Group 2ore &etwor"O Gateway 6ocation 0e ister (G60)O !ta e*Q.

%.2

6e5inition' re&ate) to Gatewa9 Location +e3i'ter (GL+)

%.2.1 Gatewa9 Location +e3i'ter (GL+)

This entity handles location mana ement of roamin subscriber in visited networ" without involvin G60. The location re ister function in the G60 stores subscription information and routein information for both 2! services and P! services. This entity can be only located in a visited P6M&.

%.2.2 4nter8e)iate Mo.i&e-'er7ice' Switchin3 (entre (4M-MS()

This entity is used as servin M!2 towards home networ" and relay some messa es between home networ" and servin M!2. This entity can be only located in a visited P6M&.

%.2.3 4nter8e)iate GP+S Ser7in3 ,o)e (4M-GS,)

This entity is used as servin G!& towards home networ" and relay some P:4 notification messa es between servin G!& and Gateway G!&. This entity can be only located in a visited P6M&.

%.3

The entitie' o5 the 8o.i&e '9'te8

%.3.1 Gatewa9 Location +e3i'ter (GL+)

G60 is pseudoAG60 located in visited networ". The roamer#s information is stored in it and handles location mana ement of it within the networ". Presence of G60 is invisible from home networ" therefore interface between G60 and G60 is same as one of G60 and ?60. /lso. the interface between the ?60 and G60 is the same as the one between the ?60 and the G60. The G60 is a lo ical node and acts as a ?60 for M/P si nallin (e. . P0&) from the GP6M& point of view. The G60 acts as a G60 for M/P si nallin (e. . 0e ister !!) from the ?P6M& point of view. The G60 also acts as an !G!& for M/P si nallin only (e. . %!:) from the GP6M& point of view. This is because M/P operations such as %!: must be terminated at the G60 for the purpose of subscriber data cachin .

3GPP

elease !"

!%"

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

The G60 shall terminate all T2 dialo ues and start new dialo ues towards the G60 or the ?60. The G60 shall enerate !22P address of the G60 (i.e. 3.*,- MGT) from %M!%.

%.3.2 4nter8e)iate Mo.i&e-'er7ice' Switchin3 (entre (4M-MS()

The %ntermediate M!2 (%MAM!2) is the lo ical node. which represent M!2s in the visited networ". !ome service features use the M!2 &umber stored in the G60 directly to deliver messa e from a certain node in home networ" (e. . !M!AGM!2) to servin M!2 in visited networ". %n such case. the messa e is firstly distributed to representative M!2 (i.e. %MAM!2) and it relays it to actual servin M!2 interro atin routin information to G60. A A The %ntermediate M!2 (%MAM!2) is a lo ical node and represents the ?M!2 in the G60 eDuipped ?P6M&. The %MAM!2 acts as the ?M!2 for the GP6M& in the same way that the G60 acts as a ?60 for GP6M&. The %MAM!2 terminates M/P si nallin from the GP6M& towards the ?M!2 and forwards the si nal to the actual ?M!2. The %MAM!2 has an address interro ation function with which it is able to obtain the actual ?M!2 &umber from the G60. The %MAM!2 is implemented in the same physical node as the one in which the G60 is implemented. The G60 alters the ?M!2 &umber to the %MAM!2 &umber within an 4pdate 6ocation messa e. The %MAM!2 &umber is the 3.,;- &umber assi ned to the %MAM!2 P=3C. The interro ation function of the %MAM!2 is similar to that in the !M!AGM!2.

A A A A A

%.3.3 4nter8e)iate GP+S Ser7in3 ,o)e (4M-GS,)

The %ntermediate G!& (%MAG!&) is a lo ical node and represents the !G!& for some GTP si nallin termination in a G60 eDuipped ?P6M&. The %MAG!& acts as an !G!& for only some GTP signalling messages (i.e. P:4J&otification reDuestFresponse. P:4J&otificationJreject reDuestFresponse) from the GP6M& point of view. The %MAG!& terminates these GTP si nallin messa es from the GP6M& towards !G!& and forwards the si nal to the actual !G!&. The %MAG!& has an address interro ation function with which it is able to reDuest the actual !G!& address from the G60. /part from the case described above (i.e. P:4J&otification reDuestFresponse. P:4J&otificationJreject reDuestFresponse). all other GTP si nallin should be handled directly between the !G!& and the GG!&. &OT3E MAP signalling towards the !G!& is NOT terminated at the %MAG!&. %nstead it is terminated at the G60.

%.4

(on5i3 ration o5 a P .&ic Lan) Mo.i&e ,etwork

%.4.1 :a'ic con5i3 ration with GL+ intro) ction

%n the basic confi uration with G60 introduction presented in fi ure /.,. all the functions related to G60 introduction are considered implemented in different eDuipments. Therefore. all the interfaces within P6M& are e'ternal. %nterfaces G6a. G6b. G6c. G6d. G6f. G6 . G6h. and G6i need the support of the Mobile /pplication Part of the si nallin system &o. < to e'chan e the data necessary to provide the mobile service. &o protocols for the G6e interface are standardi(ed. G6j and G6" need the support of GP0! Tunnellin Protocol A 2ontrol to provide the pac"et domain services.

3GPP

elease !"

!%3

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

!G!& G6" %MAG!& G6j G6c G6e G60 G6a G6f GG!& G60 Other P6M& G6b G6d

?60FM!2 G6h %MAM!2

G6 G6i

!M!AGM!2

GM62

!i nallin interface 4ser traffic interface. 4ser traffic includes !hort Messa e. .i/ure A$!0 5onfi/uration of a P;8N and interfaces with G;

%.-

PLM, inter5ace'

%.-.1 4nter5ace .etween the >L+ an) the GL+ (GLa-inter5ace)

%n circuit switched domain. this interface is the same as that between the ?60 and the G60 (see T! *9.++* P*;C). The G60 re ards the G60 as the ?60 via this interface. On the other hand. in pac"et switched domain. this interface is the same as that between the !G!& and the G60 (see T! *9.++* P*;C). The G60 re ards the G60 as the !G!& via this interface

%.-.2 4nter5ace .etween the VL+ an) the GL+ (GL.-inter5ace)

This interface is the same as those between the ?60 and the G60 (see T! *9.++* P*;C). The ?60 re ards the G60 as the G60 via this interface.

%.-.3 4nter5ace .etween the SGS, an) the GL+ (GLc-inter5ace)

This interface is the same as those between the !G!& and the G60 (see T! *9.++* P*;C). The !G!& re ards the G60 as the G60 via this interface.

%.-.4 4nter5ace .etween the GL+ an) the 4MHMS( (GL)-inter5ace)

%n the networ" with the G60. when the %MJM!2 receives a messa e. it interro ates the G60 for the routin information of the M!2. Gowever. this interface is internal because G60 and %MAM!2 are implemented in the same physical node and the protocol on this interface is not specified.

%.-.- 4nter5ace .etween the GL+ an) the 4MHGS, (GLe-inter5ace)

%n the networ" with the G60 when the %MJG!& receivin a P:4 notification from the GG!&. the %MJG!& relays the notification to the !G!& by interro atin via the interface the routin information to the G60. The interro ation uses the same operation on the interface between the !G!& and the G60 (see T! *9.++* P*;C).

3GPP

elease !"

!%'

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

%.-." 4nter5ace .etween the SMS-GMS( an) the GL+ (GL5-inter5ace)

This interface is used to forward mobileAterminated short messa es in the networ" with the G60 in case of !M! transfer over GP0!. !i nallin on this interface uses the Mobile /pplication Part (M/P) (see T! *9.++* P*;C). The !M!AGM!2 re ards the G60 as the !G!& via this interface.

%.-.1 4nter5ace .etween the SMS-GMS( an) the 4MHMS( (GL3-inter5ace)

This interface is used to forward short messa es in the networ" with the G60 in case of !M! transfer over nonAGP0!. !i nallin on this interface uses the Mobile /pplication Part (M/P) (see T! *9.++* P*;C). The !M!AGM!2 re ards the %MJM!2 as the M!2 via this interface.

%.-.; 4nter5ace .etween the MS( an) the 4MHMS( (GLh-inter5ace)

This interface is used to forward short messa es in the networ" with the G60 in case of !M! transfer over nonAGP0!. /lso this interface is used to e'chan e data needed by the M!2 to perform subscriber authori(ation and allocate networ" resources. !i nallin on this interface uses the Mobile /pplication Part (M/P) (see T! *9.++* P*;C).

%.-.# 4nter5ace .etween the GML( an) the 4MHMS( (GLi-inter5ace)

/lso this interface is used to e'chan e data needed by the M!2 to perform subscriber authori(ation and allocate networ" resources. !i nallin on this interface uses the Mobile /pplication Part (M/P) (see T! *9.++* P*;C). The GM62 re ards the %MJM!2 as the M!2 via this interface.

%.-.10 4nter5ace .etween the GGS, an) the 4MHGS, (GLL-inter5ace)

%n the networ" with the G60 when receivin a P:P P:4 from the e'ternal networ" the GG!& sends a notification to the %MJG!& by the routin information from the G60 (see T! *9.+;+ P=,C). The GG!& re ards the %MJG!& as the !G!& via this interface.

%.-.11 4nter5ace .etween the SGS, an) the 4MHGS, (GLk-inter5ace)

%n the networ" with the G60 when receivin a P:P notification from the GG!&. the %MJG!& relays the notification to the !G!& by the routin information from the G60 (see T! *9.+;+ P=,C). The !G!& re ards the %MJG!& as the GG!& via this interface.

3GPP

elease !"

!%)

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

%nne* : (in5or8ati7e)/ (han3e hi'tor9

5han/e history
6ate 0#21### 0#22010 0#22010 0#22010 0#22010 1222010 0122011 0322011 0322011 0#22011 0#22011 0#22011 1222011 0322012 0322012 0322012 0"22012 0"22012 0"22012 0"22012 0#22012 0#22012 0#22012 TSG C SP-4# SP-4# SP-4# SP-4# SP--0 SP--1 SP--1 SP--3 SP--3 SP--3 SP--4 SP--SP--SP--SP--" SP--" SP--" SP--" SP--1 SP--1 SP--1 SP-100--SP-100--1 SP-100--1 SP-100--1 SP-100"14 SP-11001SP-110010 SP-1104-" SP-1104"0 SP-1104"; SP-110131 SP-1200;1 SP-1200;1 SP-1200;SP-120244 SP-12023; SP-12024; SP-120241 SP-1204;2 SP-120414 SP-1204;1 TSG 6oc$ 5 0222 0223 0220221 0231 022; 0232 023; 023# 0240 0244 0242 024024" 0241 024; 02-0 02-1 02-3 02-4 02-2 ev Su4ject>5omment - ren 8.erin3 o5 the $re'ent )oc 8ent 5ro8 03.02 to 23.002 (23.002 7.3.0.0 i)entica& to 03.02 7.1.0.0) 1 %))ition o5 GTP .a'e) S2. in the 3GPP network architect re - U$)ate' to 4M S .'9'te8 5i3 re 5or E-(S(! an) 4:(! - %rchitect re $)ate o5 S+V(( architect re enhance) with %T(! 1 4ntro) cin3 U) inter5ace .etween U6+ an) P(+! - (orrection o5 MG(! )e5inition to 8ake it con'i'tent with TS 2#.23- U$)ate o5 LTE &o3o to LTE-%)7ance) &o3o 2 (orrection on the re5erence o5 S2. inter5ace - %)) L4P%HS4PTB in 23002 2 (orrectin3 the )e5inition o5 42 1 M:MS ' $$ort in EPS 2 4ntro) ction o5 the (SG S .'cri.er Ser7er entit9 an) inter5ace' - %))in3 8i''in3 %(T! to 4MS entitie' c&a 'e 2 (&ari5ication on GUP )ata re$o'itor9E' ro&e a' &o3ica& 5 nction in the >SS - E)itoria& an) re5erence correction' to 23.002 - (&ari5ication' 5or SaMBG in 23.002 1 (orrection' re&ate) to S%PP intro) ction in the ,etwork %rchitect re '$eci5ication 1 (orrection' re&ate) to DoSHSSL intro) ction in the ,etwork %rchitect re '$eci5ication. 1 4ntro) ction o5 (S to PS S+V(( architect re 4 ::%4 $)ate 5or architect re, entit9 an) inter5ace 5 nction 1 S4MT( $)ate 5or architect re, entitie' an) inter5ace' - +e5erence &i't correction to a&i3n with the correcte) TS 2#.212 tit&e - (orrection to the 4MS architect re )ia3ra8/ %))ition o5 8i''in3 M8 inter5ace .etween 4-(S(! an) 4P M &ti8e)ia ,etwork' 1 (&ari59in3 that MS( Ser7er a''i'te) 8i)-ca&& 5eat re )oe' not i8$&9 42 inter5ace - %))in3 the 8i''in3 %TG= to 4MS entitie' )e'cri$tion c&a 'e 2 (&ari5ication on the re5erence o5 SG) an) S"c 2 %))in3 S4PTB at the Loca& ,etwork 2 4ntro) ction o5 G9n2G?n inter5ace' to the '$eci5ication 1 %))ition o5 6ia8eter G)) inter5ace 5or SMS with SGS, - %)) ,ew 4nter5ace 6e'cri$tion .etween MME an) >+P6 %, 2 4ntro) ce T(P $ro*9 to the 3GPP network 1 4ntro) ction o5 L3) 2 Mi''in3 PSS Ser7er 4n5or8ation 2 %))in3 the 4MS =e.+T( architect re
5at

9ld New 03.0271. 23.0027 0.0 3.0.0 : #.4.0 10.0.0 ! ! ! % ! : % ! : % ! ! : ! ! : ! : ! ! #.4.0 #.4.0 #.4.0 10.0.0 10.1.0 10.1.1 10.1.1 10.2.0 10.2.0 10.3.0 11.0.0 11.1.0 11.1.0 11.1.0 11.2.0 11.2.0 11.2.0 11.2.0 11.3.0 11.3.0 11.4.0 10.0.0 10.0.0 10.0.0 10.1.0 10.1.1 10.2.0 10.2.0 10.3.0 10.3.0 11.0.0 11.1.0 11.2.0 11.2.0 11.2.0 11.3.0 11.3.0 11.3.0 11.3.0 11.4.0 11.4.0 !"$%$%

1222012 1222012 0"22013 0"22013 0"22013 1222013 1222013 1222013 1222013 0322014 0322014

SP--; SP--; SP-"0 SP-"0 SP-"0 SP-"2 SP-"2 SP-"2 SP-"2 SP-"3 SP-"3

SP-120114 SP-120;;1 SP-13030SP-130310 SP-130230 SP-130-3SP-130-3; SP-130-33 SP-130-3SP-140112 SP-140101

02-" 02"0 02"2 02"3 02"4 02"1 02"; 02"# 0210 0211 0212

% % % : : : : : : ! :

12.0.0 12.0.0 12.1.0 12.1.0 12.1.0 12.2.0 12.2.0 12.2.0 12.2.0 12.3.0 12.3.0

12.1.0 12.1.0 12.2.0 12.2.0 12.2.0 12.3.0 12.3.0 12.3.0 12.3.0 12.4.0 12.4.0

3GPP