3 Interface Protocol and Signaling Flow 49
-
Upload
sushil-ojha -
Category
Documents
-
view
231 -
download
0
Transcript of 3 Interface Protocol and Signaling Flow 49
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
1/48
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
2/48
Interface Protocol and
Signaling Flow
Version 3.00
ZTE CORPORATIONZTE Plaza, Keji Road Sout,!i"Te# Industrial Par$,Nansan %istri#t, Senzen,P. R. Cina&'(0&)Tel* +(- )&& ))'/00 (00"/(30"/(30a1* +(- )&& ))32R* tt4*55su44ort.zte.#o6.#nE"6ail* do#7zte.#o6.#n
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
3/48
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
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
4/48
/C0 rame Protocol o+ *nter+ace *ur.......................................32
RNSAP Process....................................................................32
Protocol Related to *nter+ace *u......................................3-Node o)ic odel..............................................................3,
NAP 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..........................-,
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
5/48
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
6/48
*nside UTRAN9 the inter+ace et&een RNCs is *nter+ace *ur.
*n addition9 the inter+ace et&een UTRAN and UE is *nter+aceUu.
E14lanation Related to RNSRNS 5Radio Net&or( Sus!stem6; The )eneral name +or oneRNC and all Nodes it mana)es.
SRNC 5Ser%in) RNC6; The RNS connectin) &ith CN is calledSRNS and the RNC o+ RNS is called SRNC.
DRNC 5/ri+t RNC6; *n the case o+ so+t hando%er o+ C/A9 UEcan use se%eral RNSs. i)ure 2sho&s the relation o+ SRNS and
/RNS.
F I # U R $ ) SRNS AND DRNS
SRNS
Core Network
Iu
DRNSIur
UE
Cells
Se%eral lin(s can exist inside one UE at the same time. The userdata to access /RNS is sent to SRNS +rom /RNS %ia *nter+ace*ur. /RNC &on
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
7/48
Chapter 1 C/A UTRAN S!stem Archetecture
2TRAN Co66on Proto#ol
6odeli)ure 3sho&s the )eneral protocol model +or UTRAN *nter+aces9and descried in detail in the +ollo&in) suclauses. The structureis ased on the principle that the la!ers and planes are lo)icall!independent o+ each other. There+ore9 as and &hen re=uired9 thestandardisation od! can easil! alter protocol stac(s and planesto +it +uture re=uirements.
F I # U R $ * UTRAN C % M M % N PR% T % C% ' M% D$ '
A44li#ationProto#ol
%ataStrea6+s-
ACAP+s-
Trans4ortNet8or$
a9er
P9si#al a9er
Si:nallin:;earer+s-
Trans4ort2ser
Net8or$Plane
Control Plane 2ser Plane
Trans4ort2ser
Net8or$Plane
Trans4ort Net8or$Control Plane
Radio
Net8or$a9er
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 UTRANrelated issues are %isile onl! in the Radio Net&or( a!er9 and
the Transport Net&or( a!er represents standard transporttechnolo)! that is selected to e used +or UTRAN9 ut &ithoutan! 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 NAP9 and the Si)nallin) earer +or
transportin) the Application Protocol messa)es.
Amon) other thin)s9 the Application Protocol is used +or
settin) up earers +or 5i.e. Radio Access earer or Radioin(6 in the Radio Net&or( a!er. *n the three plane
structure the earer parameters in the Application Protocolare not directl! tied to the User Plane technolo)!9 ut arerather )eneral earer parameters.
The Si)nallin) earer +or the Application Protocol ma! or
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N *
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
8/48
*nter+ace Protocol and Si)nalin) lo&
ma! not e o+ the same t!pe as the Si)nallin) Protocol +orthe ACAP. The Si)nallin) earer is al&a!s set up ! $@actions.
User plane
The User Plane *ncludes the /ata Stream5s6 and the /ataearer5s6 +or the /ata Stream5s6. The /ata Stream5s6 isarecharacterised ! 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 isareneeded to set up the transport earers 5/ata earer6 +or the
User Plane. *t also includes the appropriate Si)nallin)
earer5s6 needed +or the ACAP protocol5s6.The Transport Net&or( Control Plane is a plane that actset&een the Control Plane and the User Plane. The
introduction o+ Transport Net&or( Control Plane ma(es itpossile +or the Application Protocol in the Radio Net&or(Control Plane to e completel! independent o+ thetechnolo)! selected +or /ata earer in the User Plane.
hen Transport Net&or( Control Plane is used9 the transportearers +or the /ata earer in the User Plane are set up in
the +ollo&in) +ashion. irst there is a si)nallin) transaction !the Application Protocol in the Control Plane9 &hich tri))ersthe set up o+ the /ata earer ! the ACAP protocol that isspeci+ic +or the User Plane technolo)!.
The independence o+ Control Plane and User Plane assumesthat ACAP si)nallin) transaction ta(es place. *t should e
noted that ACAP mi)ht not e used +or all t!pes /ataearers. *+ there is no ACAP si)nallin) transaction9 theTransport Net&or( Control Plane is not needed at all. This isthe case &hen pre"con+i)ured /ata earers are used.
*t should also e noted that the ACAP protocol5s6 in theTransport Net&or( Control Plane isare not used +or settin)
up the Si)nallin) earer +or the Application Protocol or +orthe ACAP durin) real time operation.
The Si)nallin) earer +or the ACAP ma! or ma! not e o+the same t!pe as the Si)nallin) earer +or the Application
Protocol. The Si)nallin) earer +or ACAP is al&a!s set up !$@ actions.
TN user plane
The /ata earer5s6 in the User Plane9 and the Si)nallin)earer5s6 +or Application Protocol9 elon) also to TransportNet&or( User Plane. As descried in the pre%ious suclause9the /ata earers in Transport Net&or( User Plane aredirectl! controlled ! Transport Net&or( Control Plane durin)
real time operation9 ut the control actions re=uired +or
+ Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
9/48
Chapter 1 C/A UTRAN S!stem Archetecture
settin) up the Si)nallin) earer5s6 +or Application Protocolare considered $@ actions.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N ,
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
10/48
C h a p t e r )
WCDMA Interface(ierarch
Hi&h%i&hts' 8rasp the concepts o+ UTRAN control plane and user plane
Bno& aout the protocols o+ UTRAN control plane
8rasp the concepts o+ access la!er and non"access la!er
Control Plane and 2serPlanePurpose o+ the control plane;
Control the radio access earer and the connection et&een UEand the net&or(
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 *u; NAP
*nter+ace ;Uu; RRC protocol
The user plane data and control plane data o+ all RN elon) toTN user plane. TN control plane protocol is ACAP9 elon)in)
to SAA 5Si)nallin) AA6 o+ AT.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N -
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
11/48
A##ess a9er and Non"
a##ess a9erThe concepts o+ access la!er and non"access la!er are related tothe communication o+ UE and CN. The access la!er ears theupper la!er ser%ices %ia the SAP 5Ser%ice Access Point69 assho&n in i)ure -
F I # U R $ + A CC$ S S ' A. $ R AN D N% N / ACC$ S S ' A. $ R
2TRAN2E CN
A##ess Stratu6
Non"A##ess Stratu6
Radio+2u-
Iu
Radio4roto"#ols+'-
Radio4roto"#ols+'-
Iu4roto#ols
(2)
Iu4roto#ols
(2)
Example +or non"access la!er;*n AR %oice telephone 5the callin) part!69 there are se%eral UE"CN si)nalin)9 &hich are the control plane si)nalin) o+ non"accessla!er. These si)nalin) are encapsulated in RRC protocol +irst and
then transmitted to RNC transparentl!. RNC decodes thesesi)nalin) out o+ RRC messa)es9 encapsulates into RANAP9 and
then transmits to CN transparentl! %ia RANAP.
UERNC C Ser%ice Re=uest
RNCUE Authentication Re=uest
UERNC Authentication Response
RNCUE C Ser%ice Accept
UERNC SETUP
RNCUE Call Processin)
RNCUE Alertin)
RNCUE Connect
UERNC Connect Ac(no&led)e
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N 0
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
12/48
C h 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
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
13/48
F I # U R $ , RRC C % NN$ CT I % N S$ T UP
5. Downlink Synchronistion
UE Node B
Serving RNSSer!in"
RNC
DC#$%&DC#$%&
'llocte RNI
Select * nd 2
+r,eters
RRCRRC*. CCCH- RRC Connection Reuest
NB'&NB'&/. Rdio ink Setu+ Res+onse
NB'&NB'&
2. Rdio ink Setu+ Reuest
RRCRRC0. CCCH- RRC Connection Setu+
Strt R1
Strt 1
. 'C'& Iub Dt rns+ort Berer Setu+
RRCRRC3.DCCH- RRC Connection Setu+ Co,+lete
DC#$%&DC#$%&4. U+link Synchronistion
/etailed descriptions;
At the e)innin)9 UE does not ha%e dedicated channel resources9so it sends the messa)e o+ RRC connection setup on CCC05RAC06.
RNC allocates RNT* and a%ailale resources to UE9 decides toallocate /C0 to UE9 and in+orm Node to allocate /C0 to UE
&ith NAP messa)e o+ DRadio in( Setup Re=uest.
Node allocates resources to UE9 starts to recei%e9 and returnsDRadio in( Setup Response to RNC.
At this time9 there are no resources o+ the transmission net&or(
on *nter+ace *u9 so ACAP o+ SRNC sends the messa)e o+ ERF5Estalish Re=uest6. This messa)e contains AA2 indin) */.
This */ can help Node to ind the data transmission earer on*nter+ace *u and /C09 and sends the messa)e o+ EC 5EstalishCon+irm6 ac( to RNC.
Node and SRNC per+orm the +rame s!nchroni>ation %ia
D/o&nlin( S!nchroni>ation and DUplin(. S!nchroni>ation in/C0 +rame protocol9 and then to per+orm the / transmission.
Althou)h /C0 resources on *nter+ace *u are read!9 UE does not(no& it. There+ore9 SRNC sends the messa)e o+ DRRC
Connection Setup to UE on CCC0 5AC069 and in+orms UE o+related parameters.
Accordin) to related parameters in DRRC Connection Setup9 UE
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N 12
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
14/48
Chapter 3 *nter+ace and Protocol
con+i)ures the ph!sical la!er. Node sets up /C0 success+ull!and sends the messa)e o+ DRRC Connection Setup Completeac( to SRNC on /C0.
Net8or$ Re:istration Pro#ess
i)ure Gsho&s the +lo& o+ UE re)istration +or CS domain.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N 11
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
15/48
*nter+ace Protocol and Si)nalin) lo&
F I # U R $ 3 U$ '% CAT I % N UP DAT $
/etailed descriptions;
A+ter RRC connection sets up9 UE estalishes /C0. UE needs to
1) Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
16/48
Chapter 3 *nter+ace and Protocol
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+erto H3I69 that is9 to initiate the ocation Update. This messa)e isencapsulated in the RRC messa)e o+ *nitial /irect Trans+er9
&hich is sent to RNC ! UE.RRC o+ RNC recei%es the messa)e o+ *nitial /irect Trans+er9decodes the hi)h"la!er messa)es +rom it9 and sends to RANAPentit!. RANAP entit! &ill encapsulate the messa)e o+ DocationUpdate into *nitial UE essa)e and sends it to CN throu)h SCCPentit!. At this time9 there is no si)nalin) connection et&eenRNC and CN9 so the messa)e o+ D*nitial UE essa)e o+ RANAP is
encapsulated into SCCP connection setup massa)e 5CR6 andsent 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 RANAPentit!. RANAP entit! decodes the messa)e o+ Docation Update
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 Update +rom UE9 CNinitiates the authentication. The si)nallin) durin) the
authentication process is transmitted transparentl!. RNC andNode onl! trans+er et&een UE and CN9 ut do not process
messa)es. essa)es o+ DAuthentication Re=uest andDAuthentication Response are NAS messa)es9 too. The! are
encapsulated into the messa)e o+ D/irect Trans+er o+ RANAPand RRC.
A+ter the authentication chec( on UE is passed9 CN initiates thesecurit! mode process. *t is to encr!pt and protect the data and
si)nalin) o+ the air inter+ace. essa)es o+ securit! mode are nottransmitted transparentl! and it needs RNC processin).
A+ter the authentication chec( is passed and the securit! modeis initiated9 CN sends the messa)e o+ Docation Update Accept
to UE9 in+ormin) that UE re)istration succeeds. This messa)e istransmitted transparentl!.
Conne#tion Release Pro#ess
i)ure 7sho&s the connection release process.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N 1*
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
17/48
*nter+ace Protocol and Si)nalin) lo&
F I # U R $ - RRC C % NN$ CT I % N R $ ' $ AS $
/etailed descriptions;
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 ac( to RNC.RNC in+orms Node to delete R and a+ter deletin) R9 Node
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)eo+ SCCP release con+irmation.
RNC initiates to release the transmission resources on *nter+ace*u.
1+ Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
18/48
Chapter 3 *nter+ace and Protocol
Proto#ol Related to Inter=a#e
2u2u Inter=a#e 4roto#ol ar#ite#ture
i)ure #sho&s the architecture o+ Uu *nter+ace protocol.
F I # U R $ 0 ST RUCT UR$ % F RRC PR% T % C% '
L3
o"icl
Chnnels
rns+ort
Chnnels
C$+lne si"nllin" U$+lne inor,tion
L2/MAC
L1
RC
DCNt7C
L2/RLC
8'C
RC
RCRC
RC
RCRC
RC
Du+liction !oidnce
UuS boundry
B8C L2/BMC
control
&DC&&DC& L2/PDCP
DCNt7C
Rdio
Berers
RRC
The Uu inter+ace is la!ered into three protocol la!ers;
the ph!sical la!er 516
the data lin( la!er 526
net&or( la!er 536.
a!er 2 is split into +ollo&in) sula!ers; edium Access Control5AC69 Radio in( Control 5RC69 Pac(et /ata Con%er)enceProtocol 5P/CP6 and roadcastulticast Control 5C6. 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,
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
19/48
*nter+ace Protocol and Si)nalin) lo&
P/CP and C exist in the U"plane onl!.
*n the C"plane9 a!er 3 is partitioned into sula!ers &here thelo&est sula!er9 denoted as Radio Resource Control 5RRC69
inter+aces &ith la!er 2 and terminates in the UTRAN. The next
sula!er pro%ides J/uplication a%oidanceJ +unctionalit!. *tterminates in the CN ut is part o+ the Access Stratum itpro%ides the Access Stratum Ser%ices to hi)her la!ers. Thehi)her la!er si)nallin) such as oilit! ana)ement 56 andCall Control 5CC6 is assumed to elon) to the non"accessstratum..
The +unctions o+ RC;
The RC sula!er pro%ides ARF +unctionalit! closel! coupled &iththe radio transmission techni=ue used. There is no di++erence
et&een RC instances in C and U planes.The UTRAN can ere=uested ! 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 asicre=uirement to e +ul+illed ! the UTRAN retransmission+unctionalit! as pro%ided ! the RC sula!er.0o&e%er9 in caseo+ the *u connection point is chan)ed 5e.). SRNS relocation9streamlinin)69 the pre%ention o+ the loss o+ data ma! not e
)uaranteed autonomousl! ! the UTRAN ut relies onJ/uplication a%oidanceJ +unctions in the CN.There are primaril!
t&o (inds o+ si)nallin) messa)es transported o%er the radiointer+ace " RRC )enerated si)nallin) messa)es and NAS
messa)es )enerated in the hi)her la!ers. $n estalishment o+the si)nallin) connection et&een the peer RRC entities three or
+our UA si)nallin) radio earers ma! e set up. T&o o+ theseearers are set up +or transport o+ RRC )enerated si)nallin)messa)es " one +or trans+errin) messa)es throu)h anunac(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+ AC include;
Mappin& (et)een %$&ica% channe%s an" transp$rtchanne%s. The AC is responsile +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 Comination Set assi)ned! RRC9 AC selects the appropriate transport +ormat &ithinan 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+. henselectin) et&een the Transport ormat Cominations in the
)i%en Transport ormat Comination Set9 priorities o+ thedata +lo&s to e mapped onto the correspondin) Transport
Channels can e ta(en into account. Priorities are e.). )i%en! attriutes o+ Radio earer ser%ices and RC u++er status.The priorit! handlin) is achie%ed ! selectin) a Transport
ormat Comination +or &hich hi)h priorit! data is mapped
13 Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
20/48
Chapter 3 *nter+ace and Protocol
onto 1 &ith a Khi)h it rateK Transport ormat9 at the sametime lettin) lo&er priorit! data e mapped &ith a Klo& itrateK 5could e >ero it 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 resourcese++icientl! +or urst! trans+er9 a d!namic schedulin) +unctionma! e applied. AC realises priorit! handlin) on commonand shared transport channels. Note that +or dedicatedtransport 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 sula!er.
"entificati$n $f U+s $n c$mm$n transp$rt channe%s.hen a particular UE is addressed on a common do&nlin(
channel9 or &hen a UE is usin) the RAC09 there is a need +orinand identi+ication o+ the UE. Since the AC la!er handles
the access to9 and multiplexin) onto9 the transport channels9the identi+ication +unctionalit! is naturall! also placed in AC.
ultiplexin)demultiplexin) o+ upper la!er P/Us into+romtransport loc(s deli%ered to+rom the ph!sical la!er on
common transport channels. AC should support ser%icemultiplexin) +or common transport channels9 since the
ph!sical la!er does not support multiplexin) o+ thesechannels.
ultiplexin)demultiplexin) o+ upper la!er P/Us into+romtransport loc( sets deli%ered to+rom the ph!sical la!er on
dedicated transport channels. The AC allo&s ser%icemultiplexin) +or dedicated transport channels. This +unction
can e utilised &hen se%eral upper la!er ser%ices 5e.). RCinstances6 can e mapped e++icientl! on the same transportchannel. *n this case the identi+ication o+ multiplexin) iscontained in the AC protocol control in+ormation.
Traffic ,$%ume measurement. easurement o+ tra++ic%olume on lo)ical channels and reportin) to RRC. ased on
the reported tra++ic %olume in+ormation9 RRC per+ormstransport channel s&itchin) decisions.
Transp$rt Channe% type s)itchin&. Execution o+ the
s&itchin) et&een common and dedicated transportchannels ased on a s&itchin) decision deri%ed ! RRC.
Cipherin&. This +unction pre%ents unauthorised ac=uisitiono+ data. Cipherin) is per+ormed in the AC la!er +ortransparent RC mode.
Access Ser,ice C%ass se%ecti$n f$r RACH an" C#CHtransmissi$n. The RAC0 resources 5i.e. access slots andpreamle si)natures6 and CPC0 resources 5i.e. access slotsand preamle si)natures6 ma! e di%ided et&een di++erentAccess Ser%ice Classes in order to pro%ide di++erent prioritieso+ RAC0 and CPC0 usa)e. *n addition it is possile +or more
than one ASC or +or all ASCs to e assi)ned to the same
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N 1-
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
21/48
*nter+ace Protocol and Si)nalin) lo&
access slotsi)nature space. Each access ser%ice class &illalso ha%e a set o+ ac("o++ parameters associated &ith it9some or all o+ &hich ma! e roadcast ! the net&or(. TheAC +unction applies the appropriate ac("o++ and indicates
to the P0L la!er the RAC0 and CPC0 partition associated toa )i%en AC P/U trans+er.
The +unctions o+ P/CP include;
Hea"er c$mpressi$n an" "ec$mpressi$n. 0eadercompression and decompression o+ *P data streams 5e.).9
TCP*P and RTPU/P*P headers6 at the transmittin) andrecei%in) entit!9 respecti%el!. The header compressionmethod is speci+ic to the particular net&or( la!er9 transportla!er or upper la!er protocol cominations e.). TCP*P andRTPU/P*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 itto the RC la!er and %ice %ersa.
Supp$rt f$r %$ss%ess SRNS re%$cati$n. aintenance o+P/CP se=uence numers +or radio earers that are
con+i)ured to support lossless SRNS relocation.
The +unctions o+ C include;
St$ra&e $f Ce%% -r$a"cast Messa&es.The C stores the Cell roadcast messa)es recei%ed o%erthe CC"RNC inter+ace +or scheduled transmission.
Traffic ,$%ume m$nit$rin& an" ra"i$ res$urce reuest
f$r C-S.At the UTRAN side9 the C calculates the re=uiredtransmission rate +or Cell roadcast Ser%ice ased on themessa)es recei%ed o%er the CC"RNC inter+ace9 and re=uests+or appropriate CTC0AC0 resources +rom RRC.
Sche"u%in& $f -MC messa&es.
The C recei%es schedulin) in+ormation to)ether &ith eachCell roadcast messa)e o%er the CC"RNC"inter+ace. asedon this schedulin) in+ormation9 at the UTRAN side9 C)enerates schedule messa)es and schedules C messa)ese=uences accordin)l!. At the UE side9 C e%aluates theschedule messa)es and indicates schedulin) parameters to
RRC9 &hich are used ! RRC to con+i)ure the lo&er la!ers +orCS discontinuous reception.
Transmissi$n $f -MC messa&es t$ U+.This +unction transmits the C messa)es 5Schedulin) andCell roadcast 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 roadcast messa)esto upper la!er 5NAS6 in the UE. $nl! non"corrupted Cellroadcast messa)es are deli%ered.
The +unctions o+ RRC include;
10 Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
22/48
Chapter 3 *nter+ace and Protocol
The Radio Resource Control 5RRC6 la!er handles the controlplane si)nallin) o+ a!er 3 et&een the UEs and UTRAN. TheRRC per+orms the +ollo&in) +unctions;
-r$a"cast $f inf$rmati$n pr$,i"e" (y the n$naccess
stratum /C$re Net)$r0.The RRC la!er per+orms s!stemin+ormation roadcastin) +rom the net&or( to all UEs. Thes!stem in+ormation is normall! repeated on a re)ular asis.The RRC la!er per+orms the schedulin)9 se)mentation andrepetition. This +unction supports roadcast o+ hi)her la!er5ao%e RRC6 in+ormation. This in+ormation ma! e cellspeci+ic or not. As an example RRC ma! roadcast Core
Net&or( location ser%ice area in+ormation related to somespeci+ic cells.
-r$a"cast $f inf$rmati$n re%ate" t$ the accessstratum. The RRC la!er per+orms s!stem in+ormation
roadcastin) +rom the net&or( to all UEs. The s!stemin+ormation is normall! repeated on a re)ular asis. The RRC
la!er per+orms the schedulin)9 se)mentation and repetition.This +unction supports roadcast o+ t!picall! cell"speci+ic
in+ormation.
+sta(%ishment3 reesta(%ishment3 maintenance an"
re%ease $f an RRC c$nnecti$n (et)een the U+ an"UTRAN.The estalishment o+ an RRC connection is initiated
! a re=uest +rom hi)her la!ers at the UE side to estalishthe +irst Si)nallin) Connection +or the UE. The estalishment
o+ an RRC connection includes an optional cell re"selection9an admission control9 and a la!er 2 si)nallin) lin(
estalishment. The release o+ an RRC connection can einitiated ! a re=uest +rom hi)her la!ers to release the lastSi)nallin) Connection +or the UE or ! the RRC la!er itsel+ incase o+ RRC connection +ailure. *n case o+ connection loss9
the UE re=uests re"estalishment o+ the RRC connection. *ncase 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!ers9per+orm the estalishment9 recon+i)uration and release o+
Radio earers in the user plane. A numer o+ Radio earerscan e estalished to an UE at the same time. At
estalishment and recon+i)uration9 the RRC la!er per+ormsadmission control and selects parameters descriin) the
Radio earer processin) in la!er 2 and la!er 19 ased onin+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 CPC0channels6 needed +or the RRC connection includin) needs+rom oth the control and user plane. The RRC la!er ma!recon+i)ure radio resources durin) an estalished RRCconnection. This +unction includes coordination o+ the radioresource allocation et&een multiple radio earers related to
the same RRC connection. RRC controls the radio resources
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N 1
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
23/48
*nter+ace Protocol and Si)nalin) lo&
in the uplin( and do&nlin( such that UE and UTRAN cancommunicate usin) unalanced radio resources 5as!mmetricuplin( and do&nlin(6. RRC si)nals to the UE to indicateresource allocations +or purposes o+ hando%er to 8S 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 RRCconnection moilit! durin) an estalished RRC connection9such as hando%er9 preparation o+ hando%er to 8S or others!stems9 cell re"selection and cellpa)in) area updateprocedures9 ased on e.). measurements done ! the UE.
#a&in&4n$tificati$n.The RRC la!er can roadcast pa)in)in+ormation +rom the net&or( to selected UEs. 0i)her la!erson the net&or( side can re=uest pa)in) and noti+ication. TheRRC la!er can also initiate pa)in) durin) an estalished RRC
connection.
R$utin& $f hi&her %ayer #DUs.This +unction per+orms atthe UE side routin) o+ hi)her la!er P/Us to the correct hi)herla!er entit!9 at the UTRAN side to the correct RANAP entit!.
C$ntr$% $f reueste" 5$S. This +unction shall ensure thatthe FoS re=uested +or the Radio earers can e met. Thisincludes the allocation o+ a su++icient numer o+ radioresources.
U+ measurement rep$rtin& an" c$ntr$% $f therep$rtin&. The measurements per+ormed ! the UE are
controlled ! the RRC la!er9 in terms o+ &hat to measure9
&hen to measure and ho& to report9 includin) oth UTS airinter+ace and other s!stems. The RRC la!er also per+ormsthe reportin) o+ the measurements +rom the UE to thenet&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) 5ono++6 et&een the UE and UTRAN.
Ar(itrati$n $f ra"i$ res$urces $n up%in DCH. This+unction controls the allocation o+ radio resources on uplin(/C0 on a +ast asis9 usin) a roadcast channel to send
control in+ormation to all in%ol%ed users.This +unction isimplemented in the CRNC.
Initia% ce%% se%ecti$n an" rese%ecti$n in i"%e m$"e.Selection o+ the most suitale cell ased on idle modemeasurements and cell selection criteria.
Inte&rity pr$tecti$n. This +unction adds a essa)eAuthentication Code 5AC"*6 to those RRC messa)es that areconsidered sensiti%e andor contain sensiti%e in+ormation.
Initia% C$nfi&urati$n f$r C-SThis +unction per+orms the initial con+i)uration o+ the C
sula!er.
)2 Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
24/48
Chapter 3 *nter+ace and Protocol
A%%$cati$n $f ra"i$ res$urces f$r C-SThis +unction allocates radio resources +or CS ased ontra++ic %olume re=uirements indicated ! C. The radioresource allocation set ! RRC 5i.e. the schedule +or mappin)
o+ CTC0 onto AC0S"CCPC06 is indicated to C to enale)eneration o+ schedule messa)es. The resource allocation +orCS shall e roadcast as s!stem in+ormation.
C$nfi&urati$n f$r C-S "isc$ntinu$us recepti$nThis +unction con+i)ures the lo&er la!ers 519 26 o+ the UE&hen it shall listen to the resources allocated +or CS asedon schedulin) in+ormation recei%ed +rom C.
Status o= RRC Proto#ol
*n C/A9 all statuses o+ UE are scheduled ! 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) 8Sstatus6.
F I # U R $ RRC ST A T U S AN D ST AT US C% N& $ RS I % N
Esta>lis RRC
Conne#tion
Release RRC
Conne#tion
2TRA RRC Conne#ted ?ode
2TRA*Inter"RAT!ando
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
25/48
*nter+ace Protocol and Si)nalin) lo&
locates in.
CEMPC0 status indicates that UE onl! intercepts PC0 and C0.*n this status9 UE can reselect the cell. /urin) the reselection9 it
con%erts into CEMAC0 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 radioresources.
So6e E14lanations
*n CEMPC09 URAMPC0 or *dle status9 UE can intercept PC0 andC09 and can recei%e the messa)e o+ Pa)in). *n CEM/C0 orCEMAC0 status9 UE cannot intercept PC0 and C0. 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 *S*6 &illnot e sa%ed in RNC. hen UE is ma(in) a call9 CN in+orms RNC
o+ the *S* o+ the UE &ith the messa)e o+ Command */ o+RANAP. hen CN re=uires RNC to pa)e a speci+ic UE9 RNC &ill
ud)e &hich RRC status the *S* to pa)e is in9 to decide thepa)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
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
26/48
Chapter 3 *nter+ace and Protocol
Proto#ol related to Inter=a#e
IuI2 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:
BCDoa!n
C"Doa!n
P"Doa!n
9Iu$&S:
RNC
The *uinter+ace is speci+ied at the oundar! et&een the Core
Net&or( and UTRAN. i)ure depicts the lo)ical di%ision o+ the *uinter+ace. rom the *u perspecti%e9 the UTRAN access point is anRNC. The *u inter+ace to&ards the PS"domain o+ the corenet&or( is called *u"PS9 and the *u inter+ace to&ards the CS"domain is called *u"CS. The di++erences et&een *u"CS and *u"PS are treated else&here in the present document. The *uinter+ace to the roadcast domain is called *u"C.
There shall not e more than one *u inter+ace 5*u"PS6 to&ardsthe 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 ut ma! also ha%e +urther *u inter+aces5*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+aces5*u"CS6 shall onl! e used as a result o+ intra"SC inter"s!stem
hando%er or SRNS relocation9 in the case the anchor CN nodedirectl! connects to the tar)et RNC. There shall not e more
than one *u inter+ace 5*u"C6 +rom an RNC to&ards theroadcast domain.
*n the separated core net&or( architecture9 this means thatthere shall e separate si)nallin) and user data connections
to&ards the PS and CS domains O this applies in oth transport
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N )*
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
27/48
*nter+ace Protocol and Si)nalin) lo&
and radio net&or( la!ers.
*n the comined architecture9 there shall e separateconnections in the user plane to&ards the PS and CS domains
5in oth transport and radio net&or( la!ers6. *n the control
plane9 there shall e separate SCCP connections to the t&olo)ical domains.
*n either architecture9 there can e se%eral RNCs &ithin UTRAN
and so UTRAN ma! ha%e se%eral *uaccess points to&ards theCore Net&or(. As a minimum9 each *u access point 5in UTRAN or
CN6 shall independentl! +ul+il the re=uirements o+ the rele%ant *uspeci+ications
Proto#ol Stru#ture o= Iu Inter=a#e
i)ure 14sho&s the structure o+ *nter+ace *u"CS protocol andi)ure 11sho&s the structure o+ *nter+ace *u"PS protocol.
F I # U R $ 12 ST RUCT UR$ % F I U /CS PR% T % C% '
;.2*5
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
28/48
Chapter 3 *nter+ace and Protocol
F I # U R $ 11 ST RUCT UR$ % F I NT $ RF AC$ IU /PS P R% 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
&lnerns+ort Network
Control &lne
Rdio
Network
yer
'8
''5
I&
UD&
7&$U
&hysicl yer
'8
RANA#; user plane application protocol. *t pro%ides thesi)nallin) ser%ice et&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 enales to chan)e the
ser%in) RNC +unctionalit! as &ell as the related *u resources5RA5s6 and Si)nallin) connection6 +rom one RNC to another.
$%erall RA mana)ement. This +unction is responsile +orsettin) up9 modi+!in) and releasin) RAs.
Fueuin) the setup o+ RA. The purpose o+ this +unction is toallo& placin) some re=uested RAs into a =ueue9 andindicate the peer entit! aout the =ueuin).
Re=uestin) RA release. hile the o%erall RA mana)ementis a +unction o+ the CN9 the RNC has the capailit! to re=uestthe release o+ RA.
Release o+ all *u connection resources. This +unction is usedto explicitl! release all resources related to one *u
connection.
Re=uestin) the release o+ all *u connection resources. hile
the *u release is mana)ed +rom the CN9 the RNC has thecapailit! 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 ),
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
29/48
*nter+ace Protocol and Si)nalin) lo&
SRNS context +or&ardin) +unction. This +unction isresponsile +or trans+errin) SRNS context +rom the RNC tothe 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
adustin) the load in the *u inter+ace.
Resettin) the *u. This +unction is used +or resettin) an *uinter+ace.
Sendin) the UE Common */ 5permanent NAS UE identit!6 tothe RNC. This +unction ma(es the RNC a&are o+ the UEJsCommon */.
Pa)in) the user. This +unction pro%ides the CN +or capailit!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! estalished trace.
Transport o+ NAS in+ormation et&een UE and CN 5see H#I6.This +unction has t&o su"classes;
1. Transport o+ the initial NAS si)nallin) messa)e +rom the UEto CN. This +unction trans+ers transparentl! the NASin+ormation. As a conse=uence also the *u si)nallin)connection is set up.
2. Transport o+ NAS si)nallin) messa)es et&een UE and CN9This +unction trans+ers transparentl! the NAS si)nallin)messa)es on the existin) *u si)nallin) connection. *t alsoincludes a speci+ic ser%ice to handle si)nallin) messa)es
di++erentl!.
Controllin) the securit! mode in the UTRAN. This +unction isused to send the securit! (e!s 5cipherin) and inte)rit!protection6 to the UTRAN9 and settin) the operation mode +orsecurit! +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) theactual location in+ormation +rom RNC to the CN.
/ata %olume reportin) +unction. This +unction is responsile+or reportin) unsuccess+ull! transmitted / data %olume o%erUTRAN +or speci+ic RAs.
Reportin) )eneral error situations. This +unction allo&sreportin) o+ )eneral error situations9 +or &hich +unctionspeci+ic error messa)es ha%e not een de+ined.
ocation related data. This +unction allo&s the CN to eitherretrie%e +rom the RNC decipherin) (e!s 5to e +or&arded to
the UE6 +or the roadcasted assistance data9 or re=uest theRNC to deli%er dedicated assistance data to the UE.
)3 Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
30/48
Chapter 3 *nter+ace and Protocol
SCC#; The SCCP is used to support si)nallin) messa)eset&een the CNs and the RNC. $ne user +unction o+ the SCCP9called Radio Access Net&or( Application Part 5RANAP69 isde+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! useSSN9 SPC andor 8T and an! comination o+ them as addressin)schemes +or the SCCP. hich o+ the a%ailale addressin)
scheme to use +or the SCCP is an operator matter. A ne& SCCPconnection is estalished &hen in+ormation related to thecommunication et&een a UE and the net&or( has to eexchan)ed et&een RNC and CN9 and no SCCP connection existset&een the CN and the RNC in%ol%ed9 +or the concerned UE.
MT#-' pro%ides messa)e routin)9 discrimination and
distriution 5+or point"to"point lin( onl!69 si)nalin) lin(mana)ement load sharin) and chan)eo%erac( et&een lin(&ithin one lin("set. The need +or multiple lin("sets is precluded.
SAANNI'SAA"NN* H1I consists o+ the +ollo&in) su"la!ers; "
SSC H3I9 " SSC$P H2I and O AA, HGI. The SSC maps there=uirements o+ the la!er ao%e to the re=uirements o+ SSC$P.
Also SAA connection mana)ement9 lin( status and remoteprocessor status mechanisms are pro%ided. SSC$P pro%idesmechanisms +or the estalishment and release o+ connectionsand the reliale exchan)e o+ si)nallin) in+ormation et&eensi)nallin) entities. Adapts the upper la!er protocol to there=uirements o+ the o&er AT cells.
*UUP; user plane protocol.
8T#U'8TP"U is used as the user data earer to&ards the PS
domain.RANAP Si)nallin) is used to estalish9 modi+! andrelease the 8TP"U tunnels to&ards the PS domain.
AA2'AA2 is used as the user data earer to&ards the CSdomain.F.2G34.2 is used as the protocol +or d!namicall! setupAA"2 connections o%er *u to&ards the CS domain. F.2G34.2adds ne& optional capailities 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 )-
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
31/48
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
32/48
Chapter 3 *nter+ace and Protocol
SRNC relocation9 SRNC 5Ser%in) RNC6 is also called Source RNCand /RNC is also called Tar)et RNC. i)ure 1-sho&s the resulta+ter the relocation completes.
F I # U R $ 1+ SRNS R $ ' % CAT I % N 4 I I I 5
SRNS relocation is the process to mo%e *nter+ace *u +rom SourceRNC to Tar)et RNC.
RANAP Pro#ess
TA6' $ 1 C' AS S 1
+%ementary#r$ce"ure
Initiatin&Messa&e
Successfu%6utc$me
Unsuccessfu%6utc$me
Responsemessa)e
Response messa)e
*u Release *UREEASEC$AN/
*U REEASEC$PETE
RelocationPreparation
RE$CAT*$NREFU*RE/
RE$CAT*$NC$AN/
RE$CAT*$NPREPARAT*$NA*URE
RelocationResource
Allocation
RE$CAT*$N
REFUEST
RE$CAT*$NREFUEST
ACBN$E/8E
RE$CAT*$NA*URE
RelocationCancel
RE$CAT*$NCANCE
RE$CAT*$NCANCEACBN$E/8E
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N )
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
33/48
*nter+ace Protocol and Si)nalin) lo&
+%ementary
#r$ce"ure
Initiatin&
Messa&e
Successfu%6utc$me
Unsuccessfu%6utc$me
Responsemessa)e
Response messa)e
SRNSContextTrans+er
SRNSC$NTETREFUEST
SRNS C$NTETRESP$NSE
Securit!ode
Control
SECUR*TL$/E
C$AN/
SECUR*TL $/EC$PETE
SECUR*TL $/EREQECT
/ata ?olumeReport
/ATA?$UEREP$RTREFUEST
/ATA ?$UEREP$RT
Reset RESET RESET
ACBN$E/8E
ResetResource
RESETRES$URCE
RESET RES$URCEACBN$E/8E
ocation
related /ata
$CAT*$N
REATE//ATA
REFUEST
$CAT*$N
REATE/ /ATARESP$NSE
$CAT*$N
REATE/ /ATAA*URE
TA6' $ ) C' AS S )
+%ementary #r$ce"ure Messa&e
RA odi+ication Re=uest RA $/*L REFUEST
RA Release Re=uest RA REEASE REFUEST
*u Release Re=uest *U REEASE REFUEST
Relocation /etect RE$CAT*$N /ETECT
Relocation Complete RE$CAT*$N C$PETE
SRNS /ata or&ardin) *nitiation SRNS /ATA $RAR/C$AN/
SRNS Context or&ardin) +romSource RNC to CN
$RAR/ SRNS C$NTET
SRNS Context or&ardin) to Tar)et
RNC +rom CN
$RAR/ SRNS C$NTET
Pa)in) PA8*N8
Common */ C$$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*N8C$NTR$
ocation Report $CAT*$N REP$RT
*nitial UE essa)e *N*T*A UE ESSA8E
*2 Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
34/48
Chapter 3 *nter+ace and Protocol
+%ementary #r$ce"ure Messa&e
/irect Trans+er /*RECT TRANSER
$%erload Control $?ER$A/
Error *ndication ERR$R *N/*CAT*$N
TA6' $ * C' AS S *
+%ementary#r$ce"ure
Initiatin&Messa&e
Resp$nse Messa&e
RA Assi)nment RA ASS*8NENT
REFUEST
RA ASS*8NENT
RESP$NSE x N 5N16
Proto#ol related to Inter=a#eIurThe hi)hest la!er protocol o+ *nter+ace *ur control plane isRANSAP. i)ure 1,sho&s the structure o+ *nter+ace *ur protocol.
F I # U R $ 1, ST RUCT UR$ % F I NT $ RF AC$ IU R PR% T % C% '
SSC"NNI
SSCOP
?TP3";
AA&
IP
SCTP
SCCP
AA&
SSC"NNI
STC +B.'&0.'-
RNSAP Iur %ataStrea6+s-
Trans4ort
Net8or$
a9er
P9si#al a9er
Trans4ort2ser
Net8or$Plane
Control Plane 2ser Plane
Trans4ort2ser
Net8or$Plane
Trans4ort Net8or$Control Plane
Radio
Net8or$
a9er
AT?
ACAP+B.,30.'-
AA
SSC"NNI
SSCOP
?TP3";
IP
SCTPSSC"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
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
35/48
*nter+ace Protocol and Si)nalin) lo&
un#tion and Stru#ture o= Inter=a#eIur
*nter+ace *ur is to transmit data &hen UE per+orms the so+thando%er et&een adacent RNCs.
38PP prescries that *nter+ace *ur is a lo)ic entit!. That is9
*nter+ace *ur and *nter+ace *u can either share one channel +orthe transmission or connect %ia independent ph!sical inter+ace.
%C! ra6e 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 ut directl! send /C0 data at *nter+ace *u to*nter+ace *ur. /C0 +rames o+ *nter+ace *ur and *nter+ace *u (eep
consistent9 to )reatl! reduce /C0 data processin) ! /RNC.
RNSAP Pro#ess
TA6' $ + C' AS S 1 $' $ M $ NT AR. PR% C$ DUR$ S
+%ementary#r$ce"ure
Initiatin&Messa&e
Successfu%
6utc$me
Unsuccessfu%
6utc$meResponsemessa)e
Responsemessa)e
Radio in(Setup
RA/*$ *NBSETUPREFUEST
RA/*$ *NBSETUPRESP$NSE
RA/*$ *NBSETUP A*URE
Radio in(Addition
RA/*$ *NBA//*T*$N
REFUEST
RA/*$ *NBA//*T*$N
RESP$NSE
RA/*$ *NBA//*T*$N
A*URE
Radio in(/eletion
RA/*$ *NB/EET*$NREFUEST
RA/*$ *NB/EET*$NRESP$NSE
S!nchronised Radio in(Recon+i)urationPreparation
RA/*$ *NBREC$N*8URAT*$NPREPARE
RA/*$ *NBREC$N*8URAT*$N REA/L
RA/*$ *NBREC$N*8URAT*$N A*URE
Uns!nchroni
sed Radioin(
Recon+i)uration
RA/*$ *NB
REC$N*8URAT*$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
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
36/48
Chapter 3 *nter+ace and Protocol
+%ementary
#r$ce"ure
Initiatin&
Messa&e
Successfu%6utc$me
Unsuccessfu%6utc$me
Responsemessa)e
Responsemessa)e
Ph!sicalChannelRecon+i)uration
P0LS*CAC0ANNEREC$N*8URAT*$NREFUEST
P0LS*CAC0ANNEREC$N*8URAT*$N C$AN/
P0LS*CAC0ANNEREC$N*8URAT*$N A*URE
/edicatedeasuremen
t *nitiation
/E/*CATE/EASUREE
NT*N*T*AT*$N
REFUEST
/E/*CATE/EASUREENT
*N*T*AT*$NRESP$NSE
/E/*CATE/EASUREENT
*N*T*AT*$NA*URE
CommonTransport
ChannelResources*nitialisation
C$$NTRANSP$RT
C0ANNERES$URCESREFUEST
C$$NTRANSP$RT
C0ANNERES$URCESRESP$NSE
C$$NTRANSP$RT
C0ANNERES$URCESA*URE
Commoneasurement *nitiation
C$$NEASUREENT*N*T*AT*$NREFUEST
C$$NEASUREENT*N*T*AT*$NRESP$NSE
C$$NEASUREENT*N*T*AT*$NA*URE
*n+ormationExchan)e*nitiation
*N$RAT*$N EC0AN8E*N*T*AT*$NREFUEST
*N$RAT*$NEC0AN8E*N*T*AT*$NRESP$NSE
*N$RAT*$NEC0AN8E*N*T*AT*$NA*URE
TA6' $ , C' AS S ) $' $ M $ NT AR. PR% C$ DUR$ S
+%ementary #r$ce"ure Initiatin& Messa&e
Uplin( Si)nallin) Trans+er UP*NB S*8NA*N8 TRANSER*N/*CAT*$N
/o&nlin( Si)nallin) Trans+er /$N*NB S*8NA*N8 TRANSERREFUEST
Relocation Commit RE$CAT*$N C$*T
Pa)in) PA8*N8 REFUEST
S!nchronised Radio in(Recon+i)uration Commit
RA/*$ *NB REC$N*8URAT*$NC$*T
S!nchronised Radio in(Recon+i)uration Cancellation
RA/*$ *NB REC$N*8URAT*$NCANCE
Radio in( ailure RA/*$ *NB A*URE *N/*CAT*$N
Radio in( Restoration RA/*$ *NB REST$RE *N/*CAT*$N
/edicated easurementReportin)
/E/*CATE/ EASUREENT REP$RT
/edicated easurementTermination
/E/*CATE/ EASUREENTTER*NAT*$N REFUEST
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N **
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
37/48
*nter+ace Protocol and Si)nalin) lo&
+%ementary #r$ce"ure Initiatin& Messa&e
/edicated easurementailure
/E/*CATE/ EASUREENT A*URE*N/*CAT*$N
/o&nlin( Po&er ControlH//I / P$ER C$NTR$ REFUEST
Compressed ode CommandH//I
C$PRESSE/ $/E C$AN/
Common Transport ChannelResources Release
C$$N TRANSP$RT C0ANNERES$URCES REEASE REFUEST
Error *ndication ERR$R *N/*CAT*$N
/o&nlin( Po&er TimeslotControl HT//I
/ P$ER T*ES$T C$NTR$REFUEST
Radio in( Pre"emption RA/*$ *NB PREEPT*$N REFU*RE/
*N/*CAT*$N
Radio in( Con)estion RA/*$ *NB C$N8EST*$N*N/*CAT*$N
Common easurementReportin)
C$$N EASUREENT REP$RT
Common easurement
Termination
C$$N EASUREENT
TER*NAT*$N REFUEST
Common easurement
ailure
C$$N EASUREENT A*URE
*N/*CAT*$N
*n+ormation Reportin) *N$RAT*$N REP$RT
*n+ormation Exchan)e
Termination
*N$RAT*$N EC0AN8E
TER*NAT*$N REFUEST
*n+ormation Exchan)eailure
*N$RAT*$N EC0AN8E A*URE*N/*CAT*$N
Proto#ol Related to Inter=a#eIu>The hi)h la!er protocol o+ *nter+ace *u control plane is NAP.
The user plane consists o+ se%eral +rame protocols. i)ure 1Gsho&s the structure o+ protocols.
*+ Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
38/48
Chapter 3 *nter+ace and Protocol
F I # U R $ 13 ST RUCT UR$ % F I NT $ RF AC$ IU 6 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+ortNetwork
Control &lne
'8
'' y+e 5
User &lne
SSC%$UNI
SSC=&
'' y+e 5
SSC%$UNI
SSC=&
;.24/
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 lo)ic model consists o+ cell9 common transmissionchannelport9 Node communication context9 and thecorrespondin) /SC0/C0. Node controls NCP and the
communication controls port CCP9 etc.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N *,
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
39/48
*nter+ace Protocol and Si)nalin) lo&
Node communication context and the correspondin)/SC0/C0 port are related to dedicated user ser%ices.
Node communication context is correspondin) to CRNC
communication context.
Node communication context is identi+ies ! Node
Communication Text */9 containin) necessar! in+ormation tocommunicate &ith UE. *t is estalished &hen R is setup and
deleted &hen R is deleted.
There is onl! one NCP lin( on one Node . RNC sends all Node common control si)nalin) +rom NCP. NCP lin( must e setupe+ore operatin)9 maintainin)9 and controllin) Node .
There can e se%eral CCP lin(s on one Node . RNC sends allNode dedicated control si)nalin) +rom CCP lin(. Usuall!9 onecell inside Node can e con+i)ured &ith one CCP 5it is ust aroutine9 not certain.6
*3 Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
40/48
Chapter 3 *nter+ace and Protocol
N;AP Pro#ess
TA6' $ 3 C' AS S 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
CellRecon+i)uration
CEREC$N*8URAT*$N
REFUEST
CEREC$N*8URAT*$N RESP$NSE
CEREC$N*8URAT*$N A*URE
Cell /eletion CE/EET*$NREFUEST
CE /EET*$NRESP$NSE
CommonTransport
ChannelSetup
C$$NTRANSP$RT
C0ANNESETUP
REFUEST
C$$NTRANSP$RT
C0ANNE SETUPRESP$NSE
C$$NTRANSP$RT
C0ANNE SETUPA*URE
Common
TransportChannel
Recon+i)uration
C$$N
TRANSP$RTC0ANNE
REC$N*8URAT*$N
REFUEST
C$$N
TRANSP$RTC0ANNE
REC$N*8URAT*$N RESP$NSE
C$$N
TRANSP$RTC0ANNE
REC$N*8URAT*$N A*URE
CommonTransportChannel/eletion
C$$NTRANSP$RTC0ANNE/EET*$NREFUEST
C$$NTRANSP$RTC0ANNE/EET*$NRESP$NSE
Ph!sicalSharedChannelRecon+i)ure
HT//I
P0LS*CAS0ARE/C0ANNEREC$N*8U
RAT*$NREFUEST
P0LS*CAS0ARE/C0ANNEREC$N*8URAT*
$N RESP$NSE
P0LS*CAS0ARE/C0ANNEREC$N*8URAT*
$N A*URE
Audit AU/*TREFUEST
AU/*TRESP$NSE
AU/*T A*URE
loc(Resource
$CBRES$URCEREFUEST
$CBRES$URCERESP$NSE
$CBRES$URCEA*URE
Radio in(Setup
RA/*$ *NBSETUPREFUEST
RA/*$ *NBSETUPRESP$NSE
RA/*$ *NBSETUP A*URE
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N *-
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
41/48
*nter+ace Protocol and Si)nalin) lo&
+%ementary
#r$ce"ureMessa&e
Successfu%6utc$me
Unsuccessfu%6utc$me
Responsemessa)e
Responsemessa)e
S!stem*n+ormationUpdate
SLSTE*N$RAT*$N UP/ATEREFUEST
SLSTE*N$RAT*$NUP/ATERESP$NSE
SLSTE*N$RAT*$NUP/ATE A*URE
Common
easurement*nitiation
C$$N
EASUREENT
*N*T*AT*$NREFUEST
C$$N
EASUREENT*N*T*AT*$N
RESP$NSE
C$$N
EASUREENT*N*T*AT*$N
A*URE
Radio in(Addition
RA/*$ *NBA//*T*$NREFUEST
RA/*$ *NBA//*T*$NRESP$NSE
RA/*$ *NBA//*T*$NA*URE
Radio in(/eletion
RA/*$ *NB/EET*$NREFUEST
RA/*$ *NB/EET*$NRESP$NSE
S!nchronisedRadio in(Recon+i)urationPreparation
RA/*$ *NBREC$N*8URAT*$NPREPARE
RA/*$ *NBREC$N*8URAT*$N REA/L
RA/*$ *NBREC$N*8URAT*$N A*URE
Uns!nchronis
ed Radio in(Recon+i)urati
on
RA/*$ *NB
REC$N*8URAT*$N
REFUEST
RA/*$ *NB
REC$N*8URAT*$N RESP$NSE
RA/*$ *NB
REC$N*8URAT*$N A*URE
/edicatedeasurement*nitiation
/E/*CATE/EASUREENT*N*T*AT*$NREFUEST
/E/*CATE/EASUREENT*N*T*AT*$NRESP$NSE
/E/*CATE/EASUREENT*N*T*AT*$NA*URE
Reset RESETREFUEST
RESETRESP$NSE
CellS!nchronisati
on *nitiationH3.#-cps
T//I
CESLNC0R$N*
SAT*$N*N*T*AT*$N
REFUEST
CESLNC0R$N*SAT*
$N *N*T*AT*$NRESP$NSE
CESLNC0R$N*SAT*
$N *N*T*AT*$NA*URE
Cell
S!nchronisation
Recon+i)uration H3.#-
cps T//I
CE
SLNC0R$N*SAT*$N
REC$N*8URAT*$N
REFUEST
CE
SLNC0R$N*SAT*$N
REC$N*8URAT*$N RESP$NSE
CE
SLNC0R$N*SAT*$N
REC$N*8URAT*$N A*URE
CellS!nchronisationAdustmentH3.#-cpsT//I
CESLNC0R$N*SAT*$NA/QUSTENT REFUEST
CESLNC0R$N*SAT*$N A/QUSTENTRESP$NSE
CESLNC0R$N*SAT*$N A/QUSTENTA*URE
*0 Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
42/48
Chapter 3 *nter+ace and Protocol
+%ementary
#r$ce"ureMessa&e
Successfu%6utc$me
Unsuccessfu%6utc$me
Responsemessa)e
Responsemessa)e
*n+ormationExchan)e*nitiation
*N$RAT*$NEC0AN8E*N*T*AT*$NREFUEST
*N$RAT*$NEC0AN8E*N*T*AT*$NRESP$NSE
*N$RAT*$NEC0AN8E*N*T*AT*$NA*URE
TA6' $ - C' AS S )
+%ementary #r$ce"ure Messa&e
Resource Status *ndication RES$URCE STATUS *N/*CAT*$N
Audit Re=uired AU/*T REFU*RE/ *N/*CAT*$N
Common easurementReportin)
C$$N EASUREENT REP$RT
Common easurementTermination
C$$N EASUREENTTER*NAT*$N REFUEST
Common easurementailure
C$$N EASUREENT A*URE*N/*CAT*$N
S!nchronised Radio in(
Recon+i)uration Commit
RA/*$ *NB REC$N*8URAT*$N
C$*T
S!nchronised Radio in(Recon+i)uration Cancellation
RA/*$ *NB REC$N*8URAT*$NCANCE
Radio in( ailure RA/*$ *NB A*URE *N/*CAT*$N
Radio in( Restoration RA/*$ *NB REST$RE *N/*CAT*$N
/edicated easurement
Reportin)
/E/*CATE/ EASUREENT REP$RT
/edicated easurementTermination
/E/*CATE/ EASUREENTTER*NAT*$N REFUEST
/edicated easurementailure
/E/*CATE/ EASUREENT A*URE*N/*CAT*$N
/o&nlin( Po&er Control
H//I
/ P$ER C$NTR$ REFUEST
Compressed ode CommandH//I
C$PRESSE/ $/E C$AN/
Unloc( Resource UN$CB RES$URCE *N/*CAT*$N
Error *ndication ERR$R *N/*CAT*$N
/o&nlin( Po&er Timeslot
Control HT//I
/ P$ER T*ES$T C$NTR$
REFUEST
Radio in( Pre"emption RA/*$ *NB PREEPT*$N REFU*RE/*N/*CAT*$N
Cell S!nchronisationReportin) H3.#-cps T//I
CE SLNC0R$N*SAT*$N REP$RT
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N *
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
43/48
*nter+ace Protocol and Si)nalin) lo&
+%ementary #r$ce"ure Messa&e
Cell S!nchronisationTermination H3.#-cps T//I
CE SLNC0R$N*SAT*$NTER*NAT*$N REFUEST
Cell S!nchronisation ailureH3.#-cps T//I CE SLNC0R$N*SAT*$N A*URE*N/*CAT*$N
*n+ormation Reportin) *N$RAT*$N REP$RT
*n+ormation Exchan)eTermination
*N$RAT*$N EC0AN8ETER*NAT*$N REFUEST
*n+ormation Exchan)eailure
*N$RAT*$N EC0AN8E A*URE*N/*CAT*$N
Cell Setu4 Pro#essF I # U R $ 10 C$'' S$TUP PR%C$SS
RNC Node B
NB'&. Cell setu+ reuest
NC&?CC& nd 'C'& set u+
Reset +rocess
NB'& nd cell setu+ res+onse
NB'& nd SCC&C# setu+ reuest
NB'& nd SCC&C# setu+ res+onse
'C'&: ER;(%'C#)
'C'& -EC%
'C'&-ER;(&C#)
'C'&-EC%
NB'&- R'C# setu+ reuest
NB'&- R'C# setu+ res+onse
'C'&-ER;( R'C#)
'C'&- EC%
NB'&- Syste, in5or,tion u+dte reuest
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
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
44/48
Chapter 3 *nter+ace and Protocol
CS Call Ori:ination lo8
+RRC Setu4 on CC!-F I # U R $ 1 C A' ' %RI # I NAT I % N F ' %W 4RRC S $ T UP % 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#DCC#)
INII' 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#%&-U+link S6NC
DC#%&-Downlink S6NC
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N +1
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
45/48
*nter+ace Protocol and Si)nalin) lo&
CS Call Ori:ination lo8
+RRC Setu4 on %C!-F I # U R $ )2 CS CA' ' % RI # I NAT I % N F ' % W 4RRC S $ T UP % 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,+.
INII' D(C8 ser!ice re)
D(setu+)
D(cll +roceedin")
D('uthentiction re)
D('uthentiction res+)
Initil UE ,ess"e
R'B ssi"n,ent reR recon5i" +re
R recon5i" redy
'C'& ES. re
'C'& ES. c5n
R recon5i" co,,it
RB setu+
RB setu+ co,+ R'B ssi"n,ent res+
D(lertin")
D(connect)
D(connect ck)
UE NodeB RNC 8SC
'C'& ES. re
'C'& ES. c5n
D(C8 ser!ice cce+t)
DC#%&-U+link S6NC
DC#%&-Downlink S6NC
+) Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
46/48
Chapter 3 *nter+ace and Protocol
CS Call Ter6ination lo8
F I # U R $ )1 CS CA' ' T $ RM I NAT I % N F' % W 4RRC S $ T UP % N DC(5
RC connection re.
R setu+ re
R setu+ res+.
'C'& ES. re
'C'& ES. c5n
RC connection setu+
NII' D(&"in" res+)
(setu+)
(cll con5ir,ed)
('uthentiction re)
('uthentiction res+)
Initil UE ,ess"e
R'B ssi"n,ent reR recon5i" +re
R recon5i" redy
'C'& ES. re
'C'& ES. c5n
R recon5i" co,,it
B setu+
B setu+ co,+ R'B ssi"n,ent res+
(lertin")
(connect)
(connect ck)
"in" ty+e* +"in"
UE B NodeB RNC 8SC
'C'& ES. re
'C'& ES. c5n
DC#%&U S6NC
DC#%&D S6NC
RC connection setu+ co,+.
Con+idential and Proprietar! *n+ormation o+ :TE C$RP$RAT*$N +*
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
47/48
*nter+ace Protocol and Si)nalin) lo&
Release lo8 in CS %o6ain
CN Ori:inatesF I # U R $ )) R $ ' $ AS $ F' % W I N CS D % M AI N CN I NI T I 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
-
8/12/2019 3 Interface Protocol and Signaling Flow 49
48/48
Chapter 3 *nter+ace and Protocol
Release lo8 in CS %o6ain
2E Ori:inatesF I # U R $ )* R $ ' $ AS $ F' % W I N CS D % M AI N U$ INI T I AT $ S
D re ese
D Relese co,
RRC connection relese
RRC connection relese co,
IU relese co,,nd
IU re ese co,+
R delete
R delete res+
'C'& RE. re
'C'& RE. c5n
U# NodeB RNC M"C
'C'& ES. re
'C'& ES . c n
D sconnect on