3 Interface Protocol and Signaling Flow 49

Interface Protocol and
Signaling Flow
Version 3.00
ZTE CORPORATION
ZTE Plaza, Keji Road Sout,
!i"Te# Industrial Par$,
Nansan %istri#t, Senzen,
P. R. Cina
&'(0&)
Tel* +(,- )&& .,))'/00 (00"/(30"/(30
0a1* +(,- )&& .,))..3,
2R3* tt4*55su44ort.zte.#o6.#n
E"6ail* do#7zte.#o6.#n
Contents
Chapter 1..................................................................1
WCDMA UTRAN System Archetecture..........................1
UTRAN Architecture..........................................................1
Explanation Related to RNS...............................................2
UTRAN Common Protocol model.........................................3
Chapter 2..................................................................7
WCDMA Interface Hierarchy.......................................7
Control Plane and User Plane.............................................7
Access a!er and Non"access a!er....................................#
Chapter ..................................................................!
Interface an" #r$t$c$%...............................................!
Protocol $%er%ie&............................................................'
RRC Connection Setup...........................................................'
Net&or( Re)istration Process................................................11
Connection Release Process..................................................13
Protocol Related to *nter+ace Uu.......................................1,
Uu *nter+ace protocol architecture..........................................1,
Status o+ RRC Protocol.........................................................21
Some Explanations..............................................................22
Protocol related to *nter+ace *u.........................................23
*U inter+ace architecture.......................................................23
Protocol Structure o+ *u *nter+ace...........................................2-
Some Explanations..............................................................27
RANAP Process....................................................................2'
Protocol related to *nter+ace *ur........................................31
.unction and Structure o+ *nter+ace *ur...................................32
/C0 .rame Protocol o+ *nter+ace *ur.......................................32
RNSAP Process....................................................................32
Protocol Related to *nter+ace *u1......................................3-
Node 2 o)ic 3odel..............................................................3,
N2AP Process......................................................................37
Cell Setup Process..........................................................-4
CS Call $ri)ination .lo& 5RRC Setup on CC06.....................-1
CS Call $ri)ination .lo& 5RRC Setup on /C06....................-2
CS Call Termination .lo&.................................................-3
Release .lo& in CS /omain CN $ri)inates..........................--
Release .lo& in CS /omain UE $ri)inates..........................-,
Ch a p t e r 1
WCDMA UTRAN Sste!
Archetect"re
Hi&h%i&hts'
7C/3A UTRAN s!stem structure
0ierarch! &ith UTRAN protocol common model
2TRAN Ar#ite#ture
.i)ure 1 sho&s the o%erall architecture o+ 7C/3A UTRAN 5U3TS
Terrestrial Radio Access Net&or(6 s!stem o+ 38PP R-.
FI #UR$ 1 %&$RA'' UTRAN ARC(I T$CTUR$
RNS
RNC
RNS
RNC
Core Network
Node B Node B Node B Node B
Iu Iu
Iur
Iub
Iub
Iub Iub

UTRAN
The inter+ace 1et&een CN and UTRAN is *nter+ace *u.
*nside UTRAN9 the inter+ace 1et&een RNC and Node 2 is
*nter+ace *u1.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N 1
*nside UTRAN9 the inter+ace 1et&een RNCs is *nter+ace *ur.
*n addition9 the inter+ace 1et&een UTRAN and UE is *nter+ace
Uu.
E14lanation Related to RNS
RNS 5Radio Net&or( Su1s!stem6; The )eneral name +or one
RNC and all Nodes 2 it mana)es.
SRNC 5Ser%in) RNC6; The RNS connectin) &ith CN is called
SRNS and the RNC o+ RNS is called SRNC.
DRNC 5/ri+t RNC6; *n the case o+ so+t hando%er o+ 7C/3A9 UE
can use se%eral RNSs. .i)ure 2 sho&s the relation o+ SRNS and
/RNS.
FI #UR$ ) SRNS AND DRNS

SRNS
Core Network
Iu
DRNS
Iur
UE
Cells
Se%eral lin(s can exist inside one UE at the same time. The user
data to access /RNS is sent to SRNS +rom /RNS %ia *nter+ace
*ur. /RNC &on<t process the data 1ut transmit it 1et&een
*nter+ace *u1 and *nter+ace *ur transparentl!. $ne UE can access
one or se%eral /RNSs.
CRNC 5Control RNC6; 7hen UE access one RNS9 the RNC o+ the
RNS is called CRNC. There+ore9 in .i). 1.2"19 1oth SRNC and
/RNC are CRNC. CRNC mana)es the resources o+ the &hole cell.
SRNC schedules data on user /C0 and CRNC schedules data on
CC0.
.or Source RNC 5S"RNC6 and Tar)et RNC 5T"RNC69 re+er to
Chapter o+ *nter+ace *u.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N )
Chapter 1 7C/3A UTRAN S!stem Archetecture
2TRAN Co66on Proto#ol
6odel
.i)ure 3 sho&s the )eneral protocol model +or UTRAN *nter+aces9
and descri1ed in detail in the +ollo&in) su1clauses. The structure
is 1ased on the principle that the la!ers and planes are lo)icall!
independent o+ each other. There+ore9 as and &hen re=uired9 the
standardisation 1od! can easil! alter protocol stac(s and planes
to +it +uture re=uirements.
FI #UR$ * UTRAN C%MM%N PR%T%C%' M%D$'
A44li#ation
Proto#ol
%ata
Strea6+s-
A3CAP+s-
Trans4ort
Net8or$
3a9er
P9si#al 3a9er
Si:nallin:
;earer+s-
Trans4ort
2ser
Net8or$
Plane
Control Plane 2ser Plane
Trans4ort
2ser
Net8or$
Plane
Trans4ort Net8or$
Control Plane
Radio
Net8or$
3a9er
Si:nallin:
;earer+s-
%ata
;earer+s-
0ori>ontal9 The Protocol Structure consists o+ t&o main la!ers9
Radio Net&or( a!er9 and Transport Net&or( a!er. All UTRAN
related issues are %isi1le onl! in the Radio Net&or( a!er9 and
the Transport Net&or( a!er represents standard transport
technolo)! that is selected to 1e used +or UTRAN9 1ut &ithout
an! UTRAN speci+ic re=uirements.
?ertical9 UTRAn +alls into the +ollo&in) - planes; control plane 9
user plane 9 TN control plane 9 TN user plane.
Control plane
The Control Plane *ncludes the Application Protocol9 i.e.
RANAP9 RNSAP or N2AP9 and the Si)nallin) 2earer +or
transportin) the Application Protocol messa)es.
Amon) other thin)s9 the Application Protocol is used +or
settin) up 1earers +or 5i.e. Radio Access 2earer or Radio
in(6 in the Radio Net&or( a!er. *n the three plane
structure the 1earer parameters in the Application Protocol
are not directl! tied to the User Plane technolo)!9 1ut are
rather )eneral 1earer parameters.
The Si)nallin) 2earer +or the Application Protocol ma! or
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N *
*nter+ace Protocol and Si)nalin) .lo&
ma! not 1e o+ the same t!pe as the Si)nallin) Protocol +or
the ACAP. The Si)nallin) 2earer is al&a!s set up 1! $@3
actions.
User plane
The User Plane *ncludes the /ata Stream5s6 and the /ata
2earer5s6 +or the /ata Stream5s6. The /ata Stream5s6 isAare
characterised 1! one or more +rame protocols speci+ied +or
that inter+ace.
TN control plane
The Transport Net&or( Control Plane does not include an!
Radio Net&or( a!er in+ormation9 and is completel! in the
Transport a!er. *t includes the ACAP protocol5s6 that isAare
needed to set up the transport 1earers 5/ata 2earer6 +or the
User Plane. *t also includes the appropriate Si)nallin)
2earer5s6 needed +or the ACAP protocol5s6.
The Transport Net&or( Control Plane is a plane that acts
1et&een the Control Plane and the User Plane. The
introduction o+ Transport Net&or( Control Plane ma(es it
possi1le +or the Application Protocol in the Radio Net&or(
Control Plane to 1e completel! independent o+ the
technolo)! selected +or /ata 2earer in the User Plane.
7hen Transport Net&or( Control Plane is used9 the transport
1earers +or the /ata 2earer in the User Plane are set up in
the +ollo&in) +ashion. .irst there is a si)nallin) transaction 1!
the Application Protocol in the Control Plane9 &hich tri))ers
the set up o+ the /ata 2earer 1! the ACAP protocol that is
speci+ic +or the User Plane technolo)!.
The independence o+ Control Plane and User Plane assumes
that ACAP si)nallin) transaction ta(es place. *t should 1e
noted that ACAP mi)ht not 1e used +or all t!pes /ata
2earers. *+ there is no ACAP si)nallin) transaction9 the
Transport Net&or( Control Plane is not needed at all. This is
the case &hen pre"con+i)ured /ata 2earers are used.
*t should also 1e noted that the ACAP protocol5s6 in the
Transport Net&or( Control Plane isAare not used +or settin)
up the Si)nallin) 2earer +or the Application Protocol or +or
the ACAP durin) real time operation.
The Si)nallin) 2earer +or the ACAP ma! or ma! not 1e o+
the same t!pe as the Si)nallin) 2earer +or the Application
Protocol. The Si)nallin) 2earer +or ACAP is al&a!s set up 1!
$@3 actions.
TN user plane
The /ata 2earer5s6 in the User Plane9 and the Si)nallin)
2earer5s6 +or Application Protocol9 1elon) also to Transport
Net&or( User Plane. As descri1ed in the pre%ious su1clause9
the /ata 2earers in Transport Net&or( User Plane are
directl! controlled 1! Transport Net&or( Control Plane durin)
real time operation9 1ut the control actions re=uired +or
+ Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
Chapter 1 7C/3A UTRAN S!stem Archetecture
settin) up the Si)nallin) 2earer5s6 +or Application Protocol
are considered $@3 actions.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N ,
Ch a p t e r )
WCDMA Interface
(ierarch
Hi&h%i&hts'
8rasp the concepts o+ UTRAN control plane and user plane
Bno& a1out the protocols o+ UTRAN control plane
8rasp the concepts o+ access la!er and non"access la!er
Control Plane and 2ser
Plane
Purpose o+ the control plane;
Control the radio access 1earer and the connection 1et&een UE
and the net&or(C
Transmit messa)es o+ non"access la!er transparentl!.
Purpose o+ user plane;
Transmit the user data %ia the access net&or(.
*n UTRAN9 each inter+ace o+ RN has user plane and control
plane.
The control plane protocols o+ each inter+ace on RN include;
*nter+ace *u; RANAP
*nter+ace *ur; RANSAP
*nter+ace *u1; N2AP
*nter+ace ;Uu; RRC protocol
The user plane data and control plane data o+ all RN 1elon) to
TN user plane. TN control plane protocol is ACAP9 1elon)in)
to SAA 5Si)nallin) AA6 o+ AT3.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N -
A##ess 3a9er and Non"
a##ess 3a9er
The concepts o+ access la!er and non"access la!er are related to
the communication o+ UE and CN. The access la!er 1ears the
upper la!er ser%ices %ia the SAP 5Ser%ice Access Point69 as
sho&n in .i)ure -
FI #UR$ + ACC$SS 'A.$R AND N%N/ ACC$SS 'A.$R

2TRAN

2E CN
A##ess Stratu6
Non"A##ess Stratu6
Radio
+2u-
Iu
Radio
4roto"
#ols
+'-

Radio
4roto"
#ols
+'-
Iu
4roto
#ols
(2)
Iu
4roto
#ols
(2)

Example +or non"access la!er;
*n A3R %oice telephone 5the callin) part!69 there are se%eral UE"
CN si)nalin)9 &hich are the control plane si)nalin) o+ non"access
la!er. These si)nalin) are encapsulated in RRC protocol +irst and
then transmitted to RNC transparentl!. RNC decodes these
si)nalin) out o+ RRC messa)es9 encapsulates into RANAP9 and
then transmits to CN transparentl! %ia RANAP.
UERNC C3 Ser%ice Re=uest
RNCUE Authentication Re=uest
UERNC Authentication Response
RNCUE C3 Ser%ice Accept
UERNC SETUP
RNCUE Call Processin)
RNCUE Alertin)
RNCUE Connect
UERNC Connect Ac(no&led)e
Ch a p t e r *
Interface and Protocol
Hi&h%i&hts
8rasp the t!pes o+ protocols at UTRAN radio side
8rasp hierarch! o+ the protocols
8rasp the status o+ RRC protocol
Proto#ol O<er<ie8
2esides the process that UE searches +or the net9 UE re)istration
+all into 3 phases;
RRC connection setup
Net&or( re)istration
Connection release
RRC Conne#tion Setu4
.i)ure , sho&s the +lo& o+ RRC connection setup.
FI #UR$ , RRC C%NN$CTI %N S$TUP
5. Downlink Synchronistion
UE Node B
Serving RNS
Ser!in"
RNC
DC#$%& DC#$%&
'llocte RN(I
Select )* nd )2
+r,eters
RRC RRC
*. CCCH - RRC Connection Re.uest
NB'& NB'&
/. Rdio )ink Setu+ Res+onse
NB'& NB'&
2. Rdio )ink Setu+ Re.uest
RRC
RRC
0. CCCH - RRC Connection Setu+
Strt R1
descri+tion
Strt (1
descri+tion
2. ')C'& Iub Dt (rns+ort Berer Setu+
RRC
RRC
3. DCCH - RRC Connection Setu+ Co,+lete
DC#$%& DC#$%&
4. U+link Synchronistion
/etailed descriptions;
At the 1e)innin)9 UE does not ha%e dedicated channel resources9
so it sends the messa)e o+ RRC connection setup on CCC0
5RAC06.
RNC allocates RNT* and a%aila1le resources to UE9 decides to
allocate /C0 to UE9 and in+orm Node 2 to allocate /C0 to UE
&ith N2AP messa)e o+ DRadio in( Setup Re=uestE.
Node 2 allocates resources to UE9 starts to recei%e9 and returns
DRadio in( Setup ResponseE to RNC.
At this time9 there are no resources o+ the transmission net&or(
on *nter+ace *u19 so ACAP o+ SRNC sends the messa)e o+ ERF
5Esta1lish Re=uest6. This messa)e contains AA2 1indin) */.
This */ can help Node 2 to 1ind the data transmission 1earer on
*nter+ace *u1 and /C09 and sends the messa)e o+ EC. 5Esta1lish
Con+irm6 1ac( to RNC.
Node 2 and SRNC per+orm the +rame s!nchroni>ation %ia
D/o&nlin( S!nchroni>ationE and DUplin(. S!nchroni>ationE in
/C0 +rame protocol9 and then to per+orm the / transmission.
Althou)h /C0 resources on *nter+ace *u1 are read!9 UE does not
(no& it. There+ore9 SRNC sends the messa)e o+ DRRC
Connection SetupE to UE on CCC0 5.AC069 and in+orms UE o+
related parameters.
Accordin) to related parameters in DRRC Connection SetupE9 UE
Chapter 3 *nter+ace and Protocol
con+i)ures the ph!sical la!er. Node 2 sets up /C0 success+ull!
and sends the messa)e o+ DRRC Connection Setup CompleteE
1ac( to SRNC on /C0.
Net8or$ Re:istration Pro#ess
.i)ure G sho&s the +lo& o+ UE re)istration +or CS domain.
FI #UR$ 3 U$ '%CATI %N UPDAT$
A+ter RRC connection sets up9 UE esta1lishes /C0. UE needs to
1) Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
chan)e in+ormation &ith CN 5this is si)nalin) interaction o+ non"
access la!er and readers o+ non"access la!er si)nalin) can re+er
to H3I69 that is9 to initiate the ocation Update. This messa)e is
encapsulated in the RRC messa)e o+ *nitial /irect Trans+er9
&hich is sent to RNC 1! UE.
RRC o+ RNC recei%es the messa)e o+ *nitial /irect Trans+er9
decodes the hi)h"la!er messa)es +rom it9 and sends to RANAP
entit!. RANAP entit! &ill encapsulate the messa)e o+ Docation
UpdateE into *nitial UE 3essa)e and sends it to CN throu)h SCCP
entit!. At this time9 there is no si)nalin) connection 1et&een
RNC and CN9 so the messa)e o+ D*nitial UE 3essa)eE o+ RANAP is
encapsulated into SCCP connection setup massa)e 5CR6 and
sent to CN.
SCCP entit! o+ CN recei%es the SCCP connection setup re=uest.
*t returns SCCP connection setup messa)e 5CC6 to RNC and
sends the RANAP massa)e contained in CR messa)es to RANAP
entit!. RANAP entit! decodes the messa)e o+ Docation UpdateE
o+ NAS la!er and sends it to the related modules on NAS la!er
+or processin).
A+ter recei%in) the messa)e o+ Docation UpdateE +rom UE9 CN
initiates the authentication. The si)nallin) durin) the
authentication process is transmitted transparentl!. RNC and
Node 2 onl! trans+er 1et&een UE and CN9 1ut do not process
messa)es. 3essa)es o+ DAuthentication Re=uestE and
DAuthentication ResponseE are NAS messa)es9 too. The! are
encapsulated into the messa)e o+ D/irect Trans+erE o+ RANAP
and RRC.
A+ter the authentication chec( on UE is passed9 CN initiates the
securit! mode process. *t is to encr!pt and protect the data and
si)nalin) o+ the air inter+ace. 3essa)es o+ securit! mode are not
transmitted transparentl! and it needs RNC processin).
A+ter the authentication chec( is passed and the securit! mode
is initiated9 CN sends the messa)e o+ Docation Update AcceptE
to UE9 in+ormin) that UE re)istration succeeds. This messa)e is
transmitted transparentl!.
Conne#tion Release Pro#ess
.i)ure 7 sho&s the connection release process.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N 1*
FI #UR$ - RRC C%NN$CTI %N R$'$AS$
A+ter ocation Update completes9 CN initiates *u release process.
SRNC sends the messa)e o+ RRC connection release to RRC.
UE sends the messa)e o+ RRC connection release 1ac( to RNC.
RNC in+orms Node 2 to delete R and a+ter deletin) R9 Node 2
replies to RNC.
RNC in+orms CN that returns *u release completes %ia RANAP.
CN initiates to release SCCP lin( and RNC returns the messa)e
o+ SCCP release con+irmation.
RNC initiates to release the transmission resources on *nter+ace
*u1.
1+ Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
Proto#ol Related to Inter=a#e
2u
2u Inter=a#e 4roto#ol ar#ite#ture
.i)ure # sho&s the architecture o+ Uu *nter+ace protocol.
FI #UR$ 0 STRUCTUR$ %F RRC PR%T%C%'
L3
c
o
n
t
r
o
l
c
o
n
t
r
o
l
c
o
n
t
r
o
l
c
o
n
t
r
o
l
)o"icl
Chnnels
(rns+ort
Chnnels
C$+lne si"nllin"
U$+lne in5or,tion
&#6
L2/MAC
L1
R)C
DC
Nt
7C
L2/RLC
8'C
R)C
R)C
R)C
R)C
R)C
R)C
R)C
Du+liction !oidnce
UuS boundry
B8C
L2/BMC
control
&DC&
&DC& L2/PDCP
DC
Nt
7C
Rdio
Berers
RRC
The Uu inter+ace is la!ered into three protocol la!ers;
the ph!sical la!er 516C
the data lin( la!er 526C
net&or( la!er 536.
a!er 2 is split into +ollo&in) su1la!ers; 3edium Access Control
53AC69 Radio in( Control 5RC69 Pac(et /ata Con%er)ence
Protocol 5P/CP6 and 2roadcastA3ulticast Control 523C6. a!er 3
and RC are di%ided into Control 5C"6 and User 5U"6 planes.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N 1,
P/CP and 23C exist in the U"plane onl!.
*n the C"plane9 a!er 3 is partitioned into su1la!ers &here the
lo&est su1la!er9 denoted as Radio Resource Control 5RRC69
inter+aces &ith la!er 2 and terminates in the UTRAN. The next
su1la!er pro%ides J/uplication a%oidanceJ +unctionalit!. *t
terminates in the CN 1ut is part o+ the Access StratumC it
pro%ides the Access Stratum Ser%ices to hi)her la!ers. The
hi)her la!er si)nallin) such as 3o1ilit! 3ana)ement 5336 and
Call Control 5CC6 is assumed to 1elon) to the non"access
stratum..
The +unctions o+ RC;
The RC su1la!er pro%ides ARF +unctionalit! closel! coupled &ith
the radio transmission techni=ue used. There is no di++erence
1et&een RC instances in C and U planes.The UTRAN can 1e
re=uested 1! the CN to pre%ent all loss o+ data 5i.e.
independentl! o+ the hando%ers on the radio inter+ace69 as lon)
as the *u connection point is not modi+ied. This is a 1asic
re=uirement to 1e +ul+illed 1! the UTRAN retransmission
+unctionalit! as pro%ided 1! the RC su1la!er.0o&e%er9 in case
o+ the *u connection point is chan)ed 5e.). SRNS relocation9
streamlinin)69 the pre%ention o+ the loss o+ data ma! not 1e
)uaranteed autonomousl! 1! the UTRAN 1ut relies on
J/uplication a%oidanceJ +unctions in the CN.There are primaril!
t&o (inds o+ si)nallin) messa)es transported o%er the radio
inter+ace " RRC )enerated si)nallin) messa)es and NAS
messa)es )enerated in the hi)her la!ers. $n esta1lishment o+
the si)nallin) connection 1et&een the peer RRC entities three or
+our U3AA3 si)nallin) radio 1earers ma! 1e set up. T&o o+ these
1earers are set up +or transport o+ RRC )enerated si)nallin)
messa)es " one +or trans+errin) messa)es throu)h an
unac(no&led)ed mode RC entit! and the other +or trans+errin)
messa)es throu)h an ac(no&led)ed mode RC entit!.
The +unctions o+ 3AC include;
Mappin& (et)een %$&ica% channe%s an" transp$rt
channe%s. The 3AC is responsi1le +or mappin) o+ lo)ical
channel5s6 onto the appropriate transport channel5s6.
Se%ecti$n $f appr$priate Transp$rt *$rmat f$r each
Transp$rt Channe% "epen"in& $n instantane$us s$urce
rate. 8i%en the Transport .ormat Com1ination Set assi)ned
1! RRC9 3AC selects the appropriate transport +ormat &ithin
an assi)ned transport +ormat set +or each acti%e transport
channel dependin) on source rate. The control o+ transport
+ormats ensures e++icient use o+ transport channels.
#ri$rity han"%in& (et)een "ata f%$)s $f $ne U+. 7hen
selectin) 1et&een the Transport .ormat Com1inations in the
)i%en Transport .ormat Com1ination Set9 priorities o+ the
data +lo&s to 1e mapped onto the correspondin) Transport
Channels can 1e ta(en into account. Priorities are e.). )i%en
1! attri1utes o+ Radio 2earer ser%ices and RC 1u++er status.
The priorit! handlin) is achie%ed 1! selectin) a Transport
.ormat Com1ination +or &hich hi)h priorit! data is mapped
13 Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
onto 1 &ith a Khi)h 1it rateK Transport .ormat9 at the same
time lettin) lo&er priorit! data 1e mapped &ith a Klo& 1it
rateK 5could 1e >ero 1it rate6 Transport .ormat. Transport
+ormat selection ma! also ta(e into account transmit po&er
indication +rom a!er 1.
#ri$rity han"%in& (et)een U+s (y means $f "ynamic
sche"u%in&. *n order to utilise the spectrum resources
e++icientl! +or 1urst! trans+er9 a d!namic schedulin) +unction
ma! 1e applied. 3AC realises priorit! handlin) on common
and shared transport channels. Note that +or dedicated
transport channels9 the e=ui%alent o+ the d!namic schedulin)
+unction is implicitl! included as part o+ the recon+i)uration
+unction o+ the RRC su1la!er.
"entificati$n $f U+s $n c$mm$n transp$rt channe%s.
7hen a particular UE is addressed on a common do&nlin(
channel9 or &hen a UE is usin) the RAC09 there is a need +or
in1and identi+ication o+ the UE. Since the 3AC la!er handles
the access to9 and multiplexin) onto9 the transport channels9
the identi+ication +unctionalit! is naturall! also placed in 3AC.
3ultiplexin)Ademultiplexin) o+ upper la!er P/Us intoA+rom
transport 1loc(s deli%ered toA+rom the ph!sical la!er on
common transport channels. 3AC should support ser%ice
multiplexin) +or common transport channels9 since the
ph!sical la!er does not support multiplexin) o+ these
channels.
3ultiplexin)Ademultiplexin) o+ upper la!er P/Us intoA+rom
transport 1loc( sets deli%ered toA+rom the ph!sical la!er on
dedicated transport channels. The 3AC allo&s ser%ice
multiplexin) +or dedicated transport channels. This +unction
can 1e utilised &hen se%eral upper la!er ser%ices 5e.). RC
instances6 can 1e mapped e++icientl! on the same transport
channel. *n this case the identi+ication o+ multiplexin) is
contained in the 3AC protocol control in+ormation.
Traffic ,$%ume measurement. 3easurement o+ tra++ic
%olume on lo)ical channels and reportin) to RRC. 2ased on
the reported tra++ic %olume in+ormation9 RRC per+orms
transport channel s&itchin) decisions.
Transp$rt Channe% type s)itchin&. Execution o+ the
s&itchin) 1et&een common and dedicated transport
channels 1ased on a s&itchin) decision deri%ed 1! RRC.
Cipherin&. This +unction pre%ents unauthorised ac=uisition
o+ data. Cipherin) is per+ormed in the 3AC la!er +or
transparent RC mode.
Access Ser,ice C%ass se%ecti$n f$r RACH an" C#CH
transmissi$n. The RAC0 resources 5i.e. access slots and
pream1le si)natures6 and CPC0 resources 5i.e. access slots
and pream1le si)natures6 ma! 1e di%ided 1et&een di++erent
Access Ser%ice Classes in order to pro%ide di++erent priorities
o+ RAC0 and CPC0 usa)e. *n addition it is possi1le +or more
than one ASC or +or all ASCs to 1e assi)ned to the same
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N 1-
access slotAsi)nature space. Each access ser%ice class &ill
also ha%e a set o+ 1ac("o++ parameters associated &ith it9
some or all o+ &hich ma! 1e 1roadcast 1! the net&or(. The
3AC +unction applies the appropriate 1ac("o++ and indicates
to the P0L la!er the RAC0 and CPC0 partition associated to
a )i%en 3AC P/U trans+er.
The +unctions o+ P/CP include;
Hea"er c$mpressi$n an" "ec$mpressi$n. 0eader
compression and decompression o+ *P data streams 5e.).9
TCPA*P and RTPAU/PA*P headers6 at the transmittin) and
recei%in) entit!9 respecti%el!. The header compression
method is speci+ic to the particular net&or( la!er9 transport
la!er or upper la!er protocol com1inations e.). TCPA*P and
RTPAU/PA*P.
Transfer $f user "ata. Transmission o+ user data means
that P/CP recei%es P/CP S/U +rom the NAS and +or&ards it
to the RC la!er and %ice %ersa.
Supp$rt f$r %$ss%ess SRNS re%$cati$n. 3aintenance o+
P/CP se=uence num1ers +or radio 1earers that are
con+i)ured to support lossless SRNS relocation.
The +unctions o+ 23C include;
St$ra&e $f Ce%% -r$a"cast Messa&es.
The 23C stores the Cell 2roadcast messa)es recei%ed o%er
the C2C"RNC inter+ace +or scheduled transmission.
Traffic ,$%ume m$nit$rin& an" ra"i$ res$urce re.uest
f$r C-S.
At the UTRAN side9 the 23C calculates the re=uired
transmission rate +or Cell 2roadcast Ser%ice 1ased on the
messa)es recei%ed o%er the C2C"RNC inter+ace9 and re=uests
+or appropriate CTC0A.AC0 resources +rom RRC.
Sche"u%in& $f -MC messa&es.
The 23C recei%es schedulin) in+ormation to)ether &ith each
Cell 2roadcast messa)e o%er the C2C"RNC"inter+ace. 2ased
on this schedulin) in+ormation9 at the UTRAN side9 23C
)enerates schedule messa)es and schedules 23C messa)e
se=uences accordin)l!. At the UE side9 23C e%aluates the
schedule messa)es and indicates schedulin) parameters to
RRC9 &hich are used 1! RRC to con+i)ure the lo&er la!ers +or
C2S discontinuous reception.
Transmissi$n $f -MC messa&es t$ U+.
This +unction transmits the 23C messa)es 5Schedulin) and
Cell 2roadcast messa)es6 accordin) to schedule.
De%i,ery $f Ce%% -r$a"cast messa&es t$ upper %ayer
/NAS0.
This +unctions deli%ers the recei%ed Cell 2roadcast messa)es
to upper la!er 5NAS6 in the UE. $nl! non"corrupted Cell
2roadcast messa)es are deli%ered.
The +unctions o+ RRC include;
10 Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
The Radio Resource Control 5RRC6 la!er handles the control
plane si)nallin) o+ a!er 3 1et&een the UEs and UTRAN. The
RRC per+orms the +ollo&in) +unctions;
-r$a"cast $f inf$rmati$n pr$,i"e" (y the n$n1access
stratum /C$re Net)$r20. The RRC la!er per+orms s!stem
in+ormation 1roadcastin) +rom the net&or( to all UEs. The
s!stem in+ormation is normall! repeated on a re)ular 1asis.
The RRC la!er per+orms the schedulin)9 se)mentation and
repetition. This +unction supports 1roadcast o+ hi)her la!er
5a1o%e RRC6 in+ormation. This in+ormation ma! 1e cell
speci+ic or not. As an example RRC ma! 1roadcast Core
Net&or( location ser%ice area in+ormation related to some
speci+ic cells.
-r$a"cast $f inf$rmati$n re%ate" t$ the access
stratum. The RRC la!er per+orms s!stem in+ormation
1roadcastin) +rom the net&or( to all UEs. The s!stem
in+ormation is normall! repeated on a re)ular 1asis. The RRC
la!er per+orms the schedulin)9 se)mentation and repetition.
This +unction supports 1roadcast o+ t!picall! cell"speci+ic
in+ormation.
+sta(%ishment3 re1esta(%ishment3 maintenance an"
re%ease $f an RRC c$nnecti$n (et)een the U+ an"
UTRAN. The esta1lishment o+ an RRC connection is initiated
1! a re=uest +rom hi)her la!ers at the UE side to esta1lish
the +irst Si)nallin) Connection +or the UE. The esta1lishment
o+ an RRC connection includes an optional cell re"selection9
an admission control9 and a la!er 2 si)nallin) lin(
esta1lishment. The release o+ an RRC connection can 1e
initiated 1! a re=uest +rom hi)her la!ers to release the last
Si)nallin) Connection +or the UE or 1! the RRC la!er itsel+ in
case o+ RRC connection +ailure. *n case o+ connection loss9
the UE re=uests re"esta1lishment o+ the RRC connection. *n
case o+ RRC connection +ailure9 RRC releases resources
associated &ith the RRC connection.
+sta(%ishment3 rec$nfi&urati$n an" re%ease $f Ra"i$
-earers. The RRC la!er can9 on re=uest +rom hi)her la!ers9
per+orm the esta1lishment9 recon+i)uration and release o+
Radio 2earers in the user plane. A num1er o+ Radio 2earers
can 1e esta1lished to an UE at the same time. At
esta1lishment and recon+i)uration9 the RRC la!er per+orms
admission control and selects parameters descri1in) the
Radio 2earer processin) in la!er 2 and la!er 19 1ased on
in+ormation +rom hi)her la!ers.
Assi&nment3 rec$nfi&urati$n an" re%ease $f ra"i$
res$urces f$r the RRC c$nnecti$n. The RRC la!er handles
the assi)nment o+ radio resources 5e.). codes9 CPC0
channels6 needed +or the RRC connection includin) needs
+rom 1oth the control and user plane. The RRC la!er ma!
recon+i)ure radio resources durin) an esta1lished RRC
connection. This +unction includes coordination o+ the radio
resource allocation 1et&een multiple radio 1earers related to
the same RRC connection. RRC controls the radio resources
in the uplin( and do&nlin( such that UE and UTRAN can
communicate usin) un1alanced radio resources 5as!mmetric
uplin( and do&nlin(6. RRC si)nals to the UE to indicate
resource allocations +or purposes o+ hando%er to 8S3 or
other radio s!stems.
RRC c$nnecti$n m$(i%ity functi$ns. The RRC la!er
per+orms e%aluation9 decision and execution related to RRC
connection mo1ilit! durin) an esta1lished RRC connection9
such as hando%er9 preparation o+ hando%er to 8S3 or other
s!stems9 cell re"selection and cellApa)in) area update
procedures9 1ased on e.). measurements done 1! the UE.
#a&in&4n$tificati$n. The RRC la!er can 1roadcast pa)in)
in+ormation +rom the net&or( to selected UEs. 0i)her la!ers
on the net&or( side can re=uest pa)in) and noti+ication. The
RRC la!er can also initiate pa)in) durin) an esta1lished RRC
connection.
R$utin& $f hi&her %ayer #DUs. This +unction per+orms at
the UE side routin) o+ hi)her la!er P/Us to the correct hi)her
la!er entit!9 at the UTRAN side to the correct RANAP entit!.
C$ntr$% $f re.ueste" 5$S. This +unction shall ensure that
the FoS re=uested +or the Radio 2earers can 1e met. This
includes the allocation o+ a su++icient num1er o+ radio
resources.
U+ measurement rep$rtin& an" c$ntr$% $f the
rep$rtin&. The measurements per+ormed 1! the UE are
controlled 1! the RRC la!er9 in terms o+ &hat to measure9
&hen to measure and ho& to report9 includin) 1oth U3TS air
inter+ace and other s!stems. The RRC la!er also per+orms
the reportin) o+ the measurements +rom the UE to the
net&or(.
6uter %$$p p$)er c$ntr$%. The RRC la!er controls settin)
o+ the tar)et o+ the closed loop po&er control.
C$ntr$% $f cipherin&. The RRC la!er pro%ides procedures
+or settin) o+ cipherin) 5onAo++6 1et&een the UE and UTRAN.
Ar(itrati$n $f ra"i$ res$urces $n up%in2 DCH. This
+unction controls the allocation o+ radio resources on uplin(
/C0 on a +ast 1asis9 usin) a 1roadcast channel to send
control in+ormation to all in%ol%ed users.This +unction is
implemented in the CRNC.
Initia% ce%% se%ecti$n an" re1se%ecti$n in i"%e m$"e.
Selection o+ the most suita1le cell 1ased on idle mode
measurements and cell selection criteria.
Inte&rity pr$tecti$n. This +unction adds a 3essa)e
Authentication Code 53AC"*6 to those RRC messa)es that are
considered sensiti%e andAor contain sensiti%e in+ormation.
Initia% C$nfi&urati$n f$r C-S
This +unction per+orms the initial con+i)uration o+ the 23C
su1la!er.
)2 Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
A%%$cati$n $f ra"i$ res$urces f$r C-S
This +unction allocates radio resources +or C2S 1ased on
tra++ic %olume re=uirements indicated 1! 23C. The radio
resource allocation set 1! RRC 5i.e. the schedule +or mappin)
o+ CTC0 onto .AC0AS"CCPC06 is indicated to 23C to ena1le
)eneration o+ schedule messa)es. The resource allocation +or
C2S shall 1e 1roadcast as s!stem in+ormation.
C$nfi&urati$n f$r C-S "isc$ntinu$us recepti$n
This +unction con+i)ures the lo&er la!ers 519 26 o+ the UE
&hen it shall listen to the resources allocated +or C2S 1ased
on schedulin) in+ormation recei%ed +rom 23C.
Status o= RRC Proto#ol
*n 7C/3A9 all statuses o+ UE are scheduled 1! RRC protocol.
$ne UE has se%eral RRC statuses9 such as9 *dle and /C0. .i)ure
' sho&s the status and status con%ersion 5containin) 8S3
status6.
FI #UR$ 1 RRC STATUS AND STATUS C%N&$RSI %N
Esta>lis RRC
Conne#tion
Release RRC
Conne#tion
2TRA RRC Conne#ted ?ode
2TRA*
Inter"RAT
!ando<er
@S?*
!ando<er
Esta>lis RRC
Conne#tion
Release RRC
Conne#tion
2RAAPC!
CE33APC!
7S8
Connected
8ode
Estblish RR
Connection
Relese RR
Connection
Idle ?ode
Ca64in: on a 2TRAN #ell
'
Ca64in: on a @S? 5 @PRS #ell
'
@PRS Pa#$et Idle ?ode
'
7&RS
&cket
(rns5er
8ode
Initition o5
te,+orry
block 5low
Relese o5
te,+orry
block 5low
Cell resele#tion
CE33A%C!
out o=
ser<i#e
in
ser<i#e
CE33A0AC!
out o=
ser<i#e
in
ser<i#e
out o=
ser<i#e
in
ser<i#e
UE status is de+ined 1! the channel that UE uses.
CEM/C0 status indicates that UE occupies the dedicated
ph!sical channel.
CEM.AC0 status indicates that UE does not use an! dedicated
channel 1ut uses the common channel &hen the tra++ic is small.
U uses RAC0 and / uses .AC0. *n this status9 UE can initiate
cell reselection process and UTRAN can determine &hich cell UE
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N )1
locates in.
CEMPC0 status indicates that UE onl! intercepts PC0 and 2C0.
*n this status9 UE can reselect the cell. /urin) the reselection9 it
con%erts into CEM.AC0 status9 the cell update initiates9 and it
returns to CEMPC0 status. The net&or( can determine the cell
&hich the UE locates in.
URAMPC0 status is similar to CEMPC0 status. The net&or( can
onl! determine the URA cell &hich the UE locates in.
The introduction o+ CEMPC0 status and URAMPC0 status is to
(eep UE al&a!s in online status in order not to &aster radio
resources.
So6e E14lanations
*n CEMPC09 URAMPC0 or *dle status9 UE can intercept PC0 and
2C09 and can recei%e the messa)e o+ Pa)in). *n CEM/C0 or
CEM.AC0 status9 UE cannot intercept PC0 and 2C0. Pa)in)
T!pe 2 is introduced to pa)e UE in these t&o statuses.
Usuall!9 the permanent */ in+ormation o+ UE 5such as9 *3S*6 &ill
not 1e sa%ed in RNC. 7hen UE is ma(in) a call9 CN in+orms RNC
o+ the *3S* o+ the UE &ith the messa)e o+ Command */ o+
RANAP. 7hen CN re=uires RNC to pa)e a speci+ic UE9 RNC &ill
Nud)e &hich RRC status the *3S* to pa)e is in9 to decide the
pa)in) t!pe 5Pa)in) T!pe 1 or Pa)in) T!pe 26.
)) Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
Proto#ol related to Inter=a#e
Iu
I2 inter=a#e ar#ite#ture
Core Network (CN) UTRAN
Node B
Node B
Node B
Node B
RNC
Iu Interface
9Iu$BC:
9Iu$CS:
BC
Doa!n
C"
Doa!n
P"
Doa!n
9Iu$&S:
RNC
The *u inter+ace is speci+ied at the 1oundar! 1et&een the Core
Net&or( and UTRAN. .i)ure depicts the lo)ical di%ision o+ the *u
inter+ace. .rom the *u perspecti%e9 the UTRAN access point is an
RNC. The *u inter+ace to&ards the PS"domain o+ the core
net&or( is called *u"PS9 and the *u inter+ace to&ards the CS"
domain is called *u"CS. The di++erences 1et&een *u"CS and *u"
PS are treated else&here in the present document. The *u
inter+ace to the 2roadcast domain is called *u"2C.
There shall not 1e more than one *u inter+ace 5*u"PS6 to&ards
the PS"domain +rom an! one RNC. Each RNC shall not ha%e
more than one *u inter+ace 5*u"CS6 to&ards its de+ault CN node
&ithin the CS domain9 1ut ma! also ha%e +urther *u inter+aces
5*u"CS6 to&ards other CN nodes &ithin the CS domain. 5See HGI
+or de+inition o+ /e+ault CN node.6 These +urther *u inter+aces
5*u"CS6 shall onl! 1e used as a result o+ intra"3SC inter"s!stem
hando%er or SRNS relocation9 in the case the anchor CN node
directl! connects to the tar)et RNC. There shall not 1e more
than one *u inter+ace 5*u"2C6 +rom an RNC to&ards the
2roadcast domain.
*n the separated core net&or( architecture9 this means that
there shall 1e separate si)nallin) and user data connections
to&ards the PS and CS domains O this applies in 1oth transport
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N )*
and radio net&or( la!ers.
*n the com1ined architecture9 there shall 1e separate
connections in the user plane to&ards the PS and CS domains
5in 1oth transport and radio net&or( la!ers6. *n the control
plane9 there shall 1e separate SCCP connections to the t&o
lo)ical domains.
*n either architecture9 there can 1e se%eral RNCs &ithin UTRAN
and so UTRAN ma! ha%e se%eral *u access points to&ards the
Core Net&or(. As a minimum9 each *u access point 5in UTRAN or
CN6 shall independentl! +ul+il the re=uirements o+ the rele%ant *u
speci+ications
Proto#ol Stru#ture o= Iu Inter=a#e
.i)ure 14 sho&s the structure o+ *nter+ace *u"CS protocol and
.i)ure 11 sho&s the structure o+ *nter+ace *u"PS protocol.
FI #UR$ 12 STRUCTUR$ %F I U/ CS PR%T%C%'
;.2*5<.*
;.24/<.*
R'N'&
Iu U& &rotocol
)yer
(rns+ort
Network
)yer
&hysicl )yer
(rns+ort
User
Network
&lne
Control &lne User &lne
(rns+ort
User
Network
&lne
(rns+ort Network
Control &lne
Rdio
Network
)yer
'(8
SSC=&
'')5
SSC=&
SSC%$NNI
'')2 '')5
8(&/b 8(&/b
SCC&
SSC%$NNI
)+ Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
FI #UR$ 11 STRUCTUR$ %F I NT$RFAC$ I U/ PS PR%T%C%'
SSC%$NNI
SSC=&
'')5
I&
SC(&
SCC&
SSC%$NNI
8(&/$B
8/U'
R'N'&
Iu U& &rotocol
)yer
(rns+ort
Network
)yer
&hysicl )yer
(rns+ort
User
Network
&lne
Control &lne User &lne
(rns+ort
User
Network
&lne
(rns+ort Network
Control &lne
Rdio
Network
)yer
'(8
'')5
I&
UD&
7(&$U
&hysicl )yer
'(8
RANA#; user plane application protocol. *t pro%ides the
si)nallin) ser%ice 1et&een UTRAN and CN that is re=uired to
+ul+il the RANAP +unctions. RANAP protocol has the +ollo&in)
+unctions;
Relocatin) ser%in) RNC. This +unction ena1les to chan)e the
ser%in) RNC +unctionalit! as &ell as the related *u resources
5RA25s6 and Si)nallin) connection6 +rom one RNC to another.
$%erall RA2 mana)ement. This +unction is responsi1le +or
settin) up9 modi+!in) and releasin) RA2s.
Fueuin) the setup o+ RA2. The purpose o+ this +unction is to
allo& placin) some re=uested RA2s into a =ueue9 and
indicate the peer entit! a1out the =ueuin).
Re=uestin) RA2 release. 7hile the o%erall RA2 mana)ement
is a +unction o+ the CN9 the RNC has the capa1ilit! to re=uest
the release o+ RA2.
Release o+ all *u connection resources. This +unction is used
to explicitl! release all resources related to one *u
connection.
Re=uestin) the release o+ all *u connection resources. 7hile
the *u release is mana)ed +rom the CN9 the RNC has the
capa1ilit! to re=uest the release o+ all *u connection
resources +rom the correspondin) *u connection.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N ),
SRNS context +or&ardin) +unction. This +unction is
responsi1le +or trans+errin) SRNS context +rom the RNC to
the CN +or inters!stem chan)e in case o+ pac(et +or&ardin).
Controllin) o%erload in the *u inter+ace. This +unction allo&s
adNustin) the load in the *u inter+ace.
Resettin) the *u. This +unction is used +or resettin) an *u
inter+ace.
Sendin) the UE Common */ 5permanent NAS UE identit!6 to
the RNC. This +unction ma(es the RNC a&are o+ the UEJs
Common */.
Pa)in) the user. This +unction pro%ides the CN +or capa1ilit!
to pa)e the UE.
Controllin) the tracin) o+ the UE acti%it!. This +unction allo&s
settin) the trace mode +or a )i%en UE. This +unction also
allo&s the deacti%ation o+ a pre%iousl! esta1lished trace.
Transport o+ NAS in+ormation 1et&een UE and CN 5see H#I6.
This +unction has t&o su1"classes;
1. Transport o+ the initial NAS si)nallin) messa)e +rom the UE
to CN. This +unction trans+ers transparentl! the NAS
in+ormation. As a conse=uence also the *u si)nallin)
connection is set up.
2. Transport o+ NAS si)nallin) messa)es 1et&een UE and CN9
This +unction trans+ers transparentl! the NAS si)nallin)
messa)es on the existin) *u si)nallin) connection. *t also
includes a speci+ic ser%ice to handle si)nallin) messa)es
di++erentl!.
Controllin) the securit! mode in the UTRAN. This +unction is
used to send the securit! (e!s 5cipherin) and inte)rit!
protection6 to the UTRAN9 and settin) the operation mode +or
securit! +unctions.
Controllin) location reportin). This +unction allo&s the CN to
operate the mode in &hich the UTRAN reports the location o+
the UE.
ocation reportin). This +unction is used +or trans+errin) the
actual location in+ormation +rom RNC to the CN.
/ata %olume reportin) +unction. This +unction is responsi1le
+or reportin) unsuccess+ull! transmitted / data %olume o%er
UTRAN +or speci+ic RA2s.
Reportin) )eneral error situations. This +unction allo&s
reportin) o+ )eneral error situations9 +or &hich +unction
speci+ic error messa)es ha%e not 1een de+ined.
ocation related data. This +unction allo&s the CN to either
retrie%e +rom the RNC decipherin) (e!s 5to 1e +or&arded to
the UE6 +or the 1roadcasted assistance data9 or re=uest the
RNC to deli%er dedicated assistance data to the UE.
SCC#; The SCCP is used to support si)nallin) messa)es
1et&een the CNs and the RNC. $ne user +unction o+ the SCCP9
called Radio Access Net&or( Application Part 5RANAP69 is
de+ined. The RANAP uses one si)nallin) connection per acti%e UE
and CN +or the trans+er o+ la!er 3 messa)es. RANAP ma! use
SSN9 SPC andAor 8T and an! com1ination o+ them as addressin)
schemes +or the SCCP. 7hich o+ the a%aila1le addressin)
scheme to use +or the SCCP is an operator matter. A ne& SCCP
connection is esta1lished &hen in+ormation related to the
communication 1et&een a UE and the net&or( has to 1e
exchan)ed 1et&een RNC and CN9 and no SCCP connection exists
1et&een the CN and the RNC in%ol%ed9 +or the concerned UE.
MT#-' pro%ides messa)e routin)9 discrimination and
distri1ution 5+or point"to"point lin( onl!69 si)nalin) lin(
mana)ement load sharin) and chan)eo%erA1ac( 1et&een lin(
&ithin one lin("set. The need +or multiple lin("sets is precluded.
SAA71NNI' SAA"NN* H1I consists o+ the +ollo&in) su1"la!ers; "
SSC. H3I9 " SSC$P H2I and O AA, HGI. The SSC. maps the
re=uirements o+ the la!er a1o%e to the re=uirements o+ SSC$P.
Also SAA connection mana)ement9 lin( status and remote
processor status mechanisms are pro%ided. SSC$P pro%ides
mechanisms +or the esta1lishment and release o+ connections
and the relia1le exchan)e o+ si)nallin) in+ormation 1et&een
si)nallin) entities. Adapts the upper la!er protocol to the
re=uirements o+ the o&er AT3 cells.
*UUP; user plane protocol.
8T#1U' 8TP"U is used as the user data 1earer to&ards the PS
domain.RANAP Si)nallin) is used to esta1lish9 modi+! and
release the 8TP"U tunnels to&ards the PS domain.
AA72' AA2 is used as the user data 1earer to&ards the CS
domain.F.2G34.2 is used as the protocol +or d!namicall! setup
AA"2 connections o%er *u to&ards the CS domain. F.2G34.2
adds ne& optional capa1ilities to F.2G34.1.
So6e E14lanations
SRNS Relo#ation
$ne case;
UE crosses 2 RNSs durin) the mo%e9 as sho&n in .i)ure 12.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N )-
FI #UR$ 1) SRNS R$'%CATI %N 4 I 5
$ne UE can use 2 RNSs at the same time. The data can 1e sent
on t&o Rs. *n addition9 the data that UE sends to /RNC is sent
to SRNC %ia *nter+ace *ur9 and SRNC &ill com1ine them and
send to CN.
*+ UE continues to mo%e9 the R deterioration o+ UE on SRNS
cannot 1e used a)ain9 &hich &ill cause the +ollo&in) case.
FI #UR$ 1* SRNS R$'%CATI %N 4 I I 5
UE and SRNC ha%e no direct contact9 1ut all data still pass SRNC
and reach CN %ia *nter+ace *ur. *t &ill cause the &aste o+
resources. There+ore9 SRNS relocation should 1e initiated9 &hich
can mo%e *nter+ace *u +rom SRNC to /RNC. *n the course o+
SRNC relocation9 SRNC 5Ser%in) RNC6 is also called Source RNC
and /RNC is also called Tar)et RNC. .i)ure 1- sho&s the result
a+ter the relocation completes.
FI #UR$ 1+ SRNS R$'%CATI %N 4 I I I 5
SRNS relocation is the process to mo%e *nter+ace *u +rom Source
RNC to Tar)et RNC.
RANAP Pro#ess
TA6'$ 1 C'ASS 1
+%ementary
#r$ce"ure
Initiatin&
Messa&e
Successfu%
6utc$me
Unsuccessfu%
6utc$me
Response
messa)e
Response messa)e
*u Release *U
REEASE
C$33AN/
*U REEASE
C$3PETE
Relocation
Preparation
RE$CAT*
$N
REFU*RE/
RE$CAT*$N
C$33AN/
RE$CAT*$N
PREPARAT*$N
.A*URE
Relocation
Resource
Allocation
RE$CAT*
$N
REFUEST
RE$CAT*$N
REFUEST
ACBN$7E/8E
RE$CAT*$N
.A*URE
Relocation
Cancel
RE$CAT*
$N
CANCE
RE$CAT*$N
CANCE
ACBN$7E/8E
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N )1
+%ementary
#r$ce"ure
Initiatin&
Messa&e
Successfu%
6utc$me
Unsuccessfu%
6utc$me
Response
messa)e
Response messa)e
SRNS
Context
Trans+er
SRNS
C$NTEPT
REFUEST
SRNS C$NTEPT
RESP$NSE
Securit!
3ode
Control
SECUR*TL
3$/E
C$33AN/
SECUR*TL 3$/E
C$3PETE
SECUR*TL 3$/E
REQECT
/ata ?olume
Report
/ATA
?$U3E
REP$RT
REFUEST
/ATA ?$U3E
REP$RT
Reset RESET RESET
ACBN$7E/8E
Reset
Resource
RESET
RES$URCE
RESET RES$URCE
ACBN$7E/8E
ocation
related /ata
$CAT*$N
REATE/
/ATA
REFUEST
$CAT*$N
REATE/ /ATA
RESP$NSE
$CAT*$N
REATE/ /ATA
.A*URE
TA6'$ ) C'ASS )
+%ementary #r$ce"ure Messa&e
RA2 3odi+ication Re=uest RA2 3$/*.L REFUEST
RA2 Release Re=uest RA2 REEASE REFUEST
*u Release Re=uest *U REEASE REFUEST
Relocation /etect RE$CAT*$N /ETECT
Relocation Complete RE$CAT*$N C$3PETE
SRNS /ata .or&ardin) *nitiation SRNS /ATA .$R7AR/
C$33AN/
SRNS Context .or&ardin) +rom
Source RNC to CN
.$R7AR/ SRNS C$NTEPT
SRNS Context .or&ardin) to Tar)et
RNC +rom CN
.$R7AR/ SRNS C$NTEPT
Pa)in) PA8*N8
Common */ C$33$N */
CN *n%o(e Trace CN *N?$BE TRACE
CN /eacti%ate Trace CN /EACT*?ATE TRACE
ocation Reportin) Control $CAT*$N REP$RT*N8
C$NTR$
ocation Report $CAT*$N REP$RT
*nitial UE 3essa)e *N*T*A UE 3ESSA8E
*2 Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
/irect Trans+er /*RECT TRANS.ER
$%erload Control $?ER$A/
Error *ndication ERR$R *N/*CAT*$N
TA6'$ * C'ASS *
+%ementary
#r$ce"ure
Initiatin&
Messa&e
Resp$nse Messa&e
RA2 Assi)nment RA2 ASS*8N3ENT
REFUEST
RA2 ASS*8N3ENT
RESP$NSE x N 5NRS16
Proto#ol related to Inter=a#e
Iur
The hi)hest la!er protocol o+ *nter+ace *ur control plane is
RANSAP. .i)ure 1, sho&s the structure o+ *nter+ace *ur protocol.
FI #UR$ 1, STRUCTUR$ %F I NT$RFAC$ I UR PR%T%C%'
SSC0"NNI
SSCOP
?TP3";
AA3&
IP
SCTP
SCCP
AA3&
SSC0"NNI
STC +B..'&0.'-
RNSAP
Iur %ata
Strea6+s-
Trans4ort
Net8or$
3a9er
P9si#al 3a9er
Trans4ort
2ser
Net8or$
Plane
Control Plane 2ser Plane
Trans4ort
2ser
Net8or$
Plane
Trans4ort Net8or$
Control Plane
Radio
Net8or$
3a9er
AT?
A3CAP+B..,30.'-
AA3.
SSC0"NNI
SSCOP
?TP3";
IP
SCTP
SSC0"NNI
?32A ?32A
The protocol structure o+ *nter+ace *ur control plane 5includin)
RN and TN6 is same as that o+ *nter+ace *u control plane.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N *1
0un#tion and Stru#ture o= Inter=a#e
Iur
*nter+ace *ur is to transmit data &hen UE per+orms the so+t
hando%er 1et&een adNacent RNCs.
38PP prescri1es that *nter+ace *ur is a lo)ic entit!. That is9
*nter+ace *ur and *nter+ace *u can either share one channel +or
the transmission or connect %ia independent ph!sical inter+ace.
%C! 0ra6e Proto#ol o= Inter=a#e Iur
As sho&n in .i) 3.3"39 &hen UE crosses RNSs9 /RNC can
+or&ard /C0 data to SRNC %ia *nter+ace *ur. /RNC does not
process /C0 data 1ut directl! send /C0 data at *nter+ace *u1 to
*nter+ace *ur. /C0 +rames o+ *nter+ace *ur and *nter+ace *u1 (eep
consistent9 to )reatl! reduce /C0 data processin) 1! /RNC.
RNSAP Pro#ess
TA6'$ + C'ASS 1 $'$M$NTAR. PR%C$DUR$S
+%ementary
#r$ce"ure
Initiatin&
Messa&e
Successfu%
6utc$me
Unsuccessfu%
6utc$me
Response
messa)e
Response
messa)e
Radio in(
Setup
RA/*$ *NB
SETUP
REFUEST
RA/*$ *NB
SETUP
RESP$NSE
RA/*$ *NB
SETUP .A*URE
Radio in(
Addition
RA/*$ *NB
A//*T*$N
REFUEST
RA/*$ *NB
A//*T*$N
RESP$NSE
RA/*$ *NB
A//*T*$N
.A*URE
Radio in(
/eletion
RA/*$ *NB
/EET*$N
REFUEST
RA/*$ *NB
/EET*$N
RESP$NSE
S!nchronise
d Radio in(
Recon+i)urati
on
Preparation
RA/*$ *NB
REC$N.*8UR
AT*$N
PREPARE
RA/*$ *NB
REC$N.*8URAT
*$N REA/L
RA/*$ *NB
REC$N.*8URAT*$
N .A*URE
Uns!nchroni
sed Radio
in(
Recon+i)urati
on
RA/*$ *NB
REC$N.*8UR
AT*$N
REFUEST
RA/*$ *NB
REC$N.*8URAT
*$N RESP$NSE
RA/*$ *NB
REC$N.*8URAT*$
N .A*URE
*) Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
+%ementary
#r$ce"ure
Initiatin&
Messa&e
Successfu%
6utc$me
Unsuccessfu%
6utc$me
Response
messa)e
Response
messa)e
Ph!sical
Channel
Recon+i)urati
on
P0LS*CA
C0ANNE
REC$N.*8UR
AT*$N
REFUEST
P0LS*CA
C0ANNE
REC$N.*8URAT
*$N C$33AN/
P0LS*CA
C0ANNE
REC$N.*8URAT*$
N .A*URE
/edicated
3easuremen
t *nitiation
/E/*CATE/
3EASURE3E
NT
*N*T*AT*$N
REFUEST
/E/*CATE/
3EASURE3ENT
*N*T*AT*$N
RESP$NSE
/E/*CATE/
3EASURE3ENT
*N*T*AT*$N
.A*URE
Common
Transport
Channel
Resources
*nitialisation
C$33$N
TRANSP$RT
C0ANNE
RES$URCES
REFUEST
C$33$N
TRANSP$RT
C0ANNE
RES$URCES
RESP$NSE
C$33$N
TRANSP$RT
C0ANNE
RES$URCES
.A*URE
Common
3easuremen
t *nitiation
C$33$N
3EASURE3E
NT
*N*T*AT*$N
REFUEST
C$33$N
3EASURE3ENT
*N*T*AT*$N
RESP$NSE
C$33$N
3EASURE3ENT
*N*T*AT*$N
.A*URE
*n+ormation
Exchan)e
*nitiation
*N.$R3AT*$
N EPC0AN8E
*N*T*AT*$N
REFUEST
*N.$R3AT*$N
EPC0AN8E
*N*T*AT*$N
RESP$NSE
*N.$R3AT*$N
EPC0AN8E
*N*T*AT*$N
.A*URE
TA6'$ , C'ASS ) $'$M$NTAR. PR%C$DUR$S
+%ementary #r$ce"ure Initiatin& Messa&e
Uplin( Si)nallin) Trans+er UP*NB S*8NA*N8 TRANS.ER
*N/*CAT*$N
/o&nlin( Si)nallin) Trans+er /$7N*NB S*8NA*N8 TRANS.ER
REFUEST
Relocation Commit RE$CAT*$N C$33*T
Pa)in) PA8*N8 REFUEST
S!nchronised Radio in(
Recon+i)uration Commit
RA/*$ *NB REC$N.*8URAT*$N
C$33*T
Recon+i)uration Cancellation
CANCE
Radio in( .ailure RA/*$ *NB .A*URE *N/*CAT*$N
Radio in( Restoration RA/*$ *NB REST$RE *N/*CAT*$N
/edicated 3easurement
Reportin)
/E/*CATE/ 3EASURE3ENT REP$RT
Termination
/E/*CATE/ 3EASURE3ENT
TER3*NAT*$N REFUEST
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N **
+%ementary #r$ce"ure Initiatin& Messa&e
.ailure
/E/*CATE/ 3EASURE3ENT .A*URE
*N/*CAT*$N
/o&nlin( Po&er Control
H.//I
/ P$7ER C$NTR$ REFUEST
Compressed 3ode Command
H.//I
C$3PRESSE/ 3$/E C$33AN/
Common Transport Channel
Resources Release
C$33$N TRANSP$RT C0ANNE
RES$URCES REEASE REFUEST
/o&nlin( Po&er Timeslot
Control HT//I
/ P$7ER T*3ES$T C$NTR$
REFUEST
Radio in( Pre"emption RA/*$ *NB PREE3PT*$N REFU*RE/
*N/*CAT*$N
Radio in( Con)estion RA/*$ *NB C$N8EST*$N
*N/*CAT*$N
Common 3easurement
Reportin)
C$33$N 3EASURE3ENT REP$RT
Common 3easurement
Termination
C$33$N 3EASURE3ENT
TER3*NAT*$N REFUEST
Common 3easurement
.ailure
C$33$N 3EASURE3ENT .A*URE
*N/*CAT*$N
*n+ormation Reportin) *N.$R3AT*$N REP$RT
*n+ormation Exchan)e
Termination
*N.$R3AT*$N EPC0AN8E
TER3*NAT*$N REFUEST
.ailure
*N.$R3AT*$N EPC0AN8E .A*URE
*N/*CAT*$N
Proto#ol Related to Inter=a#e
Iu>
The hi)h la!er protocol o+ *nter+ace *u1 control plane is N2AP.
The user plane consists o+ se%eral +rame protocols. .i)ure 1G
sho&s the structure o+ protocols.
*+ Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
FI #UR$ 13 STRUCTUR$ %F I NT$RFAC$ I U6 PR%T%C%'
Node B
'++liction &rt
(NB'&)
'') (y+e 2
ALCAP
(rns+ort
)yer
&hysicl )yer
Rdio
Network
)yer
Rdio Network
Control &lne
(rns+ort
Network
Control &lne
D
C
#

%
&
R
'
C
#

%
&
'(8
D
S
C
#

%
&
'') (y+e 5
User &lne
SSC%$UNI
SSC=&
'') (y+e 5
SSC%$UNI
SSC=&
;.24/<.*
;.2*5<.2
%
'
C
#

%
&
&
C
#

%
&
U
S
C
#

%
&
C
&
C
#

%
&
N2AP includes Node 2 lo)ic $@3 and dedicated N2AP.
Node ; 3o:i# ?odel
FI #UR$ 1- N%D$ 6 '%#I C M%D$'
777 777
Node 6
777
Cell Cell Cell Cell Cell Cell
Node B Co,,uniction Conte>ts?
with ttributes
Co,,on (rns+ort Chnnels?
with ttributes
Node ;
Control
Port
Iu>
RAC!
%ata
4ort
Iu>
0AC!
%ata
4ort
Iu>
PC!
%ata
4ort
Controlling RNC
Iu>
0%%
CPC!
%ata
4ort
Tra==i# ter6ination 4oint
Co66uni#ation
Control
Port
Iu>
T%% 2SC!
%ata
4ort
Iu>
%C!
%ata
4ort
Iu>
%SC!
%ata
4ort
Iu>
0%% T0CI.
%ata
4ort
Tra==i# ter6ination 4oint
Co66uni#ation
Control
Port
Iu>
T%% 2SC!
%ata
4ort
Iu>
%C!
%ata
4ort
Iu>
%SC!
%ata
4ort
Iu>
0%% T0CI.
%ata
Port
Node 2 lo)ic model consists o+ cell9 common transmission
channelAport9 Node 2 communication context9 and the
correspondin) /SC0A/C0. Node 2 controls NCP and the
communication controls port CCP9 etc.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N *,
Node 2 communication context and the correspondin)
/SC0A/C0 port are related to dedicated user ser%ices.
Node 2 communication context is correspondin) to CRNC
communication context.
Node 2 communication context is identi+ies 1! Node 2
Communication Text */9 containin) necessar! in+ormation to
communicate &ith UE. *t is esta1lished &hen R is setup and
deleted &hen R is deleted.
There is onl! one NCP lin( on one Node 2. RNC sends all Node 2
common control si)nalin) +rom NCP. NCP lin( must 1e setup
1e+ore operatin)9 maintainin)9 and controllin) Node 2.
There can 1e se%eral CCP lin(s on one Node 2. RNC sends all
Node 2 dedicated control si)nalin) +rom CCP lin(. Usuall!9 one
cell inside Node 2 can 1e con+i)ured &ith one CCP 5it is Nust a
routine9 not certain.6
N;AP Pro#ess
TA6'$ 3 C'ASS 1
+%ementary
#r$ce"ure
Messa&e
Successfu%
6utc$me
Unsuccessfu%
6utc$me
Response
messa)e
Response
messa)e
Cell Setup CE SETUP
REFUEST
CE SETUP
RESP$NSE
CE SETUP
.A*URE
Cell
Recon+i)urati
on
CE
REC$N.*8U
RAT*$N
REFUEST
CE
REC$N.*8URAT*
$N RESP$NSE
CE
REC$N.*8URAT*
$N .A*URE
Cell /eletion CE
/EET*$N
REFUEST
CE /EET*$N
RESP$NSE
Common
Transport
Channel
Setup
C$33$N
TRANSP$RT
C0ANNE
SETUP
REFUEST
C$33$N
TRANSP$RT
C0ANNE SETUP
RESP$NSE
C$33$N
TRANSP$RT
C0ANNE SETUP
.A*URE
Common
Transport
Channel
Recon+i)urati
on
C$33$N
TRANSP$RT
C0ANNE
REC$N.*8U
RAT*$N
REFUEST
C$33$N
TRANSP$RT
C0ANNE
REC$N.*8URAT*
$N RESP$NSE
C$33$N
TRANSP$RT
C0ANNE
REC$N.*8URAT*
$N .A*URE
Common
Transport
Channel
/eletion
C$33$N
TRANSP$RT
C0ANNE
/EET*$N
REFUEST
C$33$N
TRANSP$RT
C0ANNE
/EET*$N
RESP$NSE
Ph!sical
Shared
Channel
Recon+i)ure
HT//I
P0LS*CA
S0ARE/
C0ANNE
REC$N.*8U
RAT*$N
REFUEST
P0LS*CA
S0ARE/
C0ANNE
REC$N.*8URAT*
$N RESP$NSE
P0LS*CA
S0ARE/
C0ANNE
REC$N.*8URAT*
$N .A*URE
Audit AU/*T
REFUEST
AU/*T
RESP$NSE
AU/*T .A*URE
2loc(
Resource
2$CB
RES$URCE
REFUEST
2$CB
RES$URCE
RESP$NSE
2$CB
RES$URCE
.A*URE
Radio in(
Setup
RA/*$ *NB
SETUP
REFUEST
RA/*$ *NB
SETUP
RESP$NSE
RA/*$ *NB
SETUP .A*URE
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N *-
+%ementary
#r$ce"ure
Messa&e
Successfu%
6utc$me
Unsuccessfu%
6utc$me
Response
messa)e
Response
messa)e
S!stem
*n+ormation
Update
SLSTE3
*N.$R3AT*
$N UP/ATE
REFUEST
SLSTE3
*N.$R3AT*$N
UP/ATE
RESP$NSE
SLSTE3
*N.$R3AT*$N
UP/ATE .A*URE
Common
3easurement
*nitiation
C$33$N
3EASURE3E
NT
*N*T*AT*$N
REFUEST
C$33$N
3EASURE3ENT
*N*T*AT*$N
RESP$NSE
C$33$N
3EASURE3ENT
*N*T*AT*$N
.A*URE
Radio in(
Addition
RA/*$ *NB
A//*T*$N
REFUEST
RA/*$ *NB
A//*T*$N
RESP$NSE
RA/*$ *NB
A//*T*$N
.A*URE
Radio in(
/eletion
RA/*$ *NB
/EET*$N
REFUEST
RA/*$ *NB
/EET*$N
RESP$NSE
S!nchronised
Radio in(
Recon+i)urati
on
Preparation
RA/*$ *NB
REC$N.*8U
RAT*$N
PREPARE
RA/*$ *NB
REC$N.*8URAT*
$N REA/L
RA/*$ *NB
REC$N.*8URAT*
$N .A*URE
Uns!nchronis
ed Radio in(
Recon+i)urati
on
RA/*$ *NB
REC$N.*8U
RAT*$N
REFUEST
RA/*$ *NB
REC$N.*8URAT*
$N RESP$NSE
RA/*$ *NB
REC$N.*8URAT*
$N .A*URE
/edicated
3easurement
*nitiation
/E/*CATE/
3EASURE3E
NT
*N*T*AT*$N
REFUEST
/E/*CATE/
3EASURE3ENT
*N*T*AT*$N
RESP$NSE
/E/*CATE/
3EASURE3ENT
*N*T*AT*$N
.A*URE
Reset RESET
REFUEST
RESET
RESP$NSE
Cell
S!nchronisati
on *nitiation
H3.#-3cps
T//I
CE
SLNC0R$N*
SAT*$N
*N*T*AT*$N
REFUEST
CE
SLNC0R$N*SAT*
$N *N*T*AT*$N
RESP$NSE
CE
SLNC0R$N*SAT*
$N *N*T*AT*$N
.A*URE
Cell
S!nchronisati
on
Recon+i)urati
on H3.#-
3cps T//I
CE
SLNC0R$N*
SAT*$N
REC$N.*8U
RAT*$N
REFUEST
CE
SLNC0R$N*SAT*
$N
REC$N.*8URAT*
$N RESP$NSE
CE
SLNC0R$N*SAT*
$N
REC$N.*8URAT*
$N .A*URE
Cell
S!nchronisati
on
AdNustment
H3.#-3cps
T//I
CE
SLNC0R$N*
SAT*$N
A/QUST3EN
T REFUEST
CE
SLNC0R$N*SAT*
$N A/QUST3ENT
RESP$NSE
CE
SLNC0R$N*SAT*
$N A/QUST3ENT
.A*URE
+%ementary
#r$ce"ure
Messa&e
Successfu%
6utc$me
Unsuccessfu%
6utc$me
Response
messa)e
Response
messa)e
*n+ormation
Exchan)e
*nitiation
*N.$R3AT*
$N
EPC0AN8E
*N*T*AT*$N
REFUEST
*N.$R3AT*$N
EPC0AN8E
*N*T*AT*$N
RESP$NSE
*N.$R3AT*$N
EPC0AN8E
*N*T*AT*$N
.A*URE
TA6'$ - C'ASS )
Resource Status *ndication RES$URCE STATUS *N/*CAT*$N
Audit Re=uired AU/*T REFU*RE/ *N/*CAT*$N
Common 3easurement
Reportin)
C$33$N 3EASURE3ENT REP$RT
Common 3easurement
Termination
C$33$N 3EASURE3ENT
TER3*NAT*$N REFUEST
Common 3easurement
.ailure
C$33$N 3EASURE3ENT .A*URE
*N/*CAT*$N
Recon+i)uration Commit
C$33*T
Recon+i)uration Cancellation
CANCE
Radio in( .ailure RA/*$ *NB .A*URE *N/*CAT*$N
Radio in( Restoration RA/*$ *NB REST$RE *N/*CAT*$N
Reportin)
/E/*CATE/ 3EASURE3ENT REP$RT
Termination
/E/*CATE/ 3EASURE3ENT
TER3*NAT*$N REFUEST
.ailure
/E/*CATE/ 3EASURE3ENT .A*URE
*N/*CAT*$N
/o&nlin( Po&er Control
H.//I
/ P$7ER C$NTR$ REFUEST
Compressed 3ode Command
H.//I
C$3PRESSE/ 3$/E C$33AN/
Un1loc( Resource UN2$CB RES$URCE *N/*CAT*$N
/o&nlin( Po&er Timeslot
Control HT//I
/ P$7ER T*3ES$T C$NTR$
REFUEST
Radio in( Pre"emption RA/*$ *NB PREE3PT*$N REFU*RE/
*N/*CAT*$N
Cell S!nchronisation
Reportin) H3.#-3cps T//I
CE SLNC0R$N*SAT*$N REP$RT
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N *1
Cell S!nchronisation
Termination H3.#-3cps T//I
CE SLNC0R$N*SAT*$N
TER3*NAT*$N REFUEST
Cell S!nchronisation .ailure
H3.#-3cps T//I
CE SLNC0R$N*SAT*$N .A*URE
*N/*CAT*$N
*n+ormation Reportin) *N.$R3AT*$N REP$RT
Termination
*N.$R3AT*$N EPC0AN8E
TER3*NAT*$N REFUEST
.ailure
*N.$R3AT*$N EPC0AN8E .A*URE
*N/*CAT*$N
Cell Setu4 Pro#ess
FI #UR$ 10 C$'' S$TUP PR%C$SS
RNC Node B
NB'&. Cell setu+ re.uest
NC&?CC& nd ')C'& set u+
Reset +rocess
NB'& nd cell setu+ res+onse
NB'& nd SCC&C# setu+ re.uest
NB'& nd SCC&C# setu+ res+onse
')C'&: ER;(%'C#)
')C'& -EC%
')C'&-ER;(&C#)
')C'&-EC%
NB'&- R'C# setu+ re.uest
NB'&- R'C# setu+ res+onse
')C'&-ER;( R'C#)
')C'&- EC%
NB'&- Syste, in5or,tion u+dte re.uest
NB'&- Syste, in5or,tion u+dte res+onse
Node B
strtu+
+rocess
Cell setu+
+rocess
%& synchroni@tion +rocess
&CC&C#
+2 Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
CS Call Ori:ination 0lo8
+RRC Setu4 on CC!-
FI #UR$ 11 CA'' %RI #I NATI %N F'%W 4 RRC S$TUP %N CC(5

RRC connection re..
R'C# ACCC#

R) setu+ re.
R) setu+ res+
.
')C'& ES(. re.
')C'& ES(. c5n
RRC connection setu+( %'C# ACCC#)
RRC connection setu+ co,+.(R'C#BDCC#)
INI(I') D((C8 ser!ice re.)( DCC#)
D((setu+)
D((cll +roceedin")
D(('uthentiction re.)
D(('uthentiction res+)
Initil UE ,ess"e
R'B ssi"n,ent re.
RB setu+
RB setu+ co,+ R'B ssi"n,ent res+
D((lertin")
D((connect)
D((connect ck)
UE NodeB RNC 8SC
D((C8 ser!ice cce+t)
DC#C%&-U+link S6NC
DC#C%&-Downlink S6NC
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N +1
CS Call Ori:ination 0lo8
+RRC Setu4 on %C!-
FI #UR$ )2 CS CA'' %RI #I NATI %N F'%W 4 RRC S$TUP %N DC(5

RRC connection re..
R) setu+ re.
R) setu+ res+.
')C'& ES(. re.
')C'& ES(. c5n
RRC connection setu+
RRC connection setu+ co,+.
INI(I') D((C8 ser!ice re.)
D((setu+)
D((cll +roceedin")
Initil UE ,ess"e
R'B ssi"n,ent re. R) recon5i" +re
R) recon5i" redy
')C'& ES(. re.
')C'& ES(. c5n
R) recon5i" co,,it
RB setu+
D((lertin")
D((connect)
D((connect ck)
UE NodeB RNC 8SC
')C'& ES(. re.
')C'& ES(. c5n
D((C8 ser!ice cce+t)
DC#C%&-U+link S6NC
DC#C%&-Downlink S6NC
+) Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
CS Call Ter6ination 0lo8
FI #UR$ )1 CS CA'' T$RMI NATI %N F'%W 4 RRC S$TUP %N DC(5

RRC connection re..
R) setu+ re.
R) setu+ res+.
')C'& ES(. re.
')C'& ES(. c5n
RRC connection setu+
INI(I') D((&"in" res+)
D((setu+)
D((cll con5ir,ed)
Initil UE ,ess"e
R'B ssi"n,ent re. R) recon5i" +re
R) recon5i" redy
')C'& ES(. re.
')C'& ES(. c5n
R) recon5i" co,,it
RB setu+
D((lertin")
D((connect)
D((connect ck)
&"in" ty+e* +"in"
UE B NodeB RNC 8SC
')C'& ES(. re.
')C'& ES(. c5n
DC#C%&U) S6NC
DC#C%&D) S6NC
RRC connection setu+ co,+.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N +*
Release 0lo8 in CS %o6ain
CN Ori:inates
FI #UR$ )) R$'$AS$ F'%W I N CS D%MAI N CN I NI TI AT$S

D((relese)
D((Relese co,+)
RRC connection relese
RRC connection relese co,+
IU relese co,,nd
IU relese co,+
R) delete
R) delete res+
')C'& RE). re.
')C'& RE). c5n
U# NodeB RNC M"C
')C'& ES(. re.
')C'& ES(. c5n
D((disconnection)
++ Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
Release 0lo8 in CS %o6ain
2E Ori:inates
FI #UR$ )* R$'$AS$ F'%W I N CS D%MAI N U$ I NI TI AT$S

D((relese)
D((Relese co,+)
RRC connection relese
RRC connection relese co,+
IU relese co,,nd
IU relese co,+
R) delet e
R) delet e res+
')C'& RE). re.
')C'& RE). c5n
U# NodeB RNC M"C
')C'& ES(. re.
')C'& ES(. c5n
D((disconnect ion)
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N +,

3 Interface Protocol and Signaling Flow 49

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

3 Interface Protocol and Signaling Flow 49

Transféré par

Droits d'auteur :

Formats disponibles

Interface Protocol and

Vous aimerez peut-être aussi