LTE-SAE Overview and Radio Signaling

8/10/2019 LTE-SAE Overview and Radio Signaling

1/363

LTE / SAE

Overviewand

Radio Signaling

INACON GmbH

Stefan-Zweig-Strae !a"#!$% &arlr'(e

German)www*ina+on*+om

e-mail, ina+onina+on*de

Licensed to Ramanathan Sundaram, Omantel. No further distribution allowed.


2/363

Cover deign b) Oliver S+(.n

!%%% - 01!$ INACON GmbH

Stefan-Zweig-Strae !a

"#!$% &arlr'(e

All rights reserved. No part of this publication may be reproduced, stored in aretrieval system, or transmitted by any means, electronic, mechanical, photocopying,recording, or otherwise, without written permission from the publisher. No patentliability is assumed with respect to the use of the information contained herein.Although every precaution has been taken in the preparation of this publication, thepublisher and authors assume no responsibility for errors or omissions. Neither isany liability assumed for damages resulting from the use of the informationcontained herein. For more information, contact INACON mb! at www.inacon.com.



3/363

Legend,

All INACON publications use the same color codes to distinguish mandatory fromoptional or conditional parts in frame formats or optional from mandatory data blocksor signaling messages in scenarios. "he different color codes are e#plainedunderneath$

Color Code in 2rame 2ormat,

Color Code in S+enario,



4/363

2oreword of t(e 3'bli(er,

%ear &eader$

Note that this book is primarily a training document because the primary business ofINACON mb! is the training and consulting market for mobile communications. Assuch, we are proud to providing high'end training courses to many clients worldwide,among them operators like A"(", )obilkom Austria, *+I**CO), "')OI- or/*N- 0India1 and e2uipment suppliers like A-CA"-'-3CN", &IC**ON and*ON4'&IC**ON, )O"O&O-A, NO5IA'*I)N* and &I).

INACON mb! is not one of the old'fashioned publishers. +ith respect to time'to'

market, form'factor, homogeneous 2uality over all books and most importantly withrespect to after'sales support, INACON mb! is moving into a new direction."herefore, INACON mb! does not leave you alone with your issues and this bookbut we offer you to contact the author directly through e'mail 0inacon6inacon.de1, ifyou have any 2uestions. All our authors are employees of INACON mb! and all ofthem are proven e#perts in their area with usually many years of practicale#perience.

"he most important assets and features of the book in front of you are$

E4treme degree of detailed information abo't a +ertain te+(nolog)*

E4tenive and detailed inde4 to allow intant a++e to information

abo't virt'all) ever) 5arameter6 timer and detail of t(i te+(nolog)*

In+or5oration of everal 5ra+ti+al e4er+ie*

If a55li+able6 in+or5oration of e4am5le from o'r 5ra+ti+al field

e45erien+e and real life re+ording*

Referen+e to t(e re5e+tive tandard and re+ommendation on

virt'all) ever) 5age*

Finally, we again like to congratulate you to the purchase of this book and we like towish you success in using it during your daily work.

*incerely,

unnar !eine 7 8resident ( CO of INACON mb!



5/363

Table of Content

Reviiting im5ortant 7etail of t(e E3S*********************************!

9.9 Architecture Overview..............................................................:

9.9.9 volved 8acket Core in Conte#t..................................................:9.9.9.9 8C vs. 8*...................................................................................:9.9.9.: Non';88 Access Networks 0trusted 7 non'trusted1......................;

9.9.:

9.9.; Network lements and their Functions within the 8C................?

9.9.;.9 )obility )anagement ntity 0))1.................................................?9.9.;.9.9 Characteristics........................................................................?9.9.;.9.: Identification...........................................................................@9.9.;.9.; Interfaces ( 8rotocols............................................................9.9.;.9.= "asks ( Functions of the )).............................................9B

9.9.;.9.=.9 NA*'*ignaling towards the 3..................................................9B9.9.;.9.=.: *9'*ignaling towards the eNode.............................................9B9.9.;.9.=.; *'+ and 8'+ *election.......................................................9:9.9.;.9.=.= Other *election Functions..........................................................9;9.9.;.9.=.> -ocal reakout...........................................................................9=9.9.;.9.=.> I)* and -ocal reakout.............................................................9=

9.9.;.: *erving ateway 0*'+1..............................................................9?9.9.;.:.9 Characteristics......................................................................9?9.9.;.:.: Identification.........................................................................9?9.9.;.:.; Interfaces ( 8rotocols..........................................................9

9.9.;.:.= "asks ( Functions of the *'+...........................................:B9.9.;.:.=.9 8acket &outing 7 &elaying..........................................................:B9.9.;.:.=.: -egal Interception.......................................................................:B9.9.;.:.=.; CI'based 8acket "agging........................................................:B9.9.;.:.=.= Accounting..................................................................................:B

9.9.;.; 8%N ateway 08'+ or 8%N'+1..............................................::9.9.;.;.9 Characteristics......................................................................::9.9.;.;.: Identification.........................................................................::9.9.;.;.; Interfaces ( 8rotocols..........................................................:=9.9.;.;.= "asks ( Functions of the 8'+...........................................:?

9.9.;.;.=.9 3 I8 Address Allocation...........................................................:?9.9.;.;.=.: CI'based 8acket "agging........................................................:?9.9.;.;.=.; 8olicy nforcement....................................................................:?9.9.;.;.=.= -egal Interception.......................................................................:@9.9.;.;.=.> !ome Agent Function................................................................:@

9.9.;.= enhanced 8acket %ata ateway 0e8%1.....................................:

9.9.;.=.9 Characteristics......................................................................:9.9.;.=.: Identification.........................................................................:9.9.;.=.; Interfaces ( 8rotocols..........................................................;B9.9.;.=.= "asks ( Functions of the e8%...........................................;:

9.9.;.=.=.9 *8'"unnel )gmt towards 3Ds...............................................;:9.9.;.=.=.: o*'specific 8acket "agging in 3-'%irection...........................;:9.9.;.=.=.; -egal Interception.......................................................................;:9.9.;.=.=.= )A'Function for 8)I8v?.........................................................;:

9.9.= 8* Architecture for /oice *upport 0C*F or /oI8I)* with *&/CC1E !ow is *)* supported.........................................................................;=

Table of Content

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11 ' i '



6/363

9.: 8rotocol *tacks......................................................................;9.:.9 Control 8lane 7 '3"&AN ' 8C...............................................;

9.:.: 3ser 8lane '3"&AN E 8C 0*>7* "8'based1....................=B

9.:.; 3ser 8lane '3"&AN E 8C 0*>7* 8)I8v?7&'based1.. .. ..=:

9.; *ecurity Architecture..............................................................==

9.;.9 Overview ( Introduction............................................................==9.;.9.9 ssentials......................................................................................=>9.;.9.: 8*'A5A.......................................................................................=>9.;.9.; *ecurity is performed independently in two protocol layers..........=>9.;.9.= Algorithms.....................................................................................=>

9.;.: Operation of 3)"*'A5A...........................................................=?

9.;.; 5ey %erivation Function 05%F1..................................................=9.;.;.9 Comprehension Check ( 8ractical #ercise$"he 5%F *09B1 for 50A*)1.....................................................................>B

9.;.;.9.9 Input 8arameters..................................................................>:

9.;.= 8*'A5A in Operation during Initial Attach 8rocedure..............>=

9.;.> 3se of the different *ecurity Algorithms....................................>?

T(e Non-A++e-Strat'm, E88 9 ES8********************************:%

:.9.9 Important ))'8rocedures......................................................?B:.9.9.9 Common 8rocedures....................................................................?9:.9.9.: *pecific 8rocedures......................................................................?9:.9.9.; Connection )anagement 8rocedures...........................................?9

:.9.: *tate )achine...........................................................................?:

:.9.:.9 &elationship between )) and C)...........................................?:))'%&I*"&% ( C)'I%-..................................................?;))'&I*"&% ( C)'I%-.......................................................?;))'&I*"&% ( C)'CONNC"%........................................?;

:.9.; 3 )ode of Operation upon Attach E /oice %omain 8reference and3Ds 3sage *etting...................................................................................?=

:.9.= )essage Format.......................................................................??:.9.=.9 *ecurity !eader.............................................................................??

:.9.> Important ))'*cenarios.........................................................?:.9.>.9 Attachment through '3"&AN 7 new ))............................... ....?:.9.>.: Comprehension Check ( 8ractical #ercise$ uilding your own))$ A""G&')essage.................................................................... ....@?:.9.>.; "racking Area 3pdate 0Inter')) 7 with new *'+1...................B

:.9.>.;.9 Initial Conditions...................................................................B:.9.>.;.: %etailed %escription.............................................................:

:.9.>.= Comprehension Check ( 8ractical #ercise$ ))')essage%ecode......................................................................................................

:.:.9 Important *)'8rocedures.......................................................HB:.:.9.9 ))'initiated................................................................................H9:.:.9.: 3'initiated....................................................................................H9

:.:.: *tate )achine...........................................................................H:

:.:.= )essage Format.......................................................................H=:.:.=.9 *ecurity !eader.............................................................................H?

LTE-SAE Overview and Radio Signaling

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' ii '



7/363

:.:.=.: 8rocedure "ransaction Identity.....................................................H?

:.;.> %edicated 8* earer stablishment.......................................H:.;.>.9 Network Initiated 0I)* triggered during Call stablishment1 .......H

:.;.>.9.9 Initial Conditions...................................................................H:.;.>.9.: %etailed %escription.............................................................H

:.;.>.: Network Initiated 0I)* triggered during Call stablishment1 .....9BB:.;.>.:.9 %etailed %escription...........................................................9B:

Radio Reo'r+e Control*******************************************************!1:

;.9 Overview..............................................................................9B?

;.9.9 "ransmission of broadcast information....................................9B@

;.9.: stablish and maintain services..............................................9B@

;.9.; o* control.............................................................................9B@;.9.= "ransfer of dedicated control information................................9B@

;.: *tate Characteristics of &&C...............................................9B

;.:.9 &&CGI%-...............................................................................9B

;.:.: &&CGCONNC"%................................................................9B

;.; *ignaling &adio earers 0*&1............................................99B

;.;.9 Overview.................................................................................99B;.;.9.9 *&B...........................................................................................99B;.;.9.: *&9...........................................................................................99B;.;.9.; *&:...........................................................................................99B

;.;.9.= Control 8lane 8rotocol *tack &eview...................................99:

Air Interface protocols................................................................. ......... ...99;

;.;.9.> 3ser 8lane 8rotocol *tack &eview.......................................99=Air Interface protocols................................................................. ......... ...99=*9 protocol..............................................................................................99>

;.;.9.? Overview on Channel "ypes and 3ser earers....................99?;.;.9.@ &eview of eN %- Channels.......................................................99;.;.9. &eview of eN 3- Channels.......................................................9:B

;.;.: )apping of &&C')essages to *&Ds and to Channels.......... .9::;.;.:.9 )essages on CC! 0)I and *I1............................................9::;.;.:.: )essages on 8CC! and %-'CCC!............................................9:=;.;.:.; )essages on %-'%CC! and %-'%"C!.................................... ..9:?;.;.:.= )essages on 3-'CCC!, 3-'%CC! and 3-'%"C!....................9:

;.= )essage ncoding through A*N.9 8&'unaligned.............9;B;.=.9 #ample$ "he A*N.9'Code of &&CGCONNG& ............. ....9;B

;.=.: and the compiled )essage *tructure 0"ree /iew1..............9;:

;.=.; Comprehension Check ( 8ractical #ercise$ncoding an &&CGCONNG&')essage.......................................9;=

;.> &&C 8rocedures..................................................................9;?

;.>.9 *ystem Information roadcast................................................9;?;.>.9.9 Overview......................................................................................9;?;.>.9.: Overview of Functions of the *ystem Information locks........ ...9;

Table of Content

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11 ' iii '



8/363

;.>.9.; #ample of an )I......................................................................9=B;.>.9.= #ample of an *I9.....................................................................9=:;.>.9.> #ample of an *I:.....................................................................9==;.>.9.? #ample of an *I;.....................................................................9=?

;.>.: Connection )anagement &elated 8rocedures........................9=;.>.:.9 8aging 8rocedure.......................................................................9=;.>.:.: &&C Connection stablishment 8rocedure................................9>B

;.>.:.:.9 *&9 %efault Configuration...............................................9>:;.>.:.:.: 8hysical -ayer %efault Configuration.................................9>=

;.>.:.; 3 Capability "ransfer 8rocedure..............................................9>?;.>.:.= &&C Initial *ecurity Activation 8rocedure...................................9>;.>.:.> &&C Connection &econfiguration 8rocedure.............................9?B

;.>.:.>.9 *&: %efault Configuration...............................................9?:;.>.:.? Counter Check 8rocedure...........................................................9?=;.>.:.@ &&C Connection &eestablishment 8rocedure............................9??

;.>.:. &&C Connection &elease 8rocedure.........................................9?

;.>.; Inter &A" &&C 8rocedures.....................................................9@B

;.>.= '3"&AN )easurements........................................................9@:;.>.=.9 Overview......................................................................................9@:;.>.=.: %efinition of )easurements in '3"&AN....................................9@=;.>.=.; )easurement vents in '3"&AN..............................................9@?;.>.=.= )easurement %efinition in the *tandard E )easurement ObJect.................................................................................................................9@;.>.=.> )easurement %efinition in the *tandard E &eport Configurationand )easurement I%...............................................................................9B;.>.=.? *tructure )easurement &eport...................................................9:

;.>.> Other &&C 8rocedures...........................................................9=

;.>.? &&C 8rocedure %elay.............................................................9?;.>.?.9 Introduction..................................................................................9?;.>.?.9 /alues.........................................................................................9

;.>.@ Idle )ode 8rocedures E Neighbor Cell )onitoring ( Cell&eselection......................................................................................9HB

;.>[email protected] 8riority'ased Cell &eselection of )ulti'&A" 3Ds.....................9HB;.>[email protected] *8I% ' *ubscriber 8rofile I% for &A"7Fre2uency priority....9H9;.>[email protected].: '3"&AN priority'based Cell &eselection %etails..............9H:;.>[email protected].; 3"&AN priority'based Cell &eselection %etails.................9H:;.>[email protected].= &AN priority'based Cell &eselection %etails.................9H;

;.>.@.: Cell *election in '3"&AN..........................................................9H=;.>.@.:.9 8-)N selection in '3"&AN..............................................9H?;.>.@.:.: Cell *election and &eselection...........................................9H?;.>.@.:.; Cell *election 8rocess........................................................9H?;.>.@.:.= Cell *election Criterion.......................................................9H@

;.>.@.; Cell &eselection valuation 8rocess in '3"&AN.....................9H;.>.@.;.9 &eselection 8riorities !andling..........................................9H;.>.@.;.: )easurement &ules for Cell &e'*election.........................:BB;.>.@.;.; )obility *tates in '3"&AN................................................:B:;.>.@.;.= *caling &ules based on )obility *tate...............................:B=

;.>.@.= '3"&AN Inter'Fre2 and I&A" Cell &eselection Criteria............:B?;.>.@.> Intra'Fre2 and e2ual 8riority Inter'Fre2 &eselection Criteria......:B

;.>.@.>.9 Cell &anking Criterion in '3"&AN for e2ual 8riority inter'Fre2 and intra'Fre2............................................................................:9B

;.>.@.? Cell &eselection towards lower 8riority '3"&AN Fre2 or I&A"Fre2 than *erving Fre2...........................................................................:9:


INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' iv '



9/363

;.? &AN to '3"&AN Cell &eselection.................................:9=;.?.9 I&A" )easurements when camping in *) or 8&*........ ...:9=

;.?.: I&A" Cell &eselection based on 8riority E : to ; 7 -".... ..:9?;.?.:.9 Cell &eselection CriteriaDs...........................................................:9?;.?.:.: Cell &eselection from &AN towards higher prioritiKed I&A"Fre2uency...............................................................................................::B;.?.:.; Cell &eselection from &AN towards lower prioritiKed I&A"Fre2uency...............................................................................................:::

Lower La)er of t(e ;'-Interfa+e, 8AC6 RLC 9 37C3*****00:

=.9 Features of )AC..................................................................::?

=.9.9 Overview.................................................................................::?

=.9.9.9 %ata transfer logical channels LM transport channels..............::?=.9.9.: &adio resource allocation............................................................::@=.9.9.; *pecial procedures.....................................................................::@

=.9.: &adio Network "emporary Identifiers 0&N"IDs1 in '3"&AN. . .::=.9.:.9 3sage of &N"IDs..........................................................................::=.9.:.9 &N"I /alues................................................................................:;B

=.9.; )AC &andom Access 8rocedure............................................:;:=.9.;.9 Contention ased &andom Access 8rocedure...........................:;:=.9.;.: Non'contention based random access procedure......................:;?

=.9.= *tructure of )AC'8%3............................................................:;=.9.=.9 )AC control element...................................................................:;H=.9.=.: Normal 0non'transparent1 )AC *%3..........................................:;H=.9.=.; "ransparent )AC *%3...............................................................:;H

=.9.> )AC Control lements............................................................:=B=.9.>.9 Contention resolution I%..............................................................:=9=.9.>.: "iming Advance...........................................................................:=9=.9.>.; %&.............................................................................................:=9=.9.>.= 8adding.......................................................................................:=9=.9.>.> 8ower headroom report...............................................................:=9=.9.>.? C'&N"I........................................................................................:=9=.9.>.@ *hort, long and truncated buffer status reports...........................:=9

=.9.? 8ractical #ercise$ )AC Operation.........................................:=:

=.9.@ 8ractical #ercise$ %- )AC 8%3 Construction.......................:==

=.9. )AC Configuration..................................................................:=?=.9..9 )AC Configuration in the *tandard ...........................................:=?

=.: Features of &-C...................................................................:=

=.:.9 Overview.................................................................................:==.:.9.9 %ata transfer................................................................................:==.:.9.: rror detection and recovery.......................................................:==.:.9.; &eset...........................................................................................:=H

=.:.: *tructure of &-C 8%3.............................................................:>B

=.:.; *tructure of &-C A) with 8%C8 8%3 *egments....................:>:

=.:.= &-C Configuration...................................................................:>==.:.=.9 &-C Configuration in the *tandard.............................................:>=

Table of Content

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11 ' v '



10/363

=.; Features of 8%C8................................................................:>?=.;.9 Overview.................................................................................:>?

=.;.9.9 &o!C...........................................................................................:>?=.;.9.: Numbering of 8%C8 8%3s.........................................................:>?=.;.9.; In'se2uence delivery of 8%3s....................................................:>?=.;.9.= %uplicate deletion........................................................................:>?=.;.9.> ncryption...................................................................................:>@=.;.9.? Integrity 8rotection......................................................................:>@

=.;.: *tructure of 8%C8 8%3..........................................................:>

=.;.; 8%C8 Configuration................................................................:?B=.;.;.9 8%C8 Configuration in the *tandard..........................................:?B

=.= !ow a "C87I8 )"3 is reaching the 3 7 the Internet..........:?:

=.=.9 "C87I8 layer............................................................................:?:

=.=.: 8%C8 layer..............................................................................:?:

=.=.; &-C layer................................................................................:?:

=.=.= )AC layer................................................................................:?;

=.=.> 8!4 layer................................................................................:?;

.9.:.9 )obility )anagement..................................................................:?

>.9.:.: -oad )anagement......................................................................:?>.9.:.; :'Interface )anagement...........................................................:?

>.9.; :'based !andover *cenario.................................................:@B>.9.;.9 Initial Conditions..........................................................................:@B>.9.;.: %etailed %escription....................................................................:@:

>.: "he *9'A8 8rotocol.............................................................:@=

>.:.9 Overview ( Introduction..........................................................:@=

>.:.: *9'based !andover *cenario..................................................:@?>.:.:.9 Initial Conditions..........................................................................:@?>.:.:.: %etailed %escription....................................................................:@


INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' vi '



11/363

C(a5ter !,Reviiting im5ortant 7etail of t(e E3S

Ob=e+tive

*ome of your 2uestions that will be answered during this session

How doe t(e ar+(ite+t're of t(e LTE-networ> loo> li>e?

@(at are t(e ta> and f'n+tion of t(e new networ> element?

How doe e+'rit) o5erate in LTE?

Revisiting important Details of the EPS

!

' 9 ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



12/363

!*! Ar+(ite+t're Overview

!*!*! Evolved 3a+>et Core in Conte4t

"he obJective of this section is to depict the 8C as new network cloud inconte#t to the legacy and new network clouds.

Image 7e+ri5tion

"he image is split into two parts$ in the upper part, the image illustrates thelegacy network parts and clouds which already e#ist with ;88 &el. ? and @.

"hese network parts and clouds are illustrated in gray color.

In the lower part, the new network clouds with &el. are depicted. "hey havebeen coloriKed to provide for a better distinction from the legacy network clouds.

I'+-AN I8 access from non';88 non'trusted access network may be achievedeither directly 0lower option1 or through the packet'switched core network domain0upper option1.

!*!*!*! E3C v* E3S"he two terms 8C and 8* can be distinguished as illustrated$

"he 8C represents the core component of the 8*.

"he 8* contains the 8C and the '3"&AN 0-"1 access network. !owever, itdoes not contain the other access networks.

P;"* :;.=B9, ;"* :;.=B:Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' : '



13/363

!*!*!*0 Non-G33 A++e Networ> Btr'ted / non-tr'ted

In the legacy part 0gray1 the image illustrates the so called non';88 non trustedaccess networks which have been supported by ;88'recommendations since&el. ?.

New with &el. and *A are the so called trustednon';88 access networks."hose trusted non';88 access networks comply to an 8C'operatorDs securityre2uirements P;"* ;;.=B: 0=.:1Q and are therefore granted direct access to the8C.

+hether a non';88 access network is trusted or untrusted is ...

9. either pre'configured in the 3 or ...

:. the 3 learns the trust relationship during A8'A5A authentication throughthat access network from its home'8-)N.

;. 4et another option is that the selected access network does not at allsupport A8'A5A authentication in which case the 3 determines that itcamps on an untrusted non';88 access network.

"he maJor difference for the 3 with respect to the trust relationship of the selectednon';88 access network is that in Runtrusted caseR the 3 must establish anI8sec'tunnel through I5v: with an e8% in the 8C P;"* ;;.=B: 01Q."he illustrated I8sec'tunnel through the non';88 trusted access network is onlynecessary in case the *:c'interface is used and it comes without interface name.

Abbreviation of t(i Se+tion,

AKA Authentication and key agreement

(3GTS 33.102)

IKEv2 Internet Key Exchange rotoco! "

#er$ion 2 (%&' 30)

E-UTRAN E#o!#ed *+TS (*ni#er$a! +o,i!eTe!ecommunication Sy$tem)Terre$tria! %adio Acce$$ -etork

IPsec Internet /rotoco! " $ecure (%&'301)

EAP Exten$i,!e Authentication /rotoco!(%&' 3)

LTE ong Term E#o!ution (o *+TS)

EAP-AKA Exten$i,!e Authentication /rotoco!method or 3rd generationAuthentication and Key Agreement(%&' 1)

PLMN /u,!ic and +o,i!e -etork

EPC E#o!#ed /acket 'ore (3GTS 23.01)(%e!. onard$)

SAE Sy$tem Architecture E#o!ution

EPS E#o!#ed /acket Sy$tem UE *$er E4uiment

I-WLAN Interorking 5A- (5ire!e$$ oca!Area -etork) (3GTS 23.23)

UTRAN *+TS (*ni#er$a! +o,i!eTe!ecommunication Sy$tem)Terre$tria! %adio Acce$$ -etork


!

' ; ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



14/363

!*!*0 Zoom into t(e E3S

"he obJectives of this section are to$9.Illustrate the inner structure of the 8C and the '3"&AN.:. 8oint out the Rone'to'manyR nature of the interconnections within the 8*.

5ey point of this section is that there is no more &NC or *C within theaccess network.

Image 7e+ri5tion

"he image depicts another time the two network clouds 8C and '3"&AN andillustrates the physical interconnections 0black lines1 of the various networkelements to the two I8'backbone networks.

P;"* :;.=B9 0>.;.:1Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' = '



15/363

!*!*0*! 2'n+tional Overview of Core Networ> Element wit(in t(e E3C

"he 88E or )obility )anagement ntity takes care of various control planefunctions like mobility management and session management.

"he S-G@or *erving ateway is the peer of the )) within the user plane andits functions evolve around packet data routing and forwarding.

"he 37N-Gatewa)has similar functions as the *erving ateway but it remainsthe anchor during a packet data connection even if )) and *'+ areswapped. It is feasible to assume that *NDs will typically be upgraded into8%N'+Ds.

S-G@ and 37N-G@may easily be integrated into a single bo# in order to savehardware and latency. A combination of )) and *'+ is probably less appealing

because the )) is a very slim hardware bo#.

"he e37G is re2uired to interconnect non'trusted non';88 networks to the8C. Its functions evolve around tunnel termination towards the 3 and the non'trusted non';88 access network.


BSC 6a$e Station 'ontro!!er MME +o,i!ity +anagement Entity (3GTS23.01) (%e!. onard$)


PDN-GW /acket 7ata -etork Gateay (arto E/')

eNB Enhanced -ode 6 PLMN /u,!ic and +o,i!e -etork


RNC %adio -etork 'ontro!!er

ePDG e#o!#ed /acket 7ata Gateay (3GTS23.02)

S-GW Ser#ing Gateay (3GTS 23.01)

EPS E#o!#ed /acket Sy$tem UE *$er E4uiment

GGSN Gateay G/%S Suort -ode UTRAN *+TS (*ni#er$a! +o,i!eTe!ecommunication Sy$tem)Terre$tria! %adio Acce$$ -etork

IP Internet /rotoco! (%&' 81)


!

' > ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



16/363

!*!* Networ> Element and t(eir 2'n+tion wit(in t(e E3C

!*!**! 8obilit) 8anagement Entit) B88E

!*!**!*! C(ara+teriti+

"he obJective of this section is to illustrate the most important characteristicsof the )).

Image 7e+ri5tion

"he )) is a network element that takes care of control plane tasks.

"he )) may physically be part of an **N or *'+ or it may be setup as astand'alone network element.

))Ds are typically organiKed in pool areas 0*9Fle#1 to provide for loadbalancing among the ))Ds which belong to the same pool. All eNodeDs whichbelong to the related '3"&AN pool areas shall have access to the ))Dsbelonging to this ))'pool area0s1.

P;"* :;.BB: 0=.9.=.91, ;"* :;.=B9 0=.=.:1Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' ? '



17/363

!*!**!*0 Identifi+ation

ach )) is identified by using an )) roup I% 0))I1, and an )) Code0))C1. oth parameters together form the ))I P;"* :;BB; 09H.=.:.=1Q.

Room for )o'r Note,


3GTS 3rd Generation Technica!Seciication

MMEC ++E 'ode


MMEGI ++E Grou Identity


MMEI ++E Identity

GW Gateay SGSN Ser#ing G/%S Suort -ode

ID Identity UTRAN *+TS (*ni#er$a! +o,i!eTe!ecommunication Sy$tem)Terre$tria! %adio Acce$$ -etork

MME +o,i!ity +anagement Entity (3GTS23.01) (%e!. onard$)


!

' @ ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



18/363

!*!**!* Interfa+e 9 3roto+ol

"he obJectives of this section are to illustrate the )), its interfaces towardsother network elements and the protocol stacks used on these interfaces.

Image 7e+ri5tion

"he green color used for the interfaces indicates the control plane relationship ofa protocol or an interface.

"he interface towards the 3 is depicted to illustrate the NA*'protocolinvolvement of the )). Obviously, this interface is realiKed over *9'A8 and 3u.

"he *9B:'interface towards the cdma:BBB access network is only necessary incase of circuit'switched fallback for cdma:BBB'networks and it is also re2uired to

support *&/CC.

"he *v'interface is re2uired to support the *&/CC'feature. "he *v'interface isdescribed in more detail in ;"* :H.:B.

P;"* :;.=B9 0>.91Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' '



19/363

Room for )o'r Note,


1xCSIWS 1x 'ircuit Sitched InterorkingSo!ution &unction (3GTS 28.2)

HSS 9ome Su,$cri,er Ser#er :3GTS23.002;. 9SS re!ace$ the 9% ith3G// %e!. o't

"he obJective of this section is to e#plain the term Rlocal breakoutR.

5ey point of this section is to bear in mind that local breakout basicallyrelates to Rroute optimiKationR in case of roaming.

-ocal breakout re2uires the 3 to using two I8'addresses because traffic fromoutside needs an unambiguous route to the 3 and previously to two separate8%N'gateways.

It is obvious that local breakout will save latency and bandwidth, because the bluelink to the server is essentially shorter than the red link.

!*!**!*$*: I8S and Lo+al Drea>o't

-ocal breakout is particularly interesting in case of roaming and I)*'access.

In that case, it may be desirable to allow the user data traffic to RbreakoutR locallyin the /'8-)N whereas the *I8'signaling must in any case be routed to the I)*in the !'8-)N 0according to the I)*'rules1.

P;"& :;.: 0@.:1Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' 9= '



25/363

Room for )o'r Note,


3GTR 3rd Generation Technica! %eort IMS Internet /rotoco! +u!timedia 'ore-etork Su,$y$tem (%e!. ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



26/363

!*!**0 Serving Gatewa) BS-G@

!*!**0*! C(ara+teriti+

"he obJective of this section is to illustrate the most important characteristicsof the *'+.

P:;.BB: 0=.9.=.:.91, :;.=B9 0=.=.;.;1Q

Image 7e+ri5tion

"he *'+ represents the user plane side of the ))

Although the *'+ is logically a separate network element from the 8%N'+ ,the two network elements may physically be integrated into a single network

element 0e.g. to save on latency1. *'+Ds are typically organiKed into *'+ pools to provide for load balancing

among the *'+Ds which belong to the same service area.

All eNodeDs which belong the related '3"&AN pool areas shall have access tothe *'+Ds belonging to this *'+ service area.

!*!**0*0 Identifi+ation

An *'+ has no 8*'specific identifiers and is identified by means of I8'addresses and 3&-Ds.


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' 9? '



27/363

Room for )o'r Note,




EPS E#o!#ed /acket Sy$tem SGSN Ser#ing G/%S Suort -ode

MME +o,i!ity +anagement Entity (3GTS23.01) (%e!. onard$)

URL *niorm %e$ource ocator (%&'13)

PDN /acket 7ata -etork UTRAN *+TS (*ni#er$a! +o,i!eTe!ecommunication Sy$tem)Terre$tria! %adio Acce$$ -etork


!

' 9@ ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



28/363

!*!**0* Interfa+e 9 3roto+ol

"he obJectives of this section are to illustrate the *'+, its interfacestowards other network elements and the protocol stacks used on theseinterfaces.

Image 7e+ri5tion

"he green color of an interface indicates the control plane relationship of aprotocol or an interface. -ikewise, orange color indicates user plane relationship.

Note that on *> and * interface it is an operator choice to implement either "8or 8)I8v? together with &. Irrespective of this choice, the *'+ must support"8 on various other interfaces like for e#ample towards )), eNode or &NC.

P;"* :;.=B9 0>.91, :;.=B: 0>.91Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' 9 '



29/363

Room for )o'r Note,


DIAMETER Succe$$or o the %A7I*S rotoco! MME +o,i!ity +anagement Entity (3GTS23.01) (%e!. onard$)


PCRF /o!icy and 'harging %u!e$ &unction(3GTS 23.203)

eNB Enhanced -ode 6 PDN /acket 7ata -etork

EPC E#o!#ed /acket 'ore (3GTS23.01) (%e!. onard$)


GRE Generic %outing Enca$u!ation(%&' 2)

PMIPv /roxy +o,i!e I/#

GTP G/%S Tunne!ing /rotoco! (3GTS28.00)

RNC %adio -etork 'ontro!!er

GTP-C GT/ 'ontro! /!ane S-GW Ser#ing Gateay (3GTS 23.01)

GTP-U GT/ *$er /!ane SCTP Stream 'ontro! Tran$mi$$ion/rotoco! (%&' 280)

H-PLMN 9ome /+- SGSN Ser#ing G/%S Suort -ode

HSGW 9%/7 Ser#ing Gateay (cdma2000term)

TCP Tran$mi$$ion 'ontro! /rotoco!

IP Internet /rotoco! (%&' 81) UDP *$er 7atagram /rotoco! (%&' )

UTRAN *+TS (*ni#er$a! +o,i!eTe!ecommunication Sy$tem)Terre$tria! %adio Acce$$ -etork


!

' 9H ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



30/363

!*!**0*$ Ta> 9 2'n+tion of t(e S-G@

"he obJective of this section is to illustrate the tasks and functions of the *'+.

!*!**0*$*! 3a+>et Ro'ting / Rela)ing

!*!**0*$*0 Legal Inter+e5tion

!*!**0*$* CI-baed 3a+>et Tagging+hen the *'+ receives I8'packets in uplink or downlink direction it will check therelated CI'value based on the relationship of the packet to a certain service dataflow and handle the packet accordingly, e.g. relay it to the responsible "8'tunnel or&'tunnel.

!*!**0*$*$ A++o'nting

P;"* :;.=B9 0=.=.;.:1, :;.=B: 0=.;.;.:1Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' :B '



31/363

Room for )o'r Note,



IP Internet /rotoco! (%&' 81)

GRE Generic %outing Enca$u!ation (%&'2)

!CI oS '!a$$ Identiier

GTP G/%S Tunne!ing /rotoco! (3GTS28.00)



!

' :9 ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



32/363

!*!** 37N Gatewa) B3-G@ or 37N-G@

!*!***! C(ara+teriti+

"he obJective of this section is to illustrate the most important characteristicsof the 8'+.

Image 7e+ri5tion

"he home agent function is only applicable if the 3 accesses the 8'+ throughone of the interfaces *:a, *:b or *:c.

It may make sense to build only combined *'+ 7 8'+ nodes in order to savelatency. !owever, this re2uires interconnection points to the e#ternal 8%N at thelocation of every *'+.

!*!***0 Identifi+ation

A 8'+ is identified by means of I8'addresses and 3&-Ds.

In addition and by means of specific %N*'resolution, a 8'+ is logicallyidentified through A8NDs which refer to a specific service 08%N'access1 that agiven 8'+ can provide 0see section :.9.:.9.91.

P:;.BB: 0=.9.=.:.:1, :;.=B9 0=.;.;.;1, :;=B: 0=.=.;.;1Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' :: '



33/363

Room for )o'r Note,


APN Acce$$ /oint -ame (%eerence to aGGS-)

P-GW /acket 7ata -etork Gateay (arto E/')

DNS 7omain -ame Sy$tem PDN /acket 7ata -etork


PDN-GW /acket 7ata -etork Gateay (arto E/')

GGSN Gateay G/%S Suort -ode PMIPv /roxy +o,i!e I/# (%&'


34/363

!*!*** Interfa+e 9 3roto+ol

"he obJectives of this section are to illustrate the 8'+, its interfacestowards other network elements and the protocol stacks used on theseinterfaces.

Image 7e+ri5tion

"he green color indicates the control plane relationship of a protocol or aninterface. -ikewise, orange color indicates user plane relationship.

"he *8'tunnel over *:c has been established using A8'A5A over I5v:.

"he protocol layer SApplicationT comprises among others http, *I8, &"8 0withvoice or video1.

P;"* :;.=B9 0>.91, :;.=B: 0>.91Q%*)I8v?


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' := '



35/363

Room for )o'r Note,


AAA Authentication> AuthoriBation andAccounting

MIPv# +o,i!e I/ @er$ion

DIAMETER Succe$$or o the %A7I*S rotoco! NAT -etork Addre$$ Tran$!ation (%&'131)

DSMIPv 7ua! Stack +o,i!e I/# P-GW /acket 7ata -etork Gateay (arto E/')



EPC E#o!#ed /acket 'ore (3GTS23.01) (%e!. onard$)


ESP Enca$u!ating Security /ay!oad(%&' 303)

PMIPv /roxy +o,i!e I/# (%&' ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



36/363

!*!***$ Ta> 9 2'n+tion of t(e 3-G@

"he obJective of this section is to present the tasks and functions of the 8'+.

!*!***$*! ;E I3 Addre Allo+ation

!*!***$*0 CI-baed 3a+>et Tagging

"he 8'+ performs this task as part of the classification and according to theinstalled o*'policy.

ased on the installed %-'"F", the CI is determined and traffic handling rulesare determined.

!*!***$* 3oli+) Enfor+ement

"raffic shaping$ %elay data packet transmission until resources becomeavailable.

"raffic policing$ %iscard packet if no resources to transmit them are available.


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' :? '



37/363

!*!***$*$ Legal Inter+e5tion

uestion No 9$ +hy does the 8'+ perform legal interception and the *'+and, as you will see, the e8%, too

!*!***$*: Home Agent 2'n+tion

P;"* :;.=B9 0=.=.;.;1, :;.=B: 0=.;.;.;1Q

Room for )o'r Note,



PMIPv /roxy +o,i!e I/# (%&'


38/363

!*!**$ en(an+ed 3a+>et 7ata Gatewa) Be37G

!*!**$*! C(ara+teriti+

"he obJective of this section is to illustrate the most important characteristicsof the e8%.

Image 7e+ri5tion

"he e8% is an enhanced 8% as defined in &elease ?. 8lease recall that a8% usually was physically broken down into two parts$ one inside the *Nand one inside the "" P;"* :;.:;=Q.

"he selection of an e8% through the 3 occurs either through staticconfiguration or dynamically P;"* :;.=B: 0=.>.=1Q.

!*!**$*0 Identifi+ation An e8% has no 8*'specific identifiers and is identified by means of I8'

addresses and 3&-Ds.

P;"* :;.=B: 0=.;.=1Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' : '



39/363

Room for )o'r Note,



PDG /acket 7ata Gateay

EPS E#o!#ed /acket Sy$tem TTG Tunne! Termination Gateay

GGSN Gateay G/%S Suort -ode UE *$er E4uiment

IP Internet /rotoco! (%&' 81) URL *niorm %e$ource ocator (%&'13)

MAG +o,i!e Acce$$ Gateay (%&'


40/363

!*!**$* Interfa+e 9 3roto+ol

"he obJectives of this section are to illustrate the e8%, its interfacestowards other network elements and the protocol stacks used on theseinterfaces.

Image 7e+ri5tion

"he green color indicates the control plane relationship of a protocol or aninterface. -ikewise, orange color indicates user plane relationship. "he blacklines represent physical links which are used to piggyback the *+u'interface.

"he *8'tunnel over *:c has been established using A8'A5A over I5v:.

"he #b'interface as depicted in the image is currently not specified.

P;"* :;.=B9 0>.91, :;.=B: 0>.91Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' ;B '



41/363

Room for )o'r Note,


AAA Authentication> AuthoriBation and

Accounting

GRE Generic %outing Enca$u!ation (%&'

2)

AKA Authentication and key agreement(3GTS 33.102)

IKEv2 Internet Key Exchange rotoco! "#er$ion 2 (%&' 30)

DIAMETER Succe$$or o the %A7I*S rotoco! IP Internet /rotoco! (%&' 81)

EAP Exten$i,!e Authentication /rotoco!(%&' 3)





42/363

!*!**$*$ Ta> 9 2'n+tion of t(e e37G

"he obJective of this section is to present the tasks and functions of thee8%.

!*!**$*$*! ES3-T'nnel 8gmt toward ;EF"he allocated I8'address is Just relayed by the e8%. It stems from the 8'+.

!*!**$*$*0 oS-5e+ifi+ 3a+>et Tagging in ;L-7ire+tion

!*!**$*$* Legal Inter+e5tion

!*!**$*$*$ 8AG-2'n+tion for 38I3v#

P;"* :;.=B: 0=.;.=1Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' ;: '



43/363

Room for )o'r Note,



P-GW /acket 7ata -etork Gateay (arto E/')

ePDG e#o!#ed /acket 7ata Gateay (3GTS23.02)



44/363

!*!*$ E3S Ar+(ite+t're for oi+e S'55ort BCS2D or oI3I8S wit(SRCC How i S8S '55orted?

"he key point of this section is to show that the I)* is the Anchor of the /oI8call when the 3 establishes the ))"el in I)* and needs to be handed overto legacy 3)"*7*) or C%)A. "he procedure for handing over a /oI8I)*call to C*'domain in 3)"*7*) or C%)A is called *&/CC and re2uires the*v'interface between )*C and )) for ;88 interconnectivity. For handingover a 8*'voice call to C*'domain in C%)A, the *9B interface0s1 arere2uired between )) and C%)ADs C*'core.Note that we also show the C*'Fallback possibility beside *&/CC. It shouldbe clear that for targeting small interruption times of the voice'call Just


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' ;= '



45/363

a seamless !O can be used for e.g. *&/CC.

Image 7e+ri5tionIn addition to the primary focus on enabling an efficient )obile roadbandsolution, the support for voice services was not forgotten in the ;88 *Aspecification work. From the start, it was however agreed that -" is a packet'onlyaccess network, allowing an optimiKation for packet services. *ince the voiceservices so far have been realiKed using circuit'switched technologies 0C*'%omain1,this meant that specific mechanisms were introduced to also allow for voice servicesfor users of the packet data services offered over the -" access."he two main solutions for voice are to either use the I)* mechanisms and realiKevoice using the )ulti)edia "elephony 0))"el1 framework, that is using voice'over'I8, or to stick to the Uold circuit'switched way of providing voice services. "he

second option is in ;88 specifications realiKed through that users temporarily leave-" to perform the voice calls over :7;, and then return when the voice call isfinished. "his C*F 0circuit'switched fallback1 is for sure not the most elegant ofsolutions, but can be seen primarily as a gap'filler in case I)* infrastructure is not inplace. "he biggest drawbacks of C*F are its latency, means delay until the /oiceCall can be established and in the loss of the high throughput earers for the 8*'*ervices particularly when the Fallback network is &AN and no %") is supportedthen the 8*'services must be even suspended.+hen a user engaged in an I)*'/oI87))"el voice call moves around, it is notunlikely that the user device may encounter that the -" radio coverage is beinglost. After all, this is a mobile system, and this of course may happen fre2uentlydepending on how users move around. For this purpose, ;88 specifiedmechanisms to hand over an ongoing voice call in I)*7))"el. +hat happens thendepends on whether the new 0target system1 can support I)*'/oI87))"el or not.If this is the case, this will be solved through a packet handover procedure and the

I)*'/oI87))"el session will continue after the handover. If this is not the case, theI)*7))"el session will be handed over to a circuit'switched call in *), +C%)Aor 9#&"" 0!O to legacy C* V *&/CC 0*ingle &adio /oice Call Continuity11. "oachieve a smooth handover, this procedure involves pre'registration of the terminalin the target system C* domain 0i.e., the system that the terminal will be attached toinstead of -" after the handover1 and an efficient handover signaling. If no I)* ispresent in the network at all or -" users have to temporarily leave -" during voicecalls as described above, the )) interacts with the circuit'switched infrastructureto achieve this temporary suspension of the -" services. "he case of a packethandover to *)7+C%)A is supported using handover signalling over the *; 0orn1 interface between the )) and the **N. "he corresponding interface forC%)A is called *9B9 and connects the )) to the S&NCT used for e!&8%. In orderto further optimiKed the packet handover performance, packet forwarding may beused 0it is optional1. "his means that any packets destined for the user device that

may have happened to have been sent Udownwards from the 8%N + 0to either the**N, *erving + or e!&8% !*+1 may be forwarded to the corresponding nodein the target system. "his is not absolutely re2uired, but may improve the usere#perience of a handover, since in theory no data need to be lost during thehandover. "he case of packet forwarding between -" and *)7+C%)A issupported over n7*= between **N and *erving +, whereas the case of -"'e!&8% packet forwarding is supported over the *9B; interface between the *erving+ and the !*+.


!

' ;> ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



46/363

Note$ if the I)*I is not available, both voice and *)* support comes from C*'%omain 0legacy )*C1. ut there is a difference between *)* support and voicesupport from )*C WX *)* transmission and reception takes place in -", the 3does not leave the '3"&AN 0but for *upplementary *ervices1 but for C*'/oice, the3 need to SfallbackT to legacy &AN73"&AN 0C*'%omain1 in order to establishmobile originating or mobile terminating C*'call.In the case ))"el7/oI8'I)*Gcall is not supported by the 0legacy1 target network,there are functions for handing over an I)*'based ))"el session to a circuit'switched voice call in *), +C%)A or C%)A 9#&"". "his handover is realiKedthrough procedures e#ecuted over the *v interface between the )) and the )*C*erver 0for *) and +C%)A1 or the *9B: interface between the )) and the9#&"" )*C. "his procedure is known as U*ingle'&adio /oice Call Continuity0*&/CC1.Finally, support for always falling back to circuit'switched calls even when in -"coverage 0which means that no I)* infrastructure is used1 is supported through

signaling over the *s interface between )) and a *)7+C%)A )*C *erver orover the *9B: interface connecting the )) to an 9#&"" )*C. "his procedure isknown as UCircuit'*witched Fallback 0C*F1.

S'mmar)For the case of localiKed '3"&AN deployments within e#tended :7; C*coverage, and mobility across the boundary of '3"&AN coverage during a voicecall$ the assumption is that 091 voice over I8 0via I)*1 is deployed by the operator,and 0:1 due to the limitations of radio bands, no parallel operation of radiotransceivers 0for both radio technologies1 is possibleY the solution is called *ingle&adio /oice Call Continuity and is based on an application server in the I)*domain, from where interworking towards )*C is controlled.For the case of overlapping coverages of '3"&AN and :7; C*, where theoperator does not 0yet1 want to deploy I)* for voice services, and the decision onthe voice call handling is taken before the corresponding originating or terminatingre2uest is made7accepted$ a fallback mechanism to C* has been developed0C*F7C* fallback1. *ervices related to voice 0*)* and *upplementary *ervices1were included in this mechanism.oth solutions have variants for the legacy C* technology stemming from ;88 orfrom ;88: 0i.e., 9#&""1. Altogether they constitute high investments intostandardiKation, development, testing, rollout and deployment7operationY however,one can see from this fact also their importance for operators.Another solution for voice in -"78* was proposed P/o-AQ, but finally notfollowedon in ;88$ C* over 8*, meaning that the legacy C* protocol stack is leftunchanged, and the C* signaling is only encapsulated and transported over thevolved 8* layer to a the point of interconnection 0enhanced )*C1, where it is thende'capsulated and handed over to the conventional C* protocol machine again.

7etail on SRCC BSingle Radio oi+e Call Contin'it)As e#plained above, a concept for smooth interworking at least for ongoing voiceservices between the 8* system and legacy C* system 0both in its ;88 andC%)A:BBB, 9#&""1 was sought. It relies on standard means ofare two variants$9. ased on dual radio$ it can be applied when the characteristics of the two involvedradio technologies allows parallel operation of transceivers 0senders and receivers1.A solution was developed already in &el. @ for /CC between legacy C* and pre'*A8* technology 0in practice +-AN1. In such a case the two systems need not becoupled tightly, because handover preparation for the target system can take placewhile the terminal is still connected via the source system. %ual radio /CC is notdiscussed further here.


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' ;? '



47/363

:. For single radio 0*&/CC1$ if the bands of the two involved radio technologies aretoo near, due to physical limitations of radio transmission 0interference1, transceiverscannot operate in parallel. In this case the handover must be prepared in the targetaccess while the terminal is connected to the source system, because no connectioncan be opened in parallel.It leads to a tighter coupling than variant 9, both in terms of interfaces andprocedures.ased on the e#pected rollout scenarios of '3"&AN, only the direction from3"&AN'8* M C* was considered for *&/CC. "he underlying assumption is thatC* coverage e#ists virtually everywhere, and then there is no need to continue a C*call in 8*, if the corresponding coverage is entered. "he case of '3"&AN onlycoverage is thus not covered.

"he I)*'/oI8 call is anchored in I)* before *&/CC handoverY as the 3 moves, itperforms measurements of the radio signal 0strength and 2uality of transmission1,

both for the '3"&AN cell it is currently using and the neighboring &AN73"&ANcells 0it knows these thanks to instructions by the serving cell1. "he measurementreports are sent to the serving cell and used to determine the handover point, andeventually the concrete cell to be used after handoverY in this voice support of&AN73"&AN cells are utiliKed. "he eNode then sends a *&/CC triggermessage to )). )) initiates the intersystem handover via a trigger messageacross *v, which leads to resource reservation in &AN73"&AN like for an intra'C* handover. Also, the )*C server initiates signaling for call establishment towardsthe *&/CC A* 0application server for *&/CC1. After resource reservation has beenacknowledged back to ))7eN, eN commands the 3 to move to&AN73"&AN. "he 3 performs there C* handover completion. "he full messageflow details is presented in sub'section in chapter ?."he *&/CC solution does not only support a single voice session to be handed overseamlessly. It can also be used if the voice call occurs in combination with a non'voice service, like video streaming, although in this case the non'voice traffichandover does not enJoy the same smoothness7seamlessness. *till, the usere#perience for voice is most critical, and small interruptions of e.g. the video orfallback to lower bandwidth are deemed acceptable. +ith non'voice components, a8* handover procedure is performed in parallel to the 8*'C* handover.administered by O)A %evice )anagement and corresponding data is transferredto the 3Y a specific )anagement ObJect has been defined, containing settings fornumbers to be used in session transfer re2uests, preference of transfer directions,preference of media in different access systems, detailed conditions on when thetransfer shall take place.

Note that 3"&AN73)"* in &el. supports also the /oI87I)* Call with a *&/CC!O functionality

For C*'Fallback there are basically following signaling methods possible in orderto push the 3 from '3"&AN to other &A" like *)78&* or 3)"*.

For changing the 3 to 3)"* the *pec defines the 8*'!andover to 3)"* and the&&C Connection &elease with &edirection Info for 3)"*.For changing the 3 to *)78&* the *pec defines beside the 8*'handover alsothe eNACC and CCO and of course the &edirection.Note that this procedures are layout in later chapter of the course.


!

' ;@ ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



48/363

!*0 3roto+ol Sta+>

!*0*! Control 3lane / E-;TRAN - E3C

"he obJectives of this section are to depict the protocols which are related tothe control plane between 3, )) and !** and to highlight whether theseprotocols are '3"&AN'specific, 8C'specific or generic.

Image 7e+ri5tion

"he *)' and ))'protocols are referred to as NA*'protocols.

*ince *)'messages may be piggybacked inside ))'messages, the *)'protocol has been depicted as illustrated above.


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' ; '



49/363

Room for )o'r Note,


DIAMETER

Succe$$or o the %A7I*S rotoco! PDCP /acket 7ata 'on#ergence /rotoco!


PH% /hy$ica! ayer

EMM E/S +o,i!ity +anagement (3GTS

2.301)

RLC %adio ink 'ontro!


RRC %adio %e$ource 'ontro!

ESM E/S Se$$ion +anagement (3GTS2.301)

S1-AP S1 A!ication /art

HSS 9ome Su,$cri,er Ser#er :3GTS23.002;. 9SS re!ace$ the 9% ith3G// %e!. are operatorspecific.

P;"* ;;.9B:Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' =? '



57/363

Room for )o'r Note,



IK Integrity Key (3GTS 33.102)

AK Anonymity Key (3GTS 33.102) MAC +e$$age Authentication 'ode

AKA Authentication and key agreement(3GTS 33.102)

RAND %andom -um,er

AMF Authentication management ie!d(3GTS 33.102)

S!N Se4uence num,er (u$ed in *+TS=$ecurity architecture " 3GTS 33.102)

AUTN Authentication Token (3GTS 33.102) UMTS *ni#er$a! +o,i!e Te!ecommunicationSy$tem

CK 'ihering Key (3GTS 33.102) RES Exected %e$on$e (3GTS 33.102)


!

' =@ ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



58/363

!** &e) 7erivation 2'n+tion B&72

"he obJective of this section is to illustrate the principles of the key derivationfunction used within the 8*'environment.

P;"* ;;.=B9 0A.9.91Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' = '



59/363

Room for )o'r Note,



KDF Key 7eri#ation &unction (3GTS33.01)

EPS E#o!#ed /acket Sy$tem SHA Secure 9a$h A!gorithm

HMAC Keyed 9a$hing or +e$$ageAuthentication (%&' 210)


!

' =H ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



60/363

!***! Com5re(enion C(e+> 9 3ra+ti+al E4er+ie,T(e &72 SB!1 for &BAS8E

"he obJective of this section is to illustrate to the student how the key50A*)1 is derived from concatenated information elements and the C5 andI5 derived from the 3)"*'A5A.

uestion No ;$ Fill in the input parameters to derive 50A*)1 applying the *09B1key derivation function.

to be continued on the ne#t page


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' >B '



61/363

Room for )o'r Note,


ASME Acce$$ Security +anagement Entity KDF Key 7eri#ation &unction (3GTS33.01)

CK 'ihering Key (3GTS 33.102) SHA Secure 9a$h A!gorithm

HMAC Keyed 9a$hing or +e$$ageAuthentication (%&' 210)

UMTS-AKA

*ni#er$a! +o,i!e Te!ecommunicationSy$tem = Authentication and KeyAgreement (3GTS 33.102)



!

' >9 ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



62/363

!***!*! In5't 3arameter

"he secret input parameters are I5 and C5 with a length of 9? octets each. "heystem from a previous run of 3)"*'A5A P;"* ;;.9B:Q.

Other input parameters are the serving network identity 0)CC Z )NC1 and *N0#or1 A5 which also stems from the previous run of 3)"*'A5A.

Although C5 and I5 together provide a key length of :>? bits and although thelength of 50A*)1 is :>? bit, the efficient key lengthis ultimately restricted by thesubscriber key 5i with a length of only 9: bit.

P;"* ;;.=B9 0A.:1Q


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' >: '



63/363

Room for )o'r Note,




AK Anonymity Key (3GTS 33.102) MCC +o,i!e 'ountry 'ode :IT*=T E.212;

ASME Acce$$ Security +anagement Entity MNC +o,i!e -etork 'ode

CK 'ihering Key (3GTS 33.102) S!N Se4uence num,er (u$ed in *+TS=$ecurity architecture " 3GTS 33.102)

UMTS-AKA

*ni#er$a! +o,i!e Te!ecommunicationSy$tem = Authentication and KeyAgreement (3GTS 33.102)


!

' >; ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



64/363

!**$ E3S-A&A in O5eration d'ring Initial Atta+( 3ro+ed're

"he obJective of this section is to illustrate how the )), the eNode andthe 3 determine the different security keys which are re2uired within the8*.


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' >= '



65/363

uestion No =$ Fill in the missing keys 0[WX 50#yK11 into the image.

Room for )o'r Note,


ASME Acce$$ Security +anagement Entity NAS -on=Acce$$=Stratum

AUTN Authentication Token (3GTS 33.102) PLMN /u,!ic and +o,i!e -etork

CK 'ihering Key (3GTS 33.102) PS /acket Sitched

CRC 'yc!ic %edundancy 'heck RAND %andom -um,er

DIA 7iameter /rotoco! (%&' 3 %&'3> ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



66/363

!**: ;e of t(e different Se+'rit) Algorit(m

"he obJective of this section is to illustrate where which security algorithmsare applied within the 8*.

5ey point of this section is that there is no integrity protection done for userplane data.


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' >? '



67/363

Room for )o'r Note,


CRC 'yc!ic %edundancy 'heck ESM E/S Se$$ion +anagement (3GTS2.301)

DL 7on!ink MME +o,i!ity +anagement Entity (3GTS23.01) (%e!. onard$)

EEA E/S Encrytion A!gorithm (3GTS33.01)

NAS -on=Acce$$=Stratum

EMM E/S +o,i!ity +anagement (3GTS2.301)

PDCP /acket 7ata 'on#ergence /rotoco!

eNB Enhanced -ode 6 RRC %adio %e$ource 'ontro!

EPS E#o!#ed /acket Sy$tem UL *!ink


!

' >@ ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



68/363

Leon Learned / Con+l'ion


!

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' > '



69/363

C(a5ter 0,T(e Non-A++e-Strat'm, E88 9 ES8

Ob=e+tive

*ome of your 2uestions that will be answered during this session

@(at are im5ortant E88- and ES8-5e+ifi+ 5ro+ed're?

@(at i t(e format of E88- and ES8-meage?

How are im5ortant +enario li>e atta+(ment and tra+>ing area '5dating

5erformed?

The on-A!!ess-Strat"m# E$$ % ES$

0

' >H ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



70/363

0*! E3S 8obilit) 8anagement BE88

0*!*! Im5ortant E88-3ro+ed're

"he obJective of this section is to illustrate the different ))'procedures.

8rocedures can be combined with each other. #ample$ "he authenticationprocedure is typically part of the attachment procedure.

P;"* :=.;B9 0>.9.:1Q


0

INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11' ?B '



71/363

0*!*!*! Common 3ro+ed'reCommon procedures are typically embedded into a given specific procedure.

0*!*!*0 S5e+ifi+ 3ro+ed're

0*!*!* Conne+tion 8anagement 3ro+ed're

Room for )o'r Note,


E-UTRA E#o!#ed *+TS Terre$tria! %adio

Acce$$

GUTI G!o,a! *ni4ue Termina! Identity

(3GTS 23.003)

EMM E/S +o,i!ity +anagement (3GTS2.301)

NAS -on=Acce$$=Stratum

EPS E#o!#ed /acket Sitched UE *$er E4uiment

The on-A!!ess-Strat"m# E$$ % ES$

0

' ?9 ' INACON GmbH 1999 - 2014. All rights reserved. Reprod!tio" #"d$or "#thori%ed se o& this m#teri#l is prohibited#"d 'ill be prose!ted to the &ll e(te"t o& Germ#" #"d i"ter"#tio"#l l#'s. )ersio" Nmber 1.*11



72/363

0*!*0 State 8a+(ine

"he obJective of this section is to illustrate the different ))'states and theirrelationship.

P;"* :=.;B9 0>1Q

)) and *) are linked with each other P;"* :=.;B9 0=.:1Q. "his relatesparticularly to the piggybacked Sdefault 8*'bearerT establishment when the 3attaches to the 8C.

0*!*0*! Relation(i5 between E88 and EC8In general, C) relates to the presence of an *9'bearer plus &&C'connection. Aslong as both are present, the 3 is in C)'CONNC"% mode. 3pon release, the3 switches to C)'I%- mode."herefore, the 3 may well be ))'registered but still be C)'idle.

+hile the 3 is in C)'CONNC"% state, the network is in charge tocontrol the 3'mobility. +hile the 3 is in C)'CONNC"% mode, thelocation of the 3 is known with the granularity of a cell inside an eNode.

+hile the 3 is in C)'I%- mode, the location of the 3 is known with thegranularity of a tracking area. +ithin C)'I%- mode, the 3 shall performautonomous cell reselection and tracking area update procedures.

P;"* ;?.;BB 0A.:1, ;"* :=.;B9 0>.9.;.:.:.=1Q

LTE-SAE Overview

LTE-SAE Overview and Radio Signaling

Documents

Transcript of LTE-SAE Overview and Radio Signaling