INBULLETS

215

LONG TERM EVOLIJTION (LTE)

23.L

RRC CONNECTION ESTABLISHMENT

make the lransition procedures

RRC conncction establishment is used 1tr make the transilion from RRC ldle mode to RRC Connecled mode. UE must 1() RRC Connecled mode before transfening any applicalion dat4 or oompieting any signalling

The RRC conncction cstablishment procedure is always initiatod by thc UE but ca.r be- tliggcrcd bf either the UE or the -19!_gork. For example, the Ulr triggers RRC conncction establishment ifthe end-user starts an application to browse the intemct, or to send an email. SimiJarly" the iJE triggers RI{C connection establishment ilthe IJE movcs into a nerv 'fracking Area and has 10 completc the-l'racking Area Update signalling procedure. 'l'hc nctwork triggers thc RRC connection cstabljshment procedure by sending a Paging messagc. This could be used to allow the delivcry ofan incoming SMS or notillcation of an incoming voice call

RRC corLnection eslablishmcnt for LTE is rclalively simple compared to RRC connection cstablishmenl for UM'I-S. The IJM l'S procedurc rcquires NBAP and ALCAP signalling across the Iub interlace betwecn the Node B and RNC. Thcse signaliing protocols are used to setup a radio link and new transport connection. I he flat network architccture for LIE removes the requirement for liesc signalling procedures In the casc of LTII, the initial Non-Access Stratum (NAS) message is transferred as part ofthe RRC conncction establishmcnt proccdure. In the case of LIMTS, thc initial NAS mcssage is transferrcd after the RRC conncction cstablishment procedure. Thc approach uscd by L l'E hclps to rcduce connection establishment delay RRC conncction establishment configures Signalling Radio Bearer (SRB) I and allows subsequent signalling 10 use the Dedicated Control Channel (DCCIJ) ralher than the Common Conlrol Channcl (CCCIJ) used by SRB 0
The signalling 1br RRC connection establishmcnl is shown in Figure 107. the entirc procedurc is compleled using oniy RltC signalling. A 3-way handshakc is used 10 move thc IJE into RRC connected node

eNode B

s
i

Er

UE

&
RRC Connection Setup / SRB 0 / CCCH / DL,SCH / PDSCH

RRC Connection Request / SRB 0 / CCCH / UL-SCH / PUSCH

/SRB

/ DCCH / UL.SCH / PUSCH

liigure

107

Signalling for RRC connection establishmcnt

The RRC Conncction Request message is sent as part oflhc Random Access procedure. It con'esponds to thc jnitial Laycr 3 message shown in Figure 84 (section 2l.l). It is transferred using SRB 0 on the Common Control Channcl (CCCH) because neither SRB 1 nor a Dedicated Control Channel (l)CCl l) havc bcan setup at this point. 'Ihe uplink Resource Block allocation 1br the R.RC Conneclion Rcquest message is signalled within the l{andom Access l{esponsc mossage The content ofthc RRC Connection Request message is shown in l'ablc 130. It includcs a UE identity and an cstablishmcnt cause. There is no scope for the LIE to report any measurcments wilhin the RRC Conncclion Requcst message. The [,MTS version ofthc RRC Connection Requcst messagc allows thc UD to reporl CPICH measurements which can subsequently be used lor downlink open loop power conhol oalculations The LJE identit), is signailed using tho SAE Temporary Mobile Subscriber ldentity (S-TMSI) ifthc LIIJ is rcgistered u ith .^ thc l'racking Area 1o whioh thc cuncnl ccll belongs. Othcrwise, the UE selects a rirndom numbcr in thc range from l)to 2o' - I to represent the IJH identity. ]'he S-|MSI is described in scction 26.3.3

216

IN BULLETS
Informarior) lilemnts UE Idenlily

cltotcE
s-'r'Msl
Random Value

iistablishmenl Cause Emrgcncy

CiIOICE
High Priority Acccss

Mobile Terminating Access

Mobile Originating Data

Trblc

130

- Content

of RRC Connection Request mes$age

l'he eslablishnenl causc wilhin thc RRC.Connection Request message is dctermined by thc Non-Acccss Straturn (NAS) procedure for which thc connection is being cstablished. lhc relationship bctween eslatiishmenr causc and NAS proccjure is specified by 3 GPP 'f S 24.3 01 . lh is relationship is presentcd in I'able l 3 L ln all caies. ihc RRC establ ishrn ent causc is sct 1(] 'll.igh Jtioi ty A qr,gss' if thc UE use s Acce ss class (AC) r I to I 5. The I ist of establishment causes is significantly shorter thlur the list used by UMTS
NAS l,rocedure
Attach Dctach Tracking Area Updalc Sen ic,l] Requcst
,.1t

RRC llstablishment Cause

Mobile Originating Signalting

Uscr plane radio resources request

Mobile Originating Data

Uplink signalling resourcs request

Paging.csponse for PS core ntwork domain Extendcd Serviolj Requcst Mobile origiDali4g CS fallbaok

Mobilc Terminating Access

Mobile Originating Data

i '. I.l ,
Tablc

'r.;.t t..1

Mobil terminating CS fallback

Mobile originatjng CS fallback emergency cali

Mobile Tgrmjnating Access

hmcrgency

l3l -

Relationship betwcen higher layer establishment cause and RRC establishment caxse

The I JE starls thc T300 timer aller transmitting the RRC Conncction Roquest messagc. l'he value of T300 is broadcast 2 [.lM'l'S uscs T300 in,combination with N300 to manage re-transmissions of the RRC Connection l{equest message. l-Tll does not have an N300 paramcter and the IIRC Conncction Request message is sent only once pr eslablishment procedure. l-TE uses the T300 timer 1o define how long the UE waits for a iesponse to the I{RC Connection Rcquest lnessage. 1 hc cstab)ishment procedure fails if T300 cxpires beforc receiving an RRC Connectjon Sctup messagc. The procedure aiso fails iflhe UE completes a cell re-selectjon prior lo rcceiving the RRC Connection Setup rnessage

wjthin SIB

Random access contcntion can occur afler scnding the RRC Conncction Request message. Seotion 2l .l explains that conlention occurs when multjple liE select the same subframe and preamble scquence for pRACH transmtsston. contention requircs the UF to repeat lraosmission ofthc PRACII preamble and ihe subsequent RRC Connection Requesl mcssage. This increases the delay associated with connection stabjjshment but docs not cause the ovcrall procedure to lail unlcss the maximum number ofprcamble lransmissions has br:en reached

Assuming that.andom access contentio-n does not occur, the UII proceeds to wait for an RRC Conneclion Setup mcssage from the eNodc B.'l-he UE has successfully compieted the random access procedurc so has been allocated a C-RNII (signalied within thc random aocess response mcssage). l'he tJl.l monilors the PDCCIJ for a downljni allocation addrcsscd to i1s (l-RNll lhc PDCCII sp(jcifies the set ofPDSCII Resource Blocks used to transfer the ]lllc Conncction Setup messagc. The IIRC Connection Sctup message is transferred using SRB 0 on thc CCCH Thc RIIC Conneclion Setup messagc conlains configuralion information for,sll] 'fhis allows subsequenl signaljing to | use the DCCH logical channel SRB 2 is always configurcd after security activation st, the RRC Connectjon selup message does not include any inlbrmation regarding SRB 2. l he cNodc B can inslruct thc UL to appiy a default configuration for SRB 1, or it can instruct thc IJE to apply a specific configuration.

LONG TERM EVOI,UTION (I-TE)

The delault configuralion for SRB I is prscnlcd in l able 132. This dcfault configuration has been specified by 3GPP within TS 36.331. tJsing the dclauil configuralion heips to reduce thc signalling requirement. The defauil oonfiguntion lor SIiB 2 is also presented in Table 132 lbr information. SRB 2 has a lower prior;ry than SRB l- i.e. a value of3 represents a lowcr priority than a valuc of I . Both SRll I and 2 always use acknowledged modc Rl.C
SRB

SRB 2

RLC Configuration

Uplink

Poll Rctransmission

imer

45

Poll PDU Poll B)4o Max Rctransmission l'hreshold

Infinity lnfinity
4
35

Infinitv

Infinity
4
35

Downiink

R-ordering Timer
Status Prohibit Timr

0
3

Logical Channel Configuration

Priority
Prioritised Bit Rale Bucket Size Duration Logical Channel Group

lnfinity N/A
0

lnfinity N/A
0

'l'able 132

Default configurations for SRB

and SRB 2

'I he RRC Connection Setup mcssage can also define configuration information for the PDSCH, I'tJCCH and Pt.lSCH physical channels. I1 can also include informalion regarding uplinJ< power control, CQI reporting, the Sounding Relcrence Signal, antenna configuration and scheduling requests

Upon recelving ar RllC Conncction Setup message, the UE stops the T300 timer and makes the transilion 10 Rli.C Connected mode. The UE thcn proceeds to complete the procedure by sending ar RRC Connectjon Setup Completc message.'lhe conlent ofthc RRC Connection Setup Complete message is shown in'lable 133
Information Elements RRC Transaction ldenti{ier (01o 3)
Selecicd PLMN ldcnfiry (1 to 6) Registered

MMU

PLI\4.1 ldontity

MMEG] MMEC
l)edicated NdS J nformation

'fable 133 - Confcnt ofRRC Connection Setup Complete message Thc l'ransaction Idcntifier, combined with the message type, identifics thc RRC procedure with thc UE Thc Sclected PLMN Identity defines a pointcr to a PLMN listed within SIB to connect when a cell belongs to more than a single PLMN

l.

i.e. UE. sclect thc PLMN to which they want

The llegistered MME inlormaljon is optional, and is included when available. It becomes available after a UII has regisrered *ith an MME. Thc MMll is identilicd by its Globaily Unique MME ldentity (Gt.lMMUl) which is a concatcnarion of the PLMN idenrity, MME Group Idcnrity (MMDGI) and MME Codc (MMEC). Thc MMEC identifies the

MME u,ithin its group

The llll also includes its initial Non-n ccess Stratum (NAS) mcssage wilhin the RRC Connection Setup Complcte message. NAS messagcs are specilied within 3GPP l S 24.301. As jndicatcd within Table l3l, thc NAS message could be an Attach, Detach, 'l'racking Arca Update, Scrvice Request or Exlended Service Request mcssage
'l he cNodc B cxtracts thc NAS message from the IIRC Connection Sctup Complete message and forwards il to an MMIl using thc Sl Application Protocol (Sl -AP) Initial UE Message. Forwarding this message does not form pad ofthe RRC

cstablishment procedurc but is described within this soction for complctcncss

The contenl ofthe S1-AP Initial UE Mcssage is shown in Tablc 134. The eNodc B scnds this mcssage to the appropriale MMII based upon i1s NAS Node Selection Funclion (NNSF). In thc case of a Service Request, the S- I MSI includod with jn

218

IN BULLET
the RRC Connection Requcst is used to identiry the appropriate MME (S- I MSI jncludes the MMEC). In the case ol an Altach or Tracking Area ljpdalc" the cNodc B uses thc GUMMEI included within the I{RC Connection Sctup Complete message. Thc eNode B is lree 10 selcct an MME u,hen the UE does nol have an S-TMSI nor GUMMlll
Information lllements
Node B UE
S

Presflc

l-AP ldentity

Mandatory

NAS PDIJ

Mardatory
Mandatory Mandalorv Optional Optional Mandalory Optional

'lracking Area Identity (TAI)

E-tJ I'RAN Ccll Global Jdenriry (CGI)

S.TMSI
CSG Identity

RRC Dstablishment Cause

Globally Unique MME ldntity (cUMMEI) Tebt t34

Content ofSl ApplicatioD protocot (Sl_Ap) Initial Utr] Message

Thc cNode B allocatcs thc cNode B UE Sl-A? Identity to allow the eNode B 10 identifr the tJE wilhin SI signalling procedures. l'hc MME UE Sl-AP Identity (not included within ths Initial UE Message) allows the MME ro idendtthc UE within Sl signalling procedures

Figure 108 illustrates the signalling associated with the RRC connoction cstablishment proccdure when the cNode B rejects thc RRC Connection Requesl. The reject mcssage is rctumed to thc UE using SRB 0 on ihe CCCI I logical channei. l hc eNode B may reject the connection eslablishment request as a rcsuh ofcongestion
eNode

$lI
1'

{p

UE

&
RRC Connection Reject / SRB 0 / CCCH / Dt -SCH / PDSCH

RRC Conneclron Request / SRB 0 / CCCH / UL,SCH / PUSCH

Figurc

108

Signalling for rejccted RRC connection establishmcnt

The contenl ofthe RRC connection Rciect message is presented in l-ablc 135. The message only includes a wait time. This is in contrast to the equivalenl UMTS messagc which also jncludcs a rejection cause- although the UMTS rejection causc can onJy be dcfincd as congestion or unspecified The UM I'S messagc can also include redireclion information to direct the ULI towards another RF carrier, or Radio Access 'l'echnology (RA'l')
lnformation Elements

Wail lime

(0

to

16 seconds)

Table 135 - Content of RRC Connection Reiect messag

lJpon recciving an IIRCI Connecljon Re.iecl mcssage, the UE starts the T302 limer with its value set equal to the wait 1ime. Access Class barring for mobilc originating caiJs, mobiic originating signalling and mobile terminating access is applied until T302 expircs, i.e. the tJE is no1 allo\.vcd to send another RRC Conncction Roquest for thosc conniction types, and to the same cell, until T302 expires. '1302 is stopped ifthc tJE completes ccll reselcction. In that casc. the UIi is p;rmjlted to scnd an I{RC Connection I{eques110 the ncw cell

ln conlrast 10 UM I S. L fE rcquires thr; higher iayers to initiate a new connectjon estabiishmcnl proccdure after the UE rcccives an RRC Conneclion l{eject messagc. UMI S allows the llRC Conneclion Requcst message to bc repeated from thc RI{C laycr, based upon 1he value ofN300

I,ONG TERM EVOLUTION (I,TE)

23.2 ATTACH AND DE,FAULT BEARER ESTABLISHMENT

* * *
Thc attach procedure is uscd to registcr with the Evolled I'acket (lore (EPC). This allows thc subsequent uso ofpacket services within the Evolved Packct System (llPS). ]'he IJD can also usc thc a11ach procedurc to regisler for non-EPS services, e.g. thc speech service based upon CS faliback

'Ihc atlach procedure also involves establishing a default bearer betwccn the IJE and PDN Gateway. This provides alwayson corlnectiviry for thc UE. In addition, the attach procedurc can lrigger thc cslablishment of dcdicated bearers
The signalling associated with thc a11ach and delault bearer establishment procedure is illustrated in Figurc 109. Somc signalling messages are nested wilhin othcr messages, e.g. rhe PDN Connectivity Rcqucsl message is scnt within an Attach Request message, which is sent within an RRC Conncclion Sotup Complete mcssage

MI\,4E

w'
i Attach Reouest/ I PDN Connec{ivity Request

Serving Gateway

PDN

Gateway

w@

RRC Connection Reconfiguration / Attach Accept / Aclivate Default EPS Bearer Context Request RRC Connection Reconflguraton Complete

lnitial Context Setup Requesl / Attach Accept / Activate Default EPS Bearer Context Request

Create Session Response

Uplink lnforma|on Transfer / Atiach C.omplete / Activate Default EPS Bearer

ConlextAccept

Uplink NAS Transport / Attach Complele / Activate Default EPS Barer Context Accept

Figur

109

Signalling for the attach and default bearer establishmcnt procedur

The atlach procedurc slarts with the RRC connectjon cstablishment proccdure which takes the UD from RRC ldlc mode to RRC connected mode. Thc Altach Requcst messagc is included as the 'Dedicatcd NAS Information' within thc RRC Sctup Complctc mcssage . Thc full contcnt of the RRC Selup Complete mcssage is presented in Table 1 33 within section 23. I . The Atlach Roqucst is a Non-Access Stratum (NAS) message so its contcnt is spccified by 3GPP TS 24.301. This cortenl is presented in 'l able 136 The firs1 3 information elements within the Attach Rcquest messagc rcpresent the message hcadcr. fhe Protocol Discriminator indicatcs that the subsequenl message is an EPS mobility managcmcnt message. lts vaiue is specified within 3GPP 24.007. 'fhc Sccurjty Ileader Type jndicates whcther or not the Nn S message is integib, prolected aId ciphered. The Atlach Request Messagc ldentity indicates that thc mcssage itself is an Attach Request

IN BULLETS

The main contenl 01'the Attach Request mcssage stads with the EPS Anach 1'ype \\'hich can be configurcd with yaiues of 'EPS Altach' or 'Combined EPS/IMSI Altach'. Thcsc valucs corrcspond to registering for only EPS packel scn,iccs, and registering for both EI'S packet scrvices and non-EPS scrviocs. Thc mosl common non-EPS service is likely to be the CS speech service lnformalion Elements Protocol Discrtminatur
Secatily Headel Type Attach ReqtEsl Messdge ldentity
EPS Attach Typc Presence

Murulutory

Mandalory

Mandatorv Mandalory Mafldatory Mandatory Mandalory Optional Optional Optional Optional

C)ptional

NAS Key Set ldcntifier Oid CiUTI or IMSI

UE Nehvork Capability

ESM Mcssagc Containcr Oid P-TMSI Signature

Additional GUl

l,iut Visited Registcred TAl

DRX Parameter
MS Netrvork Capability

Old Localion Are, Idenlificalion TMSI Status Mobile Station Classmark 2 Mobile Station Classmark 3
Supported Codecs

Optional Optional Optional Ontjonal Optional

Table 136

Contnl ofAttach Request message

* * * * * * *

The NAS Key Se1 Identifier (KSI) is used 10 idcntily thc sccurity panmeters for aulhenlication. integrity proteclion and ciphering. Security is not activated at this poinl in tjmc when scnding the Attach Request mcssage within an RRC Conncction Sclup Complclc mcssage so the KSI information element is nol rclcvant

Ihc Old Clobaliy Unique Tcmporary IJE ldenliry (GUl'l) or IMSI inlormation clement provides the nctwork with an identity for thc UE. Tbe GUTI can be dcrived lrom a previous P--I MSI and the associated RAI iflhcy are avaiJable. The IMSI is oniy sent if a GUTI js not available
['hc UL Nctwork Capability provides information regarding the encryption and integrily proteclion algorithms supporled by thc Ull. It also signals whethcr or no1 the lJIi has a prelerence for thc dcfauit alphabel over the Universal Chamcter Set (UCS) 2. Support lor Single Radio Vojce Call Continuity (SRVCC) is also indicaled The trSM Mcssage Container is used 10 include a PDN Connectivity Requost message. Ihe PI)N Connectivity Requesl is another NAS mcssagc, so one NAS message is transf-erred within another NAS mcssage. The contenl olthc PI)N Connectivity R(-quest message is shown in Table 137 The llrst 4 information elements within the PDN Conncctivity Requesl message represcnl the message header. 1he Prolocol Djscriminalor;ndicates thal the subsequent rrcssagc is an DPS session managcment message The main content ofthe I']DN Connectivity Requcst message starts with the Requesl Type which can bc configurerJ wilh values of'lnilial Rcqucsl' or 'llandover'. The 'Handover' value can be used lor an incoming inter-system transition from another lechnology The PDN Type indicates the IP capability oflhc LIE. It can be signalled using valucs oflPv4, IPv6 or lPv4v6. The IPv4v6 value indicates that thc Ull suppods the dual stack configuration which uscs both lPv4 and lPv6 address allocations

(LTE) -ONG TERM EVOLUTiON TheoptionalF,sMlnlormationlransferFiagisincludcilif'thet]Ijhasprotoco]configuralionoptionsthalnecdtobe to to provide an Access Point Name (APN) for the PDN conneclion

fanstbrred securily protected. ot ,r the

point Namc infomralion clemcnt is always excludcd u'hen establishcd during wilh,in an Atlach Rcqucsr messaFL" i.c. thc Al'N is translerred during a the pDN Conncctivity Requcsr messlle i i""rl,a.a alier securily Transler olthis information is deiaved to allou its transfer subsequcnt DSM Infonnarion n"q";;i;;;;;; has been cnabied. i.e. to allow ciphering ofthe content
Informatioo Elements
P rol oc o I D i scr im

t.ll ,iishes the attach prn""au-.;ii. optio.al Acccss

be

Prescnce

ifial

t
n I i ry

Mandatory
Mandatory

EPS

Bealer ldentllY
on I de

P / oce(lue Tr ansacli

Mandatorl,
Mandatory Mandalorv Mandatory

PDN CotlnectNitj Reguest Message ldenliry

I{ccuest l"vPe
PDN Typc ESM Information Transfer Flag
Accss Point Name

()ptional
Optional Oplional

Protocol Confi guration L)Ptlons

'l'abl

137
Lo

Content ofPDN Connectivity Requcst messagc is

'l.heUEstartstimerl.34l0allelsendjngtheAttachRequcslmessage.3Gl,Phasstaldardisedafixedva]ueofl5slorthc
T3410 timer. tf T3410 expires prior
less message once'f3411 has cxPired

ire ll E recciving a rcsponse from the MME. then the currenl attach atlempt aboltgdaldtheattachattcmptcountisincrementct]uyr.rleunstaltstimerT34llifthergsultantattachancm|tcountiS for the T34l I timer. The UFI re-lransnlits the Attach Rcquest than 5. 3Gpp has standaraiseo a itxea value of 1d s timer'f34!2, ard deletes its GUTI. TAI and list ofequivalent PI-MN' T3402 timer. The network can signd a differenl value lor 3Gpp has standardised a aefautt vatr]e oi i2 minutes for the .13402 messages. A value signal)cd by the nctrvork is only within thc Attach Accept anJi racking Area Update Accept re-acloptcd ifthc UE recejves an Attach Acocpt default-valu^e,is arr","t ur"rrign"a i.u"tin! ar."r. i'he value The atlach procedure can be rc-iniliatcd a l'3402 not specify "ppli*or.'*irlri, or Tracking Arca lJpau," a"".prn-'"rru!-" *rt-i.t ao", If the atlach attempt count
reaches 5, thc

tlll

starts

once T3402 expircs

IoncelheeNodBroceiveslhcRRCConnectionSefupCompletemcssage'theAttachRequestmessageisexfactcdand protocol (S l -AP) Iniiial t.lE Message. ',l:he content of this message is presented in ]'able placed within an S I Application and ccll Global j/t t6t wjtbtnsecrion 2j.I . Th. .N;i"";;;;l"dc; iniomdtion rcga-rdirg thc rracking Ara ldntity OAI) t 1o thc MMF Messago uE the lnitial forward to procieds B hc cNode
Idenlity

(ccl).

The S-TMSI can also ue included.'t

the IMSI belonging to the UE The IMSI may have once the MME has receivcd thc Attach Reque st message. it dclermines HoI*-"l: if rhe uE included an old GUl l inslead of an IMSI bcen included expJicitly within tle airach Rcqucst mes-sag1 -olthc old MMr (or sGSN) to which the uE.was previously thcn thc MME uses the old ctJ I L" iJ""ttri rir. address to the.otd MN4E @r SGSN) asking for the IMSI. If the MME registcrerl. l-he MMll then ,"na, unia.niity ncluesr messagc its IMS1 The signalling this a;priaoh, an taentiry i.equest is sent to the UIr asking for cannot delermine the IMSI using uscd to determine the IMSI is not shown in Figurc 109

l.heMMLcanthcncompleteauthenticationandNASSeculitysefup'AuthenticationiscompletedusinganEquipment security setup is used to enable ii""ilry n"girr* rEIR) whioh can be connected to the MME using thc S13 interface. lor authentication and N A S securitl ering to-, a;f ruur.qu"nt rigno'ing. fhc sigalling used integrity protcction ana "ipt in Figure 109
setup is no1 shown

iil';r:il,;i#;;;,i"q*;i.;;"".d";;

'l'ransfer I.lag within the PDN connecliviry Requcst If the uE included the rsM Informalion

mcssage, thelMMFl-inilialcs

iH"iffiil:;:ue"i*ril'n

::ffi;Hil'"nffi'.';;T;ili;;;;;;ie""iii"s

RRC rru,.'rpo.t-'nessases between thc MME and eNode B, and wirhin inlormaliion transler messages bet\Yeen the cNode B and IJB

rhisproccdirrcallowsthcuFro-rrovidcanApN":.t:l] ^__i:v,l]:::":] r""1'" ESM Inrormation *":.""'^'.ll:-":1i':-':.',1"J"":11.',t11:

ir-.,iilNa3

l3;l*

IN BULLETS

s
UE

"N"d"B

ql
5F I

[,,IME

q@
c,i!,lr F ,q e5i

Se.ving Galeway

PDN

Wi'

Galeway

s#*"'

llll(,1 Cenne(lroi Se1!p Coilpl.i{e

/\liaah il.]llLesi l P0N Conneciivliy ReqLregl

fr-rN cuIrrL

Downlink NAS Transpod / ESM lnformation Request

Uplink lnformation lnsfer / ESM lnformation Response

Upllnk NAS Transport / ESM lnformation Response

Crea{e S-.sercfl

Reques{

Figure

ll0

Additional signalling for the fiSM Information Requcst procedure

Th(r content o f lhc IISM Infbrmation Request and ESM Infbrmation Rcsponse messages is prescntcd in I'ablc 1 3 8. 'l he rcquesl nlessage scrvcs as a simple prompt which triggers the IJE lo rclum a responsc. The response mcssage can inclucle an Acccss Point Name (At'N) and a set of Protocol Configuration Options. 'l'he protocol configumtion options can define the uscrname and password lor the AI)N
ESM lnformatjon Request Information Elements
Presencc
I

ESM lnltrrmahon Rcsponsc nforrnation Elenents

Presence

Plolocol DBcriminalor
EPS Bealer ldehlit,,
P r oce dure Transact i an lde
n Ii

Manda/try;
Mandatory

Pralocal Discrimnalor
EPS Bedrer
P r oc e du re

,Vandalary Mandgtory Mdndalory

ldentitv

l|

Mandalory Mandalon,

7i an sac t i on ! de nt i^,

ESM lnformation Request i4essage ]dentitr-

ESM lnformalion Respo se Mess(tge \denti4) Acccss Point Name

Mandalory
Optional Oplional

Protocol Configuration Options

Table
-i

138

Clontcnt of ESM Information Request and ESM Infornation Rcsponse mcssagcs

he dcf'ault AI'N can bc uscd ilthe tJL did not inciudc thc ESM lnformation 'Iransfcr Flag within the pDN Connectivity Requesl message. Oncc thc MME has linalised the APN to be used, it scnds a Creatc Session Requesl message to lhc Scrving Gatcway. This message beiongs to the Cl'P control planc protocol (GTPv2-C) ard is specificd within 3Gpp TS Tbe Serving Galeway creates an en1ry within its EPS Bearer table and forwards the Create Session Request mcssage to thc PDN Gatcway. 1-he PDN Gateway creates a new entry wilhin its I]PS llearer Contexl lablc and gcnerates a charging identiry. 'Ihc new context allo\a,s the PDN Gateway 10 slart rouling user plane data between the Packct Data Nctwork (l'DN) and the Serving Galc\\,ay, and to start charging
'l he PDN Gateway relurns a Crcatc Session Responsc mcssage to the Scrving Gateway. This mcssagc includes the lP addrcss that has been allocalcd to the UD by the PDN Gatervay, i.e. thc PDN Gatcway is responsible for managing thc allooation of lP addresscs

AP injtial context setup proccdure. This is done by sendjng an lnitial Contoxl Setup Request message to thc eNode Il. The content ()1'the lnitial Context Setup Rcquest mcssage is prcsented in l'ablc 139. It allows the cNode Il to confisure itself for the new E-I{AR

The Serving Gateway foru'ards the Crcate Session Rcspons messagc to the N4MD, rvhich then proceeds to initiate thc

l-

I,ONG TERM EVOLUTION (LTE)

lnformalion Elements
Message Type

MME UE S|AP ]D
eNB UE S|AP ID UE Aggrcgate Maximum

llit

Rate

E-RAB to be Setup List

E-RAB to be Setup

E-RAB ID

F-IIAB Level QoS Parameters

Tra{Nport Layer Address GTP TEID

NAS PDI]
UE Security Capabilities Security Key
Trac Activation

Handover Restriction List UE Radio CapabilitY

Subscriber Profile ID for RAT/Irequency Priority

Cs Fallback lndicator
SRVCC Operation Possible

Table 139

Content

oflnitial Contexl

Sefup Requesi message

The llE Aggegate Maximum Bit Rate (UE-AMBR) defineslhe maximum aliowd throughput for a [lE ba-sed upon the sum ofalliti non-GBR bearers. This parametcr forms part ofthe QoS profile described in seclion 2.9. It can be configured with values between 0 and 10 000 Mbps, and can be specified independently for the uplint and downlink The E-RAB Level QoS Parameters include:

o o o o

QoS Class ldentifier (QCI)

Allocation and Retention Priority (ARP)

Guaranteed Bit Rates (GBR)

Maximum Bit Rates (MBR)

These paramcters form part ofthe QoS profile descdbed in section 2.9. The relationship between QCI and its associated intended for the default bearer. QCI 8 can be used for eoS pirameters is presented in Table 5. QCI values of 8 and 9 are premium subscribers, whereas QCI 9 can be used for basic subscribers. The GBR and MBR paramete$ are only applicable to GBR bearers 'I'he transporl layer address defines an IP address which can subsequently be used for tmnsferring user plane data from the eNode B to the Serving Gateway The GTp Tunnel Endpoint Identifier (TEID) defines the GTP-U tunnel for the user plane data. Multiple tunnels the same transport layer address

will

share

The Non-Access Stmtum CNAS) PDU is used to tuansler the Attach Accept message which acknowledges the original Attach Request message. The MME slarts timer T3450 afler sending the Attach Accept message. 3GPP has standardised a fixed value of 6 s for the T3450 timer. IfT3450 expires prior to the MME rceiving a response from the UE, then the Attach Accapt message is resent. The Attach Accept message can be re-sent four times. The overall attach procedure is aborted ifT3450 expires a fifth

time
The content ofthe Atlach Accept message is shown in Table 140. The first 3 inlormation elements within the Attach Accept mcssage represent the mcssage header. The Protocol Discriminator indicates that the subsequent message is an EPS 'l mobility management message. lts value is specified within 3GPP 24.007. The Security Header ype indicates whether or Accept Message ldentity The Attach indicates that the message not the NAS message is integrily protectsd and ciphered. itselfis an Attach Accept

IN BULLETS

Information E melts
Protoco I Di scr iminal or

Paesence

Mandator-v

Seartq lleader

Type

Mandatory

Attach Accept Message ldediy)

EPS Attach Result

Mandatolv Mardalory
Mandatory

T3412Vafue
TAJ List ESM Message Container

Ma.dalory
Mandatorv Optional Optional Optional Optional Optional Optional Optional

GUTI
Location Area Idefl tifi cation MS ldentitv

EMM Cause
T3402 Value T3423 Yaluc Equivalent PLMN
Emergency Numbr
EPS

List

Optional Optional

Network Feature Support Table 140

Content ofAttach Accept message

* * *

The main content ofthe Atlach Accept message starts with the EPS Attach Result which can be configured with values of 'EPS only' or'Combined EPS/IMSI Attach'. These values correspond to EPS Attach Type specified within the request
messagg

T3412 defines the periodic Tracking Area Update (TAU) timer. UE lriggcr a periodic TAU procedure when this timer expires. It can be configured with a value up to 186 minutes
The Tracking Area Identity (TAI) list defines the set ofallocated tracking areas, i.e. the tracking areas with which the UE is registered within. The TAI list can include tracking areas belonging to more than a single PLMN when a shared network is being used. Tracking Area Updates are subsequently higgered ifthe UE moves into a tracking area which is not included within the TAI list

* * '*

The ESM Message Container is used to transfer the Activate Defauil EPS Bearer Context Request message which represents a response to the PDN Connectivity Request message. The conlent ofthe PDN Connectivity Riqucst message is shown in Table 141
The first 4 information elements within the Activate Default EPS Bearer Context Request message represent the message header. The Prolocol Discriminator indicates that the subsequent message is an EPS session manigement message The EPS QoS parameter defines:

o o o

QoS Class Identifier (QCI) Guaranteed Bit Rates (GBR)

Maximum Bit Rates (MBR)

These parameters form part ofthe QoS profile descdbed in section 2.9. The relationship between eCI and its associated QoS parameters is presented in l-able 5. The GBR and MBR parameters are only appliiable to GBi bearers. The Allocation and Retention Priority (ARP) has been signalled to the eNode B but is not signalled to the UE, i.e. ARp values are used by the network rather than by the UE

* * *

The Access Point Name (APN) inlorms the UE ofthe APN to which the default bearer is connected The PDN Address allocates the UE with an IP address The eNode B exhacts the Attach Accept message from within the Initial Context Sctup Requesl., and packages it within an RRC Connection Reconfiguration message. The RRC Corurectioo Reconfiguration is iransferred to the Ulr across the airinterface. This message provides the UE with all ofthe information necessary to establish the default bearer

':?t
LONG TERM IVOLUTION (LTE)
Information lilemnts
Protocol
EPS

Presenc

Discrihi alor
llantlorory
Mandalorf
Mandatorv Mandatory Mandatory Optional Optional Optional Optional Optional Optional Optional
Optronal

Bearer ldentilY
ate DeJauh EPS Bearet Conlext Request Message ldentity

Prccedwe Transact ion ldenlilY

Acl

EPS QoS

Access Point Name

PDN Addrss
Transaction Identifier

Negotiated QoS Negotiated LLC SA?l

Radio Priority Packel FIow Identificr

APN-AMBR FsM Cause

Protocol Confi guration OPtlons

Table 141

Contcnt ofActivate Default EPS Bearr Context Rcquesf message

messagc.'lhis message is a simple The IJE responds to the eNode B using the RRC Conneclr'on Reco_nfiguration completc NAS messagcs so thc llll has to tnnsfer ability to acknowledjement without any inlormllion contcnt. lt does not oiler the message Transfer send the Aiach Complete within a subsequcnt Uplink Information ResPonse l.he eNodc B completes the S I -AI' Iniliai Contcxt Setup proccdure by forwarding an lnitial Conlext Sctup for th(r dcfault thc FI-RAB that mcssage to the MME. The content ofthis message is shown in Table 142. It acknou'ledgcs data for downiink lP address in lenns of an provided bearerlias been successfully sclup. A transport iayer address is to define provided ('lElD) also is ldentitier Endpoint transfer from the Scrving Gateway to the eilodc B. A GTP Tunnel setup failed E-RAts if the is specified the GTp_u tunnej for thi user plaae data. A failure cause
Informalion Elemgftts
Message Tjpe

MME T]E SIAP

]I)
E-RAB Sctup Ilem E-RAB ID
'I ransport Layer Addrss

eNB UE Sl)P ID

E-RAB Sclup List

(iTP 'I'EID E-RAB Failed to Setup E-RAB I"ist

E-RAts ID
Cau,se

List
Crilical ity Diagnostics

'Iehle 142 - Cootnt oflnitial Contcxt Setup Response message coniains an A11ach complsle messagc is shown in Table 143. lt is a simple acknowledgement but also Contcxt EPS Bearcr I)efault FlpS Session Management (ESM) NAS meisage. The IrSM NAS message is an ActiYate Accept mcssage

l he content olthe

Information Elements
P r o lo c o I D i s cr im i nator

Prssenca

Mandatory Mandatory

Securtly Header TyPe Anach Complete Messdge ldentilY ESM Mcssagc Clontainer

Mand.ttory
Mandatory

'l'able 143

Content ofAttach Complete message

IN BULLETS
The content ofthe Activate Dcfault Eps Bearer contxl Accept mcssage is shown in Table I44. It is another simple acknowledgement but may aiso contain some protocol config;ration options
lnfornratriQn Elements Pr o I ocol Discrimi nat or
EPS Bearer Presence

Maadatory Mqndatory
Mandatorv

ldentig

P roce dure Transacuon I de nt t ty

Actiyale Defdult EPS Bealer Coktext Accept Message (dentity Protocol Configuration Options Optional

Tabte 144 _ Content of Activat Default EpS Bearer Cohtext

A"lT,rgT"g"

After receiving both the Initial Context Rcsponse and Attach Accept messages, the.l ;de.b,ends u Modily Bearer Reqlestmessag to thc Serving Gateway. This message belongs tothe GTicont.ot plane protoJ 1cin.,nz-c;. lt prou;0., the Serving Gateway with the downlink transport layer address and the associated Gip rBro, Both ofthese are taken liom lhe S l-AP lnitial Conlexl Setup Response message
The Serving Gateway completes the procedure by sending a Modify Bearer Response message to the MML..l.his messagc is a simple acknowledgement 3GPP References: TS 24.301,T5 23.401, TS 36.413. TS 29.274

LONG TERM EVOLUTION (LTE)

23.3 DEDICATED BEARER ESTABLISHMENT

* >t
A dedicated bearer is required if tbe end-user requires a different Quality ofService (QoS) to thal offered by the default bearer, or ilthe end-useirequires connectivity to a different Packet Data Network (PDN) to that provided by the default bearer. Dedicated bearers are configured to run in parallel to the existing default bealel
The dedicated bearer establishment procedure is initiated by the network but may be requested by the l lE- The UE can request a dedicatd bearer by sending a Non-Access Stratum (NAS) Bearer Resource Allocation Request to the MME. The UE shrts the T3480 timer when sending a Bearer Rsourcc Allocation Request message, The message is re-transmitted ii T3480 expires prior to the UE recciving a response from the MME. 3GPP have specifid a fixed value of 8 s for the T3480 timer. The Beaier Resource Allocation Request messagc can be re-transmitted a maximum of4 times before the overall
procedure is abofted The signalling associated with dcdicated bearer establishment is shown in Figure I I I

UE

[ll

MME

{g

qp"
E-RAB Setup Request / Activate Dedicated EPS Bearer Context Reqirest

Serving Gateway

PDN

Gateway

qpe
1

SP
Create Bearer

Create Bearer Request

RRC Connection Reconllguration / Activate Dedicated EPS Bearer Coniext Request RRC Connection Reconfiguration

E-RAB Setup Response Uplink lnformation TEnsfer / Activate Dedicated EPS Bearer Context Accept

) Uplink NAS Transport Activate Dedicated EPS Bealr Context Accept

Figure I

l1-

Signalling for the dedicated bearer establishment procedure

The pDN Gateway starts by sending a Create Bearer Request message to the Serving Gateway. This message belongs to the GTpv2-C protocol so is specified within 3GPP TS 29.274. It includes a definition ofthe dedicated bearer QoS requirernents, i.e. eoS Class ldentifier (QCI), Allocation and Retention Priority (ARP), Guaranteed Bit Rate (GBR) and Maximum Bit Rate (MBR). It also specifies the uplink GTP-U tunnel endpoint address at the PDN Gateway. This Tunnel Endpoint Idsntity (TEID) defines the GTP-U tunnel to be used by the Serving Gateway when forwarding user plane data to th. iDN Gut"*iy. The Create Bearer Requcst also includes the identiry ofthe default bearer so the dedicated bearer and default bearer can be linked. Protocol configuration options can be included to transler application layer parameters between the PDN and UE. These parametrs are sent transparently through the Serving Gateway and MME The Serving Gateway generates its own version ofthe Create Bearer Request message. The content is similar to that received from the PDN Gateway but the Serving Gateway replaces the uplink GTP-U TEID at the PDN Galeway with an uplink GTP-U TEID at the Servjng Gateway. The MME is responsible for forwarding this TEID to the Node B to allow the eNode B to forward uplink user plane data to the appropriate address within the srving Gatevr'ay
The MME generates an E-RAB Setup Request message which encapsulates an Activate Dedicated EPS Bearer Context Request meisage. The E-RAB Serup Request bclongs to the Sl Application Protocol (Sl-AP) so is specified within 3GPP TS 36.413. The Activale Dedjcated EPS Bearer Context Request belongs to the session management component ofth Non-Access Stratum Q.qAS) protocol so is specified within 3GPP TS 24.301. The content ofthe E-RAB Setup Request is

shown in l'able 145

228

IN BULLETS
lnformation Elemenls
Message Iype

MME I]E SIAP ID

eNB tJE SI AP JD

UL Aggrcgate Maximum Bjt Ratc E-RAB

10

be Sctup

List

IiRAB to be Setup

E.RAB 1D

E-R B Ler'el QoS Parameters 'f ransport Layer Add.ess

GTP TElI)

NAS PI]U Tablc

145

Content of Ii-RAB Sctup Request messag

1'he UE Aggregate Ma:rimum Bit Rate is used to update thc value currently appiied by lhc eNode Il. This paramctcr defines a maxirnum total throughput for all non-GBR bearers bclonging to the UE. 'I'he FI-R-AB QoS parameters arc based upon thosc originating lrom thc PDN Gateway. Thc GTI'l FllD conesponds 1(] the uplink tunnel specilied by thc Scrving Gateway. 1he transpofi Iayer address idenlifics thc Serving Gateway itscll

The NAS PDtl within the E-RAB Stup Itequest corresponds to thc Activate Dcdicated BPS Bearer Context Request. This messagc is directed 1tl the UE mther than the eNode B so thc cNode l3 is rcsponsible lor forwarding it across the airinterface. 'l he content oflhe Aclivate Dedicatcd EPS Bearcr Context Rcquest is shown in'l'ablc 146 InfoImation ElemenLs
P r o I oc o I D tsc r im i1a
!

Presence

or

Mandaton, Mdndato.t^ Mandotorv

liP:i Bearer ldcntt)

Prcced re 'l run\action ldentitv
Activdle Dedrcaled tJ'S ]ledrer Conlett Re(luast Message ldentily

Mandalory
Mandatory Mandatory Mandatory Optional Optional Optional Optional Optional Optional
message

Linked FPS Bcarcr ldenlitv

FPS QoS

1'FT

lraflsaclion Idenlificr
Negotiated QoS

Ncoolialcd

1.1

.C SAPI

Radio Priorily
Packet Irlow

ldcnlilicr

Protoool CooliSuralion C)plions

'l'ahlc

146

(lontent ofActivate Dcdicatd [pS Bearer Context Request

The linked EI'S bearcr idnlificr is used to link thc dedicated bearer to fre dclauil bcarer. The QoS irlformation wilhin the Activalc l)cdicated EPS Bcarcr Context liequest js similar to that within th(r E-ltAB Setup Request bu1 jt excludes thc Allocation and Iletcntjon Priority (ARP) informalion. ARP is used b), the nctwork rilther than the llll so is not sent to the tJlr. Thc Traffic Flou'Tcmplatc (TF]-) defines a sat ofpackct filtels for thc IJE to app)y in the uplink direction. I'hesc fil1crs can bc bascd upon various criteria. including source and destination porl ranges. lype of servicc. remole address lypes and protocol identifien Thc cNode B uscs the Ir-l{AB Setup Ilequest to oonfigurc itself for the dedjcatcd bearer. It also exlracts thc Activale Dedicated FIPS Bearer Conlext llequest and packages it within an RRC Connectjon Rcconiiguralion ntessagc belore lorwarding to the UIl. l'hc RRC Conncction Reconfiguration mcssage belongs to thc RRC protocol s6 is specifiecl within 3GPPTS36.331. Ihis message providcs the L]E with all ofthc information nccessary ibr ir to oonfigurc itself for the dedicated RA-B. It is lranslerred across thc air-interface using SRB I and acknowledgcci modc RLC The []E acknowlcdges rcception ol the RIIC Connection Reconfiguration message using the RRC Connecljon I{econfiguration Complete mcssalte. 'l'his nrcssage also acknorvlcdges that the LJFlhas applied the configuration for the

LONG TERM EVOLUTION (LTE)

acknowledgcmenl and is not able dedicated bcarer. The RRC Connection Rcconfiguration completc messagc is a simple IPS Bearer Conlext Rcquest bas Dcdicated Actiyate lor the response ihc that means to transfer any NAS signalling. This messagc lo bc scnt in a seParale

responds to th E-RAB Setup Request Oncc the cNode B has received the llRC Connection Reconfiguration mcssage, i1 in'l able 147. It provides the MMts is shown this mcssage of l-he content from the MME using an E-RAB Setup Response. user plane data (TEID) the downlink for ldentib' En<lpoint with a transport layei address and GTP-U Tunnel Informalion El9me nts
Message Type

MME UL SI/lP JD
eNB UE SIAP

ID

E-RAB Sctup

List

E-R-AB StuP

II.RAB ID
Transport Layer Address GTP TEII)

Criticality Diagnostics Table 147

Content ofE-RAB Sctup Response message

'l'he UE gcnerates an Activate Dedicated EPS Bearer Contcxt Accept message to respond to the Activate Dedicated EPS 3GPP TS 24.301. Bearer C-ontext Request from the MME. This message belongs to the NAS protocol so is specificd within message Transfcr Information Uplirk within an message NAS packages the UE 148. The Table in Its content is shown LJplink NAS an Sl-AP before sending it to the eNode Il. The eNode B cxtracts the NAS messagc and packages it within Transport mcssage before sending it to the MME
lnformation El{]ments
Presenc

Ptotocol
EPS

[)6cri

inator

Mandatory Mondalory

Bearer ldentitY Trarsaction I de nli lY

P roce dwe

Mdndalory
Mandatom Optional

ActNate Dedicated EPS Bearer Conrext Aclapt Me\sa}e ldenfily Protocol Configuration OPlions

Table I48

Contellt ofAclivate Dcdicated EPS Bearer Context Accept messag

The MMD then uses the GTpv2-C protocoi to respond 10 the Serving Gateway by sending a Create Bearer Response. This plane data, i.e it allowsthe message provides thc Serving Gateway wilh thc G fP-U tunnel identity fbr the downlink uscr providcd MME with this information within the B l-he eNode eNodc B. to tbe data to forward"rlownljnk S".uirig Gut"*uy
the E-RAB Sctup Response the PDN The Serving Gateway compJetes the proccdure by sending its own version ofthe Create Bearel Responsc to th PDN Gateway so allows Gateway at the Serving identity tunnel GTP-tl Gateway. ihis u"rrion includcs the downlink to transfer downlink data 1o the Serving Gateway 3GPP References:

'fS 36.413' TS 29.274. TS 36 33 S 24.301, TS 23.401.

2?O

IN BULLETS

23.4 TRACKING AREA UPDATE

].Iacking Area Updales (TAIJ) become applicabie afler the UE has completd the Attacb procedure and moved into the EI'S MobiJity Management (EMM) I{EGIS'I ERED state. They can be triggered ir eithcr RRC ldle mode or RRC
Connected mode, but the UE must be in RRC Connecled mode to aclualiy complcte thc procedure

The

l'Atj

procedure is used for:

normal TAU due to mobility. j.e. when the UE entcrs a hacking area which is not included wilhin thc li$ oltracking areas with which the UE is rcgislcred

periodic TAU alter the T3412 timer expires. The vaiue of T3412 is initialised during the Attach procedurc within tho Atlach Acccpt message shown in Table 140. Periodic TA{J confim to thc network that the UE is still present
rcgislering with thc CS domain for non-EPS services when the UD is already atlached for EPS services. This invoives complcting an IMSI attach as part of the I AU procedure registering wil.h the EPS after an incoming inler-system change, e.g. reselecting the LTE network after being camped on the lJMl'S network o
o

re-registering with the EPS aflcr a CS fallback connsction has been completed

MME load balancing. The UE initiates

TAU proccdure ifthe eNode B releases its RRC cornection using

a cause

value of'Load Baiancing TAU Rcquired' updating the UE specific DRX cycle. UE tlre allowod to select their own DRX cyclc and signal it to the MME. The selected DItX cycle can be specified within thc Tracking Area IJpdate Requesl messago

the I

indioating that a IJE has sclccted a Closed Subscriber Group (CSG) cell whose CSG ldcntity is not included within lll's allowed CSG lisl

The TAU procedure may involvc a change ofScrving Gateway and/or a change of MME The signalling associated with the TAU procedurc is illustrated in Figure 1 12. exampie includes a change of MMI; bu1 mainlains the same Serving Gatcway. The example assunres that the UFI starts in RRC ldle mode so the Tracking Area Updale Request is sent wilhin an RRC Connection Setup Complete message. lfthc U[ is already in RRC Connectcd mode when thlr TAU procedure is triggercd, thc'l'racking Area Update Request is scnl within an lJplink Inlormation Transfer in0ssage

-fhis

l'he Utl s1ar1s timer'I'3430 afler sending thc Tracking Area Update Requcst mcssage. 3GPP has standardised a fixed value of I5 s for the T3430 timcr. IfT3430 expires prior to the UE receiving a response from thc MME, thn the curent TAU attcmpt is abortcd and the TAU attempt count is incrcmenlcd by l. The UE starts timer T34l I ifthe resultant atlempt oount is lcss than 5. 3GPP has slandardised a fixed value ol l0 s for the T341 I timer. The UE re-transmits the Tracking
Area Update Request message oncc T34l

has

expired

If the TAU attempt count reachcs 5. the UE slarts timcr T3402. and deletes i1s lis1 of equivalcnt PLMN. 3GPP has standardised a default value of I2 minutcs for thc 'l'3402 limer. The network can signal a dillcrent value lor T3402 within the Aflach Accept and Tracking Area Update Accept messages. A value signallcd by the network is onJy applicable within thc sct ofassigned Tracking Areas. lhe default value is re-adopted jfthe UE receives an Attach Accept or'l racking Area Update Accept message which docs not specify a T3402 valuc. The IAU procedure can bc re-initiated once f3402 cxpires

231

I,ONG TERM EVOI,UI'ION (LTE)

UE

"r"... 1[
/ Request
i

New

ord
I\.4ME

'I

ffi
lnrtial UE Message

w'
M[,1E

Servlng Galeway

HSS

W!tr'

sw.

RRC Connectlon Setup Complete rack nq Area Updaie

'I racking Area UPdate Requesl

Context Response

Modify Bearer Request

Downlink lnformation Transfer / Trackinq Area uPdate Accept

Downlink MS Transpod / Tracking Area UPdate Accept

I
llll

Update Location Acknowledge

/ r rirrrsrcr / tlollnK lnrormallolr Transfer Uplink lnformation Trackrnq Area Update Co'nplete

Uplrnk NAS Transpon / Trackrng Area UPdate ComPrele

I,igurc l l2

Signalling for thc 'I'rackiDg Area'Ilpdstc (TAtJ) procedure (with changc of MMII)

Table 149 The contcnt ofthe Tracking Arca Update Request mcssage is shown in
the message header. The lirst 3 inlormaljon elcments within the Tracking Area Update Requesl message rcpresent value is message managemcnt mobility EPS is an protocol Discriminator indicales that the subsequent mossage .lts protccted integrily is NAS mcssage not thc or whcther ype iidicates .p""ifi"d *i,hin 3GPP 24.007. Ihc Securiry Header'l 'l
.l"he

Updatc Request
EPS Update Type rvhich can bc configurcd The main content ofthc l'racking Area update Requcst message starts with the .I TAn-A Updating with 1MSI Atlach' and with values of A Updating'. 'C--omt incr] tA,rla iJpdating', 'Combincd .ttrio,lic Up,lating'. i'tr" 'rx Updating' valuc is ussd ifthi UE is only rcgislercd with thc I,PS' i e onll'rcgistered 1br PS ,coirbined TA/I-A Updaiing' value is usctl ifthe tJE is registcred for both EPS and non-EPS scn iccs, I c scr.,iccs. l.he .Cn.bin"d:l,q"rt.a tJpdating with IMSI Attach' value is used ifthc U!) is rcgistercd for EPS pS senices. The borh CS and whcn thc T3412 timcr seniccs but wishes to also register lor non-EPS servjces. Thc 'Pcriodic Updating' value is used expircs parameters for authcntication, inlegrity protcction and The NAS Key Sct Idenlilier (KSI) is used to identjly thc security 'l Rcquest mcssagc within ciphcring. Sccurity is not activaled at thjs pojnl in time whcn sending the racking Area Update relevant is no1 elemcnl inlbtmation Setup Complete message so the KSI

-a

lipn"r"a.

.l

ilself is an he Tracking Area Updatc l{equest Mcssagc Idcntily indicates that the message

racking Arca

un

nnCi:onn""tinn

'fhe old Globally unique lemporary tJE Identjly (GUTI) inlormation elemenl provjdcs thc nelwolk with an identity for ifthey are availablc the UE. l he GUil can bs derivcd lrom a previous P-TMSI and thc associatcd RAI
Trucking Area Updatc Requcst message is Once the eNode B receives the I{RC Connection Setup Complele mcssage, the

jnformalion regarding thc ne w liacking Area ldentitv iir' in ,..,ton'z:. t . Thc e Nodc B includes ;;;;J;;;';;"-J;6. Thc eNode B proceeds to forward thc Initial tlE inciu6ed. be can also IMSI r'rre S(TAI) and Ccll clobal Identity (ccl). change of MME) Message to tire new MME (this examplcs assumcs the TAIJ procedurc involves a

cxtracredandolacedrvithinan5lApplicarionProiocul

{\l-Al')

lnrlial

Ul

\4e:sats( lheconl'"nt ol thismes'ageis

IN BUI,LETS
Info.mation ElemenG Protocol Disctimirnlor
Prsenca

MandatoO,

Securit! Header Type 'frachng Area Updale Reqlast Message ldentity

EPS Update ]'ype

Mandatory
Mamiato4', Mandatory Mandalory Mandalory

NAS Kcy Sct Identifiel

OId GIJ'II

\('n-(

urrcnl Nati\ e Nn S

kc) sct ldcntil'cr

Oplional Optional Optional Optional Optional Optional Optional Optional Optional

CPRS Ciphcring Key Sequence Numbcr Old P-TMSI Signature

Additional (iUl'J
Nonce I lF

Ull Netrork Capability

Lasl Visjted Registered TA.1

f)RX Parametor
UJ.l Radio

Capabilily Inlormalion Update Needed

FPS Bcarer Contcxt Status

Optionrl
Optional Oplional Optional

MS Nelwork Capability Old Location AJca ldcntification

TMSI Status Mobile Stalion ClassmaJk 2 Mohile Station Classmark

Supported Codeos
3

(lnli(lnal
Optional Optional

'Irhlc

149

Content ofTratking Area Update Rcqucst mcssagc

'i he new MME uscs rhe old GUTI inlomation ftom $'i1hin the'Imckjng Area Updatc Rcqucst to dcrjvc the addrcss o1'1he old MME. Thc ncu' MME then scnds a Conlcxl Rquest mcssage 10 the old MME. This mcssagc bcJongs to thc GTP conlrol plane prolocol (Cill,v2-C) and is specilled within 3GPP 1'S 29.274. lt is used to request user inlbmration liom thc old MMt.

Thc ncu MMFI responds u ith c (-ontcxl Rcsponse message which includes thc re qucslcd tJE infolmation. l he new MMB iinaliscs thc 3-u,ay handshakc b,v sending a Context Acknowledgc mcssagc to thc old MMI1. l'his triggers the old MMI'i to mark its galcway and lJomc Subscriber Scrver (l ISS) inlormalion fbr thc UII as jnvalid. I'he context ilseifis mainlained and is no1 deletcd at this stage The nerv MMI sends a Modili Bearer Requcst ncssage to the Serving (iatcway. This message also belongs to thc GTP controi plane proroool (C;l l,v2-C). I1 inlorms thc Scrving Gateway thal the MME a-ssociatcd with the existing PDN oonneclion has changcd. Addilional Modilj,Bearer Rcqucst mcssages are sent ifthe IJE has multiple I'jDN conneclions. l he Serving Galeway acknowlcdgcs the ncw informalion using the Modiiy Bearcr Rcsponse m(jssage
'I'he neu, MMI1 thcn proceeds to send an [Jpdale Location Rcquesl message 1() the l lSS. 1'bis message belon]s to the l)iameter protocol and js specified wjthin 3GI'l' TS 29.2'12. Thc MMI'. is connecled 1() the IISS using the S6a inlerface. Thc Updatc l.ocation Request identifjcs the LIE by its IMSI and informs the I ISS that the UE has n]oved to the new MME. 'fhe I ISS contacts thc old MME usjng the Cancc] Location mcssage which also uses thc Diameter prolocol. The old MIr4E thcn deleres the context lor the IIE and responds with a Canccl Location Acknowledge. Finally, the HSS uses the tjpdat l,ocation Acknowledge message to confinn to the new MME thal is has updated its records for the L/Fl 'l he new MMll then progressos the'I'AIJ proccdurc by scnding a Tracking Arca Update Accept message to the UE. This 'l message is transferred across the Sl intcrlace using an SIAP: Dorvnlink NAS I ransporl message. he conlenl oflhe lracking Area LJpdalc Accepl messagc is shown in Tablc I50

(LTE) LONG TI]RM EVOI,UTION

lnlolmatlon I

lcmcnlt

D.^'^,,)

Div

rlntn.tlor

Mawlatory Mandat.try

\"-,,t"

Hr"d",

ftr.
ld?nlth

h,.rAing Area L)pJare Acctpr Vctsrqr

EPS Updat Result

Mandatory Optional Optional

'I3412 Valuc
GTJTI

TAI Lisl
I.IPS Bearer Context Status

OIlronal
Optiondl Optional Oplional Optional Optional Optional Optional

l.ocatioo Area ldentifi calion

MS IdentitY EMM Cause 'f3402 Value

T1423 Value Iiquivalen( PLMN
EmergencY Number

l'ist

Optional Ontional

IIPS Network Ircature Supporl

Table 150 .l.hc

message Content of-lracking Area Update Accept

the Tracking Arca Updatc A-cc^epr messagc firs1 3 information clements within lls valuc is jt an EpS mobiliq manage me nt message tnJ';;;;;;.;*ce.is prolocor Discrim jnuto, ina;.ut", t protected is integrity message NAS the not .,n"il;;;;;,1or lype iidicates whether 2.1.007. 3cpp wirhin Area specjfied .fhc Tracking Arca ,ff#;;";il";i# io"",iry indioatcs that the message itse ll is an Tracking and ciphered. Update AccaPl

'fhc refresenl the mcssa!e hcader'

'combincd l A/l.A tlpdatcd" "fA updated and lsR be allocatcd values of 'TA Upilatcd', The Et,s update l{esul1 can (lsR) is applicable to E,combined .'.A/LA ;;;;;;; isR Actirateil'. ldle rnode signalling Reduction Acrivaled, and the Ui-' and the beiu'een signalling ui*N uai"$sarcductionof the tlTRAN UE which ruppo.t cnnai'ii)of the signalling within the netlvork ;;il;, ;;":;ii;;

"

""'ou"rinn l.heMMEStartslimcrT3450allerscnciingthe.I.rackingArgau.pdateAuceFtmessage'3GPPhasStandardiscdafiXcd lit'm lhc UL rhcnthe lraclinp r'-' rhc,MM re ceiving a responsc

\aluror hslorthe 1.1450,it., fr f iqio""toirt'lrioi ArcalpJdleA!cepImcs5agc,.,.-*n,.lhc'lracl'ingAreal'pdaleAcceptrn-es.age(anb(.r(-'enlfuurlitlL...lhctlrerall iau plu..aur. rs ahuned ii'l 1450 expires a fillh t ime slAP message and packages i1 u'iihin an I{RC: "ili;t Accept.tiom within the t.he eNodc B cxtracts the Tracking Area updatc t"ttug" it rttcn scnt to the LJII across the air-interface Inlormation T'ansttr messall
Downlink
messrge to the M Mll This by sending a Tracking ArealJpclate Complelc the The UE completes the ovcrall procedure tiplink IniormaLiot' iran'fer me'sage The rontcnt of mcssase is translerr"a u"ru.r,r," 151 upoale Complere mcssage is shown in Table

uil]iir!;ilil;'RRa,

ir"Jnft^i-,

iiacLing Ated Ufuate Complete l'abl

151

Message

ldently

* *

The'fracking Arca llpdate Complcte

pro,"""LUl.iriminator,
Uplink NAS I ransonn

Update The eNode B extracts the Tracking Area

rvhich only includes header inlormation, ic' mcssage is a simple acknow.ledgement Security HeaiJer trpe and Messagc ldentity packages ir wilhin an SIAP: Cr)mplelc lrum \ ithin the RRC messagc and
the

Content

ofl

racking Area []pdatc Complcte message

rntt'uf Fli' '*t'og" i' thcn scrt tu thc oc\\' MMD across
234

Sl interfacc

IN BULLETS

23.5

INTRA-SYSTEM HANDOVER

Thc intra-system handover procedure is applicable to tJE in the ECM-(IONNEC'I'ED state. UE trigger handovers as thy move from one cell to another. Handovcrs are IJE assisted but network controlled, i.e. LJIi provide mcasurements which hclp thc eNodc B to makc handover decisions

l,TE does no1 support sofl handover so all handovers are hard handovers. Data is forwarded from the sourcc eNode B to thc targel eNode B during the handover procedure to ensure that handovers are lossless
The intra-system handover proccdurc may involvc a changc of cNode B and/or a change of Serving Gateway The signalling associated with the intra-system handover procedurc is jllustrated in F'igure I 13. This examplc includes a change of eNode B but maintains thc same Serving Gatervay. lt is refencd 10 as an X2-based handover because it uscs the X2 interlace between neighbouring eNode B for both control plane signalling and user plane data lransfer

UE

!|r

'

w
RRC Connection Reconfiguration

ry

se

w
Handover Preparation

MIME

Serving Gateway

SN Status Transfer

FoMa.d Use( Plane Data

Handover Execution

RRC Connection Reconf,glration Cornplete

and Downlink U$er Plane Data

User Piane Dala

Handover

Coftpletion
Uplink and Dowrlirk Use..Plane Da{a Uplink and Downlink User Plane Dsia Modify gaarer Raspons

fath Switch RequestAck

Uf
Figure I lJ

Cofllext

Rel$se

Signalling for th intra-systm handovcr proccdurc (with changc ofeNodc B)

l-,.@

LONG TERM EVOLTJTION (LTE)

handover phases: hardovtr pre.paratio":.n""dol:':1-::^"jton and The overall handover procedure is divided into 3 complflion llando\cr rrcr\\ork accerr radiu rhe onll inrol.e ;^ ecur,on compterion. nripi. u,,; ;;; ;;; "^"0.,., thc core nerqorl anLl radlo acccs\ nelworK involle: both

i;".;

)kHandoverpleparatiot]StartswithconfigulingthelJEtosendMeasuremcntRepoflmessages.TheUEcanbeconfigurcdto RRC Connection Reconfiguration

mcasurcment rcpofiing events The send these periodically, or based upon onc or morc Reporr mcssages. l'his messagc, re places the Measurement 'l'hey include: message is u."o rn .onttgui"-ii; u'E'i; ,;;; M""Suremcnr rcporting events are dcscribed in seclion 19 control messagc used biuMl'S. Intra-fiequcncy measuremcnt

o o o o
Events

evenl

Al
-

event ,42 event

scrving cell becomes better than an absoir;te threshold serving cell becomes worsc than an absolutc thrcshold cell neighbouring cell becomes x dB better than thc serving threshold neighbouring cell becomes betlcr than an absolute
used for triggering inlra-frequency handovers

A3

event ,A4

oevent45_servingcellbecomeswolsethanthresholdlarrclneighbouringcellbgcomesbctlelthanthreshold2

43 and A5 are the most likely to bc

*TheUEsendsaMeasurementRgporttotheeNodeBwheloneofilsrepoftingeventsiStggered'orwhenlheperiodic The compleie conlent ofa Measurement Report is shown rcporting timer cxpir", iffp"ioli.i *p.rting has been configured. r* ip,i*'"r and in practici, only a subsct ofthe content is included in l.ablc 152. U_y ,Lt

""it".r

Srving Cll Measurment Rsults

Neighbouring Cell Mcasurcment Resulls

E-UTRA Result List CGI Informalion

UTRA Rcsult t,ist

CGI Information

i
4

.i

GERAN Rsult List

)i

:!
CDMA2000 Resuits
.i

'l
Teblc 152 - Contcnt ofMeasurcment Report messagc

236

'

,li

IN BULLETS
Thc Measurement I{eport identifies ils triggering mechanism using the Mcasuremcnt ldentity. I'his identily links thc mcssagc content to the configuration inlormation rvithin the lll{C Connection Ileconfiguration message. lt docs Dot explicitly indicatc the triggcring nechanism. For cxamplc. thc Measuren'rent Idcntit) could bc signalled as '4' and then measurement idenlity '4' within thc RRC (lonnection Rcconfiguralion mcssage refcrcnces event A3 Serving cell measurements are always included within the Measurement Report. These measurcments allow thc eNode B evaluate the coverage provided by the existing serving ce1l, and lo comparc it against the coveragc reported lor each of the neighbouring cclls
10

In the case of inlra-frequency handovers. the Measuremenl Report includes thc ll-UTRA iist of measurement results but cxoludes the inter-systcm ljsts ofmcasurcmcnt results, j.e. the LlTItA, GERAN and ClDM 2000 measuremcnt rcsults are cxcluded

E-U]'RA list ofmcasurcmcnt resulls identifies each ncighbouring cell by ;ts I'hysical l-aycr Cell Identib, (PCI). The Cell Global Idcntiry (CGI) inforrnation is tl,pical11, cxcludcd al this stage. This information is only included when spccifically requested by the eNodc B. lt is not includcd by defbult bccause the UFI ha-s lo dccode the MIB and SIII 10 extracl the CGI. Thjs makes it relatively processor lntensive compared to jusl rqoording I{eference Signal measurcments. The eNode B may rcquest the CGI in a separate Measurement Reporl ifthe Automatic Neighbour l{elation (ANR) procedure described in section 25.2 is triggcrcd. The CGI information is not rcquircd ifthe ncighbouring celi is aheady included wilhin the eNode B database 01'neighbours. i.e. the eNode [] can identiry thc ncighbouring cel1 using its PCI
coverage.

'l hc

RSIiI and/or RSITQ measurements fiom the ncighbouring cclls are reported to allow the eNodc B to evaluate thcir lfthc eNode B can identiry a caodidate ncighbouring cell from its PCI, and iflhe coverage conditions indicate

that a handover should bc completed, the eNode B initiates the handovcr procedure bv sending an X2-AP Handover I{equcsl mcssagc to thc targct c'Node B. I'he conlent of this mcssagc is prcsented in 'l'able I 53
lnformation Elemenls
Message Type
Presence

Old eNode B UIi X2AI' ID

Cause

Mandatory Mandalorv Mandatory Maodalory

'l'srget Cell Idenlity

GT]MMEI
IJE Conlext lnli)rmalion

MME

U[ SIAP ID

Mandatory Mandalory Mandatory Mandatory Optional Mandatory Mandatory Oplional Mandatory Mandatorv Optional Oplional Mandalory
Optional

UE Securiry Capabilities AS Sccuritv Inlormation

Ul

Aggrgatd Maximum Bit Rate

Subscriber Profile

ld lor RA'f/l,rquency Priorilr

E-R

E-RAB Selup I-ist

{B Idcnlily
B t,evel QoS Paramclcrs

EJI

Downlink Forwarding

Uplinl RR('('ontext
Haidovcr Rcstriction Lisl
Location Rcporting lnformation

IP

I'unnci Endpoirlt

tiE Historv lniormation

Tracc Activation SRVCC Operation Possible

Optional
mcssag

l'ablc 153 Contenl of thc X2-Al' llandover Request

The Cause value wilhin thc X2-AP Ilandover Ilequest is t-vpically configured as 'l landovcr Dcsirable for Radio Rcasons' l1 can also be configured as 'Tjme Critical I Iandover', 'Resource Optimisalion Ilandovcr' or 'il{educe l-oad in Scrving Cell'. Thc lime critical cause indicates that the conncction is likell to drop if a handovcr is no1 completed. I'he resource optimisation causc indicales {hat the serving cNode B is allen1ptinEl to balancc the notwork load bctrvccn itsclf and its ncighbours

I
I,ONG TERM EVOLLTTION (LTE) I I
I

.l.he,l.argetCellldenlityissignalledastheE-t]TItAn\CCil.ThjsinfornralioniSextraclcdftomtheeNcldct]databaseol

ifthe PCll and NeJghbour.Relation (ANR) procedure is triggercd ncishbours using the pcl u, u,","r"i.".'i:t"",t,,tomatic proccdure) ANR the supports the network *;ti;,r^ifrc au,ut^" iassuming the-corresponding CGI cannot be fou'ii which MME hosts the UE (GUMMEI) is included to inlbnn the tarset eNode B of The Globally Unique MME Identity to the approprialc MME message S1-AP 'Path Swilc;Requesl' thc target cNtoiliii,o
connection- l.his alJows

during a later stage ofthe handover proccdure

handover request The se1 of

"ia."r.,fr"

t]I]ConlextlnlbrmationinfomsthctalgetcNodcBofrvhichbearcrsneedtobecstablishcdtosupporttheincoming ;;f alonA with their Qualitv of Sen'ice (QoS) i

;c' I a1c.sn'cc E-RA; ;;;s;;;;; tr:er planc datr utrn i,,.tua.u to allo* thJ turg''t eNodc B to send uplink rcouiremenrs. lhe uplink aTp 1"";.;';;;;;i'nr'i. ( a1 it't opp'op'i''t ternt inarion point at t he serr ing iateu ;H:r il;'ti ,;;.'t;. i""
"ttrt l.hetargeteNodgBapp]iesilsadmissioncontrolalgorithmaftelreceivingtheX2-APilandoverRequest.ASSuminga gandover Reques-1 Ackrowledge message Thc conlenl ofthis
positivc outcome, the targel eNode rnessage is Presenled in Table 154

;;","r".t * XZ:af,

Old eNode B tJE X2AP

Ne:l, eNode B UE X2AP

lD

lD
Uptrnt CTP l unncl EndNint Downlink GTP lunnel Endpoin{

E-RAB Admitled l-ist

|-RAB Not Admitted List

frJ.NocJr

to source eNode B Transparent Container

Criticality Diagnostjcs

q\od'' B ol uhich l -RAll {''lnurvlcdtc mcssagc lo inlurm lhc tt'ulqc flre targct eNode B urc' the llandorer Rcquc:t uplinL and 'lo$nlinL user toruarJ B t0 ro a-llou rhe.uurcc cNod. harc hecn admincd. L; I t, tunnel endioins"are specifico not been admifled have which tj .un atro s1'.. iry anv IJ-RAB plane dara across rhc x2 inrcrfaca. iil';;;.il;.
TheTargeteNodeBtosourcgeNodeBTransparenlContainerjncludcsallandoverCommandmessage'l.hcllandover message which has bcen generated by the targct
Rcconfigurarion command message encapsulates ariilic;;;;"i; the airis seint to the sourcJ eNodc B to be forwarded across ;rssagc R".;;i;;;;;;; Connccrion eNode B. The RRC .t.his aell targct the onto for complering thc handovcr message p"r"rw iall irr. ug *itrr-;"slruotions interface to the uE.

Table

l5,l

Acknortledge messagc Content ofthe X2-AP llandoYer Request

.l.hcsourcceNodeBextlactsthcIIRC]Conneclionl].econfigurationmessagefromthcX2-AI)mcssagcandinitiatesthc to thc llE phase by forwarding it across thc air-inteface

r'r".i"t"t n.""*.n
.fhe

irformation This includes a scction which specifies mobiliq' control RRC connection Rcconliguration message able 155 section oflhc mcssage is presented in l ccll lhc uplink and dorrnlink tU'lhePhrsical tater( ell ld(nlil) rl'( l)i: speiificd todircctthc ll onlo the rppropriare N. thcchanncl oan.lr. iorir isal.ospccifiedincomhinationqith earricr. are specified in ,.r^ ni,n.i,'t -t/i't{Ai-ARil any additional spectrum emission requirements lirner upon 100' 150' 200' 500'.l000 or 2000 ms fhe UE stads this l'he T304 timer is specified using a value of50' access random the completing p.io. to the UE successfully ii'i::o+ receiving thc mobiljly controj ;"rir"""ii"". "*pir", procedure ;;i;;geroetl' thc uH initiatcs the RRC Conncction Rc-establishment

;;;:"';; ;;;;;li.

ThcUEisa]locatedancwC-RNTIbythetargeteNodcB..I.hisC-RNTIisusedtoaddresstheUDwitlrinthetalgctccll

physical channets al the providcs inlormation rugarding various transport-and confiEluration Iicsourca l{adio l.he common ano uplink c-r clic prcfix length are also spccificd ,plint t'unl'nii

ii'; ;;"i-um

fo*t'

Thedct]icatedRACHConfiguralionprovidcssupportforallouingrhclJEtocompl(jlethcnon-contentionbasedRandorn .l.he rathcr than aliowing it to seiecl a sequencc at

pr.*rfrle stqLi'nce uE is attocatJi to Access procedure. "'jial."i!i thACll mask defines the subftame dur-ing u'hich the Ul'l is aliowed randon lrom thc pool ol commo" ."u."".'..1rt" procedure handovcr overall
use the dcdicated

pr"ulnbl" s"qu"n"-"'it i,

opprou"r.,

l"tp,

to impro\e the reliabilif- oflhc

238

IN BULLETS

Target Physical Cell ldenhty

Uplink Carrier Frequency

Additional Spectrum Emission Requiremenls

Conmon Radio Resourcc Configuration

Dedicatd RAC]:l Confi guralion

Random Ac{css PRAC}l Mask Index

'labl

155

Contcnt of Mobilit) Control lnformation from within an RRC Connection Reconfiguratio mcssage

The source eNode B proceeds to scnd an X2-AP Sequcnce Numbcr (SN) Status Transfer messagc to the targct eNode R. 'l his message provides the target eNode B with uplink and downlink PDCP sequence number information lor E,RAB using acknowledged mode RLC. l'his helps to ensure that sequcnce numbering is prcscrved during the handover and that tbe handover is losslcss PDCP sequence numbers for unackno\yledged mode RLC are reset in the larget eNode B. The content ofthe SN Status Transfer message is shown in 'Iablc I56 lnfonnatien Elemenls
Message Type
OhJ eNode B Prcsonce

Mahdarory Mandalorv

(lti X2AP ID ]D
E RAB ldntiry
Recei!e Status ofUplink PDCP SDU

New eNotle B tlE X2AP

Mandalorr
Mandalory Optional Mandatory Mandatorv
SN Status

EJIAB

Subject to Status

Transfer [-ist

Uplink COUNT value Downlink COIiNT vahre Tablc

156 Content of the X2-AI'

'l'ransfr mcssage
a

The optional Rcccivc Status ofllplink PDCI' SDU inlbrmation dcfines successftlly received, and which have not been reccivcd

bitmap to indicate which uplink SDU havc been

The tJplink COI-NT valuc defincs the PDCP sequencc number and Hyper Framc Number (HFN) ofthe first missing upiink SDIJ. 'l he Downlink COLIITIT value delines thc PDCP sequcnce number and HFN that the larget eNodc B should allocatc to the next downlink SDU that has not already bccn allocaled a sequencc number The sourcc eNode B starts for$'arding uscr plane data across thc X2 interfacl] to the larget eNode ts after receiving the X2AP llandovcr Request Acknowledgc message. Forwarding makes usc ofthe X2 upJink and downlink GTP l unnel l-ndpoints specified within thc Handovcr Request Acknowledge message. At this point in time, the targel eNodq B buffers the packets without lorwarding

239

LONG TDRM EVOLLTTION (LTIi)

Thc uli proccccls to achievc air-interfacc synchronisation with the 1ar8.ct ccll using thc PIimaD'and Secondary the target Synchronjsation Signals. The tJE thcn initiates the random access procedurc whiclr is non-contention based if RRC ollhe Control section the Mobility wilhin informalion I Configuration cNodc B included Dedicated l{ACI Conncction Rooonfiguration mcssage. The random acccss procedurc is contention bascd ilthe Dcdicaled ItA(lH Confi guration jnlormation was cxcludcd

lt Random Access Rcsponse (RAR) mcssage providcs the lJ[ rvith timing advancc inlormation for thc larget ccl]. also jnitial is the RRC messagc layer 3 c:r.se, the In this message. laycr 3 providcs an uplink resource allocation for the injlial bonncction Riconfiguration Complete mcssagc. The IJE compietcs the handover procedurc from the LJE pcrspective by sending this mcssage
.l'hc

Both uplink and downlinl data can now be transferred betwecn the tJE and larget cNode B. This.epresents lhe start ofthe from Hanilover Completion phasc. t)ownlink data lrom the Sen'ing Gatewa)' continucs to be sent 10 the souroc eNode B' 'fhc dala to thc uplink ll car forward eNode target where it is forwardcd to thc larget cNode B across tha X2 intcrface. SeNing Gatcway using the Sl uplink G1'P Tunnel Endpoint spccified within the X2-AP Ilandover Requcst messagc
mcssage, thc target eNode ll initiales the procedure for switching the iowniink GIP tunnel from the source eNode B to thc target cNode B. This is done by sending an S1-AI' Path Swiich Rcquest 10 the MMFI. Thc conlcnl ofthis mcssage is presenled in l'able 157

Afler receiving the RRC Conneclion Rcconfigumtion Complete

lnfomalion Elements
Message Type eNode B

Presellce

I'lanlatory
Mandatory

IIE SIAP ID

Fl-RA B to be Switched in

tj-MB ldcntity
Transport Layer Address

Mandatory
N4andatory

Do.r'nlink List

GI'P-T]JID
Source

Mandatory Mandatory Mandatory Mandatory

MME UE

SlAl'lD

ir-IITRAN CGI
1'AI

tlI

Security Capabililies

Mandaory
message

Tablt 157 Content ofth SI-AP Path Switch Requcst

Thc l,ath Su,itch liequcst specifies both the transport la),cr address and the GTP l unnel Endpoint ldentity ('I EID) $hich arc to be used when ibrwarding downlink dala to thc targel cNode B. Thc MME is also informcd oflhe Tracking Area ldenlit_v (T'Al) and Cell Global Identiry (CCI) belonging to the cell with $hich the l lE is no\l connccted
The MME decicles whcther or no1 the exisling Scrying Gatorvay can continue providing services to the UE. Thc examplc shou,n in Figure I l3 assumcs therc is no rcquirement to changc Serving Galcrvay. lf the Scn'ing Gateway needs 10 he changccl, the MME forwards a GTPv2-C Creale Session Request message to the new Serving Galervay. and the new Sen,ing Gateway oonlacts the I'DN Galeway 10 requcst re-direction ofthe existing G IP tunncl Assuming the Scrving Galeway rcmains unchangsd, the MME lorwards a G'l'l'v2-C Modil Ilearer Roquest message to thc existi"ng Serving Gatcway. This message instructs the Serving Gateway to start fbr$'arding downlink data tt)u'ards thc larget cNoie B. 'l'hi Scrving Galovay proceeds to switch thc downlink path, and a{ this poinl bolh uplink and downlink dala is tanslerrccl betwccn the UE and Scn ing Gateway without any forwarding via the source eNodc B The Sening Gateway acknowledges thc switch to the MMtr using a GTPv2-C Modii-.r Bearer Rcsponse message. The MME rhen icknowledgcs rhe swjtch to thc targct cNode B using ar Sl-AP Palh Switch Rcquest Acknorv)edge message
'I he larget eNode B completes lhe handover procedlrre by scndinl an X2-AP 1)ll Contcxt Release mcssage 1() thc source cNode E. This message inlorms the souro!'eNode B that it can release i1s rcsources for thc LIE *hich has now moved aoross to the target eNodc Il

3CPt' References:

'fS 36.423, 'l'S 29 2'74 36.300. TS 23.401, TS 36.331-

240