UTRAN RNC Types

November 16, 2007 by arvindpadmanabhan The Radio Network Controller (RNC) is a key element within TR!N "or it #ontrols all the radio reso$r#es o" TR!N% &owever, ea#h RNC #ontrols only reso$r#es $nder its #ontrol% There are m$ltiple RNCs in TR!N and as s$#h, #ontrol o" radio reso$r#es is done with a distrib$ted ar#hite#t$re% 'n this arti#le, we will "o#$s on the di""erent types o" RNCs that are de"ined in the standards% !s a preliminary let $s start with the TR!N ar#hite#t$re and the inter"a#es relatin( to an RNC ()i($re 1)%

'$b 'nter"a#e* #onne#ts to a Node+,% !n RNC #ontrols one or more Node+,s% '$r 'nter"a#e* #onne#ts to other RNCs% This inter"a#e is not ne#essarily a point+to+point link% '$ 'nter"a#e* inter"a#es to the Core Network (CN)% This is $s$ally broken down into '$+C- and '$+.- "or the respe#tive domains% There is also the '$+,C #omponent that #onne#ts to the ,road#ast /omain% '$r+( 'nter"a#e* #onne#ts to 01R!N ,-- whi#h is possible "rom Release 2 onwards when 01R!N #an operate in '$ mode% '$p# 'nter"a#e* #onne#ts to -tand+!lone -34C (-ervin( 3obile 4o#ation Center) to enable lo#ation+based servi#es% Figure 1: UTRAN Architecture

The spe#i"i#ations "re5$ently mention the "ollowin( lo(i#al separation*

CRNC* Controllin( RNC -RNC* -ervin( RNC /RNC* /ri"t RNC

The CRNC is responsible "or the #ontrollin( the reso$r#es o" a Node+,% 't is responsible "or load and #on(estion #ontrol% '" new radio links (R4s) are to be established CRNC does the 6ob%

7n the other hand, -RNC and /RNC are #on#epts that are tied to a 1+ TR!N #onne#tion on the $ inter"a#e% 'n other words, an -RNC serves a parti#$lar 1 and mana(es the #onne#tions towards that 1% 4ikewise, /RNC "$l"ils a similar role to the -RNC e8#ept that it is involved only in the #ase o" a so"t handover% Th$s the 1 initially starts a #onne#tion with an RNC that be#omes its -RNC% '" the 1 moves towards a #ell ed(e, -RNC may de#ide to p$t the 1 in so"t handover state% '" the new R4s added to 19s !#tive -et are $nder the #ontrol o" a di""erent RNC, that RNC be#omes the /RNC% The important thin( here is that CRNC is lo(i#ally tied to Node+,s, not #onne#tions% 7n the #ontrary, -RNC and /RNC are tied to #onne#tions to the 1% This implies that CRNC mana(es #ommon and shared reso$r#es while -RNC and /RNC mana(e dedi#ated reso$r#es% This does not imply that -RNC will be involved only when 1 RRC is in C144:/C& state% 1ven in C144:)!C& state, the 1 bein( allo#ated -i(nallin( Radio ,earers (-R,s), dedi#ated lo(i#al #hannels (/CC& and even /TC&) wo$ld have been established between 1 and -RNC% /RNC #annot be involved in this state be#a$se the prin#iple o" so"t handover applies only to dedi#ated physi#al #hannels% 7n#e this is $nderstood it be#omes easy to make sense o" many TR!N pro#ed$res and proto#ol termination points within TR!N% !s an e8ample, let $s look at the #ase o" )!C& ()i($re 2)% Figure 2: FACH Protocol Architecture

)i($re 2(a) is a #ase in whi#h the CRNC and -RNC are physi#ally on the same RNC% -o all that )!C& ). ()ramin( .roto#ol) does is to trans"er 3a# .d$s "rom the RNC to Node+,% 'n the Node+,, an interworkin( "$n#tion translates the )!C& "rames to .&; "rames on the $% )i($re 2(b) is a #ase in whi#h CRNC and -RNC are separate and #onne#ted by '$r% ! )!C& ). on '$r #arries the 3a#+d .d$s% 'n the CRNC, this is interworked with 3a#+#<sh<m% -$bse5$ently, )!C& ). on the '$b #arries it to the Node+,% 'n (eneral, 3a#+#<sh<m will reside on the CRNC sin#e they relate to the #ommon reso$r#es o" the #ell% 3a#+d (and 3a#+es in the #ase o" 1+/C&) resides on the -RNC% To $nderstand the di""eren#e between -RNC and /RNC, we take the e8ample o" a -RNRelo#ation pro#ed$re ()i($re =)%

Figure 3: SRNC Relocation

'n )i($re =(a), the 1 is in -&7 in whi#h 2 R4s are $nder the -RNC and one $nder the /RNC% !s the 1 #ontin$es to move away "rom its ori(inal #ells, all R4s in its !#tive -et are now $nder the /RNC ()i($re =(b))% -in#e the -RNC no lon(er mana(es any o" its own radio reso$r#es "or the 1, at some point it de#ides to trans"er the #omplete 1 #onte8t to the /RNC% !t this point, the ori(inal /RNC be#omes the -RNC% The new -RNC establishes

#onne#tion on the '$ inter"a#e to the CN% 't is always the -RNC that mana(es the R!N!. si(nallin( towards the CN% The RRC layer in TR!N resides in the -RNC whi#h takes #are o" mappin( Radio !##ess ,earer parameters to air inter"a#e transport #hannel parameters% The -RN- Relo#ation pro#ed$re is invoked within the -RNC RRC% ltimately, it is the -RNC that has an RRC #onne#tion with the 1% >hile the 1 is in 'nter+RNC -&7, '$r is invoked to trans"er data between the -RNC and /RNC% The /RNC ro$tes data transparently between the '$b and '$r inter"a#es% The /RNC may optionally (i" #on"i($red by the -RNC) #ombine or split data when relayin( data between '$b and '$r inter"a#es% This has the advanta(e o" red$#in( load on the '$r% 't also distrib$tes the pro#essin( load between the -RNC and the /RNC% 'n "a#t, these may be #onsiderations on whi#h the -RNC de#ides i" #ombinin(<splittin( is to be per"ormed at the /RNC% Nat$rally, #ombinin( is done on the 4 and splittin( is done on the /4% Two types o" data #ombinin( is possible* ma8im$m ratio #ombinin( or sele#tion #ombinin( based on 5$ality in"ormation asso#iated with ea#h T,- (Transport ,lo#k -et)% 7ne important e8#eption to this r$le is 1+/C& data handlin( at the /RNC% /RNC does not do #ombinin(% Combinin( is done in the Node+,s $nder the /RNC% This makes sense "or 1+ /C& "or whi#h .&; layer terminates at Node+,% The 1+/C& ). #arries only 3a#+es ./ s a#ross the '$b% This means that the -RNC #an re#eive d$pli#ates o" 3a#+es ./ s% Th$s one o" the "$n#tions o" the 3a#+es layer in the -RNC is to per"orm reorderin( "or in+se5$en#e delivery% This is not done at the /RNC whi#h transparently relays the 1+/C& ). "rom '$b to '$r ()i($re ?)% This is not the #ase with /C& "or whi#h .&; is distrib$ted between Node+, and RNC% Figure 4: !"CH Protocol Architecture

'n #on#l$sion, the terms CRNC, -RNC and /RNC are only lo(i#al de"initions based on "$n#tionality% .hysi#ally, an RNC may be a CRNC@-RNC or CRNC@/RNC% CRNC mana(es #ommon transport reso$r#es, #ode allo#ation, load and #on(estion #ontrol% -RNC mana(es the #onne#tion to the 1 and maintains the 1 #onte8t within TR!N% ()or this p$rpose, -+RNT' allo#ated to the 1 identi"ies the 1 $ni5$ely within the -RNC% This identity is mana(ed by the -RNC and will be reallo#ated d$rin( -RNC Relo#ation%) Th$s, o$ter loop power #ontrol, handover and R!N!. si(nallin( are mana(ed "rom the -RNC% /RNC mana(es reso$r#es $nder its #ontrol b$t relies on -RNC "or most de#isions and #ommands%

#i$e this:
4ike ,e the "irst to like this post% .osted in Te#hni#al Notes A Ta((ed CRNC, /RNC, Relo#ation, -RNC A B Comments

% Responses
1. on November 23, 2008 at 10:05 pm | ReplyAsha

&ello, #an yo$ please (ive an e8ample where CRNC and -RNC are di""erent (and #onne#ted thro$(h '$r inter"a#e)% ' am still not able to ima(ine this #on#ept% Thank yo$%

2. on November 29, 2008 at 10:16 am | Replyarvindpadmanabhan

)i($re 2(b) is an e8ample o" what yo$ are lookin( "or% 'n this #ase, CRNC is responsible "or #ontrollin( all #ommon reso$r#es on the #ell s$#h as )!C&% -RNC #ontains the dedi#ated #onte8t% 'n this e8ample, -RNC #arries the dedi#ated lo(i#al #hannels /TC& and /CC&% CRNC is $naware o" these lo(i#al #hannels sin#e they are transparently passed via )!C&+).% )inally, it is Node+, that maps these lo(i#al #hannels to the )!C&% 'n one network implementation, we #o$ld have one CRNC "or a one or more Node+,s and "ewer or less power"$l -RNCs% Network desi(ned this way wo$ld be more rob$st (no sin(le point o" "ail$re) than a network with 6$st -RNC entities% 't also makes sense "or load sharin(% &avin( said that, &-.! R7 and 4T1 networks are evolvin( in s$#h a way that RNC "$n#tionality is (oin( to be#ome part o" Node+,%

3. on

e!ember 1, 2008 at ":1" pm | Replyvi#ay

Cery (ood arti#leDEE Feep sharin( yo$r knowled(eDEE

4. on

e!ember 2, 2008 at 8:0" pm | ReplyAsha

Thank yo$% that was very in"ormative%

5. on

e!ember 15, 2008 at 2:31 pm | Reply$%&A

$se"$ll in"ormative

6. on 'ar!h 28, 2009 at 6:23 pm | ReplyAmina

>ell e8plainedDE Thank yo$

7. on $eptember 2, 2009 at ":23 pm | Reply$hrini

-o all s$pportin( sta#ks "or Node, and CN will be available in Node+, itsel"D ri(htG

8. on April 1(, 2010 at 12:11 pm | Replytom

0reat in"oEE H$estionG /oes the '$R proto#ol allow "or a 2nd /RNC to hand over to "rom the initial -RNCG ieD RNC !RNC ,RNC C% the #all ori(inates in RNC ! and is #arried to RNC ,I, thro$(h RNC , and then to RNC C "rom RNC ,% ' always see re"eren#es to the "irst /RNC b$t never to a 2nd /RNC% !ny in"o wo$ld be e8tremely help"$l% '" it helps to make it spe#i"i#, it relates to an 1ri#sson 3T- .6 TR!N plat"orm% !lon( with this 5$estion J answer is then an even lar(er 5$estion o" i" a Node , does not have an e8ternal TR!N #ell de"intion between the RNC ! and RNC C will it still handover between RNC , and RNC C i" the link is #reated between RNC ! RNC C Thanks a(ain

9. on )*ne 3, 2011 at 3:29 am | Reply+n*

' sto#ked at the transport media #on#ernin( the '$b, '$r and '$ inter"a#es% !ny in"ormation here wo$ld be (reatly appre#iated% Thank yo$ all%