UMTS 23.01: Universal Mobile Telecommunications System (UMTS) General UMTS Architecture (UMTS 23.01 Version 3.0.0)
UMTS 23.01: Universal Mobile Telecommunications System (UMTS) General UMTS Architecture (UMTS 23.01 Version 3.0.0)
01 version 3.0.0)
UMTS 23.01
UMTS
Universal Mobile Telecommunications System
Reference
Office address
$.0 +oute )es /ucioles - So%&ia 'nti%olis Valbonne - #+',(Tel.0 133 2 92 92 22 00 #a*0 133 2 93 $. 23 1$
Siret ,4 325 $23 .$2 00013 - ,'# 322 ( 'ssociation 6 but non lucrati7 enre8istr9e 6 la Sous-"r97ecture )e !rasse (0$) ,4 3503 55
nternet
secretariat:etsi.7r &tt%0 ;;;.etsi.7r &tt%0 ;;;.etsi.or8
Copyright Notification !o "art may be re"roduced e#ce"t as authori$ed by written "ermission% The co"yri&ht and the fore&oin& restriction e#tend to re"roduction in all media%
' (uro"ean Telecommunications Standards nstitute )***% All ri&hts reserved%
(ontents
+ontents%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%, ntellectual Pro"erty Ri&hts%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%.oreword%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%ntroduction%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%) Sco"e%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%/ 0 References%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%/
0%) nformative references%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%/
9istory%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%),
(TS
#ore;or)
This draft Technical S"ecification has been "roduced by the S"ecial Mobile 3rou" (SM3) Technical +ommittee of the (uro"ean Telecommunications Standards nstitute ((TS )% The contents of this TS is sub?ect to continuin& wor7 within SM3 and may chan&e followin& formal SM3 a""roval% Should SM3 modify the contents of this TS2 it will be re@released by SM3 with an identifyin& chan&e of release date and an increase in version number as follows; Aersion #%y%$ where; # the first di⁢ ) "resented to SM3 for informationB 0 "resented to SM3 for a""rovalB , indicates UMTS s"ecification a""roved by (TS SM3B y the second di&it is incremented for all other ty"es of chan&es2 i%e% technical enhancements2 corrections2 u"dates2 etc% $ the third di&it is incremented when editorial only chan&es have been incor"orated in the s"ecificationB
<ntro)uction
UMTS will su""ort a wide ran&e of a""lications with different 6uality of service "rofiles% At "resent many of these a""lications are not "ossible to "redict% Also the usa&e of the different a""lications are difficult to "redict i%e% it is not "ossible to o"timise UMTS to only one set of a""lications% One conclusion of this is that UMTS must be built in such a way that it is fle#ible and "ossible to evolve so it will have a lon& technical lifetime% Therefore a modular a""roach is recommended when definin& the networ7 "arts of UMTS% This is in line with the recommendation from 3MM% n this conte#t a module re"resents a "art of a UMTS networ7 i%e% one or several "hysical networ7 nodes that toðer im"lements some functionality% The modular a""roach should also ma7e UMTS "ossible to im"lement efficiently in different environments%
Sco%e
This TS defines the basic "hysical and functional se"aration of UMTS% The contents of this s"ecification is limited to those features that are common to all UMTS networ7s inde"endent of their ori&in . t identifies and names the reference "oints and functional &rou"in&s a""earin& at this level%
+e7erences
References are either s"ecific (identified by date of "ublication2 edition number2 version number2 etc%) or non@s"ecific% .or a s"ecific reference2 subse6uent revisions do not a""ly% .or a non@s"ecific reference2 the latest version a""lies% A non@s"ecific reference to an (TS shall also be ta7en to refer to later versions "ublished as an (! with the same number%
The followin& documents contain "rovisions which2 throu&h reference in this te#t2 constitute "rovisions of the "resent document%
3.1 De7initions
Terms introduced in this document; Domain: The hi&hest@level &rou" of "hysical entities% Reference "oints are defined between domains% Stratum: 3rou"in& of "rotocols related to one as"ect of the services "rovided by one or several domains%
3.2 Symbols
.or the "ur"oses of the "resent document2 the followin& symbols a""ly; +u u Uu CFuD CGuD Reference "oint between US M and M( Reference "oint between Access and Servin& !etwor7 domains Reference "oint between User (6ui"ment and nfrastructure domains2 UMTS radio interface Reference "oint between Servin& and Transit !etwor7 domains Reference "oint between Servin& and 9ome !etwor7 domains
3.3 'bbreviations
.or the "ur"oses of the "resent document2 the followin& abbreviations a""ly; US M M( User Services dentity Module Mobile (6ui"ment
(TS
MT M(#( T(
!eneral
The &eneral UMTS architecture is modelled2 at a hi&h level2 from both "hysical and functional view"oints% The "hysical as"ects are modelled usin& the domain conce"t and the functional as"ects are modelled usin& the strata conce"t% The two views are introduced se"arately and then the ma""in& between the views is discussed% This s"ecification shows at a basic level "hysical and functional se"arations to allow a UMTS networ7 to fit within the conte#t of the MT@0::: family of networ7s% t does not attem"t to develo" as"ects of a UMTS networ7 that are hi&hly s"ecific to that im"lementation%
Domains in UMTS
@ome ,et;or? Domain CGuD (u Uu <u CFuD
The followin& fi&ure shows the basic domains in UMTS as described in this section%
Servin8 ,et;or? Domain US<M Domain Mobile ->ui%ment Domain User ->ui%ment Domain 'ccess ,et;or? Domain (ore ,et;or? Domain <n7rastructure Domain
,AT- 0
T&e )omains i)enti7ie) in t&e 7i8ure ;ill 8enerally result 7rom an evolution o7 e*istin8 net;or? in7rastructures. T&e core net;or? )omain may result 7rom evolutions o7 e*istin8 net;or? in7rastructures= e.8.= a !SM in7rastructure= a ,-<SD, in7rastructure= a B-<SD, in7rastructure or a "D, in7rastructure. T&e evolution o7 t&ese in7rastructures may be %er7orme) via t&e use o7 <CUs= &i))en ;it&in t&e )omains s&o;n in t&e 7i8ure.
$i%ure 1& UMTS 'omains an' re(erence )oints +u u Uu CFuD CGuD H Reference "oint between US M and M( H Reference "oint between Access and Servin& !etwor7 domains H Reference "oint between User (6ui"ment and nfrastructure domains2 UMTS radio interface H Reference "oint between Servin& and Transit !etwor7 domains H Reference "oint between Servin& and 9ome !etwor7 domains
(TS
..3.2.1
The servin& networ7 domain is the "art of the core networ7 domain to which the access networ7 domain that "rovides the userKs access is connected% t re"resents the core networ7 functions that are local to the userKs access "oint and thus their location chan&es when the user moves% The servin& networ7 domain is res"onsible for routin& calls and trans"ort user data>information from source to destination% t has the ability to interact with the home domain to cater for user s"ecific data>services and with the transit domain for non user s"ecific data>services "ur"oses%
..3.2.2
The home networ7 domain re"resents the core networ7 functions that are conducted at a "ermanent location re&ardless of the location of the userKs access "oint% The US M is related by subscri"tion to the home networ7 domain% The home networ7 domain therefore contains at least "ermanently user s"ecific data and is res"onsible for mana&ement of subscri"tion information% t may also handle home s"ecific services2 "otentially not offered by the servin& networ7 domain% !OT(; Most of the functionality associated with the service "rovider role accordin& to the UMTS role model (ref UMTS 00%:))2 is normally contained within the home networ7 domain%
..3.2.3
The transit networ7 domain is the core networ7 "art located on the communication "ath between the servin& networ7 domain and the remote "arty% f2 for a &iven call2 the remote "arty is located inside the same networ7 as the ori&inatin& U(2 then no "articular instance of the transit domain is activated%
9ome stratumB Servin& stratum and Trans"ort stratum The followin& fi&ures show the interactions between the UMTS domains% Two fi&ures are used to reflect the "ath diversion between the flows e#chan&ed between servin& and home domains on one side and between servin& and transit on the other side% .i&ure 0 below shows the interactions between the US M2 MT>M(2 Access !etwor72 Servin& !etwor7 and 9ome !etwor7 domains% .i&ure , shows the interactions between T(2 MT2 Access !etwor72 Servin& !etwor72 Transit !etwor7 domains and the Remote Party % The 9ome Stratum only involves domains from fi&ure 02 the A""lication Stratum only involves domains from fi&ure ,% The Servin& and Trans"ort Strata involve domains from fi&ures 0 and ,2 so "art of them are du"licated in the two fi&ures The direct flows between non@conti&uous domains (i%e% between domains non directly interconnected) are trans"arently trans"orted across all the domains and interfaces located on the communication "ath between these end domains% (%&% the US M@9ome !etwor7 flows are trans"arently trans"orted throu&h US M@MT2 MT@Access !etwor72 Access !etwor7@Servin& !etwor7 and Servin& !etwor7@9ome !etwor7 interfaces2 and relayed without inter"retation by MT2 Access !etwor7 and Servin& !etwor7 domains% The dotted lines indicates that the "rotocol used is not s"ecific to UMTS2 in some cases different "rotocols are "ossible% 9owever2 to "rovide easy roamin& ca"abilities2 it is desirable to a&ree u"on the "rotocols used% The definition of these "rotocols is outside the sco"e of the UMTS s"ecifications%
D@ome StratumE US<M - @, US<M - MT MT - S, S, - @,
DTrans%ort StratumE D'ccess StratumE MT - ', ', - S, Servin8 ,et;or? Domain @ome ,et;or? Domain
US<M
MT M-
$i%ure 2& $unctional (lo+s bet+een the US,M- MT.M/- Access 0et+or1- Servin% 0et+or1 an' 2ome 0et+or1 'omains.
(TS
DServin8 StratumE T- - MT MT - S,
DTrans%ort StratumE D'ccess StratumE MT - ', TMobile ->ui%ment Domain MT 'ccess ,et;or? Domain Servin8 ,et;or? Domain Transit ,et;or? Domain +emote "arty ', - S,
$i%ure 3& $unctional (lo+ bet+een T/- MT- Access 0et+or1- Servin% 0et+or1- Transit 0et+or1 'omains an' the 3emote 4arty The IRemote PartyJ re"resents the remote end entity (user or machine) and is included in the fi&ure to show the end@ to@end character of the communication2 the s"ecification of the remote "arty is outside the sco"e of the UMTS s"ecifications%
11
The access stratum includes the followin& "rotocols; Mobile Termination @ Access !etwor7 This "rotocol su""orts transfer of detailed radio@related information to co@ordinate the use of radio resources bbetween the MT and the access networ7% Access !etwor7 @ Servin& !etwor7 This "rotocol su""orts the access from the servin& networ7 to the resources "rovided by the access networ7% t is inde"endent of the s"ecific radio structure of the access networ7%
(TS
(nd@to@end functions are a""lications which are consumed by users at the ed&e of>outside the overall networ7% The a""lications may be accessed by authenticated users who are authorised to access such a""lications% The users may access the a""lications by usin& any of the variety of available user e6ui"ment%
13
@istory
Document history
MAersionN :%:%) :%:%0 :%:%, :%:%:%:%/ :%:%4 :%:%5 :%)%: :%0%: :%,%: :%-%: :%/%: :%4%: :%5%: :%5%) M1ateN A"ril )**5 May )**5 May )**5 May )**5 Oune )**5 Ouly )**5 Ouly )**5 Se"t )**5 !ov )**5 March )**8 March )**8 A"ril )**8 A"ril )**8 Ouly )**8 Au&ust )**8 MMilestoneN +reated at SM3,>SA Revised2 new terminolo&y2 in"ut to SM3@SA Tdoc SM3, *5S):4 Revised durin& the meetin&2 Tdoc SM3, *5S)0) Revised durin& the meetin&2 Tdoc SM3, *5S)0Revised by editor2 in"ut to SM3,@SA Tdoc SM3, *5S )-0 Revised by the SA meetin&2 Tdoc SM3, *5S0:, Revised by the SA meetin& based on Tdoc SM3, *5S0:5 Revised by the SA meetin&2 Au& *52 Tdoc SM3, *5S0,, and 0-: Revised by the SA meetin&2 !ov )**52 Tdoc SM3, *5S,54 (sli&htly modified) Revised by the SA meetin&2 Oan *82 Tdocs SM3, *8S:4, (rev) and *8S:5- (rev)% +han&es to fi&ure ) not correctly included2 version withdrawn +han&es from SA meetin& in Oan *82 includin& fi&ure )2 see above2 chan&es relative to :%0%: indicated Revised by SM3)0 meetin& in March *82 Tdoc SM3, SA )-/ Revised by SM3)0 meetin& in A"ril *82 based on Tdocs SM3)0 *8P0:5 and 04* Revised by SM3)0 meetin& in Oune *82 Tdoc SM3)0 *8S,/0 Acce"ted as the base for further wor7 on the SM3 )0 meetin& Au&ust *8% 9idden information2 which a""ered in the "rinted 0,%0:v:%5%: on the SM3 )0 Au&ust *8 meetin&2 is removed% )%:%: 0%:%: ,%:%: Se"tember )**8 .ebruary )*** )***@:0 Aersion )%:%: for "resentation for information to SM3P05 Aersion 0%:%: for "resentation for a""roval to SM3P08 A""roved at SM3P08% 1ocument for Transfer to TS3@SA
(TS