Professional Documents
Culture Documents
UMTS Architecture
UMTS Architecture
Module Objectives: Introduction to UTRAN, UTRAN Identifiers (RNTI), UTRAN Functionalities, UTRAN Protocol Models and Protocol tac!s"
I. UMTS Architecture
I. UMTS Architecture
I. UMTS Architecture
I. UMTS Architecture
Me nu
Me nu
U"
'N
U"
fi*ure 1 To$ le+el desi*n of !o,ile co!!unication network UMTS and t-$es of infor!ation.
I. UMTS Architecture In t$is course )e )ill deal )it$ UMT Release 2 (corres(onds to UMT Release 3444)" In t$is case t$e 0N (core net)or!) is ta!en fro' % M,%PR " T$is 'eans t$e core net)or! of UMT Release 2 contains a 'S.'N.Do!ain %'ircuit Switched 'ore Network Do!ain&, )$ic$ is in fact a standard % M net)or!, and a PS.'N.Do!ain %Packet Switched 'ore Network Do!ain& , for'ed b* t$e % M5%PR net)or! (art ( % N, %% N)" T$ese t)o (arts, P . and 0 50N51o'ain, are inde(endent of eac$ ot$er" For t$e UTRAN t$is )ill 'ean t$at it $as to serve t)o core net)or!s"
I. UMTS Architecture
M enu
6ideo,Tele($on*
U+ 3
M enu
0 .0N
U+ 7
M enu
Internet ession
U+ 2
UTRAN
Ser+er
I. UMTS Architecture To (rovide a consistent set of ter' definitions, t$e 2%PP,+T I 'ade t$e follo)in& definition, t$at can be found in T 72"383" T$ese definitions divide t$e different net)or! bloc!s accordin& to t$eir function )it$ res(ect to a (rovided service" #e $ave t$e follo)in& so called do'ains: User "#ui$!ent Do!ain: T$e user e-ui('ent do'ain is t$e 'obile (art of t$e net)or!" It re(resents t$e U+ as ($*sical entit*" T$ere are t)o sub.do'ains inside: USIM do!ain: T$e U IM (User ervices Identit* Module) is t$e entit* t$at contains t$e user identit* and t$e user s(ecific settin&s" Mo,ile "#ui$!ent do!ain: T$is do'ain is t$e $ard. and soft)are in t$e 'obile ($one, necessar* to &et access to t$e net)or! and to su((ort t$e core net)or! services"
Infrastructure do!ain: T$e infrastructure do'ain covers t$e fi/ed net)or! (art of UMT , t$at 'eans all ($*sical entities controlled b* t$e net)or! o(erators" T$ere are t)o sub. do'ains: Access Network do!ain: T$e access net)or! do'ain is t$e UTRAN t$at serves t$e user" 'ore Network do!ain: T$e core net)or! do'ain re(resent t$at (art of t$e fi/ed net)or!, t$at is res(onsible for t$e basic services (s)itc$in&, routin&, M )" T$e core net)or! itself is a ($*sical entit*" Accordin& to t$eir function for a runnin& service, t$e follo)in& lo&ical do'ains can be distin&uis$ed: o Ser+in* 'N do!ain: T$e servin& 0N do'ain re(resent t$at (art of t$e 0N, t$at is currentl* servin& t$e user" o 1o!e 'N do!ain: T$e $o'e 0N do'ain is t$at (art of t$e 0N, t$e $o'e o(erator of t$e subscriber controls" In t$e $o'e 0N do'ain t$e (er'anent subscriber data base for t$e user can be found (9:R)" o Transit 'N do!ain: T$e transit 0N do'ain covers all 0N (arts t$at do not belon& to t$e servin& 0N do'ain, but are used to trans(ort user data"
I. UMTS Architecture
1o!e Network
<u
U I M
0u
Mobile Uu +-ui('ent
Iu
Ser+in* Network
;u
Transit Network
U+
UTRAN
'N Infrastructure
fi*ure
I. UMTS Architecture
T$erefore )e can distin&uis$ t$ree t*(es of si&nalin& bet)een U+, UTRAN and 0N: access stratu! %AS& : T$e access stratu' covers all si&nalin& e/c$an&e used to control t$e access of an U+ to t$e net)or!" Access stratu' 'essa&es occur bet)een U+ and UTRAN and bet)een UTRAN and 0N" T$e difference bet)een t$e access stratu' U+.UTRAN and UTRAN.0N is, t$at t$e UTRAN.0N access stratu' s$all be inde(endent of t$e radio tec$nolo&* used in UTRAN" T$is enables t$e 0N to use several different radio access tec$nolo&ies" trans$ort stratu! : T$e trans(ort stratu' (rotocols and 'essa&es $ave t$e tas! to trans(ort $i&$er la*er P1Us ((rotocol data units) and user data" =ecause UTRAN $as t$e tas! to trans(arentl* trans(ort data bet)een U+ and 0N, t$ere )ill be trans(ort stratu' 'essa&es bet)een U+ and UTRAN and bet)een UTRAN and 0N" non5 access stratu! %NAS& : T$e non.access stratu' covers all 'essa&es of $i&$er la*ers and user data, t$at do not deal )it$ access or trans(ort tas!s" T$is covers (ure a((lication control (a((lication stratu'), service re-uest and control (servin& stratu'), $andlin& of subscri(tion data and subscriber s(ecific services ($o'e stratu')"
T$e strata are e/actl* defined in T 72"383" It $as to be noted, t$at a sin&le (rotocol can belon& to different strata (e"&" RR0 belon&s to A and trans(ort stratu')"
16
I. UMTS Architecture
U"
UTRAN
'N
Access tratu'
Access tratu'
Trans(ort tratu' Trans(ort tratu' Trans(ort tratu' Non Access tratu' (NA )
11
I. UMTS Architecture
12
I. UMTS Architecture
I. UMTS Architecture
1(
I. UMTS Architecture
'N
0 .0N
Iu
P .0N
=0.0N
RN
Iub
RN0
Iub Iur Iub
RN0
Iub
Node =
Node =
Node = Node =
cell cell
cell cell
RN
1)
I. UMTS Architecture
T$is 'eans t$e controllin& RN0 of a cell is res(onsible for all lo)er la*er functions related to t$e radio tec$nolo&*"
1/
I. UMTS Architecture
0ontrollin& RN0
.ad'ission control '5RN' Iub . s*ste' infor'ation broadcastin& . radio bearer allocation , release ( code allocation , release) Node 7 . data trans'ission and rece(tion
cell
10
I. UMTS Architecture For UTRAN t$e follo)in& (rinci(le is a((lied" An U+ t$at is attac$ed to an UTRAN is served b* one and onl* one RN0" T$is RN0 is called t$e ser+in* RN' %S5RN'&" T$e e/istence of a servin& RN0 does not i'(l* t$at t$e U+ is ca'(ed on a cell belon&in& to t$e .RN0" T$e servin& RN0 $andles all $i&$er la*er functions related to radio access and infor'ation trans(ort t$rou&$ UTRAN" In detail t$e .RN0 (erfor's t$e follo)in& functions: t$e .RN0 $andles t$e Iu interface to)ards t$e 0N for t$is U+, t$e .RN0 $andles t$e co'(lete radio resource control for t$is U+, location , 'obilit* $andlin&, ci($erin&, bac!)ard error correction (la*er 7 functionalit*)"
In UMT it is (ossible t$at one U+ is connected to 'ore t$an one cell, or connected to a cell, t$at does not belon& to t$e .RN0" T$is 'eans t$e U+ is connected )it$ a cell controlled b* a RN0 different to t$e .RN0" T$is forei&n RN0 is called drift RN' %D5 RN'&" In (rinci(le t$e 1.RN0 is t$e 0.RN0 of a cell t$e U+ is connected to, but its not t$e .RN0" T$erefore t$e 1.RN0 (erfor's t$e 0.RN0 functions for t$e cells not controlled b* t$e .RN0" #$en a 1.RN0 is involved for a U+, t$en t$e data strea's bet)een U+ and UTRAN and U+.0N al)a*s (ass t$e .RN0" In t$e do)nlin! t$e .RN0 sends t$e data to o)n cells and to t$e 1.RN0 (soft $andover), t$is is called s$littin*" T$e U+ receives all t$e data strea's fro' t$e cells, it is connected to, and adds t$e' to&et$er (RA>+ receiver)" In t$e u(lin! t$e .RN0 receives data fro' t$e o)n cells and fro' t$e 1.RN0" 9ere t$e .RN0 co!,ines t$e data strea's" T$is co'bination is (erfor'ed b* t$e .RN0 in t$e follo)in& )a* : t$e .RN0 ta!es onl* t$e data fra'e )it$ t$e s'allest bit error rate, all ot$er data fra'es )ill be discarded" T$e usa&e of a 1.RN0 re-uires a Iur interface bet)een 1.RN0 and .RN0" =ecause t$e i'(le'entation of an Iur interface is o(tional, it is a 'atter of net)or! (lannin&, )$et$er t$e usa&e of 1.RN0 is allo)ed or not" T$e interface itself does not need to be a ($*sical line, it can be i'(le'ented via virtual (at$s or virtual c$annels"
12
I. UMTS Architecture
'N
Iu
ervin& RN0
Iur 1.RN0 Iub .RN0 Iub .Iu interface controllin& . radio resource control . location , 'obilit* $andlin& Node = Node = . encr*(tion , inte&rit* c$ec! . bac!)ard error correction . co'binin& , s(littin& of data strea's
Menu
U+
13
I. UMTS Architecture
I. UMTS Architecture /. Ser+ice Area Id : everal cells of one location area can be defined to for' a service area" service area is identified )it$ a SAI %ser+ice area id&: SAI ; P9MN5ID < 9A' < SA' It can be used to su((ort location based services" uc$ a
0. URA ID : T$e UTRAN introduces its o)n are conce(t ne/t to :A and RA" T$is is t$e UTRAN re&istration area
Public :and Mobile Net)or! :ocation Area Routin& Area RN0 UTRAN cell I1
P:MN.I1
7 @ 7
M00
8 3
MN0
:A0 (7b*te) :A0 (7b*te) RA0 (3b*te) RN0.I1 (37 bit) 0.I1 (7A bit) :A0 A0 (7 b*te)
ervice Area
URA I1 (7 b*te)
21
I. UMTS Architecture
In t$is c$a(ter onl* t$e UTRAN identifier are of interest" It is a t*(ical (rinci(le in co''unication and co'(utin& s*ste's t$at ever* entit* )or!in& on a s(ecific tas!, allocates its o)n identifier and $andler" T$is is also t$e case for UTRAN" +ver* UTRAN entit* li!e RN0 and Node = )ill (rovide t$eir s(ecial identifier for t$e U+" T$ese identifiers are called Radio Network Te!$orar- Identifier %RNTI& " T$ere are four t*(es of RNTI: s5RNTI : T$e s.RNTI is allocated b* t$e servin& RN0" T$e .RN0 uses t$e s.RNTI to address t$e U+" T$e 1.RN0 uses t$e s.RNTI to identif* t$e U+ to t$e .RN0" T$e s.RNTI uni-uel* addresses t$e U+ in t$e .RN0" d5RNTI : T$e d.RNTI is allocated b* a 1.RN0, but t$e d.RNTI is never used on t$e air interface Uu" Instead t$e .RN0 uses t$e d.RNTI to identif* t$e U+ to t$e 1. RN0" T$e d.RNTI uni-uel* identifies t$e U+ in t$e 1.RN0" c5RNTI : T$e c.RNTI is allocated b* a controllin& RN0 )$en t$e U+ accesses a ne) cell of t$is 0.RN0" T$e c.RNTI is uni-ue in t$e cell" T$e corres(ondin& 0.RN0 s$all be able to translate t$e c.RNTI into s.RNTI (if 0.RN0B .RN0) or into d.RNTI (if 0. RN0B1.RN0)" T$e c.RNTI is used b* U+ to identif* itself to t$e 0.RN0, and is used b* t$e 0.RN0 to address t$e U+" u5RNTI : T$e u.RNTI (UTRAN 5 RNTI) consist of RN0.Id and s.RNTI u5RNTI ; RN'5ID < s5RNTI"
o t$e u.RNTI is uni-ue )orld )ide" T$e u.RNTI )ill be used b* U+ and .RN0 to identif* t$e U+ on co''on radio c$annels and durin& (a&in& and cell access" UTRAN and UMTS Radio Protocols 22
I. UMTS Architecture
'N
s5RNTI d5RNTI
RNTI Iu
. allocated b* RN0s . 3@ bit len&t$ (u.RNTI 27 bit)
s5RNTI d5RNTI c5RNTI A
.RN0 Iub
Node =
Node =
U+
fi*ure 3 Radio Network Te!$orar- Identifiers RNTI and their usa*e and allocation.
I. UMTS Architecture
2(
I. UMTS Architecture
2)
I. UMTS Architecture
I. UMTS Architecture
U+
MM, 00, , M
RN
Rela-
M 0
MM, 00, , M
: i&nallin& ATM Ada(tation :a*er : As*nc$ronous Transfer Mode : ATM Ada(tation :a*er t*(e D : Messa&e Transfer Part level 2 for =roadband
20
I. UMTS Architecture T$e control (lane discussed before is used to e/c$an&e si&nalin& for access, trans(ort and service related control" :i!e all 'odern co''unication s*ste' also UMT trans(orts t$e control si&nalin& and t$e user data over t$e sa'e trans(ort net)or!" T$is i''ediatel* i'(lies, t$at t$ere $ave to be (rotocols su((ortin& t$e user data transfer" In t$e ne/t fi&ure t$e (rotocols used for t$is (ur(ose are s$o)n" In t$e lo)est la*ers t$ere are t$e sa'e (rotocols as for t$e control (lane" T$is results fro' t$e fact, t$at user data and control si&nalin& use t$e sa'e trans(ort s*ste'" In detail t$ere are t$e follo)in& (rotocols involved into t$e user data trans(ort: P1>, MA', R9': T$e air interface trans(ort s*ste' is built out of P9;, MA0 and R:0 as for t$e control (lane" T$e sa'e basic stac! is used for t$e user (lane" user data strea!: T$e user data strea's are &enerated b* t$e a((lications usin& t$e circuit s)itc$ed core net)or! services (s)itc$ed c$annels)" T$ese data strea's are directl* in(ut to t$e R:0" ATM : T$e trans(ort s*ste' for t$e Iu interface bet)een UTRAN and 0N is a&ain ATM" AA9 2: To (rovide a circuit s)itc$ed li!e trans(ort bearer on Iu, t$e AA: 7 (rotocol is used" T$is ada(tation la*er (rovides a bearer c$annel (virtual c$annel of AA: t*(e 7) )it$ certain Eo &uarantees" Additionall* t$e an* AA: 7 virtual c$annel includes ti'e sta'(s in t$e trans(ort fra'es" T$is allo)s s*nc$roniFation and ti'in& control bet)een sender and receiver" Iu User Plane $rotocol %Iu UP& : T$e Iu User Plane (rotocol is on to( of AA:7" T$is (rotocol can (rovide different sta&es of user data strea' su((ort" o t$e Iu UP (rotocol can (erfor' bac!)ard error correction, data rate controllin& and can be used to o(ti'iFe t$e buffer siFes for trans'ission to 'ini'iFe t$e dela* jitter" T$is (rotocol trans(orts t$e user data and can create o)n si&nalin& 'essa&es" T$e si&nalin& 'essa&es of Iu UP (rotocols are trans'itted as in.band si&nalin& )it$in t$e AA: 7 virtual c$annels used for t$e user data"
22
I. UMTS Architecture
U+
User data strea's R:0 MA0 P9; R:0 MA0 P9;
RN RN
Rela-
M 0
MM, 00, , M
User data RANAP strea's 00P Iu UP MTP 2 = AA: AA: , AA:D 7 ATM :a*er 3
23
I. UMTS Architecture
I. UMTS Architecture
U+
%MM, M, M
RN
Rela-
% N
%MM, M, M
: i&nallin& ATM Ada(tation :a*er : As*nc$ronous Transfer Mode : ATM Ada(tation :a*er t*(e D : Messa&e Transfer Part level 2 for =roadband
I. UMTS Architecture In contrast to t$e control (lanes, t$at loo! ver* si'ilar for P and 0 , t$e user (lane $as i'(ortant differences" T$is is clear, because circuit s)itc$ed data needs ot$er trans(ort 'ec$anis's (s)itc$in&) as (ac!et s)itc$ed data (routin&)" In detail t$ere are t$e follo)in& (rotocols involved: user data: T$e user data for (ac!et s)itc$ed services is usuall* dedicated to e/ternal (ac!et data net)or!s (e"&" internet)" T$ese e/ternal data net)or! $ave t$eir o)n s(ecial net)or! (rotocols (e"&" T0P,IP)" #$en a UMT user )ants to be connected )it$ suc$ an e/ternal net)or!, t$e U+ $as to send (ac!ets of t$is s(ecial net)or! (rotocol, for t$e UMT net)or! t$is is onl* data" =ut because of its s(ecial role, t$e net)or! (rotocol of t$e e/ternal net)or! is called Packet Data Protocol %PDP&" It is t$e tas! of t$e UMT net)or! to (rovide a tunnel (P1P conte/t) for trans(arent trans(ort of t$e P1P (ac!ets" Packet Data 'on+er*ence Protocol %PD'P& : T$is (rotocol (erfor's $eader co'(ression of t$e P1P (ac!et $eader" T$is s$all increase t$e efficienc* of t$e air interface usa&e" R9', MA', P1>: T$e trans(ort la*ers are t$e sa'e as for control (lane" 8PRS Tunnelin* Protocol User $lane %8TP5U& : T$e P1P (ac!ets are trans(orted in a %TP.U fra'e on Iu" %TP.U or&aniFes addressin& and identification of t$e ori&inator and destination of t$e data bet)een RN0 and % N" UDP ? IP: To route fro' RN0 to % N t$e standard U1P , IP (rotocol stac! is used" T$is is a connection less, unreliable trans(ort service" In (rinci(le onl* routin& is (erfor'ed )it$ U1P , IP" AA9 ) ? ATM : T$e U1P , IP data&ra''es ((ac!ets) are trans'itted on ATM usin& t$e ada(tation la*er D"
I. UMTS Architecture
U+
A((lication, P1P
RN
Rela-
% N
I. UMTS Architecture
I. UMTS Architecture
I. UMTS Architecture
T$is division into la*ers is also called $oriFontal structure" T$ere is also a vertical structure" T$e ele'ents of t$is vertical structure are $lanes" A (lane is (rinci(le not$in& else t$an a (rotocol stac!" More t$an one (lane can coe/ist ne/t to eac$ ot$er" In detail t$ere are t$e follo)in& (lanes: 'ontrol Plane : T$e control (lane consists of all a((lication (rotocols t$at are used for radio net)or! controllin&" To trans(ort t$e 'essa&es of an a((lication (rotocol, one or several si&nalin& bearers, (rovided b* t$e trans(ort net)or!, are necessar*" User Plane : T$e user (lane su((orts t$e data strea's for user data" T$erefore t$e data strea's are (ac!ed into fra'e (rotocols" T$ese fra'e (rotocols )ill be trans'itted via data bearers" In contrast to t$e si&nalin& bearers of t$e control (lane, t$e data bearers can re-uire to be set u( )it$ e/(licit si&nalin&" Trans$ort Network 'ontrol Plane : T$e trans(ort net)or! control (lane contains t$e A:0AP (Access :in! 0ontrol A((lication Part)" T$e A:0AP (rotocols are used to set u( and release t$e data bearers of t$e user (lane" Also A:0AP 'essa&es re-uire a si&nalin& bearer for trans'ission" It is not necessar* to use t$e A:0AP for UTRAN and UMTS Radio Protocols /
I. UMTS Architecture all data bearers" +s(eciall* t$e trans(ort net)or! control (lane is not necessar*, )$en (re.confi&ured bearers onl* are used"
fi*ure 1( UTRAN $rotocol !odel for Iu, Iu, and Iur interfaces.
I. UMTS Architecture T$e use of t$e A:0AP is de(endent on t$e t*(e of bearer to be used" T$e si&nalin& bearers are usuall* (re.confi&ured" T$is 'eans t$ere is no d*na'ical set u( and release for si&nalin& bearers" 1ata bearers $ave to be set u( and released )it$ A:0AP, )$en t$e* are not (re. confi&ured" In t$is case t$e set u( runs in t$e follo)in& 'anner: 3" T$e set u( or release of a bearer is al)a*s controlled b* an a((lication (rotocol" =ut to avoid t$e restriction to a sin&le trans(ort s*ste', t$e a((lication (rotocols s$all not be s(ecific to a certain trans(ort solution" T$erefore t$e a((lication (rotocol can control t$e bearer via abstract (ara'eters (Eo (ara'eters) onl*" T$is (rinci(le is t$e sa'e as for =I00 (=earer Inde(endent 0all 0ontrol)" To tri&&er t$e set u( of a bearer first t$e a((lication (rotocol starts a (rocedure to t$e destination node" After t$e a((lication (rotocol tri&&ered t$e (rocedure, t$e A:0AP, t$at is s(ecific to t$e bearer to be set u(, (erfor's all necessar* (rocedures to confi&ure t$e bearer" #$en t$e a((lication (art receives t$e notification of a successful bearer set u(, t$e a((lication (rotocol (rocedure can be finis$ed, and t$e a((lication can be infor'ed to start t$e data strea' trans'ission"
7" 2"
I. UMTS Architecture
3a 7a 7c
Net)or! +le'ent A
A((lication Protocol : =earer etu( Re-uest A:0AP : =earer +stablis$'ent Re-uest A:0AP : =earer +stablis$'ent 0onfir'ed A((lication Protocol : =earer etu( 0o'(lete
Net)or! +le'ent =
2a
A((lication Protocols
2b 3b
A:0AP
1ata trea's
7b
1ata =earer
i&nallin& =earer
i&nallin& =earer
fi*ure 1) Inter5workin* ,etween control, network control and user $lane in UTRAN $rotocol !odel.
I. UMTS Architecture
T$e user (lane of t$e Iur interface $as t$e tas!s to trans(ort u(lin! and do)nlin! data for t$e U+ connected to a drift RN0" T$is tas!s re-uires t$e follo)in& (rotocols: 4ra!e Protocols: T$e data to and fro' t$e U+ )ill be enca(sulated into a fra'e" T$ese fra'es are defined b* so called fra'e (rotocols" T$ese fra'e (rotocols also allo) traffic 'ana&e'ent )it$ in.band si&nalin&" AA9 2, ATM : T$e fra'e (rotocols, t$at enca(sulate t$e U+ data, are trans(orted over AA: 7 virtual c$annels of ATM" T$ese AA: 7 virtual c$annels $ave to be set u( first"
=ecause t$e AA: 7 virtual c$annels re-uire a d*na'ical set u(, t$ere is a need for a trans(ort net)or! control (lane" T$is (lane contains t$e follo)in& (rotocols: AA9 t-$e 2 si*nalin* $rotocol: T$is (rotocol is an ITU.T (rotocol, used to set u(, release and 'odif* AA: 7 virtual c$annels" T$is is t$e Iur A:0AP" UTRAN and UMTS Radio Protocols (6
I. UMTS Architecture ST', MTP 7, SAA9, AA9 ), ATM : T$ese (rotocols (rovide t$e si&nalin& bearer for t$e AA: t*(e 7 si&nalin& (rotocol" T$e T0 ( i&nalin& Trans(ort 0onverter) (rovides functionalit* for con&estion $andlin& and load control" T$e (rotocol suite MTP 2=, AA:, AA:D and ATM can be s$ared )it$ t$e si&nalin& bearer of RN AP of t$e control (lane"
T$e ($*sical la*er used for to trans(ort t$e ATM cells on Iur is not s(ecified" It is u( to t$e o(erator to c$oose an a((ro(riate ($*sical trans'ission s*ste' (e"&" TM.3, TM. G or ON+T)"
RN AP AA: t*(e 7 P 00P MTP 57 SAA9 AA9 ) ST' MTP 57 SAA9 AA9 ) ATM Ph-sical 9a-er
Fra'e Protocols
AA9 2
(1
I. UMTS Architecture
T$e user (lane of t$e Iub interface $as to transfer t$e do)nlin! and u(lin! data to and fro' t$e U+" T$erefore different fra'es are defined in t$e sa'e )a* as on t$e Iur interface" In detail t$e user (lane consists of: 4ra!e Protocols: T$e Fra'e Protocols enca(sulate t$e U+ data (do)n. and u(lin!) on t$e Iub interface" AA9 2, ATM : T$e fra'e (rotocol (ac!ets are trans'itted via Iub usin& AA: 7 virtual c$annels" o AA: 7, ATM for' t$e data bearer on t$e Iub interface"
As on t$e Iur interface t$e Iub interface uses AA: 7 virtual c$annels for data strea' trans(ort" T$is 'eans t$at t$e trans(ort net)or! control (lane is necessar* for set u(, release and 'odification of AA: 7 virtual c$annels" T$e Iub trans(ort net)or! control (lane loo!s si'ilar to Iur: AA9 t-$e 2 si*nalin* $rotocol : T$e AA: t*(e 7 P (rovides t$e 'essa&es and function to set u(, release and 'odif* AA: 7 virtual c$annels" ST', SAA9, AA9 ), ATM : T$e T0 ( i&nalin& Trans(ort 0onverter), AA:, AA: D and ATM (rovide t$e si&nalin& bearer for t$e AA: t*(e 7 si&nalin& (rotocol" (Note: T$e T0 $ere is different to t$e T0 on Iur") UTRAN and UMTS Radio Protocols (2
I. UMTS Architecture T$e ($*sical la*er is not standardiFed" It is u( to t$e o(erator and vendor to c$oose an a((ro(riate ($*sical trans'ission s*ste'"
fi*ure 10 Iu, interface $rotocol stack ,etween controllin* RN' and Node 7.
Fra'e Protocols
I. UMTS Architecture
T$e user (lane on Iu.0 $as to su((ort t$e transfer of real ti'e circuit s)itc$ed data strea's" T$erefore t$e Iu.0 user (lane $as t$e follo)in& (rotocols: Iu UP %User Plane& $rotocol: T$e Iu UP (rotocol is used to (rovide additional su((ort functions for 0 data strea's on Iu" T$ese functions can be : ti'in& control, data rate control, bac!)ard error correction" AA9 2, ATM : For t$e data bearers to trans(ort t$e data strea's t$e AA: 7 virtual c$annels are used"
A&ain t$e trans(ort net)or! control (lane is necessar*, because AA: 7 virtual c$annels need to be set u( and released" o t$e (rotocol suite on t$e trans(ort net)or! control (lane is t$e alread* !no)n stac!, consistin& of: AA9 t-$e 2 si*nalin* $rotocol : Used to set u(, 'odif* and release AA: 7 virtual c$annels" UTRAN and UMTS Radio Protocols ((
I. UMTS Architecture
ST', MTP 7, SAA9, AA9 ), ATM : T$ese (rotocols (rovide t$e si&nalin& bearer for t$e AA: t*(e 7 si&nalin& (rotocol 'essa&es"
RANAP AA: t*(e 7 P 00P MTP 57 SAA9 AA9 ) ST' MTP 57 SAA9 AA9 ) ATM Ph-sical 9a-er
Iu UP (rotocol
AA9 2
()
I. UMTS Architecture
T$e user (lane on Iu.P is co'(letel* different to t$e user (lane of Iu.0 " T$is is because t$e traffic to and fro' % N is (ac!et s)itc$ed, so routin& la*er are necessar*" T$e UTRAN (rovides t$e follo)in& (rotocols on t$e Iu.P user (lane : Iu UP $rotocol: As for Iu.0 t$e Iu UP (rotocol can (rovide additional su((ort functions for t$e data strea'" In t$e 'o'ent (7883) t$e (ac!et s)itc$ed services do not use t$is (rotocol" 8TP5U %8PRS Tunnelin* Protocol 5 User $lane& : %TP.U (rovides a fra'e for t$e user data to be trans(orted" In a %TP.U fra'e U+ identifiers (IM I) and ot$er reference nu'ber and se-uence nu'bers are contained" UDP ? IP: T$e U1P , IP (rotocol suite is used as net)or! la*er bet)een RN0 and % N" T$e 'ain tas! of t$ese (rotocols is to route fro' RN0 to % N and vice versa" AA9 ), ATM : T$e ATM ada(tation la*er of t*(e D (connection less, variable bit rate, no s*nc$roniFation su((ort) is used as bearer for t$e (ac!ets of IP , U1P , %TP.U"
T$e AA: D virtual c$annels do not need to be set u( in a d*na'ical 'anner" Rat$er t$e o(erator is e/(ected to (re.confi&ure t$e AA: D bearer to be used for t$e (ac!et UTRAN and UMTS Radio Protocols (/
I. UMTS Architecture transfer" T$erefore on Iu.P t$ere is no need for a trans(ort net)or! control (lane, no bearer set u( )it$ e/(licit si&nalin& is necessar*"
RANAP
Iu UP (rotocol
(0
I. UMTS Architecture
(2
I. UMTS Architecture
5 Protocol Standardi@ation
(3
I. UMTS Architecture
To$ic UTRAN %eneral overvie) #01MA ($*sics Radio interface (rotocols Iu interface Iur interface Iub interface
T$e non access stratu' (NA ) (rotocols %MM, MM, 00 and M can be found in t$e reco''endation T 7G"88A" T$e reco''endation T 7G"88H contains an overvie) about t$e (rotocol stac! and t$e inter.)or!in& bet)een NA (rotocols and t$e radio (rotocols"
)6
I. UMTS Architecture
UTRAN
NAS $rotocols %8MM, SM, MM, ''&
'N
TS 2(.660, TS 2(.662
Menu
Iur Interface
TS 2).(2A
Iu, Interface Radio Protocols
TS 2).( A
Iu Interface
TS 2). AA U+
TS 2).(1A
)1
I. UMTS Architecture
)2